A new energy vehicle fault diagnosis method and system

Abstract

The present invention discloses a fault diagnosis method and system for new energy vehicles. The method includes the following steps: after a fault diagnosis mode is activated, the vehicle cloud platform sends a diagnostic command to the vehicle networking module (TBOX). The TBOX then sends the diagnostic command to the ECU module on the vehicle's CAN bus, queries the current or historical fault code, and uploads the fault code information to the cloud platform. This remote fault diagnosis facilitates users to proactively or automatically obtain the vehicle's fault status, allowing them to promptly identify and address any problems and repair them, thereby ensuring safe and reliable vehicle operation.

Description

Technical Field

[0001] The present invention relates to the field of automobile fault diagnosis, and in particular to a remote fault diagnosis method for new energy vehicles. Background Art

[0002] With the continuous advancement of intelligent and electrified vehicles, the automotive industry has undergone profound changes. The proportion of automotive electronic components has increased, and their complexity has also increased. This has posed a huge challenge to vehicle diagnosis and fault location. Currently, vehicle diagnosis mainly relies on diagnostic instruments, which are connected to the vehicle's OBD port and then diagnose each ECU one by one. For example, patent application number 201611135598.0 discloses a vehicle fault diagnosis method that includes an OBD diagnostic connector and a display screen. This fault diagnosis method relies on the vehicle's OBD interface and dedicated diagnostic equipment to achieve stable and reliable fault diagnosis.

[0003] However, the traditional diagnostic mode is not only inefficient but also has great limitations. The hardware cost of the diagnostic instrument is high and it can only be processed in professional places. Users cannot know the fault status and type in time, and cannot make timely judgments on repairs or treatments. Arriving at maintenance points or 4S stores will take up users' time due to various situations such as queuing. Therefore, the existing technical diagnostic methods are not suitable for the intelligent and Internet-based needs of new energy vehicles. Summary of the Invention

[0004] The purpose of the present invention is to overcome the shortcomings of the existing technology and provide a new energy vehicle fault diagnosis method, which performs fault diagnosis through remote diagnosis, facilitates users to actively or automatically obtain the fault status of the vehicle, promptly discovers problems and handles and repairs them, and ensures the safe and reliable operation of the vehicle.

[0005] In order to achieve the above-mentioned purpose, the technical solution adopted by the present invention is: a new energy vehicle fault diagnosis method, after the fault diagnosis mode is started, the automobile cloud platform sends a diagnostic instruction to the vehicle network module TBOX, and the vehicle network module TBOX sends a diagnostic instruction to the ECU module on the vehicle CAN, queries the current or historical fault code, and the vehicle network module uploads the fault code information to the cloud platform.

[0006] The automotive cloud platform stores the ECU diagnostic database, vehicle model, and vehicle VIN code information, issues diagnostic instructions to the corresponding vehicle based on the ECU diagnostic database, vehicle model, and vehicle VIN code information, and parses the corresponding fault results based on the fault code information obtained through feedback.

[0007] The automotive cloud platform is connected to the user's Internet of Vehicles app to receive instructions from the user and provide feedback on the execution results of the instructions.

[0008] The fault diagnosis mode starts after the trigger conditions are met, including:

[0009] (1) The user sends a fault diagnosis start signal to the car cloud platform through the car networking app;

[0010] (2) Setting the periodic fault start time corresponding to the vehicle in the automotive cloud platform, and starting the fault diagnosis mode after the periodic fault start time is reached;

[0011] (3) Each ECU module on the vehicle sends a fault diagnosis request instruction to the automotive cloud platform through TBOX, and starts the fault diagnosis mode after obtaining the confirmation signal from the automotive cloud platform.

[0012] The automotive cloud platform classifies the vehicle's fault level based on the analyzed fault information, confirms whether the vehicle can be operated and the recommended driving status of the vehicle based on the fault level, and sends the information to the user's Internet of Vehicles app; at the same time, it sends an instruction to restrict vehicle driving to the on-board TBOX, and the on-board TBOX sends a restriction instruction to the vehicle's power system, prohibiting the vehicle's power output; after the user enters the user's consent instruction in the Internet of Vehicles app, the automotive cloud platform sends a control instruction corresponding to the recommended driving status of the vehicle to TBOX, and TBOX sends a restriction release instruction to the vehicle's power system, allowing the vehicle to limit the vehicle's power output according to the recommended driving status.

[0013] The method further includes: after receiving the diagnostic instruction issued by the automobile cloud platform, if the TBOX determines that the current vehicle is in a dormant state, it detects whether the vehicle's power level is greater than a set threshold, and if not, feeds back a diagnosis cancellation result to the automobile cloud platform; if so, it issues a wake-up instruction to wake up the vehicle CAN network and wake up the corresponding on-board ECU modules in turn; then encapsulates the diagnostic request instruction into a CAN message, sends the CAN message to each ECU through the CAN bus, and obtains fault diagnosis information fed back by each ECU.

[0014] The method further includes collecting the driving environment and driving time of the vehicle while the vehicle is driving; and determining whether to automatically start fault diagnosis after the vehicle ends its driving based on the collected driving environment and driving time.

[0015] The automotive cloud platform communicates with the on-board TBOX to obtain the vehicle's real-time positioning information and navigation information. When the vehicle's navigation destination is a maintenance point recorded by the automotive cloud platform or the vehicle is at a maintenance point recorded by the automotive cloud platform, the automotive cloud platform will feed back the stored vehicle fault diagnosis information to the terminal device at the maintenance point.

[0016] Based on the UDS diagnostic communication protocol, after receiving a diagnostic request, TBOX encapsulates the diagnostic request instruction into a CAN message and sends it to each ECU on the vehicle.

[0017] A new energy vehicle fault diagnosis system includes an automobile cloud platform, TBOX, an Internet of Vehicles app, and an on-board ECU; the TBOX and the Internet of Vehicles app are both connected to the automobile cloud platform; the on-board ECU is connected to the TBOX; and the automobile cloud platform, TBOX, the Internet of Vehicles app, and the on-board ECU interact using the fault diagnosis method.

[0018] The advantages of the present invention are as follows: fault diagnosis is performed remotely, allowing users to proactively or automatically obtain the vehicle's fault status, promptly identify problems, and promptly handle and repair them, thereby ensuring the safe and reliable operation of the vehicle; the hardware used is all components from the field of Internet of Vehicles, which is low-cost, and for vehicles that already have relevant components, the cost is only the software cost, resulting in a low overall diagnostic cost; fault diagnosis can be obtained and viewed on the user side, facilitating timely user processing and improving vehicle safety; the startup control of fault diagnosis is more reasonable, meeting certain requirements for fault diagnosis, and avoiding safety hazards caused by users driving the vehicle without knowing the fault has occurred. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The following is a brief description of the contents and symbols in the drawings of the present invention:

[0020] Figure 1 Schematic diagram of the hardware composition and interaction of the fault diagnosis control solution of the present invention. DETAILED DESCRIPTION

[0021] The specific implementation of the present invention will be further explained in detail below by describing the best embodiment with reference to the accompanying drawings.

[0022] This solution provides a diagnostic control method that does not rely on maintenance centers or dedicated diagnostic instruments. It is suitable for non-professional users to evaluate the condition of their own vehicles. The hardware cost of this solution is low. It only requires the development of corresponding software in the vehicle network system to implement the diagnostic control method. It has the advantages of simplicity, reliability, easy implementation, and low cost. The specific solution is as follows:

[0023] A fault diagnosis method for new energy vehicles. After the fault diagnosis mode is activated, the vehicle cloud platform sends a diagnostic command to the vehicle networking module TBOX. The vehicle networking module TBOX sends a diagnostic command to the ECU module on the vehicle's CAN, queries the current or historical fault code, and uploads the fault code information to the cloud platform.

[0024] The hardware involved in the fault diagnosis method includes the Internet of Vehicles module TBOX, the automotive cloud platform, the Internet of Vehicles APP (mobile terminal), and various vehicle-mounted ECUs;

[0025] The Internet of Vehicles (TBOX) module is the core of vehicle-side fault diagnosis, providing data processing, control, and communication capabilities. It connects to various onboard ECUs via the vehicle's CAN network, enabling interactive communication with them. Its built-in 4G communication chip connects to the automotive cloud platform, enabling interactive control with the platform. The Internet of Vehicles (IoV) app is a mobile app on the user's phone, allowing them to input control commands, perform remote control, and view remote data. Various onboard ECUs refer to control units within the vehicle, including but not limited to BMS, VCU, and DC / DC controllers. Diagnostics are accomplished by sending diagnostic commands to these controllers via the TBOX.

