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

Abstract

The invention provides a locomotive power battery system communication fault auxiliary troubleshooting strategy generation method. The method comprises the following steps: acquiring a communication fault maintenance record of a locomotive power battery system; performing fault cause extraction on each level of each type of communication faults, and establishing a fault tree; when a specific alarm communication fault exists, judging the time type and duration of the communication fault, and intercepting a fault subtree of the alarm communication fault; performing qualitative analysis on the fault sub-tree to obtain a minimum cut set; carrying out quantitative analysis on the fault sub-tree, obtaining the key importance of the bottom event, and carrying out descending sorting; correcting the sequence of the importance degrees of the bottom events to form a sequence table of the importance degrees of the bottom events; troubleshooting is carried out in sequence according to the bottom event importance ranking table. According to the invention, a fault auxiliary troubleshooting strategy of the communication fault can be accurately provided, the efficiency and accuracy of troubleshooting of the communication fault by a maintainer are improved, corresponding maintenance measures are convenient to take, the utilization rate of a new energy locomotive is improved, and the labor cost is reduced.

Description

Technical Field

[0001] The present invention relates to the field of rail transit operation and maintenance, and in particular to a method for generating a communication fault auxiliary troubleshooting strategy for a locomotive power battery system. Background Art

[0002] Under the background of energy conservation and environmental protection, the promotion of new energy locomotives has been greatly accelerated. Pure electric locomotives and hybrid locomotives with power batteries as power sources are used to replace old internal combustion locomotives. Electronic and electrical technologies are widely used in power battery systems. The communication within and between systems is much more frequent than that of traditional internal combustion locomotives. The frequency of communication fault alarms is high, which can easily affect the working state of the power battery system and the accuracy of data. However, the existing diagnosis of communication faults is usually based on the results of abnormal message check codes or interruption of life signals. At the same time, the data problems caused by communication faults make it impossible to automatically locate the cause of the fault based on data, and can only be manually checked, which is time-consuming and labor-intensive. The relevant technology only diagnoses high-voltage power-on and insulation faults of electric vehicles, and cannot troubleshoot complex communication faults in the power battery system of new energy locomotives. Therefore, there is an urgent need for a method for generating a communication fault auxiliary troubleshooting strategy for the power battery system of new energy locomotives to assist maintenance personnel in troubleshooting communication faults and improve the efficiency of fault root cause location and locomotive utilization rate. Summary of the invention

[0003] In view of the problems existing in the prior art, a method for generating an auxiliary troubleshooting strategy for a locomotive power battery system communication fault is provided. The method is mainly aimed at the complex communication faults of the power battery system of a new energy locomotive. It can assist maintenance personnel in troubleshooting communication faults and improve the efficiency of locating the root cause of faults and the utilization rate of the locomotive.

[0004] The technical solution adopted by the present invention is as follows: A method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy, comprising:

[0005] Obtain the fault maintenance records of the locomotive power battery system and separate the communication fault maintenance records;

[0006] Extract the fault causes at all levels for each type of communication fault based on the communication fault maintenance records, and establish a fault tree for the power battery system communication fault;

[0007] When there is a specific alarm communication fault, determine the communication fault time type, record the fault duration, and intercept the fault subtree of the alarm communication fault from the established fault tree according to the fault name;

[0008] Conduct qualitative analysis on the fault subtree of alarm communication fault to obtain the minimum cut set;

[0009] Quantitatively analyze the fault subtree of alarm communication faults, combine the communication fault maintenance records with the minimum cut set to obtain the key importance of the bottom events, and sort the key importance of the bottom events in descending order;

[0010] The bottom event importance ranking is modified based on the fault duration and communication fault time type to form a final bottom event importance ranking table;

[0011] According to the bottom event importance ranking table, troubleshooting is carried out in sequence to ultimately achieve fault root cause detection.

[0012] As a preferred solution, extracting the fault causes at various levels for each type of communication fault according to the communication fault repair record specifically includes:

[0013] Classify communication faults based on the fault names and fault phenomena recorded in the communication fault repair records;

[0014] For each type of communication fault, determine the various levels of causes of the fault based on the troubleshooting record of the communication fault repair record. The primary fault that directly causes the fault is the primary cause, and the next level of fault that causes the primary fault is the secondary cause, and so on, until the lowest level of cause that causes the fault is determined in the troubleshooting record;

[0015] Expand and record each type of communication failure and the causes of each level of failure step by step to complete the extraction of the cause of the failure.

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

[0017] Determine the top event of the power battery system communication fault tree based on the communication fault maintenance record; wherein the top event is the communication fault;

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

[0019] Based on the various causes and causes of the top events, a fault tree of power battery system communication failure is established.

[0020] As a preferred solution, the boundary conditions of determining the communication fault tree specifically include:

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

[0022] Determine the events that are considered unacceptable during the process of establishing the fault tree, among which low-probability events are considered unacceptable events;

[0023] Determine the events that will definitely occur and the events that will definitely not occur under certain conditions.

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

[0025] The lowest level cause of each type of communication fault is taken as the bottom event of the fault tree, and other fault causes other than the top event and the bottom event are taken as the intermediate events;

[0026] Start from the top event, use deduction method, and gradually deduce and decompose downward until you reach the bottom event;

[0027] Determine the logical relationship between adjacent levels of the communication fault tree. In the same fault tree, the events of the next level are regarded as the input events of the previous level, and the events of the previous level are regarded as the output events of the next level. When the input events occur at the same time, the output event must occur, so use the logic "AND gate"; when at least one of the input events occurs, the output event must occur, so use the "OR gate"; when the input event is the inverse event of the output event, use the "NOT gate"; when at least r of n input events occur, the output event must occur, so use the "Voting gate"; when the input events do not occur at the same time, the output event must occur, so use the "XOR gate"; when the input event causes the output event to occur only when the forbidden gate opening condition occurs, use the "forbidden gate"; when the output event occurs only when the input event occurs according to the specified sequence conditions, use the "sequential AND gate"; when the input event causes the output event to occur only when it occurs and lasts for a period of time, use the "duration AND gate";

[0028] Use graphic symbols of logical relationships to connect upper and lower level events, form and output a power battery system communication fault tree diagram, and complete the establishment of the power battery system communication fault tree.

[0029] As a preferred solution, when there is a specific alarm communication fault, determining the communication fault time type and recording the fault duration specifically includes:

[0030] When there is a specific alarm communication fault, the communication fault is transmitted to the locomotive microcomputer through the communication harness, and the console display unit displays the specific fault information, 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 communication fault, and the fault duration is the communication cycle of the specific alarm communication fault type;

[0032] If a specific alarm communication fault is reported intermittently or the fault is eliminated after the system is reset, it is regarded as an intermittent communication fault, and the longest fault duration is taken as the fault duration of the fault;

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

[0034] As a preferred solution, the fault subtree of the alarm communication fault is qualitatively analyzed to obtain the minimum cut set, which specifically includes:

[0035] Use the ascending method to obtain the minimum cut set of the fault tree of the specific alarm communication fault, starting from the intermediate event at the lowest level;

[0036] If the intermediate event is connected to the bottom event by a logic AND gate, use the AND gate structure function to represent the intermediate event;

[0037] If the intermediate event is connected to the bottom event by a logical OR gate, use the OR gate structure function to represent the intermediate event;

[0038] If the intermediate event is connected to the bottom event by a logical NOT gate, use the NOT gate structure function to represent the intermediate event;

[0039] If the intermediate event is connected to the bottom event by a logical XOR gate, use the XOR gate structure function to represent the intermediate event;

[0040] If the intermediate event is connected to the bottom event by a logical conditional AND gate, the conditional AND gate is represented as an AND gate of the original bottom event and the conditional event, and the intermediate event is represented by an AND gate structure function;

[0041] Go up to the top event in sequence and obtain the top event structure function represented by all bottom events. Use Boolean algebra to simplify and obtain the structure function expression of the sum of the bottom event products with the minimum number of terms. Each product is a minimum cut set.

[0042] As a preferred solution, the fault subtree of the alarm communication fault is quantitatively analyzed, and the key importance of the bottom event is obtained by combining the communication fault repair record and the minimum cut set, which specifically includes:

[0043] Obtain the failure probability of the bottom event through communication fault maintenance records;

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

[0045] Based on the top event structure function, the top event failure probability 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 result, and then divide it by the top event failure probability to obtain the critical importance of the bottom event, until the critical importance of all bottom events is calculated.

[0047] As a preferred solution, the bottom event importance ranking is modified based on the fault duration and the communication fault time type to form a final bottom event importance ranking table, which specifically includes:

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

[0049] Get the fault duration and communication fault time type of the alarm communication fault. If the communication fault time type is a flash communication fault and the fault duration is less than 1 second, the critical importance of the bottom event corresponding to the communication fault time type is divided by the fault duration, and the critical importance of the remaining bottom events is multiplied by the fault duration.

[0050] If the communication fault time type is intermittent communication fault, and the fault duration is greater than 1 second, the critical importance of the bottom event corresponding to the communication fault time type is multiplied by the fault duration, and the critical importance of the remaining bottom events is divided by the fault duration;

[0051] If the communication fault time type is a continuous communication fault, the critical importance of the bottom event corresponding to the communication fault time type is multiplied by the fault duration, and the critical importance of the remaining bottom events is divided by the fault duration;

[0052] Based on the corrected key importance, the bottom events are sorted in descending order according to the corrected key importance to form a final bottom event importance ranking table.

[0053] As a preferred solution, the troubleshooting is performed in sequence according to the bottom event importance ranking table, and finally the root cause detection of the fault is realized, which specifically includes:

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

[0055] If the current bottom event has no fault and is not included in the minimum cut set, check the next bottom event; if the current bottom event has no fault and is included in the minimum cut set, check other bottom events in the minimum cut set in order of importance, and if there is a fault, find out the cause of the fault; if the current bottom event has a fault cause, find out the cause of the fault;

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

[0057] Compared with the prior art, the beneficial effects of adopting the above technical scheme are as follows: the present invention provides accurate auxiliary fault troubleshooting strategies for communication faults by qualitatively and quantitatively analyzing the fault tree of communication faults in power battery systems of new energy locomotives, combining the duration and time type of communication faults, thereby improving the efficiency and accuracy of communication fault troubleshooting by maintenance personnel, facilitating the adoption of corresponding maintenance measures, improving the utilization rate of new energy locomotives, and reducing lost work costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 This is a flow chart of the method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy proposed by the present invention.

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

[0060] Figure 3 This is a troubleshooting flowchart based on the importance ranking table proposed in an embodiment of the present invention. DETAILED DESCRIPTION

[0061] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar modules or modules with the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be construed as limitations on the present application. On the contrary, the embodiments of the present application include all changes, modifications and equivalents that fall within the spirit and connotation of the appended claims.

[0062] Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work are within the scope of protection of this application. In the absence of conflict, the embodiments in this application and the features in the embodiments can be combined with each other arbitrarily. In addition, although the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in an order different from that here.

[0063] In order to assist maintenance personnel in troubleshooting communication faults, improve the efficiency of fault root cause location and locomotive utilization rate, the embodiment of the present invention proposes a method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy, which is mainly used in new energy locomotives. The specific scheme is as follows:

[0064] Step 1: Obtain the fault maintenance record of the locomotive power battery system and separate the communication fault maintenance record.

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

[0066] Communication failure is used to describe communication failures within or between different subsystems of the power battery system, which refers to data distortion or communication interruption. The communication failure subclasses can be determined based on the communication topology of the power battery system, such as Figure 2 As shown, including:

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

[0068] In practical applications, the new energy locomotive model, vehicle number and its fault inspection and repair records can be obtained. In the new energy locomotive fault inspection and repair records, the power battery cell, power battery branch, BMS, communication, fire protection system, thermal protection system, fuse, contactor and other fault inspection and repair records related to the power battery system are marked. bat ;Power battery system fault inspection and repair record based on marking R bat , split the communication fault repair record R bat-com .

[0069] Step 2: Extract the fault causes at all levels for each type of communication fault based on the communication fault maintenance record, and establish a fault tree for the power battery system communication fault.

[0070] After obtaining the communication fault repair record, the communication fault is classified according to the fault name and fault phenomenon. bat-com The fault names in R are taken as top-level faults. bat-comThe fault troubleshooting records in the system search for fault causes step by step downwards as the fault causes at each level until the root cause of the fault. Specifically, for each type of communication fault, the fault causes at each level are determined based on the fault troubleshooting records of the communication fault repair records. The primary fault that directly causes the fault is the primary cause, and 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 troubleshooting records; each type of communication fault and the fault causes at each level are expanded and recorded step by step to complete the extraction of fault causes.

[0071] Furthermore, after extracting the causes of each level of each type of communication fault, a fault tree of the power battery system communication fault 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 maintenance record. 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 a fault event that is not expected to occur in the system, not a certain type of communication fault. The top event of the fault subtree is generally a certain type of alarm communication fault name.

[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 not to be allowed to occur during the process of establishing the fault tree, regard low-probability events as not to be allowed events, and determine the events that are bound to occur and the events that are bound to not occur under certain conditions.

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

[0076] In the process of establishing the process tree, the lowest level cause among all levels of fault causes is taken as the bottom event of the fault tree, and other fault causes other than the top event and the bottom event are taken as intermediate events; starting from the top event, the deductive method is used to gradually deduce and decompose downward until the bottom event.

[0077] Determine the logical relationship between adjacent levels of the communication fault tree. In the same fault tree, the events of the next level can be regarded as the input events of the previous level, and the events of the previous level can be regarded as the output events of the next level. When the input events occur at the same time, the output event must occur, so the logic "AND gate" is used; when at least one of the input events occurs, the output event must occur, so the "OR gate" is used; when the input event is the inverse event of the output event, the "NOT gate" is used; when at least r of n input events occur, the output event must occur, so the "Voting gate" is used; when the input events do not occur at the same time, the output event must occur, so the "XOR gate" is used; when the input event only causes the output event to occur when the forbidden door opening condition occurs, the "forbidden door" is used; when the output event only occurs when the input event occurs according to the specified sequence conditions, the "sequential AND gate" is used; when the input event only causes the output event to occur when it occurs and lasts for a period of time, the "duration AND gate" is used; use the graphic symbols of the logical relationship to connect the upper and lower level events, form and output the inverted tree diagram of the power battery system communication fault tree, and complete the establishment of the power battery system communication fault tree. It should be noted that when connecting upper and lower level events, direct connection between gates is not allowed.

[0078] In one embodiment, when extracting the fault causes at each level for each type of communication fault, the communication fault troubleshooting record R bat-com In the fault phenomenon, confirm whether the fault is a flash communication fault, an intermittent communication fault, or a continuous communication fault. At the same time, confirm whether the fault is eliminated after the system is reset and restarted. Then, the fault time type F corresponding to the fault cause can be determined. type .

[0079] Step 3: When a specific alarm communication fault exists, determine the communication fault time type, record the fault duration, 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 means that the battery management system of the power battery system detects a certain communication fault sub-category, triggers an alarm and displays it on the display screen of the driver's cab console. The maintenance personnel or on-board mechanic can view the fault alarm status in real time on the display screen, or confirm the communication fault time type F of the alarm communication fault by viewing the fault history. type and fault duration.

[0081] Specifically, when there is a specific alarm communication fault, the communication fault is transmitted to the locomotive microcomputer through the communication harness, and the specific fault information is displayed on the console display unit, including the fault occurrence time, fault name, fault code, and fault level. At this time, if the specific alarm communication fault only alarms once and then returns to normal, it is considered a flash 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 eliminated after the system is reset, it is considered an intermittent communication fault, and the longest fault duration is taken as the fault duration of the fault; if the specific alarm communication fault is continuously reported and the fault is not eliminated after the system is 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 of the fault.

[0082] At the same time, the fault subtree FT of the alarm communication fault can be intercepted downward from the established fault tree according to the fault name of the existing alarm communication fault (i.e., the top event of the fault subtree). sub , then according to the fault subtree FT sub In practical applications, the alarm communication fault can be used as an intermediate event to match the communication fault tree FT, and the event can be intercepted downward until the bottom event.

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

[0084] The minimum cut set MSC(i) refers to a set of some bottom events in the fault tree. When these bottom events occur at the same time, the top event must occur. In this embodiment, the minimum cut set of the fault tree of the specific alarm communication fault is obtained by the upward method, and the calculation is started from the intermediate event of the lowest level; if the intermediate event is connected to the bottom event by a logical AND gate, the intermediate event is represented by an AND gate structure function; if the intermediate event is connected to the bottom event by a logical OR gate, the intermediate event is represented by an OR gate structure function; if the intermediate event is connected to the bottom event by a logical NOT gate, the intermediate event is represented by a NOT gate structure function; if the intermediate event is connected to the bottom event by a logical XOR gate, the intermediate event is represented by an XOR gate structure function; if the intermediate event is connected to the bottom event by a logical conditional AND gate, the conditional AND gate is represented as an AND gate of the original bottom event and the conditional event, and the intermediate event is represented by an AND gate structure function; go up to the top event in sequence, obtain the top event structure function represented by all bottom events, and simplify it by Boolean algebra to obtain the structure function expression of the sum of the bottom event products with the minimum number of terms, and each product is a minimum cut set.

[0085] Step 5: Quantitatively analyze the fault subtree of the alarm communication fault, obtain the key importance of the bottom event by combining the communication fault maintenance record and the minimum cut set, and sort the key importance of the bottom event in descending order.

[0086] In this embodiment, a specific calculation process of the critical importance of the bottom event is provided:

[0087] Step 5.1: Troubleshooting and recording R through communication faults bat-com , obtain the failure probability of the bottom event;

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

[0089] Step 5.3, based on the top event structure function, the top event failure probability is calculated 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 result, and then divide it by the top event failure probability to obtain the critical importance of the bottom event, until the critical importance of all bottom events is calculated.

[0091] Key Importance I cr (i) refers to the ratio of the rate of change of system failure probability to the rate of change of unit failure probability. 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 The probability importance I pr (i), finally calculate the bottom event E i In one embodiment, the key importance calculation formula is:

[0092]

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

[0094] Step 6: Based on the fault duration and the communication fault time type, the bottom event importance ranking is modified to form a final bottom event importance ranking table.

[0095] In this embodiment, the bottom events are classified based on the fault tree using the fault phenomenon of the intermediate events, and each bottom 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 ,

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

[0097] If the communication failure time type F type If it is an intermittent communication fault and the fault duration DeltaT is greater than 1 second, the communication fault time type F type The critical importance of the corresponding bottom event is multiplied by the fault duration DeltaT, and the critical importance of the remaining bottom events is divided by the fault duration;

[0098] If the communication failure time type F type If the communication failure is continuous, the communication failure time type F type The critical importance of the corresponding bottom event is multiplied by the fault duration DeltaT, and the critical importance of the remaining bottom events is divided by the fault duration DeltaT;

[0099] Based on the corrected key importance, the bottom events are sorted in descending order according to the corrected key importance to form the final bottom event importance ranking table T cr-rank .

[0100] Step 7: troubleshoot the faults in order according to the bottom event importance ranking table, and finally detect the root cause of the fault.

[0101] 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 has no fault and is not included in the minimum cut set, check the next bottom event; if the current bottom event has no fault and is included in the minimum cut set, check other bottom events in the minimum cut set according to the importance ranking, if there is a fault, find out the cause of the fault; if the current bottom event has a fault cause, find out the cause of the fault; exclude the bottom events that have been checked, check other bottom events sequentially until the last bottom event, and complete the fault troubleshooting.

[0102] For example, the maintenance personnel first diagnose and troubleshoot the bottom event E1 ranked first in importance. If E1 has no fault and E1 is not included in the minimum cut set, the bottom event E2 is searched downward in the table order for troubleshooting; if E1 has no fault and is included in the minimum cut set, other bottom events E(i) in the cut set are checked in order of importance. If there is a fault, the cause of the fault is found out and the bottom event is output; if E1 has a fault, the cause of the fault is found out and the bottom event is output; exclude the bottom events that have been checked, continue to check according to the modified importance ranking table until the last bottom event, and finally complete the fault troubleshooting.

[0103] In one embodiment, a device is also provided, including a memory and a processor, wherein the memory stores a computer program corresponding to the aforementioned method for generating a communication fault auxiliary troubleshooting strategy for a locomotive power battery system that can be loaded and executed by the processor.

[0104] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer readable medium, and the computer program includes a program code for executing the method shown in the flowchart.

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

[0106] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0107] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0108] As another aspect, the present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the method for generating a strategy for auxiliary troubleshooting of communication faults of a locomotive power battery system described in the above embodiment.

[0109] As another aspect, the present application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by an electronic device, the electronic device implements the method for generating a strategy for auxiliary troubleshooting of communication faults of a locomotive power battery system described in the above embodiment.

[0110] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0111] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0112] For those skilled in the art, the specific meanings of the above terms in the present invention can be understood in specific situations; the drawings in the embodiments are used to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings herein can be arranged and designed in various different configurations.

[0113] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy, characterized in that: include: Obtain the fault maintenance records of the locomotive power battery system and separate the communication fault maintenance records; Extract the fault causes at all levels for each type of communication fault based on the communication fault maintenance records, and establish a fault tree for the power battery system communication fault; When there is a specific alarm communication fault, determine the communication fault time type, record the fault duration, and intercept the fault subtree of the alarm communication fault from the established fault tree according to the fault name; Conduct qualitative analysis on the fault subtree of alarm communication fault to obtain the minimum cut set; Quantitatively analyze the fault subtree of alarm communication faults, combine the communication fault maintenance records with the minimum cut set to obtain the key importance of the bottom events, and sort the key importance of the bottom events in descending order; The bottom event importance ranking is modified based on the fault duration and communication fault time type to form a final bottom event importance ranking table; According to the bottom event importance ranking table, troubleshooting is carried out in sequence to ultimately achieve fault root cause detection.

2. The method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy according to claim 1, characterized in that: The extracting of fault causes at various levels for each type of communication fault according to the communication fault repair record specifically includes: Classify communication faults based on the fault names and fault phenomena recorded in the communication fault repair records; For each type of communication fault, determine the various levels of causes of the fault based on the troubleshooting record of the communication fault repair record. The primary fault that directly causes the fault is the primary cause, and the next level of fault that causes the primary fault is the secondary cause, and so on, until the lowest level of cause that causes the fault is determined in the troubleshooting record; Expand and record each type of communication failure and the causes of each level of failure step by step to complete the extraction of the cause of the failure.

3. The method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy according to claim 1 or 2, characterized in that: The establishment of a fault tree for power battery system communication failure specifically includes: Determine the top event of the power battery system communication fault tree based on the communication fault maintenance record; Determine the boundary conditions of the communication fault tree; Based on the various causes and causes of the top events, a fault tree of power battery system communication failure is established.

4. The method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy according to claim 3, characterized in that: The boundary conditions of determining the communication fault tree specifically include: 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 establishing the fault tree, among which low-probability events are considered unacceptable events; Determine the events that will definitely occur and the events that will definitely not occur under certain conditions.

5. The method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy according to claim 3, characterized in that: The establishment of a fault tree for power battery system communication failure specifically includes: The lowest level cause of each type of communication fault is taken as the bottom event of the fault tree, and other fault causes other than the top event and the bottom event are taken as the intermediate events; Start from the top event, use deduction method, and gradually deduce and decompose downward until you reach the bottom event; Determine the logical relationship between adjacent levels of the communication fault tree. In the same fault tree, the events of the next level are regarded as the input events of the previous level, and the events of the previous level are regarded as the output events of the next level. When the input events occur at the same time, the output event must occur, so use the logic "AND gate"; when at least one of the input events occurs, the output event must occur, so use the "OR gate"; when the input event is the inverse event of the output event, use the "NOT gate"; when at least r of n input events occur, the output event must occur, so use the "Voting gate"; when the input events do not occur at the same time, the output event must occur, so use the "XOR gate"; when the input event causes the output event to occur only when the forbidden gate opening condition occurs, use the "forbidden gate"; when the output event occurs only when the input event occurs in the specified sequence conditions, use the "sequential AND gate"; when the input event causes the output event to occur only when it occurs and lasts for a period of time, use the "duration AND gate"; Use graphic symbols of logical relationships to connect upper and lower level events, form and output a power battery system communication fault tree diagram, and complete the establishment of the power battery system communication fault tree.

