Battery Management System

ENNOID-BMS-SS

ENNOID-BMS-SS is a full-featured 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.

Features:

  • Automotive grade monitoring & balancing IC with separate power supply for increased reliability

  • High-side charge, pre-discharge & charge switches

  • 12S, 15S, 18S & 24S board options

  • Voltages measurements for load, charger & battery pack

  • Bi-directional current monitoring

  • SOC based on coulomb counting

  • Humidity sensor & board temperature monitoring

  • Charger detection circuit

  • Integrated pre-discharge circuit

  • Power button, USB-C, UART, I2C & isolated CAN bus interface

  • Configuring and firmware upgrades over USB through the ENNOID-BMS tool or VESC-Tool

  • 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

  • Buzzer & status LED

NEW feature for 2022:

  • VESC & VESC-tool CAN & USB compatibility for firmware updates, data monitoring & parameters configuration


Safety:

  • On-Board main fuse (50A to 150A BF1)

  • Configurable under/over temperature cutoffs for charge & discharge

  • Configurable under/over cell voltage cutoffs

  • Configurable over current cutoff

  • Configurable minimum pre-discharge value

  • Secondary fusing on all balance channels, USB port & power supply

**Boards are sold without accessories. Please buy the appropriate accessories for your own particular needs.

Contact us by email for availability

*(HD version with dual sided optional FETs)


Additional documentation:

**UART protocol

**CAN protocol

**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: