FlySpark logo
FlySpark logoFlySparkINAV setup guidesUpdated

Pick the grid

The video system is the name that sets how many character cells the OSD layout uses. The Screen card lists AUTO, PAL, NTSC, HDZERO, DJIWTF, AVATAR, BF43COMPAT and BFHDCOMPAT, and the demo starts on AUTO.

AUTO and PAL both preview as 30 by 16. The picture starts there. HDZERO opens 50 by 18, and DJIWTF opens 60 by 22. The layout line under the preview is the name, then the column count and the row count.

A larger grid is not a different set of alarms. The flash thresholds stay on the Alarms card, and the horizon line stays on the HUD card. This choice only changes the cells the elements snap to.

Free. Hardware connections need Chrome or Edge on a computer; phones use the FlySpark app.

  • Free
  • Nothing to install
  • Demo without hardware

In short

The Screen card's video system picks the character grid. Auto and PAL both preview as 30 by 16. HDZero is 50 by 18 and DJIWTF is 60 by 22.

Key facts

  • Video system starts on AUTO, and the layout preview draws 30 by 16, the same size as PAL.
  • NTSC draws 30 by 13. HDZero draws 50 by 18. DJIWTF draws 60 by 22.
  • AVATAR and BFHDCOMPAT draw 53 by 20. BF43COMPAT stays on the 30 by 16 grid.
  • HD OSD full redraw starts at 1.0 seconds. 0 redraws every frame. One step below 0 is legacy mode.
  • Software blinking starts off. Turn it on if warnings that should flash are invisible.
  • Antenna tracker telemetry starts off. Test repeats the top row on row 4.
  • Units start on METRIC. The alarm numbers stay metric even if you change the units.
  • Chrome or Edge uses USB or Bluetooth. iPhone has no USB host.
  • Betaflight logoBetaflight
  • INAV logoINAV
  • ArduPilot logoArduPilot
  • PX4 logoPX4
  • BLHeli_S
  • Bluejay logoBluejay
  • AM32 logoAM32
  • ExpressLRS logoExpressLRS
  • EdgeTX logoEdgeTX
  • DroneCAN logoDroneCAN
  • MAVLink logoMAVLink

Try it

See the character grid

Auto opens 30 by 16. HDZero opens 50 by 18, and DJIWTF opens 60 by 22.

AUTO · 30×16

FlySpark

Features

  • 01

    AUTO is 30 by 16

    The demo starts on AUTO. The preview draws 30 columns and 16 rows, the same grid PAL uses. The name on the layout line stays AUTO.

  • 02

    NTSC drops three rows

    NTSC is still 30 columns, but only 13 rows. Elements that sat on the bottom rows of a PAL grid no longer have those cells.

  • 03

    HDZero is 50 by 18

    HDZERO draws 50 by 18. That is the same count the Betaflight canvas list gives HDZero.

  • 04

    DJIWTF is 60 by 22

    DJIWTF is the name on the card, and it draws 60 by 22. That is the same count the Betaflight canvas list gives DJI O3/O4 and Walksnail.

  • 05

    53 by 20 is the HD canvas

    AVATAR and BFHDCOMPAT both draw 53 by 20. BF43COMPAT does not. It stays on the 30 by 16 grid.

  • 06

    Redraw starts at 1.0 seconds

    HD OSD full redraw starts at 1.0 seconds. The hint says 0 redraws every frame, and one step below 0 turns it off.

What each name draws

The layout preview asks the video system for a grid. AUTO, PAL and BF43COMPAT all draw 30 columns by 16 rows. NTSC draws 30 by 13. HDZERO draws 50 by 18. DJIWTF draws 60 by 22. AVATAR and BFHDCOMPAT draw 53 by 20. The picture uses those eight results and nothing else. Press AUTO and the line reads AUTO · 30×16. Press DJIWTF and both bars fill, because 60 columns and 22 rows are the largest pair in the list.

The Screen card shows the lookup names as they are stored. DJIWTF is that stored name, not a label the app invents. The Betaflight canvas list, on a different firmware, calls 60 by 22 the grid for DJI O3/O4 and Walksnail, 50 by 18 the grid for HDZero, and 53 by 20 Betaflight HD. INAV does not open that canvas picker. Picking the video system is what changes the preview.

Betaflight's own video system is Auto, PAL, NTSC or HD. Auto previews as PAL there too, 30 by 16, and the canvas choices stay locked until the video system is HD. Switching Betaflight to HD resets the canvas to 53 by 20 until a digital VTX reports its own grid. That is a different card. Betaflight OSD editor is where that firmware's layout lives.

Redraw, blink and the tracker row

HD OSD full redraw every starts at 1.0 seconds. The field steps by 0.5 seconds and runs up to 60.0 seconds. The hint says this is for HDZero, Walksnail and DJI over MSP DisplayPort, and that a longer interval helps at the edge of range. It also says 0 means every frame, and that one step below 0 turns the redraw off, which it calls legacy mode. The demo's 1.0 seconds is neither of those. It is a full redraw once a second.

Software blinking starts off. The hint says to turn it on if warnings that should flash are invisible. That switch does not move the alarm numbers. Those stay on the Alarms card, and OSD alarms is where altitude starts at 100 m and RSSI starts at 20%.

Antenna tracker telemetry starts on Off. On draws tracker data on the top row of the video. Test repeats that row on row 4, where you can see it. Units start on METRIC. The choices are IMPERIAL, METRIC, METRIC_MPH, UK and GA. Changing units does not change the alarm thresholds, which the Alarms footer keeps in metric.

Where you set it

Open the OSD tab on INAV and find Screen. Chrome or Edge connects over USB or Bluetooth. Android adds Wi-Fi. iPhone uses Bluetooth or Wi-Fi and has no USB host. Pick the video system that matches the goggles, then look at the layout line. It should show that name and the grid above. Save after the elements still sit inside the new cells.

The horizon is a different card. OSD horizon matches the camera uptilt to the line in the picture. It does not change 30 by 16 into 60 by 22. If the preview is still 30 by 16, the video system is still AUTO, PAL or BF43COMPAT.

FlySpark

Match the grid to the goggles

  1. Open Screen

    On INAV, open the OSD tab and find Screen. Video system starts on AUTO.

  2. Read 30 by 16

    AUTO and PAL both preview as 30 by 16. NTSC is 30 by 13. The layout line shows the name and the size.

  3. Pick the digital grid

    HDZERO is 50 by 18. DJIWTF is 60 by 22. AVATAR and BFHDCOMPAT are 53 by 20. BF43COMPAT stays 30 by 16.

  4. Leave the redraw at 1.0 seconds unless range is poor

    Full redraw starts at 1.0 seconds. The hint says a longer interval helps at the edge of range, 0 is every frame, and one step below 0 is legacy mode.

Troubleshooting

Common problems and fixes

  • Problem

    The preview is still 30 by 16

    Fix

    AUTO, PAL and BF43COMPAT all draw that grid. HDZERO, DJIWTF, AVATAR and BFHDCOMPAT are the names that open a larger one.

  • Problem

    The bottom elements fell off the grid

    Fix

    NTSC has 13 rows, and PAL has 16. A cell that used row 14, 15 or 16 has nowhere to sit on NTSC.

  • Problem

    Warnings that should flash are invisible

    Fix

    Software blinking starts off. The hint says to turn it on in that case. The alarm numbers themselves are on the Alarms card.

  • Problem

    The HD picture stutters at the edge of range

    Fix

    Full redraw starts at 1.0 seconds. The hint says a longer interval helps there. 0 redraws every frame, and one step below 0 turns it off.

FAQ

Frequently asked questions

What does the INAV video system change?

The character grid the OSD layout uses. The demo starts on AUTO, which previews as 30 by 16.

Is AUTO the same grid as PAL?

Yes. Both draw 30 by 16. The layout line still says AUTO when that is the selected name.

What grid is NTSC?

30 by 13. Same column count as PAL, three fewer rows.

What grid is HDZero?

HDZERO draws 50 by 18, the same count the Betaflight canvas list gives HDZero.

What is DJIWTF?

The name stored on the Screen card. It draws 60 by 22, the same count the Betaflight canvas list gives DJI O3/O4 and Walksnail.

Which names draw 53 by 20?

AVATAR and BFHDCOMPAT. BF43COMPAT stays on 30 by 16.

What does a full redraw of 0 do?

The hint says 0 redraws every frame. The demo starts at 1.0 seconds. One step below 0 turns the redraw off, which the hint calls legacy mode.

Why would I turn on software blinking?

It starts off. The hint says to turn it on if warnings that should flash are invisible.

What does tracker telemetry Test do?

On draws tracker data on the top row. Test repeats it on row 4, where you can see it. The demo starts on Off.

Can I set this in Chrome?

Yes, on INAV. Chrome or Edge uses USB or Bluetooth. Android adds Wi-Fi. iPhone uses Bluetooth or Wi-Fi and has no USB host.

References

Sources

The official documentation behind the background facts on this page.

  1. INAV OSD notesINAV · github.com
  2. INAV settingsINAV · github.com
  3. INAV ConfiguratorINAV · github.com

Tools

See every FlySpark tool

  • 01FlySpark logo

    FlySpark

    Match the camera

    The INAV horizon starts level, and camera uptilt starts at 0 degrees. Turn follow on and the line centres when pitch matches that uptilt in the picture.

    Learn more
  • 02FlySpark logo

    FlySpark

    Flash the value

    INAV flashes an OSD value past its alarm. The altitude alarm starts at 100 m and flashes above that, and 0 m leaves the picture steady in the demo.

    Learn more
  • 03Betaflight logo

    Betaflight

    Betaflight OSD editor in your browser

    Betaflight OSD editor for Chrome, Edge and phones: drag elements on a PAL, NTSC or HD preview, set timers, alarms and warnings, and upload MAX7456 fonts.

    Learn more
    Betaflight OSD editor in your browser

Ready to try it?

Free. Hardware connections need Chrome or Edge on a computer; phones use the FlySpark app.