[cob_hardware_config] further simplify configuration structure (modules and components) about cob_robots HOT 10 OPEN

we won't work on this for now

No need to close it.

from cob_robots.

After cleaning up unsupported robots #588, we will start introducing a more generic robot-/module-/component-base structure for all URDF, launch and config files... as discussed with @ipa-fmw @ipa-nhg @ipa-mdl

This will allow further de-duplication of code, more consistency between robots, better harmonization of HW/Sim-behavior as well as easier future maintenance and up-scaling...

from cob_robots.

#622 is a significant step towards a simplified configuration structure

I will apply a similar concept for the other "unifiable" components, e.g. torso, head, sensorring, arm(s),...

from cob_robots.

Also, we would need to adjust the structure to the robot names we are using now to refer to a (physically existing) robot composition, i.e. cob4-paul-ingolstadt...following @ipa-tif's spreadsheet Verbauliste.xlsx

The ultimate goal could be to even generate launch files based on a module configuration using a tool based on @ipa-mdl's roslaunch-dump

from cob_robots.

@ipa-mdl asked for input about roslaunch-dump (with the final goal being added to roslaunch)
ros/ros_comm#1022

from cob_robots.

reminder for @ipa-fxm: extract sick scanners from base urdf + then remove nav configs for mlr bases as they do not have laser scanners anymore

from cob_robots.

extract sick scanners from base urdf + then remove nav configs for mlr bases as they do not have laser scanners anymore

done in #654

from cob_robots.

atm none of the solutions proposed by @ipa-fxm and @ipa-nhg fully meet our requirements
also current efforts require a final decision regarding future maintaining responsibilities and supported hardware

thus, I'm moving it to Backlog

from cob_robots.

we won't work on this for now

from cob_robots.

it's been in the sprint backlog anyway...

from cob_robots.