So I finally got everything up and running. It took me a while to realise that I'm not supposed to use the official BF3.0 even thought the board is now supported but rather the one that was silently made available on the product page yesterday. When using the official firmware, the official OSD works but there's obviously no configuration as that's included only on the firmware available on the product page (basically there are 2 different OSD software options at this time).
The OSD is great indeed, there's a ton of configuration that can be done from the menu, pretty much anything one would wish to tune in the field so it really eliminates the need for bringing a PC. Thumbs up for that and looking forward to see this as part of official BF3.
I just have one issue now, the OSD doesn't appear when I plug the battery to the quad. I get video just fine but no OSD. For the OSD to startup, I need to plug the USB, connect to betaflight configurator and click save somewhere.
Am I doing something wrong or is this some sort of bug?
(10-Sep-2016, 10:43 AM)tozes Wrote: So I finally got everything up and running. It took me a while to realise that I'm not supposed to use the official BF3.0 even thought the board is now supported but rather the one that was silently made available on the product page yesterday. When using the official firmware, the official OSD works but there's obviously no configuration as that's included only on the firmware available on the product page (basically there are 2 different OSD software options at this time).
The OSD is great indeed, there's a ton of configuration that can be done from the menu, pretty much anything one would wish to tune in the field so it really eliminates the need for bringing a PC. Thumbs up for that and looking forward to see this as part of official BF3.
I just have one issue now, the OSD doesn't appear when I plug the battery to the quad. I get video just fine but no OSD. For the OSD to startup, I need to plug the USB, connect to betaflight configurator and click save somewhere.
Am I doing something wrong or is this some sort of bug?
No, it should just work. What voltage are you connect to Video IN pad ? battery or any other from Battery ?
If you have multimetr please check 5V on FC when you power up without USB. You can check it on any 5V pads on the board.
10-Sep-2016, 11:22 AM (This post was last modified: 10-Sep-2016, 11:23 AM by tozes.)
(10-Sep-2016, 11:02 AM)marbalon Wrote: No, it should just work. What voltage are you connect to Video IN pad ? battery or any other from Battery ?
If you have multimetr please check 5V on FC when you power up without USB. You can check it on any 5V pads on the board.
When you disconnect USB OSD is still working ?
Video In is connected directly to the battery so it's getting around 15v at the moment.
I measured on the 5v and GND next to the battery pin and reads stable 5.06v without USB and the same with USB.
Once I get it working by saving and rebooting on BetaFlight configurator, it still works fine after I disconnect the USB cable. Kinda looks like software issue.
I changed FW quite a few times between official BF3 RC14, your 2.9.1 and your 3.0.0. Could be some dirty settings that remained between firmware changes?
I'm attaching a dump of the settings just in case it could be useful.
Sorry for late response but don't get e-mail about new reply in this topic
Could you try firmware 3.0 from this package ? After loading this firmware you need to upload fonts in GUI. Or you prefer fly with 2.9.1? Today I flew about 20 batteries and have no problem with BF 3x.
ps. Remember there is new stick combination for menu - but you see this on splash screen.
I think you have to subscribe using the link at the bottom of the page if you want to get email notifications. No worries with the delay though, it was still a quick turnaround time for the fix Thanks for that!
The latest 3.0.0 build from your link solves the issue, now the OSD is available right when I plug the batt as expected. I can access the OSD menu just fine with Throttle Middle + Yaw Right + Pitch Up.
Just a few minor things you may or may not have noticed, in case you want to brush out all bugs: - On the menu 'Screen Layout > Active Elem.', the first line is too much up and goes out of the screen on my 16:9 monitor. - The PID scale is not the same as in the configurator, in the OSD there's 4.5 for P instead of 45 and 0.04 for I instead of 40 and so on. No big deal, just mentioning.
Are all this fixes and features going to be included in the official BF3 build at some point?
I finally took it for a first flight this afternoon, only 2 packs LOS. It flies so much better than the F3Evo I had before which had some really bad yaw vibrations on low throttle. With everything stock from BF3 it fell pretty great already. Can't wait to give it proper air time now!
I already subscribed, but like you see, now receive notification, but before not...
Thanks for all informations about pids values etc. will fix it. Still working on OSD menus etc. but now fighting with the driver, works on our target but for some reason doesn't on the other.
When i fix all issues on FC i will try to made changes in GUI, and then will try to send this changes to BF - then everything depend on BF team ;-)
Marbalon, thank you for the BF 3.0 working version (from your link). I had the same problem with disappearing OSD or video on 3.0. Please let us know when the official BF3.0 will be available.
Will try to put compilation to package with other firmwares. I'm working hard last days to make it work, and when it work on our board, there is a problem on the other targets with OSD, so need to find compromise... But If I'm find I will let you know ;-)
Thanks, is it on github from betaflight ? Or the rotoracer shop ? What is the difference from the last firmware you have posted here ? Can we use betaflight configurator now or what ? I am fine on the last firmware (I need only battery and time osd) -> sometimes after connecting the battery screen is black, quad needs to be restarted, it happens I think once three or four times. My friend told me to change osd to PAL, but it still happens. Is it fixed on new firmware ?
It is uploaded on on the shop link. Comparing latest v3 it is better initialization, reinitialization in case of OSD reset, and some optimizations to decrease looptime jitter.
16-Sep-2016, 10:04 AM (This post was last modified: 16-Sep-2016, 11:35 AM by blazomusic.)
I downloaded the racebase firmware from the shop, but the date modified of betaflight 3 firmware is 10.09.2016. So isn't that the old one ? edit: I checked the last one, it is the same date and time. It is the same file. Can you please post the new one ?