-
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
Plugged in D435 at boot gives errors #2932
Comments
I am also experiencing this issue. It seems to occur for me when after a sleep state. I have to unplug and replug to remedy. 64-Bit Ubuntu 16.04 LTS, realsense viewer V2.17.1, Intel D415 FW 05.10.13.00. This occurs in the viewer and programmatically connecting through python script. |
The problem still is there with 2.18.1 and FW 05.11.01.00 |
@kevindehecker Yes, this problem is still under triage. Will update here when get fix. Thanks for your patience! |
Hello @kevindehecker,
Also, is it possible that you're using a pre-production unit ? (camera's serial number can be useful as well) |
I'm having the same issue with this see screenshot. Happens both to D435 and D415 Using v2.18.0 |
@TheMikeyR , the error you encounter is an unrelated regression in V2.18.0 that was fixed in 2.18.1. |
@ev-mp you are right it is fixed in 2.18.1 |
Thanks for the input but the log is missing the device initialization part that is essential:
The logger is not supposed to exit, so "ctrl+c"-ing is ok. |
@kevindehecker , thanks again. In order to facilitate the reproduction - |
No, this is directly connected to my laptop. Can also reproduce with a NUC 7i3BNK (again directly plugged in) and other laptops. |
@kevindehecker Please try the latest FW v5.11.6.200 which should fix the issue. The FW can be got from |
@kevindehecker Did you get chance to try FW v5.11.6.200? Looking forward to your update. Thanks! |
@kevindehecker Didn't get response from you for several weeks. Will close this ticket at this point. Please feel free to open new tickets if you still have question, Thanks! |
Sorry, was on vacation. Will try it out Friday! |
Hmm, well unfortunately I can still reproduce this problem with steps posted in the opening post. But, I could only update to 5.11.4, the link you provided does not show v5.11.6.200 ...? |
Can you reopen this please? Or should I go through the trouble of copying the whole thing into a new issue...? |
@kevindehecker Sorry to know that you still have the issue. Please copy it to new issue and we will look into it. |
Issue Description
I get the following error in the Realsense viewer:
...When I do the following:
Step 4 can also be reproduced from a skeleton code project I have, which does nothing else then enumerating the RealSense device, and attempt to change a setting (although in this case, I have to switch the same setting on and off before some similar error occurs). I can reproduce this issue on all my systems (various types of x86 linux systems).
Currently, I can circumvent the problem in two ways:
1a. Replug the usb cable. This only has to be done once per boot, then this problem never happens anymore.
1b. Don't boot the system with the RS already plugged in
2. Perform a hardware reset in the rs2::device. Although this does seem to fix the problem, doing this preventively seems to give a set of problems of its own. (e.g. I got a access violation error )
The text was updated successfully, but these errors were encountered: