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

Static transformations missing when running the multiple camera example #141

Closed
tulku opened this issue Oct 26, 2016 · 2 comments
Closed

Comments

@tulku
Copy link

tulku commented Oct 26, 2016

System Configuration

Version Your Configuration
Operating System Ubuntu 16.04.1 LTS
Kernel 4.4.0-45-generic #66-Ubuntu SMP
Backend v4l
ROS kinetic
ROS RealSense 1.5.0
librealsense 1.11.0
Camera Type-Firmware r200-1.0.72.06

Expected Behavior

The static transformations for both cameras should be found in the tf tree.

Actual Behavior

When running the r200_nodelet_multiple_cameras.launch only one of the cameras is able to publish it's static transforms. This probably happens because the nodelet manager will have to latched publishers to tf_static, one per camera, and that does not work correctly, as explained here:

http://wiki.ros.org/tf2/Migration#Addition_of_.2BAC8-tf_static_topic

Steps to Reproduce

Start the r200_nodelet_multiple_cameras.launch and check the tf tree. This can be done doing:

$ rosrun tf tf_echo camera2_link camera2_depth_optical_frame
$ rosrun tf tf_echo camera1_link camera1_depth_optical_frame

You will see the camera2 frames being correctly resolved but the camera1 frame missing.

@tulku
Copy link
Author

tulku commented Oct 26, 2016

This is related (or even a duplicate of) #120

@reaganlo
Copy link

@tulku As you figured out, since this is a duplicate of #120, I am closing this one. Please look out for updates on the other thread.

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