I’m new here and I need some help with this problem:
The battery monitor reads correct and stable values in the HUD (16.40V / 0.8A, unchanging over several minutes), but triggers “PreArm: Battery 1 unhealthy” and later “Battery 1 is missing, last: 16.37V used 3 mAh”, followed by a battery failsafe that blocks arming.
We probably need to see an onboard log to know for sure but I would expect that BATT_MONITOR has been set to a device that has stopped providing updates for some reason. Maybe the battery voltage is coming from BLHeli?
The thread shows the HUD holding 16.40 V and 0.8 A while the monitor later reports ‘Battery 1 is missing’; that mismatch is more informative than the absolute voltage. One possibility is a frozen telemetry update, so compare the battery message timestamps around the failsafe with the selected BATT_MONITOR source before changing any failsafe setting.
I’ve seen a similar message using an the following orqa flight controller running 4.7 as well. I will have to double check my logs like as Quinn suggested. I was only able to arm by disabling the battery fail safe bit in the arming check parameter though. I still received the warning, but was able to fly after an “arm, disarm, arm” sequence. Of course, have the utmost care when doing so to ensure the safety of yourself and those around you just in case.