Greetings to the forum,

I have a Panasonic CF-18MK5 Toughbook. I have Nx0.5 installed and am trying to get the builtin OEM GPS working. It works in XP, shows as Comm 5.
I have followed the post of fellow forum member, UNCNDL1, on the toughbooktalk forum, but have had no good luck. I have also read through numerous post here on this forum, but with the same results.
If someone wants to take on this challenge, let me know what other information you need, or what you want me to try.
Thank you.
Morgan

Challenges are fun.

The first thing to do is locate the gps; find out where it's attached.

Open a terminal <ctrl><alt><t> at the same time.

All the activity on the computer is logged. You can see the log via the command dmesg. There is a lot there. You can page through the log with dmseg | less. The space bar advances one screen. The <b> key backs up one screen.

After the thrill of looking for a needle in the haystack wears off try:dmesg | grep -i gps Where 'grep -i gps' means 'just show the lines with "gps", -i means either upper or lower case (gps/GPS/gPs...) '

If we're lucky, the gps will have 'gps' as part of its name and the lines that return will show us where the thing is connected.

I've also heard that sometimes integrated gps units will be listed with rfkill list all I just don't know if it's true.

Try those two strategies to see if anything hits. If it does, paste the return on a post and we'll see about connecting it.

If we don't strike it rich right out of the gate, widen the search to something like dmesg | grep -i tty to see if it's attached somewhere.

A third option is to assume it's a pci device and lspci list those devices and see if we get a hit.

Hi Moe,

I have ran dmesg in terminal previous, and after going through it line by line, found nothing that referenced gps.
Here is the output from the rest of the commands you asked me to run.

morgan@CF-18MK5Mx0:~$ dmesg | grep -i gps
morgan@CF-18MK5Mx0:~$ rfkill list all
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
morgan@CF-18MK5Mx0:~$ dmesg | grep -i tty
[ 0.000000] console [tty0] enabled
[ 1.829447] 00:0a: ttyS4 at I/O 0x148 (irq = 4, base_baud = 115200) is a 16550A
[ 1.899660] 00:0b: ttyS5 at I/O 0x158 (irq = 3, base_baud = 115200) is a 16550A
[ 24.783651] Bluetooth: RFCOMM TTY layer initialized
[ 28.948361] ttyS0: LSR safety check engaged!
[ 28.949086] ttyS0: LSR safety check engaged!
[ 33.651412] pps pps0: source "/dev/ttyS5" added
[ 1021.923147] pps pps0: source "/dev/ttyS5" added
morgan@CF-18MK5Mx0:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 04)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)
00:1d.0 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04)
00:1d.1 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04)
00:1d.2 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 04)
00:1d.3 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 04)
00:1d.7 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d4)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 04)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 04)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 04)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 04)
06:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 8b)
06:00.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 11)
06:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
06:03.0 Network controller: Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection (rev 05)
morgan@CF-18MK5Mx0:~$

At one point a couple of hours ago, I ran gpsctl in a terminal and got a SHOUT: about a gps device on /dev/ttyS5 running at 4800 baud. Even with that info I have not been able to get the gps working.

What would you like me to try or check?

I agree, it looks like /dev/ttyS5.

This kills the daemon and sets up a non-daemon gpsd to look specifically at /dev/tty5.

If there is no error, Menu> Navigation> GPS Satellites to see if data is returned.

If there is cheering, walk through the setup screens, but when it asks for the location of the gps, rather than a blank line, add /dev/ttyS5, and then 'ok' the rest of the way out.

See how that goes.

No joy.

morgan@CF-18MK5Mx0:~$ sudo killall gpsd
morgan@CF-18MK5Mx0:~$ sudo rm /var/run/gpsd.sock
[sudo] password for morgan:
morgan@CF-18MK5Mx0:~$ gpsd -N -D3 -F /var/run/gpsd.sock /dev/ttyS5
gpsd:ERROR: can't bind to local socket /var/run/gpsd.sock
gpsd:ERROR: control socket create failed, netlib error -1
morgan@CF-18MK5Mx0:~$

I did use the word challenge.

bugger!

I forgot the 'sudo'
Sorry about that.

No problem. That seemed to get closer to working. Here is the results.

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 -N -D3 -F /var/run/gpsd.sock /dev/ttyS5
gpsd:INFO: launching (Version 3.9)
gpsd:INFO: listening on port gpsd
gpsd:INFO: NTPD ntpd_link_activate: 1
gpsd:INFO: stashing device /dev/ttyS5 at slot 0
gpsd:INFO: running with effective group ID 20
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2014-08-04T01:48:17.000Z (1407116897)
gpsd:INFO: opening GPS data source type 2 at '/dev/ttyS5'
gpsd:INFO: speed 9600, 8N1
gpsd:INFO: speed 9600, 8O1
gpsd:INFO: speed 9600, 8N1
gpsd:INFO: gpsd_activate(): activated GPS (fd 8)
gpsd:INFO: detaching ::1 (sub 1, fd 9) in detach_client

I know for a fact the GPS unit in the CF-18 will not connect at anything other than 4800 baud.

This is the first time I saw anything like this in xgps:

{"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttyS5","activated":"2014-08-04T01:48:47.352Z","native":0,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00}]}

No sats showed but as I said, first time anything like that was displayed in xgps. I think if we can get the gpsd to use 4800 instead of 9600, it might work.

gpsd negotiates the speed/protocol with the gps.

However, http://www.catb.org/gpsd/faq.html#baud
It would look something likeand then

morgan@CF-18MK5Mx0:~$ sudo killall gpsd
morgan@CF-18MK5Mx0:~$ sudo rm /var/run/gpsd.sock
[sudo] password for morgan:
morgan@CF-18MK5Mx0:~$ sudo stty speed 4800 </dev/ttyS5
9600
morgan@CF-18MK5Mx0:~$ sudo gpsd -N -D3 -F /var/run/gpsd.sock /dev/ttyS5
gpsd:INFO: launching (Version 3.9)
gpsd:INFO: listening on port gpsd
gpsd:INFO: NTPD ntpd_link_activate: 1
gpsd:INFO: stashing device /dev/ttyS5 at slot 0
gpsd:INFO: running with effective group ID 20
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2014-08-04T02:30:29.000Z (1407119429)
gpsd:INFO: opening GPS data source type 2 at '/dev/ttyS5'
gpsd:INFO: speed 4800, 8N1
gpsd:INFO: speed 9600, 8O1
gpsd:INFO: speed 4800, 8N1
gpsd:INFO: gpsd_activate(): activated GPS (fd 8)
gpsd:INFO: /dev/ttyS5 identified as type Generic NMEA (0.033479 sec @ 4800bps)
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|DRIVER}
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:DATA: GSV: Satellite data OK (3 of 3).
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|SATELLITE|PACKET}
gpsd:DATA: RMC: ddmmyy=040814 hhmmss=001147 lat=nan lon=nan speed=nan track=nan mode=0 status=0

From xgps:

{"class":"SKY","tag":"GSV","device":"/dev/ttyS5","vdop":0.00,"hdop":0.00,"pdop":0.00,"satellites":[{"PRN":2,"el":48,"az":68,"ss":35,"used":false},{"PRN":5,"el":54,"az":127,"ss":0,"used":false},{"PRN":6,"el":10,"az":65,"ss":0,"used":false},{"PRN":9,"el":13,"az":50,"ss":0,"used":false},{"PRN":10,"el":33,"az":55,"ss":0,"used":false},{"PRN":12,"el":32,"az":179,"ss":0,"used":false},{"PRN":13,"el":8,"az":26,"ss":0,"used":false},{"PRN":21,"el":7,"az":245,"ss":0,"used":false},{"PRN":25,"el":55,"az":222,"ss":0,"used":false},{"PRN":29,"el":54,"az":293,"ss":0,"used":false},{"PRN":31,"el":16,"az":294,"ss":0,"used":false}]}

Skyview shows sats but not are locked on.

For cold/cold starts it needs time to download the almanac. Let it run.

Okay, I ran through the same commands in terminal and started xgps. I will let it run but it shows no sats and the terminal is output stops at:

gpsd:INFO: gpsd_activate(): activated GPS (fd 8)

There is none of this:

gpsd:INFO: /dev/ttyS5 identified as type Generic NMEA (0.033479 sec @ 4800bps)
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|DRIVER}
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|PACKET}
gpsd:DATA: GSV: Satellite data OK (3 of 3).
gpsd:DATA: packet type 1 from /dev/ttyS5 with {ONLINE|SATELLITE|PACKET}
gpsd:DATA: RMC: ddmmyy=040814 hhmmss=001147 lat=nan lon=nan speed=nan track=nan mode=0 status=0

I will let it run for 1/2 hr and see if it changes.

Thanks Moe.

Ok, I'm confused. The part where xgps was spitting out is what we should be seeing.

The satellites are there, just not enough data for the calculation of position to be be made.

Cold/cold shouldn't take over 16 minutes.

Xgps was not 'spitting' that info out. I copied it from the horizontal window directly below the skyview window. The GPS data area was full of n/a.

In XP, a cold start usually has 6 sats locked in less than 5 minutes.

At this point, there is no change in xgps or the terminal, other than one new line in terminal:

gpsd:INFO: detaching ::1 (sub 1, fd 9) in detach_client

The 16 minutes is the outside limit.

While not specific to your situation the gpsd streams json data out in 4 classes (Version, Device, Sky, TVP)The thing I'm interested in is what happens to the process that goes from what you showed initially, with the gpsd returning satellite data, but no fix. What happens? When does it fail is a first step to understand why it fails.
It looks like something is knocking it out, but yeah, the "Responses" window shows the data that is coming from the gps.

After the gps has the almanac it can then calculate the TVP.

This is all I got from terminal on the last try.

morgan@CF-18MK5Mx0:~$ sudo killall gpsd
morgan@CF-18MK5Mx0:~$ sudo rm /var/run/gpsd.sock
[sudo] password for morgan:
morgan@CF-18MK5Mx0:~$ sudo stty speed 4800 </dev/ttyS5
4800
morgan@CF-18MK5Mx0:~$ sudo gpsd -N -D3 -F /var/run/gpsd.sock /dev/ttyS5
gpsd:INFO: launching (Version 3.9)
gpsd:INFO: listening on port gpsd
gpsd:INFO: NTPD ntpd_link_activate: 1
gpsd:INFO: stashing device /dev/ttyS5 at slot 0
gpsd:INFO: running with effective group ID 20
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2014-08-04T03:30:52.000Z (1407123052)
gpsd:INFO: opening GPS data source type 2 at '/dev/ttyS5'
gpsd:INFO: speed 4800, 8N1
gpsd:INFO: speed 9600, 8O1
gpsd:INFO: speed 4800, 8N1
gpsd:INFO: gpsd_activate(): activated GPS (fd 8)
gpsd:INFO: detaching ::1 (sub 1, fd 9) in detach_client

Yes, there is definately something going on that is not proper.

When I had the sats showing, but not locked, inxgps I took the unit outside for over 5min with no change at all in xgps. FYI.

Something is knocking it out.

Let me see what I can dig up on this.

If you kick up the 'verbosity' of the debugging, from '3' to '5', does it give anything useful?

Okay. Thank you for all the time and effort you have spent on this challenge.
Ttyl.
Morgan

Not a problem. I'm guessing it is picking up the wrong driver for the gps, or a malconfigured driver. That is, it wants to, but something gets mangled and the gpsd drops it rather than wasting resources working with something that isn't working properly.

I'll check around.

That sounds logical.
I'm going to watch some sidecar races before bed.
Thanks again for your help.
Talk to you tomorrow.
Morgan

It's not my machine, but it looks like it was connecting at 9600baud. A 4800 limitation in Windows might not be a hardware limitation.
What happens when you run diagnostic at -D5 and leave the stty alone (after a reboot)? The D5 will tell us what modules (driver) gpsd is probing, and the feedback from those tests.

So, that would be

I've added the lowercase n to the command chain so the gpsd will not wait for a client (xgps) to connect before it negotiates with the gps.
etc., etc.