GPS application crashing -help

I have written a GPS application using C# for my WinMob 5.0 PPC.
Getting the NMEA data into the device and writing it to a file is noe
problem,
BUT when I try to analyze it the application crashes.

It seems to that its not processing fast enough. Have anyone got a example
on how to process NMEA data and get the speed from the GPRMC string?

Erik

You shouldn't need to process the NMEA sentences with WM5 as WM5 now comes

You should not need to process the NMEA sentences with WM5 as WM5 now comes
with an intermediate GPS driver.

--
Simon Hart
http://srhartone.blogspot.com

But i cant find any example -Im a newbie to this and have problems getting

But i cant find any example -
Im a newbie to this and have problems getting this to work.
Do you have a example available?

Reading from COM 7 - please?

Thank you in advance.

Erik

I wrote the WM5 version of our application to exclusively use the GPS ID, and

I wrote the WM5 version of our application to exclusively use the GPS ID,
and I've run into several problems:

1. Customers don't know how to set it up - we're having to get involved in
helping users configure the device.
2. Some devices don't have the config icon enabled, so we have to go through
the whole 'registry editing' rigmarole to enable it.
3. Some devices don't have it on at all - the Fujitsu-Siemens Pocket Loox
C550 being a good example.
4. Some applications don't work properly with it (Dell Navigation, for
example).
5. Customers don't like having to set it up if they're not going to use more
than one GPS app at a time.

So although it's a great idea from the developers point of view (no NMEA
parsing, share GPS data with other apps) it hasn't worked out so well in
practice. I'm now looking at adding code into our application to support a
direct serial connection as well as the GPS ID, for maximum flexibility.

Erik, show us the code you're using to analyse the NMEA strings, and we'll
see if we can see what's causing it to crash. I have code in various
languages (not c#, though) to split the various fields out of the NMEA
string once the checksum has been checked for validity, but nothing directly
relevant. As I recall it, if you know the checksum is correct, you either
have a null string (some GPS receivers output 0 for stopped, some just
output nothing) or you have a number. The speed is in knots, so you need to
translate that to something more meaningful, but that's about it.

Mike.

Install the WM5 SDK - the SDK comes with a sample.

Install the WM5 SDK - the SDK comes with a sample.

--
Simon Hart
http://srhartone.blogspot.com

GPS application crashing -help

Also see here: http://msdn2.microsoft.com/en-us/library/ms894898.aspx

The above is for WM5.
--
Simon Hart
http://srhartone.blogspot.com

Hi MikeI have narrowed it down to that it is the processingtime that kill the

Hi Mike

I have narrowed it down to that it is the processingtime that kill the
application.

Have changed the code to receive the NMEA input line by line - nmealine =
serialport1.readline();
This causes a delay in the decoding - will have to figure out a way to speed
the !decoding".

Is there a place to see how long time a "if" or case etc takes to run thru -
compared to eachother?

Erik

I don't know of one, other than storing system time in a few vars that you can

I do not know of one, other than storing system time in a few vars that you
can examine in the debugger. Search for 'profiling' in case there is a tool
that does it for you.

Mike.