Hello Henry,
From @iter comments in his post, I also faced the same problem on my side. I set up the correct order for the signals that come from the ESC side and it didn’t work for me either. The battery readings were also around 0.56V.
-
My first experiment was to disconnet the ESC connector from the FC and Supply the FC via the main pins (GND and VBAT IN) and also configure BATT_VOLT_PIN=12 BATT_CURR_PIN=11 as mentioned in Ardupilot documentation. (note: VBAT_IN pin and CURR pin were floating in the ESC connector side)
Result: VBAT readings were OK and CURR values were ignored. -
Then I tried to measured the VBAT level on the ESC connector side with a Multimeter to check if had the same VBAT value.
Result: Same voltage between main supply VBAT IN and VBAT IN from ESC connector side. And also the measured resistance between them was 0R. -
Then I tried to touch the CURR pin with with Multimeter’s probe, just to check if there was any non-conformity in the FC.
Result: When I touch in the CURR pin with the probe, I observed VBAT values oscillating randomly in the Mission Planner. -
So I decided to set BATT_VOLT_PIN=11
Result: The oscillating behaviour in the voltage readings was gone. -
I set BATT_CURR_PIN=12 and then I tried again to touch CURR pin with my finger and I observed: only the Current values were oscilating in Mission Planner. So, at this point I assumed that it was the correct ADC for the CURR pin.
-
Then, I removed the main power wires from the FC. And connect the FC to the ESC via the ESC cable.
Result: it’s working fine and I’m able to read the battery voltage and the current consumption.
My thoughts: Probably the manufacturer mixed the ADC channels in V6.2.