Ashwoods Energy

Battery Management System

Application note

Version: 21/06/2012

AED-0001,Rev 3.6, Expiries: 21/08/2012

Page 1 of 22
Contents
Document History ................................................................................................................................... 4
Abbreviations .......................................................................................................................................... 4
Battery Management System Overview ................................................................................................. 5
Battery Management Module (BMM) ................................................................................................ 5
CAN bus Current Sensor (CCS) ............................................................................................................ 5
Battery Health Module (BHM) ............................................................................................................ 6
System Interface Module (SIM) .......................................................................................................... 6
BMS CAN bus Specification ................................................................................................................. 6
BMS CAN bus Communication ............................................................................................................ 6
Battery Management Module ................................................................................................................ 7
BMM Functional Specification ............................................................................................................ 7
BMM CAN Message Dictionary ........................................................................................................... 7
BMM Connector Locations and Pin outs .......................................................................................... 10
BMM Dimensions .............................................................................................................................. 12
CAN bus Current Sensor........................................................................................................................ 13
CCS Specification ............................................................................................................................... 13
CCS CAN Message Dictionary ............................................................................................................ 13
CCS Connector Pin outs..................................................................................................................... 16
CCS Dimensions................................................................................................................................. 17
CCS Interface Mode Overview .......................................................................................................... 17
Interface CAN Message Dictionary ................................................................................................... 17
BMM Manager Application ................................................................................................................... 20
BMM ID Allocation Process ............................................................................................................... 20
Ashwoods Energy Automotive BMS Control Message ......................................................................... 21
Data payload of control ECU message. ............................................................................................. 21
BMS Mode Request: ..................................................................................................................... 21
BMS Discharge Current Limit: ....................................................................................................... 21
BMS Regen Current Limit: ............................................................................................................. 21
ECU Alive Counter: ........................................................................................................................ 21
Data Payload of Charger Acknowledge Message. ............................................................................ 21
Charger Status Flags: ..................................................................................................................... 21
Charger Output Current: ............................................................................................................... 21
Charger Output Voltage: ............................................................................................................... 21
Charger Available Output Current: ............................................................................................... 22
Charger Counter:........................................................................................................................... 22

Page 2 of 22
Page 3 of 22
Document History
Date Notes
03/01/12 First Draft Release
19/01/12 BMM CAN Messages completed, Added Abbreviations.
13/02/12 CCS CAN Messages, Added to product specification’s.
22/02/12 Refinement to BMM Cell Sense wiring guide.
26/04/12 Added BMS control Signal guidance.
01/05/12 Added detail to CCS Pin out.
23/05/12 Added BMM manager section
21/06/12 Corrected BMM OVP/LVP fault bit order.

Abbreviations
Hex – Hexadecimal numeral which is base 16 i.e. 0x0 = 0 and 0xF = 16.

For more information on Hex numerals see, https://en.wikipedia.org/wiki/Hexadecimal

Dec – Decimal numeral which is base 10.

CAN – Controller Area Network Data bus

For more information on CAN bus see, https://en.wikipedia.org/wiki/Canbus

DLC – CANbus message Data Length Code, number of Bytes contained in the message.

SID – Standard Identifier bit, 11bit CAN bus message Identifier.

BMM – Battery Management Module.

OVP – Cell Over Voltage Protection event.

LVP – Cell Low Voltage Protection event.

OTP – Cell Over Temperature Protection event.

CCS – CANbus Current Sensor.

BHM – Battery Health Module.

SIM – System Interface Module.

ID – CANbus Message Identifier.

Hz – Frequency in Hertz (cycles per second).

LiFePO4 – Lithium Iron Phosphate battery chemistry.

ECU – Electronic Control Unit.

DCDC – An electronic circuit that converts DC voltage from one level to another.

Ah – Battery Capacity measured in Amp Hours.

JST – Japan Solderless Terminal Company, Connector Manufacturer.

GND – Electrical Ground potential.

