Prevent 32-bit micros() timestamp rollover#1
Open
Gronemeyer wants to merge 2 commits into
Open
Conversation
…ds tracking Added a 64-bit monotonic microseconds variable and updated calculations to use it for speed and distance tracking.
Updated speed calculation to use monotonic time and fixed type casting.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce a 64-bit monotonic microseconds counter to avoid timer rollover in output when recording data for more than 17 minutes.
Timekeeping improvements:
monoUsecs64-bit monotonic microseconds variable to track elapsed time without rollover issues.monoUsecsinstead of the rawmicros()value to ensure time values remain accurate across timer wraparounds. [1] [2]Output changes:
monoUsecs) rather than the raw microsecond timer to increase reliability of logged timestamps. [1] [2]