Article: 2272 of comp.protocols.time.ntp From: kondor@orchid.cbk.poznan.pl (Robert) Newsgroups: comp.protocols.time.ntp Subject: Oncore VP Date: 17 Oct 2002 04:07:28 -0700 Organization: http://groups.google.com/ Lines: 45 Message-ID: <6aa18f20.0210170307.6e2e02c0@posting.google.com> NNTP-Posting-Host: 217.98.20.195 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1034852848 1913 127.0.0.1 (17 Oct 2002 11:07:28 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 17 Oct 2002 11:07:28 GMT Path: news.meer.net!sea-read.news.verio.net!dfw-artgen!iad-peer.news.verio.net!news.verio.net!news.maxwell.syr.edu!newsfeed.stanford.edu!postnews1.google.com!not-for-mail Xref: archive.mv.meer.net comp.protocols.time.ntp:2272 I hava a problem with my Motorola Oncore VP. When i trying synchronize with my server: myhost# ntpd -n -vvv ONCORE: Send @@Cj 2 Bad address ONCORE: Send @@Fa 2 ONCORE: Send @@Cj 2 ONCORE: Send @@Cg 3 ONCORE: Send @@Bb 3 ONCORE: Send @@Ek 3 /var/log/syslog Oct 17 09:53:12 tempus2 ntpd[20956]: ntpd 4.1.1a@1.791 Wed Oct 16 15:43:43 UTC 2002 (1) Oct 17 09:53:12 tempus2 ntpd[20956]: signal_no_reset: signal 13 had flags 4000000 Oct 17 09:53:12 tempus2 ntpd[20956]: precision = 14 usec Oct 17 09:53:12 tempus2 ntpd[20956]: kernel time discipline status 2040 My system: Debian3.0 kernel 2.4.19 with PPSPatch. NTP 4.1.1a /etc/ntp.conf server 193.79.237.14 server 193.79.237.30 pps /dev/oncore.pps.1 assert hardpps server 127.127.30.0 prefer logfile /var/log/ntpd /etc/ntp.oncore0: MODE 1 LON 5.2911542 LAT 52.4019797 HT 0 M DELAY 60 NS ASSERT What mean "Bad address" Regrads Robert Diak Article: 3172 of comp.protocols.time.ntp From: hmurray@suespammers.org (Hal Murray) Newsgroups: comp.protocols.time.ntp Subject: Re: GPS clock accuracy Date: Wed, 08 Jan 2003 08:37:08 -0000 Message-ID: X-newsreader: xrn 9.02 Sender: murray@glypnod (Hal Murray) References: <3E165F1E.7FEA3720@webmaster.com> <3E1B46AA.1CFA716D@mitel.com> X-Complaints-To: abuse@supernews.com Lines: 52 Path: news.meer.net!sea-read.news.verio.net!dfw-artgen!iad-peer.news.verio.net!news.verio.net!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.icl.net!newsfeed.fjserv.net!c03.atl99!news.webusenet.com!telocity-west!DIRECTV!sn-xit-03!sn-xit-01!sn-post-02!sn-post-01!supernews.com!corp.supernews.com!glypnod!hmurray Xref: archive.mv.meer.net comp.protocols.time.ntp:3172 >If I calculate correctly one of the GPS units would be about 6 km wrong >with its position! Sounds about right. :) I setup the GPSClock 200 to send both the $GPRMC and $GPGGA messages every minute. I hacked the NMEA driver to save both in the clockstats file. A few scripts lets you graph the number of satellites and it's (claimed) position and ... If I graph the reported lat/long vs the "average", I'm occasionally off more than 150 ft. Most of the time it's much better than that. That's in my home with the antenna inside my junk/spare/computer room. It runs out of satellites (un)reasonably often. Usually a couple of times per day. At work with the antenna outside and a good sky view, it's rarely off more than 75 ft, and rarely runs out of satellites. I spent some time trying to sanity check the lat/long it prints out with a USGS topo map. I think it agrees in the 100 yard range. I'm not sure I would bet much on closer than that. That's getting down to the range I can read the map and/or correct for coordinate quirks. My script says the average is: LAT=3726.0869 LONG=12212.2000 I think the units are degress*100 plus minutes and fractions of a minute. Might be 2 digits and fraction of seconds to the right of the decimal point. [I live in west Menlo Park if anybody wants to sanity check that.] The Z3801A discovers it's lat/long via a "survey" dance. I haven't gone through the exercise of checking the numbers, partly because I don't know which coordinate system it is using. (The 1927 vs 1983? is off by 100 ft or 100 yards in this area.) HP Z3801A says: N,+37,+26,+4.89000E+000 W,+122,+12,+1.56280E+001 +3.94200E+001 I think the units are degress, min, sec. Last number is elevation in meters. -- The suespammers.org mail server is located in California. So are all my other mailboxes. Please do not send unsolicited bulk e-mail or unsolicited commercial e-mail to my suespammers.org address or any of my other addresses. These are my opinions, not necessarily my employer's. I hate spam.