Ah, not really but please accept my apologies.
I just don't understand what the problem here, the issue was discussed in depth in the other thread but apparently there's some detail that doesn't make sense - and that's fine - but instead of asking about that detail we get a new thread with the same topic.
And, regarding PAUSE, you're of course 100% correct with that comment but it doesn't really pertain to the HPWM command and may just make thing more confusing.
Anyway, I'm sorry for being harsh, not my intention, shame on me.
/Henrik.
Yup, for sure HPWM is the way to go unless you've already used those pins up, in which case you can go SPWM, but that chews up processing time. HPWM isn't "slow or fast" like Henrik says, you just change your duty cycle as quickly or slowly as you want to, you can test it with a pause loop, and then implement via a timed interrupt routine (which obviously has less overhead).
Bookmarks