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
The Lab uses a u_int16 data type for the millis() query, so each timer overflows after 32 seconds and “hangs” in the negative value range for the next 32 seconds.
In most cases this will not be noticeable, but if more complex sequences are to be programmed, which only come to the timer query after > 32 seconds, then unexpected runtime behavior can occur.
It would be great if you could specify this restriction in the NEPO help for the timer or adapt the implementation yourself.
The text was updated successfully, but these errors were encountered:
The Lab uses a u_int16 data type for the millis() query, so each timer overflows after 32 seconds and “hangs” in the negative value range for the next 32 seconds.
In most cases this will not be noticeable, but if more complex sequences are to be programmed, which only come to the timer query after > 32 seconds, then unexpected runtime behavior can occur.
It would be great if you could specify this restriction in the NEPO help for the timer or adapt the implementation yourself.
The text was updated successfully, but these errors were encountered: