5.3. Stopping¶
5.3.1. Overview¶
“Stopping” is the process of bringing the motor to a complete stop, after normal operation, with the intent of leaving the motor unpowered and at rest in the STOPPED state.
MCAF includes several different options for stopping which can be selected in the Customize page of motorBench® Development Suite:
Minimal-impact PWM (“open-loop” stopping or “coastdown”)
Closed-loop current
Closed-loop velocity
In each of these, operation in the STOPPING state continues until one of the following conditions is true:
something causes the motor to exit normal operation (example: a fault occurs, or an operator enters a test mode using real-time diagnostic tools)
the motor is requested to run again
a stop completion flag is set — this condition is determined differently for each of the different stopping methods.
5.3.2. Minimal-impact PWM¶
With minimal-impact PWM — also known as “open-loop” stopping or “coastdown” — the PWM outputs are changed to the minimal-impact state. This is essentially an open-circuit condition on the three-phase bridge; for bootstrap gate drives, the lower transistors are maintained at a low duty cycle to maintain charge in the bootstrap capacitors.
Current measurements may be lost, and sensorless estimators may not be able to provide valid estimates of commutation angle and motor velocity.
Stop completion: Because a velocity estimate may not be available, open-loop stopping waits for a fixed coastdown time interval \(t_{\rm coast}\), assuming that the initial velocity is the worst-case maximum (in case the angle estimator is wrong, or the system comes out of reset). At the end of the coastdown interval, the stop completion flag is set, when it is likely that motor velocity is below the coastdown speed threshold.
Under these conditions, the only torque acting on the motor is assumed to be from viscous damping \(B\) and friction \(T_{\mathrm{fr}}\) acting on the rotor inertia \(J\) so that the motor coasts down towards rest, as shown in Figure 5.54 and described in Equation 5.22:
This can be solved analytically for the mechanical velocity:
where \(\omega_i\) is the initial velocity, \(\omega_{\mathrm{fr}}=T_{\mathrm{fr}}/B\), and time constant \(\tau = J/B\).
The coastdown time \(t_{\mathrm{coast}}\) is estimated from Equation 5.23 to determine the time at which motor velocity \(\omega_m\) is below the coastdown speed threshold \(\omega_f\).
NOTE: Minimal-impact PWM should not be relied on under any the following conditions:
the motor has high inertia (can coast down for at least several seconds) and the motor parameters are uncertain
the motor is subject to regenerative torque from its environment that can maintain motor velocity (example: e-bikes, generators, fans subject to windmilling, etc.)
5.3.3. Closed-loop methods¶
Under closed-loop stopping, field-oriented current control is maintained, with PWM outputs continuing normal switch-mode operation. This allows sensorless estimators to continue operating, so that a velocity estimate is still available.
Stop completion: The stop completion flag is set when the motor velocity has remained below a speed threshold for a minimum time interval.
NOTE: Closed-loop stopping methods should only be used with estimators that are able to maintain velocity estimates below the stopping threshold. (ZS/MT and QEI are good examples. The AN1292 PLL may be able to maintain a velocity estimate, but use of closed-loop stopping should be checked carefully. The ATPLL is known to have stability issues operating at very low speeds.)
5.3.3.1. Closed-loop current¶
Under closed-loop current stopping, the motor current is commanded to zero. This allows the motor to coast down towards rest with similar dynamics as in the minimal-impact PWM case.
5.3.3.2. Closed-loop velocity¶
Under closed-loop velocity stopping, the outer loop is commanded to zero velocity. This will bring the motor to rest very quickly, but also regenerates energy back onto the DC link.
NOTE: Closed-loop velocity control should only be when there is a reliable path for the regenerated energy to flow — for example, a shunt voltage regulator or a battery connected to the DC link.
5.3.4. Implementation notes¶
Support for closed-loop methods was added in MCAF R7.