Re: [ntp:questions] false ticker after GPS coldreset

2017-12-19 Thread Gary E. Miller
Yo Martin! On Fri, 8 Dec 2017 10:20:59 +0100 Martin Burnicki wrote: > again sorry for the late reply. I've been mostly offline for a few > weeks now. Compounded by my being confined to bed for a bit, then taking forever to get caught back up. Nothing serious on my

Re: [ntp:questions] false ticker after GPS coldreset

2017-12-08 Thread Martin Burnicki
Hi Gary, again sorry for the late reply. I've been mostly offline for a few weeks now. Gary E. Miller wrote: > Yo Martin! > > On Mon, 6 Nov 2017 22:16:12 +0100 > Martin Burnicki wrote: > >> sorry for the late reply. I've been mostly offline for some days. > >

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-10 Thread Gary E. Miller
Yo Martin! On Mon, 6 Nov 2017 22:16:12 +0100 Martin Burnicki wrote: > sorry for the late reply. I've been mostly offline for some days. Yeah, we both have real lives too. > I'm mostly working with GPS PCI cards, where the kernel driver reads a > high resolution,

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-06 Thread Martin Burnicki
Hi Gary, sorry for the late reply. I've been mostly offline for some days. Gary E. Miller wrote: > Yo Martin! > > On Fri, 3 Nov 2017 14:27:52 +0100 > Martin Burnicki wrote: > Anyway, gpsd seems to accept the raw GPS time as UTC time, feeds it to ntpd,

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-06 Thread Gary E. Miller
Yo Martin! On Fri, 3 Nov 2017 14:27:52 +0100 Martin Burnicki wrote: > >> Anyway, gpsd seems to accept the raw GPS time as UTC time, feeds > >> it to ntpd, and ntpd sets the Linux system time off by a number of > >> seconds. > > > > Which is why gpsd should rarely

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-05 Thread William Unruh
On 2017-11-05, valizadeh...@gmail.com wrote: > On Friday, November 3, 2017 at 1:01:26 AM UTC+3:30, Martin Burnicki wrote: >> valizade...@gmail.com wrote: >> > i have a ntp server based on Raspberry Pi3 with PPS (from u-blox6 ). i >> > have also added a hardware clock to

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-04 Thread Kiss Gábor
> This is because ntpd computes the system time adjustment from the > weighted measurements against the system peer *and* from the candidates. Gee! That is interesting. :-o > Usually the GPS refclock provides high accuracy and low jitter, but NTP > servers on the network provide much more jitter

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-03 Thread Martin Burnicki
Since gatewaying from the NTP questions mailing list to this news group seems to be broken, please see http://lists.ntp.org/pipermail/questions/2017-November/thread.html for some additional replies ssubmitted via the mailing list. Martin -- Martin Burnicki Meinberg Funkuhren Bad Pyrmont

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-03 Thread Martin Burnicki
Hi Gary! Gary E. Miller wrote: > Yo Martin! > > On Thu, 2 Nov 2017 22:31:24 +0100 > Martin Burnicki wrote: > > >> GPS internal system time is off UTC by an integral number of seconds >> corresponding to the number of leap seconds that have been observed >> since

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-03 Thread Gary E. Miller
Yo Martin! On Thu, 2 Nov 2017 22:31:24 +0100 Martin Burnicki wrote: > GPS internal system time is off UTC by an integral number of seconds > corresponding to the number of leap seconds that have been observed > since 1980. This offset is sent in subframe 4, page

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-02 Thread Martin Burnicki
valizade...@gmail.com wrote: > i have a ntp server based on Raspberry Pi3 with PPS (from u-blox6 ). i have > also added a hardware clock to this system. > > > SOME times there is a large offset(3-18 sec) on the SHM (ntp driver 28). > i did some experiments and figured out it is related to "leap

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-02 Thread Jakob Bohm
On 31/10/2017 18:17, William Unruh wrote: On 2017-10-31, valizade...@gmail.com wrote: i have a ntp server based on Raspberry Pi3 with PPS (from u-blox6 ). i have also added a hardware clock to this system. SOME times there is a large offset(3-18 sec) on the SHM (ntp

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-02 Thread David Woolley
On 01/11/17 11:46, valizadeh...@gmail.com wrote: local lcok is there because my system is not connected to internet and i need to have the hwclock to keep the time during power-offs,i have disabled the pre installed fakeclock and used an I2c connected battery backed up RTC chip. Local clock

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-02 Thread David Taylor
On 01/11/2017 11:46, valizadeh...@gmail.com wrote: []> local lcok is there because my system is not connected to internet and i need to have the hwclock to keep the time during power-offs,i have disabled the pre installed fakeclock and used an I2c connected battery backed up RTC chip. the

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-02 Thread David Taylor
On 31/10/2017 08:50, valizade...@gmail.com wrote: server 127.127.1.1 minpoll 3 maxpoll 4 #hwcloak fudge 127.127.1.1 stratum 3 As Bill says, get rid of the local clock, and add some Internet sources. That way you can check whether your GPS is grossly wrong. The reach value seem wrong as

Re: [ntp:questions] false ticker after GPS coldreset

2017-11-02 Thread William Unruh
On 2017-10-31, valizade...@gmail.com wrote: > i have a ntp server based on Raspberry Pi3 with PPS (from u-blox6 ). i have > also added a hardware clock to this system. > > > SOME times there is a large offset(3-18 sec) on the SHM (ntp driver 28). What program is