Technical Provisions for Mode S Services and Extended Squitter
Technical Provisions for Mode S Services and Extended Squitter
Technical Provisions for Mode S Services and Extended Squitter
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
C-2 <strong>Technical</strong> <strong>Provisions</strong> <strong>for</strong> <strong>Mode</strong> S <strong>Services</strong> <strong>and</strong> <strong>Extended</strong> <strong>Squitter</strong><br />
Notes.—<br />
DRAFT - Working Paper ASP TSGWP11-01 <strong>for</strong> review by the TSG during the meeting in June 2011 in Paris<br />
Register<br />
number<br />
Table C-1. Register Allocation<br />
Assignment<br />
Maximum update<br />
interval<br />
05 16 <strong>Extended</strong> <strong>Squitter</strong> Airborne Position 0.2 s<br />
06 16 <strong>Extended</strong> <strong>Squitter</strong> Surface Position 0.2 s<br />
07 16 <strong>Extended</strong> <strong>Squitter</strong> Status 1.0 s<br />
08 16 <strong>Extended</strong> <strong>Squitter</strong> Identification <strong>and</strong> Category 15.0 s<br />
09 16 <strong>Extended</strong> <strong>Squitter</strong> Airborne Velocity 1.3 s<br />
0A 16 <strong>Extended</strong> <strong>Squitter</strong> Event-Driven In<strong>for</strong>mation variable<br />
61 16 <strong>Extended</strong> <strong>Squitter</strong> Aircraft Status 1.0 s<br />
62 16 Target State <strong>and</strong> Status In<strong>for</strong>mation 0.5 s<br />
63 16-64 16 Reserved <strong>for</strong> <strong>Extended</strong> <strong>Squitter</strong><br />
65 16 <strong>Extended</strong> <strong>Squitter</strong> Aircraft Operational Status 2.5 s<br />
66 16-6F 16 Reserved <strong>for</strong> <strong>Extended</strong> <strong>Squitter</strong><br />
1. The Register number is equivalent to the BDS B-Definition Subfield (BDS) value (see §2.2.14.4.20.b of<br />
RTCA DO-181D [EUROCAE ED-73C, §3.18.4.18.b]).<br />
2. Register 0A16 is not to be used <strong>for</strong> GICB or ACAS crosslink readout.<br />
3. The term “minimum update rate” is used in this Manual. The “minimum update rate” is obtained when data is<br />
loaded in one Register field once every “maximum update interval.”<br />
4. If <strong>Extended</strong> <strong>Squitter</strong> is implemented, then Register 0816 is not cleared or ZEROed once either Flight<br />
Identification or Aircraft Registration data has been loaded into the Register during the current power-on cycle.<br />
Register 0816 is not cleared since it provides in<strong>for</strong>mation that is fundamental to track file management in the ADS-B<br />
environment. Refer to §C.2.4.3.3 <strong>for</strong> implementation guidelines regarding Register 0816.<br />
5. These registers define version 2 extended squitters<br />
Draft<br />
C.2.1.1 The details of the data to be entered into the registers assigned <strong>for</strong> <strong>Extended</strong> <strong>Squitter</strong> shall be as defined in<br />
this Appendix. Table C-1 specifies the maximum update interval at which the appropriate transponder register(s)<br />
shall be reloaded with valid data. Any valid data shall be reloaded into the relevant field as soon as it becomes<br />
available at the <strong>Mode</strong> S Specific <strong>Services</strong> Entity (SSE) interface regardless of the update rate. Unless otherwise<br />
specified, if data are not available <strong>for</strong> a time no greater than twice the specified “maximum update interval,” or 2<br />
seconds (whichever is the greater), then the status bit (if provided) shall indicate that the data in that field are invalid,<br />
<strong>and</strong> the field shall be ZEROed.<br />
C.2.1.2 The register number shall be equivalent to the Comm-B data selector (BDS) value used to address that<br />
register (see §3.1.2.6.11.2.1 of Annex 10, Volume IV).<br />
C.2.2 GENERAL CONVENTIONS ON DATA FORMATS<br />
For requirements on the validity of data, see §A.2.2.1.<br />
C.2.2.1 VALIDITY OF DATA<br />
C.2.2.2 REPRESENTATION OF NUMERICAL DATA<br />
Numerical data shall be represented as specified in §A.2.2.2.<br />
DRAFT - Working Paper ASP TSGWP11-01 <strong>for</strong> review by the TSG during the meeting in June 2011 in Paris