Hi guys, I have one problem, my 5 inch quad never warn low batery and I have of activated them on dji googles menu and betaflight, what happen? I flight tomorrow to another country and it doesnt work well Thank you a lot guys

You don't get Betaflight OSD warnings in the DJI goggles unless you install modified Betaflight firmware because the "Warnings" OSD element isn't supported by the DJI FPV Goggles. You either need to just actively keep an eye on the LiPo voltage value in the OSD and land when the voltage starts to get close to 3.5V per cell, or you need to install modified Betaflight firmware that makes use of a hack to put warning messages in the craft name OSD element.

(15-Oct-2021, 03:13 PM)SnowLeopardFPV Wrote: You don't get Betaflight OSD warnings in the DJI goggles unless you install modified Betaflight firmware because the "Warnings" OSD element isn't supported by the DJI FPV Goggles. You either need to just actively keep an eye on the LiPo voltage value in the OSD and land when the voltage starts to get close to 3.5V per cell, or you need to install modified Betaflight firmware that makes use of a hack to put warning messages in the craft name OSD element.

And how can I install the modified betaflight? I dont know it

(15-Oct-2021, 03:26 PM)Fabiansendefpv Wrote: And how can I install the modified betaflight? I dont know it

Someone has a forked GitHub repo with the required modifications added to Betaflight. Have a watch of the following video to find out how to install and configure it. I'm not sure however it doing this the night before you fly out to another country will be a good idea in case something goes wrong, but that is up to you...

Or if you don't want to bother with the custom BetaFlight; Turn on Average Cell Voltage in the OSD menu of Betaflight, and land when you see if get to a certain number.

For example, I land when it gets to 3.6v.

(15-Oct-2021, 03:34 PM)SnowLeopardFPV Wrote: Someone has a forked GitHub repo with the required modifications added to Betaflight. Have a watch of the following video to find out how to install and configure it. I'm not sure however it doing this the night before you fly out to another country will be a good idea in case something goes wrong, but that is up to you...

Thanks for response, is very risky hahaha, I will do the tutorial when comeback

And another solution?

In that case just follow MrSolo's suggestion and keep an eye on the voltage readout.

(16-Oct-2021, 12:31 AM)Fabiansendefpv Wrote: Thanks for response, is very risky hahaha, I will do the tutorial when comeback

The main problem with using mbilozub's custom modified firmware is that it's not fully tested to ensure that there are no side-effects (other bugs introduced) from the implementation, and you are then forever reliant on mbilozub (who is the sole developer of that forked repo) to maintain that customised version and keep putting the changes back in for every new version of Betaflight that gets released, unless of course you are prepared to continue doing the same yourself and you know what you are doing without introducing some other undesired bugs.

Unfortunately GitHub pull request #9987 asking for a native Betaflight implementation of warnings for the DJI FPV Goggles got rejected and closed by the Betaflight developers, so I don't think we can ever expect to see that feature implemented into Betaflight without having to apply a custom modified firmware hack. INAV and Emuflight devs were more open to the idea and both of those other two firmwares now natively support Betaflight warnings in the DJI FPV Goggles without having to apply any hacks.

(16-Oct-2021, 12:31 AM)Fabiansendefpv Wrote: And another solution?

As I mentioned in post #2, I just keep an eye on the LiPo voltage (and mAh usage) in the OSD. Monitoring mAh usage is actually more important than LiPo voltage because if flying a 6S LiPo, then once voltage gets to ~3.5V per cell the voltage then starts to rapidly decrease much faster than before which can take you by surprise and not give you enough time to get the quad back to the take-off location. By monitoring the mAh you can then land when you have used the available mAh capacity of your LiPo which will happen before the voltage then starts to drop rapidly and could result in you having to emergency land your quad at an unplanned location in order to prevent the LiPo from being permanently ruined. To get accurate mAh usage readings you may need to (re)calibrate your current sensor. Procedures for checking / doing that can be found in another thread HERE.