L515 Depth Sensor Flickering after upgrading from 1.4.1.0 to 1.5.8.1 #9505
Comments
|
Hi @olivetom I was not able to recreate the flickering with your L515. The frame numbers seem to be incrementing normally without pause during streaming and do not reset. The visual effect resembles the rendering of the graphics being frequently activated and deactivated, as demonstrated by the disappearing and reappearing of the depth scale at the edge of the depth image. Given that the problem did not previously occur in firmware version 1.4.1.0, would it be possible please to downgrade your firmware to one version older than 1.5.8.1 - 1.5.5.0 - to see whether the graphical disruption still occurs? https://dev.intelrealsense.com/docs/firmware-releases-l500#section-l500-series-firmware-downloads |
|
@MartyG-RealSense thank you for the advice. |
|
I would recommend not performing repeated downgrades, as there is a limit of 20 downgrade attempts before you can no longer downgrade and only upgrade to a newer version from that point onwards.
|
|
My research located a previous case of flickering on the L515, though the problem was only reported for the depth stream in that particular case. The RealSense user found that the problem did not occur if they used the camera with their own private computer. Could you open the debug log in the RealSense Viewer please by left-clicking on the upward triangle icon at the bottom corner of the Viewer and post an image of the messages generated in the log when the flickering is occurring.
|
I know about the limit but I couldn't downgrade directly to 1.4.1.0. Would you @MartyG-RealSense tell me how to do it please? |
I have only problems with depth sensor. I've attached a capture of the realsense-viewer log for further reference.
|
|
I do not know of a reason why the original firmware 1.4.1.0 would have a problem with being installed. If you obtained that firmware from this link: https://dev.intelrealsense.com/docs/firmware-releases-l500#section-l500-series-firmware-downloads Then you could try downloading the file from this location instead: https://downloadcenter.intel.com/download/29635/Firmware-for-Intel-RealSense-L500-Product-Family The log entry about the warning receiver light saturation, stream stopped for 1 sec was very helpful, as it enabled me to find a couple of other occurrences of this error, including the one in the link below where the effect is described as 'pulsing' like in your video. IntelRealSense/realsense-ros#1750 Could you test whether it still occurs if you select the Short Range preset in the Viewer please, as that setting would configure the camera to use lower Receiver Gain and Laser Power values. |
|
Short range also throws the same flickering. This is the error message realsense-viewer throws when trying to downgrade to 1.4.1.0 Perhaps the most effective way of closing this issue is to give me instructions on how to downgrade successfully to 1.4.1.0. |
|
I will seek advice from Intel about your case. Thanks very much for your patience! |
|
@MartyG-RealSense any news about this case? Thank you. |
|
I do not have advice about this case yet. I will follow up with Intel about it. |
|
Hi @olivetom Intel have requested that you return your L515 camera to the place that you purchased it from, using the RMA (return merchandise authorization) returns process of that supplier. Could you also provide the serial number of your camera to me, please? This information can be found by using the Info option at the top of the RealSense Viewer's options side-panel to display the camera's information. |
|
Hi @MartyG-RealSense returning the camera is not possible because I need it for my daily work. Can I reset to factory somehow? |
|
A recommendation to RMA return usually means that it is believed that the problem that has been reported cannot be corrected by the user, such as a malfunction with that camera unit's internal hardware. A simple test that you can perform with L515 is to unplug the USB cable from the base of the camera, turn it around the opposite direction and re-insert it (USB-C cables are two-way insertion on the micro-sized end). If that test, or trying the camera on a different computer if you have access to one, does not work then returning the camera to the place that it was purchased from at the first opportunity to do so if it is still possible to use the camera for your work until then would be the recommendation. |
|
Hi @olivetom Do you have an update about this case that you can provide, please? Thanks! |
|
Case closed due to no further comments received. |
|
Hi, I have exactly the same problem. Did someone found a solution? |
|
Hi, the solution was to return the camera using the RMA.
I still trying to do the “golden reset” as a last resort solution before throwing it to garbage.
Mauricio
… On Jan 12, 2022, at 10:09 AM, Giggus ***@***.***> wrote:
Hi,
I have exactly the same problem. Did someone found a solution?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.
|
|
Hi @olivetom As far as I am aware, L515 cameras do not have the feature of resetting to factory defaults with a 'gold reset' like the 400 Series models can. |
|
@MartyG-RealSense So if I get this error constantly it means that the camera is broken? |
|
Thanks for the comment Marty
It was my last option as I can’t detect the camera neither on windows nor linux.
So now I’m pretty sure that I should dispose the camera. 😔
Mauricio
… On Jan 12, 2022, at 12:10 PM, MartyG-RealSense ***@***.***> wrote:
Hi @olivetom As far as I am aware, L515 cameras do not have the feature of resetting to factory defaults with a 'gold reset' like the 400 Series models can.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.
|
|
@Giggus Did your problem begin after upgrading the firmware like happened with @olivetom ? @olivetom Did the camera become undetectable after putting it in a cool dry place such as a cupboard or drawer for a period of weeks / months and it no longer was detectable after the first time that it was taken out of storage and used again? |
|
@MartyG-RealSense I didn't explicitly done the update on the realsense-viewer. If it happened it was on the background with the ubuntu update I did this morning. The version of the firmware is the same as @olivetom |
|
@Giggus The firmware would not be updated on its own. It is possible for an update to be casually performed without really thinking about it if an update prompt appears when the Viewer is launched and the button to agree to the update is clicked. Have you tried downgrading the firmware to an earlier version yet? |
|
I didn't update it for sure then. |
|
It is worth trying a downgrade anyway just to confirm whether or not it makes a difference, as what doesn't work for one person might work for another. You can downgrade using the steps below.
https://dev.intelrealsense.com/docs/firmware-releases-l500#section-l500-series-firmware-downloads
|
|
@MartyG-RealSense This morning I tried the camera (nothing changed) and the "receiver light saturation, stream stopped for 1 sec" error didn't appear (yet). |
|
@Giggus If a firmware downgrade did not correct the problem and reversing the orientation of the micro-sized end of the USB cable did not correct it either then you can try disabling the GLSL options in the RealSense Viewer settings interface to see whether that makes a positive difference. #8110 (comment) has instructions for doing this. |
|
I spoke too early and quickly... Got the problem still.. Please look at the video below. simplescreenrecorder-2022-01-13_11.37.24.mp4 |
|
@Giggus This is the same problem that @olivetom had and also another RealSense user in IntelRealSense/realsense-ros#1750 In both cases the recommendation was to return the camera to the retailer that it was purchased from. |
|
@MartyG-RealSense I tried the firmware downgrade, the cable switch and orientation and the GLSL, Nothing. I'll return the camera... Thanks! |
|
Okay, thanks very much @Giggus for the update. Good luck! |
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
Depth Sensor Flickering as in this video: https://drive.google.com/file/d/1XHQWwsWxtELUO2yREpqfNBMou3DoEvhK
The text was updated successfully, but these errors were encountered: