Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inaccurate port naming on gazebo_icub_<body_part>_ft_sensor_nws_yarp.xml files #36

Open
SimoneMic opened this issue Mar 29, 2022 · 1 comment

Comments

@SimoneMic
Copy link

Hello,

I've noticed that the port names for force sensors are not explicit/self explanatory.

For example: <param name="name"> /icubSim/left_arm </param>
I propose to change to /icubSim/left_arm/ft so that it's explicit about the data transmitted.

At the current state I fear that there could be conflict with the controlboard device of the body parts, in regard with the RPC port, that has the same naming.

@SimoneMic SimoneMic changed the title Inaccurate port naming on gazebo_icub_<body_part>_ft_sensor_nws_yarp.xml files Inaccurate port naming on gazebo_icub_<body_part>_ft_sensor_nws_yarp.xml files Mar 29, 2022
@traversaro
Copy link
Member

Hi @SimoneMic, I think the choice done in stickBot was done in coherence with the rest of the icubs, that use those configuration (see for example https://github.com/robotology/robots-configuration/blob/master/iCubValparaiso01/wrappers/FT/left_arm-FT_wrapper_multipleSens.xml).

At the current state I fear that there could be conflict with the controlboard device of the body parts, in regard with the RPC port, that has the same naming.

Which conflict can occur? Do the two device create the port with the same name? In that case, I would expect this to also happens on real robots.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants