20.3. Messages supported

Table 20.1. DIS Messages Supported

MessageFieldsRepresentation in Debrief
Entity State
  • Entity Id

  • Location

  • Orientation

  • Velocity

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
  • Issuing Entity

  • Colliding Entity

Create a narrative entry for this event, assigned against the Issuing Entity
Detonation
  • Entity Id

  • Location

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
  • Firing Entity Id

  • Target Entity Id

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
  • Originator Id

  • Event Type

  • Variable Datums

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 20.2, “DIS Event Report messages”)
Start / Resume
  • Time

Update the Debrief DIS Listener View to acknowledge that the simulator is running (e.g. enable the Pause and Stop buttons
Stop / Freeze
  • Time

  • Reason

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 20.2. DIS Event Report messages

TypeEvent TypeSampleParsingRepresentation in Debrief
Comms10001muteTime=0 txFreq=1804 ....VerbatimNarrative entry
Launch10002NAME:FF23Use colon as delimiterCollate lookup table, to translate EntityId to entity name
New TMA Track10003DETECTION E3-3E3-3Collate lookup table, to translate EntityId to entity name
Tactics Change10004XXXX from YYYYVerbatimNarrative entry
New TMA Track (where subject is OSAT)10005DETECTION E3-2E3-2Collate lookup table, to translate EntityId to entity name


comments powered by Disqus