Bruce Griffiths wrote:
Brendan Minish wrote:
Hello All
I have a little NTP server based on this project
it's running nanoBSD (FreeBSD 7.0-RC1)
NTP ver ntpd 4.2.0-a
GPS module is now an oncore UT+
I have had this device running happily for a couple of years with a GT
in NMEA mode but I am having issues with configuring the oncore driver,
it's not being used by NTP although ntpd now starts and does create the
SHMEM file in
/var/log/oncore.0
I can fiddle things by using a 'preferred' NTP server on the net for
coarse time and the elan pps driver for precision time but I would much
rather use the oncore driver directly
I have done the following
1/ symlinks in place, (I have also tried linking oncore.pps.0
to /dev/cuad1 which seems more correct ?)
lrwxr-xr-x 1 root wheel 9 Jan 21 22:09 oncore.pps.0 ->
/dev/pps0
lrwxr-xr-x 1 root wheel 10 Jan 21 22:09 oncore.serial.0
-> /dev/cuad1
lrwxr-xr-x 1 root wheel 14 Jan 21 20:53 pps0 ->
/dev/elan-mmcr
2/ /etc/ntp.oncore file created
# cat /etc/ntp.oncore
MODE 3
LAT 53 50.45830
LON -9 22.413336
HT 102.44 M
SHMEM /var/log/oncore.0
DELAY 20 NS
MASK 5
3/ enabled the oncore driver in ntp.conf, relevant bits look like this,
I have tried with the elan PPS driver enabled then disabled, but it
should work ok with it on right?
#Moto Oncore
server 127.127.30.0 minpoll 4 maxpoll 4
# PPS Disabled for now
#server 127.127.22.0 minpoll 4 maxpoll 4
#fudge 127.127.22.0 stratum 0
What else am I forgetting to do, looking at my scope starting ntpd does
not appear to be initialising the oncore at start-up since I would then
expect it's PPS output to jump or move relative to my frequency
standard
some suggestions would be most appreciated.
The link
lrwxr-xr-x 1 root wheel 9 Jan 21 22:09 oncore.pps.0 ->
/dev/pps0
should be:
lrwxr-xr-x 1 root wheel 9 Jan 21 22:09 oncore.pps.0 ->
/dev/cuad1
The link
lrwxr-xr-x 1 root wheel 14 Jan 21 20:53 pps0 ->
/dev/elan-mmcr
requires that the PPS be routed to a GPIO pin plus the timer pin.
If you haven't done this it isnt required and the standard oncore
driver will be used.
Bruce
Config files (for FreeBSD 7.2 - nanobsd) from my Soekris 4501 that uses
an M12 +T GPS timing receiver are attached.
Have since migrated to FreeBSD 8.0 (nanobsd).
Only issue for 8.0 was to ensure the real time clock driver was enabled
or the initial time error would often be too large.
Bruce
_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
#/etc/ntp.conf
tos mindist 0.010
# M12M GPS timing receiver
server 127.127.30.0 ttl 1 prefer minpoll 4 maxpoll 4
fudge 127.127.30.0 time1 -0.976
fudge 127.127.30.0 refid GPS
#PPS
server 127.127.22.0 minpoll 4 maxpoll 4
# /etc/ntp.oncore.0
MODE 1 #Fixed position
LAT -37.77718833 #Latitude in degrees
LONG 175.24084 #Longitude in degrees
HT 42.60 #height in meters
delay = 80ns #antenna cable delay
ASSERT #active high
#HARDPPS #Not required customm PPS via GPIO pin
MASK 10 #elevation mask
TRAIM YES
# /etc/rc.conf
ntpd_enable=âYESâ
hostname=âtime.has.orgâ
ifconfig_sis0=âinet 192.168.1.42â
ifconfig_sis1=âinet 192.168.1.42â
ifconfig_sis2=âinet 192.168.0.42â
# add to sysctl.conf
sysctl machdep.elan_gpio_config= ----- P...--..--------..---------
# /etc/rc.d/ntpd
ln -sf /dev/elan-mmcr /dev/pps0
ln -sf /dev/cuad1 /dev/oncore.serial.0
ln -sf /dev/cuad1 /dev/oncore.pps.0
_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
