Closed mjsobrep closed 4 years ago
If the cameras work correctly after a stop and restart, I wonder if you could incorporate a start-stop-start into your sh script.
Start
roslaunch realsense2_camera rs_rgbd.launch camera:=cam_X serial_no:=
Well, with the roslaunch API
I can start and stop the cameras when errors are detected. Such that it is a way to solve this situation.
Thanks very much @jcgarciaca
Right now I don't have a better solution for the occasional RS2_USB_STATUS_BUSY error.
RS2_USB_STATUS_BUSY is a message of the RSUSB backend which is built into the ros-librealsense2 package.
For most platforms, especially when using multiple cameras, it's best to use the build that uses the v4l backend.
That build exist in the normal installation of librealsense2 as described in librealsense2 installation guide.
In order to use it you'll have to remove the ros-librealsense2 and realsense2_camera installation:
That is:
sudo apt purge ros-melodic-realsense2_camera
And rebuild realsense2_camera from code
Does the reliability seems better with that librealsense2 build?
I just made the mistake of updating software (dumb) and am now having trouble with a setup running two D415 cameras. My launch file had been working well for sometime. Rather than just downgrading, I would like to understand the source of the problem and fix it.
The system seems to think that the cameras are busy on startup, I do not know why. If I am running in rosmon, I kill the nodes, and then restart them, then it seems to work, although CPU usage goes crazy. Simple relaunching does not solve the problem.
Weirdly, when I turn on the computer, if I launch realsense viewer, there are no problems. If I run the ros launch file above and then open realsense viewer, the cameras do not show up.
If downgrading software is the way to go. How do I downgrade librealsense, the ros stack, and the firmware all at once? Or do I only need to downgrade one? Where should I be downgrading to?
console output: