Scribd
Upload
65 views11 pages

Munication Datasheet-V2 0

The document outlines the BMS CAN2.0 communication protocol, detailing specifications for communication with chargers and battery status information. It includes various message IDs, data formats, and scales for battery parameters such as voltage, current, temperature, and state of charge. The protocol follows the SJ1939 specification and allows for configurable communication speeds.

Uploaded by

Lucas M
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
65 views11 pages

Munication Datasheet-V2 0

The document outlines the BMS CAN2.0 communication protocol, detailing specifications for communication with chargers and battery status information. It includes various message IDs, data formats, and scales for battery parameters such as voltage, current, temperature, and state of charge. The protocol follows the SJ1939 specification and allows for configurable communication speeds.

Uploaded by

Lucas M
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

BMS CAN2.

0 communication protocol

Coding by QUCC BMS


Version 1.0

2021-04-19
Catalog

1 Communication specification ............................................................................................................... 2

2 Address and data format description ................................................................................................ 2

2.1 Communication with charger ............................................................................................................... 2

2.2 battery status information ................................................................................................................... 3

2.2.1 ID: 0x02018100............................................................................................................................. 3

2.2.2 ID: 0x02028100............................................................................................................................. 4

2.2.3 ID: 0x02038100............................................................................................................................. 5

2.2.4 ID: 0x02048100............................................................................................................................. 6

2.2.5 ID: 0x02058100............................................................................................................................. 7

2.3 Battery temperature status .................................................................................................................. 8

2.3.1 ID: 0x02068100............................................................................................................................. 8

2.4 Battery voltage status .......................................................................................................................... 9

2.4.1 ID：0x02108100........................................................................................................................... 9
1 Communication specification

CAN Type：CAN2.0 (Extended)

BPS:125Kbps 250kbps 500Kbps(Configurable)


Data Length: 8
Data Encoded Format:Motorola

Follow: SJ1939 Protocol Specification

Note: Customers can also provide agreement definitions for secondary development

2 Address and data format description

2.1 Communication with charger

2.1.1 ID：0x1806E5F4
Sender:BMS Receiver:ECU Can Type:Extended Period:100ms

ID

2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0

CODE = 18 FID = 0x06 Source Address Destination Address

Data Length

8 Byte

Data

BYTE Name Scale Offset Example

1 Charger output voltage（data_h）

0.1V 0V 290=29.0V
2 Charger output voltage（data_l）

3 Charger output current(data_h)

0.1A 0A 1000=100.0A
4 Charger output current(data_l)
5 Control charger output 0：Enable 1：Disable

6 Reserved

7 Reserved

8 Reserved

2.2 battery status information

2.2.1 ID: 0x02018100


Sender:BMS Receiver:ECU Can Type:Extended Period:100ms

ID

2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0

CODE = 02 FID = 0x01 Source Address Destination Address

Data Length

8 Byte

Data

BYTE Name Scale Offset Example

1 Total voltage（data_h）

0.01V 0V 2656=26.56V
2 Total voltage（data_L）

3 Current（data_h）

0.1A 1000A 10200=20.0A


4 Current（data_L）

5 SOC（data_h）

1% 0% 80=80%
6 SOC（data_L）

7 Full capacity（data_h）
0.01AH 0AH 10000=100.00AH
8 Full capacity （data_l）

2.2.2 ID: 0x02028100

Sender:BMS Receiver:ECU Can Type:Extended Period:100ms

ID

2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0

CODE = 02 FID = 0x02 Source Address Destination Address

Data Length

8 Byte

Data

BYTE Name Scale Offset Example

1 SOH（data_h）

1% 0% 100=100%
2 SOH（data_l）

3 Running Times （data_h）

hour 0 500=500h
4 Running Times （data_l）

5 Cycles Times（data_h）

0 1000=1000
6 Cycles Times（data_L）
7 Reserved

8 Reserved

2.2.3 ID: 0x02038100

Sender:BMS Receiver:ECU Can Type:Extended Period:100ms

ID

2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0

CODE = 02 FID = 0x03 Source Address Destination Address

Data Length

8 Byte

Data

BYTE Name Scale Offset Example

1 PackStatus(DATA_H)

Bit PackStatus
2 PackStatus(DATA_L)

3 Protection reason(DATA_H)

Bit PROTECT
4 Protection reason(DATA_L)

5 Reserved

/ /
6 Reserved

7 Reserved

8 Reserved
PROTECT:

Bit 7 6 5 4 3 2 1 0

H NC NC NC NC NC UT ot uv

L ov tuv tov doc coc NC NC NC

PackStatus:

Bit 7 6 5 4 3 2 1 0
H NC NC NC NC NC NC NC NC

L CHARING DISCHARING NC NC NC NC CH_EN DIS_EN

2.2.4 ID: 0x02048100

Sender:BMS Receiver:ECU Can Type:Extended Period:100ms

ID

28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3

CODE = 02 FID = 0x04 Source Address Destination Address

Data Length

8 Byte

Data

BYTE Name Scale Offset Example

1 Vmax(data_h)

1mV 0mV 3520=3520mV


2 Vmax(data_l)

3 Vmin(data_h)
1mV 0mV 3550=3550mV
4 Vmin(data_l)

5 Vmax_Number 1 0 05=5

6 Vmin_Number 1 0 01=1

7 Reserved

8 Reserved

2.2.5 ID: 0x02058100

Sender:BMS Receiver:ECU Can Type:Extended Period:100ms

ID

2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0

CODE = 02 FID = 0x05 Source Address Destination Address

Data Length

8 Byte

Data

BYTE Name Scale Offset Example

1 Maximum temperature

0.1℃ 40℃ 755=35.5℃


2 Maximum temperature

3 Minimum temperature

0.1℃ 40℃ 696=29.6℃


4 Minimum temperature

5 Reserved

6 Reserved

7 Reserved

8 Reserved
2.3 Battery temperature status

2.3.1 ID: 0x02068100

Sender:BMS Receiver:ECU Can Type:Extended Period:100ms

ID

2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0

CODE = 02 FID = 0x06 Source Address Destination Address

Data Length

8 Byte

Data

BYTE Name Scale Offset Example

1 T1

0.1℃ 40℃ 782=38.2℃


2 T1

3 T2

0.1℃ 40℃ 681=28.1℃


4 T2

5 T3

0.1℃ 40℃ 653=25.3℃


6 T3

7 Reserved

8 Reserved
2.4 Battery voltage status

2.4.1 ID：0x02108100

Sender:BMS Receiver:ECU Can Type:Extended Period:100

ID

28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2

CODE = 02 FID = 0x10 Source Address Destination Address

Data Length

8 Byte

Data

BYTE Name Scale Offset Example

1 Vcell_1 Voltage (data_h)

1mV 0mV 3551=3551mV


2 Vcell_1 Voltage (data_l)

3 Vcell_2 Voltage (data_h)

1mV 0mV 3552=3552mV


4 Vcell_2 Voltage (data_l)

5 Vcell_3 Voltage (data_h)

1mV 0mV 3553=3553mV


6 Vcell_3 Voltage (data_l)

7 Vcell_4 Voltage (data_h)

1mV 0mV 3551=3551mV


8 Vcell_4 Voltage (data_l)

Increment by frame ID address:


0x02118100: Vcell_5---Vcel8;

0x02128100: Vcell_9---Vcel12;

………

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy