A method for diagnosing daisy-chain communication faults, a main control device, equipment, and storage medium.

Abstract

This application provides a daisy-chain communication fault diagnosis method, a main control device, an equipment, and a storage medium. The main control device is applied in a battery management system. The battery management system further includes a data acquisition module and several analog front-ends. The main control device and the analog front-ends form a daisy chain. When the data acquisition module acquires data through the daisy chain, it determines whether the acquired data is abnormal. If the acquired data is abnormal, the daisy chain is identified as a communication fault. The abnormal data is read several times unidirectionally by each analog front-end, and the cause of the communication fault is determined based on the result of each unidirectional read. This method is used to diagnose daisy-chain communication faults and promptly obtain the communication status and cause of the fault.

Description

Technical Field

[0001] This invention relates to the field of battery management technology, and more specifically, to a daisy-chain communication fault diagnosis method, a main control device, an equipment, and a storage medium. Background Technology

[0002] With the development of BWS battery management system technology, the communication between individual sampling chips in BMS has evolved from CAN communication to daisy-chain communication, which has become a trend. Daisy-chain communication has a huge cost advantage over CAN communication. As an emerging communication method between modules within the battery management system, it is now widely used due to its advantages such as low cost, simple application, and simplified wiring harness and other designs.

[0003] However, the research revealed that daisy-chain communication uses a cascaded communication method, and cascaded communication harness connections are among the most unstable systems, frequently experiencing communication failures such as chain breaks, leading to communication anomalies in the battery management system. Therefore, how to diagnose communication faults in daisy chains and promptly obtain information on the communication status and causes of faults has become an urgent problem to be solved. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a daisy-chain communication fault diagnosis method, main control device, equipment and storage medium, so as to diagnose communication faults in daisy-chain and obtain the communication status and fault cause of daisy-chain in a timely manner.

[0005] In a first aspect, embodiments of this application provide a daisy-chain communication fault diagnosis method, applied to a main control device in a battery management system. The battery management system further includes a data acquisition module and several analog front-ends, the main control device and each analog front-end forming a daisy chain. When the data acquisition module acquires data through the daisy chain, the method includes:

[0006] Determine whether the data collected by the acquisition module is abnormal;

[0007] If the data collected by the acquisition module is abnormal, the daisy chain will be identified as a communication failure.

[0008] By performing several one-way reads on the abnormal data from each simulated front end, the cause of the communication failure can be determined based on the results of each one-way read.

[0009] Optionally, determining whether the data collected by the acquisition module is abnormal includes:

[0010] When a PEC error occurs and all data collected by the acquisition module is 0xFF, the data collected by the acquisition module is determined to be abnormal.

[0011] Optionally, the unidirectional read can be a forward read or a reverse read, with one forward read and one reverse read constituting one cycle read.

[0012] Optionally, the abnormal data is read several times one-way by each analog front-end, and the cause of the communication failure is determined based on the result of each one-way read, including:

[0013] Determine if a one-way loop exists that can normally read the abnormal data;

[0014] If there is no unidirectional loop that can read the abnormal data normally, the abnormal data will be read in several loops through each simulation front end.

[0015] Determine whether the abnormal data can be read normally in each of several loop reads;

[0016] If the abnormal data can be read normally in several loop reads, then the cause of the fault is determined to be a single point of failure.

[0017] Optionally, after determining whether the abnormal data can be read normally in several loop reads, the method further includes:

[0018] If a loop of reading fails to read the abnormal data, the cause of the fault is determined to be a multi-point fault.

[0019] Optionally, after determining whether the data collected by the acquisition module is abnormal, the method further includes:

[0020] If the data collected by the acquisition module is abnormal, the validity of the data collected by the acquisition module will be determined as invalid.

[0021] If the data collected by the acquisition module does not show any abnormalities, the validity of the data collected by the acquisition module is determined to be valid.

[0022] Optionally, after determining whether a one-way loop exists that can normally read the abnormal data, the method further includes:

[0023] If a one-way loop exists that can read the abnormal data normally, then the validity of the data collected by the acquisition module is determined to be valid;

[0024] After determining whether the abnormal data can be read normally in several loop reads, the method further includes:

[0025] If a loop of reading occurs that can read the abnormal data normally, the validity of the data collected by the acquisition module is determined to be valid.

[0026] Secondly, embodiments of this application provide a main control device, which belongs to a battery management system. The battery management system further includes a data acquisition module and several analog front-ends. The main control device and each analog front-end form a daisy chain. The main control device includes:

[0027] The judgment unit is used to determine whether the data collected by the acquisition module is abnormal when the acquisition module collects data through the daisy chain;

[0028] The diagnostic unit is used to determine the daisy chain as a communication failure if the data collected by the acquisition module is abnormal.

[0029] The fault cause determination unit is used to perform several one-way reads of abnormal data that have occurred through each analog front end, and determine the cause of the communication fault based on the reading results of each one-way read.

[0030] Optionally, determining whether the data collected by the acquisition module is abnormal includes:

[0031] When a PEC error occurs and all data collected by the acquisition module is 0xFF, the data collected by the acquisition module is determined to be abnormal.

[0032] Optionally, the unidirectional read can be a forward read or a reverse read, with one forward read and one reverse read constituting one cycle read.

[0033] Optionally, the abnormal data is read several times one-way by each analog front-end, and the cause of the communication failure is determined based on the result of each one-way read, including:

[0034] Determine if a one-way loop exists that can normally read the abnormal data;

[0035] If there is no unidirectional loop that can read the abnormal data normally, the abnormal data will be read in several loops through each simulation front end.

[0036] Determine whether the abnormal data can be read normally in each of several loop reads;

[0037] If the abnormal data can be read normally in several loop reads, then the cause of the fault is determined to be a single point of failure.

[0038] Optionally, the fault cause determination unit is used to determine the fault cause as a multi-point fault if, after determining whether the abnormal data can be read normally in several cyclic reads, a cyclic read in which the abnormal data cannot be read normally occurs.

[0039] Optionally, the fault cause determination unit is used to determine the validity of the data collected by the acquisition module as invalid if the data collected by the acquisition module is invalid after determining whether the data collected by the acquisition module is abnormal.

[0040] The fault cause determination unit is used to determine the validity of the data collected by the acquisition module as valid if no abnormality is found in the data collected by the acquisition module.

[0041] Optionally, the fault cause determination unit is used to determine the validity of the data collected by the acquisition module as valid if a one-way loop capable of normally reading the abnormal data exists after determining whether there is such a loop.

[0042] The fault cause determination unit is used to determine the validity of the data collected by the acquisition module as valid if, after judging whether the abnormal data can be read normally in several loop reads, a loop read that can read the abnormal data normally occurs.

[0043] Thirdly, embodiments of this application provide a computer device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the daisy-chain communication fault diagnosis method described in any of the optional embodiments of the first aspect are performed.

[0044] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the daisy-chain communication fault diagnosis method described in any of the optional embodiments of the first aspect.

[0045] The technical solution provided in this application includes, but is not limited to, the following beneficial effects:

[0046] This application determines whether the data collected by the acquisition module is abnormal, and determines whether the daisy chain has a communication failure based on the judgment result. In the event of a communication failure, the abnormal data is read several times by each analog front end. The cause of the communication failure is determined based on the reading result of each one-way read, thereby enabling communication failure diagnosis of the daisy chain and timely knowledge of the communication status and cause of the failure.

