-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
rosrun tf view_frames shows no tf being published #120
Comments
Hi @reaganlo, were you able to reproduce this issue? Just checking in to see if there are any updates on this. Please let me know if you need more information. |
Hi @sinhau , I was able to reproduce the error. We will look into this and provide you an update. As a workaround for multiple cameras, could you please do the following:
r200_nodelet_default_1.launch.txt |
Thanks for your reply @reaganlo! I tried out your suggestion. One of the cameras is unable to launch sometimes when I call the two launch files simultaneously (see terminal output below). This seems to only happen when I'm launching both camera1 and camera2 simultaneously. If I launch them one after the other, it works fine. Here are my launch files:
|
@sinhau Yes, this can happen when you try to launch 2 cameras simultaneous because it leads 2 separate processes trying to access the librealsense "context" at the same time. Just like how you noticed, I would suggest you launch them one after the other. |
It would be good for the drivers to not fail when accessing the "context" simultaneously. @reaganlo are there plans on fixing this? |
@sinhau and @tulku - I looked into this further and the root cause can be traced to this issue in the roscomm libraries (roscpp):ros/ros_comm#146 Since that is unlikely to be fixed per their maintainers, the work-around of running from 2 launch files is the only option right now. |
Hi! I agree that the solution is to have multiple launchfiles, however that option is not currently working. As soon as you try to start too nodes (via a launchfile, so they start at the same time) one of the nodes crashes. This is probably a different bug, I can open it tomorrow. |
@tulku , yes I'm seeing the same issue. Looks like this bug was introduced in one of the newer releases because launching multiple cameras via separate launch files was working for me on 1.4.0. Thanks for opening this issue! |
@mkhansen-intel I've created the issue that should be fixed before being able to use multiple nodelet managers. #156 |
Since the underlying issue is in roscpp and is not scheduled to be fixed, we're looking into a fix for this one that would fork a new process before calling the static transform publisher. We'll update this issue* with results. |
fyi I'm also interested in having tf's for multiple cameras, so I'll be watching this. |
Fixed in release 1.7.0 |
System Configuration
Please complete Your Configuration detail below. Refer to the BKC at Configuration.
I'm launching two R200 cameras using the r200_nodelet_multiple_cameras.launch. I modified the launch file as shown below to change the
enable_tf
parameter to true. When I run the launch file, both cameras launch and I am getting all the data. The ROS logs even shows that cameras should be publishing transforms (see terminal output below) However, when I runrosrun tf view_frames
, the output frames.pdf file says no tf data received. For some reason no tf is being published. Moreover, when I runrostopic echo /tf_static
, I only see camera2 tf's.r200_nodelet_multiple_cameras.launch
Terminal output after running the above launch file
The text was updated successfully, but these errors were encountered: