refclock 28 gone wacky on me

[Gary E. Miller]

Yo Mike!

On Thu, 9 Jun 2016 18:21:32 -0400
Mike <bellyacres at gmail.com> wrote:

> Is seeing NTP0 twice like this typical? 

I'm looking at the code, maybe a couple of things to double check.

Can you send me, off list, the output of this command, about
60 seconds worth should do it.  As long as is captures a few good 
PPS pulses.

	# gpsd -nND 9 /dev/ttyXX |& fgrep PPS > text.log

It should look like this:

gpsd:PROG: KPPS:/dev/ttyUSB1 assert  1465514365.099491950, sequence: 3, clear   1465514364.999509328, sequence: 3 - using: assert
gpsd:PROG: KPPS:/dev/ttyUSB1 Assert cycle: 1000032, duration:   99982 @  1465514365.099491950
gpsd:RAW: PPS:/dev/ttyUSB1 Assert pps-detect changed to 1
gpsd:PROG: PPS:/dev/ttyUSB1 Assert cycle: 1000032, duration:   99982 @  1465514365.099491950
gpsd:PROG: PPS:/dev/ttyUSB1 Assert rejected 1Hz trailing edge
gpsd:PROG: KPPS:/dev/ttyUSB1 assert  1465514365.099491950, sequence: 3, clear   1465514365.999596356, sequence: 4 - using: clear
gpsd:PROG: KPPS:/dev/ttyUSB1 Clear cycle: 1000087, duration:  900104 @  1465514365.999596356
gpsd:RAW: PPS:/dev/ttyUSB1 Clear pps-detect changed to 0
gpsd:PROG: PPS:/dev/ttyUSB1 Clear cycle: 1000087, duration:  900104 @  1465514365.999596356
gpsd:RAW: PPS:/dev/ttyUSB1 Clear categorized 1Hz leading edge
gpsd:RAW: PPS chrony_send  1465514366.000000000 @  1465514365.999596356 Offset: 0.000403644
gpsd:INFO: PPS:/dev/ttyUSB1 Clear hooks called clock:  1465514365.999596356 real:  1465514366.000000000: accepted chrony sock
gpsd:PROG: PPS:/dev/ttyUSB1 Clear accepted chrony sock @  1465514365.999596356 offset  0.000403644



RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at rellim.com  Tel:+1 541 382 8588
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ntpsec.org/pipermail/devel/attachments/20160609/1a99b02f/attachment.bin>