Bidirectional daisy chain communication fault judgment method and system

Abstract

The invention relates to the technical field of communication fault judgment, and discloses a bidirectional daisy chain communication fault judgment method and system, which are characterized in that forward and reverse link independent data reading, verification and error counting are taken as the core, and threshold values are continuously compared, so that forward and reverse failures can be accurately distinguished and accidental misjudgment can be eliminated when a single link fails; when the nodes fail, the fault nodes or daisy chain communication faults are quickly locked through bidirectional data cross validation; the single voltage and temperature of each node are respectively and independently counted and verified, and the abnormity is accurately identified; and the system can immediately execute protection measures such as node isolation and link switching according to a diagnosis result, thereby preventing fault diffusion and comprehensively ensuring long-term safe and stable operation of the battery management system.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication fault judgment, and in particular to a bidirectional daisy chain communication fault judgment method and system. BACKGROUND

[0002] With the continuous development and wide application of daisy chain technology in the field of energy storage systems, under the architecture of centralized battery management system (BMS), the number of battery packs is increasing. Due to the expansion of the system scale, the number of single cells connected in series is also increasing. Inside each battery pack, multiple front-end cell acquisition chips (AFEs) are usually integrated and configured to achieve accurate acquisition and monitoring of various parameters of the cells. With the increase in the number of battery packs and the number of AFEs in each battery pack, the total number of nodes of the entire energy storage system is continuously increasing.

[0003] The increase in the number of nodes makes the system architecture more complex, which in turn increases the probability of system failure during operation. Among them, daisy chain communication failure is one of the key factors affecting the stable operation of the system, and its accurate judgment and timely processing are crucial to ensure the safety and reliability of the energy storage system. Therefore, exploring an effective and stable daisy chain communication fault judgment method has become an important issue to be solved in the current energy storage system field.

[0004] However, as for the current daisy chain communication fault detection technology, there are still many problems to be solved. When the communication appears one-way abnormality, the existing detection means cannot effectively distinguish whether the fault type is line breakage or node device failure, which brings great difficulty to the accurate positioning and rapid repair of the fault. In addition, with the continuous increase in the number of AFEs in the system, the diagnostic error rate in the multi-layer data relay transmission process is significantly increased, especially in one-way communication mode, which is prone to misjudgment, seriously affecting the accuracy and timeliness of fault judgment.

[0005] In view of the above problems existing in the current daisy chain communication fault detection technology, in order to improve the stability and reliability of the energy storage system, reduce the failure rate, and improve the accuracy and timeliness of fault judgment, it is imperative to improve and innovate the existing technology.

[0006] The above information is given as background information only to assist with understanding the present disclosure, and does not determine or acknowledge whether any of the above is available as prior art against the present disclosure. SUMMARY

[0007] The present application provides a bidirectional daisy chain communication fault judgment method and system to solve the problems existing in the prior art.

[0008] To achieve the above object, the present application provides the following technical solutions.

[0009] In a first aspect, the present application provides a bidirectional daisy chain communication fault judgment method, which comprises:

[0010] S1, the master control system reads data of M slave AFE nodes through a daisy chain forward link respectively;

[0011] S2, a data acquisition and verification module verifies data according to the data returned by the slave AFE nodes to determine whether there is a verification error; if yes, S4 is executed, and if no, S3 is executed;

[0012] S3, a communication fault diagnosis module determines that the daisy chain forward link is normal, the M slave AFE nodes are normal, and the forward link data error cumulative count is cleared;

[0013] S4, the communication fault diagnosis module adds 1 to the forward link data error cumulative count, and determines whether the forward link data error cumulative count is greater than a second threshold; if yes, S5 is executed, and if no, the S2 is returned to be executed;

[0014] S5, the communication fault diagnosis module determines that the daisy chain forward link may have a fault;

[0015] S6, the master control system reads data of M slave AFE nodes through a daisy chain reverse link respectively;

[0016] S7, the data acquisition and verification module verifies data according to the data returned by the slave AFE nodes to determine whether there is a verification error; if yes, S9 is executed, and if no, S8 is executed;

[0017] S8, the communication fault diagnosis module determines that the daisy chain reverse link is normal, the M slave AFE nodes are normal, and the reverse link data error cumulative count is cleared;

[0018] S9, the communication fault diagnosis module adds 1 to the reverse link data error cumulative count, and determines whether the reverse link data error cumulative count is greater than a third threshold; if yes, S10 is executed, and if no, the S7 is returned to be executed;

[0019] S10, the communication fault diagnosis module determines that the daisy chain reverse link may have a fault;

[0020] S11, a system fault module gives a final fault judgment result according to the following strategy:

[0021] If the daisy chain forward link is normal, and the daisy chain reverse link may be faulty, it is determined that the daisy chain forward link is normal, M of the slave AFE nodes are normal, and the daisy chain reverse link is faulty.

[0022] If the daisy chain forward link may be faulty, and the daisy chain reverse link is normal, it is determined that the daisy chain reverse link is normal, M of the slave AFE nodes are normal, and the daisy chain forward link is faulty.

[0023] If the daisy chain forward link may be faulty, and the daisy chain reverse link may be faulty, it is determined that the daisy chain forward link is normal, the daisy chain reverse link is normal, and one of M of the slave AFE nodes is faulty.

