FLIGHTLAB, a software development environment to support modeling of dynamic systems from a predefined library of physically based modeling components. Each component is an independent dynamic element such as a spring, a damper, an airfoil section, etc. These components can be interconnected in arbitrary architec-tures to model any desired dynamic system and the parameters of the components can be assigned vehicle-specific values, allowing a wide range of complex models to be built from a common library of modeling components that have been prederived, programmed and tested for reliability.

A numerical “Multi-Body Dynamics” solution approach was developed to support robust solu-tion of the coupled nonlinear implicit differential equations produced by interconnecting these dynamic elements.

FLIGHTLAB includes graphical user interfaces to facilitate modeling and analysis, and code generation capability to allow FLIGHTLAB models to be interfaced with user applications and run

Modeling Component Library
FLIGHTLAB includes a library of modeling components to facilitate the development of flight dynamics models. The classes of components include aerodynamic, control, structure, and propulsion components. These components can be arbitrarily connected in any desired architecture to model dynamic systems. The parameter fields of these components may then be assigned aircraft-specific data to produce the proper dynamic response for the required aircraft.

Solution Methodology The user focuses on interconnecting components and assigning data to represent the aircraft’s design and the built-in component equations and numeric solution process ensure the generation of software that properly models the dynamics of the aircraft.

Analysis FLIGHTLAB includes a number of predefined primitive analysis utilities to support engineering evaluation of the modeled system. Utilities support trim, static equilibrium, and time and frequency response. Also included is a simulation of the performance and dynamic response tests applied to an aircraft during flight testing.

FLIGHTLAB Real-Time Support ART enhanced the FLIGHTLAB Development System with a number of features to facilitate real time operation. In order to facilitate integration with other software required to support a simulator, a shared memory interface was added that allows the users to select the interface data required for their simulator and place it in a shared memory array for access by other applications. Once a model has been developed in FLIGHTLAB it may be code-generated to produce an object library that can be run independently of the Development System on any desired computer.

FLIGHTLAB Model Editor The FLIGHTLAB Model Editor (FLME) provides predefined scripts that model the most commonly used architectures for rotorcraft systems such as rotors, airframes, propulsion systems, etc. The model developer simply selects the desired modeling options at each level of the graphically depicted rotorcraft subsystem hierarchy and he is presented with a dialog box requesting data values for all parameters required by his selected options.

Control System Graphical Editor The Control System Graphical Editor (CSGE) provides the arbitrary architecture capability required to model control systems, which are not amenable to selection from predefined architectures. The developer selects icons representing the desired control elements and interconnects them in a schematic diagram of the control system using a point and click, drag and drop GUI. Dialog boxes

FCM Driver This utility cycles FLIGHTLAB Code generated Models (FCM) and synchronizes them to real time through a system timer or with an external signal, such as a 60 Hz video refresh signal. It also includes an operator con-sole that supports selecting the model to be run, setting initial conditions and configurations, monitoring and recording simulation data, trimming, flying, pausing and resetting the simulation model. All commands available from the operator console are accessible through a remote API for external IOS interfacing.

FLVIS This is an integral image generation utility that supports rendering of OpenFlight files for out-the-window displays, instrument displays, and external view displays. It uses graphics accelerator cards that support OpenGL. The FCM driver communicates with the FLVIS image generation software through a Common Image Generation Interface (CIGI) protocol, so the user may substitute any CIGI compliant Image Generator for FLVIS if desired. FLVIS comes with a generic terrain data base and a generic instrument panel display for demonstration purposes.

FLCOMMS This is an API library that supports communication with FLIGHTLAB shared memory that can be linked with a user’s custom software to interface with the FLIGHTLAB flight dynamics model.

Specifications are subject to change without notice

Network Updating of Shared Memory FLIGHTLAB models can include shared memory data structures, defined by the developer to satisfy interface requirements. The PilotStation NetFLC utility supports network updating of the shared memory data structures so that all networked computers have access to the flight dynamics data structures. The synchronization is done over Ethernet in a UDP multicast mode.

Application Programming Interfaces The shared memory data structures are used for all periodically updated interface data. The FLIGHTLAB Communications (FLCOMMS) API is used to access FLIGHTLAB shared memory data structures from other applications. Interface data and commands that are not updated each cycle are passed through an API that provides remote function calls. The remote command API includes commands such as fly, pause, reset to the last IC, load a new preset of ICs, trim, freeze airframe states, invoke malfunctions, and change environmental conditions. The API can be used to interface this PilotStation functionality, to the Instructor/Operator Station.

Graphical User Interface For PilotStationPilotStation includes the FCM Console, a Graphical User Interface (GUI) to support monitoring and debugging of the FLIGHTLAB Code-generated Model (FCM) flight dynamics model and its interfaces to the simulator. This GUI also allows for user interaction with the PilotStation API as an alternative to the FL-IOS Instructor/Operator Station (IOS) software.

PilotStation Computer and Joystick The above software is installed and tested on a Core2Duo (dual-core) 3GHz PC with 2 GB of memory and 100 GB of mass storage. An NVidea GeForce 8800 GT graphics card is included to drive the visual displays. A CD Rom Drive and a 10/100 Ethernet card are provided. The operating system is the Red Hat Enterprise Linux (RHEL) Version 5 or equivalent. A three axis joystick with discrete switches and a USB interface, such as the Microsoft Sidewinder, provides a flight control capability.