Vehicle fault diagnosis method and device, controller and vehicle

Abstract

The invention provides a vehicle fault diagnosis method and device, a controller and a vehicle, and the method comprises the steps: loading a preset fault table into a data processing environment, the fault table comprising a fault identifier, a fault confirmation condition, fault confirmation time and fault detailed information of each fault; obtaining a fault identifier and a fault setting identifier of the subsystem controller; determining a target fault confirmation condition and target fault confirmation time from a fault table according to the fault identifier; if the vehicle meets the target fault determination condition and the duration of the fault setting identifier is greater than the target fault determination time, determining that the vehicle has a fault; and determining and outputting target fault detailed information from the fault table. The fault information is concentrated in the fault table instead of being directly subjected to hard coding in the control algorithm, so that the modeling workload and the code quantity of the whole vehicle controller in fault signal processing are reduced, the fault adding and updating work is simplified, and the control algorithm or codes do not need to be modified every time.

Description

Technical Field

[0001] The present application relates to the field of vehicles, and in particular to a vehicle fault diagnosis method, device, controller and vehicle. Background Art

[0002] In new energy vehicles, the fault diagnosis system is a key part to ensure the reliability and safety of the vehicle controller. New energy vehicles use multiple subsystems such as complex battery management systems, motor control systems, and energy management systems. The stability of these systems directly affects the vehicle's operating performance and safety. The fault diagnosis system can detect potential faults in a timely manner and take corresponding countermeasures by real-time monitoring and analyzing the working status of each component of the vehicle, thereby avoiding major faults and safety hazards.

[0003] The current fault diagnosis system for new energy vehicles still has some problems in achieving efficient processing and maintenance. At present, the common solution is to design an algorithm model for each fault based on the fault data table, and each fault corresponds to an algorithm model. This modeling workload is large, and once the fault mode changes or a new fault occurs, a large amount of code needs to be modified and adjusted, which greatly increases the maintenance workload.

[0004] Therefore, it is particularly important to design a fault diagnosis solution to reduce the workload of code adjustment when adding or maintaining faults. Summary of the invention

[0005] The present application provides a vehicle fault diagnosis method, device, controller and vehicle, which are used to synchronize the fault table with the algorithm model, thereby reducing the workload of code adjustment when adding or maintaining faults.

[0006] In a first aspect, the present application provides a vehicle fault diagnosis method, the method comprising:

[0007] Loading a preset fault table into a data processing environment; wherein the fault table includes a fault identification, a fault confirmation condition, a fault confirmation time and fault detailed information of each fault;

[0008] Obtaining the fault flag and fault setting flag of the subsystem controller;

[0009] Determine a target fault confirmation condition and a target fault confirmation time from the fault table according to the fault identifier;

[0010] If the vehicle meets the target fault determination condition and the duration of the fault setting flag is greater than the target fault confirmation time, it is confirmed that the vehicle has a fault;

[0011] Determining target fault detailed information from the fault table according to the fault identifier, the target fault detailed information including fault location, fault type, fault light status and fault activation status;

[0012] The target fault information is output.

[0013] Optionally, the fault table also includes fault degradation measures corresponding to each fault, and the method further includes:

[0014] determining a fault degradation measure from the fault table according to the fault identifier;

[0015] The fault degradation measures are executed.

[0016] Optionally, the fault degradation measure includes a fault level, and the method further includes:

[0017] Obtaining a single fault level of the subsystem controller;

[0018] Taking the maximum value of the fault level and the single fault level as the target fault level;

[0019] The target failure level is output.

[0020] Optionally, the outputting the target fault information includes:

[0021] If the fault activation state indicates that a fault is activated, or the fault setting flag indicates that a fault is triggered, the output of the target fault information will be triggered.

[0022] Optionally, the fault table also includes the fault recovery time of each fault, and the method further includes:

[0023] Determine a target fault recovery time according to the fault identifier;

[0024] Correspondingly, if the vehicle meets the target fault determination condition and the duration of the fault setting flag is greater than the target fault confirmation time, then confirming that the vehicle has a fault includes:

