|  |  | Support for Garmin receivers

## Support for Garmin receivers

Any Garmin receiver should (theoretically) connect with no problems to GPSMan. It must be set to use the Garmin protocol: in the receiver's `Interface` display, under `Setup`, the `Garmin/Garmin` or `Garmin` option must be selected. Alternatively, for real-time logging only, it can be set to use the NMEA 0183 protocol, by selecting the `NMEA` option. For the use of this protocol see above.

When using the Garmin protocol GPSMan may need to convert between bytes and floating point numbers. Tcl/Tk has no machine-independent way to do these conversions and GPSMan only implements them for little- or big-endian architectures that follow the IEEE floating point standard (this will cover most personal computers and workstations). Some Garmin receivers do not use protocols having floating point numbers and are not affected by this. In any case when connecting to the receiver GPSMan tests whether there are problems with the conversions, in which case the user is asked to confirm or cancel the operation.

GPSMan follows closely the "Garmin GPS Interface Specification", December 6 1999, 001-00063-00 Revision 3, available from the Garmin WWW site. This document is known to be outdated and not completely correct, as tests with recent models show.

Some data fields are not directly accessible to the user but are nevertheless kept by GPSMan as hidden information as described above. This is the case with the data on proximity distance, facility name, city, state, country code, and class.

GPSMan identifies the receiver model when connecting to it for the first time in a session. If the receiver implements the Protocol Capabilities protocol the list of protocols it uses is also obtained. This will probably be the case with the more recent models. Otherwise a table of protocols is looked up. At present there are entries in it for the receiver models in the list below.

When GPSMan gets a list of protocols for a receiver not yet listed in the table a file is created in the GPSMan user directory and the user is asked to send it to the author of GPSMan. This file should not be removed until the table is updated so that GPSMan knows these steps were already taken.

A problem was detected with a Garmin GPS 12Map that sends some packets twice. This caused havoc in the count of packets and made GPSMan to reset the connection. The solution has been to implement a test for repeated packets that are discarded if a flag is set.

eMap |
eTrex | _, Euro, Legend, Mariner, Summit, Venture, Vista
ForeTrex
Geko | 201, 301
GPS | 5, 48, 65, 72, 75, 76, 89, 90, 125 Sounder, 126, 128
GPS 12 | _, XL (Chinese, Japanese), CX, Map
GPS 38 | _ (Chinese, Japanese)
GPS 40 | _ (Chinese, Japanese)
GPS 45 | _ (Chinese), XL
GPS 55 | _, AVD
GPS 96 | _, AVD, XL
GPS 120 | _ (Chinese), XL
GPS II | _, Plus
GPS III | _, Pilot, Plus
GPSMAP | 60C, 76, 76S, 135 Sounder, 175, 180, 195, 196,
| 205, 210, 220, 235 Sounder, 295
GPSMAP 130 | _ (Chinese)
GPSMAP 230 | _ (Chinese)
Rino | 110, 120
StreetPilot | 3
GPSCOM | 170, 190

|  |  | Support for Garmin receivers