Part Number: MSPM33-SDK
Other Parts Discussed in Thread: SYSCONFIG
Hello,
I come back on topic :
The PWM management is correct, except when the duty cycle requested is 0%.
Let me explain you
At first (after µc reset), the duty cycle requested is 0%:
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: MSPM33-SDK
Other Parts Discussed in Thread: SYSCONFIG
Hello,
I come back on topic :
The PWM management is correct, except when the duty cycle requested is 0%.
Let me explain you
At first (after µc reset), the duty cycle requested is 0%:
Hi Sebastien Le Diouri
we will check the detailed and reply to you later
Thanks
u32compareValue is set to 0, the timer's counter triggers a "compare match" at the exact moment it resets to 0 at the beginning of each cycle. Because the PWM logic is designed to toggle the signal upon a match, this causes a momentary voltage transition (the ~120ns pulse you observed) at the start of every period.Hello Ella,
ok but which function uses for disabling the PWM ?
I have
Hi Sebastien Le Diouri,
Could you please share the related PWM sysconfig settings and code? We will check the problem later.
Alternatively, you can try to use DL_Timer_overrideCCPOut to force 0% Duty Cycle.
Thanks!
Best Regards,
Ella Tang
About source code:
void vDutyCycle_PWM(float_t fDutyCycle)
Hi Sebastien Le Diouri,
Use same function, the CCP output state is changed from "DL_TIMER_FORCE_OUT_LOW" to " DL_TIMER_FORCE_OUT_DISABLED"
Best Regards,
Ella Tang