Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
manual
Notice
INFORMATION SUBJECT TO EXPORT LAWS
The technical data in this document (or file) is controlled for export under the Export
Administration Regulations (EAR), 15 CFR Parts 730-774. Violations of these laws
may be subject to fines and penalties under the Export Administration Act.
installation manual
DUE TO THE US GOVERNMENT’S IMPLEMENTATION OF EXPORT CONTROL REFORM (ECR), ALL EXPORT DATA PROVIDED IN THIS
PUBLICATION IS CURRENT AS OF THE LAST REVISION DATE AND MAY BE SUBJECT TO CHANGE BY ROCKWELL COLLINS. THERE-
FORE, PLEASE BE ADVISED THAT YOU ARE ENCOURAGED TO VALIDATE THE ACCURACY OF THE DATA PRIOR TO ANY FUTURE
EXPORT ACTIVITY RELATING TO THESE PUBLICATIONS.
PROPRIETARY NOTICE
© 2010, 2011, 2015, 2017, 2018 ROCKWELL COLLINS. ALL RIGHTS RESERVED
We welcome your comments concerning this manual. Although every effort has been made to keep it free of
errors, some may occur. When reporting a specific problem, please describe it briefly and include the manual part
number, the paragraph or figure number, and the page number.
EMAIL: pubstrain@rockwellcollins.com
TELEPHONE: 1.888.265.5467
INTERNATIONAL: 1.319.265.5467
FAX NO: 319.295.4941
EMAIL: response@rockwellcollins.com
.
T-2
INSERT LATEST CHANGED PAGES. DESTROY SUPERSEDED PAGES.
LIST OF EFFECTIVE PAGES NOTE: The portion of the text affected by the changes is indicated by a vertical line
in the outer margins of the page. Changes to illustrations are indicated by
shaded or screened areas, or by miniature pointing hands.
A/(B Blank)
TABLE OF CONTENTS
Chapter/Para Page
i
TABLE OF CONTENTS
Chapter/Para Page
3.3.1 Default Telephone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.3.2 No-Ring-On-Flaps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.3.3 Notification of Incoming Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.3.4 Transferring a Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.4 MCDU OPERATIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4.1 Overview.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4.2 Main Menu Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4.3 SAT-PHONE Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.4.4 SAT-PHONE Page Call Priorities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.4.5 SAT-PHONE Page 2/2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.4.6 MCDU History Page (SW REV-03 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.4.7 The Directory Page (SW REV-04 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.4.8 Directory Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3.4.9 Log Page (SW REV-04 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
3.4.10 Bite Status Page (SW REV-11 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
3.4.11 Configuration Page (SW REV-11 OR LATER).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
3.4.12 Flight Deck Voice Channel Redundancy (SW REV-04 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
3.4.13 Follow-on Dialing from the MCDU (SW REV-04 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
3.4.14 EICAS Interface (SW REV-04 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
3.4.15 MCDU Calls with Priority (SW REV-04 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
3.4.16 MCDU Passwords.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
3.5 DIALING PLANS AND CODES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
3.5.1 North American Dialing Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
3.5.2 International Dialing Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
3.5.3 Making Calls to Iridium Phones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
3.6 VOICE PROMPTS (SW REV-04 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
3.6.1 Overview.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
3.6.2 Lower Priority Call Pre-Emption Voice Prompt (SW REV-04 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
3.6.3 Customizing a Voice Prompt.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
3.6.4 Playing Back a Voice Prompt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
3.6.5 Saving all Prompts to Flash. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
3.7 IRIDIUM INTERNET CONNECTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
3.8 INTERNATIONAL COUNTRY CODES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
3.9 DIRECT INWARD STATION ACCESS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
3.9.1 Overview.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
3.9.2 The DISA Voice Prompt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
4 Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1 GENERAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 SOFTWARE.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2.1 IRT-2110/2120 and ICS-120A/220A Data Files (SW REV-04 OR LATER).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2.2 The Voice Prompt File (SW REV-04 OR LATER).. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.2.3 The IRT-2110/2120 and ICS-120A/220A Configuration File (SW REV-04 OR LATER). . . . . . . . . . . . . . . . . . . . . . 4-4
4.2.4 Uploading and Downloading the Data Files.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.2.5 Initializing the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.2.6 Upgrading the Firmware and Configuration File.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.3 THE IRT-2110/2120 AND ICS-120A/220A MENU SYSTEM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.3.1 Starting HyperTerminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.3.2 Navigating through the HyperTerminal Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.3.3 The Main Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.3.4 ICS-120A/220A Menu Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
4.4 CONFIGURING THE SYSTEM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.4.1 Overview.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.4.2 4-Wire Ports Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
ii
TABLE OF CONTENTS
Chapter/Para Page
4.4.3 The Stations Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4.4.4 The Trunks Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
4.4.5 Hunt Groups Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
4.4.6 Inbound Hunt Group Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
4.4.7 Outbound Hunt Group Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
4.4.8 I/O Pins Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
4.4.9 RS232 Data Interface Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
4.4.10 The PIN Table Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
4.4.11 System Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
4.4.12 ARINC 429 Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
4.4.13 MCDU Options Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
4.5 MONITORING THE SYSTEM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
4.5.1 System Information Monitor Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
4.5.2 Stations Monitor Screen.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
4.5.3 I/O Pins Monitor Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67
4.5.4 ARINC-429 Monitor Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
4.6 SYSTEM LOGGING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73
4.6.1 Overview.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73
4.6.2 Log Time Stamp Format (SW REV-04 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
4.6.3 Working with Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
4.6.4 ACARS Log (SW REV-04 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
4.6.5 Internal Logging (SW REV-06 OR LATER). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
4.7 TROUBLESHOOTING.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
4.7.1 LED Behavior During Boot Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
4.7.2 Understanding and Using the LEDs.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
4.7.3 Troubleshooting Stages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
4.7.4 Frequently Asked Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-177
4.7.5 ARINC 429 Data Words. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-181
4.7.6 Known Problem with the Windows USB Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184
4.8 AIR WORTHINESS.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184
4.8.1 Airworthiness.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184
Appendix A Equipment Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
A.1 EQUIPMENT CHARACTERISTICS.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Appendix B Iridium ATS Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
B.1 USE OF IRIDIUM ATS VOICE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
B.1.1 Priority Levels for SATCOM Voice Calls.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
B.1.2 Update AOC or ATS Directory File for ATS Voice Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
B.1.3 Configuration Update for ATS Voice Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
B.1.4 ATS Voice Operators Guide Information Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
B.1.5 Caller Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
B.1.6 Caller Priority.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
B.1.7 Call Pre-emption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
B.1.8 ATS Voice Operators Guide Information Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
B.1.9 ARINC 429 Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
B.1.10 Inbound Hunt Group Call Routing Update.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
B.1.11 Software Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13
B.1.12 ATS Voice updated MCDU Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17
B.1.13 MCDU PAGE FLOW - USE CASES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17
iii
LIST OF ILLUSTRATIONS
iv
LIST OF ILLUSTRATIONS
v
LIST OF ILLUSTRATIONS
vi
LIST OF ILLUSTRATIONS
vii
LIST OF ILLUSTRATIONS
viii
LIST OF TABLES
ix
LIST OF TABLES
x
INTRODUCTION
1. GENERAL.
This Installation Manual (IM) provides installation and maintenance information regarding the Iridium Communications System.
Elements found outside of this manual follow:
• For individual low-level component servicing information, refer to the particular Component Maintenance Manual (CMM).
• A publications index is available on-line at www.rockwellcollins.com. You may also register for an account there, so that you can
view and download those manuals that support your aircraft. For further assistance contact the Technical Publications department
as specified on page T2.
The list that follows shows the abbreviations, acronyms, and mnemonics that are used in this publication to describe the avionics
system.
ACARS Aircraft Communications Addressing and Reporting System
AFIS Aerodrome Flight Information Service
AMS Audio Management System
AMU Audio Management Unit
ANSP Air Navigation Service Provider
AOC Aeronautical Operation Control
ARINC Aeronautical Radio Inc.
ATC Air Traffic Control
ATG Air-to-Ground
ATP Aircraft Test Plan
ATS Air Traffic Services
CDU Control Display Unit
CIM Configuration Identity Module
CLI Command Line Interface
CMM Component Maintenance Manual
CMU Communications Management Unit
xi
introduction
xii
introduction
SP Service Provider
SVGM Satellite Voice Guidance Materials
TDD Time Division Duplex
TNC Threaded Neill Concelman
TRS Transceiver
TX Transmit
USB Universal Serial Bus
VDC Volts Direct Current
VHF Very High Frequency
Rockwell Collins
350 Collins Rd NE, M/S 153-250
Cedar Rapids, IA 52498-0001
xiii/(xiv Blank)
SAFETY SUMMARY
OBSERVE STANDARD SAFETY PRECAUTIONS AND WEAR SAFETY GLASSES AND OTHER PROPER
SAFETY GEAR TO PREVENT PERSONAL INJURY DURING INSTALLATIONS.
TURN OFF POWER BEFORE DISCONNECTING ANY COMPONENT FROM WIRING. DISCONNECTING
THE COMPONENT WITHOUT TURNING POWER OFF MAY CAUSE VOLTAGE TRANSIENTS THAT
CAN DAMAGE THE COMPONENT.
WHILE THE IRT-2110, IRT-2120, ICS-120A AND ICS-220A ARE NOT CLASSIFIED AS STATIC
SENSITIVE DEVICES, GOOD SHOP PRACTICES SHOULD BE FOLLOWED WHEN HANDLING AND
INSTALLING ALL EQUIPMENT. USE OF GROUNDED CONDUCTIVE SURFACES AND ANTISTATIC
MATERIALS IS RECOMMENDED.
xv
safety summary
IF THE IRT-2110/2120 and ICS-120A/220A CHASSIS IS OPENED ITS WARRANTY IS VOIDED. UNDER
NO CIRCUMSTANCES SHOULD THE IRT-2110/2120 and ICS-120A/220A CHASSIS BE OPENED BY ANY-
ONE OTHER THAN A CERTIFIED REPAIR TECHNICIAN IN A CERTIFIED REPAIR ENVIRONMENT
WITH THE EXPRESS CONSENT OF ROCKWELL COLLINS.
DO NOT INSTALL IN LOCATIONS WHERE UNIT MAY COME IN DIRECT CONTACT WITH FLUIDS
SUCH AS SKYDROL. SEE DDP (P/N 710700 Rev A and 710706 Rev D) FOR FLUID SUSCEPTIBILITY
CLASSIFICATION.
NOTE
Highlights an essential operating or maintenance procedure, condition, or statement. The stand-alone User’s Guide
(P/N 710701G) gives a basic overview of the system and its capabilities for the ICS-120A/220A user. It also
provides general instructions for using the unit’s basic telephony and data services. Please refer to that document
for basic functions.
xvi
CHAPTER 1
General Information
1.1. INTRODUCTION.
This chapter lists each piece of Rockwell Collins equipment, explains what it does at a high level, and how the equipment works
with other equipment in the system. This chapter gives an overall description of the system, including a system interfaces.
1.2. EQUIPMENT.
The equipment covered table lists the aircraft avionics and avionic software. The Associated Equipment table lists the aircraft
mounts.
1.2.1. Equipment Covered.
Refer to Table 1-1 for a complete list of the Rockwell Collins avionics equipment covered in this manual.
1-1
general information
1-2
general information
1-3
general information
FEATURE INTERFACE
Input/Output (I/O) Support (8/8) External
2-Wire Ports (4) External
4-Wire Ports (2) w/E&M signaling External
Configurable 3-Wire/9-Wire interface External
ARINC 429 Interface (3 Transmit (TX) and 6 Receive (RX)) External
USB Port External
LBT Voice/Data: A3LA-SA (-1 models); 9522B (-2 models) Internal
ICS-120A (1), ICS-220A (2)
SBD Modem 9601 (-1 models) (1); 9602 (-2 and -3 models) (1) Internal
1-4
general information
FEATURE INTERFACE
RS232 Port (1 on -1 models, 2 on -2 models) External
Fax (only available on 730616-2, 730617-2, and 740617-2) External
NOTE
Most units report maintenance information in a diagnostic word to the built-in diagnostic system. This section does
not refer to these diagnostic words. Refer to the maintenance section of this manual for diagnostic information.
The system schematics are not intended to replace bench level repair coverage. Component level coverage is
provided in the applicable repair manual.
1-5
general information
NOTE
The MCDU Audio ports on -2 models come equipped with mic bias. -2 Models will also have a second RS-232
port that is activated and configured in the Configuration Editor.
The ICS-120A/220A provides up to four 2-wire connections for telephone handsets or CTU systems and up to two 4-wire audio
connections or CTU systems with associated discrete “hook” and “incoming-ring” signals. The -2 models come equipped with mic
bias. The ICS units use a Subscriber Line Interface Connection (SLIC) to connect the 2-wire devices. The SLIC provides 48 Volts
Direct Current (VDC) of loop battery to power the telephone circuits and a high-voltage ring signal to permit the handsets to ring.
A conventional telephone circuit removes the concern about cable distances and noise when planning the layout of the handsets in
the aircraft cabin. The device’s internal circuits convert the analog audio signals on the 2-wire or 4-wire audio circuits to a standard
Pulse Code Modulation (PCM) digital format and provide connection to the Iridium transceivers. Under microprocessor control, the
1-6
general information
ICS-120A/220A communicates with the Iridium transceiver and network as it provides conventional telephony operations. The unit
also incorporates audio signal processing using a Digital Signal Processor (DSP) that provides local dial tone and other telephony
progress tones as well as such features as conferencing, audio-level adjustments, and digital echo suppression. “F” model units also
incorporate a fax connection, refer to Paragraph 2.2.3 for more details. See Figure 1-4 for Iridium Communications Interfaces. The
ICS-120A/220A enables communication functions on the ground or in flight, as long as the aircraft has an unobstructed view of the
sky 360° and 8° above the horizon. The ICS-120A/220A provides:
• Flexibility in installation. It can be installed in an Electronics Bay (E-Bay), cabin, or other location in an aircraft.
• Subscriber audio circuit connections, four 2-wire circuits for connections of POTS Tip/Ring-type telephones or external CTU
systems, and two 4-wire circuits for connections to Rockwell Collins Jetphone handsets or the flight deck audio system.
• Provides: provisions for MCDU dialing using ARINC 739A-compliant devices.
• CTU features such as call transfer, extension-to-extension calling, and 3-party conferencing.
• Provides: Configuration Interface Module (CIM), an externally mounted SIM reader to allow true Line Replaceable Unit (LRU)
functionality.
• One serial data port for data connections in models 710616-1 and 710617-1. Two serial data ports in models 710616-2, 710617-2,
713616-2, 713617-2, 720616-2, 720617-2, 730616-2, 730617-2, 740617-2, 710616-3, 710617-3 and 713617-3.
• 3 Transmit and 6 Receive ARINC 429 interfaces.
• Fax (only available on 730616-2, 730617-2, and 740617-2).
• Provides ATS safety voice preemption and priority features for models 710616-3, 710617-3 and 713617-3.
• Installation Kit consisting of an ARINC 2-MCU tray and connector, Iridium antennas, and coaxial antenna interface cables.
1-7
general information
1-8
CHAPTER 2
System Components
2.1. INTRODUCTION.
This chapter describes each Line Replaceable Unit (LRU).
2.1.1. LRUs.
This chapter presents all the information for each LRU in the IRT subsystem. Each LRU is marked with a tab. The tabs are in
alphabetical order. General descriptions of each LRU are in chapter one.
NOTE
The information is provided for both the part numbers ICM (822-2836-001/-101/- 201)/CIM (327800)
NOTE
Whenever the configuration is modified, the changes must be saved to the ICS unit and then save using the
ICM/CIM Editor screen and the unit must be rebooted.
These data files should be downloaded to a Personal Computer (PC) as a backup in case of ICM/CIM failure.
2.2.1.2. The ICM/CIM also functions as the remote Subscriber Identity Module (SIM) card reader that allows the IRT-2110/2120
and ICS-120A/220A to operate with the SIM cards stored externally in this module. This capability facilitates field replacements
without the need to manually remove and re-install the SIM cards. The SIM cards in this configuration are installed in the ICM/CIM,
which must be wired to the IRT-2110/2120 and ICS-120A/220A installation tray.
2-1
system components
2.2.1.3. Refer to Table 2-1 for ICM/CIM Wiring Termination and Figure 2-1 that show the connection between the ICM/CIM and
the unit Install Kit (Wire Insertion Side).
2-2
system components
2.2.1.4. See Figure 2-2 for ICM/CIM Interface Cable. Refer to Table 2-2 for Wire Termination Chart and Table 2-3 for Parts List.
2-3
system components
2-4
system components
CABLE COLOR DB-15 ARINC ARINC 501771 RING WIRE DESCRIPTION PART
INSERT INSERT (SHIELD TERMI- LENGTH NUM-
DESIG- (ARINC)
A B ARINC NAL BER
NATOR
SIDE)
A WHITE 12 - A4 - - 36 in. SIM PWR2 211098
(914.4 mm)
A WHITE/ 3 - - - 36 in. N/C 211098
BLUE (914.4 mm)
A GREEN - - - SA RT 6 in. - 211013
(152.4 mm)
B WHITE 4 - A6 - - 36 in. SIMTX2 211098
(914.4 mm)
2-5
system components
CABLE COLOR DB-15 ARINC ARINC 501771 RING WIRE DESCRIPTION PART
INSERT INSERT (SHIELD TERMI- LENGTH NUM-
DESIG- (ARINC)
A B ARINC NAL BER
NATOR
SIDE)
B WHITE/ 5 - A5 - - 36 in. SIM RX2 211098
BLUE (914.4 mm)
B GREEN - - - SA RT 6 in. - 211013
(152.4 mm)
C WHITE 7 C7 - - - 36 in. SIM TX1 211098
(914.4 mm)
C WHITE/ 8 C6 - - - 36 in. SIM RX1 211098
BLUE (914.4 mm)
C GREEN - - SA RT 6 in. - 211013
(152.4 mm)
D WHITE 1 B11 - - - 36 in. SIM PWR1 211098
(914.4 mm)
D WHITE/ 2 B12 - - - 36 in. GND 211098
BLUE (914.4 mm)
D GREEN - - - SA RT 6 in. - 211013
(152.4 mm)
E WHITE 10 C12 - - - 36 in. ICM/CIM TX1 211098
(914.4 mm)
E WHITE/ 11 C11 - - - 36 in. ICM/CIM RX1 211098
BLUE (914.4 mm)
E GREEN - - - SA RT 6 in. 211013
(152.4 mm)
F WHITE 13 C5 - - - 36 in. +12 VDC 211098
(914.4 mm)
F WHITE/ 14 C4 - - - 36 in. PWR GND 211098
BLUE (914.4 mm)
F GREEN - - - SA RT 6 in. - 211013
(152.4 mm)
N/A - 6 - - - - - - -
2-6
system components
CABLE COLOR DB-15 ARINC ARINC 501771 RING WIRE DESCRIPTION PART
INSERT INSERT (SHIELD TERMI- LENGTH NUM-
DESIG- (ARINC)
A B ARINC NAL BER
NATOR
SIDE)
N/A - 9 - - - - - - -
N/A - 15 - - - - - - -
2.2.1.5. Refer to Table 2-4 for CIM Bonding Requirements Parts List and see Figure 2-3 for CIM Bonding Requirements.
NOTE
DB-15 Connectors (J1) terminates onto CIM module.
Refer to labels placed on cable (327383) for installing ARINC pins into ARINC connector.
Ring terminal is to be secured to ARINC block using existing 6-32 hardware at location shown.
Item 1 is shown from rear of tray.
Refer to Difference To Depth Modulation (DDP) 327700 for bonding requirements for item 2.
2-7
system components
PARTS LIST
ITEM QTY PART NUMBER DESCRIPTION
1 1 710620 2-MCU INSTALL KIT
2 1 327000 TOP LEVEL, CIM
3 1 327383 CIM INTERFACE CABLE
2-8
system components
2-9
system components
2-10
system components
2-11
system components
2.2.2.1. ICM/CIM Module LEDs. The ICM/CIM Module contains three Light Emitting Diode (LED). These LEDs are power
indicators for the Configuration Board (LED D5), SIM slot 1 (LED D2), and SIM slot 2 (LED D3). The LEDs have two states, ON
(green) or OFF (no color), to indicate power. See Figure 2-7.
2-12
system components
POWER DOWN THE IRT-2110/2120 AND ICS-120A/220A UNIT BEFORE INSTALLING THE SIM CARDS.
FAILURE TO DO SO MAY DAMAGE THE SIM CARDS.
See Figure 2-8 for screws holding front cover in place over sim card slots, Figure 2-9 for front cover removed showing the sim card
slots and Figure 2-10 for one sim card holder raised. To insert the SIM cards into the ICM/CIM:
a. Power down the IRT-2110/2120 and ICS-120A/220A unit before installing the SIM cards.
b. Remove the front cover of the ICM/CIM.
2-13
system components
Figure 2-8. Screws Holding Front Cover In Place Over SIM Card Slots
Figure 2-9. ICM/CIM with Front Cover Removed Showing the SIM Card Slots
2-14
system components
c. Lift both SIM card holders, see Figure 2-11 (for an IRT-2120/ICS-220A only. An IRT-2110/ICS-120A will only need SIM
Card slot #1).
2-15
system components
d. Insert the SIM cards into the slots, making sure the clipped corner of the card is in the proper position, see Figure 2-12.
e. Push the cards down into their holders so the tops of the cards are even with the tops of the holders, see Figure 2-13.
2-16
system components
f. Push the cards and their holders down parallel to the surface of the ICM/CIM to seat them within the ICM/CIM, see Figure
2-14.
g. Slide the bar on each card holder down until the holder clicks, see Figure 2-15 and the SIM cards are locked in place, see Figure
2-16.
2-17
system components
Figure 2-16. Both SIM Cards Seated Properly and Locked in Place
NOTE
All SIM cards have their pin requirements removed at Rockwell Collins prior to shipping.
a. Using HyperTerminal or an equivalent application, push CTRL-C to bring up the command line interface.
b. Enter the below listed commands as needed (type in all lower-case). To de-pin the SIM card for transceiver #1: connect lbt1 to
de-pin the SIM card for transceiver #2 (in the IRT-2120/ICS-220A only):connect lbt2.
c. Use the below listed AT command sequence once a serial connection has been made to the desired transceiver:
1. Command: AT
2. Response: OK
3. Command: AT+CPIN?
4. If pin is unlocked, Response: +CPIN: READY or +CPIN: SIM PIN2. If pin is locked, Response: +CPIN: SIM PIN
5. Command: AT+CPIN=1111
6. Response: OK (may take up to 20 seconds)
7. Command: AT+CLCK=SC,0,1111
8. Response: OK (may take up to 20 seconds)
2-18
system components
2-19
system components
2-20
system components
2.2.3.3. Iridium Fax (SW REV-09 OR LATER). This section describes only F model units are equipped with fax. Refer to
Table 2-6 for Iridium Fax Connections.
2-21
system components
NOTE
Serial Port 1 is multiplexed with the Iridium Fax and internally routed to LBT 1. If the installation requires a
fax over Iridium capability and also periodic use of serial port 1 by an external application, then the ICS must be
configured for 9-wire operation for serial port 1, as 9-wire is required by the internal fax module.
INSERT A
INSERT A PIN DESCRIPTION
A11 TIP FAX
B12 RING FAX
A13 SHIELD
2-22
system components
2.3.1.2. Inputs and Outputs. The IRT-2110/2120 and ICS-120A/220A has eight inputs and eight outputs with the below listed
pinouts (refer to Table 2-8 and Table 2-9).
2-23
system components
2.3.1.3. Interface Connections. The IRT-2110/2120 and ICS-120A/220A has a back-panel ARINC 600 Size 1 connector. The
unit provides the below listed circuits:
• Four 2-wire signal circuits.
• Two 4-wire E&M signal circuits.
• Two RS-232 serial port for data communications or Internet access (on model 710617-2).
• One RS-232 serial port for data communications (on models 710616-2).
• Three Tx and six Rx ARINC 429 dual-speed ports.
• ICM module.
• CIM module.
• Mic bias enable.
• Fax Tip & Ring.
• Eight programmable ground/open discrete inputs and outputs.
2.3.1.3.1. Telephony Circuits. As with any telecommunications system, the customer must select a Service Provider from among
the companies that offer Iridium satellite services. Service Providers offer differing pricing and services and have distinct coding on
their SIM cards for recognition by the separate satellite networks. Because of these unique interaction protocols, Rockwell Collins
requires advance notification of the selected Service Provider, and registration/billing information must be pre-arranged with the Ser-
vice Provider for activation of service in order for the ICS to be shipped with the pre-programmed SIM card. The Iridium satellite
network allows access at any time. Refer to Table 2-10 for 2-Wire Audio Circuit Devices and Table 2-11 for 4-Wire Dual-Function
Connection.
2-24
system components
NOTE
The 4-wire ports may be configured as either stations or trunks.
2.3.1.3.2. Mic Bias. Mic bias is a featured added to the all -2 units. Mic bias is used as a requirement for some 4-wire headsets
that requires a DC power source. Mic bias is by default disabled. There are two mic bias circuits in the -2 units: Mic Bias 1 and
Mic Bias 2. Each consists of two ARINC 600 block inserts, (refer to Table 2-12) for Mic Bias port details. Mic bias 1 provides
mic bias for 4-wire port 15. Mic bias 2 provides mic bias for 4-wire port 16. To enable mic bias 1 or 2 simply connect the enable
insert to the return insert. i.e. to enable mic bias on 4-wire port 16, connect Enable Mic Bias 2 (ARINC Insert A: D14) to Return
Mic Bias 2 (ARINC Insert A: D15) using size 22 crimp removable pin contacts and an appropriately sized length of wire. Prior
to enabling the Mic bias provided by the ICS-120A/220A, installers must review the available Audio Control system component
features and associated wiring diagrams to confirm if Mic bias will be provided by an external component or via the ICS-120A/220A
audio circuits.
2-25
system components
MIC BIAS
ARINC INSERT A
PIN DESCRIPTION PORT
B14 MIC BIAS ENABLE 1 MIC BIAS 1 4-WIRE PORT 15
B15 MIC BIAS RETURN 1
D14 MIC BIAS ENABLE 2 MIC BIAS 2 4-WIRE PORT 16
D15 MIC BIAS RETURN 2
2.3.1.3.3. ARINC 429 Data Link Ports. The specific interfaces the unit provides are the ARINC 429 DataLink (required to
connect and communicate with the aircraft portion of the Aircraft Communications Addressing and Reporting System (ACARS)
system) and the Iridium Network communications link (necessary to transmit and receive data over the Iridium data link).
2.3.1.3.3.1. The first interface is the ARINC 429 connection to the aircraft’s ACARS-compliant Data Management Unit (DMU).
The DMU manages the message data being transmitted to the ACARS Service Provider. It also manages the responses to requests
and the normal up-linked messages used in the operation of the aircraft. See Figure 2-21 for ACARS DMU Interfaces for IRT-
2110/2120 and Figure 2-22 for ACARS DMU Interfaces for ICS-120A/220A.
2-26
system components
2.3.1.3.3.2. Using the Iridium utility, the ACARS messages can be monitored to confirm that the IRT-2110/2120 and
ICS-120A/220A is receiving and transmitting messages properly. The utility also has a logging function for these messages. Refer
to appropriate sections of this manual for instructions on the use of the logging and monitoring functions.
2.3.1.3.3.3. Once the DataLink ports have been connected, the ACARS service can be installed and the functionality tested.
2.3.1.3.3.4. Rockwell Collins Data Link Product Connections. Refer to Table 1-2 for details about the Radio Interface
Unit (RIU) and Communications Management Unit (CMU) part numbers. Refer to Table 2-13 for connections on the Rockwell
Collins RIU.
2.3.1.3.3.5. Honeywell AFIS Data Link Product Connections. The Honeywell Datalink product is the Aerodrome Flight
Information Service (AFIS) DMU, part number 400-0455 00-2011. This has a low speed ARINC 429 bus. Refer to Table 2-14 for
connections on the Honeywell DMU.
2-27
system components
2.3.1.3.3.6. Other Data Link Product Connections. The DMU/Management Unit (MU) described in Table 2-15 and Table
2-16 are 758 compliant.
2.3.1.3.3.7. The DMU/MU described in Table 2-17, Table 2-18 and Table 2-19 are 724B compliant.
2-28
system components
Table 2-18. 724B-Compliant DMU/MU Data Link Product Connections for IRT-2110/2120.
Table 2-19. 724B-Compliant DMU/MU Data Link Product Connections for ICS-120A/220A.
2.3.1.3.4. ARINC 429 CIRCUITS. The IRT-2110/2120 and ICS-120A/220A SDU provides three TX circuits and six RX AR-
INC 429 circuits. Each ARINC 429 circuit is individually configurable for high-speed (100 kbps) or low-speed (12.5 kbps) operation.
Per system configuration, CMU/DMU and MCDU devices can be interfaced to any mix of ARINC 429 circuits, as required. Its con-
nections are listed in Table 2-20 and Table 2-21.
2-29
system components
2-30
system components
2.3.1.3.5. Audio Discretes (MCDU Only). There are three audio discretes:
2.3.1.3.5.1. Discrete (1) – Ring Output: The IRT-2110/2120 and ICS-120A/220A Satellite Data Unit (SDU) provides a ground
on the Ring Output to the Audio Management Unit (AMU) when there is an Incoming Call Indication. The Ring Output remains
grounded until the call is ended. When the call ends, the Ring Output returns to open state. See Figure 2-23.
NOTE
This method of ending a call is only applicable when the Audio Management System (AMS) mode is set to Latched
Mic-On; refer to Paragraph 4.4.2 for more information on how to configure the AMS mode.
2.3.1.3.5.2. Discrete (2) – Hook Input: When the IRT-2110/2120 and ICS-120A/220A (SDU) senses a ground on the hook input
signal from the AMU, off hook indication, the incoming call is answered. When the hook input is opened, on hook indication, the
active call is ended. See Figure 2-24.
2.3.1.3.5.3. Discrete (3) – MAWEA Output: The IRT-2110/2120 and ICS-120A/220A (SDU) provides a ground to the Modu-
larized Avionics Warning Electronics Assembly (MAWEA) to activate the chime. The MAWEA discrete output is grounded when
there’s an incoming call indication, and returns to open state when the call is answered (off hook Indication). The MAWEA output
is only activated for incoming calls (ground-to-air).
2-31
system components
2.3.1.4. Aircraft Power. Standard aeronautical wiring practices are required when connecting power to the IRT-2110/2120 and
ICS-120A/220A units. See Figure 2-25 for wiring information. Its power pins are described in Table 2-22.
NOTE
The IRT-2110/2120 and ICS-120A/220A provides ancillary fused voltage connections. Check the manufacturer’s
literature for guidance on voltage/amperage tolerances of ancillary devices.
2-32
system components
INSERT C
PIN DESCRIPTION
2 +28 VDC nominal aircraft power
3 SHIELD
4 GROUND
2.3.1.5. RS-232 Serial Port. Refer to Table 2-23 and Table 2-24 to connect the serial data port.
INSERT A SIGNAL
D4 DCD
D5 RD
D6 TD
D7 DTR
D8 GROUND
D9 DSR
D10 RTS
D11 CTS
D12 RI
D13 SHIELD
2-33
system components
INSERT A SIGNAL
A10 DCD
A11 RD
B11 TD
C9 DTR
C11 GROUND
A12 DSR
B12 RTS
C10 CTS
C12 RI
B7 SHIELD
2.3.1.6. Activating the ACARS Service. The ACARS service requires an ACARS Service Provider (for example, ARINC
Direct) that will forward or respond to messages from the aircraft. The ICS-120A/220A features configurable internal hardware re-
dundancy for ACARS communications. In the event that a persistent hardware failure is detected, the system automatically switches
the ACARS communications to a different transceiver, ensuring ACARS operation is not interrupted. The SBD modem device is al-
ways by default dedicated to ACARS communications, and the other Iridium transceiver(s) can be used as backup. For installations
interested in utilizing the hardware redundancy feature for ACARS communications, the IMEIs for all Iridium transceivers need to
be provisioned by the DataLink Service Provider. The steps for activating and testing the ACARS function are outlined in Table
2-25, below.
NOTE
Users cannot have a different Service Provider (SP) for High Frequency (HF), Very High Frequency (VHF), and
Satellite Communications (SATCOM). The SP information is embedded in the ACARS message and cannot be
modified by the unit.
For installations where hardware redundancy is desired, one must ensure that the primary Flight Deck voice chan-
nel is unimpeded at all times. DataLink redundancy always overrides the secondary voice channel when the
redundancy is enabled, typically the second Iridium transceiver LBT-2.
2-34
system components
2.3.1.7. ACARS on “B” Model Units. ICS-120B and ICS-220B units can be configured to provide ACARS communications
by enabling the ACARS DataLink Configuration State and the SBD HW Redundancy settings. When ACARS communications is
enabled in a “B” unit, the system routes the ACARS SBD messaging through a dedicate Iridium transceiver, and prevents voice or
data calls from sharing that transceiver. In ICS-220B systems, the system dedicates LBT-2 for ACARS communications (if enabled).
While ACARS is an available option on the 120B and 120BF, if ACARS is enabled on these units voice and fax channels will not
be available.
2-35
system components
NOTE
See Figure 2-26 through Figure 2-28 dimensions and tolerances are per ASME Y14.5M-1994, they are designed to
meet the applicable requirements of ARINC 600-12: 2 MCU (exceptions and limitations to ARINC 600: Non-AR-
INC connector cut out location), RTCA/DO-160D ENV. CAT[(A2)-]BAB[S(B2)]XXXXXXXXXXXXXXXXX,
and the tray and connector plate finish is: CLEAR CHEM FILM PER MIL-C-5541, CLASS 3.
See Figure 2-26 for top-level illustrations. See Figure 2-27 for the Installation Tray Assembly, refer to Table 2-26 for suggested
installation tray assembly part number, and see Figure 2-28 for the Tray Detail.
2-36
system components
2-37
system components
2-38
system components
2-39/(2-40 Blank)
system components
2-41/(2-42 Blank)
system components
Table 2-28. Serial Port 2 Connections ARINC 600 Pinout for ICS-120A/220A.
SERIAL PORT 2
INSERT B
PIN DESCRIPTION
A10 DCD
A11 RD
B11 TD
C9 DTR
C11 GROUND
A12 DSR
B12 RTS
C10 CTS
C12 RI
B7 SHIELD
2-43
system components
Figure 2-29. ARINC 600, IRT-2110/2120 and ICS-120A/220A Mating Connectors (Sheet 1 of 2)
2-44
system components
Figure 2-29. ARINC 600, IRT-2110/2120 and ICS-120A/220A Mating Connectors (Sheet 2 of 2)
2-45
system components
2-46
system components
2-47
system components
2-48
system components
2-49
system components
2-50
system components
2-51
system components
2.3.4. Installation.
DO NOT INSTALL THE IRT IN LOCATIONS WHERE UNIT MAY COME IN DIRECT CONTACT WITH
FLUIDS FOR EXAMPLE, SKYDROL. REFER TO DDP (P/N 710700) FOR FLUID SUSCEPTIBILITY
CLASSIFICATION.
The IRT-2110/2120 and ICS-120A/220A is rack mounted. Refer to Table 2-29 that shows a high-level view and the major steps
involved in the installation process. Details are in the sections below. Installers should review this manual thoroughly along with
any industry-established electronic equipment practices prior to installing this unit.
2.3.4.1. Installation. Refer to Table 2-29 for the procedure to install the unit.
2-52
system components
2.3.4.2. Iridium Receiver Transmitter and Iridium Communication System Mounting Location. The IRT-2110/2120 and
ICS-120A/220A is mounted using an ARINC 2-MCU aeronautical tray and can be installed in the aircraft’s Equipment Bay (E-Bay),
in the cabin area, or in the non-controlled environment outside of the aircraft’s pressure envelope. Mount the IRT-2110/2120 and
ICS-120A/220A as close to the antenna as practical. Minimal cable runs improve system performance.
NOTE
Do not install in locations where unit may come in direct contact with fluids such as Skydrol. DDP (P/N 710700
Rev A for -1 models or 710706 Rev D for -2 and -3 models) for fluid susceptibility classification.
2-53
system components
2-54
system components
NOTE
The IRT-2110 or IRT-2120 and ICS-220xx models will require two single-element Iridium antennas (either two S-67-1575-
109 or two CL490-1, above) to operate correctly.
NOTE
Under no circumstances shall the coaxial cable loss exceed 3 dB.
2.4.1.1. Band Pass Filter. If the aircraft also has an Inmarsat Satcom terminal co-resident with an ICS-120A/220A system,
an optional Iridium band pass filter (Rockwell Collins 500918) may be installed to help reduce potential interference between the
Inmarsat and Iridium systems. Iridium performance can be significantly affected while the Inmarsat Satcom system is transmitting
2-55
system components
possibly resulting in dropped calls or an inability to place Iridium calls. This interference is caused by the lack of a “guard” band
between the Iridium and Inmarsat frequencies (see Figure 2-37), coupled with the significantly higher power of the Inmarsat antenna
system. The severity of this interference on any given aircraft may vary considerably based upon the separation between antennas,
the type and age of Inmarsat Satcom and Antenna systems, as well as the heading of the aircraft at any given time. Typically the
worst performance is seen when an older Inmarsat Satcom terminal (which would present a greater level of noise outside of the
frequency band), is transmitting directly across the Iridium antenna. While an Iridium Band Pass filter may reduce interference,
it is important to consider that the primary source of interference is presented by the Inmarsat system. Manufacturer options may
vary and therefore, Rockwell Collins recommends contacting the Satcom manufacturer and discussing which measures are available
to limit or eliminate this interference: such as improved DLNA performance or Inmarsat band filtering. When calculating coaxial
cable requirements—to maintain a maximum overall loss of -3 dB between Antenna and the Iridium system installation tray—one
must be sure to include the typical average loss of - 2 dB caused by the Iridium Band Pass filter. Within co-resident installations
where both an Iridium system and an Inmarsat are present and critical DataLink Safety Services are required via these networks, it is
recommended that the systems be configured to allow for Inmarsat as the Primary media with Iridium as the Secondary (slave) media
for installations where Inmarsat interference could not be completely overcome. In many cases, a compass swing of the aircraft while
capturing Iridium system received signal averages may be advantageous in understanding the affects of Inmarsat interference within
a given installation. Refer to Paragraph 2.4.1.2 for general Iridium antenna mounting considerations.
NOTE
The filter is not required if an Inmarsat Aero SATCOM is not present.
2.4.1.2. Antenna Installation. Antenna installation must comply with applicable Federal Aviation Regulation (FAR). As a min-
imum, the antenna installation must meet Federal Aviation Administration (FAA) FAR 23.571 or FAA FAR 25.571. Follow the
antenna manufacturer’s instructions for recommended antenna placement as long as they do not conflict with the aircraft manufac-
turer’s instructions. Refer to Table 2-32 for Antenna Connections.
2-56
system components
NOTE
Consult the antenna manufacturer’s installation manual for the proper antenna installation procedures.
Antennas must be bonded to the airframe for static and lightning protection. Check the aircraft manufacturer’s
instruction manual for recommended antenna bonding practices.
INSERT C
PIN DESCRIPTION
1 L-Band Transceiver (LBT) 1 and 2
5 SBD Modem (ACARS)
2.4.1.2.1. FAA Regulatory Approval. Any aircraft penetration must be officially inspected and approved. This inspection is
generally performed by an FAA-authorized Designated Engineering Representative (DER) and is documented on FAA Form 8110-3.
The completed form should be included with the installation certification data.
NOTE
Consult the aircraft manufacturer’s installation manual for the proper procedures for any airframe penetrations.
2.4.1.2.2. Antenna Bonding. Antennas must be bonded to the airframe for static and lightning protection.
NOTE
Check the aircraft manufacturer’s instruction manual for recommended antenna bonding practices.
2.4.1.2.3. Antenna Separation Considerations. As a general guideline, the Iridium antenna should be mounted on top of the
fuselage, as close to the centerline of the aircraft as possible, not to exceed an offset ± 5° max. The antenna should be mounted in a
location that would provide at least 8° horizontal view of the horizon and minimizing blockage from the vertical stabilizer or other
obstructions, see Figure 2-38. Refer to Paragraph 2.4.1.2. Typically, antenna manufacturers recommend a minimum separation of
24 in. (609.6 mm) or greater from any other antenna regardless of system type. Consult the relevant manufacturer’s guidelines for
further information.
NOTE
Check the aircraft manufacturer’s instruction manual for recommended antenna bonding practices.
2-57
system components
2-58
system components
2.4.1.2.3.1. Iridium and GPS Antenna Separation. While the Iridium and GPS frequency bands do not append each other,
in rare circumstances a GPS receiver’s operations can be affected by an Iridium system in transmit mode. This may occur on older
GPS systems which may not be equipped with Satcom filtering. Should you require further information contact your GPS system
manufacturer. Where possible, it is recommended that the Iridium antenna is installed at least 5 in. (127 mm) from any GPS antenna
to minimize the possibility of interference.
2.4.1.2.3.2. Iridium and Inmarsat Antenna Separation. As stated within Paragraph 2.4.1.1 Band Pass Filter, there is a signifi-
cant possibility of Inmarsat interference within co-resident Iridium – Inmarsat Satcom installations. Actual affects upon the Iridium
system may vary based upon Inmarsat antenna type and mounting locations as well as the direction of flight and Inmarsat Satellite
logon. Based upon the apparent variables, Rockwell Collins does not currently recommend any specific minimum separation dis-
tance between these antennas, only to recommend that the maximum horizontal separation be achieved based upon the airframe.
Vertical separation may also help to minimize this situation as well as the use of a phased array rather than directional Inmarsat
antenna. Within co-resident installations where both an Iridium system and an Inmarsat are present and critical DataLink Safety
Services are required via these networks, it is recommended that the systems be configured to allow for Inmarsat as the Primary
media with Iridium as the Secondary (slave) media for installations where Inmarsat interference could not be completely overcome.
2.4.2. IRT-2110/2120 and ICS-120A/220A Antenna Illustrations.
See Figure 2-39 for illustrations of Dual-Element Iridium Antenna. See Figure 2-40 for illustrations of Single-Element Iridium
Antenna. See Figure 2-41 for illustrations of Single-Element Iridium Antennas with cables attached. See Figure 2-42 for illustrations
of a Dual-Element Iridium Antenna with cables attached.
2-59
system components
2-60
system components
2-61
system components
2-62
system components
2-63
system components
2-64
system components
2-65/(2-66 Blank)
CHAPTER 3
Operation
3.1. INTRODUCTION.
This section provides the necessary general operating instructions for using the IRT-2110/2120 and ICS-120A/220A. It also gives a
basic overview of the system.
3-1
operation
3-2
operation
NOTE
If all transceivers are in use, the caller will hear a busy signal.
3.3.2. No-Ring-On-Flaps.
If the No-Ring-On-Flaps feature has been enabled, extensions in the cockpit will not ring when the aircraft flaps are set in the take-off
or landing positions.
3.3.3. Notification of Incoming Call.
Inbound call routing is controlled by configurable hunt groups. Each incoming trunk circuit is assigned one of the available hunt
groups. These hunt groups then are configured by available extensions. Incoming calls are routed via the hunt groups. For example,
if Ext. 11 was configured in the hunt group for the Iridium trunk you are calling, it would ring Ext. 11. If Ext. 11 is busy, it would ring
the next extension configured in the inbound hunt group. If Direct Inward Station Access (DISA) is set to ON and the ground-to-air
caller can call the desired extension directly, this extension will ring as a notification of the incoming call.
3.3.4. Transferring a Call.
To transfer a call to another extension:
a. Push the FLASH button.
b. Listen for a new dial tone.
c. Enter the new extension number.
d. Hang up to transfer the call. Or, wait on the line for an answer and announce the call before hanging up. (If no answer, flash
the hook switch again to reconnect to the groundside caller.)
3-3
operation
NOTE
The display screens may not directly represent your system. The identification label SAT, is customizable within
the Configuration Editor. For example, your system may have the MCDU menu label IRDM which would replace
SAT in all the display screenshots.
3-4
operation
3.4.3.1. The Channel Status Field. The Channel Status field can have the below listed values:
READY The SAT channel is registered onto the network and is available for making a voice call.
DIALING The SDU is processing the call.
RINGING The call has been passed through to the PSTN, is ringing, and is waiting for the remote party to pick up.
ANSWERED The placed call was answered and the call is active.
CALL FAIL The call has failed.
INCOMING Incoming Call – Awaiting ANSWER.
UNAVAILABLE The SAT channel is not available; insufficient signal level.
CALL ENDED The call has been terminated.
DATA CALL The SAT channel is busy, engaged in a data call.
GND CALL Incoming GTA Call – Awaiting ANSWER.
NOT READY The L-Band Transceiver (LBT) is in use and the other statuses do not apply.
ACARS USE The SBD has begun to use the LBT for ACARS because of an SBD Modem failure.
FAIL The LBT has not been initialized.
CABIN CALL A cabin phone (Ext. 11 – 14) has called the MCDU (Ext. 15 or 16).
3.4.4. SAT-PHONE Page Call Priorities.
The SAT-PHONE Page Call can have the below listed values:
HGH Highest non-emergency priority in terms of pre-empting other calls.
LOW Lowest non-emergency priority in terms of pre-empting other calls.
PUB Public call.
EMG Emergency call.
CALL FAIL Indicates that the call has not been connected.
3.4.5. SAT-PHONE Page 2/2.
A second SAT phone page provides access to the LOG, Directory Detail, Bite, and Configuration pages (see Figure 3-3).
3-5
operation
3-6
operation
NOTE
The display show one of many, possible directory hierarchy configurations. The actual MCDU directory pages
may appear slightly different than the below listed examples.
3-7
operation
3.4.7.1. The ATC Directory. The Air Traffic Control (ATC) Directory is a hierarchical directory that, in this example, begins
with regions, which are sub-divided into countries, and finally entries. Refer to Table 3-1 ATC Directory Page Region. See Figure
3-6 for ATC Directory Page.
3-8
operation
DIRECTORY REGION
AF I Africa
EUR Europe
MID/ASIA Middle East and Asia
NAT/NAM North Atlantic and North America
PAC Pacific
SAM/CAR South America and Caribbean
a. After selecting a region, the ATC Directory will show the country sub-directories for that region. See Figure 3-7 for ATC
Sub-Directory.
3-9
operation
b. After selecting the country, the ATC Directory will show all the available entries for that country. Select one using the appro-
priate LSK to send it to the SAT-Phone page’s strachpad for dialing. See Figure 3-8 for ATC Directory Details.
3-10
operation
3.4.7.1.1. Short Code Dialing. The Short Code Dialing feature uses the ATS directory to make calls. Short codes are six digits
long. If the number entered is six digits, the system searches through the ATS directory for a match. If there is a match, the call
is processed using the phone number stored in the ATS directory. Short Code Dialing is supported from any MCDU terminal, or
(2-wire/4-wire) extension port.
3.4.7.2. The AOC Directory. The Aeronautical Operational Control Directory stores entries specific to the operations of the unit
including Emergency numbers, Company specific numbers, and Operations numbers. If the Emergency, Company, and Operations
sub-directories are not empty, as is sometimes the case per configuration parameters, they will appear as short cuts on the SAT
Directory Index. See Figure 3-9 for AOC Directory.
3.4.7.2.1. Speed Dialing. The Speed Dialing feature uses the AOC directory to place calls. Speed dialing codes are three digits.
If the number entered is three digits, the system searches through the AOC directory for a match. If there is a match, the call is
processed using the phone number stored in the AOC directory. Speed Dialing is supported from any MCDU terminal, or (2-wire/4-
wire) extension port.
3-11
operation
3-12
operation
3.4.8.1. Modifying the AOC and ATC Directory. To modify an AOC or ATC Directory entry follow the directions below for
example of modifying an AOC directory. See Figure 3-11 for SAT Number Entry Page. Refer to Table 3-2 for SAT Phone Field.
a. Navigate to the SAT Directory Details page from the SAT Phone Page.
b. Enter the AOC Directory password.
c. Select AOC Directory.
d. Select the appropriate sub-directory using the LSK.
e. Select the entry you wish to modify with the LSK.
f. The Sat Number Entry page will appear. Modify the fields as necessary.
3-13
operation
FIELD DESCRIPTION
NAME The title of the entry. Up to 24 characters.
PHONE NUMBER The digits dialed when the entry is used. Up to 24 characters.
SHORT CODE A short cut for the phone number of the entry. Three (3) digits
for the AOC Directory. Six (6) digits for the ATC Directory.
VISIBLE Determines if the entry is visible on the Directory. True or
False.
PRIORITY Sets the call priority for call preemption purposes. EMG,
LOW, HGH or PUB options.
g. Push the STORE LSK. You will be returned to the AOC Directory Details page.
h. Push the SAVE LSK.
i. The SAT AOC DB PN page will appear. Now that the Directory has been modified, change the database’s PN to help keep
track of user versions. Enter a two digit user revision number by pushing the MOD PN OK LSK. The new PN will be in the
form XXXXXX-YY-ZZ where the ZZ is the User PN variable.
j. Push the CONTINUE LSK.
k. THE SAT AOC DB Change Warning page will appear. Push the CONFRIM LSK. The unit will reset at this point and changes
will go into effect. See Figure 3-12 for SAT AOC DB Change.
3-14
operation
3-15
operation
STATUS DEFINITION
READY The channel is registered to the network and able to make calls.
FAIL The channel has not been initialized and cannot make calls.
DISABLED The channel has been attenuated in the configuration.
NOT READY The channel is not in use and the other statuses do not apply.
IN USE The channel is currently supporting a call.
3-16
operation
EQUIPMENT STATUS
SDU
• OK: the SDU is installed and operational.
CIM
• OK: the CIM is installed and operational.
• FAIL: the CIM has failed.
• NOT INST: the CIM is not installed.
LBT-1
• OK: LBT-1 is enabled and operational.
• FAIL: LBT-1 has failed.
• DISABLED: LBT-1 has been disabled via the configuration.
LBT-2
• OK: LBT-2 is enabled and operational.
• FAIL: LBT-2 has failed.
• DISABLED: LBT-2 has been disabled via the configuration.
SBD
• OK: SBD is enabled and operational.
• FAIL: SBD has failed.
• DISABLED: SBD has been disabled via the configuration.
3-17
operation
EQUIPMENT STATUS
ACARS
• OK: ACARS is installed and operational.
• FAIL: ACARS has failed.
• NOT INST: ACARS is not installed.
SCDU-1
• OK: SCDU-1 is installed and operational.
• FAIL: SCDU-1 has failed.
• NOT INST: SCDU-1 is not installed.
SCDU-2
• OK: SCDU-2 is installed and operational.
• FAIL: SCDU-2 has failed.
• NOT INST: SCDU-2 is not installed.
SCDU-3
• OK: SCDU-3 is installed and operational.
• FAIL: SCDU-3 has failed.
• NOT INST: SCDU-3 is not installed.
3-18
operation
3-19
operation
3.4.11.1. Configuring the MCDU. To configure the MCDU follow the directions below:
a. Navigate to the Configuration page from the SAT menu.
b. Enter the User ORT password.
c. Select the User ORT LSK. See Figure 3-17 to that shows the display.
d. The SAT User ORT has five (5) pages of options. Refer to Table 3-5 for options are available on configuration.
FIELD OPTIONS
SCDU SYS Enter up to 8 characters
PROMPT If SAT SECURE ORT 4/4 STATIC TITLES are DISABLED,
displays entered text on all titles, sub-titles, and within pages.
If SAT SECURE ORT 4/4 STATIC TITLES are ENABLED, displays entered text only within pages
(where "SAT" would normally display, e.g. column headers) and not on titles, sub-titles
AMS SW Push to Talk (PTT) or LTCH MIC-ON
CH LABEL -1/-2 or –L/-R
SUFFIXES
3-20
operation
FIELD OPTIONS
RESTRICT ORT IN ENABLED, DISABLED
AIR LSK Active if UORT SECURE PARAMETERS are ENABLEDAIR/GND STATE
If ENABLED, entry into USER ORT, SECURE ORT, Air Traffic Control (ATC) directory
detail, and AOC directory detail is prohibited if the aircraft is in air as determined by the
AIR/GND STATE and the value of the discrete of the configured AIR/GND Input pin
If DISABLED, entry into USER ORT, SECURE ORT, ATC directory detail, and AOC
directory detail is controlled by the respective password
NOTE
ATC and AOC currently use the same password as the USER ORT
AIR/GND STATE AIR=OPN, AIR=GND, (or displays UNK if not currently valid, not changeable)
LSK Act if UORT SECURE PARAMETERS are ENABLED. An IO input pin has
to have been configured for AIR/GND for this to be valid. Determines how the
configured input discrete is interpreted to determine whether the aircraft is in air
AIR=OPN
Discrete=Open, IN AIR
Discrete=Ground, NOT IN AIR
AIR=GND
Discrete=Open, NOT IN AIR
Discrete=Ground, IN AIR
HISTORY Enabled or Disabled. Determines whether or not the History LSK is visible on the SAT-Phone page.
LBT-1 Enabled or Disabled. Determines if the LBT-1 is enabled or disabled.
LBT-2 Enabled or Disabled. Determines if the LBT-2 is enabled or disabled.
ACARS TX LOW or HIGH
ACARS RX LOW or HIGH
SBD Enabled or Disabled. Determines if the SBD Modem is enabled or disabled.
SBD HW REDUND Enabled or Disabled. Determines if the SBD hardware redundancy feature is enabled or disabled.
LBT-1 GTA CKPT The LBT-1 Routing of incoming GTA calls to extension, ordered list (CH-X(EXTXX),
ROUTING CH-X(EXTXX),(EXTXX),..), e.g. CH-1(EXT15), CH-2(EXT16)
LBT-2 GTA CKPT The LBT-2 Routing of incoming GTA calls to extension, ordered list of which to try in order
ROUTING (CH-X(EXTXX), CHX( EXTXX),(EXTXX),..), e.g. CH-1(EXT15), CH-2(EXT16)
WHT LIST ONLY Enabled or Disabled. If ENABLED, short codes/phone # entries for channel 1 must exist in the ATC or
AOC directory
SAT CH-1 Enabled or Disabled. Determines if SAT CH-1 is enabled or disabled.
ATG CKPT RTG The Channel 1 Routing of outgoing ATG calls to trunks, ordered list (LBTX,LBTX,(XX),..), e.g.
LBT1, LBT2
NOISE RED Enabled or Disabled. Determines if noise reduction is enabled or disabled.
CKPT MIC LVL Cockpit MIC volume level. -20 to +20 in increments of one (1) via the scratchpad.
4 WIRE MCDU, HANDSET, or UNK
CKPT AUDIO LVL Cockpit Audio volume level. -20 to +20 in increments of one (1) via the scratchpad.
CKPT ST Enabled or Disabled. Determines if cockpit sidetone is enabled or disabled.
3-21
operation
FIELD OPTIONS
PRIORITY Enabled or Disabled. Determines if the PRI label and channel 1 priority settings are enabled or disabled.
CKPT ST LVL Cockpit sidetone volume level. -20 to +20 in increments of one (1) via the scratchpad.
SAT CH-2 Enabled or Disabled. Determines if SAT CH-2 is enabled or disabled.
SERVICE ARINC-GL, ARINC-AD, SITA-XS, GDC-GS or OTHER
PROVIDER
CURRENT UORT Left side displays current UORT password. Right side allows entry of new UORT password (also used
ATC AOC for ATC and AOC DIR DETAIL, Up to 8 characters, 0-9, A-Z, -, space
COMPANY Enabled or Disabled. Determines if the Company option is visibile on the Directory pages.
OPERATIONS Enabled or Disabled. Determines if the Operations options is visibile on the Directory pages.
e. After making the necessary changes, push the SAVE LSK, which is located at the bottom of each page.
f. The SAT CONFIG DB PN page will appear. Now that the Configuration has been modified, change the database’s PN to help
keep track of user versions. Enter a two digit user revision number by pushing the MOD PN OK LSK. The new PN will be in
the form XXXXXX-YY-ZZ where the ZZ is the User PN variable.
g. Push the Continue LSK. The SAT Config DB Change Warning screen will appear. See Figure 3-18 for SAT Config DB Change.
h. Push the Confirm LSK to accept changes and resent the system.
3-22
operation
d. Push the Acknowledge / Continue key to proceed to the next screens and begin editing the configuration.
e. See Figure 3-20 for SAT Secure ORT page 1/4.
3-23
operation
There are four (4) pages of Secure ORT options. Refer to Table 3-6 for options that are available for configuration.
FIELD OPTIONS
429 BUS SPD HGH or LOW for each
TX1-3 and
RX1-6
429 BUS CFG Enabled or Disabled for each
TX1-3 and
RX1-6
PASSWORD
• Current: Up to eight (8) characters
• New: Up to eight (8) characters
• Current UORT / ATC / AOC: Up to eight (8) characters.
UORT Enabled or Disabled
SECURE
PARAMETERS
STATIC Enabled or Disabled
TITLES
f. After making the necessary changes, push the SAVE LSK, which is located at the bottom of each page.
3-24
operation
g. The SAT CONFIG DB PN page will appear. Now that the Configuration has been modified, change the database’s PN to help
keep track of user versions. Enter a two digit user revision number by pushing the MOD PN OK LSK. The new PN will be in
the form XXXXXX-YY-ZZ where the ZZ is the User PN variable.
h. Push the Continue LSK. See Figure 3-21 for SAT Config DB Change Warning screen.
i. Push the Confirm LSK to accept changes and resent the system.
3.4.12. Flight Deck Voice Channel Redundancy (SW REV-04 OR LATER).
The Flight Deck Voice Channel Redundancy feature provides the capability to reserve a second Iridium channel (LBT2) in an IRT-
2120/ICS-220A unit as a backup, in case of hardware failure occurring in the first Iridium channel (LBT1). The IRT-2110/ICS-
120A does not support this capability. Redundancy is achieved by setting ports 60 (LBT1) and 61 (LBT2) in the routing (outbound
huntgroup) for the desired 4-wire port (station 15 configured as MCDU device type).
3.4.12.1. If LBT1 becomes unavailable, the MCDU SAT status will display the LBT2 state (backup channel), and the call will be
processed on LBT2. If a user goes to the SAT-LOG page (by pushing NEXT PAGE on SAT-PHONE page), they will refer to the
individual channel states.
3.4.13. Follow-on Dialing from the MCDU (SW REV-04 OR LATER).
After a call has been placed, the user will have the option to enter a follow-on number to send on the active channel as Dual-Tone
Multi-Frequency (DTMF) digits. This allows users to dial extension numbers or other prompts to get access to the desired ground
party.
3.4.13.1. After a call is completed, any DTMF characters typed on the scratchpad can be dialed on an active channel by pushing
the SEND> LSK entry on the screen associated with the appropriate SATCOM channel. This action allows the MCDU to also dial
a second call on the second SATCOM without interfering with the current call setup.
3.4.13.2. When the SEND> LSK is pushed, the scratchpad entry will be used and the DTMF digits dialed on the active call over
the Iridium network. The user will be allowed to satisfy any prompts to enter information for example, extension number, call billing
information, etc as long as the call is active. See Figure 3-22 for Follow-On Dialing Example.
3-25
operation
NOTE
The information on this feature will need to be outlined clearly in any pilot user’s guide. There is NO EQUIVA-
LENT function supported by existing SATCOM devices.
NOTE
The exact EICAS text messages are dependent on the EICAS model and configuration.
3-26
operation
NOTE
Refer to Paragraph 3.8 for a list of country codes for international dialing.
AIR-TO-GROUND (ATG)
Calls to North America 1 + Area Code + Number. For example, to call Rockwell
Collins: 1 - 319 - 295 - 0594
Calls to other Int’l destinations 011 + Country Code + City Code + Number. For example, to
call the U.K.: 011 - 44 - 1703 - 123456
AIRCRAFT TO AIRCRAFT
Air to Air 011 + 8816 + 8-digit transceiver telephone number
3-27
operation
AIR-TO-GROUND (ATG)
Calls to North America 00 + Country Code + Area Code + Number
Calls to other Int’l destinations 00 + Country Code + City Code + NumberFor example, to call
the U.K.: 00 + 44 - 1703 - 123456
AIRCRAFT TO AIRCRAFT
Air to Air 00 + 8816 + 8 Digit Transceiver Number
CALLS-TO-IRIDIUM PHONE
Air-to-Iridium 011 + 8816 + 8-digit transceiver telephone number
Ground-to-Iridium 011 + 8816 + 8-digit transceiver telephone number
3-28
operation
3.6.2. Lower Priority Call Pre-Emption Voice Prompt (SW REV-04 OR LATER).
The system plays back a voice prompt to a lower priority call in progress when pre-empted to process a higher priority call. Refer
to Table 3-12 Voice Prompt ID 04. If voice prompts are disabled for a particular station, a bong tone is played back instead.
3.6.3. Customizing a Voice Prompt.
To customize a voice prompt:
a. Pick up a handset and enter <#5xx>, where xx is the VP ID to be recorded.
NOTE
Valid message numbers are from 02 through 05. Refer to Paragraph 3.4.3.1 for the complete list of customizable
voice prompts.
NOTE
It is better to push * than just hanging up because the act of hanging up the handset receiver can cause noise which
will be recorded in the message.
3-29
operation
Data Services CD or from Iridium’s website) on your computer. To access the internet with this interface the PC must have a serial
port, a standard serial cable, and the network connection (Iridium’s Direct Internet 2.0) must already be configured. Individual
aircraft may not be configured for this kind of service.
a. Attach a standard serial cable from the PC to serial port 1 at the back of the IRT-2110/2120.
b. Click on one of the below listed options:
• Shortcut for the Direct Internet 2.0, if it exists on the desk top.
• Start>Connect to>Iridium network connection.
3-30
operation
Chad 235
Chatham Island (NZ) 64
Chile 56
China 8
Christmas Island 672
Cocos Islands 672
Colombia 57
Comoros 269
Congo 242
Cook Islands 682
Costa Rica 506
Croatia 385
Cuba 53
Cyprus 357
Czech Republic 420
Denmark 45
Diego Garcia 246
Djibouti 253
Dominica 767
Dominican Republic 1-809 & 1-829
Easter Island 6
Ecuador 593
Egypt 20
El Salvador 503
Equatorial Guinea 240
Eritrea 291
Estonia 372
Ethiopia 251
Falkland Islands 500
Faroe Islands 298
Fiji 679
Finland 358
France 33
French Antilles 596
French Guyana. 594
French Polynesia 689
Fyrom (Macedonia) 389
Gabon 241
Gambia 220
Georgia 995
Germany 49
Ghana 233
Gibraltar 350
Greece 30
Greenland 299
Grenada, Carriacuou 473
Grenadin Islands 784
Guadeloupe 590
Guam 671
Guantanamo Bay 53
Guatemala 502
Guiana 594
Guinea 224
Guinea-Bissau 245
Guyana 592
Haiti 509
Honduras 504
3-31
operation
3-32
operation
Nepal 977
Netherlands 31
Neth. Antilles 599
Nevis 869
New Caledonia 687
New Zealand 64
Nicaragua 505
Niger 227
Nigeria 234
Niue 683
Norfolk Island 672
North Korea 850
Norway 47
Oman 968
Pakistan 92
Palau 680
Panama 507
Papua New Guinea 675
Paraguay 595
Peru 51
Philippines 63
Poland 48
Portugal 351
Principe 239
Puerto Rico 1-787 & 1-939
Qatar 974
Reunion Island 262
Romania 40
Russia 7
Rwanda 250
St. Kitts 869
St. Helena 290
St. Lucia 758
St. Pierre et Miquelon 508
St. Vincent 784
Saipan 670
San Marino 378
Sao Tome 239
Saudi Arabia 966
Senegal Republic 221
Serbia, Republic of 381
Seychelles 248
Sierra Leone 232
Singapore 65
Slovakia 421
Slovenia 386
Solomon Islands 677
Somalia 252
South Africa 27
South Korea 82
Spain 34
Sri Lanka 94
Sudan 249
Suriname 597
Swaziland 268
Sweden 46
Switzerland 41
3-33
operation
Syria 963
Taiwan 886
Tajikistan 7
Tanzania 255
Thailand 66
Togo 228
Tokelau 690
Tonga 676
Trinidad and Tobago 868
Tunisia 216
Turkey 90
Turkmenistan 993
Turks & Caicos Islands 649
Tuvalu 688
Uganda 256
Ukraine 380
United Arab Emirates 971
United Kingdom 44
United States 1
Uruguay 598
U.S. Virgin Islands 340
Uzbekistan 998
Vanuatu 678
Vatican City 379
Venezuela 58
Vietnam, Socialist Rep 84
Wake Island 808
Wallis & Futuna Islands 681
Western Samoa 685
Yemen 967
Zaire 243
Zambia 260
Zanzibar 259
Zimbabwe 263
NOTE
It is not necessary to wait for the prompts or the dial tone to complete.
3-34
operation
NOTE
Saving messages to flash will take some time and will disable all other functions until this operation is complete.
When complete, the unit will resume normal operation.
3-35/(3-36 Blank)
CHAPTER 4
Maintenance
4.1. GENERAL.
This chapter provides flight line maintenance instructions for an IRT-2110/2120 and ICS-120A/220A subsystem. Refer to Paragraph
4.7 for detailed troubleshooting procedures.
4.2. SOFTWARE.
The Rockwell Collins IRT-2110/2120 and ICS-120A/220A employs exclusive software to control and monitor performance as well
as to enable all user features. For information on viewing and editing the system configuration, refer to Paragraph 4.4. For informa-
tion on the system firmware updating procedure, refer to Paragraph 4.2.6. To connect computer via USB cable to front panel SDU
USB maintenance interface connector, refer to Rockwell Collins USB Driver Manual P/N 234701.
4.2.1. IRT-2110/2120 and ICS-120A/220A Data Files (SW REV-04 OR LATER).
NOTE
The information is provided for both the part numbers ICM (822-2836-001/-101/- 201)/CIM (327800).
The IRT-2110/2120 and ICS-120A/220A installation CD includes four files along with the software firmware file (710500-XX.sim
or 711500-XX.sim). Two of these files, the Air Traffic Services (ATS) directory file and the Aeronautical Operation Center directory
file, contain the telephone numbers of various air traffic control towers, among other ATS centers, and the telephone numbers of
various centers that are specific to the aircraft or airline (AOC). The voice prompts file consists of four prompts for situations for
example, Number not Found and PIN entry calls. These prompts are recorded in English but can be translated to any language
desired. Finally, the configuration file contains the default configuration for the IRT-2110/2120. This sections describe files 2 through
5 in the table above in greater detail. The sections that follow describe files 2 through 5 in the table below in greater detail. The file
set for the IRT-2110/2120 and ICS-120A/220A consists of the files in Table 4-1:
4-1
maintenance
NOTE
*XX is the current Software Revision Number. For Revision 4, for example, the default voice prompts file would
be 710500-04-VP.dat.
** : The default configuration file can be either part number 710533 or 710537 depending on the customer.
*** : There are two primary main application part numbers, 710503 or ICS and 711503 for EPIC.
4-2
maintenance
4.2.1.1. The ATS Directory File (SW REV-04 OR LATER). The Air Traffic Services (ATS) or ATS Directory resides in the
ICM/CIM memory space. It is viewable and can be edited from the Multipurpose Control Display Unit (MCDU) interface. However,
this file is password-protected: it can be viewed but not edited without first entering the password. This directory can accommodate
a maximum of 400 entries.
NOTE
While the existing file entries can be modified, no entries can be added or deleted directly on the MCDU terminal.
4.2.1.1.1. Each entry in the ATS file includes the information listed below:
• Short code (6 digits)
• Description
• Phone number
• Priority.
4.2.1.1.2. These fields can be modified. Refer to Paragraph 3.4.8 for more information. The ATS directory file may be uploaded
and downloaded using the command line interface. Refer to Paragraph 4.2.4 for instructions.
4.2.1.2. The AOC Directory File (SW REV-04 OR LATER). The Aeronautical Operation Center Directory resides in the
ICM/CIM memory space. It is viewable and can be edited from the MCDU interface. This file is password-protected. However, the
file can be viewed but not edited without first entering the password. This directory can accommodate a maximum of 100 entries. If
this file has been customized, it is advisable to download a copy to a PC as a backup in case of ICM/CIM failure.
NOTE
While the existing file entries can be modified, no entries can be added or deleted directly on the MCDU terminal.
4.2.1.2.1. Each entry in the directory includes the information listed below:
• Speed-dialing code (3 digits)
• Description
• Phone number
• Priority.
4.2.1.2.2. Refer to Paragraph 4.2.4 for more information on how to modify these parameters. The AOC directory file may also be
uploaded and downloaded using the command line interface. Refer to Paragraph 4.2.4 for instructions.
4.2.2. The Voice Prompt File (SW REV-04 OR LATER).
This file contains the voice prompts for the IRT-2110/2120 and ICS-120A/220A PABX subsystem. An IRT-2110/2120 and ICS-
120A/220A unit must be used if it is desired to translate the default prompts into a different language.
NOTE
However, that the particular function of a given voice prompt must be maintained. Refer to Paragraph 3.6 for more
information on how to customize the voice prompts.
4.2.2.1. This file is stored within the system itself as digitized audio data, and not on the ICM/CIM. However, it can be downloaded
via the Command Line Interface. If this file has been customized, it is advisable to download a copy to a PC as a backup.
4.2.2.2. This file may be uploaded and/or downloaded using the command line interface. Refer to Paragraph 4.2.4 below for
instructions.
4-3
maintenance
4.2.3. The IRT-2110/2120 and ICS-120A/220A Configuration File (SW REV-04 OR LATER).
The configuration file contains the IRT-2110/2120 and ICS-120A/220A unit default configuration parameters. During normal oper-
ations, the system reads the product configuration from the ICM/CIM when the ICM/CIM is detected by the system during system
power-up. If the ICM/CIM is not detected, or if the product configuration data stored in the ICM/CIM is missing or corrupted, the
built-in product configuration data will be used instead.
4.2.4. Uploading and Downloading the Data Files.
The system software supports the ability to upload and download the data files from a PC to the ICM/CIM. Push <Ctrl/C> on the
keyboard connected to the unit to open the command prompt screen. Refer to Table 4-2, summarizes the Command Line Inter-
face (CLI) methods for uploading and downloading data files to the IRT-2110/2120 and ICS-120A/220A unit.
NOTE
Actual screen shots may not be identical to example screen shots.
All uploads are done from the command prompt with the upload keyword, no other information will be needed. The upload handler
can determine the upload type from the header information uploaded. After the upload process is completed, the file will be processed
by the application and either a success or a failure message will be returned to the user. To upload a file using HyperTerminal or an
equivalent application:
a. Push <Ctrl/C> to bring up the CLI.
b. At the prompt, type in upload and push <Enter>, see Figure 4-1.
4-4
maintenance
c. Click on Transfer>Send Text File... in the menu bar, see Figure 4-2.
4-5
maintenance
NOTE
Be sure the parameter <Files of type: > is set to <All files (*.*)>
NOTE
It may take a couple of minutes for the Voice Prompts file uploads to complete.
f. Return to Step 4.2.4.1.b if there are more files to upload. Otherwise push <F3> to return to the Main Menu.
4-6
maintenance
g. Select the ICM/CIM Editor on the Main Menu and push <Enter>, see Figure 4-5.
NOTE
This step is only required if you have uploaded the configuration file or either of the directory files.
The Voice Prompts file is uploaded directly to the IRT-2110/2120 and ICS-120A/220A system and is not stored
on the ICM/CIM. Once the voice prompts file has been customized, it should be downloaded and stored on a PC
as a backup measure.
h. If only one file is to be updated, select the option that fits that file type. If all the data files are being updated, select option 1,
SAVE ALL, see Figure 4-6.
4-7
maintenance
4-8
maintenance
c. Select the file location to store the downloaded file, see Figure 4-9.
4-9
maintenance
NOTE
Be sure Files of type: is set to All files (*.*).
e. At the prompt, enter one of the below listed information, depends on the required file is to be downloaded and then push
<Enter>:
• >Download config
• >Download voice-prompts
• >Download ats-directory
4-10
maintenance
• >Download aoc-directory.
NOTE
It may take a couple of minutes for the Voice Prompts file downloads to complete.
f. A prompted for a password may appear. Enter password and push <Enter>.
g. Click on Transfer > Capture Text > Stop when the download is complete.
h. Push <F3> to return to the Main Menu.
NOTE
If there are more files to download, return to Step 4.2.4.2.b.
i. Navigate back to the Configuration Editor Menu screen by using the Return option.
4.2.5. Initializing the System.
The IRT-2110/2120 and ICS-120A/220A system may not initially have all the files installed that are required for all functions and
features to run properly. It will most likely come with the voice prompts file and the configuration file installed, but not the ATS
and AOC directory files installed. Normally, the IRT-2110/2120 and ICS-120A/220A unit is delivered already configured. The
ICM/CIM will already contain the default ATS Directory file and the default AOC Directory file. The default voice prompt set will
already be installed in the unit. When the IRT-2120 and ICS-120A/220A unit is first installed into a tray, but is not already configured,
the POWER lamp will flash between Red and Green. This indicates that the unit is not functioning with the configuration in the
ICM/CIM. This is normal for units with BLANK ICM/CIM modules. Once the IRT-2110/2120 and ICS-120A/220A is installed into
the tray on the aircraft, the installer may need to do all, some, or none of the below listed steps to complete the initialization of the
unit:
a. Check with Rockwell Collins Technical Support if unsure what needs to be done.
b. Upload the configuration file to the ICM/CIM. Refer to Paragraph 4.2.4 for instructions.
c. Proceed to the ICM/CIM Options menu on the HyperTerminal screen, push <Ctrl/S>, and save the configuration to the
ICM/CIM.
d. Customize the AOC Directory file, if needed (refer to Paragraph 4.2.1 and Paragraph 3.4), and upload to the ICM/CIM.
e. Proceed to the ICM/CIM Options menu on the HyperTerminal screen, push <Ctrl/S>, and save the AOC directory file to the
ICM/CIM.
f. Upload the ATS Directory file to the ICM/CIM.
g. Proceed to the ICM/CIM Options menu on the HyperTerminal screen, push <Ctrl/S>, and save the ATS directory file to the
ICM/CIM.
h. Upload the voice prompts file to the system.
i. Reboot the unit.
j. Check the POWER lamp. The POWER lamp should remain GREEN when running, meaning the ICM/CIM is functioning and
the configuration has been properly saved.
4.2.6. Upgrading the Firmware and Configuration File.
The procedure describes how to upgrade the firmware on the IRT-2110/2120 and ICS-120A/220A. This procedure assumes that the
necessary steps were carried out to install the required Universal Serial Bus (USB) drivers.
4.2.6.1. Equipment Needed. The equipment listed below is needed for this procedure:
• A PC with an available USB port running Windows 2000/XP with installed IRT-2110/2120 and ICS-120A/220A device drivers.
• USB cable.
• 28 VDC power supply.
4-11
maintenance
NOTE
If you accidentally enter the bootloader instead of the HyperTerminal Main Menu, type exit and disconnect from
HyperTerminal (by pushing <Disconnect>) and try again.
NOTE
All of the HyperTerminal screens are samples. Your system may be configured to appear differently.
4-12
maintenance
a. Deleted. Navigate to the Main Menu by using <↑> and <↓> arrow keys to select Return, if the Main Menu is not already visible.
b. Use the <↑> and <↓> arrow keys on the keyboard to navigate to the Main Menu, select Return if the Main Menu is not already
visible.
c. Push <Enter>, see Figure 4-12.
4.3.3.1. The ICM/CIM options menu only has one screen which displays the various options for saving the data files. The moni-
toring utility includes the display screens, see Figure 4-13:
4-13
maintenance
4.3.3.2. The logging utility includes the screens, see Figure 4-14:
4.3.3.3. The configuration editor utility includes the screens, see Figure 4-15:
4-14
maintenance
NOTE
Once configuration changes have been made, on any page, the RETURN option, is the only way to navigate to a
higher level menu and save changes.
4-15
maintenance
NOTE
It is important to understand what each screen does, as these are the only ways to make changes to the system.
4-16
maintenance
c. Move the cursor from field to field by pushing the <↑> and <↓> keys. There are two different types of editable fields on the
various screens:
• Text Fields: Many text fields display validation rules.
• List Fields: Select a parameter value from a pre-defined list of values by using the <←> and <→> keys.
d. After editing the fields, return to the Configuration Editor Menu Screen (Unit Setting Screen) by pushing the <Esc> key.
e. Push <Ctrl/S>. The unit application verifies that a change has been made and then saves it. If no changes were made, it ignores
the Save command.
f. Use the <↑> key to move up to ―RETURN and push <Enter>.
g. Select ICM/CIM Options Menu and push <Enter>.
h. Enter the system password if prompted.
i. Select Save Unit Config and push <Enter>.
j. Push <Ctrl/S> to save the unit configuration to the ICM/CIM.
k. Reset the unit.
NOTE
The save option is presented only on the CONFIGURATION EDITOR MENU screen. To permanently save
changes, you must save your configuration to the ICM/CIM.
Multiple changes can be introduced during a configuration session. All the changes will be saved when you click
on <Ctrl/S>.
IMPORTANT: When making adjustments to the Gain Control parameters, the unit must be rebooted. The Digital
Signal Processor (DSP) must be reloaded in order for the Gain Control changes to take effect.
IMPORTANT: When making adjustments to the I/O parameters the unit must be rebooted in order for the changes
to take effect.
4.4.2.1. Use the 4-wire ports definition screen to set the ports to one of these configurations.
a. Select the 4-wire ports editor option from the configuration editor menu using the keyboard <↑> and <↓> keys, see Figure 4-17.
b. Push <Enter>.
NOTE
A reboot is required whenever a change is made in the port configuration and saved. Such a change also requires
changes in hunt groups and other parameters.
4-17
maintenance
4.4.2.1.1. The ports, see Figure 4-17 are currently set to MCDU (Multi-Purpose Control and Display Unit). If Station (4-Wire)
is selected or Trunk is selected, the related parameters and features are set using the Stations Editor for the 4-wire stations and the
Trunks Editor for a Trunk.
4.4.2.1.2. The Audio Management System (AMS) mode has two options. The difference between the two modes (refer to Table
4-4) is how active calls are terminated for Ext. 15 and 16 (when configured as MCDU devices).
NOTE
When a 4-wire port is configured for the MCDU, it is associated to either or both transceivers depending on how
they are set up in their respective outbound hunt groups.
A reboot is required whenever a change is made in the port configuration and saved. Such a change may also
require changes in hunt groups and other parameters.
4-18
maintenance
4.4.3.1.1. Station Configuration Setting Screen for 2-Wire Stations. The station configuration setting screen, see the figure
below, is used to make changes to a particular station port. To access the station configuration setting screen from the stations editor
screen:
a. Select a station port on the stations editor screen using the keyboard <↑> and <↓> keys.
b. Push the <Enter> key on the highlighted station port row.
c. Push the <Esc> key to return to the stations editor screen when done, see Figure 4-19.
4-19
maintenance
NOTE
Although other Hunt Groups are listed, HG-3 and HG-4 are the default Hunt Groups for the 2-wire stations 11
through 14. Outbound hunt groups default setting for all extensions must use both LBTs 60 and 61; Rockwell
Collins suggest to use HG-3 for the Outbound hunt groups. Inbound hunt groups default setting for all extensions
must be configured to use all extensions by default; Rockwell Collins suggest to use IN HG -4, for in the Inbound
hunt groups. HG-3 routes outbound calls [60, 61, 0, 0, 0, 0, 0]. HG-4 routes outbound calls [61, 60, 0, 0, 0, 0, 0].
0 dB is the default Gnd-To-Air Target Level value.
4.4.3.1.2. Station Features Setting Screen: 2-Wire Stations. The configuration editor displays permission, restriction, and
configuration parameters as a set of Class of Service (COS) Fields. All the currently supported features are listed on the station
features setting screen. The user can ENABLE and DISABLE a selected feature by using the <←> and <→> keys:
a. Use the <↑> and <↓> keys to select a parameter or field.
b. Push the <←> and <→> keys to scroll through the permissible settings for the port, see Figure 4-20.
4-20
maintenance
4.4.3.1.2.1. Refer to Table 4-5, for current features defined for an IRT-2110/2120 and ICS-120A/220A 2-wire station port:
FEATURE DESCRIPTION
Voice Prompts Set to Enabled to activate this feature. Refer to Paragraph 3.6 for more information.
CTU Connection Set to Enable to activate this feature. This feature is designed to be used with CTU
integrations, where dial-tone could be used as a machine interface to indicate an
Iridium channel is available for making a voice call. If no Iridium channels are
available for the extension port in use, no dial-tone is played back.
Station-To-Station (Analog and MCDU) Allows calls from one on-board extension to another.
3-Party Conference (Analog only) Allows an extension to initiate a three-party conference call.
Call Transfer (Analog only) Allows the transfer of an incoming call to another on-board extension.
No Rings on Flaps Allows control over whether the system rings the flight deck telephone during critical
flight operations, for example take-off and landing.
NOTE
This feature requires that the flap switch position signal be wired to the input.
4-21
maintenance
FEATURE DESCRIPTION
Credit Card To place a credit card call over the Iridium network:
• A Subscriber Identity Module (SIM) card provisioned for credit card service must
be installed (internal to the L-Band Transceiver (LBT) or external in the ICM/CIM).
• The system software must dial the appropriate dialing pre-fix to instruct the Iridium
switching network to route the call to the Iridium Credit Card Platform on the ground
side.
The phone number pre-fix digits determine the call routing on the ground.
Pre-Fix Digits for example, 00 Phone Number for example, 1 757 947
1030
NOTE
The user should not dial the pre-fix digits. Only ICS unit automatically selects
the call routing based on system configuration.
4-22
maintenance
FEATURE DESCRIPTION
CC PIN Dial-Around The Credit Card PIN Dial-Around is a Private Automatic Branch exchange (PABX)
capability that allows the user to bypass the credit card processing by entering a valid
PIN. The Credit Card PIN Dial-Around is only applicable when the Credit Card
Restriction is enabled for that given extension.
NOTE
It is assumed that Credit Card PIN Dial-Around and Credit Card Restriction COS
are enabled only when the IRT-2110/2120 and ICS-120A/220A system has Credit
Card provisioned SIM cards installed. When enabled, if a PIN is entered by
the user, if a match is found, the call is routed to the Iridium Post-Paid switch-
ing network. If the entered PIN is not found in the global PIN Table, or is not
entered at all, the call is routed to the Iridium Credit Card Platform to collect
the User’s credit card information. This is true when the IRT-2110/2120 and
ICS-120A/220A system has Credit Card provisioned SIM cards installed.
PIN Restricted Restricts station use by non-authorized users. When this feature is enabled, a caller
must enter a valid PIN before the call will go through. A valid PIN number is any
number enabled in the PIN table. The PIN numbers in the PIN table are configurable
(refer to Paragraph 4.4.10).
Mode of Operation (Analog only) Voice or Data.
Executive Override (Analog and Allows you to define the station priority for placing an outbound call, the highest
MCDU) of which is priority 1. Calls placed from this station with predefined priority may
pre-empt an existing call if the existing call has been placed from a station with a
lower-priority setting. The station priority may be set in the Configuration Editor List
Field, SET PRIORITY. The below listed options are available:
• No Priority (default)
• Priority N, where N = a number between 1 and 6.
White-List Only The IRT-2110/2120 and ICS-120A/220A supports restricting calls to ONLY those
numbers contained in the ATS/AOC phone books. This feature can be enabled and
disabled on a station-by-station basis. Once enabled, each number entered will be
checked by the system to see if it is present in either the AOC or ATS Directories
before the number is dialed. No other outbound numbers will be allowed.
Ring-Down (Analog only) Allows the system to automatically dial a predefined ground-based number.
NOTE
If you ENABLE this feature, the predefined phone number must be set in the
Enter Phone# Field. The user cannot return to the configuration editor menu
screen unless you insert a value in this field.
Noise Reducer Enabling Noise Reduction processing enhances the air-to-ground audio quality in
noisy aircraft environments where a high level of background noise is present.
4-23
maintenance
4.4.3.2. Editing a 4-Wire Station (Ports 15 and 16 only). To access the Stations Editor screen:
a. Select the STATIONS EDITOR option from the configuration editor menu using the keyboard <↑> and <↓> keys.
b. Push <Enter>. The Stations Editor screen presents a title consisting of the label Station, the port type (4-wire, in this case), and
the associated extension number, <xx> (either 15 or 16). The station can either be ENABLED or DISABLED. See the display
screen, see Figure 4-21:
Figure 4-21. Sample Stations Editor Screen with 4-Wire Stations Enabled
4.4.3.2.1. Station Configuration Setting Screen for 4-Wire Stations. The station configuration setting screen, as shown in
the figure below, is used to make changes to a particular station port. To access the station configuration setting screen from the
stations editor screen:
a. Select a station port on the stations editor screen using the keyboard <↑> and <↓> keys.
b. Push the <Enter> key on the highlighted station port row.
c. Push the <Esc> key to return to the stations editor screen when done, see Figure 4-22.
4-24
maintenance
NOTE
Although other Hunt Groups are listed, HG-3 and HG-4 are the default Hunt Groups for the 2-wire stations 11
through 14. Outbound hunt groups default setting for all extensions must use both LBTs 60 and 61; Rockwell
Collins suggest to use HG-3 for the Outbound hunt groups. Inbound hunt groups default setting for all extensions
must be configured to use all extensions by default; Rockwell Collins suggest to use IN HG -4, for in the Inbound
hunt groups. HG-3 routes outbound calls [60, 61, 0, 0, 0, 0, 0]. HG-4 routes outbound calls [61, 60, 0, 0, 0, 0, 0].
-20 dBm is the default Gnd-To-Air Target Level value.
4.4.3.2.2. Station Configuration Setting Screen: 4-Wire Stations. The Station Configuration Setting screen, as shown in
the figure below, is used to make changes to a particular station port. To access the Station Configuration Setting screen from the
Stations Editor screen:
a. Select a station port using the keyboard <↑> and <↓> keys.
b. Push the <Enter> key on the highlighted station port row.
c. Push the <Esc> key to return to the Stations Editor screen when done, see Figure 4-23.
4-25
maintenance
4-26
maintenance
4.4.3.2.3.1. Listed are the current features defined for an IRT-2110/2120 and ICS-120A/220A 4-Wire port (refer to Table 4-6):
FEATURE DESCRIPTION
Voice Prompts Set to Enabled to activate this feature. Refer to Paragraph 3.6 for more information.
CTU Connection Set to Enable to activate this feature. This feature is designed to be used with CTU
integrations, where dial-tone could be used as a machine interface to indicate an
Iridium channel is available for making a voice call. If no Iridium channels are
available for the extension port in use, no dial-tone is played back.
Station-To-Station (Analog and MCDU) Allows calls from one on-board extension to another.
3-Party Conference (Analog only) Allows an extension to initiate a three-party conference call.
Call Transfer (Analog only) Allows the transfer of an incoming call to another on-board extension.
No Rings on Flaps Allows control over whether the system rings the flight deck telephone during critical
flight operations for example, take-off and landing.
NOTE
This feature requires that the flap switch position signal be wired to the input.
4-27
maintenance
FEATURE DESCRIPTION
Credit Card To place a credit card call over the Iridium network:
• A SIM card provisioned for credit card service must be installed (internal to the LBT
or external in the ICM/CIM).
• The system software must dial the appropriate dialing pre-fix to instruct the Iridium
switching network to route the call to the Iridium Credit Card Platform on the ground
side.
The phone number pre-fix digits determine the call routing on the ground.
Pre-Fix Digits for example, Phone Number for example, 1 757 947 1030
00
CC PIN Dial-Around The Credit Card PIN Dial-Around is a PABX capability that allows the user to bypass
the credit card processing by entering a valid PIN. The Credit Card PIN Dial-Around
is only applicable when the Credit Card Restriction is enabled for that given extension.
NOTE
It is assumed that Credit Card PIN Dial-Around and Credit Card Restriction COS
are enabled only when the IRT-2110/2120 and ICS-120A/220A system has Credit
Card provisioned SIM cards installed. When enabled, if a PIN is entered by
the user, if a match is found, the call is routed to the Iridium Post-Paid switch-
ing network. If the entered PIN is not found in the global PIN Table, or is not
entered at all, the call is routed to the Iridium Credit Card Platform to collect
the User’s credit card information. This is true when the IRT-2110/2120 and
ICS-120A/220A system has Credit Card provisioned SIM cards installed.
4-28
maintenance
FEATURE DESCRIPTION
PIN Restricted Restricts station use by non-authorized users. When this feature is enabled, a caller
must enter a valid PIN before the call will go through. A valid PIN number is any
number enabled in the PIN table. The PIN numbers in the PIN table are configurable
(refer to Paragraph 4.4.10).
Mode of Operation (Analog only) Voice or Data.
Executive Override Allows you to define the station priority for placing an outbound call, the highest
of which is priority 1. Calls placed from this station with predefined priority may
pre-empt an existing call if the existing call has been placed from a station with a
lower-priority setting. The station priority may be set in the Configuration Editor List
Field, Set Priority. The below listed options for this field are available:
• No Priority (default)
• Priority N, where N = a number between 1 and 6.
White-List Only The IRT-2110/2120 and ICS-120A/220A supports restricting calls to ONLY those
numbers contained in the ATS/AOC phone books. This feature can be enabled and
disabled on a station-by-station basis. Once enabled, each number entered will be
checked by the system to see if it is present in either the AOC or ATS Directories
before the number is dialed. No other outbound numbers will be allowed if they
are NOT contained in either directory.
Ring-Down (Analog only) Allows the system to automatically dial a predefined ground-based number.
NOTE
If you ENABLE this feature, the predefined phone number must be set in the
Enter Phone# Field. Inserting a value in this filed is required in order to return to
the CONFIGURATION EDITOR MENU screen.
Noise Reducer Enabling Noise Reduction processing enhances the air-to-ground audio quality in
noisy aircraft environments where a high level of background noise is present.
4.4.3.3. Editing an MCDU Port (Ports 15 and 16 only). The Stations Editor screen is used to select a 2-wire station, a 4-wire
station, or an MCDU port in order to make changes to the station settings. To access the Stations Editor screen:
a. Select the STATIONS EDITOR option from the CONFIGURATION EDITOR MENU using the keyboard <↑> and <↓> keys.
b. Push <Enter>. The display screen, see Figure 4-25 appears:
4-29
maintenance
Figure 4-25. Sample Stations Editor Screen Showing the MCDU Ports
4.4.3.3.1. The stations editor screen presents a title consisting of the label Station, the port type (MCDU, in this case), and the
associated extension number, <xx> (either port 15 or 16). The station can either be ENABLED or DISABLED.
4.4.3.3.2. Station Configuration Setting Screen: MCDU Port. The station configuration setting screen is used to make
changes to a particular station port. To access the station configuration setting screen from the stations editor screen:
a. Select an MCDU station port using the keyboard <↑> and <↓> keys.
b. Push the <Enter> key on the highlighted station port row.
c. Push the <Esc> key to return to the stations editor screen when done.
d. The display screen, see Figure 4-26 appears for MCDU port 15:
4-30
maintenance
e. The display screen, see Figure 4-27 appears for MCDU port 16:
4-31
maintenance
4.4.3.3.2.1. Configuration Settings Definitions. These station configuration setting screens display the below listed parame-
ters:
Configuration State A station can either be ENABLED or DISABLED.
Hunt Group Name OUT HG-1 must be selected for MCDU port 15. OUT HG-2 must be selected for MCDU port 16.
Audio Fixed Gain Con- The Fixed Gain Control Range is -20 db to +20 db and the default is 0 db for all extensions and trunks.
trol
The Gain Control parameters permit gain and attenuation control adjustments in the RX (receive) direction. The valid range is –30
dBm to 0 dBm.
a. Use the <↑> and <↓> keys to access the Gain Control parameters.
b. Increase the value (plus direction <→>) to add gain to the circuit and decrease the value (minus direction <←>) to add atten-
uation.
4.4.3.4. MCDU Features Setting Screen: MCDU Port. The Configuration Editor displays permission, restriction, and con-
figuration parameters as a set of COS fields. All the currently supported features are listed on the MCDU Features Setting screen.
You can ENABLE or DISABLE a selected feature by using the <←> and <→> keys:
a. Use the <↑> and <↓> keys to select a parameter or field.
b. Push the <←> and <→> keys to scroll through the permissible settings for the port.
c. The display screen appears, (see Figure 4-28):
Figure 4-28. Sample MCDU Features Setting Screen: MCDU Ports 15 and 16
4.4.3.4.1. Listed are the current MCDU features defined for an IRT-2110/2120 and only ICS-120A MCDU port. Although the
features are all listed on the screen, only the ones indicated in Table 4-7 below by an asterisk (*) are available for MCDU.
4-32
maintenance
FEATURE DESCRIPTION
Voice Prompts Set to ENABLED to activate this feature. Refer to Paragraph 3.6 for more
information.
Station-To-Station (Analog and MCDU) Allows calls from one on-board extension to another. Set to ENABLED.
No Rings on Flaps Allows control over whether the system rings the flight deck telephone during critical
flight operations for example, take-off and landing.
NOTE
This feature requires that the flap switch position signal be wired to the input.
Credit Card To place a credit card call over the Iridium network:
• A SIM card provisioned for credit card service must be installed (internal to the
LBT or external in the ICM/CIM).
• The system software must dial the appropriate dialing pre-fix to instruct the Irid-
ium switching network to route the call to the Iridium Credit Card Platform on the
ground side.
The phone number pre-fix digits determine the call routing on the ground.
Pre-Fix Digits for example, Phone Number for example, 1 757 947 1030
00
4-33
maintenance
FEATURE DESCRIPTION
CC PIN Dial-Around The Credit Card PIN Dial-Around is a PABX capability that allows the user to
bypass the credit card processing by entering a valid PIN. The Credit Card PIN
Dial-Around is only applicable when the Credit Card Restriction is enabled for that
given extension.
NOTE
It is assumed that Credit Card PIN Dial-Around and Credit Card Restriction
COS are enabled only when the IRT-2110/2120 and ICS-120A/220A system
has Credit Card provisioned SIM cards installed. When enabled, if a PIN is
entered by the user, if a match is found, the call is routed to the Iridium Post-Paid
switching network. If the entered PIN is not found in the global PIN Table, or is
not entered at all, the call is routed to the Iridium Credit Card Platform to collect
the User’s credit card information. This is true when the IRT-2110/2120 and
ICS-120A/220A system has Credit Card provisioned SIM cards installed.
PIN Restricted The PIN Restriction is a PABX capability configurable per user extension (Station)
port. The PIN Restriction is implemented as a Class of Service feature. PIN
Restriction is a call restriction applied only to outbound calls; the user may still make
a Station-to-Station call without using a PIN, even when PIN Restriction is enabled.
When PIN Restriction is enabled, and Voice Prompts are enabled, for a given
extension, a voice prompt is played back to enter the PIN (VP ID: PIN_ENTRY). If
Voice Prompts are not enabled for the given extension, a Bong Tone is played back
instead. The User must enter their PIN at that time. If the PIN matches an entry in the
global PIN Table, the User is granted access to make an outbound call. This feature
is N/A for the MCDU and should be set to DISABLED.
NOTE
Unlike the Credit Card PIN Dial-Around, PIN Restriction is not optional and
forces the User to enter a valid PIN before the call is processed. PIN Restriction
does not restrict Station-to-Station calls.
Executive Override Allows you to define the station priority for placing an outbound call, the highest
of which is priority 1. Calls placed from this station with predefined priority may
pre-empt an existing call if the existing call has been placed from a station with a
lower-priority setting. Set to ENABLED if desired. If you select this feature, the
station priority may be set in the Configuration Editor List Field, Set Priority. The
below listed options for this field are available:
• No Priority (default)
• Priority N, where N = a number between 1 and 6.
White-List Only The IRT-2110/2120 and ICS-120A/220A supports restricting calls to ONLY those
numbers contained in the ATS/AOC phone books. This feature can be enabled and
disabled on a station-by-station basis. Once enabled, each number entered will be
checked by the system to see if it is present in either the AOC or ATS Directories
before the number is dialed. No other outbound numbers will be allowed if they
are NOT contained in either directory.
Noise Reducer Enabling Noise Reduction processing enhances the air-to-ground audio quality in
noisy aircraft environments where a high level of background noise is present.
4-34
maintenance
4.4.3.4.1.1. CC PIN Dial-Around is not applicable when CC Restriction is not enabled. CC Restriction is not applicable when the
installed SIM card is not provisioned for credit card service.
4.4.4. The Trunks Editor.
The Trunks Editor screen allows a user to select the specific trunk to configure. Typically, the below listed information is displayed
here: trunk type (4-wire, Iridium, SBD), trunk number; and trunk status. Which trunks are displayed depends upon the unit config-
uration. If the 4-wire trunks have been disabled, then the unit will have the below configuration:
60 Iridium
61 Iridium
62 Short Burst Data (SBD) Modem (not configurable)
However, if the 4-wire trunks are enabled, then the unit will have the below listed configuration:
60 4-Wire Trunk
61 4-Wire Trunk
62 Iridium
63 Iridium
64 SBD Modem
The Hunt Groups will also need to be configured to conform to the Trunks assignments:
a. Highlight the Trunks Editor in the Configuration Editor Menu by using the <↑> and <↓> arrow keys.
b. Click <Enter> on the keyboard. The Trunks Editor screen is displayed.
c. Select a trunk by using the <↑> and <↓> arrow keys on the keyboard.
d. Push <Enter> to navigate to the Trunk Configuration Setting screen for the selected trunk. The display screen will appear, (see
Figure 4-29):
4.4.4.1. Trunk Configuration. The TRUNK CONFIGURATION SETTING screen allows a user to enable or disable the trunk,
assign an inbound hunt group, change the medium type, and adjust the audio gain control. The medium types vary depending on the
4-35
maintenance
type of equipment the trunk is connected to and the type of port used to interface with the equipment. The different medium types
available with 4-wire interfaces are as follows:
• Iridium
• Aero-I
• Aero-M
• Aero-H
• Aero-H+
• Iridium-A.
The Gain Control parameters permit gain or attenuation adjustments in the RX (EAR) and TX (MIC) directions, ranging between
-20 dB and +20 dB in 1 dB steps. 0 dB is the default gain value in both RX and TX directions. To change the features of each trunk:
a. Push <Enter> to move from the Trunks Editor screen to the Trunk Configuration Setting screen for the selected trunk.
b. Use the <↑> and <↓> arrow keys to select each field.
c. Use the <←> and <→> keys to select the desired option for each field:
(1) Configuration State: select either ENABLED or DISABLED.
(2) Hunt Group Name: select a number 1 to 4.
(3) Medium Type: see Paragraph 4.4.4.2.1 for values.
(4) Audio Fixed Gain Control: -20 to +20 dB.
d. Push <ENTER> to display the trunk features setting screen for the selected trunk. (Refer to Paragraph 4.4.4.2 for details and
step table.)
e. If more changes need to be made, go back to step 2; otherwise, navigate back to the configuration editor menu screen using the
<Esc> key.
f. Push <Ctrl/S> to save all the changes made in the settings.
NOTE
If appropriate, push <=> to copy all trunk configuration settings of the same type to the rest of the trunks, with the
exception of the configuration state. This step should be performed on the trunk configuration setting screen of
the trunk to be duplicated. If a trunk is disabled, it will remain disabled even though the trunk that is being copied
is enabled. This copy feature saves time when a common set of features and configurations is the same for each
trunk.
4.4.4.1.1. The display figure (see Figure 4-30) display sample trunk configuration setting screens:
4-36
maintenance
4.4.4.2. Trunk Features. The trunk features setting screen is used to change the class of service for each trunk. The fields can
be either enabled or disabled. A detailed description of each class of service is described below.
a. Push <Enter> to move from the trunk configuration setting screen for a given trunk to the trunk features setting screen for that
trunk.
b. Use the <↑> and <↓> arrow keys to select a COS feature (refer to Paragraph 4.4.4.2.1).
c. Use the <←> and <→> keys to select the desired option for each feature: either ENABLED or DISABLED.
d. If more changes need to be made go back to Step 4.4.4.2.b, otherwise navigate back to the configuration editor menu screen
using the <Esc> key.
e. Push <Ctrl/S> to save all the changes made in the settings. The display screen will appear, (see Figure 4-31):
4-37
maintenance
NOTE
When DISA is enabled and Voice Prompt is not, the service answers, then provides a dial tone. When DISA and
Voice Prompt are enabled, the service answers, then provides a voice prompt, then a dial tone.
4-38
maintenance
INBOUND OUTBOUND
HUNT GROUP STATION HUNT GROUP TRUNK
IN HG-1 15, 16 (MCDU) OUT HG-1 60, 61
IN HG-2 16, 15 (MCDU) OUT HG-2 61, 60
IN HG-3 15 (2-wire) OUT HG-3 60
IN HG-4 16 OUT HG-4 61
a. Highlight the HUNT GROUPS EDITOR in the configuration editor menu by using the <↑> and <↓> arrow keys.
b. Push <ENTER> on the keyboard. The hunt groups editor screen is displayed.
c. Select a hunt group by using the <↑> and <↓> arrow keys on the keyboard.
d. Push <ENTER> to navigate to the Outbound or Inbound Hunt Group Setting screen for the selected group. (Refer to Paragraph
4.4.6 for details.)
e. If more changes need to be made, go back to Step 4.4.5.c; otherwise, navigate back to the Configuration Editor Menu screen
using the <Esc> key.
f. Push <Ctrl/S> to save all the changes made in the settings.
NOTE
Changes can only be saved from the configuration editor menu screen.
4-39
maintenance
4-40
maintenance
NOTE
The flap discrete signal feature requires that the flap switch position signal be wired to the input.
a. Select the I/O pins editor option from the configuration editor menu (see Figure 4-35) using the <↑> and <↓> keys.
b. Push <Enter>.
4.4.8.1. The resulting screen is divided into two sections:
• Upper: I/O Inputs List
• Lower: I/O Relays List.
4-41
maintenance
4.4.8.2. Each I/O Editor screen record presents the current I/O pin setting in the below listed format: [<pin type> <pin number>]
Task <pin task> Parameter <pin task parameter>, where
• <pin type> is IN for inputs and OUT for relays.
• <pin number> is a sequential <pin type> number.
• <pin task> is a string of up to 20 characters.
The different tasks are defined for I/O inputs and relays. The <pin task parameter> is a string up to 20 characters. The task-dependent
parameters are predefined and described next.
a. Select the highlighted pin by clicking on <Enter>.
b. Push <Esc> to return to the I/O pins editor screen. The unit software opens the I/O Pin Setting screen to allow you to select a
pin task.
4.4.8.3. I/O Input Pin Setting Screen. The I/O INPUT PINS SETTING screen (see Figure 4-36) allows the user to select a pin
task and pin parameter. It also allows the user to enter an I/O pin description of up to 20 characters. The available tasks for the I/O
input pins are defined below.
N/A No Task assignment.
FLAPS Prohibits calls to the cockpit during take-off and landing flight phases. Before routing a call to the
cockpit extension, the unit application checks signal level on the input pin assigned with the FLAPS
task. The I/O input signal level depends on the flaps position on the aircraft. No parameter is required
for this task. This feature requires that the aircraft flap switch position signal be wired to the input.
Currently limited tasks have been assigned to the I/O pins. As customer requirements become known,
additional features and tasks may be assigned. To be notified when additional features are added, refer
to the instructions on how to receive email updates as Rockwell Collins issues them.
SLAVE_SELECT In a dual SATCOM installation, when this input pin is activated (grounded), the unit reports as a
slave SDU device (sets bit 18 of Label 270 word).
4-42
maintenance
DYNAMIC_CC DYNAMIC_CC, or Dynamic Credit Card Restriction, applies Credit Card Restriction to user
extensions configured as such. When the input pin is sensed as active (grounded), the PABX restricts a
given User extension port to Credit Card calls only. Each User port may be configured individually
with Dynamic Credit Card Restriction. This change was an insignificant modification to the existing
software architecture.
RELAY Allows input to trigger a change on the selected output relay state. This is primarily a production
task setting used for testing.
AIR/GND AIR/GND determines how the configured input discrete is interpreted to determine whether the aircraft
is in air. AIR=OPN - Discrete=Ground, NOT IN AIR- Discrete=Ground, NOT IN AIRAIR=GND -
Discrete=Open, NOT IN AIR - Discrete=Ground, IN AIR
NOTE
IMPORTANT: When making changes to either the I/O Pin Task or the I/O Pin Parameter the unit will need to be
rebooted.
4.4.8.4. I/O Relay Setting Screen. The I/O RELAY SETTING screen (see Figure 4-37) allows the user to select a Pin Task
and Pin Parameter. It also allows the user to enter an I/O Pin Description of up to 20 characters. The task list for I/O relays and a
description of the task is below.
N/A N/A
LBT_INUSE The LBT_INUSE discrete output provides a ground on the selected output pin when the selected LBT
is actively in progress or connected in an active call (voice or data).
LBT_AVAILABLE The LBT_AVAILABLE discrete output provides a ground on the selected output when the selected
LBT is available for placing an outbound call (voice or data). Signal strength is a factor in reporting
the availability of the LBT.
4-43
maintenance
MAWEA_CADENCE The MAWEA (Modular Avionics and Warning Electronics Assembly) Cadence discrete output
provides a cadence on the selected output pin when there's an incoming call on an Iridium Satcom
channel ringing one of the selected stations (or groups). 1. I/O Pin Parameter: Select a station
number 15, 16, or MCDUs.
MAWEA_PULSE The MAWEA Pulse discrete output provides a single pulsed output on the selected output pin when
there is an incoming call on an Iridium Satcom channel ringing one of the selected stations or groups.
MCDU_MAWEA MAWEA Output: The IRT-2110/2120 and ICS-120A/220A (SDU) provides a ground to the MAWEA
(Modularized Avionics Warning Electronics Assembly) to activate the chime. The MAWEA discrete
output is grounded when there‘s an Incoming Call Indication, and returns to open state when the
call is answered (Off Hook Indication). The MAWEA Output is only activated for incoming calls
(ground-to-air).
STATION_HOOK Indicates when a particular station goes off hook. The pin parameter determines to which station
the relay output is assigned.
STATION_RING Indicates when a particular station is ringing. The pin parameter determines to which station the
relay output is assigned.
DFDAU_AUDIO When the IRT-2110/2120 and ICS-120A/220A is configured for MCDU on the 4-wire ports, DFDAU
(Digital Flight Data Acquisition Unit) output goes to a ground state when the call is active and returns
to an open state once the call is terminated. All MCDU 4-wire ports will activate output during the
connected trunk state (MCDU status = ACTIVE). Cabin-to-Cockpit calls are optionally configurable
to activate output.
STATION_BUSY Provides status when an extension is busy. The relay is closed when the station is NOT idle (includes
off-hook and ring status), and open otherwise
IRID- The IRIDIUM_NOT_AVAIL output task is assignable to any of the eight output pins, and does not
IUM_NOT_AVAIL- include a configurable parameter. The IRIDIUM_NOT_AVAIL output indicates that all Iridium data
ABLE & voice channels are not available for data or voice calls. When this condition exists, the configured
LBT_NOT_AVAILABLE discrete output is activated (grounded state). The Iridium SBD channel is
not considered in the IRIDIUM_NOT_AVAIL output.
IRIDIUM_STATUS The IRIDUIM_STATUS output task is assignable to any of the eight output pins, and does not include
a configurable parameter. The output pin is grounded when at least one of the Iridium channels
is registered on the Iridium Network and has sufficient signal strength (2 bars or greater) for call
processing (does not apply to SBD modem).
IRIDIUM_AVAILABLE The IRIDIUM_AVAILABLE output task is assignable to any of the eight output pins, and does not
include a configurable parameter. The output pin is grounded when one of the LBT devices is in an
IDLE condition; the output is open otherwise (does not apply to SBD modem).
ACP_EPIC_CD1 and ACP_EPIC_CD1 and ACP_EPIC_CD2 work in conjunction with each other to provide the necessary
ACP_EPIC_CD2 ATG and GTA call progression discretes to the Honeywell Primus Epic Avionics. (This feature is only
available with HW 713616-2, 713617-2, 713617-3 with SW 710502-XX installed.)
For task and the expected parameter(s) that need setting when configured, refer to Table 4-8.
4-44
maintenance
4-45
maintenance
ACP_EPIC_CD2 1. I/O Pin Parameter: Select a station number 11, 12, 13, 14, 15 or 16.
2. Describe the task in the Description field.
• Answer Active, if enabled, indicates the output will become active (grounded) when the call is answered by the selected station.
• Cabin Active, if enabled, indicates the output is allowed to be triggered by a cabin call to the selected station.
4-46
maintenance
4.4.9.1. Refer to Table 4-9 for Serial Port for RS232 Data Interface Editor.
Serial Port 1 Mode Choose either 3-wire or 9-wire. The default value is 9-wire.
Serial Port 1 Route Choose either LBT-1 or LBT-2 (or LBT-1 for the IRT-2110 and ICS-120A)
Serial Port 2 Mode Choose either 3-wire or 9-wire. The default value is 9-wire. Serial Port 2 is
only available on -2 and -3 models.
Serial Port 2 Route Choose either LBT-1 or LBT-2. Serial Port 2 is only available for the IRT-
2120 and ICS-120A/220A (710616- 2, 710617-2, 710616- 3 and 710617-3).
4-47
maintenance
NOTE
When a PIN is disabled, it cannot be used for call processing.
4.4.10.1.1. The PIN NUMBER SETTING screen, see Figure 4-40, displays the below listed fields:
PIN # Defines the 4-digit PIN.
PIN Status Defines the current PIN status. If PIN is DISABLED, it cannot be used for call processing.
To modify the PIN settings:
a. Select a PIN table entry using the <↑> and <↓> keys.
b. Push the <Enter> key on the highlighted PIN row to access the PIN number setting screen.
c. Change the current status by using the <←> and <→> keys.
d. Change the PIN, if needed, by entering a new 4-digit PIN.
e. Push the <Esc> key to return to the PIN table editor screen.
4-48
maintenance
4-49
maintenance
4.4.11.1. All system editor fields are normally used for information purposes only. The system editor screen displays the below
listed data:
Customer Name Aircraft Customer Name.
Logging Mode The data logging feature is configurable to run once, run continuously, or stop to permit collection of
the device operation status as needed.
CC SIM Prefix This field identifies installed SIM card serial number(s) provisioned for post-paid credit card calling
service. The system software reads the installed SIM card serial number(s) and compares with the CC
SIM Prefix configuration field. If a match is found, the appropriate dialing prefixes are automatically
dialed for outbound calls. More than one SIM card serial number may be entered in this configuration
field as long as each serial number is separated by a comma. The SIM card serial number (a.k.a.
ICCID) is displayed on the Iridium Trunk Monitor screen, see Figure 4-53, and can also be found in
the subscriber‘s account information with the Service Provider.
Timeouts in seconds are defined below:
No Digits Period of time allowed between off-hook condition and first digit is dialed.
Inter Digits Period of time allowed between dialed digits.
DISA Ring No Answer Period of time allowed before incoming DISA call is terminated.
DISA No Digits Period of time allowed between off-hook state and first digit is dialed.
Incoming No Answer Period of time allowed before incoming call is terminated.
Incoming Ring Station Period of time allowed before incoming Ring Station call is terminated.
USB Password Required Enabled or Disabled. Enabling this option requires a password to be entered before using the
Configuration menu or SIM menu.
HW P/N Hardware part number.
CFG DB P/N Configuration Database part number.
VP DB P/N Voice Prompt Database part number.
CIM P/N Iridium Configuration Module part number.
To change the settings:
4-50
maintenance
NOTE
The data fields are usually pre-assigned and should not be changed.
a. Use the <↑> and <↓> keys to move the cursor to the desired field and push <Enter>.
b. Either type in the requested data or use the <←> and <→> keys until the desired entry is highlighted.
c. Push <Esc> to return to the previous screen.
4.4.12. ARINC 429 Editor.
The Aeronautical Radio Inc. (ARINC) 429 Editor screen (see Figure 4-42) presents the user with access to four separate editors:
• Aircraft Communications Addressing and Reporting System ACARS Datalink Editor
• Left MCDU Editor
• Right MCDU Editor
• Crew MCDU Editor.
To access the ARINC 429 editor screen:
a. Select the ARINC 429 EDITOR option from the configuration editor menu using the <↑> and <↓> keys.
b. Push <Enter>.
c. Push <Esc> to return to the unit setting screen.
4.4.12.1. ACARS Datalink Editor. To access the ACARS datalink editor menu screen:
a. Select the ARINC-429 EDITOR option from the configuration editor menu using the <↑> and <↓> keys.
b. Push <Enter>.
4-51
maintenance
c. Select the ACARS datalink editor option from the ARINC-429 editor menu using the <↑> and <↓> keys.
d. Push <Enter>.
e. Push <Esc> twice to return to the configuration editor menu screen. The display screen, (see Figure 4-43) will appear:
4-52
maintenance
NOTE
SBD messaging must be enabled through the Iridium Service Provider for the transceiver that is designated for
ACARS use. The default is the SBD modem.
When ACARS is enabled, no other data device can access the selected data port. Rockwell Collins recommends
that handsets for voice calls also be restricted from using the ACARS SBD Modem, as messages cannot be trans-
mitted or received if a voice call is in progress on the transceiver.
4.4.12.2. Left MCDU Editor. This screen (see Figure 4-44) allows the user to set the parameters for the left MCDU. To access
the left MCDU editor screen:
a. Select the ARINC-429 EDITOR option from the configuration editor menu using the <↑> and <↓> keys.
b. Push <Enter>.
c. Select the LEFT MCDU EDITOR option from the ARINC-429 Editor menu using the <↑> and <↓> keys.
d. Push <Enter>.
e. Push <Esc> twice to return to the configuration editor menu screen. The display screen will appear:
4-53
maintenance
4-54
maintenance
d. Push <Enter>.
e. Push <Esc> twice to return to the Configuration Editor screen. The display screen (see Figure 4-46) will appear:
4-55
maintenance
NOTE
DC1 Scratchpad ACK option should remain disabled and should only be enabled if the user experiences any loss
of information on the scratchpad line.
4-56
maintenance
MCDU Page Display The MCDU Page Display field allows the installer to select the page heading
in the corner of the MCDU for multiple pages. The selectable options are:
1ud: which represents the current MCDU layout with the current page num-
ber followed by the u (up arrow), and d (down arrow) characters as needed.
1/8: which represents the layout showing the current page number followed by the total page count.
1/8ud: which represents the layout showing the current page number followed by the total page count
followed by the u (up arrow) and d (down arrow) characters as needed.
Audio Channel 1 Lbl Allows for customized SAT channel labels on the MCDU display - to better match aircraft integrations.
Each of the two SAT channel labels, primary and secondary, is configurable to display as SAT-1 and
SAT-2, or SAT-L and SAT-R.
Audio Channel 2 Lbl Allows for customized SAT channel labels on the MCDU display - to better match aircraft integrations.
Each of the two SAT channel labels, primary and secondary, is configurable to display as SAT-1 and
SAT-2, or SAT-L and SAT-R.
Display History Menu ENABLED: shows the History menu option on the MCDU.
DISABLED: does not show the History menu option on the MCDU.
LBT1 Installed ENABLED: indicates to the system that the LBT1 is installed and available for use.
DISABLED: indicates to the system that the LBT1 is not installed and is unavailable for use.
LBT2 Installed ENABLE: indicates to the system that the LBT2 is installed and available for use.
DISABLED: indicates to the system that the LBT2 is not installed and is unavailable for use.
SBD Installed ENABLE: indicates to the system that the SBD Modem is installed and available for use.
DISABLED: indicates to the system that the SBD Modem is not installed and is unavailable for use.
User ORT Password The customizable password that allows access to MCDU USER ORT pages, MCDU ATC DB
Directory Detail pages, and then MCDU AOC DB Directory Detail. The password has no minimum
requirements and is completely customizable. 8-character maximum
Static Titles ENABLED: SAT will display for MCDU page titles/sub-titles where appropriate.
DISABLED: the MCDU Menu String config parameter applies to page titles/sub-titles also.
Users Secure Parameters ENABLED: MCDU will display the value of and allow changes to UORT parameter.
DISABLED: MCDU will display the value of, but not allow change to UORT parameter:
AIR/GND STATE
RESTRICT ORT IN AIR (ENABLED/DISABLED)
LBT-1 (ENABLED/DISABLED)
SBD (ENABLED/DISABLED)
SBD HW REDUND (ENABLED/DISABLED)
LBT-1 GTA CKPT ROUTING
LBT-2 GTA CKPT ROUTING
SAT CH-1 (ENABLED/DISABLED)
SAT CH-1 ATG CKPT RTG
SAT CH-1 4WIRE
SAT CH-2 ATG CKPT RTG
SAT CH-2 4WIRE
Display AOC Company Display COMPANY shortcut on SAT DIRECTORY INDEX page (if there is at least one non BLANK
directory entry in the AOC sub-directory COMPANY)
Display AOC Operations Display COMPANY shortcut on SAT DIRECTORY INDEX page (if there is at least one non BLANK
directory entry in the AOC sub-directory COMPANY)
4-57
maintenance
a. Use the <↑> and <↓> keys to scroll through the monitors menu.
b. Push the <Enter> key when the desired option is highlighted.
c. Push the <Esc> key to return to the previous screen.
4-58
maintenance
4.5.1.1. The below listed information is displayed on the system information monitor screen:
Customer Name Customer ID.
Software P/N Software Part Number.
DSP Version DSP (Digital Signal Processor) version number.
Software Build Date Date of current software build.
Software Version Version number.
Software CRC 32-bit CRC which validates the software load against the QA records for the software release. It
also verifies a software load has been successful.
Compiler Version Utility compiler version for IRT and Firmware compiler version for ICS.
Config CRC Config CRC is an eight digit hexadecimal number and may be used to uniquely identify/verify the
active system configuration.
Logging Mode The data logging feature is configurable to run once, run continuously, or stop to permit collection of
the device operation status as needed.
Number of Stations The IRT-2110/2120 and ICS-120A/220A has a maximum of 6 stations.
Number of Trunks The IRT-2120 and ICS-220A has 2 Iridium trunks and 1 SBD modem. The IRT-2110 and ICS-120A
has 1 Iridium trunk and 1 SBD modem.
UCH-Fax Option The UCH-Fax feature ―[NOT INSTALLED] for the IRT-2110/IRT-2120 and available only on
AF and BF models for ICS.
Timeouts in Seconds are defined below:
No Digits Period of time allowed between off-hook condition and first digit is dialed.
Inter Digits Period of time allowed between dialed digits.
DISA Ring No Answer Period of time allowed before incoming DISA call is terminated. Not applicable to Iridium trunks.
DISA No Digits Period of time allowed between off-hook state and first digit is dialed. Not applicable to Iridium trunks.
Incoming No Answer Period of time allowed before incoming call is terminated. Not applicable to Iridium trunks.
Incoming Ring Station Period of time allowed before incoming Ring Station call is terminated.
RS-232 Data Interface 1 Indicates which LBT is being accessed (LBT-1 or LBT-2) and what the configuration is (9-wire
or 3-wire).
4-59
maintenance
RS232 Data Interface 2 Indicates which LBT is being accessed (LBT-1 or LBT-2) and what the configuration is (9-wire
or 3-wire) for Serial Port #2.
NOTE
Customer information listed here, the customer name, tail number, and serial number, are customizable and do not
affect the performance of the system.
NOTE
Optionally, you can push the <F1> key instead, and then skip to step c.
4-60
maintenance
4.5.2.2. Station Call Control Monitor Screen. To access a station’s call control information and current state:
a. Use the <↑> and <↓> keys to highlight the desired station on the stations monitor screen.
NOTE
Optionally, you can push the <F1> key instead, and then skip to step c.
b. Push the <Enter> key to bring up the station call control monitor screen.
c. Push the <Esc> key to return to the previous screen. The display screen (see Figure 4-51) appears:
4-61
maintenance
4.5.2.3. Trunks Monitor Screen. The trunks monitor screen (see Figure 4-53) provides overall information about the state of
the three available trunks. To display this screen:
a. Use the <↑> and <↓> keys to highlight the trunks monitor option in the monitors menu.
NOTE
Optionally, you can push the <F2> key instead, and then skip to step c.
NOTE
Which trunks are displayed will depend upon the configuration of the unit.
4-62
maintenance
4.5.2.3.1. Trunk Call Control Monitor Screen: Iridium. To access a selected trunk’s call control information and current state
(see Figure 4-54):
a. Use the <↑> and <↓> keys to highlight the desired trunk on the trunks monitor screen. See Figure 4-53.
b. Push the <Enter> key to bring up the TRUNK CALL CONTROL MONITOR screen. See Figure 4-54.
c. Push the <Esc> key to return to the previous screen.
4-63
maintenance
4.5.2.3.1.1. The necessary information is displayed on the trunk call control monitor screen.
Trunk Medium Type Iridium, etc.
Trunk Number Normally a number from 60 to 63, depending upon configuration.
Trunk Status Choices: ENABLED or DISABLED.
Connected Port Port connected to this trunk.
Held Port Port on hold by this station.
Detected DTMF Detected DTMF digit.
Dialed Number Phone number dialed on this trunk.
Processed Number Phone number processed by this trunk.
DTMF Count Number of DTMF digits dialed.
Follow-On Dial DTMF digits for follow-on dialing.
Character Count Number of follow-on digits dialed.
Last Event Most recent event to occur on the port.
Port State Current state of port.
4.5.2.3.1.2. Trunk Configuration Monitor Screen: Iridium. To check the configuration details for a selected trunk, push <En-
ter>, see Figure 4-55.
4-64
maintenance
4.5.2.3.2. Iridium SBD Modem Monitor. To access the Iridium SBD modem monitor screen. See Figure 4-56:
a. Use the <↑> and <↓> keys to highlight the SBD modem on the trunks monitor screen. See Figure 4-53.
b. Push the <Enter> key to bring up the Iridium SBD modem monitor screen. See Figure 4-56.
c. Push the <Esc> key to return to the previous screen.
4-65
maintenance
4.5.2.3.2.1. The necessary information is displayed on this screen and is useful in monitoring SBD modem traffic.
Modem Revision Software revision for the SBD/LBT modem.
Modem IMEI SBD/LBT IMEI number needed to provision the modem for ACARS traffic.
Last MOMSN Previous Mobile Originated Message Sequence Number which ranges from 0 to 65535 in value. For
each message exchange this value is incriminated and saved by the SBD modem. The IRT and ICS
unit does not reset this value. It can be reset using AT commands if needed.
Sent Messages Count Total number of messages sent by the unit since power on.
Waiting Messages Count Number of messages waiting to be delivered by the IRT and ICS unit.
Received Messages Total number of messages received by the IRT and ICS unit since power on.
Count
Signal Strength Polled every 15 seconds from the LBT and displayed on the screen.
Last Status Shows the text response from the last modem transfer. On power up, the status is successful regardless.
Status (A, B): A, B indicates the (MO, MT) status in the SBDIX response from a transaction. MO
session status provides an indication of the disposition of the mobile originated transaction.
Port State Shows the current state of the modem. Possible states include:
IDLE (99% of the time, default state) WAITING_FOR_STRING WAIT-
ING_FOR_OK WAITING_FOR_BLOCK
4.5.2.3.3. Hunt Groups Monitor Screen. The HUNT GROUPS MONITOR screen (see Figure 4-57) shows a user the port
assignments for each inbound and outbound hunt group.
4-66
maintenance
4-67
maintenance
4-68
maintenance
4.5.4.1. ACARS Datalink Monitor. This screen provides ACARS configuration information and information about the service
provider. To access this screen:
a. Use the <↑> and <↓> keys to highlight the monitors menu until the ARINC-429 monitor options is highlighted.
b. Push the <Enter> key.
c. Use the <↑> and <↓> arrow on the ARINC-429 monitor menu until ACARS datalink monitor option is highlighted.
d. Push the <Enter> key.
e. Push the <Esc> key to return to the previous screen. See Figure 4-60.
4-69
maintenance
4-70
maintenance
4-71
maintenance
4-72
maintenance
4-73
maintenance
c. Push <Enter>.
4-74
maintenance
4.6.3.1. Sample General Log Screen. The log capture and stop procedures follow.
4.6.3.1.1. To capture the log as it scrolls on the screen:
a. Navigate to the screen displaying the log to be captured.
b. Click on Transfer on the HyperTerminal menu bar at the top of the screen.
c. Select the Capture Text menu option (see Figure 4-66).
d. Enter the full path and file name when prompted (see Figure 4-67).
e. Click Start.
4.6.3.1.2. To stop the text capture:
a. Click on Transfer on the HyperTerminal menu bar at the top of the screen.
b. Select the Capture Text menu item, then the Stop sub-menu option on the right (see Figure 4-68).
4-75
maintenance
c. Push <Esc> to return to the Logging Menu, each line in the (see Figure 4-69), indicates:
• The relavent LBT.
• The signal level as reported by the LBT.
• Any outstanding events.
• The current call state.
• The SIM status as reported by the LBT.
• The SIM status as reported by the CIM.
• The three common information indicators as reported by the LBT.
NOTE
Do not change screens while logging to a file. Otherwise, you will not get the messages that are displayed on the
screen.
4-76
maintenance
4.6.3.1.2.1. The Iridium log (see Figure 4-70) captures activity on the data and voice transceivers. The IRT-2110 product contains
one data and voice transceiver, while the IRT-2120 contains two data and voice transceivers. The ARINC-429 Log includes a label
number at the end of each line.
4.6.3.1.2.2. The Iridium SBD Log (see Figure 4-71) captures activity on the SBD Iridium transceiver. The IRT-2110, IRT-2120,
ICS-120A and ICS-220A products both contain an SBD transceiver.
4-77
maintenance
4-78
maintenance
4.6.5.3. LBT Logging. The LBT information is loaded into the log every minute, if there are no updates to the information.
Example LBT 1: 21/10/2009 14:49:38 G,LBT:1,SigLvl:5,Asynch Event:,Call State:Idle,SIM Status:SIM OK,SIM In-
serted,InUse:UNKNOWN,NoSvc:Off,HomeZone:On Example LBT 2: 21/10/2009 14:49:38 G,LBT:2,SigLvl:5,Asynch
Event:,Call State:Idle,SIM Status:SIM OK,SIM Init,InUse:UNKNOWN,NoSvc:Off,HomeZone:On
4.6.5.4. SBD Logging. The SBD logging interface only captures internal SDU activity for ACARS data-link service. SBD
activity caused by an external serial application is not shown in the SBD logging interface.
Example: 21/10/2009 14:49:38 G,SBD,SigLvl:4,Last Status:Successful,MO SN:50612,MO Size:36,MT SN:65535,MT Size:0,Msg
Waiting:0
4.6.5.5. ACARS Logging. After the ACARS message – represented below with the placeholder “TXT” - comma separated fields
indicate the destination device: SDU for downlink traffic, ATG; DMU for uplink traffic, GTA; mode; technical ACK; message label;
block ID; and block check sequence Cyclic Redundancy Check (CRC) for the ACARS message.
Example: 22/10/2009 16:07:26 G,TXT:ACARS,SDU,2,,Q0,0,16C8
4.7. TROUBLESHOOTING.
The information in this section is intended to help you troubleshoot possible installation problems. The information featured here
will ultimately help you determine simple installation errors and correct them. If you are in need of further assistance please contact
Rockwell Collins Technical Support.
4.7.1. LED Behavior During Boot Up.
When the IRT-2110/2120 and ICS-120A/220A is first powered up the Power LED behaves in a defined pattern. It is important
to understand this pattern because it will give you opportunities to access the bootloader and will help you begin troubleshooting
if necessary. There are two distinct behaviors, detailed below, that occur during different boot-up scenarios: one when the IRT-
2110/2120 and ICS-120A/220A is powered up while connected to a PC via USB, and the other when it is not connected to a PC.
4.7.1.1. Power LED during Boot Up when the Unit is Connected to a PC via USB. The total time for this start-up procedure
is approximately 50 seconds. See Figure 4-72.
4.7.1.2. Power LED during Boot Up. The total time for this start-up procedure is approximately 40 seconds. See Figure 4-73.
4-79
maintenance
NOTE
The LEDs are best used as a diagnostic tool after the Boot-Up behavior, detailed in Paragraph 4.7.1 is completed.
Do not attempt to troubleshoot using the LEDs until after that process is complete.
4-80
maintenance
4-81
maintenance
4.7.2.1. If the LEDs indicate a hardware failure or DPL communication failure, follow the steps below.
a. Check that the SIM cards are installed in the ICM/CIM correctly.
b. Check that the ICM/CIM is configured and that the IRT-2110/2120 and ICS-120A/220A is configured properly to your system.
Make sure that transmit and receive speeds are correct.
c. After checking and correcting any potential problems mentioned in the above steps, if your system is still indicating a fault,
contact Rockwell Collins technical support for additional assistance before determining the need to enact an RMA procedure.
4.7.3. Troubleshooting Stages.
See Figure 4-74 for trouble shooting stages.
4-82
maintenance
4-83/(4-84 Blank)
maintenance
4.7.3.1. Stage 1 Trouble Shooting Exterior Indications. See Figure 4-75 for Front Panel Diagnostic Indicators.
4-85/(4-86 Blank)
maintenance
4-87/(4-88 Blank)
maintenance
4.7.3.2. Outbound Calling Troubleshooting. See Figure 4-76 for Outbound Calling Troubleshooting.
4-89/(4-90 Blank)
maintenance
4-91/(4-92 Blank)
maintenance
4.7.3.3. Outbound Fax Troubleshooting. See Figure 4-77 for Outbound Fax Troubleshooting.
4-93/(4-94 Blank)
maintenance
4-95/(4-96 Blank)
maintenance
4.7.3.4. Inbound Calling Troubleshooting. See Figure 4-78 for Inbound Calling Troubleshooting.
4-97/(4-98 Blank)
maintenance
4-99/(4-100 Blank)
maintenance
4.7.3.5. Inbound Faxing Troubleshooting. See Figure 4-79 for Inbound Faxing Troubleshooting.
4-101/(4-102 Blank)
maintenance
4-103/(4-104 Blank)
maintenance
4.7.3.6. RS232 Data Port Troubleshooting. See Figure 4-80 for RS232 Data Port Troubleshooting.
4-105/(4-106 Blank)
maintenance
4-107/(4-108 Blank)
maintenance
4-109/(4-110 Blank)
maintenance
4-111/(4-112 Blank)
maintenance
4.7.3.8. Extension Verification Troubleshooting. See Figure 4-82 for Extension Verification Troubleshooting.
4-113/(4-114 Blank)
maintenance
4-115/(4-116 Blank)
maintenance
4.7.3.9. Troubleshooting with the NxtLink Iridium Utility. See Figure 4-83 for No Dial Tone at Extension.
4-117/(4-118 Blank)
maintenance
4-119/(4-120 Blank)
maintenance
4.7.3.10. Extension Does not Ring. See Figure 4-84 for Extension Does not Ring.
4-121/(4-122 Blank)
maintenance
4-123/(4-124 Blank)
maintenance
4.7.3.11. Unable to make an Extension to Exentension Call. See Figure 4-85 for Unable to make an Extension to Exenten-
sion Call.
4-125/(4-126 Blank)
maintenance
4-127/(4-128 Blank)
maintenance
4.7.3.12. Unable to receive Ground-to-Air Call. See Figure 4-86 for Unable to receive Ground-to-Air Call.
4-129/(4-130 Blank)
maintenance
4-131/(4-132 Blank)
maintenance
4-133/(4-134 Blank)
maintenance
4-135/(4-136 Blank)
maintenance
4.7.3.14. MCDU Ports Verification. See Figure 4-88 for MCDU Ports Verification.
4-137/(4-138 Blank)
maintenance
4-139/(4-140 Blank)
maintenance
4.7.3.15. Setting the MCDU Label. See Figure 4-89 for Setting the MCDU Label.
4-141/(4-142 Blank)
maintenance
4-143/(4-144 Blank)
maintenance
4-145/(4-146 Blank)
maintenance
4-147/(4-148 Blank)
maintenance
4-149/(4-150 Blank)
maintenance
4-151/(4-152 Blank)
maintenance
4.7.3.18. Data Call Verification. See Figure 4-92 for Data Call Verification.
4-153/(4-154 Blank)
maintenance
4-155/(4-156 Blank)
maintenance
4.7.3.19. Input and Output Discrete Verification. See Figure 4-93 for Input and Output Discrete Verification.
4-157/(4-158 Blank)
maintenance
4-159/(4-160 Blank)
maintenance
4.7.3.20. In-depth Troubleshooting. See Figure 4-94 for Unit Voltage Verification.
4-161/(4-162 Blank)
maintenance
4-163/(4-164 Blank)
maintenance
4.7.3.21. No Signal on Antenna Connections. See Figure 4-95 for No Signal on Antenna Connections.
4-165/(4-166 Blank)
maintenance
4-167/(4-168 Blank)
maintenance
4.7.3.22. No Dial Tone on 2-Wire Extension. See Figure 4-96 for No Dial Tone on 2-Wire Extension.
4-169/(4-170 Blank)
maintenance
4-171/(4-172 Blank)
maintenance
4.7.3.23. Extension does not Ring. See Figure 4-97 for Extension does not Ring.
4-173/(4-174 Blank)
maintenance
4-175/(4-176 Blank)
maintenance
4-177
maintenance
f. Make sure that the station does not have No_Ring_Flaps_COS enabled and the flaps input is not grounded. If the station has
No_Ring_Flaps_COS and the flaps input is grounded, then the station is working as intended.
g. Check the handset wiring and correct any issues.
h. Change the configuration state to Enabled.
i. Make sure the hunt group name, class of service and features of the extension.
j. Save any configuration changes.
4.7.4.3. Unable to place an Extension-to-Extension Call. If a given telephone station can not complete an extension-to-ex-
tension call there are several possible problems to consider: the extension is not correctly configured; the extension is not correctly
installed; and/or there are similar issues with the extension you are trying to contact. To determine the possible problem and correct
it, follow the table below.
a. Open the Hyper Terminal.
b. Push <F3> for the Main Menu.
c. Push <1> for the Monitor Menu.
d. Push <2> for the Stations Monitor.
e. Is the station going off-hook when you pick it up.
(1) If the station does not go off-hook, go to Step 4.7.4.3.f.
(2) If the station does go off-hook go to Step 4.7.4.3.g.
f. Check the handset wiring and correct any issues.
g. Push <F3> for the Main Menu.
h. Push <3> for the Configuration Editor.
i. Push <2> for the Stations Editor.
j. Confirm that the COS Station-to-Station is enabled.
(1) Check: If the Station-to-station COS is enabled go to Step 4.7.4.3.k.
(2) If the Station-to-station COS is not enabled go to Step 4.7.4.3.l.
k. Repeat the steps above for the extension you are placing a call too.
l. Enabled the Station-to-station COS.
m. Save any configuration changes.
4.7.4.4. Unable to Place a GTA Call. If a given telephone station can not complete a Ground-to-Air (GTA) call (i.e. receive
a call from a ground-based caller) there are several possible problems to consider: the extension is not correctly configured or the
extension is not correctly installed. To determine the possible problem and correct it, follow the table below.
a. Open the Hyper Terminal.
b. Push <F3> for the Main Menu.
c. Push <1> for the Monitor Menu.
d. Push <2> for the Stations Monitor.
e. Make sure the station is ringing when it receives a GTA call.
(1) If the Monitor shows that the station is ringing go to Step 4.7.4.4.f.
(2) If the Monitor shows that the station is not ringing go to Step 4.7.4.4.g.
f. Check the handset wiring.
g. Push <F3> for the Main Menu.
h. Push <3> for the Configuration Editor.
i. Push <2> for the Stations Editor.
4-178
maintenance
b. Check the configuration of the Inbound Hunt Groups editor using the Hunt Groups Editor screen (see Figure 4-99).
4-179
maintenance
c. Connect a 2-wire POTS telephone to the Service Jack on the front of the unit.
d. Check station-to-station calls and determine whether or not they ring.
e. Connect the HyperTerminal and view the current status via the Monitor screens, as in the screen shot below (see Figure 4-100).
f. Check each extension configuration and wiring. Correct any possible configuration and/or wiring errors.
g. Contact Technical Support for further assistance.
4.7.4.6. ACARS is not Incoming and Unable to Send and Receive Messages . Perform the procedure that follows:
a. Check if the service is activated with the service provider. If the service is not activated, contact your Service Provider for more
information.
b. Using the HyperTerminal Utility, check that you have the:
4-180
maintenance
c. Check if ACARS goes into a logged-on state. Reconfigure ACARS to correctly enter a logged-on state.
d. Contact Rockwell Collins Technical Support for further assistance.
4.7.4.7. No SAT Display on the MCDU. Perform the procedure that follows:
a. Confirm configuration.
• Check that the 4-wire ports 15 and/or 16 are enabled and wired per Hyperterminal configuration utility. Enable them if they
are disabled.
• Check that the ARINC-429 bus for the MCDU is configured properly via the NxtLink utility per the MCDU specification
for speed (high or low).
NOTE
The IRT-2110/2120 and ICS-120A/220A does not attempt to determine status of other equipment on the ARINC-
429 bus by monitoring the 270 status words from other equipment. The minimum requirement is that any MCDU
connected should be transmitting a periodic word at least once every 1-second to keep the link active. There is no
requirement for the connected DMU.
Received ARINC-429 words need to be referenced to the appropriate ARINC document describing the commu-
nications and status information. Information contained here only applies to the transmitting SDU (IRT-2120 and
ICS-220A).
4.7.5.1. Hexadecimal Conversions. ARINC-429 uses Hexadecimal notation to represent binary digits. Refer to Table 4-11 for
converting from the more compact HEX format of the ARINC-429 data to bits and octal digits.
4-181
maintenance
NOTE
HEX is normally grouped in 4 binary bits and Octal is grouped in 3 binary bits (with the leading 0 removed from
the 4-bits displayed in the table).
4.7.5.2. ARINC-429 Log Format. The fields of an ARINC-429 message and each field meanings are explained below.
FIELD MEANING
15/06/2006 Date in day/month/year format
00:01:15* Time in UTC (with valid identifier)
00:01:15G Time in UTC (or GMT)
ARINC Write Word This indicates ARINC write/send command
dev=0, Device number 0-first ARINC interface, etc. Transmitters are from 0 to 2 and receivers are from 0 to 5.
data=0004E3 This is the data portion of the ARINC-429 word and represents bits 9-32 of the word.
lbl=172 This represents bits 1-8 of the ARINC-429 word and signifies the content of the ARINC-429 word.
4.7.5.3. Octal Label 172 (Subsystem Identifier word). This ARINC-429 word is described in the ARINC-761 document and
allows other equipment to be told of the SAL (sub-address label) to use when communicating with the IRT-2120 and ICS-120A/220A
unit. This label has two fields:
1. Bits 9-16 represent the octal SAL number to use and are in the same format as the ARINC-429 label. (hex E3 = 1110 0011 =
11 000 111 = octal 307).
2. Bit 19 is set to indicate an Iridium interface.
The ARINC-429 bits for the label field are transmitted MSB (Most Significant Bit) first on the ARINC-429 interface. This means
the bits are transmitted from the device to the ARINC-429 interface in reverse order; since, the least significant bit on the 32-bit
word is transmitted first. To translate octal bits to hexadecimal bits:
a. Write out the octal label in bit format. For example, 172 in octal would translate to 01 111 010 in binary.
4-182
maintenance
b. Reverse the bits. Therefore as in the above example 01 111 010 would be written as 01 011 110.
c. Convert the binary code to hexadecimal. For example, 01 011 110 in binary becomes 5E in hexadecimal.
4.7.5.3.1. From the examples above we can tell that label 172 is displayed as 5E on the physical interface by most computers today.
The IRT-2120 and ICS-120A/220A is doing this conversion to display the more meaningful octal labels used in the ARINC-429 and
other ARINC documents referencing the octal labels on the physical interface.
4.7.5.4. Label-270 Word. ARINC-429 word label 270 contains the status information on the SDU and is completely described
in the ARINC-741 document.
4.7.5.4.1. The System Log example that shows label 270 and description is shown below.
• System Log example >> 08/04/2009 16:49:09G ARINC WriteWord dev=0, data=000000 lbl=270.
• Description: Indication of Label-270 (lbl=270) transmission (WriteWord) on TX-1 (dev=0) reporting service availability and
system status.
4.7.5.4.2. The bits below represent the information the IRT-2120 and ICS-120A/220A currently broadcasts to all equipment con-
nected to the enabled ARINC-429 interfaces. Bits not described below will be transmitted with a 0 value indicating no problems.
IRT-2110/2120 and ICS-120A/220A implements 270 word bits, they are shown below:
• Bits 10-9 (SDI) : 00 - Sole SDU, 01 - SDU#1, 10 - SDU#2
• Bit 11: DataLink not Available
• Bit 13: SATCOM Voice Unavailable
• Bit 14: SELCAL (incoming call)
• Bit 17: SATCOM not Logged-On
• Bit 18: Slave Bit (Master = 0).
NOTE
The remaining bits of the 270 word are set to 0.
4.7.5.5. Label-172 Word. The System Log example that shows label 172 and description is shown below.
• System Log example >> 08/04/2009 16:49:09G ARINC WriteWord dev=0, data=0004E3 lbl=172
• Description: Indication of Label-172 (lb=172) transmission (WriteWord) on TX-1 port (dev=0) containing System Address Label
307 (data=0004E3).
NOTE
The System Address Label will be 307 only when the IRT-2110/2120 and ICS-120A/220A is configured as Sole
SDU or SDU#1; refer to Paragraph 4.4.12.1 for more information regarding the IRDM Identity configuration
setting.
4.7.5.6. Label-377 Word. The data words below are displayed in hexadecimal format. For more information on the data bit
definitions, refer to ARINC 741 and ARINC 429 specifications. The System Log example that shows label 377 and description is
shown below.
• System Log example >> 08/04/2009 16:49:09G ARINC WriteWord dev=0, data=000104 lbl=377
• Bits 10-9 (SDI) : 00 - Sole SDU, 01 - SDU#1, 10 - SDU#2
• Bits 11-22 (Equipment ID code) : 041 refers to the Hexadecimal value of the equipment ID.
4-183
maintenance
NOTE
Other ARINC-429 words are used to follow a protocol or file transfer method. For transfers to/from a DMU refer
to ARINC-429 Part 3, and for MCDU transfers refer to ARINC-739A. These transfer protocols are outside the
normal troubleshooting and should not normally need troubleshooting unless there is an incompatibility problem.
If this is the case, please contact Rockwell Collins.
NOTE
On computer platforms with the problem, the firmware upgrade succeeds but the final message Programming:
100010040 – 100xxxxx OK, does not appear.
4.7.6.1. Workaround. After the XModem file transfer completes, the user must wait 1 minute before power-cycling the system.
Verification of the firmware upgrade by inspecting the System Monitor screen is recommended. At this point the Firmware Upgrade
is complete.
4-184
APPENDIX A
Equipment Characteristics
A-1
appendix A
Certification
FAA TSO Refer to Table A-2.
Environmental Refer to Table A-2 and to the environmental qualification forms provided in Table A-4.
Size Refer to Table A-4.
Weight Refer to Table A-4.
Power requirements Refer to Table A-4 (typical values).
Maintenance requirements On condition.
ELECTRICAL SPECIFICATIONS
Prime Power 12-36 VDC, 28 VDC NOMINAL
Power Consumption 28 Watts +/- 2% at 28 VDC
Surge: IRT-2110/2120 1.44 A [typ]1.168 A [surge <100 mSec]2.04 A[typ]1.636
ICS-120A/220A A[surge <100 mSec]
Recommended Circuit Breaker 5.0 Amps
MECHANICAL SPECIFICATIONS
Weight: IRT-2110 6.9 lb (3.1kg)
IRT-2120 7.4 lb (3.4kg)
Weight: ICS-120A-1 5.9 lb (2.7kg) MAX
ICS-220A-1 6.8 lb (3.1kg) MAX
ICS-120A 6.3 lb (2.9kg) MAX
ICS-220A 7.4 lb (3.4kg) MAX
ICS-120B 6.3 lb (2.9kg) MAX
ICS-220B 7.4 lb (3.4kg) MAX
ICS-120BF 6.6 lb (3.0kg) MAX
ICS-220BF 7.9 lb (3.6kg) MAX
ICS-220AF 7.9 lb (3.6kg) MAX
Length 15.97 in. (40.56 cm)
Height 7.75 in. (19.3 cm)
Width 2.33 in. (5.92 cm)
A-2
appendix A
MECHANICAL SPECIFICATIONS
Finish IRT-2110/2120 Chemical film per MIL-C-5541, class 3, Paint:
Sherwin-Williams Polane LG, Polyurethane Black
Finish ICS-120A/220A Chemical film per MIL-DTL-5541 class 3, Paint:
Sherwin-Williams Polane LG, Polyurethane Black. F63B21 or
equivalent Medium Texture
2-MCU TRAY
Weight 2.0 lbs (0.909 kg) (Approx.)
Length 14.92 in. (37.90 cm) (short tray)
Height 7.25 in. (18.42 cm)
Width 2.39 in. (6.07 cm)
FRONT PANEL CONNECTOR
Programming port USB type B connector
BACK PANEL CONNECTOR
Power, audio, and antenna connectors ARINC 600 Size 1
ENVIRONMENTAL SPECIFICATIONS
Temperature -20°C to +55°C (−4°F to +131°F)
Altitude 50,000 ft. (15,240 m)
Vibration DO-160E Category S
EMI/RFI DO-160E Category M
EXTERNAL CARD READER (ICM/CIM) SPECIFICATIONS
Weight 6.3 oz
Height 1.7 in. (34.06 mm)
Length 4.88 in. (123.83 mm)
Width 2.50 in. (63.50 mm)
Finish IRT-2110/2120 MIL-C-5541C3, Yellow
Finish ICS-120A/220A MIL-DTL-5541 Class 3, Yellow
A-3
appendix A
2. Weight 0.5lbs
3. Speed Rating 600 Knots @ 55,000 Ft
4. Finish Gloss white paint
A-4
APPENDIX B
Iridium ATS Voice
B-1
appendix B
B.1.2. Update AOC or ATS Directory File for ATS Voice Unit.
The instruction in this section will allow the user to modify the existing AOC or ATS directory .csv file with the appropriate priority.
1. Obtain the current AOC or ATS directory file use the instructions in Paragraph 4.2.1.1. Uploading and Downloading the Data
Files.
2. Open the .csv file using Microsoft Excel.
3. Locate the row that begins with ".pn= ….". Change the current part number to a new part number since this new directory is
for ATS Voice. This is only a comment for the actual part number on row #27 since this line begins with a period. The full part
number has three parts: <pn1>, <pn2>, and <pn3>, where <pn1> is the part number base, <pn2> is the part number revision,
and the optional <pn3> is the user revision associated with <pn1>. One recommendation is to roll part number revision <pn2>
by one. For example, change ".pn=710541-03" to ".pn=710541-04-01". See Figure B-1 for an example.
4. Locate the first row which does not begin with a period. This is the first row that contains the actual information in the AOC
or ATS file. In most cases, this is row #27. On this row, column A contains a value "3", column B contains a value "AOC" or
"ATC", column C contains the part number base, column D contains the part number revision, column E contains part number
user revision, and column F contains the format entry. Change this value to the same value performed in the previous step. In
this example, change the value in cell 27D from a value of "3" to "4". See Figure B-2 as an example.
5. Locate all rows below row #27 and their column A contains a value of "2". These rows contains the AOC or ATC entries with
current call priority set to 1 (Emergency). For these rows, the call priority is the value in column C. Change the call priority the
appropriate value using Table B-1 as a guide. The possible values can be entered are summarized in Table B-2.
6. Save the file with the new part number and keep the same format (comma delimited, .csv extension). When saving this file, if
prompted by MS Excel to keep the workbook in the same format, select "Yes". In this example, save the file as 710541-04-
01.csv.
7. Repeat the same editing procedure for the other directory (AOC or ATS directory).
8. Repeat steps 1 through 5 (except ATS).
9. Upload the new directory files (AOC and ATS) to the ICS-120A/220A or IRT-2110/2120, use the instructions in Paragraph
4.2.1.1. Uploading and Downloading the Data Files.
B-2
appendix B
B-3
appendix B
B-4
appendix B
5. AtG calling can be accomplished using the direct dial method, Last Number redial from the History page on the MCDU screen,
as well as lookup in the local ATS or AOC directories loaded into the system configuration. The local directories can be modified
as need from the MCDU console.
6. The dialing methods that may be used for ATS services are as follows:
• Direct Dial
• Direct Dial with User Priority Code
• Destination Short Code
• Destination Short Code with User Priority Code
• Aircraft ICAO ID Code – for ground to air calls only
Three attempts can be made to properly enter the User authentication information before the call is terminated.
B.1.6. Caller Priority.
The instruction in this section describes features of Caller Priority. Caller Priority procedures are as follows:
• Dynamic priority dialing for any call.
• Assign and maintain call priority for all active AtG and GtA calls for each aircraft.
• Maximum call priority is defined for each unique GtA user. No max priority for pilot AtG.
B-5
appendix B
• AtG calls can be preempted by the Cockpit Stations in any situation deemed necessary.
• Caller ID.
• Support for communicating calling party identification for all AtG and GtA calls.
NOTE
Bit 14 is the SELCAL bit for the chime. It follows the ARINC 741 commentary on the implementation and will
produce a chime on both single calls via channel #1 and #2 as well as handling simultaneous incoming calls.
Bit 20 is for all as an AND of all three (3) conditions.
Bit 21 is for the voice channels only implemented as a time-out of 2-minutes for signal level of '0' before declaring
a voice failure.
B-6
appendix B
If an “N/A” separator is not used in the middle of the routing path, Priority 1 – 3 inbound calls are routed in accordance with the
extensions listed in the path. However, Priority 4 calls from the ground will not be routed to any station. If a Priority 4 call is
attempted to the aircraft, after multiple rings, the ground caller will hear the Iridium message, “The subscriber you are trying to
reach is unavailable at this time …” before Iridium terminates the call attempt.
NOTE
If it is desired for Priority 4 inbound calls to be routed to the cockpit, the cockpit station(s) must be listed twice in
the Hunt Group path: once before the “N/A” separator and once after. See Example #2 below for an example of
this particular case.
The illustrations/samples given above are examples only, and are by no means the only ways to route inbound
calls. Each installation must be individually evaluated and configured so that incoming ATS Voice calls are routed
properly.
In Example #1, with the use of the “N/A” separator, Priority 1 – 3 inbound calls will be routed to Station 15. Priority 4 inbound calls
will be routed to Station 11, and then 12, see Figure B-3.
B-7
appendix B
Figure B-3. Example #1: Priority 4 Calls Ring just the Cabin and not the Cockpit
B-8
appendix B
In Example #2, with the use of the “N/A” separator, Priority 1 – 3 inbound calls will be routed to Station 15. Priority 4 inbound calls
will be routed to Station 15, and then 11, see Figure B-4.
B-9
appendix B
Figure B-4. Example #2: Priority 4 Calls Ring the Cockpit and then the Cabin
B-10
appendix B
In Example #3, Priority 1 – 3 inbound calls will be routed to Station 15, and then 16. However, with no “N/A” separator in the
middle of the Inbound Hunt Group routing path, Priority 4 calls from the ground will not be routed to any station. If a Priority 4 call
is attempted to the aircraft, after multiple rings, the ground caller will hear the Iridium message, “The subscriber you are trying to
reach is unavailable at this time …” before Iridium terminates the call attempt, see Figure B-5.
B-11
appendix B
Figure B-5. Example #3: Priority 4 Calls Do Not Ring the Aircraft Whatsoever
B-12
appendix B
B.1.11.1. ATS Voice Open Software issues (IRT/ICS ATS Voice Systems only). ATS Voice Open Software issues are as
follows:
B.1.11.1.1. ICS-48. Ensure Channel 1 (Ch1) and Ch2 status is READY
a. Place a priority 2 GTA call
b. Ch1 status will display GND CALL
NOTE
GTA Call should be coming on Ch1
NOTE
The Advisory text "INCOMING" will be displayed in the scratchpad area
NOTE
The Advisory text "INCOMING" will be removed from the scratchpad area as a result of pushing the <REJECT
LSK
NOTE
Ch1 status will continue to display GND CALL
The <MAKE CALL LSK push did not intitate the dialing
j. Ch1 status will display READY after timeout from the ground
B.1.11.1.1.1. Workaround. Push the <MAKE CALL LSK to place the call only when the Ch1 status displays READY
NOTE
The phone number displayed below the <MAKE CALL LSK will be dialed upon pushing the <MAKE CALL
LSK
B-13
appendix B
NOTE
Ch1 status will display CABIN USE
NOTE
The <PREEMPT and <QUEUE CALL LSK are displayed upon number entry in the scratchpad
NOTE
The cabin Ext. 11 is displayed below the <PREEMPT LSK
e. Ch1 status will transition from CABIN USE to DIALING, RINGING (for a short time) and back to CABIN USE
NOTE
The <END CALL LSK is displayed while Ch1 status shows DIALING and RINGING
The <PREEMPT LSK is displayed while Ch1 status shows CABIN USE
Unable to preempt a cabin call to the ground (initiated from Ext. 11), to place a cockpit call to the same cabin Ext.
11, unless Ext. 11 ATG call is terminated
NOTE
Ch1 status of ANSWERED and <END CALL LSK are displayed
NOTE
Ch1 status of READY and <MAKE CALL LSK should not be displayed before displaying CALL ENDED status
(sequence)
NOTE
Ch1 status of ANSWERED and <END CALL LSK are displayed
B-14
appendix B
NOTE
Cabin status of IDLE and <CBN CONF LSK are displayed
NOTE
Conference call status transitions from IDLE to RNG while the cabin is ringing
e. Ch1 status RINGING and <END CALL LSK are displayed while the cabin is ringing
NOTE
Should continue to display Ch1 status ANSWERED and <END CALL LSK while the cabin is ringing
NOTE
Ch1 status will display CABIN USE
NOTE
Ch1 status of READY is displayed
Should display Ch1 status of CALL ENDED before displaying status of READY
NOTE
Ch1 status will display CABIN USE
The <PREEMPT LSK is displayed
NOTE
The <PREEMPT and <QUEUE CALL LSK are displayed
B-15
appendix B
NOTE
The <QUEUE CALL LSK is not displayed
The <PREEMPT LSK is still displayed
Should not display <PREEMPT LSK upon clearing the scratchpad
NOTE
GTA Call should be coming on Ch1
NOTE
The Advisory text "INCOMING" will be displayed in the scratchpad area
NOTE
Ch1 status will display CABIN USE
NOTE
The <PREEMPT and <QUEUE CALL LSK are displayed
NOTE
Ch1 status changes to CALL IN QUEUE
The <QUEUE CALL LSK transitions to <END QUEUE LSK
The <PREEMPT LSK is not displayed [Should display upon pushing the <QUEUE CALL LSK]
B-16
appendix B
NOTE
Ch1 status transitions from CALL IN QUEUE to CABIN USE
NOTE
The cabin call will be preempted and the dialing of phone number entered in the scratchpad is initiated
B.1.13.2. READY, No active calls. Page shows voice 1 and voice 2 channels are available to place calls. No page transition is
displayed for selection of <HISTORY LSK, see Figure B-7.
B-17
appendix B
B.1.13.3. READY, <MAKE CALL, PRI, SCRATCHPAD ENTRY. Upon scratchpad entry, <MAKE CALL LSK is displayed
for voice 1 and voice 2 channels. With invalid scratchpad entry, selection of <MAKE CALL LSK displays INVALID ENTRY on
next page, see Figure B-8.
B-18
appendix B
B.1.13.4. READY, <MAKE CALL, PRI, INVALID ENTRY. INVALID ENTRY is displayed after selection of <MAKE CALL
from previous page, see Figure B-9.
B-19
appendix B
B.1.13.5. READY, <MAKE CALL, PRI, VALID ENTRY. With valid scratchpad entry, selection of priority via <HGH LSK
changes the priority from HGH to EMG, displayed on next page, see Figure B-10.
B-20
appendix B
After call priority set to HGH from previous page, selection of <MAKE CALL LSK for voice 1 channel causes the AES to initiate
call placement from the phone number in scratchpad and the selected priority. The MCDU page is transitioned to next page, see
Figure B-11.
B-21
appendix B
B.1.13.6. DIALING, <END CALL. <END CALL LSK, voice 1 channel status of DIALING are displayed along with the dialed
phone number and priority in color green, on line below <END CALL LSK, see Figure B-12.
B-22
appendix B
B.1.13.7. RINGING, <END CALL. <END CALL LSK, voice 1 channel status of RINGING are displayed along with the dialed
phone number and priority in color green, on line below <END CALL LSK. Upon selection of <END CALL, the MCDU page is
transitioned to next page, see Figure B-13.
B-23
appendix B
B.1.13.8. CALL ENDED, <CLR STATUS, READY. <CLR STATUS LSK, voice 1 channel status of CALL ENDED are dis-
played along with the dialed phone number and priority in color green, online below <CLR STATUS LSK. No MCDU page transition
is displayed on the next page for selection of <CLR STATUS LSK, see Figure B-14.
B-24
appendix B
B.1.13.9. SAT DIRECTORY, AOC DIR>. Two directory index entries are displayed, selection of AOC DIR> LSK transitions
the MCDU page to next page, see Figure B-15.
B-25
appendix B
B.1.13.10. SAT DIRECTORY, OPERATIONS. AOC directory entry is displayed to contain entry for <JOHN DOE along with
phone number and priority in "phone number: priority" format. No MCDU page transition is displayed on the next page for selection
of <RETURN LSK, see Figure B-16.
B-26
appendix B
OPERATIONS directory entry is displayed to contain entry for <BOEING along with phone number and priority in "phone number:
priority" format. Upon selection of <BOEING LSK, the MCDU page is transitioned to next page, see Figure B-17.
B-27
appendix B
B.1.13.11. READY, <MAKE CALL, PRI, VALID DIR NUMBER. <MAKE CALL is displayed along with valid scratchpad
entry from the DIRECTORY page. HGH> LSK displays the priority of the phone number selected from the DIRECTORY page.
Priority of DIRECTORY phone number of HGH is not changed, but can be changed by selection of HGH> LSK, see next page for
call placement, see Figure B-18.
B-28
appendix B
With valid entry in the scratchpad for phone number from the DIRECTORY page, selection of <MAKE CALL LSK for voice 2
channel causes the AES to initiate call placement from the phone number in scratchpad and the displayed priority. The MCDU page
is transitioned to next page, see Figure B-19.
B-29
appendix B
B.1.13.12. READY, DIALING, <END CALL. <END CALL LSK, voice 2 channel status of DIALING are displayed along with
the dialed phone number and priority in color green, on line below <END CALL LSK. See next page for the MCDU page with voice
2 channel status of RINGING. <END CALL LSK is not selected, see Figure B-20.
B-30
appendix B
B.1.13.13. READY, RINGING, <END CALL. <END CALL LSK, voice 2 channel status of RINGING are displayed along with
the dialed phone number and priority in color green, on line below <END CALL LSK, see Figure B-21.
B-31
appendix B
B.1.13.14. READY, ANSWERED, <END CALL. After the call is answered, <END CALL LSK, voice 2 channel status of
ANSWERED are displayed along with the dialed phone number and priority in color green, on line below <END CALL LSK, see
Figure B-22.
B-32
appendix B
B.1.13.15. READY, ANSWERED, <PREEMPT, <QUEUE CALL, CBN CONF>, SEND>, SCRATCHPAD ENTRY. When
voice 2 channel status is displayed as ANSWERED, scratchpad entry of 11 causes the AES to change <END CALL LSK to
<PREEMPT, and display <QUEUE CALL, CBN CONF>, SEND> LSK along with cabin call conference status of IDLE and label
DTMF. Selection of CBN CONF> LSK causes the AES to dial cabin extension and current MCDU page is transitioned to next page,
see Figure B-23.
B-33
appendix B
B.1.13.16. READY, ANSWERED, <END CALL, END CONF>, RNG. For voice 2 channel, END CONF> LSK and cabin
conference call status of Ringing (RNG) are displayed. See next page for selection of END CONF> LSK, see Figure B-24.
B-34
appendix B
B.1.13.17. READY, ANSWERED, <END CALL, END CONF>, RNG. For voice 2 channel, selection of END CONF> LSK
causes the AES to terminate cabin conference call attempt and MCDU page is transitioned back to when CBN CONF> was selected,
see Figure B-25.
B-35
appendix B
B.1.13.18. READY, ANSWERED, <PREEMPT, <QUEUE CALL, CBN CONF>, SEND>, SCRATCHPAD ENTRY. Se-
lection of END CONF> causes the AES to transition back to this MCDU page displaying voice 2 channel status as ANSWERED,
scratchpad entry of 11, <PREEMPT LSK, <QUEUE CALL, CBN CONF>, SEND> LSK along with cabin call conference status of
IDLE and label DTMF, see Figure B-26.
B-36
appendix B
B.1.13.19. READY, ANSWERED, <END CALL, END CONF>, RNG. For voice 2 channel, END CONF> LSK and cabin
conference call status of ringing (RNG) are displayed. See next page when cabin extension has answered, see Figure B-27.
B-37
appendix B
B.1.13.20. READY, ANSWERED, <END CALL, EST CONF>, END CONF>, ANS. When cabin extension has answered,
EST CONF> LSK, END CONF> LSK along with cabin conference call status of ANS are displayed. Selection of EST CONF>
LSK causes the AES to transition the current MCDU page to next page, see Figure B-28.
B-38
appendix B
Figure B-28. READY, ANSWERED, END CALL, EST CONF SAT-PHONE Page 1/2
B.1.13.21. READY, ANSWERED, <END CALL, END CONF>, EST. Upon selection of EST CONF> LSK in previous page,
END CONF> LSK along with cabin conference call status of Established (EST) are displayed, see Figure B-29.
B-39
appendix B
Figure B-29. READY, ANSWERED, END CALL, EST SAT-PHONE Page 1/2
B.1.13.22. READY, ANSWERED, <PREEMPT, <QUEUE CALL, END CONF>, SEND>, EST, SCRATCHPAD
ENTRY. Initiating scratch pad entry while the cabin conference call status is EST, causes the AES to display <PREEMPT LSK,
<QUEUE CALL LSK, and SEND> LSK along with label DTMF displayed on line above SEND> LSK, see Figure B-30.
B-40
appendix B
Figure B-30. READY, ANSWERED, END CONF, EST SAT-PHONE Page 1/2
B.1.13.23. READY, ANSWERED, <END CALL, END CONF>, ANS. Removing scratch pad entry while the cabin conference
call status is EST, causes the AES to remove <PREEMPT LSK, <QUEUE CALL LSK, and SEND> LSK along with label DTMF.
Selection of <END CALL LSK transitions the current MCDU page to next page, see Figure B-31.
B-41
appendix B
Figure B-31. READY, ANSWERED, END CALL, END CONF, ANS SAT-PHONE Page 1/2
B.1.13.24. READY, CALL ENDED, <CLR STATUS. <CLR STATUS LSK, voice 2 channel status of CALL ENDED are
displayed along with the dialed phone number and priority in color green, on line below <CLR STATUS LSK. No MCDU page
transition is displayed on the next page, see Figure B-32.
B-42
appendix B
Figure B-32. READY, CALL ENDED, CLR STATUS SAT-PHONE Page 1/2
B.1.13.25. CABIN CALL. Voice 1 and voice 2 channel statuses of CABIN CALL are displayed due to both channel being used
by the cabin users, see Figure B-33.
B-43
appendix B
B.1.13.26. CABIN CALL, <PREEMPT, <QUEUE CALL, SCRATCHPAD ENTRY. Upon initial scratchpad entry, the
previous page transitions to this page displaying options for flight crew for <PREEMPT LSK, <QUEUE CALL LSK, HGH> for
voice 1 and voice 2 channels, see Figure B-34.
B-44
appendix B
Figure B-34. CABIN CALL, PREEMPT, QUEUE CALL SAT-PHONE Page 1/2
B.1.13.27. CABIN CALL, <PREEMPT, <QUEUE CALL, PRI, SCRATCHPAD ENTRY. Upon complete phone number
scratchpad entry, selection of <PREEMPT LSK, causes the AES to preempt the voice 1 channel used by the cabin user, initiate
dialing of phone number from scratchpad with selected priority and transition to next page, see Figure B-35.
B-45
appendix B
B.1.13.28. DIALING, <END CALL, CABIN CALL. <END CALL LSK, voice 1 channel status of DIALING are displayed along
with the dialed phone number and priority in color green, on line below <END CALL LSK. Voice 2 channel status of CABIN CALL
is displayed as in previous page. No selection is made to transition to next page, see Figure B-36.
B-46
appendix B
Figure B-36. DIALING, END CALL, CABIN CALL SAT-PHONE Page 1/2
B.1.13.29. CABIN CALL, <PREEMPT, <QUEUE CALL, PRI, SCRATCHPAD ENTRY. Upon complete phone number
scratchpad entry, selection of <QUEUE CALL LSK causes the AES to place the phone number from scratchpad with selected
priority for voice 1 channel in queue and transition to next page, see Figure B-37.
B-47
appendix B
Figure B-37. CABIN CALL, QUEUE CALL, PRI SAT-PHONE Page 1/2
B.1.13.30. CALL IN QUEUE, <PREEMPT, <END QUEUE, CABIN CALL. This page is displaying a number placed in queue
for voice 1 channel. <PREEMPT LSK and <END QUEUE LSK options are displayed for the flight crew to either preempt cabin
user or remove the phone number from the queue respectively. The phone number along with priority in queue are displayed on line
below <END QUEUE LSK, see Figure B-38.
B-48
appendix B
Figure B-38. CALL IN QUEUE, PREEMPT, END QUEUE, CABIN CALL SAT-PHONE Page 1/2
B.1.13.31. DIALING, <END CALL, CABIN CALL. When the voice 1 channel is available, the AES initiates dialing of the
phone number from the queue, thereby emptying the queue. The option to end call is displayed with <END CALL LSK along with
voice 1 channel status of DIALING. No selection is made to transition to next page, see Figure B-39.
B-49
appendix B
Figure B-39. DIALING, END CALL, CABIN CALL SAT-PHONE Page 1/2
B.1.13.32. CALL IN QUEUE, <PREEMPT, <END QUEUE, <QUEUE CALL, PRI, SCRATCHPAD ENTRY. Selection of
Directory phone number causes the AES to place it in scratchpad and display options for flight crew for <PREEMPT LSK, <QUEUE
CALL LSK, HGH> for voice 1 and voice2 channels. Voice 1 channel status shows CALL IN QUEUE with the queued phone number
displayed on line below <END QUEUE LSK. Selection of <QUEUE CALL LSK for voice 2 channel, causes the AES to place the
phone number from scratchpad with selected priority in queue and transition to next page, see Figure B-40.
B-50
appendix B
Figure B-40. CALL IN QUEUE, PREEMPT, END QUEUE, QUEUE CALL SAT-PHONE Page 1/2
B.1.13.33. CALL IN QUEUE, <PREEMPT, <END QUEUE. This page is displaying phone number placed in queue for voice
1 and voice 2 channels. <PREEMPT LSK and <END QUEUE LSK options are displayed for the flight crew to either preempt cabin
user or remove the phone number from the queue respectively. The phone number along with priority in queue are displayed on line
below <END QUEUE LSK for voice 1 and voice 2 channels, see Figure B-41.
B-51
appendix B
Figure B-41. CALL IN QUEUE, PREEMPT, END QUEUE, SAT-PHONE Page 1/2
B.1.13.34. CALL IN QUEUE, <PREEMPT, <QUEUE CALL, PRI, SCRATCHPAD ENTRY. To replace existing phone
number in queue for voice 1 channel, scratchpad entry is made. Selection of <QUEUE CALL LSK causes the AES to remove the
existing phone number in queue and place the phone number from scratchpad with selected priority for voice 1 channel in queue
and transition to next page, see Figure B-42.
B-52
appendix B
Figure B-42. CALL IN QUEUE, PREEMPT, QUEUE CALL SAT-PHONE Page 1/2
B.1.13.35. CALL IN QUEUE, <PREEMPT, <END QUEUE. This page is displaying updated phone number placed in queue
for voice 1 channel while keeping the existing phone number in queue for voice 2 channel. <PREEMPT LSK and <END QUEUE
LSK options are displayed for the flight crew to either preempt cabin user or remove the phone number from the queue respectively.
The phone number along with priority in queue are displayed on line below <END QUEUE LSK for voice 1 and voice 2 channels.
See next page when GTA call is initiated, see Figure B-43.
B-53
appendix B
Figure B-43. CALL IN QUEUE, PREEMPT, END QUEUE, SAT-PHONE Page 1/2
B.1.13.36. PREEMPTED, CALL IN QUEUE, <PREEMPT, <END QUEUE. Voice 1 channel resources are preempted when
a GTA call is initiated and in progress. Voice 1 channel status of PREEMPTED is displayed. This page transitions to next page
when voice 1 channel status is GND CALL, see Figure B-44.
B-54
appendix B
Figure B-44. PREEMPTED, CALL IN QUEUE, PREEMPT, END QUEUE SAT-PHONE Page 1/2
B.1.13.37. GND CALL, <ANSWER, <REJECT, CALL IN QUEUE, <PREEMPT, <END QUEUE. Voice 1 channel status
changes to GND CALL and <ANSWER LSK and <REJECT LSK are displayed for voice 1 channel and INCOMING CALL is
displayed on line below DIRECTORY> LSK. Selection of <REJECT LSK transitions the page to next page, see Figure B-45.
B-55
appendix B
B.1.13.38. NOT READY, <END QUEUE, CALL IN QUEUE, <PREEMPT, <END QUEUE. Voice 1 channel status of NOT
READY is displayed after selection of <REJECT LSK on previous page. See next page when voice 1 channel status changes to
READY, see Figure B-46.
B-56
appendix B
B.1.13.39. READY, <END QUEUE, CALL IN QUEUE, <PREEMPT, <END QUEUE. Voice 1 channel status of READY is
displayed after rejection call is cleared. When voice 1 channel status is READY, AES initiates dialing of phone number in queue.
The current MCDU page is transitioned to next page, see Figure B-47.
B-57
appendix B
B.1.13.40. DIALING, <END CALL, CALL IN QUEUE, <PREEMPT, <END QUEUE. Voice 1 channel status of DIALING
is displayed along with <END CALL LSK. For voice channel 2, <PREEMPT LSK and <END QUEUE LSK are unchanged. See
next page when ATG call is answered, see Figure B-48.
B-58
appendix B
B.1.13.41. ANSWERED, <END CALL, CALL IN QUEUE, <PREEMPT, <END QUEUE. When ATG call is answered, voice
1 channel status of ANSWERED and <END CALL LSK are displayed along with phone number with priority are displayed on line
<END CALL LSK. See next page when a stratchpad entry is initiated, see Figure B-49.
B-59
appendix B
B.1.13.42. ANSWERED, <END CALL, <QUEUE CALL, DIALING, <CBN CONF, <SEND, STRATCHPAD EN-
TRY. When voice 1 channel status is displayed as ANSWERED, scratchpad entry of 11 causes the AES to change <END CALL
LSK to <PRERMPT, and display <QUEUE CALL, CBN CONF>, SEND> LSK along with cabin call conference status of IDLE
and label DTMF. When voice 2 channel status is ANSWERED, the current MCDU page is transitioned to next page, see Figure
B-50.
B-60
appendix B
Figure B-50. ANSWERED, END CALL, QUEUE CALL, DIALING, CBN CONF SAT-PHONE Page 1/2
B.1.13.43. ANSWER, <END CALL. Voice 1 and voice 2 channel statuses of ANSWERED is displayed, see Figure B-51.
B-61
appendix B
B.1.13.44. GND CALL, <ANSWER, <REJECT, READY. Voice 1 channel status of GND CALL and <ANSWER LSK and
<REJECT LSK are displayed. Voice 2 channel status is displayed as READY. Selection of <ANSWER LSK transitions the page to
next page, see Figure B-52.
B-62
appendix B
B.1.13.45. GND CALL, <END CALL, READY. When GTA call is answered, voice 1 channel status of ANSWERED and <END
CALL LSK are displayed along with phone number with priority are displayed on line below <END CALL LSK. Selection of <END
CALL LSK transitions to next page, see Figure B-53.
B-63
appendix B
B.1.13.46. CALL ENDED, <CLR STATUS, READY. Voice 1 channel status of CALL ENDED, <CLR STATUS LSK along
with phone number and priority are displayed. No MCDU page transition is displayed on the next page for selection of <CLR
STATUS LSK, see Figure B-54.
B-64
appendix B
B-65/(B-66 Blank)
523-0818093
© 2018, Rockwell Collins.
All Rights Reserved, Printed in USA