Rotary-wing Entities

Table of Contents

• Core Elements of Rotary-wing Entities
• Component Systems that Make Up a Rotary-wing Entity
  • A Specific Example: AH-64 Apache
  • Systems
  • Other Simulation Components
    • Sensors
    • Controllers
    • Actuators

Rotary-wing entities are simulated as platform-level entities in VR-Forces.

Examples include the AH-64 Apache and UH-60 Blackhawk.They share some of the same subsystems and components, such as the IR sensor and the movement dynamics models. Depending on the aircraft, some may be outfitted with missile launchers (e.g. Hellfire Missile Launcher), while others may have a different type of sensor (e.g. Airborne Targeting RADAR).

Core Elements of Rotary-wing Entities

Rotary-wing entities in VR-Forces share certain common elements. A typical rotary-wing entity in VR-Forces is always configured with the following:

• DtRotaryWingEntityStateRepository -- Holds state information specific to rotary-wing entities.
• DtSimIndividualLocalEntityNetInterface -- Handles network publishing of individual (platform-level entities)

Note that many of the DtSimComponents that make up a rotary-wing entity's behavior and dynamics require a state repository of type DtRotaryWingEntityStateRepostiory.

Component Systems that Make Up a Rotary-wing Entity

Rotary-wing entities also share many of the same systems and simulation components (sensors, controllers, and actuators). To examine the systems typically configured on a rotary-wing entity, we'll look at a specific instance of a helicopter, the AH-64 Apache entity. Differences arise between the various types of entities as a function of what particular sub-systems are configured on the vehicle, and the parameter values it is configured with.

A Specific Example: AH-64 Apache

Defined in parameter file US-generic-attack-helicopter-platform_1_1_2_225_20_-1_-1_-1.ope

The figure below shows which systems and simulation components are configured as part of an Apache. The boxes (nodes) represent either a system of components (DtComponentSystem) or individual DtSimComponent classes. The edges connecting the boxes indicate port or port group connections between components. Information such as detected targets and control inputs are exchanged between components through ports.

Apache

Systems

Major sub-elements of an entity's capabilities are organized into systems.

• IR Sensor -- Infra-red sensor for detecting entities.
• Rotary Wing Default Armor -- Determine damage as a result of direct and indirect fire.
• Rotary Wing Attack Movement -- The kinematics model for movement and the associated sensors and controllers that implement movement behaviors for rotary-wing entities. Configured with parameter values appropriate for an attack helicopter (as opposed to a utility helicopter).
• Spot Report Generator -- Send spot reports based on my contact list.
• Spot Report Receiver -- Listen for spot reports.
• Hellfire Missile Launcher -- Missile launcher for Hellfire missiles.
• Sidewinder Missile Launcher -- Missile launcher for Sidewinder air-to-air and air-to-ground missiles.
• Laser Designator -- Laser designator system.

Other Simulation Components

Individual DtSimComponents (not organized as part of a system) that make up the rest of entity:

Sensors

There are no sensors directly configured as part of this entity.

Controllers

• Organization -- Maintain my position in the aggregate organizational hierarchy.
• Set-data -- Respond to DtSetDataRequests, such as set location, set heading.
• Target Selection -- Choose target for weapon system.
• Contact Fusion -- Fuse contact information from various sources into a single list.
• Send Radio Message Controller -- Send text or task messages through the radio.
• Embarkation -- Support entity's ability to embark on other entities.

Actuators

There are no actuators directly configured as part of this entity.