[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [questions] Re: GPS+PPS vs NTP server, why a huge offset ?
- To: questions@xxxxxxxxxxxxx
- Subject: Re: [questions] Re: GPS+PPS vs NTP server, why a huge offset ?
- From: Jim Pennino <jimp@xxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Jun 2022 07:50:29 -0700
- Cancel-lock: sha1:/9zwp0Id2Mbk4C+gW3N8864d2PA=
- Delivered-to: questions@xxxxxxxxxxxxx
- List-id: questions.lists.ntp.org
- List-unsubscribe: mailto:email@example.com
- Organization: A noiseless patient Spider
- References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <633A7397-0163-4408-BB2C-D639D6C5B92D@dons.net.au> <email@example.com>
- Reply-to: questions@xxxxxxxxxxxxx
- User-agent: tin/2.4.4-20191224 ("Millburn") (Linux/5.4.0-120-lowlatency (x86_64))
David Taylor <firstname.lastname@example.org> wrote:
> On 17/06/2022 03:03, Daniel O'Connor wrote:
>>> Yes, Thiebaud, USB is not good enough for PPS signals!
>> This is absolutely false.
>> If you are using it for NTP then GPS+PPS over USB is quite adequate (from personal experience).
>> Ian Lepore (RIP) who worked for Micro Semi and worked on FreeBSD did a bunch of tests on a PPS over USB setup and found it more than
>> acceptable for keeping a PC in (good) time. Here's the thread:https://lists.freebsd.org/pipermail/freebsd-arm/2019-August/020263.html
>>> See if your motherboard has a true serial port - perhaps just as a header but not a back connector. If not, just set the offset of the PPS to ~10.3 milliseconds (10.3 - IIRC the offsets are in milliseconds but please check). Plus or minus 10.3, try it and see! Not perfect, but better than nothing.
>>> You might find better results using that GPS/PPS with a Raspberry Pi as a stratum-1 server and offering that as a server on your LAN.
>> The next level would be something where you can do an input capture on the PPS I don't think there are any pre canned solutions. I made one with a Beagle Bone Black and a uBox GPS module but it's not exactly turn key. Or for a server then you would need a fancy (ie $$$$) internal card.
>> The Raspberry Pi does not have an input capture timer, but I believe you can do better with DMA hackery (I haven't tried though).
> If a 125 us uncertainty in the PPS is something you can tolerate, so be it. If
> you are bothering with PPS then presumably you want better accuracy than can be
> achieved without it.
> No need for DMA hackery. Standard NTP with the Raspberry Pi can handle PPS on
> a GPIO signal with a couple of edits to allow the PPS support already built
> into the kernel to be attached to the appropriate GPIO pin. Not out of the
> box, but very little effort required.
> The Raspberry Pi can act as a server for hundreds of clients. If you mean a
> PC-based Windows server, that's not something I would immediately recommend,
> but if you must a £20 serial card may be all you need to add.
The Pi4 with a current GNSS model $29.95 Adafruit Ultimate GPS HAT will
provide an accuracy of about 1 to 2 microseconds.
If you plot loopstats you can see the offset vary with the heat/AC going
on and off and the error varying by about .5 microseconds.
If you want better than that, you need a GNSS receiver with a managed
oscillator such as an OCXO or rubidium.
However actually achieving in NTP anywhere near the +/- 1 nanosecond
accuracy of an OCXO will require careful selection of both hardware
This is questions@xxxxxxxxxxxxx