[LinuxPPS] NTP not using PPS

susmi sarah george sarah_13 at rediffmail.com
Wed Oct 24 19:02:44 CEST 2007


  
hi,

Thanks for reply,

my serial port is      : ttyS3
my LinuxPPS Source is  : pps3
i have done in this way,

ln -s /dev/ttyS3 /dev/gps0
ln -s /dev/pps3 /dev/pps0

my ntp.conf file :

# time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.

restrict default nomodify notrap noquery

restrict 127.0.0.1

#enable stats
#statsdir /var/log
#statistics loopstats
logconfig = all

enable stats monitor pps

# --- OUR TIMESERVERS -----

#NMEA + PPS
server 127.127.20.0 mode 1 prefer minpoll 4
fudge 127.127.20.0 flag3 1 flag2 0 time1 0.0

#server 0.pool.ntp.org
#server 1.pool.ntp.org
#server 2.pool.ntp.org


# --- NTP MULTICASTCLIENT ---
#multicastclient                        # listen on default 224.0.1.1
# restrict 224.0.1.1 mask 255.255.255.255 nomodify notrap
# restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap



# --- GENERAL CONFIGURATION ---
#
# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available. The
# default stratum is usually 3, but in this case we elect to use stratum
# 0. Since the server line does not have the prefer keyword, this driver
# is never used for synchronization, unless no other other
# synchronization source is available. In case the local host is

server  127.127.1.0     # local clock
fudge   127.127.1.0 stratum 10

#
# Drift file.  Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
#
driftfile /var/lib/ntp/drift
broadcastdelay  0.008

#
# Keys file.  If you want to diddle your server at run time, make a
# keys file (mode 600 for sure) and define the key number to be
# used for making requests.
#
# PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote
# systems might be able to reset your clock at will. Note also that


but log messages not showing anything about PPS

cd /var/log

Oct 24 21:56:21 localhost ntpd: ntpd startup succeeded
Oct 24 21:56:23 localhost ntpd[5205]: peer GPS_NMEA(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
Oct 24 21:56:23 localhost ntpd[5205]: peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
Oct 24 21:57:15 localhost ntpd[5205]: system event 'event_peer/strat_chg' (0x04) status 'sync_alarm, sync_uhf_clock, 2 events, event_restart' (0xc421)
Oct 24 21:57:15 localhost ntpd[5205]: synchronized to GPS_NMEA(0), stratum 0
Oct 24 21:57:15 localhost ntpd[5205]: kernel time sync disabled 0041
Oct 24 21:57:15 localhost ntpd[5205]: system event 'event_sync_chg' (0x03) status 'leap_none, sync_uhf_clock, 3 events, event_peer/strat_chg' (0x434)
Oct 24 21:57:15 localhost ntpd[5205]: system event 'event_peer/strat_chg' (0x04) status 'leap_none, sync_uhf_clock, 4 events, event_sync_chg' (0x443)
Oct 24 21:57:30 localhost ntpd[5205]: kernel time sync enabled 0001
Oct 24 21:58:25 localhost ntpd[5270]: ntpd 4.2.4p4 at 1.1520-o Wed Oct 24 13:55:00 UTC 2007 (1)
Oct 24 21:58:25 localhost ntpd[5271]: precision = 3.000 usec
Oct 24 21:58:25 localhost ntpd[5271]: unable to bind to wildcard socket address 0.0.0.0 - another process may be running - EXITING


The Jitter Value of GPS_NMEA NMEA is changing approx.between 1.123 to 30.148.

Thanks,
lola



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ml.enneenne.com/pipermail/linuxpps/attachments/20071024/7aa1378b/attachment.html


More information about the LinuxPPS mailing list