Daisy chain communication fault diagnosis method, master control device, equipment and storage medium

Abstract

The invention provides a daisy chain communication fault diagnosis method, a master control device, equipment and a storage medium, the daisy chain communication fault diagnosis method is applied to the master control device in a battery management system, the battery management system further comprises an acquisition module and a plurality of analog front ends, and the master control device and the analog front ends form a daisy chain. When the acquisition module performs data acquisition through the daisy chain, judging whether the data acquired by the acquisition module is abnormal or not; if the data acquired by the acquisition module is abnormal, the daisy chain is determined as a communication fault; and carrying out multiple times of unidirectional reading on the abnormal data which is abnormal through each analog front end, and determining the fault reason of the communication fault according to the reading result of each time of unidirectional reading. By adopting the method, communication fault diagnosis is carried out on the daisy chain, and the communication state and the fault reason of the daisy chain are obtained in time.

Description

Technical Field

[0001] The present invention relates to the field of battery management technology, and in particular to a daisy chain communication fault diagnosis method, a main control device, equipment and a storage medium. Background Art

[0002] With the development of BWS battery management system technology, it has become a trend for the communication between BMS single sampling chips to develop from CAN communication to daisy chain communication. Compared with CAN communication, daisy chain communication has a huge cost advantage. As an emerging communication method between modules within the battery management system, it is now widely used for its low cost, simple application, simplified wiring harness and other designs.

[0003] However, the research found that the communication mode of daisy chain communication is cascade communication, and cascade communication is one of the most unstable systems, which often leads to communication failures such as broken links, resulting in abnormal communication in the battery management system. Therefore, how to diagnose communication failures of daisy chains and timely obtain the communication status and cause of failures of daisy chains has become an urgent problem to be solved. Summary of the invention

[0004] In view of this, an object of the present invention is to provide a daisy chain communication fault diagnosis method, a main control device, an equipment and a storage medium, so as to diagnose the communication fault of the daisy chain and promptly know the communication status of the daisy chain and the cause of the fault.

[0005] In a first aspect, an embodiment of the present application provides a daisy chain communication fault diagnosis method, which is applied to a main control device in a battery management system, wherein the battery management system further includes an acquisition module and a plurality of analog front ends, wherein the main control device and the analog front ends constitute a daisy chain, and when the acquisition module performs data acquisition 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 collection module is abnormal, the daisy chain is determined to be a communication failure;

[0008] The abnormal data having the abnormality is read unidirectionally several times through each analog front end, and the cause of the communication fault is determined according to the reading result of each unidirectional reading.

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

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

[0011] Optionally, the unidirectional reading is forward reading or reverse reading, so that one forward reading and one reverse reading constitute one cyclic reading.

[0012] Optionally, each analog front end performs a unidirectional reading of the abnormal data several times, and determines the cause of the communication failure according to the reading result of each unidirectional reading, including:

[0013] Determine whether there is a one-way loop capable of reading the abnormal data normally;

[0014] If there is no one-way cycle capable of reading the abnormal data normally, the abnormal data is read several times in a cycle through each analog front end;

[0015] Determine whether the abnormal data can be read normally in several cycles of reading;

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

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

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

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

[0020] If the data collected by the collection module is abnormal, the validity of the data collected by the collection module is determined to be invalid;

[0021] If there is no abnormality in the data collected by the collection module, the validity of the data collected by the collection module is determined to be valid.

[0022] Optionally, after determining whether there is a one-way loop capable of reading the abnormal data normally, the method further includes:

[0023] If there is a one-way loop capable of reading the abnormal data normally, the validity of the data collected by the collection module is determined to be valid;

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

[0025] If a cyclic reading occurs in which the abnormal data can be read normally, the validity of the data collected by the collection module is determined to be valid.

[0026] In a second aspect, an embodiment of the present application provides a main control device, which belongs to a battery management system. The battery management system also includes an 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] A judging unit, used for judging whether the data collected by the collecting module is abnormal when the collecting module collects data through the daisy chain;

[0028] a diagnostic unit, configured to determine that the daisy chain is a communication failure if the data collected by the collection module is abnormal;

[0029] The fault cause determination unit is used to perform unidirectional reading of abnormal data with abnormalities for several times through each analog front end, and determine the fault cause of the communication fault according to the reading result of each unidirectional reading.

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

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

[0032] Optionally, the unidirectional reading is forward reading or reverse reading, so that one forward reading and one reverse reading constitute one cyclic reading.

[0033] Optionally, each analog front end performs a unidirectional reading of the abnormal data several times, and determines the cause of the communication failure according to the reading result of each unidirectional reading, including:

[0034] Determine whether there is a one-way loop capable of reading the abnormal data normally;

[0035] If there is no one-way cycle capable of reading the abnormal data normally, the abnormal data is read several times in a cycle through each analog front end;

[0036] Determine whether the abnormal data can be read normally in several cycles of reading;

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

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

[0039] Optionally, the fault cause determination unit is configured to, after determining whether the data collected by the acquisition module is abnormal, determine the validity of the data collected by the acquisition module as invalid if 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 there is no abnormality in the data collected by the acquisition module.

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

[0042] The fault cause determination unit is used to determine whether the abnormal data can be read normally in several cyclic readings, and if a cyclic reading that can read the abnormal data normally occurs, determine the validity of the data collected by the collection module as valid.

[0043] In a third aspect, an embodiment of the present application provides a computer device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the computer device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the steps of the daisy chain communication fault diagnosis method described in any optional implementation manner of the first aspect are performed.

[0044] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the daisy chain communication fault diagnosis method described in any optional implementation manner in the above-mentioned first aspect are executed.

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

[0046] The present application determines whether the data collected by the acquisition module is abnormal, determines whether a communication failure occurs in the daisy chain based on the judgment result, and in the event of a communication failure, performs several unidirectional readings of the abnormal data through each analog front end, and determines the cause of the communication failure based on the reading result of each unidirectional reading, thereby enabling communication failure diagnosis of the daisy chain and timely knowing the communication status and cause of the daisy chain.

[0047] In addition, the present application, through the logical judgment of normal data collection and chain break, and through the repeated cycle reading of unidirectional and bidirectional reading data, the correctness of the read data and the existence of the fault point are confirmed, and the automatic recovery of the chain break, the data processing of the chain break recovery and the communication switching operation mode in the single point fault situation are considered. When the battery management system detects a chain break in the daisy chain, it can quickly identify and locate the location of the fault, which helps to timely discover and solve potential safety hazards and prevent further damage to the battery system. At the same time, since the daisy chain break may cause the communication between the battery modules to be interrupted, thereby affecting the monitoring of the entire battery pack by the battery management system, and through the chain break diagnosis, the battery management system can ensure the integrity of the system, reduce the safety risks caused by communication failures, and improve the safety of the battery management system. Furthermore, by monitoring the status of the daisy chain, the battery management system can ensure that the information transmission between the battery modules is unimpeded, thereby optimizing the performance of the battery. This helps to improve the energy efficiency of the battery, extend the service life of the battery, and optimize the battery performance. Finally, the daisy chain break diagnosis function of the battery management system simplifies the maintenance of the battery system. When a fault occurs, the maintenance personnel can quickly find the problem based on the diagnostic information provided by the battery management system, reducing the maintenance cost and time cost.

[0048] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0050] Figure 1 A flow chart of a daisy chain communication fault diagnosis method provided by Embodiment 1 of the present invention is shown;

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

[0052] Figure 3 A flow chart of a daisy chain break diagnosis method provided by the first embodiment of the present invention is shown;

[0053] Figure 4 A schematic diagram showing the structure of a main control device provided by 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 DESCRIPTION

[0055] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. The components of the embodiments of the present invention generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present invention.

[0056] Embodiment 1

[0057] To facilitate understanding of this application, Figure 1 The flowchart of a daisy chain communication fault diagnosis method provided by the first embodiment of the present invention is shown to describe the contents of the first embodiment of the present application in detail.

[0058] See also Figure 1 As shown, Figure 1 A flowchart of a daisy chain communication fault diagnosis method provided in Embodiment 1 of the present invention is shown, wherein the main control device is applied to a battery management system, the battery management system further includes an acquisition module and a plurality of analog front ends, the main control device and the analog front ends form a daisy chain, when the acquisition module performs data acquisition through the daisy chain, the method includes steps S101 to S103:

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

[0060] Specifically, first, based on the state of the data collected by the acquisition module, it can be determined whether the daisy chain has a communication failure. If the state of the data collected by the acquisition module is normal, it means that the daisy chain can communicate normally and there is no communication failure.

[0061] S102: If the data collected by the collection module is abnormal, the daisy chain is determined to be a communication failure.

[0062] Specifically, on the contrary, if the state of the data collected by the collection module is abnormal, it means that the daisy chain cannot perform data transmission normally and a communication failure occurs.

[0063] S103: performing unidirectional reading of abnormal data for several times through each analog front end, and determining the cause of the communication failure according to the reading result of each unidirectional reading.

[0064] Specifically, when it is determined that there is a problem with the collected data, a broken chain detection is started, and abnormal data with abnormalities is continuously read, and the cause of the communication failure of the daisy chain is determined based on the reading result of each unidirectional reading.

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

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

[0067] Specifically, PEC is a communication data error check. When a PEC error occurs at the same time and the data collected by the acquisition module are all 0xFF (hexadecimal), the data collected by the acquisition module is determined to be abnormal.

[0068] In an optional embodiment, the unidirectional reading is forward reading or reverse reading, so that one forward reading and one reverse reading are performed as one cyclic reading.

[0069] Specifically, read forward once and read backward once, which is recorded as one cycle reading.

[0070] In an alternative embodiment, see Figure 2 As shown, Figure 2 A flow chart of a method for determining a fault cause provided by the first embodiment of the present invention is shown, wherein each analog front end performs a unidirectional reading of abnormal data with an abnormality for several times, and determines the fault cause of the communication fault according to the reading result of each unidirectional reading, including steps S201 to S204:

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

[0072] S202: If there is no one-way cycle capable of reading the abnormal data normally, the abnormal data is read several times in a cycle through each analog front end.

[0073] S203: Determine whether the abnormal data can be read normally in several cycles of reading.

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

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

[0076] Step 1: If normal data is read unidirectionally during the loop reading process, the loop reading is exited.

[0077] Step 2: If the data read in one direction are all wrong and the data read in two directions are complete after 6 consecutive read cycles, it is determined whether the error is in the same position; if it is in the same position, a single point fault is reported and the communication is switched to dual-chain communication; if it is not in the same position, a single point fault is also reported and the communication is switched to dual-chain communication, and the broken link position is reported. If the single point fault is found to have disappeared during the dual-chain communication, it is jumped to step 1.

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

[0079] If a cyclic reading in which the abnormal data cannot be read normally occurs, the cause of the fault is determined to be a multi-point fault.

[0080] Specifically, if the combined data is identified to be incomplete during the dual-link communication process, the cause of the fault is determined to be a multi-point fault, and the fault diagnosis in steps S101 to S103 is executed cyclically, and the number of cyclic fault diagnosis is recorded; it is determined whether the loop cause obtained after continuous cyclic fault diagnosis is a multi-point fault for more than 3 consecutive times, and if so, a reset operation is performed to reinitialize; and the fault diagnosis steps are repeated to determine whether the loop cause obtained after continuous cyclic fault diagnosis is a multi-point fault for more than 3 consecutive times. When resetting to try to recover, all faulty interfaces of 6830 are cleared to 0 (except for multi-point faults).