Page 4 of 22
Battery Management System Overview
The Ashwoods Energy Battery Management system (BMS) is a distributed modular digital BMS which
utilises a CAN bus backbone for communication between modules. The CAN bus backbone provides
a robust and reliable communication system with significant data bandwidth that allows the BMS to
easily interact with other CAN bus components within the energy system. The CAN bus backbone is
complimented by a hardware fault line that runs through all modules within the system and also
provides a continuity check to ensure all harnesses are correctly connected. The BMS core functions
include the ability to measure and report the voltage of every cell within the battery pack, to balance
the whole battery pack without the need for a master controller, to calculate key battery
performance metrics including the battery state of charge (SOC) and to cut off the battery current to
protect the cells.

Fig.1, BMS Block Diagram.

The BMS is composed of up to 4 different modules each performing unique functions within the
system. The modular nature of the system allows it to be configured and scaled to fit the specific
requirements of an application. The modules within the system are introduced below.

Battery Management Module (BMM)

The BMM is a digital balancer that monitors and balances up to 8 Cells in series. A single BMM is
aware of the complete battery pack balance state by monitoring the CAN messages broadcast by the
other BMM’s within the system. The BMM logs cell specific performance data including extreme
voltage and temperature event counters.

CAN bus Current Sensor (CCS)

The CCS monitors the battery pack current flow and calculates the SOC applying relevant correction
algorithms. The CCS logs battery current specific data including extreme current events and battery
energy throughput. The CCS has the additional capability of driving one 12V coil line contactor,
controlling power supply to the BMM boards and monitoring two digital switch inputs.

Page 5 of 22
Battery Health Module (BHM)
The BHM monitors key parameters relating to the health and usability of the battery pack including
chassis isolation, overall pack temperature and total pack voltage. The BHM controls battery heating
and cooling if available to ensure optimum operating conditions for the battery pack. The BHM
provides a secondary pack level thermal protection level to complement the BMM cell level thermal
protection. The BHM logs pack specific health data including isolation faults and extreme
temperature events.

System Interface Module (SIM)

The SIM provides an interface between the BMS CAN bus and non CAN bus energy system
components. The SIM has 5 digital outputs and 2 digital inputs which include cutback and inhibit
signals for charge/discharge output, key switch and charger present inputs. The SIM also provides
visual and RS232 user diagnostics and setup of systems.

BMS CAN bus Specification

The BMS default operation mode is CAN 2.0B Passive at a data rate of 500Kbits/s. This means that
the BMS handles standard 11 bit message IDs and ignores extended 29 bit message IDs allowing the
BMS to operate within a mixed CAN domain of standard and extended IDs without error. The
interface modules and CCS can be modified to utilise extended message identifiers if required. A
maximum of 120 modules can function on a single CAN bus. The CAN bus is galvanically isolated
from the battery pack and is common to vehicle chassis.

BMS CAN bus Communication

The BMS utilises CAN bus communication for the distributed balancing strategy and other internal
housekeeping requirements between the system modules. The BMS CAN bus system is a broadcast
approach with critical message time outs used for safety, this approach is used for reliability and to
reduce the number of message IDs required within the system. In normal operation each module
within the system broadcasts 2 message types a 5Hz “A Message” which contains BMS operational
data and a 1Hz “B Message” which contains status and diagnostic information. The “A Message” is
normally broadcast on the modules even ID and the “B” on the odd ID. To function correctly the
BMS requires an exclusive contiguous pool of CAN message IDs, the size of the ID pool required is
dependent on the number of modules within the system. A system requires 2 CAN Message IDs for
each module within the system for the “A” and “B” message types and 2 further IDs for global
command and control functions i.e. firmware updating.

CAN Message ID Pool = (2 x Number of Modules within BMS) + 2

An example is a 102V battery pack made from 32 LifePO4 Cells connected in series. This battery pack
requires 4 BMM’s and is also fitted with a CCS and a BHM, the total number of modules within the
BMS is 6 which means that 14 CAN message IDs are required i.e. 0x100 to 0x10E where 0x100 and
0x101 are used as the global command and control message IDs.

Depending on the BMS integration within the application up to 12 further CAN message IDs may be
required for diagnostic broadcast and communication with battery charger, vehicle ECU, DCDC
converter and/or traction inverter.

Page 6 of 22
Battery Management Module

BMM Functional Specification

• Cell Voltage Range per balance channel: 500mv to 4530mV
• Cell Voltage Broadcast resolution: 10mV
• Active balance supply current: 130mA
• Dissipative balance current max: 900mA
• Operating Supply Current at 12V: 65mA
• Operating Supply Voltage Range: 9V to 14V
• Functional Temperature range: -27⁰C to +65⁰C
• Withstand Temperature range: -40⁰C to +85⁰C
• Isolation to Chassis GND: 1000V
•

BMM CAN Message Dictionary

Each BMM within the system will use a unique pair of message IDs for it’s “A” and “B” messages.

A Message Content: Cell Voltages

CAN Message ID: Even (SID0 = 0), e.g. 0x102 in the battery pack example

Broadcast Rate: 200mS (5Hz)

Message Length (DLC): 8 Bytes

Message Data:

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7

Cell 1 Volt Cell 2 Volt Cell 3 Volt Cell 4 Volt Cell 5 Volt Cell 6 Volt Cell 7 Volt Cell 8 Volt

Min. Value Max. Value

Description Scaling/Offset
(hex) (dec) (hex) (dec)
10mV per bit with 0x01 2.01 VDC 0xFD 4.53 VDC
B0 –B7 Cell X Volt
2V Offset Data Range Examples
0x00 >0.50V & <2.00 V
0x32 +2.50 V
0xA5 +3.65 V
0xFE Cell <0.5V (Dead Cell)
0xFF Cell Not Present
The BMM has multiple “B” messages that can be requested for diagnostic purposes from the PC
application, the standard broadcast message is detailed below.

Page 7 of 22
B Message Content: Fault Events and Status Flags

CAN Message ID: Odd (SID0 = 1), e.g. 0x103 in the battery pack example

Broadcast Rate: 1000mS (1Hz)

Message Length (DLC): 8 Bytes

Message Data:

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7

Message Status Temp 1-4 Temp 5-8 OVP LVP Count OTP Cycle
Type Flags Count Count Count

Min. Value Max. Value

Description Scaling/Offset
(hex) (dec) (hex) (dec)
Bits 0-6 Diag, Bit 7 0x00 Msg 0 0x80 Msg 128
B0 Message Type
Standard “B” MSg Data Range Examples
0x00 Diag Msg 0
0x40 Diag Msg 64
0x7F Diag Msg 127
0x80 Standard B Message

Min. Value Max. Value

Description Scaling/Offset
(hex) (dec) (hex) (dec)
0x00 0 0xFF 255
B1 Status Flags 1 bit per Flag
Data Range Examples
Bit 0 (&0x01) Cell Over volt
Bit 1 (&0x02) Cell Under volt
Bit 2 (&0x04) Cell Over Temp
Bit 3 (&0x08) DCDC Cells 1-4 ON
Bit 4 (&0x10) DCDC Cells 5-8 ON
Bit 5 (&0x20) Resistor Over Temp
Bit 6 (&0x40) DCDC Over Temp
Bit 7 (&0x80) System Fault
Indicating either CAN
bus, Calibration or
Temperature
sensor error

Page 8 of 22
 Min. Value Max. Value
Description Scaling/Offset
(hex) (dec) (hex) (dec)
1⁰C per bit with 0x0D -27⁰C 0x8C 100⁰C
B2, B3 Temp X – X
40⁰C Offset Data Range Examples
0x0D -27⁰C
0x28 0⁰C
One temperature sensor per 4 Cells 0x3F 23⁰C
0x8C 100⁰C

Min. Value Max. Value

Description Scaling/Offset
(hex) (dec) (hex) (dec)
0x00 0 0xFF 255
B4, B5, B6 XXX Count 1 bit per event
Data Range Examples
0x00 0 Events
0x32 50 Events
OVP, LVP and OTP 0x64 100 Events
0xFF 255 Events

Min. Value Max. Value

Description Scaling/Offset
(hex) (dec) (hex) (dec)
0x00 0 0xFF 2550
B7 Cycle Count 1 bit/ 10 Cycles
Data Range Examples
0x00 0 Cycles
0x32 500 Cycles
0x64 1000 Cycles
0xFF 2550 Cycles

Page 9 of 22
BMM Connector Locations and Pin outs

Connectors Locations

J6

J1

J5

J9

J7 J2

Fig.2, BMM Connector Locations.

J6 (5 Way JST XH 2.5mm) CAN Bus, Fault and Power In

J1 (5 Way JST XH 2.5mm) CAN Bus, Fault and Power Out

Connector Housing part number: JST XHP-5. Contact part number: JST SXH-001T-P0.6.

J7 (6 Way JST PH 2mm) Cells 1-4 Sense leads (AE Supplied lead has black heat shrink)

J2 (6 Way JST PH 2mm) Cells 5-8 Sense leads (AE Supplied lead has Red heat shrink)

Connector Housing part number: JST PHR-6. Contact part number: JST SPH-002T-P05S.

J5 Temperature Sensor Cells 1-4 (Non Polarised connector as N Type Thermistor)

J9 Temperature Sensor Cells 5-8 (Non Polarised connector as N Type Thermistor)

It is recommended that the Cell Voltage and Temperature sense leads are kept shorter than
300mm to minimise electrical noise coupling into the signals.

CAN Bus, Fault and Power Connections

In (J6) Out(J1)

Pin 5 = Chassis GND (Black Wire) Pin 5 = Chassis GND (Black Wire)

Pin 4 = +12V Supply (Red Wire) Pin 4 = +12V Supply (Red Wire)

Pin 3 = Fault Line In (White Wire) Pin 3 = Fault Line In (White Wire)

Pin 2 = CAN Low (Yellow or Black Wire) Pin 2 = CAN Low (Yellow or Black Wire)

Pin 1 = CAN High (Pink or Red Wire) Pin 1 = CAN High (Pink or Red Wire)

Page 10 of 22
 Pin 6 to BAT 8+
BAT 8

Pin 5 to BAT 7+/8-

BAT 7

Pin 3 to BAT 6+/7-

BAT 6

Pin 2 to BAT 5+/6-

BAT 5

Pin 1 to BAT 4+/5-

Pin 6 to BAT 4+/5-

BAT 4

Pin 5 to BAT 3+/4-

BAT 3

Pin 3 to BAT 2+/ 3-

BAT 2

Pin 2 to BAT 1+/ 2-

BAT 1

Pin 1 to BAT 1-

Fig.3, BMM Cell Voltage Sense Connections.

Cell Sense Lead Connections

Cells 1-4 (J7) (Black Heat Shrink) Cells 5-8 (J2) (Red Heat Shrink)

Pin 6 = Cell 5-/4+ (Red Wire) Pin 6 = Cell 8 + (Red Wire)

Pin 5 = Cell 4-/3+ (Black Wire) Pin 5 = Cell 8-/7+ (Black Wire)

Pin4 = Not connected Pin4 = Not connected

Pin 3 = Cell 3-/2+ (White Wire) Pin 3 = Cell 7-/6+ (White Wire)

Pin 2 = Cell 2-/1+ (Orange Wire) Pin 2 = Cell 6-/5+ (Orange Wire)

Pin1 = Cell 1- (Green Wire) Pin1 = Cell 5-/4+ (Green Wire)

Where Cell 1 is the most negative cell in the series string and Cell 8 is the most positive.

For a final sanity check Bat 4+/5- (Red wire) from the J7 Black Heat Shrink harness is common to Bat
4+/5- (Green Wire) from the J2, Red Heat shrink harness.

Page 11 of 22
BMM Dimensions

Fig.4. Standard BMM Assembled in Chassis Dimensions (mm).

Fig. 5. OEM BMM Dimensions (mm)

Page 12 of 22
CAN bus Current Sensor

CCS Specification
• The CAN bus Current Sensor is available in 3 measuring ranges.
• +/- 300Amp with 200mA Resolution.
• +/- 600 Amp with 400mA Resolution.
• +/- 1200Amp with 800mA Resolution.
• Measured Signal Bandwidth: 1.5kHz
• Operating Temperature Range: -40⁰C to +85⁰C
• Standby power consumption at 12V:40mA
• Operating power consumption at 12V: 80mA
• 12V 4A Suppressed Contactor Driver.
• 12V 4A Supply for BMM’s.
• 24V Tolerant Ignition Signal input.

CCS CAN Message Dictionary

Each CCS within the system will use a unique pair of message IDs for its “A” and “B” messages.

A Message Content: Measured Current, Sensor Zero Offset, Accumulated Ah

CAN Message ID: Even (SID0 = 0), e.g. 0x10D in the battery pack example

Broadcast Rate: 200mS (5Hz)

Message Length (DLC): 8 Bytes

Message Data:

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7

Current Current Offset Offset IGNORE IGNORE Ah Count Ah Count
Low Byte High Byte Low Byte High Byte Low Byte High Byte

Min. Value Max. Value

Description Scaling/Offset
(hex) (dec) (hex) (dec)
100mA per bit 0xD120 -1200.0A 0x2EE0 +1200.0A
B1, B0 Current
Signed Int16 Data Range Examples
0xD120 -1200.0Amps
0xE890 -600.0Amps
The Current range depends on the sensor
0x0000 0.0Amps
ordered, standard is +-600Amp
0x1770 +600.0Amps
0x2EE0 +1200.0Amps

Page 13 of 22
 Min. Value Max. Value
Description Scaling/Offset
(hex) (dec) (hex) (dec)
100mA per bit 0xFF38 -20.0A 0x +20.0A
B3, B2 Offset
Signed Int16 Data Range Examples
0xFF38 -20.0Amps
The Offset is fixed at device power on and 0x0000 0.0Amps
is provided for diagnostic use only 0x00C8 +20.0Amps

Min. Value Max. Value

Description Scaling/Offset
(hex) (dec) (hex) (dec)
10mAh per bit 0x0000 0.0Ah 0xFFFF 655.35Ah
B7, B6 Ah Count
Int16 Data Range Examples
0x0000 0.00Ah
0x4E20 200.00Ah
0xFFFF 655.35Ah

The CCS has multiple “B” messages that can be requested for diagnostic purposes by the PC
application, the standard broadcast message is detailed below.

B Message Content: Fault Events, Status Flags

CAN Message ID: Odd (SID0 = 1), e.g. 0x10E in the battery pack example

Broadcast Rate: 1000mS (1Hz)

Message Length (DLC): 8 Bytes

Message Data:

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7

Message System Fault Fault Fault Fault PCB Temp PCB Temp
Type State Flags low Flags Flags Flags High Low Byte High Byte

Min. Value Max. Value

Description Scaling/Offset
(hex) (dec) (hex) (dec)
Bits 0-6 Diag, Bit 7 0x00 Msg 0 0x80 Msg 128
B0 Message Type
Standard “B” MSg Data Range Examples
0x00 Diag Msg 0
0x40 Diag Msg 64
0x7F Diag Msg 127
0x80 Standard B Message

Page 14 of 22
 Min. Value Max. Value
Description Scaling/Offset
(hex) (dec) (hex) (dec)
Enumerated BMS 0x00 0 0xFF 255
B1 System State
State Flags Data Range Examples
0x00 System Ready
0x01 System Run
Normally only Initialise, Run and Error
0x02 System Plugin Charge
apply. Other states are for interface.
0x03 System Error
0x04 System Initialise

Min. Value Max. Value

Description Scaling/Offset
(hex) (dec) (hex) (dec)
0x0000 0 0xFFFF 65535
B5, B2 Fault Flags 1 bit per Flag
Data Range Examples
Bit 0 (&0x01) BMM Temp Low
Bit 1 (&0x02) BMM Temp High
Bit 2 (&0x04) BMM Missing
Bit 3 (&0x08) BMM Comms
Bit 4 (&0x10) BMM Fault line
Bit 11 (&0x400) Current Error
Bit 17 (&0x20000) Controller Coms
Bit 18 (&0x40000) EV_Coms Fault
Bit 19 (&0x80000) CCS_COMS Fault
Bit 20(&0x100000) Ash_CAN Coms Fault

