System operation state monitoring method and system for fault occurrence of battery management system

Abstract

The invention discloses a system operation state monitoring method and system for battery management system fault occurrence. The method comprises the following steps: constructing a linked list D data structure comprising M data cache positions; constructing a system state cache data structure comprising N data areas; updating the system operation state data in the data area regularly and sequentially; when monitoring that a fault occurs, recording a fault ID and a fault occurrence timestamp and storing the fault ID and the fault occurrence timestamp to a blank data cache position, and storing all system operation state data in a system state cache data structure corresponding to a fault occurrence time point to the blank data cache position; cyclically traversing the linked list, and judging whether a fault occurrence timestamp exists in the current data cache position or not and whether preset delay fixed time from the fault occurrence timestamp is met or not; if yes, storing all the system running state data in the system state cache data structure corresponding to the time point when the preset delay fixed time reaches to the current data cache position, transferring the data in the current data cache position together, and judging the next data cache position.

Description

Technical Field

[0001] The present invention relates to the technical field of system operation status monitoring, and in particular to a method for monitoring the system operation status when a battery management system failure occurs and a system for monitoring the system operation status when a battery management system failure occurs. Background Art

[0002] At present, battery management systems all have a method to record system operation failures. When a failure occurs, the battery management system will record some state quantities of the system at the time of the failure and store them in the corresponding storage medium. Then, at a later time, other devices (such as APPs developed by computers) will read them through a fixed communication protocol and display them on the corresponding interface.

[0003] In the prior art, the battery management system only records the system operation information when a fault occurs. This leads to a problem that the system status for a continuous period of time before the fault occurs and the system status for a continuous period of time after the fault occurs cannot be recorded. Only the system status from the occurrence of the fault to a certain moment after the fault occurs can be recorded. The status at this single moment cannot reflect the real status of the system at the time of the fault. The real status when the fault occurs should be jointly determined by the status of the system in a continuous period of time before and after the fault occurs. In order to solve this technical problem, the present invention designs a method and system for monitoring the system operation status when a battery management system fault occurs. Summary of the invention

[0004] In view of the problems and shortcomings of the prior art, the present invention provides a method and system for monitoring the system operating status of a battery management system when a fault occurs.

[0005] The present invention solves the above technical problems through the following technical solutions: The present invention provides a method for monitoring the system operation status of a battery management system when a fault occurs, which is characterized in that it comprises the following steps: S1. Construct a linked list D data structure, wherein the linked list D data structure includes M data backup areas, each of which is used as a data cache location, and each of which is composed of a pre-failure backup area 1, a post-failure backup area 2, and a failure backup area, and M is a positive integer; S2. Build a system status cache data structure. The system status cache data structure is shared by M data backup areas. The system status cache data structure includes N data areas. Each data area is used to cache a copy of system operation status data. N is a positive integer. S3, for the system status cache data structure, regularly and sequentially updating the system operation status data in the data area of ​​the system status cache data structure at set intervals, and using the updated system operation status data to overwrite the original system operation status data in the currently updated data area; Constantly monitor whether there is a fault. Whenever a fault is detected, record the fault ID and the timestamp of the fault and cache them in the fault backup area of ​​the blank data cache position. Cache all system operation status data in the system status cache data structure corresponding to the time of the fault to the pre-fault backup area 1 of the blank data cache position. Loop through the M data cache positions in the linked list D data structure to determine whether the current data cache position has a cached fault occurrence timestamp and whether it meets the preset fixed delay time from the fault occurrence timestamp. If both are yes, cache all system operation status data in the system status cache data structure corresponding to the moment when the preset fixed delay time is reached to the post-fault backup area 2 of the current data cache position, and move the data cached in the pre-fault backup area 1, the backup area at the time of the fault, and the post-fault backup area 2 in the current data cache position to the storage medium. The current data cache position becomes a blank data cache position, and the next data cache position is determined. Otherwise, the next data cache position is directly determined.

[0006] The present invention also provides a system operation status monitoring system for a battery management system failure, which is characterized in that it includes a first data structure building module, a second data structure building module, a data updating module, a first fault monitoring module and a second fault monitoring module; The first data structure building module is used to build a linked list D data structure, the linked list D data structure includes M data backup areas, each data backup area is used as a data cache location, each data backup area is composed of a pre-failure backup area 1, a post-failure backup area 2 and a failure backup area, and M is a positive integer; The second data structure building module is used to build a system status cache data structure, the system status cache data structure is shared by M data backup areas, the system status cache data structure includes N data areas, each data area is used to cache a copy of system operation status data, and N is a positive integer; The data update module is used to update the system operation status data in the data area of ​​the system state cache data structure at set intervals, and to overwrite the original system operation status data with the updated system operation status data in the currently updated data area; The first fault monitoring module is used to continuously monitor whether a fault occurs, and whenever a fault is monitored, the fault ID and the timestamp of the fault are recorded and cached in the fault backup area of ​​the blank data cache position, and all system operation status data in the system status cache data structure corresponding to the time point of the fault occurrence are cached in the pre-fault backup area 1 of the blank data cache position; The second fault monitoring module is used to loop through the M data cache positions in the linked list D data structure, determine whether the current data cache position has a cached fault occurrence timestamp and whether it meets the preset fixed delay time from the fault occurrence timestamp, and if both are yes, cache all system operation status data in the system status cache data structure corresponding to the moment when the preset fixed delay time is reached to the post-fault backup area 2 of the current data cache position, and move the data cached in the pre-fault backup area 1, the fault backup area and the post-fault backup area 2 in the current data cache position to the storage medium, the current data cache position becomes a blank data cache position, and the next data cache position is determined, otherwise the next data cache position is directly determined.

[0007] The positive and progressive effects of the present invention are: The present invention is used to realize that when a fault occurs, the system can store the system operation status data for a period of time before and after the fault occurs. When the fault data is subsequently read through the APP, the entire continuous system status data before and after the fault occurs can be accessed. In simple terms, when the fault data occurs, the status of the period of time before the fault occurs and the time when the fault occurs are cached, and then after the system continues to run for a fixed period of time, the system status during this period and the previously cached system status data are stored together in the storage medium. The entire fault storage logic is performed continuously, and the status information of all faults within a period of time before and after the occurrence of the fault can be stored for easy viewing by users. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 It is a block diagram of the composition of the linked list D data structure of the present invention.

[0009] Figure 2 It is a block diagram of the composition of the system status cache data structure of the present invention.

[0010] Figure 3 The flowchart of Task 1 of the present invention is for updating the system status cache data structure.

[0011] Figure 4 This is the workflow diagram of Task 3 for updating the content of the "Link List D Data Structure" of the present invention.

[0012] Figure 5It is a block diagram of the working principle of the system operation status monitoring system of the present invention.

[0013] Figure 6 It is the experimental effect diagram of the present invention. DETAILED DESCRIPTION

[0014] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0015] like Figure 1-4 As shown, this embodiment provides a method for monitoring the system operation status when a battery management system failure occurs, which includes the following steps: S1. Construct a linked list D data structure. The linked list D data structure includes M data backup areas. Each data backup area is used as a data cache location. Each data backup area consists of a pre-failure backup area 1, a failure backup area, and a post-failure backup area 2 (see Figure 1 ), M is a positive integer.

[0016] In this step, the pre-failure backup area 1 is used to temporarily store data before the failure occurs, the on-failure backup area is used to temporarily store data when the failure occurs, and the post-failure backup area 2 is used to temporarily store data after the failure occurs.

[0017] S2. Build a system status cache data structure. The system status cache data structure is shared by M data backup areas. The system status cache data structure includes N data areas (see Figure 2 ), each data area is used to cache a copy of system operation status data, and N is a positive integer.

[0018] S3. For the system status cache data structure, the system operation status data in the data area of ​​the system status cache data structure is updated in sequence at set intervals, and the updated system operation status data is used to overwrite the original system operation status data in the currently updated data area.

[0019] See Figure 3 , Task 1 further specifically includes: S311. Initialize n=1.

[0020] S312: When the set interval time is reached, the system operation status data in the nth data area of ​​the system status cache data structure is updated regularly and the original system operation status data in the nth data area is overwritten.

[0021] S313, assign n=n+1, determine whether n>N, if not, go to step S312, if yes, go to step S314.

[0022] S314, assign n=1, and repeat step S312.

[0023] Task 2: Continuously monitor whether there is a fault. Whenever a fault is monitored, record the fault ID and fault occurrence timestamp of the fault, and cache them in sequence in the fault-time backup area of ​​the blank data cache position. Take out all system operation status data in the system status cache data structure corresponding to the time when the fault occurred in order from old to new, and cache them in the pre-fault backup area 1 of this blank data cache position. When the fault is cached to the Mth data cache position, the next sequence is the first blank data cache position starting from the first data cache position.

