KR102501640B1 - Distributed battery management system and method - Google Patents

Abstract

The present invention relates to a distributed battery management technology, and a distributed battery management system according to an aspect of the present invention is a distributed battery management system for managing a plurality of battery modules, each connected to the plurality of battery modules , a plurality of slave controllers for generating battery sensing information for connected battery modules; a master controller connected to the highest slave controller among the plurality of slave controllers and selectively connected to the lowest slave controller; And located between the master control unit and the lowest slave control unit, operating under the control of the master control unit to connect the master control unit and the lowest slave control unit or to release the connection between the master control unit and the lowest slave control unit. Including the conversion part.

Description

Distributed battery management system and method

The present invention relates to distributed battery management, and more particularly, to a distributed battery management system and method implemented to detect a slave controller in a communication-disabled state and monitor a battery using a slave controller capable of communication. will be.

In general, a battery management system refers to a battery management system for medium and large-sized secondary batteries used in electric vehicles, electric motorcycles, energy storage devices, etc. It has input/output and remaining amount control functions.

Here, the battery management system can be divided into an integral type and a distributed type. In particular, the distributed battery management system connects battery modules obtained by modularizing a certain number of tens to hundreds of batteries, which are the main power source, in series to each other, and each battery or battery By monitoring the module, it determines whether the battery or battery module is abnormal and controls the output of the main power.

At this time, the distributed battery management system includes a master controller and a plurality of slave controllers for battery monitoring and management. It is possible to minimize hardware resources.

Therefore, the remaining slave controllers except for the uppermost slave controller have only sensing ICs therein, and each sensor IC is serially connected to each other according to a daisy chain method.

1 shows the configuration of a conventional daisy-chain distributed battery management system. As shown in FIG. 1, the conventional distributed battery management system 100 includes a master controller 110 and a plurality of slave controllers 120 composed of two groups, and each slave controller 120 includes a battery module 130 ) are connected.

At this time, the plurality of slave controllers 120 are connected in a daisy chain structure, and the highest slave controller 120 (#1) to the lowest slave controller 120 (#n) are connected in series.

Meanwhile, each of the plurality of slave controllers 120 includes a sensing IC 121 , and the topmost slave controller 120 (#1) includes a microcontroller 122 . The slave controllers 120 are connected through a wire harness to transmit/receive data to each other.

Looking at the operation of the distributed battery management system 100 having the configuration shown in FIG. 1 , address information and command information of the slave control unit are transferred from the master control unit 110 to the microcontroller 122 of the highest slave control unit 120 (#1). transmits the same control information.

Then, the microcontroller 122 sequentially transmits control information from the highest sensing IC 121, #1 to the lowest sensing IC 121, #n, and each sensing IC 121, #1 to #n Information on the battery module 130 is sensed in response to the control information, and the sensing information is sequentially transferred from the lowest sensing IC 121 (#n) to the highest sensing IC 121 (#1), and the microcontroller 122 transmits the information on the battery module collected by the uppermost sensing IC 121 (#1) to the master controller 110.

In this way, when a specific slave controller or a specific communication line is damaged by external noise or physical pressure during communication in a daisy chain method, a problem occurs in that all slave controllers cannot sense the battery module.

This problem occurs due to the characteristics of sequentially receiving data from the lower slave controller and transmitting the data to the upper slave controller in a daisy chain structure.

In addition, when a failure occurs in any slave control unit, it is difficult to detect which slave control unit has failed because all slave control units do not communicate.

Therefore, the present invention has been made to solve the problems of the prior art as described above, and an object of the present invention is to detect a slave controller in a communication disabled state and to monitor a battery using a slave controller capable of communication. It is to provide a distributed battery management system and method implemented so as to be.

Distributed battery management system according to an aspect of the present invention for achieving the above object is a distributed battery management system for managing a plurality of battery modules, each connected to the plurality of battery modules, the connected battery modules A plurality of slave controllers for generating battery sensing information for; a master controller connected to the highest slave controller among the plurality of slave controllers and selectively connected to the lowest slave controller; And located between the master control unit and the lowest slave control unit, operating under the control of the master control unit to connect the master control unit and the lowest slave control unit or to release the connection between the master control unit and the lowest slave control unit. Including the conversion part.

In addition, a distributed battery management method according to another aspect of the present invention is a distributed battery management method for managing a plurality of battery modules based on battery sensing information transmitted from a slave controller connected to each of the plurality of battery modules, managing the plurality of battery modules while operating in a normal mode in which the battery sensing information is received through a first communication module connected to a top-level slave control unit; determining whether an abnormal slave control unit exists based on the battery sensing information; switching to a failure mode for receiving the battery sensing information through a second communication module connected to the first communication module and the lowest slave control unit when the abnormal slave control unit exists; and managing the plurality of battery modules while operating in the failure mode.

Conventionally, when a specific slave controller or a specific communication line is burnt out, all slave controllers fail to sense the battery module, and it is difficult to detect which slave controller is out of order.

However, according to the present invention, it is possible to detect a slave controller in a communication-disabled state, and battery sensing information can be obtained from a communicable slave controller other than the detected slave controller, so battery management is possible.

1 is a configuration diagram showing an example of a conventional daisy-chain distributed battery management system;
2 is a diagram showing an example of a distributed battery management system according to an embodiment of the present invention.
3 is a diagram showing the configuration of a distributed battery management system in a normal state according to an embodiment of the present invention.
4 is a diagram showing the configuration of a distributed battery management system in a fault state according to an embodiment of the present invention.
5 is a flowchart illustrating a process of detecting a slave control unit in a non-communicable state in a distributed battery management system according to an embodiment of the present invention.
6 is a flowchart illustrating communication line resetting and communication resumption operations in the distributed battery management system according to an embodiment of the present invention.
7 is a flowchart illustrating a sequence of battery management operations of the distributed battery management system according to an embodiment of the present invention.

Advantages and features of the present invention, and methods for achieving them, will become clear with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only the present embodiments make the disclosure of the present invention complete, and common knowledge in the art to which the present invention belongs It is provided to fully inform the holder of the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals designate like elements throughout the specification.

In describing the embodiments of the present invention, if it is determined that a detailed description of a known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. In addition, terms to be described below are terms defined in consideration of functions in the embodiments of the present invention, which may vary according to the intention or custom of a user or operator. Therefore, the definition should be made based on the contents throughout this specification.

Hereinafter, a distributed battery management system and management method according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

2 is a diagram showing an example of a distributed battery management system according to an embodiment of the present invention.

Referring to FIG. 2 , the distributed battery management system 200 (hereinafter, 'system') according to an embodiment of the present invention includes a master controller 210, a slave controller 230, a battery module 250, and a switching unit 270. Including, the configuration of the system 200 is not limited to the present embodiment, and may be implemented by further including other configurations in addition to the above-mentioned configurations.

The master controller 210 controls the overall system 200 using state information of the battery module 250 monitored by the slave controller 230 .

To this end, the master controller 210 includes first and second communication modules 213 and 215 that are in charge of communication with the control module 211 and the slave controller 230 .

The control module 211 is a component for controlling the system 200 by controlling the overall master controller 210 .

The control module 211 transmits control information including address information and command information of the slave control unit 230 to the slave control unit 230, and the battery module 250 transmitted from the slave control unit 230 in response to the control information. The system 200 is controlled using sensing information ('battery sensing information') for ).

At this time, the control module 211 uses only the first communication module 213 or both the first and second communication modules 215 for communication with the slave control unit 230 .

In addition, the control module 211 transmits a control signal to the conversion unit 270 according to the state of the system 200 .

At this time, when the system 200 is in a normal state, the control module 211 transmits a control signal ('normal operation control signal') for the switching unit 270 to operate in the normal mode to the switching unit 270. And, when the system 200 is in a failure state, a control signal ('failure operation control signal') is transmitted to the switching unit 270 to cause the switching unit 270 to operate in a failure mode.

Meanwhile, the control module 211 includes a plurality of terminals for communication, for example, terminals M_Tx and M_Rx for communication with the first communication module 213 and communication with the second communication module 215. It may include terminals for communication (FS_Tx, FS_Rx) and a terminal for transmitting a control signal to the conversion unit 270 (FS_Dout).

The first and second communication modules 213 and 215 are mediums for communication between the control module 211 and the slave control unit 230, and transmit control information transmitted from the control module 211 to the slave control unit 230. and transfers the battery sensing information transmitted from the slave controller 230 to the control module 211 .

At this time, the first and second communication modules 213 and 215 may encode control information transmitted from the control module 211 into an asynchronous differential signal and decode battery sensing information transmitted from the slave controller 230. can

On the other hand, the first communication module 213 is directly connected to the slave controller ('topmost slave controller') closest to the master controller 210 in a state in which the system 200 normally operates ('normal state').

And, the first communication module 213 operates both when the system 200 is in a normal state and when the system 200 is in a non-normal state ('failure state').

On the other hand, the second communication module 215 is directly connected to a slave control unit ('lowest slave control unit') located farthest from the master control unit 210 when the system 200 is in a normal state.

And, the second communication module 215 operates only when the system 200 is in a failure state, and the failure state of the system 200 means that, for example, a specific slave control unit or a specific communication line is affected by external noise or physical This means that it is damaged by phosphorus pressure.

That is, the master controller 210 communicates with the slave controller 230 using the first communication module 215 when the system 200 is in a normal state, and when the system 200 is in a failure state, the first And it communicates with the slave controller 230 using the second communication modules 213 and 215 .

Meanwhile, the first communication module 213 may include terminals C1_Rx1 and C1_Tx1 for communication with the control module 211 and terminals C1_Tx2 and C1_Rx2 for communication with the slave controller 230.

In addition, the second communication module 215 may include terminals C2_Rx1 and C2_Tx1 for communication with the control module 211 and terminals C2_Tx2 and C2_Rx2 for communication with the slave controller 230 .

Here, 'Tx' means an output terminal, 'Rx' means an input terminal, '1' means a terminal for communication with a device located at the front end ('front end device'), and '2' means a terminal for communication with a device located at the front end. It means a terminal for communication with a device located at the rear end ('back end device').

In addition, the front end and the rear end may be interpreted differently depending on the communication direction, but in the present invention, a device located close to the first communication module 213 of the master controller 210 based on the first communication module 213 is used as the front end. A device, and a device located far from the first communication module 213 is referred to as a rear end device.

The slave control unit 230 is provided in plurality and communicates with the master control unit 210 while being connected to each other by a daisy chain method.

*At this time, each slave control unit 230 includes a sensing module 231, and a battery module 250 is connected to each slave control unit 230. In detail, the battery module 250 is connected to the sensing module 231 .

That is, each of the plurality of slave controllers 230_1 to 230_n has sensing modules 231_1 to 231_n therein, and the plurality of battery modules 250_1 to 250_n are configured to control the plurality of slave controllers 230_1 to 230_n on a one-to-one basis. It is connected to the sensing modules 231_1 to 231_n.

The sensing module 231 of the slave controller 230 senses the battery module 250 according to the request of the master controller 210 to generate battery sensing information, and transmits the generated battery sensing information to the master controller 210. do.

At this time, the sensing module 231 senses the battery cell state of the battery module, and also senses the cell voltage, cell balancing, cell temperature, and cooling state of the battery cell.

Each of the sensing modules 231 includes a terminal for communicating with a device at a previous stage and a terminal for communicating with a device at a later stage.

For example, the sensing module 231_1 of the first slave controller 230_1 includes terminals B1_Rx1 and B1_Tx1 for communication with the master controller 210 positioned at the front end, and the second slave controller 230_2 positioned at the rear end. ) and terminals B1_Tx2 and B1_Rx2 for communication.

As another example, the sensing module 231_n_ of the n-th slave control unit 230_n includes terminals Bn_Rx1 and Bn_Tx1 for communication with the n-1st slave control unit 230_n-1 located at the front end and located at the rear end. and terminals (Bn_Tx2, Bn_Rx2) for communication with the second communication terminal 215 of the master control unit 210 for communication.

The battery module 250 is configured by modularizing a plurality of cells, and may be provided as an aggregate in which a plurality of cells are connected in series or parallel.

Since the battery module 250 is a common technology in the field of battery management, a detailed description of the battery module 250 will be omitted.

The switching unit 270 performs a switching operation under the control of the control module 211 of the master control unit 210, and is controlled according to a normal operation control signal and a failure operation control signal transmitted from the control module 211. .

Meanwhile, the switching unit 270 may include a first switching unit 271 and a second switching unit 273 .

The first switching unit 271 is provided for connection or disconnection between the master control unit 210 and the lowest slave control unit 230_n, and is turned off when a normal operation control signal is received, and is turned off when a failure operation control signal is received. When received, it turns on.

At this time, the first switching unit 271 may include a first switch element SW1 and a second switch element SW2.

The first switch element (SW1) is located between the output terminal (C2_Tx2) of the second communication module 215 and the input terminal (Bn_Rx2) of the lowest slave control unit 230_n, and turns off when a normal operation control signal is received. ) and turns on when receiving a failure operation control signal.

The second switch element SW2 is located between the input terminal C2_Rx2 of the second communication module 215 and the output terminal Bn_Tx2 of the lowest slave control unit 230_n, and turns off when a normal operation control signal is received. ) and turns on when receiving a failure operation control signal.

At this time, when the first and second switch elements SW1 and SW2 are turned on, the master controller 210 and the lowest slave controller 230_n are connected.

Conversely, when the first and second switch elements SW1 and SW2 are turned off, the connection between the master controller 210 and the lowest slave controller 230_n is released.

The second conversion unit 273 is configured to return a signal output from the lowest slave control unit 230_n to the lowest slave control unit 230_n.

At this time, the second switching unit 273 is composed of a third switch element SW3, and the third switch element SW3 is between the output terminal Bn_Tx2 and the input terminal Bn_Rx2 of the lowest slave control unit 230_n. , the signal output from the output terminal (Bn_Tx2) is input to the input terminal (Bn_Rx2).

At this time, the third switch element SW3 is turned on when a normal operation control signal is received and turned off when a failure operation control signal is received.

When the third switch element SW3 is turned on, the output terminal Bn_Tx2 and the input terminal Bn_Rx2 of the lowest slave controller 230_n are connected.

Conversely, when the third switch element SW3 is turned off, the connection between the output terminal Bn_Tx2 and the input terminal Bn_Rx2 of the lowest slave controller 230_n is disconnected.

In the above, the configuration of the distributed battery management system according to the embodiment of the present invention has been examined. Hereinafter, operations of the distributed battery management system according to an embodiment of the present invention in a normal state and a failure state will be described.

3 is a diagram showing the configuration of a distributed battery management system according to an embodiment of the present invention in a normal state.

Referring to FIG. 3, the operation of the distributed battery management system according to an embodiment of the present invention in a steady state will be described, but only configurations related to the operation of the system 200 in a steady state will be described in detail, and other configurations will be described. omit explanation.

Hereinafter, in order to describe the operation of the system 200 in a normal state, an example in which the system 200 includes four slave controllers 230_1 to 230_4 will be described.

As shown in FIG. 3, when the system 200 of the present invention operates in a normal state, the first switching unit 271 of the switching unit 270 is in an off state, and the second switching unit 271 ) is an on (0n) state. That is, the control module 211 is in a state of transmitting a normal operation control signal to the switching unit 270 .

Looking at the operation of the system 200 shown in FIG. 3 , the control module 211 transmits control information to the highest slave controller 230_1 through the first communication module 213 to obtain battery sensing information.

Then, the control information is sequentially transmitted from the highest slave control unit 230_1 to the lower slave control unit, and is finally transmitted to the lowest slave control unit 230_4.

Through this process, all the slave control units 230_1 to 230_4 receive control information, and each slave control unit 230_1 to 230_4 receiving the control information performs battery sensing for the battery modules 250_1 to 250_4 connected in a one-to-one correspondence. Information is generated, and the generated sensing information is transmitted to the master controller 210 .

Therefore, all of the battery sensing information individually generated by the plurality of slave controllers 230_1 to 230_4 is transmitted to the control module 211 through the first communication module 213, and based on the received battery sensing information, the control module ( 211 controls the system 200 as a whole.

Therefore, the control module 211 in the system 200 operating in a normal state uses only the first communication module 213 for communication with the slave control unit 230 and does not use the second communication module 215.

In this way, when the system 200 operates in a normal state, there is no slave controller in which a short has occurred between the corresponding input terminal and output terminal among the plurality of slave controllers 230_1 to 230_4.

4 is a diagram showing the configuration of a distributed battery management system in a fault state according to an embodiment of the present invention.

Referring to FIG. 4 , the operation of the distributed battery management system according to an embodiment of the present invention in a fault state will be described, but only components related to the operation of the system 200 will be described in detail, and descriptions of other components will be omitted. .

Hereinafter, to describe the operation of the system 200 in a failure state, it is assumed that the system 200 includes four slave controllers 230_1 to 230_4 and the second slave controller 230_2 is in a failure state.

Accordingly, input and output terminals B1_Rx1 and B1_Tx1 at the front end of the first slave control unit 230_1 located at the front end of the second slave control unit 230_2 are shorted to each other.

In addition, input/output terminals B3_Rx1 and B3_Tx1 at the front end of the third slave control unit 230_3 located at the rear end of the second slave control unit 230_2 are also shorted to each other.

Also, when the system 200 of the present invention operates in a failure state, the first switching unit 271 of the switching unit 270 is in an on state, and the second switching unit 271 is in an off state. That is, the control module 211 is in a state of transmitting a failure operation control signal to the switching unit 270 .

Looking at the operation of the system 200 shown in FIG. 4 , the control module 211 transmits control information to the highest slave controller 230_1 through the first communication module 213 to obtain battery sensing information.

In addition, the control module 211 transmits control information to the lowest slave control unit 230_4 through the second communication module 215 to obtain battery sensing information.

At this time, since the first switching unit 271 of the switching unit 270 is in an on state, the control module 211 can communicate with the lowest slave control unit 230_4.

That is, the control module 211 uses the first and second communication modules 213 and 215 to obtain battery sensing information.

Meanwhile, the input and output terminals B1_Rx1 and B1_Tx1 at the front end of the uppermost slave control unit 230_1 are shorted to each other, and communication with the second slave control unit 230_2 located at the next stage is disconnected. , control information cannot be delivered to the second slave control unit 230_2.

Also, upon receiving the control information, the top-level slave controller 230_1 generates battery sensing information for the first battery module 250_1 and transmits it to the master controller 210 .

In addition, upon receiving control information, the lowest slave controller 230_4 transmits the received control information to the third slave controller 230_3.

At this time, since the front-side input and output terminals B3_Rx1 and B3_Tx1 of the third slave control unit 230_3 are shorted to each other and communication with the second slave control unit 230_2 is disconnected, the second slave control unit 230_2 is disconnected. Control information cannot be transmitted to the controller 230_2.

Upon receiving the control information, the lowest slave controller 230_4 and the third slave controller 230_3 generate battery sensing information for the battery modules 250_4 and 250_3 connected to each other, and transmits the battery sensing information to the master controller 210 .

* As such, when the system 200 is in a failure state, the control module 211 communicates with the slave control unit using the first and second communication modules 213 and 215.

Therefore, in the prior art, the master controller could not obtain battery sensing information from not only the failed slave controller but also all slave controllers thereafter. It is possible.

In the above, the operation of the distributed battery management system according to an embodiment of the present invention in a normal state and a failure state has been examined. Hereinafter, a method for detecting a slave control unit in a communication disabled state in a distributed battery management system according to an embodiment of the present invention will be described.

5 is a flowchart illustrating a process of detecting a slave control unit in a communication disabled state in a distributed battery management system according to an embodiment of the present invention.

Referring to FIG. 5 , a method for detecting a slave control unit in a communication disabled state in a distributed battery management system according to an embodiment of the present invention will be described, but it is assumed that the system 200 is configured as shown in FIG. 2 .

First, the master controller 210 checks the communication state of the slave controller 230 (S500). For example, the master controller 210 may transmit control information to the slave controller 230 and then check the communication state of the slave controller 230 based on whether battery sensing information corresponding to the control information is received.

Based on the confirmation result according to step S500, the master control unit 210 determines whether there is a slave control unit ('abnormal slave control unit') in a communication-disabled state (S510). At this time, the master controller 210 may determine whether an abnormal slave controller exists based on whether battery sensing information for all battery modules 250_1 to 250_n in the system 200 is received.

As a result of the determination in step S510, if the master controller 210 determines that the abnormal slave controller does not exist (S510-No), the process of detecting the abnormal slave controller of the present invention ends.

In this case, the master controller 210 may determine that there is no abnormal slave controller when all battery sensing information is received.

Meanwhile, as a result of the determination in step S510, if the master controller 210 determines that there is an abnormal slave controller (S510-Yes), it detects which slave controller among the plurality of slave controllers 230_1 to 230_n is the abnormal slave controller. perform the action

Specifically, the master controller 210 shorts the input and output terminals Bn_Rx1 and Bn_Tx1 at the front end of the n-th slave controller 230_n (lowest slave controller) (S520). That is, the master controller 210 forcibly shorts the inside of the n-th slave controller 230_n.

Thereafter, the master controller 210 determines whether communication with the slave controller is normally performed (S530). As an example, the master controller 210 transmits control information to the slave controller 230 and determines whether all battery sensing information corresponding to the control information is received.

As a result of the determination according to step S530, if it is determined that communication is normally performed (S530-Yes), the master control unit 210 recognizes the upper slave control units of the short-circuited slave control unit as normal slave control units (S550), and replaces the short-circuited slave control unit with It is recognized as an abnormal slave (S560).

Accordingly, in this embodiment, the master controller 210 recognizes the upper slave controllers 230_1 to 230_n-1 of the n-th slave controller 230_n-1 as normal slave controllers, and the n-th slave controller 230_n is abnormal. It is recognized as a slave controller.

Meanwhile, as a result of the determination in step S530, if it is determined that communication is not normally performed (S530-No), the master control unit 210 releases the short circuit of the slave control unit, and inputs and outputs of the slave control unit of one level higher. The terminal is shorted (S560).

That is, the master control unit 210 releases the short circuit of the n-th slave control unit 230_n, and short-circuits the input and output terminals Bn-1_Rx1 and Bn-1_Tx1 at the front end of the n-1-th slave control unit 230_n-1. It does (S560).

As in step S560, in a state in which the inside of the slave control unit 230_n-1 at a higher stage is short-circuited, the master control unit 210 proceeds to step S530 to determine whether communication is normally performed.

* The master control unit 210 repeatedly performs steps S530 and S560 until it detects an abnormal slave control unit.

In the above, a method for detecting a slave control unit in a non-communicable state in a distributed battery management system according to an embodiment of the present invention has been described. Hereinafter, a process of resuming communication after detecting a slave unit controller in a communication disabled state in a distributed battery management system according to an embodiment of the present invention will be described.

6 is a flowchart illustrating communication line resetting and communication resumption operations in the distributed battery management system according to an embodiment of the present invention.

Referring to FIG. 6, an operation of resetting a communication line and resuming communication in a distributed battery management system according to an embodiment of the present invention will be described, taking a system having the configuration shown in FIG. 4 as an example, and a slave control unit in an abnormal state. ('Abnormal slave control unit') is detected and the subsequent process is initiated.

First, in a state where the abnormal slave control unit is detected, the master control unit 210 checks the location of the detected abnormal slave control unit (S600). That is, it is checked which slave control unit of the slave control units is an abnormal slave control unit, and in this embodiment, the second slave control unit 230_2 is an abnormal slave control unit.

Thereafter, the master control unit 210 transmits a failure operation control signal to the switching unit 270 to turn on the first switching unit 271 and turn off the second switching unit 273, The second communication module 215, which is a communication module for failure mode, and the lowest slave control unit 250_4 are connected (S610).

Thereafter, the master controller 210 shorts input and output terminals inside the slave controllers 230_1 and 230_3 located at the front and rear ends of the abnormal slave controller 230_2 to each other, so that the front end of the abnormal slave controller 230_2 And the connection between the slave controllers 230_1 and 230_3 located at the rear end and the abnormal slave controller 230_2 is disconnected (S620).

Therefore, the slave control unit 230_1 located at the front end of the abnormal slave control unit 230_2 is connected to the first communication module 213, which is a normal mode communication module, and the slave control unit located at the rear end of the abnormal slave control unit 230_2 ( 230_3 and 230_4) are connected to the second communication module 215, which is a communication module for failure mode.

At this time, input and output terminals B1_Rx1 and B1_Tx1 at the front end of the slave control unit 230_1 located at the front end of the abnormal slave control unit 230 are shorted to each other, and the slave control unit 230_2 is located at the rear end of the abnormal slave control unit 230_2. Input and output terminals B3_Rx1 and B3_Tx1 at the front end of the control unit 230_3 are shorted to each other.

After step S620, the master controller 210 transmits control information to the highest slave controller 230_1 through the first communication module 213, and the control information to the lowest slave controller 230_4 through the second communication module 215. is transmitted to request battery sensing information (S630).

At this time, the control information transmitted through the first communication module 213 is transmitted to all slave controllers positioned in front of the abnormal slave controller 230_2, and is transmitted to the highest slave controller 230_1 in this embodiment.

And, the control information transmitted through the second communication module 215 is transmitted to all slave controllers located at the rear end of the abnormal slave controller 230_2, and in this embodiment, the third slave controller 230_3 and the lowest slave controller It is transmitted to (230_4).

Accordingly, the control information is transmitted to all slave controllers 230_1, 230_3, and 230_4 except for the abnormal slave controller 230_2.

After step S630, the slave controllers 230_1, 230_3, and 230_4 that have received the control information sense the battery modules 250_1, 250_3, and 250_4 connected to them to generate battery sensing information and transmit it to the master controller 210 ( S640).

Then, the master controller 210 receives battery sensing information transmitted from the slave controllers 230_1, 230_3, and 230_4 through the first and second communication modules 213 and 215 (S650).

Accordingly, the master controller 210 can acquire battery sensing information from all other slave controllers 230_1, 230_3, and 230_4 except for the abnormal slave controller 230_2.

As described above, the process of resetting the communication line and resuming communication according to the embodiment of the present invention may be performed through steps S600 to S650. However, the following process may be further performed after step S650.

That is, after step S650, the master controller 210 checks the operating states of the slave controllers 230_1, 230_3, and 230_4 other than the abnormal slave controller 230_2 based on the received battery sensing information (S660).

At this time, based on the confirmation result according to step S660, the master controller 210 determines whether there is a slave controller operating abnormally (S670), and as a result of the determination, if there is a slave controller operating abnormally (S670-Yes) ), an abnormal slave control unit is detected (S680).

Meanwhile, as a result of the determination in step S670, when it is determined that there is no abnormally operating slave control unit (S670-No), the process of resuming communication according to an embodiment of the present invention is terminated.

In the above, the configuration of the distributed battery management system according to the embodiment of the present invention, the operation of the system according to the state, the method of detecting the abnormal slave control unit, and the method of resetting the communication line and resuming communication have been reviewed. Hereinafter, a battery management method of a distributed battery management system according to an embodiment of the present invention will be described.

7 is a flowchart illustrating a sequence according to a battery management operation of a distributed battery management system according to an embodiment of the present invention.

A battery management operation of the distributed battery management system according to an embodiment of the present invention will be described with reference to FIG. 7 , but initially, it is assumed that the system operates normally.

First, when the system 200 is in a normal state, the master module 210 manages the battery modules 250_1 to 250_n while operating in a normal mode (S700). In this case, the system 200 may be configured as shown in FIG. 3 as an example, but is not limited thereto.

Looking at the operation of the system 200 in step S700, the master controller 210 transmits control information to the slave controller 230, and the battery sensing information transmitted from the slave controller 230 in response to the control information. and manages the battery module based on the received battery sensing information.

At this time, the master controller 210 communicates with the slave controller 230 using the first communication module 213, the first switch 271 of the switch 270 is in an off state, and the switch The second switching unit 273 of 270 is in an on state.

Matters related to the operation of the system 200 in a steady state may be referred to the description of FIG. 3 , so detailed descriptions thereof are omitted.

Meanwhile, while operating in the normal mode, the master controller 210 determines whether there is an abnormal slave controller based on the received battery sensing information (S710).

At this time, the master controller 210 determines whether there is an abnormal slave controller based on whether all battery sensing information transmitted from the plurality of slave controllers 230 is received.

That is, if the master controller 210 receives all the battery sensing information transmitted from the plurality of slave controllers 230, it is determined that the abnormal slave controller does not exist, and if there is battery sensing information that has not been received, the abnormal slave controller exists. judge it to be

As a result of the determination in step S710, if it is determined that there is no abnormal slave control unit (S710-No), the master control unit 210 manages the battery module 250 while operating in a normal mode.

On the other hand, as a result of the determination in step S710, if it is determined that there is an abnormal slave control unit (S710-Yes), the master control unit 210 detects the abnormal slave control unit (S720).

Matters related to the detection of the abnormal slave controller may be referred to FIG. 5 and related detailed descriptions, and thus, a detailed description of the detection of the abnormal slave controller will be omitted.

Thereafter, the master controller 210 resets the communication line, operates in a failure mode (S730), and manages the battery module 250 based on the battery sensing information while operating in a failure mode (S740).

Meanwhile, the system 200 in step S740 may be configured as shown in FIG. 4 as an example, but is not limited thereto.

Looking at the operation of the system 200 in step S740, the master controller 210 receives battery sensing information while communicating with the slave controller using the first and second communication modules 213 and 215.

