FATE CONTROL STATIONCONCEPTUAL BLOCK DIAGRAM

• Operator Vehicle Interface

Control Console

• Display Surfaces

• Controls

• Display Formats

- Dedicated Switches

• Keyboard & Mouse

• Video Monitors

Communications

• UHF LOS RADIO

• VHF LOS RADIO

• SATCOM (Growth)

• TELCOS

• LAN (Growth)

• WAN (Growth)

• IFF Interrogator

• Differential GPS Station

• Outside Video Sources

UPS

Off Board Flight

Control (Optional)

- Auto Takeoff Systems

- Auto Land Systems

- Off Board Autopilot

- Manual Control

Main Processors & Memory

• Autopilot & Vehicle Control

• Mission Planning

- Sensor Models

- Sensor Management Planning

- Comm Models

- Comm Planning

- Geo/Terrain Models & Data

- Route Planning

- Contingency Planning

- Flight Operations Data

- Ops Data Collections

- Real Time Planning

- Control Station Models

- Control Station OVI Plan

- OVI Map Plan

Antenna

Farm

Outside

World

Aircraft

Data

Transfer

Equipment

Previous slide

Next slide

Back to first slide

View graphic version

CONTROL STATION CONCEPTUAL BLOCK DIAGRAM

This is a conceptual block diagram of the control station. This may not be representative of the actual partitioning but includes the main functions . Basically, it is more detail of some of the conceptual elements in the previous chart. This does show how the elements might communicate with each other.

The Console will contain the Operator Vehicle Interfaces (OVI) such as the switches, displays and keyboards. The Data Transfer Equipment will be located at the console where the operator has easy access. The communications will be controlled and operated from the console, however the actual electronics may be elsewhere. The Main Processors and Memory may be embedded in the console, but may also be separate units. The connections to the outside world, such as LANs, WANs, interphone lines etc. will need to connect with the operator, and for data to the Main Processor . The UPS, most likely, will be a separate unit. The off board control may actually be software and hardware, some of which resides in the control station, some in external ground hardware, and from a system standpoint, software and hardware may reside in the UCAV for this control path. This concept has a ground based console with peripherals. This may actually evolve toward a desktop or laptop computer, and peripherals. It is conceivable the “control station software” or subsets of it may be used in various computers for tailored functions, such as a experiment in field control of UCAVs. In such a case a subset of this architecture may develop using a data link and a laptop as an example of a minimum control station.