Multi-bus equipment diagnosis test method and system

Abstract

The invention provides a multi-bus equipment diagnostic test method, which comprises the following steps of: inputting a diagnostic test sequence through an Excel file, and analyzing to generate an executable test instruction; performing protocol conversion on the test instruction to obtain PDU data conforming to a target bus protocol; calling a uniform interface function through the API compatible layer, and sending the converted PDU data to the connected controller to be tested through the bus equipment for diagnosis test; and receiving response data of the controller to be tested in real time, comparing response information with a preset expected result, executing test result verification, and generating a diagnosis report in an Excel format. The invention further discloses a corresponding system. According to the method and the device, the Excel is used as the test sequence input, so that the test sequence is automatically sent and the result is checked, the learning cost can be reduced, and the test efficiency and the hardware compatibility are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of equipment diagnosis, and particularly to a multi-bus equipment diagnosis test method and system. Background Art

[0002] In the technical field of equipment diagnosis, especially in scenarios where the Controller Area Network (CAN) and Controller Area Network with Flexible Data-rate (CANFD) bus protocols are used for diagnosis, existing toolchains often exhibit the characteristics of diversification and self-contained systems. These toolchains include various hardware interfaces, software platforms, and scripting languages, providing engineers with multiple options. However, there are also some deficiencies in these existing diagnostic solutions:

[0003] Firstly, there are numerous toolchains: There are various different toolchains in the market, and each toolchain has its unique technical system and operation method, resulting in engineers needing to spend a lot of time learning and adapting to different tools.

[0004] Secondly, script development is complex: Due to the diversity of toolchains, the development and debugging process of scripts has also become complex and changeable. Engineers need to master multiple scripting languages and adjust the script content according to different toolchains.

[0005] In addition, the sending of diagnostic instructions cannot be automated: Existing tools often do not support the serial automatic sending of diagnostic instructions, and engineers need to send instructions one by one manually, greatly reducing the test efficiency.

[0006] In addition, the hardware compatibility is poor: Different toolchains have different degrees of support for hardware devices, and engineers need to select corresponding toolchains for different hardware devices, increasing the work complexity. Summary of the Invention

[0007] The technical problem to be solved by the present invention is to propose a multi-bus equipment diagnosis test method and system, which uses Excel as the input of the test sequence to realize the automatic sending and result checking of the test sequence, and can reduce the learning cost, improve the test efficiency, and improve the hardware compatibility.

[0008] As one aspect of the present invention, a multi-bus equipment diagnosis test method is provided, which includes the following steps:

[0009] Input the diagnostic test sequence through an Excel file and parse it to generate executable test instructions;

[0010] Perform protocol conversion on the test instructions to obtain Protocol Data Unit (PDU) data that conforms to the target bus protocol;

[0011] Call the unified interface function through the API compatibility layer, and send the converted PDU data to the connected controller under test through the bus device for diagnostic testing;

[0012] Receive the response data of the controller under test in real time, compare the response information with the preset expected result, perform test result verification, and generate a diagnostic report in Excel format.

[0013] Among them, the parsing to generate executable test instructions includes:

[0014] Obtain the location of the target Excel file according to the operating system file dialog box, and the Excel file contains a diagnostic test sequence;

[0015] Verify whether the format of the Excel file conforms to the preset standard;

[0016] Call the Excel switch function to establish a file operation channel, and extract the control parameters in the test sequence through the read and write functions. The parameters at least include the bus type, message address, diagnostic service identifier, and expected response value.

[0017] Among them, the performing protocol conversion on the test instructions to obtain PDU data that conforms to the target bus protocol includes:

[0018] Implement multiplexing control in the PDU sending stage, dynamically select the CAN / CANFD message encapsulation format according to the target bus type, and use the message PDU sending function to send the assembled diagnostic PUD data;

[0019] Perform demultiplexing processing in the PDU receiving stage, use the message PDU receiving function to receive the diagnostic PUD data, and implement the CRC check and timeout retransmission mechanism when extracting the payload.

[0020] Among them, the calling the unified interface function through the API compatibility layer and sending the converted PDU data to the connected controller under test for diagnostic testing includes:

[0021] Call the unified message sending interface function, unified message receiving interface function, unified device startup function, or unified device shutdown function to realize the sending and receiving of bus messages, and the startup and shutdown of bus devices;

[0022] When transmitting data through the unified message sending interface, dynamically load the hardware driver library file of the corresponding manufacturer, and send the converted PDU data to the connected controller under test for diagnostic testing.

[0023] Further included are:

[0024] Before testing, select the controller to be tested through the test interface and configure it;

[0025] After testing, save the diagnostic report in Excel format and display it on the test interface.

[0026] Correspondingly, as another aspect of the present invention, a multi-bus device diagnostic test system is further provided, which includes:

[0027] An Excel processing module, configured to input a diagnostic test sequence through an Excel file, parse and generate executable test instructions;

[0028] A protocol conversion module, configured to perform protocol conversion on the test instructions to obtain PDU data conforming to the target bus protocol;

[0029] An API compatibility processing module, configured to call a unified interface function, send the converted PDU data to the connected controller to be tested through a bus device for diagnostic testing;

[0030] A result verification module, configured to receive the response data of the controller to be tested in real time, compare the response information with a preset expected result, perform test result verification, and generate a diagnostic report in Excel format.

[0031] Among them, the Excel processing module includes:

[0032] A file path unit, configured to obtain the location of the target Excel file according to the operating system file dialog box, and the Excel file contains a diagnostic test sequence;

[0033] A file format verification unit, configured to verify whether the format of the Excel file conforms to a preset standard;

[0034] A data parsing unit, configured to call an Excel switch function to establish a file operation channel, and extract control parameters in the test sequence through read and write functions, and the parameters at least include a bus type, a message address, a diagnostic service identifier, and an expected response value.

[0035] Among them, the protocol conversion module includes:

[0036] A sending processing unit, configured to implement multiplexing control in the PDU sending stage, dynamically select a CAN / CANFD message encapsulation format according to the target bus type, and send the assembled diagnostic PUD data by using a message PDU sending function;

[0037] A receiving and processing unit is used to perform demultiplexing processing during the PDU receiving stage, receive diagnostic PUD data using a message PDU receiving function, and implement a CRC check and timeout retransmission mechanism when extracting the payload.

[0038] Among them, the API compatibility module includes:

[0039] A device abstraction interface unit is used to call a unified message sending interface function, a unified message receiving interface function, a unified device startup function, or a unified device shutdown function to implement the sending and receiving of bus messages, as well as the startup and shutdown of bus devices;

[0040] A driver adaptation unit is used to dynamically load the hardware driver library file of the corresponding manufacturer when transmitting data through the unified message sending interface, and send the converted PDU data to the connected controller under test through the bus device for diagnostic testing.

[0041] Among them, it further includes:

[0042] A configuration module is used to select the controller under test through a test interface before testing and perform configuration;

[0043] A save processing module is used to save the diagnostic report in Excel format after testing and display it on the test interface.

[0044] Implementing the embodiments of the present invention has the following beneficial effects:

[0045] The present invention provides a multi-bus device diagnostic testing method and system. Through an Excel file, the serialization and automatic sending of diagnostic instructions are realized. Engineers only need to write a test sequence in Excel, and the software can automatically send instructions and check the results, greatly improving the testing efficiency.

[0046] Moreover, through modular design, the software can be easily extended and upgraded, theoretically enabling the same software to support all hardware devices, improving device utilization, and reducing the tool usage and learning costs.

[0047] In this embodiment, by adding an API compatibility layer, the interface call of multi-bus devices and the conversion between PDU and transport layer messages are made more convenient, enabling the software to be compatible with various bus devices supporting secondary development and improving device utilization. Through unified device startup and shutdown functions, engineers can conveniently manage hardware devices and reduce problems caused by incompatibility between the upper computer and the devices. Description of the Drawings

[0048] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, obtaining other drawings based on these drawings still belongs to the scope of the present invention;

[0049] Figure 1 It is a schematic diagram of the main process of an embodiment of a multi-bus device diagnostic test method provided by the present invention;

[0050] Figure 2 It is a more detailed schematic diagram of the process of the method provided by the present invention;

[0051] Figure 3 It is a schematic diagram of the structure of an embodiment of a multi-bus device diagnostic test system provided by the present invention;

[0052] Figure 4 For Figure 3 It is a schematic diagram of the structure of the Excel processing module in

[0053] Figure 5 For Figure 3 It is a schematic diagram of the structure of the protocol conversion module in

[0054] Figure 6 For Figure 3 It is a schematic diagram of the structure of the API compatibility module in

[0055] Figure 7 It is a block diagram of the implementation architecture in an embodiment of the system provided by the present invention. Detailed implementation manners

[0056] To make the objectives, technical solutions, and advantages of the present invention clearer, the following will further describe the present invention in detail with reference to the drawings.

[0057] As Figure 1 shown, it shows a schematic diagram of the main process of an embodiment of a multi-bus device diagnostic test method provided by the present invention; also in conjunction with Figure 2 shown, in this embodiment, the method at least includes the following steps:

[0058] Step S10, input a diagnostic test sequence through an Excel file and parse it to generate executable test instructions;

[0059] In a specific example, the parsing to generate executable test instructions includes:

[0060] Obtain the location of the target Excel file according to the operating system file dialog box, and the Excel file contains a diagnostic test sequence;

[0061] Verify whether the format of the Excel file conforms to the preset standard;

[0062] Call the Excel switch function to establish a file operation channel, and extract the control parameters in the test sequence through the read and write functions. The parameters at least include the bus type, message address, diagnostic service identifier, and expected response value.

[0063] In this step, the Excel switch function and the Excel switch function are required. Among them, the Excel switch function is used to open and save the Excel file, and the Excel read and write function is used to operate the content of the Excel file;

[0064] At the same time, an equipment selection entry needs to be set in the test interface for bus equipment configuration selection; and an Excel path selection entry needs to be set for Excel path storage.

[0065] For example, in an example, the engineer clicks on the "Excel Path Selection Entry" in the test interface, and the operating system pops up a file dialog box. The engineer browses the file system and selects the Excel file containing the diagnostic test sequence, such as TestSequence.xlsx.

[0066] The system checks whether the Excel file contains the necessary columns (bus type, message address, diagnostic service identifier, expected response value), and whether the data format is correct (such as whether the message address is a hexadecimal number).

[0067] Use the Excel switch function (such as OpenExcelFile) to open the file, and read the test sequence line by line through the read and write function (such as ReadExcelCell).

[0068] Store the read parameters (such as bus type CAN, message address 0x123, diagnostic service identifier 0x22, expected response value 0x55) into a structure or list in the memory as executable test instructions.

[0069] Provide a drop-down menu in the test interface. The engineer can select the type of controller to be tested (such as CAN device or CANFD device), and perform relevant configurations (such as baud rate, channel number).

[0070] Step S11, perform protocol conversion on the test instruction to obtain PDU data conforming to the target bus protocol;

[0071] In a specific example, the step S11 further includes:

[0072] Implement multiplexing control during the PDU transmission phase, dynamically select the CAN / CANFD message encapsulation format according to the target bus type, and use the message PDU transmission function to send the assembled diagnostic PUD data;

[0073] Execute demultiplexing processing during the PDU reception phase, use the message PDU reception function to receive diagnostic PUD data, and implement the CRC check and timeout retransmission mechanism when extracting the payload.

[0074] Among them, in this step, it is necessary to use the pre-set message PDU transmission function and message PDU reception function. The message PDU transmission function is used to send diagnostic PDUs; while the message PDU reception function is used to receive diagnostic PDUs.

[0075] For example, in a specific example, in the PDU transmission phase of this step: the message encapsulation format can be dynamically selected according to the bus type (such as CAN or CANFD). For CAN messages, a standard ID (11 bits) or an extended ID (29 bits) may be used; for CANFD messages, a longer ID and a larger data length may be used. Call the message PDU transmission function (such as SendCANPDU or SendCANFDPDU) to send the encapsulated PDU data to the bus.

[0076] In the PDU reception phase, the message PDU reception function (such as ReceiveCANPDU or ReceiveCANFDPDU) can be called to receive PDU data from the bus. When extracting the payload, perform a CRC check to ensure data integrity. If the check fails, execute the timeout retransmission mechanism to request the data again.

[0077] Step S12, call the unified interface function through the API compatibility layer, and send the converted PDU data to the connected controller under test through the bus device for diagnostic testing;

[0078] In a specific example, step S12 further includes:

[0079] Call the unified message sending interface function, unified message receiving interface function, unified device startup function or unified device shutdown function to implement the sending and receiving of bus messages, and the startup and shutdown of bus devices;

[0080] When transmitting data through the unified message sending interface, dynamically load the hardware driver library file of the corresponding manufacturer, and send the converted PDU data to the connected controller under test for diagnostic testing.

[0081] It can be understood that it is necessary to pre-set:

[0082] The unified message sending interface function is used to send bus messages;

[0083] The unified message receiving interface function is used to receive bus messages;

[0084] The unified device startup function is used to start bus devices;

[0085] The unified device shutdown function is used to shut down bus devices.

[0086] For example, in a specific example, the unified interface function calls include: calling the unified message sending interface function (such as SendUnifiedPDU), which dynamically loads the hardware driver library files of the corresponding manufacturers (such as CANDriver.dll or CANFDDriver.dll) according to the bus device type. Send PDU data to the controller under test. For example, send a CAN message (message address 0x123, service identifier 0x22) to the bus.

[0087] Device startup and shutdown include: calling the unified device startup function (such as StartDevice) to start the bus device and perform initialization settings. After the test is completed, call the unified device shutdown function (such as CloseDevice) to shut down the bus device and release resources.

[0088] Step S13, receive the response data of the controller under test in real time, compare the response information with the preset expected result, perform test result verification, and generate a diagnostic report in Excel format.

[0089] For example, in a specific example, this step includes:

[0090] Receiving response data: Listen to the bus in real time and call the unified message receiving interface function (such as ReceiveUnifiedPDU) to receive the response data of the controller under test.

[0091] Test result verification: Compare the received response data with the preset expected result (such as the expected response value 0x55). If they are consistent, the test passes; if not, the test fails and the error information is recorded.

[0092] Generating a diagnostic report: Write the test results (including test time, test items, test results, error information, etc.) into a diagnostic report in Excel format, such as TestReport.xlsx.

[0093] Display the diagnostic report on the test interface, and engineers can view and analyze the test results.

[0094] It can be understood that in the embodiments of the present invention, it further includes:

[0095] Step S00, select the controller to be tested through the test interface before the test and perform configuration; in a specific example, before the test starts, the engineer selects the type of the controller to be tested through the test interface and performs relevant configurations, such as selecting the CAN channel, setting the baud rate, etc.

[0096] Step S12, after the test, save the diagnostic report in Excel format and display it on the test interface. In a specific example, after the test is completed, the system automatically saves the generated diagnostic report in Excel format to the specified path and displays the report content on the test interface, and the engineer can view or print the report.

[0097] It can be understood that by implementing the method of the present invention, the serialization and automatic sending of diagnostic instructions are realized through an Excel file. The engineer only needs to write the test sequence in Excel, and the software can automatically send the instructions and check the results, greatly improving the test efficiency.

[0098] Moreover, through the modular design, the software can be easily extended and upgraded, and theoretically, the same software can support all hardware devices, improving the equipment utilization rate and reducing the tool usage and learning costs.

[0099] In this embodiment, by adding an API compatibility layer, the interface call of multi-bus devices and the conversion between PDU and transport layer messages are made more convenient.

[0100] As Figure 3 shown, a schematic structural diagram of an embodiment of a multi-bus device diagnostic test system provided by the present invention is shown; in combination with Figures 4 to 7 shown, in this embodiment, the multi-bus device diagnostic test system 1 at least includes:

[0101] A configuration module 10, configured to select the controller to be tested through the test interface before the test and perform configuration;

[0102] An Excel processing module 11, configured to input a diagnostic test sequence through an Excel file and parse and generate executable test instructions;

[0103] A protocol conversion module 12, configured to perform protocol conversion on the test instructions to obtain PDU data conforming to the target bus protocol;

[0104] An API compatibility processing module 13, configured to call a unified interface function, send the converted PDU data to the connected controller to be tested through a bus device for diagnostic testing;

[0105] A result verification module 14, configured to receive the response data of the controller to be tested in real time, compare the response information with a preset expected result, perform test result verification, and generate a diagnostic report in Excel format;

[0106] The saving processing module 15 is used to save the diagnostic report in Excel format after the test and display it on the test interface.

[0107] In a specific example, as Figure 4 shown, the Excel processing module 11 includes:

[0108] The file path unit 110 is used to obtain the location of the target Excel file according to the operating system file dialog box. The Excel file contains a diagnostic test sequence.

[0109] The file format verification unit 111 is used to verify whether the format of the Excel file conforms to the preset standard.

[0110] The data parsing unit 112 is used to call the Excel switch function to establish a file operation channel and extract the control parameters in the test sequence through the read and write functions. The parameters at least include the bus type, message address, diagnostic service identifier, and expected response value.

[0111] In a specific example, as Figure 5 shown, the protocol conversion module 12 includes:

[0112] The sending processing unit 120 is used to implement multiplexing control in the PDU sending stage, dynamically select the CAN / CANFD message encapsulation format according to the target bus type, and send the assembled diagnostic PUD data by using the message PDU sending function.

[0113] The receiving processing unit 121 is used to perform demultiplexing processing in the PDU receiving stage, receive the diagnostic PUD data by using the message PDU receiving function, and implement the CRC check and timeout retransmission mechanism when extracting the payload.

[0114] In a specific example, as Figure 6 shown, the API compatibility module 13 includes:

[0115] The device abstraction interface unit 130 is used to call the unified message sending interface function, unified message receiving interface function, unified device startup function, or unified device shutdown function to implement the sending and receiving of bus messages, and the startup and shutdown of bus devices.

[0116] The driver adaptation unit 131 is used to dynamically load the hardware driver library file of the corresponding manufacturer when transmitting data through the unified message sending interface, and send the converted PDU data to the connected controller under test for diagnostic testing.

[0117] In practical applications, a more detailed framework structure can be referred to Figure 7 as shown.

[0118] For more details, please refer to the foregoing description of Figures 1 to 2 , which will not be elaborated here.

[0119] Implementing the embodiments of the present invention has the following beneficial effects:

[0120] The present invention provides a multi-bus device diagnosis and test method and system. Through an Excel file, the serial automatic sending of diagnostic instructions is realized. Engineers only need to write a test sequence in Excel, and the software can automatically send instructions and check the results, greatly improving the test efficiency.

[0121] Moreover, through modular design, the software can be easily extended and upgraded. In theory, the same software can support all hardware devices, improving the device utilization rate and reducing the tool usage and learning costs.

[0122] In this embodiment, by adding an API compatibility layer, the software can be compatible with various bus devices that support secondary development, improving the device utilization rate. Through unified device startup and shutdown functions, engineers can conveniently manage hardware devices, reducing problems caused by incompatibility between the host computer and the device.

[0123] The present invention is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as the combination of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0124] The foregoing disclosure is only a preferred embodiment of the present invention, and of course, it cannot be used to limit the scope of the rights of the present invention. Therefore, equivalent changes made according to the claims of the present invention still fall within the scope covered by the present invention.

Claims

