Running Mission Planner and my Pixhawk does not want to arm. Gives me Battery 1 unhealthy error. I have an identical quadcopter with a PX4 with no issues, and the parameters between the two are the same.
Values in the battery monitor 1 window look as expected.
Please provide more information
Hello. My pixhawk 6c says" prearm battery1 unnhealthy". The battery Is fully charged and the voltage Is correctly displayed on the hud. I “fixed” this by unchecking the battery level checkbox in prearms bitmap arming checks. So i can arm but the annoying message “bad battery” now pops out.
I Remember i plug the power cable on power2 plug of the FC instead of power1 and i had troubles with the battery monitor…dont know of this Is rilevant…
Anyone knows the origine of this bug?
Many thanks
We really need a .bin log
Set LOG_DISARMED,1 and try to arm, then set LOG_DISARMED,0
Did you use the MissionPlanner Initial Parameters screen to set the battery correct voltage levels?
Yes, that is very relevant. You need to use the correct plug in order to get current and voltage monitoring
Hello.
The LOG_DISARMED, 1 and than, 0 had no effect.
Yes i used MP initial parameters screen where i give cells number their max and min voltage, and the battery capacity (6 cells 7000 mah).
In this link you should find the .bin file (hopefully…)
https://drive.google.com/file/d/1OowpP4gBTKKDH_XkhZ1bxuyECWk8PYUE/view?usp=sharing
The link has an access requirement - you need to make it open to anyone
LOG_DISARMED was not to fix the issue, but to allow creation of a .bin log without arming and flying.
Figured it out, the Pixhawk 6C needs the battery and current pin manually changed to 8 and 4 respectively.
That’s right!!
Changing the pins value as you write all Is fixed.
Grateful for your support
Marco
Please do a PR to fix the hwdef file
By the way, this does not work
What is your specific issue?
The hardware definition file was fixed and should just work.
I’m facing sort of the same issue, I’m running ardupilot on speedybee F405 V4 Stack, and a 3s 5000 mAh lipo, I’m getting Prearm:Battery 1 unhealthy, even tho is correctly reading the voltage 12.4 and current at 1.1
pram list.param (19.0 KB)
Exact same problem on my config… Ardupilot / SpeedyBee / Battery voltage >12V (more than enough to prearm) >>> “PreArm: Battery 1 unhealthy” message in red in MP. Super annoying and confusing.
Probably a speedybee hardware specific error. Open a new thread for that.
Start by setting any BATT_*_MAH parameters to zero and see if the issue goes away.
Provide a list of your BATT params.
What battery pack do you have?
In the MissionPlanner HUD, is the battery voltage correct?
Does the current show as negative?
Issue solved ! My BATT parameter values were incorrectly set, essentially the VOLT related ones which were very badly set. Now, ARM higher than LOW, in turn higher than CRT and everything’s sorted-out and cleared (sorry for that, but a no nonsense error message would have helped there !)
. BATT_ARM_VOLT = 11
. BATT_LOW_VOLT = 10.5
. BATT_CRT_VOLT = 10
Thank you for your help
For 3S LiPo use these:
BATT_ARM_VOLT,11.00
BATT_CRT_VOLT,10.50
BATT_LOW_VOLT,10.80
BATT_FS_CRT_ACT,1
BATT_FS_LOW_ACT,2 or 3
MOT_BAT_VOLT_MAX,12.60
MOT_BAT_VOLT_MIN,9.90
The Initial Parameters section of MissionPlanner will set these correctly for you.
Hey @xfacta
Hope you’re doing well. My team and I are currently working on a drone project using a 6S LiPo battery at 7000mAh. We’ve been running into an issue where Mission Planner gives us a “bad battery” notification, even though we’re using a working PM02D power module.
We were wondering if you’d be able to help us figure out what might be going on. I’ve seen you have much more experience than us. Let us know what info or logs you’d need from us to get started. Whether it’s our config list, .bin file, etc.
Thanks in advance for your time!
A link to a .bin log file would be useful. Set LOG_DSIARMED,1 to gather a log.
Or you can just list all your BATT and MOT_BAT parameters.
In MissionPlanner HUD what voltage and current does it display while the battery is connected?
Verify that you have these set - use these EXACT voltage values
BATT_MONITOR,21
BATT_I2C_BUS,1
BATT_I2C_ADDR,0
BATT_ARM_VOLT,22.10
BATT_CRT_VOLT,21.00
BATT_LOW_VOLT,21.60
BATT_CAPACITY,7000
BATT_ARM_MAH,2800
BATT_LOW_MAH,2100
BATT_CRT_MAH,1400
BATT_FS_CRT_ACT,1
BATT_FS_LOW_ACT,2
MOT_BAT_VOLT_MAX,25.20
MOT_BAT_VOLT_MIN,19.80
All the MAH settings can be zero for testing or if you’re not positive about the battery capacity.