ArduPilot Battery Integration Guide for UAV Smart BMS

Start With the ArduPilot Battery Data Path

ArduPilot can work with different battery monitor sources. A simple drone may use an analog voltage and current power module. A more advanced UAV battery may use a smart BMS that sends battery data through DroneCAN, SMBus, MAVLink, or another system-level interface. The correct path depends on the flight controller hardware, battery pack design, BMS firmware, and how the ground station should display battery state.

For a UAV Smart BMS, the key question is not only “Can the BMS output voltage and current?” The more important question is: which data does ArduPilot receive, and which data does it trust for battery failsafe? For example, ArduPilot may receive voltage and current from one monitor, SOC from a smart battery, and additional fault information through another telemetry path. If the mapping is unclear, Mission Planner may show battery data but failsafe behavior may not match the actual battery condition.

ArduPilot documentation states that up to 16 battery monitors may be used, with parameter groups starting from BATT_ and extending through additional monitor groups. This is important for multi-pack UAVs because each pack or monitor may need a separate battery instance, serial number, or sum monitor strategy.

Choose the Protocol Path: DroneCAN, MAVLink, SMBus, or Custom

The protocol path determines how much integration work the engineering team must do. DroneCAN is often preferred when the BMS can publish standard BatteryInfo data and the flight controller CAN port is available. ArduPilot documentation lists BATT_MONITOR type 8 as DroneCAN-BatteryInfo, which makes it relevant for a smart UAV battery that publishes battery data over DroneCAN.

MAVLink can also carry battery information, but the architecture must be clear. MAVLink is often the telemetry layer between autopilot, ground station, and companion computer. If the BMS sends data to a companion computer, that computer may need to translate battery data into MAVLink messages that ArduPilot or the ground system can use. This is not the same as connecting a BMS directly to an autopilot battery monitor port.

SMBus smart battery integration may be useful if the battery follows a supported smart battery model. Custom CAN, UART, or RS485 routes may require firmware adaptation, Lua scripting, companion-computer middleware, or supplier-side protocol mapping. For OEM UAV projects, the protocol document should be reviewed before sampling.

Wiring and CAN Bus Checks for ArduPilot Smart BMS

For DroneCAN BMS integration, wiring should be treated as part of the avionics bus, not as an accessory cable. Check CAN_H, CAN_L, termination, cable shielding, connector locking, bus length, node ID, and CAN port configuration. A smart battery may work on a bench tool but fail on the aircraft if the CAN bus is not terminated correctly or if the battery node conflicts with another device.

ArduPilot DroneCAN setup documentation covers CAN bus setup, DroneCAN parameters, node management, SLCAN access, and DroneCAN GUI tools. These tools are useful for checking whether the BMS node is visible before relying on it for battery failsafe.

If the BMS also uses RS485 or UART for charger communication, PC software, or upper-computer diagnostics, keep those lines separate from the flight battery monitor path. A common mistake is to prove that the BMS communicates with a PC tool, then assume ArduPilot is receiving the same data. The aircraft and the service tool may be using different interfaces.

Parameter Mapping in Mission Planner

In Mission Planner, ArduPilot battery measurement is commonly configured in Initial Setup > Optional Hardware > Battery Monitor. For advanced monitor types or additional battery instances, engineers may need to use the full parameter list. ArduPilot documentation notes that Mission Planner may only show the first two battery monitors in the Battery Monitor screen, while more battery monitor instances can be configured directly in parameters.

The most important parameter is the monitor type. For the first battery monitor, this is usually BATT_MONITOR. Additional monitor instances use related parameter groups. For DroneCAN smart batteries, ArduPilot documentation lists DroneCAN-BatteryInfo as one of the supported monitor types. Exact values and names should be verified against the firmware version and vehicle type.

Mapping BMS Data to ArduPilot Battery Status

A Smart BMS may report many fields, but ArduPilot only acts on the fields it receives and maps into its battery monitor system. Engineering teams should define which data is authoritative: BMS SOC, ArduPilot voltage-based estimate, current integration, consumed mAh, or a combined monitor strategy.

For DroneCAN smart batteries, ArduPilot documentation mentions options related to SOC and battery serial number. This matters because some BMS platforms may populate SOC differently from ArduPilot's internal estimation. If SOC is noisy, missing, or not calibrated to the UAV load profile, engineers may need to adjust monitor options, use voltage/current thresholds, or validate the BMS SOC behavior before enabling aggressive failsafe actions.

For an OEM ardupilot battery system, create a data mapping sheet before flight tests. The sheet should define every field: voltage, current, consumed mAh, remaining capacity, SOC, temperature, fault flag, serial number, battery ID, and update rate. Then compare those values across BMS software, Mission Planner, and flight logs.

Mission Planner and Log Checks Before Flight

After wiring and parameter setup, the next step is to confirm that Mission Planner displays correct battery data. Check voltage, current, capacity, SOC, temperature, and battery instance. Compare displayed voltage with a calibrated meter and compare current against a known load. If the BMS software and Mission Planner show different values, do not move to flight testing until the scaling, source, or parameter mapping is understood.

