Getting "Init failed"? Here's how to restart the Depth Camera Manager

[Robert_Oschler]

If you have installed the Intel Depth Camera Manager version 1.3 and you are using the external F200 USB 3.0 camera, be aware that detaching and re-attaching the camera can cause the DCM to become unresponsive.  Note, this will still happen even if you use the USB detach device utility from your system tray panel on your taskbar, to "properly" detach the device.  If the DCM becomes unresponsive, you have two choices to bring it back to life:

- reboot  your ystem

- (faster) Use the Windows 8.1 control panel applet and look for the "Local Services" applet.  Run that applet and it will show you a list of the services running on your PC.  In that list, look for the service named Intel Depth Camera Manager.  You may need to widen the service name column to see the full name since it may be truncated in the default view.  Once you find it right-click on it and choose Restart from the context menu.  That will restart the DCM service and bring it back to life.  Otherwise you will get "Init failed" errors.

I keep a shortcut on my Desktop to the Local Services control panel applet.  If this doesn't work for you, then you have a different problem such as:

• Flaky USB 3.0 port
• Your F200 USB cable not fully pushed in to the USB port (happened to me)
• Something else and harder to fix.

[Stephen_M_5]

Robert.  Thank you for re-iterating this.  I had read this in the release notes for the SDK, but being generally unfamiliar with Windows it didn't register.

I can reliably reproduce this error with the Capture Viewer from the SDK if I

1. Run the capture viewer and play around with the F200

2. Close the program, unplug that camera, and connect the R200

3. Run the capture viewer again

or the reverse order.  The Capture Viewer program thinks that the previously disconnected camera is still there (e.g. in the routine above, even though the R200 is connected, the streams for the F200 are present -- execution of which will ultimately crash the program after much blinking).

- - - - - - -

Strangely enough, I have to restart these services even after a fresh boot.  So again...THANK YOU for making it very clear how to restart the service!!!

- - - - - - -

As a side-note, this process can be automated a bit further.

Step 1 is to create a  bat script (e.g. mine is named reset_real_sense.bat).  The contents should be

:: The following script 'restarts' the relevant Depth Camera Manager(s) (DCM)
:: for the Intel RealSense _F_200 and _R_200.

:: Stop the RealSense DCM Services
net stop RealSenseDCM
net stop RealSenseDCMR200

:: Start the RealSense DCM Services
net start RealSenseDCM
net start RealSenseDCMR200

:: I like to see what was / was not executed;
:: change the number of seconds or delete all
:: of this if you don't care
@echo off
echo Finished restarting the relevant services,
echo counting down until exit so you can read
echo what was completed.
echo vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
echo E.g. if you do not have admin access, then
echo this script did not do anything...
Timeout 11

Notes:

(a) Starting / stopping a service with 'net' won't do anything if you don't have the service installed, but you should just delete the irrelevant lines for you (the user).  E.g. if you only have an _F_200, delete the lines pertaining to 'RealSenseDCMR200'.

(b) The echo / Timeout at the bottom is not necessary.  I just don't like that bat scripts close immediately, and like to see what happened ;)

(c) I'm sure there is a better way to do this...please chime in if you have a better way!

Step 2 is to create a shortcut to this .bat file.  Now right-click the shortcut and click on properties.  In the Shortcut tab (default tab), click on the "Advanced..." button and check "Run as Administrator".  Services cannot be started / stopped by a regular user ;)

I hope that helps somebody!

[Robert_Oschler]

Hi Stephen,

What are you doing with the R200?  I'm going to get one as soon as their back in stock.  Right now orders have been suspended.  I love my F200 and I was wondering what you can do with the R200 that you can't do with the F200?

[Stephen_M_5]

Hi Robert,

To be honest we're just starting out with these cameras, so I don't really understand the big differences between the two (other than that they are very different in style / hardware e.g. stereo cameras)...

At this point it seems like the F200 will be the primary focus (for now!) since it has much better resolution close up.  Once we get things going close up, who knows!  The R200 definitely has great resolution at farther distances, though!

[Robert_Oschler]

Hi Stephen,

Apparently one key advantage of the R200 is that it can measure distance.  The F200 can't according to Colleen.

[Colleen_C_Intel]

OK - I shouldn't say can't. I should say Intel SDK isn't pursuing that particular use case for F200, only R200. I've found independent developers do lots of amazing things so quite possibly could - but remember the range limitation around 1 meter - so not a whole lot to measure :>}

[Mona_J_1]

So I used the .bat script as an administrator but still my camera gives me init_failed when I am running the sdk samples. Problem is I want to use this camera in a time critical application and I can't reinstall the DCM and SDK every once in a while or say restart the system which none helps as of now.

Is there any recent update to this problem? I wonder if Intel developers have thought of a solution by now as there's been frequent entries just very recently telling they can't get their realsense init!!

Bests,

Mona Jalal

Stephen M. wrote:

Robert.  Thank you for re-iterating this.  I had read this in the release notes for the SDK, but being generally unfamiliar with Windows it didn't register.

I can reliably reproduce this error with the Capture Viewer from the SDK if I

1. Run the capture viewer and play around with the F200

2. Close the program, unplug that camera, and connect the R200

3. Run the capture viewer again

or the reverse order.  The Capture Viewer program thinks that the previously disconnected camera is still there (e.g. in the routine above, even though the R200 is connected, the streams for the F200 are present -- execution of which will ultimately crash the program after much blinking).

- - - - - - -

Strangely enough, I have to restart these services even after a fresh boot.  So again...THANK YOU for making it very clear how to restart the service!!!

- - - - - - -

As a side-note, this process can be automated a bit further.

Step 1 is to create a  bat script (e.g. mine is named reset_real_sense.bat).  The contents should be

:: The following script 'restarts' the relevant Depth Camera Manager(s) (DCM)
:: for the Intel RealSense _F_200 and _R_200.

:: Stop the RealSense DCM Services
net stop RealSenseDCM
net stop RealSenseDCMR200

:: Start the RealSense DCM Services
net start RealSenseDCM
net start RealSenseDCMR200

:: I like to see what was / was not executed;
:: change the number of seconds or delete all
:: of this if you don't care
@echo off
echo Finished restarting the relevant services,
echo counting down until exit so you can read
echo what was completed.
echo vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
echo E.g. if you do not have admin access, then
echo this script did not do anything...
Timeout 11

Notes:

(a) Starting / stopping a service with 'net' won't do anything if you don't have the service installed, but you should just delete the irrelevant lines for you (the user).  E.g. if you only have an _F_200, delete the lines pertaining to 'RealSenseDCMR200'.

(b) The echo / Timeout at the bottom is not necessary.  I just don't like that bat scripts close immediately, and like to see what happened ;)

(c) I'm sure there is a better way to do this...please chime in if you have a better way!

Step 2 is to create a shortcut to this .bat file.  Now right-click the shortcut and click on properties.  In the Shortcut tab (default tab), click on the "Advanced..." button and check "Run as Administrator".  Services cannot be started / stopped by a regular user ;)

I hope that helps somebody!

[Mona_J_1]

I disabled the camera in my computer and now it is working. 

Here's a screenshot:

[Colleen_C_Intel]

To clarify - you mean you disabled the non RealSense camera integrated into your system?

[Mona_J_1]

No not that one. I had a separate RealSense 3D camera which I connect to my laptop. I had to disable the laptop camera in the device manager. However it is somewhat weird because I never used it so there's still this question, what enabled the laptop camera and why it didn't happen previously?

Colleen Culbertson (Intel) wrote:

To clarify - you mean you disabled the non RealSense camera integrated into your system?

[Niels_Dekker]

We upgraded to Depth Camera Manager (DCM) 1.4 HF3 (installer intel_rs_dcm_f200_1.4.27.41944.exe) but we still have the same problem, I guess: When we plug in a RealSense 3D Camera (F200) into a USB3 port of our PC or laptop, we often find that the camera seems to remain undetected. For example, when we start the Camera Explorer from the SDK Sample Browser, it says that the camera is "not connected". Usually in that case, we just terminate the Depth Camera Manager (using Windows Task Manager), and then the camera is detected!

Is there any change that this issue will be fixed with another software update?