Hello Experts!

Looking for some urgent help, To build a NTP server I have installed Open Suse Linux and plugged in Garmin 18xLVc,5m GPS device with a Searial Cable.

After installed gpsd deamon 3.4 i have followed all required steps to work my gps but I am confused to see its result.

Here is my result:

1) The gpsd is running like :

linux-3s8f:/opt/gpsd-3.4 # gpsd -N -n -D 2 /dev/ttyS0
gpsd:INFO: launching (Version 3.4)
gpsd:INFO: listening on port gpsd
gpsd:INFO: NTPD ntpd_link_activate: 1
gpsd:INFO: stashing device /dev/ttyS0 at slot 0
gpsd:INFO: opening GPS data source type 2 at '/dev/ttyS0'
gpsd:INFO: speed 4800, 8N1
gpsd:INFO: PPS cycle: 691074274, duration: 691074274 @ 1350553157.301474
gpsd:INFO: PPS cycle: 691395220, duration: 320946 @ 1350553157.622420
gpsd:INFO: speed 9600, 8O1
gpsd:INFO: speed 4800, 8N1
gpsd:INFO: gpsd_activate(): activated GPS (fd 5)
gpsd:INFO: device /dev/ttyS0 activated
gpsd:INFO: running with effective group ID 16
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2012-10-18T09:39:19.000Z (1350553159)
gpsd:INFO: PPS cycle: 2420985, duration: 100007 @ 1350553159.722459
gpsd:INFO: PPS cycle: 1000017, duration: 900010 @ 1350553160.622469
gpsd:INFO: PPS cycle: 1000022, duration: 100012 @ 1350553160.722481
gpsd:INFO: PPS cycle: 1000025, duration: 900013 @ 1350553161.622494
gpsd:INFO: PPS cycle: 1000010, duration: 99997 @ 1350553161.722491
gpsd:INFO: PPS cycle: 1000015, duration: 900018 @ 1350553162.622509
gpsd:INFO: PPS cycle: 1000021, duration: 100003 @ 1350553162.722512
gpsd:INFO: PPS cycle: 1000015, duration: 900012 @ 1350553163.622524
gpsd:INFO: PPS cycle: 1000015, duration: 100003 @ 1350553163.722527
gpsd:INFO: PPS cycle: 999994, duration: 899991 @ 1350553164.622518
gpsd:INFO: PPS cycle: 1000020, duration: 100029 @ 1350553164.722547
gpsd:INFO: PPS cycle: 1000041, duration: 900012 @ 1350553165.622559
gpsd:INFO: PPS cycle: 1000026, duration: 100014 @ 1350553165.722573


2) I have checked
gpspipe -r

Output:
{"class":"VERSION","release":"3.4","rev":"3.4","proto_major":3,"proto_minor":6}
{"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttyS0","activated":"2012-10-18T09:33:29.473Z","native":0,"bps":4800,"parity":"N","stopbits":1,"cycle":1.00}]}
{"class":"WATCH","enable":true,"json":false,"nmea":true,"raw":0,"scaled":false,"timing":false}


3)
I have configured /etc/ntp.conf

server 127.127.28.0 minpoll 4
fudge 127.127.28.0 time1 0.535 refid NMEA
server 127.127.28.1 minpoll 4 prefer
fudge 127.127.28.1 refid PPS


Next I have restarted the ntp

/etc/init.d/ntp start


4) To see the result typed

ntpq -p

output:
remote refid st t when poll reach delay offset jitter
==============================================================================
SHM(0) .NMEA. 0 l - 16 0 0.000 0.000 0.000
SHM(1) .PPS. 0 l - 16 0 0.000 0.000 0.000


Note, the offset, jitter is not showing any value?

Please tell me where is the problem? Is my gps device is working? How i can understand?

Any steps i missed or what?

Please help me its really urgent to get a solution, My project is stopped.

Br
mhz_orcl

The simplest thing I'd do is to stop the GPS daemon, and see what data is coming out of the /dev/ttyS0 port.

Looks like the port was set up for 4800, looks like it tried 9600 and then set back for 4800.

stty -F/dev/ttyS0 will show you what the port is set for and likely it is still set for 4800.

cat /dev/ttyS0 will show you the data on that port. It should be normal NMEA GPS packets, $GPRMC ..., $GPGSV ..., $GPGGA ...; and you'll have to grab a NMEA spec online to explain to you what these packets mean. Basically if they show data like, 18160401.000,4317.4568,N,7130.3563,W, then that's the time and coordinates. If you see $GPRMC,,,,,,,*xx, then it doesn't have a fix. But it is working, and it may not have a fix if the antenna is blocked from viewing satellites.

If you see NMEA packets with little or not content, working, but no signal fix.
If you don't see any data at all, it may be working, but improperly talking to your computer, either because you have incorrect port settings, the port driver is not properly discovering your device, or it may not be working at all. Based on the log you've shown here, it appears to be working at 4800 bps.