Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed change: Adding timestamping to received mssgs #19

Merged
merged 2 commits into from Feb 19, 2017
Merged

Proposed change: Adding timestamping to received mssgs #19

merged 2 commits into from Feb 19, 2017

Conversation

thomasonw
Copy link
Contributor

Proposing to add additional value to CANFRAME structure: .time
(timestamp). Allows applications to apply aging decisions to received
messages.

thomasonw added 2 commits March 6, 2016 10:56
Correcting functions: get_internal_timer_value(); and
get_timestamp_value(); to indicate 16 bit returned values as opposed to
32 bit.

CAN_TIM & CAN_TIMESTP are 16 bit registers.  Representing them as 32bit
could cause issues when one is attempting to do relative time
calculations and these 16 bit registers have been extended to 32 bits.
Proposing to add additional value to CANFRAME structure:  .time
(timestamp).  Allows applications to  apply aging decisions to received
messages.
@thomasonw
Copy link
Contributor Author

This pull request also has a correction in it (Still working out details of how to use GitHub - sorry):

Corrected size of timer return values.

Correcting functions: get_internal_timer_value(); and
get_timestamp_value(); to indicate 16 bit returned values as opposed to
32 bit.

CAN_TIM & CAN_TIMESTP are 16 bit registers. Representing them as 32bit
could cause issues when one is attempting to do relative time
calculations and these 16 bit registers have been extended to 32 bits.

@collin80 collin80 merged commit 4a086aa into collin80:master Feb 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants