View my account

SR300 detected but not working from Intel tools

Comments

10 comments

  • MartyG

    The symptoms are typical of a power instability on the USB port, meaning that the camera can be detected but disconnects when streaming activates as the camera increases its power demands from the USB port.  If trying the camera in a different USB port does not work (if you have another port), plugging the camera into a mains powered USB 3 hub instead of directly into the PC may help.

    A way to test whether a USB power instability is the cause of your problem is to put a chargable device such as a smartphone or tablet on charge on the USB 2 port via a charging cable, and then insert the camera in the USB 3 port.  Sometimes the camera will then work whilst the device is on charge, due to the PC providing the USB system with extra power for the charging.

    0
    Comment actions Permalink
  • T Batal

    Using a chargeable device is an interesting tip, I didn't know that ; unfortunately it didn't work in my case...
    My main powered USB3 hub didn't change anything neither, but maybe mine is declining, I have to find another one to test.

    I noticed a possible cause of the problem in my Windows Devices manager, where I get :

    Instead of (according to https://mtaulty.com/2016/04/30/windows-10-uwp-intel-realsense-sr300-first-steps/) :

     

    To set up the cam, I first plugged it (otherwise DCM does not run), then installed DCM then the SDK and the viewer.

    Did I miss a driver ?

    Thanks.

     

     

    0
    Comment actions Permalink
  • MartyG

    Sometimes the RGB driver is placed by the computer in the 'Camera' section of the Device Manager instead of in Imaging Devices with the other drivers.  So there can be differences in the driver locations between one PC and another, so that in itself is not something to be concerned about.  Can you check your Camera section to see if the RGB driver is under that, please?

    Since you do not have a missing Virtual Driver and have already tried a powered USB hub, my next suggestion would be to see if the Windows Troubleshoot tool can fix your problem.  Details for using this tool are in a comment at the link below.

    https://forums.intel.com/s/question/0D70P000006JugoSAC/i-have-a-intel-sr300-but-i-cannot-install-the-realsense-camera-sr300-virtual-driver

    0
    Comment actions Permalink
  • T Batal

    Great thanks, I'll be able to try on monday

    0
    Comment actions Permalink
  • T Batal

    Hi Marty,

    You were right, the RGB driver is under the Camera section.

    I tried the Troubleshooter, but mine is missing like with this guy : https://answers.microsoft.com/en-us/windows/forum/all/troubleshoot-hardware-and-devices/72f2c6cd-9755-4537-aa4e-85371d68ca93?page=1

    I'm investigating on how to solve this troubleshooter problem ; I'm also investigating to update Windows (Windows insider program), but I'm currently out of space -> I have to wait for my new SSD to be delivered.

    0
    Comment actions Permalink
  • MartyG

    There is an indirect way to get to the Troubleshoot from the Control Panel's front page in Windows 10.

    STEP ONE

    Open the 'System and Security' section

    STEP TWO

    Under the 'Security and Maintenance' option, there is a sub-link called 'Troubleshoot common computer problems'

    STEP THREE

    Clicking on this link opens the 'Settings' window, which has a 'Troubleshoot' option in its list.

    STEP FOUR

    When the 'Troubleshoot' option is highlighted, scroll down the list of options on the right-hand side and left-click on 'Hardware and Devices', then the 'Run the Troubleshooter' button that appears.

    STEP FIVE

    Windows then does a general scan for any devices in your Device Manager that may have problems and tries to auto-fix them.

    0
    Comment actions Permalink
  • T Batal

    Yes, but the "Hardware and devices" item does not exist in my OS :

     

    I received my new USB 3 hub ; it is powered with a usb-c port and connected to the barebone with a thunderbolt 3. The SR300 is the only device plugged to the hub.

    As shown below, with this configuration the rgb stream works (1) ! But the coded light depth sensor does not work... Either I check the depth stream, the infrared 1 stream or both of them, when I play it makes a window trying to open (2), the camera to disconnect then the Viewer to close...

    (1)


    (2)

     

    In the SDK Viewer Information, I noticed that both the 32 and 64-bits modules are set up for the SR300 ; is it normal? Sometimes having both architectures of a library provoke conflicts

    0
    Comment actions Permalink
  • T Batal

    Yeaaaaaah

    I solved the problem : it was because of the wire that you provide with the camera ; I just used another one (from a USB3.0 mobile screen) and everything ran fine, even without using the usb 3.0 hub !

    Thanks Marty :)

    Have a good day,

    Thibaut

    0
    Comment actions Permalink
  • MartyG

    Apparently Microsoft recently removed the 'Hardware and Devices' option from the Troubleshoot because they didn't think that people wanted to use it.  Which caused many people problems because specific Troubleshoot options do not exist for the kind of hardware problem that they have.

    https://answers.microsoft.com/en-us/windows/forum/all/why-is-there-no-troubleshoot-hardware-devices-in/c78af528-4b0c-47b6-89dc-4292bc1b80bb

    I ran extensive tests with the RealSense Viewer with my SR300, which also suffers from disconnections.  A workaround I found was to go into the 'Controls' options and decrease the Laser Power slider to '0' (instead of its default of '16'), and then start the streams.  With this method, I was able to consistently stream both depth and IR at the same time.

    During streaming, if the slider is increased then the camera disconnects.  This would seem to suggest that there is a certain threshold of camera power draw beyond which the camera can cut out if the camera is not being supplied with enough power.

    0
    Comment actions Permalink
  • MartyG

    I'm very glad you were able to find a solution for your problem by changing the cable.  :)

    0
    Comment actions Permalink

Please sign in to leave a comment.