6. The method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy according to claim 1, characterized in that: When there is a specific alarm communication fault, determining the communication fault time type and recording the fault duration specifically includes: When there is a specific alarm communication fault, the communication fault is transmitted to the locomotive microcomputer through the communication harness, and the console display unit displays the specific fault information, 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 communication fault, and the fault duration is the communication cycle of the specific alarm communication fault type; If a specific alarm communication fault is reported intermittently or the fault is eliminated after the system is reset, it is regarded as an intermittent communication fault, and the longest fault duration is taken as the fault duration of the fault; If a specific alarm communication fault continues to be reported and the fault is not eliminated after the system is reset, it is regarded as a continuous communication fault, and the difference between the current maintenance time and the fault occurrence time is taken as the fault duration of the fault.

7. The method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy according to claim 1, characterized in that: The qualitative analysis of the fault subtree of the alarm communication fault to obtain the minimum cut set specifically includes: Use the ascending method to obtain the minimum cut set of the fault tree of the specific alarm communication fault, starting from the intermediate event at the lowest level; If the intermediate event is connected to the bottom event by a logic AND gate, use the AND gate structure function to represent the intermediate event; If the intermediate event is connected to the bottom event by a logical OR gate, use the OR gate structure function to represent the intermediate event; If the intermediate event is connected to the bottom event by a logical NOT gate, use the NOT gate structure function to represent the intermediate event; If the intermediate event is connected to the bottom event by a logical XOR gate, use the XOR gate structure function to represent the intermediate event; If the intermediate event is connected to the bottom event by a logical conditional AND gate, the conditional AND gate is represented as an AND gate of the original bottom event and the conditional event, and the intermediate event is represented by an AND gate structure function; Go up to the top event in sequence and obtain the top event structure function represented by all bottom events. Use Boolean algebra to simplify and obtain the structure function expression of the sum of the bottom event products with the minimum number of terms. Each product is a minimum cut set.

8. The method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy according to claim 1, characterized in that: The quantitative analysis of the fault subtree of the alarm communication fault, combining the communication fault repair record with the minimum cut set to obtain the key importance of the bottom event, specifically includes: Obtain the failure probability of the bottom event through communication fault maintenance records; The bottom events in the fault tree are independent of each other. The failure probability of all minimum cut sets is calculated. The failure probability of the intersection of the bottom events is equal to the product of the failure probabilities of the bottom events. Based on the top event structure function, the top event failure probability 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 result, and then divide it by the top event failure probability to obtain the critical importance of the bottom event, until the critical importance of all bottom events is calculated.

9. The method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy according to claim 1, characterized in that: The bottom event importance ranking is modified based on the fault duration and the communication fault time type to form a final bottom event importance ranking table, which specifically includes: Based on the fault tree, the bottom events are classified using the fault phenomena of the intermediate events, and each bottom event corresponds to a communication fault time type; Get the fault duration and communication fault time type of the alarm communication fault. If the communication fault time type is a flash communication fault and the fault duration is less than 1 second, the critical importance of the bottom event corresponding to the communication fault time type is divided by the fault duration, and the critical importance of the remaining bottom events is multiplied by the fault duration. If the communication fault time type is intermittent communication fault, and the fault duration is greater than 1 second, the critical importance of the bottom event corresponding to the communication fault time type is multiplied by the fault duration, and the critical importance of the remaining bottom events is divided by the fault duration; If the communication fault time type is a continuous communication fault, the critical importance of the bottom event corresponding to the communication fault time type is multiplied by the fault duration, and the critical importance of the remaining bottom events is divided by the fault duration; Based on the corrected key importance, the bottom events are sorted in descending order according to the corrected key importance to form a final bottom event importance ranking table.

10. The method for generating a locomotive power battery system communication fault auxiliary troubleshooting strategy according to claim 1, characterized in that: The troubleshooting is performed in sequence according to the bottom event importance ranking table, and finally the root cause of the fault is detected, which specifically includes: Check the bottom events in the bottom event importance ranking table from front to back in order; If the current bottom event has no fault and is not included in the minimum cut set, check the next bottom event; if the current bottom event has no fault and is included in the minimum cut set, check other bottom events in the minimum cut set in order of importance, and if there is a fault, find out the cause of the fault; if the current bottom event has a fault cause, 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 troubleshooting.

Images