Device status: DISCONNECTED - 3 leaps, 2 machines, same bugs

[bradherman]

Testing out a new shipment of leaps and I have a strange issue.
Fresh install of:
Leap_Motion_Setup_4.0.0+52173

fresh out of the box leap.
Plug it in, leap has a red led on top but shows green on all the status lights in the drivers.
I try and launch visulizer
it takes a while but launches, and the leap never kicks in.
i quit the app and the led is now out and all the device status is now disconnected.
I try and launch diagnostic viz and i see no data.

I try and plug that leap into any other machine with 4.0.0+52173 and I just get
Device status: DISCONNECTED

Went to a fresh machine, never had a leap, and repeated, same issues. reboots did nothing. LM_FirmwareReset_Win.exe did nothing.
dpinst64.exe did nothing.
Nothing strange in the device manager, no yellow triangles.

Some firmware issue with the current hardware and the new drivers perhaps?
Hope I didn't just brick 3 leaps. I have 2 more in box. Won't plug them in till after I get a support response.

I tried the other threads for Device status: DISCONNECTED, no help for me.

[jhung]

Does the software log in the Leap Motion Control Panel display any useful information?

[bradherman]

just tried the 4th leap and captured this:
[10:28:35] [Info] Connected to Leap Service
[10:45:40] Leap Motion Controller detected: LP82388095982
[10:45:45] Firmware version: 0.9.0
[10:45:45] Leap Motion Controller firmware version 0.9.0 is out of date.
[10:45:45] Initiating firmware upgrade to version 1.7.0.
[10:45:45] Do not unplug your Leap Motion Controller.
[10:45:45] If upgrade fails, please visit http://support.leapmotion.com to troubleshoot.
[10:45:45] [Info] Leap Motion Controller firmware update in progress
[10:45:46] Firmware Update Started! DO NOT DETACH
[10:45:46] Progress: 0%
[10:45:48] Progress: 10%
[10:45:50] Progress: 20%
[10:45:52] Progress: 30%
[10:45:53] Progress: 40%
[10:45:55] Progress: 50%
[10:45:57] Progress: 60%
[10:45:59] Progress: 70%
[10:46:00] Progress: 80%
[10:46:02] Progress: 90%
[10:46:04] Progress: 100%
[10:46:04] Firmware update succeeded.
[10:46:04] Unhandled exception: The device has been detached from the system
[10:46:04] The device has been detached from the system
[10:46:04] Leap Motion Controller disconnected: LP82388095982
[10:46:04] [Info] Firmware Update Complete

also tried to revert to this software:
Leap_Motion_Orion_Setup_win_3.2.1.exe
same issues.

[bradherman]

tried LM_FirmwareReset_Win.exe
results:

Leap Motion Firmware Reset tool

       ____________________________________________________
      |                                                    |
      |  Please select "Pause Tracking" in the Leap        |
      |  Motion Tray Icon.                                 |
      |                                                    |
      |              Press Enter to continue.              |
      |____________________________________________________|

Please plug in your Leap Motion Controller.

[16:15:32] [Info] ResourceHost running

[lolloso]

Same problem here. Just unpacked the device, plugged in a USB plug (no hub), did go red light first, then I installed the software and it does not get recognized as connected.

I am using Windows10; tried with both installation of the drivers (the v2 and the latest beta), and I get no light on and nothing happen. The control panel for the leap seems to be 32 bit.
In device drivers I see no leap, but a "westgate", which does not have drivers available.

I am not sure if this device is still actively developed; got it to give a try but I can't even get it to work...and I write software, so it is not an issue "user side" for sure.

[jhung]

Looks like there's an issue with the firmware on your device. Try downloading and running the firmware reset tool here: https://leapmotion.box.com/s/p5t23n0uqpxynevhgbx9h7u1swbh3h45

[bradherman]

jung, I did, Look 2 posts up. No results.

[jhung]

Sorry, that was for the post by lolloso. I created a support ticket requesting additional info from you, please respond to that at your convenience.

[bradherman]

I'm guessing he will have the same results.
I'm Ticket #61532

Seems like this problem may be growing.

windows 10.0.17134 Build 17134
Leap Version 4.0 + 52173

4 bricked leaps, one left in box.

[jhung]

Updating this thread for clarity. bradherman's issue was caused by a compatibility with the Meta 2 headset software. Uninstalling the Meta 2 software and using the firmware reset tool appears to have resolved the issue on the controller.

[bradherman]

This is correct. There was a Firmware Reset tool issue with the meta2 drivers. The meta2 drivers thought that the bricked leaps where meta2 hardware and stopped the reset tool. I uninstalled meta2 and I was able to fix the hardware.