An interactive test method and system for a hybrid vehicle drive controller

Abstract

The application provides a hybrid vehicle driving controller interaction test method and system, the method comprises: obtaining an input signal, the input signal comprises a vehicle state signal and an operation signal; inputting the input signal into a preset signal simulation model, so that the signal simulation model simulates a plurality of CAN signals and a plurality of IO signals corresponding to the input signal; inputting the plurality of CAN signals and the plurality of IO signals into a vehicle controller, so that the vehicle controller processes the plurality of CAN signals and the plurality of IO signals, generates corresponding torque request messages and sends them to an engine controller and a motor controller respectively; obtaining a plurality of response signals output by the engine controller and the motor controller; comparing the plurality of response signals with a preset output result, and then judging whether the measured function of the driving control system is normal, thereby improving the accuracy of the driving controller interaction test.

Description

Technical Field

[0001] This application relates to the field of interactive testing technology, and in particular to an interactive testing method and system for a hybrid vehicle drive controller. Background Technology

[0002] As a core component of the powertrain system in electric or hybrid vehicles, the automotive drive controller is responsible for receiving instructions from the vehicle control unit and precisely controlling parameters such as the motor's speed and torque to achieve functions such as vehicle acceleration, deceleration, braking, and energy recovery. Therefore, functional testing of the automotive drive controller to ensure its stable performance and reliability is an indispensable part of the automotive research and development and production process.

[0003] Currently, functional testing of automotive drive controllers primarily relies on simulation testing in a laboratory environment and real-world road testing. Real-world road testing directly evaluates the drive controller's performance in actual use by driving on real roads. While this method more realistically reflects the drive controller's performance, it is costly, poses safety risks, and is difficult to conduct on a large scale. Simulation testing typically utilizes motor test benches and data acquisition systems to simulate different operating conditions and loads, testing key indicators such as the drive controller's output performance, efficiency, and response speed. However, traditional simulation testing mainly focuses on building individual controller test environments for engine or motor controllers. This method has several drawbacks: 1) The test environment for individual drive controllers differs significantly from the test environment for interaction with the actual vehicle drive control system. The power-on / off interaction and torque coordination functions of the actual vehicle drive control system cannot be verified in the individual controller environment. 2) Due to the differences between the individual controller test environment and the actual vehicle environment, issues such as the power-on / off timing and torque controller timing of the drive control system are easily overlooked until the actual vehicle development stage, where the cost of fixing these issues far exceeds that of the controller development stage. 3) The drive controller problems discovered after the sale are usually interactive problems of the drive control system. The controller unit test environment is difficult to reproduce such complex after-sales problem scenarios and cannot help to quickly solve after-sales problems. Summary of the Invention

[0004] To address the aforementioned technical issues, this application provides an interactive testing method and system for hybrid vehicle drive controllers, constructing a testing environment that more closely resembles the actual vehicle drive control system, thereby improving the accuracy and efficiency of drive controller interactive testing.

[0005] In a first aspect, embodiments of this application provide an interactive testing method for a hybrid vehicle drive controller, including:

[0006] Acquire input signals, including vehicle status signals and operation signals;

[0007] The input signal is input to a preset signal simulation model, so that the signal simulation model simulates and generates a number of corresponding CAN signals and a number of IO signals according to the input signal.

[0008] The plurality of CAN signals and the plurality of IO signals are input to the vehicle controller, so that the vehicle controller performs calculations on the plurality of CAN signals and the plurality of IO signals, generates corresponding torque request messages, and sends them to the engine controller and the motor controller respectively.

[0009] Acquire several response signals output by the engine controller and the motor controller;

[0010] The measured response signals are compared with the preset output results to determine whether the tested function of the drive control system is normal.

[0011] This application provides an interactive testing method for hybrid vehicle drive controllers. It integrates the actual vehicle controller, motor controller, and engine controller. By inputting simulated signals to the vehicle controller, it processes and responds to the data, further interacting with the engine and motor controllers. Finally, by analyzing the response signals of the engine and motor controllers, it completes the overall interactive test of each drive controller. This avoids the significant difference between the individual drive controller testing environment and the actual vehicle drive control system interaction testing environment in existing technologies. Furthermore, this application uses signal simulation models to generate simulated signals for other vehicle controllers to construct a complete vehicle testing environment. This allows for the early detection of systemic interaction problems that would otherwise only be apparent in a real vehicle, even before the prototype is manufactured. This intercepts serious systemic problems during the component development stage, improving the efficiency of vehicle manufacturing and design. Moreover, the simulated signal design allows testers to quickly adjust relevant simulation parameters as needed, significantly improving the efficiency of drive controller interactive testing compared to full physical testing.

