Terminal output:

morgan@CF-18MK5Mx0:~$ sudo killall gpsd
gpsd: no process found
morgan@CF-18MK5Mx0:~$ sudo rm /var/run/gpsd.sock
[sudo] password for morgan:
rm: cannot remove ‘/var/run/gpsd.sock’: No such file or directory
morgan@CF-18MK5Mx0:~$ sudo gpsd -Nn -D5 -F /var/run/gpsd.sock /dev/ttyS5
gpsd:PROG: control socket opened at /var/run/gpsd.sock
gpsd:INFO: launching (Version 3.9)
gpsd:IO: opening IPv4 socket
gpsd:IO: opening IPv6 socket
gpsd:INFO: listening on port gpsd
gpsd:PROG: NTPD shmat(0,0,0) succeeded, segment 0
gpsd:PROG: NTPD shmat(32769,0,0) succeeded, segment 1
gpsd:PROG: NTPD shmat(950285,0,0) succeeded, segment 2
gpsd:PROG: NTPD shmat(983054,0,0) succeeded, segment 3
gpsd:PROG: successfully connected to the DBUS system bus
gpsd:PROG: PPS thread launched
gpsd:INFO: NTPD ntpd_link_activate: 1
gpsd:INFO: stashing device /dev/ttyS5 at slot 0
gpsd:PROG: no /etc/gpsd/device-hook present, skipped running ACTIVATE hook
gpsd:INFO: opening GPS data source type 2 at '/dev/ttyS5'
gpsd:PROG: PPS Create Thread gpsd_ppsmonitor
gpsd:PROG: PPS chrony socket /var/run/chrony.ttyS5.sock doesn't exist
gpsd:INFO: KPPS checking /sys/devices/virtual/pps/pps0/path, /dev/ttyS5
gpsd:INFO: KPPS caps 1133
gpsd:WARN: KPPS kernel PPS will be used
gpsd:INFO: speed 9600, 8N1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:PROG: Probing "Garmin USB binary" driver...
gpsd:PROG: Probe not found "Garmin USB binary" driver...
gpsd:PROG: Probing "GeoStar binary" driver...
gpsd:IO: Sent GeoStar packet id 0xc1
gpsd:IO: => GPS: 5053474700c100010000000050924746
gpsd:PROG: Probe not found "GeoStar binary" driver...
gpsd:PROG: Probing "Trimble TSIP" driver...
gpsd:INFO: speed 9600, 8O1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:INFO: speed 9600, 8N1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:PROG: Probe not found "Trimble TSIP" driver...
gpsd:PROG: no probe matched...
gpsd:INFO: gpsd_activate(): activated GPS (fd 7)
gpsd:INFO: device /dev/ttyS5 activated
gpsd:INFO: running with effective group ID 20
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2014-08-04T05:45:44.000Z (1407131144)
gpsd:INFO: speed 4800, 8N1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:PROG: switch_driver(Generic NMEA) called...
gpsd:PROG: selecting Generic NMEA driver...
gpsd:INFO: /dev/ttyS5 identified as type Generic NMEA (4.782815 sec @ 4800bps)
gpsd:PROG: => Probing for Garmin NMEA
gpsd:IO: => GPS: $PGRMCE*0E\x0d\x0a
gpsd:IO: <= GPS: $GPGSV,3,3,11,24,29,081,28,27,38,245,29,28,04,356,00,,,,*4F
gpsd:WARN: GPGSV field 3 value of 11 != actual count 3
gpsd:DATA: GSV: Satellite data OK (3 of 3).
gpsd:IO: Not enough satellites available 0 < 4:
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|SATELLITE|PACKET|DRIVER}
gpsd:PROG: => Probing for SiRF
gpsd:IO: => GPS: $PSRF100,0,4800,8,1,0*0F\x0d\x0a
gpsd:IO: <= GPS: $GPRMC,054548,V,5003.9850,N,11301.5794,W,000.0,350.2,040814,,,N*72
gpsd:DATA: RMC: ddmmyy=040814 hhmmss=054548 lat=nan lon=nan speed=nan track=nan mode=0 status=0
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for FV-18
gpsd:IO: => GPS: $PFEC,GPint*58\x0d\x0a
gpsd:IO: <= GPS: $PASHQ,RID*28
gpsd:WARN: unknown sentence: "$PASHQ,RID*28\x0d\x0a"
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for Trimble Copernicus
gpsd:IO: => GPS: $PTNLSNM,0139,01*5C\x0d\x0a
gpsd:IO: <= GPS: @F2.2=1*64
gpsd:WARN: unknown sentence: "@F2.2=1*64\x0d\x0a"
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for Evermore
gpsd:IO: => GPS: 1002128e7f0101000101010001000000000000131003
gpsd:IO: <= GPS: $PGRMCE*0E
gpsd:WARN: unknown sentence: "$PGRMCE*0E\x0d\x0a"
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for GPSClock
gpsd:IO: => GPS: $PFEC,GPsrq*5B\x0d\x0a
gpsd:IO: <= GPS: $PSRF100,0,4800,8,1,0*0F
gpsd:WARN: unknown sentence: "$PSRF100,0,4800,8,1,0*0F\x0d\x0a"
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for Ashtech
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: <= GPS: $PFEC,GPint*58
gpsd:WARN: unknown sentence: "$PFEC,GPint*58\x0d\x0a"
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for UBX
gpsd:IO: => GPS: UBX class: 0a, id: 04, len: 0, crc: 0e34
gpsd:IO: => GPS: b5620a0400000e34
gpsd:IO: <= GPS: $GPGGA,054549,2515.9850,N,10141.5794,W,0,00,,01151.2,M,-018.1,M,,*68
gpsd:DATA: GGA: hhmmss=054549 lat=nan lon=nan alt=nan mode=0 status=0
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|STATUS|PACKET}
gpsd:PROG: => Probing for MediaTek
gpsd:IO: => GPS: $PMTK605*31\x0d\x0a
gpsd:IO: <= GPS: $GPGSA,A,1,,,,,,,,,,,,,,,*1E
gpsd:PROG: GPGSA sets mode 1
gpsd:DATA: GPGSA: mode=1 used=0 pdop=0.00 hdop=0.00 vdop=0.00
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|MODE|DOP|PACKET|USED}
gpsd:IO: <= GPS: $GPGSV,3,1,11,03,31,273,00,11,08,313,00,14,45,191,00,15,16,049,00*76
gpsd:PROG: Partial satellite data (1 of 3).
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:IO: <= GPS: $GPGSV,3,2,11,18,58,081,35,19,39,286,00,21,33,140,00,22,80,275,43*74
gpsd:PROG: Partial satellite data (2 of 3).
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:IO: => client(0): {"class":"VERSION","release":"3.9","rev":"3.9","proto_major":3,"proto_minor":8}\x0d\x0a
gpsd:PROG: checking client(0)
gpsd:IO: <= client(0): ?WATCH={"enable":true,"json":true,"scaled":true}\x0a
gpsd:PROG: device 0 (fd=7, path /dev/ttyS5) already active.
gpsd:IO: => client(0): {"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttyS5","activated":"2014-08-04T05:45:50.866Z","flags":1,"driver":"Generic NMEA","native":0,"bps":4800,"parity":"N","stopbits":1,"cycle":1.00}]}\x0d\x0a{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":true,"timing":false}\x0d\x0a
gpsd:IO: => client(1): {"class":"VERSION","release":"3.9","rev":"3.9","proto_major":3,"proto_minor":8}\x0d\x0a
gpsd:PROG: checking client(1)
gpsd:IO: <= client(1): ?WATCH={"enable":true,"json":true};\x0a
gpsd:PROG: device 0 (fd=7, path /dev/ttyS5) already active.
gpsd:IO: => client(1): {"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttyS5","activated":"2014-08-04T05:45:50.866Z","flags":1,"driver":"Generic NMEA","native":0,"bps":4800,"parity":"N","stopbits":1,"cycle":1.00}]}\x0d\x0a{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":false,"timing":false}\x0d\x0a
gpsd:PROG: checking client(1)
gpsd:INFO: detaching ::1 (sub 1, fd 10) in detach_client

Responses output in xgps:

{"class":"VERSION","release":"3.9","rev":"3.9","proto_major":3,"proto_minor":8}

GPS data all show n/a with no sats showing in skyview.

It wants to work.

I say this because it looks like you're in a 'new' house near Morningside.

We just need to figure out why it craps out, eh?

This will take some research. I'll be back.

I'm actually in an old building in Crossfield, about 80-90mi south of Morningside.

At least it want to work.

Place a # in front of the last line. Save and reboot.

After the reboot,again to see if has changed. (Not the time part, but the assignment part.)

Don't worry, I've got a few more quirky ideas, I just don't want to rush in yet.

Moe,
I brought the unit with me to work this morning, but have been too busy yo even look at it. Maybe in an hour or two, if not, this evening.
Morgan

Terminal output:

morgan@CF-18MK5Mx0:~$ sudo medit /var/lib/setserial/autoserial.con
[sudo] password for morgan:

(medit:2539): GLib-GObject-WARNING **: Attempt to add property MooEditConfig::lang after class was initialised

(medit:2539): GLib-GObject-WARNING **: Attempt to add property MooEditConfig::indent after class was initialised

(medit:2539): GLib-GObject-WARNING **: Attempt to add property MooEditConfig::strip after class was initialised

(medit:2539): GLib-GObject-WARNING **: Attempt to add property MooEditConfig::add-newline after class was initialised

(medit:2539): GLib-GObject-WARNING **: Attempt to add property MooEditConfig::wrap-mode after class was initialised

(medit:2539): GLib-GObject-WARNING **: Attempt to add property MooEditConfig::show-line-numbers after class was initialised

(medit:2539): GLib-GObject-WARNING **: Attempt to add property MooEditConfig::tab-width after class was initialised

(medit:2539): GLib-GObject-WARNING **: Attempt to add property MooEditConfig::word-chars after class was initialised

(medit:2539): GLib-GObject-WARNING **: Attempt to add property MooEditConfig::indent-use-tabs after class was initialised

(medit:2539): GLib-GObject-WARNING **: Attempt to add property MooEditConfig::indent-width after class was initialised

When medit opened, it was blank, no first or last line.

Okay, I ran the command again, this time medit was not blank. I put a # in front of the last line, rebooted then ran the dmesg command.
Here is the terminal output:

morgan@CF-18MK5Mx0:~$ dmesg | grep tty
[ 0.000000] console [tty0] enabled
[ 1.837209] 00:0a: ttyS4 at I/O 0x148 (irq = 4, base_baud = 115200) is a 16550A
[ 1.907310] 00:0b: ttyS5 at I/O 0x158 (irq = 3, base_baud = 115200) is a 16550A
morgan@CF-18MK5Mx0:~$

So, where to next, Captian?

The <blank> medit was because of the dropped last letter in the cut'n'paste.

However, the dmesg | grep tty return is not what I expected. I didn't see the pps source found, e.g., or why were things listed twice in your initial dmesg, etc.

The LSR safety check engaged! comes from a port that was probed initially, but for some reason disappears, or is knocked out.

By commenting out (#) the last line of /var/lib/setserial/autoserial.conf took care of that LSR problem...that was expected.

I guess I was expecting since the probe/disable cycle was broken, another ttySx, or reassignment, or what I don't know. I could replicate the LSR safety check yesterday, but lost the secret incantation.

Now, the best I can do is with /dev/ttyS4 being the bluetooth. So, I'm limited in hands-on testing ideas as we walk down the chain of events that make a working thing, not work, and we close those options. When in doubt, poke about...and methodically limit the ways it can all go wrong.

The track I was taking was a comment by a CF-18 user that his gps was on /dev/ttyS0 and that the user needed to be added to the uucp/dialout group because in some weird legacy data flow that's the group for the ttys.

http://www.catb.org/gpsd/installation.html

It gets strange because of gpsd's ability to maintain security and yet operate with root privileges and then I read this While it's grammatically confusing, I was wondering if the whole operation was being set up to ship data to a buffer that was not being accessed by the user who was not in the group...you. And the whole thing shuts down.

At least that was the straw I was clinging to.

I checked and am in the dialout group.

morgan@CF-18MK5Mx0:~$ groups
morgan adm dialout cdrom sudo dip plugdev lpadmin netdev sambashare debian-tor

Or are you thinking I need to be in another group, other that the ones listed, in order for gpsd to be able to access the buffer?

It looks like my bluetooth module is also on ttyS4:

morgan@CF-18MK5Mx0:~$ setserial -g /dev/ttyS[12345678]
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3
/dev/ttyS4, UART: 16550A, Port: 0x0148, IRQ: 4
/dev/ttyS5: Device or resource busy
/dev/ttyS6, UART: unknown, Port: 0x0000, IRQ: 0
/dev/ttyS7, UART: unknown, Port: 0x0000, IRQ: 0
/dev/ttyS8, UART: unknown, Port: 0x0000, IRQ: 0

Alright lets see why is test for drivers and then craps out.





This will start pulling data without a client attached from the gps in non-daemon mode and level 5 diagnostics.

We can see what drivers are rejected and what spit back something intelligible but fail for some reason.

Please post the output. A fix will look likeWhich shows 31° 23.7343'S and 149° 9.4261'E Location data can also be in other 'NMEA' prefaced sentences 'RMC', or 'GGA'

In the interim I'll look for a way to query the gps chip to find out what breed we're dealing with, as I don't currently know how to do that for something that is not USB or PCI.

To make sure that the GPS module in the CF-18 had not died, I swapped the XP hdd into the unit.
I started VisualGPS and had a 3D fix w/3 sats and within 10min had a fix on 6.
This was with the unit inside sitting on my desk with heavy thunderstorms blowing by overhead.
Swapped hdds, ran the commands and here is the output:

morgan@CF-18MK5Mx0:~$ sudo killall gpsd
gpsd: no process found
morgan@CF-18MK5Mx0:~$ sudo rm /var/run/gpsd.sock
[sudo] password for morgan:
rm: cannot remove ‘/var/run/gpsd.sock’: No such file or directory
morgan@CF-18MK5Mx0:~$ sudo gpsd -D5 -nN -F /var/run/gpsd.sock /dev/ttyUSB1
gpsd:PROG: control socket opened at /var/run/gpsd.sock
gpsd:INFO: launching (Version 3.9)
gpsd:IO: opening IPv4 socket
gpsd:IO: opening IPv6 socket
gpsd:INFO: listening on port gpsd
gpsd:PROG: NTPD shmat(0,0,0) succeeded, segment 0
gpsd:PROG: NTPD shmat(32769,0,0) succeeded, segment 1
gpsd:PROG: NTPD shmat(917516,0,0) succeeded, segment 2
gpsd:PROG: NTPD shmat(950285,0,0) succeeded, segment 3
gpsd:PROG: successfully connected to the DBUS system bus
gpsd:PROG: PPS thread launched
gpsd:INFO: NTPD ntpd_link_activate: 1
gpsd:INFO: stashing device /dev/ttyUSB1 at slot 0
gpsd:PROG: no /etc/gpsd/device-hook present, skipped running ACTIVATE hook
gpsd:INFO: opening read-only GPS data source type 0 and at '/dev/ttyUSB1'
gpsd:ERROR: device open failed: No such file or directory - retrying read-only
gpsd:ERROR: read-only device open failed: No such file or directory
gpsd:ERROR: initial GPS device /dev/ttyUSB1 open failed
gpsd:INFO: running with effective group ID 20
gpsd:INFO: running with effective user ID 65534
gpsd:PROG: PPS Create Thread gpsd_ppsmonitor
gpsd:PROG: PPS thread awaiting device activation
gpsd:INFO: startup at 2014-08-07T03:56:33.000Z (1407383793)
gpsd:PROG: PPS thread awaiting device activation
#The last line repeated close to one hundred times,
#ending with the next 2 lines when I opened another terminal and ran the commands again
gpsd:WARN: received terminating signal 15.
gpsd:WARN: exiting.

morgan@CF-18MK5Mx0:~$ sudo killall gpsd
morgan@CF-18MK5Mx0:~$ sudo rm /var/run/gpsd.sock
[sudo] password for morgan:
morgan@CF-18MK5Mx0:~$ sudo gpsd -D5 -nN -F /var/run/gpsd.sock /dev/ttyS5
gpsd:PROG: control socket opened at /var/run/gpsd.sock
gpsd:INFO: launching (Version 3.9)
gpsd:IO: opening IPv4 socket
gpsd:IO: opening IPv6 socket
gpsd:INFO: listening on port gpsd
gpsd:PROG: NTPD shmat(0,0,0) succeeded, segment 0
gpsd:PROG: NTPD shmat(32769,0,0) succeeded, segment 1
gpsd:PROG: NTPD shmat(917516,0,0) succeeded, segment 2
gpsd:PROG: NTPD shmat(950285,0,0) succeeded, segment 3
gpsd:PROG: successfully connected to the DBUS system bus
gpsd:PROG: PPS thread launched
gpsd:INFO: NTPD ntpd_link_activate: 1
gpsd:INFO: stashing device /dev/ttyS5 at slot 0
gpsd:PROG: no /etc/gpsd/device-hook present, skipped running ACTIVATE hook
gpsd:INFO: opening GPS data source type 2 at '/dev/ttyS5'
gpsd:PROG: PPS Create Thread gpsd_ppsmonitor
gpsd:PROG: PPS chrony socket /var/run/chrony.ttyS5.sock doesn't exist
gpsd:INFO: KPPS checking /sys/devices/virtual/pps/pps0/path, /dev/ttyS5
gpsd:INFO: KPPS caps 1133
gpsd:WARN: KPPS kernel PPS will be used
gpsd:INFO: speed 9600, 8N1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:PROG: Probing "Garmin USB binary" driver...
gpsd:PROG: Probe not found "Garmin USB binary" driver...
gpsd:PROG: Probing "GeoStar binary" driver...
gpsd:IO: Sent GeoStar packet id 0xc1
gpsd:IO: => GPS: 5053474700c100010000000050924746
gpsd:PROG: Probe not found "GeoStar binary" driver...
gpsd:PROG: Probing "Trimble TSIP" driver...
gpsd:INFO: speed 9600, 8O1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:INFO: speed 9600, 8N1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:PROG: Probe not found "Trimble TSIP" driver...
gpsd:PROG: no probe matched...
gpsd:INFO: gpsd_activate(): activated GPS (fd 7)
gpsd:INFO: device /dev/ttyS5 activated
gpsd:INFO: running with effective group ID 20
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2014-08-07T04:00:53.000Z (1407384053)
gpsd:INFO: speed 4800, 8N1
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: => GPS: @F0.3=1*67\x0d\x0a
gpsd:IO: => GPS: @F2.2=1*64\x0d\x0a
gpsd:IO: writing oncore control type Cj
gpsd:IO: => GPS: @@Cj)\x0d\x0aRID*28\x0d\x0a
gpsd:PROG: switch_driver(Generic NMEA) called...
gpsd:PROG: selecting Generic NMEA driver...
gpsd:INFO: /dev/ttyS5 identified as type Generic NMEA (5.340027 sec @ 4800bps)
gpsd:PROG: => Probing for Garmin NMEA
gpsd:IO: => GPS: $PGRMCE*0E\x0d\x0a
gpsd:IO: <= GPS: $GPGSV,3,3,09,27,40,299,00,,,,,,,,,,,,*43
gpsd:WARN: GPGSV field 3 value of 9 != actual count 1
gpsd:DATA: GSV: Satellite data OK (3 of 3).
gpsd:IO: Not enough satellites available 0 < 4:
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|SATELLITE|PACKET|DRIVER}
gpsd:PROG: => Probing for SiRF
gpsd:IO: => GPS: $PSRF100,0,4800,8,1,0*0F\x0d\x0a
gpsd:IO: <= GPS: $GPRMC,040057,V,5125.4664,N,11401.6000,W,001.4,201.2,070814,,,N*72
gpsd:DATA: RMC: ddmmyy=070814 hhmmss=040057 lat=nan lon=nan speed=nan track=nan mode=0 status=0
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for FV-18
gpsd:IO: => GPS: $PFEC,GPint*58\x0d\x0a
gpsd:IO: <= GPS: $PASHQ,RID*28
gpsd:WARN: unknown sentence: "$PASHQ,RID*28\x0d\x0a"
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for Trimble Copernicus
gpsd:IO: => GPS: $PTNLSNM,0139,01*5C\x0d\x0a
gpsd:IO: <= GPS: @F2.2=1*64
gpsd:WARN: unknown sentence: "@F2.2=1*64\x0d\x0a"
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for Evermore
gpsd:IO: => GPS: 1002128e7f0101000101010001000000000000131003
gpsd:IO: <= GPS: $PGRMCE*0E
gpsd:WARN: unknown sentence: "$PGRMCE*0E\x0d\x0a"
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for GPSClock
gpsd:IO: => GPS: $PFEC,GPsrq*5B\x0d\x0a
gpsd:IO: <= GPS: $PSRF100,0,4800,8,1,0*0F
gpsd:WARN: unknown sentence: "$PSRF100,0,4800,8,1,0*0F\x0d\x0a"
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for Ashtech
gpsd:IO: => GPS: $PASHQ,RID*28\x0d\x0a
gpsd:IO: <= GPS: $PFEC,GPint*58
gpsd:WARN: unknown sentence: "$PFEC,GPint*58\x0d\x0a"
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for UBX
gpsd:IO: => GPS: UBX class: 0a, id: 04, len: 0, crc: 0e34
gpsd:IO: => GPS: b5620a0400000e34
gpsd:IO: <= GPS: $PTNLSNM,0139,01*5C
gpsd:WARN: unknown sentence: "$PTNLSNM,0139,01*5C\x0d\x0a"
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:PROG: => Probing for MediaTek
gpsd:IO: => GPS: $PMTK605*31\x0d\x0a
gpsd:IO: <= GPS: $GPGGA,040058,5125.4664,N,11401.6000,W,0,00,,00001.2,M,-018.1,M,,*60
gpsd:DATA: GGA: hhmmss=040058 lat=nan lon=nan alt=nan mode=0 status=0
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|STATUS|PACKET}
gpsd:IO: <= GPS: $GPGSA,A,1,,,,,,,,,,,,,,,*1E
gpsd:PROG: GPGSA sets mode 1
gpsd:DATA: GPGSA: mode=1 used=0 pdop=0.00 hdop=0.00 vdop=0.00
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|MODE|DOP|PACKET|USED}
gpsd:IO: <= GPS: $GPGSV,3,1,09,14,03,190,00,15,47,073,36,16,14,263,00,18,82,228,35*72
gpsd:PROG: Partial satellite data (1 of 3).
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:IO: <= GPS: $GPGSV,3,2,09,19,15,319,00,21,76,122,00,22,40,244,00,24,04,116,00*77
gpsd:PROG: Partial satellite data (2 of 3).
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:IO: => client(0): {"class":"VERSION","release":"3.9","rev":"3.9","proto_major":3,"proto_minor":8}\x0d\x0a
gpsd:PROG: checking client(0)
gpsd:IO: <= client(0): ?WATCH={"enable":true,"json":true};\x0a
gpsd:PROG: device 0 (fd=7, path /dev/ttyS5) already active.
gpsd:IO: => client(0): {"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttyS5","activated":"2014-08-07T04:00:59.837Z","flags":1,"driver":"Generic NMEA","native":0,"bps":4800,"parity":"N","stopbits":1,"cycle":1.00}]}\x0d\x0a{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":false,"timing":false}\x0d\x0a
gpsd:PROG: checking client(0)
gpsd:INFO: detaching ::1 (sub 0, fd 9) in detach_client

It got a fix through ttyS5. 2 in fact, the first:

gpsd:PROG: => Probing for SiRF
gpsd:IO: => GPS: $PSRF100,0,4800,8,1,0*0F\x0d\x0a
gpsd:IO: <= GPS: $GPRMC,040057,V,5125.4664,N,11401.6000,W,001.4,201.2,070814,,,N*72

And the second:

gpsd:PROG: => Probing for MediaTek
gpsd:IO: => GPS: $PMTK605*31\x0d\x0a
gpsd:IO: <= GPS: $GPGGA,040058,5125.4664,N,11401.6000,W,0,00,,00001.2,M,-018.1,M,,*60

Would it help if I pulled the bottom off the unit and checked the chip? No big deal.

Sorry, there was a typo in the command chain above, I had included the command I used for my USB gps....and I'm a lousy proofreader.

The chips have a vendor:product number17ef:1003 for this machine's card reader, e,g. 067b:2303 for the USB gps through a USB/Serial converter, etc...

I'm learning how to get the same info from a device attached to a serial, like explained in https://wiki.debian.org/HowToIdentifyADevice/Serial, but I'm not very successful on this machine.

I did have some luck with cat /sys/class/tty/ttyS4/device/vendor and cat /sys/class/tty/ttyS4/device/device (Your's would be the same except for ttyS5 exchanged)...and then see if this cross reference to a known device of the gps nature. There is the additional problem of cat /sys/class/tty/ttyS4/device/subsystem_vendor and /subsystem_device being different and not know which is which.

...but, yeah, if you can read some numbers of the gps by removing the cover. It might save some tears.

There's also

morgan@CF-18MK5Mx0:~$ cat /sys/class/tty/ttyS5/device/vendor
cat: /sys/class/tty/ttyS5/device/vendor: No such file or directory
morgan@CF-18MK5Mx0:~$ cat /sys/class/tty/ttyS5/device/device
cat: /sys/class/tty/ttyS5/device/device: No such file or directory
morgan@CF-18MK5Mx0:~$ ls /dev/serial/by-id/
ls: cannot access /dev/serial/by-id/: No such file or directory
morgan@CF-18MK5Mx0:~$

I will pull the bottom tomorrow. If I get some time tomorrow, I will check out the link. Thank you.

Bloody hell. It must be a typo in there because I'm running a modified Navigatrix system and the bloody thing worked for me. I don't know what it told me, but it worked.

I look in the morning.

but it's not morning yet.

Don't get in a rush on my account. Maybe you could send me a bottle and after drinking it, I can see if I can duplicate your results.

It looks like I will have time today to remove the bottom and get some numbers.
Post results later.

The GPS module in the CF-18 is a Sony, GXB5005.
The rest of the markings are probably not relivant, but will include them anyways.

Japan MKM
070724 Ver1.0
8-753-242-14

Hope that helps.

Here is a link to a datasheet for the module.

http://www.datasheet4u.com/datasheet/G/X/B/GXB5005_Sony.pdf.html

The download link is at the bottom of the page, to the left of the 'Buy' button.
I downloaded it with no problem, or money.
Hope it helps.

The famous line in the software world is: "It should work."

...let's see what we can do about.

Currently striking out on information on driving your chip. The two 'full runs' you pasted understandably are the same, at least the Universe is consistent.

The following are two different gps unit. One is binary, the other is not.
The other gps, still without a fix, but not binary.
See what you gps dumps with sudo cat /dev/ttyS5

I'm guessing it will also not be binary... guessing is just like gambling, but cheaper.

Then give this a whack

I found this interesting.