Part Number: LAUNCHXL-F28379D
Hi Team,
Follow up with the related thread:
The estimator doesn't seem to be working properly, what can I do to fix it?
Best Regards,
Ben
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.
Part Number: LAUNCHXL-F28379D
Hi Team,
Follow up with the related thread:
The estimator doesn't seem to be working properly, what can I do to fix it?
Best Regards,
Ben
Hi Ben,
Could you share the link of the thread you mentioned?
What estimator are they using? FAST or eSMO? How did they test the estimator?
Thanks,
Jiaxin
Hi Ben,
Okay, I see. Thank you. Was customer running with their own motor? Can they confirm their motor parameters are accurate?
There is another finding that you mentioned in a previous thread that you have to change the "obj->oneOverDcBus_invV" from the estimator output to ADC feedback in level 2 for the motor to operate, but level 2 always uses the actual ADC data as shown below.
![]()
To debug the estimator, it would be better to make sure the estimator functions well in level 2 when the motor is running in open loop control.
Thanks,
Jiaxin
HI Jiaxin,
Sorry for the late reply.
At present, the motor used is a motor from Tongchuan, and under the level 2 construction, the display estimate has always been 31415.9277
Best Regards,
Ben
Hi Ben,
No worry. Since customer is using a custom motor, can they confirm the motor parameters defined in "user_mtr.h" are accurate? If they are not sure about these, they can run the motor identification first.
Thanks,
Jiaxin