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
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
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
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:
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
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
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.
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
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
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
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
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
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
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
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
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:
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:
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
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 --
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,
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,
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
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.
23 matches
Mail list logo
