-
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
Cannot connect to multiple cameras after updating to v3.2.3 #2171
Comments
Hi @ParthasarathyBana Is the second camera detectable if the two cameras are launched in separate ROS terminals instead of with the multiple camera ROS2 launch file? Terminal 1 Terminal 2 |
When launched in separate terminals , it looks like both the cameras are detected. However, one of the cameras produces a hardware stream error as shown below:
Image msgs are seen via |
Is the affected camera able to successfully stream depth in the RealSense Viewer tool? Does the depth stream start failure still occur if you add initial_reset:=true to the roslaunch instruction of the affected camera to reset it at launch? ros2 launch realsense2_camera rs_launch.py camera_name:=my_d415 serial_no:=135322062929 initial_reset:=true |
Yes, I am able to see the color and depth feeds from both cameras using the As for the |
Which ROS2 version are you using, please? (Foxy, Galactic, etc) If you are using Galactic, advice relating to the Depth stream start failure hardware error is offered in IntelRealSense/librealsense#9829 (comment) In that same discussion in IntelRealSense/librealsense#9829 (comment) the RealSense ROS user in that case shared the details of what enabled them to view the image in RViz2. |
We are using We previously had both cameras working using the package specs as mentioned above #2171 (comment). Therefore, we rolled back to the previous specs and it is now working. I am not sure why this does not work for For now we will continue with the previous versions and look forward to getting an update in the future that would solve this issue. Besides, I can only help you with testing this on our systems and don't think we can help in developing support for |
The ROS2 wrapper - including 3.2.3 - already supports Rolling. I will close this case though as you suggest, but please feel free to return to the subject on tis support forum at a future date if you need to. Good luck! |
Thanks for your help! I just wanted to highlight that you say it is working for |
I am not aware of any changes in the last release to introduce these errors. I am not sure what's wrong with watching with RViz but I suggest checking that the "Fixed Frame" is set to something valid like "camera1_link" maybe. Alternatively, you can test using rqt_image_view. |
This issue is related to
D415
cameras andros2
.Our robot was set up with two D415 cameras and both the cameras were streaming image feed correctly with the following config:
realsense_ros
-v3.2.2
librealsense2
-v2.49.0
firmware
-v5.12.15.50
After updating to the recent versions, as follows, one of the cameras is not detected when we run the following launch script.
realsense_ros
-v3.2.3
librealsense2
-v2.50.0
firmware
-v5.13.00.50
ros2 launch realsense2_camera rs_multi_camera_launch.py serial_no_camera1:=135322062929 serial_no_camera2:=135322061686
Only feed from camera with
serial_no_camera1
is detected and displayed onrviz2
.The following is the output from the terminal.
The text was updated successfully, but these errors were encountered: