Hi again,
 
Just a quick follow up about this
 
I'm a developer as well (not used to using C/C++ language however). So just for learning purpose, I decided to try to compile BetaFlight as well using the following two useful documents I found:
https://github.com/betaflight/betaflight...0Ubuntu.md
https://github.com/betaflight/betaflight...Version.md
 
In short, I installed Ubuntu in a VM (using VirtualBox) then I cloned BetaFlight sources.
After it I checked out version 4.0.6 (it was the last official release for my FC) using the following command:
git checkout 4.0.6
After it I edited the file betaflight/src/main/target/LUX_RACE/target.h then I added following lines:
 
#define USE_OSD
#define USE_OSD_OVER_MSP_DISPLAYPORT
#define USE_OSD_ADJUSTMENTS
#define USE_OSD_PROFILES
#define USE_OSD_STICK_OVERLAY
 
This is because these lines are not defined by default in file betaflight/src/main/target/common_pre.h
By default these lines are defined only if the FC as more than 256K FLASH mamory size and since the LUXV2 FC has 256K (not more than 256K) it does not meet this condition. So, by directly adding these lines into the file betaflight/src/main/target/LUX_RACE/target.h it activates OSD options.
 
Now, just build it using command
make TARGET=LUXV2_RACE
and the file betaflight_4.0.6_LUXV2_RACE.hex will be created. Just flash your FC using this new file. I flashed mine and now I can see OSD data in my DJI goggles. It worked :-)
 
Important note:
If I decide to fly using this custom firmware, I will do a lot of tests to be sure there is no problem. If by default, OSD options are enabled only with FC with more than 256K of flash memory, there is probably a good reason to it. I would not want to get an "Out of memory" error during my flight ;-). Anyway, I decided to buy a new F7 FC. I posted this information here just for information purpose.


Thanks for all the help I received.

G. Plante

That is good to know. Proof of concept works. Good luck if you decide to use the firmware for flight. It might be something you can bring up with the developer on github to see if there might be any issue.