[0025] If the vehicle meets the target fault determination condition and the duration of the fault setting mark is greater than the target fault confirmation time, determining whether the fault setting mark is restored to a non-fault state within the target fault recovery time;

[0026] If the fault setting flag does not return to a non-fault state, it is confirmed that the vehicle has a fault.

[0027] Optionally, the fault confirmation condition in the fault table is a fault confirmation condition mask, the fault confirmation time is a fault confirmation time mask, the fault recovery time is a fault recovery time mask, and the fault detailed information includes a fault type SPN mask and a fault mode and location FMI mask.

[0028] Optionally, the method further includes:

[0029] Acquire a new fault table, wherein the new fault table includes a new fault identifier, a new fault confirmation condition, a new fault confirmation time, and new fault detailed information;

[0030] The new fault table is loaded into the data processing environment to replace the fault table.

[0031] In a second aspect, the present application provides a vehicle fault diagnosis device, the device comprising:

[0032] A loading module, used to load a preset fault table into the data processing environment; wherein the fault table includes a fault identification, a fault confirmation condition, a fault confirmation time and fault detailed information of each fault;

[0033] A fault input module is used to obtain a fault flag and a fault setting flag of a subsystem controller;

[0034] A fault confirmation condition module, used to determine a target fault confirmation condition and a target fault confirmation time from the fault table according to the fault identifier;

[0035] A fault confirmation module, configured to confirm that a fault occurs in the vehicle if the vehicle meets the target fault determination condition and the duration of the fault setting flag is greater than the target fault confirmation time;

[0036] A fault polling module, used to determine target fault detailed information from the fault table according to the fault identifier, the target fault detailed information including fault location, fault type, fault light status and fault activation status;

[0037] A fault output module is used to output the target fault information.

[0038] In a third aspect, the present application provides a controller, including: a memory, a processor;

[0039] The memory stores computer-executable instructions;

[0040] The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method as described in any one of the first aspects.

[0041] In a fourth aspect, the present application provides a vehicle, comprising a controller, wherein the controller is used to execute the method as described in any one of the first aspects.

[0042] In a fifth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in any one of the first aspects above.

[0043] In a sixth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementations of the first aspect.

[0044] The vehicle fault diagnosis method, device, controller and vehicle provided by the present application include: loading a preset fault table into a data processing environment, verifying the fault confirmation conditions and confirmation time; obtaining detailed fault information from the fault table after confirming the fault, and finally outputting the fault information. The fault information is concentrated in a fault table instead of being hard-coded directly in the control algorithm, which makes the entire fault handling process modular and easy to expand. The vehicle's whole vehicle controller can obtain and process fault information by reading the table without modifying the control algorithm or code each time. The controller also does not need to develop a separate processing model for each fault, but only needs to extract relevant information from the fault table through the fault identifier. Therefore, through the tabular management of faults, the modeling workload and code volume of the vehicle controller in fault signal processing are reduced, the work of adding and updating faults is simplified, and the complexity and workload of maintenance are greatly reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0046] Figure 1 Schematic diagram of the vehicle fault diagnosis method provided in this application Figure 1 ;

[0047] Figure 2 Schematic diagram of the vehicle fault diagnosis method provided in this application Figure 2 ;

[0048] Figure 3 A schematic diagram of the structure of a vehicle fault diagnosis device provided by the present application;

[0049] Figure 4 A schematic diagram of the structure of the electronic device provided in this application.

[0050] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0051] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0052] New energy fault diagnosis is the key work of controller development. As the number of faults increases, the model and code volume of the existing controller fault processing algorithm will increase, which will make later maintenance more troublesome. Therefore, it is particularly important to establish a modular fault model algorithm. The modular fault algorithm makes later fault maintenance and addition simple.

[0053] In view of the above problems, the present application provides a vehicle fault diagnosis method, firstly, a fixed format fault data table is designed, and a new fault is updated or modified in the fault table. The fault table is associated with the algorithm model through a data dictionary. The algorithm model is modularized, and the fault input module reads the fault in real time, performs fault analysis, and outputs the fault identification and fault setting flg. The fault confirmation module polls the fault table content (fault confirmation condition mask, fault confirmation time mask, fault recovery time mask) according to the fault sequence number to parse out the fault confirmation condition, fault confirmation time, and fault recovery time. The current vehicle state and the fault sequence number correspond to the fault confirmation condition. After meeting the conditions, the fault confirmation time and fault recovery time are confirmed to obtain the final confirmed fault. For confirmed faults, the fault sequence number and fault setting flg are stored in an array. The fault polling module polls the confirmed fault sequence number and fault setting flg in real time to store the array to parse the fault sequence number and fault setting flg, poll the fault table in real time, and output the fault information. In the above manner, the fault table is associated with the algorithm model, and new maintenance faults are added and the fault table is changed, which can be synchronized with the model, greatly reducing the workload.

[0054] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0055] Figure 1Schematic diagram of the vehicle fault diagnosis method provided in this application Figure 1 ,like Figure 1 As shown, the method includes:

[0056] S101, loading a preset fault table into a data processing environment; wherein the fault table includes a fault identification, a fault confirmation condition, a fault confirmation time and fault detailed information of each fault.

[0057] In this step, each time the vehicle is powered on, the fault table data is read into a data processing environment, which may be a MATLAB workspace, an embedded controller's memory, or other suitable operating environments.

[0058] Each fault entry in the fault table includes:

[0059] Fault ID: used to uniquely identify each fault.

[0060] Fault confirmation condition: The condition used to determine whether a fault has occurred.

[0061] Fault confirmation time: The time that needs to be reached after a fault occurs in order to confirm the fault.

[0062] Fault details: Specific information when the fault occurs, including fault location, type, etc.

[0063] The fault table can be modified, for example, to modify the confirmation time of certain faults, or detailed information, or to add fault entries.

[0064] Optionally, the fault confirmation conditions, fault confirmation conditions, and fault confirmation time that can be queried in the fault table can all be expressed in the form of a mask to facilitate query.

[0065] S102: Obtain a fault flag and a fault setting flag of a subsystem controller.

[0066] The subsystem controllers are the various modules of the vehicle (such as the battery management system, drive controller, etc.), each of which independently detects and marks fault conditions. The subsystem controllers pass fault flags and fault set flags to the vehicle controller via a communication protocol (such as the CAN bus). The vehicle controller monitors these flags in real time so that it can respond when a fault occurs.

[0067] S103: Determine a target fault confirmation condition and a target fault confirmation time from a fault table according to the fault identifier.

[0068] According to the acquired fault identification, the fault confirmation condition and fault confirmation time corresponding to the fault are found from the fault table. Among them, the fault confirmation condition is a combination of vehicle OFF state, vehicle ON state, vehicle Ready state, vehicle speed <5, and vehicle charging. Different faults correspond to different combinations. The fault confirmation time refers to the time that the state needs to be maintained after the fault occurs.

[0069] S104: If the vehicle meets the target fault determination condition and the duration of the fault setting flag is greater than the target fault confirmation time, it is confirmed that the vehicle has a fault.

[0070] Monitor the fault flag and fault setting flag in real time and record the duration. Obtain the actual status of the vehicle and compare it with the target fault confirmation condition. If the confirmation condition of the target fault is met and the duration of the fault flag is greater than the target fault confirmation time, the fault is confirmed to be a real fault.

[0071] S105 . Determine target fault detailed information from the fault table according to the fault identification, where the target fault detailed information includes fault location, fault type, fault light status, and fault activation status.

[0072] From the fault table, find detailed information about the fault based on the fault ID, which usually includes:

[0073] Fault location: Indicates where the fault occurred (e.g., battery module, drive motor, etc.).

[0074] Fault type: describes the nature of the fault, such as electrical fault, mechanical fault, etc.

[0075] Malfunction light status: Indicates whether the malfunction light on the instrument panel is on to alert the driver.

[0076] Fault activation status: Indicates whether the fault has been activated and determines whether to trigger related protection measures.

[0077] S106. Output target fault information.

[0078] If a fault is confirmed, the target fault information will be output. The vehicle controller can feed back the fault information to the driver through the vehicle display system, displaying the fault code, location, type, etc.; it can also send the fault information to external diagnostic equipment through the OBD interface for viewing and analysis.

[0079] The vehicle fault diagnosis method provided in this embodiment includes loading a fault table, real-time monitoring of fault identification, verifying fault confirmation conditions and confirmation time, obtaining detailed fault information, and finally outputting the fault information. The fault information is concentrated in a fault table instead of being hard-coded directly in the control algorithm, which makes the entire fault handling process modular and easy to expand. The vehicle controller can obtain and process the fault information by reading the table without modifying the control algorithm or code each time. The controller also does not need to develop a separate processing model for each fault, but only needs to extract relevant information from the fault table through the fault identification.

[0080] Therefore, through the tabular management of faults, not only can the modeling workload and code volume of the vehicle controller in fault signal processing be reduced, but it can also effectively solve the problem of the insynchronization between fault table maintenance and algorithm model. The table-driven approach simplifies the work of adding and updating faults, and greatly reduces the complexity and workload of maintenance.

[0081] After the target fault information is output, the corresponding countermeasures can be automatically executed according to the target fault information. The fault table also includes fault degradation measures corresponding to each fault, such as limiting the motor speed and power after the motor temperature is too high. The fault degradation measures are determined from the fault table according to the fault identification, and then the fault degradation measures are executed.

[0082] If the user modifies the fault table, either by adding a new fault or modifying the fault, the controller needs to obtain a new fault table. The new fault table includes a new fault identifier, a new fault confirmation condition, a new fault confirmation time, and new fault details; the new fault table is loaded into the data processing environment to replace the fault table. In this way, the synchronous linkage between the table and the fault confirmation algorithm model can be completed.

[0083] The fault diagnosis method is introduced below with a specific example.

[0084] 1) Design a data dictionary format based on Microsoft Excel (.xls). According to this approach, the attributes of data objects are collected and organized into an Excel workbook (with a .xls extension) according to a predefined schema, which can be further used as an overall interface and delivery for modeling, software integration, and calibration.

[0085] The data dictionary is a tool for defining, describing and managing data, and is used to store and manage information such as data structure, data type, field meaning, and data constraints. The data dictionary records the definition, structure, and constraints of each data element in the system. When the content of a table changes (for example, modifying the field type, field name, or adding a new field), the data dictionary will be updated accordingly to maintain accurate description and consistency of the data.

[0086] In addition, the data dictionary associates the specific information of each fault (such as fault description, fault classification, trigger conditions, etc.) with the corresponding algorithm model. Each unique identifier of a fault (such as a fault ID) has a corresponding entry in the data dictionary, pointing to the algorithm module associated with it. In this way, each fault record in the fault table can find the corresponding algorithm processing module through the data dictionary.

[0087] When the fault table changes (such as adding or modifying fault items), the data dictionary ensures that the new fault is automatically associated with the corresponding algorithm. In this way, developers do not need to manually modify the relevant parts in the code, but only need to update the fault table and data dictionary.

[0088] For example, if a new fault is added (such as "Battery overtemperature"), you only need to add the fault information to the fault table and associate it with the appropriate algorithm model in the data dictionary. The algorithm model will automatically adapt to the new fault.

[0089] In one implementation, each table, column in the database, or data structure in the API may be listed in detail in the form of a table in the data dictionary.

[0090] For example, in a table-based data dictionary, the field "user_id" may be defined as an integer (int), with a length of 10 and cannot be empty. When the requirements change, it is changed to a "floating type", and the corresponding algorithm can be associated with the floating type algorithm.

[0091] 2) Fault table: contains three worksheets (MEASURE, CALIBRATION, MAP_DATA). MAP_DATA is a hyperlink in the CALIBRATION table, which defines the fault-related attributes in detail.

[0092] 3) Arrangement of fault tables. The keyword names of the worksheets include MEASURE, CALIBRATION, and a separate worksheet named MAP_DATA, which is used to store multidimensional MAP data. The MEASURE worksheet is for observations related to fault processing, the CALIBRATION worksheet is for calibration quantities related to fault processing, and the MAP_DATA worksheet is a hyperlink to the multidimensional calibration quantities in the CALIBRATION worksheet.

[0093] 4) Fault table MAP_DATA worksheet data arrangement. The data includes the title row and the following data. The keywords of the title row include: fault confirmation condition mask, fault confirmation time mask, fault recovery time mask, DM1_SPN mask, DM1_FMI mask, fault downgrade measure mask, fault description, fault sequence number, fault classification, fault confirmation condition (vehicle OFF, vehicle ON, vehicle Ready, vehicle speed <5, vehicle charging), J1939DM1 (SPN, FMI, CM, LED, SaveFlg, Protity, Active), fault downgrade measures (fault level FaultLeve, fast power off HV_Fa stOff_Req, normal power off HV_NormalOff_Req, drive power reduction PwrReduce_pct, speed limit enable VehSpdLim_Open, speed limit value VehSpdLim_kpd, energy recovery off DisRegen_Req, DCDC off DisDCDC_Req, oil pump off DisOilPump_Req, air pump off DisAirPump_Req, air conditioning off DisAC_Req, heater off DisPTC_Req, charging off DisChrg_Req). Keywords are used to identify the title row. The items before the fault description keywords are data dictionary content, which is associated with the algorithm model, and the contents after are comments for technical or related personnel to understand and use.

[0094] 5) Read the fault table data into the MATLAB workspace. Create a SeatTest.Parameter or SeatTest.Signal data object in the MATLAB workspace and call the create_seat_parameter.m or create_seat_signal.m file through the script read_DD_xls.m.

[0095] 6) Fault algorithm: 4 independent modules, namely fault confirmation condition module, fault confirmation module, fault polling module, and fault input and output module.

[0096] 7) Fault polling module. After reading the fault confirmed by the fault confirmation module, this module polls the fault storage array in real time, parses and outputs the fault sequence number and fault setting flg, and the two values ​​enter the J1939DM1 module. According to the sequence number, the corresponding DM1_SPN mask and DM1_FMI mask in the fault table are read, and J1939DM1 (fault component or system number SPN, fault mode FMI, whether the fault is a conditional monitoring type CM, fault indicator status LED, whether to save fault information SaveFlg, fault priority Protity, fault activation status Active) is parsed. Active and fault setting flg are combined, which means that if either the activation status Active or the fault setting flg flag is "1", indicating that the fault is activated, then the fault is considered to be activated or triggered. The setting triggers the output of DM1 fault information. The two values ​​enter the fault degradation measure module, and the corresponding fault degradation measure mask in the fault table is read according to the serial number patrol, and the fault degradation measures are parsed (fault level FaultLeve, fast power off HV_FastOff_Req, normal power off HV_NormalOff_Req, drive power reduction PwrReduce_pct, speed limit enable VehSpdLim_Open, speed limit value VehSpdLim_kpd, energy recovery off DisRegen_Req, DCDC operation off DisDCDC_Req, oil pump operation off DisOilPump_Req, air pump operation off DisAirPump_Req, air conditioning operation off DisAC_Req, heater operation off DisPTC_Req, charging off DisChrg_Req), each degradation measure item is calculated with the initial design value (MAX, or set), and the trigger confirmation fault degradation measure array is stored (the order of degradation measure items is fixed).

[0097] Figure 2 Schematic diagram of the vehicle fault diagnosis method provided in this application Figure 2 ,like Figure 2 As shown, the following steps are included:

[0098] S201, fault input.

[0099] Obtain a fault identifier from an external interface. The fault identifier may be an SPN code, an FMI code identifier, etc. sent by the sub-controller system.

[0100] S202: Fault analysis.

[0101] According to the input fault identification, the fault sequence number of the fault in the fault table can be determined. The fault sequence number is unique in the table and is the sequence number of the leftmost entry in the table.

[0102] S203: Determine the fault confirmation condition mask from the fault table according to the fault sequence number.

[0103] Search the corresponding fault confirmation condition mask by the fault number in the fault table. The fault confirmation condition mask is used to confirm whether the fault has met the triggering requirements.

[0104] Exemplarily, the fault confirmation conditions of each fault entry include the following five states: vehicle OFF, vehicle ON, vehicle Ready, vehicle speed <5, and whether the vehicle is charged. Each state can be represented by 1 or 0. If it is 1, it means that the fault can only be triggered when the condition is activated, and 0 means that the condition does not need to be activated. The fault confirmation condition mask is a mask determined based on the combination of the five states. Different combinations form different masks, and the specific association relationship is not limited. In actual applications, there is no need to obtain the five states one by one, and the fault condition mask can be directly obtained, which represents the combination of the five states.

[0105] Similarly, not only the fault confirmation condition is expressed in mask form, the fault confirmation time is the fault confirmation time mask, the fault recovery time is the fault recovery time mask, and the fault detailed information includes the fault type SPN mask and the fault mode and location FMI mask.

[0106] S204: Determine whether the current vehicle status satisfies a fault confirmation condition.

[0107] The current state of the vehicle is obtained, and the same mask association relationship is used to determine the current fault confirmation condition mask of the vehicle, and compare it with the fault confirmation condition mask determined from the fault table. If they are the same, it means that the fault confirmation condition is met.

[0108] S205: Combine the confirmed fault sequence number and the fault setting flg.

[0109] S206: Look up the fault confirmation time from the fault table to determine whether the fault duration meets the fault confirmation time.

[0110] If the fault still exists within the fault confirmation time, it means that the fault is still ongoing.

[0111] S207: Query the fault recovery time from the fault table to determine whether the fault is recovered within the fault recovery time.

[0112] Some faults can be automatically recovered and have a default fault recovery time. You need to determine whether the fault is recovered within the fault recovery time. If it is recovered, no subsequent steps are required.

[0113] S208, confirm the fault, and store the fault sequence number and the fault bit flg in the storage array.

[0114] At this point, it is determined that the vehicle has a fault and cannot be automatically restored, so the fault sequence number and the fault set flag are stored in the fault storage array, indicating that the fault has been confirmed.

[0115] S209, polling and parsing the storage array, and parsing the SPN mask and the FMI mask from the fault table according to the fault sequence number.

[0116] Parse J1939DM1 (faulty component or system number SPN, fault mode FMI, whether the fault is conditional monitoring type CM, fault indicator status LED, whether to save fault information SaveFlg, fault priority Protity, fault activation status Active).

[0117] S210: The fault activation state Active and the fault setting flg are combined.

[0118] The fault activation state (Active) is combined with the fault set flag (flg). If either flag is "1", the fault is activated.

[0119] S211, trigger fault information output.

[0120] If a fault has been activated, the output of fault information is triggered, such as displaying the fault type and fault location on a display screen for further processing.

[0121] S212: parse the fault downgrade measure mask according to the fault sequence number polling table.

[0122] The fault degradation measure mask includes the status of each item, such as fault level FaultLeve, fast power off HV_FastOff_Req, normal power off HV_NormalOff_Req, drive power reduction PwrReduce_pct, speed limit enable VehSpdLim_Open, speed limit value VehSpdLim_kpd, energy recovery off DisRegen_Req, DCDC operation off DisDCDC_Req, oil pump operation off DisOilPump_Req, air pump operation off DisAirPump_Req, air conditioning operation off DisAC_Req, heater operation off DisPTC_Req, and charging off DisChrg_Req.

[0123] Different faults and different fault levels may have corresponding degradation measures, which require specific settings by the developer.

[0124] S213. Compare each downgrade measure item with the initial design value and take the maximum downgrade value.

[0125] S214. Confirm that the fault degradation measures are stored in the array.

[0126] S215, reading the single fault level information of each subsystem controller.

[0127] When the subsystem controller sends the fault identification and fault setting flg, it also sends the single fault level information determined by itself.

[0128] S216: Read the fault degradation measure array and parse the fault level information.

[0129] S217. Take the maximum value of the two fault levels.

[0130] By comparing the fault level information obtained by analysis with the fault level information sent by the received sub-controller, a secondary verification is performed to prevent analysis errors or controller errors.

[0131] S218. Output the maximum fault level information.

[0132] The determined fault level information is output on a vehicle display.

[0133] S219, read and confirm the fault degradation measures array output.

[0134] Through this technical solution, fault information is synchronized to the algorithm model through fault table management and real-time polling. Each input fault will be processed, and the algorithm model is modular, simple in design, and requires less code.

[0135] Figure 3 A schematic diagram of the structure of a vehicle fault diagnosis device provided in this application, such as Figure 3 As shown, the vehicle fault diagnosis device 30 includes:

[0136] The loading module 301 is used to load a preset fault table into the data processing environment; wherein the fault table includes a fault identification, a fault confirmation condition, a fault confirmation time and fault detailed information of each fault;

[0137] A fault input module 302 is used to obtain a fault flag and a fault setting flag of a subsystem controller;

[0138] A fault confirmation condition module 303 is used to determine a target fault confirmation condition and a target fault confirmation time from the fault table according to the fault identifier;

[0139] A fault confirmation module 304 is used to confirm that a vehicle fault occurs if the vehicle meets the target fault determination condition and the duration of the fault setting flag is greater than the target fault confirmation time;

[0140] A fault polling module 305 is used to determine target fault detailed information from the fault table according to the fault identifier, wherein the target fault detailed information includes fault location, fault type, fault light status and fault activation status;

[0141] The fault output module 306 is used to output the target fault information.

[0142] Optionally, the fault table also includes fault degradation measures corresponding to each fault, and the fault output module 306 is further used to:

[0143] determining a fault degradation measure from the fault table according to the fault identifier;

[0144] The fault degradation measures are executed.

[0145] Optionally, the fault degradation measure includes a fault level, and the fault output module 306 is further used to:

[0146] Obtaining a single fault level of the subsystem controller;

[0147] Taking the maximum value of the fault level and the single fault level as the target fault level;

[0148] The target failure level is output.

[0149] Optionally, the fault output module 306 is further used for:

[0150] If the fault activation state indicates that a fault is activated, or the fault setting flag indicates that a fault is triggered, the output of the target fault information will be triggered.

[0151] Optionally, the fault table also includes the fault recovery time of each fault, and the fault confirmation condition module 303 is further used to:

[0152] Determine a target fault recovery time according to the fault identifier;

[0153] Accordingly, the fault confirmation module 304 is specifically used for:

[0154] If the vehicle meets the target fault determination condition and the duration of the fault setting mark is greater than the target fault confirmation time, determining whether the fault setting mark is restored to a non-fault state within the target fault recovery time;

[0155] If the fault setting flag does not return to a non-fault state, it is confirmed that the vehicle has a fault.

[0156] Optionally, the fault confirmation condition in the fault table is a fault confirmation condition mask, the fault confirmation time is a fault confirmation time mask, the fault recovery time is a fault recovery time mask, and the fault detailed information includes a fault type SPN mask and a fault mode and location FMI mask.

[0157] Optionally, the loading module 301 is further used for:

[0158] Acquire a new fault table, wherein the new fault table includes a new fault identifier, a new fault confirmation condition, a new fault confirmation time, and new fault detailed information;

[0159] The new fault table is loaded into the data processing environment to replace the fault table.

[0160] The vehicle fault diagnosis device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0161] Figure 4 This is a schematic diagram of the structure of the electronic device provided in this application, which may be a controller of a vehicle. Figure 4 As shown, the electronic device 50 provided in this embodiment includes: at least one processor 501 and a memory 502. Optionally, the device 50 also includes a communication component 503. The processor 501, the memory 502 and the communication component 503 are connected via a bus 504.

[0162] In a specific implementation process, at least one processor 501 executes the computer-executable instructions stored in the memory 502, so that at least one processor 501 executes the above method.

