| pblais@odstrategies.org 2006-10-16, 9:55 pm |
| While Capesoft can easily handle the communications it lacks any help
in dealing with the real issues of NMEA 0183. The serial
communications part of this really is easy. I've used NMEA 0183 a lot
as a user of marine navigation software. NMEA 0183 isn't so much
difficult but it does have it's quirks and "non standard issues". NMEA
was a standards group made up of industry manufacturers not a formal
standard organization. This is technology rooted in the mid 1970's.
You really need to be over 50 to have been where this all started. It
wasn't that great but it does work sort of.
NMEA 0183 is really a half baked standard for a modern industry that
really needs a lot more. Unless you have a need to really get into
this market I would suggest you have deeper pockets. NMEA 2000 is
probably DOA as none of the major companies are going to use it. NMEA
is the "network" version of the old technology that is even less fully
cooked.
I've often wanted to write some NMEA 0183 stuff to work with my GPS
but the standard really isn't all that standard and the variants in
the sentence structure is enough to probably drive you nuts, It won't
give you a lot of really nasty issues like spheroids and interfacing
modern devices. You are all on your own.
On 16 Oct 2006 09:58:13 -0400, "Paul Crafton"
<pcrafton@ptssolutions.com> wrote:
>Use the WinEvent (Capesoft) comm capabilities to read (accept) seriel data
>on a COMM port and NETTALK tyo transmit data to a server or what ever you
>wish....
>
---------------------------------------
Paul Blais - Hayes, Virginia
|