KR102711057B1 - Method for updating BMS software of an energy storage system having different internal and external communication methods - Google Patents

Abstract

A method for updating BMS software of an ESS using different external and internal communication methods of the present invention comprises an update file validity verification step of verifying the validity of an update file from an external device, an update notification step of notifying the start of an update of a BMS from an external device, an update execution step of transmitting the prepared update file from the external device to a BMS via a DC/DC converter and performing an update, and an update termination step of verifying the update file transmitted from the BMS and terminating the update, wherein each of the update notification step, the update execution step, and the update termination step may be configured to include a timeout check step of verifying whether a timeout has occurred in each step.

Description

{Method for updating BMS software of an energy storage system having different internal and external communication methods}

The present invention relates to a device and method for updating a BMS of an energy storage system when the inside and the outside of the energy storage system use different communication methods.

Specifically, the present invention relates to a device and method for updating a BMS of an energy storage system in which the energy storage system and an external device communicate via Modbus, and the energy storage system performs CAN communication.

An energy storage system (ESS) is a device that improves power usage efficiency by storing generated electricity in a storage device such as a battery and supplying it when electricity is needed. The energy storage system stores electricity generated by renewable energy such as solar and wind power or electricity transmitted from a power plant in a lithium-ion battery, and stores the electricity at night when power consumption is low, and then uses the stored electricity during the day when power consumption is relatively high.

This plays a vital role in saving electricity usage, saving electricity bills, and ensuring a stable power supply in case of emergency.

The energy storage system described above is configured with hardware such as a plurality of battery cells, a battery management system (BMS) for controlling the battery cells, and a DC-DC converter for transforming the input DC voltage, and such hardware operates under software control.

Meanwhile, software must be updated according to new technology developments. The conventional BMS software update method was that the BMS software could be updated only when the PC (external device) and the BMS used the same communication method.

Meanwhile, in order to update the software of the BMS without using the same communication method, a separate interface for update was provided to update the software of the BMS, but the update was performed from the beginning to the end without checking the intermediate process of the update, and only then was it confirmed whether the update was performed normally at the end.

In other words, once an update starts, it is inefficient because you have to complete the update process to know whether the update was performed properly.

Therefore, the present invention proposes a method of updating a BMS using a DC/DC converter mounted on an energy storage system having different internal and external communication methods.

Specifically, we propose a method to perform accurate updates by adding an intermediate verification process to check whether the update is performed normally.

Korean Patent Publication No. 10-2015-0066222

The present invention provides a method for updating BMS software of an energy storage system in which internal and external parts use different communication methods.

Specifically, a method for updating BMS software using a DC/DC converter mounted on an energy storage system is provided.

Additionally, it provides a method for performing accurate BMS software updates by adding an intermediate verification process to check whether the BMS software update is being performed normally.

In another embodiment of the present invention, a method for updating BMS software of an ESS using different external and internal communication methods comprises an update file validity checking step of checking the validity of an update file in an external device, an update notification step of notifying the start of an update of a BMS in an external device, an update performing step of transmitting the prepared update file from the external device to a BMS through a DC/DC converter and performing an update, and an update terminating step of verifying the update file transmitted from the BMS and terminating the update, wherein each of the update notification step, the update performing step, and the update terminating step comprises a timeout checking step of checking whether a timeout occurs in each step, and communication between the external device and the DC/DC converter may be performed by MODBUS communication, and communication between the DC/DC converter and the BMS may be performed by CAN communication.

The above update file validity verification step is configured to include an ID verification step for verifying the ID of the update file, a version information verification step for verifying the version information of the update file, a type information verification step for verifying the type information of the update file, a data size verification step for verifying the data size of the update file, and a CRC verification step for verifying the CRC (Cyclic Redundancy Check) of the update file. If an error is detected in at least one of the ID verification step, the version information verification step, the type information verification step, the data size verification step, and the CRC verification step, the update file may be determined to be invalid and the BMS software update may be stopped.

The above update notification step includes a communication baud rate setting step of transmitting a predetermined baud rate setting signal from an external device to a DC/DC converter in a Modbus communication manner and setting a communication baud rate by receiving a response from the DC/DC converter, an update start signal transmitting step of transmitting an update start signal from an external device to the DC/DC converter in a Modbus communication manner, and an update acceptance step of transmitting an update start signal from the DC/DC converter that has received the update start signal to a BMS in a CAN communication manner and receiving an update acceptance signal from the BMS. If the update notification step is not completed within a predetermined time, a time out may occur.

The above update acceptance step may be configured to include an authentication request step of transmitting a BMS authentication request signal from the DC/DC converter to the BMS via a CAN communication method and receiving a response signal from the BMS, a security connection request step of transmitting a secure connection request signal from the DC/DC converter to the BMS via a CAN communication method and receiving a response signal from the BMS, a memory connection request step of transmitting a memory connection request signal from the DC/DC converter to the BMS via a CAN communication method and receiving a response signal from the BMS, and an update start approval step of transmitting an update start approval signal to the external device when the BMS transmits a normal response signal for all of the update request step, the authentication request step, the security connection request step, and the memory connection request step.

The above update execution step is configured to include an update file transmission step between an external device and a DC/DC converter in which the external device reads the update file in a predetermined number of bytes and transmits the read update file of the predetermined number of bytes to the DC/DC converter, an update file transmission step between the DC/DC converter and the BMS in which the DC/DC converter transmits the update file of the predetermined number of bytes transmitted in the update file transmission step from the DC/DC converter to the BMS, a reception confirmation signal transmission step in which the BMS transmits a reception confirmation signal indicating that the update file of the predetermined number of bytes has been received, and a normal reception completion signal transmission step in which the DC/DC converter receiving the reception confirmation signal transmits a normal reception completion signal to the external device, and if the file transmission step between the DC/DC converter and the reception confirmation signal transmission step takes longer than a first reference time, or if the file transmission step or the settlement reception completion signal transmission step between the external device and the DC/DC converter takes longer than a second reference time, a timeout occurs, and if a timeout occurs, the update file is retransmitted from the beginning, and the update execution step is configured to transmit the update file divided into the predetermined number of bytes until all of the update files are transmitted. It can be performed repeatedly.

The above update termination step is configured to include an update data transmission completion signal transmission step for transmitting a signal from an external device to the DC/DC converter to indicate that update data transmission is complete, a BMS self-check step for transmitting a self-check request signal from the DC/DC converter to the BMS and receiving a self-check result, a log record request signal transmission step for transmitting a log record request signal for requesting recording if there is no abnormality in the result of the self-check step, a communication termination signal transmission step for transmitting a communication termination signal from the DC/DC converter to the BMS after the log recording is complete, and a BMS software update completion signal transmission step for transmitting a signal from the DC/DC converter to the external device to indicate that the BMS has normally completed the update. If the above update termination step is not completed within a predetermined time, a time out may occur.

The above timeout confirmation step determines that the update has temporarily failed if a timeout occurs at each step and restarts the step where the timeout occurred from the beginning. If the number of times each step has been restarted is greater than a predetermined number of times, it determines that the update is impossible and performs an update file deletion decision step that determines whether to delete the update file.

The above update file deletion decision step can delete the update file if an existing BMS software file remains, and can maintain the update file if no existing BMS software remains.

The present invention can perform BMS software update using a DC/DC converter installed in an energy storage system in which internal and external communication methods are different.

In addition, the present invention can perform accurate BMS software updates by adding an intermediate verification process to check whether BMS software updates are being performed normally.

FIG. 1 is a flowchart illustrating a method for updating BMS software of an energy storage system having different internal and external communication methods according to an embodiment of the present invention.
FIG. 2 is a flowchart showing an update file validity verification step according to an embodiment of the present invention.
FIG. 3 is a diagram showing the sequence of update notification steps according to an embodiment of the present invention.
FIG. 4 is a diagram showing an update execution step according to an embodiment of the present invention.
FIG. 5 is a diagram showing an update termination step according to an embodiment of the present invention.
FIG. 6 is a diagram illustrating a method for updating BMS software of an energy storage system having different internal and external communication methods according to an embodiment of the present invention, which further includes a time-out recovery confirmation step.

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 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 relevant 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 updating BMS software of an energy storage system having different internal and external communication methods according to an embodiment of the present invention.

FIG. 1 is a flowchart illustrating a method for updating BMS software of an energy storage system having different internal and external communication methods according to an embodiment of the present invention.

Hereinafter, a method for updating BMS software of an energy storage system having different internal and external communication methods according to an embodiment of the present invention will be described with reference to FIG. 1.

The internal and external different communication methods according to an embodiment of the present invention are that the BMS of the energy storage system and the external device communicate through the DC/DC converter. Specifically, the communication between the DC/DC converter and the external device uses the Modbus communication method, and the communication between the DC/DC converter and the BMS uses the CAN communication method.

Typically, to update BMS software, an external device using the CAN communication method used by the BMS is used.

However, as the communication methods of external devices have diversified, a method for updating BMS software using different internal and external communication methods has become necessary.

In the conventional technology for updating BMS software using different internal and external communication methods, a separate interface was provided to update the BMS software.

However, this method of updating BMS software using a separate interface does not separately check the update process during the update process, but only checks whether the update was completed normally after the update process is completely completed.

In other words, even if a problem occurs during the update process, the update process is completed before determining whether the update was successful. Therefore, even if a problem occurs during the update process, if it is determined that there is a problem with the update, the update must be performed again from the beginning. This makes the update time long and makes it difficult to determine at which stage of the update the problem occurred.

Therefore, in the present invention, a process for checking whether the update is being performed normally is added during the update process, so that if a problem occurs during the update process, the update is restarted immediately, thereby shortening the update time.

In addition, the present invention can quickly identify which update process a problem occurred in by checking whether the update is being performed normally during the update process.

FIG. 1 is a flowchart illustrating a method for updating BMS software of an energy storage system having different internal and external communication methods according to an embodiment of the present invention.

A method for updating BMS software of an energy storage system having different internal and external communication methods according to an embodiment of the present invention may include an update file validity verification step (S100) for verifying the validity of an update file in an external device, an update notification step (S200) for notifying the start of an update of a BMS in an external device, an update execution step (S300) for transmitting the prepared update file from the external device to the BMS through a DC/DC converter to perform an update, and an update termination step (S400) for verifying the update file transmitted from the BMS and terminating the update.

Meanwhile, each of the update notification step (S200), update execution step (S300), and update termination step (S400) may be configured to include a timeout check step (S500) that checks whether a timeout has occurred at each step.

Meanwhile, Fig. 2 is a flowchart showing the update file validity verification step (S100). The update file validity verification step (S100) includes an ID verification step (S110) for verifying the ID of the update file, a version information verification step (S120) for verifying the version information of the update file, a type information verification step (S130) for verifying the type information of the update file, a data size verification step (S140) for verifying the data size of the update file, and a CRC verification step (S150) for verifying the CRC (Cyclic Redundancy Check) of the update file. If an error is detected in any one or more of the ID verification step (S110), the version information verification step (S120), the type information verification step (S130), the data size verification step (S140), and the CRC verification step (S150), the BMS software update can be stopped.

Meanwhile, the DC/DC converter is configured to include a control unit, and the control unit of the DC/DC converter further includes an algorithm for converting the Modbus communication method (protocol) to a CAN communication method (protocol).

Meanwhile, an algorithm for converting the above Modbus communication method (protocol) to the CAN communication method (protocol) can use already known technology.

Below, the update file validity verification step (S100) is described with reference to Fig. 2.

First, the ID verification step (S110) verifies whether the ID of the update file matches the ID of the preset update file.

Next, the version information verification step (S120) is a step for checking whether the version information of the update file matches the version information to be newly updated.

Meanwhile, the above type information verification step (S130) is a step for verifying the data type of the update file information, and is a step for verifying whether it is a data type that can be installed in BMS.

Meanwhile, the CRC verification step (S150) is a step for performing a cyclic redundancy check, and is a known data transmission inspection method. Specifically, in the process of transmitting and receiving an update file, it is a data integrity inspection method that attaches a redundant code to each block or frame and transmits it to check if there is an error in the transmitted data, and checks if the transmitted content is accurate.

Meanwhile, if an error is detected in any one of the above-described ID verification step (S110), version information verification step (S120), type information verification step (S130), data size verification step (S140), and CRC verification step (S150), it is determined that there is a problem with the update file.

If it is determined that there is a problem with the update file, it is desirable that the BMS update process, including the update request step, update execution step, and update termination step, not be performed.

Meanwhile, FIG. 3 is a drawing showing the sequence of an update notification step (S200) according to an embodiment of the present invention.

The above update notification step (S200) may be configured to include a communication baud rate setting step of transmitting a predetermined baud rate setting signal from an external device to a DC/DC converter via a modbus communication method and setting a communication baud rate by receiving a response from the DC/DC converter, an update start signal transmission step of transmitting an update start signal from an external device to the DC/DC converter via a modbus communication method, and an update acceptance step of transmitting an update start signal from the DC/DC converter that has received the update start signal to a BMS via a CAN communication method and receiving an update acceptance signal from the BMS.

Meanwhile, the update acceptance step may be configured to include an authentication request step of transmitting a BMS authentication request signal from the DC/DC converter to the BMS via a CAN communication method and receiving a response signal from the BMS, a security connection request step of transmitting a secure connection request signal from the DC/DC converter to the BMS via a CAN communication method and receiving a response signal from the BMS, a memory connection request step of transmitting a memory connection request signal from the DC/DC converter to the BMS via a CAN communication method and receiving a response signal from the BMS, and an update start approval step of transmitting an update start approval signal to the external device when the BMS transmits a normal response signal for all of the update request step, the authentication request step, the security connection request step, and the memory connection request step.

Meanwhile, the above time-out confirmation step (S500) confirms whether a time-out has occurred in the update notification step described above.

Specifically, it is desirable that the update notification step be completed within a given time (20 seconds), and if the above-described update request step is not completed within the given time (20 seconds), a timeout occurs and the update notification step can be restarted from the beginning.

Meanwhile, the number of times a timeout occurs and the update notification step (S200) is restarted can be counted and stored in the BMS, and if the number of times the update notification step stored in the BMS is restarted exceeds a predetermined number, it can be determined that the update is impossible.

Meanwhile, FIG. 4 is a drawing showing an update execution step (S300) according to an embodiment of the present invention.

The above update execution step (S300) is configured to include an update file transmission step between an external device and a DC/DC converter in which the external device reads the update file of a predetermined number of bytes and transmits the read update file of a predetermined number of bytes to the DC/DC converter via a modbus communication method, an update file transmission step between a DC/DC converter and a BMS in which the DC/DC converter transmits the transmitted update file of the predetermined number of bytes to a BMS, a reception confirmation signal transmission step in which the BMS transmits a reception confirmation signal indicating that the update file of the predetermined number of bytes has been received to the DC/DC converter, and a normal reception completion signal transmission step in which the DC/DC converter receiving the reception confirmation signal transmits a normal reception completion signal to the external device.

In other words, the update execution step of the present invention is one repetition cycle in which the update file transmission step between the external device and the DC/DC converter, the update file transmission step between the DC/DC converter and the BMS, the reception confirmation signal transmission step, and the normal reception completion signal transmission step are sequentially performed. Meanwhile, the update execution step can be repeatedly performed until the entire update file is divided into the predetermined bytes and all are transmitted.

Meanwhile, if the file transfer step and the reception confirmation signal transmission step between the DC/DC converter and the BMS take longer than the first reference time, a timeout occurs, and if the file transfer step or the settlement reception completion signal transmission step between the external device and the DC/DC converter takes longer than the second reference time, a timeout occurs.

Meanwhile, the predetermined number of bytes dividing the above update file may be 8 bytes, which is the data size of standard CAN communication.

Meanwhile, the above time-out confirmation step (S500) confirms whether a time-out has occurred in the update execution step described above.

Meanwhile, in the prior art, after transmitting all update files in the update execution stage, it was checked whether the update files were transmitted normally. Therefore, there was a problem of transmitting all update files even if a transmission error occurred in the middle of transmitting the update files.

In contrast, the present invention measures the time required to transmit an update file divided into 8-byte units, thereby confirming whether the update file divided into 8-byte units has been transmitted normally.

Meanwhile, if it is confirmed that the update file has been transmitted normally and the update file divided into 8 bytes has been transmitted normally, the next update file divided into 8 bytes will be transmitted continuously.

However, if an error occurs during the process of transmitting the update file by dividing it into 8 bytes and it is not transmitted normally, a timeout occurs and the update file is retransmitted from the first 8 bytes.

