I’ve been searching and searching for an answer to this and have gotten nowhere. Does anyone have an idea why I lost my OSD on my flywoo baby 2s analog when I did the betaflight update? It was working fine till then and even put the dump back into CLI. Yes OSD is turned on in the configuration and when updated analog was selected. It’s driving me crazy lol. It gives me the option to setup the OSD in BF and shows on my computer screen but it does not show in my goggles. Any help would greatly be appreciated.
Go to the CLI tab in Betaflight Configurator and click `Submit Support Data`, then send the resulting ID in a reply
Go to the CLI tab in Betaflight Configurator and click `Submit Support Data`, then send the resulting ID in a reply
@Quadbeard89 the board was flashed with a HappyModel target, since you didn't mention otherwise, I'm assuming it's stock from Flywoo - so it should use a Flywoo target, most likely FLYWOOF405S_AIO
I got it to work finally! Thank you @VitroidFPV and @GreenthumbFPV the info between the two of y'all fixed it. After reflashing the board and setting it back to BF 4.3.1 everything is good to go!
Hi Quadbeard89, amazing that you’ve managed to solve the issue 🙌 could you please mark the question resolved? Thanks!
That's good to hear! If you want to go to newer Betaflight versions, make sure that you only flash with the OSD (Analog) option - remove the OSD (Digital) option if you want previous backups to work as expected - while keeping OSD (Digital) does not prevent analog OSD from working, it requires extra setup. This has been addressed in future releases of Betaflight Configurator where it is now an exclusive option that prevents the features from colliding
“09c172bc-6715-493c-b68e-10e8bedfd735”