Vehicle fault code conversion method, storage medium, vehicle control unit and vehicle

Abstract

The application discloses a vehicle fault code conversion method, a storage medium, a whole vehicle controller and a vehicle. The vehicle fault code conversion method comprises the following steps: in response to a UDS diagnosis service request, performing fault diagnosis on the vehicle to obtain a UDS diagnosis fault code; converting the UDS diagnosis fault code into a DM1 message fault code, and sending the DM1 message fault code to an instrument of the vehicle for display. The whole vehicle controller is used to convert the UDS diagnosis fault code into a DM1 message format, so that the function of displaying the fault code on the instrument is realized.

Description

Technical Field

[0001] This invention relates to the field of vehicle technology, and in particular to a method for converting vehicle fault codes, a storage medium, a vehicle controller, and a vehicle. Background Technology

[0002] The three-electric system of new energy vehicles supports the UDS (Unified Diagnostic Services) diagnostic protocol and can read fault codes through a fault diagnostic tool, but it cannot actively display faults on the instrument panel. Summary of the Invention

[0003] One objective of this invention is to provide a method for converting vehicle fault codes, a storage medium, a vehicle controller, and a vehicle. The vehicle controller converts UDS diagnostic fault codes into DM1 message format, thereby enabling the instrument panel to display fault codes.

[0004] To achieve the above objectives, a first aspect of the present invention provides a method for converting vehicle fault codes. The method includes: responding to a UDS diagnostic service request, performing fault diagnosis on the vehicle to obtain a UDS diagnostic fault code; converting the UDS diagnostic fault code into a DM1 message fault code; and sending the DM1 message fault code to the vehicle's instrument panel for display.

[0005] In addition, the vehicle fault code conversion method proposed in the above embodiments of the present invention may also have the following additional technical features:

[0006] According to one embodiment of the present invention, the DM1 message fault code includes a Suspicious Parameter Number (SPN), a Fault Mode Flag (FMI), a Suspicious Parameter Number Conversion Method (CM), and an Occurrence Count (OC). Converting the UDS diagnostic fault code into a DM1 message fault code includes: converting a portion of the high byte and middle byte of the UDS diagnostic fault code into the SPN, converting another portion of the UDS diagnostic fault code into the FMI, converting the Occurrence Count of the Extended Data Record in the UDS diagnostic fault code into the OC, and setting the CM to 0.

[0007] According to one embodiment of the present invention, the method further includes: determining whether the number of bytes of the DM1 message fault code is greater than a preset threshold; if the number of bytes of the DM1 message fault code is greater than the preset threshold, then sending the DM1 message fault code to the vehicle's instrument panel using a first transmission method; if the number of bytes of the DM1 message fault code is less than or equal to the preset threshold, then sending the DM1 message fault code to the vehicle's instrument panel using a second transmission method.

[0008] According to one embodiment of the present invention, the preset threshold is 8 bytes, the first transmission mode is a multi-frame transmission mode, and the second transmission mode is a single-frame transmission mode.

[0009] According to one embodiment of the present invention, the UDS diagnostic fault code includes fault information of the vehicle controller and / or function controller of the vehicle, wherein the function controller includes at least one of a battery management system, a motor controller, a DC-DC converter, and a DC-AC converter.

[0010] According to one embodiment of the present invention, sending the DM1 message fault code to the vehicle's instrument panel includes: sending the DM1 message fault code to the central gateway via the CAN bus, and sending the DM1 message fault code to the instrument panel via the central gateway.

[0011] According to one embodiment of the present invention, the instrument displays the DM1 message fault code in text or on a fault interface.

[0012] The vehicle fault code conversion method of this invention involves the vehicle controller responding to a UDS diagnostic service request, performing fault diagnosis on the vehicle to obtain UDS diagnostic fault codes, converting the UDS diagnostic fault codes into DM1 message fault codes, and sending the DM1 message fault codes to the vehicle's instrument panel for display, thereby realizing the function of displaying fault codes on the instrument panel.

[0013] To achieve the above objectives, a second aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the vehicle fault code conversion method described above.

[0014] To achieve the above objectives, a third aspect of the present invention provides a vehicle controller, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, it implements the vehicle fault code conversion method described above.

[0015] To achieve the above objectives, a fourth aspect of the present invention provides a vehicle including the vehicle controller as described above.

[0016] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0017] Figure 1 This is a flowchart of a vehicle fault code conversion method according to an embodiment of the present invention;

[0018] Figure 2This is a schematic diagram of vehicle controller fault diagnosis according to an embodiment of the present invention;

[0019] Figure 3 This is a schematic diagram of a UDS diagnostic fault code according to an embodiment of the present invention;

[0020] Figure 4 This is a schematic diagram of a method for representing DM1 message fault codes according to an embodiment of the present invention;

[0021] Figure 5 This is a flowchart illustrating the determination of the number of bytes of the DM1 message fault code according to an embodiment of the present invention;

[0022] Figure 6 This is a schematic diagram of the structure of a vehicle controller according to an embodiment of the present invention;

[0023] Figure 7 This is a schematic diagram of the structure of a vehicle according to an embodiment of the present invention. Detailed Implementation

[0024] Embodiments of the present invention are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain the present invention, and should not be construed as limiting the present invention.

[0025] The following will describe in detail the vehicle fault code conversion method, storage medium, vehicle controller, and vehicle of the present invention with reference to the accompanying drawings and specific embodiments.

[0026] This invention, based on research into the faults of the vehicle controller in pure electric heavy-duty trucks, proposes a method for displaying vehicle controller faults on the instrument panel of pure electric heavy-duty trucks. The heavy-duty truck controller supports the J1939 protocol and can send fault diagnostic codes via DM1 when a system fault occurs. However, new energy vehicle systems support the UDS diagnostic protocol. Both UDS (14229) and J1939 use the term DTC (Diagnostic Trouble Code) for fault diagnosis, but they are significantly different and cannot coexist. This prevents fault codes in new energy vehicles from being displayed on existing instrument panels. The vehicle fault code conversion method proposed in this invention converts the UDS diagnostic fault codes into DM1 message fault codes through the vehicle controller and sends the DM1 message fault codes to the vehicle's instrument panel for display.

[0027] Figure 1 This is a flowchart of a vehicle fault code conversion method according to an embodiment of the present invention.

[0028] In one embodiment of the present invention, such as Figure 1As shown, the methods for converting vehicle fault codes include:

[0029] S1, in response to a UDS diagnostic service request, performs fault diagnosis on the vehicle to obtain UDS diagnostic fault codes.

[0030] Specifically, the UDS diagnostic protocol is a request protocol. The fault request process is as follows: The host computer sends a message requesting to read the fault. The fault request content includes: ID + (fault service number) data. The slave computer replies with: ID + (positive response + current DTC code) data. The host computer parses the current DTC based on the slave computer's reply and then displays the fault description of the corresponding DTC according to the standard. The host computer can be a client, and the slave computer can be a vehicle controller. In this invention, the slave computer is described using a vehicle controller as an example. The client sends a UDS diagnostic service request, the vehicle controller accepts and responds to the UDS diagnostic service request, performs fault diagnosis on the vehicle, and obtains the UDS diagnostic fault code.

[0031] More specifically, the vehicle controller responds to UDS diagnostic service requests and performs fault diagnosis on the vehicle, including diagnosing faults within itself and on functional controllers within the vehicle system. The UDS diagnostic fault codes obtained by the vehicle controller include fault information from either the vehicle controller itself or the functional controllers within the vehicle system.

[0032] In one embodiment of the present invention, the UDS diagnostic fault code includes fault information of the vehicle controller and / or function controller, wherein the function controller includes at least one of the battery management system, motor controller, DC-DC converter, and DC-AC converter.

[0033] Specifically, such as Figure 2As shown, the vehicle control unit (VCU) is connected to the battery management system (BMS), motor control unit (MCU), DC-DC converter (DCDC), and DC-AC converter (DCAC). When the VCU receives a UDS diagnostic service request, it responds to the request. The VCU can perform self-monitoring and fault diagnosis, obtaining fault diagnostic codes for itself. It can also perform fault diagnosis on functional controllers, including the battery management system, motor controller, DC-DC converter, and DC-AC converter, obtaining UDS diagnostic fault codes for either the battery management system, motor controller, DC-DC converter, or DC-AC converter. In other words, UDS diagnostic fault codes include fault information from at least one of the vehicle's control unit, battery management system, motor controller, DC-DC converter, and DC-AC converter.

[0034] To facilitate the explanation of converting UDS diagnostic fault codes to DM1 message fault codes, we will first provide a detailed explanation of the content and reading of UDS diagnostic fault codes. A UDS diagnostic fault code consists of a 3-byte DTC identifier and a 1-byte DTC status bit. The 3-byte DTC identifier includes a high byte (DTCHighByte), a middle byte (DTCMiddleByte), and a low byte (DTCLowByte). The high byte (DTCHighByte) and the middle byte (DTCMiddleByte) represent the fault internal code, corresponding to a 5-digit standard fault code. In a 5-digit standard fault code, the first digit is a letter, and the following four digits are numbers. For example... Figure 3This diagram illustrates the correspondence between internal fault codes and 5-digit standard fault codes. The first three digits of a standard fault code correspond to the high byte (DTCHighByte), and the last two digits correspond to the middle byte (DTCMiddleByte). For example, in the DTC diagnostic code "B100016", "B1000" is the internal fault code, and the last "16" is the content of the low byte (DTCLowByte). "B1000" corresponds to the content of a 5-digit standard fault code. The first digit of the fault code is a letter, indicating the system to which the fault belongs. For example, P indicates a powertrain fault, C indicates a chassis system fault, B indicates a body system fault, and U indicates a network fault. The second digit of the fault code is a number, indicating the fault type. The third digit of a fault code is a number, indicating the subsystem to which the fault belongs. Taking the powertrain system as an example (fault codes starting with P), the following possibilities exist: 0: Fuel and air metering auxiliary emission control system; 1: Fuel and air metering system; 2: Fuel and air metering system (injectors); 3: Ignition system; 4: Exhaust gas control system; 5: Cruise control and idle speed control system; 6: Onboard computer and output signals; 7: Transmission system control; 8: Transmission system control. The last two digits of the fault code are also numbers, indicating the specific object and type of fault.

[0035] The rules for reading DTC diagnostic fault codes in the UDS diagnostic protocol include: 1. The host computer can read the status information of any one or a group of servers stored in the vehicle. The slave computer should return emission-related and non-emission DTC information. 2. The host computer can obtain the number of DTCs matching the DTC status mask code defined by the host computer. 3. The host computer can obtain a list and status of all DTCs matching the DTC status mask code defined by the host computer. 4. The host computer can obtain DTC Snapshot record information related to the DTC code and DTC snapshot record number defined by the host computer. 5. The host computer can obtain DTC ExtendedData record information related to the DTC code and DTCExtendedData record number defined by the client. DTCExtendedData is typically used to store dynamic data related to DTCs, such as the number of DTC occurrences and the time of the last DTC occurrence. 6. The host computer can obtain the status of all DTCs supported by the server.

[0036] In summary, the lower-level machine performs a bitwise AND operation between the DTC status mask requested by the upper-level machine and the actual status of each DTC it supports. The lower-level machine will return not only the valid DTC status mask, but also all DTCs whose AND operation result is non-zero. For example, (statusOfDTC&DTCStatusMask)! = 0. If the status mask specified by the upper-level machine contains bits that the lower-level machine does not support, the lower-level machine only needs to use the status bits it supports to process the DTC information. If the server does not have a DTC that matches the status mask in the client's request, the DTC status mask byte in the positive response message will not include the DTC and status information. The server searches for matching faults according to the defined status mask format and returns the matching DTC identifier (3 bytes) and DTC status (1 byte) information. Among them, the 01 sub-service only counts the number of DTCs that match the status mask, while the 02 sub-service returns the information of these matching DTCs.

[0037] DTC diagnostic fault code information also includes DTC extended data information, which records other information about the fault, such as the number of times the fault occurred, the number of times it has aged, and the number of times it has aged. Service 06 is used to request extended information for a specified fault code (DTC). The host computer can use the "Report DTC Extended Data Record via DTC Code" sub-function service to read DTC extended data information. The host computer can read the DTC extended data based on the DTC code and the record number of the DTC extended data. In this case, the slave computer must search among all the DTCs it supports for a DTC that completely matches the DTC mask record defined by the host computer. The response must contain a predefined DTC extended data record. The structure of the data reported in the DTC extended data record is defined by the DTC extended data record number, similar to the definition of data in a data identifier. The response can include multiple sets of DTC extended data record numbers and corresponding DTC extended data records. A DTC can store different types of DTC extended data records. The slave computer must report one DTC extended data record in a response message. If the host computer has already set the DTC extended data record to 0xFF, the slave computer must include all the extended data records corresponding to that DTC code in a response message. If the parameter DTC code or DTC extended data record number is invalid or not supported, the slave computer should send a negative response.

[0038] After the lower-level machine (such as the vehicle controller) obtains the UDS diagnostic fault code, it converts the UDS diagnostic fault code into DM1 message format based on the obtained DTC fault information and DTC extended information, and provides it to the vehicle's instrument panel for display.

[0039] S2 converts the UDS diagnostic fault code into a DM1 message fault code and sends the DM1 message fault code to the vehicle's instrument panel for display.

[0040] Specifically, after the vehicle controller obtains the UDS diagnostic fault code, it converts the UDS diagnostic fault code into a DM1 message fault code according to the DM1 message format, and sends the DM1 message fault code to the vehicle's instrument panel for display.

[0041] More specifically, the J1939 protocol fault diagnosis is relatively complex, and its fault diagnosis is divided into current fault DM1, historical fault DM2, and cleared fault DM3. The UDS diagnostic fault code obtained by this invention is the current fault, so it is converted into a DM1 message fault code. The DM1 message fault code is continuously sent on the bus if there is a fault.

[0042] In one embodiment of the present invention, the DM1 message fault code includes a suspected parameter number SPN, a fault mode flag FMI, a conversion method CM for the suspected parameter number, and an occurrence count OC; converting the UDS diagnostic fault code into a DM1 message fault code includes: converting a portion of the high byte and middle byte of the UDS diagnostic fault code into SPN, converting another portion of the UDS diagnostic fault code into FMI, converting the occurrence count of the extended data record in the UDS diagnostic fault code into OC, and setting CM to 0.

[0043] Specifically, such as Figure 4 The DM1 message fault code representation shown is composed of the Suspicious Parameter Number (SPN), Fault Mode Flag (FMI), Suspicious Parameter Number Conversion Method (CM), and Occurrence Count (OC). In the J1939 protocol, the DM1 message has 6 bytes. Byte 1 of the DMI message fault code is the lamp status, byte 2 is a reserved bit, byte 3 is the lower 8 significant bits of the Suspicious Parameter Number (SPN), byte 4 is the second byte of the Suspicious Parameter Number (SPN), byte 5 is the higher 3 significant bits of the Suspicious Parameter Number (SPN) and the significant bits of the Fault Mode Flag (FMI), and byte 6 is the Occurrence Count (OC).

[0044] More specifically, the conversion method for UDS diagnostic fault codes into DM1 message fault codes is as follows: convert some bits in the high byte DTCHighByte and the middle byte DTCMiddleByte of the UDS diagnostic fault code to SPN, convert the low byte DTCLowByte of the UDS diagnostic fault code to FMI, and convert the occurrence count of the extended data record in the extended information of the read UDS diagnostic fault code to OC. CM is 0 by default.

[0045] For example, if the UDS diagnostic fault code is U007388, its fault internal code is: 1100 0000 0111 0011, which is C073 in hexadecimal. If the low byte DTCLowByte(2) is added, its complete hexadecimal representation is 0xC07302. If the fault occurrence counter is 1, then the DM1 message fault code is 73C0 02 01. When byte 1 of DM1 is 00 and byte 2 is FF, the complete DM1 message fault code of the 0xFD node is: 0x18FECAFD: 00FF 73C002 01FFFF.

[0046] It should be noted that DM1 message fault codes have two transmission methods: single-frame message transmission and multi-frame message transmission. When the number of bytes in the converted DM1 message fault code is too large, single-frame message transmission cannot completely transmit the DM1 message.

[0047] In one embodiment of the present invention, such as Figure 5 As shown, the methods for converting vehicle fault codes also include:

[0048] S101, determine whether the number of bytes of the DM1 message fault code is greater than the preset threshold.

[0049] S102, if the number of bytes of the DM1 message fault code is greater than the preset threshold, the first transmission method is used to send the DM1 message fault code to the vehicle's instrument panel.

[0050] S103, if the number of bytes of the DM1 message fault code is less than or equal to the preset threshold, the second transmission method is used to send the DM1 message fault code to the vehicle's instrument panel.

[0051] In one embodiment of the present invention, the preset threshold is 8 bytes, the first transmission mode is multi-frame transmission mode, and the second transmission mode is single-frame transmission mode.

[0052] Specifically, after the vehicle controller converts the UDS diagnostic fault code into a DM1 message fault code, the number of bytes in the DM1 message fault code may exceed 8 bytes or be less than or equal to 8 bytes. When transmitting the DM1 message, only 8 bytes can be transmitted per frame. When the number of bytes in the DM1 message fault code is greater than 8 bytes, a multi-frame transmission method is used; when the number of bytes in the DM1 message fault code is less than or equal to 8 bytes, a single-frame transmission method is used. For example, the DM1 message fault code "00FF73C0 0201FF FF" illustrated above has more than 8 bytes and is transmitted using a multi-frame transmission method.

[0053] After converting the UDS diagnostic fault code into a DM1 message fault code using the method described above, the DM1 message fault code is sent to the vehicle's instrument panel for display.

[0054] In one embodiment of the present invention, sending the DM1 message fault code to the vehicle's instrument panel includes: sending the DM1 message fault code to the central gateway via the CAN bus, and sending the DM1 message fault code to the instrument panel via the central gateway.

[0055] Specifically, such as Figure 2 As shown, the vehicle control unit (VCU) also communicates with the central gateway (CGW). The VCU sends the DM1 fault code to the central gateway via the CAN bus. The central gateway communicates with the vehicle's instrument cluster, and the VCU sends the DM1 fault code to the instrument cluster via the central gateway. The instrument cluster displays the DM1 fault code for the convenience of customers and after-sales service personnel.

[0056] In one embodiment of the present invention, the DM1 message fault code is displayed in text or on a fault interface by an instrument.

[0057] Specifically, the vehicle's instrument panel can display the DM1 fault code and can also parse the DM1 fault code to display specific fault information on the fault interface, such as which system or system fault type, to facilitate customers and after-sales maintenance personnel.

[0058] The vehicle fault code conversion method of this invention involves the vehicle controller responding to a UDS diagnostic service request to perform vehicle fault diagnosis. The vehicle controller detects the UDS diagnostic fault codes (DTCs) and the number of fault occurrences. Functional controllers such as the battery management system, motor controller, DC-DC converter, and DC-AC converter send information to the vehicle controller via CAN message. The vehicle controller converts the UDS diagnostic fault codes (DTCs) into DM1 message format. Depending on the number of faults, the DM1 message is divided into single-frame or multi-frame messages and transmitted according to different transmission methods. The DM1 message fault codes are then sent to the instrument cluster for display.

[0059] The present invention also proposes a computer-readable storage medium.

[0060] In one embodiment of the present invention, a computer program is stored on a computer-readable storage medium, and when the computer program is executed by a processor, it implements the vehicle fault code conversion method as described above.

[0061] The present invention also proposes a vehicle controller.

[0062] In one embodiment of the present invention, such as Figure 6As shown, the vehicle controller 100 includes a memory 10 and a processor 20. The memory 10 stores a computer program. When the computer program is executed by the processor 20, it implements the vehicle fault code conversion method described above.

[0063] The present invention also proposes a vehicle.

[0064] In one embodiment of the present invention, such as Figure 7 As shown, vehicle 1000 includes vehicle controller 100 as described above.

[0065] The vehicle fault code conversion method, storage medium, vehicle controller, and vehicle of this invention embodiment involve the vehicle controller responding to a UDS diagnostic service request to perform fault diagnosis on the vehicle. The vehicle controller itself detects the UDS diagnostic fault codes (DTCs) and the number of fault occurrences. Functional controllers such as the battery management system, motor controller, DC-DC converter, and DC-AC converter send information to the vehicle controller via CAN message. The vehicle controller converts the UDS diagnostic fault codes (DTCs) into DM1 message format. Depending on the number of faults, the DM1 message is divided into single-frame or multi-frame messages and transmitted according to different transmission methods. The DM1 message fault codes are then sent to the instrument cluster for display.

[0066] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0067] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0068] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0069] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing this invention and simplifying the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this invention.

[0070] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0071] In this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise explicitly limited. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0072] In this invention, unless otherwise explicitly specified and limited, "above" or "below" the second feature can mean that the first feature is in direct contact with the second feature, or that the first feature is in indirect contact with the second feature through an intermediate medium. Furthermore, "above," "over," and "on top" of the second feature can mean that the first feature is directly above or diagonally above the second feature, or simply that the first feature is at a higher horizontal level than the second feature. "Below," "below," and "under" the second feature can mean that the first feature is directly below or diagonally below the second feature, or simply that the first feature is at a lower horizontal level than the second feature.

[0073] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. A method for converting vehicle fault codes, characterized in that, The method includes: In response to a UDS diagnostic service request, perform vehicle fault diagnosis to obtain UDS diagnostic fault codes; The UDS diagnostic fault code is converted into a DM1 message fault code, and the DM1 message fault code is sent to the vehicle's instrument panel for display.

2. The vehicle fault code conversion method according to claim 1, characterized in that, The DM1 message fault code includes the Suspicious Parameter Number (SPN), Fault Mode Flag (FMI), Suspicious Parameter Number Conversion Method (CM), and Occurrence Count (OC); the conversion of the UDS diagnostic fault code to the DM1 message fault code includes: Convert a portion of the high byte and middle byte of the UDS diagnostic fault code to the SPN, convert another portion of the bits in the UDS diagnostic fault code to the FMI, convert the occurrence count of the extended data record in the UDS diagnostic fault code to the OC, and set the CM to 0.

3. The vehicle fault code conversion method according to claim 1, characterized in that, The method further includes: Determine whether the number of bytes of the DM1 message fault code is greater than a preset threshold; If the number of bytes of the DM1 message fault code is greater than the preset threshold, the DM1 message fault code is sent to the vehicle's instrument panel using the first transmission method. If the number of bytes of the DM1 message fault code is less than or equal to the preset threshold, the DM1 message fault code is sent to the vehicle's instrument panel using the second transmission method.

4. The vehicle fault code conversion method according to claim 3, characterized in that, The preset threshold is 8 bytes, the first transmission method is a multi-frame transmission method, and the second transmission method is a single-frame transmission method.

5. The vehicle fault code conversion method according to claim 1, characterized in that, The UDS diagnostic fault codes include fault information of the vehicle's overall controller and / or functional controller, wherein the functional controller includes at least one of the battery management system, motor controller, DC-DC converter, and DC-AC converter.

6. The vehicle fault code conversion method according to claim 5, characterized in that, Sending the DM1 fault code to the vehicle's instrument panel includes: The DM1 fault code is sent to the central gateway via the CAN bus, and then sent to the instrument via the central gateway.

7. The method for converting vehicle fault codes according to claim 1, characterized in that, The instrument displays the DM1 message fault code in text or on a fault interface.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the vehicle fault code conversion method as described in any one of claims 1-7.

9. A vehicle controller, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the computer program is executed by the processor, it implements the vehicle fault code conversion method as described in any one of claims 1-7.

10. A vehicle, characterized in that, Includes the vehicle controller as described in claim 9.

Images