[0026] The automotive cloud platform stores the ECU diagnostic database, vehicle model, and VIN code information. Based on this information, the platform issues diagnostic instructions to the corresponding vehicle and resolves the corresponding fault results based on the fault code information received in response. The platform obtains the corresponding diagnostic instructions based on the vehicle model, VIN code, and ECU diagnostic database information. These instructions are then sent to the vehicle's corresponding TBOX. To avoid errors, the vehicle model and VIN code are used to uniquely identify the vehicle to be diagnosed, allowing the fault diagnostic instructions to be sent to the vehicle to be diagnosed. Upon receiving the diagnostic instructions, the TBOX in the vehicle to be diagnosed sends them to each onboard ECU via the vehicle's CAN network. The ECUs execute the diagnostic process and, after receiving the instructions, send the fault code to the TBOX. The TBOX then uploads the information to the automotive cloud platform via the 4G network. The platform then parses the fault diagnostic code and extracts the fault diagnostic result information. This information, combined with the time of diagnosis, is then stored and displayed to the user.

[0027] In order to display to users, the car cloud platform is connected to the user's car networking app, and a connection is established between the car cloud platform and the car networking app. The car networking app displays the received fault diagnosis result information, so that users can know whether the vehicle has fault codes and fault information. At the same time, users can send remote control commands to the car cloud platform based on the car networking app, including vehicle control commands and fault diagnosis commands. Users send fault diagnosis commands to the car cloud platform through mobile phone apps, so that users can start fault diagnosis anytime and anywhere according to actual needs, realize the purpose of user self-inspection of the vehicle, improve the user's right to know, improve the user experience, and avoid the vehicle driving without the user's knowledge when there are abnormal conditions, thereby improving driving safety.

[0028] Since in this embodiment, when fault diagnosis is performed automatically, the start of fault diagnosis is conditional. It can be actively started by the user through the Internet of Vehicles app, or it can be automatically started by the car cloud platform or by each ECU. Therefore, the method of starting fault diagnosis includes at least the following:

[0029] (1) The user sends a fault diagnosis start signal to the car cloud platform through the car networking app; the car networking app is integrated with a function button for actively starting fault diagnosis. After the user triggers the function button for starting fault diagnosis through the mobile app according to actual needs, the car networking app sends a corresponding fault diagnosis start signal to the car cloud platform. After the car cloud platform receives the start signal, it sends a diagnostic instruction to the corresponding vehicle based on the ECU diagnostic database, vehicle model, and vehicle VIN code information. After receiving the fault diagnosis instruction, the vehicle TBOX starts fault diagnosis and feedbacks the corresponding fault diagnostic code.

[0030] (2) Set the periodic fault start time corresponding to the vehicle in the car cloud platform, and start the fault diagnosis mode after the periodic fault start time is reached; since the occurrence of vehicle faults is related to the vehicle's usage time, a periodic start time is set in the car cloud platform to perform fault diagnosis on the vehicle. The fault diagnosis time is set periodically based on the vehicle purchase time or the vehicle activation time of the Internet of Vehicles function. When the fault diagnosis time is reached, the car cloud platform sends the corresponding fault diagnosis instruction to the vehicle's on-board TBOX. If each year starting from the basic time point is set as a fault diagnosis time point, and the time point is set with one year as a cycle, a fault diagnosis process will be automatically started every year, so that the vehicle's operating status can be accurately and reliably monitored, fault codes can be discovered in time, and repairs can be made in time.

[0031] (3) Each on-board ECU module sends a fault diagnosis request instruction to the automotive cloud platform through TBOX, and starts the fault diagnosis mode after obtaining the confirmation signal from the automotive cloud platform. Since vehicle faults are unpredictable and have a certain degree of randomness, in order to better perform fault troubleshooting, each on-board ECU is given the permission to self-start fault diagnosis. When the on-board ECU or the on-board ECU with which it is communicating encounters an abnormality or fault during operation, it immediately sends a fault diagnosis request to TBOX. The on-board TBOX sends the fault diagnosis request to the automotive cloud platform, and then after confirmation by the automotive cloud platform, the automotive cloud platform restarts the fault diagnosis process and issues the corresponding fault diagnosis instruction.

[0032] By using at least one of the three methods above or a combination thereof to start fault diagnosis, the fault code can be diagnosed promptly and effectively, and the fault information can be discovered in a timely manner, making it convenient for users to handle and repair the fault in a timely manner, and avoiding the safety risks brought about by driving the vehicle without knowing the severity of the fault.

