Vehicle diagnosis system, vehicle, method, storage medium, and program product

Abstract

The invention relates to the technical field of vehicles, in particular to a vehicle diagnosis system, a vehicle, a method, a storage medium and a program product, and the system comprises a gateway and a plurality of ECU nodes. The interaction assembly is arranged in the vehicle and used for generating a target diagnosis request according to interaction actions of a user and diagnosing the ECU nodes according to the target diagnosis request and the gateway, the interaction assembly issues the target diagnosis request to the gateway, the gateway generates a target diagnosis instruction according to the target diagnosis request, and the target diagnosis instruction is sent to the ECU nodes according to the target diagnosis instruction. And the gateway issues the target diagnosis instruction to the target ECU node, extracts feedback information of the target ECU node, sends the feedback information to the interaction component, and determines a diagnosis result of the target ECU node based on the feedback information. Therefore, the problems that EOL detection and after-sales diagnosis need special equipment, the cost is high, diagnostic equipment is not uniform in busy and idle states, the utilization rate is low, the communication stability of external equipment and an in-vehicle controller is affected by OBD connection, and the risk that communication data is stolen through an OBD interface exists are solved.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a vehicle diagnostic system, a vehicle, a method, a storage medium and a program product. Background Art

[0002] With the rapid development of the automobile manufacturing industry, people's requirements for automobile quality are also increasing. In order to ensure that every car is in the best condition before leaving the factory, a technology called EOL (End of Line) detection is widely used in modern automobile production lines. This test is usually the last process after the vehicle is assembled, which aims to verify whether the various functions of the vehicle are normal and confirm that there are no potential manufacturing defects or faults. To this end, manufacturers have designed special EOL offline diagnostic equipment, which can communicate with various controllers inside the car through the OBD (On-Board Diagnostics) interface on the vehicle, perform a series of tests to check the functionality of the vehicle, and read possible fault codes.

[0003] During the EOL detection process, technicians connect the EOL diagnostic equipment to the car's OBD interface and send instructions to the vehicle through dedicated diagnostic software. These instructions can trigger different systems or components to enter test mode, such as starting the engine, checking sensor output, or testing the braking system. In addition, the device can also read fault information in the vehicle's ECU (Electronic Control Unit) to help identify and locate the problem. Similarly, in the after-sales service of the vehicle, 4S stores will also use specially developed after-sales diagnostic equipment and corresponding software tools to maintain and repair vehicles. These tools can not only help technicians quickly and accurately find the problem, but also perform necessary software updates or firmware upgrades to ensure that the vehicle can maintain good operating conditions throughout its life cycle.

[0004] However, the existing EOL detection and after-sales maintenance solutions have some obvious limitations. First, both EOL offline equipment and after-sales diagnostic equipment need to be customized and developed according to specific vehicle models, which not only increases the cost of hardware, but also brings additional costs for software development and maintenance. Secondly, since these devices are fixedly configured, their quantity is often difficult to fully match the needs of the production line or after-sales service center, which may lead to equipment shortages during peak periods and idle equipment during low periods, affecting overall work efficiency. Third, since the diagnostic process relies on the OBD interface and its related communication links, any physical connection problems or network configuration errors may cause diagnostic interruptions or failures, which in turn affects the accuracy and timeliness of the detection. Finally, illegal intruders may obtain communication data during the diagnostic process through the OBD interface, resulting in hidden dangers in the vehicle's information security. Summary of the invention

[0005] The present application provides a vehicle diagnostic system, vehicle, method, storage medium and program product to solve the problems that EOL detection and after-sales diagnosis require dedicated equipment, the cost is high, the diagnostic equipment is unevenly busy and idle, the utilization rate is low, the communication stability between the external device and the in-vehicle controller is affected by the OBD connection, and there is a risk of communication data being stolen through the OBD interface.

[0006] The first aspect of the present application provides a vehicle diagnostic system, comprising the following steps: a gateway and multiple ECU nodes; an interactive component arranged in the vehicle, for generating a target diagnostic request based on the user's interactive actions, and diagnosing the multiple ECU nodes based on the target diagnostic request and the gateway, wherein the interactive component sends the target diagnostic request to the gateway, the gateway generates a target diagnostic instruction based on the target diagnostic request, the gateway sends the target diagnostic instruction to the target ECU node, the gateway extracts feedback information of the target ECU node, and sends the feedback information to the interactive component, and determines the diagnostic result of the target ECU node based on the feedback information.

[0007] Optionally, the interactive component includes: a display screen supporting interactive functions and a controller, wherein the controller determines a target diagnosis request according to the user's interactive action, and controls the display screen to display the target diagnosis request and feedback information.

[0008] Optionally, a virtual operation button is displayed on the display screen, a virtual operation button is selected according to an interactive action of the user, and a target diagnosis request is generated according to the corresponding virtual operation button.

[0009] Optionally, a diagnostic application is displayed on the display screen, and after a target diagnostic mode of the diagnostic application is selected, a mode interface of the target diagnostic mode is entered.

[0010] Optionally, the target diagnosis mode includes a factory offline mode and an after-sales maintenance mode, and the target diagnosis request includes a factory offline mode diagnosis request and an after-sales maintenance mode diagnosis request.

[0011] A second aspect of the present application provides a vehicle, comprising: a vehicle diagnostic system according to the first aspect.

[0012] The third aspect of the present application provides a vehicle diagnostic method, which uses the vehicle diagnostic system of the first aspect for diagnosis, and the method includes the following steps: generating a target diagnostic request based on the user's interactive action; sending the target diagnostic request to a gateway, the gateway generating a target diagnostic instruction based on the target diagnostic request, the gateway sending the target diagnostic instruction to a target ECU node, and the gateway extracting feedback information from the target ECU node; and determining a diagnostic result of the target ECU node based on the feedback information.

[0013] Optionally, a virtual operation button is selected according to the user's interactive action, and a target diagnosis request is generated according to the corresponding virtual operation button, including: selecting a virtual operation button according to the user's interactive action; and generating a target diagnosis request according to the selected virtual operation button.

[0014] The third aspect of the present application provides a computer-readable storage medium having a computer program or instructions stored thereon. When the computer program or instructions are executed, the vehicle diagnostic method of the third aspect is implemented.

[0015] The fourth aspect of the present application provides a computer program product, including a computer program or instructions, which, when executed, implements the vehicle diagnostic method of the third aspect.

[0016] Therefore, this application includes the following beneficial effects:

[0017] The vehicle diagnostic system provided by the embodiment of the present application includes a gateway, multiple ECU nodes and an interactive component arranged in the vehicle. It can generate a target diagnostic request according to the user's interactive action, and diagnose multiple ECU nodes according to the target diagnostic request and the gateway, realizing the functions of completing the EOL offline equipment and after-sales diagnostic instrument in the vehicle without connecting any equipment. At the same time, the communication data is exchanged between the controllers in the vehicle, ensuring the security of data information in the vehicle. Thus, it solves the problems of EOL detection and after-sales diagnosis requiring dedicated equipment, high cost, uneven busy and idle time of diagnostic equipment, low utilization rate, stability of communication between external equipment and in-vehicle controller affected by OBD connection, and risk of communication data being stolen through the OBD interface.

[0018] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0020] Figure 1 A structural example diagram of a vehicle diagnostic system provided according to an embodiment of the present application;

[0021] Figure 2 This is an example diagram of the EOL end-of-line and after-sales diagnostic instrument solutions for related technologies;

[0022] Figure 3 An example diagram of a vehicle diagnostic system provided according to an embodiment of the present application;

[0023] Figure 4 It is a flowchart of a vehicle diagnostic method provided according to an embodiment of the present application. DETAILED DESCRIPTION

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