When checking whether an update file divided into 8-byte units is normally transmitted using the above-described method, if a transmission error occurs in the middle of transmitting the update file, the update data to be transmitted later is not transmitted and is retransmitted from the first 8 bytes of the update file. Therefore, even if a transmission error occurs in the middle of transmitting the update file, the time required to transmit the update file can be shortened compared to the conventional technology in which the entire update file is transmitted and then retransmitted from the beginning if an error is found.

For example, it is preferable that the update file transmission step and the reception confirmation signal transmission step between the DC/DC converter and the BMS are performed within the first reference time (2 seconds), and the update file transmission step and the normal reception completion signal transmission step between the external device and the DC/DC converter are preferably performed within the second reference time (7 seconds).

Meanwhile, if the update file transmission step and the reception confirmation signal transmission step between the DC/DC converter and the BMS are not performed within the first reference time, or if the update file transmission step or the normal reception completion signal transmission step between the external device and the DC/DC converter are not performed within the second reference time, a time out occurs and the update execution step can be restarted from the beginning.

Meanwhile, the BMS can count the number of times the update execution step is restarted due to a timeout, and if the number of times the update execution step stored in the BMS is restarted exceeds a certain number, it can be determined that the update is impossible.

Meanwhile, FIG. 5 is a drawing showing an update termination step (S400) according to an embodiment of the present invention.

The above update termination step (S400) may be configured to include an update data transmission completion signal transmission step for transmitting a signal from an external device to the DC/DC converter indicating that update data transmission is complete, a BMS self-check step for transmitting a self-check request signal from the DC/DC converter to the BMS and receiving a self-check result, a log record request signal transmission step for transmitting a log record request signal requesting recording when there is no abnormality in the result of the self-check step, a communication termination signal transmission step for transmitting a communication termination signal from the DC/DC converter to the BMS after the log recording is complete, and a BMS software update completion signal transmission step for transmitting a signal from the DC/DC converter to the external device indicating that the BMS has normally completed the update.

Meanwhile, the above time-out confirmation step (S500) confirms whether a time-out has occurred in the above-described update termination step (S400).

It is desirable that the above-described update termination steps are all completed within a given time (20 seconds), and if the above-described update termination steps are not completed within a given time (20 seconds), a timeout occurs and the update termination step (S400) is restarted from the beginning.

Meanwhile, the BMS can count and record the number of times the above timeout occurs and the update termination step (S400) is restarted, and if the number of times the update termination step recorded in the BMS is restarted exceeds a predetermined number, it can be determined that the update is impossible.

Meanwhile, in the timeout confirmation step (S500) performed in each of the update notification step (S200), update execution step (S300), and update termination step (S400), if a timeout occurs in each step, the step in which the timeout occurred is judged to have failed as shown in Fig. 6, and the step in which the timeout occurred is restarted from the beginning. The number of restarts is counted, and if the number of restarts is greater than a predetermined number, it can be judged that the update is impossible.

Meanwhile, if it is determined that an update is not possible, an update file deletion decision step can be performed to determine whether to delete the update file.

Meanwhile, the above update file deletion decision step is a step for deleting new update files if the existing BMS software remains.

For example, if three timeouts occur during the update execution step and the update execution step is restarted three times, it is determined that the update is not possible because three timeouts occur and the number of restarts is more than three, and if there is existing BMS software, the existing BMS software can be continued and the new update file deletion decision step can be performed to delete the new update file.

On the other hand, if there is no existing BMS software, even if the BMS software update fails, the new update file can be maintained without being deleted because there is no software that operates the BMS.

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.

Claims (8)

