1 Reply Latest reply on May 17, 2017 9:29 AM by MartyG

    get SR300 serial through SDK with driver



      I'm working with two SR300 and SDK on Windows 10.

      Windows 10 Professional  version 1703  OS version : 15063.296


      The SDK worked well with previous driver version.

      The Device Manager showed :

      - Virtual Driver : driver date 08/06/2016  version

      - RGB : driver date 21/06/2006 version 10.0.15063.0

      - Depth : driver date 22/09/2016 version

      I modified the CameraViewer sample from SDK, and insert the code to enumerate the devices, as shown in the SDK documentation.

      The modified software displayed the streams Depth and Color in two Windows, and found two devices.

      I could display fields of DeviceInfo structure  :

      - the serial number of the device

      - the streams supported :  COLOR, DEPTH and IR

      - firmware :


      Now, a new driver has been installed.

      The Device Manager show :

      - Intel(R) RealSense(TM) Camera SR300 Color , driver date 08/05/2017  version

      - Intel(R) RealSense(TM) Camera SR300 Depth, driver date 08/05/2017  version

      The modified Viewer displays the streams Depth and Color in two windows and finds :

      > two devices in the first module :

      - device[0] name :<Peripherique video USB>   serial <>  streams <COLOR>

      - device [1] name: <Intel(R) RealSense(TM) Camera SR300 Depth>  serial <> streams <COLOR>

      - in the fields of DeviceInfo  structure :

      > a device in another module :

      - device[0] name: <Intel(R) RealSense(TM) Camera module (SR300)>  serial<> streams <COLOR, DEPTH and IR>


      I have seen a previous topic related to the incompatibility between Windows 10 build 15063 and RealSense SR300.

      Is it the reason of the different behavior of the software ?

      Since Virtual Driver is missing in Device Manager, does it explain these results ?