This project comprised ADAPS and control systems for use in two Control Rooms for the control and operation of three test cells (NAC Test Cells # 5, 6, and 7). The systems were configured for complete overhaul test capability of the following engine types:
The systems were configured for testing of 26 different engine variants within the above engine types. The new systems were installed into operational test cells without any disruption in the normal workflow through the test cells.The successful completion of this project resulted in Yanos Aerospace subsequently installing systems in all of the customer’s remaining test cells.
The system comprised two complete ADAPS products with hardware and software.The systems were completely assembled and tested at Yanos Aerospace prior to delivery of the system.
These were the first systems to use the engine simulator on the real-time system. As such, the customer could actually run a test at Yanos Aerospace in order to verify the function of the system.
The Houston system included all facility and engine control in the installation. As such, the engine control interface was developed along with the use of the console-mounted touch panel for controlling all of the engine, facility and mechanical test system functions.
The new technical items in this test cell were the addition of the engine control and the generation of an interface to that control. The interface had to ensure that the engine functions operated within the engine design limits and that no adverse conditions could exist that would harm the engine.
The facility interface was quite sophisticated as well and included full PID control on the oil temperature through the Yanos Aerospace provide oil system as well as facility fire and safety features associated with the use of natural gas.
The system for the control of the AE1107 FADEC engine was installed in one of the existing test cells and the standard Yanos Aerospace configurations for the logsheet and real time systems were implemented along with the FADEC engine control system using MIL-STD-1553B.
The purpose of the FADEC Interface Software (FIS) was to provide a user interface to manage engine control operations and to view engine information for the AE1107C engine. In addition, the FIS was designed to enable the publishing of parameters such that they can be brought into the real time application. This allows the real time system (RTS) to be capable of treating the FADEC parameters in the same manner as all other parameters, allowing the RTS developer to set up alarms and historical recording in a homogeneous way for all parameters.
Data flows from the two FADECs installed on the engine are controlled through two independent MIL STD 1553 busses and the 1553 card installed on the FADEC interface computer manages messages placed on the bus and received from both FADECs. The FADEC Interface PLC is responsible for handling some of the various discrete IO requirements in the system.