[0081] During the process of detecting and confirming multiple-point faults, if the data combination is incomplete, the missing data is set to 0xFF and the validity is set to invalid. The readable data is uploaded normally and the data is valid. During the reset period (trying to restore the reset), all collected data maintain the last value, and the data validity is set to invalid until the reset is restored, and then the sampling data is updated. If the cycle cause obtained after the cycle fault diagnosis is a multiple-point fault for more than 3 consecutive times, a multiple-point fault is reported; after the multiple-point fault is confirmed, data collection continues, and it is determined whether the data combination is complete. If the data is complete, the multiple-point fault is jumped out; otherwise, the multiple-point fault state is maintained.

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

[0083] If the data collected by the collection module is abnormal, the validity of the data collected by the collection module is determined to be invalid.

[0084] If there is no abnormality in the data collected by the collection module, the validity of the data collected by the collection module is determined to be valid.

[0085] Specifically, after determining whether the data collected by the collection 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 there is a one-way loop capable of reading the abnormal data normally, the method further includes:

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

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

[0089] If a cyclic reading occurs in which the abnormal data can be read normally, the validity of the data collected by the collection module is determined to be valid.

[0090] Specifically, in the cyclic reading judgment logic, if the unidirectional data returns to normal during the cyclic reading process, the data validity is set to valid; if the data combination is normal during the cyclic reading 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 by the present application can be used to diagnose the loopback daisy chain in the following types of battery management systems. The loopback daisy chain is composed of a main control device, a first communication unit and a second communication unit connected to the main control device, and a plurality of analog front ends. Starting from the analog front end connected to the first communication unit, multiple analog front ends in the loopback daisy chain are accessed in sequence to determine the first analog front end that is closest to the first communication unit; when the first communication unit accesses the first analog front end, multiple analog front ends in the loopback daisy chain are accessed in sequence to determine that the signal data is read in this direction; based on the first analog front end and the Nth analog front end, the state information of the loopback daisy chain is determined. When the state information of the loopback daisy chain is determined in 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 closest to the first communication unit in the loopback daisy chain, and the Nth analog front end is the analog front end closest to the second communication unit in the loopback daisy chain, it is determined that the state data content reading of the loopback daisy chain occurs in a state where both sides are fully passed, which is a forward cycle. When the second communication unit accesses the Nth analog front end, it starts to sequentially access multiple analog front ends in the loopback daisy chain to determine that signal data is read in this direction; based on the Nth analog front end and the first analog front end, the state information of the loopback daisy chain is determined. It is determined that the state data content reading of the loopback daisy chain occurs in the state of full pass on both sides, which is a reverse cycle.

[0092] See also Figure 3 As shown, Figure 3 The flowchart of a daisy chain break diagnosis method provided by the first embodiment of the present invention is shown, wherein, when diagnosing the daisy chain break, the main control device first controls the acquisition module to collect data normally, and determines whether there is a problem according to the chain break situation. If not, continue to collect other data, and if so, record the forward and reverse readings once each as 1 cycle for cyclic reading, and determine whether the following situations exist during the cyclic reading process: Situation S, unidirectional reading is normal in the cycle; Situation Y, unidirectional errors in 6 cycles and bidirectional data are complete; Situation Z, unidirectional errors in 6 cycles and bidirectional data are incomplete. If it is situation S, continue to collect other data; if it is situation Y, determine whether the error is in the same position. If so, report a single-point fault and perform dual-chain communication. Otherwise, report a single-point fault, perform dual-chain communication, and report the broken link position; if it is situation Z, loop the above steps to determine whether the number of cycles is greater than 3 times. If otherwise, continue to loop. If so, perform Reset, reinitialize, repeat the above steps, loop the above steps to determine whether the number of cycles is greater than 3 times. If otherwise, continue to loop. If so, report multiple-point faults, continue to read data and determine whether the data combination is complete; if so, continue to collect other data. Otherwise, report multiple-point faults.

[0093] When judging the validity of collected data, the following steps are included:

