requirements verification & validation€¦ · web viewuser guide. issue: draft 0.17. author:...

TCAS 2004 Reference GL/<project>/<type>/<no>

30 March 2006 /tt/file_convert/5f0a3ac57e708231d42aa384/document.doc

TCAS 2004

User Guide

Issue: Draft 0.17

Author: Graffica

Date: 30 March 2006

Company: Graffica Ltd

of 38



Table Of Contents

1 Introduction......................................................................................................................................4

1.1 Version History........................................................................................................................4

1.2 References................................................................................................................................4

1.3 Abbreviations...........................................................................................................................5

2 Installation Notes.............................................................................................................................6

2.1 Haptic Alarm............................................................................................................................6

2.2 Support For MP3 Files.............................................................................................................7

3 Resource Descriptions.....................................................................................................................8

4 Revised Resolution Advisory File Format.....................................................................................14

4.1 Examples................................................................................................................................14

5 Scenarios........................................................................................................................................15

6 The Launcher.................................................................................................................................16

6.1 Simulation Configuration Options.........................................................................................18

6.2 Recording Options.................................................................................................................18

6.3 Replay Options......................................................................................................................18

7 Sound Clips File.............................................................................................................................22

8 Launching The Air Configuration.................................................................................................23

9 Changing TCAS Alert Colours......................................................................................................24

10 Stopping Scenarios At a Specified Time...................................................................................25

11 Using The ILS Capability..........................................................................................................26

12 Running In Distributed Mode....................................................................................................27

13 Managing Advisories in the PWP..............................................................................................28

14 Launching the FARADS/RADE eDEP Simulation with ACAS server....................................30

14.1 Login to the required machines.............................................................................................30

14.2 Launch the ACAS server.......................................................................................................30

14.3 Launch the eDEP Simulation engine.....................................................................................30

14.4 Launch the CWP....................................................................................................................31

14.5 Launch the PWPs...................................................................................................................31

14.6 To start the simulation,..........................................................................................................31

14.7 To stop the simulation,...........................................................................................................31

14.8 Passwords...............................................................................................................................31

15 Installation Locations.................................................................................................................32

15.1 Windows PCs.........................................................................................................................32

15.2 Hflab (Linux) machines.........................................................................................................32

15.3 Configuration Issues..............................................................................................................32

16 Launching the SAT....................................................................................................................34

of 38



16.1 Required Software.................................................................................................................34

16.2 Locating the XML Data.........................................................................................................35

16.3 Locating the XML SCHEMA................................................................................................35

17 CWP RAs – eDEP for RADE-2 (when connected to ACAS server)........................................36

18 CWP RAs – eDEP for RADE-2 (no ACAS server, non-interactive scenarios)........................37

of 38



1 INTRODUCTION

The aim of this document is to assist eDEP users with the activities of platform installation, configuration and launching. This note contains information detailing:

the installation of the software necessary to drive the TCAS haptic alarm;

the set up of the TCAS resource parameters; and

the revised file format containing the resolution advisories used by TCAS.

For more information concerning the platform design the reader should address either the Architecture Design Document (ADD) [Ref. 1] or the Detailed Design Document (DDD).

1.1 VERSION HISTORYRelease Author Release Date Release Description Modifications (sections affected

and relevant information)

0.8 Graffica (Aynsworth)

13th April 2005

Eighth release Added section on running sim.

0.9 Graffica (Cooper)

14th April 2005

Updated following Launcher and Recording / Replay changes.

0.10 Graffica (Humphrey)

14th April 2005

Added section on Installation Locations.


14th April 2005

Added section on PWP shortcuts. Described new resource parameters.


15th April 2005

Updated Replay description.


27th April 2005

Included instructions to launch the SAT.


2nd June 2005 Updated with resources and screenshots used with version Rel_eDEP_1_5(TCAS).


25th August 2005

Updated resources for climb and descend flight levels and rates during a TCAS RA.


26th August 2005

Added resource for filtering / removing the CFL display when AFL is within a variable distance of it.


13th Sept 2005 Added resources for configuring the generalised TCAS RA display symbols.

1.2 REFERENCESThe following documents are referenced.

1. eDEP Architecture Design Doc., GL/eDEP/ADD/1 V1.8, M. Vere, March 2003

2. eDEP GSDK Detailed Design, 1.5, M.Vere, October 2002

3. eDEP ATC Detailed Design, GL/eDEP/DDD/1/1.9, M. Vere, March 2003

4. eDEP User Guide, Graffica, May 2004.

of 38



5. eDEP ATCX User Guide, Graffica, May 2004.

1.3 ABBREVIATIONSAbbreviation Meaning

CWP Controller Working Position

IDE Integrated Development Environment

JRE Java Runtime Environment

JVM Java Virtual Machine

SDK Software Development Kit

VOIP Voice Over Internet Protocol

of 38



2 INSTALLATION NOTES

2.1 HAPTIC ALARMTo install the driver necessary to control the haptic alarm through a parallel port follow the installation instructions at www.geocities.com/juanga69/parport.

This will involve copying parport.dll to your <JDK>\bin i.e. the bin folder below your JDK installation.

If you have Windows NT (or higher) then you will also need to install UserPort. You will need administrator privileges to use UserPort as it grants you access to hardware addresses that are not usually available to a user.

Step by step instructions for the installation of parport and UserPort can be obtained from www.geocities.com/juanga69/parport.

If the parport.dll file is not copied to the correct location, a Java UnsatisifiedLinkError will be generated. If the UserPort software is not used to provide access to the parallel port addresses, an exception will be raised when eDEP attempts to control the port. Typical output when this exception is raised is shown below.

An unexpected exception has been detected in native code outside the VM.Unexpected Signal : EXCEPTION_PRIV_INSTRUCTION occurred at PC=0xD30107BFunction=[Unknown.]Library=C:\j2sdk1.4.0_01\bin\parport.dllNOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions.Current Java thread:

at parport.ParallelPort.writeOneByte(Native Method)at parport.ParallelPort.write(ParallelPort.java:60)at test.parallel.SimpleHapticTest.sendHexPair(SimpleHapticTest.java:45)at

test.parallel.SimpleHapticTest$ButtonListener.actionPerformed(SimpleHapticTest.java:84)at java.awt.Button.processActionEvent(Button.java:381)at java.awt.Button.processEvent(Button.java:350)at java.awt.Component.dispatchEventImpl(Component.java:3526)at java.awt.Component.dispatchEvent(Component.java:3367)at java.awt.EventQueue.dispatchEvent(EventQueue.java:445)at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:191)at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:144)at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:130)at java.awt.EventDispatchThread.run(EventDispatchThread.java:98)

Dynamic libraries:0x00400000 - 0x00406000 C:\j2sdk1.4.0_01\bin\javaw.exe0x77F80000 - 0x77FFB000 C:\WINNT\System32\ntdll.dll0x0E800000 - 0x0E80B000 C:\WINNT\System32\PSAPI.DLL

Local Time = Tue Sep 09 17:40:44 2003Elapsed Time = 4## The exception above was detected in native code outside the VM## Java VM: Java HotSpot(TM) Client VM (1.4.0_01-b03 mixed mode)#

of 38



2.2 SUPPORT FOR MP3 FILESIf MP3 Support is required, the Java SPI is required. This library is platform independent. The Java SPI Framework is available for download from:

http://www.javazoom.net/mp3spi/mp3spi.html

Copy tritonus_share.jar, mp3spi1.9.jar and jl0.4.jar into the TOOLS directory and add a reference to each in eclipse in Project – Properties – Java Build Path – Libraries.

of 38



3 RESOURCE DESCRIPTIONSRESOURCE TYPICAL VALUE DESCRIPTION

IFPL.SCENARIO "tcas/resources/scenarios/54/CORA1_54_TRAFFIC.dat" The traffic file used in the scenario. This resource is set automatically in the launcher.

IAS.SCENARIO_READER "tcas.ias.server.TCASScenarioReaderImpl" The Scenario Reader class implementation defined for TCAS.

TCAS.ABBREVIATE_CLEAR

TCAS.ABBREVIATE_CLIMB

TCAS.ABBREVIATE_CLIMB_CLIMB

TCAS.ABBREVIATE_DESCEND

TCAS.ABBREVIATE_DESCEND_DESCEND

TCAS.ABBREVIATE_CLIMB_500FPM



TCAS.ABBREVIATE_DESCEND_500FPM



"COC"

"CLM"

"ICL"

"DES"

"IDE"

“LC5”

“LC1”

“LC2”

"LD5"

"LD1"

"LD2"

TCAS default abbreviations/symbols. Note: can use Unicode to define symbols e.g. replace “CLM” with “\\u2191” to get up arrow. Similarly, replace “ICL” with \\u2191\\u2191 to get a double up arrow.

This functionality is no longer supported due to the need to support RA types from both the server and the scripted files. The RA mnemonics are hardcoded in the ResolutionAdvisoryUtilities class.

TCAS.RESOLUTION_FLASH_RATE_MS 1000.0 Duration, which TCAS label and/or background will remain on when flashing.

TCAS.RESOLUTION_FLASH_OFF_RATE_MS 1000.0 Duration, which TCAS label and/or background will remain off when flashing.

TP.MODEL_CLIMB_SMOOTHING TRUE Smoothes the climb/descent profile to remove discontinuities that can confuse the ACAS server.

TP.MODEL_SMOOTH_ACCELERATION TRUE Smoothes the flight acceleration profile.

STCA.VERTICAL_SEPARATION.NON_LEVEL_SUPPLEMENT 0 Reduces the sensitivity of STCA to flights climbing / descending in order to remove unnecessary STCA alerts.

PVD.LABEL.CLASS “tcas.graphics.label.TCASLabel” The Label class to be used with flights in the

of 38



RESOURCE TYPICAL VALUE DESCRIPTION

CWP.

PVD.ALERT_WINDOW.CLASS “tcas.alertwindow.TCASAlertWindow” The Alert Window to be used in the CWP.

