Battery Management System
ENNOID-BMS-SS-LITE is a charge only BMS oriented toward Light Electric Vehicles.
Thanks to the Open-Source nature of ENNOID-BMS, customers can contribute to the project and adapt the BMS to their needs. Firmware & software repositories are available on our Github page.
Automotive grade monitoring & balancing IC with separate power supply for increased reliability
15S, 18S & 24S board options are available
Voltages measurements for charger & battery pack
Bi-directional current monitoring
SOC based on coulomb counting
Humidity sensor & board temperature monitoring
Charger detection circuit
Power button, USB C, UART, I2C & isolated CAN bus interface
Configuring and firmware upgrades over USB through the ENNOID-BMS tool (Bluetooth mobile version coming soon with external module)
On board High-Efficiency 3.3V regulator powered from the main battery pack
JST PH 2.0mm connectors
High current capacity automotive grade screw connectors for main power connections (Optional for a lower profile: you can ask for direct soldered wires for connecting to external XT90 connector or similar)
SS-LITE version has no pre-charging circuit & no main fuse. User must use an external anti-spark switch or anti-spark connector & use an external main fuse on the main discharge path. This version of the BMS has no direct control over the battery discharge path.
Transient voltage suppression on all inputs
Secondary fusing on all balance channels, USB port & power supply
*Status: 15S-LITE & 18S-LITE in production & shipping
**Boards are sold without accessories. Please buy the appropriate accessories for your own particular needs.
15S version is out of stock due to the global part shortage.
*(HD version with dual sided optional shunt & FETs).
**Discharge/regen current is limited only when the BMS is wired to monitor the discharge/regen current path. There is no current limit if the BMS discharge/regen path is bypassed. See user guide for additional information.
**The documentation pointed to could be outdated due to the constant evolution of the firmware data sets. The basis for UART & CAN implementation will stay valid despite firmware updates. You can refer to the official firmware source code for accurate data sets.
Communication related files subject to incremental changes between firmware updates:
Foundation source code used for communication: