[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: firstname.lastname@example.org
- Subject: Re: [questions] Re: GPS+PPS vs NTP server, why a huge offset ?
- From: Ralph Blach <chip.from.nc@xxxxxxxxx>
- Date: Fri, 17 Jun 2022 08:14:34 -0600
- Cc: questions@xxxxxxxxxxxxx
- Delivered-to: questions@xxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dzCQKfem8/5dD9si9MxwFxTP4a26ebssnSRK5uoTJqc=; b=c9XSvfub0SWA3uOKrF7dMg4AH6TfMA/Z6ygO99zZgNBcjcwTcHV4nNrSPYgOsYsAQC IexRC0jTX/5P97mbwq1a1bcJ9u3Y7Wa4ysBesz8DUekwI376YrYGcDc6rvUhkZv8YaHA wVjTldIuKZVblRgJEFmQc7U+8PabgCs6t5QleNMD9aoaxRrxjp+/96dcmmCtniQj4U8v vpY+7GOhQ5DimBn2eH3yJ8e2rckQCYk/IwhGqjK5Erwzhmhm6fyWqM6L+eSDjnZ3iMYY K2u1Rgcja42Qyj2zcR3cKbZ2viN28gnQT/MTDgJu/PMe+QRHXSu+zEITcAzs4he6ac53 okyw==
- In-reply-to: <email@example.com>
- List-id: questions.lists.ntp.org
- List-unsubscribe: mailto:firstname.lastname@example.org
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <633A7397-0163-4408-BB2C-D639D6C5B92D@dons.net.au> <firstname.lastname@example.org>
- Reply-to: questions@xxxxxxxxxxxxx
I have complete instructions on how to use a raspberry pi as an NTP server.
Ping me if you want them
On Fri, Jun 17, 2022, 8:08 AM David Taylor <email@example.com> 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.
This is questions@xxxxxxxxxxxxx