Drones and docks
Every cell on the flight controller’s CAN bus as standard DroneCAN battery messages. Docks wake the pack by powering the bus.
MODB-BB 6–12S · MODB-SB 3–8S
Configure for thisBMS applications · drones, robots and beyond
Your system shouldn’t work around its BMS.
Most off-the-shelf BMS boards arrive locked: a fixed cell count, factory limits, a vendor app and a switch that decides for you. MODB works the other way round. Every limit is a parameter, the data is on an open CAN bus, and your controller makes the call.
Where the standard boards stop, the lab works out the right configuration with you — thresholds, balancing, protocol, harness, firmware.
3–12S
on one board family, more when stacked
4
chemistries: LiPo, LiHV, Li-ion, LiFePO4
0
switches deciding for your system
01 / Where it fits
Built for drones. Configured for anything with cells in series.
The same monitor, balancer and CAN node that watches a drone pack works wherever a battery has to report to a controller. Each tile names the starting point; the lab takes it from there.
Ground robots and AGVs
Pack data straight into the robot controller over isolated CAN, so the controller schedules charging and derates on real cell data — not a guess from pack voltage.
24–44 V on one board · higher as stacked segments
Configure for thisLight EVs
Cell voltages, temperatures and pack current to your motor controller or VCU. The BMS reports; your controller or contactor acts, on rules you set.
MODB-SB · 100 A continuous measured · stack for 36–48 V
Configure for thisLiFePO4 storage and field power
12 V and 24 V LiFePO4 on a single board, 48 V as two stacked. Telecom backup, portable power stations and solar storage that report every cell.
MODB-SB · 4S / 8S / 2 × 8S LiFePO4
Configure for thisMarine and underwater
Boards built for conformal coating, with the CAN side isolated from pack ground — useful when a vehicle shares one bus across several packs.
Either board · enclosure and sealing by you or the lab
Configure for thisBattery pack makers
One configuration per product line, loaded identically into every unit. Cell data on CAN for end-of-line testing and a fault log that ships with the pack.
Either board · configuration file per product
Configure for thisR&D and test benches
Log every cell, temperature and fault — and pack current on MODB-SB — at configurable rates over CAN, for characterisation and cycle testing.
Either board · CAN or service port
Configure for thisNot on the list?
If it has cells in series and a controller that needs to know what they are doing, it is worth a conversation.
Describe it02 / Locked vs open
A BMS that works for your system.
A closed-box BMS is designed for the vendor’s idea of a battery. MODB is designed to be told what your battery is, and to hand everything it knows to the controller that runs your machine.
AspectTypical locked BMSMODB
Cell countFixed at the factory. A different pack needs a different board.Set per build: 3–8S or 6–12S, and stackable in series for more.
Protection limitsFactory-set, often undocumented.Every threshold and delay is a documented parameter you set.
ChemistryOne chemistry per model.LiPo, LiHV, Li-ion or LiFePO4, selected in configuration.
Your dataBehind a vendor app or an undocumented serial link.Every cell, temperature and fault on an isolated CAN bus.
ProtocolWhatever the vendor chose.DroneCAN today. CANopen, J1939 or your own protocol on request.
Power cut-offThe BMS cuts power on its own rules.No switch on the board: your controller decides.
FirmwareClosed.Custom firmware logic, and source access can be arranged.
SupportA reseller.The lab that designed the board.
MODB boards monitor, balance and report; they do not switch pack current. Where an application needs a hardware disconnect, your controller drives the contactor on MODB’s data, or the planned pack-switch module does. Boards are designed toward, not certified to, industry standards.
03 / Configured with the lab
The people who designed the board configure it with you.
WhatsNext is an engineering lab, not a reseller. Getting a BMS right for an application means choosing limits, balancing and a protocol that fit how your system actually runs — so that is done together, on your pack.
- 01
Brief
Your application, pack, host system and environment. The form below turns it into a message in a minute.
- 02
Configuration
Board and cell count, chemistry, thresholds and delays, balancing, protocol and harness — chosen for your system.
- 03
Bench validation
The configuration runs on your pack, talking to your controller, before anything is built in quantity.
- 04
Pilot units
Configured boards, with the configuration documented and handed over. It is yours.
- 05
Production
The same configuration in every unit. Changes stay under your control.
PROTOCOL
Speaks your bus
DroneCAN today. CANopen, J1939 or your own message set on request, so the BMS fits the controller you already have.
FIRMWARE
Logic for your machine
Application-specific firmware — derating curves, charge handshakes, custom alarms — with source access available.
HARDWARE
Variants and harnesses
Cell count, balancing stage, connectors and harnesses chosen per build; custom board variants through a lab engagement.
04 / Start with a brief
Tell the lab about your system.
Fill in what you know; leave the rest. The form writes the message and suggests a starting board. Send it on WhatsApp or by email.
Likely starting point
MODB-SB
Your message
Opens WhatsApp or your mail app with the message filled in. Nothing is sent or stored until you press send there.
Contact
Building batteries for a specific system? Write to us.
Drones, robots, vehicles, storage or test rigs: describe the pack and the controller it has to work with.
Datasheets
Preliminary documents. Figures are design targets until measured on Alpha hardware.