Table 21.1. DIS Messages Supported
Message | Fields | Representation in Debrief |
---|---|---|
Entity State |
| Retrieve the vessel name from the Launch message lookup table, create a track for this fix (if necessary), and add this fix to that track |
Collision |
| Create a narrative entry for this event, assigned against the Issuing Entity |
Detonation |
| Create both a narrative entry for this event, assigned against the Issuing Entity. Also create a text label at the relevant location, placed in the Detonations layer |
Fire |
| Create both a narrative entry for this event, assigned against the Issuing Entity. Also create a text label at the relevant location, placed in the WPN Release layer |
Event Report |
| The Event Report PDU is used as a handler for textual content across a range of simulation events. See the list of event report types below (Table 21.2, “DIS Event Report messages”) |
Start / Resume |
| Update the Debrief DIS Listener View to acknowledge that the simulator is running (e.g. enable the Pause and Stop buttons |
Stop / Freeze |
| Update the Debrief DIS Listener View to acknowledge that the simulator has either stopped or paused (by inspecing the value of the Reason field) |
Table 21.2. DIS Event Report messages
Type | Event Type | Sample | Parsing | Representation in Debrief |
---|---|---|---|---|
Comms | 10001 | muteTime=0 txFreq=1804 .... | Verbatim | Narrative entry |
Launch | 10002 | NAME:FF23 | Use colon as delimiter | Collate lookup table, to translate EntityId to entity name |
New TMA Track | 10003 | DETECTION E3-3 | E3-3 | Collate lookup table, to translate EntityId to entity name |
Tactics Change | 10004 | XXXX from YYYY | Verbatim | Narrative entry |
New TMA Track (where subject is OSAT) | 10005 | DETECTION E3-2 | E3-2 | Collate lookup table, to translate EntityId to entity name |