CN116980499A - BMS serial port data transmission method based on Modbus communication protocol - Google Patents
BMS serial port data transmission method based on Modbus communication protocol Download PDFInfo
- Publication number
- CN116980499A CN116980499A CN202311004017.XA CN202311004017A CN116980499A CN 116980499 A CN116980499 A CN 116980499A CN 202311004017 A CN202311004017 A CN 202311004017A CN 116980499 A CN116980499 A CN 116980499A
- Authority
- CN
- China
- Prior art keywords
- bms
- data
- communication protocol
- modbus communication
- register
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004891 communication Methods 0.000 title claims abstract description 58
- 238000000034 method Methods 0.000 title claims abstract description 22
- 230000005540 biological transmission Effects 0.000 title claims abstract description 18
- 230000004044 response Effects 0.000 claims abstract description 9
- 230000009471 action Effects 0.000 claims abstract description 7
- 238000012360 testing method Methods 0.000 claims description 8
- 238000004458 analytical method Methods 0.000 claims description 3
- 238000011084 recovery Methods 0.000 claims description 2
- 230000001960 triggered effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 239000000178 monomer Substances 0.000 description 2
- 102220032811 rs367543159 Human genes 0.000 description 2
- 102220092750 rs876657859 Human genes 0.000 description 2
- 238000005070 sampling Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H03—ELECTRONIC CIRCUITRY
- H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
- H03M13/00—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
- H03M13/03—Error detection or forward error correction by redundancy in data representation, i.e. code words containing more digits than the source words
- H03M13/05—Error detection or forward error correction by redundancy in data representation, i.e. code words containing more digits than the source words using block codes, i.e. a predetermined number of check bits joined to a predetermined number of information bits
- H03M13/09—Error detection only, e.g. using cyclic redundancy check [CRC] codes or single parity bit
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L2012/40208—Bus networks characterized by the use of a particular bus standard
- H04L2012/40228—Modbus
Abstract
The invention discloses a BMS serial port data transmission method based on a Modbus communication protocol, and belongs to the technical field of communication. The method comprises the following steps: the BMS terminal judges whether to respond to a request sent by an upper computer according to a MODBUS communication protocol, wherein the agreed baud rate of the MODBUS communication protocol is 9600 bits/second, the data bit of the MODBUS communication protocol is 8 bits, the stop bit of the MODBUS communication protocol is 1 bit, and the MODBUS communication protocol has no parity check bit; if the request sent by the upper computer is responded, the request is analyzed and corresponding response actions are made. The invention solves the data communication problem of the battery management system BMS under the Modbus communication protocol, and expands the functions and application scenes of the Modbus communication protocol.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a BMS serial port data transmission method based on a Modbus communication protocol.
Background
Traditional Modbus communication protocol does not have special data definition to battery management system BMS, can't realize the communication between BMS end and the server end (host computer) under the Modbus communication protocol, and then can't realize remote data transmission, show, configuration and the remote monitoring to battery operation state to BMS product under the Modbus communication protocol.
Therefore, how to provide a BMS serial data transmission method under the Modbus communication protocol is a problem that needs to be solved by those skilled in the art.
Disclosure of Invention
In view of the above, the invention provides a BMS serial port data transmission method based on a Modbus communication protocol, which is used for realizing data transmission between a BMS end and an upper computer under the Modbus communication protocol, and displaying and configuring BMS data.
In order to achieve the above purpose, the present invention adopts the following technical scheme:
a BMS serial port data transmission method based on Modbus communication protocol comprises the following steps:
the BMS terminal judges whether to respond to a request sent by an upper computer according to a MODBUS communication protocol, wherein the agreed baud rate of the MODBUS communication protocol is 9600 bits/second, the data bit of the MODBUS communication protocol is 8 bits, the stop bit of the MODBUS communication protocol is 1 bit, and the MODBUS communication protocol has no parity check bit;
if the request sent by the upper computer is responded, the request is analyzed and corresponding response actions are made.
Further, the MODBUS communication protocol adopts an RTU mode.
Further, the request sent by the upper computer includes:
slave address, function code, register address, read data length, and CRC check code;
the slave address corresponds to the BMS terminal;
the register address includes a register high-order address and a register low-order address.
Further, the function code includes,
a read register function code for reading single or multiple register data; write register function code for writing single register data;
test mode function codes for testing BMS functions;
the read charge-discharge FLASH cache data function code is used for reading the charge-discharge FLASH cache data of the read BMS;
a read alert history data function code for reading alert history data;
and a read charge and discharge operation data function code for reading the charge and discharge operation data of the BMS.
Further, the register address is composed of 2 bytes, and comprises two states of read-only and read-write, and different register addresses correspond to different register contents.
Further, the different register contents include a protection parameter, a protection delay parameter, a recovery parameter, and a BMS system parameter.
Further, in the request sent by the upper computer, the read data includes BMS voltage data, BMS current data, BMS temperature data, charging state data, alarm data and BMS charging and discharging operation data.
Further, responding to the request sent by the upper computer, the analyzing request specifically comprises the following steps:
s21, the BMS end receives request data sent by the upper computer, and obtains a frame identifier of the request data for analysis;
s22, reading a slave address, a function code and a register address corresponding to the frame identifier;
s23, judging whether the slave address is correct, if so, entering into a step S24;
s24, judging whether the function code is correct, if so, entering a step S25;
s25, judging whether the register address is correct, if so, entering into a step S26;
and S26, the BMS responds to corresponding read-write operation according to the identified function code.
Compared with the prior art, the BMS serial port data transmission method based on the Modbus communication protocol has the following beneficial effects:
the invention solves the data communication problem of the battery management system BMS under the Modbus communication protocol, and expands the functions and application scenes of the Modbus communication protocol.
Based on the invention, the data transmission of the battery running state and the historical state can be realized, and the battery problem can be positioned more accurately and more quickly.
Compared with the traditional Modbus communication protocol, the invention has more abundant functional instructions and improves the safety and application scene to a certain extent.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic overall flow chart of a method according to an embodiment of the present invention.
Fig. 2 is a schematic diagram of interaction between a BMS end and an upper computer according to an embodiment of the present invention.
Fig. 3 is a flow chart of a BMS end parsing request provided in an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
As shown in fig. 1, the embodiment of the invention discloses a BMS serial port data transmission method based on a Modbus communication protocol, which comprises the following steps:
the BMS terminal judges whether to respond to a request sent by an upper computer according to a MODBUS communication protocol, wherein the agreed baud rate of the MODBUS communication protocol is 9600 bits/second, the data bit of the MODBUS communication protocol is 8 bits, the stop bit of the MODBUS communication protocol is 1 bit, and the MODBUS communication protocol has no parity check bit;
if the request sent by the upper computer is responded, the request is analyzed and corresponding response actions are made.
As shown in fig. 2, in this embodiment, a battery management system BMS end and a user end are included, and a communication protocol between the BMS end and the user end adopts a MODBUS communication protocol.
The communication interfaces related in the embodiment all accord with the international standard of RS-232 and RS-485. The communication protocol adopts an RTU mode, namely the communication format refers to an RTU frame format, and the specific format of the RTU frame is shown in table 1.
Table 1 RTU frame format
Initial structure | Address code | Function code | Data area | Error checking | Ending structure |
Time of 4 bytes or more | 1 byte | 1 byte | N bytes | 16-bit CRC code | Time of 4 bytes or more |
The request sent by the upper computer in this embodiment includes:
slave address, function code, register address, read data length, and CRC check code; wherein the slave address corresponds to the BMS end, and once the product BMS determines that the slave address will not change; the register addresses include a register high-order address and a register low-order address.
In this embodiment, the master transmission request format and the slave response request format are shown in table 2.
Table 2 request format
The CRC check code is automatically generated and is only used for judging whether the data has errors or not, and if so, error correction is carried out.
In this embodiment, the function code is composed of 1 byte, and provides a read-write function, and the specific function is shown in table 3.
Table 3 function code function table
Function code | Function of | Description of the invention |
0x03 | Reading registers | For reading data of single or multiple registers |
0x06 | Write register | For writing data to a single register |
0x09 | Test mode | For testing BMS function |
0xAA | Reading bulk data | Is used for reading the charge and discharge operation data-FLASH |
0xDD | Reading bulk data | For reading alarm history data |
0xEE | Reading bulk data | For reading charge-discharge operation data |
In this embodiment, the register address is composed of 2 bytes, and the register content is read and written according to the register address, where the specific content of the register address is shown in table 4.
Table 4 register table of contents
When the test mode is entered, i.e. when the function code is "0x09", the register address correspondence will change, and the specific register contents are shown in table 5.
Table 5 table of test mode register contents
When the upper computer sends a request is a 01DD 010203040506 instruction, the alarm history data is read. After receiving the request, the BMS returns alarm history data. The return alarm history data start field is "ID DD 000102030405", wherein ID is the slave address; the end field of the returned alarm history data is 'ID DD 010203040506'; the specific meaning of the returned alert history data field is shown in table 6.
TABLE 6 alarm history data field meanings
In this embodiment, the alarm flag bit is composed of 2 bytes, that is, 16 bits, where each bit corresponds to a different alarm condition, and the specific content is shown in table 7.
TABLE 7 alarm flag definition
Wherein temp_e is in a temperature sampling state, OTWMos is MOS high temperature alarm, OTWBDSG is battery discharge high temperature alarm, OTWBCHG is battery charge high temperature alarm, OCWCHG is charge overcurrent alarm, OCWDSG is discharge overcurrent alarm. The mark positions 1 are abnormal, and the mark positions 0 are normal.
When BMS protection is triggered, this piece of data will also be saved to the alert history. The protection bit marks are divided into a protection bit mark 1 and a protection bit mark 2, wherein the protection bit mark 1 and the protection bit mark 2 are composed of 16 bits, and each bit corresponds to different protection conditions. The specific contents of the protection bit flag 1 are shown in table 8, and the specific contents of the protection bit flag 2 are shown in table 9.
Table 8 protection flag 1 definition
Bit16 | Bit15 | Bit14 | Bit13 | Bit12 | Bit11 | Bit10 | Bit9 |
UV | OV | OT_Bat | OT_Mos | UT_CHG | UT_DSG | OC_DSG | OC_CHG |
Bit8 | Bit7 | Bit6 | Bit5 | Bit4 | Bit3 | Bit2 | Bit1 |
SCD | POV | PUV | UV_T | OV_T | OCD_T | OC2_DSG | OC2_CHG |
Wherein UV is an under-voltage protection zone bit; OV is an overvoltage protection zone bit; OT_Bat is a battery over-temperature protection zone bit; OT_Mos is an MOS over-temperature protection zone bit; UT_CHG is a low-temperature charging protection flag bit; UT_DSG is a low-temperature discharge protection zone bit; OC_DSG is a discharge overcurrent protection zone bit; OC_CHG is a charging overcurrent protection zone bit; SCD is short-circuit protection zone bit; POV is the total voltage overvoltage flag bit; the PUV is a total voltage undervoltage flag bit; UV_T is a hardware undervoltage protection flag bit; OV_T is a hardware overvoltage protection flag bit; OCD_T is a hardware overcurrent protection zone bit; the OC 2-DSG is a diode discharge overcurrent protection zone bit; oc2_chg is a diode charge over-current protection flag bit. The mark positions 1 trigger protection, and the mark positions 0 are not triggered protection.
Table 9 protection flag bit 2 definition
Bit | Bit15 | Bit | Bit13 | Bit12 | Bit11 | Bit10 | Bit9 |
CHG | DSG | TEMP_E | |||||
Bit8 | Bit7 | Bit6 | Bit5 | Bit4 | Bit3 | Bit2 | Bit1 |
BAL | VDIFF |
Wherein CHG is the state of charge MOS, DSG is the state of discharge MOS, TEMP_E is the state of temperature sampling, BAL is the balanced open flag bit, VDIFF is the warning of excessive pressure difference. The mark positions 1 trigger protection, and the mark positions 0 are not triggered protection.
In the embodiment of the invention, when the upper computer sends a request of 01EE 010203040506 when the charge and discharge operation data is read, the charge and discharge operation data is read. And after the BMS receives the request, the BMS returns the charge and discharge operation data. The start field of the returned charge and discharge operation data is 'ID EE 0001020304 05', wherein the ID is the address of the slave; the return charge and discharge operation data end field is 'ID EE 0102030405 06'; the specific meaning of the return charge-discharge operation data field is shown in table 10.
TABLE 10 charge-discharge run data definition
When the charge and discharge FLASH cache data is read, the upper computer sends a '01AA 010203040506' instruction, namely the charge and discharge FLASH cache data is read. And after the BMS receives the request, returning the charge-discharge operation FLASH cache data. The starting field of the FLASH cache data of the charge and discharge operation is returned to be 'ID EE 000102030405', wherein the ID is the address of the slave; the end field of the FLASH cache data of the charge and discharge operation is returned to be 'ID EE 010203040506'; the specific meaning of the return charge-discharge operation FLASH cache data field is shown in table 11.
Table 11 charge-discharge run FLASH cache data definition
/>
In the embodiment of the invention, a request is sent from a user terminal to a BMS terminal to respond to the request, whether the BMS terminal makes a response request action is judged through the communication protocol, if the response request action is matched with the BMS terminal, the sending request of the user terminal is analyzed, and the BMS terminal makes a corresponding response action.
As shown in fig. 3, a flow chart of the BMS end analyzing data, where a specific BMS end responds to a request sent by an upper computer, and the analyzing request includes the following steps:
s21, the BMS end receives request data sent by the upper computer, and obtains a frame identifier of the request data for analysis;
s22, reading a slave address, a function code and a register address corresponding to the frame identifier;
s23, judging whether the slave address is correct, if so, entering into a step S24;
s24, judging whether the function code is correct, if so, entering a step S25;
s25, judging whether the register address is correct, if so, entering into a step S26;
and S26, the BMS responds to corresponding read-write operation according to the identified function code.
The following further explains the process of sending the analytic data of the present invention
In the data analysis example, the addresses of the slaves are 55H, the upper computer is a sending request user terminal, and the product BMS is a response request terminal, namely the slaves.
1) Reading single register contents
The upper computer sends a request of 55H 03H 00H 03H 00H 01H 79H DEH. "55H" is the slave address; "03H" is the function code, and the function code function table of Table 3 indicates that the request is to read the content of the register; "00H 03H" is the register address, and the table of contents of the table look-up 4 registers indicates that the content of the request read is the total voltage; "00H 01H" is the number of registers, converted into decimal 1, referring to 1 register; "79H DEH" is automatically generated for the CRC check code.
If the read register is successful, the BMS responds to the request as "55H 03H 02H 00H6BH C8H 67H". "55H 03H" is consistent with the meaning of the send request field; "02H" refers to return data of 2 bytes; "00H6BH" refers to data content converted to decimal 107, representing a total voltage of 10.7V; "C8H 67H" is automatically generated for the CRC check code.
If the read register is in error, the BMS responds to the request as "55H 83H 40H CRCLo CRCHi". "55H" is the slave address; "83H" is a function code; "40H" is an error code, indicating an invalid data address; "CRCLo CRCHi" is automatically generated for the CRC check code.
2) Reading multiple register contents
The upper computer sends a request of 55H 03H 00H 04H 00H 02H 88H 1EH. "55H 03H" is as above; "00H 04H" is a register address; "00H 02H" is the number of read registers; "88H 1EH" is automatically generated for the CRC check code. The request is to read the contents of register addresses from 0004H to 0005H, specifically, the total current and the residual power are read; "88H 1EH" is automatically generated for the CRC check code.
If the read register is successful, the BMS responds to the request as "55H 03H 04H FFH 9CH 00H1EH 9FH C4H". "55H 03H" is as above; "04H" means that the return data is 4 bytes; "FFH 9CH" refers to the first data value converted to a signed decimal of-100, representing a total current of-10A; "00H1EH" refers to the second data value, converted to decimal 30, representing a remaining capacity (SOC) of 30%; "9FH C4H" is automatically generated for the CRC check code.
If the read register is in error, the BMS responds to the request by reading the contents of the single register.
3) Data write register
The upper computer sends a request of 55H 06H 00H 07H 00H 01H CRCLo CRCHi. This command refers to changing the number of cycles to 1; "CRCLo CRCHi" is automatically generated for the CRC check code.
If the data writing into the register is successful, the BMS responds that the request is '55H 06H 00H 07H 00H 01HCRCLo CRCHi' and the sending request is completely consistent.
If the data write to the register fails, the BMS responds to the request as "55H 86H 40H CRCLo CRCHi". "55H" is the slave address; "86H" is a function code; "41H" is an error code, indicating invalid data; "CRCLo CRCHi" is automatically generated for the CRC check code.
4) Reading alert history data
The upper computer sends a request of 55HDDH 01H 02H 03H 04H 05H 06H. The request format is fixed and cannot be changed.
The BMS responds to the request, returning the data format as follows:
{
01DD 000102030405
AA 552D 13091B 0A 011000010000000055FE 8D 0D 560C F10D 4E 0C E70D 520C F00D 530C E7 FF AD FE ED FE ED FF BB FF B700270027FD 32
01DD 010203040506
}
"01DD 000102030405" means that the data starts without specific meaning.
"AA 552D 13091B 0A 011000010000000055FE 8D 0D 560CF10D 4E 0C E70D 520C F00D 530C E7 FF AD FE ED FE ED FF BB FF B700270027FD 32" look up table 6 alarm history data field meaning, table 7 alarm flag bit definition, table 8 protection bit flag 1 definition, table 9 protection bit flag 2 definition. The data is 45 bytes in total, meaning that 1 minute 16 seconds at 10 days of 2019 and 9 months trigger discharge overcurrent alarm, discharge MOS is closed, SOC is 85%, total current is-37.1A, 1 st string voltage is 3414mV, 2 nd string voltage is 3313mV, 3 rd string voltage 3406mV, 4 th string voltage 3299mV, 5 th string voltage 3410mV, 6 th string voltage 3312mV, 7 th string voltage 3411mV, 8 th string voltage 3303mV, temperature 1 is-83 ℃, temperature 2 is-275 ℃, temperature 3 is-275 ℃, temperature 4 is-69 ℃, temperature 5 is-73 ℃, temperature 6 is 39 ℃, temperature 7 is 39 ℃, and if the temperature is-275 ℃, the temperature indicates that the temperature sensor is not connected, CRC check code is FD 32.
"01DD 010203040506" means that the data ends without any specific meaning.
5) Reading charge-discharge operation data
The upper computer sends a request of 55H EEH 01H 02H 03H 04H 05H 06H. The request format is fixed and cannot be changed.
The BMS responds to the request, returning the data format as follows:
{
01EE 000102030405
AA 551C 0006170B 301902000080004C 01D7006400640C7E 0B A3001900130023AD 94
01EE 010203040506
}
"01EE 000102030405" means that the data starts without specific meaning.
"AA 551C 0006170B 301902000080004C 01D7006400640C 7E 0B A3001900130023AD 94" look-up table 8 protection bit flag 1 definition, table 9 protection bit flag 2 definition, table 10 charge and discharge operation data definition. The data is 28 bytes in total, meaning that the MOS is turned on during charging in the middle of 30 minutes and 25 seconds at the time of 11 days of 6 months and 23 years of 2000, the SOC is 76%, the total voltage is 47.1V, the real-time current is 10A, the maximum current is 10A, the highest voltage of a single body is 3198mV, the lowest voltage of the single body is 2979mV, the highest temperature of a battery is 25 ℃, the lowest temperature of the battery is 19 ℃, the highest temperature of the MOS is 35 ℃, and the CRC check code is AD 94.
"01EE 010203040506" means that the data ends without any specific meaning.
6) Reading FLASH cache data of charge-discharge operation
The upper computer sends a request of 55H AAH 01H 02H 03H 04H 05H 06H. The request format is fixed and cannot be changed.
The BMS responds to the request, returning the data format as follows:
{
01AA 000102030405
AA 551C 17050F 110C 2D 02000080006001D7006C 006D 0C800B A3001E 001300190C 220C 2A 0B B70C 800B A30C 080B F40B B875 E4
01AA 010203040506
}
"01AA 000102030405" means that the data starts without specific meaning.
"AA 551C 17050F 110C 2D 02000080006001D7006C 006D0C 800B A3001E 001300190C 220C 2A 0B B70C 800B A30C 080BF40B B875 E4" look-up table 8 protection bit flag 1 definition, table 9 protection bit flag 2 definition, and table 11 charge-discharge operation FLASH cache data definition. The total data is 28 bytes, meaning that during the 12 minutes 45 seconds of charge and discharge at the time of 17 days of 2023, 5 and 15, a charge MOS tube is opened, the SOC is 96 percent, the total voltage is 47.1V, the real-time current is 10.8A, the maximum current is 10.9A, the highest monomer voltage is 3200mV, the lowest monomer voltage is 2979mV, the highest cell temperature is 30 ℃, the lowest cell temperature is 19 ℃, the MOS highest temperature is 25 ℃, the 1 st string voltage is 3106mV, the 2 nd string voltage is 3114mV, the 3 rd string voltage is 2999mV, the 4 th string voltage is 3200mV, the 5 th string voltage is 2979mV, the 6 th string voltage is 3080mV, the 7 th string voltage is 3060mV, the 8 th string voltage is 300 mV, and the CRC check code is 75E4"
"01AA 010203040506" means that the data ends without any specific meaning.
In the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, and identical and similar parts between the embodiments are all enough to refer to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (8)
1. The BMS serial port data transmission method based on the Modbus communication protocol is characterized by comprising the following steps of:
the BMS terminal judges whether to respond to a request sent by an upper computer according to a MODBUS communication protocol, wherein the agreed baud rate of the MODBUS communication protocol is 9600 bits/second, the data bit of the MODBUS communication protocol is 8 bits, the stop bit of the MODBUS communication protocol is 1 bit, and the MODBUS communication protocol has no parity check bit;
if the request sent by the upper computer is responded, the request is analyzed and corresponding response actions are made.
2. The Modbus communication protocol-based BMS serial data transmission method according to claim 1, wherein the Modbus communication protocol adopts an RTU mode.
3. The Modbus communication protocol-based BMS serial data transmission method of claim 1, wherein the request sent by the upper computer comprises:
slave address, function code, register address, read data length, and CRC check code;
the slave address corresponds to the BMS terminal;
the register address includes a register high-order address and a register low-order address.
4. The method for transmitting data to the BMS serial port based on the Modbus communication protocol of claim 3, wherein the function code comprises,
a read register function code for reading single or multiple register data; write register function code for writing single register data;
test mode function codes for testing BMS functions;
the read charge-discharge FLASH cache data function code is used for reading the charge-discharge FLASH cache data of the read BMS;
a read alert history data function code for reading alert history data;
and a read charge and discharge operation data function code for reading the charge and discharge operation data of the BMS.
5. The method for transmitting BMS serial data according to claim 3, wherein said register address is composed of 2 bytes, including read-only and read-write states, and different register addresses correspond to different register contents.
6. The Modbus communication protocol based BMS serial data transmission method of claim 5, wherein the different register contents comprise a protection parameter, a protection delay parameter, a recovery parameter, and a BMS system parameter.
7. The method for transmitting BMS serial data based on Modbus communication protocol according to claim 3, wherein the read data comprise BMS voltage data, BMS current data, BMS temperature data, charge status data, alarm data and BMS charge and discharge operation data in the request sent by the upper computer.
8. The BMS serial data transmission method based on the Modbus communication protocol according to claim 1, wherein responding to the request sent by the host computer, analyzing the request specifically comprises the following steps:
s21, the BMS end receives request data sent by the upper computer, and obtains a frame identifier of the request data for analysis;
s22, reading a slave address, a function code and a register address corresponding to the frame identifier;
s23, judging whether the slave address is correct, if so, entering into a step S24;
s24, judging whether the function code is correct, if so, entering a step S25;
s25, judging whether the register address is correct, if so, entering into a step S26;
and S26, the BMS responds to corresponding read-write operation according to the identified function code.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202311004017.XA CN116980499A (en) | 2023-08-10 | 2023-08-10 | BMS serial port data transmission method based on Modbus communication protocol |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202311004017.XA CN116980499A (en) | 2023-08-10 | 2023-08-10 | BMS serial port data transmission method based on Modbus communication protocol |
Publications (1)
Publication Number | Publication Date |
---|---|
CN116980499A true CN116980499A (en) | 2023-10-31 |
Family
ID=88473021
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202311004017.XA Pending CN116980499A (en) | 2023-08-10 | 2023-08-10 | BMS serial port data transmission method based on Modbus communication protocol |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN116980499A (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112362983A (en) * | 2020-10-10 | 2021-02-12 | 东风时代(武汉)电池系统有限公司 | Battery management system diagnosis method, upper computer and system |
CN112436970A (en) * | 2020-11-24 | 2021-03-02 | 深圳市易优电气有限公司 | Communication method, equipment slave machine, building equipment management system and storage medium |
CN114025032A (en) * | 2022-01-06 | 2022-02-08 | 深圳市聚能优电科技有限公司 | Transmission protocol method, system, equipment and storage medium of EMS and BMS |
CN218352516U (en) * | 2022-09-28 | 2023-01-20 | 北京市轨道交通运营管理有限公司 | ModbusRTU test system |
CN115665018A (en) * | 2022-10-20 | 2023-01-31 | 上海果下科技有限公司 | Universal energy storage BMS protocol configurable debugging device and method |
-
2023
- 2023-08-10 CN CN202311004017.XA patent/CN116980499A/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112362983A (en) * | 2020-10-10 | 2021-02-12 | 东风时代(武汉)电池系统有限公司 | Battery management system diagnosis method, upper computer and system |
CN112436970A (en) * | 2020-11-24 | 2021-03-02 | 深圳市易优电气有限公司 | Communication method, equipment slave machine, building equipment management system and storage medium |
CN114025032A (en) * | 2022-01-06 | 2022-02-08 | 深圳市聚能优电科技有限公司 | Transmission protocol method, system, equipment and storage medium of EMS and BMS |
CN218352516U (en) * | 2022-09-28 | 2023-01-20 | 北京市轨道交通运营管理有限公司 | ModbusRTU test system |
CN115665018A (en) * | 2022-10-20 | 2023-01-31 | 上海果下科技有限公司 | Universal energy storage BMS protocol configurable debugging device and method |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10404083B2 (en) | Quick charging method, power adapter and mobile terminal, bidirectional communication using USB interface | |
CN111124986B (en) | Asynchronous serial port communication protocol compatible with Modbus and high in efficiency | |
CN103677671A (en) | Data reading-writing method and system of electrical port module | |
US11899068B2 (en) | Battery life extension via changes in transmission rates | |
CN113297865B (en) | Switch cabinet data management method based on RFID temperature label | |
CN102830680A (en) | Remote monitoring controller for hybrid power vehicle | |
CN204101707U (en) | The multi-section lithium ion battery tension temperature real-time detecting system of radio communication | |
CN113993002A (en) | Cable monitoring data reporting method and device | |
CN103778772A (en) | Framing and interconnection transmitting method in electricity utilization information collecting system | |
CN116980499A (en) | BMS serial port data transmission method based on Modbus communication protocol | |
CN102361104B (en) | Battery and battery identification circuit | |
CN206479188U (en) | Multi-turn modular converter and encoder | |
CN102881146A (en) | Industrial on-site equipment data acquirer of multiple industrial buses | |
US11293779B2 (en) | Battery life extension via changes in message size | |
CN203117961U (en) | Dead halt monitoring and resetting device | |
CN204178538U (en) | A kind of Intelliqent Temperature Monitoring System | |
CN117014525B (en) | Data communication method used between BMS (battery management system) end and server | |
CN111770105B (en) | Multi-protocol self-adaptive electricity meter data acquisition method | |
CN202871076U (en) | Industrial field equipment data collector for multiple industrial buses | |
CN113127063B (en) | Operation circuit and control method | |
WO2024001105A1 (en) | Communication detection method and apparatus, device, system, and storage medium | |
CN117527474A (en) | Unified communication method for intelligent electric power instrument and intelligent fusion terminal | |
CN213632485U (en) | Acquisition system of capacitive torque sensor | |
CN103049347A (en) | Computer crash monitoring and resetting device | |
EP4283893A1 (en) | Data processing method, device, and data transmission system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |