Vehicle fault processing method and device, vehicle, electronic equipment and medium

Abstract

The embodiment of the invention provides a vehicle fault processing method and device, a vehicle, electronic equipment and a medium. The method comprises the steps that fault signals of modules in the vehicle are acquired; and under the condition that the fault signal triggers the associated suppression condition, performing suppression processing on the fault signal. Through the embodiment of the invention, part of fault signals in the vehicle are suppressed, all the fault signals do not need to be diagnosed, fault information does not need to be stored, the diagnosis efficiency is improved, and the occupied storage space is reduced.

Description

Technical Field

[0001] The present invention relates to the field of automobile technology, and in particular to a method, device, vehicle, electronic equipment and medium for handling vehicle faults. Background Art

[0002] In smart cars, many modules are involved, such as the chassis domain of the vehicle, including MCU (Microcontroller Unit), power management module, communication module, EPS (Electronic Power Steering), EPB (Electrical Park Brake), and suspension system. These modules may fail, and fault diagnosis is particularly important.

[0003] In the prior art, all acquired fault signals are usually diagnosed to obtain diagnostic results and store fault information. However, there are a large number of faults in a vehicle, and one fault may trigger multiple other faults. Diagnosing and storing multiple fault data not only reduces execution efficiency but also wastes storage space. Summary of the invention

[0004] In view of the above problems, a method, device, vehicle, electronic device and medium for vehicle fault handling are proposed to overcome the above problems or at least partially solve the above problems, including:

[0005] A method for handling a vehicle fault, the method comprising:

[0006] Obtain fault signals from modules in the vehicle;

[0007] In the case where the fault signal triggers an associated suppression condition, suppression processing is performed on the fault signal.

[0008] Optionally, after obtaining the fault signal of the module in the vehicle, the method further includes:

[0009] determining a diagnostic suppression identifier associated with the fault signal;

[0010] In case the diagnostic suppression identifier is in an activated state, it is determined that the fault signal triggers an associated suppression condition.

[0011] Optionally, after determining the diagnostic suppression identifier associated with the fault signal, the method further comprises:

[0012] determining a plurality of fault codes associated with the diagnostic suppression identifier;

[0013] When a diagnostic check result corresponding to any target fault code among the plurality of fault codes indicates that a fault state exists, it is determined that the diagnosis inhibition identifier is in an activated state.

[0014] Optionally, after determining the plurality of fault codes associated with the diagnostic suppression identifier, the method further comprises:

[0015] Acquire a two-dimensional matrix; wherein the two-dimensional matrix stores a plurality of candidate diagnostic suppression identifiers and diagnostic inspection results corresponding to a plurality of fault codes associated with each candidate diagnostic suppression identifier;

[0016] By using the two-dimensional matrix, it is detected whether any target fault code among the multiple fault codes associated with the diagnosis suppression identifier has a diagnostic check result indicating that a fault state exists.

[0017] Optionally, it also includes:

[0018] In the case where the fault signal does not trigger an associated suppression condition, performing diagnostic processing on the fault signal;

[0019] The two-dimensional matrix is ​​updated according to the diagnosis and inspection result of the fault signal.

[0020] Optionally, it also includes:

[0021] In the case where the fault signal does not trigger an associated suppression condition, performing diagnostic processing on the fault signal;

[0022] The diagnosing and processing the fault signal includes:

[0023] determining a number of times a fault signal of a target fault state is received;

[0024] When the number is greater than or equal to a preset number threshold corresponding to the target fault state, determining that the diagnostic inspection result of the fault signal is the target fault state;

[0025] Alternatively, determining a duration of receiving a fault signal of a target fault state;

[0026] In a case where the duration is greater than or equal to a preset duration threshold corresponding to the target fault state, it is determined that the diagnostic check result of the fault signal is the target fault state.

[0027] Optionally, before diagnosing the fault signal, the method further includes:

[0028] When the currently received fault signal is in a fault state and the previously received fault signal is in a non-fault state, performing the diagnostic processing on the fault signal;

[0029] Alternatively, when the currently received fault signal is in a non-fault state and the previously received fault signal is in a fault state, the diagnostic processing of the fault signal is performed.

[0030] Optionally, before diagnosing the fault signal, the method further includes:

[0031] When the received fault signal indicates that a fault state exists and the diagnostic check result after filtering of the fault signal indicates that there is no fault state, performing the diagnostic processing on the fault signal;

[0032] Alternatively, when the received fault signal is in a non-fault state and the diagnostic check result of the fault signal after filtering is that a fault state exists, the diagnostic processing of the fault signal is performed.

[0033] Optionally, it also includes:

[0034] The data identifier associated with the fault code is configured, and when the condition for freezing the frame is triggered, the freeze frame including the data identifier associated with the fault code and the associated data is stored.

[0035] A vehicle fault processing device, the device is used for:

[0036] Obtain fault signals from modules in the vehicle;

[0037] In the case where the fault signal triggers an associated suppression condition, suppression processing is performed on the fault signal.

[0038] A vehicle comprises a processor, a memory and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the vehicle fault handling method as described above when executed by the processor.

[0039] An electronic device comprises a processor, a memory and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the vehicle fault handling method as described above when executed by the processor.

[0040] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the vehicle fault processing method as described above is implemented.

[0041] The embodiments of the present invention have the following advantages:

[0042] In an embodiment of the present invention, by acquiring a fault signal of a module in a vehicle, and when the fault signal triggers an associated suppression condition, the fault signal is suppressed, thereby suppressing some fault signals in the vehicle. There is no need to diagnose all fault signals and store fault information, thereby improving diagnostic efficiency and reducing storage space usage. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solution of the present invention, the accompanying drawings required for use in the description of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.

[0044] Figure 1 is a flowchart of the steps of a method for handling a vehicle fault provided by some embodiments of the present invention;

[0045] Figure 2 is a schematic diagram of a domain controller provided by some embodiments of the present invention;

[0046] Figure 3 is a schematic diagram of a freeze frame processing process provided by some embodiments of the present invention. DETAILED DESCRIPTION

[0047] In order to make the above-mentioned purposes, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below in conjunction with the accompanying drawings and specific embodiments. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0048] Reference Figure 1 , shows a flowchart of the steps of a method for handling vehicle faults provided by some embodiments of the present invention, which can be applied to a controller of a vehicle, such as a domain controller, such as Figure 2 The domain controller is equipped with a function monitoring module and a diagnosis management module. The function monitoring module calculates the original diagnostic data associated with each fault and outputs the original fault signal, including the original fault signals of MCU, power management module, communication module, EPS, EPB, and suspension system. The diagnosis management module realizes the diagnosis of fault signals through sub-modules such as diagnosis suppression, diagnosis filtering, and diagnosis fault storage.

[0049] Specifically, the following steps may be included:

[0050] Step 101, obtaining a fault signal of a module in a vehicle.

[0051] In some examples, the module in the vehicle may be software or hardware or a combination of software and hardware used by the vehicle to implement specific functions. The module in the vehicle may be a module in each controller of the vehicle, such as a functional module. MCU, power management module, communication module, EPS, EPB, and suspension system can all be used as a functional module. Of course, in addition to functional modules, other modules in each controller of the vehicle, such as control modules and diagnostic modules, can also be included.

[0052] In practical applications, the function monitoring module can be used to obtain the fault signal of the module in the vehicle, that is, the original fault signal. Specifically, the function monitoring module can calculate the original diagnostic data associated with each fault and output the original fault signal, including the original fault signal of the MCU, power management module, communication module, EPS, EPB, and suspension system, etc. In response to the generation of the fault signal, step 101 and subsequent steps are executed.

[0053] In some embodiments of the present invention, after obtaining the fault signal of the module in the vehicle, the method further includes:

[0054] Determine a diagnostic suppression identifier associated with the fault signal; and when the diagnostic suppression identifier is in an activated state, determine a suppression condition associated with the fault signal triggering.

[0055] In practical applications, it is possible to determine whether a fault signal triggers an associated suppression condition. By determining whether the associated suppression condition is triggered, it is possible to determine whether to suppress the fault signal. Suppressing the fault signal can be understood as ignoring the fault signal, reporting the fault, and not issuing an alarm.

[0056] In some examples, determining whether the fault signal triggers an associated suppression condition may include:

[0057] In the diagnosis suppression module, it is determined whether the fault signal is suppressed by the diagnosis suppression identifier associated with the fault and activated, or suppressed by the fault status masking interface function.

[0058] For the suppression of the interface function shielded by the fault status, the details are as follows:

[0059] The fault code masking parameter is passed through the interface function to achieve the classification suppression of the fault code. The fault code data bits correspond to the data bits of the fault code masking parameter one by one. If one or several bits of the fault code masking parameter are set to 1, the fault code of this type corresponding to the data bits set to 1 by the fault code masking parameter is masked.

[0060] For suppression by diagnostic suppression identifier, the details are as follows:

[0061] In practical applications, a diagnostic suppression identifier can be set, and different fault signals can be associated with different diagnostic suppression identifiers. When the diagnostic suppression identifier related to the fault signal is in an activated state, the fault signal can be suppressed, that is, the suppression condition is triggered. When the diagnostic suppression identifier related to the fault signal is in an inactivated state, the suppression condition is not triggered.

[0062] In some embodiments of the present invention, after determining the diagnostic suppression identifier associated with the fault signal, the method further includes:

[0063] Determine a plurality of fault codes associated with the diagnostic suppression identifier; and determine that the diagnostic suppression identifier is in an activated state when a diagnostic check result corresponding to any target fault code among the plurality of fault codes is a fault state.

[0064] In practical applications, each diagnostic suppression identifier may be associated with multiple fault codes, and multiple diagnostic suppression identifiers and diagnostic inspection results (historical diagnostic inspection results) corresponding to the multiple fault codes associated with each diagnostic suppression identifier may be pre-stored.

[0065] After receiving the fault signal, the fault code of the current fault signal can be determined, and then the diagnostic suppression identifier associated with the current fault signal can be determined based on the fault code. Then, the diagnostic inspection results of multiple fault codes associated with the pre-stored diagnostic suppression identifier (historical diagnostic inspection results) can be used to determine whether there is a target fault code with a faulty state as a result of the diagnostic inspection. If so, that is, the diagnostic suppression identifier has previously experienced a fault, then the diagnostic suppression identifier is in an activated state and can be suppressed. If not, then the diagnostic suppression identifier is in an inactivated state.

[0066] In some embodiments of the present invention, after determining the plurality of fault codes associated with the diagnostic suppression identifier, the method further includes:

[0067] A two-dimensional matrix is ​​obtained; and through the two-dimensional matrix, it is detected whether any target fault code among the multiple fault codes associated with the diagnosis suppression identifier has a diagnostic check result corresponding to a fault state.

[0068] The two-dimensional matrix may store a plurality of candidate diagnostic suppression identifiers and diagnostic inspection results corresponding to a plurality of fault codes associated with each candidate diagnostic suppression identifier.

[0069] In some examples, the matrix data type is a 16-bit unsigned integer, the row subscript is the total number of diagnostic suppression identifiers, that is, each row corresponds to a diagnostic suppression identifier, and the column subscript is the maximum number of faults supported by the controller divided by 16, that is, each column corresponds to a fault code associated with the diagnostic suppression identifier. Each bit of the matrix data represents a diagnostic check result corresponding to a fault code, which can be used to enable the activation state of the diagnostic suppression identifier.

[0070] In some examples, each diagnostic suppression identifier includes an associated value, the associated value of the diagnostic suppression identifier being 0 to disable suppression, and the remaining values ​​being identifiers to enable suppression.

[0071] When the diagnostic suppression identifier of the original fault is the associated value of the diagnostic suppression identifier 0, suppression is not enabled and the fault is directly passed to the diagnostic filter module.

[0072] When the associated value of the diagnostic suppression identifier of the original fault is not 0, query the two-dimensional matrix to see whether there is a value greater than 0 in any column of the row corresponding to the diagnostic suppression identifier that suppresses the original fault (i.e., it indicates that there is a fault code previously marked as a fault state in the fault code associated with the diagnostic suppression identifier). If so, the fault is suppressed by the associated and activated diagnostic suppression identifier, and no filtering is required, and the fault signal is directly determined to be fault-free. If not, the diagnostic suppression identifier associated with the fault is not activated, and the original fault needs to be transferred to the diagnostic filtering module for subsequent processing.

[0073] In some embodiments of the present invention, it also includes:

[0074] In the case that the fault signal does not trigger the associated suppression condition, the fault signal is diagnosed and processed; and according to the diagnosis and inspection result of the fault signal, the two-dimensional matrix is ​​updated.

[0075] After obtaining the diagnostic check result of a certain fault signal, filtering processing can be performed, and a two-dimensional matrix of diagnostic suppression identifiers can be set according to the diagnostic check result after filtering processing. In actual applications, the diagnostic check result is refreshed and the activation state of the diagnostic suppression identifier bound as the parent fault is determined by the diagnostic suppression module, and can be used for diagnostic suppression judgment of other faults.

[0076] In some examples, when a fault signal does not trigger an associated suppression condition, that is, a fault signal is received, and the diagnostic suppression identifier associated with the fault signal is not in an activated state, indicating that the fault signal associated with the fault signal has not appeared before (or may not have appeared within the most recent preset time period), then after receiving the fault signal, the fault signal can be diagnosed and processed, and then the two-dimensional matrix described above can be updated according to the diagnostic inspection results of the fault signal, and the activation state of the diagnostic suppression identifier associated with the fault signal can be updated by updating the two-dimensional matrix.

