-
Notifications
You must be signed in to change notification settings - Fork 27
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
Issue Finding the Correct Offset for GPS0 #20
Comments
looks like there is no log file. please try to uncomment the 99-calibration settings line and comment out the regular configurations line in the file on your system:
and restart chrony/gpsd without deleting the :
after that a log file should be generated, i forgot to mention this - it is not clear that note 2 is only working if the calibration settings are enabled in |
Thanks; will try tomorrow. Can I see the plot over SSH or do I need a desktop environment for that? |
no you can't. but @Lefuneste83 told me, that there is a pure text version pf gnuplot output possible. EDIT: maybe this will work for you to enable X11 forwarting to see the graphical output: EDIT2: see also the additional comments iat the top of /etc/chrony/stratum1/99-calibrate-offset.gps0 |
So I could try the instructions under "note2" but replace the final one with this?:
|
this can be run at any time. even without enabling the 99-calibration settings. something like:
|
i tried the pure text version of @Lefuneste83 in #16, and it works over SSH
|
Ok, I'll be back sometime again tomorrow (Central European Time, CET) if I need to ask more follow-ups. |
oops, i made a mistake under note 2:
option and if your user is not member of group it is so long time ago that i made this project - i forgot already so many tiny things or they changed over time. |
Hi again,
and modified chrony.conf correctly. What is the next step? |
your chrony is up and running with the 99-calibration settings for more than 30 minutes? you will see a graph on the console (may take some time, depending on the size of the log file) depending on how wide your graph is, and if you have only on single big spike, or two, choose the value of mean, median or the value of the highest peak as offset. (the offset in the 10-refclocks-pps0.conf are in [s] not [ms]) if you have found your good offset, comment-out the 99-calibration line and uncomment the regular configuration in /etc/chrony.chrony.conf file. put the offset you found to the done. it is not a problem if EDIT: i notices i changed the regular configurations to generate log files. switching to the 99-calibration configuration was not necessary. EDIT2: it is not needed to calibrate / set the offset as long you just use the |
What's the full path to |
it is in /etc/chrony/stratum1/ |
To restart gpsd and chrony can I just execute this?:
|
to restart gpsd + chrony, do this:
(gpsd service and socket must stop first, then chrony must restart and at last gpsd must start again) this sequence is important (at least on my older version of RasPi OS 11), otherwise some gpsd / chrony shared memory objects will not restart correctly. alternatively you can reboot your RPi. |
if everything is running as normal again for about 30 minutes, you can show me the output of: |
I'll try your instructions tomorrow and let you know how it went. Thanks for everything so far. |
|
that looks good to me. |
Ok, thanks for the all the tips and help! A note on the offset for RPi5B: The offset is several times larger than what I get on my two other RPi Zero 2 W:s (~158 milliseconds). |
interesting. |
in case you want to use stratum one time servers nea by you (sweden) instead of the (generic) pool.ntp.org time servers in the file /etc/chrony/stratum1/20-ntp-servers.conf here some stratum one time servers in sweden i scraped from the StratumOneTimeServers web page:
you can copy'n'past them to your |
Recently I set up this project on a RPi5B 4GB with a NEO-M8T GNSS HAT and today I tried to refine the setup by finding a better value for the GPS0 offset.
I ran the long chain of commands under "note2:" and got this:
What can I do about it?
The text was updated successfully, but these errors were encountered: