Could you check please whether your Windows 10 has updated to Build 15063 (also known as the Creators Update). The SR300 has been having problems with this Windows version, and Intel and Microsoft are currently working on a fix for it.
You can find out your Windows version by typing 'system info' into the text box at the bottom of your Windows screen (the box next to the button where you shut down the PC). Please select the System Information application, and see what the 'Version' section of it says.
The problem took place after the windows update. So yes it's build 15063 and the problem is with the old dcm firmware update which failed and resulted in not working usb device.
Regarding your question about resetting the firmware: if you have had a working installation on the DCM prior to the error then you should have a file on your computer that tries to reinstall the firmware only (not the RGB, Depth and Virtual drivers) when it is run.
This post describes how to locate the SR300 firmware updater on your PC if you wish to try it.
Thank you for your help.
I've found the directory and the FWUpdateSR300.exe inside it. But it wants some arguments (I think at least a camera device id) because gives me return code -1.
Here is this program help.
How can I get the correct DeviceID?
This is the first time I have seen these codes associated with the FWUpdate file, except for the 'force' one (which forces the firmware to update).
I would try using a couple of the codes in the Windows command line interface. First, to check that the camera is connected:
And then if it is connected, see if the firmware update can be forced.
The command line can be accessed by typing 'command' into the same box at the bottom of the Windows screen.
It says "Camera not connected" (but it physically is via usb) and does not want to do any command (also -force since camera is not connected)
Is the camera and its drivers listed in the Device Manager?
If it is plugged in and shown in the Device Manager but you are being told it is disconnected, this could be related to the Build 15063 of Windows and the ongoing issues for RealSense cameras caused by it.
Power fluctuations in the USB ports are another cause for non-detection, which can be fixed by plugging the camera into a mains-powered USB hub instead of plugging it directly into the PC. I have seen cases before where a camera worked fine for a while until a Windows update took place and then it suddenly couldn't be detected.
It was listed before the last dcm installation, but now it's just an unrecognized usb device.
I tried the powered USB 3.0 hub (via the monitor) and it didn't help.
I have seen cases before where a camera worked fine for a while until a Windows update took place and then it suddenly couldn't be detected.
This is exactly how it happened, but after that I decided to try older dcm and "bricked" the camera.
Your camera does sound bricked if it is now an unrecognized device, sadly. If it has been less than 90 days since you purchased it, you can return it to Intel.