Vehicle fault processing method and device

Abstract

The invention discloses a vehicle fault processing method and device. The vehicle fault processing method comprises the following steps: in a current fault processing period, obtaining current detection information corresponding to each fault code according to a detection mode corresponding to each fault code; if the current detection information corresponding to the fault code is greater than the corresponding threshold information, taking the fault code as a target fault code; executing a target processing mode corresponding to the target fault code; if the target fault code is not in the current fault table, storing the target fault code, the target detection information corresponding to the target fault code and the fault information into the current fault table; and if the target fault code is in the historical fault table, determining whether to store the target fault code determined by the current fault processing period into the historical fault table according to the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table. According to the technical scheme of the invention, vehicle fault processing can be carried out better.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle fault processing, and in particular to a vehicle fault processing method and device. Background Art

[0002] With the rapid development and increasing perfection of energy storage equipment, new energy vehicles are developing rapidly. The safety of new energy vehicles is particularly important. Therefore, it is necessary to perform fault detection on the vehicle and implement corresponding measures when a fault is detected.

[0003] However, the existing vehicle controller can only perform fault detection and determine the corresponding fault handling measures according to the fault type. If the fault is serious and needs to be repaired, it is necessary to test various components of the vehicle during the repair to determine how to repair it. This is not conducive to vehicle fault handling and cannot effectively handle vehicle faults. Summary of the Invention

[0004] The present invention provides a vehicle fault handling method and device to solve the problem that vehicle fault handling cannot be performed well.

[0005] According to one aspect of the present invention, a vehicle fault handling method is provided, the vehicle fault handling method comprising:

[0006] In a current fault handling cycle, current detection information corresponding to each fault code is obtained according to the detection method corresponding to each fault code; wherein each detection information corresponds to a threshold information, and each fault code corresponds to a fault information; the fault information includes at least a fault level and a fault name;

[0007] For each fault code, if the current detection information corresponding to the fault code is greater than the corresponding threshold information, the fault code is used as a target fault code, and the current detection information corresponding to the target fault code is used as the target detection information;

[0008] Executing a target processing method corresponding to the target fault code;

[0009] If the target fault code is not in the current fault table, storing the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code into the current fault table; wherein the current fault table is stored in a first memory of the vehicle;

[0010] If the target fault code is in the historical fault table, determine whether to store the target fault code determined in the current fault processing cycle into the historical fault table based on the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table; wherein, the historical fault table is stored in the second memory of the vehicle.

[0011] Optionally, if the target fault code is in a historical fault table, determining whether to store the target fault code determined in the current fault processing cycle in the historical fault table according to the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table includes:

[0012] If the target fault code is in the historical fault table, and the difference between the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table is greater than a preset time length, the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code are stored in the historical fault table;

[0013] If the target fault code is in the historical fault table, and the difference between the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table is less than or equal to the preset duration, the target fault code determined by the current fault processing cycle will not be stored in the historical fault table.

[0014] Optionally, the method comprises:

[0015] If the target fault code is not in the historical fault table, the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code and the fault time corresponding to the target fault code are stored in the historical fault table.

[0016] Optionally, storing the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code into the current fault table includes:

[0017] Determine the target storage address according to the number of faults of the fault codes stored in the current fault table;

[0018] According to the target storage address, the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code are stored in the current fault table.

[0019] Optionally, storing the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code into the historical fault table includes:

[0020] Determining a maximum storage address of the historical fault table according to the storage space of the historical fault table;

[0021] Determine the target storage first address according to the number or address of the fault codes stored in the historical fault table;

[0022] If the target storage first address is greater than the maximum storage address, subtracting the maximum storage address from the target storage first address to obtain a final storage address;

[0023] Starting from the final storage address, the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code are stored in the historical fault table.

[0024] Optionally, in the current fault handling cycle, obtaining detection information corresponding to each fault code according to the detection method corresponding to each fault code includes:

[0025] In the current fault handling cycle, the detection method corresponding to each fault code is determined according to a preset correspondence relationship, and the current detection information corresponding to each fault code is obtained according to the detection method corresponding to each fault code; wherein the preset correspondence relationship is the correspondence between the fault code, the fault level, the detection method, and the handling method;

[0026] The executing the target processing method corresponding to the target fault code includes:

[0027] A target processing method corresponding to the target fault code is determined according to the target fault code and the preset corresponding relationship, and the target processing method corresponding to the target fault code is executed.

[0028] Optionally, determining a target processing method corresponding to the target fault code according to the preset correspondence between the target fault code and the preset correspondence includes:

[0029] A target fault level corresponding to the target fault code is determined based on the target fault code and the preset corresponding relationship, and a target processing method corresponding to the target fault code is determined based on the target fault level or the target fault code; wherein, when the target fault level is level one, the motor that drives the vehicle is controlled to stop running; when the target fault level is level two, the speed of the motor is reduced; when the target fault level is level three, a fault prompt message is issued.

[0030] Optionally, the method further includes:

[0031] When the vehicle is powered on, the historical fault table in the second memory is read and the historical fault table is sent to the first memory.

[0032] Optionally, the method further includes:

[0033] For each fault code, if the detection information corresponding to the fault code is less than or equal to the corresponding threshold information, and the fault code is stored in the current fault table, the fault code is deleted from the current fault table.

[0034] Optionally, for each fault code, if the current detection information corresponding to the fault code is greater than the corresponding threshold information, then after using the fault code as the target fault code, the method further includes:

[0035] The units digit of the target fault code is used as a first target flashing number of the first indicator light, and the tens digit of the target fault code is used as a second target flashing number of the second indicator light; wherein the first indicator light and the second indicator light have different luminous colors;

[0036] The first indicator light is controlled to emit light according to the first target flashing number, and the second indicator light is controlled to emit light according to the second target flashing number.

[0037] According to another aspect of the present invention, a vehicle fault processing device is provided, which is used to execute the vehicle fault processing method according to any embodiment of the present invention;

[0038] The vehicle fault handling device includes:

[0039] an acquisition module, configured to acquire, in each fault processing cycle, detection information corresponding to each fault code according to the detection method corresponding to each fault code; wherein each detection information corresponds to a threshold value, and each fault code corresponds to a fault information; the fault information at least includes a fault level and a fault name;

[0040] a fault determination module, configured to, for each fault code, determine, if the detection information corresponding to the fault code is greater than the corresponding threshold information, take the fault code as a target fault code and the detection information corresponding to the target fault code as target detection information;

[0041] A fault processing module, configured to execute a target processing method corresponding to the target fault code;

[0042] a first storage control module, configured to store the target fault code, target detection information corresponding to the target fault code, and fault information corresponding to the target fault code into the current fault table if the target fault code is not in the current fault table; wherein the current fault table is stored in a first memory of the vehicle;

[0043] A second storage control module is used to determine whether to store the target fault code in the historical fault table based on the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table if the target fault code is in the historical fault table; wherein, the historical fault table is stored in the second memory of the vehicle.

[0044] The technical solution of the embodiment of the present invention is that in the current fault processing cycle, the current detection information corresponding to each fault code is obtained according to the detection method corresponding to each fault code. If the current detection information is greater than the corresponding threshold information, the fault code corresponding to the current detection information is the target fault code, and the current detection information corresponding to the target fault code is used as the target detection information, and the target processing method corresponding to the target fault code is executed to facilitate fault repair. If the target fault code is not in the current fault table, the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code are stored in the current fault table. The vehicle controller can transmit the current fault table to the host computer, so that when the vehicle itself cannot repair the fault, the maintenance personnel can perform repairs based on the current fault table. If the target fault code is in the historical fault table, the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table determine whether to store the target fault code determined in the current fault processing cycle in the historical fault table. For example, if the current fault time is far away from the historical fault time, it may be that the fault has recurred after the fault has been resolved. In this case, in the current fault processing cycle, the target fault code is stored in the historical fault table again, so that if the fault recurs, fault recovery can be performed again. The vehicle controller can transmit the historical fault table to the host computer, so that maintenance personnel can perform repairs based on the historical fault table. In this way, when repairing the vehicle, there is no need to conduct inspections, and repairs can be carried out directly based on the current fault table or the historical fault table, which facilitates better vehicle fault handling.

[0045] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0047] Figure 1 This is a flow chart of a vehicle fault handling method provided by an embodiment of the present invention;

[0048] Figure 2 is a flow chart of another vehicle fault handling method provided by an embodiment of the present invention;

[0049] Figure 3 This is a flow chart of another vehicle fault handling method provided by an embodiment of the present invention;

[0050] Figure 4 It is a structural schematic diagram of a vehicle fault handling device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0051] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0052] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0053] An embodiment of the present invention provides a vehicle fault handling method. The vehicle may include an electric vehicle. The vehicle fault handling method may be executed by a vehicle fault handling device. The vehicle controller includes the vehicle fault handling device, or the vehicle controller is the vehicle fault handling device. The vehicle controller is a controller that controls the operation of a motor.

[0054] Figure 1 This is a flow chart of a vehicle fault handling method provided by an embodiment of the present invention, with reference to Figure 1 , vehicle troubleshooting methods include:

[0055] S101. In the current fault handling cycle, obtain current detection information corresponding to each fault code according to the detection method corresponding to each fault code; wherein each detection information corresponds to a threshold information, and each fault code corresponds to a fault information; the fault information includes at least a fault level and a fault name.

[0056] After the vehicle is powered on and completes the power-on self-test, the vehicle fault handling device begins periodically executing the fault handling cycle. Each fault code corresponds to a detection method, which may include detecting the voltage of the detected device, detecting the current of the detected device, detecting the temperature of the detected device, and detecting the pressure of the detected device. The detected device is a device, circuit, or line in the vehicle, such as a motor, tire, power conversion circuit, communication line, DC bus, or power supply circuit, etc., which is not limited in this embodiment. The detection information may include voltage values, temperature values, current values, power values, or pressure values, such as at least one of voltage values, temperature values, current values, power values, and pressure values. Current detection information includes current voltage values, current temperature values, current current values, current power values, or current pressure values. The fault name may be overvoltage, overcurrent, or overtemperature, such as at least one of overvoltage, overcurrent, and overtemperature. Each detection information corresponds to a threshold value. For example, if the detection information is a voltage value, the threshold value information is a threshold voltage.

[0057] Specifically, by obtaining the current detection information corresponding to each fault code according to the detection method corresponding to each fault code in the current fault handling cycle, it is possible to determine whether the detected component corresponding to the fault code is faulty based on the current detection information. Each fault handling cycle can be executed according to the steps of the current fault handling cycle, so that in each fault handling cycle, it is possible to determine whether the detected component is faulty and execute the corresponding handling method.

[0058] S102 . For each fault code, if the current detection information corresponding to the fault code is greater than the corresponding threshold information, the fault code is used as a target fault code, and the current detection information corresponding to the target fault code is used as the target detection information.

[0059] Specifically, during the current fault handling cycle, the current detection information corresponding to each fault code is compared with the threshold information corresponding to the detection information. If the current detection information corresponding to a fault code is greater than the corresponding threshold information, the fault code is designated as the target fault code, and the current detection information corresponding to the target fault code is designated as the target detection information. That is, the current detection information greater than the threshold information is designated as the target detection information, i.e., the target detection information is the specific fault value.

[0060] For example, in the nth fault processing cycle (current fault processing cycle), the current detection information corresponding to the first fault code is compared with the threshold information corresponding to the detection information. If the current detection information corresponding to the first fault code is greater than the corresponding threshold information, the first fault code is determined to be the target fault code. ... The current detection information corresponding to the mth fault code is compared with the threshold information corresponding to the detection information. If the current detection information corresponding to the mth fault code is greater than the corresponding threshold information, the mth fault code is determined to be the target fault code. Where n is a positive integer and m is an integer greater than 1.

[0061] S103: Execute a target processing method corresponding to the target fault code.

[0062] Specifically, each fault code corresponds to a fault level, and each fault level corresponds to a handling method. That is, each fault code corresponds to a handling method. The handling method corresponding to the target fault code is the target handling method. Based on the target fault code, the corresponding target handling method can be determined and executed. This way, during each fault handling cycle, the corresponding handling method can be executed when a vehicle fault occurs, facilitating fault repair. For example, if the fault corresponding to the target fault code is motor overvoltage, the target handling method could be to reduce the voltage input to the motor to repair the fault.

[0063] S104. If the target fault code is not in the current fault table, the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code are stored in the current fault table; wherein the current fault table is stored in a first memory of the vehicle.

[0064] Among them, the first memory is a random access memory (RAM), which is volatile and will be lost when the power is off. Therefore, the data in the current fault table is lost when the vehicle is powered off. When the vehicle is powered on, the data is stored again. That is, the current fault table is the fault table stored in the first memory when the current vehicle is powered on.

[0065] Specifically, during the current fault handling cycle, if the target fault code is not in the current fault table, the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code determined during the current fault handling cycle are stored in the current fault table. This allows the target fault code and the information corresponding to the target fault code to be stored in the current fault table. The vehicle controller can transmit the current fault table to a host computer, facilitating maintenance personnel to perform repairs based on the current fault table. After the target detection information is transmitted to the host computer, subsequent fault analysis can be performed based on the target detection information.

[0066] For example, Table 1 is a current fault table provided in an embodiment of the present invention. As shown in Table 1, the current fault table includes target fault codes, target detection information corresponding to the target fault codes, and fault information (fault name and fault level) corresponding to the target fault codes. N01, N02, and N03 represent fault codes (target fault codes). In other embodiments, the fault codes may also be 01, 02, 03, etc., which are not limited in this embodiment.

[0067] Table 1 A current fault table provided by an embodiment of the present invention

[0068] NO1. Fault name NO1. Fault level NO1. Target detection information NO2. Fault name NO2. Fault level NO2. Target detection information NO3. Fault name NO3. Fault level NO3. Target detection information ......

[0069] S105. If the target fault code is in the historical fault table, determine whether to store the target fault code determined in the current fault processing cycle in the historical fault table based on the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table; wherein the historical fault table is stored in the second memory of the vehicle.

[0070] Among them, the second memory is Flash Memory, which is a non-volatile memory (data is not lost after power failure). Therefore, the data in the historical fault table can be maintained without loss during power failure, and the data in the historical fault table are all fault data since the vehicle left the factory. The current fault time corresponding to the target fault code is the time corresponding to when the fault code is determined to be the target fault code. The historical fault time corresponding to the target fault code in the historical fault table is the fault time corresponding to the target fault code in the historical fault table. For example, the target fault code is 01, and the time when the fault code 01 is determined to be the target fault code is t1, that is, the current fault time is t1, and the fault code 01 has been stored in the historical fault table, then the fault time t2 corresponding to the fault code 01 in the historical fault table is the historical fault time.

[0071] Specifically, during the current fault handling cycle, if the target fault code is already stored in the historical fault table, the current fault time corresponding to the target fault code is compared with the historical fault time corresponding to the target fault code in the historical fault table. Based on the comparison result, it is determined whether to store the target fault code determined for the current fault handling cycle in the historical fault table, that is, whether to store the target fault code again in the historical fault table. For example, if the current fault time is close to the historical fault time, the target fault code may not be stored again in the historical fault table during the current fault handling cycle, thereby avoiding the continuous storage of unhandled faults in the historical fault table and the waste of storage space due to multiple storage in a short period of time. If the current fault time is far from the historical fault time, it may be that the fault has re-occurred after being resolved. In this case, the target fault code is stored again in the historical fault table during the current fault handling cycle to facilitate fault recovery if the fault re-occurs. The vehicle controller can transmit the historical fault table to a host computer to facilitate maintenance personnel to perform repairs based on the historical fault table.

[0072] Optionally, in the current fault handling cycle, if a target fault code has been stored in the historical fault table, and the number of the target fault codes stored in the historical fault table is greater than 1, the historical fault time corresponding to the latest time of all historical fault times corresponding to the target fault code is compared with the current fault time, and whether to store the target fault code in the historical fault table is determined based on the comparison result.

[0073] For example, Table 2 is a historical fault table provided by an embodiment of the present invention. As shown in Table 2, the historical fault table includes target fault codes, target detection information corresponding to the target fault codes, fault information corresponding to the target fault codes (fault name and fault level), and fault time. N01, N02, and N03 represent fault codes (target fault codes).

[0074] Table 2 A historical fault table provided by an embodiment of the present invention

[0075] NO1. Fault name NO1. Fault level NO1. Target detection information NO1. Failure time NO2. Fault name NO2. Fault level NO2. Target detection information NO2. Failure time NO3. Fault name NO3. Fault level NO3. Target detection information NO3. Failure time ......

[0076] The technical solution of this embodiment is to obtain the current detection information corresponding to each fault code according to the detection method corresponding to each fault code in the current fault processing cycle. If the current detection information is greater than the corresponding threshold information, the fault code corresponding to the current detection information is the target fault code, and the current detection information corresponding to the target fault code is used as the target detection information, and the target processing method corresponding to the target fault code is executed to facilitate fault repair. If the target fault code is not in the current fault table, the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code are stored in the current fault table. The vehicle controller can transmit the current fault table to the host computer, so that when the vehicle itself cannot repair the fault, maintenance personnel can perform repairs based on the current fault table. If the target fault code is in the historical fault table, the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table determine whether to store the target fault code determined in the current fault processing cycle in the historical fault table. For example, if the current fault time is far away from the historical fault time, it may be that the fault has recurred after the fault was resolved. In this case, the target fault code is stored in the historical fault table again in the current fault processing cycle to facilitate fault recovery if the fault recurs. The vehicle controller can transmit the historical fault table to the host computer, so that maintenance personnel can perform repairs based on the historical fault table. In this way, when repairing the vehicle, there is no need to conduct inspections, and repairs can be carried out directly based on the current fault table or the historical fault table, which facilitates better vehicle fault handling.

[0077] On the basis of the above technical solutions, Figure 2 is a flowchart of another vehicle fault processing method provided by an embodiment of the present invention. Figure 2 , vehicle troubleshooting methods include:

[0078] S201. In the current fault processing cycle, obtain current detection information corresponding to each fault code according to the detection method corresponding to each fault code; wherein each detection information corresponds to a threshold information, and each fault code corresponds to a fault information; the fault information includes at least a fault level and a fault name.

[0079] S202 . For each fault code, if the current detection information corresponding to the fault code is greater than the corresponding threshold information, the fault code is used as a target fault code, and the current detection information corresponding to the target fault code is used as the target detection information.

[0080] S203: Execute a target processing method corresponding to the target fault code.

[0081] S204. If the target fault code is not in the current fault table, the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code are stored in the current fault table; wherein the current fault table is stored in a first memory of the vehicle.

[0082] S205: Determine whether the target fault code is in the historical fault table. If so, execute step S206; if not, execute step S209.

[0083] Specifically, the content in the historical fault table is read to determine whether the target fault code determined in the current fault processing cycle has been stored in the historical fault table.

[0084] S206. Determine whether the difference between the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table is greater than a preset time length. If so, execute step S207; if not, execute step S208.

[0085] Specifically, if the target fault code determined in the current fault handling cycle is already stored in the historical fault table, the current fault time corresponding to the target fault code determined in the current fault handling cycle is subtracted from the historical fault time corresponding to the target fault code in the historical fault table. That is, the difference between the current fault time and the historical fault time is compared with the preset time duration. For example, the preset time duration can be any time duration between one hour and three hours, and this embodiment is not limited thereto.

[0086] S207 : Store the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code into a historical fault table.

[0087] Specifically, if the difference between the current fault time and the historical fault time is greater than a preset time, it is determined that the current fault time is far away from the historical fault time, which means that the fault may have recurred after being resolved. In this case, the target fault code is stored in the historical fault table again during the current fault handling cycle to facilitate fault recovery if the fault reoccurs. The vehicle controller can transmit the historical fault table to the host computer to facilitate maintenance personnel to perform repairs based on the historical fault table.

[0088] S208: Do not store the target fault code determined in the current fault processing cycle in the historical fault table.

[0089] Specifically, when the difference between the current fault time and the historical fault time is less than or equal to the preset time length, it indicates that the current fault time is close to the historical fault time. In the current fault processing cycle, the target fault code may not be stored in the historical fault table again, so as to avoid storing unprocessed faults in the historical fault table all the time, and avoid multiple storage in a short period of time, which wastes storage space.

[0090] S209 , storing the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code into a historical fault table.

[0091] Specifically, if the target fault code determined in the current fault handling cycle is not stored in the historical fault table, the target fault code determined in the current fault handling cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code are stored in the historical fault table, so as to facilitate maintenance personnel to perform repairs according to the historical fault table and better handle vehicle faults.

[0092] On the basis of the above technical solutions, optionally, storing the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code into the current fault table includes:

[0093] Step a1: Determine the target storage address according to the number of faults of the fault codes stored in the current fault table.

[0094] Specifically, based on the number of faults in the fault codes already stored in the current fault table, the number of bits of data already stored in the current fault table can be determined, so that the number of bits of the already stored data can be added by one to obtain the target storage address, which is the starting address of the target fault code to be stored, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code.

[0095] Step a2: store the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code into the current fault table according to the target storage address.

[0096] Specifically, the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code are stored starting from the target storage address, that is, all data that need to be stored are stored starting with the target storage address as the first address, so that the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code are stored in the current fault table.

[0097] Optionally, storing the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code into a historical fault table includes:

[0098] Step b1: Determine the maximum storage address of the historical fault table according to the storage space of the historical fault table.

[0099] Specifically, when establishing the historical fault table, the storage space of the historical fault table, that is, the number of data bits that can be stored, can be set. Therefore, the maximum storage address of the historical fault table can be determined based on the storage space of the historical fault table.

[0100] Step b2: Determine the target storage first address according to the number or address of the fault codes stored in the historical fault table.

[0101] Specifically, by reading the historical fault table and determining the number of fault codes already stored in the historical fault table, the number of data already stored in the historical fault table can be determined, and the number of bits of the already stored data can be increased by one to obtain the target storage starting address. Alternatively, the historical fault table can be read to determine the end address of the data already stored in the historical fault table, that is, the end address of all data in the historical fault table, and the end address of all data in the historical fault table can be increased by one to obtain the target storage starting address.

[0102] Step b3: If the target storage first address is greater than the maximum storage address, subtract the maximum storage address from the target storage first address to obtain the final storage address.

[0103] Specifically, if the target storage first address is less than or equal to the maximum storage address, the target fault code, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code determined in the current fault processing cycle are stored starting from the target storage first address. If the target storage first address is greater than the maximum storage address, the maximum storage address is subtracted from the target storage first address to obtain the final storage address.

[0104] Step b4: Starting from the final storage address, the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code are stored in the historical fault table.

[0105] Specifically, the final storage address is the first address, and the target fault code, target detection information corresponding to the target fault code, fault information corresponding to the target fault code, and fault time corresponding to the target fault code determined in the current fault processing cycle are stored starting from the final storage address.

[0106] For example, if the maximum storage address of the historical fault table is 15, and the target storage first address determined according to the number or address of the fault codes stored in the historical fault table is 20, which is greater than the maximum storage address of the historical fault table, then the target storage first address 20 is subtracted from the maximum storage address 15 to obtain the final storage address 5. Starting from the final storage address 5, the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code are stored in the historical fault table.

[0107] In this way, the earliest data in the historical fault table can be overwritten, and the data of the latest (latest) target fault code up to the current fault processing cycle can be written into the historical fault table. There is no need to shift the data in the historical fault table before writing the target fault code determined by the current fault processing cycle, which can reduce the number of operations on the second memory (flash memory) and facilitate operation.

[0108] Based on the above technical solutions, optionally, in the current fault handling cycle, the detection information corresponding to each fault code is obtained according to the detection method corresponding to each fault code, including:

[0109] During the current fault handling cycle, the detection method corresponding to each fault code is determined based on a preset correspondence, and the current detection information corresponding to each fault code is obtained based on the detection method corresponding to each fault code. The preset correspondence is the correspondence between the fault code, fault level, detection method, and handling method. The fault levels corresponding to different fault codes can be the same or different.

