WSF_UPLINK_PROCESSOR

Derives From: WSF_SCRIPT_PROCESSOR

Script Classes: WsfUplinkProcessor

processor WSF_UPLINK_PROCESSOR

processor <name> WSF_UPLINK_PROCESSOR

   WSF_SCRIPT_PROCESSOR Commands ...

   max_weapon_uplinks <integer-value>
   weapon_uplink_path <sensor-name> <comm-name>

end_processor

Overview

WSF_UPLINK_PROCESSOR is the default method of access and control for uplinks. If a WSF_TASK_PROCESSOR or RIPR processor has uplink settings specified, those are actually fed to the default uplink processor on their platform. In the future, we envision other uplink processors being made available that might service those uplinks in varied ways. For now, the only operation of the WSF_UPLINK_PROCESSOR matches that of the WSF_TASK_PROCESSOR and RIPR processor. See WsfUplinkProcessor for the various query methods and control methods available. If you do not specify uplink paths (with the weapon_uplink_path command), then all uplinks that are started will be serviced by local track updates for the target of interest.

max_weapon_uplinks <integer>

Specifies the maximum number of active uplinks the RIPR agent is capable of.

Default: 0, no maximum

weapon_uplink_path <sensor-name> <comm-name>

If a weapon uplink path is specified, then the processor will support uplinks by sending track updates over the designated comm to the fired weapon platform using tracks from the designated sensor. Uplinks can be stopped and started from script, see WsfUplinkProcessor.

Default: no paths defined