"xyz-2041" <xyz2...@gmail.com> wrote in message
news:1ae0f584-2dd7-4244-8a58-0c31df806...@r33g2000yqb.googlegroups.com...
OK. Couldn't get the Oncore unit to work in any way
shape or form. I bought a DB9 LED tester like this:
<http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=260546635257>
Had PPS going to pin 1, DATA OUT to pin 2, and DATA IN to pin 3.
Still
no good.
Bought a Garmin GPS 25-LVC, put it in an enclosure, commented
out the Oncore driver and added to ntp.conf:
# Garmin / PPS driver:
server 127.127.20.0 prefer
fudge 127.127.20.0 refid GPS
Restarted:
/etc/rc.d/ntpd restart
Checking the status:
# ntpq -c pe
remote refid st t when poll reach delay
offset jitter
==========================================================
xGPS_NMEA(0) .GPS. 0 l 15 64 377 0.000
-716.52 105.934
Looks like it is being read, but is off by quite a bit. Any ideas on
how
to get it to behave?
with an offset of -716ms, NTP is unlikely to sync to it. Any chance that
you are syncing to the wrong edge of the PPS signal, and that you need to
use one of the fudge settings to invert the polarity?
http://www.eecis.udel.edu/~mills/ntp/html/drivers/driver20.html
"flag2 0 | 1
If PPS signal processing is enabled, capture the pulse on the rising
edge if 0 (default); capture on the falling edge if 1. "
Just a suggestion.
Good luck,
David
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
