Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04
On Fri, Mar 30, 2012 at 15:58, David Lord wrote: > If you need to use 127.127.22 driver I'd suggest to use ntpd > v4.2.6p3. I don't know if parallel port pps works with the type > 20 driver. It does as long as /dev/gpspps0 (or whichever unit number) is linked to the correct device to use with PPSAPI. In other words, NMEA unit X when PPSAPI is enabled looks first for /dev/gpsppsX, and if that doesn't exist, attempts PPSAPI using the same /dev/gpsX device being used for NMEA data. Cheers, Dave Hart ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04
G wrote: update status for yesterday test: #ntpq -p remote refid st t when poll reach delay offset jitter == xGPS_NMEA(1) .GPS.0 l58 3770.000 -256.03 3.906 xtb.mircx.com64.147.116.229 2 u 25 64 377 57.804 226.565 21.617 remote refid st t when poll reach delay offset jitter == xGPS_NMEA(1) .GPS.0 l78 3770.000 -249.14 3.906 xtb.mircx.com64.147.116.229 2 u 32 64 377 57.804 226.565 17.471 # ntptime ntp_gettime() returns code 0 (OK) time d3202393.1dcde5c4 Fri, Mar 30 2012 8:20:35.116, (.116423510), maximum error 1779138 us, estimated error 39027 us, TAI offset 0 ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset 0.000 us, frequency -92.524 ppm, interval 1 s, maximum error 1779138 us, estimated error 39027 us, status 0x2007 (PLL,PPSFREQ,PPSTIME,NANO), time constant 3, precision 0.001 us, tolerance 500 ppm, # ntptime ntp_gettime() returns code 0 (OK) time d3202394.eeafaafc Fri, Mar 30 2012 8:20:36.932, (.932368988), maximum error 1779638 us, estimated error 39027 us, TAI offset 0 ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset 0.000 us, frequency -92.524 ppm, interval 1 s, maximum error 1779638 us, estimated error 39027 us, status 0x2007 (PLL,PPSFREQ,PPSTIME,NANO), time constant 3, precision 0.001 us, tolerance 500 ppm, # ntpq -p remote refid st t when poll reach delay offset jitter == xGPS_NMEA(1) .GPS.0 l68 3770.000 -247.00 4.208 xtb.mircx.com64.147.116.229 2 u 39 64 377 57.804 226.565 17.471 root@test12041:/home/ntp-4.2.6p5# ntpq -p remote refid st t when poll reach delay offset jitter == xGPS_NMEA(1) .GPS.0 l-8 3770.000 -244.15 4.163 xtb.mircx.com64.147.116.229 2 u 57 64 377 57.804 226.565 17.471 root@test12041:/home/ntp-4.2.6p5# date Fri Mar 30 08:22:23 EDT 2012 root@test12041:~# uname -a Linux test12041 3.2.0-17-generic-pae #27-Ubuntu SMP Fri Feb 24 15:59:25 UTC 2012 i686 i686 i386 GNU/Linux I use ntp-4.2.6p5. should I try latest 4.2.7? thanks your attention, geng - Original Message - From: G To: Dave Hart Cc: "questions@lists.ntp.org" Sent: Thursday, March 29, 2012 1:17 PM Subject: Re: Trimble Resolution SMT on Ubuntu 12.04 Dave, thanks for your email. I change my conf as your suggest: --- server 127.127.20.1 mode 18 prefer minpoll 3 maxpoll 3 peer 0.ca.pool.ntp.org fudge 127.127.20.1 time2 0. fudge 127.127.20.1 flag1 1 flag3 1 and I link pps0 to gpspps1: -- #ln -s /dev/pps0 /dev/gpspps1 # ppstest /dev/gpspps1 trying PPS source "/dev/gpspps1" found PPS source "/dev/gpspps1" ok, found 1 source(s), now start fetching data... source 0 - assert 1333040090.999603804, sequence: 8631 - clear 0.0, sequence: 0 source 0 - assert 1333040091.999709923, sequence: 8632 - clear 0.0, sequence: 0 source 0 - assert 1333040092.999797692, sequence: 8633 - clear 0.0, sequence: 0 source 0 - assert 1333040093.999884565, sequence: 8634 - clear 0.0, sequence: 0 -- also update system time before run ntpd: -- root@test12041:~# ntpdate 0.ca.pool.ntp.org 29 Mar 10:28:42 ntpdate[1129]: adjust time server 129.128.5.210 offset -0.464322 sec root@test12041:~# ntpdate 0.ca.pool.ntp.org 29 Mar 10:28:52 ntpdate[1130]: adjust time server 209.167.68.100 offset -0.457408 sec root@test12041:~# ntpdate 1.ca.pool.ntp.org 29 Mar 10:29:06 ntpdate[1131]: adjust time server 216.194.70.2 offset -0.450851 sec -- root@test12041:# ntptime ntp_gettime() returns code 0 (OK) time d31ef2ca.2940fec0 Thu, Mar 29 2012 10:40:10.161, (.161148460), maximum error 8043832 us, estimated error 34655 us, TAI offset 0 ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset -80566.987 us, frequency 21.606 ppm, interval 1 s, maximum error 8043832 us, estimated error 34655 us, status 0x2007 (PLL,PPSFREQ,PPSTIME,NANO), time constant 3, precision 0.001 us, tolerance 500 ppm, root@test12041:# ntpq -p remote refid st t when poll reach delay offset jitter == GPS_NMEA(1) .GPS.0 l-800.0000.000 0.000 caustique.anox. .INIT. 16
Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04
On Fri, Mar 30, 2012 at 12:44, G wrote: > root@test12041:/home/ntp-4.2.6p5# ntpq -p > remote refid st t when poll reach delay offset jitter > == > xGPS_NMEA(1) .GPS. 0 l - 8 377 0.000 -244.15 4.163 > xtb.mircx.com 64.147.116.229 2 u 57 64 377 57.804 226.565 17.471 > > root@test12041:/home/ntp-4.2.6p5# date > Fri Mar 30 08:22:23 EDT 2012 > root@test12041:~# uname -a > Linux test12041 3.2.0-17-generic-pae #27-Ubuntu SMP Fri Feb 24 15:59:25 UTC > 2012 i686 i686 i386 GNU/Linux > > I use ntp-4.2.6p5. should I try latest 4.2.7? I would spend more time experimenting with fudge time2 values to try to get your NMEA and network offsets closer. They are almost 500 msec apart in the ntpq output above. They need to come within 400 msec before the PPS will take over. Cheers, Dave Hart ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04
update status for yesterday test: #ntpq -p remote refid st t when poll reach delay offset jitter == xGPS_NMEA(1) .GPS. 0 l 5 8 377 0.000 -256.03 3.906 xtb.mircx.com 64.147.116.229 2 u 25 64 377 57.804 226.565 21.617 remote refid st t when poll reach delay offset jitter == xGPS_NMEA(1) .GPS. 0 l 7 8 377 0.000 -249.14 3.906 xtb.mircx.com 64.147.116.229 2 u 32 64 377 57.804 226.565 17.471 # ntptime ntp_gettime() returns code 0 (OK) time d3202393.1dcde5c4 Fri, Mar 30 2012 8:20:35.116, (.116423510), maximum error 1779138 us, estimated error 39027 us, TAI offset 0 ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset 0.000 us, frequency -92.524 ppm, interval 1 s, maximum error 1779138 us, estimated error 39027 us, status 0x2007 (PLL,PPSFREQ,PPSTIME,NANO), time constant 3, precision 0.001 us, tolerance 500 ppm, # ntptime ntp_gettime() returns code 0 (OK) time d3202394.eeafaafc Fri, Mar 30 2012 8:20:36.932, (.932368988), maximum error 1779638 us, estimated error 39027 us, TAI offset 0 ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset 0.000 us, frequency -92.524 ppm, interval 1 s, maximum error 1779638 us, estimated error 39027 us, status 0x2007 (PLL,PPSFREQ,PPSTIME,NANO), time constant 3, precision 0.001 us, tolerance 500 ppm, # ntpq -p remote refid st t when poll reach delay offset jitter == xGPS_NMEA(1) .GPS. 0 l 6 8 377 0.000 -247.00 4.208 xtb.mircx.com 64.147.116.229 2 u 39 64 377 57.804 226.565 17.471 root@test12041:/home/ntp-4.2.6p5# ntpq -p remote refid st t when poll reach delay offset jitter == xGPS_NMEA(1) .GPS. 0 l - 8 377 0.000 -244.15 4.163 xtb.mircx.com 64.147.116.229 2 u 57 64 377 57.804 226.565 17.471 root@test12041:/home/ntp-4.2.6p5# date Fri Mar 30 08:22:23 EDT 2012 root@test12041:~# uname -a Linux test12041 3.2.0-17-generic-pae #27-Ubuntu SMP Fri Feb 24 15:59:25 UTC 2012 i686 i686 i386 GNU/Linux I use ntp-4.2.6p5. should I try latest 4.2.7? thanks your attention, geng - Original Message - From: G To: Dave Hart Cc: "questions@lists.ntp.org" Sent: Thursday, March 29, 2012 1:17 PM Subject: Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04 Dave, thanks for your email. I change my conf as your suggest: --- server 127.127.20.1 mode 18 prefer minpoll 3 maxpoll 3 peer 0.ca.pool.ntp.org fudge 127.127.20.1 time2 0. fudge 127.127.20.1 flag1 1 flag3 1 and I link pps0 to gpspps1: -- #ln -s /dev/pps0 /dev/gpspps1 # ppstest /dev/gpspps1 trying PPS source "/dev/gpspps1" found PPS source "/dev/gpspps1" ok, found 1 source(s), now start fetching data... source 0 - assert 1333040090.999603804, sequence: 8631 - clear 0.0, sequence: 0 source 0 - assert 1333040091.999709923, sequence: 8632 - clear 0.0, sequence: 0 source 0 - assert 1333040092.999797692, sequence: 8633 - clear 0.0, sequence: 0 source 0 - assert 1333040093.999884565, sequence: 8634 - clear 0.0, sequence: 0 -- also update system time before run ntpd: -- root@test12041:~# ntpdate 0.ca.pool.ntp.org 29 Mar 10:28:42 ntpdate[1129]: adjust time server 129.128.5.210 offset -0.464322 sec root@test12041:~# ntpdate 0.ca.pool.ntp.org 29 Mar 10:28:52 ntpdate[1130]: adjust time server 209.167.68.100 offset -0.457408 sec root@test12041:~# ntpdate 1.ca.pool.ntp.org 29 Mar 10:29:06 ntpdate[1131]: adjust time server 216.194.70.2 offset -0.450851 sec -- root@test12041:# ntptime ntp_gettime() returns code 0 (OK) time d31ef2ca.2940fec0 Thu, Mar 29 2012 10:40:10.161, (.161148460), maximum error 8043832 us, estimated error 34655 us, TAI offset 0 ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset -80566.987 us, frequency 21.606 ppm, interval 1 s, maximum error 8043832 us, estimated error 34655 us, status 0x2007 (PLL,PPSFREQ,PPSTIME,NANO), time constant 3, precision 0.001 us, tolerance 500 ppm, root@test12041:# ntpq -p remote refid st t when poll reach delay offset jitter == GPS_NMEA(1) .GPS. 0 l - 8 0 0.000 0.000
Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04
On Thu, Mar 29, 2012 at 17:17, G wrote: > remote refid st t when poll reach delay offset jitter > == > GPS_NMEA(1) .GPS. 0 l - 8 0 0.000 0.000 0.000 > caustique.anox. .INIT. 16 u - 64 0 0.000 0.000 0.000 > remote refid st t when poll reach delay offset jitter > == > *GPS_NMEA(1) .GPS. 0 l 2 8 7 0.000 -73.419 22.031 > caustique.anox. .INIT. 16 u - 64 0 0.000 0.000 0.000 > > remote refid st t when poll reach delay offset jitter > == > *GPS_NMEA(1) .GPS. 0 l 5 8 377 0.000 4.693 3.906 > caustique.anox. .INIT. 16 u - 64 0 0.000 0.000 0.000 > root@test12041:/home/test# ntpq -p > remote refid st t when poll reach delay offset jitter > == > *GPS_NMEA(1) .GPS. 0 l - 8 377 0.000 4.945 3.906 > caustique.anox. .INIT. 16 u - 64 0 0.000 0.000 0.000 > root@test12041:/home/test# ntpq -p > remote refid st t when poll reach delay offset jitter > == > oGPS_NMEA(1) .GPS. 0 l 2 8 377 0.000 -0.581 3.906 > caustique.anox. .STEP. 16 u - 1024 0 0.000 0.000 0.000 > > remote refid st t when poll reach delay offset jitter > == > oGPS_NMEA(1) .GPS. 0 l 2 8 377 0.000 0.105 3.906 > caustique.anox. .STEP. 16 u - 1024 0 0.000 0.000 0.000 > > remote refid st t when poll reach delay offset jitter > == > oGPS_NMEA(1) .GPS. 0 l 1 8 377 0.000 0.838 3.906 > caustique.anox. 128.233.150.93 2 u 698 1024 1 5.516 994.460 3.906 > > remote refid st t when poll reach delay offset jitter > == > oGPS_NMEA(1) .GPS. 0 l 7 8 377 0.000 1.849 3.906 > caustique.anox. 128.233.150.93 2 u 1024 1024 1 5.516 994.460 3.906 > > > remote refid st t when poll reach delay offset jitter > == > xGPS_NMEA(1) .GPS. 0 l 5 8 377 0.000 1.460 3.906 > xcaustique.anox. 128.233.150.93 2 u 59 64 377 4.457 995.520 3.906 > > this is result for ntpd 3hours running . > > I guess not good . I will let it run over night to see what change. It appears you've latched onto the wrong second, perhaps helped by connectivity problems to the single pool server. Once it became reachable the problem is clear. Use fudge time2 -0.600 so that ntpd is steering the clock closer to correct when using only NMEA end of sentence timestamps, so that when the clock is believed to be close enough to engage PPS, it's indeed close and not close to a second off. If you pay attention to the offset closely during startup, you can tune time2 closer to minimize startup transients. Cheers, Dave Hart ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04
good . I will let it run over night to see what change. thanks, geng - Original Message - From: Dave Hart To: G Cc: "questions@lists.ntp.org" Sent: Thursday, March 29, 2012 12:56 AM Subject: Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04 On Mon, Mar 26, 2012 at 16:06, G wrote: > I use Trimble Resolution SMT to sync time for a Ubuntu 12.04 server (kernel > 3.2.0). > > Trimble send NMEA to /dev/ttyUSB1(9600 8N1) on Ubuntu server > PPS signal connect ACK pin on /dev/parport0 > . Ubuntu load Linux-PPS module( PPS_parport clear_wait=0) to > create PPS device /dev/pps0 > > I use verify the /dev/pps0 using rising edge by "ppstest /dev/pps0" > > trying PPS source "/dev/pps0" > found PPS source "/dev/pps0" > ok, found 1 source(s), now start fetching data... > source 0 - assert 1332775909.500413150, sequence: 249302 - clear > 0.0, sequence: 0 > source 0 - assert 1332775910.500456132, sequence: 249303 - clear > 0.0, sequence: 0 > source 0 - assert 1332775911.500499213, sequence: 249304 - clear > 0.0, sequence: 0 > --- > To verify the NMEA message , I link /dev/ttyUSB1 to /dev/gps1 > --- > #cat /dev/gps1 > $GPRMC,153343.000,A,4529.904930,N,07343.904831,W,0.241,325,260312,,,A*6F > $GPGGA,153344.000,4529.905010,N,07343.904879,W,1,3,3.17,12.368,M,-32.087,M,,*5E > --- > I create the /etc/ntp.conf: > - > server 127.127.20.1 mode 17 prefer # NMEA RMC/GGA 9600bps mode 17 is 16 (9600) plus 1 (select RMC) > fudge 127.127.20.1 time2 0.01 > > server 127.127.22.0 minpoll 4 maxpoll 4 # PPS ATOM > fudge 127.127.22.0 flag2 0 flag3 1 > > driftfile /var/lib/ntp/ntp.drift > -- > after ntpd run 48hours, ntpq -p: > > remote refid st t when poll reach delay offset jitter > == > xGPS_NMEA(1) .GPS. 0 l 44 64 377 0.000 -214.54 25.464 > xPPS(0) .PPS. 0 l 11 16 377 0.000 -174.60 4.981 > > > I have no idea why I got this result . what do I miss for config? by the way > , I compile ntpd from source , not using ntpd from Ubuntu. I'm not sure why you're seeing that result. First, flag3 1 doesn't appear to be working, in that the offset of the PPS is far away. Moreover, when feasible I suggest using NMEA's built-in PPSAPI support. You should be able to to remove the PPS refclock and add flag1 1 to the fudge 127.127.20.1 line, then add a soft link from /dev/gpspps1 to /dev/pps0. This eliminates the risk of two clocks whose confidence intervals don't overlap both being tossed as falsetickers, as your PPS will be provided via the same refclock. Good luck, Dave Hart ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04
Geng, You could try mode 18 to use GPGGA instead of GPRMC. You're way over my head trying to use PPS on a parallel port. You might want to put noselect on the server lines for all non gps servers, just for testing. Make sure you're getting output from the gps immediately before starting NTPD. You may have to reestablish your symbolic links if you reboot. I suggest commenting out the lines in your ntp.conf file which relate to PPS and just trying to get the NMEA working by itself. Then go back and troubleshoot PPS once you know NMEA is working. If you can shut off all the NMEA sentences but the one you want, you'll get less jitter on NMEA. That won't affect you much once pps is working. On Windows, I was able to get + / - 10 ms offset performance from GPS time using NMEA only data through USB. Note that NMEA data will drift over time, by a substantial margin, on many gps's. When I started forwarding pps to the DCD pin of the serial port, but still going through a Trendnet TU-S9 serial - USB converter, I was able to get + / - 1 ms performance. As I mentioned in another thread, on my other computer with a real serial port, I'm getting + / - 50 us performance. Other than that, someone with more knowledge than me will have to help you. Good luck. Sincerely, Ron On 3/29/2012 9:59 AM, G wrote: Hi Ron, Thanks a lot for your help. I change my conf as your suggest: server 127.127.22.0 minpoll 3 maxpoll 3 #ATOM PPS fudge 127.127.22.0 flag2 0 server 127.127.20.1 mode 17 prefer minpoll 3 maxpoll 3 #NMEA RMC 9600 fudge 127.127.20.1 time2 0. driftfile /var/lib/ntp/ntp.drift unfortunately, result is not much different. geng - Original Message - From: Ron Frazier (NTP) To: Cc: "questions@lists.ntp.org" Sent: Monday, March 26, 2012 4:19 PM Subject: Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04 Hi Geng, I don't know if this will help or not, but the following things came to mind. I am running Windows at the moment, but Linux should be similar. I plan to try all this in Ubuntu eventually. When I was using NMEA only data, I had to have a bigger fudge factor, like this: fudge 127.127.20.5 time2 0.3710 refid GPS1 # use WITHOUT PPS However, when I started using PPS, I found that the fudge factor was messing things up, so now I use this: fudge 127.127.20.5 time2 0. refid GPS1 # use WITH PPS Note that I stuck the fudge factor in there for readability. However, its value is 0. The other thing that occurred is that your clock may be too far out from gps time to begin with. Try shutting down NTPD. Note, if you compiled NTP yourself, the startup and shutdown scripts may not be in the right places. I think the command is: sudo /etc/init.d ntp stop Then run this command to sync your clock with the NIST server in New York. If you're not in the US, substitute another server name. ntpdate -b nist1-ny.ustiming.org Now your clock should be very close to NIST or UTC. Now, restart NTPD. sudo /etc/init.d ntp start Wait a few minutes and run ntpq -p to see what's happening. Also, make sure NTPD is reading the correct config file and that you don't have two of them around or something. Finally, I'd recommend putting minpoll 4 maxpoll 4 on your NMEA line to match your PPS line. I'm using a value of 3 on mine, which polls every 8 seconds. Sincerely, Ron On 3/26/2012 12:06 PM, G wrote: I use Trimble Resolution SMT to sync time for a Ubuntu 12.04 server (kernel 3.2.0). Trimble send NMEA to /dev/ttyUSB1(9600 8N1) on Ubuntu server PPS signal connect ACK pin on /dev/parport0 . Ubuntu load Linux-PPS module( PPS_parport clear_wait=0) to create PPS device /dev/pps0 I use verify the /dev/pps0 using rising edge by "ppstest /dev/pps0" trying PPS source "/dev/pps0" found PPS source "/dev/pps0" ok, found 1 source(s), now start fetching data... source 0 - assert 1332775909.500413150, sequence: 249302 - clear 0.0, sequence: 0 source 0 - assert 1332775910.500456132, sequence: 249303 - clear 0.0, sequence: 0 source 0 - assert 1332775911.500499213, sequence: 249304 - clear 0.0, sequence: 0 --- To verify the NMEA message , I link /dev/ttyUSB1 to /dev/gps1 --- #cat /dev/gps1 $GPRMC,153343.000,A,4529.904930,N,07343.904831,W,0.241,325,260312,,,A*6F $GPGGA,153344.000,4529.905010,N,07343.904879,W,1,3,3.17,12.368,M,-32.087,M,,*5E -
Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04
Hi Ron, Thanks a lot for your help. I change my conf as your suggest: server 127.127.22.0 minpoll 3 maxpoll 3 #ATOM PPS fudge 127.127.22.0 flag2 0 server 127.127.20.1 mode 17 prefer minpoll 3 maxpoll 3 #NMEA RMC 9600 fudge 127.127.20.1 time2 0. driftfile /var/lib/ntp/ntp.drift unfortunately, result is not much different. geng - Original Message - From: Ron Frazier (NTP) To: Cc: "questions@lists.ntp.org" Sent: Monday, March 26, 2012 4:19 PM Subject: Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04 Hi Geng, I don't know if this will help or not, but the following things came to mind. I am running Windows at the moment, but Linux should be similar. I plan to try all this in Ubuntu eventually. When I was using NMEA only data, I had to have a bigger fudge factor, like this: fudge 127.127.20.5 time2 0.3710 refid GPS1 # use WITHOUT PPS However, when I started using PPS, I found that the fudge factor was messing things up, so now I use this: fudge 127.127.20.5 time2 0. refid GPS1 # use WITH PPS Note that I stuck the fudge factor in there for readability. However, its value is 0. The other thing that occurred is that your clock may be too far out from gps time to begin with. Try shutting down NTPD. Note, if you compiled NTP yourself, the startup and shutdown scripts may not be in the right places. I think the command is: sudo /etc/init.d ntp stop Then run this command to sync your clock with the NIST server in New York. If you're not in the US, substitute another server name. ntpdate -b nist1-ny.ustiming.org Now your clock should be very close to NIST or UTC. Now, restart NTPD. sudo /etc/init.d ntp start Wait a few minutes and run ntpq -p to see what's happening. Also, make sure NTPD is reading the correct config file and that you don't have two of them around or something. Finally, I'd recommend putting minpoll 4 maxpoll 4 on your NMEA line to match your PPS line. I'm using a value of 3 on mine, which polls every 8 seconds. Sincerely, Ron On 3/26/2012 12:06 PM, G wrote: > I use Trimble Resolution SMT to sync time for a Ubuntu 12.04 server (kernel > 3.2.0). > > Trimble send NMEA to /dev/ttyUSB1(9600 8N1) on Ubuntu server > PPS signal connect ACK pin on /dev/parport0 . Ubuntu load Linux-PPS module( > PPS_parport clear_wait=0) to create PPS device /dev/pps0 > > I use verify the /dev/pps0 using rising edge by "ppstest /dev/pps0" > > trying PPS source "/dev/pps0" > found PPS source "/dev/pps0" > ok, found 1 source(s), now start fetching data... > source 0 - assert 1332775909.500413150, sequence: 249302 - clear > 0.0, sequence: 0 > source 0 - assert 1332775910.500456132, sequence: 249303 - clear > 0.0, sequence: 0 > source 0 - assert 1332775911.500499213, sequence: 249304 - clear > 0.0, sequence: 0 > --- > To verify the NMEA message , I link /dev/ttyUSB1 to /dev/gps1 > --- > #cat /dev/gps1 > $GPRMC,153343.000,A,4529.904930,N,07343.904831,W,0.241,325,260312,,,A*6F > $GPGGA,153344.000,4529.905010,N,07343.904879,W,1,3,3.17,12.368,M,-32.087,M,,*5E > --- > I create the /etc/ntp.conf: > - > server 127.127.20.1 mode 17 prefer # NMEA RMC/GGA 9600bps > fudge 127.127.20.1 time2 0.01 > > server 127.127.22.0 minpoll 4 maxpoll 4 # PPS ATOM > fudge 127.127.22.0 flag2 0 flag3 1 > > driftfile /var/lib/ntp/ntp.drift > -- > after ntpd run 48hours, ntpq -p: > > remote refid st t when poll reach delay offset jitter > == > xGPS_NMEA(1) .GPS. 0 l 44 64 377 0.000 -214.54 25.464 > xPPS(0) .PPS. 0 l 11 16 377 0.000 -174.60 4.981 > > > I have no idea why I got this result . what do I miss for config? by the way > , I compile ntpd from source , not using ntpd from Ubuntu. > > > Thanks for your time to read my question. give me some light please. > > regards, > > geng > > -- (PS - If you email me and don't ge
Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04
On Mon, Mar 26, 2012 at 16:06, G wrote: > I use Trimble Resolution SMT to sync time for a Ubuntu 12.04 server (kernel > 3.2.0). > > Trimble send NMEA to /dev/ttyUSB1(9600 8N1) on Ubuntu server > PPS signal connect ACK pin on /dev/parport0 > . Ubuntu load Linux-PPS module( PPS_parport clear_wait=0) to > create PPS device /dev/pps0 > > I use verify the /dev/pps0 using rising edge by "ppstest /dev/pps0" > > trying PPS source "/dev/pps0" > found PPS source "/dev/pps0" > ok, found 1 source(s), now start fetching data... > source 0 - assert 1332775909.500413150, sequence: 249302 - clear > 0.0, sequence: 0 > source 0 - assert 1332775910.500456132, sequence: 249303 - clear > 0.0, sequence: 0 > source 0 - assert 1332775911.500499213, sequence: 249304 - clear > 0.0, sequence: 0 > --- > To verify the NMEA message , I link /dev/ttyUSB1 to /dev/gps1 > --- > #cat /dev/gps1 > $GPRMC,153343.000,A,4529.904930,N,07343.904831,W,0.241,325,260312,,,A*6F > $GPGGA,153344.000,4529.905010,N,07343.904879,W,1,3,3.17,12.368,M,-32.087,M,,*5E > --- > I create the /etc/ntp.conf: > - > server 127.127.20.1 mode 17 prefer # NMEA RMC/GGA 9600bps mode 17 is 16 (9600) plus 1 (select RMC) > fudge 127.127.20.1 time2 0.01 > > server 127.127.22.0 minpoll 4 maxpoll 4 # PPS ATOM > fudge 127.127.22.0 flag2 0 flag3 1 > > driftfile /var/lib/ntp/ntp.drift > -- > after ntpd run 48hours, ntpq -p: > > remote refid st t when poll reach delay offset jitter > == > xGPS_NMEA(1) .GPS. 0 l 44 64 377 0.000 -214.54 25.464 > xPPS(0) .PPS. 0 l 11 16 377 0.000 -174.60 4.981 > > > I have no idea why I got this result . what do I miss for config? by the way > , I compile ntpd from source , not using ntpd from Ubuntu. I'm not sure why you're seeing that result. First, flag3 1 doesn't appear to be working, in that the offset of the PPS is far away. Moreover, when feasible I suggest using NMEA's built-in PPSAPI support. You should be able to to remove the PPS refclock and add flag1 1 to the fudge 127.127.20.1 line, then add a soft link from /dev/gpspps1 to /dev/pps0. This eliminates the risk of two clocks whose confidence intervals don't overlap both being tossed as falsetickers, as your PPS will be provided via the same refclock. Good luck, Dave Hart ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Trimble Resolution SMT on Ubuntu 12.04
Hi Geng, I don't know if this will help or not, but the following things came to mind. I am running Windows at the moment, but Linux should be similar. I plan to try all this in Ubuntu eventually. When I was using NMEA only data, I had to have a bigger fudge factor, like this: fudge 127.127.20.5 time2 0.3710 refid GPS1 # use WITHOUT PPS However, when I started using PPS, I found that the fudge factor was messing things up, so now I use this: fudge 127.127.20.5 time2 0. refid GPS1 # use WITH PPS Note that I stuck the fudge factor in there for readability. However, its value is 0. The other thing that occurred is that your clock may be too far out from gps time to begin with. Try shutting down NTPD. Note, if you compiled NTP yourself, the startup and shutdown scripts may not be in the right places. I think the command is: sudo /etc/init.d ntp stop Then run this command to sync your clock with the NIST server in New York. If you're not in the US, substitute another server name. ntpdate -b nist1-ny.ustiming.org Now your clock should be very close to NIST or UTC. Now, restart NTPD. sudo /etc/init.d ntp start Wait a few minutes and run ntpq -p to see what's happening. Also, make sure NTPD is reading the correct config file and that you don't have two of them around or something. Finally, I'd recommend putting minpoll 4 maxpoll 4 on your NMEA line to match your PPS line. I'm using a value of 3 on mine, which polls every 8 seconds. Sincerely, Ron On 3/26/2012 12:06 PM, G wrote: I use Trimble Resolution SMT to sync time for a Ubuntu 12.04 server (kernel 3.2.0). Trimble send NMEA to /dev/ttyUSB1(9600 8N1) on Ubuntu server PPS signal connect ACK pin on /dev/parport0 . Ubuntu load Linux-PPS module( PPS_parport clear_wait=0) to create PPS device /dev/pps0 I use verify the /dev/pps0 using rising edge by "ppstest /dev/pps0" trying PPS source "/dev/pps0" found PPS source "/dev/pps0" ok, found 1 source(s), now start fetching data... source 0 - assert 1332775909.500413150, sequence: 249302 - clear 0.0, sequence: 0 source 0 - assert 1332775910.500456132, sequence: 249303 - clear 0.0, sequence: 0 source 0 - assert 1332775911.500499213, sequence: 249304 - clear 0.0, sequence: 0 --- To verify the NMEA message , I link /dev/ttyUSB1 to /dev/gps1 --- #cat /dev/gps1 $GPRMC,153343.000,A,4529.904930,N,07343.904831,W,0.241,325,260312,,,A*6F $GPGGA,153344.000,4529.905010,N,07343.904879,W,1,3,3.17,12.368,M,-32.087,M,,*5E --- I create the /etc/ntp.conf: - server 127.127.20.1 mode 17 prefer # NMEA RMC/GGA 9600bps fudge 127.127.20.1 time2 0.01 server 127.127.22.0 minpoll 4 maxpoll 4 # PPS ATOM fudge 127.127.22.0 flag2 0 flag3 1 driftfile /var/lib/ntp/ntp.drift -- after ntpd run 48hours, ntpq -p: remote refid st t when poll reach delay offset jitter == xGPS_NMEA(1) .GPS.0 l 44 64 3770.000 -214.54 25.464 xPPS(0) .PPS.0 l 11 16 3770.000 -174.60 4.981 I have no idea why I got this result . what do I miss for config? by the way , I compile ntpd from source , not using ntpd from Ubuntu. Thanks for your time to read my question. give me some light please. regards, geng -- (PS - If you email me and don't get a quick response, don't be concerned. I get about 300 emails per day from alternate energy mailing lists and such. I don't always see new messages very quickly. If you need a reply and have not heard from me in 1 - 2 weeks, send your message again.) Ron Frazier timekeepingdude AT c3energy.com ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] Trimble Resolution SMT on Ubuntu 12.04
I use Trimble Resolution SMT to sync time for a Ubuntu 12.04 server (kernel 3.2.0). Trimble send NMEA to /dev/ttyUSB1(9600 8N1) on Ubuntu server PPS signal connect ACK pin on /dev/parport0 . Ubuntu load Linux-PPS module( PPS_parport clear_wait=0) to create PPS device /dev/pps0 I use verify the /dev/pps0 using rising edge by "ppstest /dev/pps0" trying PPS source "/dev/pps0" found PPS source "/dev/pps0" ok, found 1 source(s), now start fetching data... source 0 - assert 1332775909.500413150, sequence: 249302 - clear 0.0, sequence: 0 source 0 - assert 1332775910.500456132, sequence: 249303 - clear 0.0, sequence: 0 source 0 - assert 1332775911.500499213, sequence: 249304 - clear 0.0, sequence: 0 --- To verify the NMEA message , I link /dev/ttyUSB1 to /dev/gps1 --- #cat /dev/gps1 $GPRMC,153343.000,A,4529.904930,N,07343.904831,W,0.241,325,260312,,,A*6F $GPGGA,153344.000,4529.905010,N,07343.904879,W,1,3,3.17,12.368,M,-32.087,M,,*5E --- I create the /etc/ntp.conf: - server 127.127.20.1 mode 17 prefer # NMEA RMC/GGA 9600bps fudge 127.127.20.1 time2 0.01 server 127.127.22.0 minpoll 4 maxpoll 4 # PPS ATOM fudge 127.127.22.0 flag2 0 flag3 1 driftfile /var/lib/ntp/ntp.drift -- after ntpd run 48hours, ntpq -p: remote refid st t when poll reach delay offset jitter == xGPS_NMEA(1) .GPS. 0 l 44 64 377 0.000 -214.54 25.464 xPPS(0) .PPS. 0 l 11 16 377 0.000 -174.60 4.981 I have no idea why I got this result . what do I miss for config? by the way , I compile ntpd from source , not using ntpd from Ubuntu. Thanks for your time to read my question. give me some light please. regards, geng ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Trimble Resolution SMT
In article <4be025aa.4050...@signaturealpha.com>, Marc Leclerc writes: > I am trying to have NTP use the trimble resolution SMT gps module, I > have tried other trimble clock driver without success so I assume that > one specific to the module has to be used. Unfortunately there does not > seems to be any way to search the mailing list to see if this was > discuss before. I would appreciate if anyone with information could get > back to me. I've just released a patch to RIPENCC driver (43). Maybe it can help you. http://wiki.enneenne.com/index.php/LinuxPPS_NTPD_support Gabor ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] Trimble Resolution SMT status
Hi, I suspect I have an anthena connection problem, ntpq -> cl reports baddata=1 + ILLEGAL DATE. It also outputs status=0x0015. There is no description of the status value in the doc I have, would anyone know what the status value of 0x0015 is and even better where can I find the description of those. ntpq> cl associd=0 status=0x0015, device="Trimble GPS (TSIP) receiver", timecode="\x10\x13/\x10\x03", poll=19, noreply=0, badformat=0, baddata=1, fudgetime1=20.000, stratum=0, refid=GPS, flags=0, refclock_time="", refclock_status="", refclock_format="Trimble TSIP", refclock_states="NOMINAL: 00:00:01 (0.08%); *ILLEGAL DATE: 00:19:38 (99.91%); running time: 00:19:39", trimble_version="0.8 (1909/4/2)" Thanks ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] Trimble Resolution SMT status
Hi, I suspect I have an anthena connection problem, ntpq -> cl reports baddata=1 + ILLEGAL DATE. It also outputs status=0x0015. There is no description of the status value in the doc I have, would anyone know what the status value of 0x0015 is and even better where can I find the description of those. ntpq> cl associd=0 status=0x0015, device="Trimble GPS (TSIP) receiver", timecode="\x10\x13/\x10\x03", poll=19, noreply=0, badformat=0, baddata=1, fudgetime1=20.000, stratum=0, refid=GPS, flags=0, refclock_time="", refclock_status="", refclock_format="Trimble TSIP", refclock_states="NOMINAL: 00:00:01 (0.08%); *ILLEGAL DATE: 00:19:38 (99.91%); running time: 00:19:39", trimble_version="0.8 (1909/4/2)" Thanks ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Trimble Resolution SMT
On 2010-05-05, Hal Murray wrote: > In article <4be025aa.4050...@signaturealpha.com>, > Marc Leclerc writes: > >>I am trying to have NTP use the trimble resolution SMT gps module, I >>have tried other trimble clock driver without success so I assume that >>one specific to the module has to be used. Unfortunately there does not >>seems to be any way to search the mailing list to see if this was >>discuss before. I would appreciate if anyone with information could get >>back to me. > >>I am trying to make this work on an embedded linux platform, I already >>have the linuxpps driver installed and have the /dev/pps0 node >>available. the module is wired to /dev/ttyS1. Using the clock driver for >>the palisade lead to wrong answer format messages. > > The Palisade driver supports several different variations of > Trimble products. Which one(s) did you try? > > The data sheet says it speaks TISP and NMEA. I don't know which > one is the default. You might try running some helper code > before starting ntpd to switch it to NMEA mode, and then telling > ntpd that it's a NMEA device. > There might be some issues with your serial port connection to the receiver. You might want to pipe the serial I/O to your console and monitor what is being sent and received from the serial port. I have used a Trimble Thunderbolt for NTP and it also uses the TSIP protocol. The Palasades driver worked for me, but I had issues with getting the Thunderbolt to serve the time after a NTP poll instead of whenever it chose. My receiver came with a RS-232 interface, but a lot of Trimble OEM products are RS-422 single ended and require a converter to RS-232 standard serial port. Since your clock is supposed to understand TSIP, there might be a program from Trimble that lets you talk directly to your clock to make sure that it is operational, has a valid position and your serial level converter is working. If your module does not have a diagnostic utility, you may try the one for the Thunderbolt. The Trimble website has these utilities. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Trimble Resolution SMT
In article <4be025aa.4050...@signaturealpha.com>, Marc Leclerc writes: >I am trying to have NTP use the trimble resolution SMT gps module, I >have tried other trimble clock driver without success so I assume that >one specific to the module has to be used. Unfortunately there does not >seems to be any way to search the mailing list to see if this was >discuss before. I would appreciate if anyone with information could get >back to me. >I am trying to make this work on an embedded linux platform, I already >have the linuxpps driver installed and have the /dev/pps0 node >available. the module is wired to /dev/ttyS1. Using the clock driver for >the palisade lead to wrong answer format messages. The Palisade driver supports several different variations of Trimble products. Which one(s) did you try? The data sheet says it speaks TISP and NMEA. I don't know which one is the default. You might try running some helper code before starting ntpd to switch it to NMEA mode, and then telling ntpd that it's a NMEA device. -- These are my opinions, not necessarily my employer's. I hate spam. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Trimble Resolution SMT
On 2010-05-04, Marc Leclerc wrote: > I am trying to have NTP use the trimble resolution SMT gps module, I > have tried other trimble clock driver without success so I assume that > one specific to the module has to be used. Unfortunately there does > not seems to be any way to search the mailing list to see if this was > discuss before. Try searching at http://groups.google.com/group/comp.protocols.time.ntp/topics?lnk or search Google for site:lists.ntp.org+questions+trimble+... -- Steve Kostecke NTP Public Services Project - http://support.ntp.org/ ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] Trimble Resolution SMT
Hi, I am trying to have NTP use the trimble resolution SMT gps module, I have tried other trimble clock driver without success so I assume that one specific to the module has to be used. Unfortunately there does not seems to be any way to search the mailing list to see if this was discuss before. I would appreciate if anyone with information could get back to me. I am trying to make this work on an embedded linux platform, I already have the linuxpps driver installed and have the /dev/pps0 node available. the module is wired to /dev/ttyS1. Using the clock driver for the palisade lead to wrong answer format messages. Regards ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
