I built a new micro using the Rush 20x20 stack.  I plugged in and Betaflight wouldn't recognize it, but it recognized every one of my other quads.  Used the same cable and everything.  It shows up under drivers as STM32 Virtual ComPort in FS mode.  

So I ran the ImpulseRC driver fixer and it tried assigning it to COM5 but it fails, saying COM5 doesn't exist (I know it exists, it's the same port I connect all other quads to).

Even though it fails - I unplug and plug the Rush quad and lo and behold, it now connects to BF via COM5.  Unfortunately, then NONE of my other quads connect, showing up no longer as COM5, but as Betaflight STM32F405 under USB devices.

I run the driver fixer with one of my other quads connected, and it assigns them all back to COM5, EXCEPT for the Rush quad.  That gets booted back to USB devices and renamed back to STM32 Virtual ComPort in FS mode. 

So I can have one or the other, but not both.  My laptop connects to all of my quads just fine, but I rarely use it and would like it to work on my main PC.  Any ideas?

Did you turn off, turn on pc?

Yes. Many times.

Have you tried it a different COM port number?

(30-Nov-2020, 06:15 PM)voodoo614 Wrote: Have you tried it a different COM port number?

Yes - at first it automatically assigned it to COM10 which worked, but then none of my quads on COM5 would connect.  It makes no sense to me.  I even tried changing it to COM5 with the rest of them.

I just discovered that my Chameleon build also does not want to connect - I have to run the driver fixer to get it to connect as well but same problem - then none of my other quads will connect.  It's like those two quads just will not play nice.

I guess I'll just have to use my laptop in the meantime while I try to figure this out, since everything connects fine with that.

Personally, I would uninstall the STM32 driver and manually reinstall it. Don't use the fixer. I think the fixer does something funny. Joshua Bardwell seems to have the same problem as you. He seems to use the fixer everytime he plugs in a different quad, which should not be the case

(01-Dec-2020, 12:52 AM)voodoo614 Wrote: Personally, I would uninstall the STM32 driver and manually reinstall it. Don't use the fixer. I think the fixer does something funny. Joshua Bardwell seems to have the same problem as you. He seems to use the fixer everytime he plugs in a different quad, which should not be the case

Interesting. Let me try that! Thank you.

Remember to click the delete driver when you uninstall. Otherwise Windows automatically install the last driver.

Didn't work

I deleted the driver STM32 Virtual ComPort in FS Mode and when I plug the quad back in, it shows up again. Made sure the box was checked as well.

That is interesting. Have you tried it in normal mode?

(01-Dec-2020, 02:33 AM)voodoo614 Wrote: That is interesting. Have you tried it in normal mode?

Normal mode?  Not sure what that is, or what FS mode is for that matter.  I just plug the quads in and that's how they come up.

When you say FS mode, what do you mean by that. I was assuming safe mode, but I think I am mistaken.

OK, I see what you mean. I totally missed it. Does your driver looks like this?



If that is the case, then I would right click and update driver. Then manually pick the STM32 VCP driver you downloaded. Restart and hopefully that will work.

I tried to update driver.  It tells me the following:



   

Which makes no sense to me because that's not what it shows up as in Device manager.

You have to manually pick the driver. Don't let Windows search for one.