AntoineWefit
commented
5 years ago We actually encounter a similar issue which is preventing the cameras to work properly after any boot. A reliable fix is indeed to unplug/replug, but it's quite inconvenient... Updating the firmware also doesn't do anything (for now), plus it's quite a pain to update our codes to match the new firmware/libraries and hope that this problem is solved.
I notice that your camera is plugged in as USB 2.1, is that a consequence of the problem or intentional ? Maybe scheduling a USB reset at your computer boot could do the trick ? Haven't tested it yet though...
I've also tried to update the firmware to 5.11.6.200, according to your past advices, but couldn't find this version of the firmware on the driver page... It only goes up to 5.11.4.
Not sure if it's going to help you but here is a copy : Signed_Image_UVC_5_11_6_200.zip
piraog
m9dfukc
antoniodourado
Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):
All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)
Issue Description
When opening Realsense Viewer or trying to run a python script to stream from the camera, i get the following error:
Now, the camera usually works perfectly fine, and I'm really happy with the performances. But from time to time I get stuck with this error and forced to replug the device. From what I read on the now closed issue #2932 and my experience, it seems like it happens when I restart my computer with the camera plugged in and don't replug the camera afterwards.
Following your instructions on #2932 I've logged the infos when I try to open the viewer (copied for the fw-logger): fwlog.log
I've also tried to update the firmware to 5.11.6.200, according to your past advices, but couldn't find this version of the firmware on the driver page... It only goes up to 5.11.4.
The problem is that in my use case, my computer operates in a remote place and must restart now and then, so I often end up stuck with this error and replugging the device isn't a long term solution for me.
Do you have any solution since #2932 ? Is it being looked into? Is their any way to prevent being stuck in this situation, maybe a protocol to follow before shutting down?
Thanks in advance for your response.