Skip to content

Timestamp improvements #43

Description

@ItsHarper
  1. All returned timestamps should be defined in the same unit and reference frame as WPILib's CAN timestamps
    1. WPILib doesn't do a fantastic job of being consistent and documenting how timestamps work. Improve this upstream, and make sure that the behavior is consistent between simulation and the roboRIO.
  2. All timestamp values should have a type of uint64_t
    1. WPILib HAL timestamps are typed as uint32_t, unfortunately. We'll need to use CANMessage for our internal CAN stream data representation, rather than the WPILib version like we do now.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions