One thing to note is that if you're moving to Betaflight 4 they recommend that you DON'T post dumps in directly, since enough has changed around filtering and PIDs that it might do more harm than good. If it's a diff then you're probably OK as long as you flew defaults, since it won't overwrite the existing BF4 values.

It really would be nice if Betaflight added a feature where you could open Betaflight configurator and load a backup to visually look at the configuration, rather than scroll through a dump file.

(15-Apr-2019, 04:32 PM)Sugs Wrote: It really would be nice if Betaflight added a feature where you could open Betaflight configurator and load a backup to visually look at the configuration, rather than scroll through a dump file.

I totally agree but I got used to read the dump. In addition, there are a lot of things in the dump you don't have in the GUI. It would be nice. One of our member Konrads did write a GUI interface.

https://intofpv.com/t-share-your-config-dump

Completely forgot about that, thanks voodoo!

(14-Apr-2019, 03:39 AM)voodoo614 Wrote: You are welcome.

Would you happen to know why I'm able to flash my FC manually in dfu, but cannot reach the COM port recognition on my computer. Quite frustrating seeing that my brand new ESC's I cant use right now.  I've updated all firmware. but it IS not letting me download fully my STM32. It says that the version isn't able to finish; check that info online. they had said it may be an outdated version. Please HElP?

Just run the IRC Driver Fixer, should fix your issue
https://impulserc.blob.core.windows.net/..._Fixer.exe

(30-Apr-2019, 05:27 PM)RENOV8R Wrote: Just run the IRC Driver Fixer, should fix your issue
https://impulserc.blob.core.windows.net/..._Fixer.exe

Lights up on connect, only submits a response in DFU mode. Otherwise cant connect.

Thanks for responding.

(30-Apr-2019, 06:07 PM)DClassPilot Wrote: Lights up on connect, only submits a response in DFU mode. Otherwise cant connect.

I take if from this response thatyou still aren't able to connect to the FC in normal (non-DFU) mode.

I'm not entirely sure what you mean by this...

"but it IS not letting me download fully my STM32. It says that the version isn't able to finish;"

You said you were able to flash the firmware, so what isn't able to finish? Can you please post a screenshot showing the error message.

(30-Apr-2019, 06:26 PM)SnowLeopardFPV Wrote: I take if from this response thatyou still aren't able to connect to the FC in normal (non-DFU) mode.

I'm not entirely sure what you mean by this...

"but it IS not letting me download fully my STM32. It says that the version isn't able to finish;"

You said you were able to flash the firmware, so what isn't able to finish? Can you please post a screenshot showing the error message.

Mainly just being unable to connect to my com port. Im afraid i lost the COM4 I was using on the board. (But it was already not working) in an attempt to reinstall the driver.  image here     Serial Port FAILED to open is the main error  ps a628:failed to complete installation is another stm32 error showing

Heres's another error in my troubleshooting of the comport
 

What populates in the Device Manager when you connect the FC normally?

(01-May-2019, 02:36 AM)voodoo614 Wrote: What populates in the Device Manager when you connect the FC normally?

only a com3 on an old board. Had uninstalled the com4 originally applied to the board im trying to use. But I had uninstalled it because it wasn't working. That may have been a mistake. Though now I get no response, from boot-loader, and the stm32 regular connection. Was gonna try and reinstall everything until I got a com port response; that a good idea?

You never answer what populates when you plug in your FC? I can't tell what actually pops up when you post a screenshot without pointing out what actually populates.

(01-May-2019, 06:13 PM)voodoo614 Wrote: You never answer what populates when you plug in your FC? I can't tell what actually pops up when you post a screenshot without pointing out what actually populates

I was trying to say, that only in DFU mode it would have came up as "STM bootloader". But it no longer has anything popping up when plug in; either in DFU or for regular configuration. Originally in "ports" it was listed as COMM4.
Thanks for responding

http://indotraq.com/forum/viewtopic.php?t=5

Found this Link that may solve my Windows 10 COM port issue.

For any other pilots

(01-May-2019, 08:07 PM)DClassPilot Wrote: I was trying to say, that only in DFU mode it would have came up as "STM bootloader". But it no longer has anything popping up when plug in; either in DFU or for regular configuration. Originally in "ports" it was listed as COMM4.
Thanks for responding

If you get the FC to function and still need help with driver, come back.