Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris C-22 Technical Provisions for Mode S Services and Extended Squitter Table C-7. “Selected Altitude Type” Subfield Encoding Coding Meaning Data being used to encode “ME” bits 10 – 20 is derived from the Mode 0 Control Panel / Flight Control Unit (MCP / FCU) or equivalent equipment. Data being used to encode “ME” bits 10 – 20 is derived from the Flight 1 Management System (FMS). C.2.3.9.4 MCP/FCU Selected Altitude or FMS Selected Altitude a. The “MCP / FCU Selected Altitude or FMS Selected Altitude” subfield is an 11-bit (“ME” bits 10 – 20, Message bits 42 – 52) field that contains either “MCP / FCU Selected Altitude” or “FMS Selected Altitude” data in accordance with the following subparagraphs. b. Whenever valid Selected Altitude data is available from the Mode Control Panel / Flight Control Unit (MCP / FCU) or equivalent equipment, such data shall be used to encode “ME” bits 10 – 20 (Message bits 42 – 52) in accordance with Table C-8. Use of MCP / FCU Selected Altitude is then declared in the “Selected Altitude Type” subfield as specified in Table C-7. c. Whenever valid Selected Altitude data is NOT available from the Mode Control Panel / Flight Control Unit (MCP / FCU) or equivalent equipment, but valid Selected Altitude data is available from the Flight Management System (FMS), then the FMS Selected Altitude data is used to encode “ME” bits 10 – 20 (Message bits 42 – 52) in accordance with Table C-8. Use of FMS Selected Altitude is then declared in the “Selected Altitude Type” subfield as specified in Table C-7. d. Encoding of Selected Altitude data in “ME” bits 10 – 20 (Message bits 42 – 52) is in accordance with Table C-8. Encoding of the data is rounded so as to preserve accuracy of the source data within ±½ LSB. e. Whenever there is NO valid MCP / FCU or FMS Selected Altitude data available, then the “MCP / FCU Selected Altitude or FMS Selected Altitude” subfield (“ME” bits 10 – 20, Message bits 42 – 52) shall be set to ZERO (0) as indicated in Table C-8. Table C-8. “MCP/FCU Selected Altitude or FMS Selected Altitude” Subfield Encoding Coding (“ME” bits 10 ---- 20) Meaning (Binary) (Decimal) 000 0000 0000 0 NO Data or INVALID Data 000 0000 0001 1 0 feet 000 0000 0010 2 32 feet 000 0000 0011 3 64 feet *** **** **** *** *** **** **** *** **** **** *** *** **** **** *** **** **** *** *** **** **** 111 1111 1110 2046 65440 feet 111 1111 1111 2047 65472 feet Draft C.2.3.9.5 Barometric Pressure Setting (Minus 800 millibars) a. The “Barometric Pressure Setting (Minus 800 millibars)” subfield is a 9-bit (“ME” bits 21 – 29, Message bits 53 – 61) field that contains Barometric Pressure Setting data that has been adjusted by subtracting 800 millibars from the data received from the Barometric Pressure Setting source. b. After adjustment by subtracting 800 millibars, the Barometric Pressure Setting is encoded in “ME” bits 21 – 29 (Message bits 53 – 61) in accordance with Table C-9. c. Encoding of Barometric Pressure Setting data in “ME” bits 21 – 29 (Message bits 53 – 61) shall be rounded so as to preserve a reporting accuracy within ±½ LSB. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Appendix C C-23 d. Whenever there is NO valid Barometric Pressure Setting data available, then the “Barometric Pressure Setting (Minus 800 millibars) subfield (“ME” bits 21 – 29, Message bits 53 – 61) shall be set to ZERO (0) as indicated in Table C-9. e. Whenever the Barometric Pressure Setting data is greater than 1208.4 or less than 800 millibars, then the “Barometric Pressure Setting (Minus 800 millibars) subfield (“ME” bits 21 – 29, Message bits 53 – 61) shall be set to ZERO (0). Note.— This Barometric Pressure Setting data can be used to represent QFE or QNH/QNE, depending on local procedures. It represents the current value being used to fly the aircraft. Table C-9. “Barometric Pressure Setting (Minus 800 millibars)” Subfield Encoding Coding (“ME” bits 21 ---- 29) Meaning (Binary) (Decimal) 0 0000 0000 0 NO Data or INVALID Data 0 0000 0001 1 0 millibars 0 0000 0010 2 0.8 millibars 0 0000 0011 3 1.6 millibars * **** **** *** *** **** **** * **** **** *** *** **** **** * **** **** *** *** **** **** 1 1111 1110 510 407.2 millibars 1 1111 1111 511 408.0 millibars C.2.3.9.6 Selected Heading Status The “Selected Heading Status” subfield is a 1-bit (“ME” bit 30, Message bit 62) field that shall be used to indicate the status of Selected Heading data that is being used to encode “ME” bits 32 – 39 (Message bits 64 – 71) in accordance with Table C-10. Coding (“ME” bit 30) 0 1 Table C-10. “Selected Heading Status” Subfield Encoding Meaning Draft Data being used to encode “ME” bits 32 – 39 (Message bits 64 – 71) is either NOT Available or is INVALID. See Table C-12. Data being used to encode “ME” bits 32 – 39 (Message bits 64 – 71) is Available and is VALID. See Table C-12. C.2.3.9.7 Selected Heading Sign The “Selected Heading Sign” subfield is a 1-bit (“ME” bit 31, Message bit 63) field that shall be used to indicate the arithmetic sign of Selected Heading data that is being used to encode “ME” bits 32 – 39 (Message bits 64 – 71) in accordance with Table C-11. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Page 1 and 2:
DRAFT - Working Paper ASP TSGWP11-0
Page 3 and 4:
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Appendix A A-7 TYPE Code Format Hor
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Appendix A A-13 The supersonic vers
Page 39 and 40:
Appendix A A-15 The transponder sha
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Appendix A A-41 MB FIELD DRAFT - Wo
Page 67 and 68:
Appendix A A-43 MB FIELD 1 MSB TRAN
Page 69 and 70:
Page 71 and 72:
Appendix A A-47 MB FIELD 1 2 3 4 5
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Appendix A A-55 MB FIELD 1 BDS A,8
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Appendix A A-97 a) the PI sends a T
Page 123 and 124:
Appendix A A-99 This subfield shall
Page 125 and 126:
Appendix A A-101 These channels hav
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Appendix A A-109 A.4. MODE S BROADC
Page 135 and 136:
Appendix A A-111 Note 1.— This st
Page 137 and 138:
Page 139 and 140:
Appendix B B-3 TYPE code Subtype co
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Appendix B B-17 Coding (Binary) (De
Page 155 and 156:
Appendix B B-19 a) ACAS operational
Page 157 and 158:
Appendix B B-21 Subfield Coding: DR
Page 159 and 160: Appendix B B-23 Coding (Binary) (De
Page 161 and 162: DRAFT - Working Paper ASP TSGWP11-0
Page 169 and 170: Appendix B B-33 MB FIELD DRAFT - Wo
Page 177 and 178: Appendix B B-41 CF value ICAO/Mode
Page 193 and 194: Appendix C C-5 Table C-2. “TYPE
Page 199 and 200: Appendix C C-11 C.2.3.2.2 Time Sync
Page 209: DRAFT - Working Paper ASP TSGWP11-0
Page 213 and 214: Appendix C C-25 Notes.— DRAFT - W
Page 219 and 220: Msg Bit # “ME” Bit # Appendix C
Page 221 and 222: Appendix C C-33 Msg Bit # "ME” Bi
Page 231 and 232: Appendix C C-43 Notes. — DRAFT -
Page 239 and 240: Appendix C C-51 3. The decoded posi
Page 245 and 246: Appendix C C-57 B Reports to have k
Page 247 and 248: Appendix C C-59 Register 0516 DRAFT
Page 253 and 254: Appendix C C-65 Register 0A16 Figur
Page 259 and 260: Appendix C C-71 Table C-37. CF Fiel
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Appendix CD CD-3 ACTIONS EVENTS DRA
Page 289 and 290:
Page 291 and 292:
Appendix CD CD-7 too many broadcast
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Appendix CD CD-13 CD.2.4.4.1.2 Poss
Page 299 and 300:
Appendix CD CD-15 D.2.4.4.2.1.2 A32
Page 301 and 302:
Appendix CD CD-17 AP/FD mode V/S-FP
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Appendix CD CD-23 CD.2.4.7.5 BINARY
Page 309 and 310:
Page 311 and 312:
Appendix CD CD-27 Zone no. DRAFT -
Page 313 and 314:
Page 315 and 316:
Appendix CD CD-31 CD.4 IMPLEMENTATI
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Appendix DE DE-7 c. for GNSS, the p
Page 327 and 328:
Appendix DE DE-9 MB FIELD DRAFT - W
Page 329 and 330:
Appendix DE DE-11 MB FIELD DRAFT -
show all

Technical Provisions for Mode S Services and Extended Squitter

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

Delete template?

Save as template?