The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 |
Newsgroups: comp.protocols.time.ntp
From: David Taylor <david-tay...@blueyonder.co.uk.invalid>
Date: Tue, 30 Oct 2012 19:28:26 +0000
Local: Tues, Oct 30 2012 3:28 pm
Subject: Re: What is the NTP recovery time from 16s step in GPS server?
On 30/10/2012 17:59, Rob wrote:
[] > When I wrote that part of gpsd, I implemented the proper checks so
THanks for this information, Rob. In this case the GPS appears to have > that the time is only put in the SHM after the GPS receiver has > indicated that it has a valid fix on the satellites. a valid fix, but it is outting GPS time and not UTC. There must be a flag in the Trimble TSIP which tells you this, as I've seen the same when monitoring with the Trimble Studio software. It takes some time for the switch-over to occur. > I would hope that the receiver has collected the GPS offset by that
For this receiver that hope is not applicable. Perhaps gpsd should only > time, so that it will not put the wrong time value in SHM during a > short interval. show UTC, or have a flag to indicate between GPS time and UTC? > However, it has been a couple of years and many changes have been
Oh, I really see this. I had occasion to restart my Raspberry Pi NTP > made to the code, I cannot tell you if it may have been broken. > Do you really see the problem you describe above, or is it only a
server and the gpsd source was off by 16.0 seconds for a few minutes after booting. The GPS receiver is powered from the PC. At the moment it has multiple Internet servers as well as the gpsd/ATOM reclocks. -- Cheers, David Web: http://www.satsignal.eu You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||