You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All returned timestamps should be defined in the same unit and reference frame as WPILib's CAN timestamps
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.
All timestamp values should have a type of uint64_t
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.
uint64_tuint32_t, unfortunately. We'll need to useCANMessagefor our internal CAN stream data representation, rather than the WPILib version like we do now.