-
Notifications
You must be signed in to change notification settings - Fork 167
Windows driver troubleshooting
Michael Lyle edited this page Jul 17, 2017
·
4 revisions
A rare issue exists with USB drivers on Windows. Usually, when one plugs in a flight board, the correct HID driver is attached and everything works well. But occasionally another driver can become attached to the flight controller, which prevents correct operation.
- Board is detected and automatically connected to GCS,
- Board information after Firmware Rescue is correct,
- Board looks running: fast led blinking at bootup,
- But on the telemetry status at the bottom of GCS, no data is received, only tx data is shown.
Uninstall windows driver and reinstall according to these steps:
- Enter the control panel, and go to the device manager.
- Expand "Universal Serial Bus controllers"
Most likely you will have one or more "USB Composite Device"
Right click -> Properties each "USB Composite Device" listed and note its "Location", each has a unique location. - Plug in the controller, but do not launch GCS.
You now have one new "USB Composite Device", Identify which one is the new one by right clicking on Properties.
Uninstall this new "USB Composite Device" ie your the controller by Right click -> Uninstall - Unplug the controller from USB Port
Sometimes it is necessary to reboot at this step. - Plug in the controller and let windows reinstall the driver. You'll hear the Windows Device Discovery tones indicating the device is successfully installed.
- Launch GCS, all should be good now.
This documentation is derived from the LibrePilot documentation page at https://librepilot.atlassian.net/wiki/display/LPDOC/Troubleshooting, which is licensed under the CC-BY-SA 3.0 license.