Creating a High-Fidelity Model of an Electric Motor for Control System Design and Verification

By Brad Hieb, MathWorks

An accurate plant model is the linchpin of control system development using Model-Based Design. With a well-constructed plant model, engineers can verify the functionality of their control system, conduct closed-loop model-in-the-loop tests, tune gains via simulation, optimize the design, and run what-if analyses that would be difficult or risky to do on the actual plant.

Despite these advantages, engineers are sometimes reluctant to commit the time and resources required to create and validate a plant model. Concerns include how much time it will take to run a simulation, how much domain and tool knowledge will be required to build and validate the model, and what type of equipment will be needed to acquire hardware test data for building and validating the model.

This article describes a workflow for creating a permanent magnet synchronous machine (PMSM) plant model using MATLAB® and Simulink® and commonly available lab equipment. The workflow involves three steps:

  • Execute tests
  • Identify model parameters from test data
  • Verify parameters via simulation

We used the plant model to build and tune a closed-loop PMSM control system model. We ran step response and coast-down tests using the controller model in simulation and on hardware using an xPC Target™ turnkey real-time testing system. We found close agreement between the simulation and hardware results, with normalized root mean square deviation (NRMSD) below 2% for key signals such as rotor velocity and motor phase currents (Figure 1).

Figure 1. Comparison of simulation results with hardware results for rotor velocity and phase current.
Figure 1. Comparison of simulation results (blue) with hardware results (red) for rotor velocity (left) and phase current (right).

The Plant Model and Its Parameters

The PMSM plant model, developed with SimPowerSystems™, includes the motor and a load—in this example, an acrylic disc. The model has nine parameters that define its behavior: one (disc inertia) associated with the load and eight associated with the motor (Figure 2).

Figure 2. Simulink model of a PMSM.
Figure 2. Simulink model of a PMSM.

We conducted five tests to characterize these parameters: the bifilar pendulum test, the back EMF test, the friction test, the coast-down test, and the DC voltage step test (Table 1). In this article, we will focus on the coast-down test and the DC voltage step tests. These tests demonstrate progressively more sophisticated methods of parameter identification, and illustrate extracting parameter values via curve fitting and parameter estimation, respectively.

TestParameters IdentifiedIdentification Method
Bifilar pendulum testDisk inertia (Hd)Calculation
Back EMF testNumber of poles (P)
Flux linkage constant (Apm)
Torque constant (Kt)
Calculation
Friction testViscous damping coefficient (b)
Coulomb friction (J0)
Curve fitting
Coast-down testRotor inertia (H)Curve fitting
DC voltage step testResistance (R)
Inductance (L)
Parameter estimation
Table 1. Model parameters and the tests conducted to characterize them.

For each test, we describe the test setup and then explain how we conducted the test, acquired the data, extracted the parameter value, and verified it.

Characterizing Rotor Inertia with the Coast-Down Test

To characterize the rotor inertia (H) we spin the rotor up to an initial speed (ωr0) and measure the rotational speed (ω) as the rotor coasts to a stop. Using this measured result, the rotor inertia can be identified by curve fitting the equation for ωr to the measured rotational speed during the period of time when the motor is coasting to a stop.

The differential equation [1] describes the mechanical behavior of the motor. The coast-down test is set up so that the load torque (Tload) is always 0. Once the motor is up to an initial, steady-state speed, the motor is turned off, so that the electromagnetic driving torque (Tem) is also 0. Under these conditions the solution to [1] is given by the equation for ωr [2], where

    ωr is the rotational speed of the rotor shaft

    ωr0 is the initial rotational speed of the rotor shaft

    J0 and b are the Coulomb friction and viscous damping coefficient, respectively, characterized from a
    separate friction test

    Tem is the electromagnetic driving torque (0 during this test)

    Tload is the load torque (0 during this test)

PMSM Equations

Conducting the Test and Acquiring the Data

In the lab we created an open-loop Simulink test model to drive the motor to an initial speed of 150 radians per second, at which time the motor drive was turned off and the rotor coasted to a stop. Throughout the test the model captured the output of the rotational speed sensor. Using Simulink Coder™ and xPC Target, we deployed this model to an xPC Target turnkey real-time system. We executed the model using xPC Target, and imported the rotor speed data into MATLAB for analysis.

Extracting and Verifying the Parameter Values

After running the tests, we plotted the measured speed data in MATLAB and used Curve Fitting Toolbox™ to fit equation [2] for the rotor angular velocity (ωr) to the measured speed data while the rotor was coasting to a halt. Using the value of H from the curve fit, we evaluated equation [2] from the point at which the motor started coasting and plotted the results with the original test data (Figure 3). As Figure 3 shows, equation [2] with the value of H from the curve fit closely predicts the motor speed during the coast-down test.

Figure 3. Plot of rotor velocity during the coast down test.
Figure 3. Plot of rotor velocity during the coast-down test. Blue = hardware test results; red = curve fitting results.

We used a model to verify our parameter identification result. Using the rotor inertia value obtained from the coast-down test (3.2177e-06 Kg m^2 in our PMSM model), we ran a simulation of the coast-down test in Simulink. We then compared and plotted the simulated results with the measured results (Figure 4). The results matched closely, with a normalized root mean square deviation (NRMSD) of about 2%.

Figure 4. Comparison of measured rotor velocity and simulated rotor velocity.
Figure 4. Comparison of measured rotor velocity (red) and simulated rotor velocity (blue).

Characterizing Resistance and Inductance with the DC Voltage Step Test

In the DC voltage step test a DC voltage is applied across the motor phase A and phase B connections and the resulting current is measured. Electrically, under these conditions, a three-phase PMSM behaves like a circuit with two series resistors and two series inductors (Figure 5).

Figure 5. Equivalent electrical circuit for DC step test.
Figure 5. Equivalent electrical circuit for DC step test.

The measured current (i) is used to find the resistance and inductance parameter values. During the test the rotor is held motionless to avoid complicating the analysis with back EMF waveforms, which tend to oppose the current flow. To avoid burning out the motor with the rotor motionless, a current limiting resistor (Rlimit) is added and a step pulse rather than a steady DC voltage is used.

Conducting the Test and Acquiring the Data

We again used xPC Target and an xPC Target turnkey real-time system to conduct the test. In Simulink we developed a model that produced a series of 24-volt pulses roughly 2.5 milliseconds in duration. We deployed this model to our xPC Target system using Simulink Coder, and applied the voltage pulse across the phase A and phase B terminals of the PMSM. We measured the applied voltage and the current flowing through the motor using an oscilloscope, and using Instrument Control Toolbox™ we read the measured data into MATLAB, where we plotted the results (Figure 6).

Figure 6. Voltage and current for a pulse in the DC voltage step test.
Figure 6. Voltage (top) and current (bottom) for a pulse in the DC voltage step test.

Extracting and Verifying the Parameter Values

Extracting the phase resistance from the measured data required only the application of Ohm’s law (R = V/I) using the steady-state values for voltage and current. For the PMSM we calculated the resistance as 23.26 volts / 2.01 amps = 11.60 ohms. By subtracting 10 ohms (the value of the current limiting resistor), and dividing the result by 2 to account for the two-phase resistances in series, we calculated the motor phase resistance to be 0.8 ohms.

Characterizing the inductance required a more sophisticated approach. At first glance, it looks as if we could have used curve fitting, as we did when characterizing the rotor inertia. However, due to the internal resistance of the DC supply, the measured DC voltage decays from an initial value of 24 volts at the start of the test, when the current into the circuit is 0, to a steady-state value of 23.26 volts after the current is flowing in the circuit. Because the input voltage is not a pure step signal, the results from curve fitting the solution to the series RL circuit equation would not be accurate.

To overcome this difficulty we opted for a more robust approach using parameter estimation and Simulink Design Optimization™. The advantage of this approach is that it requires neither a pure step input nor curve fitting.

We modeled the motor’s equivalent series RL circuit with Simulink and Simscape™ (Figure 7). Simulink Design Optimization applied the measured voltage as an input to the model, and with the value of the limiting resistor (Rlimit) and the motor phase resistance (R_hat) already known, estimated the value of the inductance (L_hat) to make the current predicted by the model match the measured current data as closely as possible.

Figure 7. Simscape model of the motor’s equivalent circuit.
Figure 7. Simscape model of the motor’s equivalent circuit.

To verify the values that we had obtained for phase resistance (0.8 ohms) and inductance (1.15 millihenries), we plugged the values into our PMSM model and stimulated the model with the same input that we used to stimulate the actual motor. We compared the simulation results with our measured results (Figure 8). The results matched closely, with an NRMSD of about 3%.

Figure 8. Comparison of measured results with simulation results for voltage and current.
Figure 8. Comparison of measured results (blue) with simulation results (red) for voltage (top) and current (bottom).

Using the Plant Model to Design the Controller

After identifying and verifying all key parameters, our PMSM plant model was ready to use in the development of the motor controller. We used Simulink Design Optimization to tune the proportional and integral gains of the controller’s outer loop, the velocity regulator. We ran closed-loop simulations to verify the functionality of the controller model, and used Simulink Coder to generate code from the model, which we deployed to an xPC Target turnkey real-time target machine.

As a final controller verification step, we ran step response and coast-down simulations in Simulink and hardware tests using the deployed controller code on an xPC Target turnkey real-time system. We compared simulation and hardware test results for rotor velocity and phase current, and once again found close agreement between the model and the hardware, with NRMSD below 2% in both cases (Figure 9).

Figure 9. Comparison of simulation results with hardware results for rotor velocity and phase current.
Figure 9. Comparison of simulation results (blue) with hardware results (red) for rotor velocity (left) and phase current (right).

Summary

Development of the PMSM plant model highlighted two parameter identification tests. Data was acquired via a sensor for the coast-down test, and with Instrument Control Toolbox via an oscilloscope for the DC voltage step test. We extracted data via curve fitting for the coast-down test and parameter estimation for the DC voltage step test. We verified all parameter values by comparing simulation results against measured test data, which enabled us to produce a plant model that we could trust as we developed and tuned the controller.

All this work can be done early in the development process, well before embedded code is generated for the control system, enabling engineers to find and eliminate problems with the requirements and the design before hardware testing begins. These benefits typically far outweigh the costs associated with creating the plant model, particularly if the model can be reused on other projects.

We would like to acknowledge the contribution of Professor Heath Hofmann of the University of Michigan, who recommended test procedures for characterizing a PMSM and allowed us to use his lab facilities for the initial phase of this project.

Published 2013 - 92130v00

Receive the latest MATLAB and Simulink technical articles.

Related Resources

Latest Blogs