1. A multi-bus device diagnostic test method, characterized in that: The following steps are involved: Input diagnostic test sequences through Excel files and parse and generate executable test instructions; Performing protocol conversion on the test instruction to obtain PDU data that complies with the target bus protocol; Call the unified interface function through the API compatibility layer, send the converted PDU data to the connected controller to be tested through the bus device, and perform diagnostic testing; Receive the response data of the controller to be tested in real time, compare the response information with the preset expected results, perform test result verification, and generate a diagnostic report in Excel format.

2. The method according to claim 1, characterized in that The parsing generates executable test instructions, including: Obtaining a target Excel file location according to an operating system file dialog box, wherein the Excel file contains a diagnostic test sequence; Verify whether the format of the Excel file meets the preset standards; The Excel switch function is called to establish a file operation channel, and the control parameters in the test sequence are extracted through the read and write functions. The parameters at least include the bus type, message address, diagnostic service identifier and expected response value.

3. The method according to claim 2, characterized in that The step of performing protocol conversion on the test instruction to obtain PDU data that complies with the target bus protocol includes: Implement multiplexing control in the PDU sending phase, dynamically select the CAN / CANFD message encapsulation format according to the target bus type, and use the message PDU sending function to send the assembled diagnostic PDU data; Demultiplexing is performed during the PDU reception phase, and the diagnostic PDU data is received using the message PDU reception function.

4. The method according to claim 3, characterized in that The method of calling the unified interface function through the API compatibility layer and sending the converted PDU data to the connected controller to be tested through the bus device to perform a diagnostic test includes: Calling unified message sending interface function, unified message receiving interface function, unified device startup function or unified device shutdown function to realize the sending and receiving of bus messages and the startup and shutdown of bus devices; When transmitting data through the unified message sending interface, the hardware driver library file of the corresponding manufacturer is dynamically loaded, and the converted PDU data is sent to the connected controller under test through the bus device for diagnostic testing.

5. The method according to claim 4, characterized in that Further including: Before testing, select the bus device to be used through the test interface and configure it; After the test, the diagnostic report is saved in Excel format and displayed on the test interface.

6. A multi-bus device diagnostic test system, characterized in that: Include: Excel processing module, used to input diagnostic test sequences through Excel files, parse and generate executable test instructions; A protocol conversion module, used for performing protocol conversion on the test instruction to obtain PDU data conforming to the target bus protocol; An API compatible processing module is used to call a unified interface function and send the converted PDU data to the connected controller to be tested through a bus device for diagnostic testing; The result verification module is used to receive the response data of the controller to be tested in real time, compare the response information with the preset expected results, perform test result verification, and generate a diagnostic report in Excel format.

7. The system according to claim 6, characterized in that The Excel processing module includes: A file path unit, used for obtaining a target Excel file location according to an operating system file dialog box, wherein the Excel file contains a diagnostic test sequence; A file format verification unit is used to verify whether the format of the Excel file meets the preset standard; The data parsing unit is used to call the Excel switch function to establish a file operation channel, and extract the control parameters in the test sequence through the read and write functions. The parameters at least include the bus type, message address, diagnostic service identifier and expected response value.

8. The system according to claim 7, characterized in that The protocol conversion module comprises: The sending processing unit is used to implement multiplexing control in the PDU sending stage, dynamically select the CAN / CANFD message encapsulation format according to the target bus type, and use the message PDU sending function to send the assembled diagnostic PUD data; The receiving processing unit is used to perform demultiplexing processing in the PDU receiving stage and receive the diagnostic PDU data using the message PDU receiving function.

9. The system according to claim 8, characterized in that The API compatible modules include: The device abstract interface unit is used to call the unified message sending interface function, the unified message receiving interface function, the unified device startup function or the unified device shutdown function to realize the sending and receiving of bus messages and the startup and shutdown of bus devices; The driver adapter unit is used to dynamically load the hardware driver library file of the corresponding manufacturer when transmitting data through the unified message sending interface, and send the converted PDU data to the connected controller to be tested for diagnostic testing.

10. The system according to claim 9, characterized in that Further including: Configuration module, used to select the controller to be tested through the test interface and configure it before testing; The saving processing module is used to save the diagnostic report in Excel format after the test and display it on the test interface.

Images