PRINT 1<<29
536870912
OK
PRINT 1<<29+1
761419044
OK
In some circumstances this crashes the system. One example is the millis() function:
CONFIG MILLIS, 1<<31
OK
PRINT MILLIS()
... system not responding anymore
This means when using millis() the time counter gets corrupted during day 373 (after 536870912 ms). This might be an issue for IoT applications running extend periods of time and using millis() for time reference.
Large numbers result in wrong values, e.g.
In some circumstances this crashes the system. One example is the millis() function:
This means when using millis() the time counter gets corrupted during day 373 (after 536870912 ms). This might be an issue for IoT applications running extend periods of time and using millis() for time reference.