Intel Realsense D4XX USB2 Recovery Connected #10499
Comments
|
Hi @xin-Dream Your rs-fw-update log's message that update progress is at 100% suggests to me that firmware update completed successfully and it failed to detect the camera when trying to restart it afterwards. If the camera is still listed as Recovery in the RealSense Viewer after the firmware update, please first try a complete uninstall of the RealSense camera drivers in the Windows Device Manager using the instructions at the link below. https://support.intelrealsense.com/hc/en-us/community/posts/4419989666323/comments/4431239847443 If you do not have RealSense Depth and RGB drivers listed under the 'Cameras' category of the Device Manager then please try uninstalling 'Intel RealSense (TM) RS400 Device' instead using the uninstall method in the instructions. |
|
Hi @xin-Dream Do you require further assistance with this case, please? Thanks! |
|
Case closed due to no further comments received. |
|
HI @MartyG-RealSense , I have Realsense D420, I have the issue mentioned above.I tried solutions mentioned here too. Doesn't seem to be working for me. |
|
Hi @anujpatel1608 The message Firmware update progress: 100% ... firmware update done suggest that the firmware update process completed successfully and the camera is just not being detected when being re-initialized after the update has completed. Is the camera able to be detected successfully in the RealSense Viewer tool, please? If it is, what is the name of the camera that is shown at the top of the Viewer's options side-panel? |
|
Actually, I get 98% ,the viewer says it will disconnect & try to connect again. The notification on the right pops up saying it got disconnected and another notification pops up a sec later indicating realsense did connect again(in recovery). In the viewers panel I get 'Intel Realsense D4XX Recovery' |
|
Is it ok for serial no. ,firmware no. & usb type to be unknown? |
|
Using rs-fw-update tool I got 100% but in the viewer i get 98%.After this showing 100% I did check it still went into recovery. Also if firmware update is done,why doesn't realsense connect again? |
|
Serial number, firmware and USB type showing as unknown would not be a good sign. If the update gets to 100% in rs-fw-update and shows in the RealSense Viewer's options side-panel as being in Recovery mode, this is better than the camera not being detected by the Viewer at all. May I ask whether you are performing the update using the official 1 meter USB cable supplied with the camera or a longer cable of your own choice? If you are using your own cable then I would recommend trying the update with the official short cable. When the firmware update is completed, the camera is automatically reset but may sometimes fail to be detected on the restart. In tis situation, an unplug and re-insert of the camera may enable detection. |
|
I have realsense l515 i'm using cable that I got with that...its a 1m USB-c to USB3.0 Cable. I correctly plugged to USB3.0 port too. |
|
what about those serial no.,etc being unknown? How does this happen? and how much chances do you think i have of getting this realsense up and running? |
|
If you have a D420 caseless camera board and a Vision Processor D4 Board joined together by an 'interposer' rigid board or flexible cable, the recent case at the link below of a firmware update gone bad may be helpful. |
|
yes, i'm using the configuration you mentioned. So the solution on that link suggests that I should disconnect interposer from vision processor board and then perform firmware upgrade by just connecting vision processor board to pc, is that right? |
|
It sounds as though they disconnected the camera depth module board from the interposer and performed the firmware update on the D4 board that the USB cable attaches to. |
|
Tried that, disconnected camera module from vision board and then connected to pc. When only vision board is connected everything works fine. I click on check for updates and it says all sw up to date and i'm out of recovery too. As soon as i unplug and attach camera module back to Vision Board I again get into recovery mode. Also one error i receive when connecting without camera module(the image i attached) Also I have a question regarding l515 which we've been using for last 8 months in indoor conditions, the l515 is very sensitive to indoor lightings as well as sunlight from windows. There is lot of noise and this noise gets detected as obstacle and the robot stops completely. I checked and there is a 'ambience' preset ,but I want to use that preset in ros,so how do i do that? Also is there any other solution for this lighting condition problem? |
|
I'm also getting, ERROR: UNKNOWN in rs2_update_firmware_cpp(device:000001B1ADD2C6C0, fw_image:000001B1AE6C1060): |
|
Once the depth module is reconnected, are you able to reset the camera to its default factory-new calibration settings in the 'More' setting at the top of the Viewer's options side-panel using the instructions at #10182 (comment) The L515 model works best indoors in controlled lighting and without the presence of infrared light sources or sunlight. The L515 can handle the presence of some sunlight though when the Low Ambient Light preset is used. In ROS you can set presets at launch by loading a json camera configuration file. You can create a json that represents the Low Ambient Light settings by going to the RealSense Viewer, setting the Low Ambient Light preset from the drop-down list of presets and then clicking the json save option to save the configuration to a json.
You can then load the json in the roslaunch instruction. For example:
Alternatively, you can do so within the launch file using the json_file_path parameter to set the location where the ROS wrapper can find the preset. A third approach that is available in ROS1 would be to set the L515 preset in the dynamic reconfigure settings interface panel after launch has completed. The dynamic reconfigure interface can be opened by inputting this command into the ROS terminal: rosrun rqt_reconfigure rqt_reconfigure
RealSense devices have a limit of 20 firmware downgrades. This mechanism has been used since the original RealSense camera models in 2014. After 20 firmware downgrades have been performed, the camera locks downgrades and from that point onwards only allows the installation of a newer firmware version than the currently installed one. This lock is permanent for the lifetime of that particular camera. Although there is not an official reason for the lock, my understanding is that it is to prevent multiple changes to the camera by malicious updates such as 'malware'. |
|
|
|
In order for the Write Table option to be usable, you need to first enable the Stereo Module by left-clicking on the red icon to turn it to blue (On) before opening the Camera Calibration window.
|
|
I get this when I try to enable Stereo Module |
|
Please click the 'i' information button in the Viewer's options side-panel to display information about the camera and post a picture of it in a comment here please. |
|
|
|
Thank you very much for the image. I requested it in order to check the camera's serial number because in previous cases of this invalid value in rs2_open_multiple error at #7337 and #10093 the camera serial number was incorrectly displayed as 'ffffffffffff'. The image shows that your camera has the same issue. The RealSense user in #7337 eventually concluded at #7337 (comment) that their particular problem was caused by the USB cable having been bent at an angle. Is this a possibility for your own situation, please? |
|
I think yes, but now I tried with a different usb3 cable which is perfect but error persists. |
|
The serial number fffffffff and the inability to enable the Stereo Module in the Intel RealSense D400 image above are likely due to the D420 being disconnected from the interposer, as the D420 is the Depth Module that contains the depth sensor hardware. The RealSense firmware driver decides what name will be displayed for the camera based on the sensors that it is able to detect. So if the D420 board is disconnected when the Viewer is launched and only attached after Viewer launch has completed then it may not know how to access the depth stream when it is enabled. If you go to the More option at the top of the options side-panel after connecting the D420 to the interposer after the Viewer has launched, do you have the menu option Hardware Reset please? This resets the camera without having to unplug the USB cable.
|
|
I clicked on Hardware Reset and landed in Recovery Mode. And now same error of realsense locked for update comes up |
|
If you are updating the firmware in rs-fw-update, can you confirm please whether you have used the '-r' flag to try to recover a camera that is in Recovery mode? For example when using the downloaded formware bin file 'Signed_Image_UVC_5_13_0_50.bin': rs-fw-update -r -f Signed_Image_UVC_5_13_0_50.bin |
|
I did, check this image #10499 (comment) . |
|
Thanks very much, @anujpatel1608 -I look forward to your next update. Good luck! |
|
Now I'm getting this |
|
Could you confirm which version of the Vision Processor D4 Board you are using, please? There are currently 4 versions from V1 to V4, but only the original D4 V1 board is compatible with the D420 depth module. This is because V2 is for the D430 module to give it IMU capability, V3 is for the D450 module and V4 is for the D401 module. |
|
I brought it from mouser. Here is the link to the one I brought -https://www.mouser.in/ProductDetail/Intel/82635DSASMDLPRQ?qs=wd5RIQLrsJhT7QD5H29iow%3D%3D . Could you please check version I have, as I couldn't find on that page. |
|
The Mouser product code is for the original V1 board, so that does not appear to be the problem. I will discuss your situation with my RealSense colleagues. Thanks again for your patience! |
|
Do you have a Non Disclosure Agreement (NDA) with Intel, please? If so then you can submit a support ticket on Intel's Zendesk support system. |
|
we dont' have NDA. But if we buy from 3rd party sites like mouser(depth module & interposer) & evelta(we brought camera module from evelta.com which is based in India) why would we need to sign an NDA / How do we sign an NDA with the product manufacturer Intel? How do we raise a support ticket urgently as it is causing delay to our deployment? |
|
I will discuss your case further with my Intel RealSense colleagues later today in regard to what you can do if you do not have an NDA. |
|
OK,Great, Thank you! |
|
Could you provide an email address to contact you at, please? |
|
@anujpatel1608 Thanks very much, I have passed your email address to my colleagues. |
|
Thanks for the support! |
|
Hi @MartyG-RealSense ,We haven't received any communication yet. |
|
Thanks very much @anujpatel1608 for the update. I have contacted my Intel RealSense colleagues to follow up on your case. |
|
Hi again @anujpatel1608 I have been advised that you have signed an NDA agreement. Please submit a ticket about your issue on the Zendesk support channel. Thanks again! |
Question：
I have a D455 camera that when opened with the Realsense Viewer reads:
notifications. CPP :511 - Intel Realsense D4XX USB2 Recovery Connected, as shown belowI tried to upgrade in the Realsense Viewer, but the connection timed out after the upgrade，as shown below
And then I looked at the other answers,Intel ResalSense D4xx Recovery #4744，So I tried using rs-fw-update.exe to upgraded firmware,but it did not work . It says timeout
I looked in device Manager and it showed RS400 in device Manager.
So could you tell what could I do to solve it?
The text was updated successfully, but these errors were encountered: