I just picked up the DJI FPV Goggles and 2 air units. I am putting one of them in an existing quad that has an X-racer f303 FC. Now the way the air unit interfaces with the OSD is over an MSP connection on a uart. I have read that DJI does not use the OSD chip on the FC, and the OSD will work on a FC without one (the X-racer has none). I have it all configured, uart 2 is set to msp, OSD and Telemetry are turned on on the configuration screen. I know the FC and air unit are communicating as the goggles say unlocked after I arm the quad.  My problem is when I click on the OSD in Betaflight, it says: Your FC is not responding to commands, this probably means you do not have an integrated Betaflight OSD. Does anyone know if there any way to disable this check in CLI? I am trying to post on the DJI forums, but for some reason I never get the activation email, even though I have requested it 3 times now, and it has been close to 24 hours. No it is not in my junk mail. 
Thanks a lot guys!
Alan

For the MSP and OSD functionality to work reliably you need one of the later versions of Betaflight where the devs added functionality to cater for FC's without an OSD chip. Unfortunately support for the F3 boards was dropped from Betaflight quite some time ago so you can't get newer version of Betaflight with the required changes in for F3 FC's.

I therefore think you are unfortunately out of luck. Your best option is going to be to upgrade the FC to at least an F4, or an F7 if you have the budget.

Thanks for the reply!

Upgrading the FC would be the easiest way to fix it. However, I found this on the DJI website, "How To Set the Betaflight Flight Parameters", (https://forum.dji.com/thread-195912-1-1.html):

"It should be noted that the flight controller firmware supporting DJI HDL must be version 4.1.0 or above, as mentioned in DJI tutorial video. If S.Bus is used, you can choose any firmware."

So this means the devs only added support for the DJI HDL (which is their low latency receiver protocol).

 And in one of their FAQs DJI says "The DJI FPV Air Unit supports F3, F4, and F7 flight controllers that support the Betaflight firmware."

And I have read of people getting it to work. I suspect I may be able to get it to work using an earlier release that does not do this check. I just thought if there was a way in CLI to disable this check it would be a quick way to maybe get it working.

Thanks Again!!!

(17-Jul-2021, 02:07 PM)Deadstick Wrote: So this means the devs only added support for the DJI HDL (which is their low latency receiver protocol).

Yes. I have seen people using DJI FPV System with F3 boards, and not even using one of the "performance edition" Betaflight builds for F3.

But this looks to me like your OSD chip is busted/not recognized by configurator and I think Snow is correct in saying that can be ignored on more recent versions of BF, maybe try performance edition https://github.com/joelucid/betaflight/r...v4.1.1-EA3

Thanks so much for this information!!! Maybe I don't know how to navigate the github, but I didn't see this listed under betaflight releases, How did you come upon this info?

So the F3 performance edition did not work  . However, I tried a lot of different firmware and 3.3.3 works!!!
Hopefully, this will save someone some time!!!!