[0110] Specifically, the preset correspondence relationship may be stored in the first memory or the second memory in the form of a table. In the current fault processing cycle, for each fault code, the fault code may be substituted into the preset correspondence relationship, the detection method corresponding to the fault code may be determined, and the current detection information corresponding to the fault code may be obtained according to the determined detection method.

[0111] For example, Table 3 is a schematic table of preset correspondences provided in an embodiment of the present invention. As shown in Table 3, each fault code corresponds to a fault level, each fault code corresponds to a detection method, and each fault code corresponds to a processing method. By substituting the fault code into the preset correspondence, the detection method corresponding to the fault code can be determined.

[0112] Table 3 Schematic table of preset correspondences provided by an embodiment of the present invention

[0113]

[0114] For example, as shown in Table 3, for example, the detection method corresponding to fault code 01 is to detect the battery current, the detection method corresponding to fault code 02 is to detect the motor temperature, and the detection method corresponding to fault code 03 is to detect the tire pressure. Table 3 is only an example, and the specific detection method can be set according to actual needs and is not limited here.

[0115] Optionally, executing a target processing method corresponding to a target fault code includes:

[0116] The target processing method corresponding to the target fault code is determined according to the target fault code and the preset corresponding relationship, and the target processing method corresponding to the target fault code is executed.

[0117] Specifically, by substituting the target fault code into the preset corresponding relationship, the corresponding processing method can be determined, namely the target processing method. By executing the target processing method, the fault can be repaired. For example, as shown in Table 3, the detection method corresponding to fault code 01 is to detect the battery current. In the current fault processing cycle, if the current detection information (current current) is greater than the corresponding threshold information (current threshold), the motor driving the vehicle is controlled to stop running to avoid safety hazards caused by battery short circuit. The detection method corresponding to fault code 02 is to detect the temperature of the motor. If the current detection information (current temperature) is greater than the corresponding threshold information (temperature threshold), the motor speed is reduced, and the motor power can also be reduced to reduce the temperature of the motor. The detection method corresponding to fault code 03 is to detect tire pressure. If the current detection information (current tire pressure) is greater than the corresponding threshold information (tire pressure threshold), a fault prompt message is issued, prompting the driver to check or refill tires, etc. Table 3 is only an example. The specific detection method and processing method can be set according to actual needs and are not limited here.

[0118] On the basis of the above technical solution, optionally, determining a target processing method corresponding to the target fault code according to a preset correspondence between the target fault code and the preset correspondence includes:

[0119] The target fault level corresponding to the target fault code is determined based on the target fault code and the preset correspondence, and the target processing method corresponding to the target fault code is determined based on the target fault level or the target fault code; among which, when the target fault level is level one, the motor that drives the vehicle is controlled to stop running; when the target fault level is level two, the speed of the motor is reduced; when the target fault level is level three, a fault prompt message is issued.

[0120] Specifically, each fault code corresponds to a fault level. Different fault codes may correspond to the same fault level, but different fault levels may correspond to different processing methods. The target fault code can be substituted into the preset corresponding relationship to determine the target fault level corresponding to the target fault code, and then the target processing method can be determined based on the target fault level. For example, as shown in Table 3, for example, the target fault level corresponding to fault code 01 is level one. In the current fault processing cycle, if the current detection information is greater than the corresponding threshold information, the motor driving the vehicle is controlled to stop running. The target fault level corresponding to fault code 02 is level two. If the current detection information is greater than the corresponding threshold information, the speed of the motor is reduced, and the power of the motor can also be reduced. The target fault level corresponding to fault code 03 is level three. If the current detection information is greater than the corresponding threshold information, a fault prompt message is issued to prompt the driver to perform maintenance, etc.

[0121] On the basis of the above technical solutions, Figure 3 This is a flowchart of another vehicle fault processing method provided by an embodiment of the present invention. Optionally, refer to Figure 3 , vehicle troubleshooting methods include:

[0122] S301. When the vehicle is powered on, read the historical fault table in the second memory, and send the historical fault table to the first memory.

[0123] Specifically, the first memory is a random access memory (RAM), a high-speed storage device. Each time the vehicle is powered on, the historical fault table in the second memory is read and sent to the first memory. This table can then be transferred from the first memory to a host computer or vehicle controller, facilitating rapid access to the historical fault table from the first memory.

[0124] S302. In the current fault processing cycle, obtain current detection information corresponding to each fault code according to the detection method corresponding to each fault code; wherein each detection information corresponds to a threshold information, and each fault code corresponds to a fault information; the fault information includes at least a fault level and a fault name.

[0125] S303 . For each fault code, if the current detection information corresponding to the fault code is greater than the corresponding threshold information, the fault code is used as a target fault code, and the current detection information corresponding to the target fault code is used as the target detection information.

[0126] S304: Execute the target processing method corresponding to the target fault code.

[0127] S305. If the target fault code is not in the current fault table, the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code are stored in the current fault table; wherein the current fault table is stored in a first memory of the vehicle.