[0024] Task 3: Loop through the M data cache positions in the linked list D data structure, determine whether the current data cache position has a cached fault occurrence timestamp and whether it meets the preset fixed delay time from the fault occurrence timestamp. If both are true, all system operation status data in the system status cache data structure corresponding to the moment when the preset fixed delay time is reached are taken out in order from old to new, and cached to the post-fault backup area 2 of the current data cache position, and the data cached in the pre-fault backup area 1, the backup area at the time of the fault, and the post-fault backup area 2 in the current data cache position are moved to the storage medium together, and the current data cache position becomes a blank data cache position, and the next data cache position is determined, otherwise the next data cache position is directly determined.

[0025] See Figure 4 , Task 3 further specifically includes: S321. Initialize m=1.

[0026] S322 , determine whether the mth data cache location has a fault occurrence timestamp cached, if yes, proceed to step S323 , if not, proceed to step 325 .

[0027] S323, determine whether the preset fixed delay time from the fault occurrence timestamp is met, if so, proceed to step S324, if not, proceed to step 325.

[0028] S324. All system operation status data in the system status cache data structure corresponding to the time point when the preset delay fixed time is reached are taken out in order from old to new, and cached in the post-failure backup area 2 of the m-th data cache position, and the data cached in the pre-failure backup area 1, the backup area at the time of the failure, and the post-failure backup area 2 in the m-th data cache position are moved to the storage medium together, and the m-th data cache position becomes a blank data cache position, and the process proceeds to step S325.

[0029] S325, assign m=m+1, determine whether m>M, if not, go to step S322, if yes, go to step S326.

[0030] S326. Assign m=1, and repeat step S322.

[0031] In this embodiment, a "system status cache data structure" is set up (the data cache position in the "linked list D data structure" is shared, and each data area in the system status cache data structure caches a system operation status data). The structure contains N data areas. The structure will call task 1 to update the system operation status data in the data area in a regular and sequential manner; the update time interval between two adjacent data areas from data area 1 to data area N is the same, which ensures that the data in the data area can always be acquired sequentially from old to new.

[0032] In this embodiment, a "link list D data structure" is set up, which includes M data backup areas, each of which is a data cache position, such as position 1 to position M; each data backup area contains a pre-fault backup area 1, a fault backup area, and a post-fault backup area 2. The pre-fault backup area 1 is used to cache the data in the system status cache data structure before the fault, the fault backup area is used to cache data such as the fault ID and the time of the fault, and the post-fault backup area 2 is used to cache the data in the system status cache data structure after the fault. Among them, the data in the pre-fault backup area 1 and the data in the post-fault backup area 2 are both from the system status cache data structure; the data structure stored in the area from position 1 to position M in the linked list D data structure is the same, which is the system status data within a period of time before and after the fault occurs.

[0033] This embodiment includes a task 1 corresponding to the "system status cache data structure", which is responsible for periodically updating the system operation status data in the data area of ​​the system status cache data structure; for example, when task 1 is called for the first time, the current data area index of the "system status cache data structure" is 1, and the task will store the current system operation status data in data area 1; when task 1 is called for the second time, the current data area index of the "system status cache data structure" is 2, and the task will store the current system operation status data in data area 2; when task 1 is called for the N+1th time, the current data area index of the "system status cache data structure" is 1, and the task will store the current system operation status data in data area 1 and overwrite the original system operation status data in data area 1; and so on, it keeps running.

[0034] This embodiment includes a task 2, which is responsible for continuously monitoring whether a fault occurs. Whenever a fault is monitored, the fault ID and the timestamp of the fault are recorded, and the fault ID and the current time (timestamp of the fault) of the fault are sequentially cached in the fault backup area of ​​the blank data cache position in the "link list D data structure". At the same time, at the moment of the fault, all system operation status data in the system status cache data structure are taken out in order from old to new, and stored in the pre-fault backup area 1 of the blank data cache position in the "link list D data structure", and then the data cache position will automatically move to the next blank data cache position. When the data cache position is originally the last position, the next position moved to is the first blank data cache position starting from the first data cache position.

[0035] This embodiment includes a task 3, which is first responsible for finding the position m corresponding to the alarm that has not been stored in the storage medium in the "link list D data structure", and then continuously detecting whether the current system timestamp has exceeded the specified time (for example, 10 seconds, i.e., the preset delay fixed time) relative to the timestamp of the fault occurrence time at the position m (m=1...M) in the "link list D data structure". If the specified time is exceeded, task 3 immediately stores the data in the entire "system status cache data structure" in the order from old to new in the post-fault backup area 2 at the position m (m=1...M) in the "link list D data structure"; in this way, the system operation status data corresponding to a continuous period before and after the fault occurs can be formed together with the pre-fault backup area 1 at the position m (m=1...M) in the "link list D data structure". At the same time, task 3 will store all the data at the position m in the entire "link list D data structure" into the storage medium; then the position m will automatically move to the next one. When m is originally the last position, the next position moved to is the first position.

[0036] During the whole process, Task 1, Task 2 and Task 3 will run once at a corresponding frequency. Task 1 records the system operation status data of a continuous period of time in real time through the "system status cache data structure". When Fault 1 occurs, Task 2 records the timestamp B1 when Fault 1 occurs, and caches the fault ID1 and the corresponding "system status cache data structure" from old to new system status data to the corresponding position in the current position 1 of the "linked list D data structure", and the data "system status cache data structure" will continue to update the data regularly, and then the storage position of the "linked list D data structure" will shift to the next position 2. When the next Fault 2 occurs, the system will again cache the timestamp B2 when Fault 2 occurs, Fault ID2 and the "system status cache data structure" from old to new system operation status data to the corresponding position in position 2 of the "linked list D data structure" according to the above process, and then the storage position of the "linked list D data structure" will shift to the next position 3, and so on. At the same time, Task 3 will also scan the timestamp B1 when the fault occurred at the current position 1 (the oldest timestamp position) in the "Link List D Data Structure". When it is determined that the fault record timestamp B1 in the current position 1 in the "Link List D Data Structure" has continued for a fixed time, the system operation status data from old to new in the "System Status Cache Data Structure" will be quickly cached to another corresponding position in the current position 1 in the "Link List D Data Structure". In this way, the data in the current position 1 in the "Link List D Data Structure" can record all the system operation status data in a continuous period of time before and after the timestamp B1 when the fault 1 occurred. Then Task 3 will quickly store the information in position 1 into the storage medium, clear position 1, and quickly move position m (m=1...M) of the "Linked List D Data Structure" to the next position, and continue to scan the timestamp B2 of the fault 2 record in position 2 in the "Linked List D Data Structure". When it is determined that the fault record timestamp B2 in the current position 2 in the "Linked List D Data Structure" has continued for a fixed time, the system operation status data from old to new in the "System Status Cache Data Structure" will be quickly cached to another corresponding position in the current position 2 in the "Linked List D Data Structure"; if it is determined that the fault record timestamp B2 in the current position 2 in the "Linked List D Data Structure" has not met the preset delay fixed time, continue to judge the next position.

[0037] By analogy, when running at this rhythm, Task 2 continuously updates the faults stored in the "Link List D Data Structure" and their corresponding timestamps and system operation status data, while Task 3 continuously detects whether the delayed storage time after the fault stored in the "Link List D Data Structure" meets the requirements. After the specified time is reached, Task 3 will store the corresponding alarm information in the "Link List D Data Structure" into the storage medium. The cooperation between Task 2 and Task 3 can always ensure that after Task 3 stores the fault information of one position and moves to the next position, the fault corresponding to the next position must have occurred after the fault of the previous position, thereby ensuring the continuity of the storage of the entire status information.

[0038] See Figure 5 This embodiment also provides a system operation status monitoring system for a battery management system failure, which includes a first data structure construction module 1, a second data structure construction module 2, a data update module 3, a first fault monitoring module 4 and a second fault monitoring module 5.

[0039] The first data structure construction module 1 is used to construct a linked list D data structure, which includes M data backup areas. Each data backup area serves as a data cache location. Each data backup area is composed of a pre-failure backup area 1, a post-failure backup area 2 and a failure backup area. M is a positive integer.

[0040] The second data structure building module 2 is used to build a system status cache data structure, which is shared by M data backup areas. The system status cache data structure includes N data areas, each of which is used to cache a system operation status data, and N is a positive integer.

[0041] The data update module 3 is used to update the system operation status data in the data area of ​​the system status cache data structure at set intervals, and to overwrite the original system operation status data with the updated system operation status data in the currently updated data area.

