Development of electric vehicle controller technology

In the traditional control unit development process, usually the serial development mode, that is, according to the application needs, put forward the requirements of the system and the corresponding function definition, then hardware design, using assembly language or C language for hardware-oriented coding, and then complete the hardware and software and external interface integration, and finally the system test calibration.

The whole vehicle controller, especially the pure electric vehicle controller, has the development process of V-mode. The continuous development of hardware and software technology provides a powerful tool for parallel development.

The first step, functional definition and off-line emulation. Firstly, the function of the controller should be defined according to the application, which provides the foundation for the hardware design, then the simulation model of the whole control system is established and the off-line simulation is carried out, and the control strategy is designed and validated by the software simulation method.

Second step, rapid controller prototyping and hardware development. The controller model is taken out from the MATLAB simulation model of the control system, and the physical connection with the controlled object is realized by combining the DSpace physical interface module, then the DSpace is provided with the compiler tool to generate the executable program and download to the DSpace. DSpace at this time as a substitute for the target controller, it is easy to realize the control parameter on-line debugging and control logic regulation.

While off-line simulation and rapid control of its prototype, according to the function of the controller design, synchronous completion of the hardware function analysis and the corresponding hardware design, production, and according to the results of software simulation to improve and modify the hardware.

The third step is to generate the target code. The rapid control prototype has basically generated a satisfactory control strategy, the hardware design has also formed the final physical carrier ECU's bottom drive software, both integrated to generate target code to download to the ECU.

The fourth step, pure electric vehicle hardware in the loop simulation, the purpose is to verify its electric vehicle controller ECU function of electronic control unit. In this link, in addition to the electronic control unit is a real part, some of the controlled objects can also be real parts.

The fifth step, debugging and calibration. The ECU which is verified by hardware-exchange simulation is linked to the completely true controlled object, and the actual running test and debugging are carried out.

Category editors

The electric vehicle controller is divided into two kinds from the structure, we call it the separation type and the integral type.

1, separation: the so-called separation, refers to the controller and display part of the separation. The latter is installed on the handlebar, the controller body is hidden in the car body box or electric box, not exposed outside. This way the controller and the power supply, motor line between the distance shortened, the body appearance appears concise.

2. All-in-one: The control part is integrated with the display part and is packed in an exquisite special plastic box. The box is installed in the center of the Handlebar, the box panel is opened with a number of small holes, aperture 4-5mm, external transparent waterproof film. The hole is provided with a light-emitting diode to indicate the speed, power supply and battery remaining charge.