Vehicle electrical function test method, device and equipment and storage medium

Abstract

A vehicle electrical function test method, apparatus and device, and a computer readable storage medium, the method comprising: detecting an operation instruction in a graphical programming interface, and according to the operation instruction, calling a preset UDS instruction set editor to edit an ECU instruction and calling a preset test scene editor to edit test scene information; generating a UDS instruction sequence file based on the ECU instruction and the test scene information; sending the UDS instruction sequence file to an edge device to obtain a target log file uploaded by the edge device, and converting the target log file into an asc file; and verifying the asc file according to a preset verification rule, and generating a test report, so that the technical problem that the accuracy of a UDS diagnosis result cannot be improved due to the fact that the UDS application message cannot be monitored and acquired and the application message cannot be analyzed in related technologies is solved, UDS diagnosis and acquisition and analysis of the application message are realized, and the accuracy of the UDS diagnosis result cannot be improved. And the accuracy of function test results is improved.

Description

Technical Field

[0001] This application relates to the field of vehicle testing technology, specifically to a method, apparatus, equipment, and computer-readable storage medium for testing the electrical functions of a vehicle. Background Technology

[0002] In the field of automotive electronic diagnostics, Unified Diagnostic Service (UDS) plays an indispensable role as an industry-standard diagnostic tool in vehicle fault detection, condition monitoring, and system configuration. The accuracy of UDS diagnostic results directly affects the precise location of problems in the vehicle's electronic control units, thereby impacting vehicle repair efficiency and driving safety. UDS application messages, as a crucial carrier of information exchange between various electronic control units during UDS diagnostics, contain a wealth of key data, including diagnostic requests, responses, and vehicle operating status. Effective monitoring and acquisition of UDS application messages, followed by in-depth analysis, are essential prerequisites for improving the accuracy of UDS diagnostic results. Analysis of these application messages allows for a clear understanding of the execution process of diagnostic commands, the integrity of data transmission, and the coordination among various control units, thus providing a strong basis for judging the reliability of diagnostic results. However, in current automotive electrical function testing and diagnostics, there is a common problem of being unable to effectively monitor and acquire UDS application messages. Due to the lack of corresponding technical means and tools, it is difficult to capture the transmission trajectory and specific content of UDS application messages in real time. Even if some messages can be acquired, the lack of professional parsing capabilities often prevents the conversion of the binary data in the messages into meaningful diagnostic information, resulting in an inability to deeply understand the diagnostic process and vehicle status reflected in the messages. The inability to monitor, acquire, and parse UDS application messages makes it difficult for diagnostic personnel to comprehensively and accurately assess the authenticity and validity of UDS diagnostic results. When faced with complex vehicle faults, misinterpretations of diagnostic results may lead to incorrect repair measures, increasing repair costs and time, and potentially creating safety hazards. Furthermore, this also limits the depth and breadth of automotive electrical function testing, hindering the provision of reliable data analysis support for the optimization and upgrading of vehicle electronic systems. Therefore, solving the problems of monitoring, acquiring, and parsing UDS application messages is of great practical significance for improving the accuracy of UDS diagnostic results and promoting the development of automotive diagnostic technology. Summary of the Invention

[0003] This application provides a method, apparatus, device, and computer-readable storage medium for testing vehicle electrical functions, which can solve the technical problems existing in the prior art that cannot monitor and acquire UDS application messages, and cannot parse application messages, thus failing to improve the accuracy of UDS diagnostic results.

[0004] In a first aspect, embodiments of this application provide a method for testing the electrical functions of a vehicle, the method comprising: Operation commands are detected in the graphical programming interface, and the preset UDS instruction set editor is called to edit ECU commands and the preset test scenario editor is called to edit test scenario information according to the operation commands. The test scenario information includes the vehicle's electrical function modules. Based on the ECU instructions and the test scenario information, a UDS instruction sequence file is generated; The UDS instruction sequence file is sent to the edge device to obtain the target log file uploaded by the edge device, and the target log file is converted into an .asc file. The target log file is generated by the edge device testing the vehicle based on the UDS instruction sequence file and monitoring the diagnostic information and application messages during the vehicle testing process in real time. The .asc file is verified according to preset verification rules, and a test report is generated, which characterizes the performance status of the vehicle's electrical functions.

[0005] In conjunction with the first aspect, in one implementation, the step of verifying the .asc file according to preset verification rules and generating a test report includes: The preset verification rules include Uds verification rules and Message verification rules; The asc file is verified according to the Uds verification rules to obtain a first verification result, wherein the first verification result includes verifying whether the UDS response data in the target log file meets expectations; The asc file is verified according to the Message verification rules to obtain a second verification result, wherein the second verification result includes verifying the validity of the application message in the target log file; A test report is generated based on the first verification result and the second verification result.

[0006] In conjunction with the first aspect, in one implementation, the step of verifying the .asc file according to the Uds verification rules to obtain a first verification result includes: The Uds verification rules include time verification logic rules and message content verification logic rules; The time verification logic rules are used to verify whether the UDS response data in the .asc file was obtained within the preset time period, and the first verification information is obtained. The message content verification logic is used to verify whether the UDS response data in the .asc file responds to the message and to obtain the second verification information. Based on the first verification information and the second verification information, a first verification result is generated.

[0007] In conjunction with the first aspect, in one implementation, the step of verifying the .asc file according to the Message verification rules to obtain a second verification result includes: The message verification rules include parsing rules and validity verification rules; The .asc file is parsed using the aforementioned parsing rules to obtain application messages; The sampled values ​​in the application message are validated using validity verification rules to obtain a second verification result.

[0008] In conjunction with the first aspect, in one implementation, obtaining the target log file uploaded by the edge device includes: The UDS instruction sequence file is sent to the edge device so that the edge device can test the vehicle based on the UDS instruction sequence in the UDS instruction sequence file. The UDS instruction sequence includes the name of the ECU to be tested, the number of executions, the execution priority, and the execution duration. The diagnostic information is obtained by the diagnostic monitoring module in the edge device during the real-time monitoring of the vehicle executing the UDS command sequence. The application messages are recorded by the application message listening module in the edge device, which listens to the UDS instruction sequence executed by the vehicle.

[0009] In conjunction with the first aspect, in one implementation, the step of calling the preset test scenario editor to edit the test scenario information includes: The system invokes a preset test scenario editor, which includes a template graphics container and a preset database. The graphical programming interface allows users to select target electrical function modules from the preset database through drag-and-drop operations; The target electrical function module is configured to the CAN channel according to the drag-and-drop operation, and the test scenario information is edited, wherein there are multiple CAN channels.

[0010] In conjunction with the first aspect, in one implementation, configuring the target electrical function module to a designated CAN channel according to the drag-and-drop operation and editing the test scenario information includes: If multiple target electrical function modules are detected in any one of the CAN channels, the multiple target electrical function modules in any one of the CAN channels are sorted so that the multiple target electrical function modules in the CAN channels are executed serially. If multiple target electrical function modules are detected in multiple CAN channels, the target electrical function modules in the multiple CAN channels will be executed in parallel logic. The test scenario information is edited by executing logic serially on multiple target electrical function modules in the CAN channel, and / or executing logic in parallel on multiple target electrical function modules in the CAN channel.

[0011] Secondly, embodiments of this application provide a testing device for vehicle electrical functions, the testing device for vehicle electrical functions comprising: The editing module is used to detect operation commands in the graphical programming interface, and to call the preset UDS instruction set editor to edit ECU commands and the preset test scenario editor to edit test scenario information according to the operation commands. The test scenario information includes the vehicle's electrical function modules. The first generation module is used to generate a UDS instruction sequence file based on the ECU instructions and the test scenario information; The acquisition module is used to send the UDS instruction sequence file to the edge device to obtain the target log file uploaded by the edge device, and convert the target log file into an asc file. The target log file is generated by the edge device testing the vehicle based on the UDS instruction sequence file and listening to the diagnostic information and application messages during the vehicle testing process in real time. The second generation module is used to verify the .asc file according to preset verification rules and generate a test report, which characterizes the performance status of the vehicle's electrical functions.

[0012] Thirdly, embodiments of this application provide a vehicle electrical function testing device, which includes a processor, a memory, and a vehicle electrical function testing program stored in the memory and executable by the processor. When the vehicle electrical function testing program is executed by the processor, it implements the steps of the vehicle electrical function testing method described above.

[0013] Fourthly, a computer-readable storage medium storing a test program for a vehicle electrical function, wherein when the test program for the vehicle electrical function is executed by a processor, it implements the steps of the test method for the vehicle electrical function as described above.

[0014] The beneficial effects of the technical solutions provided in this application include: By detecting operation commands in a graphical programming interface, and based on these commands, calling a preset UDS command set editor to edit ECU commands and a preset test scenario editor to edit test scenario information (including the vehicle's electrical function modules), a UDS command sequence file is generated. This UDS command sequence file is then sent to an edge device to obtain a target log file uploaded by the edge device. The target log file is then converted into an ASCII file, generated by the edge device testing the vehicle based on the UDS command sequence file and monitoring diagnostic information and application messages during the testing process in real time. The ASCII file is then verified according to preset verification rules to generate a test report. This test report characterizes the performance status of the vehicle's electrical functions. This addresses the technical problems in related technologies where monitoring and obtaining UDS application messages and parsing them are impossible, thus hindering the accuracy of UDS diagnostic results. This method enables the acquisition and analysis of UDS diagnostic and application messages, improving the accuracy of functional test results. Attached Figure Description

[0015] Figure 1 This is a flowchart illustrating the first embodiment of the vehicle electrical function testing method of this application; Figure 2 For this application Figure 1 A detailed flowchart of step S40; Figure 3 This is a schematic diagram of the functional modules of an embodiment of the vehicle electrical function testing device of this application; Figure 4 This is a schematic diagram of the hardware structure of the vehicle electrical function testing equipment involved in the embodiments of this application. Detailed Implementation

[0016] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0017] First, some of the technical terms used in this application will be explained to help those skilled in the art understand this application.

[0018] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0019] In a first aspect, embodiments of this application provide a method for testing the electrical functions of a vehicle.

[0020] In one embodiment, reference is made to Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the vehicle electrical function testing method of this application. Figure 1 As shown, the test methods for vehicle electrical functions include: Step S10: An operation command is detected in the graphical programming interface, and the preset UDS instruction set editor is called to edit the ECU command and the preset test scenario editor is called to edit the test scenario information according to the operation command. The test scenario information includes the vehicle's electrical function modules. As an example, the user's operation commands are detected in the graphical programming interface, and the preset UDS instruction set editor and preset test scenario editor are invoked based on the user's operation commands. ECU commands are edited through the preset UDS instruction set editor, and test scenario information is edited through the preset test scenario editor.

[0021] Specifically, calling the preset test scenario editor to edit test scenario information includes: calling the preset test scenario editor, wherein the preset test scenario editor includes a template graphic container, and the template graphic container includes a preset database, the graphical programming interface allows users to select target electrical function modules in the preset database through drag-and-drop operations; configuring the target electrical function modules to CAN channels according to the drag-and-drop operations, and editing the test scenario information, wherein there are multiple CAN channels.

[0022] The exemplary pre-built test scenario editor includes a template graphical container containing a pre-built database of multiple vehicle electrical function modules. A graphical programming interface allows users to select target electrical function modules from the pre-built database via drag-and-drop operations, configuring them to CAN channels and editing test scenario information. Multiple CAN channels are available. For example, at the scenario level, there are four CAN channels (CAN0-CAN3), each executing in parallel. Users can freely select icons from the module or model library for each CAN channel and drag them into the CAN channel to execute the corresponding module or model. At the template level, users can select corresponding model icons from the model library and drag them to the template graphical container, where the order of the models can be freely adjusted.

[0023] Specifically, configuring the target electrical function module to the specified CAN channel according to the drag-and-drop operation and editing the test scenario information includes: If multiple target electrical function modules are detected in any one of the CAN channels, the multiple target electrical function modules in any one of the CAN channels are sorted to perform serial execution logic on the multiple target electrical function modules in the CAN channels; if multiple target electrical function modules are detected in multiple CAN channels, the target electrical function modules in the multiple CAN channels are executed in parallel; by performing serial execution logic on the multiple target electrical function modules in the CAN channels and / or performing parallel execution logic on the multiple target electrical function modules in the multiple CAN channels, the test scenario information is edited.

[0024] Exemplary, if multiple target electrical function modules are detected in any one CAN channel, these modules are ordered to execute logic serially. If multiple target electrical function modules are detected in multiple CAN channels, their logic is executed in parallel. The test scenario information is edited by executing logic serially and / or in parallel on the multiple target electrical function modules in the CAN channels.

[0025] Step S20: Generate a UDS instruction sequence file based on the ECU instructions and the test scenario information; As an example, ECU commands and test scenario information are used to generate a UDS command sequence file, which contains multiple UDS command sequence files and is a JSON file.

[0026] Step S30: Send the UDS instruction sequence file to the edge device to obtain the target log file uploaded by the edge device, and convert the target log file into an asc file. The target log file is generated by the edge device testing the vehicle based on the UDS instruction sequence file and monitoring the diagnostic information and application messages during the vehicle testing process in real time. As an example, the UDS instruction sequence file is sent to the edge device. The edge device reads the UDS instruction sequence in the UDS instruction sequence file to test the vehicle, monitors the diagnostic information and application messages during the vehicle test in real time, generates a target log file from the monitored diagnostic information and application messages, and uploads it.

[0027] Specifically, obtaining the target log file uploaded by the edge device includes: The UDS instruction sequence file is sent to an edge device so that the edge device can test the vehicle based on the UDS instruction sequence in the UDS instruction sequence file. The UDS instruction sequence includes the name of the ECU to be tested, the number of executions, the execution priority, and the execution duration. The diagnostic information is obtained by the diagnostic monitoring module in the edge device monitoring the vehicle's execution of the UDS instruction sequence in real time. The application messages are recorded by the application message monitoring module in the edge device monitoring the vehicle's execution of the UDS instruction sequence.

[0028] As an example, the edge device includes an instruction parsing module, an instruction execution module, a diagnostic monitoring module, an application message monitoring module, and a file upload module. The instruction parsing module is responsible for parsing JSON files, extracting the UDS instruction sequence (including the name of the detected ECU, execution count, execution priority, and execution duration), and issuing execution instructions to the instruction execution module. Extraction rules are based on predefined attributes in the JSON file, such as `count` (execution count), `ecu_name` (ECU name), and `vin` (VIN code of the vehicle being tested). The instruction execution module executes the instructions issued by the instruction parsing module and triggers the subsequent diagnostic and application message monitoring modules. During the execution of the UDS instruction sequence, the diagnostic monitoring module monitors the execution process in real time using a loosely coupled approach and generates BLF format log files in real time. The purpose of real-time monitoring is to collect signal messages on the CAN bus during vehicle testing. These messages are used for subsequent result parsing; the real-time approach is primarily to achieve simultaneous testing and parsing, shortening the overall testing time. Generate BLF format log files: Based on the timestamp of the device's executed instructions, capture signal messages on the CAN line and generate them in the specified format, here BLF format. Application message monitoring module: Triggered simultaneously with the diagnostic monitoring module, the final monitoring data is stored in the same BLF log file; the final monitoring data is determined by the execution rounds in the JSON file, and after each round, the collected application messages are merged and saved. File upload module: Generates a target log file from the monitored diagnostic information and application messages, and uploads it. The diagnostic information is in BLF format. Convert the acquired target log file into an ASC file.

[0029] Step S40: Verify the .asc file according to the preset verification rules and generate a test report, which characterizes the performance status of the vehicle's electrical functions.

[0030] As an example, the ASC file is verified according to preset verification rules to generate a test report. The test report characterizes the performance status of the vehicle's electrical functions, such as verifying the ASC file through Uds verification rules and / or Message verification rules to generate a test report.

[0031] like Figure 2 As shown, Figure 2 For the purposes of this application Figure 1 A detailed flowchart of step S40.

[0032] Step S41: Verify the asc file according to the Uds verification rules and obtain a first verification result, wherein the first verification result includes verifying whether the UDS response data in the target log file meets expectations; Step S42: Verify the asc file according to the Message verification rules and obtain a second verification result, wherein the second verification result includes verifying the validity of the application message in the target log file; Step S43: Generate a test report based on the first verification result and the second verification result.

[0033] As an example, the UDS verification rules include time verification logic rules and message content verification logic rules. The time verification logic rules are used to verify whether the UDS response data in the .asc file is obtained within a preset time period and to obtain the first verification information. The message content verification logic rules are used to verify whether the UDS response data in the .asc file responds to the message and to obtain the second verification information. The first verification information and the second verification information are combined to generate the first verification result.

[0034] The message verification rules include parsing rules and validity verification rules. The parsing rules are used to parse the .asc file to obtain application messages. The validity verification rules are used to verify the sampled values ​​in the application messages to obtain a second verification result. The first and second verification results are combined to generate a test report, which also includes performance status information of the vehicle's various electrical functional modules.

[0035] In this embodiment, operation commands are detected in the graphical programming interface, and a preset UDS command set editor is invoked to edit ECU commands and a preset test scenario editor is invoked to edit test scenario information according to the operation commands. The test scenario information includes the vehicle's electrical function modules. Based on the ECU commands and the test scenario information, a UDS command sequence file is generated. The UDS command sequence file is sent to an edge device to obtain a target log file uploaded by the edge device, and the target log file is converted into an ASCII file. The target log file is generated by the edge device testing the vehicle based on the UDS command sequence file and monitoring the diagnostic information and application messages during the vehicle testing process in real time. The ASCII file is verified according to preset verification rules to generate a test report. The test report characterizes the performance status of the vehicle's electrical functions. This solves the technical problems in related technologies where it is impossible to monitor and obtain UDS application messages and parse application messages, thus failing to improve the accuracy of UDS diagnostic results. This embodiment realizes the acquisition and analysis of UDS diagnostic and application messages, improving the accuracy of functional test results.

[0036] Secondly, embodiments of this application also provide a testing device for vehicle electrical functions.

[0037] In one embodiment, reference is made to Figure 3 , Figure 3 This is a functional module diagram of an embodiment of the vehicle electrical function testing device of this application. Figure 3 As shown, the testing equipment for vehicle electrical functions includes: The editing module 10 is used to detect operation instructions in the graphical programming interface, and to call the preset UDS instruction set editor to edit ECU instructions and the preset test scenario editor to edit test scenario information according to the operation instructions. The test scenario information includes the vehicle's electrical function modules. The first generation module 20 is used to generate a UDS instruction sequence file based on the ECU instructions and the test scenario information; The acquisition module 30 is used to send the UDS instruction sequence file to the edge device to obtain the target log file uploaded by the edge device, and convert the target log file into an asc file. The target log file is generated by the edge device testing the vehicle based on the UDS instruction sequence file and listening to the diagnostic information and application messages during the vehicle testing process in real time. The second generation module 40 is used to verify the .asc file according to preset verification rules and generate a test report, which characterizes the performance status of the vehicle's electrical functions.

[0038] Furthermore, in one embodiment, the second generation module 40 is used for: The preset verification rules include Uds verification rules and Message verification rules; The asc file is verified according to the Uds verification rules to obtain a first verification result, wherein the first verification result includes verifying whether the UDS response data in the target log file meets expectations; The asc file is verified according to the Message verification rules to obtain a second verification result, wherein the second verification result includes verifying the validity of the application message in the target log file; A test report is generated based on the first verification result and the second verification result.

[0039] Furthermore, in one embodiment, the testing apparatus for vehicle electrical functions further includes a new module for: The Uds verification rules include time verification logic rules and message content verification logic rules; The time verification logic rules are used to verify whether the UDS response data in the .asc file was obtained within the preset time period, and the first verification information is obtained. The message content verification logic is used to verify whether the UDS response data in the .asc file responds to the message and to obtain the second verification information. Based on the first verification information and the second verification information, a first verification result is generated.

[0040] Furthermore, in one embodiment, the testing apparatus for vehicle electrical functions further includes a new module for: The message verification rules include parsing rules and validity verification rules; The .asc file is parsed using the aforementioned parsing rules to obtain application messages; The sampled values ​​in the application message are validated using validity verification rules to obtain a second verification result.

[0041] Furthermore, in one embodiment, the acquisition module 30 is used for: The UDS instruction sequence file is sent to the edge device so that the edge device can test the vehicle based on the UDS instruction sequence in the UDS instruction sequence file. The UDS instruction sequence includes the name of the ECU to be tested, the number of executions, the execution priority, and the execution duration. The diagnostic information is obtained by the diagnostic monitoring module in the edge device during the real-time monitoring of the vehicle executing the UDS command sequence. The application messages are recorded by the application message listening module in the edge device, which listens to the UDS instruction sequence executed by the vehicle.

