RCSE 443: Remote Control and Status Equipment

Reference No.
83140 55322
RCSE 443
Remote Control and

Status Equipment
Technical Manual
Equipment Description
Operation
As for details, the electrical and mechanical information given in the

documentation supplied with each equipment prevails
All rights reserved

E 2002
Thales ATM Navigation GmbH
Stuttgart
Printed in Germany
RMMC Navaids 400
Conventional Navaids Documentation Structure
RCSE 443
The equipment documentation comprises:
Part Technical Manuals Code No.

- Equipment Description, Operation 83140 55322
Annex NAV-LCU 443
Volume Drawing Set Code No.

- Delivery List, Parts List, 83051 48440
Schematic Diagrams, Layout Drawings
Ed. 01.02
RMMC RCSE 443
Description and Operation Preliminary Remarks
PRELIMINARY REMARKS
The Technical Manual for the RCSE 443 comprises:
PART CONTENTS REF. No.

- Description and Operation 83140 55322
This Technical Manual describes the equipment in the following chapters:
1 General Description
2 Installation and Initial Setup
3 Operation
4 Detailed Description
5 Maintenance
Annex NAV-LCU 443
Since the Technical Manual cannot include modifications made to circuit details or dimensions as a
result of technical advances, please remember that the technical documentation supplied with the
system is always valid in questions of details. It is possible that drawing numbers referred to in this
description are no longer contained in the enclosed set of drawings, but have been replaced by new
drawings with different numbers (in accordance with the system). Please therefore check, and if necĆ
essary correct, the drawing numbers specified in the manuals on the basis of the delivery lists.
Description and use of the PC User Program will be found in the Technical Manual ADRACS, Code
No. 83140 55324.
MARK SYMBOLS
To get the best out of the navigation systems you should study the contents of this manual carefully.
In particular 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. 01.02 A
RCSE 443 RMMC
Preliminary Remarks Description and Operation
Table of effective pages

Basic edition: 01.02
Pages Ed. Remarks
Title 01.02
A 01.02
B 10.02
I to X 01.02
AV-1 to 8 01.02
1-1 to 42 01.02
2-1 to 20 01.02
2-21 10.02
2-22 to 35 01.02
2-36 10.02
2-37 to 39 01.02
2-40 10.02
3-1 to 7 01.02
3-8 10.02
3-9 to 10 01.02
4-1 01.02
4-2 to 3 10.02
4-4 to 22 01.02
5-1 to 2 01.02
Annex 01.02 NAV-LCU 443
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 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 of careful editing work technical inaccuracies and printing faults cannot be excluded in this publication. Change of text remains reserved without notification.
B Ed. 10.02
RMMC RCSE 443
Description and Operation Table of Contents
TABLE OF CONTENTS
Section Title Page
CHAPTER 1 GENERAL DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2.2 Components of the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2.2.1 Remote Control and Status Equipment (RCSE) . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2.2.2 Remote Control and Monitoring System (RCMS) . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2.2.3 Remote Maintenance Center (RMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2.2.4 Navaids Local Communication Unit (NAV-LCU) . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2.2.5 Remote Maintenance Subsystem (RMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.2.3 Hierarchy of RMMC Remote Control Equipment . . . . . . . . . . . . . . . . . . . . . 1-4
1.2.4 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.2.4.1 Local Remote Control Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.2.4.2 Remote Control and Status Equipment RCSE 443 . . . . . . . . . . . . . . . . . . . . . . 1-6
1.2.4.3 Remote Control and Monitoring System RCMS 443 . . . . . . . . . . . . . . . . . . . . . 1-6
1.2.4.4 Remote Maintenance Center RMC 443 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1.2.4.5 General Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1.3 MECHANICAL DESIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
1.3.1 RCSE: REU with INC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
1.3.2 CTU with RWY-SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
1.4 TECHNICAL DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
1.4.1 General Data REU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
1.4.1.1 Housing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
1.4.1.2 Dimensions and Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
1.4.1.3 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
1.4.1.4 Environmental Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
1.4.1.5 PC Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
1.4.1.6 Modem and Distribution Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
1.4.1.6.1 Dialing Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
1.4.1.6.2 Dedicated-line Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
1.4.1.6.3 Distribution Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Ed. 01.02 I
RCSE 443 RMMC
Table of Contents Description and Operation
Section Title Page
1.4.1.6.4 Supported Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

1.4.1.7 Modem Replacement Unit LGM Extender 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
1.4.2 General data INC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
1.4.2.1 Housing and Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
1.4.2.2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
1.4.2.3 Main Status Indication and Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
1.4.2.4 RCSE Status Indication and Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
1.4.2.5 Detailed Subsystem Status Indication and Control . . . . . . . . . . . . . . . . . . . . . . 1-23
1.4.2.6 Control Facilities for an attached PC with ADRACS User Program . . . . . . . . 1-24
1.4.3 General Data CTU and RWY-SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
1.4.3.1 Housing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
1.4.3.2 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
1.4.3.3 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
1.4.3.4 Subsystem Status Indication (CTU Panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
1.4.3.5 System Status Indication (RWY-SELECT Panel) . . . . . . . . . . . . . . . . . . . . . . . 1-26
1.4.3.6 CTU Switch Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
1.4.3.7 RWY-SELECT Switch Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
1.4.4 Conformity and Licensing Approval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
1.4.5 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
1.4.5.1 Work on the Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
1.4.5.2 Handling electrostatically sensitive Subassemblies . . . . . . . . . . . . . . . . . . . . . 1-27
1.4.5.3 Using Lithium Batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
1.4.5.4 Observation of safety regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
1.5 SHORT DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
1.5.1 General Overview RCSE 443 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
1.5.2 Control Tower Unit CTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
1.5.3 Maintenance Data Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
1.5.4 Principle of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
1.5.4.1 Internal Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
1.5.4.2 External Functions/Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
1.5.4.2.1 Designation and Storage of Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
1.5.4.2.2 Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
1.5.4.3 System Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
1.5.5 Interfaces to local Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
II Ed. 01.02
RMMC RCSE 443
Section Title Page
1.5.5.1 NAVAIDS/ILS Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32

1.5.5.2 On-site Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
1.5.5.3 ADRACS Interface to local PC (Laptop) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
1.5.5.4 Interface for remote Data Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
1.5.6 Interface to LAN Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
1.6 RCSE SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
1.6.1 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
1.6.2 System Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
1.6.3 Communication Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37
1.6.3.1 Communication Distributor/History Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37
1.6.3.2 Subsystem Data Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38
1.6.3.3 Communication with Navaids 400 and SYSTEM 4000 Stations . . . . . . . . . . . 1-38
1.6.3.4 Communication via Open Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
1.6.3.5 History Memories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
1.6.3.6 Control of Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
1.6.4 System Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
1.6.5 INTERNET Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
1.6.5.1 PPP Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41
1.6.5.2 SNMP Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41
CHAPTER 2 INSTALLATION AND INITIAL SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2.2 Cabling (RCSE/CTU+RWY/PC/RMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2.3 RCSE/REU, Pin Assignment of Interface Connectors . . . . . . . . . . . . . . . . . 2-4
2.2.3.1 SubD 25 Pin Connectors NFK-1, NFK-2 (male) . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.3.2 SubD 9 Pin Connectors (male) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2.2.3.3 64 Pin Connectors OIO 1, OIO 2 and S12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
2.2.4 CTU, Pin Assignment of Interface Connectors . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.2.4.1 SubD 9 Pin Connectors J1, J2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.3 INITIAL HARDWARE SETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.3.1 General Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.3.2 Assignment of connected Stations (CTU and RWY-SELECT) . . . . . . . . . 2-11
2.3.3 Hardware Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Ed. 01.02 III

RCSE 443 RMMC
Section Title Page
2.3.3.1 REU, Jumper Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

2.3.3.2 Processor Board P4N 486 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2.3.3.3 SIB Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
2.3.3.4 NFK Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
2.3.3.5 LGM28.8 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
2.3.3.6 LGM64K Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
2.3.3.7 ZUA29 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
2.3.3.8 ZU1 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
2.3.3.9 LGM9600H1 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
2.3.3.10 LGM1200MD Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
2.3.3.11 INC/CTU Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
2.3.3.12 LGM Extender 2 Unit Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
2.3.3.13 OIO Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
2.3.3.14 Multiplexer RS232 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
2.3.4 Connection to a PSTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
2.3.5 Connection to an Ethernet Line (Network Interface Link) . . . . . . . . . . . . . . 2-34
2.4 INITIAL SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
2.4.1 Initial Power up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
2.4.2 Configuration of the REU with PC and ADRACS . . . . . . . . . . . . . . . . . . . . . 2-36
2.4.2.1 Actualization of REU Application Program (REU.EXE) . . . . . . . . . . . . . . . . . . . 2-36
2.4.2.2 Setting of PTT file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
2.4.2.3 Explanation of Modem Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
2.4.3 Faulty Switching-on Behaviour of RCSE after Configuration . . . . . . . . . . 2-40
CHAPTER 3 OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 OPERATION OF THE RCSE/REU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2.1 Switching On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2.2 Switching Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.3 General Controls of the INC/CTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.3.1 Lamp Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.3.2 Alarm Silent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.3.3 Brightness up/Brightness down (INC and CTU) . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.4 Special Controls of INC/CTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.2.4.1 INC Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
IV Ed. 01.02
RMMC RCSE 443
Section Title Page
3.2.4.2 CTU and RWY-SELECT Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

3.2.5 CTU Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.2.6 INC Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.2.6.1 Subsystem Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.2.6.2 System (RCSE) Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.2.7 CTU and RWY-SELECT Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.2.7.1 CTU Subsystem Status Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.2.7.2 RWY-SELECT System Status Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.2.8 Assignment of Station Main Status Indications . . . . . . . . . . . . . . . . . . . . . . 3-5
3.2.9 Indications and Switches of the REU Subassemblies . . . . . . . . . . . . . . . . . 3-8
3.3 MAINTENANCE OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.3.2 Operation with a Maintenance Data Terminal (PC) . . . . . . . . . . . . . . . . . . . 3-9
3.3.3 Operation at the Remote Maintenance Center (RMC) . . . . . . . . . . . . . . . . 3-9
CHAPTER 4 DETAILED DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 OVERVIEW REU-SUBASSEMBLIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.3 REU-SUBASSEMBLIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.3.1 Processor Board P4N 486 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.3.2 SIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.3.3 OIO (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.3.4 Ethernet Controller (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.3.5 ADC (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.3.6 Modem LGM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.3.6.1 LGM28.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.3.6.2 LGM64K (ISDN Modem) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.3.6.3 Connection Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.3.6.3.1 Connection Setup via Switched Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.3.6.4 Dedicated Line Modem LGM1200MD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.3.6.5 Dedicated Line Modem LGM9600H1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.3.6.6 LGM Extender 2 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.3.7 Modem ZU1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.3.8 Modem ZUA29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.3.9 Star Distributor NFK 29-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Ed. 01.02 V
RCSE 443 RMMC
Section Title Page
4.3.10 Multiplexer RS232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

4.3.11 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.3.11.1 AC/DC-Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.3.11.1.1 AC/DC-Converter Puls AP346 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.3.11.1.2 AC/DC-Converter VERO TRIVOLT PK60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.3.11.1.3 AC/DC-Converter MELCHER LM 1001-7R Option A . . . . . . . . . . . . . . . . . . . 4-15
4.3.11.2 DC/DC-Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.3.11.2.1 DC/DC-Converter Puls APD346 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.3.11.2.2 DC/DC-Converter MELCHER BM 1001-7R Option D . . . . . . . . . . . . . . . . . . 4-17
4.4 CTU/RWY-SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
4.5 RCSE 443 SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4.5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4.5.1.1 Data Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4.5.1.2 Maintenance Mode and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4.5.2 Communication via Switched Lines (PTT) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.5.3 Data Com Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.5.4 PC Control / PC Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.5.5 Switch Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4.5.6 Runway Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
4.5.6.1 Runway Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
4.5.6.2 Runway Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
4.5.6.3 Automatic Disable (Forced Shutdown) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
CHAPTER 5 MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1 ORDINARY MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.2 PREVENTIVE MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
VI Ed. 01.02
RMMC RCSE 443
LIST OF FIGURES
Fig.-No. Title Page
Fig. 1-1 Overview RMMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Fig. 1-2 Hierarchy of the remote control subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Fig. 1-3 RMMC for two ILS and VOR/DME/TACAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Fig. 1-4 RMMC for MLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Fig. 1-5 RCSE 443 for one Navaids 420 ILS with 5 (6) subsystems, connected . . . . . 1-10
to an RMC 443
Fig. 1-6 RCMS components (configuration example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Fig. 1-7 RCSE: REU with INC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Fig. 1-8 REU, front panel open, and back panel (example) . . . . . . . . . . . . . . . . . . . . . . 1-13
Fig. 1-9 CTU with RWY-SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Fig. 1-10 CTU and RWY-SELECT housing, back panel . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Fig. 1-11 INC panel of RCSE with indications and controls . . . . . . . . . . . . . . . . . . . . . . . 1-22
Fig. 1-12 RCSE, block diagram (with one ILS Navaids system), example . . . . . . . . . . . 1-29
Fig. 2-1 RCSE system cabling, power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Fig. 2-2 CTU system cabling, power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Fig. 2-3 ILS stations connected to RCSE via party line modems LGM1200MD . . . . . 2-2
(example)
Fig. 2-4 (D)VOR S4000 station connected to RCSE (example) . . . . . . . . . . . . . . . . . . . 2-2
Fig. 2-5 RCMS 443 system cabling, connections of peripheral equipment, example 2-3
Fig. 2-6 RCSE/REU back panel, connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Fig. 2-7 CTU subrack, back panel connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Fig. 2-8 REU, configuration of CBP and default setting . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Fig. 2-9 P4N 486, position of jumpers and default settings . . . . . . . . . . . . . . . . . . . . . . 2-12
Fig. 2-10 SIB setting: 1a1,2a1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
(e.g.: RSU not connected,CTU connected)
Fig. 2-11 SIB setting: 1a3 configuration (example: RS232) . . . . . . . . . . . . . . . . . . . . . . . 2-15
Fig. 2-12 SIB setting: 2a3 configuration (example: RS232) . . . . . . . . . . . . . . . . . . . . . . . 2-16
Fig. 2-13 SIB setting: 1sA, 1sB configuration (example: TTL) . . . . . . . . . . . . . . . . . . . . . 2-17
Fig. 2-14 SIB setting: 2sA configuration (example: TTL) . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Fig. 2-15 SIB setting: no DMA operation, 2 waitstates for synchronous channels . . . 2-19
(default setting)
Fig. 2-16 NFK, position of jumpers and default settings (2-wire operation) . . . . . . . . . 2-20
Fig. 2-17 LGM28.8, position of jumpers and default settings . . . . . . . . . . . . . . . . . . . . . . 2-21
Fig. 2-18 LGM64K, position of jumpers and default settings . . . . . . . . . . . . . . . . . . . . . . 2-22
Ed. 01.02 VII

RCSE 443 RMMC
Fig.-No. Title Page
Fig. 2-19 ZUA, position of jumpers and default settings (4-wire, -6 dBm, 600 ohms) 2-23
Fig. 2-20 ZU1, position of jumpers and default settings (4-wire operation, 600 ohms) 2-24
Fig. 2-21 LGM9600H1, position of jumpers and default settings . . . . . . . . . . . . . . . . . . . 2-25
Fig. 2-22 LGM1200MD, position of jumpers and default settings (2-wire, 300 ohms) 2-26
Fig. 2-23 INC rear side, position of connectors and jumpers . . . . . . . . . . . . . . . . . . . . . . 2-27
Fig. 2-24 CTU rear side, position of jumpers and default settings, address coding . . . 2-28
switch
Fig. 2-25 LGM Extender 2 Unit, position of jumpers and settings . . . . . . . . . . . . . . . . . 2-29
(example: RS422 without termination)
Fig. 2-26 OIO (example: 24x Input, 8x Output), position of jumpers and default . . . . . 2-30
settings
Fig. 2-27 Multiplexer RS232 (MPX), position of jumpers and default settings . . . . . . . . 2-31
Fig. 2-28 Pin assignment of connector TAE 6 N, RJ12 and RJ45 for connection . . . . . 2-33
to the PTT
Fig. 2-29 Connection to Ethernet line via RJ45 connector of P4N processor board . . 2-34
Fig. 2-30 Location of On/Off switches (REU-subrack and CTU-subrack) . . . . . . . . . 2-35
Fig. 2-31 Window to define modem settings within PTT file (example) . . . . . . . . . . . . . 2-37
Fig. 2-32 Window to define telephone numbers within PTT file (example) . . . . . . . . . . . 2-38
Fig. 2-33 RCSE rear side with PC2 interface to connect service adapter . . . . . . . . . . . . 2-40
Fig. 3-1 Position of On/Off-switch at RCSE, indications . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Fig. 3-2 CTU rear side, position of RWY-SELECT enable switches SW1 and SW2 . 3-3
Fig. 3-3 INC panel (of RCSE) and CTU/RWY-SELECT panel . . . . . . . . . . . . . . . . . . . . 3-7
Fig. 3-4 REU interior, indications and switches, example . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Fig. 4-1 Circuit diagrams of subassemblies of RCSE 443 . . . . . . . . . . . . . . . . . . . . . . . 4-1
Fig. 4-2 Processor board P4N 486, block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Fig. 4-3 SIB, block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Fig. 4-4 LGM28.8, block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Fig. 4-5 Modem LGM1200MD, block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Fig. 4-6 LGM Extender 2 Unit, block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Fig. 4-7 Modem ZU1, block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Fig. 4-8 Modem ZUA29, block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Fig. 4-9 Star distributor NFK 29, block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Fig. 4-10 AC/DC-Converter (Puls AP346), block diagram . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Fig. 4-11 AC/DC-Converter (VERO TRIVOLT PK60), block diagram . . . . . . . . . . . . . . . 4-14
Fig. 4-12 AC/DC-Converter (MELCHER LM 1001-7R), block diagram . . . . . . . . . . . . 4-15
VIII Ed. 01.02

RMMC RCSE 443
Fig.-No. Title Page
Fig. 4-13 DC/DC-Converter (Puls APD346), block diagram . . . . . . . . . . . . . . . . . . . . . . 4-16

Fig. 4-14 DC/DC-Converter (MELCHER BM 1001-7R), block diagram . . . . . . . . . . . . 4-17
Fig. 4-15 CTU/RWY-SELECT, block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Ed. 01.02 IX
RCSE 443 RMMC
X Ed. 01.02
RMMC RCSE 443
Description and Operation Abbreviations
ABKÜRZUNGSVERZEICHNIS
LIST OF ABBREVIATIONS
LISTE D'ABREVIATIONS
LISTA DE ABREVIATURAS
A
AC Alternating Current
Courant alternatif
Corriente alterna
ADC Analog-Digital Converter
Convertisseur analogique/numérique
Convertidor analógico/digital
ADRACS Automatic Data Recording And Control System
AF Audio Frequency
Basse fréquence
Audiofrequencia
ASCII American Standard Code for Information Interchange
Code standard américain pour l'échange d'informations
Código stándard americano para el intercambio de informaciones
ATC Air Traffic Control
Flugsicherung
Contrôle du trafic aérien
Control del tráfico aéreo
AWD Automatische Wähleinrichtung für Datenverbindungen
Automatic dialling equipment for data connections
Dispositif automatique de sélection pour liaisons d'acheminement de données
Dispositivo automático de selección para comunicaciones de datos
AZ Azimuth
B
BAZ Back-Azimuth
BD Baud
Baud
Baudio
BIOS Basic Input/Output System
BIT(E) Built-in Test (Equipment)
Dispositif de test intégré
Dispositivo de test integrado
C
Cat. Category
CBP Connector Back Panel
CCITT Comité Consultatif International Télégraphique et Téléphonique
International Telegraph and Telephone Consultative Commitee
International beratender Ausschuß für den Telegrafen- und Fernsprechdienst
Ed. 01.02 AV-1

RCSE 443 RMMC
Abbreviations Description and Operation
CEPT Conférence Européenne des Administrations des Postes et des Télécommunications
European Conference of Postal and Telecommunications Administrations
Konferenz der Europäischen Post- und Fermeldeverwaltungen
CLK Clock
Takt
CMOS Complementary Metaloxide Semiconductor
Semi-conducteur oxyde métallique complémentaire
Semiconductor complementario de óxido metálico
CPU Central Processing Unit
Zentrale Prozessoreinheit
CRC Cyclic Redundancy Check
CSB Control&Status Board (part of the LCSU)
CTS Clear to Send
Prêt à émettre
Listo para transmitir
CTU Control Tower Unit
CVOR Conventional VOR
D
DC Direct Current
Courant continu
Corriente continua
DCE Data Circuit terminating Equipment
Datenübertragungseinrichtung (DÜE)
DDM Difference in Depth of Modulation
Differenz der Modulationsgrade
Différence de taux de modulation
Diferencia de grados de modulación
DFS Deutsche Flugsicherung
Administration of air navigation services
Bureau de la sécurité aérienne
Instituto de protección de vuelo
DIN Deutsche Industrie Norm
German industrial standard
Norme industrielle allemande
Norma industrial alemana
DMA Direct Memory Access
DME Distance Measuring Equipment
Equipement de mesure de la distance
Equipo de medición de la distancia
DRAM Dynamic RAM
DSR Data Set Ready
Enregistrement des données prêt
Registro de datos listo
AV-2 Ed. 01.02

RMMC RCSE 443
DTE Data Terminal Equipment
Datenendeinrichtung (DEE)
DTR Data Terminal Ready
Terminal de données prêt
Terminal de datos listo
DVOR Doppler Very High Frequency Omnidirectional Radio Range
Radiophare omnidirectionnel VHF Doppler
Radiofaro omnidireccional VHF Doppler
E
EL Elevation
ELTA Electronic TACAN Antenna
EPROM Erasable Programmable Read Only Memory
Mémoire à lecture seule, programmable et erasable
Memoria permanente borrable y programada
EUROCAE European Organization for Civil Aviation Electronics
Organisation européenne pour l'électronique de l'aviation civile
Organización europea para la electrónica de la aviacion civil
F
FAA Federal Aviation Administration
Administration fédérale de l'aviation
Administración federal de aviación
FFM Farfield Monitor
(FF) Moniteur de champ lointain (zone Fraunhofer)
Monitor campo lejano
FSD FACE Standard DME
FSK Frequency-Shift Keying
Frequenzumtastverfahren
Manipulation par déplacement de fréquence
Método de manipulación de frecuencia
FTA FACE TACAN
G
GND Ground
Erde
GP (GS) Glide Path (Glide Slope)
Radiophare d'alignement de descente
Transmisor de trayectoria de descenso
H
HDLC High-level Data Link Protocol
I
ICAO International Civil Aviation Organization
Organisation de l'aviation civile internationale (OACI)
Organización de aviación civil international (OACI)
Ed. 01.02 AV-3

RCSE 443 RMMC
ILS Instrument Landing System
Système d'atterrissage aux instruments
Sistema de aterrizaje por instrumentos
INC Indication and Control
Anzeige und Steuerung
IOM Input/Output Manager
I/O Input/Output
Eingang/Ausgang
entrée/sortie
entrada/salida
IP Internet Protocol
ISDN Integrated Services Digital Network
Dienste-integrierendes digitales Netzwerk
ISO International Organization for Standardization
Internationale Organisation für Normung
Organisation Internationale de Normalisation
ITU International Telecommunication Unit
Internationale Fernmeldeunion
Union Internationale des Télécommunications
K
KDI Keyboard and Display
L
LAN Local Area Network
LAPB Link Access Procedure Balanced
LCD Liquid Crystal Display
Ecran à cristaux liquides
Indicador de cristal liquido
LCP Link Control Protocol
LCSU Local Control and Status Unit
LCU Local Communication Unit
LED Light Emitting Diode
Diode électroluminiscente
Diodo electroluminiscente
LGM Modembezeichnung (LOGEM)
Modem assignation (LOGEM)
LLZ (LOC) Localizer
Radiophare d'alignement de piste
Localizador
LRC Longitudinal Redundancy Check
AV-4 Ed. 01.02

RMMC RCSE 443
M
MFM Memory Filecard Module
MLS Microwave Landing System
Système d'atterrissage aux micro-ondes
Sistema de aterrizaje por microondas
MM Middle Marker
Radiobalise médiane
Radiobaliza intermedia
MON Monitor
Moniteur
Monitor
MOSFET Metallic Oxide Semiconductor Field-effect transistor
N
NAV Navigation
Navigation
Navigation
Navegación
NCP Network Control Protocol
NDB Non-Directional radio Beacon
Radiophare omnidirectional
Radiofaro omnidireccional
NF Niederfrequenz
Audio frequency
Basse fréquence
Baja frecuencia
NFK Niederfrequenzknoten (Sternverteiler)
Star distributor (for audio frequency)
NMI Non-Maskable Interrupt
Nicht-maskierbarer Interrupt
O
OACI = ICAO, Organisation de l'aviation civile internationale
International Civil Aviation Organization
Organización de aviación civil international
OIO Opto coupler isolated Input/Output
OSI Open Systems Interconnection
OTP Overtemperature Protection
Übertemperaturschutz
OVP Overvoltage Protection
Überspannungsschutz
Ed. 01.02 AV-5

RCSE 443 RMMC
P
PC Personal Computer
PE Protection Earth
PPP Point-to-Point Protocol
Punkt-zu-Punkt Protokoll
PROM Programmable Read Only Memory
Mémoire à lecture seule et programmable
Memoria permanente programada
PSTN Public-Switched Telephone Network
PTT Post Telephone and Telecommunications (authority)
PU Processor Unit
R
RAM Random Access Memory
Mémoire à accés aléatoire
Memoria de acceso aleatorio
RCMS Remote Control Monitoring System
Système de télécommande et de surveillance
Sistema de control y monitoreo remotos
RCSU Remote Control Status Unit
RD Read
Reg. Regulator
Regler
REU Remote Electronic Unit
RMC Remote Maintenance Center
RMMC Remote Maintenance and Monitoring Configuration
ROM Read Only Memory
Mémoire à lecture seule
Memoria permanente
RTC Real-Time Clock
Echtzeituhr
RTS Request to send
Marche l'émetteur
Activación del transmisor
RWY Runway
Landebahn
RX Receiver
Empfänger
Récepteur
Receptor
RXD Receiver Data
Données de récepteur
Datos de receptor
AV-6 Ed. 01.02

RMMC RCSE 443
S
SIB Serial Interface Board
SW Switch
Schalter
Commutateur
Conmutador
T
TACAN Tactical Air Navigation
Navigation aérienne tactique
Navigación aérea táctica
TCP Transmission Control Protocol
TTL Transistor-Transistor Logic
Logique transistor-transistor
Lógica transistor - transistor
TX Transmitter
Emetteur
Transmisor
TXD Transmitter Data
Données d'émetteur
Datos de transmisor
U
UDP User Datagram Protocol
V
VOR Very High Frequency Omnidirectional Radio Range
Radiophare omnidirectionnel VHF
Radiofaro omnidireccional VHF
VRC Vertical Redundancy Check
W
WAN Wide Area Network
WIN Windows (Microsoft)
WR Write
WS Wait States
Z
ZU Zeichenumsetzer
Modem for data transfer
Convertisseur de signaux
Convertidor de señal
Ed. 01.02 AV-7

RCSE 443 RMMC
AV-8 Ed. 01.02

RMMC RCSE 443
Description and Operation General Description
CHAPTER 1
GENERAL DESCRIPTION
1.1 GENERAL
1.1.1 Introduction
The Remote Maintenance and Monitoring Configuration (RMMC) is used for remote monitoring, opĆ
eration and maintenance of all the connected navigation systems. The network has a radially configĆ
ured architecture based on communication between the system components via switched or private
lines in the public network and dedicated lines in private networks. Optionally a connection to a LAN
(local area network) via Ethernet line is possible.
The remote control instruments allow all the networked navigation systems to be operated optionally
from central points, from normal operation of the dual systems with automatic changeover in the event
of a fault through manual operation to measurement and setting of all the possible signal parameters,
as well as detailed fault analyses on the basis of a wide range of measured values. They facilitate new
maintenance strategies, whereby primary importance is placed on concentrating logistics and qualiĆ
fied personnel, and then on responding to specific failures with systematic maintenance activities
rather than relying on periodic precautionary measures. This considerably improves both mainteĆ
nance efficiency and the economic efficiency of the systems throughout their service life.
Although these advantages only apply to the modern generation of air traffic control systems develĆ
oped by Thales ATM (in other words to the Navaids 400/SYSTEM 4000 and the navigation aids used
with it, namely the CVOR and DVOR, the ILS and MLS instrument landing systems, the ILS farfield
monitor (FFM), the TACAN 453 and the DME 415 radio beacons, the electronic TACAN antenna (ELTA
200) and the NDB 436) the extensive range of interface boards makes it possible to incorporate other
collocated systems in the remote control and monitoring strategy if desired. The outstanding features
of the system are as follows:
- EXTREME FLEXIBILITY
The open system architecture enables a variety of standard connections to be established using dediĆ
cated or switched lines, telephone or data networks, local area networks and serial or parallel interĆ
faces. The many different interface boards and software utilities which are available allow the system
configuration to be adapted to local requirements. A remote maintenance and monitoring configuraĆ
tion which provides a permanent indication of the availability of all the navigation systems in the netĆ
work can, for example, be set up via the public telephone network. As an option of the P4N processor
board an Ethernet connector enables the connection of the REU to a LAN to transfer status informaĆ
tion from the RCSE to a host PC or workstation.
- EXCEPTIONAL RELIABILITY
All data communication is implemented using reliable data protocols. The instruments are designed
for the operating conditions specified in the EUROCAE recommendations. The DIN plug-in connecĆ
tions ensure excellent contact is made between the subassemblies and the bus board. There are no
mechanical wearing parts, and even disk drives for storing data have been dispensed with.
Ed. 01.02 1-1

RCSE 443 RMMC
General Description Description and Operation
- USER-FRIENDLY OPERATOR INTERFACES
To allow the user to work in a familiar environment, the currently prevailing PC standards and operatĆ
ing systems have been employed. All the control, monitoring and maintenance functions are disĆ
played on a color screen. They are executed in windows with aid of function keys or a mouse. The
most important status indications and control elements are implemented on the front panel of the baĆ
sic instrument, so that simplified remote control and monitoring are also possible without connecting
a PC system.
- LOW EQUIPMENT COSTS
Due to the use of standard PC technology the system is situated in the lower price range for computer
networks and remote control and maintenance systems. The RMMC is a complete, autonomous sysĆ
tem. It can however also be used as a gateway to more complex data processing systems.
RMC 443
Remote Maintenance Center
RCSE 443
Ê
ÊÊÊ
INC
REU
PTT
RCMS 443
Remote Control and Monitoring System
Host
RCSE 443
Remote Control and
Status Equipment
Ê
ÊÊÊ
ÊÊÊ
Ê
INC
REU LAN
RCMS 443
Host
Stations
RCMS 443
Other systems
Fig. 1-1 Overview RMMC
1-2 Ed. 01.02

RMMC RCSE 443
1.2 SYSTEM OVERVIEW
1.2.1 General
The Remote Maintenance and Monitoring Configuration (RMMC) is a flexible information processing
network for remote control, monitoring and maintenance of navigational aids systems for air traffic
control. In addition to the usual remote control functions, it enables all the possible signal parameters
to be set and read, and permits extensive remote analysis of system failures by polling and interpretĆ
ing a wide range of measured values.
1.2.2 Components of the System

1.2.2.1 Remote Control and Status Equipment (RCSE)
The RCSE is intended to be installed in the maintenance equipment room. It provides separate status
display and on/off-control functions for all Navaids equipment, and mechanisms to change and disĆ
play auxiliary data words for MLS. The RCSE consists of the Remote control Electronic Unit (REU)
with an Indication and Control (INC) panel. The RCSE is interfacing with one or two Control Tower
Units (CTU), with a maintenance data terminal (PC). The CTU is intended for installation in the ATC
control tower. It provides system 'main status' indications and may provide a separate status display
for each Navaids subsystem as well as switching the ILS or MLS to the active runway (RWY-SELECT,
optional). Optionally a slave RCSE panel unit defined as Remote Status Unit (RSU) with an 'old' verĆ
sion of indication panel (RPU) can be connected to the RCSE, but this equipment is no more availaĆ
ble, and therefore not considered within this document.
1.2.2.2 Remote Control and Monitoring System (RCMS)

The RCMS is the equipment used for maintenance and control of ILS or MLS landing systems. The
basic configuration of the RCMS contains the RCSE and a maintenance data terminal (PC) to perform
the RCMS functions.
1.2.2.3 Remote Maintenance Center (RMC)

RMC is the equipment used at the Regional (RMC-R) or at the Central (RMC-C) site. The basic conĆ
figuration of the RMC contains the RCSE and a maintenance data terminal (PC) to perform the RMC
functions. The operational mode of the RMC is defined by a software different from the RCMS softĆ
ware.
1.2.2.4 Navaids Local Communication Unit (NAV-LCU)

The NAV-LCU is a device used as local communication interface between en-route navigation sysĆ
tems TACAN, ELTA, CVOR, DVOR and the RMC. The NAV-LCU comprises the Remote control ElecĆ
tronic Unit ( REU), which is equipped according to the specific requirements of the NAV station. It
serves as a communication interface between the connected equipment and the public switched netĆ
work (PTT), and as a common point for connecting a service terminal (Laptop PC) for commissioning
and maintenance purposes.
In Navaids 400 en-route navigation systems (e.g. CVOR 431) no separate NAV-LCU device has to
be used as local communication interface. The NAV-LCU functionality is integrated in the Navaids
400 subrack, i.e. the LCU software is running on the already existing LCSU/CSB board, additional
modems are used for communication purposes.
NOTE: The Annex NAV-LCU 443 of this technical manual (Register 6) gives additional informaĆ
tion to design, technical data and installation of the separate device NAV-LCU 443.
Ed. 01.02 1-3

RCSE 443 RMMC
1.2.2.5 Remote Maintenance Subsystem (RMS)

The RMS is used within MLS system configurations as an additional controller system separate from
the RCMS to perform maintenance, data gathering and alarm determination functions for the various
pieces of equipment being supervised. It consists of the REU and a maintenance data terminal (PC)
installed in the maintenance equipment room and is also interfaced via a modem to the stations,
which are available to communicate to both the RCMS and the RMS equipment.
1.2.3 Hierarchy of RMMC Remote Control Equipment

At the top, the Central Remote Maintenance Center (RMC-C) is used to obtain an overview of the
status of all systems. The RMC-C is connected via dialing modems to the PTT to obtain serial data
from the RMC-R, NAV-LCU 443 or RCMS 443.
At the RMC-R the main status of all enroute equipments (VOR, DME-Transponder and TACAN-
ground stations) of one defined region are displayed continuously at an INC panel to the controller
for enroute. Besides enroute systems, the main status indications of the ILS and MLS landing systems
are also displayed for maintenance purposes. The RMC-R is also connected to the PTT via dialing
modems. For special applications a dedicated line interface may be provided. For maintenance activiĆ
ties at the screen of the PC maintenance data are displayed. The maintenance technician obtains all
the data from the subsystems configured for this region with defined menus on the screen of the data
terminal (PC). It is possible to use the ADRACS (Automatic Data Recording And Control System) softĆ
ware for maintenance purposes to control Navaids 400 or SYSTEM 4000 equipment at the remote
site. For MLS the MLS-menu technique is employed as well as respective ELTA-, DME-, or TAĆ
CAN-PC supervisory programs.
The RCMS 443 and the NAV-LCU 443 are link control units and provide central points for commuĆ
nication between RMC's and the navaids systems. While the RCMS is connected via twisted teleĆ
phone line pairs and modems to the ILS/MLS-systems the NAV-LCU 443 has direct RS-232/422
interfaces to the VOR, TACAN/DME and ELTA-equipment. For small projects, it is possible to conĆ
nect the NAV-LCU of en-route navigation systems via switched lines to an RCMS.
RMC-C Remote Maintenance Center

CENTRAL
Remote Maintenance Center
REGIONAL
RMC-R RMC-R RMC-R
PTT
RMS RCMS 443 ILS
NAV-LCU 443
LLZ GP MM
LCSU/CSB
RCMS 443 MLS
VOR CVOR 431
4000 TAC ELTA
AZ EL DME/P TAC ELTA
Fig. 1-2 Hierarchy of the remote control subsystems
1-4 Ed. 01.02

RMMC RCSE 443
The protocols for serial data communications between the RCMS 443 and the navaids landing subĆ
systems (ILS/MLS) and between the NAV-LCU 443 and the en-route navaids subsystems (VOR,
DME/TACAN) are harmonized to Navaids 400, MLS, ELTA and SYSTEM 4000. According to these proĆ
tocols the subsystem data is continuously polled by the link control unit with commands for the status
messages. To get specific messages for maintenance a scheduled and also specific polling is proĆ
vided. The specified frames used in the protocols are defined to obtain an optimum of information
within short time intervals with the highest data integrity. A data communications error is indicated in
case of command telegrams not followed by correct message telegrams.
In case that a switched line connection is used and there is a change in system status, the NAV-LCU
443 or the RCMS 443 initiates a dialing procedure to the dedicated RMC-R which then polls the new
status message. Besides the status, maintenance data may also be added. With respect to DME-
transponder DME 415/435 and TACAN-equipment TAC 453, the protocols do not follow the polling
procedure as described before. These subsystems also deliver messages to the NAV-LCU without
a request by command telegrams. The protocol used serves maintenance data terminal (PC) menus
for the following functions:
- about 10 standard (colloquial) procedures,
- login/logout and password procedures
- routine check for history storage with about 50 measurements.
1.2.4 System Configuration

1.2.4.1 Local Remote Control Interface
The Navaids stations communicate with the remote control system in different ways. The remote conĆ
trol interfaces which are provided locally vary according to the type of installation:
Type Modem Baudrate Remark
Dedicated ZU1 600 baud SYSTEM 4000

line (up to end of '92)
ZUA29 1200 baud (V.23) SYSTEM 4000 (since 1993),
NAV 400, MLS
LGM1200MD 600/1200 baud (V.23) SYSTEM 4000,

party line NAV 400, MLS
LGM9600H1 1200 baud (V.23), ILS/MK20A

half duplex
LGM14.4 1200...19200 baud (V.32) NAV 400

(up to end of 2000)
LGM28.8 1200...38400 baud (V.34) NAV 400 (since 2000)
Std. bus modem 1200, 2400, 4800, 9600 DME 415/435, TAC 453
LGM724 desktop 2400 baud (V.22bis) ELTA-200
Switched line LGM28.8 up to 28.8k baud NAV-LCU 443,

LGM64K (ISDN) 64k baud NAV 400
LGM928 desktop 1200...38400 baud (V.34) NAV 400 (since 2001)
Ed. 01.02 1-5

RCSE 443 RMMC
1.2.4.2 Remote Control and Status Equipment RCSE 443
The RCSE is an REU with an Indication and Control (INC) panel. It can be used as a simple, yet comĆ
plete, remote control unit. The INC indicates the states of up to eight substations with the following
LED displays: ALARM, WARNING, NORMAL, DATA COMmunication and MAINTENance.
An alarm tone is sounded if a status changes. Each station can be selected by pressing a membrane
button, in order to activate the EQUIPment ON, OFF and CHANGEOVER functions and to indicate
specific monitor alarms. An additional status indication device is the Control Tower Unit (CTU), which
however, only indicates the NORMAL, WARNING and ALARM operating states of up to eight NAV staĆ
tions. Its display brightness is adjustable to permit adaptation to the varying light conditions in the
control tower. The CTU can be used in conjunction with a runway selector (RWY-SELECT), which
activates the ILS systems in one approach direction and switches the other direction to a dummy load.
This panel also indicates the general status of the two ILS systems (OPERATIONAL, DEGRADED,
SHUT DOWN) and their availability (ENABLE) to aircraft as a landing aid.
A variety of interface boards is available for serial or parallel data I/O, installing an ETHERNET interĆ
face, connecting a PC and dialing via the public network (PTT), so that the system has a considerable
potential for expansion. The connections to the NAV stations are set up via modems and telephone
lines (600 ohms). The control and indication panels are connected by means of serial RS422 interĆ
faces.
1.2.4.3 Remote Control and Monitoring System RCMS 443
The maintenance, fault analysis and documentation functions of the RMMC are implemented by conĆ
necting a PC system to the RCSE and installing the RMS or RCMS application software on it. The
difference in the names is a reflection of the definitions laid down by the U.S. FAA. An RMS designed
for maintenance purposes has direct, permanent access to the navigation systems via separate cable
connections, and is operated independently of the RCSE, while an RCMS uses the same communicaĆ
tion paths for the maintenance functions as it does for remote control and monitoring. The following
functions are provided:
- System status indication for each connected system
- Permanent indication of the general status of all systems
- Permanent indication of the current date and time
- Detailed status indications for a selected system
- Polling, display and setting of system parameters
- Polling of internal measured values (BITE)
- Continuous monitoring of parameters (either printout if a programmable limit value is reached or
periodic polling)
- 5-level password protection
- Configuration of the remote maintenance and monitoring system
- Loading and saving of setups for operation
- Logbook function, status and alarm history memories
- Selection of data to be printed out
1-6 Ed. 01.02

RMMC RCSE 443
1.2.4.4 Remote Maintenance Center RMC 443
If a maintenance center is installed, it is possible to connect several different remote control systems
to a central REU via switched lines. The general status of all the remote control systems in the network
is indicated permanently on one or more INC panels. Any change in a status causes a connection
to be set up automatically from the LCU or the RCSE to the responsible center and all the current
status information to be transmitted. The center can also be set up to poll the regional stations periodiĆ
cally.
The center is fully equipped to exchange such data with the networked systems which is necessary
for it to be able to perform a detailed fault diagnosis. It communicates either directly with en-route
navigation systems via switched connections or with ILS substations via the Remote Control and StaĆ
tus Equipment (RCSE) at each airfield.
1.2.4.5 General Examples
Fig. 1-3 illustrates the function of the RCMS 443 ILS. Besides the ILS subsystems, terminal CVOR/
DME has also an interface to the RCSE 443 ILS. The number of subsystems connected to the RCSE
443 is shown to demonstrate the variety of subsystems. In fact the figure is limited to a maximum of
12 connected lines.
Fig. 1-4 shows a configuration for Cat.I operation for MLS (with combined data link for status transfer
and maintenance data). The LRCI used for MLS equipment is replaced in the case of DME/TACAN
equipment by input/output managers (IOM). The RCSE 443 displays the status of two MLS systems
with Azimuth (AZ), Elevation (EL) and DME/P. The AZ station of the MLS for the runway direction not
in use is used as Back-Azimuth. The MLS subsystems may also contain additional RMC-modems
(optional).
Fig. 1-5 - a simple RMMC for ILS - shows the function of the RCSE in more detail. The Navaids
400 subsystems (LLZ, GP, FFM and Marker) are shown connected via a star distributor (NFK29) to
a common modem. In the polling procedure the subsystems are interrogated sequentially in time mulĆ
tiplex mode. As shown in Fig. 1-5, for the function of the RCSE 443 the status of the DME 415 (also
TAC 453) is transferred via parallel lines to the collocated Navaids 400 equipment. The status of the
DME/TACAN is transmitted to the REU of the RCSE 443 ILS within the Navaids 400 protocol.
Alternatively the Navaids 400 subsystems may be connected to the RCSE via dedicated line modems
LGM1200MD, operated in party line mode. On replacement, the LGM1200MD is used in the RCSE
instead of common modem and NFK star distributor. This is shown in Fig. 2-3.
A second alternative is the usage of a Multiplexer RS232 board instead of the NFK star distributor
within the RCSE. In this case the ILS stations are connected via RS232 (or RS422) dedicated lines
to the RCSE (see Fig. 1-5).
Ed. 01.02 1-7

RCSE 443 RMMC
to Maintenance Center Ethernet (LAN), optional

(PTT line)
RMMC
RCSE 443
additional
MODEM Ethernet IF
panels
CTU RWY
Ê
ÊÊÊ
SELECT
REU
INC
NAV-LCU
MODEM MODEM MODEM MODEM MODEM KDI IOM CU
FFM Marker ELTA
VOR DME
LLZ GP DME DVOR TACAN
SYSTEM 2 (S 4000)
MODEM MODEM MODEM MODEM MODEM MODEM CSB CU
FFM Marker ELTA
CVOR DME
LLZ GP DME DVOR TACAN
SYSTEM 1 (NAV 400)
Fig. 1-3 RMMC for two ILS and VOR/DME/TACAN (example)
1-8 Ed. 01.02

RMMC RCSE 443
to Maintenance Center Ethernet (LAN), optional

(PTT line)
RMMC
RCSE 443
additional
MODEM (optional) Ethernet IF (optional)
panels
CTU RWY
ÊÊ
ÊÊ
SELECT
REU
INC
MODEM
MODEM MODEM MODEM MODEM MODEM MODEM
LRCI LRCI LRCI LRCI LRCI LRCI
AZ EL BAZ AZ EL BAZ
(opt.) (opt.)
SYSTEM 1 SYSTEM 2
Fig. 1-4 RMMC for MLS (example)
Ed. 01.02 1-9

RCSE 443 RMMC
RMC 443
INC
REU
Ê
ÊÊÊ SIB
DIAL MODEM LGM
MAINTENANCE CENTER
ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ
PTT LINES
AIRPORT
TOWER
RCSE 443
1)
REU DIAL MODEM LGM
RSU RS4222)
CTU RWY
RS4222) SELECT
INC SIB
ÊÊ
ÊÊÊ
MODEMS LGM
STATIONS
(Navaids 400)
MODEM
3) 3) 3) 3)
MODEM MODEM MODEM MODEM MODEM
M 4000
LLZ FFM Marker GP DME
1) RSU with 'old' indication 2) RS422 interface to equipment situated 3) alternatively the ILS stations can be connected
panel RPU can be used in a different building than RCSE - via RS232 or RS422 dedicated lines to the RCSE
LGM Extender 2 Unit has to be used! (Multiplexer RS232 board is used in RCSE,
RS232 interfaces instead of modem within ILS
stations)
Fig. 1-5 RCSE 443 for one Navaids 420 ILS with 5 (6) subsystems, connected to RMC 443
1-10 Ed. 01.02

RMMC RCSE 443
1.3 MECHANICAL DESIGN
The components of the RCMS to be combined to various configurations are (Fig. 1-6):
- the RCSE 443 consisting of the REU in various configurations, and the INC panel
- a Maintenance Data Terminal (PC and printer)
- the CTU and RWY-SELECT (eventually more CTUs cascaded)
Maintenance Data Terminal with printer
RCSE with REU and INC
ÊÊ
ÊÊÊÊ
ÊÊ
ÊÊÊÊ
INC
CTU and RWY-SELECT
CTU and RWY-SELECT
Fig. 1-6 RCMS components (configuration example)
Ed. 01.02 1-11

RCSE 443 RMMC
1.3.1 RCSE: REU with INC
EQUIPMENT RC
MAIN STATUS DETAILED STATUS
1 2 3 4 5 6 7 8
MON 1 MON 2 TX 1 TX 2
CONTROL STATION
SIL
COMMAND
SELECT SELECT SELECT SELECT SELECT SELECT EQUIP CHANGE REQUEST LAMP
SELECT SELECT
ON/OFF OVER RELEASE TEST
19"-cabinet
550x197x450 [WxHxD mm]
REU 19" subrack

482x131x380 (+40 for fuses)
[WxHxD mm]
INC
Fig. 1-7 RCSE: REU with INC
1-12 Ed. 01.02

RMMC RCSE 443
Front Panel (INC removed)

Equipped with DC/DC converter
4)
PC2
Processor Board
PC1
2), 3)
1)
1)
OIO1 1)
LGMx 3
LGMx 4
LGMx 1
Spare
LGMx 2
2)
2)
Spare
OIO2
OIO3
2)
NFK 1
NFK 2
ZUx
SIB
1) optional LGM x = LGM28.8, LGM9600H1 or LGM64K (ISDN) DC/DC-Converter

ZUx = ZUA29 or ZU1 APD346
2) LGM1200MD at LGM4 instead
of NFK1/2 and ZUx or
Multiplexer RS232 board instead
of NFK and ZUx
3) LGM Extender 2 Unit at LGM4 to connect
devices situated in other building (e.g. CTU , RSU)
via RS422 without potential difference
4) optional RJ45 or AUI network link interface to connect
RCSE to LAN network (via SNMP)
Back panel
LGM1 1sA 1a2/PC1

VAC 115/230 V 2AT OIO 1 OIO 2 S12
NFK-1 LGM2 1sB 2a2/PC2 1

LAN
6.3.AT 2
VDC LGM3 2sA/422 2a1/CTU
36-72 V
+- 1AT
LGM4 1+2a3/422 1a1/RSU 1AT -12V +12V
NFK-2 1)
ZUA 1a3
DC/DC
ON IN/OUT 2a3
2)
OFF
1) prepared for DCF77 clock

2) connector not used
Fig. 1-8 REU, front panel open, and back panel (example)
Ed. 01.02 1-13

RCSE 443 RMMC
1.3.2 CTU with RWY-SELECT
Control Tower Unit (CTU) RunWaY Select
AIR NAV SUBSYSTEM RWY-SELECT
19"-cabinet
520 x 179 x 300 [mm]
RWY-SELECT
CTU Blank panel

AC/DC,DC/DC converter in 19" subrack (alt. to RWY-SELECT)
482.6 x 133.3 x 150 [mm]
NOTE:The 19"-cabinet with power supply is used if CTU or RWY-SELECT are not mounted in existing 19"-subracks of
controlconsoles.
Fig. 1-9 CTU with RWY-SELECT
1-14 Ed. 01.02

RMMC RCSE 443
AC mains fuse
VAC 85V...264V
DC/DC
I
0
J1 CTU/RPU IN
J3 J4
VDC J17
J2 CTU/RPU SLAVE
-+
Fig. 1-10 CTU and RWY-SELECT housing, back panel
Ed. 01.02 1-15

RCSE 443 RMMC
1-16 Ed. 01.02

RMMC RCSE 443
1.4 TECHNICAL DATA
The device fulfills the EMC requirements of EC Guideline 89/336/EEC. It bears the CE Designation
(see section 1.4.4).
1.4.1 General Data REU
NOTE: The following sections are also valid for the NAV-LCU 443, the differences in the used
components are described in the Annex NAV-LCU 443 (register 6) of this document.
1.4.1.1 Housing
All REU-components are housed in a 19"-subrack. All the slide-in units and plug-in boards are
designed in the standard single Eurocard format and have DIN plug connectors. The REU is subdiĆ
vided in three compartments.
- Central Processing Unit (PC-unit) max. 7 boards

- Modem units max. 7 boards
- Power-supply 1 plug-in unit
Each REU is fitted with a series of standard components and can be extended by a number of optional
or alternative plug-in units, depending on the application.
The 19" subrack is normally mounted in a separate housing (Fig. 1-7).
1.4.1.2 Dimensions and Weight
Dimensions Standard 19-inch rack, single height,

all boards in single Eurocard-format.
Weight approx. 15 kg
1.4.1.3 Power Supply
The REU can be supplied with either AC/DC or DC/DC power-supplies. The power supply can be
an AC/DC-Converter or alternatively a DC/DC-Converter.
AC input Puls AP346: nom. 100...240 VAC (85...265 VAC)

Frequency range: nom. 50/60 Hz (47...63 Hz)
DC input Puls APD346: nom. 36...72 VDC (30...90 VDC)
Power consumption max. 40 VA
Ed. 01.02 1-17

RCSE 443 RMMC
1.4.1.4 Environmental Conditions
Operation: ambient temperature 0 to 70 °C

relative humidity max. 95 % (below 35 °C)
Storage : ambient temperature -20 to+ 85 °C

relative humidity max. 95 %
1.4.1.5 PC Unit
The PC-unit consists of up to 7 Eurocards running on the MCE-bus-backplane (PC/AT-compatĆ

ible bus).
- Processor board P4N 486 with:

· 4 MB (max. 64 MB) DRAM (System RAM)
· 128 Kbyte Flash EPROM (ELITE-BIOS by AWARD)
· watchdog
· real time clock (battery-backed)
· 4 MB SAN disk (flash disk, acts like a hard disk) integrated on IDE bus, divided into 3 MB
EPROM partition ("EPROM side") containing DOS 5.x and REU application software and
1 MB RAM partition ("RAM side") containing the configuration files
· optional Ethernet controller on board with RJ45 (10BASET) network interface to connect
RCSE to a LAN network using SNMP Internet protocol
The further configuration depends on the application requirements. The system can hold and control:
- Serial Interface Board (SIB):
· 10 channels (interrupt-driven):
2x RS422/485
2x RS232
1x TTL, 1x TTL or RS422/485
2x adjustable on TTL or RS232
2x adjustable on TTL or RS422/485 or RS232
· each channel is fully interrupt-driven
· transmission rate: 0 ... 38400 baud
The following cards are optional available for special applications:

- Opto-isolated Input/Output card (OIO):
· max. 2 cards with 32 inputs/outputs max. for each card, variable
- Analog/Digital converter card (ADC):

· 13-bit AD-conversion with
· 16 channels single-ended or
· 8 channels double-ended
- Real Time Clock (RTC) plug-in card with receiver DCF77
1-18 Ed. 01.02

RMMC RCSE 443
1.4.1.6 Modem and Distribution Units
The modem compartment holds the possible dial modems (LGMx), dedicated-line modems (ZUx)
and dedicated-line star-distributors (NFK29). It is equipped with a specially designed wiring board
to match the different plug connectors and pin configurations. The wiring board has seven slots. The
four left-hand slots are reserved for switched-line modems (LGM28.8 or LGM64K) with the standard
CEPT 96-pin configuration. The next slot is used for the dedicated-line modem ZUx (ZU1 or ZUA29)
and the two right-hand slots accommodate the star distributor NFK29. Alternatively it may be reĆ
placed by the Multiplexer RS232 board. All the line inputs are designed for connecting balanced 600
ohm cables and are protected against overvoltage conditions by metal-oxide varistors. The followĆ
ing modems are used at present:
- Standard dialing modem LGM28.8: V.21, V.22, V.22bis, V.32, V.32bis, V.34;
V.25bis, V.42bis; dialing modem;
LGM28.8 fibre optic (optional): Standard LGM28.8 with fibre optic connectors
- ISDN dialing modem LGM64K: D-channel (DSS1, 1TR6), B-channel data transmission
- Dedicated line modem ZUA29: V.23, 1200 Baud
- Dedicated line modem ZU1: 600 Baud
- LGM1200MD partyline: V.23, (600 or) 1200 baud, half duplex
- Dedicated line modem LGM9600H: V.21, V.22, V.22bis, V.23, V.26bis, V.27ter, V.29; half duplex
- Star-distributors NFK29: Each distributor can handle and switch up to six tele-
(max. 2 hardwired) phone channels. The two NFK29 work together with
modem ZUA29 or ZU1.
- Multiplexer RS232 (MPX): Each multiplexer can handle and switch up to six RS232
(max. 2 ) or RS422 channels.
1.4.1.6.1 Dialing Modems
- Standard Dialing Modem LGM28.8D1

Transmission mode: V.21 (300 bit/s, duplex) asynchronous
V.22 (1200 bit/s, duplex) synchronous and asynchronous
V.22bis (2400 bit/s, duplex) synch. and asynch.
V.23 (75/1200, 1200/75 bit/s, asym. duplex) asynch.
V.32 (4800, 7200, 9600 bit/s; duplex) synch./asynch.
V.32bis (14400 bit/s, 12000 bit/s, duplex) synch./asynch.
V.34 (2400 ... 28800 bit/s, duplex) synch. and asynch.
Control interface V.24, TTL, connector CEPT standard
Dialing pulse or multi-frequency, FLASH/GROUND key function
Transmit-level -10 dBm
Receive-level -43 ... 0 dBm, adjustable
- ISDN Dialing Modem LGM64K
Transmission rate to DTE 300 to 115,200 bit/s, duplex, asynchronous
600 to 64,000 bit/s, duplex, synchronous
Line attenuation for S0 installation 6 dB/96 Hz
Unbalanced attenuation for S0 install. >43 dB
Ed. 01.02 1-19

RCSE 443 RMMC
1.4.1.6.2 Dedicated-line Modems
- Dedicated-line Modem ZUA29

Related specifications V.23
Baudrate 1200 bit/s, half-duplex (sync.,async.)
Control interface V.24, RS232 or RS422 specification
Transmission V.23 (fdown=1300 Hz, fup=2100 Hz)
Transmit level -45 ... 0 dBm, adjustable
Maximum line attenuation handled by 43 dB (at 0 dBm Tx-level)
the receiver
Adjustable receive attenuation 0 ... 36 dB
- Dedicated-line Modem ZU1

Related specifications V.23 modified
Baudrate 600 bit/s, half duplex (async.)
Control interface V.24, RS232 or RS422 specification
Transmission fdown=1320 Hz, fup=2760 Hz
Transmission level -36 ... 0 dBm, adjustable
Maximum line attenuation handled by 36 dB (at 0 dBm Tx-level)
the receiver
Adjustable receive attenuation 0 ... 36 dB
- Dedicated-line Modem LGM1200MD Partyline

Principle frequency-shift keying (V.23)
Telegraphic speed 600 or 1200 baud, half duplex (sync., async.)
Code any
Center frequency at up to 1200 bit/s outgoing: 1300 Hz
incoming: 2100 Hz
Frequency deviation ±400 Hz
Transmit level -6 dBm, adjustable to ±0, -3, -9 dBm
Receive level - 43 dBm, adjustable to -33 dBm,
Interface to CSB V.24
Telephone trunk line 2-wire, 300 ohms (remote side, e.g. RCSE)
- Dedicated-line Modem LGM9600H1

Transmission mode V.21, V.22, V.22bis, V.23, V.26bis, V.27ter, V.29
in half duplex mode
Control interface V.24, TTL, connector CEPT standard
Dialing pulse or multi-frequency,
FLASH- and GROUND-key function supported
Transmit-level -10 dBm
Receive-level -43 ... 0 dBm, adjustable
(used as dedicated line modem to connect a Wilcox MK20A station to the RCSE)
1-20 Ed. 01.02

RMMC RCSE 443
1.4.1.6.3 Distribution Units
- Star-distributor NFK29
Multiplexed lines 6 independent lines to switch
Amplification (transmit, receive) 0 dB / 20 dB
Channel decoupling 60 dB
Inputs separate opto-isolated switching inputs for each line
Drive capability one dedicated line modem can operate two NFK29
Line connection 2 or 4-wire telephone cable
Line protection lightning protection is provided for each channel with metal
oxide varistors
- Multiplexer RS232
Output channels 6 channels configurable to modes RS232, RS422 and TTL

Output signals RS232: TXD, RXD, GND of 6 channels or
RS422: +TXD, -TXD, +RXD, -RXD of 6 channels,
led to NFK-1/2 connector to connect ILS stations via
RS232/RS422 dedicated lines
Input signals TXD, RXD in mode RS232 or TTL (configurable)
1.4.1.6.4 Supported Protocols
Asynchronous protocol
Code code transparent transmission
Data Security CRC-CCITT-Bytes for each telegram (SOFT-CRC)
telegram frames SEL Doc. MLSG-SE-DR-A/0,
S4000-SE-DS-AR/000-100, SN400-TEL-SPEC
Local Area Network (LAN) NETBIOS interface for the session-layer (Ethernet)
Wide Area Network (WAN) Internet IP, TCP/IP, PPP Implementation
1.4.1.7 Modem Replacement Unit LGM Extender 2
Level conversion CEPT-DEE of TTL to RS232 resp. RS422,

opto and electrically isolated for RS 422 connections
to distant equipment (e.g. CTU) without potential difference
Transmission baud rate up to 38.4 kbit/s (for RS232)
Insulating property >= 0.5 kV
Output LGMx (x = 1..4, only at LGM4 all signals are available),
RS232 or RS422, Canon DB9, secondary overvoltage
protection
External power supply + 5 V (possible for optocoupler outputs), not used in RCSE
Operation ambient temperature 0 to 70 °C
relative humidity max. 95 %
Ed. 01.02 1-21

RCSE 443 RMMC
1.4.2 General data INC

1.4.2.1 Housing and Power Supply
For standard applications the INC is mounted directly as a front panel to the REU 19"-subrack. The
INC is supplied with 5 V by the REU power module.
1.4.2.2 Components
- Panel with Status LED/Select Keys
- LED-display driver
EQUIPMENT RC
1 2 3 4 5 6 7 8
MON 1 MON 2 TX 1 TX 2 OPERATION
AERIAL AERIAL ON ON
WARNING
STANDBY STANDBY WARNING WARNING
ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM DATA COM
FAULTY FAULTY FAULTY FAULTY

WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
BYPASSED BYPASSED ON ANT ON ANT
NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL
CONTROL STATION
DATA COM DATA COM DATA COM DATA COM DATA COM DATA COM DATA COM DATA COM
ENGAGED MAINS OFF
SIL
MAINTEN MAINTEN MAINTEN MAINTEN MAINTEN MAINTEN MAINTEN MAINTEN
ENABLED ENV ALRM
COMMAND
ANT FTY
SELECT SELECT SELECT SELECT SELECT SELECT EQUIP CHANGE REQUEST LAMP
SELECT SELECT
ON/OFF OVER RELEASE OTHERWARN TEST
Fig. 1-11 INC panel of RCSE with indications and controls
1.4.2.3 Main Status Indication and Control
For each subsystem (area EQUIPMENT-MAIN STATUS, see Fig. 1-11) the following indications are
available:
Text field, top red characters four displays for characters, indicates station name or other;
if more than 4 characters are used indication is alternating
ALARM red Alarm:
- Subsystem shut-down
- Out-of-tolerance signal(s) while monitor in bypass
WARNING yellow Warning (Alert):
1. Transmitter(s) OFF
2. Equipm. initializing or (MLS: AZ/BAZ) reconfiguring
3. Primary Equipment shut-down by monitor
4. Limited Monitor Configuration (only one executive)
6. Local access (local panel or attached terminal)
7. Monitor Bypass (one or both)
8. MLS: Non-essential data shut-down
9. MLS: C-band sync switched off
10. Battery operation
1-22 Ed. 01.02

RMMC RCSE 443
NORMAL green Normal Operation:
All transmitter and monitor equipments are switched on,
initialized and serviceable for the intended category
of operations (i. e. No Warning and No Alarm Condition).
DATA COM green Data-Communication:
Data-Communication between subsystem and
RCSE available
MAINTEN yellow Permanent indication:

1. Maintenance Warning (BITE Warning)
2. Local access (local panel or attached terminal)
Blinking indication:
indication of selected station
1.4.2.4 RCSE Status Indication and Control

For the RCSE function (area RC, see Fig. 1-11) the following indications and keys are available:
OPERATION green Normal operation
WARNING yellow REU BITE-Warning
DATA COM red Internal communication fault
SIL key Switches off the buzzer in case of alarm ('silence')

LAMP TEST key Test of all indication lamps (buzzer is switched on)
1.4.2.5 Detailed Subsystem Status Indication and Control
By selection of a defined Subsystem the following indications and controls are available:
Monitor 1/2 status indication (area EQUIPMENT-DETAILED STATUS-MON1/2, see Fig. 1-11):
AERIAL green No Aerial Alarm
STANDBY green No Standby warning
FAULTY yellow Monitor Fault
BYPASSED yellow Monitor Bypass
Transmitter 1/2 status indication (area EQUIPMENT-DETAILED STATUS-TX1/2, see Fig. 1-11):
ON green TX on
WARNING yellow BITE Warning
FAULTY red Transmitter faulty (TX shut down)
ON ANT green TX connected to aerial
Control of local/remote mode (area EQUIPMENT-DETAILED STATUS-CONTROL, see Fig. 1-11):

ENGAGED yellow Remote mode, RCSE can only be controlled by PC
(COMMAND keys not active)
ENABLED green Local mode, RCSE can be controlled using INC panel keys
(COMMAND keys active)
REQUEST RELEASE key Change between local and remote mode (in local mode the
COMMAND keys EQUIP ON/OFF and CHANGE OVER are
active)
Ed. 01.02 1-23

RCSE 443 RMMC
Station status indication (area EQUIPMENT-DETAILED STATUS-STATION, see Fig. 1-11),
currently no indication (defined for further use):
MAINS OFF yellow Mains power supply of station is switched off
ENV ALRM red Multiple purpose (e.g. intrusion alarm, fire alarm)
ANT FTY red currently not used
OTHER WARN yellow Miscellaneous communication and protocol errors
Commands for change mode (area EQUIPMENT-DETAILED STATUS-COMMAND, see Fig. 1-11):
EQUIP ON/OFF key Switching on/off station (after actuating REQUEST RELEASE
key), local mode is active, ENABLED indication is switched on
CHANGE OVER key Transmitter is changed over to other antenna (after actuating
REQUEST RELEASE key), local mode is active, monitors are
both in bypassed mode
1.4.2.6 Control Facilities for an attached PC with ADRACS User Program
Standard operating software for the specific NAV-systems is used. The following listing refers basiĆ
cally to navaids (with implemented functions valid for MLS).
The attached terminal has the following control facilities:
- to enter passwords for different security levels,

- to select a defined subsystem to obtain subsystem data,
- to display subsystem additional status indications,
- to display Basic and Auxiliary Data Words,
- to display transmitter data (frequency, ..),
- to display executive monitor alarms and alerts,
- to display executive monitor alarm and alert limits,
- to display executive monitor numerical results,
- to display maintenance data (BITE data, BITE results, .....),
- to deny/grant local control mastership,
- to input/change Basic and Auxiliary Data Words,
- to input/change transmitter data (frequency, ..),
- to input/change executive monitor alarm and alert limits (this capability is only available using
the highest security level password),
- to switch equipment ON/OFF,
- to switch subsystems to standby equipment and redundant components
(where applicable),
- to switch the runway configuration (AZ/BAZ conversion, EL control),
- to restart equipment,
- to input dialing numbers for autodialing modems.
1-24 Ed. 01.02

RMMC RCSE 443
1.4.3 General Data CTU and RWY-SELECT
1.4.3.1 Housing
For standard applications the CTU and RWY-SELECT panels are mounted as a front panel to a 19
inch subrack which is mounted in a 19 inch housing (Fig. 1-9). For special applications it can also
be mounted in 19 inch racks or control consoles. The RWY-SELECT panel is an ILS application and
only installed when required and, if not equipped, replaced by a blank panel (see Fig. 1-9).
1.4.3.2 Power Supply

Input: DC +5 V (from REU) or
14 ... 70 V with built-in DC/DC-converter
AC 85 ... 264 V with built-in AC/DC-converter
1.4.3.3 Components
- Processor unit 8051 (PU-51) with generic software (firmware) to control the displays and key acĆ
tivations
- CTU-panel with Status LED/Select Keys
- RWY-panel with Status LED/Select Keys
1.4.3.4 Subsystem Status Indication (CTU Panel)
NORMAL green Normal Operation

of operations (i. e. No Warning and No Alarm Condition).
WARNING yellow Warning (Alert)

- Transmitter(s) OFF
- Equipm. initializing or (MLS: AZ/BAZ) reconfiguring
- Primary Equipment shut-down by monitor
- Limited Monitor Configuration (only one executive)
- Local Access (local panel or attached terminal)
- Monitor Bypass (one or both)
- MLS: Non-essential data shut-down
- MLS: C-band sync switched off
- Battery operation
ALARM red Alarm

- Subsystem shut-down
- Out-of-tolerance signal(s) while monitor in bypass
Ed. 01.02 1-25

RCSE 443 RMMC
1.4.3.5 System Status Indication (RWY-SELECT Panel)
OPERATIONAL green Normal Operation

All subsystems required for operation in the designated
category of service are switched on, initialized and fully
serviceable. It is also required that all subsystems
are under remote control (no Warning, no Alarm).
DEGRADED yellow Degraded, Warning (Alert)

Any condition of a subsystem, that would impair the
system availability or continuity of service
(De-Categorization).
Initialization or (AZ/BAZ) reconfiguration.
SHUT DOWN red Alarm

- Any subsystem OFF.
- Any shut-down of a subsystem.
- Local control of a subsystem.
1.4.3.6 CTU Switch Controls
For the CTU function the following controls are available:

BRIGHTNESS UP Increase brightness of indicators
BRIGHTNESS DOWN Decrease brightness of indicators
ALARM SILENT Visual and audible alarm reset
LAMP TEST
1.4.3.7 RWY-SELECT Switch Controls
Runway select switch including indication (ENABLE) for clearance and availability.
1.4.4 Conformity and Licensing Approval
The RCSE 443 device complies with the requirements of EC Guideline 89/336/EEC in its implementaĆ
tion.
Individually, the device fulfills the requirements of the following EMC Guidelines:
- EN 55022 1998 Emission Tests
EN 61000-3-2 1995
EN 61000-3-3 1995
- EN 55024 1998 Immunity Tests
(EN 61000-4-2 1995
EN 61000-4-11 1994)
1-26 Ed. 01.02

RMMC RCSE 443
1.4.5 Safety Precautions
1.4.5.1 Work on the Equipment
In order to avoid risks to persons and consequential damage to subassemblies, the DC-converter
has to be switched off prior to removing or inserting a subassembly or prior to removing a plug-in
connector.
1.4.5.2 Handling electrostatically sensitive 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. We refer to the customer documentation of the
manufacturer.
Subassemblies which contain electrostatically sensitive components are
marked with this symbol.
If any of the maintenance personnel need to touch one of these subassemblies, they should place
both hands flat on a grounded conductive surface for a few seconds to eliminate static charges. The
subassembly can be touched - preferably at an insulator (board edge, lever mechanism, etc.) - as
soon as the potential has been equalized in this manner. It is advisable to avoid touching the contacts
of the plug-in connectors, the conductor paths and the components themselves. Some of the subasĆ
semblies must be left in their antistatic packaging or plastic bags as long as possible. The special
procedures described below should be followed when subassemblies and plug-in boards are reĆ
placed within the framework of repair and maintenance activities, due to the risk of damage to electroĆ
statically sensitive components.
To remove a subassembly:
- Switch off the system before beginning the replacement procedure.
- Eliminate any static body charges by touching the frame of the grounded rack with both hands.
- Remove the subassembly and lay it down on a bench with a grounded conductive worktop.
- Pack the subassembly in an antistatic plastic bag and send it off to the manufacturer for repair.
To install a subassembly:
- Eliminate any static body charges by touching the frame of the grounded rack with both hands.
- Remove the subassembly from the antistatic plastic bag.
- Install the subassembly.
- Switch on the system again.
1.4.5.3 Using Lithium Batteries
Always read the label on the battery.
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.
1.4.5.4 Observation of safety regulations

In addition to the above-mentioned instructions for avoiding damage and injury, locally valid safety
regulations should always be observed.
Ed. 01.02 1-27

RCSE 443 RMMC
1-28 Ed. 01.02

RMMC RCSE 443
1.5 SHORT DESCRIPTION
1.5.1 General Overview RCSE 443
Fig. 1-12 shows the structure of a typical ILS remote control system. The central unit is the RCSE,
which is connected to the stations of the instrument landing system via dedicated lines. It includes
the REU and the INC as standard components. The REU is also used for the RMC 443 and also for
the NAV-LCU 443 in the VORTAC (or VOR/DME) shelter. Therefore the design of the REU is modular
in order to be adaptable for the different applications. The block diagram below shows the REU with
the 7 available boards, which may be present in one of the existing seven PC-slots. The maintenance
functions are controlled by a PC system via the communications interface of the REU. In addition, a
connection to a maintenance center (RMC) is available via the dialing modem (or ISDN modem) and
the PTT. The control and indication panels are largely identical. The control panel is black with inscripĆ
tions in white; the recessed, transparent fields are half back-illuminated with red, yellow and green
LED arrays. A separate text field with a four character red LED display indicates the assigned stations
or other text in the top row for each system. The power supply is always +5 V and is obtained either
from the REU or from a separate DC converter.
115/230 VAC (or alternatively 36 ... 72 VDC) Network interface link (optional) In/Out analog
J18/19 S12 OIO 1/2/3
REU AC/DC or 5V Processor Board

DC/DC +12 V P4N 486 INC ADC OIO
Converter X4
-12 V
PC Backpanel
Modem Backpanel
PC1 Serial
PC2 Interface Board
SIB modem bus
LED SIB
SW1
Modem 1) Modem 1) Modem 1)3) Modem 1)2)3) Modem NFK-29
5)
NFK-29
5)
LGM 1 LGM 2 LGM 3 LGM 4 ZUA/ZU1 1 2
RCSE
Connector Backpanel with Protectors
1a2 2a2 1sA 1sB LGM1 LGM2 LGM3 LGM4 ZUA NFK-1 NFK-2 2sA/ 2a1/ 1+2a3/ 1a1/ 1a3 2a3 IN/OUT
422 CTU 422 RSU
6) 5)
3) 2) 2) 4)
3) 5)
4)
PTT 1) normally dialing modems

PC1
PC2 (analog CTU LGM28.8 or LGM64K are used
diagnosis or S0) 2) alternatively the ILS system
can be connected at LGM4
using an LGM1200MD
LLZ GP FFM MM OM modem
RWY 3) MK20A stations are connected
RMC SELECT via dedicated line modems
lLGM9600H1 (half duplex mode)
4) alternatively RS422 connection
Printer REU+INC DME to CTU via LGM Extender 2 Unit
at LGM4
5) alternatively Multiplexer RS232
PC ILS Navaids System 2) 3) for dedicated lines to ILS stations
driven by 1a3connector
6) RSU with 'old' indication panel
optional RPU can be connected (see
section 1.2.2.1)
Fig. 1-12 RCSE, block diagram (with one ILS Navaids system), example
Ed. 01.02 1-29

RCSE 443 RMMC
1.5.2 Control Tower Unit CTU
The CTU is designed to be installed in the ATC control tower. It consists of a front panel, which indiĆ
cates the status of each of eight NAV subsystems with one green, one red and one yellow LED, and
can be enhanced with the RWY selector, which in ILS/MLS installations indicates the general status
of two approach systems with four LED's each, and which has a key switch for selecting the desired
approach direction. Once again, it is possible to cascade additional units. An external line termination
at the end of the cascaded units is not necessary.
1.5.3 Maintenance Data Terminal

The navigation systems can be controlled via a maintenance data terminal in local mode, for the purĆ
poses of first setup procedure, maintenance and flight measurements. The PC control software for
the various NAV systems must be installed on a portable PC system.
The following PC system configuration is recommended:

- Processor Pentium 90 or better (IBM PC/AT compatible)
- 32 MB RAM, min. 1 GB HDD, VGA adapter, CD-ROM drive
- VGA color monitor
- control via mouse or comparable
- two serial interface connectors
- any 32-Bit version of Microsoft WINDOWS operating system
- min. 10 MB free disk space on HDD
NOTE: The PC control software running on the Maintenance Data Terminal is ADRACS. For deĆ
tailed information on recommendations on PC and others see technical manual of
ADRACS (Code No. 83140 55324).
1.5.4 Principle of Operation
The REU is the central unit of the Remote Control and Status Equipment (RCSE 443), thus responsiĆ
ble for the functions which control the data communication sequences and organization. It also hanĆ
dles higher-level system functions. The functions performed by the REU can be subdivided into 3
groups:
- Internal functions
- Setting the interface parameters
- Interrupt control of the interfaces
- Data backups
- External functions/Communication
- Periodical request of status data (master)
- Control of polling of the maintenance data of a selected station with the PC program (slave)
- Forwarding control commands from the control panel to the station concerned (slave)
- Forwarding the status, history status and maintenance data to the PC and RMC (slave)
- Forwarding all status changes to the RMC (master)
- Driving the control and indication panels
- History memories
- Access management
1-30 Ed. 01.02

RMMC RCSE 443
- System control (according to priorities; optional)
- Runway selection (RWY 1/2 SWITCH)
- Runway selection enable (SWITCH CONTROL)
- Operation/programming with the PC (PC CONTROL)
- Dual-face interlock
- Forced switching off of the LLZ, GP, markers and FFM
1.5.4.1 Internal Functions

Whereas the interface parameters have only to be set once when the system is started up, selection
of the communication paths and data back up are recurring tasks. The respective communication
interface is selected via the interrupt-driven Serial Interface Board (SIB). The connections of the dialĆ
ing modems are set up via the modem interface in accordance with V.25bis conventions.
All the data necessary for the RC system for running correctly (i.e. the operating parameters) are
saved within a file in the 'RAM side' of the flash disk (on processor board P4N 486). The actual REU
application program and the operating system (MS-DOS) are stored in the 'EPROM side' of the flash
disk (on processor board P4N 486) in form of normal MS-DOS files. The EPROM/RAM side of the
flash disk (on processor board P4N 486) is managed by MS-DOS.
When the system is started up, the application program and the configuration file are loaded by
means of the AUTOEXEC.BAT file (AUTOmatic EXECution BATch). During the initialization procedure,
a checksum is figured out for the configuration file (CRC) and compared with the checksum stored
in this file, to make sure that the file does not contain any errors and has not been modified in an unauĆ
thorized way (the configuration file can only be modified by authorized persons).
Whenever the synchronous and asynchronous interfaces are used for communication, either a CRC
(Cyclic Redundancy Check) checksum in form of two bytes is appended to the telegrams, which enĆ
sures extremely reliable data transmission, or at least a parity bit is set.
1.5.4.2 External Functions/Communication

Each time an attempt is made to communicate, the REU must check whether or not the requested
procedure is actually allowed according to the control message. The command is not executed until
confirmation is received. Otherwise, an error message is generated. If a transmission error occurs,
an answer message is never generated.
1.5.4.2.1 Designation and Storage of Events

Events are all confirmed recognized condition changes of a subsystem, regardless of whether they
are reactions to errors, control commands or parameter changes which have been placed into effect
(not in TEST mode), as well as communication errors. All events are provided with the identity and
type of the affected device as well as a time label, and stored internally in non-volatile memory. Data
retention is limited to 100 entries. The entries may be deleted completely or in part through operator
functions or transmitted through the user interfaces to a maintenance terminal.
1.5.4.2.2 Error Handling

Communication errors are acknowledged with corresponding error codes. Every error recognized
during data checking leads to the discarding of the corresponding telegrams.
Ed. 01.02 1-31

RCSE 443 RMMC
1.5.4.3 System Control
The REU manages the priorities of RWY SWITCH, SWITCH CONTROL and PC CONTROL. It also disĆ
tinguishes between two operating modes:
- With DUAL FACE INTERLOCK:
Only one ILS system at a time is allowed to radiate a signal if the runway has ILSs on both sides.
- Without DUAL FACE INTERLOCK:
Each ILS system can be switched on and off separately if there are two intersecting or parallel apĆ
proach directions.
The operating mode is preset in the configuration file. The REU also controls forced switching off of
the GP, the MARKER and the FFM, if the associated LLZ indicates an ALARM or a DATA COM ERROR
or is set to LOCAL MODE, or if the associated FFM indicates an ALARM (time-delayed, 1... 60 s).
"Automatic disable on/off" is specified separately in the configuration file for the GP, Marker and FFM.
1.5.5 Interfaces to local Installations

1.5.5.1 NAVAIDS/ILS Systems
The NAV-LCU communicates with the NAV systems through the existing RS232C or RS422 interĆ
faces with the current unchanged protocols. The transmission rate is set as high as possible, dependĆ
ing on the type and quality of the link. Up to three NAV systems can be connected to a NAV-LCU
(for example: CVOR or DVOR, TAC 453 or DME 415 and ELTA).
The individual NAV systems of a station are controlled through serial interfaces (via SIB), or as an opĆ
tion through parallel interfaces (via OIO). Navaids 400 and S4000 systems C/DVOR, DME/TACAN
(DME 415/TAC 453 and ELTA; via IOM) are connected through serial interfaces, while the older device
generation (D)VOR-3000 as well as FSD-10/FTA-13 are linked in parallel as necessary.
For the incorporation of an ILS, the NAV-LCU is installed in form of the RCSE 443 in the engineering
area of the associated airport. With this variation, the individual ILS stations are linked by means of
dedicated lines.
Corresponding to the modems of the station, the ZU1 or ZUA signal converters or the LGM 28.8/64K
modems are employed for data transmission. Cyclical line polling is performed through the NFK29
low-frequency node, to which up to 6 dedicated lines may be connected. Alternatively a dedicated
line modem LGM1200MD (in party line operation mode) can be used instead of ZUx modem and star
distributor NFK. A second alternative is the usage of a Multiplexer RS232 board instead of a star disĆ
tributor NFK to build RS232 resp. RS422 dedicated line connections to ILS stations. The data transĆ
mission rate using ZU1 modem is 600 Bd, using LGM1200MD modem it is 600 or 1200 Bd and using
LGM28.8 modem it is 4800 Bd. To connect MK20A ILS equipment to the RCSE 443 the LGM9600H1
modem is used in half duplex mode.
1.5.5.2 On-site Devices
Additional devices and in-house technical installations may be monitored through discrete line conĆ
ditions. The OIO (Optocoupled-Input-Output) card with 24 + 8 discrete inputs/outputs is provided
for this purpose. This card is connected directly through the bus and controlled by its own driver proĆ
gram.
1-32 Ed. 01.02

RMMC RCSE 443
The configuration - that is, the assignment of specific inputs to specific devices as well as the definiĆ
tion of the allocated signals - is performed through the local maintenance terminal. The plug-in unit
is designed for signals of 5 V, while other versions for 12 V or 24 V are also optionally available.
1.5.5.3 ADRACS Interface to local PC (Laptop)
The functions for settings and maintenance are executed by a local control PC (laptop). In order to
simplify the operations, communications may take place through the NAV-LCU and not directly at
the navigation device (no plug switching of the V.24/RS232C interface). The laptop used for local
ADRACS operation is connected through an RS232C serial interface with a configurable baud rate.
The concept of control and message telegram transmission is also applied here. In the case of a failĆ
ure, if the queried device does not respond after a configurable repetition, a message is displayed
to the user. The telegram structure corresponds to an asynchronous protocol which is specifically
adapted to the remote controls of the navigation system.
The telegram is composed of bytes (1 byte = 8 bits). Each byte is limited by a start bit and a stop bit.
A maximum interval of 1 ms each occurs between the data blocks of 10 bits which have been generĆ
ated. By setting time loops at the beginning of the transmission, it is thus possible to recognize imĆ
proper telegram lengths. Data security is performed by a Cyclic Redundancy Check (CRC).
The ADRACS program is described in more detail in the corresponding Technical Manual ADRACS,
Code No. 83140 55324.
1.5.5.4 Interface for remote Data Transmission

Modems for remote data transmission is connected through a serial, asynchronous interface.
1.5.6 Interface to LAN Network

The base for network interfacing is the P4N processor board with Ethernet controller/connector which
is available for the RCSE. The network interface feature allows to transfer the information of the RCSE
containing the status of all connected systems via SNMP (Simple Network Management Protocol).
SNMP is a TCP/IP protocol that generally uses the User Datagram Protocol (UDP) to exchange mesĆ
sages between a Management Information Base (MIB) and a management client residing on a netĆ
work. Since SNMP does not rely on the underlying communication protocols, it can be made available
over other protocols, such as XNS or DECnet etc. A generic "NAVAIDS MIB" was defined in order to
mirror the status of the REU. The configuration of the network link feature is implemented in the speĆ
cific SIT-file of the RCSE installation.
The performance of the RCSE is enlarged by the availability of a network interface, which allows acĆ
cess to the REU via Ethernet and SNMP. The following characteristics are accessible:
- Status of the REU
- Status of the stations connected to the REU
- Transfer of status changes to up to four hosts (IP address) using SNMP trap function. This trap
contains the new status.
- Definition of a gateway (IP address) for routing to other subnet.
- Definition of the IP address of a NTP-server in order to request time status every 10 minutes. InterĆ
nal time of REU is corrected correspondingly (accuracy : ±5 s).
- All IP addresses are defined in the associated SIT-file.
Ed. 01.02 1-33

RCSE 443 RMMC
1-34 Ed. 01.02

RMMC RCSE 443
1.6 RCSE SOFTWARE
The central feature of the RCSE/REU is an industrial PC system which uses MS-DOS (Version 5.0).
All the data required to run the remote control system correctly (operating parameters) is saved in
a file in an SRAM (flash disk).
The software is written in programming language ADA. The software and the operating system are
stored in the EPROM side of the flash disk as normal MS-DOS files. The RCSE software is subdivided
into the following functions:
- Initialization
- Communication routines
- Communication distributor/history memories/system control
- Subsystem data input
- System security
1.6.1 Initialization
When the system is started up, the configuration files (*.SIT, *.OIO. *.PTT) are loaded to the RAM side
of the flash disk (the user has access to the RAM side via ADRACS user program) and verified with
a CRC checksum. The communication channels are assigned according to the system configuration
and the interrupts for controlling the interfaces are defined.
The sequence table is then initialized for the connected stations (baud rate, channel number, telegram
type, etc.), the switched-line modems are installed and the telephone numbers are programmed.
All the flags, peripheral chips, HW and SW counters, multiplexers, tables, etc. must be set to a defined
initial state, which is also partly dependent on the contents of the configuration file. Finally, the passĆ
word is installed and communication is started.
1.6.2 System Control
The REU system incorporates a maintenance mode, which is controlled via a maintenance data termiĆ
nal (PC) or via an RMC.
The RCSE software controls certain system functions by setting/resetting software flags resulting
from error detection or status changes of hardware switches or keys on the CTU or INC. The states
of the flags are indicated on the CTU respectively INC panels.
- Data communication error
The software flag DATA COM ERROR of a station is set in the REU software if an attempt to exchange
telegrams between the REU and the desired (selected) station fails x times in a row. The number 'x'
can be defined in the configuration file for each station.
The DATA COM ERROR flag is reset after each successful telegram exchange.
Ed. 01.02 1-35

RCSE 443 RMMC
- Runway selection
The selection of the active runway system is normally done via the CTU. The hardware switches
SW1/SW2 on the rear side of the CTU board enable or disable the selection of runway 1 or runway
2, which is done via the key switch on the front side of the RunWaY Select panel of the CTU. A telegram
is sent to the REU every 2 seconds containing the status of the key switch and the position of the
SW1/SW2 hardware switches. The REU sets the flag RWY-1/2-SWITCH, if the selection of the runway
is enabled (on CTU).
If the REU doesn't receive any Runway Select telegram from the CTU for more than 10 seconds, the
PC gets the permission to manipulate the RWY-1/2-SWITCH flag by actuating buttons within the
ADRACS user program. This only applies until another valid telegram is received from the CTU. OtherĆ
wise, the PC is not allowed to alter the RWY-1/2-SWITCH flag.
- INC control of stations (switch control)
The INC control of a station is only possible, if the corresponding runway is not active, i.e. the flag
RWY-1/2-SWITCH flag is set to 0. The PC control of the INC panel controlled station is not allowed,
only the PC control of other stations of the runway is possible.
- PC control of stations
Sending telegrams to a station from PC (using ADRACS user program) is only allowed if the correĆ
sponding runway is not active and the selected station is not controlled by INC panel. To send comĆ
mands to the station (e.g. transmitter on/off) the PC user has to be logged in with a password level
> 2. If PC control is active the flag PC CONTROL is set.
- Dual-face interlock
The REU manages the two different operating modes for runway systems having ILS systems on both
sides. This mode is preset in the configuration file. The two modes are:
- With DUAL FACE INTERLOCK:
Only one of the ILS systems at a time is allowed to radiate a signal.
- Without DUAL FACE INTERLOCK:
Each ILS system can be switched on/off separately if there are two intersecting or parallel
approach directions.
- Automatic disabling of stations (Forced Shutdown)
For ILS or MLS systems it is sometimes necessary to do forced switching off of associated stations,
if a 'Main' station is in ALARM state. For the stations GP, LLZ and Marker it is possible to define two
'Main' stations in the configuration file. An 'ON'- and 'OFF'-time for each 'Main' station has to be
configured in the file, that define the switching on and off delays between alarm occurrence/disapĆ
pearance and the forced switching off/on of the associated stations. Additionally, the consideration
of a data com error in context with forced switching off can be defined in the configuration file (flag
ON-/OFF-CONTROL).
1-36 Ed. 01.02

RMMC RCSE 443
1.6.3 Communication Routines
The precondition for the establishment of a communications link is that there are identical protocols
on all terminal systems. Open communication between all user stations is then possible technically.
However, this may be restricted at any time, for organizational purposes, for instance. A switched line
connection with an analog (or digital) terminal, which also allows telephone operations, exists as a
network system connection for cost-effective data communication through the public telecommuĆ
nications network (PTT).
Communication with the terminal equipment is implemented using different types of telegram. The
telegrams are converted by special communication routines. The data answers are checked in addiĆ
tion, and either forwarded to the communication distributor or ignored if applicable with an error mesĆ
sage. A special communication routine is used to control the dialing modem, so that switched line
connections can be set up automatically. Optionally communication with an existing LAN network is
possible via SNMP protocol using the Network Interface Link of the P4N processor board.
1.6.3.1 Communication Distributor/History Memory
The communication distributor RCSE can be imagined as a kind of data "turntable" for the different
telegram types between the orderers of the requested tasks. It receives data, checks it and redistribĆ
utes it. The distributor controls the chronological sequence of all communication functions. The
RCSE only performs the role of the master when the MAIN STATUS is requested from the stations
and when the general status is signaled to the RMC as a result of a status change. All other serial
interfaces are polled in response to a request. The MAIN STATUS of stations directly connected is
requested by means of a polling mechanism.
Communication with the stations is periodic and controlled by sequence tables listing all the confiĆ
gured stations. The structure of the tables differs according to the requirements of the other communiĆ
cation channels. Due to the fact that no stations not belonging to the system are configured, the seĆ
quence tables and the polling cycles are both shortened. If there are two low-frequency nodes, the
stations are split between two sequence tables and two of them are addressed simultaneously. The
length of the polling cycles is thus halved.
The control program monitors the time frame of the individual telegram sequences. If an answer mesĆ
sage is not received from the polled station within the specified frame time, the polling continues with
the next station in the table. After 'n' unsuccessful attempts (value 'n' see configuration file),
DATA_COM_ERROR is set for the station concerned, and the history memory is updated due to the
change in the MAIN STATUS. The status information which is received is checked for changes stored
(if need be) in the history memory.
Since the devices at the interfaces are polled with different protocols, it is necessary to preprocess
the data at the interface uniformly for the system. It is also possible to incorporate new protocols non-
reactively into the existing REU software at later date because of this separation.
The functions at the station are realized on the one side by the application software of the REU and,
on the other side, by the software in the maintenance PC. As is the case with remote diagnosis, the
PC assumes the interface function to the maintenance engineer, while the REU establishes commuĆ
nications to the individual devices. As a result of the multiple serial interfaces, a quasi multitasking
structure of the REU software is necessary. Communications for the serial interfaces to the individual
devices takes place through the V.24/RS232C or RS422 interfaces.
Ed. 01.02 1-37

RCSE 443 RMMC
The application is processed in specific structures. In the Accept section, the tasks are accepted by
the task requester and queued for processing. Execution is asynchronous to the task request. In the
Operation Controls section, the tasks are, according to the current status of the subsystem, discarded
or additionally detailed for execution. In the Execution section, the tasks are executed, by polling other
devices, for example, or by assigning other Ada subsystems.
1.6.3.2 Subsystem Data Input
The programming of site specific data is required for all navaids equipment with microprocessor-
controlled signal processing for transmitter signal generation, built-in testing and monitoring. The
input/change of variable system parameters for the transmitter and for the monitor is executed by digiĆ
tal data entry. The data input via the keyboard of a maintenance data terminal in a menu technique
is a comfortable method to enter data to the equipment.
For integrity reasons, the data entry (input/change) is only possible in the maintenance mode (moniĆ
tor bypass on) and besides, corresponding password procedures are implemented. In addition to
local control, executive monitor alarm and alert limits can be changed remotely by means of an atĆ
tached terminal (beside the input/change of Basic and Auxiliary Data words).
The capability of remote data input of Auxiliary Data words is absolutely necessary. The remote
change of monitor alarm limits can ease the flight test procedure.
Due to the fact that at the remote site it should be possible to change parameters which are critical
to safety, the monitor-bypass mode (maintenance mode) is not identical to the local/remote control
switching function on the Local/Remote Communication Interface (LRCI), i.e. the following switching
functions are independent:
- Remote control/local control
- Test mode (MLS only) and
- Monitor-bypass mode (maintenance mode)
For Navaids 400 and S4000 systems only the monitor-bypass mode is used. For MLS and DME/P
the following definitions are to be applied:
- Monitor-bypass mode defines that this specific monitor is not executive (no switch-over-shut
down initiation, even if the signal is out-of-tolerance).
- Maintenance mode defines that the equipment to be monitored is under control of the maintenance
personnel (no monitor executive function to this equipment).
1.6.3.3 Communication with Navaids 400 and SYSTEM 4000 Stations
The REU is the controlling, active unit for this type of communication. The stations receive control
messages in a fixed polling cycle and respond with answer messages; they cannot issue an answer
message without first receiving a control message (MASTER/SLAVE principle). A transmission cycle
thus always consists of a control message and an answer message.
The configured stations are not accessed democratically, i.e. all the primary stations LLZ-1, GP-1,
LLZ-2 and GP-2, but only one of the other stations, are addressed during each polling cycle. The
time until the secondary stations are updated is correspondingly longer. It is also generally possible
to communicate with two ILS stations on one channel, or with one or more VOR systems. If the remote
1-38 Ed. 01.02

