Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

A-14 Technical Provisions for Mode S Services and Extended Squitter A.2.3.5.6.2 Magnetic heading value This 10-bit field shall contain the aircraft magnetic heading (in degrees clockwise from magnetic north) when velocity over ground is not available. The magnetic heading shall be encoded as an unsigned angular weighted binary numeral with an MSB of 180 degrees and an LSB of 360/1 024 degrees, with zero indicating magnetic north. The data in the field shall be rounded to the nearest multiple of 360/1 024 degrees. A.2.3.5.7 DIFFERENCE FROM BAROMETRIC ALTITUDE IN AIRBORNE VELOCITY MESSAGES This 8-bit field shall contain the signed difference between barometric and GNSS altitude. (Coding for this field shall be as indicated in Tables A-2-9a and A-2-9b.) The difference between barometric altitude and GNSS height above ellipsoid (HAE) shall be used if available. If GNSS HAE is not available, GNSS altitude (MSL) shall be used when airborne position is being reported using format TYPE Codes 11 through 18. If airborne position is being reported using format TYPE Code 9 or 10, only GNSS (HAE) shall be used. For format TYPE Code 9 or 10, if GNSS (HAE) is not available, the field shall be coded with all zeros. The basis for the barometric altitude difference (either GNSS (HAE) or GNSS altitude MSL) shall be used consistently for the reported difference. A.2.3.6 STATUS REGISTER FORMAT The status register shall be formatted as specified in the definition of transponder register number 0716 and in the following paragraphs. A.2.3.6.1 PURPOSE DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Unlike the other extended squitter registers, the contents of this register shall not be broadcast. The purpose of this register shall be to serve as an interface between the transponder function and the general formatter/manager function (GFM, 2.5). The two fields defined for this format shall be the transmission rate subfield and the altitude type subfield. A.2.3.6.2 TRANSMISSION RATE SUBFIELD (TRS) Draft This field is only used for a transponder implementation of extended squitter. The TRS shall be used to notify the transponder of the aircraft motion status while on the surface. If the aircraft is moving, the surface position squitter shall be broadcast at a rate of twice per second, and identity squitters at a rate of once per 5 seconds. If the aircraft is stationary, the surface position squitter shall be broadcast at a rate of once per 5 seconds and the identity squitter at a rate of once per 10 seconds. The algorithm specified in the definition of transponder register number 0716 shall be used by the GFM (2.5) to determine motion status and the appropriate code shall be set in the TRS subfield. The transponder shall examine the TRS subfield to determine which rate to use when it is broadcasting surface squitters. A.2.3.6.3 ALTITUDE TYPE SUBFIELD (ATS) This field shall only be used for a transponder implementation of extended squitter. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Appendix A A-15 The transponder shall load the altitude field of the airborne position squitter from the same digital source as used for addressed replies. Note.— This is done to minimize the possibility that the altitude in the squitter is different from the altitude that would be obtained by direct interrogation. If the GFM (2.5) inserts GNSS height (HAE) into the airborne position squitter, it shall instruct the transponder not to insert the barometric altitude into the altitude field. The ATS subfield shall be set to ONE for this purpose. A.2.3.7 EVENT-DRIVEN PROTOCOL The event-driven protocol register shall be as specified in the definition of transponder register number 0A16 in §A.2.5.5 and in the following paragraphs. A.2.3.7.1 PURPOSE DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris The event-driven protocol shall be used as a flexible means to support the broadcast of messages beyond those defined for position, velocity, and identification. Note.— These typically will be messages that are broadcast regularly for a period of time based on the occurrence of an event. An example is the broadcast of emergency/priority status every second during a declared aircraft emergency. A second example is the periodic broadcast of intent information for the duration of the operational condition. A.2.3.8 EMERGENCY/PRIORITY STATUS The emergency/priority status squitter shall be formatted as specified in the definition of transponder register number 6116 and in the following paragraphs. A.2.3.8.1 TRANSMISSION RATE Draft This message shall be broadcast once per second for the duration of the emergency. A.2.3.8.2 MESSAGE DELIVERY Message delivery shall be accomplished using the event-driven protocol (see §A.2.3.7). The broadcast of this message shall take priority over the event-driven protocol broadcast of all other message types, as specified in §A.2.5.5.3. A.2.3.9 RESERVED A.2.3.10 RESERVED A.2.3.11 AIRCRAFT OPERATIONAL STATUS The aircraft operational status message squitter shall be formatted as specified in the definition of register number 6516 and in the following paragraphs. 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 31 and 32: Appendix A A-7 TYPE Code Format Hor
Page 37: Appendix A A-13 The supersonic vers
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 89 and 90:
Appendix A A-65 MB FIELD DRAFT - Wo
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

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

Delete template?

Save as template?