-
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
Problems running 2 d435i cameras on Ubuntu 22 with Docker #3234
Comments
Hi @kushal2507 If you are launching with 2 cameras then I would recommend using the rs_multi_camera_launch.py launch file instead of rs_launch.py, or launching each camera with an rs_launch.py instruction for each individual camera in two separate terminal windows. If your preference is to launch with a single rs_launch.py instruction then you can define a separate camera_name for each camera to ensure that the launch can correctly tell the two cameras apart. |
hi @MartyG-RealSense I have my custom launch file, it is laucnhing the two cameras with different names, Main launch file
python file with properties being loaded from the main launch file
The two yaml files that you see in the launch.py file, adds unique serial numbers to each camera |
Do the two cameras launch correctly if Usually, only one yaml file is imported into a RealSense ROS launch and I have not seen a previous case where two yaml files were imported, so there is no previous precedent to confirm whether it can work. Would it be possible to simplify the system by defining the configs for both cameras in a single yaml? |
Issue Description
I am truing to run 2 intel d435i cameras on my ros2 humble ubuntu 22 docker container. I followed the instructions mentioned here to clone and compile librealsense. Attached below is the log after I launch the two cameras :
These are the parameters I am using :
After receiving this error
WARNING [137682959205952] (uvc-sensor.cpp:131) Frame received with streaming inactive,Depth0, Arrived,0.000000 1729853021018.471680
the images are no longer published for that camera.The text was updated successfully, but these errors were encountered: