Equipment diagnosis system

Abstract

The invention provides an equipment diagnosis system, which is applied to the technical field of vehicle diagnosis, and comprises an interaction module used for obtaining reference data and triggering operation; the process module is used for obtaining a diagnosis program carrying diagnosis instruction information; under the condition that the triggering operation is received, executing a corresponding diagnosis program to generate a calling instruction and sending the calling instruction to the diagnosis module; the calling instruction is used for indicating a target diagnosis instruction corresponding to the diagnosis instruction information; the diagnosis module is used for obtaining a target diagnosis instruction; under the condition that the calling instruction is received, a corresponding target diagnosis instruction is sent to the to-be-detected device; the to-be-detected equipment is used for responding to the target diagnosis instruction and returning response data to the analysis module; and the analysis module is used for determining a diagnosis function corresponding to the response data and executing the diagnosis function so as to compare the response data with the reference data and obtain a diagnosis result. The vehicle production efficiency can be improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of vehicle diagnosis technology, and in particular to a device diagnosis system. Background Art

[0002] The vehicle end-of-line electrical inspection (EDI) is an inspection of the vehicle's electrical system performed immediately after production is complete and the vehicle is about to roll off the assembly line. This inspection ensures that all components within the vehicle are functioning properly, ensuring the vehicle can start and function normally. This helps identify potential safety hazards and prevent dangerous situations while the vehicle is in motion.

[0003] In the related technology, a diagnostic instrument is used to diagnose the equipment in the vehicle when the vehicle is off the production line. If there is a problem, the problem is recorded and located on site.

[0004] However, diagnosing the equipment in the vehicle when it is off the production line will require pausing the production line to locate the problem, and the equipment in the vehicle will also need to be replaced, resulting in lower overall production efficiency. Summary of the Invention

[0005] In view of the above problems, embodiments of the present application are proposed to provide a device diagnostic system that overcomes the above problems or at least partially solves the above problems.

[0006] The present application discloses a device diagnosis system, which includes:

[0007] The interaction module is used to obtain reference data and trigger operations;

[0008] The process module is used to obtain a diagnostic program carrying diagnostic instruction information; when receiving the trigger operation, execute the corresponding diagnostic program to generate a call instruction and send it to the diagnostic module; the call instruction is used to indicate a target diagnostic instruction corresponding to the diagnostic instruction information;

[0009] The diagnostic module is used to obtain a target diagnostic instruction; upon receiving the call instruction, the diagnostic module sends the corresponding target diagnostic instruction to the device to be inspected; the device to be inspected is used to respond to the target diagnostic instruction and return response data to the parsing module;

[0010] The parsing module is used to determine a diagnostic function corresponding to the response data and execute the diagnostic function to compare the response data with the reference data and obtain a diagnostic result.

[0011] Optionally, the diagnostic program includes multiple diagnostic instruction information, and different diagnostic instruction information is used to generate different call instructions; the process module is used to:

[0012] executing the diagnostic program carrying multiple diagnostic instruction information to generate a first call instruction according to the first diagnostic instruction information among the multiple diagnostic instruction information;

[0013] When the response data corresponding to the first call instruction is received, the next call instruction is generated according to the next diagnostic instruction information until no response data corresponding to the previous call instruction is received, or each diagnostic instruction information in the diagnostic program is traversed.

[0014] Optionally, the interaction module includes an input control, a trigger control, and a display control;

[0015] The input control is used for the user to input reference data; the trigger control is used for the user to perform a trigger operation; and the display control is used to display the diagnosis result.

[0016] Optionally, the process module is used to:

[0017] Upon receiving the trigger operation, determining a target trigger control corresponding to the trigger operation;

[0018] determining a target diagnostic program corresponding to the target trigger control, executing the target diagnostic program to generate a call instruction and sending it to the diagnostic module;

[0019] The trigger control includes at least one diagnostic control; each diagnostic control corresponds to a respective diagnostic program; and the diagnostic instruction information in different diagnostic programs is at least partially different.

[0020] Optionally, the process module is used to:

[0021] Create a new script to obtain the script to be edited, or determine that an existing script is the script to be edited;

[0022] For the script to be edited, triggering an instruction selection interface corresponding to the script to be edited, determining diagnostic instruction information in the instruction selection interface, and adding the diagnostic instruction information to the script to be edited;

[0023] A diagnostic program is generated based on the script to be edited that carries the diagnostic instruction information.

[0024] Optionally, the diagnostic module is further configured to:

[0025] Determine a target configuration interface among multiple configuration interfaces corresponding to the diagnosis module according to the device information of the device to be inspected;

[0026] Determining a target controller area network corresponding to the device information among a plurality of controller area networks, and determining a target communication protocol corresponding to the device information among a plurality of communication protocols;

[0027] Determining a target communication address of the device to be inspected in the target controller local area network, configuring a preset communication address in the target configuration interface as the target communication address, and generating a diagnostic tag associated with the device to be inspected and the target communication protocol;

[0028] Diagnostic instruction information is determined in the target configuration interface, and a diagnostic instruction is generated based on the diagnostic instruction information and the diagnostic tag.

[0029] Optionally, the parsing module is further configured to:

[0030] In the message editing interface corresponding to the parsing module, add an external message and associate the external message with the diagnostic instruction information to generate a diagnostic function corresponding to the diagnostic instruction information;

[0031] Target diagnostic instruction information corresponding to the response data and a target diagnostic function corresponding to the target diagnostic instruction information are determined.

[0032] Optionally, the system further includes a state management module, which is configured to:

[0033] In the application signal interface corresponding to the state management module, add an application signal and configure the signal type of the application signal to be a state coding type;

[0034] In the case where the signal type is the status coding type, adding multiple status values ​​in the status description interface corresponding to the application signal;

[0035] determining a corresponding first target state value among a plurality of state values ​​according to the diagnosis result, and setting the state value of the application signal to the first target state value;

[0036] Optionally, at least one of the interaction module, the process module, the diagnosis module, and the analysis module is configured to:

[0037] According to the respective executed actions, a corresponding second target state value is determined among the multiple state values, and the state value of the application signal is set to the second target state value.

[0038] Optionally, each status value is associated with a corresponding status name; the system includes a first module and multiple second modules, the first module is a module for setting the status value of the application signal; the second module is a module for not setting the status value of the application signal, and the second module is used to:

[0039] In the case where the first module sets the state value of the application signal, the first target state value or the second target state value is read, and the corresponding target state name is determined to complete state synchronization.

[0040] In implementing the embodiment of the present application, the interaction module obtains reference data and a trigger operation. When the process module receives the trigger operation, it executes the diagnostic program and generates a call instruction and sends it to the diagnostic module. When the diagnostic module receives the call instruction, the diagnostic module obtains the target diagnostic instruction. When the call instruction is received, the corresponding target diagnostic instruction is sent to the device to be inspected. The device to be inspected responds to the target diagnostic instruction and returns response data to the parsing module. When the parsing module receives the response data, it determines the diagnostic function corresponding to the response data, executes the diagnostic function, compares the response data with the reference data, and obtains a diagnostic result. Therefore, there is no need to rely on the entire vehicle to be inspected before diagnosing the device to be inspected in the entire vehicle. Instead, by generating a diagnostic instruction and having the device to be inspected return response data, the response data is compared with the reference data to obtain a diagnostic result. This allows for direct and simulated testing of the individual device to be inspected in advance for diagnosis, avoiding the need to suspend the production line when a problem occurs with the device to be inspected, and avoiding the tedious replacement of the device to be inspected in the entire vehicle, thereby ultimately improving vehicle production efficiency as a whole. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 This is a block diagram of a device diagnostic system provided by an embodiment of the present application;

[0042] Figure 2 is a schematic diagram of a diagnostic scenario provided by an embodiment of the present application;

[0043] Figure 3 Schematic diagram of the offline electrical inspection and diagnosis architecture provided by an embodiment of the present application;

[0044] Figure 4 This is a block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The following describes exemplary embodiments of the present application in more detail with reference to the accompanying drawings. Although exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.

[0046] End-of-Line Testing (EOL) refers to a series of inspections conducted after a vehicle completes assembly line production to ensure it meets design requirements and quality standards. EOL electrical testing, a specialized component of EOL testing, primarily focuses on checking the functionality of the vehicle's electrical and electronic systems to ensure all electronic components are functioning properly. For example, this includes diagnosing the Electronic Control Unit (ECU).

[0047] During the off-line electrical inspection of vehicles, if a device fails, the impact on the production line may include: 1. Reduced production efficiency, time-consuming troubleshooting, and production line downtime to identify the cause of the problem. Troubleshooting is time-consuming and often involves multiple stages, which can be very time-consuming. 2. Increased costs. These include direct costs for replacing the device under inspection, indirect costs for losses caused by production line downtime, and additional labor costs.

[0048] Figure 1 This is a block diagram of a device diagnostic system provided by an embodiment of the present application, the system comprising:

[0049] The interaction module 101 is used to obtain reference data and trigger operations.

[0050] In the embodiments of the present application, the device diagnostic system can be deployed on a diagnostic device with data processing capabilities, such as a computer, without specific limitation. The computer can be installed with diagnostic software tools, such as VSPY (Vehicle Spy), MaxiSys, OpenECU, and other diagnostic tools, without specific limitation.

[0051] Figure 2 is a schematic diagram of a diagnostic scenario provided by an embodiment of the present application; Figure 2 The diagram includes scenarios 1 and 2. Scenario 1 includes diagnostic device 201 equipped with diagnostic tools and device 202 to be inspected, indicating that diagnostic device 201 can directly diagnose individual device 202. Scenario 2 includes diagnostic device 201 and vehicle 203, indicating that diagnostics can also be performed on devices within vehicle 203.

[0052] The device diagnostic system can use diagnostic tools to construct interactive modules, process modules, diagnostic modules, parsing modules, and other modules, without specific limitations here. For example, constructing an interactive module can involve using diagnostic tools to create input components such as text boxes and drop-down menus for entering reference data, as well as interactive elements such as buttons and checkboxes for triggering actions. Event handlers can also be configured to capture user actions on these components. When a user enters reference data in a text box, the program listens for these input events and stores the input in a specific variable.

[0053] When a user clicks a button, the associated event handler is called, which can execute the corresponding logic, such as initiating an electrical inspection. Furthermore, the input reference data can be formatted and validated, checking for correct data types and values ​​within a reasonable range. Each of these modules can be modified and adapted from existing functional modules in the diagnostic tool.

[0054] The interaction module monitors the state changes of input devices (such as keyboards, mice, and touch screens) in real time. Upon detecting user input, the module captures the user's input data and performs processing operations, such as encoding it according to a specific data format. The module also identifies the type of operation (such as clicking a button or selecting a menu) and generates corresponding event messages. The module then uses the system's communication mechanisms to send the encoded data and event messages to other relevant modules in the system, such as the control module and the parsing module, for subsequent processing and response.

[0055] Among them, the reference data can be standard data of the vehicle in a normal state or in compliance with specific requirements. For example, it is information such as the identification number (ID, Identification) and vehicle identification code (VIN, Vehicle Identification Number) of the device to be inspected. The reference data can also be data used to describe whether the device to be inspected has specific functions or services. For example, specific functions or services may include diagnostic session control (Diagnostic Session Control) service, security access (Security Access) service, write data service, etc. Each specific function or service can have corresponding reference data. For example, the reference data of the write data service can be "6e 12", which means that the write data service responds positively and writes the input corresponding to the identifier 12 to the device to be inspected. The specific content of the reference data is not limited here.

[0056] The process module 102 is used to obtain a diagnostic program carrying diagnostic instruction information; when the trigger operation is received, the corresponding diagnostic program is executed to generate a call instruction and send it to the diagnostic module; the call instruction is used to indicate the target diagnostic instruction corresponding to the diagnostic instruction information.

[0057] The interactive module allows users to interact with the diagnostic system and monitors user actions. For example, when a user triggers an action, the interactive module captures the action event and converts it into a recognizable signal.

[0058] When the process module receives a trigger signal from the interaction module, it can execute corresponding operations according to pre-defined logic, such as executing a diagnostic program that carries diagnostic instruction information. The diagnostic program can be a pre-written script that contains diagnostic instruction information. When the process module executes the script, it can generate a call instruction based on the diagnostic instruction information. Based on the call instruction, the diagnostic module can determine the diagnostic instruction to perform a specific diagnostic task.

[0059] Diagnostic instruction information can be used to distinguish and identify different diagnostic instructions. For example, specific functions or services may include diagnostic session control services, security access services, and data writing services. Each service to be diagnosed can correspond to a different diagnostic instruction. The diagnostic instruction information can be an identifier. For example, the diagnostic instruction information for the diagnostic session control service can be identifier 10, the diagnostic instruction information for the security access service can be identifier 27, and the diagnostic instruction information for the data writing service can be identifier 2e. The diagnostic instruction information can also be an instruction name. For example, the diagnostic instruction information for the diagnostic session control service can be Diagnostic Session Control, and the diagnostic instruction information for the security access service can be Security Access. The type of diagnostic instruction information is not specifically limited here.

[0060] The process module can generate a call instruction carrying the specific diagnostic instruction information based on the specific diagnostic instruction information, and send the call instruction to the diagnostic module, thereby controlling the entire diagnostic process.

[0061] The diagnostic module 103 is used to obtain a target diagnostic instruction; upon receiving the call instruction, the corresponding target diagnostic instruction is sent to the device to be inspected; the device to be inspected is used to respond to the target diagnostic instruction and return response data to the parsing module.

[0062] The diagnostic module can manage multiple diagnostic instructions, each used to perform a different diagnostic task. When the diagnostic module receives a call instruction from the process module, which contains the specific diagnostic instruction information to be executed, it can parse the call instruction and extract the target diagnostic instruction information. Since the instruction information of different diagnostic instructions is different, the target diagnostic instruction can be determined based on the target diagnostic instruction information.

[0063] The devices under test are typically various electronic control units on a vehicle. These devices are capable of receiving diagnostic commands and performing corresponding processing. The diagnostic module sends the target diagnostic command to the device under test, which then performs the corresponding operation, such as reading or writing specific data or automatically performing a functional test.

[0064] After executing the operation, the device under test can generate response data. The response data contains information about the results of executing the diagnostic instruction, which may be the requested data, operation status feedback, etc. The device under test returns the response data to the analysis module, which analyzes the response data.

[0065] For example, the response data corresponding to the content of the reference data described above may include data such as the vehicle VIN code or the ID of the device under inspection. Furthermore, when diagnosing a specific function or service, the response data corresponding to the diagnostic data write service may be "6e 12," indicating that the data write service responded positively and completed the data write corresponding to identifier 12. However, the response data may also indicate a negative response, such as "7F 2e 11," where 7F is the negative response service identifier, 2e represents the data write service, and 11 is a negative response code indicating the specific error type encountered when processing the request. Furthermore, negative response codes may include: 11, Service Not Supported, indicating that the device under inspection does not support the 2e service; 12, Sub-Function Not Supported, indicating that specific data writes are not supported within the 2e service; 22, Condition Not Satisfied, for example, the device under inspection is in a state where data writing is not permitted; and 31, The write operation cannot be completed and the requested action is not implemented. The specific content of the response data is not specifically limited herein.

[0066] The analysis module 104 is configured to determine a diagnostic function corresponding to the response data and execute the diagnostic function to compare the response data with the reference data and obtain a diagnostic result.

[0067] After receiving the response data from the device under test, the parsing module processes it based on a diagnostic function. A diagnostic function is a predefined set of algorithms and logic rules, each associated with a specific type of response data. The function compares the received response data with reference data previously entered by the user. Because the reference data represents the vehicle's normal state or standard data that meets specific requirements, the parsing module can determine whether the device under test is operating normally through this comparison, thereby generating a diagnostic result.

[0068] The parsing module can maintain a diagnostic function library that stores diagnostic functions corresponding to different diagnostic instructions and response data types. When the parsing module receives response data, it can search the diagnostic function library for the corresponding diagnostic function based on the characteristics of the response data, such as the data format and service ID.

[0069] After determining the corresponding diagnostic function, the parsing module can call the function and pass the response data and reference data as parameters to the diagnostic function. The diagnostic function performs comparison operations internally, such as comparing whether the response data and reference data are consistent, the size of the numerical value, judging whether the data range meets the requirements, checking the logical relationship of the data, etc., so as to determine whether there is a fault in the equipment to be inspected.

[0070] The diagnostic function can then return the comparison results to the parsing module, which outputs them as diagnostic results and can present them to the user in the form of intuitive text descriptions, fault codes, or charts.

[0071] For example, for a data write service diagnosis, the reference data could be "6e 12." If the response data is also "6e 12," the diagnosis could be qualified. If the response data is "7F 2e 11," the diagnosis could be unqualified. Regarding the vehicle VIN code, if the VIN code in the response data returned by the device under test doesn't match the VIN code in the reference data, the diagnosis could be unqualified. If the VIN code in the response data matches the VIN code in the reference data, the diagnosis could be qualified.

[0072] In summary, in the implementation of the embodiment of the present application, the interaction module obtains reference data and trigger operations. When the process module receives the trigger operation, it executes the diagnostic program and generates a call instruction and sends it to the diagnostic module. When the diagnostic module receives the call instruction, the diagnostic module obtains the target diagnostic instruction. When the call instruction is received, the corresponding target diagnostic instruction is sent to the device to be inspected. The device to be inspected responds to the target diagnostic instruction and returns response data to the parsing module. When the parsing module receives the response data, it determines the diagnostic function corresponding to the response data, executes the diagnostic function, compares the response data with the reference data, and obtains the diagnostic result. Therefore, there is no need to rely on the whole vehicle to be inspected before diagnosing the device to be inspected in the whole vehicle after it is off the line. Instead, by generating a diagnostic instruction and having the device to be inspected return the response data, and then comparing the response data with the reference data, a diagnostic result is obtained. The individual device to be inspected can be simulated and tested in advance and directly for diagnosis, avoiding the need to suspend the production line when a problem occurs with the device to be inspected, and avoiding the tedious replacement operation of the device to be inspected in the whole vehicle, thereby ultimately improving the overall vehicle production efficiency.

[0073] Figure 3 Schematic diagram of the offline electrical inspection and diagnosis architecture provided by an embodiment of the present application; Figure 3 The system includes an interaction module 301, a process module 302, a diagnostic module 303, a parsing module 304, and a device to be inspected 305. The interaction module 301 obtains reference data and triggers operations. The process module 302 generates a call instruction and sends it to the diagnostic module 303. The diagnostic module 303 sends the target diagnostic instruction to the device to be inspected 305. The device to be inspected 306 returns response data to the parsing module 305. The parsing module 304 executes the diagnostic function to obtain the diagnostic result. In addition, the diagnostic architecture can also include a vehicle simulation switch 306 and a vehicle simulation module 307. The vehicle simulation module 307 simulates the signal transmission and reception and logic processing of the entire vehicle. The vehicle simulation switch 306 can control the operation and shutdown of the vehicle simulation module 308.

[0074] Optionally, the interaction module includes an input control, a trigger control, and a display control;

[0075] The input control is used for the user to input reference data; the trigger control is used for the user to perform a trigger operation; and the display control is used to display the diagnosis result.

[0076] In an embodiment of the present application, for the diagnostic tool VSPY, the graphical panel interface can be controlled to open based on the Measurement and GraphicalPanels trigger path. A display control, such as an information display box, can be created by adding a Text Entry component. The information display box is used to display various information, such as diagnostic results from the analysis module and received response messages. The Text Entry component can display various information, such as text, and the size, position, and display format of the display control can be configured to suit different display requirements.

[0077] In the graphical panel interface, you can add trigger controls such as diagnostic buttons through Function Block Button. The button is the entry point for users to trigger diagnostic operations. You can also add input controls such as text input boxes through Text Entry, where users can enter the required parameters. These parameters can be synchronized to the Function module and CCode Interface module, allowing each module to work together under the same data source, avoiding data inconsistencies and facilitating subsequent parsing and processing. You can also add a description box through Text Display. The description box is used to explain the meaning and function of the parameter. For example, if the input parameter is a vehicle VIN code, the description box can display "Please enter the 17-digit vehicle VIN code."

[0078] Based on the above input controls, trigger controls, and display controls, an interaction module is constructed. It is understandable that the input controls, trigger controls, and display controls are the visual components of the interaction module. The interaction module also needs to include other components such as event handling functions and monitoring functions to fully realize the various functions of the interaction module.

[0079] By implementing the embodiments of the present application, an interactive module is constructed through input controls, trigger controls and display controls, allowing users to conveniently input key parameters and avoid complex operations; the diagnostic process can be triggered with one click through the trigger control, greatly improving operational efficiency; the display control can provide intuitive feedback of diagnostic results and device status to the user, making it easier for the user to understand the device status, thereby improving the overall interaction efficiency of the diagnostic process.

[0080] Optionally, the diagnostic program includes multiple diagnostic instruction information, and different diagnostic instruction information is used to generate different call instructions; the process module is used to:

[0081] executing the diagnostic program carrying multiple diagnostic instruction information to generate a first call instruction according to the first diagnostic instruction information among the multiple diagnostic instruction information;

[0082] When the response data corresponding to the first call instruction is received, the next call instruction is generated according to the next diagnostic instruction information until no response data corresponding to the previous call instruction is received, or each diagnostic instruction information in the diagnostic program is traversed.

[0083] In an embodiment of the present application, when the process module executes the diagnostic program, the triggering process module can first read the diagnostic instruction information in the script one by one, generate calling instructions, and thus complete each diagnostic task one by one.

[0084] The process module sends the first call instruction to the diagnostic module, which then sends the first target diagnostic instruction to the device under test. After receiving the diagnostic instruction, the device under test processes it accordingly and returns a response. The parsing module receives and parses this response data.

[0085] For the first diagnostic instruction information and the first call instruction, when the parsing module receives the corresponding response data, it means that the device to be tested has processed the first target diagnostic instruction and the corresponding diagnostic task has been completed, and then the next diagnostic task can be continued.

[0086] When the parsing module receives the response data corresponding to the first call instruction, similarly, the trigger process module continues to generate the next call instruction based on the next diagnostic instruction information and sends it to the diagnostic module. The diagnostic module sends the next target diagnostic instruction to the device to be tested. After the device to be tested completes the target diagnostic instruction and returns the response data, the current diagnostic task is completed.

[0087] It is understandable that when the call instruction is received by the diagnostic module, the correct process should be that the diagnostic module sends the target diagnostic instruction to the device to be tested, and the device to be tested returns the response data. However, in this process, there may be different problems in various links (such as communication failures or problems with the device to be tested), resulting in the parsing module not receiving the response data corresponding to the previous call instruction. This means that the current diagnostic task cannot be carried out normally. At this time, the diagnostic process can be stopped to troubleshoot the problem. When the diagnostic device can directly obtain the cause of the problem, the diagnostic device can output an error code to remind the user. In addition, it can also be that all diagnostic instruction information in the diagnostic program is traversed and completed, each diagnostic task is executed normally, and the entire diagnostic process is completed.

[0088] For example, the three diagnostic instruction information contained in the diagnostic program can be instruction identifiers 1, 2, and 3. When the process module is triggered to execute this diagnostic program, it first generates the first call instruction based on the first diagnostic instruction information 1. The diagnostic module determines the target diagnostic instruction A based on the diagnostic instruction information 1 in the first call instruction and sends the target diagnostic instruction A to the TBOX. After receiving the instruction, the TBOX returns the response data a. After the parsing module receives the response data a, the process module then generates the second call instruction based on the second diagnostic instruction information 2 and repeats the above process. If the parsing module does not receive the response data at a certain step, the process module can stop executing the script and prompt that there may be a communication failure or a TBOX operation failure, or it can directly output a fault code. If the situation of not receiving the response data occurs, each diagnostic instruction information in the diagnostic program is traversed to complete the entire diagnostic process.

[0089] By implementing the embodiments of the present application, based on the diagnostic program, multiple diagnostic tasks can be automatically executed in a predetermined order without manual intervention in each diagnostic step, thereby improving diagnostic efficiency and being suitable for diagnostic scenarios under large-scale equipment; by executing diagnostic tasks in sequence, and depending on whether response data is received, the diagnostic link where problems may occur can be quickly located, which facilitates the investigation of the cause of the fault and improves diagnostic efficiency.

[0090] Optionally, the process module is used to:

[0091] Upon receiving the trigger operation, determining a target trigger control corresponding to the trigger operation;

[0092] determining a target diagnostic program corresponding to the target trigger control, executing the target diagnostic program to generate a call instruction and sending it to the diagnostic module;

[0093] The trigger control includes at least one diagnostic control; each diagnostic control corresponds to a respective diagnostic program; and the diagnostic instruction information in different diagnostic programs is at least partially different.

[0094] In an embodiment of the present application, the interaction module can monitor the user's trigger operation. When a trigger operation is received, the process module can determine the target trigger control corresponding to the trigger operation. For example, for some operations triggered by mouse clicks, touching the screen, etc., the process module can determine the target trigger control based on the coordinate position where the trigger operation occurs. Each trigger control has its own specific coordinate range on the screen, and the coordinate ranges of all trigger controls can be traversed to determine whether the coordinates fall within the range of a certain control. There is no restriction on how to determine the target trigger control.

[0095] A trigger control can be a diagnostic control used to trigger the diagnostic process. This can include full diagnostic controls, such as a "one-click electrical test" control, which diagnoses various aspects of the device under inspection, including, for example, the VIN code, device ID, specific functions or services, etc. It can also include partial diagnostic controls, which diagnose one or more aspects, such as diagnosing the data write service alone. It is understood that there can be only one full diagnostic control to cover the maximum diagnostic scope, or multiple partial diagnostic controls, each with different diagnostic content.

[0096] The process module can maintain an association table or other data structure between trigger controls and diagnostic programs. Based on the target diagnostic control determined by the user's trigger operation, the corresponding target diagnostic program is searched from the association table. Once the target diagnostic program is found, the process module begins executing the target diagnostic program, generates a call instruction based on the diagnostic instruction information contained in the target diagnostic program, and then sends the call instruction to the diagnostic module.

[0097] For example, in the interactive interface of an automobile diagnostic system, there may be two trigger controls: "All diagnostic controls" and "Partial diagnostic controls." When the user clicks "All diagnostic controls," the interactive module detects the click event, and the process module determines that "All diagnostic controls" is the target trigger control. The process module finds the target diagnostic program corresponding to "All diagnostic controls" in the association table. This target diagnostic program may contain diagnostic instruction information related to data writing services, security access services, etc. The process module executes the script, sequentially generates call instructions for each and sends them to the diagnostic module. The diagnostic module sends the target diagnostic instructions to the device to be inspected to diagnose the data writing service and security access service.

[0098] If the user clicks "Partial Diagnostic Control," the process module identifies it as a target trigger control and determines a corresponding target diagnostic program. This target diagnostic program may only contain diagnostic instructions related to the data write service. The process module executes this target diagnostic program, generates a call instruction for the data write service, and sends it to the diagnostic module. The diagnostic module then sends the target diagnostic instruction to the device under test, thereby diagnosing the data write service.

[0099] By implementing the embodiments of this application and providing both full and partial diagnostic controls, users can select different diagnostic methods based on their actual needs. When conducting a comprehensive diagnosis, all diagnostic controls can be used; when specific issues may exist, partial diagnostic controls can be used to quickly diagnose specific issues, saving diagnostic time and resources. Furthermore, by using different diagnostic programs with different diagnostic instruction information, the diagnostic process can be customized according to specific diagnostic needs, making the diagnostic process more accurate and efficient, avoiding unnecessary diagnostic steps, and improving diagnostic efficiency.

[0100] Optionally, the process module is used to:

[0101] Create a new script to obtain the script to be edited, or determine that an existing script is the script to be edited;

[0102] For the script to be edited, triggering an instruction selection interface corresponding to the script to be edited, determining diagnostic instruction information in the instruction selection interface, and adding the diagnostic instruction information to the script to be edited;

[0103] A diagnostic program is generated based on the script to be edited that carries the diagnostic instruction information.

[0104] In an embodiment of the present application, the process module may have an entry for creating a script, such as a "New Script" button. By triggering this button, the process module can generate a new script and can also configure the Description field to modify the script name.

[0105] In addition, the function block interface displays a list of existing scripts, allowing you to select a specific script to edit. Alternatively, you can select a script by typing its name. Once you've selected the script you want to edit, you can load the script into the editing area, placing it in the editing state.

[0106] When a new script or an existing script is selected, the script editing area can be displayed in the interactive interface. Select a line in the script and click "After", "+Before" or double-click the line directly, select Diag Job Action, and then double-click in the second column. In the pop-up dialog box, select Start in the first column and the diagnostic instruction information is displayed in the second column. The diagnostic instruction information can be the identifier or name of the diagnostic instruction. Select the required diagnostic instruction information to add the diagnostic instruction information to the script to be edited, and finally generate a complete script to be edited with the target diagnostic instruction information. Generate a diagnostic program based on the script to be edited, thereby constructing a diagnostic module including a diagnostic program.

[0107] Alternatively, add a line of instructions in Diag Job Action, select Set Value, select App signals, and then select the application signal. In Add Operator, select the operator corresponding to the diagnostic instruction. In Add State, select the enumeration value corresponding to the diagnostic instruction to complete the addition of the diagnostic instruction information.

[0108] By implementing the embodiments of the present application, it is possible to flexibly create or select existing scripts for editing according to actual diagnostic needs, quickly determine the target diagnostic instruction information through the instruction selection interface, and generate targeted diagnostic programs. Compared with fixed diagnostic processes, unnecessary diagnostic steps are reduced and diagnostic efficiency is improved; different users can generate different diagnostic programs according to diagnostic needs to meet diverse diagnostic needs, enhance the customizability of the diagnostic process, and improve diagnostic flexibility.

[0109] Optionally, the diagnostic module is further configured to:

[0110] Determine a target configuration interface among multiple configuration interfaces corresponding to the diagnosis module according to the device information of the device to be inspected;

[0111] Determining a target controller area network corresponding to the device information among a plurality of controller area networks, and determining a target communication protocol corresponding to the device information among a plurality of communication protocols;

[0112] Determining a target communication address of the device to be inspected in the target controller local area network, configuring a preset communication address in the target configuration interface as the target communication address, and generating a diagnostic tag associated with the device to be inspected and the target communication protocol;

[0113] Diagnostic instruction information is determined in the target configuration interface, and a diagnostic instruction is generated based on the diagnostic instruction information and the diagnostic tag.

[0114] In embodiments of the present application, a data table or other data structure may be maintained containing device information and configuration interfaces for the device under test. Once the device information (e.g., device model, name, etc.) is determined, a search may be performed within the table to determine the target configuration interface corresponding to the device under test. Taking VSPY as an example, different ECUs may have different configuration requirements and, therefore, different configuration interfaces. The specific configuration interface may be triggered to open based on the input ECU information.

[0115] Because various devices or components in a vehicle have different functions and data transmission requirements, for example, the ECU needs to transmit large amounts of data related to engine operating status, such as speed, torque, and fuel injection rate, in real time and at high speed to precisely control engine operation. Window and door control units, on the other hand, primarily process low-speed, relatively simple switching signals. Furthermore, due to factors such as network load balancing, different devices or components can be connected to different Controller Area Networks (CANs). The corresponding CAN, for example, CAN1 or CAN2, can be determined based on the specific device information.

[0116] In addition, during the diagnosis process, signal reception and transmission are realized based on a specific communication protocol. The communication protocol may be a Unified Diagnostic Services (UDS) protocol, an On-Board Diagnostics (OBD) protocol, a Local Interconnect Network (LIN) protocol, etc., which are not specifically limited here. In the diagnosis, different devices to be inspected may correspond to different communication protocols. For example, the engine control unit corresponds to a diagnostic communication protocol based on the CAN bus or a UDS protocol, and the body control module may correspond to a LIN protocol, which are not specifically limited here. A mapping relationship between the device information and the communication protocol of different devices to be inspected may be constructed, and then the target communication protocol may be determined based on the device information of the current device to be inspected.

[0117] After determining the target LAN (Controller Area Network), the target communication address of the device under test within that network is obtained. This can be obtained through documentation associated with the device or through network scanning. The preset communication address in the target configuration interface is modified to the target communication address. The diagnostic module then generates a unique diagnostic tag based on the target communication address and device information. For example, the diagnostic module can generate a diagnostic tag "($240)TBOX" for a specific target communication protocol and target LAN (Controller Area Network) option, indicating that the target communication address of the device under test, TBOX, is 240.

[0118] In the configuration interface, based on the determined diagnostic tag, the user can select or enter diagnostic command information. For example, the diagnostic command information could be "$10-Diagnostic Session Control," where "10" indicates the diagnostic session control service; or "$2E-Write Data By Identifier," where "2E" indicates the data write service, and so on.

[0119] Diagnostic instructions specify the diagnostic tasks to be performed on the device under inspection. The diagnostic module combines diagnostic tags with the rules of the target communication protocol to convert these instructions into diagnostic instructions that comply with that protocol. Users can add diagnostic instructions for different services under the tags, and the diagnostic module generates corresponding diagnostic instructions according to the protocol requirements.

[0120] For example, in the configuration interface, select the sub-label "($240)TBOX" and the Jobs label, click "+" to add a diagnostic instruction, select ISO14229-"$10-Diagnostic Session Control", and edit the instruction name and other content. After saving the project, 10 service diagnostic instructions that comply with the ISO14229 protocol are generated.

[0121] By implementing the embodiments of the present application, since different devices to be inspected have different configuration and communication requirements, the target configuration interface, target controller local area network and target communication protocol corresponding to the device to be inspected can be determined, different diagnostic schemes can be determined for different devices to be inspected, and compatibility with multiple devices to be inspected is achieved, thereby improving the applicability of diagnosis, as well as the accuracy and pertinence of diagnosis; and based on the generation of diagnostic tags and diagnostic instructions that comply with the target communication protocol, the diagnostic process can be made more standardized and automated, and configuration and instruction generation can be completed quickly, reducing the time and errors of manual operations and improving diagnostic efficiency.

[0122] Optionally, the parsing module is further configured to:

[0123] In the message editing interface corresponding to the parsing module, add an external message and associate the external message with the diagnostic instruction information to generate a diagnostic function corresponding to the diagnostic instruction information;

[0124] Target diagnostic instruction information corresponding to the response data and a target diagnostic function corresponding to the target diagnostic instruction information are determined.

[0125] In an embodiment of the present application, the message editing interface can be opened through the trigger path of Scripting and Auto-C Code Interface, SpyNetworks, and Message Editor, and in the message editing interface corresponding to the parsing module. Triggering the "+" button can trigger the add message operation to add an external message (i.e., receive a message), and associate the external message with the diagnostic instruction information, which can be done by setting the arbitration identifier (Arb ID, Arbitration ID) of the external message to the diagnostic instruction ID and naming the message, such as "Diag_Resp_TBOX". Further, in a specific area of ​​the C Code Interface module, such as "Rx Messages" in "Message Events", the diagnostic instruction can be added to the specified area, so that the diagnostic tool can clearly know the message type and source to be monitored.

[0126] The diagnostic function used to process the response data can be automatically generated by the parsing module or pre-built by the user. Different diagnostic functions correspond to different diagnostic instruction information, such as the diagnostic instruction name. The corresponding diagnostic function can be found based on the diagnostic instruction name and copied. The diagnostic function is stored in a specific code file (such as SpyCCode.c). The response data is then processed based on the diagnostic function in SpyCCode.c.

[0127] Upon receiving the response data, the parsing module first filters out matching target diagnostic instruction information from the existing diagnostic instruction information set based on the response data's characteristics, such as the data format, specific identifier, and the instruction identifier it carries. Based on the target diagnostic instruction information, the parsing module then determines the corresponding target diagnostic function and executes the target diagnostic function to process the response data.

[0128] In implementing the embodiments of the present application, by setting the external message identifier as a diagnostic instruction identifier, etc., the external message is associated with the diagnostic instruction information in the message editing interface, and the diagnostic tool generates a diagnostic function corresponding to the diagnostic instruction information. When the response data is received, the parsing module can respond to the target diagnostic instruction information corresponding to the data, determine the target diagnostic function, and analyze the response data more accurately, thereby improving the accuracy of the diagnosis.

[0129] Optionally, the system further includes a state management module, wherein the state management module is configured to:

[0130] In the application signal interface corresponding to the state management module, add an application signal and configure the signal type of the application signal to be a state coding type;

[0131] In the case where the signal type is the status coding type, adding multiple status values ​​in the status description interface corresponding to the application signal;

[0132] According to the diagnosis result, a corresponding first target state value is determined among a plurality of state values, and the state value of the application signal is set to the first target state value.

[0133] In an embodiment of the present application, the device diagnostic system may further include a state management module. The state management module may add an application signal in the corresponding Application Signals interface and configure the signal type of the application signal to be a state encoding type. When the signal type of the application signal is a state encoding type, multiple corresponding state values ​​may be further added to the application signal. The application signal may be set to different state values ​​among the multiple state values ​​by various modules in the system.

[0134] The diagnostic result determined by the analysis module may indicate whether the comparison between the response data and the reference data is consistent or inconsistent. If the comparison is consistent, the diagnostic result may be a passed diagnosis; if the comparison is inconsistent, the diagnostic result may be a failed diagnosis. The diagnostic result may also be expressed in other different ways, such as numbers, which is not specifically limited here.

[0135] Among the multiple status values, there may be a status value corresponding to the diagnostic result. If the diagnostic result includes a pass or fail, there may be two status values ​​corresponding to the two diagnostic results. Furthermore, the status management module may determine a corresponding first target status value from the multiple status values ​​based on the current diagnostic result, and set the status value of the application signal to the first target status value. By setting the status value of the application signal based on the diagnostic result, the diagnostic result can be represented by the application signal.

[0136] In implementing an embodiment of the present application, an application signal is added in the application signal interface corresponding to the status management module, and the signal type of the application signal is configured as a status coding type; when the signal type is the status coding type, multiple status values ​​are added in the status description interface corresponding to the application signal, and according to the diagnosis result, the corresponding first target status value is determined among the multiple status values, and the status value of the application signal is set to the first target status value. The diagnosis result can be converted into the form of an application signal, and the application signal can flow more conveniently and quickly between the various modules in the system, thereby improving the convenience and efficiency of transmitting diagnostic information.

[0137] Optionally, at least one of the interaction module, the process module, the diagnosis module, and the analysis module is configured to:

[0138] According to the respective executed actions, a corresponding second target state value is determined among the multiple state values, and the state value of the application signal is set to the second target state value.

[0139] In an embodiment of the present application, other modules besides the status management module may be an interaction module, a process module, a diagnosis module, and an analysis module, etc. These modules are used to perform different actions respectively. For example, the interaction module needs to obtain reference data and trigger operations, the process module needs to execute diagnostic procedures, generate call instructions, and send call instructions, the diagnostic module sends target diagnostic instructions to the device to be inspected, and the analysis module needs to execute diagnostic functions for data comparison.

[0140] Different diagnostic results can correspond to different state values ​​of the application signal. Similarly, the actions executed by different modules can also correspond to different state values ​​of the application signal. Furthermore, each module can determine a corresponding second target state value from multiple state values ​​based on its own execution action and set the state value of the application signal as the second target state value.

[0141] In implementing the embodiments of the present application, other modules other than the status management module, namely the interaction module, process module, diagnosis module and analysis module, respectively determine the second target status value from multiple status values ​​according to the actions they respectively perform, and set the status value of the application signal to the second target status value. Since the execution actions of each module represent the current diagnostic progress and status, each module sets the status value according to the execution action, and can determine the diagnostic progress in real time according to the execution action, so that the diagnostic progress can be monitored, which is more intuitive, thereby improving the intuitiveness of the equipment diagnostic process.

[0142] Optionally, each status value is associated with a corresponding status name; the system includes a first module and multiple second modules, the first module is a module for setting the status value of the application signal; the second module is a module for not setting the status value of the application signal, and the second module is used to:

[0143] In the case where the first module sets the state value of the application signal, the first target state value or the second target state value is read, and the corresponding target state name is determined to complete state synchronization.

[0144] In an embodiment of the present application, different status values ​​of the application signal may have different status names. For example, the status value of a passed diagnostic result may be 0, and the status name corresponding to the status value 0 may be succ. The status value of a failed diagnostic result may be 1, and the status name corresponding to the status value 1 may be fail. The status value set based on the execution action of other modules outside the status management module may have a corresponding status name related to the execution action, such as sending a call instruction, sending a target diagnostic instruction, etc.

[0145] The module currently setting the status value of the application signal can be referred to as the first module. When the first module sets the status value of the application signal, other modules outside the first module, namely the second module, can read the first target status value (the status value set by the status management module) or the second target status value (the status value set by the module outside the status management module) and determine the corresponding target status name. This allows each module to obtain the status of other modules, thereby achieving state synchronization.

[0146] In implementing an embodiment of the present application, when the first module sets the status value of the application signal, the second module outside the first module reads the first target status value or the second target status value and determines the corresponding target status name to complete status synchronization, so that different modules can more accurately know the system status based on the status value of the application signal, and can realize real-time update of the system status, which facilitates the collaborative work of each module based on the latest status, thereby improving the system operation efficiency and reliability.

[0147] In summary, by simulating the off-line electrical inspection process of a real vehicle, problems can be discovered in advance, analyzed and solved, and production line-related risks can be reduced. This has the following effects:

[0148] 1. Improve development efficiency.

[0149] Preemptive problem discovery: Before the device to be tested, such as ECU hardware, is installed on the vehicle, the simulation environment can simulate the diagnostic interaction process between the device to be tested and the diagnostic instrument, so that potential problems can be exposed in advance, effectively reducing the modification costs caused by delayed problem discovery in the subsequent development stage.

[0150] Enable parallel development: In the early stages of vehicle development, the equipment to be tested and the vehicle system can be tested simultaneously. The parallel operation mode breaks the limitations of the traditional serial development process and greatly shortens the overall development cycle.

[0151] Improved problem-solving efficiency: A simulation environment offers unique advantages for solving problems that are difficult to replicate in real-world scenarios. By setting ideal conditions, problems can be accurately reproduced and located, significantly improving problem-solving efficiency.

[0152] 2. Reduce testing costs

[0153] Reduced reliance on physical equipment: Simulation eliminates the need for physical vehicles or real-world scenarios. Electrical inspections can be completed using only virtual models and test software, reducing testing costs.

[0154] Low-cost fault simulation: It can conveniently simulate various fault scenarios. Compared with fault simulation on actual physical devices, the cost is effectively controlled and reduced.

[0155] 3. Expand test coverage

[0156] Covering more test scenarios: Complex and diverse test scenarios such as extreme voltages, multiple DUT communication errors, and packet loss can be simulated to improve test coverage.

[0157] Precise control of test conditions: In a simulation environment, various test conditions can be precisely controlled to ensure the accuracy and reliability of test results.

