Transcript Inertial Systems Development

Fire Control-Node Engagement
Technology (FC-NET)
Implementing FC-NET: Initial Experiences
Deborah A. Butler
Aviation and Missile Research,
Development, and Engineering Center
(256)876-1303
[email protected]
DB03-124
UNCLASSIFIED
Overview
DB03-124
15 May 2003

Introduction

XD1 Weapon System

Development Environment

Implementation Description

Conclusion
UNCLASSIFIED
2
The Fire Control Challenge
Unique Point Designs
for Fire Control
TODAY
F
C
S
Reconfigurable,
Flexible,
System of
Systems
•
•
•
•
•
•
•
•
•
“Stove-Pipe” Solutions
Proprietary Solutions
Limited Software Reuse
Non-Interoperable
Large Logistic and O&S Budgets
Non-Scalable
Non-Reconfigurable
Single Weapon Centric
Non-Standards Based
Future Combat Systems
Requires a New Vision for
Providing Fire Control
Capabilities for MultiMissions, Weapons, and
Platforms.
DB03-124
15 May 2003
LNS
SINCGARS
EPLRS
JTRS
IFF
COMMON
MSL
FLIR
DVO
TV
SMI
Weapons Control
Platform Control
COMMS, SA,
Targeting,
BIT, Training
Safety, Security
TURRET
LCPK
CKEM
SASPG
BEYOND LOS
NET FIRES
CM
UGV
UAV
FC-NET
Solution
SM1
The FC-NET Fire Control Architecture
is Modular, Distributable, and
Scalable to Match the Flexible,
Configurable Nature of FCS.
UNCLASSIFIED
3
Fire Control Puts Munitions on Targets
Weapon
System
Weapon Suite
Targets
Weapon
Munition
Launcher
ECC/Gunner
Targeting
Estimator
Target Acquisition
Sensor Suite
Manager
Sensor
Target Selection
Tracker
Acquisition
Weaponeering
Weapons
Assignment
Target
Engagement
Tracking
Track DB
Correlator
Platform Suite
Platform
Position
Damage
Assessment
Operator
Environment
The Fire Control System is a Force Multiplier for the Individual Soldier
More Targets, More Quickly, More Accurately!
DB03-124
15 May 2003
UNCLASSIFIED
4
Program Status



FC-NET is a DoD Science and Technology Objective
(STO) Program.
Currently in Year 2 of the 5 Year Program.
Developing a Series of Experimental Weapon Systems to
–
–
–
–

Partnering with TARDEC (Detroit Arsenal) for
–
–

15 May 2003
Reuse of Existing Integrated Crew Station
User Interface Expertise
Partnering with ARDEC (Picatinny Arsenal) for
–
DB03-124
Evolve the Capabilities of the FC-NET Architecture
Populate a Set of Fire Control Foundation Classes (FCFC)
Integrate Missile- and Gun-Target Pairing Algorithms
Demonstrate FC-NET Applicability to Future Weapon Systems
Gun-Target Pairing Algorithms
UNCLASSIFIED
5
XD1 Weapon System
XD1 is an Experimental Weapon System Composed of
Both Real Hardware and Simulations of Tactical LRUs.
LCPK
(19)
...
CMS
CMS
CMS
CMS
(4)
Launcher
(M261)
Launcher
(M299)
LCPK LEU
CMS LEU
Platform
ICS
Target
Data
DB03-124
15 May 2003
Cueing
Sensor
UNCLASSIFIED
Console
Vehicle
FCC
Position/
Attitude
Sensor
6
Integrated Crew Station (ICS)
DB03-124

Using TARDEC’s Vetronics Technology Testbed (VTT) as
ICS Provides Real Soldier Machine Interface (SMI)
Functionality Using Tactical Hardware

VTT Includes Touch Screen, Map Display and Target List

VTT Provides an Upgrade Path to Next Generation Crew
Station Technology Being Developed by the Crew
Integration and Automation Testbed (CAT) Advanced
Technology Demonstration (ATD).
15 May 2003
UNCLASSIFIED
7
Development System
Development Client
Windows 2000TM PC
VNC, ssh, scp
Development
Server
Development Client
TCP/IP
Windows XPTM PC
VNC, ssh, scp
TCP/IP
Development
Client
Dual 2.4 Ghz XeonTM
2 GB RAM
160 GB disk
-----------------------Redhat GNU/Linux 7.3
gcc
CVS
Apache
GNATS
TFTP
NFS
RLOGIN
Target
System
Windows 2000TM PC
VNC, ssh, scp
DB03-124
15 May 2003
UNCLASSIFIED
8
Free and Open Source Tools


fcnetidl Compiler
–
Custom Tool Based on ORBit IDL Parsing Library
–
Automatically Generated Approximately 350,000 C++ SLOC
–
Generated Code for
15 May 2003
Client-Server Communications

XD1 Application and FCFC Class Skeletons
Doxygen
–
DB03-124

Automatically Generated 1282 Page API Description Document
UNCLASSIFIED
9
Target System
Fire Control Computer
VTT
TCP/IP
Development
System
TCP/IP
TFTP
NFS
RLOGIN
DB03-124
15 May 2003
Radstone VME64 SBC
400 Mhz PowerPC 7410
256 MB RAM
64 MB Flash
4 serial ports
10/100 BaseT
UltraSCSI
Dual redundant 1553 Interface
-----------------------------------------LynxOS 3.1.1
FCFC
FCNETcomms
GNU Common C++
WSTAWG OE 2.0
libXML2
xmlwrap
UNCLASSIFIED
CMS LEU
TCP/IP
LCPK LEU
TCP/IP
M20 Platform
RS232
10
Free and Open Source Libraries

GNU Common C++
–

WSTAWG OE 2.0
–

15 May 2003
Support for XML-Based Configuration Files
xmlwrap
–
DB03-124
C++ Bindings Developed for TARDEC OE 2.0 Implementation
libXML2
–

Provides an Abstract Interface for Serial Ports and TCP/IP Sockets
C++ Wrapper for libXML2
UNCLASSIFIED
11
FC-NET SIL Logical Connectivity
DIS Network
SIL Network
RISC
Mission Simulation
Embedded
Simulation
System
Simulation Control
Simulation World View
LCPK LEU Simulation
Vetronics
Technology
Testbed
Vehicle
Simulation
CMS LEU Simulation
Simulation Logging
Tactical Interface
Platform Simulation
Laser Designator Simulation
Fire Control Computer
Weapon
Advisor
Fire Control
Weapon System
Simulation
Battlespace Simulation
Weapon
System
Network
SIL Network
DB03-124
15 May 2003
UNCLASSIFIED
Munition Simulation
DIS Network
12
FC-NET API Implementation
DB03-124

Based Upon the FC-NET Architecture

Defined in Object Management Group (OMG) IDL
–
IDL is Standardized and Compilable
–
IDL has Mappings to C, C++, Java, Ada, ...

IDL use Forced Consideration of Implementation Issues

Implementation Issues Led to Revisions in Architecture

Language-Independence of IDL Limits Object-Oriented
Implementations
15 May 2003
–
No Function Overloading
–
No Polymorphism
–
Single Inheritance Only
UNCLASSIFIED
13
Impact of IDL on Implementation
DB03-124

Identified and Isolated Commonalities in Position- and
Device-Oriented Components

Developed a Position Class Hierarchy that Incrementally
Exposes Different Types of Position Information (e.g.,
Location, Orientation, Acceleration)

Developed a Common State Model for all Physical
Devices (e.g., Launcher, Platform, Munition).

Device State Model is Embedded in a Device Class
Hierarchy Built on Top of the Position Class Hierarchy
15 May 2003
UNCLASSIFIED
14
Impact of Implementation on
Architecture
DB03-124

Implementation Required Refinement of the Architecture’s
Initial Set of Attributes, Services, and Notifications

Services, Attributes, and Notifications were Renamed to
Enhance Naming Consistency Across Components.

Services, Attributes, and Notifications were Added to Ease
Necessary Component Interactions

Components were Consolidated to Enhance
Encapsulation
15 May 2003
UNCLASSIFIED
15
Example Munition Domain Component
Consolidation
Launcher
Domain
BEFORE
Munition
Predictor
Munition
Operator
Munition
Devices
Munition
Physical
Munition
Devices
Launcher
Domain
AFTER
Munition
Predictor
Munition
Munition
Devices
DB03-124
15 May 2003
UNCLASSIFIED
Physical
Munition
Devices
16
FC-NET XD1 Source Code Structure

FC-NET is Written in ANSI C++

XD1 Application is Built on a Multi-Tiered Foundation of
Supporting Classes

Every Application Component Runs as an Independent
Process
XD1 Application Code
XD1 Skeleton Classes
FC-NET Fire Control
Foundation Classes
FC-NET Communications
Library
DB03-124
15 May 2003
UNCLASSIFIED
17
Conclusions
DB03-124

The Architecture is Feasible

Implementing Components as Separate Processes Has
–
Eased Assignment of Programming Tasks to Developers
–
Reduced Developer Interdependence During Testing
–
Eased Construction of Test Clients and Subsystems
–
Eased Fault Isolation

Communication Overhead of Separate Processes is
Acceptable, Even in Initial Implementation

Use of XML Files Provides Flexible, Uniform, and Readable
Component Configuration Capability
15 May 2003
UNCLASSIFIED
18
Contact Information
DB03-124
Deborah A. Butler
Joel Sherrill
FC-NET Program Manager
Director of Research and Development
U.S. Army Aviation and Missile Command
OAR Corporation
ATTN: AMSAM-RD-MG-NC (Deborah A. Butler)
4910-L Corporate Drive
Redstone Arsenal, AL 35898-5000
Huntsville, AL 35805
Voice: 256-876-1303
Voice: 256-722-9985
FAX: 256-876-9476
FAX: 256-722-0985
[email protected]
[email protected]
15 May 2003
UNCLASSIFIED
19