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

Provide service call to verify time synchronization status #7

Open
boxanm opened this issue Sep 16, 2024 · 0 comments
Open

Provide service call to verify time synchronization status #7

boxanm opened this issue Sep 16, 2024 · 0 comments

Comments

@boxanm
Copy link

boxanm commented Sep 16, 2024

Currently, the ROS driver contains a service call to set up different time synchronization methods (ntp, ptp, GPS). However, it is not possible to read the master-slave device delays and, therefore, assess the synchronization quality. Devices from other brands usually provide some status, for example "locked", together with the delay in ticks or nanoseconds between the two devices.

Since the Windows app allows us to check the status, I assume the packets must contain these values, and it is simply a question of writing the appropriate service call to read and interpret these values. Nevertheless, since most ROS systems, including ours, are running on Linux, using the Windows app is not an option.

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

No branches or pull requests

1 participant