On 2012-03-10, alex n wrote:
> 2012/3/11 unruh
>
>> On 2012-03-10, alex n wrote:
>> >>
>> >> >> Are both drivers using the same PPS signal?
>> >> >
>> >> >
>> >> > Yes, it is so.
>> >> >
>> >> >
>> >> >> If so, what do you hope to gain?
>> >> >
>> >> >
>> >> > Why the same source (PPS) may not
2012/3/11 unruh
> On 2012-03-10, alex n wrote:
> >>
> >> >> Are both drivers using the same PPS signal?
> >> >
> >> >
> >> > Yes, it is so.
> >> >
> >> >
> >> >> If so, what do you hope to gain?
> >> >
> >> >
> >> > Why the same source (PPS) may not be shared?
> >>
> >> You show it does. But wh
On 2012-03-10, alex n wrote:
>>
>> >> Are both drivers using the same PPS signal?
>> >
>> >
>> > Yes, it is so.
>> >
>> >
>> >> If so, what do you hope to gain?
>> >
>> >
>> > Why the same source (PPS) may not be shared?
>>
>> You show it does. But why? It is the same source.
>> Note that if this
>
> >> Are both drivers using the same PPS signal?
> >
> >
> > Yes, it is so.
> >
> >
> >> If so, what do you hope to gain?
> >
> >
> > Why the same source (PPS) may not be shared?
>
> You show it does. But why? It is the same source.
> Note that if this is not the same source-- ie is attached to
On 2012-03-10, alex n wrote:
> 2012/3/10 Dave Hart
>
>> On Sat, Mar 10, 2012 at 13:08, alex n wrote:
>> > xGPS_NMEA(0) .NV24. 0 l916 3770.0000.021
>> 0.004
>> > oPPS(0) .PPS.0 l7 16 3770.000
>> 0.020 0.004
>> >
>> > GPS_NMEA is n
2012/3/10 Nickolay Orekhov
>
> Next, i think that's because GPS_NMEA differs from ntp1.vniiftri.r.
> And I bet you didn't set GPS_NMEA or ntp1.vniiftri.r as "prefer" because
> none
> of them is used as supported clock for PPS.
>
As I understand a cause of the situation both drivers are using t
2012/3/10 Dave Hart
> On Sat, Mar 10, 2012 at 13:08, alex n wrote:
> > xGPS_NMEA(0) .NV24. 0 l916 3770.0000.021
> 0.004
> > oPPS(0) .PPS.0 l7 16 3770.000
> 0.020 0.004
> >
> > GPS_NMEA is nmea driver with pps support. Why GPS is
Tricky situation. First of all you should remove LOCAL(0). It is not needed
now and can only fool ntpd in many situations.
Next, i think that's because GPS_NMEA differs from ntp1.vniiftri.r.
And I bet you didn't set GPS_NMEA or ntp1.vniiftri.r as "prefer" because
none
of them is used as supported
On Sat, Mar 10, 2012 at 13:08, alex n wrote:
> xGPS_NMEA(0) .NV24. 0 l 9 16 377 0.000 0.021 0.004
> oPPS(0) .PPS. 0 l 7 16 377 0.000
> 0.020 0.004
>
> GPS_NMEA is nmea driver with pps support. Why GPS is falseticker
> though it has a s
On Sat, Mar 10, 2012 at 11:59, alex n wrote:
> Hi All,
>
> I'd like add 127.127.22.0 refclock on a fly but ntpdc -c addrefclock
> 127.127.22.0 minpoll 4 gives :
>
> Name or service not known
> ntpdc: connect: Invalid argument
I've never used that approach. I know the following approach works,
if
Folks, for what it's worth, I am updating my NTP Plotter program to
provide some statistics and graphical display of peerstats. If anyone
has any particular input to this please contact me directly.
Cheers,
David
First experimental beta:
http://www.satsignal.eu/software/net.htm#NTPplotter
Hi All,
I have following:
==
LOCAL(0) .CTB1. 1 l 39m800.0000.000 0.000
ntp1.vniiftri.r .PPS.1 u 10 16 377 223.489
37.761 7.349
xGPS_NMEA(0) .NV24.
Hi All,
I'd like add 127.127.22.0 refclock on a fly but ntpdc -c addrefclock
127.127.22.0 minpoll 4 gives :
Name or service not known
ntpdc: connect: Invalid argument
What do I do wrong?
Thanks,
Alex.
___
questions mailing list
questions@lists.ntp.org
13 matches
Mail list logo