Fault code real-time exposure method and system of vehicle and vehicle

Abstract

A fault code real-time exposure method for a vehicle, comprising: a step (S100) of obtaining fault data: an ECU controller obtains the fault data of the vehicle; a fault data uploading step (S200): the ECU controller maps the fault data into a fault code message, and uploads the fault code message to the central gateway in a multiplexing mode; a step (S300) of receiving a fault code message: a central gateway receives and locally stores the fault code message; a fault message uploading step (S400): the central gateway packages the locally stored fault code message into a fault message and sends the fault message to a remote communication module, and the remote communication module receives the fault message and uploads the received fault message to a cloud server; and a step (S500) of analyzing the fault message: the cloud server receives and stores the fault message, analyzes the data of the fault message according to the mapping rule, and reads and displays the fault code. The invention further discloses a fault code real-time exposure system for the vehicle and the vehicle.

Description

Technical Field

[0001] The present invention relates to the field of vehicle fault diagnosis, and more specifically, to a method for real-time exposure of vehicle fault codes, a system using the method, and a vehicle using the system. Background Art

[0002] As the requirements for automobile functions and configurations become higher and higher, more and more controllers are used in the whole vehicle, and the need for fast and efficient diagnosis of vehicle faults becomes more and more urgent. At present, the diagnosis of vehicle faults generally uses the software module of the unified diagnostic service built into the ECU (Electronic Control Unit) controller, and detects the fault through the internal and external sensors of the ECU controller. After the ECU controller detects the fault, it stores the fault in the form of a fault code. There are currently two mainstream methods to read the fault code: one is to send the diagnostic service to read the fault code through the vehicle's OBD (On-Board Diagnostics) interface; the other is to send the diagnostic service to read the fault code through the vehicle's remote diagnostic module.

[0003] However, both of the above methods require separate hardware devices or integrated corresponding software to support, and require instructions to be sent for reading. The above methods also have the following disadvantages: one is that it affects driving safety: for example, during driving, the diagnostic instructions are sent through the OBD interface external device to read the DTC (Diagnostic Trouble Code) information of each ECU in the car, causing the driver to be distracted and affecting driving safety; the other is that the remote diagnostic module needs to be triggered by certain conditions before sending the diagnostic instructions, and the timeliness of reading is poor; in addition, it increases manpower and material costs: the reading operation requires expensive expenses to purchase hardware equipment and manpower support. In addition, when multiple faults occur, the efficiency of uploading fault codes is low, and the fault of the vehicle cannot be quickly located. Summary of the invention

[0004] The purpose of the present invention is to provide a real-time exposure method for vehicle fault codes, which can autonomously report a large number of fault codes to a cloud server at one time.

[0005] Another object of the present invention is to provide a real-time exposure system for vehicle fault codes, which can autonomously report a large number of fault codes to a cloud server at one time.

[0006] Another object of the present invention is to provide a vehicle, which adopts the above-mentioned fault code real-time exposure system for the vehicle.

[0007] The present invention provides a method for real-time exposure of fault codes for a vehicle. The vehicle includes an ECU controller, a central gateway and a remote communication module and is connected to a cloud server. The method for real-time exposure of fault codes includes the steps of obtaining fault data, uploading fault data to the central gateway, receiving a fault code message by the central gateway, uploading a fault message to the cloud server and parsing the fault message.

[0008] In the step of obtaining fault data, the ECU controller obtains the fault data of the vehicle. In the step of uploading fault data, the ECU controller maps the fault data into a fault code message, and uploads the fault code message to the central gateway in a multiplexed manner. In the step of receiving a fault code message, the central gateway receives and stores the fault code message locally. In the step of uploading a fault message, the central gateway packages the locally stored fault code message into a fault message and sends the fault message to the remote communication module. The remote communication module receives the fault message and uploads the received fault message to the cloud server. In the step of parsing the fault message, the cloud server receives and stores the fault message, and the background monitoring system of the cloud server parses the data of the fault message according to the mapping rules, reads the fault code and displays the fault code.