[0077] For example, update a two-dimensional matrix as follows:

[0078] As described above, each row in the two-dimensional matrix corresponds to a diagnostic suppression identifier, each column corresponds to a fault code associated with the diagnostic suppression identifier, and each bit represents a diagnostic check result corresponding to a fault code, which can be used to enable the activation state of the diagnostic suppression identifier (for example, a bit of 1 indicates that the diagnostic check result is a fault, which means it can be activated; a bit of 0 indicates that the diagnostic check result is no fault, which means it is in an inactivated state).

[0079] When updating the two-dimensional matrix, the row where the diagnostic suppression identifier associated with the fault signal is located can be found in the two-dimensional matrix, and the fault code of the fault signal can be found in the row, and then the bit of the fault code is set to 1 or 0 to represent whether the diagnostic check result of the fault signal is faulty or not. After the bit is set to 1, that is, the diagnostic check result of the fault signal is faulty, the diagnostic suppression identifier is updated to an activated state; after the bit is set to 0, that is, the diagnostic check result of the fault signal is not faulty, the diagnostic suppression identifier remains in an inactive state.

[0080] Step 102: When the fault signal triggers an associated suppression condition, suppress the fault signal.

[0081] In some examples, the fault signal to be suppressed is other related faults triggered by an existing fault, that is, if a corresponding fault has existed before, the related fault can be suppressed when it occurs again.

[0082] In practical applications, the diagnostic suppression module is used to suppress the occurrence of other related faults when certain parent faults (the fault that occurred first is the parent fault, and other faults related to the fault are sub-faults) occur. When the fault signal triggers the associated suppression condition, that is, the parent fault representing the fault signal has occurred first, the fault signal as a sub-fault can be suppressed.

[0083] In some examples, a parent fault corresponds to multiple sub-faults. After a certain fault occurs, it may cause one or more other faults. "One fault" is the parent fault; "other one or more faults" are sub-faults. Each fault can be used as a parent fault to suppress sub-faults and mark the diagnostic suppression identifier bound to the parent fault. At the same time, it can also be used as a sub-fault of other faults and mark the diagnostic suppression identifier that suppresses the fault.

[0084] In some examples, the filtered diagnostic inspection result can be used as a parent fault to suppress other related faults, and the diagnostic suppression identifier bound to the parent fault is calibrated. When the identifier bound to the parent fault is not a diagnostic suppression identifier, the associated value is not 0, and the state of the filtered diagnostic inspection result is flipped, the refresh of the above two-dimensional matrix is ​​performed. If the filtered diagnostic inspection result is that there is a fault, the diagnostic suppression identifier bound to the fault is activated, and the corresponding row of the associated value of the diagnostic suppression identifier bound to the fault and the corresponding bit of the column data of the diagnostic inspection result are assigned 1 in the two-dimensional matrix. If the filtered diagnostic inspection result is that there is no fault, the diagnostic suppression identifier bound to the fault is not activated, and the corresponding row of the associated value of the diagnostic suppression identifier bound to the fault and the corresponding bit of the column data of the diagnostic inspection result are assigned 0 in the two-dimensional matrix.

[0085] Take the fault of the suspension system as an example: for example, the solenoid valve that controls the height is short-circuited to the power supply, generating an original fault signal. This fault can be used as a sub-fault, and one of its parent faults is that the solenoid valve power supply voltage is too low. When this sub-fault occurs, the diagnostic check confirms that the parent fault already exists. The parent fault is bound to the diagnostic suppression identifier 1 and the diagnostic suppression identifier 3. In the diagnostic suppression two-dimensional matrix, the corresponding bit of the column data corresponding to the row subscript 1 and the solenoid valve power supply voltage is too low has been assigned a value of 1, and the corresponding bit of the column data corresponding to the row subscript 3 and the solenoid valve power supply voltage is too low has also been assigned a value of 1.

[0086] The diagnostic suppression identifier of the calibrated suppression height battery valve short circuit to power supply fault is queried. The identifiers that suppress this fault are diagnostic suppression identifier 1 and diagnostic suppression identifier 5. If a value greater than 0 is found in the row with row subscript 1 in the diagnostic suppression two-dimensional matrix, the fault is suppressed by the associated and activated diagnostic suppression identifier, and the fault signal is directly determined to be fault-free. If the fault is not suppressed by diagnostic suppression identifier 1, it is necessary to continue to query to determine whether the fault is suppressed by diagnostic suppression identifier 5.

[0087] In some examples, the input of the diagnostic fault storage module is the diagnostic inspection result output by the diagnostic filter module, which provides a storage entry for the determined fault event and its related information, and completes the use of storage space, replacement after the storage space is full, and fault clearing functions. Each storage entry stores a fault event and its related information.

[0088] In some embodiments of the present invention, the further step includes: performing diagnostic processing on the fault signal when the fault signal does not trigger an associated suppression condition.

[0089] When the fault signal does not trigger the associated suppression condition, that is, the fault is not suppressed, it is necessary to determine the timing of starting the diagnostic filter in the diagnostic filter module. When the diagnostic filter is started, the anti-bounce filter is used to output the diagnostic inspection result of the fault signal.

[0090] In some examples, after the diagnostic check result is obtained, a storage operation is performed through a diagnostic fault storage module to control an instrument alarm or control the system to enter a safe state.

[0091] In some embodiments of the present invention, the diagnosing and processing the fault signal includes:

[0092] Determine the number of times a fault signal of a target fault state is received; and when the number is greater than or equal to a preset number threshold corresponding to the target fault state, determine that the diagnostic check result of the fault signal is the target fault state.

[0093] In some embodiments of the present invention, the diagnosing and processing the fault signal includes:

[0094] Determine the duration of receiving a fault signal of a target fault state; when the duration is greater than or equal to a preset duration threshold corresponding to the target fault state, determine that the diagnostic inspection result of the fault signal is the target fault state.

[0095] In some examples, in the diagnostic filtering module, a fault identifier can be configured, one fault corresponds to one fault identifier, the fault identifier value range is 0 to the maximum number of faults supported by the controller, and the filtering benchmark, fault occurrence count threshold and fault recovery count threshold of each fault can be calibrated. The filtering benchmark is time-based filtering or event-based filtering. The fault occurrence count threshold range is 0 to 32767, and the fault recovery count threshold range is -32767 to 0. It is also possible to create a filtering count value, a filtering count value percentage, and a diagnostic inspection result after filtering for each fault.

[0096] For a fault condition:

[0097] When the original fault signal is in a fault state and the filter is started, fault identification is performed. The filter count value records the time when the fault occurs or the number of fault events by adding 1. The filter count value percentage is equal to the filter count value divided by the fault occurrence count threshold. When the filter count value is equal to the fault occurrence count threshold, that is, the fault duration or the number of consecutive fault occurrences exceeds the calibration threshold, the filtering is completed, and the diagnostic check result after filtering is determined to be a fault state.

[0098] For a no-fault condition:

[0099] When the original fault signal is in a fault-free state and the filter is started, fault recovery identification is performed. The filter count value records the time of fault recovery or the number of fault recovery events by counting down by 1. The filter count value percentage is equal to 1 minus the filter count value divided by the fault recovery count threshold. When the filter count value is equal to the fault recovery count threshold, the filtering is completed, and the diagnostic check result after filtering is determined to be fault-free.

[0100] In some embodiments of the present invention, before diagnosing the fault signal, the method further includes:

[0101] In the case that the currently received fault signal is in a fault state and the previously received fault signal is in a non-fault state, the diagnostic processing of the fault signal is performed.

[0102] In some embodiments of the present invention, before diagnosing the fault signal, the method further includes:

[0103] In the case that the currently received fault signal is in a non-fault state and the previously received fault signal is in a fault state, the diagnostic processing of the fault signal is performed.

[0104] In some embodiments of the present invention, before diagnosing the fault signal, the method further includes:

[0105] When the received fault signal indicates that a fault state exists and the diagnostic check result after filtering of the fault signal indicates that there is no fault state, performing the diagnostic processing on the fault signal;

[0106] In some embodiments of the present invention, before diagnosing the fault signal, the method further includes:

[0107] When the received fault signal is in a non-fault state and the diagnostic check result of the fault signal after filtering is that a fault state exists, the diagnostic processing of the fault signal is performed.

[0108] In practical applications, the methods for determining the start of diagnostic filtering are:

[0109] 1. The original fault signal flips from a no-fault state to a fault state, or from a fault state to a no-fault state;

[0110] 2. The original fault signal is in a fault state, but the diagnostic check result after filtering is no fault, or the original fault signal is in a no fault state, but the diagnostic check result after filtering is a fault. In some examples, after starting the filtering, the filtering process is stopped when it is determined that the filtering is completed, and the filtering count value is reset to 0 when the reset condition is met.

[0111] It should be noted that the currently received fault signal and the previously received fault signal are fault signals of the same fault code, that is, the fault signal of the fault code is continuously issued, and the fault signal itself carries a fault state, which can be a fault state or a non-fault state.

