GARMIN GPS Interface Specification

More documents

Recommendations

Info

6.3.2. A011 – Device Command Protocol 2 This protocol is implemented mainly by panel-mounted aviation GPS products (see Section 1.1, , on page 61). The enumerated values for Command_Id_Type are shown below: enum { Cmnd_Abort_Transfer = 0, /* abort current transfer */ Cmnd_Transfer_Alm = 4, /* transfer almanac */ Cmnd_Transfer_Rte = 8, /* transfer routes */ Cmnd_Transfer_Prx = 17, /* transfer proximity waypoints */ Cmnd_Transfer_Time = 20, /* transfer time */ Cmnd_Transfer_Wpt = 21, /* transfer waypoints */ Cmnd_Turn_Off_Pwr = 26 /* turn off power */ }; Page 18 001-00063-00 Rev. A
6.4. A100 – Waypoint Transfer Protocol The Waypoint Transfer Protocol is used to transfer waypoints between devices. When the Host commands the GPS to send waypoints, the GPS will send every waypoint stored in its database. When the Host sends waypoints to the GPS, the Host may selectively transfer any waypoint it chooses. The packet sequence for the Waypoint Transfer Protocol is shown below: N Direction Packet ID Packet Data Type 0 Device1 → Device2 Pid_Records Records_Type 1 Device1 → Device2 Pid_Wpt_Data 2 Device1 → Device2 Pid_Wpt_Data … … … … n-2 Device1 → Device2 Pid_Wpt_Data n-1 Device1 → Device2 Pid_Xfer_Cmplt Command_Id_Type The first and last packets (Packet 0 and Packet n-1) are the standard beginning and ending packets (see Section 5.3, Standard Beginning and Ending Packets, on page 12). The Command_Id_Type value contained in Packet n-1 is Cmnd_Transfer_Wpt, which is also the command value used by the Host to initiate a transfer of waypoints from the GPS. Packets 1 through n-2 (Pid_Wpt_Data) each contain data for one waypoint, which is provided in product-specific data type . This data type usually contains an identifier string, latitude and longitude, and other productspecific data. Page 19 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 and 10: units may work sporadically if only
Page 11 and 12: 5. Overview of Application Protocol
Page 13 and 14: Some GPS units (e.g., the StreetPil
Page 15 and 16: 6.2. A001 - Protocol Capability Pro
Page 17: 6.3. Device Command Protocols This
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

GARMIN GPS Interface Specification

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

Delete template?

Save as template?