| Cell Count and Battery Chemistry | Confirm the supported series cell count and chemistry, such as Li-ion or LiPo. Do not assume that voltage limits are identical across chemistries or battery specifications. | Match the BMS cell-count setting to the pack. Check the battery and BMS documentation for per-cell charge, discharge, and cutoff limits. | The BMS must measure and protect every series cell within the limits specified for the battery. |
| Current Rating | Check continuous and peak discharge ratings, along with peak duration and thermal conditions. The BMS rating must suit the aircraft’s maximum expected load. | Compare the BMS rating with measured or calculated worst-case current, including motor and payload demand. Allow for wiring, connector, cooling, and altitude constraints. | An undersized BMS may overheat or disconnect during high-load flight; a rating alone does not guarantee performance in every installation. |
| Voltage and Power Path | Verify the BMS operating-voltage range, charge and discharge path, and whether its output is common-port or separate-port. | Check the power schematic and confirm that the charger, battery, ESCs, and any power module are connected to the intended terminals. | Incorrect port wiring or voltage limits can prevent charging, interrupt power, or damage connected equipment. |
| Communication Interface | Identify the available interface, such as UART or CAN, and confirm protocol, connector pinout, baud rate, and electrical signal levels. | Check that the flight controller supports the BMS protocol—not just the physical connector. Verify signal voltage compatibility before connecting. | UART and CAN are not automatically interchangeable, and devices using the same interface may still use different protocols or pinouts. |
| CAN Bus Integration | For CAN-connected systems, verify the supported message format, bitrate, node configuration, and termination requirements. | Consult both device manuals. A CAN bus typically requires 120-ohm termination at each physical end of the bus; avoid adding unnecessary terminators. | Correct bus setup helps prevent communication errors and allows the flight controller to receive battery data reliably. |
| Battery Monitoring Data | Check which values are reported, such as pack voltage, current, individual cell voltages, temperature, state of charge, and fault status. | Confirm that the flight controller can display or log the required fields, and compare reported voltage and current with a suitable meter during bench testing. | Useful telemetry supports low-battery warnings, flight planning, and troubleshooting. Reported state of charge depends on the BMS method and battery configuration. |
| Protection and Recovery | Review overvoltage, undervoltage, overcurrent, short-circuit, and temperature protections, including recovery behavior after a fault. | Use the manufacturer’s documented test procedure; do not deliberately trigger hazardous faults on a flight-ready battery. | Protection thresholds and reset behavior affect whether a fault is safely managed or causes an unexpected loss of power. |
| Flight Controller Compatibility | Confirm supported firmware, battery-monitor configuration, connector pinout, data scaling, and any required parameter settings. | Bench-test telemetry and alarms with propellers removed. Verify that voltage, current direction, and battery capacity readings are plausible. | A compatible connector does not ensure compatible data. Incorrect scaling or configuration can produce misleading battery estimates. |
| Size, Mass, and Thermal Design | Check board dimensions, mounting holes, cable clearance, mass, airflow, and operating-temperature limits. | Measure the available installation space and assess heat dissipation in the actual enclosure and expected flight environment. | A compact board still needs secure mounting, adequate insulation, and suitable cooling for its current and operating conditions. |
| Preflight Acceptance Checks | Confirm correct cell count, balanced cell readings, secure connections, valid telemetry, and functioning low-battery and fault alerts. | Perform ground tests according to the battery and aircraft procedures, then recheck wiring and configuration before flight. | System-level checks can reveal wiring, configuration, or communication problems before the aircraft is airborne. |