Method for generating auxiliary troubleshooting strategy for communication fault of locomotive power battery system

Abstract

A method for generating an auxiliary troubleshooting strategy for communication faults of a locomotive power battery system. The method comprises: acquiring a communication fault troubleshooting record of a locomotive power battery system; extracting fault causes at various levels for each type of communication faults, and establishing a fault tree; when there is a specific alarm communication fault, determining the time type and duration of the communication fault, and intercepting a fault subtree of the alarm communication fault; qualitatively analyzing the fault subtree to obtain a minimum cut set; quantitatively analyzing the fault subtree to obtain critical importance degrees of bottom events, and ranking same in a descending order; correcting the ranking of the importance degrees of the bottom events, so as to form a bottom event importance degree ranking table; and successively performing troubleshooting on the basis of the bottom event importance degree ranking table. Auxiliary troubleshooting strategies for communication faults are provided accurately, which improves the efficiency and accuracy of troubleshooting communication faults by maintenance staff, and helps to take corresponding maintenance measures, thus improving the utilization rate of new energy locomotives, and reducing downtime costs.

Description

A method for generating a strategy to assist in troubleshooting communication faults in a locomotive power battery system Technical Field

[0001] This invention relates to the field of rail transit operation and maintenance, and in particular to a method for generating auxiliary troubleshooting strategies for communication faults in locomotive power battery systems. Background Technology

[0002] Against the backdrop of energy conservation and environmental protection, the promotion of new energy locomotives has accelerated significantly. Pure electric locomotives and hybrid locomotives, powered by batteries, are replacing older internal combustion engine locomotives. Electronic and electrical technologies are being widely applied in battery systems, resulting in much more frequent communication within and between systems compared to traditional internal combustion engine locomotives. This leads to a high frequency of communication fault alarms, which can easily affect the operating status and data accuracy of the battery system. However, current diagnostic methods for communication faults typically rely on abnormal message checksums or interrupted vital signals. Furthermore, data problems caused by communication faults prevent automatic fault location based on data, requiring manual troubleshooting, which is time-consuming and labor-intensive. Moreover, existing technologies only diagnose high-voltage power-on and insulation faults in electric vehicles and cannot troubleshoot the complex communication faults in the battery systems of new energy locomotives. Therefore, there is an urgent need for a method to generate auxiliary troubleshooting strategies for communication faults in the battery systems of new energy locomotives. This would assist maintenance personnel in troubleshooting communication faults, improve the efficiency of root cause location, and increase locomotive utilization. Summary of the Invention

[0003] To address the problems existing in the prior art, a method for generating auxiliary troubleshooting strategies for communication faults in locomotive power battery systems is provided. This method is mainly aimed at complex communication faults in the power battery systems of new energy locomotives. It can assist maintenance personnel in troubleshooting communication faults, improve the efficiency of fault root cause location, and increase the utilization rate of locomotives.

[0004] The technical solution adopted in this invention is as follows: A method for generating a strategy to assist in troubleshooting communication faults in a locomotive power battery system, comprising:

[0005] Obtain the fault repair records of the locomotive's power battery system and extract the communication fault repair records;

[0006] Based on the communication fault repair records, the causes of each type of communication fault are extracted at each level, and a fault tree for communication faults in the power battery system is established.

[0007] When a specific alarm communication failure exists, determine the time type of the communication failure, record the duration of the failure, and extract the fault subtree of the alarm communication failure from the established fault tree according to the fault name.

[0008] Qualitative analysis is performed on the fault subtree of alarm communication failure to obtain the minimum cut set;

[0009] Quantitative analysis of the fault subtree of alarm communication failure is performed. The critical importance of the bottom events is obtained by combining communication failure repair records and minimum cut sets, and the critical importance of the bottom events is sorted in descending order.

[0010] The importance ranking of bottom events is revised based on the duration of the failure and the type of communication failure time, resulting in the final importance ranking table of bottom events.

[0011] The faults are investigated sequentially according to the importance ranking table of the underlying events, and the root cause of the fault is finally detected.

[0012] As a preferred embodiment, the step of extracting the causes of each type of communication fault from the communication fault repair records at various levels specifically includes:

[0013] Based on the fault name and fault phenomenon in the communication fault repair records, communication faults are classified.

[0014] For each type of communication fault, the causes of the fault at each level are determined based on the fault investigation records in the communication fault maintenance records. The primary fault that directly causes the fault is the primary cause, the next level fault that causes the primary fault is the secondary cause, and so on, until the lowest level cause of the fault is determined in the fault investigation records.

[0015] The causes of each type of communication failure and each level of failure are broken down and recorded step by step to complete the extraction of failure causes.

[0016] As a preferred embodiment, the establishment of a fault tree for communication faults in the power battery system specifically includes:

[0017] The top event of the communication fault tree of the power battery system is determined based on the communication fault repair records; the top event is the communication fault.

[0018] Determine the boundary conditions of the communication fault tree;

[0019] By combining the various causes of the top event and the causes at each level, a fault tree for communication failures in the power battery system is established.

[0020] As a preferred embodiment, the determination of the boundary conditions for the communication fault tree specifically includes:

[0021] Determine the operating status of the components related to the occurrence of the top event;

[0022] The events considered unacceptable during the construction of the fault tree are identified, with low-probability events being considered unacceptable events;

[0023] To determine events that are bound to happen and events that are bound to not happen under certain conditions.

[0024] As a preferred embodiment, the establishment of a fault tree for communication faults in the power battery system specifically includes:

[0025] The lowest-level cause of each type of communication failure is designated as the bottom event of the fault tree, while other failure causes besides the top and bottom events are designated as intermediate events.

[0026] Starting from the top event, the deductive method is used to gradually decompose and expand downwards until the bottom event is reached;

[0027] To determine the logical relationships between adjacent levels of the communication fault tree, within the same fault tree, events at lower levels are considered input events of higher levels, and events at higher levels are considered output events of lower levels. If an output event is guaranteed to occur when all input events occur simultaneously, an AND gate is used. If at least one input event occurs and the output event occurs more than once, an OR gate is used. If an input event is the inverse of an output event, a NOT gate is used. If at least r of n input events occur and the output event is guaranteed, a voting gate is used. If the output event is guaranteed to occur even if no input events occur simultaneously, an XOR gate is used. If an input event causes an output event only when the disable gate condition is met, a disable gate is used. If an output event occurs only when the input events occur in a specified order, a sequential AND gate is used. If an input event causes an output event only when it occurs and lasts for a certain period, a duration AND gate is used.

[0028] Using logical relationship graphical symbols to connect upper and lower level events, a power battery system communication fault tree diagram is formed and output, thus completing the establishment of the power battery system communication fault tree.

[0029] As a preferred embodiment, when a specific alarm communication failure exists, determining the communication failure time type and recording the failure duration specifically includes:

[0030] When a specific alarm communication fault exists, the communication fault is transmitted to the locomotive microcomputer through the communication harness, and the specific fault information is displayed by the control panel display unit, including the fault occurrence time, fault name, fault code, and fault level.

[0031] If a specific alarm communication fault only alarms once and then returns to normal, it is considered a flash alarm communication fault, and the fault duration is the communication cycle of the specific alarm communication fault type.

[0032] If a specific alarm communication failure is reported intermittently or the failure is eliminated after a system reset, it is considered an intermittent communication failure, and the longest failure duration is taken as the failure duration.

[0033] If a specific alarm communication fault continues to be reported and the fault is not eliminated after system reset, it is considered a continuous communication fault. The difference between the current time of maintenance and the time when the fault occurred is taken as the fault duration.

[0034] As a preferred embodiment, the qualitative analysis of the fault subtree of the alarm communication failure to obtain the minimum cut set specifically includes:

[0035] The minimum cut set of the fault tree for a specific alarm communication fault is obtained using the uplink method, and the calculation starts from the intermediate event at the lowest level.

[0036] If an intermediate event is connected to a base event via a logical AND gate, then the intermediate event is represented using an AND gate structure function.

[0037] If an intermediate event is connected to the underlying event via a logical OR gate, use an OR gate structure function to represent the intermediate event.

[0038] If an intermediate event is connected to a base event via a NOT gate, the NOT gate structure function is used to represent the intermediate event.

[0039] If an intermediate event is connected to the underlying event via a logical XOR gate, the XOR gate structure function is used to represent the intermediate event.

[0040] If an intermediate event is connected to a base event via a logical conditional AND gate, the conditional AND gate is represented as an AND gate between the original base event and the conditional event, and the intermediate event is represented using an AND gate structure function.

[0041] By proceeding sequentially upwards to the top event, we obtain the top event structure function representing all bottom events. We then simplify this function using Boolean algebra to obtain the structure function expression of the sum of bottom event products with the minimum number of terms. Each product of terms is a minimal cut set.

[0042] As a preferred approach, the quantitative analysis of the fault subtree of the alarm communication fault, combined with the communication fault repair records and the minimum cut set to obtain the critical importance of the bottom event, specifically includes:

[0043] By analyzing communication fault repair records, the probability of failure for low-level events can be obtained.

[0044] The base events in the fault tree are independent of each other. The fault probability of all minimum cut sets is calculated, and the fault probability of the intersection of the base events is equal to the product of the fault probabilities of the base events.

[0045] Based on the top event structure function, the failure probability of the top event is calculated using the failure probabilities of all minimum cut sets;

[0046] For each bottom event, calculate the partial derivative of the top event structure function with respect to the bottom event. Multiply the bottom event failure probability by the partial derivative and divide by the top event failure probability to obtain the criticality of the bottom event. Repeat this process until the criticality of all bottom events has been calculated.

[0047] As a preferred embodiment, the step of revising the importance ranking of bottom events based on fault duration and communication fault time type to form a final bottom event importance ranking table specifically includes:

[0048] Based on the fault tree, the fault phenomena of intermediate events are used to classify the bottom events, and each bottom event corresponds to a communication fault time type.

[0049] Obtain the duration and type of the alarm communication failure. If the communication failure type is a flash communication failure and the duration is less than 1 second, divide the critical importance of the underlying event corresponding to the communication failure time type by the duration of the failure, and multiply the critical importance of the other underlying events by the duration of the failure.

[0050] If the communication failure time type is intermittent communication failure and the failure duration is greater than 1 second, then the critical importance of the underlying event corresponding to the communication failure time type is multiplied by the failure duration, and the critical importance of other underlying events is divided by the failure duration.

[0051] If the communication failure time type is a continuous communication failure, then the critical importance of the underlying event corresponding to the communication failure time type is multiplied by the failure duration, and the critical importance of other underlying events is divided by the failure duration.

[0052] Based on the revised critical importance, the bottom events are sorted in descending order of the revised critical importance to form the final bottom event importance ranking table.

[0053] As a preferred embodiment, the step of sequentially investigating faults according to the importance ranking table of basic events to ultimately achieve root cause detection of faults specifically includes:

[0054] Check the bottom events in the bottom event importance ranking table in order from front to back;

[0055] If the current bottom event is fault-free and not included in the minimum cut set, then check the next bottom event; if the current bottom event is fault-free and included in the minimum cut set, then check other bottom events in the minimum cut set according to importance. If a fault exists, then find out the cause of the fault; if the current bottom event has a fault cause, then find out the cause of the fault.

[0056] Exclude the bottom events that have already been checked, and check the other bottom events in sequence until the last bottom event is checked to complete the troubleshooting.

[0057] Compared with the prior art, the beneficial effects of adopting the above technical solution are as follows: This invention provides accurate auxiliary troubleshooting strategies for communication faults by qualitative and quantitative analysis of the fault tree of the power battery system of new energy locomotives, combined with the duration and time type of the communication faults. This improves the efficiency and accuracy of maintenance personnel in troubleshooting communication faults, facilitates the adoption of corresponding maintenance measures, increases the utilization rate of new energy locomotives, and reduces downtime costs. Attached Figure Description

[0058] Figure 1 is a flowchart of the method for generating a strategy to assist in troubleshooting communication faults in a locomotive power battery system proposed in this invention.

[0059] Figure 2 is a communication topology diagram of the power battery system proposed in an embodiment of the present invention.

[0060] Figure 3 is a flowchart of the fault diagnosis process based on the importance ranking table proposed in an embodiment of the present invention. Detailed Implementation

[0061] The embodiments of this application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar modules or modules having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application. Rather, the embodiments of this application include all variations, modifications, and equivalents falling within the spirit and scope of the appended claims.

[0062] Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without inventive effort are within the scope of protection of this application. Unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other. Furthermore, although a logical order is shown in the flowcharts, in some cases, the steps shown or described may be performed in a different order than that shown here.

[0063] To assist maintenance personnel in troubleshooting communication faults and improve the efficiency of root cause location and locomotive utilization, this invention proposes a method for generating auxiliary troubleshooting strategies for locomotive power battery systems, primarily applied in new energy locomotives. The specific solution is as follows:

[0064] Step 1: Obtain the fault repair records of the locomotive's power battery system and separate the communication fault repair records.

[0065] In this embodiment, the locomotive is a new energy locomotive, which includes pure electric locomotives or hybrid locomotives that use power batteries as a power source. The power battery system refers to an energy storage device used to provide energy to the new energy locomotive, consisting of multiple battery packs, a fire protection system, a thermal protection system, a battery management system, high-voltage circuits and protection components, sensors and low-voltage wiring harnesses, and a mechanical structure. The fault repair record refers to the repair record of faults occurring during the operation of the new energy locomotive by maintenance personnel. It typically includes the locomotive model, vehicle number, fault occurrence time, fault name, fault phenomenon, fault severity level, fault investigation record, and fault cause analysis.

[0066] Communication faults describe communication failures within or between different subsystems of a power battery system, referring to data distortion or communication interruptions. Based on the communication topology of the power battery system, communication fault subclasses can be determined, as shown in Figure 2, including:

[0067] Obtain the communication topology diagram of the power battery system and determine that the communication of the power battery system involves internal communication between the battery control unit (BCU) and the battery monitoring unit (BMU), communication between the battery control unit (BCU) and the fire protection system, communication between the battery control unit (BCU) and the thermal protection system, communication between the battery control unit (BCU) and the locomotive microcomputer, and communication between the battery control unit (BCU) and the insulation tester.

[0068] In practical applications, the model, license plate number, and fault repair records of new energy locomotives can be obtained. These records can be used to mark fault repairs related to the power battery system, including battery cells, battery circuits, BMS, communication systems, fire protection systems, thermal protection systems, fuses, and contactors. bat ; Tag-based power battery system fault repair records R bat Segment the communication fault repair record R bat-com .

[0069] Step 2: Extract the causes of each type of communication fault from the communication fault repair records and establish a fault tree for the communication faults of the power battery system.

[0070] After obtaining the communication fault repair record, the communication faults are classified according to the fault name and fault symptoms. In this embodiment, the communication fault repair record R... bat-com The fault name in R is used as the top-level fault, according to R bat-comThe fault investigation records are used to search for fault causes level by level, down to the root cause. Specifically, for each type of communication fault, the fault investigation records in the communication fault maintenance records are used to determine the causes of the fault at each level. The primary fault that directly causes the fault is the primary cause, the next level of fault that causes the primary fault is the secondary cause, and so on, until the lowest level cause of the fault is determined in the fault investigation records. Each type of communication fault and the causes of each level of fault are expanded and recorded step by step to complete the fault cause extraction.

[0071] Furthermore, after extracting the causes of each type of communication fault at each level, a fault tree for the communication faults of the power battery system can be established. The specific process is as follows:

[0072] Step 2.1: Determine the top event of the power battery system communication fault tree based on the communication fault repair records. The power battery system communication fault tree generally contains multiple fault subtrees. The top event of the power battery system communication fault tree refers to an undesirable fault event in the system, not a specific type of communication fault. The top event of a fault subtree is generally the name of a specific type of alarm communication fault.

[0073] Step 2.2: Determine the boundary conditions of the communication fault tree.

[0074] In this embodiment, it is necessary to determine the working status of the components related to the occurrence of the top event, determine the events that are considered unacceptable during the process of building the fault tree, regard low-probability events as unacceptable events, and determine the events that are bound to occur and the events that are bound not to occur under certain conditions.

[0075] Step 2.3: Based on the various causes of the top event and the causes at each level, establish a fault tree for the communication failure of the power battery system.

[0076] In the process of building the process tree, the lowest level cause of each level of failure cause is taken as the bottom event of the failure tree, and the top event and other failure causes besides the bottom event are taken as intermediate events. Starting from the top event, the deductive method is used to gradually decompose and expand downwards until the bottom event.

[0077] The logical relationships between adjacent levels of the communication fault tree are determined. Within the same fault tree, an event at a lower level can be considered an input event of the upper level, and an event at an upper level can be considered an output event of the lower level. If the output event is guaranteed to occur when all input events occur simultaneously, an AND gate is used. If the output event occurs more than one of the input events, an OR gate is used. If the input event is the inverse of the output event, a NOT gate is used. If at least r of n input events occur, the output event is guaranteed to occur, a voting gate is used. If the output event is guaranteed to occur even if the input events do not occur simultaneously, an XOR gate is used. If an input event causes an output event only when the disable gate condition is met, a disable gate is used. If the output event occurs only when the input events occur in a specified order, a sequential AND gate is used. If the output event occurs only when the input event occurs and lasts for a certain period, a duration AND gate is used. The logical relationships are then connected using graphical symbols to form and output the inverted tree diagram of the power battery system communication fault tree, thus completing the establishment of the power battery system communication fault tree. It should be noted that when connecting hierarchical events, direct door-to-door connections are not allowed.

[0078] In one embodiment, when extracting the causes of each type of communication fault at various levels, the communication fault repair record R can be used as a reference. bat-com By confirming whether the fault is a flash communication fault, an intermittent communication fault, or a continuous communication fault, and by confirming whether the fault is eliminated after a system reset and restart, the corresponding fault time type F can be determined. type .

[0079] Step 3: When a specific alarm communication fault exists, determine the time type of the communication fault, record the duration of the fault, and extract the fault subtree of the alarm communication fault from the established fault tree according to the fault name.

[0080] An alarm communication fault refers to a situation where the battery management system of the power battery system detects a specific communication fault subtype, triggering an alarm and displaying it on the driver's cab control panel. Maintenance personnel or on-board mechanics can view the fault alarm status in real time via the display screen, or confirm the communication fault time type F by reviewing the fault history. type And the duration of the fault.

[0081] Specifically, when a specific alarm communication fault exists, the communication fault is transmitted to the locomotive's microcomputer through the communication harness. The control panel display unit displays the specific fault information, including the fault occurrence time, fault name, fault code, and fault level. If the specific alarm communication fault only alarms once and then returns to normal, it is considered a flash alarm communication fault, and the fault duration is the communication cycle of the specific alarm communication fault type. If the specific alarm communication fault is reported intermittently or the fault is cleared after a system reset, it is considered an intermittent communication fault, and the longest fault duration is taken as the fault duration. If the specific alarm communication fault is reported continuously and the fault is not cleared after a system reset, it is considered a continuous communication fault, and the difference between the current maintenance time and the fault occurrence time is taken as the fault duration.

[0082] Simultaneously, the fault subtree FT of the existing alarm communication fault can be extracted downwards from the established fault tree based on the fault name (i.e., the top event of the fault subtree). sub Subsequently, the FT can be based on this fault subtree. sub Perform fault analysis. In practical applications, alarm communication faults can also be used as intermediate events to perform matching in the communication fault tree (FT), and the process can be truncated downwards along this event until the bottom event is reached.

[0083] Step 4: Perform qualitative analysis on the fault subtree of the alarm communication failure to obtain the minimum cut set.

[0084] The minimum cut set MSC(i) refers to a set of bottom events in a fault tree. When these bottom events occur simultaneously, the top event must also occur. In this embodiment, the minimum cut set of the fault tree for a specific alarm communication fault is obtained using the uplink method, starting from the lowest level intermediate events. If an intermediate event is connected to a bottom event by a logical AND gate, the intermediate event is represented by an AND gate structure function. If an intermediate event is connected to a bottom event by a logical OR gate, the intermediate event is represented by an OR gate structure function. If an intermediate event is connected to a bottom event by a logical NOT gate, the intermediate event is represented by a NOT gate structure function. If an intermediate event is connected to a bottom event by a logical XOR gate, the intermediate event is represented by an XOR gate structure function. If an intermediate event is connected to a bottom event by a logical conditional AND gate, the conditional AND gate is represented as an AND gate between the original bottom event and the conditional event, and the intermediate event is represented by an AND gate structure function. This process continues upwards until the top event, obtaining the top event structure function representing all bottom events. Boolean algebra is used for simplification to obtain a structure function expression for the sum of bottom event products with the minimum number of terms. Each product of terms is a minimum cut set.

[0085] Step 5: Perform quantitative analysis on the fault subtree of the alarm communication fault, combine the communication fault repair record and the minimum cut set to obtain the critical importance of the bottom event, and sort the critical importance of the bottom event in descending order.

[0086] This embodiment provides a detailed calculation process for the critical importance of bottom-level events:

[0087] Step 5.1, through the communication fault repair record R bat-com To obtain the failure probability of the bottom event;

[0088] Step 5.2: The base events in the fault tree are independent of each other. Calculate the fault probability of all minimum cut sets. The fault probability of the intersection of the base events is equal to the product of the fault probabilities of the base events.

[0089] Step 5.3: Based on the top event structure function, calculate the top event failure probability using the failure probabilities of all minimum cut sets;

[0090] Step 5.4: For each bottom event, calculate the partial derivative of the top event structure function with respect to the bottom event. Multiply the bottom event failure probability by the partial derivative and divide by the top event failure probability to obtain the critical importance of the bottom event. Repeat this process until the critical importance of all bottom events has been calculated.