[0042] Furthermore, in one embodiment, the editing module 10 is used for: The system invokes a preset test scenario editor, which includes a template graphics container and a preset database. The graphical programming interface allows users to select target electrical function modules from the preset database through drag-and-drop operations; The target electrical function module is configured to the CAN channel according to the drag-and-drop operation, and the test scenario information is edited, wherein there are multiple CAN channels.

[0043] Furthermore, in one embodiment, the testing apparatus for vehicle electrical functions further includes a new module for: If multiple target electrical function modules are detected in any one of the CAN channels, the multiple target electrical function modules in any one of the CAN channels are sorted so that the multiple target electrical function modules in the CAN channels are executed serially. If multiple target electrical function modules are detected in multiple CAN channels, the target electrical function modules in the multiple CAN channels will be executed in parallel logic. The test scenario information is edited by executing logic serially on multiple target electrical function modules in the CAN channel, and / or executing logic in parallel on multiple target electrical function modules in the CAN channel.

[0044] The functions of each module in the above-mentioned vehicle electrical function testing device correspond to the steps in the above-mentioned vehicle electrical function testing method embodiment, and their functions and implementation processes will not be described in detail here.

[0045] Thirdly, embodiments of this application provide a testing device for vehicle electrical functions. The testing device for vehicle electrical functions can be a personal computer (PC), a laptop computer, a server, or other devices with data processing capabilities.

[0046] Reference Figure 4 , Figure 4 This is a schematic diagram of the hardware structure of a vehicle electrical function testing device involved in an embodiment of this application. In this embodiment, the vehicle electrical function testing device may include a processor, a memory, a communication interface, and a communication bus.

[0047] The communication bus can be of any type and is used to interconnect the processor, memory, and communication interface.

[0048] Communication interfaces include input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting internal components of test equipment to implement vehicle electrical functions, as well as interfaces used for interconnecting test equipment to implement vehicle electrical functions with other devices (such as other computing devices or user equipment). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user equipment can be displays, keyboards, etc.

[0049] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0050] The processor can be a general-purpose processor, which can call the vehicle electrical function test program stored in the memory and execute the vehicle electrical function test method provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the vehicle electrical function test program is called can refer to the various embodiments of the vehicle electrical function test method of this application, which will not be repeated here.

[0051] Those skilled in the art will understand that Figure 4 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0052] Fourthly, embodiments of this application also provide a computer-readable storage medium.

[0053] The present application provides a computer-readable storage medium storing a test program for vehicle electrical functions, wherein when the test program for vehicle electrical functions is executed by a processor, it implements the steps of the vehicle electrical function test method described above.

[0054] The method implemented when the vehicle electrical function test procedure is executed can be referred to in various embodiments of the vehicle electrical function test method of this application, and will not be repeated here.

[0055] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0056] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.

[0057] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.

[0058] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0059] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.

[0060] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.

[0061] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A method for testing the electrical functions of a vehicle, characterized in that, The test methods for the vehicle's electrical functions include: Operation commands are detected in the graphical programming interface, and the preset UDS instruction set editor is called to edit ECU commands and the preset test scenario editor is called to edit test scenario information according to the operation commands. The test scenario information includes the vehicle's electrical function modules. Based on the ECU instructions and the test scenario information, a UDS instruction sequence file is generated; The UDS instruction sequence file is sent to the edge device to obtain the target log file uploaded by the edge device, and the target log file is converted into an .asc file. The target log file is generated by the edge device testing the vehicle based on the UDS instruction sequence file and monitoring the diagnostic information and application messages during the vehicle testing process in real time. The .asc file is verified according to preset verification rules, and a test report is generated, which characterizes the performance status of the vehicle's electrical functions.

2. The test method for vehicle electrical functions as described in claim 1, characterized in that, The preset verification rules include Uds verification rules and Message verification rules. The step of verifying the .asc file according to the preset verification rules and generating a test report includes: The asc file is verified according to the Uds verification rules to obtain a first verification result, wherein the first verification result includes verifying whether the UDS response data in the target log file meets expectations; The asc file is verified according to the Message verification rules to obtain a second verification result, wherein the second verification result includes verifying the validity of the application message in the target log file; A test report is generated based on the first verification result and the second verification result.

3. The test method for vehicle electrical functions as described in claim 2, characterized in that, The step of verifying the .asc file according to the Uds verification rules and obtaining a first verification result includes: The Uds verification rules include time verification logic rules and message content verification logic rules; The time verification logic rules are used to verify whether the UDS response data in the .asc file was obtained within the preset time period, and the first verification information is obtained. The message content verification logic is used to verify whether the UDS response data in the .asc file responds to the message and to obtain the second verification information. Based on the first verification information and the second verification information, a first verification result is generated.

4. The test method for vehicle electrical functions as described in claim 2, characterized in that, The step of verifying the .asc file according to the Message verification rules and obtaining a second verification result includes: The message verification rules include parsing rules and validity verification rules; The .asc file is parsed using the aforementioned parsing rules to obtain application messages; The sampled values ​​in the application message are validated using validity verification rules to obtain a second verification result.

5. The test method for vehicle electrical functions as described in claim 1, characterized in that, The step of obtaining the target log file uploaded by the edge device includes: The UDS instruction sequence file is sent to the edge device so that the edge device can test the vehicle based on the UDS instruction sequence in the UDS instruction sequence file. The UDS instruction sequence includes the name of the ECU to be tested, the number of executions, the execution priority, and the execution duration. The diagnostic information is obtained by the diagnostic monitoring module in the edge device during the real-time monitoring of the vehicle executing the UDS command sequence. The application messages are recorded by the application message listening module in the edge device, which listens to the UDS instruction sequence executed by the vehicle.

6. The test method for vehicle electrical functions as described in claim 1, characterized in that, The step of calling the preset test scenario editor to edit test scenario information includes: The system invokes a preset test scenario editor, which includes a template graphics container and a preset database. The graphical programming interface allows users to select target electrical function modules from the preset database through drag-and-drop operations; The target electrical function module is configured to the CAN channel according to the drag-and-drop operation, and the test scenario information is edited, wherein there are multiple CAN channels.

7. The test method for vehicle electrical functions as described in claim 6, characterized in that, The step of configuring the target electrical function module to the specified CAN channel according to the drag-and-drop operation and editing the test scenario information includes: If multiple target electrical function modules are detected in any one of the CAN channels, the multiple target electrical function modules in any one of the CAN channels are sorted so that the multiple target electrical function modules in the CAN channels are executed serially. If multiple target electrical function modules are detected in multiple CAN channels, the target electrical function modules in the multiple CAN channels will be executed in parallel logic. The test scenario information is edited by executing logic serially on multiple target electrical function modules in the CAN channel, and / or executing logic in parallel on multiple target electrical function modules in the CAN channel.

8. A testing device for the electrical functions of a vehicle, characterized in that, The testing device for the vehicle's electrical functions includes: The editing module is used to detect operation commands in the graphical programming interface, and to call the preset UDS instruction set editor to edit ECU commands and the preset test scenario editor to edit test scenario information according to the operation commands. The test scenario information includes the vehicle's electrical function modules. The first generation module is used to generate a UDS instruction sequence file based on the ECU instructions and the test scenario information; The acquisition module is used to send the UDS instruction sequence file to the edge device to obtain the target log file uploaded by the edge device, and convert the target log file into an asc file. The target log file is generated by the edge device testing the vehicle based on the UDS instruction sequence file and listening to the diagnostic information and application messages during the vehicle testing process in real time. The second generation module is used to verify the .asc file according to preset verification rules and generate a test report, which characterizes the performance status of the vehicle's electrical functions.

9. A testing device for the electrical functions of a vehicle, characterized in that, The vehicle electrical function testing equipment includes a processor, a memory, and a vehicle electrical function testing program stored in the memory and executable by the processor, wherein when the vehicle electrical function testing program is executed by the processor, it implements the steps of the vehicle electrical function testing method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a test program for vehicle electrical functions, wherein when the test program for vehicle electrical functions is executed by a processor, it implements the steps of the test method for vehicle electrical functions as described in any one of claims 1 to 7.

Images