Hello everyone!

I recently learned about On Screen Display (OSD) and decided I wanted to try it out in my googles.

After a lot of trials and errors, I am able to access the OSD menu (Yaw Left, Pitch Up), I am also able to see the OSD splashscreen (with BetaFlight Logo) for a few seconds when I turn on the flight controller... so I should be pretty close, right?

BUT no "interesting" OSD info (like Battery Voltage, Artificial horizon, crosshair, etc... I tried out a lot) is showing on in my goggles (even when I put them right in the middle of the screen in BetaFlight Configurator), once the OSD splashscreen disappears. I recently updated to the newer version of Betaflight (4.4) but it did not change anything. 

What am I doing wrong?

I use a Speedybee 450 f3 stack + Speedybee TX800 VTX + Foxeer T-Rex mini camera.

Thanks a lot!


PS: This is my first post on this forum, but I have used information from this forum so many times already! So thanks for this great community!

Could you post a pic of your wiring?

As already mentioned we need to see some photos of your wiring, in particular the wiring between the camera and the FC and also the wiring between the VTX and the FC.

Can you please also run both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.

Here are the pics : 











And I copied and pasted the dump and diff all in the the two text files linked below.

Thanks!

All your wiring looks correct. Run the following commands in the CLI and see if doing that changes anything...

Thanks! I have just tried this cmd, but it does not change anything unfortunately!

Hey,

I assume you have the OSD turned on (Configuration > Other Features > OSD) and compiled-in in the Betaflight image that you've flashed - nowadays BF allows us to leave some features out of the flashed image to save space on chip.

On the OSD configuration page check the OSD profiles - if it's missing, it would suggest it's not compiled in.
In the top right of the page is the setting for the current profile that you are using. Check if you're using the correct one.
In the top left corner of the preview image you can change the one that is pictured - they are not linked together and might be set differently.
There are three profiles - it's the 1,2,3 in the Elements panel on the left and the three checkboxes in the row in each row - mark all three on elements you need.

Hope this helps.
Don't give up, it must work ...eventually. 

I see what you mean
I don't think that's it though  

We'll get it somehow!  

(21-Feb-2023, 12:17 AM)gwennoyel Wrote: Thanks! I have just tried this cmd, but it does not change anything unfortunately!

What model of Foxeer camera do you have? Try setting the Video Format to NTSC in the OSD tab instead of PAL.

Changed it to NTSC, PAL, AUTO, and HD but still no luck...



(I saved and disconnected in Betaflight before trying with my goggles)

Use a multimeter in continuity (beep) mode to check that you don't have a short circuit between the following pads:

• The CAM pad and either of the 5V or GND pads.
  
• The VTX pad and either of the 5V or GND pads.
  

EDIT: Also, use a magnifying glass to check that there are no minuscule solder balls, splatters of solder, or whiskers of wire between any of the pins on the rectangular 28-pin OSD chip on the FC.

I tested where you told me to with a multimeter, but no problem found...


Would there be a chance I don't have my UART(s) enabled in the right place and/or with the right "telemetry output", "sensor input", or "peripherals" ?

Thanks for the help everybody.

The OSD isn't controlled by any of the UARTs. The only options in Betaflight that control the OSD are the OSD on/off feature in the Configuration tab, and the settings in the OSD tab along with a few additional CLI commands, all of which are correctly set in your Betaflight settings.

A couple of things you have left to try is re-uploading the fonts to the MAX7456 OSD chip using the Font Manager button on the OSD tab. Just click on that button then on the Upload Font button on the OSD Font Manager screen that appears. You will need a LiPo plugged in to do that. If that doesn't resolve the issue then try re-flashing the Betaflight 4.4.0 firmware to the FC making sure that you switch on the "Full chip erase" option. If that still doesn't work then try flashing back to Betaflight 4.3.2 and/or Betaflight 4.2.11 to see if the OSD works under any of those previous versions just in case there's a bug in Betaflight 4.4.0.

I uploaded different fonts but the OSD still isn't showing up.

Before I try to change Betaflight version, could the problem come from that in the top right corner of the Betaflight app it is saying "no dataflash chip found"?


If not I'll see if different Betaflight versions make a difference with the OSD.

Thanks!

No. That status just indicates that there is no onboard flash chip for blackbox data. It has nothing to do with the OSD chip. For reference, the Speedybee F405 V3 FC does have onboard blackbox data storage capabilities, but it's provisioned as (non-removable) SD Card memory rather than dataflash memory.