[time-nuts] Fury ntp refclock
Scott Mace
smace at intt.net
Tue Jul 8 06:26:55 UTC 2008
This is on a net4501 with the TMRIN mod running FreeBSD 7.0 (nanobsd).
Fury 1.18 firmware with a surplus LPRO-101 packaged up in an old 1U Datum
670x rubidium reference chassis.
> ntptime
ntp_gettime() returns code 0 (OK)
time cc1d84fd.0fbd3800 Tue, Jul 8 2008 6:17:33.061, (.061481758),
maximum error 1480 us, estimated error 15 us, TAI offset 0
ntp_adjtime() returns code 0 (OK)
modes 0x0 (),
offset -0.014 us, frequency -0.040 ppm, interval 1 s,
maximum error 1480 us, estimated error 15 us,
status 0x2001 (PLL,NANO),
time constant 4, precision 0.001 us, tolerance 496 ppm,
>
> ntpq -c peers
remote refid st t when poll reach delay offset jitter
==============================================================================
+REFCLK(45,0) .GPS. 0 l 13 16 377 0.000 -1.152 3.108
oPPS(0) .PPS. 0 l 4 16 377 0.000 0.000 0.015
>
clockstats:
54655 22687.015 127.127.45.0 94 1 0 0 5.09e-12 -1.10e-09 46.10 1.994153 0.000004 10.53 8 9 1 38 10
54655 22697.016 127.127.45.0 94 1 0 0 4.59e-12 -1.40e-09 46.00 1.994255 0.000004 10.53 8 9 1 38 10
54655 22707.017 127.127.45.0 94 1 0 0 4.29e-12 -1.60e-09 46.10 1.994454 0.000004 10.53 8 9 1 38 -11
54655 22717.017 127.127.45.0 94 1 0 0 3.56e-12 -1.90e-09 46.10 1.994834 0.000004 10.53 9 9 1 38 4
54655 22727.018 127.127.45.0 94 1 0 0 3.29e-12 -2.10e-09 46.10 1.994912 0.000004 10.53 9 9 1 36 -6
54655 22737.010 127.127.45.0 94 1 0 0 2.35e-12 -2.30e-09 46.10 1.994695 0.000004 10.53 9 9 1 36 -14
54655 22747.010 127.127.45.0 94 1 0 0 2.08e-12 -2.60e-09 46.10 1.994872 0.000004 10.53 9 9 1 36 -13
54655 22757.011 127.127.45.0 94 1 0 0 1.43e-12 -2.80e-09 46.10 1.995252 0.000004 10.53 9 9 1 36 0
54655 22767.012 127.127.45.0 94 1 0 0 1.16e-12 -3.00e-09 46.10 1.995357 0.000004 10.53 9 9 1 36 -5
54655 22777.012 127.127.45.0 94 1 0 0 8.07e-13 -3.20e-09 46.10 1.995337 0.000004 10.53 9 9 1 36 3
54655 22787.014 127.127.45.0 94 1 0 0 5.83e-13 -3.40e-09 46.10 1.995080 0.000004 10.53 9 9 1 36 -8
Scott
SAIDJACK at aol.com wrote:
> Hi guys,
>
> We formatted the syst:stat? command on the Fury GPSDO so as to be compatible
> to GPSCon, that meant following a very rigorous syntax (including the exact
> number of spaces etc), it's not pretty - but works perfectly with GPSCon.
>
> One note of interest to the group in general: some of our future products
> have a new, very high performance mobile GPS on them that will actually track
> and output 16 Sats and more simultaneously (well, if it could see the Sats it
> would receive more than 30 channels) to GPSCon. A far cry from the 8-sat
> Oncore days, and this is causing some grief for GPSCon (not the entire list of
> Sat's can be shown by GPSCon without overflowing the page etc). We can't reveal
> the GPS details just yet though, please don't ask :)
>
> Seems the web interface of GPSCon works well with any number of Sats though,
> see for example:
>
> _http://www.jackson-labs.com/images/gpsstat.htm_
> (http://www.jackson-labs.com/images/gpsstat.htm)
>
>
> We are working hard on a set of new products right now, so the ptime command
> changes will have to be put on a slightly lower priority for now
> unfortunately. Seems your driver is working well right now though from what I can gather
> in the email thread.
>
> Thanks for your hard work on this,
> bye,
> Said
>
>
>
>
> In a message dated 7/8/2008 02:09:12 W. Europe Daylight Time, smace at intt.net
> writes:
>
>
> The gps?,sync?,diag?,meas? results were easier to parse than the
> system:status?
> since everything has a prefix.
>
> I'm not a fan of a the system:status? command, but it would be nice to get
> sat signal strength from the gps? command tree.
>
> My driver is not ideal, but it works with what the Fury can do with the
> current
> firmware. More to come.
>
> Scott
>
>
>
>
>
> **************Gas prices getting you down? Search AOL Autos for
> fuel-efficient used cars. (http://autos.aol.com/used?ncid=aolaut00050000000007)
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
More information about the Time-nuts_lists.febo.com
mailing list