Thank you for taking time to review my problem. I’m a mechanical person so please lend me some grace for any ignorance.
While researching my problem I found that most causes for bad voltage readings in Mission Planner are due to incorrect power module configuration. In my situation, Mission Planner battery voltage is showing 0 for every power module configuration I’ve tried, even “Other” custom config, but in APM Planner battery voltage shows correctly. APM Planner has “APM 2.5/6 Power Module” as a battery monitor preset and this selection reports battery voltage correctly in APM Planner but not MP. When I measure the battery voltage pin from the power module on the APM CCA and multiply by the BAT_VOLT_MULT, I get the correct battery voltage. Hardware seems to be working correctly.
My hunch - MP is not recognizing the pin assignments for my hardware, as the pin assignments listed are not in the current Copter documentation. Specifically, BATT_VOLT_PIN = 13. Did we lose support for atmega MC at some point? It’s worth noting that, while I can get the current to read correctly in MP, the field of the dropdown box for “Battery Current sensing pin” in the Standard Parameters tab of MP is blank. If I choose any of the options from there current is reported grossly high.
Atmega2560 APM board (hardware ver 2.8)
RCTimer power module (old but works fine)
RFD SiK 1.9 on HM-TRP (both air and ground)
MP ver 1.3.79
APM Planner V2.0.26
Setup that works in APM Planner
Anyone know what is going on here? I prefer to use MP over APM Planner if possible.