Re: [time-nuts] Raspberry Pi NTP server

2020-07-15 Thread Petr Titěra
On 15.07.2020 0:13, Trent Piepho wrote: On Mon, Jul 13, 2020 at 4:52 PM Hal Murray wrote: Is there any way for a USB device to synchronise with the CPU clock (perhaps via the USB framing) so that a special-purpose device could timestamp the PPS occurrence with respect to CPU time ? It seems

Re: [time-nuts] Raspberry Pi NTP server

2020-07-13 Thread Petr Titěra
On 12.07.2020 3:57, jimlux wrote: On 7/11/20 1:30 PM, Steven Sommars wrote: Using GPIO with an RPi is a good direction, of course.   That wasn't my question.   Some data may help explain. Configuration = RPi4 (raspbian buster) Uputronics RPi GPS board (includes PPS) connected to GPIO

Re: [time-nuts] Raspberry Pi NTP server

2020-07-09 Thread Petr Titěra
ted to the GPIO pins. That offset will fluctuate, of course. Steve Sommars On Wed, Jul 8, 2020 at 12:57 PM ASSI wrote: On Dienstag, 7. Juli 2020 18:27:01 CEST Petr Titěra wrote: Timing on USB need not to be so horrible. Below is stats from my server with GPS connected using FT232H c

Re: [time-nuts] Raspberry Pi NTP server

2020-07-07 Thread Petr Titěra
Timing on USB need not to be so horrible. Below is stats from my server with GPS connected using FT232H chip (supporting high speed transfers on USB). Yes, the jitter is far greater than on other computer where PPS is connected directly but it is a lot less than that 500microseconds you get

Re: [time-nuts] NTP server using an OCXO, GPS chip and Raspberry Pi

2020-04-27 Thread Petr Titěra
On 25.04.2020 12:19, Hal Murray wrote: David Taylor said: With those recommendations, and noting the delays in RPi I/O (at least in the earlier RPi cards where Ethernet is over USB), I would suggest that an OCXO is overkill. No reason to deviate from the Raspbian OS. That's an important

Re: [time-nuts] Portable Time Standard

2019-03-07 Thread Petr Titěra
On 07.03.2019 14:14, Jim Harman wrote: For ease of programming and reasonably low power consumption I would look into an Arduino. Hello, I can only agree. Use Ardiuno and you will have complete control about your environment. You can even put your board into sleep between pulses. For

Re: [time-nuts] Portable Time Standard

2019-02-17 Thread Petr Titěra
ou use to communicate with the DS3231 and display time? > >How long has your DS3231 been running? > >Have you changed the crystal aging offset register(s) to compensate for > crystal aging? > > Thank you, > Joe > > > On 2/15/2019 12:51 PM, Petr Titěra

Re: [time-nuts] Portable Time Standard

2019-02-15 Thread Petr Titěra
e a portable > communications system. > > Thank you, > Joe > > > On 1/13/2019 2:23 PM, Petr Titěra wrote: >> I will probably sound dumb but did you consider cheap RTC chips? I have >> one based on DS3231 currently on my table and although its is specified >> to h

Re: [time-nuts] Portable Time Standard

2019-01-13 Thread Petr Titěra
I will probably sound dumb but did you consider cheap RTC chips? I have one based on DS3231 currently on my table and although its is specified to have precision +/-2PPM my seems to be in range about 0.5PPM right from package with possibility to do some corrections. Petr Titera Dne 11. 1. 2019 v

Re: [time-nuts] Pseudorange and carrier phase data in L1 only RINEX

2018-07-04 Thread Petr Titěra
On 04.07.2018 8:55, Mark Sims wrote: The main reason is to reduce the file size. RINEX files can be rather long... depending upon what the receiver reports and the satellite systems in use, a 24 hour long 1 Hz file can be over 40 MB. BTW, you can .zip the file for uploading. CSRS-PPP is