AIR TRAFFIC AND INFORMATION MANAGEMENT SYSTEM (ATIMS) - COMPONENTS AND INTERFACES - DESCRIPTION AND OPERATION

** ON A/C NOT FOR ALL

1. General

ATIMS - General Architecture ** ON A/C NOT FOR ALL

Until now, the flight crew have communicated with the air traffic controllers using High Frequency (HF) and Very High Frequency (VHF) radio communications. These communications are subjected to atmospheric disturbances and difficult to understand.
Furthermore, the transmission networks become saturated due to the increase in air traffic and to the limited capability to exchange complex data (routes, weather information, etc.).
Consequently, the Air Traffic and Information Management System (ATIMS) was developed to enable datalink communications and exchange of complex data or specific reports between the aircraft and the ground centers:

Controller-pilot datalink communications (HF voice in backup) for air traffic management
Automatic reporting (position, intention) for air traffic surveillance
Specific airline-aircraft communications (operational control) to improve the airline operational costs and flexibility.

ATIMS - General Architecture ** ON A/C NOT FOR ALL

Up to now, flight crew 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 increase, 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 complex data or specific reports between the aircraft and the ground centers:

controller-pilot datalink communications (HF voice in backup) for air traffic management,
specific airline-aircraft communications (operational control) to improve airline operational costs and flexibility.

** ON A/C NOT FOR ALL

2. Component Location

Component Location - Avionics Compartment ** ON A/C NOT FOR ALL

Component Location - Cockpit ** ON A/C NOT FOR ALL

Component Location - Avionics Compartment ** ON A/C NOT FOR ALL

Component Location - Cockpit ** ON A/C NOT FOR ALL

Component Location - Avionics Compartment ** ON A/C NOT FOR ALL

FIN	FUNCTIONAL DESIGNATION	PANEL	ZONE	ATA REF
** ON A/C NOT FOR ALL
1TX1	ATSU	80VU	122	46-21-34
** ON A/C NOT FOR ALL
1TX1	ATSU	81VU	127	46-21-34
** ON A/C NOT FOR ALL
20TX	SOFTWARE-ATSU A/C INTERFACE		211	46-21-00
** ON A/C NOT FOR ALL
22TX	SOFTWARE-AOC		211	46-21-00
24TX	SOFTWARE-AOC DATABASE		211	46-21-00
** ON A/C NOT FOR ALL
21TX	SOFTWARE-ATSU CONFIGURATION		211	46-21-00
** ON A/C NOT FOR ALL
30TX	SOFTWARE-ATSU ROUTER PARAM		211	46-21-00
** ON A/C NOT FOR ALL
2TX1	DCDU-1		211	46-21-21
2TX2	DCDU-2		212	46-21-21
** ON A/C ALL
4TX1	P/BSW-ATC MSG, CAPT	131VU	211	46-21-00
4TX2	P/BSW-ATC MSG, F/O	130VU	212	46-21-00
** ON A/C NOT FOR ALL
25TX	SOFTWARE-ATC HMI UTILITIES		211	46-21-00
** ON A/C NOT FOR ALL
35TX	SOFTWARE-ATSU ATC FANSA APPLICATIONS		211	46-21-00
** ON A/C NOT FOR ALL
23TX	SOFTWARE-ATSU ATC ARINC 623 APPLICATIONS		211	46-21-00
** ON A/C NOT FOR ALL
31TX	SOFTWARE-ATSU ISM APPLICATION		211	46-21-00
36TX	SOFTWARE-ATSU ATC FANSB APPLICATIONS		211	46-21-00
37TX	SOFTWARE-ATSU CMA DATABASE		211	46-21-00

** ON A/C NOT FOR ALL

3. System Description

A. System Configuration

ATIMS - System Configuration ** ON A/C NOT FOR ALL

The Air Traffic and Information Management System (ATIMS) consists mainly of an Air Traffic Service Unit (ATSU) which provides:

management of the datalink media: VHF datalink Satellite datalink (optional) and HF datalink (optional).

The ATSU is configured with the following applications:

Aircraft Interface software (for host platform services)
Configuration software (for manufacturer configuration parameters)
Router parameters software (for the VHF Datalink Service Provider (DSP) World Map)

ATIMS - System Configuration ** ON A/C NOT FOR ALL

The ATIMS consists mainly of an Air Traffic Service Unit (ATSU) which manages the datalink media:

VHF datalink (Aircraft Communication Addressing and Reporting System (ACARS) mode or VHF Data Link (VDL) mode 2, also known as ACARS aviation VHF link control: new frequency, new modulation, new air/ground protocol)
Satellite datalink (optional)
HF datalink (optional).
The ATSU is configured with the applications that follows:
Aircraft interface software (for the host platform services)
Configuration software (for the manufacturer configuration parameters)
Router parameters software (for the VHF Datalink Service Provider (DSP) world-map)

ATIMS - System Configuration ** ON A/C NOT FOR ALL

The ATIMS consists mainly of an Air Traffic Service Unit (ATSU) which provides:

datalink services for ATC
management of the datalink media: VHF datalink (mode ACARS or VDL mode 2, also known as ACARS Aviation VHF Link Control (AOA): new frequency, new modulation, new air/ground protocol) Satellite datalink (optional) and HF datalink (optional).

The ATSU is configured with the following applications:

Aircraft Interface software (for host platform services)
Configuration software (for manufacturer configuration parameters)
Router parameters software (for the VHF Datalink Service Provider (DSP) World Map)

B. System Architecture

The ATIMS comprises:

an Air Traffic Service Unit (ATSU),
two Datalink Control and Display Units (DCDUs),
two ATC MSG illuminated pushbutton switches.

NOTE: In Pre-FANS and Pre-FANS + configurations, the two DCDUs are not fitted and the ATC MSG pushbuttons switches are not operational.

The ATSU interfaces with the following on-board units:

for Aeronautical Passenger Communications (APC) applications:
FMGC, CFDIU, DMU, Digital Interface Unit (DIU).
for access and management to the datalink sub-networks:
VHF Data Radio (VDR3), SATCOM (optional).
for system management, maintenance and configuration:
FWC, SDAC, CFDIU, LGCIU, Multipurpose Disk Drive Unit (MDDU) or Portable Data Loader (PDL).
for multipurpose Human-Machine Interface needs:
Multipurpose Control and Display Unit (MCDU), Printer and Radio Management Panels (RMPs).

The ATIMS comprises an ATSU which has interface with the onboard units that follow:

For the aeronautical passenger-communications application:
Flight Management and Guidance Computer (FMGC), Centralized Fault Display Interface Unit (CFDIU), Data Management Unit (DMU), Digital Interface Unit (DIU).
For the datalink and sub-networks access and management:
VHF Data Radio (VDR) (VDR mode ACARS or VDL mode 2), SATCOM (optional), HF (optional).
For the system management, maintenance and configuration:
Flight Warning Computer (FWC), System Data Acquisition Concentrator (SDAC), CFDIU, Landing Gear Control and Interface Unit (LGCIU), Multipurpose Disk Drive Unit (MDDU) or Portable Data Loader (PDL) and Air Traffic Control (ATC) transponders.
For the multipurpose Human-Machine Interface (HMI) needs:
Multipurpose Control and Display Unit (MCDU), Printer and Radio Management Panels (RMP).

C. ATSU Description

ATIMS - Functional Architecture ** ON A/C NOT FOR ALL

The ATSU is the main component of the system.
The ATSU consists of a hardware case with the minimum software and of five packages. Each one is related to a set of disks identified by a Functional Item Number (FIN). These disks contain the ATSU software and application software. The software is uploaded in the ATSU by means of the MDDU or the PDL. A package must be loaded completely and the application/software becomes operational after the ATSU self-test. The package part number(s) is(are) displayed on the MCDU, in the LRU IDENT page related to the ATSU.
The designation on the floppy disk related to the abbreviated terms of official designations are as follow:

-------------------------------------------------------------------------------

FIN DESIGNATION ABBREVIATED DESIGNATION FUNCTION

(ON FLOPPY DISKS)

-------------------------------------------------------------------------------

20TX SOFTWARE-ATSU A/C S/W-ATSU A/C INTFC Aircraft interface

INTERFACE package for the host

platform services

-------------------------------------------------------------------------------

21TX SOFTWARE-ATSU S/W-ATSU CONFIG Configuration

CONFIGURATION package for the

manufacturer

configurable

parameters

-------------------------------------------------------------------------------

30TX SOFTWARE-ATSU ROUTER S/W-ATSU ROUTR PARAM Router parameters

PARAM package

-------------------------------------------------------------------------------

The main functions of the ATSU are:

To host the various datalink applications which includes the Airline operational control.
To provide management and access to the different datalink services available.
To provide management and access to the various datalink networks available.

ATIMS - Functional Architecture ** ON A/C NOT FOR ALL

The ATSU is the main component of the system.
The ATSU consists of a hardware case with minimum software and of five packages, each one corresponding to a set of disks identified by a Functional Item Number. These disks contain the ATSU software and application software. The software is uploaded in the ATSU by means of the MDDU or the PDL. A package must be loaded completely and the application/software becomes operational after the ATSU self-test. The package part number(s) is (are) displayed on the MCDU, in the LRU IDENT page related to the ATSU.
The designation on the floppy disk corresponds to abbreviated terms of the official designations:

-------------------------------------------------------------------------------

FIN DESIGNATION ABBREVIATED DESIGNATION FUNCTION

(ON FLOPPY DISKS)

-------------------------------------------------------------------------------

20TX SOFTWARE-ATSU A/C S/W-ATSU A/C INTFC Aircraft Interface

INTERFACE package for host

platform services

-------------------------------------------------------------------------------

21TX SOFTWARE-ATSU S/W-ATSU CONFIG Configuration

CONFIGURATION package for

manufacturer

configurable

parameters

-------------------------------------------------------------------------------

25TX SOFTWARE-ATC HMI S/W-ATSU ATC UTIL ATC HMI utilities

UTILITIES package

-------------------------------------------------------------------------------

30TX SOFTWARE-ATSU ROUTER S/W-ATSU ROUTR PARAM Router Parameters

PARAM package

-------------------------------------------------------------------------------

31TX SOFTWARE-ATSU ISM S/W-ATSU ISM APPLI ISM application

APPLICATION package

-------------------------------------------------------------------------------

36TX SOFTWARE-ATSU FANSB S/W-ATSU FANSB FANS B applications

APPLICATIONS package

-------------------------------------------------------------------------------

37TX SOFTWARE-ATSU CMA S/W-ATSU CMA CONFIG CMA configuration

CONFIG package

-------------------------------------------------------------------------------

The main functions of the ATSU are:

to host the various datalink applications, including Airline Operational Control,
to provide management and access to the different datalink services available,
to provide management and access to the various datalink networks available.

ATIMS - Functional Architecture ** ON A/C NOT FOR ALL

The ATSU is the primary component of the system.
The ATSU has a hardware case that contains a minimum number of software applications and packages. Each package is related to a software that has a Functional Item Number (FIN).
The Multipurpose Disk Drive Unit (MDDU) or the Portable Data Loader (PDL) uploads the software to the ATSU. The application or the software will operate only after the loading is completed and after you do the ATSU self-test.
You can find the Part Number (PN) of each package in the LRU IDENT menu of the Air Traffic and Information Management System (ATIMS) page, on the Multipurpose Control and Display Unit (MCDU).
The table that follows gives the references of the software applications and their related functions:

-------------------------------------------------------------------------------

FIN DESIGNATION FUNCTION

-------------------------------------------------------------------------------

20TX SOFTWARE-ATSU A/C Aircraft interface package for the host

INTERFACE platform services

-------------------------------------------------------------------------------

21TX SOFTWARE-ATSU Configuration package for the manufacturer

CONFIGURATION configurable parameters

-------------------------------------------------------------------------------

25TX SOFTWARE-ATC HMI ATC HMI utilities package

UTILITIES

-------------------------------------------------------------------------------

30TX SOFTWARE-ATSU ROUTER Router parameters package

PARAM

-------------------------------------------------------------------------------

31TX SOFTWARE-ATSU ISM ISM application package

APPLICATION

-------------------------------------------------------------------------------

36TX SOFTWARE-ATSU FANSB FANS B applications package

APPLICATIONS

-------------------------------------------------------------------------------

37TX SOFTWARE-ATSU CMA CMA configuration package

CONFIG

-------------------------------------------------------------------------------

The primary functions of the ATSU are as follows:

Hosting of the different datalink applications, which includes the airline operational control
Management of, and access to, the different datalink services available
Management of, and access to, the different datalink networks available.

(1) ATSU hardware case
The ATSU hardware case consists of all the necessary hardware resources (hardware platform) and a minimum software.
This minimum software contains two main parts:

The first one is in charge of hardware initialization.
The second part is designed to allow the uploading of the software components.

(2) ATSU A/C interface software
It functions are:

System monitoring (power supply and BITE functions)
Acquisition of the aircraft parameters for the application software use
Management of the air/ground communications (ARF function)
Management of the communication with the onboard peripheral units
Management of the Human/Machine Interface (MCDU, printer and alert function).

The ATSU A/C interface software enables the applications to access the communication environment. It contains the functional services which let the applications to perform their tasks and the main part of the interface services. The air/ground communication services depend on the communication environment (ACARS network), while the onboard integration services and the human/machine interface services depend on the aircraft system configuration.

(3) ATSU hardware case
The ATSU hardware case consists of all necessary hardware resources (hardware platform) and minimum software.
The minimum software contains two main parts:

the first one is in charge of hardware initialization
the second part is designed to allow the uploading of the software components.

(4) ATSU A/C interface software
Its different functions are :

monitoring of the system (power supply and BITE functions)
acquisition of the aircraft parameters for application software use
management of the air/ground communications (ARF function)
management of the communication with the on-board peripheral units
management of the Human/Machine Interface (MCDU, printer and alert function).

The ATSU A/C interface software enables applications to access the communication environment. It contains the functional services allowing the applications to perform their tasks and the main part of the interface services. The air/ground communication services depend on the communication environment (ACARS or ATN network), while the on-board integration services and the human/machine interface services depend on aircraft system configuration.

(5) ATSU configuration software
The configuration software is a complement to the A/C interface software.
This software consists of a database containing routing policies definitions and configuration elements.

(6) ATSU router parameters software
The ATSU router parameters software is a complement to the A/C interface software.
This software contains the standard DSP world map database. The DSP world map contains two types of tables: media configuration tables and VHF world map

(7) ATSU configuration software
The configuration software is a complement to the A/C interface software.
This software consists of a database that has:

Routing policies definitions
Configuration elements
Downlink messages priorities
VDL2 parameters.

This database also contains three elements that are "software pin programmed":

HFDL for ATC applications.
VHF3 voice/data switching by MCDU: this is enabled in the VDL2 configuration and it is inhibited when ATC applications are loaded.
VDL activation.

(8) ATSU router parameters software
The ATSU router parameters software is a complement to the A/C interface software.
This software contains the standard DSP-world-map database and a customization file for the Airline Identification (A/L Id) and for the scan mask parameters.
The DSP world map contains two types of tables: Media configuration tables and VHF world map.

NOTE: By default, A/L Id and scan mask are not customized and the customization file is empty. If they are customized, they cannot be modified on the MCDU. They are always customized together or not.

(a) VHF world map
The DSP-world-map database contains the VHF geographic areas for each service provider. The world map is described over rectangular zones defined by the latitude/longitude of their South-East limits.
The first zone of the world map defined is delimited by 90° at its North border and 180° at its West border. The world map can contain up to 512 zones.

(b) Media configuration tables
The media configuration tables give the ARINC 618 parameters for each air/ground communication medium such as timers, counters, identifiers and VDL2 parameters.
There is a SATCOM, VHF and a HF configuration table for each service provider.

(9) AOC software
The AOC software consists of hosted AOC applications which depend on the airline definition.
An AOC database enables customization of the AOC applications. In this package, it defines the list of the labels used by the AOC application which have to be extracted from the ATSU input data.
These datalink applications concern the operations related to the flight such as flight plans, weather, behaviour of aircraft elements transmitted for maintenance reasons, fuel quantity, personnel management, gate management, etc.

(10) ATSU FANS A applications software
The different ATC applications contained in this package are:

(a) Air Traffic Service (ATS) Facilities Notification (AFN) application:
The purpose of this application is to establish contact with the ATC ground center. Then, to provide the ATC center with the aircraft registration and the datalink applications available on the aircraft with the related addresses.

(b) Controller-Pilot DataLink Communications (CPDLC) application:
The aim of this application is to provide dialog between the ground controllers and flight crews with the aid of datalink instead of voice communication.
Each CPDLC message comprises of a set of message elements which correspond to the existing phraseology used by the current ATC procedures.

(c) Automatic Dependent Surveillance (ADS) application:
The function of the ADS application is to provide the ATC ground center with aircraft surveillance data through the periodic, event or on-demand reports.

(11) ATSU FANS B applications software
The different Air Traffic Control (ATC) applications contained in this package are:

(a) Context Management Application (CMA)
The CMA provides the necessary information to enable data-link communication between Air Traffic Service (ATS) units and aircraft systems. This function will typically be initiated when an aircraft is either at the gate in the pre-departure phase of flight, or before entering a new FIR supporting data-link communications.
The CMA supports the Data-Link Initiation Capability (DLIC) ATS.

(b) Controller-Pilot DataLink Communications (CPDLC) application
The aim of this application is to provide dialog between ground controllers and flight crews, using datalink instead of voice communications.
Each CPDLC message comprises a set of message elements which correspond to the existing phraseology used by current ATC procedures.

D. Description of the Datalink Control and Display Units (DCDU)

The DCDUs are the interface means dedicated to the ATC applications. They provide the flight crew with display capabilities and control means. This allows the display of messages received from ATC ground center and the sending of answer and messages to the ground center. The DCDUs are managed by the ATSU which processes and organizes the data in screen pages to be displayed, and translates received key codes into crew orders (soft keys).

E. Description of the ATC MSG Illuminated Pushbutton-Switches

These pushbutton switches provide the flight crew with a visual alert in case of ATC message reception and with an alert cancel means when pressed.
In addition, the FWCs trigger an aural alert according to the priority of the message (single or repetitive chime sounds).

F. MCDU Use

The air/ground communication-management function is accessed through the MCDU.

The MCDU provides the crew with the functions that follow:

For the air/ground communication management:
. Configuration/initialization
. VHF3, SATCOM (optional) and HF (optional) control
. Communication statistics display
. Test/audit mode control

The pages managed by the ATSU are independently accessible from the two MCDUs and are accessible in parallel on the two MCDUs: access to and exit from the MCDU pages are independent on these MCDUs.

NOTE: If a third MCDU is installed, only two MCDUs out of the three can be used simultaneously by the ATSU.

For the ATC applications in the FANS A configuration:
. Preparation and modificaton of all the messages initiated by the crew
. Justification to the negative replies or to a particular request
. Text editing
. Configuration of the applications (ADS activation, AFN initialization)
. Configuration of the systems (ATSU management, automatic or on-request printing).

for ATC applications in FANS B configuration:
. preparation and modificaton of all the messages initiated by the crew,
. justifications to negative replies or to a particular request,
. configuration of applications (CMA initialization) and
. configuration of systems (ATSU management, automatic or on-request printing).

G. FWC Use
The ATSU uses the services provided by the FWCs to activate the visual/aural alerts and warnings for the different applications.

(1) Air/Ground communication warnings:
The air/ground communication warnings are generated by the FWCs according to the information provided by the ATSU and the communication peripherals:

Internal ATSU failure
Datalink status (failure or unavailability)
Communication system failure or unavailability.

They are inhibited during some flight phases according to the priority level.

(2) Air/Ground communication limitations:
The limitations are displayed to the crew to indicate the availability of the communication sub-networks. In case of unavailability, the procedure is to return to VOICE mode.

H. Printer Use

(1) Air/ground communication function:
The air/ground communication-management function uses the services of the printer for the below purposes:

Automatic print out of a message directed to the printer (label C1)
MCDU screen hard copy
Statistics reports
Audit information
Company-call message print.

In case of ground messages directed to the printer (label C1), the ATSU can reject the uplink message, if the printer is unavailable. The UPLINK REJECT message (label Hx) is sent to the ground to indicate that the printer is failed. The PRT MSG PRINT FAIL message is also displayed on the MCDU scratchpad.
Even if the printer is busy, the print request is accepted by the ATSU and the ATSU buffers the data, waiting for the printer availability.

I. 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 request a switching of the system between the RMP and the ATSU. It controls the VDR3 frequency by pressing the transfer pushbutton switch located between the two windows:

When the frequency is displayed in the ACTIVE window of the RMP, the RMP controls the VDR3 frequency.
VDR3 is in voice mode is available and the selection of the VDR3 frequency is done through the RMP.
When the ACARS indication is displayed in the ACTIVE window of the RMP instead of the frequency, the ATSU controls the VDR3 frequency.
VDR3 is in data or voice mode.

NOTE: The RMP sends the pilot request of switching the system controlling the VDR3 (between the RMP and the ATSU) to the ATSU. In return, the ATSU indicates the RMP which system between the RMP and the ATSU is controlling the VDR3 frequency.

** ON A/C NOT FOR ALL

4. Power Supply

ATIMS - Power Supply ** ON A/C NOT FOR ALL

The ATIMS system is supplied with the circuit breaker(s) that follows.

A. Circuit Breaker(s) Table

PANEL	DESIGNATION	FIN	LOCATION
** ON A/C NOT FOR ALL
121VU	ATSU 1	3TX1	L16
** ON A/C NOT FOR ALL
121VU	ATSU 1	3TX1	K43
** ON A/C NOT FOR ALL
121VU	ATSU 1/SWTG	5TX1	L15
** ON A/C NOT FOR ALL
121VU	ATSU 1/SWTG	5TX1	K42
** ON A/C NOT FOR ALL
121VU	DCDU 1	6TX1	L17
** ON A/C NOT FOR ALL
121VU	DCDU 1	6TX1	L17
** ON A/C NOT FOR ALL
121VU	DCDU 1	6TX1	K44
** ON A/C NOT FOR ALL
121VU	DCDU 2	6TX2	L18
** ON A/C NOT FOR ALL
121VU	DCDU 2	6TX2	L18
** ON A/C NOT FOR ALL
121VU	DCDU 2	6TX2	K45

B. ATSU
The ATSU is supplied with 115VAC from the main 115VAC BUS1 bar 101XP-C through circuit breaker 3TX1 and 28VDC from the main 28VDC BUS1 bar 101PP through circuit breaker 5TX1.

C. DCDU
DCDU1 is supplied with 28VDC from the main 28VDC BUS1 bar 103PP through circuit breaker 6TX1.
The DCDU2 is supplied with 28VDC from the main 28VDC BUS1 bar 202PP through circuit breaker 6TX2.

** ON A/C NOT FOR ALL

5. Interface

A. General

ATIMS - System Architecture ** ON A/C NOT FOR ALL

The ATSU uses the data transparent protocol, defined in ARINC 429 Specification, when it communicates with the on-board avionics systems.
The ATSU is interfaced with the following peripheral units:

the Flight Management and Guidance Computer 1 and 2 (FMGC) (Ref. AMM 22-83-00)
the Multipurpose Control and Display Unit 1 and 2 (MCDU) (Ref. AMM 22-82-00)
the VHF Data Radio 3 (VDR3) transceiver (Ref. AMM 23-12-00)
the Satellite Data Unit (SDU) (Ref. AMM 23-28-00)
the Cabin Terminals: the Cabin Management System (Ref. AMM 23-74-00) and the Digital Interface Unit (Ref. AMM 23-34-00)
the Radio Management Panels 1, 2 and 3 (RMP) (Ref. AMM 23-81-00)
the Clock (Ref. AMM 31-21-00)
the Data Management Unit (DMU) (Ref. AMM 31-36-00)
the Flight Warning Computer 1 and 2 (FWC) (Ref. AMM 31-52-00)
the System Data Acquisition Concentrator 1 and 2 (SDAC) (Ref. AMM 31-54-00)
the Display Management Computer 1, 2 and 3 (DMC) (Ref. AMM 31-62-00)
the Centralized Fault Display Interface Unit (CFDIU) (Ref. AMM 31-32-00)
the Multipurpose Disk Drive Unit (MDDU) (Ref. AMM 31-38-00)
the printer (Ref. AMM 31-35-00)

ATIMS - System Architecture ** ON A/C NOT FOR ALL

The ATSU uses the data transparent protocol defined in the ARINC 429 specification when it communicates with the onboard avionics systems.
The ATSU is interfaced with the peripheral units that follow:

FMGC1 and FMGC2 (Ref. AMM 22-83-00)
MCDU1 and MCDU2 (Ref. AMM 22-82-00)
VDR3 transceiver (Ref. AMM 23-12-00)
Satellite Data Unit (SDU) (Ref. AMM 23-28-00)
High Frequency Data Radio (HFDR) 1 transceiver (Ref. AMM 23-11-00)
Cabin Terminals: Cabin Management System (Ref. AMM 23-74-00) and the Digital Interface Unit (DIU) (Ref. AMM 23-34-00)
RMP1, RMP2 and RMP3 (Ref. AMM 23-81-00)
Clock (Ref. AMM 31-21-00)
DMU (Ref. AMM 31-36-00)
FWC1 and FWC2 (Ref. AMM 31-52-00)
SDAC1 and SDAC2 (Ref. AMM 31-54-00)
Display Management Computer (DMC) 1, 2 and 3 (Ref. AMM 31-62-00)
CFDIU (Ref. AMM 31-32-00)
MDDU (Ref. AMM 31-38-00)
Printer (Ref. AMM 31-35-00)
Multi-Mode Receiver (MMR) 2 (Ref. AMM 34-36-00) or the Global Positioning System Sensor Unit (GPSSU) 2 (Ref. AMM 34-58-00)
ATC transponders (Ref. AMM 34-52-00)

ATIMS - System Architecture ** ON A/C NOT FOR ALL

The ATSU uses the data transparent protocol, defined in ARINC 429 Specification, when it communicates with the on-board avionics systems.
The ATSU is interfaced with the following peripheral units:

the Flight Management and Guidance Computer 1 and 2 (FMGC) (Ref. AMM 22-83-00)
the Multipurpose Control and Display Unit 1 and 2 (MCDU) (Ref. AMM 22-82-00)
the VHF Data Radio 3 (VDR3) transceiver (Ref. AMM 23-12-00)
the Satellite Data Unit (SDU) (Ref. AMM 23-28-00)
the High Frequency Data Radio 1 (HFDR1) transceiver (Ref. AMM 23-11-00)
the Cabin Terminals: the Cabin Management System (Ref. AMM 23-74-00) and the Digital Interface Unit (Ref. AMM 23-34-00)
the Radio Management Panels 1, 2 and 3 (RMP) (Ref. AMM 23-81-00)
the Clock (Ref. AMM 31-21-00)
the Data Management Unit (DMU) (Ref. AMM 31-36-00)
the Flight Warning Computer 1 and 2 (FWC) (Ref. AMM 31-52-00)
the System Data Acquisition Concentrator 1 and 2 (SDAC) (Ref. AMM 31-54-00)
the Display Management Computer 1, 2 and 3 (DMC) (Ref. AMM 31-62-00)
the Centralized Fault Display Interface Unit (CFDIU) (Ref. AMM 31-32-00)
the Printer (Ref. AMM 31-35-00)
the MMR2 (Ref. AMM 34-36-00) or the GPSSU2 (Ref. AMM 34-58-00)
the ATC transponders (Ref. AMM 34-52-00)

B. DCDU/ATSU Interface

(1) Digital and discrete inputs/outputs:

---------------------------------------------------------------------

! INTERFACE SERVICES ! TRANSMISSION MEANS ! COMMENTS !

---------------------------------------------------------------------

! Initialization ! ATSU -> DCDU1 ! ARINC 429 !

! ! SYS1 ! !

! ! ATSU -> DCDU2 ! !

! ! SYS2 ! !

! ! DCDU1 -> ATSU DCDU ! !

! ! GEN/1 ! !

! ! DCDU2 -> ATSU DCDU ! !

! ! GEN/2 ! !

---------------------------------------------------------------------

! Display ! ATSU -> DCDU1 ! ARINC 429 !

! ! SYS1 ! !

! ! ATSU -> DCDU2 ! !

! ! SYS2 ! !

! ! DCDU1 -> ATSU DCDU ! !

! ! GEN/1 ! !

! ! DCDU2 -> ATSU DCDU ! !

! ! GEN/2 ! !

---------------------------------------------------------------------

! Recall ! DCDU1 -> ATSU DCDU ! Label 272 !

! ! GEN/1 ! bits 11 -> 18 !

! ! DCDU2 -> ATSU DCDU ! !

! ! GEN/2 ! !

---------------------------------------------------------------------

! Response ! DCDU1 -> ATSU DCDU ! Label 272 !

! ! GEN/1 ! bits 11 -> 18 !

! ! DCDU2 -> ATSU DCDU ! bits 22 -> 26 !

! ! GEN/2 ! !

---------------------------------------------------------------------

! Display test demand ! ATSU -> DCDU1 ! Label 271 !

! ! SYS1 ! bits 16 -> 18 !

! ! ATSU -> DCDU2 ! !

! ! SYS2 ! !

! Display test in progress ! DCDU1 -> ATSU DCDU ! Label 155 !

! ! GEN/1 ! bit 28 !

! ! DCDU2 -> ATSU DCDU ! !

! ! GEN/2 ! !

---------------------------------------------------------------------

! Self test demand ! ATSU -> DCDU1 ! Label 271 !

! ! SYS1 ! bits 19 !

! ! ATSU -> DCDU2 ! !

! ! SYS2 ! !

! Self test in progress ! DCDU1 -> ATSU DCDU ! Label 155 !

! ! GEN/1 ! bit 27 !

! ! DCDU2 -> ATSU DCDU ! !

! ! GEN/2 ! !

---------------------------------------------------------------------

! Error report ! DCDU1 -> ATSU DCDU ! Labels 156/157 !

! ! GEN/1 ! bits 11 -> 24 !

! ! DCDU2 -> ATSU DCDU ! Labels 156/157 !

! ! GEN/2 ! bits 25 -> 28 !

---------------------------------------------------------------------

! Status report ! DCDU1 -> ATSU DCDU ! Label 155 !

! DCDU internal faults ! GEN/1 ! bits 16 -> 25 !

! ! DCDU2 -> ATSU DCDU ! bit 29 !

! ! GEN/2 ! !

---------------------------------------------------------------------

! Line Replaceable Unit ! DCDU1 -> ATSU DCDU ! Labels 354 !

! (LRU) identification ! GEN/1 ! !

! Part Number (P/N) ! DCDU2 -> ATSU DCDU ! !

! GEN/2 ! !

---------------------------------------------------------------------

(2) ATSU/DCDU interface
This interface fulfills the functions that follow:

Display function
Recall function
Flight crew response
BITE test
Report function
LRU identification
Communication protocol in the initialization function.

(a) Display function
This function enables the DCDUs to provide the flight crew with the information related to the ATC applications.
This information is displayed screen by screen on the DCDUs with the required frame.

(b) Recall function
This function enables the DCDU to receive again all the information related to the last display.

(c) Response function
This function enables the DCDUs to transmit the flight crew order to the ATSU generated by pushing the keys located on the DCDU front face, except for the BRT/DIM keys.

(d) Test function
This function enables to display the DCDU test or the self test when the aircraft is on ground.

(e) Report function
This function enables to provide the ATSU with the BITE memory data concerns the specific events which do not occur in normal operation:

Error reports when a problem occurs during the transmission of information between the ATSU and the DCDU for maintenance purpose.
Status reports when the internal faults are detected in the DCDU.

(f) LRU identification function
This function enables the ATSU to get the part number and the serial number of the DCDUs.

(g) Initialization function
This function enables to inform the ATSU that the data transmission protocol has been initialized or reinitialized (after the ATSU power up or reset, after the DCDU reset or after the consecutive transmission errors).

(h) Data transmission protocol
The ATSU transmits the display information to the DCDU through the ARINC 429 high-speed bus, using the bit-oriented communication protocol as defined in the ARINC 429 specifications.

C. AFS/ATIMS Interface

(1) General
The ATSU is interfaced with both FMGCs and the three MCDUs of the Automatic Flight System (AFS) (the third MCDU is optional) for:

The AOC hosted application to acquire the operational data (origin/destination airport, flight number, fuel on board, etc.). These parameters are processed and then inserted in some downlink reports to enable:
. The AOC menu selection
. The display of specific AOC information (AOC received messages, scratchpad messages, etc.)
. The parameters entry by the crew (captain name, fuel units, etc.).
The remote AOC application to exchange the AOC messages. Effectively, the FMGCs integrate a remote AOC application and the ATSU acts like a router in this case.
The air/ground communication functions to enable the display of specific router information, crew request and parameters entry (flight number, Flight Management System (FMS) master/slave, etc.).
The system management and configuration to exchange the status and configuration between the ATSU and FMGCs.

(2) FMGC/ATSU interface
This interface supports the broadcasted data exchange on its buses.

(3) FMGC/ATSU interface - Identification
The identification of the master/slave FMGC for the communication and guidance.
Both the FMGCs operate simultaneously.
One of them is in charge of communication with the ground, the other one is in charge of the guidance (the ATSU acquires the navigation data from this FMGC).
The ATSU determines which FMGC is the communication master and which FMGC is the guidance master.
If no specific FMGC is required by the ground, the ATSU sends the uplink data to the communication master FMGC and gets back the downlink messages from this FMGC.
If the ground requires a specific FMGC, uplink data are sent to the required FMGC.

(4) FMGC/ATSU interface - Status of the datalink communication
The ATSU and both the FMGCs exchange status information (status of the communication with the ground and between the ATSU and the FMGCs) in order to determine the availability of the datalink communication.

(5) FMGC/ATSU interface - Periodic data
These data are mainly navigation data and are used by a hosted AOC application.
The ATSU/FMGC interface supports the exchange with ARINC 429 Williamsburgh Protocol. These exchanges concern ARINC 619 messages related to the remote AOC application hosted in the FMGC. These messages are the FMGC downlink reports or the uplink requests.

The used System Address Labels (SAL) are:

FMGC1 SAL is 300
FMGC2 SAL is 301
ATSU SAL is 304.

(6) FMGC/ATSU interface - Flight number
This parameter is sent by the FMGC to the ATSU.

(7) FMGC/ATSU interface - Pin Programming (PIN PROG)
The configuration of the ATSU/FMGC interface is done through the two PIN PROG in the FMGC:

PIN PROG 'Mini ACARS': only the broadcast data are transmitted from the FMGC to the ATSU.
PIN PROG 'Full ACARS': broadcast data are transmitted from the FMGC to the ATSU and AOC messages are exchanged between the ATSU and the FMGC.

NOTE: The airline policy file with the ACARS options is contained in the FMS navigation data-base.

NOTE: Activation of printer interface in the FMS is mandatory for 'Full ACARS' configuration, to avoid the display of "FMS INOP" message on the MCDU.

(8) FMGC/ATSU interface - PIN PROG indication
The FMGC supports a PIN PROG indicating which equipment is installed: the ACARS Management Unit (MU) or the ATSU.
The FMGC determines the ATSU is functioning onboard and that the ATSU interface is to be taken into account.

(9) MCDU/ATSU interface
The ATSU interfaces with the three MCDUs (the third MCDU is optional), but it can only interface with two of them simultaneously.
The MCDUs have a standard interface for different onboard systems.

(a) MCDU status
Each MCDU sends its status to the ATSU and the ATSU determines if the MCDU is available or not (before it sends a page for display).

(b) Connection to the MCDU
The ATSU sends its SAL to the MCDUs for the to make the connection.

(d) Keys selection
The ATSU acquires the information from the MCDUs about the MCDU key the pilot has selected.
The used SALs are:

MCDU1 SAL is 220
MCDU2 SAL is 221
MCDU3 SAL is 222
ATSU SAL is 304.

D. Communication/ATIMS Interface

The ATIMS has the interface with:

VDR3 for the VHF data communications and the .VHF voice/data mode control
Satellite Data Unit (SDU) 1 for the satellite data communications
RMP 1/2/3 for the VDR3 voice/data mode switching.

A PIN PROG received from the SDAC enables the ATSU to determine if the HFDR1 is installed or not.

The ATIMS is interfaced with:

VDR3 for VHF data communication and VHF voice/data mode control
SDU1 for satellite data communication
HFDR1 for HF data communication
RMP 1/2/3 for VDR3 voice/data mode switching
ATC transponders for the International Civil Aviation Organization (ICAO) code.

A pin-programming received from the SDAC enables the ATSU to determine if HFDR1 is installed or not.

The ATIMS is interfaced with:

VDR3 for VHF data communications and VHF voice/data mode control
SDU1 for satellite data communications
HFDR1 for HF data communications
RMP 1/2/3 for VDR3 voice/data mode switching
ATC transponders for the International Civil Aviation Organization (ICAO) code.

A pin-programming received from the SDAC enables the ATSU to determine if the HFDR1 is installed or not.

(1) VDR3/ATIMS interface
This interface is in accordance with the ARINC 750 specifications.
The ATSU uses the services provided by VDR3 to communicate with the ground in data or voice mode.
The two output discrete signals from the ATSU are used to control:

The VDR3 switching between the voice and data mode: voice/data select discrete
The VDR3 frequency selection (port A for ATSU, Port B for RMP): port select discrete

The broadcast data are sent on output bus SYS5 of the ATSU to the VDR3 port A for the VDR3 frequency selection.
The ATSU COM2 and VDR/3 buses support:

The VDR3 status transmission to the ATSU (voice/data mode, failure...)
The ATSU status transmission to VDR3 (primary source/destination, failure...)
The VDR3 configuration and control by the ATSU
ARINC 618 downlink and uplink block exchanges.

(a) Functional split
The functional split between ATSU and VDR3 is as follows:

In Voice mode
The ATSU controls the VDR3 switching between data and voice mode.
In Data mode

1 The ATSU configures VDR3 in the appropriate protocol.

2 The ATSU sends the ARINC 618 messages in the digital format to VDR3.

3 VDR3 adds the VHF protocol overhead and performs the modulation operation on the VHF signal.

4 VDR3 demodulates the received VHF signal, eliminates the VHF overhead and sends the received messages to the ATSU in the digital format.

5 The ATSU controls the VHF operational parameters of VDR3 (frequency...).

When the ATSU transmits the ARINC 618 blocks to VDR3, it waits for the effective transmission to the ground before transmitting other ones.
In case the transmission is not completed by VDR3, the ATSU sends a 'purge down-link' command to clear the failed VDR3 downlink transmission.
The used SALs are:

VDR3 SAL is 253
ATSU SAL is 304.

(2) Satellite Communication (SATCOM)/ATIMS interface
The broadcast data are sent on the output bus SYS5 of the ATSU to the SDU1.
The ATSU COM1 and SDU1 buses support:

SDU1 status transmission to the ATSU
ATSU status transmission to the SDU1 (primary source/destination, failure...)
ARINC 618 downlink and uplink blocks exchanges.

The protocols used on these buses are ARINC 429, ARINC 618 and ARINC 741.
When the ATSU transmits ARINC 618 blocks to the SDU1, it waits for the effective transmission to the ground before transmitting other ones. In case the transmission is not completed by the SDU1, the ATSU sends a 'purge down-link' command to clear the failed SDU1 downlink transmission.
The used SALs are:

SDU1 SAL is 307
ATSU SAL is 304.

(3) RMP /ATIMS interface

ATIMS - Switching Request to Data Mode from the RMP ** ON A/C NOT FOR ALL

ATIMS - Switching Request to Voice Mode from the RMP ** ON A/C NOT FOR ALL

The ATSU indicates to the RMPs which system between the ATSU and the RMP is controlling the frequency by means of the port select discrete.
The ATSU acquires the remote port-select discrete from each of the three RMPs to transmit the pilot request of switching the system controlling the VDR3 frequency.
When a switching request is issued, the ATSU activates the VHF voice-mode function. It determines, which system between the ATSU and the RMP will control the VDR3 frequency and in which mode.

(4) VDR3/ATIMS interface:
This interface is in accordance with the ARINC 750 specifications.
The ATSU uses the services provided by VDR3 to communicate with the ground in data/voice mode.
The two output discrete signals from the ATSU are used to control:

VDR3 switching between voice and data mode: voice/data select discrete
VDR3 frequency selection port A for the ATSU and port B for the RMP): port select discrete

The broadcast data are sent on the output bus SYS5 of the ATSU to the VDR3 port A for the VDR3 frequency selection.
The ATSU COM2 and VDR/3 buses support:

The VDR3 status transmission to the ATSU (voice/data mode, failure, etc.)
The ATSU status transmission to the VDR3 (primary source/destination, failure, etc.)
The VDR3 configuration and control by the ATSU
ARINC 618 downlink and uplink block exchanges.

(a) Functional split:
The functional split between the ATSU and VDR3 is as follows:

In voice mode:
The ATSU controls the VDR3 switching between data and voice mode.
In data mode:

1 The ATSU configures VDR3 in the appropriate protocol.

2 The ATSU sends the ARINC 618 messages in the digital format to VDR3.

3 VDR3 adds the VHF protocol overhead and performs the modulation operation on the VHF signal.

4 VDR3 demodulates the received VHF signal, eliminates the VHF overhead and sends the received messages to the ATSU in the digital format.

5 The ATSU controls the VHF operational parameters of VDR3.

When the ATSU transmits the ARINC 618 blocks to VDR3, it waits for the effective transmission to the ground before transmitting other ones.
In case the transmission is not completed by VDR3, the ATSU sends a 'purge down-link' command to clear the failed VDR3 downlink transmission.
The used SALs are:

VDR3 SAL is 253
ATSU SAL is 304.

(5) Satellite Communication (SATCOM)/ATIMS interface:
The broadcast data are sent on the output bus SYS5 of the ATSU to SDU1.
The ATSU COM1 and SDU1 buses support:

SDU1 status transmission to the ATSU
ATSU status transmission to the SDU1 (primary source/destination, failure, etc.)
ARINC 618 downlink and uplink block exchanges.

The protocols used on these buses are ARINC 429, ARINC 618 and ARINC 741.
When the ATSU transmits ARINC 618 blocks to SDU1, it waits for the effective transmission to the ground before transmitting other ones. In case the transmission is not completed by SDU1, the ATSU sends a 'purge down-link' command to clear the failed SDU1 downlink transmission.
The SALs are:

SDU1 SAL is 307
ATSU SAL is 304.

(6) High Frequency Data Radio (HFDR)/ATIMS interface:
The ATSU uses the services provided by HFDR1 to communicate with the ground in data mode.
The ATSU COM2 and HFDR1 buses support:

The HFDR1 status transmission to the ATSU
The ATSU status transmission to HFDR1 (primary source/destination, failure, etc.)
ARINC 618 downlink and uplink blocks exchanges.

When the ATSU transmits ARINC 618 blocks to HFDR1, it waits for the effective transmission to the ground before transmitting other ones. In case the transmission is not completed by HFDR1, the ATSU sends a 'purge down-link' command to clear the failed HFDR1 downlink transmission.
The used SALs are:

HFDR1 SAL is 340
ATSU SAL is 304.

(7) RMP /ATIMS interface:

ATIMS - Switching Request to Data Mode from the RMP ** ON A/C NOT FOR ALL

ATIMS - Switching Request to Voice Mode from the RMP ** ON A/C NOT FOR ALL

The ATSU indicates the RMPs which system between the ATSU and the RMP is controlling the frequency by means of the port select discrete.
The ATSU acquires the remote port-select discrete from each of the three RMPs. It is used to transmit the pilot request of switching the system controlling the VDR3 frequency.
When a switching request is issued, the ATSU activates the VHF voice mode function. It determines which system between the ATSU and the RMP will control the VDR3 frequency and in which mode.

(8) ATC transponders/ATIMS interface
The ATSU uses the ICAO code (24 bit address) sent by the ATC transponders for the VDL2 function.
The ICAO code is first extracted from ATC transponder 1 and then from ATC transponder 2 if ATC transponder 1 is not available.

(9) VDR3/ATIMS interface
This interface is in accordance with ARINC 750 specifications.
The ATSU uses the services provided by the VDR3 to communicate with the ground in DATA or VOICE mode.
Two output discrete signals from the ATSU are used to control:

VDR3 switching between voice and data mode: voice/data select discrete
VDR3 frequency selection (Port A for ATSU, Port B for RMP): port select discrete

Broadcast data are sent on output bus SYS5 of the ATSU to the VDR3 port A for VDR3 frequency selection.
The ATSU COM2 and VDR/3 buses support:

VDR3 status transmission to the ATSU (voice/data mode, failure...)
ATSU status transmission to the VDR3 (primary source/destination, failure...)
VDR3 configuration and control by the ATSU
ARINC 618 downlink and uplink block exchanges.
X25 downlink/uplink packets (for ATN traffic)

(a) Functional split
The functional split between ATSU and VDR3 is the following:

in Voice mode
The ATSU controls the VDR3 switching between data and voice mode.
in Data mode

1 The ATSU configures the VDR3 in the appropriate protocol

2 The ATSU sends messages in digital format to the VDR3

3 The VDR3 adds the VHF protocol overhead and performs the modulation operation on the VHF signal

4 The VDR3 demodulates the received VHF signal, eliminates the VHF overhead and sends the received messages to the ATSU in digital format.

5 The ATSU controls the VHF operational parameters of the VDR3 (frequency...).

Only in ACARS transmission, when the ATSU transmits ARINC 618 blocks to the VDR3, it waits for the effective transmission to the ground before transmitting other ones.
In case where the transmission is not completed by the VDR3, the ATSU sends a 'purge down-link' command, in order to clear the failed VDR3 downlink transmission.
The used System Address Labels (SAL) are:

VDR3 SAL is 253
ATSU SAL is 304.

(10) Satcom/ATIMS interface
Broadcast data are sent on output bus SYS5 of the ATSU to the SDU1.
The ATSU COM1 and SDU1 buses support:

SDU1 status transmission to the ATSU
ATSU status transmission to te SDU1 (primary source/destination, failure...)
ARINC 618 downlink and uplink blocks exchanges.

The protocols used on these buses are ARINC 429, ARINC 618 and ARINC 741.
When the ATSU transmits ARINC 618 blocks to the SDU1, it waits for the effective transmission to the ground before transmitting other ones. In case where the transmission is not completed by the SDU1, the ATSU sends a 'purge down-link' command, in order to clear the failed SDU1 downlink transmission.
The used System Address Labels (SAL) are:

SDU1 SAL is 307
ATSU SAL is 304.

(11) HFDR/ATIMS interface
The ATSU uses the services providedby the HFDR1 to communicate with the ground in data mode.
The ATSU COM2 and HFDR1 buses support:

HFDR1 status transmission to the ATSU
ATSU status transmission to the HFDR1 (primary source/destination, failure,...)
ARINC 618 downlink and uplink blocks exchanges.

When the ATSU transmits ARINC 618 blocks to the HFDR1, it waits for the effective transmission to the ground before transmitting other ones. In case where the transmission is not completed by the HFDR1, the ATSU sends a 'purge down-link' command, in order to clear the failed HFDR1 downlink transmission.
The used System Address Labels (SAL) are:

HFDR1 SAL is 340
ATSU SAL is 304.

(12) RMP /ATIMS interface

ATIMS - Switching Request to Data Mode from the RMP ** ON A/C NOT FOR ALL

ATIMS - Switching Request to Voice Mode from the RMP ** ON A/C NOT FOR ALL

The ATSU indicates to the RMPs which system between the ATSU and the RMP is controlling the frequency by means of the port select discrete.
The ATSU acquires the remote port select discrete from each of the three RMPs to transmit the pilot request of switching the system controlling the VDR3 frequency.
When a switching request is issued, the ATSU activates the VHF voice mode function to determine which system between the ATSU and the RMP will control the VDR3 frequency and in which mode.

(13) ATC Transponders/ATIMS Interface
The ATSU uses for the VDL2 function the ICAO code (24 bit address) sent by the ATC transponders.
The ICAO code is first extracted from the ATC transponder 1 and then from the ATC transponder 2 if the ATC transponder 1 is not available.

E. Interface with the Ground Network

(1) Ground network architecture

ATIMS - Ground Network World Map ** ON A/C NOT FOR ALL

The airline can exchange the data with its aircraft through a ground network which is managed by the world service providers that follows:

ARINC AFRICA

ARINC AMERICA

ARINC ASIA

ARINC EUROPE

ARINC KOREA

AVICOM

DEPV BRAZIL

SITA EUROPE

SITA LATIN AMERICA

SITA NORTH AMERICA

SITA PACIFIC

In this ground network, each service provider is responsible for its own network.
The networks are interconnected, therefore the data is transferred over any network.
The aircraft is linked with the network through the VHF.
On the ground, each service provider works on a special frequency:

-------------------------------------------------------------------------

! ABBREVIATION ! SERVICE PROVIDER ! MCDU LABEL ! FREQUENCY ! FAMILY !

-------------------------------------------------------------------------

! AF ! ARINC AFRICA ! ARI-AFR ! 126.900 MHz ! ARINC !

! AM ! ARINC AMERICA ! ARI-AM ! 131.550 MHz ! ARINC !

! AS ! ARINC ASIA ! ARI-ASI ! 131.450 MHz ! ARINC !

! AE ! ARINC EUROPE ! ARI-EUR ! 136.925 MHz ! ARINC !

! AK ! ARINC KOREA ! ARI-KOR ! 131.725 MHz ! ARINC !

! AV ! AVICOM ! AVICOM ! 131.450 MHz ! SITA !

! DE ! DEPV BRAZIL ! DEPV ! 131.550 MHz ! SITA !

! SE ! SITA EUROPE ! SITA-E/A ! 131.725 MHz ! SITA !

! SL ! SITA LATIN AMERICA ! SITA-LAM ! 131.725 MHz ! SITA !

! SN ! SITA NORTH AMERICA ! SITA-NAM ! 136.850 MHz ! SITA !

! SP ! SITA PACIFIC ! SITA-PAC ! 131.550 MHz ! SITA !

---------------------------------------------------------------------------

(2) Data exchange between aircraft and ground network

ATIMS - ISO Alphabet No. 5 ** ON A/C NOT FOR ALL

(a) Data coding
The signal transmitted by the ATSU to VHF3 is modulated with the VHF radio signal and then, sent to the ground. Conversely, the signal transmitted by VHF3 to the ATSU is obtained after demodulation of the radio signal from the ground.
The transmitted data are characters from the ISO alphabet no.5 except the block-check sequence field at the end of transmission.

(b) Message format
The format of the messages exchanged between the ground and the aircraft is as follows (in the transmission order):

Start of heading (1 character)

Mode (1 character)

Address (7 characters)

Technical acknowledgement (1 character)

Label (2 characters)

Uplink block identifier (1 character)

Downlink block identifier (1 character)

Start of text (1 character)

Text (220 characters max)

Suffix (1 character)

Block check sequence (2 characters)

Block-check sequence suffix (1 character)

Start of heading:
It indicates the start of data transmission.
Mode:
It enables the selection of a ground station or a specific group of ground stations for the communication with aircraft.
Address:
It contains the identification of the aircraft which transmits or receives the message.
Technical acknowledgement:
It is an acknowledgement (either positive or negative) related to the last message received.
Label:
It identifies a specific type of message.
Uplink block identifier:
It appears only in the messages transmitted by the ground. It enables the aircraft to detect the duplicated ground messages (aircraft-to-ground messages may have a downlink block identifier to enable detection of duplicated aircraft messages on the ground).
Downlink block identifier:
It appears only in the message transmitted by the aircraft. It enables the ground to detect duplicated messages.
Start of text:
It indicates the start of the useful data transmission.
Text:
It is an useful data. Only one part of the ISO alphabet no.5 characters can be transmitted in this field.
Suffix:
It indicates the end of useful data transmission.
Block check sequence:
It is the result of a computation made before transmission on the previous bit set. At reception, the same computation is made and the two results are compared. If they are identical, the transmission is correct.

(3) Ground network architecture

ATIMS - Ground Network World Map ** ON A/C NOT FOR ALL

The airline can exchange data with its aircraft through a ground network which is managed by the following world service providers:

ARINC AFRICA

ARINC AMERICA

ARINC ASIA

ARINC EUROPE

ARINC KOREA

AVICOM

DEPV BRAZIL

SITA EUROPE

SITA LATIN AMERICA

SITA NORTH AMERICA

SITA PACIFIC

In this ground network, each service provider is responsible for its own network.
The networks are interconnected, therefore the data is transferred over any network.
The aircraft is in liaison with the network through the VHF.
On the ground, each service provider works on a special frequency:

-------------------------------------------------------------------------

! ABBREVIATION ! SERVICE PROVIDER ! MCDU LABEL ! FREQUENCY ! FAMILY !

-------------------------------------------------------------------------

! AF ! ARINC AFRICA ! ARI-AFR ! 126.900 MHz ! ARINC !

