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

iCubGazebo2_5_visuomanip: provide port names consistent with the real robot #47

Open
traversaro opened this issue Jul 27, 2020 · 1 comment

Comments

@traversaro
Copy link
Member

traversaro commented Jul 27, 2020

See #44 (comment) .

In particular, according to #44 (comment) the real robot publishes RGB images as:

  • /icub/cam/right
  • /icub/cam/left

While the Gazebo simulated robot:

  • /icubSim/cam/left/rgbImage:o
  • /icubSim/cam/right
@xEnVrE
Copy link
Contributor

xEnVrE commented Mar 30, 2023

I am considering again this issue, after #195 and vvv-school/assignment_make-it-roll#9.

At the moment, we can only decide the initial part of the port name:

<device xmlns:xi="http://www.w3.org/2001/XInclude" name="left_camera_rgbd_nws_yarp" type="rgbdSensor_nws_yarp">
<param name="period">0.033</param>
<param name="name"> ${portprefix}/cam/left </param>

To solve the problem from the root, what is missing is having the possibility to decide the final part of the port names within the rgbdSensor_nws_yarp device.

The final part of the ports is hardcoded at the moment, as can be seen in https://github.com/robotology/yarp/blob/03a47d532b048bd862eb763c58badf2f7576847d/src/devices/RGBDSensor_nws_yarp/RgbdSensor_nws_yarp.cpp#L255.

Changing that behavior would imply adding some parameters and proper defaults to avoid the necessity to change a huge number of configuration files.

cc @pattacini

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