Arducopter 3.5 RC5
MP 1.3.48
Pixhawk 2.1
3DR Power Module
Measured Anp draw by an external ampere meter: 680mA
Calculatted Amp in the Battery calibration menu in MP: 670 (no unit of measure given)
Displayed amps in Tower: 0.7A
Displayed amps in the MP hud: 670A
The amp displeased in the MP hud mixes up Ampere with milli Amps apparently.
I have the same issue on the newest version of MP on AMPs (Just updated to it this weekend). The MaH draw is wrong as well and is not calculating correctly under both the status and quick tabs. I am running the same HW:
Arducopter 3.5 RC5
MP 1.3.48
Pixhawk 2.1
3DR Power Module
The Battery per cells volts and temp are reporting incorrectly as well in MP, though Dataflash logs are OK. I put a couple of short logs in a follow up message.
I’m having the same problem with my Pixhawk 2.1 with a attopilot 180. My PH2.1 running with the supplied power module on another unit are working correctly. Weird lol. Both are running Arducopter 3.5rc5.
New update build 1.1.6338.38467 solved my problems with big numbers…readings are somehow correct numbers but it still jumping 1-10A(this may be due to my setup with Power Cube4?)
Nope: replay my Tlog in new MP, Check Mah used in status: call voltage, and temp, MP math problem I think due to new battery pram reports. all goofy when replayed.
Haven’t’ tried a new flight yet.
Joe
Still showing 112 Amps draw. Maybe /100? Also “battery-usedmah” counting up each read cycle, and MP is showing individual cell voltages at 65.535 and a battery temp of 327 (and I am not using a smart battery-so I expect a zero for these new cell volt and temp items?)
Joe
Just tested the latest beta Mission Planner with the same results. Very high current reading. Batter used field seems correct though. This running 3.5rc05 firmware and a Pixhawk 2.1.2017-05-10 12-58-27.tlog (408.0 KB) 2017-05-10 13-00-09.bin (1.5 MB)
Just heading out to test another Pixhawk 2.1 on the 3.5rc05 beta that I though was working…
Think I found the issue. Took up my quad pixhawk 2.1 running 3.5rc04 and it works fine. Upgraded the firmware to 3.5rc05 and the current displayed skyrockets. Also, the battery used is flickering and glitchy, though it seems accurate enough. This was done on Mission Planner 1.3.48 build 1.1.6338.38467.