From: Jim Thompson <jim@netgate.com>
To: "thumbgps-devel@lists.bufferbloat.net"
<thumbgps-devel@lists.bufferbloat.net>
Subject: [Thumbgps-devel] navisys GR-601W gps on FreeBSD/NTP
Date: Sun, 3 Jun 2012 09:16:10 -0500 [thread overview]
Message-ID: <682FD158-B62B-4D41-A5BF-23F0C6029BA1@netgate.com> (raw)
after a long night of hacking, here is the result of about a 5 minute run on FreeBSD 8.3 (a pfSense 2.1 beta that was handy) running on a PC Engines Alix 3d2 board with
the Navisys GR-601W plugged in via USB
[2.1-BETA0][root@pfsense-beta.netgate.com]/dev(655): ntpdc -c kern
pll offset: 0.0131656 s
pll frequency: 25.385 ppm
maximum error: 0.025897 s
estimated error: 0.006287 s
status: 2001 pll nano
pll time constant: 4
precision: 1e-09 s
frequency tolerance: 496 ppm
pps frequency: 24.724 ppm
pps stability: 0.000 ppm
pps jitter: 0 s
calibration interval: 4 s
calibration cycles: 0
jitter exceeded: 0
stability exceeded: 0
calibration errors: 0
[2.1-BETA0][root@pfsense-beta.netgate.com]/dev(656): ntpdc -c "clockstat 127.127.20.0"
clock address: 127.127.20.0
clock type: Generic NMEA GPS Receiver (20)
last event: 0
current status: 0
number of polls: 21
no response to poll: 0
bad format responses: 0
bad data responses: 0
running time: 338
fudge time 1: 0.155000
fudge time 2: 0.000000
stratum: 0
reference ID: GPS
fudge flags: 0x5
[2.1-BETA0][root@pfsense-beta.netgate.com]/dev(657): ntpdc -c dm
remote local st poll reach delay offset disp
=======================================================================
*GPS_NMEA(0) 127.0.0.1 0 16 377 0.00000 0.018658 0.02373
LOCAL(0) 127.0.0.1 10 64 77 0.00000 0.000000 0.43401
.clock.isc.org 192.168.3.166 1 64 77 0.05998 0.045383 0.43512
.199.4.29.166 192.168.3.166 2 64 77 0.04831 0.026922 0.06511
[2.1-BETA0][root@pfsense-beta.netgate.com]/dev(658): ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*GPS_NMEA(0) .GPS. 0 l 3 16 377 0.000 17.541 4.836
LOCAL(0) .LOCL. 10 l 43 64 77 0.000 0.000 0.004
+199.4.29.166 64.90.182.55 2 u 39 64 77 48.317 26.922 19.527
+clock.isc.org .GPS. 1 u 37 64 77 59.994 45.383 10.124
[2.1-BETA0][root@pfsense-beta.netgate.com]/dev(659):
and after 10 minutes:
[2.1-BETA0][root@pfsense-beta.netgate.com]/dev(668): ntpdc -c "clockstat 127.127.20.0"
clock address: 127.127.20.0
clock type: Generic NMEA GPS Receiver (20)
last event: 0
current status: 0
number of polls: 42
no response to poll: 0
bad format responses: 0
bad data responses: 0
running time: 681
fudge time 1: 0.155000
fudge time 2: 0.000000
stratum: 0
reference ID: GPS
fudge flags: 0x5
[2.1-BETA0][root@pfsense-beta.netgate.com]/dev(669): ntpdc -c dm
remote local st poll reach delay offset disp
=======================================================================
*GPS_NMEA(0) 127.0.0.1 0 16 377 0.00000 0.026902 0.02632
LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03052
.clock.isc.org 192.168.3.166 1 64 377 0.05960 0.065447 0.03905
.199.4.29.166 192.168.3.166 2 64 377 0.04929 0.070362 0.05154
[2.1-BETA0][root@pfsense-beta.netgate.com]/dev(670): ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*GPS_NMEA(0) .GPS. 0 l 2 16 377 0.000 14.092 10.630
LOCAL(0) .LOCL. 10 l 46 64 377 0.000 0.000 0.004
+199.4.29.166 64.90.182.55 2 u 40 64 377 49.289 70.362 10.886
+clock.isc.org .GPS. 1 u 39 64 377 59.612 65.447 10.469
Note that PPS is not working
[2.1-BETA0][root@pfsense-beta.netgate.com]/dev(659): tail /var/log/ntpd.log
3 Jun 09:03:07 ntpd[61833]: synchronized to 199.4.29.166, stratum 2
3 Jun 09:03:07 ntpd[61833]: kernel time sync status change 2001
3 Jun 09:03:20 ntpd[61833]: refclock_nmea: time_pps_getcap failed: Inappropriate ioctl for device
3 Jun 09:03:23 ntpd[61833]: refclock_nmea: time_pps_getcap failed: Inappropriate ioctl for device
3 Jun 09:03:23 ntpd[61833]: refclock_nmea: time_pps_getcap failed: Inappropriate ioctl for device
3 Jun 09:03:25 ntpd[61833]: refclock_nmea: time_pps_getcap failed: Inappropriate ioctl for device
3 Jun 09:03:46 ntpd[61833]: synchronized to GPS_NMEA(0), stratum 0
3 Jun 09:03:50 ntpd[61833]: refclock_nmea: time_pps_getcap failed: Inappropriate ioctl for device
3 Jun 09:04:14 ntpd[61833]: refclock_nmea: time_pps_getcap failed: Inappropriate ioctl for device
3 Jun 09:08:34 ntpd[61833]: refclock_nmea: time_pps_getcap failed: Inappropriate ioctl for device
Will investigate.
Jim
next reply other threads:[~2012-06-03 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 14:16 Jim Thompson [this message]
2012-06-03 15:50 ` Ron Frazier (NTP)
[not found] ` <cb3d7ca5-6039-410f-9eb9-38c833e1cc6e@email.android.com>
[not found] ` <5F4AC3BC-3E72-4003-962A-2EA502B3015A@netgate.com>
2012-06-04 1:46 ` Ron Frazier (NTP)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=682FD158-B62B-4D41-A5BF-23F0C6029BA1@netgate.com \
--to=jim@netgate.com \
--cc=thumbgps-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox