Looks like Tim figured it out all ready. Using the cube orange plus requires different prams. They can be found in his video at 37:00 min in.
I have the issue that using the default parameters, the voltage is fine, but the current is jumping between 0A and -3.4A. Itās flicking between the two values about two times per second. I followed @danlaks advice, I found that with a BATT_AMP_OFFSET of 0.38, it puts the current perfectly to 0A. However it still says battery unhealthy and I canāt arm the vehicle. Has anyone else ever seen the current jump about and been able to solve the issue. I need this drone built for a client yesterday.
These are the correct values
BATT_AMP_OFFSET,0.37
BATT_AMP_PERVOLT,68.5
If you still have an issue set LOG_DISARMED,1 and gather the .bin log file. Upload it to a fileshare site and paste the link to it here.
Also specify your battery type and number of cells
Iāve changed the parameters to the ones you suggested. It now flicks between 0 and 0.1Amps. Iāve triple checked every parameter and canāt see any discrepency.
Please see the .bin file here; https://drive.google.com/file/d/1z0Uha8SNUxUKhrwMRfFg4xqtBeBjF5oz/view?usp=sharing
Thanks for your support Shawn.
Up to 100mA current draw is normal depending on the accessories you have.
I use BATT_VOLT_MULT,15.35 but itās easy enough to test and set yourself via MissionPlanner - Itās those current parameters that get tricky.
If you have a 12S Lipo (judging by your MOT_BAT_VOLT values) these are the correct voltage levels you need:
BATT_ARM_VOLT,44.30
BATT_CRT_VOLT,42.00
BATT_LOW_VOLT,43.20
Let me know if you need voltages for a different kind of battery chemistry. The Initial Parameters in MissionPlanner also sets these correctly.
Remember to set LOG_DISARMED,0
Sorry, forgot to say 12S LiIon. I have CRT_volt and Low_volt very low because theyāre some new chemistry batteries that discharge to a really low voltage.
I donāt know if you can see it in the logs, it still says battery unhealthy, even with the current and voltage looking correct. The current and voltage looks correct in the logs, itās not oscillating up and down, both look stable. The battery is at 48.5v, way above all of the battery failsafes, so I donāt know why itās saying battery unhealthy and wonāt let me arm. Cheers, Adam.
12S LiIon:
BATT_ARM_VOLT,38.30
BATT_CRT_VOLT,36.00
BATT_LOW_VOLT,37.20
MOT_BAT_VOLT_MAX,49.20
MOT_BAT_VOLT_MIN,33.60
or the LiIon semi-solid state batteries:
BATT_ARM_VOLT,37.10
BATT_CRT_VOLT,34.80
BATT_LOW_VOLT,36.00
MOT_BAT_VOLT_MAX,50.40
MOT_BAT_VOLT_MIN,32.40
Be aware that the MOT_BAT_VOLT_* values should always suit the exact battery type regardless of what you set for failsafe values, because they affect the thrust expo MOT_THST_EXPO
Hi Shawn,
I have the LiIon semi-solid state batteries and all of the values you have look spot on.
I still canāt arm the drone though, it says Battery1 unhealthy. In the arducopter manual it says this is either due to a physical connection problem, which you canāt get with the Kore carrier board unless thereās a manufacturing fault or thereās a parameter error. But Iāve followed everything I can read online and to me it looks like I have all of the battery1 parameters correct.
Try setting the battery capacity to 0, I seem to remember the capacity thresholds were 0 anyway.
EDIT:
I only ever set the voltages, I dont use the MAH settings even though they would be ideal. The MAH settings rely on ALWAYS starting the a 100% charged battery, and the capacity always being correct for the battery in use.
Hi Shawn, I set battery capacity to 0, but it still gives me battery1 unhealthy. I also went the other way and set the battery capacity to 40,000, then set the low_mah and critical_mah, so there was no zeroās left relating to battery capacity and I still have battery1 unhealthy.
I tried disconnecting everything from the kore carrier board other than the cube orange and holybro 100mw radio and it still says battery1 unhealthy. Do you think its a faulty sensor on the kore board?
A faulty battery monitor sensor?
I just checked settings on a couple more copters using Kore boards!
They are using the standard Cube Orange pin numbers for voltage and current, NOT the old Kore board pin numbers from the doco:
BATT_CURR_PIN,15
BATT_VOLT_PIN,14
Iāll try to get the doco updated properly.
Yessss!!! Itās working, thanks heaps Shawn ![]()
In hindsight, that was a bit obvious and I should have thought to look through the options of those two params.
Updating the Kore carrier manual would definitely help people out in the future.