cancel
Showing results for 
Search instead for 
Did you mean: 

[ST MCSDK5] The motor does not run in encoder mode.

PolarBearINBrown
Associate

Using a 2804 gimbal motor, and the specifications provided by the vendor are as follows.

PolarBearINBrown_0-1715393672072.png

The parameters tested using the Motor Profiler tool are as follows.

 
 

204655b3lg5kfst5k58s8p.png

The encoder uses MT6701, in ABZ mode, with 4000 CPR (pulse count and phase difference are normal upon testing).

Workbench Settings

1. The motor parameters are as follows (neither vendor data nor test data could resolve the issue, and increasing the torque was also ineffective).

205615r67iijnvekqibjxw.png

2. The motor sensor configuration is as follows (auxiliary sensors not activated).

205653bz2bwgp9db4ifdj1.png

205725x18e1dc7s8ldwsw1.png

3. The parameters for the current sensor are as follows (after testing, the current readings are correct).

210733uyy82nv8p3vzp0vv.png

4. The PI (Proportional-Integral) parameters are as follows (using system default settings).

205936qgkhwg21uhh8gmz4.png

5. The I/O port settings are as follows (after testing, the voltage output, data reading from various sensors, and communication interfaces are all functioning normally).

Phenomenon

1. I can use Motor Profiler to run the motor.

2. Switched the UVW phase sequence, but it was ineffective.

3. In torque mode with a specified Iq, the internal parameters of the motor are tracking normally, but the three duty cycles just stabilize around the set values, unable to run the motor.

212153jkcmxfukk0wzckom.png

211829xefvxxdl76d7eemx.png

4. The poster, a complete newbie to FOC, after several days of fruitless online research, has turned to posting here for help (T^T). Hoping for guidance (please help).

0 REPLIES 0