Motor profiler does not work in 6.3.2 while it is in 5.4.8

[JulienD]

Hello

I'm evaluating B-G431B-ES1 design.

As I don't have accurate specifications for the motor, I'm going through motor profiler.

If I use SDK 5.4.8, profiling seems to work. At least, the motor turns.

If I use SDK 6.3.2, profiling whistles while keeping the "startup beep-beep" but the motor never starts. Before that, I built a firmware with the motor profile option activated.

What did I miss?

Thanks

Julien

[GMA]

@JulienD,

Does "Max current" is correct? Does progression bar is stuck? Does MC profiler report an error? 

On the other hand, you can directly use the SDK 5.4.8 results to create the your_motor.json file using one of the already existing files (MC_SDK_6.3.2\Utilities\PC_Software\STMCWB\assets\hardware\motor) as an example.

[JulienD]

Hello,

Thanks for your answer.

Videos (with sound!) 

with SDK5:

https://youtu.be/XqiQC8ekYhk

Video with SDK6:

https://youtu.be/ekjRnlMP2wc

Max current : 10A, btw the power supply says that the average current does not exceed 350mA during the whole video.

The progressbar seems to be stuck.

I did a new longer try and MC porfiler provides a "measurement takes too long" dialog.

Thanks

Julien

[GMA]

Hello @JulienD,

According to User Manual documentation available through "Workbench tool">About>Documentations>Documentation>"User manual", "7. Known Problems" Chapter in "Motor Profiler Application Note" link, "Progress execution bar stays at 7%" could be linked to ADC number usage.
Are you using a B-G431B-ESC1 standard board or a customized one? Standard board is using two ADCs...

[JulienD]

I finally found your documentation. Thanks.

I'm using B-G431B-ESC1 standard board. If needed, it's revision C.

And 2 adcs seems to be configured as requested in the above documentation.

Generated CubeMx file seems to be correct according to the above screenshot.

[GMA]

Hello @JulienD,

You call also try by tuning Max current and Max speed as mentioned for 28% stall as referred in User Manual (decreasing Max current for example).
As previously mentioned, could you generate a motor.json file from SDK5 profiling result, check that you are able to generate a functional project with SDK6 and share the json file?

[JulienD]

Hi

So, I put this settings:

into MCW:

Which leads to this json file :

{
    "hardwareFamily": "MOTOR",
    "label": "turbine2",
    "description": "Turbine",
    "polePairs": 2,
    "nominalCurrent": 10,
    "nominalDCVoltage": 12,
    "rs": 0.24,
    "ls": 0.05,
    "magneticStructure": {
        "type": "SM-PMSM"
    },
    "BEmfConstant": 0.86,
    "inertia": 9.74,
    "friction": 25.63,
    "maxRatedSpeed": 10970,
    "compatibility": ["FOC", "sixStep"],
    "id": "turbine2"
}

I activated potentiometer and electronic speed control which settings are coherent with schematic:

Now when I click the button on the board to start the motor, the behaviour looks like while profiling:

https://youtube.com/shorts/QNHE1RNi2oE

[GMA]

Hello @JulienD,

I am sorry but I missed one point, the "beep-beep" is coming from the fact that Electronic Speed Control ESC is enabled:

Could you please try disabling it?
Electronic Speed Control is described in UM2516: Electronic speed controller Discovery kit for drones with STM32G431CB. 

[JulienD]

I supposed that the test you asked was motor profiling. 

I disabled electronic speed control (even if plan to use it in the future).

I ran motor profiling. The result is better but not fully successfull. Video below.

I tried several combinations of rpm from 15k to 5k and max current from 10 to 3A. It ends up with firmware fault detected : Speed feedback.

hardware

https://youtu.be/ha1z1pHCxz0

software

https://youtu.be/oNSxv0Zegxc

[GMA]

Hello @JulienD,

Could you please try, with your motor.json+MCSDK6 and without ESC feature?