You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On some boards (e.g. ATmega like Uno) "int" is only 2 bytes and thus is capped unsigned at only roughly 65000. As mUpdateInterval holds milliseconds this more or less means that you can have 1 minute max as update interval.
I suggest to set the type of mUpdateInterval to uint32_t, which is always right.
The text was updated successfully, but these errors were encountered:
electricant
added a commit
to electricant/EasyNTPClient
that referenced
this issue
Apr 2, 2021
hardware.
AS decribed in aharshac#5
On some boards (e.g. ATmega like Uno) "int" is only 2 bytes and thus is capped unsigned at only roughly 65000. As mUpdateInterval holds milliseconds this more or less means that you can have 1 minute max as update interval.
On some boards (e.g. ATmega like Uno) "int" is only 2 bytes and thus is capped unsigned at only roughly 65000. As mUpdateInterval holds milliseconds this more or less means that you can have 1 minute max as update interval.
I suggest to set the type of mUpdateInterval to uint32_t, which is always right.
The text was updated successfully, but these errors were encountered: