TCAS_CTSD.doc
Page : 1 /

EUROCONTROL EXPERIMENTAL CENTRE

Brétigny-sur-Orge, FRANCE

TCAS

Technical Document

Test Scripts

Document Ref: TEC/<Activity/<No>/<Release<Draft>/<Author>

Issue date: 21 February 200829 January 200813 September 2007

<Preface>

The information contained in this document is the property of the EUROCONTROL Agency and no part should be reproduced in any form without the Agency’s permission.

The views expressed herein do not necessarily reflect the official views or policy of the Agency.

Document Change Log
Rel. / Author / Date of the release / Description of the release / Modifications (sections affected and relevant information)
0.1 / Graffica (Aynsworth) / Sept 2003 / Created
0.2 / Graffica (Aynsworth) / April 2004 / Added MP3, air and ILS tests.
0.3 / Graffica (Aynsworth) / 23rd June 2004 / Added TCAS Server tests.
0.4 / Graffica (Murillo) / 21st Dec 2004 / Updated TCAS Server test
0.5 / Graffica (Cooper / 15th Apr 2005 / Removed observations.
Added unique scenario ids.
0.6 / Graffica (Aynsworth) / 22nd Sept 2005 / Updated TCAS_TEST1
0.7 / Graffica (Isherwood) / 29th Jan 2008 / Updated TCAS_AIR_Test1
0.8 / Graffica (Isherwood) / 21st Feb 2008 / Updated TCAS_HMI_Test1
Acceptance and Reviewing Procedures
Name (s) / Date of acceptance/ review / Date of approval
Document distribution
to/cc / Name / Role

Table of contents

1Introduction

1.1Purpose

1.2Intended audience

1.3Responsibilities

1.4Associated documentation

1.4.1Internal project documentation

1.4.2General documentation

1.5Glossary

2airspace

2.1General

3test environment

3.1Related Documents

3.2File Structure

3.3Launcher HMI

4TCAS MOde Tests

4.1Datalink Mode

4.1.1Datalink Updates

4.2Radar Mode

4.2.1Radar Mode 6 Second Update

4.2.2Radar Mode 4 Second Update

5DISTRIBUTION Tests

5.1Distribution Test

5.1.1Distribution Test

6HMI VARIANT Tests......

6.1Extreme HMI

6.1.1TCAS Extreme HMI Variant

6.2Extreme No Haptic

6.3Intermediate HMI

6.4Minimum HMI

6.5EATMP HMI

6.6Customised HMI

7HAPTIC ALARM Tests

7.1Haptic Alarm Test

7.1.1Extreme HMI and Uninstalled parport.dll

7.1.2Extereme_No_Haptic HMI and Uninstalled parport.dll

7.1.3HMI with No Haptic and Uninstalled parport.dll

8MP3 Player Tests

8.1MP3 Tests

9Air Configuration Test

10ILS Capability

10.1Automatic ILS Lock On

10.2Manual ILS Lock On

11TCAS Server Connection

Index of figures

Index of tables

STATUSTITLE

Company Ref. Template : tec01.dot

TCAS_CTSD.doc
Page : 1 /

1 Introduction

1.1 Purpose

This document contains tests for the eDEP TCAS subsystem.

1.2 Intended audience

This document is of interest to all eDEP developers.

1.3 Responsibilities

The eDEP EEC and Graffica project managers are responsible for updating this document.

1.4 Associated documentation

1.4.1 Internal project documentation

Title / Reference / Date
EDEP Acceptance Plan (STP) / V0.3

1.4.2 General documentation

Title / Authors / Date

1.5 Glossary

2 airspace

2.1 General

The same airspace (Sectors/Units, routes, SIDs, STARs and Agrrements) as the eDEP component test specifications will be used.

3 test environment

3.1 Related Documents

The eDEP Software Test Plan defines the high level test cases.

3.2 File Structure

The tests are found within

<eDEP root>/TCAS/src/tcas/resources/scenarios

3.3 Launcher HMI

The tests will be initiated via the TCAS Launcher configuration. In the distributed tests both The TCAS Launcher configuration and the TCASVVC configuration will be used.

4 TCAS MOde Tests

4.1 Datalink Mode

4.1.1 Datalink Updates

Scenario ID / TCAS_Datalink_Test1
Tested Functionality
Objective / In this test the scenario will progress with the aircraft labels updated on every datalink update (i.e. typically every second).
Resource File / <test home>/TCASTest1/TCASTest1.gsdk

Test Scenario:

ID / Time / Actions / Expectations
From Launcher, select:
  1. Datalink from Event Dispatch Mechanism list
  2. ‘Extreme No Haptic’ from HMI Variant.
Run TCAS Scenario.
Observe Flight CNF001
16:19:16 /
  1. FL 311
  2. A TCAS advisory is displayed in the aircraft label.
  3. The TCAS advisory is displayed in a yellow foreground against a black background.

16:19:17 / FL 310
16:19:18 / FL 311
16:19:19 / FL 312
16:19:20 / FL 312
16:19:21 / FL 311
16:19:22 / FL 313
16:19:23 / FL 319
16:19:24 / FL 314
16:19:25 / FL 315
16:19:26 / FL 315
16:19:27 / FL 316
16:19:28 / FL 316
16:19:29 / FL 317
16:19:30 / FL 317
16:19:31 / FL 318
16:19:32 / FL 318
16:19:33 / FL 319
16:19:34 / FL 319
16:19:35 / FL 320
16:19:36
-> . . . / FL 320
Repeat the test with IAS.FLY_TRAJECTORY AIRCRAFT

4.2 Radar Mode

4.2.1 Radar Mode 6 Second Update

Scenario ID / TCAS_RADAR_Test1
Tested Functionality
Objective / In this test the scenario will progress with the aircraft labels updated on every radar update (i.e. every 6s).
Resource File / <test home>/TCASTest1/TCASTest1.gsdk

Test Scenario:

ID / Time / Actions / Expectations
From Launcher:
Use default Radar update Interval (6s).
Select ‘Extreme No Haptic’ HMI Variant.
Run TCAS Scenario.
Observe Flight CNF001
16:19:16
->
16:19:36 / Same expectations as Datalink but aircraft label will only be updated on the 6-second update boundary.

4.2.2 Radar Mode 4 Second Update

Scenario ID / TCAS_RADAR_Test2
Tested Functionality
Objective / In this test the scenario will progress with the aircraft labels updated on every radar update (i.e. every 4s).
Resource File / <test home>/TCASTest1/TCASTest1.gsdk

Test Scenario:

ID / Time / Actions / Expectations
From Launcher:
Select Radar update Interval of 4s.
Select ‘Extreme No Haptic’ HMI Variant.
Run TCAS Scenario.
Observe Flight CNF001
16:19:16
->
16:19:36 / Same expectations as Datalink but aircraft label will only be updated on the 4-second update boundary.

5 DISTRIBUTION Tests

5.1 Distribution Test

5.1.1 Distribution Test

Scenario ID / TCAS_DIST_Test1
Tested Functionality
Objective / In this test the two machines are required. The first machine will act as the Simulation Engine (SE) and the second to run the voice and vibration subsystem (VV).
The test scripts assume that the SE is named mars.
The test will demonstrate that the software can be run over a distributed system.
Resource File / <test home>/TCASTest1/TCASTest1.gsdk

Test Scenario:

ID / Time / Actions / Expectations
On the SE:
Run the TCAS Launcher configuration.
Select:
-Scenario TCASTest1
-Variant Extreme_No_Haptic
-Appropriate display
-run remote VVC
On the SE:
Run TCAS Scenario / GSDK Control console appears.
PVD appears.
No mention of VVC appears in the SE Eclipse Console log other than the report that the VVC has been removed from the components.
On the VV:
Run the TCASVVC configuration / Note that VV Eclipse Console log show starting application VVC.
Note that the SE Eclipse Console log shows
“Discovery: registering [VVC. . .”
On the SE PVD check resources. Discovery_host will be mars and use_discovery_server will be true.
On the SE:
Play scenario. / Scenario will play with PVD updating on SE and the VV machine playing the audio.

6 HMI VARIANT Tests

6.1 Extreme HMI

6.1.1 TCAS Extreme HMI Variant

Scenario ID / TCAS_HMI_Test1
Tested Functionality
Objective / This test will progress illustrating:
  1. Aircraft labels indicating TCAS and advisory direction.
  2. Alert window indicating TCAS and advisory direction.
  3. TCAS audio alert
  4. TCAS haptic alert.

Resource File / <test home>/TCASTest1/TCASTest5.gsdk

Test Scenario:

ID / Time / Actions / Expectations
On TCAS Scenario Launcher select:
-Scenario TCASTest5.
-Variant Extreme.
-Appropriate display
Run TCAS Scenario / eDep Control console appears.
PVD appears
Fast Forward / Aircraft BAW002 and CNF001 appear on PVD at approx 16:12:10 with MTCD red dot in label.
16:17:40 / Select real time.
All following times are approx / The predicted expectations will appear on first update of track within the time period specified.
16:19:15
->
16:19:34 / Audible TCAS “TCAS TCAS” alarm sounded.
Haptic alarm vibrates for 10s.
CNF001 Label shows “TCAS CLM” an ‘up’ arrow text flashing on red background.
TCAS alert for CNF001 appears in Alert window indicating text as shown in label.
BAW002 label is boxed in red.
16:19:35 -> 16:19:46 / CNF001 label now shows an ‘up’ arrow “TCAS ICL”.
16:19:47
->
16:20:22 / CNF001 label now shows an ‘up’ arrow “TCAS LC1”.
16:20:23
->
16:2032 / CNF001 label initially shows a down “TCAS DES(LC1)” before changing to “TCAS DES”.arrow
16:20:42
-> / TCAS alert removed from label.
TCAS alert removed from alert window.

6.2 Extreme No Haptic

As Extreme HMI but select Extreme_No_Haptic as variant. Expectations will be the same as Extreme HMI but no haptic alarm will be activated.

6.3 Intermediate HMI

As Extreme_No_Haptic but select Intermediate variant. Expectations will be the same but no TCAS audio alert will be sounded.

6.4 Minimum HMI

As Intermediate HMI but select Minimum variant. Expectations will be the same but the TCAS direction advisory (i.e. CLM, DES etc) will not be displayed in the label or in the Alert window.

6.5 EATMP HMI

As Minimum HMI but select EATMP variant. No TCAS information will be displayed in the label. Neither will it be displayed in the Alert window.

6.6 Customised HMI

When selecting the Customised HMI a tab pane will appear on the Launcher allowing the user to select or deselect individual elements. For example the user will be able to select the repetitive nature of the audio and haptic alarms (i.e. single or continuous alarms).

7 HAPTIC ALARM Tests

7.1 Haptic Alarm Test

7.1.1 Extreme HMI and Uninstalled parport.dll

Scenario ID / TCAS_HAPTIC_Test1
Tested Functionality
Objective / To illustrate that the Haptic alarm variant can only be run if the parport.dll is installed. Typically parport.dll will be installed in c:/jsdk1.4.0_01/bin.
Resource File / <test home>/TCASTest1/TCASTest5.gsdk

Test Scenario:

ID / Time / Actions / Expectations
Rename parport.dll to XXXparport.dll
Run TCAS Launcher
Select:
- Scenario:TCASTest5
-Variant: Extreme
- Appropriate Display
Run TCAS Scenario / Exception raised specifying:
Caused by: java.lang.UnsatisfiedLinkError: no parport in java.library.path
Rename XXXparport.dll to parport.dll

7.1.2 Extereme_No_Haptic HMI and Uninstalled parport.dll

Scenario ID / TCAS_HAPTIC_Test2
Tested Functionality
Objective / To illustrate that the Extreme HMI can be run by specifically excluding the Haptic alarm when the Parport.dll is not installed.
Resource File / <test home>/TCASTest1/TCASTest5.gsdk

Test Scenario:

ID / Time / Actions / Expectations
Rename parport.dll to XXXparport.dll
Run TCAS Launcher
Select:
- Scenario: TCASTest5
- Variant: Extreme_No_Haptic
- Appropriate: Display
Run TCAS Scenario / Scenario progresses as described in HMI Variant section.
Rename XXXparport.dll to parport.dll

7.1.3 HMI with No Haptic and Uninstalled parport.dll

Scenario ID / TCAS_HAPTIC_Test3
Tested Functionality
Objective / To illustrate that any HMI variant that does not include the Haptic alarm can be run when the parport.dll is not installed.
Resource File / <test home>/TCASTest1/TCASTest5.gsdk

Test Scenario:

ID / Time / Actions / Expectations
Rename parport.dll to XXXparport.dll
Run TCAS Launcher
Select:
- Scenario: TCASTest5
- Variant: Intermediate
- Appropriate: Display
Run TCAS Scenario / Scenario progresses as described in HMI Variant section.
Rename XXXparport.dll to parport.dll

8 MP3 Player Tests

8.1 MP3 Tests

Scenario ID / TCAS_MP3_Test1
Tested Functionality
Objective / To demonstrate that the platform is capable of:
  • playing mp3 files on both Windows and Linux systems.
  • playing mp3 files as either scripted events or as STCA/TCAS alerts.
  • playing wav files on both Windows and Linux systems.
  • playing wav files as either scripted events or as STCA/TCAS alerts.
  • stopping at a specified time.

Resource File / <test home>/TCASTest1/TCASTest1.gsdk

Test Scenario:

ID / Time / Actions / Expectations
1 / Set HMI Variant to ‘Extreme No Haptic’
Launch the platform
2 / 16:12:10 / The sound of an approaching train is heard.
3 / 16:15:10 / An announcement concerning Air Force 936 is played.
4 / 16:16:30 / An announcement concerning Air Force 936 is played.
5 / 16:19:10 / A short ice hockey commentary clip is played when a TCAS alert occurs.
6 / 16:20:00 / The platform shutsdown.
7 / Repeat this test on a Linux platform.

9 Air Configuration Test

Scenario ID / TCAS_AIR_Test1
Tested Functionality / Air configuration and User Requirement 4.
Objective / To demonstrate that the platform offers both Controller Working Position and Pilot Working Positions.
Resource File / <test home>/TCASTest2/TCASTest2.gsdk

Test Scenario:

ID / Time / Actions / Expectations
1 / Launch the platform in Combined platform in datalink mode.mode and select datalink /
  1. A CWP appears.
  2. A PWP appears.

2 / 16:12:30 / PWP CNF001 CFL 330 / CNF001 climbs to FL3330.

10 ILS Capability

10.1 Automatic ILS Lock On

Scenario ID / TCAS_ILS_Test1
Tested Functionality / User Requirement 5: ILS Capability
User Requirement 12: SIDs and STARs.
Objective / To demonstrate that the platform:
  • offers an ILS landing capability
  • the ILS may be locked on to automatically.

Resource File / <test home>/TestSIDsSTARs/TestSIDsSTARs.gsdk

Test Scenario:

ID / Time / Actions / Expectations
1 / Launch the platform.
2 / 17:00:30 /
  1. STAR111 appears.

3 / 17:01:47 /
  1. STAR111 starts to descend to FL100

4 / 17:15:04 /
  1. STAR111 reaches FL100.

5 / 17:15:00 /
  1. STAR111 starts to descend to FL20.

6 / 17:22:00 /
  1. STAR111 reaches FL20.

7 / Bring up extended label window. /
  1. ELW is displayed.
  2. Ground speed = 320 knots.

8 / 17:24:00 /
  1. MESSAGE ILSEnabledPMControllerImpl: executeILSLanding: STAR111 Executing ILS Landing is displayed in console.

9 / 17:25:00 /
  1. STAR111 commences approach.

10 / 17:25:33 /
  1. STAR111 ground speed 150 knots
  2. STAR111 altitude 1300 feet.

11 / 17:27:20 /
  1. STAR111 lands and is removed from the scenario.

10.2 Manual ILS Lock On

Scenario ID / TCAS_ILS_Test2
Tested Functionality / User Requirement 5: ILS Capability
User Requirement 12: SIDs and STARs.
Objective / To demonstrate that the platform:
  • offers an ILS landing capability
  • the ILS may be locked on to manually.
The test should be repeated
  • ILS lock on manual: intercept ILS in PWP
  • ILS lock on manual: do not intercept ILS in PWP.
It is necessary to set the FPM.AUTOMATIC_ILS_LOCKON resource to false for this test. This resource is commented out in the configuration file.
It may also be necessary to modify the TCAS launcher in order that it does not remove the PWP from the set-up. The PWP is required to instruct the flights to lock on.
Resource File / <test home>/TestSIDsSTARs/TestSIDsSTARs.gsdk

Test Scenario:

ID / Time / Actions / Expectations
1 / Launch the platform.
2 / 17:00:30 /
  1. STAR111 appears.

3 / 17:01:47 /
  1. STAR111 starts to descend to FL100

4 / 17:15:04 /
  1. STAR111 reaches FL100.

5 / 17:15:00 /
  1. STAR111 starts to descend to FL20.

6 / 17:22:00 /
  1. STAR111 reaches FL20.

7 / Bring up extended label window. /
  1. ELW is displayed.
  2. Ground speed = 320 knots.

17:23:00 /
  1. STAR111 PWP Intercept ILS

8a / 17:24:00 /
  1. MESSAGE ILSEnabledPMControllerImpl: executeILSLanding: STAR111 Executing ILS Landing is displayed in console.

9a / 17:25:00 /
  1. STAR111 commences approach.

10a / 17:25:33 /
  1. STAR111 ground speed 150 knots
  2. STAR111 altitude 1300 feet.

11a / 17:27:20 /
  1. STAR111 lands and is removed from the scenario.

8b /
  1. No lock on message is displayed in console.

9b /
  1. STAR111 commences approach.

10b /
  1. STAR111 ground speed remains 320 knots.

11b / 17:27:20 /
  1. STAR111 lands and is removed from the scenario.

Also observer flight STAR222. This flight overflies the airport to fix BOLYN. If the aircraft does not lock onto the ILS, the flight continues to BOLYN. If the flight captures the ILS it lands at the airport.

TCAS Server Connection

Scenario ID / TCAS_ACSG_Test1
Tested Functionality / User Requirement 8: TCAS Server connection
Objective / To demonstrate that the platform:
  • is capable of connecting to the TCAS server;
  • is capable of broadcasting state vector information; and
  • is capable of receiving TCAS advisories.

Resource File / <test home>/Acsg/Acsg.gsdk

Test Scenario:

In the absence of a connection to the real TCAS server, a test TCAS server has been created.

ID / Time / Actions / Expectations
1 / Launch the Test TCAS server.
2 / Launch the eDEP platform.
3 / 08:00:15 /
  1. Flights STC003, STC004 and STC005 appear in the scenario.

4 / 08:00:30 and beyond /
  1. The following debug output is observed, and continues to be observed, in the TCASServer window:
  • wait for datagram packets....
  • Test received data from /192.168.0.12:8888
  • PlumeMtrk message n° 221
  • not last message
  • Received 1 flights
  • CAL: STC003
  • SYS: 0
  • PHI: 0
  • LON: 1.0766073
  • LAT: 51.731564
  • CAP: 0.0
  • TAS: 733.0
  • AFL: 310.0
  • RAT: 0.0
  • HEI: 0.0
  • ROL: 0.0
  • MAB: 0
  • MC: 0
  • DUM: 0

5 / Dummy RAs are received from the TCASServer, the advisories are displayed in the report button in the PWP and in the labels in the CWP.
The display of RAs in the CWP is synchronised with the radar sweeps.

STATUSTITLE

Company Ref. Template : tec01.dot