The ART office is open Monday through Friday, from 9:00 AM to 5:00 PM PST.
If you are having issues with our software products, please send a detailed description of the issue to helpdesk@flightlab.com
Node-locked license
For a node-locked license, ART issues a license file for a designated computer. The FLIGHTLAB license is thus locked to running on that machine only. Multiple users may log in to this machine and run an arbitrary number of instances of the software.
Floating license
For a floating license, ART assists the customer in setting up a license server. ART then issues a license token (Yubikey) that is plugged into the server. The user then sits down at a computer connected to the server and launches a FLIGHTLAB process, which pulls the license from the server.
Cluster license
Cluster licensing is available, but the implementation varies from customer to customer and requires a technical discussion.
To obtain the license, send your machine ID to license@flightlab.com. One recieved, we will generate the license file, which will either be e-mailed to the customer or uploaded to the customer's portal account.
If your computer fails, contact ART. They will provide you with a license transfer form where you will provide the machine ID for the replacement computer. ART will then issue a new license assigned to that computer.
ART has available two different FLIGHTLAB software packages:
The type of model that runs in the Development System is called a Development Model and the type that runs in the Run-time System is called a Run-time Model.
Development Models consist of the input files used by the FLIGHTLAB Development System to create the model. In this environment, the user has complete access to the model data and structure and can edit any aspect of the model and conduct extensive engineering analysis of the model.
Run-time Models are models that run in the FLIGHTLAB Run-time System, independent of the Development System. These models are produced from the FLIGHTLAB Development System for a Development Model and require the FLIGHTLAB Run-time System for execution. Run-time Models contain the aircraft specific data and modeling structure required by the Run-time System to create and run the model, however the modeling data is not user-accessible. The Run-time System includes:
A FLIGHTLAB Run-time Model may be integrated with an external simulation software package that supports the Functional Mockup Interface (FMI) via an FMU. This requires a Generic FLIGHTLAB Run-time License.
A typical application for the FMU is flight control system development in Simulink requiring a fully nonlinear FLIGHTLAB model.
FMU is supported on both Linux and Windows.
Linux Support:
Windows Support: