Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
On Thu, Oct 17, 2013 at 2:54 PM, Chris Albertson albertson.ch...@gmail.comwrote: Details like this about NTP ref clocks are best posted to the NTP list. The true experts live there I would suggest that's not the best choice (been there, done that). If you're looking at a controller managed GPSDO you've moved well past the typical mass-market (e.g. MTK) GPS+PPS module and are presumably interested in more than just the Void flag. In general the NTP folks stop caring a bit before 10e-3 and see no real point in having constellation of local stratum-1 clocks. Naturally there are exceptions and they're probably all on this list. I think this is the best place to talk about the GPSDO big picture. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
On the other hand if you are using NTP you have no need for a clock that does better than about 1e-8. Anything better is wasted. NTP at best cares about microseconds, not nanoseconds. What I meant was that if you need to know the nuts and bolts of how NTP ref clocks work at the level of software internals the NTP list is the place to be. That level of expertise is rare here and common there. I was not implying at all that you should not be permitted to ask here, just that as a practical matter the experts are not here. On Fri, Oct 18, 2013 at 7:57 AM, Paul tic-...@bodosom.net wrote: On Thu, Oct 17, 2013 at 2:54 PM, Chris Albertson albertson.ch...@gmail.comwrote: Details like this about NTP ref clocks are best posted to the NTP list. The true experts live there I would suggest that's not the best choice (been there, done that). If you're looking at a controller managed GPSDO you've moved well past the typical mass-market (e.g. MTK) GPS+PPS module and are presumably interested in more than just the Void flag. In general the NTP folks stop caring a bit before 10e-3 and see no real point in having constellation of local stratum-1 clocks. Naturally there are exceptions and they're probably all on this list. I think this is the best place to talk about the GPSDO big picture. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. -- Chris Albertson Redondo Beach, California ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
On Fri, Oct 18, 2013 at 4:48 PM, Chris Albertson albertson.ch...@gmail.comwrote: What I meant was that if you need to know the nuts and bolts of how NTP ref clocks work at the level of software internals the NTP list is the place to be. I was overly casual. Back when Frank was getting started he said he wanted a frequency reference and then realized it would nice to have PPS for NTP. From that perspective it seems that monitoring your GPSDO is more important than numbering your seconds. So given a single serial output I would suggest running LH, Z38XX etc. to stay apprised of the state of the GPSDO and letting whatever consumes the PPS sort out acquiring coarse time. That was the main point I failed to make and the NTP/refclock details really are a distraction. My bad. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
I posted a patch for the Fury to work with ntpd in Oct 2008. It uses the GPGGA output. The PTIME:TCODE? command is not on-time with the 1-PPS output on the Fury, so the HPGPS driver does not work. http://www.febo.com/pipermail/time-nuts/2008-October/033901.html the ntp-fury.diff: http://www.febo.com/pipermail/time-nuts/attachments/20081020/846021fe/attachment-0001.bin Scott On 10/16/2013 04:44 PM, Frank Hughes wrote: Hi, What NTP REFCLOCK can be used for a Jackson Fury? I know that the Jackson Fury docs suggest using: http://www.realhamradio.com/gpscon-info.htm But that means I would have to put up a windows server to replace the FreeBSD ntpd server I built for use w/ the Trimble TB. Looking for open source options, if possible. Thanks, Frank KJ4OLL ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
On Thu, Oct 17, 2013 at 9:40 AM, Scott Mace sm...@intt.net wrote: The PTIME:TCODE? command is not on-time with the 1-PPS output on the Fury Is it consistently before or after the pulse? I.e. can it be fixed with time1? Is there the same problem with the NMEA sentences? In any case these sorts of issues are why I prefer to number seconds with a known-to-work system. -- Paul ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
Back in 2003 or so, in the Z3801A with hpgps ntpd refclock driver, I had to add a negative offset of -0.98 seconds to the driver's decoding of PTIME:TCODE? to get it to be right in combination with PPS refclock. The documentation in the Z3801A manual correctly described the actual behavior PTIME:TCODE? Provides timecode message 980 to 20 ms prior to 1 PPS of indicated time. On Thu, Oct 17, 2013 at 9:40 AM, Scott Mace sm...@intt.net wrote: I posted a patch for the Fury to work with ntpd in Oct 2008. It uses the GPGGA output. The PTIME:TCODE? command is not on-time with the 1-PPS output on the Fury, so the HPGPS driver does not work. http://www.febo.com/pipermail/**time-nuts/2008-October/033901.**htmlhttp://www.febo.com/pipermail/time-nuts/2008-October/033901.html the ntp-fury.diff: http://www.febo.com/pipermail/**time-nuts/attachments/** 20081020/846021fe/attachment-**0001.binhttp://www.febo.com/pipermail/time-nuts/attachments/20081020/846021fe/attachment-0001.bin Scott On 10/16/2013 04:44 PM, Frank Hughes wrote: Hi, What NTP REFCLOCK can be used for a Jackson Fury? I know that the Jackson Fury docs suggest using: http://www.realhamradio.com/**gpscon-info.htmhttp://www.realhamradio.com/gpscon-info.htm But that means I would have to put up a windows server to replace the FreeBSD ntpd server I built for use w/ the Trimble TB. Looking for open source options, if possible. Thanks, Frank KJ4OLL __**_ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/** mailman/listinfo/time-nutshttps://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. __**_ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/** mailman/listinfo/time-nutshttps://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
The GPGGA sentence is on-time enough so that ntpd will work. You still have to set 'mindist' to something like 0.050. The driver will also query other interesting things from the Fury. The response from PTIME:TCODE? varied too much for ntpd to use it even with a large mindist. Scott On 10/17/2013 09:14 AM, Paul wrote: On Thu, Oct 17, 2013 at 9:40 AM, Scott Mace sm...@intt.net wrote: The PTIME:TCODE? command is not on-time with the 1-PPS output on the Fury Is it consistently before or after the pulse? I.e. can it be fixed with time1? Is there the same problem with the NMEA sentences? In any case these sorts of issues are why I prefer to number seconds with a known-to-work system. -- Paul ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
Interesting.. I see something completely different with my Fury. My hard-coded fudge factor is 0.077 yielding: Every 2.0s: ntpq -p Thu Oct 17 10:20:00 2013 remote refid st t when poll reach delay offset jitter == -four2.fairy.mat 64.250.177.145 2 u 12 64 377 72.493 17.784 0.524 -66-162-15-65.li 64.236.96.53 2 u 33 64 377 50.226 15.291 1.181 +barricade.rack9 209.51.161.238 2 u 10 64 377 22.9081.075 0.362 -ccadmin.cycores 130.207.244.240 2 u 38 64 377 39.2183.972 1.241 192.168.1.171 .INIT. 16 u- 102400.0000.000 0.000 +SHM(0) .FURY. 0 l6 16 3770.0000.526 0.034 *SHM(1) .PPSF. 0 l5 64 3770.0000.008 0.001 -europium.canoni 193.79.237.142 u 32 64 377 116.177 -1.573 0.992 So... i could fine tune my fudge some but the point is the jitter is fairly low. (fury is from the sentences and ppsf is pps from fury). My soekris (soekris is the .171) numbers were much better but it is inoperable for some reason. Doc On Thu, Oct 17, 2013 at 9:59 AM, Tim Shoppa tsho...@gmail.com wrote: Back in 2003 or so, in the Z3801A with hpgps ntpd refclock driver, I had to add a negative offset of -0.98 seconds to the driver's decoding of PTIME:TCODE? to get it to be right in combination with PPS refclock. The documentation in the Z3801A manual correctly described the actual behavior PTIME:TCODE? Provides timecode message 980 to 20 ms prior to 1 PPS of indicated time. On Thu, Oct 17, 2013 at 9:40 AM, Scott Mace sm...@intt.net wrote: I posted a patch for the Fury to work with ntpd in Oct 2008. It uses the GPGGA output. The PTIME:TCODE? command is not on-time with the 1-PPS output on the Fury, so the HPGPS driver does not work. http://www.febo.com/pipermail/**time-nuts/2008-October/033901.**html http://www.febo.com/pipermail/time-nuts/2008-October/033901.html the ntp-fury.diff: http://www.febo.com/pipermail/**time-nuts/attachments/** 20081020/846021fe/attachment-**0001.bin http://www.febo.com/pipermail/time-nuts/attachments/20081020/846021fe/attachment-0001.bin Scott On 10/16/2013 04:44 PM, Frank Hughes wrote: Hi, What NTP REFCLOCK can be used for a Jackson Fury? I know that the Jackson Fury docs suggest using: http://www.realhamradio.com/**gpscon-info.htm http://www.realhamradio.com/gpscon-info.htm But that means I would have to put up a windows server to replace the FreeBSD ntpd server I built for use w/ the Trimble TB. Looking for open source options, if possible. Thanks, Frank KJ4OLL __**_ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/** mailman/listinfo/time-nuts https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. __**_ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/** mailman/listinfo/time-nuts https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. -- Doc Bill Dailey KXØO ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
I think the Fury does not guarantee that the PTIME:TCODE will be near the 1-PPS leading edge. When I tried it with the HPGPS driver and a net4501, ntpd wasn't happy with it. I also needed leap second processing to work, holdover notification, and to collect other data from it. The GPGGA sentence is on-time even if you are asking the Fury to do other things with SCPI commands. Try setting your Fury hpgps driver fudge flag4 to 1 and I bet it will stop working well. This flag logs the system:print output. Scott On 10/17/2013 10:24 AM, Bill Dailey wrote: Interesting.. I see something completely different with my Fury. My hard-coded fudge factor is 0.077 yielding: Every 2.0s: ntpq -p Thu Oct 17 10:20:00 2013 remote refid st t when poll reach delay offset jitter == -four2.fairy.mat 64.250.177.145 2 u 12 64 377 72.493 17.784 0.524 -66-162-15-65.li 64.236.96.53 2 u 33 64 377 50.226 15.291 1.181 +barricade.rack9 209.51.161.238 2 u 10 64 377 22.9081.075 0.362 -ccadmin.cycores 130.207.244.240 2 u 38 64 377 39.2183.972 1.241 192.168.1.171 .INIT. 16 u- 102400.0000.000 0.000 +SHM(0) .FURY. 0 l6 16 3770.0000.526 0.034 *SHM(1) .PPSF. 0 l5 64 3770.0000.008 0.001 -europium.canoni 193.79.237.142 u 32 64 377 116.177 -1.573 0.992 So... i could fine tune my fudge some but the point is the jitter is fairly low. (fury is from the sentences and ppsf is pps from fury). My soekris (soekris is the .171) numbers were much better but it is inoperable for some reason. Doc On Thu, Oct 17, 2013 at 9:59 AM, Tim Shoppa tsho...@gmail.com wrote: Back in 2003 or so, in the Z3801A with hpgps ntpd refclock driver, I had to add a negative offset of -0.98 seconds to the driver's decoding of PTIME:TCODE? to get it to be right in combination with PPS refclock. The documentation in the Z3801A manual correctly described the actual behavior PTIME:TCODE? Provides timecode message 980 to 20 ms prior to 1 PPS of indicated time. On Thu, Oct 17, 2013 at 9:40 AM, Scott Mace sm...@intt.net wrote: I posted a patch for the Fury to work with ntpd in Oct 2008. It uses the GPGGA output. The PTIME:TCODE? command is not on-time with the 1-PPS output on the Fury, so the HPGPS driver does not work. http://www.febo.com/pipermail/**time-nuts/2008-October/033901.**html http://www.febo.com/pipermail/time-nuts/2008-October/033901.html the ntp-fury.diff: http://www.febo.com/pipermail/**time-nuts/attachments/** 20081020/846021fe/attachment-**0001.bin http://www.febo.com/pipermail/time-nuts/attachments/20081020/846021fe/attachment-0001.bin Scott On 10/16/2013 04:44 PM, Frank Hughes wrote: Hi, What NTP REFCLOCK can be used for a Jackson Fury? I know that the Jackson Fury docs suggest using: http://www.realhamradio.com/**gpscon-info.htm http://www.realhamradio.com/gpscon-info.htm But that means I would have to put up a windows server to replace the FreeBSD ntpd server I built for use w/ the Trimble TB. Looking for open source options, if possible. Thanks, Frank KJ4OLL __**_ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/** mailman/listinfo/time-nuts https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. __**_ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/** mailman/listinfo/time-nuts https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
It looks like in this Ubuntu I am using 28 SHM with gpsd which is different that the soekris. Sent from mobile On Oct 17, 2013, at 1:00 PM, Scott Mace sm...@intt.net wrote: I think the Fury does not guarantee that the PTIME:TCODE will be near the 1-PPS leading edge. When I tried it with the HPGPS driver and a net4501, ntpd wasn't happy with it. I also needed leap second processing to work, holdover notification, and to collect other data from it. The GPGGA sentence is on-time even if you are asking the Fury to do other things with SCPI commands. Try setting your Fury hpgps driver fudge flag4 to 1 and I bet it will stop working well. This flag logs the system:print output. Scott On 10/17/2013 10:24 AM, Bill Dailey wrote: Interesting.. I see something completely different with my Fury. My hard-coded fudge factor is 0.077 yielding: Every 2.0s: ntpq -p Thu Oct 17 10:20:00 2013 remote refid st t when poll reach delay offset jitter == -four2.fairy.mat 64.250.177.145 2 u 12 64 377 72.493 17.784 0.524 -66-162-15-65.li 64.236.96.53 2 u 33 64 377 50.226 15.291 1.181 +barricade.rack9 209.51.161.238 2 u 10 64 377 22.9081.075 0.362 -ccadmin.cycores 130.207.244.240 2 u 38 64 377 39.2183.972 1.241 192.168.1.171 .INIT. 16 u- 102400.0000.000 0.000 +SHM(0) .FURY. 0 l6 16 3770.0000.526 0.034 *SHM(1) .PPSF. 0 l5 64 3770.0000.008 0.001 -europium.canoni 193.79.237.142 u 32 64 377 116.177 -1.573 0.992 So... i could fine tune my fudge some but the point is the jitter is fairly low. (fury is from the sentences and ppsf is pps from fury). My soekris (soekris is the .171) numbers were much better but it is inoperable for some reason. Doc On Thu, Oct 17, 2013 at 9:59 AM, Tim Shoppa tsho...@gmail.com wrote: Back in 2003 or so, in the Z3801A with hpgps ntpd refclock driver, I had to add a negative offset of -0.98 seconds to the driver's decoding of PTIME:TCODE? to get it to be right in combination with PPS refclock. The documentation in the Z3801A manual correctly described the actual behavior PTIME:TCODE? Provides timecode message 980 to 20 ms prior to 1 PPS of indicated time. On Thu, Oct 17, 2013 at 9:40 AM, Scott Mace sm...@intt.net wrote: I posted a patch for the Fury to work with ntpd in Oct 2008. It uses the GPGGA output. The PTIME:TCODE? command is not on-time with the 1-PPS output on the Fury, so the HPGPS driver does not work. http://www.febo.com/pipermail/**time-nuts/2008-October/033901.**html http://www.febo.com/pipermail/time-nuts/2008-October/033901.html the ntp-fury.diff: http://www.febo.com/pipermail/**time-nuts/attachments/** 20081020/846021fe/attachment-**0001.bin http://www.febo.com/pipermail/time-nuts/attachments/20081020/846021fe/attachment-0001.bin Scott On 10/16/2013 04:44 PM, Frank Hughes wrote: Hi, What NTP REFCLOCK can be used for a Jackson Fury? I know that the Jackson Fury docs suggest using: http://www.realhamradio.com/**gpscon-info.htm http://www.realhamradio.com/gpscon-info.htm But that means I would have to put up a windows server to replace the FreeBSD ntpd server I built for use w/ the Trimble TB. Looking for open source options, if possible. Thanks, Frank KJ4OLL __**_ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/** mailman/listinfo/time-nuts https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. __**_ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/** mailman/listinfo/time-nuts https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
On Thu, Oct 17, 2013 at 2:00 PM, Scott Mace sm...@intt.net wrote: Try setting your Fury hpgps driver fudge flag4 to 1 He said he thought he was using 20+22 (NMEA+PPS). Of course the ntpq output suggests GPSD or other shared memory driver. -- Paul ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
Correct. And I can access my soekris right now. Sent from mobile On Oct 17, 2013, at 1:35 PM, Paul tic-...@bodosom.net wrote: On Thu, Oct 17, 2013 at 2:00 PM, Scott Mace sm...@intt.net wrote: Try setting your Fury hpgps driver fudge flag4 to 1 He said he thought he was using 20+22 (NMEA+PPS). Of course the ntpq output suggests GPSD or other shared memory driver. -- Paul ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
Yes, the GPGGA method works. Scott On 10/17/2013 01:35 PM, Paul wrote: On Thu, Oct 17, 2013 at 2:00 PM, Scott Mace sm...@intt.net wrote: Try setting your Fury hpgps driver fudge flag4 to 1 He said he thought he was using 20+22 (NMEA+PPS). Of course the ntpq output suggests GPSD or other shared memory driver. -- Paul ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
This isn't NMEA but many NMEA GPSes work just find and if you read the NMEA specifications the ascci data only has to be valid for the second in it is output. This allows for a random 0.... second offset. If your ref cock is bothered by a .999 second offset I'd argue the ref clock software is broken because it makes a wrong assumption. The ASCII data is analogous to the old voice telephone service what says at the tone the time will be xxx BEEP. As long as she makes the announcement before the beep and after the last beep it is perfectly in spec. If the software depends on an EXACT and CONSTANT offset between the announcement and the UTC second it is really not doing the correct thing re. the specs. But NTP ref clocks do make this assumption because many times it is correct. Many GPS receivers are predicable and each sentence has a common offset. I think there really is a difference between using two drivers, Atom for PPS and some other for ASCII data vs. using a combined driver. The combined drivers are not forced into making the constant offset assumption and use the PPS for timing and ASCII for numbering. But if you look at the stand alone drivers they use the ASCII for both numbering and timing. So I argue the best model for your device is a combined driver. Details like this about NTP ref clocks are best posted to the NTP list. The true experts live there On Thu, Oct 17, 2013 at 11:00 AM, Scott Mace sm...@intt.net wrote: I think the Fury does not guarantee that the PTIME:TCODE will be near the 1-PPS leading edge. When I tried it with the HPGPS driver and a net4501, ntpd wasn't happy with it. I also needed leap second processing to work, holdover notification, and to collect other data from it. The GPGGA sentence is on-time even if you are asking the Fury to do other things with SCPI commands. Try setting your Fury hpgps driver fudge flag4 to 1 and I bet it will stop working well. This flag logs the system:print output. Scott On 10/17/2013 10:24 AM, Bill Dailey wrote: Interesting.. I see something completely different with my Fury. My hard-coded fudge factor is 0.077 yielding: Every 2.0s: ntpq -p Thu Oct 17 10:20:00 2013 remote refid st t when poll reach delay offset jitter ==**==** == -four2.fairy.mat 64.250.177.145 2 u 12 64 377 72.493 17.784 0.524 -66-162-15-65.li 64.236.96.53 2 u 33 64 377 50.226 15.291 1.181 +barricade.rack9 209.51.161.238 2 u 10 64 377 22.9081.075 0.362 -ccadmin.cycores 130.207.244.240 2 u 38 64 377 39.2183.972 1.241 192.168.1.171 .INIT. 16 u- 102400.0000.000 0.000 +SHM(0) .FURY. 0 l6 16 377 0.0000.526 0.034 *SHM(1) .PPSF. 0 l5 64 3770.0000.008 0.001 -europium.canoni 193.79.237.14 2 u 32 64 377 116.177 -1.573 0.992 So... i could fine tune my fudge some but the point is the jitter is fairly low. (fury is from the sentences and ppsf is pps from fury). My soekris (soekris is the .171) numbers were much better but it is inoperable for some reason. Doc On Thu, Oct 17, 2013 at 9:59 AM, Tim Shoppa tsho...@gmail.com wrote: Back in 2003 or so, in the Z3801A with hpgps ntpd refclock driver, I had to add a negative offset of -0.98 seconds to the driver's decoding of PTIME:TCODE? to get it to be right in combination with PPS refclock. The documentation in the Z3801A manual correctly described the actual behavior PTIME:TCODE? Provides timecode message 980 to 20 ms prior to 1 PPS of indicated time. On Thu, Oct 17, 2013 at 9:40 AM, Scott Mace sm...@intt.net wrote: I posted a patch for the Fury to work with ntpd in Oct 2008. It uses the GPGGA output. The PTIME:TCODE? command is not on-time with the 1-PPS output on the Fury, so the HPGPS driver does not work. http://www.febo.com/pipermail/time-nuts/2008-October/** 033901.**htmlhttp://www.febo.com/pipermail/**time-nuts/2008-October/033901.**html http://www.febo.com/pipermail/**time-nuts/2008-October/033901.**htmlhttp://www.febo.com/pipermail/time-nuts/2008-October/033901.html the ntp-fury.diff: http://www.febo.com/pipermail/time-nuts/attachments/**http://www.febo.com/pipermail/**time-nuts/attachments/** 20081020/846021fe/attachment-0001.bin http://www.febo.com/pipermail/**time-nuts/attachments/** 20081020/846021fe/attachment-**0001.binhttp://www.febo.com/pipermail/time-nuts/attachments/20081020/846021fe/attachment-0001.bin Scott On 10/16/2013 04:44 PM, Frank Hughes wrote: Hi, What NTP REFCLOCK can be used for a Jackson Fury? I know that the Jackson Fury docs suggest using: http://www.realhamradio.com/gpscon-info.htmhttp://www.realhamradio.com/**gpscon-info.htm
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
Frank, try GPSD on Linux: http://gpsd.berlios.de/hardware.html Bye, Said In a message dated 10/16/2013 14:50:19 Pacific Daylight Time, hp_cisco...@yahoo.com writes: Hi, What NTP REFCLOCK can be used for a Jackson Fury? I know that the Jackson Fury docs suggest using: http://www.realhamradio.com/gpscon-info.htm But that means I would have to put up a windows server to replace the FreeBSD ntpd server I built for use w/ the Trimble TB. Looking for open source options, if possible. Thanks, Frank KJ4OLL ___ ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
You can use FreeBSD. I will dig out the refclock I am using with my disciplined soekris. Sent from mobile On Oct 16, 2013, at 4:44 PM, Frank Hughes hp_cisco...@yahoo.com wrote: Hi, What NTP REFCLOCK can be used for a Jackson Fury? I know that the Jackson Fury docs suggest using: http://www.realhamradio.com/gpscon-info.htm But that means I would have to put up a windows server to replace the FreeBSD ntpd server I built for use w/ the Trimble TB. Looking for open source options, if possible. Thanks, Frank KJ4OLL ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
On Wed, Oct 16, 2013 at 5:44 PM, Frank Hughes hp_cisco...@yahoo.com wrote: What NTP REFCLOCK can be used for a Jackson Fury? One normally uses the ATOM driver with PPS. If you need to number your seconds I've heard of a SCPI (hpgps) driver but I suggest using another one of your clocks or any other clock if you have confidence in your network connection. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
On Wed, Oct 16, 2013 at 6:38 PM, Paul tic-...@bodosom.net wrote: a SCPI (hpgps) driver Sorry, hpgps is the driver/port name but the NTP driver id is GPS_HP. Again, I have no direct experience with it. -- Paul ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
With my Z3801A (which I understand the Fury to be compatible with at SCPI level), I use GPS_HP refclock in ntpd, along with nanokernel PPS. I had to tweak baud rate in the source code. Tim N3QE On Wed, Oct 16, 2013 at 6:44 PM, Paul tic-...@bodosom.net wrote: On Wed, Oct 16, 2013 at 6:38 PM, Paul tic-...@bodosom.net wrote: a SCPI (hpgps) driver Sorry, hpgps is the driver/port name but the NTP driver id is GPS_HP. Again, I have no direct experience with it. -- Paul ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
I think I used type 20 and 22 with bsd on my soekris. I have had it off for some time because it started to error on boot. Have it apart now trying to figure out what is going on. I suspect a problem with the clock block. Set the fury to output ggtts. Bill Sent from my iPad On Oct 16, 2013, at 4:44 PM, Frank Hughes hp_cisco...@yahoo.com wrote: Hi, What NTP REFCLOCK can be used for a Jackson Fury? I know that the Jackson Fury docs suggest using: http://www.realhamradio.com/gpscon-info.htm But that means I would have to put up a windows server to replace the FreeBSD ntpd server I built for use w/ the Trimble TB. Looking for open source options, if possible. Thanks, Frank KJ4OLL ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
On Wed, Oct 16, 2013 at 7:18 PM, Bill Dailey docdai...@gmail.com wrote: Set the fury to output ggtts Did you mean GPGGA? If the Fury is producing RMC sentences then NMEA+PPS (20+22) should work. Some folks recommend the NMEA PPS option (flag1) but in my experience it's less stable than the stand-alone PPS driver. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] NTP REFCLOCK for a Jackson Fury??
Yes Sent from mobile On Oct 16, 2013, at 8:39 PM, Paul tic-...@bodosom.net wrote: On Wed, Oct 16, 2013 at 7:18 PM, Bill Dailey docdai...@gmail.com wrote: Set the fury to output ggtts Did you mean GPGGA? If the Fury is producing RMC sentences then NMEA+PPS (20+22) should work. Some folks recommend the NMEA PPS option (flag1) but in my experience it's less stable than the stand-alone PPS driver. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
