Add Robot Hardware Timestamp Synchronization#12
Open
srvald wants to merge 2 commits into
Open
Conversation
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
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.
Summary
This PR introduces a new feature to synchronize ROS 2 message timestamps directly with the Universal Robots controller's internal hardware clock. Additionally, a constant latency compensation parameter has been added.
Changes
use_robot_timestamp(bool): Enables anchoring the timeline to the robot's hardware clock.t_delay(double): Constant network latency compensation factor in seconds [s].RtdePublisherNode):t_0andT_0) upon receiving the first RTDE package.dt).README.rstanddoc/usage.rstwith the new parameters' descriptions.Verification & Testing
The feature was validated using the following launch configuration with a real UR robot:
Log Analysis & Mathematical Proof
Looking at the initialization sequence, we can verify that the timeline synchronization behaves exactly as specified:
Reference Anchor Setup (First Packet):
1779781131.140454T_0):9010.081000t_delay:=0.004): The adjusted base time (t_0) calculation matches perfectly:1779781131.140454 - 0.004 = 1779781131.1364541779781131.136454(withdt = 0.000000)Timeline Progression (Subsequent Packets):
9010.087000(delta =0.006). The calculatedpacket_timeincrements to1779781131.142454, tracking the robot clock linearly instead of the host processor time.