BLDC Motor Control with Model Based Design

I think you need to use source insight to search all of the dead time variables in your project. 

So that you can make clear where you should modify exactly.

hello,

   Thank you very much,I have solved my previous problem, but I have encountered a new problem.I want to use freemaster to connect my MPC5744 DevKit via CAN. But there is a problem like the one shown.

PS: 1. I have completed the repair of hot fix_8.
          2. I use openSDA to connect freemaster to MPC5744 DevKit is normal.

    thanks very much and wait for your reply!

Hi Zhang, 

    Your problem is similar with my previous one. 

This kind problem maybe caused by:

Firstly, The corresponding NXP demo software project for MPC5744 dismatch with your board. 

Sometimes, the NXP demo board use external/internal oscillar but the demo software use internal/external oscillar.

Secondly, we suggest you  to pay your attention to the jumpers configuration for different connection cables. You need to read your demo board manual carefully. NXP board mainly have several connection methods including SCI, USB2UART, PEMicro, and openBDM.

All above connections have different jumper configurations. 

So, please read the corresponding document carefully to make sure your jumers' configuration are exact. 

.  

Hi,thomson

thanks for your help. I tried to use the etimer module of MBDT for MPC574XP to read the signal of the photoelectric encoder. I can get the count value of a certain etimer module, but I can't make the etimer module detect the pulse of the encoder index and then clear the value of the register captured by etimer. How can I do this?
PS, I used two etimer modules and one used for orthogonal decoding. Read the pulses of the A and B phases of the encoder. Another pulse is used to detect the index and generate an interrupt.

Dear Zhang, 

    Sorry to reply too late. I was  on my business tour in last two weeks. I saw your problem. My answer is you can add a detection fucntion manually in the generated code. Or you can add one user define simulink function in your BLDC module.

   To detect the first and the second pulses, you need to be very familar with your NXP TIMERS, which is used for PWM signal detecting.

  To NXP MCU, it is much easier for PWM signal detecting. After read the MCU manual, you can find the timer exact registers description for the hex value of the registers.

  Usually, if you use pulse A and pulse B then you need to use one timer with two channels to detect the first clock time and the second clock time for your machine. After you get the two hex values you can evaluate the exact time, frequency and periods or any variable you want.

  The problem is you need to reset your clock before start your function because all of the clock counting need to start from zero clock time.

Good Luck!

Thomson 

When you generate the model from simulink model to C code, you can locate the exact location of GDU part settings. 

Locate the exact deadtime register, and then modify the deadtime value from 24us to 1us.

So often we use 1us to make BLDC/PMSM rotate as faster as possible. 

To make clear which register is the deadtime register, please research the corresponding MCU manual. 

You can download the corresponding manual from www.nxp.com

 GOOD LUCK!

Hello,

       MPC5744P should have its own demo code. Or you can use MBDT simulink modues of BLDC or FOC to make your motor rotate. Since the MCU model can be changed from one to another, you can change it the simulink MCU model from MC9S12 to  MPC5744P and then generate your code directly. 

    If you use the exact evaluation board, you can make your motor rotate immediately.

:smileyhappy:

Hi Eden Li, 

We start with BLDC because is simple. Depending on the feedback we get - for sure we can think of another course on FOC Sensorless on PMSM - for second half of this year.

Best regards,

Daniel

Hi Daniel, 

   For the BLDC MCT toolbox model toolbox 1.3 , the target MCU does not contain the target MCU: MC9S12ZVML32. I have no idea why NXP does not provide the both options for both MC9S12ZVML32 and MC9S12ZVM32.

  What is the differences between MC9S12ZVML32 and MC9S12ZVM32?

  How can we reuse the model for MC9S12ZVML32?

  Do you have any better suggestions for MC9S12ZVML32? Or do you have example BLDC modles for MC9S12ZVML32 ?

Thomson 

Hi Thomson, 

This toolbox has been release some time ago and in the meantime was not updated to support all the available derivatives. Anyhow - the parts you are refering looks very similar - please check table 1 in this application node

https://www.nxp.com/docs/en/application-note/AN5330.pdf 

You may reuse the MATLAB support for MC9S12ZVM32 to develop applications for MC9S12ZVML32 and should work fine.

As a BLDC example you can start with this one: Example Model: S12ZVM Trapezoidal Motor Control  and migrate it to use the MC9S12ZVM32.

Hope this helps!

Daniel

Hi Daniel,

    I downloaded the BLDC model you attached, however, I found when I use a simulink scope model, which contains 3

three input ports, connected to the corresponding 3 BLDC motor PWM output ports( pwma , pwmb and pwmc) , with

matlab BLDC data file ?.mat putted in matlab enviroment, the BLDC PWM output signals are always zero. It means the

BLDC model you attached did not run at all. 

   How can I make this BLDC simulink model generate the exact PWM signal waves when I attached a simulink scope?

 Or this simulink model need to be actived to run with free master project, which attached in the simulink model file?

If yes, please let me know the corresponding pdf, http links or other resources with details how to make this simulink

BLDC model generate exact right PWM output signal.

  Finally, I downloaded the FOC simulink model in your class, however, it always generate zero in the simulink scope,

which means the FOC motor does not run at all. 

I have no idea, how to make this  models generate exactly right signal output?

Thank you very much and wait for your reply.

Thomson 

Thank you very much. This helps.

Hi Maciek, 

We look forward to answer all your questions. We want to change the way we do things and become much more involved with the customers/users of MBD via this community and this course is one of the first initiatives that hopes to clarify some of the aspects you have already highlighted.

For the setup - please wait until Monday when we will release the 1st video - mainly that is the content of the Introduction video - unboxing the devkits and various information about it. We want to avoid spoiler alert at this time :-)

Thank you!

Daniel