Repository navigation
feat(scripts): time sync of the robot, chrony and PTP for the LiDAR - #5
Merged
Merged
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.
Every stamp on one clock, the same as Pashupati and Dharma's template (DarmawanRobotics/Dharma#8).
scripts/timesync.sh, also run byscripts/setup.sh install timesync ptp; both are in the default install:TIME_SERVERS(empty: Ubuntu's pool) and serves the robot's other computers inTIME_ALLOW, e.g. the Lite3's network.ptp4lruns as PTP master on the interface of the Mid-360 (the route toLIVOX_IP, orPTP_IFACE), so its points carry this computer's time. PTP is skipped whileLIVOX_IPis empty.clock.enabledinstack.yaml, off insim.yaml).molly.env.example, the README and the CHANGELOG describe the settings.Generated by Claude Code