RC-Hangout

Hey there. Help again guys. I have a Omnibus F4V2 FC that has no problem flashing the updated version of betaflight 3.2. Once that is done, i proceed to connect and set up the FC in betaflight. This is where it gets weird, It doesn't matter if I try to connect to the port, configuration or motors, once I hit save and reboot my FC, fail to connect shows up in betaflight everytime I'm stuck and I can use the help guys. I have a fossil 180 coming and i have another Omnibus to install in that...if i can get them to work. Thanks

Can you put up some pictures of what is happening? Have you ticked the right boxes above. betaflight can be difficult at times:)

Thanks Graham for helping out. I made a short video instead of pictures. Sorry the quality isn't good but hopefully this might help https://youtu.be/XKG7l1_SgWA

What version are you flashing to and from DOG? e.g. version 1 to 1.1 etc

This can be several things. Try a different usb cable. Also try an earlier version. It sounds as if there is an error in the program and it is timing out.

All right then. I'm flashing from omnibusF4SD 3.1.0 to the 3.3 version. I did change out the usb cord for another one. What version should I try? When I go into the port of betaflight it has the usb vcp is the only thing on. Shouldn't i have serial rx on in uart1 too? Thanks for the links too. Hopefully I can get it going. Thanks again

Well after many attempts and different combination still no luck Doesn't make sense. I have no problem flashing but still no port settings for RX or any other ports after done flashing. DFU shows every time when I flash. Obviously I'm missing or over seeing something but I just cant put my finger on it. One of the members, Derek, is willing to help me when he has some free time. I appreciate that very much but still I'm disappointed that I'm not intelligent enough to figure it out on my own . Anyway...I'm going to keep on trying and maybe I can pull a rabbit out of a hat trick

Hi DOG, you cant jump from 3-1 to 3.3 you need to do it in stages you need to flash all the stages on the way to 3.3

Hey Graham. Thanks for the information. I didn't know that so I went back and started over. Well this time the program saved for about 2/3 seconds before it went back into failed. At least it held for a few second longer then it did before. I'll keep trying.

This is just crazy I've tried from 3.1.0, 3.1.1, 3.1.2 and so on but still nothing. It does hesitate long enough to get you excited and then it fails I've come this far, no need to give up hope yet lol. I do appreciate the help that's for sure Thanks

DOG wrote:This is just crazy I've tried from 3.1.0, 3.1.1, 3.1.2 and so on but still nothing. It does hesitate long enough to get you excited and then it fails I've come this far, no need to give up hope yet lol. I do appreciate the help that's for sure Thanks

I also found out if i plug the battery in while on betaflight, the same thing happens. The fail comes up and reboots again.

Thanks for the help. I just smoked another FC. When I'm ready for assistance again, I'll will diffidently shout out to you guys. Thanks

Not good DOG:( what about a change of FC,s?

Bit Late to this thread but most newer FC's need to be in DFU mode for flashing these days,

2 ways to put in DFU mode,

Push bootloader button or pads while connecting.

Or

connect FC go into cli and type DFU then save, then disconnect and go into flash screen and it should show in DFU mode up in the corner where it normally tells you what Com port your using.

Hey KevG. It's never to late for advice. I have another Omnibus F4V2 that I'm setting up...again. My problem wasn't DFU mode. I had no problem getting into the DFU mode and flashing but afterward. When I was setting the port modes,configuration and ect that's where the problem started. Once I try to save a port in betaflight, the FC wouldn't save and reboot. It would disconnect and start from the beginning again. Like it didn't recognize the setting and not save. Same thing if I plug the battery in to calibrate the ESC. Like it didn't want to save. Anyway, I'm going to setup another FC and see what happens this time. I'm sure I'll have questions again or might get lucky and work this time.

Hey guys, an update. After switching out USB cords and going through all different set up. I decided to re install everything and start all over again. When it came to beta flight installation I notice that this time beta flight took for ever to install compare to the first time I install it. What ever it was I finally got the FC working on the 210. I still have a few fine tune adjusting to do with the help of Derek but at least the TX and FC are communicating with each other. Now to get the 180 working . I want to say,"THANKS" for everyone's advice. It help me tremendously