-
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
Not working L500 Depth Sensor #8723
Comments
This is output console
|
|
Hi @webant-ltd. I am having exactly the same problem - same errors are being shown in RealSense Viewer and when launching ROS Node. Funny thing is that it actually worked last week just normally. Can you confirm that as well or your sensor never worked as supposed? Thanks. |
@taletovic I have the exact same thing, my camera worked last week. I have been having success with it. |
@theotromp97 I was using different presets (close range was interesting for me) as well as trying to save the settings in a .json file which could be later on loaded in the ROS driver. Maybe that could cause this problem, however I've no solution to it. About the USB Port - it's a known phenomena (saw it in troubleshooting guide). @RealSenseCustomerSupport any answer/comment on this? Please help. |
Did anyone figure out a solution to this? The device was working fine last week but now I'm getting the exact same errors as @webant-ltd when trying to turn on the depth sensor. The motion module and rgb camera are working fine though. I've even tested it out on a different computer but the problem persists. |
Hi All If you're having issues with the streaming of the depth in the manner outlined above or even having issues with the USBC connection orientation changing behavior with regards to detected as USB2 or USB3, please open a ticket here: https://support.intelrealsense.com/hc/en-us/requests/new |
I'm using the USB cable that came with the L515.
Run
realsense-viewer
After launching, I get an error
RGD Camera and Motion Module work stably.
I tried updating the firmware version to 1.5.5.0 (Signed_Image_UVC_1_5_5_0.bin). The error remains.
The text was updated successfully, but these errors were encountered: