How does rusEFI handle 23 (or 46?) days of continues operation #4554
This commit is contained in:
parent
cbb42b68d1
commit
6b03f4ba68
|
@ -43,8 +43,8 @@ using efitimesec_t = time_t;
|
|||
|
||||
/**
|
||||
* integer time in milliseconds (1/1_000 of a second)
|
||||
* 32 bit 4B / 1000 = 4M seconds = 1111.11 hours = 46 days.
|
||||
* Please restart your ECU every 46 days? :)
|
||||
* 32 bit 4B / 1000 = 4M seconds = 1111.11 hours = 23(or46?) days.
|
||||
* Please restart your ECU every 23(or46?) days? :) See issue https://github.com/rusefi/rusefi/issues/4554 tag#4554
|
||||
* See getTimeNowUs()
|
||||
*/
|
||||
using efitimems_t = uint32_t;
|
||||
|
|
|
@ -164,7 +164,7 @@ class EngineStateBlinkingTask : public PeriodicTimerController {
|
|||
static EngineStateBlinkingTask engineStateBlinkingTask;
|
||||
|
||||
/**
|
||||
* 32 bit return type overflows in 23 days. I think we do not expect rusEFI to run for 23 days straight days any time soon?
|
||||
* 32 bit return type overflows in 23(or46?) days. tag#4554. I think we do not expect rusEFI to run for 23 days straight days any time soon?
|
||||
*/
|
||||
efitimems_t currentTimeMillis(void) {
|
||||
return US2MS(getTimeNowUs());
|
||||
|
|
Loading…
Reference in New Issue