TMS320F28069M: GUI is not working for Insta-MOTION

How are you measuring the phase current? You could take an external measurement using some tools to determine the speed of rotation. These often work on the principle of measuring the frequency of rotation using a laser. You could also use a physical sensor such as an encoder to determine the speed of rotation

Sean

Hello Sean.

I used an external tool (current probe) to measure the phase currents because motor has no encoder.

Since the phase current rotation frequency is unmatched with what the GUI displays, I thought my way of confirmation is incorrect and TI has probably a special way of confirming it.

Do you have other advice?

By the way I followed the sequence below and updated the corresponding define values in user.j1.h.

     proj_lab02c           ⇒      proj_lab05c            ⇒       proj_lab05d    ⇒    proj_lab05e

(for motor parameter  >  motor inertia & friction  >  spintac control  >  spintac control tuning)

Thank you  very much.

Best regards,

Muriel

What are your values for the identified motor parameters? It seems there may be some issue with the motor ID in lab2c

Sean

Hello Sean,

Sorry for my late reply.

I think you're right. There's something strange during my FOC implementation. But I am not sure if there's something in my procedure.

I compared the results of proj_lab02c using boards F28027F & F28069M and the same motor.
FOC:
F28069M F28027F
spd_ref = 40,000rpm spd_ref = 40,000rpm
spd_fdbk = 28,000rpm spd_fdbk = 40,000rpm approx.

Also, using F28069M & proj_lab02c, unlike F28027F, motor ID becomes hard to do(it takes a lot of trials and motor ID parameters,Lsd&Lsq&Rotor FLux, identified is higher).

What do you think is my lacking?

I am sorry to bother you, but thank you for your understanding.

Best regards,
Muriel

What are the identified values? Which estimator state is experiencing this issue? You may need to increase some #defines in the user.h depending on which state you are having issues at

Sean