In message <[EMAIL PROTECTED]>, Nate Williams writes:
>>
>> "What is a PPS signal ?"
>>
>> Typically handheld/boat naviation stuff. The NMEA or other
>> serial timecodes are at best in the 1msec class.
>
>Again, for me this is acceptable. It would be nice to have it better
>than this
In message <[EMAIL PROTECTED]>, Nate Williams writes:
>> : You may not know the answer to this, but it's worth a shot. Wht kind of
>> : accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
>>
>> We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
>> gps receiver +
In message <[EMAIL PROTECTED]> Nate Williams writes:
: > : Cool. I was under the impression that the cheap NMEA signals only gave
: > : 2-5sec accuracy given the 2400 baud speed issues.
: >
: > If you have a PPS signal, then you can get fairly close even if the
: > inforation about the PPS signa
> >> Between the two of us Dave Mills and I have managed to get the
> >> "nanokernel" to act sensibly in the domain inside +/- 1usec which
> >> the old one didn't. (See http://gps.freebsd.dk for what kind of
> >> performance this can result in, given appropriate hardware).
> >
> >You may not know
> : Cool. I was under the impression that the cheap NMEA signals only gave
> : 2-5sec accuracy given the 2400 baud speed issues.
>
> If you have a PPS signal, then you can get fairly close even if the
> inforation about the PPS signal comes in at 2400 baud.
Hmm, how do I find out how good it is
In message <[EMAIL PROTECTED]> Nate Williams writes:
: Cool. I was under the impression that the cheap NMEA signals only gave
: 2-5sec accuracy given the 2400 baud speed issues.
If you have a PPS signal, then you can get fairly close even if the
inforation about the PPS signal comes in at 2400 b
In message <[EMAIL PROTECTED]>, Nate Williams writes:
>> Between the two of us Dave Mills and I have managed to get the
>> "nanokernel" to act sensibly in the domain inside +/- 1usec which
>> the old one didn't. (See http://gps.freebsd.dk for what kind of
>> performance this can result in, given
> : > : You may not know the answer to this, but it's worth a shot. Wht kind of
> : > : accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
> : >
> : > We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
> : > gps receiver + atomic clock on a i486 class machine.
>
In message <[EMAIL PROTECTED]> Nate Williams writes:
: > : You may not know the answer to this, but it's worth a shot. Wht kind of
: > : accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
: >
: > We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
: > gps receive
> : You may not know the answer to this, but it's worth a shot. Wht kind of
> : accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
>
> We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
> gps receiver + atomic clock on a i486 class machine.
I've got the cheap g
In message <[EMAIL PROTECTED]> Nate Williams writes:
: You may not know the answer to this, but it's worth a shot. Wht kind of
: accuracy can we expect using 'cheap' off-the-shelf GPS receivers?
We're getting, with ntp4 on a 3.x kernel, about +- 4uSec with a cheap
gps receiver + atomic clock on
In message <[EMAIL PROTECTED]> Matthew Jacob
writes:
: Huh? What about the impact on all ntp.conf files? Or is this seamless?
Except for additional clocks, I've had no problems using old ntp.conf
files with the new ntpd.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
> Between the two of us Dave Mills and I have managed to get the
> "nanokernel" to act sensibly in the domain inside +/- 1usec which
> the old one didn't. (See http://gps.freebsd.dk for what kind of
> performance this can result in, given appropriate hardware).
You may not know the answer to thi
Thanks for the very clear writeup of what we can expect. I'm happy.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message <[EMAIL PROTECTED]>, Matthew
Jacob writes:
>
>Huh? What about the impact on all ntp.conf files? Or is this seamless?
I was just about to start to compose an email with some info on this
one when you email arrived.
/etc/ntp.conf is the same unless you have a refclock. If you have
a r
Huh? What about the impact on all ntp.conf files? Or is this seamless?
On Thu, 16 Dec 1999, Ollivier Robert wrote:
> This is a HEADSUP message to warn all current users that tha following is
> being done:
>
> - disable xntpd build
> - enable ntp build
> - removal of old xntpd/xntpdc binaries
This is a HEADSUP message to warn all current users that tha following is
being done:
- disable xntpd build
- enable ntp build
- removal of old xntpd/xntpdc binaries as they've been renamed
- modifications in /etc/defaults/rc.conf to take the new daemon into
account.
xntpd will be "cvs removed
17 matches
Mail list logo
