Skip to content

Step 6: OSD in the goggles (optional)

This step is optional. Head tracking and video work on the helicopter’s factory firmware. Do this step if you also want altitude, speed, GPS and cell voltage from the flight controller in your goggles.

View through the goggles in flight with altitude, speed and cell voltage on screen

The factory firmware has no MSP, which DJI OSD needs, and the standard ArduPilot image for this board leaves it out to fit in 1 MB of flash. So we built our own on custom.ardupilot.org: official ArduCopter Heli 4.5.6 (git 7ce11b41), board QioTekAdeptF407, the server’s default features plus MSP, MSP DisplayPort and Rally, without Airspeed. No code changes, only a different selection of features.

File
arducopter-heli-4.5.6-msp-qiotekadeptf407.apjReady to flash
build_request.json, extra_hwdef.datExact build configuration

SHA-256 of the firmware: 1ca0c7a942b9e59c4f990789383180919378b1e8b9c1e014196035e9012fdf33

ArduPilot is GPLv3. Source: tag Copter-4.5.6. This image is for the ROBAN X2 / QioTek Adept F407 only.

This step needs a command line: Python and a copy of ArduPilot at tag Copter-4.5.6. If that’s new to you, skip it. Have the helicopter on USB only, without the flight battery.

  1. Save your way back. A full parameter file (Mission Planner: Full Parameter List, Save to file) and a copy of the factory firmware with ArduPilot’s Tools/scripts/uploader.py --download. That copy is a raw .bin: pack it into an .apj and compare it byte for byte with the download.
  2. Flash the .apj with uploader.py from the same ArduPilot tag.
  3. Restore your parameters, reboot, restore again. Some battery parameters only appear after a reboot. Use Mission Planner: Full Parameter List, Load from file, Write Params. Don’t edit the saved file, because rounded values corrupt the sensor IDs. We used our own script, so this exact route is untested on this board, which is why the final bench check comes next.
  4. Before anything else, run the final bench check. A wrong board orientation shows up there, and not in the air.

To go back, flash the packed factory copy and restore the same file. We made this copy but have never had to use it.

The DJI plug on the base plate fits UART2 on the X2 mechanically, but not electrically. Plugged straight in, it shorts the flight controller’s TX to ground. Re-pin it:

UART2 on the X2Base plate port 2
Pin 2, TXPin 3, air unit UART Rx
Pin 3, RXPin 4, air unit UART Tx
Pin 6, GNDPin 2 or 5, GND
Pin 1, +5 VNot connected

The air unit takes its power from the pack. Leave DJI HDL unconnected, and find pin 1 with a multimeter.

ParameterValueWhy
SERIAL2_PROTOCOL42DisplayPort on UART2
SERIAL2_BAUD115
OSD_TYPE5MSP DisplayPort
OSD1_TXT_RES1HD grid, 50×18
MSP_OPTIONS4Betaflight font symbols. With 0 the goggles drop decimals: 16.0 V shows as “1 V”
OSD_OPTIONS17No crosshair
OSD1_CRSSHAIR_EN, OSD1_HORIZON_EN0The camera follows your head, so a horizon line would mislead
OSD_CELL_COUNT4Auto-detection miscounts Li-ion
OSD1_AVGCELLV_EN, OSD_W_AVGCELLV1, 3.4Average cell voltage on screen, warning below 3.4 V
RSSI_TYPE, RSSI_CHANNEL2, 14Signal strength from the FRM303

Turn on the other panels you want with OSD1_name_EN (ALTITUDE, GSPEED, GPSLAT, GPSLONG, HOMEDIR and so on) and place them with _X and _Y.

Restart the flight controller, then turn on Custom OSD in the goggles. The cross in the centre of the picture comes from the goggles: Settings, Camera, Gridlines, Center Point.

The flight-mode text carries an armed or disarmed symbol, the satellite count blinks until the GPS fix is good, the home arrow appears once home is set, and pre-arm messages show on screen.