# Help with using gps time with chrony

**URL:** <https://community.ntppool.org/t/help-with-using-gps-time-with-chrony/2116>\
**Category:** Client Configuration and Development\
**Created:** [August 1, 2021, 10:40pm UTC](https://community.ntppool.org/t/help-with-using-gps-time-with-chrony/2116 "2021-08-01T22:40:20Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![tennisbowling](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tennisbowling](https://community.ntppool.org/u/tennisbowling)\
**Post date:** [August 1, 2021, 10:40pm UTC](https://community.ntppool.org/t/help-with-using-gps-time-with-chrony/2116/1 "2021-08-01T22:40:20Z")

</div>

Hello, I’m currently following this guide [Building a GPS Time Server with the Raspberry Pi 3](http://www.unixwiz.net/techtips/raspberry-pi3-gps-time.html) . It’s a great guide, just it uses ntpd. My question is how would I use the ntpq -q command with chrony? What is the equivalent?

---

<div class="post-metadata">

**Author:** ![tennisbowling](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tennisbowling](https://community.ntppool.org/u/tennisbowling)\
**Post date:** [August 1, 2021, 11:38pm UTC](https://community.ntppool.org/t/help-with-using-gps-time-with-chrony/2116/2 "2021-08-01T23:38:39Z")

</div>

Also, is the adafruit external active antenna waterproof? It should but better safe than sorry

---

<div class="post-metadata">

**Author:** ![Clock](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/clock/32/757_2.png) [@Clock](https://community.ntppool.org/u/Clock)\
**Post date:** [August 2, 2021, 12:07am UTC](https://community.ntppool.org/t/help-with-using-gps-time-with-chrony/2116/3 "2021-08-02T00:07:25Z")

</div>

The **chronyc tracking** command displays parameters about the system’s clock performance.  
**chronyc sources -v** displays information about the current time sources that chronyd is accessing. The **-v** option enables a verbose output. In this case, extra caption lines are shown as a reminder of the meanings of the columns.

**chronyc sources** is the command equivalent to **ntpq -p**

I recommend reading the documentation at [chrony – chronyc(1)](https://chrony.tuxfamily.org/doc/4.1/chronyc.html)

---

<div class="post-metadata">

**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\
**Post date:** [August 2, 2021, 9:29am UTC](https://community.ntppool.org/t/help-with-using-gps-time-with-chrony/2116/4 "2021-08-02T09:29:25Z")

</div>

chronyc sourcestats -v =\> source statistiscs over longer period of time  
chronyc clients =\> who is using my ntp-server?  
chronyc makestep =\> set system time correct to NTP time  
chronyc ntpdata =\> give a lot of info about all your sources incl remote - sort of multi-tracking  
chronyc serverstats =\> stats of packets, send, received and dropped.

Those are about the most usefull including tracking and sources as listed above.

---

<div class="post-metadata">

**Author:** ![tennisbowling](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tennisbowling](https://community.ntppool.org/u/tennisbowling)\
**Post date:** [August 2, 2021, 1:37pm UTC](https://community.ntppool.org/t/help-with-using-gps-time-with-chrony/2116/5 "2021-08-02T13:37:43Z")

</div>

This works great. Thanks. Do you know how I can set a refid (like Facebook or google)?

---

<div class="post-metadata">

**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\
**Post date:** [August 2, 2021, 2:40pm UTC](https://community.ntppool.org/t/help-with-using-gps-time-with-chrony/2116/6 "2021-08-02T14:40:33Z")

</div>

In chrony.conf:

refclock SHM 0 refid GPS poll 4 precision 1e-3 offset 0.1256 delay 0.2  
refclock SHM 1 refid PPS poll 2 precision 1e-9 lock GPS prefer

But beware, not all refid’s are accepted as valid.

---

<div class="post-metadata">

**Author:** ![tennisbowling](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tennisbowling](https://community.ntppool.org/u/tennisbowling)\
**Post date:** [August 2, 2021, 3:14pm UTC](https://community.ntppool.org/t/help-with-using-gps-time-with-chrony/2116/7 "2021-08-02T15:14:31Z")

</div>

But when I query your server, which refid will I get? Maybe I’m asking for the wrong thing here - I used a tool about a year ago that told me the refid of a ntp server I query. For googles ntp server I got GOOG. I’m wondering how I can setup that for my server to be for ex. TEBO.

---

<div class="post-metadata">

**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\
**Post date:** [August 3, 2021, 2:30pm UTC](https://community.ntppool.org/t/help-with-using-gps-time-with-chrony/2116/8 "2021-08-03T14:30:09Z")

</div>

When you query my server you get PPS as refid.  
As that is the most accurate time-source I have and as such does it show it’s refid.

Have a look here:

https://ntp.teambelgium.net/stats.php

GOOG is generally not accepted as valid refid.  
Also beware that Google is not advising to use their NTP as timesource for distribution in e.g. NTP-pool servers.  
Google NTP should be used as endpoint-client only.

---

<div class="post-metadata">

**Author:** ![erayd](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/erayd/32/85_2.png) [@erayd](https://community.ntppool.org/u/erayd)\
**Post date:** [August 5, 2021, 1:20am UTC](https://community.ntppool.org/t/help-with-using-gps-time-with-chrony/2116/9 "2021-08-05T01:20:10Z")

</div>

> [@Bas](#):
>
> Also beware that Google is not advising to use their NTP as timesource for distribution in e.g. NTP-pool servers.

This point is worth stressing. Google implements leap smearing on its time servers. As such, they should _never_ be used as an upstream source for any server that is participating in the NTP pool project, because the NTP pool does _not_ use leap smearing.

This isn’t just “Google advises you not to”; it’s a hard “do not ever do this.”
