GPS Port connection problem on Tue Jan 18, 2011 7:55 am

Maplorer for WinCE GPS and other moving map software

GPS Port connection problem on Tue Jan 18, 2011 7:55 am

Postby guest » Fri Jul 12, 2013 10:00 am

I tried to use Maplorer on my Window CE 6.0 machine with
built-in gps.
When I run the program, it works great. The map is displayed
on the screen and can be moved around.
However, when I tried to show raw data of the GPS, I got only after I set up the word "invalid" on the last white box, but no raw data
received from GPS.
I am quite sure I have set up the right gps comm port with
correct baud rate. This is because if I set the gps comm
port to other, the program hangs up. I had also tried other
software such as GPS2blue, GPS2KML, Sirf Tech to check the
GPS comm port and all is working.
Please advise if Maplorer support only certain kind of GPSs,
and if Maplorer support GPS NEMA data.
Thanks a lot in advance.
guest
 
Posts: 36
Joined: Fri Jul 12, 2013 8:45 am

Re: GPS Port connection problem on Tue Jan 18, 2011 7:55 am

Postby guest » Fri Jul 12, 2013 10:01 am

Hi,

There is no limit to certain types of GPS; the NMEA sentences are sent to a given port as ASCII text - this basic mechanism should be the same on all devices.

Maplorer reads GPS NMEA.

On some devices, the port is 'blocked' by some other application (such as the built-in navigation software).
You could try to shut that software down/kill its process.
guest
 
Posts: 36
Joined: Fri Jul 12, 2013 8:45 am

Re: GPS Port connection problem on Tue Jan 18, 2011 7:55 am

Postby guest » Fri Jul 12, 2013 10:01 am

Thanks for your suggestion.
I have encountered the same problem on the same machine when
I tried the GPS2BLUE program. There is a background GPS
program running and opening the GPS port. However, I can
solve the problem with a port splitter program and configure
GPS2BLUE program to access another port. I tried the same for the
maplorer, but the "INVALID" word is still displaying when I
tried to show GPS raw data.
I had tried OZIexplorer, and it is also working fine.
I had tried to kill all the processes with task manager, but
Maplorer is still giving me the same result. Perhaps, I also
need to modify the registery in order to release the GPS
comm port after killing the process. Is there any information
about this ? How do I know if the comm port is opened by
other program, or not ready to open.
By the way, may I know under what condition Maplorer display
the word "INVALID".
guest
 
Posts: 36
Joined: Fri Jul 12, 2013 8:45 am

Re: GPS Port connection problem on Tue Jan 18, 2011 7:55 am

Postby guest » Fri Jul 12, 2013 10:01 am

bigbuffalo,

If it doesn't work with a port splitter, I guess its not a port allocation problem.

I wonder if it is linked to the architecture of your device: Maplorer uses a native DLL to communicate with the GPS; this DLL is compiled for the ARM3 instruction set (or compatible). What processor does yours have?

The reason why this DLL is used is explained here, if you're interested:
http://www.codeproject.com/KB/windows/GpsDll.aspx
I thought this solution would work on all devices, as .NET only supports ARM3 compatible devices. But maybe I'm wrong. You can get the source code there and see when the DLL fails to deliver a valid NMEA.

If you're interested, I could replace the DLL by a module in .NET - it could work on your device (while it wouldn't on the type discribed in the article).

Please send me your email at postmaster@maplorer.com if you want to try it out.
guest
 
Posts: 36
Joined: Fri Jul 12, 2013 8:45 am

Re: GPS Port connection problem on Tue Jan 18, 2011 7:55 am

Postby guest » Fri Jul 12, 2013 10:02 am

Correction: its ARM4, not ARM3 the DLL is targeting.
guest
 
Posts: 36
Joined: Fri Jul 12, 2013 8:45 am

Re: GPS Port connection problem on Tue Jan 18, 2011 7:55 am

Postby guest » Fri Jul 12, 2013 10:02 am

The processor of my Window CE machine is SiRF AtlasIV
Dual-Core 500MHz which is an ARM11 processor + SiRF Atlas-IV
GPS signal processor in one chip.
I expect the ARM11 is downward compatible with ARM4 or ARM3
processor, and is not a key issue.

I believe the problem is that GPSdll is not compatible with
my GPS. It seems the GPSdll can not detect a valid NMEA
sentence from my GPS, and send the word "INVALID" to
Maplorer to display. I may spend some time when I am free to
check the source code to verify this.

Anyway, I am interested to try again with your solution to
replace the DLL by a module in .NET. I will send a separate
email to postmaster@maplorer.com later.
guest
 
Posts: 36
Joined: Fri Jul 12, 2013 8:45 am


Return to Moving map software for GPS systems and cell phones

Who is online

Users browsing this forum: No registered users and 2 guests

cron