[0158] 4. Enhanced test security

[0159] Avoid hardware damage risk: During the simulation process, there is no need to use real hardware devices for high-risk testing, thus effectively avoiding hardware damage caused by improper test operations.

[0160] Safety verification of high-risk scenarios: For scenarios with high safety risks, such as battery thermal runaway and bus congestion, safety verification can be performed in a simulation environment to identify potential risks in advance and develop response strategies.

[0161] The present application also provides an electronic device, such as Figure 4 As shown, it includes a processor 1001 , a communication interface 1002 , a memory 1003 and a communication bus 1004 , wherein the processor 1001 , the communication interface 1002 , and the memory 1003 communicate with each other via the communication bus 1004 .

[0162] The memory 1003 is used to store computer programs.

[0163] When the processor 1001 is used to execute the program stored in the memory 1003, it implements the steps executed by each module in the above-mentioned device diagnosis system, which will not be repeated here.

[0164] The communication bus mentioned in the electronic device mentioned above may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.

[0165] The communication interface is used for communication between the above electronic device and other devices.

[0166] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage. Alternatively, the memory may be at least one storage device located away from the processor.

[0167] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

[0168] In another embodiment provided by the present application, a readable storage medium is further provided, on which a computer program is stored. When the program is executed by a processor, the steps executed by each module in the device diagnostic system in the above embodiment are implemented.

[0169] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a readable storage medium or transmitted from one readable storage medium to another readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0170] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply the existence of any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

[0171] Each embodiment in this specification is described in a related manner. Similar portions between the various embodiments can be referenced to each other. Each embodiment focuses on the differences from other embodiments. The embodiments of the apparatus, electronic device, readable storage medium, and computer program product containing instructions thereof are generally similar to the system embodiments, so their description is relatively simple. For related portions, reference can be made to the description of the system embodiments.

[0172] The above description is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the scope of protection of the present application.

Claims

1. A device diagnostic system, characterized in that: The system comprises: The interaction module is used to obtain reference data and trigger operations; The process module is used to obtain a diagnostic program carrying diagnostic instruction information; when receiving the trigger operation, execute the corresponding diagnostic program to generate a call instruction and send it to the diagnostic module; the call instruction is used to indicate a target diagnostic instruction corresponding to the diagnostic instruction information; The diagnostic module is used to obtain a target diagnostic instruction; upon receiving the call instruction, the diagnostic module sends the corresponding target diagnostic instruction to the device to be inspected; the device to be inspected is used to respond to the target diagnostic instruction and return response data to the parsing module; The parsing module is used to determine a diagnostic function corresponding to the response data and execute the diagnostic function to compare the response data with the reference data and obtain a diagnostic result.

2. The system according to claim 1, wherein: The diagnostic program includes multiple diagnostic instruction information, and different diagnostic instruction information is used to generate different call instructions; the process module is used to: executing the diagnostic program carrying multiple diagnostic instruction information to generate a first call instruction according to the first diagnostic instruction information among the multiple diagnostic instruction information; When the response data corresponding to the first call instruction is received, the next call instruction is generated according to the next diagnostic instruction information until no response data corresponding to the previous call instruction is received, or each diagnostic instruction information in the diagnostic program is traversed.

3. The system according to claim 1, wherein: The interactive module includes an input control, a trigger control and a display control; The input control is used for the user to input reference data; the trigger control is used for the user to perform a trigger operation; and the display control is used to display the diagnosis result.

4. The system according to claim 1, wherein: The process module is used to: Upon receiving the trigger operation, determining a target trigger control corresponding to the trigger operation; determining a target diagnostic program corresponding to the target trigger control, executing the target diagnostic program to generate a call instruction and sending it to the diagnostic module; The trigger control includes at least one diagnostic control; each diagnostic control corresponds to a respective diagnostic program; and the diagnostic instruction information in different diagnostic programs is at least partially different.

5. The system according to claim 1, wherein: The process module is used to: Create a new script to obtain the script to be edited, or determine that an existing script is the script to be edited; For the script to be edited, triggering an instruction selection interface corresponding to the script to be edited, determining diagnostic instruction information in the instruction selection interface, and adding the diagnostic instruction information to the script to be edited; A diagnostic program is generated based on the script to be edited that carries the diagnostic instruction information.

6. The system according to claim 1, wherein: The diagnostic module is further configured to: Determine a target configuration interface among multiple configuration interfaces corresponding to the diagnosis module according to the device information of the device to be inspected; Determining a target controller area network corresponding to the device information among a plurality of controller area networks, and determining a target communication protocol corresponding to the device information among a plurality of communication protocols; Determining a target communication address of the device to be inspected in the target controller local area network, configuring a preset communication address in the target configuration interface as the target communication address, and generating a diagnostic tag associated with the device to be inspected and the target communication protocol; Diagnostic instruction information is determined in the target configuration interface, and a diagnostic instruction is generated based on the diagnostic instruction information and the diagnostic tag.

7. The system according to claim 1, wherein: The parsing module is also used to: In the message editing interface corresponding to the parsing module, add an external message and associate the external message with the diagnostic instruction information to generate a diagnostic function corresponding to the diagnostic instruction information; Target diagnostic instruction information corresponding to the response data and a target diagnostic function corresponding to the target diagnostic instruction information are determined.

8. The system according to claim 1, wherein: The system further includes a state management module, which is configured to: In the application signal interface corresponding to the state management module, add an application signal and configure the signal type of the application signal to be a state coding type; In the case where the signal type is the status coding type, adding multiple status values ​​in the status description interface corresponding to the application signal; According to the diagnosis result, a corresponding first target state value is determined among a plurality of state values, and the state value of the application signal is set to the first target state value.

9. The system according to claim 8, characterized in that At least one of the interaction module, the process module, the diagnosis module, and the analysis module is configured to: According to the respective executed actions, a corresponding second target state value is determined among the multiple state values, and the state value of the application signal is set to the second target state value.

10. The system according to any one of claims 8 or 9, characterized in that Each status value is associated with a corresponding status name; the system includes a first module and multiple second modules, the first module is a module for setting the status value of the application signal; the second module is a module for not setting the status value of the application signal, and the second module is used to: In the case where the first module sets the state value of the application signal, the first target state value or the second target state value is read, and the corresponding target state name is determined to complete state synchronization.

Images