[0091] Key Importance I cr (i) refers to the ratio of the system failure probability change rate to the unit failure probability change rate. First, the top event failure probability Q should be calculated based on the top event structure function ψ(x), and then the bottom event E should be calculated. i Probability Importance I pr (i), finally calculating the base event E i In one embodiment, the key importance is calculated using the following formula:

[0092] Among them, MSC i Let q represent the i-th minimum cut set. i Let I represent the failure probability of the i-th bottom event, Q represent the failure probability of the top event, and I represent the failure probability of the bottom event. pr (i) represents the probability importance of the i-th bottom event, I cr (i) represents the criticality of the i-th bottom event.

[0093] Step 6: Correct the importance ranking of bottom events based on the duration of the fault and the type of communication fault time to form the final importance ranking table of bottom events.

[0094] In this embodiment, the fault phenomena of intermediate events are used to classify the base events based on the fault tree, and each base event corresponds to a communication fault time type; the fault duration DeltaT and the communication fault time type F of the alarm communication fault are obtained. type ,

[0095] If the communication failure time type F typeIf the communication failure is a flash message and the failure duration DeltaT is less than 1 second, then the communication failure time type F is... type The critical importance of the corresponding bottom event is divided by the failure duration DeltaT, and the critical importance of the remaining bottom events is multiplied by the failure duration.

[0096] If the communication failure time type F type If the communication is intermittent and the duration DeltaT is greater than 1 second, then the communication failure time type F is... type The critical importance of the corresponding bottom event is multiplied by the failure duration DeltaT, and the critical importance of the remaining bottom events is divided by the failure duration.

[0097] If the communication failure time type F type For persistent communication failures, the communication failure time type F type The critical importance of the corresponding bottom event is multiplied by the failure duration DeltaT, and the critical importance of the remaining bottom events is divided by the failure duration DeltaT.

[0098] Based on the revised critical importance, the bottom events are sorted in descending order of their revised critical importance, forming the final bottom event importance ranking table T. cr-rank .

[0099] Step 7: Troubleshoot according to the importance ranking table of the underlying events to ultimately achieve root cause detection of the fault.

[0100] In practical applications, please refer to Figure 3. The bottom events in the bottom event importance ranking table can be checked sequentially from front to back. If the current bottom event is fault-free and not included in the minimum cut set, then check the next bottom event. If the current bottom event is fault-free and included in the minimum cut set, then check other bottom events in the minimum cut set according to importance ranking. If a fault exists, then find out the cause of the fault. If the current bottom event has a fault cause, then find out the cause of the fault. Exclude the bottom events that have been checked, and check other bottom events in sequence until the last bottom event, to complete the fault diagnosis.

[0101] For example, maintenance personnel first diagnose and troubleshoot the bottom event E1, which ranks first in importance. If E1 is fault-free and not included in the minimum cut set, they search downwards according to the table for bottom event E2 and troubleshoot it. If E1 is fault-free and included in the minimum cut set, they check other bottom events E(i) in the cut set according to their importance. If a fault exists, they find out the cause of the fault and output the bottom event. If E1 is faulty, they find out the cause of the fault and output the bottom event. They exclude the bottom events that have been checked and continue to check according to the corrected importance ranking table until the last bottom event, thus completing the fault troubleshooting.

[0102] In one embodiment, an apparatus is also provided, including a memory and a processor, wherein the memory stores a computer program that can be loaded by the processor and executed corresponding to the aforementioned method for generating auxiliary troubleshooting strategies for communication faults in a vehicle power battery system.

[0103] In particular, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts.

[0104] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such transmitted data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0105] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0106] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0107] In another aspect, this application also provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the locomotive power battery system communication fault auxiliary troubleshooting strategy generation method described in the above embodiments.

[0108] In another aspect, this application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to implement the locomotive power battery system communication fault auxiliary troubleshooting strategy generation method described in the above embodiments.

[0109] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0110] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, touch terminal, or network device, etc.) to execute the method according to the embodiments of this application.

[0111] For those skilled in the art, the specific meanings of the above terms in this invention can be understood according to the specific circumstances; the accompanying drawings in the embodiments are used to clearly and completely describe the technical solutions in the embodiments of this invention. Obviously, the described embodiments are some embodiments of this invention, but not all embodiments. Generally, the components of the embodiments of this invention described and shown in the accompanying drawings can be arranged and designed in various different configurations.