[0009] According to the real-time fault code exposure method provided by the present invention, the ECU controller uses multiplexing to enable one message to carry a large number of fault codes, thereby greatly improving the efficiency of the ECU controller in reporting fault codes, and further realizing rapid positioning of vehicle faults.

[0010] In an illustrative implementation of the method for real-time exposure of fault codes, the step of uploading fault data includes a step of generating a fault code message and a step of sending a fault code message. In the step of generating a fault code message, the ECU controller generates a corresponding fault code based on the fault data, maps the fault code to the data field of the application message, and uses the application message as a fault code message. A frame of fault code message includes a multiplexing switch signal and fault code information. The multiplexing switch signal is the multiplexing group number n. The multiplexing group number n occupies four bits, 0≤n≤15. In the step of sending a fault code message, the ECU controller periodically sends fault code messages to the central gateway in the order of the multiplexing group number n starting from 0 and increasing by 1. In this way, uploading fault code messages to the central gateway in a multiplexing manner of fault code messages is achieved.

[0011] In an exemplary implementation of the method for real-time exposure of fault codes, the mapping rules of fault codes in the fault code message include: in the data field of a frame of fault code message, the fault code information represents a fault code with every two bits and the fault codes are arranged in sequence. In this way, a maximum of 30 fault codes can be carried in the data field of a frame of fault code message, thereby improving the efficiency of reporting fault codes.

[0012] In another exemplary embodiment of the method for real-time exposure of fault codes, the mapping rule of the fault code in the fault code message further includes: the relationship between the fault code sequence number K and the multiplexing group sequence number n is: K=DTC(n*30+m), where 1≤m≤30. In this way, the relationship between the fault code sequence number K and the multiplexing group sequence number n is established.

[0013] The present invention also provides a real-time exposure system for fault codes of vehicles. The system includes an ECU controller, a central gateway, a remote communication module and a cloud server. The ECU controller obtains the fault data of the vehicle, maps the fault data into a fault code message, and uploads the fault code message to the central gateway in a multiplexed manner. The central gateway receives and stores the fault code message locally, and packages the locally stored fault code message into a fault message and sends the fault message to the remote communication module of the vehicle. The remote communication module receives the fault message and uploads the received fault message to the cloud server. The cloud server receives and stores the fault message, and its background monitoring system parses the data of the fault message according to the mapping rules, reads the fault code and displays the fault code.

[0014] According to the real-time fault code exposure system of the present invention, a message can carry a large number of fault codes through multiplexing, thereby greatly improving the efficiency of reporting fault codes and being able to quickly locate vehicle faults.

[0015] In an illustrative implementation of a fault code real-time exposure system, the ECU controller maps fault data to a fault code message, including: the ECU controller generates a corresponding fault code based on the fault data, and maps the fault code to the data field of the application message, and uses the application message as a fault code message. A frame of fault code message includes a multiplexing switch signal and fault code information. The multiplexing switch signal is the multiplexing group number n. The multiplexing group number n occupies four bits, 0≤n≤15. The ECU controller uploads the fault code message to the central gateway in a multiplexed manner, including: the ECU controller periodically sends the fault code message to the central gateway in the order of the multiplexing group number n starting from 0 and increasing by 1. Thereby, the fault code message is sent to the central gateway in a multiplexed manner.

[0016] In an exemplary implementation of the fault code real-time exposure system, the mapping rule of the fault code in the fault code message includes: in the data field of a frame of the fault code message, the fault code information represents a fault code with every two bits and the fault codes are arranged in sequence. In this way, a maximum of 30 fault codes can be carried in the data field of a frame of the fault code message, thereby improving the efficiency of reporting fault codes.

[0017] In another exemplary embodiment of the fault code real-time exposure system, the mapping rule of the fault code in the fault code message further includes: the relationship between the fault code sequence number K and the multiplexing group sequence number n is: K=DTC(n*30+m), where 1≤m≤30. In this way, the relationship between the fault code sequence number K and the multiplexing group sequence number n is established.

[0018] The present invention further provides a vehicle, which adopts the above-mentioned real-time fault code exposure system for vehicles and can autonomously report a large number of fault codes to a cloud server at one time.

[0019] According to the method for real-time exposure of fault codes provided by the present invention, by adopting a scheme of message multiplexing, in the data field of the message, a state of mapping a fault code with every two bits is realized, so that a frame of message can carry a maximum of 30 fault codes, thereby realizing that a message can carry a maximum of 480 fault codes, which greatly improves the efficiency of the ECU controller in reporting fault codes. In addition, according to the method for real-time exposure of fault codes of the present invention, the process of interacting with the ECU controller through external instructions is omitted, which greatly reduces the unpredictable faults of the ECU controller caused by the interaction and improves the safety of driving. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The following drawings are only used to schematically illustrate and explain the present invention, and do not limit the scope of the present invention.

[0021] Figure 1 It is a schematic flow chart of a method for real-time exposure of fault codes of a vehicle according to the present invention.

[0022] Figure 2 The figure is a schematic flow chart of a step of uploading fault data according to an exemplary embodiment of a method for real-time exposure of fault codes of a vehicle according to the present invention.

[0023] Figure 3 It is a schematic block diagram of a real-time exposure system of fault codes for a vehicle according to the present invention.

[0024] Description of symbols S100: Steps to obtain fault data S200: Steps for uploading fault data to the central gateway S300: Steps for the central gateway to receive fault code messages S400: Steps for uploading fault messages to the cloud server S500: Steps for analyzing fault messages 100 Fault code real-time exposure system 110 ECU controller 120 Central Gateway 121 Local Storage 123 Data upload cache 130 Telecommunications module 140 Cloud Server DETAILED DESCRIPTION

[0025] In order to have a clearer understanding of the technical features, purposes and effects of the invention, the specific embodiments of the present invention are now described with reference to the accompanying drawings. The same reference numerals in the drawings represent components with the same structure or similar structures but the same functions.

[0026] In this document, “exemplary” means “serving as an example, instance or illustration”, and any diagram or implementation described in this document as “exemplary” should not be interpreted as a more preferred or more advantageous technical solution.

[0027] In order to simplify the drawings, each figure only schematically shows the parts related to the present invention, which do not represent the actual structure of the product.

[0028] Figure 1 FIG. 1 is a schematic flow chart of a method for real-time exposure of fault codes of a vehicle according to the present invention. Figure 1 As shown, the real-time exposure method of fault codes for vehicles provided by the present invention includes a step of acquiring fault data S100, a step of uploading fault data S200, a step of receiving fault code messages S300, a step of uploading fault messages S400 and a step of parsing fault messages S500.

[0029] In the step S100 of acquiring fault data, the ECU controller acquires the fault data of the vehicle. During the driving process, the vehicle monitors the performance of the vehicle in real time through various sensors and sends the data to the ECU controller, which processes the data in real time and identifies potential faults.

[0030] In the step S200 of uploading fault data, the ECU controller maps the fault data into a fault code message, and uploads the fault code message to the central gateway in a multiplexed manner.

[0031] Figure 2 FIG. 1 is a schematic flow chart of a step of uploading fault data according to an exemplary embodiment of a method for real-time exposure of fault codes of a vehicle according to the present invention. Figure 2 As shown, in an exemplary implementation of the method for real-time exposure of fault codes, the step of uploading fault data S200 includes a step of generating a fault code message S210 and a step of sending a fault code message S220.

[0032] In the step S210 of generating a fault code message, the ECU controller generates a corresponding fault code according to the fault data, maps the fault code to the data field of the application message, and uses the application message as the fault code message. A frame of the fault code message includes a multiplexing switch signal and fault code information. The multiplexing switch signal is the multiplexing group number n. The multiplexing group number n occupies four bits and has a value of: 0≤n≤15.

[0033] Table 1: CAN message data field Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0 Bit15 Bit14 Bit13 Bit12 Bit11 Bit10 Bit9 Bit8 Bit23 Bit22 Bit21 Bit20 Bit19 Bit18 Bit17 Bit16 Bit31 Bit30 Bit29 Bit28 Bit27 Bit26 Bit25 Bit24 Bit39 Bit38 Bit37 Bit36 Bit35 Bit34 Bit33 Bit32 Bit47 Bit46 Bit45 Bit44 Bit43 Bit42 Bit41 Bit40 Bit55 Bit54 Bit53 Bit52 Bit51 Bit50 Bit49 Bit48 Bit63 Bit62 Bit61 Bit60 Bit59 Bit58 Bit57 Bit56

[0034] Table 2: Mapping rules of fault codes in fault code messages

[0035] Table 1 is a schematic diagram of the data field of a CAN message. Table 2 is a schematic diagram of the mapping rules of the fault code in the fault code message. As shown in Table 1, the data field of a CAN message frame has a total of sixty-four bits. As shown in Table 2, for example, four bits are used to represent the multiplexed switch signal, and the value range is 0 to 15, for example, using hexadecimal values ​​from 0X1 to 0XF, but not limited to this. In this way, there can be a total of sixteen groups of CAN message data frames. For example, the four bits from Bit7 to Bit4 are used to represent the multiplexed group number, and any other four bits can be selected to represent the multiplexed group number, but not limited to this, and other number of bits can also be selected to represent the multiplexed switch signal.

[0036] In an illustrative implementation of the method for real-time exposure of fault codes, the other sixty bits in the CAN message data field, except for the multiplexed group sequence number, are used for fault codes. In the data field of a frame of fault code message, the fault code information represents a fault code with every two bits and the fault codes are arranged in sequence. For example, there are four states of fault codes, namely: no fault, current fault, history fault and reserved. For example, the hexadecimal value 0X0 is used to represent no fault, 0X1 is used to represent current fault, 0X3 is used to represent history fault and 0X4 is used to represent reserved bit. Other base values ​​can also be used to represent, such as binary, octal, etc., to achieve different states of fault codes represented by two bits. However, it is not limited to this, and other bit numbers can also be used to represent fault codes.

[0037] The relationship between the fault code number K and the multiplex group number n is: K=DTC(n*30+m), where 1≤m≤30. In this way, the relationship between the fault code number K and the multiplex group number n is established. For example, as shown in Table 2, when the multiplex group number n is 0 and 1≤m≤30, the value range of K is 1 to 30; when the multiplex group number n is 1 and 1≤m≤30, the value range of K is 31 to 60; when the multiplex group number n is 2 and 1≤m≤30, the value range of K is 61 to 90; ...; when the multiplex group number n is 15 and 1≤m≤30, the value range of K is 451 to 480. That is, a data field of a fault code message corresponding to a multiplexing group can carry a maximum of 30 fault codes. After 16 frames (i.e., 16 groups) of fault code messages are multiplexed, a fault code message corresponding to a message ID can carry a maximum of 480 fault codes.

[0038] In the step S220 of sending the fault code message, the ECU controller periodically sends the fault code message to the central gateway in the order of multiplexing group number n starting from 0 and increasing by 1. For example, with a period of 500ms, first send the fault code message frame with multiplexing group number n as 0, then send the fault code message frame with multiplexing group number n as 1, and so on. After sending the fault code message frame with multiplexing group number n as 15, send the fault code message frame with multiplexing group number n as 0 again, and send it in such a periodic cycle. In this way, it can be achieved that a maximum of 30 fault codes can be carried in the data field of a frame of fault code message, and a fault code message corresponding to a message ID can carry a maximum of 480 fault codes. Thereby, it is achieved that the fault code message is sent to the central gateway cyclically by multiplexing the fault code message, the efficiency of reporting the fault code is improved, and the efficiency of reporting the fault code by the ECU controller is greatly improved.

[0039] In the step S300 of receiving the fault code message, the central gateway receives and stores the fault code message locally. The central gateway collects the fault code messages sent by each ECU controller of the vehicle in real time, and collects important information from other application messages sent by each ECU controller, such as vehicle speed, time, engine operating status, vehicle status, BMS (battery management system) high-voltage bus voltage, current and other information. In an illustrative embodiment, for example, the central gateway can be configured with 4G or 8G of local memory to store the above information, for example, store it in the order of timestamps, maintain data in the case of poor network transmission or interruption, and extract the local data of the central gateway through secure access, for example, read the local data of the central gateway through OBD diagnostic equipment or remote commands.

[0040] In the step S400 of uploading the fault message, the central gateway packages the locally stored fault code message into a fault message and sends the fault message to the remote communication module. The remote communication module receives the fault message and uploads the received fault message to the cloud server. In addition to the fault code information, the fault message also includes other application message information such as vehicle speed, time, engine operating status and vehicle status. For example, when the vehicle is connected to a 4G or 5G external network, the central gateway stores the collected information in the local memory while packaging the stored information into small-capacity data blocks and sending them to the remote communication module, which is then uploaded to the cloud server. Alternatively, when the vehicle is not connected to a 4G or 5G external network, the central gateway first saves the various types of collected information in the local memory, and then, after the vehicle is connected to a 4G or 5G external network, sends the fault message to the remote communication module, which is then uploaded to the cloud server. For example, the central gateway packages the collected information messages (including fault code messages and other application messages) in the minimum unit of 10M and in the order of timestamps to form fault messages. For example, the data upload cache of the central gateway is set to 10M, and the fault message is sent to the remote communication module.

[0041] In the fault message parsing step S500, the cloud server receives and stores the fault message, and the background monitoring system of the cloud server parses the data of the fault message according to the mapping rule, reads the fault code and displays the fault code, and when the fault code indicates that the vehicle has a fault, automatically intercepts the vehicle message data within a preset time period before and after the fault occurs to perform fault analysis. For example, the preset time period can be set by the manufacturer before the vehicle leaves the factory, and after leaving the factory, the user can modify it as needed.

[0042] According to the real-time fault code exposure method provided by the present invention, the ECU controller uses multiplexing to enable one message to carry a large number of fault codes, thereby greatly improving the efficiency of the ECU controller in reporting fault codes, and further realizing rapid positioning of vehicle faults.

[0043] Figure 3 FIG. 1 is a schematic block diagram of a real-time exposure system for fault codes of a vehicle according to the present invention. Figure 3As shown, the present invention also provides a real-time exposure system 100 for fault codes of vehicles, including an ECU controller 110, a central gateway 120, a remote communication module 130 and a cloud server 140. The ECU controller 110 may include one or more, and each ECU controller 110 is connected to the central gateway 120 via a CAN bus. The central gateway 120 and the remote communication module 130 are connected via an in-vehicle Ethernet. The remote communication module 130 communicates with the cloud server 140 via a municipal 4G or 5G communication network. However, it is not limited to this, and the communication between each ECU controller 110 and the central gateway 120, between the central gateway 120 and the remote communication module 130, and between the remote communication module 130 and the cloud server 140 can be achieved through any other suitable communication method.

[0044] The ECU controller 100 obtains the fault data of the vehicle, maps the fault data into a fault code message, and uploads the fault code message to the central gateway 140 in a multiplexed manner.

[0045] The central gateway 120 receives and stores the fault code message locally. For example, the central gateway 120 has a local memory 121. The central gateway 120 stores the received fault code message and other application message data in the local memory 121. The central gateway 120 packages the fault code message stored in the local memory 121 into a fault message and sends the fault message to the remote communication module 130. In addition to the fault code information, the fault message also includes other application message information such as vehicle speed, time, engine running status and vehicle status. For example, when the vehicle is connected to a 4G or 5G external network, the central gateway stores the collected information in the local memory, and at the same time, the stored information is packaged into small-capacity data blocks and sent to the remote communication module, and then uploaded to the cloud server. Alternatively, when the vehicle is not connected to a 4G or 5G external network, the central gateway first saves the collected information in the local memory, and then, after the vehicle is connected to a 4G or 5G external network, sends the fault message to the remote communication module, and then uploads it to the cloud server. For example, the central gateway 120 also has a data upload cache 123. For example, if the data upload cache 123 is set to 10M, the central gateway 120 will package the collected information messages in 10M as the minimum unit and in the order of timestamps to form a fault message, and send the fault message to the remote communication module. The remote communication module 130 receives the fault message and uploads the received fault message to the cloud server 140.

[0046] The cloud server 140 receives and stores fault messages, and its background monitoring system parses the data of the fault message according to the mapping rules, reads the fault code and displays the fault code. When the fault code indicates that a vehicle failure has occurred, the vehicle message data of the vehicle within a preset time period before and after the failure is automatically intercepted for fault analysis.

[0047] According to the real-time fault code exposure system of the present invention, a message can carry a large number of fault codes through multiplexing, thereby greatly improving the efficiency of reporting fault codes and being able to quickly locate vehicle faults.

[0048] In an illustrative embodiment of the fault code real-time exposure system 100, the ECU controller 110 maps the fault data into a fault code message, including: the ECU controller 100 generates a corresponding fault code according to the fault data, and maps the fault code to the data field of the application message, and uses the application message as a fault code message. A frame of fault code message includes a multiplexing switch signal and fault code information, and the multiplexing switch signal is a multiplexing group number n. The multiplexing group number n occupies four bits and has a value of: 0≤n≤15. In this way, the fault code message is sent to the central gateway in a multiplexing manner of the fault code message. The ECU controller 110 uploads the fault code message to the central gateway 140 in a multiplexing manner, including: the ECU controller 100 periodically sends the fault code message to the central gateway 120 in the order of the multiplexing group number n starting from 0 and increasing by 1.

[0049] For example, in the data field of a fault code message, the fault code information represents a fault code with every two bits and the fault codes are arranged in sequence. In this way, a maximum of 30 fault codes can be carried in the data field of a fault code message, thereby improving the efficiency of reporting fault codes. The relationship between the fault code sequence number K and the multiplexing group sequence number n is: K=DTC(n*30+m), where 1≤m≤30. In this way, the relationship between the fault code sequence number K and the multiplexing group sequence number n is established.

[0050] The present invention further provides a vehicle, which adopts the above-mentioned real-time fault code exposure system 100 for vehicles, and can autonomously report a large number of fault codes to the cloud server 140 at one time.

[0051] According to the method for real-time exposure of fault codes provided by the present invention, by adopting a scheme of message multiplexing, in the data field of the CAN message, a state of mapping a fault code with every two bits is realized, so that a frame of message can carry a maximum of 30 fault codes, thereby realizing that a message can carry a maximum of 480 fault codes, which greatly improves the efficiency of the ECU controller in reporting fault codes. In addition, according to the method for real-time exposure of fault codes of the present invention, the process of interacting with the ECU controller through external instructions is omitted, which greatly reduces the unpredictable faults of the ECU controller caused by the interaction and improves the safety of driving.

[0052] The series of detailed descriptions listed above are only specific descriptions of feasible embodiments of the present invention. They are not intended to limit the scope of protection of the present invention. Any equivalent implementation scheme or changes that do not deviate from the technical spirit of the present invention, such as combination, division or repetition of features, should be included in the scope of protection of the present invention.

Claims

1. A method for real-time exposure of fault codes of a vehicle, the vehicle comprising an ECU controller, a central gateway and a remote communication module; The vehicle communication is connected to the cloud server, characterized in that: The method comprises: Fault data acquisition step (S100): the ECU controller acquires fault data of the vehicle; Uploading fault data step (S200): the ECU controller maps the fault data into a fault code message, and uploads the fault code message to the central gateway in a multiplexing manner; Receiving a fault code message step (S300): the central gateway receives and locally stores the fault code message; Uploading fault message step (S400): the central gateway packages the locally stored fault code message into a fault message, and sends the fault message to the remote communication module, the remote communication module receives the fault message and uploads the received fault message to the cloud server; and Fault message parsing step (S500): the cloud server receives and stores the fault message, the cloud server parses the data of the fault message according to the mapping rule, reads the fault code and displays the fault code.

2. The method for real-time exposure of fault codes according to claim 1, characterized in that: The step of uploading fault data (S200) includes: Generating a fault code message step (S210): the ECU controller generates a corresponding fault code according to the fault data, maps the fault code to a data field of an application message, and uses the application message as the fault code message, wherein one frame of the fault code message includes a multiplexing switch signal and fault code information, the multiplexing switch signal is a multiplexing group number n, and the multiplexing group number n occupies four bits, 0≤n≤15; and The step of sending fault code messages (S220): the ECU controller periodically sends the fault code messages to the central gateway in the order of multiplexing group number n starting from 0 and increasing by 1.

3. The method for real-time exposure of fault codes according to claim 2, characterized in that: The mapping rule of the fault code in the fault code message includes: in a data field of a frame of the fault code message, the fault code information represents a fault code with every two bits and the fault codes are arranged in sequence.

4. The method for real-time exposure of fault codes according to claim 3, characterized in that: The mapping rule of the fault code in the fault code message also includes: the relationship between the fault code sequence number K and the multiplexing group sequence number n is: K=DTC (n*30+m), where 1≤m≤30.

5. A real-time exposure system (100) for a vehicle fault code, the system comprising an ECU controller (110), a central gateway (120), a remote communication module (130) and a cloud server (140), characterized in that: The ECU controller (110) acquires fault data of the vehicle, maps the fault data into a fault code message, and uploads the fault code message to the central gateway (140) in a multiplexed manner; The central gateway (120) receives and locally stores the fault code message, packages the locally stored fault code message into a fault message, and sends the fault message to the remote communication module (130); The remote communication module (130) receives the fault message and uploads the received fault message to the cloud server (140); and The cloud server (140) receives and stores the fault message, and its background monitoring system parses the data of the fault message according to the mapping rule, reads the fault code and displays the fault code.

6. The fault code real-time exposure system (100) according to claim 5, characterized in that: Mapping the fault data into a fault code message comprises: the ECU controller (110) generates a corresponding fault code according to the fault data, and maps the fault code into a data field of an application message, and uses the application message as the fault code message, wherein one frame of the fault code message comprises a multiplexing switch signal and fault code information, the multiplexing switch signal is a multiplexing group number n, wherein the multiplexing group number n occupies four bits, 0≤n≤15; and The uploading of the fault code message to the central gateway (140) in a multiplexing manner comprises: the ECU controller (110) periodically and cyclically sends the fault code message to the central gateway (120) in the order of the multiplexing group number n starting from 0 and increasing by 1.

7. The fault code real-time exposure system (100) according to claim 6, characterized in that: The mapping rule of the fault code in the fault code message includes: in a data field of a frame of the fault code message, the fault code information represents a fault code with every two bits and the fault codes are arranged in sequence.

8. The fault code real-time exposure system (100) according to claim 7, characterized in that: The mapping rule of the fault code in the fault code message also includes: the relationship between the fault code sequence number K and the multiplexing group sequence number n is: K=DTC (n*30+m), where 1≤m≤30.

9. A vehicle, characterized in that: The vehicle adopts the real-time fault code exposure system (100) for the vehicle as claimed in any one of claims 5 to 8.

Images