MTRCKTSPS5744P - Issue for triggering PWM after Motor Driver Initialization

cancel
Showing results for 
Search instead for 
Did you mean: 

MTRCKTSPS5744P - Issue for triggering PWM after Motor Driver Initialization

192 Views
Contributor III

Hello,

I am using Simulink and I could perform the Motor Driver Initialization properly.

However I faced a strange behavior after the initialization, sending the PWM signals output:

I can not update the PWM output when the PWM ports are externally triggered, as shown below:

pastedImage_3.png

However I can update my PWM outputs when the ports are inside the Initialization block, as can be seen below:

pastedImage_1.png

What is the cause of this issue?

How to make the PWM port execute externally by the trigger?

Also I am sending the models attached to make the situation easier for understanding.

Kind Regards, Rafael

3 Replies

44 Views
NXP Employee
NXP Employee

Hello ext-rafael.barbosa@chassisbrakes.com‌,

Do you still facing this strange behavior?

Best Regards,

Marius

0 Kudos

44 Views
Contributor III

Hello mariuslucianandrei‌,

Yes, I do.

Could you reproduce the same error?

Kind Regards, Rafael

0 Kudos

44 Views
NXP Employee
NXP Employee

Hello ext-rafael.barbosa@chassisbrakes.com‌,

I run the both models but without the GD3000 attached (probably I didn't reproduced exactly the same conditions like you) I didn't notice big changes between models. However, the diff between the code generation revealed that in the working model the PWM is initialized before the MC34GD3000_EN_Start() function is called while in the Not Working model the PWM is initialized after the GD3000 initialization is called. This might produce the issue you are facing. Please check the block priorities.

Hope this helps,

Marius