[0112] For the case where the original fault signal is reversed:

[0113] In the case of continuously receiving fault signals with the same fault code, if the continuously received fault signals are all in a fault state or a non-fault state, the diagnostic check result can be generated by the counting method as described above, and since the original fault signal received has not changed, the diagnostic check result does not need to be updated, and the most recent diagnostic check result will continue to be maintained.

[0114] If the original fault signal received is flipped, such as from a fault state to a no-fault state, or from a no-fault state to a fault state, indicating that the most recent diagnostic check result may be inaccurate, diagnostic processing of the fault signal can be performed, such as by continuously counting the number of times the fault signal is received and generating a diagnostic result based on the counting result.

[0115] For situations where the fault status of the diagnostic check result and the original fault signal are different:

[0116] If the most recent diagnostic check result shows that a fault state exists, and the fault signals received continuously with the fault code are all fault states, the most recent diagnostic check result will continue to be maintained. If the most recent diagnostic check result shows that there is no fault state, and the fault signals received continuously with the fault code are all fault states, the most recent diagnostic check result will continue to be maintained.

[0117] However, if the most recent diagnostic check result is different from the fault status of the original fault signal received subsequently, such as the most recent diagnostic check result is that a fault status exists while the original fault signal is not in a fault status, or if the most recent diagnostic check result is that there is no fault status while the original fault signal is in a fault status, indicating that the most recent diagnostic check result may be inaccurate, diagnostic processing of the fault signal can be performed, such as by counting the number of times the fault signal is continuously received and generating a diagnostic result based on the counting result.

[0118] In some embodiments of the present invention, it also includes:

[0119] The data identifier associated with the fault code is configured, and when a condition for freezing frame preservation is triggered, a frozen frame including the data identifier associated with the fault code and the associated data is stored. In some examples, the condition for freezing frame preservation may include any of the following:

[0120] 1. OBD (On-Board Diagnostics) confirms the fault;

[0121] 2. When the original fault is in a fault state and the filter count value percentage exceeds the calibration threshold;

[0122] 3. Apply for a stored process freeze frame at any time during the fault monitoring process.

[0123] In actual application, the data identifier associated with the fault code is configured, and then when the freeze frame saving condition is triggered, the freeze frame containing the data identifier associated with the fault code and the associated data is stored. Figure 3 , as follows:

[0124] Configure the public data identifier of the freeze frame and record the vehicle running status, including the data identifier associated with the vehicle driving mode and gear, the data identifier associated with the vehicle speed and vehicle acceleration, the data identifier associated with the vehicle mileage and slope, etc. Traverse and query the public data identifier to obtain the associated data of the public data identifier. At the same time, calibrate the freeze frame two-dimensional array, each row represents a group of freeze frame combinations, and each column in the same row represents the dedicated data identifier bound to the group of freeze frames.

[0125] In some examples, freeze frames may include the calibration and storage of OBD freeze frames, suspicious freeze frames, and process freeze frames, and the types of freeze frames may be expanded as needed later.

[0126] The frame number of the OBD freeze frame is defined as 00. The OBD freeze frame is the diagnostic data of the power system. When the OBD-related suspected fault is converted into a confirmed fault that lights up the MIL (Malfunction Indicator Lamp), the OBD freeze frame is stored once. Create or find the storage entry of the fault that triggers the OBD freeze frame to be saved. The first row of the freeze frame two-dimensional array is marked as the OBD special data identifier. The first row of the two-dimensional array is directly traversed and queried to obtain the OBD data identifier and related data that conform to the ISO-15031 standard definition.

[0127] The frame number of the suspicious freeze frame is defined as 01. When the original fault is in a fault state and the percentage value of the filter count value increases until it exceeds the calibration threshold (the threshold can be set to 50%-100%), the suspicious freeze frame is stored or refreshed once. Configure the group to which each fault belongs, and the group corresponds to the dedicated data identifier bound to the corresponding row in the freeze frame two-dimensional array. Create or find the storage entry of the fault that triggers the saving of the suspicious freeze frame, traverse and query the freeze frame two-dimensional array according to the fault group, obtain the dedicated data identifier and associated data of the group of freeze frames, and then collect the public data identifier and associated data for storage.

[0128] The frame number of the process freeze frame is defined as 02. You can apply for storage, refresh, and delete this freeze frame at any time during the fault monitoring process, even if no fault event occurs at this time. According to the fault group, traverse and query the two-dimensional array of freeze frames, obtain the dedicated data identifier and associated data bound to the group of freeze frames, and then gather the public data identifier and associated data for storage.

[0129] In an embodiment of the present invention, by calibrating the data identifier bound to the freeze frame according to whether the fault is related to OBD or the fault group, the storage of OBD freeze frames, suspicious freeze frames and process freeze frames is realized, the vehicle operation status during the fault process and at the moment of the fault occurrence is reproduced, and relevant data is recorded in order to prevent possible vehicle faults in advance.

[0130] In an embodiment of the present invention, by acquiring a fault signal of a module in a vehicle, and when the fault signal triggers an associated suppression condition, the fault signal is suppressed, thereby suppressing some fault signals in the vehicle. There is no need to diagnose all fault signals and store fault information, thereby improving diagnostic efficiency and reducing storage space usage.

[0131] It should be noted that, for the sake of simplicity, the method embodiments are described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0132] Some embodiments of the present invention provide a vehicle fault processing device, wherein the device is specifically used for:

[0133] Obtain fault signals from modules in the vehicle;

[0134] In the case where the fault signal triggers an associated suppression condition, suppression processing is performed on the fault signal.

[0135] In some embodiments of the present invention, after obtaining the fault signal of the module in the vehicle, it is also used to:

[0136] determining a diagnostic suppression identifier associated with the fault signal;

[0137] In case the diagnostic suppression identifier is in an activated state, it is determined that the fault signal triggers an associated suppression condition.

[0138] In some embodiments of the present invention, after determining the diagnostic suppression identifier associated with the fault signal, the method is further configured to:

[0139] determining a plurality of fault codes associated with the diagnostic suppression identifier;

[0140] When a diagnostic check result corresponding to any target fault code among the plurality of fault codes indicates that a fault state exists, it is determined that the diagnosis inhibition identifier is in an activated state.

[0141] In some embodiments of the present invention, after determining the plurality of fault codes associated with the diagnostic suppression identifier, the method is further configured to:

[0142] Acquire a two-dimensional matrix; wherein the two-dimensional matrix stores a plurality of candidate diagnostic suppression identifiers and diagnostic inspection results corresponding to a plurality of fault codes associated with each candidate diagnostic suppression identifier;

[0143] By using the two-dimensional matrix, it is detected whether any target fault code among the multiple fault codes associated with the diagnosis suppression identifier has a diagnostic check result indicating that a fault state exists.

[0144] In some embodiments of the present invention, it is also used for:

[0145] In the case where the fault signal does not trigger an associated suppression condition, performing diagnostic processing on the fault signal;

[0146] The two-dimensional matrix is ​​updated according to the diagnosis and inspection result of the fault signal.

[0147] In some embodiments of the present invention, it is also used for:

[0148] In the case where the fault signal does not trigger an associated suppression condition, performing diagnostic processing on the fault signal;

[0149] In some embodiments of the present invention, the diagnosing and processing the fault signal includes:

[0150] determining a number of times a fault signal of a target fault state is received;

[0151] When the number is greater than or equal to a preset number threshold corresponding to the target fault state, determining that the diagnostic inspection result of the fault signal is the target fault state;

[0152] Alternatively, determining a duration of receiving a fault signal of a target fault state;

[0153] In a case where the duration is greater than or equal to a preset duration threshold corresponding to the target fault state, it is determined that the diagnostic check result of the fault signal is the target fault state.

[0154] In some embodiments of the present invention, before the fault signal is diagnosed and processed, the method is further used to:

[0155] When the currently received fault signal is in a fault state and the previously received fault signal is in a non-fault state, performing the diagnostic processing on the fault signal;

[0156] Alternatively, when the currently received fault signal is in a non-fault state and the previously received fault signal is in a fault state, the diagnostic processing of the fault signal is performed.

[0157] In some embodiments of the present invention, before the fault signal is diagnosed and processed, the method is further used to:

[0158] When the received fault signal indicates that a fault state exists and the diagnostic check result after filtering of the fault signal indicates that there is no fault state, performing the diagnostic processing on the fault signal;

[0159] Alternatively, when the received fault signal is in a non-fault state and the diagnostic check result of the fault signal after filtering is that a fault state exists, the diagnostic processing of the fault signal is performed.

[0160] In some embodiments of the present invention, it is also used for:

[0161] The data identifier associated with the fault code is configured, and when the condition for freezing the frame is triggered, the frozen frame containing the data identifier associated with the fault code and the associated data is stored. Some embodiments of the present invention also provide a computer program including a processor, a memory, and a computer program stored in the memory and capable of running on the processor, and when the computer program is executed by the processor, the method for handling vehicle faults as described above is implemented.