[0042] Optimally, the data updating module 3 includes a first initialization unit, an updating unit, a first assignment judgment unit and a first direct assignment unit.

[0043] The first initialization unit is used to initialize n=1.

[0044] The updating unit is used to regularly update the system operation status data in the nth data area of ​​the system state cache data structure when the set interval time is reached and overwrite the original system operation status data in the nth data area.

[0045] The first assignment judgment unit is used to assign n=n+1, judge whether n>N, call the update unit when it is no, and call the first direct assignment unit when it is yes.

[0046] The first direct assignment unit is used to assign n=1 and call the update unit.

[0047] The first fault monitoring module 4 is used to continuously monitor whether a fault occurs. Whenever a fault is monitored, the fault ID and fault occurrence timestamp of the fault are recorded, and they are cached in sequence in the fault-time backup area of ​​the blank data cache position. All system operation status data in the system status cache data structure corresponding to the time when the fault occurred are taken out in order from old to new, and cached in the pre-fault backup area 1 of the blank data cache position. When the fault is cached to the Mth data cache position, the next sequence is the first blank data cache position starting from the first data cache position.

[0048] The second fault monitoring module 5 is used to loop through the M data cache positions in the linked list D data structure, determine whether the current data cache position has a cached fault occurrence timestamp and whether it meets the preset fixed delay time from the fault occurrence timestamp, and if both are yes, cache all system operation status data in the system status cache data structure corresponding to the moment when the preset fixed delay time is reached at the current data cache position to the post-fault backup area 2 of the current data cache position, and move the data cached in the pre-fault backup area 1, the backup area at the time of the fault, and the post-fault backup area 2 in the current data cache position to the storage medium, the current data cache position becomes a blank data cache position, and the next data cache position is determined, otherwise the next data cache position is directly determined.

[0049] Optimally, the second fault monitoring module 5 includes a second initialization unit, a first fault judgment unit, a second fault judgment unit, a fault backup module, a second assignment judgment unit and a second direct assignment unit.

[0050] The second initialization unit is used to initialize m=1.

[0051] The first fault judgment unit is used to judge whether the mth data cache location has a cached fault occurrence timestamp, and to call the second fault judgment unit if it does, and to call the second value assignment judgment unit if it does not.

[0052] The second fault judgment unit is used to judge whether a preset fixed delay time from the fault occurrence timestamp is satisfied, and if so, the fault backup module is called, and if not, the second value assignment judgment unit is called.

[0053] The fault backup module is used to cache all system operation status data in the system status cache data structure corresponding to the moment when the preset delay fixed time is reached in the mth data cache position to the post-fault backup area 2 of the mth data cache position, and to transfer the data cached in the pre-fault backup area 1, the fault backup area and the post-fault backup area 2 in the mth data cache position to the storage medium, the mth data cache position becomes a blank data cache position, and the second assignment judgment unit is called.

[0054] The second assignment judgment unit is used to assign m=m+1, judge whether m>M, and call the first fault judgment unit when the answer is no, and call the second direct assignment unit when the answer is yes.

[0055] The second direct assignment unit is used to assign m=1 and repeatedly call the first fault judgment unit.

[0056] The present invention is used to realize that when a fault occurs, the system can store the system operation status data for a period of time before and after the fault occurs. When the fault data is subsequently read through the APP, the entire continuous system status data before and after the fault occurs can be accessed. In simple terms, when the fault data occurs, the status of the period of time before the fault occurs and the time when the fault occurs are cached, and then after the system continues to run for a fixed period of time, the system status during this period and the previously cached system status data are stored together in the storage medium. The entire fault storage logic is performed continuously, and the status information for a period of time before and after all faults occur can be stored.

[0057] The effects achieved by the present invention are as follows: Figure 6 When a fault occurs, the system records the time when any fault occurs and a continuous period of system operation status data according to the above process, and then accesses the storage information in the storage medium of the battery management system through a specific APP software, and displays it on the APP interface, as shown in the figure below. Figure 6The contents shown in the "Fault Data" column in the "Fault Data" column record the events that occurred in the battery management system at fixed times. Each of these events has a continuous system status information. For example, the "Single Voltage Overvoltage Level 1 Fault Disappeared" with directory 14 recorded in the "Fault Data" column can only see the time information such as the fault ID, fault type, fault value and fault disappearance time when the fault disappeared. Then click on this column, and the "Fault Data Record" column that pops up can continuously display the status of the "Single Voltage Overvoltage Level 1 Fault Disappeared" event for a period of time before and after it occurs. For example, the battery management system starts to drop voltage at time -14, and confirms the occurrence of the "Single Voltage Overvoltage Level 1 Fault Disappeared" event after a delay of 4 moments. From the moment -10, the highest single voltage of the system is maintained at 3300mV after the fault disappears. From the moment -17 to the moment 0, the first half of the time is the system operation status data before the fault disappears, and the second half of the time is the system operation status data maintained after the fault disappears. Other operation status data, such as "System Minimum Single Voltage", etc., have the same effect.

[0058] Although the specific embodiments of the present invention are described above, those skilled in the art should understand that these are only examples, and the protection scope of the present invention is defined by the appended claims. Those skilled in the art may make various changes or modifications to these embodiments without departing from the principles and essence of the present invention, but these changes and modifications all fall within the protection scope of the present invention.

Claims

1. A method for monitoring the system operation status of a battery management system failure, characterized in that: It includes the following steps: S1. Construct a linked list D data structure, wherein the linked list D data structure includes M data backup areas, each of which is used as a data cache location, and each of which is composed of a pre-failure backup area 1, a post-failure backup area 2, and a failure backup area, and M is a positive integer; S2. Build a system status cache data structure. The system status cache data structure is shared by M data backup areas. The system status cache data structure includes N data areas. Each data area is used to cache a copy of system operation status data. N is a positive integer. S3, for the system status cache data structure, regularly and sequentially updating the system operation status data in the data area of ​​the system status cache data structure at set intervals, and using the updated system operation status data to overwrite the original system operation status data in the currently updated data area; Constantly monitor whether there is a fault. Whenever a fault is detected, record the fault ID and the timestamp of the fault and cache them in the fault backup area of ​​the blank data cache position. Cache all system operation status data in the system status cache data structure corresponding to the time of the fault to the pre-fault backup area 1 of the blank data cache position. Loop through the M data cache positions in the linked list D data structure to determine whether the current data cache position has a cached fault occurrence timestamp and whether it meets the preset fixed delay time from the fault occurrence timestamp. If both are yes, cache all system operation status data in the system status cache data structure corresponding to the moment when the preset fixed delay time is reached to the post-fault backup area 2 of the current data cache position, and move the data cached in the pre-fault backup area 1, the backup area at the time of the fault, and the post-fault backup area 2 in the current data cache position to the storage medium. The current data cache position becomes a blank data cache position, and the next data cache position is determined. Otherwise, the next data cache position is directly determined.

2. The method for monitoring the system operation status of a battery management system failure as claimed in claim 1, characterized in that: Step S3 includes: S311, initialize n=1; S312, when the set interval time is reached, the system operation status data in the nth data area of ​​the system status cache data structure is updated regularly and the original system operation status data in the nth data area is overwritten; S313, assign n=n+1, determine whether n>N, if not, go to step S312, if yes, go to step S314; S314, assign n=1, and repeat step S312.

3. The method for monitoring the system operation status of a battery management system failure as claimed in claim 1, characterized in that: Step S3 includes: Continuously monitor whether there is a fault. Whenever a fault is monitored, record the fault ID and fault occurrence timestamp of the fault, and cache them in sequence in the fault-time backup area of ​​the blank data cache position. Take out all system operation status data in the system status cache data structure corresponding to the time when the fault occurred in order from old to new, and cache them in the pre-fault backup area 1 of the blank data cache position. When the fault is cached to the Mth data cache position, the next sequence is the first blank data cache position starting from the first data cache position.

4. The method for monitoring the system operation status of a battery management system failure as claimed in claim 1, characterized in that: Step S3 includes: S321, initialize m=1; S322, determine whether the mth data cache location has a fault occurrence timestamp cached, if yes, proceed to step S323, if not, proceed to step 325; S323, determine whether the preset delay fixed time from the fault occurrence timestamp is met, if yes, proceed to step S324, if not, proceed to step 325; S324, all system operation status data in the system status cache data structure corresponding to the time point when the preset delay fixed time is reached are taken out in order from old to new, and cached in the post-failure backup area 2 of the m-th data cache position, and the data cached in the pre-failure backup area 1, the backup area at the time of the failure, and the post-failure backup area 2 in the m-th data cache position are moved to the storage medium, and the m-th data cache position becomes a blank data cache position, and the process proceeds to step S325; S325, assign m=m+1, determine whether m>M, if not, go to step S322, if yes, go to step S326; S326. Assign m=1, and repeat step S322.

