06.03.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

543<br />

Section 8<br />

Distributed Emission Regeneration family<br />

2) Fundamental Operational Data Record: System Status: System On/Off. The System<br />

On/Off Status shall be set to 1 (On) if the RRB Response Status (bit 13 in Parameter 1) is<br />

set to 1 (On), the RRB Response Damage (bit 14 in Parameter 1) is set to 0 (No Damage)<br />

<strong>and</strong> the RRB Response Malfunction (bit 15 in Parameter 1) is set to 0 (no malfunction).<br />

Otherwise the status shall be set to 0 (Off). If the Entity State PDU Appearance Damage<br />

Status value = 3 (Destroyed) <strong>for</strong> the associated entity <strong>and</strong> the entity is not canceled at the<br />

time it is destroyed, the System Status/System On/Off field <strong>and</strong> the Parameter 1 Status<br />

fields (Bit 13) shall be set to 0 (Off). This change in status shall be automatically set<br />

within 10 seconds of the simulation determining that the entity could no longer transmit a<br />

reply to an interrogation. For the destroyed case, it is not required that the Operational<br />

Status field be set to System Failed or the Parameter 1 Damage or Malfunction Status<br />

fields be set to 1. However, these fields can be set if desired. At least three periodic<br />

updates shall be sent <strong>for</strong> the IFF/ATC/NAVAIDS PDU following the change to Off status<br />

due to the entity being destroyed. After the three periodic updates are sent, a simulation<br />

may either continue to send periodic updates or cease sending them.<br />

3) Fundamental Operational Data Record: Operational Status. This status shall be set<br />

to 1 (System failed) if the RRB Response Damage bit (bit 14 in Parameter 1) is set to 1<br />

(Damaged) or the RRB Reponse Malfunction bit (bit 15 in Parameter 1) is set to 1<br />

(Malfunction). Otherwise, the status shall be set to 0.<br />

4) Fundamental Operational Data Record: Parameter 1 Code. Codes shall reflect the<br />

present code settings <strong>for</strong> an entity at the time an IFF/ATC/NAVAIDS PDU is transmitted<br />

<strong>and</strong> are independent of the present Mode Status settings. Code 0 shall not be used to<br />

indicate off <strong>for</strong> a mode. However, code zero may be transmitted <strong>for</strong> a mode if that is the<br />

setting <strong>for</strong> the transponder.<br />

5) System ID Record: Change Indicator. The Change Indicator shall be set to 1 <strong>for</strong> all<br />

initial reports <strong>and</strong> whenever a change is a being reported even if the change coincides<br />

with a periodic update report. For all other cases, the Change indicator shall be set to 0.<br />

8.3.6.4 Receipt Rules: System Type 5 (RRB Transponder)<br />

1) Fundamental Operational Data Record: Parameter 1 Codes. Code values of zero<br />

shall be valid <strong>and</strong> shall not be interpreted as a Mode Off status.<br />

2) If a receiving site/application has the capability to set transponder data <strong>for</strong> received<br />

entities <strong>for</strong> distribution to other applications not directly connected on the DIS network,<br />

receipt of transponder data on the received entity shall always override locally entered<br />

data <strong>for</strong> the received entity.<br />

3) A receiving site/application may per<strong>for</strong>m validity checks on parameter data to<br />

ensure they are within the limits specified in the DIS enumeration <strong>document</strong>. Only<br />

invalid data <strong>for</strong> the specific parameter processed shall be ignored. Any previously<br />

accepted data <strong>for</strong> that parameter may either be retained or cleared.<br />

4) Fundamental Operational Data Record: Mode Status. The Mode Status - Damage<br />

<strong>and</strong> Malfunction field values shall be processed upon receipt as agreed to by participants<br />

prior to a DIS exercise.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!