← All tools

Message & Error Explainer

What an ArduPilot message means and what to do about it

Українська

No analog input is left for the battery monitor

Stops itBattery and power4.7 only

What ArduPilot says:

New in 4.7. A battery monitor is set to an analog type (BATT_MONITOR 3, 4 or 31) but the board could not give ArduPilot an analog input to read it with. It is a Config Error: the flight controller repeats the message and does not finish starting until the parameter is corrected. The number counts from 0 here: “battery 0” is the first monitor (BATT_MONITOR), “battery 1” the second (BATT2_MONITOR).

What to do, most likely first

  1. A second or third monitor was switched on by mistake, or with a type the board cannot serve.

    CheckBATT2_MONITOR and the later ones should be 0 unless that sensor exists.

    FixSet the monitor that is not fitted to 0 and reboot. Parameters can still be changed while the board shows a Config Error.

  2. All the board's analog inputs are taken: several analog monitors, an analog airspeed sensor, analog RSSI.

    FixFree an input, or use a digital sensor type for one of the batteries, and reboot.

  3. The board has no analog battery input at all.

    CheckThe board's documentation says which battery sensor it carries.

    FixChoose the type of the sensor it does have (INA2xx, DroneCAN, ESC telemetry) and reboot.

Parameters to look at

ParameterWhat it is
BATT_MONITORBattery monitoring
BATT2_MONITORBattery monitoring
BATT_VOLT_PINBattery Voltage sensing pin on the AD7091R5 Ic
BATT_CURR_PINBattery Current sensing pin
The code that sends it

Config Error: No analog voltage channel for battery N

libraries/AP_BattMonitor/AP_BattMonitor_Analog.cpp AP_BattMonitor_Analog::AP_BattMonitor_Analog() · Open in ArduPilot Copter-4.7.1

Config Error: No analog current channel for battery N

libraries/AP_BattMonitor/AP_BattMonitor_Analog.cpp AP_BattMonitor_Analog::AP_BattMonitor_Analog() · Open in ArduPilot Copter-4.7.1

Written here for Copter 4.7. In the tool you choose your vehicle and version, see your own parameter values beside the ones named here, and drop a flight log to have every message in it explained.

Open it in the Message & Error Explainer