5. A system operating status monitoring system for a battery management system failure, characterized in that: It includes a first data structure building module, a second data structure building module, a data updating module, a first fault monitoring module and a second fault monitoring module; The first data structure building module is used to build a linked list D data structure, the linked list D data structure includes M data backup areas, each data backup area is used as a data cache location, each data backup area is composed of a pre-failure backup area 1, a post-failure backup area 2 and a failure backup area, and M is a positive integer; The second data structure building module is used to build a system status cache data structure, the system status cache data structure is shared by M data backup areas, the system status cache data structure includes N data areas, each data area is used to cache a copy of system operation status data, and N is a positive integer; The data update module is used to update the system operation status data in the data area of ​​the system state cache data structure at set intervals, and to overwrite the original system operation status data with the updated system operation status data in the currently updated data area; The first fault monitoring module is used to continuously monitor whether a fault occurs, and whenever a fault is monitored, the fault ID and the timestamp of the fault are recorded and cached in the fault backup area of ​​the blank data cache position, and all system operation status data in the system status cache data structure corresponding to the time point of the fault occurrence are cached in the pre-fault backup area 1 of the blank data cache position; The second fault monitoring module is used to loop through the M data cache positions in the linked list D data structure, determine whether the current data cache position has a cached fault occurrence timestamp and whether it meets the preset fixed delay time from the fault occurrence timestamp, and if both are yes, cache all system operation status data in the system status cache data structure corresponding to the moment when the preset fixed delay time is reached to the post-fault backup area 2 of the current data cache position, and move the data cached in the pre-fault backup area 1, the fault backup area and the post-fault backup area 2 in the current data cache position to the storage medium, the current data cache position becomes a blank data cache position, and the next data cache position is determined, otherwise the next data cache position is directly determined.

6. The system operating status monitoring system for a battery management system failure as claimed in claim 5, characterized in that: The data update module includes a first initialization unit, an update unit, a first assignment judgment unit and a first direct assignment unit; The first initialization unit is used to initialize n=1; The updating unit is used to regularly update the system operation status data in the nth data area of ​​the system status cache data structure when the set interval time is reached and overwrite the original system operation status data in the nth data area; The first assignment judgment unit is used to assign n=n+1, judge whether n>N, and call the update unit when it is no, and call the first direct assignment unit when it is yes; The first direct assignment unit is used to assign n=1 and call the update unit.

7. The system operating status monitoring system for a battery management system failure as claimed in claim 5, characterized in that: The first fault monitoring module is used to continuously monitor whether a fault occurs. Whenever a fault is monitored, the fault ID and fault occurrence timestamp of the fault are recorded, and they are cached in sequence in the fault backup area of ​​the blank data cache position. All system operation status data in the system status cache data structure corresponding to the time when the fault occurred are taken out in order from old to new, and cached in the pre-fault backup area 1 of the blank data cache position. When the fault is cached to the Mth data cache position, the next sequence is the first blank data cache position starting from the first data cache position.

8. The system operating status monitoring system for a battery management system failure as claimed in claim 5, characterized in that: The second fault monitoring module includes a second initialization unit, a first fault judgment unit, a second fault judgment unit, a fault backup module, a second assignment judgment unit and a second direct assignment unit; The second initialization unit is used to initialize m=1; The first fault judgment unit is used to judge whether the mth data cache location has a timestamp of the fault occurrence cached, and call the second fault judgment unit if it does, and call the second value assignment judgment unit if it does not; The second fault judgment unit is used to judge whether the preset delay fixed time from the fault occurrence timestamp is met, and call the fault backup module if it is, and call the second value assignment judgment unit if it is not; The fault backup module is used to take out all system operation status data in the system status cache data structure corresponding to the time point when the preset delay fixed time is reached in order from old to new, and cache them in the post-failure backup area 2 of the m-th data cache position, and move the data cached in the pre-failure backup area 1, the backup area at the time of the failure, and the post-failure backup area 2 in the m-th data cache position to the storage medium, the m-th data cache position becomes a blank data cache position, and calls the second assignment judgment unit; The second assignment judgment unit is used to assign m=m+1, judge whether m>M, and call the first fault judgment unit when the answer is no, and call the second direct assignment unit when the answer is yes; The second direct assignment unit is used to assign m=1 and repeatedly call the first fault judgment unit.

Images