On Sat, May 06, 2017 at 08:52:40AM -0700, Deven Hickingbotham wrote:
> I have a GPS app that runs on a Raspberry Pi. The system is powered off
> most of the time, but on startup needs to sync time very quickly using PPS.
>
> It looks like the makestep directive is the way to do this. Which of th
On 5/9/2017 5:35 AM, Miroslav Lichvar wrote:
Unless the system will be offline for very long intervals (e.g.
months), in which it could gain a very large offset, which would take
too long to correct, or it can be suspended and resumed without an
RTC, it's better to limit the number of updates in
William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
Physics&Astronomy _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/
On Tue, 9 Ma
On 5/9/2017 12:52 PM, Bill Unruh wrote:
Note that the main problem with pps is that it tells chrony exactly when
the
transition at the top of the second takes place, it does not tell it which
second that was.
So for PPS to work, there has to be a second time source to identify the
second. Wha
No. Besides I do not think a RPi has an RTC.
Also, you can use the NMEA on the gps to give the seconds. PPS and NMEA are
two separate reference clocks. NMEA gives the labeling of the seconds, but is
a horrible time source (good to about 100ms is you are careful). PPS is a
wonderful time source (g
