[LinuxPPS] RIPE NCC interface: needing help

[Kiss Gabor (Bitman)]

> > Now other ntp server is configured also.
> 
> An external server that serves time?

Yes.

> > However NMEA sentences are not available.
> 
> >From the local pps source, yes, but any other time source that can keep
> ntpd up to date should work.
> Once ntpd has reliable time etc, it can have a look at the local pps
> source and show reachability.

Fine. :-)

...
refclock_pps: 397 -0.046725 0.020000
refclock_pps: 398 -0.046608 0.020000
refclock_pps: 399 -0.046491 0.020000
refclock_pps: 400 -0.046376 0.020000
...
and decreasing.

ntpdc> peers
     remote           local      st poll reach  delay   offset    disp
=======================================================================
*127.127.1.0     127.0.0.1       15   64  377 0.00000  0.000000 0.03044
=193.xxx.xxx.xxx 195.xxx.xxx.xxx  3   64  177 0.00029 32.044950 0.25185
=127.127.22.0    127.0.0.1        0   64  177 0.00000  0.064462 0.25201
ntpdc> 

> 
> >   Port B can also be configured to transmit NMEA packets, but these
> >   packets are not guaranteed to be sent within 30 milliseconds after the
> >   PPS output.
> 
> If they arrive before the next pulse there should be no real problem.
> (!?)
> 
> Just try.

OK. But actually I have no software that could control the receiver.
It could be downloaded from Trimble but it runs under M$ Windows.
However I have no windows machine. Next week I ask one of my
colleagues to come with me to the server room where cable from the
roof ends. :-)

Gabor