Re: [time-nuts] Sawtooth Error Correction, WAS: Capturing NMEA and TICC timestamp data in time-correlated way?

2019-09-15 Thread Bob kb8tq
Hi The TBolt does code phase to lock up the OCXO. Effectively its best guess error is zero once the control loop closes. That also means the average error is also zero. Since it’s yanking the OCXO *and* guessing at the error, separating those two numbers can get a bit tangled up. One of the

Re: [time-nuts] Sawtooth Error Correction, WAS: Capturing NMEA and TICC timestamp data in time-correlated way?

2019-09-15 Thread Dana Whitlow
Assuming that the T'bird works as you stated, you might still want to know where in that sawtooth the supposedly "fixed" error falls. Maybe this is unimportant if all you want is a stable reference frequency source, or very important if you actually want to know what time it is. However, the

Re: [time-nuts] Sawtooth Error Correction, WAS: Capturing NMEA and TICC timestamp data in time-correlated way?

2019-09-15 Thread Ole Petter Ronningen
Precisely. On Sun, Sep 15, 2019 at 6:03 PM Alberto di Bene wrote: > On 2019-09-15 14:12, Forrest Christian (List Account) wrote: > > > Most GPS receivers with 1PPS outputs are only able to align the 1PPS to > the > > nearest edge of some internal clock. In addition, in most GPS > receivers, >

Re: [time-nuts] Sawtooth Error Correction, WAS: Capturing NMEA and TICC timestamp data in time-correlated way?

2019-09-15 Thread Forrest Christian (List Account)
Let me see if I can give this a go. Some of this will likely be oversimplified and not exactly accurate. Consider this a simplified 101 level class taught by an assistant and not the professor. Most GPS receivers with 1PPS outputs are only able to align the 1PPS to the nearest edge of some