[0012] In one possible implementation, acquiring the input signal includes:

[0013] The operation signals are obtained through a host computer, and the operation signals include throttle signals and brake signals.

[0014] Vehicle status signals are obtained through a preset vehicle model. These vehicle status signals include vehicle speed signal, vehicle attitude signal, battery status signal, gear signal, and power mode signal.

[0015] This embodiment simulates acceleration and braking operations during vehicle operation by inputting operation signals from the upper control unit. Since only the vehicle controller, engine controller, and motor controller actually exist in this embodiment, it is necessary to simulate the vehicle's driving state based on a preset vehicle model and obtain vehicle status signals from the model. Obtaining the operation signals and vehicle status signals provides the data foundation for subsequent calculations by the vehicle controller.

[0016] In one possible implementation, the signal simulation model simulates and generates corresponding CAN signals and IO signals based on the input signal, including:

[0017] Based on the input signal, several VCU sensor signals, several ECM sensor signals, and several MCU sensor signals are generated through a preset IO model, which serve as the several IO signals;

[0018] Based on the input signal, several preset residual bus simulation signals and several real-time residual bus simulation signals are generated through a preset CAN bus model as the several CAN signals, wherein the real-time residual bus simulation signals are generated in real time by a preset vehicle model.

[0019] This application provides a method for signal simulation generation. Since the acquired input signals cannot be directly recognized by the vehicle controller, they need to be converted to simulate and generate several I / O signals and CAN signals. The I / O signals are mainly sensor signals, such as throttle opening and brake switch of the VCU, oxygen sensor, intake air pressure, oil and water temperature, and ambient temperature of the ECM, and temperature and resolver of the MCU. The CAN signals are mainly residual bus simulation signals; some are set by the tester, such as ignition key position, gear, and vehicle mode, while others are generated in real-time based on calculations from the vehicle model, such as vehicle speed, lateral acceleration, and yaw rate. By generating several I / O signals and several CAN signals, the controller under test can achieve closed-loop control in a simulation environment, improving the accuracy of drive controller interaction testing.

[0020] In one possible implementation, the engine controller and the motor controller output response signals, including:

[0021] The engine controller generates corresponding fuel injection actuator signals and ignition actuator signals based on the torque request message, as the response signals;

[0022] The motor controller generates a corresponding PWM drive actuator signal based on the torque request message, which serves as the response signal.

[0023] Furthermore, after the engine controller and the motor controller receive the torque request message, the engine controller and the motor controller perform data interaction, including:

[0024] The engine controller receives a fault light illumination request signal sent by the motor controller;

[0025] The engine controller sends engine start status, speed, and fault information to the motor controller.

[0026] In this embodiment, the engine controller and motor controller each generate different response signals based on the simulated driving environment and the torque request message from the vehicle controller. These response signals are then collected and compared with preset output results to complete the interaction test of the drive controllers. Furthermore, after receiving the torque request message, the engine controller and motor controller perform several data interactions, more realistically simulating the data interaction scenario during actual vehicle operation. This achieves data linkage between different drive controllers under the test environment. Compared to existing single-drive controller testing methods, this embodiment effectively captures potential problems in the data interaction of various drive controllers, further improving the accuracy of drive controller interaction testing.

[0027] In one possible implementation, comparing the plurality of response signals with preset output results to determine whether the tested function of the drive control system is normal includes:

[0028] Calculate the first time difference between the signal received by the vehicle controller and the response signal output by the engine controller;

[0029] Calculate the second time difference between the signal received by the vehicle controller and the response signal output by the motor controller;

[0030] Calculate the third time difference between the output response signal of the engine controller and the output response signal of the motor controller;

[0031] The first time difference, the second time difference, and the third time difference are compared with preset output results to determine whether the torque coordination control function between the vehicle controller, the engine controller, and the motor controller is normal.

[0032] In this embodiment of the application, the first time difference, the second time difference, and the third time difference are obtained by recording the time difference between the vehicle controller receiving the input signal and the engine controller and the motor controller outputting the signal. Each time difference is compared with the preset output result to verify whether the real-time performance of the actual vehicle torque coordinated control meets the preset requirements and to determine whether the functional logic strategy of the drive control system is normal.

[0033] Furthermore, the interaction testing method also includes:

[0034] The aforementioned response signals are input to a preset vehicle model, so that the vehicle model updates its current vehicle state based on the aforementioned response signals, thereby generating a corresponding updated vehicle state signal.

[0035] In this embodiment, after the engine controller and motor controller generate response signals, each response signal is further input to the vehicle model to update the current vehicle state and provide a data basis for the next input of the vehicle controller. This realizes the cyclical data interaction and data conversion between the virtual vehicle model and the real drive controllers, providing testers with an efficient automated testing environment. It can realize automated testing of the hybrid drive controller interaction function with higher efficiency than manual testing of real vehicles, and improve the efficiency of drive controller interaction testing.

[0036] Secondly, correspondingly, embodiments of this application provide an interactive testing system for a hybrid vehicle drive controller, including a first acquisition module, a signal simulation module, a controller execution module, a second acquisition module, and a judgment module;

[0037] The first acquisition module is used to acquire input signals, which include vehicle status signals and operation signals.

[0038] The signal simulation module is used to input the input signal to a preset signal simulation model, so that the signal simulation model simulates and generates a number of corresponding CAN signals and a number of IO signals according to the input signal.

[0039] The controller execution module is used to input the plurality of CAN signals and the plurality of IO signals to the vehicle controller, so that the vehicle controller performs calculations on the plurality of CAN signals and the plurality of IO signals, generates corresponding torque request messages, and sends them to the engine controller and the motor controller respectively.

[0040] The second acquisition module is used to acquire several response signals output by the engine controller and the motor controller;

[0041] The judgment module is used to compare the plurality of response signals with preset output results, thereby determining whether the tested function of the drive control system is normal.

[0042] In one possible implementation, the signal simulation model simulates and generates corresponding CAN signals and IO signals based on the input signal, including:

[0043] Based on the input signal, several VCU sensor signals, several ECM sensor signals, and several MCU sensor signals are generated through a preset IO model, which serve as the several IO signals;

[0044] Based on the input signal, several preset residual bus simulation signals and several real-time residual bus simulation signals are generated through a preset CAN bus model as the several CAN signals, wherein the real-time residual bus simulation signals are generated in real time by a preset vehicle model.

[0045] In one possible implementation, the engine controller and the motor controller output response signals, including:

[0046] The engine controller generates corresponding fuel injection actuator signals and ignition actuator signals based on the torque request message, as the response signals;

[0047] The motor controller generates a corresponding PWM drive actuator signal based on the torque request message, which serves as the response signal. Attached Figure Description

[0048] Figure 1 : A flowchart illustrating an interactive testing method for a hybrid vehicle drive controller provided in an embodiment of this application.

[0049] Figure 2 This is a schematic diagram of the structure of a traditional single-unit drive controller simulation test system.

[0050] Figure 3 This is a schematic diagram of a traditional multi-controller vehicle testing system.

[0051] Figure 4 : A schematic diagram of the structure of a simulation test system used to implement the interactive test method provided in the embodiments of this application.

[0052] Figure 5 : A schematic diagram of the structure of an interactive testing device used to implement the interactive testing method provided in the embodiments of this application.

[0053] Figure 6 This is a schematic diagram of the data interaction process of various models in an interactive testing method for a hybrid vehicle drive controller provided in an embodiment of this application.

[0054] Figure 7 : A schematic diagram of the structure of an interactive test system for a hybrid vehicle drive controller provided in an embodiment of this application. Detailed Implementation

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

[0056] It should be noted that the step numbers in this document are only for the convenience of explaining the specific embodiments and are not intended to limit the order in which the steps are performed. In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature specified as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0057] Example 1:

[0058] like Figure 1 As shown, Embodiment 1 provides an interactive testing method for a hybrid vehicle drive controller, including steps S1-S5:

[0059] Step S1: Acquire input signals, including vehicle status signals and operation signals;

[0060] Step S2: Input the input signal to a preset signal simulation model so that the signal simulation model can simulate and generate a number of corresponding CAN signals and a number of IO signals according to the input signal;

[0061] Step S3: Input the plurality of CAN signals and the plurality of IO signals to the vehicle controller, so that the vehicle controller can perform calculations on the plurality of CAN signals and the plurality of IO signals, generate corresponding torque request messages, and send them to the engine controller and the motor controller respectively.

[0062] Step S4: Acquire several response signals output by the engine controller and the motor controller;

[0063] Step S5: Compare the several response signals with the preset output results to determine whether the tested function of the drive control system is normal.

[0064] This application provides an interactive testing method for hybrid vehicle drive controllers. It integrates the actual vehicle controller, motor controller, and engine controller. By inputting simulated signals to the vehicle controller, it processes and responds to the data, further interacting with the engine and motor controllers. Finally, by analyzing the response signals of the engine and motor controllers, it completes the overall interactive test of each drive controller. This avoids the significant difference between the individual drive controller testing environment and the actual vehicle drive control system interaction testing environment in existing technologies. Furthermore, this application uses signal simulation models to generate simulated signals for other vehicle controllers to construct a complete vehicle testing environment. This allows for the early detection of systemic interaction problems that would otherwise only be apparent in a real vehicle, even before the prototype is manufactured. This intercepts serious systemic problems during the component development stage, improving the efficiency of vehicle manufacturing and design. Moreover, the simulated signal design allows testers to quickly adjust relevant simulation parameters as needed, significantly improving the efficiency of drive controller interactive testing compared to full physical testing.

[0065] Traditional controller unit testing systems, such as Figure 2 As shown, the message exchanges between controllers are sent by the tester via a host computer, therefore the real-time performance of millisecond-level message exchanges between the drive controllers cannot be verified. The torque coordination control signal flow in a real hybrid vehicle is as follows: Figure 3 As shown, although the real-time communication between various drive controllers can be effectively verified through actual vehicles, this test system relies on a real-world driving environment, resulting in high deployment and testing costs. Even if problems are discovered through testing, the cost of fixing them in the real-world vehicle phase far exceeds the cost of controller development. Therefore, in a preferred embodiment, as... Figure 4 As shown, a real-time system is constructed by replacing the actual vehicle with a real-time system, creating a test environment consisting of a real-time system, a vehicle controller, and engine and motor controllers to implement the interactive testing method proposed in this application. In this application embodiment, the physical characteristics of the actual vehicle, engine, and motor are simulated using a vehicle model. Sensor signals and driver operation signals are simulated using an IO model, while actuator drive signals from the engine and motor controllers are simultaneously acquired. Vehicle status messages from other controllers are simulated using a CAN bus model, while CAN messages from the engine and motor controllers are simultaneously acquired. By recording the time difference between the vehicle controller receiving the input signal and the engine and motor controllers outputting the signal, the real-time performance of the torque coordination control of the actual vehicle is verified on a test bench.

[0066] In one possible implementation, step S1, acquiring the input signal, includes:

[0067] The operation signals are obtained through a host computer, and the operation signals include throttle signals and brake signals.

[0068] Vehicle status signals are obtained through a preset vehicle model. These vehicle status signals include vehicle speed signal, vehicle attitude signal, battery status signal, gear signal, and power mode signal.

[0069] This embodiment simulates acceleration and braking operations during vehicle operation by inputting operation signals from the upper control unit. Since only the vehicle controller, engine controller, and motor controller actually exist in this embodiment, it is necessary to simulate the vehicle's driving state based on a preset vehicle model and obtain vehicle status signals from the model. Obtaining the operation signals and vehicle status signals provides the data foundation for subsequent calculations by the vehicle controller.

[0070] In one possible implementation, in step S2, the signal simulation model simulates and generates corresponding CAN signals and IO signals based on the input signal, including:

[0071] Based on the input signal, several VCU sensor signals, several ECM sensor signals, and several MCU sensor signals are generated through a preset IO model, which serve as the several IO signals;

[0072] Based on the input signal, several preset residual bus simulation signals and several real-time residual bus simulation signals are generated through a preset CAN bus model as the several CAN signals, wherein the real-time residual bus simulation signals are generated in real time by a preset vehicle model.

[0073] This application provides a method for signal simulation generation. Since the acquired input signals cannot be directly recognized by the vehicle controller, they need to be converted to simulate and generate several I / O signals and CAN signals. The I / O signals are mainly sensor signals, such as throttle opening and brake switch of the VCU, oxygen sensor, intake air pressure, oil and water temperature, and ambient temperature of the ECM, and temperature and resolver of the MCU. The CAN signals are mainly residual bus simulation signals; some are set by the tester, such as ignition key position, gear, and vehicle mode, while others are generated in real-time based on calculations from the vehicle model, such as vehicle speed, lateral acceleration, and yaw rate. By generating several I / O signals and several CAN signals, the controller under test can achieve closed-loop control in a simulation environment, improving the accuracy of drive controller interaction testing.

[0074] In one possible implementation, in step S4, the engine controller and the motor controller output response signals, including:

[0075] The engine controller generates corresponding fuel injection actuator signals and ignition actuator signals based on the torque request message, as the response signals;

[0076] The motor controller generates a corresponding PWM drive actuator signal based on the torque request message, which serves as the response signal.

[0077] Furthermore, after the engine controller and the motor controller receive the torque request message, the engine controller and the motor controller perform data interaction, including:

[0078] The engine controller receives a fault light illumination request signal sent by the motor controller;

[0079] The engine controller sends engine start status, speed, and fault information to the motor controller.

[0080] In this embodiment, the engine controller and motor controller each generate different response signals based on the simulated driving environment and the torque request message from the vehicle controller. These response signals are then collected and compared with preset output results to complete the interaction test of the drive controllers. Furthermore, after receiving the torque request message, the engine controller and motor controller perform several data interactions, more realistically simulating the data interaction scenario during actual vehicle operation. This achieves data linkage between different drive controllers under the test environment. Compared to existing single-drive controller testing methods, this embodiment effectively captures potential problems in the data interaction of various drive controllers, further improving the accuracy of drive controller interaction testing.

[0081] In one possible implementation, step S5, comparing the plurality of response signals with a preset output result to determine whether the tested function of the drive control system is normal, includes:

[0082] Calculate the first time difference between the signal received by the vehicle controller and the response signal output by the engine controller;

[0083] Calculate the second time difference between the signal received by the vehicle controller and the response signal output by the motor controller;

[0084] Calculate the third time difference between the output response signal of the engine controller and the output response signal of the motor controller;

[0085] The first time difference, the second time difference, and the third time difference are compared with preset output results to determine whether the torque coordination control function between the vehicle controller, the engine controller, and the motor controller is normal.

[0086] In this embodiment of the application, the first time difference, the second time difference, and the third time difference are obtained by recording the time difference between the vehicle controller receiving the input signal and the engine controller and the motor controller outputting the signal. Each time difference is compared with the preset output result to verify whether the real-time performance of the actual vehicle torque coordinated control meets the preset requirements and to determine whether the functional logic strategy of the drive control system is normal.

[0087] In addition to testing the interaction functions of the three controllers, the embodiments of this application can also test the interaction functions between two controllers, such as the high-voltage system power-on / off control and anti-shake control of the interaction between VCU and MCU, and the engine start-stop control and high-pressure fuel tank control of the interaction between VCU and ECM.

[0088] Furthermore, the interaction testing method also includes:

[0089] The aforementioned response signals are input to a preset vehicle model, so that the vehicle model updates its current vehicle state based on the aforementioned response signals, thereby generating a corresponding updated vehicle state signal.

[0090] In this embodiment, after the engine controller and motor controller generate response signals, each response signal is further input to the vehicle model to update the current vehicle state and provide a data basis for the next input of the vehicle controller. This realizes the cyclical data interaction and data conversion between the virtual vehicle model and the real drive controllers, providing testers with an efficient automated testing environment. It can realize automated testing of the hybrid drive controller interaction function with higher efficiency than manual testing of real vehicles, and improve the efficiency of drive controller interaction testing.

[0091] In a preferred embodiment, an interactive testing device for a hybrid vehicle drive controller is provided to implement the interactive testing method proposed in the embodiments of this application, such as... Figure 5 As shown, it includes both software and hardware systems.

[0092] The hardware system includes a host computer, fiber optic cable, real-time system, I / O harness, CAN bus, power supply lines, and the controller under test (DUT). The real-time system consists of a real-time processor, a programmable power supply, I / O boards, and a CAN bus board. The programmable power supply, I / O boards, and CAN bus board of the real-time system are connected to the power interface, sensor / actuator interface, and CAN bus interface of the DUT, respectively. The connection method between the CAN bus board and the DUT's CAN bus interface requires the CAN bus architecture of the vehicle model. The host computer communicates with the real-time system via fiber optic cable.

[0093] The software system includes a host computer interface, an I / O model, a CAN bus model, and a vehicle dynamics model. The I / O model is used to set the signal parameters of each channel on the I / O board, which must be consistent with the sensor / actuator interface signal parameters of the controller under test (DUT), such as analog signals, digital signals, or other special signals. The CAN bus model is used to configure the CAN bus board, import the DBC file (CAN bus database file) of the DUT, and establish a CAN network environment consistent with the actual vehicle. The CAN signals emitted by the vehicle controller, engine controller, and motor controller are the actual signals emitted by the controllers, while the CAN signals of other controllers are simulated by the CAN bus board. The vehicle dynamics model (referred to as the vehicle model) is used to simulate the physical environment of the drive control system during operation, including the driver, road scene, engine, motor, and vehicle. The host computer interface displays the actuator signals and CAN signals of the DUT acquired by the real-time system, as well as the power values, sensor signals, and residual CAN bus signals output by the real-time control system to the DUT. The specific steps for testing using the interactive testing device are as follows:

[0094] 1) Set up the hardware system. Follow the instructions... Figure 4 The hardware system solution connects the vehicle controller, motor controller, engine controller and real-time system, and the host computer and real-time system are connected via optical fiber.

[0095] 2) Configure the I / O model. Configure the I / O model according to the interface specification of the controller under test, and ensure that the parameters of each channel connecting the I / O board to the controller under test are correct.

[0096] 3) Configure the CAN bus model. Configure the CAN bus model according to the communication matrix and CAN bus architecture, import the DBC file, and the CAN signals issued by the vehicle controller, engine controller and motor controller are the actual signals issued by the controller, while the CAN signals of other controllers are simulated by the CAN bus board.

[0097] 4) Debug the dynamics model. Prepare the road scenarios and driver models to be verified in the vehicle dynamics model, such as highways, urban roads, slippery surfaces, curves, etc. Configure the vehicle dynamics model according to the engine, motor, and vehicle parameters to ensure that the simulated vehicle model is close to the real vehicle.

[0098] 5) Design the host computer interface. The host computer interface should include all variables that need to be controlled and displayed, such as power control, sensor input interfaces, actuator feedback signals, and the display and control of CAN bus signals.

[0099] 6) Test execution. For example... Figure 4As shown, the tester sets vehicle status signals and driver operation signals through the host computer. The real-time system converts these input signals into IO signals, CAN signals, etc., and sends them to the vehicle controller. After processing, the vehicle controller outputs a torque request to the engine controller and motor controller via the CAN bus. After receiving the torque request command, the engine controller and motor controller process it and output torque response messages and actuator signals. The real-time system collects these output signals and displays them on the host computer. The tester observes whether the output signals meet the expected results of the test cases, thereby judging whether the functional design of the hybrid drive control system is correct.

[0100] Furthermore, such as Figure 6 As shown, the actuator signals output by the engine controller and motor controller can be further input to the engine model and motor model in the vehicle model, thereby jointly generating a torque signal. The vehicle model updates the current vehicle state based on the torque signal, and then generates the corresponding updated vehicle state signal, which is then input back to the real-time system, providing a data basis for the next test and improving the efficiency of drive controller interactive testing.

[0101] In summary, the technical solutions provided in this application have the following beneficial effects:

[0102] 1) The constructed drive controller interactive test environment includes real vehicle controllers, motor controllers and engine controllers. The power management and CAN network communication are closer to the working environment of the real vehicle drive control system than the controller unit test environment. The real-time performance of the power-on / off function and torque coordination function is also closer to that of the real vehicle.

[0103] 2) Before the prototype vehicle is manufactured, the built drive controller interactive test environment can be used to discover systemic interactive problems that could not be found in the actual vehicle in advance in the bench test environment, thus intercepting serious systemic problems in the component development stage.

[0104] 3) After-sales problems of drive control systems are usually systemic problems involving the interaction of multiple controllers. The constructed drive controller interaction test environment can reproduce complex after-sales problem scenarios, observe the communication timing of the vehicle controller, engine controller, and motor controller, and locate the problem to the specific controller, IO signal, or CAN message.

[0105] 4) It can achieve automated testing of the interactive functions of the hybrid drive controller, which is more efficient than manual testing of actual vehicles, and significantly shortens the testing time.

[0106] Example 2:

[0107] like Figure 7As shown, Embodiment 2 provides an interactive testing system for a hybrid vehicle drive controller, including a first acquisition module 10, a signal simulation module 20, a controller execution module 30, a second acquisition module 40, and a judgment module 50;

[0108] The first acquisition module 10 is used to acquire input signals, including vehicle status signals and operation signals.

[0109] The signal simulation module 20 is used to input the input signal to a preset signal simulation model, so that the signal simulation model simulates and generates a number of corresponding CAN signals and a number of IO signals according to the input signal.

[0110] The controller execution module 30 is used to input the plurality of CAN signals and the plurality of IO signals to the vehicle controller, so that the vehicle controller performs calculations on the plurality of CAN signals and the plurality of IO signals, generates corresponding torque request messages, and sends them to the engine controller and the motor controller respectively.

[0111] The second acquisition module 40 is used to acquire several response signals output by the engine controller and the motor controller;

[0112] The judgment module 50 is used to compare the plurality of response signals with preset output results, thereby determining whether the tested function of the drive control system is normal.

[0113] In one possible implementation, the first acquisition module 10 acquires the input signal, including:

[0114] The operation signals are obtained through a host computer, and the operation signals include throttle signals and brake signals.

[0115] Vehicle status signals are obtained through a preset vehicle model. These vehicle status signals include vehicle speed signal, vehicle attitude signal, battery status signal, gear signal, and power mode signal.

[0116] In one possible implementation, the signal simulation model simulates and generates corresponding CAN signals and IO signals based on the input signal, including:

[0117] Based on the input signal, several VCU sensor signals, several ECM sensor signals, and several MCU sensor signals are generated through a preset IO model, which serve as the several IO signals;

[0118] Based on the input signal, several preset residual bus simulation signals and several real-time residual bus simulation signals are generated through a preset CAN bus model as the several CAN signals, wherein the real-time residual bus simulation signals are generated in real time by a preset vehicle model.

[0119] In one possible implementation, the engine controller and the motor controller output response signals, including:

[0120] The engine controller generates corresponding fuel injection actuator signals and ignition actuator signals based on the torque request message, as the response signals;

[0121] The motor controller generates a corresponding PWM drive actuator signal based on the torque request message, which serves as the response signal.

[0122] Furthermore, after the engine controller and the motor controller receive the torque request message, the engine controller and the motor controller perform data interaction, including:

[0123] The engine controller receives a fault light illumination request signal sent by the motor controller;

[0124] The engine controller sends engine start status, speed, and fault information to the motor controller.

[0125] In one possible implementation, the judgment module 50 compares the plurality of response signals with preset output results to determine whether the tested function of the drive control system is normal, including:

[0126] Calculate the first time difference between the signal received by the vehicle controller and the response signal output by the engine controller;

[0127] Calculate the second time difference between the signal received by the vehicle controller and the response signal output by the motor controller;

[0128] Calculate the third time difference between the output response signal of the engine controller and the output response signal of the motor controller;

[0129] The first time difference, the second time difference, and the third time difference are compared with preset output results to determine whether the torque coordination control function between the vehicle controller, the engine controller, and the motor controller is normal.

[0130] In one possible implementation, the interactive testing system further includes an update module, which is used to input the plurality of response signals to a preset vehicle model, so that the vehicle model updates the current vehicle state according to the plurality of response signals, thereby generating a corresponding updated vehicle state signal.

[0131] This application provides an interactive testing system for hybrid vehicle drive controllers. It integrates a real vehicle controller, motor controller, and engine controller. By inputting simulated signals to the vehicle controller, it processes and responds to the vehicle controller's calculations, further interacting with the engine and motor controllers. Finally, by analyzing the response signals of the engine and motor controllers, it completes the overall interactive testing of each drive controller. This avoids the significant difference between the individual drive controller testing environment and the actual vehicle drive control system interaction testing environment in existing technologies. Furthermore, this application uses signal simulation models to generate simulated signals for other vehicle controllers to construct a complete vehicle testing environment. This allows for the early detection of systemic interaction problems that would otherwise only be apparent in a real vehicle, even before the prototype is manufactured. This intercepts serious systemic problems during the component development stage, improving the efficiency of vehicle manufacturing and design. Moreover, the simulated signal design allows testers to quickly adjust relevant simulation parameters as needed, significantly improving the efficiency of drive controller interactive testing compared to full physical testing.

[0132] For a more detailed explanation of the working principle and procedures of this embodiment, please refer to the relevant description in Embodiment 1.

[0133] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above descriptions are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. In particular, it should be noted that any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application for those skilled in the art.

Claims

1. A hybrid vehicle drive controller interactive test method, characterized by, The method comprises the following steps: acquiring input signals, the input signals comprising vehicle state signals and operation signals; inputting the input signals into a preset signal simulation model to make the signal simulation model simulate corresponding CAN signals and IO signals according to the input signals; inputting the CAN signals and the IO signals into a vehicle controller to make the vehicle controller perform operation processing on the CAN signals and the IO signals, generate corresponding torque request messages and send the torque request messages to an engine controller and a motor controller respectively; acquiring response signals output by the engine controller and the motor controller; comparing the response signals with preset output results to determine whether the measured functions of the drive control system are normal, comprising: calculating a first time difference between the vehicle controller receiving signals and the engine controller output response signals; calculating a second time difference between the vehicle controller receiving signals and the motor controller output response signals; calculating a third time difference between the engine controller output response signals and the motor controller output response signals; comparing the first time difference, the second time difference and the third time difference with the preset output results respectively to determine whether the torque cooperative control functions among the vehicle controller, the engine controller and the motor controller are normal. The method of acquiring input signals comprises:

2. The interactive test method of a hybrid vehicle drive controller according to claim 1, wherein, acquiring operation signals through a host computer, the operation signals comprising throttle signals and brake signals; acquiring vehicle state signals through a preset vehicle model, the vehicle state signals comprising vehicle speed signals, vehicle attitude signals, battery state signals, gear signals and power supply mode signals. The signal simulation model simulates corresponding CAN signals and IO signals according to the input signals, comprising:

3. The interactive test method of a hybrid vehicle drive controller according to claim 1, wherein generating a plurality of VCU sensor signals, a plurality of ECM sensor signals and a plurality of MCU sensor signals as the IO signals through a preset IO model according to the input signals; generating a plurality of preset residual bus simulation signals and a plurality of real-time residual bus simulation signals as the CAN signals through a preset CAN bus model according to the input signals, wherein the real-time residual bus simulation signals are generated in real time by a preset vehicle model. The engine controller and the motor controller output response signals, comprising:

4. The method of claim 1, wherein the method further comprises: the engine controller generates corresponding fuel injection actuator signals and ignition actuator signals as the response signals according to the torque request messages; the motor controller generates corresponding PWM drive actuator signals as the response signals according to the torque request messages. When the engine controller and the motor controller receive the torque request messages, the engine controller and the motor controller perform data interaction, comprising:

5. The interactive test method of a hybrid vehicle drive controller according to claim 4, wherein the engine controller acquires a fault light lighting request signal sent by the motor controller; the engine controller sends engine start state, speed and fault information to the motor controller. The interaction test method further comprises:

6. The interactive test method of a hybrid vehicle drive controller according to any one of claims 1 to 5, characterized in that, ​ The several response signals are input to a preset whole vehicle model, so that the whole vehicle model updates a current vehicle state according to the several response signals, and then generates corresponding updated vehicle state signals.

7. An interactive test system for a hybrid vehicle drive controller, the system comprising: The method comprises a first acquisition module, a signal simulation module, a controller execution module, a second acquisition module, and a judgment module. The first acquisition module is configured to acquire input signals, wherein the input signals comprise vehicle state signals and operation signals. The signal simulation module is configured to input the input signals to a preset signal simulation model, so that the signal simulation model simulates and generates corresponding several CAN signals and several IO signals according to the input signals. The controller execution module is configured to input the several CAN signals and the several IO signals to a whole vehicle controller, so that the whole vehicle controller performs operation processing on the several CAN signals and the several IO signals, generates corresponding torque request messages, and respectively sends the torque request messages to an engine controller and a motor controller. The second acquisition module is configured to acquire several response signals output by the engine controller and the motor controller. The judgment module is configured to compare the several response signals with preset output results, and then judge whether a measured function of a drive control system is normal, comprising: calculating a first time difference between a whole vehicle controller receiving signal and an engine controller output response signal; calculating a second time difference between the whole vehicle controller receiving signal and a motor controller output response signal; calculating a third time difference between the engine controller output response signal and the motor controller output response signal; comparing the first time difference, the second time difference, and the third time difference with preset output results respectively, and then judging whether a torque collaborative control function among the whole vehicle controller, the engine controller, and the motor controller is normal.

8. The hybrid vehicle drive controller interactive test system of claim 7, wherein, The signal simulation model simulates and generates corresponding several CAN signals and several IO signals according to the input signals, comprising: According to the input signals, several VCU sensor signals, several ECM sensor signals, and several MCU sensor signals are generated through a preset IO model as the several IO signals; According to the input signals, several preset residual bus simulation signals and several real-time residual bus simulation signals are generated through a preset CAN bus model as the several CAN signals, wherein the real-time residual bus simulation signals are generated in real time by a preset whole vehicle model.

9. The hybrid vehicle drive controller interactive test system of claim 7, wherein, The engine controller and the motor controller output response signals, comprising: The engine controller generates corresponding fuel injection executor signals and ignition executor signals as the response signals according to the torque request messages; The motor controller generates corresponding PWM drive executor signals as the response signals according to the torque request messages.

Images