Closed Ezward closed 4 years ago
@Ezward hello, I tried D435i with the same FW and kernel versions as specified but could not reproduce any of the above in realsense-viewer
/ rs-capture
/ rs-measure
.
Can you turn on and provide the SDK and kernel logs for review ?
Additionally I'd recommend to try a different USB cable/port as some of the warnings are associated with power/hw setup.
It was the cable. I was using a 3rd party cable when getting the errors. When I switch to the supplied cable, everything worked. Thank you.
Issue Description
I updated SDK, then updated firmware. Now when I run realsense viewer, if I use rgb and depth everything is fine (although missng 848x480 resolution, which I used to have), but if I turn on Motion Module, realsense-view crashes. Restarting and it will crash as well, indicating camera is in a bad state. Hardware reset from realsense-view did not work. Uplugging camera, quitting realsense-viewer, plug back in camera and restart realsense-viewer and I'm back to where I can use RGB and Depth.
If I only use the Motion Module, it seems to work fine (which is an improvement over prior versions, where it did not seem to return correct values). However, once I turn on RGB camera, I get error message. Here is what console looks like;
Those first six lines show up if I just start realsense-viewer and never even try to turn on a sensor.
Here is what happens run I run some python examples from librealsense:
Frame didn't arrived within 5000
If you unplug and plugin the camera again, then align-depth2color.py will start working again. So whatever the issue is, it puts the camera into an unstable state.
Is there a way to revert; what I had before worked well. At this point, the camera is useless to me because I need all 3 streams.