Vehicle lamp control unit test method and device and electronic equipment

Abstract

The embodiment of the invention provides a method and device for testing a vehicle lamp control unit and electronic equipment, and relates to the technical field of automatic testing. The method comprises the following steps: acquiring test case data corresponding to a vehicle lamp control unit of a target vehicle; according to the test case data and a first script, the vehicle lamp control unit is driven to perform logic processing on an input signal to generate an output signal, and the input signal is generated by triggering the first script according to signal data corresponding to the test case data; the output signal is checked through a second script, a test result is obtained, and the second script is used for calibrating logic processing data of the vehicle lamp control unit. According to the method, the technical problems of low efficiency and high cost of the test method due to the fact that the test case is manually covered by a tester in the related technology are solved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of automatic testing technology, and in particular to a testing method, device, and electronic equipment for a vehicle light control unit. Background Art

[0002] With the advancement of intelligent driving technology, the functionality of vehicle lighting control units is becoming increasingly complex. Testing the complex logical processing of these control units has become a pressing challenge in the relevant technical field. In the relevant art, testers typically rely on manual testing of test cases to trigger the lighting control unit to execute them. However, this method requires significant manpower and time, resulting in low efficiency in testing lighting control units.

[0003] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0004] The embodiments of the present application provide a testing method, device, and electronic device for a vehicle light control unit, aiming to improve the technical problem in related technologies of relying on testers to manually cover test cases, resulting in low efficiency and high cost of the testing method.

[0005] According to one aspect of an embodiment of the present application, a method for testing a headlight control unit is provided, including: obtaining test case data corresponding to the headlight control unit of a target vehicle; driving the headlight control unit to perform logical processing on an input signal to generate an output signal based on the test case data and a first script, wherein the input signal is triggered by the first script according to signal data corresponding to the test case data; and using a second script to check the output signal to obtain a test result, wherein the second script is used to calibrate the logical processing data of the headlight control unit.

[0006] The above-mentioned vehicle light control unit testing method provided by the embodiment of the present application achieves the following technical effects: by obtaining test case data corresponding to the vehicle light control unit of the target vehicle; then, a first script can automatically trigger the generation of an input signal corresponding to the test case based on signal data corresponding to the test case data, drive the vehicle light control unit to perform logical processing on the input signal, and generate an output signal, thereby achieving automatic triggering of the input signal and automatic execution of the test case, thereby improving the efficiency of the vehicle light control unit testing method; further, using a second script to automatically check the output signal generated by the vehicle light control unit, thereby achieving automatic checking of the output signal, thereby automatically obtaining a test result, thereby improving the efficiency of the vehicle light control unit testing method. As a result, the embodiment of the present application achieves the purpose of efficiently and automatically testing the vehicle light control unit using the first script and the second script, achieving the technical effect of improving the efficiency of the vehicle light control unit testing method and reducing the cost of the vehicle light control unit testing method, and solving the technical problem in the related art that the vehicle light control unit testing method relies on testers to manually cover test cases, resulting in low efficiency and high cost.

[0007] Optionally, the vehicle light control unit testing method further includes: in response to generating the output signal, resetting the input signal using a reset script.

[0008] The above-mentioned optional embodiments of the present application can achieve the following technical effects: by using a reset script to reset the input signal in response to the generation of an output signal, it can ensure that after the test case is executed, the input signal that triggers the test case is reset, avoiding interference with subsequent tests and ensuring the accuracy of the test method.

[0009] Optionally, according to the test case data and the first script, driving the headlight control unit to perform logical processing on the input signal to generate an output signal includes: using the test case data to determine the first script; generating an input signal according to the signal data corresponding to the first script and the test case data; sending the input signal to the headlight control unit, driving the headlight control unit to perform logical processing on the input signal, and generating an output signal.

[0010] The above-mentioned optional embodiments of the present application can achieve the following technical effects: by utilizing the test case data to determine the first script corresponding to the test case; then, automatically generating an input signal according to the signal data corresponding to the first script and the test case data; further, sending the input signal to the headlight control unit, automatically driving the headlight control unit to perform logical processing on the input signal, and generating an output signal, thereby realizing the automatic generation of the input signal and the automatic processing of the input signal by the headlight control unit, without the need for manual triggering to execute the test case, thereby improving the efficiency of the testing method of the headlight control unit, saving the cost of the testing method of the headlight control unit, and enhancing the intelligence of the testing method of the headlight control unit.

[0011] Optionally, using the test case data, determining the first script includes: configuring the diagnostic data identifier corresponding to the headlight control unit according to the third script and the test case data to obtain a diagnostic configuration result; calibrating the actuator signal corresponding to the headlight control unit using the fourth script and the test case data to obtain a calibration result; determining a target operation script from multiple candidate operation scripts based on the diagnostic configuration result and the calibration result, wherein the target operation script is used to set the parameter value of the signal data corresponding to the test case data; and using the target operation script to update the parameter value of the first script.

[0012] The above-mentioned optional embodiment of the present application can achieve the following technical effects: the vehicle light control unit is configured using the third script and the fourth script to ensure that the vehicle light control unit corresponds to the actual test case, and then, based on the diagnostic configuration results and calibration results, a target operation script is determined from multiple candidate operation scripts, and the parameter values of the first script are updated using the target operation script to ensure the correspondence between the first script and the test case, thereby ensuring that the test can be performed according to the actual vehicle configuration, thereby improving the accuracy of the vehicle light control unit test method. In addition, by configuring the vehicle light control unit and updating the parameter values of the first script, it can be ensured that the vehicle light control unit test method of the present application can be more flexible in testing vehicles with different configurations, thereby improving the compatibility of the test method.

[0013] Optionally, the testing method for the headlight control unit also includes: obtaining electrical parameters output in real time by the central domain controller where the headlight control unit is located; in response to the electrical parameters satisfying the driving conditions, driving the headlight control unit to perform logical processing on the input signal according to the test case data and the first script to generate an output signal, wherein the driving conditions are used to determine whether the headlight control unit is in an abnormal state.

[0014] The above-described optional embodiment of the present application can achieve the following technical effects: by acquiring the electrical parameters output in real time by the central domain controller where the headlight control unit is located, the electrical parameters of the central domain controller can be monitored in real time. In response to the electrical parameters meeting the driving conditions, the headlight control unit is driven to perform logical processing on the input signal according to the test case data and the first script to generate an output signal, thereby improving the accuracy of testing the headlight control unit. Furthermore, it can avoid the problem of invalid or repeated testing of the headlight control unit due to the central domain controller outputting electrical parameters that do not meet the driving conditions, thereby improving the efficiency of the testing method.

[0015] Optionally, using the second script to check the output signal to obtain the test result includes: using the second script to extract target logic processing data from the output signal; using the second script and the expected logic processing data corresponding to the test case data to verify the target logic processing data to obtain the test result.

[0016] The above-mentioned optional embodiments of the present application can achieve the following technical effects: by utilizing the second script, the target logic processing data is extracted from the output signal, which can reduce the amount of data that needs to be verified in the subsequent inspection of the output signal, reduce the complexity of inspecting the output signal, and improve the efficiency of the testing method; further, by utilizing the expected logic processing data corresponding to the second script and the test case data, the target logic processing data can be automatically verified, and the test results can be automatically obtained, thereby realizing the automation of the inspection of the output signal, further improving the testing efficiency of the headlight control unit, and reducing the manpower and time costs of testing the headlight control unit.

[0017] Optionally, the testing method for the headlight control unit also includes: using a power control script and a communication data file to perform initial engineering configuration on the central domain controller where the headlight control unit is located to obtain an initial configuration result, wherein the power control script is used to control the hardware equipment of the target vehicle to perform power on and off operations, and the communication data file is used to define the communication node information between the central domain controller and other controllers of the target vehicle, and the other controllers represent electronic controllers in the target vehicle other than the central domain controller; in response to the initial configuration result meeting the expected configuration result, test case data is obtained.

[0018] The above-described optional embodiment of the present application can achieve the following technical effects: utilizing power control scripts and communication data files to perform initial engineering configuration on the central domain controller where the headlight control unit resides. This allows for engineering initialization of the central domain controller before testing the headlight control unit, preventing the central domain controller from retaining previous test signals that could affect the testing process of the headlight control unit, thereby improving the accuracy of the testing method. Furthermore, in response to the initial configuration result meeting the expected configuration result, test case data can be automatically loaded, eliminating the need for manual loading of test case data, thereby improving testing efficiency and reducing the labor cost of testing the headlight control unit.

[0019] Optionally, a power control script and a communication data file are used to perform an initial engineering configuration on a central domain controller including a headlight control unit, and the initial configuration result obtained includes: using the power control script to drive the programmable power supply to perform a power-on operation on the central domain controller, triggering a power-on event of the central domain controller; in response to triggering the power-on event, initializing the signal state of the central domain controller to obtain an initialization result; in response to the initialization result indicating that the signal state of the central domain controller is in an initialized state, using the communication data file to configure the communication node information of the central domain controller to obtain the initial configuration result.

[0020] The above-mentioned optional embodiments of the present application can achieve the following technical effects: by configuring the communication node information of the central domain controller using the communication data file, it can ensure that the communication node information of the central domain controller is consistent with the communication node information of the test case data, thereby ensuring that in the subsequent testing process, the first script can match the communication node information of the central domain controller, ensuring the versatility of the first script, avoiding repeated writing of the first script, and thus improving the compatibility of the test method.

[0021] According to another aspect of an embodiment of the present application, a testing device for a headlight control unit is also provided, including: an acquisition module for acquiring test case data corresponding to the headlight control unit of a target vehicle; a generation module for driving the headlight control unit to perform logical processing on an input signal and generate an output signal based on the test case data and a first script, wherein the input signal is triggered by the first script according to signal data corresponding to the test case data; and a checking module for checking the output signal using a second script to obtain a test result, wherein the second script is used to determine whether the logical processing data of the headlight control unit is correct.

[0022] The test device for the above-mentioned headlight control unit provided in the embodiment of the present application achieves the following technical effects: utilizing the acquisition module, by acquiring the test case data corresponding to the headlight control unit of the target vehicle; further, utilizing the generation module, the first script can automatically trigger the generation of an input signal corresponding to the test case according to the signal data corresponding to the test case data, drive the headlight control unit to perform logical processing on the input signal, and generate an output signal, thereby realizing automatic triggering of the input signal and automatic execution of the test case, and improving the efficiency of the test method of the headlight control unit; further, utilizing the inspection module, the second script is used to automatically inspect the output signal generated by the headlight control unit, thereby realizing automatic inspection of the output signal, thereby automatically obtaining the test result, and improving the efficiency of the test method of the headlight control unit. Therefore, the embodiment of the present application achieves the purpose of efficiently and automatically testing the headlight control unit using the first script and the second script, and realizes the technical effect of improving the efficiency of the testing method of the headlight control unit and reducing the cost of the testing method of the headlight control unit. It overcomes the defect of relying on testers to manually cover test cases in the related technology, resulting in low efficiency and high cost of the testing method of the headlight control unit, and solves the technical problem of low testing efficiency and low intelligence level of the testing device of the headlight control unit due to relying on testers to manually cover test cases.

[0023] According to another aspect of an embodiment of the present application, an electronic device is provided, including a processor and a memory, wherein the memory is used to store computer programs; and the processor is used to execute the programs stored in the memory to implement any one of the above methods.

[0024] The above-mentioned electronic device provided in the embodiment of the present application achieves the following technical effects: by obtaining test case data corresponding to the headlight control unit of the target vehicle; then, the first script automatically triggers the generation of an input signal corresponding to the test case according to the signal data corresponding to the test case data, drives the headlight control unit to perform logical processing on the input signal, and generates an output signal, thereby realizing automatic triggering of the input signal and automatic execution of the test case, and improving the testing efficiency of the electronic device; further, the second script is used to automatically check the output signal generated by the headlight control unit, thereby realizing automatic checking of the output signal, thereby automatically obtaining the test result, improving the testing efficiency of the electronic device, and enhancing the intelligence level of the electronic device. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 This is a flow chart of a method for testing a vehicle light control unit provided in one embodiment of the present application;

[0026] Figure 2 is a schematic diagram of a method for testing a vehicle light control unit provided in one embodiment of the present application;

[0027] Figure 3 This is a hardware topology diagram of a method for testing a vehicle light control unit provided in one embodiment of the present application;

[0028] Figure 4 This is a structural diagram of a testing device for a vehicle light control unit provided in one embodiment of the present application;

[0029] Figure 5 is a structural diagram of an electronic device provided in one embodiment of the present application;

[0030] Figure 6 This is a structural block diagram of a vehicle provided by an embodiment of the present application;

[0031] Figure 7 This is a hardware structure block diagram of a computing terminal provided in one embodiment of the present application. DETAILED DESCRIPTION

[0032] In order to make the technical problems, technical solutions and beneficial effects solved by this application more clearly understood, this application is further described in detail below in conjunction with the embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0033] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0034] Example 1

[0035] This application embodiment provides a method for testing a vehicle light control unit. Figure 1 , including the following steps:

[0036] S10: Acquire test case data corresponding to the headlight control unit of the target vehicle;

[0037] S20: driving the vehicle light control unit to perform logic processing on the input signal according to the test case data and the first script to generate an output signal, wherein the input signal is generated by triggering the first script according to signal data corresponding to the test case data;

[0038] S30: Using a second script to check the output signal to obtain a test result, wherein the second script is used to calibrate the logic processing data of the vehicle light control unit.

[0039] The vehicle lighting control unit may include an exterior lighting control unit (ELC) and an interior lighting control unit. The exterior lighting control unit may refer to a control unit for controlling the vehicle's exterior lighting equipment (e.g., headlights, taillights, turn signals, daytime running lights, etc.). The vehicle lighting control unit can automatically adjust the parameters of the exterior lighting equipment (e.g., brightness, color, and flashing mode) based on the vehicle's status (e.g., speed, vehicle heading, etc.), ambient light intensity, driver-input commands, and communication data with other onboard systems to improve driving safety and user experience.

[0040] The above-mentioned test case data can represent a single test case, or a test suite containing multiple test cases. In particular, each test case can correspond to a function of the headlight control unit. The test case data can be used to test whether the above-mentioned headlight control unit can correctly respond to input signals. The test case data may include but is not limited to: input signal parameters corresponding to the test case, user operation data, diagnostic data identifier parameters, actuator signal parameters, environmental data (such as light intensity, temperature, humidity, road type, etc.). The test case data can be designed according to the functional requirements of the above-mentioned headlight control unit. The test case data can also be obtained through a preset use case data set. The test case data can be written in extensible markup language.

[0041] The first script may include, but is not limited to, a signal triggering module, a state initialization module, a diagnostic configuration module, a signal calibration module, and a test step execution module. This first script can be used to trigger the input signal corresponding to the test case. This first script can be designed based on the functional requirements of the headlight control unit and the device parameters of the headlight control unit. The device parameters of the headlight control unit may include, but are not limited to, the headlight control unit's signal channel identifier, signal transmission frequency, and signal type.

[0042] The above-mentioned input signal may include but is not limited to: an input signal of a controller area network (CAN), an input signal of a local interconnect network (LIN), and an input signal of an Ethernet. The input signal can be used to characterize the trigger condition corresponding to the test case data. The input signal can be a digital signal (such as a brake signal, a door switch signal) or an analog signal (such as a light intensity signal). By calling the first script, the input signal can be automatically triggered according to the signal data corresponding to the test case data. The input signal can simulate the target vehicle in the operating scenario and various conditions corresponding to the test case data, and then automatically drive the headlight control unit to perform logical processing on the input signal to generate an output signal. There is no need to manually trigger the test case, which improves the efficiency of the test method and saves the cost of the test method.

[0043] The output signal may represent the response of the headlight control unit to the input signal. The output signal may be used to control the external lighting equipment of the target vehicle, for example, to adjust the switch state, brightness, color, and lighting mode of the external lighting equipment of the target vehicle. The second script may include, but is not limited to, a signal extraction module, a data comparison module, and a result determination module. The second script may be designed based on logic inspection requirements and data comparison standards. By utilizing multiple modules in the second script, the logic processing data of the headlight control unit can be calibrated, thereby automatically checking the output signal and generating test results, thereby improving the efficiency of the test method, eliminating the need for manual recording of test results, and reducing the cost of the test method.

[0044] The above-mentioned vehicle light control unit testing method provided by the embodiment of the present application achieves the following technical effects: by obtaining test case data corresponding to the vehicle light control unit of the target vehicle; then, a first script can automatically trigger the generation of an input signal corresponding to the test case based on signal data corresponding to the test case data, drive the vehicle light control unit to perform logical processing on the input signal, and generate an output signal, thereby achieving automatic triggering of the input signal and automatic execution of the test case, thereby improving the efficiency of the vehicle light control unit testing method; further, using a second script to automatically check the output signal generated by the vehicle light control unit, thereby achieving automatic checking of the output signal, thereby automatically obtaining a test result, thereby improving the efficiency of the vehicle light control unit testing method. As a result, the embodiment of the present application achieves the purpose of efficiently and automatically testing the vehicle light control unit using the first script and the second script, achieving the technical effect of improving the efficiency of the vehicle light control unit testing method and reducing the cost of the vehicle light control unit testing method, and solving the technical problem in the related art that the vehicle light control unit testing method relies on testers to manually cover test cases, resulting in low efficiency and high cost.

[0045] The testing method for the vehicle light control unit provided in the embodiment of the present application can efficiently and automatically test the vehicle light control unit by utilizing the first script and the second script, and can be widely used in multiple application scenarios.

[0046] For example, in the application scenario of system integration testing, during the joint development of the headlight control unit and other control units of the vehicle, since the ELC software version needs to be iteratively updated multiple times, the technical solution of the present application can automatically test the functional performance of the ELC software version after the update, and test whether the logical processing capability of the ELC can correctly control the vehicle lighting system, thereby improving the testing efficiency. In addition, the test results can also be automatically generated, which helps R&D personnel to quickly identify potential problems in the software and reduce the time cost of R&D.

[0047] For example, in the application scenario of after-sales fault diagnosis and repair, when a fault related to the headlight system occurs during the use of the vehicle, the technical solution of the present application can be used to quickly test the headlight system through an automated testing method, and automatically generate test results so that maintenance personnel can perform fault diagnosis and repair.

[0048] For example, in the application scenario of production quality control, at the end of the automobile production line, the technical solution of this application can be used to automatically test the ELC of each vehicle to be produced to quickly verify whether it meets the factory standards, especially whether the control of the headlight system is accurate. This can reduce the time cost of manual inspection, improve inspection efficiency, and ensure the quality of the vehicle.

[0049] The testing method for the vehicle light control unit provided in the embodiment of the present application can be applied to, but is not limited to, the application scenarios listed above. With the continuous evolution of technology, the above method can also be applied to a wider range of scenarios. By providing an automatic testing solution, the vehicle light control unit can be tested more efficiently and test results can be generated. It supports a variety of advanced functions and applications, which can improve the efficiency of testing.

[0050] Optionally, the above-mentioned vehicle light control unit testing method further includes the following steps:

[0051] S40: In response to generating the output signal, resetting the input signal using a reset script.

[0052] The reset script can be used to restore the triggered input signal to its initial state. This reset script may include, but is not limited to, signal reset instructions, signal recording instructions, and hardware device reset instructions. When an output signal is generated, the current test case is considered complete. By utilizing the reset script, the impact of the current test case on subsequent test cases can be eliminated, ensuring that each test case is executed under consistent starting conditions. In particular, the reset script can be integrated into the state initialization module of the first script.

[0053] In an exemplary application scenario, Figure 2 As shown, the above reset script is integrated into the state initialization module of the first script. Test case data is obtained, and the test case data may include use case data corresponding to multiple test cases (such as test case 1, test case 2, ... test case n), and then multiple test cases are executed. Specifically, before executing each test case, the signal recording instruction in the reset script is used to record the signal state of the central domain controller where the headlight control unit is located, and the initial signal data corresponding to the current test case is obtained; further, the first script is triggered to generate an input signal according to the signal data corresponding to the current test case, and the headlight control unit is driven to perform logical processing on the input signal to generate an output signal; and then, in response to the generation of the output signal, the input signal is reset using the above-recorded initial signal data corresponding to the current test case.

[0054] In another exemplary application scenario, the above-mentioned reset script may also include reset signal data. In response to generating an output signal, the reset signal data in the reset script is directly used to overwrite the signal status of the central domain controller where the headlight control unit is located to achieve the reset of the input signal.

[0055] The above-mentioned optional embodiments of the present application can achieve the following technical effects: by using a reset script to reset the input signal in response to the generation of an output signal, it can ensure that after the test case is executed, the input signal that triggers the test case is reset, avoiding interference with subsequent tests and ensuring the accuracy of the test method.

[0056] Optionally, in step S20, driving the vehicle light control unit to perform logical processing on the input signal according to the test case data and the first script to generate the output signal includes the following steps:

[0057] S201: Determine a first script using test case data;

[0058] S202: Generate an input signal according to the first script and the signal data corresponding to the test case data;

[0059] S203: Send the input signal to the headlight control unit, drive the headlight control unit to perform logic processing on the input signal, and generate an output signal.

[0060] The signal data may include, but is not limited to, a signal identifier, a signal value, a signal transmission frequency, and a signal state. This signal data may be used to guide the first script in generating an input signal corresponding to the test case. The first script may also be used to define the logic for generating and transmitting the input signal.

[0061] In an exemplary application scenario, Figure 3 As shown, the above-mentioned headlight control unit is tested on the computer side, and the test case data is used to determine the first script corresponding to the test case data; further, the first script is called, and the input signal corresponding to the test case is generated according to the input signal generation logic defined in the first script and the signal data corresponding to the test case data; then, the digital signal in the input signal is sent to the communication channel corresponding to the headlight control unit through the test development tool (for example, Controller Area Network observer, abbreviated as CANoe) by serial communication, and the hard-wired signal in the input signal is simulated by changing the output voltage state of the relay to realize the sending of the hard-wired signal in the input signal to the headlight control unit; then, the headlight control unit is driven to perform logical processing on the input signal to generate an output signal. The above-mentioned input signal generation logic can be set according to the requirements of the test case, for example, setting the corresponding relationship between the signal identifier and the communication channel type, and for another example, setting the corresponding relationship between the signal identifier and the signal type (such as digital signal, hard-wired signal).

[0062] It should be noted that in the above application scenario, the model of the above test development tool can be selected according to the configuration of the communication channel (such as CAN, LIN, Ethernet) of the headlight control unit. For example, the communication channels of the headlight control unit include CAN1, CAN2, ..., CANn, LAN1, ..., LANn, Eth1, ..., Ethn, then the communication channels of the above test development tool must also include CAN1, CAN2, ..., CANn, LAN1, ..., LANn, Eth1, ..., Ethn. In particular, when the above test development tool is CANoe, the model of CANoe can be selected as 1640A, 1670, 5640, etc. At this time, the above first script can correspond to CANoe and use the .cin file. The above hard-wired signal can refer to the hardware input signal that triggers the headlight control unit to perform an action, for example, the hardware input signal corresponding to the brake operation. The output voltage state of the above relay can include high level and low level, wherein the high level can represent an activation signal and the low level can represent an inactivated signal. The process in the above application scenario can also refer to Figure 2 Specifically, the first script is called to generate a corresponding input signal according to the input signal generation logic defined in the first script and the signal data corresponding to the test case data; further, the test case is executed (i.e., the input signal is sent to the headlight control unit, and the headlight control unit is driven to perform logical processing on the input signal) to generate an output signal.

[0063] The above-mentioned optional embodiments of the present application can achieve the following technical effects: by utilizing the test case data to determine the first script corresponding to the test case; then, automatically generating an input signal according to the signal data corresponding to the first script and the test case data; further, sending the input signal to the headlight control unit, automatically driving the headlight control unit to perform logical processing on the input signal, and generating an output signal, thereby realizing the automatic generation of the input signal and the automatic processing of the input signal by the headlight control unit, without the need for manual triggering to execute the test case, thereby improving the efficiency of the testing method of the headlight control unit, saving the cost of the testing method of the headlight control unit, and enhancing the intelligence of the testing method of the headlight control unit.

[0064] Optionally, in step S201 above, using the test case data to determine the first script includes the following steps:

[0065] S211: configuring a diagnostic data identifier corresponding to the vehicle light control unit according to the third script and the test case data to obtain a diagnostic configuration result;

[0066] S212: Calibrate the actuator signal corresponding to the headlight control unit using the fourth script and the test case data to obtain a calibration result;

[0067] S213: Determine a target operation script from a plurality of candidate operation scripts according to the diagnosis configuration result and the calibration result, wherein the target operation script is used to set parameter values of signal data corresponding to the test case data;

[0068] S214: Utilize the target operation script to update the parameter value of the first script.

[0069] The above-mentioned third script can be used to encapsulate diagnostic read and write functions. The above-mentioned diagnostic read and write functions may include a diagnostic address, a data identifier, and an operation type (e.g., a read data operation, a write data operation). By abstracting the complex diagnostic read and write operations of the headlight control unit into simple function calls, it is possible to facilitate the machine to quickly call the third script to implement read and write operations. The above-mentioned diagnostic data identifier can be used to identify data objects in the electronic control unit. Using this diagnostic data identifier, the test tool can request to read or write specific vehicle data or status information to the electronic control unit, for example, to adjust the calibration value of the electronic control unit.

[0070] The fourth script mentioned above can be used to encapsulate the calibration function. The actuator signal mentioned above may include but is not limited to: measurement data, calibration parameters, and mapping functions. The measurement data mentioned above may include but is not limited to: the measurement range, accuracy, and conversion formula of the sensor. The mapping function mentioned above can be used to represent the decision basis of the internal algorithm of the electronic control unit. The parameter values of the signal data mentioned above may include but are not limited to: interface parameters of the signal data, trigger conditions of the signal data, sequence of the signal data, signal duration, signal delay time, signal priority, and communication protocol corresponding to the signal data. The candidate operation script mentioned above can be used to define the functional functions of the headlight control unit, and can also be used to define the sending logic of the input signal.

[0071] In an exemplary application scenario, Figure 2 As shown, the configuration of the diagnostic data identifier and the calibration of the actuator signal are used as prerequisites for executing the test case. By configuring the diagnostic data identifier corresponding to the headlight control unit and calibrating the actuator signal corresponding to the headlight control unit, the headlight control unit can be read and written to set the parameters of the headlight control unit of the target vehicle, thereby adapting to the parameters of models with different configurations; then, according to the diagnostic configuration results and the calibration results, a target operation script matching the model of the target vehicle is determined from multiple candidate operation scripts, and the target operation script is used to update the parameter value of the first script to ensure that the first script can be tested according to different vehicle configurations, thereby improving the compatibility of the test method of the headlight control unit.

[0072] In particular, each candidate operation script can also correspond to a function of the headlight control unit. When the above-mentioned test case data is used to represent a certain function of the headlight control unit, the target operation script corresponding to the function can be determined from multiple candidate operation scripts based on the diagnostic configuration results and calibration results; further, the target operation script calls the first script, and passes the parameter value of the signal data corresponding to the test case data set in the target operation script to the first script to update the parameter value of the first script, ensuring that the first script can be tested according to the actual function of the vehicle, thereby improving the accuracy of the test method of the headlight control unit.

[0073] The above-mentioned optional embodiment of the present application can achieve the following technical effects: the vehicle light control unit is configured using the third script and the fourth script to ensure that the vehicle light control unit corresponds to the actual test case, and then, based on the diagnostic configuration results and calibration results, a target operation script is determined from multiple candidate operation scripts, and the parameter values of the first script are updated using the target operation script to ensure the correspondence between the first script and the test case, thereby ensuring that the test can be performed according to the actual vehicle configuration, thereby improving the accuracy of the vehicle light control unit test method. In addition, by configuring the vehicle light control unit and updating the parameter values of the first script, it can be ensured that the vehicle light control unit test method of the present application can be more flexible in testing vehicles with different configurations, thereby improving the compatibility of the test method.

[0074] Optionally, the above-mentioned vehicle light control unit testing method further includes the following steps:

[0075] S50: Acquire electrical parameters output in real time by the central domain controller where the headlight control unit is located;

[0076] S60: In response to the electrical parameters satisfying the driving conditions, the headlight control unit is driven to perform logical processing on the input signal according to the test case data and the first script to generate an output signal, wherein the driving conditions are used to determine whether the headlight control unit is in an abnormal state.

[0077] The aforementioned Central Domain Controller (CCU) can refer to the computing unit in the target vehicle used to manage and coordinate complex electronic systems. The CCU is capable of integrating and managing multiple subsystems or functional domains within the target vehicle to achieve a higher level of collaboration and data sharing. Compared to the traditional distributed electronic control unit architecture, the CCU can merge multiple electronic control units with similar functions into a single, more powerful processor, thereby reducing the number of electronic control units on the vehicle, simplifying wiring, and lowering vehicle manufacturing costs, while also improving the system's computing power and software updatability.

[0078] The above electrical parameters may include but are not limited to: the current output by the central domain controller in real time, the voltage output by the central domain controller in real time, and the power of the central domain controller. The above driving conditions may include but are not limited to: whether the voltage is stable (for example, when the voltage value output by the central domain controller in real time is within the safe voltage range, the voltage is considered stable), whether the current exceeds the limit (for example, when the current value output by the central domain controller in real time exceeds the safe current threshold of the headlight control unit, the current is considered to exceed the limit). The above abnormal conditions may include but are not limited to: abnormal voltage value transmitted to the headlight control unit, current overload of the headlight control unit, and communication failure of the headlight control unit.

[0079] In an exemplary application scenario, the real-time output voltage of the central domain controller where the headlight control unit is located is obtained. When the voltage output by the low-voltage power module of the central domain controller does not reach the minimum voltage threshold, the output of the central domain controller will affect the headlight control unit, causing the headlight control unit to be unable to perform logical processing on the input signal normally. At this time, the headlight control unit is considered to be in an abnormal state, and it is considered that the voltage value output by the central domain controller does not meet the driving conditions; accordingly, when the voltage output by the low-voltage power module of the central domain controller reaches the minimum voltage threshold, it is considered that the electrical parameters meet the driving conditions. In response to the electrical parameters meeting the driving conditions, according to the test case data and the first script, the headlight control unit is driven to perform logical processing on the input signal to generate an output signal.

[0080] In another exemplary application scenario, the headlight control unit has a timed wake-up / shutdown function (e.g., after triggering the vehicle lock signal, the vehicle lighting system is timed to shut down). In response to the triggering of the timed wake-up signal, the real-time output current of the central domain controller where the headlight control unit is located is obtained, and the rise time for the real-time output current value to reach the wake-up current threshold is recorded. If the rise time does not exceed the wake-up time threshold, it is considered that the electrical parameters meet the driving conditions. In response to the electrical parameters meeting the driving conditions, according to the test case data and the first script, the headlight control unit is driven to perform logical processing on the input signal to generate an output signal.

[0081] The above-described optional embodiment of the present application can achieve the following technical effects: by acquiring the electrical parameters output in real time by the central domain controller where the headlight control unit is located, the electrical parameters of the central domain controller can be monitored in real time. In response to the electrical parameters meeting the driving conditions, the headlight control unit is driven to perform logical processing on the input signal according to the test case data and the first script to generate an output signal, thereby improving the accuracy of testing the headlight control unit. Furthermore, it can avoid the problem of invalid or repeated testing of the headlight control unit due to the central domain controller outputting electrical parameters that do not meet the driving conditions, thereby improving the efficiency of the testing method.

[0082] Optionally, in the above step S30, using the second script to check the output signal to obtain the test result includes the following steps:

[0083] S301: Extracting target logic processing data from the output signal using the second script;

[0084] S302: Using the second script and the expected logic processing data corresponding to the test case data, the target logic processing data is verified to obtain a test result.

[0085] The above-mentioned target logic processing data may include but is not limited to: signal identifier, signal length, and signal value. The above-mentioned expected logic processing data can be used to characterize the expected behavior data and output data of the headlight control unit for the test case data. The expected logic processing data can be set according to the functions of the headlight control unit. The expected logic processing data can be used to provide a clear judgment standard for verifying the test case data. For example, the above-mentioned test case data is used to characterize that the target vehicle is in a rainy environment, and the above-mentioned expected logic processing data can be used to reflect the process and results of the response output by the expected headlight control unit in the rainy environment. In some application scenarios, the above-mentioned expected logic processing data can also be defined in the second script. The above-mentioned test results may include but are not limited to: the functional status corresponding to the test case data (such as abnormal function, normal function, etc.), and the difference information between the target logic processing data and the expected logic processing data.

[0086] In an exemplary application scenario, Figure 2 As shown, the second script is called to extract the target logic processing data to be checked from the output signal; then, the second script is used to check whether the actual output data of the headlight control unit (i.e., the target logic processing data) is consistent with the expected output data (i.e., the expected logic processing data) corresponding to the test case data. If the target logic processing data is consistent with the expected logic processing data, it is considered that the functional state corresponding to the test case data is in a normal functional state, the test case passes, and a test result is generated; if the target logic processing data is inconsistent with the expected logic processing data, it is considered that the functional state corresponding to the test case data is in an abnormal functional state, the test case fails, and a test result is generated. The test result may include difference information between the target logic processing data and the expected logic processing data, which is convenient for testers to analyze the test results.

[0087] Still in the aforementioned application scenario, the specific process of calling the second script to extract the target logical processing data to be checked from the output signal can be as follows. The lighting control unit typically performs multiple steps of logical processing on the input signal, with the corresponding logical processing data being obtained after each step. The logic processing data corresponding to each step can be recorded in the final processing result (i.e., the output signal) of the lighting control unit. The second script can be used to extract the logic processing data corresponding to some steps from the output signal as the target logical processing data, thereby reducing the complexity of subsequent output signal verification and improving test efficiency.

[0088] Still in the above application scenario, the specific process of calling the second script to extract the target logic processing data to be checked from the output signal can also be as follows. The output signal generated by the headlight control unit includes multiple types of data. The second script is used to filter the multiple types of data contained in the output signal, and only some types of data are extracted as target logic processing data to ensure that the target logic processing data can correctly reflect the output signal, so as to reduce the amount of data that needs to be verified, thereby reducing the complexity of verifying the output signal and improving test efficiency. In particular, all data contained in the output signal can also be used as target logic processing data, that is, the expected logic processing data corresponding to the second script and the test case data can be directly used to check the output signal to obtain the test results. It should also be noted that when there are multiple test cases, the output signal of each test case can be integrated to obtain the test results.

[0089] Still in the above application scenario, after obtaining the test results, the report generation script can be used to process the test results, generate a test report, and send the test report to the graphical user interface for display. Specifically, Figure 3 As shown, CANoe receives the output signal transmitted by CCU, uses the second script to extract the target logic processing data from the output signal, further uses the second script and the expected logic processing data corresponding to the test case data to verify the target logic processing data to obtain the test results, and then calls the report generation script to process the test results, generate a test report, and send the test report back to the computer.

[0090] The above-mentioned optional embodiments of the present application can achieve the following technical effects: by utilizing the second script, the target logic processing data is extracted from the output signal, which can reduce the amount of data that needs to be verified in the subsequent inspection of the output signal, reduce the complexity of inspecting the output signal, and improve the efficiency of the testing method; further, by utilizing the expected logic processing data corresponding to the second script and the test case data, the target logic processing data can be automatically verified, and the test results can be automatically obtained, thereby realizing the automation of the inspection of the output signal, further improving the testing efficiency of the headlight control unit, and reducing the manpower and time costs of testing the headlight control unit.

[0091] Optionally, the above-mentioned vehicle light control unit testing method further includes the following steps:

[0092] S70: Performing an initial engineering configuration on the central domain controller where the headlight control unit is located using the power control script and the communication data file to obtain an initial configuration result. The power control script is used to control the hardware devices of the target vehicle to perform power on and off operations, and the communication data file is used to define communication node information between the central domain controller and other controllers of the target vehicle. The other controllers represent electronic controllers in the target vehicle other than the central domain controller.

[0093] S80: In response to the initial configuration result meeting the expected configuration result, acquiring test case data.

[0094] The above-mentioned power control script may include but is not limited to: execution sequence instructions, conditional judgment execution, and status monitoring instructions. The power control script can be used to ensure that the dependent hardware corresponding to the headlight control unit is correctly powered on before the central domain controller where the headlight control unit is located is tested, and to ensure that it is safely powered off after the test to prevent power waste or equipment damage. The power control script can be written in accordance with the script language corresponding to the test tool (such as Capl script) based on hardware characteristics and test requirements. The above-mentioned hardware equipment may include but is not limited to: central domain controllers, relays, and electronic controllers other than the central domain controller in the target vehicle. The above-mentioned power on and off operations may include power on operations and power off operations.

[0095] The communication data file may be a standard format file for describing communications. The communication data file may include communication node information between the central domain controller and other controllers of the target vehicle, including but not limited to: message format, data type, transmission cycle, and signal definition.

[0096] The above-mentioned initial configuration result can be used to reflect the working status of the central domain controller where the headlight control unit is located (such as power status, signal status, communication node status, etc.). The above-mentioned expected configuration result can be used to indicate that the preset initial standard for testing the headlight control unit is met. The expected configuration result may include initial power data, initial communication node information, and initial signal data. The expected configuration result can be set according to the initial startup state and test requirements of the target vehicle. By comparing the initial configuration result and the expected configuration result, it can be ensured that the central domain controller where the headlight control unit is located is in a stable working condition before performing the test, thereby improving the accuracy of the test results.

[0097] In an exemplary application scenario, Figure 2 As shown, before acquiring test case data, the central domain controller housing the headlight control unit can be initially configured. This initial configuration process can include powering on the central domain controller, initializing its signal states, and configuring communication node information between the central domain controller and other controllers in the target vehicle. Upon completion of the initial configuration of the central domain controller housing the headlight control unit, an initial configuration result is generated. This initial configuration result is then compared with an expected configuration result to determine whether it meets the expected configuration result. If so, the initial configuration process for the central domain controller housing the headlight control unit is deemed successful, and test case data can be acquired.

[0098] The above-described optional embodiment of the present application can achieve the following technical effects: utilizing power control scripts and communication data files to perform initial engineering configuration on the central domain controller where the headlight control unit resides. This allows for engineering initialization of the central domain controller before testing the headlight control unit, preventing the central domain controller from retaining previous test signals that could affect the testing process of the headlight control unit, thereby improving the accuracy of the testing method. Furthermore, in response to the initial configuration result meeting the expected configuration result, test case data can be automatically loaded, eliminating the need for manual loading of test case data, thereby improving testing efficiency and reducing the labor cost of testing the headlight control unit.

[0099] Optionally, in step S70, performing an initial engineering configuration on the central domain controller including the headlight control unit using the power control script and the communication data file, and obtaining the initial configuration result includes the following steps:

[0100] S701: Using the power control script, drive the programmable power supply to perform a power-on operation on the central domain controller, thereby triggering a power-on event of the central domain controller;

[0101] S702: In response to triggering a power-on event, initializing a signal state of the central domain controller to obtain an initialization result;

[0102] S703: In response to the initialization result indicating that the signal state of the central domain controller is in the initialization state, the communication node information of the central domain controller is configured using the communication data file to obtain an initial configuration result.

[0103] The programmable power supply can be used to power the target vehicle's hardware devices. It can be connected to a control device via serial communication to remotely control the power supply to power on and off the hardware devices. The programmable power supply can be selected based on test requirements; for example, the IT6332A model can be used. The signal states described above may include, but are not limited to, initialization, fault, and operating states.

[0104] The communication data file (e.g., Database for CAN, DBC) is loaded into the central domain controller. This communication data file can be used to simulate sending node signals to the central domain controller, thereby configuring the central domain controller's communication node information, enabling the central domain controller to identify and understand the signal structure and communication protocol of nodes in the vehicle network. The simulated node signals sent may include, but are not limited to, wake-up node signals (e.g., sending an NM message to trigger the network management process to check whether nodes in the network are ready for communication) and application message signals.

[0105] In an exemplary application scenario, Figure 3 As shown, the hardware devices used in the test (e.g., programmable power supply, relays) and test tools (e.g., CANoe) are initialized. Furthermore, the computer calls the programmable power supply serial communication interface function library (e.g., PowerCtrl.cin) via serial communication. Using the power control script, the programmable power supply powers on the central domain controller, triggering a power-on event for the central domain controller. Furthermore, the power control script can also be used to drive the programmable power supply to power on the relay, enabling the relay to output a high / low level signal to trigger a hardwired signal in the CCU.

[0106] Still in the aforementioned application scenario, in response to a power-on event, the signal state of the central domain controller is initialized, and the signal state of the central domain controller is checked to determine whether the signal state of the central domain controller is in the initialized state, with the determination result being used as the initialization result. Furthermore, in response to the initialization result indicating that the signal state of the central domain controller is in the initialized state, the communication node information of the central domain controller is configured using the communication data file to obtain an initial configuration result. By configuring the communication node information of the central domain controller, the central domain controller can identify and understand the signal structure of nodes in the vehicle network, thereby facilitating the smooth execution of subsequent testing processes.

[0107] The above-mentioned optional embodiments of the present application can achieve the following technical effects: by configuring the communication node information of the central domain controller using the communication data file, it can ensure that the communication node information of the central domain controller is consistent with the communication node information of the test case data, thereby ensuring that in the subsequent testing process, the first script can match the communication node information of the central domain controller, ensuring the versatility of the first script, avoiding repeated writing of the first script, and thus improving the compatibility of the test method.

[0108] Example 2

[0109] The present application also provides a test device 400 for a vehicle light control unit. Figure 4 , including: an acquisition module 401, used to obtain test case data corresponding to the headlight control unit of the target vehicle; a generation module 402, used to drive the headlight control unit to perform logical processing on the input signal according to the test case data and a first script, and generate an output signal, wherein the input signal is triggered by the first script according to the signal data corresponding to the test case data; a checking module 403, used to use a second script to check the output signal to obtain a test result, wherein the second script is used to determine whether the logical processing data of the headlight control unit is correct.

[0110] The test device for the above-mentioned headlight control unit provided in the embodiment of the present application achieves the following technical effects: utilizing the acquisition module 401, by acquiring the test case data corresponding to the headlight control unit of the target vehicle; further, utilizing the generation module 402, the first script automatically triggers the generation of an input signal corresponding to the test case according to the signal data corresponding to the test case data, drives the headlight control unit to perform logical processing on the input signal, and generates an output signal, thereby realizing automatic triggering of the input signal and automatic execution of the test case, and improving the efficiency of the test method of the headlight control unit; further, utilizing the inspection module 403, the second script is used to automatically inspect the output signal generated by the headlight control unit, thereby realizing automatic inspection of the output signal, thereby automatically obtaining the test result, and improving the efficiency of the test method of the headlight control unit. Therefore, the embodiment of the present application achieves the purpose of efficiently and automatically testing the headlight control unit using the first script and the second script, and realizes the technical effect of improving the efficiency of the testing method of the headlight control unit and reducing the cost of the testing method of the headlight control unit. It overcomes the defect of relying on testers to manually cover test cases in the related technology, resulting in low efficiency and high cost of the testing method of the headlight control unit, and solves the technical problem of low testing efficiency and low intelligence level of the testing device of the headlight control unit due to relying on testers to manually cover test cases.

[0111] It should be noted that the optional implementation methods of this embodiment can refer to the relevant description in Example 1 and will not be repeated here.

[0112] Example 3

[0113] The present application also provides an electronic device 500. Figure 5 , including a memory 510 and a processor 520, wherein the memory 510 is used to store computer programs; the processor 520 is used to execute the programs stored in the memory 510 to implement the testing method of the vehicle light control unit introduced in any embodiment of the present application.

[0114] The above-mentioned electronic device provided in the embodiment of the present application achieves the following technical effects: by obtaining test case data corresponding to the headlight control unit of the target vehicle; then, the first script automatically triggers the generation of an input signal corresponding to the test case according to the signal data corresponding to the test case data, drives the headlight control unit to perform logical processing on the input signal, and generates an output signal, thereby realizing automatic triggering of the input signal and automatic execution of the test case, and improving the testing efficiency of the electronic device; further, the second script is used to automatically check the output signal generated by the headlight control unit, thereby realizing automatic checking of the output signal, thereby automatically obtaining the test result, improving the testing efficiency of the electronic device, and enhancing the intelligence level of the electronic device.

[0115] It can be understood by those skilled in the art that Figure 5 The structure shown is for illustration only, and the electronic device may also be a terminal device such as a smart phone (eg, an Android phone, an iOS phone, etc.), a tablet computer, a PDA, or a mobile Internet device (MID). Figure 5 The structure of the electronic device is not limited. For example, the electronic device 500 may further include Figure 5 More or fewer components (e.g., network interface, display device, etc.) shown in, or with Figure 5 Different configurations shown.

[0116] Example 4

[0117] The present application also provides a vehicle 600, please refer to Figure 6 , including an on-board memory 610 and an on-board processor 620, wherein the on-board memory 610 is used to store computer programs; the on-board processor 620 is used to execute the computer programs stored in the memory to implement the test method of the vehicle light control unit of any embodiment.

[0118] The vehicle provided by the embodiment of the present application achieves the following technical effects: by obtaining the test case data corresponding to the headlight control unit of the target vehicle; then, the first script automatically triggers the generation of an input signal corresponding to the test case based on the signal data corresponding to the test case data, drives the headlight control unit to perform logical processing on the input signal, and generates an output signal, thereby achieving automatic triggering of the input signal and automatic execution of the test case, thereby improving the testing efficiency of the electronic device; further, the second script is used to automatically check the output signal generated by the headlight control unit, thereby achieving automatic checking of the output signal and automatically obtaining the test result. Therefore, in the event that the vehicle's headlight control unit fails, the above-mentioned headlight control unit testing method can be used to automatically detect the fault of the vehicle's headlight control unit, thereby enhancing the vehicle's intelligence level and improving the user experience.

[0119] Those skilled in the art will appreciate that, similarly, the above-mentioned vehicle may also be a computing terminal. Figure 7 This is a hardware structure diagram of a computing terminal for implementing the xxx method according to an embodiment of the present application. Figure 7As shown, a computing terminal 700 (e.g., a computer terminal, a mobile smart terminal, a vehicle terminal, or a cloud computing virtual terminal, etc.) may include: one or more processors 702 (e.g., may include processors 702a, 702b, ..., 702n), a memory 704 for storing data, and a transmission device 706 for implementing a communication function, wherein the processor 702 may include but is not limited to processing components such as a microprocessor (Microcontroller Unit, abbreviated as MCU) or a programmable logic device (Field Programmable Gate Array, abbreviated as FPGA).

[0120] The computing terminal 700 may also include a display, an input / output interface, a Universal Serial Bus (USB) port (the USB port may be used as one of the ports of a computer bus, not shown in the figure), a network interface (not shown in the figure), a power supply (not shown in the figure), and a camera (not shown in the figure).

[0121] It should be noted that the one or more processors 702 and / or other data processing circuits in the computing terminal 700 may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computing terminal 700 (or mobile device).

[0122] The memory 704 can be used to store software programs and modules of application software, such as program instructions and data storage devices corresponding to the path planning method in the embodiment of the present application. The processor 702 executes various functional applications and data processing by running the software programs and modules stored in the memory 704, that is, implementing the above-mentioned path planning method. The memory 704 may include a high-speed random access memory and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 704 may further include a memory remotely located relative to the processor 702, and these remote memories may be connected to the vehicle terminal 70 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0123] The transmission device 706 is used to receive or send data via a network. Specific examples of the aforementioned network may include a wireless network provided by the communication provider of the vehicle terminal 70. In one example, the transmission device 706 includes a network adapter (Network Interface Controller, abbreviated as NIC) and a network interface. The network adapter can be connected to other network devices through a base station so as to communicate with the Internet. The transmission device 706 can communicate data using a wired and / or wireless network connection. In one example, the transmission device 706 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0124] The input / output interface can be connected to the corresponding input / output devices of the computing terminal 700 to implement input / output functions. The input / output devices may include, but are not limited to, cursor control devices, keyboards, displays, etc. The above-mentioned input / output devices may be built into the computing terminal 700 or external devices.

