Inverter flow request test method, device, equipment, medium and product
By constructing test cases to simulate sensor delay and filtering delay, the problems of low test coverage and efficiency in inverter flow control are solved, and efficient flow request testing is achieved.
Patent Information
- Application Number
- CN202511208545.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-27
- Publication Date
- 2025-11-14
AI Technical Summary
Existing technologies fail to fully consider parameter acquisition delays and system failures in inverter flow control, resulting in low test coverage and efficiency.
By acquiring the current operating condition signal of the motor under various load conditions, the cooling medium flow request signal, and the fault signal, test cases are constructed to simulate the signal delay and filtering delay of the sensors. A scheduling queue is used to process multiple request triggering modes to generate flow request test results.
It improves test coverage and accuracy, reduces the need for manual load testing, and enhances testing efficiency and system reliability.
Smart Images
Figure CN120948937A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of vehicle electronic control testing technology, specifically to inverter flow request testing methods, devices, equipment, media, and products. Background Technology
[0002] As new energy vehicle power systems develop towards higher power density and higher efficiency, the thermal management of motors and inverters is becoming increasingly prominent. During high-power output or prolonged full-load operation of the motor, heat generated by the inverter's internal semiconductor devices and motor windings rapidly accumulates. If heat dissipation is not timely or the strategy is inappropriate, it can not only lead to device performance degradation and shortened lifespan, but also potentially trigger safety risks such as thermal runaway and protection tripping. Therefore, inverter flow control is a crucial element in ensuring system reliability and economy.
[0003] Currently, thermal management strategies often determine the cooling medium flow rate through multidimensional condition mapping tables (MAPs). However, MAPs are numerous and have complex node distributions. In addition, some parameter acquisition links, such as thermistors, have signal delays and filtering issues. Furthermore, faults that occur during flow requests must also be taken into account. It is difficult to fully cover all combinations of operating conditions by relying solely on manual calibration and manual testing. Summary of the Invention
[0004] In view of this, the present invention provides a method, apparatus, device, medium and product for testing inverter flow request, in order to solve the problems that the prior art does not fully consider the delay of parameter acquisition and system failure, and has low test coverage and test efficiency.
[0005] In a first aspect, the present invention provides an inverter traffic request testing method, the method comprising:
[0006] Acquire multiple test cases for the motor under each load condition, as well as the sensor delay time; each test case includes the current operating condition signal, cooling medium flow request signal, and fault signal collected by the sensor;
[0007] For each load condition, the original load condition signal is sent to the inverter under test and timing is performed. When the timing time reaches the delay time, multiple test cases corresponding to the load condition are sent to the inverter under test and the test data of the inverter under test is obtained.
[0008] Based on the test data, generate traffic request test results.
[0009] This application acquires current operating condition signals, cooling medium flow request signals, and fault signals corresponding to various load conditions of the motor, thereby comprehensively covering various load and fault conditions and improving test coverage. During testing, the raw operating condition signal is first sent to the inverter under test and timing is started. When the timing reaches the sensor's delay time, the corresponding current operating condition signal, cooling medium flow request signal, and fault signal are then sent to the inverter under test. This simulates the sensor's signal delay and filtering delay, and the test data of the inverter under test is collected to obtain the flow request test results, further improving the coverage and accuracy of the test scenarios. Furthermore, it eliminates the need for manually creating various load conditions, improving test efficiency.
[0010] In one optional implementation, the test cases further include a request triggering mode and a triggering priority; multiple test cases corresponding to the load conditions are sent to the inverter under test, and test data of the inverter under test is obtained, including:
[0011] A scheduling queue is constructed based on the trigger priority corresponding to each test case;
[0012] For each test case in the scheduling queue, the current operating condition signal and fault signal of the test case are sent to the inverter under test in sequence. Based on the request triggering mode, current operating condition signal and fault signal corresponding to the test case, the cooling medium flow request signal of the test case is sent to the inverter under test to obtain the test data of the inverter under test.
[0013] This application constructs a scheduling queue according to the trigger priority field in the test cases, and sends test cases to the inverter under test based on the scheduling queue. In this way, when multiple test cases with different request trigger modes arrive at the same time, it ensures that high-priority events are sent first, and low-priority events can be queued or discarded, so as to verify the response performance of the inverter traffic request strategy under various request trigger modes.
[0014] In one optional implementation, the request triggering mode includes a periodic triggering mode and a conditional triggering mode; based on the request triggering mode corresponding to the test case, the current operating condition signal, and the fault signal, a cooling medium flow request signal from the test case is sent to the inverter under test to obtain the test data of the inverter under test, including:
[0015] When the request triggering mode corresponding to the test case is detected to be the periodic triggering mode, a cooling medium flow request signal is sent to the inverter under test based on the preset period, and the actual sending time of the cooling medium flow request signal is recorded.
[0016] When it is detected that the request triggering mode corresponding to the test case is the condition triggering mode, and the current operating condition signal or fault signal corresponding to the test case exceeds the signal threshold, a cooling medium flow request signal is sent to the inverter under test, and the sending delay of the cooling medium flow request signal is recorded.
[0017] Test data of the inverter under test are obtained based on the actual transmission time and / or transmission delay.
[0018] This application sends a cooling medium flow request signal to the inverter under test according to a preset cycle and records the actual sending time of the cooling medium flow request signal; and / or, when a sudden change is detected in the current operating condition signal or fault signal, a cooling medium flow request signal is sent to the inverter under test and the sending delay of the cooling medium flow request signal is recorded, so as to verify the correctness and response performance of the flow request strategy in both time-driven and event-driven dimensions.
[0019] In an alternative implementation, after sending a cooling medium flow request signal to the inverter under test, the method further includes:
[0020] It continuously receives response signals from the inverter under test in response to the cooling medium flow request signal;
[0021] Based on the response signal, the test data of the inverter under test is obtained.
[0022] This application continuously receives response signals from the inverter under test in response to the cooling medium flow request signal, in order to determine whether the inverter under test can correctly respond to the cooling medium flow request signal sent by the test equipment, thereby verifying the correctness and response performance of the flow request strategy.
[0023] In an alternative implementation, the test case further includes a number of retries; the method also includes:
[0024] If the response signal is detected as an incorrect response signal, or if no response signal is received within the preset timeout window, the cooling medium flow request signal is resent to the inverter under test.
[0025] When the number of retransmissions of the cooling medium flow request signal reaches the retry count, the inverter under test is controlled to perform flow control based on the preset cooling medium flow rate.
[0026] This application verifies the correctness of the response signal and the response time. If the response signal is detected as an incorrect response signal or no response signal is received within the preset timeout window, the cooling medium flow request signal is resent to the inverter under test until the number of retries is reached. This enables the inverter under test to perform flow control based on the backup flow strategy, so as to verify the performance of the controller under test in the timeout retry scenario.
[0027] In one optional implementation, based on the test data, traffic request test results are generated, including:
[0028] The response test results are obtained based on the response signals in the test data;
[0029] And / or, based on the actual transmission time in the test data, obtain the interval time between two adjacent frames of cooling medium flow request signals, and based on the jitter time of the interval time compared with the preset period, obtain the periodic trigger test result;
[0030] And / or, based on the relationship between the transmission delay and the delay threshold of the cooling medium flow request signal in each frame of the test data, the condition-triggered test results are obtained;
[0031] The traffic request test results are obtained based on the response test results and / or the periodic trigger test results and / or the conditional trigger test results.
[0032] This application analyzes the actual transmission time and transmission delay of the cooling medium flow request signal and the response signal fed back by the inverter under test under various load conditions. It verifies the correctness and reliability of the response signal, the timing jitter of the periodic trigger frame and the delay of the conditional trigger frame, comprehensively covering various test scenarios and improving test coverage and efficiency.
[0033] In an alternative implementation, before continuously receiving a response signal from the inverter under test in response to a cooling medium flow request signal, the method further includes:
[0034] Based on the current operating condition signals in the test cases, construct abnormal frame signals;
[0035] Send an abnormal frame signal to the inverter under test.
[0036] This application constructs an abnormal frame signal based on the current operating condition signal, and injects the abnormal frame signal into the inverter under test to verify the inverter under test's ability to ignore abnormal frames, confirm that the inverter under test does not deadlock or restart, and can immediately resume the correct response to legitimate requests after the abnormality ends, thereby verifying the robustness of the traffic request strategy.
[0037] Secondly, the present invention provides an inverter flow request testing device, the device comprising:
[0038] The acquisition module is used to acquire multiple test cases corresponding to the motor under each load condition and the delay time of the sensor; wherein, each test case includes the current operating condition signal collected by the sensor, the cooling medium flow request signal and the fault signal;
[0039] The first processing module is used to send the original operating condition signal to the inverter under test for each load condition and to perform timing. When the timing time reaches the delay time, it sends multiple test cases corresponding to the load condition to the inverter under test and obtains the test data of the inverter under test.
[0040] The second processing module is used to generate traffic request test results based on the test data.
[0041] Thirdly, the present invention provides a testing device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the computer instructions to perform the inverter flow request testing method of the first aspect or any corresponding embodiment described above.
[0042] Fourthly, the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to execute the inverter flow request test method of the first aspect or any corresponding embodiment thereof.
[0043] Fifthly, the present invention provides a computer program product, including computer instructions for causing a computer to execute the inverter flow request test method of the first aspect or any corresponding embodiment thereof.
[0044] The beneficial effects of this application are as follows:
[0045] This application acquires current operating condition signals, cooling medium flow request signals, and fault signals corresponding to various load conditions of the motor, thereby comprehensively covering various load and fault conditions and improving test coverage. During testing, the raw operating condition signal is first sent to the inverter under test and timing is started. When the timing reaches the sensor's delay time, the corresponding current operating condition signal, cooling medium flow request signal, and fault signal are then sent to the inverter under test. This simulates the sensor's signal delay and filtering delay, and the test data of the inverter under test is collected to obtain the flow request test results, further improving the coverage and accuracy of the test scenarios. Furthermore, it eliminates the need for manually creating various load conditions, improving test efficiency. Attached Figure Description
[0046] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.
[0047] Figure 1This is a flowchart illustrating the inverter flow request testing method according to an embodiment of the present invention;
[0048] Figure 2 This is a flowchart illustrating another inverter flow request testing method according to an embodiment of the present invention;
[0049] Figure 3 This is a flowchart illustrating another inverter flow request testing method according to an embodiment of the present invention;
[0050] Figure 4 This is a structural block diagram of an inverter flow request testing device according to an embodiment of the present invention;
[0051] Figure 5 This is a schematic diagram of the hardware structure of the test equipment according to an embodiment of the present invention. Detailed Implementation
[0052] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0053] According to an embodiment of the present invention, an embodiment of an inverter flow request test method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.
[0054] This embodiment provides a method for testing inverter traffic request, which can be applied to test equipment for performing traffic request tests, such as test devices, tablet computers, etc. Figure 1 This is a flowchart of an inverter flow request test method according to an embodiment of the present invention, such as... Figure 1 As shown, the process includes the following steps:
[0055] Step S101: Obtain multiple test cases for the motor under each load condition and the delay time of the sensor.
[0056] Specifically, each test case includes, but is not limited to, the current operating condition signals collected by the sensors, the cooling medium flow request signals, fault signals, request trigger modes, trigger priorities, and the number of retries. The sensors are used to collect the current operating condition signals of the motor, which include, but are not limited to, the current motor temperature, the current transmission oil temperature, the current motor speed, the current motor torque, the current motor power, and the battery's state of charge (SOC). The cooling medium flow request signal includes the cooling medium flow rate corresponding to the current operating condition signal. Fault signals include, but are not limited to, various motor fault flags. The request trigger modes include periodic trigger modes and conditional trigger modes. The number of retries is the number of times the inverter retries the flow request when it fails to respond correctly to the motor request. It should be noted that test cases can be written in advance according to the actual test scenario and test requirements.
[0057] In some embodiments, the load conditions of the motor are mainly distinguished by operating condition signals such as motor temperature T_motor, transmission oil temperature T_oil, motor speed RPM, and motor torque Torque. The corresponding motor temperature T_motor, transmission oil temperature T_oil, motor speed RPM, and motor torque Torque are different for each load condition. These motor load conditions include, but are not limited to, low-speed low-torque, low-speed medium-torque, high-speed low-power, high-speed medium-power, low-speed high-torque, and high-speed high-power conditions, which can be specifically set according to the actual test scenario.
[0058] In some embodiments, the motor's operating condition signals can be acquired by sensors, and the delay time during sensor signal acquisition can be determined. Parameters such as cooling medium flow request signals, fault signals, request trigger modes, trigger priorities, and retry counts corresponding to each load condition can be stored in an external editable file such as an Excel / CSV file to form a MAP table. Test cases can then be constructed based on the MAP table to achieve full coverage of various load conditions.
[0059] It should be noted that test cases can be written using the Communication Access Programming Language (CAPL), but this application is not limited to this.
[0060] Step S102: For each load condition, send the original operating condition signal to the inverter under test and start timing. When the timing time reaches the delay time, send multiple test cases corresponding to the load condition to the inverter under test and obtain the test data of the inverter under test.
[0061] In some embodiments, a high-performance test device (e.g., CPU ≥ i5, memory ≥ 16GB) running CAN bus development environment software (e.g., CANoe) can be installed on a test bench. A CAN interface card supporting CAN / CAN-FD communication is inserted into the test device, and the test device is connected to the inverter under test via a CAN bus. The CAN interface card can be a VectorCAN interface card, but this application is not limited to this. Furthermore, if multiple buses are required to cover the inverter under test, the CAN bus between the test device and the inverter under test can also be connected in parallel with LIN, FlexRay, or Ethernet communication lines. Simultaneously, a temperature control chamber and a motor test bench can be deployed on the test bench to simulate ambient temperature and motor load conditions.
[0062] Furthermore, install a CAN bus analysis tool (such as VectorCANoe) and its corresponding driver on the test equipment to ensure that one or more test configuration files (TestConfiguration), virtual channels, and CAPL editing environments can be created, and a test case parameter library can be built.
[0063] Specifically, after the test starts, the general CAPL script in the test equipment automatically reads the test cases from the test case parameter library, maps the parameters of each test case to global variables in the CAPL script, and sets parameters such as sensor delay time and retry count through the test configuration file. Furthermore, during the CAPL script startup phase, a sensor delay timer is created, and a virtual channel between the test equipment and the inverter under test is configured to inject signals from the test cases, such as current operating condition signals, cooling medium flow request signals, fault signals, request trigger modes, trigger priorities, and retry counts, into the inverter under test.
[0064] In step S102, for each test case corresponding to each load condition, the CAPL script retrieves the current operating condition signal from the parameter list of the test case, including the current motor temperature, current transmission oil temperature, current motor speed, and current motor torque. First, the virtual channel is invoked to send the original operating condition signal, triggering the sensor delay timer to simulate the signal delay and filtering delay scenarios of the sensor acquisition link. After the timer reaches the sensor's delay time, the current operating condition signal, cooling medium flow request signal, and fault signal from the corresponding test case are injected into the inverter under test. The sensor delay time can be 10 seconds, but can be set according to the actual scenario; this application is not limited to this.
[0065] Step S103: Based on the test data, generate traffic request test results.
[0066] Specifically, after sending the current operating condition signal, cooling medium flow request signal, and fault signal from the test case to the inverter under test, the test data of the inverter under test is collected in real time and analyzed to generate the flow request test results.
[0067] The inverter flow request test method provided in this embodiment acquires current operating condition signals, cooling medium flow request signals, and fault signals corresponding to various load conditions of the motor, thereby comprehensively covering various load and fault conditions and improving test coverage. During testing, the original operating condition signal is first sent to the inverter under test and timing is started. When the timing reaches the sensor's delay time, the corresponding current operating condition signal, cooling medium flow request signal, and fault signal are then sent to the inverter under test, simulating the sensor's signal delay and filtering delay. Test data from the inverter under test is collected to obtain the flow request test results, further improving the coverage and accuracy of the test scenario. Furthermore, it eliminates the need for manually creating various load conditions, improving test efficiency.
[0068] This embodiment provides a method for testing inverter traffic request, which can be applied to test equipment for performing traffic request tests, such as test devices, tablet computers, etc. Figure 2 This is a flowchart of an inverter flow request test method according to an embodiment of the present invention, such as... Figure 2 As shown, the process includes the following steps:
[0069] Step S201: Obtain multiple test cases for the motor under each load condition, as well as the sensor delay time. See details in [link to relevant documentation]. Figure 1 The detailed description of step S101 in the illustrated embodiment will not be repeated here.
[0070] Step S202: For each load condition, send the original operating condition signal to the inverter under test and start timing. When the timing time reaches the delay time, send multiple test cases corresponding to the load condition to the inverter under test and obtain the test data of the inverter under test.
[0071] Specifically, step S202 includes:
[0072] Step S2021: For each load condition, send the original operating condition signal to the inverter under test and start timing.
[0073] Specifically, taking a thermistor (Negative Temperature Coefficient, NTC) sensor as an example, based on the current load conditions under test, a raw NTC temperature message is injected into the inverter under test, and a timer is started to simulate the measurement and filtering delay of the temperature sensor. Before the timer expires, the temperature information of the inverter under test remains at the old value, and flow determination and control are not triggered.
[0074] Step S2022: When the timing time is detected to have reached the delay time, a scheduling queue is constructed based on the trigger priority corresponding to each test case.
[0075] Specifically, after the timing reaches the delay time, the test equipment begins to inject current operating condition signals, fault signals, and cooling medium flow request signals into the inverter under test. The cooling medium flow request signal has two trigger modes: periodic trigger mode (sending requests periodically) and conditional trigger mode (sending requests only when a trigger condition is met). When performing flow request tests under multi-event scenarios, test cases from multiple trigger sources, such as periodic and conditional trigger requests, arrive simultaneously. The CAPL script first constructs a scheduling queue according to the trigger priority field defined in each test case, determining the scheduling order of multiple test cases. Based on the scheduling order determined by the scheduling queue, test cases are sent to the inverter under test one by one, ensuring that high-priority events send cooling medium flow request signals first, while low-priority events can be queued or discarded at an opportune time. The complete scheduling order and discard status of the scheduling queue are recorded in the log.
[0076] In this embodiment of the application, a scheduling queue is constructed according to the trigger priority field in the test case, and test cases are sent to the inverter under test based on the scheduling queue. This ensures that when multiple test cases with different request trigger modes arrive at the same time, high-priority events are sent first, while low-priority events can be queued or discarded, so as to verify the response performance of the inverter traffic request strategy under various request trigger modes.
[0077] Step S2023: For each test case in the scheduling queue, send the current operating condition signal and fault signal of the test case to the inverter under test in sequence, and send the cooling medium flow request signal of the test case to the inverter under test based on the request triggering mode, current operating condition signal and fault signal corresponding to the test case, so as to obtain the test data of the inverter under test.
[0078] Specifically, taking the NTC sensor as an example, the CAPL script injects the current operating condition signal into the inverter under test, thereby updating the temperature information of the inverter under test to the latest current motor temperature and current transmission oil temperature. According to the test cases, it sequentially injects signals such as current motor speed, current motor torque, SOC, and fault flags into the inverter under test. At the same time, according to the periodic trigger mode or conditional trigger mode, it sends a cooling medium flow request signal to the inverter under test at regular intervals or immediately.
[0079] In some optional implementations, step S2023 above includes:
[0080] Step a1: When the request triggering mode corresponding to the test case is detected to be the periodic triggering mode, a cooling medium flow request signal is sent to the inverter under test based on the preset period, and the actual sending time of the cooling medium flow request signal is recorded.
[0081] Specifically, for the periodic trigger mode test, the test equipment sends a cooling medium flow request signal to the inverter under test at regular intervals according to the configured preset period, and records the actual transmission time of each frame of the cooling medium flow request signal. The preset period can be 1 second, 10 seconds, etc., and this application is not limited to this.
[0082] Step a2: When it is detected that the request triggering mode corresponding to the test case is the condition triggering mode, and the current operating condition signal or fault signal corresponding to the test case exceeds the signal threshold, a cooling medium flow request signal is sent to the inverter under test, and the sending delay of the cooling medium flow request signal is recorded.
[0083] Specifically, for condition-triggered mode testing, the test equipment monitors whether the current operating condition signal or fault signal exceeds a signal threshold based on the current operating condition signal and fault signal in the test case, such as current motor temperature, current transmission oil temperature, current motor speed, current motor torque, SOC, and fault flags. If the current operating condition signal or fault signal exceeds the signal threshold, it indicates a sudden change in motor load. The time of the change is recorded, and a cooling medium flow request signal is immediately sent to the inverter under test. The transmission delay of the cooling medium flow request signal is obtained based on the difference between the actual transmission time of the cooling medium flow request signal and the change time. The signal threshold includes thresholds for both the current operating condition signal and the fault signal, which can be set according to the actual scenario.
[0084] Step a3: Obtain the test data of the inverter under test based on the actual transmission time and / or transmission delay.
[0085] Specifically, the actual transmission time of the cooling medium flow request signal for each frame under the periodic trigger mode test, and / or the transmission delay under the condition trigger mode test, are recorded in the test data of the inverter under test.
[0086] In this embodiment, a cooling medium flow request signal is sent to the inverter under test according to a preset period, and the actual sending time of the cooling medium flow request signal is recorded; and / or, when a sudden change is detected in the current operating condition signal or fault signal, a cooling medium flow request signal is sent to the inverter under test, and the sending delay of the cooling medium flow request signal is recorded, so as to verify the correctness and response performance of the flow request strategy in both time-driven and event-driven dimensions.
[0087] In some optional implementations, after sending a cooling medium flow request signal to the inverter under test, the system continuously receives response signals from the inverter under test in response to the cooling medium flow request signal, and obtains the test data of the inverter under test based on the response signals.
[0088] Specifically, the actual sending time of the cooling medium flow request signal, the response signal fed back by the inverter under test, and the response time of the response signal are recorded in the test data of the inverter under test in order to verify whether the inverter under test can correctly respond to the cooling medium flow request signal sent by the test equipment.
[0089] This embodiment continuously receives the response signal from the inverter under test in response to the cooling medium flow request signal, in order to determine whether the inverter under test can correctly respond to the cooling medium flow request signal sent by the test equipment, thereby verifying the correctness and response performance of the flow request strategy.
[0090] In some alternative implementations, before continuously receiving the response signal from the inverter under test in response to the cooling medium flow request signal, an abnormal frame signal is constructed based on the current operating condition signal in the test case; and the abnormal frame signal is sent to the inverter under test.
[0091] Specifically, based on the current operating condition signal, abnormal frame signals such as Cyclic Redundancy Check (CRC) error frames, abnormal frame length frames, and high-frequency burst frames above 10Hz can be constructed through a virtual channel or hardware signal generator. These abnormal frame signals are then injected into the inverter under test to verify the inverter's ability to ignore abnormal frames. This confirms that the inverter under test does not deadlock or restart and can immediately resume responding correctly to legitimate requests after the abnormality ends, thereby verifying the robustness of the traffic request strategy.
[0092] In some optional implementations, if the response signal is detected as an incorrect response signal, or if no response signal is received within a preset timeout window, the cooling medium flow request signal is resent to the inverter under test; when the number of resentments of the cooling medium flow request signal reaches the retry count, the inverter under test is controlled to perform flow control based on the preset cooling medium flow rate.
[0093] In some embodiments, the data consistency and message format of the response signal are verified. If the verification fails, it is determined that the response signal failed to correctly respond to the cooling medium flow request signal, that is, the response signal is an incorrect response signal, and the cooling medium flow request signal is resent to the inverter under test. Alternatively, after sending the cooling medium flow request signal, a timeout timer is triggered. If no response signal is received within the preset timeout window, the cooling medium flow request signal is resent to the inverter under test. The specific duration of the preset timeout window can be set according to the actual test requirements.
[0094] In this embodiment, if no response signal is received or an erroneous response signal is received within the preset timeout window, the CAPL script triggers a retry mechanism to resend the cooling medium flow request signal until the number of retries is reached. After the number of retries is exhausted, the inverter under test automatically switches to the backup flow strategy and performs flow control according to the preset cooling medium flow. At the same time, the test equipment records alarm information through logError() and issues alarm tags through the internal log system.
[0095] This application embodiment verifies the correctness of the response signal and the response time. If the response signal is detected as an incorrect response signal or no response signal is received within the preset timeout window, the cooling medium flow request signal is resent to the inverter under test until the number of retries is reached. This allows the inverter under test to perform flow control based on the backup flow strategy, so as to verify the performance of the controller under test in the timeout retry scenario.
[0096] Step S203: Based on the test data, generate traffic request test results.
[0097] Specifically, step S203 includes:
[0098] Step S2031: Obtain the response test result based on the response signal in the test data.
[0099] Specifically, the data consistency and message format of the response signal are verified to determine whether the inverter under test can correctly respond to the cooling medium flow request signal. The response time of the response signal is detected to determine whether the inverter under test can respond to the cooling medium flow request signal in a timely manner, and the response test results are obtained.
[0100] Step S2032: Based on the actual transmission time in the test data, obtain the interval time between two adjacent frames of cooling medium flow request signals, and obtain the periodic trigger test result based on the jitter time of the interval time compared with the preset period.
[0101] For example, the difference between the interval between two adjacent frames of cooling medium flow request signals and a preset period is determined to obtain the jitter time. If the jitter time is within the preset jitter range, the periodic trigger test is qualified; if the jitter time is not within the preset jitter range, the periodic trigger test is unqualified, thus obtaining the periodic trigger test result. The preset jitter range can be -1ms to 1ms, and can be set according to actual test requirements; this application is not limited to this.
[0102] Step S2033: Based on the relationship between the sending delay and the delay threshold of the cooling medium flow request signal in each frame of the test data, the condition-triggered test result is obtained.
[0103] Specifically, the test determines whether the transmission delay of the cooling medium flow request signal is greater than a delay threshold. If the transmission delay is greater than the delay threshold, the conditional trigger test fails; if the transmission delay is less than or equal to the delay threshold, the conditional trigger test passes, thus obtaining the conditional trigger test result. The delay threshold can be 20ms, but it can be set according to actual test requirements, and this application is not limited to this.
[0104] Step S2034: Obtain the traffic request test result based on the response test result and / or the periodic trigger test result and / or the conditional trigger test result.
[0105] Specifically, the response test results, periodic trigger test results, and conditional trigger test results are analyzed and processed to obtain the traffic request test results.
[0106] In this embodiment, the CAPL script uses interfaces such as write() and logError() to record test data throughout the execution process, including: test case number, trigger time, test case parameters injected into the inverter under test, actual transmission time of the cooling medium flow request signal, response time of the response signal, number of retransmissions of the cooling medium flow request signal, scheduling order of the scheduling queue, and exception handling status. After the test, the ASC / BLF log file is saved, and VectorReportWizard or a custom script is used to automatically extract key indicators, analyze cycle jitter distribution, trigger delay statistics, retry distribution, and exception robustness results, and generate a visualized PDF / HTML test report, which is then archived and alerted through the CI platform. The test report may include test case pass rate, timing error graph, concurrent scheduling status, retransmission count graph, and exception handling summary, but this application is not limited to these.
[0107] This application improves the test coverage and efficiency of traffic request testing by covering test cases under various load conditions and supporting one-click command-line execution of traffic request tests and automatic report generation. It can be seamlessly integrated into CI pipelines, significantly reducing labor costs and improving the speed and quality of regression testing.
[0108] This application embodiment analyzes the actual transmission time and transmission delay of the cooling medium flow request signal and the response signal fed back by the inverter under test under various load conditions. It verifies the correctness and reliability of the response signal, the timing jitter of the periodic trigger frame and the delay of the conditional trigger frame, comprehensively covering various test scenarios and improving test coverage and test efficiency.
[0109] Traditional semi-automatic testing largely relies on manual testing or a small number of scripts. Manual operation is time-consuming and labor-intensive, resulting in low test coverage and efficiency. It is difficult to verify hundreds or even thousands of operating conditions point by point, and continuous integration testing is challenging. Furthermore, timing accuracy is difficult to guarantee, and the jitter of periodic frames and the latency of conditionally triggered frames cannot be reliably quantified. In addition, there is a lack of systematic verification for abnormal scenarios such as malformed packets, frame loss, and fault injection, making it impossible to fully assess the robustness of traffic request strategies.
[0110] The inverter traffic request testing method provided in this embodiment eliminates the maintenance difficulties caused by hard coding by managing test cases in a tabular format and dynamically loading them into the test equipment using CAPL scripts. It comprehensively covers normal operating conditions, boundary conditions, extreme operating conditions, and abnormal operating conditions by simulating various test scenarios such as sensor latency, periodic triggering tests, conditional triggering tests, retry strategy verification, backup strategy switching when retry attempts are exhausted, priority queue scheduling, and abnormal frame injection. Test data is recorded in real time, and test results are analyzed.
[0111] This invention not only significantly improves testing efficiency and enables seamless integration of batch command-line triggering with CI pipelines, but also automatically generates visual reports, providing a high-coverage, high-precision, and high-reliability closed-loop process for the research and verification of traffic request strategies, effectively reducing labor costs and improving the quality and speed of regression testing.
[0112] The traffic request testing scheme of the present invention will be described in detail below with reference to a specific application example.
[0113] This application example provides an inverter flow request testing system, which consists of a hardware environment, a software platform, a signal injection module, a signal acquisition module, and an automation script library working together.
[0114] The hardware environment includes a test device and a VectorCAN interface card. The test device runs the CANoe platform and test scripts. The VectorCAN interface card of the test device is directly connected to the main control board of the inverter under test via a CAN or CAN-FD bus. The main control board of the inverter under test provides a signal injection channel for the NTC temperature sensor. Through the virtual channel driven by CANoeCAPL, the signal injection process of "raw NTC temperature message → 10s delay → final temperature" is realized. Signals such as motor speed, motor torque, and fault flags can all be injected through CANoe driver or hardware signal source.
[0115] The software platform, centered on VectorCANoe, loads test configuration files and CAPL scripts from the automation script library, providing virtual channel injection and bus monitoring functions for the inverter under test. Based on test case parameter tables in Excel / CSV format, the platform automatically reads parameters such as cooling medium request flow rate, retry count, and priority configuration for each load condition during runtime, achieving parameter-driven operation.
[0116] The signal injection module uses a CANoe virtual channel to simulate original NTC temperature messages, sensor delays, and signal updates for test cases. Under concurrent conditions, it sends the latest signals from the test cases to the inverter under test according to a scheduling queue. The signal acquisition module records the signal interaction process through logs and calls VectorReportWizard to parse the message files, extract key indicators, and generate test reports.
[0117] The inverter traffic request test system in this embodiment supports command-line mode, which can trigger the batch execution of specified test cases with one click. It realizes full load condition test coverage, timing accuracy verification in periodic trigger mode, retry strategy verification, etc., which significantly improves the testing efficiency and reliability of inverter traffic request strategy.
[0118] like Figure 3 As shown, this application example includes the following steps:
[0119] Step S301: Read all test parameters from an external Excel / CSV file, including the cooling medium flow rate, preset cycle, number of retries, and priority corresponding to various load conditions.
[0120] Specifically, the test equipment uses an editable EXCE / CSV file and a CAPL script to inject information such as motor temperature, transmission oil temperature, motor speed, and motor torque into the inverter to simulate the actual load conditions of the motor system.
[0121] Step S302: Inject the original NTC temperature message into the inverter under test and start a 10s timer to simulate sensor delay and filter delay.
[0122] Step S303: After the timer expires, the latest motor temperature signal and transmission oil temperature signal are sent to the inverter under test. At the same time, according to the test case, the latest motor speed signal, motor torque signal, motor power signal, SOC, fault flag, periodically triggered cooling medium flow request signal, and conditionally triggered cooling medium flow request signal are injected into the inverter under test.
[0123] Step S304: Real-time capture of the response signal returned by the inverter under test, record test data such as the actual sending time of the cooling medium flow request signal, the response time of the response signal, the number of times the cooling medium flow request signal is resent, and the priority scheduling status, and organize and record the test data through ASC / BLF logs and CAPL scripts.
[0124] Step S305: Analyze the test data using the reporting tool, extract period jitter distribution, trigger delay statistics, retry distribution, abnormal robustness results, etc., generate a visual report and automatically archive it to the CI platform.
[0125] This embodiment also provides an inverter flow request testing device, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.
[0126] This embodiment provides an inverter flow request testing device, such as... Figure 4 As shown, it includes:
[0127] The acquisition module 401 is used to acquire multiple test cases corresponding to the motor under each load condition and the delay time of the sensor; wherein, each test case includes the current operating condition signal collected by the sensor, the cooling medium flow request signal and the fault signal;
[0128] The first processing module 402 is used to send the original operating condition signal to the inverter under test for each load condition and to perform timing. When the timing time reaches the delay time, it sends multiple test cases corresponding to the load condition to the inverter under test and obtains the test data of the inverter under test.
[0129] The second processing module 403 is used to generate traffic request test results based on the test data.
[0130] In some optional implementations, the test cases also include a request triggering mode and a triggering priority; the first processing module 402 is further configured to:
[0131] A scheduling queue is constructed based on the trigger priority corresponding to each test case;
[0132] For each test case in the scheduling queue, the current operating condition signal and fault signal of the test case are sent to the inverter under test in sequence. Based on the request triggering mode, current operating condition signal and fault signal corresponding to the test case, the cooling medium flow request signal of the test case is sent to the inverter under test to obtain the test data of the inverter under test.
[0133] In some optional implementations, the request triggering mode includes a periodic triggering mode and a conditional triggering mode; the first processing module 402 is further configured to:
[0134] When the request triggering mode corresponding to the test case is detected to be the periodic triggering mode, a cooling medium flow request signal is sent to the inverter under test based on the preset period, and the actual sending time of the cooling medium flow request signal is recorded.
[0135] When it is detected that the request triggering mode corresponding to the test case is the condition triggering mode, and the current operating condition signal or fault signal corresponding to the test case exceeds the signal threshold, a cooling medium flow request signal is sent to the inverter under test, and the sending delay of the cooling medium flow request signal is recorded.
[0136] Test data of the inverter under test are obtained based on the actual transmission time and / or transmission delay.
[0137] In some alternative implementations, after sending a cooling medium flow request signal to the inverter under test, the first processing module 402 is further configured to:
[0138] It continuously receives response signals from the inverter under test in response to the cooling medium flow request signal;
[0139] Based on the response signal, the test data of the inverter under test is obtained.
[0140] In some optional implementations, the test cases also include a number of retries; the first processing module 402 is further configured to:
[0141] If the response signal is detected as an incorrect response signal, or if no response signal is received within the preset timeout window, the cooling medium flow request signal is resent to the inverter under test.
[0142] When the number of retransmissions of the cooling medium flow request signal reaches the retry count, the inverter under test is controlled to perform flow control based on the preset cooling medium flow rate.
[0143] In some alternative implementations, before continuously receiving response signals from the inverter under test regarding its request for cooling medium flow, the first processing module 402 is further configured to:
[0144] Based on the current operating condition signals in the test cases, construct abnormal frame signals;
[0145] Send an abnormal frame signal to the inverter under test.
[0146] In some alternative implementations, the second processing module 403 is further configured to:
[0147] The response test results are obtained based on the response signals in the test data;
[0148] And / or, based on the actual transmission time in the test data, obtain the interval time between two adjacent frames of cooling medium flow request signals, and based on the jitter time of the interval time compared with the preset period, obtain the periodic trigger test result;
[0149] And / or, based on the relationship between the transmission delay and the delay threshold of the cooling medium flow request signal in each frame of the test data, the condition-triggered test results are obtained;
[0150] The traffic request test results are obtained based on the response test results and / or the periodic trigger test results and / or the conditional trigger test results.
[0151] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.
[0152] In this embodiment, the inverter flow request test device is presented in the form of a functional unit. Here, a unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.
[0153] This invention also provides a testing device having the above-described features. Figure 4 The inverter flow request test device shown is shown.
[0154] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of a testing device provided in an optional embodiment of the present invention, such as... Figure 5As shown, the test device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise as required. The processors can process instructions executed within the test device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple test devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 5 Take a processor 10 as an example.
[0155] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.
[0156] The memory 20 stores instructions executable by at least one processor 10 to cause the at least one processor 10 to perform the method shown in the above embodiments.
[0157] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the test equipment. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories can be connected to the test equipment via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0158] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 20 may also include a combination of the above types of memory.
[0159] The testing equipment also includes an input device 30 and an output device 40. The processor 10, memory 20, input device 30, and output device 40 can be connected via a bus or other means. Figure 5 Taking the example of a connection between China and Israel via a bus.
[0160] Input device 30 can receive input numerical or character information, and generate key signal inputs related to user settings and function control of the test equipment, such as a touch screen, keypad, mouse, trackpad, touchpad, indicator, one or more mouse buttons, trackball, joystick, etc. Output device 40 may include display devices, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibration motors). The aforementioned display devices include, but are not limited to, liquid crystal displays, light-emitting diodes, displays, and plasma displays. In some alternative embodiments, the display device may be a touch screen.
[0161] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as computer code that can be recorded on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.
[0162] A portion of this invention can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to the invention through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions, or the computer compiling the instructions and then executing the corresponding compiled program, or the computer reading and executing the instructions, or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.
[0163] Although embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations all fall within the scope defined by the appended claims.
Claims
1. A method for testing inverter flow request, characterized in that, The method includes: The system acquires multiple test cases for the motor under each load condition, as well as the delay time of the sensors; each test case includes the current operating condition signal, cooling medium flow request signal, and fault signal collected by the sensors. For each load condition, a raw load condition signal is sent to the inverter under test and a timer is started. When the timer reaches the delay time, multiple test cases corresponding to the load condition are sent to the inverter under test and the test data of the inverter under test is obtained. Based on the test data, traffic request test results are generated.
2. The method according to claim 1, characterized in that, The test cases also include request triggering modes and triggering priorities; The step of sending multiple test cases corresponding to the load condition to the inverter under test and obtaining the test data of the inverter under test includes: A scheduling queue is constructed based on the trigger priority corresponding to each test case; For each test case in the scheduling queue, the current operating condition signal and fault signal of the test case are sent to the inverter under test in sequence, and the cooling medium flow request signal of the test case is sent to the inverter under test based on the request triggering mode, current operating condition signal and fault signal corresponding to the test case, so as to obtain the test data of the inverter under test.
3. The method according to claim 2, characterized in that, The request triggering mode includes a periodic triggering mode and a conditional triggering mode; based on the request triggering mode corresponding to the test case, the current operating condition signal, and the fault signal, the cooling medium flow request signal in the test case is sent to the inverter under test to obtain the test data of the inverter under test, including: When it is detected that the request triggering mode corresponding to the test case is the periodic triggering mode, a cooling medium flow request signal is sent to the inverter under test based on a preset period, and the actual sending time of the cooling medium flow request signal is recorded. When it is detected that the request triggering mode corresponding to the test case is the condition triggering mode, and the current operating condition signal or fault signal corresponding to the test case exceeds the signal threshold, a cooling medium flow request signal is sent to the inverter under test, and the sending delay of the cooling medium flow request signal is recorded. Test data of the inverter under test are obtained based on the actual transmission time and / or the transmission delay.
4. The method according to claim 3, characterized in that, After sending a cooling medium flow request signal to the inverter under test, the method further includes: Continuously receive response signals from the inverter under test in response to the cooling medium flow request signal; Based on the response signal, the test data of the inverter under test is obtained.
5. The method according to claim 4, characterized in that, The test cases also include the number of retries; the method also includes: If the response signal is detected as an erroneous response signal, or if the response signal is not received within the preset timeout window, the cooling medium flow request signal is resent to the inverter under test. When the number of retransmissions of the cooling medium flow request signal reaches the retry count, the inverter under test is controlled to perform flow control based on the preset cooling medium flow rate.
6. The method according to claim 4, characterized in that, The step of generating traffic request test results based on the test data includes: Based on the response signals in the test data, the response test results are obtained; And / or, based on the actual transmission time in the test data, obtain the interval time between two adjacent frames of cooling medium flow request signals, and based on the jitter time of the interval time compared with the preset period, obtain the periodic trigger test result; And / or, based on the relationship between the transmission delay and the delay threshold of the cooling medium flow request signal in each frame of the test data, the condition-triggered test results are obtained; Based on the response test results and / or the periodic trigger test results and / or the conditional trigger test results, the traffic request test results are obtained.
7. The method according to claim 4, characterized in that, Before continuously receiving the response signal from the inverter under test in response to the cooling medium flow request signal, the method further includes: Based on the current operating condition signals in the test cases, an abnormal frame signal is constructed; The abnormal frame signal is sent to the inverter under test.
8. An inverter flow request testing device, characterized in that, The device includes: The acquisition module is used to acquire multiple test cases corresponding to the motor under each load condition and the delay time of the sensor; wherein, each test case includes the current operating condition signal, cooling medium flow request signal and fault signal collected by the sensor; The first processing module is used to send the original operating condition signal to the inverter under test for each load condition and to perform timing. When the timing time reaches the delay time, it sends multiple test cases corresponding to the load condition to the inverter under test and obtains the test data of the inverter under test. The second processing module is used to generate traffic request test results based on the test data.
9. A testing device, characterized in that, include: The system includes a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to perform the inverter flow request test method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to execute the inverter flow request test method according to any one of claims 1 to 7.
11. A computer program product, characterized in that, Includes computer instructions for causing a computer to execute the inverter flow request test method according to any one of claims 1 to 7.