-
Notifications
You must be signed in to change notification settings - Fork 6
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
Comments
Do you have |
I do not ever get that message. I can confirm messages are being published to that topic as a sensor_msgs/TimeReference |
Is there any other information via ROS or Chrony I can provide to help investigate this? |
Can you try to send some TimeReference manually via rostopic? ntpd_driver/src/shm_driver.cpp Line 155 in b8b9e1d
|
Any update on this issue? |
Seems no. But note that time ref topic parameter was dropped. Please use remap. |
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.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.
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.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
The text was updated successfully, but these errors were encountered: