Skip to main content
Version: 4.14

Data Handling

The Data Handling subsystem is responsible for the collection, storage, and transmission of data within and between agents.

Data Types

Before configuring the data handling behavior for an agent, you must first define the types of data that the system will manage. You could treat all data as the same type, but specifying different data types here allows for dedicated data interfaces and simulation results specific to each data type.

Create a data type

Add the following data types:

Data Type Name
Telemetry
Remote Sensing

Data Storage

Data storage is attached to other components and is where data of any type can be stored. Data flowing to a component will either pass through the component if there is an active data interface that allows it, or it will be stored in the component's data storage until such an interface becomes active.

Create data storage

Create the following data storage devices:

Storage NameStorage Capacity (bits)Max Write Bitrate (bit/s)Max Read Bitrate (bit/s)Component
TT&C Storage5000000000010000003000000Flight Computer
Sensing Storage350000000000100000000100000000Payload Computer
Crosslink Modem Storage6400000000050000000100000000Crosslink Modem

Data Handling Devices

Data handling devices are components that are specifically responsible for receiving and transmitting data.

Create a data handling device

Create the following data handling devices:

Device NameDevice TypeField of View
Crosslink AntennaAntennaCrosslink FoV
Crosslink ModemModem

Data Interfaces

Data interfaces facilitate the flow of data. Internal data interfaces connect components within an agent and external data interfaces connect the data handling devices of different agents in a scenario.

Create a data interface

Create the following internal data interfaces:

Data Interface NameBitrate (bit/s)Data TypeInterface TypeData SourceData SinkData BusAlways ActiveOperational Modes
Comp. to Crosslink Modem Inter.60000000TelemetryInternal Data InterfaceFlight ComputerCrosslink ModemCrosslink
Cam to Payload Comp. Interface100000000Remote SensingInternal Data InterfacePayload CameraPayload ComputerImaging
Payload Comp. to CL Modem Inter.80000000Remote SensingInternal Data InterfacePayload ComputerCrosslink ModemCrosslink

Create the following cooperative transmit interfaces:

Data Interface NameBitrate (bit/s)Data TypeInterface TypeModemDirected Energy DeviceLink TargetAlways ActiveOperational Modes
Crosslink Interface (T)80000000TelemetryCooperative Transmit InterfaceCrosslink ModemCrosslink AntennaLaserComm RelaysCrosslink
Crosslink Interface (RS)80000000Remote SensingCooperative Transmit InterfaceCrosslink ModemCrosslink AntennaLaserComm RelaysCrosslink

Data Modes

Data modes are necessary if you want to create or delete data on a component without using external data interfaces. For Wildfire, we will use data modes as the origin of our two data types.

Create a data mode

Create the following data modes:

Data Mode NameComponentsData TypesInput Bitrate (bit/s)Output Bitrate (bit/s)Always ActiveOperational Modes
OperatingFlight ComputerTelemetry0500000
Remote SensingPayload CameraRemote Sensing064000000Imaging

Data Buses

Data buses allow you to group internal data interfaces together for analytical purposes. You do not have to add any data buses to Wildfire.