Hello,
From your stmcx file, I noticed that you do not use any overcurrent protection.
It is recommended to connect EN_FAULT of STSPIN233 to a BKIN input of the PWM timer.
A schematic example can be found here :
https://www.st.com/content/st_com/en/products/ecosystems/stm32-open-development-environment/stm32-nucleo-expansion-boards/stm32-ode-move-actuate-hw/x-nucleo-ihm17m1.html#cad-resources
Without this connection, you will never see an overcurrent error reported to the monitor tool.
When you write "However, 4 time in 100 it will just slightly budge then stop."
It means that startup parameters are not able to spin the motor in open loop mode. During the revup phase, the algo start spinning your motor without any knowledge of the real position of the rotor. Once the motor reaches a certain speed, the algo closes the loop and switch to the sensor less observer. The observer needs a minimum speed to be able to track the rotor position and control your motor accordingly.
The reason why no errors are reported is under study, we are facing some difficulties to reproduce this behavior right now.
In your rev-up parameters, the values you enter is very closed to your motor nominal current, I would advise you to try to lower the current during your rev-up phase. We have already noticed that starting with a to strong current can prevent the motor to start spinning.
Regards
Cedric
