GARMIN GPS Interface Specification

More documents

Recommendations

Info

enum { Pid_Command_Data = 10, Pid_Xfer_Cmplt = 12, Pid_Date_Time_Data = 14, Pid_Position_Data = 17, Pid_Prx_Wpt_Data = 19, Pid_Records = 27, Pid_Rte_Hdr = 29, Pid_Rte_Wpt_Data = 30, Pid_Almanac_Data = 31, Pid_Trk_Data = 34, Pid_Wpt_Data = 35, Pid_Pvt_Data = 51, Pid_Rte_Link_Data = 98, Pid_Trk_Hdr = 99, Pid_FlightBook_Record = 134 /* packet with FlightBook data */ Pid_Lap = 149 /* part of Forerunner data */ }; 4.3. L002 – Link Protocol 2 This Link protocol is used mainly for panel-mounted aviation GPS products (see Section 1.1, , on page 61). This protocol is the same as L000 – Basic Link Protocol, except that the following Packet IDs are used in addition to the Basic Packet IDs: enum { Pid_Almanac_Data = 4, Pid_Command_Data = 11, Pid_Xfer_Cmplt = 12, Pid_Date_Time_Data = 20, Pid_Position_Data = 24, Pid_Prx_Wpt_Data = 27, Pid_Records = 35, Pid_Rte_Hdr = 37, Pid_Rte_Wpt_Data = 39, Pid_Wpt_Data = 43 }; Page 10 001-00063-00 Rev. A
5. Overview of Application Protocols Each Application protocol has a unique Protocol ID to allow it to be identified apart from the others. Future products may introduce additional protocols to transfer new data types or to provide a newer version of an existing protocol (e.g., protocol A101 might be introduced as a newer version of protocol A100). Whenever a new protocol is introduced, it is expected that the Host software will have to be updated to accommodate the new protocol. However, new products may continue to support some of the older protocols, so full or partial communication may still be possible with older Host software. To better support this capability, newer products are able to report which protocols they support (see Section 6.2, A001 – Protocol Capability Protocol, on page 15). For older products, the Host must contain a lookup table to determine which protocols to use with which product types (see Section 1.1, , on page 61). 5.1. Packet Sequences Each of the Application protocols is defined in terms of a packet sequence, which defines the order and types of packets exchanged between two devices, including direction of the packet, Packet ID, and packet data type. An example of a packet sequence is shown below: N Direction Packet ID Packet Data Type 0 Device1 → Device2 Pid_First First_Data_Type 1 Device1 → Device2 Pid_Second ignored 2 Device1 → Device2 Pid_Third 3 Device1 ← Device2 Pid_Fourth 4 Device1 ← Device2 Pid_Fifth In this example, there are five packets exchanged: three from Device1 to Device2 and two in the other direction. Each of these five packets must be acknowledged, but the acknowledgement packets are omitted from the table for clarity. Most of the protocols are symmetric, meaning that the protocol for transfers in one direction (e.g., GPS to Host) is the same as the protocol for transfers in the other direction (e.g., Host to GPS). For symmetric protocols, either the GPS or the Host may assume the role of Device1 or Device2. For non-symmetric protocols, the sequence table will explicitly show the roles of the GPS and Host instead of showing Device1 and Device2. The first column of the table shows the packet number (used only for reference; this number is not encoded into the packet). The second column shows the direction of each packet transfer. The third column shows the Packet ID enumeration name (to determine the actual value for a Packet ID, see Section 4, Link Protocols, on page 8). The last column shows the Packet Data Type. 5.2. Packet Data Types The Packet Data Type may be specified in several different ways. First, it may be specified with an explicitly-named data type (e.g., “First_Data_Type”); all explicitly-named data types are defined in this document. Second, it may indicate that the packet data is not used (e.g., “ignored”), in which case the packet data may have a zero size. Finally, the data type for a packet may be specified using angle-bracket notation (e.g. ). This notation indicates Page 11 001-00063-00 Rev. A
Page 1 and 2: GARMIN GPS Interface Specification
Page 3 and 4: 6.10. A650 - FlightBook Transfer pr
Page 5 and 6: 1. Introduction 1.1. Overview This
Page 7 and 8: 3. Physical Protocols 3.1. P000 - D
Page 9: units may work sporadically if only
Page 13 and 14: Some GPS units (e.g., the StreetPil
Page 15 and 16: 6.2. A001 - Protocol Capability Pro
Page 17 and 18: 6.3. Device Command Protocols This
Page 19 and 20: 6.4. A100 - Waypoint Transfer Proto
Page 21 and 22: multiple routes. Device2 must monit
Page 23 and 24: 6.6.3. A301 - Track Log Transfer Pr
Page 25 and 26: 6.8. A500 - Almanac Transfer Protoc
Page 27 and 28: 6.10. A600 - Date and Time Initiali
Page 29 and 30: 6.13. A800 - PVT Data Protocol The
Page 31 and 32: 7.3.3. long The long data type is 3
Page 33 and 34: typedef struct { double lat; /* lat
Page 35 and 36: sym_car = 170, /* car symbol */ sym
Page 37 and 38: sym_letter_a_blue = 8317, /* blue l
Page 39 and 40: typedef struct { char ident[6]; /*
Page 43 and 44: The “addr” member is only valid
Page 45 and 46: enum Color { Black = 0, Dark_Red =
Page 47 and 48: 7.5.14. D152_Wpt_Type Example produ
Page 51 and 52: typedef struct { Semicircle_Type po
Page 53 and 54: typedef struct { int idx; /* proxim
Page 55 and 56: 7.5.35. D650_FlightBook_Record_Type
Page 57 and 58: enum { unusable = 1, /* failed inte
Page 59 and 60: 35 All L001 A010 A100, D100 A200, D
Page 61 and 62:
8.3. Frequently Asked Questions 8.3
show all

GARMIN GPS Interface Specification

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?