KR102723144B1 - Method for confirm software compatibility and update - Google Patents

Abstract

A method for verifying software compatibility between BMSs according to an embodiment of the present invention may be configured to include a lower-level controller software version verification step of verifying the software version of a lower-level controller (BBMS, RBMS, MBMS) in a top-level controller (BSC), a software compatibility verification step of verifying whether software installed in a top-level controller and software installed in a lower-level controller are compatible in a top-level controller, and a battery system operation step of starting operation of the battery system.

Description

Method for confirming software compatibility and automatic update between BMSs installed in ESS {Method for confirming software compatibility and update}

The present invention relates to a method for checking software compatibility between BMSs mounted on an ESS and an automatic update method.

ESS is composed of multiple battery banks, each of which is composed of multiple racks, and each of which is composed of battery modules. ESS configured in this manner is configured including a BSC (Battery System Controller), which is the top-level controller that controls the entire ESS, and each of the battery bank, battery rack, and battery module is configured including a BBMS (Bank BMS), RBMS (Rack BMS), and MBMS (Module BMS).

Meanwhile, since the above BSC, BBMS, RBMS, and MBMS each control different hardware (number of fans, number of contactors, presence or absence of circuit breakers, etc.), different software is installed and used.

Since different software is installed in this way, in order for the ESS to operate normally, it had to be confirmed that the software installed in the top-level controller, BSC, and the software installed in each of the lower-level controllers, BBMS, RBMS, and MBMS, were mutually compatible.

A specific compatibility verification method is that since the BSC does not know the software information of the lower controller at the time of initial communication, it assumes that the software is compatible with the BSC and attempts to communicate with the lower controller using the same communication protocol and procedure as the software of the BSC.

If the software of the lower controller is a version compatible with the software of the BSC, the above communication is performed normally, but if it is an incompatible version, communication may not be possible or may not operate properly.

Specifically, if the software of the lower controller uses a different communication protocol and procedure from that of the BSC, communication itself may not be possible. And if the communication method of the software of the lower controller is the same as that of the BSC, it is impossible to verify whether the software of the lower controller is compatible with that of the BSC.

In order to solve the problem of not being able to check whether the software of the lower controller is compatible in the BSC, a conventional technique involved having an engineer directly check the version information of the BSC and the lower controller, and if incompatible software was installed in the lower controller, updating the software of the lower controller.

These conventional techniques are highly prone to errors again due to engineer mistakes.

Therefore, the present invention proposes a method for checking whether the software of a lower controller is compatible in a BSC, and automatically updating the software of the lower controller in the BSC if it is not compatible.

Korean Patent Publication KR 10-2014-0056170 A

The present invention provides a method for determining whether software of a lower level controller in a BSC is compatible.

Additionally, the present invention provides a method for automatically updating the software of a lower controller from a BSC when the software of the BSC and the software of the lower controller are not compatible.

A method for verifying software compatibility between BMSs according to an embodiment of the present invention may be configured to include a lower-level controller software version verification step of verifying the software version of a lower-level controller (BBMS, RBMS, MBMS) in a top-level controller (BSC), a software compatibility verification step of verifying whether software installed in a top-level controller and software installed in a lower-level controller are compatible in a top-level controller, and a battery system operation step of starting operation of the battery system.

The above software compatibility verification step may be configured to include a version and type compatibility verification step for verifying whether the version and type of software installed in the top-level controller are compatible with the version and type of software installed in the lower-level controller, and an NV value comparison step for comparing the NV value set in the top-level controller with the NV value set in the lower-level controller.

Meanwhile, the above NV value is non-volatile information recorded in the ROM of the controller and is the basis for the data operation of the controller and the control logic of the controller.

The above version and type compatibility check step can check whether the collected software version and type are compatible with the software of the top controller based on the software compatibility table pre-stored in the top controller.

In the above version and type compatibility check step, if the version and type of the software of the lower controller are not compatible with the software version and type of the top controller, a lower controller software update step can be performed to update the software of the lower controller using software data built into the top controller.

Meanwhile, if the version and type of the software of the lower controller are compatible with the version and type of the software of the upper controller, the NV value comparison step can be performed.