ArduPilot logs are important for integration validation. Engineers should review battery log messages after bench tests and early flight tests. Look for voltage sag during throttle increase, current direction, consumed mAh, battery failsafe events, communication dropouts, and temperature if available. For multi-battery systems, verify that each battery instance appears as expected and that summed or selected monitors behave correctly.

Return-to-Home and Battery Failsafe Strategy

Battery failsafe should be designed around the aircraft mission, not only around cell voltage. A mapping drone, agricultural UAV, inspection drone, and heavy-lift UAV may need different reserve energy and different response actions. The BMS should report accurate battery status, while ArduPilot decides aircraft-level behavior such as warning, RTL, SmartRTL, land, or another configured action.

For industrial drones, a two-stage strategy is usually safer than a single hard threshold. The low battery stage should warn the operator or trigger return while there is enough reserve for wind, payload, and landing. The critical stage should be reserved for controlled landing or stronger action. BMS hard cutoff should remain a last-resort battery protection boundary, not the normal flight-management tool.

Common ArduPilot BMS Integration Problems

Most integration problems come from source confusion, parameter mismatch, communication instability, or overly aggressive failsafe settings. The following table lists common symptoms and where to start checking.

Choosing an ArduPilot Compatible Battery System

An ArduPilot compatible battery system should be evaluated by protocol path, data-field mapping, firmware configurability, and failsafe behavior. The BMS should provide stable voltage, current, SOC, temperature, remaining capacity, and fault data. The supplier should also provide protocol documents and support for parameter review, especially when DroneCAN, custom CAN, UART, or companion-computer translation is involved.

For custom aircraft, AYAA provides custom UAV BMS solutions covering communication interface, firmware logic, smart battery protocol, charger communication, heating control, and pack-level integration. The AYAA UAV BMS FAQ also explains common topics such as SOC accuracy, pre-discharge, active balancing, communication stability, and troubleshooting.

1. Confirm the flight controller and firmware version. Parameter names and available options may vary by vehicle type and ArduPilot version.
2. Choose the battery monitor source. Decide between DroneCAN BatteryInfo, SMBus smart battery, analog monitor, MAVLink route, or custom integration.
3. Map the required fields. Define voltage, current, SOC, consumed capacity, remaining capacity, temperature, serial number, and fault status.
4. Check Mission Planner display. Verify readings against BMS software and external measurement tools.
5. Review logs under load. Confirm that voltage sag, current, SOC, and failsafe events match real battery behavior.
6. Set RTL and landing strategy. Configure low and critical failsafe actions based on tested reserve, not assumptions.

Technical References

ArduPilot's Power Monitor/Module Configuration in Mission Planner documentation explains battery monitor setup, supported monitor types, battery monitor instances, DroneCAN BatteryInfo support, arming voltage and capacity settings, serial-number handling, and calibration. ArduPilot's DroneCAN Setup documentation covers CAN bus setup, DroneCAN parameters, node management, and diagnostic tools.

These documents should be used together with the BMS supplier's protocol document and project-specific flight test data. ArduPilot parameters are powerful, but they must be mapped to the actual UAV battery pack, BMS firmware, current profile, and return-to-home requirement.

FAQ

1. What is the best way to integrate a Smart BMS into ArduPilot?

For many UAV smart battery projects, DroneCAN BatteryInfo is the cleanest route when the BMS supports it and the autopilot CAN bus is available. Set the correct battery monitor type, verify the BMS node, check Mission Planner display, and review logs before flight.

2. Which ArduPilot parameter selects the battery monitor type?

For the first battery monitor, BATT_MONITOR selects the monitor type. ArduPilot supports multiple battery monitor instances, and additional instances use related parameter groups. Exact parameter names should be verified against the firmware version.

3. Can ArduPilot use DroneCAN BMS data?

Yes. ArduPilot documentation lists DroneCAN-BatteryInfo as a supported battery monitor type. Engineers should verify node visibility, monitor type, serial number, voltage, current, SOC, temperature, and log data.

4. Can a BMS send battery data to ArduPilot through MAVLink?

It can be possible through a companion computer or middleware, but the architecture must be checked carefully. MAVLink battery data may be displayed or forwarded, but engineers must confirm whether ArduPilot uses it for battery failsafe decisions.

5. Why does Mission Planner show voltage but no SOC?

ArduPilot may be reading voltage and current from one battery monitor while SOC is not provided, ignored, or not mapped from the BMS. Check the monitor type, BMS message fields, BATT_OPTIONS, and battery display source.

6. How should RTL battery thresholds be set?

Set low and critical battery thresholds after testing the aircraft under real load. Use enough reserve for return, wind, payload, and landing. Do not rely only on no-load voltage or unvalidated SOC.

7. Should the BMS or ArduPilot decide return-to-home?

The BMS should report battery status and protect the pack at defined safety boundaries. ArduPilot should handle aircraft-level action such as warning, RTL, SmartRTL, or landing based on configured failsafe logic.

8. What should procurement teams ask before buying an ArduPilot compatible BMS?

Ask for ArduPilot integration route, DroneCAN or MAVLink support, battery fields transmitted, protocol documents, update rate, Mission Planner validation, log examples, and whether custom parameter mapping is available for OEM UAV projects.