Pure electric vehicle controller fault processing measure calling method and system and medium

Through troubleshooting, confirmation and serial number calculation, the problem of waste of computing resources in the fault processing of electric vehicle controllers is solved, the processing efficiency and system response speed are improved, and the equipment life is extended.

CN118953027AInactive Publication Date: 2024-11-15JIANGLING MOTORS
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202411210830.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-30
Publication Date
2024-11-15
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing electric vehicle controllers require a lot of computing resources and time when troubleshooting, resulting in inefficient processing, especially when the number of faults is high.

Method used

By collecting and sorting fault types, checking and confirming the real fault item by item, calculating the fault sequence number, and determining the serial number that needs to be called based on the preset calibration, searching and executing corresponding measures from the preset table, optimizing the fault processing process, and ensuring that Critical faults are prioritized.

Benefits of technology

Significantly save computing resources, improve fault handling efficiency, reduce hardware requirements, and extend the service life of the equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118953027A_ABST
    Figure CN118953027A_ABST
Patent Text Reader

Abstract

The invention provides a pure electric vehicle controller fault processing measure calling method and system and a medium, and the method comprises the steps: sorting all faults, confirming effective faults, and calculating the serial numbers of the confirmed faults in an original array; and finally, the fault sequence number of the fault processing measure needing to be called is confirmed, the fault processing measure is called according to the fault sequence number, a new method is provided for calling the fault processing measure of the pure electric vehicle, and system computing power resources are remarkably saved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of electric vehicle control, and in particular to a method, system and medium for calling fault handling measures of a pure electric vehicle controller. Background Art

[0002] The development of new energy vehicles has become an international consensus and a national strategy. The development of new energy vehicles has driven automobiles from traditional hardware-dominated to software-dominated mobile smart terminals. The electronic and electrical architecture of the entire vehicle has undergone tremendous changes, with higher and higher integration and more and more functions for a single controller. This also means that the controller's requirements for computing power are constantly increasing. Among them, optimizing the controller's fault handling module is particularly significant in saving computing power.

[0003] At present, mainstream domain controllers often integrate multiple traditional control units, resulting in a surge in the number of faults. The number of faults in a single domain controller has also increased from dozens to hundreds or even thousands. In traditional solutions, all faults need to be identified and fault handling measures called in one operation cycle. However, handling all faults requires a lot of computing resources and time, resulting in low processing efficiency of the controller. Especially when the number of faults is large, the response speed of the system will be significantly affected. Therefore, how to efficiently call fault handling measures to save computing resources has become an urgent problem to be solved. Summary of the invention

[0004] In view of the defects in the prior art, the purpose of the present invention is to provide a method, system and medium for calling fault handling measures of a pure electric vehicle controller, which can efficiently call fault handling measures to save computing resources.

[0005] In order to achieve the above technical effects, the present invention adopts the following technical solutions:

[0006] According to a first aspect of the present invention, a method for invoking fault handling measures for a pure electric vehicle controller is provided, comprising the following specific steps:

[0007] Step S1. Collect all fault types existing in the system and sort these faults to form an original fault array;

[0008] Step S2. Check the sorted faults one by one to confirm whether the faults really exist, record all confirmed faults and mark them as valid, and form a confirmed fault list;

[0009] Step S3. In the confirmed fault list obtained in step S2, for each fault, calculate its sequence number in the original fault array;

[0010] Step S4. Determine the fault number for which the fault handling measures need to be invoked according to the preset calibration amount;

[0011] Step S5. According to the fault sequence number for which the fault handling measure needs to be called as confirmed in step S4, the corresponding handling measure is searched and executed from the preset fault handling measure calibration table.

[0012] Preferably, the fault sorting in step S1 is achieved by setting weights or priorities, thereby ensuring that the most critical faults are handled first.

[0013] Preferably, the method further includes step S6. After the fault processing is completed, the processing result is recorded in a log file and uploaded to the central management system through the vehicle communication bus for data analysis.

[0014] Preferably, in step S2, all faults are tested item by item by performing fault filtering confirmation, and the confirmed faults are set to 1, and the unconfirmed faults are set to 0.

[0015] According to a second aspect of the present invention, a pure electric vehicle controller fault processing measure invocation system is provided, which is used to implement the above-mentioned pure electric vehicle controller fault processing measure invocation method and includes the following modules:

[0016] Fault sorting module: This module is used to collect all possible fault types in the system and sort the detected faults according to preset standards to determine the processing priority;

[0017] Fault confirmation module: This module is used to check the sorted faults one by one to confirm whether the faults really exist, and extract the valid faults from the original list to form a confirmed fault list;

[0018] Fault sequence number calculation module: This module is used to calculate the sequence number of the confirmed faults in the original fault list and record the original sequence number corresponding to each confirmed fault. The calculated sequence number will be used to determine which specific fault needs to be handled first during the fault handling process;

[0019] Fault number confirmation module for invoking fault handling measures: This module is used to determine the fault number for which fault handling measures need to be invoked according to a preset calibration quantity, which limits the number of faults to be processed each time;

[0020] Fault handling measures calling module: This module is used to call the fault sequence number of the fault handling measures according to the confirmed needs, find the corresponding handling measures from the preset fault handling measures calibration table, and execute these measures.

[0021] According to a third aspect of the present invention, there is provided a computer-readable storage medium on which a computer program is stored, and the program is executed by a processor to implement the above-mentioned method for calling fault handling measures for a pure electric vehicle controller.

[0022] Compared with the prior art, the present invention has the following beneficial effects:

[0023] The method provided by the present invention optimizes the fault sorting and confirmation process, and only focuses on the actual key faults, effectively reducing unnecessary calculations and false alarm processing, and significantly saving system computing resources. Through intelligent priority management, it ensures that computing resources are concentrated on the most needed links, avoiding global scanning and repeated verification, thereby improving overall processing efficiency, reducing hardware requirements, and extending the service life of equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:

[0025] Figure 1 A flowchart of the steps of the method for calling the fault handling measures of the pure electric vehicle controller described in the first embodiment;

[0026] Figure 2 This is a schematic diagram of the system for calling the fault handling measures for the pure electric vehicle controller described in the second embodiment. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

[0028] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0029] First Embodiment

[0030] like Figure 1 As shown, this embodiment provides a method for calling fault handling measures of a pure electric vehicle controller, which specifically includes the following steps:

[0031] Step S1. Collect all possible fault types in the system and record them in a list or array. Sort these faults according to the severity, frequency or other important indicators to form the original fault array. This can be achieved by setting weights or priorities to ensure that the most critical faults are handled first.

[0032] If multiple sorting criteria are involved, a comprehensive scoring method can be used, or a multi-level sorting strategy can be used to determine the final order. This sorting process is executed in the master control program of the domain controller to ensure that the sorting results can be quickly called in subsequent steps.

[0033] Step S2. Check the sorted faults one by one to confirm whether the faults really exist. This can be done by monitoring the real-time data of the system, fault signals or other diagnostic tools. Verify each fault to determine whether it meets the preset fault conditions, such as abnormal sensor feedback, abnormal system performance, etc. Record all confirmed faults, and the confirmed faults will be marked as valid and recorded in a state array. Each element of the array corresponds to the confirmation state of a fault (1 means confirmed, 0 means unconfirmed), and extract the valid faults from the original fault array to form a confirmed fault list. The confirmation process may involve filtering, analyzing and verifying the fault data to determine which faults are real and which are false alarms or insignificant.

[0034] Step S3. For each of the confirmed fault lists obtained in step 2, calculate its serial number in the original fault array. Ensure that the serial number is calculated accurately, because these serial numbers will be used to locate specific faults and their corresponding treatment measures in subsequent steps. Record the original serial number corresponding to each confirmed fault. The calculated serial number will be used to determine which specific fault needs to be handled first during the fault handling process.

[0035] Step S4. Confirm the fault sequence number for invoking the fault handling measure; determine the fault sequence number for invoking the fault handling measure according to the preset calibration amount. The calibration amount may limit the number of faults to be handled each time, so it is necessary to select the part that needs to be handled immediately from all confirmed faults.

[0036] Step S5. Call the fault handling measures according to the fault sequence number; according to the fault sequence number that needs to call the fault handling measures confirmed in the previous step, find the corresponding handling measures from the preset fault handling measures calibration table, and execute these measures. The calling of the handling measures should be based on the mapping relationship between the sequence number and the measures determined previously, so as to ensure that each fault can be properly handled. In this step, the priority of fault handling and multi-task scheduling must also be considered to ensure that critical faults can be responded to in the first time.

[0037] Step S6. Feedback and storage of processing results: After the fault processing is completed, the processing results are recorded in a log file and uploaded to a central management system (such as a cloud platform or a remote monitoring system) through an on-board communication bus (such as a CAN bus or Ethernet) for data analysis. The software layer also needs to regularly evaluate the effectiveness of the fault handling measures and optimize the fault handling strategy for the next cycle.

[0038] Example description: Assume that a component has 400 faults as shown in Table 1 below. Each fault can call any 10 fault handling measures through calibration.

[0039] 1 2 … 399 400 Fault 1 Fault 2 … Fault 399 Fault 400

[0040] Table 1: Unconfirmed fault array

[0041]

[0042]

[0043] Table 2: Fault handling measures calibration table

[0044] The 400 faults are confirmed by fault filtering, the confirmed faults are set to 1, and the unconfirmed faults are set to 0, forming an array with a dimension of 400;

[0045] Calculate the above array and calculate the sequence number equal to 1 in the array. For example, faults 11 to 20 are confirmed, and the fault sequence number array [11, 12, 13, 14, 15, 16, 17, 18, 19, 20… 0, 0, 0] with a dimension of 400 is calculated.

[0046] Confirm the number of faults that call fault handling measures through the calibration quantity, and select the fault sequence numbers that call fault handling measures. For example, if the calibration quantity is 10, the fault sequence numbers that call fault handling measures in the above example are [11, 12, 13, 14, 15, 16, 17, 18, 19, 20];

[0047] According to the fault sequence number [11, 12, 13, 14, 15, 16, 17, 18, 19, 20] of the fault handling measure to be called, check Table 2 (Fault Handling Measure Calibration Table) above, select the fault handling measure sequence number, and then call the handling measure.

[0048] The traditional method of calling fault handling measures is to call the fault measures for all faults (including unconfirmed faults), which wastes a lot of computing power. In this solution, the confirmed faults are calculated first, and then the faults are called fault measures in batches. This means that in the calling of fault handling measures, if the total number of all faults is 400, the present invention sets the single-cycle calling of handling measures to 20 faults, and the computing power used for calling fault handling measures for one fault is n, 20n / (400n)=0.05. Considering that the present invention also needs to calculate the serial number of the confirmed fault and the delay reduction processing of the fault handling measures, it is evaluated that the computing power can be saved by nearly 80% in the calling of fault handling measures.

[0049] Second Embodiment

[0050] like Figure 2 As shown, this embodiment provides a pure electric vehicle controller fault processing measure calling system, which is used to implement the pure electric vehicle controller fault processing measure calling method described in the first embodiment, and specifically includes the following modules:

[0051] Fault sorting module: This module is used to collect all possible fault types in the system and sort the detected faults according to preset standards to form an original fault array and determine the processing priority.

[0052] Fault confirmation module: This module is used to detect the sorted faults one by one to confirm whether the faults really exist, and extract the valid faults from the original list to form a confirmed fault list.

[0053] Fault sequence number calculation module: This module is used to calculate the sequence number of the confirmed faults in the original fault array and record the original sequence number corresponding to each confirmed fault. The calculated sequence number will be used to determine which specific fault needs to be handled first during the fault handling process.

[0054] Fault number confirmation module for invoking fault handling measures: This module is used to determine the fault number for which fault handling measures need to be invoked according to the pre-set calibration quantity. The calibration quantity may limit the number of faults to be handled each time, so it is necessary to select the part that needs to be handled immediately from all confirmed faults.

[0055] Fault handling measures calling module: This module is used to call the fault sequence number of the fault handling measures according to the confirmed needs, find the corresponding handling measures from the preset fault handling measures calibration table, and execute these measures.

[0056] Embodiment 3

[0057] This embodiment provides a computer-readable storage medium on which a computer program is stored. The program is executed by a processor to implement the method for calling fault handling measures for a pure electric vehicle controller described in the first embodiment.

[0058] The above describes the specific embodiments of the present invention. Based on the above description, relevant personnel can make various changes and modifications without departing from the technical concept of the present invention.

Claims

1. A method for calling fault handling measures for a pure electric vehicle controller, characterized in that: The specific steps include: Step S1. Collect all fault types existing in the system and sort these faults to form an original fault array; Step S2. Check the sorted faults one by one to confirm whether the faults really exist, record all confirmed faults and mark them as valid, and form a confirmed fault list; Step S3. In the confirmed fault list obtained in step S2, for each fault, calculate its sequence number in the original fault array; Step S4. Determine the fault number for which the fault handling measures need to be invoked according to the preset calibration amount; Step S5. According to the fault sequence number for which the fault handling measure needs to be called as confirmed in step S4, the corresponding handling measure is searched and executed from the preset fault handling measure calibration table.

2. The method for calling fault handling measures for a pure electric vehicle controller according to claim 1, characterized in that: The fault sorting in step S1 is achieved by setting weights or priorities, thereby ensuring that the most critical faults are handled first.

3. The method for calling fault handling measures for a pure electric vehicle controller according to claim 1, characterized in that: The method also includes step S6. After the fault processing is completed, the processing result is recorded in a log file and uploaded to the central management system through the vehicle communication bus for data analysis.

4. The method for calling fault handling measures for a pure electric vehicle controller according to claim 1, characterized in that: In step S2, all faults are tested item by item by performing fault filtering confirmation, and the confirmed faults are set to 1, and the unconfirmed faults are set to 0.

5. A pure electric vehicle controller fault processing measure calling system, used to implement the pure electric vehicle controller fault processing measure calling method according to any one of claims 1 to 4, characterized in that: Includes the following modules: Fault sorting module: This module is used to collect all possible fault types in the system and sort the detected faults according to preset standards to determine the processing priority; Fault confirmation module: This module is used to check the sorted faults one by one to confirm whether the faults really exist, and extract the valid faults from the original list to form a confirmed fault list; Fault sequence number calculation module: This module is used to calculate the sequence number of the confirmed faults in the original fault list and record the original sequence number corresponding to each confirmed fault. The calculated sequence number will be used to determine which specific fault needs to be handled first during the fault handling process; Fault number confirmation module for invoking fault handling measures: This module is used to determine the fault number for which fault handling measures need to be invoked according to a preset calibration quantity, which limits the number of faults to be processed each time; Fault handling measures calling module: This module is used to call the fault sequence number of the fault handling measures according to the confirmed needs, find the corresponding handling measures from the preset fault handling measures calibration table, and execute these measures.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the method for calling fault handling measures for a pure electric vehicle controller as described in any one of claims 1 to 4.

Citation Information

Patent Citations

  • Fault handling method and system of blade electric vehicle (BEV) and BEV

    CN107020957A

  • Automobile fault diagnosis method, automobile fault diagnosis apparatus, and electronic equipment

    CN107918382A

  • Fault processing method and device based on battery management system of pure electric vehicle

    CN113386570A

  • Automobile fault maintenance priority ranking method and system and storage medium

    CN114266367A

  • New energy vehicle fault management method and system

    CN116373606A