RMMC RCSE 443
station is a NAV-LCU, all the instruments connected to it can be addressed individually. The channel
assignment is always freely selectable. During normal operation, only the MAIN STATUS is requested
from all stations.
If a station is selected with the control unit however (INC or PC), the system status data and the mainĆ
tenance data (PC CONTROL) are requested from this station as well. The refresh rate of all the system
data is reduced as a result.
1.6.3.4 Communication via Open Interfaces
Open interfaces are ones which can be used for maintenance operation, e.g. the PC interfaces and
the RMC connection. It is not possible to begin maintenance operation (i.e. control operations) via
different interfaces at the same time, but simultaneous status indication is possible. This is governed
by access levels 1...5. Operation at levels 3 to 5 (i.e. control of the system is allowed) is only possible
if no other sessions are in progress simultaneously. In order to protect the RCMS system against unĆ
authorized access, the REU demands a modifiable 6-character password, which is transmitted toĆ
gether with the number of the access level (password level).
The REU operates in slave mode with this type of communication, i.e. no telegrams are issued without
a prior request. The PC control program (ADRACS) requests the system status or the maintenance
data (PC CONTROL) of a particular station via the PC or RMC interface. This data is then forwarded
by the REU to the station, if necessary (control message). The answer data which are returned by the
station is forwarded to the PC. The REU is informed about the start of each PC communication sesĆ
sion by means of the LOGIN command (password), and about the end of a session by the LOGOUT
command. The LOGIN procedure does not allow more than three input attempts.
If three unsuccessful attempts are made, all further inputs are blocked for 3 minutes. This interval is
incremented by 1 minute with each additional, unsuccessful attempt, and finally increased to 60 minĆ
utes after the 10th failed attempt. For a new site, where user and passwords have not yet been arĆ
ranged, user 1 is free for the first access to the system (all other users are blocked).
1.6.3.5 History Memories
All system changes (RWY 1/2) and all changes in the status of a station which are not caused by RWY
CONTROL or SWITCH CONTROL are stored in a history memory in the REU. This stack is physically
located in the 'RAM side' of the flash disk on processor board P4N 486. When the REU is initialized,
an initial event (history event) is stored for each approach direction and subsystem. Each history
memory can be erased by the control program for a particular date. A status change is stored after
the new MAIN STATUS has remained unchanged for at least one minute. If the status changes conĆ
stantly, only one change per day is recorded.
1.6.3.6 Control of Indications
The indications are derived continuously from the MAIN STATUS telegrams, and output to the reĆ
questing point when the general status is polled.
Ed. 01.02 1-39

RCSE 443 RMMC
1.6.4 System Security
The Maintenance Data Terminal uses passwords and user identifiers to prevent from unauthorized
access to the system. This is implemented in all the maintenance menus active for the different subĆ
systems (e.g. ADRACS for Navaids 400 systems) for five levels of security. Not having an open system
communication concept but only a point-to-point connection, access to the maintenance data terĆ
minal is possible only at especially assigned locations. These areas are usually only accessible by
authorized personnel.
In addition to the maintenance data terminal security with the above passwords, the start of data-
transmission at the RMC's for starting communication on switched public telephone lines is secured
by a variable password with '6 characters' including defined login sequences. To increase the system
security, the data communication with control and message telegrams for switched public telephone
lines to a subsystem can only start after establishing a switched line connection with the subsystem
site. This ensures that authorized telephone numbers are allowed communication accesses to a subĆ
system.
For the autodialing procedure caused by a change of subsystem-status, this process of communiĆ
cating is straight forward. Having established the connection, the RMC sends control telegrams and
the subsystem replies with the message telegrams.
In case of a desired communications link from an RMC, the RMC dials the number of the subsystem
and gives the message to call the RMC back. Now the subsystem reorganizes the communication
with the configured fixed programmed telephone number of the defined RMC. With this procedure
access by other than authorized personnel is avoided.
The security of the data transmission itself is ensured by the master/slave concept employed with its
defined control and message telegrams within fixed time frames. Each telegram is terminated by a
two byte CRC. The data communication is monitored and displayed on the INC.
1.6.5 INTERNET Interface
The PPP protocol has been established in the Internet standard for the transmission of data packets
on serial transmission paths with the following advantages:
- error recognition by means of CRC in accordance with CCITT in an asynchronous HDLC frame
- support of different protocols such as TCP, UDP, IP-Datagrams, DECNet, Apple-Talk, Novell, ...
- better support of the connection establishment procedure on the switched lines
The serial communication link between the RCSE and the RMC is a link on a switched line of the public
telecommunication network. The packets of the IP entity are transmitted in a PPP frame and with a
fast modem through the serial line.
Additionally to the serial communication link using the PPP protocol a RJ45 interface (10BASET) avaiĆ
lable as an option of the P4N processor board exists to connect the RCSE to an existing LAN network
using the SNMP protocol.
1-40 Ed. 01.02

RMMC RCSE 443
1.6.5.1 PPP Definition
The PPP protocol represents an implementation of the data link layer (OSI level 2), and makes a
method for transmitting of datagrams through a serial point-to-point link available. The protocol
may be subdivided into three main components:
- a method for encapsulating of datagrams on serial links
- a Link Control Protocol (LCP) for the establishment, configuration and validation of data link
connections
- a family of Network Control Protocols (NCP) for the establishment and configuration of different
network layer protocols (OSI level 3).
The PPP protocol utilizes the principles, terminology and frame structures of the specifications of ISO
3309 (HDLC or CCITT X.25 LAPB). The PPP applies the HDLC principle on an asynchronous serial
connection. The control principle corresponds to ISO 4335. The integrity of the data is ensured in acĆ
cordance with HDLC by a CRC-CCITT. Upon the establishment of a PPP connection, both stations
send LCP packets (link control). These packets serve to configure and test the link.
After the creation of the data link, the network layer protocol which is used by both sides must be conĆ
figured and established with NCP packets (for example: Internet, DECNet, Novell). After the configuĆ
ration of the link by PPP, information packets may be sent until the logical connection is canceled by
corresponding NCP, LCP packets. Determined by the clear standardization of the PPP by RFC 1331,
PPP implementations exist for SUN workstations (the BRXPPP used by Brixton Inc., for example) on
the one side and implementations for PC (the PCTCP used by ftp-Softw. Inc., for example) on the
other side of the link. These communicate with each other without problems.
1.6.5.2 SNMP Definition
The SNMP (Simple Network Management Protocol) is a TCP/IP protocol that generally uses the User
Datagram Protocol (UDP) to exchange messages between a management information base (MIB)
and a management client residing on a network. Since SNMP does not rely on the underlying commuĆ
nication protocols, it can be made available over other protocols, such as XNS or DECnet etc. A geĆ
neric "NAVAIDS MIB" was defined in order to mirror the status of the REU.
The SNMP interface provides the following features:

- SNMP agent
The SNMP agent is running if the REU is initialized properly.
- MIB access
Run the MIB browser.
- MIB information
Run the MIB browser to request the status of the REU and the connected stations. The community
name to read out data is "public". The data in the MIB must match the status shown at the INC panel
of the RCSE.
- MIB information update
The REU updates the information of the MIB. Information is transferred to the MIB if any status is
changed.
Ed. 01.02 1-41

RCSE 443 RMMC
- Trap handling
If a change in the status of the REU occurs a specific trap is sent. A maximum of four trap hosts
can be addressed. The IP address of the trap hosts is part of the SIT-file that is used to initialize
the network interface. The traps propagate the new status. Following traps are specified:
S REU status trap
S PC-control_1 trap
S PC-control_2 trap (only available if a second runway (ILS) is configured in the SIT file)
S Runway-status trap (ILS)
S Station status trap
- Diagnosis channel of REU
Using the diagnosis channel of the REU with a connected PC following information is available:
S data (addresses), used during initialisation
S trigger action by the REU on a NTP request; this is done, while a network is configured;
it depends on the definition of a host if there is really a request. The trigger informs only that the
REU has tried to get the actual time from the NTP server.
S transfer of data to the SNMP agent
1-42 Ed. 01.02

RMMC RCSE 443
Description and Operation Installation
CHAPTER 2
INSTALLATION AND INITIAL SETUP
2.1 GENERAL
This chapter describes the installation and initial setup procedures for the RCMS 443. The equipment
and system configurations are dependent on the local situation and may vary accordingly. The RCMS
hardware configuration is adapted to the site with the software by configuration files.
The installation and configuration of the optional Network Interface Link provided via P4N processor
board is described in section 2.3.5.
2.2 INSTALLATION
2.2.1 General
The installation procedures for the various components of the RCMS 443 are dependent on the local
situation. A default configuration is therefore assumed, consisting of an RCSE 443, a CTU and RWY-
SELECT, a PC with a printer and an RMC-R/RMC-C (see Fig. 2-5).
2.2.2 Cabling (RCSE/CTU+RWY/PC/RMC)
- Set the AC and DC power switch on the rear of the subracks to "off": lower position.
- Connect a ground or frame cable.
- Connect the power supply (either AC or DC, depending on the configuration).
- Connect the external equipment (see Fig. 2-5).
CAUTION
If a DC power supply is used, take care to connect it with the correct polarity. Make sure
the correct mains voltage is set if an AC supply is used (REU: 115 or 230 V).
VAC 115/230 V 2AT Mains switch AC VAC 115/230 V 2AT
NFK-1 NFK-1
Mains fuse
6.3AT AC, F2H/250V 6.3AT
VDC VDC
36-72 V 36-72 V
+- +-
NFK-2 NFK-2
DC/DC DC/DC
ON ON
OFF OFF
DC power switch
+ - REU-subrack: REU-subrack:
36 ... 72 V
~
AC-Power 115/230 V (selectable)
DC-Power
Supply Supply
Equipped with DC/DC-converter Equipped with AC/DC-converter
Fig. 2-1 RCSE system cabling, power supply
Ed. 01.02 2-1

RCSE 443 RMMC
Installation Description and Operation
VAC 85V...264V VAC 85V...264V

DC power switch Mains switch AC
DC/DC DC/DC
I I
Mains fuse
0 AC, F2H/250V 0
CTU-subrack:
14 ... 70 V
+-
DC-Power ~
J3 J4 AC-Power J3 J4
Supply VDC J17 Supply VDC J17
CTU-
-+ subrack: -+
85 ... 264 V
Equipped with DC/DC-converter Equipped with AC/DC-converter
Fig. 2-2 CTU system cabling, power supply
- Connection of ILS stations via LGM1200MD party line modems:

Use R/C-line termination (600 ohms II 47 nF) as shown in Fig. 2-3:
RCSE 443
REU INC
LGM1200MD**)
*)
*) 600 ohms II 47 nF
**) replaces ZU modem and dedicated lines 2-wire
star distributor NFK29
*) *) *) *)
LGM1200MD LGM1200MD LGM1200MD LGM1200MD
LLZ FFM Marker LLZ
Fig. 2-3 ILS stations connected to RCSE via party line modems LGM1200MD (example)
- Connection of (D)VOR S4000 stations:

Replace cable to MB-E1/J11 and MB-E2/J9 with AF cable 24009 28099 and connect SubD
connector to 2a3 of RCSE. If necessary, use the 97240 28168 extension cable.
(D)VOR 4000
AF Extension AF Cable
97240 28168 24009 28099
MB-E1 J11
J9
MB-E2
rear side
Fig. 2-4 (D)VOR S4000 station connected to RCSE (example)
2-2 Ed. 01.02

RMMC RCSE 443
2 (28.8)
LGM1
4 (64K)
RMC-C 2 (28.8)
LGM1
4 (64K)
RMC-R
PTT
Note:
2 (28.8)
4 (64K)
The overall length of a RS422 connection
LGM4
DVOR NAV-LCU line should be 1 km !

2a3
S4000 RS422 443 5) The overall length of a RS232 connection

line should be 15 m !
Terminal 2 (28.8) 2 (28.8)

(D)VOR 4) 4 (64K) 4 (64K)
RS232
Printer
2a3 LGM1 LGM2
PC2
COM1
ZUx 2a2
COM1
LPT1
PC1 diagnosis
1a2
RS232
RS232
RCSE 443
1a1
CTU+RWY J2
2a1
J1
RS422
2)
S12 OIO2 OIO1 LGM31) LGM41) 2) RS422
Dedicated
Lines J1 CTU+RWY J2
2-wire
16 IN
24 IN
2 2
16 OUT
8 OUT
Analog Control Control Navaids 400 3)

Signals Signals Signals Landing System DME/TAC
1) LGM3/4 is equipped with LGM9600H1 3) Alternatively to ZU/NFK dedicated lines

modem (half duplex, V.23) to connect the Navaids 400 landing system can be optional
an MK20A ILS system to the RCSE. connected via LGM4 using a modem
LGM1200MD (party line), see fig.2-3.
2) CTU is connected via LGM4 if LGM
Extended 2 Unit is used to prevent 4) (D)VOR S4000 connection, see Fig. 2-4
potential difference in case of long lines 5) Information to NAV-LCU 443 see annex
in Register 6 of this technical manual
Fig. 2-5 RCMS 443 system cabling, connections of peripheral equipment, example
Ed. 01.02 2-3

RCSE 443 RMMC
2.2.3 RCSE/REU, Pin Assignment of Interface Connectors
LGM1 1sA 1a2/PC1

VAC 115/230 V 2AT OIO 1 OIO 2 S12
NFK-1 LGM2 1sB 2a2/PC2 1

LAN
6.3.AT 2
VDC LGM3 2sA/422 2a1/CTU
36-72 V
+- 1AT
LGM4 1+2a3/422 1a1/RSU 1AT -12V +12V
NFK-2 1)
ZUA 1a3
DC/DC
ON IN/OUT 2a3
2)
OFF
1) prepared for DCF77 clock

2) connector not used
Fig. 2-6 RCSE/REU back panel, connectors
2.2.3.1 SubD 25 Pin Connectors NFK-1, NFK-2 (male)

NFK-1 / NFK-2 slot equipped with NFK29-1 board (used for connections via modem):
PIN ASSIGNMENT PIN ASSIGNMENT
1 F1 IN-A (2-wire Rx/Tx; 4-wire Rx) 13 Not connected
2 F1 IN-B (2-wire Rx/Tx; 4-wire Rx) 14 F1 OUT-A (4-wire Tx)
3 F2 IN-A (2-wire Rx/Tx; 4-wire Rx) 15 F1 OUT-B (4-wire Tx)
25 F6 OUT-B (4-wire Tx)
NFK1 / NFK-2 slot equipped with Multiplexer RS232 board (used for RS232/RS422 connection):
1 RS232 RXD Ch1 / RS422 +RXD Ch1 13 Not connected
2 not used / RS422 -RXD Ch1 14 RS232 TXD Ch1 / RS422 +TXD Ch1
3 RS232 RXD Ch2 / RS422 +RXD Ch2 15 RS232 GND Ch1 / RS422 -TXD Ch1
25 RS232 GND Ch6 / RS422 -TXD Ch6
2-4 Ed. 01.02

RMMC RCSE 443
2.2.3.2 SubD 9 Pin Connectors (male)
LGM1 used for LGM28.8 / LGM64K / LGM1200MD / LGM9600H1

1 La / SX2- (Tx-) 6 E / not connected
2 Lb / SX1+ (Tx+) 7 not connected
3 a2 / SR1- (Rx-) 8 not connected
4 b2 / SR2+ (Rx+) 9 not connected
5 G / not connected

5 G / not connected

5 G / not connected

5 G / not connected
LGM Extender 2 Unit used at one of LGM1..4 slots for external RS232 / RS422 connections,
e.g. to CTU in other buildings
1 DCD / +TXD 6 DSR / +RTS
2 RXD / -TXD 7 RTS / -RTS
3 TXD / +RXD 8 CTS / +CTS
4 DTR / -RXD 9 RI / -CTS
5 Gnd
1sA used for external RS232 connections

1 DCD 6 DSR
2 RxD 7 RTS
3 TxD 8 CTS
4 DTR 9 RI
5 Gnd
Ed. 01.02 2-5

RCSE 443 RMMC
1sB used for external RS232 connections

1 DCD 6 DSR
2 RxD 7 RTS
3 TxD 8 CTS
4 DTR 9 RI
5 Gnd
2sA/422 used for external RS422 connections

1 +TxD 6 +RxD
2 -TxD 7 - RxD
3 not connected 8 not connected
5 Gnd
1+2a3/422 used for external RS422 connections

1 +TxD (1a3) 6 +TxD (2a3)
2 -TxD (1a3) 7 - TxD (2a3)
3 +RxD (1a3) 8 +RxD (2a3)
4 -RxD (1a3) 9 -RxD (2a3)
5 Gnd
ZUA used for ZUA29

1 A12 (2-wire Rx/Tx; 4-wire Tx) 6 B22 (2-wire Rx/Tx; 4-wire Tx)
line amplifier
2 B12 (2-wire Rx/Tx; 4-wire Tx) 7 A21 (4-wire Rx)
used as
used as ZU
3 A11 (4-wire Rx) 8 B21 (4-wire Rx)

4 B11 (4-wire Rx) 9 not used
5 A22 (2-wire Rx/Tx; 4-wire Tx)
IN/OUT used as TTL Auxiliary I/O

1 AUX IN 1 6 AUX IN 6
2 AUX IN 2 7 AUX IN 7
3 AUX IN 3 8 AUX OUT 1
4 AUX IN 4 9 +5 V
5 AUX IN 5
1a2/PC1 used for PC1 (maintenance data terminal, PC)

1 DCD 6 DSR
2 RxD 7 RTS
3 TxD 8 CTS
4 DTR 9 RI
5 Gnd
2-6 Ed. 01.02

RMMC RCSE 443
2a2/PC2 used for PC2 (diagnosis terminal only, defined by internal software)

1 DCD 6 DSR
2 RxD 7 RTS
3 TxD 8 CTS
4 DTR 9 RI
5 Gnd
2a1/CTU used for CTU (RS422 connection)

1 +TxD 6 +RxD
2 -TxD 7 -RxD
5 Gnd
1a1/RSU used for 'old' RSU (RS422 connection)

1 +TxD 6 +RxD
2 -TxD 7 -RxD
5 Gnd
1a3 used for external RS232 connections

1 DCD 6 DSR
2 RxD 7 RTS
3 TxD 8 CTS
4 DTR 9 RI
5 Gnd
2a3 used for external RS232 connections

1 DCD 6 DSR
2 RxD 7 RTS
3 TxD 8 CTS
4 DTR 9 RI
5 Gnd
Ed. 01.02 2-7

RCSE 443 RMMC
2.2.3.3 64 Pin Connectors OIO 1, OIO 2 and S12
These connectors are optionally equipped together with optional OIO boards or an ADC board.
OIO 1, OIO 2, OIO 3 (S12 connector)* (Example: Assignment for variant 24 inputs / 8 outputs)

1 OUT 17 IN
Definition of inputs and outputs
2 OUT 18 IN
3 OUT 19 IN Vcc Vcc
4 OUT 20 IN
R**
5 OUT 21 IN a c
6 OUT 22 IN IN OUT
7 OUT 23 IN
8 OUT 24 IN c
log. 0= max. 1 mA
a
max. 35 V/150 mA
9 IN 25 IN log. 1= min. 10 mA
10 IN 26 IN ** depends on input voltage

11 IN 27 IN Uin R**
12 IN 28 IN 5V 560
13 IN 29 IN 12 V
15 V
1k
1,5 k
14 IN 30 IN 24 V 2,2 k
15 IN 31 IN
16 IN 32 IN
* Polarity of Input-pins: row a positive, row c negative

Polarity of Output-pins: row a negative, row c positive
Other variants of OIO PIN layouts exist:

TYPE PIN layout
32 inputs 1..32 IN
32 outputs 1..32 OUT
16 inputs / 16 outputs 1..8 IN
9..16 OUT
17..24 IN
25..32 OUT
8 inputs / 24 outputs 1..8 IN
9..32 OUT
8 outputs / 24 inputs 1..8 OUT
9..32 IN
S12 used for ADC or for other special applications
2-8 Ed. 01.02

RMMC RCSE 443
2.2.4 CTU, Pin Assignment of Interface Connectors
VAC 85V...264V
DC/DC
I
0
J1 CTU/RPU IN
J3 J4
VDC J17
J2 CTU/RPU SLAVE
-+
Fig. 2-7 CTU subrack, back panel connectors
2.2.4.1 SubD 9 Pin Connectors J1, J2
J1 used for CTU/RPU IN (female)

1 +RxD 6 +TxD
2 -RxD 7 -TxD
3 +CTS 8 +RTS
4 -CTS 9 -RTS
5 Gnd
J2 used for CTU/RPU SLAVE (male)

1 +TxD 6 +RxD
2 -TxD 7 -RxD
3 +RTS 8 +CTS
4 -RTS 9 -CTS
5 Gnd
Ed. 01.02 2-9

RCSE 443 RMMC
2-10 Ed. 01.02

RMMC RCSE 443
2.3 INITIAL HARDWARE SETTINGS
2.3.1 General Prerequisites
This chapter describes the prerequisites for first setup of the equipment and gives an overview of the
hardware settings. It presumes that the equipment has been factory-aligned and tested.
NOTE: More HW settings on boards used for NAV-LCU are described in annex (register 6).
2.3.2 Assignment of connected Stations (CTU and RWY-SELECT)

The top row of the CTU front panel contains vacant fields, which can be used for adhesive labels for
the connected stations to assign the status indications. The fields on the RWY-SELECT subassemĆ
bly should be inscribed in the same way.
2.3.3 Hardware Settings

All relevant parameters are normally set before factory acceptance has taken place. These parameĆ
ters are checked during the acceptance procedure. The figures show a default configuration of the
hardware settings, which may vary individually for each installation.
2.3.3.1 REU, Jumper Settings

Configuration of Connector Back Panel (CBP)
Standard Modem Assignment State of delivery setting:
1 A 1-2 (a-h) LGM-3 operated via 2a3 1
A 2 A 2
3 A 2-3 (a-h) LGM-3 operated via 2sA 3
1 B 1-2 (a-h) LGM-2 operated via 2a3 1
B 2 B 2
3 B 2-3 (a-h) LGM-2 operated via 1sB 3
1 C 1-2 (a-h) LGM-1 operated via 1a3 1
C 2
C 2
3 C 2-3 (a-h) LGM-1 operated via 1sA 3
1 1
D 1-2 (a-d) ZU-Modem operated via 1a3
D 2
D 2
3 D 2-3 (a-d) ZU-Modem operated via 2a3 3
1 1
E 2 E 2
a b c d e f g h i a b c d e f g h i
Default setting for specific configurations: = jumper set

LGM-2 distributed via NFK-2*
1
A 2
3
1
LGM x in dedicated line mode and distribution via NFK (FACElink):
B 2
NFK channel 6 externally with La/Lb of LGM modem. NFK channel
3
1 6 converts LGM output signal from 2 to 4-wire operation with speĆ
C 2
3 cial B64/B63 setting (see Section 2.3.3.4). Otherwise set NFK to 2
1 or 4-wire operation as normal with jumpers.
D 2
3
1
E 2
a b c d e f g h i
ZU-Modem distributed ZU-Modem distributed ZU-Modem distributed
via NFK-1 via NFK-2 via NFK-1 and NFK-2
1 1 1
A 2 A 2 A 2
3 3 3
1 1 1
B 2 B 2 B 2
3 3 3
1 1 1
C 2 C 2 C 2
3
3 3
1 1 1
D 2 D 2 D 2
3
3 3
1 1 1
E 2 E 2 E 2
a b c d e f g h i a b c d e f g h i a b c d e f g h i
Fig. 2-8 REU, configuration of CBP and default setting
Ed. 01.02 2-11

RCSE 443 RMMC
2.3.3.2 Processor Board P4N 486 Settings
x5 x10
x17 J11
x12
x18
x4 3 2 1
J9
2 1
J3
x14
x9
1
4
x11 J2
1
3 21
x7
J7
4
1 2 3
J4
x8
J1
3 21
Battery
x6
x1
+
x3
J6 J8
3 21
x2 x13 x16 J5 J10
3 2 1
set open open set
1 2 3
Fig. 2-9 P4N 486, position of jumpers and default settings
JUMPER REMARKS
J1 1-2 (A) Normal operation mode of ACCU (ACCU connected)
2-3 (B) 'Parking' mode of ACCU (for delivery or storage)
J2 1-2 (A) multiplicator of processor clock (depending on CPU type)
for AMD DX4, AMD 4X and iDX4: *3
2-3 (B) for AMD DX4: undef., AMD 5X: *4, iDX: *2
J3 1-2 (A) active level of signal PENA: negative
2-3 (B) active level of signal PENA: positive
J4 1-2 (A) boot via internal flash disk IC10 (for initial programming)
2-3 (B) boot via external flash disk (for initial programming)
J5-1 J5-2 J5-3 selection of LCD display type:
open open open 640 * 480 Dual Mono LCD
open open set 640 * 480 Sharp TFT
open set open 640 * 480 Hosiden TFT
open set set 800 * 600 Dual Color LCD
set open open 640 * 480 Dual Color LCD
set open set 640 * 480 18-Bit TFT
set set open 1024 * 768 TFT
set set set 800 * 600 TFT
J6-1 J6-2 J6-3 spare jumper
open open open (not equipped in actual version)
2-12 Ed. 01.02

RMMC RCSE 443
JUMPER REMARKS
J7 set write protection on BIOS flash not active
open write protection on BIOS flash active
J8 1-2 (A) NMI request after watchdog timeout
2-3 (B) system reset after watchdog timeout
open no action after watchdog timeout
J9-1 J9-2 system clock (of CPU and onboard PCI components)
set set 25 MHz
set open 30 MHz
open set 33.3 MHz
open open illegal
J10 set output on display in simultaneous mode (LCD and CRT)
open output on display only in CRT mode
J11 set NMI request after cooler failure
open no action after cooler failure
(only valid if supervision of cooler r.p.m. is installed, not equipped in
actual version of RCSE 443)
CONNECTOR REMARKS
x1 floppy disk interface
x2 parallel printer interface
x3 E-IDE interface
x4 or X5 Ethernet RJ45 interface or Ethernet AUI interface (optional)
x6, x7 serial interfaces COM1 (x7) and COM2 (x6)
x8 optional multiplex connector: COM1-keyboard
x9 keyboard interface
x10 KEYLOCK option
x11 power supply RAM disk (5V)
x12 SPEAKER interface (optional)
x13 flat panel connector
x14 service interface for initial BIOS programming
x15 CPU socket
x16 CRT interface (optional)
x17 PS2-SIMM socket
x18 ISA-96 bus
Ed. 01.02 2-13

RCSE 443 RMMC
2.3.3.3 SIB Settings
RSU
X32
X35
X33 3
CTU 2
1
X34
2a1
1a1
1a1
1 1
2 2
3 3
2a1
CTU
1 2 3
set open set

open
1 2 3
Fig. 2-10 SIB setting: 1a1,2a1 configuration (e.g.: RSU not connected, CTU connected)
NOTE: The communication channels have to be set independently from each other. To ensure
a correct operation of the SIB board the following jumper settings are always necessary:
'No DMA Operation' (X7, position 2-3) and '2 Wait States' (X36 set), see Fig. 2-15.
CONFIGURATION 1a1 (RSU) X33 X35 Remark

RS422 Operation*
100 Ohm termination set x with RSU*
100 Ohm termination not set - without RSU*
Send Enable via RTS x
Continuous Send-Enable - Default setting
Channel not in operation - -
CONFIGURATION 2a1 (CTU) X32 X34 Remark

RS422 Operation*:
100 Ohm termination set x with CTU*
100 Ohm termination not set - without CTU*
Send Enable via RTS x
Continuous Send-Enable - Default setting
Channel not in operation - -
*NOTE: A 100 Ohm termination must be provided for the 1a1 and 2a1 RS422 connections if RSU or CTU is connected.
If a RSU or CTU is connected, a 100 Ohm termination is also located and set on the RSU or CTU. The termination concerns
the RX-path of the RS422 connection in both directions.
-=jumper not set x= jumper set
2-14 Ed. 01.02

RMMC RCSE 443
X58
X57
X56
X55
X52
X59
1 TTL
X53
X54
TTL
RS232 X43
3
2
RS422 1
X8
1 1
2 2
3 3
1 2 3
X62
RS422
X60
set open set

open
1 2 3
Fig. 2-11 SIB setting: 1a3 configuration (example: RS232)
CONFIGURATION 1a3 (ZUA+NFK1+NFK2) X43 X52...X59 X8 X60 X62 Remark
RS232 Operation x - - - - Default setting

TTL Operation - x - - -
RS422 Operation* - - x
100 Ohm termination set x
100 Ohm termination not set -
Send Enable via RTS 1-2
Continuous Send Enable 2-3 Default setting
Channel not in operation - - - - -
*NOTE: A 100 Ohm termination must be provided for the 1a3/RS422 connection if nothing is connected at the output.
Ed. 01.02 2-15

RCSE 443 RMMC
X51
X50
X49
X44
1
TTL X46
TTL
X48
TTL X47
X45
RS232 X42
3
RS422 RS422 2
1
X63
X9
1 1
2 2
3 3
RS422 X61
1 2 3
set open set

open
1 2 3
Fig. 2-12 SIB setting: 2a3 configuration (example: RS232)
CONFIGURATION 2a3 (e.g. DME) X42 X44...X51 X9 X61 X63 Remark
RS232 Operation x - - - - Default setting

TTL Operation - x - - -
RS422 Operation* - - x
Channel not in operation - - - - -
*NOTE: A 100 Ohm termination must be provided for the 2a3/RS422 connection if nothing is connected at the output.
2-16 Ed. 01.02

RMMC RCSE 443
3
2
1
1
1
2 2
3 3
1 2 3
X22
1sB/TTL
X17
X12 1sA/TTL
X21 X15
X20 X13
1sB/TTL
X27 X16
1sA/TTL
X26 X14
1 1 1
X25 X19
X24 X18
X23 X10
1sB/RS232
X11 1sA/RS232
set open set

open
1 2 3
Fig. 2-13 SIB setting: 1sA, 1sB configuration (example: TTL)
CONFIGURATION 1sA, 1sB X11 X20...27 X10 X12...19 Remark
1sA (LGM-1): RS232 Operation x - - -

TTL Operation - x - - Default setting
1sB (LGM-2): RS232 Operation - - x -

TTL Operation - - - x Default setting
Channels not in operation - - - -
Ed. 01.02 2-17

RCSE 443 RMMC
X6
3
2
1
RS422
1 1
2 2
3 3
1 2 3
X28
RS422
X29
set open set

open
1 2 3
Fig. 2-14 SIB setting: 2sA configuration (example: TTL)
CONFIGURATION 2sA (LGM-3) X6 X28 X29 Remark

TTL Operation - - - Default setting
RS422 Operation* x
Channel not in operation - - -
*NOTE: A 100 Ohm termination must be provided for the 2sA/RS422 connection if nothing is connected at the output.
DRQ=DMA Request
CONFIGURATION 2sB (LGM-4)

Remark
TTL Operation No jumper setting Always TTL
2-18 Ed. 01.02

