[ntp:questions] ntp version 4.2.7p257-o

Mark C. Stephens marks at non-stop.com.au
Mon Feb 20 04:53:55 UTC 2012


> -----Original Message-----
> From: Dave Hart [mailto:hart at ntp.org]
> Sent: Monday, 20 February 2012 3:09 PM
> To: Mark C. Stephens
> Cc: questions at lists.ntp.org
> Subject: Re: ntp version 4.2.7p257-o
> 
> On Mon, Feb 20, 2012 at 02:57, Mark C. Stephens <marks at non-
> stop.com.au> wrote:
> > Unfortunately, this RX is locked at 9600, no way (I have discovered)
> > to change baud rate (do we stall call it that?!)
> 
> People often do refer to serial transmission rates as baud, but that'
> s incorrect when there's no modem involved, it's bits per second or bps.
> Higher transmission rate modems get more than one bit per baud, as I recall,
> so it's also incorrect to talk about a 33.6 baud modem to modem link.

[Mark C. Stephens] 
BPS it is then!
> 
> > Just curious which refclock driver it was, having never seen the line
> > drawing characters popping up in the debug output before.  :)
> 
> I have not experienced the garbled characters.  I was hoping your UART
> being overrun at high bps was the cause, but I'm sure it can manage
> 9600 cleanly.  So I'm not positive the pending fixes will cure that aspect.

[Mark C. Stephens] 
Ah, I was aware that Hal had added some extra counters in the driver, and I was thinking (novel concept there) that perhaps there is an error with the new counters.

Why I say this is that that it's not related to the serial input as per:

C:\Documents and Settings\Administrator>ntpq -c clockvar
associd=0 status=0011 1 event, clk_no_reply,
device="NMEA GPS Clock", timecode="$GPZDA,044739,20,02,2012,+00,00",
poll=564, noreply=1, badformat=0, baddata=0, fudgetime2=-480.000,
stratum=0, refid=GPS, flags=1

the timecode looks great there, as does clockstats:
55915 45557.497 127.127.20.1 delay 0.020001 $GPGGA
55915 45558.495 127.127.20.1 delay 0.020017 $GPGGA
55915 45559.495 127.127.20.1 delay 0.020008 $GPGGA
55915 45560.495 127.127.20.1 delay 0.020022 $GPGGA
55915 45561.495 127.127.20.1 delay 0.020017 $GPGGA
55915 45562.495 127.127.20.1 delay 0.020023 $GPGGA
55915 45563.495 127.127.20.1 delay 0.020025 $GPGGA
55915 45564.495 127.127.20.1 delay 0.020012 $GPGGA
55915 45565.495 127.127.20.1 delay 0.020020 $GPGGA
55915 45566.495 127.127.20.1 delay 0.020027 $GPGGA


But anyway, let's see what the new code brings.


Many thanks,
Mark



> 
> Cheers,
> Dave Hart




More information about the questions mailing list