DRV8301-69M Kit not identifying the motor's parameters

Fahad,

1. you may need to use proj_lab02c to ID this motor since it may be low inductance. This lab implements some rescaling of variables to be able to ID the motor. However, you say the motor is only rated at 200 Hz...so that shouldn't be a low inductance motor...which brings me to:

2. you have a motor with rated current of 1.1A continuous and yet you are using hardware that measures 41.25A on hardware. That means that when LOADED you are only using the bottom 2.6% of your current scaling, and with no load you are pretty close to 0%.  This isn't going to give you good results at all.  I would recommend using an inverter like the BOOSTXL-DRV8301 or the DRV8312-69M-KIT with this motor. Performance will be much improved.

3. you have major user.h issues

#define USER_ADC_FULL_SCALE_CURRENT_A        (33.0)     // 82.5 drv8301_revd current scaling

you aren't allowed to change this variable unless you change the hardware scaling. This variable tells the software that when it sees 3.3V on the ADC it should translate that to (82.5 / 2) and 0.0V on the ADC should translate to (-82.5/2).  You have told the algorithm that your range is actually +/- 16.5A, which is completely incorrect.

#define USER_IQ_FULL_SCALE_CURRENT_A          (18.0)

this value should always be >= ADC_FULL_SCALE_CURRENT / 2.  So update to (42.0) after you fix above

#define USER_R_OVER_L_EST_FREQ_Hz (300)

for your motor you can reduce this to (100.0)

#define USER_MOTOR Anaheim_BLY172S

you have the default motor from the DRV8312 kit active. You need to follow the InstaSPIN_labs.pdf guide to set-up your own USER_MOTOR.  Though using this Anaheim motor to start should allow you to ID your motor w/o any problems because they have the same # of poles and similar current and frequency ratings.

Chris,

         Thanks for replying fast. I wanted to tell you that I did follow the labs and I finally got my motor to spin up to speed @ 3000 RPM. I pretty much got It working with lab 2a and now will continue with all the labs that follow. This motor is basically a test bench to implement FOC before I get the actual motor(Axial Flux PMSM) that my university's research lab is developing to use with the DRV8301-69M kit. I wanted to ask you a couple of questions before I proceed with the motorware labs.

1. You said that the HW is scaled to 41.25 A and I am only using the bottom 2.6% of the current scaling. If my motor is spinning under no-load conditions do you think that the performance is going to be affected at full-load given the same HW?

2. Is there any way that I can tune 'control timing' values within InstaSPIN-FOC/MOTION GUI as according to me, the only problem is the PWM frequency that keeps the GUI from properly identifying the motor.

By the way, I got to spin my motor using all the default values in user.h. All I had to do was set up  my own motor in the 'Motor and ID settings'

Thanks,

Fahad Raza

Fahad Raza said:

1. You said that the HW is scaled to 41.25 A and I am only using the bottom 2.6% of the current scaling. If my motor is spinning under no-load conditions do you think that the performance is going to be affected at full-load given the same HW?

Yes.  You should aim to maximize the resolution of the peak sensed signals to the HW sensing.  You are very far off today and will see much better performance with better HW.

Fahad Raza said:

2. Is there any way that I can tune 'control timing' values within InstaSPIN-FOC/MOTION GUI as according to me, the only problem is the PWM frequency that keeps the GUI from properly identifying the motor.

It's not your PWM frequency. It is the resolution of the sense signals.

You can change everything required if you use the MotorWare projects.  And then if you want a GUI to instrument this code you should use INSTASPINUNIVERSALGUI

Fahad Raza said:

By the way, I got to spin my motor using all the default values in user.h. All I had to do was set up  my own motor in the 'Motor and ID settings'

This is not surprising. As mentioned on one of your other posts I said I expected this to work just fine.