Motor Profiler stuck at 28%

[DMeie.2]

[VERSION]: 6.2.1
[TOOL]: Motor Profiler in Motor Pilot V1.2.5
[DETAILS]:Motor Profiler gets stuck while profiling at "Profiling % 28".
Hardware used is the inverter-board B-G431B-ESC1.
[EXPECTED BEHAVIOR]: I expect the motor profiler to either finish the process or abort with an error so that I can fix any existing issues.
[HOW TO REPRODUCE]: Motor is soldered to the inverter-board, power supply connected and set up to deliver the correct voltage and enough current (12V, 30A). Motor Profiler is started and connects successfully. The required motor parameters are entered accordingly. The profiling is started. At 7%, the motor twitches once, and at 21% the motor hums for half a second. Maximum observed current is around 2.5A until then. Then the process gets stuck at 28% until the notification pops up that the measurement takes too long. The board pulls standby current.

[DMeie.2]

Also tried with MCSDK 6.3.0 and Motor Pilot V1.2.9.
Issue still persists identically.

[Gael A]

Hello DMeie.2,

Have you tried playing with the Max Current and Max Speed values, reducing them for instance, to allow a clean start-up ? Profiling may need to tinker those values a bit. This will lead to incorrect Max Current and Max Speed values in the json file at the end, but those can be easily modified directly in the file and all other values will be correct.

If you have trouble nonetheless, you can try to make your motor run in Open Loop mode first, to see if currents are correctly generated. The Open Loop mode description can be found in the MCSDK User Manual.
You can then define a correct speed ramp for your motor that you would then apply to your Profiler project and profile it again with those new values.

[DMeie.2]

I tried various different combinations of the Max Current and Max Speed settings, however none of those lead to a change of the issue.

I'll see if I have time to try the open loop method with the ESC module
Nontheless, I think it instead of just hanging, the Motor Profiler should report an error.

[DMeie.2]

Changed my setup to use a X-NUCLEO-IHM08M1 together with a NUCLEO-G431RB.
Issue is still the same.

Motor twitches once, audibly hums for half a second and then gets stuck doing nothing anymore at 21% until the "takes too long" message pops up.

Looks like the software is having issues trying to measure some parameter of the motor we use.

[aosb]

I am using MotorControl Workbench 6.3.1 with Motor Profiler V1.2.11, and the B-G431B-ESC1 inverter board and am experiencing the same behaviour.

Has any further investigation on this topic been performed?

Cheers

[DMeie.2]

Unfortunately not, it seems.

We put our effort on getting this to work on hold and keep relying on the motor datasheet for now.

[Gael A]

Hello all,

It seems there has been a little confusion there, I apologise for that and I will rephrase and complete my answer.

The Profiling getting stuck at 28% is symptomatic of the FW not being able to find a suitable speed ramp for the start-up. Usually you can find a suitable solution by tinkering with the Max Current and Max Speed values as I said in my previous comment.

However, if this does not work, then your best shot is to switch to an Open Loop project, and find the best suitable start-up method for your motor manually. Once you have it, you can put it into your Profiler project, that will start according your new ramp up, and hopefully will be able to switch to close loop and then finish the profiling.

[DMeie.2]

@Gael AI got around to play with the setup some more and got the motor to run by rebuilding the project from scratch with the most recent MCWB release.

However, the profiling process is still stuck at 28%, this time with the motor running reliably at a constant RPM.

[Gael A]

Hello DMeie.2,

This usually means that the speed is not stable enough for the Profiler to conduct the next steps, despite reaching close loop control. It can come from badly tuned PI gains or trying to run the motor in a difficult speed range.

Have you tried creating a custom open loop ramp to reach the best running spot for your motor ?

[DMeie.2]

How would I go about doing that?

[DMeie.2]

I already have set a known working Start-up profile for the motor into the Profiler project.

As for Open-Loop mode, I have used this before.
However, I am not sure how to enter these values into the Profiler project, as it is not possible to have Profiler and Open-Loop mode at the same time.

[soheil3041]

I have the same problem. I connected a PMSM motor, but it gets stuck at 28%. I tried changing the maximum current and maximum RPM, but it didn’t work. I also tried running it in open-loop mode, but as soon as I start, it shows an “Error Over.” What should I do?

I tested with an AC induction motor in open-loop voltage mode, and it works fine. However, when I switch to the PMSM motor, it doesn’t work.

[JandreFrey]

Hi all,

I would like to follow up on this post, as I am experiencing the same issues.

Motor: Faulhaber 0620B

Nucleo: F446RE

Driver: IHM17M1

MCSDK: V6.4.1

I was easily able to spin the motor up in open loop mode to a whole range of speeds at a wide range of currents. 
However, when I run the profiler, the motor spins up and then fails about halfway to the target speed. The profiler then hangs at 28%.The speed up seems perfectly fine, and I have tried both with aux hall sensors and without. I have also tried a wide range of speeds from 50000RPM to 5000RPM, and all currents from 0.1-0.3A. 

Any help would be appreciated.

Kind regards,

J Frey