2020-04-25 12:55 PM
Me and my team have been working for a while now on the Stm32 workbench. The Motor Profiler calculates the parameters for the motor, and are then they are imported to the workbench to generate code to TrueStudio IDE. We are facing some issues with driving the motor and have been following the instructions and steps in the "STM32 PMSM FOC SDK Frequently-asked questions (FAQ)" pdf found below, but the same problems are still occurring and no change at all in the motor behaviour.
1. In the Motor Profiler Software, the motor does not stabilize at the low RPM below 1000 - 1200 RPM, but at higher RPM the motor stabilizes.
2. In TrueStudio the motor works for a few seconds and then stops immediately while the rest of the code works normally. As if the pwm breaks, the Methods used in the TrueStudio code are
MC_ProgramSpeedRampMotor1( 1000, 500 );
MC_StartMotor1();
bly172s-24v-4000 Anaheim Automation
QBL4208-61-04-013 Trinamic
Solved! Go to Solution.
2020-10-19 07:22 AM
Dear @Laurent Ca...
Thanks you for your Reply.
"Without any code running on it, just connecting the IHM08M1 damages the ST-Link on the stm32f303re boards."
Regarding this issue, yes we have it solved. The problem is that the pins PA13 and PA14 were used for USART communication and this should not happen, because the MCU uses those pins internally for clock and data transfer. Try changing the USART to different pins if you are using them.
In our case, we have developed our own BLDC Control Driver.
Best regards
@OTcho.1
2020-05-11 02:33 AM
Dear OTcho.1,
The FAQ document you found is a bit old, but still valid, you were right to use it.
Now, how can we help you?
Do you want to describe your problem with more details?
Thanks a lot,
Claire
2020-06-03 01:31 PM
Hello,
Me and my team have resolved the Workbench issue as follows:
- the "sensorless Speed Feedback" box was automatically checked when the code was generated with st Workbench.
- We just unchecked this box.
when we unchecked this box, the Motor worked perfectly.
The box is under:
Firmware Drive Management-> additional features-> sensorless Speed Feedback
we have been using the 3 shunt configuration for 2 IHM08M1 boards with 2 stm32f303re boards for FOC. We used the Motor Profiler to calculate the needed values, STWorkbench to generate code. We obtained the values of the motor using its nominal voltage 24V. In the While loop we used the functions:
- MC_ProgramSpeedRampMotor1 (3000/6, 500);
- MC_StartMotor1 ();
It was working good with no problems, stable current and voltage for some days. Then, the two IHM08M1 boards separately with different codes started damaging the stm32f303re boards.
Without any code running on it, just connecting the IHM08M1 damages the ST-Link on the stm32f303re boards.
1) Data sheets of the Micro-controllers states this hardware configuration also for FOC (removing 3 capacitors and adjusting the jumpers):
- Setting jumpers JP1 and JP2
- Adjusting JP5 and JP6 on the 3Sh configuration
- Removing C3, C5 and C6
Best regards,
Octave
2020-10-14 01:47 PM
Dear @OTcho.1
Do you have still this problem to solve?
Best regards
Laurent Ca...
2020-10-19 07:22 AM
Dear @Laurent Ca...
Thanks you for your Reply.
"Without any code running on it, just connecting the IHM08M1 damages the ST-Link on the stm32f303re boards."
Regarding this issue, yes we have it solved. The problem is that the pins PA13 and PA14 were used for USART communication and this should not happen, because the MCU uses those pins internally for clock and data transfer. Try changing the USART to different pins if you are using them.
In our case, we have developed our own BLDC Control Driver.
Best regards
@OTcho.1