-
Notifications
You must be signed in to change notification settings - Fork 4.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
D415 got stuck/frooze in wait_for_frame() after unplug-replug #10543
Comments
Hi @LLY13 It is possible for a program to become unresponsive after the camera is disconnected by some means (such as physically unplugging it from the USB port). RealSense users have sometimes created workaround mechanisms when frames stop arriving, such as automatically resetting the camera with the hardware_reset() instruction. A C++ case that discusses the issue is at #10084 |
I have tried use hardware_reset() before this I posted this issue, seemed like useless. I'd just try not to unplug it. |
When you unplug, how long on average do you wait before re-inserting? Upon disconnection, the pipeline should be able to resume streaming if the camera is reconnected within 5 seconds, otherwise the connection time-outs. |
less than 1 seconds. yep most time reconnected in 5 seconds. but somtimes 15s even 45s+ |
I would recommend trying a wait period of 2 seconds before re-inserting to give the computer time to properly register the removal of the device from the USB system and see whether that reduces the occurrences of the long time-out events. |
Hi @LLY13 Do you require further assistance with this case, please? Thanks! |
no thx |
Thanks very much @LLY13 for the update. As you do not require further assistance, I will close this case. Thanks again! |
Issue Description
D415 got stuck in wait_for_frame() after unplug-replug about 45 seconds occasionally. I just updated everything today but it still happend in my code. So I copied demo code, still got stuck. I need know it's normal situation or exception. In the image, I unplugged and replugged immediately.
The text was updated successfully, but these errors were encountered: