欧博ABG官网-欧博官方网址-会员登入

you are probably right.

I come back on post because of this:
I thought that "timers" in general use the ...timers (hardware). But as I see on this lib, it uses millis(). So it brings the question:
what happens in millis() overload (rollover)? Follows part of the lib:

int8_t Timer::every(unsigned long period, void (*callback)(void*), int repeatCount, void* context) {     int8_t i = findFreeEventIndex();     if (i == -1) return -1;     _events[i].eventType = EVENT_EVERY;     _events[i].period = period;     _events[i].repeatCount = repeatCount;     _events[i].callback = callback;     _events[i].lastEventTime = millis();     _events[i].count = 0;     _events[i].context = context;     return i; }

Since this lib "keeps" the millis of last event, how it compares with new millis after rollover?

As you understand I need a hardware timer (counting clock ticks). Millis() makes demanding to ckeck if "old value" is smaller than millis() value (normal run from start until rollover) or greater (1st time after rollover) before any compare.