a 2003 document whose - Institute for Simulation and Training ...

542
Section 8
Distributed Emission Regeneration family
9) System ID Record: Change Indicator. The Change Indicator shall be set to 1 for all
initial reports and whenever a change is a being reported even if the change coincides
with a periodic update report. For all other cases, the Change indicator shall be set to 0.
8.3.6.2 Receipt Rules: System Type 1 (Mark X/XII/ATCRBS/Mode S Transponder)
1) System ID Record: Alternate Mode 4. Any application that can receive Mode 4 data
shall be able, as a minimum, to process the Alternate Mode 4 field to derive the present
Mode 4 value. If an application can also process any "pseudo-crypto" value contained in
the Mode 4 parameter, it may either process the Mode 4 value or the Alternate Mode 4
value. If an application can detect a conflict in the Valid/ Invalid setting between the
values in the two fields, the Alternate Mode 4 field value shall be the value that is
accepted.
2) System ID Record: Alternate Mode C. Any application that can receive Mode C shall
be able, as a minimum, to process the Alternate Mode C field in the Fundamental Data
Record. If an application can also process an encoded altimeter value contained in the
Mode C parameter, it may either process the Mode C value or the Alternate Mode C value
(i.e., use the entity's altitude value derived from the Entity State PDU.) If an application
can detect a conflict in the values contained in the two fields, the Mode C field value shall
be the value that is accepted and not the entity altitude from the Entity State PDU.
4) Fundamental Operational Data Record: System Status: Capable Parameters 1-5. If
the Not Capable field is set for a specific parameter (1-5), the receiving site/application
need not process that Parameter's values in the Fundamental Operational Data Record.
5) Fundamental Operational Data Record: Parameter 1-3 Codes. Mode 1, 2 and 3 code
values of zero shall be valid and shall not be interpreted as a Mode Off status.
6) If a receiving site/application has the capability to set transponder data for received
entities for distribution to other applications not directly connected on the DIS network,
receipt of transponder data on the received entity shall always override locally entered
data for the received entity.
7) A receiving site/application may perform validity checks on parameter data to
ensure they are within the limits specified in the DIS enumeration document. Only
invalid data for the specific parameter processed shall be ignored. Any previously
accepted data for that parameter may either be retained or cleared.
8) Fundamental Operational Data Record: Mode Status. The Mode Status - Damage
and Malfunction field values shall be processed upon receipt as agreed to by participants
prior to a DIS exercise.
9) Fundamental Operational Data Record: Parameter 6. Mode S data elements shall
be agreed to by participants prior to a DIS Exercise.
8.3.6.3 Issuance Rules: System Type 5 (RRB Transponder)
1) Fundamental Operational Data Record: System Status: Capable. All RRB
Transponders shall set the Parameter 1 system status bit to 0 (Capable) and the
Parameters 2-6 system status bits to 1 (Not Capable).