[0128] S306: Determine whether the target fault code is in the historical fault table. If so, execute step S307; if not, execute step S310.

[0129] S307. Determine whether the difference between the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table is greater than a preset time length. If so, execute step S308; if not, execute step S309.

[0130] S308 : Store the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code into a historical fault table.

[0131] S309: Do not store the target fault code determined in the current fault processing cycle in the historical fault table.

[0132] S310 , storing the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code into a historical fault table.

[0133] S311. For each fault code, if the detection information corresponding to the fault code is less than or equal to the corresponding threshold information, and the fault code is stored in the current fault table, then the fault code is deleted from the current fault table.

[0134] Specifically, if the detection information corresponding to the fault code is less than or equal to the corresponding threshold information, and the fault code is stored in the current fault table, it indicates that the detected device corresponding to the fault code failed in the previous fault handling cycle, and now the fault disappears, then the fault code can be deleted from the current fault table, which can save storage space and avoid continuous fault alarms, thereby achieving better fault handling.

[0135] Based on the above technical solutions, optionally, for each fault code, if the current detection information corresponding to the fault code is greater than the corresponding threshold information, then after the fault code is used as the target fault code, the vehicle fault handling method further includes:

[0136] Step c1: using the units digit of the target fault code as the first target flashing number of the first indicator light, and using the tens digit of the target fault code as the second target flashing number of the second indicator light; wherein the first indicator light and the second indicator light have different luminous colors.

[0137] Step c2: controlling the first indicator light to illuminate according to the first target flashing number, and controlling the second indicator light to illuminate according to the second target flashing number.

[0138] Specifically, for example, if the fault code is a two-digit number, that is, the target fault code is a two-digit number, by using the units digit of the target fault code as the first target flashing number of the first indicator light, and the tens digit of the target fault code as the second target flashing number of the second indicator light, the first indicator light is controlled to flash the first target number of times, and the second indicator light is controlled to flash the second target number of times, the user can determine the target fault code based on the flashing number of the first indicator light and the second indicator light, thereby facilitating the determination of the cause of the vehicle fault based on the target fault code and facilitating timely maintenance.

[0139] In some embodiments, step c2 may be performed once. In some embodiments, step c2 may be performed multiple times in a cycle, with a preset interval between two consecutive executions of step c2. That is, step c2 may be performed periodically, thereby ensuring that the user can determine the target fault code for better vehicle fault handling.

[0140] An embodiment of the present invention further provides a vehicle fault handling device, which is used to execute the vehicle fault handling method provided by any embodiment of the present invention. Figure 4 This is a schematic diagram of the structure of a vehicle fault handling device provided by an embodiment of the present invention, with reference to Figure 4 , the vehicle fault handling device includes:

[0141] The acquisition module 410 is configured to acquire detection information corresponding to each fault code according to the detection method corresponding to each fault code in each fault processing cycle; wherein each detection information corresponds to a threshold value, and each fault code corresponds to a fault information; the fault information includes at least a fault level and a fault name;

[0142] a fault determination module 420 for determining, for each fault code, if the detection information corresponding to the fault code is greater than the corresponding threshold information, that the fault code is used as a target fault code, and the detection information corresponding to the target fault code is used as target detection information;

[0143] The fault processing module 430 is used to execute a target processing method corresponding to a target fault code;

[0144] a first storage control module 440 configured to store the target fault code, target detection information corresponding to the target fault code, and fault information corresponding to the target fault code into the current fault table if the target fault code is not in the current fault table; wherein the current fault table is stored in a first memory of the vehicle;

[0145] The second storage control module 450 is used to determine whether to store the target fault code in the historical fault table based on the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table if the target fault code is in the historical fault table; wherein the historical fault table is stored in the second memory of the vehicle.

[0146] The vehicle fault handling device provided in the embodiment of the present invention can execute the vehicle fault handling method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0147] An embodiment of the present invention further provides a vehicle, which includes the vehicle fault handling device provided by any embodiment of the present invention. Therefore, the vehicle has the same beneficial effects as the vehicle fault handling device provided by any embodiment of the present invention, which will not be repeated here.

[0148] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the present invention can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved. This is not limited herein.

[0149] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. A vehicle fault handling method, characterized in that: include: In a current fault handling cycle, current detection information corresponding to each fault code is obtained according to the detection method corresponding to each fault code; wherein each detection information corresponds to a threshold information, and each fault code corresponds to a fault information; the fault information includes at least a fault level and a fault name; For each fault code, if the current detection information corresponding to the fault code is greater than the corresponding threshold information, the fault code is used as a target fault code, and the current detection information corresponding to the target fault code is used as the target detection information; Executing a target processing method corresponding to the target fault code; If the target fault code is not in the current fault table, storing the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code into the current fault table; wherein the current fault table is stored in a first memory of the vehicle; If the target fault code is in the historical fault table, determine whether to store the target fault code determined in the current fault processing cycle into the historical fault table based on the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table; wherein, the historical fault table is stored in the second memory of the vehicle.

2. The method according to claim 1, characterized in that If the target fault code is in the historical fault table, determining whether to store the target fault code determined in the current fault processing cycle in the historical fault table according to the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table includes: If the target fault code is in the historical fault table, and the difference between the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table is greater than a preset time length, the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code are stored in the historical fault table; If the target fault code is in the historical fault table, and the difference between the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table is less than or equal to the preset duration, the target fault code determined by the current fault processing cycle will not be stored in the historical fault table.

3. The method according to claim 1, characterized in that The method comprises: If the target fault code is not in the historical fault table, the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code and the fault time corresponding to the target fault code are stored in the historical fault table.

4. The method according to any one of claims 1 to 3, characterized in that The storing the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code into the current fault table includes: Determine the target storage address according to the number of faults of the fault codes stored in the current fault table; According to the target storage address, the target fault code, the target detection information corresponding to the target fault code, and the fault information corresponding to the target fault code are stored in the current fault table.

5. The method according to claim 2 or 3, characterized in that The storing the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code into the historical fault table includes: Determining a maximum storage address of the historical fault table according to the storage space of the historical fault table; Determine the target storage first address according to the number or address of the fault codes stored in the historical fault table; If the target storage first address is greater than the maximum storage address, subtracting the maximum storage address from the target storage first address to obtain a final storage address; Starting from the final storage address, the target fault code determined in the current fault processing cycle, the target detection information corresponding to the target fault code, the fault information corresponding to the target fault code, and the fault time corresponding to the target fault code are stored in the historical fault table.

6. The method according to any one of claims 1 to 3, characterized in that In the current fault handling cycle, obtaining detection information corresponding to each fault code according to the detection method corresponding to each fault code includes: In the current fault handling cycle, the detection method corresponding to each fault code is determined according to a preset correspondence relationship, and the current detection information corresponding to each fault code is obtained according to the detection method corresponding to each fault code; wherein the preset correspondence relationship is the correspondence between the fault code, the fault level, the detection method, and the handling method; The executing the target processing method corresponding to the target fault code includes: A target processing method corresponding to the target fault code is determined according to the target fault code and the preset corresponding relationship, and the target processing method corresponding to the target fault code is executed.

7. The method according to claim 6, characterized in that The determining, based on the target fault code and the preset corresponding relationship, a target processing method corresponding to the target fault code includes: A target fault level corresponding to the target fault code is determined based on the target fault code and the preset corresponding relationship, and a target processing method corresponding to the target fault code is determined based on the target fault level or the target fault code; wherein, when the target fault level is level one, the motor that drives the vehicle is controlled to stop running; when the target fault level is level two, the speed of the motor is reduced; when the target fault level is level three, a fault prompt message is issued.

8. The method according to any one of claims 1 to 3, characterized in that The method further comprises: When the vehicle is powered on, the historical fault table in the second memory is read and the historical fault table is sent to the first memory.

9. The method according to any one of claims 1 to 3, characterized in that The method further comprises: For each fault code, if the detection information corresponding to the fault code is less than or equal to the corresponding threshold information, and the fault code is stored in the current fault table, the fault code is deleted from the current fault table.

10. The method according to any one of claims 1 to 3, characterized in that For each fault code, if the current detection information corresponding to the fault code is greater than the corresponding threshold information, then the fault code is used as the target fault code, and the method further includes: The units digit of the target fault code is used as a first target flashing number of the first indicator light, and the tens digit of the target fault code is used as a second target flashing number of the second indicator light; wherein the first indicator light and the second indicator light have different luminous colors; The first indicator light is controlled to emit light according to the first target flashing number, and the second indicator light is controlled to emit light according to the second target flashing number.

11. A vehicle fault handling device, characterized in that: Used to execute the vehicle fault handling method according to any one of claims 1 to 10; The vehicle fault handling device includes: an acquisition module, configured to acquire, in each fault processing cycle, detection information corresponding to each fault code according to the detection method corresponding to each fault code; wherein each detection information corresponds to a threshold value, and each fault code corresponds to a fault information; the fault information at least includes a fault level and a fault name; a fault determination module, configured to, for each fault code, determine, if the detection information corresponding to the fault code is greater than the corresponding threshold information, take the fault code as a target fault code and the detection information corresponding to the target fault code as target detection information; A fault processing module, configured to execute a target processing method corresponding to the target fault code; a first storage control module, configured to store the target fault code, target detection information corresponding to the target fault code, and fault information corresponding to the target fault code into the current fault table if the target fault code is not in the current fault table; wherein the current fault table is stored in a first memory of the vehicle; A second storage control module is used to determine whether to store the target fault code in the historical fault table based on the current fault time corresponding to the target fault code and the historical fault time corresponding to the target fault code in the historical fault table if the target fault code is in the historical fault table; wherein, the historical fault table is stored in the second memory of the vehicle.

Images