You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
The text was updated successfully, but these errors were encountered: