Betaflight OSD Setup

What is Betaflight OSD?

Betaflight OSD (on screen display) is an integrated component/feature in Betaflight flight controllers that shows important flight data on your FPV feed, such as battery voltage, current draw and much more.

You can even use it as a menu to change your quad’s PID, rates, filters and other settings. This article will go into what Betaflight OSD can do, and how to setup it up.

Betaflight OSD vs. MinimOSD (MWOSD)

Betaflight OSD is simply better than MinimOSD in my opinion, it has the following advantages:

  • Cheaper and solder-free! (Micro) MinimOSD is an separate module you need to purchase and install in your quad, while Betaflight OSD is normally integrated in the FC
  • Configuration is easier! All the OSD configuration can be done in the Betaflight GUI, so there is no 3rd-party software involved and there is no extra firmware flashing for OSD module
  • BF OSD doesn’t take up an extra UART (serial port) as it’s normally connected via SPI BUS

However the latest MWOSD firmware allows MimimOSD to have nearly identical features, settings and controls as Betaflight OSD. So if you are already running MinimOSD with MWOSD you don’t really need to change to Betaflight OSD, just make sure you update your firmware to the latest version.

Flight Controllers that support Betaflight OSD

Not every FC with integrated OSD supports Betaflight OSD, some of them might use 3rd part OSD firmware.

However a lot of flight controllers do these days, such as the Matek F405, DYS F4 Pro, Kakute F4, Omnibus F4 and Betaflight F3. Anyway this should be stated clearly in the product specifications.

Setup Betaflight OSD

Setting up Betaflight OSD is very simple, here are the steps I follow to setup mine.

First of all, you need to make sure the FC has the latest Betaflight firmware (OSD feature is properly supported since Betaflight V3.1).

If the FC has integrated BF OSD, you can simply connect the camera and VTX to it directly. For example, this is how the connection looks like on the DYS F4 Pro FC (assuming both camera and VTX can be powered off 5V).

Camera signal goes to “Vin”, while VTX signal connects to “Vout”.

Connect your flight controller to the Betaflight Chrome GUI, and turn on OSD feature in the Configuration tab.

Then go to the OSD Tab where you can configure the OSD settings.

The OSD interface cannot be simpler, turn on/off the flight data you want to display on the screen.

Video format – choose PAL or NTSC depends on your camera. If you do not know, you can use “Auto” which works fine by detecting the correct video format for you. But be aware that the preview screen of “Auto” and “PAL” are the same, so if your camera happens to be NTSC, the data at the very bottom will not be displayed (because NTSC has a shorter frame). When using “Auto”, it’s best to position the data up toward the middle so they don’t get “chopped off”.

Under “Alarms“, you can set the limits for RSSI, Capacity (battery), Minutes (fly time/on time), and Altitude). When these limits are reached the data will start flashing on and off on the screen.

You can drag the data around in the preview to change their positions and overall layout. But do not put them too close to the edge to avoid getting cutoff in the actual screen.

My personally choice of display elements are

  • Main battery voltage – Lipo battery voltage
  • Flytime – time since take off
  • Craft Name – custom name
  • Throttle Position
  • Current Draw – real time current draw
  • Mah Drawn – battery capacity used

Let’s walk though the Betaflight OSD menu

To activate OSD menu in your Goggles, do this stick combination:

  • mid throttle
  • yaw left
  • pitch forward

Your throttle would have to remain at around the middle throughout the operation.

From here you can scroll through the menu with the pitch stick, use roll stick to select options. Values can be changed with your roll stick.

There are a lot of things you can change, such as PID, PID profile, rate, rate profile, filter frequencies, etc. And the OSD is just going to get better and better with more options being added into the OSD menu. Most of these options are self-explanatory if you are already familiar with the Betaflight GUI.

However not all the options in Betaflight GUI are available in the OSD, so you can only change those settings on your computer if you can’t find them in the OSD menu, for example d_lowpass_type.

After you have finished editing the options, make sure to save it by going back to the main menu, and select the second last option “Save * Reboot”.

Change Betaflight OSD Font

On the OSD tab in BF GUI, in the bottom right of the screen you will see the Font Manager button. If you don’t like the default font, font size or simply need something more recognizable, you can choose a different font in this window.

Be aware that once you’ve uploaded a new font, it wont’ show it in the preview window. It will continue to show the default one. Don’t worry your OSD will show the most recently uploaded font.

FAQ

I am not getting OSD text on the screen, why?

Make sure you have chosen the correct video format, try PAL or NTSC see which one works. Another thing is to check your camera and VTX wiring.

Where to change Craft Name in OSD?

In Betaflight GUI, configuration tab, scroll all the way down, and the “craft name” text box is located on the bottom right.

 

3 thoughts on “Betaflight OSD Setup

  1. GrannyApple

    Hey is there any chance you can write about using external OSDs with betaflight?

    Blue Falcon(RIP) on YT had a micro minum osd working with a sp f3 Board. I tried hooking mine up to a SP F3evo but the osd tab would register the osd. Osd worrks fine and read attitude and voltage and arm/disarm state. Heading and RSSI stopped working.

    Reply
  2. ysdairy

    Please tell that the reach of the OSD setting screen and the reach of the picture from a camera aren’t identical.
    In case of the camera which is pal system in particular, actual indication becomes quite smaller than a setting screen.
    When setting an indication element as the end on the screen and the lower end, an element isn’t seen.
    I apologize for that in clumsy English.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Are you Robot? *

I only check blog comments once or twice a week, if you want a quick reply you can post your question on this forum IntoFPV.com... You might get a faster response from me there (multirotor related only).