[0047] In addition, this application, through logical judgment of normal data acquisition and chain break conditions, and by repeatedly reading data in both unidirectional and bidirectional directions to confirm the correctness of the read data and the existence of the fault point, considers automatic chain break recovery, data processing during chain break recovery, and communication switching operations in single-point fault situations. This allows the battery management system to quickly identify and locate the fault location when it detects a chain break in the daisy chain, helping to promptly discover and resolve potential safety hazards and prevent further damage to the battery system. Furthermore, since a daisy chain break can cause communication interruptions between battery modules, affecting the battery management system's monitoring of the entire battery pack, chain break diagnosis ensures system integrity, reduces safety risks caused by communication failures, and improves the safety of the battery management system. Moreover, by monitoring the daisy chain status, the battery management system ensures unimpeded information transmission between battery modules, thereby optimizing battery performance. This helps improve battery energy efficiency, extend battery life, and optimize battery performance. Finally, the daisy chain break diagnosis function of the battery management system simplifies battery system maintenance. When a fault occurs, maintenance personnel can quickly find the problem based on the diagnostic information provided by the battery management system, reducing maintenance costs and time.

[0048] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0049] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0050] Figure 1 A flowchart of a daisy-chain communication fault diagnosis method provided in Embodiment 1 of the present invention is shown;

[0051] Figure 2 A flowchart of a fault cause determination method provided in Embodiment 1 of the present invention is shown;

[0052] Figure 3 The flowchart of a daisy chain breakage diagnosis method provided in Embodiment 1 of the present invention is shown;

[0053] Figure 4 A schematic diagram of the structure of a main control device provided in Embodiment 2 of the present invention is shown;

[0054] Figure 5A schematic diagram of the structure of a computer device provided in Embodiment 3 of the present invention is shown. Detailed Implementation

[0055] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0056] Example 1

[0057] To facilitate understanding of this application, the following is combined with... Figure 1 The flowchart of the daisy-chain communication fault diagnosis method provided in Embodiment 1 of the present invention illustrates the content of Embodiment 1 in detail.

[0058] See Figure 1 As shown, Figure 1 The flowchart illustrates a daisy-chain communication fault diagnosis method provided in Embodiment 1 of the present invention. The method is applied to a main control device in a battery management system. The battery management system further includes a data acquisition module and several analog front-ends. The main control device and each analog front-end constitute a daisy chain. When the data acquisition module acquires data through the daisy chain, the method includes steps S101 to S103:

[0059] S101: Determine whether the data collected by the acquisition module is abnormal.

[0060] Specifically, firstly, the status of the data collected by the acquisition module can determine whether a communication failure has occurred in the daisy chain. If the status of the data collected by the acquisition module is normal, it indicates that the daisy chain can communicate normally and there is no communication failure.

[0061] S102: If the data collected by the acquisition module is abnormal, the daisy chain is identified as a communication failure.

[0062] Conversely, if the data collected by the acquisition module shows an abnormal state, it indicates that the daisy chain cannot transmit data normally, and a communication failure has occurred.

[0063] S103: The abnormal data that occurs is read several times by each analog front end, and the cause of the communication failure is determined based on the reading result of each one-way read.

[0064] Specifically, when it is determined that there is a problem with the collected data, a disconnection detection is initiated. Abnormal data that appears is continuously read, and the cause of the daisy chain communication failure is determined based on the reading results of each one-way read.

[0065] In an optional implementation, determining whether the data collected by the acquisition module is abnormal includes:

[0066] When a PEC error occurs and all data collected by the acquisition module is 0xFF, the data collected by the acquisition module is determined to be abnormal.

[0067] Specifically, PEC stands for Communication Data Error Detection. When a PEC error occurs simultaneously and all the data collected by the acquisition module is 0xFF (hexadecimal), the data collected by the acquisition module is determined to be abnormal.

[0068] In an optional implementation, the unidirectional read is either a forward read or a reverse read, such that one forward read and one reverse read constitute one cycle read.

[0069] Specifically, reading once in the forward direction and once in the reverse direction constitutes one cycle of reading.

[0070] In an optional implementation, see Figure 2 As shown, Figure 2 The flowchart of a fault cause determination method provided in Embodiment 1 of the present invention is shown. The method involves performing several one-way reads of abnormal data from each simulated front end, and determining the cause of the communication fault based on the result of each one-way read, including steps S201 to S204.

[0071] S201: Determine whether there is a one-way loop that can read the abnormal data normally.

[0072] S202: If there is no unidirectional loop that can read the abnormal data normally, then the abnormal data is read in several loops through each simulation front end.

[0073] S203: Determine whether the abnormal data can be read normally in several loop reads.

[0074] S204: If the abnormal data can be read normally in several loop reads, then the cause of the fault is determined to be a single point of failure.

[0075] Specifically, the loop reading and judgment logic includes the following steps:

[0076] Step 1: If normal data is read in one direction during the loop reading process, then exit the loop reading.

[0077] Step two: If six consecutive loop reads show erroneous data read in one direction but complete data read in both directions, determine if the error occurs at the same location. If it does, report a single point of failure and switch to dual-chain communication. If it does not occur at the same location, also report a single point of failure and switch to dual-chain communication, and report the break point location. If the single point of failure is detected to have disappeared during dual-chain communication, proceed to step one.

[0078] In an optional implementation, after determining whether the abnormal data can be read normally in several loop reads, the method further includes:

[0079] If a loop of reading fails to read the abnormal data, the cause of the fault is determined to be a multi-point fault.

[0080] Specifically, if incomplete combined data is detected during dual-chain communication, the cause of the fault is determined to be a multi-point fault, and the fault diagnosis in steps S101 to S103 is executed repeatedly, recording the number of times the fault diagnosis is repeated. It is determined whether the repeated causes obtained after continuous fault diagnosis are multi-point faults for more than three consecutive times. If so, a reset operation is performed to re-initialize the system. The fault diagnosis steps are then repeated to determine whether the repeated causes obtained after continuous fault diagnosis are multi-point faults for more than three consecutive times. When attempting to recover via reset, all fault interfaces of the 6830 are cleared to 0 (except for multi-point faults).

[0081] During the multi-point fault confirmation process, if the data combination is incomplete, the missing data is set to 0xFF and its validity is set to invalid. Readable data is uploaded normally and is considered valid. During the reset period (attempting to recover from the reset), all collected data retains the previous values, and the data validity is set to invalid until the reset is completed, at which point the sampled data is updated. If the cause of the loop after the loop fault diagnosis is a multi-point fault for more than three consecutive times, a multi-point fault is reported. After multi-point fault confirmation, data collection continues, and the completeness of the data combination is checked. If the data is complete, the multi-point fault state is exited; otherwise, the multi-point fault state is maintained.

[0082] In an optional implementation, after determining whether the data collected by the acquisition module is abnormal, the method further includes:

[0083] If the data collected by the acquisition module is abnormal, the validity of the data collected by the acquisition module will be determined as invalid.

[0084] If the data collected by the acquisition module does not show any abnormalities, the validity of the data collected by the acquisition module is determined to be valid.

[0085] Specifically, after determining whether the data collected by the acquisition module is abnormal, if it is determined that there is a problem with the collected data, the validity of the data is immediately set to invalid.

[0086] In an optional implementation, after determining whether a one-way loop exists that can normally read the abnormal data, the method further includes:

[0087] If a one-way loop exists that can read the abnormal data normally, then the validity of the data collected by the acquisition module is determined to be valid.

[0088] After determining whether the abnormal data can be read normally in several loop reads, the method further includes:

[0089] If a loop of reading occurs that can read the abnormal data normally, the validity of the data collected by the acquisition module is determined to be valid.

[0090] Specifically, in the loop read judgment logic, if the unidirectional data recovers normally during the loop read process, the data validity is set to valid; if the data combination is normal during the loop read process, the data validity is immediately set to valid (without considering other validity influencing factors, the same below); if the data combination is incomplete, the missing data is set to 0xFF and the validity is set to invalid, and the readable data is uploaded normally, and this part of the data is valid.

[0091] In practical applications, the daisy-chain communication fault diagnosis method provided in this application can be used to diagnose the loop daisy chain in the following type of battery management system. The loop daisy chain consists of a main control device, a first communication unit and a second communication unit connected to the main control device, and multiple analog front-ends. Starting from the analog front-end connected to the first communication unit, the multiple analog front-ends in the loop daisy chain are accessed sequentially to determine the closest first analog front-end accessible to the first communication unit; when the first communication unit accesses the first analog front-end, the multiple analog front-ends in the loop daisy chain are accessed sequentially to determine the direction in which signal data is read; the state information of the loop daisy chain is determined based on the first analog front-end and the Nth analog front-end. When determining the state information of the loop daisy chain from the first analog front-end and the Nth analog front-end, it is achieved by the following method: when the first analog front-end is the analog front-end in the loop daisy chain closest to the first communication unit, and the Nth analog front-end is the analog front-end in the loop daisy chain closest to the second communication unit, it is determined that the state data content reading of the loop daisy chain occurs in a state where both sides are fully accessible, which is one positive cycle. When the second communication unit accesses the Nth analog front-end, it begins to sequentially access multiple analog front-ends in the loop-through daisy chain to determine the direction for signal data reading. Based on the Nth analog front-end and the first analog front-end, the state information of the loop-through daisy chain is determined. The reading of the state data content of the loop-through daisy chain occurs when both sides are fully open, constituting one reverse loop.

[0092] See Figure 3 As shown, Figure 3 The flowchart illustrates a daisy-chain breakage diagnosis method provided in Embodiment 1 of the present invention. During daisy-chain breakage diagnosis, the main control device first controls the acquisition module to collect data normally, and determines whether there is a problem based on the breakage status. If not, it continues to collect other data; if yes, it performs a loop, recording one forward and one reverse read as one cycle, and determines whether the following conditions exist during the loop reading process: Condition S: One-way reading is normal in the loop; Condition Y: One-way error occurs in 6 loops, and bidirectional data is complete; Condition Z: One-way error occurs in 6 loops, and bidirectional data is incomplete. If the situation is S, continue collecting other data; if the situation is Y, determine if the error is at the same location. If so, report a single point of failure and initiate dual-link communication; otherwise, report a single point of failure, initiate dual-link communication, and report the broken link location. If the situation is Z, repeat the above steps, checking if the loop count is greater than 3. If not, continue the loop; if so, perform a Reset, reinitialize, and repeat the above steps. Repeat the above steps, checking if the loop count is greater than 3. If not, continue the loop; if so, report a multi-point failure, continue reading data, and determine if the data combination is complete. If so, continue collecting other data; otherwise, report a multi-point failure.

[0093] The following steps are included when determining the validity of collected data:

[0094] Step 1: Apply high voltage and read data. Determine if relevant data can be read. If data can be read, proceed to the next step of determining the link breakage; otherwise, the process is considered a failure. The link breakage determination includes three scenarios: single-point link breakage, double-point link breakage, and no link breakage.

[0095] Step Two: Perform process checks and simulate real-world scenarios. In a single-point chain failure scenario, collect battery cell voltage and temperature, upload the data, and modify the flag bit. In a two-point chain failure scenario, modify the flag bit, and the data becomes invalid. In a no-chain failure scenario, collect cell voltage and temperature, upload the data, initialize the system, and modify the flag bit.

[0096] Step 3: Data Selection. When there is a single point of disconnection, modify the label and upload the data. The data will then be evaluated for validity; valid data will be selected, otherwise, the data will be considered invalid. When there are no disconnections, modify the label and upload the data. The data will then be evaluated for validity; valid data will be selected, otherwise, the data will be considered invalid.

[0097] Example 2

[0098] See Figure 4 As shown, Figure 4 This diagram illustrates the structure of a main control device according to Embodiment 2 of the present invention. The main control device belongs to a battery management system, which further includes a data acquisition module and several analog front-ends. The main control device and the analog front-ends form a daisy chain. The main control device includes:

[0099] The judgment unit 401 is used to determine whether the data collected by the acquisition module is abnormal when the acquisition module collects data through the daisy chain;

[0100] The diagnostic unit 402 is used to determine the daisy chain as a communication failure if the data collected by the acquisition module is abnormal.

[0101] The fault cause determination unit 403 is used to perform several one-way reads of the abnormal data that has occurred through each analog front end, and determine the fault cause of the communication fault based on the reading result of each one-way read.

[0102] In an optional implementation, determining whether the data collected by the acquisition module is abnormal includes:

[0103] When a PEC error occurs and all data collected by the acquisition module is 0xFF, the data collected by the acquisition module is determined to be abnormal.

[0104] In an optional implementation, the unidirectional read is either a forward read or a reverse read, such that one forward read and one reverse read constitute one cycle read.

[0105] In one optional implementation, the abnormal data is read several times one-way by each simulated front end. The cause of the communication failure is determined based on the result of each one-way read, including:

[0106] Determine if a one-way loop exists that can normally read the abnormal data;

[0107] If there is no unidirectional loop that can read the abnormal data normally, the abnormal data will be read in several loops through each simulation front end.

[0108] Determine whether the abnormal data can be read normally in each of several loop reads;

[0109] If the abnormal data can be read normally in several loop reads, then the cause of the fault is determined to be a single point of failure.

[0110] In an optional implementation, the fault cause determination unit is used to determine the fault cause as a multi-point fault if, after determining whether the abnormal data can be read normally in several cyclic reads, a cyclic read in which the abnormal data cannot be read normally occurs.

[0111] In an optional implementation, the fault cause determination unit is used to determine the validity of the data collected by the acquisition module as invalid if the data collected by the acquisition module is invalid after determining whether the data collected by the acquisition module is abnormal.

[0112] The fault cause determination unit is used to determine the validity of the data collected by the acquisition module as valid if no abnormality is found in the data collected by the acquisition module.

[0113] In an optional implementation, the fault cause determination unit is used to determine the validity of the data collected by the acquisition module as valid if a one-way loop capable of normally reading the abnormal data exists after determining whether there is such a loop.

[0114] The fault cause determination unit is used to determine the validity of the data collected by the acquisition module as valid if, after judging whether the abnormal data can be read normally in several loop reads, a loop read that can read the abnormal data normally occurs.

[0115] Example 3

[0116] Based on the same application concept, see [link / reference] Figure 5 As shown, Figure 5 A schematic diagram of the structure of a computer device provided in Embodiment 3 of the present invention is shown, wherein, as Figure 5 As shown, the computer device 500 provided in Embodiment 3 of this application includes:

[0117] The computer device 500 includes a processor 501, a memory 502, and a bus 503. The memory 502 stores machine-readable instructions that can be executed by the processor 501. When the computer device 500 is running, the processor 501 and the memory 502 communicate through the bus 503. When the machine-readable instructions are executed by the processor 501, the steps of the daisy-chain communication fault diagnosis method shown in Embodiment 1 are performed.

[0118] Example 4

[0119] Based on the same concept, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the daisy-chain communication fault diagnosis method described in any of the above embodiments.

[0120] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the system and apparatus described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0121] The computer program product for diagnosing daisy-chain communication faults provided in this embodiment of the invention includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods described in the preceding method embodiments. For specific implementation details, please refer to the method embodiments, which will not be repeated here.

[0122] The main control device provided in this embodiment of the invention can be specific hardware on a device or software or firmware installed on the device. The implementation principle and technical effects of the device provided in this embodiment of the invention are the same as those in the foregoing method embodiments. For the sake of brevity, any parts not mentioned in the device embodiments can be referred to the corresponding content in the foregoing method embodiments. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can all be referred to the corresponding processes in the above method embodiments, and will not be repeated here.