[0163] The specific implementation process of the processor 501 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0164] In the above embodiments, it should be understood that the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the invention can be directly implemented as a hardware processor, or can be implemented by a combination of hardware and software modules in the processor.

[0165] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (NVM), such as at least one disk storage.

[0166] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of this application is not limited to only one bus or one type of bus.

[0167] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0168] The present application also provides a vehicle, including a vehicle controller, which can implement the method in the above embodiment.

[0169] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0170] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0171] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0172] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

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

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

[0175] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0176] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0177] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A vehicle fault diagnosis method, characterized in that: The method comprises: Loading a preset fault table into a data processing environment; wherein the fault table includes a fault identification, a fault confirmation condition, a fault confirmation time and fault detailed information of each fault; Obtaining the fault flag and fault setting flag of the subsystem controller; Determine a target fault confirmation condition and a target fault confirmation time from the fault table according to the fault identifier; If the vehicle meets the target fault determination condition and the duration of the fault setting flag is greater than the target fault confirmation time, it is confirmed that the vehicle has a fault; Determining target fault detailed information from the fault table according to the fault identifier, the target fault detailed information including fault location, fault type, fault light status and fault activation status; The target fault information is output.

2. The method according to claim 1, characterized in that: The fault table also includes fault degradation measures corresponding to each fault, and the method further includes: determining a fault degradation measure from the fault table according to the fault identifier; The fault degradation measures are executed.

3. The method according to claim 2, characterized in that The fault degradation measure includes a fault level, and the method further includes: Obtaining a single fault level of the subsystem controller; Taking the maximum value of the fault level and the single fault level as the target fault level; The target failure level is output.

4. The method according to any one of claims 1 to 3, characterized in that: The outputting the target fault information comprises: If the fault activation state indicates that a fault is activated, or the fault setting flag indicates that a fault is triggered, the output of the target fault information will be triggered.

5. The method according to any one of claims 1 to 3, characterized in that: The fault table also includes the fault recovery time of each fault, and the method further includes: Determine a target fault recovery time according to the fault identifier; Correspondingly, if the vehicle meets the target fault determination condition and the duration of the fault setting flag is greater than the target fault confirmation time, then confirming that the vehicle has a fault includes: If the vehicle meets the target fault determination condition and the duration of the fault setting mark is greater than the target fault confirmation time, determining whether the fault setting mark is restored to a non-fault state within the target fault recovery time; If the fault setting flag does not return to a non-fault state, it is confirmed that the vehicle has a fault.

6. The method according to claim 5, characterized in that In the fault table, the fault confirmation condition is the fault confirmation condition mask, the fault confirmation time is the fault confirmation time mask, the fault recovery time is the fault recovery time mask, and the fault detailed information includes the fault type SPN mask and the fault mode and location FMI mask.

7. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Acquire a new fault table, wherein the new fault table includes a new fault identifier, a new fault confirmation condition, a new fault confirmation time, and new fault detailed information; The new fault table is loaded into the data processing environment to replace the fault table.

8. A vehicle fault diagnosis device, characterized in that: The device comprises: A loading module, used to load a preset fault table into the data processing environment; wherein the fault table includes a fault identification, a fault confirmation condition, a fault confirmation time and fault detailed information of each fault; A fault input module is used to obtain a fault flag and a fault setting flag of a subsystem controller; A fault confirmation condition module, used to determine a target fault confirmation condition and a target fault confirmation time from the fault table according to the fault identifier; A fault confirmation module, configured to confirm that a fault occurs in the vehicle if the vehicle meets the target fault determination condition and the duration of the fault setting flag is greater than the target fault confirmation time; A fault polling module, used to determine target fault detailed information from the fault table according to the fault identifier, the target fault detailed information including fault location, fault type, fault light status and fault activation status; A fault output module is used to output the target fault information.

9. A controller, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 7.

10. A vehicle, characterized in that: The method comprises a controller, wherein the controller is used to execute the method according to any one of claims 1 to 7.

Images