Min. Value Max. Value

Description Scaling/Offset
(hex) (dec) (hex) (dec)
B7, B6 PCB 1⁰C per bit Signed 0xFFD7 -40⁰C 0x0050 80⁰C
Temperature Int16 Data Range Examples
0xFFD7 -40⁰C
0x0000 0⁰C
0x0019 +25⁰C
0x0050 +80⁰C

Page 15 of 22
CCS Connector Pin outs

Fig.6. CCS Connector Location.

J1 CAN bus, Power and Signal Connection.

Pin 1 is top left corner in this view and can be identified by the moulded rib.

Pin 1 = +12 Supply In Pin 9 = +12 Supply In

Pin 2 = GND Pin 10 = Contactor Power Out

Pin 3 = GND Contactor Pin 11 = Ignition Signal In

Pin = 4 CAN High Pin = 12 CAN High

Pin = 5 CAN Low Pin = 13 CAN Low

Pin 6 = Fault Line Out Pin 14 = Fault Line In

Pin 7 = +12 Supply In Pin 15 = BMM Power Out

Pin 8 = GND Pin 16 = GND BMM

Molex Mini-Fit Jr. 16 Way

Connector Housing part number: Molex 39-01-2160. Contact part number: Molex 39-00-0078.

Page 16 of 22
CCS Dimensions

Fig.7. CCS Mounting Dimensions (mm)

CCS Interface Mode Overview

The CCS supports an additional operating mode where it can provide full BMS interface data for a
battery pack as well as control the pack line contactor and BMM bus power bus. The BMS interface
data includes pack current limits and status. The CCS can also control a CAN bus enabled battery
charger to implement BMS lead charging. The additional CAN messages are detailed in the following
dictionary.

Interface CAN Message Dictionary

State Of Charge Message Content: State of Charge, Battery Current, State of Health

CAN Message ID: 0x122

Broadcast Rate: 200mS (5Hz)

Message Length (DLC): 8 Bytes

Message Data:

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7

Current Current Current Current Pack State Pack Ah Pack Ah Pack State
Average Average Raw Low Raw High of Health Low Byte High Byte of Charge
Low Byte High Byte Byte Byte % %

Page 17 of 22
Charger Control Message Content: Requested Voltage, Current, Pack Voltage and Charge State.

CAN Message ID: 0x125

Broadcast Rate: 1000mS (1Hz)

Message Length (DLC): 8 Bytes

Message Data:

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7

Current Current Voltage Voltage Pack Pack Counter Charge
Request Request Request Request Voltage Voltage State
Low Byte High Byte Low Byte High Byte Low Byte High Byte

Current Limit Message Content: Discharge and Charge current limits

CAN Message ID: 0x126

Broadcast Rate: 200mS (5Hz)

Message Length (DLC): 8 Bytes

Message Data:

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7

Charge Charge Discharge Discharge Charge Discharge BMM BMM
Limit Low Limit High Limit Low Limit High Moderator Moderator Pack Max Pack Min
Byte Byte Byte Byte Temp Temp

Energy Statistics Message Content: Battery Energy Throughput in Watt Hours.

CAN Message ID: 0x127

Broadcast Rate: 1000mS (1Hz)

Message Length (DLC): 8 Bytes

Message Data:

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7

Wh Drive Wh Drive Wh Regen Wh Regen Wh Trip Wh Trip Wh Chrg Wh Chrg
Low Byte High Byte Low Byte High Byte Low Byte High Byte Low Byte High Byte

Journey Statistics Message Content: Peak Temperature and Current Values during journey.

CAN Message ID: 0x129

Broadcast Rate: 1000mS (1Hz)

Message Length (DLC): 8 Bytes

Page 18 of 22
Message Data:

Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7

