(17-Apr-2019, 03:19 AM)fpvnov Wrote: There are a number of things you can do.  You may need to uninstall the drivers before you install again.  Do CP210, STM, Zadig, or Impulse RC have the option to uninstall drivers?  I would try to clean things up and then install again using as few installers as possible.  It is possible you have too many different versions of the same driver and things are getting confused.

If that does not work, you can consider manually uninstalling from Control Panel, Programs, Programs and Features.  Your drivers will be listed as Windows Driver Package - xxx.

As far as I know you only need two drivers.  DFU (for flashing) which I used Impulse RC to install, and the STM driver (to connect normally).  There are multiple ways to installe the STM driver, and I don't know which way is best.  In my case the Ardupilot Mission Planner software installed the correct driver that worked with iNav.

Thanks for the insightful and excellent advice, I hadn't thought of that angle.  Didn't realize drivers loaded as programs.  It did turn out I had a large number of USB drivers besides the STM driver.  In following up on an internet lead I tried installing mission planner as that installed the needed driver for someone.  It installed about 10 USB drivers which didn't help.  In trying to delete these extras the normal program remove couldn't remove the extra drivers.  It came up with a super detailed command line way to remove each one, which didn't work.  On the other hand I downloaded the free version of IObit uninstaller which made it super easy to remove any of them.  I removed all of the extra USB drivers and reinstalled just the stm one which shows up correctly under programs.  However it still won't open a port.  I checked in device manager and it does show just the STM virtual comport in FS mode as the only one under USB devices.  I am able to use that same PC USB to run OPEN tx and a number of FPV simulators so the USB works.  At one brief point I actually flew this 1 foot above ground so I know it can work.  I also tried a new true data micro usb cable. Suggestions?

I did make progress. After using free IObit uninstaller to uninstall all obvious USB drivers (works great!), I installed the 32 bit version of STM USB instead of the 64 bit version. On one post I read the 32 bit version worked so I installed that instead of the 64 bit version I thought I would need. It does now open a port 3 and I can connect. The crowd goes wild. All seems good in terms of sensors and GPS but I get nothing from the receiver sticks or switches in iNAV. Motors rev up, but says not ready for flight. Although the failsafe is set to RTH the parachute icon is still red. I previously set up all the switches and modes so I know it can work. Everything works fine in Freerider. Getting close. Any suggestions?

I was also having intermittent problems connecting my Kakute F7 to Inav.  What seems to have fixed it for me is I have to unplug my GPS unit from the FC when I want to connect to INAV using USB only.  With the GPS plugged in the USB alone is not enough to power it.  For whatever reason the FC will not enter the necessary state (flashing blue led) to connect to Inav if the GPS is plugged in and I am using the USB only.  If I plug a battery in, in addition to the USB, connection works fine with GPS connected.  If I unplug the GPS, USB only woks fine and I can connect.

Well I'll chime in: I had to un-install all of my usb hub software and re-install the AMD driver for the hubs.  I deleted all of my STM downloads and drivers, even the zips from the download page.  Once the AMD hub software was re-upt, I re-installed STM and CP210X. After connecting I ran Zadig and everything went smoothly from there. The key is that your virtual comport has to be in the network adapters chain, not in the usb hub. If there is clutter in the device chain STM goes to USB. While I'm no expert, it looks like windows wants to put your FC usb line in the hub.  That's good for connecting in DFU mode for flashing, but it won't get your FC to link with the configurator.  That is the work of the virtual comport.  Since my system has been cleaned out and I installed the drivers without clutter in the USB hub, it all seems to work. The late Blue Falcon did a very nice video on this: