Recorder XML file format

This article presents the XML file format for the recorder and player applications:

• Stored by the recorder Application or the External Communication module
• Read by the player Application

This file format stores the content of the services received by the recorder or External Communication module.

Schema

The schema is: recorder.xsd.

Structure

The file contains record elements. Each record element represents one record, which is a list of services received at one instant.

record

Represents one record, for a time expressed in milliseconds since the start of the framework.

The record contains the list of services sent by the recorder at that time.

For example:

      <record time="639">
         <service name="clock" uri="http://dassault-aviation.com/clock">
            <data name="time" value="1014"/>
         </service>
      </record>

service

Presents one service sent by the recorder. The service contains either:

• The list of data values for this service, if the scenario has been produced by the recorder Application
• The binary content for the whole service, if the scenario has been produced by the External Communication module

For example:

      <service name="clock" uri="http://dassault-aviation.com/clock">
          <data name="time" value="1014"/>
      </service>

Note that:

• A service for which the player application is not a provider will be silently ignored
• A data which has a null value will not have a value or hexValue attribute

buffer

Presents one buffer value for a service. it caontains the whole content of the binary buffer for the service, expressed as an hexadecimal content.

For example:

      <scenario date="2020:06:03 18:22:10" endianness="littleEndian" charAs8Bits="true" >
         <record time="31">
            <service name="service1" >
               <buffer size="34" data="000DA666000000005235101C01000001727AFD762F00000000000000000A00000001" />
            </service>
         </record>
      </scenario>

data

Presents one data value for a service. The value can be expressed either in:

• An hexadecimal value with the hexaValue attribute
• A readable value with the value attribute. This representation will be used for datas of a simple type if the recorder Application writeSimpleValues property is set to true

Note that:

• A data which does not exist in its parent service will be silently ignored by the player application
• A data which has a null value will not have a value or hexValue attribute

For example:

      <service name="aircraftAttitudes">
         <data name="HRS" value="9144.0"/>
         <data name="V_VZH" value="true"/>
      </service>
      <service name="SendLocalizations">
         <data name="currentLocalizations" hexValue="C027EB66"/>
      </service>

Example

      <scenario date="20200205">
         <record time="639">
            <service name="clock" uri="http://dassault-aviation.com/clock">
               <data name="time" value="1014"/>
            </service>
         </record>
         <record time="1653">
            <service name="clock" uri="http://dassault-aviation.com/clock">
               <data name="time" value="2028"/>
            </service>
         </record>
         <record time="2667">
            <service name="clock" uri="http://dassault-aviation.com/clock">
               <data name="time" value="3042"/>
            </service>
         </record>
      </scenario>