[0033] In a preferred solution of this embodiment, the automobile cloud platform classifies the vehicle's fault level based on the analyzed fault information, confirms whether the vehicle can be operated and the recommended driving status of the vehicle based on the fault level, and sends the result to the user's Internet of Vehicles app; at the same time, it sends an instruction to restrict the vehicle's driving to the on-board TBOX, and the on-board TBOX sends a restriction instruction to the vehicle's power system, prohibiting the vehicle's power output; after the user enters the user's consent instruction in the Internet of Vehicles app, the automobile cloud platform sends a control instruction corresponding to the recommended driving status of the vehicle to TBOX, and TBOX sends a restriction release instruction to the vehicle's power system, allowing the vehicle to limit the vehicle's power output according to the recommended driving status.

[0034] There are many types of vehicle failure results. Some failures affect the vehicle's driving safety, such as power system failures. Some failures only affect the vehicle's usage, audio and video effects, etc., and will not affect the vehicle's driving in a short time. For example, if the multimedia IVI has an abnormality, it will only affect the multimedia function and will not affect the vehicle's driving. Therefore, it is necessary to divide the failure level into failures that do not affect driving, failures that do not affect driving at low speeds, etc.; give vehicle driving suggestions according to the failure level. For example, if the failure level is a failure that does not affect driving, it is recommended that the vehicle be operated at medium and low speeds and repair and inspected as soon as possible. Medium and low speeds can be set to an upper limit speed of 60-80km / h according to actual needs; if the failure level is a failure that does not affect driving at low speeds, it is recommended that the vehicle be operated at low speeds and repair and inspected as soon as possible. The low speed is generally set to 30km / h and can be adjusted according to actual needs. Users can view the fault level and the corresponding recommended maximum driving speed through the mobile app; when the fault diagnosis classifies the fault level, a restriction instruction prohibiting the vehicle from driving will be sent to TBOX. After receiving the restriction instruction, TBOX sends an instruction to the power system to prohibit the vehicle from outputting power through the power system, thereby avoiding driving in the event of a fault; in order to improve safety and meet the needs of users to drive vehicles within a certain range, such as driving vehicles to maintenance points, certain autonomy is given. If the user confirms through the mobile app that he agrees that the vehicle can be driven under restriction, the car cloud platform will lift the instruction prohibiting the vehicle from driving through TBOX after receiving the confirmation signal, and use the speed limit instruction to limit the vehicle to the power output below the recommended maximum speed, that is, to limit the power output of the vehicle, so that the vehicle can be driven but at a slower speed, meeting the short-term driving needs of vehicle users.

[0035] In a preferred embodiment of this embodiment, after receiving a diagnostic command from the automotive cloud platform, the TBOX checks whether the vehicle's battery level is above a set threshold if it determines the vehicle is currently dormant. Otherwise, it sends a diagnostic cancellation response to the automotive cloud platform, preventing the vehicle from failing to start due to fault diagnosis under low battery conditions. If so, indicating sufficient battery life for fault diagnosis, the TBOX issues a wake-up command, waking up the vehicle's CAN network and, in turn, the corresponding onboard ECUs. The diagnostic request is then encapsulated into a CAN message, which is then sent to each ECU via the CAN bus to retrieve the fault diagnostic information provided by each ECU. Fault diagnostic commands are based on the UDS diagnostic communication protocol. Upon receiving the diagnostic request, the TBOX encapsulates the diagnostic request into a CAN message and sends it to each onboard ECU.

[0036] In this application, faults are often caused by the vehicle's driving environment. Therefore, the vehicle's driving environment and driving time can be collected while the vehicle is driving; the collected driving environment and driving time are used to determine whether to automatically start fault diagnosis after the vehicle has finished driving. Driving environment data is collected through on-board cameras and sensors such as temperature, humidity, and dust levels to determine whether the environment is a harsh environment. When it is determined to be in a harsh environment and the driving time reaches a set time threshold, it is determined that fault diagnosis needs to be started, because driving in this situation is prone to faults; the definition of a harsh environment can be pre-set based on the actual calibrated temperature, humidity, and dust level.

