SPRUHJ1I January 2013 – October 2021 TMS320F2802-Q1 , TMS320F28026-Q1 , TMS320F28026F , TMS320F28027-Q1 , TMS320F28027F , TMS320F28027F-Q1 , TMS320F28052-Q1 , TMS320F28052F , TMS320F28052F-Q1 , TMS320F28052M , TMS320F28052M-Q1 , TMS320F28054-Q1 , TMS320F28054F , TMS320F28054F-Q1 , TMS320F28054M , TMS320F28054M-Q1 , TMS320F2806-Q1 , TMS320F28062-Q1 , TMS320F28062F , TMS320F28062F-Q1 , TMS320F28068F , TMS320F28068M , TMS320F28069-Q1 , TMS320F28069F , TMS320F28069F-Q1 , TMS320F28069M , TMS320F28069M-Q1
This section covers the recalibration of PMSM and ACIM motors when motor parameters have been provided through a header file. The exact state machine used in Section 7.8.1 applies to this section.
Prior to enabling the controller, the code knows that a motor recalibration will be done using motor parameters from user.h when this condition is true:
if(CTRL_getFlag_enableUserMotorParams(ctrlHandle) == TRUE)
The same state, state transition conditions and functionality as described in Section 7.8.1 for Recalibration after Full Identification are also used for this case, recalibration using parameters from user.h.