RealSense SR300 bricked by older DCM Version.
Greetings!
Unsure where to start to further diagnose the issue. I've been using a Realsense SR300 flawlessly for over a year now under Windows 10. However, I came across some new software which exhibited issues with support and detection. Up until this point other software including the Realsense Viewer had no issue with the RealSense. After attempting some resolutions to no avail I came across a few "fixes for the software" involving using an older version of the DCM... Version "3.0.24.59748".
This is unfortunately where the issues began. It requested I "update the firmware" to continue so I did.. regrettably... as I could not continue otherwise. During the firmware update the Realsense disconnected and reconnected only to now report that the "The hub does not have enough power to support the USB Composite Device". As a result the firmware update then reported a failure. The "hub" reporting this issue is the internal "Generic SuperSpeed USB hub" appearing upon connecting the camera and the "USB Composite Device" is the device entry for enabling the camera functions. The audio functions of the camera are detected fine and functional. Disabling the "USB Composite Device" prevents the power issue from being reported but no camera functions are available aside from the audio.
I have tested the camera on 4 different production machines in all ports with the same result. I even tried a few externally powered hubs from mains power [one with support of 2A output] to the same issue. I am also using the originally included 1metre cable and have tested with another that was on hand.
running "rs-fw-update -l" results in the response "There are no connected devices".
-
Hi Chozo I located a newer 3.4.104.3435 version of the SR300 DCM installer that you could try. The Google Drive link below that I have created will allow you to download it to your computer.
https://drive.google.com/file/d/1TyDmO-CdqqrM6in1PnbxJACoZVpB4R3x/view?usp=drive_link
If that installer does not resolve the problem, there is an old method for forcing a firmware update without having to run the DCM program, so long as the DCM has been installed on the computer.
https://support.intelrealsense.com/hc/en-us/community/posts/360037842634/comments/360009745714
-
I have tried the newer DCM as well [3.4.104.3435] to only find it cannot be installed due to 'no realsense device detected'. It is the one I was using previously before trying the older version for debugging purposes and this incident occurring. I underwent the firmware force flash but the paths were different in the newer DCM.
Using "FWUpdateSR300.exe -force -confirmed -y .\SignedFirmwareImage\SignedFirmwareImage_1_5.bin" ended with the result "FW update return code: -1". The newer DCM does not have an ihex file to use.
Attempting to access the camera using the RealSense Viewer results in the notice to "Please Connect a Realsense Device!" -
The SR300 model had USB power issues for some RealSense users, where the camera disconnected or could not be detected because the port was supplying insufficient power to the camera to meet its requirements.
If using a mains electricity powered USB hub did not make a difference, another workaround I found was to attach a switched-off USB chargeable device such as a phone or tablet to the computer that initiated charging of the device through the USB cable if the device's charge was at less than 100%.
Once the computer's USB system started sending power to the USB port to charge the device, connecting an SR300 to another USB port afterwards sometimes enabled the SR300 to be detected so long as the charging device was at less than 100% (the camera connection would cut off once the charge was 100%). This method did not always work but may be worth a try if you already have a phone or tablet that you can test with.
-
I have tried that as well to no joy with my phone at 43%. It is the cameras own internal "Generic SuperSpeed USB Hub" reporting insufficient power not the PC or externally powered hub that it is connected to. It's as if the firmware caused the camera itself to report a higher power requirement that itself cannot provide through its' own internal hub. This is a screenshot of the device manager:
The audio portion [connected over its' Internal "Generic USB Hub"] functions normally. Once the sensors come online to the internal Superspeed hub it reports insufficient power [as noted by the yellow marker over the "USB Composite Device"] from the Superspeed "hub". The other "USB Composite Device" that works is the bridge for the audio functionality. Neither the RGB nor Depth sensor are detected at this point.
-
It looks as though the SR300's three drivers (Depth, RGB and Virtual) are absent from the Imaging Devices category of the Device Manager where they would usually be. The image below shows what the Imaging Devices section should look like when the drivers are installed.
It is unusual that your SR300 drivers are absent, as the SR300 can automatically download and install the drivers from the internet if the drivers are not currently installed when the camera is inserted into the USB port (it does not update the firmware driver though - the DCM program is usually required in order to do that). Has the computer that you are using the SR300 with got an active internet connection, please?
On some computers the SR300 drivers are divided between the Imaging Devices section and the Cameras section. Your Device Manager does not have a Cameras section, though it might if the SR300 drivers were installed.
-
Yes, this machine has internet and the DCM/drivers as well as the SDK. They were previously installed on this very machine and are still installed. The cameras section does not show because the cameras since the firmware update are no longer detectable. This is the same result on multiple machines. It worked fine until the firmware update from the older DCM package caused this on the development machine.
-
For report comparison, this is the same issue occurring on another internet connected unit which too has the DCM+SDK installed and has previously used a working SR300. This too shows the same issue with this SR300 in particular. It will not show a cameras sections because this is currently the only connected camera of which its camera functions isn't being detected due to the "USB Composite Device" bridge failing to function.
-
A RealSense team member at the link below offers advice about reinstalling the USB Composite Deivce.
-
Unfortunately that doesn't work either. The driver was reinstalled and it still has the same issue. There was no crashing involved in any form. This is occurring on several different systems with this exact camera. No other realsense units are experiencing this aside from this particular one that was bricked.
-
The rs-fw-update tool is not compatible with the SR300 camera model.
Another RealSense user who had a similar problem to yours found that they were able to get their bricked SR300 detected in version 2.26.0 of the RealSense Viewer and then restore it by using the Install Recommended Firmware option in that old Viewer.
https://github.com/IntelRealSense/librealsense/issues/4435#issuecomment-525617614
The 2.26.0 Viewer can be installed on its own as a standalone program by visiting the link below and downloading and running the file Intel.RealSense.Viewer.exe from the 'Assets' file list at the bottom of the page.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.26.0
As you are using an SR300, it should not matter that the Viewer is a very old version.
-
If the method in the link below does not work then realistically I believe that there are no further options for restoring the camera after everything that you have already tried, unfortunately.
https://support.intelrealsense.com/hc/en-us/community/posts/360052144833/comments/7147407891603
Please sign in to leave a comment.
Comments
13 comments