Model-Based Design Toolbox (MBDT)のトピックRe: MTRCKTSPS5744P - Issue for triggering PWM after Motor Driver Initialization

MTRCKTSPS5744P - Issue for triggering PWM after Motor Driver Initialization

ext-rafael_barb — Thu, 18 Jul 2019 13:47:46 GMT

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:

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

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

Re: MTRCKTSPS5744P - Issue for triggering PWM after Motor Driver Initialization

mariuslucianand — Wed, 31 Jul 2019 12:21:48 GMT

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

Do you still facing this strange behavior?

Best Regards,

Marius

Re: MTRCKTSPS5744P - Issue for triggering PWM after Motor Driver Initialization

ext-rafael_barb — Thu, 01 Aug 2019 08:49:41 GMT

Hello mariuslucianandrei‌,

Yes, I do.

Could you reproduce the same error?

Kind Regards, Rafael

Re: MTRCKTSPS5744P - Issue for triggering PWM after Motor Driver Initialization

mariuslucianand — Fri, 02 Aug 2019 10:28:44 GMT

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