[0112] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A method for generating a strategy to assist in troubleshooting communication faults in a locomotive power battery system, characterized in that, include: Obtain the fault repair records of the locomotive's power battery system and extract the communication fault repair records; Based on the communication fault repair records, the causes of each type of communication fault are extracted at each level, and a fault tree for communication faults in the power battery system is established. When a specific alarm communication failure exists, determine the time type of the communication failure, record the duration of the failure, and extract the fault subtree of the alarm communication failure from the established fault tree according to the fault name. Qualitative analysis is performed on the fault subtree of alarm communication failure to obtain the minimum cut set; Quantitative analysis of the fault subtree of alarm communication failure is performed. The critical importance of the bottom events is obtained by combining communication failure repair records and minimum cut sets, and the critical importance of the bottom events is sorted in descending order. The importance ranking of bottom events is revised based on the duration of the failure and the type of communication failure time, resulting in the final importance ranking table of bottom events. The faults are investigated sequentially according to the importance ranking table of the underlying events, and the root cause of the fault is finally detected.

2. The method for generating a communication fault auxiliary troubleshooting strategy for a locomotive power battery system according to claim 1, characterized in that, The step of extracting the causes of each type of communication fault from the communication fault repair records at various levels specifically includes: Based on the fault name and fault phenomenon in the communication fault repair records, communication faults are classified. For each type of communication fault, the causes of the fault at each level are determined based on the fault investigation records in the communication fault maintenance records. The primary fault that directly causes the fault is the primary cause, the next level fault that causes the primary fault is the secondary cause, and so on, until the lowest level cause of the fault is determined in the fault investigation records. The causes of each type of communication failure and each level of failure are broken down and recorded step by step to complete the extraction of failure causes.

3. The method for generating a communication fault auxiliary troubleshooting strategy for a locomotive power battery system according to claim 1 or 2, characterized in that, The establishment of a fault tree for communication faults in the power battery system specifically includes: The top event of the communication fault tree of the power battery system is determined based on the communication fault repair records; Determine the boundary conditions of the communication fault tree; By combining the various causes of the top event and the causes at each level, a fault tree for communication failures in the power battery system is established.

4. The method for generating a communication fault auxiliary troubleshooting strategy for a locomotive power battery system according to claim 3, characterized in that, The boundary conditions for determining the communication fault tree specifically include: Determine the operating status of the components related to the occurrence of the top event; The events considered unacceptable during the construction of the fault tree are identified, with low-probability events being considered unacceptable events; To determine events that are bound to happen and events that are bound to not happen under certain conditions.

5. The method for generating a communication fault auxiliary troubleshooting strategy for a locomotive power battery system according to claim 3, characterized in that, The establishment of a fault tree for communication faults in the power battery system specifically includes: The lowest-level cause of each type of communication failure is designated as the bottom event of the fault tree, while other failure causes besides the top and bottom events are designated as intermediate events. Starting from the top event, the deductive method is used to gradually decompose and expand downwards until the bottom event is reached; To determine the logical relationships between adjacent levels of the communication fault tree, within the same fault tree, events at lower levels are considered input events of higher levels, and events at higher levels are considered output events of lower levels. If an output event is guaranteed to occur when all input events occur simultaneously, an AND gate is used. If at least one input event occurs and the output event occurs more than once, an OR gate is used. If an input event is the inverse of an output event, a NOT gate is used. If at least r of n input events occur and the output event is guaranteed, a voting gate is used. If the output event is guaranteed to occur even if no input events occur simultaneously, an XOR gate is used. If an input event causes an output event only when the disable gate condition is met, a disable gate is used. If an output event occurs only when the input events occur in a specified order, a sequential AND gate is used. If an input event causes an output event only when it occurs and lasts for a certain period, a duration AND gate is used. Using logical relationship graphical symbols to connect upper and lower level events, a power battery system communication fault tree diagram is formed and output, thus completing the establishment of the power battery system communication fault tree.

6. The method for generating a communication fault auxiliary troubleshooting strategy for a locomotive power battery system according to claim 1, characterized in that, When a specific alarm communication failure exists, determining the communication failure time type and recording the failure duration specifically includes: When a specific alarm communication fault exists, the communication fault is transmitted to the locomotive microcomputer through the communication harness, and the specific fault information is displayed by the control panel display unit, including the fault occurrence time, fault name, fault code, and fault level. If a specific alarm communication fault only alarms once and then returns to normal, it is considered a flash alarm communication fault, and the fault duration is the communication cycle of the specific alarm communication fault type. If a specific alarm communication failure is reported intermittently or the failure is eliminated after a system reset, it is considered an intermittent communication failure, and the longest failure duration is taken as the failure duration. If a specific alarm communication fault continues to be reported and the fault is not eliminated after system reset, it is considered a continuous communication fault. The difference between the current time of maintenance and the time when the fault occurred is taken as the fault duration.

