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 CD-4 Technical Provisions for Mode S Services and Extended Squitter CD.2.4.1.1 BIT 9 (CONTINUATION FLAG) This bit should be set as specified in Table A-2-16 of Appendix A. In order to determine the extent of any continuation of the data link capability report (into those registers reserved for this purpose: register 1116 to register 1616), bit 9 is reserved as a ‘continuation flag’ to indicate if the subsequent register can be extracted. For example: upon detection of bit 9=1 in register 1016 then register 1116 can be extracted. If bit 9=1 in register 1116 then register 1216 can be extracted, and so on (up to register 1616). Note that if bit 9=1 in register 1616 then this shall be considered as an error condition. As long as transponder registers 1116 to 1616 are undefined, bit 9 should be set to 0. CD.2.4.1.2 BIT 16 AND BITS 37-40 (ACAS BITS) The setting of these bits is dynamic. They are set by ACAS and possibly overwritten by the transponder. These bits should be set as specified in Table A-2-16. Bit 16 should be set to ONE (1) to indicate that the transponder ACAS interface is operational and the transponder is receiving TCAS RI=2, 3 or 4. Bit 37 should be set to ONE (1) to indicate the capability of Hybrid Surveillance, and set to ZERO (0) to indicate that there is no Hybrid Surveillance capability. Bit 38 should be set to ONE (1) to indicate that the ACAS is generating both TAs and RAs, and set to ZERO (0) to indicate the generation of TAs only. Bits 39 and 40 should be set according to the ACAS version: Bit 40 Bit 39 Meaning 0 0 RTCA DO-185 (6.04A) (see Note 2) 0 1 RTCA DO-185A (see Note 2) 1 0 RTCA DO-185B / EUROCAE ED-143 1 1 Reserved for future versions Note 1.— Future versions of ACAS will be identified using Part Numbers and Software Version Numbers specified in Registers E516 and E616. Note 2.— RTCA DO-185 equipment is also referenced as TCAS logic version 6.04A. Equipment compliant to RTCA DO-185A, or later versions, are SARPs compliant. CD.2.4.1.3 BITS 17-23 (MODE S SUBNETWORK VERSION NUMBER) These bits should be set as specified in Table A-2-16 of Appendix A. 17-23 Mode S subnetwork version number. 0 = Mode S subnetwork not available 1 = Version No. 1 (ICAO Doc 9688 - 1996) 2 = Version No. 2 (ICAO Doc 9688 - 1998) 3 = Version No. 3 (Annex 10 Vol III, Amendment 77 - 2002) 4 = Version No. 4 (2007), 1st Edition of this document 5 = Version No. 5 2nd Edition of this document 56-127 = Unassigned Draft The Mode S subnetwork version number should be set to a non-zero value if at least one DTE or Mode S specific service is installed. For example, if register 4016 is loaded with data, it means that the GICB service associated to register 4016 is installed. In that case bits 17-23 will be set to a non-zero value, e.g. value 3 if the format of register 4016 meets the requirements of Amendment 77 (applicable in 2002). If the installed DTE or the Mode S specific services meet the requirements of Amendment 71 and ICAO Doc 9688 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 CD CD-5 (applicable in 1996) only, then the Mode S subnetwork number should be set to 1. If the installed DTE or the Mode S specific services meet the requirements of Amendment 73 (applicable in 1998) only and/or the transponder register formats meet the requirements of Doc 9688 version 1, then the Mode S subnetwork number should be set to 2. If the installed DTE or the Mode S specific services meet the requirements of Amendment 77, then the Mode S subnetwork number should be set to 3. If the installed DTE or the Mode S specific services meet the requirements of ICAO Doc 9871, Edition 1, then the Mode S subnetwork version number should be set to 4. If the installed DTE or the Mode S specific services meet the requirements of ICAO Doc 9871, Edition 2, which additionally complies with RTCA DO-181D and EUROCAE ED-73C, including Change 1, then the Mode S subnetwork version number should be set to 5. The setting of these bits is static. CD.2.4.1.4 BIT 24 (TRANSPONDER ENHANCED PROTOCOL INDICATOR) This bit is set to 1 when the transponder is a level 5 transponder. This bit is set by the transponder itself. It is a static bit. CD.2.4.1.5 BIT 25 (MODE S SPECIFIC SERVICES CAPABILITY) This bit should be set as specified in Table A-2-16, item 2 of Appendix A. When bit 25 is set to 1, it indicates that at least one Mode S specific service is supported and the particular capability reports should be checked. Note.— Registers accessed by BDS codes 0,2; 0,3; 0,4; 1,0; 1,7 through 1,C; 2,0 and 3,0 do not affect the setting of bit 25. This bit actually indicates if the aircraft installation enables the loading of airborne parameters in at least one register not accessed by the BDS codes mentioned above. The setting of this bit is preferably static. Draft CD.2.4.1.6 BITS 26-32 (UPLINK AND DOWNLINK ELM THROUGHPUT CAPABILITY) Bits 26-28 indicate the uplink ELM average throughput capability. These bits are set by the transponder and are preferably static. Bits 29-32 indicate the throughput capability of downlink ELM containing the maximum number of ELM segments that the transponder can deliver in response to an interrogation. These bits are set by the transponder and are preferably static. CD.2.4.1.7 BIT 33 (AIRCRAFT IDENTIFICATION CAPABILITY) This bit should be set as required in Annex 10, Volume IV, §3.1.2.9.1.3: Aircraft identification capability report. Transponders which respond to a ground-initiated request for aircraft identification shall report this capability in the data link capability report (Annex 10, Volume IV, §3.1.2.6.10.2.2.2) by setting bit 33 of the MB subfield to 1. This bit actually indicates whether the aircraft installation supports an interface to load the aircraft identification into the transponder register 2016. It does not take into account the consistency of the data loaded into the register. 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:
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: DRAFT - Working Paper ASP TSGWP11-0
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 287: Appendix CD CD-3 ACTIONS EVENTS DRA
Page 291 and 292: Appendix CD CD-7 too many broadcast
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 307 and 308: Appendix CD CD-23 CD.2.4.7.5 BINARY
Page 311 and 312: Appendix CD CD-27 Zone no. DRAFT -
Page 315 and 316: Appendix CD CD-31 CD.4 IMPLEMENTATI
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?