[0037] In a preferred solution of this embodiment, the car cloud platform communicates with the on-board TBOX to obtain the vehicle's real-time positioning information and navigation information. When the vehicle's navigation destination is a maintenance point recorded by the car cloud platform or the vehicle is at a maintenance point recorded by the car cloud platform, the car cloud platform will feed back the stored vehicle fault diagnosis information to the terminal device at the maintenance point. Through the vehicle's running trajectory or destination, the user's intention is promptly identified. If it is found that the user is heading to a maintenance point, the fault information is sent to the corresponding maintenance point, which facilitates the maintenance point to obtain information in a timely manner for analysis, understand the vehicle's fault status in advance, and prepare for subsequent repairs. The maintenance point recorded by the car cloud platform refers to the maintenance point that has a registered server address information in the car cloud platform, so that the fault information can be sent to the terminal device and server corresponding to the maintenance point.

[0038] The present application also provides a new energy vehicle fault diagnosis system, which includes a car cloud platform, TBOX, a car networking APP, and an on-board ECU; the TBOX and the car networking APP are both connected to the car cloud platform; the on-board ECU is connected to the TBOX; the car cloud platform, TBOX, the car networking APP, and the on-board ECU interact using the fault diagnosis method described in the above embodiment to achieve fault diagnosis.

[0039] This solution provides a remote fault diagnosis method for new energy vehicles. It uses the automotive cloud platform to issue diagnostic commands and query the fault status of the vehicle's ECU. The system includes the automotive cloud platform, a vehicle-to-vehicle (TBOX) module, and the vehicle's ECU modules. The automotive cloud platform issues diagnostic commands to the vehicle-to-vehicle (TBOX) module. The TBOX then sends diagnostic commands to the ECU modules on the vehicle's CAN bus via the CAN bus, querying current or historical faults and identifying the cause. The TBOX then uploads the acquired fault information to the cloud platform.

[0040] The automotive cloud platform stores the ECU diagnostic database, vehicle models, and vehicle VIN code information, and sends the collected user diagnostic requests to the remote diagnostic module TBOX, and converts the fault data returned by the remote diagnostic module TBOX into diagnostic results and displays them on the platform.

[0041] TBOX (Internet of Vehicles Module) is used to receive diagnostic commands issued by the automotive cloud platform and send them to each ECU module on the CAN line via the CAN line. TBOX then uploads the acquired diagnostic information to the cloud platform.

[0042] The vehicle ECU module develops a diagnostic database based on its own fault strategy (e.g., U007388-CAN busoff), receives diagnostic commands from the TBOX, and reports fault information. (Diagnosis complies with ISO 14229)

[0043] Example:

[0044]

[0045]

[0046] Figure 1 This is a flowchart of a remote fault diagnosis method for new energy vehicles provided by an embodiment of the present invention. The method specifically includes the following steps:

[0047] Step 1: The automotive cloud platform issues a diagnostic request;

[0048] Step 2: TBOX receives and parses the diagnostic request sent by the automotive cloud platform;

[0049] Step 3: The vehicle fault remote diagnosis method also supports a wake-up function to determine the communication status of the vehicle. If the vehicle is currently in a dormant state, a wake-up command is issued to wake up the CAN communication module, and then step 4 is executed. If the vehicle is in an awake state, step 4 is directly executed.

[0050] Step 4: Based on the UDS diagnostic communication protocol, after receiving the diagnostic request, the TBOX encapsulates the diagnostic request instruction into a CAN message and sends the CAN message to each ECU through the CAN bus;

[0051] Step 5: Each ECU receives the fault diagnosis request from TBOX and feeds back the fault information to TBOX via CAN message;

[0052] Step 6: TBOX receives the fault information fed back by each ECU and uploads it to the automotive cloud platform;

[0053] Step 7: The automotive cloud platform receives the ECU fault information fed back by TBOX and analyzes and displays it.

[0054] The vehicle fault remote diagnosis system and method of this solution is based on the vehicle UDS diagnostic system and integrated into the T-box vehicle remote communication module. It can effectively save the development cost of the entire vehicle remote diagnosis system and realize the sharing and interaction of fault information among faulty vehicles, repair shops, and vehicle manufacturers, thereby effectively reducing maintenance costs and maintenance hours and improving vehicle maintenance efficiency.

[0055] Obviously, the specific implementation of the present invention is not limited to the above-mentioned methods. As long as various non-substantial improvements are made using the method concept and technical solution of the present invention, they are all within the scope of protection of the present invention.

Claims