RMMC RCSE 443
X37 (1WS)
X39 (4WS)
X36 (2WS)
X38 (8WS)
X31
X30
X40
3
2
X41
1
DMA DMA
1 1
2 2
3 3
DMA
1 2 3
X7
DMA
set open set

open
1 2 3
Fig. 2-15 SIB setting: no DMA operation, 2 waitstates for synchronous channels (default setting)
NOTE: The following jumper settings must not be changed, otherwise the correct operation of
the SIB board is not ensured.
CONFIGURATION of DMA Operation
X7 X30/X31 X40/X41 Remark

Full duplex DMA via DRQ 1,3 1-2 x x
No DMA Operation 2-3 - - Default setting
CONFIGURATION of Waitstates (WS) for all synchronous channels (1sA, 1sB, 2sA, 2sB)
X36 X37 X38 X39 Remark

1 WS - x - -
2 WS x - - - Default setting
4 WS - - - x
8 WS - - x -
NOTE: Always set one jumper only.
Ed. 01.02 2-19

RCSE 443 RMMC
2.3.3.4 NFK Settings
F3 F2 F1
B38
B36
B35
B28
B26
B25
B18
B16
B15
A B A B A B A B A B A B
B39 B37 B29 B27 B19 B17 refer to 1) below

B B B
A A A
B64
B63
B34
B33
B32
B31
B24
B23
B22
B21
B14
B13
B12
B11
B
A
B44
B43
B42
B41
B54
B53
B52
B51
B64
B63
B62
B61
B B B
A A A
B49 B47 B59 B57 B69 B67
B48
B46
B45
B58
B56
B55
B68
B66
B65
F4 F5 F6
set open set

open
1 2 3
Fig. 2-16 NFK, position of jumpers and default settings (2-wire operation)
CONFIGURATION Bx3 Bx4 Bx5

(x=channel 1...6)Bx6 Bx7 Bx8 Bx9 Bx1 Bx2
---------------------------------------------------------
Amplification 0 dB x
Amplification 20 dB -
Service line or true standby line x - x -

Simulated standby line - x - x
Service line with simulated standby line x x x x
4-wire operation - - x - x - x - x -
2-wire operation x x - x - x - x - x
1) Special application LGMx to NFK:

NFK channel 6 supplied internally with La/Lb of LGM modem, NFK channel 6 converts LGM output signal
from 2- or 4-wire operation with special B64/B63 setting (FACE-link: Refer also to section 2.3.3.1.)
---------------------------------------------------------
-=Jumper not set x= Jumper set
2-20 Ed. 01.02

RMMC RCSE 443
2.3.3.5 LGM28.8 Settings
S4
1
ST1
OFF
LB1
ON
2
3
BU3
1 2 3
BU2
1 5
D5 2 6
4 5 6 7 8 9 10
D4 ST2
S1
BU1
1 2 3
S3 (side view)
1 2 3 4 5 6 S2
OFF
4
ON
LB1 open : BU2 pin 25b = AF signal set open set

LB1 closed : BU2 pin 25b = time slot open
1 2 3
Fig. 2-17 LGM28.8, position of jumpers and default settings
Dialing mode: automatic recognition of type of modulation, V.25bis, auto reliable mode,
flow control with RTS/CTS (S2/M2), autobaud (AT), pulse dial mode
S1.1 S1.2 S1.3 S1.4 S1.5 S1.6 S1.7 S1.8 S1.9 S1.10
OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF
S2.1 S2.2 S2.3 S2.4 S3.1 S3.2 S3.3 S3.4 S3.5 S3.6
OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF
Dedicated line mode: V.32 (9600 bit/s), error correction with direct mode 10 bit/sign, flow control with
RTS/CTS (S2/M2), autobaud (AT), 2-wired dedicated line
S1.1 S1.2 S1.3 S1.4 S1.5 S1.6 S1.7 S1.8 S1.9 S1.10
ON ON OFF OFF ON ON OFF ON ON OFF for RCSE/RMC
ON ON OFF ON ON ON OFF ON ON OFF for NAV-LCU
S2.1 S2.2 S2.3 S2.4 S3.1 S3.2 S3.3 S3.4 S3.5 S3.6
OFF OFF OFF OFF OFF ON OFF OFF OFF ON
ST1 Receive level range:

Level at Z ST1
-43 dBm 1 - 2 (delivery setting)
-33 dBm 2-3
Ed. 10.02
01.02 2-21
RCSE 443 RMMC
ST2 Transmit level range:
Switched line at Z ST2 Dedicated line (600 W) ST2
-4,5 dBm 3-5 -6 dBm 3-5
-6,5 dBm 5-6 -8 dBm 5-6
-8,5 dBm 3 - 4 (default setting) -10 dBm 3-4
-10,5 dBm 1-2 -12 dBm 1-2
CAUTION
Some telephone networks may prohibit alteration of the transmit level.
2.3.3.6 LGM64K Settings
S4
LB1
OFF
ON
BU3
BU2
1 2 3 4 5 6 7 8 9 10
D5
D4
S1
1 2 3 4
BU1 S2
S3 (side view)
1 2 3 4 5 6
OFF
ON
LB1 open : BU2 Pin 25b = AF signal

LB1 closed : BU2 Pin 25b = time slot
Fig. 2-18 LGM64K, position of jumpers and default settings
S3.2 S3.3 S3.4 S3.5 S3.6 Default settings, software mode

OFF OFF OFF OFF OFF Only DIP switches S3.2 to S3.6 are active in software
mode with these default settings. All other configurations
are set by software.
Default setting LGM64K:

ISDN, D-channel, B-channel, AT commands, autobaud, asynchronous
2-22 Ed. 01.02

RMMC RCSE 443
2.3.3.7 ZUA29 Settings
W106 W104
W118 -24
W116 -12
-6
-3
W114
W112
W105 W103
amplifiction
W108 W102
(+)
(0) W107 W101
W109
W218 W117
W216 W115
W214 W113
W212 W111
Transmit level (dBm)
W110
Receive level (dB)
W208
4-wire
(+)
(0) W207
W401
W402
W217
W215
W213
W211
W411 W412
W409 W410
W407 W408
W405 W406
W307
W305
W303
W301
W311
W309
W404
W403
attenuation
(0)
(+)
W308
W306
W304
W302
W312
W310
-24
-12
+12
+24
-6
-3
set open set

open
1 2 3
Fig. 2-19 ZUA, position of jumpers and default settings (4-wire, -6 dBm, 600 ohms)
CONFIGURATION W 107 108 207 208 REMARKS

4-wire operation - x - x RCSE operating with NFK29
2-wire operation x - x - Stand alone with one substation only
CONFIGURATION W 101 102 109 110

IN-impedance 600 ohms x - x -
CONFIGURATION W 103 104 105 106

OUT-impedance 600 ohms x - x -
CONFIGURATION W 411 412

Baudrate 1200 Bd, V.23 - x
CONFIGURATION W 301 302 303 304 305 306 307 308 309 310 311 312
Transmit level -6 dB x - - x x - x -
Receive level 0 dB x - x -
CONFIGURATION W 410 409 408 407 406 405 REMARKS

2/4-wire operation - x - x x - without amplifier
4-wire amplifier - x - x - x
2-wire amplifier - x x - - x
-=no jumper x= jumper set
Ed. 01.02 2-23

RCSE 443 RMMC
2.3.3.8 ZU1 Settings
a
ST7 a
ST2 ST8
b
b
ST4
b a a
b a a
ST9
ST3 a b
a ST10
b ST18/19
ST6 a
a b c b
ST5 b d ST11
b
a
b a
ST21 ST12
b
c a a b
b
ST13
a b a
ST16
b b
ST14 ST15
a a
a
ST20 ST17
b
b a
set open set

open
1 2 3
Fig. 2-20 ZU1, position of jumpers and default settings (4-wire operation, 600 ohms)
JUMPER POSITION REMARKS

3 a left no test operation
5 a right Idle tone disconnectable
6 a top no test operation
7 a top no extraneous feed
8...12 b down 2-wire operation
8...12 a top 4-wire operation
14 a down Points of disconnection for adjustment receive filter
15 b top Points of disconnection for adjustment receive filter
16 b left TxD-polarity, positive
20 a,b Points of disconnection for adjustment receive filter
21 a 2nd from right Transmitter may be modulated

17 b down Application: positive stop polarity (for CSB station with inverter)
a top Application: negative stop polarity (for CSB station without inverter)

18/19 a top coarse ) Adjustment of transmit level at ZU1:
2 a right fine ) attenuation 0 dBm; U=1100 mVss
4 a right fine )
13 b top Receive level at ZU1: from -36 dBm to -10 dBm; U= 35...693 mVss
2-24 Ed. 01.02

RMMC RCSE 443
2.3.3.9 LGM9600H1 Settings
BR1
2
S4 3
ST2 LB1
OFF
ON
1 5
ST1
BU3
1 2 3
BR2
BU2
2 6
D5
4 5 6 7 8 9 10
D4 S1
BU1
1 2 3
S3 (side view) S2
1 2 3 4 5 6
4
OFF
ON
LB1 open : BU2 pin 25b = AF signal set open set

LB1 closed : BU2 pin 25b = time slot open
1 2 3
Fig. 2-21 LGM9600H1, position of jumpers and default settings
Default setting LGM9600H1 (used to connect MK20A stations via dedicated line to RCSU/RCSE):
V.23, 1200 baud, half duplex (HX), asynchronous, pulse dialling, 1 start bit, 1 stop bit, 8 data bits,
1 parity bit (odd parity)
S1.1 S1.2 S1.3 S1.4 S1.5 S1.6 S1.7 S1.8 S1.9 S1.10
OFF OFF OFF OFF ON OFF OFF OFF OFF OFF
S2.1 S2.2 S2.3 S2.4

OFF OFF OFF OFF
S3.1 S3.2 S3.3 S3.4 S3.5 S3.6

OFF ON OFF ON OFF ON
ST1 Receive level range:

Level at Z ST1
-43 dBm 1 - 2 (delivery setting)
-33 dBm 2-3
ST2 Transmit level range:

Switched line at Z ST2 Dedicated line (600 W) ST2
-4,5 dBm 3-5 -6 dBm 3-5
-6,5 dBm 5-6 -8 dBm 5-6
-8,5 dBm 3 - 4 (default setting) -10 dBm 3-4
-10,5 dBm 1-2 -12 dBm 1-2
Ed. 01.02 2-25

RCSE 443 RMMC
2.3.3.10 LGM1200MD Settings
Test
OFF
ON
1 2 3 4 5 6 7 8 9 10
BU2
BR1
1 2 3
S1
1 2 3 4
S2
open set
set
open 1 2 3
Fig. 2-22 LGM1200MD, position of jumpers and default settings (2-wire, 300 ohms)
Permanent transmission control S2.1

on OFF default setting
off ON
Operation 1200/600 bit/s S2.2
1200 bit/s OFF default setting
600 bit/s ON
Transmit level S1.9 S1.10
1 ±0 dBm OFF OFF
2 -3 dBm ON OFF
3 -6 dBm OFF ON
4 -9 dBm ON ON default setting
Impedance during transmission S1.8
300 ohms OFF for remote side (e.g. RCSE)
600 ohms ON for station side
Receive level (min.) S1.7
-43 dBm OFF
-33 dBm ON default setting
Carrier lag time S1.6
13 ms OFF
3 ms ON default setting
S2-M2 lead time S1.5
30 ms OFF default setting
200 ms ON
Additional equalizer S1.4
Equalizer switched on OFF default setting
Equalizer switched off ON
2-26 Ed. 01.02

RMMC RCSE 443
Switching on mode S1.3
Fixed switching on (M1+) operation OFF default setting
Switching on with S1.1 ON
Operation mode S1.1 S1.2 S2.2
0...1200 bit/s, hx, asyn. (1300/2100 Hz) OFF OFF OFF default setting
0...1200 bit/s, hx, syn. with 1:1 change ON OFF OFF
0...1200 bit/s, hx, syn. without change OFF ON OFF
not used ON ON OFF
0...600 bit/s, hx, asyn. (1300/1700 Hz) OFF OFF ON
Sensitivity increase (-53 dBm) BR1
Sensitivity higher + add. equalizer 1-2
Sensitivity normal 2-3 default setting
2.3.3.11 INC/CTU Settings
No settings have to be done on the INC panel used as indication panel for the RCSE. On the rear side
of the INC panel, connectors to the REU and to another optional INC panel are available. The DIP
switch and the jumper are not used (switched OFF resp. open jumper).
connector to another INC panel
87 6 54 32 1
connector to parallel
ON
printer interface of
REU (x2)
connectors to
power supply (+5V)
Fig. 2-23 INC rear side, position of connectors and jumpers
Ed. 01.02 2-27

RCSE 443 RMMC
The EPROM of the processor unit for the CTU contains the complete software for test and operation
with software version 1.23. The setting of the address coding switch has to be set in accordance with
the table in Fig. 2-24. The setting up to software version 1.07 is also indicated (example of the adĆ
dress coding switch in the figure).
Runway Select enable (Runway 1)

Address coding switch
1=enabled 0=disabled
S5 (not used)
S5
OPEN
SW1
1 1 23 4 56 72 9
S1
OPEN
0
1
1 23 4 56 72 9
0
SW2
W5 W4 W2 W3
RST
W1
RS422 input/output open set

set
Reset Watchdog on/off Runway Select enable (Runway 2) Termination RS422 open
1 2 3
Software (up to V. 1.07) Address coding switch

987654321
CTU 001100100 Switch position and setting
1 23 4 56 78 9
0
Software ( V.1.23) Address coding switch
OPEN 1
987654321
CTU 1 (station 0...7) 100100100 closed
CTU 1 (station 8...15) 010100100
Test CTU 010100010
or
Fig. 2-24 CTU rear side, position of jumpers and default settings, address coding switch
2-28 Ed. 01.02

RMMC RCSE 443
2.3.3.12 LGM Extender 2 Unit Settings
RS422
RS232
CLOSED=INVERT
TXD X20 X30
RTS X21 X31
DTR X22 X32
LEDs
V1 to RI X23 X33
V16 DSR X24 X34
DCD X25 X35
CTS X26 X36
RXD X27 X37
1
USED
COM IDENT
X10 X1
X11
CLOSED OPEN
X12 X38
RS232 RS422
X13 X39
TERMINATOR
X14 X40
TERMINATOR
X15
1
X16
INT-VCC
+5V +12V X4 DC/DC Converter
1
RS232/422
X17
X18
X3 S1 S2
INT EXT
RS232-TEST (not used) (not used)
VCC
set open open set

1 2 3
Fig. 2-25 LGM Extender 2 Unit, position of jumpers and settings (example: RS422 without
termination)
CONFIGURATION X10..15 X16..18 X30..37 X38 X39..40 Remarks
RS232, INT-VCC = 5V 1-2 1-2 1-2 set open Default setting
RS422, INT-VCC = 5V 1-2 1-2 2-3 open connection to

CTU or RSU
without termination open
with termination set
Inversion of output signals X20..27

not active open Default setting
active set
NOTE: Depending on used LGMx slot (x=1..4, but only at LGM4 all signals are available), the
corresponding interface on the SIB board (1sA for LGM1, 1sB for LGM2, 2sA for LGM3,
2sB for LGM4) has to be set to TTL level (see section 2.3.3.3).
The LEDs V1 to V16 on the LGM Extender 2 Unit (see Fig. 2-25) indicate the signal levels of the
RS232 lines (DCD, RXD, TXD, DTR, DSR, RTS, CTS, RI):
- red LED on (back row: V1, V3, V6, V7, V10, V11, V14, V15): signal level is +12V
- green LED on (front row: V2, V4, V5, V8, V9, V12, V13, V16): signal level is -12V
- LEDs off (both rows): signal level is 0 V
Ed. 01.02 2-29

RCSE 443 RMMC
2.3.3.13 OIO Settings

32
32
a b RA1
RA2
J1
RA3 1' 1
1
7
J3*
RA4 **
1
1
set open set * set standard address: 230

** optional instead of zero ohm resistors for output
open
1 2 3 (depends on configuration)
Fig. 2-26 OIO (example: 24x Input, 8x Output), position of jumpers and default settings

J3/1 (A8) 1 Bit 8 of I/O base address = 1
1' Bit 8 of I/O base address = 0*
J3/4 (A5) 1 Bit 5 of I/O base address = 1*
1' Bit 5 of I/O base address = 0
J3/5 (A4) 1 Bit 4 of I/O base address = 1*
1' Bit 4 of I/O base address = 0
Address setting: OIO 1 230 OIO 2 234 OIO 3 238 OIO 4 (reserve) 23C
1' 1 1' 1 1' 1 1' 1
1 1 1 1
7 7 7 7
J3* J3 J3 J3
2-30 Ed. 01.02

RMMC RCSE 443
2.3.3.14 Multiplexer RS232 Settings
TTL TTL RS232/TTL

RS232 RS232 RS422
X39 X21 X27
TxD (red)
X22 X28
X40
X23 X29
RxD (green)
OPEN: TTL X24 X30
RS232 X25 X31
RS422 X26 X32
Ch1 X3
X4
Ch2 Processor
X5
X6 RS232/TTL
Ch3 X7 RS422
X8
(yellow) X33
Ch4 X34
X35
Ch5 RS232 TTL X36
X37
Ch6 X9 X15 X38
X10 X16
X11 X17
X12 X18
X13 X19
X14 X20
RS422 RS232/TTL
set open open set

1 2 3
Fig. 2-27 Multiplexer RS232 (MPX), position of jumpers and default settings
The Multiplexer RS232 is internally driven by the 1a3 channel of the Connector Back Panel (CBP) of
the Serial Interface Board (SIB).
The modes of the output channels 1 to 6 are configured via jumpers X8 to X38:
- Channel 1: X8, X9, X15, X21, X27, X33
- Channel 2: X7, X10, X16, X22, X28, X34
- Channel 3: X6, X11, X17, X23, X29, X35
- Channel 4: X5, X12, X18, X24, X30, X36
- Channel 5: X4, X13, X19, X25, X31, X37
- Channel 6: X3, X14, X20, X26, X32, X38
The jumper settings for the different modes are printed on the circuit board.
The output signals (for RS232/TTL: TXD, RXD, GND and for RS422: +TXD, -TXD, +RXD, -RXD)
of the 6 channels are led to the SubD 25 pin connector NFK-1 (if MPX plugged into slot NFK1) and
to NFK-2 (if MPX plugged into slot NFK2) on the back side of the remote control equipment.
The signals of RS232/TTL output channels (Ch1 to Ch6) are led to the following pins of NFK-1 resp.
NFK-2 connectors:
Ch1 Ch2 Ch3 Ch4 Ch5 Ch6
Signal TXD: Pin 14 Pin 16 Pin 18 Pin 20 Pin 22 Pin 24
Signal RXD: Pin 1 Pin 3 Pin 5 Pin 7 Pin 9 Pin 11
Signal GND: Pin 15 Pin 17 Pin 19 Pin 21 Pin 23 Pin 25
Ed. 01.02 2-31

RCSE 443 RMMC
The signals of RS422 output channels (Ch1 to Ch6) are led to following pins of NFK-1 resp. NFK-2
connectors:
Ch1 Ch2 Ch3 Ch4 Ch5 Ch6
Signal +TXD: Pin 14 Pin 16 Pin 18 Pin 20 Pin 22 Pin 24
Signal -TXD: Pin 15 Pin 17 Pin 19 Pin 21 Pin 23 Pin 25
Signal +RXD: Pin 1 Pin 3 Pin 5 Pin 7 Pin 9 Pin 11
Signal -RXD: Pin 2 Pin 4 Pin 6 Pin 8 Pin 10 Pin 12
The modes of the input channels TXD and RXD have to be configured via jumpers X39 and X40. The
jumper settings for the different modes (RS232 or TTL) are printed on the circuit board.
The LEDs on the left side of the MPX board (see Fig. 2-27) indicate the states of the input signals
TXD (red LED) and RXD (green LED) and the state of the output channels 1 to 6 (yellow LEDs). If the
channel is connected through, the LED is switched off.
NOTE: Depending on the type (ref. no.) of the Modem Backpanel board (MBP) actually used
within the remote control equipment, some pins have to be connected via soldered wirĆ
ings.
MBP with ref. no. 84045 81700:

1) +5V from X3 a16,c16 to X5/X6 a12,c12 (+5V for MPX board)
2) TXD_E from X3 a24 to X5 c16 (ZU-1 -> NFK-1)
3) RXD_E from X3 a30 to X5 a16 (ZU-1 -> NFK-1)
4) TXD_E from X4 a24 to X6 c16 (ZU-2 -> NFK-2)
5) RXD_E from X4 a30 to X6 a16 (ZU-2 -> NFK-2)

1) +5V from X5 a16,c16 to X6/X7 a12,c12 (+5V for MPX board)

no wiring connections necessary!
2-32 Ed. 01.02

RMMC RCSE 443
2.3.4 Connection to a PSTN
The connection to the PTT is achieved by the standardized angle connector TAE 6 N. The pin assignĆ
ment is shown in the following figure:
TAE 6 N Sub D 9pin Canon D9

analog ISDN
1w La Tx-
4 ye E G 3 gn 2 br Lb Tx+
5 gr a2 Lb 2 br 3 pk a2 Rx-
6 pk b2 La 1 ws 4 gr b2 Rx+
5 gn G
6 ge E
7
8
9
RJ 12 * RJ45 *
1w not conn. 1 not conn.
2 br Tx+ 2 not conn.
3 pk Rx+ 3 Tx+
4 gr Rx- 4 Rx+
5 gn Tx- 5 Rx-
6 ge not conn. 6 Tx-
7 not conn.
8 not conn.
* RJ12 and RJ45 are alternative connectors to TAE 6 N
Fig. 2-28 Pin assignment of connector TAE 6 N, RJ12 and RJ45 for connection to the PTT
Ed. 01.02 2-33

RCSE 443 RMMC
2.3.5 Connection to an Ethernet Line (Network Interface Link)
The connection to an Ethernet line (LAN network) is achieved by an RJ45 interface which is optionally
available on the P4N processor board (see section 2.3.3.2).
To use the network feature following prerequisites are necessary:

- REU with P4N processor board with assembled Ethernet controller and RJ45 connector (X4)
- REU-SW V2.23 in the version "Network"
To connect the network cable proceed as follows:

- Switch off power of RCSE.
- Open RCSE cabinet.
- Pull the network link cable carefully through a suited opening at the rear side of the RCSE
(e.g. opening for the DC switch -if not assembled- in the back panel).
- Feed the cable to the front, e.g. to the left of the SIB board.
- Place RJ45 plug of the network cable to RJ45 connector on the front of the P4N processor board.
- Close RCSE cabinet.
- Switch on power of RCSE.
The configuration of the Network Interface requires the following prerequisites:

- RCSE is connected to Ethernet network.
- REU SW V2.23 "Network" is implemented.
- SIT-file is loaded.
- MIB Browser on host system/server is installed.
The SIT-file contains the configuration of the specific site installation. This SIT-file can be configured
for operation with or without network interface. This is because not every REU has a network interface
facility. The SIT-file for network interfacing contains a unique IP address (the one for the REU and
all other needed), which makes the REU accessible to the network. It is set during initialisation of the
P4N network interface. The IP addresses are stored in the address table of the network stack.
To check if the network interface is working, use the "ping" command from a host, to get a response
from the selected REU.
Ethernet line
REU
Ethernet RJ45 connector
Network cable
P4N processor board

Pin Signal Type
1 TXTP+ Out
2 TXTP- Out
3 RXTP+ In
4,5 not conn.
6 RXTP- In
7,8 not conn.
9,10 SHLD PWR
Fig. 2-29 Connection to Ethernet line via RJ45 connector of P4N processor board
2-34 Ed. 01.02

RMMC RCSE 443
Description and Operation Initial Setup
2.4 INITIAL SETUP
This chapter describes the procedure for initial setup of the equipment. It presumes that the equipĆ
ment has been factory-aligned and tested (the configuration files are not yet loaded). The installation
must be in the following status:
- External power supply and external equipment (e.g. ILS systems) are installed and cabled.
- The input voltage to the REU and the peripherals (e.g. CTU, optional) must correspond to the
assigned input voltage.
- The Dip-fix switches and jumpers of the relevant plug-in units must be set to the correct position
(refer to section 2.3.3)
- Processor board P4N 486: set jumper J1 to position A (1-2) to activate memory buffer battery
2.4.1 Initial Power up

The installation procedure must be completed and all the connections made before the RCSE can
be started up. The power switch for the supply voltage must be set to "off". Proceed as follows, deĆ
pending on the type of converter:
- Switch on the AC-switch or DC-switch (depending on type of converter) on the rear of the REU.
- Switch on the CTU-subrack as for the REU, if existing and connected.
The power supply LEDs on the REU and the Life LED on the SIB should light up when the voltage
is applied. As soon as the device is switched on, the REU initialization routine starts automatically:
the boot procedure is performed, the main REU program is loaded while the red LED of the flash disk
is blinking (see also section 2.4.2.1), start procedures are run, etc. After start of the program all text
fields above columns where stations are configured (area EQUIPMENT-MAIN STATUS on the INC
panel) show the text "Wait" for about 10 s. The initialization procedure may take around 20 s altoĆ
gether. A tone is emitted by the buzzer.
Since the configuration files (e.g. *.sit) are not yet loaded, the main status of station no. 8 shows the
string No" stat" (no station, area EQUIPMENT-MAIN STATUS on the INC panel). The status indicaĆ
tions of the other connected stations are all switched off. After configuration of the REU (described
in section 2.4.2), the subsystem states of the connected stations are indicated on the INC/CTU and
the system status is indicated on the CTU. The NORMAL indicators light up for the various subsysĆ
tems during normal operation. If no maintenance data terminal is connected, the RCSE can comĆ
mence operation.
On/Off switch if AC/DC converter

used (no function for DC).
REU-subrack, rear side
CTU-subrack, rear side
On/Off switch if DC/DC converter

used (no function for AC)
Fig. 2-30 Location of On/Off switches (REU-subrack and CTU-subrack)
Ed. 01.02 2-35

RCSE 443 RMMC
Initial Setup Description and Operation
2.4.2 Configuration of the REU with PC and ADRACS

a) Switch on the PC and run Windows.
NOTE: Installation and use of the PC User Program is described in the Technical Manual
ADRACS (Code No. 83140 55324). The former version of the user program was WIN
ADRACS (described in technical manual no. 83140 55323). It is recommended to become
familiar with the menus of the user program before performing the first set up procedure.
b) Click 'Start' button, select Programs, program group Adracs Remote Controlling, program Adracs
Remote Controlling Software to start the user program.
NOTE: For WIN ADRACS select program Adracs-RC of program group Adracs-Remote.
c) Perform Login procedure at the PC. Acknowledge 'User 1, Level 5' with softkey OK.
d) Click softkey Control in the opening window.
e) Select menu File Transfer of 'RC Management' window.
NOTE: In WIN ADRACS select File Transfer of 'REU-OPERATIONS' window.
f) Copy configuration files (*.SIT, *.PTT, *.OIO) of the configuration floppy to the REU with
command Copy PC file to RAM of menu File Transfer.
g) Click on command Reset SITE of menu File Transfer to activate the loaded files.
NOTE: Due to this reset the user program will be terminated. It has to be restarted manually.
h) Start the PC user program again (see b). Perform the Login procedure (see c).
i) Click softkey Control in the opening window.
j) Load station-relevant files (*.LKE) to the REU via File Transfer command UpDate LKE Files. Click
on command Reset Site of menu File Transfer to activate the loaded files. Start the PC user program
again (see b). Perform the Login procedure (see c).
k) Select menu DateTimeREU in 'RC Management' (for WIN ADRACS: 'REU OPERATIONS') window.
Set date and time and acknowledge with button Set New. Close 'Date&Time REU' window.
l) Close 'RC Management' (for WIN ADRACS: 'REU OPERATIONS') window.
Logout and exit from user program.
NOTE: In case of any faulty reaction after switching on the configured RCSE (e.g. with a not-
blinking life LED on the SIB or with a permanent resetting of the RCSE) a special proceĆ
dure has to be performed which is described in chapter 2.4.3.
2.4.2.1 Actualization of REU Application Program (REU.EXE)

After delivery, the REU application program (Standard version) is stored on the EPROM side of the
SAN flash disk (integrated on the P4N processor board). This software is loaded during initial power
up procedure (see section 2.4.1).
If the REU application program has to be actualized by the user, the new REU.EXE file must be loaded
from PC to RAM side of SAN flash disk (using (WIN) ADRACS command Copy PC file to RAM, see
above). During next start-up of the system, the software is first looking for an REU.EXE file on the RAM
side of the SAN flash disk. If the executable file exists there, it is used for start-up, otherwise the stanĆ
dard REU.EXE on the EPROM side is used. If the standard executable file on EPROM side is damaged
the procedure in section 2.4.3 has to be performed.
2-36 Ed. 10.02

01.02
RMMC RCSE 443
2.4.2.2 Setting of PTT file
a) Run program Adracs Remote Controlling Software again (for WIN ADRACS run program Adracs-
RC). Perform Login.
b) Click softkey CONTROL in the opening window.
c) Select File Transfer from menu RC Management" (for WIN ADRACS menu REU-OPERAĆ
TIONS") and start procedure with command Edit phonenumber File.
The window 'File Manager PC (Open File)' appears. Select the corresponding *.ptt file to open the
file for configuration entries. The window 'Phone numbers of <site name>.PTT' provides a filing cabiĆ
net with filing cards for each subsystem to define modem settings and phone numbers (see Fig. 2-31
and 2-32).
Phonenumbersof ILS-RMC.PTT X
16
12 13 14 15
8 9 10 11
4 5 6 7
ILS-RMC Shawnee Stuttgart Gorgonzola
Modem1
Mode: Disable V.25bis Direct Reliable
Init String: ATS0=1\N7S51=255\Q2F255X4S10=2S20=0 Baud: 19200
Modem2
Init String: Baud:
Modem3
Init String: Baud:
Modem4
Init String: Baud:
REU-ID-OWN: 3
OK X Cancel ? Help
Fig. 2-31 Window to define modem settings within PTT file (example)
Ed. 01.02 2-37

RCSE 443 RMMC
Phonenumbers of ILS-RMC.PTT X
16
12 13 14 15
8 9 10 11
4 5 6 7
ILS-RMC Shawnee Stuttgart Gorgonzola
Phonenumber1: Shawnee Gorgonzola

Phonenumber2:
Phonenumber3:
Phonenumber4: ATS0=0DT0071182112345
Connection after Start: Yes No REU-ID: 10 NEW: 10
Call time: 00:00:00 [day:hour:min] (First connection time after REU start time, 0=no call)
Time interval: 00:00:00 [day:hour:min] (Time interval for periodic connections, 0=no call)
Min. interval: 00:00:00 [day:hour:min] (Min. time interval of last con. initiat. by other REU, 0=OFF)
Data com off: 0 [sec] (Data Com off Distance TIMEOUT, 0=no action)
First retry: 00:00:00 [day:hour:min] (Time of next call attempt after last bad call)
Max. bad call: 0 [0..255] (Maximum number of bad call attempts)

