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 A-4 Technical Provisions for Mode S Services and Extended Squitter A.2.2 GENERAL CONVENTIONS ON DATA FORMATS A.2.2.1 VALIDITY OF DATA The bit patterns contained in the 56-bit transponder registers (other than registers accessed by BDS codes 0,2; 0,3; 0,4; 1,0; 1,7 to 1,C; 2,0 and 3,0) shall be considered as valid application data only if: 1) the Mode S specific services capability is present. bit is set in register number 1016. This is indicated by bit 25 of the data link capability report contained in register 1016 being set to “ONE”, and 2) the GICB service corresponding to the application is shown as “supported” by the corresponding bit in the GICB capability reportCommon Usage Capability Report (register numbers 1716 )to 1C16 being set to “ONE”; and Note 1.— The intent of the capability bits in register number 1716 is to indicate that useful data are is contained in the corresponding transponder register. For this reason, each bit for a register is cleared if data becomes unavailable (see §A.2.5.4.1) and set again when data insertion into the register resumes. Note 2.— A bit set in registers numbers 1816 to 1C16 indicates that the application using this register has been installed on the aircraft. These bits are not cleared to reflect the real-time loss of an application, as is done for register number 1716 (see §A.2.5.4.2). 3) the data value is valid at the time of extraction. This is indicated by a data field status bit (if specified for that fieldprovided). When this status bit is set to “ONE” the data field(s) which follow, up to the next status bit, are valid. When this status bit is set to “ZERO”, the data field(s) are invalid. Numerical data shall be represented as follows: A.2.2.2 REPRESENTATION OF NUMERICAL DATA 1) Numerical data shall be represented as binary numerals. When the value is signed, two’s complement representation shall be used, and the bit following the status bit shall be the sign bit. 2) Unless otherwise specified, whenever more bits of resolution are available from the data source than in the data field into which that data are is to be loaded, the data shall be rounded to the nearest value that can be encoded in that data field. Draft Note.— Unless otherwise specified, it is accepted that the data source may have fewer less bits of resolution than the data field. 3) When the data source provides data with a higher or lower range than the data field, the data shall be truncated to the respective maximum or minimum value that can be encoded in the data field. 4) Where ARINC 429 data are used, the ARINC 429 status bits 30 and 31 shall be replaced with a single status bit, for which the value is VALID or INVALID as follows: a) If bits 30 and 31 represent “Failure Warning, No Computed Data” then the status bit shall be set to “INVALID”. b) If bits 30 and 31 represent “Functional Test” then the status bit shall be set to “INVALID”. c) If bits 30 and 31 represent “Normal Operation,” “plus sign,” or “minus sign,” then the status bit shall be set to “VALID” provided that the data are being updated at the required rate (see §A.2.1.1). 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 A A-5 d) If the data are not being updated at the required rate (see §A.2.1.1), then the status bit shall be set to “INVALID”. For interface formats other than ARINC 429, a similar approach is used. 5) In all cases where a status bit is specified in the data field it shall be set to “ONE” to indicate VALID and to “ZERO” to indicate INVALID. Note.— This facilitates partial loading of the registers. 6) When specified in the field, the switch bit shall indicate which of two alternative data types is being used to update the parameter in the transponder register. 7) Where the sign bit (ARINC 429 bit 29) is not required for a parameter, it has been actively excluded. 8) Bit numbering in the MB field shall be as specified in Annex 10, Volume IV (see §3.1.2.3.1.3). 89) Registers containing data intended for broadcast Comm-B shall have the broadcast identifier located in the eight most significant bits of the MB field. A.2.2.2.1 Recommendation.— When multiple data sources are available, the one with the highest resolution should be selected. Note 1.— Tables are numbered Table A.2-X where “X” is the decimal equivalent of the BDS code that is used to access the register to which the format applies. As used in this Manual, BDS A,B is equivalent to Register AB16. Note 2.— By default, values indicated in the range of the different fields of registers have been rounded to the nearest integer value or represented as a fraction. A.2.2.3 RESERVED FIELDS Unless specified in this document, these bit fields shall be are reserved for future allocation by ICAO and they shall be set to ZERO. Draft A.2.3 EXTENDED SQUITTER FORMATS This section defines the formats and coding that shall be used for extended squitter ADS-B messages. The convention for register numbering shall not be required for an extended squitter/non-transponder device (ES/NT, Annex 10, Volume IV, §3.1.2.8.7). The data content and the transmit times shall be the same as specified for the transponder case. 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 27: DRAFT - Working Paper ASP TSGWP11-0
Page 31 and 32: Appendix A A-7 TYPE Code Format Hor
Page 37 and 38: Appendix A A-13 The supersonic vers
Page 39 and 40: Appendix A A-15 The transponder sha
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 71 and 72: Appendix A A-47 MB FIELD 1 2 3 4 5
Page 79 and 80:
Appendix A A-55 MB FIELD 1 BDS A,8
Page 81 and 82:
Appendix A A-57 MB FIELD DRAFT - Wo
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:
DRAFT - Working Paper ASP TSGWP11-0
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:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Appendix B B-33 MB FIELD DRAFT - Wo
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Appendix B B-41 CF value ICAO/Mode
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Appendix C C-5 Table C-2. “TYPE
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Appendix C C-11 C.2.3.2.2 Time Sync
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Appendix C C-25 Notes.— DRAFT - W
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Msg Bit # “ME” Bit # Appendix C
Page 221 and 222:
Appendix C C-33 Msg Bit # "ME” Bi
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Appendix C C-43 Notes. — DRAFT -
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Appendix C C-51 3. The decoded posi
Page 241 and 242:
Page 243 and 244:
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 249 and 250:
Page 251 and 252:
Page 253 and 254:
Appendix C C-65 Register 0A16 Figur
Page 255 and 256:
Page 257 and 258:
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

Create successful ePaper yourself

Delete template?

Save as template?