EVSPIN32G4 & Portescap 16ECP52 profiling fails

[Hartwig]

Dear all,

[PN]: EVSPIN32G4 & Portescap 16ECP52 Ultra EC Slotless Brushless DC Motor (Datasheet as pdf attached)

[VERSION]:

MC Workbench : 6.3.2
WB_to_Mx : 6.2.3.template-24-04-17
STM32CubeMX : 6.14.1
MC Firmware Library: 6.3.2-Full
Target Toolchain : ST STM32CubeIDE
Target Driver : LL - Low Level
Target STM32 FW : 1.6.0

[TOOL]: MC Profiler

[DETAILS]:Motor stutters and profiler stops with error 'Speed Feedback'
[EXPECTED BEHAVIOR]:smooth operation within 100-5000 RPM
[HOW TO REPRODUCE]:

1. MC Workbench (specify defaults and motor settings from Portescap)

2. Generate LL code for STM32CubeIDE, target firmware recommended

3. start STM32Cube  : nothing changed -> generate code

4. start IDE, compile, run (its being uploaded)

5. connect using Motor Pilot V1.2.12 profiler app shows up.

6.  Detect pole pairs

Specification from motor manufacturer says two pole but :

I need two rotations to come back to the same orientation, after 5 'notches' in first rotation the original position is not achieved, then 6 more notches are required in a second rotation to come to close 360deg x 2, with in total 11 notches during the two full rotations.

7. Start profile

--> using 5 as well as 6 pole pairs (also tried 1,2,4,5,5.5,6 pole pairs)

---> changed Max Speed from 8k-16k in steps of 2k rpm

max current 0.8

Motor starts spinning at around 28% profiling, runs more or less smooth around 35% at 64% begins good but starts to stutter half way then shortly after error 'Firmware fault detected' Speed Feedback' is indicated.

All help is much appreciated.

Thanks a lot

Hartwig

[GMA]

Hello @Hartwig,

According to specifications_16ecp52.pdf, the Maximum Motor Speed is 40k RPM. Did you try with this value?

[Hartwig]

Yes, I checked to be sure again, same results. smooth around 35% at 64% beginning is good but then within 64%  the profiler reports Firmware fault, 'Speed Feedback',

Speed Sensing is in Observer + PLL mode, when the installed hall effect is specified the motor profiler cannot be used.

In the Speed Sensing Config, tab, the standard values are used :

variance threshhold 25%

Average speed depth for speed loop: 64

Average speed depth for observer equations: 64

B-emf consistency tolerance: 100%

B-emf consistency gain:100%

Sensorless speedfeedback checked.

Observer & PLL Auto Calculate checked

Thanks GMA for looking into it. I did identify a gearbox attached, the pole pair is 1, and consistent with the manufacturers specification. *blush*

Cheers,

Hartwig

[GMA]

Hello @Hartwig,

Can you try decreasing "Max current" value for profiling? This will lead to incorrect Max Current and Max Speed values in the generated motor json file, but those can be easily modified directly in the file and all other values will be correct.

Refer to User Manual documentation available through "Workbench tool">About>Documentations>Documentation>"User manual" tab, "Firmware errors" link, "7. Speed Feedback error" chapter.