In the above NV value comparison step, if the NV value of the lower controller is different from the NV value of the upper controller, an NV value update step of updating the NV value of the lower controller with the NV value stored in the upper controller can be performed.

Meanwhile, if the NV value of the lower controller is equal to the NV value of the upper controller, the battery system operation step can be performed.

In an energy storage system according to an embodiment of the present invention, the energy storage system may have one or more lower level controllers connected to a top level controller.

Specifically, the top controller may be configured to include a first control unit that controls the operation of the top controller, a first software storage unit in which top controller software and software of lower controllers are stored, a first NV value storage unit in which NV values of the top controller are stored, a measurement data storage unit in which data measured by the top controller are stored, and a first communication module that performs mutual communication with the lower controller.

The above-described lower controller may be configured to include a second control unit that controls the operation of the lower controller, a second communication module that performs mutual communication with the upper-level controller, a second software storage unit in which software of the lower controller is stored, a second NV value storage unit in which NV values of the lower controller are stored, and a software tool storage unit in which a software tool for updating the second software storage unit is stored.

The first control unit can check the software version and type of the top controller and the software version and type of the lower controller, and if the software version and type of the top controller and the software version and type of the lower controller are compatible, the energy storage system can be operated.

Meanwhile, if the software version and type of the top controller are not compatible with the software version and type of the lower controller, the software of the lower controller can be updated to software that is compatible with the software version and type of the top controller.

The first control unit can check the NV (non-volatile) value of the top controller and the NV value of the lower controller, and if the NV value of the top controller and the NV value of the lower controller match, the energy storage system can be operated.

Meanwhile, if the NV value of the top controller and the NV value of the lower controller do not match, the NV value of the lower controller can be matched with the NV value of the top controller.

The present invention can check whether the software of a lower controller in a BSC is compatible.

In addition, the present invention can automatically update the software of the lower controller from the BSC when the software of the BSC and the software of the lower controller are not compatible.

Figure 1 is a diagram showing the system of various types of controllers mounted on an ESS.
FIG. 2 is a flowchart illustrating a method for checking BMS software compatibility according to an embodiment of the present invention.
FIG. 3 is a configuration diagram of a top-level controller and a lower-level controller according to an embodiment of the present invention.

Hereinafter, with reference to the attached drawings, embodiments of the present invention will be described in detail so that those skilled in the art can easily practice the present invention. However, the present invention may be implemented in various different forms and is not limited to the embodiments described herein. In addition, in order to clearly describe the present invention in the drawings, parts that are not related to the description are omitted, and similar parts are assigned similar drawing reference numerals throughout the specification.

Terms including ordinal numbers such as first, second, etc. may be used to describe various components, but the components are not limited by the terms. The terms are only used for the purpose of distinguishing one component from another. For example, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component, without departing from the scope of the present invention. The terminology used in this application is only used to describe specific embodiments and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly indicates otherwise.

Throughout the specification, when a part is said to be “connected” to another part, this includes not only the case where it is “directly connected” but also the case where it is “electrically connected” with another element in between. Also, when a part is said to “include” a certain component, this does not mean that other components are excluded, but that other components can be included, unless specifically stated to the contrary. The terms “step of doing ~” or “step of ~” used throughout the specification do not mean “step for ~.”

The terms used in the present invention are selected from the most widely used general terms possible while considering the functions of the present invention, but they may vary depending on the intention of engineers working in the field, precedents, the emergence of new technologies, etc. In addition, in certain cases, there are terms arbitrarily selected by the applicant, and in this case, the meanings thereof will be described in detail in the description of the relevant invention. Therefore, the terms used in the present invention should be defined based on the meanings of the terms and the overall contents of the present invention, rather than simply the names of the terms.

1. A method for verifying software compatibility of a BMS according to an embodiment of the present invention.

Figure 1 is a diagram showing the system of various types of BMS mounted on ESS.

ESS is equipped with various BMS. Specifically, it consists of BSC, which is the top-level controller that manages the entire ESS, BBMS that controls the battery bank that makes up the ESS, RBMS that controls the battery rack, and MBMS that controls the battery module.

