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
User must know their motor type in order to run motor identification. For PMSM motor identification, set the following definition to PMSM motor type (MOTOR_Type_Pm) as shown below. This definition is in user.h:
#define USER_MOTOR_TYPE MOTOR_Type_Pm
If the wrong motor is selected, for example a PMSM when an ACIM motor is connected, the estimator will not be able to identify the correct parameters. Motor identitication cannot identify what type of motor is connected, instead it identifies the motor parameters. Having the correct motor definition specified is required, otherwise motor identification will not work.