[0125] It can be understood by those skilled in the art that Figure 7 The structure of the computing terminal 700 shown is only for illustration and does not impose a strict limitation on the structure of the computing terminal 700. For example, the computing terminal 700 may also include Figure 7 More or fewer components than those shown in FIG, or computing terminal 700 may have the same Figure 7 Different categories of components are shown.

[0126] Example 5

[0127] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the method for testing the vehicle light control unit described in any embodiment of the present application is implemented.

[0128] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store computer programs.

[0129] The above-mentioned computer-readable storage medium provided in the embodiment of the present application achieves the following technical effects: by obtaining test case data corresponding to the headlight control unit of the target vehicle; then, the first script automatically triggers the generation of an input signal corresponding to the test case according to the signal data corresponding to the test case data, drives the headlight control unit to perform logical processing on the input signal, and generates an output signal, thereby realizing automatic triggering of the input signal and automatic execution of the test case, and improving the testing efficiency of the electronic device; further, the second script is used to automatically check the output signal generated by the headlight control unit, thereby realizing automatic inspection of the output signal, thereby automatically obtaining the test result, and improving the efficiency of the testing method of the headlight control unit.

[0130] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0131] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0132] In this application, a plurality refers to two or more.

[0133] In this application, unless otherwise expressly defined, the terms "mounted," "connected," and "connected" should be interpreted broadly. For example, they can refer to fixed, detachable, or integral connections; mechanical or electrical connections; direct or indirect connections through an intermediary; and internal communication between two components. A person of ordinary skill in the art will understand the specific meanings of these terms in this application.

[0134] In this application, the terms "first," "second," "third," "fourth," etc. (if any) are used to distinguish similar objects and are not necessarily used to describe a particular sequential order.

[0135] The term "and / or" in this application simply describes an association between related objects, indicating that three possible relationships exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this application generally indicates that the related objects are in an "or" relationship.

[0136] Unless otherwise specified, all steps of the present application may be performed sequentially or randomly. For example, a statement that the method includes steps A and B indicates that the method may include steps A and B performed sequentially, or steps B and A performed sequentially. For example, a statement that the method may also include step C indicates that step C may be added to the method in any order, for example, the method may include steps A, B, and C, or steps A, C, and B, or steps C, A, and B, etc.

[0137] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present application should be included in the scope of protection of the present application.

Claims

1. A method for testing a vehicle light control unit, characterized in that: include: Obtain test case data corresponding to the headlight control unit of the target vehicle; According to the test case data and the first script, drive the vehicle light control unit to perform logical processing on the input signal to generate an output signal, wherein the input signal is triggered by the first script according to the signal data corresponding to the test case data; The output signal is checked using a second script to obtain a test result, wherein the second script is used to calibrate logical processing data of the vehicle light control unit.

2. The vehicle light control unit testing method according to claim 1, characterized in that: The testing method of the vehicle light control unit further includes: In response to generating the output signal, the input signal is reset using a reset script.

3. The method for testing a vehicle light control unit according to claim 1, wherein: Driving the vehicle light control unit to perform logic processing on the input signal to generate the output signal according to the test case data and the first script includes: Determine the first script using the test case data; generating the input signal according to the first script and the signal data corresponding to the test case data; The input signal is sent to the vehicle light control unit, and the vehicle light control unit is driven to perform logic processing on the input signal to generate the output signal.

4. The method for testing a vehicle light control unit according to claim 3, characterized in that: Using the test case data, determining that the first script includes: configuring a diagnostic data identifier corresponding to the vehicle light control unit according to the third script and the test case data to obtain a diagnostic configuration result; Calibrate the actuator signal corresponding to the headlight control unit using the fourth script and the test case data to obtain a calibration result; Determining a target operation script from a plurality of candidate operation scripts according to the diagnostic configuration result and the calibration result, wherein the target operation script is used to set parameter values of the signal data corresponding to the test case data; The target operation script is used to update the parameter value of the first script.

5. The vehicle light control unit testing method according to claim 1, characterized in that: The testing method of the vehicle light control unit further includes: Obtaining electrical parameters output in real time by a central domain controller where the headlight control unit is located; In response to the electrical parameters satisfying the driving conditions, the headlight control unit is driven to perform logical processing on the input signal according to the test case data and the first script to generate the output signal, wherein the driving conditions are used to determine whether the headlight control unit is in an abnormal state.

6. The vehicle light control unit testing method according to claim 1, characterized in that: Checking the output signal using the second script to obtain the test result includes: extracting target logic processing data from the output signal using the second script; The target logic processing data is verified using the second script and the expected logic processing data corresponding to the test case data to obtain the test result.

7. The vehicle light control unit testing method according to any one of claims 1 to 6, characterized in that: The testing method of the vehicle light control unit further includes: Performing an initial engineering configuration on the central domain controller where the headlight control unit is located using a power control script and a communication data file to obtain an initial configuration result, wherein the power control script is used to control the hardware devices of the target vehicle to perform power on and off operations, and the communication data file is used to define communication node information between the central domain controller and other controllers of the target vehicle, where the other controllers represent electronic controllers in the target vehicle other than the central domain controller; In response to the initial configuration result meeting the expected configuration result, the test case data is acquired.

8. The vehicle light control unit testing method according to claim 7, characterized in that: Using the power control script and the communication data file, an initial engineering configuration is performed on a central domain controller including the vehicle light control unit, and the initial configuration result includes: Using the power control script, driving the programmable power supply to perform a power-on operation on the central domain controller, thereby triggering a power-on event of the central domain controller; In response to triggering the power-on event, initializing the signal state of the central domain controller to obtain an initialization result; In response to the initialization result indicating that the signal state of the central domain controller is in the initialization state, the communication node information of the central domain controller is configured using the communication data file to obtain the initial configuration result.

9. A testing device for a vehicle light control unit, characterized in that: include: An acquisition module, used to obtain test case data corresponding to the headlight control unit of the target vehicle; a generation module, configured to drive the vehicle light control unit to perform logic processing on an input signal and generate an output signal based on the test case data and a first script, wherein the input signal is generated by triggering the first script based on signal data corresponding to the test case data; The checking module is used to check the output signal using a second script to obtain a test result, wherein the second script is used to determine whether the logical processing data of the headlight control unit is correct.

10. An electronic device, characterized in that: comprising a processor and a memory, wherein Memory for storing computer programs; A processor, configured to execute a program stored in a memory to implement the method described in any one of claims 1 to 8.

Images