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-24 Technical Provisions for Mode S Services and Extended Squitter Coding (“ME” bit 31) 0 1 Table C-11. “Selected Heading Sign” Subfield Encoding Meaning Data being used to encode “ME” bits 32 – 39 (Message bits 64 – 71) is Positive in an angular system having a range between +180 and –180 degrees. (For an Angular Weighted Binary system which ranges from 0.0 to 360 degrees, the sign bit is positive or Zero for all values that are less than 180 degrees). See Table C-12. Data being used to encode “ME” bits 32 – 39 (Message bits 64 – 71) is Negative in an angular system having a range between +180 and –180 degrees. (For an Angular Weighted Binary system which ranges from 0.0 to 360 degrees, the sign bit is ONE for all values that are greater than 180 degrees). See Table C-12. C.2.3.9.8 Selected Heading a. The “Selected Heading” subfield is an 8-bit (“ME” bits 32 – 39, Message bits 64 – 71) field that contains Selected Heading data encoded in accordance with Table C-12. b. Encoding of Selected Heading data in “ME” bits 31 – 39 (Message bits 63 – 71) shall be rounded so as to preserve accuracy of the source data within ±½ LSB. c. Whenever there is NO valid Selected Heading data available, then the Selected Heading Status, Sign, and Data subfields (“ME” bits 30 – 39, Message bits 62 – 71) shall be set to ZERO (0) as indicated in Table C-12. Table C-12. “Selected Heading Status, Sign and Data” Subfields Encoding “ME” Bit Coding 30 31 32 -------- 39 Meaning Status Sign Data 0 0 0000 0000 NO Data or INVALID Data 1 0 0000 0000 0.0 degrees 1 0 0000 0001 0.703125 degrees 1 0 0000 0010 1.406250 degrees * * **** **** **** **** **** * * **** **** **** **** **** * * **** **** **** **** **** 1 0 1111 1111 179.296875 degrees 1 1 0000 0000 180.0 or -180.0 degrees 1 1 0000 0001 180.703125 or -179.296875 degrees 1 1 0000 0010 181.406250 or -178.593750 degrees * * **** **** **** **** **** * * **** **** **** **** **** * * **** **** **** **** **** 1 1 1000 0000 270.000 or -90.0000 degrees 1 1 1000 0001 270.703125 or -89.296875 degrees 1 1 1000 0010 271.406250 or -88.593750 degrees 1 1 1111 1110 358.593750 or -1.4062500 degrees 1 1 1111 1111 359.296875 or -0.7031250 degrees Draft C.2.3.9.9 Navigation Accuracy Category for Position (NACP) This 4-bit (“ME” bits 40 – 43, Message bits 72 – 75) subfield shall be used to indicate the Navigational Accuracy Category of the navigation information used as the basis for the aircraft reported position. The NAC P subfield shall be encoded as shown in Table C-13. If an update has not been received from an onboard data source for NAC P within the past 2 seconds, then the NAC P subfield shall be encoded as a value indicating “Unknown Accuracy.” DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Appendix C C-25 Notes.— DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Table C-13. Encoding of Navigation Accuracy Category for Position (NACP) Coding (Binary) (Decimal) Meaning = 95% Horizontal Accuracy Bounds (EPU) 0000 0 EPU ≥ 18.52 km (10 NM) - Unknown accuracy 0001 1 EPU < 18.52 km (10 NM) - RNP-10 accuracy 0010 2 EPU < 7.408 km (4 NM) - RNP-4 accuracy 0011 3 EPU < 3.704 km (2 NM) - RNP-2 accuracy 0100 4 EPU < 1852 m (1NM) - RNP-1 accuracy 0101 5 EPU < 926 m (0.5 NM) - RNP-0.5 accuracy 0110 6 EPU < 555.6 m ( 0.3 NM) - RNP-0.3 accuracy 0111 7 EPU < 185.2 m (0.1 NM) - RNP-0.1 accuracy 1000 8 EPU < 92.6 m (0.05 NM) - e.g., GPS (with SA) 1001 9 EPU < 30 m - e.g., GPS (SA off) 1010 10 EPU < 10 m - e.g., WAAS 1011 11 EPU < 3 m - e.g., LAAS 1100 - 1111 12 - 15 Reserved 1. The Estimated Position Uncertainty (EPU) used in the table is a 95% accuracy bound on horizontal position. EPU is defined as the radius of a circle, centered on the reported position, such that the probability of the actual position lying outside the circle is 0.05. When reported by a GPS or GNSS system, EPU is commonly called HFOM (Horizontal Figure of Merit). 2. RNP accuracy includes error sources other than sensor error, whereas horizontal error for NACP only refers to horizontal position error uncertainty. 3. A non-excluded satellite failure requires that the NACP parameter be set to ZERO (binary 0000) along with RC being set to Unknown to indicate that the position has been determined to be invalid (see §C.2.3.1.1.3 and §C.2.3.1.2.4). C.2.3.9.10 Navigation Integrity Category for Baro (NICBARO) This 1-bit (“ME” bit 44, Message bit 76) subfield shall be used to indicate whether or not the barometric pressure altitude being reported in the Airborne Position Message (§C.2.3.2) has been cross-checked against another source of pressure altitude. The NICBARO subfield shall be encoded as shown in Table C-14. If an update has not been received from an on-board data source for NICBARO within the past 2 seconds, then the NICBARO subfield shall be encoded as a value of ZERO (0). Draft Table C-14. NICBARO Encoding Coding Meaning The barometric altitude that is being reported in the Airborne Position 0 Message is based on a Gilham coded input that has not been crosschecked against another source of pressure altitude The barometric altitude that is being reported in the Airborne Position Message is either based on a Gilham code input that has been cross- 1 checked against another source of pressure altitude and verified as being consistent, or is based on a non-Gilham coded source Notes.— 1. The barometric altitude value itself is conveyed within the ADS-B Position Message. 2. The NICBARO subfield provides a method of indicating a level of data integrity for aircraft installed with Gilham encoding barometric altitude sources. Because of the potential of an undetected error when using a Gilham encoded altitude source, a comparison will be performed with a second source and only if the two sources agree will the NICBARO subfield be set to a value of “1”. For other barometric altitude sources (Synchro or DADS) the integrity of the data is indicated with a validity flag or SSM. No additional checks or comparisons are necessary. For these sources the NICBARO subfield will be set to a value of “1” whenever the barometric altitude is valid. 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 211: DRAFT - Working Paper ASP TSGWP11-0
Page 219 and 220: Msg Bit # “ME” Bit # Appendix C
Page 221 and 222: Appendix C C-33 Msg Bit # "ME” Bi
Page 227 and 228: Appendix C C-39 Notes.— DRAFT - W
Page 229 and 230: Appendix C C-41 Notes.— DRAFT - W
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 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

Create successful ePaper yourself

Delete template?

Save as template?