[ntp:questions] problems with pps and meinberg gps 167

Nec nec at kloserver.de
Fri Nov 21 18:17:30 UTC 2003


Hi,

i use a Meinberg GSP 167 with PPS but the PPS-Signal is not reachable 
although the status-bit PPSTIME is set.
I built a ttl-to-rs232 gage converter (the function of it is correct -> 
inverst a +5V to -8.5V and -5V to +8.5V for rs232) and start the 
synchronisation and all the time this output is in ntp.log:

21 Nov 18:38:07 ntpd[493]: time reset +0.196016 s
21 Nov 18:38:07 ntpd[493]: system event 'event_clock_reset' (0x05) tatus 
'leap_none, sync_unspec, 15 events, event_peer/strat_chg' (0xf4)
21 Nov 18:38:07 ntpd[493]: system event 'event_peer/strat_chg' (0x04) 
status 'leap_none, sync_unspec, 15 events, event_clock_reset' (0xf5)
21 Nov 18:38:07 ntpd[493]: peer PPS(0) event 'event_reach' (0x84) status 
'unreach, conf, 15 events, event_reach' (0x80f4)
21 Nov 18:39:12 ntpd[493]: peer GENERIC(0) event 'event_reach' (0x84) 
status 'unreach, conf, 13 events, event_reach' (0x80d4)
21 Nov 18:40:06 ntpd[493]: pps sync disabled
21 Nov 18:42:25 ntpd[493]: synchronized to GENERIC(0), stratum=0
21 Nov 18:44:25 ntpd[493]: pps sync disabled
21 Nov 18:46:40 ntpd[493]: peer PPS(0) event 'event_unreach' (0x83) 
status 'unreach, conf, 15 events, event_unreach' (0x80f3)
21 Nov 18:53:07 ntpd[493]: time reset +0.196371 s
21 Nov 18:53:07 ntpd[493]: system event 'event_clock_reset' (0x05) 
status 'leap_none, sync_unspec, 15 events, event_peer/strat_chg' (0xf4)
21 Nov 18:53:07 ntpd[493]: system event 'event_peer/strat_chg' (0x04) 
status 'leap_none, sync_unspec, 15 events, event_clock_reset' (0xf5)
21 Nov 18:53:07 ntpd[493]: peer PPS(0) event 'event_reach' (0x84) status 
'unreach, conf, 15 events, event_reach' (0x80f4)
21 Nov 18:53:50 ntpd[493]: offset 0.000000 sec freq 195.647 ppm error 
0.000001 poll 4


always comes:
	- pps sync disabled
	- peer PPS(0) event 'event_unreach'
	- system event 'event_clock_reset'
	- ...
	- peer PPS(0) event 'event_reach'


ntptime output (PPSSIGNAL is set):

ntp_gettime() returns code 0 (OK)
   time c368d525.da26804c  Fri, Nov 21 2003 19:17:09.852, (.852150688),
   maximum error 6587 us, estimated error 2035 us, TAI offset -1073742424
ntp_adjtime() returns code 0 (OK)
   modes 0x0 (),
   offset -0.096 us, frequency -22.314 ppm, interval 64 s,
   maximum error 6587 us, estimated error 2035 us,
   status 0x2107 (PLL,PPSFREQ,PPSTIME,PPSSIGNAL,NANO),
   time constant 6, precision 2.688 us, tolerance 496 ppm,
   pps frequency -22.314 ppm, stability 0.174 ppm, jitter 0.377 us,
   intervals 401, jitter exceeded 121, stability exceeded 38, errors 0.


my config:

# Meinberg GPS 167
server 127.127.8.0 mode 7 prefer
fudge 127.127.8.0 stratum 0 time1 0.0042

# pps device
server 127.127.22.0
fudge 127.127.22.0 flag3 1

# local clock
#server 127.127.1.0
#fudge 127.127.1.0

# various options
enable stats
enable pps

#server 195.72.96.5

statsdir /var/log/ntplog
driftfile /etc/ntp.drift
logconfig =all
logfile /var/log/ntp.log
statistics loopstats clockstats

filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable


ntpq -p:
      remote     refid      st t when poll reach   delay   offset  jitter
==============================================================================
*GENERIC(0)   .GPS.        0 l    7   64  377    0.000  191.405   4.870
  PPS(0)       .PPS.        0 l  711   64    0    0.000    0.000 4000.00

I don't have any idea anymore.. :(

maybe you have one..

thx for reading!

Markus




More information about the questions mailing list