From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <5d4f27980009c26d46e274b004371bbb@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /n/gps/time ?
Date: Fri,  6 Apr 2007 16:41:02 -0400
From: Sape Mullender <sape@plan9.bell-labs.com>
In-Reply-To: <20070406202203.GA29531@pestilenz.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 40a3646e-ead2-11e9-9d60-3106f5b1d025

> Hi,
> using gpsfs i get the correct position
> from an NMEA gps device (Haicom 204); but
>  aux/timesync -G 
> resets the clock to 19:xx 31 December 1969.
> The valid nanoseconds value in 
>  /n/gps/time
> is a 10-digit number. Converted to
> seconds it's about 20 seconds after the
> start of the epoch. 
> All other time values are zero.
> Anyone had the same problem?
> 
> Best regards,
> 
> Matthias

Why not
	cat /n/gps/time
This prints three numbers, the time in seconds since the epoch,
the GPS time in nanoseconds since the epoch and the local time
in nanoseconds since the epoch (the local time at which the GPS
time was received).  The difference between the 2nd and 3rd number
measures how far your local clock is off.

Without running timesync, try to see if the numbers make sense.

	Sape