U.S. patent application number 14/335007 was filed with the patent office on 2014-11-06 for battery control system and battery control method.
The applicant listed for this patent is Hitachi, Ltd.. Invention is credited to Motoo FUTAMI, Kenji TAKEDA, Takeshi UCHIDA, Shin YAMAUCHI, Kouichi YOKOURA.
Application Number | 20140327403 14/335007 |
Document ID | / |
Family ID | 62043967 |
Filed Date | 2014-11-06 |
United States Patent
Application |
20140327403 |
Kind Code |
A1 |
YOKOURA; Kouichi ; et
al. |
November 6, 2014 |
Battery Control System and Battery Control Method
Abstract
When detecting a fault of a master control device, a slave
control device refers to master-device-line information, and
obtains line information to establish a connection with the other
master control device. The slave control device transmits
connection request information to the master control device
extracted from the other master control devices. The other master
control device determines whether or not it is connectable with the
slave control device that has transmitted the connection request
information, and transmits a determination result as connectability
information. The slave control device switches a communication line
to the other master control device when the received connectability
information indicates the connectable status.
Inventors: |
YOKOURA; Kouichi; (Kawasaki,
JP) ; FUTAMI; Motoo; (Hitachiota, JP) ;
TAKEDA; Kenji; (Mito, JP) ; YAMAUCHI; Shin;
(Mito, JP) ; UCHIDA; Takeshi; (Kasukabe,
JP) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Hitachi, Ltd. |
Tokyo |
|
JP |
|
|
Family ID: |
62043967 |
Appl. No.: |
14/335007 |
Filed: |
July 18, 2014 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
13408017 |
Feb 29, 2012 |
8816640 |
|
|
14335007 |
|
|
|
|
Current U.S.
Class: |
320/128 |
Current CPC
Class: |
H02J 7/0021 20130101;
H01M 10/441 20130101; H01M 10/4207 20130101; H01M 10/4257 20130101;
Y02E 60/10 20130101 |
Class at
Publication: |
320/128 |
International
Class: |
H02J 7/00 20060101
H02J007/00 |
Foreign Application Data
Date |
Code |
Application Number |
Mar 1, 2011 |
JP |
2011-044039 |
Claims
1. A method for controlling a battery system, the battery system
comprising: a plurality of battery modules, each of which has a
battery and a slave control device; a master control device
connected to the plurality of slave control devices via a first
communication line; and a battery system managing device connected
to the plurality of master control devices via a second
communication line, wherein the slave control devices configure a
string for battery modules connected in series, and wherein if the
master control device to which the slave control device is
connected suffers a fault, the slave control device and other slave
control devices belonging to the same string are connected to the
same other master control device.
2. The method of claim 1, wherein the master control device
determines whether or not the master control device is connectable
to all of the slave control devices belonging to the same string,
and if connectable, the master control device is connected to all
of the slave control devices belonging to the same string.
3. The method of claim 1, wherein the master control device
determines whether or not the master control device is connectable
to all of the slave control devices belonging to the same string,
and if not connectable, the slave control device searches other
connectable master control device.
4. The method of claim 2, wherein the master control device
determines whether or not the master control device is connectable
to all of the slave control devices belonging to the same string,
and if not connectable, the slave control device searches other
connectable master control device.
Description
CROSS REFERENCE TO RELATED APPLICATION
[0001] This application is a divisional of U.S. application Ser.
No. 13/408,017, filed Feb. 29, 2012, which claims priority from
Japanese Patent Application No. 2011-044039 filed on Mar. 1, 2011,
the disclosures of which are expressly incorporated by reference
herein.
BACKGROUND OF THE INVENTION
[0002] 1. Field of the Invention
[0003] The present invention relates to a battery control system
and a battery control method which dispose, as a hierarchical
structure, control devices that control batteries.
[0004] 2. Description of the Related Art
[0005] A technology of charging a battery with power generated by
utilizing natural energy and with power from a system is getting
attention. A battery control system realized by such a technology
has, as shown in FIG. 9, slave control devices 93 controlling a
battery and connected in series or in parallel as a group, and a
master control device 92 comprehensively controls such a group of
the slave control devices 93. Moreover, a whole group of the
plurality of master control devices 92 is managed by a
battery-system managing device 91, and thus a large-capacity
battery is realized. In the battery control system having master
and slave control systems as a hierarchical structure, the
battery-system managing device 91 transmits a control signal to
instruct charging, discharging, etc., of the battery to each slave
control device 93 through the master control device 92, and manages
a status of a communication line for transmitting/receiving the
control signal and the operation status of the control device
itself (see JP 2000-358330 A).
[0006] According to the conventional battery control system shown
in FIG. 9, however, when the master control device 92 suffers a
fault like a breakdown, a communication with the slave control
devices 93 managed by that master control device 92 is disabled,
and a battery charging/discharging control is also disabled even if
the battery controlled by that master and slave control devices 92
and 93 is in a normal condition.
[0007] For example, in the example case shown in FIG. 9, when a
fault occurs at the master control device 92 (92A), the slave
control devices 93 ((1) to (8)) under the control of such a master
control device become unable to control the battery since a
communication is disabled between the master control device 92 and
each slave control device 93.
[0008] The present invention has been made in view of such a
circumstance, and it is an object of the present invention to
provide a battery control system and a battery control method that
can avoid uncontrollability of a battery by slave control devices
when a master control device suffers a fault in a system which
establishes a hierarchical structure of the master control system
and the slave control systems and which transmits a control signal
for controlling a battery.
SUMMARY OF THE INVENTION
[0009] To address the above-explained technical issue, a battery
control system of the present invention causes a slave control
device to refers to master-device line information when detecting a
fault of a master control device, and obtains line information to
establish a connection with the other master control device. Next,
the slave control device transmits connection request information
to the master control device extracted from the other master
control devices. The other master control device determines whether
or not a connection with the slave control device that has
transmitted the connection request information is possible, and
transmits a determination result as connectability information. The
slave control device switches a communication line to the other
master control device when the received connectability information
indicates a connectable status.
BRIEF DESCRIPTION OF THE DRAWINGS
[0010] FIG. 1 is a diagram for explaining a process outline by a
battery control system according to an embodiment of the present
invention;
[0011] FIG. 2 is a diagram showing an example connection (four
series and two parallel) of an electric system of a battery control
module;
[0012] FIG. 3 is a diagram showing an example connection (eight
series) of an electric system of a battery control module;
[0013] FIG. 4 is a diagram showing an example connection (two
series and four parallel) of an electric system of a battery
control module;
[0014] FIG. 5 is a functional block diagram showing example
configurations of a slave control device, a master control device
and a battery-system managing device in the battery control system
according to the embodiment of the present invention;
[0015] FIG. 6A is a diagram showing an illustrative data structure
of string information according to the embodiment of the present
invention;
[0016] FIG. 6B is a diagram showing an illustrative data structure
of string information according to the embodiment of the present
invention;
[0017] FIG. 7 is a flowchart showing a flow of a communication-line
switching process executed by the slave control device according to
the embodiment of the present invention;
[0018] FIG. 8 is a sequence diagram showing a whole process flow by
the battery control system according to the embodiment of the
present invention; and
[0019] FIG. 9 is a diagram for explaining a process outline of a
battery control system according to a prior art.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
[0020] <Process Outline>
[0021] First, an explanation will be given of a process outline
executed by a battery control system 1 according to an embodiment
of the present invention.
[0022] FIG. 1 is a diagram for explaining a process outline by the
battery control system 1 according to the embodiment.
[0023] As shown in FIG. 1, the battery control system 1 of this
embodiment includes a plurality of slave control devices 30 that
control charging/discharging of a battery, a plurality of master
control devices 20 (20A, 20B, 20C, etc.,) each connected to the
plurality of slave control devices 30 via a communication line (a
first communication line) 5, and configured to control the whole
plural slave control devices 30 connected to the local master
control device 20, and a battery-system managing device 10 which is
connected to the plurality of master control devices 20 via a
communication line (a second communication line) 6 and which
controls the whole battery control system 1.
[0024] According to the prior art battery control system shown in
FIG. 9, for example, a master control device 92A and slave control
devices 93 that are the slave devices of the master control device
are disposed as a battery pack 2 with a fixed communication line 5.
Hence, when the master control device 92A suffers a fault, the
slave control devices 93 ((1) to (8)) connected to the master
control device 92A as slaves become unable to communicate, and thus
a control of a battery, such as charging and discharging, is
disabled.
[0025] According to the battery control system 1 of this
embodiment, as shown in FIG. 1, when, for example, the master
control device 20A suffers a fault, the slave control devices 30
that are the slave devices of the master control device 20A
transmit a connection request (connection request information to be
discussed later) to the other master control device 20 (e.g.,
master control devices 20B and 20C) other than the breakdown master
control device 20A. Next, when the other master control device 20
(20B and 20C) is connectable, those slave control devices 30 switch
the communication line (the first communication line) 5, and
charge/discharge the battery under the control of the other master
control device 20 (20B and 20C).
[0026] Moreover, the slave control device 30 switches of this
embodiment, for each string indicating a configuration (a group) of
series connection of a set electric system, a communication line to
the other master control device 20 of the same string. An
explanation will now be given of a string (a group of series
connection) according to this embodiment.
[0027] FIG. 2 is a diagram showing an example connection (four
series and two parallel) of an electric system of a battery
module.
[0028] In this embodiment, a battery module means a configuration
including the slave control devices 30 and a battery controlled by
the slave control devices 30. Illustration of the battery is
omitted in FIGS. 2 to 4.
[0029] In FIG. 2, the slave control devices 30 (1) to (4) and 30
(5) to (8) are connected in series, respectively, and such two
systems are connected in parallel. The slave control devices 30 (1)
to (4) or (5) to (8) in series connection, respectively, are
defined as a string (a group of series connection). The battery
controlled by the slave control devices 30 (1) to (4) and the
battery controlled by the slave control devices 30 (5) to (8) are
connected in series, and groups of batteries in series connection
are connected in parallel. The communication line 5 for
transmitting/receiving control information, etc., with the master
control device 20 is connected in parallel for each slave control
device 30.
[0030] According to the example case shown in FIG. 3 (eight
series), the slave control devices 30 (1) to (8) are connected in
series, and configure a string. That is, batteries controlled by
the slave control devices 30 (1) to (8) are connected in
series.
[0031] According to the example case shown in FIG. 4 (two series
and four parallel), the slave control devices 30 (1) and (2), (3)
and (4), (5) and (6), (7) and (8) are connected in series,
respectively and each series connection configures a string. That
is, batteries controlled by respective pairs of slave control
devices 30 (1) and (2), (3) and (4), (5) and (6), (7) and (8) are
connected in series, and groups of the batteries in series
connection are connected in parallel.
[0032] The reason why such a string (a group of series connection)
is introduced is if the slave control devices 30 belonging to the
same string detect a fault of the master control device 20
connected to those slave control devices 30, and switch the line
individually, those slave control devices 30 are connected to the
other master control devices 20, respectively, and become
uncontrollable. The introduction of the concept of string is to
prevent such uncontrollability. For example, in FIG. 1, when the
slave control device 30 (1) which is controlled by the master
control device 20A having a fault and belonging to the same string,
and which switches the communication line to be connected to the
master control device 20B, and the slave control device 30 (2)
belonging to the same string switches the communication line to be
connected to the master control device 20C, separate instructions
for charging and discharging are given from respective master
control devices 20 (20B and 20C) to the batteries in a series
connection at different timings, and the slave control devices 30
become uncontrollable.
[0033] The slave control device 30 of this embodiment stores in
advance information on the local string, and transmits a connection
request ("connection request information" to be discussed later)
containing information on the local string to the other master
control device 20. Accordingly, the slave control devices 30
belonging to the same string can switch the communication line to
the same other master control device 20. That is, the slave control
devices 30 can switch the communication line to the other master
control device 20 while maintaining the string (the group of series
connection). The detail of this operation will be explained
later.
[0034] <System Configuration>
[0035] Next, a detailed explanation will be given of individual
configurations of the slave control device 30, the master control
device 20, and the battery-system managing device 10 configuring
the battery control system 1 of this embodiment.
[0036] FIG. 5 is a functional block diagram showing respective
configurations of the slave control device 30, the master control
device 20, and the battery-system managing device 10 of the battery
control system 1 of this embodiment.
[0037] <Slave Control Device>
[0038] First, an explanation will be given of the detail of a
configuration of the slave control device 30 according to this
embodiment.
[0039] The slave control device 30 controls charging/discharging of
a battery 4 under the control of the master control device 20.
Moreover, the slave control device 30 executes a process of
switching the communication line 5 to the other master control
device 20 when the master control device 20 connected to this slave
control device 30 suffers a fault like a breakdown.
[0040] As shown in FIG. 5, the slave control device 30 includes a
control unit 31, a communication unit 32, and a memory unit 33.
[0041] The control unit 31 is responsible for the whole control of
the slave control device 30 which performs processes of
charging/discharging the battery 4 and switching a communication
line to the other master control device 20, and includes a
transmitting/receiving unit 311, a fault monitoring unit 312, a
master-device searching unit 313, a connection-request-information
generating unit 314, a connectability information obtaining unit
315, a line switching unit 316, and a battery control unit 317.
[0042] The transmitting/receiving unit 311 controls
transmission/reception of information with the master control
device 20 through the communication unit 32.
[0043] The fault monitoring unit 312 receives a connection check
signal from the master control device 20 at a predetermined
interval, and transmits a reply signal to the master control device
20, thereby periodically monitoring the communication line with the
master control device 20.
[0044] When not receiving the connection check signal from the
master control device 20 even if the predetermined interval has
elapsed, the fault monitoring unit 312 detects a fault occurring on
the master control device 20, and transmits information on that
fault to the master-device searching unit 313.
[0045] Moreover, after detecting that the fault has occurred on the
master control device 20, when receiving the connection check
signal again from that master control device 20, the fault
monitoring unit 312 determines that the master control device 20 is
recovered from the fault, and transmits information on that
recovery to the master-device searching unit 313.
[0046] The master-device searching unit 313 refers to string
information 300 stored in the memory unit 33 when obtaining the
information to the effect that the fault occurring on the master
control device 20 is detected from the fault monitoring unit 312,
and obtains information on the slave control devices 30 configuring
the local string (the group of series connection).
[0047] FIGS. 6A and 6B are diagrams showing an illustrative data
structure of the string information 300 according to this
embodiment.
[0048] FIG. 6A shows the string information 300 stored in the
memory unit 33 of the slave control device 30 belonging to a string
"A-1" under the control of the master control device 20A in FIG. 1.
Moreover, FIG. 6B shows the string information 300 stored in the
memory unit 33 of the slave control device 30 belonging to a string
"A-2" under the control of the master control device 20A in FIG.
1.
[0049] As shown in FIG. 6A, the string information 300 of this
embodiment includes a master-device ID 301, a string ID 302, and a
slave-device ID 303.
[0050] The master-device ID 301 is unique to the master control
device 20 to which the slave control device 30 is currently
connected. For example, the master-device ID 301 that is "A" of the
master control device 20 is stored.
[0051] The string ID 302 is unique to the string (the group of
series connection) to which the slave control device 30 belongs.
For example, the string ID 302 that is "A-1" of the string
connected to the master control device 20A is stored. The string ID
"A-1" indicates that the string is set as the "first" string of the
master control device 20A.
[0052] The slave-device ID 303 is unique to the slave control
device 30, and for example, the slave-device ID 303 that is "A-1-1"
is stored. The slave-device ID "A-1-1" indicates that, as an
initial basic setting, this slave control device 30 is under the
control of the master control device 20A, and is set as the "first"
slave control device 30 among the slave control devices 30 with the
string ID of "A-1".
[0053] The string information 300 shown in FIG. 6A includes four
records, and indicates that the four slave control devices 30
belong to the string having the string ID 302 of "A-1".
[0054] Likewise, the string information 300 shown in FIG. 6B
indicates that the four slave control devices 30 belong to the
string having the string ID 302 of "A-2" and connected to the
master control device 20A.
[0055] Returning to FIG. 5, the master-device searching unit 313
refers to the string information 300, and obtains the local
slave-device ID 303 and information on the number of slave control
devices 30 belonging to the local string.
[0056] Moreover, the master-device searching unit 313 refers to
master-device-line information 350 stored in the memory unit 33,
and determines whether or not line information (a frequency, a time
slot, a phase, and a modulation scheme) necessary for a
communication with each master control device 20 is stored.
[0057] Next, when the stored master-device-line information 350
contains the line information of the other master control device
20, the master-device searching unit 313 obtains the line
information of the other master control device 20 from the
master-device-line information 350.
[0058] Moreover, when the master-device-line information 350 stored
in the memory unit 33 does not contain the line information of the
other master control device 20, the master-device searching unit
313 calculates the line information of the other master control
device based on the line information of the local master control
device 20. For example, the master-device searching unit 313
calculates and obtains the line information of the other master
control device 20 for each predetermined difference in frequency
within a predetermined frequency range set in advance.
[0059] Next, the master-device searching unit 313 extracts a piece
of line information among the pieces of obtained line information
of the other master control devices 20, and passes the extracted
line information of the other master control device 20, the local
slave-device ID 303 obtained from the string information 300 and
information on the number of slave control devices 30 in the local
string to the connection-request-information generating unit 314 to
execute a communication line switching process for switching the
communication line 5 to the other master control device 20. The
communication line switching process is a successive process
executed by the master-device searching unit 313, the
connection-request-information generating unit 314, the
connectability information obtaining unit 315, and the line
switching unit 316, and will be explained in more detail later with
reference to FIG. 7.
[0060] Next, the connection-request-information generating unit 314
generates connection request information containing the local
slave-device ID 303 obtained from the master-device searching unit
313 and the information on the number of slave control devices
belonging to the local string. Thereafter, the connection request
information is transmitted to the extracted other master control
device 20 based on the line information of the other master control
device 20 extracted by the master-device searching unit 313.
[0061] The connectability information obtaining unit 315 obtains
connectability information from the other master control device 20
which has received the connection request information. The
connectability information indicates whether or not the slave
control devices 30 by what corresponds to the number thereof
configuring the local string are connectable to the other master
control device 20, and is added with information "connectable" or
"unconnectable".
[0062] When the information added to the connectability information
is "connectable", the connectability information obtaining unit 315
passes such information to the line switching unit 316.
[0063] Conversely, when the information added to the connectability
information is "unconnectable", the connectability information
obtaining unit 315 passes such information to the master-device
searching unit 313.
[0064] The line switching unit 316 switches the communication line
5 to the other master control device 20 which has transmitted the
connectability information of "connectable" when obtaining the
information of "connectable" from the connectability information
obtaining unit 315.
[0065] Moreover, the line switching unit 316 switches the
communication line 5 to the original master control device 20 when
obtaining information to the effect that the original master
control device 20 is recovered from the fault from the fault
monitoring unit 312.
[0066] The battery control unit 317 receives a battery control
signal from the battery-system managing device 10 via the master
control device 20, and controls charging/discharging of the battery
4 connected to the battery control unit 317.
[0067] The communication unit 32 includes a communication interface
for transmitting and receiving information with each master control
device 20.
[0068] The memory unit 33 includes memory means, such as a flash
memory or a RAM (Random Access Memory), and stores the string
information 300, the master-device-line information 350, etc.
[0069] The function of the control unit 31 of the slave control
device 30 is realized by, for example, a CPU (Central Processing
Unit) which extracts in a memory like a RAM a program stored in the
memory unit 33 of the slave control device 30 and runs such a
program, or an exclusive circuit, etc.
[0070] <Master Control Device>
[0071] Next, a detailed explanation will be given of a
configuration of the master control device 20 according to this
embodiment.
[0072] The master control device 20 is connected to the
battery-system managing device 10 and individual local slave
control devices 30, and transmits control information from the
battery-system managing device 10 to each slave control device
30.
[0073] As shown in FIG. 5, the master control device 20 includes a
control unit 21, a communication unit 22, and a memory unit 23.
[0074] The control unit 21 is responsible for the control of the
whole master control device 20, and includes a
transmitting/receiving unit 211, a fault monitoring unit 212, a
slave-device connection managing unit 213, and a battery control
unit 214.
[0075] The transmitting/receiving unit 211 controls transmission
and reception of information with the battery-system managing
device 10 and each slave control device 30 via the communication
unit 22.
[0076] The fault monitoring unit 212 receives a connection check
signal from the battery-system managing device 10 at a
predetermined interval, and transmits a reply signal to the
battery-system managing device 10, thereby periodically monitoring
the communication line with the battery-system managing device 10.
Moreover, the fault monitoring unit 212 transmits a connection
check signal to each slave control device 30 at a predetermined
interval, and receives a reply signal from each slave control
device 30, thereby periodically monitoring the communication line
with each slave control device 30.
[0077] The slave-device connection managing unit 213 executes a
following process when receiving the connection request signal from
the slave-control device 30 under the control of the other master
control device 20 than the local master control device 20 via the
transmitting/receiving unit 211. That is, the slave-device
connection managing unit 213 determines whether or not the local
master control device 20 is connectable as the other master control
device 20 to the slave control devices 30 by what corresponds to
the number of slave control devices 30 belonging to the string
where the slave control device 30 which has requested a connection
belongs based on the information which is added with the connection
request signal and which is on the number of the slave devices 30
belonging to the string where the slave control device 30 that has
requested a connection belongs.
[0078] The determination by the slave-device connection managing
unit 213 for the connectability can be made based on a
determination on whether or not the transmission channels within
the frequency range set for the master control device 20 have
unused channels by what corresponds to the number of slave control
devices 30 belonging to the string where the slave control device
30 which has requested a connection belongs when, for example,
transmission is carried out through a frequency division multiplex
scheme over the communication line 5, and whether or not time slots
have unused time slots by what corresponds to the number of such
slave control devices 30 belonging to the string when transmission
is carried out through a time division multiplex scheme, etc.
[0079] When determining that the slave control devices 30 by what
corresponds to the number of slave control devices 30 belonging to
the string are connectable, the slave-device connection managing
unit 213 replies the connectability information added with the
information "connectable" to the slave control device 30 that has
transmitted the connection request information.
[0080] Conversely, when determining that it is unconnectable, the
slave-device connection managing unit 213 replies the
connectability information added with the information
"unconnectable" to the slave control device 30 that has transmitted
the connection request information.
[0081] The slave-device connection managing unit 213 receives the
same connectability information from the slave control devices 30
belonging to the same string by what corresponds to the number of
such slave control devices 30, but transmits the same determination
result on the determination of "connectable" or "unconnectable" as
the connectability information to each slave control device 30.
[0082] Moreover, when each slave control device 30 which has
received the connectability information added with the information
"connectable" switches the communication line, the slave-device
connection managing unit 213 generates slave-device connection
information 200 indicating that this slave control device 30 is
connected to the local master control device 20, and stores the
generated information in the memory unit 23. Furthermore, the
slave-device connection managing unit 213 transmits the generated
slave-device connection information 200 to the battery-system
managing device 10 via the transmitting/receiving unit 211.
[0083] The battery control unit 214 transmits battery control
information received from the battery-system managing device 10 to
the slave control device 30 connected to the local master control
device 20.
[0084] The communication unit 22 includes a communication interface
for transmitting and receiving information with each slave control
device 30 and the battery-system managing device 10.
[0085] The memory unit 23 includes memory means, such as a flash
memory or a RAM, and stores the slave-device connection information
200, etc., indicating each slave control device 30 connected to the
local master control device 20.
[0086] The function of the control unit 21 of the master control
device 20 is realized by, for example, a CPU (Central Processing
Unit) which extracts in a memory like a RAM a program stored in the
memory unit 23 of the master control device 20 and runs such a
program, or an exclusive circuit, etc.
[0087] <Battery-System Managing Device>
[0088] Next, a configuration of the battery-system managing device
10 of this embodiment will be explained in detail.
[0089] The battery-system managing device 10 is connected to each
master control device 20, and transmits battery control
information, etc., to the slave control devices 30 under the
control of each master control device 20.
[0090] As shown in FIG. 5, the battery-system managing device 10
includes a control unit 11, a communication unit 12, a memory unit
13, and an input/output unit 14.
[0091] The communication unit 12 includes a communication interface
for transmitting and receiving information with each master control
device 20.
[0092] The memory unit 13 includes memory means, such as a hard
disk, a flash memory, or a RAM, and stores connection status
information 100 indicating to which slave control devices 30 each
master control device 20 connected to the battery-system managing
device 10 is connected, etc.
[0093] The input/output unit 14 includes an input device
(unillustrated), such as a keyboard or a mouse, an output device
(unillustrated) like a display, and an input/output interface for
exchanging information with those devices.
[0094] The control unit 11 is responsible for the control of the
whole battery-system managing device 10, and includes a
transmitting/receiving unit 111, a fault monitoring unit 112, a
connection status managing unit 113, a battery managing unit 114,
and a display processing unit 115.
[0095] The transmitting/receiving unit 111 controls transmission
and reception of information with each master control device 20 via
the communication unit 12.
[0096] The fault monitoring unit 112 transmits the connection check
signal to each master control device 20 at a predetermined
interval, and receives the reply signal from each master control
device 20, thereby periodically monitoring the communication line
with each master control device 20.
[0097] When not receiving the reply signal from the master control
device 20 even if a predetermined interval has elapsed, the fault
monitoring unit 112 detects the fault occurring on the master
control device 20, and passes information on that fault to the
display processing unit 115.
[0098] Moreover, after detecting the fault occurring on the master
control device 20, when receiving the reply signal from that master
control device 20 again, the fault monitoring unit 112 determines
that the master control device 20 is recovered from the fault, and
passes information on that recovery to the display processing unit
115.
[0099] The connection status managing unit 113 receives, from each
master control device 20, the slave-device connection information
200 indicating the slave control devices 30 connected to that
master control device 20, and updates the connection status
information 100 stored in the memory unit 13.
[0100] Moreover, the connection status managing unit 113 passes the
slave-device connection information 200 to the display processing
unit 115 when receiving such information from each master control
device 20.
[0101] The battery managing unit 114 refers to the connection
status information 100 stored in the memory unit 13, and transmits
battery control information, etc., to the slave control devices 30
under the control of each master control device 20.
[0102] The display processing unit 115 causes the unillustrated
display device to display fault information indicating the fault
master control device 20 and obtained from the fault monitoring
unit 112 and fault recovery information. Moreover, the display
processing unit 115 causes the unillustrated display device to
display information on the slave control devices 30 connected to
each master control device 20 based on the slave-device connection
information 200 received from the connection status managing unit
113.
[0103] <Process Detail>
[0104] Next, a detailed explanation will be given of a
communication-line switching process executed by the slave control
device 30 according to this embodiment. Thereafter, the flow of the
whole process by the battery control system 1 of this embodiment
will be explained.
[0105] <Communication-Line Switching Process>
[0106] FIG. 7 is a flowchart showing a flow of the
communication-line switching process executed by the slave control
device 30 of this embodiment. The communication-line switching
process causes the slave control device 30 to switch the
communication line to the other master control device 20 when the
master control device 20 becomes uncommunicatable due to a fault
like a breakdown. It is presumed that, as shown in FIG. 1, the
master control device 20A suffers a fault like a breakdown. The
master control device 20A controls the slave control devices 30
((1) to (8)) of the electric system in the four series and two
parallel connection as shown in FIG. 2, and as shown in FIG. 1, the
slave control devices 30 ((1) to (4)) belong to the string "A-1",
and the slave control devices 30 ((5) to (8)) belong to the string
"A-2".
[0107] First, the fault monitoring unit 312 of the slave control
device 30 detects, upon checking of no check signal after the
predetermined interval has elapsed with the master control device
20, that the master control device 20 is suffering a fault (step
S101).
[0108] Next, the master-device searching unit 313 of the slave
control device 30 refers to the string information 300 stored in
the memory unit 33, and obtains information on the slave control
devices 30 configuring the string where the local slave control
device 30 belongs (step S102). In this step, the master-device
searching unit 313 obtains, from the string information 300, the
slave-device ID 303 of the local device that is "A-1-1", and
information to the effect that the number of slave control devices
30 belonging to the same string is four (see FIG. 6A).
[0109] Subsequently, the master-device searching unit 313 refers to
the master-device-line information 350 stored in the memory unit
33, and determines whether or not line information (frequency, time
slot, phase, and modulation scheme) necessary to communication with
the other master control device 20 is stored (step S103).
[0110] When the master-device-line information 350 is recorded with
the necessary line information to communicate with the other master
control device 20 (step S103: YES), the master-device searching
unit 313 obtains the line information for the other master control
device 20 from the master-device-line information 350 (step S104),
and the process progresses to next step S106.
[0111] Conversely, when the master-device-line information 350 is
not recorded with such necessary line information to communicate
with the other master control device 20 (step S103: NO), the
master-device searching unit 313 calculates the line information of
the other master control device 20 (step S105), and the process
progresses to the next step S106. The calculation of the line
information of the other master control device 20 by the
master-device searching unit 313 is carried out by, for example,
calculating the line information of each master control device 20
based on a predetermined difference in frequency stored in advance
in the memory unit 23 and within a frequency range used to
communicate with the master control device 20.
[0112] Next, in the step S106, the master-device searching unit 313
extracts one of the other master control devices 20 than the local
master control device 20, and obtains the line information of the
extracted master control device 20.
[0113] Regarding the extraction of the other master control device
20 by the master-device searching unit 313, the same logic is
applied to each of the slave control devices 30 (four devices)
belonging to the same string shown in FIG. 1 and one of the other
master control devices 20 is extracted in the same order. Moreover,
the way of extracting the master control device 20 by the
master-device searching unit 313 may employ, for example, a logic
of extracting the other master control device 20 in the order of
closer frequency to that of the master control device 20 that has
been connected before. Hence, the master-device searching units 313
of the slave control devices 30 (four devices) belonging to the
same string do not separately extract the different master control
devices 20, but extract the same master control device 20 in
accordance with the same logic.
[0114] Subsequently, the connection-request-information generating
unit 314 of the slave control device 30 generates the connection
request information including the slave-device ID 303 (A-1-1) of
the local slave device 30 obtained in the step S102, and the
information on the number of slave control devices 30 (four
devices) configuring the local string (A-1). Thereafter, the
connection-request-information generating unit 314 transmits the
generated connection request information to the other master
control device 20 (e.g., the master control device 20B) based on
the line information of the other master control device 20 obtained
in the step S106 (step S107).
[0115] The connectability information obtaining unit 315 of the
slave control device 30 obtains the connectability information
added with information on whether or not the master control device
20 is connectable from the master control device 20 which has
transmitted the connection request information in the step S107
(step S108), and checks whether or not it is connectable (step
S109).
[0116] When the information added to the connectability information
indicates a connectable status (step S109: YES), the connectability
information obtaining unit 315 passes such information to the line
switching unit 316, and the line switching unit 316 switches the
communication line for a battery control to the connectable master
control device 20 (step S110).
[0117] Conversely, when the information added to the connectability
information indicates an unconnectable status (step S109: NO), the
connectability information obtaining unit 315 passes such
information to the master-device searching unit 313, and the
master-device searching unit 313 determines whether or not all
pieces of line information of the other master control devices 20
are processed (step S111).
[0118] The determination by the slave-device connection managing
unit 213 of the master control device 20 on whether or not it is
connectable is to determine whether or not the slave control
devices 30 by what corresponds to the number thereof in the string
are connectable. Accordingly, the pieces of connectability
information from the slave control devices 30 (four devices)
belonging to the same string are added with the same determination
result "connectable" or "unconnectable". Moreover, when the
slave-device connection managing unit 213 is configured to
determine whether or not the slave control device 30 belonging to a
string is connectable for the pieces of connection request
information from the slave control devices 30 (four devices)
belonging to the same string, the further determination for the
pieces of connection request information from the slave control
devices 30 (the remaining three devices) belonging to the same
string is unnecessary, and it is fine if the connectability
information generated using the determination result of the first
process is transmitted.
[0119] When there is the line information of the other master
control device 20 not processed yet (step S111: NO), the process
returns to the step S106, and the master-device searching unit 313
extracts the next master control device 20.
[0120] Conversely, when determining that all pieces of line
information of the other master control devices 20 are processed
(step S111: YES), the master-device searching unit 313 determines
that the line switching is unavailable, and terminates the process
(step S112).
[0121] In the example case shown in FIG. 1, as a result of the
communication line switching process, the four slave control
devices 30 ((1) to (4)) belonging to the string "A-1" switch the
communication line 5 to the master control device 20B, and the four
slave control devices 30 ((5) to (8)) belonging to the string "A-2"
switch the communication line 5 to the master control device
20C.
[0122] According to such a process, each slave control device 30
can switch the communication line to the other master control
device 20 while maintaining the string (the group of series
connection).
[0123] <Whole Process by Battery Control System>
[0124] Next, an explanation will be given of a flow of the whole
process by the battery control system 1 of this embodiment.
[0125] FIG. 8 is a sequence diagram showing a flow of the whole
process by the battery control system 1 according to this
embodiment.
[0126] It is presumed that as shown in FIG. 1 the master control
device 20 (20A) suffers a fault like a breakdown, the slave control
devices 30 (hereinafter, referred to as "slave control devices
30a") belonging to the string "A-1" under the control of the master
control device 20A and the slave control devices 30 (hereinafter,
referred to as "slave control devices 30b") belonging to the string
"A-2" also under the control of the master control device 20A
perform line switching to be connected to the other master control
devices 20 (20B and 20C), respectively.
[0127] First, periodical monitoring is performed between the master
control device 20A and the slave control device 30a and the slave
control device 30b under the control of such master control device
20A, and between the master control device 20A and the
battery-system managing device 10 (step S1). The four slave control
devices 30a and the four slave control devices 30b shown in FIG. 1
respectively perform periodical monitoring with the master control
device 20A. The processes executed by the slave control device 30a
and the slave control device 30b and explained below are executed
by respective four devices.
[0128] Respective fault monitoring units 312 of the slave control
devices 30a and 30b detect that the master control device 20A is
suffering a fault like a breakdown since, for example, no
connection check signal from the master control device 20A is
confirmed even after the predetermined interval (step S2: detect
fault).
[0129] Moreover, the battery-system managing device 10 (the fault
monitoring unit 122) detects that the master control device 20A is
suffering a fault since, for example, no reply signal to the
connection check signal transmitted by battery-system managing
device 10 to the master control device 20A is confirmed even after
the predetermined interval, and displays information on the fault
detection on the display device (unillustrated) through the display
processing unit 115 (step S3: display fault occurrence).
[0130] The slave control device 30a that has detected the fault
executes the communication-line switching process (see FIG. 7). The
slave control device 30a searches the other master control device
20 (step S4), and transmits the connection request information to
the searched master control device 20B (step S5). The master
control device 20B determines that the four slave control devices
30 belonging to the string "A-1" (see FIG. 6A) are connectable, and
transmits the connectability information indicating the
determination result "connectable" to the slave control device 30a
(step S6). Next, the slave control device 30a switches the
communication line for battery control from the master control
device 20A to the master control device 20B (step S7). Next, the
master control device 20B transmits the slave-device connection
information 200 to the effect that the communication line is
established with the slave control devices 30a (the four devices)
belonging to the string "A-1" to the battery-system managing device
10 (step S8).
[0131] The slave control device 30b also detecting the fault
executes the same process as that of the slave control device 30a
(steps S4 to S8) with the master control device 20C extracted from
the other master control devices 20 (steps S9 to S13).
[0132] The battery-system managing device 10 that has received
respective slave-device connection information 200 from the master
control device 20B and the master control device 20C causes the
display device to display information to the effect that the group
of slave control devices 30 belonging to the string "A-1" and the
group of slave control devices 30 belonging to the string "A-2" are
connected to the master control device 20B and the master control
device 20C, respectively (step S14: display connection status).
[0133] Next, when the master control device 20A suffering a fault
is recovered from such a fault by repair, replacement, etc.,
respective fault monitoring units 312 of the slave control devices
30a and 30b detect that the master control device 20A is recovered
from the fault by, for example, receiving the connection check
signal from the master control device 20A (step S21: detect fault
recovery).
[0134] Moreover, the battery-system managing device 10 (the fault
monitoring unit 122) detects that the master control device 20A is
recovered from the fault by, for example, receiving the reply
signal to the connection check signal transmitted by the
battery-system managing device 10 to the master control device 20A
within a predetermined interval, and causes the display device to
display information on the recovery from the fault through the
display processing unit 115 (step S22: display fault recovery).
[0135] Next, the slave control device 30a that has detected the
recovery of the master control device 20A from the fault switches
the communication line for a battery control from the master
control device 20B to the master control device 20A (step S23).
Moreover, the slave control device 30b that has detected the
recovery of the master control device 20A from the fault switches
the communication line for a battery control from the master
control device 20C to the master control device 20A (step S24).
[0136] Subsequently, the master control device 20A transmits the
slave-device connection information 200 to the effect that the
communication lines are established with the group of slave control
devices 30 belonging to the string "A-1" and the group of slave
control devices 30 belonging to the string "A-2" to the
battery-system managing device 10 (step S25).
[0137] Next, the battery-system managing device 10 that has
received the slave-device connection information 200 from the
master control device 20A causes the display device to display
information to the effect that the master control device 20A is
recovered from the fault and the communication line is returned to
the original connection (step S26: display connection status).
[0138] As explained above, according to the battery control system
1 and the battery control method according to this embodiment, even
if the master control device 20 suffers a fault, the slave control
device 30 under the control of that master control device 20 can
switch the line to the other master control device 20 while
maintaining the string (the group of series connection) where the
local slave control device 30 belongs. Accordingly, it becomes
possible to avoid uncontrollability of the battery controlled by
the slave control device 30 under the control of the master control
device 20 suffering a fault.
[0139] The distributed processing of the battery control employed
by the battery control system 1 and the battery control method of
this embodiment is advantageous when the number of batteries is
large, and is especially advantages for the battery management of a
natural energy power generating system in a mega-watt class.
* * * * *