! AM ! ARINC AMERICA ! ARI-AM ! 131.550 MHz ! ARINC !

! AS ! ARINC ASIA ! ARI-ASI ! 131.450 MHz ! ARINC !

! AE ! ARINC EUROPE ! ARI-EUR ! 136.925 MHz ! ARINC !

! AK ! ARINC KOREA ! ARI-KOR ! 131.725 MHz ! ARINC !

! AV ! AVICOM ! AVICOM ! 131.450 MHz ! SITA !

! DE ! DEPV BRAZIL ! DEPV ! 131.550 MHz ! SITA !

! SE ! SITA EUROPE ! SITA-E/A ! 131.725 MHz ! SITA !

! SL ! SITA LATIN AMERICA ! SITA-LAM ! 131.725 MHz ! SITA !

! SN ! SITA NORTH AMERICA ! SITA-NAM ! 136.850 MHz ! SITA !

! SP ! SITA PACIFIC ! SITA-PAC ! 131.550 MHz ! SITA !

---------------------------------------------------------------------------

(4) Data exchange between aircraft and ground network

ATIMS - ISO Alphabet No. 5 ** ON A/C NOT FOR ALL

(a) Data coding
The signal transmitted by the ATSU to the VHF 3 is modulated with the VHF radio signal and then, sent to the ground. Conversely, the signal transmitted by the VHF 3 to the ATSU is obtained after demodulation of the radio signal from the ground.
The transmitted data are characters from the ISO alphabet No.5 except the block check sequence field at the end of transmission.

(b) ACARS Message format
The format of the messages exchanged between the ground and the aircraft is as follows (in the transmission order):

Start of heading (1 character)

Mode (1 character)

Address (7 characters)

Technical acknowledgement (1 character)

Label (2 characters)

Uplink block identifier (1 character)

Downlink block identifier (1 character)

Start of text (1 character)

Text (220 characters max)

Suffix (1 character)

Block check sequence (BCS) (2 characters)

BCS suffix (1 character)

Start of heading:
indicates the start of data transmission.
Mode:
enables selection of a ground station or a specific group of ground stations for communication with the aircraft.
Address:
contains the identification of the aircraft which transmits or receives the message.
Technical acknowledgement:
acknowledgement (either positive or negative) related to the last message received.
Label:
identifies a specific type of message.
Uplink block identifier:
only appears in the messages transmitted by the ground. Enables the aircraft to detect duplicated ground messages (aircraft-to-ground messages may have a downlink block identifier to enable detection of duplicated aircraft messages on the ground).
Downlink block identifier:
only appears in the message transmitted by the aircraft. Enables the ground to detect duplicated messages.
Start of text:
indicates the start of useful data transmission.
Text:
useful data. Only one part of the ISO 5 characters can be transmitted in this field.
Suffix:
indicates the end of useful data transmission.
Block check sequence:
result of a computation made before transmission on the previous bit set. At reception, the same computation is made and the two results are compared. If they are identical, the transmission is correct.

(c) ATN protocol communication
The messages exchanged are in a binary format according to the ATN protocol (ATN SARPS doc. 9705).

F. Indicating and Recording Systems /ATIMS Interface
The ATIMS has interface with different sub-systems of the indicating and recording systems:

Flight Warning System (FWS) (Flight Warning Computer (FWC)/SDAC)
Electronic Instrument System (EIS) (DMC)
Clock
Aircraft Integrated Data System (AIDS) (DMU)
CFDS (CFDIU, Printer)
DLS

(1) ATIMS/FWS interface
The FWS is used to generate warning indications for the crew.
The ATSU broadcasts the data on its output buses for information transmission to the FWC.
On the other hand, the ATSU acquires the FWC and SDAC broadcasted data which are needed for the AOC hosted application.
The ATSU broadcasts the data on the ATSU SYS1 & SYS2 output-buses data for the:

Airline warnings
Datalink system alarms.

The FWC and the SDAC broadcast on the FWC L1, FWC L2, SDAC L1 or SDAC L2 buses data for the:

AOC application data-delivery
ACARS routing function data-delivery.

(a) Company alerts
The ATSU generates the alert while the FWCs manage:

The alert display
The flight phase inhibition
The alert cancel and priority.
The ATSU sends signals to the FWCs for memos activation on the EWD:

1 When an alert message is received from the airline.

2 When a VOICE GO-AHEAD message is received from the airline requires a voice communication.

3 When a standard AOC message is received from the airline.

NOTE: These messages are inhibited during the takeoff and landing phases.

(b) System alarms

1 The system management function of the ATSU sends the signals to the FWCs concerning its own status and the VDR3 mode.

2 The air/ground communication router of the ATSU sends signals to the FWCs concerning the status of the interface with communication system peripherals and the datalink communication availability.

3 The FWCs generate the system alarms such as internal ATSU alarm, datalink alarm and communication system alarm, according to the flight phases inhibition and the priority level.

4 The FWC displays the warnings/malfunctions in amber on the upper Electronic Centralized Aircraft Monitoring (ECAM) Display Unit (DU). The INOP SYSTEM is displayed in amber and the limitations are displayed on in cyan on the System Display (SD).

(c) A/C configuration parameters
The FWCs provide the ATSU with the aircraft configuration parameters as software PIN PROG (SDU1 and DMU installed or not installed).
These data are used by the system management function of the ATSU for the peripherals management (alarm signals, BITE message generation or inhibition, on-board routing function, etc.).

(2) ATIMS/clock interface
The clock provides the ATSU with the Universal Time Coordinated (UTC) date and time.
The ATSU acquires these broadcasted data from the clock output bus.

(3) ATIMS/EIS interface
The ATSU acquires the broadcasted data from the DMC output bus which are needed for AOC hosted application.

(4) ATIMS/AIDS interface
The DMU is an optional peripheral hosting a remote AOC application.
A PIN PROG sent by the CFDIU enables the ATSU to determine if the DMU is installed or not.
The ATSU/DMU interface supports exchanges using ARINC 429 protocol.
These exchanges concern the ARINC 619 messages related to the remote AOC application hosted in the DMU.
The DMU uses the ATSU as an ACARS router to send the DMU downlink reports and to receive the DMU uplink requests.

(a) Status of the datalink communication
The ATSU broadcasts the status of the air/ground datalink communication to the DMU, because the DMU checks it before sending the downlink reports (status of the communication with the ground and between the ATSU and DMU).

(b) DMU fault detection
The ATSU acquires a periodic broadcasted data from the DMU to know if the DMU or the DMU/ATSU communication is operational or not.

(5) ATIMS/CFDS interface

(a) BITE interface
The ATSU is connected to the CFDIU for maintenance purposes and complies with the requirements and recommendations of ABD018.
The ATSU transmits information of the detected ATIMS internal or external failures to the CFDIU.
The ATSU receives the broadcasted BITE message parameters from the CFDIU for the BITE message generation.
When the aircraft is on the ground, the CFDIU sends the ATSU test requests (menu mode or interactive mode).

(b) LRU identification
The ATSU sends the part number and the software number of each component of the ATIMS system (ATSU hardware case and ATSU loaded softwares) to the CFDIU.

(c) CFDIU AOC application
The ATSU/CFDIU interface supports exchanges using character-oriented ARINC 429 protocol. These exchanges concern the ARINC 619 messages related to the remote AOC application hosted in the CFDIU: CFDIU downlink reports.
The CFDIU sends downlink reports (Post Flight Report (PFR) or BITE data messages) to the ATSU and it informs the result of the transmission to the ground.

(d) Status of the datalink communication
The ATSU broadcasts the status of the air/ground datalink communication to the CFDIU because the CFDIU checks it before sending the downlink reports (status of the communication with the ground and between the ATSU and the CFDIU).

(e) CFDIU fault detection
The ATSU acquires a periodic broadcast label from the CFDIU to determine if the CFDIU and the CFDIU/ATSU communication are operational or not.

(f) A/C configuration parameters
The ATSU acquires a broadcasted configuration parameter from the CFDIU, in order to know if the DMU system is installed on the aircraft.

(g) A/C identification
The ATSU acquires the broadcasted Aircraft Registration Number (ARN) and the flight number from the CFDIU, for the air/ground communication functions.
Then the ARN is stored in a non-volatile memory until a new value is acquired.

(h) CFDIU active function programming
The ATSU sends the reports that are forecasted in the automatic transmission by means of the active functions programming to the CFDIU :

BITE report
Real time warning
Real time failure
Post/current flight report

(i) AOC parameters
The CFDIU provides the ATSU with AOC parameters related to the desired information which is included in the AOC report by the hosted AOC application.

(6) ATIMS/printer interface
The ATSU transmits data to the printer in accordance with the ARINC 740 specifications.
As the printer is a multipurpose printer, the ATSU has to be recognized by the printer as one of its peripherals.
So, the ATSU sends its system address label on label 172 to the printer periodically.
The ATSU acquires the printer status to determine if it is operational or not.

NOTE: The printer is a multipurpose printer. So, the ATSU buffers data printing when the printer is busy.

(7) ATIMS/data-loading system interface
The ATSU uses the dataloading system services for the application software and the database uploading. This interface supports the ATSU software and database loading and complies with the ARINC 615 requirements.
The ATSU software is loaded through a PDL or with the MDDU (selector switch 11TD in the ATSU position, on overhead panel 265VU).
The ATSU must be reset after a software loading operation (the DATA LOADING SELECTOR switch must be set to OFF) to validate the operation.

(8) ATIMS/cabin terminals interface
The cabin terminal system is to be considered as the Passenger Flight Information System (PFIS). The ATSU is connected to the Data Interface Unit (DIU).
This interface is optional and no PIN PROG determines if the DIU is installed or not.
This ATSU/DIU interface supports exchanges using the ARINC 429 protocol. These exchanges concern the ARINC 619 messages related to the remote AOC application hosted in the DIU: the DIU downlink reports and the DIU uplink requests.
The DIU uses the ATSU as an ACARS router.
The ATSU sends downlink reports and informs the cabin terminals about the result of the transmission.

NOTE: The transmissions are only automatic or on ground request.

The ATSU broadcasts the status of the datalink communication to the DIU about the availability of communication with the ground and between the ATSU and DIU.

G. Landing Gear/ATIMS Interface
The ATSU and both the DCDUs receive three distinct discrete signals from the LGCIU to determine whether the aircraft is on ground or in flight.
These discrete signals correspond to the "Left hand gear compressed" information.
The ATSU receives three distinct discrete signals from the LGCIU to determine whether the aircraft is on ground or in flight.
These discrete signals correspond to the "Left hand gear compressed" information.

H. Lights/ATIMS Interface

(1) ATC MSG pushbutton switches
The ATC MSG pushbutton-switches power supply is provided by the transformers from the LP circuit (annunciator light test and dimming) which supply 7.5VDC voltage.

Transformer 2LP2 supplies the legends of the pushbutton switches related to the FWC2 signals for both the captain and first officer alerts.
Transformer 2LP3 supplies the legends of the pushbutton switches related to the FWC1 signals for both the captain and first officer alerts.

NOTE: The ATC MSG pushbutton switches are also linked to the annunciator test command to check the correct operation of all the annunciators in the cockpit.

(2) DCDU
The DCDU front face is illuminated through a 5VAC/400Hz voltage supplied by the LF circuit (circuit LF Instrument and panel integral lighting).
This voltage is provided by the graduator 6LF which enables light dimming in the cockpit.

I. ATIMS/Air Conditioning Interface
The ATSU is ventilated in electronics rack 80VU.

J. ATIMS/GPS Interface
The Global Positioning System (GPS) receiver can be MMR2 or Global Positioning System Sensor Unit (GPSSU) 2 depending on the aircraft configuration. It provides the ATIMS with the UTC date and time.

** ON A/C NOT FOR ALL

6. Component Description

A. Air Traffic Service Unit (ATSU) FIN: 1-TX-1

(1) Functional breakdown

ATIMS - Functional Breakdown

The ATSU functional breakdown consists of:

The hardware case containing the minimum software to enable uploading of the different applications (the hardware resources and the part of interface services necessary to upload the ATSU).
The ATSU A/C INTERFACE software with the functional services and the main part of the interface services.
The ATSU CONFIGURATION software for the manufacturer configuration parameters.
The ATSU ROUTER PARAMETERS software for the VHF DSP world-map database.

The ATSU provides the applications with all the resources and services required to perform their tasks.

(a) Hardware resources

Computing capacities
Memory capacities
Hardware input/output capacities.

(b) Functional services
Functional services are high-level services and comprise of:

Air/ground communication services
. Air/ground routing function
. Communication sub-networks management
. Communication sub-networks access
. Messages formatting.
HMI services
. HMI resources (MCDU, printer, etc.) management
. HMI resources access.
Onboard integration services
. Onboard data access and delivery for the hosted applications.
System management services
. System configuration set-up
. System status monitoring
. System maintenance (BITE)
. Operating system to use and share the hardware resources.

(c) Interface services
The interface services are the low-level services shared by the functional services and used to handle the ATSU interfaces:

Discrete signals input or output management
ARINC 429 broadcast and Williamsburg protocol

(2) ATSU hardware case description

ATIMS - ATSU Hardware Case

(a) Characteristics
The ATSU complies with the ARINC 600 specification:

Size: 4MCU case.
Weight: 6kg.
Dissipated power: 55.5 Watts in average value and 70 Watts in maximum value.
Unit connectors size: 2 shell.

