Changes to Support the Fire At Target Task

Table of Contents

• Changes to the Weapon Component Interface
• Changes to the Target Selection Controller
• Changes to Communication
• DtIntegratedLaserGuidedLauncherController
• Controller Changes to the Lasing Controller
• Other Changes
• New Messages

The new Fire At Target task, which replaces Set Fire Now, required a variety of changes to entity components and interfaces.

Changes to the Weapon Component Interface

The target selection controller (TSC) now communicates with weapon systems through the Weapon Component Interface. Each of the following controllers has a DtWeaponControllerInterface member, which is cached by the TSC:

• DtBallisticGunController
• DtIntegratedLaserGuidedLauncherController
• DtWeaponController
• DtLasingController (The actual interface is part of the DtLasingControllerWeaponInterfaceInput)

Targets are sent from the TSC to the weapon system through the weapon component interface. The weapon and task (in the case of the Fire At Target task) state is sent back to the TSC.

Changes to the Target Selection Controller

The target selection controller now Derives from DtSingleTaskControllerComponent, so it can process DtFireAtTargetTasks. It now uses DtComponentDescriptor because it does not contain the target-priorities any longer. It responds to weapon list requests from the GUI.

The target selection controller no longer contains target priorities. These are defined in the weapon systems and the TSC gets them through the weapon component interface. The TSC now performs permission to fire checks.

The ports the TSC used to use to communicate to weapons are gone. It still communicates with the sensors through ports.

Changes to Communication

Communication between TSC and turreted weapons now goes through the weapon interface, to the weapon controller - the weapon controller sends the target info to the turret, rather than the turret sending it to the weapon controller.

DtIntegratedLaserGuidedLauncherController

DtIntegratedLaserGuidedLauncherController is a subclass of the DtLaserGuidedLauncher. It contains 2 new data members:

• DtEntityListOutputPort* myTargetListOutputPort is connected to a laser designator. When it is given a target, it passes along the target to the laser designator.
• DtWeaponComponentInterface myWeaponComponentInterface. Since this launcher is integrated with a laser designator, it can be explicitly tasked.

If this controller is given a new target while it already has a missile in the air, it will ignore the new target and keep its laser designator on the old target until the missile is removed. Then it will go back to processing targets as usual.

Controller Changes to the Lasing Controller

The lasing controller now has a concept of being “integrated” with a launcher. Whether or not it is integrated determines how it gets target input, as follows:

• If integrated, it creates a DtLasingControllerPortInput, which contains an input port through which the launcher controller sends targets.
• If not integrated, it creates a DtLasingControllerWeaponInterfaceInput, which contains a DtWeaponComponentInterface that the TSC finds and sets targets to.

Other Changes

Permission to fire is now handled in the TSC, instead of within the individual weapon controllers.

The OPD Editor no longer adds connections between target selection controllers and weapon systems.

DtSimComponent has a componentFullName for getting the fully qualified name (unique name) for a component.

In the GUI, DtWeaponListRequestor requests a weapon list from the selected entity when the Fire At Target task dialog is opened. It caches the results.

New Messages

• DtWeaponListRequestAdmin. Sent from the front-end to the back-end to request a weapon list for an entity.
• DtWeaponListResponseAdmin. The response from the back-end with list of weapons for an entity.
• DtFireAtTargetTask. Task to fire upon a target with a specified or automatically chosen weapon.

[<< VR-Forces 4.0.3 to 4.0.4 Simulation Model Set Changes] [Home] [Top of Page] [VR-Forces 4.0.4 to 4.1 API Changes]