Leap Control Panel falsely reading as "disconnected

ougridlab 2016-07-07 17:19:00 UTC #1

Hello, I am developing for the leap in conjunction with a vive in unity. I however am frequently running into an issue where my leap isn't being read as connected, even though the cable and provided cable extender are plugged in properly. I saw another user with the same issue but he said his end problem was that he plugged it into the wrong computer, which isn't happening here.

Any thoughts? I've tried restarting the Leap Control Panel and my computer, twice, to no luck. The problem is also inconsistent because yesterday it appeared to work fine out of nowhere after tackling the issue for an hour or so. It started up again just this morning, although I hadn't touched the cords and its been connected the same way this whole time. The light on the leap controller is green, and the icon for it shows up as black.

jhung 2016-07-07 17:20:44 UTC #2

Could you try uninstalling and reinstalling the Leap motion software to see if that resolves the issue for you?

ougridlab 2016-07-07 17:23:41 UTC #3

Done, and unfortunately with the same results as before

jhung 2016-07-07 17:24:12 UTC #4

Does hovering your mouse cursor over the Leap Motion Control Panel icon show "Disconnected"?

ougridlab 2016-07-07 17:24:57 UTC #5

Leap Motion Controller is off

jhung 2016-07-07 17:25:17 UTC #6

Does right clicking and selecting "resume tracking" do anything?

ougridlab 2016-07-07 17:26:07 UTC #7

Same results, nothing popped up or changed either

jhung 2016-07-07 17:26:36 UTC #8

Do you have another computer that you can test the controller with?

ougridlab 2016-07-07 17:27:34 UTC #9

Yes, I will be right back after testing that

jhung 2016-07-07 17:27:50 UTC #10

sounds good, let me know if you run into the same issue on the other machine

ougridlab 2016-07-07 17:28:25 UTC #11

other computer works fine, and is an identical machine to the one I am working on

jhung 2016-07-07 17:29:01 UTC #12

Open up the device manager on the machine that's having issues and check if the controller shows up under imaging devices or USB devices and maybe try a different USB port

ougridlab 2016-07-07 17:32:12 UTC #13

trying a different USB port worked, but they are the same kind of port (2.0) Why is it that this would occur?

jhung 2016-07-07 17:47:29 UTC #14

There may be some kind of connectivity issue with that one port. Are you able to use other USB devices with it?

jnovoa82 2017-10-17 17:07:00 UTC #15

Hi, I had the same problem after upgrading to windows 10 (build 16299). I solve the problem by reinstalling the drivers manually. Here is the drivers path (C:\Program Files (x86)\Leap Motion\Core Services\Drivers\dpinst64.exe).

mythosyggdrasil 2017-10-27 00:01:50 UTC #16

I was having the problem and I just want to let everyone know that jnovoa82's suggestion to reinstall the drivers manually fixed the problem for me as well.

DsharpK 2017-10-31 20:14:26 UTC #17

I was the same problem on Windows 10 (16299)
So jnovoa82's suggestion is Exactly succeced.
I manually removed the device, run the installation file for that folder, and then click Resome Tracking. It was successful.

jhung 2017-10-31 22:49:56 UTC #18

Did you guys update to the Win 10 creator's update when this issue came up?

Carpetheaddev 2017-11-07 15:47:36 UTC #19

I seem to be having this issue after updating to the fall creators update

edit: dpinst64 fixed the issue for one of my devices, but not the other one

jhung 2017-11-07 16:14:20 UTC #20

Thanks for the info. Our engineering team is currently working on a fix for this that should hopefully be releasing in the next week or two.