[0123] In the embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the coupling or direct coupling or communication connection shown or discussed may be through some communication interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0124] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0125] In addition, the functional units in the embodiments provided by the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0126] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0127] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0128] Finally, it should be noted that the above-described embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. All should be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for diagnosing daisy-chain communication faults, characterized in that, A main control device is used in a battery management system, the battery management system further including a data acquisition module and several analog front-ends, the main control device and each analog front-end forming a daisy chain, and the method for the data acquisition module to acquire data through the daisy chain includes: Determine whether the data collected by the acquisition module is abnormal; If the data collected by the acquisition module is abnormal, the daisy chain will be identified as a communication failure. The abnormal data that occurs is read several times by each simulated front end, and the cause of the communication failure is determined based on the reading result of each one-way read. The unidirectional read can be either a forward read or a reverse read, with one forward read and one reverse read constituting one cycle read; By performing several one-way reads on the abnormal data from each simulated front end, the cause of the communication failure is determined based on the results of each one-way read, including: Determine if a one-way loop exists that can normally read the abnormal data; If there is no unidirectional loop that can read the abnormal data normally, the abnormal data will be read in several loops through each simulation front end. Determine whether the abnormal data can be read normally in each of several loop reads; If the abnormal data can be read normally in several loop reads, then the cause of the fault is determined to be a single point of failure.

2. The method according to claim 1, characterized in that, Determining whether the data collected by the acquisition module is abnormal includes: When a PEC error occurs and all data collected by the acquisition module is 0xFF, the data collected by the acquisition module is determined to be abnormal.

3. The method according to claim 1, characterized in that, After determining whether the abnormal data can be read normally in several loop reads, the method further includes: If a loop of reading fails to read the abnormal data, the cause of the fault is determined to be a multi-point fault.

4. The method according to claim 3, characterized in that, After determining whether the data collected by the acquisition module is abnormal, the method further includes: If the data collected by the acquisition module is abnormal, the validity of the data collected by the acquisition module will be determined as invalid. If the data collected by the acquisition module does not show any abnormalities, the validity of the data collected by the acquisition module is determined to be valid.

5. The method according to claim 3, characterized in that, After determining whether a one-way loop exists that can normally read the abnormal data, the method further includes: If a one-way loop exists that can read the abnormal data normally, then the validity of the data collected by the acquisition module is determined to be valid; After determining whether the abnormal data can be read normally in several loop reads, the method further includes: If a loop of reading occurs that can read the abnormal data normally, the validity of the data collected by the acquisition module is determined to be valid.

6. A master control device, characterized in that, The main control device belongs to the battery management system, which also includes a data acquisition module and several analog front-ends. The main control device and the analog front-ends form a daisy chain. The main control device includes: The judgment unit is used to determine whether the data collected by the acquisition module is abnormal when the acquisition module collects data through the daisy chain; The diagnostic unit is used to determine the daisy chain as a communication failure if the data collected by the acquisition module is abnormal. The fault cause determination unit is used to perform several one-way reads of the abnormal data that has occurred through each analog front end, and determine the fault cause of the communication fault based on the reading result of each one-way read. The unidirectional read can be either a forward read or a reverse read, with one forward read and one reverse read constituting one cycle read; By performing several one-way reads on the abnormal data from each simulated front end, the cause of the communication failure is determined based on the results of each one-way read, including: Determine if a one-way loop exists that can normally read the abnormal data; If there is no unidirectional loop that can read the abnormal data normally, the abnormal data will be read in several loops through each simulation front end. Determine whether the abnormal data can be read normally in each of several loop reads; If the abnormal data can be read normally in several loop reads, then the cause of the fault is determined to be a single point of failure.

7. A computer device, characterized in that, include: The computer device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the daisy-chain communication fault diagnosis method as described in any one of claims 1 to 5 are performed.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the daisy-chain communication fault diagnosis method as described in any one of claims 1 to 5.

Images