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

ROS Noetic chrony no time sync #7

Closed
nomah98 opened this issue Jul 22, 2022 · 6 comments
Closed

ROS Noetic chrony no time sync #7

nomah98 opened this issue Jul 22, 2022 · 6 comments

Comments

@nomah98
Copy link

nomah98 commented Jul 22, 2022

Hello,

I am running ROS Noetic and chrony.

I am running the ntpd_driver with rosrun _shm_driver:=0 _time_ref_topic:=/mini_2/mavros/time_reference _fixup_enabled:=true __ns:=mini2. I do not seem to have any permissions issue.

Screenshot from 2022-07-22 11-48-37

My /etc/chrony/chrony.conf file includes refclock SHM 0 delay 0.5 refid ROS

Running sudo chronyc sources shows the ROS source as unreachable.

Screenshot from 2022-07-22 11-51-57

rosnode info /mini_2/ntpd_shm shows the node is subscribed to my /mini_2/mavros/time_reference topic, which is being published on via a recorded bag as a TimeReference message.
Screenshot from 2022-07-22 11-54-17

Screenshot from 2022-07-22 11-57-26

I am unsure why the source is still shown as unreachable. I installed via apt. I have used the repo previously and installed with catkin in ROS Melodic and have had success with the same setup. Any help would be appreciated

@vooon
Copy link
Owner

vooon commented Jul 22, 2022

Do you have Setting system date to: <some-date> message? It looks like topic never got the message.

@nomah98
Copy link
Author

nomah98 commented Jul 22, 2022

I do not ever get that message. I can confirm messages are being published to that topic as a sensor_msgs/TimeReference

@nomah98
Copy link
Author

nomah98 commented Jul 25, 2022

Is there any other information via ROS or Chrony I can provide to help investigate this?

@vooon
Copy link
Owner

vooon commented Jul 26, 2022

Can you try to send some TimeReference manually via rostopic?
Also could you please enable debug log for the node (use rqt)?
We are looking that message:

ROS_DEBUG_THROTTLE(10, "Got time_ref: %s: %lu.%09lu",

@matthewryanburgin191
Copy link

matthewryanburgin191 commented Mar 17, 2023

Any update on this issue?

@vooon
Copy link
Owner

vooon commented Mar 20, 2023

Seems no. But note that time ref topic parameter was dropped. Please use remap.

@vooon vooon closed this as completed Mar 20, 2023
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

3 participants