Professional Documents
Culture Documents
ATA 46-21 Information Systems
ATA 46-21 Information Systems
A 319/320/321
ATA 46
Information Systems
46-21 ATIMS
Level 3
Page i
TABLE OF FIGURES
Figure 1 ATIMS - Concept / Architecture . . . . . . . . . . . . . . . . . . . . . 3
Figure 2 ATIMS - General Schematic . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 3 ATIMS - Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 4 ATIMS - Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Figure 5 ATSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 6 DCDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 7 MCDU MENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 8 ATIMS - RMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 9 ATIMS - Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 10 ATIMS - Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 11 ATIMS / VDR3 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 12 ATIMS / RMP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Figure 13 ATIMS - Ground Network . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 14 COMM menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Figure 15 AOC Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 16 ATC Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 17 ATIMS - BITE Architecture . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 18 ATIMS - SYSTEM REPORT / TEST page access . . . . 35
Figure 19 ATIMS - System Test Page . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 20 ATIMS - Specific Data Page . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 21 VHF 3 LINK TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 22 VHF 3 LINK TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Page ii
Lufthansa Technical Training
INFORMATION SYSTEM A319/320/321
ATIMS
46-21
GENERAL
Up to now, flight crews have communicated with air traffic controllers using HF and
VHF radio communications which are subject to atmospheric disturbances and so,
often difficult to understand.
Furthermore, the transmission networks become saturated due to the air traffic in-
crease, and to the limited capability to exchange complex data (routes, weather
information...).
Consequently, the Air Traffic and Information Management System (ATIMS)
has been developed to enable datalink communications and the exchange of com-
plex data or specific reports between the aircraft and the ground centers:
S controller-pilot datalink communications (HF voice in backup) for air traffic
management,
S automatic reporting (position, intention) for air traffic surveillance,
S specific airline-aircraft communications (operational control) to improve airline
operational costs and flexibility.
For Training Purposes Only
CNS
For Training Purposes Only
NOTE:The Datalink Control and Display Units (DCDU) are not fitted and the
ATC MSG pushbuttons switches are not operational in Pre-FANS configura-
tion.
In addition, the FANS A configuration contains the ATSU FANS A applications (Air
Traffic Control) with the Datalink Control and Display Units (DCDU) and the ATC
MSG pushbuttons switches operational.
System Architecture
The ATIMS is composed of:
S an Air Traffic Service Unit (ATSU),
S two Datalink Control and Display Units (DCDUs),
S two ATC MSG illuminated pushbuttons switches.
NOTE:The two DCDUs are not fitted in Pre-FANS configuration and the ATC
MSG pushbuttons switches are not operational.
The ATSU is connected to the following units and uses the services of these multi-
purpose devices for interface needs:
S the Multipurpose Control and Display Units (MCDUs)
S the Printer
For Training Purposes Only
LOCATIONS
-------------------------------------------------------------------------------
FIN | FUNCTIONAL DESIGNATION | PANEL|ZONE|ACCESS | ATA
| | | | DOOR | REF.
-------------------------------------------------------------------------------
COMPONENT DESCRIPTION
ATSU Description - ATSU A/C interface software
The ATSU is the main component of the system.
Itsdifferent functions are :
Its architecture is based on: Smonitoring of the system (power supply and BITE functions)
S an Air Traffic Service Unit (ATSU) hardware case Sacquisition of the aircraft parameters for applications software use
S an ATSU A/C INTERFACE software uploaded in the ATSU through the Multi- Smanagement of the air/ground communications (ARF function)
purpose Disk Drive Unit (MDDU) or the portable data loader Smanagement of the communication with the on-board peripheral
S an AOC software uploaded in the ATSU through the MDDU or the portable data units
loader S management of the human/machine interface (MCDU, DCDU, Printer
S an ATSU FANS A APPLICATIONS software uploaded in the ATSU through the and alert function)
MDDU or the portable data loader (only in FANS A configuration). - AOC software
The main functions performed by the ATSU are:
S to host the various datalink applications, including Airline Operational Control The AOC software consists in hosted AOC applications which are de-
and Air Traffic Services, pending on airline definition.
These datalink applications concern operations related to the flight such
S to provide management and access to the different datalink services available,
as flight plans, weather, behaviour of aircraft elements transmitted for
S to provide management and access to the various datalink networks available. maintenance reasons, fuel quantity, personnel management, gate man-
agement...
- ATSU FANS A applications software
The different Air Traffic Control (ATC) applications contained in this pack-
age are:
S (a)ATS Facilities Notification (AFN) application
The purpose of this application is to establish the contact with the ATC
ground center, then to provide the ATC center with the aircraft registra-
tion, the data-link applications available on the aircraft with the corre-
For Training Purposes Only
sponding addresses.
S (b)Controller-Pilot Data Link Communications (CPDLC) application
The aim of this application is to provide dialog between ground control-
lers and flight crews, using datalink instead of voice communications.
Each CPDLC message is composed of a set of message elements
which correspond to the existing phraseology used by current ATC pro-
cedures.
S (c)Automatic Dependent Surveillance (ADS) application
The ADS function is to provide the ATC ground center with aircraft sur-
veillance data through periodic, event or on-demand reports.
Figure 5 ATSU
HAM US/F JC 01.07.2000 Page 9
Lufthansa Technical Training
INFORMATION SYSTEM A319/320/321
ATIMS
46-21
DCDU Description Functional Operation
Datalink Control and Display Unit (DCDU) (in FANS A configuration only) The DCDU has two main functions:
The DCDUs are the interface means dedicated to the ATC applications. They pro- S Display function: display of the air traffic system information to the flight
vide the flight crew with display capabilities and control means, allowing the display crew
of messages received from ATC ground center and the sending of answer and The DCDU is equipped with an LCD flat panel.
messages to the ground center. The DCDUs are managed by the ATSU which pro- The DCDU displays the messages formatted by the ATSU on a black back-
cesses and organizes the data in screen pages to be displayed and translates re- ground, in eight different colors: amber, black, cyan, green, magenta, red,
ceived key codes into crew orders (soft keys). white and yellow.
These messages are in semi-graphical format and include alphanumerical
text and simple graphical attributes such as boxes, arrows, separation lines,
Physical Description
”inverse video”...
The DCDU is equipped with a LCD screen and twice four push-buttons located
on each side of the screen. S Control function: a response device for the flight crew.
Electrical Characteristics The DCDU has:
S power supply: 28VDC - four pushbuttons switches associated to menu keys named ”soft keys”
S dissipated power : 16.5 Watts (average value). - four engraved pushbuttons switches dedicated to:
S one back connector composed of: S page up and down functions.
- one ARINC 429 input bus from the ATSU. S message up and down functions .
- one ARINC 429 output bus to the ATSU. S print function .
- eleven discrete inputs (P- type) for pin programming, power supply, S manual brightness control.
ground and air/ground signal.
- one analog input. In addition, the pushbuttons switches are lighted for night vision in accor-
dance with the general cockpit selection.
Each DCDU has a ”black screen” function in order not to disturb the flight
crew in case of abnormal display.
Any action on a pushbutton switch is transmitted to the ATSU.
Any action on a menu key is acknowledged by the DCDU itself on the
display, prior to and independently of a possible message change from
the ATSU, by a reverse video display.
For Training Purposes Only
The time elapsed between pilot action and both sending of the data on
the ARINC bus and local feedback displayed on the screen is not greater
than 100 ms.
Figure 6 DCDU
HAM US/F JC 01.07.2000 Page 11
Lufthansa Technical Training
INFORMATION SYSTEM A319/320/321
ATIMS
46-21
MCDU USE
The MCDU gives access to these three independent menus:
S for air/ground communication management functions:
- configuration/initialization.
- VHF3 control.
- communication statistics display.
- test/audit mode control
S for AOC hosted applications:
- configuration/initialization.
- downlink message entry/selection/transmission.
- uplink message display
S for ATC applications in FANS A configuration:.
- preparation and modificaton of all the messages initiated by the crew,
- justifications to negative replies or to a particular request,
- editing of text,
- configuration of applications (ADS activation, AFN initialization) and
- configuration of systems (ATSU management, automatic or on-request
printing).
For Training Purposes Only
RMP USE
Each of the three RMPs is an interface device for the VDR3 operation.
The frequency range is from 118000 to 136975 KHz by 25 KHz or 8.33KHz steps.
Each RMP enables the crew to ask for a switching between the RMP and the ATSU
to control the VDR3 frequency:
S When the RMP controls the VDR3 frequency, only the Voice mode is avail-
able and the selection of the VDR3 frequency is done through the RMP by dis-
playing the frequency in the ACTIVE window.
S When the ATSU controls the VDR3 frequency, the Voice mode can be ac-
cessed through the ATSU menu on the MCDU and the selection of the VDR3
frequency is done on the MCDU either in Data mode or in Voice mode.
NOTE:
The RMP sends to the ATSU the pilot request of switching the system control-
ling the VDR3 between the RMP and the ATSU. In return, the ATSU indicates
to the RMP which system, between the RMP and the ATSU, is controlling the
VDR3 frequency.
For Training Purposes Only
POWER SUPPLY
The ATIMS system is supplied with this(these) following circuit breaker(s):
The DCDU2 is supplied with 28VDC from the main 28VDC BUS1 bar 202PP via
circuit breaker 6TX2.
For Training Purposes Only
INTERFACE
General The ATSU is interfaced with the following peripheral units:
The ATSU uses the data transparent protocol, defined in ARINC 429 Specifica- S the Flight Management and Guidance Computer 1 and 2 (FMGC) (Ref.
tion, when it communicates with the on-board avionics systems. AMM 22-83-00)
S the Multipurpose Control and Display Unit 1 and 2 (MCDU) (Ref. AMM
22-82-00)
S the Cabin Terminals: the Cabin Management System (Ref. AMM 23-74-00)
and the Digital Interface Unit (Ref. AMM 23-34-00)
31-62-00)
S the Centralized Fault Display Interface Unit (CFDIU) (Ref. AMM 31-32-00)
OPERATION
System Configuration ATSU DATALINK applications
Three menus are available:
(1)ATSU A/C INTERFACE software loading S Air/Ground Communication Menu
S The loading procedure is ensured by the ” Boot software” included in the
ATSU hardware case. The COMM MENU is available in pre-FANS and FANS A configurations
The ATSU is first to be loaded with the A/C INTERFACE software which and gives access to:
takes A/C configuration and adaptation to different system interfaces into - the COMM INIT page to initialize the datalink communications
account.
It contains namely air/ground communication services and the router func- - the VHF3 DATA MODE page to select the Data mode and the VDR3 fre-
tion. quency
The adaptation to the A/C configuration is also ensured through pin pro- - the VHF3 VOICE DIRECTORY page to select the Voice mode and the
gramming acquisition, either from hard ATSU pin programming, or from pin VDR3 frequency
programming information received fron CFDIU (configuration label). - the COMM STATUS page to display the availability of the VHF3 and
SATCOM networks
NOTE:The ATSU is automatically reseted after a software loading operation - the COMPANY CALL page to display the message content and to vali-
through an internal mechanism.The LRU IDENTIFICATION function from date a VOICE-GO-AHEAD
the BITE enables to display the software version reference in order to check
- the MAINTENANCE page which comprises a TEST part and an AUDIT
the correct uploading.
part
(2)AOC software and database loading
These menus are developped in AMM 46-24-00, P. Block 001.
S In Pre-FANS configuration, the AOC application software and the associ-
ated database are then up-loaded in the ATSU.
The AOC software package contains the specific airline datalink applica-
tions.
Remote AOC applications are also embedded in peripherals which some of
them are optional such as DMU, Cabin Terminals (remote AOC peripher-
als).
(3)ATSU FANS A applications loading
For Training Purposes Only
BITE ARCHITECTURE
The ATIMS BITE is used to facilitate the aircraft maintenance in compliance
with ABD048 specifications.
It detects, identifies and memorizes the internal and external failures related to
the ATIMS system:
S ATSU internal failures
S external interface failures with ATSU peripherals.
The ATIMS BITE is ensured by the ATSU which concentrates the failure infor-
mation provided by the ATSU internal monitoring.
This BITE is of type 1 and operates in two modes:
S normal mode
S MENU mode
Normal mode
During the normal mode, the BITE:
S monitors the ATSU status
S monitors data inputs from the various ATIMS peripherals (FMGC, MCDU,
CFDIU,...)
S permanently transmits ATIMS system status and its identification message
to the CFDIU.
In case of fault detection, the BITE stores the information in the fault memories
and transmits it to the CFDIU by an ARINC 429 message (Label 356).
The BITE memorizes the failures which occurred during the last 63 flight legs.
For Training Purposes Only
This mode enables communication between the CFDIU and the ATIMS
BITE by means of the MCDU.
S TEST OK indication when all the tests are completed and no failure has
been detected
S or the failure message(s) when one or more failures have been detected.