[0094] Step 1: Apply high voltage to read data. Determine whether the relevant data can be read. If the data can be read, proceed to the next step of judging the link break. If the data cannot be read, it is considered a failure. There are three types of link break judgment: single-point link break, double-point link break, and no link break.

[0095] Step 2: Conduct process judgment and simulate the actual processing situation. When there is a single-point disconnection, collect the battery cell voltage and temperature, upload the data, and modify the flag. When there is a double-point disconnection, modify the flag and the data will become invalid. When there is no disconnection, collect the battery cell voltage and temperature, upload the data, initialize, and modify the flag.

[0096] Step 3: Data selection. When there is a single point of disconnection, modify the marked position and upload the data to determine whether the data is qualified. If it is qualified, the data is valid, otherwise the data is invalid. When there is no disconnection, modify the marked position and upload the data to determine whether the data is qualified. If it is qualified, the data is valid, otherwise the data is invalid.

[0097] Embodiment 2

[0098] See also Figure 4 As shown, Figure 4 The structure diagram of a main control device provided in the second embodiment of the present invention is shown, wherein the main control device belongs to a battery management system, the battery management system further includes an acquisition module and several analog front ends, the main control device and each analog front end form a daisy chain, and the main control device includes:

[0099] A judging unit 401, configured to judge whether the data collected by the collecting module is abnormal when the collecting module collects data through the daisy chain;

[0100] A diagnostic unit 402, configured to determine that the daisy chain is a communication failure if the data collected by the collection module is abnormal;

[0101] The fault cause determination unit 403 is used to perform unidirectional reading of abnormal data with abnormality for several times through each analog front end, and determine the fault cause of the communication fault according to the reading result of each unidirectional reading.

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

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

[0104] In an optional embodiment, the unidirectional reading is forward reading or reverse reading, so that one forward reading and one reverse reading are performed as one cyclic reading.

[0105] In an optional implementation scheme, each analog front end performs a unidirectional reading of abnormal data several times, and determines the cause of the communication failure according to the reading result of each unidirectional reading, including:

[0106] Determine whether there is a one-way loop capable of reading the abnormal data normally;

[0107] If there is no one-way cycle capable of reading the abnormal data normally, the abnormal data is read several times in a cycle through each analog front end;

[0108] Determine whether the abnormal data can be read normally in several cycles of reading;

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

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

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

[0112] The fault cause determination unit is used to determine the validity of the data collected by the acquisition module as valid if there is no abnormality 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 there is a one-way loop capable of reading the abnormal data normally after determining whether there is a one-way loop capable of reading the abnormal data normally;

[0114] The fault cause determination unit is used to determine whether the abnormal data can be read normally in several cyclic readings, and if a cyclic reading that can read the abnormal data normally occurs, determine the validity of the data collected by the collection module as valid.

[0115] Embodiment 3

[0116] Based on the same application concept, see Figure 5 As shown, Figure 5 FIG. 4 shows a schematic diagram of the structure of a computer device provided by Embodiment 3 of the present invention, wherein: Figure 5 As shown, a computer device 500 provided in Embodiment 3 of the present application includes:

[0117] A processor 501, a memory 502 and a bus 503, wherein the memory 502 stores machine-readable instructions executable by the processor 501. When the computer device 500 is running, the processor 501 communicates with the memory 502 via the bus 503. When the processor 501 is running, the machine-readable instructions execute the steps of the daisy chain communication fault diagnosis method shown in the above-mentioned embodiment 1.

[0118] Embodiment 4

[0119] Based on the same application concept, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the daisy chain communication fault diagnosis method described in any one of the above embodiments are executed.

[0120] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system and device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0121] The computer program product for daisy chain communication fault diagnosis provided in the embodiment of the present invention includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the method described in the previous method embodiment. The specific implementation can be found in the method embodiment and will not be repeated here.

