"Q" <@..> wrote in message
news:4d18cb5a$0$12172$fa0fc...@news.zen.co.uk...
I wonder if someone would be kind enough to help me out a little here. I
have done lots of googleing and found nothing that helps me out with the
issues I'm seeing.
I am trying to reduce the PPS offset & delay (Whi
David J Taylor wrote:
"Q" <@..> wrote in message
news:4d18cb5a$0$12172$fa0fc...@news.zen.co.uk...
I wonder if someone would be kind enough to help me out a little here.
I have done lots of googleing and found nothing that helps me out with
the issues I'm seeing.
I am trying to reduce the
"David Lord" wrote in message
news:6utou7-ut8@p4x2400c.home.lordynet.org...
> On NetBSD I've had periods when rms offset as from
> peer_summary, has remained below 10us for many days.
> Mean offset is usually near 0.000ms. I don't have
> reliable reception so would expect lower offset with
"David Lord" wrote in message
news:6utou7-ut8@p4x2400c.home.lordynet.org...
[]
I think it's dependent on the ntpd version as to best
settings. I was using "fudge 127.127.20.0 time1 0.650"
and checking stats to make sure NMEA offset remained
low. That was with ntpd 4.2.4p6-o.
Thanks, David
hi all,
I have tried real hard to get ntp to build in a clearcase version
controlled environment. If I try to build "vanilla", everything works
and builds. But as soon as I check everything in and tries to build I
get into problems. It seems that as part of configuring alot of
"touch" is done to e.
On Tue, Dec 28, 2010 at 15:00 UTC, David J Taylor
wrote:
> As I never needed fudge before, why should I suddenly start to need it? And
> 0.650s sounds rather larger than the measurements would suggest.
>
> http://www.dangl.at/ausruest/gps18lvc_e.htm
> http://www.dangl.at/ausruest/gps_osz21.gif
>
On Tue, Dec 28, 2010 at 15:58 UTC, bombjack wrote:
> Are ntp as part of building checking file dates or
> something? Because that is the only thing that changes when I put
> files under version control.
Yes, the relative timestamps of files matter when building from
source. There are quite a few
ntpd timestamps the CR/LF at the end of each NMEA sentence. According
to this thread:
http://www.febo.com/pipermail/time-nuts/2010-December/052859.html
the latest (3.50) firmware for the Garmin GPS 18x LVC shifts the NMEA
generation even later in the second. You might want to try reverting
to
On 12/28/2010 8:53 AM, Q wrote:
"David Lord" wrote in message
news:6utou7-ut8@p4x2400c.home.lordynet.org...
On NetBSD I've had periods when rms offset as from
peer_summary, has remained below 10us for many days.
Mean offset is usually near 0.000ms. I don't have
reliable reception so would
Folks,
Following my previous message, I can confirm that the NMEA output from the
GPS18x LVC with the firmware 3.50 upgrade is coming out something like a
second after the PPS signal, and worse, it's very variable so sometimes
just before the PPS leading edge, and sometimes after. No wonder N
10 matches
Mail list logo
