Re: Garmin protocol: Packet ID 1 byte ?
- From: "John" <google@xxxxxxxxxxxxxx>
- Date: 30 Aug 2006 15:54:00 -0700
Bruce probably has the easiest approach, especially if you are going to
talk to different Garmin units and are interested in doing more than
simply reading messages.
If you are as hardheaded as myself, you're welcome to look at my code
for reading raw messages from the GPS18usb. I was dealing with an early
version of the driver and had to work around bugs.
www.precision-gps.org. Look in the src/receivers/garmin directory. I
haven't tested the Garmin code lately, but it used to work.
- John
Bruce E. Stemplewski wrote:
JF Mezei wrote:
Are there situations where secial communications would have 2 byte
Packet IDs, or are those codes simply unavailable to software that uses
serial comms to make transfers ?
No there are never situations when there are 2 byte packet ids. The
documentation is very accurate, not very clear but accurate.
Instead of "pulling out your hair" trying to understand the
documentation, you may want to consider an established C++ library or
ActiveX control like the one found on my website at www.stempsoft.com.
--
Bruce E. Stemplewski
GarXface OCX and C++ Class Library for the Garmin GPS
www.stempsoft.com
.
- References:
- Garmin protocol: Packet ID 1 byte ?
- From: JF Mezei
- Re: Garmin protocol: Packet ID 1 byte ?
- From: Bruce E. Stemplewski
- Garmin protocol: Packet ID 1 byte ?
- Prev by Date: Re: Magellan 315 Firmware Problem
- Next by Date: Re: Garmin 2610 Update Question
- Previous by thread: Re: Garmin protocol: Packet ID 1 byte ?
- Next by thread: Casio Pro Trek Wristwatch PRG 40-3VER
- Index(es):