PVD.EXTENDED_LABEL_CLASS “tcas.graphics.extendedlabel.ExtendedTCASLabel” The Extended Label to be shown in the ELW.

VVC.AUDIO_ALARM.CLASS "tcas.vvc.server.AudioAlarmImpl" The Audio alarm class implementation defined for TCAS.

VVC.STCA_WARNING ON Can be either ON or OFF. When ON STCA “softly spoken” warning will be issued.

VVC.STCA_STERN_WARNING ON Can be either ON or OFF. When ON STCA “sternly spoken” (2nd) warning will be issued.

VVC.HAPTIC_ALARM.CLASS "tcas.vvc.server.HapticAlarmImpl" The Haptic alarm class implementation defined for TCAS.

VVC.PARALLEL_PORT_ADDRESS 888 Parallel port address (decimal) of haptic alarm (888 = 0x378).

VVC.HAPTIC_ALARM_SIGNAL_ON 128 Byte value (decimal) to switch alarm on (128 = 0x80).

VVC.HAPTIC_ALARM_SIGNAL_OF 0 Byte value (decimal) to switch alarm off.

VVC.RESOLUTION_TCAS_AUDIO_PERIOD_MS 5000.0 Time (ms) at which TCAS audio alarm will be repeated.

VVC.RESOLUTION_VIBRATE_DURATION_MS 10000.0 Duration (ms) which haptic alarm will vibrate for.

VVC.SCENARIO "tcas/resources/scenarios/54/54_sounds.dat The location of the sound clips file. This resource is set automatically in the launcher. The name is derived from the scenario name.

of 38




VVC.SOUNDFILE_DIRECTORY "tcas/resources/sounds/" The location of the sound clips played when an STCA or TCAS alert occurs.

VVC.CONFLICT_CLIP conflict.wav 1st STCA clip to be played.

The filename is specified relative to the sound file directory specified above.

VVC.CONFLICT_CONFLICT_CLIP conflictconflict.wav 2nd STCA clip to be played.


VVC.TCAS_TCAS_CLIP tcastcas.wav TCAS alert to be played.


The TCAS Launcher uses the resources defined below to realize the four different HMI variants.

TCAS.RESOLUTION_TEXT <string> The text to be displayed in the aircraft label, typically TCAS or RA.

TCAS.RESOLUTION_DIRECTION <boolean> Determines whether the resolution sense is displayed.

TCAS.RESOLUTION_FLASH_TEXT <boolean> Determines whether flashing text is displayed.

TCAS.RESOLUTION_AC_INVOLVED <boolean>

TCAS.RESOLUTION_BACKGROUND <”OFF” | “HIGHLIGHT” | “FLASH”>

VVC.RESOLUTION_AUDIO <"OFF" | “SINGLE” | “CONTINUOUS”> Determines whether the TCAS warning is played and if it is played, whether it is played once or continuously.

VVC.RESOLUTION_VIBRATE <"OFF" | “SINGLE” | “CONTINUOUS”> Determines whether the haptic alarm is triggered and if it is triggered, whether it is triggered once or continuously.

TCAS.RESOLUTION_HIGHLIGHT_AC_INVOLVED <boolean> Determines whether an aircraft, involved in an advisory, without an advisory is highlighted.

of 38




The settings for each of the four HMI variants are listed below. Changing these settings will enable the user to change the configuration of one of the predefined HMIs.

TCAS.HMIMIN_RES_TEXT

TCAS.HMIMIN_RES_DIRECTION

TCAS.HMIMIN_RES_FLASH_TEXT

TCAS.HMIMIN_RES_AC_INVOLVED

TCAS.HMIMIN_RES_BACKGROUND

TCAS.HMIMIN_RES_AUDIO

TCAS.HMIMIN_RES_VIBRATE

TCAS.HMIMIN_RES_HIGHLIGHT_AC_INVOLVED

"TCAS"

FALSE

FALSE

FALSE

HIGHLIGHT

"OFF"

"OFF"

TRUE

TCAS HMI Minimum configuration

TCAS.HMIINT_RES_TEXT

TCAS.HMIINT_RES_DIRECTION

TCAS.HMIINT_RES_FLASH_TEXT

TCAS.HMIINT_RES_AC_INVOLVED

TCAS.HMIINT_RES_BACKGROUND

TCAS.HMIINT_RES_AUDIO

TCAS.HMIINT_RES_VIBRATE

TCAS.HMIINT_RES_HIGHLIGHT_AC_INVOLVED

"TCAS"

TRUE

FALSE

FALSE

HIGHLIGHT

"OFF"

"OFF"

TRUE

TCAS HMI Intermediate configuration

TCAS.HMIEXT_RES_TEXT

TCAS.HMIEXT_RES_DIRECTION

TCAS.HMIEXT_RES_FLASH_TEXT

TCAS.HMIEXT_RES_AC_INVOLVED

TCAS.HMIEXT_RES_BACKGROUND

TCAS.HMIEXT_RES_AUDIO

TCAS.HMIEXT_RES_VIBRATE

"TCAS"

TRUE

FALSE

FALSE

FLASH

"SINGLE"

"SINGLE"

TRUE

TCAS HMI Extreme configuration

of 38




TCAS.HMIEXT_RES_HIGHLIGHT_AC_INVOLVED

CLOCK.STOPTIME "16:43:00” This determines the end time of the simulation. When set, the entire application shuts down at the specified time.

ACSG.ACS_HOSTNAME The hostname of the ACAS Server

ACSG.ACS_PORT The port on which to connect to the ACAS Server

ACSG.LOCAL_PORT The port on the local machine to which to listen

The settings for recording the replay of the log and audio files are listed below. The Launcher sets these values based on the recording and replay options,

VOIP.AUDIO_MODE AUDIO_RECORD Determines whether the VOIP component should record or play and audio file. Available values are: AUDIO_RECORD and AUDIO_REPLAY. Any other value will result in neither a recording or replay.

VOIP.AUDIO_FILE The ‘audio’ file, A or B, in the recording directory on the local machine.

Specifies the directory and filename for which the audio recording should be read or written.

<CWP Component Name>.RECORD_MODE RECORD Determines whether the log and orders log file should be read or written for the specified CWP component. Available values are: RECORD, REPLAY and NONE

<CWP Component Name>.RECORD_FILE The ‘log’ file, A or B, in the recording directory on the local machine.

Specifies the directory and filename for which the logs recording file should be read or written.

<CWP Component Name>.ORDER_RECORD_FILE The ‘orders log’ file, A or B, in the recording directory on the local machine.

Specifies the directory and filename for which the order logs recording file should be read or written.

RECORD.ORDER_RECORD_INDEX The ‘sigEvents’ file, A or B, in the recording directory on the local machine.

This file is written by the Launcher prior to replaying, and contains a reference to the ORDER_RECORD_FILE created by when recording. Temporary file needed for replay purposes only.

TCAS.ALIGN_SCENARIO_TIME TRUE Defines whether to align the eDEP simulation length defined in the log files to the audio file length.

TCAS.CLIMB_DESCEND_FL 5 The number of flight levels an aircraft should climb or descend when ordered to

of 38




climb/descend as a result of a TCAS advisory. eDEP has no explicit climb/descend command. Climb/descend is achieved by instructing an aircraft to climb/descend to AFL+/-CLIMB_DESCEND_FL

TCAS.CLIMB_DESCEND_RATE 1500 The rate at which an aircraft should climb or descend when ordered to climb/descend as a result of a TCAS advisory.

TCAS.REVERSALS_REQUIRED TRUE Determines whether reversal RAs should be displayed.

TCAS_CFL_DISPLAY_RANGE 2 The CFL is removed from the display when the AFL is within the given FL distance from it.

TCAS.SHOW_RA_SYMBOLS TRUE Determines if the CWP should display generalized TCAS RA information or the mnemonic information. The default (TRUE) settings shows the generalized RA symbols.

TCAS.RESOLUTION_SYMBOL.UP “\\u2191” A string allowing the up or climb symbol displayed when showing generalized TCAS RA information to be customized.

TCAS.RESOLUTION_SYMBOL.DOWN “\\u2193” A string allowing the down or descend symbol displayed when showing generalized TCAS RA information to be customized.

TCAS.RESOLUTION_SYMBOL.LEVEL “-“ A string allowing the level-off symbol displayed when showing generalized TCAS RA information to be customized.

TCAS.RESOLUTION_SYMBOL.NOADV ““– no text A string allowing the no-advisory symbol displayed when showing generalized TCAS RA information to be customized.

TCAS.RESOLUTION_SYMBOL.UNKNOWN “?” A string allowing the unknown advisory symbol displayed when showing generalized TCAS RA information to be customized.

PVD.STCA.LIMIT_TIME 90 The maximum length of the STCA conflict line in seconds from current location. Current limit is 90 seconds.

<STCA>.FILTER_ON_CFL TRUE Flag used to select filtering of STCA according to expected CFL stop-off level.

of 38



4 REVISED RESOLUTION ADVISORY FILE FORMAT

TCAS_Advisory = <time> + <callsign> + <altitude> + [<advisory> + [<involved_aircraft>]];

Where time = nn:nn:nn

callsign = name

altitude = number

involved_aircraft = name

advisory = < “CLEAR” | <descend_advisory> | <climb_advisory> >

descend_advisory = string starting with the text “DESCEND”

climb_advisory = string starting with the text “CLIMB”

4.1 EXAMPLES

Time

Callsign Altitude Advisory Involved Aircraft

16:13:26 CNF001 31550 DESCEND SPOOF

16:13:27 CNF001 31550 DESCEND_DESCEND SPOOF

16:13:28 CNF001 31550 DESCEND_500FPM SPOOF

16:13:29 CNF001 31550 DESCEND_1000FPM SPOOF

16:13:29 CNF001 31550 DESCEND_QUICKLY SPOOF

The advisories CLEAR, CLIMB and DESCEND have default abbreviations COC, CLM and DES but can be replaced by the user by defining abbreviations in the TCAS resource file. For any other advisory to be indicated on the display a matching abbreviation must exist in the TCAS resource file e.g. TCAS.ABBREVIATE_DESCEND_QUICKLY “DQ”

Note: For backwards compatibility the previous advisories “DESCEND DESCEND” and “CLIMB CLIMB” can still be used but internally they will be treated as “DESCEND_DESCEND” and “CLIMB_CLIMB” respectively.

of 38



5 SCENARIOS

The CORA2 2002 traffic files have been added to the tcas scenarios. A distributed scenario has been created, this is TCASTest4. This scenario cannot be launched through the launcher. Bat files have been provided to launch this scenario. The common_distribution.gsdk file will need to be modified, to include the appropriate discovery host name.

The original scenario files are compatible with the new file format.

of 38



6 THE LAUNCHER

The Launcher allows a TCAS scenario to be launched in a number of different distribution modes. The modes are

1. Standalone, where the scenario is run on a single machine

2. Dual, where the scenario is run split between two machines.

3. CWP Only, runs the CWP without the VVC

4. Sim. Engine Only, runs the simulation engine and time control panel.

5. VVC Only, is run on a remote machine to pair with a CWP. This mode is not supported as of 14/04/2005.

The TCAS launcher provides a number of differing HMI variants. The launcher, showing the available HMI variants, is shown in Figure 1, below.

Figure 1 Launcher Showing HMI Variants

It can be seen from Figure 1 that the launcher supports a customise HMI mode This allows a user to create a bespoke HMI. If the user selects the customise HMI variant, a tabbed pane, named RAOptions, is included in the launcher. This is shown in figure 2, below.

of 38



Figure 2 Launcher with RAOptions Tab

Figure 3, below, illustrates the options that can be customised through the launcher.

Figure 3 Defining a Customised HMI

Customised HMIs cannot be saved. However, the contents of the standard HMIs can be changed through the resource parameters.

of 38



6.1 SIMULATION CONFIGURATION OPTIONSThe launcher allows the simulation configuration to be specified as one of two variants, A or B. The following resource files support this:

<resources>acsg_settings_A.gsdk

<resources>common_distribution_A.gsdk

<resources>distributed_PWP1_A.gsdk

<resources>distributed_PWP2_A.gsdk

<resources>acsg_settings_B.gsdk

<resources>common_distribution_B.gsdk

<resources>distributed_PWP1_B.gsdk

<resources>distributed_PWP2_B.gsdk

The values for each configuration must be set depending on the local environment before running a distributed simulation.

6.2 RECORDING OPTIONSThe launcher allows the configuration of the recording options for log files and audio, and allows for the specification of the location for the recording files. The ‘Browse’ button next to the directory location allows the recording /replay directory location to be changed.

An audio file can be created when running in ‘STANDALONE’ or ‘SIM. ENGINE ONLY’ modes. The audio file name will be appended with the simulation configuration (A or B) and written to the specified directory.

The log files can be created when running in ‘STANDALONE’ or ‘CWP ONLY’ modes. The log files will be appended with the simulation configuration (A or B) and written to the specified directory.

6.3 REPLAY OPTIONSRecorded files can be replayed using the ‘Replay’ button in the Launcher. The location of the files to be replayed is specified in the launcher, and can be changed using the ‘Browse’ button to select another directory. The ‘Replay’ button, Record and Replay Directory Location and ‘Browse’ button can be seen in the following screen shot:

of 38



Figure 4 Replay Options in the Launcher

Figure 5 below shows the directory selection window opened by clicking the ‘Browse’ button:

Figure 5 Record / Replay Directory Selector

The launcher attempts to load files from the selected directory that match the following formats:

Log Files:

CWP_<A|B>.log

CWP_<A/B>_orders.log

of 38



Audio File:

AudioRecording_<A|B>.wav

The simulation configuration option is taken into account, replaying all files with either the A or B indicator tag. The replay will run with the Log files only, Audio files only, or both Log and Audio files together.

The replay display consists of the Time Control Panel, Replay Orders window and a basic CWP, like the one shown below:

Figure 6 Replay CWP

The Replay Orders window can be seen in Figure 7:

of 38



Figure 7 Replay Orders Window

When a replay is launched all options other than the replay location and the simulation configuration are ignored.

of 38



7 SOUND CLIPS FILE

An example scenario sound clips file is shown above. When adding sound clips, the following rules shall be followed:

//time filename//16:12:10 "AF855PT leaves_with acnoise.wav"16:12:11 "AF855PT leaves_with acnoise.wav"16:19:10 "AF936EZ Leave_with_hum+noise.mp3"16:19:30 "AF936EZ Leave_with hum+noise.wav"

The sound clips, i.e. the .wav or mp3 files, shall reside in a directory, sounds, located in the scenario directory. For example, given the scenario TCASTest1, the sound clips are located in TCASTest1/sounds.

The file name of the scenario sound clips file shall be <<scenario_name>>_sounds.dat, e.g. for the test scenario TCASTest1, the scenario sound clips file is TCASTest1_sounds.dat. This file shall be located in the scenario directory; in the example TCASTest1.

The resource VVC.SCENARIO specifies the location of the sound clips file. This resource is set automatically in the launcher. It is not necessary to set this resource in the scenario’s resource file. The location is derived from the scenario name. Given the scenario TCASTest1, located in the directory TCASTest1, the resource would be set to:

"tcas/resources/scenarios/TCASTest1/TCASTest1_sounds.dat"

If the Java SPI is installed as described in the installation notes, MP3 files can be used in addition to WAV files. The type of file is determined by the file extension.

of 38



8 LAUNCHING THE AIR CONFIGURATION

The air configuration is automatically launched if the resource parameter IAS.TRAJECTORY_TO_FLY is set to AIRCRAFT in the tcas_cwp.gsdk file. In addition to specifying flown trajectory, it is also necessary to list the Pilot Working Positions to be included in the scenario. This is achieved by setting the PWP.NAMES resource parameter. The PWPs are assigned to sectors in the tcas_pwp.gsdk file, an extract of this file is shown in the figure below.

@LOAD "atcapp/resources/common/pwp_defaults.gsdk"

PWP1.FREQUENCY ( 124.3, 126.7, 133.35, 135.45 )PWP2.FREQUENCY (120.185, 122.725, 119.25, 120.15, 119.15 )

PWP1.WIDTH 900PWP1.HEIGHT 800PWP1.PVD.WIDTH 300PWP1.PVD.HEIGHT 300PWP1.PVD.LATITUDE 50.0PWP1.PVD.LONGITUDE 3.0PWP1.PVD.SCALE 200

An option to launch the air configuration is not included in the Launcher because it was thought that this would be an option that would not change on a regular basis, and it could even lead to some confusion.

of 38



9 CHANGING TCAS ALERT COLOURS

The colours of the TCAS alert buttons are configured, and hence may be changed, through the TCAS logical colour file. This file is located in tcas/resources. The contents of this file are illustrated below. The physical colours referenced in this file, in the example below, Orange and Green, must be included in the eDEP physical colours file. This file is located in atcapp/resources/common/graphics.

TCAS.LOGICAL_COLOURS

(

( ALERT_DEFAULT_BACKGROUND, Orange ),

( ALERT_DEFAULT_FOREGROUND, Green )

)

of 38



10 STOPPING SCENARIOS AT A SPECIFIED TIME

There are two mechanisms for stopping a scenario: specifying the CLOCK.STOPTIME resource parameter or using the scripted event tool. The resource parameter mechanism is detailed in the eDEP User Guide [Ref. 5] whilst the scripted event mechanism is described in the eDEP ATC Extensions User Guide [Ref. 5].

of 38



11 USING THE ILS CAPABILITY

If the ILS landing functionality is to be utilised, the ils_defaults.gsdk resource file must be loaded. It is imperative that a STAR’s constituent points correctly align the aircraft with the runway; otherwise the aircraft will not be captured by the ILS. There is a thirty degree capture angle in which the approach the runway.

Figure 8 ILS Capability

of 38

final STAR pointfinal STAR point

Aircraft must enter through this box within +- 30 degrees of the centre line.

runway



12 RUNNING IN DISTRIBUTED MODE

The TCAS platform may be run across two machines, with the CWP and simulation engine on one machine, and the PWP on the other. The DUAL mode from the TCAS Launcher must be selected. Before running the system it is necessary to modify one of the bat files to ensure connection between the PWP and the CWP/Simulation Engine. The necessary steps are detailed in the following sections.

The java.policy file must be copied into the directory from which the CWP and the PWP are to be run.

The CWP must be launched first via the TCASSeparateResources.bat file. When the CWP has been successfully launched, the PWP may be launched. The TCAS_PWP.bat file is used to launch the PWP. The name of the machine upon which the corresponding CWP is run must be specified in this file. The batch script is shown below; the line that must be modified for each installation is highlighted.

remrem This is a batch script to launch the TCAS PWP.rem

set PTT_CWP=othello

java -cp eDEP.jar;products/classes -Djava.security.policy=java.policy ……..

Figure 9 – TCAS_PWP.bat File

The PWP launcher automatically detects the host name, and therefore, the TCASSeparateResources.bat file does not need to be modified. To assist launching the TCAS Launcher displays the name of the machine upon which it is run.

Figure 10 - TCAS Launcher

of 38



13 MANAGING ADVISORIES IN THE PWP

Figure 11 illustrates how an advisory is displayed in the PWP. The reports column is highlighted red. The highlighted page button indicates that there is an advisory for a second aircraft. The pilot can quickly respond to the advisory by clicking on the reports field.

Figure 11 Advisory Displayed in PWP

Figure 12 shows the advisory response panel accessed through the reports field This is only accessible when there is an advisory for a flight.

Figure 12 Responding to an Advisory

of 38



Figure 13 shows the final stage of the advisory response. The pilot must execute the command for the aircraft to climb/descend.

Figure 13 Responding to an Advisory

of 38



14 LAUNCHING THE FARADS/RADE EDEP SIMULATION WITH ACAS SERVER

This brief guide lists the steps to launch the eDEP platform, integrated with the ACAS server, to run a FARADS/RADE enroute simulation with just one CWP. It assumes all the necessary simulation and scenario preparation for eDEP and the ACAS server has already been performed.

14.1 LOGIN TO THE REQUIRED MACHINES.There are two groups of machines, for running two separate simulations. These are:

PCs RADE1, RADE2, RADE3 with workstations hflab1, hflab2; or

PCs RADE4, RADE5, RADE6 with workstations hflab3, hflab4.

For both configurations, the ACAS server is run on the machine moorea, under the user account acas. This computer can be accessed via remote login from one of the hflab workstations (rlogin –l acas moorea), or via Exceed from the PC RADE1.

14.2 LAUNCH THE ACAS SERVER.In the directory ~/PhaseB/simulation/Rade2, run the command:

execute_edep_exercise.csh Rade2 <exercise> <scenario>

e.g. execute_edep_exercise.csh Rade2 RADL2 test.

While any name can be chosen for the scenario, to distinguish results for example, the file TrafficSample.<scenario> must already exist in the <exercise> sub-directory; this can be a straight copy of any previous traffic samples for the same exercise.

The server is ready when the following text is shown, without any error messages appears:Simulation Rade2Exercise <exercise>Log file: Rade2/<exercise>/Exercise.log.<scenario>Out file : Rade2/<exercise>/Exercise.out

The progress of the server can be checked by examining the given log file, for example, in a text editor, or following it from a different window (tail –f Exercsie.log.<scenario>).

14.3 LAUNCH THE EDEP SIMULATION ENGINE(on RADL1 or RADL4 according to the configuration being used):

double-click on the TCAS2004 EEC icon in the middle of the screen

select the scenario to be run – the same as the ACAS server exercise!

select the mode SIM. ENGINE ONLY

select the simulation configuration – A or B

click on Run Test

When the Console window appears, the remaining eDEP components can be launched:

of 38



14.4 LAUNCH THE CWPOn hflab1 or hflab2, or on hflab3 or hflab4:

click on the TCAS2004 icon on the left hand side of the screen

select the mode CWP ONLY

select the scenario to be run – the same as the ACAS server exercise!

select the HMI variant INTERMEDIATE

select the Display BARCO

select the simulation configuration – the same as the eDEP Simulation Engine.

click on Run Test.

14.5 LAUNCH THE PWPSOn RADE2 & RADE3 or on RADE5 and RADE6 by double-clicking on the PWP1 and PWP2 icons in the middle of the screens.

14.6 TO START THE SIMULATION,press the Play button on the Console (on RADL1 or RADL4).

14.7 TO STOP THE SIMULATION,Press the Stop button on the Console (on RADL1 or RADL4). When the eDEP Simulation Engine has shut down, select the menu item File/Exit on the CWP and PWPs. The ACAS server will shutdown automatically on a signal from the eDEP simulation engine, and will ask if any previous stored exercise log file should be overwritten.

14.8 PASSWORDSFor the PCs RADL1 - RADL6, the user account/password is guest1/guest1.

For the workstations hflab1 - hflab4, the user account/password is edep/edep123.

For the acas server, moorea, the user account/password is acas/dcl1000.

of 38



15 INSTALLATION LOCATIONS

This section gives details of directory locations, etc. relevant to the eDEP TCAS platform. This information is not intended for the average user, but for simulation supervisors, support, etc.

15.1 WINDOWS PCSThe simulation is installed in D:\RADE2005.

This directory contains all the launch batch files and the directories log, rec and products.

The products directory contains all the jar files.

The launch batch files redirect output to log files in the directory log.

The rec directory is intended to hold eDEP recordings (CWP or VOIP).

The main eDEP jar is currently named tcas_05Q1.jar. This will change for future deliveries and any interim updates. The batch files will need to be updated to use the new jar when this happens.

An alternative jar, tcas_nores_05Q1.jar is also present. This is identical to the above except it does not contain the tcas resources. Alternative batch files (…_local).bat run with this jar, and will search the local directory for the resources – i.e. if the resource files themselves are placed in D:\RADE2005\tcas\resources\... . These alternative batch files should be checked to ensure they do include the current directory ‘.’ in the classpath.

Eclipse is installed on RADE1 and RADE2. The source is located in D:\workspace\eDEP. The source on RADE2 is out of date.

A shared directory F:\TCAS is available for easy copying between the PCs.

The ‘Hummingbird Neighbourhood’ provides an easy ftp interface to hflab1.

The previous version of eDEP was installed in D:\TCAS2004. This is imminently obsolete.

The batch files on RADE1 must specify the absolute path for Java – the installation of Eclipse put in a different version and running the default version causes an incorrect version error. There is something referenced in the registry which can be updated to solve this problem. An alternative batch file (.._path.bat) does this. This has not been copied to other machines for the moment, so they remain flexible, although java is unlikely to be upgraded to cause any issues.

15.2 HFLAB (LINUX) MACHINESThe simulation is installed in ~/edep/RADE2005 (i.e. /home/edep/edep/RADE2005).

This directory contains all the launch script files and the directories log, rec and products.

The products directory contains all the jar files.

The launch script files redirect output to log files in the directory log.

The rec directory is intended to hold CWP recordings. It has two sub-directories, CWP and SME for recordings from the respective positions.

See notes in the previous section about jar naming, and launch file updates.

The previous version of eDEP was installed in ~/edep/TCAS2004. The previous version of eDEP used in standalone for scenario development was installed in ~/edep/eDEP_TCAS. These are imminently obsolete.

15.3 CONFIGURATION ISSUESAT THE TIME OF WRITING THE DESKTOP ICONS LAUNCH THE PREVIOUS VERSION.

of 38



Currently both platform configurations have the same ACAS server settings – they cannot be run in parallel and both connect.

On the ACAS server machine, currently the ExerciseConfiguration link in PhaseB/simulation/Rade2/ needs to point at the appropriate ExerciseConfiguration.RADEn file according to the PC hosting the simulation engine.

of 38



16 LAUNCHING THE SAT

This section details how to launch the SAT.

16.1 REQUIRED SOFTWAREThe SAT is launched via the SAT.bat file. The SAT.jar and StoriaManagementAPI.jar, file must be placed in the directory from which the SAT is to be launched. The following jar files should be placed in the locations specified below:

jaxp\xercesImpl.jar

jaxp\dom.jar

jdom\build\jdom.jar

Chart2D\Chart2D.jar

The directory structure is illustrated in Figure 14, below.

Figure 14 Required Directory Structure

of 38



16.2 LOCATING THE XML DATA

Figure 15 SAT

The XML file to be loaded into the SAT must be placed in the following location:

<<Users home directory>>/Simulations/<<Simulation Name>>/Exercises

In the Figure 15, above, the RADL_A2.xml XML file is located in:

F:\Documents and Settings\rob\Simulations\TCAS\Exercises.

16.3 LOCATING THE XML SCHEMAThe STORIA grammar, the XML schema against which the XML data is validated should be positioned in the following location:

TBD

of 38



17 CWP RAS – EDEP FOR RADE-2 (WHEN CONNECTED TO ACAS SERVER)

No. ACAS Server RA Abbr.eDEP symbol

Word TCAS followed by

PWP

Up Advisory

2 CLIMB_CLIMB CLM TCAS Climb

3 CLIMB CLM TCAS Climb

4 CROSSING_CLIMB CCL TCAS Climb

5 MAINTAIN_CLIMB MCL TCAS Climb

6 CROSSING_MAINTAIN_CLIMB MCC TCAS Climb

7 INCREASE_CLIMB ICL TCAS Climb

8 REVERSAL_CLIMB RCL TCAS Climb

9 REDUCE_DESCEND DDE — TCAS RA

19 ADJUST_VS_DESCEND DDE — TCAS RA

Down Advisory

11 DESCEND_DESCEND DES TCAS Descent

12 DESCEND DES TCAS Descent

13 CROSSING_DESCEND CDE TCAS Descent

14 MAINTAIN_DESCEND MDE TCAS Descent

15 CROSSING_MAINTAIN_DESCEND MCD TCAS Descent

16 INCREASE_DESCEND IDE TCAS Descent

17 REVERSAL_DESCEND RDE TCAS Descent

18 REDUCE_CLIMB DCL — TCAS RA

10 ADJUST_VS_CLIMB DCL — TCAS RA

Other

0 NO_ADVISORY -- None None

1 CLEAR_OF_CONFLICT COC None None

20 MONITOR_VERTICAL_SPEED_MVS MVS [blank]1 TCAS RA – NO ACTION

21 MONITOR_VERTICAL_SPEED MVS [blank]2 TCAS RA – NO ACTION

1 Just the word “TCAS”, no symbol next to it. 2 Just the word “TCAS”, no symbol next to it.

of 38



18 CWP RAS – EDEP FOR RADE-2 (NO ACAS SERVER, NON-INTERACTIVE SCENARIOS)

Abbr. RA Aural (cockpit)eDEP symbol Word TCAS followed by

Up Advisory

CLM Climb Climb (x2)

DDE Don’t descend Adjust vertical speed, adjust —

LD5 Limit descend to 500 ft/min Adjust vertical speed, adjust —



CCL Crossing climb Climb, crossing climb (x2)

ICL Increase climb Increase climb (x2)

RCL Reversal climb Climb, climb now (x2)

MCL Maintain climb Maintain vertical speed, maintain

MCC Maintain crossing climb Maintain vertical speed, crossing maintain

Down Advisory

DES Descend Descend (x2)

DCL Don’t climb Adjust vertical speed, adjust —

LC5 Limit climb to 500 ft/min Adjust vertical speed, adjust —



CDE Crossing descend Descend, crossing descend (x2)

IDE Increase descend Increase descend (x2)

RDE Reversal descend Descend, descend now (x2)

MDE Maintain descend Maintain vertical speed, maintain

MCD Maintain crossing descend Maintain vertical speed, crossing maintain

Other

MVS Monitor vertical speed Monitor vertical speed [blank]3

TA Traffic advisory Traffic (x2) None

COC Clear of conflict Clear of conflict None

3 Just the word “TCAS”, no symbol next to it.

of 38



of 38