[0025] The vehicle diagnostic system, vehicle, method, storage medium and program product of the embodiment of the present application are described below with reference to the accompanying drawings. In view of the problems mentioned in the above background technology that EOL detection and after-sales diagnosis require dedicated equipment, high cost, uneven busyness and idleness of diagnostic equipment, low utilization rate, OBD connection affects the stability of communication between external devices and in-vehicle controllers, and there is a risk of communication data being stolen through the OBD interface, the present application provides a vehicle diagnostic system, in which a gateway, multiple ECU nodes and an interactive component arranged in the vehicle are included, and a target diagnostic request can be generated according to the user's interactive action, and multiple ECU nodes can be diagnosed according to the target diagnostic request and the gateway, so as to realize the functions of EOL offline equipment and after-sales diagnostic instrument in the vehicle without connecting any equipment. At the same time, the communication data is exchanged between the in-vehicle controllers, ensuring the security of in-vehicle data information, thereby solving the problems that EOL detection and after-sales diagnosis require dedicated equipment, high cost, uneven busyness and idleness of diagnostic equipment, low utilization rate, OBD connection affects the stability of communication between external devices and in-vehicle controllers, and there is a risk of communication data being stolen through the OBD interface.

[0026] Specifically, Figure 1 This is a structural example diagram of a vehicle diagnostic system provided in an embodiment of the present application.

[0027] like Figure 1As shown, the vehicle diagnostic system includes: a gateway 101 , a plurality of ECU nodes 102 and an interaction component 103 .

[0028] Among them, the interactive component 103 is set in the vehicle, and is used to generate a target diagnosis request according to the user's interactive actions, and diagnose multiple ECU nodes according to the target diagnosis request and the gateway. Among them, the interactive component 103 sends the target diagnosis request to the gateway 101, the gateway 101 generates a target diagnosis instruction according to the target diagnosis request, and the gateway 101 sends the target diagnosis instruction to the target ECU node 102. The gateway 101 extracts the feedback information of the target ECU node 102 and sends the feedback information to the interactive component 103, and determines the diagnosis result of the target ECU node 102 based on the feedback information.

[0029] It is understandable that the embodiment of the present application responds to the user's operation and generates a target diagnosis request through the interactive component 103. For example, when the user interacts with the interactive component 103 through a touch screen, the component will generate a specific diagnosis request according to the user's intention, and send the target diagnosis request to the gateway 101 in the car. The gateway 101 can understand and process the target diagnosis request, and convert it into a specific target diagnosis instruction, and send it to the specified one or more ECU nodes 102. After receiving the diagnosis instruction, the designated ECU node 102 will execute the corresponding self-diagnosis program and return the diagnosis result as feedback information to the gateway 101. The gateway 101 collects the feedback information and passes it back to the interactive component 103. Finally, the interactive component 103 determines the health status or diagnosis result of the ECU node based on the feedback information received from the ECU node 102. Among them, the target diagnosis request will be described in detail below and will not be repeated here.

[0030] Therefore, the embodiments of the present application can integrate EOL detection and after-sales diagnosis functions in the vehicle. There is no need to use professional equipment for detection and diagnosis. The diagnostic function can be completed directly by using the functions integrated in the vehicle, thereby greatly improving the convenience of diagnosis, facilitating timely and convenient inspections by diagnostic personnel, improving the efficiency of diagnosis, and reducing the cost of diagnosis. There is no need to consider the compatibility of the vehicle model and professional equipment during diagnosis. It is more applicable and can achieve quick and efficient fault diagnosis.

[0031] In the embodiment of the present application, the interactive component 103 includes: a display screen and a controller supporting interactive functions, wherein the controller determines a target diagnosis request according to the user's interactive action, and controls the display screen to display the target diagnosis request and feedback information.

[0032] It can be understood that the interactive component 103 in the embodiment of the present application includes a display screen that supports interactive functions and a controller. The display screen that supports interactive functions means that the user can interact with the system by touching the screen, such as clicking, sliding the screen, etc.; the controller can determine the target diagnostic request based on the user's interactive actions on the display screen, and control the display screen to provide visual feedback, so that the user can intuitively see the result of the request being executed.

[0033] In an embodiment of the present application, a virtual operation button is displayed on a display screen, a virtual operation button is selected according to an interactive action of a user, and a target diagnosis request is generated according to the corresponding virtual operation button.

[0034] Among them, the virtual operation buttons displayed on the display screen refer to graphic elements that exist on the display screen in digital form, and the user can interact with the system directly by touching these buttons.

[0035] It can be understood that in the embodiment of the present application, virtual operation buttons for corresponding operations can be displayed on the display screen. The user can select and touch the virtual operation buttons displayed on the display screen to interact with the system according to his or her own operation needs. After the system obtains the user's interaction intention based on the corresponding virtual operation button, it generates a target diagnosis request.

[0036] In an embodiment of the present application, a diagnostic application is displayed on the display screen, and after a target diagnostic mode of the diagnostic application is selected, a mode interface of the target diagnostic mode is entered.

[0037] It can be understood that in the embodiment of the present application, the virtual operation buttons for the corresponding operations displayed on the display screen include a button for the diagnostic application, and the user can enter the diagnostic application through the button, and select the target diagnostic mode of the application, enter the mode interface of the target diagnostic mode, and perform diagnosis. The target diagnostic mode will be described in detail below and will not be repeated here.

[0038] In the embodiment of the present application, the target diagnosis mode includes a factory offline mode and an after-sales maintenance mode, and the target diagnosis request includes a factory offline mode diagnosis request and an after-sales maintenance mode diagnosis request.

[0039] Among them, factory off-line refers to a series of comprehensive tests carried out when the vehicle completes all assembly steps and is ready to leave the factory production line. The factory off-line mode is applicable to the situation when the factory is off-line; the after-sales maintenance mode refers to the diagnostic mode used for daily maintenance or troubleshooting after the vehicle has been sold and put into use; the factory off-line mode diagnostic request refers to the diagnostic request made in the factory off-line mode, the purpose is to conduct comprehensive EOL testing to ensure that all functions of the vehicle are normal; the after-sales maintenance mode diagnostic request refers to the diagnostic request made in the after-sales stage of the car, which is used to find and solve problems encountered during the use of the vehicle.

[0040] It can be understood that in the embodiment of the present application, the target diagnostic mode includes a factory offline mode and an after-sales maintenance mode, and the target diagnostic request includes a factory offline mode diagnostic request and an after-sales maintenance mode diagnostic request, which are respectively used for the diagnostic conditions when the vehicle is offline and the diagnostic conditions after the vehicle is sold.

[0041] According to the vehicle diagnostic system proposed in the embodiment of the present application, through the gateway, multiple ECU nodes and interactive components arranged in the vehicle, a target diagnostic request can be generated according to the user's interactive actions, and multiple ECU nodes can be diagnosed according to the target diagnostic request and the gateway, thereby completing the functions of EOL offline equipment and after-sales diagnostic instruments in the vehicle without connecting any equipment. At the same time, communication data are exchanged between controllers in the vehicle, ensuring the security of data information in the vehicle.

[0042] The vehicle diagnostic system provided in the embodiment of the present application is further described below through a specific example.

[0043] like Figure 2 As shown in the figure, in the current EOL offline and after-sales maintenance solutions, the EOL offline diagnostic equipment and after-sales diagnostic instrument are connected to edge nodes such as CGW (Central Gateway) through the vehicle OBD interface. When the EOL is offline, the device will issue a diagnostic instruction, and the gateway will forward it to each controller and send the reply result back to the device, thereby realizing vehicle function control, data writing, fault reading and other processes; after-sales diagnosis is similar, connected to the gateway through OBD, and through the diagnostic service to read information, read faults, and perform software upgrades on the ECU in the vehicle.