Meanwhile, since each of the above BSC, BBMS, RBMS, and MBMS controls various types and numbers of hardware, the types of software installed on each are also different. For example, since the number of fans managed by the MBMS and the number of fans managed by the BBMS are different, each must use different software.

Since BSC, BBMS, RBMS, and MBMS each use different software, compatibility testing is required.

In the past, users (engineers) directly checked the software versions of the BSC and lower controllers to confirm compatibility. However, there is a very high possibility that errors will occur in this process where users (engineers) directly check with their own eyes.

Meanwhile, in the present invention, the top-level controller (BSC) directly checks the software version of the lower-level controller (BBMS, RBMS, MBMS) to check whether compatibility is possible, and if compatibility is not possible, the software of the lower-level controller (BBMS, RBMS, MBMS) is updated to a software version that is compatible with the top-level controller (BSC).

FIG. 2 is a flowchart illustrating a method for verifying software compatibility of a BMS according to an embodiment of the present invention.

Hereinafter, a method for verifying software compatibility of a BMS according to an embodiment of the present invention will be described with reference to FIG. 2.

A method for verifying software compatibility of a BMS according to an embodiment of the present invention may be configured to include a step (S100) of verifying a software version of a lower controller (BBMS, RBMS, MBMS) in a top-level controller (BSC), a step (S200) of verifying whether software installed in a top-level controller and software installed in a lower controller are compatible, and a step (S300) of operating a battery system to start operation of the battery system.

Specifically, the software compatibility check step (S200) may be configured to include a version and type compatibility check step (S210) for checking whether the version and type of software installed in the top-level controller are compatible with the version and type of software installed in the lower-level controller, and an NV value comparison step (S220) for comparing the NV value set in the top-level controller with the NV value set in the lower-level controller.

The above NV value is non-volatile information recorded in the ROM of the controller, and is a value that serves as the basis for the data operation of the controller and the control logic of the controller, and is a value set according to the type of battery controlled by the controller when designing the controller. For example, the NV value may be a reference value preset for each type of battery cell. Specifically, it may be a battery cell's over-discharge limit value, an over-charge limit value, a battery cell's operating temperature range value, etc.

Meanwhile, the version and type compatibility check step (S210) can check whether the collected software version and type are compatible with the software of the top controller based on the software compatibility table pre-stored in the top controller.

Table 1 is an example of a compatibility table by software.

BSC S/W BBMS S/W RBMS S/W MBMS S/W Alpha BSC N/A A Gen1 RBMS 1.0 Gen1 MBMS S/W N/A B Gen1 RBMS 1.0 Gen2 MBMS S/W N/A A Gen2 RBMS 1.0 Gen2 MBMS S/W N/A B Gen2 RBMS 1.0 Gen2 MBMS S/W N/A C Gen2 RBMS 1.0 Gen2 MBMS S/W N/A D Gen2 RBMS 1.0 Gen2 MBMS S/W Beta BSC A Gen1 BBMS 1.0 A Gen1 RBMS 1.0 Gen1 MBMS S/W A Gen1 BBMS 1.0 B Gen1 RBMS 1.0 Gen2 MBMS S/W A Gen2 BBMS 1.0 A Gen2 RBMS 1.0 Gen2 MBMS S/W A Gen2 BBMS 1.0 B Gen2 RBMS 1.0 Gen2 MBMS S/W A Gen2 BBMS 1.0 C Gen2 RBMS 1.0 Gen2 MBMS S/W A Gen2 BBMS 1.0 D Gen2 RBMS 1.0 Gen2 MBMS S/W A Gen3 BBMS 1.0 A Gen3 RBMS 1.0 Gen3 MBMS S/W A Gen3 BBMS 1.0 B Gen3 RBMS 1.0 Gen3 MBMS S/W

For example, if the software version of the top controller is Alpha BSC, the lower controller RBMS must have installed software of any one of A Gen1 RBMS 1.0, B Gen1 RBMS 1.0, A Gen2 RBMS 1.0, B Gen2 RBMS 1.0, C Gen2 RBMS 1.0, and D Gen2 RBMS 1.0 to be compatible with the software version Alpha BSC of the top controller.

Meanwhile, in the above version and type compatibility check step, if the version and type of the software of the lower controller are not compatible with the software version and type of the upper controller, a lower controller software update step (S230) can be performed to update the software of the lower controller by transmitting the software for the lower controller built into the upper controller to the lower controller.

For example, if the software version of the top controller is Alpha BSC, but the lower controller RBMS has the A Gen3 RBMS 1.0 software version installed, it is not compatible.

Therefore, the top controller can replace the software of the lower controller RBMS with any one of the software of A Gen1 RBMS 1.0, B Gen1 RBMS 1.0, A Gen2 RBMS 1.0, B Gen2 RBMS 1.0, C Gen2 RBMS 1.0, and D Gen2 RBMS 1.0.

Meanwhile, if the version and type of the software of the lower controller are compatible with the version and type of the software of the upper controller, the NV value comparison step can be performed.

In the above NV value comparison step (S220), if the NV value of the lower controller is different from the NV value of the upper controller, an NV value update step of updating the NV value of the lower controller with the NV value stored in the upper controller can be performed to match the NV value of the lower controller with the NV value of the upper controller (S240).

Meanwhile, if the NV value of the lower controller is equal to the NV value of the upper controller, the battery system operation step can be performed.

2. Energy storage system according to an embodiment of the present invention

An energy storage system according to an embodiment of the present invention may be configured such that one or more lower-level controllers are connected to one upper-level controller.

Figure 4 is a diagram showing the configuration of a specific top-level controller and the configuration of lower-level controllers.

Specifically, the top controller (100) may be configured to include a first control unit (110) that controls the operation of the top controller, a first software storage unit (120) in which top controller software and software of lower controllers are stored, a first NV value storage unit (130) in which NV values of the top controller are stored, a measurement data storage unit (140) in which measurement data of the top controller is stored, and a first communication module (150) that performs mutual communication with the lower controller.

Meanwhile, the lower controller (200) may be configured to include a second control unit (210) that controls the operation of the lower controller, a second communication module (220) that performs mutual communication with the uppermost controller, a second software storage unit (230) in which software of the lower controller is stored, a second NV value storage unit (240) in which NV values of the lower controller are stored, and a software tool storage unit (250) in which a software tool for updating the second software storage unit is stored.

The above first control unit can check the software version and type of the top controller and the software version and type of the lower controller.

Specifically, a software version request signal can be transmitted to the subordinate controller, and software version information can be received from the subordinate controller.

Meanwhile, the first control unit (110) can check whether the software version and type of the collected lower controller are compatible with the software of the upper controller based on the software compatibility table pre-stored in the upper controller (100).

Meanwhile, the first software storage unit (120) may store not only the software of the top controller (100), but also all software for lower level controllers that are compatible with the software of the top controller. Accordingly, in the case where the software of the lower level controller (200) and the software of the top controller (100) are not compatible with each other, the software of the lower level controller (100) may be updated to software that is compatible with the software of the top level controller (100). In other words, the update process is to transfer the software for the lower level controller (200) stored in the top level controller (100) to the lower level controller (200) to replace the existing incompatible software with the compatible software.

Meanwhile, if the software version and type of the top controller and the software version and type of the lower controller are compatible as a result of the software version and type verification, the energy storage system can be operated.

Meanwhile, if the software version and type of the top controller and the software version and type of the lower controller are not compatible as described above, the compatible software for the lower controller stored in the first software storage unit can be transmitted to the lower controller to update it.

Meanwhile, the first control unit (110) checks the NV (non-volatile) value of the top controller (100) and the NV value of the lower controller (200), and if the NV value of the top controller (100) and the NV value of the lower controller (200) match, the energy storage system can be operated.

The above NV value is non-volatile information recorded in the ROM of the controller, and is a value that serves as the basis for the data operation of the controller and the control logic of the controller. It is a value set according to the type of battery controlled by the controller when designing the controller. For example, the NV value may be a voltage diagnosis condition value, an over-discharge limit value, an over-charge limit value, a temperature limit value, etc. according to the type of battery cell.

Meanwhile, if the NV value of the top controller and the NV value of the lower controller do not match as a result of the NV value verification, the NV value of the lower controller can be matched with the NV value of the top controller.

Meanwhile, although the technical idea of the present invention has been specifically described according to the above embodiments, it should be noted that the above embodiments are for the purpose of explanation and not for the purpose of limitation. In addition, those skilled in the art will be able to understand that various embodiments are possible within the scope of the technical idea of the present invention.

100 : Top controller
110: Control Unit 1
120: 1st software storage unit
130: 1st NV value storage unit
140 : Measurement data storage unit
150: 1st communication module
200 : Sub controller
210: Second Control Unit
220: Second Communication Module
230: Second software storage unit
240: 2nd NV value storage
250 : Software Update Tool

Claims (10)

In a method for verifying software compatibility between BMS,
A step for checking the software version of lower level controllers (BBMS, RBMS, MBMS) in the top level controller (BSC);
A software compatibility check step that checks whether the software installed in the top controller is compatible with the software installed in the lower controller at the top controller;
Battery system operation phase that initiates operation of the battery system;
Including,
The above software compatibility check steps are:
Version and type compatibility check step to check whether the version and type of the software installed on the top controller are compatible with the version and type of the software installed on the lower controller;
NV value comparison step that compares the NV value set in the top controller with the NV value set in the lower controller;
A method for verifying software compatibility of a battery system, characterized in that it comprises:
delete In claim 1,
The above NV values are,
A method for verifying software compatibility of a battery system, characterized in that the nonvolatile information recorded in the ROM of the controller is a value that serves as the basis for the data operation of the controller and the control logic of the controller.
In claim 1,
The above version and type compatibility check steps are:
A method for checking software compatibility of a battery system, characterized in that it is checked whether the version and type of software installed in the lower controller is compatible with the software of the upper controller based on a software compatibility table pre-stored in the upper controller.
In claim 1,
In the above version and type compatibility check step
If the version and type of the software of the lower controller are not compatible with the version and type of the software of the upper controller,
A sub-controller software update step that updates the software of the sub-controller using software data embedded in the top-level controller;
To perform,
If the version and type of the software of the above lower controller are compatible with the version and type of the software of the top controller,
A software compatible learning method of a battery system, characterized by performing the above NV value comparison step.
In claim 1,
In the above NV value comparison step,
If the NV value of the lower controller is different from the NV value of the top controller,
An NV value update step that updates the NV values of lower level controllers with the NV values stored in the top level controller;
To perform
If the NV value of the lower controller is equal to the NV value of the top controller,
A method for verifying software compatibility of a battery system, characterized by performing the above battery system operation steps.
In an energy storage system having one or more sub-controllers connected to a top-level controller,
The top level controller above is
A first control unit that controls the operation of the top controller;
A first software storage unit in which the top-level controller software and the software of the lower-level controllers are stored;
A first NV value storage unit in which the NV value of the top controller is stored;
A measurement data storage unit in which data measured by the top controller is stored; and
A first communication module that performs mutual communication with the above sub-controller;
An energy storage system characterized by comprising:
In claim 7,
The above sub-controllers are,
A second control unit for controlling the operation of the above sub-controller;
A second communication module that performs mutual communication with the above top-level controller;
A second software storage unit in which the software of the lower controller is stored;
A second NV value storage unit in which the NV values of the lower controller are stored;
A software tool storage unit in which a software tool for updating the above second software storage unit is stored;
An energy storage system characterized by comprising:
In claim 7,
The above first control unit,
Check the software version and type of the top controller and the software version and type of the lower controller.
If the software version and type of the top controller and the software version and type of the lower controller are compatible, the energy storage system is operated,
If the software version and type of the above top controller are not compatible with the software version and type of the above sub controller,
An energy storage system characterized in that the software of the above lower controller is updated to software compatible with the software version and type of the above upper controller.
In claim 7,
The above first control unit,
By checking the NV (non-volatile) value of the top controller and the NV value of the lower controller,
When the NV value of the top controller and the NV value of the lower controller match, the energy storage system is operated,
If the NV value of the top controller and the NV value of the lower controller do not match,
An energy storage system characterized in that the NV value of the lower controller matches the NV value of the upper controller.

Images