Training Handout ‘ec Ascent Simulator Control Panel Module Control Areae Training Handout Mec Contents Chapter Cont Panel Architectural Design 11 Rationale 12 User Interiace, 1 Overview. 2 Main User Interiace . ‘3 Status Sidebar Modul ‘4 Simulator Control Module... .§ Software Loads. 6 7 8 8 Development Load Test Pilot Load Training Load. Simulator Start’ Stop Actions, 10 Simulator Modules Control Module 11 Shortcut Page Module... 2.12 Simulator Status Module Chapter 2 _ MSI Agent 2.4 System Topology... 2.1.1. Control Panel Scripts. Chapter 3 _ Installation Guide... 3.1 QNX Installation 3.1.1” QNXMSI Agent Insialation.. 3.1.2 _ Windows installation 32" External Utilies. 3.2.1 _ Sample Tools... 33° Practical Exercises... Figures Figure 1-1 Regions of the User Interface. Figure 1-2 Status Sidebar Module Figure 1-3 Simulator Control Module... on Figure 1-4 Simulator Control Madule ~ Choose Airralt Configuration Clicked. Figure 1-5 Simulator Control Module - Power Up Simulator Clicked... Figure 1-6 Simulator Modules Control Module Figure 1-7 Shortcut Page Module Figure 1-8 Simulator Status Modul Figure 2-1 MSI Agent Scripts Figure 2-2 Script Execution Process... Figure 2-3 Control Panel Scripts. Displaying a Failure.. Training Handout ‘Aec Chapter 1 Control Panel Architectural Design 1.1 Rationale The Ascent Control Panel allows controlling an Ascent FFS,EFT or FTD simulator. It communicates through a network of peer-to-peer agents which can execute remote shell scripts on computers. The Control Panel is a modular system which configures itself through a series of configuration script files. These scripts describe the layout, behavior and functions of the control panel. The control panel communicates using a separate software tool called MSI Agent. ntrol Panel talks to the MSI Agent network using Shell Soripis, these script files describe the not only the behavior of the control panel but are shell scripts used to send to execute commands on remote pc's via the agent network. ‘The main functions of the Control Panel are: Selection of Aircraft Configurations. ~ Simulator Start and Stop Routines. — Monitor the status of the hardware components of the simulator. — Monitor the status of simulator software modules. = Control and access test utility software. — Remote control of simulator computers. ~ ‘Access simulation program without the need to restart software. - NOSREDS 1.2 User Interface 1.2.1 Overview The user interface of the Ascent Control Panel is modular, and its content is managed through a master configuration script. This configuration script indicates to the Control Panel which configuration scripts to load to build the user interface. These configuration scripts contain link to shell scripts to execute through the Agent Network. These soripts are configured specific to each simulator MSI manufacture and should need no further alteration by users. 1.2.2 Main User Interface illustrates the control panel when loaded with an empty master configuration script. The user interface is divided into three sections: The Header, containing the Simulator Name and the Company Name/Logo; ‘The Status Sidebar, containing the current overall status of the simulator;* Training Handout Mec ‘The Control Area, containing control and monitoring modules. Control Area ‘Sais sidebar diseazs Figure 1-1 Regions of the User Interfacee Training Handout 1.2.3 Status Sidebar Module The Status Sidebar is a necessary module which polls the different software and hardware modules of a simulator configuration. The sidebar is divided into three sections: Statistics, System Status and Faults Summary. The Statistics box indicates the uptime and total uptime of the simulator, as well as the last time the system was started. The statistics cannot be configured by the user; they are simply there to indicate that the system is running. ‘The System Status box indicates the overall status of the system. This box contains two indicators, one for the software components of the system, and one for the hardware components of the system. These indicators change colors based on the status of the simulator. Red: A fault is present which will prevent the simulator from operating; Yellow: A fault is present due to some other another fault; Green: No faults are present; the system is fully working; Grey: The status is unknown; the simulator might be powered down. The Fault Summary box indicates any error which alters the status of the indicators of the System Status box. A symbol will indicate if the fault is caused by a computer not being powered on (System not responding) or by a module explicitly returning an error code (System error returned). Figure 1-2 Status Sidebar ModuleTraining Handout 1.2.4 Simulator Control Module Part of the Control Area, this module allows the user to: 1. Select aircraft configuration 2. Start and shutdown the entire simulator under this configuration. This module is composed of one script (containing the configuration of the module) as well as two scripts per aircraft configuration: one containing the start sequence of that particular aircraft configuration, and one containing the stop sequence of that configuration. ‘The module features three areas, of which one is optional: 1. Aircraft Configuration - Allows changing the aircraft configuration controlled by the Ascent Control Panel 2. Simulator Control - Allows stavting/stopping the simulator. 3. Simulation Model Remote Window (Optional) - Allows connecting to the simulation model software. Figure 1-3 Simulator Control Module Aircraft Configurations Many aircraft types may be selected via the Aircraft configurations selection. This selection is also used not just for different aircraft types but is also used for different software loads. SeeTraining Handout Pergcer ne RARRRORAR pvnnonove ll Figure 1-4 Simulator Control Module - Choose Aircraft Configuration Clicked 1.2.5 Software Loads ‘The most typical variations of software loads in use for a specific aircraft types are: 1. Development Load 2. Test Pilot Load 3. Training Load 1.2.6 Development Load The Development Load is used by Mechtronix to implement software updates without putting at risk the Training load. This gives the user the opportunity to test software updates with no risk to student or pilot training exercises. The development load is found under the following directories: H/ust/Ascent/common_data H/usr/Ascent/Aircarft Model name /exe 1.2.7 Test Pilot Load The Test Pilot Load is used by Mechtronix to implement software updates without putting at risk the Training or Development loads. This gives the user the opportunity to help develop software updates with no risk to student or pilot training exercises. The test pilot load may be identified as: Hi/usr/Ascenticommon_data_TestPilot Hilusr/Ascent/TestPilot/Aircarft Model name/exeM e Cc i Training Handout 1.2.8 Training Load The Training Load is current customer approved software load. This software load will generally be the software load approved by the National Approval Authority. The Development load will be transferred to this load once the customer approves any updates in that configuration. The training load will be identified and located as follows: Hfusr/Ascent/common_data_Training H:Just/Ascent/Training/Aircarft Model name/exe In all of the above examples, with the exception of the Development load, the use of the Aircraft Model name may sometimes be omitted from the Training and Test pilot load directory structures. As this can vary users should acquaint themselves with simulator directory structures 1.2.9 Simulator Start/ Stop Actions The Simulator Power On and Power Off options allows the user to automatically start or stop (Power on or of) the simulator. The sequence is designed for the correct start and stop sequence. Some steps may be manual, in which case the operators is advised and should complete the required action to allow the sequence to continue. An example of the Power up sequence is shown in Figure 1-5- Training Handout 'ec _ Figure 1-5 Simulator Contro! Module - Power Up Simulator Clicked 1.2.10 Simulator Modules Control Module This optional module allows a user to individually control the components (or Modules) of the simulator. These can be elther Hardware or Software components. This module represents every component as a Control Box. Each Control Box has two functions: 1. Display the status of a component, 2. Allow starting/stopping it Each component can be linked to the components tested by the Status Sidebar, such that when an error occurs, the error message in the Faults Summary box of the Sidebar links to this module.Mechtrenix Teoma Seeeeents Figure 1-6 Simulator Modules Control Module* Training Handout ‘Aec x 1.2.11 Shortcut Page Module This module allows the user to launch applications on the local computer, or on remote computers. Also, as for other modules, multiple instances of this module can be created through the Master Configuration Script of the Ascent Control Panel. The module features a set of scripts, each script being represented as an icon, link and description. When the user clicks the icon/script or description, the script is launched on the destination machine. Most of these scripts will be launched on the local machine, since they launch utilities that the user wants to use. However, since the scripts are executed through the MSI Agent 2.0 network, they can run any Shell Script anywhere. Figure 1-7 Shortcut Page Module 1.2.12 Simulator Status Module Part of the Control Area, this module allows the user to see the status of the simulator in a text-based fashion. This optional module is displayed at the bottom of every page of the Control Area once activated. Users can resize the log to read it, or shrink it to hide it. The content of the log is maintained in a file, which is restored when the Control Panel is loaded, Thus, the content of the log is never cleared, and errors can be traced,M e Cc a Training Handout Figure 1-8 Simulator Status Module, Displaying a Failure Chapter 2. MSI Agent 2.1 System Topology Figure 2-1 shows an example layout of computer peer to peer communications for a typical MSI FFS or FNPT device.Training Handout ‘Aec Figure 2-1 MSI Agent Scripts MSI Agent Scripts are wrappers around shell scripts. Three kinds of scripts exist command scripts, batch scripts and link scripts. Even though different, every kind of script has the same goal: execute command(s) on a local/remote machine and obtain the result of the execution of that command. The script execution process is depicted in Figure 2-2 command Execution Response siaptancnper Figure 2-2 Script Execution ProcessM e Cc 5 Training Handout The Control Panel sends out commands to the remote pc and awaits a response. The sequence is determined by the script files and is organised on a hierarchy basis The commands used may be basedon Windows batch commands or QNX Ksh shell commands. 2.1.1 Control Panel Scripts Figure 2-3 below is an example of how the various scripts link to each other. These scripts in general should not require further alteration by the customer. However for some modules (Shortcut Links) it can be useful for the customer to create new links should they so desire. Details Q ‘Ascent Control Panel — Q ‘Stats Sidebar Configuration Seript (Per Areratt Configuration Status) Macro Seite) (Contains commands reusable ‘among the oierent sce) ‘Control Pane! Status Configuration Script (System Log) Slmulator Start Sesipt (Contains Acrft Configuration Dependent Startup Procedure} S| 4 ‘Master Coriguraton Sit Simultor Conirl Configuration Sit ‘Contains links to (Airrat Contgurstin Information, Ccantguraton Serpts) nk to Simulator St2/Stop Seep, ‘optional Simulaten Model Viewer (Telnet) ‘Simulator Stop Script (Contains Aera® Configuration Dependent ‘Shutdown Procedure) ‘Silat Modules Configuration Sit (Stat’Stop havidal components ofthe Simulator) | |, Shortcut Pate Configuration Serine) ld (Alou launching LocalRemote Applicator con the local machine, oF on remote machines) Figure 2-3 Control Panel ScriptsTraining Handout ‘ec Chapter 3. Installation Guide 3.1 QNX Installation Should re-installation of the control panel software be necessary the following procedure should be followed. 3.1.1 QNX MSI Agent Installation. Under QNX, an installation of the MS! Agent 2.0 is necessary for the Control Panel to function. 1. Retrieve the latest version of msiAgent2 along with the binary tools. 2. Copy the file MSIAgent2 to /ust/Ascent 3. Copy the file screen to /bin 4, Make sure the files are executable, type: a. chmod a+x /bin/screen b. chmod a+x /usr/Ascent/MSIAgent2 5. Edit /etc/rd.dirc.local (using ped or vi), add these lines (towards the end): @. echo Cleaning up dead screen sessions b. 1m tf /tmp/screens c. rm—r /tmp/u-screens d. echo Starting MSI Agent on port 4121 e. /ust/AscenlMSIAgent2 4121 & 6. Restart the computer 3.1.2 Windows Installation To install the Control Panel under Windows proceed as follows: 1. Retrieve the latest version of msiAgent2 and Control Panel along with the binary tools. 2. The MSI Agent 2.0 files normally go under c:\Ascent\MSIAgent2 (this is not necessary, though) and are composed of: a. ClientAgentDotNet.exe b. AgentDLLDotNet.ail ¢. MSIAgentConfig.xm! d. Other utility files 3, The Control Panel files normally go under c:\Ascent\ControlPanel (this is not necessary, though) and are composed of: a. ControlPanel.exe' Training Handout Mec b. AgentDLLDotNet.dll ¢. Contro!PanelConfiguration.xml d. Script Files 4. On every computer (including the development computer), copy an installation of the MSI Agent 2.0 under c:\Ascent\MSIAgent2, that is the three essential files enumerated above (point 2). Once all three files are copied, create a shortcut to ClientAgentDotNet.exe under Start Menu\Startup. 5. On the Development Computer, copy an installation of the Control Panel under c:\Ascent\ControlPanel, that is the three essential files enumerated above (point 3) along with the appropriate script files. Once all the files are copied, create a shortcut to ControlPanel.exe under Start Menu\Startup. 6. On the Development Computer, copy the additional utility files (WaitForBoot.bat, BringToFront.exe, MessageBox.exe, etc...) to c:\AscentiMSIAgent2, 3.2 External Utilities The Ascent Simulator Control Panel has no control/power over any device/software. lis power is derived from scripts executed through the MSI Agent 2.0 network. As such, the possibilities offered by the Control Panel can be extended greatly through external tools. Such tools can talk to hardware, to computers, to the Operating System, etc. 3.2.1 Sample Tools 3.2.4.4 Ping Ping allows a machine to test if another machine is currently connected to the network, This test also allows determining if an operating system is started, since the IP address of a network card is assigned by the operating system. Under Windows (cmd.exe), ping does not return any useful error code. Therefore, it must be combined with the find command to be useful to the Control Panel. A sample ping command would be: ping —n 1 -w 300 192.168.1.1 | find “TTL” Where the (n 1) parameter indicates to test the connection only once, the (w) parameter indicates to wait a maximum of 300ms to determine the status. The pipe (|) indicate that the output of the ping command will be fed to the find command, and that find will return 0 if the word TTL is found, and 255 if not found. Under Unix, ping returns 0 or 255 on successful or unsuccessful connection test. Therefore, it is not necessary to add the pipe find to the ping command if testing from a Unix machine. 3.2.1.2 Tasklist Tasklist is a Windows command allowing listing every process currently executing.* Training Handout ‘Aec This is useful to determine if a process is currently running on a given machine. Using the same pipe trick as for the Windows ping command, it is possible to determine if a given process is running: tasklist | find /I “ios-x d.exe” Where the (/) parameter indicates that find should be case-insensitive (ignore letter capitalization). Find will return 0 if the entry is found in the list provided by tasklist or 255 if not found. 3.21.3 Ps Ps is a QNX/UNIX command allowing listing every process currently executing. Using a similar trick as in the Windows Tasklist pipe find case, it is possible to determine if a process is running ps -A | grep “B737-800-rrs" Where the (A) parameter indicates to list every process, and the grep command to find a certain entry in the list provided by ps. 3.21.4 Screen Screen is a GNU/UNIX command, which allows executing another command within a virtual terminal screen. Screen is quite simple to operate. The syntax is: screen ~dms SoreenName Command CommandParameters The “-dms ScreenName"” parameter indicate to start the command in daemon mode (service mode, for Windows users), with a given name. If this parameter is not passed, screen will start the application in a virtual screen and connect to the screen directly. Connecting to a virtual screen is done by typin screen -r ScreenName Disconnecting from a virtual screen is done by typing successively: Control-A Control-DMec ‘ Training Handout 3.3 Practical Exercises sen Exercise 1 Start the control panel on the Dev PC Navigate around all panel tabs and famiurise with contents Locate the Maintenace manual Access IOS PC desktop remotely Locate the control panel script files on the dev pc.Mechtrenix Ascent FFS IlOS ModuleM e Cc | Training Handout Instructors Operating Station Module Contents Chapter 1 Non-Simulated Area. 14 108 Tower... 2 Hardware Architecture. 3 Block Schematic 4 Instructor Actions. 5 Software Architecture... 1.5.1 10S Manual. 6 7 8 9 Drive Mapping 108 Screens. IOS Options File Maintenance Faciltie.. 10 108 Screen Troubleshooting 111 108 Touch Screen Troubleshooting, Chapter 2 IOS Procedures. 7 2.1 10S User Manual... 1 Lasson Plans. aad 2.1.2 Lesson Plan operation.. 2.1.3 Lesson Plan Creation 214 215 Failure of a Nav Station. (5 Preselct a Malfunction .. 2118 Save a Gate/TaxiHold Position... Chapter 3 10S Practical Lesson 1 8.1 10S Practical 1 Figures Figure 1-1 Overview of the Non-Simulated Area, Figure 1-2 10S Tower... Figure 1-3 Example of Cat 8 Unit Front Figure 1-4 Example of Cat 5 Unit Rear... Figure 1-5 Example of How Cat 5 extender Connection... Figure 1-6 Example of an IOS Options file content. Page 2Training Handout ‘Aec Chapter 1 Non-Simulated Area The Non-Simulated Area is the area of the cab normally occupied by instructors_and observers during simulation sessions and contains the Instructor Operating Station (|OS"). Error! Reference source not found. illustrates its layout. The Non-Simulated Area contains the following equipment: * 10S Tower The IOS Tower, described further in section 1.1, contains the equipment with which the instructor normally interacts during a simulation session, {Details of this interaction are provided in the User Manual.) The IOS Tower is mounted on rails and can be repositioned to suit the personal preferences of the instructor. * Instructor's Seat The instructor's seat is mounted on rails and can be repositioned and rotated to suit the instructor. * Observer's Seat ‘The observer's seat can also be repositioned along rails and rotated. © Thermostat A wall-mounted temperature control unit allows regulation of the ambient air temperature in the cab interior. ‘© Ambient Lighting Dimmer Switch A switch just inside the Cab Entrance Door regulates ambient lighting levels, * Miscellaneous Equipment The non-simulated area also contains miscellaneous equipment such as. the fire extinguisher, headset hooks, document rack, receptacles (for AC power and data connections), anti-skid floor covering, area speaker (on Tear wall), video camera, etc. © Doors Trainer users use only the Cab Entrance Door. The other two doo intended exclusively for use by maintenance personnel. are Refer to the User Manual for details of the function and use of the various controls and displays located in the non-simulated area. {The Instructor Operating Station (IOS) consists of the |OS Tower and the Instructor's Seat. The door on the left side provides access to the Onboard Electrical Closet; that on the right side provides access to the Visual Display Area. Page 3MecRtrenix Tennateni Fite Alor Ugbt— Brergency Door —Second Observer's Cob Entrance Door Headset Hook View Port— Second Observer's sim pe! iota tac dole: Usk hone Ei Document Rock Observer's Headset Jacks Observer's— Oxygen Mask 6 Mabtenance— Incerphone Observer's Headset Hooks Fre Extinguisher " —_— AC Power - Outlet monet beara’ faut np Sout emtere Seat 18 Tore a Figure 1-1 Overview of the Non-Simulated Area Page 4‘Aec 11 * Training Handout X 10S Tower ‘An overview of a representative IOS Tower is provided in Figure 1-2. The two touchscreens on the right side of the IOS Tower provide the principal means by which the Instructor interacts with the trainer. On trainers equipped for simulated smoke, a stowage area for the instructor's oxygen mask is provided below the touchscreens. (This space is normally blocked off except on trainers which use simulated smoke.) The left side of the IOS Tower contains various panels. (Refer to the User Manual for details of these panels.) The jacks into which the Instructor plugs his communications equipment (headset, microphone, etc.) are mounted in a small panel on the side of the IOS Tower to the instructor's left (not visible in Figure 1-2 Figure 1-2 10S Tower Page 5Mec 1.2 7 Training Handout X Hardware Architecture The 10S Tower is situated on board the FFS Cockpit but the computer which controls the IOS system is located in the MSI Computer Cabinet ( MSICC). This is generally in a dedicated computer room located some distance away. Connectioni between the IOS PG and computer can vary dependent on the age of the trainer but is generally achieved via a Cat 5 Extender unit. This unit provides an easy way to transfer video , usb and mouse connections over a long distance. There can be a Cat 5 Transmitter located in the MSI CC and a second receiver unit located in the base of the IOS tower. Figure 1-3 Example of Cat 5 Unit Front 1.3 Figure 1-4 Example of Cat 5 Unit Rear Block Schematic Figure 1-5 is an example of how Cat 5 extenders can be connected to extend USB, Video, RS232 and audio connections from a PC. It also depicts how local monitors and sound can also be connected. It is just an example lease refer to trainer tions. Page 6. ‘Aec x Computer Training Handout TS6/uTo Local Monitor 1 soosZesivd wo0scZesiva Local Monitor 2 Figure 1-5 Example of How Cat 5 extender Connections 1.4 Instructor Actions The simulator instructor during a training exercise will generally perform some or all of the following actions: + Aircraft Fuel and Weight Loading + Simulator positioning + Environmental control + Malfunction insertion + Traffic Insertion ‘The IOS provides pages of buttons which allow control of all of the functions a simulator instructor should require. Some or all of these features can be pre- recorded and inserted later as Lesson Plans. 1.5 Software Architecture Software for the IOS system is to be found at two separate locations Page 7M e Cc . Training Handout 1. The IOS PC contains the executable software for the IOS program. It is located at : = CAAscent\lOS_X The Simhost PC contains data files which configure the IOS to display specifics for any simulator configuration specified at build time. The 10S executable program is common to all MSI simulators. It is the configuration files which make each IOS unique. The configuration files are located at : * \usr\Ascent\common_datalios. » \usr\Ascent\modelname\exe\data\ios The OS runtime executable file is called: 108-X_d.exe 1.5.1 10S Manual For detailed instruction is on the facilities provided by the IOS refer to the User Manual provided as part of the simulator documentation package. 1.6 Drive Mapping In order for the IOS software to function correctly the IOS PC must have a “mapped” drive connection to the Sim Host PC. This drive mapping is always labled as Drive H . It is simply refered to as the H Drive. Without this connection the IOS program will start but will not function correctly. Generally itis not possible for the user to log in. This connection once configured should need no further adjustment. It is pre-configured by Mechtronix during build time. 1.7 10S Screens The IOS program displays on two screens. In fact theprogram is actually running two instances of itself and its output is to two separate screens. This provides flexibility for the user in that it is possible to display any combination of available screen on both monitors at the same time or independently. The number of screens available is configured in a user data file known as the IOS Options file. This file is located at the following location : H:/usr/Ascent/common_data/ios Its file name is actually —ios_options.cfg Page 8Mec 1.9 Training Handout 10S Options File Figure 1-6 is an example of the contents of the IOS options file. This file should need no furthert adjustments once pre-configured by Mechtronix. [0PTIONS} Host PORT SCREENS BORDER NORMAL_coLouR WARNING COLOUR —=2552550 ERROR_COLOUR = 25500 LEGACY_LOGIN. = false REC_AND_PLAYBAC! DEBRIEF true CNIA_NON_MODAL = true INFO_BAR true Figure 1-6 Example of an 10S Options file content Maintenance Facilities ‘A special maintenance section is provided for access to special features not normally reuired for daily instructor use. It is for maintenance personnel or for control by an instructor who is designated as administrator manager. The features in this section of the IOS may include some or all of the following: + Qualification Test Guide ( QTG) performance + Lesson plan preparation + Pre-Positioning recording + Special technician maintenance controls + Generics visual scene recording + OPC and usr management functions The maintenance section should be password protected so access is controlled, Page 9