[0044] Figure 3 An example diagram of a vehicle diagnostic system provided in this embodiment, such as Figure 3 As shown in the figure, the display functions of EOL offline equipment and after-sales diagnostic instruments are replaced by IVI (In-Vehicle Infotainment) and display screens. After the factory and after-sales operators enter the "factory offline mode" or "after-sales maintenance mode" on the vehicle screen, they click the corresponding operation button (such as reading fault codes). The Diag App (Diagnosis Application) or browser running these two modes on the IVI will send the operation request to the gateway. The gateway generates a diagnostic instruction based on the request and sends it to the corresponding ECU node. After the ECU node replies, the gateway extracts the relevant information and returns it to the IVI for result display.

[0045] Taking the factory operator's query of EMS (Engine Management System) controller fault information as an example, the implementation process is as follows:

[0046] 1. The operator opens the Diag App on the IVI screen and clicks "Factory End-of-Line Detection Mode" to enter the EOL detection mode interface. One of the options is to read the fault code. Select the EMS controller in the drop-down box and click "Read"

[0047] 2. Diag App sends the "Read DTC:EMS" request message to the gateway controller

[0048] 3. After receiving the request, the Diag Master in the CGW generates a diagnostic instruction 0x780 03 19 02 09 and calls the diagnostic interface to send the above diagnostic instruction to the EMS controller.

[0049] 4. After receiving the diagnostic command, the EMS controller returns the fault information 0x788 xx 59 02xx xxxxxxxx. After receiving the reply information, the gateway controller sends the fault information (xx xxxxxxxx) to the IVI controller, and the IVI controller displays the information.

[0050] An embodiment of the present application also provides a vehicle, which includes the above-mentioned vehicle diagnostic system.

[0051] The vehicle diagnosis method proposed according to the embodiment of the present application is described below with reference to the accompanying drawings.

[0052] Figure 4 It is a flow chart of a vehicle diagnostic method provided in an embodiment of the present application.

[0053] like Figure 4 As shown, the vehicle diagnosis method includes the following steps:

[0054] In step S201 , a target diagnosis request is generated according to the user's interactive action.

[0055] The user's interactive actions are obtained through the display screen, and the target diagnosis request is generated by the controller of the interactive component in the system.

[0056] It is understandable that the embodiments of the present application can obtain the user's interaction intention through an interactive display screen, and generate a corresponding target diagnosis request through a controller in the interactive component.

[0057] In an embodiment of the present application, a virtual operation button is selected according to the user's interactive action, and a target diagnosis request is generated according to the corresponding virtual operation button, including: selecting a virtual operation button according to the user's interactive action; and generating a target diagnosis request according to the selected virtual operation button.

[0058] It can be understood that in the embodiment of the present application, the user can interact with the virtual operation button to determine the user's intention through the user's operation, and then the system generates a target diagnosis request according to the user's intention to start the corresponding diagnosis process.

[0059] In step S202, a target diagnosis request is sent to the gateway, the gateway generates a target diagnosis instruction according to the target diagnosis request, the gateway sends the target diagnosis instruction to the target ECU node, and the gateway extracts feedback information of the target ECU node.

[0060] It can be understood that the embodiment of the present application utilizes an interactive component to send a target diagnostic request to a gateway. The gateway generates corresponding diagnostic instructions based on the request and sends these instructions to a designated ECU node to perform a diagnostic task. After the ECU node completes the diagnostic task, it sends feedback information to the gateway. The gateway collects feedback information from these ECU nodes and completes the extraction of diagnostic data.

[0061] In step S203 , the diagnosis result of the target ECU node is determined based on the feedback information.

[0062] It can be understood that in the embodiment of the present application, after the gateway obtains the feedback information, it can determine the diagnostic result of the target ECU node through the feedback information, and use the display screen to feed back the result to the user.

[0063] It should be noted that the aforementioned explanations of the vehicle diagnostic system embodiment are also applicable to the vehicle diagnostic method of this embodiment, and will not be repeated here.

[0064] According to the vehicle diagnosis method proposed in the embodiment of the present application, a target diagnosis request is generated through the user's interactive actions, and the request is sent to the gateway. The gateway generates corresponding diagnostic instructions based on the request and sends these instructions to the target ECU node for diagnosis. After the diagnosis, the gateway collects feedback information from the target ECU node and determines the diagnosis result based on this information, thereby realizing the functions of EOL offline equipment and after-sales diagnostic instrument in the vehicle without connecting any equipment. At the same time, communication data is exchanged between controllers in the vehicle, ensuring the security of data information in the vehicle.

[0065] An embodiment of the present application also provides a computer-readable storage medium on which a computer program or instruction is stored. When the computer program or instruction is executed, the above-mentioned vehicle diagnostic method is implemented.

[0066] An embodiment of the present application also provides a computer program product, including a computer program or instructions, which, when executed, implements the above-mentioned vehicle diagnostic method.

[0067] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms are not necessarily directed to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0068] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0069] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or N executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0070] It should be understood that the various parts of the present application can be implemented in hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, the steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array, a field programmable gate array, etc.

[0071] A person of ordinary skill in the art may understand that all or part of the steps carried by the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the above-mentioned program may be stored in a computer-readable storage medium, which, when executed, includes one of the steps of the method embodiment or a combination thereof.

[0072] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in the field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A vehicle diagnostic system, characterized in that: include: Gateway and multiple ECU nodes; An interactive component disposed in the vehicle is used to generate a target diagnosis request according to the user's interactive action, and diagnose the multiple ECU nodes according to the target diagnosis request and the gateway, wherein: The interactive component sends the target diagnostic request to the gateway, and the gateway generates a target diagnostic instruction based on the target diagnostic request. The gateway sends the target diagnostic instruction to the target ECU node, and the gateway extracts feedback information of the target ECU node and sends the feedback information to the interactive component, and determines the diagnostic result of the target ECU node based on the feedback information.

2. The vehicle diagnostic system according to claim 1, characterized in that: The interactive component includes: a display screen and a controller supporting interactive functions, wherein: The controller determines a target diagnosis request according to the user's interactive action, and controls the display screen to display the target diagnosis request and the feedback information.

3. The vehicle diagnostic system according to claim 2, characterized in that: The display screen displays virtual operation buttons, selects a virtual operation button according to an interactive action of a user, and generates the target diagnosis request according to the corresponding virtual operation button.

4. The vehicle diagnostic system according to claim 2, characterized in that: A diagnostic application is displayed on the display screen, and after a target diagnostic mode of the diagnostic application is selected, a mode interface of the target diagnostic mode is entered.

5. The vehicle diagnostic system according to claim 4, characterized in that: The target diagnosis mode includes a factory offline mode and an after-sales maintenance mode, and the target diagnosis request includes a factory offline mode diagnosis request and an after-sales maintenance mode diagnosis request.

6. A vehicle, characterized in that: A vehicle diagnostic system comprising any one of claims 1-5.

7. A vehicle diagnostic method, characterized in that: The method uses the vehicle diagnostic system according to any one of claims 1 to 5 for diagnosis, wherein the method comprises the following steps: Generate a target diagnosis request based on the user's interactive actions; Sending the target diagnosis request to the gateway, the gateway generating a target diagnosis instruction according to the target diagnosis request, the gateway sending the target diagnosis instruction to the target ECU node, and the gateway extracting feedback information of the target ECU node; A diagnosis result of the target ECU node is determined based on the feedback information.

8. The vehicle diagnostic method according to claim 7, characterized in that: The step of selecting a virtual operation button according to the user's interactive action and generating the target diagnosis request according to the corresponding virtual operation button includes: Select a virtual operation button according to the user's interactive action; The target diagnosis request is generated according to the selected virtual operation button.

9. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed, the vehicle diagnostic method according to claim 7 or 8 is implemented.

10. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed, the vehicle diagnostic method according to claim 7 or 8 is implemented.

Images