Vehicle-mounted controller testing method and device and computer readable storage medium
By combining data comparison between diagnostic protocols and measurement protocols, a test report for on-board controllers is generated, which solves the problem of low accuracy caused by a single test method and improves the accuracy and efficiency of on-board controller testing.
Patent Information
- Application Number
- CN202411236264.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-04
- Publication Date
- 2024-12-10
AI Technical Summary
In the prior art, the test accuracy of on-board controllers is low, mainly due to test errors caused by a single test method.
By obtaining the diagnostic identifier generated by the on-board controller, using a combination of diagnostic protocols and measurement protocols, the diagnostic data and measurement data are obtained and compared, and the test report of the on-board controller is generated to ensure the accuracy of the test.
By integrating multiple protocol testing services, avoid errors in a single protocol testing service, improve the accuracy and efficiency of on-board controller testing, and ensure the accuracy of test data.
Smart Images

Figure CN119105454A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present invention relate to the field of automation technology, and in particular to a vehicle controller testing method, device and computer-readable storage medium. Background Art
[0002] At present, the vehicle controller is generally tested in one way, such as diagnostic testing through diagnostic protocol related services, or measurement testing through measurement protocol related services. However, a single test method is prone to test errors, resulting in low accuracy of vehicle controller testing. Therefore, a single vehicle controller test method has the problem of low accuracy of vehicle controller testing.
[0003] Therefore, there is an urgent need for a vehicle controller testing strategy to solve the problem of low vehicle controller testing accuracy due to a single vehicle controller testing method. Summary of the invention
[0004] In view of the above problems, embodiments of the present invention provide a vehicle controller testing method, device and computer-readable storage medium, which are used to solve the problem of low vehicle controller testing accuracy due to a single vehicle controller testing method.
[0005] According to one aspect of an embodiment of the present invention, a vehicle controller testing method is provided, the method comprising:
[0006] Obtaining a diagnostic identifier generated by a vehicle controller; wherein the diagnostic identifier is diagnostic information corresponding to a plurality of test areas of the vehicle;
[0007] Based on the diagnostic identifier and the first protocol, obtaining diagnostic data of each test area; wherein the first protocol is used for diagnosis of the onboard controller;
[0008] Based on the second protocol, each test area is detected to obtain measurement data of each test area; wherein the second protocol is used for detecting the vehicle controller;
[0009] The diagnostic data and the measurement data are compared to generate a test report of the vehicle controller.
[0010] According to another aspect of an embodiment of the present invention, there is provided a vehicle controller testing device, comprising:
[0011] A data acquisition module, configured to obtain diagnostic data of each test area based on the diagnostic identifier and a first protocol, wherein the first protocol is used for diagnosis of an onboard controller;
[0012] A diagnostic module, configured to detect each test area based on a second protocol and obtain measurement data of each test area; wherein the second protocol is used for detecting the vehicle controller;
[0013] A measurement module, used to detect each test area and obtain measurement data of each test area;
[0014] The result generating module is used to compare the diagnostic data with the measurement data and generate a test report of the vehicle controller.
[0015] In an optional manner, before generating a test report of the vehicle-mounted controller, the method further includes:
[0016] Summarize the test data corresponding to each diagnostic identifier; wherein the test data includes: diagnostic data and measurement data corresponding to each test area;
[0017] Each test data is transmitted to the external device, so that the external device generates a test report based on the received test data.
[0018] In an optional manner, the transmitting each test data to an external device includes:
[0019] Determining whether the test areas corresponding to each diagnostic identifier overlap;
[0020] If yes, each test data is numbered and the numbered test data is transmitted to an external device;
[0021] If not, each test data is directly transmitted to the external device.
[0022] In an optional manner, the step of marking each test data with a number includes:
[0023] According to the time sequence of generating the test data for each diagnostic identifier, each test data is numbered and labeled;
[0024] or,
[0025] Obtain the actual time required for each diagnostic identifier to generate test data, as well as the theoretical time required for each diagnostic identifier to generate test data, and number and label each test data according to the actual time, the theoretical time and preset rules; wherein the preset rules are specifically: based on the absolute value of the difference between the actual time and the theoretical time, number and label each test data in descending order.
[0026] In an optional manner, obtaining the diagnostic data of each test area based on the diagnostic identifier and the first protocol includes:
[0027] Based on the first protocol, matching the diagnostic identifier with identifier samples in a preset database;
[0028] The equipment operation data samples corresponding to the successfully matched identifier samples are retrieved as the diagnostic data of each test area.
[0029] In an optional manner, the detecting each test area to obtain measurement data of each test area includes:
[0030] According to the location information of the equipment corresponding to each test area, data is collected from the equipment to obtain real-time data of equipment operation as the measurement data of each test area.
[0031] In an optional manner, obtaining the diagnostic identifier generated by the vehicle controller includes:
[0032] Receiving a diagnostic configuration instruction input by a user; wherein the diagnostic configuration instruction includes: location information of the test device and test content;
[0033] The diagnostic configuration instruction is transmitted to the vehicle controller so that the vehicle controller uses the location information of the test device as the test area, tests the test area based on the test content, obtains response data fed back by the test area, and generates a diagnostic identifier based on the response data.
[0034] According to another aspect of an embodiment of the present invention, there is provided a vehicle controller testing device, comprising:
[0035] Obtaining a diagnostic identifier generated by a vehicle controller; wherein the diagnostic identifier is diagnostic information corresponding to a plurality of test areas of the vehicle;
[0036] Based on the diagnostic identifier and the first protocol, obtaining diagnostic data of each test area; wherein the first protocol is used for diagnosis of the onboard controller;
[0037] Based on the second protocol, each test area is detected to obtain measurement data of each test area; wherein the second protocol is used for detecting the vehicle controller;
[0038] The diagnostic data and the measurement data are compared to generate a test report of the vehicle controller.
[0039] In an optional manner, before generating a test report of the vehicle-mounted controller, the method further includes:
[0040] Summarize the test data corresponding to each diagnostic identifier; wherein the test data includes: diagnostic data and measurement data corresponding to each test area;
[0041] Each test data is transmitted to the external device, so that the external device generates a test report based on the received test data.
[0042] In an optional manner, the transmitting each test data to an external device includes:
[0043] Determining whether the test areas corresponding to each diagnostic identifier overlap;
[0044] If yes, each test data is numbered and the numbered test data is transmitted to an external device;
[0045] If not, each test data is directly transmitted to the external device.
[0046] In an optional manner, the step of marking each test data with a number includes:
[0047] According to the time sequence of generating the test data for each diagnostic identifier, each test data is numbered and labeled;
[0048] or,
[0049] Obtain the actual time required for each diagnostic identifier to generate test data, as well as the theoretical time required for each diagnostic identifier to generate test data, and number and label each test data according to the actual time, the theoretical time and preset rules; wherein the preset rules are specifically: based on the absolute value of the difference between the actual time and the theoretical time, number and label each test data in descending order.
[0050] In an optional manner, obtaining the diagnostic data of each test area based on the diagnostic identifier and the first protocol includes:
[0051] Based on the first protocol, matching the diagnostic identifier with identifier samples in a preset database;
[0052] The equipment operation data samples corresponding to the successfully matched identifier samples are retrieved as the diagnostic data of each test area.
[0053] In an optional manner, the detecting each test area to obtain measurement data of each test area includes:
[0054] According to the location information of the equipment corresponding to each test area, data is collected from the equipment to obtain real-time data of equipment operation as the measurement data of each test area.
[0055] In an optional manner, obtaining the diagnostic identifier generated by the vehicle controller includes:
[0056] Receiving a diagnostic configuration instruction input by a user; wherein the diagnostic configuration instruction includes: location information of the test device and test content;
[0057] The diagnostic configuration instruction is transmitted to the vehicle controller so that the vehicle controller uses the location information of the test device as the test area, tests the test area based on the test content, obtains response data fed back by the test area, and generates a diagnostic identifier based on the response data.
[0058] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, wherein the storage medium stores at least one executable instruction, and the executable instruction enables a vehicle controller test device / apparatus to perform the following operations:
[0059] Obtaining a diagnostic identifier generated by a vehicle controller; wherein the diagnostic identifier is diagnostic information corresponding to a plurality of test areas of the vehicle;
[0060] Based on the diagnostic identifier and the first protocol, obtaining diagnostic data of each test area; wherein the first protocol is used for diagnosis of the onboard controller;
[0061] Based on the second protocol, each test area is detected to obtain measurement data of each test area; wherein the second protocol is used for detecting the vehicle controller;
[0062] The diagnostic data and the measurement data are compared to generate a test report of the vehicle controller.
[0063] In an optional manner, before generating a test report of the vehicle-mounted controller, the method further includes:
[0064] Summarize the test data corresponding to each diagnostic identifier; wherein the test data includes: diagnostic data and measurement data corresponding to each test area;
[0065] Each test data is transmitted to the external device, so that the external device generates a test report based on the received test data.
[0066] In an optional manner, the transmitting each test data to an external device includes:
[0067] Determining whether the test areas corresponding to each diagnostic identifier overlap;
[0068] If yes, each test data is numbered and the numbered test data is transmitted to an external device;
[0069] If not, each test data is directly transmitted to the external device.
[0070] In an optional manner, the step of marking each test data with a number includes:
[0071] According to the time sequence of generating the test data for each diagnostic identifier, each test data is numbered and labeled;
[0072] or,
[0073] Obtain the actual time required for each diagnostic identifier to generate test data, as well as the theoretical time required for each diagnostic identifier to generate test data, and number and label each test data according to the actual time, the theoretical time and preset rules; wherein the preset rules are specifically: based on the absolute value of the difference between the actual time and the theoretical time, number and label each test data in descending order.
[0074] In an optional manner, obtaining the diagnostic data of each test area based on the diagnostic identifier and the first protocol includes:
[0075] Based on the first protocol, matching the diagnostic identifier with identifier samples in a preset database;
[0076] The equipment operation data samples corresponding to the successfully matched identifier samples are retrieved as the diagnostic data of each test area.
[0077] In an optional manner, the detecting each test area to obtain measurement data of each test area includes:
[0078] According to the location information of the equipment corresponding to each test area, data is collected from the equipment to obtain real-time data of equipment operation as the measurement data of each test area.
[0079] In an optional manner, obtaining the diagnostic identifier generated by the vehicle controller includes:
[0080] Receiving a diagnostic configuration instruction input by a user; wherein the diagnostic configuration instruction includes: location information of the test device and test content;
[0081] The diagnostic configuration instruction is transmitted to the vehicle controller so that the vehicle controller uses the location information of the test device as the test area, tests the test area based on the test content, obtains response data fed back by the test area, and generates a diagnostic identifier based on the response data.
[0082] The embodiment of the present invention reversely infers the diagnostic data through the first protocol based on the obtained diagnostic identifier of the vehicle controller, and detects the measurement data through the second protocol, compares the reversed diagnostic data with the detected measurement data, and then generates a test report of the vehicle controller. Compared with the prior art that only tests in a single way, the present application compares the data obtained by the diagnostic protocol test service and the data obtained by the detection protocol test service, which can avoid test errors caused by errors in a single protocol test service, and improve the test accuracy of the vehicle controller by integrating multiple protocol test services.
[0083] Furthermore, an embodiment of the present invention can detect the overlap of the test areas included in multiple diagnostic identifiers before generating a test report. If there is no overlap, the test report can be directly generated based on the existing data; if there is overlap, the data needs to be numbered and marked, and a test report is generated for the numbered data to distinguish the data corresponding to the overlapping test areas. When generating a test report, the present invention detects the overlapping test areas and marks them with numbers when they overlap, which can improve the efficiency of the vehicle controller test while ensuring the accuracy of the test data.
[0084] The above description is only an overview of the technical solution of the embodiment of the present invention. In order to more clearly understand the technical means of the embodiment of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0085] The accompanying drawings are only used to illustrate the embodiments and are not to be considered as limiting the present invention. In addition, the same reference symbols are used to represent the same components throughout the accompanying drawings. In the accompanying drawings:
[0086] Figure 1 A schematic diagram showing a flow chart of a first embodiment of a vehicle controller testing method provided by the present invention;
[0087] Figure 2 A schematic diagram showing an external connection structure diagram of the vehicle-mounted controller test device provided by the present invention;
[0088] Figure 3 A schematic structural diagram of a first embodiment of a vehicle controller testing device provided by the present invention is shown;
[0089] Figure 4 A schematic structural diagram of an embodiment of a vehicle controller testing device provided by the present invention is shown;
[0090] Figure 5 The structure diagram of the program architecture corresponding to the vehicle controller testing method provided by the present invention is shown. DETAILED DESCRIPTION
[0091] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be limited to the embodiments set forth herein.
[0092] Figure 1 FIG. 1 is a flow chart showing a first embodiment of a vehicle controller testing method of the present invention, wherein the method is executed by a vehicle controller testing device. Figure 1 As shown, the method comprises the following steps:
[0093] Step 110: Obtain a diagnostic identifier generated by a vehicle controller; wherein the diagnostic identifier is diagnostic information corresponding to a plurality of test areas of the vehicle.
[0094] In an optional manner, obtaining the diagnostic identifier generated by the vehicle controller includes:
[0095] Receiving a diagnostic configuration instruction input by a user; wherein the diagnostic configuration instruction includes: location information of the test device and test content;
[0096] The diagnostic configuration instruction is transmitted to the vehicle controller so that the vehicle controller uses the location information of the test device as the test area, tests the test area based on the test content, obtains response data fed back by the test area, and generates a diagnostic identifier based on the response data.
[0097] It can be understood that by receiving diagnostic configuration instructions input by the user, diagnostic changes can be made according to user needs when testing the vehicle controller, and the location information and test content of the required test equipment can be adjusted to test different functions of the vehicle controller.
[0098] In a specific embodiment, the user inputs the diagnosis configuration instructions through the original diagnosis questionnaire and the A2L file; this implementation sets the A2L file parsing module through a python script and performs A2L file parsing.
[0099] Step 120: Obtain diagnostic data of each test area based on the diagnostic identifier and the first protocol; wherein the first protocol is used for diagnosis of the onboard controller.
[0100] In an optional manner, obtaining the diagnostic data of each test area based on the diagnostic identifier and the first protocol includes:
[0101] Based on the first protocol, matching the diagnostic identifier with identifier samples in a preset database;
[0102] The equipment operation data samples corresponding to the successfully matched identifier samples are retrieved as the diagnostic data of each test area.
[0103] It can be understood that by matching the diagnostic identifier with the identifier samples in the preset database through the first protocol, the diagnostic data can be reversed based on the diagnostic identifier, thus laying a foundation for the implementation of multi-mode vehicle controller testing.
[0104] It should be noted that the first protocol may be one or more different protocols.
[0105] In a specific embodiment, the first protocol is the Unified Diagnostic Services (UDS) protocol. In this embodiment, a UDS diagnostic module is set in an external device through a python script, and the UDS diagnostic module is called to perform diagnosis based on UDS, such as routine control, diagnostic identifier writing, and diagnostic identifier reading.
[0106] Step 130: Based on the second protocol, each test area is tested to obtain measurement data of each test area; wherein the second protocol is used for testing the vehicle controller.
[0107] In an optional manner, the detecting each test area to obtain measurement data of each test area includes:
[0108] According to the location information of the equipment corresponding to each test area, data is collected from the equipment to obtain real-time data of equipment operation as the measurement data of each test area.
[0109] It can be understood that by collecting data on the location information of devices corresponding to several test areas through the second protocol, the measurement of device data is achieved, which further lays the foundation for the realization of multi-mode vehicle controller testing.
[0110] It should be noted that the second protocol may be one or more different protocols.
[0111] In a specific embodiment, the second protocol is the Universal Measurement and Calibration Protocol (XCP for short). In this implementation, an XCP calibration module is set up through a python script, and the XCP calibration module is called to calibrate and observe the internal quantities of the vehicle controller based on XCP.
[0112] Step 140: Compare the diagnostic data with the measurement data to generate a test report of the vehicle controller.
[0113] In this embodiment, the external device may be a PC.
[0114] In an optional manner, before generating a test report of the vehicle-mounted controller, the method further includes:
[0115] Summarize the test data corresponding to each diagnostic identifier; wherein the test data includes: diagnostic data and measurement data corresponding to each test area;
[0116] Each test data is transmitted to the external device, so that the external device generates a test report based on the received test data.
[0117] It is understandable that by transmitting the test data to an external device, the high computing power and high operating efficiency of the external device can be utilized to generate a test report, thereby improving the efficiency of generating the test report.
[0118] In a specific embodiment, the external device can generate a report by calling the pytest function and the allure function of python; wherein allure is a java library for beautifying test reports; and pytest is an automated testing framework library based on python.
[0119] In an optional manner, the transmitting each test data to an external device includes:
[0120] Determining whether the test areas corresponding to each diagnostic identifier overlap;
[0121] If yes, each test data is numbered and the numbered test data is transmitted to an external device;
[0122] If not, each test data is directly transmitted to the external device.
[0123] It is understandable that judging whether the test areas overlap and determining the test data number marking based on the overlap judgment result can improve the efficiency of generating the test report while ensuring that the test data is clear.
[0124] In an optional manner, the step of marking each test data with a number includes:
[0125] According to the time sequence of generating the test data for each diagnostic identifier, each test data is numbered and labeled;
[0126] or,
[0127] Obtain the actual time required for each diagnostic identifier to generate test data, as well as the theoretical time required for each diagnostic identifier to generate test data, and number and label each test data according to the actual time, the theoretical time and preset rules; wherein the preset rules are specifically: based on the absolute value of the difference between the actual time and the theoretical time, number and label each test data in descending order.
[0128] It can be understood that the test data can be numbered in two ways: by numbering in chronological order, the user can trace the data according to the set diagnostic order; and by comparing the absolute value of the difference between the actual duration and the theoretical duration of the test data generation, it can be known whether the test ended too early or too late. The test data with obviously abnormal end time is placed in front, which can enable the user to troubleshoot the fault earlier, thereby improving the operation and maintenance efficiency of the vehicle controller.
[0129] In a specific embodiment, see Figure 5 , Figure 5 A structural diagram of a program architecture provided for an embodiment of the present invention; Figure 5 A test program 510, a UDS diagnostic module 520, a configuration parsing module 530, an XCP calibration module 540, a connection module 550 and a test interface 560 are shown; wherein the test program executes the vehicle controller test method according to the present invention;
[0130] The A2L file is parsed through a configuration parsing module, and the parsed information is added to the database. A2L is a file written in a descriptive language similar to XML specified by the ASAP2 standard, which describes the measurement and calibration information. The ASAP2 standard is a set of standards developed by the ASAM organization for how the Master side describes and parses the information on the Slave side.
[0131] A connection module is used to adapt to different underlying buses (CAN, Ethernet), and the ZLGCANFD400U driver is also adapted;
[0132] Implement the UDS protocol through a UDS diagnostic module;
[0133] Implement the XCP protocol through an XCP calibration module;
[0134] The test interface includes: UDS TP module and XCP TP module. A UDS TP module is used to adapt different transport layer protocols (15765, DoIP), and an XCP TP module is used to implement the XCP TP layer protocol. The UDS TP module, XCPTP module and connection module are bridged together.
[0135] In addition, the UDS diagnostic module uses a config.ini configuration file to parameterize the UDS canfd path, UDS diagnostic parameters, and UDS diagnostic ID;
[0136] The XCP calibration module uses a XcpConfig.json configuration file to parameterize the XCP canfd path, XCP diagnostic parameters, and XCP diagnostic ID;
[0137] It can be understood that the user of the present invention exposes a test interface adapted to different bus (CAN / CANFD / Ethernet) protocols (13400 / 14229 / XCP / UDS), which can be automatically tested through pytest and allure.
[0138] In a specific embodiment, the PC computer parses the diagnostic identifiers and XCP calibration quantity lists that need to be calibrated and measured through the USD diagnostic module, and after parsing, calls the XCP calibration module to assemble the XCP message, and sends the assembled CAN / CANFD message to the CAN bus connected to the Ethernet message OBD port to calibrate the vehicle controller; then the diagnostic service is read through the UDS diagnostic module for the diagnostic identifier that needs to be read by UDS to obtain diagnostic data, and then calls the XCP calibration module to observe the measurement quantity corresponding to the diagnostic identifier to obtain the measurement. The message required for measurement and the message required for diagnosis are sent to the OBD port through ZLG or PC, and then the diagnostic data and the measurement data are compared to verify whether the diagnostic identifier is developed correctly. The results of the above judgment are input into pytest, and allure is used to generate an automated test report.
[0139] Beneficial Effects
[0140] The embodiment of the present invention reversely infers the diagnostic data through the first protocol based on the obtained diagnostic identifier of the vehicle controller, and detects the measurement data through the second protocol, compares the reversed diagnostic data with the detected measurement data, and then generates a test report of the vehicle controller. Compared with the prior art that only tests in a single way, the present application compares the data obtained by the diagnostic protocol test service and the data obtained by the detection protocol test service, which can avoid test errors caused by errors in a single protocol test service, and improve the test accuracy of the vehicle controller by integrating multiple protocol test services.
[0141] Furthermore, an embodiment of the present invention can detect the overlap of the test areas included in multiple diagnostic identifiers before generating a test report. If there is no overlap, the test report can be directly generated based on the existing data; if there is overlap, the data needs to be numbered and marked, and a test report is generated for the numbered data to distinguish the data corresponding to the overlapping test areas. When generating a test report, the present invention detects the overlapping test areas and marks them with numbers when they overlap, which can improve the efficiency of the vehicle controller test while ensuring the accuracy of the test data.
[0142] Figure 2 The figure shows the external connection structure of the vehicle controller test device of the present invention. Figure 2 As shown, the external connection structure diagram includes the following modules: vehicle controller OBD interface 210, ZLG 220, PC computer USB / Ethernet 230 and PC program 240;
[0143] In this embodiment, ZLG is Zhou Ligong, a CAN bus measurement tool.
[0144] Beneficial Effects
[0145] This embodiment can test the vehicle controller only through ZLG and the test program. Compared with the existing software, it reduces unnecessary test components and UI components, has a fast startup speed, and can better cover the test scenarios that require a quick connection after power-on. At the same time, the python interface set by the PC program has better compatibility, scalability and ease of learning than the interface exposed by professional software.
[0146] Figure 3 FIG. 2 is a schematic diagram showing the structure of an embodiment of a vehicle controller testing device of the present invention. Figure 3 As shown, the device 300 includes: a data acquisition module 310 , a diagnosis module 320 , a measurement module 330 and a result generation module 340 .
[0147] A data acquisition module, configured to obtain diagnostic data of each test area based on the diagnostic identifier and a first protocol, wherein the first protocol is used for diagnosis of an onboard controller;
[0148] A diagnostic module, configured to detect each test area based on a second protocol and obtain measurement data of each test area; wherein the second protocol is used for detecting the vehicle controller;
[0149] A measurement module, used to detect each test area and obtain measurement data of each test area;
[0150] The result generating module is used to compare the diagnostic data with the measurement data and generate a test report of the vehicle controller.
[0151] In an optional manner, before generating a test report of the vehicle-mounted controller, the method further includes:
[0152] Summarize the test data corresponding to each diagnostic identifier; wherein the test data includes: diagnostic data and measurement data corresponding to each test area;
[0153] Each test data is transmitted to the external device, so that the external device generates a test report based on the received test data.
[0154] In an optional manner, the transmitting each test data to an external device includes:
[0155] Determining whether the test areas corresponding to each diagnostic identifier overlap;
[0156] If yes, each test data is numbered and the numbered test data is transmitted to an external device;
[0157] If not, each test data is directly transmitted to the external device.
[0158] In an optional manner, the step of marking each test data with a number includes:
[0159] According to the time sequence of generating the test data for each diagnostic identifier, each test data is numbered and labeled;
[0160] or,
[0161] Obtain the actual time required for each diagnostic identifier to generate test data, as well as the theoretical time required for each diagnostic identifier to generate test data, and number and label each test data according to the actual time, the theoretical time and preset rules; wherein the preset rules are specifically: based on the absolute value of the difference between the actual time and the theoretical time, number and label each test data in descending order.
[0162] In an optional manner, obtaining the diagnostic data of each test area based on the diagnostic identifier and the first protocol includes:
[0163] Based on the first protocol, matching the diagnostic identifier with identifier samples in a preset database;
[0164] The equipment operation data samples corresponding to the successfully matched identifier samples are retrieved as the diagnostic data of each test area.
[0165] In an optional manner, the detecting each test area to obtain measurement data of each test area includes:
[0166] According to the location information of the equipment corresponding to each test area, data is collected from the equipment to obtain real-time data of equipment operation as the measurement data of each test area.
[0167] In an optional manner, obtaining the diagnostic identifier generated by the vehicle controller includes:
[0168] Receiving a diagnostic configuration instruction input by a user; wherein the diagnostic configuration instruction includes: location information of the test device and test content;
[0169] The diagnostic configuration instruction is transmitted to the vehicle controller so that the vehicle controller uses the location information of the test device as the test area, tests the test area based on the test content, obtains response data fed back by the test area, and generates a diagnostic identifier based on the response data.
[0170] Beneficial Effects
[0171] The embodiment of the present invention reversely infers the diagnostic data through the first protocol based on the obtained diagnostic identifier of the vehicle controller, and detects the measurement data through the second protocol, compares the reversed diagnostic data with the detected measurement data, and then generates a test report of the vehicle controller. Compared with the prior art that only tests in a single way, the present application compares the data obtained by the diagnostic protocol test service and the data obtained by the detection protocol test service, which can avoid test errors caused by errors in a single protocol test service, and improve the test accuracy of the vehicle controller by integrating multiple protocol test services.
[0172] Furthermore, an embodiment of the present invention can detect the overlap of the test areas included in multiple diagnostic identifiers before generating a test report. If there is no overlap, the test report can be directly generated based on the existing data; if there is overlap, the data needs to be numbered and marked, and a test report is generated for the numbered data to distinguish the data corresponding to the overlapping test areas. When generating a test report, the present invention detects the overlapping test areas and marks them with numbers when they overlap, which can improve the efficiency of the vehicle controller test while ensuring the accuracy of the test data.
[0173] Figure 4 The schematic diagram of the structure of an embodiment of the vehicle controller test device of the present invention is shown. The specific embodiment of the present invention does not limit the specific implementation of the vehicle controller test device.
[0174] like Figure 4 As shown, the vehicle-mounted controller test device may include: a processor (processor) 402 , a communications interface (Communications Interface) 404 , a memory (memory) 406 , and a communication bus 408 .
[0175] The processor 402, the communication interface 404, and the memory 406 communicate with each other via the communication bus 408. The communication interface 404 is used to communicate with other devices such as a client or other server network elements. The processor 402 is used to execute the program 410, which can specifically execute the relevant steps in the above-mentioned embodiment of the vehicle controller test method.
[0176] Specifically, the program 410 may include program code including computer executable instructions.
[0177] The processor 402 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiment of the present invention. The one or more processors included in the vehicle controller test equipment may be processors of the same type, such as one or more CPUs; or may be processors of different types, such as one or more CPUs and one or more ASICs.
[0178] The memory 406 is used to store the program 410. The memory 406 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
[0179] The program 410 may be specifically called by the processor 402 to enable the vehicle controller test device to perform the following operations:
[0180] Obtaining a diagnostic identifier generated by a vehicle controller; wherein the diagnostic identifier is diagnostic information corresponding to a plurality of test areas of the vehicle;
[0181] Based on the diagnostic identifier and the first protocol, obtaining diagnostic data of each test area; wherein the first protocol is used for diagnosis of the onboard controller;
[0182] Based on the second protocol, each test area is detected to obtain measurement data of each test area; wherein the second protocol is used for detecting the vehicle controller;
[0183] The diagnostic data and the measurement data are compared to generate a test report of the vehicle controller.
[0184] In an optional manner, before generating a test report of the vehicle-mounted controller, the method further includes:
[0185] Summarize the test data corresponding to each diagnostic identifier; wherein the test data includes: diagnostic data and measurement data corresponding to each test area;
[0186] Each test data is transmitted to the external device, so that the external device generates a test report based on the received test data.
[0187] In an optional manner, the transmitting each test data to an external device includes:
[0188] Determining whether the test areas corresponding to each diagnostic identifier overlap;
[0189] If yes, each test data is numbered and the numbered test data is transmitted to an external device;
[0190] If not, each test data is directly transmitted to the external device.
[0191] In an optional manner, the step of marking each test data with a number includes:
[0192] According to the time sequence of generating the test data for each diagnostic identifier, each test data is numbered and labeled;
[0193] or,
[0194] Obtain the actual time required for each diagnostic identifier to generate test data, as well as the theoretical time required for each diagnostic identifier to generate test data, and number and label each test data according to the actual time, the theoretical time and preset rules; wherein the preset rules are specifically: based on the absolute value of the difference between the actual time and the theoretical time, number and label each test data in descending order.
[0195] In an optional manner, obtaining the diagnostic data of each test area based on the diagnostic identifier and the first protocol includes:
[0196] Based on the first protocol, matching the diagnostic identifier with identifier samples in a preset database;
[0197] The equipment operation data samples corresponding to the successfully matched identifier samples are retrieved as the diagnostic data of each test area.
[0198] In an optional manner, the detecting each test area to obtain measurement data of each test area includes:
[0199] According to the location information of the equipment corresponding to each test area, data is collected from the equipment to obtain real-time data of equipment operation as the measurement data of each test area.
[0200] In an optional manner, obtaining the diagnostic identifier generated by the vehicle controller includes:
[0201] Receiving a diagnostic configuration instruction input by a user; wherein the diagnostic configuration instruction includes: location information of the test device and test content;
[0202] The diagnostic configuration instruction is transmitted to the vehicle controller so that the vehicle controller uses the location information of the test device as the test area, tests the test area based on the test content, obtains response data fed back by the test area, and generates a diagnostic identifier based on the response data.
[0203] Beneficial Effects
[0204] The embodiment of the present invention reversely infers the diagnostic data through the first protocol based on the obtained diagnostic identifier of the vehicle controller, and detects the measurement data through the second protocol, compares the reversed diagnostic data with the detected measurement data, and then generates a test report of the vehicle controller. Compared with the prior art that only tests in a single way, the present application compares the data obtained by the diagnostic protocol test service and the data obtained by the detection protocol test service, which can avoid test errors caused by errors in a single protocol test service, and improve the test accuracy of the vehicle controller by integrating multiple protocol test services.
[0205] Furthermore, an embodiment of the present invention can detect the overlap of the test areas included in multiple diagnostic identifiers before generating a test report. If there is no overlap, the test report can be directly generated based on the existing data; if there is overlap, the data needs to be numbered and marked, and a test report is generated for the numbered data to distinguish the data corresponding to the overlapping test areas. When generating a test report, the present invention detects the overlapping test areas and marks them with numbers when they overlap, which can improve the efficiency of the vehicle controller test while ensuring the accuracy of the test data.
[0206] An embodiment of the present invention provides a computer-readable storage medium, which stores at least one executable instruction. When the executable instruction is executed on a vehicle controller testing device / apparatus, the vehicle controller testing device / apparatus executes the vehicle controller testing method in any of the above method embodiments.
[0207] The executable instructions may be specifically used to enable the vehicle controller test equipment / device to perform the following operations:
[0208] Obtaining a diagnostic identifier generated by a vehicle controller; wherein the diagnostic identifier is diagnostic information corresponding to a plurality of test areas of the vehicle;
[0209] Based on the diagnostic identifier and the first protocol, obtaining diagnostic data of each test area; wherein the first protocol is used for diagnosis of the onboard controller;
[0210] Based on the second protocol, each test area is detected to obtain measurement data of each test area; wherein the second protocol is used for detecting the vehicle controller;
[0211] The diagnostic data and the measurement data are compared to generate a test report of the vehicle controller.
[0212] In an optional manner, before generating a test report of the vehicle-mounted controller, the method further includes:
[0213] Summarize the test data corresponding to each diagnostic identifier; wherein the test data includes: diagnostic data and measurement data corresponding to each test area;
[0214] Each test data is transmitted to the external device, so that the external device generates a test report based on the received test data.
[0215] In an optional manner, the transmitting each test data to an external device includes:
[0216] Determining whether the test areas corresponding to each diagnostic identifier overlap;
[0217] If yes, each test data is numbered and the numbered test data is transmitted to an external device;
[0218] If not, each test data is directly transmitted to the external device.
[0219] In an optional manner, the step of marking each test data with a number includes:
[0220] According to the time sequence of generating the test data for each diagnostic identifier, each test data is numbered and labeled;
[0221] or,
[0222] Obtain the actual time required for each diagnostic identifier to generate test data, as well as the theoretical time required for each diagnostic identifier to generate test data, and number and label each test data according to the actual time, the theoretical time and preset rules; wherein the preset rules are specifically: based on the absolute value of the difference between the actual time and the theoretical time, number and label each test data in descending order.
[0223] In an optional manner, obtaining the diagnostic data of each test area based on the diagnostic identifier and the first protocol includes:
[0224] Based on the first protocol, matching the diagnostic identifier with identifier samples in a preset database;
[0225] The equipment operation data samples corresponding to the successfully matched identifier samples are retrieved as the diagnostic data of each test area.
[0226] In an optional manner, the detecting each test area to obtain measurement data of each test area includes:
[0227] According to the location information of the equipment corresponding to each test area, data is collected from the equipment to obtain real-time data of equipment operation as the measurement data of each test area.
[0228] In an optional manner, obtaining the diagnostic identifier generated by the vehicle controller includes:
[0229] Receiving a diagnostic configuration instruction input by a user; wherein the diagnostic configuration instruction includes: location information of the test device and test content;
[0230] The diagnostic configuration instruction is transmitted to the vehicle controller so that the vehicle controller uses the location information of the test device as the test area, tests the test area based on the test content, obtains response data fed back by the test area, and generates a diagnostic identifier based on the response data.
[0231] Beneficial Effects
[0232] The embodiment of the present invention reversely infers the diagnostic data through the first protocol based on the obtained diagnostic identifier of the vehicle controller, and detects the measurement data through the second protocol, compares the reversed diagnostic data with the detected measurement data, and then generates a test report of the vehicle controller. Compared with the prior art that only tests in a single way, the present application compares the data obtained by the diagnostic protocol test service and the data obtained by the detection protocol test service, which can avoid test errors caused by errors in a single protocol test service, and improve the test accuracy of the vehicle controller by integrating multiple protocol test services.
[0233] Furthermore, an embodiment of the present invention can detect the overlap of the test areas included in multiple diagnostic identifiers before generating a test report. If there is no overlap, the test report can be directly generated based on the existing data; if there is overlap, the data needs to be numbered and marked, and a test report is generated for the numbered data to distinguish the data corresponding to the overlapping test areas. When generating a test report, the present invention detects the overlapping test areas and marks them with numbers when they overlap, which can improve the efficiency of the vehicle controller test while ensuring the accuracy of the test data.
[0234] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system or other device. In addition, the embodiments of the present invention are not directed to any particular programming language.
[0235] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. Similarly, in order to simplify the present invention and help understand one or more of the various inventive aspects, in the above description of exemplary embodiments of the present invention, the various features of the embodiments of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. Wherein, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, wherein each claim itself is a separate embodiment of the present invention.
[0236] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and further may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive.
[0237] It should be noted that the above embodiments illustrate the present invention rather than limit it, and that those skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets shall not be construed as a limitation on the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention may be implemented by means of hardware comprising a number of different elements and by means of a suitably programmed computer. In a unit claim enumerating a number of devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.
Claims
1. A vehicle controller testing method, characterized in that: The method comprises: Obtaining a diagnostic identifier generated by a vehicle controller; wherein the diagnostic identifier is diagnostic information corresponding to a plurality of test areas of the vehicle; Based on the diagnostic identifier and the first protocol, obtaining diagnostic data of each test area; wherein the first protocol is used for diagnosis of the onboard controller; Based on the second protocol, each test area is detected to obtain measurement data of each test area; wherein the second protocol is used for detecting the vehicle controller; The diagnostic data and the measurement data are compared to generate a test report of the vehicle controller.
2. The method according to claim 1, characterized in that Before generating the test report of the vehicle controller, the method further includes: Summarize the test data corresponding to each diagnostic identifier; wherein the test data includes: diagnostic data and measurement data corresponding to each test area; Each test data is transmitted to the external device, so that the external device generates a test report based on the received test data.
3. The method according to claim 2, characterized in that The transmitting each test data to the external device comprises: Determining whether the test areas corresponding to each diagnostic identifier overlap; If yes, each test data is numbered and the numbered test data is transmitted to an external device; If not, each test data is directly transmitted to the external device.
4. The method according to claim 3, characterized in that: The step of marking each test data with a number includes: According to the time sequence of generating the test data for each diagnostic identifier, each test data is numbered and labeled; or, Obtain the actual time required for each diagnostic identifier to generate test data, as well as the theoretical time required for each diagnostic identifier to generate test data, and number and label each test data according to the actual time, the theoretical time and preset rules; wherein the preset rules are specifically: based on the absolute value of the difference between the actual time and the theoretical time, number and label each test data in descending order.
5. The method according to any one of claims 1 to 4, characterized in that: The obtaining of diagnostic data of each test area based on the diagnostic identifier and the first protocol comprises: Based on the first protocol, matching the diagnostic identifier with identifier samples in a preset database; The equipment operation data samples corresponding to the successfully matched identifier samples are retrieved as the diagnostic data of each test area.
6. The method according to any one of claims 1 to 4, characterized in that: The detecting each test area to obtain the measurement data of each test area includes: According to the location information of the equipment corresponding to each test area, data is collected from the equipment to obtain real-time data of equipment operation as the measurement data of each test area.
7. The method according to claim 1, characterized in that The step of obtaining a diagnostic identifier generated by the vehicle-mounted controller includes: Receive a diagnostic configuration instruction input by a user; wherein the diagnostic configuration instruction includes: location information of the test device and test content; The diagnostic configuration instruction is transmitted to the vehicle controller so that the vehicle controller uses the location information of the test device as the test area, tests the test area based on the test content, obtains response data fed back by the test area, and generates a diagnostic identifier based on the response data.
8. A vehicle controller testing device, characterized in that: The device comprises: A data acquisition module, configured to obtain diagnostic data of each test area based on the diagnostic identifier and a first protocol, wherein the first protocol is used for diagnosis of an onboard controller; A diagnostic module, configured to detect each test area based on a second protocol and obtain measurement data of each test area; wherein the second protocol is used for detecting the vehicle controller; A measurement module, used to detect each test area and obtain measurement data of each test area; The result generating module is used to compare the diagnostic data with the measurement data and generate a test report of the vehicle controller.
9. A vehicle controller test device, characterized in that: include: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the operation of the vehicle controller testing method as described in any one of claims 1-7.
10. A computer-readable storage medium, characterized in that: The storage medium stores at least one executable instruction. When the executable instruction is executed on the vehicle controller testing device / apparatus, the vehicle controller testing device / apparatus performs the operation of the vehicle controller testing method as described in any one of claims 1-7.
