Search results

I know this thread is a bit old, but I am having the same issue which was reported by the original author. Has anyone found out the cause of this?

Hi luni, this is an interesting idea, yeah a PID would be one way to achieve this, thank you!

Hi luni, thanks for the follow up, I see the fixFTM branch and the new commit you pushed up to the repository. I noticed this commented-out block: errorCode FTM_Channel::setPeriod(float us) { stop(); ci->reload = ticksFromMicros(us); start(); return...

Hi luni, ...when you say "end the current period", does this mean: wait for the remaining time in the current period to finish, then start again with the new period don't wait for the remaining time in the current period to finish, start again with the new period immediately

Thanks joepasquariello, ...understood, and then I guess the next time the hw_interrupt is triggered, the call to t1.begin() will cause the t1 timer to start from zero again? I'm concerned that t1.begin() might be "slow" (I don't know what it needs to do under the hood to get the timer t1...

Question: my understanding was that my timer t1 would be reset when setPeriod() is called, but that appears to not work with the FTM timer(s) - or am I doing something wrong? Context: I want to re-start a PeriodicTimer (1st channel of FTM1, specifically) any time I detect a rising edge on one...