[0122] The main control device provided in the embodiment of the present invention can be specific hardware on the device or software or firmware installed on the device. The device provided in the embodiment of the present invention has the same implementation principle and technical effects as the aforementioned method embodiment. For the sake of brief description, the parts not mentioned in the device embodiment can refer to the corresponding contents in the aforementioned method embodiment. Technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can all refer to the corresponding processes in the aforementioned method embodiment, and will not be repeated here.

[0123] In the embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

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

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

[0126] If the functions are implemented in the form of 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 the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc., which can store program codes.

[0127] It should be noted that similar numbers and letters represent similar items in the following figures. 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 only used to distinguish the description and are not to be understood as indicating or implying relative importance.

[0128] Finally, it should be noted that the above-described embodiments are only specific implementations of the present invention, which are used to illustrate the technical solutions of the present invention, rather than to limit them. The protection scope of the present invention is not limited thereto. Although the present invention is described in detail with reference to the above-described embodiments, those skilled in the art should understand that any person skilled in the art can still modify the technical solutions described in the above-described embodiments within the technical scope disclosed by the present invention, or can easily think of changes, or perform equivalent replacements on some of the technical features thereof; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. They should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A daisy chain communication fault diagnosis method, characterized in that: A main control device applied to a battery management system, the battery management system further comprising an acquisition module and a plurality of analog front ends, the main control device and the analog front ends forming a daisy chain, when the acquisition module performs data acquisition through the daisy chain, the method comprising: Determine whether the data collected by the acquisition module is abnormal; If the data collected by the collection module is abnormal, the daisy chain is determined to be a communication failure; The abnormal data having the abnormality is read unidirectionally several times through each analog front end, and the cause of the communication fault is determined according to the reading result of each unidirectional reading.

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

3. The method according to claim 1, characterized in that The unidirectional reading is forward reading or reverse reading, and one forward reading and one reverse reading constitute one cycle reading.

4. The method according to claim 3, characterized in that The abnormal data that has abnormality is read several times in one direction through each analog front end, and the cause of the communication fault is determined according to the reading result of each one-way reading, including: Determine whether there is a one-way loop capable of reading the abnormal data normally; If there is no one-way cycle capable of reading the abnormal data normally, the abnormal data is read several times in a cycle through each analog front end; Determine whether the abnormal data can be read normally in several cycles of reading; If the abnormal data can be read normally in several cyclic readings, the cause of the failure is determined to be a single point failure.

5. The method according to claim 4, characterized in that After determining whether the abnormal data can be read normally in several cycles of reading, the method further includes: If a cyclic reading in which the abnormal data cannot be read normally occurs, the cause of the fault is determined to be a multi-point fault.

6. The method according to claim 5, characterized in that After determining whether the data collected by the collection module is abnormal, the method further includes: If the data collected by the collection module is abnormal, the validity of the data collected by the collection module is determined to be invalid; If there is no abnormality in the data collected by the collection module, the validity of the data collected by the collection module is determined to be valid.

7. The method according to claim 5, characterized in that After determining whether there is a one-way loop capable of reading the abnormal data normally, the method further includes: If there is a one-way loop capable of reading the abnormal data normally, the validity of the data collected by the collection module is determined to be valid; After determining whether the abnormal data can be read normally in several cycles of reading, the method further includes: If a cyclic reading occurs in which the abnormal data can be read normally, the validity of the data collected by the collection module is determined to be valid.

8. A main control device, characterized in that: The main control device belongs to a battery management system. The battery management system also includes an 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: A judging unit, used for judging whether the data collected by the collecting module is abnormal when the collecting module collects data through the daisy chain; a diagnostic unit, configured to determine that the daisy chain is a communication failure if the data collected by the collection module is abnormal; The fault cause determination unit is used to perform unidirectional reading of abnormal data with abnormalities for several times through each analog front end, and determine the fault cause of the communication fault according to the reading result of each unidirectional reading.

9. A computer device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the computer device is running, the processor and the memory communicate via the bus, and 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 7 are performed.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the daisy chain communication fault diagnosis method according to any one of claims 1 to 7 are executed.

Images