Realsense: Handling USB Connection Errors and Ensuring Program Stability #13081
Replies: 2 comments 1 reply
-
Hi @wataru-okumura xioctl errors are typically related to a conflict between the librealsense SDK and the Linux kernel. I have seen an example of C++ code that tries to catch this error and handle it.
An alternative to using a catch would be to build librealsense from source code with CMake with the flag -DFORCE_RSUSB_BACKEND=TRUE included in the CMake build instruction. An RSUSB build of the SDK bypasses the kernel. |
Beta Was this translation helpful? Give feedback.
-
It's no problem at all. xioctl errors are kernel messages, so if you need to check if they have occurred then you could examine the kernel log using the information at the RealSense troubeshooting documentation link below. https://dev.intelrealsense.com/docs/troubleshooting#general-linux-kernel-log |
Beta Was this translation helpful? Give feedback.
-
I have always used realsense. Thanks for the daily updates.
I would like to discuss one point.
When using librealsense, you may keep getting the following error. It is probably caused by a bad USB connection.
In this case, command operations on the console will be disabled and recovery will take time.
So, when such an error occurs (or continues to occur for a certain period of time), is it possible to change the code so that it throws an exception or otherwise terminates abnormally and appropriately without running out of control?
Beta Was this translation helpful? Give feedback.
All reactions