[time-nuts] GPS receiver time message offsets to 1PPS (updated)

The Skylab is effectively useless for sub-second timing. The message arrival time periodically jumps around, up to +/- 300 msecs. There are a couple of values that it seems to prefer, but any value can be seen. NMEA works a lot better on most receivers that I expected. They send several

[time-nuts] GPS receiver time message offsets to 1PPS (updated)

Lady Heather keeps the date/time time in two sets of variables. One is the receiver time message values in UTC (or GPS) time. The other is local time (UTC/GPS adjusted for time zone or time scale) that is used for the clock displays. There are integer year,month,day, hours,minutes,seconds

Re: [time-nuts] GPS receiver time message offsets to 1PPS (updated)

Hi So everything is inside a 10 ms sdev except: UBLOX LEA-6T NMEA at 11.1 ms (Binary is much better) Adafruit Ultimate at 39.8 ms Neither one of those are really surprising. NMEA is not the best thing on uBlox. The specs on the Adafruit part have never made much sense for timing. Somebody was

Re: [time-nuts] GPS receiver time message offsets to 1PPS (updated)

Yo Mark! On Thu, 28 Jul 2016 02:13:09 + Mark Sims wrote: > I found what was causing the apparent ramps in the message offset > time for the Motorola mode receivers and the Z38xx receivers. And the problem was? RGDS GARY

[time-nuts] GPS receiver time message offsets to 1PPS (updated)

I found what was causing the apparent ramps in the message offset time for the Motorola mode receivers and the Z38xx receivers. Here is the updated and corrected info. Note that a couple of receivers do have some minor ramp sawtooths in their message timing. They are less than +/- 10 msecs

Re: [time-nuts] GPS receiver time message offsets to 1PPS

hol...@hotmail.com said: > I originally thought the SCPI receivers would be right on time due to > my original measurements of their message jitter, but when I started > measureing the actual message arrival times... surprise, surprise, surprise! > I think the issue is due to the fact that they

[time-nuts] GPS receiver time message offsets to 1PPS

Heather will take either time format, but requests the receiver to send T2 format. I originally thought the SCPI receivers would be right on time due to my original measurements of their message jitter, but when I started measureing the actual message arrival times... surprise, surprise,

Re: [time-nuts] GPS receiver time message offsets to 1PPS

hol...@hotmail.com said: > Here are the results of measuring the difference between the time code in a > GPS receiver time message and the arrival time of the last byte of the > message. Negative values mean that the receiver sends the timing message > after the 1PPS pulse that it describes. The

Re: [time-nuts] GPS receiver time message offsets to 1PPS

Yo Mark! On Mon, 25 Jul 2016 22:51:01 + Mark Sims wrote: > Here are the results of measuring the difference between the time > code in a GPS receiver time message and the arrival time of the last > byte of the message. Negative values mean that the receiver sends > the

[time-nuts] GPS receiver time message offsets to 1PPS

Here are the results of measuring the difference between the time code in a GPS receiver time message and the arrival time of the last byte of the message. Negative values mean that the receiver sends the timing message after the 1PPS pulse that it describes. The table also shows the standard