Aug 28, 2019
04:49 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 28, 2019
04:49 AM
Hi,
Sometimes I see that*Icu_17_GtmCcu6_GetDutyCycleValues() can return 0. Did somebody observe similar effects?
#8042000 12587
Sometimes I see that*Icu_17_GtmCcu6_GetDutyCycleValues() can return 0. Did somebody observe similar effects?
#8042000 12587
- Tags:
- IFX
1 Reply
Aug 28, 2019
04:57 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 28, 2019
04:57 AM
Hello,
Due to the software structure, Icu_17_GtmCcu6_GetDutyCycleValues() can return 0.
This happens when Icu_17_GtmCcu6_GetDutyCycleValues() is called right after*Icu_17_GtmCcu6_GetInputState() and the period of PWM input is larger or equal to the period of function calls.*
So, please ensure the calling period of*Icu_17_GtmCcu6_GetDutyCycleValues() is larger than* period of PWM input.
Due to the software structure, Icu_17_GtmCcu6_GetDutyCycleValues() can return 0.
This happens when Icu_17_GtmCcu6_GetDutyCycleValues() is called right after*Icu_17_GtmCcu6_GetInputState() and the period of PWM input is larger or equal to the period of function calls.*
So, please ensure the calling period of*Icu_17_GtmCcu6_GetDutyCycleValues() is larger than* period of PWM input.