I've been having trouble getting my DJI Air Unit 3 to show the Betaflight OSD, but I realized that I don't have any MSP connection at all because, when I arm the drone, the low power mode doesn't turn off. Today, I reflashed the latest version of Betaflight and used the "OSD for fpv.wtf, DJI O3, Avatar HD" preset. I've double-checked the wiring harness for the air unit to the flight controller (FC) to make sure it works, and that I used the correct UART. I have no clue what else to do—I've tried soldering it directly to the FC instead of using the connector and a series of other things I can't remember. I would really appreciate any help with this, as I have no idea what to do next. FC, air unit and goggles v2 are all on latest firmware.



EDIT FIXED kinda:
went back to betaflight 4.3 and it worked fine. i couldn't get it to work on any later version. i have no idea why but just swiched to inav 7 and it also works fine.

That FC is junk and has loads of problems   In BF, under the ports, turn on Configuration/MSP on both UART 1 and UART 4.  Also, turn off blackbox logging if you want the barometer to work.

The Duck Posted at 10-14 07:38
That FC is junk and has loads of problems   In BF, under the ports, turn on Configuration/MSP on both UART 1 and UART 4.  Also, turn off blackbox logging if you want the barometer to work.

i already had configuration/msp on for uart 1 and 4. ive tried this on 2 different fcs of the same model. the osd worked awhile ago and i dont remember what happened when it stopped working. how can i rule out it being a hardware error?

I'll take a swing at this...

The instructions to get the Betaflight OSD (i.e. MSP Display Port) working on Betaflight 4.4 or later is different as posted above. The fact that you're not able to get out of low power mode means that either the wiring is incorrect (e.g. connecting Rx to Rx instead of Rx to Tx) or the UART selection is not correct. Once you verify that you can see the actual voltage of the drone in the goggles (meaning the air unit and the flight controller are communicating correctly), you can proceed with setting up the MSP Display Port.

In Betaflight 4.4, note that you no longer need to use the two CLI commands from the O3 manual and you would set the MSP Displayport straight from the ports tab (Peripherals column). Sometimes I still need to use the set osd_displayport_device = MSP CLI command.

WeatherB Posted at 10-15 02:38
I'll take a swing at this...

The instructions to get the Betaflight OSD (i.e. MSP Display Port) working on Betaflight 4.4 or later is different as posted above. The fact that you're not able to get out of low power mode means that either the wiring is incorrect (e.g. connecting Rx to Rx instead of Rx to Tx) or the UART selection is not correct. Once you verify that you can see the actual voltage of the drone in the goggles (meaning the air unit and the flight controller are communicating correctly), you can proceed with setting up the MSP Display Port.

its just a problem with betaflight 4.43+ it worked fine in 4.3 and inav without changing wiring or port used.  i moved onto inav but thank you anyways!