[0024] Further, in the daisy chain communication fault judgment method, the S1 comprises:

[0025] S101, the master control system reads data of M slave AFE nodes through a daisy chain forward link, and judges whether the reading times are greater than a first threshold value; if yes, S102 is executed, and if no, S2 is executed.

[0026] S102, it is determined that it is in a power-on filtering stage, and abnormal data that may exist is discarded, and the S101 is returned.

[0027] Further, in the daisy chain communication fault judgment method, before the S1, the method further comprises:

[0028] S0, initialization power-on, the master control system wakes up M AFE nodes, and performs slave control configuration to obtain M slave AFE nodes.

[0029] Further, in the daisy chain communication fault judgment method, after the S11, the method further comprises:

[0030] S12, the system fault module determines the slave AFE node that exists fault from M slave AFE nodes according to the serial number of the slave AFE node that exists fault determined on the daisy chain forward link and the serial number of the slave AFE node that exists fault determined on the daisy chain reverse link.

[0031] In a second aspect, the application provides a daisy chain communication fault judgment system, which comprises M slave AFE nodes, a master control system, a data acquisition and verification module, a communication fault diagnosis module and a system fault module connected in sequence.

[0032] The master control system is used for reading data of M slave AFE nodes through a daisy chain forward link.

[0033] The data acquisition and verification module is configured to perform data verification according to the data returned by the slave AFE node, to determine whether there is a verification error;

[0034] The communication fault diagnosis module is configured to, if there is no verification error, determine that the daisy chain forward link is normal, the M slave AFE nodes are normal, and clear the forward link data error accumulation count;

[0035] The communication fault diagnosis module is further configured to, if there is a verification error, add 1 to the forward link data error accumulation count, and determine whether the forward link data error accumulation count is greater than a second threshold value;

[0036] The communication fault diagnosis module is further configured to, if the second threshold value is greater than the second threshold value, determine that the daisy chain forward link may have a fault;

[0037] The master control system is further configured to perform data reading on the M slave AFE nodes through the daisy chain reverse link;

[0038] The data acquisition and verification module is further configured to perform data verification according to the data returned by the slave AFE node, to determine whether there is a verification error;

[0039] The communication fault diagnosis module is further configured to, if there is no verification error, determine that the daisy chain reverse link is normal, the M slave AFE nodes are normal, and clear the reverse link data error accumulation count;

[0040] The communication fault diagnosis module is further configured to, if there is a verification error, add 1 to the reverse link data error accumulation count, and determine whether the reverse link data error accumulation count is greater than a third threshold value;

[0041] The communication fault diagnosis module is further configured to, if the third threshold value is greater than the third threshold value, determine that the daisy chain reverse link may have a fault;

[0042] The system fault module is configured to give a final fault determination result according to the following strategy:

[0043] If the daisy chain forward link is normal and the daisy chain reverse link may have a fault, it is determined that the daisy chain forward link is normal, the M slave AFE nodes are normal, and the daisy chain reverse link has a fault;

[0044] If the daisy chain forward link may have a fault and the daisy chain reverse link is normal, it is determined that the daisy chain reverse link is normal, the M slave AFE nodes are normal, and the daisy chain forward link has a fault;

[0045] If the daisy chain forward link can exist a fault, the daisy chain reverse link can exist a fault, it is determined that the daisy chain forward link is normal, the daisy chain reverse link is normal, and one of the M slave AFE nodes exists a fault.

[0046] Further, in the bidirectional daisy chain communication fault judgment system, the master control system is specifically used for:

[0047] The M slave AFE nodes are read through the daisy chain forward link, and it is judged whether the reading times are greater than a first threshold value; if yes, it is determined that it is in a power-on filtering stage, and the abnormal data can be discarded.

[0048] Further, in the bidirectional daisy chain communication fault judgment system, the master control system is further used for:

[0049] Initialization power-on, wake up the M AFE nodes, and perform slave control configuration to obtain the M slave AFE nodes.

[0050] Further, in the bidirectional daisy chain communication fault judgment system, the system fault module is further used for:

[0051] According to the sequence number of the slave AFE node determined to exist a fault on the daisy chain forward link and the sequence number of the slave AFE node determined to exist a fault on the daisy chain reverse link, the slave AFE node existing a fault is determined from the M slave AFE nodes.

[0052] In a third aspect, the present application provides a computer device, comprising a memory and a processor, the memory stores a computer program, and the processor realizes the bidirectional daisy chain communication fault judgment method provided in the first aspect when executing the computer program.

[0053] In a fourth aspect, the present application provides a computer readable storage medium, which stores computer executable instructions, and the computer executable instructions are executed by a computer processor to realize the bidirectional daisy chain communication fault judgment method provided in the first aspect.

[0054] Compared with the prior art, the present application has the following beneficial effects:

[0055] (1) One-way link fault identification can be accurately performed after single-link fault, and the continuity judgment eliminates the probability of misjudgment;

[0056] (2) After a certain node fault, the faulty node and the daisy chain communication fault can be identified through the combination of forward and reverse links;

[0057] (3) Each node monomer voltage, temperature judgment check is counted separately, and the voltage and temperature abnormality detection method is realized, so that the accuracy of fault judgment is effectively improved;

[0058] (4) Different faults can be handled and protected in time.

[0059] The present application has other characteristics and advantages, which will be apparent or will be described in detail in the accompanying drawings and subsequent specific embodiments incorporated herein, which together serve to explain the specific principles of the present application. BRIEF DESCRIPTION OF DRAWINGS

[0060] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed in the embodiment or prior art description will be briefly introduced below, and obviously, the drawings in the following description are only some embodiments of the present application, and those skilled in the art can obtain other drawings according to these drawings without creative labor.

[0061] Figure 1 is one of the flowcharts of a bidirectional daisy chain communication fault judgment method provided by the first embodiment of the present application;

[0062] Figure 2 is the second flowchart of a bidirectional daisy chain communication fault judgment method provided by the first embodiment of the present application;

[0063] Figure 3 is the third flowchart of a bidirectional daisy chain communication fault judgment method provided by the first embodiment of the present application;

[0064] Figure 4 is a functional module schematic diagram of a bidirectional daisy chain communication fault judgment system provided by the second embodiment of the present application;

[0065] Figure 5 is a structural schematic diagram of a computer device provided by the third embodiment of the present application. DETAILED DESCRIPTION

[0066] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed in the embodiment or prior art description will be briefly introduced below, and obviously, the drawings in the following description are only some embodiments of the present application, and those skilled in the art can obtain other drawings according to these drawings without creative labor.

[0067] The term "embodiment" is mentioned herein means that the specific features, structures, or characteristics described in connection with the embodiment can be included in at least one embodiment of the present application. The term "embodiment" appearing in various places in the specification does not necessarily refer to the same embodiment, nor does it particularly limit the independence or association between other embodiments. In principle, in the present application, as long as there is no technical contradiction or conflict, each technical feature mentioned in each embodiment can be combined in any way to form a corresponding implementable technical solution.

[0068] Unless otherwise defined, the meaning of technical terms used in the present application is the same as that generally understood by those skilled in the art to which the present application belongs; the use of related terms in the present application is only for the purpose of describing specific embodiments, and is not intended to limit the present application.

[0069] In the description of the present application, the phrase "and / or" is a description of the logical relationship between the objects, which means that there can be three relationships, for example, A and / or B, which means that there are three cases: A exists, B exists, and A and B exist at the same time. In addition, the character " / " in the present application generally represents that the associated objects before and after are a "or" logical relationship.

[0070] In the present application, the terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual quantity, primary and secondary or order relationship between the entities or operations.

[0071] In the present application, without more limitation, the "includes", "contains", "has" or other similar expressions used in the sentence are intended to cover non-exclusive inclusion, and these expressions do not exclude the presence of other elements in the process, method or product including the described elements, so that the process, method or product including a series of elements can not only include those limited elements, but also include other elements not explicitly listed, or also include the elements inherent to such process, method or product.

[0072] In the present application, the expressions such as "greater than", "less than", "exceed" are understood as not including the number; the expressions such as "above", "below", "within" are understood as including the number. In addition, in the description of the embodiments of the present application, the meaning of "multiple" is more than two (including two), and similar expressions related to "multiple" are also understood in this way, for example, "multiple groups", "multiple times" and the like, unless otherwise explicitly limited.

[0073] In the description of the embodiments of the present application, the spatial-related expressions used, such as "center", "lengthwise", "transverse", "length", "width", "thickness", "upper", "lower", "front", "back", "left", "right", "vertical", "horizontal", "vertical", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", "axial", "radial", "circumferential", and the like, indicate the orientation or positional relationship shown in the specific embodiments or the drawings, and are only for the convenience of describing the specific embodiments of the present application or for the reader to understand, and do not indicate or imply that the indicated device or component must have a particular position, a particular orientation, or be constructed or operated in a particular orientation, and therefore cannot be understood as a limitation on the embodiments of the present application.

[0074] Unless otherwise explicitly specified or limited, in the description of the embodiments of the present application, the terms "mount", "connect", "connect", "fix", "set", and the like should be understood broadly. For example, the "connection" can be fixed connection, or detachable connection, or integral setting; it can be mechanical connection, or electrical connection, or communication connection; it can be direct connection, or indirect connection through intermediate medium; it can be the internal communication of two elements or the interaction relationship between two elements. For those skilled in the art to which the present application belongs, the specific meaning of the above terms in the embodiments of the present application can be understood according to the specific circumstances.

[0075] Embodiment one

[0076] Please refer to Figure 1 , Figure 1 A flowchart of a bidirectional daisy chain communication fault judgment method provided for the first embodiment of the present application. The method specifically comprises the following steps:

[0077] S1, the master control system reads data from the M slave AFE nodes through the daisy chain forward link.

[0078] It should be noted that this step is the starting operation of the entire fault judgment process. The master control system as the core control unit uses the forward link of the daisy chain to sequentially obtain data from the M slave AFE (front-end battery chip) nodes, which provides basic data for subsequent data verification and fault analysis.

[0079] S2, the data acquisition verification module performs data verification according to the data returned by the slave AFE node to determine whether the verification is incorrect; if so, S4 is executed, if not, S3 is executed.

[0080] It's important to note that in this step, the data acquisition and verification module performs verification on the data returned by the slave AFE node. This verification checks for errors during data transmission. If errors are detected, this indicates a potential problem with forward link data transmission, and further processing proceeds to step S4. If the verification is correct, the process proceeds to step S3 to confirm that the daisy-chain forward link and the slave AFE node are functioning properly.

[0081] S3. The communication fault diagnosis module determines that the daisy chain forward link is normal, the M slave AFE nodes are normal, and clears the forward link data error cumulative count.

[0082] It should be noted that when the data verification is correct, the communication fault diagnosis module determines that the forward link and all slave AFE nodes are normal. At the same time, the forward link data error cumulative count is cleared to zero, indicating that the data transmission is normal, and the counting of possible subsequent errors begins again.

[0083] S4. The communication fault diagnosis module adds 1 to the forward link data error cumulative count and determines whether the forward link data error cumulative count is greater than a second threshold; if so, execute S5; if not, return to execute S2.

[0084] It should be noted that if a data verification error occurs, the communication fault diagnosis module increments the forward link data error cumulative count by 1 to record the number of errors that occurred. It then determines whether this count exceeds a pre-set second threshold. If so, it indicates that the forward link has detected data errors multiple times, confirming a fault and proceeding to step S5. If not, the module returns to step S2 to continue reading and verifying data to observe subsequent data transmission.

[0085] S5. The communication fault diagnosis module determines that a fault may exist in the daisy chain forward link.

[0086] It should be noted that when the cumulative count of forward link data errors exceeds the second threshold, the communication fault diagnosis module determines that the daisy chain forward link may have a fault. This is a preliminary fault judgment result, which provides direction for subsequent further investigation.

[0087] S6. The master control system reads data from the M slave control AFE nodes respectively through the daisy chain reverse link.

[0088] It's important to note that after completing data reading, verification, and fault diagnosis on the forward link, the master control system reads data again from the M slave AFE nodes via the daisy-chain's reverse link. This is a key step in bidirectional communication fault diagnosis, as the reverse link data transmission is compared and analyzed with the forward link.

[0089] S7, the data acquisition verification module performs data verification according to the data returned by the slave AFE node, to determine whether there is a verification error; if yes, S9 is executed, and if no, S8 is executed.

[0090] It should be noted that, similar to step S2, the data acquisition verification module verifies the data returned by the reverse link slave AFE node. According to the verification result, the subsequent operation is determined. If the verification is incorrect, step S9 is entered, and if there is no error, step S8 is entered.

[0091] S8, the communication fault diagnosis module determines that the daisy chain reverse link is normal, M slave AFE nodes are normal, and the reverse link data error accumulation count is cleared.

[0092] It should be noted that when the reverse link data verification is correct, the communication fault diagnosis module confirms that the reverse link and all slave AFE nodes are normal, and the reverse link data error accumulation count is cleared, and the subsequent possible reverse link error condition is restarted.

[0093] S9, the communication fault diagnosis module adds 1 to the reverse link data error accumulation count, and determines whether the reverse link data error accumulation count is greater than a third threshold; if yes, S10 is executed, and if no, S7 is returned.

[0094] It should be noted that if the reverse link data verification is incorrect, the communication fault diagnosis module adds 1 to the reverse link data error accumulation count, and determines whether the count exceeds a third threshold. If it exceeds, step S10 is entered, and if it does not exceed, step S7 is returned to continue reverse link data reading and verification.

[0095] S10, the communication fault diagnosis module determines that the daisy chain reverse link may have a fault.

[0096] It should be noted that when the reverse link data error accumulation count exceeds the third threshold, the communication fault diagnosis module determines that the daisy chain reverse link may have a fault, which is a preliminary fault determination result.

[0097] S11, the system fault module gives a final fault determination result according to the following strategy:

[0098] If the daisy chain forward link is normal, and the daisy chain reverse link may have a fault, it is determined that the daisy chain forward link is normal, M slave AFE nodes are normal, and the daisy chain reverse link has a fault.

[0099] If the daisy chain forward link may have a fault, and the daisy chain reverse link is normal, it is determined that the daisy chain reverse link is normal, M slave AFE nodes are normal, and the daisy chain forward link has a fault.

[0100] If the forward link and the backward link of the daisy chain are possibly faulty, it is determined that the forward link and the backward link of the daisy chain are normal, and one of the M slave AFE nodes is faulty.

[0101] It should be noted that the system fault module comprehensively determines the results of the forward link and the backward link. When the forward link is normal and the backward link is possibly faulty, it is further determined that the backward link is faulty, and the forward link and all slave AFE nodes are normal.

[0102] When the forward link is possibly faulty and the backward link is normal, the system fault module determines that the forward link is faulty, and the backward link and all slave AFE nodes are normal.

[0103] When the forward link and the backward link are possibly faulty, the system fault module determines that the fault possibly occurs in one of the slave AFE nodes, and the forward link and the backward link are normal. This comprehensive determination strategy can more accurately locate the fault position.

[0104] The bidirectional daisy chain communication fault determination method provided by the embodiment of the application can accurately identify whether the forward link or the backward link is faulty when a single link is faulty by respectively performing data reading, verification and error counting determination on the forward link and the backward link. Moreover, a continuity determination method is adopted, that is, the fault is determined according to whether the error accumulation count exceeds a threshold value through multiple data transmission and verification, which avoids misjudgment caused by accidental factors and improves the accuracy of fault identification.

[0105] When one of the slave AFE nodes is faulty, the data transmission of the forward link and the backward link is affected. By comprehensively analyzing the data verification results and fault determination conditions of the forward link and the backward link, the system can determine whether the fault is caused by a node or a link, and can further locate the specific fault node, thereby providing accurate information for fault repair.

[0106] The voltage and temperature data of each slave AFE node are respectively independently verified and counted. This targeted processing method can more accurately detect voltage and temperature abnormalities, because the voltage and temperature of different nodes may be affected by different factors, and separate counting can avoid interference between different data, thereby improving the accuracy of fault determination.

[0107] Based on the above accurate fault determination results, the system can take corresponding processing measures in a timely manner, such as isolating the fault node, switching to a backup link, etc., to prevent the fault from expanding and affecting the operation of the entire system. At the same time, the timely fault protection mechanism can ensure the safety and stability of the system, and avoid problems such as equipment damage or data loss caused by faults.

[0108] Reference is made to Figure 2 In one implementation of the embodiment, the S1 can be further refined to include the following steps:

[0109] S101, the master system reads data of the M slave AFE nodes through the daisy chain forward link respectively, and judges whether the reading times is greater than a first threshold; if yes, S102 is executed, and if no, S2 is executed;

[0110] It should be noted that when implementing the bidirectional daisy chain communication fault judgment method, the master system first reads data of the M slave AFE (front-end cell acquisition chip) nodes in turn through the daisy chain forward link. This step is the basis for obtaining node data, and provides original information for subsequent data verification and fault analysis. At the same time, the master system judges the data reading times in real time, and compares it with the first threshold set in advance. The first threshold is a key parameter, which determines the duration of the power-on filtering stage. If the reading times has not exceeded the first threshold, it means that the system is still in the power-on filtering stage, at which time the data reading operation is continued, and the subsequent data verification (i.e. S2) is prepared; if the reading times exceeds the first threshold, it means that the power-on filtering stage may have ended or the data of the filtering stage needs to be further processed, at which time step S102 is entered.

[0111] S102, it is determined that the power-on filtering stage is in, and the abnormal data possibly existing is discarded, and the S101 is returned.

[0112] It should be noted that when it is judged that the reading times is greater than the first threshold, it is determined that the current is in the power-on filtering stage. At the initial power-on, since the communication link has not been completely stabilized, the start-up time of each chip may also have differences, resulting in poor synchronicity, and the data read in this case is likely to be abnormal. If these abnormal data are directly used for subsequent fault judgment, the accuracy of the judgment result will be disturbed, and even misjudgment will be caused. Therefore, the embodiment adopts the strategy of discarding the abnormal data possibly existing, so as to eliminate the influence of these unstable factors on the fault judgment. After discarding the data, the system returns to step S101, continues to perform the data reading operation, and again judges whether the reading times exceeds the first threshold, so as to circulate until the condition of entering the normal data reading and verification stage is met.

[0113] It can be understood that in the bidirectional daisy chain communication of the energy storage system, the initial power-on is a special and critical period. At this time, the communication link may be in the process of gradually establishing and stabilizing, and the chip start-up time of each slave AFE node may also be inconsistent, resulting in poor synchronization between them. This unstable state is prone to cause communication failures, such as data transmission errors, loss, and the like. The current common abnormality judgment method is to perform unified value analysis on the entire AFE data, however, the collection of voltage and temperature data itself has different characteristics and time requirements, and their reading is not performed simultaneously. This makes it difficult to accurately distinguish voltage and temperature collection failures when analyzing the data, and it is impossible to determine whether the failure occurs in the voltage collection part or the temperature collection part, and thus it is impossible to provide accurate information for failure troubleshooting and repair, which is not conducive to the stable operation and maintenance of the system.

[0114] In view of the unstable communication link in the initial power-on stage and the problems existing in the current abnormality judgment method, an effective solution is proposed in the embodiment. By setting the power-on filtering stage, when the system is initially powered on, the fault filtering operation is performed first. In this stage, the master control system performs data reading and processing in the manner of steps S101 and S102, discards the data that may have abnormalities, and avoids the interference of these unstable data on the subsequent fault judgment. At the same time, a first threshold is set to control the duration of the power-on filtering stage. Only when the reading times exceed the first threshold, it is considered that the power-on filtering stage is ended, and the system starts the normal data reading and verification operation. This way can effectively improve the stability and data accuracy of the system during the initial power-on, lay a foundation for subsequent accurate fault judgment, and thus better guarantee the normal operation of the energy storage system.

[0115] In an embodiment of the embodiment, before the S1, the method further comprises:

[0116] S0, initializing power-on, the master control system wakes up M AFE nodes, and performs slave control configuration to obtain M slave AFE nodes.

[0117] It should be noted that the master control system sends a wake-up instruction to the M AFE nodes through a specific communication protocol and signal line, so that these nodes which are originally in a low-power sleep state are activated and enter a normal working mode. The wake-up process may include starting the internal clock of the AFE node, initializing the register, and the like, to ensure that the AFE node can accurately collect and transmit data.

[0118] After the AFE nodes are woken up, the host system needs to configure them as slaves. The purpose of slave configuration is to set specific parameters and working modes for each AFE node according to the overall requirements and design requirements of the system. For example, configure the sampling frequency, range, communication address and other parameters of the AFE node, so that it can accurately collect data according to the requirements of the host system, and transmit data to the host system through the daisy chain communication link. After slave configuration, these AFE nodes become slave AFE nodes with specific functions and parameters, and can work with the host system to complete the data acquisition and control tasks of the system.

[0119] Please refer to Figure 3 In one embodiment of the present embodiment, after the S11, the method further comprises:

[0120] S12, the system fault module determines the slave AFE nodes with faults from the M slave AFE nodes according to the serial numbers of the slave AFE nodes with faults determined on the daisy chain forward link and the serial numbers of the slave AFE nodes with faults determined on the daisy chain reverse link.

[0121] It should be noted that in the bidirectional daisy chain communication structure, there are two communication paths, the forward link and the reverse link. In the previous steps, the system has detected faults in the M slave AFE nodes on the daisy chain forward link and reverse link, and recorded the serial numbers of the slave AFE nodes with faults determined on the two links. These serial numbers are like the "identity" of the faulty nodes, which can accurately locate the specific problematic nodes.

[0122] The system fault module will integrate the serial number information of the faulty nodes recorded on the forward link and the reverse link. It will compare and analyze the two sets of serial numbers to determine the final slave AFE nodes with faults. This can avoid misjudgment that may occur in single link detection, and improve the accuracy and reliability of fault judgment.

[0123] Suppose in a energy storage system, a bidirectional daisy chain communication structure is used to manage the battery pack. There are M=10 slave AFE (front-end cell acquisition) nodes in the system, which are connected in series on the daisy chain, and communicate data with the host system through the forward link and the reverse link. Each AFE node is responsible for collecting the voltage, temperature and other parameters of the corresponding battery cell, and transmitting these data to the host system for real-time monitoring and control of the state of the battery pack.

[0124] The host system sends data read instructions to the 10 slave AFE nodes in turn through the forward link, and receives the collected data returned by them.

[0125] In the data transmission process, the host system checks the data returned by each node.

[0126] It is found through detection that the data returned by the third node is checked to be wrong, and the host system records that the third node has a fault on the forward link and records its serial number as 3.

[0127] The host system sends data reading instructions to the 10 slave AFE nodes through the reverse link and receives data.

[0128] The data is checked again, and it is found that the data returned by the eighth node on the reverse link is checked to be wrong. The host system records that the eighth node has a fault on the reverse link and records its serial number as 8.

[0129] Since the third node on the forward link and the eighth node on the reverse link point to the same node, which is essentially the third node on the forward link, the system fault module determines that the third node on the forward link is the slave AFE node with a fault, thereby excluding the possibility of faults of other nodes.

[0130] Although the terms daisy chain, host system, and the like are used more in this application, the possibility of using other terms is not excluded. The use of these terms is only to facilitate the description and explanation of the essence of the application; any additional limitation on them is contrary to the spirit of the application.

[0131] Embodiment Two

[0132] Please refer to Figure 4 The embodiment of the application provides a bidirectional daisy chain communication fault judgment system, which comprises M slave AFE nodes, a host system, a data acquisition and checking module, a communication fault diagnosis module and a system fault module connected in sequence.

[0133] The host system is used for reading data of the M slave AFE nodes through the daisy chain forward link.

[0134] The data acquisition and checking module is used for checking the data returned by the slave AFE nodes to determine whether there is a checking error.

[0135] The communication fault diagnosis module is used for determining that the daisy chain forward link is normal, the M slave AFE nodes are normal, and the forward link data error accumulation count is cleared to zero if there is no checking error.

[0136] The communication fault diagnosis module is also used for adding 1 to the forward link data error accumulation count and determining whether the forward link data error accumulation count is greater than a second threshold value if there is a checking error.

[0137] the communication fault diagnosis module is further configured to determine that the daisy chain forward link is possibly faulty if the number is greater than a second threshold value;

[0138] the master control system is further configured to read data from the M slave AFE nodes through the daisy chain reverse link respectively;

[0139] the data acquisition and verification module is further configured to perform data verification according to the data returned by the slave AFE nodes to determine whether there is a verification error;

[0140] the communication fault diagnosis module is further configured to determine that the daisy chain reverse link is normal, the M slave AFE nodes are normal, and the reverse link data error accumulation count is cleared if there is no verification error;

[0141] the communication fault diagnosis module is further configured to add 1 to the reverse link data error accumulation count if there is a verification error, and determine whether the reverse link data error accumulation count is greater than a third threshold value;

[0142] the communication fault diagnosis module is further configured to determine that the daisy chain reverse link is possibly faulty if the number is greater than the third threshold value;

[0143] the system fault module is configured to give a final fault determination result according to the following strategy:

[0144] if the daisy chain forward link is normal and the daisy chain reverse link is possibly faulty, it is determined that the daisy chain forward link is normal, the M slave AFE nodes are normal, and the daisy chain reverse link is faulty;

[0145] if the daisy chain forward link is possibly faulty and the daisy chain reverse link is normal, it is determined that the daisy chain reverse link is normal, the M slave AFE nodes are normal, and the daisy chain forward link is faulty;

[0146] if the daisy chain forward link is possibly faulty and the daisy chain reverse link is possibly faulty, it is determined that the daisy chain forward link is normal, the daisy chain reverse link is normal, and some of the M slave AFE nodes are faulty.

[0147] Optionally, the master control system is specifically configured to:

[0148] read data from the M slave AFE nodes through the daisy chain forward link respectively, and determine whether the number of reading times is greater than a first threshold value; if yes, it is determined that it is in the power-on filtering stage, and the data that may be abnormal is discarded.

[0149] Optionally, the master control system is further configured to:

[0150] Initialization power-on, wake up M AFE nodes, and slave configuration, get M slave AFE nodes.

[0151] Optionally, the system fault module is further configured to:

[0152] Determine the slave AFE node with fault from M slave AFE nodes according to the serial number of the slave AFE node with fault determined on the daisy chain forward link and the serial number of the slave AFE node with fault determined on the daisy chain reverse link.

[0153] The system can execute the method provided by any embodiment of the application, and has the corresponding function modules and beneficial effects of executing the method.

[0154] Embodiment three

[0155] Figure 5 A structural schematic diagram of a computer device provided for embodiment three of the application. Figure 5 A block diagram of an exemplary computer device 12 suitable for implementing embodiments of the present application is shown. Figure 5 The computer device 12 shown is merely one example and should not be construed as limiting the scope of the embodiments of the application.

[0156] As shown in Figure 5 The computer device 12 is shown in the form of a general-purpose computing device. The components of the computer device 12 can include, but are not limited to, one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.

[0157] The bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration bus, a processor or local bus using any of a variety of bus architectures including Industry Standard Architecture (ISA), Micro Channel Architecture (MCA), Enhanced ISA (EISA), Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0158] The computer device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by the computer device 12 and includes both volatile and non-volatile media, removable and non-removable media.

[0159] System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. Computer device 12 can further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (e.g., a "hard drive") Figure 5 not shown, commonly referred to as a "hard disk drive"). Although Figure 5 not shown, a magnetic hard disk drive, a solid state drive, or a combination of

[0160] Program / utility 40, having a set (at least one) of program modules 42, can be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data, each or some combination thereof, can include implementation of a network environment. Program modules 42 generally carry out the functions and / or methodologies of embodiments of the application as described herein.

[0161] Computer device 12 can also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc.; one or more devices that enable a user to interact with computer device 12; and / or one or more devices that enable computer device 12 to communicate with one or more other computing devices. Such communication can be via input / output (I / O) interfaces 22. Still yet, computer device 12 can communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or the Internet) through network adapter 20. As an example, network adapter 20 can include a modem, a network card (wireless or wired), or other well-known interface devices. Computer device 12 can also contain communication devices and drives for various output devices. Figure 5 It should be appreciated that the above-described hardware and / or software modules (e.g., microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.) could be utilized in connection with computer device 12, although they are not explicitly shown in FIG. 1. Furthermore, although FIG. 1

[0162] The processing unit 16 performs various function applications and data processing by running programs stored in the system memory 28, such as implementing the bidirectional daisy chain communication fault determination method provided by the embodiments of the present application.

[0163] Embodiment four

[0164] Embodiment four of the present application provides a computer readable storage medium, which stores computer executable instructions, and the instructions are executed by a processor to implement the bidirectional daisy chain communication fault determination method provided by all embodiments of the present application.

[0165] Any combination of one or more computer readable medium can be employed. The computer readable medium can be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination of the above. More specific examples (a non-exhaustive list) of the computer readable storage medium include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, the computer readable storage medium can be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0166] A computer readable signal medium can include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal can take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium can be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate or transport program for use by or in connection with an instruction execution system, apparatus, or device.

[0167] Program code embodied on a computer readable medium can be transmitted using any appropriate medium, including but not limited to wireless, wire line, optical fiber cable, RF, etc., or any suitable combination of the above.

[0168] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0169] Finally, it should be noted that the above-described embodiments are merely intended to illustrate the technical solutions of the present application, but not to limit the patent protection scope of the present application. Any equivalent structure or equivalent flowchart replacement or modification based on the technical concept of the present application, and the technical solutions of the above embodiments directly or indirectly applied to other related technical fields, etc., are all included in the patent protection scope of the present application.

Claims

1. A bidirectional daisy chain communication fault judgment method, characterized in that: The method comprises: S1. The master control system reads data from M slave control AFE nodes through the daisy chain forward link. S2, the data acquisition and verification module performs data verification based on the data returned from the control AFE node to determine whether the verification error occurs; if so, execute S4, if not, execute S3; S3. The communication fault diagnosis module determines that the daisy chain forward link is normal, the M slave AFE nodes are normal, and clears the forward link data error cumulative count; S4, the communication fault diagnosis module adds 1 to the forward link data error cumulative count and determines whether the forward link data error cumulative count is greater than a second threshold; if so, execute S5; if not, return to execute S2; S5. The communication fault diagnosis module determines that a fault may exist in the daisy chain forward link; S6. The master control system reads data from the M slave control AFE nodes respectively through the daisy chain reverse link; S7, the data acquisition and verification module performs data verification based on the data returned from the control AFE node to determine whether a verification error occurs; if so, execute S9; if not, execute S8; S8. The communication fault diagnosis module determines that the daisy chain reverse link is normal, the M slave AFE nodes are normal, and clears the reverse link data error cumulative count; S9, the communication fault diagnosis module adds 1 to the reverse link data error cumulative count and determines whether the reverse link data error cumulative count is greater than a third threshold; if so, executing S10; if not, returning to executing S7; S10, the communication fault diagnosis module determines that there may be a fault in the daisy chain reverse link; S11. The system fault module gives the final fault judgment result according to the following strategy: If the daisy chain forward link is normal and the daisy chain reverse link may have a fault, it is determined that the daisy chain forward link is normal, the M slave AFE nodes are normal, and the daisy chain reverse link has a fault; If the daisy chain forward link may have a fault and the daisy chain reverse link is normal, determining that the daisy chain reverse link is normal, the M slave AFE nodes are normal, and the daisy chain forward link has a fault; If the daisy chain forward link may be faulty and the daisy chain reverse link may be faulty, it is determined that the daisy chain forward link is normal, the daisy chain reverse link is normal, and one of the M slave AFE nodes is faulty.

2. The bidirectional daisy chain communication fault judgment method according to claim 1, characterized in that: Said S1 comprises: S101, the master control system reads data from M slave control AFE nodes respectively through the daisy chain forward link, and determines whether the number of reads is greater than a first threshold; if so, execute S102, if not, execute S2; S102: Determine that the system is in the power-on filtering stage, discard data that may be abnormal, and return to S101.

3. The bidirectional daisy chain communication fault judgment method according to claim 1, characterized in that: Before S1, the method further includes: S0: Initialize power-on, the master control system wakes up M AFE nodes, and performs slave control configuration to obtain M slave control AFE nodes.

4. The bidirectional daisy chain communication fault judgment method according to claim 1, characterized in that: After S11, the method further includes: S12. The system fault module determines the faulty slave AFE node from the M slave AFE nodes based on the serial number of the faulty slave AFE node determined on the daisy chain forward link and the serial number of the faulty slave AFE node determined on the daisy chain reverse link.

5. A bidirectional daisy chain communication fault diagnosis system, characterized in that: The system includes M slave control AFE nodes connected in sequence, a master control system, a data acquisition and verification module, a communication fault diagnosis module and a system fault module: The master control system is used to read data from M slave control AFE nodes respectively through a daisy chain forward link; The data acquisition and verification module is used to perform data verification based on the data returned by the slave control AFE node to determine whether a verification error occurs; The communication fault diagnosis module is used to determine that the daisy chain forward link is normal and the M slave AFE nodes are normal if there is no verification error, and clear the forward link data error cumulative count to zero; The communication fault diagnosis module is further configured to, if there is a check error, increase the forward link data error cumulative count by 1, and determine whether the forward link data error cumulative count is greater than a second threshold; The communication fault diagnosis module is further configured to determine that a daisy chain forward link may have a fault if the value is greater than a second threshold; The master control system is further configured to read data from the M slave control AFE nodes respectively through a daisy chain reverse link; The data acquisition and verification module is further configured to perform data verification based on the data returned from the control AFE node to determine whether a verification error occurs; The communication fault diagnosis module is further configured to determine that the daisy chain reverse link is normal and the M slave AFE nodes are normal if there is no verification error, and clear the reverse link data error cumulative count to zero; The communication fault diagnosis module is further configured to, if a check error occurs, increase a reverse link data error cumulative count by 1, and determine whether the reverse link data error cumulative count is greater than a third threshold; The communication fault diagnosis module is further configured to determine that a daisy chain reverse link may have a fault if the value is greater than a third threshold; The system fault module is used to give the final fault judgment result according to the following strategy: If the daisy chain forward link is normal and the daisy chain reverse link may have a fault, it is determined that the daisy chain forward link is normal, the M slave AFE nodes are normal, and the daisy chain reverse link has a fault; If the daisy chain forward link may have a fault and the daisy chain reverse link is normal, determining that the daisy chain reverse link is normal, the M slave AFE nodes are normal, and the daisy chain forward link has a fault; If the daisy chain forward link may be faulty and the daisy chain reverse link may be faulty, it is determined that the daisy chain forward link is normal, the daisy chain reverse link is normal, and one of the M slave AFE nodes is faulty.

6. The bidirectional daisy chain communication fault diagnosis system according to claim 5, characterized in that: The main control system is specifically used for: Data is read from M slave AFE nodes respectively through the daisy chain forward link, and it is determined whether the number of readings is greater than a first threshold; if so, it is determined to be in the power-on filtering stage, and data that may be abnormal is discarded.

7. The bidirectional daisy chain communication fault diagnosis system according to claim 5, characterized in that: The main control system is also used for: Initialize power-on, wake up M AFE nodes, and perform slave control configuration to obtain M slave AFE nodes.

8. The bidirectional daisy chain communication fault diagnosis system according to claim 5, characterized in that: The system fault module is also used to: The faulty slave AFE node is determined from the M slave AFE nodes according to the serial number of the faulty slave AFE node determined on the daisy chain forward link and the serial number of the faulty slave AFE node determined on the daisy chain reverse link.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the bidirectional daisy chain communication fault judgment method according to any one of claims 1 to 4 is implemented.

10. A computer-readable storage medium having computer-executable instructions stored thereon, characterized in that: The computer executable instructions are executed by a computer processor to implement the bidirectional daisy chain communication fault judgment method according to any one of claims 1 to 4.

Images