Teemo Vaas

Hi. Have not much time to dig into the conversation. But just for info I have had good result with the lfuse:0xAF and hfuse:0xC9.

> The `PENDING` macro should already handle this correctly since it always starts by creating an unsigned difference value, then looks for a negative result. So it can handle any...

By the way there is also a even more efficient way of using the millis(). Provided that the interval is shorter that 2ˇ16 ms ( about 65.5s). So for intervals...

Currently I can see no way of getting the overflow proof behaviour when pre-calculating the future value, and trying to compare this to the current value, no matter how to...

I looked at the new template MTimeout. It seems promicing. In the regard of properly and most importantly effectively handling shorter variable types for the shorter delays. Although here might...

> Size optimization of `MTimeout` being determined by the delay value type is good. We can just define the delay as a fast type. For size optimization of `MDelay` (which...

Ok, I have been thinking about the topic here. Maybe it has been a little overheated. I did read the more info form here(https://arduino.stackexchange.com/questions/12587/how-can-i-handle-the-millis-rollover/12588#12588) As it was with the cast...

> What's wrong with default ~7Hz PWM? It works fine with zero-crossing. Also optotriacs only turn on at zero, but turn off happens immediately. Though charge usually carry triac open...

Yeah, catering for all the bases with one function messes it up there. When printing decimal only, much smaller buffer is needed(11bytes vs 33bytes). The good formula for calculating needed...

At first glimpse of look seems like the `setFuelschedule()` needs to be wrapped inside the nointerrupts(); interrupts(); Because the interrupt can occur between checking the schedule state and actually taking...