13-Mar-2018, 10:58 AM
Hello, I am having problems getting any of my flight controllers to connect with betaflight. I have downloaded the drivers but still no joy. Could anyone please help me figure out what the problem is?
betaflight problems |
13-Mar-2018, 10:58 AM Hello, I am having problems getting any of my flight controllers to connect with betaflight. I have downloaded the drivers but still no joy. Could anyone please help me figure out what the problem is? 13-Mar-2018, 01:20 PM What sort of problem? SoCal Kaity :D OMG, no one told me it would be this much fun! Addicted :) 13-Mar-2018, 01:51 PM If you've installed the correct drivers but it still won't connect, open Betaflight configurator and plug in USB from your quad. Run Impulse RC Driver Fixer. https://impulserc.blob.core.windows.net/..._Fixer.exe 13-Mar-2018, 02:25 PM (13-Mar-2018, 01:51 PM)RENOV8R Wrote: If you've installed the correct drivers but it still won't connect, open Betaflight configurator and plug in USB from your quad. Run Impulse RC Driver Fixer. Thank you, I will try that. What FC do you have? What OS are you running? If you are running Windows, what populates in device manager when you plug in the FC? 19-Mar-2018, 03:49 PM 19-Mar-2018, 04:27 PM 19-Mar-2018, 05:22 PM Try a different USB cable. Some are just for charging, some are for data transfer 19-Mar-2018, 09:45 PM 20-Mar-2018, 07:25 AM Or maybe a different USB port, one of my usb extensions won't do signal anymore but will still charge. Windless fields and smokeless builds 21-Mar-2018, 12:24 PM (This post was last modified: 21-Mar-2018, 12:34 PM by czdraconis.) (19-Mar-2018, 04:27 PM)Dougc1967 Wrote: Piko blx, windows 10 home, nothing populated in device manager When having issues with any USB device in Windows, always check the device manager list. Windows provide some kind of history for previously connected devices (even when the device is not successfully connected for the first time) and every time you try to connect that kind of device again, it gets previously used driver - whether it's working or not. As what my 15+ years of practice with such devices says, it's really good idea to clean these devices time after time (Windows keeps in the list ALL the devices that has been historically connected from the beginning) as this can really cause serious USB connection problems sometimes. I must say many users don't even know about this. Now you're probably asking about "how do I get rid of these ghosts?" Here's the solution: ----- 1. ----- Using .BAT file (or registry entry edit) These devices can be seen as ghosted (when disconnected) - unfortunately they are hidden in the device manager list by default. I've made my own .BAT file to make this easier, here's the code: Code: set DEVMGR_SHOW_NONPRESENT_DEVICES=1 When you run this .BAT file, it will enable ghosted devices in system registry and then opens the device manager window. Then you have to enable option to see the ghosted devices in the upper menu. Unfortunately I'm using Czech Windows translation so I'm not sure how it is in English version, but I think it should be something like VIEW->SHOW HIDDEN DEVICES. Please note that this DOES NOT enable visibility of ghosted devices permanently! ----- 2. ----- GHOSTBUSTER software After some time I've found out pretty much easier solution - free software called GHOSTBUSTER which just does the job in much more convenient way for the user. Ghostbuster can delete multiple ghosted devices according to your selection (adding class) at one time. This means you just set the class for the first time you run Ghostbuster and then just run it time after time and it automatically deletes all ghosted devices. DOWNLOAD: https://bitbucket.org/wvd-vegt/ghostbuster/downloads Personally I use the portable version just because I don't like to install this kind of simple one-purpose tools. 21-Mar-2018, 12:30 PM (This post was last modified: 21-Mar-2018, 01:10 PM by czdraconis.) So when you are experiencing problems with connecting any USB device, this is definitely a first-to-try solution I'd recommend. BTW I'd also recommend to anybody who reads this information for the first time to create the .BAT file mentioned in my post above just to see how many devices are there in the history. You'll be probably surprised and disappointed at least... So it's good to check it this way just to better understand why this is important. And then stick to use Ghostbuster time after time. |
« Next Oldest | Next Newest » |
Possibly Related Threads... | |||||
Thread | Author | Replies | Views | Last Post | |
Announcement Betaflight 4.5.0 *** FINAL RELEASE *** Now Available | SnowLeopardFPV | 4 | 460 | Yesterday, 02:19 PM Last Post: SnowLeopardFPV | |
Betaflight Configurator - HELP | iFly4rotors | 11 | 524 | 05-May-2024, 08:09 PM Last Post: Eyes.fpv | |
Announcement Betaflight 4.5.0 Release Candidate 4 Now Available | SnowLeopardFPV | 8 | 2,439 | 15-Apr-2024, 06:50 PM Last Post: SnowLeopardFPV | |
problems binding receiver on mobula 6 2024 | whattheheck345 | 13 | 516 | 30-Mar-2024, 12:32 AM Last Post: whattheheck345 | |
Betaflight Configurator Windows - Bluetooth Connection | norseman73 | 1 | 203 | 17-Mar-2024, 02:55 PM Last Post: SnowLeopardFPV |