• State
  • Locked Locked
  • Replies 13 replies
  • Subscribers 83 subscribers
  • Views 2060 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Enabling PowerWarp for AC Induction Motors

ChrisClearman
Guru** 119680 points

Other Parts Discussed in Thread: MOTORWARE

PowerWarp is an incredbile technology that dramatically reduces the power consumption of induction motors during their operation.  For dynamic applications, especially those that often run at only partial load / low torque output requirements (ventilation fans, traction machines) induction motors can now be even more efficient, practical, and offer a lower cost / longer lifetime alternative to rare earth permanent magnet machines.

The InstaSPIN-FOC GUI that comes with the kits does allow for enabling of PowerWarp for demonstration, but as we have communicated we recommend moving to the MotorWare projects as soon as possible.  Unfortunately, with the first release of MotorWare (1_01_00_05) the lab (proj_lab08) that demonstrates PowerWarp was not yet included.

If you would like to enable PowerWarp

1. First, check if there is an update to MotorWare that includes proj_lab08

2. If not yet, I have updated proj_lab09 with the necessary function call that allows you to toggle the PowerWarp function (Flag_enableEpl)

simply copy the 3 attached files: main.h, proj_lab09.c, proj_lab09.js into your latest copy of MotorWare, ex: C:\ti\motorware\motorware_1_01_00_05\sw\solutions\instaspin_foc\src

Build and load proj_lab09 (making sure you take the proper steps regarding Motor ID vs. user.h params and ReCal of Rs and Offsets) and you will now have

gMotorVars.Flag_enableEpl

which is set to 0 when disabled and 1 when you want to enable on the fly.

This project also allows you - like the GUI - to change the overmodulation index (set initially as full modulation 2.0) by changing

gMotorVars.OverModulation

  • 0 in reply to ChrisClearman
    TI__Guru** 119680 points

    expressions window java script

    proj_lab09.js

     

    proj_lab09.js
  • 0
    Expert 1830 points

    hi,

    i have a question.

    i am using a InstaSPINTM- FOC GUI in hvkit_rev1p1 with TMS320F28069MISO control card.

    when using gui, after identification, i set 1500rpm fo speed but, estimated speed didn't receive to destination(1500rpm) and stop in 1200 rpm. addition, Id was so high and motor made so much noise.

    when enabling the POWERWARP, speed reached to destination, Id dropped down and the noise was gone.

    the question is:

    "is this natural? or i this is a problem?"

    how can i correct it?

    this is two pictures of process, with and without POWERWARP.

    thanks.

  • 0 in reply to msadegh agha
    TI__Guru** 119680 points

    the GUI uses a fixed binary project that uses a very early version of MotorWare that doesn't have some of the enhancements we've made for ACI motors.

    I suggest downloading MotorWare and working through the labs. Also see the ACI ID section in SPRUHJ1.

    I will warn you that the induction motor ID is not "insta" for many motors. In some cases it takes some "tweaking" of the variables to get things to work and in other cases (usually high current ACI) it won't properly ID at all.

  • 0 in reply to ChrisClearman
    Expert 1830 points

    hi ChrisClearman,

    i have done what you said. i ran my ACIM motor with debugging process in new Motorware(motorware_1_01_00_14) and the results become worst.

    when i'am using the GUI with a fixed binary project, the speed without using PowerWarp reach to 1200rpm but in new project of motorware_1_01_00_14(proj_lab05b and proj_lab010a), the speed without using PowerWarp reach to 600rpm.

    in both cases, using PowerWarp convay motor speed to 1500 rpm.

    by the way i'm using a 2 pair poles, 1500 rpm(max), 220v ACIM motor. this is my user.h file:     8156.user.h

    and also this is two pictures of my results:

    5873.Desktop.rar

  • 0 in reply to msadegh agha
    TI__Guru** 119680 points
    what are the motor parameters you identified using MotorWare.
    best to just drag & drop the completed user.h file
  • 0 in reply to ChrisClearman
    Expert 1830 points

    2742.user.h

    this is my user.h file

  • 0 in reply to msadegh agha
    TI__Guru** 119680 points
    try raising this
    #define USER_MOTOR_MAX_CURRENT (7.0)

    the parameters don't look to bad at first glance, but it's clear from the currents that there is something wrong with the feedback from the estimator, which would most likely mean the parameters are incorrect.

    what parameters did you ID using the GUI?

    I've tagged this for one of our other experts to look at also.
  • 0 in reply to ChrisClearman
    Expert 1830 points

    this is my parameter in GUI(just like user.h):

    by the way, i set the USER_MOTOR_MAX_CURRENT  to 7, and checked with both GUI and debug part in ccs,

    the result was as same as usual.

  • 0 in reply to msadegh agha
    TI__Expert 5180 points

    The parameter Ind Est Current (A) only applies to PMSM motors. For ACIM, please set that value to zero.

    Have you tried loading your own parameters and running other labs that enable PowerWarp? In other words, have you tried without the GUI?

    -Jorge

  • 0 in reply to Jorge Zambada
    Expert 1830 points
    yes, i tied that.
    i used proj_lab05b, proj_lab10a but they are worst than gui.
    in this labs the speed stops at 600 rpm without PowerWarp but in gui speed stops at 1200rpm
  • 0
    Expert 1830 points

    hi, 

    i used the gui with params shown in below pic:

    the result was fantastic without powerwarp. the motor spin in real speed and the estimation was correct.

    but when i set this parameter in user.h and use debug in CCS, the result was awful. the speed of motor without powerwarp was not the speed that i set.

    what is the diffrence? you said the primitive .out file with gui is old and using new proj from motorware could solve the problem, but the result was inverse.

    is there a parameter in user.h that most set and differ from primitive .out file? 

    also this is the full picture:

  • 0 in reply to msadegh agha
    TI__Guru** 119680 points
    the GUI is giving you false hope because it appears to be running "better" but you will note that some of the parameters it identified are obviously incorrect. The Rr value will never be 0.01 when the Rs is 3.47, that's your first clue. Second, the flux value is much too low for a 220V high voltage 50 Hz motor.

    if you tried to load this motor I'm sure you would see that it doesn't produce very much torque.


    you need to abandon this GUI and just use MotorWare proj_lab02b. Hopefully Jorge will be able to give you some additional pointers to get the parameters ID'd correctly.