Ads-B As680 Thales

Reference No.
83140 56221
Draft Version
ADS−B
Automatic Dependent Surveillance Broadcast
ADS−B Ground Station

AS 680/682
and RCMS
Technical Manual
Description, Operation and Maintenance
Draft
As for details, the electrical and mechanical information given in the

documentation supplied with each equipment prevails
All rights reserved

E 2007
Thales ATM GmbH
Stuttgart
Printed in Germany
ADS−B AS 680/682
Documentation Structure
ADS–B Ground Station AS 680/682
The Description, Operation and Maintenance Manual of the

ADS–B Ground Station AS 680/682 and RCMS, comprises:
Part Technical Manuals Code No.

− Description, Operation and Maintenance 83140 56221
The Description, Operation and Maintenance Manual contains the complete description of operation
and maintenance actions of the ADS–B Ground Station AS 680/682 and RCMS. It describes the func-
tions, subsystems and the set–up of the ADS–B system.
Ed. 10.07
ADS−B AS 680/682
Description, Operation and Maintenance Preliminary Remarks
PRELIMINARY REMARKS
The technical manual for the AS 680/682 ADS−B Ground Station comprises:
PART CONTENTS CODE NO.

Description, Operation, Maintenance 83140 56221
This Technical Manual contains the Description, Operation and Maintenance with the following
chapters:
1 System Description
2 Subsystem Description
3 Installation and Setup
4 Use of LCMS/RCMS Application Software
5 Supervisor Operation
6 Monitor User Operation
7 Maintenance, Fault Location and Repair
8 Basic Installation of LCMS and RCMS
Since it is not possible to include modifications, such as those which may be made to circuitry details
or dimensioning in the interests of technical progress, in the Technical Manual, we should point out
that questions of detail should always be answered using the technical documentation supplied with
the system. It is possible that drawing numbers used in this description are no longer contained in
the set of drawings supplied, but rather than (to conform with the system) they have been replaced
by new drawings with another number. Please carry out a once−only check on the basis of delivery
list supplied and exchange where appropriate.
MARK SYMBOLS
To get the best out of the equipment you should study the contents of this manual carefully. In particu-
lar you should familiarize yourself with the marks given in this manual which are highlighted for easy
recognition:
CAUTION WARNING
Cautions call attention to methods Warnings call attention to methods,

and procedures which must be procedures or limits which must be
followed to avoid damage to followed precisely to avoid injury to
equipment. persons.
NOTE or REMARK : For more information about operations.
Ed. 10.07 A
AS 680/682 ADS−B
Preliminary Remarks Description, Operation and Maintenance
Table of effective pages

Basic edition: 10.07 (Draft Version)
Pages Ed. Remarks
Title 10.07
A to B 10.07
I to XXII 10.07
AV−1 to 2 10.07
1−1 to 8 10.07
2−1 to 28 10.07
3−1 to 34 10.07
4−1 to 86 10.07
5−1 to 50 10.07
6−1 to 2 10.07
7−1 to 26 10.07
8−1 to 18 10.07
Trademarks: Microsoft and MS−DOS are registered trademarks, WINDOWS is a trademark of the Microsoft Corporation. IBM is a registered trademark of the International
Business Machines Corporation. Pentium is a registered trademark of the Intel Corporation. All other mentioned product names may be trademarks of the
respective manufacturers and must be observed.
Note Despite careful editing work technical inaccuracies and printing faults cannot be excluded in this publication. Change of text remains reserved without notification.
B Ed. 10.07
ADS−B AS 680/682
Description, Operation and Maintenance Table of Contents
TABLE OF CONTENTS
Section Title Page
CHAPTER 1 SYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−1

1.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−1
1.1.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−2
1.2 SYSTEM COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−3
1.3 TECHNICAL CHARACTERISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−5
1.3.1 Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−5
1.3.2 Peripheral Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−5
1.3.3 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−5
1.3.4 Environmental Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−5
1.3.5 System Data Ground Station AS 680/682 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−6
1.3.5.1 Signal Processing Unit (SPU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−6
1.3.6 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−6
1.3.7 Conformity and Licensing Approval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−6
1.4 GENERAL SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−7
1.4.1 Observation of Safety Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−7
1.4.2 Maintenance Operation at the Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−7
1.4.3 Handling Subassemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−7
1.4.4 Using Lithium Batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−7
1.4.5 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−8
1.4.6 Observation of Safety Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−8
CHAPTER 2 SUBSYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−1

2.1 ADS−B GROUND STATION AS 680 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−1
2.1.1 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−1
2.1.2 Physical Breakdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−2
2.1.3 External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−2
2.1.4 Signal Processing Unit (SPU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−4
2.1.4.1 Receiver Unit (RXU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−6
2.1.4.2 GPS Timing System (GTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−6
2.1.4.3 Signal Processing Board (SPB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−8
2.1.4.3.1 Definition of front Connectors J3 to J6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−9
2.1.4.4 Single Board Computer (SBC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−10
2.1.4.5 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−12
Ed. 10.07 I
AS 680/682 ADS−B
Table of Contents Description, Operation and Maintenance
Section Title Page
2.1.4.6 Fan Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−12

2.1.5 Site Monitor (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−13
2.1.6 Rack Integration example of the AS680 Ground Station . . . . . . . . . . . . . . 2−14
2.2 ADS−B GROUND STATION AS 682 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−15
2.2.1 Physical Breakdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−15
2.2.2 Data Switch, 16 Port Gigabit Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−17
2.2.3 Exchange Panel 4/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−17
2.2.4 Uninterruptible Power Supply (UPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−17
2.2.4.1 Controls and Display Function of Base Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−17
2.3 PERIPHERAL EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−21
2.3.1 Omnidirectional Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−21
2.3.2 Antenna Amplifier Unit (AAU) with mounting Kit and Weather Protection 2−21
2.3.3 GPS Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−22
2.4 REMOTE/LOCAL CONTROL AND MONITORING SYSTEM (RCMS/LCMS) . 2−23
2.4.1 Technical System Control (TSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−25
2.4.2 Technical Situation Display (TSD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−26
2.4.3 Recording and Replay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−27
2.4.4 Raw Data to Asterix Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−28
CHAPTER 3 INSTALLATION AND SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−1

3.1 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−1
3.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−1
3.1.2 Hardware Items for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−1
3.1.2.1 Ground Station AS 680 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−1
3.1.3 Hardware Items for RCMS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−2
3.1.4 Ground Station System Cabling Set Definition . . . . . . . . . . . . . . . . . . . . . . 3−3
3.1.5 Interconnection of System Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−5
3.1.6 Mounting Requirements and Recommendations . . . . . . . . . . . . . . . . . . . . 3−9
3.1.6.1 Installation Notes to Ground Station (RXU) and Antenna Amplifier Unit . . . . 3−9
3.1.6.2 Installing the ADS−B Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−9
3.1.6.3 Installing the Antenna Amplifier Unit (AAU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−9
3.1.6.4 Installing the GPS Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−10
II Ed. 10.07
ADS−B AS 680/682
Section Title Page
3.1.6.5 Performing the Outdoor Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−10

3.1.6.6 Installing the Indoor Equipment Ground Station AS 680, Site Monitor . . . . . 3−10
3.1.6.6.1 Installing the Cabling within the Shelter or Building (AS 680) . . . . . . . . . . . . . 3−11
3.1.6.7 Installing the Indoor Equipment Ground Station AS 682 . . . . . . . . . . . . . . . . . 3−12
3.1.6.7.1 Installing the Cabling within the Shelter or Building (AS 682) . . . . . . . . . . . . . 3−12
3.1.6.8 Final Installation Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−13
3.2 SWITCHING ON GROUND STATION ON SITE . . . . . . . . . . . . . . . . . . . . . . . . . 3−15
3.2.1 Status of Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−15
3.2.2 Status of the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−15
3.2.3 Uninterruptible Power Supply (UPS), Startup and Operation . . . . . . . . . . 3−15
3.2.4 Switch On Ground Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−16
3.2.5 Check and Adjustment of the GS Receiver Frequency (RXU) . . . . . . . . . . 3−16
3.2.6 Adjustment of the SPU/RXU Receiver Sensitivity Level . . . . . . . . . . . . . . . 3−17
3.2.7 Initial Ground Station Settings AS 680 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−19
3.2.8 Site Monitor Settings AS 680 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−19
3.2.9 Initial Ground Station Settings AS682 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−20
3.2.10 Site Monitor Settings AS682 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−20
3.3 STARTING THE RCMS AT REMOTE SITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−21
3.4 CONFIGURATION OF RCMS/LCMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−22
3.4.1 Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−22
3.4.2 Site−specific Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−22
3.5 FURTHER TSC CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−23
3.5.1 User Role Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−23
3.5.2 Runtime Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−24
3.5.2.1 Settings File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−24
3.5.2.1.1 Starting Settings File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−24
3.5.3 Ground Station List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−24
3.6 SITE VERIFICATION TEST PROCEDURE AND INSTALLATION REPORT . . 3−27
3.6.1 Serial Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−27
3.6.2 Mechanical Setup of Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−27
3.6.2.1 ADS−B Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−27
3.6.2.2 Antenna Amplifier Unit (AAU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−27
3.6.2.3 GPS Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−27
3.6.2.4 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−27
Ed. 10.07 III

AS 680/682 ADS−B
Section Title Page
3.6.3 Electrical Connection of AAU, SPU, Site Monitor, active GPS Antenna . . 3−28
3.6.4 RF properties of Antenna cables and Receiver adjustment . . . . . . . . . . . . 3−28
3.6.5 Configuration of Site Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−28
3.6.6 Configuration of Ground Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−30
3.6.7 Network Connection to RCMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−31
3.6.8 Site Installation Report (SIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−31
CHAPTER 4 USE OF LCMS/RCMS APPLICATION SOFTWARE . . . . . . . . . . . . . . . . . . . . . . 4−1

4.1 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−1
4.2 TECHNICAL SYSTEM CONTROL (TSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−3
4.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−3
4.2.2 Starting the TSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−3
4.2.3 Operation of the TSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−3
4.3 MASTER TECHNICAL SYSTEM CONTROL (MTSC) . . . . . . . . . . . . . . . . . . . . . 4−5
4.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−5
4.3.2 Structure of the MTSC GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−5
4.3.2.1 MTSC Main Window on Screen 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−6
4.3.2.1.1 Event Window on Screen 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−7
4.3.2.2 Detailed Status Window on Screen 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−7
4.3.2.2.1 Menubar of Detailed Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−8
4.3.2.2.2 BITE Panel of Detailed Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−9
4.3.2.2.3 BITE File Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−9
4.3.2.2.4 Statusbar of Detailed Status Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−9
4.3.3 Supervisor Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−10
4.3.3.1 Menubar of Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−10
4.3.3.2 Toolbar of Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−12
4.3.3.3 Map Panel of Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−12
4.3.3.3.1 Map Menu of Map Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−12
4.3.3.3.2 GS Menu of Map Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−15
4.3.4 Monitor User Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−16
4.3.4.1 Menubar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−16
4.3.4.2 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−16
4.3.4.3 Map Panel of Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−16
4.3.4.3.1 Map Menu of Map Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−16
4.3.4.3.2 GS Menu of Map Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−16
IV Ed. 10.07
ADS−B AS 680/682
Section Title Page
4.4 ADS−B TOOLS: TECHNICAL SITUATION DISPLAY (TSD) . . . . . . . . . . . . . . . 4−17

4.4.1 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−17
4.4.2 Menubar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−19
4.4.2.1 Menu ’File’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−19
4.4.2.2 Menu ’Map Items’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−20
4.4.2.3 Menu ’Markings’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−20
4.4.2.4 Menu ’Display’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−21
4.4.2.5 Menu ’Tracks’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−21
4.4.2.6 Menu ’Preferences’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−23
4.4.2.6.1 Information Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−23
4.4.2.6.2 GS Filter Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−23
4.4.2.6.3 PA Filter Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−24
4.4.2.6.4 View Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−24
4.4.2.6.5 Interface Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−25
4.4.2.7 Menu ’Help’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−25
4.4.2.8 About Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−26
4.4.2.9 Short Reference Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−26
4.4.3 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−27
4.4.4 Detailed Target View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−28
4.4.5 Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−29
4.4.5.1 Map View Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−29
4.4.5.2 Target Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−31
4.4.5.3 Ground Station Distance Circle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−32
4.4.5.4 Flight Level Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−33
4.4.6 Statusbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−34
4.5 DISPLAY CONFIGURATION TOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−35
4.5.1 Titlebar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−35
4.5.2 Menubar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−35
4.5.2.1 Menu ’File’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−36
4.5.2.2 Menu ’Help’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−37
4.5.3 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−37
4.5.4 Configuration Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−38
4.5.5 Parameter Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−38
4.5.5.1 Change of Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−39
Ed. 10.07 V
AS 680/682 ADS−B
Section Title Page
4.5.5.2 Addition and Deletion of List Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−40

4.5.6 Statusbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−41
4.5.7 Parameter Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−41
4.5.7.1 DisplayConfig Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−41
4.5.7.2 Window Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−42
4.5.7.3 Refltf Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−43
4.5.7.4 ltfParameter Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−43
4.5.7.5 RefGS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−44
4.5.7.6 Ground Station Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−44
4.5.7.7 Display Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−46
4.5.7.8 Delay Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−47
4.5.7.9 Grid Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−47
4.5.7.10 Speed Vector Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−48
4.5.7.11 Compass Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−49
4.5.7.12 FLPanel Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−49
4.5.7.13 Marking Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−50
4.5.7.14 Detail Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−50
4.5.7.15 Plot and Label Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−51
4.5.7.16 Map Items Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−52
4.6 ADS−B TOOLS: RECORD AND REPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−53
4.6.1 Starting the Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−53
4.6.2 General Structure of the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−53
4.6.2.1 Titlebar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−55
4.6.2.2 Menubar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−55
4.6.2.2.1 Menu ’File’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−55
4.6.2.2.2 Menu ’Command’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−55
4.6.2.2.3 Menu ’Help’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−56
4.6.2.3 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−57
4.6.2.3.1 Toolbar Record Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−57
4.6.2.3.2 Toolbar Replay Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−57
4.6.2.4 Notebook Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−58
4.6.2.4.1 Page ’Top’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−58
4.6.2.4.2 Page ’Screen Output’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−58
4.6.2.5 Statusbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−59
VI Ed. 10.07
ADS−B AS 680/682
Section Title Page
4.6.3 ADS−B Raw Data Record Tool (RRC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−60

4.6.3.1 RRC Notebook Page ’Parameter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−60
4.6.3.1.1 RRC Parameter: Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−60
4.6.3.1.2 RRC Parameter: Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−60
4.6.3.1.3 RRC Parameter: Logging Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−61
4.6.3.1.4 RRC Parameter: File Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−62
4.6.3.1.5 RRC Parameter: Automatic File Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−63
4.6.3.1.6 RRC Parameter: Log Buffering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−63
4.6.3.2 RRC Notebook Page ’Filter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−64
4.6.4 ADS−B Replay Raw Data Send Raw Data Tool (RRP) . . . . . . . . . . . . . . . . 4−65
4.6.4.1 RRP Notebook Page ’I/O Parameter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−65
4.6.4.1.1 RRP I/O Parameter: Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−66
4.6.4.1.2 RRP I/O Parameter: Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−66
4.6.4.1.3 RRP I/O Parameter: Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−66
4.6.4.2 RRP Notebook Page ’Data Parameter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−67
4.6.4.2.1 RRP Data Parameter: Replay Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−67
4.6.4.2.2 RRP Data Parameter: Time Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−68
4.6.4.2.3 RRP Data Parameter: Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−68
4.6.5 ADS−B Replay Raw Data Send Asterix Data Tool (RAC) . . . . . . . . . . . . . . 4−69
4.6.5.1 RAC Notebook Page ’I/O Parameter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−69
4.6.5.1.1 RAC I/O Parameter: Logging to File and Standard Output . . . . . . . . . . . . . . . 4−70
4.6.5.1.2 RAC I/O Parameter: Logging to Screen Output . . . . . . . . . . . . . . . . . . . . . . . . . 4−71
4.6.5.1.3 RAC I/O Parameter: Pipeline Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−72
4.6.5.2 RAC Notebook Page ’Data Parameter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−73
4.6.5.3 RAC Notebook Page ’Trackstore’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−73
4.6.5.4 RAC Notebook Page ’CPR Decoding’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−75
4.6.5.5 RAC Notebook Page ’ASTERIX CAT 21’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−77
4.6.5.5.1 RAC Tool: Help/About Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−78
4.6.6 Record Asterix Data Tool (ARC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−79
4.6.6.1 ARC Notebook Page ’Parameter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−79
4.6.6.1.1 ARC Parameter: Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−79
4.6.6.1.2 ARC Parameter: Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−79
4.6.6.1.3 ARC Parameter: Logging Format/Verbose Mode . . . . . . . . . . . . . . . . . . . . . . . 4−80
4.6.6.2 ARC Notebook Page ’Filter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−80
Ed. 10.07 VII

AS 680/682 ADS−B
Section Title Page
4.6.7 Replay Asterix Data Tool (ARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−81

4.6.7.1 ARP Notebook Page ’I/O Parameter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−81
4.6.7.1.1 ARP I/O Parameter: Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−81
4.6.7.1.2 ARP I/O Parameter: Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−82
4.6.7.1.3 ARP I/O Parameter: Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−82
4.6.7.2 ARP Notebook Page ’Data Parameter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−83
4.7 MISCELLANEOUS TOOLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−85
4.7.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−85
4.7.2 Burning application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−85
4.7.3 Nedit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−85
4.7.4 Minicom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−85
4.7.5 Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−86
4.7.6 Capture Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−86
4.7.7 Image Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−86
4.7.8 PDF Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−86
CHAPTER 5 SUPERVISOR OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−1

5.1 GENERAL DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−1
5.2 STATUSBAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−2
5.3 MENUBAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−3
5.3.1 Menu ’File’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−3
5.3.2 Menu ’Groundstation’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−4
5.3.3 Menu ’Settings’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−4
5.3.4 Menu ’Refresh’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−5
5.3.5 Menu ’Page’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−5
5.3.6 Menu ’About’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−6
5.4 NOTEBOOK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−7
5.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−7
5.4.2 Page ’Overview’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−9
5.4.2.1 Ground Station and User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−9
5.4.2.2 Ground Station Status and Monitoring Information . . . . . . . . . . . . . . . . . . . . . . 5−9
5.4.3 Page ’BITE’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−10
5.4.3.1 BITE Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−11
5.4.3.2 Bite Status (Read Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−12
5.4.3.3 Bite Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−13
VIII Ed. 10.07

ADS−B AS 680/682
Section Title Page
5.4.3.4 Loop Back Telegram Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−14

5.4.3.5 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−14
5.4.4 Page ’Telegram Filter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−15
5.4.5 Page ’Groundstation’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−17
5.4.5.1 Ground Station Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−17
5.4.5.2 Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−17
5.4.5.3 NTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−18
5.4.5.4 Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−18
5.4.6 Page ’Network’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−19
5.4.6.1 Raw Data Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−19
5.4.6.2 Main Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−19
5.4.6.3 Auxiliary Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−19
5.4.6.4 Main and Auxiliary Asterix Data Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−19
5.4.7 Page ’Output’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−20
5.4.7.1 Asterix Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−20
5.4.7.2 Raw Data Optional Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−21
5.4.8 Page ’Telegram Check’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−22
5.4.8.1 Confidence Bits, AP Residuum and Signal Amplitude . . . . . . . . . . . . . . . . . . . 5−22
5.4.8.2 Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−22
5.4.9 Page ’Process’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−23
5.4.9.1 Idle Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−23
5.4.9.2 Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−23
5.4.9.3 HW−Interrupt and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−24
5.4.10 Page ’ADSB’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−24
5.4.10.1 Trackstore and FOM/PA Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−25
5.4.10.2 Asterix Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−25
5.4.10.3 Automatic Data Rate Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−25
5.4.11 Page ’ADSB Filter’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−26
5.4.11.1 Extended Squitter and CPR Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−26
5.4.11.2 Age Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−27
5.4.12 Page ’Site Monitor’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−28
5.4.12.1 Own and other Site Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−28
5.4.12.2 Test Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−28
5.4.13 Page ’Software’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−29
Ed. 10.07 IX
AS 680/682 ADS−B
Section Title Page
5.4.13.1 Current Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−30
5.4.13.2 Flash Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−30
5.4.13.3 Figure of Merit − Position Accuracy Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−30
5.4.13.4 Figure of Merit − Position Accuracy Restriction Table . . . . . . . . . . . . . . . . . . . 5−30
5.4.13.5 Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−31
5.4.13.5.1 Upload Ground Station Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−31
5.4.13.5.2 Upload Ground Station Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−32
5.4.13.5.3 Upload FOM/PA Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−32
5.4.13.5.4 Upload NVRAM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−33
5.4.13.5.5 Upload FOM/PA Restriction Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−34
5.4.13.6 Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−35
5.4.13.6.1 Download NVRAM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−35
5.4.13.6.2 Download FOM/PA Restriction Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−36
5.4.13.7 Restart/Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−37
5.4.13.7.1 Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−37
5.4.13.7.2 Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−38
5.4.13.7.3 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−38
5.4.14 Page ’GPS’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−39
5.4.14.1 GPS Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−39
5.4.14.2 Ground Station Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−39
5.4.14.3 Satellites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−40
5.4.14.4 HPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−40
5.4.14.5 GPS Module Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−40
5.4.14.6 DOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−40
5.4.14.7 GPS Position Deviation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−40
5.4.14.8 GPS and System Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−40
5.4.15 Page ’UPS’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−41
5.4.15.1 UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−41
5.4.15.2 Configuration of SNMP−Card ’CS121 BUDGET’ . . . . . . . . . . . . . . . . . . . . . . . 5−42
5.4.15.2.1 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−42
5.4.15.2.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−42
5.4.15.2.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−44
5.4.16 Page ’Logging’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−49
CHAPTER 6 MONITOR USER OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6−1
CHAPTER 7 MAINTENANCE, FAULT LOCATION AND REPAIR . . . . . . . . . . . . . . . . . . . . . . . 7−1
7.1 PREVENTIVE MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−1
X Ed. 10.07
ADS−B AS 680/682
Section Title Page
7.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−1

7.1.2 Periodic Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−1
7.1.3 Elimination of Static Charges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−1
7.1.4 Damage Check/Visual Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−2
7.1.5 Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−2
7.1.5.1 Cleaning the Dust Filter Mat of the Air Inlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−2
7.1.6 Preventive Exchange of Fan Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−3
7.1.7 Check and Adjustment of SPU/RXU local Oscillator Frequency . . . . . . . . 7−3
7.1.7.1 Adjustment of SPU/RXU Local Oscillator Frequency . . . . . . . . . . . . . . . . . . . . 7−4
7.1.8 Preventive Exchange of the Lithium Battery (SBC) . . . . . . . . . . . . . . . . . . . 7−4
7.1.9 Maintenance of UPS Battery Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−6
7.2 FAULT LOCATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−7
7.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−7
7.2.2 Power Supply, Subsystem Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−7
7.2.3 Performing Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−7
7.2.3.1 Tests if BITE Failure (red) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−8
7.2.3.1.1 GPS Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−8
7.2.3.1.2 Fault in Site Monitor Telegram (own), Site Monitor Bite (own) . . . . . . . . . . . . . 7−8
7.2.3.1.3 Fault in the RF Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−8
7.2.3.2 Tests if no Network Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−9
7.2.3.2.1 If on Site: Check cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−9
7.2.3.2.2 Check Network Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−9
7.2.3.3 Tests if no Raw Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−9
7.2.3.3.1 Check Output Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−9
7.2.3.3.2 Check Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−9
7.2.3.3.3 Check Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−9
7.2.3.4 Tests if no Asterix Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−10
7.2.3.4.1 Check Output Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−10
7.2.3.4.2 Check Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−10
7.2.3.4.3 Check Test Target Report Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−10
7.2.3.4.4 Check Raw Data Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−10
7.3 REPAIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−11
7.3.1 Replacing Subsystems and individual Subassemblies (LRU) . . . . . . . . . . 7−11
7.3.1.1 Replacing Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−12
Ed. 10.07 XI
AS 680/682 ADS−B
Section Title Page
7.3.2 Replacing Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−12

7.3.3 Specific Procedure for Subassemblies of SPU . . . . . . . . . . . . . . . . . . . . . . 7−12
7.3.3.1 Exchange of RXU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−12
7.3.3.2 Exchange of SPB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−13
7.3.3.3 Exchange of SBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−14
7.3.3.4 Exchange of GTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−15
7.3.3.5 Exchange of Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−15
7.3.3.6 Exchange of Fan Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−16
7.3.4 Exchange of Site Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−16
7.3.5 Exchange of UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−16
7.3.6 Exchange of Data Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−16
7.3.7 Exchange of Peripheral Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−17
7.3.7.1 Exchange of AAU (LNA Housing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−17
7.3.7.2 Exchange of ADS−B RX Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−17
7.3.7.3 Exchange of GPS Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−17
7.3.8 List of DIP−FIX−Switches and Jumpers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−19
7.3.8.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−19
CHAPTER 8 BASIC INSTALLATION OF LCMS AND RCMS . . . . . . . . . . . . . . . . . . . . . . . . . . 8−1

8.1 SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−1
8.2 INSTALLATION OF KANGAROO 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−1
8.2.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−1
8.2.2 Start Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−2
8.2.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−3
8.2.4 Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−3
8.3 POST INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−5
8.3.1 Network Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−5
8.3.2 Installation of ADS−B Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−9
8.3.3 Installation of ADS−B Configuration Software . . . . . . . . . . . . . . . . . . . . . . . 8−12
8.3.4 Finishing Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−14
8.4 LOGIN PROCEDURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−15
8.5 ADDITIONAL INSTALLATION INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . 8−16
8.5.1 User/Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−16
8.5.2 Xfce Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−16
8.5.3 Data Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−16
XII Ed. 10.07

ADS−B AS 680/682
Section Title Page
8.5.4 USB Memory Stick Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−17

8.5.5 Network Time Protocol (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−17
Ed. 10.07 XIII

AS 680/682 ADS−B
XIV Ed. 10.07

ADS−B AS 680/682
LIST OF FIGURES
Fig.−No. Title Page
Fig. 1−1 System overview ADS−B, examplary configuration . . . . . . . . . . . . . . . . . . . . . 1−1

Fig. 1−2 ADS−B AS 680, basic equipment configuration, examplary overview . . . . . 1−3
Fig. 1−3 ADS−B AS 682 in 19" cabinet, equipment overview, examplary . . . . . . . . . . 1−4
configuration
Fig. 2−1 AS 680 Ground Station equipment (example Ground Station A) . . . . . . . . . . 2−1
Fig. 2−2 ADS−B Ground Station AS 680 architecture (at one site) . . . . . . . . . . . . . . . . 2−3
Fig. 2−3 SPU 19" subrack, front view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−4
Fig. 2−4 SPU 19" subrack, rear view, DC/DC and AC/DC option . . . . . . . . . . . . . . . . . . 2−4
Fig. 2−5 SPU location of part/serial numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−5
Fig. 2−6 AS 680 Interfaces, overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−5
Fig. 2−7 AS 680 information flow, overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−5
Fig. 2−8 RXU (RXU1 and RXU2), front view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−6
Fig. 2−9 GTS module/GPS receiver DG14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−7
Fig. 2−10 Signal Processing Board (SPB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−8
Fig. 2−11 Single Board Computer (SBC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−10
Fig. 2−12 SPU power supply options: DC/DC converter and AC/DC converter . . . . . . 2−12
Fig. 2−13 Fan unit tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−12
Fig. 2−14 ADS−B Site Monitor (SM), rear view, connectors and identification labels . 2−13
Fig. 2−15 ADS−B Site Monitor (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−13
Fig. 2−16 Proposal of arrangement and cabling of SPU, SM and Exchange Panel . . . 2−14
in 19" rack
Fig. 2−17 AS 682 Ground Station equipment, assembled in 19" cabinet . . . . . . . . . . . . 2−15
Fig. 2−18 ADS−B Ground Station AS 682 architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−16
Fig. 2−19 Data Switch, front view (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−17
Fig. 2−20 Exchange Panel, rear side of AS682 cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−17
Fig. 2−21 Uninterruptible Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−18
Fig. 2−22 Uninterruptible Power Supply, operating panel at base unit . . . . . . . . . . . . . . 2−19
Fig. 2−23 Omnidirectional antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−21
Fig. 2−24 Antenna Amplifier Unit (AAU) with mounting kit and weather protection . . . . 2−21
Fig. 2−25 GPS antenna and mounting accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−22
Fig. 2−26 RCMS subsystem configuration (example equipment) . . . . . . . . . . . . . . . . . . . 2−23
Fig. 2−27 AS 680 tool chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−23
Fig. 2−28 RCMS subsystem tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−24
Ed. 10.07 XV
AS 680/682 ADS−B
Fig. 2−29 LCMS subsystem tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−24

Fig. 2−30 Detailed BITE Status display on RCMS (example) . . . . . . . . . . . . . . . . . . . . . . 2−26
Fig. 2−31 ADS−B Technical Situation Display (example) . . . . . . . . . . . . . . . . . . . . . . . . . 2−26
Fig. 2−32 Display Configuration tool for the Technical Situation Display (example) . . . 2−27
Fig. 3−1 24028 28001, Status cable Site Monitor, SubD/9pin to SubD/15pin . . . . . . 3−3
(used with AS 680)
Fig. 3−2 240xx 28xxx, Status cable Site Monitor/Intrusion, SubD/9pin to SubD/15pin 3−3
(AS 682)
Fig. 3−3 27288 04059, ANT AAU cable, RF, N−N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−3
Fig. 3−4 27288 04140 to 42, Ground Station internal RF−cable to Exchange Panel, 3−3
RF, N−SMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig. 3−5 24028 28002, BITE connection cable, RJ45, 8/8 to RJ45, 8/8, crossed . . . . 3−4
Fig. 3−6 24028 28003, LCMS serial cable, SubD/9pin to MicroSubD/9pin, crossed . 3−4
Fig. 3−7 24028 28004, LCMS Ethernet cable (standard), 10/100Base−T, RJ45, 8/8, . 3−4
cross over
Fig. 3−8 24028 xxxxx, LCMS Serial to USB adapter cable, SubD/9pin to USB A, . . . . 3−4
optional
Fig. 3−9 System cabling ADS−B Ground Station AS 680 (one station shown) . . . . . . 3−5
Fig. 3−10 ADS−B Ground Station AS 680, SPU, power connection rear side . . . . . . . . 3−6
Fig. 3−11 RCMS, system cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−6
Fig. 3−12 System cabling ADS−B Ground Station AS 682 (1) . . . . . . . . . . . . . . . . . . . . . 3−7
Fig. 3−13 AS 682, SPU power connection rear side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−8
Fig. 3−14 System cabling ADS−B Ground Station AS 682, Data Switch and UPS (2) . 3−8
Fig. 3−15 Cabling and arrangement example of Exchange Panel . . . . . . . . . . . . . . . . . . 3−11
Fig. 3−16 Test setup frequency check of local oscillator of RXU . . . . . . . . . . . . . . . . . . . 3−16
Fig. 3−17 Test setup sensitivity level adjustment of RXU . . . . . . . . . . . . . . . . . . . . . . . . . . 3−17
Fig. 3−18 Receiver sensitivity level setting, signal at monitor output (1 of 3) . . . . . . . . . 3−17
Fig. 3−21 RCMS desktop panel to start up the MTSC and the TSC application . . . . . . 3−21
(example)
Fig. 4−1 RCMS desktop panel with the set of application software (example) . . . . . . 4−1
Fig. 4−2 LCMS desktop panel with the set of application software (example) . . . . . . . 4−1
Fig. 4−3 Structure of the application software on the LCMS and the RCMS . . . . . . . . 4−2
Fig. 4−4 RCMS Configuration with the two screens used for the MTSC application . 4−5
Fig. 4−5 Structure of the MTSC Main Window on screen 1 (example) . . . . . . . . . . . . . 4−6
XVI Ed. 10.07

ADS−B AS 680/682
Fig. 4−6 MTSC, Event window on screen 1 (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−7

Fig. 4−7 MTSC, Detailed Status window on screen 0 (example) . . . . . . . . . . . . . . . . . . 4−8
Fig. 4−8 Detailed Status window, ’Edit Properties’ window (example) . . . . . . . . . . . . . 4−8
Fig. 4−9 Menubar of the MTSC Supervisor main window (example) . . . . . . . . . . . . . . . 4−10
Fig. 4−10 MTSC, Settings Window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−10
Fig. 4−11 MTSC, Pop−up window indicating an MTSC Error (example) . . . . . . . . . . . . 4−10
Fig. 4−12 MTSC, About Window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−11
Fig. 4−13 MTSC Help window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−11
Fig. 4−14 Map menu provided to the Supervisor within the map panel (example) . . . . 4−12
Fig. 4−15 Window ’Create New Device’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−13
Fig. 4−16 Map panel with new GS icon (default name), example . . . . . . . . . . . . . . . . . . . 4−13
Fig. 4−17 Window ’Open’ to select a new map file (example) . . . . . . . . . . . . . . . . . . . . . 4−14
Fig. 4−18 Window ’Save’ to save the actual configuration (example) . . . . . . . . . . . . . . . 4−14
Fig. 4−19 Window ’Features’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−14
Fig. 4−20 GS menu provided to the Supervisor within the map panel (example) . . . . . 4−15
Fig. 4−21 Window ’Configuration Info −<GS name>’ (example) . . . . . . . . . . . . . . . . . . 4−15
Fig. 4−22 Desktop panel menu with ’ADS−B Tools’ submenus ’Technical Situation . 4−17
Display’
Fig. 4−23 Technical Situation Display − TSD, main components (example) . . . . . . . . . 4−17
Fig. 4−24 TSD, menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−19
Fig. 4−25 TSD, menu ’File’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−19
Fig. 4−26 TSD file selection for saving configuration (example) . . . . . . . . . . . . . . . . . . . . 4−19
Fig. 4−27 TSD, menu ’Map Items’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−20
Fig. 4−28 TSD, menu ’Markings’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−20
Fig. 4−29 TSD, menu ’Display’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−21
Fig. 4−30 TSD, menu ’Tracks’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−21
Fig. 4−31 TSD, submenu ’Plot Shape’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−21
Fig. 4−32 TSD, submenu ’Plot Size’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−22
Fig. 4−33 TSD, submenu ’History’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−22
Fig. 4−34 TSD, submenu ’Speed Vector’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−23
Fig. 4−35 TSD, menu ’Preferences’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−23
Fig. 4−36 TSD, ’Information’ panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−23
Fig. 4−37 TSD, ’GS Filter’ panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−24
Fig. 4−38 TSD, ’PA Filter’ panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−24
Ed. 10.07 XVII

AS 680/682 ADS−B
Fig. 4−39 TSD, ’Selected localisation’ panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−25

Fig. 4−40 TSD, ’Selected interface’ panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−25
Fig. 4−41 TSD, menu ’Help’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−25
Fig. 4−42 TSD, ’About’ panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−26
Fig. 4−43 TSD, ’Short Reference’ panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−26
Fig. 4−44 TSD, Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−27
Fig. 4−45 TSD, ’Target Details’ panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−28
Fig. 4−46 TSD, Map view (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−29
Fig. 4−47 TSD, distance line (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−30
Fig. 4−48 TSD, Track (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−31
Fig. 4−49 TSD, Ground Station distance circles (example) . . . . . . . . . . . . . . . . . . . . . . . . 4−32
Fig. 4−50 TSD, distance circle panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−32
Fig. 4−51 TSD, flight panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−33
Fig. 4−52 TSD, Statusbar (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−34
Fig. 4−53 Display Configuration Tool, main components (example) . . . . . . . . . . . . . . . . 4−35
Fig. 4−54 Display Configuration, Menubar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−35
Fig. 4−55 Display Configuration, Menu ’File’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−36
Fig. 4−56 Configuration Tool, File Selection (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−36
Fig. 4−57 Display Configuration, menu ’Help’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−37
Fig. 4−58 Display Configuration, About Panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . 4−37
Fig. 4−59 Display Configuration, Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−37
Fig. 4−60 Display Configuration, Tree View (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−38
Fig. 4−61 Display Configuration, Parameter Panel (example) . . . . . . . . . . . . . . . . . . . . . . 4−39
Fig. 4−62 Display Configuration, No Element Selected (example) . . . . . . . . . . . . . . . . . . 4−39
Fig. 4−63 Display Configuration, Add New List Item (example) . . . . . . . . . . . . . . . . . . . . 4−40
Fig. 4−64 Display Configuration, Delete List Item (example) . . . . . . . . . . . . . . . . . . . . . . . 4−41
Fig. 4−65 Display Configuration, Statusbar (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−41
Fig. 4−66 Parameters DisplayConfig (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−42
Fig. 4−67 Parameters Window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−42
Fig. 4−68 Parameters Refltf (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−43
Fig. 4−69 Parameters ltfParameters (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−43
Fig. 4−70 Parameters RefGS (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−44
Fig. 4−71 Parameters Groundstation (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−45
Fig. 4−72 Parameters Display (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−46
XVIII Ed. 10.07

ADS−B AS 680/682
Fig. 4−73 Parameters Delay (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−47

Fig. 4−74 Parameters Grid (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−48
Fig. 4−75 Parameters SpeedVector (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−48
Fig. 4−76 Parameters Compass (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−49
Fig. 4−77 Parameters FLPanel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−49
Fig. 4−78 Parameters Marking (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−50
Fig. 4−79 Parameters Detail (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−51
Fig. 4−80 Parameters Plot and Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−51
Fig. 4−81 Parameters Road (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−52
Fig. 4−82 Desktop panel menu with ’ADS−B Tools’ for record and replay (example) . 4−53
Fig. 4−83 Record/Replay tools, components of start window (example) . . . . . . . . . . . . 4−54
Fig. 4−84 Record/Replay, menubar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−55
Fig. 4−85 Record/Replay, menu File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−55
Fig. 4−86 Command Buttons for Replay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−56
Fig. 4−87 Record/Replay, About menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−56
Fig. 4−88 Record/Replay tools, ’About’ panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . 4−56
Fig. 4−89 Record/Replay tools, ’Reference’ panel (example) . . . . . . . . . . . . . . . . . . . . . . 4−57
Fig. 4−90 Toolbar of Record Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−57
Fig. 4−91 Toolbar of Replay Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−57
Fig. 4−92 Record/Replay tools, ’Top’ page (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−58
Fig. 4−93 Record/Replay tools, ’Screen Output’ page (example) . . . . . . . . . . . . . . . . . . 4−59
Fig. 4−94 Statusbar of Replay Tool (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−59
Fig. 4−95 RRC, page ’Parameter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−60
Fig. 4−96 RRC, File Selection Box (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−62
Fig. 4−97 RRC, page ’Filter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−64
Fig. 4−98 RRP, page ’I/O Parameter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−65
Fig. 4−99 RRP, page ’Data Parameter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−67
Fig. 4−100 RAC, page ’I/O Parameter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−69
Fig. 4−101 RAC, page ’Data Parameter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−73
Fig. 4−102 RAC, page ’Trackstore’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−74
Fig. 4−103 RAC, page ’CPR Decoding’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−75
Fig. 4−104 RAC, page ’ASTERIX CAT 21’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−77
Fig. 4−105 RAC, ’About’ panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−78
Fig. 4−106 ARC, page ’Parameter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−79
Ed. 10.07 XIX

AS 680/682 ADS−B
Fig. 4−107 ARC, page ’Filter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−80

Fig. 4−108 ARP, page ’I/O Parameter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−81
Fig. 4−109 ARP, Data Parameter (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−83
Fig. 4−110 RCMS desktop panel with the ’Misc. Tools’ menu (example) . . . . . . . . . . . . . 4−85
Fig. 4−111 LCMS desktop panel with the ’Misc. Tools’ menu (example) . . . . . . . . . . . . . 4−85
Fig. 5−1 Structure of the TSC GUI (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−1
Fig. 5−2 TSC Statusbar (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−2
Fig. 5−3 TSC, Minimized View (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−3
Fig. 5−4 Logging Settings Window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−5
Fig. 5−5 About Panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−6
Fig. 5−6 Notebook Page ’Overview’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−9
Fig. 5−7 Page BITE (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−10
Fig. 5−8 Page ’Telegram Filter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−15
Fig. 5−9 Page ’Groundstation’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−17
Fig. 5−10 Page ’Network’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−19
Fig. 5−11 Page ’Output’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−20
Fig. 5−12 Page ’Telegram Check’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−22
Fig. 5−13 Page ’Process’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−23
Fig. 5−14 Page ’ADSB’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−24
Fig. 5−15 Page ’ADSB Filter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−26
Fig. 5−16 Page ’Site Monitor’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−28
Fig. 5−17 Page ’Software’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−29
Fig. 5−18 FOM/PA table (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−30
Fig. 5−19 FOM/PA restriction table (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−30
Fig. 5−20 Upload Kernel, start of upload (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−31
Fig. 5−21 Upload Kernel, upload successfully done (example) . . . . . . . . . . . . . . . . . . . . 5−31
Fig. 5−22 Upload Application (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−32
Fig. 5−23 Upload FOM/PA Table (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−32
Fig. 5−24 Upload NVRAM, 3 steps of uploading (example) . . . . . . . . . . . . . . . . . . . . . . . 5−33
Fig. 5−25 Upload FOM/PA Restriction Table (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−34
Fig. 5−26 Download NVRAM, start of download (example) . . . . . . . . . . . . . . . . . . . . . . . . 5−35
Fig. 5−27 Download NVRAM, download successfully done (example) . . . . . . . . . . . . . . 5−35
Fig. 5−28 Extract of an NVRAM configuration file contents (example) . . . . . . . . . . . . . . . 5−35
Fig. 5−29 Download FOM/PA Restriction Table (example) . . . . . . . . . . . . . . . . . . . . . . . . . 5−36
XX Ed. 10.07
ADS−B AS 680/682
Fig. 5−30 Extract of a FOM/PA Restriction Table file (example) . . . . . . . . . . . . . . . . . . . . 5−36

Fig. 5−31 Reboot terminal log without kernel switch (example) . . . . . . . . . . . . . . . . . . . . 5−37
Fig. 5−32 Reboot terminal log with kernel switch (example) . . . . . . . . . . . . . . . . . . . . . . . 5−37
Fig. 5−33 Restarting the application (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−38
Fig. 5−34 Ground Station Login (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−38
Fig. 5−35 Page ’GPS’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−39
Fig. 5−36 Page ’UPS’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−41
Fig. 5−37 SNMP−Card ’CS121 Budget’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−42
Fig. 5−38 Set−Up for CS 121 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−42
Fig. 5−39 Firefox Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−43
Fig. 5−40 UPS Adapter Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−43
Fig. 5−41 Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−44
Fig. 5−42 Model & System setting (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−44
Fig. 5−43 Network & Security settings (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−45
Fig. 5−44 SNMP settings (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−46
Fig. 5−45 Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−46
Fig. 5−46 Save Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−46
Fig. 5−47 Reboot the adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−47
Fig. 5−48 Normal Operation, UPS Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−47
Fig. 5−49 Page ’Logging’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−49
Fig. 6−1 Page ’Software’ for the Monitor User (example) . . . . . . . . . . . . . . . . . . . . . . . 6−2
Fig. 7−1 Test setup frequency check of local oscillator of RXU subassembly . . . . . . . 7−3
Fig. 7−2 Adjustment of local oscillator frequency of RXU1, location of oscillator . . . . 7−4
and trimmer
Fig. 7−3 Removing Snaphat battery pack from SBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−5
Fig. 7−4 Removing subassemblies of SPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−11
Fig. 7−5 Replacing fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−12
Fig. 7−6 Removing/mounting of LNA−housing (AAU) . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−17
Fig. 8−1 Boot sequence (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−1
Fig. 8−2 BIOS settings (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−2
Fig. 8−3 Host installation (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−2
Fig. 8−4 Configuration of ’Keyboard Type’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−3
Fig. 8−5 Start of installation process (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−3
Fig. 8−6 ’Setup Agent’ main window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−5
Ed. 10.07 XXI

AS 680/682 ADS−B
Fig. 8−7 Window ’Network Setup’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−5

Fig. 8−8 Window ’Network Configuration’, page ’Devices’ (example) . . . . . . . . . . . . . . 8−6
Fig. 8−9 Window ’Ethernet Device’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−6
Fig. 8−10 Window ’Network Configuration’, page ’DNS’ (example) . . . . . . . . . . . . . . . . . 8−7
Fig. 8−11 Information window after saving the network setup (example) . . . . . . . . . . . . 8−7
Fig. 8−12 Window ’Network Setup’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−7
Fig. 8−13 Window ’Additional CDs’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−8
Fig. 8−14 Window ’Add/Remove Packages’ for ADS−B software installation . . . . . . . 8−9
(example)
Fig. 8−15 Window ’Add/Remove Packages’, select equipment and SW for installation 8−9
(example)
Fig. 8−16 Window ’Add/Remove Packages’, RCMS list of SW packages (example) . . 8−10
Fig. 8−17 Window ’Installation Overview’, list of installing SW (example) . . . . . . . . . . . . 8−10
Fig. 8−18 Window with information on status of SW installation process (example) . . 8−11
Fig. 8−19 Window after successfully installed ADS−B software (example) . . . . . . . . . . 8−11
Fig. 8−20 Window ’Additional CDs’ for further SW installation (example) . . . . . . . . . . . . 8−12
Fig. 8−21 Window ’Add/Remove Packages’ for ADS−B configuration SW installation 8−12
(example)
Fig. 8−22 Window ’Add/Remove Packages’, select configuration SW for installation . 8−12
(example)
Fig. 8−23 Window with list of packages (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−13
Fig. 8−24 Window ’Installation Overview’ with installing ADS−B configuration files . . . 8−13
(example)
Fig. 8−25 Window successfully installed configuration SW (example) . . . . . . . . . . . . . . 8−13
Fig. 8−26 Window ’Additional CDs’ to continue/finish SW installation process . . . . . . . 8−14
(example)
Fig. 8−27 Kangaroo login window to enter username (example) . . . . . . . . . . . . . . . . . . . 8−15
Fig. 8−28 Kangaroo login window to enter password (example) . . . . . . . . . . . . . . . . . . . 8−15
Fig. 8−29 Device menu for memory stick handling (example) . . . . . . . . . . . . . . . . . . . . . 8−17
XXII Ed. 10.07

ADS−B
List of Abbreviations
LIST OF ABBREVIATIONS
AAU Antenna Amplifier Unit

AC Alternating Current
ADS−B Automatic Dependent Surveillance−Broadcast
ARC ASTERIX data ReCord tool
ARP ASTERIX data RePlay tool
AS 680 Aggregation Suggestion 680
ASP ASTERIX Status rePlay tool
ASR ASTERIX Status Record tool
ASTERIX All purpose STructured Eurocontrol suRveillance Information eXchange
ATC Air Traffic Control
BITE Built−In Test Equipment
CAT Category
CDTI Cockpit Display of Traffic Information
COTS Commercial Off The Shelf
CPR Compact Position Reporting
CPU Central Processing Unit
CRC Cyclic Redundancy Check
DC Direct Current
DF Downlink Format
DME Distance Measuring Equipment
DOP Dilution of Precision
ES Extended Squitter
ft feet
FOM PA Figure of Merit Position Accuracy
GB Giga Byte
GNSS Global Navigation Satellite System
GPS Global Positioning System
GS Ground−Station
GTK Gimp Tool Kit
GTS GPS Timing System
GUI Graphical User Interface
HPL Horizontal Protection Level
I/O Input / Output

ICAO International Civil Aviation Organisation
KB Kilo Byte (1024 bit)
LAN Local Area Network

LCMS Local Control and Monitoring System
Ed. 10.07 AV−1

ADS−B
List of Abbreviations
LED Light Emitting Diode
LMW Log Message Window
LNA Low Noise Amplifier
MB Mega Byte
MIB Management Information Base
MMS ID Mode S address Identification
MTSC Master Technical System Control
n. a. not applicable
NTP Network Time Protocol
NVRAM Non Volatile RAM
PC Personal Computer
PE Protective Earth
PPS Pulse Per Second
RAC Raw data ASTERIX Converter tool

RAM Random Access Memory
RCMS Remote Control and Monitoring System
RF Radio Frequency
RPM Red Hat Package Manager
RRC Raw data ReCord tool
RRP Raw data RePlay tool
RX Receiver
RXU Receiver Unit
SAC System Area Code

SBC Single Board Computer
SIC System Identification Code
SIS Signal In Space
SM Site Monitor
SNMP Simple Network Management Protocol
SPB Signal Processing Board
SPU Signal Processing Unit
TCL/TK Tool Command Language / Tool Kit

TIS−B Traffic Information Services−Broadcast
TSC Technical System Control
TSD Technical Situation Display
TSS Technical System Supervisor
TXU Transmitter Unit
UDP/IP User Datagram Protocol / Internet Protocol

UPS Uninterruptable Power Supply
VAC Volts AC
VDL VHF Data Link
VHF Very High Frequency
VM Virtual Machine
VME VERSA Module Eurocard
AV−2 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance System Description
CHAPTER 1
SYSTEM DESCRIPTION
1.1 GENERAL
ADS−B is a data link application or principle that makes use of navigational data that are available
onboard of an aircraft. Aircraft avionics permanently determines the aircraft’s navigational position
and movement vector. Most air transport aircraft are also equipped with a flight management system
that guides the aircraft along waypoints programmed by the pilot.
The principle of ADS−B refers to making available this information by means of an automatic broad-
cast via digital data link. ADS−B is an acronym for Automatic Dependent Surveillance Broadcast:
Automatic no human intervention is required,
Dependent the surveillance solution is not determined by the observer but provided by the
observed object
Surveillance data provided include position, velocity vector etc.
Broadcast transmitted without external trigger (e.g. interrogation) without any specific addressee
This broadcast information may be received and processed by other aircraft or ground systems for
use in improved situational awareness, conflict avoidance and airspace management. Three ADS−B
data link technologies are emerging as possible contenders − namely, Universal Access Transceiver
(UAT), VHF Data Link (VDL) Mode 4 and 1090MHz Extended Squitter (Mode S data link). The interna-
tional civil aviation organization ICAO has recommended to use the 1090 MHz (Mode S) data link as
global data link technology for ADS−B purposes. The other two data links are seen only for regional
applications. Fig. 1−1 shows the system and its components in an example view.
Aircrafts, MODE S data GPS Satellites
1090 ES SIS GPS SIS
ADS−B RX GPS RX
AS 680/682 AS 680/682 AS 680/682 AS 680/682
AS 680/682 AS 680/682 AS 680/682 AS 680/682
Ground Network
Ground−Station data
ADS−B operational data
Maintenance data
ATC ATC
RCMS 1 RCMS 2
ADS−B LAN A ADS−B LAN A

ADS−B LAN B ADS−B LAN B
ATC−Center ATC−Center
Fig. 1−1 System overview ADS−B, examplary configuration
Ed. 10.07 1−1

AS 680/682 ADS−B
System Description Description, Operation and Maintenance
1.1.1 Applications
Automatic Dependent Surveillance Broadcast (ADS−B) is a surveillance technology that uses posi-
tion information broadcast by aircraft as a basis for surveillance, rather than a radar scan to plot air-
borne targets. Aircraft (or vehicles) equipped with ADS−B transponders broadcast information con-
tinuously directly from the flight management system. This data is used to provide a very accurate
visual display containing information such as height, speed and identity, in a similar way to secondary
radar, but more detailed and comprehensive at a fraction of the cost. ADS−B offers other advantages
such as more frequent update rates and the potential to convey aircraft derived data such as spot
weather updates, aircraft intent and avionics data.
The ADS−B system serves the following benefits:

− Reduced Communication Congestion
− Enhanced Situational Awareness and Safety for Pilots
− Reduced Taxi/Takeoff Delays
− Expanded Surveillance, also on airport surface
− Reduced Cost
There are three kinds of ADS−B applications defined as follows:

− Air−to−Air Applications
Receiving the ADS−B data, the pilot is enabled to actually see other aircraft in his vicinity. This
Cockpit Display of Traffic Information (CDTI) is the basic technology which will enable the pilot to
electronically "see and avoid" other aircraft in a largely passive mode. Independent of ground
based radar CDTI will greatly enhance pilot situational awareness and lead to safer and more effi-
cient airspace operations. ADS−B techniques can also enhance traffic collision avoidance sys-
tems in the future.
− Air−to−Ground Applications
ADS−B is able to provide surveillance data to Air traffic Controllers and or aircraft operations facili-
ties on the ground. An aircraft in flight broadcasts its position, altitude, identification, and other per-
tinent information to Ground Stations that relay this data to Air Traffic Control or aircraft operations
facilities. This information is used to effectively establish surveillance in remote locations or extend
or even replace current surveillance capabilities. Air−to−Ground ADS−B can greatly assist con-
trollers and aircraft operations facilities with airspace management.
− Ground−to−Ground Applications
ADS−B provides accurate position and identification of aircraft and other equipped vehicles for
airport surface surveillance. Aircraft and vehicles, if suitably equipped, broadcast information con-
taining position, speed, heading and identification to Ground Stations located around the airport.
This information is relayed to air traffic controllers and airport management facilities personnel. Air-
port surface surveillance enhanced through the ADS−B Data Link application will lead to safer and
more efficient airport surface operations in all weather conditions.
1−2 Ed. 10.07

ADS−B AS 680/682
1.2 SYSTEM COMPONENTS
See Figs. 1−2, 1−3.
The ADS−B Ground Station AS 680 or AS 682 is a system that offers Automatic Dependent Surveil-
lance Broadcast (ADS−B) services based on the 1090 ES SSR Mode S data link (1090 MHz). The
AS 680 version builts a single system for integration in an existing environment, while the AS 682 ver-
sion builts a completely wired and redundant system including uninterruptible power supplies (UPS)
assembled in a 19" cabinet. The ADS−B Ground Station receives Mode S ADS−B Broadcasts (ex-
tended squitters) periodically emitted by equipped aircraft. These messages contain information
about the aircraft’s current position, altitude, velocity vector, callsign, etc. The Ground Station pro-
vides the decoded data as standard ASTERIX output via an attached network to Air Traffic Control
surveillance applications. The signal processing techniques applied within AS 680 allow for reliable
operation even under heavy radio load conditions and long−range coverage. The usual application
is en−route surveillance with coverage ranges of up to 250 NM. Other applications are terminal area
surveillance and airport surface surveillance. The system consists of 3 main subsystems:
− AS 680/682
The ADS−B Ground Stations subsystem to be installed at remote sites.
− RCMS
The centralized Remote Control and Monitoring System (RCMS), to monitor, configure and control
the ADS−B Ground Station.
− Maintenance equipment
LCMS (Local Control and Monitoring System: Laptop), extender card and a set of spare parts
Two ADS−B Ground Station subsystems (GS A and GS B) are usually installed at one remote site.
The subsystems are supplied by either optional mains voltage (100 to 240 VAC) or standard DC volt-
age (nominal 24 VDC). The DC voltage may be generated by Solar powered DC generators.
RX A RX B
ADS−B Ground−Station A ADS−B Ground−Station B
GPS−antenna ADS−B receiving antenna GPS−antenna ADS−B receiving antenna
THALES THALES
I I
0 0
SPU SPU
THALES THALES
Site Monitor Site Monitor

LCMS local connection to antenna GS B to antenna GS A
Station 1 or 2 optional optional
AAU AAU
LAN
RCMS−configuration
Fig. 1−2 ADS−B AS 680, basic equipment configuration, examplary overview
Ed. 10.07 1−3

AS 680/682 ADS−B
The two Ground Stations A and B (or 1 and 2) comprise identical components (Fig. 1−2, 1−3), i.e.:
− Signal Processing Unit (SPU)
− Site Monitor (SM)
− GPS RX antenna
− ADS−B RX antenna
− Antenna Amplifier Unit (AAU)
− cables and accessories
In addition the Local Control and Monitoring System (LCMS) is used for local operation and/or local
maintenance purposes. It is built by a standard Laptop computer as data terminal including the ap-
propriate application software. It is similar to that of the RCMS excluding the MTSC application.
Two Remote Control and Monitoring Systems (RCMS 1 and 2) may be installed each centrally at the
Air Traffic Controller building (ATC) at two dedicated sites. The two RCMS 1 and 2 are built up with
identical components which comprise (Fig. 1−2):
− Personal Computer with dual TFT LCD−monitor; operating system: Linux
− Application Software including:
S Master Technical System Control (MTSC),
S Technical System Control (TSC),
S multiple network interfaces,
S raw data recording and replay tools, Asterix data recording/replay and conversion,
S ADS−B Display with a display configuration tool.
In addition there are some options which may be used according to customer requirements, e.g.:
− an Uninterruptable Power Supply system (UPS) which buffers the operation of the GS in case of
a mains power fail, used in the AS 682 version for each SPU (Fig. 1−3)
− a Data Switch, used in the AS 682 version for interconnection of each SPU, UPS to LAN (Fig. 1−3)
− an independent site monitor device which is not directly connected to the GS (e.g. other location)
but offers radiation of test signals via an individual antenna.
ADS−B Ground Station AS682 19" cabinet ADS−B RX antenna
THALES GPS−antenna 1
0 Exchange Panel
SPU1
RF distribution
RF
AAU
Data switch
THALES GPS−antenna 2
I
RCMS−configuration
0
SPU2
Site Monitor
UPS1 LAN
UPS2
Fig. 1−3 ADS−B AS 682 in 19" cabinet, equipment overview, examplary configuration
1−4 Ed. 10.07

ADS−B AS 680/682
1.3 TECHNICAL CHARACTERISTICS
1.3.1 Dimensions and Weight
AS 680 basic system
SPU (HxWxD); weight 19", 3HU; 133x482x250 mm; approx. 7.1 kg
SM (HxWxD); weight 19", 1HU; 43x482x250 mm; approx. 1.0 kg
AS 682 cabinet, fully equipped, (HxWxD); weight 19", 24HU; 1200x600x600 mm; approx. 150 kg
− SPU (HxWxD); weight (2x) 19", 3HU;133x482x250 mm; approx. 7.1 kg
− SM (HxWxD)/weight 19", 1HU; 43x482x250 mm; approx. 1.0 kg
− Data Switch (HxWxD); weight 19", 1HU; 43x482x180 mm; approx. 1.5 kg
− UPS, basic (HxWxD); weight (2x) 19", 2HU; 86x444x410 mm; approx. 19 kg
− UPS, extension (HxWxD); weight (2x) 19", 2HU; 86x444x410 mm; approx. 25 kg
1.3.2 Peripheral Equipment
RX antenna, omnidirectional (H,∅); weight max. 3420 mm, 60 mm; approx. 26 kg max.
Antenna Amplifier Unit (AAU) (HxWxD); weight 280x180x105 mm; approx. 4 kg
AAU support and cover (HxWxD); weight 300x255x220; approx. 5 kg
GPS antenna, (HxW); weight (2x) 60x100 mm; approx. 0.3 kg
1.3.3 Power Supply
SPU
AC voltage input (AC/DC converter option) 100 to 240 VAC, 50/60 Hz, single phase
DC voltage input (DC/DC converter option) nom. 24 VDC, 18 to 36 VDC, max. 4.5 A
Power consumption approx. 55 VA
Site Monitor
AC voltage input via plug−in mains supply 100 to 240 VAC, 50/60 Hz (DC out 24 V)
Power consumption approx. 5 VA
DC voltage input nom. 24 VDC, 20 to 28 VDC, max. 1 A
Data Switch
AC voltage input 100 to 240 VAC, 50/60 Hz, single phase
DC intern 5 V, max. 8 A
UPS type RS 1000 with 1 battery extension
AC voltage input / max. current 160 to 276 VAC, 50 Hz, single phase / 6.0 A
AC voltage output 208/220/230/240 VAC / 50 Hz
Power rating approx. 1000 VA (700 W)
Batteries 3x 12V, 7Ah
Battery extension 1
Typical battery time (battery mode) in [min] 53 (100 % load), 122 (50 % load)
1.3.4 Environmental Conditions
Ambient temperature
Operation indoor , +10 to +40 °C
(SPU, Data Switch, SM, UPS)
Operation outdoor equipment (antennas) −40 to +70 °C
Transport −55 to +70 °C
Relative humidity
indoor max. 90%, non condensing
outdoor max. 95% (−10 to +39 °C); max. 50% (40 to 70 °C)
non operation and transport up to 100 % with condensation
Ed. 10.07 1−5

AS 680/682 ADS−B
1.3.5 System Data Ground Station AS 680/682

ADS−B System Ground Station with redundant equipment, built
by 2 SPU, coupled via Data Switch to ADS−B LAN
Report generation Asterix Cat 21 reports, Asterix Cat 23 reports
Communication interface UP/IP, SNMP on UDP/IP, SSH, SCP on TCP/IP
1.3.5.1 Signal Processing Unit (SPU)
Receiving signals 1090 ES ADS−B, GPS L1−band 1575.42 MHz
Coverage range up to 150 NM at flight level > 300, omnidirectional
Capacity (GS) > 250 targets
Report generation Asterix cat21 (ADS−B)
1.3.6 Interfaces
SPU
− PC connector */** Serial, SubD, 9 pin, male
− Data interface connector */** RJ45, Ethernet 10/100Base−T
Serial, V.24, MicroSubD, 9 pin, female
− Others */** Serial, RS232, SubD, 9pin, female
Bite, RJ45, 8pin;
Status Interface I/O, SubD, 15pin, female
Site monitor
− Communication/control */** Serial, RS232, MicroSubD, 9pin, female;
− Status */** Status Interface I/O, SubD, 15pin, female
− Data interface connector (ADS−B LAN) */** 2x RJ45, dual port Ethernet, 1000Base−T
Data Switch (ADS−B LAN) */** 2x 8 connectors RJ45, Ethernet, 1000Base−T
* according IEC60950 ** SELV−circuit (Safety Extra Low Voltage)
1.3.7 Conformity and Licensing Approval

The AS 680 Ground Station is compliant to ICAO Annex 10 and to current European Regulations for
human health (low voltage directive) and electromagnetic compatibility (EMC). It complies with the
requirements of EC Guideline 89/336/EEC in its implementation. It also fulfills the requirements of the
following EMC Guidelines:
− Emission Test: EN 55022 (1998); EN 61000−3−2 (1995); EN 61000−3−3 (1995)
− Immunity Tests: EN 55024 (1998); (EN 61000−4−2 (1995); EN 61000−4−11 (1994))
1−6 Ed. 10.07

ADS−B AS 680/682
1.4 GENERAL SAFETY PRECAUTIONS
1.4.1 Observation of Safety Regulations
The following are general safety precautions that are not related to any specific procedures. These
are recommended precautions that personnel must understand and apply during many phases of
operation and maintenance. Regard also the safety precautions and measures which are contained
in the original technical manuals (COTS) of the individual equipment manufacturer. In addition to the
mentioned instructions for avoiding damage and injury, locally valid safety regulations should always
be observed.
1.4.2 Maintenance Operation at the Device
The primary power supply voltage should always be disconnected by actuating the corresponding
switch (mains and/or DC power) on the equipment concerned before removing a subassembly or a
plug−in connection in order to avoid injury to persons or subsequent damage to devices or subas-
semblies.
1.4.3 Handling Subassemblies

When replacing subassemblies and plug−in cards containing electrostatically sensitive compo-
nents, special precautionary measures should be taken during removal, transport and installation in
order to prevent damage to the components.
PCB’s containing electrostatically sensitive components are marked with this symbol:
Electrostatic damage may be caused when the person performing the subassembly replacement
bears a static charge due to friction with an insulated floor covering or with synthetic articles of cloth-
ing (e.g. soles) and the charge is transferred to the terminals of the MOS components.
In order to avoid this, make positive contact between the system ground and your hand before and
during removal or insertion of the subassembly. Any body charge is then discharged to the system
ground. When the subassembly has been removed, the subassembly should be placed in a special
container or envelope. Use the following procedure and sequence to insert a subassembly:
− Discharge the body by touching the system ground with both hands.
− Remove the subassembly from the special container.
− Remove the short−circuit bar from the subassembly.
− Touch the device ground.
− Insert the subassembly, if possible whilst retaining contact with the device ground.
1.4.4 Using Lithium Batteries
State of the art computer systems may contain Lithium batteries for data backup. These are used in
the AS 680 Signal Processing Unit and in commercial Personal Computers (PC) used for the RCMS
systems. If replacement is necessary, always read the label on the battery. It is recommended to insert
only batteries of the same type according to the recommendations of the manufacturer.
WARNING
Do not recharge, disassemble, heat above 100 °C or incinerate any lithium cell. Do not
short−circuit the cell or solder directly on it. Disregard of the norms regarding the use of
lithium batteries may cause the risk of fire, explosion and the leakage of toxic liquid and
gas. Run−down batteries are objects that can pollute the environment and must be dis-
posed of taking the proper precautions.
Ed. 10.07 1−7

AS 680/682 ADS−B
1.4.5 Miscellaneous
To avoid risks of lightning, do not work outside a building or on the Ground Station antenna system
during thunderstorms.
1.4.6 Observation of Safety Regulations

In addition to following the above instructions for avoiding damage and injury, always observe locally
pertinent safety regulations.
1−8 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Subsystem Description
CHAPTER 2
SUBSYSTEM DESCRIPTION
2.1 ADS−B GROUND STATION AS 680
2.1.1 General Description
See Fig. 2−1.
The ADS−B Ground Station AS 680 developed by Thales is a compact and autonomous unit based
on 1090 MHz Extended Squitter (ES) reception. The main functions of AS 680 are to receive and pro-
cess ADS Broadcasts on 1090 MHz and to directly output decoded consistent target report data to
an ATC application using the international ASTERIX standard category 21, ed. 0.23. Further central
equipment is not needed. In order to output complete ASTERIX reports, data from different ADS−B
reports (extended squitter messages) of the same target are collected (e.g. position, velocity, etc.).
The Ground Station processing makes sure that data derived from different extended squitter types
are combined in a consistent way.
GPS−antenna ADS−B receiving antenna
and Low Noise Amplifier (LNA)
RF cable, 1/4" cellflex RF cable, 1/2" cellflex,

up to 10 m up to 30 m
Local Monitoring
LCMS
Signal Processing Unit (SPU)
Status exchange
BITE signal to/from GS B (option)
Ethernet connection to ATC/RCMS
Site monitor (SM)

AAU
Maintenance
RF cable, 1/2" cellflex, up to 2 m
to GS B antenna (optional)* from GS B SM
RF cable, 1/4" cellflex, up to 30 m (optional)*
*NOTE: Instead of this optional RF signal line from other Site Monitor the signal is received via RF.
Fig. 2−1 AS 680 Ground Station equipment (example Ground Station A)

The AS 680 includes internal and external Built In Test Equipment (BITE) functionality, which allows
optimizing the automatic and manual failure detection and identification process. The status as well
as all functions and parameters of the Ground Station can be monitored and controlled via the simple
network management protocol (SNMP). An additional local serial connection to which a standard ter-
minal (e.g. a laptop PC) can be connected serves as console port to perform the basic setup or to
perform local maintenance and control. The basic system data interface is a 10/100BaseT Ethernet
port. On top of Ethernet, the following standard communication protocols are used:
− ASTERIX Category 021 on UDP/IP for operational ADS−B target reports
− SNMP on UDP/IP for remote configuration, maintenance, monitoring and control
− UDP/IP for raw data
− Secure Shell (SSH) for direct remote access on operating system level
− Secure Copy (SCP) for remote upload of configuration files and executables
Ed. 10.07 2−1

AS 680/682 ADS−B
Subsystem Description Description, Operation and Maintenance
For remote operation (i.e. not integrated within an existing ATC network) the Ground Station can be
optionally equipped with a modem to bridge its external Ethernet interface over a telecommunication
line (e.g. ISDN, Fibre Optical Network, etc.). Standard is the Ethernet LAN communication.
The Ground Station equipment can be supplied with DC voltage, e.g. generated by Solar power, or
optional with AC from mains, using the AC/DC converter option.
2.1.2 Physical Breakdown

See Fig. 2−2.
The Ground Station hardware architecture is shown in Fig. 2−2. The configuration delivered for one
ADS−B Ground Station AS 680 includes the following main components:
− 1 omnidirectional antenna
− 1 GPS antenna
− 1 Antenna Amplifier Unit (AAU) which comprises a low−noise pre−amplifier (LNA) and an RF filter
and lightning protection to ensure a good signal−to−noise ratio at the input of the reception chan-
nel and to avoid losses due to the attenuation by antenna cables. It is powered via the RF line from
the Ground Station receiver. The AAU can be mounted with a support on a mast.
− a low−loss cable (e.g. 1/2" cellflex), with a required total maximum attenuation of 4 dB, to connect
the antenna and the AAU, as well as the AAU and the equipment rack
− a Signal Processing Unit (SPU), core module of AS 680, integrated into a 3HU, 19" subrack
− a separate Site Monitor (SM) as external test tool, integrated into a 1HU, 19" subrack
The cables are listed in more detail in section 3.1.4, Figs. 3−1 to 3−4.
The signal processing unit (SPU) is based around a VME−bus system. It includes a receiver unit
(RXU), a signal processing board (SPB), a single board computer (SBC) and a GPS timing system
(GTS). Received RF signals are converted into video signals by the RXU’s logarithmic receiver, and
analyzed by the signal processing board in order to reliably detect ADS−B signals. The decoded data
are collected and further processed by the application software of the SBC. The GPS Timing system
provides a positive system time reference to support the SBC’s real time clock. It also provides addi-
tional information about GPS status, like position, dilution of precision, number and identity of satel-
lites visible and – optionally – also GPS integrity information in the same way as an ADS−B target
(RAIM / HPL). The Ground Station constantly verifies GPS health by checking the deviation of the
measured GPS position versus the configured Ground Station position.
The Ground Station application software runs on an embedded version of the operating system Linux
providing high robustness and flexibility for network communication and remote operation. Changes
in, or updates of the application can be performed while the Ground Station is operational and do not
require a reboot. Thus the system downtime is minimize. Remote upload of new software releases
as well as configuration files is handled in a secured and fail−safe way which is essential for true re-
mote operation.
2.1.3 External Interfaces

The interfaces are identified in Fig. 2−2, as well as in Fig. 2−6. The Ground Station has the following
RF and analogue signal interfaces:
− an ADS−B 1090 MHz interface (antenna/AAU/receiver), Fig. 2−2/3
− a monitor output of the received ADS−B video signal (base band), Fig. 2−2/11
− a GPS L1−band 1575 MHz interface (active antenna/receiver), Fig. 2−2/4
− 2 monitor probes on the antenna to inject test signals, e.g. coming from a site monitor, Fig. 2−2/9
2−2 Ed. 10.07

ADS−B AS 680/682
The Ground Station communication interfaces are:
− Ethernet 10/100Base−T main interface, Fig. 2−2/7
− separate Ethernet 10Base−T auxiliary interface, e.g. for maintenance purposes, Fig. 2−2/6
− console port V.24 for local set up, Fig. 2−2/5
Other interfaces are:
− an external BITE I/O to accommodate BITE status summary from another (redundant) Ground Sta-
tion, Fig. 2−2/8
− an external sensor input to connect site monitor BITE status, door lock switches, smoke detectors,
etc., Fig. 2−2/9
− a telegram generator output (not used in this application) to drive a Mode S interrogator transmitter
and Mode S downlink transmitter, e.g. as an ADS−B test generator or for TIS−B transmissions,
Fig. 2−2/10.
NOTE: The I/O port of the SPB has only operational insulation and must only connect to Safety
Extra Low Voltage (SELV) as defined in IEC 60950. Connecting other than SELV circuits
can create hazards.
ADS−B RX antenna (1090 ES) GPS RX antenna
from GS 2/SM
optional** optional**
AAU incl.
RF Filter
Low−noise Amplifier
Site Monitor 1) 2) 3) 4) SPU

ADS−B Receiver Unit Ground−Station A
Generator
Power Supply RXU
DC/DC Interface
Signal Processing Board GPS Timing System

SPB GTS
DC in nom. 24 V local configuration
(20 to 28 V) interface (V.24)
Maintenance VME−bus
Laptop Power Supply
DC out S2 DC/DC F1
Video Single Board Computer
monitor
output SBC AC/DC option*
11)
F1 S1
10) 9) 8) 7) 6) 5)
VHF GPS
TX control LCMS
out local configuration
BITE status I/O interface (V.24) Maintenance
Site Monitor BITE status
Ethernet Ethernet local maintenance Laptop
door lock switches etc. interface (Ethernet)
1 0
Ground−Station B
(SPU+SM) Monitor signal of
2nd independent operational data (Asterix Category 021) 100 to 240 VAC (optional)
Ground Station maintenance data (SNMP) or nom. 24 VDC (18 to 36 VDC)
optional
to ATC center/RCMS
Fuses:
* AC/DC converter can be used instead of DC/DC converter F1=2x 6.3AT DC
** Instead of this optional RF signal line from other Site Monitor the signal is received per RF. F1=2x 0.8AT AC
Fig. 2−2 ADS−B Ground Station AS 680 architecture (at one site)
Ed. 10.07 2−3

AS 680/682 ADS−B
2.1.4 Signal Processing Unit (SPU)

See Figs. 2−2 to 2−7.
As the Ground Station equipment is intended to be installed in remote sites with power and space
constraints, considerable importance was attached to finding a solution that combines the utmost
performance at lowest possible power consumption and size. The SPU design led to a robust and
compact Ground Station drawer with small dimensions of only 3 height units (HU) in standard 19"
format, ready for integration into existing racks. If there is no space available at a certain site, a small
cabinet can be easily provided off the shelf.
The power consumption is approx. 55 VA. As standard, the SPU is equipped with a DC/DC converter
which is to be supplied with nominal +24 VDC (18 to 36 VDC). As option for connecting to mains sup-
ply, an AC/DC converter is available which is to be supplied with nominal 230 VAC (100 to 240 VAC,
50/60 Hz). The electronic subassemblies are cooled with a built in, removable fan unit, located at the
inner right side. The SPU is built by the following main subassemblies:
− Receiver unit for ADS−B signals (RXU)
− GPS Timing System (GTS), GPS Receiver for GPS SIS signals
− Signal Processing Board (SPB)
− Single Board Computer (SBC)
− Power Supply, DC/DC or AC/DC (option)
− Fan unit
All user relevant connectors and indicators are located on the SPU front. The front is equipped with
handles to facilitate the insertion and removal of the subrack. The power connectors including fuses
and filters (AC and DC) and the mains switch (with AC/DC option) are located at the rear of the SPU.
NOTE: The label containing part and serial number of the entire SPU as well as the label describ-
ing its power consumption is located on the subrack’s backpanel. The label on the side
is indicating the part and serial number of the chassis itself. Refer to Fig. 2−5.
Power Supply (DC/DC) Air Inlet GPS RX GTS DG14 SBC SPB Fan unit Air outlet
DC on switch RXU
Fig. 2−3 SPU 19" subrack, front view

Air outlet DC input connector with fuse holder (2x 6.3 AT) Option: mains input connector with AC switch and fuse holder (2x 0.8 AT)
Input voltage 18−36 VDC Input voltage 100−240 VAC

Current in 4.5 A max. Current in 0.5 A max.
Fuses 2x 6.3 AT/250 V Fuses 2x 0.8 AT/250 V
1/4" x 1.1/4" 1/4" x 1.1/4"
PE=Protective Earth Fuses DC input PE Fuses Mains switch AC input PE

Fig. 2−4 SPU 19" subrack, rear view, DC/DC and AC/DC option
2−4 Ed. 10.07

ADS−B AS 680/682
SPU part number/

serial number label Chassis part number/
serial number label
Power consumption/
supply data label
Input voltage 18−36 VDC
Current in 4.5 A max.
Fuses 2x 6.3 AT/250 V
1/4" x 1.1/4"
Fig. 2−5 SPU location of part/serial numbers
GPS subassembly, auxiliary Ethernet port (6)

GPS subassembly, serial port SBC serial port, V.24 (5)
GPS antenna RF input (4) Main Ethernet port (7)
Activity indicators BITE status I/O (8)

Video signal monitor output (11) RF input from AAU, ADS−B antenna (3)
Trigger in, not used Site Monitor BITE status and/or door lock switch etc.(9)
TX control, not used (10)
NOTE: Reference numbers in brackets () correspond to Fig. 2−2 .
Fig. 2−6 AS 680 Interfaces, overview
The AS 680 information flow as well as the various intermediated states of processing that AS 680
provides and the diagnostic interface are shown in Fig. 2−7.
GTS SPU
GPS signals (RF)
Aux. through
Ethernet interf.
RF signals Asterix CAT 21
ADS−B antenna GPS antenna GPS data
SBC
Main through
Ethernet interf.
ADS−B signals (RF)
through
SNMP Ethernet interf.
Raw data Remote access (SNMP)
SPB
through
Ethernet interf.
Raw data
RF signals
AAU
Video signal
RXU
through
RF connector
Video signal monitor output
Improved RF signals
Fig. 2−7 AS 680 information flow, overview
Ed. 10.07 2−5

AS 680/682 ADS−B
2.1.4.1 Receiver Unit (RXU)

See Fig. 2−8.
There are two versions: RXU1 and RXU2. The RXU2 with Ref. No. 83142 71503 replaces the RXU1
with Ref. No. 83142 71502. The actual improved RXU2 can operate without an AAU and needs no local
oscillator adjustment. The RXU1 operates only with a receiving antenna including the AAU.
The RXU receives the Mode S downlink RF signals from the antenna and prepares it as a video input
signal for the Signal Processing Board. The receiver provides a logarithmic receiving characteristic
so that the relation between RF input power and video signals is not linear. Optimal performance of
the RXU is achieved by an accurate local oscillator frequency (flo=1030 MHz ±1 MHz). The Low Noise
Amplifier (LNA) within the AAU is supplied with DC via the antenna cable from the RXU. It is protected
against short circuit. The DC supply can be disabled on the RXU board (jumper X3) if no LNA (AAU)
available (see also section 7.3.8.1). If the the RXU is used without an AAU or other equipment is con-
nected to it, jumper X3 of the RXU needs to be removed. In addition, there is no band−pass filter at
the input of the SPU/RXU. If the RXU subassembly should be operated without AAU, a separate dedi-
cated 1090 MHz bandpass filter is needed at the input.
A monitor output delivers the ADS−B video signal for maintenance purposes. A digital storage oscil-
loscope with high impedance connected to this output interface supports adjusting the RXU perfor-
mance (see also sections 3.2.5 and section 3.2.6) and allows further analysis of the received signal.
An indicator "Fail" indicates a malfunction of the RF path (i.e. RXU, LNA, antenna and cabling) as re-
sult of BITE.
The following table gives a definition of the indicators and controls of the RXU.
Board Indicator Color Control Function of control or indicator (lit or flashing)
RXU LED, Fail red Normally out; lit if RX function is faulty.
RXU2 only LED, AAU green Lit if AAU supply is available.
RXU1
BITE LED Video Monitor out RF in from antenna/DC out to LNA

AAU supply indication
RXU2
BITE LED Video Monitor out RF in from antenna/DC out to LNA
Fig. 2−8 RXU (RXU1 and RXU2), front view
2.1.4.2 GPS Timing System (GTS)

See Fig. 2−9.
The GTS DG14 GPS receiver (or optional the GTS B12) processes signals from the Global Positioning
System (GPS) and the geostationary satellites from satellite based augmentation systems (SBAS).
It uses 14 discrete parallel channels for Coarse/Acquisition (C/A) code−phase (pseudo range) mea-
surements and carrier phase measurements on the GPS L1 band (1575.42 MHz).
2−6 Ed. 10.07

ADS−B AS 680/682
In addition to providing the absolute timing reference for the internal timing system (GTS), the receiver
also makes available the measured position of its GPS antenna as well as other data like various dilu-
tions of precision (DOP) and the satellites actually being tracked by the unit.
In case of the DG14 based GTS, an integrated receiver autonomous integrity monitoring (RAIM) func-
tionality allows to determine the horizontal level of protection (HPL) in the same way as an ADS−B
equipped aircraft. HPL indicates the ability to determine satellite errors within the current constella-
tion. It is used to provide position and time as base for the timing system.
The GPS signal is received through an L−band antenna and a low noise amplifier (integrated in the
antenna). The RF port also supplies power to the antenna.
The GTS module provides also the physical connector to the auxiliary Ethernet interface of the Ground
Station. The Local Control and Monitoring System (LCMS), consisting of a maintenance Laptop PC,
can be connected to that auxiliary Ethernet connector for control and maintenance purposes.
The following table gives a definition of the indicators and controls of the GTS module.
GTS DG14 Reset Recessed key, manual reset of GPS board
LED, Fail red Normally out; lit if RX function faulty.

LED, PPS green Flashing once a sec., indicates a PPS trigger.
LED, Status, bicolor red/ On, if satellites not locked;
green Flashing once for each channel with a valid
satellite.
GTS module DG14 BITE RF in from antenna/DC out to antenna
Receiver reset Data Flow Serial RS232 Ethernet (auxiliary)

Status MicroSubD
Fig. 2−9 GTS module/GPS receiver DG14
Ed. 10.07 2−7

AS 680/682 ADS−B
2.1.4.3 Signal Processing Board (SPB)

See Fig. 2−10.
The Signal Processing Board is used to process the video signal of the RXU. The implemented algo-
rithms in the SPB (e.g. 25% of the 1st preamble pulse amplitude) are applied on the video input signal
only and do not consider the receiver characteristics. In detail the following processes are executed
by the SPB:
− Video signal processing
− Preamble detection
− Message decoding
− Retriggering, if a weaker Mode−S is overlapped by a stronger Mode−S message, the weaker
message will be disturbed, therefore the stronger message is decoded.
The following table gives a definition of the indicators and controls of the SPB module.
SPB Reset Recessed key, manual reset of SPB.
LED, Fail red Normally out; BITE indication if watchdog fails.
LED, RxDL green Flashing, indicates receiving a valid MODE−S

telegram (preamble).
LED, TxUL green Normally out, indicates the transmission of an
uplink message (only valid with uplink
modulator option).
LED, TxDL green Normally out, indicates the transmission of a
downlink message (only valid with downlink
modulator option).
LED, TSC green Flashing, indicates SNMP activity on the

network.
LED, OVF green If lit, indicates an overflow in the input hard-
ware buffer of the SPB.
LED, TxN green If lit, indicates that a data packet has been
written to the network.
LED, RxN green If lit, indicates that a data packet has been
read from the network.
LED, TxH green If lit, indicates that data has been sent to the
hardware (only valid with uplink or downlink
modulator option).
LED, RxH green If lit, indicates that data has been read from
the hardware telegram buffer.
LED, Bite green If lit, indicates that the BITE process is active.
LED, Main green If lit, indicates that the MAIN process is active.
front view J5 J3 J4 J6
Board reset LED indications Trigger in Serial RS232 Status interface BITE I/O
TX−Control out I/O Exchange
Fig. 2−10 Signal Processing Board (SPB)
2−8 Ed. 10.07

ADS−B AS 680/682
2.1.4.3.1 Definition of front Connectors J3 to J6
− J3, Transmitter Interface (TX control); normally not used; connector SubD, 9pin, female
This interface is used for downlink as well as for uplink telegrams. The SPB provides digital video
signals. All signals have TTL level characteristics (with 50 ohm termination) and are equipped by
ac−filter to ensure high signal shape quality. For transmitting Mode−S messages on air, additional
equipment is required: a downlink modulator and transmitter unit at 1090 MHz or an uplink modula-
tor and transmitter unit at 1030 MHz. The signal "Suppress" indicates that a downlink (or an uplink)
telegram is going to be transmitted. The signal is available 120 µs for downlink and 2.6 µs for uplink
telegrams before the video signal carries the signal shape.
Assignation of J3:
PIN ASSIGNMENT PIN ASSIGNMENT
1 UL Phase 6 Ground
2 UL Pulse 7 Ground
3 DL Pulse 8 Ground
4 DL Pulse Env 9 Ground
5 Suppress
− J4, Input/Output interface (I/O); connector SubD, 15pin, female

This interface provides 8 input lines and 6 transfer lines: The status signals are general purpose
input lines. Their digital status can be read via the SPB_Sense register. The Ground Station (GS)
status lines have TTL signal characteristics. The meaning is:
Status line 0: Readable by software; used to indicate the status of the GS cabinet door
(open/close).
Status line 4: Readable by software; used to input the status of the Site Monitor.
The Status lines 1 to 3 and 5 to 7 are at time not used. They are readable by software.
The transfer lines are passive connections between the front panel and internal connector J2 at
the back panel of the SPB. They are used to forward backplane signals to the front panel or vice
versa. They are protected by a serial 100 ohm resistor. The max. permitted current load is 50 mA.
Assignation of J4:
PIN ASSIGNMENT PIN ASSIGNMENT
1 Transfer 0 9 Status 3
2 Transfer 1 10 Status 4 − Input Status Site Monitor
3 Transfer 2 11 Ground − Input Status Site Monitor
6 Status 0 − Door Status (opt.) 14 Status 7
7 Status 1 15 Ground
8 Status 2
− J5, Trigger in; normally not used; jack, 4 mm

External trigger signal for telegram transmission purposes.
− J6, BITE I/O (status exchange); optionally use; connector RJ45, 8pin, female
The Status exchange can be used to interchange the BITE status between two Ground Stations
(GS A with GS B) at a dual site if the corresponding BITE test is enabled.
Ed. 10.07 2−9

AS 680/682 ADS−B
2.1.4.4 Single Board Computer (SBC)

See Fig. 2−11.
Control of the SPU, ADS−B process network and communication to the ATC application, the RCMS
or LCMS, is performed by the Single Board Computer (SBC). The SBC is a highly integrated, VMEbus
processor card based on the Thales product PowerEngine 7. The SBC is running under Linux.
The SBC provides the two Ethernet interfaces 0 and 1 of the Ground Station. The main external inter-
face 1 is used to connect the Ground Station to the actual ATM application and the Remote Control
and Monitoring System (RCMS) via an operational data network. The auxiliary Ethernet interface 0
is located at the front panel of the GTS module but provided by the SBC as well. Both interfaces are
separately driven by individual Ethernet controllers.
In addition to that, the SBC is equipped with a V.24 serial port, to which the local the Local Control
and Monitoring System (LCMS), consisting of a maintenance Laptop PC, can be connected using
a standard terminal program (minicom under Linux). This port allows to open a local command shell
and to perform initial configuration for the Ground Station (refer also to section 3.2.7). If the Laptop
does not include a serial connector but an USB port a special conversion cable (USB to Serial) has
to be used which is optional available.
The following table gives a definition of the indicators and controls of the SBC module.
LED Ethernet LED
Keyboard/Mouse (n.a.) Expansion slots (n.a.) Board reset Serial V.24 Ethernet
MicroSubD (RJ45, 10/100Base−T)
Fig. 2−11 Single Board Computer (SBC)

SBC Abort/Reset Key switch, neutral position: mid; manual reset
of SBC or abort program execution
LED, CPU (0)* red If lit, it indicates a checkstop condition.

green If lit, it indicates an activity of the CPU0
processor. Active when the CPU0 transfers
data on the system bus.
LED, CPU (1)* red If lit, it indicates a checkstop condition.

green If lit, it indicates an activity of the CPU1
processor. Active when the CPU1 transfers
data on the system bus.
Only used if CPU 1 option is available.
LED, PCI (32/64)* red Indicates an activity on the 32−bit PCI bus.
green Indicates an activity on the 64−bit PCI bus.
LED, RST* red If lit, indicates that board is in reset state.

green If lit, this indication is meaningless.
2−10 Ed. 10.07

ADS−B AS 680/682

SBC cont. LED, USR (0/1)* red The function of this LED is programmable by
green software and depends on the operating
system. Not used.
LED, USR (2/3)* red The function of this LED is software

green programmable and depends on the operating
system. Not used.
Ethernet conn. LED:
Speed green Lit:active connection at 100 Mbps; off:10 Mbps
yellow Spare/reserved
LINK/ACT green Lit: indicates an active connection; blinking:

indicates transmit or receive activity
yellow Off: Indicates no active connection
* These LED are bi−color LED (green/red)
NOTE: The small Abort/Reset key switch (ABT − idle − RST) is normally not used. The neutral
position is mid (idle). "RST" (move to right position) would initiate a reset of the processor
board and thus a reboot of the system software. "ABT" (move to left position) is intended
to interrupt program execution and to call a separate custom routine.
In the AS 680 Ground Station this custom routine does not exist nor is there any intended
use for this switch. Therefore actuating it would just stop the Ground Station from opera-
tion without a reboot.
CAUTION
Do not actuate the key switch to the left position "ABT". Avoid to actuate it accidentally.
Ed. 10.07 2−11

AS 680/682 ADS−B
2.1.4.5 Power Supply

See Figs. 2−4, 2−12.
Power supply of the SPU can be performed with a DC supply of nom. +24 V or an AC supply of 100
to 240 VAC from mains. For this purpose two converters are available including associated connector
assembly (located at the rear of the SPU). The connector assembly contains the appropriate input
filter and fuses (see Fig. 2−4). The SPU is normally switched on or off with the DC switch (I/0) at the
front of the SPU. The converters deliver the following supply voltages:
− DC/DC converter (make Telkoor):
input 18 to 36 V/15 A max.; output +5V/25 A, +3.3 V/ 36 A, +12 V/3 A, −12 V/0.5 A
− AC/DC converter (make Schroff):
input 100 to 240 V/4 A max.; output +5V/40 A, +3.3 V/ 40 A, +12 V/5.5 A, −12 V/2 A
The following table gives a definition of the indicators and controls of the power supply modules.
AC/DC or LED, Fault red Normally off; if lit, converter is faulty.
DC/DC LED Power green Normally on, DC input voltage available.
Power connector assembly (see Fig. 2−4):

AC/DC Mains Switch Switches AC/DC converter to mains (I/0)
Fuses DC 2x T6.3H, protects DC input supply line.
AC 2x T0.8H, 250 V, protects AC input supply line.
DC/DC converter AC/DC converter (option)
Fig. 2−12 SPU power supply options: DC/DC converter and AC/DC converter
2.1.4.6 Fan Unit

The fan unit is used to cool the internal subassemblies of the SPU. It is extractable for easy exchange.
Connector DC Fan (92 mm)
Fig. 2−13 Fan unit tray
2−12 Ed. 10.07

ADS−B AS 680/682
2.1.5 Site Monitor (SM)
See Figs. 2−14, 2−15.
The Site Monitor is normally associated to a Ground Station (GS). It is intended to allow verification
of correct GS operation independent of environmental conditions. To achieve this, the Site Monitor
injects its fixed test message directly into the ADS−B antenna monitor probe. Determining the re-
ceived signal level, the Ground Station is thus able to verify if antenna, LNA and cables are working
within their specification. The Site Monitor of one Ground Station (e.g. GS A) can inject directly this
message both to the antenna of GS A (RF OUT1) and optionally GS B (RF OUT2) for testing on site.
If not in use, the RF outputs have to be terminated with 50 ohms. In usual configurations, only one
of the two outputs are used. The second output must therefore be terminated with the 50 ohms
dummy load supplied.
In the standard configuration, Ground Station GS B receives the Site Monitor A signal via mutual an-
tenna coupling.
The Ground Station also checks for correct data contents and correct timing of site monitor message.
Periodically, the Ground Station generates an Asterix test target report triggered by a configurable
set of conditions, e.g. if the site monitor signal is received properly and no BITE failure exists. The test
target message contains the site monitor address, but the Ground Station GPS position and figure
of merit. An ATC application using ADS−B is thus able to determine whether a Ground Station is op-
erational or not based on received operational data. After power up, the Site Monitor will indicate a
fault for about 60 s while transmission activity starts immediately.
The following table gives a definition of the indicators and controls of the Site Monitor.
SM LED, TX green Flashing, if telegram is sent.
LED, FAULT red Normally out; lit, if SM function is faulty.
DC switch DC power on/off
LED, POWER green Lit, if power available and DC switch to on.
Power consumption/supply data label SM part number/serial number label
DC input 24 VDC nom; incl. fuses RF OUT1 RF OUT2 PE
Fig. 2−14 ADS−B Site Monitor (SM), rear view, connectors and identification labels
cutout for RF cable pass through Serial V.24 LED indications DC switch Status out
MicroSubD SubD
Fig. 2−15 ADS−B Site Monitor (SM)
Ed. 10.07 2−13

AS 680/682 ADS−B
A serial port (V.24) is available to connect the Local Control and Monitoring System (LCMS), consist-
ing of a maintenance Laptop PC. This serial connector (MicroSubD, 9pin), used to connect to the Site
Monitor with the aid of a standard terminal program (minicom under Linux), and to open a local com-
mand shell and configure for the Sit Monitor (refer also to section 3.2.8).
The status I/O interface connector (out, SubD, 9pin, female) provides the Site Monitor BITE status
summary to the Ground Station status input connector (at SPB, SubD,15pin, female). The status
signal is available at pin 1 (OUT) and 5 (GND) of the SubD, 9pin connector. Refer also to Fig. 3−1.
The site monitor can be mechanically integrated into the Ground Station, i.e. mounted into the same
19" rack (refer to section 2.1.6).
2.1.6 Rack Integration example of the AS680 Ground Station
Ground Stations and Site Monitors follow the 19" form factor for easy installation into existing racks.
The RF cables connecting the site equipment (Ground Station and Site Monitor) to the antennas are
usually placed at the rear of a 19" rack. While the Site Monitor has its RF connectors (N−type) right
at the rear, the RF input connectors (SMA) of the Ground Station are located on its front panels.
To relieve the more delicate SMA connectors of the Ground Station front from mechanical stress im-
posed by stiff RF cables, an Exchange Panel is supplied together with the appropriate cables. The
Site Monitor front panel has a recess to guide through these exchange cables from the rear to the
Ground Stations front. The whole configuration is shown in Fig. 2−16.
Side view, right hand rear front view GPS cable SPU
SPU THALES
THALES
SM
ADS−B RX cable SM
recess
19" rack Exchange Panel

GPS cable
N/TNC
SPU
SMA/N ADS−B cable
N/N
SMA/N
recess
SM SM cable
RF OUT 1 N/N
RF OUT 2
50 ohms
load
Top view rear
Fig. 2−16 Proposal of arrangement and cabling of SPU, SM and Exchange Panel in 19" rack
2−14 Ed. 10.07

ADS−B AS 680/682
2.2 ADS−B GROUND STATION AS 682
See Figs. 1−3, 2−17.
The ADS−B Ground Station AS 682 builts a complete redundant ADS−B system system in a 19" cab-
ninet housing which comprises as basic component the AS680 Signal Processing Unit (SPU) and the
Site Monitor (SM). The SPU is built−in two times in a redundant design. Each SPU is powered by an
Uninterruptible Power Supply (UPS). The cabinet houses in addition a Data Switch device which is
used to connect the units within the cabinet to the remote RCMS via LAN.
Intrusion switch
Drawer, key−locked
SPU 1
Data switch
SPU 2
Site Monitor
UPS, basic unit 1
UPS, Extension 1
UPS, basic unit 2
UPS, Extension 2
Sockets, spare
Fig. 2−17 AS 682 Ground Station equipment, assembled in 19" cabinet

2.2.1 Physical Breakdown
See Fig. 2−18.
The Ground Station hardware architecture is shown in Fig. 2−18. The basic hardware architecture
of the SPU and SM is already shown in Fig. 2−2. The configuration for a ADS−B Ground Station
AS 682 includes the following main components:
− 1 omnidirectional ADS−B RX antenna for Mode S,
− 2 GPS antenna
− 1 Antenna Amplifier Unit (AAU); the AAU can be mounted with a support on a mast.
− 19" cabinet equipped with front and rear door, which comprises the following main components:
2x Signal Processing Unit (SPU) in redundant configuration,
Site Monitor (SM),
Data Switch,
2x Uninteruptible Power supply, dedicated each to one SPU,
Exchange Panel providing 4/2 RF connectors and RF divider for RX antenna signals
Ed. 10.07 2−15

AS 680/682 ADS−B
The AS 682 cabinet houses also an intrusion switch, front and rear, a key locked drawer, two eightfold
AC sockets with fuses, and the necessary guides and cabling.
RF divider Intrusion switch, front and rear

RX antenna GPS antenna
Mode−S GPS
RF RXU1 RXU2 RXU3 RXU4 GPS1 GPS2
2 1
RF RF Exchange panel cabinet rear
SPU 1
Data Switch
SPU 2 redundant
AAU
ADS−B Network
LAN
OUT2 50 ohm OUT1
Site monitor
SNMP
UPS 1
SNMP
Mains
UPS 2 redundant
AS 682 cabinet
Fig. 2−18 ADS−B Ground Station AS 682 architecture
2−16 Ed. 10.07

ADS−B AS 680/682
2.2.2 Data Switch, 16 Port Gigabit Ethernet
See Figs. 1−3, 2−19.
The SPUs and the UPS are interconnected to the ADS−B network via the 16 port Gigabit Data Switch.
Mains In (rear) Power LED Status and network activity LED RJ45 network connectors
Fig. 2−19 Data Switch, front view (example)
2.2.3 Exchange Panel 4/2

See Fig. 2−20.
To relieve the more delicate SMA connectors of the SPU from mechanical stress imposed by stiff RF
cables, the Ground Station AS 682 provides an Exchange Panel (4/2) together with the appropriate
cables to connect both the VHF RX input cables and the GPS input cable from RX/GPS antenna and
SPU 1 and 2.
RF out2
RF in
RF out 1
RF divider VHF RX Spare GPS antenna1

cabinet rear GPS antenna2
Fig. 2−20 Exchange Panel, rear side of AS682 cabinet
2.2.4 Uninterruptible Power Supply (UPS)

See Figs. 1−3, 2−21, 2−22.
The AS682 ground station is equipped with an additional rack−mounted uninterruptible power sup-
ply module (UPS, X1000 R) with extension pack, dedicated to one SPU each. These UPS are used
to supply the individual GS in case of a power supply failure.
An additional SNMP support card is available so that UPS parameters like battery loading status, time-
out configuration, voltages, alarms, etc. are available via SNMP. It is connected to the Data Switch
in order to provide network connectivity.
2.2.4.1 Controls and Display Function of Base Unit

See Fig. 2−22.
− ON−button
Turn on UPS system: By pressing the ON−button the UPS system is turned on.
Deactivate acoustic alarm: By pressing this button an acoustic alarm can be deactivated.
− Standby button
he UPS system switches to Standby mode when the Standby button is pressed. It is then switched
to Bypass and the inverter is off. The output sockets are supplied with voltage via the bypass if the
mains power supply is available.
Ed. 10.07 2−17

AS 680/682 ADS−B
Indication panel (LED) On and Stdby button

Base unit
front view
Fuse
additional SNMP board

and network connector
rear view
Mains out Interconnection Mains in
to extension
Extension pack
front view
rear view
Interconnection Security switch Interconnection
to base unit to extension 2, not used
Fig. 2−21 Uninterruptible Power Supply

− LINE−LED
The green LINE−LED lights up if mains voltage is applied to the UPS input.
LINE−LED blinks when the phase and neutral conductor have been reversed at the input of the
UPS system.
If LINE−LED and BATTERY−LED light up, the mains power supply is out of tolerance.
− BATTERY−LED
The orange−coloured BATTERY−LED lights up when the mains power supply has failed and the
inverter is being powered by the batteries.
− BYPASS−LED
The orange−coloured BYPASS−LED lights up when the UPS system is supplying voltage pro-
vided by the mains power supply system via the bypass.
− INVERTER−LED
The green INVERTER−LED lights up if the inverter is operating and powering the UPS output.
− FAULT−LED
The red FAULT−LED lights up and an acoustic warning signal is issued every second when the
UPS system is overloaded.
The red FAULT LED lights up and an acoustic warning signal is issued when the UPS system
is in fault condition. Press the Standby−button in order to turn off the warning tone.
2−18 Ed. 10.07

ADS−B AS 680/682
− Load and battery capacity LEDs
These LEDs signal the UPS system load if the mains power is available (normal operation):
1st LED 1−35 %
2nd LED 35−55 %
3rd LED 55−75 %
4th LED 75−95 %
5th LED 95−105%.
In the case of battery operation, the LEDs indicate the capacity of the batteries:
1st LED 1−35 %
2nd LED 35−55 %
3rd LED 55−75 %
4th LED 75−95 %
5th LED 95−100 %.
Fault LED Standby button

ON−button
Load and Capacity LED
Bypass LED
Inverter LED
Battery LED
Line LED
Fig. 2−22 Uninterruptible Power Supply, operating panel at base unit
Ed. 10.07 2−19

AS 680/682 ADS−B
2−20 Ed. 10.07

ADS−B AS 680/682
2.3 PERIPHERAL EQUIPMENT
2.3.1 Omnidirectional Antenna
See Figs. 2−2, 2−23.
The ADS−B RX antenna is derived from a well−proven world wide deployed DME antenna. It consists
of a number of identical, decoupled half−wave dipoles and phase feeding cables and transformer.
Its gain is about 11.5 dBi. The high gain of this antenna is achieved by a vertically focussed diagram
that is elevated by an uptilt of ca. 2°. It is important that the antenna is mounted to an exact upright
position so that the main lobe remains close to the horizon in all directions.
bottom view, connectors
RF out
RF test in (GS1) RF test in (GS2)
ANTENNA
connector
N N N
M1 M2
mounting
clamp
Radome cover
OL
power supply for obstruction lights

not used
Fig. 2−23 Omnidirectional antenna
2.3.2 Antenna Amplifier Unit (AAU) with mounting Kit and Weather Protection
See Fig. 2−24.
The AAU is mounted as close as possible to the omnidirectional antenna (cable length <2 m). It
serves to optimize the system signal−to−noise ratio and to compensate cable attenuation. It has a
gain of approx. 15 dB and a noise figure below 0.7 dB. It is DC powered via the RF output cable from
the Ground Station receiver unit RXU. The DC supply can be interrupted with a jumper on the RXU
board. A passive lightning protector stub and a 1090 MHz band−pass filter are also part of the assem-
bly as shown in Fig. 2−24 below. To avoid overload an optional HF limiter at the RF input is available.
NOTE: If the AAU is not powered up it will not provide gain but will attenuate the signal. Therefore
it is crucial to verify that the supply voltage is available.
1 Filter (optional) AAU assembled to support 1 2 3 7a
2 Input limiter (optional)
3 Earthing cable between 11
housing base and cover
4 Input connector, from
VHF antenna, including
Î
lightning protector (optional)
Î
5 Earthing bolt
6 Output connector to RXU
ÎÎ
7 AAU housing base
7a AAU housing cover 8
ÎÎ
8 Low−noise amplifier
9 Mast support 10
10 Mounting base 9 4
11 Weather protection 7 6 5 AAU housing, opened
Fig. 2−24 Antenna Amplifier Unit (AAU) with mounting kit and weather protection
Ed. 10.07 2−21

AS 680/682 ADS−B
The AAU device comprises the housing with Low Noise Amplifer (LNA) and following options:
Ref. No. 83142 75210 with lightning protection for RF IN, RF filter
Ref. No. 83142 75310 with lightning protection for RF IN, RF filter, input limiter
2.3.3 GPS Antenna

See Figs. 2−2, 2−25.
The GPS antenna (model AT575−68, Part No. 72600 28001) is a receiving antenna for the L1−band
(1572.42 MHz). It receives the SIS signals from the up to 24 satellites of the Global Positioning System
(GPS). The Antenna supplies the GTS DG14 receiver within the SPU. The GPS antenna is an active
unit which is supplied with +5 VDC by the antenna RF cable. The antenna is mounted with four screws
(M3) to an adapter. A mounting kit comprising a tube and 2 clamps is optional available for elongation
of the adapter pedestal and easier fixing to an appropriate support.
GPS antenna RF connector GPS antenna and mounting accessories

bottom view
GPS antenna
RF connector (TNC)
RF out
Gasket
GPS antenna adapter
TNC
Mounting Kit (option) with:

mounting tube and
clamps (2x)
∅
990 mm 25 mm
Fig. 2−25 GPS antenna and mounting accessories
2−22 Ed. 10.07

ADS−B AS 680/682
2.4 REMOTE/LOCAL CONTROL AND MONITORING SYSTEM (RCMS/LCMS)
The RCMS functionality is hosted on a standard PC platform (Fig. 2−26) under the operating system
Linux. The basic system includes the necessary software licenses as well as a suitable standard desk-
top PC, e.g. type HP Compaq D530, with dual 19" TFT screen output, 40 GB Harddisk, DVD/CD−
writer, etc. The RCMS is the platform for a number of tools as illustrated in Fig. 2−27.
ATC Center
LAN
Fig. 2−26 RCMS subsystem configuration (example equipment)
Ethernet
MTSC
SNMP Master Technical System Control
V.24 AS 680 TSD

Ground Station Asterix CAT 021 Technical Situation Display
Basic configuration ARC ARP

Asterix recorder Asterix replay
RRC
Raw data recorder
Maintenance Laptop Logfile

Raw data
Raw data Logfile
for Test Generator only
Excel
RRP RAC
Raw data replay Raw data to
Asterix converter Asterix CAT 021
MTSC Master Technical System Control, provides overview status RRC Raw Data Recording Tool, to log raw data as received on Mode S level
of entire system (group of remote sites) (only RCMS) by the Ground Station hardware (ADS−B not decoded)
TSC Technical System Control, provides detailed view of a single RAC Raw Data to Asterix Converter, to replay raw data, to decode the ADS−B contents
Ground Station’s status, allows configuration changes, SW updates, etc. and to output Asterix data e.g. to the TSD. Operation similar but not identical to a
RRP Raw Data Replay Tool, to replay logged raw data to the test generator Ground Station.
of the ADS−B Test Bed TSD Technical Situation Display, plan view of ADS−B traffic as reported via Asterix
ARC Asterix Recording Tool, to log Asterix target reports target reports
ARP Asterix Replay Tool, to replay logged Asterix data to a destination (e.g. TSD)
Fig. 2−27 AS 680 tool chain
Ed. 10.07 2−23

AS 680/682 ADS−B
As illustrated in Fig. 2−28 below, the RCMS additionally provides several auxiliary tools for CD/DVD−
writing, text editing, pocket calculator, screenshot utilities, image and PDF viewers, etc.
RCMS
MTSC TSC ADS Tools

ADS−B B Miscellaneous Tools
TSD Burning application
TSD−Config Nedit
ARC Calculator
ARP Capture Screen 0/1
RRP Image Viewer
RAC
PDF Viewer
RRC
Terminal
Fig. 2−28 RCMS subsystem tools
Additionally, a Local Control and Monitoring system (LCMS) is used, built with a maintenance laptop
hosting also most of the RCMS tools. The LCMS is intended for local maintenance and test activity,
and recording on site.
LCMS
TSC ADS−B
ADS Tools
B Miscellaneous Tools
TSD Burning application
TSD−Config Nedit
ARC Minicom
ARP Calculator
RRP
Capture Screen
RAC
Image Viewer
RRC
PDF Viewer
Terminal
Fig. 2−29 LCMS subsystem tools
System−wide remote control and monitoring for the system hardware and software is handled by
means of the simple network management protocol (SNMP), a well−proven industry standard for net-
work management.
2−24 Ed. 10.07

ADS−B AS 680/682
SNMP is an asynchronous query/answer protocol based on the connectionless transport protocol
UDP. The controlled unit must have one or more local SNMP agents or daemons having access meth-
ods to the parameters under control.
The controlling entity is also known as SNMP manager. Both the agent and the manager have the
same description of controlled parameters within the so−called management information base
(MIB). Four transaction types are basically provided: get parameter, set parameter, get next parame-
ter and trap, the latter can be used for event oriented signaling. Most network components and com-
puter operating systems on the market are already equipped with SNMP agents and come with a spe-
cially adapted MIB. New components are made known to the SNMP manager by including their MIBs.
ADS−B Ground Stations are monitored, configured, tested and controlled using an SNMP manage-
ment program that connects to the Ground Station’s SNMP agents. SNMP covers the complete con-
figuration, operational parameters, control commands (reset, switch−over, disable output, etc.) and
the full BITE and status information (including such details as the individual tasks priorities of the SPC
software). Remote monitoring and control via SNMP is possible via the ground network in the same
way as locally.
The SNMP access is provided on a separate logical IP port. Multiple external SNMP managers can
be connected at the same line via a separate (auxiliary Ethernet interface) and/or the same physical
network connection as the operational data stream (main Ethernet interface). As the SNMP imple-
mentation allows sensitive commands and actions, a role concept with specified user access levels
and authentication is implemented. Notably for the remote software upload feature, a dedicated cyclic
redundancy check mechanism was implemented to verify data and code integrity prior to accepting
a new software from the network at the Ground Station.
The SNMP manager runs on a dedicated Remote Control and Monitoring System (RCMS), a PC−
based software application, called TSC, running under Linux Operating System. In addition to the
SNMP manager, the RCMS integrates also logging and replay tools, and an ADS−B Display.
2.4.1 Technical System Control (TSC)

See Figs. 2−27, 2−30.
The RCMS includes the Technical System Control (TSC), a dedicated SNMP manager that extends
the standard MIB by a few useful add−on functions based on a proprietary protocol. The main func-
tionality of the TSC is to monitor the state of the Ground Stations and to alarm their administrator in
case of a malfunction. In addition to that, the TSC is used to
− inspect and change all parameters of the Ground Stations
− log the system state and any configuration change to a file and a log window on screen
− manage user roles with different access rights
− allow rebooting the Ground Stations remotely
− allow updating the Ground Station software
Parameter settings, status changes and TSC user activities are time stamped and logged onto hard
disk.
The TSC provides a BITE status summary for the Ground Station as a whole and shows its operational
state (operational, maintenance, warning, fault). Parameter accessibility is managed using a user role
concept with each role having dedicated access rights (read−only, read/write, or not accessible) and
views. User access is secured using a password protected login procedure.
A complete description of parameters and screenshots of all TSC pages is given in section 4.2.
Ed. 10.07 2−25

AS 680/682 ADS−B
Fig. 2−30 Detailed BITE Status display on RCMS (example)
2.4.2 Technical Situation Display (TSD)

See Figs. 2−31, 2−32.
The Remote Control and Monitoring System platform is also used as a simple Technical Situation Dis-
play (TSD) to display in real time the ADS−B traffic situation as acquired by a selected Ground Station.
Titlebar
Menubar
Toolbar
Detailed Map View

Target View (Situation
Display)
Statusbar
Fig. 2−31 ADS−B Technical Situation Display (example)
2−26 Ed. 10.07

ADS−B AS 680/682
The traffic situation is presented on a full−featured electronic map organized in layers representing
different object types like runways, taxiways, buildings, rivers, cities, roads, boundaries, etc. Individ-
ual layers can be enabled or disabled. The Technical Situation Display (’ADSB Display’) allows zoom-
ing, panning, rotation, layer switching, history setting, position/distance measurement, different
symbology, etc.
Targets are shown as symbol with track history and a short label attached. Targets of interest can be
selected with the mouse and their detailed full Asterix report data items can be shown in a side panel.
This allows easy online analysis of an aircraft’s ADS−B performance. The Technical Situation Display
accepts Asterix cat 21 data as an input to its network port. In addition to showing live traffic from a
selected Ground Station set, replayed or simulated data can be shown in the same way. They are
usually marked as simulated data. A more detailed description of the Technical Situation Display and
its use is given in section 4.4.
The Technical Situation Display is configured using an XML−based configuration file that can be con-
veniently edited with a dedicated Display Configuration tool (see section 4.4.2.1).
Fig. 2−32 Display Configuration tool for the Technical Situation Display (example)
2.4.3 Recording and Replay
Another functionality of the RCMS is recording and replay both ASTERIX CAT 21 data and raw de-
coded Mode S data (i.e. telegram contents, confidence bits, time of arrival, power level, etc.) as re-
ceived by the Ground Station hardware. Recorded data are stored either in readable ASCII format
or as binary file in order to conserve hard disk space.
While recording Asterix data, the tool is able to display the decoded output on the screen, to store
everything in a format readable by standard spreadsheet programs and to copy the recorded data
to another network address and port. The replay tools allow to select partial replays, faster/slower
than life replays, etc. Depending on the available ground network bandwidth raw data logging could
also be done from a remote station.
More details about all application tools may be found in Chapter 4.
Ed. 10.07 2−27

AS 680/682 ADS−B
2.4.4 Raw Data to Asterix Conversion
Recorded Raw Data represent the actually received messages as seen by the Ground Station’s signal
processing hardware. These can be inspected on an individual message basis as in the Raw Data
tools or converted to Asterix target reports, almost similar to the Ground Station processing (a number
of restrictions apply). This is an opportunity to verify data content offline without using the actual
Ground Station.
The Raw Data to Asterix Converter (RAC) is able to output Asterix data either fully decoded, together
with the respective Raw input data, or as Asterix data stream that could drive the ADS−B Display
More details about the RAC tool is available within Chapter 4.
2−28 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Installation and Setup
CHAPTER 3
INSTALLATION AND SETUP
3.1 INSTALLATION
3.1.1 General
The installation of the ADS−B Ground Station AS 680/682 equipment and the RCMS equipment in
the ATC centers depends on local conditions. The equipment can be easily integrated in existing envi-
ronment (e.g. existing buildings on remote sites or an ATC supervisor room). This means that the
illustrations do not show a concrete mounting procedure but the interconnection of the individual sys-
tem items. Recommendations and installation requirements are listed in section 3.1.6. The difference
of AS 680 to AS 682 is that the AS 680 consists of individual equipment to be integrated by the cus-
tomer while the AS 682 is a redundant equipped station already assembleded in a 19" cabinet.
The environmental conditions, preparations and given technical facilities of the installation sites have
to be in accordance with the technical characteristics as described in chapter 1, section 1.3. Cables
indicated as 1) in Figs. 3−9 to 3−11 are provided by the customer. Also mounting facilities for equip-
ment and antenna or cable run are to be provided by the customer. Verification test procedures after
site installation and a related installation report form are described in section 3.6.
3.1.2 Hardware Items for Installation
3.1.2.1 Ground Station AS 680
The following table lists the hardware and software items of the ADS−B Ground Station AS 680.
Hardware Item P/N Remark
ADS−B Ground Station AS 680 comprises individual equipment
Signal Processing Unit DC/DC 83142 71030
− GTS DG14 83142 71600
− SBC 83142 71230
− SPB 83142 71301
− RXU2 83142 71503 Replaces RXU1, Ref.No. 83142 71502
− DC/DC converter 58142 30510
− DC kit 58142 30610
− Fan Unit 58142 30400
− Dust filter mat 58142 30410
Signal Processing Unit, AC/DC option 83142 71020 used if mains supply is provided
− AC/DC converter 58142 30500
− AC kit 58142 30600
Option: Mounting kit for 19" rack 22731 28001 consists of 4 screws, 4 washers, 4 cage nuts
Option: Exchange panel 35490 28061 used to interconnect RF cables
Site Monitor 61460054
GPS Antenna 72600 28001 incl. adapter
Option: mounting kit for GPS antenna 58142 50020 incl. mounting tube 34450 28021, 2 clamps
ADS−B RX Antenna 97980 28192
Option: Mounting frame for antennas xxxxx xxxxx used individually for antenna mounting on site
AAU (ADS−B Antenna Amplifier Unit) 83142 75100 incl. LNA unit, mounting kit, weather protection
− LNA−Unit incl. housing 83142 75210 incl.lightning protection of RF IN, RF filter
− LNA−Unit incl. housing 83142 75310 incl.lightning prot. of RF IN, RFfilter, input limiter
− LNA−housing mast support (mounting kit) 35380 28051
Cable set ADS−B (optional) 58142 40020 Refer to 3.1.4.
Ed. 10.07 3−1

AS 680/682 ADS−B
Installation and Setup Description, Operation and Maintenance
The following table lists the hardware and software items of the Ground Station AS 682.
ADS−B Ground Station AS682 cabinet 83142 70200 preassembled, dualized equipment
Signal Processing Unit, AC/DC option 83142 71020 2x
− GTS DG14 83142 71600
− SBC 83142 71230
− SPB 83142 71301
− RXU2 83142 71503 Replaces RXU1, Ref.No. 83142 71502
− AC/DC converter 58142 30500
− AC kit 58142 30600
− Fan Unit 58142 30400
− Dust filter mat 58142 30410
Exchange panel 4/2 35490 28066 used to interconnect RF cables incl. RF divider
− RF divider 49915 28050 used to split RF IN to both SPU/RXU devices
Site Monitor with AC/DC plug−in power supply 61460054 1x
Data Switch (Longshine) for networking 97528 28200 16 port Gigabit Ethernet Switch
Uninterruptible Power Supply Xantos RS1000 97541 28006 2x, incl. opt. UPS WEB/SNMP manager CS121
− UPS WEB/SNMP manager CS121 RS1000 97541 28008
Uninterruptible Power Supply Extension Pack 97541 28007 2x, dedicated to RS 1000 each
GPS antenna 72600 28001 2x, incl. adapter
Option: mounting kit for GPS antenna 58142 50020 2x, incl. mounting tube 34450 28021, 2 clamps
ADS−B RX antenna 97980 28192 1x
Option: Mounting frame for antenna xxxxx xxxxx used individually for antenna mounting on site
AAU (ADS−B Antenna Amplifier Unit) 83142 75200 incl. LNA unit, mounting kit, weather protection
− LNA−Unit incl. housing (option) 83142 75210 incl.lightning protection of RF IN, RF filter
− LNA−Unit incl. housing (option) 83142 75310 incl.lightning prot. of RF IN, RFfilter, input limiter
− LNA−housing mast support (mounting kit) 35380 28051 1x
2x 8 socket strip with 10A fuse; 1x 9 socket strip 60110−202/−212 (part of cabinet)
Cable set AS682 (optional) Refer to 3.1.4.
3.1.3 Hardware Items for RCMS Installation
The following table lists the hardware and software items of the RCMS configuration at remote site.
Standard Personal Computer Type HP Compaq Evo D530 or similar
Additional subassemblies for standard PC:
− Graphics adapter, dual head Type Matrox G450 or similar
− Ethernet adapter 0, 1 Type Intel Ethernet Pro 100 or similar
TFT−LCD screen monitor 19" monitor
Cable Item P/N Remark

Cable set RCMS dual VGA−cable, power cables
3−2 Ed. 10.07

ADS−B AS 680/682
3.1.4 Ground Station System Cabling Set Definition
SM, Status (out) SPU, J4 Status (in) Status 1 1

GND 2 2
shielding soldered to socket 3 3
4 4
5 5
6 6
7 7
8 8
approx. 1 m 9 9
10 Status
SubD, 9pin, male LiYCY 4x0.14 SubD, 15pin, male 11 GND
12
1 5 1 5 13
6
Shield 14
6 15
front view front view
NOTE: used only for AS 680

Fig. 3−1 24028 28001, Status cable Site Monitor, SubD/9pin to SubD/15pin (used with AS 680)
SM, Status (out) SubD, 15pin, male Status SM1,2 1

2 1
1 5 3 2
6 4 3
approx. 1.5 m GND 5 4
6 5
SubD, 9pin, male LiYY 2x0.14 front view 7 6 Status door
8 7
9
1 5 SPU, J4 Status (in) 8
Shield 9
6
10 Status SM
11 GND
front view 12
13
14
Door intrusion status 15
cabinet front switch
SPU I/O (1)
SPU, J4 Status (in)
1
2
approx. 0.6 m
1 2 3
rear door 4
open/closed 5
6 Status door
1 2 7
cabinet rear switch 8
front door 9
open/closed Status SM
10
11 GND
Status door intrusion 12
13
14
15
NOTE: used only for AS 682 SPU I/O (2)
Fig. 3−2 240xx 28xxx, Status cable Site Monitor/Intrusion, SubD/9pin to SubD/15pin (AS 682)
ADS−B RX antenna AAU
approx. 2 m
N−Type, male N−Type, male
recommended: Cellflex 1/2"
Fig. 3−3 27288 04059, ANT AAU cable, RF, N−N
Exchange panel RXU or GTS DG14 RF in
approx. 1 m
N, straight panel bulkhead SMA, right angle plug
cable plug recommended: Suhner S−series
NOTE:
GPS: 27288 04140
SPU 1 (RXU): 27288 04141
SPU 2 (RXU): 27288 04142
Fig. 3−4 27288 04140 to 42, Ground Station internal RF−cable to Exchange Panel, RF, N−SMA
Ed. 10.07 3−3

AS 680/682 ADS−B
GS A/SPU A, SPB J6 BITE GS B /SPU B, SPB J6 BITE

GND 1 1 GND
T2OUT 2 2 T2OUT
T1OUT 3 3 T1OUT
4 4
5 5
R1IN 6 6 R1IN
RJ45 8/8 RJ45 8/8 R2IN 7 7 R2IN
approx. 2 m GND 8 8 GND
LiYCY 8x0.14
1 front view 1 front view
NOTE: This is not an Ethernet cable ! Standard colour: grey.
Fig. 3−5 24028 28002, BITE connection cable, RJ45, 8/8 to RJ45, 8/8, crossed
1 1
RxD 2 2 RxD
TxD 3 3 TxD
4 4
GND 5 5 GND
6 6
approx. 2 m 7 7 RTS
RTS
SubD, 9pin, male LiYCY 8x0.14 MicroSubD, 9pin, male CTS 8 8 CTS
9 9
1 5 1 5
6
6
front view front view
Shield
NOTE: Used, if also a maintenance data terminal , e.g. as LCMS, shall be connected to configure e.g. Site Monitor.
Fig. 3−6 24028 28003, LCMS serial cable, SubD/9pin to MicroSubD/9pin, crossed
GPS receiver, auxiliary Ethernet interface LCMS

TXD+ 1 1 RXD+
TXD− 2 2 RXD−
RXD+ 3 3 TXD+
not used 4 4 not used
not used 5 5 not used
approx. 1.8 m RXD− 6 6 TXD−
RJ45 8/8 RJ45 8/8 not used 7 7 not used
LiYCY 8x0.14 not used 8 8 not used
1 front view 1 front view

NOTE: Standard colour: yellow
Fig. 3−7 24028 28004, LCMS Ethernet cable (standard), 10/100Base−T, RJ45, 8/8, cross over
SPU RS232 Laptop USB

DCD 1
Serial to USB RxD 2
TxD 3
converter DTR 4 1 Vcc+
GND 5 2 data−
approx. 300 mm Converter 3 data+
DSR 6
RTS 7 4 GND
SubD, 9pin, female or MicroSubD, 9pin, female USB A, male CTS 8
RI 9
1 5 1 5
6
6
front view 1
front view Construction example !
Fig. 3−8 24028 xxxxx, LCMS Serial to USB adapter cable, SubD/9pin to USB A, optional
3−4 Ed. 10.07

ADS−B AS 680/682
3.1.5 Interconnection of System Items
ADS−B RX antenna A NOTE: GPS antenna A
bottom view RF cable to ADS−B antenna: 1/2" cellflex or similar bottom view
RF cable to GPS antenna: 1/4" cellflex or similar
1) up to 30 m
ANTENNA
connector RF out
N N N RF test in from RF out2 of GS B/SM B,
up to 30 m option
1) TNC
M1 M2
27288 04059
1)
AAU up to 10 m
RF out PE RF in
OL +12V DC in LP
N* 1) N*
not used 1)
up to 2m
up to 30 m
N+LP N+LP N+LP
outdoor
N indoor N N
1) 1)
THALES Mode S Ground Station SPU
from 1) 1)
SM B SMA RJ45
GTS
DG14
MicroSubD RJ45
I 24028 28004
opt. to LCMS
SPB
SubD15
Fault
Power
0
+ −
RXU
SMA
SPU, front view (SPU A)

24028 28001 27288 04135 N N
1) 27288 04135 N N
Status Exchange to GS B/SPU B (option)
24028 28002 Exchange panel (option)
pass through for antenna cables from SPU BITE signal
MAINTENANCE TX FAULT Power STATUS
THALES
ADS−B SITE MONITOR MicroSubD SubD9
SM, front view (SM A)
LCMS
RF test out to ADS−B RX antenna A/M1 24028 28003 to SPU or SM
DC in 24 V nom
1) 20...28 VDC RF out 1** RF out 2**
local DC + PE
supply − N N 1)
1)
SM, rear view (SM A) 1) 1)
RF test out to ADS−B RX antenna B/M2, option**
1) Provided by customer Ethernet
LAN
* Connector definitions: N, SMA, TNC, N+LP, MicroSub ** if not connected to antenna, it must be terminated with 50 ohm LP=Lightning protection to RCMS
Fig. 3−9 System cabling ADS−B Ground Station AS 680 (one station shown)
Ed. 10.07 3−5

AS 680/682 ADS−B
SPU subrack, rear SPU subrack, rear
18...36 VDC VAC 85V...264V
DC supply fuse Mains fuse

6.3AT/250V (2x) AC, 0.8AT/250V (2x)
plus (+)
Mains switch AC
0
I
minus (−)
nom. 24 VDC PE nom. 230 VAC PE
DC−Power AC−Power 1)
local supply 1) 1) local supply
1) mains 1) 1)
Equipped with DC/DC−converter Equipped with AC/DC−converter (option)

1) Provided by customer
Fig. 3−10 ADS−B Ground Station AS 680, SPU, power connection rear side
TSD
RCMS PC
Monitor 1
19" TFT example HP
PS/2
230VAC
RS232
Parallel
230VAC VGA 1
VGAint
Keyboard * Mouse*
rear view
USB
4x
Power cable
Audio
Power cable
VGA cable,
dual
Dual VGA
Eth 0 Eth 1
TSC
Monitor 2
19" TFT
Mains sockets
230 VAC
230VAC VGA 2
rear view
rear view
to/from
ADS−B LAN
1)
Power cable
1)
Mains 230 VAC
1) Provided by customer 1) local supply
* optional PS/2 connection 1)
Fig. 3−11 RCMS, system cabling
3−6 Ed. 10.07

ADS−B AS 680/682
ADS−B RX antenna NOTE: GPS antenna (1) GPS antenna (2)
bottom view RF cable to RX antenna: 1/2 cellflex or similar bottom view bottom view
RF cable to GPS antenna: 1/4" cellflex or similar
ANTENNA
not used
connector * Connector definitions: N, SMA, TNC, N+LP, MicroSub
N N N ** if not connected to antenna, it must be terminated
with 50 ohm RF out RF out
M1 M2 LP=Lightning protection
1) Provided by customer
TNC TNC
AAU
RF out PE
+12V DC in LP
27288 04059 1) 1)
OL
1) RF in up to 2m up to 10 m up to 10 m
N* N*
not used 1)
N+LP N+LP up to 30 m N+LP outdoor N+LP
Exchange Panel 4/2

N N
N VAC 100...240 V
1)
SMA
GTS
DG14
Fault
Power
RJ45
I
SPB
SubD9 SubD15
0
RXU
SMA
SPU, front view) (1) 27288 04141

N VAC 100...240 V 27288 04140
1)
THALES Mode S Ground Station SPU status
doors
SMA
GTS
DG14
Fault
Power
RJ45
I
SPB
SubD9 SubD15
0
RXU
SMA
SPU, front view) (2)

AC/DC plug−in 27288 04142
Mains sockets 27288 04140
230 VAC SM Status
bottom top 240xx 28xxx
STANDBY
MAINTENANCE TX FAULT Power
THALES
ADS−B SITE MONITOR MicroSubD SubD9
SM, front view SM1 SM1

20...28 VDC RF out 1** RF out 2**
+ PE
− N N 1)
mains
plug RJ45
SM, rear view DC in 24 V nom if not used terminate
with 50 ohm AS682 cabinet
to UPS mains distribution to Data switch
Fig. 3−12 System cabling ADS−B Ground Station AS 682 (1)
Ed. 10.07 3−7

AS 680/682 ADS−B
SPU subrack, rear Equipped with AC/DC−converter
VAC 85V...264V
Mains fuse
AC, 0.8AT/250V (2x)
Mains switch AC
0
I
nom. 230 VAC PE
AC−Power
mains
Fig. 3−13 AS 682, SPU power connection rear side

cabinet rear, top SPU1 1) Provided by customer
Mains sockets Fuse 10 A Cabinet door switch
230 VAC rear front
SPU1 RJ45 Ethernet, SNMP RJ45 Ethernet, SNMP (UPS 1 and 2)

SPU2
Status
doors
Data switch, front to SPU 1 ,2
RJ45 Ethernet
to ADS−B Network
SPU2
cabinet rear, bottom
Fuse 10 A 1)
Mains sockets
230 VAC
SM1/DC AC/DC conv.

plug−in
RJ45 Ethernet
SNMP
UPS XS 1000, rear (1)
UPS Ext. rear
RJ45 Ethernet
SNMP
UPS XS 1000, rear (2)
Earth bar
PE
UPS Ext. rear
cabinet front, bottom
Mains sockets 9x
230 VAC Mains terminals
Fig. 3−14 System cabling ADS−B Ground Station AS 682, Data Switch and UPS (2)
3−8 Ed. 10.07

ADS−B AS 680/682
3.1.6 Mounting Requirements and Recommendations
3.1.6.1 Installation Notes to Ground Station (RXU) and Antenna Amplifier Unit
1 ADS−B Ground−Station: If the the RXU subassembly in the SPU is intended to be used without
an AAU or other equipment is connected to it, internal jumper X3 of the RXU1 (Ref. No. 83142
71502) or X1 of the RXU2 (Ref. No. 83142 71503) needs to be removed. In addition, there is no
band−pass filter at the input of the SPU/RXU. If the RXU subassembly should be operated without
AAU, a separate dedicated 1090 MHz band−pass filter is needed at the input.
2 Antenna Amplifier Unit (AAU): The AAU requires a 12 VDC power supply otherwise it will not provide
any gain and attenuate the signal instead. If next to the ADS−B RX antenna a TX antenna is
installed, the AAU should comprise the RF limiter option to avoid RF input overload.
3. The recommendations are valid for all channels even only one channel is referred to.
3.1.6.2 Installing the ADS−B Antenna

To mount the antenna and the AAU preferably use pre−installed mounting assembly if possible. To
fulfill the installation criteria consider the following recommendations and mounting aspects:
− Ensure obstacle free line of sight to the aircraft.
− Avoid shadowing by tower structures.
− Avoid possibility of signal reflections.
− Mount antenna as high as possible, but respect cable length restrictions.
− Mount the antenna in a vertical position and align within ±0.5°.
− The antenna can be mounted on a stub or mast, max. 60.5 mm ∅ (see Fig. 2−23).
− Antenna fastening base shall have conductive connection to the tower (earth). Insulating material
or paint must not be used.
3.1.6.3 Installing the Antenna Amplifier Unit (AAU)

If the pre−installed mounting assembly is used, the AAU is already installed as part of it. To fulfill the
installation criteria consider the following recommendations and mounting aspects:
− The AAU assembly can be mounted on a stub (or short mast), min. 60.5 mm ∅.
− Always mount the AAU assembly in upright position, connectors toward bottom to provide proper
convection cooling and splash protection. Use the weather cover for protection against sun.
− The distance to the ADS−B RX antenna shall not exceed 2 m.
− Record the serial number in the installation protocol.
To connect the AAU perform following connections (refer to Fig. 3−9):
a) RF cable (e.g. optional cable 27288 04059) from AAU connector "RFin" to antenna "RFout"; cable
characteristics shall be similar to Cellflex 1/2", attenuation < 8 dB/100 m, cable length up to 2 m.
b) Earth cable to tower; recommended is a cable with more than 16 mm2 ∅. It shall be as short as
possible and be connected to the metallic tower structure.
The cable shall be fixed by mounting brackets or UV resistant cable ties. The cable shall have addi-
tional earthing/shielding to protect against lightning stroke.
The Low Noise Amplifier (LNA) input of the AAU is protected against surge and lightning by a quarter
wave stub. DC input voltages will be blocked. The AAU houses no serviceable parts.
Ed. 10.07 3−9

AS 680/682 ADS−B
3.1.6.4 Installing the GPS Antenna

To mount the GPS antenna preferably use the associated mounting material if possible. To fulfill the
installation criteria consider the following recommendations and mounting aspects:
− Ensure obstacle free line of sight to the satellite.
− Avoid shadowing by shelter and/or buildings.
− The mounting tube shall have conductive connection to earth.
− The antenna cable connector (TNC type) is inside the antenna adapter (see Fig. 2−25).
− Check correct fitting of gasket between antenna and adapter.
− The antenna can be mounted to an optional mounting tube with thread, L=990 mm, 25 mm ∅.
To connect the GPS antenna perform following connections (refer to Fig. 3−9):
a) RF cable from building to GPS antenna; the RF cable characteristics shall be similar to Cellflex 1/4",
attenuation < 15 dB/100 m. The cable length can be up to 20 m.
b) Earth cable to building; the earth cable shall be a cable with more than 16 mm2 ∅. It shall be as
short as possible and be connected to the earth of the shelter or building.
The cable shall be fixed by mounting brackets or UV resistant cable ties. The cable shall have addi-
tional earthing/shielding to protect against lightning stroke. The GPS antenna is supplied with +5 V
DC via the RF cable. Therefore the antenna output may not have a quarter wave lightning protector
because of DC blockage.
3.1.6.5 Performing the Outdoor Cabling
The outdoor cabling includes all cables outside the shelter or building:
a) ADS−B antenna cable from "RFout" (AAU or antenna assembly):
the characteristics shall be similar to 1/2" cellflex (attenuation < 8db/100m),
the cable length shall not exceed 30 m
b) Site Monitor cable to the antenna monitor probe (or antenna assembly):
the characteristics shall be similar 1/4" cellflex (attenuation <15db/100m),
the cable length shall not exceed 30 m
c) GPS antenna cable:
all cables shall have N−type male connectors (except GPS antenna input: TNC)
All cables shall be protected against lightning strokes or surge (primary protection) preferably at the
shelter entry. No filters are allowed for cables to GPS and AAU because they individually provide sup-
ply voltage for GPS antenna and AAU. Also no quarter wave lightning protectors are allowed (block-
age of DC); only gas filled protectors may be used. All cables shall be as short as possible, avoid
loops. Fix the cables with mounting brackets or UV resistant cable ties. Proper earthing is required:
use earth clamps every 2 meters.
3.1.6.6 Installing the Indoor Equipment Ground Station AS 680, Site Monitor
See Figs. 3−9, 3−10, 3−15.
This section contains general procedures for installation of the equipment in the shelter or building.
Mount the Ground Station (GS A) in the provided rack:
a) Fix the Ground Station with the supplied mounting material (screws, nuts and washers).
b) Be sure that the air inlet at the front panel as well as the fan outlet at the right side of the Ground
Station is free (minimum distance to rack cover: 40 mm).
3−10 Ed. 10.07

ADS−B AS 680/682
c) Mount the exchange panels at the back side of the rack (if possible) with the supplied mounting
material.
d) Connect the Ground Station ADS−B RF input (RXU) and the GPS antenna input (GTS) to the ex-
change panel by using the adapter cables 27288 04135; see also Fig. 3−15.
e) Connect the Ground Station to a DC supply (required connector: Molex 03−12−1026).
Side view, right hand rear front view GPS cable
SPU THALES
SPU
I
THALES SM
SM
ADS−B cable
recess
19" rack Exchange Panel

GPS cable
N/TNC
SPU
SMA/N ADS−B cable
N/N
27288 04135 SMA/N
recess
SM SM cable
RF OUT 1
N/N
RF OUT 2
50 ohms
load
Top view rear
Fig. 3−15 Cabling and arrangement example of Exchange Panel

Mount the Site Monitor (SM A) in the provided rack:
a) Put the Site Monitor in the rack directly below the Ground Station and fix it with the supplied mount-
ing material.
b) The cable to the Exchange Panel (if used) shall be guided through the recess in the Site Monitor
front panel; see also Fig. 3−15.
c) Connect the SM status cable to the Ground Station status input (SPB) using cable 24028 28001
d) Connect the Site Monitor to DC supply (required connector: Molex 03−12−1026).
Mounting the second Ground Station (GS B), if intended: follow previous instructions for GS A.
Mount the second Site Monitor (SM B), if intended: follow previous instructions for SM A.
3.1.6.6.1 Installing the Cabling within the Shelter or Building (AS 680)
All inputs of the Ground Station and the Site Monitor provide secondary surge protection. They re-
quire primary protection means at the shelter entry point. All RF cables shall be as short as possible,
loops have to be avoided.
Ed. 10.07 3−11

AS 680/682 ADS−B
All RF cables shall be equipped with N−type male connectors. The LAN connection to RCMS is pro-
vided by a customer supplied router on site. Install the following cables:
a) from Exchange Panel (RFin) to shelter/building entry (RF from ADS−B antenna):
the characteristics shall be similar to 1/2" cellflex (attenuation < 8 db/100 m),
the cable length shall not exceed 10 m.
b) from Site Monitor (RFout1) to shelter/building entry (to ADS−B antenna, connector M1)
c) from Exchange Panel (GPS) to shelter/building entry (from GPS antenna)
d) from BITE status connector on SM A front panel to GS A, SPB, status connector J4
use cable 24028 28001.
e) from BITE status connector on SM B front panel to GS B, SPB, status connector J4 (if intended);
use cable 24028 28001.
f) from status exchange connector on GS A, SPB J6 to status connector GS B, SPB J6 (if intended);
use cable 24028 28002.
g) LAN connection: from main Ethernet interface RJ45 connector of SBC/SPU to customer supplied
network router.
3.1.6.7 Installing the Indoor Equipment Ground Station AS 682

See Figs. 3−9, 3−10, 3−14.
This section contains general procedures for installation of the equipment in the shelter or building.
a) Fix the Ground Station with the supplied mounting material (screws, nuts and washers).
b) Check that local mains supply is switched off. Perform earthing connection to earth bar of cabinet.
Connect the Ground Station to the mains supply.
3.1.6.7.1 Installing the Cabling within the Shelter or Building (AS 682)
See Figs. 3−9, 3−10, 3−14.
All inputs of the Ground Station and the Site Monitor provide secondary surge protection. They re-
quire primary protection means at the shelter entry point. All RF cables shall be as short as possible,
loops have to be avoided. All RF cables shall be equipped with N−type male connectors. The LAN
connection to RCMS is provided by a customer supplied router on site. Install the following cables:
a) from Exchange Panel (RXU1 and RXU2) to shelter/building entry (RF from ADS−B antennas):
b) from Site Monitor (RFout1 and RFout2) to shelter/building entry (to ADS−B antennas for channel
A and Channel B, connector M1): the characteristics shall be similar to 1/4" cellflex (attenuation
< 15 db/100 m), the cable length shall not exceed 10 m.
c) from Exchange Panel (GPS) to shelter/building entry (from GPS antenna)
d) LAN connection: from main Ethernet interface RJ45 connector of Data Switch to ADS−B commu-
nication network, e.g. customer supplied network router.
3−12 Ed. 10.07

ADS−B AS 680/682
3.1.6.8 Final Installation Check
Before the Ground Station is switched to operation, check all installation items:
− cabling of equipment and earthing connections
− tight cable fitting, no cable bents
− tight fitting of outdoor equipment
− power supply connections
Check at Ground Station equipment:
a) Check that DC supply jumper on the Ground Station RXU board is inserted.
b) To check the value of the supply voltages for the antenna preamplifiers, switch on the Ground Sta-
tion by setting the DC power switch on front panel to I" (local DC supply has to be set to "on" too).
c) Check the supply voltage for the AAU/LNA at the RF cable on the LNA RFout connector and regis-
ter it in the installation report form in section 3.6. The value has to be between 11.2 and 12.2 V.
d) Check the supply voltage for the GPS antenna at the RF cable on the antenna output and register
it in the installation report form in section 3.6. The value has to be between 4.0 and 5.5 V.
e) Finally switch off the Ground Station and fix and seal the cables at the antennas.
A site verification test procedure and a related installation report form is given in section 3.6.
Ed. 10.07 3−13

AS 680/682 ADS−B
3−14 Ed. 10.07

ADS−B AS 680/682
3.2 SWITCHING ON GROUND STATION ON SITE
3.2.1 Status of Installation
Before operation, the system must be completely installed as follows:
− ADS−B Ground Station (AS 680 or AS 682), installed as per section 3.1.
− Power supply, installed.
− Antennas installed and cabling complete.
− Network connected.
− Mains AC voltage or, if DC version, DC voltage must be in accordance with assigned input voltage
range.
3.2.2 Status of the System

− Local DC supply and local mains supply, if AC/DC version used, off.
− DC switch on SPU and SM in off−position ("0"); with AC/DC version: also mains switch at back-
panel of SPU to off ("0").
NOTE: The Ground Station and the Site Monitor are normally configured and preset for operation
in the factory before delivery. This means that normally no basic software installations
have to be performed. Depending on antenna characteristics and local radio environment
an adaptive adjustment of the receiver sensitivity (SPU, RXU) may be necessary. Refer
for the appropriate measures to section 3.2.6 and perform the steps for setting the value
with the oscilloscope.
3.2.3 Uninterruptible Power Supply (UPS), Startup and Operation

NOTE: Regard also the information and the safety instructions of the original manufacturer user
manual of the Xantos UPS equipment.
WARNING
Risk of electric shock. Even after the unit is disconnected from the mains power supply
(building wiring socket outlet), components inside the UPS system are still connected to
the battery and are still electrically live and dangerous.
Before carrying out any kind of servicing and/or maintenance, disconnect the batteries
and verify that no current is present.
Only persons adequately familiar with batteries and with the required precautionary mea-
sures may exchange batteries and supervise operations. Unauthorised persons must be
kept well away from the batteries.
− Verify that the security switch on the back side of the battery extensions is in ON position.
− Switch on local mains AC supply.
As soon as the UPS is connected to mains supply, the UPS outlet sockets are now powered. This
is indicated by the LED LINE and BYPASS.
Fully charge the batteries of the UPS system by leaving the UPS system connected to the mains
for approx. 1 to 2 hours. The UPS system can also be use directly without charging it, but the stored
energy time may then be shorter than the nominal value specified.
− Press the ON−button "I" on the front panel to start the UPS system.
Load capacity LEDs first light up simultaneously, then one after the other. After a few seconds the
INVERTER−LED lights up and the BYPASS−LED turns off. The UPS is now functioning normally.
Ed. 10.07 3−15

AS 680/682 ADS−B
3.2.4 Switch On Ground Station

a) DC/DC version used: Switch on local main DC supply.
AC/DC version used: Set AC switch at backpanel of all SPU to on ("I")).
b) Set DC switches at front panel of all SPU and SM to on ("I"). The systems start. The initialisation
procedure takes some time while LED "Fail" of SPB of the SPU is lit, others are on or slow flashing.
Finally all LED of the SPB are checked, before the system is ready for operation. No fault indication
should be noted after the systems have start up.
c) To perform initial Ground Station and Site Monitor settings see section 3.2.7 and section 3.2.8.
NOTE: If a LCMS Laptop is used connect the LCMS Laptop to the serial interface MicroSubD con-
nector of the Ground Station respectively Site Monitor (or, for GS, the auxiliary Ethernet
connector of the SPU/GTS DG14) using the suitable interface cable (zero modem cable).
If the LCMS Laptop used does not include a serial interface connector but an USB port,
a special conversion cable (USB to Serial) has to be used. This cable is optional available.
Further setup of the application software and user roles are described in section 3.3. The basic prepa-
ration of the RCMS/LCMS and the installation of operating and application software is described in
in Chapter 8. After setup, a site verification test procedure and a related installation report form is given
in section 3.6.
3.2.5 Check and Adjustment of the GS Receiver Frequency (RXU)
The optimal performance of the Ground Station depends on the SPU/RXU local oscillator which is
factory adjusted to its intended frequency of 1030 MHz ±1 MHz. To ensure the performance, it is man-
datory to verify this frequency during installation. It is also recommended to perform this check as
preventive maintenance item every 2 years to ensure continuous performance of the SPU.
Perform for RXU1 (83142 71502) only: If necessary adjust frequency as described in section 7.1.7.1.
NOTE: The RXU2 (83142 71503) requires no adjustment of the local oscillator G1.
Perform the following procedure to check the frequency (refer to Fig. 3−16):
a) Switch off the correspondent SPU to be checked. Remove RF cable from SPU connector RF In.
b) Withdraw RXU board until jumper X3 (RXU1) or X1 (RXU2) is visible. Open X3 (RXU1) or X1 (RXU2).
Insert RXU board again.
c) Connect the RF Generator to connector RF In; connect Digital Voltmeter to connector Monitor Out.
d) Set RF Generator to apply an RF signal of 1090 MHz and P= −80 dBm to connector RF In.
e) Switch on the affected SPU.
f) Vary the RF frequency about ±3 MHz at the RF generator to get a maximum DC voltage reading
at the Digital Voltmeter. The maximum should be within 1089 to 1091 MHz. If not, an adjustment
of the local oscillator frequency (LO) on the RXU is required. Refer to section 7.1.7.1.
g) Switch off the affected SPU. Remove measuring cables. Withdraw RXU board. Set X3 (RXU1) or
X1 (RXU2) again. Insert RXU board and connect RF cable as normal again.
SPU
top view Digital voltmeter SPU RF generator
000.0 1090 MHz

I
0 RF out
RXU Monitor Out RF In
RXU partly withdrawn. X3 or X1
Adapter cable SMA/BNC/Banana plug Cable SMA/SMA or adapter SMA/BNC
Fig. 3−16 Test setup frequency check of local oscillator of RXU
3−16 Ed. 10.07

ADS−B AS 680/682
3.2.6 Adjustment of the SPU/RXU Receiver Sensitivity Level
The SPU/RXU forwards a video signal to the SPB. The SPB input stage is DC coupled. All signals
(noise) below 300 mV will be discarded. The video signal contains a noise floor. Noise level depends
on radio environment, used antenna and cable length. The RXU provides an adjustable DC offset us-
ing a DIP switch (refer to 7.3.8) to adapt the actual noise to the trigger level:
− Noise floor below 300 mV: reduce detection of small signals (far aircraft).
− Noise floor above 300 mV: produce false detections
To adjust the SPU/RXU input sensitivity perform the following steps for each channel (Fig. 3−17):
a) Switch off the correspondent SPU to be checked.
b) Use of RXU1: Connect an oscilloscope to the monitor output of the RXU.
Use of RXU2: Connect an oscilloscope to the monitor output of the RXU. Jumper X2 is set to 1−2.
c) Switch on the affected SPU. Notice the noise value. If the level has to be adjusted:
− Switch off the correspondent SPU. Remove RF cable.
− Withdraw RXU. Set the DIP switch (refer to 7.3.8) to the convenient value (approx. 300 mV).
− Insert the RXU. Connect RF cable.
d) Switch on the affected SPU. Refer to the examples in Fig. 3−18 to 3−20 as adjustment help.
e) Repeat this operation until the required level is obtained. Switch off the affected SPU. Remove RF
cable and oscilloscope probe. Connect the RF antenna cable as normal. Switch on the affected
SPU for normal operation.
SPU Oscilloscope SPU
top view
RXU1 only
I
Ch1 in 0 from ADS−B antenna

Monitor Out RF In
RXU,
optionally plugged on
maintenance adapter
RXU
DipSwitch X2 (RXU2 only) Probe RF cable
Fig. 3−17 Test setup sensitivity level adjustment of RXU
Signal at monitor output (1)
Fig. 3−18 Receiver sensitivity level setting, signal at monitor output (1 of 3)
Ed. 10.07 3−17

AS 680/682 ADS−B
Signal at monitor output (2)
Signal at monitor output (3), adjusted
3−18 Ed. 10.07

ADS−B AS 680/682
3.2.7 Initial Ground Station Settings AS 680
Normally the setting of parameters will be done by the Technical System Control (TSC) either locally
on the LCMS or remotely via the RCMS. This requires that all network parameters are set correctly.
The initial setting related to the network parameters is performed via the serial interface using the
LCMS. After initial setting, the Ground Station (GS) is accessible by the LCMS via the auxiliary Ether-
net interface. All other settings will be done by the Technical System Control (TSC) on the LCMS.
Perform the following procedure:
a) Switch off the Ground Station. Log into the Ground Station by the serial interface: Connect the
LCMS to the serial interface of the Ground Station using the serial cable 24028 28003.
b) Switch on the LCMS and the Ground Station.
c) After booting, login as "supervisor " and enter the password.
d) Open a terminal, set the mouse pointer in it and press the left mouse button.
e) After entering the command minicom <enter> you are connected to the Ground Station and the
Ground Station prompt gs login: is displayed.
f) By entering supervisor <enter> followed by the password, the Ground Station command line
interface is displayed.
g) Set or check the initial settings of network parameters:
Entering the command cmdgs <enter> will show the values of all parameters. A single parameter
can be accessed by cmdgs get ‘parameter name’ <enter> . The value of a parameter can be
changed by cmdgs set ‘parameter name’ ‘value’<enter> . Verify the parameters (and change
them if need be) according to the following table:
Parameter Name Value Remark
groundstationIpAdr 192.168.23.35 IP address of main Ethernet IF (customer defined)
netmask 255.255.255.128 Netmask of main Ethernet IF (customer defined)
groundstationIpAdrAux 192.168.23.235 IP address of auxiliary Ethernet IF
netmaskAux 255.255.255.128 Netmask of auxiliary IF
defaultGateway 192.168.23.235 −
h) Confirm the network parameter changes by entering netconfig <enter> or press the reset but-
ton on the SBC to restart the Ground Station.
3.2.8 Site Monitor Settings AS 680

The operational parameters of the Site Monitor (SM) need to be set once during installation. The set-
ting will be permanently stored within the Site Monitor. The setting of the operational parameters will
be done by the serial interface (Maintenance Interface) of the SM.
Perform the following procedure:
a) Switch off the Site Monitor.
b) Set the operational parameters: Connect the LCMS to the serial interface of the site monitor using
the serial cable 24028 28003.
c) Switch on the LCMS.
d) After booting, login as "supervisor " and enter the password.
Ed. 10.07 3−19

AS 680/682 ADS−B
e) Open a terminal, set the mouse pointer in it and press the left mouse button.
f) After entering the command minicom <enter> you are connected to the Site Monitor.
g) Switch on the Site Monitor.
h) On the LCMS terminal window, the Site Monitor prompt
FM−VERSION: [1.1]
BITE STATUS: [OK]
is displayed.
i) Set or check the Site Monitor parameters:
Entering the command getall <enter> will show the values of all parameters. A single parame-
ter can be accessed by getpar ‘parameter name’ <enter>. The value of a parameter can be
changed by setpar ‘parameter name’ ‘value’ <enter>. Entering help <enter> will show all pa-
rameters and their valid values. Verify the parameters (and change them if needed) according to
the following table:
Parameter Name Value Remark

DF 18 Downlink format of Site Monitor messages
ADDRESS <3C3D0C> Use Mode−S address in SM messages (customer defined).
PERIOD 0.5 Repetition rate of Site Monitor messages
JITTER 1 Transmission period will be jittered.
j) Check the parameter setting by entering getall <enter> again.

k) Enter the command setall <enter> to store changes permanently in the flash EPROM.
3.2.9 Initial Ground Station Settings AS682

It is supposed that the initial GS settings (network parameters) have already be done by the Thales
ATM service personnel. The GS is ready for operation.
3.2.10 Site Monitor Settings AS682

It is supposed that the initial Site Monitor settings (operational parameters) have already be done by
the Thales ATM service personnel. The SM is ready for operation.
3−20 Ed. 10.07

ADS−B AS 680/682
3.3 STARTING THE RCMS AT REMOTE SITE
NOTE: It is supposed that the Linux operating system and the application software is already in-
stalled on the RCMS, i.e. ready for operation. Otherwise the installation procedures des-
cribed in Chapter 8 are required before.
For detailed information to the RCMS software structure, see chapter 4.
Starting the RCMS requires the following steps:

− Switch on the RCMS. Wait until the operating system is loaded (this takes a few seconds...)
− The operating system will be booted into the login screen.
− Login as ’supervisor’ or ’monitor’ (user account) to the Xfce desktop. A password is required.
− At the bottom of screen 0 the desktop panel provides the several icons to start up the ADS−B ap-
plications (see Fig. 3−21).
The user is now able to start up the various ADS−B applications by clicking on the corresponding
menu icons, e.g. click on the MTSC icon to start up the MTSC application (this takes a few seconds).
On screen 1 the MTSC main window appears, containing the title bar with the current user role and
the name of the RCMS machine.
A user with supervisor permission is now able to modify the configuration of the GS system or of the
MTSC application (see section 4.3.3).
If the user wants to get detailed information on a specific GS or the Supervisor wants to change para-
meters of a specific Ground Station, he can start the TSC application via the TSC icon on the desktop
panel (see Fig. 3−21).
MTSC TSC
Fig. 3−21 RCMS desktop panel to start up the MTSC and the TSC application (example)
Ed. 10.07 3−21

AS 680/682 ADS−B
3.4 CONFIGURATION OF RCMS/LCMS
The configuration of the RCMS/LCMS is located in the directory /usr/local/etc . Each ADS−B
application will get its configuration from this location.
The configuration consist of the following files:
Configuration file ADS−B application

recordasx.cfg ARC – Asterix recorder
recordraw.cfg RRC – Raw Data Recorder
replayasx.cfg ARP – Asterix Replayer
recordrawreplayasx.cfg RAC – Raw Data To Asterix Converter
recordrawreplayraw.cfg RRP – Raw Data Replayer
display.xml TSD – Technical Situation Display
gs_list.conf TSC − Technical System Control
data.xml MTSC− Master Technical System Control
3.4.1 Default Configuration
After installation of the RCMS/LCMS, a default configuration exists in the directory /usr/local/etc.
3.4.2 Site−specific Configuration
To get a site−specific configuration it is recommended to install a configuration package, e.g. for the
site ’Aena’ the package ’adsb_cfg_aena’ has to be installed.
The configuration package consists of site−specific configuration files for the ADS−B applications.
After installation, all applications will use this specific configuration. After de−installation of the config-
uration package the default configuration will be used again.
3−22 Ed. 10.07

ADS−B AS 680/682
3.5 FURTHER TSC CONFIGURATION
The TSC configuration consist of three parts:

S User role configuration (see section 3.5.1)
S Runtime settings (see section 3.5.2)
S Groundstation list (see section 3.5.3)
3.5.1 User Role Configuration

This section gives an overview of the TSC user role configuration. The user role configuration doesn’t
belong to the configuration described in section 3.4.
The TSC can be started in two different modes (user roles) depending on the account, the user has
logged in:
S Monitor User Mode
S Supervisor Mode
In the Monitor User Mode, the current status of the Ground Station can be monitored and a few opera-
tional parameters can be set. The Supervisor User Mode grants full access to all parameters of the
Ground Station.
The configuration files for these two modes are located in the configuration directory (.tsc_config)
of the TSC which is located under /usr/local/tsc.
The following naming convention applies to the configuration files:

[role]_user.conf
Considering only the roles Supervisor and Monitor, there are two files:
S supervisor_user.conf
S monitor_user.conf
During the start sequence of the TSC, the application is looking for a file in the .tsc_config directory
with the following pattern:
<current username>.conf
For the default user ‘monitor’ (of the group monitor) there is a link monitor.conf which is pointed to
the file monitor_user.conf. For the default user ‘supervisor’ (of the group supervisor) there is a link
supervisor.conf which points to the file supervisor_user.conf.
For example, if the user ‘smith’ starts the TSC, the software will look for the file smith.conf. If this file
does not exist, the application will use the monitor_user.conf file, instead.
To change the role of user ’smith’ from a monitor user to a supervisor just go to the .tsc_config
directory and create a symbolic link named smith.conf pointing to supervisor_user.conf:
ln −s supervisor_user.conf smith.conf
That is the way, how the user roles can simply be assigned to the corresponding users. Only the users
of the group supervisor may get write permission to the /usr/local/tsc and the .tsc_config direc-
tories.
Ed. 10.07 3−23

AS 680/682 ADS−B
3.5.2 Runtime Settings
The runtime settings of the TSC are user−specific. This means the settings files are located in the
home directory of the specific user. These files are generated by the TSC and must not be edited
manually.
The two settings files are located in the directory [home]/.tsc/settings/. [home] is to be replaced
with the user’s home directory, which is extracted from the environment variable $HOME. If this vari-
able is not set correctly, loading and saving of these files can fail.
The files are

[home]/.tsc/settings/settings_tsc.conf or
[home]/.tsc/settings/settings_startup_tsc.conf.
(see section 5.3.3 for details)
3.5.2.1 Settings File
The file settings_tsc.conf can be saved and loaded manually by the user or automatically by the TSC.
This depends on the TSC settings in the ’Settings’ menu (see section 5.3.3).
3.5.2.1.1 Starting Settings File
The settings_startup_tsc.conf file is loaded and saved automatically during TSC start−up and shut-
down, respectively. The following configuration parameters are stored:
S State of the window (normal or minimized)
S Size of the window
S Last selected page
S Logging parameters (log file directory, etc.)
S Size and position of the log message window
3.5.3 Ground Station List
The Technical System Control (TSC) is to monitor the Ground Station state and to alarm a user in case
of a malfunction. The TSC can be switched to control another Ground Station. This requires that the
TSC needs a list of available ground stations.
On a RCMS the Ground Station list of the MTSC is used by the TSC. The data file data.xml is located
in the directory /usr/local/etc .
To add or delete a Ground Station to the system (changing configuration), a user with supervisor per-
mission can perform that via the MTSC application (see section 4.3).
On an LCMS, where no MTSC is installed, the TSC is using its own gs_list.conf file. This file is located
in the directory /usr/local/etc . The file defines the available Ground Stations, how they can be
accessed, and their names. By default, the first Ground Station of the list will be connected.
3−24 Ed. 10.07

ADS−B AS 680/682
Changing to another Ground Station of the list has to be done via the corresponding menu in the TSC
application (menu ’Groundstation’, see section 5.3.2).
The following example defines a list of two Ground Stations, ’Melbourne’ and ’Brisbane’, within the
configuration file gs_list.conf:
global gsArray
set timeout 5
set retries 1
set netCommandSndPort 8080
set gsArray(1) [list Melbourne 149.204.178.236 $timeout $retries $netCommandSndPort]
set gsArray(2) [list Brisbane 149.204.178.101 $timeout $retries $netCommandSndPort]
(Parameters that can be changed by the user are printed in boldface.)
Ed. 10.07 3−25

AS 680/682 ADS−B
3−26 Ed. 10.07

ADS−B AS 680/682
3.6 SITE VERIFICATION TEST PROCEDURE AND INSTALLATION REPORT
This section suggests tests and procedures that the Installation Team can perform in order to verify
that a remote site has been properly installed and commissioned. The result is laid down in a Site
Installation Report (SIR). An appropriate form will be found in section 3.6.8.
3.6.1 Serial Numbers

Record all serial numbers into the Site Installation Report (SIR).
3.6.2 Mechanical Setup of Equipment

3.6.2.1 ADS−B Antenna
1 Verify that the ADS−B antenna is mounted vertical within ±0.5°.
2 Note the installed antenna height above ground to the SIR.
3 Take photos of the installed ADS−B antenna and its surroundings. If there are obstructions, docu-
ment their direction and distance from the antenna. A 360° panorama photo of the antenna envi-
ronment would be extremely valuable. Check box for ADS−B antenna photos on SIR.
4 Document the mounting configuration and antenna height (drawing with directions of compass
and rough distances). Include obstacles in the immediate surrounding of the antenna.
5 Verify that the antenna has conductive connection to the mounting assembly (i.e. no paint at the
contact surface). Check that the mounting assembly is correctly connected to the protective earth
bus bar.
3.6.2.2 Antenna Amplifier Unit (AAU)

1 Check that the AAU is mounted close to the ADS−B antenna so that the cable length between
antenna and AAU is less than 2 m.
2 Verify that the AAU protective earth strap is attached and correctly connected to the protective
earth bus bar.
3 Verify that the RF cables are correctly connected to the AAU:
input (with quarter−wave lightning protector) connected to the ADS−B antenna,
output connected to the SPU
3.6.2.3 GPS Antenna

1 Take photos of the installed GPS antenna and its surroundings. If there are obstructions, document
their direction and distance from the antenna. A 360° panorama photo of the antenna environment
would be valuable.
2 Document the mounting configuration and antenna height (drawing with directions of compass
and rough distances). Include obstacles in the immediate surrounding of the antenna.
3 Check that the GPS antenna mounting tube is correctly earthed.
3.6.2.4 Cables
1 Make sure that all cables are properly mounted according to the cable plan. Verify they are as short
as possible (no unnecessary loops).
2 Verify that the correct lightning protection is in place at the shelter cable entrance (for ADS−B RX
and GPS RX must be DC−pass type).
Ed. 10.07 3−27

AS 680/682 ADS−B
3 Verify that the earthing of all cables is done according to standard.
4 Make sure the blue exchange cables (between SPU/RXU, SPU/GTS and the arriving low−loss
cables) are properly connected and not twisted or sharply bent.
5 Verify that the second output of the Site Monitor (unused) is terminated using the supplied 50 ohms
terminator.
3.6.3 Electrical Connection of AAU, SPU, Site Monitor, active GPS Antenna
1 Make sure the Ground Station is properly connected to 24 V DC power supply and that a protective
earth strap is applied to the protective earth bus bar.
2 Make sure the Site Monitor is properly connected to 24 V DC power supply and that a protective
earth strap is applied to the protective earth bus bar.
3 Verify that jumper X3 on the SPU RXU is set to provide AAU with 12 V DC feed on its input RF line.
4 When the SPU is powered (switched on) measure the voltage arriving at the AAU output. Discon-
nect the cable from the AAU and measure the voltage between the cable’s centre conductor and
shielding. The measured voltage must be between 11.2 and 12.2 V DC. Document the measured
voltage in the SIR.
5 When the SPU is powered (switched on) measure the voltage arriving at the active GPS antenna
cable output. Disconnect the cable from the antenna and measure the voltage between the cable’s
centre conductor and shielding. The measured voltage must be between 4.0 and 5.5 V DC. Docu-
ment the actual voltage in the SIR.
3.6.4 RF properties of Antenna cables and Receiver adjustment

1 Measure the cable insertion loss at 1090 MHz of ADS−B antenna−AAU cable, ADS−B cable, Site
Monitor Cable and document the result within the SIR.
2 Connect a suitable digital storage oscilloscope to the monitor output of the RXU.
3 Set the DSO input characteristic to high impedance (e.g. 1 Mohm) and DC coupling, trigger to au-
tomatic.
4 Switch on the Ground Station.
5 Verify that the noise level is shown on the DSO screen at +300 mV (refer also to section 3.2.6).
6 Make a screenshot to document the setting and check the appropriate box in the SIR.
3.6.5 Configuration of Site Monitor

1 Switch on Site Monitor.
2 Verify Site Monitor BITE Status is OK (Fault LED goes off after 1 min).
3 Connect the LCMS serial cable to the Site Monitor maintenance port and the other side to the
USB−to−serial converter. Connect the USB−to−serial converter to the LCMS.
4 Start the LCMS and login as supervisor. Supply the appropriate password.
5 From the desktop start the terminal application minicom from either the Misc. Tools menu of the
application panel or the context menu (right mouse button on desktop background).
6 Enter the command getall<enter> to retrieve and document the current site monitor configu-
ration.
3−28 Ed. 10.07

ADS−B AS 680/682
7 Verify that the site monitor responds with the following output:
DF: [18]
ADDRESS: [<24−bit address intended for that site monitor, e.g.
7CF726>]
PERIOD: [0.5]
JITTER: [1]
FW−VERSION: [<current FW Version>]
BITE−STATUS: [OK]
8 Leave minicom by entering CTRL−a and then x. Disconnect the serial cable
9 Connect Ethernet crossover cable to Ground Station Auxiliary Port located at the GTS module in
the upper left slot of the SPU. Connect the other side to the LCMS Ethernet port.
10 Start the Ground Station.
11 Verify that all failure LEDs are off after the Ground Station boot up sequence.
12 Start the TSC from the LCMS desktop.
13 Verify that the Ground Station parameters are properly retrieved by the TSC.
14 In the TSC, go to the Network page
15 Enable the Raw Data Stream Output.
16 Verify that the IP−Address for the Raw Data Stream is configured as 192.168.23.2
17 Verify that the Port for the Raw Data Stream is configured to 50001
18 Change the visible desktop window by selecting one of the blue areas within the desktop panel
at the bottom of the desktop.
19 From the ADS−B Tools menu select the Raw Data Recording Application (RRC).
20 On the RRC Parameter page, set the interface, from which the RRC will read data, to lcmsmaint
and the port to 50001.
21 Disable the output to file checkbox. Enable the output to screen checkbox.
22 Go to the RRC Filter page and disable the filters Record only groundstation and Re-
cord only downlink format.
23 Enable the filter Record only Mode S address (HEX) and enter the site monitor’s 24 bit
address as it should be according to the planned configuration.
24 Switch to the Screen Output page and start the recording by clicking on the red button below
the File menu or by selecting the menu item Command|Record .
25 Verify that raw data are received.
26 Verify that column no. 6 contains the value 18 corresponding to the downlink format DF−18 that
the site monitor is configured to send.
27 Verify that column no. 7 contains the 24−bit address that the site monitor is configured to send
(e.g. 7CF726).
28 Verify that the last digit before the decimal dot in column no. 5 (message time of arrival counter
in seconds) occurs twice in sequence corresponding to a twice per second update rate. Note that
occasionally there could be only 1 occurrence of a digit or three. This is due to the configured jit-
tered transmission interval of the site monitor.
29 Verify that column no.8 (containing the message data) are always the same and contain 6 zero
digits at the end. This is the result of the CRC check. 6 zeroes indicate that the message has been
correctly received.
Ed. 10.07 3−29

AS 680/682 ADS−B
30 Note the hex value given within the last column. This is the actual relative signal strength with which
the site monitor signal is received by the Ground Station. Log it into the SIR.
31 Stop the recording by either clicking on the black square below the File menu or by selecting
menu Command|Stop .
32 Quit the RRC application using the File|Exit menu item.
at the bottom of the desktop. Select the window where the TSC is still running.
34 In the TSC, go to the Site Monitor Page.
35 Verify the Own Site Monitor Address and Telegram Downlink Format is as verified with the site mon-
itor (DF= DF18, Mode S address as configured).
36 Verify the RX Level is set to approx. 10% below the one noted from that site monitor in step 30.
37 Verify the Repetition Interval is at least twice the configured interval.
38 If there is a second site monitor on site, repeat steps 35 to 37 with the parameters in the Other Site
Monitor group of the TSC Site Monitor page.
39 Verify correct setting of Test Target Report Trigger.
40 Verify correct setting of Tests Target Report Interval.
3.6.6 Configuration of Ground Station

1 Connect the LCMS serial cable to the Site Monitor maintenance port and the other side to the
USB−to−serial converter. Connect the USB−to−serial converter to the LCMS.
2 Start the LCMS and login as supervisor. Supply the appropriate password.
3 Connect Ethernet crossover cable to Ground Station auxiliary port located at the GTS module in
the upper left slot of the SPU. Connect the other side to the LCMS Ethernet port.
4 Start the Ground Station.
5 Verify that all failure LEDs are off after the Ground Station boot up sequence.
6 Start the TSC from the LCMS desktop.
7 Verify that the Ground Station parameters are properly retrieved by the TSC. The last log message
in the log message window should read All parameters retrieved!".
8 Go to the TSC BITE page.
9 Verify that all BITE results are "green" or disabled (grey).
10 Go to the Software Page.
11 Verify that the correct SW version and Kernel is installed.
12 Go to the Ground Station Page.
13 Verify that the Ground Station name, SAC and SIC is correctly configured.
14 Go to the Network Page.
15 Verify the correct configuration of parameters in group Main Network Configuration :
Ground Station IP−Address , Netmask, Default Gateway.
16 Verify the correct configuration of parameters in group Main Asterix Data Stream:
Output must be enabled, Host IP and Port .
3−30 Ed. 10.07

ADS−B AS 680/682
17 Go to the GPS page.
18 Verify that the field Satellites: Number shows at least five satellites (required for useful opera-
tion).
19 Verify that the measured GPS WGS−84 Positions roughly corresponds to the configured GS
Reference Position of the Ground Station. The difference is shown in the field GPS Posi-
tion Deviation. Document both the measured lat/lon and the configured lat/lon in the SIR.
20 Verify that the Auxiliary Asterix Data Stream is enabled and set to the Host IP
192.168.23.2 (that of the LCMS), and that the Port is set correctly to 50000.
at the bottom of the desktop. Select an empty desktop the window.
22 Start the Technical Situation Display TSD from either the ADS−B tools menu of the
desktop panel or from the context menu activated with a right mouse click on the desktop back-
ground.
23 Within the TSD, set the Selected Interface to lcmsmaint:50000 and push OK.
24 Select from the preferences menu the item GS Filter to open the GS Filter Window.
25 Select the Ground Station under test from which you wish to receive data of from the list and close
the window.
26 Select from the preferences menu the item View to open the Selected Loc Window.
27 Select the Ground Station name from the drop down list View of groundstation to adjust
the correct map section.
28 Verify that at lease a Target with a label containing the name Thales is displayed. The first line of
the label must show the own site monitor address as configured.
29 Left−click on that label to select the test target.
30 Open the Target Details panel (if not already open) from the menu Display|Show Details
to show all the message contents of the test target report sent via Asterix.
31 Verify that the test target Time of Day is updated twice per second.
32 Verify that the Test Target Signal Amplitude corresponds to the one your were seeing before
within the Raw Data in section 2.5 step 30 and that is logged into the SIR.
3.6.7 Network Connection to RCMS

1 Call the TSS (responsible Technical System Supervisor) operating the RCMS, ask to check
whether the Ground Station is visible and its status can be retrieved.
2 Ask TSS to access Ground Station parameters.
3 Ask TSS to login into the Ground Station using the Login button on TSC software page.
4 Ask TSS to record Asterix data from this Ground Station to verify if any Asterix data can be received.
3.6.8 Site Installation Report (SIR)
If all the above mentioned tests were successful, the Ground Station installation should be accepted.
The following form is an example to be used as report for the site verification test.
Ed. 10.07 3−31

AS 680/682 ADS−B
3−32 Ed. 10.07

ADS−B AS 680/682
SITE INSTALLATION REPORT (SIR)
SITE Site Name Callsign
1. Basic Parameters
On TSC Ground Station 1 Ground Station 2

Callsign
SIC
IP Address
Latitude
Longitude
SPU S/N
2. ADS−B Antennas
ADS−B Antenna 1 ADS−B Antenna 2 (if available)

Type
S/N
VSWR
Height
Additionally j Sketch of Configuration j Sketch of Configuration
available
j Installation Photo j Installation Photo
j 360° Panorama j 360° Panorama
3. Antenna Amplifier Unit (AAU)
AAU AAU 1 AAU 2 (if available)

AAU S/N
DC Voltage
4. GPS Antenna
GPS GPS Antenna 1 GPS Antenna 2

Height
Additionally j Sketch of Configuration j Sketch of Configuration
available
j Installation Photo j Installation Photo
j 360° Panorama j 360° Panorama

DC Voltage
Page 1 of 2
Ed. 10.07 3−33

AS 680/682 ADS−B
5. Receiver Unit (RXU)
Ground Station 1 RXU Ground Station 2 RXU

RXU Offset: DIP−switch Settings: DIP−switch Settings:
j DSO Screenshot available j DSO Screenshot available
RXU/SW2 jjjj Off jjjj Off
jjjj On jjjj On
1234 1234
6. RF Cables
Ground Station 1 Ground Station 2

Cable Insertion Loss VSWR Insertion Loss VSWR
ADS−B Ant. – AAU
ADS−B AAU – Shltr
ADS−B Shltr – Rck
SM Ant. – Shelter
7. Technical System Control (TSC) – Site Monitor Settings
On TSC Site Monitor 1 Site Monitor 2 (if available)

Mode S ID (own)
Mode S ID (other)
Actual Site Monitor
RX Level
Site Monitor RX
Threshold
8. Ground Station Settings
Ground Station 1 Ground Station 2

GS Settings j Configuration exported j Configuration exported
j TSC Screenshots available j TSC Screenshots available
9. Notes
Name Date Signature
Page 2 of 2
3−34 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance LCMS/RCMS Application Software
CHAPTER 4
USE OF LCMS/RCMS APPLICATION SOFTWARE
4.1 OVERVIEW
The application software on both systems, the LCMS and the RCMS, support the exchange and han-
dling of the data. The status as well as all functions and parameters of the Ground Station are moni-
tored and controlled system−wide via the Simple Network Management Protocol (SNMP).
The controlled unit (Ground Station) has one or more local SNMP agents or daemons having access
methods to the parameters under control, the controlling entities (LCMS and RCMS) include the
SNMP manager(s). The SNMP implementation allows sensible commands and actions, a user role
concept with specified user access levels and authentication is implemented.
The RCMS and the LCMS include a set of application software, available for the user in the desktop
panel (see Figures 4−1 and 4−2) at the bottom of the RCMS screen 0 and the LCMS screen.
MTSC TSC ADS–B Misc.

Tools Tools System Info (opt.)
Fig. 4−1 RCMS desktop panel with the set of application software (example)
TSC ADS–B Misc.

Tools Tools System Info (opt.)
Fig. 4−2 LCMS desktop panel with the set of application software (example)
The set of application software comprises:

− The TSC (Technical System Control) on the RCMS and the LCMS is a dedicated SNMP manager,
that extends the standard MIB by a few useful add−on functions based on a proprietary protocol
(see section 4.2). The main functionality is to monitor the state of the Ground Station and to alarm
a user in case of malfunction.
− Within the RCMS at the remote site (e.g. ATC−Center) the TSC is integrated into a hierarchical
MTSC (Master Technical System Control). The top level of the MTSC presents the system status
as a simplified map with the Ground Station site for further selection (see section 4.3). The MTSC
can be started by a ’Monitor User’ as well as by a ’Supervisor’.
− The TSD (Technical Situation Display) on the RCMS and the LCMS displays in real time the
ADS−B traffic situation as acquired by the selected Ground Station (see section 4.4). The tool is
available for the user via the desktop panel menu ’ADS−B Tools’. The Display Configuration tool
(see section 4.5) is a tool to edit the configuration file used by the TSD. The TSD can be started
by a ’Monitor User’ as well as by a ’Supervisor’.
− A set of record and replay tools on the RCMS and the LCMS is installed for recording/replaying
the raw decoded Mode S data and the ASTERIX CAT 21/ CAT 23 data (see section 4.6). These tools
are also available for the user via the desktop panel menu ’ADS−B Tools’.
Ed. 10.07 4−1

AS 680/682 ADS−B
LCMS/RCMS Application Software Description, Operation and Maintenance
− On the LCMS and the RCMS some additional miscellaneous tools are available, like a calculator,
an editor, the RCMS Logviewer and a screen capture tool to make a screen shot of the RCMS/
LCMS screen(s). The tools are available via the desktop panel menu ’Misc. Tools’. They are descri-
bed in section 4.7.
Fig. 4−3 shows the structure of the application software on the LCMS and the RCMS.
LCMS screen RCMS screen 0 RCMS screen 1
TSC MTSC
Monitor User Monitor User

Supervisor Supervisor
ADS−B
Tools
Technical Situation
Display (TSD) and
Configuration
Record/Replay Tools
RRC, RRP3), RAC,
ARC, ARP
Misc.
Tools
RCMS/LCMS−Burning
Applications
Nedit
Minicom 1)
Calculator
Capture Screen 2)
Image Viewer
PDF Viewer
Terminal
1) only on LCMS screen

2) on RCMS: Capture Screen 0 and Screen 1
3) because of safety reasons, only available via command line
Fig. 4−3 Structure of the application software on the LCMS and the RCMS
4−2 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Technical System Control
4.2 TECHNICAL SYSTEM CONTROL (TSC)
4.2.1 General
The main functionality of the Technical System Control (TSC) is to monitor the Ground Station state
and to alarm a user in case of a malfunction. Additionally the TSC can be used
S to inspect and change all parameters of the Ground Station,
S to log the system state and any configuration changes to a file and a log window on screen,
S to allow rebooting the Ground Station remotely,
S to allow updating the Ground Station software remotely.
The basic TSC operating principle is to retrieve and update configuration and status information of
the Ground Station via the protocol SNMP (Simple Network Management Protocol).
SNMP is an asynchronous query/answer protocol based on the standard connectionless transport

protocol UDP/IP. The unit under control (Ground Station) must be equipped with a local SNMP agent
or daemon having access methods to the configuration and status parameters of interest. The con-
trolling entity is referred to as SNMP manager. Both, the agent and the manager have the same de-
scription of controlled parameters within a data structure called management information base (MIB).
Most network components and computer operating systems on the market are equipped with SNMP
agents and come with a specially adapted MIB. New components are made known to the SNMP man-
ager by including their MIBs.
The TSC includes an SNMP manager, but extends the standard MIB by a few useful add−on functions
based on a proprietary protocol.
The TSC can be started in different modes (user roles) depending on the user account that runs the
application (’Monitor User’ or ’Supervisor’). Setting up and configuring the TSC is described in sec-
tion 3.5.
The TSC monitors only one Ground Station but can switch to different Ground Stations easily. The
TSC has a list of Ground Stations which the TSC can switched to.
4.2.2 Starting the TSC

A file including a list of available Ground Stations has to be used as start−up parameter. On the RCMS
the TSC uses the same data file as the MTSC.
On the RCMS the TSC is started from the desktop panel, ’Misc. Tools’, ’Terminal’ with the command:
/usr/local/tsc/tsc −mtsc /usr/local/etc/data.xml
On the LCMS there is no MTSC installed. So the TSC will get the list of available Ground Stations using
a special Ground Station list file.
On the LCMS the TSC is started from the desktop panel, ’Misc. Tools’, ’Terminal’ with the command:
/usr/local/tsc/tsc −gsl /usr/local/etc/gs_list.conf
4.2.3 Operation of the TSC
The operation of the TSC in the Supervisor Mode is described in chapter 5, the TSC operation in
the Monitor User Mode is described in chapter 6 of this technical manual.
Ed. 10.07 4−3

AS 680/682 ADS−B
Technical System Control Description, Operation and Maintenance
4−4 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Master Technical System Control
4.3 MASTER TECHNICAL SYSTEM CONTROL (MTSC)
4.3.1 General
The main functionality of the Master Technical System Control (MTSC) on the RCMS is to monitor
several ADS−B Ground Stations. The status of every Ground Station is represented by an icon in the
Graphical User Interface (GUI) of the MTSC. The MTSC gets the status of a Ground Station by periodi-
cally polling the device over SNMP.
The MTSC is designed to run on an RCMS workstation using two screens. Its primary output (the
MTSC ’Main window’) is shown on the so called ’screen 1’. This window gives an overview of all
Ground Stations of the system and needs to be permanently visible. Auxiliary windows with detailed
information to single Ground Stations are shown on the other ’screen 0’.
The MTSC can be started in two different modes (user roles) depending on the login user account:
− Monitor User Mode
− Supervisor Mode
In the Monitor User Mode, the current status of the Ground Stations can only be monitored. In the
Supervisor Mode the configuration of the system can be changed, i.e. adding, deleting of Ground
Stations is possible. Parameters in the Detailed Status window can be modified.
The following sections describe first the general Graphical User Interface (GUI) structure of the MTSC
application on both screens, followed by the functions available for the different user roles (Monitor
user and Supervisor).
4.3.2 Structure of the MTSC GUI
The MTSC application is designed to run on an RCMS workstation using two screens (see Fig. 4−4).
LAN
Screen 0 Screen 1
Fig. 4−4 RCMS Configuration with the two screens used for the MTSC application
On screen 1 the ’MTSC Main window’ (see section 4.3.2.1) and the ’Event window’ (see section
4.3.2.1.1 ), presenting a log of the latest status changes are shown.
On screen 0 a window with detailed GS information, i.e. ’Detailed Status window’ (see section 4.3.2.2)
is shown. Additionally the desktop panel providing all the RCMS application software is available at
the bottom of screen 0.
Ed. 10.07 4−5

AS 680/682 ADS−B
Master Technical System Control Description, Operation and Maintenance
4.3.2.1 MTSC Main Window on Screen 1

The MTSC Main window consists of several parts (see Fig. 4−5):
S Menubar
S Toolbar
S List Panel
S Map Panel
S Event Window
S Statusbar
Menubar
Toolbar
Map
List Panel
Panel
Event
Window
Statusbar
Fig. 4−5 Structure of the MTSC Main Window on screen 1 (example)
The list panel consists of a list of all configured ADS−B Ground Stations. Each device is represented
by a label with an icon. Its background is colored according to its current status (red−fault, yellow−
warning, green−ok, blue−maintenance, orange−undefined, grey−deactivated). Selecting an icon
with the right mouse button opens a context menu.
NOTE: Clicking the right mouse button while not pointing on an actual GS icon, opens a different
context menu.
The BITE status of the entire system is calculated based on all Ground Station status results. The cal-
culation of the equation result can be enabled/disabled globally within the map menu. It is shown on
top of the list panel (e.g. "LaRéunion", see Fig. 4−5).
4−6 Ed. 10.07

ADS−B AS 680/682
The map panel consists of a map picture and one icon per monitored GS at its approximate site posi-
tion on the map.
Depending on the user role the menubar, the toolbar and the context menus available within the map
panel provide different functions (submenus) to the user. Therefore these functions are described in
section 4.3.3 for the Supervisor and in section 4.3.4 for the Monitor User.
4.3.2.1.1 Event Window on Screen 1
After starting the MTSC application (see section 3.3) as a Supervisor or a Monitor User, the ’Event
window’ appears on the screen 1 (see Fig. 4−6), below the map panel.
Fig. 4−6 MTSC, Event window on screen 1 (example)
In the ’Event Window’ the MTSC application lists status change events of all configured Ground Sta-
tions. The events are divided into three priorities:
S Error
S Warning
S Info
The error events are displayed with red colour. If an error event occurs a confirmation window opens,
if configured via MTSC ’File’ menu ’Settings’ (see section 4.3.3.1). Warning events are displayed with
yellow color and information events with black color.
The ’Clear’ button clears the event table of the ’Event window’. All events are also logged to a file using
the syslog daemon and thus available for later retrieval. Depending on the event type this is logged
to different files: ’user info’ or ’user error’.
4.3.2.2 Detailed Status Window on Screen 0
If a user wants to get detailed information on one specific Ground Station, he uses the ’Detailed Status
window’ on screen 0 (see Fig. 4−7). It appears after selecting the submenu ’Detailed View’ of the GS
menu within the map panel on screen 1 (see sections 4.3.3.3.2 and 4.3.4.3.2 ).
Ed. 10.07 4−7

AS 680/682 ADS−B
Menubar
BITE panel
BITE file tabs

Statusbar
Fig. 4−7 MTSC, Detailed Status window on screen 0 (example)
The ’Detailed Status’ window consists of four parts (described in sections 4.3.2.2.1 to 4.3.2.2.4 ):
S Menubar
S BITE panel
S BITE file tabs
S Statusbar
4.3.2.2.1 Menubar of Detailed Status Window

The ’File’ menu contains the submenu:
S Exit:
Closes the ’Detailed Status window’.
The ’Edit’ menu contains the submenu:

S Properties (only for Supervisor):
The Supervisor can enable/disable the monitoring and can set the polling rate within the ’Edit
Properties’ window (see Fig. 4−8).
Fig. 4−8 Detailed Status window, ’Edit Properties’ window (example)
4−8 Ed. 10.07

ADS−B AS 680/682
S Exit:
Closes the ’Detailed Status window’.
NOTE: The button has not to be used to close the window.
The ’Help’ menu contains the menu item ’About’. Clicking on this item opens the ’About’ window,
which shows the actual version of the ADS−Bx plugin software.
NOTE: The menu items presented in grey letters are not accessible.
4.3.2.2.2 BITE Panel of Detailed Status Window
The BITE panel shows the actual BITE status of the ADS−B Ground Station, see Fig. 4−7. The BITE
status shows the states of important subsystems of the Ground Station. The subsystem values of the
BITE are divided into three groups:
S Critical (Error)
S Warning
S Maintenance
Greyed subsystem values indicate that they are deactivated in the Ground Station. The values could
have the following states:
S green − ok
S red −failure
S orange − invalid
4.3.2.2.3 BITE File Tabs
The BITE file tabs enables the operator to have a view on the Detailed Status of ’Groundstation A’,
of ’Groundstation B’ or of ’M/S Control’ (Master/Slave control of both ground stations), see Fig. 4−7.
4.3.2.2.4 Statusbar of Detailed Status Window
The status bar shows the actual state of the monitored Ground Station, see Fig. 4−7. The meaning
of the icons are
S green − operational
S yellow − warning
S blue − maintenance
Ed. 10.07 4−9

AS 680/682 ADS−B
4.3.3 Supervisor Operation

4.3.3.1 Menubar of Main Window
The menubar of the MTSC Supervisor Main window provides the menus ’File’ and ’Help’:
Fig. 4−9 Menubar of the MTSC Supervisor main window (example)
The ’File’ menu of the contains the following submenus:

S Save Configuration
After selecting this submenu the actual configuration of the system is saved within the configura-
tion file config.xml. Clicking on the corresponding icon of the toolbar performs the same function.
S Settings
Clicking on this submenu opens the ’Settings’ window on screen 0 (see Fig. 4−10). The ’Settings’
dialog allows to change the Main window size. The ’Apply’ button activates the actual values for
width and height immediately.
Fig. 4−10 MTSC, Settings Window (example)
In the ’Audible Alert’ group the user can enable/disable the audible alert. If enabled every state
change of the observed ADS−B Ground Stations causes an audible alert. With the combox
Sound" the user can select the alert file which is played if an alert occurs. The played audio file
has the standard *.wav format.
The ’Popup Window’ select button enables or disables the pop−up of the ’MTSC Error’ window
(see Fig. 4−11), which appears on screen 0 if an error occurs in an ADS−B Ground Station. The
default setting is ’disabled’ (’off’). Clicking on the ’OK’ button confirms the error message and
closes the pop−up window automatically.
NOTE: The default setting of ’Popup Window’ is ’disabled’. If the feature is enabled, the
supervisor has to execute the error confirmation three times, because of the ’error state
acknowledgement’ procedure available on screen 1 (see section 4.3.3.3.2 ).
Fig. 4−11 MTSC, Pop−up window indicating an MTSC Error (example)
S Quit
After clicking on this submenu the Supervisor leaves the MTSC application.
4−10 Ed. 10.07

ADS−B AS 680/682
The ’Help’ menu contains the items ’About’ and ’Content F1’.
Clicking on the submenu ’About’ opens the ’About window’ (see Fig. 4−12) on screen 0. The window
shows the actual version of the MTSC application. Further the window shows some variables of the
Java Virtual Machine (VM).
Version
Java VM
Fig. 4−12 MTSC, About Window (example)
Clicking on the submenu ’Content F1’ opens the ’MTSC Help window’ (see Fig. 4−13) on screen 0.
Fig. 4−13 MTSC Help window (example)
Ed. 10.07 4−11

AS 680/682 ADS−B
4.3.3.2 Toolbar of Main Window
The toolbar of the MTSC Supervisor Main window (see Fig. 4−5) contains the following icons:
The icons provide the following functions:

S Save configuration
Same function as ’Save configuration’ submenu of menu ’File’, see section 4.3.3.1. After clicking
on this icon the actual configuration of the system is saved within the configuration file config.xml.
S Enable monitoring of selected item

After clicking on this icon the item (Ground Station) selected in the List Panel of the Main window
is monitored, i.e. the GS status is periodically polled. The Ground Station in the list panel is now
marked with the in front of the GS name.
S Disable monitoring of selected item

After clicking on this icon the monitoring of the item (Ground Station) selected in the List Panel is
disabled. The Ground Station in the list panel is now marked with the in front of the GS name
and the background color of the item is grey.
4.3.3.3 Map Panel of Main Window
The map panel on screen 1 of the RCMS consists of a map picture and one icon per monitored GS
at its approximate site position on the map.
Within the Map Panel the MTSC Supervisor is able to open two different context menus:
− The Map menu, which appears after clicking with the right mouse button on any point within the
Map Panel work space (not on a GS icon), see section 4.3.3.3.1 .
− The GS menu, which appears after clicking with the right mouse button on a GS icon in the Map
Panel, see section 4.3.3.3.2 .
4.3.3.3.1 Map Menu of Map Panel
The Map menu (see Fig. 4−14) appears after clicking with the right mouse button on any point within
the Map Panel work space (not on a GS icon).
Fig. 4−14 Map menu provided to the Supervisor within the map panel (example)
4−12 Ed. 10.07

ADS−B AS 680/682
The Map menu contains the following items:
S Refresh: Refreshes the status indication of all GS indicated in the map panel.
S Rename: Possibility to give a new name to the file.
S Equation:
States of all GS in the map panel are (not) relevant for the calculation of the entire system status
(e.g. ’Australia’) in the list panel.
S New Device:
The window ’Create New Device’ appears in screen 0 (see Fig. 4−15) to define a new GS.
Fig. 4−15 Window ’Create New Device’ (example)
After entering the values of ’Proxy Host’ and ’Proxy Port’ and confirming with the ’OK’ button, a
new GS icon appears in the left upper corner of the map panel on screen 1 with a GS default name
("ADS−B_GS"), see Fig. 4−16. With the select button Monitoring Enabled" it is possible to acti-
vate/deactivate the monitoring of the new device. The icon can be moved to the desired place
within the map by clicking and holding the left mouse button on the new icon.
NOTE: To define a new GS it is necessary to update the /etc/hosts table, i.e. to enter the new IP
address and the new alias name (e.g. ’192.168.23.123 Brisbane’).
new GS icon
Fig. 4−16 Map panel with new GS icon (default name), example
The new GS can now be renamed by using the ’Rename’ submenu of the GS menu (see following
section 4.3.3.3.2 ), which appears after clicking with the right mouse button on the new GS icon.
Ed. 10.07 4−13

AS 680/682 ADS−B
S Edit Select Map:
The window ’Open’ appears to select a new map file (see Fig. 4−17).
Fig. 4−17 Window ’Open’ to select a new map file (example)
Edit Save:
The window ’Save’ appears to save the actual configuration within an *.xml file (see Fig. 4−18).
Fig. 4−18 Window ’Save’ to save the actual configuration (example)
Edit Default View:

Gives the possibility to enable/disable the view.
S Features:
The window ’Features’ appears in screen 0 (see Fig. 4−19).
Fig. 4−19 Window ’Features’ (example)
4−14 Ed. 10.07

ADS−B AS 680/682
4.3.3.3.2 GS Menu of Map Panel
The GS menu appears after clicking with the right mouse button on a GS icon in the Map Panel.
Fig. 4−20 GS menu provided to the Supervisor within the map panel (example)
The GS menu provides the following submenus (see Fig. 4−20):

S Delete: Deletes the selected GS within the map panel.
S Refresh: Refreshes the status indication of the selected GS.
S Rename:
The Supervisor can rename the GS within a ’Rename’ window. First the GS icon gets the new
name. After selecting the function ’Save Configuration’ (see section 4.3.3.1), the name is also
changed in the configuration file config.xml. To set the new name in the GS NVRAM use the sub-
menu ’Detailed View Show’ of this GS menu (see below).
S Equation:
The state of the selected GS is (not) relevant for the calculation of the entire system status (e.g.
’Australia’) in the list panel.
S Set Device Name: Reads the GS name defined in the NVRAM of the GS.
S Info:
The window ’Configuration Info − <GS name>’ (see Fig. 4−21) appears in screen 0 with informa-
tion to the selected GS, like device name, host name, SNMP port, actual state and map position.
Fig. 4−21 Window ’Configuration Info −<GS name>’ (example)
S Detailed View Show:

The ’Detailed Status window’ appears on screen 0 (see section 4.3.2.2)
Detailed View Hide:
The ’Detailed Status window’ disappears on screen 0.
S Features:
The window ’Features’ appears in screen 0 (see Fig. 4−19).
Ed. 10.07 4−15

AS 680/682 ADS−B
4.3.4 Monitor User Operation

4.3.4.1 Menubar
The ’File’ menu of the Monitor User’s main window contains the submenu ’Exit’. After clicking on this
submenu the Supervisor leaves the MTSC application.
The ’Help’ menu contains the items ’About’ and ’Content F1’. Clicking on the submenu ’About’
opens the ’About window’ (see Fig. 4−12) on screen 0. The window shows the actual version of the
MTSC application. Further the window shows some variables of the Java Virtual Machine (VM). Clik-
king on the submenu ’Content F1’ opens the ’MTSC Help window’ (see Fig. 4−13) on screen 0.
4.3.4.2 Toolbar
See also section 4.3.3.2.

The icons on the Toolbar of the Monitor User’s main window are all greyed, i.e. not available.
4.3.4.3 Map Panel of Main Menu

4.3.4.3.1 Map Menu of Map Panel
See also section 4.3.3.3.1 .
The Map menu of the Monitor User’s map panel contains the submenus:
S Refresh:
Refreshes the status indication of all GS indicated in the map panel.
S Edit Access to Export:
The window ’Save’ appears to save the actual configuration within an *.xml file (see Fig. 4−18).
4.3.4.3.2 GS Menu of Map Panel
See also section 4.3.3.3.2 .
The GS menu of the Monitor User’s map panel provides the following submenus:
S Refresh:
Refreshes the status indication of the selected GS.
S Info:
The window ’Configuration Info − <GS name>’ appears in screen 0 (see Fig. 4−21).
S Detailed View Show:
The ’Detailed Status window’ appears on screen 0 (see section 4.3.2.2).
Detailed View Hide:
The ’Detailed Status window’ disappears on screen 0.
4−16 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Technical Situation Display
4.4 ADS−B TOOLS: TECHNICAL SITUATION DISPLAY (TSD)
4.4.1 General Description
The Technical Situation Display (TSD) listens to a network interface and displays incoming ASTERIX
CAT 21 data on a map.
The TSD tool can be called on the LCMS screen or on the RCMS screen 0 via the desktop panel menu
’ADS−B Tools’, submenu ’Technical Situation Display − TSD’ (see Fig. 4−22).
Fig. 4−22 Desktop panel menu with ’ADS−B Tools’ submenus ’Technical Situation Display’
The Technical Situation Display is always launched with a configuration file. The loaded configuration
file is found in the title bar of the main window. The configuration file is an XML−File, i.e. a text−file,
which can be edited with an arbitrary text editor, but also with the special Display Configuration Tool,
refer to section 4.5.
From command line the Technical Situation Display is started with the command
adsb−display –config <configuration file>".
NOTE: The configuration of the TSD tool can be started via the ’ADS−B Tools’ submenu ’Techni-
cal Situation Display − Configuration’ (see Fig. 4−22). This is described in section 4.5.
Titlebar
Menubar
Toolbar
Detailed Map View

Target View (Situation
Display)
Statusbar
Fig. 4−23 Technical Situation Display − TSD, main components (example)
Ed. 10.07 4−17

AS 680/682 ADS−B
Technical Situation Display Description, Operation and Maintenance
The main components of the Technical Situation Display are:
The titlebar shows the name of the tool Technical Situation Display and the name of the loaded con-
figuration file. The titlebar contains the window features provided by the used window manager, which
may be, e.g., close, maximise, minimise, resize, move the window or put it to some workspaces.
The menubar contains the menus ’File’, ’Map Items’, ’Markings’, ’Display’, ’Tracks’, ’Preferences’
and ’Help’ (see Fig. 4−24). The menus of the menubar are described in section 4.4.2.
The toolbar consists of five items. The toolbar tools are used to clear the targets’ history or to zoom
the map view. The toolbar is described in section 4.4.3.
The detailed target view shows the ASTERIX CAT 21 fields that can be received for a target. The
detailed target view is described in section 4.4.4.
The map view of the Technical Situation Display shows an environment of a groundstation. The map
view is described in section 4.4.5.
The statusbar at the bottom of the Technical Situation Display is described in section 4.4.6.
4−18 Ed. 10.07

ADS−B AS 680/682
4.4.2 Menubar
Fig. 4−24 TSD, menu bar
4.4.2.1 Menu ’File’
The menu ’File’ (Fig. 4−25) contains the items ’Save Configuration’, ’Load Configuration’ and ’Quit’.
Fig. 4−25 TSD, menu ’File’
Pushing the ’Save configuration’ opens a file selection box (see Fig. 4−26) to save the settings made
by the user in the Technical Situation Display to an XML−configuration file.
Fig. 4−26 TSD file selection for saving configuration (example)
In general, the configuration file, which has initialized the current session, is selected by default. Set-
tings that can be adjusted by the user, are the options of the menus ’Map Items’, ’Display’, ’Markings’,
’Tracks’ and ’Preferences’. Refer to the corresponding sections 4.4.2.2 to 4.4.2.6 for more information
on these menus.
Pushing the ’Load configuration’ opens a file selection box similar to the one shown in Fig. 4−26
to load an XML−configuration file. It is possible to load any valid XML−configuration. The settings
of the new configuration file take effect immediately.
The Technical Situation Display application is terminated, if the ’Quit’ menu item is selected.
Ed. 10.07 4−19

AS 680/682 ADS−B
4.4.2.2 Menu ’Map Items’

The menu ’Map Items’ (see Fig. 4−27) gives the possibility to show or hide components of the map.
The menu contains the following items:
Fig. 4−27 TSD, menu ’Map Items’ (example)
In general, the map contains only a subset of all the components that are listed in the menu. Compo-
nents that are displayed, if available, are marked with a hook on the left side of the respective menu
item. The selected combination can be saved to the configuration file (see section 4.4.2.1).
It is possible to determine in the configuration file, which items shall be shown in this menu. If the corre-
sponding ’show’−tag is set to ‘true’, then the item is available in the menu ’Map Items’.
4.4.2.3 Menu ’Markings’
The menu "Markings", (see Fig. 4−28), gives the possibility to show or hide the highlighting of tracks
with certain attributes:
S ’Special Position Indicator (Spi)’
S ’Figure of Merit / Position Accuracy (Pa)’
S ’Address Type (Atp)’
S ’Simulation Flag (Sim)’
S ’Version Number (Vn)’
S ’Ground Bit Set (Gbs)’
It is possible to highlight tracks which are set to a configurable value.

The hooks in front of every activated item are coloured according to the respective highlighting colour
of the track. The configuration of the markings are done with the help of the Display Configuration
tool referring to 4.5.7.13.
Fig. 4−28 TSD, menu ’Markings’ (example)
4−20 Ed. 10.07

ADS−B AS 680/682
4.4.2.4 Menu ’Display’
The menu ’Display’ (Fig. 4−29) allows to show or hide additional map components and the detailed
target view. The mentioned components are not part of the vector map of the display. It is possible
S to lay a grid over the map (menu item ’Show Grid’)
S to show a compass at the upper left side of the map (menu item ’Show Compass’)
S to show or hide the detailed view of a selected target; the detailed view is a box put to the left side
of the map (menu item ’Show Details’)
S to enable the display of plots with older time stamps than most recent one (refer to section 4.5.7.8)
S to show or hide the Flight Level Panel displaying graphically the current altitude and vertical rate,
and the history of the altitude of a presently selected target, refer to section 4.4.5.4.
A hook at the left side of the menu items indicates, if the corresponding component is shown or hid-
den. The selected combination can be saved to the configuration file (refer to section 4.4.2.1)
Fig. 4−29 TSD, menu ’Display’ (example)
4.4.2.5 Menu ’Tracks’
The menu ’Tracks’ enables the user to adjust some settings of the displayed targets. The targets are
displayed as plots with a configurable shape and a configurable size.
The previous positions of a target are also displayed as plots. It is possible to determine, how long
a plot shall be shown until it disappears from display. It is possible to show a speed vector of select-
able length.
All the changes made in the submenus can be saved to the configuration file (see section 4.4.2.1).
The menu ’Tracks’ (see Fig. 4−30) contains the following four submenus:
Fig. 4−30 TSD, menu ’Tracks’ (example)
Submenu ’Plot Shape’:

It is possible to select one of the following three possible plot shapes from the submenu ’Plot Shape’
(see Fig. 4−31). The tick before a menu item indicates the current selection.
Fig. 4−31 TSD, submenu ’Plot Shape’ (example)
Ed. 10.07 4−21

AS 680/682 ADS−B
Submenu ’Plot Size’:
It is possible to choose among five different sizes for the target plots in the submenu ’Plot Size’ (see
Fig. 4−32). The tick before a menu item indicates the current selection.
Fig. 4−32 TSD, submenu ’Plot Size’ (example)
Submenu ’History’:
It is possible to choose among eleven different plot ages in the submenu ’History’ (see Fig. 4−33).
The tick before a menu item indicates the current selection.
If the history age ’Mem limit’ is chosen, the configuration parameter ’Memory limit of history’ (refer
to section 4.5.7.7) applies. A memory limit of e.g. 99 percent means that with every position a new
plot is allocated until 99 percent of the physical memory is in use. If this threshold is reached, the ap-
plication uses the time period since its start up to the moment, when the limit is reached as history
age. That is, plots, which reach this history age, will be deleted.
If 99 percent of the physical memory is in use, it is still very probable that enough virtual memory is
available to avoid a blocking of the system. The period, up to when the memory limit is reached, is
of course influenced by other applications running on the same system, too.
It is possible to clear all history plots with the ’clear’ menu item. Clearing the history plots can also
be achieved by pushing the corresponding button on the toolbar, refer to section 4.4.3.
Fig. 4−33 TSD, submenu ’History’ (example)
Submenu ’Speed Vector’:

It is possible to choose among six options of speed vector representations in the submenu ’Speed
Vector’ (see Fig. 4−34).
The tick before a menu item indicates the current selection. It is possible to hide the speed vector or
to give a time representing the length of the speed vector.
For instance, if selecting the time 1 minute, the speed vector points to the location on the map, where
the target is expected one minute from now, provided that direction and speed do not change.
The color of the speed vector can be chosen in the configuration file.
4−22 Ed. 10.07

ADS−B AS 680/682
Fig. 4−34 TSD, submenu ’Speed Vector’ (example)
4.4.2.6 Menu ’Preferences’
The menu ’Preferences’ contains the menu items ’Info’, ’GS Filter’, ’PA Filter’, ’View’ and ’Interface’.
All menu items cause the pop up of panels, which are explained in the following sections.
Fig. 4−35 TSD, menu ’Preferences’
4.4.2.6.1 Information Panel

The menu item ’Info’ opens the ’Information’ panel (see Fig. 4−36) which displays information
S on the interface address, consisting of the hostname (or IP−address) and a port, the Technical
Situation Display is listening to,
S on the name of the currently used configuration file, and
S on the currently accepted ASTERIX categories and editions.
NOTE: It is possible to receive two different editions of one ASTERIX category.
Fig. 4−36 TSD, ’Information’ panel (example)
4.4.2.6.2 GS Filter Panel
The menu item ’GS Filter’ opens the ’Selected Filter’ panel, see Fig. 4−37, to change the Ground
Station filter. The Ground Station filter is enabled by default, i.e. it can only be disabled within the con-
figuration file (with limited access rights).
Ed. 10.07 4−23

AS 680/682 ADS−B
Fig. 4−37 TSD, ’GS Filter’ panel (example)
The list in the filter panel consists of five columns, see Fig. 4−37:
− the first column contains check boxes relating to the complete line
− the second column contains the Ground Station identification
− the third column contains the site name of the Ground Station
− the fourth column contains the System Area Code (SAC) of the Ground Station
− the fifth column contains the System Identification Code (SIC) of the Ground Station
ASTERIX CAT 21 data is only accepted from the Ground Stations, which are selected in the Ground
Station list. Checking a Ground Station activates immediately the corresponding filter. The display will
accept only targets arriving from the checked Ground Stations. Pushing the ’Close’ button closes the
’Filter’ panel. The filter settings are saved, if the configuration is saved, refer to section 4.4.2.1.
4.4.2.6.3 PA Filter Panel
The menu item ’PA Filter’ opens a panel, see Fig. 4−38, to change the Position Accuracy Filter. It
is possible to select a position accuracy between 0 and 9. All targets with a position accuracy less
than the selected number are not displayed. The position accuracy (PA) is found in the mandatory
ASTERIX field Figure of Merit (FOM). Thus no targets are filtered out with this filter, if the number ’0’
is chosen in the option box.
Fig. 4−38 TSD, ’PA Filter’ panel (example)
4.4.2.6.4 View Panel
The menu item ’View’ opens the ’Selected localisation’ panel, see Fig. 4−39, to change the current
view. There is defined one view per available Ground Station site. It is possible to select the wished
view in the option menu ’View of groundstation’.
4−24 Ed. 10.07

ADS−B AS 680/682
With the selection of the view, the SAC, SIC, longitude and latitude of the selected groundstation (site)
are displayed. Clicking on the ’OK’ button sets the corresponding view in the map and closes the
panel. Clicking on the ’CANCEL’ button cancels the selection and closes the panel.
NOTE: The selection of a new view can be prevented, if the ’View pursues Target’ mode is activa-
ted and a selected target is not found within a threshold near the border of the selected
view (refer to section 4.4.5.1).
The view settings are saved, if the configuration is saved, refer to section 4.4.2.1.
Fig. 4−39 TSD, ’Selected localisation’ panel (example)
4.4.2.6.5 Interface Panel

The menu item ’Interface’ opens the ’Selected Interface’ panel (see Fig. 4−40) to change the current
ASTERIX interface. The available interfaces, consisting of a combination of hostname and port, are
configured in the configuration file. It is possible to select an interface from the option menu. The se-
lected interface becomes active as soon as the dialog is closed with the ’OK’ button. The currently
selected interface is shown in the line of text above the option menu and in the information panel, refer
to section 4.4.2.6.1 .
Fig. 4−40 TSD, ’Selected interface’ panel (example)
4.4.2.7 Menu ’Help’
The menu ’Help’ contains the menu items ’About’ and ’Reference’. All menu items cause the pop up
of panels, which are explained in the following sections.
Fig. 4−41 TSD, menu ’Help’
Ed. 10.07 4−25

AS 680/682 ADS−B
4.4.2.8 About Panel
The menu item ’About’ opens the About panel (see Fig. 4−42) that shows the tool command, version,
name of the tool, as well as the reference address of the supporter.
Fig. 4−42 TSD, ’About’ panel (example)
4.4.2.9 Short Reference Panel
The menu item ’Reference’ opens the ’Short Reference’ panel (see Fig. 4−43) that shows short in-
structions of the use of the available mouse and key functions.
Fig. 4−43 TSD, ’Short Reference’ panel (example)
4−26 Ed. 10.07

ADS−B AS 680/682
4.4.3 Toolbar
The toolbar of the Technical Situation Display consists of five items, see Fig. 4−44. The toolbar tools
are used to clear the targets’ history or to zoom the map view.
S The brush is used to clear the history of the targets displayed on the map.
S The three magnifying glasses are needed to zoom in, zoom out and to reset the map view to its
initial state.
S The select−button and textfield are used to ease the search for a certain target. Entering a target
address into the textfield and pushing the select−button will select the corresponding target on
the display.
S The slider is used to zoom in or out. Sliding to the left zooms in, sliding to the right zooms out.
Fig. 4−44 TSD, Toolbar
Ed. 10.07 4−27

AS 680/682 ADS−B
4.4.4 Detailed Target View
The detailed target view (’Target Details’, see Fig. 4−45) shows the ASTERIX CAT 21 fields that can
be received for a target. To see the detailed view, the menu item ’Show Details’ in the menu ’Display’
must be selected (refer to section 4.4.2.4). If ’Show Details’ is activated, a target in the map view must
be selected with a click of the left mouse button on the target’s label (refer to section 4.4.5.2).
The target can be deselected by a click of the right mouse button somewhere on the map holding
the ’Ctrl’ key.
The target’s ASTERIX CAT 21 attributes, as far as valid, are displayed on the detailed view. Missing
or invalid data are indicated by a hyphen ‘−‘.
It is possible to choose the ASTERIX CAT 21 fields to be displayed in the configuration file, mentioned
in section 4.4.1. Set the corresponding tag of the field in the paragraph ‘Detail’ of the configuration
file to ‘true’, if the field shall be shown, otherwise to ‘false’.
Fig. 4−45 TSD, ’Target Details’ panel (example)
4−28 Ed. 10.07

ADS−B AS 680/682
4.4.5 Map View
The map view, see Fig. 4−46, of the Technical Situation Display shows an environment of a Ground
Station. The map’s co−ordination system can be a cartesian or a spherical one. The used vector
maps are found in files with the extension .reg.
S The cartesian co−ordination system needs a map, whose components are given in cartesian co−
ordinates in the unit meters, where the origin of the reference system is the position of the Ground
Station. The position of the Ground Station must be given in the configuration file in longitude /
latitude values.
S The spherical maps use longitude and latitude values. Spherical maps don’t need a reference
point, they take the global WGS 84 reference system. For representation in the map view, the Miller
projection (a world projection) is applied to the spherical maps. The ADS−B applications use
spherical maps.
The colors of the map components can be chosen in the configuration file. It is possible to show/hide
components and to configure the representation of the target plots referring to sections 4.4.2.2 to
4.4.2.5.
Fig. 4−46 TSD, Map view (example)
4.4.5.1 Map View Features

The following actions are provided for the map view:
S Zooming:
It is possible to zoom into the map, to zoom out of the map or to reset the original view by using
the tools of the toolbar (see section 4.4.3) or the corresponding keys ‘Alt −’ or ‘Alt +‘ or ‘Alt r’.
It is possible to zoom into a rectangle by holding the left mouse button pressed and dragging the
mouse. It is possible to zoom in or out by using the scroll wheel of the mouse. Endless zooming
is not applicable. There are upper and lower bounds.
Ed. 10.07 4−29

AS 680/682 ADS−B
S Panning:
It is possible to shift the view by holding the middle mouse button pressed and dragging the
mouse. It is also possible to shift the view with the cursor keys (vertical and horizontal arrows).
S Hitting the keys ’Alt r’ resets the view to the initial view.
S Hitting the keys ’Alt c’ connects or disconnects the plots of the targets’ tracks, i.e. draws a line.
S Only if a target is selected, hitting the keys ’Alt f’ activates or deactivates the ’View pursues
Target’ mode. In that case, the indicator ’follow’ is found in the status bar (refer to section 4.4.6).
If this mode is activated, the map view is shifted in the way that a selected target is positioned to
the center of the view, whenever it passes a threshold (refer to section 4.5.7.1) being defined in
the configuration file.
− If this threshold shows its smallest value 0, then the target will not leave the center of the view
and the map will move underneath the target.
− If this threshold shows its greatest value 100, the target may move up to the borders of the view
before the view will be centered to the position of the selected target.
This automatic shifting can happen, if the view is zoomed, rotated or moved by the user or, if the
selected target itself moves to this threshold.
NOTE: Selection of another view (refer to section 4.4.2.6.4 ) is prevented, if a selected target is
not found within the thresholds of that view.
S Position:
The current position of the mouse pointer is always displayed in the statusbar (see section 4.4.6)
S Distance bearing and elevation measurement:

− Between two points of the map view: Hold the ’Shift’−key and click with the left mouse button on
the first point; keep the left mouse button pressed and drag the mouse to the second point. The
current length of the displayed line is found in the statusbar (refer to 4.4.6) in unit Nautical Miles
and in meters. The current bearing and elevation angles with the first point as reference point will
also be displayed in the status bar.
− Between target and point of the map view: refer to the previous item, but choose start or end point
on a target label. The end point is the point on the map, where the mouse button is released. The
current distance bearing and elevation are permanently shown in the statusbar, also after release
of the mouse button. The measurement is stopped by a double click somewhere on the map.
− Between two targets: refer to the previous item, but choose start and end point on a target label.
The current distance bearing and elevation are permanently shown in the statusbar. The measure-
ment is stopped by a double click somewhere on the map.
The measurement is represented in the map view by a black line as shown in Fig. 4−47.
Distance line
Fig. 4−47 TSD, distance line (example)
4−30 Ed. 10.07

ADS−B AS 680/682
S Moving of the target label: It is possible to move the label of any target by selecting it with the right
mouse button and moving it to any position in the map view.
S Rotation of the view: It is possible to rotate the view around its center. Rotating the map is done
in the following way: Click with the left mouse button on a position of the map and hold the ’Ctrl’−
key; keep the left mouse button and the ’Ctrl’−key pressed and drag the mouse; the view rotates
depending on the movement of the mouse.
S Hitting the keys ’Alt b’ rotates back to the initial view.
S Selection of a target: Select a target by left mouse button click onto its label
S Deselecting a target: Deselect a target by holding the ’Ctrl’ key and click the right mouse button
somewhere on the map.
S Selection of a Ground Station: Select a Ground Station and open its ’Distance circle’−dialog by
double clicking of the left mouse button onto the symbol representing the Ground Station. A dialog
will arise. Refer to section 4.4.5.3 for more information.
4.4.5.2 Target Representation
Targets received via network by the ASTERIX CAT 21 protocol are displayed in the map view. Every
valid position of a target is shown in a configurable shape (refer to section 4.4.2.5, ’plot shape’) and
size (refer to section 4.4.2.5, ’plot size’). The time, how long a position is shown, can be configured
in the track history, a menu item of the menu ’Tracks’ submenu ’History’ (refer to section 4.4.2.5, ’hi-
story’). The speed vector can be configured in the menu item ’Speed Vector’ (refer to section 4.4.2.5,
’speed vector’) of the menu ’Tracks’.
Every displayed target (see Fig. 4−48) gets a label, which shows the unique mode S address in the
first row, in the next row the mode 3/A address (squawk), if available, then the current height in Flight
Level (1 FL = 100 ft), if available, and in the last row the target identification, if available.
A target can be selected by left mouse click on the respective target label. Select a target and open
the ’Detailed View’ (refer to section 4.4.4) to get detailed information about the target.
Fig. 4−48 TSD, Track (example)
Ed. 10.07 4−31

AS 680/682 ADS−B
4.4.5.3 Ground Station Distance Circle

It is possible to display circles around Ground Stations, refer to Fig. 4−49, to be able to estimate the
distance of targets from a Ground Station.
Fig. 4−49 TSD, Ground Station distance circles (example)
It is possible to show or hide these distance circles, to determine the number of circles and the delta
radius of the circles individually per Ground Station.
The distance circle settings are saved, if the configuration is saved, refer to section 4.4.2.1.
The parameters of the distance circles are entered in a panel, refer to Fig. 4−50, which pops up with
a double click on the respective Ground Station.
Fig. 4−50 TSD, distance circle panel (example)
The title bar displays the name of the selected Ground Station. The following controls are available:
S the checkbox to switch the rendering of the circles on or off.
S an option menu allows to select the ’Number of circles’ that shall be shown. It is possible to choose
between one and five circles.
S an option menu to choose the Difference of the circles’ radius, the delta radius of the circles. It
is possible to select a radius of either 1 NM, 2NM, 5 NM, 10 NM, 20 NM or 50 NM.
4−32 Ed. 10.07

ADS−B AS 680/682
4.4.5.4 Flight Level Panel
It is possible to show the course of the altitude change and the current vertical rate of a selected target
graphically in the flight level panel. This panel, see Fig. 4−51, is shown or hidden by selecting the entry
’Show FL Panel’ in the menubar item ’Display’, refer to section 4.4.2.4.
If no target is selected or if vertical rate or altitude is not available, then the panel is blank. If the altitude
and the vertical rate of a selected target are given, then
S the inclination of the airplane symbol shows the degree of the target’s vertical rate
S red lines give the altitude level in distances of 10 Flight Level (FL)
S the history of the altitude of the target is marked by x symbols, which are drawn in time distance
of about 1.5 seconds at the corresponding altitude
The titlebar of the flight level panel shows the ICAO address and, if available, the identification of the
selected target.
The flight level panel is closed by the window’s standard possibilities depending on the used window
manager, e.g. by pushing the x on the upper right corner of the panel.
Fig. 4−51 TSD, flight panel (example)
Ed. 10.07 4−33

AS 680/682 ADS−B
4.4.6 Statusbar
The statusbar at the bottom of the Technical Situation Display, see Fig. 4−52, contains the following
features:
S current position of the mouse pointer in the map view. In a cartesian co−ordination system, the
position is given in the unit meters with the Ground Station position as origin. In a spherical co−or-
dination system, the position is given in longitude (x−coordinate) and latitude (y−coordinate).
S during distance, bearing, elevation measurements, the third field (marked with ’d’) in the statusbar
shows the current distance, the fourth field (marked with ’b’) the bearing, and the fifth field (marked
with ’e’) the elevation of a measurement in the map view.
− The distance is measured in Nautical Miles (NM) and in meters (m) shown in brackets. The dis-
tance in meters is shown in braces.
− The bearing is measured in degrees from 0° up to 360°. The reference point of the bearing mea-
surement is the start point. The angle 0° is the geographical north. The measurement is done
clockwise, e.g. an object on the east side of the measurement’s start point has the bearing 90°.
− The elevation is measured in degrees from −90° up to +90°. The start point is the reference
point of the measurement. The reference plane of the elevation is a ’tangential’ plane contain-
ing the reference point, where the plane’s normal vector is parallel to the line from the center
of the earth to the reference point. For instance, an object exactly below the start point has the
elevation −90°, while an object exactly above the start point has an elevation of 90°. Due to
the earth curvature, the measurement of two points on the ground results in a negative eleva-
tion.
Measurements in the map view can be performed by holding the ’Shift’ key and dragging the
mouse holding the left button pressed (refer to section 4.4.5.1).
S the current date of the system in the format ’day−month−year hour:minute:second’.
S indicator of the activation of the ’View pursues Target’ mode (refer to section 4.4.5.1):
If the statusbar indicates "follow" the mode is active, else no indicator is shown.
S the network interface, the Technical Situation Display is currently listening to.
Fig. 4−52 TSD, Statusbar (example)
4−34 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Display Configuration Tool
4.5 DISPLAY CONFIGURATION TOOL
The Display Configuration tool is used to edit the configuration file used by the Technical Situation
Display tool, described in section 4.4. From command line, it is started with the configuration file as
only parameter. In the path, where the configuration file is located, current versions of the files display-
config.xml and DisplayConfig.dtd must be present.
The Display Configuration tool is to be launched with the XML configuration file to be edited. After
starting the tool, the window ’Display Configuration − <xml config file>’ appears (see Fig. 4−53).
Titlebar
Menubar
Toolbar
Parameter
Panel
Configuration
Tree View Statusbar
Fig. 4−53 Display Configuration Tool, main components (example)
4.5.1 Titlebar
The titlebar shows the name of the tool ’Display Configuration’ and the currently loaded configuration
file.
If configuration parameter values have been added, deleted or changed in the Parameter Panel the
supplementary hint ’(Modified)’ reveals that the configuration is still not saved.
The titlebar contains the typical window features provided by the window manager being used, i.e.
close, maximise, minimise, resize, move the window or put it to some workspaces.
4.5.2 Menubar
The menubar, see Fig. 4−54, contains the menu ’File’ and ’Help’.
Fig. 4−54 Display Configuration, Menubar
Ed. 10.07 4−35

AS 680/682 ADS−B
Display Configuration Tool Description, Operation and Maintenance
4.5.2.1 Menu ’File’
The menu ’File’, see Fig. 4−55, contains the items ’New’, ’Open’, ’Save’, ’Save As’ and ’Quit’.
Fig. 4−55 Display Configuration, Menu ’File’
S The menu item ’New’ is used to create a new configuration file. The entries of the new configuration
file are default values, which have to be edited by the user.
S It is possible to load an already existing configuration file by using the menu item ’Open’. A stan-
dard file selection box, see Fig. 4−56, opens, where a new XML configuration file can be selected.
Fig. 4−56 Configuration Tool, File Selection (example)
S Pushing the menu item ’Save’ opens a file selection box, see Fig. 4−56, to save the current set-
tings into an XML−configuration file, if a new configuration has been allocated with the help of the
’New’ menu item. If a configuration has been loaded from an already existing configuration file,
the parameter changes are automatically saved to the configuration file without opening a file
selection dialog.
S The ’Save As’ menu item opens a file selection box. Thus, the currently applied parameters and
parameter values can be saved to any file. If a configuration file is not saved in the standard direc-
tory, the user must take care that current versions of the files displayconfig.xml and DisplayCon-
fig.dtd are available in the directory (either a copy or as soft link), where the configuration file is
saved. Otherwise he will not be able to start the configuration tool with this new configuration file
from its directory.
S The Display Configuration tool is terminated, if the ’Quit’ menu item is selected.
4−36 Ed. 10.07

ADS−B AS 680/682
4.5.2.2 Menu ’Help’
The menu ’Help’ contains the item ’About’ (see Fig. 4−57).
Fig. 4−57 Display Configuration, menu ’Help’
The menu item ’About’ opens a panel, see Fig. 4−58, that shows the tool command, version, name
of the tool as well as the reference address of the supporter.
Fig. 4−58 Display Configuration, About Panel (example)
4.5.3 Toolbar
The toolbar, see Fig. 4−59, of the Technical Situation Display consists of seven items. The toolbar
tools are used to create, open, refresh and save configuration changes or to expand and shrink tree
view nodes.
New Open Save Save As

Reload Magnification
Fig. 4−59 Display Configuration, Toolbar
S The ’New’ button is used to create a new default configuration (see ’New’ menu item in 4.5.2.1).
S The ’Open’ button is used to load the existing configuration file (see ’Open’ menu item in 4.5.2.1).
S The ’Reload’ button is used to update the parameters and parameter values in the tree view and
in the parameter panel. ’Reload’ reloads the current configuration file.
S The ’Save’ button is used to save the current configuration file (see ’Save’ menu item in 4.5.2.1).
S The ’Save As’ button is used to save the curent settings (configuration) into another configuration
file (see ’Save As’ menu item in section 4.5.2.1).
S The two magnifying glasses can be used to expand or shrink nodes in the Configuration Tree
View, respectively.
Ed. 10.07 4−37

AS 680/682 ADS−B
4.5.4 Configuration Tree View
The Configuration Tree View, see Fig. 4−60, shows the hierarchy in the currently loaded configuration
file. The Configuration Tree View consists of two columns. The first column (black faces) shows the
paragraph names of the configuration file as nodes, while the second column (blue faces) shows the
corresponding, used internal XML−Reference.
The Configuration Tree View works like usual file managers.
S Simple left mouse click onto a tree node shows the parameter belonging to that node on the Pa-
rameter Panel to the left of the Configuration Tree View (see Fig. 4−61).
S Left mouse click onto right oriented arrows left to some nodes opens the corresponding hierarchy
below the corresponding item. The same result is achieved by double clicking onto a node or using
the ’+’ magnifying glass of the toolbar, refer to section 4.5.3.
S Left mouse click onto a downward oriented arrow closes the configuration parameter hierarchy
below that item. Closing of the hierarchy below is also got by the use of the ’−’ magnify glass of
the toolbar, refer to section 4.5.3.
S Vertical and horizontal scroll bars are available, if the Tree View entries exceed the boundaries.
Fig. 4−60 Display Configuration, Tree View (example)
4.5.5 Parameter Panel
The Parameter Panel of the Display Configuration tool (see Fig. 4−61) consists of three parts:
S A label showing the currently selected node name representing a paragraph of the configuration
file. In brackets there is found the corresponding XML−reference identity.
S A list of parameters and parameter values belonging to the corresponding configuration file para-
graph (The type of widgets is determined by the type of the items given in the displayconfig.xml
file).
S A button box containing the buttons ’Delete’, ’Apply’ and ’Close’.
4−38 Ed. 10.07

ADS−B AS 680/682
Fig. 4−61 Display Configuration, Parameter Panel (example)
4.5.5.1 Change of Parameter Values

Once selected a node from the Configuration Tree View, it is possible to change the corresponding
parameter values in the Parameter Panel. There are several types of widgets, which are validated on
user input, when the ’Apply’ button is pressed.
S The ’Apply’ button does not save the current entries into the currently loaded configuration file. Still
after applying, it is possible to retrieve the original parameter values from the configuration file with
the ’Refresh’ button in the toolbar, refer to section 4.5.3.
S The entries are finally stored to a configuration file, if the ’Save’ or the ’Save As’ procedure is done.
Refer to sections 4.5.2.1 or 4.5.3 for more details.
S Pressing the ’Close’ button deselects the currently selected node in Tree View and presents an
empty Parameter Panel as shown in Fig. 4−62.
S The ’Refresh’ button in the toolbar, refer to 4.5.3, reselects a currently deselected node.
S The ’Delete’ button is only sensitive, if the selected Tree View node represents a list, refer to section
4.5.5.2.
Fig. 4−62 Display Configuration, No Element Selected (example)
Ed. 10.07 4−39

AS 680/682 ADS−B
4.5.5.2 Addition and Deletion of List Items
Addition of List Items:

If the configuration file contains list items like for example the configuration paragraph ’Location’, it
is possible to add list items by the help of the Display Configuration tool.
Clicking the node, which represents a list, in the Tree View causes the appearance of a button in the
Parameter Panel with the text "Add a new ‘<list item>’ element", see Fig. 4−63.
Clicking this button shows the default values of a new list item in the Parameter Panel. It is up to the
user to update the default values, apply the changes with the ’Apply’ button and save the changed
configuration to a configuration file, refer to sections 4.5.2.1 or 4.5.3.
Fig. 4−63 Display Configuration, Add New List Item (example)
NOTE: It is not possible to enter ’xmlRefld’ in the configuration tool for added list items. The tool
will assign an automatically generated identification, e.g. ’Ground−Station057’. To
change this automatically generated identification into a preferred name, the correspond-
ing entry in the configuration file must be edited with the help of a usual editor.
Deletion of List Items:

If a user selects a list item in the Tree View, the corresponding parameters and values appear in the
Parameter Panel to the right side, see Fig. 4−64.
The ’Delete’ button becomes sensitive. Now it is possible to delete the selected list item. After con-
firmation of the deletion, it is possible to save the changed configuration values to the configuration
file as explained in 4.5.2.1 or 4.5.3.
4−40 Ed. 10.07

ADS−B AS 680/682
Fig. 4−64 Display Configuration, Delete List Item (example)
4.5.6 Statusbar
The statusbar, see Fig. 4−65, at the bottom of the Display Configuration tool shows currently per-
formed actions and their corresponding state.
Fig. 4−65 Display Configuration, Statusbar (example)
4.5.7 Parameter Panels

The following section explains the parameters, which are applicable in the Display Configuration tool.
4.5.7.1 DisplayConfig Parameters

The parameter panel DisplayConfig, see Fig. 4−66, contains some general parameters:
S The ASTERIX CAT 21 version of the data being expected. If enabled, then the older ASTERIX CAT
21 edition 0.20 data can be read and displayed, else data edition 0.23.
S File name of map: shows the path including the filename, where the vector map, displayed in the
view panel of the Technical Situation Display, is found.
S Initial rotation value of map: the loaded map can be initially displayed rotated by a configurable
angle measured in degrees.
S Max. center distance of the target: Is a value between 0 and 100 representing the section around
the center of the view, where the target may be found; if the target reaches the edge of that section,
the map will be moved so that the target is found in the center of the view. This parameter applies
only to the ’View pursues Target’ mode (refer to section 4.4.5.1).
S Font of City Names: gives the name of the font being used to display the city names in the map.
The selected font must be available on the operating system.
Ed. 10.07 4−41

AS 680/682 ADS−B
S Map in spherical representation: for ADS−B purposes this parameter has always to be enabled,
because only spherical maps are used. However, it is possible to disable this parameter, if the
loaded map represents cartesian coordinates.
S GS filter: if this parameter is checked, the GS Filter in the Technical Situation Display is available.
If this parameter is not checked, then no filtering on SAC and SIC values is performed, independent
on what is shown in the GS filter panel, refer to section 4.4.2.6.2 , of the Technical Situation Display.
S Lowest FOM/PA to be displayed: represents the lowest allowed (Figure of Merit) position accuracy
of the targets being displayed in the Technical Situation Display. This value is found in the PA filter
panel, refer to section 4.4.2.6.3 .
Fig. 4−66 Parameters DisplayConfig (example)
4.5.7.2 Window Parameters

The parameter panel Window, see Fig. 4−67, contains parameters concerning the initial size of the
main window of the Technical Situation Display:
S Width of main window:
Gives the initial and minimal width in pixels for the Technical Situation Display’s main window.
S Height of main window:
Gives the initial and minimal height in pixels for the Technical Situation Display’s main window.
Fig. 4−67 Parameters Window (example)
4−42 Ed. 10.07

ADS−B AS 680/682
4.5.7.3 Refltf Parameters
The parameter panel RefItf, see Fig. 4−68, contains parameters concerning the reference Asterix in-
terface, meaning the Asterix interface used, when starting the Technical Situation Display. Its parame-
ters can be overwritten, when the configuration is saved in the Technical Situation Display.
S Incoming Interface:
Displays the host name or the IP address of the ASTERIX interface that is opened, when the Techni-
cal Situation Display is started.
S Incoming port:
Displays the port of the ASTERIX interface that is opened, when the Technical Situation Display
is started.
Fig. 4−68 Parameters Refltf (example)
4.5.7.4 ltfParameter Parameters

The node Interface contains a list of ItfParameters, see Fig. 4−69, giving the available Asterix Inter-
faces, which can be selected in the Interface Panel, refer to section 4.4.2.6.5 , of the Technical Situa-
tion Display.
S Incoming Interface:
Displays the host name or IP address of an available ASTERIX interface.
S Incoming port:
Displays the port of an ASTERIX interface.
Fig. 4−69 Parameters ltfParameters (example)
Ed. 10.07 4−43

AS 680/682 ADS−B
4.5.7.5 RefGS Parameters

The parameter panel RefGS, see Fig. 4−70, contains parameters concerning the reference Ground
Station, meaning the view being displayed, when the Technical Situation Display is started. The first
three parameters can be overwritten, if the configuration is saved in the Technical Situation Display.
S View center latitude:
Gives the latitude of the center of the view initially displayed in the Technical Situation Display.
S View center longitude:
Gives the longitude of the center of the view initially displayed in the Technical Situation Display.
S View zoom:
Gives a factor of the initial zoom. The greater the zoom factor the more the view is zoomed out.
The value 0 is not allowed.
S GS symbol size:
Gives the size of the Ground Station symbols in the map in pixels.
S Font of the GS label:
Gives the font of the Ground Station labels in the map. The selected font must be available on the
operating system.
Fig. 4−70 Parameters RefGS (example)
4.5.7.6 Ground Station Parameters

The node Location contains a list of Ground Stations, see Fig. 4−71, showing the attributes of all avai-
lable Ground Stations of the ADS−B system.
S System Area Code (SAC):
Gives the SAC of the respective Ground Station.
S System Identification Code (SIC):
Gives the SIC of the respective Ground Station.
S Latitude of GS:
Gives the latitude of the respective displayed Ground Station symbol in degrees, which is also the
latitude of the Technical Situation Display view’s center, if this Ground Station’s view is selected.
S Longitude of GS:
Gives the longitude of the respective displayed Ground Station symbol in degrees, which is also
the longitude of the Technical Situation Display view’s center, if this Ground Station’s view is se-
lected
4−44 Ed. 10.07

ADS−B AS 680/682
S Zoom:
Gives the zoom factor of this Ground Station’s view.
S Accept data from GS:
Shows, if the GS filter for this Ground Station is active. Only applicable, if the parameter GS filter
is enabled, refer to section 4.5.7.1.
S Name of GS:
Gives the name of the Ground Station’s location.
S Label to the left of GS:
If enabled, the Ground Station label is placed to the left of the Ground Station symbol in the Techni-
cal Situation Display, else it is found to the right of the Ground Station symbol.
S Abbreviation of GS:
Gives the abbreviated name of the Ground Station.
S Show distance circles:
Shows, if distance circles shall be displayed initially around the Ground Station. This parameter
can be overwritten, if the configuration is saved in the TSD.
S Number of circles:
Represents the number of circles to be displayed, if distance circles around the Ground Station
shall be shown. The number is the position, starting from 0, in the corresponding menu of the Tech-
nical Situation Display. This parameter can be overwritten, if the configuration is saved in the Tech-
nical Situation Display.
S Difference between circles:
Represents the distance difference between circles to be displayed, if distance circles around the
Ground Station shall be shown. The number is the position, starting from 0, in the corresponding
menu of the Technical Situation Display. This parameter can be overwritten, if the configuration is
saved in the Technical Situation Display.
Fig. 4−71 Parameters Groundstation (example)
Ed. 10.07 4−45

AS 680/682 ADS−B
4.5.7.7 Display Parameters
The parameter panel Display, see Fig. 4−72, contains the background color of the map, but also para-
meters being found in the menus ’Display’ and ’Tracks’ of the Technical Situation Display (refer to
sections 4.4.2.4 and 4.4.2.5). The parameters ’Shape of plot’, ’Size of plot’, ’History of plot’ and ’Show
Detailed View’ can be changed in the Technical Situation Display and so be overwritten, if a change
is saved in the Technical Situation Display.
S Background color of map:

Represents the background color of the situation display and can be changed with help of an
OpenGL standard widget for color selection.
S Shape of plot:
It is found in the menu ’Tracks’ and gives a choice among 3 different plot shapes. The number rep-
resents the position, starting from 1, in the corresponding submenu.
S Size of plot:
It is found in the menu ’Tracks’ and gives a choice among 5 different plot sizes. The number repre-
sents the position, starting from 1, in the corresponding submenu.
S History of plot:
It is found in the menu ’Tracks’ and gives a choice among 12 different history times. The number
represents the position, starting from 0, in the corresponding submenu.
S Memory limit of history:
Gives a threshold in percent of the available physical memory. If the value ’mem limit’ is selected
in the parameter ’History of plot’, then plots representing target positions will be allocated and not
deleted until this limit is reached (refer also to section 4.4.2.5, submenu ’History’).
S Show Detailed View:
It is found in the menu ’Display’ and enables the display of the detailed view in the Technical Situa-
tion Display.
Fig. 4−72 Parameters Display (example)
4−46 Ed. 10.07

ADS−B AS 680/682
4.5.7.8 Delay Parameters
The node Display contains the parameter panel Delay, see Fig. 4−73, which can be used to enable
the display of delayed plots.
Delayed plots means the following: If a certain squitter telegram of a target is received by different
Ground Stations, every Ground Station creates an ASTERIX CAT21 telegram with the corresponding
information and sets its own time stamp as time of day into the telegram.
If the Ground Stations are not synchronised, then ASTERIX CAT21 telegrams received from one
Ground Station might have quite different time of day values than the telegrams from another Ground
Station.
If the most recent time of day value causes the skipping of older incoming telegrams, then an irregular
track of a target may be got.
S Show Delayed Plots: enable the display of delayed plots with a time of day value, which may not
be older than the
S Time Tolerance: in seconds before the most recent time of day value, received at the Technical
Situation Display.
Fig. 4−73 Parameters Delay (example)
4.5.7.9 Grid Parameters

The node Display contains the parameter panel Grid, see Fig. 4−74, which can be used to overlay
the view with a squared grid.
S Show Grid; indicates, if the grid is displayed at start of the Technical Situation Display. This parame-
ter can be overwritten, if the configuration is saved in the Technical Situation Display.
S Width of Grid cells: represents the width and height of the grid squares. In case of spherical maps,
it is not possible to give a unit for the width, because the width is not constant according to the
earth sphere. If a cartesian map is used, then the unit is meters.
Ed. 10.07 4−47

AS 680/682 ADS−B
S Color of Grid: represents the color of the grid.
Fig. 4−74 Parameters Grid (example)
4.5.7.10 Speed Vector Parameters

The node Display contains the parameter panel SpeedVector, see Fig. 4−75, which can be used to
configure length and color of the speed vector of the tracks shown in the Technical Situation Display.
S Length of Speed Vector: is found in the menu ’Tracks’ and gives a choice among 6 different speed
vector lengths. The number represents the position, starting from 0, in the corresponding sub-
menu of the Technical Display, refer to section 4.4.2.5. This parameter can be overwritten, if the
configuration is saved in the Technical Situation Display.
S Color of Speed Vector: represents the color of the grid.
Fig. 4−75 Parameters SpeedVector (example)
4−48 Ed. 10.07

ADS−B AS 680/682
4.5.7.11 Compass Parameters
The parameter panel Compass, see Fig. 4−76, is used to configure the compass symbol in the upper
left corner of the Technical Situation Display’s view.
S Show Compass; indicates, if the compass is displayed at start of the Technical Situation Display.
This parameter can be overwritten, if the configuration is saved in the Technical Situation Display
S Color of Compass’ North: represents the current initial color of the north vertex of the compass.
S Color of Compass’ South: represents the current initial color of the south vertex of the compass.
Fig. 4−76 Parameters Compass (example)
4.5.7.12 FLPanel Parameters

The parameter panel FLPanel, see Fig. 4−77, is used to show or hide the Flight Level Panel, when
the Technical Situation Display is started.
Fig. 4−77 Parameters FLPanel (example)
Ed. 10.07 4−49

AS 680/682 ADS−B
4.5.7.13 Marking Parameters

The node ’Marking’ contains the parameter panels for the different marking possibilities. These layers
can be found in the menu ’Markings’ of the Technical Situation Display, refer to section 4.4. The config-
uration panels of the different layers are equal in structure. Hence, the parameter panel of the map
item ’Spi’, Fig. 4−78, serves exemplary to explain also the parameter panels of the other marking
items.
S The ’Activate mark’ enabler activates the highlighting of tracks, which apply to the conditions deter-
mined in the following attributes.
S The ’Value marking target’ text field contains the value of the SPI (in the present case), when the
respective track shall be highlighted.
S The ’Priority’ value, an integer value, determines the priority of the present marking. For it is pos-
sible that a target applies to several markings, the priority tells, which marking shall overrule. The
higher the priority value the higher the priority.
Example:
If the marking of a certain ’PA’, e.g. PA = 8, is set to green and the marking of the ’SPI’ value ’1’
is red and if both markings are activated, then the target applying to both conditions is shown in
the colour of the marking of the highest priority.
S If the ’Activate blinker’ flag is enabled, tracks, which apply to the respective condition, are dis-
played with the corresponding colour, but with blinking target label.
S The colour widget enables the user to change the colour and opacity of the target’s label applying
to the condition of the respective activated mark.
Fig. 4−78 Parameters Marking (example)
4.5.7.14 Detail Parameters

The parameter panel Detail, see Fig. 4−79, is used to configure the Asterix Data Fields, which shall
be displayed in the Detailed View of the Technical Situation Display, refer to section 4.4.4. Asterix
Fields are shown, if enabled.
4−50 Ed. 10.07

ADS−B AS 680/682
Fig. 4−79 Parameters Detail (example)
4.5.7.15 Plot and Label Parameters

The parameter panel Plot and Label, see Fig. 4−80, is used to configure the colors and fonts for plots
and labels representing targets on the Technical Situation Display.
Fig. 4−80 Parameters Plot and Label

S Use of background color: gives the possibility to enable or disable the background color for the
targets’ label in the Technical Situation Display.
S Use of plot age transparency: indicates, if target plots and target label will fade out slowly, if becom-
ing older or if plots and labels shall disappear suddenly, when the target’s history age expires.
Ed. 10.07 4−51

AS 680/682 ADS−B
S Background color of selected label: represents the background color of labels of selected targets.
S Color of selected plot: represents the color of the plots of selected targets.
S Font of the target label: gives the font to be used for the target labels. The selected font must be
available on the operating system.
4.5.7.16 Map Items Parameters

The node Map contains the parameter panels for the different map layers. These layers can be found
in the menu ’Map Items’ of the Technical Situation Display. The configuration panels of the different
layers are equal in structure. Hence, the parameter panel of the map item Road, see Fig. 4−81, serves
exemplary to explain also the parameter panels of the other map items (layers).
S Name of Map Layer: represents the name of the layer containing corresponding map items. This
name must be exactly equal (case sensitivity!) to the corresponding layer name in the *.reg file
containing the vector map of the situation display. Thus it is possible to add, delete or change lay-
ers in a driven way.
NOTE: The Ground Station layer is the only layer being not found in the vector map. Its layer
name must not be reused for other layers and must not be changed!
S Show Roads in menu: enables the display of roads as layer on the map view. Roads are only
loaded from the map’s vector map file, if this checkbox is enabled. And only, if this parameter is
enabled, the corresponding layer is found in the menu ’Map Item’.
S Display of Roads: Only if the parameter ’Show Roads in menu’ is enabled, it is possible to show
roads on the map. In that case the corresponding entry in the menu ’Map Items’ shows a tick. If
’Display of Roads’ is disabled, the layer Roads is hidden on the map and no tick is found in front
of the corresponding map item. This parameter can be overwritten, if the configuration is saved
in the Technical Situation Display.
S Color: represents the color used to display the map layer.
Fig. 4−81 Parameters Road (example)
4−52 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Record and Replay
4.6 ADS−B TOOLS: RECORD AND REPLAY
The record and replay tools can be categorized into two groups:
S One group contains the tools that handle so−called raw data. Raw data are the not decoded data
sent by targets. Raw data are the content of the downlink telegrams as byte sequence received
by the Ground Station at the interface to the telegram sender.
S The other group contains the tools that handle the ASTERIX data. ADS−B provides the ASTERIX
CAT 21 protocol, edition 0.20 and edition 0.23.
4.6.1 Starting the Tools
Starting a record or replay tool is done by means of the desktop panel at the bottom of the LCMS
screen or of the RCMS screen 0. The menu ’ADS−B Tools’ provides the available record and replay
tools (see Fig. 4−82).
The tools can be started in command line mode, too. This is a mode assuming that the environment
(e.g. the variable LD_LIBRARY_PATH) is set correctly and the command is executed in the path,
where the tools are found. Some experiences with the operating system are advantageous.
NOTE: Because of safety reasons, the replay tool ’RRP’ (Replay raw data send raw data) is not
available in the pull−down menu ’ADS−B Tools’, but only in command line mode. The
RRP tool is described in section 4.6.4 of this manual.
Fig. 4−82 Desktop panel menu with ’ADS−B Tools’ for record and replay (example)
4.6.2 General Structure of the GUI
After starting a record or replay tool, a window as shown in Fig. 4−83 pops up, which consists of the
components titlebar, menubar, toolbar, notebook and statusbar. These components are common to
all the record and the replay tools of the ADS−B system.
Notes, warnings and errors are shown as dialog boxes popping up.
The selected parameters in the notebook can be saved to configuration files. The tools can be started
from the terminal with a given configuration file name, e.g. ‘recordraw –g −−config myConfigura-
tion.cfg’. The default configuration file name has a name according to the corresponding tool name
and the extension *.cfg, e.g. rawrecord.cfg.
Ed. 10.07 4−53

AS 680/682 ADS−B
Record and Replay Description, Operation and Maintenance
The option ’−g’ in the command starts the graphical tool mode and ’config <config file>’ enables
the user to pass a configuration file to the tool. The default configuration file must be present in the
path /usr/local/etc. If no valid configuration file exists, the tool allocates one by itself or throws an error
and exits. The settings are stored, when the tool is quit. The user explicitly saves the configuration
via the menu item ‘Save Configuration’ of the file menu shown in section 4.6.2.2.1 .
It is possible to load another configuration file via the menu item ‘Load Configuration’ of the file menu
shown in section 4.6.2.2.1 .
Changing of parameters during the replay or record process has no effect. The tool must be stopped
or paused, before the new parameter settings apply.
The components common for all record and replay tool windows are:
− titlebar
− menubar
− toolbar
− notebook
− notebook pages
− statusbar
The common components are described in the following sections 4.6.2.1 to 4.6.2.5. The functions
(pages) which are special for a certain record or replay tool (RRP, RAC, RRC, ARC or ARP) are descri-
bed in the corresponding section 4.6.3 to 4.6.7.
Titlebar
Menubar
Toolbar
Notebook
Notebook Pages
Statusbar
Fig. 4−83 Record/Replay tools, components of start window (example)
4−54 Ed. 10.07

ADS−B AS 680/682
4.6.2.1 Titlebar
The titlebar shows the short name of the tool just started, and the name of the currently loaded config-
uration file. In the example Fig. 4−83, the shown tool is the Raw Data Recorder ’RRC’, which has
loaded the configuration file recordraw.cfg. Additionally, the titlebar contains the typical window fea-
tures provided by the used window manager, which may be, e.g.: close, maximise, minimise, resize,
move the window or put it to some workspaces.
4.6.2.2 Menubar
The menubar (refer to Fig. 4−83) contains the menus ’File’, ’Command’ and ’Help’. All menus are
tear−off menus, i.e. clicking on the dotted line of a selected menu opens the menu in a usual, sepa-
rate window. A tear−off window does not close on selecting one of its menu items.
Fig. 4−84 Record/Replay, menubar
4.6.2.2.1 Menu ’File’

The menu ’File’ contains the five entries
. clears the content of the text field in the notebook page Screen Output
. opens a selection box to save the content of the text field screen
. opens a selection box to load new configuration
. opens a selection box to save current configuration
. quits the application (exit the tool)
Fig. 4−85 Record/Replay, menu File
The menu items ’Clear’ and ’Save Screen Output As’ are related to the ’Screen Output’, a notebook
page, which are explained later in detail (refer to section 4.6.2.4.2 ). The ’Screen Output’ contains data
recorded or replayed by the tool. The ’Screen Output’ is a text field, where input or output data are
logged, respectively. The menu items ’Load Configuration ...’ and ’Save Configuration As’ are used
to load and save the settings found on the following notebook pages.
4.6.2.2.2 Menu ’Command’
The menu ’Command’ contains the available commands to start and stop the tool. These commands
are different depending on the use of replay or record tools.
In case of record tools, the ’Command’ menu contains only the ’Record’/’Stop’ submenu.
The ’Record’ button changes to the ’Stop’ function , if the tool is recording. Selecting the ’Re-
cord’ function starts the record tool until recording is explicitly stopped with the stop function.
In case of replay tools, the ’Command’ menu contains the ’Play’/’Pause’, the ’Stop’, the single step
’Next’ and the single step ’Previous’ functions (refer to Fig. 4−91).
Ed. 10.07 4−55

AS 680/682 ADS−B
The replay tools contain four buttons/functions in the menu ’Command’, which are the following:
. start and play the replaying process

. stop and reset the replaying process
. read the next input record
. read the previous record
Fig. 4−86 Command Buttons for Replay
The first button is the ’Play’ button to start the replay process. This button changes to a ’Pause’ button,
if pressed. Conversely, the ’Pause’ button becomes a ’Play’ button, if pressed. Pushing the ’Pause’
button interrupts the replay, i.e. a subsequent click on the ’Play’ button continues the replay at the
record, where the replay process has been interrupted before.
The toolbar (see section 4.6.2.3) contains the same features as the menu ’Command’. The state of
the buttons in the toolbar are consistent to the state of the corresponding menu items of the menu
’Command’.
Depending on the settings in the different tools, some buttons become insensitive. More details are
found in the description of the corresponding tools (sections 4.6.3 to 4.6.7).
4.6.2.2.3 Menu ’Help’
The menu ’Help’ (refer to Fig. 4−87) offers the selection of the menu item ’About’, opening an informa-
tion panel and in case of the Raw Record (RRC) tool, the additional possibility to open a reference
panel showing the structure and format of Raw Record telegrams.
Fig. 4−87 Record/Replay, About menu
The information panel shows the tool command, version, name of the tool, building date, the user,
who built the tool as well as the reference address of the supporter (refer to Fig. 4−88).
Fig. 4−88 Record/Replay tools, ’About’ panel (example)
4−56 Ed. 10.07

ADS−B AS 680/682
The Raw Record Reference panel shows the format of the Raw Record telegrams and the order they
are found inside a data block.
Fig. 4−89 Record/Replay tools, ’Reference’ panel (example)
4.6.2.3 Toolbar
The toolbar contains the same features as the menu ’Command’. The state of the buttons in the tool-
bar are consistent to the state of the corresponding menu items of the menu ’Command’.
4.6.2.3.1 Toolbar Record Tools

In case of recording tools, the toolbar contains only the ’Start’/’Stop’ button (refer to Fig. 4−90).
Fig. 4−90 Toolbar of Record Tool
4.6.2.3.2 Toolbar Replay Tools

In case of replay tools, the toolbar contains the ’Start’/’Pause’, the ’Stop’, the single step ’Next’ and
the single step ’Previous’ buttons (refer to Fig. 4−91).
Fig. 4−91 Toolbar of Replay Tool
Ed. 10.07 4−57

AS 680/682 ADS−B
4.6.2.4 Notebook Pages
The main panels of the tools have the layout of a notebook. The pages ’Top’ and ’Screen Output’ are
pages common to all replay and record tools. These pages are introduced in this section. The other
pages depend on the respective tools and are explained later on, in the corresponding sections.
4.6.2.4.1 Page ’Top’
The page ’Top’ has no functional meaning, but shows an introducing picture, the logo of the company
THALES and the name of the current tool (refer to Fig. 4−92).
Fig. 4−92 Record/Replay tools, ’Top’ page (example)
4.6.2.4.2 Page ’Screen Output’

The page ’Screen Output’ (refer to Fig. 4−93) is a textfield used to log the replayed or recorded data.
It shows logs in different layouts, e.g. in well readable format, decoded format or just in the format,
the data are written into or read from files. The text within the ’Screen Output’ is editable. Hence it is
possible to enter user comments or delete text. The horizontal and vertical scrollbars are used to navi-
gate through the text.
The ’Screen Output’ can be saved as usual text into a file by selecting the option ’Save Screen Output
As’ from the menu ’File’. So it is possible to continue working up the text in an arbitrary editor. The
’Screen Output’ can be cleared with the option ’Clear’ of the menu ’File’ (see section 4.6.2.2.1 ).
NOTE: The page ’Screen Output’ is a text buffer, which can be limited in a textfield of a following
notebook page. The corresponding textfield contains the maximum number of lines the
’Screen Output’ buffer shall contain. The number of lines of the ’Screen Output’ buffer is
limited to the range of 100 up to 10,000 lines.
4−58 Ed. 10.07

ADS−B AS 680/682
Fig. 4−93 Record/Replay tools, ’Screen Output’ page (example)
4.6.2.5 Statusbar
The statusbar of the replay and record tools at the bottom of the display is used to indicate, if the tool
is running and to show some status messages (see Fig. 4−94).
The indicator, showing whether a tool is just recording or replaying, is a little blue bar in the left bottom
corner of the tools swapping left and right while the tool is reading from or writing to the network.
A status message is a one−line text, saying for example, if logging of recorded data is only done to
the ’Screen Output’ (see section 4.6.2.4.2 ) or into a file.
Fig. 4−94 Statusbar of Replay Tool (example)
Ed. 10.07 4−59

AS 680/682 ADS−B
4.6.3 ADS−B Raw Data Record Tool (RRC)
The ’Raw Data Record’ tool listens to a socket and records data in a file or on the ’Screen Output’.
The configuration parameters and their meanings are described in this section in context of the re-
spective notebook pages of the ’Raw Data Record’ tool.
4.6.3.1 RRC Notebook Page ’Parameter’
The notebook page ’Parameter’ (refer to Fig. 4−95) is used to adjust the most important parameters
for the ’Raw Data Record’ tool.
Fig. 4−95 RRC, page ’Parameter’ (example)
4.6.3.1.1 RRC Parameter: Interface

A mandatory parameter is the address of the interface, where the tool shall listen to. The address con-
sists of the hostname and the port of the socket, where the incoming data are expected. It is possible
to enter the hostname of the interface as it is known to the present host, e.g. ’localhost’, or to enter
the IP−address, e.g. 127.0.0.1. If the incoming data are not of raw data format, the warning "WARN-
ING: Received no Raw data! Returning!" is prompted to standard output.
4.6.3.1.2 RRC Parameter: Output

The output of the received data can be done on the ’Screen Output’ (refer to section 4.6.2.4.2 ) as
well as into a file.
The size of the ’Screen Output’ buffer can be limited in the corresponding text field. The textfield con-
tains the maximum number of lines, the ’Screen Output’ buffer shall contain.
4−60 Ed. 10.07

ADS−B AS 680/682
The selection of the required output destination is done with checkboxes. If both checkboxes are disa-
bled, the received data is logged to standard output on that terminal, where the tool is started. The
logging to standard output can be used to pipe the received data to standard input of another tool,
e.g. to the tools ’Replay Raw Data Send Raw Data’ (refer to section 4.6.4) or ’Replay Raw Data Send
Asterix Data’ (refer to section 4.6.5). Later on, it is described, how the ’Replay Raw Data Send Raw
Data’ tool can read from standard input (refer to section 4.6.4.1.1 ).
4.6.3.1.3 RRC Parameter: Logging Format

There is a proprietary format for logging of raw data. The layout of this format consists of:
S the identification of the system area (System Areas Code: SAC)
S the identification of the Ground Station within the system area (System Identification Code: SIC)
S the timestamp, when the telegram has been received at the recording tool (in seconds since mid-
night with a precision of 3 decimal in UTC system time)
S the time of day, when the telegram has been sent by the Ground Station (in seconds since midnight
with a precision of 3 decimal in UTC system time)
S the time of arrival of the downlink telegram at the Ground Station with a precision of 9 decimal for
internal use in a Ground Station specific time.
S the downlink telegram format type
S the world wide unique ICAO−address (Mode S address) of the target in hexadecimal representa-
tion
S the not decoded downlink telegram message in hexadecimal representation
S the confidence bits for internal use in hexadecimal representation
S the signal amplitude for internal use in hexadecimal representation
Example of a logged record in proprietary format:

096 007 70756.591 32449.230 6020.026122437 17 4004C3 8F4004C390B981923FF879000000 −− AA
Logging to ’Screen Output’ can be done in the same format being used for file logging or it can be
chosen a better readable, verbose mode, which contains the same items, but the items are shown
in a list. The Mode S addresses are partially decoded in that case.
The verbose logging format is only applicable for logging to ’Screen Output’ and contains the follo-
wing items:
S the system area code, called source area
S the Ground Station identification, called source id or system identification code
S the mode S address of the sending target
S the time of receipt of the downlink telegram in seconds since midnight in UTC time
S the time of day, when the telegram has been sent from the Ground Station in UTC time
S the time of arrival of the telegram in the Ground Station based on the Ground Station internal clock,
not system time
S the downlink format type
Ed. 10.07 4−61

AS 680/682 ADS−B
S the not decoded downlink telegram data
S the confidence bits
S the signal amplitude
S the mode 3/A address (squawk)
S the tail number
S the flight plan
S the country obtained from the mode S address
Example:
Area Id (SAC): 96
Source Id (SIC): 7
Mode S Address: 4004C3
Time of Receipt: 07:24:49 (26689.388)
Time of Day: 07:24:49 (26689.388)
Time of Arrival: 3324.388488574
Downlink Format: 17
Telegram Data: 8F4004C390B981923FF879000000
Confidence Bits: 69
Signal Amplitude: AA
Squawk: −−
Tail Number: −−
Flight Plan: −−
Country: United Kingdom
4.6.3.1.4 RRC Parameter: File Logging

If logging into a file is selected on the notebook page ’Parameter’, the following parameters can be
set (see Fig. 4−95). The logfile has to be chosen, where the received data shall be written to. A file-
name can immediately be entered into the textfield ’Filename’, or the button ’Choose’ can be pushed
to get a file selection box as shown in Fig. 4−96.
Fig. 4−96 RRC, File Selection Box (example)
4−62 Ed. 10.07

ADS−B AS 680/682
4.6.3.1.5 RRC Parameter: Automatic File Increment
It is possible to select the checkbox ’Automatic file increment ...’ to limit the size of a logfile automati-
cally by a certain number of records. Checking this feature makes a textfield sensitive, where the maxi-
mum number of records (being equal to the maximum number of lines) of a logfile can be entered.
If the recording reaches the given number of records, then the current logfile is closed and a new one
is automatically allocated to continue recording.
The naming of the files is managed as follows. Starting the recording process, the tool takes the name
of the logfile from the textfield ’Filename’ and extends this name by date, time and the extension *.log.
The date is expressed in the sequence ’year.month.day’, the time in the sequence ’hour_minute_sec-
ond’, e.g. logfile−2004.03.25−09_46_40.log is an automatically allocated file, if the ’Filename’ en-
tered, is ‘logfile’.
4.6.3.1.6 RRC Parameter: Log Buffering
Writing to a file or to the ’Screen Output’ with every incoming telegram, takes a lot of performance.
Hence it is possible to buffer the received data and perform the writing action only, when a certain
number of telegrams has arrived (log buffering).
A drop−down menu becomes sensitive, if the check box ’I/O Performance’ is selected. The drop−
down menu enables the user to select a buffer size, measured in bytes or kbytes. Whenever an inter-
nal buffer of the tool reaches the given limit, the tool flushes its buffer to output. If the tool is stopped,
the remaining data in the buffer are flushed, even when the buffer size is not reached.
NOTE: It can easily happen that a user is wondering about the missing data of an expected out-
put. If buffering is enabled, the output occurs perhaps very much later depending on the
chosen buffer size.
Ed. 10.07 4−63

AS 680/682 ADS−B
4.6.3.2 RRC Notebook Page ’Filter’
The ’Raw Data Record’ tool provides some filter parameters, shown in Fig. 4−97.
S It is possible to record only data coming from a certain Ground Station within a system area. Clik-
king the corresponding check, it is possible to enter a System Area Code (SAC) and a Ground
Station identification, called SIC, into the corresponding textfields. Only telegrams coming from
that given Ground Station are recorded.
S It is possible to record only telegrams from a certain target, e.g. from a site monitor. In that case
the user must enable the corresponding check and enter the target address of the target to be re-
corded. The target address is expected in a hexadecimal representation, but it is not case sensi-
tive, so it does not matter, if an address ‘4004C1’ or ‘4004c1’ is entered.
S It is possible to use the asterisk ‘*’ as wildcard, i.e. ‘4004*’, for instance, accepts all targets with
an address starting with ‘4004’. This wildcard is only possible as last character of the search string,
e.g. search strings ‘4004*1’ and ‘*4C1’ do not work.
S It is possible to record only telegrams of certain downlink formats. Enabling the checkbox ’Record
only downlink format’ activates a matrix of 24 checks, each representing a different downlink for-
mat. It is possible to check the formats to be recorded. Extended squitters have the downlink for-
mat 17 and 18 (Note: The mode 3/A address is contained in the downlink formats 5 and 21).
Fig. 4−97 RRC, page ’Filter’ (example)
4−64 Ed. 10.07

ADS−B AS 680/682
4.6.4 ADS−B Replay Raw Data Send Raw Data Tool (RRP)
The ’Replay Raw Data Send Raw Data’ tool reads raw data from a file or from standard input, performs
no CPR decoding on the received data and sends the received data as raw data to a certain interface,
identified by a hostname and a port. The configuration parameters and their meanings are described
in the present paragraph in the context of the respective notebook pages of the ’Replay Raw Data
Send Raw Data’ tool.
Because of safety reasons, the replay tool ’RRP’ (Replay raw data send raw data) is not available in
the pull−down menu ’ADS−B Tools’, but only in command line mode.
To start the RRP tool, the user has to open a Terminal application (via desktop panel) and to enter
the command from terminal /usr/local/adsb−tools/bin/replayrawsendraw −g. The corre-
sponding start window appears on the screen.
4.6.4.1 RRP Notebook Page ’I/O Parameter’
The page ’I/O parameter’ (refer to Fig. 4−98) offers some parameters to specify the source and the
destination of the replay.
Fig. 4−98 RRP, page ’I/O Parameter’ (example)
Ed. 10.07 4−65

AS 680/682 ADS−B
4.6.4.1.1 RRP I/O Parameter: Input
It is possible to select the source of the input data. The input may either come from standard input
or from a file.
If standard input is selected, the standard output of another tool must be piped to this tool (refer to
section 4.6.3.1.2 of the ’Raw Data Record’ tool), else the option ’standard input’ is not applicable.
Example:
The command "recordraw –e localhost –p 5545 | replayrawsendraw –g" starts the ’Raw Data Record’
tool listening to port 5545 of the local host. The received data are not logged to standard output, but
piped to the ’Replay Raw Data Send Raw Data’ tool, which starts up in graphical mode. The ’Replay
Raw Data Send Raw Data’ tool replays the data received via standard input, if the corresponding radio
button is selected and replay is started.
If selecting the radio button ’file’, it is possible to choose an input file by pressing the button ’Choose’,
which opens a file selection dialog as shown in section 4.6.3.1.4 .
NOTE: It is not possible to enter the input file name directly into the textfield. The destination host
can be changed only by a supervisor user in a non−intuitive fashion in order to avoid acci-
dental replay of data into a live operational system.
If the data read from input are not of raw data format, then an error message is written to standard
output. The error message says that there are missing columns in the read records.
4.6.4.1.2 RRP I/O Parameter: Interface
A mandatory parameter is the address of the interface, where data shall be sent to. The address con-
sists of the hostname and the port of the socket, to which the data have to be output. Only the IP port
can be changed within the application. The hostname is a parameter only accessible within the config-
uration file (access restrictions apply).
4.6.4.1.3 RRP I/O Parameter: Logging
Logging to ’Screen Output’ can be done in the same format being used for file logging (one line per
record) or in a verbose mode. The layouts of the formats are introduced in section 4.6.3.1.3 .
tains the maximum number of lines, the ’Screen Output’ buffer shall contain.
4−66 Ed. 10.07

ADS−B AS 680/682
4.6.4.2 RRP Notebook Page ’Data Parameter’
The notebook page ’Data Parameter’ (refer to Fig. 4−99) contains settings concerning time schedul-
ing and filters.
Fig. 4−99 RRP, page ’Data Parameter’ (example)
4.6.4.2.1 RRP Data Parameter: Replay Factor
It is possible to speed up or slow down the replay by a replay factor. However, this feature is only avai-
lable, if reading from file. Reading from standard input is done with the speed that the incoming tele-
grams dictate.
If the replay factor is set to 1, replay is done according to the time determined by the input records.
The delay between the sending of two consecutive telegrams is given by the difference of the time
of day, if available, or by the difference of the time of receipt, found as fourth and third entry in every
raw data record.
The delay is calculated by the replay factor multiplied with the time difference of two consecutive tele-
grams. That means: replay speeds up by the factor 10, if entering the replay factor 0.1, replay slows
down by the factor 10, if entering the replay factor 10.
Ed. 10.07 4−67

AS 680/682 ADS−B
4.6.4.2.2 RRP Data Parameter: Time Scheduling
It is possible to replay only a certain part of a replay file. This feature is only applicable, if reading from
file and not from standard input. To replay a part of an input file, a starting time and a duration is
needed.
For that reason there is an indication, at which time of day (in hours, minutes and seconds) the input
time starts and how long (in hours, minutes and seconds) the reading of the input file lasts according
to the timestamps given in the input. This information is updated every time, when the file selection
box, which opens pressing the ’Choose’ button on the page ’I/O Parameter’, is closed. This is why
it is not possible to enter an input file directly into the ’Filename’ textfield of the page ’I/O Parameter’
referring to section 4.6.4.1.1 .
The information about the start and the duration given in the input file, is a help to determine the range,
the user intents to replay.
The user enters the desired start of replay interval and a duration of the replay by entering a duration
of the format ‘hours:minutes:seconds’ or ‘seconds’ into the corresponding text fields. Even a duration
of more than 24 hours is possible, although the start of interval can only be within the first 24 hours
since starting time given in the replay file.
It is only possible to select a replay interval inside the interval calculated by the tool. If a start time
outside the applicable replay interval is selected, then start time is automatically set back to the begin-
ning of the replay file.
The actual replay time can be shortened or lengthened by entering a corresponding replay factor (see
section 4.6.4.2.1 ).
4.6.4.2.3 RRP Data Parameter: Filter
The filter settings are a part of the notebook page ’Data Parameter’. The following filters are available:
S It is possible to replay only data recorded from a certain Ground Station. Clicking the correspond-
ing check, enables the user to enter a System Area Code and a Ground Station identification (Sy-
stem Identification Code) into the corresponding textfield. Only telegrams of the Ground Station
with the given identification are replayed.
S It is possible to replay only telegrams recorded from certain targets, e.g. from a site monitor. In that
case, the corresponding check must be enabled and the target address of the target to be replayed
has to be entered. The target address is expected in a hexadecimal representation, but is not case
sensitive, i.e. it does not matter, if an address 4004C1 or 4004c1 is entered.
It is possible to use the asterisk ‘*’ as wildcard, i.e. ‘4004*’, for instance, accepts all targets with
an address starting with ‘4004’. This wildcard is only possible as last character of the search string,
e.g. search strings ‘4004*1’ and ‘*4C1’ do not work.
4−68 Ed. 10.07

ADS−B AS 680/682
4.6.5 ADS−B Replay Raw Data Send Asterix Data Tool (RAC)
The ’Replay Raw Data Send Asterix Data’ tool (Raw data Asterix Converter) reads raw data from a
file or from standard input, performs a CPR−Decoding and sends the ’CPR−decoded’ data in AS-
TERIX CAT 21 format to a certain interface, identified by a hostname and a port. The configuration
parameters and their meanings are described in the present paragraph in the context of the respective
notebook pages of the ’Replay Raw Data Send Raw Data’ tool.
4.6.5.1 RAC Notebook Page ’I/O Parameter’
The page ’I/O parameter’ (see Fig. 4−100) offers some parameters to specify the source and logging
possibilities of the replay process. The destination IP address can only be set within the configuration
file (with limited access rights) as it is potentially dangerous to replay data into a live system.
Concerning the selection of input and interface, refer to the corresponding sections of the ’Replay
Raw Data Send Raw Data’ tool in section 4.6.4.1.
A main feature of the ’Replay Raw Data Send Asterix Data’ tool is logging. The output of the replay
process can be written to the ’Screen Output’, into a file or to standard output. If no output is specified,
no logging is done.
Fig. 4−100 RAC, page ’I/O Parameter’ (example)
Ed. 10.07 4−69

AS 680/682 ADS−B
4.6.5.1.1 RAC I/O Parameter: Logging to File and Standard Output
The logging to file and to standard output is rather easy. Only the ASTERIX output data can be logged.
File logging of raw data is not necessary, because the input file contains the raw data or, if read from
standard input, the raw data can be logged by the ’Raw Data Record’ tool (refer to section 4.6.2.4)
providing the input.
In case of logging to a file the ’Automatic file increment’ feature can be enabled. More information
about this feature is found in section 4.6.3.1.5 . The logged ASTERIX data can be read from the ’Re-
play Asterix Data’ tool described in section 4.6.7.
The following proprietary format is used for the ASTERIX output.
If logging to a file is enabled, the first row is a comment line starting with a ‘#’. The next item in the
comment line indicates the ASTERIX category, that is ‘CAT21’. Subsequently the ASTERIX fields and
subfields are assigned to positions to be able to locate ASTERIX field values. In the following (non−
comment) lines, all ASTERIX fields and subfields are listed, set to the position described in the first
comment line.
Logging to standard output does not output the comment line, because, in general, the first line to
standard output is not catched by tools reading the output. However, every logfile must get the first
comment line.
The actual logged ASTERIX records, being the values of the ASTERIX fields and subfields, are listed
‘|’ separated in the sequence described in the first comment line. If no values are available a ‘−‘ is
required instead.
Example of ASTERIX logging:

# CAT21 1:ds_sac 2:ds_sic 3:trd_dcr 4:trd_gbs 5:trd_sim 6:trd_tst 7:trd_rab 8:trd_saa 9:trd_spi 10:trd_vn
11:trd_atp 12:trd_arc 13:tod 14:wgs_lat 15:wgs_lon 16:add 17:galt 18:fom_ac 19:fom_mn 20:fom_dc
21:fom_pa 22:lt_mds 23:lt_uat 24:lt_vdl 25:lt_otr 26:roll 27:fl 28:as_im 29:as_as 30:tas 31:head 32:barvr
33:geovr 34:gv_gs 35:gv_ta 36:rot_ri 37:rot_rot 38:tid 39:vac 40:toda 41:ts 42:ec 43:mr_ind 44:mr_ws
45:mr_wd 46:mr_tmp 47:mr_trb 48:issa_sas 49:issa_src 50:issa_alt 51:fssa_mv 52:fssa_ah 53:fssa_am
54:fssa_alt 55:ti_ind 56:ti_nav 57:ti_nvb 58:ti_rep 59:ti0_tca 60:ti0_nc 61:ti0_tcp 62:ti0_alt 63:ti0_lat 64:ti0_lon
65:ti0_pt 66:ti0_td 67:ti0_tra 68:ti0_toa 69:ti0_tov 70:ti0_ttr 71:ti1_tca 72:ti1_nc 73:ti1_tcp 74:ti1_alt 75:ti1_lat
76:ti1_lon 77:ti1_pt 78:ti1_td 79:ti1_tra 80:ti1_toa 81:ti1_tov 82:ti1_ttr 83:sigam 84:m3a 85:m3a_gc
86:m3a_cne 87:m3a_m3a
96|7|0|0|0|0|0|0|0|0|1|0|49559.391|−|−|400A55|38000.00|−|−|−|−|1|0|0|0|−|370.00|−|−|−
|−|−|62.50|0.141052|128.7653|−|−|−|0|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|
−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|
96|7|0|0|0|0|0|0|0|0|1|0|49559.508|−|−|3C6666|−|−|−|−|−|1|0|0|0|−|220.25|1|0.553000|35
6|−|−62.50|−|−|−|−|−|−|0|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|
−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|−|
Logging ASTERIX data means the logging of output data, i.e. only successfully decoded and checks
passing telegrams are considered. To be able to reconstruct the processing (from reading raw data
to sending ASTERIX data) performed by the tool, it is necessary to trace the telegrams. The tracing
of the replay is possible by enabling the ’Detailed Telegram Decomposition’ mode (refer to section
4.6.5.2 and to following section 4.6.5.1.2 )
4−70 Ed. 10.07

ADS−B AS 680/682
4.6.5.1.2 RAC I/O Parameter: Logging to Screen Output
The tool tries always to decode the incoming raw data.
The logging on ’Screen Output’ gives the possibility to take a view to the raw data input, to the de-
coded raw data and to the ASTERIX encoded output. The size of the ’Screen Output’ buffer can be
limited in the corresponding text field. The textfield contains the maximal number of lines, the ’Screen
Output’ buffer shall contain.
On the other side, logging to file and standard output comprises only the logging of the ASTERIX out-
put. Every read record gets a sequentially incremented input number, no matter, if the input data can
be decoded or not. Every send ASTERIX data block gets a sequentially ordered output number.
The output number increases with every data block sent. The input number decreases, if using the
single step ’Previous’ button (refer to section 4.6.2.2.2 ) to read previous records of a file, else it in-
creases.
Stepping forward with the ’Previous’ button does not output reasonable decoding results because
of timestamps running backward.
The input number plus raw data input string are always shown on the ’Screen Output’, even if there
is no ASTERIX output generated. The layout of the input line is
IN #<input number>: <raw data>
Example:
IN #000011: 096 005 26704.120 26704.120 8055.581931656 17 3C658C 8D3C658C9055C1A897D4EA000000 −− −−
’Screen Output’ ASTERIX data are always logged in a well readable format. Only valid ASTERIX fields
are logged. The output format has the following layout:
OUT #<output number>: <extended squitter type and decoding information>
<UAP identification of ASTERIX field>: <field value in hex> [<user readable field value>]
Example:
OUT #000002: EVEN EXTENDED SQUITTER AIRBORNE POSITION WITH GLOBAL COMPUTATION
I021/010: 0x6005 [SAC: 96; SIC: 5]
I021/030: 0x34283A [TOD: 07:25:04.455 (26704.455 s)]
I021/040: 0x0020 [TRD DCR: 0; GBS: 0; SIM: 0; TST: 0; RAB: 0; SAA: 0; SPI: 0; VN: 0; ATP: 1; ARC: 0]
I021/080: 0x400A54 [TADD: 400A54]
I021/090: 0x0006 [FOM AC: 0; MN: 0; DC: 0; PA: 6]
I021/095: 0x00 [VACC: 0]
I021/130: 0x3866D7AB9EB3 [WGS84 LAT: 79.314926147 °; LON: −118.659484863 °]
I021/140: 0x188C [GALT: 39275.00 ft]
I021/145: 0x0618 [FL: 390.00 FL]
I021/157: 0x0000 [GEOVR: 0.00 ft/min]
I021/157: 0x0000 [GEOVR: 0.00 ft/min]
I021/210: 0x08 [LTI MDS: 1; UAT: 0; VDL: 0; OTR: 0]
If the decomposition mode is enabled (refer to section 4.6.5.2), then the input data are shown in a
decomposed format. Decomposed format means that the parts, a read downlink telegram is consist-
ing of, are shown in a well readable list. If an input telegram could not be decoded, the reason is given,
if the decomposed mode is enabled. The decomposed mode has the following layout:
IN #<input number>: <raw data>

<subfield name> [<bit position from>−<bit position to>]: <decimal value of subfield>
NOTE: <eventual reason for failure of decoding>
Ed. 10.07 4−71

AS 680/682 ADS−B
Example:
IN #000001: 096 005 26702.961 26702.961 8054.460492031 17 AB00D6 8DAB00D620397075C60820000000 −− −−
MSG PART DL FORMAT [1.BYTE: 01−05]: 17
MSG PART CF/CA [1.BYTE: 06−08]: 5
MSG PART TARGET ADDRESS [2. − 4.BYTE ]: AB00D6 (hex)
MSG PART START 5.BYTE [01−56]: 20 39 70 75 C6 08 20 00 00 00
FORMAT TYPE CODE [01−05]: 4
AIRCRAFT CATEGORY [06−08]: 0
AIRCRAFT IDENTIFICATION [09−56]: NWA51
CHARACTER 1 [09−14]: 28
CHARACTER 2 [15−20]: 7
CHARACTER 3 [21−26]: 23
NOTE: Altitude is invalid or out of range!
NOTE: Allocated new track!
’Screen Output’ can be saved and edited by the user (refer to section 4.6.2.2.2 ).
4.6.5.1.3 RAC I/O Parameter: Pipeline Mode
A checkbox allows to switch the pipeline mode. If the pipeline mode is activated, the RAC−tool works
like the groundstation’s pipeline mode.
Pipeline mode means that telegrams are only sent, if the input is a position or a velocity squitter, i.e.
every other kind of squitter does not generate output.
S In pipeline mode, only the current information of the position or velocity squitter is kept, respec-
tively, and additionally the information of the last identification or status squitter received since the
last output.
S Pipeline mode means that the mandatory field check, refer to 4.6.5.4, is disabled to prevent the
loss of velocity squitter generated output not containing mandatory position information.
S If the pipeline mode is switched off, every telegram generates output telegrams containing all infor-
mation being up to date. The ages of the information, refer to 4.6.5.3, decide which information
is up to date and which information is obsolete.
4−72 Ed. 10.07

ADS−B AS 680/682
4.6.5.2 RAC Notebook Page ’Data Parameter’
The notebook page ’Data Parameter’ (see Fig. 4−101) of the tool ’Replay Raw Data Send Asterix
Data’ is the same as the corresponding notebook page of the tool ’Replay Raw Data Send Raw Data’
(refer to section 4.6.4.2). The only additional option is the check to enable or disable the decomposi-
tion mode. The meaning of the decomposition mode is explained in section 4.6.5.1.2 .
Fig. 4−101 RAC, page ’Data Parameter’ (example)
4.6.5.3 RAC Notebook Page ’Trackstore’
The ’Replay Raw Data Send Asterix Data’ tool needs a trackstore to store the information of target
telegrams. It is necessary to keep e.g. position and velocity information for a target as long as the
corresponding information is considered to be valid or is updated by the input of another telegram.
The following information about trackstore data is configurable in the notebook page ’Trackstore’
(see Fig. 4−102):
S Size of the trackstore: There is a drop down menu to select the size of the trackstore, i.e. the num-
ber of targets, the trackstore must be able to store. The size must always be a prime for tool internal
reasons.
S Maximal age of a target (in seconds) in the trackstore since its last update: If time has passed
this age, then the target is removed from trackstore.
Ed. 10.07 4−73

AS 680/682 ADS−B
Fig. 4−102 RAC, page ’Trackstore’ (example)
The following parameters are only applicable, if the ’check for mandatory ASTERIX CAT 21 items’ in
the notebook page ’CPR Decoding’, refer to section 4.6.5.4, is enabled (see Fig. 4−102):
S Absolute maximal age of the track position in seconds: The position of a target is set to invalid,
if the time passed since the last position update is greater than the value given in this text field.
S Maximal velocity age (in seconds) relative to the time of the last position: If the last update of the
speed is older than the last position update minus the velocity age or more recent than the last
position update plus the velocity age, then the speed data for the respective target are declared
invalid.
S Maximal target status age (in seconds) relative to the time of the last position: If the last update
of target status is older than the last position update minus target status age or more recent than
the last position update plus the target status age, then the target status for the respective target
is declared invalid.
S Maximal operational status age (in seconds) relative to the time of the last position: If the last
update of the operational status is older than the last position update minus maximal operational
status age or more recent than the last position update plus the maximal operational status age,
then the operational status for the respective target is declared invalid.
S Maximal identification age (in seconds) relative to the time of the last position: If the last update
of the identification is older than the last position update minus identification age or more recent
than the last position update plus the identification age, then the identification for the respective
target is declared invalid.
S Absolute maximal Mode 3/A age in seconds: The mode 3/A address of a target is set to invalid,
if the time passed since the last position update is greater than the value given in this text field.
4−74 Ed. 10.07

ADS−B AS 680/682
4.6.5.4 RAC Notebook Page ’CPR Decoding’
The ’Replay Raw Data Send Asterix Data’ tool decodes raw data input. If the downlink telegrams are
extended squitters (DF 17, DF 18 or DF 19) or of downlink format DF5 or DF21, the content of the
telegrams is at least partially decoded. The extended squitters can be position squitters, which are
encoded with the help of the so−called Compact Position Reporting (CPR). The present notebook
page (see Fig. 4−103) is called CPR Decoding, because the prevailing part of the options concern
the CPR decoding. Other options concern validity checks related to the decoded position squitters.
Fig. 4−103 RAC, page ’CPR Decoding’ (example)
The following parameters are provided:

S The locally unique CPR decoding needs a reference position to calculate target positions from po-
sition squitters (airborne or surface). It is possible to choose a Ground Station position or the last
valid target’s position as reference. If the Ground Station is selected as reference location, then
the Groundstation position in latitude / longitude must be entered into the corresponding fields.
S It is possible to enable or disable separately the decoding mode of airborne position or surface
position squitters. The selection of ’Globally unique’ or ’Local’ decoding are applicable for airborne
and surface position squitters.
S Check on mandatory ASTERIX CAT 21 fields: If the mandatory field check is activated, then AS-
TERIX data may only be sent, if the mandatory fields Data Source Identification, Target Address,
Target Report Descriptor, Time of Day, Figure of Merit, and Position are available and valid (refer
to section 4.6.5.3).
Ed. 10.07 4−75

AS 680/682 ADS−B
S Check on AP/PI field: If this check is activated, the AP field (Address/Parity field) or PI field (Parity/
Interrogator identifier) or the extended squitters of downlink format 17, 18 and 19 (if available) are
checked. This field is represented by the last three bytes in the telegram. If the AP or PI field is 0,
then the telegram is correctly transmitted, else the squitter is damaged and will be ignored.
S Check on the coverage range: If the check on the coverage range is activated, it is possible to
enter a distance in Nautical Miles, beyond which no targets are considered. This coverage range
check is only applicable within the boundaries of uniqueness, i.e. within a range of 170 nautical
miles around the Ground Station for airborne positions and 45 Nautical Miles around the Ground
Station for surface positions. Telegrams that fail the check will be ignored. If this check is disabled
and telegrams arrive from beyond the range of 170 NM for airborne position squitters or from be-
yond the range of 45 NM for surface position squitters, then the targets will always be tried to get
located with the respective global decoding mode.
S Check on the distance of two consecutive positions of a target by using the maximal target veloc-
ity in Nautical Miles per Second and the maximal age of the track position in seconds (refer to sec-
tion 4.6.5.3). If this check is activated, it is possible to enter a maximal target velocity in Nautical
Miles per second. In the case that two consecutive positions of a target exceed the maximal dis-
tance limit, got from the product of maximal target velocity and maximal position age, then the ATP
subfield of the target report descriptor is set to 0 for the concerned target. Once set to 0, this ATP
subfield will be overwritten after 10 seconds. The indication ATP equal to ’Non Unique Address’
(=0) indicates that the ICAO address, assigned to the target, is not unique or that the target sends
some faulty telegrams causing deserting plots of the track.
S Check on maximal altitude of a target. If this check is activated, it is possible to enter an altitude
in Flight Level. If the height of target exceeds the maximal altitude, then the corresponding tele-
gram is ignored.
S Check on minimal altitude of a target. If this check is activated, it is possible to enter an altitude
in Flight Level. If the height of a target remains under the minimal altitude, then the corresponding
telegram is ignored.
If some checks fail, then the corresponding notes can be received on ’Screen Output’, if the ’Detailed
telegram decomposition’ mode is activated (refer to section 4.6.5.2).
4−76 Ed. 10.07

ADS−B AS 680/682
4.6.5.5 RAC Notebook Page ’ASTERIX CAT 21’
After decoding of raw data input, the ’Replay Raw Data Send Asterix Data’ tool encodes output data
in the ASTERIX CAT 21 format. There are some ASTERIX CAT21 data fields, which cannot be got from
the raw data information or which shall be manipulated. In addition, data fields being very usable to
the user of the tool, but which are not defined by the ASTERIX CAT 21 standard, can be transmitted.
The following parameters are provided for the ASTERIX CAT 21 encoding on the notebook page AS-
TERIX CAT 21 referring to Fig. 4−104.
Fig. 4−104 RAC, page ’ASTERIX CAT 21’ (example)
S indication of the source identifier, System Area Code (SAC) and System Identification Code (SIC).
The SAC cannot be got from the input. It is a mandatory parameter of the ASTERIX protocol and
identifies the area, where the ASTERIX records are to be assigned to. The SIC is associated with
the Ground Station identification, which can be obtained from the input data. If the SAC or the SIC
is set to –1, then the corresponding information found in the input data are taken in the outgoing
ASTERIX data records, else the user defined SAC or SIC of the corresponding textfield is taken
in the output ASTERIX data records.
S the non−standard data ’Signal Amplitude’ and ’Squawk’ can be transmitted in the ASTERIX data.
These data are either ignored by external interfaces or must be switched off. The signal amplitude
is an indicator of the intensity of the mode S telegrams sent by targets. Squawk is the mode 3/A
address, which is e.g. part of the downlink formats DF5 and DF21.
S the ASTERIX field I021/210 ’Consider Link Technology Indicator’, indicating that the telegrams,
which are received by the Ground Station, are Mode S extended squitters, can be sent or sup-
pressed in the ASTERIX datagrams.
Ed. 10.07 4−77

AS 680/682 ADS−B
S it is possible to mark the data sent by the RAC−tool as simulated. If the check box is enabled, then
the subfield SIM of the field ’Target Report Descriptor’ is set to 1, else to 0.
S it is possible to pass the Mode S address of a field monitor to the tool. A field monitor is an ADS−B
equipment sending periodic signals to survey the operational state of the Ground Station. The tar-
get report descriptor of ASTERIX datagrams generated for a field monitor get settings being differ-
ent to usual targets’ report descriptor. It is possible to use the asterisk ‘*’ as wildcard, i.e. ‘4004*’,
for instance, defines all address starting with ‘4004’ as addresses of field monitors. This wildcard
is only possible as last character, e.g. ‘4004*1’ and ‘*4C1’ do not work.
S it is possible to decide, if the current system UTC time or the time, given in the input file, shall be
used as Time of Day in the ASTERIX protocol. This feature is needed, because some external inter-
faces ignore ASTERIX records, which seem to be obsolete. Hence the time of day given in the input
can be overwritten by the current system UTC time.
4.6.5.5.1 RAC Tool: Help/About Panel
The About panel of the RAC Tool, see Fig. 4−105, called by the selection of ’About’ in the menu ’Help’,
contains an additional text line compared with the general ’About’ panel (see Fig. 4−88).
This additional line shows the version of the currently loaded FOM/PA table, which is used to evaluate
the Position Accuracy in the Figure of Merit field of the ASTERIX data.
This table is used for targets sending reports according the standard DO−260A.
Fig. 4−105 RAC, ’About’ panel (example)
4−78 Ed. 10.07

ADS−B AS 680/682
4.6.6 Record Asterix Data Tool (ARC)
The ’Record Asterix Data’ tool handles the ASTERIX CAT 21 protocol. The ’Record Asterix Data’ tool
receives ASTERIX data via the network and records them in a file or on ’Screen Output’.
4.6.6.1 ARC Notebook Page ’Parameter’

The notebook page ’Parameter’, see Fig. 4−106, is needed to adjust the most important parameters
of this tool.
Fig. 4−106 ARC, page ’Parameter’ (example)
4.6.6.1.1 ARC Parameter: Interface

A mandatory parameter is the address of the interface, to which the tool shall listen. The address con-
sists of the hostname and the port of the socket, where the incoming data are expected. It is possible
to enter the hostname of the interface like it is known to the present host, e.g. ’localhost’, or to enter
the IP−address, e.g. 127.0.0.1. If the incoming data have no ASTERIX format CAT 21, a warning is
prompted to standard output.
It is possible to enable a forwarding of the received data to another interface, e.g. a situation display.
The forwarding option does not restrict the other features of the ’Record Asterix Data’ tool.
4.6.6.1.2 ARC Parameter: Output

The output of the received data can be written on the ’Screen Output’ (see section 4.6.2.4.2 ) as well
as into a file. The selection of the required output destination is done with checkboxes. If both check-
boxes are disabled, then the received data is logged to standard output on that terminal, where the
tool is started. The logging to standard output can be used to pipe the received data to standard input
of other tools. This works in the same way as for the ’Raw Data Record’ tool (refer to section 4.6.3.1).
It is possible to record the incoming data in binary format. The other possibility is to decode the incom-
ing ASTERIX stream and log it as ASCII text into a file or on ’Screen Output’.
Ed. 10.07 4−79

AS 680/682 ADS−B
4.6.6.1.3 ARC Parameter: Logging Format/Verbose Mode

The following logging format is available for logging on ’Screen Output’:
S If the input shall be recorded as byte stream, then the logging on ’Screen Output’ is represented
in hexadecimal representation with 16 bytes per line, if no verbose mode is required.
Example:
15 00 22 FB A3 48 FF 07 00 20 6F AF 5B 23 9C B1
05 F1 83 A4 AA 47 00 04 08 01 69 00 00 04 FC 29
55 00
If verbose mode is required, the screen output is shown in the same way as the verbose logging
format of ASCII format recording.
S If the incoming ASTERIX stream shall be output as ASCII text, a decoding of the input is necessary.
The logging to the file is done in a proprietary format for the replay and record tools. Refer to section
4.6.5.1 for a detailed description of the ASTERIX file logging format and the ’Screen Output’ ver-
bose logging format. Functionality and meaning of the remaining options of this notebook page
can be found in the referred sections.
4.6.6.2 ARC Notebook Page ’Filter’
The notebook page ’Filter’, refer to Fig. 4−107, contains the possibility to restrict and steer the data
to be recorded. Refer to the corresponding items of section 4.6.3.2 for the description of the
groundstation and mode S address filter.
The radio buttons ASTERIX CAT 21 version allow to select, if edition 0.20 or edition 0.23 of ASTERIX
CAT 21 shall be recorded.
NOTE: If the selected version is not consistent to data received, it can happen that data will be
missing or will be confused. There is no possibility to differentiate between edition 0.20
and edition 0.23 due to incoming data.
Fig. 4−107 ARC, page ’Filter’ (example)
4−80 Ed. 10.07

ADS−B AS 680/682
4.6.7 Replay Asterix Data Tool (ARP)
The ’Replay Asterix Data’ too reads ASTERIX data from a file or from standard input and sends these
data in ASTERIX CAT 21 format to a user defined network interface.
4.6.7.1 ARP Notebook Page ’I/O Parameter’
Fig. 4−108 shows the first page with configuration parameters in the ’Replay Asterix Data’ tool.
Fig. 4−108 ARP, page ’I/O Parameter’ (example)
4.6.7.1.1 ARP I/O Parameter: Input
The input of the ’Replay Asterix Data’ tool can be either the proprietary ASCII file logging format or
the not decoded pure binary input stream being recorded in the way sent over network (refer to 4.6.6.1
’Output’). If input is a binary stream, then the single step ’Previous’ replay is not possible, because
reading the previous record is not possible due to missing length knowledge.
The input source may either come from standard input or from a file.
S If standard input is selected, then the standard output of some other tool must be piped to this tool
(refer to section 4.6.3.1), else the option ’standard input’ does not work.
S If selecting the radio button ’file’, it is possible to choose an input file by pressing the button
’Choose’, which opens a file selection dialog.
S In addition, it is possible to replay one single hard coded ASTERIX record for test purposes.
NOTE: It is not possible to enter the input file name directly into the textfield. The reason is found
in the explanation of section 4.6.4.2.2 .
Ed. 10.07 4−81

AS 680/682 ADS−B
If the source is a file, the tool evaluates from the first line of the input file, which ASTERIX category
is required (refer to section 4.6.5.1.1 ). Only Asterix Cat 21 is currently allowed.
The ’Replay Asterix Data’ tool recognizes input data as valid ASTERIX CAT 21 and pops up a message
box, if the input is encountered to be not valid.
4.6.7.1.2 ARP I/O Parameter: Interface
A mandatory parameter is the address of the interface, where data shall be sent to. The address con-
sists of the hostname and the port of the socket, where the data have to be output. The output address
cannot be changed from the toll’s user interface as transmitting replayed data into a live system is
potentially dangerous. Instead, the output address can be changed within the tool’s configuration file
(access restrictions apply).
If the source is a file, the tool evaluates from the first line of the input file, which ASTERIX category
is required (refer to section 4.6.5.1). Only Asterix CAT 21 is allowed currently.
Binary data replay is not affected by any category aspects, because binary data contents are not eval-
uated.
4.6.7.1.3 ARP I/O Parameter: Logging
tains the maximum number of lines that the ’Screen Output’ buffer shall contain.
Logging of data to ’Screen Output’ is possible in the layout of the file logging format or in a verbose
mode. The layout of the file logging format is described in detail in section 4.6.5.1.
The layout of the verbose mode is the same as the one introduced for ASTERIX logging in section
4.6.5.1, but no counter of input and output records are available.
Binary input log has always the layout described in section 4.6.6.1.3 .
4−82 Ed. 10.07

ADS−B AS 680/682
4.6.7.2 ARP Notebook Page ’Data Parameter’
The notebook page ’Data Parameter’, see Fig. 4−109, provides packing, time scheduling and filter
options.
Fig. 4−109 ARP, Data Parameter (example)
S It is possible to pack several records of the input into one ASTERIX CAT 21 data block. If packing
is disabled, the data will be replayed as found in the input, else as many data records will be packed
into one ASTERIX data block as selected in the selection box. When the end of an input file is
reached, the remaining records are sent in one block, even if this data block is smaller than the
required number.
S The option ’Multiply replay time by the factor’ is explained in section 4.6.4.2.1 . This is the only fea-
ture of this page, which is applicable for binary replay, too.
In case of binary replay, the replay factor indicates the periods in seconds, when the next binary
decoded ASTERIX data block is to be sent. The differentiation of binary ASTERIX data blocks is
possible by evaluation of their length fields. The evaluation of the length field is needed to avoid
an uncontrolled flush of the input to network.
S ’Time Scheduling’ is explained in section 4.6.4.2.2 .
S The second enumeration item in section 4.6.4.2.3 explains the mode S filter functionality.
S It is possible to mark the data sent by the ARP−tool as simulated. If the check box is enabled, then
the subfield SIM of the field ’Target Report Descriptor’ is set to 1, else to 0.
S The radio buttons ASTERIX CAT 21 version allow to select the edition, which shall be replayed. It
is possible to replay edition 0.20 or edition 0.23 data. It is very important that the selected version
is consistent with the data to be replayed, because otherwise data can go lost or get confused.
There is no possibility by the tool to differentiate between ed. 0.20 and 0.23 due to information of
the file to be replayed.
S The choice of the time base feature is explained in section 4.6.5.5.
Ed. 10.07 4−83

AS 680/682 ADS−B
4−84 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Miscellaneous Tools
4.7 MISCELLANEOUS TOOLS
4.7.1 General
The set of miscellaneous tools is available for the user in the desktop panel at the bottom of the LCMS
screen and RCMS screen 0. Clicking on the icon opens the ’Misc. Tools’ menu (see Fig. 4−110).
Fig. 4−110 RCMS desktop panel with the ’Misc. Tools’ menu (example)
Fig. 4−111 LCMS desktop panel with the ’Misc. Tools’ menu (example)
4.7.2 Burning application

After selection of ’Misc. Tools’ submenu ’Burning application’ on RCMS screen 0 (see Fig. 4−110),
resp. on LCMS screen (see Fig. 4−111), the application is started to store ADS−B data on CD or DVD.
The application checks the drive (CD or DVD inside?), then the user is able to enter the path of the
data source.
NOTE: The data amount is limited by the used storage medium (CD: 700 MB, DVD: 4.2 GB).
4.7.3 Nedit
After selection of ’Misc. Tools’ submenu ’Nedit’ on RCMS screen 0 (see Fig. 4−110), or on LCMS
screen (see Fig. 4−111), the editor is started to read/write ADS−B data files. The user is able to enter
the path and the file name (e.g. *.raw, *.org, *.log). Some rules are defined to highlight certain data
within the file for better reading.
4.7.4 Minicom
After selection of ’Misc. Tools’ submenu ’Minicom’ on LCMS screen (see Fig. 4−111), a Linux Termi-
nal application is started to get direct access to the Ground Station for administration purposes. The
Terminal application is connected to the GS via serial line.
Ed. 10.07 4−85

AS 680/682 ADS−B
Miscellaneous Tools Description, Operation and Maintenance
4.7.5 Calculator
After selection of ’Misc. Tools’ submenu ’Calculator’ on RCMS screen 0 (see Fig. 4−110), or on LCMS
screen (see Fig. 4−111), a calculator application is started.
4.7.6 Capture Screen
After selection of ’Misc. Tools’ submenu ’Capture Screen’ (see Figs. 4−110 and 4−111), one (LCMS)
or two (RCMS) screen capture tools are applicable to take a screenshot of the screen contents.
The LCMS has only one laptop screen, therefore only one ’Capture Screen’ tool is provided within
’Misc. Tools’ menu of the LCMS desktop panel.
The RCMS has two screens, the screen 0 (left screen, used for the TSC application) and the screen
1 (right screen, reserved for the MTSC application), therefore the tools ’Capture Screen0’ and ’Cap-
ture Screen1’ are provided within ’Misc. Tools’ menu of the RCMS desktop panel (see Fig. 4−110).
To take a screenshot (e.g. of RCMS screen 1) the user has to perform the following steps:
− double left mouse click on ’Misc. Tools’ submenu ’Capture Screen1’ on RCMS screen 0;
the special mouse pointer (cross sign) appears on RCMS screen 1.
− single left mouse click on screen 1;
the screenshot of screen 1 (’MTSC main window’) appears on RCMS screen 0.
− single right mouse click within screenshot on screen 0;
a menu appears.
− single left mouse click on submenu ’Save...’;
the window ’Browse and Select a File’ appears on screen 0.
− click on button ’Save’; select/edit file name and preferably the JPEG quality ’100’;
confirm by clicking on button ’Save.
− single right mouse click within screenshot on screen 0;
a menu appears.
− single left mouse click on submenu ’Quit’;
the screenshot on screen 0 disappears.
4.7.7 Image Viewer
After selection of ’Misc. Tools’ submenu ’Image Viewer’ on RCMS screen 0 (see Fig. 4−110), or on
LCMS screen (see Fig. 4−111), the application is started to view an image file (e.g. *.jpg, *.tif). The
user is able to enter the path and the file name of the image file. This tool can be used to view for exam-
ple a screenshot.
4.7.8 PDF Viewer
After selection of ’Misc. Tools’ submenu ’PDF Viewer’ on RCMS screen 0 (see Fig. 4−110), or on
LCMS screen (see Fig. 4−111), the application ’xpdf’ is started to view a *.pdf file. The user is able
to enter the path and the file name of the image file. This tool can be used to read for example tool
manuals available in pdf−format.
4−86 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Supervisor Operation
CHAPTER 5
SUPERVISOR OPERATION
5.1 GENERAL DESCRIPTION
Chapter 5 and chapter 6 describe the operation of the TSC (running on the RCMS screen 0 and on
the LCMS screen). The TSC can be started in different user modes. In this chapter the TSC operating
in supervisor mode is explained, i.e. the full functionality of the TSC is described here.
In chapter 6 the functionality available for the Monitor User is described, which is a subset of the func-
tions described within this chapter 5.
NOTE: Another application is the MTSC running mainly on the RCMS screen 1. The MTSC func-
tionality available for the Supervisor on the RCMS is described in section 4.3.3.
The following Fig. 5−1 depicts the basic structure of the TSC Graphical User Interface (GUI). It con-
sists of the components titlebar, menubar, notebook and statusbar.
Titlebar
Menubar
Notebook
Statusbar
Fig. 5−1 Structure of the TSC GUI (example)
Clicking with the left mouse button on a tab of the notebook switches to the corresponding page.
The titlebar shows the character string "Thales Stuttgart – AS680 Technical System Control".
The menubar is described in section 5.3, the notebook in section 5.4 and the statusbar in section
5.2.
Ed. 10.07 5−1

AS 680/682 ADS−B
Supervisor Operation Description, Operation and Maintenance
5.2 STATUSBAR
The Statusbar, see Fig. 5−2 given as an example, gives current information about the TSC and the
Ground Station status.
Fig. 5−2 TSC Statusbar (example)
The first field shows the Ground Station name with the current status color as background.
The second field shows the latest Log−Message being also found in the log message window, refer-
ring to section 5.4.16.
The third and fourth field shows the current date and time based on the system time of the RCMS or
LCMS, where the current TSC is running.
5−2 Ed. 10.07

ADS−B AS 680/682
5.3 MENUBAR
The menubar (refer to Fig. 5−1) contains the menus ’File’, ’Groundstation’, ’Settings’, ’Refresh’,
’Page’ and ’About’.
5.3.1 Menu ’File’
The menu ’File’ contains two menu items with the following meaning:
S Minimize Window: Minimizes the main window.

S Exit: Saves the ’start−up settings’ for the next TSC session and exits the
TSC application.
The main window of the TSC cannot be minimized in the usual way, i.e. by pressing the minimize but-
ton which is mostly located at one of the upper corners of the window (depending on the window man-
ager actually used). Instead, the application can only be set to a similar state by choosing the ’Mini-
mize Window’ entry of the ’File’ menu. This command will shrink the window size to a certain minimum
while still showing the color coded operational status and the name of the Ground Station, as de-
picted in Fig. 5−3. The colors and codes of the operational status are described in section 5.4.2.2.
Fig. 5−3 TSC, Minimized View (example)
The Ground Station name is printed on a button that can be used to restore the main window.
The minimized view of the TSC application is particularly useful, if more than one Ground Station is
monitored at the same time. In this case, several instances of the TSC can run simultaneously each
supervising a different Ground Station. The minimized views of all the Ground Stations can be ar-
ranged on the screen so that an overview of the complete Ground Station network is immediately vis-
ible. The advantage of this decentralized view – unlike an integrated display of all Ground Stations’
status – is the complete independence of the TSC instances.
If the application is closed during the minimized state, size and position of the minimized window are
stored within the setting file:
[home]/.tsc/settings/ settings_startup_tsc.conf
When the TSC is started again, it will come up as minimized window at the previous size and position.
Ed. 10.07 5−3

AS 680/682 ADS−B
5.3.2 Menu ’Groundstation’

This menu is used to switch between the different Ground Stations.
5.3.3 Menu ’Settings’
This menu is used to configure the user preferences of the TSC. The configuration parameters are
found in the home directory of the current user under
[home]/.tsc/settings/settings_tsc.conf or
[home]/.tsc/settings/settings_startup_tsc.conf.
NOTE: These files should not be edited manually.
The menu items are:

S Beep on error: : Enables/disables the error beep.
S Logging... : Opens a dialog, see Fig. 5−4, to configure logging settings.
S New Log File : Forces the creation of a new file.
S Load Settings : Loads the settings, which are saved in the settings_tsc.conf file.
S Save Settings : Saves the current settings to the file settings_tsc.conf.
NOTE: The menu item ’Beep on Error’ is hidden by default and the option itself is enabled. To
make this menu item visible, change the corresponding user role configuration file (refer
to section 3.5.1) and set the popUpAndBeep(enableMenu) parameter ’0’ to ’1’.
Example:
Load TSC configuration file into editor with
nedit /usr/local/tsc/.tsc−config/supervisor_user.config
Change parameter: popUpAndBeep(enableMenu)0 to 1
Save and quit the editor. Start the TSC again and select the menu settings. Disable Beep.
Save your settings.
The dialog appearing after selecting the menu item ’Logging ...’ has the following layout (see Fig.
5−4):
The first field shows the name of the log file currently in use. The name is automatically generated and
cannot be changed.
The next two fields define the conditions under which the current log file is closed and a new log file
is generated. If the corresponding option buttons are enabled, a new file is allocated, if
S the maximum size of the log file in KB or
S the maximum age of the log file in minutes
is reached.
If none of the option buttons is enabled, the log file will grow until it runs out of available disk space.
If both option buttons are enabled, the first condition met triggers the creation of a new log file.
The ’Logfile Lifetime’ parameter defines how long the log file is allowed to exist before deletion. The
TSC installs a cron job, that runs every 24 hours. It deletes all logfiles whose write access timestamp
is older than n days ago (n = logfile lifetime parameter). The cron job also starts, if no instance of the
TSC is running. Logfiles currently in use by a TSC are not deleted.
5−4 Ed. 10.07

ADS−B AS 680/682
The last field in this dialog shows the directory where log files are kept. The default logging directory
is [home]/.tsc/logging where [home] is the current user’s home directory. If the environment
variable $HOME is not set correctly or the directory does not exist, logging is disabled and an error
message is printed.
If the logging directory is changed, a new log file will be created after the change is validated by press-
ing the OK button.
The parameters ’Max. Logfile Size’, ’Max. Logfile Age’, ’Logfile Lifetime’ and ’Logging Directory’ are
saved in the file settings_startup_tsc.conf .
Fig. 5−4 Logging Settings Window (example)
5.3.4 Menu ’Refresh’

The Refresh menu items are used to refresh the notebook pages of the TSC user interface:
S Refresh All Pages : Updates each notebook page by requesting all parameters from
the Ground Station
S Refresh Current Page : Updates the current page by requesting the corresponding
parameters from the Ground Station
5.3.5 Menu ’Page’

This menu is used to bring the corresponding tabulator page to foreground. It can be used alterna-
tively to page selection with the help of the notebook tabs. The menu items are:
S Overview
S Bite
S Telegram Filter
S Groundstation
S Network
S Output
S Telegram Check
S Process
Ed. 10.07 5−5

AS 680/682 ADS−B
S ADSB
S ADSB Filter
S Site Monitor
S Software
S GPS
S UPS
S Logging
All notebook pages are described in section 5.4.
5.3.6 Menu ’About’
By selection of the only menu item ’About TSC’ of this menu ’About’ an information panel pops up.
The information panel, see Fig. 5−5, contains information about the current name and version of the
TSC software and the contact address of the responsible person.
Fig. 5−5 About Panel (example)
5−6 Ed. 10.07

ADS−B AS 680/682
5.4 NOTEBOOK
5.4.1 Overview
The TSC is organized in separate notebook pages that can be accessed by the tabs at the lower part
of the window. Each page represents a set of parameters that are described in more detail in the follo-
wing sections.
Each of the pages has a ’Refresh’ button at the lower right corner of the page. Pressing this button
requests the Ground Station to refresh all parameters or status values that are currently displayed on
the page.
NOTE: An automatic refresh is performed during start−up and when switching between the
Ground Stations.
Pressing the ‘Refresh’ button, the TSC requests each parameter of the current page subsequently
from the Ground Station until all values are received. If all requests succeed, the following message
is displayed in the status bar:
"All Values successfully received for page XXX!"
The TSC waits up to a certain timeout for an answer. The failure of one of these update requests
causes the skipping of the following ones to avoid blocking of the TSC.
Example: Consider a timeout of 5 seconds per parameter on a page displaying 25 parameters and
consider failure of single requests. Clicking the refresh button, the TSC could be blocked more than
1 minute, if the TSC waits 5 seconds for every request of the 25 parameters. Thus the sending of the
remaining requests will be stopped with the failure of a first request . The following message is logged
to the status bar, to the log window and to the log file:
"One of the Values couldn’t be received! See earlier Log−Messages for further details!"
Previous log messages show information about the failed request.
Parameter fields are used for displaying and changing values. There are two types of parameter
fields: text fields and option fields.
In locked mode (by default), the values of the parameter fields are shown, but cannot be changed.
The parameter fields are used for data types like integer, floating point and strings. The option field
is used for selection of enumeration values (e.g. on/off).
Pressing the ’Get’ button, the current setting or the corresponding value retrieved from the Ground
Station is displayed. Pushing the ’Edit’ button the parameter fields switch to edit mode.
In edit mode, i.e. after having selected ’Edit’, the color and the text of the buttons changes. The value
of the text field or the option menu can be changed. By pressing the ’Set’ button or hitting the return
key, a plausibility and range check is performed. If this test fails, the parameter setting is not accepted
and a message window, pops up on top of the TSC informing the user about the reason for the rejec-
tion and about the available choices or parameter ranges. After closing the message window (selec-
tion of ’Set’) the parameter field remains in locked mode and the button ’Set’ changes to ’Get’.
Ed. 10.07 5−7

AS 680/682 ADS−B
If the plausibility check succeeds, a change request is sent to the Ground Station. If that request
succeeds, the parameter field switches back to the locked mode. If not, the parameter field remains
in edit mode and an error message is displayed in the statusbar, in the log window and in the log file.
To unchange a value just press the ’Cancel’ button. The parameter field switches back to the locked
mode.
NOTE: Not all parameter fields have an ’Edit’ button. The ’Edit’ button is hidden for some parame-
ters, if no write access is granted to the parameter or to the current user role (see Monitor
user, chapter 6).
5−8 Ed. 10.07

ADS−B AS 680/682
5.4.2 Page ’Overview’
This page shows basic information about the TSC, the Ground Station, the current user and his role.
These data are read from the configuration files.
Fig. 5−6 Notebook Page ’Overview’ (example)
5.4.2.1 Ground Station and User Information

The name and IP−Address of the Ground Station is taken from the configuration file that the TSC cur-
rently uses. The username is the login name of the current user and the user role is extracted from
the role_user.conf file the current user is linked to.
5.4.2.2 Ground Station Status and Monitoring Information

The color of the disc together with the text field next to it indicates the current state of the Ground
Station. The ’BITE Status’ Parameter of the GS has to be requested via SNMP to obtain the GS status
’GS−Status’. This is done periodically. The ’GS Status’ can get one of the following states:
Color Status Description
Yellow WARNING The Ground Station state changes to WARNING (e.g. door is open, temperature
threshold exceeded) or one of the NON−critical tests fails
Red FAULT The Ground Station (GS) state changes to FAULT, if one of the critical tests fails.
The critical resources include the operational state of the GS. The TSC indicates
the FAULT state, if the Ground Station doesn’t answer to a ’BITE Status’ request.
Green OPERATIONAL Everything is ok.
Blue MAINTENANCE Maintenance Mode
The text below the circle indicates, whether polling of the ’BITE Status’ is currently enabled and shows
the polling rate.
Ed. 10.07 5−9

AS 680/682 ADS−B
5.4.3 Page ’BITE’
The ’BITE’ page, see Fig. 5−7, is the most important page of the TSC. It provides a detailed view of
individual BITE test results. It allows to select the BITE tests currently running and allows to check,
if their result values are periodically retrieved. Some of these tests require configuration parameters,
e.g. the Mode S address used for the test signal.
Fig. 5−7 Page BITE (example)

BITE tests cover
S hardware components
S status parameter thresholds
S software thread activities
S signals
The individual BITE tests are discussed in the next section.
The tests are grouped according to:

S ’Critical’ tests on Ground Station operations
S tests on data integrity (’Warning’)
S ’Maintenance’
A failed test can thus result in a critical failure or only in a warning.
5−10 Ed. 10.07

ADS−B AS 680/682
The test results are indicated on the right side of the tests in specific colors, which are:
S GREEN: test result is ok.
S RED: failure of a critical test, i.e. a ’failure’
S YELLOW: failure of a non critical test, i.e. a ’warning’
S BLUE: maintenance mode is active
S GREY: test is not running.
NOTE: Not all tests and resources on the ’BITE’ page must necessarily be installed as hardware
components in the Ground Station. Displaying the color of the Ground Station status, the
RED color has the highest priority, followed by YELLOW, BLUE and GREEN color. That
means, if e.g. a failure and a warning happens at the same time, the failure color RED over-
rules the warning color YELLOW and the Ground Station status is displayed in RED.
5.4.3.1 BITE Tests
In this section, the different BITE tests are described. There are critical tests, whose states are found
in the column ’Critical:’ and non−critical tests, whose states are found in the column ’Warning:’. Addi-
tionally, there is one maintenance test found in the column ’Maintenance:’.
Critical tests:
S MAIN THREAD
This test monitors the periodic heartbeat signal of the application main thread.
S BASE THREAD
This test monitors the periodic heartbeat signal of the base thread.
S ADSB THREAD
This test monitors the periodic heartbeat signal of the ADS−B thread.
S BITE THREAD
This test monitors the periodic heartbeat signal of the BITE thread.
S LOOPBACK TELEGRAM
This test monitors the successful reception of a Mode S signal that is generated once per second
on the SPB and looped back directly into its analogue input. The signal remains on video level,
i.e. no RF modulation is involved. Hence the test covers only the SPB and not the RXU.
S GPS
This test monitors the status of the Time Reference System (TRS). The TRS consists of a GPS time
receiver module in the AS 680 VME bus. If GPS is enabled and the Ground Station position re-
ceived by the GPS is outside the given range around the reference Ground Station position given
by the TSC, the test results in an error.
S RF−PATH
This test checks, if any signals of a Site Monitor are received. This test is used for detection of hard-
ware failures.
S SITE MONITOR BITE
This test monitors the successful reception of BITE states, emitted by the own Site Monitor.
S SITE MONITOR TELEGRAM (own)
Checks, if Mode S telegrams from the own Site Monitor are received.
S VOLTAGE
The secondary voltage circuit is checked.
Ed. 10.07 5−11

AS 680/682 ADS−B
Non−Critical tests:
S SITE MONITOR TELEGRAM (other)

Checks, if mode S telegrams from the peer Ground Station’s Site Monitor are received.
S PARTNER BITE SIGNAL
In a dual redundant channel configuration this test monitors the overall BITE status of the backup
channel, which is needed for automatic switchover in case of failure of the active channel.
S FAN STATUS
This test generates a warning, if the SPU fan does not work properly.
S TEMPERATURE
This test signals a warning, if the temperature exceeds the temperature threshold. The threshold
level and the temperature monitoring interval can be configured on the page ’Groundstation’. The
temperature sensor is located on the SPB.
S TRACKSTORE ADS−B
This test signals a warning, if the size of the SPC trackstore exceeds a given threshold or if the
system detects collisions during address allocation in the trackstore.
S ASTERIX DATA RATE
This test signals a warning, if the Asterix data rate exceeds the corresponding threshold.
S NVRAM BATTERY
NVRAM battery test − indicates a warning if battery has low voltage (for replacing battery see sec-
tion 7.1.8).
S UPS
Uninterruptable Power Supply
S DOOR
− door status − indicates a warning if the door (if available) is open.
S TIME SYNC
− time synchronization status − indicates a warning if ntp daemon is not running.
S MAINTENANCE
Shows, if the maintenance mode is set. If set, the color of corresponding indicator switches to blue.
5.4.3.2 Bite Status (Read Only)
The ’Bite Status’ value describes the state of the resource. The ’Bite Status’ is used in the same way
as the ’Bite Mask’ value. The allocation of bits to the resources is the same, but the meaning of the
value is different. A BITE Status bit set to ‘1’ indicates that the corresponding test failed.
Non critical resources Critical resources
Example:
0x00200000 HEX = [0] 0 | 00 0000 0010 0000 | 0000 0000 0000 0000 binary notation
The sixth (from right to left) of the warning bits is set to 1 (Non critical tests). According to Fig. 5−7,
this test checks the Asterix Data Rate. The corresponding indicator has to switch to yellow conse-
quently.
The BITE Status value is used to determine the overall operational status of the Ground Station being
displayed on the Overview Page (see section 5.4.2). The following table shows the mapping between
the ’BITE Status’ value and the ’GS−Status’:
5−12 Ed. 10.07

ADS−B AS 680/682
BITE Status Value Indicator Color GS−Status
0xFFFFFFFF RED FAULT
0x00000000 GREEN OPERATIONAL
> 0x00000000 RED, YELLOW or BLUE FAULT, WARNING or MAINTENANCE
Table: BITE Status Value and Ground Station Status
The indicators of all resources switch to gray, if the BITE Status has the value 0xFFFFFFFF. This can
happen, if the ’BITE Status’ is requested too often (BITE Thread is busy), at boot time or for test pur-
poses, if the BITE test is disabled. The result is the Ground Station status ’Fault’.
There are three ways to request the BITE Status value:

S pressing the ’Get’ button next to the ’BITE Status’ field.
S pressing the ’Refresh’ button at the bottom of the page.
S enabling the polling mechanism (’Polling’ button) with the option button beneath the ’BITE Status’
field.
The polling mechanism arranges the TSC for periodic BITE status requests. The polling interval in
seconds can be changed in the entry field below the selection button (’Polling Rate’). The interval can
be changed either by pressing the up or down buttons or by typing the corresponding value into the
text field. The ’Set’ button has to be clicked to activate the change.
5.4.3.3 Bite Mask

The BITE Mask determines which of the BITE tests shall run.
Example: The BITE Mask value be set to 0x407F03EF. The prefix ’0x’ indicates, that the value is shown
in hexadecimal notation. Each bit of this value represents one resource and the value of the bits deter-
mine, whether the resource is monitored.
Non critical resources Critical resources
0x403C020F HEX = [0] 1 | 00 0000 0011 1100 | 0000 0010 0000 1111 binary notation
The lower 16 bits (from right to left) represent the ’critical resources’. Only these ’critical tests’, whose
corresponding bit is set to ‘1’, are performed. In this example, only the enabled 9 ’critical tests’ run
and yield an operational status. The remaining tests are disabled. Actually there are only 10 ’critical
resources’, so only 10 of the lower 16 bits are used. The remaining 6 bits are reserved.
The bits 17 to 30 represent the ’non critical tests’ depicted in the same way in the warning column
of the BITE page. Actually there are only 7 ’non critical tests’, so only 7 bits are used. The remaining
7 bits are reserved.
Bit 31 represents the maintenance test.
Press the ’Edit’ button next to the corresponding field to change the bite mask. The indicators of the
tests change to toggle buttons . Each toggle button represents one bit in the BITE mask. A toggled
button sets the corresponding bit to ‘1’ or ‘0’. It is possible to change the BITE mask by pressing the
option buttons of the corresponding tests or by entering the BITE mask directly as hexadecimal string
into the textfield BITE Mask.
After pressing the ’Set’ button belonging to the respective BITE Mask, the option button of the test
changes back to an indicator again.
Updates on the option buttons changes the text field BITE Mask accordingly.
Ed. 10.07 5−13

AS 680/682 ADS−B
5.4.3.4 Loop Back Telegram Address

This parameter defines the Mode S address of the internal loop back telegram used by the Ground
Station signal processing board (SPB) for test purposes.
5.4.3.5 Maintenance
Every write access to the online running Ground Station is a maintenance task. The supervisor should
activate the maintenance mode. This indicator notices the monitor users about the maintenance,
which will be performed.
In the ’Information’ text field, the supervisor in maintenance mode can prompt a message to the moni-
tor users. If the ’Information’ field is empty, a default string is written to the ’Information’ text field, if
monitor mode is switched on. Already present text in the field will not be overridden.
5−14 Ed. 10.07

ADS−B AS 680/682
5.4.4 Page ’Telegram Filter’
The Ground Station AS 680 is able to filter Mode S downlink telegrams according to their format in
order to reduce SPC CPU load. This feature can be useful to eliminate undesired signals e.g. replies
to TCAS interrogations, short squitters or replies to radar interrogations.
The filter settings are defined on the ’Telegram Filter’ page (see Fig. 5−8) by selecting or deselecting
the desired Mode S formats. Deselected formats are not processed by the Ground Station. The follo-
wing figure shows the page with a sample downlink mask. Each selected format is indicated by a
green button (‘On’) while deselected formats are shown by a red button (‘Off’).
Fig. 5−8 Page ’Telegram Filter’ (example)
The ’Refresh’ button requests the current downlink mask settings from the Ground Station and up-
dates the page accordingly.
All settings can be changed in supervisor mode by clicking on the red or green indicators to the left
of each format description. Before changes take effect, they have to be applied to the Ground Station
using the corresponding ’Set Values’ button.
Ed. 10.07 5−15

AS 680/682 ADS−B
The buttons ’Switch all on’ and ’Switch all off’ can be used to switch all downlink formats on or off,
respectively. Using the ’Save as Default’ button, the current settings can be made default settings.
Using the ’Show Default’ button, the default settings are loaded.
The default downlink mask setting will be temporarily stored as long as the TSC is not restarted. To
make the default downlink mask persistent, the ’Save Settings’ menu entry in the ’Settings’ menu (see
section 5.3.3) has to be selected. This will save the current configuration settings, including the default
mask, to the [home]/.tsc/settings/settings_tsc.conf file.
NOTE:
S Replies to TCAS interrogations (DF−0) represent the majority of the load within the SSR downlink
channel. Usually, DF−0 are filtered out by the AS 680 SPB hardware in order to minimise the pro-
cessing load for the SPC.
S DF−24 detection is based on the Mode S data block’s two most significant bits only (all other for-
mats are five bit data fields), so that it is quite likely to detect erroneous signals in DF−24.
5−16 Ed. 10.07

ADS−B AS 680/682
5.4.5 Page ’Groundstation’
This page, see Fig. 5−9, presents basic information about the Ground Station’s operational mode.
Fig. 5−9 Page ’Groundstation’ (example)
5.4.5.1 Ground Station Identification
The name of the Ground Station or the System Area Code (SAC) and System Identification Code (SIC)
identify a Ground Station. SIC and SAC identify a system, uniquely worldwide. They are defined by
Eurocontrol in the Asterix standard documents.
5.4.5.2 Time Synchronization

It is possible to enable the ’GPS ’ module to be able to synchronise the Ground Station’s internal clock
based on GPS. It is possible to synchronise the Ground Station’s system time based on NTP or based
on the GPS. The Ground Station’s clock is not synchronised, if the option ’none’ is selected. Chang-
ing the base of the time synchronisation, a confirmation panel pops up telling that the application must
manually be restarted.
Ed. 10.07 5−17

AS 680/682 ADS−B
5.4.5.3 NTP Server Configuration

It is possible to give the IP address of the NTP server, if the system time of the Ground Station shall
be synchronised via NTP.
5.4.5.4 Temperature
Reading of the temperature inside the Ground Station can be requested periodically. The procedure
to enable/disable the polling and to change the polling rate is the same as for the BITE status polling
parameter.
The temperature progress is shown in a diagram together with the temperature warning threshold as
dashed line. Pointing with the mouse into the diagram shows the temperature recorded at the indi-
cated position as a tool tip.
The threshold defines the temperature level in degrees of Celsius that must not be transgressed. If
this threshold is reached, the status of the Ground Station changes to WARNING, provided that the
temperature BITE mechanism is enabled and the ’BITE Status’ is retrieved, e.g. by polling.
Note that the threshold check is part of the BITE tests and always performed, if enabled, no matter,
whether temperature polling is enabled. Polling of temperature is only used for the visualization of the
temperature progress.
5−18 Ed. 10.07

ADS−B AS 680/682
5.4.6 Page ’Network’
This page, see Fig. 5−10, holds all network parameters of the Ground Station.
Fig. 5−10 Page ’Network’ (example)
5.4.6.1 Raw Data Stream

A destination, consisting of IP address and port, must be given on this page, if raw data output is en-
abled. It is possible to give an interval in seconds, when raw data shall be sent.
5.4.6.2 Main Network Configuration

The IP address of the Ground Station is needed by the TSC to communicate with the Ground Station.
The net mask used for sub network addressing and the default gateway address are mandatory net-
work configuration parameters.
5.4.6.3 Auxiliary Network Configuration

It is possible to configure an auxiliary network on a second Ethernet card, which can be used instead
of the main network. This auxiliary network is configured with a Ground Station’s IP address and a
net mask.
5.4.6.4 Main and Auxiliary Asterix Data Stream

A destination, consisting of IP address and port, must be given, if Asterix CAT 21 output is required.
’Auxiliary Asterix Data Stream’ is an alternative destination address, where Asterix data shall be sent
to. This parameters need not be present.
Ed. 10.07 5−19

AS 680/682 ADS−B
5.4.7 Page ’Output’
This page, see Fig. 5−11, gives the possibility to configure the data being sent by the Ground Station.
Fig. 5−11 Page ’Output’ (example)
5.4.7.1 Asterix Fields
It is possible to send the Asterix output as stream to the main or to the auxiliary Asterix address.
The Link Technology flag in the Asterix Standard Fields indicates that mode S telegrams are sent. It
is possible to disable the sending of this information, if the receiver don’t want or cannot get it.
Some non−standard, but user defined Asterix CAT 21 fields are the mode 3A code and the signal
amplitude.
S The mode 3 A code, also called squawk is information contained in squitters of downlink format
5 and 21.
S The signal amplitude is an indicator of the quality of the received telegrams. The higher the signal
amplitude, the better the reception of data.
5−20 Ed. 10.07

ADS−B AS 680/682
5.4.7.2 Raw Data Optional Items
Raw data are the data contained in the telegram received from targets. Unlike the Asterix Standard
Fields, raw data is not decoded. It is possible to switch off the sending of the raw data.
Optional values that can be sent over the raw data interface are:
S the time of day (TOD), based on the system time of the Ground Station, when the respective tele-
gram has been received.
S the time of arrival (TOA), based on the Ground Station’s internal clock, when the respective tele-
gram arrived.
S the enabling of ’loop back’ telegrams (HW generated telegram) adds the loop back telegrams to
the output stream. These loop back telegrams are used for test purposes.
S the confidence bits, indicating the number of bad bits in the telegram. It is an indicator of the quality
of the telegram data
S the signal amplitude, being an indicator, how strong the telegram signal is received.
NOTE: The time of arrival has a very much higher resolution than the time of day, but it cannot
be synchronized with usual clocks, because its range is less than 3000 seconds. The TOA
is not considered in ADS−B applications.
Ed. 10.07 5−21

AS 680/682 ADS−B
5.4.8 Page ’Telegram Check’

On this page, see Fig. 5−12, test criteria for telegram validation are defined. Any telegram that does
not pass these tests is discarded. This page is used to fine tune the probability of detection versus
the false alarm rate.
Fig. 5−12 Page ’Telegram Check’ (example)
5.4.8.1 Confidence Bits, AP Residuum and Signal Amplitude

Confidence bits are generated for all telegrams. The number of telegram bits, called confidence bits,
is counted and checked versus a given threshold. If the given confidence bits threshold is reached,
the telegram will be discarded. If the value of the parameter equals −1, the confidence check is disa-
bled.
The ’AP Field Residuum Check’ enables the check on a correct residuum of the parity check for squit-
ters. This check is only applicable of squitters containing an AP−field. If the residuum is equal to zero,
the information contained within the telegram data block is considered correct. The AP residuum
check is more reliable and overrules the confidence bit check.
The signal amplitude level determines the minimum amplitude of a signal to represent a valid tele-
gram. If the value of the parameter equals −1, the amplitude check is disabled.
5.4.8.2 Error Correction

Enabling error correction means that the SPB tries to correct damaged telegrams. Error correction
is only performed, if the AP−Field is not 0 and only one confidence bit is set, i.e. only one telegram
bit is bad.
5−22 Ed. 10.07

ADS−B AS 680/682
5.4.9 Page ’Process’
This page, see Fig. 5−13, is for internal use only. It allows to configure and fine−tune the multi−
threading behavior of the Ground Station software.
Fig. 5−13 Page ’Process’ (example)
5.4.9.1 Idle Times
The idle times determine, in which intervals the following threads have to run.
S the ’Main Thread’ manages among others the GPS polling trigger
S the ’Base Thread’ fetches telegrams from telegram buffer and sends raw data
S the ’ADSB Thread’ performs CPR Decoding
S the ’Bite Thread’ performs the BITE tests
S the LED Thread manages the LEDs at the SPU
5.4.9.2 Buffers
The text fields ’Raw Data Buffer Size’ and ’Asterix Buffer Size’ show the maximum size of the corre-
sponding software internal buffer in bytes. At least, when the maximum size is reached, the respective
data are flushed to the network.
Ed. 10.07 5−23

AS 680/682 ADS−B
The ’Trackstore Size’ gives the number of entries in the software internal buffer holding the information
about the targets. Every target, i.e. every mode S address, received by the Ground Station has one
entry in the trackstore until its maximum age is reached. The trackstore is implemented as a static
hash map for fast read access. Its size must be a prime due to the used hashing algorithm.
NOTE: The use of a hash map is a very efficient possibility of storing a big amount of data, which
have to be accessed very frequently. The current hash map being used as trackstore is
of a fixed size (no dynamic memory allocation or de−allocation) for reasons of software
robustness.
5.4.9.3 HW−Interrupt and Memory
The SPB reading interval is a read−only parameter, which can be requested from the Ground Station
and shows the reading intervals (in seconds) of data input in the hardware.
The ’System’ parameter ’Free Memory’ is also read−only and shows the currently free memory on
the SPB in KB.
5.4.10 Page ’ADSB’
This page, see Fig. 5−14, defines all necessary parameters for AS 680 ADS−B processing. The
ADS−B processing can be enabled or disabled.
Fig. 5−14 Page ’ADSB’ (example)
5−24 Ed. 10.07

ADS−B AS 680/682
5.4.10.1 Trackstore and FOM/PA Restriction
The parameter ’No. of Targets’ (Trackstore) shows the number of targets just found in the output buffer
(see section 5.4.9.2). This parameter is used to check the fill level of the trackstore.
The parameter ’No. of Targets’ (FOM/PA Restriction) is the same like the parameter explained above,
with the exception that only the targets whose Mode−S ID matches an entry in the FOM/PA Restric-
tion table.
The threshold level in percent of the trackstore size (refer to section 5.4.9.2) defines the warning
threshold of the trackstore fill level. If the trackstore threshold level is reached, the status of the Ground
Station changes to WARNING, provided that the BITE test for ‘Trackstore Status’ is enabled and the
’BITE Status’ is retrieved (refer to section 5.4.3).
5.4.10.2 Asterix Information
Sending asterix target reports can be done in two ways: ’Pipeline Mode’ or ’Buffered Mode’. In ’Pipe-
line Mode’ a report is sent as soon as possible after the reception of a valid position or velocity squitter.
In ’Buffered Mode’ the reports are sent in certain interval. The interval can be configured by setting
the parameter ’Send Interval’. If the interval is e.g. set to 4, then a reports (if available) are sent every
4 seconds.
NOTE: The parameter ’Send Interval’ has no effect if pipe line mode is enabled.
The parameter ’Packing’ enables Asterix packing as defined by Eurocontrol. Packing of several re-
ports into one data block is used to reduce network overhead and thus improves efficiency on the
ground communication. In pipeline mode packing is disabled by default.
The text field ’Data Rate’ shows the current rate of sent ASTERIX data in bytes per second. The ’Data
Rate Threshold’ in bytes per second defines the warning threshold for the Asterix data rate.
5.4.10.3 Automatic Data Rate Reduction
This feature will reduce/increase the asterix data output by automatically changing the ’Send Interval’,
if the ’Data Rate’ exceeds/falls below the ’Data Rate Threshold’. ’Min/Max Send Interval’ constraints
can be configured to ensure a certain ’Send Interval’ range in which the ground station will operate.
If the ’Send Interval’ has reached its maximum and the ’Data rate’ still exceeds the ’Data Rate Thresh-
old’, an ADS−B BITE error will be raised.
NOTE: If ’Pipeline Mode’ is enabled this ’Automatic Datat Rate Reduction’ has no effect.
Ed. 10.07 5−25

AS 680/682 ADS−B
5.4.11 Page ’ADSB Filter’
This page, see Fig. 5−15, defines parameters and filter settings used during CPR decoding of incom-
ing extended squitters.
Fig. 5−15 Page ’ADSB Filter’ (example)
5.4.11.1 Extended Squitter and CPR Decoding

The parameter ’Position Type’ defines the extended squitter filter setting for airborne targets or targets
on the ground. It is possible to let the Ground Station consider only airborne, only surface or airborne
and surface positions.
It is possible to determine a certain method of the compact position reporting algorithm (CPR) for
airborne or surface position squitters.
The globally unique position decoding needs two airborne position extended squitters. One of these
must be decoded with the even decoding technique, the other one with the odd decoding technique
to get a worldwide (in case of surface position squitters almost worldwide) unique target position.
Selecting ’global’, the Ground Station needs always an odd and even airborne position squitter to
calculate a target position.
Selecting ’local’, the first position of a target is calculated with the global decoding method. All subse-
quent position squitters are decoded with the help of a reference position being the position of the
Ground Station or the previously decoded position of the target. This depends on the setting of the
’Last Target Position as Ref.’ parameter.
5−26 Ed. 10.07

ADS−B AS 680/682
Only extended squitter being compliant with the given versions DO260 or DO260A determined with
the ’DO260A Filter’ are considered by the Ground Station.
The ’Mandatory Field Check’ enables the check for the presence of data items, which are mandatory
for generation of valid Asterix target reports. Mandatory fields are e.g. the target position (longitude
and latitude), the time of day, the target ICAO 24−bit address.
The Asterix CAT21 mandatory fields are:
− Data Source Identification
− Target Report Descriptor
− Time of Day
− Position in WGS 84 Coordinates
− Target Address
− Figure of Merit.
The ’Cover Range’ of the Ground Station is given in nautical miles (NM). If set, any position reports
beyond that range are ignored by the Ground Station. The ’Cover Range’ is disabled setting the value
’–1’.
A minimum and maximum flight level threshold, given in Flight Level (1 FL = 100 ft), cause the Ground
Station to discard any target reports outside the given range.
FOM/PA Restriction can be enabled/disabled. When enabled, a Target’s PA value (Position Accuracy)
can be limited depending on the FOM/PA Restriction table which can be uploaded/downloaded on
the software page (see section 5.4.13).
5.4.11.2 Age Filters
The ’Track’ age, given in seconds, is the maximum age of a track since its last valid update, before
it becomes invalid.
’Position’ defines the maximum age of a valid position in seconds. Obsolete positions are not consid-
ered, when Asterix reports are generated.
If the last update of the identification is older than the last position update minus relative ’Target Identi-
fication’ age in seconds or more recent than the last position update plus the relative ’Target Identifica-
tion’ age, then the identification for the respective target is declared invalid.
If the last update of the velocity is older than the last position update minus the relative ’Velocity Squit-
ter’ age in seconds or more recent than the last position update plus the last ’Velocity Squitter’ age,
then the velocity data for the respective target is declared invalid.
If the last update of the aircraft status is older than the last position update minus the relative ’Target
Status Squitter’ age in seconds or more recent than the last position update plus the relative ’Target
Status Squitter’ age, then the aircraft status for the respective target is declared invalid.
If the last update of the aircraft operational status is older than the last position update minus the rela-
tive ’Aircraft Operational Status’ age in seconds or more recent than the last position update plus the
relative ’Aircraft Operational Status’ age, then the operational status for the respective target is de-
clared invalid.
Ed. 10.07 5−27

AS 680/682 ADS−B
5.4.12 Page ’Site Monitor’
This page, see Fig. 5−16, is used to configure the Site Monitors’ test equipment. Every Ground Sta-
tion is duplicated, i.e. for every Ground Station there is a backup Ground Station. The currently active
system and the backup system are equipped with a Site Monitor, respectively. Every Site Monitor gen-
erates target telegrams for test purposes, which must be received by both Ground Stations. The BITE
test ’RF−Path’ tests the working of the Site Monitors (see page ’BITE’, section 5.4.3).
Fig. 5−16 Page ’Site Monitor’ (example)
5.4.12.1 Own and other Site Monitor

The Site Monitors at both Ground Stations (own and other) generate targets with the mode S address
found in the textfield ’Address’ and the downlink format given in the option field ’Telegram Downlink
Format’, respectively.
The Ground Station expects the signals at a least receiver level given in the field ’RX Level’ fields and
within the intervals determined by ’Expected Repetition Interval’ in seconds.
5.4.12.2 Test Target

The test targets are generated in the Ground Station software within a given ’Report Interval’ in se-
conds. This test target sends only surface position squitters. If the ’Report Identity’ parameter is blank,
the default value ’THALES’ is used for the test target identity.
It is possible to decide with the ’Report Trigger’, if no reports shall be generated or reports shall only
be generated, if:
S no BITE error is found (biteNoErr) or
S Site Monitor exists and no BITE error is found (siteMonBiteNoErr) or
S a valid GPS position exists and no BITE error is found (gpsPosBiteNoErr) or
S a valid GPS position and a Site Monitor exists and no BITE error is found (siteMonGpsPosBite-
NoErr).
5−28 Ed. 10.07

ADS−B AS 680/682
5.4.13 Page ’Software’
This page informs about the software versions running in the Ground Station (see Fig. 5−17).
Fig. 5−17 Page ’Software’ (example)
Ed. 10.07 5−29

AS 680/682 ADS−B
5.4.13.1 Current Configuration

Two kernel and two application partitions are supported in a Ground Station. The parameter ’Kernel
Partition’ shows the currently active kernel partition and the parameter ’Application Partition’ shows
the currently active application partition. Different kernels with application versions are possible.
5.4.13.2 Flash Content

Content of the possible partitions as file names consisting of name, version, date, time and build user
for Kernel and Application.
5.4.13.3 Figure of Merit − Position Accuracy Table

Contains the FOM/PA table version with name, version and date.
Fig. 5−18 FOM/PA table (example)
5.4.13.4 Figure of Merit − Position Accuracy Restriction Table

Contains the FOM/PA restriction table version with name, version and date.
Fig. 5−19 FOM/PA restriction table (example)
5−30 Ed. 10.07

ADS−B AS 680/682
5.4.13.5 Upload
NOTE: The ’Browse’ button within this ’Upload’ section of the ’Software’ page can be used to
select a file within an appearing file selection dialog. The selected file is then entered auto-
matically into the corresponding edit field. The other possibility is to enter the file name
manually.
5.4.13.5.1 Upload Ground Station Kernel

With the ’Upload’ of a ’Kernel’, a new kernel image can be uploaded from the RCMS/LCMS, where
the TSC is running, to the Ground Station, the TSC is connected to. Only the not active kernel will be
uploaded automatically. A confirmation panel pops up, when uploading a kernel image.
Enter the kernel image file (via ’Browse’ or manually, see NOTE above), and click on ’Upload’. A con-
firmation dialog appears, start the uploading of the file by clicking on button ’OK’.
After confirmation, a terminal window named ’uploadKernel’ pops up, where the password of the su-
pervisor is requested (see Fig. 5−20).
Fig. 5−20 Upload Kernel, start of upload (example)
After entering the correct password, the uploading process will continue with any further user interca-
tion. If the uploading of the kernel is successfully done the instruction string "Press return to close!"
appears in the window (see Fig. 5−21). So press the <RET> key to close the terminal window.
Fig. 5−21 Upload Kernel, upload successfully done (example)
Ed. 10.07 5−31

AS 680/682 ADS−B
5.4.13.5.2 Upload Ground Station Application
The ’Upload’ of the ’Application’ is done in the same way then described for the ’Kernel’ in previous
section 5.4.13.5.1 . Fig. 5−22 shows an example of an ’uploadApplication’ terminal window.
Fig. 5−22 Upload Application (example)
NOTE: It is important to keep the recommended order when uploading the kernel and the
application software. The upload sequence is as follows:
1. Upload new Kernel software version.
2. Switch over to new Kernel via Kernel partition reboot.
3. Upload the new Application software version.
4. Switch over to new Application partition via application restart.
5. Repeat for the other Kernel and Application as required.
5.4.13.5.3 Upload FOM/PA Table
The ’Upload’ of the ’FOM/PA table’ is done in the same way then described for the ’Kernel’ in section
5.4.13.5.1 . Fig. 5−23 shows an example of an ’uploadNuc’ terminal window.
Fig. 5−23 Upload FOM/PA Table (example)
5−32 Ed. 10.07

ADS−B AS 680/682
5.4.13.5.4 Upload NVRAM Configuration
Uploading the NVRAM Configuration is a bit different to the previously described uploading proce-
dures and therefore described here again in detail. First, the user has to confirm the intention to
upload the NVRAM Configuration within a confirmation window by clicking on the ’OK’ button.
The uploading of the NVRAM Configuration is divided into 3 steps (see Fig. 5−24, where all 3 steps
are presented on the screen):
1. A backup of the NVRAM Configuration will be copied to the local /tmp directory.
For this action the password of the supervisor is requested.
2. A check is done, testing if uploading the new NVRAM Configuration will change ’critical’ network
parameter, which are:
− Ground Station IP Address (Main)
− Ground Station IP Address (Aux)
− Netmask (Main)
− Netmask (Aux)
− Default Gateway
NOTE: Changing those parameters can cut off the network connection to the Ground Station.
If changes were detected, the user is asked whether to proceed the uploading process
or not (see Fig. ).
3. The new NVRAM Configuration is copied to the GS. Therefore the user has to give the password
of the supervisor again.
If the uploading of the NVRAM Configuration is successfully done the instruction "Press return to
close!" appears in the ’uploadConfig’ window. So press the <RET> key to close the window.
Fig. 5−24 Upload NVRAM, 3 steps of uploading (example)
Ed. 10.07 5−33

AS 680/682 ADS−B
5.4.13.5.5 Upload FOM/PA Restriction Table
The ’Upload’ of the ’FOM P/A Restriction Table’ is done in the same way then described for the ’Kernel’
in section 5.4.13.5.1 . Fig. 5−25 shows an example of an ’uploadFomPaRestriction’ terminal window.
Fig. 5−25 Upload FOM/PA Restriction Table (example)
5−34 Ed. 10.07

ADS−B AS 680/682
5.4.13.6 Download
NOTE: The ’Browse’ button within this ’Download’ section of the ’Software’ page can be used
to select a file within an appearing file selection dialog. The selected file is then entered
automatically into the corresponding edit field. The other possibility is to enter the file
name manually.
5.4.13.6.1 Download NVRAM Configuration

Downloading the NVRAM Configuration is done by entering a valid filename (via ’Browse’ button or
manually, see NOTE above) and pressing the ’Download’ button.
First, the user has to confirm the intention to download the NVRAM Configuration within a confirma-
tion window by clicking on the ’OK’ button. Then a terminal pops up (’downloadConfig’), where the
destination file is shown (in our example: /tmp/ajacciob.csg). The password of the supervisor is re-
quested (see Fig. 5−26).
Fig. 5−26 Download NVRAM, start of download (example)
After entering the correct password, the uploading process will continue with any further user interca-
tion. If the uploading of the kernel is successfully done the instruction string "Press return to close!"
appears in the window (see Fig. 5−27). So press the <RET> key to close the terminal window.
Fig. 5−27 Download NVRAM, download successfully done (example)
The contents of the table stored in the destination file can be edited (see Fig. 5−28). Call an editor
within a ’Terminal’ window and enter the command: nedit <destination file>.
Fig. 5−28 Extract of an NVRAM configuration file contents (example)
Ed. 10.07 5−35

AS 680/682 ADS−B
5.4.13.6.2 Download FOM/PA Restriction Table
The ’Download’ of the ’FOM P/A Restriction Table’ is done in the same way then described for the
’NVRAM Configuration’ in the previous section 5.4.13.6.1 . Fig. 5−29 shows an example of a ’down-
loadFomPaRestriction’ terminal window.
Fig. 5−29 Download FOM/PA Restriction Table (example)
The contents of the table stored in the destination file can be edited (see Fig. 5−30). Call an editor
within a ’Terminal’ window and enter the command: nedit <destination file>.
Fig. 5−30 Extract of a FOM/PA Restriction Table file (example)
5−36 Ed. 10.07

ADS−B AS 680/682
5.4.13.7 Restart/Reboot
5.4.13.7.1 Reboot
The Ground Station can be rebooted remotely by the TSC. This can be done on the page ’Software’
within the section ’Restart/Reboot.
By selecting the corresponding ’Kernel Partition’, it is possible to reboot the currently running kernel,
or to make a ’kernel switch over’ and boot the currently not running kernel.
Start the reboot procedure by clicking on the ’Reboot’ button. First, the user has to confirm the inten-
tion to reboot within a confirmation window by clicking on the ’OK’ button. Then a terminal pops up
(’reboot’), requesting the supervisor’s password.
After entering the correct password, the rebooting process will continue with any further user interca-
tion. The progress of the reboot process depends on the selected ’Kernel Partition’. Fig. 5−31 shows
an example for rebooting the currently running kernel
Fig. 5−31 Reboot terminal log without kernel switch (example)
If booting the currently not running kernel, a ping test on the IP−address of the current RCMS, stored
in the NVRAM, is performed (see Fig. 5−32). If the ping test is successful, then the kernel switch is
supposed to have successfully finished. In case of failure, the old kernel is rebooted.
Fig. 5−32 Reboot terminal log with kernel switch (example)
If the rebooting is successfully done the instruction string "Press return to close!" appears in the win-
dow (see Fig. 5−31). So press the <RET> key to close the terminal window.
To see if a kernel switch has been successful, just press the green ’Refresh’ button in the middle of
the ’Software’ page (see Fig. 5−17) and then, after rebooting, check if the contents of the ’Kernel Parti-
tion’ field within the ’Current Configuration’ section shows the right running kernel.
Ed. 10.07 5−37

AS 680/682 ADS−B
5.4.13.7.2 Restart
The Ground Station application can be restarted remotely by the TSC.
After selection of the ’Application Partition’ and clicking on the ’Restart’ button, the user has to confirm
the intention to restart within a confirmation window by clicking on button ’OK’. Then a terminal pops
up (’restart’) showing the progress of the restart process (see Fig. 5−33). During this process the
Ground Station can not be accessed (for some seconds).
Fig. 5−33 Restarting the application (example)
If the restarting is successfully done the instruction string "Press return to close!" appears in the win-
dow (see Fig. 5−31). So press the <RET> key to close the terminal window.
To see if the application restart has been successful, just press the green ’Refresh’ button in the
middle of the ’Software’ page (see Fig. 5−17) and then, after refreshing, check if the contents of the
’Application Partition’ field within the ’Current Configuration’ section shows the right running applica-
tion partition.
5.4.13.7.3 Login
The button ’Login to Groundstation’ opens a terminal Fig. 5−34, so that the supervisor can login into
the Ground Station.
Fig. 5−34 Ground Station Login (example)
5−38 Ed. 10.07

ADS−B AS 680/682
5.4.14 Page ’GPS’
The GPS module and the Ground Station are connected to each other via a serial connection. The
communication between both is configured on this page, see Fig. 5−35.
Fig. 5−35 Page ’GPS’ (example)
5.4.14.1 GPS Position

If the Ground Station has a GPS module and this GPS is enabled, then GPS provides the Ground
Station’s position in degrees and altitude in feet. These values found out by GPS are inserted into the
text fields ’Latitude’, ’Longitude’ and ’Altitude’.
5.4.14.2 Ground Station Position

The position of the Ground Station antenna given in degrees of latitude and longitude, is based on
the WGS−84 reference system in ellipsoidal co−ordinates (decimal representation). These parame-
ters are necessary for CPR decoding and set by the supervisor. The altitude (in feet) of the Ground
Station is used for the test target report depending on the test target ’Report Trigger’ (refer to section
5.4.12.2).
Ed. 10.07 5−39

AS 680/682 ADS−B
5.4.14.3 Satellites
The number of tracked satellites and their corresponding PRN numbers (SV−ID) are shown.
5.4.14.4 HPL
The HPL (Horizontal Protection Level) is given in Nautical Miles [NM] and meters [m]. The No of Sat-
ellites (HPL)’ shows how many satellites are used for the HPL calculation.
5.4.14.5 GPS Module Information
There are two types of GPS modules supported by the Ground Station:
S DG14 with Type−Version: DG−DC15
S B12 with Type−Version: EX−HM09
Other modules will be indicated with unknown’ in the Type−Version’ field.
NOTE: Only the DG14 GPS module can provide HPL information.
The GPS Data’ field shows available’ only if all GPS values on this page are received correctly by
the Ground Station. Otherwise the field shows notAvailable’.
The ’Polling Interval’ determines the interval, how often GPS data shall be sent to the Ground Station.
5.4.14.6 DOP
The DOP field shows the three Dilution of Precision’ values (V=vertical, P=position, H=horizontal).
5.4.14.7 GPS Position Deviation
’Current Position Deviation’ shows the deviation between the position sent by GPS and the reference
position given in ’GS Reference Position’. If the deviation exceeds the Position Deviation Threshold’,
the GPS BITE test fails.
5.4.14.8 GPS and System Time
’System Time’ shows the present time in the Ground Station. Time Difference’ shows the difference
between the GPS time and the System time in seconds. If this difference exceeds the value given in
the Time Difference Threshold’ field, the BITE will indicate a GPS error.
5−40 Ed. 10.07

ADS−B AS 680/682
5.4.15 Page ’UPS’
Fig. 5−36 Page ’UPS’ (example)
5.4.15.1 UPS
The first parameter defines the IP address of the UPS communication module. The status can have
one of the following values:
S ok
UPS is running without any failure.
S upsAlarm
Indicates the UPS alarm condition.
S snmpTimeout
The UPS communication module can’t be accessed via SNMP.
S threadTimeout
UPS surveillance process is not running, see page ’BITE’ (section 5.4.3)
To get more information about a UPS alarm condition, press the button ’Launch UPS Diagnostic’.
Ed. 10.07 5−41

AS 680/682 ADS−B
5.4.15.2 Configuration of SNMP−Card ’CS121 BUDGET’
This section describes the configuration of the SNMP−Card ’CS121 Budget’ of the UPS XS1000R.
After configuration you will be able to correspond from a computer (RCMS or LCMS) via LAN/WAN
with the UPS.
To readout the UPS within a LAN /WAN it is necessary to build in and configure the SNMP−Card
CS121 BUDGET".
5.4.15.2.1 Setup
Remove the cover at the rear right side (two screws).

Make sure that the two switches of the DIP−Switch are in position OFF",
(default IP Address = 10.10.10.10), see Fig. 5−37.
DIP−Switch
Fig. 5−37 SNMP−Card ’CS121 Budget’
Insert the SNMP−Card CS 121 BUDGET".

Connect the LCMS via a cross−over cable with the SNMP−Card of the UPS (see Fig. 5−38).
UPS CS 121 LCMS
Fig. 5−38 Set−Up for CS 121 configuration
5.4.15.2.2 Preparation
Switch on the LCMS and wait for booting and login as supervisor.
Open a terminal window.
Check the IP address of LCMS by typing: </sbin/ifconfig>
Result should be: <IP=192.168.23.2>
Change the IP address to <10.10.10.11> as follows:
S Type <system−config−network> <Enter>
S Enter root password : <12lcms21>
S Double−click on <eth0>
5−42 Ed. 10.07

ADS−B AS 680/682
S Change address to <10.10.10.11> and click <OK>
S Click on the button <Deactivate> (click in the next 2 Windows on <OK>)
S Click on the button <Activate> to save the changes
S Close the window
Send a ping to the SNMP card, type: <ping 10.10.10.10> <Enter>
Wait for answer.
To stop the answers press <CTRL + C>
Click with the right mouse button within the desktop screen
Select <Run Program …> and type <firefox> <ENTER>
The Firefox Web Browser will be opened with a blank page
Enter in the URL line the IP address <10.10.10.10> and press <OK>
Fig. 5−39 Firefox Browser
Fig. 5−40 UPS Adapter Configuration Mode
Ed. 10.07 5−43

AS 680/682 ADS−B
5.4.15.2.3 Configuration
Click on the left side in the Configuration−Menu on <UPS Model & System> and the following
windows will be opened for the HTTP administrator login:
Fig. 5−41 Administrator Password
Enter the username <admin> and the password <cs121−snmp>.
- Settings of Model & System
The following settings must be made:

S UPS Model: select the used type XANTO S 1000 R with the correct number of Battery packs
S The following items at the left side will be filled in normally automatically.
S At the right side fill in all relevant items like:
System Name
System Location
System Contact
Attached Devices and the
Battery Installation Date (Fig. 5−42 shows an example)
S After filling in all items click <Apply>.
Fig. 5−42 Model & System setting (example)
5−44 Ed. 10.07

ADS−B AS 680/682
- Settings of the network
Click on the left side within the menu <Configuration> the button <Network & Security>
The following settings must be made (example see Fig. 5−43):
S Local Address (192.168.24.215 for the first UPS, 192.168.24.216 for the second UPS etc.)
S Gateway Address (192.168.24.254)
S Subnet Mask (255.255.255.0)
S Change Administrator Password to <12ups21>
S Confirm Password
S For the UpsMon & SS4 Password click <Clear>
S Enter a hook at Use UpsMon Password for Web Pages:"
Fig. 5−43 Network & Security settings (example)
After filling in all items click <Apply>.
NOTE: Do not forget the password, because you must start the procedure from beginning (De-
fault Settings).
- Settings of SNMP
Click on the left side within the menu <Configuration> the button <SNMP>.
The SNMP Settings" window will be opened.
The following settings must be made, to make communication for the UPS available (see Fig. 5−44):
S Addresses
S Communities and
S Permissions
Ed. 10.07 5−45

AS 680/682 ADS−B
Fig. 5−44 SNMP settings (example)
After filling in all items click <Apply>.
- Save Configuration
Click on the left side within the menu <Configuration> the button <Save Configuration>.
The following Fig. 5−45 (Configuration Manager) is shown:
Fig. 5−45 Configuration Manager

Click <Save Configuration> . The following window will be shown (see Fig. 5−46):
Fig. 5−46 Save Configuration
Click the <OK> button and wait until the changes are written to the flash memory (working cursor).
Click <Reboot>.The following window (Fig. 5−47) is shown:
5−46 Ed. 10.07

ADS−B AS 680/682
Fig. 5−47 Reboot the adapter
Click the <OK> button and wait until the adapter is been rebooted (working cursor). Wait at least 60
sec. and press than ’Reload’.
- Normal Operation
The next is to change the adapter to the normal operation.
Switch the UPS OFF".
Disconnect the UPS from main power.
Remove the SNMP−Card CS 121 BUDGET".
Change the DIP−Switch switch 1 to ON" and switch 2 to OFF".
Insert the SNMP−Card CS 121 BUDGET" again.
Connect the UPS to the main power.
Switch the UPS ON".
Click with the right mouse button within the desktop screen
Select <Run Program …> and type <firefox>. Press <Enter>
Enter in the URL line the IP address you set during the configuration phase (see section ’Settings of
the network’) and press <Enter>
Wait until the adapter has been booted. The following window (Fig. 5−48) is shown:
Fig. 5−48 Normal Operation, UPS Status
Ed. 10.07 5−47

AS 680/682 ADS−B
- Reconfigure the UPS
To change the settings of the UPS−Adapter enter from normal operation into the configuration menu
of UPS−Adapter.
After changing the entries within a window click on <Apply> before you change to the next configura-
tion menu point.
NOTE: Don’t forget to save the new configuration as written in section ’Save Configuration’.
5−48 Ed. 10.07

ADS−B AS 680/682
5.4.16 Page ’Logging’
The TSC records all configuration and status changes of the AS 680 to three different output devices:
S the status bar
S the page ’Logging’
S the log file
Fig. 5−49 Page ’Logging’ (example)
The content of the page ’Logging’, see Fig. 5−49, and the content of the log file are identical except
that the page ’Logging’ has a buffer of only 1000 log−messages, i.e. only the last 1000 log−mes-
sages can be displayed. A scroll bar on the right side can be used to scroll through the messages
on the page.
The option button at top of the message field can be used to enable/disable the ’Automatic scroll to
the last Log−Message’.
Ed. 10.07 5−49

AS 680/682 ADS−B
The configuration and status output comprises:
S each Get/Refresh click/command will be logged including the received values
S all commands, that will change one or more parameters of the Ground Station; previous and cur-
rent value(s) are mentioned in the log−message
S special commands, like rebooting a kernel.
S all commands that fail, no matter, if the command requests a change in Ground Station parameters
or if the command only polls for Ground Station parameters.
S the status of the Ground Station and the value of the ’BITE Status’, if the ’BITE Status’ is requested.
S information about switches between Ground Stations
As depicted in Fig. 5−49, the messages have different colors depending on the status of the Ground
Station. Log messages describing successful commands will be printed with a white background
(instead of green color indicating actually the RUNNING status of the Ground Station).
5−50 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Monitor User Operation
CHAPTER 6
MONITOR USER OPERATION
In this chapter the operation of the TSC in Monitor User mode is described. The set of available func-
tions for the Monitor User is a subset of the Supervisor functions described within chapter 5.
Therefore only the differences to the Supervisor functions are listed within this chapter.
NOTE: Another application is the MTSC running on the RCMS. The MTSC functionality available
for the Monitor User on the RCMS is described in section 4.3.4.
The Monitor User is not allowed to change any parameter within the Notebook of the TSC. That
means, that all ’Edit’ buttons on any page of the TSC Notebook are hidden and not available (refer
to section 5.4.1).
Additionally for Monitor Users it is not allowed to configure or tune the behavior of the Ground Station
software. Therefore the page ’Process’ (see section 5.4.9) is not available, the tab is not provided
within the Monitor User’s notebook.
On some of the notebook pages described in chapter 5, the Monitor User’s functionality is restricted:
S On page ’’BITE’ (see section 5.4.3) no deactivation of Bite Status polling is possible, i.e. the fea-
ture ’Polling is activated’ can’t be deactivated by the Monitor User.
S On page ’Telegram Filter’ (see section 5.4.4) all buttons are hidden, i.e. no setting of downlink
format filters is possible. Only the ’Refresh’ button is active to update the page.
S In addition the Monitor User is not allowed to update or restart/reboot the Ground Station soft-
ware, i.e. on page ’Software’ there are some restrictions for the Monitor User.
The ’Upload’ (see section 5.4.13.5) and the ’Restart / Reboot’ function (see section 5.4.13.7) are
not available for the Monitor User within the notebook of page ’Software’ (see Fig. 6−1, next page).
Ed. 10.07 6−1

AS 680/682 ADS−B
Monitor User Operation Description, Operation and Maintenance
Fig. 6−1 Page ’Software’ for the Monitor User (example)
6−2 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Maintenance and Repair
CHAPTER 7
MAINTENANCE, FAULT LOCATION AND REPAIR
7.1 PREVENTIVE MAINTENANCE
7.1.1 General
This chapter describes all measures of preventive maintenance to be performed during the life time
of the ADS−B Ground Station. The ADS−B Ground Station does not require any periodic calibration
and, as such, there are no items which need to be returned for adjustment. Although, there are no
periodic calibration or re−initialization procedures required, basic preventive maintenance must be
performed periodically.
The annual inspection should include, but is not limited to a general check of the condition of power
distributions, conduits, ground connections, lightning rods, RF cable connectors for corrosion or wa-
ter intrusion (if applicable). An inspection of the GPS and ADS−B RX antenna and possibly the an-
tenna ground planes for damage or pollution is recommended.
If any fault is detected refer to 7.2 Fault Location. After the fault is located corrective maintenance is
performed to replace subsystems or subassemblies. This is described in 7.3 Repair.
7.1.2 Periodic Maintenance
We recommend performing the maintenance activities listed in the table below. The used interval de-
pends on the actual environment and may be defined by the local authorities.
NOTE: During preventive maintenance, the Ground Station does not need to be switched into
a non−operational mode.
No. Daily maintenance Reference
no measures −
No. Monthly maintenance Reference
no measures −
No. Six month maintenance Reference
no measures −
No. Yearly maintenance Reference
1 Damage check, visual inspection 7.1.4
2 Cleaning of equipment surfaces 7.1.5
3 Change and/or cleaning of dust filter 7.1.5.1
No. Two−year maintenance Reference
1 Preventive exchange of fan tray 7.1.6
2 Verify SPU/RXU Local Oscillator frequency 7.1.7
No. Five−year maintenance Reference
1 Exchange of Lithium Snaphat battery (SPU/SBC) 7.1.8
7.1.3 Elimination of Static Charges

A grounding strip with a large cross−sectional area is connected between the shelter grounding ter-
minal, the equipment racks and the worktable to act as the system ground and to eliminate electro-
static charges. It is firmly connected to the table and a grounding bus on the working surface. This
system ground should not be connected to either the mains protective ground conductor or to hous-
ings and grounds of external consumers, i.e. consumers not associated with the worktable, except
at the potential equalization bus for the overall installation.
Ed. 10.07 7−1

AS 680/682 ADS−B
Maintenance and Repair Description, Operation and Maintenance
The protective ground wire offered with mains cable or plug connections is not suitable for potential
equalization of equipment on a worktable. Depending on local circumstances, it can carry quite high
RF interference voltages.
Mains−supplied equipment, power supplies and test equipment should be connected via two−wire
cables and two−pin plugs. For measures to be taken with respect to components sensitive to elec-
trostatic charging (MOS, Low Power Schottky) please refer to the customer service documentation
of the manufacturer. If an employee is required to handle subassemblies for transport purposes, he
should place both hands flat on a grounded surface beforehand (e.g. on the ground bus of the work
table). The module can be picked up by its insulator immediately following this potential equalization.
It is safer to avoid touching the terminals. Only remove short−circuit links where absolutely neces-
sary. Place printed circuit boards only on tables with a conductive, grounded working surface. Leave
individual subassemblies in the antistatic plastic bags for as long as possible.
7.1.4 Damage Check/Visual Inspection

The following outdoor and indoor system parts have to be checked visually for entirety.
Outdoor:
− State of ADS−B RX and GPS antennas, LNA−housing, cables
− Tight fitting of all RF cable and earthing connections (external).
Indoor:
− State of SPU and Site Monitor, cables
− Openings of the SPU for dust, dirt or other obstacle of air flow and remove it.
− Tight fitting of all RF/AF cable and earthing connections (internal).
7.1.5 Cleaning
Required Tools: Brush, soft tissue or vacuum cleaner depends on level of dirt.
CAUTION
Cleaning aids, such as brushes and dusters, must be made of antistatic material. See also
the instructions in Section 7.1.3.
The air dust filter of the SPU and ventilation openings (front air inlet and right side air outlet) should
be checked from time to time in accordance with the volume of dirt that accumulates at the particular
location.
7.1.5.1 Cleaning the Dust Filter Mat of the Air Inlet

See Fig. 7−4.
Required Tools: Philips Screw Driver #2, vacuum cleaner (depends on level of dirt)
− Open the air inlet cover with the four captive screws and remove it.
− Withdraw the dust filter mat frame right hand inside.
− Carefully beat it clean or use a vacuum cleaner, or if need be insert a new dust filter mat frame
(Ref. No. 58142 30410).
− Slide the dust filter mat frame into the slide close to the stop.
− Clean the air inlet cover.
− Mount the air inlet cover and fasten the four captive screws.
7−2 Ed. 10.07

ADS−B AS 680/682
7.1.6 Preventive Exchange of Fan Unit
As preventive measure it is recommended to replace the fan unit in the SPU after about 2 years.
Tools required: Philips Screw Driver #2
Replace the Fan Unit as follows (see also section 7.3.3.6):
a) Switch off DC of the Ground Station (recommended: change without GS switch off also possible).
b) Unfasten the four captive screws fixing the Fan Unit.
c) Extract the Fan Unit carefully from the 19" subrack until the DC supply cable with the connector
is visible. Press the lock of the fan supply cable connector and remove it from the cable to the mo-
therboard.
d) Connect the connector of the spare Fan Unit to the supply cable to the motherboard until it locks.
e) Carefully insert the new Fan Unit into the slide. Take care not to squeeze the supply cable. Fasten
the four captive screws.
f) Switch on DC of the Ground Station.
7.1.7 Check and Adjustment of SPU/RXU local Oscillator Frequency

As preventive measure it is recommended to perform a check and if necessary a corrective adjust-
ment of the local oscillator frequency of the RXU subassembly in the SPU.
Tools required: Philips Screw Driver #2, Maintenance Adapter,Digital Multimeter, RF−Generator
Perform the following procedure to check the frequency (refer to Fig. 7−1):
a) Switch off the Ground Station. Remove RF cable from connector RF In.
b) Remove the RXU board, and insert the RXU again plugged on a maintenance adapter. Open
jumper X3 (RXU1) or X1 (RXU2).
d) Set RF Generator to apply an RF signal of 1090 MHz and P= −80 dBm to connector RF In.
NOTE: The LO frequency will be calculated as flo = fin − 60 MHz; this is 1030 MHz.
e) Switch on the Ground Station.
f) Vary the RF frequency about ±3 MHz at the RF generator to get a maximum DC voltage reading
at the Digital Voltmeter. The maximum should be within 1089 to 1091 MHz.
RXU1, Ref. No. 83142 71502, only: If not, an adjustment of the local oscillator frequency (LO) on
the RXU1 is required. Perform procedure in 7.1.7.1.
g) Switch off the Ground Station. Remove measuring cables. Withdraw RXU board. Set X3 (RXU1)
or X1 (RXU2) again. Insert RXU board and connect RF cable as normal again.
SPU
top view
Digital voltmeter SPU RF generator
000.0 1090 MHz

I
shielding
cover 0 RF out
Monitor Out RF In
RXU
RXU, plugged on
X3 (RXU1)
maintenance adapter or
X1 (RXU2) Adapter cable SMA/BNC/Banana plug Cable SMA/SMA or adapter SMA/BNC
Fig. 7−1 Test setup frequency check of local oscillator of RXU subassembly
Ed. 10.07 7−3

AS 680/682 ADS−B
7.1.7.1 Adjustment of SPU/RXU Local Oscillator Frequency

NOTE: Only to be performed with RXU1, Ref. No. 83142 71502.
Tools required: Philips Screw Driver #2, Allan key, Maintenance Adapter, Digital Multimeter, RF−
Generator, non−metallic aligning tool (1 mm blade width)
Perform the following procedure to adjust the frequency (refer to Figs. 7−1, 7−2):
a) Switch off the Ground Station. Remove RF cable from connector RF In.
b) Remove the RXU1 board. Remove shielding top cover (12 screws). Insert the RXU1 again plugged
on a maintenance adapter. Open jumper X3.
d) Set the RF Generator to apply an RF signal of 1090 MHz and P= −80 dBm to the RXU1.
f) Carefully align the frequency of the local oscillator adjusting the trimmer (Fig. 7−2) slightly clock
or counter−clockwise to get a maximum DC voltage reading at the Digital Voltmeter. Use a non−
metallic aligning tool with a blade width of about 1 mm.
g) Switch off the Ground Station.
h) Remove measuring cables. Withdraw RXU1 board from maintenance adapter. Set X3 again.
i) Mount shielding top cover to RXU1 and fix the 12 screws.
j) Remove maintenance adapter.
k) Insert the RXU1 without maintenance adapter and connect RF cable as normal again.
Trimmer
X3
Local Oscillator (VCO)
RXU subassembly, shielding top cover removed
Fig. 7−2 Adjustment of local oscillator frequency of RXU1, location of oscillator and trimmer
7.1.8 Preventive Exchange of the Lithium Battery (SBC)

To back up the system date of the NVRAM and the real time clock in case of a voltage drop, the subas-
sembly SBC contains a Lithium battery in form of a Snaphat lithium battery pack. Lithium batteries
have an extended life time of approx. 10 years depending on the local environment. It ages as a result
of self−discharging. Therefore it is advisable as preventive measure to install a replacement battery
after about five years operation. The Lithium battery has to be replaced by the same battery type. Al-
ways observe the label on the battery. Other types of lithium batteries are not approved by Thales.
7−4 Ed. 10.07

ADS−B AS 680/682
WARNING
Do not recharge, disassemble, heat above 100 °C or incinerate the lithium cell. Do not
short circuit, or solder directly on the cell. Disregard of the norms regarding the use of
lithium batteries may cause risk of fire, explosion or leaking out of toxic liquid and gas.
Run−down batteries are objects that can pollute the environment and must be disposed
of with proper precautions.
CAUTION
To avoid leakage discharge, never store the "Snaphat" housing on a conductive surface
(such as a dedicated anti−static foam pad used for ESD sensitive devices).
Replace the battery pack as follows (regard also manufacturers COTS documentation):
a) Connect the LCMS with the SBC serial port of GS via the LCMS serial cable (see Fig. 3−3).
b) Boot the LCMS and login as supervisor.
c) Start Minicom by clicking the following keys: right mouse key ? Misc. ? Minicom.
d) Switch the Ground Station OFF and ON again.
e) After you get a new message in the Minicom window press the ENTER"−key within 1 sec. The
COMMAND>" line is shown at the bottom.
f) Type: ENV ;S <Enter> to save the NVRAM contents into the system flash.
g) Switch OFF the Ground Station.
h) Remove the SBC using the unlocked handles left and right. The yellow Snaphat battery is located
near the front panel on the right hand side (see Fig. 7−3).
i) Carefully remove the Snaphat battery from its location. The Snaphat battery in mounted on the
M48T59 device.
j) Insert the new Snaphat battery carefully to its base. The battery is keyed to prevent reverse inser-
tion.
k) Insert the SBC to the SPU subrack and lock with handles.
l) Switch ON the Ground Station.
m)After you get a new message in the Minicom window press the ENTER"−key within 1 sec. The
COMMAND>" line is shown at the bottom.
n) Type: ENV ;C <Enter>
o) Enter new date and UTC time (it is necessary because the RTC contents becomes undefined if the
battery is removed). Type: DATE MM DD hh mm YYYY <Enter>
p) Switch the Ground Station OFF and ON again.
q) Remove the LCMS from the SBC. Battery exchange is now finished.
SBC board
Snaphat battery
MT48T59 device
Fig. 7−3 Removing Snaphat battery pack from SBC
Ed. 10.07 7−5

AS 680/682 ADS−B
7.1.9 Maintenance of UPS Battery Packs
NOTE: Regard the recommendations of the UPS manufacturer (see COTS user manual).
Normally the UPS system does not require maintenance, because it contains no serviceable parts.
If the battery service life (about 3 to 5 years at 25 °C ambient temperature) has been exceeded, the
batteries must be exchanged. Contact Thales ATM for service.
If the battery are to be stored in temperate climatic zones, they should be charged every three months
for 1 to 2 hours. The charging intervals should be shortened to two months at locations subject to
high temperatures.
7−6 Ed. 10.07

ADS−B AS 680/682
7.2 FAULT LOCATION
7.2.1 General
To perform maintenance activities, the user must login at the RCMS or LCMS. Fault detection is pos-
sible down to LRU level (subsystem or selected subassemblies in SPU) to support the replacement
of the failing LRU.
7.2.2 Power Supply, Subsystem Indicators
The BIT of the individual subsystems indicates faulty operating voltages, so that the defective subsys-
tem can be defined and replaced. Before replacing the AC/DC converter (or optional DC/DC conver-
ter) check external power supply fed to the equipment. Before locating a fault, try to define roughly
the defective functional LRU, i.e. the SPU (with RXU, GTS, SPB, SBC), Site Monitor, Data Switch and
UPS. Check also external equipment:
− Antenna and antenna connections,
− Ethernet interface to ground network
− DC or mains (if applicable) power supply cable
A first localization is done by evaluating the Fail or Power indicators (LED) on the various subsystems.
Step Fault A B C
All
Power Supply Power−LED off? Device switched to ON? AC input power available?
If yes, check fuses (also of
mains supply socket strip:
Replace once if blown.
Fault−LED on? Power available? If ok, AC/DC converter or

other subassembly may
cause the fault: replace
the resp. subassembly.
SPU
1 DC/DC conv. Power−LED off? DC switched to ON? DC input power available?
If yes, check fuses:
Fault−LED on? DC power available? If ok, DC/DC converter or

2 AC/DC conv. Power−LED off? AC switched to ON? AC input power available?
(optional) If yes, check fuses:
Fault−LED on? AC power available? If ok, AC/DC converter or

7.2.3 Performing Tests

This section describes recommended test procedures to localise a faulty component presuming fol-
lowing fault characteristics:
− BITE Failure (indication "red") refer to section 7.2.3.1
− No Network Connection refer to section 7.2.3.2
− No Raw Data refer to section 7.2.3.3
− No Asterix Data refer to section 7.2.3.4
Ed. 10.07 7−7

AS 680/682 ADS−B
7.2.3.1 Tests if BITE Failure (red)

7.2.3.1.1 GPS Fault
− If on site: Does the GPS module show a fault (red LED on front panel)?
− If on site: Is the GPS antenna connected?
− If on site: Is a GPS module present at all (GTS, upper left slot)?
− On the TSC ’Groundstation’ page, is ’GPS’ enabled? Is ’Time Synchronisation’ set to ’gps’?
− If on site: Does the GPS module front panel LED show a 1 PPS flash once per second?
− If on site: Does the GPS module front panel LED indicate satellites being tracked (number of green
flashes indicates number of satellites in view). At least 5 satellites are required.
− On the TSC ’GPS’ page, is a ’Type’ and (Software) ’Version’ indicated?
− Does it announce ’GPS Data’ available?
− Is there a ’HPL’ value and the ’No. of Satellites (HPL)’ different to 0?
− Is the current position deviation between declared Ground Station position and measured GPS
position lower than the configured threshold?
− Is the actual time deviation between GPS and system clock lower than the configured threshold?
7.2.3.1.2 Fault in Site Monitor Telegram (own), Site Monitor Bite (own)
− If on site: Is Site Monitor properly connected and active? Site Monitor TX LED flashes at configured
rate.
− If on site: Does the Site Monitor show a fault (red LED on front panel)?
− If on site: Verify Site Monitor Configuration:
Downlink Format DF−18, Unique Mode S Address, Jitter enabled, Repetition interval.
− On the TSC ’Site Monitor’ page, Is the correct ’Telegram Downlink Format’ and the Mode S ’Ad-
dress’ configured for the own Site Monitor?
− Is the ’Expected Repetition Interval’ of the own Site Monitor telegram at least twice as large as the
configured repetition interval of the Site Monitor?
− Is the received signal strength higher than the configured minimum threshold for the own Site Mon-
itor (look at raw data)?
7.2.3.1.3 Fault in the RF Path

− If the own Site Monitor is not received and the own Site Monitor BITE is not ok then the Site Monitor
is faulty.
− If the own Site Monitor is not received, and the own Site Monitor bite is ok and the other Site Monitor
is received, then the cable between own Site Monitor and antenna is broken.
− If the own Site Monitor is not received, and if the own Site Monitor bite is ok and if the other Site
Monitor is not received, then further test is needed:
a) Check if any target is received on the SPB RXDL LED (if on site) or using raw data recording.
b) On the TSC BITE page, verify that the SBC software is correctly running, i.e. all threads are green
(e.g. main thread, base thread, etc.).
c) Activate the loopback telegram test to verify the SPB is working.
7−8 Ed. 10.07

ADS−B AS 680/682
d) Go on site and disable RXU DC output (jumper X3 open) and connect the Site Monitor output
directly to the RXU input.
e) Check own Site Monitor telegram reception to verify RXU is ok.
− If SBC, SPB and RXU are ok, the ADS−B antenna or the LNA or the connecting cable is broken.
7.2.3.2 Tests if no Network Connection

In preparation
7.2.3.2.1 If on Site: Check cables
− Is a straight Ethernet cable connected between main interface and router?
− Is a crossover Ethernet cable connected between auxiliary interface and LCMS?
− The BITE connector on the SPB is for a special non−Ethernet cable to exchange BITE summary
between ground stations on site.
7.2.3.2.2 Check Network Connection
− Login into the Ground Station: either from the other network connection, if available, or better from
the serial interface (if on site).
− If not possible try the next step below from outside, i.e. the following unit on the network (e.g. the
LCMS).
− Enter the command ping <IP−Address of next unit on network> (this could be e.g. the router
or the LCMS) to see if a connection can be established at all on low protocol level.
− Verify both units belong to the same network (e.g. both units’ interfaces have the same front part
of the IP address (first three numbers), like "192.168.23.4".
At the LCMS, enter the command /sbin/ifconfig −a . Look for the Ethernet address in the
first line.
7.2.3.3 Tests if no Raw Data

Any BITE failure? If yes, try looking at more detail in the TSC (see also previous tests).
7.2.3.3.1 Check Output Configuration
− On the TSC ’Network’ page, check that Raw Data ’Output’ is enabled on the affected output port.
− Check that its destination ’IP−Address’/’Port’ is consistent with the intended output interface and
the IP address/port settings of the destination.
7.2.3.3.2 Check Network
See previous tests, refer to section 7.2.3.2.
7.2.3.3.3 Check Reception
− If on site: Is there any valid Mode S input signal at all? RXDL LED on SPB active? Can at least the
Site Monitor be received (provided it is properly connected and active it should always be received,
see previous tests)?
− If on site, check cables: Is an ADS−B antenna cable connected between SPU/RXU and the Ex-
change Panel, between the Exchange Panel and the AAU and between the AAU and the antenna?
− If on site, try recording raw data if another network interface is available. Are there any messages
at all?
Ed. 10.07 7−9

AS 680/682 ADS−B
− On the TSC ’Telegram Filter’ page, verify that at least DF−17,−18 and −19 are enabled. For the
test enable all formats (switch all on, set values).
− On the TSC ’Telegram Check’ page, make sure that the required minimum ’Signal Amplitude Level’
is set to 0x00.
7.2.3.4 Tests if no Asterix Data

Any BITE failure? If yes, try looking at more detail in the TSC (see also previous tests).
7.2.3.4.1 Check Output Configuration
− On the TSC ’Network’ page, check that Asterix data ’Output’ is enabled on the affected output port.
− Check that its destination IP address/Port is consistent with the intended output interface and the
IP address/port settings of the destination.
7.2.3.4.2 Check Network

See previous test, refer to section 7.2.3.2.
7.2.3.4.3 Check Test Target Report Output

− On the TSC ’Site Monitor’ page, verify that a test target report is output regularly (e.g. ’Report Trig-
ger’ condition set to ’biteNoError’, ’Report Interval’ set to 1s). Make sure that there is no BITE error
(RED). A test target report will be output.
− With the test target report activated, verify on the ’ADSB’ page that the Asterix ’Data Rate’ is greater
than zero.
− On the TSC ’Groundstation’ page, verify SIC/SAC settings to the expected value of the receiving
element (e.g. T’SD, ARC, ATC−Center).
− On the ’Groundstation’ page, verify the ’Time Synchronisation’ is set to GPS if a GPS is available,
or to NTP with a correctly configured ’NTP Server IP−Address’ if an NTP server is available (with
incorrect timing, applications like ATC−Center systems reject Asterix target reports).
7.2.3.4.4 Check Raw Data Reception

− See also previous test.
− Try recording raw data if a network interface is available.
Are there any messages DF−17, −18 or −19?
− On the TSC ’Telegram Filter’ page, verify that ADS−B formats DF−17, −18 and −19 are enabled.
− On the TSC ’ADSB Filter’ page, make sure that all filters are set as insensitive as possible (i.e. wide
open, ’both’, ’Cover Range’ = −1, altitude filters ’Max./Min. Flight Levels’ to 1500 and −15).
7−10 Ed. 10.07

ADS−B AS 682
7.3 REPAIR
WARNING
Before replacing a subsystem connected to mains, shut down mains supply. The supply
voltage (AC or DC) must always be disconnected before removing or installing subsys-
tems, fuses or cables.
CAUTION
Take care when removing or inserting cables to the MicroSubD connectors. Fixing screws
of the SubD cable connectors have to be tightened to the SubD connector bolts with max.
40 Ncm. Use a torque wrench.
7.3.1 Replacing Subsystems and individual Subassemblies (LRU)
Tools required: Oscilloscope, Digital Voltmeter, measurement cables and Maintenance Adapter for
RXU adjustment; screw driver set.
The relevant subsystems must be de−energized before removing or installing:
a) Switch off DC of the respective subsystem: Signal Processing Unit or Site Monitor. If AC is option-
ally used: Switch off the mains switch. Remove the DC or mains or DC supply cable.
The SM, UPS and Data Switch are replaced completely. The following steps are a general procedure
for all LRU’s. Special procedures are described in 7.3.3.
a) First remove the concerned cables carefully from the subsystem or subassembly to be changed.
b) All subassemblies of the SPU can be removed easily: Unfasten the captive screws holding the sub-
assembly. Press corrugated locker button in the extraction handle (RXU, SBC, SPB both sides)
and move the extraction handles simultaneously to withdraw the respective board as shown in Fig.
7−4. Exception DC/DC converter: additionally loosen the screws fixing the front panel to the 19"
rack. The GTS DG14 (or B12) and the AC/DC (or DC/DC) converter own only one extraction han-
dle. Pull the subassembly carefully out from the subrack.
c) To insert a subassembly gently push it into its position in the subrack and lock to the subrack with
the extraction handles. Finally fasten captive screws again.
Â
Power Supply Air Inlet Dust Filter captive screws (example) Fan Unit
Â
Â
GTS
DG14
I
Â
Â
Â
SPB
Fault
Â
Power 0
Â
RXU
withdraw
Â corrugated locker button withdraw
extraction handle
SPU housing front subassembly
Fig. 7−4 Removing subassemblies of SPU
Ed. 10.07 7−11

AS 682 ADS−B
d) Connect the pertinent cable connectors carefully to the subsystem:
Tighten all screws of the SubD cable connectors with max. 40 Ncm. Use a torque wrench tool.
e) Check that all the cables have been connected correctly before switching the subsystem on again.
7.3.1.1 Replacing Fuses

See Fig. 7−5.
Blown fuses are allowed to be replaced only once. If the fuses blow again, check equipment for the
reason, e.g. short circuits. The exchangeable fuses are located within the DC or AC connector at the
rear of the SPU or SM housing.
a) Switch off respective equipment: SPU or SM.
b) Remove power supply cable from DC or AC connector.
c) Open hinged cover carefully with suitable auxiliary tool, e.g. small screw driver blade or knife.
d) Withdraw fuseholder and replace fuses. If small fuses (20x20x5 mm) are used regard position.
e) Insert fuseholder up to the stop, close hinged cover, connect supply cable again.
f) Switch on equipment.
rear of SPU or SM open here rear of SPU or SM Fuse (2x)
Fuse holder 1/4x1−1/4"
hinged cover
Fuse holder front
hinged cover
supply cable
position of small fuses
leave 1. clamp open
Fig. 7−5 Replacing fuses
7.3.2 Replacing Cables

The relevant subsystems must be de−energized before removing or installing:
a) Switch off DC of the respective Subsystem: Signal Processing Unit or Site Monitor. If AC is option-
ally used: Switch off the mains switch. Remove the DC or mains or DC supply cable.
b) Carefully remove cable connectors from the respective sockets.
c) Connect new cable carefully to the pertinent connector of the subsystem:
Tighten the screws of the SubD cable connector with max. 40 Ncm. Use a torque wrench tool.
d) Check that the cables have been connected correctly before switching the subsystem on again.
7.3.3 Specific Procedure for Subassemblies of SPU

7.3.3.1 Exchange of RXU
See Fig. 7−4.
Tools required:
Philips screw driver #2, Oscilloscope, measurement cables, Maintenance Adapter, Digital Voltmeter
a) Connect the maintenance Laptop (LCMS) with the crossover Ethernet cable to the SBC auxiliary
port located on the GTS.
7−12 Ed. 10.07

ADS−B AS 682
b) Open the TSC with focus to this Ground Station, refresh all pages. Change to the ’BITE’ page and
enable Maintenance Mode.
c) Switch off the Ground Station.
d) Disconnect the main Ethernet Interface network cable from the SBC. Disconnect the RF cable from
the RXU.
e) Unfasten the two grips with the small locker button. Extract the RXU by gently pressing the extrac-
tion handles outwards.
f) Carefully insert the Maintenance Adapter (optional, Ref. No. xxxxx xxxxx) into the slides.
g) Insert a new RXU into the Maintenance Adapter.
h) Connect the RF cable to the RXU input (RF in). Connect the oscilloscope to the RXU monitor output
(Monitor out).
i) Switch on the Ground Station.
j) Select DIP switch settings (refer 7.3.8) to a value that the noise peaks shown by the oscilloscope
is just below 300 mV (MTL). Refer also to procedure and figures described already in section 3.2.6.
k) Switch off the Ground Station.
l) Disconnect the RF cable. Disconnect the oscilloscope.
m)Perform check. RXU1, Ref. No. 83142 71502, only: if need be, adjustment of local oscillator fre-
quency according section 7.1.7.
n) Remove the RXU. Remove the Maintenance Adapter.
o) Carefully insert the new RXU into the slide. Verify that the handles lock into the side railings.
p) Connect the RF cable to the new RXU (RF in). Connect the oscilloscope to the RXU monitor output.
q) Switch on the Ground Station. Verify the noise level being below MTL.
r) Refresh the TSC. Verify that all parameter settings are as intended. Verify that all BITE tests are ok.
s) Reconnect the Ground Station main Ethernet interface located on the SBC to the ground network.
t) Disconnect the LCMS from the Ground Station. Fasten the two screws.
7.3.3.2 Exchange of SPB

Tools required: Philips screw driver #2
d) Disconnect the main Ethernet interface cable to the ground network located on the SBC. Discon-
nect the BITE crossover cable to the other Ground Station. Disconnect the BITE signal cable from
the Site Monitor .
e) Unfasten the two screws holding the SPB. Unfasten the two grips with the small locker button.
f) Extract the SPB by gently pressing the extraction handles outwards.
g) Carefully insert a new SPB into the slide. Verify that the handles lock into the side railings.
Ed. 10.07 7−13

AS 682 ADS−B
h) Reconnect the BITE crossover cable to the other Ground Station. Reconnect the BITE signal cable
from the Site Monitor.
i) Switch on the Ground Station.
j) Refresh the TSC and verify that all parameter settings are as intended. Verify that all BITE tests are
ok.
k) On the BITE page, disable Maintenance Mode.
l) Reconnect the Ground Station main Ethernet interface located on the SBC to the ground network.
m)Disconnect the LCMS from the Ground Station.
n) Fasten the two screws holding the SPB.
7.3.3.3 Exchange of SBC

Tools required: Philips screw driver #2, Maintenance Laptop, serial cable,crossover Ethernet cable
d) Disconnect the main Ethernet Interface network cable from the SBC.
e) Unfasten the two screws holding the SBC. Extract the SBC by gently pressing the extraction han-
dles outwards.
f) Carefully insert a new SBC into the slide. Verify that the handles lock into the side railings.
g) Switch on the Ground Station.
h) Change TSC focus to the Default Ground Station, refresh all pages. Change to the Software Page.
i) Upload the latest Kernel as Kernel 2.
j) Upload the latest Application as Application 2.
k) Upload the latest Configuration File (site−independent parameters only).
l) Upload the NUC conversion table.
m)Set site specific parameters including the Ground Station’s correct IP−Address, position, etc. to
the intended values.
n) Refresh the TSC and verify that all parameter settings are as intended. Verify that all BITE tests are
ok.
o) Reboot the Ground Station.
p) Set the TSC focus to the actual Ground Station, refresh all parameters.
q) Verify that all parameter settings are as intended. Verify that all BITE tests are ok.
r) Change to the ’BITE’ page and disable Maintenance Mode.
s) Reconnect the Ground Station main Ethernet interface located on the SBC to the ground network.
t) Disconnect the LCMS from the Ground Station.
u) Fasten the two screws holding the SBC.
7−14 Ed. 10.07

ADS−B AS 682
7.3.3.4 Exchange of GTS
d) Disconnect the main Ethernet Interface network cable from the SBC. Disconnect the GPS antenna
cable.
e) Unfasten the four screws fixing the GTS. Unfasten the grip with the small locker button. Extract the
GTS by gently pressing the extraction handle outwards.
f) Carefully insert a new GTS into the slide. Verify that the handle locks into the side railing.
g) Reconnect the GPS antenna cable.
h) Switch on the Ground Station.
i) Refresh the TSC and verify that all parameter settings are as intended. Verify that all BITE tests are
ok.
j) Change to the ’BITE’ page and disable Maintenance Mode.
k) Reconnect the Ground Station main Ethernet interface located on the SBC to the ground network.
l) Disconnect the LCMS from the Ground Station.
m)Fasten the four screws fixing the GTS.
7.3.3.5 Exchange of Power Supply
d) Disconnect the main Ethernet Interface network cable from the SBC. Disconnect the power chord
at the rear.
e) Unfasten the four screws fixing the Power Supply. Unfasten the grip with the small locker button.
Extract the Power Supply by gently pressing the extraction handle outwards.
f) Carefully insert a new Power Supply into the slide. Verify that the handle locks into the side railing.
g) Reconnect the power chord at the rear.
h) Switch on the Ground Station.
i) Refresh the TSC and verify that all parameter settings are as intended. Verify that all BITE tests are
ok. Change to the ’BITE’ page and disable Maintenance Mode.
j) Reconnect the Ground Station main Ethernet interface located on the SBC to the ground network.
k) Disconnect the LCMS from the Ground Station.
l) Fasten the four screws fixing the Power Supply.
Ed. 10.07 7−15

AS 682 ADS−B
7.3.3.6 Exchange of Fan Unit

a) Switch off DC of the Ground Station.
b) Unfasten the four captive screws fixing the Fan unit.
c) Extract the Fan Unit carefully from the 19" subrack until the DC supply cable with the connector
is visible. Press the lock of the fan supply cable connector and remove it from the cable to the mo-
therboard. Recommended: Clean the air outlet.
d) Connect the connector of the spare fan unit to the supply cable to the motherboard until it locks.
e) Carefully insert the new Fan Unit into the slide. Take care not squeeze the supply cable. Fasten
the four captive screws.
f) Switch on DC of the Ground Station.
7.3.4 Exchange of Site Monitor

Tools required: Philips Screw Driver #5, LCMS, serial cable.
a) Switch off the Site Monitor.
b) Disconnect the power chord at the rear. Disconnect the RF cable and the 50 ohm load (or two RF
cables if applicable) at the Site Monitor rear. Disconnect the BITE cable.
c) Carefully unfasten the four screws holding the Site Monitor within the rack in order not let it drop
to the ground .
d) Install a new Site Monitor into the rack and fasten the four screws.
e) Reconnect the power chord to the Site Monitor.
f) Connect the LCMS to the maintenance port of the Site Monitor using the serial cable.
g) Open a terminal window on the LCMS.
h) Enter the command minicom
i) Verify the Site Monitor Status entering the command Getall
j) Adjust the Site Monitor settings as needed using the Set… commands.
k) Verify the correct ICAO address setting.
l) Make all changes permanent by entering the command saveall.
m) Power Cycle the Site Monitor.
n) Verify the Site Monitor Status entering the command Getall.
o) Disconnect the LCMS.
p) Reconnect the BITE cable.
q) Reconnect the RF cable and the 50 ohm load (or two RF cables if applicable) at the Site Monitor
rear.
7.3.5 Exchange of UPS

In preparation
7.3.6 Exchange of Data Switch

In preparation
7−16 Ed. 10.07

ADS−B AS 682
7.3.7 Exchange of Peripheral Equipment
Due to the fact that the installation and mounting of the LNA, ADS−B RX antenna and GPS antenna
depend on local environment which may change from site to site the following is a general instruction
how to proceed. In detail local procedures have to be observed.
7.3.7.1 Exchange of AAU (LNA Housing)

a) Switch off the Ground Station.
b) Remove cables.
c) Lift (1) the AAU and remove (2) it from the mounting support (see Fig. 7−6).
d) Remove the weather protection. Replace the LNA−housing. Mount the weather protection again.
e) Hang the AAU to the mounting support again and lock on downwards.
f) Reconnect the cables.
g) Switch on the Ground Station.
LNA−housing Mast
Mounting support
weather protection
2) fastening detail
1)
Fastening screw
of LNA−housing
Mast mounting LNA−housing
Fig. 7−6 Removing/mounting of LNA−housing (AAU)
7.3.7.2 Exchange of ADS−B RX Antenna

b) Remove the RF cables.
c) Replace the ADS−B RX antenna.
d) Reconnect the RF cables.
7.3.7.3 Exchange of GPS Antenna

b) Remove the RF cable.
c) Replace the GPS antenna.
d) Reconnect the RF cables.
Ed. 10.07 7−17

AS 682 ADS−B
7−18 Ed. 10.07

ADS−B AS 682
7.3.8 List of DIP−FIX−Switches and Jumpers
7.3.8.1 General
Some of the SPU subassemblies have DIP−FIX switches or jumpers on the component side. The
jumpers act either as on/off switches or as changeover switches. The DIP−FIX switches and jumpers
can be set or placed to particular positions in order to adapt universal subassemblies to specific
equipment types.
NOTE: Before installing a spare subassembly, check and correct, if necessary, the position of the
DIP−FIX switches and jumpers.
Overview of subassemblies containing DIP−FIX switches and jumpers:
No. Subassembly Short name Reference number

1a Receiver Unit RXU1 83142 71502
1b Receiver Unit RXU2 83142 71503
2 Signal Processing Board SPB 83142 71300
3 VMEbus−Backplane − 58142 30210
Ed. 10.07 7−19

AS 682 ADS−B
SW2
ON
1
2 3
4
Local Oscillator
X5
X3
open set
1a Receiver Unit (RXU) 83142 71502 1 of 2
7−20 Ed. 10.07

ADS−B AS 682
JUMPER POSITION DEFINITION REMARKS

X3 set 12 VDC to ADS−B RX antenna enabled default
open 12 VDC to ADS−B RX antenna disabled −
X5 set Setting of attenuation 0 dB default
open Setting of attenuation −15 dB −
SWITCH POSITION DEFINITION REMARKS
SW2 SW2 is used to adjust the DC offset of the
RXU output signal. The offset value can be
set in 16 combinations setting switches 1 to
4. Basic value is 0 mV (all open), maximum
value is 750 mV (all closed, "ON").
The individual values are:
/1 to /4 all open 0 mV Default setting
/1 if closed 50 mV add to other switch settings
1 Receiver Unit (RXU) 83142 71502 2 of 2

NOTE: Jumper X3 needs to be removed when the RXU is intended to be used without the AAU, or other equipment is connected to it.
If the RXU should be operated without AAU, a separate dedicated 1090 MHz bandpass filter is needed.
Ed. 10.07 7−21

AS 682 ADS−B
Board Error red

H2
ON
1
2 3
Offset setting
4
SW1
Offset setting 1 2
fixed/adjustable 3 4
X2
MONITOROUt
J6
Video RF
Test
RF IN
AAU supply green

H1
X1
open set
1b Receiver Unit 2 (RXU2) 83142 71503 1 of 2
7−22 Ed. 10.07

ADS−B AS 682

X1 set 12 VDC to ADS−B RX antenna enabled −
open 12 VDC to ADS−B RX antenna disabled default setting
X2 1−2 Mean Noise Offset (MNO): +400 mV ±50 mV default setting
3−4 Mean Noise Offset (MNO): 0 mV ±50 mV Test purpose
SWITCH POSITION DEFINITION REMARKS
SW1 SW1 is used to adjust the DC offset of the Adjustable DC offset, if
RXU2 output signal. The offset can be ad- jumper X2 is set to 1−2
justed in steps with SW1, 1...4. This reduces
the MNO value resulting from X2 setting 1−2
(approx. 400 mV) to the required value of
approx. 300 mV. The basic setting is −0 mV
(all open), maximum value is −750 mV (all
closed, "ON"). The individual values are:
/1 to /4 all open (MNO) − 0 mV Default setting

/1 if closed (MNO) − 50 mV add to other switch settings
1b Receiver Unit 2 (RXU2) 83142 71503 2 of 2
NOTE: Jumper X1 needs to be removed when the RXU is intended to be used without the AAU, or other equipment is connected to it.
If the RXU should be operated without AAU, a separate dedicated 1090 MHz bandpass filter is needed.
Ed. 10.07 7−23

AS 682 ADS−B
TP14 TP13
TP7
TP6
open set
2 Signal Processing Board (SPB) 83142 71301 1 of 2
7−24 Ed. 10.07

ADS−B AS 682

TP6 set Analog IN to A/D converter disabled factory use, test purposes
open Analog IN to A/D converter enabled default setting
TP7 set TOA Trigger output disabled factory use, test purposes
open TOA Trigger output enabled default setting
TP13 set RX IRQ enabled default setting
open RX IRQ disabled factory use, test purposes
TP14 set TX IRQ enabled default setting
open TX IRQ disabled factory use, test purposes
2 Signal Processing Board (SPB) 83142 71301 2 of 2
Ed. 10.07 7−25

AS 682 ADS−B
1 2 3
GND
X300
L
4 5 6
+5V P A
N
PE
−12V GND
Fan
+12V GND
Fan 1 2 3
1 X301
X1 2 +3.3V 4 5 6
3
P A
+5V Stby
open set VMEbus Backplane Power Supply Backplane

X300, 301 1−2, 4−5 − default setting
2−3, 5−6 − −
X1 1−2 Fan is used without tacho generator −
2−3 Fan is used with tacho generator default setting

3 VMEbus Backplane 58142 30210 1 of 1
7−26 Ed. 10.07

ADS−B AS 680/682
Description, Operation and Maintenance Basic Installation LCMS/RCMS
CHAPTER 8
BASIC INSTALLATION OF LCMS AND RCMS
8.1 SCOPE
This chapter describes the installation of the Linux operating system on the LCMS and the RCMS
and the installation of the application software. After the basic installation another section describes
specific LCMS and RCMS installation and configuration processes.
The package for the basic installation comprises 3 CD/DVD:

S the operating system software, i.e. KANGAROO 6,
S the ADS−B application software, i.e. ADS−B Software, and
S the Configuration software.
8.2 INSTALLATION OF KANGAROO 6

Kangaroo 6 is a customized Linux operating system based on the Fedora Core distribution. The instal-
lation generates new partitions on the hard disk.
CAUTION
If there are data on the hard disk you want to keep, create a backup before installing the
RCMS/LCMS as this will delete all data on the harddisk.
8.2.1 Preparation
First plug−in the AC−power switch of the RCMS PC and of the screens, resp. of the LCMS laptop.
Load the Kangaroo 6 CD/DVD. The installation starts by booting from DVD (see Fig. 8−1).
Fig. 8−1 Boot sequence (example)
Ed. 10.07 8−1

AS 680/682 ADS−B
Basic Installation LCMS/RCMS Description, Operation and Maintenance
NOTE: To make sure that the computer is booting from the DVD/CD media, check the BIOS set-
tings of the LCMS/RCMS. Fig. 8−2 shows an example of a typical BIOS setup.
Fig. 8−2 BIOS settings (example)
8.2.2 Start Installation
After booting from the Kangaroo 6 CD/DVD, select which type of host you want to install (see also
Fig. 8−3):
− To install an RCMS, enter ’rcms’ at the ’boot’ prompt and press the <ENTER> button.
− To install an LCMS, enter ’lcms’ at the ’boot’ prompt and press the <ENTER> button.
Fig. 8−3 Host installation (example)
8−2 Ed. 10.07

ADS−B AS 680/682
8.2.3 Installation
NOTE: Depending on the local hardware configuration and requirements, specific operating sy-
stem parameters have to be set.
For the basic installation of Kangaroo 6 you have to configure the keyboard layout (see Fig. 8−4).
Select the type ’US’ for the RCMS keyboard, and the type ’UK’ for the LCMS keyboard.
Fig. 8−4 Configuration of ’Keyboard Type’ (example)
After selecting the keyboard type, the installation process will launch automatically (see Fig. 8−5).
Fig. 8−5 Start of installation process (example)
8.2.4 Reboot
After the installation of Kangaroo, the computer will be rebooted automatically.
NOTE: Please make sure that there is no DVD/CD in the drive.
Ed. 10.07 8−3

AS 680/682 ADS−B
8−4 Ed. 10.07

ADS−B AS 680/682
8.3 POST INSTALLATION
After the installation of the operating system (Kangaroo 6) the host boots up to the ’Setup Agent’ ap-
plication (see Fig. 8−6). The system can be reconfigured with the specific software tools at any time.
NOTE: With the ’Setup Agent’ window several final system configuration steps will be carry out.
Fig. 8−6 ’Setup Agent’ main window (example)
Press the ’Forward’ button to proceed to the first step, which are is the network setup (see following
section 8.3.1). Fig. 8−8 shows, as an example, how the network parameters can be configured.
8.3.1 Network Setup

Specific configuration changes have to be made by pressing the ’Change Network Configuration’ but-
ton. For clarification, ask your network administrator regarding the network parameters.
Fig. 8−7 Window ’Network Setup’ (example)
Ed. 10.07 8−5

AS 680/682 ADS−B
After clicking on the button ’Change Network Configuration’ The window ’Network Configuration ap-
pears showing the page ’Devices’ (see Fig. 8−8).
Fig. 8−8 Window ’Network Configuration’, page ’Devices’ (example)
After double−click on eth0", the window ’Ethernet Device’ appears (see Fig. 8−9).
Fig. 8−9 Window ’Ethernet Device’ (example)
Enter the convenient values (IP addresses): these values are given by the administrator (customer).
Confirm the settings ’OK’. The window ’Ethernet Device’ is closed automatically.
8−6 Ed. 10.07

ADS−B AS 680/682
Then select the page ’DNS’. The following window (Fig. 8−10) appears.
Fig. 8−10 Window ’Network Configuration’, page ’DNS’ (example)
Set parameter ’Hostname’ to e.g. RCMS" or LCMS". Select menu ’File’, submenu ’Save’. Confirm
the saving by clicking on button ’Yes’ within the appearing confirmation window.
Another window appears (see Fig. 8−11).
Fig. 8−11 Information window after saving the network setup (example)
Click on button ’OK’ to continue.
Fig. 8−12 Window ’Network Setup’ (example)
Ed. 10.07 8−7

AS 680/682 ADS−B
Click on button ’Forward’, the following window ’Additional CDs’ appears (see Fig. 8−13). The win-
dow ’Additional CDs’ enables the user to install further software from CD/DVD.
Fig. 8−13 Window ’Additional CDs’ (example)
Section 8.3.2 describes how to install the ADS−B applications from the ADS−B software CD/DVD
(e.g. ’ADSB_2.7’). Section 8.3.3 describes how to install the ADS−B configuration software from the
configuration CD/DVD (e.g. ’LA−REUNION_0.2’)
8−8 Ed. 10.07

ADS−B AS 680/682
8.3.2 Installation of ADS−B Software
Insert the ADS−B Software CD/DVD and press the ’Install’ button. The window ’Add/Remove Pack-
ages’ appears (see Figure 8−14).
Fig. 8−14 Window ’Add/Remove Packages’ for ADS−B software installation (example)
Click on button ’Forward’, the list to select the equipment where to install the software appears (see
Fig. 8−15).
NOTE: When selecting either ’LCMS’ or ’RCMS’, a short description of the just selected equip-
ment is given in the information box below the list.
Fig. 8−15 Window ’Add/Remove Packages’, select equipment and SW for installation (example)
NOTE: The procedure to install the ADS−B software on different equipment (i.e. ’RCMS’ or
’LCMS’) is very similar. Therefore only the SW installation on the RCMS is described in
detail in the following. Differences for an LCMS equipment are given by means of notes.
Ed. 10.07 8−9

AS 680/682 ADS−B
Select ’RCMS’ in the right equipment list of the Window ’Add/Remove Packages’; then, on the left,
the software ’ADS−B applications’. Click on button ’Forward’ to continue, the following window (Fig.
8−16) appears.
Fig. 8−16 Window ’Add/Remove Packages’, RCMS list of SW packages (example)
Select all of the 4 ADS−B application SW packages (’ADS−B Tools’, ’Master Technical System Con-
trol’, ’Software for ADS−B Groundstation’, ’Technical System Control’). The box below the list gives
a short description of the SW packages just selected in the list (e.g. in Fig. 8−16: ’ADS−B Tools’).
NOTE: For LCMS SW installation the package ’Master Technical System Control’ hasn’t to be
selected.
Click on button ’Forward’ to continue, the ’Information Overview’ window appears (see Fig. 8−17).
Fig. 8−17 Window ’Installation Overview’, list of installing SW (example)
8−10 Ed. 10.07

ADS−B AS 680/682
Click on button ’Forward’ to continue, the following information window appears (see Fig. 8−18).
Fig. 8−18 Window with information on status of SW installation process (example)
If all selected SW packages are installed, the following window appears (see Fig. 8−19).
Fig. 8−19 Window after successfully installed ADS−B software (example)
Click on button ’Close’ to return to the window ’Additional CDs’ (see Fig. 8−20). Remove the ADS−B
(application) Software CD/DVD from the CD/DVD drive.
Ed. 10.07 8−11

AS 680/682 ADS−B
8.3.3 Installation of ADS−B Configuration Software
Fig. 8−20 Window ’Additional CDs’ for further SW installation (example)
Insert the ADS−B configuration software CD/DVD and press the ’Install’ button in the ’Additional CDs’
window (see Fig. 8−20). The following window ’Add/Remove Packages’ appears (see Figure 8−21).
Fig. 8−21 Window ’Add/Remove Packages’ for ADS−B configuration SW installation (example)
Click on button ’Forward’ to continue; the window with the list of software packages to install appears
(example see Fig. 8−22).
Fig. 8−22 Window ’Add/Remove Packages’, select configuration SW for installation (example)
Click on button ’Optional packages’, the list of software packages appears (see Fig. 8−23).
8−12 Ed. 10.07

ADS−B AS 680/682
Fig. 8−23 Window with list of packages (example)

Select the package corresponding to the site and click on button ’Close. The window with the list of
packages is closed. Click on button ’Forward’ in the ’Add/Remove Packages’ window to continue.
The following window ’Installation Overview’ appears (example see Fig. 8−24).
Fig. 8−24 Window ’Installation Overview’ with installing ADS−B configuration files (example)
NOTE: If the wrong configurationhas been selected, click on button ’Back’ to select again.
Click on button ’Forward’ to continue. If the selected configuration is installed, the following window
appears (see Fig. 8−25).
Fig. 8−25 Window successfully installed configuration SW (example)
Click on button ’Close’ to return to the window ’Additional CDs’ (see Fig. 8−26).
Ed. 10.07 8−13

AS 680/682 ADS−B
Fig. 8−26 Window ’Additional CDs’ to continue/finish SW installation process (example)
8.3.4 Finishing Software Installation
Click on button ’Finish’ in the window ’Additional CDs’ (see Fig. 8−26) to finish the software installa-
tion procedure. Remove the ADS−B configuration CD/DVD from the CD/DVD drive.
Reboot the system. After the login procedure (see section 8.4) the configured system is ready for ope-
ration.
8−14 Ed. 10.07

ADS−B AS 680/682
8.4 LOGIN PROCEDURE
After rebooting the system, the Kangaroo login window appears (see Fig. 8−27). Enter for ’Username’
either "supervisor" or "monitor". Press keyboard key <Enter> to continue.
Fig. 8−27 Kangaroo login window to enter username (example)
Enter the ’Password’ (for ’supervisor’: "12super21", for ’monitor’: "12mon21"), see Fig. 8−28. Press
key <Enter> to confirm.
Fig. 8−28 Kangaroo login window to enter password (example)
Now the configured system is ready for operation.
Ed. 10.07 8−15

AS 680/682 ADS−B
8.5 ADDITIONAL INSTALLATION INFORMATION

8.5.1 User/Groups
The applications on the LCMS/RCMS require the groups ’supervisor’ and ’monitor’. The installation
of the lcms/rcms software creates these groups. Further, the default users ’supervisor’ and ’monitor’
are created automatically.
If the customer wants to create further users, this section describes the creation of these users, if there
is any need to perform it manually. To create further accounts the following procedures can be used.
If not already existing, create the groups monitor and supervisor:

/usr/sbin/groupadd −f monitor
/usr/sbin/groupadd −f supervisor
If not already done, change/create user accounts to have at least the default accounts according the
following table:
Machine Account Group
LCMS monitor users, monitor
LCMS supervisor users, supervisor, uucp
RCMS monitor users, monitor
RCMS supervisor users, supervisor
E.g.: To create a user ‘smith’ with monitor permission the following commands can be used:
/usr/sbin/useradd −g users −G monitor smith
/usr/sbin/passwd smith
/usr/sbin/usermod −G monitor,uucp monitor
8.5.2 Xfce Setup
Every user has to use the desktop ’Xfce4’. Execute the following command by each user:
Login as ’user’:
switchdesk xfce
After a new graphical login the ’Xfce4’ desktop should be active.
8.5.3 Data Partition
The partition which is mounted under /local should be used to store data files.
NOTE: It is not recommended to store data files in the /tmp directory.
8−16 Ed. 10.07

ADS−B AS 680/682
8.5.4 USB Memory Stick Handling
Normally, the kernel recognizes the usage of an USB memory stick automatically. The user shall
mount or dismount the memory stick like other interface devices.
Insert the USB memory stick. An icon with its device name (example in Fig. 8−29 <sda1>) appears
on the desktop representing the device. A menu can be opened by right−mouse clicking on the icon,
which enables the user to mount the device through selecting ’Mount Volume’ (see Fig. 8−29).
NOTE: The automatic detection takes a few seconds.
Before pulling out the USB memory stick, unmount the device using the command ’Unmount Volume’
of the device menu.
Fig. 8−29 Device menu for memory stick handling (example)
8.5.5 Network Time Protocol (NTP)
It is recommended to run the NTP service on the RCMS host. A correct working NTP service ensures
that the RCMS has a correct system time.
The NTP package is installed on the RCMS by default. The NTP service has to be configured concern-
ing the network parameters. (Please ask your network administrator for details.)
To start/stop the NTP service you can use the tool system−config−services. The configuration file
is located in /etc/ntp.conf. Further information about NTP can be obtained from the online docu-
mentation which is located in /usr/share/doc/ntp−x.y−z/index.html.
Ed. 10.07 8−17

AS 680/682 ADS−B
8−18 Ed. 10.07

Ads-B As680 Thales

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ads-B As680 Thales

Uploaded by

Copyright:

Available Formats

Reference No.

ADS−B Ground Station

Description, Operation and Maintenance

As for details, the electrical and mechanical information given in the

All rights reserved

ADS–B Ground Station AS 680/682

The Description, Operation and Maintenance Manual of the

Part Technical Manuals Code No.

PART CONTENTS CODE NO.

Cautions call attention to methods Warnings call attention to methods,

NOTE or REMARK : For more information about operations.

Table of effective pages

Pages Ed. Remarks

Section Title Page

CHAPTER 1 SYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−1

CHAPTER 2 SUBSYSTEM DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−1

2.1.4.6 Fan Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−12

CHAPTER 3 INSTALLATION AND SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−1

3.1.6.5 Performing the Outdoor Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3−10

Ed. 10.07 III

CHAPTER 4 USE OF LCMS/RCMS APPLICATION SOFTWARE . . . . . . . . . . . . . . . . . . . . . . 4−1

4.4 ADS−B TOOLS: TECHNICAL SITUATION DISPLAY (TSD) . . . . . . . . . . . . . . . 4−17

4.5.5.2 Addition and Deletion of List Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−40

4.6.3 ADS−B Raw Data Record Tool (RRC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−60

Ed. 10.07 VII

4.6.7 Replay Asterix Data Tool (ARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−81

CHAPTER 5 SUPERVISOR OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−1

VIII Ed. 10.07

5.4.3.4 Loop Back Telegram Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5−14

7.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−1

7.3.2 Replacing Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7−12

CHAPTER 8 BASIC INSTALLATION OF LCMS AND RCMS . . . . . . . . . . . . . . . . . . . . . . . . . . 8−1

XII Ed. 10.07

8.5.4 USB Memory Stick Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−17

Ed. 10.07 XIII

XIV Ed. 10.07

Fig. 1−1 System overview ADS−B, examplary configuration . . . . . . . . . . . . . . . . . . . . . 1−1

Fig.−No. Title Page

Fig. 2−29 LCMS subsystem tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2−24

XVI Ed. 10.07

Fig. 4−6 MTSC, Event window on screen 1 (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−7

Ed. 10.07 XVII

Fig.−No. Title Page

Fig. 4−39 TSD, ’Selected localisation’ panel (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−25

XVIII Ed. 10.07

Fig. 4−73 Parameters Delay (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−47

Ed. 10.07 XIX

Fig.−No. Title Page

Fig. 4−107 ARC, page ’Filter’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4−80

Fig. 5−30 Extract of a FOM/PA Restriction Table file (example) . . . . . . . . . . . . . . . . . . . . 5−36

Ed. 10.07 XXI

Fig.−No. Title Page

Fig. 8−7 Window ’Network Setup’ (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8−5

XXII Ed. 10.07

AAU Antenna Amplifier Unit

BITE Built−In Test Equipment

HPL Horizontal Protection Level

I/O Input / Output

KB Kilo Byte (1024 bit)

LAN Local Area Network

Ed. 10.07 AV−1

RAC Raw data ASTERIX Converter tool

SAC System Area Code