At this time, the first switching unit 271 of the switching unit 270 is in an on state, and the second switching unit 273 of the switching unit 270 is in an off state.

At this time, since matters related to resetting the communication line and operation in the failure mode can be referred to FIGS. 4 and 6 and detailed descriptions thereof, detailed descriptions of resetting the communication line and operation in the failure mode are omitted.

On the other hand, although the distributed battery management system and management method according to the present invention have been described according to embodiments, the scope of the present invention is not limited to specific embodiments, and will be apparent to those skilled in the art in relation to the present invention. Various alternatives, modifications, and changes can be implemented within the scope.

Therefore, the embodiments described in the present invention and the accompanying drawings are not intended to limit the technical idea of the present invention, but to explain, and the scope of the technical idea of the present invention is not limited by these embodiments and the accompanying drawings. . The protection scope of the present invention should be construed by the claims, and all technical ideas within the equivalent range should be construed as being included in the scope of the present invention.

200: battery management system 210: master control unit
211: control module 213: first communication module
215: second communication module 230: slave control unit
231: sensing module 250: battery module
270: conversion unit 271: first conversion unit
273: second conversion unit

Claims (11)

In a distributed battery management system that manages a plurality of battery modules,
a plurality of slave controllers respectively connected to the plurality of battery modules and generating battery sensing information for the connected battery modules;
a master controller connected to the highest slave controller among the plurality of slave controllers and selectively connected to the lowest slave controller; and
It is located between the master controller and the lowest slave controller, and operates under the control of the master controller to connect the master controller and the lowest slave controller or release the connection between the master controller and the lowest slave controller. including wealth,
The master controller determines whether an abnormal slave controller exists based on battery sensing information transmitted from the highest slave controller or the lowest slave controller, and if the abnormal slave controller exists, a first communication module connected to the top slave controller And converting to a failure mode in which the battery sensing information is received through a second communication module connected to the lowest slave control unit,
The distributed battery management system, characterized in that the master control unit detects the abnormal slave control unit by sequentially shorting the inside from the lowest slave control unit. The method of claim 1,
The master controller determines that the abnormal slave controller does not exist when all battery sensing information transmitted from the plurality of slave controllers is received, and determines that the abnormal slave controller exists if there is battery sensing information that has not been received. Distributed battery management system featuring. The method of claim 1,
Wherein the master controller receives battery sensing information transmitted from the plurality of slave controllers through the first communication module when all of the plurality of slave controllers are normally operating. delete The method of claim 1,
The master control unit sequentially shorts the inside from the lowest slave control unit, determines whether communication is normally performed, and recognizes the shorted slave control unit as an abnormal slave control unit when communication is normally performed Distributed battery management system. In the distributed battery management method for managing the plurality of battery modules based on battery sensing information transmitted from a slave control unit connected to each of the plurality of battery modules,
determining whether an abnormal slave control unit exists based on the battery sensing information;
switching to a failure mode for receiving the battery sensing information through a first communication module connected to the highest slave control unit and a second communication module connected to the lowest slave control unit when the abnormal slave control unit exists; and
When the abnormal slave control unit exists, detecting the abnormal slave control unit;
In the detecting of the abnormal slave control unit, the abnormal slave control unit is detected by sequentially short-circuiting an inside of the lowest slave control unit. The method of claim 6,
The determining step may include determining that the abnormal slave controller does not exist when all battery sensing information transmitted from the plurality of slave controllers is received, and determining that the abnormal slave controller exists if there is battery sensing information that has not been received. Distributed battery management method, characterized in that. The method according to claim 6, wherein the distributed battery management method,
Distributed battery management method, characterized in that performed by a master controller connected to the highest slave controller among the plurality of slave controllers and selectively connected to the lowest slave controller. The method of claim 8,
The switching to the failure mode may include controlling a switching unit located between the master controller and the lowest slave controller so that the master controller and the lowest slave controller are connected. delete The method of claim 6,
After the step of switching to the failure mode, if the abnormal slave control unit exists, detecting the abnormal slave control unit; further comprising;
In the step of detecting the abnormal slave control unit, the inside is sequentially shorted from the lowest slave control unit, and it is determined whether communication is normally performed, and when communication is normally performed, the shorted slave control unit is recognized as an abnormal slave control unit. How to take care of your battery.

Images