00:00:0
Retry time: 00:00:00 [day:hour:min] (Time of next call after bad call attempts reached, 0=no call)
0
DataComNb: 00:00:0
0 [0..255] (Switch lamp off after max. bad call attempts, 0=no action)
00 [sec] (Report good/bad time after change MAINSTATE, 0=no action)
Good/Bad:
Priority: 5 [0..5] (Back call is performed, if the caller priority is higher)
Don't use Modem:

1 2 3 4 ? Help
OK X Cancel
Fig. 2-32 Window to define telephone numbers within PTT file (example)
2.4.2.3 Explanation of Modem Setting

V AT-/V.25bis modems:
AT modems (Hayes compatible) as well as V.25bis modems are supported. The setting for the modem
type occurs in the configuration file REU- CONF.SIT. This setting can be overwritten with the PTT file.
The following two modem connection modes are supported:
- DIRECT-MODE
The baud rate between REU and modem is the same as the baud rate between the two modems.
The data is sent to the modem path without buffering. Handshaking is not necessary. Fault correctiĆ
on or data compression is not possible. This mode is suitable for the virtual link (former 'Face Link')
to Navaids stations like DME 415 or TACAN TAC 453.
- RELIABLE MODE
This is at least a connection of the type MNP4 or V.42. If additionally a data compression is selected,
the type is called MNP5 or V.42bis. The baud rate between REU and modem can differ from that
between the two modems. It is convenient to set the baud rate from the REU to the modem as high
as possible (e.g. 38400 baud). Data buffering takes place in the modems. Therefore a RTS/CTS
hardware handshake is necessary.
2-38 Ed. 01.02

RMMC RCSE 443
V Configuration of AT modems:
The advantage of AT modems is the various configuration possibilities. The following three standard
initialisation strings are available which are sent automatically from the REU to AT modems:
- Init String: ATZ0
Z0 = reset with following loading of EPROM configuration
- Init-String: ATE0V1X1S0=1S2=255
E0 = echo off
V1 = message code as text (because of baud rate in CONNECT message)
X1 = message codes with state of the baud rate and also dialing without dial tone
S0 = 1 = receive calls after one ring
S2 = 255 = accepting no abort sign
- Init-String: AT&S1&D3
&S1 = M1 (DSR) on at data connection
&D3 = ON-OFF change at S1 (DTR) interrupts connection and resets modem (ATZ0)
V Reliability of a modem connection (connection build-up mode):

The reliability of a modem connection is dependent on the selected build-up mode. Two different
build-up modes are available. The safest mode is the BACK CALL.
- NO-BACK-CALL: Build up due to a single call and identification (START CALL).
- BACK-CALL: Build up due to a call and identification. Then back call and identification
(START CALL, BACK CALL). Setting the priority to 0 in the PTT file of the
called site.
V Setting of modems LGM9600H1 / LGM1200MD

After jumper setting (described in sections 2.3.3.9 and 2.3.3.10) the modems are ready for operation.
V Setting of modem LGM28.8D1
There are different configurations possible. For example as universal reliable mode modem:
- basic setting: : 2 (factory delivery state)
- baud rate : 38400 Baud
- Modem mode : Reliable-Mode
- PTT-Init-String : AT\N2S51=12\Q2F255X4S10=100S20=0
- Dial string : "AT"+"DP" or "DT"+"telephone number" <blank> host name" of this
telephone number
V Setting of modem LGM64K

There are different configurations possible. For example as universal reliable mode modem:
- basic setting : 2 (factory delivery state)
- baud rate : 19200 Baud
- Modem mode : Reliable-Mode
- PTT-Init-String : AT\N7S51=255\Q2F255X4S96=1S47=3
- Dial string : "AT"+"S0=0D"+ "telephone number" <blank> host name" of this tele-
phone number
V Dedicated line connection between REU and REU.

Setting the 'Data com off' timeout to 10 sec. (range from 1..32767 sec., standard is 10 sec.).
Ed. 01.02 2-39

RCSE 443 RMMC
2.4.3 Faulty Switching-on Behaviour of RCSE after Configuration
If the RCSE 443 is reacting faulty when switching on the equipment after configuration (e.g. with a
not-blinking life LED on the SIB or with permanent resetting of RCSE), it may be possible, that one
or more of the configuration files *.sit, *.ptt, *.oio, *.lke at the RAM side of the REU (which is part of
the flash disk on P4N processor board) are damaged or wrong for this site.
A special AUTOBOOT.BAT file is installed on the SAN flash disk of the processor board P4N 486,
which supports the deletion of the incorrect, wrong data on the disk depending on the used type of
service adapter connected to the PC2 (Diagnosis) interface at the RCSE. After deletion the default
application program is started to reconfigure the processor board.
To initiate the deletion of the wrong contents of the RAM side on the remote control unit (RCSE
443) the following steps have to be done:
- switch off RCSE 443
- connect adapter of type B with PC2 interface of RCSE
- switch on RCSE 443
- wrong contents of RAM side (i.e. the configuration files) is deleted
- repeat the configuration procedure described in section 2.4.2.
In case of a possible incorrect REU application program (REU.EXE on EPROM side of SAN flash
disk) the adapter of type A has to be connected to the PC2 (Diagnosis) interface to delete the wrong
application program and to load a standard application program from the corresponding subdirecĆ
tory of the EPROM side.
1a2/PC1 OIO 1 OIO 2 S12
2a2/PC2 1
LAN
2a1/CTU 2
PC2 interface
(Diagnosis) 1a1/RSU -12V +12V
1a3
2a3
Fig. 2-33 RCSE rear side with PC2 interface to connect service adapter
The adapters of type A and B are both SubD 9 female connectors, where the following two pins have
to be connected via a short cable:
- adapter type A: connection between pin 4 (DTR) and pin 9 (RI) 1

6
solder side
- adapter type B: connection between pin 7 (RTS) and pin 9 (RI) 1
6
2-40 Ed. 10.02

01.02
RMMC RCSE 443
Description and Operation Operation
CHAPTER 3
OPERATION
3.1 GENERAL
This chapter describes the operation of the RCSE in the RCMS 443 for Navaids 400 (SYSTEM 4000)
ILS, VOR/DVOR and DME. It includes details of the INC, the CTU and the PC user program ADRACS.
Description and use of the PC User Program will be found in the Technical Manual ADRACS, Code
No. 83140 55324. The former version of the user program was WIN ADRACS which is described in
technical manual no. 83140 55323. The INC and CTU panels are shown in Fig. 3-3.
3.2 OPERATION OF THE RCSE/REU

3.2.1 Switching On
See Fig. 3-1.
NOTE: For the described switching-on procedure it is assumed that the configuration of the
REU (see section 2.4.2) has already be done (i.e. configuration files are loaded).
- AC-power supply: The mains switch (AC-supply) is located on the rear.
Set switch to "ON" (upper position). The Control LED of DC-Converter and the Life LED of the
SIB board inside are on.
- DC-power supply: The DC ON switch (DC-supply) is located on the rear.
Set switch to "I" (upper position). The Control LED of DC-Converter and the Life LED of the SIB
inside are on.
When the unit is switched on, the REU starts up automatically. This takes around 20 seconds altogethĆ
er. After start of the program all text fields above columns where stations are configured (area EQUIPĆ
MENT-MAIN STATUS on the INC panel) show the text "Wait" for about 10 s. A tone is emitted by the
buzzer. Following the subsystem names and the states of the connected stations are indicated on
the INC panel. The NORMAL indicators light up for the various subsystems during normal operation.
If no maintenance data terminal is connected, the RCSE can commence operation.
NOTE: In case of a faulty switching-on behaviour of the RCSE (e.g. blinking Life LED or permaĆ
nent reset) a special procedure has to be performed which is described in chapter 2.4.3.
On/Off switch if AC/DC converter used On/Off switch if DC/DC converter used
(no function for DC) (no function for AC)
REU Control LED
DC-Converter
Life LED SIB

rear INC
front
Fig. 3-1 Position of On/Off-switch at RCSE, indications
Ed. 01.02 3-1

RCSE 443 RMMC
Operation Description and Operation
3.2.2 Switching Off

See Fig. 3-1.
- AC-power supply: The mains switch (AC-supply) is located on the rear.
Set switch to "Off" (lower position). The Control LED of DC-Converter and the Life LED of SIB
inside are off.
- DC-power supply: The DC ON switch (DC-supply) is located on the rear.
Set switch to "0" (lower position). The Control LED of DC-Converter and the Life LED of SIB inside
are off.
3.2.3 General Controls of the INC/CTU

See Fig. 3-3.
3.2.3.1 Lamp Test
As long as LAMP TEST is pressed, the lamp test is activated: All indicators are on and the text field
indicates "TEST". The buzzer is also activated. If a station has been selected before the lamp test it
remains selected and the request of selected state telegrams runs in the background.
3.2.3.2 Alarm Silent

The device buzzer sounds whenever the status of a station indicated on the device changes. This is
only provided in the DATA COM, MAINTENANCE, NORMAL, WARNING and ALARM states (not
MAINTENANCE for the CTU). The buzzer remains switched on until either the SIL button (on INC)
resp. the ALARM SILENT button (on CTU) is pressed or the time preset for it elapses. The buzzer
times are as follows:
- INC: 15 s
- CTU: No limit
- PC : 15 s
A station status change does not result in a buzzer alarm in the following situations:
- If either PC control or switch control has been set for the station.
- If the runway select bit for the runway to which the station belongs has been altered during the
previous 60 seconds.
- If the ADRACS maintenance function (PC) is active.
3.2.3.3 Brightness up/Brightness down (INC and CTU)

- INC-panel
The brightness of the text fields and status indicators can be adapted to the ambient brightness:
To activate the brightness control press the controls SIL and LAMP TEST within 5 s in the following
sequence: SIL - LAMP TEST - SIL - LAMP TEST. All LED indicators are illuminated, the text
fields indicate alternating "Brig" and "htne" (for Brightness). To decrease or increase the brightĆ
ness press control key EQUIP ON/OFF for text fields or CHANGE OVER for status indicators. The
setting is finished automatically after 5 s, if no correspondent control is pressed or pressing SIL
or LAMP TEST.
- CTU-panel
The brightness of the indicators can be adapted to the ambient brightness with the BRIGHTNESS
UP and BRIGHTNESS DOWN controls.
If a station has been selected before the brightness control it remains selected and the request of
selected state telegrams runs in the background.
3-2 Ed. 01.02

RMMC RCSE 443
3.2.4 Special Controls of INC/CTU
3.2.4.1 INC Control Functions
See Fig. 3-3.
Each of the eight displayable stations is assigned a SELECT button (row at the bottom). After pressĆ
ing a SELECT-button the respective Mainten" display is blinking to indicate the station selected.
Stations selected can be controlled by the commands in the EQUIPMENT-DETAILED STATUS-
COMMAND field.
The INC can only send commands to the station selected, if the local mode" is active, indicated by
the green ENABLED" field in EQUIPMENT-DETAILED STATUS-CONTROL" area. If necessary, acĆ
tivate the local mode" by pressing the key REQUEST RELEASE.
The following options are available:
- CHANGE OVER button: Changes the transmitter connected to the antenna
- EQUIP ON/OFF button: Switches the transmitters TX1 and TX2 on/off of the LLZ and GP.
3.2.4.2 CTU and RWY-SELECT Control Functions

The CTU has no special controls on its front panel. The runway which is displayed on the RWY-SEĆ
LECT can be selected with the SW1 and SW2 switches on the CTU board (CTU rear side). The followĆ
ing options are available:
SW1 (position '1'): Runway1 Select enabled
SW1 (position '0'): Runway1 Select disabled
SW2 (position '1'): Runway2 Select enabled
SW2 (position '0'): Runway2 Select disabled

1
SW1
0 S1 OPEN
1
1 23 4 56 72 9
0
SW2
RST
W1
Fig. 3-2 CTU rear side, position of RWY-SELECT enable switches SW1 and SW2
The runways can be switched on (and off) with the key switch of the RWY-SELECT unit (CTU front,
see Fig. 3-3). The ENABLE lamp of the determined runway must light up. ENABLE off is a result of
the following conditions:
- Datacom error to LLZ or GP and DME (if it belongs to the system)
- Local control of LLZ or GP and DME (FACE LINK)
- Switch control mode (RPU SW1 and station selected)
- PC control mode, maintenance active for a station in (WIN) ADRACS
- DME TX1 and 2 SHUT DOWN
Ed. 01.02 3-3

RCSE 443 RMMC
3.2.5 CTU Cascading
It is always possible to connect several CTU's in a cascade with a CTU. The same status is indicated
on each unit. If one of the CTU's in the chain develops a fault however, all the indication units conĆ
nected downstream of it will also be affected. If there are two CTU's cascaded, the runway select can
be changed over to a single CTU, or each CTU can be used to switch only one runway:
CTU (1) SW1 = '1' => Runway 1 enabled (Runway 1 enabled on CTU 1)
CTU (1) SW2 = '0' => Runway 2 disabled
3.2.6 INC Indications

3.2.6.1 Subsystem Indications
See Fig. 3-3 and sections 1.4.2.3 and 1.4.2.5.
The INC panel provides eight columns to indicate the state of the correspondent subsystem/station.
Indications are only provided on the panel for the stations which are configured in the REU.
On top of each subsytem column a text field is located with four LED's to indicate characters. If the
RCSE is switched on and configured the connected station name is indicated derived from the configĆ
uration file. Because this name consists of up to eight characters the name is shown 1 s each alternatĆ
ing the first four and the last four characters.
Text fields of columns to which no station corresponds are off. If no station is configured to the eight
columns, the most right text field shows "No" Stat".
The following signals are evaluated by the REU and indicated by the INC accordingly:
V INC subsystem indications (INC area EQUIPMENT->MAIN STATUS)

ALARM => Station status = ALARM
WARNING => Station status = WARNING
NORMAL => Station status = NORMAL
DATA COM => Modem link to station (CTU only)
MAINTEN => Station status = Maintenance/BITE warning or Local access
V INC indications if station selected (INC area EQUIPMENT->DETAILED STATUS)

MON1/2 AERIAL => No operational monitor ALARM
MON1/2 STANDBY => Standby Warning
MON1/2 FAULTY => Monitor FAULT set
MON1/2 BYPASSED => Monitor bypass set
TX1/2 ON => Transmitter x = ON
TX1/2 WARNING => Transmitter x has BITE WARNING
TX1/2 FAULTY => Transmitter x has operational OFF (faulty)
TX1/2 ON ANT => Transmitter x = aerial (connected to antenna)
3-4 Ed. 01.02

RMMC RCSE 443
ENGAGED => Remote mode (control by ADRACS on PC)
ENABLED => Local mode (control by INC panel keys)
MAINS OFF => Mains power supply of station is switched off
ENV ALRM => Multiple purpose (e.g. intrusion alarm, fire alarm)
ANT FTY => not used
OTHER WARN => Miscellaneous communication and protocol errors
3.2.6.2 System (RCSE) Indications
V RCSE (RC) status indication (INC area EQUIPMENT->RC)

OPERATION => Normal operation
WARNING => REU BITE warning
DATA COM => Internal communication fault
3.2.7 CTU and RWY-SELECT Indications

3.2.7.1 CTU Subsystem Status Indication
NORMAL => Normal Operation:
of operations (i. e. no Warning and no Alarm condition).
WARNING => Warning (Alert):
Transmitter(s) OFF, equipment initializing, primary equipment
shut-down by monitor, limited monitor configuration (only one
executive), local access (local panel or attached terminal), monitor
bypass (one or both), battery operation
ALARM => Alarm
Subsystem shut-down
Out-of-tolerance signal(s) while monitor in bypass
3.2.7.2 RWY-SELECT System Status Indication

OPERATIONAL => Operational performance fulfilled (e.g. Runway in CAT III mode)
DEGRADED => Operational performance limited (e.g. RWY degraded to CAT I/II)
SHUT DOWN => Runway shut down or has ALARM
ENABLE => Runway follows CTU runway switch
3.2.8 Assignment of Station Main Status Indications

This section interprets the meaning of the main status indications for the respective connected staĆ
tions. The meaning is shown as a logical OR-combination.
- GP, LLZ-Main Status:
ALARM Alarm or Monitor-Bypass
WARNING Mains-Off or Single-Monitoring or Standby-Alarm or TX-Off or
TX-Operational-Off
MAINTEN BITE-Alarm or Local-Control or Mains-Off
Ed. 01.02 3-5

RCSE 443 RMMC
- Marker Main Status
ALARM Alarm
WARNING Mains-Off or (not Master-Off) or Standby-Alarm
MAINTEN Mains-Off
- FFM-Main Status
WARNING Mains-Off or Single-Monitoring
MAINTEN BITE-Alarm or Mains-Off
- DME Main Status (DME 415)

ALARM Beacon-Faulty or (not Beacon-Operation)
WARNING Battery-On or Beacon-Degraded or TX1 Shut-Down or TX2 Shut-Down
MAINTEN Battery-On
- DME-Main Status (FSD10/15 only)

ALARM Beacon-Faulty or (not Beacon-Operation)
WARNING Battery-On or (not Beacon-Operation) or TX1 Shut-Down or
TX2 Shut-Down or Second Alarm Monitor 1 or Second Alarm Monitor 2
MAINTEN Battery-On
- NDB-Main Status
ALARM Alarm
WARNING Mains-Off or Standby-Alarm or SWR-Alarm
MAINTEN Mains-Off
- VOR-Main Status
WARNING Mains-Off or Single-Monitoring or TX-Operational-Off
MAINTEN Alarm-Memory or BITE-Alarm or Mains-Off
- Additional linkages of Main Status in the REU-Software

DATA-COM (not Data-Com-Error)
ALARM ALARM or Data-Com-Error
MAINTEN (MAINTENANCE and (not Data-Com-Error) or Face-Link-Active or
PC-Maintenance
WARNING WARNING and (not ALARM)
NORMAL (not WARNING) and (not ALARM)
3-6 Ed. 01.02

4 character text field
EQUIPMENT RC
Fig. 3-3
Ed. 01.02
1 2 3 4 5 6 7 8
MON 1 MON 2 TX 1 TX 2 OPERATION
RMMC
AERIAL AERIAL ON ON
WARNING
STANDBY STANDBY WARNING WARNING

ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM DATA COM
FAULTY FAULTY FAULTY FAULTY

WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING
BYPASSED BYPASSED ON ANT ON ANT

NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL
CONTROL STATION
DATA COM DATA COM DATA COM DATA COM DATA COM DATA COM DATA COM DATA COM
ENGAGED MAINS OFF
Description and Operation
SIL
MAINTEN MAINTEN MAINTEN MAINTEN MAINTEN MAINTEN MAINTEN MAINTEN
ENABLED ENV ALRM
COMMAND
ANT FTY
SELECT SELECT SELECT SELECT SELECT EQUIP CHANGE REQUEST
SELECT SELECT SELECT LAMP
ON/OFF OVER RELEASE
OTHER WARN TEST
RCSE Indication and Control panel (INC)
AIR NAV SUBSYSTEM RWY-SELECT
INC panel (of RCSE) and CTU/RWY-SELECT panel

ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM OPERATIONAL OPERATIONAL
WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING DEGRADED DEGRADED
NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL SHUT DOWN SHUT DOWN
ALARM BRIGHT- BRIGHT- LAMP

NESS NESS ENABLE ENABLE
SILENT TEST
DOWN UP
Control Tower Unit (CTU) RunWaY Selector (RWY)
Key Switch
3-7
Operation
RCSE 443
RCSE 443 RMMC
3.2.9 Indications and Switches of the REU Subassemblies

1 2 3 4 5 6 7 8 9 10
PC2
PC1
OIO2* / ADC*
LGM9600H1**
Board P4N
LGM Ext.**
Processor
LGM28.8**
LGM28.8**
OIO 1*
Spare
LAN
MPX
ZUA
NFK
SIB
* optional ** different configurations of LGMx slots (equipped with DC/DC-Converter

possible (see fig. 1-8) APD346)
1 Processor Board P4N: LED to show RAM access (red, blinking)

NOTE: LED may be encapsulated, i.e. not visible for user.
Life on
2 SIB: upper LED is life LED (green, blinking) Life off
Switch (not used)
PM1 ANS
3 LGM28.8: switched line modems (LGM1/2) M5 S1
PM1 = State of interface line PM1, ON: test condition
ANS = Indication of time slot, blinking: modem is seizing a line
M5 = State of interface line M5, ON: transmission mode
S1 = State of interface line S1, ON: DTE ready for operation
4 LGM: switch test
5 LGM9600H1: dedicated line modem (LGM3/4) PM1 ANS

PM1 = State of interface line PM1, ON: test condition M1 S1
ANS = Indication of time slot, blinking: modem is seizing a line
M1 = State of interface line M1, ON: modem ready for operation
S1 = State of interface line S1, ON: DTE ready for operation
6 LGM Extender 2 Unit: optional instead of LGM4 for RS232/422 connections

signal levels of RS232 lines (DCD, RXD, TXD, DTR, DSR, RTS, CTS, RI):
red LED on (back row: V1, V3, V6, V7, V10, V11, V14, v15): signal level is +12V
green LED on (front row: V2, V4, V5, V8, V9, V12, V13, V16): signal level is -12V
LEDs off (both rows): signal level is 0V
LGM1200MD: optional (instead of ZUA/NFK) in LGMx slot (LGM4 preferred)
PM1 = test condition PM1 M5
M5 = receive signal level M2 S2
M2 = ready for transmission
S2 = switch on transmission part, DSK (permanent transmission control) on/off
7 ZUA: LED top = Activity data lines (RxD/TxD) RxD TxD

LED down = Receive level F11/F21 F11 F21
F2 F1
8 NFK: LED on = Channel switched off or alternatively F4 F3
F6 F5
9 Multiplexer RS232: LEDs for input channelsTXD (red), RXD (green);
6 output channels (yellow), LED off means connected through
10 DC-Converter: LED on= Voltages +5, +12, -12 [V] available.
Fig. 3-4 REU interior, indications and switches, example
3-8 Ed. 10.02

01.02
RMMC RCSE 443
3.3 MAINTENANCE OPERATION
3.3.1 General
Maintenance mode can be set either at a Maintenance Data Terminal (PC) connected to the RCSE/
REU or at a Remote Maintenance Center (RMC), again via a PC which is connected there to the RCSE/
REU. In both cases, it is controlled using the installed PC User Program (WIN) ADRACS.
Since the interface in the REU system is an open interface, access and thus operator actions are govĆ
erned by a multi-level password code. When the (WIN) ADRACS program is started, password inforĆ
mation is sent to the REU. The first PC with a suitable password level (> 2) to issue a request is given
priority over the next requesting PC with the same password level, in other words only one PC at a
time can be operated in maintenance mode in the same system (either locally or at the RMC). The
other PCs receive an "Other User is master" message. All PCs with a password level < 3 will get acĆ
cess to the system. The only exception is a request for GetAllState data (telegram for main status of
station), which can be made by several different PCs.
NOTE: To avoid bringing in a computer virus it is not allowed to run computer games generally
and to use software programs which are not authorized on the Maintenance Data Terminal
(PC). It is recommended to test the computer or disks with a virus checker.
3.3.2 Operation with a Maintenance Data Terminal (PC)
The Maintenance Data Terminal (PC) is ready as soon as the REU (1a2 PC1) has been connected
and the (WIN) ADRACS software has been installed. When the PC is switched on and the (WIN)
ADRACS software is started, the REU software realizes that a PC is connected and that it can commuĆ
nicate with it. The PC can also be connected at any time during normal operation.
The Maintenance Data Terminal can control and poll the REU and the connected stations via this interĆ
face, and if necessary program them using the facilities of the (WIN) ADRACS program. The control
functions of the user program are described in Technical Manual ADRACS, ref. no. 83140 55324, resp.
in Technical Manual of WIN ADRACS, ref. no. 83140 55323.
3.3.3 Operation at the Remote Maintenance Center (RMC)
It is possible to poll several systems (with local RCSEs) via the telephone network, using the PC of
the RMC, and to set them to maintenance mode. Only the general status of an airport or of several
en-route systems can be displayed on the INC of the RCSE in the RMC. The subsystem select butĆ
tons on the INC are not active. The software of the RCSE/REU in the RMC has been designed accordĆ
ingly.
The Maintenance Data Terminal (PC) in the RMC can control and poll the connected stations via the
REU, and if necessary program them using the facilities of the (WIN) ADRACS program. The control
functions of the user program are described in Technical Manual ADRACS, ref. no. 83140 55324, resp.
in Technical Manual of WIN ADRACS, ref. no. 83140 55323. The priorities described in section 3.3.1
apply.
Ed. 01.02 3-9

RCSE 443 RMMC
3-10 Ed. 01.02

RMMC RCSE 443
Description and Operation Detailed Description
CHAPTER 4
DETAILED DESCRIPTION
4.1 GENERAL
All plug-in or screw-on subassemblies (printed circuit boards) in the RCSE 443 are described in
section 4.3. Their tasks are described and illustrated with the aid of simplified block diagrams. The
integration within the complete system is shown in block diagram Fig. 1-12. More details about the
subassemblies (printed circuit boards), which may exceed the information given in the following deĆ
scription part and figures, may be taken from the circuit diagrams listed in Fig. 4-1.
4.2 OVERVIEW REU-SUBASSEMBLIES
SUBASSEMBLY ASSIGNMENT CODE NUMBER*) REFERENCE
Processor Board P4N 486 (P4N) 84045 82230 4.3.1

Processor Board P4N 486 with Ethernet Controller 84045 82231 4.3.1/4.3.4
Serial Interface Board (SIB) 84045 83106 4.3.2
Opto-Isolated Input/Output Board (OIO) 84045 83xxx**) 4.3.3
Modems: 4.3.6
Modem, switched line (LGM 28.8) 84045 83246 4.3.6.1

Modem, switched line, ISDN (LGM 64K) 84045 83230 4.3.6.2
Modem, dedicated line (LGM 1200MD) 84045 83233 4.3.6.4
Modem, dedicated line (LGM 9600H1) 84045 83260 4.3.6.5
LGM Extender 2 Unit (LGM Ext) 84045 83903 4.3.6.6
Modem, dedicated line (ZU1) 57200 04405 4.3.7
Modem, dedicated line (ZUA29) 83131 72601 4.3.8
Star distributor (NFK29-1) 75864 81410 4.3.9
Multiplexer RS232 (MPX) 84045 83800 4.3.10
Power Supply: 4.3.11
AC/DC-Converter (Puls AP346) 84045 82350 4.3.11.1.1

AC/DC-Converter for CTU (MELCHER LM 1001-7R) 84045 90700 4.3.11.1.3
DC/DC-Converter, 36-72V (Puls APD346) 84045 79850 4.3.11.2.1
DC/DC-Converter, 18-36V (Puls APD346) 84045 79700
DC/DC-Converter for CTU (MELCHER BM 1001-7R) 84045 89800 4.3.11.2.2
*) The code numbers given may differ to those of the delivered installation in individual cases. In such case the actual code
number can be taken from the delivery list of the installation or the drawing set.
**) The code number of the OIO board depends on the configuration (input/output and voltage range).
Fig. 4-1 Circuit diagrams of subassemblies of RCSE 443
Ed. 01.02 4-1

RCSE 443 RMMC
Detailed Description Description and Operation
4.3 REU-SUBASSEMBLIES
4.3.1 Processor Board P4N 486
The processor board P4N 486 includes a flash disk (SAN disk) providing a RAM area ('RAM side')
and an EPROM area ('EPROM side'). The single-board computer P4N 486 is built up entirely in
high-speed CMOS technology and integrated on a simple Eurocard.
Optionally, the processor board P4N 486 may hold an Ethernet contoller interface. This allows the
REU to be linked up to a THIN-Wire Ethernet LAN.
The voltages (+5 V and +12 V) necessary for operation are supplied from the bus via VG connector.
The supply voltage of +12 V is only required for a CPU fan and for an external MAU subassembly
connected to the Ethernet AUI interface. A signal which monitors the revolutions of the fan down to
a full stop can be processed through pin 4 of this plug connector.
The processor board accommodates between 2 and 64 MB dynamic read/write memories (DRAM).
The memory is organized in 32-bit words, has one parity bit per byte and begins with the address
00000000H. Shadow RAM can be activated in the setup in 16-byte increments for the range from
C000:0000 to F000:FFFF. The BIOS is a flash EPROM with a capacity of 128 KB. Address space from
E000:0000 to F000:FFFF is reserved for the BIOS. The contents of the BIOS can be copied into the
Shadow RAM for more rapid execution of BIOS functions. In the actual version the E-segment is free
for operator usage after booting.
The CPU platform can be equipped with an Intel 486DX-compatible CPU. Types of 5 V and 3.3 V can
be used, which are e.g. i486DX(2/4), AMD486DX(2/4) and SGS486DX2/4. The system clock can be
set by jumper field J9 to 25, 30 or 33 MHz, from which the internal CPU oscillation is derived. J2 is
used to determine the multiplication factor for the internal clock according to the used CPU.
Cold-booting the processor leads to a reset of the CPU, of the entire on-board peripherals and of
all subassemblies connected via ISA 96 bus. It is initiated:
- when the +5 V supply voltage sinks below a threshold value (typ. 4.65 V, min. 4.5 V, max. 4.75 V)
for a certain time period,
- by the "watchdog time-out" function, which monitors program execution in the microprocessor
(monitoring of read access, which must be executed at least every 1.6 seconds),
- by the excess temperature watchdog which monitors the CPU housing temperature (temperature
sensor is set for a maximum housing temperature of +85 _C),
- by sending a reset signal to the C32 pin of the ISA 96 bus which is configured as a reset input (low
active, /RESET)
A battery-backed real-time clock (RTC) contains the time, the date, a wake-up time, as well as 128
bytes of CMOS RAM. Data contents are secured for more than 5,000 hours with the rechargeable
accu (30 mAh), which is located on the mother board. Battery supply voltage can be interrupted
through jumper J1, especially for long down-time periods (storage).
The processor board P4N 486 provides an integrated flash disk (SAN disk) connected via IDE bus.
The flash disk (min. 4 MB, also possible 8 MB resp. 16 MB) operates like a hard disk and is partitioned
into drive c: (so called 'EPROM side', min. 3 MB, max. 4 MB) and drive d: (so called 'RAM side', min.
1 MB, also possible 4 MB resp. 8 MB). The configuration files (*.SIT and *.OIO) are stored on 'RAM
side', the 'EPROM side' contains the DOS 5.x software and the REU application program.
4-2 Ed. 10.02

01.02
RMMC RCSE 443
DRAM Keyboard flash disk*:

2/4 MB Controller 3 MB EPROM
J9 J2 1 MB RAM
Clock Generator
96 pin VG-Connector:
25/30/33 MHz
x12 Data/Address/Control
Speaker (opt..) Buffer
CPU
X4
2 1
Real Time a b c
Interrupt Controller Clock Battery
XT
XT
AT
Power on/off Ethernet Interrupt (RTC) J1
Watch Dog connector
Reset
3
* for flash disk size 4 MB: EPROM 3 MB, RAM 1 MB

for flash disk size 8 MB: EPROM 4 MB, RAM 4 MB
for flash disk size 16 MB: EPROM 4 MB, RAM 12 MB
Fig. 4-2 Processor board P4N 486, block diagram
NOTE: In case of data loss or wrong data of configuration files or REU application program a speĆ
cial AUTOBOOT.BAT file is installed on the flash disk, which deletes the certain incorrect,
wrong data on the disk depending on the used type of dongle (adapter) connected to the
PC2 interface at the REU. After deletion the default application program is started to reĆ
configure the processor board (see also section 2.4.3).
4.3.2 SIB
SIB stands for Serial Interface Board. The card is employed in the REU for the implementation of asynĆ
chronous, synchronous and parallel communication channels. The INTEL controllers which are used
are PC-software compatible in order to allow compatibility for the entire system of the REU, which
employs an industry PC in Eurocard format as the central unit. The bus on which the card is located
is the MCE bus. All communications connections are implemented through the connector back
panel. The settings for interrupt assignment, base address assignment, signal specification and pollĆ
ing logic are all made on the card with jumpers. A maximum of 6 asynchronous channels and 4 synĆ
chronous channels may be realized in a system.
The bus drivers/receivers serve for bus coupling and buffering for the MCE bus. The PAL preproĆ
cesses the necessary chip-select signals, preprocesses the RD and WR signals and makes the
selection signals available for data/control words. In addition, it makes the signals available for the
.bis matching circuit and preprocesses the controls for the 8-bit parallel I/O processing.
The communication controllers are operated with the buffered system bus and supplied by the TTL
clock with a basic frequency of 18.432 MHz. The controllers preprocess their baud rate from this basic
frequency. The primary requirement for the synchronous communication controller (82530) is the
maintenance of the recovery time between two read/write processes. This time is summed with a
counter. In case the recovery time has not elapsed before the next read/write command, an I/O extenĆ
sion is initiated. In addition, two WAIT STATES are inserted with every read/write process.
Ed. 10.02
01.02 4-3
RCSE 443 RMMC
Interface modules serve to convert the TTL outputs of the controllers to the desired level, which are:
- Asynchronous Controller 1 (NS 16552) fixed at RS422
- Asynchronous Controller 2 (NS 16552) fixed at RS232
- Asynchronous Controller 3 (NS 16552 ) optional at TTL level or RS232 or RS422
- Synchronous Controller 1 (82530) optional at TTL level or RS232
- Synchronous Controller 2 (82530) optional at TTL level or RS422; TTL fixed
Asynchronous channels:
The existing controllers may assign interrupt lines independently (normal state). However, they may
also jointly poll interrupt lines. Jumpers serve for setting the interrupt line assignment, selection beĆ
tween XT and AT interrupts, the signal specification for channel 3. For the utilization of one of the interĆ
rupts IRQ 10, 11, or 12, it is necessary for a PC-AT to be available as the central unit.
In order to make possible operation of the communication channels 2 and 3 with the ZU1 (Tx inverted
on the KDI), configurable inverters are available on the SIB.
Synchronous channels:
The interface modules serve to convert the TTL outputs of the controller to the desired level, whereby
channel A and channel B may be offered optionally on the TTL level or on the RS232 level. The comĆ
munications controller is polled with the buffered system bus and provided with the basic frequency
through the TTL clock. The controller can preprocess its baud rate from this basic frequency.
The setting of the interrupt-request channel, whereby only one channel may be plugged at any time,
and the channel selection for the DMA operation is made by jumpers. For the utilization of one of the
interrupts IRQ 12, 14, or 15, it is necessary for a PC-AT to be available as the central unit.
Chipselect PAL
IRQ Logic
Oscillation Selection
Base address
I/O,R/W Conditioning
Waitstates sync.
Bus: Data, addresses, CS-x, INT-x, WR, RD, reset, oscillation

Bus
X1 Buffer
PC-Bus
ISA-96
Front panel 8 bit 8 bit Asynchronous Asynchronous Asynchronous Synchronous Synchronous

parallel parallel controller 1 controller 2 controller 3 controller 1 controller 2
out in DMA
1 2 1 2 1 2 A B A B
Life
Local
(NFK7...12, AUX IN 1...7)
Local
(NFK1...6, AUX OUT1)
RS422
RS422
RS232
RS232
TTL
PC2
RS232
RS422
RS232
RS422
RS232
RS232
RS422
TTL
TTL
TTL
TTL
TTL
PC1
IN/OUT 1a1 2a1 1a2 2a2 1a3 2a3 1sA 1sB 2sA 2sB
Connector Back Panel
Fig. 4-3 SIB, block diagram
4-4 Ed. 01.02

RMMC RCSE 443
4.3.3 OIO (optional)
The optional OIO board is used in the REU to connect IN or OUT control signals from/to external
equipment. It provides 32 decoupled inputs and outputs by means of optocouplers. The OIO is conĆ
trolled by In/Out commands. 4 I/O addresses are used, which can be set with jumpers (J3) in steps
of four starting from a fixed base address. On default it is set to 0230H to 0233H. The OIO consists
of the following functional groups:
- completely buffered and decoded processor bus interface
- four eightfold tristate line driver circuits
- four 8 bit registers with tristate outputs
- 32 optocouplers used for potential isolation (e.g. 24 Inputs, 8 Outputs)
INPUTS:
The input current for logical 0 is max. 1 mA, for logical 1 min. 10 mA. The voltage of the IN-signal
is adjustable by changing the input resistor of the respective optocoupler (factory adjustment). ForĆ
ward and feedback lines of the inputs are fed separately to connector J1. The inputs are protected
by antiparallel connected diodes. Interference pulses are suppressed by RC-filters in the signal path.
OUTPUTS:
The output drive capability is max. 150 mA, the supply voltage is 35 V. Forward and feedback lines
of the outputs are fed separately to connector J1. The outputs are protected by antiparallel connected
Z diodes. Switch-over time is approx. 100 ms depending on the actual pull-up resistor. During/after
a system reset all outputs are at the same potential because the optocouplers are not conductive.
The definition of the outputs and the associated levels is set by the initialization program.
4.3.4 Ethernet Controller (optional)
The optional Ethernet controller allows the REU to be linked up to a THIN-Wire Ethernet network
(LAN). The processor board P4N 486 may hold this optional interface.
4.3.5 ADC (optional)
The optional ADC board enables up to 16 single-ended channels and up to 8 double-ended chanĆ
nels to be coupled to analog signals converted to digital signals by the 13-bit A/D converter.
Ed. 01.02 4-5

RCSE 443 RMMC
4.3.6 Modem LGM

4.3.6.1 LGM28.8
The LGM 28.8 is a high speed modem for duplex operation which supports all common duplex moduĆ
lation procedures. The modem is designed for synchronous as well as for asynchronous data transĆ
mission according to the following CCITT modulation modes: V.34, V.32bis, V.32, V.22bis, V.22, and
V.21, which have implemented the data securing procedures according to V.42 and MNP4. Data comĆ
pressing to increase the baud rate is implemented according to V.42bis and MNP5. These procedures
enable a practical fault free transmission between two data terminal equipment (DTE) units. DependĆ
ing on the procedure the transmission rate can be increased up to 38400 Bd (autobaud) using V.42bis
and the AT -mode/reliable mode. The modem can also communicate with modems from other venĆ
dors at the same transmission rates, providing these modems comply with CCITT Recommendations
V.22 and V.22bis. Software configuration is possible using AT or DNL commands while hardware conĆ
figuration is performed employing the DIP switches located at the bottom and on one side of the moĆ
dule. It is designed for operation in public switched networks and consequently equipped with an inteĆ
grated automatic dialing facility (IAWD). Data connections can however also be set up by the subĆ
scriber dialing manually and pressing the data key. Point-to-point operation on dedicated lines
(leased or tie lines) is likewise possible. Almost all the modem functions can be set by the data terminal
equipment (DTE) using a command set in accordance with CCITT Recommendation V.25bis. Correct
operation of the microprocessor and the signal processors is monitored by an integrated circuit,
which initiates a "master reset" if one of these processors malfunctions (watchdog).
A data connection can be set up by means of either the integrated automatic dialing facility or the
automatic call acceptance feature. It is also possible to dial out or to accept incoming calls manually.
No dialing takes place on dedicated lines. All the V.25bis commands and messages are exchanged
via the interfaces which are also used to transfer the actual data. After a call request with identification,
the LGM checks whether the subscriber line is already busy, i.e. whether the subscriber is in the proĆ
cess of making a call. If not, the outside line is seized. The LGM then transmits the dialed digits which
have previously been transmitted by the DTE. After the dialing procedure, an intermittent 1300 Hz tone
is transmitted and the modem waits for a constant 2100 Hz answer tone. As soon as this answer tone
- which is transmitted by modems with an automatic call acceptance facility - is identified, the two
modems start the prolog (handshake).
La Busy detection
a2
Lb
Modem controller
b2
Data key detection

Ringing tone
detection
G
E
Setting
Fig. 4-4 LGM28.8, block diagram
4-6 Ed. 01.02

RMMC RCSE 443
A data connection can only be terminated by the DTE, unless there is no carrier for more than 250
ms/10 s. In this case, the line seizure is canceled by the LGM. Eighteen switches are provided on the
PC board for presetting the seven different operating modes, the four communication protocols and
various other parameters. A self-test is performed each time the modem is switched on. The default
setup is as follows: 2400 bd, V.22bis, dialing mode.
4.3.6.2 LGM64K (ISDN Modem)
The LGM 64K is an ISDN terminal adapter (module) in the Eurocard format for the use of public ISDN
switched lines and dedicated lines. In terms of hardware, the LGM64K is built up the same as the
LGM28.8, and the pins are compatible. It possesses the same operations set and the same definitions
for the DIP switches. In software, the module is configured through AT and V.25bis commands and
the hardware is configured through DIP switches. The modem is connected to the line through the
S0 terminal and can be operated through the implemented D channel protocols 1TR6 and DSS1 both
in the national and in the European ISDN network. One B channel with 64 kbits/s is available for data
transmission. Data transmission to the terminal device may take place either synchronously or asynĆ
chronously through the serial interface (TTL level on the VG bar). Matching the speed of the serial
interface to the ISDN speed of 64 kbit/s is managed by the bit rate adaptation according to ITU-T
V.110. The LGM64K modem may be remotely configured.
4.3.6.3 Connection Setup

4.3.6.3.1 Connection Setup via Switched Circuits
' Autodialing
"Autodialing" means that the connection is set up by the modem automatically. The desired teleĆ
phone number is transferred to the modem by means of a command. This dialing command can be
preceded by a command for setting the transmission parameters. The commands can be transferred
automatically with the desired data (transmission parameters and telephone number) by the commuĆ
nication program. The user does not need to do anything more.
4.3.6.4 Dedicated Line Modem LGM1200MD

See Fig. 4-5.
The LGM1200MD is a universally applicable half duplex permanent line modem. The data transfer rate
is 1200 or 600 bit/s. The LGM 1200MD (MD=multidrop) is optimized for operation on permanent two-
wire lines in the so called party line mode. In this case, several modems are served by a control station
via one line only (polling mode). On replacement, the LGM1200MD is used in stations instead of the
ZUA29, on remote side instead of ZUA29 and NFK. It occupies one LGM slot.
The LGM1200MD operates in the voice band with FSK modulation, i.e. frequency shift keying in con-
formity with V.23 at 1300 and 2100 Hz with up to 1200 bit/s and 1300 and 1700 Hz with up to 600
bit/s. The data transfer method is half duplex or simplex. Generation of interfering trailing bits (on
deactivation of the remote transmitter) is largely excluded by process–controlled ”fast clamping” of
the received data. In the asynchronous mode, data transfer from 0 to 1200 bit/s or 0 to 600 bit/s is
possible, independently of the code and speed. A microcomputer controls and monitors all functions
of the LGM. Parameters for the processor and processor–independent circuitry can be influenced
by means of 14 adjacent coding switches. A power–on self–test is run. LEDs indicate transmit and
receive data activity or line seizure. The connected trunk lines are accessible via an ISEP test socket
on the front panel (for monitoring the analog line signal).
Ed. 01.02 4-7

RCSE 443 RMMC
When the ”TEST” key on the front panel is pressed, the modem is switched to the ”close range analog
loop” (without transmitter) while the key is pressed. This is also active during the transmission phase
(the connection is then aborted).
In half duplex mode on two–wire connections, the participating data transmission equipment each
seizes the telephone line in succession. The respective DTE responsible for transmission controls
operation with the 105/S2/RTS (ready to send) signal. This activates the modem’s carrier. The DTE
must only offer data to the modem via the 103/D1/TD line once a specific delay after ready to send
has elapsed and the modem has switched the 106/M2/CTS (clear to send). During the delay time
between the ”ready to send” 105/S2/RTS and ”clear to send” 106/M2/CTS signals, the signal detector
of the receiving modem will already react and will adapt the clock signals of the receiver to the clock
pulse of the incoming signals.
With the 109/M5/DCD (receive signal level) signal, the receiving modem indicates that it is capable
of forwarding received data (104/D2/RD). If the 109/M5/DCD (receive signal level) signal is not in the
ON state, the receive interface line (104/D2/RD) is in the ”I” state. A so–called fast clamping circuit
is integrated in the LGM1200MD to avoid trailing bits during reception. It is processor–controlled, with
the result that no more than 1 byte can occur as a trailing byte.
transmit path
Over-
voltage
protection Level
a2 adaptation TxA
La
Lb FSK signal
b2
E converter
Level
connection
Filter RxA
adaptation
2-wire line
receive path
TD
Microprocessor
RD
DIL switch TTL/V.24 interface
Set 1...14 Data in/out
Fig. 4-5 Modem LGM1200MD, block diagram
4.3.6.5 Dedicated Line Modem LGM9600H1
The LGM9600H1 is a universally applicable half duplex permanent line modem. The data transfer rate
is 1200 or 600 bit/s. It occupies one LGM slot.
The LGM9600H1 operates in the voice band with FSK modulation, i.e. frequency shift keying in con-
formity with V.23 at 1300 and 2100 Hz with up to 1200 bit/s and 1300 and 1700 Hz with up to 600
bit/s. The data transfer method is half duplex. Generation of interfering trailing bits (on deactivation
of the remote transmitter) is largely excluded by process–controlled ”fast clamping” of the received
data. In the asynchronous mode, data transfer from 0 to 1200 bit/s or 0 to 600 bit/s is possible, inde-
pendently of the code and speed. A microcomputer controls and monitors all functions of the LGM.
4-8 Ed. 01.02

RMMC RCSE 443
4.3.6.6 LGM Extender 2 Unit
The LGM Extender 2 Unit is an opto- and electrically isolated level converter. It is able to convert TTL
signals to RS232 resp. to RS422 signals and vice versa. The maximum data transfer rate is 38.4 kbit/s
(for RS232). The LGM Extender 2 Unit occupies one LGM slot and is normally plugged into LGM4 slot
of RCSE subrack. The RS232 resp. RS422 outputs are led to CEPT plug outputs La, Lb, a2, b2, G,
E, TXA, TXB, RXA, RXB (CEPT plug X1, see Fig. 4-6). The signals are connected to the pins of LGMx
(x=1..4, preferred 4) as described in section 2.2.3.2. This signals are also led to plug X4, a conversion
from Speedy 10 (X4) to DB 9 (LGMx connector) results in the same pin assignment than for LGMx
connector. This is not used for RCSE application. Another Speedy 10 connector X3 is provided to the
user for RS232 data test purposes, the signals are not opto- and electrically isolated, the signal levels
are indicated via LEDs (V1..V16).
All output signals can be inverted by setting the jumpers X20 to X27 on the LGM Extender board. The
terminal bars S1 and S2 are not used for RCSE connection (see also section 2.3.3.12).
LGM1..4
La, Lb, a2, b2, TxA, TxB, RxA, RxB, E, G
(SUBD 9)
at Back-
panel Electrical Isolation
+5V (+/-10%) +5V isolated (+5%,-2%)
GND -GND
DC/DC-Converter
Opto-Isolation Level Conversion

RS232
X1
X1
X30..37
TxD, RxD, RTS, CTS, DTR,, DSR, DCD , RI
TTL
SIB
RS422
TTL Optocoupler
Processor only for connection to
Board RS232 X4 DME via separate cable,
then LGM1..4 port may
not be used.
(not used in RCSE)
X3 LEDs V1..V16
RS232 Data Test
RCSE LGM Extender 2 Unit
Fig. 4-6 LGM Extender 2 Unit, block diagram
4.3.7 Modem ZU1

See Fig. 4-7.
The ZU1 is a voice frequency telegraphy facility (VFT) for transmitting digital signals on transmission
links with a frequency range between 300 Hz and 3.4 kHz, such as telephone lines. The modulation
method is frequency shift keying (FSK). The ZU1 can transmit data asynchronously in any code up
to a maximum telegraphic speed of 600 baud. The information which must be transmitted to the naviĆ
gation station (voice frequency telegraphy signals) takes the form of commands and interrogations.
The center transmission frequency is 2760 Hz, with a frequency deviation of ±200 Hz. These signals
are converted into DC signals in the modem and supplied to the navigation station via a V.24 interface.
In the opposite direction, the information which must be transmitted to the remote control system -
status messages and acknowledgments - is offered to the V.24 interface of the ZU1 by the navigation
station in the form of DC signals. The modem converts the information into AC signals with a center
transmission frequency of 1320 Hz and a frequency deviation of ±200 Hz. The connection is impleĆ
Ed. 01.02 4-9

RCSE 443 RMMC
mented using a 2-wire line on which duplex operation is possible. The main functional units of the
ZU1 are the balanced-to-unbalanced transformer, the receive branch and the transmit branch.
The modulator IS7 converts the digital DC signals into AC signals. The frequency of an RC generator
is shift-keyed by a control signal. The modulator has a transmitter disconnection facility IS8, which
allows the sound to be switched on and off by remote control. The quiescent tone is switched off autoĆ
matically if the control line is interrupted. The transmit filter is an active, 4th-order filter. It serves to
limit the frequency spectrum of the modulated signal. The gain of the filter can be set with jumpers
to ±0 dB, -3 dB, -6 dB or -9 dB. The transmit level is set approximately by a voltage divider, which
is decoupled from the transmit filter by means of a buffer preamplifier. The level can be reduced by
up to 30 dB in steps of 10 dB. The fine setting is made in steps of 3 dB using the transmit filter.
The line disconnection circuit IS11 isolates the transmitter and the receiver jointly from the trunk cirĆ
cuit. The trunk circuit is disconnected automatically if the control line is interrupted. It is matched to
the ZU1 by a balanced-to-unbalanced transformer, and is therefore electrically isolated from it and
terminated with 600 W. Test sockets are provided on the front panel of the ZU1 for measuring the transĆ
mit and receive levels. The ZU1 is set to 4-wire operation in conjunction with the NFK.
The receive preamplifier IS2 has two stages. Its gain can be set to either 6 dB or 26 dB. The receive
filter is a 5-stage L/C filter with a band-pass characteristic. A limiting amplifier IS3 is connected to
the output of the receive filter. It amplifies the signal which has been attenuated by the receive filter,
and its limiting action prevents the downstream demodulator from being overdriven. This reduces the
effects of level fluctuations on the transmission path.
Extension for additional lines
Quiescent tone Line External supply
Generator and Modulator disconnection Transmit filter Preamplifier Level setting disconnection
Output amplifier
IS7 IS8 IS6/4,1 IS6/2 IS11 IS6/3
RXD Receive Data
Local line RTS Request To Send
DTR Data Terminal Ready Line Remote line
RXD V.24 matching TR3
TXD Transmission Data
RTS DSR Data Set Ready
DTR
Receive enable Demodulator
TXD
TR2
IS10 IS4
Level monitoring Limiting amplifier Receive filter Receive preamplifier
DSR Line
disconnection
TTL IS3 IS2/2,1 IS1
Level conversion Extension for up to 14 additional lines
Fig. 4-7 Modem ZU1, block diagram
4.3.8 Modem ZUA29
The ZUA is an interface board for converting a V.24/V.28 (RS232C) or V.11 (RS422) interface to an FSK
signal (frequency shift keying) according to CCITT V.23 (half duplex operation). The digital interface
can be set to either V.24/V.28 or V.11. It is possible to connect transmission links with a frequency
range of 300 Hz to 3.4 kHz, and to transmit data asynchronously and code-transparently up to a rate
of 1200 baud. The information which must be transmitted (voice frequency telegraphy signals) takes
the form of commands and interrogations. The center transmission frequency at 1200 Bd (standard
setting) is 1700 Hz, with a frequency deviation of ±400 Hz (i.e. fu=1300 Hz and fo=2100 Hz). The conĆ
nection is implemented using a 2-wire line. The received information (status messages and acknowĆ
ledgments) is converted into DC signals in the modem and supplied to the connected station via the
V.24 interface. In the opposite direction, the information (commands and interrogations) which must
4-10 Ed. 01.02

RMMC RCSE 443
be transmitted from the connected station are offered to the V.24 interface of the ZUA in the form of
DC signals. The modem converts this information into modulated AC signals.
In conjunction with the NFK, the ZUA29 is set to 4-wire operation, 1200 Bd, V.23.
The ZUA incorporates a 2/4-wire amplifier, which can be looped into a transmission path in order
to compensate the attenuation. It is also used as a switching network for coupling the FSK transmit
and receive signals in and out. The amplifier is switched permanently in 4-wire mode; in 2-wire
mode, it is through-connected in the desired direction according to the incoming levels. Sequence
control is handled by a microcomputer (63701 type).
The ZUA can be looped in to implement a transition from 2-wire to 4-wire lines. Tandem operation
with a high input impedance and a variable output impedance is also possible. The microcomputer
monitors the transmit signal of the ZUA and disconnects the transmit direction as soon as the transmit
level is switched on for more than 1 s. A watchdog timer checks that the microcomputer is functioning
correctly. The voltage monitor trips a reset if the 5 V operating voltage is no longer present.
In addition, a continuous tone can be switched in the transmit direction in order to adjust the level
of the ZUA. The tone can either have a constant frequency or be an FSK signal for tuning the internal
FSK receiver. The activity of the transmit and receive data and the levels on the connected lines are
indicated by LEDs. The connected trunk circuits are accessible via ISEP test sockets on the front
panel. The gain can be set separately with jumpers for each transmission direction. The signals of
F11 and F21 are supplied to the modem.
The transmit signal of the modem is switched to the F12 and F22 outputs with the signal of the analog
switch (MRTS). The transmit level of the modem can be set jointly for both outputs by means of jumpĆ
ers. The LD A and LD B LEDs indicate the receive levels of F11 and F21, while the TxD and RxD LEDs
indicate activity on the transmit and receive data lines. The CTRS interface signal switches the transĆ
mit level of the modem via MRTS. The MDCD input signal is switched to the TCRR interface line and
indicates readiness to receive.
Level
detector
PE1
S12 S13 S21
T101 T202
F11 D105 D102B D106 D201 D202A F22
S11 S11 S23 S22
F12 F21
T102 T201
D101 D102A D201 D206 D202B D205
F11, F12, F21, F22 AF-interfaces D303, MRTS Level

detector
PE2
S11 to S13 and S21 to S23 Control lines 301
LD A, LD B LED's
PE1, PE2 Test jack MRTS = Modem Request to Send
TCRST = Transmitter to Controller ReStart
FSK- Mode CTRS = Transmitter to Controller Request to Send
Watch- Signal converter LD A CTSD = Controller to Transmit Send Data
5V LD B
dog- Monitor (modem) TCRD = Transmitter to Controller Receive Data
Timer TCRR = Transmitter to Controller Receiver Ready
MDCD = Modem Data Carrier Detect
S11,S12
S13
Microcomputer V.24-/RS422-Interface
S21,S22
S23
TCRST
TCRD
CTRS
TCRR
TCRR
CTSD
TCRD
A/B
A/B
A/B
A/B
28
28
Fig. 4-8 Modem ZUA29, block diagram
Ed. 01.02 4-11

RCSE 443 RMMC
4.3.9 Star Distributor NFK 29-1

See Fig. 4-9.
The NFK can link up to six different lines, each of which can be set to either 2-wire or 4-wire operaĆ
tion. Two NFKs with up to 12 lines can be connected in the REU. If NFKs are used in the top section,
each line can be switched to a standby top section as a simulated standby line. A common transĆ
former of the NFK in the top service section is used for the service line and the simulated standby line.
Each line can be disconnected separately by means of a control line.
The control inputs are electrically isolated from NFK ground. The control states of the lines are indiĆ
cated by means of LEDs on the front panel (LED lit = line disconnected). All the inputs/outputs of the
line interface have a balanced impedance of 600 W and are electrically isolated from one another. The
transmit and receive levels can be measured at the test sockets on the front panel.
ZU-Interface Line amplifier 2...6 Line Interface
F1 IN Analog F1 AB
Amplifier Amplifier Trans-
Switch former
0 dB/+3 dB
(4-/2-wire)
UF1 Opto- Hook

coupler LED F1 (-3dB)
0 V/12 ... 72 V
F1 OUT Analog Trans- F1 IN

Power Amplifier
source Switch former F1 IN/OUT
0 dB/+20 dB
Line amplifier 2...6 NE 12 NE 11
NOTE: Only 1 of 6 line distributors (F1...F6) is shown. Simulated Standby Line
Fig. 4-9 Star distributor NFK 29, block diagram
4.3.10 Multiplexer RS232
The Multiplexer RS232 (MPX) board is used to connect ILS subsystems (e.g. LOC, GS) via dedicated
lines to the RCSE. Each Multiplexer RS232 board provides six of these dedicated lines. The board
is used within remote control equipment instead of the star distributor NFK29. On the ILS subsystem
side an RS232 resp. RS422 modem builds the dedicated line connection instead of a ZU modem.
The MPX board has to be plugged into the NFK1 or NFK2 slot of the remote control subrack. It is also
possible to use two of the MPX boards (plugged into NFK1 and NFK2 slots) to provide 12 of the dediĆ
cated line connections to ILS subsystems.
The MPX RS232 is internally driven by the 1a3 channel of the Connector Back Panel (CBP) of the Serial
Interface Board (SIB).
The 6 outputs (channels) of the MPX board are configurable via jumpers. The possible output modes
are RS232, RS422 or TTL. The mode of the TXD and RXD (RS232 or TTL) input channels for the board
is also configurable. LEDs on the front side of the board indicate the state of the TXD and RXD input
channels and of the output channels 1 to 6.
4-12 Ed. 01.02

RMMC RCSE 443
4.3.11 Power Supply
4.3.11.1 AC/DC-Converter
4.3.11.1.1 AC/DC-Converter Puls AP346
The AC/DC-Converter contains a two-stage long-range transformer (48/60 V) and an active MOSĆ
FET synchronous rectifier. The supply voltage at the input may be 100 to 240 VAC, and the allowable
output power is 60 W. Over-voltage protection (OVP) and over-temperature protection (OTP) preĆ
vent problems during operation under abnormal ambient conditions.
16
PF
30 T3.15A/250V
L F
Cycle 4
(Vin) I converter
Vout1
L 5V
Control
U T 75 kHz 6
typical Control Reglulator
PF OVP
28 ϑ E
8
N R
GND1
(GNDin)
10
32 Temperature
PE monitoring
OTP
18
In-phase Vout2
regulator +12 V
Temperature
monitoring
OTP
20
GND2,3
22
In-phase
regulator Vout3
-12 V
Fig. 4-10 AC/DC-Converter (Puls AP346), block diagram
Ed. 01.02 4-13

RCSE 443 RMMC
4.3.11.1.2 AC/DC-Converter VERO TRIVOLT PK60
NOTE: This AC/DC-converter was used in former versions of the RCSE 443.
See Fig. 4-11.
The AC/DC converter contains three regulators for generating the desired voltages. The converter
can be switched between AC input voltages of 115 and 230 V. Some protection mechanisms are proĆ
vided, like OverVoltage Protection (OVP) for the 5 V output voltage generation, or a powerfail signal
generation if a minimum output voltage of 4.8 V is reached.
+5V
+ Sensor
Reg.
OVP
Driver - Sensor
GND 5 V
L
Power Supply
Monitoring
Powerfail
N +12 V
−ϑ
PE Reg.
115/
230 V GND 12V
Reg.
Driver
-12 V
Main
Regulator
Fig. 4-11 AC/DC-Converter (VERO TRIVOLT PK60), block diagram
4-14 Ed. 01.02

RMMC RCSE 443
4.3.11.1.3 AC/DC-Converter MELCHER LM 1001-7R Option A
See Fig. 4-12.
The AC/DC converter comprises an input voltage range from 85 to 264 VAC. It is used within a CTU
19 inch cabinet. The converter inputs are protected against surges and transients occuring at the
source lines. An input over- and undervoltage lock-out circuitry disables the outputs if the input voltĆ
age is outside the specified range. All outputs are open- and short-circuit proof and are protected
against overvoltages by means of built-in suppressor diodes. The outputs can be inhibited by a logĆ
ical signal applied to the connector pin 2 (i). LED indicators display the status of the converter and
allow visual monitoring of the system at any time. Full input to output, input to case, output to case
and output to output isolation is provided.
The modules are designed and built according to the international safety standard IEC/EN 60950 and
have been approved by the safety agencies LGY (Germany) and UL (USA).
A temperature sensor generates an inhibit signal which disables the outputs if the case temperature
exceeds the limit. The outputs are automatically re-enabled when the temperature drops below the
limit.
Using option A of the AC/DC converter module includes test sockets provided at the front panel of
the module for check of the output voltage. The output voltage is sensed at the connector pins inside
the module.
i
2
Main control circuit
20
Output 1
U01
Filter
Vi+ 23
Forward converter
29
approx. 70 kHz
Input Filter
14
Control Output 2
U02
circuit Filter
17
Fuse
Vi-
8
32 Control Output 3
circuit Filter U03
11
26
Fig. 4-12 AC/DC-Converter (MELCHER LM 1001-7R), block diagram
Ed. 01.02 4-15

RCSE 443 RMMC
4.3.11.2 DC/DC-Converter
4.3.11.2.1 DC/DC-Converter Puls APD346
See Fig. 4-13.
The DC/DC-Converter contains a two-stage long-range transformer (48/60 V) and an active MOSĆ
FET synchronous rectifier. The DC nominal input voltage may be in a range from 30 to 90 V, and the
allowable output power is 60 W. Over-voltage protection (OVP) prevent problems during operation
under abnormal ambient conditions.
28 ϑ
+ Vin F
Cycle 4
I converter
Vout1
L 5V
Control
U T
75 kHz 6
typical Control OVP Reglulator
T4A/250 V E 8
- Vin
R
30 GND1
32 10
PE
Temperature
monitoring
OTP
18
In-phase Vout2
regulator +12 V
Temperature
monitoring
OTP
20
GND2,3
22
In-phase
regulator Vout3
-12 V
Fig. 4-13 DC/DC-Converter (Puls APD346), block diagram
4-16 Ed. 01.02

RMMC RCSE 443
4.3.11.2.2 DC/DC-Converter MELCHER BM 1001-7R Option D
See Fig. 4-14.
The DC/DC converter comprises an input voltage range from 14 to 70 VDC. It is used within a CTU
19 inch cabinet. The converter inputs are protected against surges and transients occuring at the
source lines. An input over- and undervoltage lock-out circuitry disables the outputs if the input voltĆ
age is outside the specified range. All outputs are open- and short-circuit proof and are protected
against overvoltages by means of built-in suppressor diodes. The outputs can be inhibited by a logĆ
ical signal applied to the connector pin 2 (i). LED indicators display the status of the converter and
allow visual monitoring of the system at any time. Full input to output, input to case, output to case
and output to output isolation is provided.
The modules are designed and built according to the international safety standard IEC/EN 60950 and
have been approved by the safety agencies LGY (Germany) and UL (USA).
A temperature sensor generates an inhibit signal which disables the outputs if the case temperature
exceeds the limit. The outputs are automatically re-enabled when the temperature drops below the
limit. Using option D (which includes also option V) of the DC/DC converter module includes an input
and/or output undervoltage monitoring circuitry. A safe data signal output (D0 to D9) is generated at
pin 5 (D/V) as soon as one of the monitored voltages drops below a preselected threshold level (opĆ
tion D). Additionally an ACFAIL signal (V signal) is generated (option V) which conforms to the VME
standard.
i
2
D/V
Main control circuit 5
20
Output 1 U01
Filter
Vi+ 23
Forward converter
29
approx. 70 kHz
Input Filter
14
Control Output 2 U02
circuit Filter
17
Fuse
Vi-
8
32 Control Output 3 U03
circuit Filter
11
26
Fig. 4-14 DC/DC-Converter (MELCHER BM 1001-7R), block diagram
Ed. 01.02 4-17

RCSE 443 RMMC
4.4 CTU/RWY-SELECT
See Fig. 4-15.
The CTU is the Tower status display and obtains its data via a RS422 interface from the REU via conĆ
nector 2a1/CTU. It consists of the submodules Processor unit PU-51, LED/display Driver, Status LED
and Select keys. The generic software (firmware) of the PU-51 of the CTU controls the display and
key activations. The CTU can display the main status of 8 subsystems. The CTU can be mounted for
standard application in a 19 inch cabinet with separate power supply (+5 VDC). Two or more CTU
panels can be cascaded.
A RWY-SELECT panel with indicator can be mounted next to the CTU in the 19 inch subrack instead
of the blank panel. The RWY-SELECT panel is controlled by the CTU panel.
Status LED
Select keys
LED display driver
Audible Device
Processor unit PU-51 RWY-SELECT
RWY1/2 select
SERIAL DATA to/from REU
Fig. 4-15 CTU/RWY-SELECT, block diagram
4-18 Ed. 01.02

RMMC RCSE 443
4.5 RCSE 443 SOFTWARE
4.5.1 General
The central feature of the RCSE/REU is an industrial PC system which uses MS-DOS (Version 3.3
or higher). All the data required to run the remote control system correctly (the operating parameters)
is saved in a file on the 'RAM side' of the flash disk on the processor board P4N 486. The actual RC
program and the operating system (MS-DOS) are stored on the 'EPROM side' of the flash disk on
the processor board P4N 486 as normal MS-DOS files.
4.5.1.1 Data Protection
The flash disk on the processor board P4N 486 is managed by MS-DOS. MS-DOS is loaded when
the system is started up. The RC program is loaded in the program memory with the DOS automatic
execution batch file function (AUTOEXEC.BAT). The configuration file (CONFIG.SYS) is loaded next.
The configuration file can only be modified by authorized persons.
Two cyclic redundancy check bytes, which ensure the necessary data transmission reliability, are apĆ
pended to all telegrams sent during communication via the synchronous and asynchronous interĆ
faces. The only exception (for historical reasons) is communication via the ZU1 with the various SYSĆ
TEM 4000 navaids stations, which have in the past been remote-controlled with the RCMS 4000. A
parity byte is used to protect this data.
4.5.1.2 Maintenance Mode and Password

The REU system incorporates a maintenance mode, in which the REU itself and all the stations can
be operated and programmed. The maintenance mode is controlled via the following interfaces:
- Maintenance Data Terminal (PC)
- Remote Maintenance Center (RMC)
- Ethernet LAN
In order to protect the REU system against outside, unauthorized access at these open interfaces,
the REU demands that a code be entered (variable password with 6 characters). A login command
and the <password> are transferred to the REU whenever the (WIN) ADRACS control program is
started; a logout command is transferred when it is exited.
The login procedure does not allow more than 3 input attempts. The first three unsuccessful attempts
are acknowledged with the following error code: PASSWORD AUTHORITY FAILURE. If a further unĆ
successful attempt is made, all inputs are initially disabled for the next 3 minutes, i.e. no more error
codes are output by the REU in response to telegrams during this period, even if the password is enĆ
tered correctly. The error code LOGIN REU CLOSED is generated after any input. The input lock is
extended by another minute each time a new attempt is made; it is increased to 60 minutes after the
10th attempt. When this period has elapsed, the error code THERE WERE WRONG LOGINS is generĆ
ated the next time a correct login attempt is made, to inform the user that there has been an unauthoĆ
rized access attempt. If there is no communication after a correct login, this interface is locked by the
REU after 2 minutes, i.e. a new login command must be entered.
Maintenance communication can only be set for one user at a time (PC, Ethernet LAN or maintenance
center), i.e. all other users have no access to maintenance mode (read-out data possible) until the
end of the current session. The other users receive an OTHER USER IS MASTER error message in
this mode.
Ed. 01.02 4-19

RCSE 443 RMMC
4.5.2 Communication via Switched Lines (PTT)
Providing a modem is installed in the REU, it can be used to exchange data with any other RMC (reĆ
mote maintenance center) or PC. The protocol corresponds to the PC telegram types. The RMC has
either a master function or a slave function.
Master function: If the requirement for this function is specified in the configuration file, a connection
to the remote maintenance center is set up according to V.25bis conventions each time a stable status
change occurs in the complete system (stable for at least 5 minutes), in order to report the new status.
If the connection cannot be set up successfully (busy, etc.), up to six further attempts are made alterĆ
nately using switched circuits 1 and 2 (if the latter exists). A statistical delay of at least 1 minute and
no more than 6 minutes is inserted between the dial attempts (random-function generator). The staĆ
tistical delay is necessary due to the fact that several REUs may want to send a status message to
the remote maintenance center at the same time. It prevents them from blocking each other. The conĆ
nection is cleared down again after the telegrams have been transmitted successfully.
Slave function: Either the status or maintenance data is transmitted when the remote maintenance
center is called, depending on the situation and on a correct login command being entered. The hardĆ
ware of the REU supplies a modem (dial modem 28.8/64K) via a USART (on SIB). The information
then passes via the telephone network (PTT) to the remote maintenance center.
NOTE: Telegrams are exchanged in this way externally only with subscribers who can be dialed
by the REU (RCSE/LCSU). It is not planned to allow telegrams to be exchanged following
an external call.
4.5.3 Data Com Error
The data com error of a station is set if an attempt to exchange telegrams between the REU and the
desired station fails x times in a row. The number "x" can be set in the configuration file for each station.
The data com error is reset after each successful telegram exchange and the data com error counter
is set to 0.
4.5.4 PC Control / PC Maintenance
If telegrams are sent to a station with a PC via the REU, and if these telegrams contain a set PC control
bit, PC control and PC maintenance are set for this station. PC control (not PC maintenance) is also
set for all the stations which either belong to this system (runway) or which are collocated with it. PC
control is reset 10 s after the last telegram with the PC control bit. The delay for PC maintenance is
7 s. This ensures that the INC does not start to buzz as soon as the MAINTENANCE lamp goes out.
4.5.5 Switch Control
If telegrams are sent to a station with a PC via the REU, and if these telegrams contain a set switch
control bit, switch control is set for this station. This telegram also contains the states of the two switch
control switches (on the INC board). Switch control is set additionally for all the stations which either
belong to this system (runway) or which are collocated with it. Switch control is reset 10 seconds after
the last telegram with the switch control bit. If a PC is switched to a control panel with switch control,
an RPU IS MASTER message is output on the PC.
4-20 Ed. 01.02

RMMC RCSE 443
4.5.6 Runway Information
4.5.6.1 Runway Status
The runway status only refers to the stations which belong to this runway. If no stations belong to the
runway, all the states will be "OFF". The meaning of the Runway status is shown as a logical AND-
combination.
OPERATIONAL (not ALARM (DME, FFM, MARKER)) and (not Local-Control (GP, LLZ)) and
NORMAL (GP, LLZ)
DEGRADED (not OPERATIONAL) and (not ALARM (GP, LLZ))
SHUTDOWN (not OPERATIONAL) and (not DEGRADED)
ENABLE DATA-COM (DME, GP, LLZ) and (not Local-Control (GP, LLZ)) and
(not PC-Control (DME, GP, LLZ)) and (not (Shut-Down-TX1 and
Shut-Down-TX2 (DME)) and (not Switch-Control (DME, GP, LLZ))
4.5.6.2 Runway Select

The runway is normally selected via the CTUs. The CTUs send the status of the runway select switch
(key switch) to the REU every 2 s. This telegram also contains the states of the two runway select
enable switches (on the CTU board). The REU only evaluates the runway select switches whose runĆ
way select enable switches are set to "ON". The status of the runway select switch is saved in the
runway select bit. If a valid runway select telegram is not received for a runway for more than 10 s,
the REU assumes that the corresponding CTU is no longer functioning correctly and allows the PC
to manipulate the runway select bit for this runway. This only applies until another valid telegram is
received from the CTU. Otherwise, the PC is not allowed to alter the runway select bit.
If there are several cascaded CTUs, the previous CTU in the chain which is set to enable for one runĆ
way, checks whether or not the next CTUs have the same setting for the same runway. If not - e.g.
if CTU 1 is set to enable and CTU 2 to disable - the next CTU is ignored. If the opposite is true - i.e.
if CTU 1 is set to disable and CTU 2 to enable - there are no restrictions. A runway can only be shut
down by the master CTU which is set to enable for it. The other CTUs in the chain are set to disable.
4.5.6.3 Automatic Disable (Forced Shutdown)

The GS, LOC and marker stations can be disabled automatically. Two stations (master stations),
whose alarms are to cause the stations to be shut down, can be defined for each of the above types.
They are defined with the runway select bit, which is ANDed with the automatic disable bit.
There are two configurable times for each master station to which the automatic disable function is
to apply. The first time determines the delay after an alarm before the station is shut down ("ON" time).
The second time defines the delay which elapses before the station is switched on again after the
alarm ("OFF" time). The following rules must be observed when defining the automatic disable states:
- The automatic disable function is activated for a station (or remains active) if one of the master staĆ
tions has an alarm for longer than the "ON" time.
- The automatic disable function is deactivated if all the master stations have no more alarms for
longer than the "OFF" time.
In all other situations, the automatic disable state remains the same. When the REU is started up, an
alarm at a master station does not activate the automatic disable function. This is not possible until
either 60 seconds have passed since the master station alarm was tripped or after the alarm has been
canceled again. In the case of the markers, the automatic disable state is frozen when PC or switch
control is set and not updated again until the markers no longer have PC or switch control.
Ed. 01.02 4-21

RCSE 443 RMMC
4-22 Ed. 01.02

RMMC RCSE 443
Description and Operation Maintenance
CHAPTER 5
MAINTENANCE
5.1 ORDINARY MAINTENANCE
There are no activities for ordinary maintenance.
5.2 PREVENTIVE MAINTENANCE
Preventive Maintenance is scheduled in daily, weekly, monthly or yearly measures which are necesĆ
sary or recommended. The following table contains these recommendations.
After initial setup Basic settings:

For first alignment procedures for Navaids 400 and SYSTEM 4000 staĆ
tions (LLZ, GP, FFM, CVOR, DVOR) the ADRACS user program has to
be used, see Technical Manual ADRACS, code no. 83140 55324, section
3.3. For DME/TACAN refer to the appropriate technical manuals.
Dial numbers:
It is useful to generate a dial number directory. This is done with 'Edit phoĆ
nenumber File' of the RC Management menu FILE TRANSFER. The diĆ
rectory is created automatically in the file "site name\*.PTT" in the PC.
Daily No recommended activities.
Weekly HISTORY file:
The HISTORY file of a station should be stored in the PC. It is recomĆ
mended to do this weekly at first. Afterwards it may be done monthly or
if a change in history has taken place.
Back-Up:
A regular back-up of collected data on a separate floppy disk or at least
a regular printout should be performed to prevent data loss of mainteĆ
nance data, collected over a longer period. It is recommended to do this
weekly at first. Afterwards it may be done monthly or if a change has taken
place.
Monthly DATE/TIME:
It is recommended to check the correctness of the REU Date and Time.
An incorrect time or date will result in differences in summer time and winĆ
ter time setting or in other differences. If the time and date are incorrect,
adjust with DATE&TIME REU in the RC Management menu.
Yearly No recommended activities.
Ed. 01.02 5-1

RCSE 443 RMMC
Maintenance Description and Operation
5-2 Ed. 01.02

RMMC RCSE 443
Description and Operation Annex NAV-LCU
Annex
NAV-LCU 443
Description and Operation
RMC-R RMC-C
PTT
LCSU/CSB
VOR 431
NAV-LCU 443
TAC ELTA
VOR
4000 TAC ELTA
Ed. 01.02 A
RCSE 443 RMMC
Annex NAV-LCU Description and Operation
Table of effective pages

Basic edition: 01.01
Pages Ed.-No. Remarks
A 1 01.02
B 1 01.02
AN-1 to 14 1 01.02
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 Corporation. Pentium is a registered trademark of the Intel Corporation.
B Ed. 01.02
RMMC RCSE 443
Description and Operation Annex Nav-LCU General Description
CHAPTER 1
GENERAL DESCRIPTION
1.1 GENERAL
This Annex NAV-LCU to the Technical Manual RCSE 443, Ref. No. 83140 55322, contains additional
information for the NAV-LCU 443.
The chapters and sections of this annex are similar to the chapters and sections of the Technical
Manual RCSE 443, therefore it is easy for the reader of this annex to build a connection between the
annex information of NAV-LCU and the information within RCSE 443 manual.
1.2 SYSTEM OVERVIEW
The NAV-LCU 443 is a device used as local communication interface between en-route navigation
systems TACAN, ELTA, (D)VOR and the RMC. The NAV-LCU comprises the Remote control ElecĆ
tronic Unit ( REU), which is equipped according to the specific requirements of the NAV station. It
serves as a communication interface between the connected equipment and the public switched netĆ
work, and as a common point for connecting a service terminal (Laptop PC) for commissioning and
maintenance purposes.
NOTE: In NAV 400 en-route navigation systems (e.g. VOR 431) no separate NAV-LCU device
has to be used as local communication interface. The LCU functionality is integrated in
the NAV 400 subrack, i.e. the LCU software is running on the already existing LCSU/CSB
board, additional modems are used for communication purposes.
The NAV-LCU 443 is a link control unit and provides central points for communication between
RMC's and the navaids systems. The NAV-LCU 443 has direct RS-232/422 interfaces to the
(D)VOR, TACAN/DME and ELTA-equipment. For small projects, it is possible to connect the NAV-
LCU of en-route navigation systems via switched lines to an RCMS.
RMC-R RMC-C
PTT
LCSU/CSB
VOR 431
NAV-LCU 443
TAC ELTA
VOR
4000 TAC ELTA
Fig. 1-1 Hierarchy of remote control subsystems for enroute navigation systems, example
Ed. 01.02 AN-1

RCSE 443 RMMC
General Description Annex NAV-LCU Description and Operation
1.3 MECHANICAL DESIGN
The NAV-LCU 443 consists of an REU in a special configuration without an INC panel. The back
panel is similar to the RCSE 443 back panel.
The NAV-LCU configuration of the REU comprises the following subassemblies:

- Processor Board PDX 80C486
- EPROM/RAM Disk (MFM)
- Serial Interface Board (SIB) for PDX processor boards (code number 84045 83105)
- Auto-Dial Modem LGM 28.8D1 at LGM4
- DC/DC-Converter Puls APD 346.112F
The SIB, Modem LGM 28.8 and the DC/DC-Converter are also used in the REU configuration of the
RCSE 443, i.e. these subassemblies are described in the Technical Manual RCSE 443.
The subassemblies Processor Board PDX 80C486 and the MFM are special for the NAV-LCU 443
configuration and therefore described in detail within the following sections of this Annex.
APD346
LED green
PC2
Vout 1
Processor Board PDX 486
EPROM/RAM Disk
PC1
Spare
Spare
Spare
Spare
Spare
Spare
Spare
Spare
Spare
Spare
LGM4
SIB
5 V/12 A ±12 V...15 V/2 A
Fig. 1-2 REU configuration of NAV-LCU 443, front panel
AN-2 Ed. 01.02

RMMC RCSE 443
Description and Operation Annex Nav-LCU General Description
1.4 TECHNICAL DATA
The PC-unit consists of up to 7 Eurocards running on the MCE-bus-backplane (PC/AT-compatĆ

ible bus).
- Processor board PDX 80C486 with:
· 4 MB (max. 16 MB) system RAM
· 128 Kbyte EPROM (AWARD-BIOS)
· watchdog
· real time clock
- EPROM/RAM disk (MFM) with:
· 512 kB (max. 2 MB) EPROM/flash holding the DOS 5.x and the application program
· additional 128 Kbyte (max. 2 MB) static RAM to hold the adaptable configuration file,
the static RAM is battery-backed
1.5 SHORT DESCRIPTION

1.5.1 General Overview NAV-LCU 443
Fig. 1-3 shows the structure of a typical remote control system for enroute navigation systems using
the NAV-LCU 443.
36 .. 72 VDC
J18/19
REU 5V
Processor Board
DC/DC EPROM/RAM
Converter +12 V 80C486DX DISK
-12 V
PC Backpanel
Modem Backpanel
PC1 Serial
PC2 Interface Board
SIB modem bus
LED SIB
SW1
Dial modem
NAV-LCU
LGM28.8
Connector Backpanel with Protectors
1a2 2a2 1sA 1sB LGM1 LGM2 LGM3 LGM4 ZUA NFK-1 NFK-2 2sA/ 2a1/ 1+2a3/ 1a1/ 1a3 2a3 IN/OUT
422 CTU 422 RSU
PSTN
PC2 (analog
PC1 diagnosis or S0)
P(D)VOR
4000
PTT Network
Printer
Fig. 1-3 NAV-LCU 443, block diagram, example
Ed. 01.02 AN-3

RCSE 443 RMMC
General Description Annex NAV-LCU Description and Operation
AN-4 Ed. 01.02

RMMC RCSE 443
Description and Operation Annex NAV-LCU Installation
CHAPTER 2
INSTALLATION AND INITIAL SETUP
2.1 GENERAL
The installation and initial setup for a remote control system with a (D)VOR 4000 station connected
to a NAV-LCU 443 is described in chapter 2 of the Technical Manual RCSE 443. The special configuĆ
ration of the NAV-LCU described within this supplement has to be considered.
2.2 INSTALLATION
No special installation instructions concerning NAV-LCU 443 have to be added.
2.3 INITIAL HARDWARE SETTINGS

2.3.1 Hardware Settings on NAV-LCU Subassemblies
2.3.1.1 Processor Board PDX 80C486 Settings
x2
J1
x5
1 4 1 2 3
T1
x13
x14
3 21
J3
J2
J4
Battery
+
J10
J11 J12
J9
J8
x15 x16
1 2 3
x17
J7
1 2 3 1 2 3 4
set open open set

1 2 3
Fig. 2-1 PDX 80C486, position of jumpers and default settings
J1-1 J1-2 J1-3 CPU-CLK SELECTION

open set open 33.3 MHz
set set open 25 MHz
open open set 20 MHz
Ed. 01.02 AN-5

RCSE 443 RMMC
Installation Annex NAV-LCU Description and Operation
J2 1-2 (A) 5 V CPU
2-3 (B) 3.3 V CPU
J3 set Color/VGA adapter
open Monochrome adapter
J4 set ISA bus with Power Good of Watchdog
open ISA bus without Power Good
J7 1-2 (A) Normal operation mode of ACCU (VBAT internal)
2-3 (B) 'Parking' mode of ACCU (for delivery or storage)
J8 open BIOS flash disabled (boot via external BIOS)
set normal operation mode (BIOS flash enabled)
J9 open flash disk disabled
set normal operation mode (flash disk enabled)
J10 open keyboard input port (Port 12) = 1
set keyboard input port (Port 12) = 0
J11.1 set CPU-CLK*3 (DX4 Mode)
J11.2 set CPU-CLK*2.5 (only INTEL DX4)
J11.3 set CPU-CLK*2 (DX2 Mode), not used for NAV-LCU
J12.1 set Watchdog timeout NMI allowed
J12.2 set CPU air cooler fail NMI allowed
J12.3 open excess temperature NMI allowed
J12.4 set excess temperature reset allowed
2.3.1.2 EPROM/RAM Disk (MFM) Settings
BANK A
IC18 J3
IC15 IC16 IC17
EPROM
D7
D6
D5
D4
D3
D2
D1
D0
J18
1'
J10
J16 J12 J6 1 2 3 J14
LOGICAL 0
LOGICAL 1
1 2 3
1 1' 1' 1 1 1' 1 1' 1
1 1' 1' 1 1' 1 1 1 1'
J17 J8 J13 J7 J9 J15 1 J1

A8
J11 A7
A6
1' A5
J19 1' A4
RAM J4 A3
A2
A1
1
BATTERY
J5
+ - 1
1'
BANK B
set open set EPROM: 512 kB
open RAM: 128 kB
1 2 3
Fig. 2-2 EPROM/RAM disk, position of jumpers and default settings
AN-6 Ed. 01.02

RMMC RCSE 443
Description and Operation Annex NAV-LCU Installation
J1 Adjusting base address (2A8)
J3 Status port allocation (0+2+3 set: BANK A 2Mbyte, BANK B 520 Kbyte)
0...3 Coding memory
4 Memory type select BANK A

set Static RAM
open EPROM/Flash
5 Memory type select BANK B

set Static RAM
open EPROM/Flash
6 Boot flag
set Boot from MFM
open No boot from MFM
J4 1 Normal operating position, data backup for CMOS-RAM is activated.

1' Decoupled park position, battery is disconnected.
J5 1 Power fail recognition PWR GOOD

1' Power fail recognition RESET
J6...19 Adjustment of memory type
Ed. 01.02 AN-7

RCSE 443 RMMC
Installation Annex NAV-LCU Description and Operation
AN-8 Ed. 01.02

RMMC RCSE 443
Description and Operation Annex NAV-LCU Operation
CHAPTER 3
OPERATION
The NAV-LCU 443 consists of an REU in a special configuration without an INC panel (see section
1.3 of this annex). The back panel is similar to the RCSE 443 back panel. Therefore no special informaĆ
tion to the operation of the NAV-LCU is necessary. For operation instructions see Technical Manual
RCSE 443, chapter 3.
Ed. 01.02 AN-9

RCSE 443 RMMC
Operation Annex NAV-LCU Description and Operation
AN-10 Ed. 01.02

RMMC RCSE 443
Description and Operation Annex NAV-LCU Detailed Description
CHAPTER 4
DETAILED DESCRIPTION
4.1 GENERAL
The NAV-LCU configuration of the REU comprises the following subassemblies:
- Processor Board PDX 80C486

- EPROM/RAM Disk (MFM)
- Serial Interface Board (SIB)
- Auto-Dial Modem LGM 28.8D1 at LGM4
- DC/DC-Converter Puls APD 346.112F
The SIB, Modem LGM 28.8 and the DC/DC-Converter are also used in the REU configuration of the
RCSE 443, i.e. these subassemblies are described in the Technical Manual RCSE 443.
The subassemblies Processor Board PDX 80C486 and the MFM are special for the NAV-LCU 443
configuration and therefore described in detail within the following sections of this chapter.
4.2 NAV-LCU SUBASSEMBLIES

4.2.1 Processor Board PDX 80C486
The PSX386 processor board may be replaced by the PDX486 processor board (e.g. necessary if
the RCSU possesses an Ethernet (LAN) connection). The PDX 80C486 single-board computer is
built up entirely in high-speed CMOS technology and integrated on a simple Eurocard.
Separate terminals for supply voltages (+5 V and +12 V) and a CPU fan are available. The supply
voltage of +12 V is only required for a CPU fan which can be connected to the voltage source through
the X2 plug connector. A signal which monitors the revolutions of the fan down to a full stop can be
processed through pin 4 of this plug connector.
The processor board accommodates 4/16 MB dynamic read/write memories (DRAM).The memory
is organized in 32-bit words, has one parity bit per byte and begins with the address 00000000H.
A refresh cycle is automatically invoked every 15.6 µs. The BIOS is a Flash EPROM with a capacity
of 128 KB. Address space from E000:0000 to F000:FFFF is reserved for the BIOS. Shadow RAM can
be activated in the setup in 16-byte increments for the range from C000:0000 to F000:FFFF. The conĆ
tents of the BIOS can be copied into the Shadow RAM for more rapid execution of BIOS functions.
The CPU platform is equipped with the Intel 486DX-compatible AMD486DX4 CPU (3.3 V type). The
maximum allowed CPU oscillation at the CPU-CLK pin is 33 MHz. The chip set is fed with the doubled
frequency for oscillation generation. The oscillation for the chip set (40/50/66.6 MHz) can be selected
through the J1 jumper field.
Cold-booting the processor leads to a reset of the CPU and the entire on-board peripherals. It is
initiated:
- when the +5 V supply voltage sinks below a threshold value (a module monitors the system voltage
and ensures a positive Power ON/OFF reset through defined switch-on and switch-off points),
Ed. 01.02 AN-11

RCSE 443 RMMC
Detailed Description Annex NAV-LCU Description and Operation
- by the "watchdog time-out" function, which monitors program execution in the microprocessor
(monitoring of read access, which must be executed at least every 3.2 seconds),
- by the excess temperature watchdog which monitors the CPU housing temperature (the tempera-
ture sensor is set for a maximum housing temperature of +85 _C),
- by pressing the reset button (T1); the reset signal is active as long as the reset button is held, plus
an additional 200 ms after release.
A battery-backed real-time clock (RTC) contains the time, the date, a wake-up time, as well as 128
bytes of CMOS RAM. Data contents are secured for more than 5,000 hours with the rechargeable
Ni-Cd battery, which is located on the mother board. Battery supply voltage can be interrupted
through jumper J7, especially for long down-time periods (storage).
A keyboard controller assumes the controls between the serial interface of the keyboard and the sysĆ
tem. A data transfer between the controller and the keyboard is possible in both directions. The conĆ
troller receives information from the keyboard through the pressing and releasing of keys, and sends
the information to the keyboard for autorepeat and wait periods. Along with this primary function, the
keyboard controller also has an 8-bit output and an 8-bit input port available to it.
4.2.2 EPROM/RAM disk (MFM)
The EPROM/RAM disk (Memory File Module) is a PC XT/AT-compatible "disk drive" with a memory
capacity of up to 4 MB (max. 2 MB EPROM and 2 MB RAM), and has no moving parts. It has been
designed using high-speed CMOS technology. The board, which has a single eurocard format, can
be used either as an EPROM disk or as a CMOS-RAM disk. The data in the RAM disk area is backed
up by a storage battery and is not lost when the system is switched off. The storage battery is activated
via jumper J4, so that the configuration set in the factory remains valid. If the disk is stocked as a spare
part without being programmed, jumper J4 must be "parked", so that the battery is disconnected.
Write protection is provided by the hardware, to prevent data from being overwritten accidentally.
Jumpers are used to match the disk to the appropriate memory type. An additional status port, which
can be programmed using the jumpers, allows the user to read in a data word in order, for example,
to code information about the memory type and the write protection. The status port is allocated via
jumper panel J3 as a freely inserted 8-bit data word. The J3/1 information is read in at D0 and the
J3/2 information at D1, etc. A set jumper means that the corresponding bit has a logical "0", while
an open jumper corresponds to a logical "1". The bits are read in via the status register.
The memory type is set with jumpers J6 to J19. All the memory on the board is subdivided into two
banks with different memory types. The bank A consists of bases IC15*,16*,17,18, while bank B comĆ
prises bases IC19*,20,21,22 (*=tipped). The EPROM/RAM disk requires four addresses in the I/O
address area. The base address is fixed. The base address of the first board is 02A0H.
The EPROM/RAM disk is subdivided into tracks and sectors, in exactly the same way as a normal disk
drive. Each block is 256 bytes long. An auto-incremental byte counter is used to access the individĆ
ual bytes in the blocks. In other words, after each read or write access, the counter points to the next
position which must be read or written. The byte counter is incremented each time the data register
is accessed. The counter is reset to zero by writing to the sector register.
AN-12 Ed. 01.02

RMMC RCSE 443
Description and Operation Annex NAV-LCU Detailed Description
96 pin VG-Connector:
EPROM RAM
Controller (512 KB) (128 KB) Battery
(max. 2 MB) (max. 2 MB) J4
PC-Bus
Buffer
Fig. 4 EPROM/RAM disk (MFM), block diagram
Ed. 01.02 AN-13

RCSE 443 RMMC
Detailed Description Annex NAV-LCU Description and Operation
AN-14 Ed. 01.02

RCSE 443: Remote Control and Status Equipment

Uploaded by

Copyright:

Available Formats

RCSE 443: Remote Control and Status Equipment

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

RCSE 443: Remote Control and Status Equipment

Uploaded by

Copyright:

Available Formats

Reference No.

Remote Control and

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

All rights reserved

The equipment documentation comprises:

Part Technical Manuals Code No.

Volume Drawing Set Code No.

The Technical Manual for the RCSE 443 comprises:

PART CONTENTS REF. No.

This Technical Manual describes the equipment in the following chapters:

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

Annex 01.02 NAV-LCU 443

CHAPTER 1 GENERAL DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.4.1.6.4 Supported Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

1.5.5.1 NAVAIDS/ILS Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32

CHAPTER 2 INSTALLATION AND INITIAL SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Ed. 01.02 III

2.3.3.1 REU, Jumper Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

CHAPTER 3 OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.2.4.2 CTU and RWY-SELECT Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

CHAPTER 4 DETAILED DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.3.10 Multiplexer RS232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

CHAPTER 5 MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Fig. 1-1 Overview RMMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Ed. 01.02 VII

Fig.-No. Title Page

VIII Ed. 01.02

Fig. 4-13 DC/DC-Converter (Puls APD346), block diagram . . . . . . . . . . . . . . . . . . . . . . 4-16

Ed. 01.02 AV-1

AV-2 Ed. 01.02

Ed. 01.02 AV-3

AV-4 Ed. 01.02

Ed. 01.02 AV-5

AV-6 Ed. 01.02

Ed. 01.02 AV-7

AV-8 Ed. 01.02

Ed. 01.02 1-1

- USER-FRIENDLY OPERATOR INTERFACES

- LOW EQUIPMENT COSTS

Fig. 1-1 Overview RMMC

1-2 Ed. 01.02

1.2.2 Components of the System

1.2.2.2 Remote Control and Monitoring System (RCMS)

1.2.2.3 Remote Maintenance Center (RMC)

1.2.2.4 Navaids Local Communication Unit (NAV-LCU)

Ed. 01.02 1-3

1.2.2.5 Remote Maintenance Subsystem (RMS)

1.2.3 Hierarchy of RMMC Remote Control Equipment

RMC-C Remote Maintenance Center

RMC-R RMC-R RMC-R

RMS RCMS 443 ILS

AZ EL DME/P TAC ELTA

Fig. 1-2 Hierarchy of the remote control subsystems

1-4 Ed. 01.02

1.2.4 System Configuration

Type Modem Baudrate Remark