Skip to main content
K
kumarairia
Associate III
November 14, 2025
Question

Assistance Required – Motor Issues with MCSDK 6.41 on STM32F303EVAL

  • November 14, 2025
  • 0 replies
  • 173 views

Hello Expert,

I am reaching out regarding some persistent issues I am facing with MCSDK 6.41 on the STM32F303EVAL control board with the STEVAL-IPM-NM2S. I suspect there may be bugs or configuration issues.

Background:

  • I previously purchased two boards, and neither motor ran correctly during initial experiments(external opamp case motor work fine)

  • I have now purchased a fresh STM32F303EVAL board and intend to use the internal op-amps and comparators as before. Using external op-amps allows the motors to run, but with internal op-amps, the motors do not start.

  • I followed previous technical support guidance:

    1. Set HTMIN2 = 1 and applied the new configuration.

    2. Replaced the file r3_2_f30x_pwm_curr_fdbk.c in project\MCSDK_v6.4.1-Full\MotorControl\MCSDK\MCLib\F3xx\Src\ with the attached version.

    3. Reduced the PWM pulse width.

Observed Issues:

  1. Motor 1 always faults (mostly fault code 32), whereas Motor 2 runs without issue. I have tried more many times to play with parameters, suggested in MCSDK FOC errors, but did not help. then i tried Using MC_AcknowledgeFault in code allows both motors to run.

  2. High power draw and noise:

    • The motors run at expected RPMs (target speed is correct), but the power draw is unusually high. I mean same rpm, in external opampm draws less power. two ECM motors on the other hand for comparison from the same supplier typically draw ~26 W, but with MCSDK, it draws ~44 W, and there is noticeable humming/noise.

  3. RPM limitation:

    • When trying to exceed 3700 RPM, the motors do not reach the target and remain stuck around 3000 RPM.

Questions:

  • Why does Motor 1 always fault when using internal op-amps, while Motor 2 runs correctly?

  • Could the high power draw and humming noise indicate a configuration issue, SDK bug, or hardware mismatch?

  • Why are the motors unable to reach the target RPM of 3700, even when configured?

  • Are there known limitations in MCSDK 6.41 related to using internal op-amps or comparators on the F303 evaluation board?

I have attached the MCSDK project code for reference.

I have also attached a video, how I am measuring RPM in code. Please advise on possible solutions, or let me know if additional boards need to be purchased for testing.

Thank you for your guidance and support.

Terms & ConditionsAccessibility statement