[0162] Some embodiments of the present invention also provide an electronic device, which may include a processor, a memory, and a computer program stored in the memory and capable of running on the processor, and when the computer program is executed by the processor, the above vehicle fault handling method is implemented.

[0163] Some embodiments of the present invention further provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the above vehicle fault processing method is implemented.

[0164] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0165] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0166] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0167] Those skilled in the art will appreciate that the embodiments of the present invention may be provided as methods, devices, or computer program products. Therefore, the embodiments of the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0168] The embodiments of the present invention are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0169] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0170] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0171] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0172] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the above elements.

[0173] The above provides a detailed introduction to a vehicle fault handling method, device, vehicle, electronic device and medium. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for a person skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A method for handling vehicle failure, characterized in that: The method comprises: Obtain fault signals from modules in the vehicle; In the case where the fault signal triggers an associated suppression condition, suppression processing is performed on the fault signal.

2. The method according to claim 1, characterized in that After obtaining the fault signal of the module in the vehicle, the method further includes: determining a diagnostic suppression identifier associated with the fault signal; In case the diagnostic suppression identifier is in an activated state, it is determined that the fault signal triggers an associated suppression condition.

3. The method according to claim 2, characterized in that After determining the diagnostic suppression identifier associated with the fault signal, the method further includes: determining a plurality of fault codes associated with the diagnostic suppression identifier; When a diagnostic check result corresponding to any target fault code among the plurality of fault codes indicates that a fault state exists, it is determined that the diagnosis inhibition identifier is in an activated state.

4. The method according to claim 3, characterized in that After determining the plurality of fault codes associated with the diagnostic suppression identifier, the method further includes: Acquire a two-dimensional matrix; wherein the two-dimensional matrix stores a plurality of candidate diagnostic suppression identifiers and diagnostic inspection results corresponding to a plurality of fault codes associated with each candidate diagnostic suppression identifier; By using the two-dimensional matrix, it is detected whether any target fault code among the multiple fault codes associated with the diagnosis suppression identifier has a diagnostic check result indicating that a fault state exists.

5. The method according to claim 4, characterized in that Also includes: In the case where the fault signal does not trigger an associated suppression condition, performing diagnostic processing on the fault signal; The two-dimensional matrix is ​​updated according to the diagnosis and inspection result of the fault signal.

6. The method according to claim 1, characterized in that Also includes: In the case where the fault signal does not trigger an associated suppression condition, performing diagnostic processing on the fault signal; The diagnosing and processing the fault signal includes: determining a number of times a fault signal of a target fault state is received; When the number is greater than or equal to a preset number threshold corresponding to the target fault state, determining that the diagnostic inspection result of the fault signal is the target fault state; Alternatively, determining a duration of receiving a fault signal of a target fault state; In a case where the duration is greater than or equal to a preset duration threshold corresponding to the target fault state, it is determined that the diagnostic check result of the fault signal is the target fault state.

7. The method according to claim 6, characterized in that Before the fault signal is diagnosed and processed, the method further includes: When the currently received fault signal is in a fault state and the previously received fault signal is in a non-fault state, performing the diagnostic processing on the fault signal; Alternatively, when the currently received fault signal is in a non-fault state and the previously received fault signal is in a fault state, the diagnostic processing of the fault signal is performed.

8. The method according to claim 6, characterized in that Before the fault signal is diagnosed and processed, the method further includes: When the received fault signal indicates that a fault state exists and the diagnostic check result after filtering of the fault signal indicates that there is no fault state, performing the diagnostic processing on the fault signal; Alternatively, when the received fault signal is in a non-fault state and the diagnostic check result of the fault signal after filtering is that a fault state exists, the diagnostic processing of the fault signal is performed.

9. The method according to claim 1, characterized in that: Also includes: The data identifier associated with the fault code is configured, and when the condition for freezing the frame is triggered, the freeze frame including the data identifier associated with the fault code and the associated data is stored.

10. A vehicle fault handling device, characterized in that: The device is used for: Obtain fault signals from modules in the vehicle; In the case where the fault signal triggers an associated suppression condition, suppression processing is performed on the fault signal.

11. A vehicle, characterized in that: The invention comprises a processor, a memory and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the vehicle fault processing method according to any one of claims 1 to 9 when executed by the processor.

12. An electronic device, characterized in that: The invention comprises a processor, a memory and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the vehicle fault processing method according to any one of claims 1 to 9 when executed by the processor.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for handling a vehicle fault according to any one of claims 1 to 9 is implemented.

Images