You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When use the set_devices_changed_callback to detect device connect and disconnect events. We noticed that this mechanism does not always invoke the registered callback of disconnect events. We have not come across any issue with a subsequent connect. In other words, even if the callback was not invoked for disconnect, it gets invoked when the sensor is connected back.
Is there a recommended way to reliably detect the sensor disconnects?
The text was updated successfully, but these errors were encountered:
Hi @banuprathap Did you build the librealsense SDK using the RSUSB backend method or with the kernel patching method, please?
If you are using RSUSB (which is known to have issues with timing when polling) then you could either use a kernel-patched librealsense build instead or reduce the time period between each polling of the device under RSUSB, as described in the comment linked to below and the comments beneath it.
When use the
set_devices_changed_callback
to detect device connect and disconnect events. We noticed that this mechanism does not always invoke the registered callback of disconnect events. We have not come across any issue with a subsequent connect. In other words, even if the callback was not invoked for disconnect, it gets invoked when the sensor is connected back.Is there a recommended way to reliably detect the sensor disconnects?
The text was updated successfully, but these errors were encountered: