CF-30 Stock GPSr using Linux

Decided to start a new thread...
Sadlmkr and I have been PM'ing back and forth and it got a little confusing...
As you know, I acquired a fairly stock MK2 CF-30 for the TBT server: ~Toughbook Talk~ Toughbook Discussion • View topic - Equipment Upgrade Needed. Details plus auction inside
The stock Panasonic GPSr (?sony) works great in Windows 7, we've been struggling a little in Linux MInt.
I downloaded this :hi2:navigation program: Download OpenCPN | Official OpenCPN Homepage
and ran it in Linux Mint 13 lts MATE on the MK2 CF-30. I used these settings:
Type: Serial Data Port: /dev/TTYS3 4800 (yes, the capital S is very important)
and voila...it found my location here: 40. 48.426 N, 074 37.531 W
Locking in 7 Sats...
Please chime in here for all to read. FWIW, the stock gpsr works great in Windows on COM3, Baud rate 4800
...however, using Wine HQ, it is (on my Mint Box at COM 4, Baud Rate 4800)
Interesting stuff as Linux starts counting at "0", so COM 3 is at S3 (I think)...Jeff, please add to this...
Best regards...please respond and add to this all you GPSr gurus...
Best Regards,

 

........................

 

windows COM1, COM2, ...
*nix ttyS0, ttyS1, ...
so COM3 corresponds to ttyS2 in Linux.

 

Well, yes it does when in Bios you have GPS enabled...however I just went in to BIOS at Jeff's request, and set it to "Auto". I also for this test disabled "blue tooth", disabled "serial port A", disabled "serial port B", and disabled "parallel port". I re-booted the ToughBook and loaded U-blox program via Wine...Results show that now Satellites lock in only on the COM1 setting with Baud Rate 4800. Interesting stuff. Seems Linux must look for what's available and assign what has been either set to enable or auto. More to follow...

 

Cleve,
In your case I think their is a "conflict" caused by the USB Serial Driver seen in your

Code:

dmesg | grep USB and $ ls /dev/ttyUSB* #Not really a conflict....just Linux doing it's job.

Code:

$ dmesg | grep ttyUSB*
[    5.750267] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0 <<MINE

Can you run this and paste the output please.

Code:

ls ~/.wine/dosdevices/
ls /dev/ttyS*# I think we did this. Do it again. :)

You are correctamundo in that Linux checks devices, and writes a new kernel for each session. :hi2:

Mini-tute for everyone: The # sign is used to separate code from notes. Unit ignores anything after and including the #.
As you said up there somewhere /\ Capitalization is critical. Like ttyS3...cap S.
Spaces are important also at times. If you get "bash" check spelling, need for sudo and spacing.
ls means list.
dmesg prints the kernel that has been written for this session.
For fun, run dmesg, plug in a device...like USB stick and then run dmesg | tail #this prints the last ten lines of dmesg.
| is a shifted backspace. :thumbsup:

 

Found this link that has some possibly helpful Linux commands to use in Terminal:
Raspberry Pi • View topic - Setting up a usb gps dongle

 

Great Jeff, will try your additions. I typed this in Terminal after disabling everything in Bios except for GPS, which I chose "auto"
touchbook@touchbook-CF-30FCS80AM ~ $ dmesg | grep tty
[ 0.000000] console [tty0] enabled
[ 0.831016] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 1.245026] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 4.695140] usb 6-1: Sierra USB modem converter now attached to ttyUSB0
[ 4.695749] usb 6-1: Sierra USB modem converter now attached to ttyUSB1
[ 4.695922] usb 6-1: Sierra USB modem converter now attached to ttyUSB2
[ 4.928497] ttyS1: LSR safety check engaged!
It looks like with the above settings, Linux has assigned the stock Panasonic CF-30 MK2 GPSr to ttyS0, which I believe is COM port 1
go figure?
keep on searching!
Cleve

 

okay Jeff, per your request for Terminal:
touchbook@touchbook-CF-30FCS80AM ~ $ $ dmesg | grep ttyS3^C
touchbook@touchbook-CF-30FCS80AM ~ $
touchbook@touchbook-CF-30FCS80AM ~ $ ls ~/.wine/dosdevices/
c: d:: e:: z:
touchbook@touchbook-CF-30FCS80AM ~ $

 

Okay, and the following request yielded this
touchbook@touchbook-CF-30FCS80AM ~ $ ls /dev/ttyS*
/dev/ttyS0 /dev/ttyS14 /dev/ttyS2 /dev/ttyS25 /dev/ttyS30 /dev/ttyS8
/dev/ttyS1 /dev/ttyS15 /dev/ttyS20 /dev/ttyS26 /dev/ttyS31 /dev/ttyS9
/dev/ttyS10 /dev/ttyS16 /dev/ttyS21 /dev/ttyS27 /dev/ttyS4
/dev/ttyS11 /dev/ttyS17 /dev/ttyS22 /dev/ttyS28 /dev/ttyS5
/dev/ttyS12 /dev/ttyS18 /dev/ttyS23 /dev/ttyS29 /dev/ttyS6
/dev/ttyS13 /dev/ttyS19 /dev/ttyS24 /dev/ttyS3 /dev/ttyS7
touchbook@touchbook-CF-30FCS80AM ~ $

 

Soup first and unfreezing of the feet.

ISR

Jeff I shall return check PM

 

Sanity Check:
With Ublox running on Mint 15 here is a taste of gpscat. As is mostly usual, info can be found at

Code:

man gpscat

and of course Google is your friend. I had seen the sanity check quote in a document accessed through berlios.de. (I think)

What I did here as seen is check gpscat on my serial ports one at a time. :hi2:

 

Cleaner with a double /triple post:

What I don't understand is ublox 7.02 is running in .wine and in the /.wine/dosdevices directory, com3 is a soft link to /dev/ttyS2. Seem familiar Cleve? Some sort of internal magic here. Of course I have little to no understanding of soft links. I just know that this works.

Comments welcome from the Linux community. Ownership of a Toughbook not required. Of course if you feel bad about NOT owning a Toughbook we can fix you up. :thumbsup: