SERIAL PORTS , COM PORTS AND EXTREME FRUSTRATION ON GPS

[SHEEPMAN!]

Let's fix this by Christmas.

If this is over your head, please come back in a week and try again.

STATEMENT:
THE PROGRAM I AM TRYING NOW...VIA WINE....(WINDOWS PROGRAM LOADER) HAS NO PROBLEM WITH COM PORTS. SO WHAT IS THE DIFFERENCE?
1. Because it's debian?
2. I held my mouth right?
3. Because it's Makulu-Aero-10...Beta? Makulu-9 works too.

SAME PROGRAM WORKS FINE AFTER TWO RE-BOOTS....WITH MINT 17.2.....GPS SET TO AUTO ANDDDDDDDDD:

Code: Select all

cd ~/.wine/dosdevices/
sudo ln -s /dev/ttyS2 com3

SO....WHAT IS MAKULU DOING DIFFERENTLY?

[Shawn]

watt program r u trying....?
winfast won't run..

[SHEEPMAN!]

I shouldn't reread my posts. This is terrible. Throwing words at the screen while frustrated is a no-no. (ALFM) (at least for me)

I assume now after a length of time that .wine has been upgraded.

1. Program loads with wine windows program loader.
2. Com ports are recognized without the use of soft links.
3. I'm talking about Winscape Navigator in this case BTW. (by the way)

Five years and less ago, wine needed soft links for com ports. I am interested in the specific change that was made to fix this. Anyone?.....you Linux lurkers? I know you are out there.

Wine says it's a work in progress and apparently someone is working.

Thanks.

[Shawn]

I still find it bizarre that Winfast will run a GPS under Wine, yet, Garmin will not find the same GPS on the same machine under the same OS and Wine.

I am going to download PC-BSD just to see how Wine works with GPS on it.

[Shawn]

From another thread.. I looks like it may be easier to get OSX to see the serial GPS..

The ToughMac video shows google earth on osx running with serial gps.
Not sure how they did it. Either it works out of the box, requires a loadable kernel module or is based on something like http://www.w7ay.net/site/Applications/Serial%20Tools/ .

Never really bothered with Wine ... more of a Parallels/VirtualBox/VMWare kind of guy.
I know you can pass through usb and serial ports to a VirtualBox guest, So I guess that should also work with Parallels.
Why Parallels? Because the OSX integration is very seamless. It even scans the Windows guests registry and extends these programs to be directly assigned to osx file types.
E.g. you click on foo.docx in OSX and the correct Windows tool starts in seamless window mode.

Running a serial NMEA GPS on Linux should not be much of an issue.
The lack of good GPS navigation software was more troublesome to me - now using MapFactor Navigator on Win7 (feels like a beta test version of OSMAnd).
Try gpscat /dev/ttyS2 or gpscat −s 4800N1 /dev/ttyS2 to view the NMEA output of COM3. The second command worked fine for my Leadtek LR9548S module.
Gpscat is part of the http://www.catb.org/gpsd/ toolsuite.
You may have to stop gpsd and/or use sudo in order to get proper access to the serial port, depending on the default /etc/init.d setup for gpsd and file permission/group memberships of your linux distribution.

BR,
Karl Klammer

[Shawn]

Short story is I want / insist on Garmin Mobile PC and it refuses to acknowledge the GPS com port in Wine.. WinFast sees the Leadtek GPS in Linux via Wine now.

[Karl Klammer]

Let me get this straight:
1) gpscat works for ttyS2
2) You symlink your ttys2 to a file COM3 within the Wine folder.
3) You can access the GPS chip via COM3 file from within Wine environment
4) One GPS software works, the other one doesn't

If that's about correct, than the issue is most likely within the GPS software (settings).
How are these GPS programs configured to interact with the COM3 port? (baud rate, stop bit, ...)

Do dmesg, Wine log or /var/log/messages on Linux give any output while accessing the COM3 port from within Wine? Does it differ between the two GPS programs?

Are you farily familar with system call debugging tools like strace? (just checking if that would be a viable debug route)

BR,
Karl Klammer

[Shawn]

baud 4800 com3 ..I believe it's N,8,1 which is the standard settings.

I pull the Linux drive and drop in a Win7 drive and the very same GPS software works perfectly.

While in Linux/ wine, I can run Winfast(a windows gps program) and it finds the gps also.

Somewhere in the translation of tty2 to com3 there is an issue. Which I don't understand, because I thought the software looked for a certain signal at 0x3E8, IRQ 4 and the "name" com or tty would not matter.

I will upload the GPS software to my dropbox and you can investigate it. It is good GPS navigation software. It's now discontinued.

[Karl Klammer]

just to clarify (maybe language barrier)

are my assumptions 1-4 correct?
are both programms configured to use the mentioned serial settings?
what is the "error pattern" within the wine environemt? (german: "fehlerbild")

btw, not to get too much into the details, but standard baud rate for linux and windows[at least putty] is 9600, imho
that might make a differnce when accessing a 4800 device, if my default=9600 assumption is correct (could only check on a linux VM)
maybe one program is just more robust in this sense than the other?
what is the output of sudo stty -F /dev/ttyS2 -a ?
does it help to run sudo stty -F /dev/ttyS2 4800 or sudo setserial /dev/ttyS2 baud_base 4800 prior to starting Wine?

BR,
Karl Klammer

[Shawn]

Yes. 1-4 are correct. Not sure about GPScat, but Jeff and I have found GPS at ttyS2 using a Linux program. I forget the name of it. FoxGPS maybe?

Yes the configurations are correct in all software packages.
We reset the Linux baud rate for that port to 4800.

I can try those commands tonight when I get home.
Jeff will jump on with more info as to what all we tried...