ACIM Identification using InstaSPIN GUI

Anantha,

This is a good place to discuss some items.

Motor ID
    a. It is critical for Motor ID (and run-time control) that you have proper scaling/resolution of current and voltage (most critical) signals.  It is impossible to provide a universal hardware and software solution that works as-is out of the box for all the motors that could possibly be attached.  So step 1 is understanding if one of the three kits will give you enough resolution. For example, using a 12V motor on the DRV8312 kit is often unsuccessful because the voltage scaling is over 66V so the feedback drops into the noise (especially on the low Bemf motors typically designed for 12V). It is recommended to make changes to the sense feedback circuits on the TI kits (or build your own hardware) to properly test performance for your motor.  Of course, for best low and high speed operation you also need to focus on good layout design of the feedback path to insure lowest noise / cross-talk possible during sampling.

    b. The GUI project is several projects smashed together to support three pieces of hardware and software, and we don't even give you access to change any of the SW scaling or PWM rates like you can in the MotorWare based projects.  So if the standard software from the GUI doesn't work you need to realize that you need to move to the C code projects and not try to do everything just with the GUI.  It is recommended to move to the CCS projects as soon as you can. 

   c. For induction motors the Motor ID feature is not working universally.  We are working on improving this but it is a known issue, especially for low voltage / high current or higher power induction machines.  A portion of this is due to scaling effects as noted in a.) but there are also some additional items that we need to improve during the identification process.  It has to do with some default scaling values in the Flux estimation and the current controllers during ID only.  We are working on this and will provide an update when we have a robust solution.

  d. The good news is that this issue is just with the Motor ID feature. Once the values are known and loaded through user.h the FAST observer works properly.

   e. Yes, there are some tricks for Motor ID with both PM and induction motors to successfully ID and get InstaSPIN-FOC running when the motor either can not be disengaged from a load/linkage or a locked rotor test can not be performed.  I have documented an example for the PM machine here, and as we update the Induction machine we will post something here as often with a fan you don't want the user to stick his hand in the blades.  For the induction machine it's a similar approach where you use Rs (take a guess on Rr) and Lhf to get the motor started and converge.

Thank you Mr. ChrisClearman for the detailed explanation of the process of identification.  We are experimenting with high voltage hvmtrkit-r1p1 kit and as you say, we start building CCS projects apart from using GUI.

regards

anantha

Also, make sure you review the UG section on Motor ID, chapter 6, section 6.7 for induction motors.

Dear Chris,

I'm also planning to make a produce of identifying the parameters of my ACIM motor. Because my ACIM motor don't have enough the parameters get from its datasheet or name place, so that I want to know:
1. How good is for the "proper scaling/resolution of current and voltage (most critical) signals" to available for indetification of ACIM motor?

2. How is the reliability of the ACIM ID motor in Motorware 16 now? Whether I can believe in its qualification to apply for industrial motors or not? Because in fact I met many motor without the name plate attached to it.

3. Which document can I read to understand the Motor ID of Motorware?

4. The inputs for FAST are I_alpha, I_beta, V_alpha, V_beta, and V_dcBus MUST BE in PU, aren't they?

5. If I want to modify the code of Lab11a, b to prepare for Motor ID, what should I do?

Thanks