(b) Functions
It provides the functions with the hardware resources such as:

Processing power
Memory capacity
Input/output electrical circuit
Power supply

And also with the minimum softwares to enable the corresponding software loading:

hardware initialization
data loading processing.

(3) ATSU A/C interface software

(a) Characteristics
This software is provided by a set of disks.
It complies with the ARINC 615 specification.

(b) Operation
The different functions provided are:

Monitoring of the system: power supply and BITE functions
Acquisition of the aircraft parameters for applications software use
Management of the air/ground communications
Management of communication with the onboard peripheral units
Management of the human/machine interface (MCDU, printer and alert function).

(4) ATSU aircraft-interface software

(a) Properties
This software complies with the ARINC 615 specification.

(b) Operation
The different functions are as follows:

Monitoring of the system: power supply and BITE functions
Acquisition of the aircraft parameters that the software applications use
Management of the air/ground communications
Management of the communication with the onboard peripheral units
Management of the Human-Machine Interfaces (HMI) (MCDU, printer and alert function).

(5) ATSU configuration software

(a) Characteristics
This software is provided in a set of disks.
It complies with ARINC 615 Specification.

(b) Operation
This software consists of a database containing:

routing policies definitions
A routing policy lists a set of allowed media, with a preference order and the conditions which lead to a change of media.
A downlink AOC message is submitted to the ACARS router with a routing policy code. The meaning of this code is customizable for hosted AOC applications and ATSU 619 peripherals except FMGC: it can specify a subnetwork to be used, an ordered list of subnetworks and a service provider for the VHF subnetwork.
configuration elements
The configuration database contains two software pin-programming: HFDL pin-programming for ATC applications and VHF3 voice/data switching through the MCDU (it will be inhibited if ATC applications are uploaded).
downlink messages priorities.

(6) Router Parameters software

(a) Characteristics
This software is provided in a set of disks.
It complies with ARINC 615 Specification.

(b) Operation
This software consists of a database containing the standard DSP world map database:

media configuration tables
The media configuration tables give the ARINC 618 parameters for each air/ground communication medium, such as timers, counters, identifiers.
There is a Satcom media configuration table and a VHF media configuration table for each service provider.
VHF world map
The VHF world map database contains the VHF geographical areas for each service provider.
The world map is described over 512 rectangular areas defined by the latitude/longitude of their south-east limits. It can be presented in an array form or in graphic format.
The first defined area is delimited by 90°N at its north border and 180°W at the west border.
In the standard DSP world map, the order of the service providers is not taken into account. When more than one service provider cover an area, a scan mask must be defined.

(7) ATSU configuration software

(a) Characteristics
This software is provided by a set of disks.
It complies with the ARINC 615 specification.

(b) Operation
This software consists of a database with:

Routing policies definitions
A routing policy lists a set of allowed media, with a preference order and the conditions which lead to a change of media.
A downlink AOC message is submitted to the ACARS router with a routing policy code. The meaning of this code is customizable for the hosted AOC applications and the ATSU 619 peripherals except FMGC. It can specify a subnetwork to be used, an ordered list of subnetworks and a service provider for the VHF subnetwork.
Configuration elements
The configuration database contains three software PIN PROG:
HFDL PIN PROG for ATC applications
VHF3 voice/data switching through the MCDU (it will be inhibited if the ATC applications are uploaded)
Downlink messages priorities
VDL2 parameters.

(8) Router parameters software

(a) Characteristics
This software is provided by a set of disks.
It complies with the ARINC 615 specification.

(b) Operation
This software consists of a database with the standard DSP world-map database:

Media configuration tables
The media configuration tables give the ARINC 618 parameters for each air/ground communication medium, such as timers, counters, identifiers and the VDL2 parameters.
There is a SATCOM media-configuration table, a VHF media-configuration table and a HF media-configuration table for each service provider.
VHF world map
The VHF world-map database contains the VHF geographical areas for each service provider.
The world map is described over 512 rectangular areas defined by the latitude/longitude of their south-east limits. It can be presented in an array form or in the graphic format.
The first defined area is delimited by 90°N at its north border and 180°W at the west border.
In the standard DSP world map, the order of the service providers is not taken into account. When more than one service provider cover an area, a scan mask must be defined.

(9) ATSU configuration software

(a) Properties
This software complies with the ARINC 615 specification.

(b) Operation
This software has a database that contains:

The routing policies definitions
A routing policy gives the list of the permitted media, the recommended sequence to use them and the conditions to change media.
A downlink AOC message is sent to the ACARS router with a routing policy code. It is possible to change the meaning of this code for the installed AOC applications and the ATSU 619 peripherals but not the FMGC. It can give a subnetwork to be used, an ordered list of subnetworks and a service provider for the VHF subnetwork.
The configuration elements
The configuration database has three software pin-programming:
The HFDL pin-programming for the ATC applications
The VHF3 voice/data switching through the MCDU (it will be inhibited if the ATC applications are uploaded)
The downlink message priorities
The VDL2 parameters.

(10) Router parameter software

(a) Properties
This software complies with the ARINC 615 specification.

(b) Operation
This software has a database that contains the standard DSP world-map database:

Media configuration tables
The media configuration tables give the ARINC 618 parameters for each air/ground communication medium, for example the timers, counters and identifiers.
There is a Satcom media-configuration table and a VHF media-configuration table for each service provider.
VHF world map
The VHF world-map database contains the VHF geographical areas for each service provider.
The world map includes more than 512 rectangular areas with the latitude/longitude of their South-East limits. It can have an array or a graphic format.
The limits of the first area are as follows: 90°N at its North border and 180°W at its West border.
In the standard DSP world-map, the sequence of the service providers is not taken into account. When more than one service provider cover an area, it is necessary to set a scan mask.

(11) ATSU FANS A applications software

(a) Characteristics
This software is provided by a set of disks.
It complies with the ARINC 615 specification.
The different ATC applications contained in the package are :

ADS : Automatic Dependent Surveillance
AFN : Air Traffic Service (ATS) Facilities Notification
CPDLC : Controller-Pilot Data Link Communication

The ATSU FANS A software is identified by a global part number.
However, each application is also identified by a sub-part number.

(b) Operation
The ATC applications require the resources and services to perform their tasks which are:

Functional services
. Air/ground communication services
. HMI services
. Onboard integration services
. System management services
Interface services
Hardware ressources

(12) ATSU FANS B applications Software

(a) Characteristics
This software is provided by a set of disks.
It complies with ARINC 615 Specification.
The different ATC applications contained in the package are :

CPDLC : Controller-Pilot Data Link Communication
CMA : Context Management Application

The ATSU FANS B Software is identified by a global part number.
However, each application is also identified by a sub-part number.

(b) Operation
The ATC applications require the following resources and services to perform their tasks :

Functional Services
. air/ground communication services
. human machin interface services
. on-board integration services
. system management services
interface services
hardware ressources

(13) ATSU FANS B application software

(a) Properties
This software complies with the ARINC 615 specification.
The package contains the different ATC applications that follow:

CPDLC: Controller-Pilot Data-Link Communication
CMA: Context Management Application.

A global part number identifies the ATSU FANS B software.
But each application also has a sub-part number.

(b) Operation
The resources and services that follow are necessary for the ATC applications:

Functional Services
. Air/ground communication services
. Human-Machine Interface (HMI) services
. On-board integration services
. System management services
Interface services
Hardware ressources.

(14) ATSU AOC software

(a) Characteristics
This software is provided by a set of disks.
It complies with the ARINC 615 specification.

(15) ATSU AOC software

(a) Properties
This software complies with the ARINC 615 specification.

B. Datalink Control and Display Unit (DCDU) (in FANS A and FANS B configurations only)

(1) Physical description

ATIMS - DCDU Display ** ON A/C NOT FOR ALL

The DCDU is equipped with an LCD screen and two sets of four pushbutton switches located on each side of the screen.

(a) Electrical characteristics

Compliance with ABD 0100
Power supply: 28VDC
Dissipated power : 16.5 Watts (average value).
One back connector composed of:
. One ARINC 429 input bus from the ATSU
. One ARINC 429 output bus to the ATSU
. 11 discrete inputs (P-type) for PIN PROG, power supply, ground and air/ground signal
. One analog input.

(b) Mechanical characteristics

Attachment by four captive corner attachment-screws
Compliance with ABD 0100
Weight: 2kg
Dissipated power: 16.5 Watts (average value)
Cooling by air convection.

(2) Functional operation
The DCDU has two main functions:

Display function: display of the air-traffic system information to the flight crew
Control function: a response device for the flight crew.

(a) Display function
The DCDU is equipped with a LCD flat panel.
The DCDU displays the messages formatted by the ATSU on a black background in eight different colors: amber, black, cyan, green, magenta, red, white and yellow.
These messages are in semi-graphical format and include the alphanumerical text and simple graphical attributes such as boxes, arrows, separation lines, reverse video, etc.

(b) Control function
The DCDU has:

Four pushbutton switches associated to the menu keys referred to as the soft keys
Four engraved pushbutton switches dedicated to:
. Page up and down functions
. Message up and down functions
. Print function
. Manual brightness control.

In addition, the pushbutton switches are lighted for night vision in accordance with the general cockpit selection.
Each DCDU has a "black screen" function in order to not 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 by a reverse video display. This action is acknowledged prior to and independently of a possible message change from the ATSU.
The time elapsed between the pilot action and sending of the data (on the ARINC bus) and local feedback displayed on the screen is not greater than 100 ms.

** ON A/C NOT FOR ALL

7. Operation

A. System Configuration

(1) ATSU A/C INTERFACE software loading
The loading procedure is ensured by the "Boot software" included in the ATSU hardware case.
The ATSU is the first to be loaded with the A/C INTERFACE software which takes A/C configuration and adaptation to different system interfaces into account.
It contains air/ground communication services and the router function.
The adaptation to the A/C configuration is also ensured through pin programming acquisition. This is done either from hard ATSU pin programming, or from pin-programming information received from CFDIU (configuration label).

NOTE: The ATSU is automatically reset after a software loading operation through an internal mechanism.
The LRU IDENTIFICATION function from the BITE enables to display the software version reference in order to check the correct uploading.

(2) ATSU Configuration software loading
The ATSU Configuration software is uploaded into the ATSU.
It consists of a database containing routing policies definitions and configuration elements.
This database enables the manufacturer to modify configuration parameters (flexibility improvement).

(3) Loading of ATSU router parameters software
The ATSU router parameters software is uploaded in the ATSU.
It contains the standard DSP world map database: media configuration tables and VHF world map.
This database gives the list of VHF datalink service providers available in each geographical area: automatic selection of VHF frequency depending on the aircraft position as well as the scan mask entered by the airline.

(4) AOC software and database loading
In Pre-FANS configuration, the AOC application software and the associated database are uploaded in the ATSU.
The AOC software package contains the specific airline datalink applications.
Remote AOC applications are also embedded in peripherals which some of them are optional such as DMU, Cabin Terminals (remote AOC peripherals).

(5) ATSU FANS A applications loading
In the FANS A configuration, the ATSU FANS A application software package is also uploaded.
In this case, the ATSU sends information to the FWCs indicating that the ATC applications are active for the ATC datalink-alarm generation.

(6) ATSU FANS B applications loading
In FANS B configuration, the ATSU FANS B application software package is also up-loaded.
In this case, the ATSU sends information to the FWCs indicating that ATC applications are active for ATC datalink alarm generation.

B. ATSU DATALINK applications

Three menus are available:

Three menus are available:

(1) Air/Ground Communication menu

ATIMS - Access to COMM MENU Page ** ON A/C NOT FOR ALL

The COMM MENU menu page gives access to:

The COMM INIT page to let the datalink communications start again
The VHF3 DATA MODE page to select the Data mode and the VDR3 frequency
The VHF3 VOICE DIRECTORY page to select the Voice mode and the VDR3 frequency
The COMM STATUS page to know if the VHF3 and SATCOM networks are available
The MAINTENANCE page to select a TEST part and an AUDIT part.

For more information, refer to (Ref. AMM D/O 46-24-00-00).

(2) Air/Ground Communication Menu

ATIMS - Access to the COMM MENU Page ** ON A/C NOT FOR ALL

The COMM MENU menu page gives access to:

The COMM CONFIG page to let the datalink communications start again
The VHF3 DATA MODE page to select the Data mode and the VDR3 frequency
The MAINTENANCE page to select a TEST part, a STATISTICS part and an AUDIT part.

For more information (Ref. AMM D/O 46-24-00-00).

(3) Airline Company menu (optional)
Each airline has its dedicated Airline Operational Control (AOC) menu.
For more information, refer to (Ref. AMM D/O 46-23-00-00).

(4) Airline Company menu (optional)
Each airline has its dedicated Airline Operational Control (AOC) menu.
For more information, refer to (Ref. AMM D/O 46-23-00-00).

(5) Controller-Pilot DataLink Communication (CPDLC) menu

ATIMS - Access to the ATC MENU ** ON A/C NOT FOR ALL

The ATC menu is applicable only to the FANS A configuration and gives access to:

The LAT REQ page to tell the Air Traffic Control (ATC) center that the crew changes the lateral trajectory
The WHEN CAN WE page to give the time necessary to the ATC center
The MSG RECORD page to show the messages closed and stored in the Datalink Control and Display Unit (DCDU)
The NOTIFICATION page to let the ATS Facilities Notification (AFN) with an ATC center start again and to make sure that there is a communication between the ATC center and the crew
The VERT REQ page to tell the ATC center that the crew changes the vertical trajectory
The OTHER REQ page for other requests (for example, voice contact with the ATC center)
The TEXT page to send, to the ATC center, the justifications for the negative replies
The REPORT page to give the position reports automatically at each ATC waypoint
The CONNECTION STATUS page to show the status of the CPDLC connections and the ADS applications
The EMERGENCY page to give the emergency messages to the ATC center.

A second menu page gives access to the ARINC 623 applications (optional):

The DEPART REQ page to give the departure clearances
The OCEANIC REQ page to give the oceanic clearances
The ATIS page to give information about the active terminal conditions (runway, meteorological parameters and approach procedure).

For more information, refer to (Ref. AMM D/O 46-22-00-00).

(6) Controller-Pilot DataLink Communication (CPDLC) menu

ATIMS - Access to ATC MENU ** ON A/C NOT FOR ALL

The Air Traffic Control (ATC) menu is applicable only to the FANS A configuration and gives access to:

The REQUEST menu page which has:
- The LAT REQ page for requests of lateral trajectory changes to the ATC center
- The VERT REQ page for requests of vertical trajectory changes to the ATC center.
The MSG RECORD page to show messages closed and stored in the DCDU
The CONNECTION menu page which has:
- The NOTIFICATION page to let the ATS Facilities Notification (AFN) with an ATC center start again and to make sure that there is a communication between the ATC center and the crew
- The CONNECTION STATUS page to show the status of the CPDLC connections.

For more information, refer to (Ref. AMM D/O 46-22-00-00).

C. Datalink Alerts and Alarms
The ATSU uses the services provided by the FWCs to activate visual/aural alerts and alarms in case of:

failure or unavailability of datalink functions.

The FWCs are used to generate these warning indications according to the information provided by the ATSU. The conditions of activation/deactivation of these warning indications are managed by the ATSU, while the FWCs are in charge of display, priority and inhibition management.

A pin-programming is activated on the FWC following airline request to generate:

ACARS messages when the "ACARS installed" hard pin-programming is activated
ATSU messages when the "ATSU installed" hard pin-programming is activated

The ATSU uses the services provided by the FWCs to activate the visual/aural alerts and alarms (in case of failure or unavailability of the datalink functions).

The FWCs are used to generate these warning indications according to the information provided by the ATSU. The conditions of activation/deactivation of these warning indications are managed by the ATSU, while the FWCs are in charge of display, priority and inhibition management.

A pin-programming is activated on the FWC upon the airline request to generate:

The ACARS messages when the "ACARS installed" hard pin-programming is activated
The ATSU messages when the "ATSU installed" hard pin-programming is activated.

The ATSU uses the services provided by the FWCs to activate visual/aural alerts and alarms in case of:

failure or unavailability of datalink functions.

ATSU messages when the "ATSU installed" hard pin-programming is activated

(1) ECAM messages related to the datalink media failure

-------------------------------------------------------------------------------

CONDITIONS UPPER ECAM DU MESSAGES

"ACARS installed" "ATSU installed"

pin-prog activated pin-prog activated

-------------------------------------------------------------------------------

VHF3 data loss: VDR3 is failed COM VHF 3 FAULT COM VHF 3 DATA FAULT

for datalink communication. (amber message) (amber message)

-------------------------------------------------------------------------------

SATCOM data loss: SATCOM is COM SATCOM FAULT COM SATCOM DATA FAULT

failed for datalink (amber message) (amber message)

communication.

-------------------------------------------------------------------------------

VHF3 in voice mode: the VHF3 is VHF 3 VOICE VHF 3 VOICE

currently used in voice mode. (green right memo) (green left memo)

-------------------------------------------------------------------------------

The crew has received a message SATCOM ALERT

requesting a voice communication (green right memo)

from the ground.

-------------------------------------------------------------------------------

(2) ECAM messages related to the datalink media failure

-------------------------------------------------------------------------------

CONDITIONS UPPER ECAM DU MESSAGES

"ACARS installed" "ATSU installed"

PIN PROG activated PIN PROG activated

-------------------------------------------------------------------------------

VHF3 data loss: VDR3 is failed COM VHF 3 FAULT COM VHF 3 DATA FAULT

for datalink communication. (amber message) (amber message)

-------------------------------------------------------------------------------

SATCOM data loss: SATCOM is COM SATCOM FAULT COM SATCOM DATA FAULT

failed for datalink (amber message) (amber message)

communication.

-------------------------------------------------------------------------------

HF1 data failure without loss COM HF 1 DATA FAULT

of HF1: HF1 is failed for (amber message)

datalink communications (only activated if the

PIN PROG "HFDR1

installed" is set to

the ground)

-------------------------------------------------------------------------------

VHF3 in voice mode: VHF3 is VHF 3 VOICE VHF 3 VOICE

currently used in voice mode. (green right memo) (green left memo)

-------------------------------------------------------------------------------

The crew has received a message SATCOM ALERT

requesting a voice communication (green right memo)

from the ground.

-------------------------------------------------------------------------------

All the installed HFDR are in HF VOICE

voice mode (green right memo)

(only activated if the

PIN PROG "HFDR1

installed" is set to

the ground)

-------------------------------------------------------------------------------

HF data on ground HF DATA OVRD

(green right memo)

(only activated if the

PIN PROG "HFDR1

installed" is set to

the ground)

-------------------------------------------------------------------------------

(3) ECAM messages related to the datalink media failure

-------------------------------------------------------------------------------

CONDITIONS UPPER ECAM DU MESSAGES

"ATSU installed"

pin-prog activated

-------------------------------------------------------------------------------

VHF3 data loss: VDR3 is failed COM VHF 3 DATA FAULT

for datalink communication. (amber message)

-------------------------------------------------------------------------------

SATCOM data loss: SATCOM is COM SATCOM DATA FAULT

failed for datalink (amber message)

communication.

-------------------------------------------------------------------------------

HF1 data failure without loss COM HF 1 DATA FAULT

of HF1: HF1 is failed for (amber message)

datalink communications (only activated if the

pin program "HFDR1

installed" is set to

ground)

-------------------------------------------------------------------------------

VHF3 in voice mode: the VHF3 is VHF 3 VOICE

currently used in voice mode. (green left memo)

-------------------------------------------------------------------------------

The crew has received a message

requesting a voice communication

from the ground.

-------------------------------------------------------------------------------

All the installed HFDR are in HF VOICE

voice mode (green right memo)

(only activated if the

pin program "HFDR1

installed" is set to

ground)

-------------------------------------------------------------------------------

HF data on ground HF DATA OVRD

(green right memo)

(only activated if the

pin program "HFDR1

installed" is set to

ground)

-------------------------------------------------------------------------------

ATC datalink communications DATALINK ATC FAULT

failure: the air-ground (amber message with

communications means used for ATC MAST CAUT light and

applications. ATC applications Single Chime

are all failed. The datalink activated)

communications are definitely and

unavailable. ATC COM VOICE ONLY

(cyan message with

MAST CAUT light and

Single Chime

activated)

-----------------------------------------------------------------------------

ATC datalink application loss: DATALINK ATC FAULT

the airborne datalink ATC (amber message with

applications are failed. MAST CAUT light and

Single Chime

activated)

and

ATC COM VOICE ONLY

(cyan message with

MAST CAUT light and

Single Chime

activated)

-----------------------------------------------------------------------------

Temporary loss of ATC datalink ATC DATALINK STBY

communications: the air-ground (green right memo)

communications means used for

ATC applications. ATC

applications are temporarily

unavailable for less than

10 minutes, but not failed. The

ATSU is trying to recover the

datalink communications with the

ground.

** ON A/C NOT FOR ALL

8. Test

A. BITE Architecture

ATIMS - BITE Architecture ** ON A/C NOT FOR ALL

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:

ATSU internal failures
external interface failures with ATSU peripherals.

The ATIMS BITE is ensured by the ATSU which concentrates the failure information provided by the ATSU internal monitoring.
This BITE is of type 1 and operates in two modes:

normal mode
MENU mode

ATIMS - BITE Architecture ** ON A/C NOT FOR ALL

ATSU internal failures
External interface failures with ATSU peripherals.

The ATIMS BITE is ensured by the ATSU which concentrates the failure information provided by the ATSU internal monitoring.
This BITE is of type 1 and operates in two modes:

Normal mode
Menu mode

ATIMS - BITE Architecture ** ON A/C NOT FOR ALL

ATSU internal failures
external interface failures with ATSU peripherals.

The ATIMS BITE is ensured by the ATSU which concentrates the failure information provided by the ATSU internal monitoring.
This BITE is of type 1 and operates in two modes:

normal mode
MENU mode

(1) Normal mode
During the normal mode, the BITE:

monitors the ATSU status
monitors data inputs from the various ATIMS peripherals (FMGC, MCDU, CFDIU,...)
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.

(2) Menu mode

(a) System Report/Test Function

Access to the ATIMS SYSTEM REPORT/TEST Page ** ON A/C NOT FOR ALL

The BITE information (system report) and the test request (system test function) are available through MCDU menus which allow to communicate with ATIMS BITE via the CFDIU.
To gain access to the BITE, it is necessary to use one MCDU (Ref. AMM D/O 22-82-00-00).
All the information displayed on the MCDU during the BITE test configuration can be printed by the printer.
ATIMS maintenance menu is only accessible on ground from the general maintenance menu and the SYSTEM REPORT/TEST page.
This mode enables communication between the CFDIU and the ATIMS BITE by means of the MCDU.

(b) LAST LEG REPORT page

ATIMS - LAST LEG REPORT Page ** ON A/C NOT FOR ALL

This report contains the failure messages (internal and external, Class 1 and 2) recorded during the last flight. It is available at the end of the flight. Each failure message is reported with the failure classes defined by the CFDS standard.

ATIMS - PREVIOUS LEGS REPORT Page ** ON A/C NOT FOR ALL

This report contains the fault messages related to the external or internal failures (Class 1 or 2) recorded during the previous 63 flight legs.

(d) LRU IDENTIFICATION page

ATIMS - LRU IDENTIFICATION Page ** ON A/C NOT FOR ALL

This menu enables to display the identification of the various ATIMS components (ATSU and Software packages). It is used to check the uploading of the correct software Part Number:

Part Number and Serial Number of the ATSU (hardware case - FIN 1TX1)
Part Number and Serial Number of the DCDU 1 and DCDU 2 (FIN 2TX1 and 2TX2)
Part Number of the SOFTWARE-ATSU A/C INTERFACE (FIN 20TX)
Part Number of the SOFTWARE-ATSU CONFIGURATION (FIN 21TX)
Part Number of the SOFTWARE-AOC (FIN 22TX)
Part Number of the SOFTWARE-AOC DATABASE (FIN 24TX)
Part Number of the SOFTWARE-ATSU ATC HMI utilities (FIN 25TX)
Part Number of the SOFTWARE-ATSU ROUTER PARAM (FIN 30TX)
Part Number of the SOFTWARE-ISM APPLICATION (FIN 31TX)
Part Number of the SOFTWARE-ATSU FANS B APPLICATIONS (FIN 36TX)
Part Number of the SOFTWARE-ATSU CMA CONFIGURATION (FIN 37TX)

If one component is missing in a given configuration, the corresponding line is not displayed.

(e) GROUND SCANNING page

ATIMS - GROUND SCANNING Page ** ON A/C NOT FOR ALL

This function is based on the monitoring and the fault analysis during the flight and enables consultation of the ATIMS failure recordings.
The ATSU peripheral monitoring and internal cyclic tests are used in order to detect transient failures.

(f) TROUBLE SHOOTING DATA page

ATIMS - TROUBLE SHOOTING DATA Page ** ON A/C NOT FOR ALL

This function provides correlation parameters and snapshot data concerning the failure displayed in the LAST LEG REPORT and the PREVIOUS LEGS REPORT pages.

(g) CLASS 3 FAULTS page

ATIMS - CLASS 3 FAULT Page ** ON A/C NOT FOR ALL

This menu enables to display the Class 3 faults recorded during the last flight leg.

(h) SYSTEM TEST page

ATIMS - SYSTEM TEST Page ** ON A/C NOT FOR ALL

The ATIMS BITE test is initiated when pressing the line key adjacent to the SYSTEM TEST indication.
The test ends with the display of the following message on the MCDU:

TEST OK indication when all the tests are completed and no failure has been detected
or the failure message(s) when one or more failures have been detected.

(i) GROUND REPORT page

ATIMS - GROUND REPORT Page ** ON A/C NOT FOR ALL

This function is used to present Class 1, 2 or 3 internal failures when they are detected on ground.
The relevant trouble shooting data are displayed by pressing the line key adjacent to the failure indication.
These failures differ from those displayed on the LAST LEG REPORT page.

(3) Normal mode
During the normal mode, the BITE:

monitors the ATSU status
monitors data inputs from the various ATIMS peripherals (FMGC, MCDU, CFDIU,...)
permanently transmits ATIMS system status and its identification message to the CFDIU.

(4) Menu mode

(a) System Report/Test Function

Access to the ATIMS SYSTEM REPORT/TEST Page ** ON A/C NOT FOR ALL

(b) LAST LEG REPORT page

ATIMS - LAST LEG REPORT Page ** ON A/C NOT FOR ALL

ATIMS - PREVIOUS LEGS REPORT Page ** ON A/C NOT FOR ALL

This report contains the fault messages related to the external or internal failures (Class 1 or 2) recorded during the previous 63 flight legs.

(d) LRU IDENTIFICATION page

ATIMS - LRU IDENTIFICATION Page ** ON A/C NOT FOR ALL

This menu enables to display the identification of the various ATIMS components (ATSU and Software packages). It is used to check the uploading of the correct software Part Number:

Part Number and Serial Number of the ATSU (hardware case - FIN 1TX1)
Part Number of the SOFTWARE-ATSU A/C INTERFACE (FIN 20TX)
Part Number of the SOFTWARE-ATSU CONFIGURATION (FIN 21TX)
Part Number of the ATSU ATC ARINC 623 Applications software (23TX)
Part Number of the SOFTWARE-ATSU ATC HMI utilities (FIN 25TX)
Part Number of the SOFTWARE-ATSU ROUTER PARAM (FIN 30TX)
Part Number of the SOFTWARE-ISM APPLICATION (FIN 31TX)
Part Number of the SOFTWARE-ATSU FANS B APPLICATIONS (FIN 36TX)
Part Number of the SOFTWARE-ATSU CMA CONFIGURATION (FIN 37TX)

If one component is missing in a given configuration, the corresponding line is not displayed.

(e) GROUND SCANNING page

ATIMS - GROUND SCANNING Page ** ON A/C NOT FOR ALL

(f) TROUBLE SHOOTING DATA page

ATIMS - TROUBLE SHOOTING DATA Page ** ON A/C NOT FOR ALL

This function provides correlation parameters and snapshot data concerning the failure displayed in the LAST LEG REPORT and the PREVIOUS LEGS REPORT pages.

(g) CLASS 3 FAULTS page

ATIMS - CLASS 3 FAULT Page ** ON A/C NOT FOR ALL

This menu enables to display the Class 3 faults recorded during the last flight leg.

(h) SYSTEM TEST page

ATIMS - SYSTEM TEST Page ** ON A/C NOT FOR ALL

The ATIMS BITE test is initiated when pressing the line key adjacent to the SYSTEM TEST indication.
The test ends with the display of the following message on the MCDU:

TEST OK indication when all the tests are completed and no failure has been detected
or the failure message(s) when one or more failures have been detected.

(i) GROUND REPORT page

ATIMS - GROUND REPORT Page ** ON A/C NOT FOR ALL

(j) SPECIFIC DATA page

ATIMS - SPECIFIC DATA Page ** ON A/C NOT FOR ALL

This menu enables acces to different functions:

1L : LOAD STATUS (available in Pre-FANS+ configuration only)
2L : PIN PROGRAMMING to check the ATSU configuration with its parity validity.

NOTE: The order of the pin programming display is in accordance with the one of the ATSU input connector:
- a pin programming not defined (spare) is displayed with a zero value.
- an active pin programming is displayed with a 1 value.

3L : DUMP TSD
4L : SW P/N PRINT OUT

(5) Normal mode
During the normal mode, the BITE:

monitors the ATSU status
monitors data inputs from the various ATIMS peripherals (FMGC, MCDU, CFDIU,...)
permanently transmits ATIMS system status and its identification message to the CFDIU.

(6) Menu mode

(a) System Report/Test Function

Access to the ATIMS SYSTEM REPORT/TEST Page ** ON A/C NOT FOR ALL

(b) LAST LEG REPORT page

ATIMS - LAST LEG REPORT Page ** ON A/C NOT FOR ALL

ATIMS - PREVIOUS LEGS REPORT Page ** ON A/C NOT FOR ALL

This report contains the fault messages related to the external or internal failures (Class 1 or 2) recorded during the previous 63 flight legs.

(d) LRU IDENTIFICATION page

ATIMS - LRU IDENTIFICATION Page ** ON A/C NOT FOR ALL

This menu enables to display the identification of the various ATIMS components (ATSU and Software packages). It is used to check the uploading of the correct software Part Number:

Part Number and Serial Number of the ATSU (hardware case - FIN 1TX1)
Part Number of the SOFTWARE-ATSU A/C INTERFACE (FIN 20TX)
Part Number of the SOFTWARE-ATSU CONFIGURATION (FIN 21TX)
Part Number of the SOFTWARE-ATSU ROUTER PARAM (FIN 30TX)
Part Number of the SOFTWARE-AOC (FIN 22TX)
Part Number of the SOFTWARE-AOC DATABASE (FIN 24TX)

If one component is missing in a given configuration, the corresponding line is not displayed.

(e) GROUND SCANNING page

ATIMS - GROUND SCANNING Page ** ON A/C NOT FOR ALL

(f) TROUBLE SHOOTING DATA page

ATIMS - TROUBLE SHOOTING DATA Page ** ON A/C NOT FOR ALL

This function provides correlation parameters and snapshot data concerning the failure displayed in the LAST LEG REPORT and the PREVIOUS LEGS REPORT pages.

(g) CLASS 3 FAULTS page

ATIMS - CLASS 3 FAULT Page ** ON A/C NOT FOR ALL

This menu enables to display the Class 3 faults recorded during the last flight leg.

(h) SYSTEM TEST page

ATIMS - SYSTEM TEST Page ** ON A/C NOT FOR ALL

The ATIMS BITE test is initiated when pressing the line key adjacent to the SYSTEM TEST indication.
The test ends with the display of the following message on the MCDU:

TEST OK indication when all the tests are completed and no failure has been detected
or the failure message(s) when one or more failures have been detected.

(i) GROUND REPORT page

ATIMS - GROUND REPORT Page ** ON A/C NOT FOR ALL

(j) SPECIFIC DATA page

ATIMS - SPECIFIC DATA Page ** ON A/C NOT FOR ALL

This menu enables access to different functions:

1L : LOAD STATUS (available in Pre-FANS+ configuration only)
2L : PIN PROGRAMMING to check the ATSU configuration with its parity validity.

3L : DUMP TSD
4L : SW P/N PRINT OUT

(7) Normal mode
During normal mode, the BITE:

Monitors the ATSU status
Monitors the data inputs from the various ATIMS peripherals (FMGC, MCDU, CFDIU, etc.)
Permanently transmits the ATIMS system status and its identification message to the CFDIU.

(8) Menu mode

(a) System Report/Test Function

Access to the ATIMS SYSTEM REPORT/TEST Page ** ON A/C NOT FOR ALL

The BITE information (system report) and the test request (system test function) are available through the MCDU menus which allow to communicate with the ATIMS BITE via the CFDIU.
To gain access to the BITE, it is necessary to use one MCDU (Ref. AMM D/O 22-82-00-00).
All information displayed on the MCDU during the BITE test configuration can be printed.
The ATIMS maintenance menu is only accessible on the ground from the general maintenance menu and the SYSTEM REPORT/TEST page.
This mode enables communication between the CFDIU and the ATIMS BITE by means of the MCDU.

(b) LAST LEG REPORT page

ATIMS - LAST LEG REPORT Page ** ON A/C NOT FOR ALL

ATIMS - PREVIOUS LEGS REPORT Page ** ON A/C NOT FOR ALL

This report contains the fault messages related to the external or internal failures (Class 1 or 2) recorded during the previous 63 flight legs.

(d) LRU IDENTIFICATION page

ATIMS - LRU IDENTIFICATION Page ** ON A/C NOT FOR ALL

This menu enables the display for the identification of the various ATIMS components (ATSU and software packages). It is used to check the uploading of the correct software part number:

Part number and serial number of the ATSU (hardware case - FIN 1TX1)
Part number and serial number of DCDU1 and DCDU2 (FIN 2TX1 and 2TX2)
Part number of the SOFTWARE-ATSU A/C INTERFACE (FIN 20TX)
Part number of the SOFTWARE-ATSU CONFIGURATION (FIN 21TX)
Part number of the SOFTWARE-ATSU ROUTER PARAM (FIN 30TX)
Part number of the ATC HMI utilities software (25TX)
Part number of the ATSU ATC FANS A Applications software (35TX)
Part number of the ATSU ATC ARINC 623 Applications software (23TX)
Part number of the SOFTWARE-AOC DATABASE (FIN 24TX)
Part number of the SOFTWARE-AOC (FIN 22TX)

If one component is missing in a given configuration, the corresponding line is not displayed.

(e) GROUND SCANNING page

ATIMS - GROUND SCANNING Page ** ON A/C NOT FOR ALL

(f) TROUBLE SHOOTING DATA page

ATIMS - TROUBLE SHOOTING DATA Page ** ON A/C NOT FOR ALL

This function provides the correlation parameters and snapshot data concerning the failure displayed in the LAST LEG REPORT and the PREVIOUS LEGS REPORT pages.

(g) CLASS 3 FAULTS page

ATIMS - CLASS 3 FAULT Page ** ON A/C NOT FOR ALL

This menu enables the display of Class 3 faults recorded during the last flight leg.

(h) SYSTEM TEST page

ATIMS - SYSTEM TEST Page ** ON A/C NOT FOR ALL

The ATIMS BITE test is initiated when pressing the line key adjacent to the SYSTEM TEST indication.
The test ends with the display of the following message on the MCDU:

The TEST OK indication when all the tests are completed and no failure has been detected, or
The failure message(s) when one or more failures have been detected.

(i) GROUND REPORT page

ATIMS - GROUND REPORT Page ** ON A/C NOT FOR ALL

This function is used to present Class 1, 2 or 3 internal failures when they are detected on ground.
The relevant troubleshooting data are displayed by pressing the line key adjacent to the failure indication.
These failures differ from those displayed on the LAST LEG REPORT page.

(j) SPECIFIC DATA page

ATIMS - SPECIFIC DATA Page ** ON A/C NOT FOR ALL

This menu enables access to the different functions:

1L : LOAD STATUS (available in pre-FANS+ configuration only)
2L : PIN PROGRAMMING to check the ATSU configuration with its parity validity.

NOTE: The order of the pin programming display is in accordance with the one of the ATSU input connectors:
- A pin programming not defined (spare) is displayed with a zero value.
- An active pin programming is displayed with a 1 value.

3L : DUMP TSD
4L : SW P/N PRINT OUT.

(9) Normal mode
During the normal mode, the BITE:

monitors the ATSU status
monitors data inputs from the various ATIMS peripherals (FMGC, MCDU, CFDIU,...)
permanently transmits ATIMS system status and its identification message to the CFDIU.

(10) Menu mode

(a) System Report/Test Function

Access to the ATIMS SYSTEM REPORT/TEST Page ** ON A/C NOT FOR ALL

(b) LAST LEG REPORT page

ATIMS - LAST LEG REPORT Page ** ON A/C NOT FOR ALL

ATIMS - PREVIOUS LEGS REPORT Page ** ON A/C NOT FOR ALL

This report contains the fault messages related to the external or internal failures (Class 1 or 2) recorded during the previous 63 flight legs.

(d) LRU IDENTIFICATION page

ATIMS - LRU IDENTIFICATION Page ** ON A/C NOT FOR ALL

This menu enables to display the identification of the various ATIMS components (ATSU and Software packages). It is used to check the uploading of the correct software Part Number:

Part Number and Serial Number of the ATSU (hardware case - FIN 1TX1)
Part Number and Serial Number of the DCDU 1 and DCDU 2 (FIN 2TX1 and 2TX2)
Part Number of the SOFTWARE-ATSU A/C INTERFACE (FIN 20TX)
Part Number of the SOFTWARE-ATSU CONFIGURATION (FIN 21TX)
Part Number of the SOFTWARE-ATSU ATC HMI utilities (FIN 25TX)
Part Number of the SOFTWARE-ATSU ROUTER PARAM (FIN 30TX)
Part Number of the SOFTWARE-ISM APPLICATION (FIN 31TX)
Part Number of the SOFTWARE-ATSU FANS B APPLICATIONS (FIN 36TX)
Part Number of the SOFTWARE-ATSU CMA CONFIGURATION (FIN 37TX)

If one component is missing in a given configuration, the corresponding line is not displayed.

(e) GROUND SCANNING page

ATIMS - GROUND SCANNING Page ** ON A/C NOT FOR ALL

(f) TROUBLE SHOOTING DATA page

ATIMS - TROUBLE SHOOTING DATA Page ** ON A/C NOT FOR ALL

This function provides correlation parameters and snapshot data concerning the failure displayed in the LAST LEG REPORT and the PREVIOUS LEGS REPORT pages.

(g) CLASS 3 FAULTS page

ATIMS - CLASS 3 FAULT Page ** ON A/C NOT FOR ALL

This menu enables to display the Class 3 faults recorded during the last flight leg.

(h) SYSTEM TEST page

ATIMS - SYSTEM TEST Page ** ON A/C NOT FOR ALL

The ATIMS BITE test is initiated when pressing the line key adjacent to the SYSTEM TEST indication.
The test ends with the display of the following message on the MCDU:

TEST OK indication when all the tests are completed and no failure has been detected
or the failure message(s) when one or more failures have been detected.

(i) GROUND REPORT page

ATIMS - GROUND REPORT Page ** ON A/C NOT FOR ALL

(j) SPECIFIC DATA page

ATIMS - SPECIFIC DATA Page ** ON A/C NOT FOR ALL

This menu enables acces to different functions:

1L : LOAD STATUS (available in Pre-FANS+ configuration only)
2L : PIN PROGRAMMING to check the ATSU configuration with its parity validity.

3L : DUMP TSD
4L : SW P/N PRINT OUT

[Rev.10 from 2021] 2026.04.01 05:21:34 UTC