Peak Peak Peak Peak Journey Journey Journey Journey
Charge Charge Discharge Discharge Max BMM Max BMM Min BMM Min BMM
Low Byte High Byte Low Byte High Byte Temp Temp ID Temp Temp ID

Page 19 of 22
 BMM Manager Application

BMM ID Allocation Process

4
3

Fig.8 BMM Manager Screen Shot.

ID Allocation Procedure

1. Press “unallocated”
2. Set the virtual pack balancing range to the number of BMM modules on the bus, starting
from 1. i.e. 32S 2P system would have 8 BMM modules so range is 1 to 8.
3. Set the ID allocate from board number to the starting range of the pack i.e. if the 32S 2P
system was split into two 32S 1P packs they could be allocated individually as pack 1 (ID’s 1
to 4) and pack 2 (ID’s 5 to 8). So pack 1 would start from ID 1 and pack 2 would start from ID
5.
4. Press “ID allocate” you will now see the ID’s that are being allocated appear in the cell
column of the table.
5. Once all of the ID’s have been allocated cycle the 12V power supply to the pack.
6. The Cell data and statics should now appear in the table, the row will be proportional to the
ID of the BMM so for high ID numbers you may need to scroll down to find them in the
table.

Page 20 of 22
Ashwoods Energy Automotive BMS Control Message
The section following details the best practise control messages to be used during automotive BMS
integration. It is also recommended that the BMS to Charger control message has a checksum if the
charger voltage is >255V to minimise the risk of data interpretation error. The recommended
checksum is created in the final byte of the message from an Exclusive OR operation performed on
all of the previous bytes in the message.

Data payload of control ECU message.

Typically 6 Bytes required on 1000mS cycle time for EV application and 100mS for Hybrid
Applications.

BMS Mode Request:

This requests the operation state of the BMS to be; Charge state, Drive state, Pre-charge State or
Standby state. The BMS has 2 additional operational states which are Initialise state and Error State.
These states cannot be requested by the ECU. Commonly this message is BIT encoded within a single
byte i.e. 1 bit per state.

BMS Discharge Current Limit:

This is a repeat of the battery discharge current limit that the ECU is working with to acknowledge
acceptance of the current limit when in Drive mode. Commonly this is sent as a signed integer 16 bit
with units of 100mA giving +/- 3276.7 Amps range

BMS Regen Current Limit:

This is a repeat of the battery Regen current limit that the ECU is working with to acknowledge
acceptance of the current limit when in Drive mode. Commonly this is sent as a signed integer 16 bit
with units of 100mA giving +/- 3276.7 Amps range

ECU Alive Counter:

This is typical an incrementing single byte counter that increases with each message send and rolls
over from 255 to 0. This is required to provide a safety confirmation that the ECU is functioning as
expected and that the current limit data is valid.

Data Payload of Charger Acknowledge Message.

Typically 8 Bytes required on 1000mS cycle time for low voltage applications down to 50mS for high
voltage Applications.

Charger Status Flags:

Ideally this should be one byte containing the following flags Bit encoded; Hardware Fault, Over
Temperature Fault, Input Voltage Fault, Output Polarity Fault, Output Contactor State,
Communication Fault. Other fault and status flags can be added as required.

Charger Output Current:

Charger Measured output current typically signed integer 16 format with 100mA per bit scaling to
allow the BMS to compensate for charger calibration errors in its current set point. The signed
format of the current is to allow for interaction with bi-directional chargers. I.e. chargers with grid
tie inverter functionality.

Charger Output Voltage:

Charger Measured output voltage typically integer 16 format with 100mV per bit scaling to allow the
BMS to compensate for charger calibration errors in its Voltage set point.

Page 21 of 22
Charger Available Output Current:
Charger available output current typically signed integer 16 format with 100mA per bit scaling to
allow the BMS to fully utilise the available output from the charger to minimise the charging time.
This is especially useful for chargers that offer a constant power output.

Charger Counter:
This is typical an incrementing single byte counter that increases with each message send and rolls
over from 255 to 0. This is required to provide a safety confirmation that the Charger is functioning
as expected and that the measured current and voltage data is valid.

Page 22 of 22