This is what I had with no time1:
remote refid st t when poll reach delay offset jitter
==
oPPS(0) .PPS.0 l 13 16 3770.000 -0.007 0.005
*GPS_PALISADE(0) .GPS.
On 08/16/2013 05:44 AM, David Taylor wrote:
On 15/08/2013 21:33, Magnus Danielson wrote:
[]
They completely avoid it by not numbering it that way. They have their
own numbering scheme that fit's the system, and the conversion over to
UTC is an added feature. It's all in ICD-GPS-200 for the
On 08/15/2013 11:02 PM, unruh wrote:
On 2013-08-15, Magnus Danielson mag...@rubidium.dyndns.org wrote:
On 08/15/2013 10:22 AM, David Taylor wrote:
On 15/08/2013 08:34, Rob wrote:
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 14/08/2013 17:44, Rob wrote:
[]
How does a good
On 16/08/2013 08:12, Magnus Danielson wrote:
[]
If you go here:
http://www.gps.gov/technical/icwg/
you will find IS-GPS-200G (which is the new name since 2006, I have
failed to adapt) on this link here:
http://www.gps.gov/technical/icwg/IS-GPS-200G.pdf
Using ICD-GPS-200D gives a fair idea of
Mark C. Stephens wrote:
This is what I had with no time1:
remote refid st t when poll reach delay offset jitter
==
oPPS(0) .PPS.0 l 13 16 3770.000 -0.007 0.005
David Taylor wrote:
On 14/08/2013 04:01, Danny Mayer wrote:
[]
NTP doesn't own the OpenSSL sources so we don't distribute it. People
can get their own if they want it.
OpenSSL is also not easy to compile from scratch, i.e. you need at least
some perl interpreter, and assembler if you want
David Taylor writes:
A pity that they haven't been able to find two or three spare bits to
reduce the 1024 week ambiguity to nearer a half-century or even 100
years.
From the Wikipedia article:
To determine the current Gregorian date, a GPS receiver must be
provided with the approximate
David Lord wrote:
Mark C. Stephens wrote:
This is what I had with no time1:
remote refid st t when poll reach delay
offset jitter
==
oPPS(0) .PPS.0 l 13 16 377
On 16/08/2013 13:02, John Hasler wrote:
David Taylor writes:
A pity that they haven't been able to find two or three spare bits to
reduce the 1024 week ambiguity to nearer a half-century or even 100
years.
From the Wikipedia article:
To determine the current Gregorian date, a GPS receiver
On 08/16/2013 10:36 AM, David Taylor wrote:
Yes, all my receivers are very simple, consumer-level ones. Sometimes
I see as low as 2m location accuracy on the GPS 60 CSx, more likely
3m when walking.
Thanks for the pointers to the documents. A pity that they haven't
been able to find two
On 08/16/2013 03:34 PM, David Taylor wrote:
On 16/08/2013 13:02, John Hasler wrote:
David Taylor writes:
A pity that they haven't been able to find two or three spare bits to
reduce the 1024 week ambiguity to nearer a half-century or even 100
years.
From the Wikipedia article:
To
On 8/15/2013 11:15 PM, Mark C. Stephens wrote:
This is what I had with no time1:
remote refid st t when poll reach delay offset jitter
=
oPPS(0) .PPS. 0 l 13 16 3770.000 -0.007 0.005
12 matches
Mail list logo