1. A new energy vehicle fault diagnosis method, characterized in that After the fault diagnosis mode is started, the car cloud platform sends a diagnostic command to the car networking module TBOX. The car networking module TBOX queries the current or historical fault code by sending a diagnostic command to the onboard ECU on the vehicle CAN. The car networking module then uploads the fault code information to the car cloud platform. The automobile cloud platform classifies the vehicle's fault level based on the analyzed fault information, and confirms whether the vehicle can be operated and the recommended driving state of the vehicle based on the fault level, and sends the confirmed information of whether the vehicle can be operated and the recommended driving state of the vehicle to the user's Internet of Vehicles APP; at the same time, it sends an instruction to restrict the vehicle's driving to the Internet of Vehicles module TBOX, and the Internet of Vehicles module TBOX sends a restriction instruction to the vehicle's power system to prohibit the vehicle's power output; after the user enters the user's consent instruction in the Internet of Vehicles APP, the automobile cloud platform sends a control instruction corresponding to the recommended driving state of the vehicle to the Internet of Vehicles module TBOX, and the Internet of Vehicles module TBOX sends a lifting of restriction instruction to the vehicle's power system, allowing the vehicle to limit the vehicle's power output according to the recommended driving state; The method further includes: after receiving the diagnostic instruction issued by the automotive cloud platform, the vehicle networking module TBOX detects whether the vehicle's power level is greater than a set threshold if it is determined that the vehicle is currently in a dormant state, and if not, feeds back a diagnosis cancellation result to the automotive cloud platform; if so, sends a wake-up instruction to wake up the vehicle CAN network and sequentially wake up the corresponding on-board ECUs; then encapsulates the diagnostic request instruction into a CAN message, sends the CAN message to each on-board ECU via the CAN bus, and obtains fault diagnosis information fed back by each on-board ECU; The method further includes collecting the driving environment and driving time of the vehicle while the vehicle is driving; and determining whether to automatically start fault diagnosis after the vehicle has finished driving based on the collected driving environment and driving time; The automotive cloud platform communicates with the Internet of Vehicles module TBOX to obtain the vehicle's real-time positioning information and navigation information. When the vehicle's navigation destination is a maintenance point recorded by the automotive cloud platform or the vehicle is at a maintenance point recorded by the automotive cloud platform, the automotive cloud platform will feed back the stored vehicle fault diagnosis information to the terminal device at the maintenance point.

2. A new energy vehicle fault diagnosis method as claimed in claim 1, characterized in that :The automotive cloud platform stores the ECU diagnostic database, vehicle model, and vehicle VIN code information, issues diagnostic instructions to the corresponding vehicle based on the ECU diagnostic database, vehicle model, and vehicle VIN code information, and parses the corresponding fault results based on the fault code information obtained based on the feedback.

3. A new energy vehicle fault diagnosis method as claimed in claim 1 or 2, characterized in that : The automotive cloud platform is connected to the user's Internet of Vehicles APP to receive instructions from the user and provide feedback on the execution results of the instructions.

4. A new energy vehicle fault diagnosis method as claimed in claim 1 or 2, characterized in that : Fault diagnosis mode starts after the trigger conditions are met, including: (1) The user sends a fault diagnosis start signal to the car cloud platform through the Internet of Vehicles APP; (2) Set the periodic fault start time corresponding to the vehicle in the automotive cloud platform, and start the fault diagnosis mode after the periodic fault start time is reached; (3) Each vehicle-mounted ECU sends a fault diagnosis request command to the automotive cloud platform through the Internet of Vehicles module TBOX, and starts the fault diagnosis mode after obtaining the confirmation signal from the automotive cloud platform.

5. A new energy vehicle fault diagnosis method according to claim 1, characterized in that: Based on the UDS diagnostic communication protocol, after receiving a diagnostic request, the TBOX module of the Internet of Vehicles encapsulates the diagnostic request instruction into a CAN message and sends it to each on-board ECU.

6. A new energy vehicle fault diagnosis system, characterized by: The system includes an automotive cloud platform, a vehicle networking module TBOX, a vehicle networking APP, and an on-board ECU; the vehicle networking module TBOX and the vehicle networking APP are both connected to the automotive cloud platform; the on-board ECU is connected to the vehicle networking module TBOX; the automotive cloud platform, the vehicle networking module TBOX, the vehicle networking APP, and the on-board ECU interact using the fault diagnosis method described in any one of claims 1 to 5.

Images