Find the error - Code issue to drive CC motor with timer

[alto777]

Naturally I think you could do worse than understand the code in this post from the near past:

Making a LED switch but it's a bit more complex

I think the state change detection as typically presented is harder to understand, or at least it is easier once a few things get learnt. After the check for a change in the input, if there is one we can deduce that a pressed button must just have become pressed, and similarly an unpressed button must just have been released. But we use the state as proxy for those events. Properly, from a logic point of view, but confusing. Borrowing from some code I saw that handled multiple inputs and reca…

The thread is worth time and will place that post in context.

However you do the buttons the way we all want you to, you will have to decide what to do with the edges.

It seems like you are solving a specific problem, perhaps describing it in some detail would let us help better, fun as it is to speculate.

a7