7. The method for generating a communication fault auxiliary troubleshooting strategy for a locomotive power battery system according to claim 1, characterized in that, The qualitative analysis of the fault subtree of the alarm communication failure to obtain the minimum cut set specifically includes: The minimum cut set of the fault tree for a specific alarm communication fault is obtained using the uplink method, and the calculation starts from the intermediate event at the lowest level. If an intermediate event is connected to a base event via a logical AND gate, then the intermediate event is represented using an AND gate structure function. If an intermediate event is connected to the underlying event via a logical OR gate, use an OR gate structure function to represent the intermediate event. If an intermediate event is connected to a base event via a NOT gate, the NOT gate structure function is used to represent the intermediate event. If an intermediate event is connected to the underlying event via a logical XOR gate, the XOR gate structure function is used to represent the intermediate event. If an intermediate event is connected to a base event via a logical conditional AND gate, the conditional AND gate is represented as an AND gate between the original base event and the conditional event, and the intermediate event is represented using an AND gate structure function. By proceeding sequentially upwards to the top event, we obtain the top event structure function representing all bottom events. We then simplify this function using Boolean algebra to obtain the structure function expression of the sum of bottom event products with the minimum number of terms. Each product of terms is a minimal cut set.

8. The method for generating a communication fault auxiliary troubleshooting strategy for a locomotive power battery system according to claim 1, characterized in that, The quantitative analysis of the fault subtree of the alarm communication fault, combined with the communication fault repair records and the minimum cut set to obtain the critical importance of the bottom event, specifically includes: By analyzing communication fault repair records, the probability of failure for low-level events can be obtained. The base events in the fault tree are independent of each other. The fault probability of all minimum cut sets is calculated, and the fault probability of the intersection of the base events is equal to the product of the fault probabilities of the base events. Based on the top event structure function, the failure probability of the top event is calculated using the failure probabilities of all minimum cut sets; For each bottom event, calculate the partial derivative of the top event structure function with respect to the bottom event. Multiply the bottom event failure probability by the partial derivative and divide by the top event failure probability to obtain the criticality of the bottom event. Repeat this process until the criticality of all bottom events has been calculated.

9. The method for generating a communication fault auxiliary troubleshooting strategy for a locomotive power battery system according to claim 1, characterized in that, The process of revising the importance ranking of bottom events based on fault duration and communication fault time type to form the final bottom event importance ranking table specifically includes: Based on the fault tree, the fault phenomena of intermediate events are used to classify the bottom events, and each bottom event corresponds to a communication fault time type. Obtain the duration and type of the alarm communication failure. If the communication failure type is a flash communication failure and the duration is less than 1 second, divide the critical importance of the underlying event corresponding to the communication failure time type by the duration of the failure, and multiply the critical importance of the other underlying events by the duration of the failure. If the communication failure time type is intermittent communication failure and the failure duration is greater than 1 second, then the critical importance of the underlying event corresponding to the communication failure time type is multiplied by the failure duration, and the critical importance of other underlying events is divided by the failure duration. If the communication failure time type is a continuous communication failure, then the critical importance of the underlying event corresponding to the communication failure time type is multiplied by the failure duration, and the critical importance of other underlying events is divided by the failure duration. Based on the revised critical importance, the bottom events are sorted in descending order of the revised critical importance to form the final bottom event importance ranking table.

10. The method for generating a communication fault auxiliary troubleshooting strategy for a locomotive power battery system according to claim 1, characterized in that, The process of troubleshooting based on the importance ranking table of the underlying events to ultimately achieve root cause detection includes: Check the bottom events in the bottom event importance ranking table in order from front to back; If the current bottom event is fault-free and not included in the minimum cut set, then check the next bottom event; if the current bottom event is fault-free and included in the minimum cut set, then check other bottom events in the minimum cut set according to importance. If a fault exists, then find out the cause of the fault; if the current bottom event has a fault cause, then find out the cause of the fault. Exclude the bottom events that have already been checked, and check the other bottom events in sequence until the last bottom event is checked to complete the troubleshooting.

Images