When the Simulink file "mcb_pmsm_​foc_sensor​less_dyno_​f28379d.sl​x" from the official MATLAB website is downloaded to the motor, the motor fails to start.

The Simulink file "mcb_pmsm_foc_sensorless_dyno_f28379d.slx" from the official MATLAB website can be compiled and downloaded to the motor successfully, and the simulation results are satisfactory. However, when attempting to start the motor via the host computer using the "mcb_pmsm_foc_host_model_dyno_f28379d.slx" file (by clicking the "Run" and "Start" buttons), the motor does not respond.

[Walter Roberson]

I wonder if you were affected by temporary file disruptions because of the ransomware attack ?

[鑫剑]

Thanks. I have solved the issue, which was caused by excessively high frequency settings. However, now I have modified the observer to the one I designed. The simulation works, but during the on-machine experiment, the angle is correct while the speed is twice the actual value. Why is this happening?

Answer 1

[Aabha]

Hi @鑫剑,

Since this is a hardware related problem, it is hard to pinpoint the exact reason you might be facing this issue. But here are a few different ways you can try to troubleshoot.

Make sure that you have correctly configured the hardware for this model, by following the steps mentioned in the following documentation link: https://www.mathworks.com/help/releases/r2025a/ti-c2000/ug/dual-motor-dyno-example.html

Additionally, ensure that the code is correctly deployed to both the cores of the ‘F28379D’ processor, and the peripherals are configured correctly. Make sure the heartbeat LED (red) is blinking, which indicates that the deployed code is running on hardware as expected. Simulating the host model, and then toggling the 'Motor 1' slider switch to the 'start' position should start spinning the motor. If it does not run, try resetting the hardware using the following steps:

1. Build and deploy the code of the target model.
2. Keep the DC supply powered on, and reset the hardware using the reset switch (yellow push button) on the launchpad.
3. Update the correct comport in the host model and simulate the host model. Then, try and run the motor again using the slider switch.

Please refer to the following documentation link for instructions to identify and debug common problems that can occur when you run the model on the target hardware: https://www.mathworks.com/help/releases/r2025a/mcb/gs/create-validate-model-for-motor-control-system.html

I hope this helps.

[鑫剑]

Thanks. I have solved it. The issue was caused by excessively high frequency settings