Users Guide for the In House Test Platform - ASAS TN · PDF fileAirtel ATN Ltd (Ireland)...

MA-AFAS IN STRICT CONFIDENCE Contract No.G4RD-2000-00228Report No. 560/80174Issue 1.06

IN STRICT CONFIDENCE Page i

CONTRACT N° : G4RD-2000-00228

PROJECT N° : GRD1-1999-10516

ACRONYM : MA-AFAS

TITLE : THE MORE AUTONOMOUS - AIRCRAFT IN THE FUTUREAIR TRAFFIC MANAGEMENT SYSTEM

D68 - Users Guide for the In House TestPlatform

AUTHOR: BAE SYSTEMS

PROJECT CO-ORDINATOR : BAE SYSTEMS

PRINCIPAL CONTRACTORS :Airtel ATN Ltd (Ireland) QinetiQ (UK)ETG (Germany) EUROCONTROL (France)NLR (Netherlands)

ASSISTANT CONTRACTORS:AMS (Italy) DLR (Germany)ENAV (Italy) FRQ (Austria)Galileo Avionica (Italy) Indra Sistemas (Spain)NATS (UK) SCAA (Sweden)S-TT (Sweden) Skysoft (Portugal)SOFREAVIA (France) Stasys Limited (UK)Thales-ATM (France)

Report Number : 560/80174Project Reference number : MA-AFAS – Wp2.4-BAESYSTEMSDate of issue of this report : 29 May 2003Issue No: 1.06PROJECT START DATE : 1/3/2000 DURATION : 36 months

Project funded by the EuropeanCommunity under the ‘Competitive andSustainable Growth’ Programme (1998-2002)

This document is proprietary of the MA-AFAS consortium members listed on the frontpage of this document. The document is supplied on the express understanding that it isto be treated as confidential and may not be used or disclosed to others in whole or inpart for any purpose except as expressly authorised under the terms of CEC Contractnumber G4RD-2000-00228


IN STRICT CONFIDENCE Page iii

LIST OF EFFECTIVE PAGES AND CHANGE HISTORY

Insert latest changed pages. Destroy superseded pages

TOTAL NUMBER OF PAGES IN THIS PUBLICATION IS 59CONSISTING OF THE FOLLOWING

Page No. Date Issue DCR Page No. Date Issue DCR

All 1.06 -


IN STRICT CONFIDENCE Page iv

DISTRIBUTION LIST

This Document is distributed as below.

Additional copies held by unnamed recipients will not be updated.

Paper Copies Name Address

MASTER Library BAE SYSTEMS, Rochester

MA-AFAS Library Avionic Systems

ElectronicCopies

Name Address

European Commission EC, Brussels

MA-AFAS Consortium Members [email protected]

MA-AFAS Web Site

mailto:[email protected]


IN STRICT CONFIDENCE Page v

Contents1 SCOPE ...........................................................................................................................................1

1.1 Purpose ......................................................................................................................................11.2 System Overview .......................................................................................................................11.3 Document Overview ...................................................................................................................11.4 Applicability.................................................................................................................................1

2 REFERENCED DOCUMENTS.......................................................................................................2

3 OPERATOR ACTIONS ..................................................................................................................3

3.1 Switch On ...................................................................................................................................33.1.1 System Connections ......................................................................................................3

3.1.1.1 Desktop IHTP.................................................................................................................33.1.1.2 Laptop IHTP...................................................................................................................3

3.1.2 Logon Procedure............................................................................................................33.2 Use of a Desktop IHTP...............................................................................................................4

3.2.1 Invoking the Test Program and Initialisation..................................................................43.2.2 Available Functionality ...................................................................................................6

3.2.2.1 History ............................................................................................................................63.2.2.2 The MCDU .....................................................................................................................83.2.2.3 Display Control Panels...................................................................................................93.2.2.4 Aircraft Model ...............................................................................................................103.2.2.5 Automatic Flight Control System..................................................................................153.2.2.6 Comms Functions ........................................................................................................173.2.2.7 ACMSLog.....................................................................................................................213.2.2.8 CSV IN .........................................................................................................................223.2.2.9 Performance Monitor....................................................................................................243.2.2.10 Interface Status Monitor ...........................................................................................243.2.2.11 Typical Workspace ...................................................................................................25

3.2.3 Output Files..................................................................................................................263.2.3.1 History ..........................................................................................................................263.2.3.2 Warnings.txt .................................................................................................................263.2.3.3 Errors.txt.......................................................................................................................263.2.3.4 Advice.txt......................................................................................................................263.2.3.5 Dump File.....................................................................................................................27

3.2.4 Program Shutdown ......................................................................................................273.3 Use of a Laptop IHTP...............................................................................................................273.4 Switch Off .................................................................................................................................27

3.4.1 Logoff Procedure..........................................................................................................273.4.2 Power Down Sequence ...............................................................................................27

4 CUSTOMISATION OF THE IHTP ................................................................................................29

4.1 Ethernet Router Initialisation ....................................................................................................304.2 ARINC Router Initialisation.......................................................................................................314.3 COM Router Initialisation .........................................................................................................324.4 Physical Port Manager Initialisation .........................................................................................33

4.4.1 ARINC Channel Customisation....................................................................................344.4.2 Ethernet Channel Customisation .................................................................................344.4.3 RS232 Channel Customisation....................................................................................354.4.4 Discrete Channel Customisation..................................................................................35

4.5 Virtual Port Manager Initialisation ............................................................................................354.6 Scenario File Default Directory.................................................................................................364.7 Log File Defaults ......................................................................................................................364.8 Aircraft Model Initialisation .......................................................................................................374.9 Comms Initialisation .................................................................................................................39


IN STRICT CONFIDENCE Page vi

4.10 Data Transmission Rate .........................................................................................................404.11 Default Window Positioning ....................................................................................................41

5 SCENARIO FILES........................................................................................................................43

5.1 Special Cases ..........................................................................................................................465.1.1 SSM Bits ......................................................................................................................465.1.2 Data Update Flag .........................................................................................................47

6 PARTNER PACKAGES...............................................................................................................48

6.1 Communications Ground Router..............................................................................................486.2 Traffic Simulator .......................................................................................................................50

6.2.1 Synchronisation of the Traffic Simulator ......................................................................506.2.2 IHTP Configuration for Traffic Simulator ......................................................................516.2.3 Traffic Simulator Configuration ....................................................................................526.2.4 Running the IHTP When Connected to the Traffic Simulator ......................................52

6.3 AOC Ground Platform ..............................................................................................................526.3.1 Scenario Generation ....................................................................................................52

FiguresFigure 1 Initial IHTP Functions Dialog Box..........................................................................................4Figure 2 IHTP History Window (with example text).............................................................................6Figure 3 History Window .....................................................................................................................7Figure 4 Logging Pop-Up Window ......................................................................................................7Figure 5 MCDU Emulator Window ......................................................................................................8Figure 6 BAC1-11 Display Control Panel Window ..............................................................................9Figure 7 ATTAS Display Control Panel Window ...............................................................................10Figure 8 Model Control and Display Window ....................................................................................11Figure 9 Altitude ActiveX Display ......................................................................................................12Figure 10 Airspeed ActiveX Display ....................................................................................................12Figure 11 Artificial Horizon ActiveX Display ........................................................................................12Figure 12 Ownship Position Display....................................................................................................12Figure 13 Data Object Selection Dialogue Box ...................................................................................13Figure 14 Data Object Log Window ....................................................................................................13Figure 15 Emulator Control Panel .......................................................................................................14Figure 16 SBAS/GBAS Sensor Status Word GUI...............................................................................15Figure 17 Autopilot Window.................................................................................................................16Figure 18 IHTP ATTAS Autopilot GUI .................................................................................................17Figure 19 METAR GUI ........................................................................................................................18Figure 20 ATIS GUI .............................................................................................................................19Figure 21 RVR GUI .............................................................................................................................20Figure 22 SIGMET GUI .......................................................................................................................20Figure 23 Message Activation Panel...................................................................................................21Figure 24 Process Activation Panel ....................................................................................................21Figure 25 Example of ACMS Output ...................................................................................................22Figure 26 ACMS Operator Button .......................................................................................................22Figure 27 IHTP CSV Injection Window ...............................................................................................22Figure 28 Old version of the CSV Injector...........................................................................................24Figure 29 Performance Monitor...........................................................................................................24Figure 30 Interface Status Monitor ......................................................................................................25Figure 31 Typical Workspace..............................................................................................................25Figure 32 Initialisation File Selection Window.....................................................................................29Figure 33 IHTP Initialisation - Ethernet Router....................................................................................30Figure 34 IHTP Initialisation - ARINC Router ......................................................................................32Figure 35 IHTP Initialisation - COM Router.........................................................................................33Figure 36 IHTP Initialisation - Physical Port Manager.........................................................................33Figure 37 IHTP Initialisation - ARINC Link Speed...............................................................................34


IN STRICT CONFIDENCE Page vii

Figure 38 Ethernet Channel Customisation ........................................................................................34Figure 39 RS232 Configuration Parameters .......................................................................................35Figure 40 IHTP Initialisation - Virtual Port Manager ............................................................................36Figure 41 IHTP Initialisation - Scenario File Default Directory ............................................................36Figure 42 IHTP Initialisation - Log File Defaults ..................................................................................37Figure 43 IHTP Initialisation - Aircraft Model.......................................................................................37Figure 44 COM Initialisation Files Path Entry......................................................................................39Figure 45 Initialisation Panel for ASE1 Comms Link...........................................................................39Figure 46 Data Transmission Rate Panel (Example)..........................................................................41Figure 47 Window Positioning Panel...................................................................................................41Figure 48 Example CSV File ...............................................................................................................43Figure 49 Comms Interconnections in the Test Environment .............................................................48Figure 50 Example cfgB.sh File...........................................................................................................49Figure 51 Example start_cfgB_R2.sh File...........................................................................................49Figure 52 Traffic Simulator Interface with IHTP ..................................................................................51

TablesTable 1. IHTP Menu Selections...........................................................................................................5Table 2. Definition of History Parameters ...........................................................................................7Table 3. Standard Configuration Files...............................................................................................29Table 4. Standard Ports Definition ....................................................................................................31Table 5. ARINC Channel Defaults ....................................................................................................32Table 6. Aircraft Model Parameters ..................................................................................................38Table 7. Example Comms .ini File Data............................................................................................39Table 8. Example Comms Initialisation Data ....................................................................................40Table 9. Data Idents (Octal) ..............................................................................................................46Table 10. Equipment Idents ................................................................................................................46Table 11. SSM Bits..............................................................................................................................47


IN STRICT CONFIDENCE Page 1

1 SCOPE

1.1 Purpose

This document provides guidance to users of the In House Test Platform (IHTP) software package. Ithas been designed and developed by the MA-AFAS consortium, lead by BAE SYSTEMS, for use inthe testing and supporting of trials equipment built to validate the concepts explored by theprogramme.

1.2 System Overview

The hardware that supports the MA-AFAS programme comprises an Avionics Rig, a Multi-functionControl and Display Unit (MCDU) and Navigation Display (ND). The Avionics Rig is a VME chassiscontaining two PowerPC single board computers, called the Flight Management Unit (FMU) and theCommunications Management Unit (CMU), an ARINC429 interface card, an RS232/RS422 I/Omodule and a 9.1 Gbyte Hard Disk Drive (HDD). Integral to the FMU is a graphics adapter and SCSIcontroller (for the hard drive), whilst the CMU houses a 28VDC discrete I/O module.

The IHTP has been designed to support testing of the Avionics Rig prior to delivery. It will also providesupport during the development and trials of the Avionics Rig. Because of the wide nature of the IHTPusage, the system is split into two distinct pieces; the software suite that provides the test andstimulation functionality and the physical platform that is used to run the software and provide anoperator interface.

The IHTP software is a modular suite of software functionality that has been designed to run onvirtually any Windows NT computer system. The more capable the computer, the more functionalitythat is simultaneously available. Each function in the suite can be individually configured either by aninitialisation file or by the user.

For the hardware, four custom built tower PC’s have been commissioned by BAE SYSTEMS forbench use whilst the five MA-AFAS laptops will be used to support the Avionics Rig when fitted toaircraft and simulators. The software is capable of running on any PC that uses the WindowsNToperating environment.

1.3 Document Overview

This document sets out to describe how to use the IHTP functionality in its various implementations.This covers the actions required to initialise the computer system and invoke the IHTP software andthen each of the available functions is described from an operators point of view. Note that thisdocument does not attempt to identify what level of functionality will be available for a given hardwareset-up.

1.4 Applicability

This document will be updated to reflect the functionally availlable in the latest release of IHTPsoftware. The software release number will be used as the issue number of the document thatappears in the top right hand corner of each page. The corresponding release information can beobtained from the software by selecting the Help:IHTP Menu Item of the IHTP Workspace Window(shown in Fig 25).

This document describes the functionality available in Release 6.00 of the IHTP software.



2 REFERENCED DOCUMENTSARINC 429 ARINC Characteristic 429Pt1-15, Mark 33 Digital Information Transfer System

(DITS), Part 1, Functional Description, Electrical Interface, Label Assignmentsand Word Formats, Dated: September 1, 1995.

560/80175 Installation Manual for the In House Test Platform

D24 Interface Control Specification, 560/80386, Issue 1

D30 Specification for the In House Test Platform, Issue 1.0, Dated: 29 May 2003.

D41 Installation Guide for the Avionics Rig, 560/78718, Issue 1, Date: 29 May 2003,Issued by BAE Systems.

D42 Users Guide for the MA-AFAS Avionics Rig, 560/80240, Issue 1, Issued byBAE Systems.

D54 HMI Requirements Spacification, issued by NLR.

D63 AGP User Manual, Issue 1.0, Date 6 February 2003, issued by Skysoft.



3 OPERATOR ACTIONS

3.1 Switch On

3.1.1 System Connections

3.1.1.1 Desktop IHTP

The Desktop IHTP comprises a DELL Optiplex GX240 Personal Computer (PC), complete withmouse, keyboard, soundcard and bespoke ARINC429/28 VDC discrete driver card, and a DELLTrinitron 21” monitor. This equipment may be operated standalone by connecting the mouse.Keyboard and monitor to the rear of the base unit and the mains supply to the computer base unit andmonitor.

The IHTP software was developed for a desktop system with a 21” monitor running at a resolution of1600 x 1200 pixels. It is recommended that this screen resolution be maintained to allow maximumuse of the display area, however, lower resolutions will work satisfactorily especially if only a few ofthe many possible sub-windows are opened in the workspace.

If the IHTP is to be used as part of a site network then an RJ45 connector is required to be connectedto the ethernet port located at the rear of the base unit. The IHTP is compatible with 10/100 BaseTsystems. Note that it is possible to connect both the IHTP and an Avionics Rig to a site network anduse the ethernet connection to stimulate the Rig using the IHTP. In this case, the advice of thenetwork administrator should be sought to ensure that the network will be able to cope with the extradata traffic. Similarly, although all IHTP (and rigs) have been assigned a unique BAE SYSTEMS IPaddress, in existing site networks these addresses may need to be replaced by site specific IPaddresses. This will entail modification of the .INI files used by the IHTP as defined in Section 4.

If the IHTP is to be used to stimulate/test an Avionics Rig using the ARINC429, RS232 and RS422datalinks, then the two systems must be connected using wiring harness as defined in document D24.

For systems requiring audio output, the optional sound system should be connected to the speakerconnection at the rear of the base unit. Details of this are also included in document 560/TBD.

3.1.1.2 Laptop IHTP

The Laptop computers supplied by BAE SYSTEMS comprise a DELL Latitude CPt with integralFloppy Disk drive or CD-ROM drive and PCMCIA LAN and Modem cards.

When a Laptop computer is used as an IHTP, the interface will be limited to the ethernet connectionand, possibly, the audio output. Screen resolution will be limited to 1024x768 with the BAE SYSTEMSlaptops.

The ethernet connection is achieved by connecting the LAN RJ45 connector to the PCMCIA to RJ45adapter supplied with the laptop. The adapter is then connected to the lower PCMCIA card on the lefthand side of the laptop. Note that the same restrictions apply to the Laptop regarding the use of thisequipment on a site network.

Audio output is by way of the 3.5mm jack socket on the right hand side of the laptop.

3.1.2 Logon Procedure

The IHTP uses Windows NT 4.0 as its operating system and when powered, requests an operatorname and password. The login screen also requires the input of a domain name.



If the IHTP is connected to the BAE SYSTEMS Rochester site network, operators can use their ownsite login by entering their usual username and password and selecting the ROCHESTER domainfrom the drop-down list on the login screen.

When not connected to a network, or the ethernet is only used to connect to an Avionics Rig, usersshould use the login name of “ihtpguest” with its associated password of “ihtpguest” and a domain ofthe computer identification number. For a desktop PC, this will be RC256x where x is 6 to 9depending upon the IHTP used. For a BAE SYSTEMS laptop, the unit number is of the form RC48yywhere yy is between 89 and 93. The specific id number is printed on a label affixed to each unit but isalso available in the pull-down menu in the Domain field of the login screen.

3.2 Use of a Desktop IHTP

3.2.1 Invoking the Test Program and Initialisation

As with many Windows programs, the IHTP software is invoked by using the Start button and

selecting Programs:IHTP. On the desktop IHTP’s there will additionally be an IHTP icon on thedesktop; double clicking this will also start the IHTP software.

The software configuration is controlled by the use of several configuration files stored in the“C:\IHTP\Configuration” folder. Normally, the configuration for a given site will not change very oftenand so the software has been designed to automatically detect and use the stored configuration.Section 4 of this document identifies the procedure required to modify the default configuration shouldthe need arise.

When the IHTP program is invoked, a display of available functions is generated as shown in Fig 1.The currently available options and a brief description of the functionality are given in Table 1.

Figure 1 Initial IHTP Functions Dialog Box



The initial IHTP Function Dialogue Box allows the operator the ability of selecting multiple windows fordisplay in a single operation. It also allows the definition of a default set of windows using the ‘tickboxes’. To set an item as a default, the item should be ‘double clicked’.

To select the default set of windows for display, the operator clicks ‘Default’ and then ‘OK’.

To select multiple windows, the operator uses the standard click, CTRL-click mechanism to highlightall the required windows. To open the selected windows, the operator clicks ‘Selected’ and ‘OK’.

The IHTP workspace is then invoked with all the required windows.

Acronym Program Functionality

History Opens a window that shows the data transfer history

History Filter Opens a window that shows the data logging/transfer history

The MCDU Starts the MCDU emulation

BAC11-1 DCP A Display Control Panel for use with the BAC1-11 configuration

BAC1-11 AFCS Starts the Autopilot emulation and GUI for the BAC1-11

Aircraft Model Starts the aircraft model and initiates the model GUI

Airspeed Dial ActiveX Airspeed Indicator Display

ArtificialHorizon ActiveX Artificial Horizon Display

Altitude Dial ActiveX Altitude Indicator Display

CSV IN Starts the CSV file injector

Performance Processor Performance Monitor

ATTAS DCP A Display Control Panel for use with the ATTAS configuration

ATTAS AFCS Starts the Autopilot emulation and GUI for the ATTAS

ACMSLog Opens a Log of Received ACMS Messages

Ownship GUI Displays the Current Ownship Position

GBAS Emulator Displays the GBAS Status Word Input

SBAS Emulator Displays the SBAS Status Word Input

IHTP_RVR AOC RVR data entry

IHTP_SIGMET AOC SIGMET data entry

IHTP_METAR AOC METAR data entry

IHTP_ATIS AOC ATIS data entry

XMLSnoop Provides a monitor for data transfers between the Avionics Rig and theTaxi and ATC Tool (TAT)

DOLog Provides a monitor for data objects in the IHTP

TEST CSV IN Starts the older version of the CSV file injector (only from within theIHTP)

Table 1. IHTP Menu Selections

After the IHTP is functional, further function windows may be opened by using the 'New' option in theFile pull-down menu (shortcut: Ctrl-N). This invokes the available functions list again and the operatorcan then choose a subsequent option. Note that it is possible to open some windows more than once;



e.g. the CSV injectors. Other windows, e.g. the aircraft model, will produce an error if an attempt ismade to open a second instance.

The default selection of sub-windows also stores the position of each window. To update the default,the ‘New’ dialogue box should be invoked (CTRL-N) and the Save Defaults button clicked.

3.2.2 Available Functionality

3.2.2.1 History

The History Window (Fig 2) allows the display of a log of the events in the system. Each entrycomprises five items:

Tx/Rx Flag Identifies the direction of data flow

Event Id Sequential count of all the new events

Event Count The number of times that the event has occurred

Event Time The time of occurrence of the lastest event

Event Name The (class) name of the event being logged.

Associated with this window are two options in the Connections pull down menu. These are

Start system time :- This starts the system sortie time running if not already active.

All Inputs :- This starts listening on all input ports. Any events incoming will be recorded

The prime usage of this window is to monitor the ports activity. When activated, it also enablesgeneration of a history file as detailed in 3.2.3.1.

Figure 2 IHTP History Window (with example text)

The History Window (Fig 3) allows the display of a log of the events in the system. The display isbased upon the standard Windows browser with the left hand pane displaying the message groupsand the right hand pane displaying the individual messages being transmitted/received.

In the Left Hand pane, the message grouping comprises the events group, which contains allmessages in the system, and the subdivisions of ARINC, Block, RS232 and Other. The ARINC groupis further divided into the various equipment types emulated by the IHTP and contains all themessages normally transmitted via the ARINC429 interface. The Block group contains messages thatcomprise a block of data rather than individual parametric data. Examples of Block data include theATTAS and RFS interfaces. The Other group contains Comms related messages.



Selecting one of the Blocks by left clicking will result in the display, in the Right Hand pane, of all themessages that comprise that Block. This is also true of the ARINC subdivision groupings.

Figure 3 History Window

Whenever a Block is selected in the Left Hand pane, message details are presented in the RightHand pane. Seven data items are available for each message as described in Table 2

Data Item Description

Name Name of the message

ID IHTP identifier of the message. This is usually the ARINC 429 labelof the message and is thus printed in Octal

SubID IHTP sub-identifier of the message. This is usually the ARINC 429equipment type of the source of the data. It is only used for ARINCmessages

LOG True/False flag to show if the message will be included in the Logfile

Frequency Transmission rate for the message

Activity Count of the number of messages transmitted/received

Last Time Time of last data transmission/reception

Table 2. Definition of History Parameters

3.2.2.1.1 Enabling/Disabling Data Logging

The History window can be used to modify whether or not the message data is included in the loggeddata (see 3.2.3.1). If a message or message group is right clicked, a pop-up menu will appear asshown in Fig 4.

Figure 4 Logging Pop-Up Window



This menu allows the setting of the TRUE/FALSE flag for individual messages or groups ofmessages. It also provides a mechanism for purging a data transmission from the system. I.e. to stopthe IHTP from transmitting the data again. When this is invoked, a progress indicator is provided toindicate when the task is complete. This can take several seconds to complete.

3.2.2.1.2 Data Transmission Frequency Modification

The History window can be used to modify the transmission rate of the message.

3.2.2.2 The MCDU

The MCDU window (Fig 4) provides a representation of a generic Multipurpose Control Display Unitas will be used for the MA-AFAS trials. It comprises a 24 character by 14 row alphanumeric display,alphanumeric keypad, dedicated control buttons and status lights. Each button on the displayprovides an input mechanism to the system when used in conjunction with the PC mouse.

The operation of the IHTP MCDU emulation mimics that of the MCDU in the avionics system. I.e. thedisplay and lamps are controlled by the FMU which generates the required display based uponoperator keypresses. The available functionality of the IHTP emulation is therefore defined indocument D54.

When invoked, the IHTP MCDU emulation will behave as the ’real’ equipment in as much that it willattempt to establish two way communication with a controller unit (in this case the FMU). Whilstwaiting for the controller to respond, the MCDU display will read SEARCHING FOR SYSTEMS’ asshown in Fig 5. Note that the emulation does not employ all of the time-out functionality of the realequipment thus facilitating its intended test and trials usage.

If the History window is available at this time, it will show the periodic attempts of the emulation inestablishing a connection.

Once connection has been established, the contents of the screen will be controlled by the FMU.

Figure 5 MCDU Emulator Window



3.2.2.3 Display Control Panels

There are two Display Control Panels (DCPs) available for use in the IHTP. One is for the BAC1-11configuration, and the other for the ATTAS configuration. The NLR configuration is expected to usethe same DCP as the BAC1-11 but via ethernet rather than RS232.

3.2.2.3.1 BAC1-11 Display Control Panel

This sub-window provides control of the Nav Display based upon the Display Control Panel fitted tothe BAC 1-11 aircraft. As with the MCDU, operator control of the buttons is provided by the mousewhich is used to position the cursor over the required button. Operating the left mouse button will’depress’ the selected button.

Note that the functionality of the IHTP emulation allows the setting of all permissible codes as definedby the DCP interface definition. This functionality may, therefore, differ slightly from that of the realDCP made by QinetiQ. Similarly, for ease of display generation, the rotary scale selector of the DCPhas been replaced by six buttons on the emulation.

Figure 6 BAC1-11 Display Control Panel Window

3.2.2.3.2 ATTAS Display Control Panel

The ATTAS DCP emulation is much simpler than that of the BAC1-11. It provides a simple simulationof two rotary switches; Display Scale/Range and Display Mode, as two sets of radio (i.e. one selectionat a time) buttons as shown in Fig 7.



Figure 7 ATTAS Display Control Panel Window

Since the data for the display control is output in the same data block as some of the parametricinformation (in the EXO block), the ATTAS DCP is not available for invocation unless the aircraftmodel is active. An attempt to invoke the ATTAS DCP before the Aircraft Model will result in an errormessage being generated.

3.2.2.4 Aircraft Model

The aircraft model uses a number of different windows for its control and display; a basic parameterdisplay, various aircraft instrument emulators and an AFCS control panel.

The basic display, shown as Fig 8, provides a view of the parameters used in the model. Because itgives a digital readout, in SI units, it is not particularly user friendly, but it provides a simplemechanism for starting and freezing the model (as an aid to diagnostics) and control of the modelusing the keyboard.



Figure 8 Model Control and Display Window

Keyboard controls are provided for stick forward/back (cursor control keys Up and Down), stickleft/right (cursor control keys Left and Right), Rudder left/right (Keypad ’0’ and ’.’) and thrustincrease/decrease (keypad ’+’ and ’-’).

3.2.2.4.1 User Interface

To provide a more user friendly view of the model outputs, a number of ActiveX aircraft instrumentshave been provided; Airspeed Indicator, Artificial Horizon and Altitude Indicator, along with anOwnship position readout. These are independently available from the IHTP Menu and are shown inFigs 9 to 12.



Figure 9 Altitude ActiveX Display Figure 10 Airspeed ActiveX Display

Figure 11 Artificial Horizon ActiveX Display

Figure 12 Ownship Position Display

Notes:



1 The aircraft model will continue to run with the Model Control and Display window minimisedproviding at least one of the ActiveX components is running and has the cursor focus to allow thekeyboard controls to work.

2 The ActiveX components utilise a high proportion of processor power and may causeproblems if used on the laptop version of IHTP. A known problem occurs if (unrealistic) high bankangles are used. For this reason, a limit of ±75 degrees has been set in the software for the bank andelevation angles.

3 Negative values for the Lat/Long data indicate South and West respectively.

3.2.2.4.2 Data Object Display

A further operator aid has been added to allow the display of any data item in the IHTP. This is theData Object Log (DOLog) that can be invoked from the New menu. Upon selection, the DOLogprovides a dialogue box to input the required data object. A pull down menu lists all the availableoptions as shown in Fig 13.

Figure 13 Data Object Selection Dialogue Box

Once selected, a blank window is generated. In order to refresh the data in the window, the refreshrate for the window needs to be specified. This is achieved by using the Timer pull down menu item toset the refresh rate at 10, 5 or 1Hz. The DO window is then updated with the required value (see Fig14 for an example)

Figure 14 Data Object Log Window

To view different data objects, the user can invoke a number of windows, each displaying a singledata item. As shown in Fig 14, each object is individually identified.



3.2.2.4.3 Emulator Controls

Associated with the aircraft model are the equipment emulators. These read the raw aircraft data fromthe model and convert the data into the format required for transmission to the Avionics Rig.

There is one emulator for each type of aircraft sensor (IRS, DADC, SBAS, etc), the ATTAS interfaceand the Traffic Simulator Interface. Each emulator has a control to enable or disable the Interface.Figure 11 shows the Emulator Control Panel, with the Traffic Simulator Interface (TSIM) buttonselected and the cursor positioned over the ATTAS button.

Figure 15 Emulator Control Panel

Associated with the SBAS and GBAS emulators are two GUIs that allow the modification of individualdata bits in the Sensor Status Word. This GUI is shown in Fig 16. Note that this version of the IHTPonly allows the modification of the Satellites tracked and SSM data items, the other tick boxes are‘greyed out’.



Figure 16 SBAS/GBAS Sensor Status Word GUI

3.2.2.5 Automatic Flight Control System

Associated with the aircraft model is the Automatic Flight Control System (Autopliot) emulation. Thisprovides a GUI that allows the aircraft model to be controlled by the avionics rig, IHTP autopilotsoftware or user inputs.

Two different autopilots are provided in the IHTP start-up menu; one for the BAC1-11 and another forthe ATTAS. The reason for this is that the operational modes are slightly different in the two aircraftand it was decided that a ’universal’ GUI would be confusing.

Note: The software will not permit autopilot emulation without the aircraft model running. Thus, themodel needs to be invoked before an autopilot. The software will also not permit both Autopilots to berun simultaneously.



3.2.2.5.1 BAC1-11 Autopilot

The BAC1-11 Autopilot emulation is shown in Fig 17 and is based upon the unit fitted to the BAC1-11.As with the actual unit, the emulator is split into 3 channels for Speed, Altitude and Heading control.The interconnection between the channels also emulates that of the real system. Controls also existto emulate the selection of Autopilot/Manual control and ILS modes of operation.

Figure 17 Autopilot Window

When invoked, with the aircraft model running, the AFCS emulation defaults to manual control. (It ispossible to run the Aircraft Model in manual mode without invoking this function if AFCS functionalityis not required). In order to invoke Autopilot control, the operator needs to select the A/P button withthe left mouse button. Note that since the emulation is for a single operator, dual button functionality(e.g. AP1/AP2 and PORT HDG/STBD HDG) is ’wired together’; selecting one button will automaticallyselect both buttons.

Under Autopilot control, flight parameters are changed by typing new values in the relevant window(normal mouse and keyboard functionality is available for this) and pressing the TAB key to enter thevalue. This functionality replaces the rotary dial of the AFCS. If not already selected, selecting theCHGE SPEED, CHGE LEVEL or PORT HDG/STBD HDG button will then inform the aircraft model touse the new data.

To select FMU control of the model, the operator should select the PROFL (for CAS and Altitudedemands) and/or LAT NAV (for Heading demand) buttons.

Note: ILS functionality is not included in this release of IHTP software, so the PRIME LOC and PRIMEGLIDE buttons have no effect other than illuminating their respective lamps.

3.2.2.5.2 ATTAS Autopilot

A second Autopilot Control Panel (Fig 15) is provided that emulates the functionality of the ATTASAFCS control panel. As with the BAC1-11 version, this control panel can only be invoked when themodel is running. Each of the 3 channels has 3 modes of operation controlled by the two buttonsbelow the data entry window:

Free flight: When neither button is selected, the actions of the model are controlled bythe operator using the keyboard.

FMS: When the ‘FMS x’ button is selected, then the Avionics rig controls theactions of the aircraft in this channel

AFCS: When the ‘AFCS x’ button is selected, the operator controls the channelusing the relevant data entry window.



Note: Only one button in a channel can be selected at one time.

Figure 18 IHTP ATTAS Autopilot GUI

As with the BAC1-11 control panel, the two autopilot channels are linked; selecting one will selectboth.

Other controls allow the operator to input data in different units when in AFCS mode.

3.2.2.6 Comms Functions

There are a number of functions associated with the Communications facilities of the Avionics Rig.Most of these require a Graphical User Interface (GUI) to allow the operator to input data fortransmission to the Avionics Rig. Data to populate the transmissions are held in separate initialisationfiles in the directory pointed to by the COMLinkManagerlist; COM Files Path value in the IHTP.ini file.

3.2.2.6.1 METAR

Data for the Meteorological Report (METAR) is entered using the METAR GUI shown in Fig 19.



Figure 19 METAR GUI

3.2.2.6.2 ATIS

Data for the Airport Traffic Information Service (ATIS) report is entered using the ATIS GUI shown inFig 20.



Figure 20 ATIS GUI

3.2.2.6.3 RVR

The (RVR) GUI shown in Fig 21 allows the input of data by the operator.



Figure 21 RVR GUI

3.2.2.6.4 SIGMET

Data for Significant Meteorological weather conditions is entered using the SIGMET GUI shown in Fig22.

Figure 22 SIGMET GUI



3.2.2.6.5 Message Transfer Controls

Each GUI panel has the same control buttons as shown in Fig 23. This section of the GUI providesthe following functionality:

Send Msg. Initiates the data transmission to the Avionics Rig

Periodic: Tick box that initiates the message transfer once every 10 seconds

Proc. Activ. Button that invokes the Process Activation sub panel

Exit: Closes the GUI.

Figure 23 Message Activation Panel

The Process Activation panel (shown in Fig 24) allows the operator to define the type of report to betransmitted to the Avionics Rig. As with all other Comms GUIs, the operator uses pull-down menus todefine what is required.

Figure 24 Process Activation Panel

3.2.2.7 ACMSLog

Invoking this option provides a window to record messages received from the Avionics rig in theAircraft Condition Monitoring System (ACMS) message.

The window invoked, shown as Fig 25, is a simple printout of any data received from the Avionics Rigand comprises a source identifier (ACMS_SAMPLE_DO), the time of data reception (5.994) and thereceived message data.



Figure 25 Example of ACMS Output

Associated with the window is a control button, shown in Fig 26, that allows control of the datareception. In order to capture the data, the button needs to be pressed.

Figure 26 ACMS Operator Button

When the operator closes the window, or shuts down the IHTP application, a standard Windowsdialog box appears asking if the data displayed in the window is to be saved or discarded.

3.2.2.8 CSV IN

This function provides the ability to stimulate the Avionics rig from test files that can be manuallygenerated or recorded by the IHTP as a history file. Invocation of the function using the File:New(CTRL-N) menu selection results in the display of a standard Windows pop-up file browser which canbe used to select a required scenario file. The default directory is as set in the .ini file.

On selection of a scenario file, the CSV Injection window, shown in Fig 27, is displayed.

Figure 27 IHTP CSV Injection Window



Two progress bars are provided by the window. One identifies how much of the file has been read into the IHTP, the other identifies how the transmission of data to the Avionics Rig is progressing. Oninvocation of the function, the data from the CSV is immediately read into the IHTP and the STARTbutton is Active. Upon pressing the START button, the Progress bar is activated, and the Pause andStop buttons are made Active.

Note: It is recommended, but not necessary, that the system finishes reading in the data prior to theSTART button operation. This will ensure that there are no timing or IHTP loading factors that mayinfluence the correct operation of the IHTP I/O. This is mainly necessary for large CSV files; e.g.those derived from the snoop facility of the IHTP during ‘real’ operation of the hardware.

Each event in a scenario file is associated with a time of occurrence. The CSV window is used todisplay the time that the next event in the list will occur ('Next Event 33.081 Sec’ in Fig 27) along withthe current Sortie time ('Current Time 31.753 Sec’ in Fig 27). This can be used to identify when anevent will occur. When the last event has been actioned, the Next value will remain frozen at the lastvalue read, the Pause and Stop buttons will be de-activated and the Start button will be activated. Thescenario can be re-run at this stage although data will continue to be output from the IHTP.

Note: Each event in the scenario file identifies one, or more, data changes; the rate of transmission ofthe data is fixed by the ICD (although section 4.10 details how to modify the transmission rates fortest purposes). Section 5 gives more details on the scenario files and their generation.

It is possible for more than one CSV Injector to be run simultaneously although the starting of each isunder manual control so tight correllation of the data is not possible. Note that this also allows thesame emulator (e.g. IRS) to be stimulated from two CSV’s simultaneously – this will cause problemsfor the Avionics Rig!!!

3.2.2.8.1 TEST CSV IN

To retain commonality with previous versions of the IHTP software, the older version of the CSVInjector has been retained. When invoked from the New menu, the window shown in Fig 25 isinvoked.

Left clicking on the centre of the window invokes a standard Windows file browser which can be usedto define which scenario file (identified by the.csv extension) is to be used as input. The defaultdirectory for the browser is C:\Program Files\IHTP\Scenario although this can be changed in theInitialisation process defined in Section 4. Selection of a scenario file closes the browser and returnsthe selected file data to the IHTP software for use. The current file name is displayed as depicted inFig 28.

Once a scenario file has completed, the operator can remove the window. Two choices are availableat this point; a) remove the window and continue the data transmissions using the last data read fromthe scenario file, or b) remove the window and the data transmission(s). This is controlled by the'Remove Message On Exit' tick-box. Note that the default is for the data transmission(s) to becontinued; this can cause large files to be generated if the 'dump file' option is enabled.

The other two tick boxes 'Emulate FMS' and 'Install Slave Port Handler' are for test purposes only andwill not be described here.



Figure 28 Old version of the CSV Injector

3.2.2.9 Performance Monitor

This display, depicted in Fig 29, is primarily a diagnostic aid for the IHTP software. As such, there isno user functionality that will be described here.

Figure 29 Performance Monitor

Information displayed in the four columns is Min time taken, Max time taken, Average time taken andProcess name.

3.2.2.10 Interface Status Monitor

The lower margin of the workspace window is used to display the Interface Status Monitor. This visualaid identifies the active interfaces of the IHTP. Fig 30 shows an example of the display with 25interfaces enabled. To determine what indicator refers to which interface, the cursor should be



positioned over the relevant symbol and a tool tip will be displayed naming the interface. Fig 30 showsthe IRS Receiver interface being highlighted in this way.

Figure 30 Interface Status Monitor

Enabled interfaces are depicted by circles, whilst active interfaces, i.e. those sending or receivingdata, are depicted using clock dials where the hands move whenever data is transferred. Note thatthe display is only updated when the cursor is positioned in the monitor area.

Each interface is represented by two dials, one for received data and one for transmitted data. Notethat under normal IHTP operation, only one dial will be used except for the MCDU.

3.2.2.11 Typical Workspace

Fig 31 illustrates a workspace that is used to stimulate the avionics rig using the IHTP aircraft modelto supply flight data and the BAC1-11 DCP, BAC1-11 MCP and MCDU emulation’s to provide control.Feedback is provided by the 3 aircraft instruments, the MCDU screen and the History window. Notethat the aircraft model control panel is running, but is minimised behind the AFCS control panel.

Figure 31 Typical Workspace



3.2.3 Output Files

When running, the IHTP outputs a number of files to aid post test diagnosis. When using these files todiagnose problems, care should be exercised to ensure that all the files were generated in the samerun: i.e. the creation date/times are identical.

3.2.3.1 History

The history file provides readout of all changed data output by and input to the IHTP during operationof the IHTP application. It is generated during the running of the IHTP application if the Historywindow has been selected for display (see 3.2.2.1). The format of the file is a Comma SeparatedVariable (.csv) text file with the same data fields as the Scenario files. This identical format allows theuse of history files as scenario files to allow re-runs of test flights on the ground. Note: The onlydifference between the two formats is the case of the data identifiers; lower case for recorded dataand upper case for playback data.

Each history file has a unique name with the format:

’History’ + date + time.csv

e.g. History09-07-02 16;00;15.csv. These files are normally stored in the directory ’C:\ProgramFiles\IHTP\Data Logs’ but this parameter is set in the IHTP.ini file and can be changed by the user(see section 4 for more details).

Note that this file only contains records where changes of data occur and does not contain a record ofevery data transmission to/from the IHTP. This is achieved by filtering the received data prior tosaving it.

3.2.3.2 Warnings.txt

This file will be generated each time the IHTP program is run. Unexpected events, e.g out of rangevalue, unexpected I/O disruption, overrun interrupt, will be recorded in this file which may be used toprovide diagnostic information to the IHTP development team in the event of a reported non-fatalerror.

Note that this file is not deleted by the application so its presence should be checked for after eachrun.

The file will be located in the same folder as the IHTP.exe file.

3.2.3.3 Errors.txt

This file will be generated if system errors are encountered - these are usually fatal. e.g. transmit anon-existent message, code errors. The file will be used to provide diagnostic information to the IHTPdevelopment team in case of a reported fatal error.

Note that this file is only generated, or replaced, if a problem occurs during an IHTP run. The file isnot deleted by the application so its presence should be checked for after each run.


3.2.3.4 Advice.txt

Advice.txt is a log of advisory messages detailing program operation. It will be the largest of the threeerror files and simply acts as a map of the functions used during an IHTP run.

The file is generated during each IHTP run, overwriting the previous version.




3.2.3.5 Dump File

The dump file provides a readout of all data output by and input to the IHTP during operation of theIHTP application. The format of the file is a Comma Separated Variable (.csv) text file with the samedata fields as the Scenario files. Dump file generation is enabled by Initialisation file selection.

Each dump file has a unique name with the format:

’Dump’ + date + time.csv

e.g. Dump09-07-02 16;00;15.csv. These files are normally stored in the directory ’C:\ProgramFiles\IHTP\Data Logs’ but this parameter is set in the IHTP.ini file and can be changed by the user(see section 4 for more details).

Note that this file contains all data transferred to/from the IHTP. As such, it is expected to becomequite large, especially if 50Hz data transmissions at being performed.

3.2.4 Program Shutdown

As with many Windows applications, the application as a whole is shut down by left clicking the closewindow icon (X) in the top right hand corner of the workspace window. Individual functions may alsobe closed down by the same mechanism for each window in the workspace, but this is not arequirement for normal shutdown.

Note that the filtering and saving processes for the History and dump files may cause the applicationto keep running after the windows have closed. The application will terminate when all data has beensaved.

3.3 Use of a Laptop IHTP

To date, no difference has been found in the operation of IHTP software when using a laptopcomputer except that it is not possible to exercise the ARINC429 interfaces. This, however, is aconfiguration issue and the available configuration files on a laptop will reflect the differences.

3.4 Switch Off

3.4.1 Logoff Procedure

The Logoff procedure to be employed is the same for the Desktop and Laptop computers. It involvesthe selection of :

Start: Shut Down…

and then the selection of the

Close all programs and log on as a different user?

option followed by OK. This will result in the Log-On screen being displayed once again, ready for thenext user.

3.4.2 Power Down Sequence

The power down sequence is slightly different for Laptop and Desktop. Both sequences are invokedby selecting



Start: Shut Down…

and then the

Shutdown Computer

option should be selected and OK pressed. The laptop will then power down automatically, but powerfor the desktop needs to be manually operated when the Dialog box appears stating that power canbe removed.



4 CUSTOMISATION OF THE IHTPUnder normal circumstances, the IHTP software will be initialised using data held in the IHTP.ini fileresident in the \Configuration directory. If this file is absent, then a Windows dialog box is generated,shown in Fig 32, that prompts the user for a startup file that identifies the current systemconfiguration. Several standard files will exist as defined in Table 2 that cover the normal rigconfigurations and one of these should be selected.

Figure 32 Initialisation File Selection Window

File Name Program Functionality

ATTAS Configuration for use when connected to the ATTAS simulator. Functionality islimited to the generation of alert tones and the emulation of the ground basedfacilities (AOC and ATC).

BAC1-11 Configuration for use when connected to the BAC1-11 aircraft or RTAVSsimulator. Functionality is limited to the generation of alert tones and theemulation of the ground based facilities (AOC and ATC).

NLR Configuration for use when connected to the NLR simulator. Functionality islimited to the emulation of the ground based facilities (AOC and ATC).

Test-ATTAS This configuration allows the testing of an Avionics Rig using the ATTASinterfaces. Full functionality is available using the F100 aircraft model. ATTASformatted data is transferred using the ethernet.

Test-BAC1-11 This configuration allows the testing of an Avionics Rig using the BAC1-11interfaces. Full functionality is available using the BAC1-11 aircraft model. Datais transferred using ARINC429, RS232 and RS422 interfaces

Test-NLR This configuration allows the testing of an Avionics Rig using the NLRinterfaces. Full functionality is available using the Boeing 747 aircraft model.NLR formatted data is transferred using the ethernet.

Table 3. Standard Configuration Files



Following the acceptance of the initialisation file, the Initialisation Pre-Initialise Check window will bedisplayed. This comprises several panels, as detailed below, which allow the modification of each ofthe initialisation parameters. It is possible to edit the .ini files directly; they are in plain TXT format, butuse of the initialisation panels is much easier.

On each panel are two tick boxes; Edit On Start and Save Now. Edit On Start is used to defer theentry of initialisation data until the interface is used. This can be useful if data, e.g. target information,is not known at the start of the sortie but will be known when the data is needed.

When changes are made to the initialisation data and they need to be made permanent, the SaveNow option should be selected. Without this selected, the data displayed is used for the currentsession but not recorded to the .ini file for future use.

Note that these buttons apply individually to each panel and should be ticked on all relevant panels.

4.1 Ethernet Router Initialisation

The CEthernetRouter panel allows the customisation of the port numbers that are associated with thevarious data blocks transmitted between the IHTP and the Avionics Rig. Fig 33 shows the initialdisplay.

Figure 33 IHTP Initialisation - Ethernet Router

The definition of the ports has been standardised as given in Table 3. The use of Ethernet (asopposed to ARINC429 or RS232) is defined by the Physical Port Manager detailed in section 4.4.

Interface Ethernet Port #

Inertial Reference System 50003

Attitude and Heading Reference System 50004

Air Data Computer 50005

Global Navigation Satellite System (GNSS) 50006

BAC1-11 Data Puddle 50006

SBAS 50007

GBAS 50008

VDL Mode 2 TBD (50101)

VDL Mode 4 TBD (50100)

Automatic Flight Control System (AFCS) Tx 50012



Interface Ethernet Port #

Experimental Flight Management SystemEFMS) Rx

50011

Mode Control Panel 50013

Engine Management System (EMS/EIU) 50014

Weight and Balance System TBD

MCDU Rx (Ethernet Server) 50000

MCDU Tx (Ethernet Client) 50001

MCDU Control Tx 50002

Display Control Panel 50015

Aircraft Conditioning Monitoring System Tx 50017

Aircraft Conditioning Monitoring System Rx 50016

Aircrew Warning System 50018

ATTAS (EXO, ASV and OLG) 5003

ATTAS Time and Position 5005

Position And Time (PAT) Time Sync 50020

Traffic Simulator 2040

Taxi and ATC Tool TBD

Alert TBD

RFS (NLR Flight Sim) TBD

Table 4. Standard Ports Definition

Note: Each data emulation has an input port and output port definition although in general, sensorswill only be output from the IHTP with the input definition being reserved for test purposes. TBD Portscan be set at any unique port number in the range 50100 to 50200.

4.2 ARINC Router Initialisation

As with the ethernet, the data output by the ARINC429 ports is also customisable. Each of thesensors defined in Table 4 can be configured onto any of the ARINC channels controlled by the IHTP.However, the Avionics Rigs and test harnesses are designed and built to the default identified in theTable and this data should not be altered without corresponding hardware alterations.



Figure 34 IHTP Initialisation - ARINC Router

IHTPChannel

Usage Speed

rx1 EFMS Low

rx2 MCDU Low

tx10 EMS/EIU Low

tx2 AHRS High

tx9 MCP Low

tx8 AFCS High

tx5 SBAS Low

tx4 GNSS/Data Puddle Low

tx3 ADC Low

tx6 GBAS Low

tx1 IRS High

tx12 MCDU Low

Table 5. ARINC Channel Defaults

Note that those sensors that are not identified in Table 4 can be set to a fixed value (Rx9 or Tx16) butthe channels are enabled/disabled using the Physical Port Manager.

4.3 COM Router Initialisation

The third type of serial data connection is the COM (RS232) port. The Desktop IHTP has 2 of these,predominantly for use by the DCP emulator (COM1) and the VDL4 interface (COM2). Note that whena Laptop is used as an IHTP, only one COM port is available and the operator needs to define whatthe single RS232 port is to be used for. It is not anticipated that the laptop will be required to emulatemore than one RS232 based equipment at any one time.

The CCOMPortMapper panel is used to configure these two ports to carry sensor data; those sensorsthat do not use a COM port should be set to port 0, the DCP Tx to 1 and the VDL4 Tx and Rx to 2.



Figure 35 IHTP Initialisation - COM Router

As with the Ethernet and ARINC interfaces, the ports are enabled using the Physical Port Manager.

4.4 Physical Port Manager Initialisation

The CPhysicalPortManager panel (Fig 36) allows the configuration of the interface hardware. Eachchannel is identified by a sensor name, either transmit or receive, which can be configured to beoutput using Ethernet (E; the port number is allocated in the CethernetRouter panel), ARINC429 (A;the channel number being allocated in the CARINCHardwareRouter panel), RS232 (R; the COM portnumber being allocated in the CCOMPortRouter panel) or Unconnected (U). Option D, for an outputof 28Vdc Discrete data, is also included but is currently not implemented.

Figure 36 IHTP Initialisation - Physical Port Manager

Each interface comprises a Transmit and a Receive port. Under normal circumstances, only one ofthe ports will be used. The exception is the MCDU where both ports are always used.

For interfaces where the IHTP transmits data to the Avionics Rig, the Tx port should be connected (E,A or R) and the Rx port left unconnected (U). In this case, the Rx port is used to ‘snoop’ realequipment to discover the characteristics of the data provided.

Note that the Autopilot also uses a bi-directional link but in this case the data from the IHTP(Autopilot) to the Avionics Rig is carried on the AFCS Tx port whilst the data from the Avionics Rig tothe IHTP (Autopilot) is carried on the EFMS Rx port. Thus the AFCS Rx and EFMS Tx ports shouldnormally be unconnected (U).



Associated with each port is a Named Config value that allows the customisation of the channels in anumber of different ways for the given configuration. When used, each predefined config valuecauses another configuration panel to be invoked to allow definition of the extra data items.

4.4.1 ARINC Channel Customisation

For ARINC429 channels, Named Config may take the values Default or FastArinc. This allows thesetting of two different speeds (Slow;11k bps or Fast; 100k bps) for the interface type using two newconfiguration panels; ArincDefault (shown in Fig 37) and ArincFastArinc.

Figure 37 IHTP Initialisation - ARINC Link Speed

4.4.2 Ethernet Channel Customisation

For the Ethernet channels, fourteen values of Named Config are defined: Default, OnDemand,CLIENT1, CLIENT2, SERVER1, SERVER2, SERVER3, SERVER4, Slave, CON1, CON2, CON3,CON4 and UDP. Each sub panel allows the definition of 4 parameters associated with the ethernettransmissions as shown in Fig 38.

Figure 38 Ethernet Channel Customisation

The four parameter are:

IP Address if Target: This allows the specification of the ethernet address of the target processoras a quad value in the standard ethernet ’dot’ notation. Note that the local loopback address(127.0.0.1) is not implemented in the IHTP software. If the target process is also housed on the IHTPhardware, then the specific address for the IHTP should be used. Similarly, if the address specified isinvalid or not connected, then the IHTP software will appear to ’hang’ until the normal ethernet



connection timeout occurs. In this instance, the warnings file will identify which interface is causing theproblem.

Use TCP IP: This allows the definition of the protocol used for the ethernet link. Only two areimplemented in the IHTP; TCP/IP (value = TRUE) and UDP (value = FALSE)

Connect On Demand: This option should only be selected TRUE for the MCDU control port. Allother ports should be FALSE.

Type of Link I:- IHTP System S:-Server C:-Client: Normally, this option should be set to I. When theIHTP is used to emulate the ATTAS, option S should be used (this will only be for ATTAS port types).Option C is only required as a test facility for the ATTAS configuration and should not normally beselected.

4.4.3 RS232 Channel Customisation

Two values of Named Config have been defined for the RS232 interfaces: Default and FastCOM. Foreach setup, 5 parameters can be defined as shown in Fig 39. These are:

Baud Rate: This should be set to one of the standard COM Baud rate values. For MA-AFAS, only9600 (BAC1-11 DCP and VDL4) and 19200 (Aquarius GNSS) are expected to be used.

Parity ?: TRUE if the data link uses parity, otherwise FALSE.

Even Parity ?: TRUE for even parity, FALSE for odd. Note that if Parity ? is set FALSE, then thisparameter is not used and can be set to either value..

No of Stop Bits: Allowable values are 0, 1 or 2. (1 for MA-AFAS)

No of Data Bits: Allowable values are 7 or 8. (7 for BAC1-11 DCP)

Figure 39 RS232 Configuration Parameters

4.4.4 Discrete Channel Customisation

This facility is not implemented in this release of software.

4.5 Virtual Port Manager Initialisation

The CVirtualPortManager panel (Fig 40) allows data to be transmitted with a slight timing offset tosimulate the non-coherent data transmissions from multiple, unconnected, sensors. The facility iscurrently not used and all values should be set to zero.



Figure 40 IHTP Initialisation - Virtual Port Manager

4.6 Scenario File Default Directory

The CReadSortieFileTask panel (Fig 41) allows customisation of the default directory for the scenariofiles. Normally, this is set to "C:\Program Files\IHTP\scenarios\" but users can define whatever path isrequired. Note that the trailing ’\’ is required.

Figure 41 IHTP Initialisation - Scenario File Default Directory

4.7 Log File Defaults

The CHistory panel (Fig 42) allows customisation of the default directory for the Log files generatedby the IHTP at runtime. Four parameters are initialised using this panel as follows:

History File Path: When the History window is invoked (See 3.2.2.1) log data generated is heldin the directory defined by this parameter. Normally, this is set to "C:\Program Files\IHTP\data logs\"but users can define whatever path is required. Note that the trailing ’\’ is required.

Generate Dump File: The user can enable the generation of the dumpfile using this parameter.TRUE or 1 will enable the output, FALSE or 0 will disable it.

Dump File Path:When the ’Generate Dump File’ parameter is set to TRUE, this parameter is used todefine the directory used to store the dumpfile. Normally, this is set to "C:\Program Files\IHTP\datalogs\" but users can define whatever path is required. Note that the dump file can potentially be hugeso this value should be chosen with care.



One Event per Line: This switch should normally be set to FALSE, but can be used to force theIHTP to store each recorded event on a separate line.

Figure 42 IHTP Initialisation - Log File Defaults

4.8 Aircraft Model Initialisation

The final panel is the Aircraft Model panel which is used to define the characteristic values that theIHTP model should use in its calculations. The panel is depicted in Fig 43, and the parameters thatmay be defined are given in Table 5 which also gives suitable default values for each of the 3 aircrafttypes used in the MA-AFAS trials.

Figure 43 IHTP Initialisation - Aircraft Model

Most of the values shown in Table 5 are self explanatory and will not be further elaborated. The lastthree items, however, do warrant further explanation:

’Initially Aircraft on ground’: This is effectively a weight on wheels signal. When set TRUE, the aircraftmodel will be inhibited from reducing the altitude at model start until the aircraft altitude has increased.The value should be set TRUE whenever the scenario starts with the aircraft on the ground.

’User is to specify start time of scenario’: This flag allows the user to specify the time at the start of thescenario (value = TRUE) or to set the scenario clock using the PC clock (value = FALSE). When setby the user, the initial time is entered in the last parameter: ’ Input start date and time of scenario’using the format shown in Table 5.

MA

-AF

AS

IN

ST

RIC

T C

ON

FID

EN

CE

Con

trac

t No.

G4R

D-2

000-

0022

8R

epor

t No.

56

0/80

174

Issu

e1.

06

IN S

TR

ICT

CO

NF

IDE

NC

EP

age

38

Para

met

erB

AC

1-11

Val

ueA

TT

AS

Val

ueN

LR

Val

ueA

ircr

aft T

ype

BA

C 1

-11

AT

TA

SN

LR

747

-400

Air

craf

t Mas

s w

ithou

t Fue

l (kg

)24

000

1570

018

0700

Air

craf

t Fue

l Mas

s (k

g)21

000

3500

1745

00A

ircr

aft F

uel B

urn

Rat

e (k

g/s)

0.75

0.38

3.0

Air

craf

t Win

g A

rea

(m^2

)93

.264

524.

9A

ircr

aft M

ax S

peed

(m

/s)

242

129

260.

8A

ircr

aft M

ax T

hrus

t (N

)91

800

6478

510

3096

0A

ircr

aft M

ax A

ltitu

de (

m)

1067

076

2012

800

Air

craf

t Ang

le o

f A

ttack

(ra

ds)

0.04

363

0.00

872

0.04

765

Air

craf

t Win

g A

spec

t Rat

io7.

87.

228.

0A

ircr

aft E

ffic

ienc

y Fa

ctor

0.78

0.85

0.86

Initi

al A

ltitu

de (

m)

260

Initi

al H

eadi

ng (

rads

)4.

5379

4.53

7856

0551

Win

dspe

ed (

m/s

)In

itia

l Air

spee

d (m

/s)

Init

ial A

ccel

erat

ion

(m/s

/s)

Initi

al T

hrus

t (N

)In

itia

l Pit

ch A

ngle

(ra

ds)

Init

ial R

oll A

ngle

(ra

ds)

Initi

al Y

aw A

ngle

(ra

ds)

Win

d D

irec

tion

(rad

s)In

itial

Lat

itude

(ra

ds)

0.91

164

0.91

3141

429

Initi

al L

ongi

tude

(ra

ds)

-0.0

0765

0.18

4240

446

Init

ial R

ate

of C

lim

b (m

/s)

Initi

ally

Air

craf

t on

grou

nd (

TR

UE

/FA

LS

E)

TR

UE

/FA

LS

EU

ser

is to

spe

cify

sta

rt ti

me

of s

cena

rio

(TR

UE

/FA

LS

E)

TR

UE

/FA

LS

EIn

put s

tart

dat

e an

d tim

e of

sce

nari

o (Y

YY

Y:M

M:D

D:h

h:m

m:s

s)20

02:0

8:13

:17:

07:0

0

Tab

le 6

. A

ircra

ft M

odel

Par

amet

ers



4.9 Comms Initialisation

Initialisation for the Comms facilities in the IHTP is achieved ina slightly different manner in as muchas the Comms initialisation panels are not included in with all the others. Instead, whan a Commsscenario file is invoked by the CSV Injector function, if initialisation files do not exist, or are not up todate, then initialisation panels are displayed for input of data.

The first panel that may pop up allows the user to identify where the COM ini files are located and isshown in Fig 44. The standard location is shown but the user is free to chose any path.

Figure 44 COM Initialisation Files Path Entry

The subsequent panel(s) that pop up allow the user to input the specific Comms parameters for eachcommunication link identified in the .ini file. For example, the data shown in Table 8 will give rise tothe initialisation panel shown in Fig 45.

Time ASE1 (666)5 c0 cc 03 e7 c07 c0 14 22 59 c0

Table 7. Example Comms .ini File Data

Note that the identifier at the head of column 2 (ASE1) is repeated in the title bar of the initialisationpanel.

Figure 45 Initialisation Panel for ASE1 Comms Link

Parameter Example Value

COM Type 0:-ASE 1:-BC 2:-GACS 0

The local network address 127.0.0.1:7790

The remote server network address 10.4.111.156:6770



Parameter Example Value

ASE The CM PeerIDGround address 41 42 43 44 45 46 47 48

ASE The CPDLC PeerIDGround address 41 42 43 44 45 46 47 48

ASE The Ground NSAP address 47 00 07 32 59 00 29 03 99 01

ASE The Air NSAP address 47 00 07 32 59 00 29 03 21 01

ASE The CM TSEL Ground address 66 66

ASE The CPDLC TSEL Ground address 66 66

ASE The CPDLC TSEL Air address 55 55

ASE The CM Logon Response 00 00

The Version Context Eg ACN_5_V1 = 1 1

The Peer Aircraft ID 41 46 44

CM Enabled FALSE

GStation GACS Address Name

GACS Message ID LocalForm 0

GACS Socket Address 10.4.101.49:8023

GACS Asynch FALSE

GACS Max User Data 0

GACS Optional Message Type FALSE

GACS Message Form 0

GACS Message ID 0

GACS Recipient Called Address Name Id

GACS Called Address Name Mask 0

GACS Called Address Name SysIDLow 0

GACS Called Address Name SysIDHigh 0

GACS RER 0

GACS Class 0

GACS Priority 0

Table 8. Example Comms Initialisation Data

4.10 Data Transmission Rate

An addition to the IHTP program is the ability to modify the transmission frequency of data from theIHTP to the Avionics Rig. Under normal circumstances, this is fixed in the software by therequirements of the ICD. However, for test purposes, it has been found necessary to modify some ofthe transmission frequencies to enable specific fault finding.

To modify transmission frequencies, the user must manually edit the .ini file associated with theprogram invocation. To do this, the relevant .ini file should be edited, using Notepad or Wordpad, toadd extra lines. These lines are or the form:

Variable_name,Frequency (Integer Hz),frequency,



e.g. IRS Groundspeed,Frequency (Integer Hz),100,

this sets the transmission frequency for the IRS Groundspeed parameter to 100Hz

The underlined text ‘Frequency (Integer Hz)’ is a necessary formatting phrase and should beduplicated exactly, including the spaces.

Variable names are those found in the dump file when enabled, or in the software.

When the user has included a variable in the .ini file, the IHTP includes the data in a configurationpanel as shown in Fig 46. This allows the modification of the parameter at run initialisation timewithout the need to re-edit the .ini file.

To remove the modified frequency (and revert to the ICD defined value) the user needs to remove theextra line(s) in the .ini file.

Figure 46 Data Transmission Rate Panel (Example)

4.11 Default Window Positioning

The default windows position panel is shown in Fig 47. This allows modification of the position of eachwindow on the screen. However, it is anticipated that modification of the data in this panel will beundertaken by use of the ‘Save Defaults’ option on the ‘New’ window.

Figure 47 Window Positioning Panel



Positioning data in this window is in the form of XY co-ordinates for the position and size of thewindow. The default setting for an unused window would be "X100 Y200 Ht0 Wd0". The defaultsetting for a used window is: "X100 Y200 Ht200 Wd200"

To identify a window as a default option, the DefaultsOn parameter should be set to 1.



5 SCENARIO FILESThe format of the scenario files, comma separated variable (CSV), has been chosen to allow the easygeneration of the scenarios using a standard spreadsheet application (such as Microsoft’s Excel).Within the spreadsheet, time is entered in the first column (column A in Excel) and parameter valuesare entered in subsequent columns. The top cell in each column of data is reserved for the parametername and identification data as shown in Fig 48.

The parameter name is chosen to identify the data item and its source in a human readable form. Theactual text is not required to be a standard format and can be operator chosen. At the end of the textis the Parameter Identifier, enclosed in round brackets. This identifier comprises two octal numbers; adata ident and an equipment ident separated by a slash (’/’) character. Many of the idents are thosefound in ARINC429 for data labels and equipment idents. Others have been generated for the MA-AFAS programme; complete lists of data and equipment idents are given in Tables 9 and 10.

One exception to the ’two parameter’ rule is Comms. Here, no equipment Ident is required when adata ident of 666 is used.

Time

Data Puddle Present Position - Latitude (310/14)

Data Puddle Present Position - Longitude(311/14)

Data Puddle Groundspeed(312/14)

Data Puddle Track Angle True(313/14)

10 45 15 350 12511 45.001 15.001 352 125.0112 45.002 15.002 354 125.0213 45.003 15.003 356 125.0314 45.004 15.004 358 125.0415 45.005 15.005 360 125.0516 45.006 15.006 362 125.0617 45.007 15.007 364 125.0718 45.008 15.008 366 125.0819 45.009 15.009 368 125.0920 45.01 15.01 370 125.121 45.011 15.011 372 125.1122 45.012 15.012 374 125.12

Figure 48 Example CSV File

Ident(Octal)

Data ApplicableEquipment

076 Altitude SBAS, GBAS

101 HDOP SBAS, GBAS

101 Selected Heading AFCS

102 Selected Altitude AFCS

102 VDOP SBAS, GBAS

103 Selected Airspeed AFCS

103 Track Angle (True) SBAS, GBAS

105 Runway Heading (Magnetic) SBAS, GBAS

110 PP Latitude - Coarse SBAS, GBAS

111 PP Longitude - Coarse SBAS, GBAS

112 Groundspeed SBAS, GBAS



Ident(Octal)


116 Cross Track Distance EFMS

120 PP Latitude - Fine SBAS, GBAS

121 Bank Demand EFMS

121 PP Longitude - Fine SBAS, GBAS

125 UTC Coarse SBAS, GBAS

130 Horizontal Integrity SBAS, GBAS

133 Vertical Integrity SBAS, GBAS

140 UTC - Fine SBAS, GBAS

141 UTC - Fine Fractions SBAS, GBAS

150 UTC SBAS, GBAS

156 FQIS MCDU

165 Vertical Velocity SBAS, GBAS

172 SAL MCDU

173 Localiser Deviation SBAS, GBAS

174 Glideslope Deviation SBAS, GBAS,EFMS

201 Last Failure Condition AFCS

202 Last IO Failure Condition AFCS

203 Altitude DADC

205 Mach DADC

206 Computed Airspeed DADC

210 True Airspeed DADC

211 Output Status 1 AFCS

212 Altitude Rate DADC

212 Output Status 2 AFCS

213 Static Air Temperature DADC

217 Static Air Pressure DADC

232 Throttle 1 Position AFCS

233 Throttle 2 Position AFCS

245 N1 - Starboard Engine EMS

246 N1 - Port Engine EMS

260 Date SBAS, GBAS

270 Discrete Status Word 1 AFCS

270 Normal Discrete MCDU

271 Discrete Status Word 2 AFCS

272 Operational Modes AFCS

273 Flight Phase AFCS



Ident(Octal)


273 Status Word SBAS, GBAS

274 Vertical Modes AFCS

275 Lateral Modes AFCS

301 Current Profile Mode EFMS

310 PP Latitude IRS, Data Puddle

311 PP Longitude IRS, Data Puddle

312 Groundspeed IRS, Data Puddle

313 Track Angle (True) IRS, Data Puddle

314 True Heading IRS, Data Puddle

315 Windspeed IRS, Data Puddle

316 Wind Direction IRS, Data Puddle

317 Track Angle (Magnetic) IRS

320 Magnetic Heading IRS

321 Drift Angle IRS

322 Flight Path Angle IRS

323 Flight Path Acceleration IRS

324 Pitch Angle IRS

325 Roll Angle IRS

326 Pitch Rate - Body IRS

327 Roll Rate - Body IRS

330 Yaw Rate - Body IRS

331 Longitudinal Acceleration -Body

IRS

332 Lateral Acceleration - Body IRS

333 Normal Acceleration - Body IRS

334 Platform Heading IRS

335 Track Angle Rate IRS

336 Pitch Rate - Inertial IRS

337 Roll Rate - Inertial IRS

350 EICAS MCDU

360 Approach Mode PrimeCommand

EFMS

361 Height Demand EFMS

362 Computed Airspeed Demand EFMS

363 N1 Demand EFMS

364 Next Level Height EFMS

364 Vertical Acceleration IRS



Ident(Octal)


365 Vertical Profile GradientChange

EFMS

365 Vertical Speed IRS

366 N-S Velocity IRS

366 Throttle Demand EFMS

367 E-W Velocity IRS

370 CAS Rate Demand EFMS

377 MAL MCDU

666 Packed Comms Data N/A

Table 9. Data Idents (Octal)

Equipment Id(Octal)

Equipment

1 AFCS

2 EFMS

4 IRS

6 DADC

10 SBAS

11 GBAS

14 Data Puddle

47 MCDU

320 EMS

Table 10. Equipment Idents

5.1 Special Cases

To improve the flexibility of using spreadsheet programs to generate and display data to and from therig, some special characters may be inserted at the beginning of the data parameter to cause theIHTP to perform certain actions. This section describes the implementation of these ‘special cases’.

5.1.1 SSM Bits

The ARINC429 protocol defines two bits as the Status/Sign Matrix (Section 2.1.5 of ARINC 429). Forthe majority of data transmissions between the IHTP and Avionics Rig, these two bits are not usedand therefore are set by default to ‘11’. However, some data items, notably from the SBAS and GBASreceivers, utilise the SSM bits and thus the IHTP has been designed to allow the interpretation ofthese bits, when received from the Avionics Rig, and the setting of these bits in a scenario file.

For parameters where the SSM bits are ‘11’, no extra characters are appended to the data item in the.csv file. For each bit cleared, a double dash ‘—‘ is added to the front of the data item as described inTable 10. Note that spreadsheet programs interpret this as ‘double minus’, i.e. ‘plus’ and the data itemmay therefore be plotted using a chart facility without modification.



SSM Bits Data Prefix ARINC 429 Definition

00 ------ Failure Warning

01 ---- No Computed Data

10 -- Functional Test

11 Normal Operation

Table 11. SSM Bits

5.1.2 Data Update Flag

By default, data logged is by the IHTP at the fastest rate at which data is updated. Thus, if two datastreams are received at different rates, say 5Hz and 1HZ, then all data will be logged at the fasterrate, i.e. 5Hz. For the slower data rate, each data item will be logged at the fast rate but the datacontent will only be updated at the slower rate. To identify when a numeric data item has beenupdated, an equals sign ‘=‘ is prepended to the value.

When the data is viewed in a spreadsheet, the equals sign does not interfere with functions such asplotting, but can be easily seen, thus identifying new data.



6 PARTNER PACKAGESThere are a number of software packages that can be run in conjunction with the IHTP software eitherusing the same, or remote, PC hardware. This section identifies those software packages and thesetup procedures needed to allow the various packages to communicate. Individual usageinstructions for the various applications are not included in this document.

Figure 49 diagrammatically shows the Partner Packages and the interconnectivity between them.Note that all require the use of a Ground Router to forward the data from the ‘ground’ to the ‘air’components of MA-AFAS.

AGP

AMS

BAGS

AMS

TRAFFICSIM

GalileoAvionica

IHTPTAXI ANDATC TOOL

(TAT)

Frequentis

AIRTEL

GROUNDSERVER

FISB

GACS9023

BC9390

ASE6570

9270

AIRTEL

AIR SERVER

BC

GACS

ASE

Position andTime

XML

BC

GACS8023

9290

6770ASE

92509200

9270

BC

9270 9270

BC BC

7750

Avionics Rig

Figure 49 Comms Interconnections in the Test Environment

6.1 Communications Ground Router

The Ground Router, resident on a standard PC, is used to pass data to/from the Air Router, hosted bythe CMU. In the flight trials environment, this datalink is implemented using two VDL Mode 4transponders. For the test environment, however, the implementation is via ethernet.

The Ground Server software (Gnd_AAS.exe) is a command line interpreter type of application thatuses operator inputs to define the required connectivity. To preclude the necessity of an operatortyping in the commands each time the server is run, the command line switch –I is used to allow inputfrom a script file. The ground server application is capable of being run in a UNIX or Windowsenvironment.

The software is supplied with script files for use with both the air and ground routers in the UNIXenvironment. For the simplest usage in a Windows environment, it is recommended that the scripts berun using a UNIX shell such as that provided by the Cygwin application (See http://www.cygwin.comfor more information). Four sets of scripts are provided; Ground (2) and Air (1) routers and Ethernet(B) or COM (C) interface. Each script filename identifies the particular configuration, for example the

http://www.cygwin.com/



script files used to start a Ground Router over ethernet would contain 2 and B. The configuration ofthe files is given in the Avionics Rig Installation Guide.

The first script to run is cfgB.sh (ethernet) or cfgC.sh (COM), an example of which is given in Fig 50:

## Configuration B#

# Router 1 is an Airborne ESexport AAS_R1_IP={IP Address of CMU}

# Router 2 is a Ground ESexport AAS_R2_ATNR={Full pathname}/gnd_aas.exeexport AAS_R2_IP={IP Address of Ground Router}

Figure 50 Example cfgB.sh File

This is invoked in the Cygwin window using the command

. ./cfgB.sh

in the directory holding the script files (usually the aas-scripts directory). This is followed by thecommand

./start_cfgB_R2.sh

that runs the ground router software using the IP addresses set up above. An example file is given inFig 51.

#!/bin/bash

if [[ -z $AAS_R2_ATNR ]]then echo "AAS_R2_ATNR not set" exit 1fi

if [[ -z $AAS_R1_IP ]]then echo "AAS_R1_IP not set" exit 1fi

if [[ -z $AAS_R2_IP ]]then echo "AAS_R2_IP not set" exit 1fi

export AAS_TEST={full pathname}/aas-scriptsexport SCENARIOS=$AAS_TEST/scenariosexport SCRIPTS=$AAS_TEST/scriptsexport DATE_TIME=‘date ’+%d%m%y_%H%M%S’‘export LOGS=$AAS_TEST/../aas-logs/

export AAS_IPADDRESS=$AAS_R2_IP. $AAS_TEST/env_Gnd.shexport ATNR=$AAS_R2_ATNR

$ATNR -i scenarios/maafas_cfgB_R2.inp | tee ${LOGS}/${DATE_TIME}_maafas_cfgB_R2.out

Figure 51 Example start_cfgB_R2.sh File



The start file above uses an input file that defines the actions of the router. In normal circumstances,this input file need not be modified. One modification that can be made is to enable the logging ofdata from the Ground Router.

The Ground Router can be commanded to output logging data by the inclusion of the followingcommands at the end of the input file:

mode orptrace level 0xffff

Values from 0x80 to 0xffff provide differing amounts of logging from minimum to maximumrespectively. To remove logging, the line should be commented out using an initial #.

Terminating the application is achieved by typing ‘exit’ in the shell window, followed by a confirmation‘y’. Note: This may require the entry of several Carriage Returns before control is returned to thecygwin window.

Note that the Ground Router can only accept one broadcast client at a time (i.e. BAGS, Traffic Sim orFIS-B). Thus, only one application (AGP, Traffic Sim or IHTP FIS-B emulation) should be used at anyone time.

6.2 Traffic Simulator

The Traffic Simulator supplied by Galileo Avionica comes in two parts. The initial steps towardcreating a scenario are carried out using an Access database. This database is used to generate anumber of traffic trajectories that can be combined into a named scenario stored in four data files. TheAccess database and its interface are not described here.

The second part of the traffic generator comprises an application (currently TrafficSimulatorv100pE.exe) and a configuration file (TrafficConfig.txt). The application reads the four scenario filesoutput from the Access database and generates real time data for each of the traffic objects definedby the database scenario. This data is then transmitted to the CMU via the Ground Server(Broadcast) application using a UDP protocol ethernet transfer.

In order for the IHTP and Traffic Simulator to interact correctly, each application requires coherentconfiguration data as described in the following sections.

6.2.1 Synchronisation of the Traffic Simulator

The data output by the TSIM comprises a position and time for each traffic object defined by thescenario. These data items are updated at 1Hz. A filter is included in the TSIM to simulate the effectsof range; only objects within 250nm of the current aircraft position are output. To achieve this, theTSIM requires current time and ownship position. These values are obtained in one of two ways,dependant upon the test setup. (See Fig 49)

When the system is run in flight trials, position and time data is generated by the VDL4 transponder.This is then output by the Avionics Rig to the IHTP. By selecting the ADSB to TSIM Operator (see Fig22), this data is forwarded to the Traffic Simulator.

When the system is tested on the bench, time and position data is provided from the IHTP model viathe TSIM Emulator. In this case, the TSIM Emulator should be enabled (See Fig 11). By selecting thePAT to TSIM Operator (see Fig 22), this data is forwarded to the Traffic Simulator.



IHTP PC PC

TrafficSim

PC

GroundServer

CMU

Port2040

Port9270

Port2040

Port9290

Port9250

AirServer

VDL4I/F

A/CModel

Operators

Port50020

Port50020

Port9200

Figure 52 Traffic Simulator Interface with IHTP

Note, the ADSB to TSIM Operator and PAT to TSIM Operator are mutually exclusive and should notbe selected at the same time.

6.2.2 IHTP Configuration for Traffic Simulator

In order for the IHTP to transmit time and ownship position data to the Traffic Simulator, a UDPconnection needs to be set up. This is achieved using the following configuration panels:

CEthernetRouter (4.1)

CPhysicalPortManager (4.4)

EtherUDP (4.4.2)

The CEthernetRouter panel is used to set the Traffic ports to 2040 (the standard setting).

CPhysicalPortManager is used to set the Traffic Tx Port Type to E (ethernet) and the Traffic TxNamed Config to UDP.

The EtherUDP panel should have the following set:

IPAddress if Target: [IP address of PC running Traffic Simulator]

Use TCP IP: FALSE

Connect On Demand: FALSE

Type of Link: I

Note that when the a/c model provides the time and position data, the Aircraft Present Position andAttitude should be compatible with the Traffic Simulator scenario. This is achieved using theCAircraftModel configuration panel to set the initial parameters.

When the Avionics Rig supplies the time source, the IHTP should be set up to receive the PositionAnd Time (PAT) transmissions from the Rig using the following configuration panels:

CEthernetRouter (4.1)

CPhysicalPortManager (4.4)

The CEthernetRouter panel is used to set the PAT ports to 50020 (the standard setting).



The CPhysicalPortManager panel is used to set the PAT Rx Port Type to E (ethernet) and PAT RxNamed Config to Default

6.2.3 Traffic Simulator Configuration

In the directory that contains the Traffic Simulator executable, there is a text configuration file;TrafficConfig.txt, that can be edited using notepad as follows:

IPaddressIN: [IP Address of PC running Traffic Simulator]

PortIN: 2040

IPaddressOUT: [IP Address of PC running Broadcast Server]

PortOUT: 9290

SerialPort COM5

Note that the Serial Port data is for use when the Traffic Sim:CMU link is achieved using VDL4Transponders.

6.2.4 Running the IHTP When Connected to the Traffic Simulator

Once the IHTP is running, the a/c model should be invoked and the TSIM Emulator enabled(3.2.2.4.1). The transmission of data to the Traffic Simulator can then be verified by the inclusion of aCTrafficSimulationMessage entry in the History screen and the activation of the Interface StatusMonitor (3.2.2.9) for the Traffic Sim. Data will be transmitted at a 1Hz rate.

6.3 AOC Ground Platform

The AOC Ground Platform (AGP) is used to simulate the Aircraft Operations Centre (AOC) in the MA-AFAS environment. The tool can compile and transmit (via Ethernet) datalink messages to theAvionics Rig as defined in the AGP Users Guide D63. When used to stimulate the Avionics Rig,configuration files are used to define the physical setup (Ethernet addresses etc) and the plannedflight. Although the AGP doesn’t connect to the IHTP or use the IHTP facilities it is included here forcompleteness. The following sections define the steps needed to configure the AGP; specific detailsof how to perform the steps are to be found in D63.

6.3.1 Scenario Generation

A scenario needs to be generated that matches the intended route(s) input to the Avionics Rig. Thefile configurationData.dat in the AGP executables directory is used to identify the path of the scenariofiles along with the slot allocation file slotAllocation.dat.

This scenario is defined by a file in the AGP Data directory with an extension of .sen. This file definesthe directory in which all information is stored.

The scenario directory must hold flight plan files (*.fp) and a slot allocation file (slotAllocations.dat).Optionally, it can hold a flight simulator control file (*.fs). Flight Plan and Company Route files havethe same format and this is described in the Avionics Rig Userguide, D42, and the AGP UsersManual, D63.

The AGP is configured using the configurationData.dat file held in the same directory as theexecutable. This configuration file contains paths for all the operating files. The only paths to modifyare those associated with the flight path and the slot allocation files.

Date post:	09-Feb-2018
Category:	Documents
Upload:	volien
View:	213 times
Download:	0 times

Users Guide for the In House Test Platform - ASAS TN · PDF fileAirtel ATN Ltd (Ireland)...

Documents