Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-19 Thread Gary E. Miller
Yo Hal! On Sun, 19 Jun 2016 17:24:56 -0700 Hal Murray wrote: > g...@rellim.com said: > > Yes, that is expected. You need to tetll the Skytrazzq to force > > the top of the second, and save to flash. > > What does that mean? The Skytraq GPS, and some others, have two modes they can report t

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-19 Thread Hal Murray
g...@rellim.com said: > Yes, that is expected. You need to tetll the Skytrazzq to force the top of > the second, and save to flash. What does that mean? bellyac...@gmail.com said: > Did that which is why I didn't understand the delivery coming at near the > end of the second. It appears tho

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-19 Thread Gary E. Miller
Yo Mike! On Sun, 19 Jun 2016 18:45:45 -0400 Mike wrote: > > Which is why I asked what your other chimers say. > +199.102.46.75 ( .GPS.1 u 61 64 377 39.468 6.354 2.236 > +fairy.mattnordh 192.5.41.40 2 u 37 64 377 60.559 3.875 0.986 > -origin.towfowi. 204.9.54.1

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-19 Thread Mike
On 06/19/2016 06:14 PM, Gary E. Miller wrote: Yo Mike! On Sun, 19 Jun 2016 17:46:48 -0400 Mike wrote: What do your other chimers in 'ntpq -p show'? Youu still have not confirmmed which PPS edge you are on. The leading or trailing. I'll likely put an arrow through this module before I'm abl

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-19 Thread Gary E. Miller
Yo Mike! On Sun, 19 Jun 2016 17:46:48 -0400 Mike wrote: > > What do your other chimers in 'ntpq -p show'? Youu still have not > > confirmmed which PPS edge you are on. The leading or trailing. > I'll likely put an arrow through this module before I'm able to get a > scope hooked up too it!

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-19 Thread Mike
On 06/19/2016 04:23 PM, Gary E. Miller wrote: Yo Mike! ` On Sun, 19 Jun 2016 15:59:16 -0400 Mike wrote: On 06/10/2016 03:17 PM, Gary E. Miller wrote: Yo Eric! On Fri, 10 Jun 2016 03:49:22 -0400 "Eric S. Raymond" wrote: That's... very weird. I've never seen it happen. But it would ex

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-19 Thread Gary E. Miller
Yo Mike! ` On Sun, 19 Jun 2016 15:59:16 -0400 Mike wrote: > On 06/10/2016 03:17 PM, Gary E. Miller wrote: > > Yo Eric! > > > > On Fri, 10 Jun 2016 03:49:22 -0400 > > "Eric S. Raymond" wrote: > > > >> That's... very weird. I've never seen it happen. > > But it would explain some old compla

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-19 Thread Mike
On 06/10/2016 03:17 PM, Gary E. Miller wrote: Yo Eric! On Fri, 10 Jun 2016 03:49:22 -0400 "Eric S. Raymond" wrote: That's... very weird. I've never seen it happen. But it would explain some old complaints. Now that we know which Skytraq option it is, I recall always selecting the workaroun

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-10 Thread Gary E. Miller
Yo Eric! On Fri, 10 Jun 2016 03:49:22 -0400 "Eric S. Raymond" wrote: > That's... very weird. I've never seen it happen. But it would explain some old complaints. Now that we know which Skytraq option it is, I recall always selecting the workaround. > It sounds as though for some crazy reason

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-09 Thread Gary E. Miller
Yo Hal! On Thu, 09 Jun 2016 20:46:58 -0700 Hal Murray wrote: > e...@thyrsus.com said: > > That's odd. The normal semtence budget including GPGSV should fit > > inside a second. Are you getting some kind of $PMTK thing that > > pushes it over? > > I'm using gpsmon to watch the output. Ther

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-09 Thread Gary E. Miller
Yo Hal! On Thu, 09 Jun 2016 17:29:19 -0700 Hal Murray wrote: > > Can you send me the output of this when it fails: > > Not anytime soon. It's working correctly and I can't predict when it > will fail. Luckily we have a hard test case to work on. But, I have found a way to predict some of t

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-09 Thread Hal Murray
> Can you send me the output of this when it fails: Not anytime soon. It's working correctly and I can't predict when it will fail. g...@rellim.com said: > Well, then not the case at hand. the current problem is two edges per > second, 500 milliSec apart. How would an extra pulse at 500 ms

Re: [gpsd-dev] refclock 28 gone wacky on me

2016-06-09 Thread Gary E. Miller
Yo Hal! On Thu, 09 Jun 2016 17:04:08 -0700 Hal Murray wrote: > > GPS module is a ST22, SkyTraq Venus 6 chipset. > [ntpq -p shows PPS link off by a second.] > > It's a gpsd bug/quirk. I've seen the same thing on a PC with a Venus > chip connected via USB. > > I mentioned it a month or two ag