In a method of updating the BMS software of an ESS where the outside and inside use different communication methods,
Update file validation step to check the validity of update files on external devices;
Update notification step to notify the start of an update of the BMS from an external device;
An update execution step of performing an update by transmitting the prepared update file from an external device to the BMS via a DC/DC converter;
An update termination step that verifies the update files transmitted from BMS and terminates the update;
It consists of, including:
Each of the above update notification step, update execution step, and update termination step is a timeout check step that checks whether a timeout occurs at each step;
Consists of including,
The above update steps are:
An update file transmission step between an external device and a DC/DC converter, in which the external device reads a predetermined number of bytes of the update file and then transmits the read update file of the predetermined number of bytes to the DC/DC converter;
An update file transmission step between a DC/DC converter and a BMS, which transmits an update file of a predetermined number of bytes transmitted in the update file transmission step from the DC/DC converter to the BMS;
A reception confirmation signal transmission step for transmitting a reception confirmation signal indicating that the update file of the predetermined number of bytes has been received from the BMS to the DC/DC converter; and
A normal reception completion signal transmission step for transmitting a normal reception completion signal from a DC/DC converter that has received the above reception confirmation signal to an external device;
It consists of, including:
A BMS software update method characterized in that communication between an external device and a DC/DC converter is performed using MODBUS communication, and communication between the DC/DC converter and the BMS is performed using CAN communication.
In claim 1,
The above update file validation step is:
ID verification step to check the ID of the update file;
Version information check step to check the version information of the update file;
Type information verification step to check the type information of the update file;
Data size check step to check the data size of the update file;
CRC verification step to check the CRC (Cyclic Redundancy Check) of the update file;
It consists of, including:
A BMS software update method characterized in that if an error is detected in one or more of the ID verification step, version information verification step, type information verification step, data size verification step, and CRC verification step, the BMS software update is stopped by determining that the update file is invalid.
In claim 1,
The above update notification steps are:
A communication baud rate setting step of transmitting a predetermined baud rate setting signal from an external device to a DC/DC converter in a Modbus communication manner and receiving a response from the DC/DC converter to set the communication baud rate;
An update start signal transmission step for transmitting an update start signal from an external device to a DC/DC converter via Modbus communication;
An update acceptance step in which an update start signal is transmitted to a BMS by a CAN communication method from a DC/DC converter that has received the above update start signal, and an update acceptance signal is received from the BMS;
It consists of, including:
A BMS software update method characterized in that a time out occurs if the above update notification step is not completed within a predetermined time.
In claim 3,
The above update acceptance steps are:
An authentication request step of transmitting a BMS authentication request signal from a DC/DC converter to a BMS using a CAN communication method and receiving a response signal from the BMS;
A secure connection request step of transmitting a secure connection request signal requesting a secure connection from a DC/DC converter to a BMS via a CAN communication method and receiving a response signal from the BMS;
A memory access request step for transmitting a memory access request signal requesting memory access from a DC/DC converter to a BMS in a CAN communication manner and receiving a response signal from the BMS; and
In the above BMS, when a normal response signal is transmitted for all of the update request step, the authentication request step, the secure access request step, and the memory access request step, the DC/DC converter transmits an update start approval signal to the external device;
A BMS software update method characterized by comprising:
In claim 1,
If the file transfer step and the reception confirmation signal transmission step between the DC/DC converter and the BMS take longer than the first reference time, or if the file transfer step or the settlement reception completion signal transmission step between the external device and the DC/DC converter takes longer than the second reference time, a timeout occurs.
If a timeout occurs, the update file will be retransmitted from the beginning.
The above update steps are:
A BMS software update method characterized in that the update file is divided into the above-mentioned predetermined bytes and repeatedly performed until all are transmitted.
In claim 1,
The above update completion steps are:
An update data transmission completion signal transmission step for transmitting a signal indicating that the update data transmission from an external device to the DC/DC converter has been completed;
A BMS self-check step that transmits a self-check request signal from the DC/DC converter to the BMS and receives the self-check result;
A log record request signal transmission step for transmitting a log record request signal requesting a record when there is no abnormality in the result of the above self-check step;
After the above log recording is completed, a communication termination signal transmission step for transmitting a communication termination signal from the DC/DC converter to the BMS; and
A BMS software update completion signal transmission step in which the DC/DC converter transmits a signal to an external device that the BMS has successfully completed the update;
It consists of, including:
A BMS software update method characterized in that a time out occurs if the above update termination step is not completed within a predetermined time.
In claim 1,
The above time-out check step is
If a timeout occurs at each step, the update is judged to have temporarily failed and the step where the timeout occurred is restarted from the beginning.
If the number of times each of the above steps is restarted is greater than the specified number of times,
An update file deletion decision step that determines that an update is not possible and decides whether to delete the update file;
A BMS software update method characterized by performing the following.
In claim 7,
The above update file deletion decision step is,
If you still have existing BMS software files,
Delete the above update file,
If there is no existing BMS software left,
A BMS software update method characterized by maintaining the above update file.

Images