- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software:
Hello,
Is there a new tuning guide for the latest MSPM0 Sensorless FOC GUI?
https://dev.ti.com/gallery/view/TIMSPGC/MSPM0G-SENSORLESS_FOC/ver/2.0.0/
It looks like the linked tuning guide is for a different version of the GUI. I'm currently using the DRV8323RS boosterpack and the LVSERVOMTR which should be what's been tuned already in the system. I have everything powered up and there are no faults, but when I set a speed reference the motor doesn't start spinning. If I try to set the GUI motor state to something like "MOTOR_ALIGN", it goes right back to MOTOR_IDLE.
This GUI is definitely not user friendly and there's no steps on how to actually start the motor in the GUI.
Also, in the hardware setup guide for the Sensorless FOC Middleware, you should mention that if you want to use the backchannel UART to communicate with the GUI, you need to have UART3 wired to the XDS110 UART TX and RX pins.
Basically as it stands nobody outside whoever wrote this thing would be able to use it so any help here would be appreciated!
Munan
Hi Munan,
s, but when I set a speed reference the motor doesn't start spinning.
I assume the tuning guide gives the example of how to spin the motor, would you set speedinput rather than speedreference?
B.R.
Sal
Hi Sal,
Ok, I see what the issue was, the speed input is a (signed?) int16 value and the speed I was putting in was like "10" so this was too low of a value for the motor to do anything.
I also notice that at low speeds (in this case 1000/32767) the motor rotor is stuttery and doesn't spin smoothly.
What version of GUI is documented in the app note? I don't have those three tabs at the top I just have 3 columns of values:
It seems like if the motor stalls or loses sync the algorithm doesn't try to restart the motor, is that expected?
Finally, I'm still not seeing any values update from the MSP side of things, it looks like the GUI values for things like bus voltage and motor state don't update.
Munan
Hi Sal,
I followed the link in the Tuning Guide and it took me to yet another GUI and this one looks like what you're showing. This was not the GUI I originally found.
Also, just FYI, nowhere on the motor control middleware page does it link to the correct GUI. In fact the motor control middleware documentation barely mentions the GUI:
If you think about this from a discoverability point of view I don't think the way this is set up makes for a good user experience.
You need to have an actual getting started guide that goes through ALL of the required materials including the GUI and it needs to mention all of the hardware modifications needed (like rerouting UART3). And it needs to also walk through the steps of how to hook up the motor and how to start it using the GUI.
Right now I think this is quite messy and I wouldn't hand this over to a customer to try and get started on their own.
Munan
Ok, I see what the issue was, the speed input is a (signed?) int16 value and the speed I was putting in was like "10" so this was too low of a value for the motor to do anything.
It is a unsigned 15 bit value, according to the tuning guide register map. The direction is not controlled by speedinput, while use DIR_input to set the spinning direction.
I also notice that at low speeds (in this case 1000/32767) the motor rotor is stuttery and doesn't spin smoothly.
It is a sensorless solution, so low speed is not good option, and not supposed to stable running. Higher than 20% is better, which means set it as 32767 * 0.2 = 6,553, or higher.
What version of GUI is documented in the app note? I don't have those three tabs at the top I just have 3 columns of values:
As you know, the application version will be little lately than the GUI, you could access the correspondingly GUI in the tuning guide link.
It seems like if the motor stalls or loses sync the algorithm doesn't try to restart the motor, is that expected?
Yes, I think the demo project not include this function. While it can be implemented in their application code. We give the partial source code opened in the SDK.
Finally, I'm still not seeing any values update from the MSP side of things, it looks like the GUI values for things like bus voltage and motor state don't update.
Yes, SDK user guide document will guide user to tuning guide and get the GUI link.
B.R.
Sal
