En 07.03 RMMC Config Tool

Reference No.
52828 09870
RMMC Configuration
Remote Maintenance
and Monitoring
Technical Manual
Introduction
Basic Operation
As for details, the electrical and mechanical information given in the

documentation supplied with each equipment prevails
All rights reserved

E 2003
Thales ATM GmbH
Stuttgart
Printed in Germany
RMMC RMMC Config
Configuration Program Preliminary Remarks
PRELIMINARY REMARKS
The Technical Manual for the RMMC Configuration Program comprises:
PART CONTENTS REF. No.

- Introduction, Basic Operation 52828 09870
This Technical Manual describes the equipment in the following chapters:
1 General
2 Description and Use of RMMC Configuration
Annex Additional Features for Service Personnel (optional)
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 RMMC Configuration Program 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. 07.03 A
RMMC Config RMMC
List of valid pages Configuration Program
List of valid pages

Basic edition: 07.99 / Revised edition: 07.03
Pages Ed.-No. Remarks
Title 07.03
A and B 07.03
I to IV 07.03
1-1 to 8 07.03
2-1 to 32 07.03
Annex 07.03 Additional Features for Service Personnel

(optional)
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. 07.03
RMMC RMMC Config
Configuration Program Table of Contents
TABLE OF CONTENTS
Section Title Page
CHAPTER 1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 PC REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.3 PC INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.4 INSTALLATION OF THE CONFIGURATION PROGRAM . . . . . . . . . . . . . . . . . . 1-3
1.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.4.2 Installation of 'RMMC Configuration' on PC . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.5 BRIEF DESCRIPTION OF SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.5.2 Program Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
CHAPTER 2 DESCRIPTION AND USE OF RMMC CONFIGURATION . . . . . . . . . . . . . . . . . 2-1

2.1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2 STARTING RMMC CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2.1 Start to create a new SIT-File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2.2 Start to modify an existing SIT-File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2.3 Start to create a new OIO-File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2.2.4 Start to modify an existing OIO-File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.3 HANDLING OF CONFIGURATION FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.3.1 Saving a SIT-File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.3.2 Closing a SIT-File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.3.3 Saving an OIO-File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.3.4 Closing an OIO-File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.4 LEAVING RMMC CONFIGURATION PROGRAM . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2.5 CONFIGURATION OF SIT-FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
2.5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
2.5.2 File Tab 'System' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
2.5.3 File Tab 'Hardware' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
2.5.4 File Tab 'Stations' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
2.5.5 File Tab 'Forced Shutdown' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
2.5.6 File Tab 'Status Exchange' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Ed. 07.03 I
RMMC Config RMMC
Table of Contents Configuration Program
Section Title Page
2.6 CONFIGURATION OF OIO-FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

2.6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
2.6.2 File Tab 'General' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
2.6.3 File Tab 'OIO-Pins' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
2.6.4 File Tab 'Concurrences' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
2.7 HELP FUNCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
2.7.1 Help Topics for SIT-File Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
2.7.2 Context Help for SIT-File Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
2.7.3 Help Topics for OIO-File Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
2.7.4 Context Help for OIO-File Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
II Ed. 07.03
RMMC RMMC Config
Configuration Program Table of Contents
LIST OF FIGURES
Fig.-No. Title Page
Fig. 1-5 System configuration of 'RMMC Configuration' program via PC (example) . 1-2
Fig. 1-6 Start installation of 'RMMC Configuration' program . . . . . . . . . . . . . . . . . . . . . 1-3
Fig. 1-7 'RMMC Configuration' program within 'Adracs Remote Controlling' . . . . . . 1-4
program group
Fig. 1-8 Structure of 'RMMC Configuration' program, functions in start window . . . . 1-5
Fig. 1-9 Structure of 'RMMC Configuration' program, SIT-file configuration . . . . . . . 1-6
Fig. 1-10 Structure of 'RMMC Configuration' program, OIO file configuration . . . . . . . 1-7
Fig. 2-1 Starting 'RMMC Configuration' program (example) . . . . . . . . . . . . . . . . . . . . . 2-2

Fig. 2-2 Application window 'RMMC Configuration' after start (example: New Site) . 2-2
Fig. 2-3 Dialog box for creation of a new SIT-file (example) . . . . . . . . . . . . . . . . . . . . . 2-3
Fig. 2-4 Application window 'RMMC Configuration' after start (example: Open Site) 2-4
Fig. 2-5 Dialog box to select the SIT-file for modification (example) . . . . . . . . . . . . . . 2-4
Fig. 2-6 Dialog box for modification of a SIT-file, file card 'System' (example) . . . . . 2-5
Fig. 2-7 Dialog box for creation of a new OIO-file (example) . . . . . . . . . . . . . . . . . . . . 2-6
Fig. 2-8 Application window 'RMMC Configuration' after start (example: Open Site) 2-7
Fig. 2-9 Dialog box to select an OIO-file for modification (example) . . . . . . . . . . . . . . 2-7
Fig. 2-10 Dialog box for modification of an OIO- file, file card 'General' (example) . . 2-8
Fig. 2-11 Saving a SIT-file with File menu or push buttons (example) . . . . . . . . . . . . . 2-9
Fig. 2-12 Closing SIT-file with File menu or push buttons (example) . . . . . . . . . . . . . . 2-10
Fig. 2-13 Saving an OIO-file with command 'Save' of File menu (example) . . . . . . . . 2-11
Fig. 2-14 Leaving the 'RMMC Configuration' program (example: SIT-file) . . . . . . . . . . 2-12
Fig. 2-15 Overview of the system configuration example . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Fig. 2-16 Selection of SIT file tab 'System' for hardware type REU . . . . . . . . . . . . . . . . 2-14
(example: RCSU-SITE)
Fig. 2-17 Selection of SIT file tab 'System' for hardware type REU . . . . . . . . . . . . . . . . 2-15
(example: RMC-SITE)
Fig. 2-18 Selection of SIT file tab 'Hardware' (example: RCSU-SITE) . . . . . . . . . . . . . 2-16
Fig. 2-19 Selection of SIT file tab 'Hardware' (example: LCU-SITE) . . . . . . . . . . . . . . . 2-17
Fig. 2-20 Selection of SIT file tab 'Stations', left columns (example: RCSU-SITE) . . . 2-18
Fig. 2-21 Selection of SIT file tab 'Stations', right columns (example: RCSU-SITE) . . 2-19
Fig. 2-22 Selection of SIT file tab 'Forced Shutdown' (example: RCSU-SITE) . . . . . . 2-20
Fig. 2-23 Selection of SIT file tab 'Status Exchange' (example: RCSU-SITE) . . . . . . . 2-22
Fig. 2-24 Selection of SIT file tab 'Status Exchange' (example: RMC-SITE) . . . . . . . . 2-23
Ed. 07.03 III

RMMC Config RMMC
Table of Contents Configuration Program
Fig.-No. Title Page
Fig. 2-25 RCSU-Site of the system configuration example, function of OIO card . . . 2-25
Fig. 2-26 Selection of OIO file tab 'General' of system configuration example . . . . . . 2-26
(RCSU-SITE)
Fig. 2-27 OIO file tab 'General', Assignments of the System Texts . . . . . . . . . . . . . . . . 2-27
Fig. 2-28 Time values defined for OIO inputs and outputs . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Fig. 2-29 Selection of OIO file tab 'OIO-Pins' (example: RCSU-SITE) . . . . . . . . . . . . 2-28
Fig. 2-30 Selection of file tab 'Concurrences', text string definitions . . . . . . . . . . . . . . . 2-29
Fig. 2-31 Selection of file tab 'Concurrences', status output definition . . . . . . . . . . . . . 2-30
Fig. 2-32 Function 'Help Topics' for SIT file configuration (example) . . . . . . . . . . . . . . . 2-31
Fig. 2-33 Function 'Help Topics' for OIO file configuration (example) . . . . . . . . . . . . . . . 2-32
IV Ed. 07.03
RMMC RMMC Config
Configuration Program General
CHAPTER 1
GENERAL
1.1 OVERVIEW
The 'RMMC Configuration' program is a user-friendly interface to support the creation and modificaĆ
tion of a configuration of remote control (RMMC*) systems for navigation systems according to the
respective operational sites and applications. The use of usual PC standards and operating systems
ensures a familiar operating environment for the user. The configuration program is implemented as
an MS-WINDOWS application running on the PC or laptop where ADRACS user program is installed
for remote system control and monitoring.
A file tab control system supports the creation of the configuration data. The various configuration
data sets are stored on different file cards presented in dialog boxes. System parameters, interface
configuration data and equipment/station configuration data can be defined by means of familiar
WINDOWS dialog box elements like edit boxes, list boxes, radio buttons and check boxes. The
'RMMC Configuration' program interprets the configuration data input by the user, checks it for plausiĆ
bility, determines possible dependencies and reacts automatically with modification on data repreĆ
sented in the dialog boxes.
The configuration data is put in via keyboard of the PC/laptop (using the mouse to select tabs and
boxes) by authorized operating personnel of the respective operator (usually air traffic control authoriĆ
ties). Requested by the operator the configuration of the remote control system may be stored within
a file on the PC and has then to be loaded into the RAM of the remote control system (e.g. Remote
Control Electronic Unit, REU) by means of the ADRACS user program. Modification of an already exĆ
isting configuration file requires loading the file from the RAM of the remote control system to the PC
file system via ADRACS. After modification of the configuration data the file has to be stored on PC
and loaded back to the RAM of the remote control system.
Via a printer connected to the PC/laptop configuration data can be printed out and thus documented.
Protection against unauthorized access is given by a HW key (dongle) fit to actual configuration apĆ
plication.
* RMMC: The Remote Maintenance and Monitoring Configuration represents a system for remote monitoring, control, and
maintenance of all navigation systems connected. The remote control instruments allow all the networked navigation sysĆ
tems 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 measured value.
1.2 PC REQUIREMENTS
The 'RMMC Configuration' program must be installed on a PC/laptop system (normally the configuraĆ
tion program is installed on the same PC than used for ADRACS user program). The PC system must
meet the following requirements:
- Processor Pentium 90 or better (IBM PC/AT compatible)
- 32 MB RAM, VGA adapter, CD-ROM drive
- min. 10 MB free disk space on HDD
- VGA color monitor (min. resolution 800 x 600 pixels)
- Control via mouse or comparable
- one serial interface connector (RS232)
- any 32-Bit version of Microsoft Windows operating system
Trademarks:
Microsoftand MS-DOS are registered trademarks, WINDOWS is a trademark of the Microsoft Corporation. Pentium is a registered trademark
of the INTEL Corporation. IBM is a registered trademark of the International Business Corporation.
Ed. 07.03 1-1

RMMC Config RMMC
General Configuration Program
1.3 PC INSTALLATION
NOTE: Connection and control of the PC and the operating system software are to be carried out
in compliance with the manufacturer documentation. It is assumed that the user is familiar
with the basics of PC hardware and CD ROM handling, and the operating system. The
respective handling instructions in the manufacturer documentation must be observed.
The 'RMMC Configuration' program can be operated on a PC connected to a remote control system
(RCSE 443, RCSU 443, RCSI 446, NAV-LCU, CTU) or on a PC directly connected to a computing
system of a station (LCSU/CSB or LCP). The connection of the PC is established via a zero modem
cable. Normally the configuration program is installed on the same PC than ADRACS user program.
NOTE: Two types of front panels, LCP and LCSU/CSB, are used for Navaids 400 systems. The
LCP is the new version with LCD screen to display parameters and commands. Further
on the two types of front panels with the corresponding communication functions are
named as LRCI (Local/Remote Communication Interface).
A hardware key (actuator, a so-called 'dongle') is used to get access rights to a certain configuration
program application. Usage of the dongle prevents unauthorized personnel from creating or modifyĆ
ing configuration data in a wrong or faulty way. Reading of the configuration data is always possible
without dongle usage. Before starting the configuration program the dongle has to be connected to
the printer interface of the PC (see Fig. 1-1). If a printer is used too, the printer is connected to the
dongle. Each dongle contains a special key code, which defines an identification and access code
for the operator. This code is filed in each site file (*.SIT, *.OIO) as a kind of finger-print" to identify
the creator unambiguously. The dongle can only be purchased from Thales ATM GmbH.
NOTE: The dongle has to be used only during operation of 'RMMC Configuration' program. It
is recommended to define a responsible person, who is allowed to use the dongle excluĆ
sively. After leaving the configuration program the dongle has to be disconnected from
the PC/laptop and put away safely.
a) connection to a station b) connection to a remote control system
Mouse Keyboard Printer Printer Mouse Keyboard

Centronics Centronics
z.B. LPT1
z.B. LPT1
PC or Laptop PC or Laptop
e.g. COM1 e.g. COM1
RS 232 Dongle RS 232
Zero modem cable Zero modem cable
RS 232 1a2/PC1
LRCI
Navaids 400 RCSE 443
Subsystem
(e.g. DVOR) Switched line Dedicated line
PTT 6
2
LGM1, top LGM, top
Modem (LGM) Modem (LGM)
NOTE:Connectionsshown are examples valid for Subsystem Subsystem
Navaids 400 systems. (e.g. DVOR) (e.g. ILS)
Fig. 1-1 System configuration of 'RMMC Configuration' program via PC (example)
1-2 Ed. 07.03

RMMC RMMC Config
1.4 INSTALLATION OF THE CONFIGURATION PROGRAM
1.4.1 General
The 'RMMC Configuration' program is a Windows-based product and requires Windows to be

installed first (for version see section 1.2). Basis for the description of the configuration program within
this technical manual is the English version of Windows. The configuration program software and the
driver software for the dongle (Sentinel System Drivers) are supplied on a CD ROM.
1.4.2 Installation of 'RMMC Configuration' on PC
The configuration program software is supplied on a CD-ROM. To start installation of 'RMMC ConfigĆ
uration' on the PC the following actions have to be performed:
- Run WINDOWS. Insert CD ROM with software of 'RMMC Configuration' program into the CD drive
(typically d:).
- Connect dongle to the PC printer interface (e.g. LPT1, see Fig. 1-1).
- Click 'Start' button, select Run... (see fig. 1-2), type d:\Setup in the Command Line field of the
Run dialog box, click 'OK' button.
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
PC Info
Windows NT Workstation
Programs
Documents
Microsoft
Settings
Find
Help
Run...
Shut Down
Fig. 1-2
Start
Start installation of 'RMMC Configuration' program
NOTE: The following instructions are based on the assumption that the ADRACS program group
'Adracs Remote Controlling' containing the program 'Adracs Remote Controlling SoftĆ
ware' is already installed on PC. After the following instruction steps the 'RMMC ConfiguĆ
ration' program will also be member of the 'Adracs Remote Controlling' program group.
Follow the instructions on the screen. The 'RMMC Configuration' program will be created within
the existing ADRACS program group 'Adracs Remote Controlling'.
- After installation of the 'RMMC-Configuration' program the driver software of the dongle has to
be installed, additionally. The driver software is also supplied on the CD ROM.
Click 'Start' button, select Run... (see fig. 1-2), type d:\Setup-Dongle in the Command Line field
of the Run dialog box, click 'OK' button.
NOTE: If the dongle has not been connected to the printer interface of the PC the following error
message will appear:
Actuatornot found [SproFindFirstKritUnit]. Check actuator or printer interface. Write Config file not possible!"
NOTE: The correct installation of the driver software is performed without any information on the
screen.
Ed. 07.03 1-3

RMMC Config RMMC
- After installation of the driver software the PC has to be restarted (reset).
- The configuration program is now ready for starting. Fig. 1-3 shows the program group 'Adracs
Remote Controlling' containing the program 'RMMC Configuration'.
PC Info
Accessories
Programs
Programme Command Prompt
Simulation
Windows NT Explorer
Documents Tools
Settings Adracs
Programme
Remote Controlling Adracs Remote Controlling Software
Find Autostart Konfig RMMC Configuration
Microsoft Office
Help Web Helpers
Run...
Shut Down
Start
Fig. 1-3 'RMMC Configuration' program within 'Adracs Remote Controlling' program group
NOTE: To make the access to the program 'RMMC Config' easier for the user it is possible to
generate an icon which is available on Windows desktop. This is done by using the menu
(via right mouse click on free space of desktop) New... -> Shortcut (window 'Create
Shortcut' appears) and entering the right path via Browse... function. The user is able to
choose a name for the new icon. Starting of 'RMMC Config' program is then possible via
double clicking on that icon.
1-4 Ed. 07.03

RMMC RMMC Config
1.5 BRIEF DESCRIPTION OF SW
1.5.1 General
The 'RMMC Configuration' program puts a file tab control system at operator's disposal to provide
an easy, clear tool for creation and modification of a configuration file for a remote control (RMMC)
system of navigation systems. The software generates and manages the presentation of the dialog
boxes (screen control by means of graphical masks), handles the dependences upon configuration
data and controls the mouse-driven operator communication system.
The operator is guided and advised by the PC software (e.g. by means of list boxes). The configuraĆ
tion program interprets the configuration data which is entered by the operator, checks it for plausibilĆ
ity, determines possible dependencies and reacts automatically with modification on data repreĆ
sented in the dialog boxes. Requested by the operator the configuration of the remote control system
may be stored within a file on the PC and has then to be loaded into the computing unit of the remote
control system (REU or LRCI) by means of the ADRACS user program. Modification of an already
existing configuration file requires loading the file from the computing unit of the remote control sysĆ
tem (or from the station) to the PC file system via ADRACS. After modification of the configuration data
the file has to be stored on PC and loaded back to the computing unit of the remote control system
or station.
The 'RMMC Configuration' program is running on a PC connected to a remote control system (e.g.
RMC 443, RCSE 443, RCSU 443, RCSI 446, NAV-LCU, CTU) or directly connected to the computing
unit LCRI of the station.
1.5.2 Program Structure

The 'RMMC Configuration' program is started after selecting the program 'RMMC Config' within the
program group 'Adracs Remote Controlling' (see Fig. 1-3) or via double clicking on created icon.
The application window 'RMMC Configuration' appears, which provides a menu bar containing the
menus File, Options and Help (see Fig. 1-4). The menu File contains functions to create a new configĆ
uration file ('New Site'), to open/modify an existing file ('Open Site') and to leave the configuration
program ('Exit'). After selecting the command AboutConfig of menu Help an information window apĆ
pears containing the version number of the actual installed 'RMMC Configuration' program.
Konfig
RMMC Configuration
Menu: Command: Edit box:

Options Font Font
Start window
RMMC Configuration Command: Edit box:
Help Topics Help to Configuration Tool
Menu:
Dialog box: - Help Command: Edit box:
1 Menu: File About Config About RMMC Configuration Tool
Exit SIT file OIO file

configuration configuration
(see Fig. 1-5) (see Fig. 1-6)
Fig. 1-4 Structure of 'RMMC Configuration' program, functions in start window
Ed. 07.03 1-5

RMMC Config RMMC
After selection of the command 'New Site' and the hardware type a dialog box appears presenting
the appropriate standard configuration SIT-file with cards providing configuration data sets for the
selected hardware type (see Fig. 1-5). Some edit boxes and radio buttons are predefined by default
entries, which can be modified by the operator. Other boxes are empty, the operator is able to select
an entry out of list boxes or input text via keyboard.
Konfig
RMMC Configuration
SIT-file
configuration
New Site Open Site
2 Selection of Hardware type: Selection of config file:

3
Directory = PNBxxxxx\<HW type> Directory = Project
Config file = <HW type>.sit Config file = <site>.sit
Application window Application window

RMMC Configuration RMMC Configuration
Dialogbox: Dialog box:
Config of <HW type>\<HW type>.sit Config of project\<site>.sit
Menu: File
Push buttons:
Exit New Open Save Save as Close Edit Info Print Print to file SAVE Only with
Dongle
CANCEL 1
Only with Dongle Fig.1-4 Fig.1-4
2 3 1
Selection of file tab:
System Hardware Stations Forced Status

Shutdown Exchange
Project SIB Outputs/ Station Type Dual Face RPU

COM Ports Interlock Position
Order No. Address
Devices Runway 1 Runway
Project Path SIB Output - Master Status
Baudrate - Slave Indication
- Delay
Location Collocation optional
NFK
Project-Id RPU-Panel Runway 2
Options - Master
- Slave
Runway 1/2 Runway No. - Delay
REU id RWY Switch optional

(available for certain
Config Text Com Error hardware types)
Count
HW Type
Time values
Fig. 1-5 Structure of 'RMMC Configuration' program, SIT-file configuration
1-6 Ed. 07.03

RMMC RMMC Config
Selecting command 'Open Site' instead of 'New Site' will open a dialog window for selection of alĆ
ready existing configuration files (SIT- or OIO-file). These files contain configuration data sets for
certain remote control systems identified by the file name (directory path defines the project, file name
<SITE>.SIT or <SITE>.OIO defines the site). The edit and list boxes, radio buttons and check boxes
contain entries, which may be defined or modified by the operator. The creation of a new OIO-file
can also be done by using the command 'Open Site'. Then the selection of the station type is required
in the corresponding directory (see Fig. 1-6).
Konfig
RMMC Configuration
OIO-file
configuration
Open Site
creation of a new OIO-file modification of an existing OIO-file
Selection of station type: Selection of config file:

Directory = PNBxxxxx\OIO_STD\<stationtype> Directory = <project>
Config file = *.oio Config file = <site>.oio
Application window Application window

RMMC Configuration RMMC Configuration
Dialogbox: Dialogbox:
C:\CONFIG\PNBxxxxx\OIO_STD\<station type>\*.oio C:\CONFIG\<project>\<site>.oio
Menu: File Selection of file tab:
Exit Save Save as Close

General* OIO-Pins* Concurrences*
Version Number OIO-Card 1 Station 1

Only with Dongle OIO-Card 2 Station 2
1 Nb. of OIO Cards OIO-Card 3
(1..4) OIO-Card 4 ... Station n
Fig.1-4
Description Nb. of OIO Pin Function
System Texts xToy_z_Time (Result)
Timer Assignments Input/Output First Operand
Special Functions Static (Second Operand)
Assignments of Start Value

System Texts
Switch Control
Codes
Initial Concurrences
Assignments of
Meanings
Stations (1..n) * available functions depending on type of dongle
Fig. 1-6 Structure of 'RMMC Configuration' program, OIO file configuration
Ed. 07.03 1-7

RMMC Config RMMC
After generation of new data sets or modification of existing data sets the operator has the possibility
to store the configuration data within a configuration file. Selecting the command Save of the menu
File stores the data within the file under the name given in the header of the dialog box. Saving the
file under a new name is done with the command Save as of menu File. After selecting the commands
Close (to close the dialog box) or Exit (to leave the configuration program) without saving modified
data a dialog box Confirm appears to give the option to the operator to save the modified data before
closing the configuration file and the dialog box or leaving the program.
Alternatively to the commands within the menu File each dialog box of SIT file configuration provides
push buttons in the lower part of the box to have a fast access to the saving data function (button
SAVE) and to the function to close the dialog box (and the configuration file) without saving (button
CANCEL).
1-8 Ed. 07.03

RMMC RMMC Config
Configuration Program Description and Use
CHAPTER 2
DESCRIPTION AND USE OF RMMC CONFIGURATION
2.1 GENERAL
The 'RMMC Configuration' program is running on a PC/laptop either connected to a remote control
system (REU) or to a local station (LRCI). The remote control system includes a RAM storing the correĆ
sponding 'site' configuration data (*.sit, *.ptt, *.oio, *.lke). The files have been loaded from PC/laptop
to the RAM of the remote control unit via ADRACS (command Copy PC File to RAM).
To modify an already existing configuration file, the file must be copied from RAM of remote control
unit to the PC file system via ADRACS command Copy SITE File to PC.
A new created configuration file has to be saved first on PC and then to be loaded into the RAM of
the computing unit, i.e. into REU or LRCI of the appropriate site (remote control system or station)
via ADRACS command Copy PC File to RAM.
NOTE: The access rights to certain functions of the 'RMMC Configuration' program are defined
by the type of 'dongle' the operator is using (details to the 'dongle' see section 1.3). The
restrictive access to features of the configuration tool has its reason in the very large numĆ
ber of possible configurations. The program doesn't always check logical coherences
between different configuration data. Some changes may have side effects to other parts
of the configuration. The service personnel of Thales ATM is competent to perform 'bigĆ
ger' modifications of configuration files. The optional annex 'Additional Features for SerĆ
vice Personnel' contains information about the additional features.
CAUTION
After creation and modification of SIT- and OIO-files the operator has to check very conĆ
scientiously the definitions and changes within the file, otherwise it may be possible that
the whole remote control system is locked after loading the new files. Thales ATM does
not give any guarantee or support for changed files!
2.2 STARTING RMMC CONFIGURATION
NOTE: The following instructions and figures describing the start of the software are based on
the PC operating system Windows (for version see section 1.2). For details to the operatĆ
ing system see the corresponding technical manuals.
NOTE: The following instructions are based on the assumption that the 'RMMC Configuration'
program is defined within the ADRACS program group Adracs Remote Controlling. The
installation is defined in section 1.4.2.
- Run Windows operating system.

- Click 'Start' button, select Programs, select program group Adracs Remote Controlling, select proĆ
gram RMMC Configuration (see fig. 2-1).
Ed. 07.03 2-1

RMMC Config RMMC
Description and Use Configuration Program
PC Info
Accessories
Programs
Programme Command Prompt
Simulation
Windows NT Explorer
Documents Tools
Settings Adracs
Programme
Remote Controlling Adracs Remote Controlling Software
Autostart RMMC Configuration
Find
Konfig
Microsoft Office
Help
Web Helpers
Run...
Shut Down
Start
Fig. 2-1 Starting 'RMMC Configuration' program (example)
- The application window RMMC Configuration appears (see fig. 2-2).
NOTE: If the PC has not been reset after installation of the dongle driver software (see section
1.4.2) the following error message will appear within an information box:
Systemdriver not installed [SproInitialize]. Is the correct driver loaded? Check driver. Write Config file not posĆ
sible!"
If the dongle has not been connected to the printer interface of the PC the following error
message will appear:
Actuatornot found [SproFindFirstKritUnit]. Check actuator or printer interface. Write Config file not possible!
RMMC Configuration
Konfig
File Help Options
New Site CSB
Open Site .. ILS-LKE
NAV-LKE
Exit PC/CTU
RCSI
REU
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ REMICS_LKE
Start Konfig RMMC Configuration
Fig. 2-2 Application window 'RMMC Configuration' after start (example: New Site)
- The menu bar of the application window includes the menu File providing commands to create
a new configuration file (command New Site, see fig. 2-2), to modify an already existing file stored
on the PC (command Open Site, see fig. 2-4) or to leave the config program (command Exit).
2-2 Ed. 07.03

RMMC RMMC Config
2.2.1 Start to create a new SIT-File
- Select command New Site of menu File within application window RMMC Configuration.
- Select hardware type of remote control interface in the pulldown menu (e.g. REU).
- Select standard configuration file <HW type>.sit within dialog box Open and click OK to confirm
(e.g. for hardware type REU the standard file is RCSU_STD.SIT).
NOTE: The standard files (*_STD.SIT) which are part of the config tool can be modified by the
operator.
- The dialog box Config of <HW type>.SIT appears in the application window (see fig. 2-3).
- The file tab 'System' is selected and the corresponding file card is presented in the foreground
ready to fill in. The operator has to change the 'DEFAULT' project setting to the actual Project (i.e.
Project Path) and to define the System Configuration data. For detailed information to fill out the
file card 'System' see section 2.5.2.
- To store the new data within the configuration file (named in the header line of the dialog box
C:\CONFIG\<Project>\<Location>.SIT) click on push button SAVE.
- Selection of another file tab (e.g. 'Hardware') is possible by clicking on the file tab with the right
mouse button. The other card appears in the foreground (details in section 2.5).
- Generally all modifications and new entries can be saved by clicking on SAVE push button, closing
the configuration file (and the dialog box) without saving is performed by clicking on CANCEL
push button (see section 2.3).
Konfig RMMC Configuration
File Help Options
Konfig Config of C:\CONFIG\DEFAULT\RCSU_STD.SIT
Forced Shutdown Status Exchange
System Hardware Stations
Project Data
Project: DEFAULT
Order Number:
Project Path: C:\CONFIG\DEFAULT
System Configuration
Location: XXX-YYY Project Id: 0
Runway1: RWY_YYY
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ X Update Statnames
Runway2:
REU Id: 1 (1 .. 4095)
Config Text: RCSU-443: Location (XXX-YYY)
Hardware: REU
ID=1 10.02.99NS
SAVE CANCEL
Fig. 2-3 Dialog box for creation of a new SIT-file (example)
Ed. 07.03 2-3

RMMC Config RMMC
2.2.2 Start to modify an existing SIT-File

- Select Open Site of menu File within application window RMMC Configuration (see fig. 2-4).
File Help Options
New Site
Open Site ..
Exit
Fig. 2-4 Application window 'RMMC Configuration' after start (example: Open Site)
- The dialog box Open appears in the application window (see fig. 2-5).
- The configuration files of the appropriate site appear (project is assigned to the directory, in examĆ
ple of fig. 2-5 the project is named Example, the locations/sites are the file names, in example of
fig. 2-5 CSB-VOR.SIT, LCU-SITE.SIT, RCSUSITE.SIT, RMC-SITE.SIT).
RMMC Configuration
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
Konfig
File Help Options
Open
?
File name: Folders:
c:C OK
*.SIT, *.OIO c:\configs\example
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ y c:\ y
Cancel
CSB-VOR.SIT
LCU-SITE.SIT CONFIG Network
RCSUSITE.SIT Example
RCSUSITE.OIO SITBACK
Read only
RMC-SITE.SIT y
y
List files of type: Drives:
y y
SITE files [*.SIT, *.OIO] c:NT_SYS
Start Konfig RMMC Configuration Open
Fig. 2-5 Dialog box to select the SIT-file for modification (example)
NOTE: The project Example with the sites CSB-VOR, LCU, RCSU and RMC is defined as system
configuration example which serves as a basis for the explanation of the operation of the
configuration program within this document. An overview of the system configuration exĆ
ample is given in section 2.5.1.
- Select one of the configuration files (e.g. RCSUSITE.SIT) and click OK to confirm.
2-4 Ed. 07.03

RMMC RMMC Config
- The dialog box Config of <SITE>.SIT appears in the application window (Fig. 2-6).
- The file card 'System' of the configuration file <SITE>.SIT is presented in the foreground und can
be modified by the user. Selection of the edit boxes (e.g. Location) is done by clicking on the box
with right mouse button (cursor appears within the edit box). The text within the box can be modiĆ
fied or deleted. For detailed information to set the data within file card 'System' see section 2.5.2.
- Clicking on another file tab (e.g. 'Hardware') presents the new selected file card in the foreground.
More descriptions and operation instructions are given in section 2.5.
- Modifications and new entries can be saved by clicking on SAVE push button, closing the file (and
the dialog box Config of <SITE>.SIT) without saving is performed by clicking on CANCEL push
button (see section 2.3).
RMMC Configuration
Konfig
File Help Options
Config of C:\CONFIG\EXAMPLE\RCSUSITE.SIT
Konfig
Status Exchange
Forced Shutdown
Project Data
Project: EXAMPLE
Order Number:
Project Path: C:\CONFIG\EXAMPLE\
Location:
Runway 1:
RCSUSITE
RWY-34L
Project Id: 0
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ X Update Statnames
Runway 2:
REU Id: 200 (1 .. 4095)
Config Text: EXAMPLE: Location (RCSUSITE)
Hardware: REU
ID=200 19.05.99NN
SAVE CANCEL
Fig. 2-6 Dialog box for modification of a SIT-file, file card 'System' (example)
Ed. 07.03 2-5

RMMC Config RMMC
2.2.3 Start to create a new OIO-File

NOTE: The configuration program includes standard OIO files stored within directory C:\CONĆ
FIG\OIO_STD with subdirectories containing a standard OIO file for a certain type of staĆ
tion (e.g. Marker 3100) connectable to the OIO card of the remote control unit. The type
of station is described within the README.TXT file of this subdirectory.
- Select command Open Site of menu File within application window RMMC Configuration.
- The dialog box Open appears in the application window.
- Change to directory C:\CONFIG\OIO_STD\. Select the subdirectory of the corresponding station
type (e.g. M-3100 for station type Marker 3100).
- Select OIO configuration file *.oio within dialog box Open and click OK to confirm (e.g. for station
type Marker 3100 the OIO file is sel_3100.oio).
- The dialog box C:\CONFIG\PNBXXXXX\<station type>\*.OIO appears (see fig. 2-7).
File Help Options
C:\CONFIG\PNBXXXXX\OIO_STD\M-3100\SEL_3100.OIO
Konfig
General OIO-Pins Concurrences
Version Number: 001.04 Number of OIO Cards
0 1 2 3 4
Description: OIO-Conf of SEL Marker 3100 Marker 02.08.99NS
Selected List
System Texts 255 MAINS OFF
Timer Assignment
Special Functions
Assignments of the System Texts
Switch Control Codes
Assignment of Meanings
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Insert Add Delete
Stations:
Typ: OIO Address: 7
Insert
Delete
Copy Station
Fig. 2-7 Dialog box for creation of a new OIO-file (example)
- The file tab 'General' is selected and the corresponding file card is presented in the foreground
ready to fill in. The operator has to actualize the number of OIO cards and to put a description of
the OIO configuration file into the Description field. For detailed information to modify data on the
file card 'General' see section 2.6.2.
- To store the data within a new OIO file select command Save As of menu File and name the new
file (select the corresponding project/directory and the site/file name). See also section 2.3.3.
- Selection of another file tab (e.g. 'OIO-Pins') is possible by clicking on the file tab with the right
mouse button. The other card appears in the foreground (details in section 2.6).
2-6 Ed. 07.03

RMMC RMMC Config
2.2.4 Start to modify an existing OIO-File
- Select Open Site of menu File within application window RMMC Configuration (see fig. 2-4).
- The dialog box Open appears in the application window (see fig. 2-5).
- The configuration files of the appropriate site appear (project is assigned to the directory, in examĆ
ple of fig. 2-8 the project is named Example, the locations/sites are the file names).
RMMC Configuration
Konfig
File Help Options
New Site
Open Site ..
Exit
Fig. 2-8 Application window 'RMMC Configuration' after start (example: Open Site)
File Help Options
Open ?
File name:
*.SIT, *.OIO
Folders:
c:C
c:\configs\example
OK
Cancel
CSB-VOR.SIT y c:\ y
LCU-SITE.SIT CONFIG Network
RCSUSITE.SIT Example
RCSUSITE.OIO SITBACK
Read only
RMC-SITE.SIT y y
List files of type:
SITE files [*.SIT, *.OIO]
y
Drives:
c:NT_SYS
y
Start Konfig RMMC Configuration Open
Fig. 2-9 Dialog box to select an OIO-file for modification (example)
NOTE: The project Example with the sites CSB-VOR, LCU, RCSU and RMC is defined as system
configuration example which serves as a basis for the explanation of the operation of the
configuration program within this document. An overview of the system configuration exĆ
ample is given in section 2.5.1.
- Select the OIO-file (RCSUSITE.OIO) and click OK to confirm.
Ed. 07.03 2-7

RMMC Config RMMC
- The dialog box C:\CONFIG\<PROJECT>\<SITE>.OIO appears in the application window (see
Fig. 2-10).
- The file card 'General' of the configuration file <SITE>.OIO is presented in the foreground und
can be modified by the user. For detailed information to fill out or modify the file card 'General' see
section 2.6.2.
- Clicking on another file tab (e.g. 'OIO-Pins') presents the new selected file card in the foreground.
More descriptions and operation instructions are given in section 2.6.
- To store the modified data within the OIO configuration file select command Save of menu File.
Closing the file (and closing the dialog box) without saving is performed by selecting command
Close of menu File. See also section 2.3.
File Help Options
C:\CONFIGS\EXAMPLE\RCSUSITE.OIO
Konfig
0 1 2 3 4
Description: OIO Configuration for RCSUSITE Example 06.07.99NS
Selected List
System Texts
Timer Assignment
Special Functions
Stations:
Typ: DME-TAC Address: 128
Insert Add Delete
Typ: SN400 Address: 0
Insert Delete
Copy Station
Fig. 2-10 Dialog box for modification of an OIO- file, file card 'General' (example)
2-8 Ed. 07.03

RMMC RMMC Config
2.3 HANDLING OF CONFIGURATION FILES
After modification of configuration data of one site within the file tab control system the operator can
save the modified file without closing the dialog box (see sections 2.3.1 and 2.3.3) or close the configĆ
uration file and the dialog box without saving the modified data (see section 2.3.2 and 2.3.4).
2.3.1 Saving a SIT-File

See fig. 2-11.
Via command Save of menu File the operator can save the data in the configuration file named in the
header line of the dialog box behind Config of... (in fig. 2-11: C:\CONFIG\EXAMPLE\RC SUSITE.SIT).
The edit box Project of the file card 'System' defines the PC directory where configuration file is stored.
The edit box Location contains the name of the configuration file.
To store the configuration data in a new file (with a new name) the operator has to select the command
Save as of the menu File. The dialog box File save as appears, where the new name of the configuraĆ
tion file can be edited.
Each dialog box presenting a file card of the tab control system provides a push button in the lower
part of the box to have a fast access to the saving data function (button SAVE). Actuating this button
corresponds to the saving function of command Save of menu File.
The dialog box with the tab control system (and also the configuration file) is not closed after the preĆ
viously described saving functions. The operator is able to do further modifications within the configuĆ
ration file. He is also allowed to open an additional configuration SIT- or OIO-file (Open), create a
new file (New), close the already saved file (Close)or leave the program (Exit, see section 2.4).
File Help Options
NewConfig of C:\CONFIG\EXAMPLE\RCSUSITE.SIT
Open..
Close Forced Shutdown
System
Status Exchange
Hardware Stations
Save
Save As..
Project Data
Project: EXAMPLE
Edit Info
Order Number:
Print
Project
Print to filePath: C:\CONFIG\EXAMPLE\
Exit System Configuration
Location: RCSUSITE Project Id: 0
Runway 1: RWY-34L
X Update Statnames
Runway 2:
REU Id: 200 (1 .. 4095)
Hardware: REU
ID=200 19.05.99NN
SAVE CANCEL
Fig. 2-11 Saving a SIT-file with File menu or push buttons (example)
Ed. 07.03 2-9

RMMC Config RMMC
2.3.2 Closing a SIT-File
See fig. 2-12.
The command Close of the menu File closes the dialog box Config of <SITE>.SIT and therefore also
the configuration file <SITE>.SIT and returns to state presenting the empty application window
RMMC Configuration. This is the state after starting the configuration program (see fig. 2-2).
Each dialog box provides a push button in the lower part of the box to have a fast access to the funcĆ
tion to close the dialog box (and the configuration file) without saving (button CANCEL). The function
of this button corresponds to the closing function of command Close of menu File.
Actuating the button CANCEL (or selecting the command Close) means losing all modified data of
all file cards within the open configuration file <SITE>.SIT. The dialog box Config of <SITE>.SIT will
be closed.
After actuating the push button CANCEL or selecting the command Close without saving modified
data a dialog box Confirm appears to give the option to the operator to save the modified data before
closing the configuration file and the dialog box.
File Help Options
Open..
Close Forced Shutdown Status Exchange
Save
Save As..
Project Data
Project: EXAMPLE
Edit Info
Order Number:
Print
Project
Runway 1: RWY-34L
X Update Statnames
Runway 2:
REU Id:
200 (1 .. 4095)
Config Text: EXAMPLE: Location (RCSUSITE) ID=200 19.05.99NN
Hardware: REU
SAVE CANCEL
Fig. 2-12 Closing SIT-file with File menu or push buttons (example)
2-10 Ed. 07.03

RMMC RMMC Config
2.3.3 Saving an OIO-File
See fig. 2-13.
Via command Save of menu File the operator can save the data in the configuration file named in the
header line of the dialog box (in fig. 2-13: C:\CONFIG\EXAMPLE\RC SUSITE.OIO).
To store the configuration data in a new file (with a new name) the operator has to select the command
Save as of the menu File. The dialog box File save as appears, where the new name of the configuraĆ
tion file can be edited.
The dialog box with the tab control system (and also the configuration file) is not closed after the preĆ
viously described saving functions. The operator is able to do further modifications within the configuĆ
ration file. He is also allowed to open (Open) an additional configuration file (SIT- or OIO-file), close
the already saved file (Close) or leave the program (Exit, see section 2.4).
RMMC Configuration
Konfig
File
File Help Options
Open..
Close
Save Number of OIO Cards
Version
Save As.. Number: 001.04
0 1 2 3 4
Exit
Selected List
System Texts
Timer Assignment
Special Functions
Stations: Insert Add Delete
Insert Delete
Copy Station
Fig. 2-13 Saving an OIO-file with command 'Save' of File menu (example)
2.3.4 Closing an OIO-File
The command Close of the menu File closes the dialog box (in fig. 2-13 C:\CONFIG\EXAMĆ
PLE\RCSUSITE.OIO) and also the configuration file <SITE>.OIO and returns to the state presenting
the empty application window RMMC Configuration. This is the state after starting the configuration
program (see fig. 2-2).
Ed. 07.03 2-11

RMMC Config RMMC
2.4 LEAVING RMMC CONFIGURATION PROGRAM
See fig. 2-14.
To leave the 'RMMC Configuration' program select the command Exit of the menu File. The dialog
box<SITE>.SIT (i.e. the configuration file <SITE>.SIT) or <SITE>.OIO and the application window
RMMC Configuration are closed. The program returns to the state, where the configuration program
has to be started again by double click on icon 'RMMC Configuration' of program group Adracs ReĆ
mote Controlling within the Windows desktop (see section 2.2).
After selecting the command Exit without saving modified data a dialog box Confirm appears to give
the option to the operator to save the modified data before closing the configuration file, the dialog
box and the application window and leaving the program.
RMMC Configuration
Konfig
File Help Options
Open..
Close Forced Shutdown Status Exchange
Save
Save As..
Project Data
Project:
Edit Info EXAMPLE
Order Number:
Print
Project
Runway 1: RWY-34L
X Update Statnames
Runway 2:
REU Id: 200 (1 .. 4095)
Config Text: EXAMPLE: Location (RCSUSITE) ID=200 19.05.99NN
Hardware:
REU
SAVE CANCEL
Fig. 2-14 Leaving the 'RMMC Configuration' program (example: SIT-file)
2-12 Ed. 07.03

RMMC RMMC Config
2.5 CONFIGURATION OF SIT-FILES
2.5.1 General
The file tab control system supports the creation of the SIT-files. The various configuration data sets
are stored on different file cards each presented in a certain dialog box. To select one of the dialog
boxes (i.e. one of the file cards) click on the corresponding file tab. The following sections are explainĆ
ing the different dialog boxes which are opened after a file tab selection.
For better understanding a system configuration example is presented first in fig. 2-15. All following
dialog boxes are based on the presented configuration example, i.e. all system parameters, interface
configuration data and equipment/station configuration are defined in the following fig. 2-15.
RMC 443 RMC-SITE ID=1
1 2 3 4 5 6 7 8 RPU-Position
DME_100
VOR_100
SITE_200
ILS_200
Switched
line
PTT
Switched Switched
line line
LCSU/CSB LCU-SITE ID=100 RCSU 443 RCSU-SITE ID=200
VOR_100 / DME_100 ILS_200 SITE_200
1 2 3 4 5 6 7 8 RPU-Position 1 2 3 4 5 6 7 8
VOR_100W
FSD_34L
LLZ_34L
DME-45
GP_34L
DME
VOR
NDB 436
OIO
SN400_VOR 2sB 2sB 1sB 2sB 1sA

FSD-45
Dedicated
SN400_LLZ_2F
lines
SN400_GP_2F
FSD-40
FSD-45
SN400_VOR CSB-VOR ID=201
VOR_100W
Fig. 2-15 Overview of the system configuration example
Ed. 07.03 2-13

RMMC Config RMMC
2.5.2 File Tab 'System'

By means of file card 'System' the project and system configuration data is defined. By clicking on
file tab 'System' the corresponding file card is presented in the foreground within the dialog box ready
for modification (see fig. 2-16).
The file card is divided into different sections. Section Project Data comprises the edit box Project
defining the name of the project the NAV system belongs to. The order number of the project has to
be put into the text field Order Number. The text field Project Path defines the directory where the conĆ
figuration file is stored on PC/laptop (example in fig. 2-16 C:\CONFIG\EXAMPLE\).
After selection of command Edit Info of menu File an edit box will be opened listing a Configuration
History Text which may comprise a few DIN A4 pages. The header section of this text includes informaĆ
tion about the PC operator, the CONFIG path, the project and the order number. Additionally the
names of all modified *.SIT files of the actual project are listed within the history text with the date and
the path where the predecessor file is stored.
If for example the configuration file RCSUSITE.SIT has been modified 10 times, then 9 predecessors
will be filed in the directory ..\SITBACK\ under file names RCSUSITE.000 to RCSUSITE.009. Therefore
the access to the original file and all predecessors is possible at any time. Another file called PROĆ
JECT.LOG is stored in the directory, where configuration program is installed (normally C:\CONFIG).
The file contains all modified *.SIT files with date and project names. This file gives an overview of all
modifications and creations of configuration files. The operator is allowed to put additional remarks
manually into the files.
RMMC Configuration
Konfig
File Help Options
Config of C:\CONFIG\EXAMPLE\RCSUSITE.SIT
Konfig
System
Project Data
Hardware Stations
Project: EXAMPLE
Order Number:
Project Path:
C:\CONFIG\EXAMPLE\
Runway 1: RWY-34L
X Update Statnames
Runway 2:
REU Id:
200 (1 .. 4095)
ID=200 19.05.99NN
Hardware: REU
SAVE CANCEL
Fig. 2-16 Selection of SIT file tab 'System' for hardware type REU (example: RCSU-SITE)
2-14 Ed. 07.03

RMMC RMMC Config
In section System Configuration all configuration data of the system is defined. The edit box LocaĆ
tion defines the site of the system (e.g. town, location within airport). This name is also used as name
of the configuration file (file format *.SIT), which is stored on the project directory of PC after saving
(example in fig. 2-16 C:\CONFIG\EXAMPLE\RCSUSITE.SIT). The edit box Project Id contains norĆ
mally the standard identification 0. The project Id is set to a defined value for specific projects like
NAV-LKE (Id: 1) or ILS-LKE (Id: 2). The name of the runway, e.g. 'RWY-34L', is defined within the
edit box(es) Runway(1/2). This is only used for ILS systems.
If the check box Update Statnames is marked (if runway(s) are defined, see fig. 2-16), the station
names of stations connected to this runway defined on file card 'Stations' (see section 2.5.4) are autoĆ
matically updated using the letters behind RWY-" (in our example 34L), but only on condition that
a -" is on the 4th position of the runway name and on 4th position of the station names (stations
of type 'RMC' or 'RCSU' will not be updated).
The REU ID is the 'house number' of the REU (or LRCI), which accepts an even-numbered value from
1 to 4095. The operator can put any text (max. 80 characters) into the edit box ConfigText. This text
is issued on the diagnosis channel during start of REU (or LRCI). The hardware type of the remote
control interface (stand-alone maintenance device or interface board within rack) has been specified
by selecting the type from the pulldown menu during start of new creation of configuration file (see
section 2.2.1). The type is only shown on the file card and can not be modified.
Actuating the push buttons SAVE and CANCEL will provide a fast access to functions for saving the
configuration file or closing the dialog box (see section 2.3).
RMMC Configuration
Konfig
File Help Options
Konfig Config of C:\CONFIG\EXAMPLE\RMC-SITE.SIT
Forced Shutdown
System
Status Exchange
Hardware Stations
Project Data
Project: EXAMPLE
Order Number:
Project Path: C:\CONFIG\EXAMPLE
Location: RMC-SITE Project Id: 0
Runway 1:
Runway 2:
X Update Statnames
REU Id:
1 (1 .. 4095)
Config Text: EXAMPLE: Location (RMCSITE) ID=1 19.05.99NN
Hardware:
REU
SAVE CANCEL
Fig. 2-17 Selection of SIT file tab 'System' for hardware type REU (example: RMC-SITE)
Ed. 07.03 2-15

RMMC Config RMMC
2.5.3 File Tab 'Hardware'

Serial and parallel interfaces for connection of external and peripheral devices to the remote control
unit are configured on the file card 'Hardware'.
By clicking on file tab 'Hardware' the corresponding file card is presented in the foreground within
the dialog box ready for modification (see fig. 2-18, example RCSU-SITE, hardware type REU).
The left part of the file card in fig. 2-18 defines the communication channels of the interface board
SIB (Serial Interface Board), realized in the hardware of the control unit (REU or LKE) by asynchroĆ
nous and synchronous communication channels (1a1, 1a2, 1a3, 2a1, 2a2, 2a3, 1sB, 2sB). For other
hardware types (LCU) the COM interfaces Com1 ... Com 10 are presented here as communication
channels (see fig. 2-19).
The edit boxes of column Device define the assignment of these internal SIB channels to the external
connections of the control unit (via Connector Backpanel). The selection of the connected external
device type ('RPU/CTU, 'ADRACS', 'Diagnosis', etc.) and the type of the external interface (e.g. 'DiĆ
rect', 'Dial') is done by the operator via group boxes. Selection of the Baudrate (also defined within
group boxes) completes the configuration of the interface.
The check boxes within NFK area define the configuration of the associations between SIB or COM
channels and star distributors NFK1 and NFK2. The SIB channel definition (see Device area on
left-hand side) describes here the association between channel and NFK, i.e. 'NFK1_1a3' means
'SIB channel 1a3 is operated via NFK1'. This is the standard association on REU.
File Help Options
Konfig Config of C:\CONFIG\EXAMPLE\RCSUSITE.SIT
Device Baudrate NFK
y y
1a1 RPU/CTU 9600 NFK1-1a3
ADRACS
y
19200
y NFK2-1a3
1a2
y y NFK1-2a3
1a3 Direct 2400
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ y y NFK2-2a3
RPU/CTU 9600
2a1 NFK2-1sB
y y
Diagnosis 9600
2a2 Options
y y
Direct 2400 OIO
2a3
Direct
y
2400
y Ethernet
1sA
y y TCP/IP-1a3 Dedicate
Direct 2400
1sB TCP/IP-1a3 Dial
y y
Dial 2400
2sA
2sB
Partyline
y
1200
y
SAVE CANCEL
Fig. 2-18 Selection of SIT file tab 'Hardware' (example: RCSU-SITE)
2-16 Ed. 07.03

RMMC RMMC Config
By means of the Options selection the operator can define the optional external interface (OIO, EtherĆ
net, TCP/IP via dedicated or switched line), where additional peripheral devices can be connected.
The boxes Ethernet and TCP/IP may only be selected by service personnel.
Depending on the type of the remote control unit the type of interfaces are different. For RMC, RCSE/
RCSU remote control units the interfaces of the SIB board (1a1, 1a2,... 2sB) are listed within file tab
'Hardware' (see fig. 2-18). For local types (LRCI) the COM ports will be defined on file tab 'Hardware'
(see fig. 2-19).
The left part of the LCU example in fig. 2-19 defines the COM ports, realized in the hardware of the
Local Control Unit (LRCI). The ports COM 1/2 and COM 9/10 are permanently connected to certain
hardware components (TX and MON) and therefore reserved.
File Help Options
Konfig Config of C:\CONFIG\EXAMPLE\LCU-SITE.SIT
Device Baudrate NFK
y y
Com 1 TX-1 19200 NFK1-Com3
TX-2
y
19200
y NFK2-Com3
Com 2
y y NFK1-Com6
Com 3 Direct 2400
y y NFK2-Com6
Com 4 Direct 2400
NFK2-Com8
y y
Direct 2400
Com 5 Options
y y
Dial 2400 X OIO
Com 6
Diagnosis
y
9600
y Ethernet
Com 7
y y TCP/IP-1a3 Dedicate
ADRACS 19200
Com 8 TCP/IP-1a3 Dial
y y
MON-1 19200
Com 9 y y
MON-2 19200
Com 10
SAVE CANCEL
Fig. 2-19 Selection of SIT file tab 'Hardware' (example: LCU-SITE)
Ed. 07.03 2-17

RMMC Config RMMC
2.5.4 File Tab 'Stations'
The external and peripheral devices connected to the external interfaces configured on file card 'HardĆ
ware' are defined on the file card 'Stations'. By clicking on file tab 'Stations' the corresponding file
card is presented in the foreground within the dialog box ready for modification (see fig. 2-20, examĆ
ple RCSU-SITE, hardware type REU).
Each connected station is defined by a serial number (Nb.) and a Name. The input of column Station
Type is selected from a group box (e.g. 'SN400_LLZ_2F', 'FSD_40') which appears after the mouse
click on edit box. The address (Addr.) is awarded by the config program for NAV systems S4000 and
SN400. If more than one RMMC device ('RMC' or RCSU', see fig. 2-20 Nb. 6 and 7) exists, the adĆ
dress is incremented automatically.
The column Output defines the output, where the external station is connected. The corresponding
type of the SIB channel (e.g. '2sB') or the type 'dial' connection are selected from a group box, which
appears after right mouse click on edit box. Collocations between stations are defined in column Col..
In example of fig. 2-20 a collocation exists between stations ILS_200 (Nb. 6) and SITE_200 (Nb. 7).
A control and indication panel (RPU=Remote Panel Unit) on the remote control unit presents the
states of the stations. This indication consists of 16 columns (positions). The assignment of a station
to a position at RPU panel is defined in column Rpu of file card 'Stations'. In fig. 2-20 for example
the state of ELTA_200 is indicated at RPU position 3.
File Help Options
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Stations
System Hardware
Nb. Name Station Type Addr. Output Col. Rpu RWY Follow
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ RWY
1 LLZ_34L SN400_LLZ_2F 1 2sB 0 1 I YES
2 GP_34L
3 FSD_34L
SN400_GP_2F
FSD_40
0
128
2sB
1sB
0
0
2
3
I
I
YES
YES
4 VOR
5 DME
SN400_VOR
FSD_45
2
129
2sB
1sA
0
0
5
6
NO
NO
YES
YES
6 ILS_200 RMC 0 Dial 7 0 NO YES
7 SITE_200 RMC 1 Dial 0 0 NO YES
8 OIO-EXPL USER_DEF_2 0 OIO 0 4 NO YES
9 -1 0 0 NO YES
SAVE DeleteStat CANCEL
Fig. 2-20 Selection of SIT file tab 'Stations', left columns (example: RCSU-SITE)
2-18 Ed. 07.03

RMMC RMMC Config
The column RWY (RunWaY) defines the runway (1 or 2) to which the station belongs. If the correĆ
sponding station follows the state of the 'Runway Selector' (activate runway) at the CTU (Control
Tower Unit), the column Follow RWY has to be set to value YES. If no runway is set (RWY column
is set to NO, then value within column Follow RWY is not valid.
CAUTION
Some additional columns are part of the file card and for information only. They should
only be set or changed by service personnel! Click on to reach these columns. The numĆ
ber of unsuccessful deliveries of telegrams to the station until DATA COM ERROR is set
is defined in column Com Error Count (default value is 5). Further columns inform about
Poll Time [sec], Hist. Time [sec], Hist. Nb. max, Tel. Typ, Resp. Time [ms] and Resp.
Time Special [ms].
configuration file or closing the dialog box (see section 2.3). The push button DeleteStat enables the
user to delete the whole entry (corresponding line of the table) of a station. By clicking on the number
of the station (column Nb.) the station to be deleted can be selected.
File Help Options
System
Hardware Stations
Resp. Resp. Time
Nb. Rpu RWY Follow Com Poll Hist. Hist. Nb. Tel.
RWY Error Time Time max Typ Time Special
Count [sec] [sec] [ms] [ms]
1 1 I YES 5 0 0 0 B 250 2100
2 2 I YES 5 0 0 0 B 250 2100
3 3 I
4 5 NO
YES
YES
5
5
20
10
0
0
0
0
A
B
0
250
0
2100
5 6 NO
6 0 NO
YES
YES
5
5
20
0
0
0
0
0
A
A
0
0
0
7 0 NO YES 5 0 0 0 A 0 0
8 4 NO YES 5 10 0 0 A 0 0
9 0 NO NO 5 0 0 0 A 0 0
SAVE DeleteStat CANCEL
Fig. 2-21 Selection of SIT file tab 'Stations', right columns (example: RCSU-SITE)
Ed. 07.03 2-19

RMMC Config RMMC
2.5.5 File Tab 'Forced Shutdown'
The file tab 'Forced Shutdown' is only used if remote control systems have to be configured (HardĆ
ware Type on file card 'System' is defined as REU or LKE). ILS stations of the runway(s) are controlled
by these remote control systems. Connected stations are GP, LLZ, Marker, defined on file card 'StaĆ
tions'. During configuration of other remote control systems there is no reaction after clicking on file
tab 'Forced Shutdown'. An information box appears containing message 'Not supported for CSB staĆ
tions'.
By clicking on file tab 'Forced Shutdown' the corresponding file card is presented in the foreground
within the dialog box ready for modification (see fig. 2-22, example RCSU-SITE, hardware type
REU). On the file card 'Forced Shutdown' certain system functions of the REU can be defined:
Dualface Interlock:
If the runway controlled by the REU has ILS systems on both sides, two different operation modes
are defined:
With DUAL FACE INTERLOCK (in check box marked with 'X') means only one system at a time is
allowed to radiate a signal;
Without DUAL FACE INTERLOCK (no mark in check box, example in fig. 2-22) means each sysĆ
tem can be switched on and off separately if there are two intersecting or parallel approach direcĆ
tions.
RMMC Configuration
Konfig
File Help Options
System
Forced Shutdown
Hardware
Status Exchange
Stations
Dualface Interlock: YES/NO
Forced shutdown:
Runway #1 Master:
LLZ Alarm LLZ Alarm or Datacom Error
ON Slave: GP MM OM
OFF Delay: Standard Other ON 0 [sec]
OFF 0 [sec]
Forced Shutdown:
Runway #2 Master: LLZ Alarm LLZ Alarm or Datacom Error
ON Slave: GP MM OM
OFF Delay: Standard Other ON 0 [sec]
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ OFF 0 [sec]
SAVE CANCEL
Fig. 2-22 Selection of SIT file tab 'Forced Shutdown' (example: RCSU-SITE)
2-20 Ed. 07.03

RMMC RMMC Config
Forced Shutdown (forced switching off of stations):
For ILS systems it is sometimes necessary to do delayed forced switching off of associated staĆ
tions, if a 'Main' station is in ALARM state. For the 'Master' station LLZ it is possible to define 'Slave'
stations (GP, IM and/or OM) on the file card. The corresponding check boxes have to be marked
with an 'X'. By clicking on the radio buttons ON and OFF the forced shutdown can be activated
(ON) or deactivated (OFF).
An 'ON' and 'OFF' time can be configured for the 'Slave' stations defining the switching delay time
- between end of alarm and switching on of the 'Slave' stations
(Station will be switched on after ... seconds = 'ON' time) resp.
- between occurrence of alarm and forced shutdown
(Station will be switched off after ... seconds = 'OFF' time).
If the radio button Standard is selected the standard delay time of 10 seconds is defined. In this
case the ON and OFF time value has to be '0'.
Other times between 0 and 200 seconds are defined by selecting radio button Other and putting
the time value into the edit box.
Besides that it is possible to define on the file card, whether a Data Communication Error between
the remote control unit and the 'Master' station initiates additionally to ALARM state at 'Master' station
a forced shutdown of the 'Slave' stations. The radio button LLZ Alarm or Datacom Error has to be
marked (see fig. 2-22).
Ed. 07.03 2-21

RMMC Config RMMC
2.5.6 File Tab 'Status Exchange'

NOTE: The function 'Status Exchange' is optional. Normally only service personnel has access
to the data. If the function isn't implemented, there will be no reaction after clicking on file
tab 'Status Exchange'.
To transmit a state of a station (MAIN STATE) of a RCSE/RCSU to another remote control unit (RMC)
it is necessary to define on both sides, which stations will trigger a dialling process on RCSE/RCSU
or LRCI side. The definition is done on this file card 'Status Exchange'. By clicking on file tab 'Status
Exchange' the corresponding file card is presented in the foreground within the dialog box ready for
modification (see fig. 2-23, example definition of RCSU site). The table is not completely presented
within the dialog box, the scroll bar below the table enables the operator to get access to the 'hidden'
columns (in fig. 2-23 the RPU positions 15, 16 and the columns RWY-1/2).
For better understanding of the following explanations see the system configuration example which
which was presented in fig. 2-15.
In the present example (see fig. 2-23) the RPU positions 5 and 6 are marked, i.e. each of these staĆ
tions will trigger a dialling process to report the state to the remote control unit when status changes.
The table on the file card 'Status Exchange' defines the positions of the RPU panel at the RCSE/RCSU
site where the NAVAIDS stations of the system are indicated. The stations of the system are defined
on the file card 'Stations' (see section 2.5.4).
The stations indicated on the RPU panel are listed in the table column Name. The column OtherId
specifies the REU Id of the remote control unit, where the stations are indicated. In our example the
remote control unit RMC has the Id 1 (see fig. 2-15).
File Help Options
Name OtherId RemRpu DataSelf 1 2 3 4 5 6 7 8 9 10 11 12 13
ILS_200
SITE_200
1
1
0
0
X
X X X
y
y
SAVE CANCEL
Fig. 2-23 Selection of SIT file tab 'Status Exchange' (example: RCSU-SITE)
2-22 Ed. 07.03

RMMC RMMC Config
If stations defined by file cards are directly connected to the remote maintenance unit (e.g. RCSE/
RCSU or LRCI) the station data exists locally (DataSelf = TRUE, i.e. check box is marked, see fig.
2-23). An example where the DataSelf flag is set to FALSE is given in fig. 2-24.
The RPU panel is able to indicate max. 8 stations. The data of station 9 to 16 is indicated on RPU panel
2 (optional) and via ADRACS user program at the connected PC/laptop. The horizontal rows of numĆ
bers 1 to 16 define the indication positions.
By means of columns RWY-1 and RWY-2 the operator can define, that the state of the runways
(only for ILS system) should be indicated additionally to the states of stations. This indication can be
taken place at a CTU or within ADRACS user program.
Additionally to the definition of the RCSE/RCSU site the definition of the RMC site on the other side
of the status exchange has to be defined. Fig. 2-24 shows the file tab with these definitions.
The remote RPU position (RemRpu) specifies the RPU position of a station connected to the local
RCSU seen from the remote maintenance unit (RMC). This is necessary for commands carried out
by the remote maintenance unit to switch stations on/off (exact position is necessary) and to start a
dialling process.
If the remote maintenance unit (RMC) is configured the station data is received from remote unit via
PTT or dedicated line (DataSelf = FALSE), i.e. the check box is not marked.
File Help Options
Konfig Config of C:\CONFIG\EXAMPLE\RMC-SITE.SIT
System
Forced Shutdown
Hardware
Status Exchange
Stations
Name OtherId RemRpu DataSelf 1 2 3 4 5 6 7 8 9 10 11 12 13
VOR_100 100 1 X
DME_100 100
ILS_200 200
2
0
X
SITE_200 200
0 X X
y
y
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ SAVE CANCEL
Fig. 2-24 Selection of SIT file tab 'Status Exchange' (example: RMC-SITE)
Ed. 07.03 2-23

RMMC Config RMMC
2-24 Ed. 07.03

RMMC RMMC Config
2.6 CONFIGURATION OF OIO-FILES
2.6.1 General
The file tab control system supports the creation of the OIO-files. The various data sets to define the
connections between input and /or output pins of OIO board to external devices are stored on differĆ
ent file cards each presented in a certain dialog box. To select one of the dialog boxes (i.e. one of the
file cards) click on the corresponding file tab. The following sections are explaining the different dialog
boxes which are opened after a file tab selection.
The RCSU of the system configuration example presented in fig. 2-15 includes one OIO card to
provide an additional indication of the states of connected stations. In our example the states of the
connected SN400 and DME stations (via SIB) are put out via OIO output pins 9 to 13 and indicated
at external devices (e.g. at LEDs). Additionally an NDB station is connected to the OIO board of the
RCSU via OIO input pins 1 and 2. The data communication is supervised and the status of the NDB
station is indicated on LCD display of RCSU. All connected stations with the corresponding adĆ
dresses have been defined on the file card 'Stations' of the RCSU SIT-file (see section 2.5.4). The
following sections are based on the presented example of fig. 2-25.
RMC-SITE
LCU-SITE Status
Information
PTT
SN400_VOR FSD-45
Data Com
OIO Output Pins 9 10 11 12 13 14 15 16 NDB 436
1
RCSU 443 RCSU-SITE ID=200 OIO Card 1
2
ILS_200 SITE_200
Information
Status
3
1 2 3 4 5 6 7 8
4 Addr. 0
FSD_34L
LLZ_34L
5
GP_34L
DME
VOR
8
LCD Display
OIO Input Pins
SIB
NDB <Status>
2sB 2sB 2sB 1sB 1sA
SN400_LLZ_2F Addr. 1
SN400_GP_2F Addr. 0
SN400_VOR Addr. 2
FSD-40 Addr. 128
FSD-45 Addr. 129
Fig. 2-25 RCSU-Site of the system configuration example, function of OIO card
Ed. 07.03 2-25

RMMC Config RMMC
2.6.2 File Tab 'General'
By clicking on file tab 'General' the corresponding file card is presented in the foreground within the
dialog box ready for modification (see fig. 2-26).
By means of file card 'General' the Number of OIO Cards, the System Texts with the assignments
within the system (Assignments of the System Texts), Timer Assignment and some other assignĆ
ments and concurrences are defined.
CAUTION
The modification of system texts is the only action the operator is allowed to do. The other
definitions and assignments of data within the Selected List box should not be modified
by the operator. The definitions and modifications should only be done by the service perĆ
sonnel of Thales ATM.
The operator is able to modify the system texts by selecting the radio button System Texts of SeĆ
lected List box. Within the edit box beside the Selected List box the text definition is presented (see
fig. 2-26). By means of the edit boxes Index: and System Text: the system text can be modified. After
actuating the 'return' key of the PC keyboard the modification of the text appears within the edit box.
File Help Options
Konfig
General
Version Number: 001.04
OIO-Pins Concurrences
Number of OIO Cards
0 1 2 3 4
Selected List
System Texts 255 NDB OK
Timer Assignment 254 NDB ALARM
Special Functions 253 BURGLARY
252
251
250
ALARM
DISABLED
DISCONNECT
Typ: OIO Address: 0
Typ: DME-TAC Address: 128 Index:
254
Typ: SN400 Address: 2 System Text:
Delete NDB ALARM
Insert
Copy Station
Fig. 2-26 Selection of OIO file tab 'General' of system configuration example (RCSU-SITE)
2-26 Ed. 07.03

RMMC RMMC Config
The assignment of the defined system texts to the station and the line of the LCD display of the RPU
indication panel where it is indicated is presented be selecting the radio button Assignments of the
System Texts. A certain station can be selected within Stations group box (see fig. 2-27).
File Help Options
Konfig
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Number of OIO Cards
Version Number: 001.04
0 1 2 3 4
Selected List
System Texts Text: NDB OK (255) at LCD-Pos: Line 4a
Timer Assignment Text: NDB ALARM (254) at LCD-Pos: Line 4a
Special Functions
Typ: OIO Address: 0
Typ: DME-TAC Address: 128 System Text:
NDB ALARM
Typ: SN400 Address: 1 at LCD-Position:
Line 4a
Insert Delete
Copy Station
Fig. 2-27 OIO file tab 'General', Assignments of the System Texts (example: RCSU-SITE)
Ed. 07.03 2-27

RMMC Config RMMC
2.6.3 File Tab 'OIO-Pins'

By clicking on file tab 'OIO-Pins' the corresponding file card is presented in the foreground within
the dialog box ready for modification (see fig. 2-29).
NOTE: If number of OIO card is set to '0' on file tab 'General' there is no reaction after clicking
on file tab 'OIO-Pins'.
Another file card system within file tab 'OIO-Pins' is defining the different OIO cards. For each OIO
card all OIO input and output pins (pin Nb.) are described by setting the input and output time values
0To1_0Time, 0To1_1Time, 1To0_0Time and 1To0_1Time. The following figure shows the meaning
of the time values.
Input Ouput
current logical 1
Input Value
Signal in REU
no current logical 0
logical 1 circuit closed

Value Output
in REU Signal
logical 0 circuit open
0To1_0Time 0To1_1Time 1To0_1Time 1To0_0Time 0To1_0Time 0To1_1Time 1To0_1Time 1To0_0Time
Fig. 2-28 Time values defined for OIO inputs and outputs
RMMC Configuration
Konfig
File Help Options
Konfig C:\CONFIGS\EXAMPLE\RCSUSITE.OIO
OIO-Card 1
Nb. 0To1_0Time 0To1_1Time 1To0_1Time 1To0_0Time In/Out Sta
1 1000
2 1000
0
0
1000
1000
0
0
Input
Input
YE
YE
3 1000 0 1000 0 Input YE
4 1000 0 1000 0 Input YE
5 1000 0 1000 0 Input YE
6 1000
7 1000
0
0
1000
1000
0
0
Input
Input
YE
YE
8 0 100 0 100 Output (single pulse) YE
15
0 100 0 100 Output (single pulse) YE
Fig. 2-29 Selection of OIO file tab 'OIO-Pins' (example: RCSU-SITE)
2-28 Ed. 07.03

RMMC RMMC Config
The column In/Out defines wether the pin is an OIO input pin or an OIO output pin. The input or output
signal can be Static (without pulse) or with negative/positive pulse. The Start value defines if the
pulse begins with '0' or '1'.
2.6.4 File Tab 'Concurrences'

By clicking on file tab 'Concurrences' the corresponding file card is presented in the foreground within
the dialog box ready for modification (see fig. 2-30).
NOTE: If no station is defined on file tab 'General' there is no reaction after clicking on file tab
'Concurrences'.
A subsystem of file cards appears, each card presenting the definition of concurrences of one certain
station defined in edit box Stations: of file tab 'General'. In example of fig. 2-30 the station OIO / Adr.
0 is selected. For this station text strings are defined, which are indicated on the LCD display of the
RPU depending on actual state of specified OIO pins.
After selecting a certain concurrence within the text box the list boxes Function:, Result:, First OperĆ
and: and Second Operand: appear containing the definition of the concurrence (e.g. in fig. 2-30,
Function: Concurrence, Result: History Data/History Byte 2 Bit 0, First Operand: OIO Pin 2). This definiĆ
tion can be modified by the operator by means of the list boxes. For example to invert the OIO pin
status of OIO Pin 2 in 2nd line of example the operator has to select the 'NOT' function in the list box
Function:. The concurrence within the text box is then changed to History Byte 2 Bit 0 := NOT OIO
Pin (2)". The stations and the LCD texts are predefined on file card 'General'.
NOTE: The operator is not allowed to perform bigger modifications like creation of new concurĆ
rences or deletion of existing concurrences, because certain modifications may change
the whole system state and lock the system. Therefore the push buttons Insert, Add and
Delete are not active for the operator.
RMMC Configuration
Konfig
File Help Options
General
OIO-Pins Concurrences
Typ: OIO / Adr. 0 Typ: DME-TAC/Adr.128
Function:
IF OIO Pin (1)
Concurrence
History Byte 2 Bit 0 := OIO Pin (2)
OIO Pin
Station (12) :=:=
Warning Station Alarm
Logisch 0
Result: Station
OIO PinAlarm
(12) := Station
NOT History
AlarmByte 2 Bit 0
History-Data IF History Byte 2 Bit 0
Show Text "NDB OK " in LCD-Line 4a := Logisch 1
History Byte 2 Bit 0 ELSE
OIO Pin
Show Text(12)
"NDB:= ALARM"
Station Alarm
in LCD-Line 4a := Logisch 1
First Operand: END IF
ELSE
OIO Pin OIO Pin
Station (12) := Station
DataComError Alarm
sofort := Logisch 1
OIO Pin
Clear (12) :=Bits
All History Station Alarm 1
:= Logisch
2
Station
OIO PinAlarm
(12) := Station
LogischAlarm
1
Station
OIO PinMaintenance := Logisch
(12) := Station Alarm 0
END IF
Insert Add Delete
Fig. 2-30 Selection of file tab 'Concurrences', text string definitions (example: RCSU-SITE)
Ed. 07.03 2-29

RMMC Config RMMC
Within the text box each logical branch (of IF and ELSE statements) can be presented (open) or not
presented (closed) by clicking on the icon in front of IF" or ELSE".
To select the concurrency file card of another station click on the corresponding file tab inside the
header of the text box. To get more stations click on push buttons or .
In example of fig. 2-31 the station SN400 / Adr.1 is selected. For this station the alarm status of the
station is given to OIO output pin 9. As described in fig. 2-25, the station is internally connected via
SIB board to the OIO card. The status of the station is indicated on an external device (e.g. at an LED).
File
Help Options
Konfig
Function:
Typ: SN400/ Adr.0 Typ: SN400 / Adr. 1 Typ: SN400 / Adr. 2
Concurrence OIOPin
OIO Pin(9)
(12)
:=:= Station
Station Alarm
Alarm
Result:
OIO Pin
9
First Operand:
Station-Status-Output
Station Alarm
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Insert Add Delete
Fig. 2-31 Selection of file tab 'Concurrences', status output definition (example: RCSU-SITE)
2-30 Ed. 07.03

RMMC RMMC Config
2.7 HELP FUNCTION
2.7.1 Help Topics for SIT-File Configuration
The help function is explaining the procedure of SIT file creation in principle. Special emphasis is
placed on the input possibilities on the different file tabs. The following items are considered:
- general explanations to SIT configuration (application examples)

- project data
- communication interfaces (default interfaces for different devices)
- station peculiarities (e.g. ZUA task)
- status exchange (mechanism of sending/receiving status messages)
RMMC Configuration
Konfig
File Help Options
Konfig Config Help
of C:\CONFIG\EXAMPLE\RCSUSITE.SIT
Topics
Forced Shutdown
About
System
Config
Status Exchange
Hardware Stations
Project Data
Finger Print
Project: EXAMPLE
Country: Germany
Order Number: Customer: AIRSYS, ATS/E
PC_USER: NS
Project Path: C:\CONFIG\EXAMPLE\ Date: 21.7.1999 10:52:58
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ CRC: OK
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ RWY-34L
Runway 1:
X Update Statnames
Runway 2:
REU Id: 200 (1 .. 4095)
Hardware: REU
ID=200 19.05.99NN
SAVE CANCEL
Fig. 2-32 Function 'Help Topics' for SIT file configuration (example)
2.7.2 Context Help for SIT-File Configuration
On each file tab of SIT file configuration system it is possible to get context help to different keywords.
The keyword selection is done by clicking with the right mouse button on the keyword and then actuĆ
ating the F1 hardkey of the keyboard.
Ed. 07.03 2-31

RMMC Config RMMC
2.7.3 Help Topics for OIO-File Configuration
The help function is explaining the procedure of OIO file creation in principle. Special emphasis is
placed on the input possibilities on the different file tabs. The following items are considered:
- general explanations to SIT configuration (application examples)

- explanations to file tab 'General'
- explanations to file tab 'OIO-Pins' including the possible time settings
- explanations to file tab 'Concurrences' (function, result, operands)
- explanations to different possibilities for selection of variables (function, result, operands)
File Help Options
Help Topics
General
About Config OIO-Pins Concurrences
0 1 2 3 4
Selected List
System Texts
Timer Assignment
Special Functions
Typ: OIO Address: 0
Insert Delete
Copy Station
Fig. 2-33 Function 'Help Topics' for OIO file configuration (example)
2.7.4 Context Help for OIO-File Configuration
On each file tab of OIO file configuration system it is possible to get context help to different keywords.
The keyword selection is done by clicking with the right mouse button on the keyword and then actuĆ
ating the F1 hardkey of the keyboard.
2-32 Ed. 07.03

En 07.03 RMMC Config Tool

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

En 07.03 RMMC Config Tool

Hochgeladen von

Copyright:

Verfügbare Formate

Reference No.

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

All rights reserved

The Technical Manual for the RMMC Configuration Program 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.

List of valid pages

Pages Ed.-No. Remarks

Annex 07.03 Additional Features for Service Personnel

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

CHAPTER 2 DESCRIPTION AND USE OF RMMC CONFIGURATION . . . . . . . . . . . . . . . . . 2-1

2.6 CONFIGURATION OF OIO-FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

Fig. 2-1 Starting 'RMMC Configuration' program (example) . . . . . . . . . . . . . . . . . . . . . 2-2

Ed. 07.03 III

Fig.-No. Title Page

Ed. 07.03 1-1

a) connection to a station b) connection to a remote control system

Mouse Keyboard Printer Printer Mouse Keyboard

Zero modem cable Zero modem cable

Fig. 1-1 System configuration of 'RMMC Configuration' program via PC (example)

1-2 Ed. 07.03

The 'RMMC Configuration' program is a Windows-based product and requires Windows to be

1.4.2 Installation of 'RMMC Configuration' on PC

Start installation of 'RMMC Configuration' program

Ed. 07.03 1-3

1-4 Ed. 07.03

1.5.2 Program Structure

Menu: Command: Edit box:

Exit SIT file OIO file

Fig. 1-4 Structure of 'RMMC Configuration' program, functions in start window

Ed. 07.03 1-5

New Site Open Site

2 Selection of Hardware type: Selection of config file:

Application window Application window

System Hardware Stations Forced Status

Project SIB Outputs/ Station Type Dual Face RPU

REU id RWY Switch optional

Fig. 1-5 Structure of 'RMMC Configuration' program, SIT-file configuration

1-6 Ed. 07.03

Selection of station type: Selection of config file:

Application window Application window

Menu: File Selection of file tab:

Exit Save Save as Close

Version Number OIO-Card 1 Station 1

System Texts xToy_z_Time (Result)

Timer Assignments Input/Output First Operand

Special Functions Static (Second Operand)

Assignments of Start Value

Stations (1..n) * available functions depending on type of dongle

Fig. 1-6 Structure of 'RMMC Configuration' program, OIO file configuration

Ed. 07.03 1-7

1-8 Ed. 07.03

2.2 STARTING RMMC CONFIGURATION

- Run Windows operating system.

Ed. 07.03 2-1

Fig. 2-1 Starting 'RMMC Configuration' program (example)

- The application window RMMC Configuration appears (see fig. 2-2).

File Help Options

2-2 Ed. 07.03

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ X Update Statnames

Fig. 2-3 Dialog box for creation of a new SIT-file (example)