FCC ID: 2A6TS-AVIATOR700S Aircraft earth station (AES)

 

AVIATOR 700S Installation Manual Cobham Public AVIATOR 700S System Installation Manual Document number: 98-158751-C Release date: 10 November 2023 Disclaimer Information in this document is subject to change without notice. The information, drawings and wiring diagrams contained in this manual are intended as a reference for engineering planning only. The drawings and wiring diagrams contained herein do not represent any specific Supplemental Type Certificate (STC). It is the installer's responsibility to compose installation drawings specific to the aircraft. This manual and the drawings and wiring diagrams contained herein may not be used as a substitute for an STC package. Cobham Aerospace Communications is not responsible for the content or accuracy of any translations or reproductions, in whole or in part, of this manual from any other source. In the event of any discrepancies, the English version shall be the governing text. Manufacturer address Cobham Aerospace Communications - Fullerton, 577 Burning Tree Road, Fullerton, CA 92833 USA Copyright 2023 Cobham Aerospace Communications. All rights reserved. Trademark Acknowledgements Inmarsat is a registered trademark of the International Maritime Satellite Organization (IMSO) and is licensed by IMSO to Inmarsat Limited and Inmarsat Ventures plc. Inmarsats product names are either trademarks or registered trademarks of Inmarsat. Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Other product and company names mentioned in this manual may be trademarks or trade names of their respective owners. Company web site https://cobhamaerospacecommunications.com ii 98-158751-C Record of revisions Rev. A B C Description Original document Update following 99-158751-draft-A1_Installation Manual_Peer-review_FS_PF_MdP.docx Release Date Initial 6 September 2022 LLE Update MCHPA tray connector reference:

Table 2-9: change MCHPA tray connector reference 27 October 2022 LLE 10 November 2023 LLE Update according to internal comments:

Change Thrane & Thrane A/S by Cobham Aerospace Communications Add document Approval and Validation Add precision in chapter 2 Resize figure 2-1 Update figure 2-2 Update drawings with latest version Update Figure 4-1 and Figure 4-2 Add precision in chapter 4 and update pinning tables, to be in-line with Figure 4-2 Wording issues in chapter 5 6.2: delete RF cable DC resistance, precise that RF losses are measured on all coaxial cables 6.3/6.5: put a reference for Aviator 700S User Manual 7.1.1: update Technical support information Glossary: add ACR, ADIRU, AMU, ATSU, LGCIU, LGERS, RMP and TCP Delete table in 4.4.4 and refer to ARINC standard for RF cable loss Replace DLNA-5013 by DLNA type F in all the document 4.2.3: add non-controlled temperature A.3: Add controlled temperature location Update HGA installation manual reference Update website address on last page DOCUMENT APPROVAL AND VALIDATION Name Signature Date Edited Ludovic LEGEAY Approved Engineering Manager Rabah BOUDA Approved System Engineering Approved Program Management Bo DYSSEGARD Kim HARDER Approved Engineering Dave HOLLOWAY Approved QA Nathaniel HAYES iv 98-158751-C 11/10/2023Nov 15 202316/11/2023Nov 21 202311/21/2311/21/23 Table of contents Chapter 1 About this manual Purpose ...................................................................................................1-1 1.1 1.2 Organization ..........................................................................................1-1 1.3 Precautions: Warnings, Cautions and Notes ......................................1-2 Chapter 2 Introduction Chapter 3 2.1 General description ...............................................................................2-1 2.1.1 The AVIATOR 700S System ...............................................................2-1 2.1.2 Maintenance interfaces (ACD) .............................................................2-7 2.1.3 Power supply input ...............................................................................2-7 2.1.4 Interface to the SCM .............................................................................2-7 2.1.5 Interface to the DLNA ..........................................................................2-7 2.1.6 Electrical interfaces - overview ............................................................2-8 2.2 Part numbers .........................................................................................2-9 Equipment drawings SDU-5045 Compact Satellite Data Unit ..............................................3-2 3.1 3.2 SCM-5055 SDU Configuration Module ..............................................3-4 3.3 HPA-5015 Multi-Carrier High Power Amplifier ...............................3-6 3.4 DLNA-5013 ............................................................................................3-8 3.5 CSDU/MCHPA tray .............................................................................3-9 3.6 CSDU tray connector ..........................................................................3-10 3.7 MCHPA tray connector .....................................................................3-11 Chapter 4 Installation 4.1 General installation information .........................................................4-1 4.1.1 Overview ...............................................................................................4-1 4.1.2 System components ..............................................................................4-1 4.2 Mounting considerations ......................................................................4-3 4.2.1 Overview ...............................................................................................4-3 4.2.2 SDU-5045 CSDU .................................................................................4-3 4.2.3 SCM-5055 SCM ...................................................................................4-4 4.2.4 HPA-5015 MCHPA ..............................................................................4-5 98-158751-C Chapter :

-v 4.3 Electrical installation and wiring .........................................................4-6 4.3.1 Wiring symbols .....................................................................................4-6 4.3.2 Wiring overview .................................................................................4-7 4.3.3 To wire the CSDU with AC input .........................................................4-8 4.3.4 To wire the MCHPA with AC input ...................................................4-10 4.3.5 To wire the SCM .................................................................................4-12 4.3.6 To wire the MCHPA ...........................................................................4-12 4.3.7 To wire the MCDU 1, 2 and 3 .............................................................4-13 4.3.8 To wire the CMU 1 and 2 ...................................................................4-13 4.3.9 To wire aircraft AES ID ......................................................................4-14 4.3.10 To wire cockpit audio 1 and 2 .............................................................4-14 4.3.11 To wire IRS/GNSS ..............................................................................4-15 4.3.12 To wire antenna BITE .........................................................................4-15 4.3.13 To wire EICAS/FWS ..........................................................................4-16 4.3.14 To wire discrete inputs and outputs ....................................................4-16 4.3.15 To wire airborne data loader ...............................................................4-17 4.3.16 To wire Antenna multi control ............................................................4-18 4.3.17 To wire fault/health reporting (CFDS) ................................................4-18 4.3.18 To wire Ethernet 1 (AISD#1 or EFB 1) ..............................................4-18 4.3.19 To wire Ethernet 11 (AISD#2 or EFB2) .............................................4-19 4.3.20 To wire Ethernet 3 (ADL in ACD) .....................................................4-19 4.3.21 To wire Ethernet 2 (PIESD#1 or Cabin1) ...........................................4-20 4.3.22 To wire Ethernet 12 (PIESD#2 or Cabin2) .........................................4-20 4.3.23 To wire Ethernet 4 (ACD#1) ...............................................................4-21 4.3.24 To wire Ethernet 5 (ACD#2) ...............................................................4-21 4.3.25 To wire the Maintenance interfaces ....................................................4-22 4.3.26 CSDU ARINC 600 connector block ...................................................4-25 4.3.27 MCHPA ARINC 600 connector block ...............................................4-33 4.4 Recommended cables ..........................................................................4-37 4.4.1 Introduction .........................................................................................4-37 4.4.2 Allowed cable lengths for power cables .............................................4-37 4.4.3 Recommended power cables ...............................................................4-38 4.4.4 Recommended RF cables ....................................................................4-38 4.4.5 Recommended cables for ARINC 429 ................................................4-38 4.4.6 Recommended cables for Ethernet ......................................................4-38 4.4.7 Recommended cables for discrete signals ...........................................4-39 4.4.8 Recommended cable between the SCM and the CSDU .....................4-39 4.5 Verifying the installation ....................................................................4-39 4.6 Activation of airtime services .............................................................4-39 4.6.1 ID numbers for the AVIATOR 700S system ......................................4-39

-vi Chapter :

98-158751-C Chapter 5 Setup of the system 5.1 Software upload ....................................................................................5-1 5.1.1 Overview ...............................................................................................5-1 5.1.2 Uploading software ...............................................................................5-2 5.2 SATCOM system ready for use ...........................................................5-2 Chapter 6 Verification 6.1 Basic check flow ....................................................................................6-1 6.1.1 Check procedures ..................................................................................6-1 Pre-Installation Check ..........................................................................6-2 6.2 6.3 Functional Test, on Ground .................................................................6-3 6.3.1 Before you start .....................................................................................6-3 6.3.2 Check list for functional test on ground ................................................6-3 Interference Test ...................................................................................6-4 6.4 6.4.1 Introduction ...........................................................................................6-4 6.4.2 Test procedure .......................................................................................6-4 6.5 Functional test, airborne ......................................................................6-5 6.5.1 Before you start .....................................................................................6-5 6.5.2 Check list for functional test, airborne ..................................................6-5 Chapter 7 Maintenance and troubleshooting 7.1 Continued Airworthiness .....................................................................7-1 7.1.1 General ..................................................................................................7-1 7.1.2 Maintenance instructions ......................................................................7-2 7.2 Helpdesk .................................................................................................7-4 7.2.1 System support ......................................................................................7-4 7.2.2 Security log and system log files ..........................................................7-4 7.3 Software update ....................................................................................7-5 7.4 To exchange an LRU ............................................................................7-5 7.4.1 Time required ........................................................................................7-5 7.4.2 Tools required .......................................................................................7-5 7.4.3 Removal and re-installation of the CSDU (SDU-5045) .......................7-5 7.4.4 Removal and re-installation of the SCM (SCM-5055) .........................7-6 7.4.5 Removal and re-installation of the MCHPA (HPA-5015) ....................7-6 7.5 Troubleshooting ....................................................................................7-7 7.5.1 Status signalling ....................................................................................7-7 7.5.2 Status signalling with LEDs .................................................................7-8 7.5.3 Initial troubleshooting ...........................................................................7-9 7.6 Returning units for repair ..................................................................7-10 7.6.1 Repackaging requirements ..................................................................7-10 98-158751-C Chapter :

-vii 7.7 Disposal of electrical and electronic equipment ...............................7-11 Appendix A Equipment specifications A.1 Introduction ..........................................................................................A-1 A.2 SDU-5045 Compact Satellite Data Unit .............................................A-2 A.3 SCM-5055 Configuration Module ......................................................A-4 A.4 HPA-5015 Multi-Carrier High Power Amplifier ..............................A-5 Appendix B System messages B.1 BITE error codes ..................................................................................B-1 B.1.1 List of BITE error codes ......................................................................B-1 Appendix C DO-160G specifications C.1 General DO-160 information ..............................................................C-1 C.1.1 Certifying agency .................................................................................C-1 C.1.2 Environmental Qualification Forms .....................................................C-1 C.2 Compact Satellite Data Unit (CSDU) .................................................C-2 C.3 Configuration Module (SCM) .............................................................C-5 C.4 Multi-Carrier High Power Amplifier (MCHPA) ..............................C-8 Appendix D References D.1 Applicable standards ............................................................................D-1 D.2 Other references ...................................................................................D-1 Glossary Index

....................................................................................................................Glossary-1

.........................................................................................................................Index-1

-viii Chapter :

98-158751-C About this manual Chapter 1 1 1.1 Purpose The purpose of this manual is to provide information for installation of the AVIATOR 700S system. Important The information, drawings and wiring diagrams contained in this manual are intended as a reference for engineering planning only. The drawings and wiring diagrams contained herein do not represent any specific Supplemental Type Certificate (STC). It is the installer's responsibility to compose installation drawings specific to the aircraft. This manual and the drawings and wiring diagrams contained herein may not be used as a substitute for an STC package. 1.2 Organization The chapters of this Installation Manual have the following information:

Introduction An overview of the AVIATOR 700S system and services. Equipment drawings Outline drawings of the units, trays and connectors of the AVIATOR 700S system. Installation Wiring drawings, installation instructions and wiring requirements. Configuration A description of how to set up the AVIATOR 700S system. Verification with check procedures. An overview of the recommended check procedures and checklists. Service and maintenance Service information, initial troubleshooting Appendices Equipment specifications, DO-160 Forms, list of error messages (BITE) and a list of applicable standards. 98-158751-C 1-1 Precautions: Warnings, Cautions and Notes 1.3 Precautions: Warnings, Cautions and Notes Text marked with Warning, Caution, Note or Important show the following type of data:

Warning: A Warning is an operation or maintenance procedure that, if not obeyed, can cause injury or death, or jeopardize the flight safety on the aircraft. Caution: A Caution is an operation or maintenance procedure that, if not obeyed, can cause damage to the equipment. Note: A Note gives information to help the reader. Important: A text marked Important gives information that is important to the user, e.g. to make the system work properly. This text does not concern damage on equipment, flight safety nor personal safety. General precautions All personnel who operate equipment or do maintenance as specified in this manual must know and follow the safety precautions. The warnings and cautions that follow apply to all parts of this manual. WARNING! Before using any material, refer to the manufacturers material safety data sheets for safety information. Some materials can be dangerous. WARNING! Make sure that system power is off before you disconnect the LRU mating connectors. CAUTION! Do not use materials that are not equivalent to materials specified by Cobham. Materials that are not equivalent can cause damage to the equipment and can void the warranty. Weights and measurements Weights and measurements are in metric values (SI) with imperial metrics in parentheses. 1-2 Chapter 1: About this manual 98-158751-C Chapter 2 2 Introduction This chapter has the following sections:

General description Part numbers 2.1 General description This installation manual provides the general installation instructions and setup of the AVIATOR 700S System. Please see separate Installation Manual [8] for the HGA antenna and DLNA which forms part of the AVIATOR 700S System. The installer must derive specific installation details for each different aircraft type, using this manual as a guideline, while adhering to standard aircraft practices. Refer to [1], or its equivalent. CAUTION! The material in this manual is subject to change. Before you start with the installation you must verify that the complete and up-to-date publication is used. 2.1.1 The AVIATOR 700S System System overview The AVIATOR 700S System is an Inmarsat aeronautical SATCOM system, which provides Inmarsat SwiftBroadband services and safety services (Class 6), using a standard ARINC 781/741 compliant High Gain Antenna (HGA). It delivers secure ACARS services over a robust IP data link together with dual cockpit voice channels. The AVIATOR 700S System is a dual-channel system for cockpit and cabin use and complies with ARINC Characteristic 781 Mark 3 Aviation Satellite Communication Systems. The system provides services in the L-band (1525 to 1559 MHz for the receive channel and 1626.5 to 1660.5 MHz for the transmit channel). The AVIATOR 700S System provides the following classes of communication services:

Air Traffic Service (ATS) Airline Operational Control (AOC) Aeronautical Administrative Communications (AAC) Aeronautical Passenger Communication (APC) The services include cockpit voice with two voice channels, IP data (Internet), ACARS over IP and Electronic Flight Bag (EFB) services for direct satellite communication in the Inmarsat BGAN Satellite Network, using the Inmarsat 4th and 6th generation satellites. The following figure shows the AVIATOR 700S System. 98-158751-C 2-1 General description Figure 2-1: AVIATOR 700S System, dual channel (Class 6) The AVIATOR 700S System consists of:

SDU-5045 Compact Satellite Data Unit (CSDU) SCM-5055 Compact SDU Configuration Module (SCM) HPA-5015 Multi-Carrier High Power Amplifier (MCHPA) Diplexer/Low Noise Amplifier (DLNA) Type F ARINC 781/741 compliant with High Gain Antenna (HGA) The CSDU is the master of the AVIATOR 700S System and controls the associated units in the system. The SCM is powered by the CSDU. The AVIATOR 700S System has the following features:

Complete aircraft network segregation with priority for the Aircraft Control Domain

(ACD) over the Aircraft Information Services Domain (AISD) and also the Passenger Information Entertainment Services Domain (PIESD). ARINC 781-7 compliant network security Approved FANS 1/A services, including CPDLC, ADS-C and ACARS. Enhanced ACARS (with IPSEC VPN) and Secure Cockpit Voice. Media for aircraft monitoring systems and continuous positioning reporting. Background IP data for AISD (e.g. EFB) applications. Two cockpit voice over 4-wire connections, with three MCDU ARINC 429 interfaces for SATCOM and voice management Two CMU/AFIS ARINC 429 interfaces for ACARS. Cabin IP data up to 432 kbps and higher data rate streaming HDR on the dedicated 2nd channel. 2-2 Chapter 2: Introduction 98-158751-C Compact Satellite Data Unit (CSDU) General description The AVIATOR 700S Compact Satellite Data Unit (CSDU) is a 2 MCU LRU with an ARINC 600 connector. It is a highly secure system with complete aircraft network segregation for the Aircraft Control Domain (ACD) over the Aircraft Information Service Domain (AISD) and also Passenger Information and Entertainment Services Domain

(PIESD). The aircraft network segregation between ACD and AISD ensures highest data security and meets all data communications specifications of ARINC 781-7, Attachment 8 [3] requirements. The system also meets requirements for Future Air Navigation System

(FANS) 1/A operations. PIESD interfaces and services are physically segregated from the other Cockpit interfaces through a dedicated radio module. The domain specific interface groups and the external interfaces of the CSDU are listed in the following table. Domain Interface Group Description ACD Cockpit User Interfaces ACD Internal SATCOM Interfaces ACD Aircraft Interfaces ACD Maintenance Interfaces Interfaces to avionics equipment used by the flight crew Interfaces between units in the SATCOM system Interfaces to Avionics equipment used by the SATCOM system Interfaces intended for maintenance staff ACD ACD AISD System Configuration inputs Discrete configuration pins Power Supply inputs Power supply inputs Cockpit User Interfaces for EFB services Interfaces dedicated for EFB devices PIESD Passenger Inetrfaces Interfaces for Passengers (Voice +

data) Table 2-1: Domain specific interface groups The following table lists the external interfaces of the CSDU, grouped after system functions. System function Flight Deck Cockpit interfaces Interfaces 3x ARINC 429 inputs, for MCDU/WSC/RMP/TCP 1x ARINC 429 output, for MCDU/WSC/RMP/TCP 1x ARINC 429 output, for FWC/FWS/EICAS Table 2-2: System function, cockpit interfaces 98-158751-C Chapter 2: Introduction 2-3 General description System function Cockpit Voice Cockpit interfaces Interfaces 2x 4-Wire DO-214A, for Cockpit Audio for AMS 1x Discrete input ARINC 781, for Mic-on for/PTT for ACP 1x Discrete input ARINC 781, for Call Place/End for ACP 1x Discrete input ARINC 781, for Cockpit Voice Go Ahead Chime reset for ACP 1x Discrete output, for Call Light for ACP 2x Discrete relay contacts ARINC-781, for Chime signal for ACP Cockpit Data ACARS 1x Ethernet AISD#1, for EFB 1x Ethernet Priority IP ACD#1 (provisioned) 1x Ethernet AISD#2 Spare 1x Ethernet ACD#2 Spare 1x Discrete output, hardware provisioned for ACARS Service Available 2x ARINC 429 Input for 2x CMU/ATSU/ACR 1x ARINC 429 Output for CMUs/ATSU/ACR Table 2-2: System function, cockpit interfaces (Continued) System function Inmarsat Radio Configuration Product interfaces Interfaces 2x HS ARINC 429 input for IRS/GNSS 1x ARINC 429 input for GNSS 1x Discrete input, ARINC 781, for Tx Mute 1x Modem control + DC 210 kHz Modem Control 1x ARINC 429 output for Multi-Control 1x ARINC 429 input for Antenna BITE 1x Discrete output, ARINC 781, for LNA On/Off 1x Discrete input, ARINC 781, for LNA BITE 1x Coaxial cable from DLNA 1x RF TX coxial cable for MCHPA 1x ARINC 429 input for AES ID 1x Discrete input, ARINC 781, for SDU Number 1x Discrete input, ARINC 781, for SCM Fitted 1x Discrete input, ARINC 781, for Program Pin Parity 1x Discrete output, ARINC 781, for 0V Common Table 2-3: System functions, product 2-4 Chapter 2: Introduction 98-158751-C General description System function BITE Maintenance interfaces Interfaces 1x ARINC 429 output for CFDS 1x ARINC 429 input for CFDS 1x Discrete ARINC 781 output, hardware provisioned for System Fail Data Loading 1x Ethernet for Data Loader A615A 1x Discrete input ARINC 781 for Data Loader Link A 1x ARINC 429 output for Data Loader A615 1x ARINC 429 input for Data Loader A615 Support 1x USB for Local Maintenance 1x Ethernet for Shop Maintenance System functions Environment Table 2-4: System functions, interfaces Aircraft interfaces Interfaces 1x Power AC input 115 VAC 360 to 800 Hz 1x Discrete input, for External Reset 1x Discrete input, ARINC 781, for WoW 1x Discrete input for Dual System Disable 1x Discrete I/O output for Dual System Select I/O 1x Discrete output, hardware provisioned for Fallback SDU Reset 1x Discrete output, hardware provisioned for Slave Tx Mute 1x ARINC 429 output, hardware provisioned for Crosstalk 1x ARINC 429 input, hardware provisioned for Crosstalk 1x ARINC 429 input, hardware provisioned spare 1x ARINC 429 output, hardware provisioned spare 4x Discrete input, ARINC 781, hardware provisioned spares 2x Discrete output, ARINC 781, hardware provisioned spares Table 2-5: System functions, aircraft Passenger Interface Passenger Voice 1x Ethernet for audio calls and data Table 2-6: Passenger interface 98-158751-C Chapter 2: Introduction 2-5 General description SDU Configuration Module (SCM) The SCM contains non-volatile memory for storing the Secure Owner Requirement Table

(ORT) and the User ORT, which hold the system settings. The SCM contains a write-

protected area for storing installation data (system configuration, RF cable losses, antenna system etc.) that are only updated during installation, and a user non-write-protected area for storing a phone book and the customer-specific configuration parameters. The SCM is an external module for the CSDU, making it easier to replace the CSDU while retaining all system and user settings in the SCM. If the CSDU must be replaced, the SCM remains installed in the aircraft. When the replacement CSDU is installed and connected to the SCM the system user settings are available again. The SCM, contains four Inmarsat BGAN USIM cards and one security SmartCard. In the AVIATOR 700S System system, two USIM cards are used to access the Inmarsat SwiftBroadband services and the remaining two USIM cards are reserved for future use. The Security SmartCard contains integrity/ciphering keys and authentication algorithms and is used by the Aircraft ACARS Gateway (AAGW). The SCM is delivered with all five cards installed and these cannot be replaced in the field. Multi-Carrier High Power Amplifier (MCHPA) The CSDU interfaces directly to a MCHPA. The Multi-Carrier High Power Amplifier is defined in Attachment 7 of ARINC 781-8 as a Line Replaceable Unit (LRU) that amplifies the RF transmit signal to the correct high power levels required by a compact aeronautical SATCOM system MCHPA is connected to the CSDU via a RF coaxial interface, over which it receives its RF input signal, a local oscillator reference signal and control signals. It is also connected to the DLNA via a second RF coaxial interface, over which it transmits the RF output signal. The physical interface for the RF input and output signals and for the 115 V AC power supply to the HPA 5015 is an ARINC 600 connector. Operation with an MCDU and headset You can operate the AVIATOR 700S system via the following user interfaces:

Headset and MCDU connected to the CSDU to make and answer calls MCDU to display system messages (Information and BITE codes) Headset connected to the audio control panel to make and answer calls Up to 3 MCDUs can be connected. System status and BITE messages of the AVIATOR 700S system can be displayed in the MCDU display. Other user interfaces The AVIATOR 700S system has a dedicated AISD Ethernet interface for EFB or other cockpit application requiring IP data communication services. It has also a dedicated PIESD Ethernet interface for voice and data communications for passengers. 2-6 Chapter 2: Introduction 98-158751-C General description Configuration files for the AVIATOR 700S system The configuration files (Secure ORT and User ORT) for the AVIATOR 700S system are uploaded to the CSDU with an ARINC 615A (Ethernet) or ARINC 615-3 (ARINC 429) compliant data loader. Refer to the ORT Tool User Guide [9]. There are two configuration files:

Secure ORT with all necessary system settings for the correct functioning of the system User ORT with phone book and other non-critical user-specific data. Maintenance interfaces (ACD) The following interfaces belong to the ACD and are controlled by it. These interfaces are all located on the front panel of the CSDU. 1x Ethernet maintenance interface (shop maintenance) 1x Micro USB maintenance interface (on-ground aircraft maintenance) 3x Status LEDs 1x button for push-to-test Power supply input The system is designed for the following power supply input:

115 VAC, 360 to 800 Hz Interface to the SCM The SCM is connected to the CSDU via the following interface:

1x ARINC-781 compliant power and RS-422 communications interface [3]

Interface to the DLNA The DLNA interface is part of the internal SATCOM interfaces and listed below:

1x Coax RF RX to CSDU 2.1.2 2.1.3 2.1.4 2.1.5 98-158751-C Chapter 2: Introduction 2-7 General description 2.1.6 Electrical interfaces - overview s e c a f r e n t i i n b a C s e c a f r e t n i t i p k c o C s e c a f r e t n I t f a r c r i A CSDU 2 x PIESD (Cabin) 10/100 BaseT Ethernet 2 x AISD (EFB) Ethernet 3 x MCDU (A429) ECAM / EICAS (FWC/FWS) 2 x ACARS/CMU (A429) 2 x Cockpit Audio 8 x Cockpit Voice Discrete 1 x Priority Ethernet HPA-5015 MCHPA DLNA Inmarsat TX+Signalling Inmarsat RX 1 x LNA BITE discrete 1 x LNA On/Off discrete HGA Multi-Control (A429) HGA BITE (A429) HGA 1 x Data Load Discrete 1 x Data Loader A615A (Ethernet) 1 x Data Loader A615-3 (A429) SDU-

5045 CSDU 2 x IRS/AHRS/GNSS/NPI (A429) 1 x SCM 1 x Tx Mute Discrete 1 x AES ID (A429) 1 x SDU Reset discrete 1 x WOW Discrete 1 x CFDS/CMC (A429) Aircraft Power : 115V AC Chassis ground SCM SCM-5055 SDU Configuration Module (SCM) up to 5 SIM Cards 1 x ARINC-429 Dual System Crosstalk 1 x Dual System Select 1 x Dual System Disable 2 x ATE Inputs for production 1 x Ethernet on Front Panel

(for production only) 1 x USB on Front Panel

(for maintenance only) 1 x Push-to-Test on Front Panel 3 x Status LED on Front Panel I n t e r n a l S a t c o m i t n e r f a c e s i n t e r f a c e s P r o d u c t i o n

M a n t e n a n c e i Figure 2-2: Electrical interfaces - overview Note The interfaces greyed out are disabled or not in use in the AVIATOR 700S software. This can be due to interfaces not being supported or reserved for future use. Interfaces marked in black are supported in the AVIATOR 700S software. For interfaces marked in black showing support of 2 interfaces, at least one will be implemented. This is the case for AISD EFB Ethernet, e.g. picture shows 2xEFB, but only one EFB interface is available. The second AISD Ethernet is reserved for test or maintenance use. 2-8 Chapter 2: Introduction 98-158751-C Part numbers 2.2 Part numbers This installation manual is for the AVIATOR 700S system and is applicable to the type and part numbers below:

Type number Part number Component name SDU-5045 SCM-5055 HPA-5015 405045-vvccca 405055-vvccc Compact Satellite Data Unit (CSDU) Compact SDU Configuration Module (SCM), external 405015-vvccc Multi-Carrier High Power Amplifier. Table 2-7: Type and part numbers for the AVIATOR 700S system a. The part number suffix vvccc is variable and consists of the fields vv = main variant and ccc = minor variant. The system also needs Field Loadable Software (FLS) containing:

User ORT Secure ORT SDU or CSDU and HPA FLS ORT tool Circuit breakers Part number Recommended circuit breakers 2TC2-2 2TC2-4 Klixon 2TC series, 2 A current rating (AC input) for CSDU Klixon 2TC series, 5 A current rating (AC input) for MCHPA Table 2-8: Part numbers for Klixon circuit breaker Trays and connectors Part number Recommended tray and connector ECS 6L02S1C1C20 AD2-203CF-30081510 CU Tray assembly, 2 MCU (for forced air flow cooling) CSDU tray ARINC 600 connector (Amphenol) NSXN2P221X0008 MCHPA tray ARINC 600 connector (Radiall) Table 2-9: Part numbers for trays and connectors 98-158751-C Chapter 2: Introduction 2-9 Part numbers 2-10 Chapter 2: Introduction 98-158751-C Chapter 3 Equipment drawings 3 This chapter has the following sections. SDU-5045 Compact Satellite Data Unit SCM-5055 SDU Configuration Module HPA-5015 Multi-Carrier High Power Amplifier DLNA Type F CSDU/MCHPA tray CSDU tray connector MCHPA tray connector The following pages show copies of outline drawings of important system units relevant for the installation. 98-158751-C 3-1 SDU-5045 Compact Satellite Data Unit 3.1 SDU-5045 Compact Satellite Data Unit

Figure 3-1: Outline Drawing: CSDU (1/2) 3-2 Chapter 3: Equipment drawings 98-158751-C SDU-5045 Compact Satellite Data Unit

Figure 3-2: Outline Drawing: CSDU (2/2) 98-158751-C Chapter 3: Equipment drawings 3-3 SCM-5055 SDU Configuration Module 3.2 SCM-5055 SDU Configuration Module

Figure 3-3: Outline drawing SCM-5055 (1/2) 3-4 Chapter 3: Equipment drawings 98-158751-C SCM-5055 SDU Configuration Module

Figure 3-4: Outline drawing SCM-5055 (2/2) 98-158751-C Chapter 3: Equipment drawings 3-5 HPA-5015 Multi-Carrier High Power Amplifier 3.3 HPA-5015 Multi-Carrier High Power Amplifier

Figure 3-5: Outline Drawing: MCHPA (1/2) 3-6 Chapter 3: Equipment drawings 98-158751-C HPA-5015 Multi-Carrier High Power Amplifier

Figure 3-6: Outline Drawing: MCHPA (2/2) 98-158751-C Chapter 3: Equipment drawings 3-7 DLNA Type F 3.4 DLNA Type F Figure 3-7: Outline Drawing: DLNA 3-8 Chapter 3: Equipment drawings 98-158751-C 3.5 CSDU/MCHPA tray CSDU/MCHPA tray Figure 3-8: Outline drawing: CSDU/MCHPA tray 98-158751-C Chapter 3: Equipment drawings 3-9 CSDU tray connector 3.6 CSDU tray connector

Figure 3-9: CSDU ARINC 600 tray connector 3-10 Chapter 3: Equipment drawings 98-158751-C 3.7 MCHPA tray connector MCHPA tray connector

Figure 3-10: MCHPA ARINC 600 tray connector 98-158751-C Chapter 3: Equipment drawings 3-11

MCHPA tray connector 3-12 Chapter 3: Equipment drawings 98-158751-C Chapter 4 4 Installation This chapter has the following sections:

General installation information Mounting considerations Electrical installation and wiring Recommended cables Verifying the installation Activation of airtime services 4.1 4.1.1 4.1.2 General installation information Overview This chapter contains considerations and recommendations for the installation of the AVIATOR 700S System. Interconnect harness wiring and physical mounting must satisfy all applicable regulations. Also see the accompanying HGA Installation Manual [8] for the antenna and also DLNA Installation Manual, which is part of the AVIATOR 700S system. The information, drawings and wiring diagrams in this manual are intended as a reference for engineering planning only. The drawings and wiring diagrams contained herein do not represent any specific STC. It is the installers responsibility to compose installation drawings specific to the aircraft. This manual and the drawings and wiring diagrams contained herein may not be used as a substitute for an STC. Note For optimal performance from the AVIATOR 700S system you must strictly follow the installation guidelines in this chapter. System components A working system consists of:

1 SDU-5045 CSDU 1 SCM-5055 SCM 1 HPA-5015 MCHPA 1 DLNA type F 1 HGA for more information, refer to [8]

The SCM is powered by the CSDU. The following drawing shows the minimum installation. 98-158751-C 4-1 General installation information Minimum system drawing This drawing shows which units to connect as a minimum for the system to function.

+115 VAC 360-800 Hz Aircraft Power Supply SCM-5055 SCM 5 1 i n P 8 i n P 2 i n P 1 i n P 4 i n P 3 i n P BP1 +115 VAC Line (Hot) BP7 +115 VAC Neutral (Cold) BP8 Chassis Ground HPA-5015 MCHPA 1 7 P T RF Input MP71 RF Output Cable length Max. 10 m Modem, RF RX/TX Max. 18 dB @ 1.6 GHz Max. 0.6 Ohm DC resistance DLNA

+115 VAC 360-800 Hz Aircraft Power Supply D 2 0 P M D 1 0 P M D 6 0 P M D 5 0 P M n r u t e r r e w o p M C S r e w o p t u p t u o M C S M C S m o r f a t a D

) B t u p n i 2 2 4 S R

M C S m o r f a t a D

) A t u p n i 2 2 4 S R

D 4 0 P M M C S o t a t a D

) B t u p t u o 2 2 4 S R

BP5 +115 VAC Line (Hot) BP1 +115 VAC Neutral (Cold) BP3 Chassis Ground D 3 0 P M M C S o t a t a D

) A t u p t u o 2 2 4 S R

SDU-5045 CSDU 1 7 P T t u p t u o F R Multi Carrier: RX input BP07 HGA Multi-Control A429 A, MP01E HGA Multi-Control A429 B, MP01F HGA BITE A429 A, MP08C HGA BITE A429 B, MP08D IRS/AHRS A429 A, MP02A IRS/AHRS A429 B, MP02B Aircraft ARINC 429 Navigation outputs HGA Figure 4-1: AVIATOR 700S system (minimum, AC powered) 4-2 Chapter 4: Installation 98-158751-C Mounting considerations 4.2 4.2.1 Mounting considerations Overview For optimum system performance you must follow some guidelines on where to install the components of the AVIATOR 700S system. Installation and placement details are included in this section. For information on requirements to cables refer to the individual sections in Electrical installation and wiring on page 4-6. For information on recommended cable types and lengths refer to Recommended cables on page 4-37. Note When mounting the units, give enough space for a sufficient bend radius for the cables. Refer to the cable data sheet for minimum bend radius. 4.2.2 SDU-5045 CSDU Installation Install the CSDU in one of the locations described below:

Temperature/Non-temperature controlled locations and forced airflow cooling (Tray with fan/plenum) Temperature/Non-temperature controlled location and supplied airflow cooling (Tray integrated onto a shelf rack system) Pressurized/Non-pressurized locations. Mount the CSDU in a suitable tray, refer to Figure 3-8: Outline drawing:

CSDU/MCHPA tray and Figure 3-9: CSDU ARINC 600 tray connector. Coolant air pressure drop through the CSDU (ARINC 600 Equipment Level 1) Install the CSDU in a location with forced cooling. The CSDU dissipates approximately 40 W and requires air at a flow rate of 26 kg/hr at a maximum of 70C. This leads to a pressure drop of roughly 20 Pa (2 mm water, within the 5 3 mm of water specification of ARINC 600 [4], Level 1). Ground bonding1 1. Make the grounding wires shorter than 150 mm from grounding start at cable to crimp terminal lugs. 2. Make the grounding wires as short as possible. When you combine ground wires it is necessary that the combined wires are as short as possible. Requirements for combined grounding wire for cockpit audio 1. Crimp with: Contact size: #22, R/R Crimp PIN contacts P/N: AC-772222-301 1. Source: 97-146191. 98-158751-C Chapter 4: Installation 4-3 Mounting considerations 2. Mount according to Amphenol ARINC 600 Document SL-379-3. 3. Mount ground PIN to MP04G on ARINC 600 Connector Chassis Ground: ARINC 600 pin BP3 Amphenol contact part number: AC-781212-304. Fit to wire AWG12 & AWG14 Total max resistance: 25 mOhm. Shield from fluid drippage To fulfill DO-160G Waterproofness Cat. Y, the equipment must be shielded from fluid drippage. 4.2.3 SCM-5055 SCM Installation 1. Install the SCM in temperature controlled/non-controlled Temperature areas and inside or outside pressurized locations (e.g. avionics bay). 2. Forced flow air cooling is not required. 3. To prevent fluids from entering the SCM through the connector, select the SCM mounting orientation such that its connector is not oriented upwards 4. Mount the SCM to the aircraft structure using four fasteners through its mounting flange. Refer to Figure 3-3: Outline drawing SCM-5055 (1/2). The flange thickness is 2 mm. 5. Insert the D-sub connector of the SCM cable harness into the mating connector on the SCM. 6. Torque the cable harness D-sub connector screw-locks to 0.32 Nm. 7. You may add a drip loop to the cable harness to prevent water from flowing along the cable harness and towards the SCM connector. Ground bonding 1. Use an electrically conductive back shell for the DB15 connector. 2. Terminate the cable shields to the electrically conductive back shell. 3. Bond the SCM to the aircraft structure via the top and bottom surfaces of the SCM mounting flange. These are electrically conductive and are designated as the equipment's ground bonding points. Refer to Figure 3-3: Outline drawing SCM-

5055 (1/2). 4. The M3 threaded stud provides an alternative means for bonding the SCM and may be used at the installer's discretion by fitting a suitable ground bonding strap. Refer to Figure 3-2. 4-4 Chapter 4: Installation 98-158751-C Mounting considerations 4.2.4 HPA-5015 MCHPA Installation Install the MCHPA in one of the locations described below:

Temperature/Non-temperature controlled locations and forced airflow cooling (Tray with fan/plenum) Temperature/Non-temperature controlled location and supplied airflow cooling (Tray integrated onto a shelf rack system) Pressurized/Non-pressurized locations. Mount the MCHPA in a suitable tray, refer to Figure 3-8: Outline drawing:

CSDU/MCHPA tray and Figure 3-10: MCHPA ARINC 600 tray connector. Coolant air pressure drop through the MCHPA (ARINC 600 Equipment Level 1) Install the MCHPA in a location with forced cooling. The MCHPA requires air at a flow rate of 43.9 kg/hr at a maximum of 70C, with a maximum allowed pressure drop of 5030 Pa (53 mm of water). (ARINC 600 [4] Level 1). Ground bonding1 1. Make the grounding wires shorter than 150 mm from grounding start at cable to crimp terminal lugs. 2. Make the grounding wires as short as possible. When you combine ground wires it is necessary that the combined wires are as short as possible. Chassis Ground: ARINC 600 pin BP8 Radiall contact part number: 620 341. Fit to wire AWG18-20-22-24 Total max resistance: 25 mOhm. Shield from fluid drippage To fulfill DO-160G Waterproofness Cat. Y, the equipment must be shielded from fluid drippage. 1. Source: 97-146191. 98-158751-C Chapter 4: Installation 4-5 Electrical installation and wiring 4.3 4.3.1 Electrical installation and wiring Wiring symbols Throughout the wiring section these common symbols are used:

Coax Shield Ground (fuselage) Twisted Twisted and shielded Important Each wiring drawing in this chapter only shows the connections referred to in that particular section. Other connections may be required for the system to work properly. 4-6 Chapter 4: Installation 98-158751-C 4.3.2 Wiring overview Ethernet 1 from CSDU to EFB 1 TX+

Ethernet 1 from CSDU to EFB 1 TX-

Ethernet 1 from EFB to CSDU 1 RX+

Ethernet 1 from EFB to CSDU 1 RX-

Ethernet 2 from CSDU to Cabin 1 TX+

Ethernet 2 from CSDU to Cabin 1 TX-

Ethernet 2 from Cabin 1 to CSDU RX+

Ethernet 2 from Cabin 1 to CSDU RX-

Ethernet 11 from CSDU to EFB2 TX+ Future use Ethernet 11 from CSDU to EFB2 TX- Future use Ethernet 11 from EFB2 to CSDU RX+ Future use Ethernet 11 from EFB2 to CSDU RX- Future use Ethernet 12 from CSDU to Cabin2 TX+ Future use Ethernet 12 from CSDU to Cabin2 TX- Future use Ethernet 12 from Cabin2 to CSDU RX+ Future use Ethernet 12 from Cabin2 to CSDU RX- Future use Ethernet 3 from CSDU to ADL TX+

Ethernet 3 from CSDU to ADL TX-

Ethernet 3 from ADL to CSDU RX+

Ethernet 3 from ADL to CSDU RX-

Ethernet 4 from CSDU to ACD1 TX+

Ethernet 4 from CSDU to ACD1 TX-

Ethernet 4 from ACD1 to CSDU RX+

Ethernet 4 from ACD1 to CSDU RX-

Ethernet 5 from CSDU to ACD2 TX+

Ethernet 5 from CSDU to ACD2 TX-

Ethernet 5 from ACD2 to CSDU RX+

Ethernet 5 from ACD2 to CSDU Rx-

Crosstalk to other SDU A TX+ Future use Crosstalk to other SDU B TX- Future use Crosstalk from other SDU A RX+ Future use Crosstalk from other SDU B RX- Future use TP03A (+TX) TP04B (-TX) TP03B (+RX) TP04A (-RX) TP06A (+TX) TP07B (-TX) TP06B (+RX) TP07A (-RX) TP03J (+TX) TP04K (-TX) TP03K (+RX) TP04J (-RX) TP06J (+TX) TP07K (-TX) TP06K (+RX) TP07J (-RX) MP1T1 (+TX) MP1T3 (-TX) MP1T2 (+RX) MP1T4 (-RX) MP2T1 (+TX) MP2T3 (-TX) MP2T2 (+RX) MP2T4 (-RX) MP06E (+TX) MP06F (-TX) MP07E (+RX) MP07F (-RX) MP09G A429 MP09H A429 MP09C A429 MP09D A429 CSDU SDU-5045 Electrical installation and wiring DB15 Data from MCDU 1 Data from MCDU 1 Data from MCDU 2 Data from MCDU 2 Data from MCDU 3 Data from MCDU 3 Data to MCDU 1, 2, 3 Data to MCDU 1, 2, 3 Data from CMU 1 Data from CMU 1 Data from CMU 2 Data from CMU 2 Data to CMU 1 & 2 Data to CMU 1 & 2 Data from CFDS Data from CFDS Data to CFDS Data to CFDS AES ID AES ID Data from GNSS to SDU A Data from GNSS to SDU B Data from Sec. IRS/GNSS A Data from Sec. IRS/GNSS B Data from Pri. IRS/GNSS A Data from Pri. IRS/GNSS B Spare ARINC 429 Spare ARINC 429 Data to EICAS/FWS A Data to EICAS/FWS B From Airborne Data Loader A From Airborne Data Loader B To Airborne Data Loader A To Airborne Data Loader B Cockpit Audio Input 1 (Hi) Cockpit Audio Input 1 (Lo) Cockpit Audio Output 1 (Hi) Cockpit Audio Output 1 (Lo) Cockpit Audio Input 2 (Hi) Cockpit Audio Input 2 (Lo) Cockpit Audio Output 2 (Hi) Cockpit Audio Output 2 (Lo) Antenna BITE Antenna BITE Antenna Multi Control Antenna Multi Control A-429 input (A) A-429 input (B) A-429 input (A) A-429 input (B) A-429 input (A) A-429 input (B) A-429 output (A) A-429 output (B) A-429 input (A) A-429 input (B) A-429 input (A) A-429 input (B) A-429 output (A) A-429 output (B) A-429 input (A) A-429 input (B) A-429 output (A) A-429 output (B) A-429 input (A) A-429 input (B) A-429 input (A) A-429 input (B) A-429 input (A) A-429 input (B) A-429 input (A) A-429 input (B) MP01A MP01B MP01J MP01K MP10A MP10B MP10J MP10K MP03A MP03B MP03J MP03K MP07J MP07K MP08A MP08B MP08J MP08K MP07A MP07B MP06J MP06K MP02J MP02K MP02A MP02B A-429 input (A) A-429 input (B) A-429 output (A) A-429 output (B) A-429 input (A) A-429 input (B) A-429 output (A) A-429 output (B) MP06G MP06H MP05G MP05H MP09A MP09B MP09J MP09K 4-Wire 4-Wire 4-Wire 4-Wire 4-Wire 4-Wire 4-Wire 4-Wire MP04A (Hi) MP04B (Lo) MP05A (Hi) MP05B (Lo) MP04J (Hi) MP04K (Lo) MP05J (Hi) MP05K (Lo) A-429 input (A) A-429 input (B) A-429 output (A) A-429 output (B) MP08C MP08D MP01E MP01F Reserved Ext. Reset Discrete Output (Spare) Call Place/End 2 Call Place/End 1 Cockpit Voice Mic On 2 Cockpit Voice Mic On 1 Cockpit Voice Go Ahead Chime Reset 1 Cockpit Voice Call Light Output 1 WOW Input 1 Discrete Output (Spare) Data Loader Link A Cockpit Voice Call Light Output 2 Spare Discrete Output Discrete Input (Spare) Discrete Input (Spare) Discrete Input (Spare) Service Availability Discretes 4 TX Mute Input Service Availability Discretes 1 Service Availability Discretes 2 Discrete Input (Spare) Service Availability Discretes 3 Dual System Disable Discrete Input Dual System Select Discrete I/O MP01G MP05E Discrete Input Discrete Output MP01H MP01C MP04H MP04C MP05C MP03C MP07D MP03E MP08E MP03H MP04E MP07C MP06C MP06A MP12F Discrete Input Discrete Input Discrete Input Discrete Input Discrete Input Discrete Output Discrete Input Discrete Output Discrete Input Discrete Output Discrete Output Discrete Input Discrete Input Discrete Input Discrete Output MP08F MP11E Discrete Input Discrete Output MP11F MP06B MP12E MP09F MP09E Discrete Output Discrete Input Discrete Output Future Use Future Use Cockpit Voice Chime contact 1,2 Cockpit Voice Chime contact 1,2 MP02C MP02H Contact Function Contact Function 3 4 1 2 8 15 7 3 4 1 2 8 15 7 DB15 Data to SCM A Data to SCM B Data from SCM A Data from SCM B SCM Power output SCM Power Return Chassis Max. Length: 10 m MP03D MP04D MP05D MP06D MP01D MP02D RS-422 output RS-422 output RS-422 input RS-422 input SCM Power output SCM Power return d n u o r G s s s a h C i t l d o C c a V 5 1 1 o H c a V 5 1 1 5 P B 1 P B 3 P B SDU Configuration Module SCM-5055 TNC-TNC TP71 RF TX to MCHPA MP04G BP07 Front panel Front panel Audio ground RX input from DLNA Maintenance LAN # 7 Maintenance USB USB Cable Length: 5 m 115 VAC Hot 115 VAC Cold Figure 4-2: Wiring overview 98-158751-C Chapter 4: Installation 4-7 Electrical installation and wiring 4.3.3 To wire the CSDU with AC input ARINC-781 compliant. The aircraft power bus provides the electric power required to operate the CSDU, and a chassis connection to the aircraft chassis and the installation tray. The +115 VAC power wire must include a circuit breaker capable of carrying the required current continuously under the required environmental conditions. The following drawing shows the wiring of the CSDU AC power supply. Requirements to the wiring are stated in the notes on the drawing and in the section To wire the MCHPA with AC input on page 4-10. Aircraft power Bus 115 VAC

(360 Hz to 800 Hz)

[1]

[2]

[4]

5 A

[3]

BP5 +115 VAC Line (Hot) BP1 +115 VAC Neutral (Cold) CSDU BP3 Chassis

[1] + [2] Total resistance (Hot and cold) max. 1 Ohm incl. circuit breaker.

[3] Directly to installation tray and aircraft chassis, max. 25 mOhm resistance.

[4] Compatible with an aircraft circuit breaker of the following characteristics: 115VAC /

5A Solid state power controllers (SSPC) Figure 4-3: Wiring AC power The COLD does not need to go through a breaker. The COLD must not be connected to chassis ground. Connect the COLD to the aircraft power bus as stated in the following table. Pins for AC power The following list shows the pins used for the AC power supply. CSDU pin BP5 BP1 BP3 Name Description

+115 VAC Line (Hot)

+115 VAC Neutral

(Cold) Chassis Ground

+115 VAC Line (Hot) power input from aircraft power bus.

+115 VAC Neutral (Cold) return from aircraft power bus. Chassis connection, connect to the installation tray and Aircraft chassis. Table 4-1: CSDU pins (AC input) 4-8 Chapter 4: Installation 98-158751-C Electrical installation and wiring Description of the CSDU power supply

+115 VAC Power (BP1, BP5) The target line impedance should be as low as possible; 1 Ohm preferred maximum;

should not exceed 4 Ohms. Required current capability for the Circuit Breaker: 99 W @ 90 VAC which equals 1.1 A at the required environmental conditions. A suitable circuit breaker is Klixon 2TC series with 2 A current rating. Important Use a separate 2 A circuit breaker for the AC input. Chassis Ground (BP3) The chassis connection makes sure that the cabinet and the installation tray has the same potential, and that there is a connection from the wiring shields to the cabinet for EMC

(ElectroMagnetic Compatibility) purposes. Connect the wire directly to the installation tray, and to aircraft chassis. Cable requirements, CSDU power supply (AC) Cablea

[1] 115 VAC Line and neutral

[2] Chassis Ground Maximum resistance 1 , incl. circuit breaker Other Requirements 25 m Connect directly to the aircraft chassis. Table 4-2: Requirements to CSDU power cables (AC input) a. The cable numbers refer to the numbers stated on the wiring drawing in the section To wire the CSDU with AC input on page 4-8. Note Maximum cable lengths are calculated and listed in the section Allowed cable lengths for power cables on page 4-37. 98-158751-C Chapter 4: Installation 4-9 Electrical installation and wiring 4.3.4 To wire the MCHPA with AC input ARINC-781 compliant. The aircraft power bus provides the electric power required to operate the MCHPA, and a chassis connection to the aircraft chassis and the installation tray. The +115 VAC power wire must include a circuit breaker capable of carrying the required current continuously under the required environmental conditions. The following drawing shows the wiring of the MCHPA AC power supply. Aircraft power Bus 115 VAC

(360 Hz to 800 Hz)

[1]

[2]

[4]

5 A

[3]

BP1 +115 VAC Line (Hot) BP7 +115 VAC Neutral (Cold) MCHPA BP8 Chassis

[1] + [2] Total resistance (Hot and cold) max. 1 Ohm incl. circuit breaker.

[3] Directly to installation tray and aircraft chassis, max. 25 mOhm resistance.

[4] Compatible with an aircraft circuit breaker of the following characteristics: 115VAC /

5A Solid state power controllers (SSPC) Figure 4-4: Wiring AC power The COLD does not need to go through a breaker. The COLD must not be connected to chassis ground. Connect the COLD to the aircraft power bus as stated in the following table. Pins for AC power The following list shows the pins used for the AC power supply. CSDU pin BP1 BP7 BP8 Name Description

+115 VAC Line (Hot)

+115 VAC Neutral

(Cold) Chassis Ground

+115 VAC Line (Hot) power input from aircraft power bus.

+115 VAC Neutral (Cold) return from aircraft power bus. Chassis connection, connect to the installation tray and Aircraft chassis. Table 4-3: MCHPA pins (AC input) 4-10 Chapter 4: Installation 98-158751-C Electrical installation and wiring Description of the MCHPA power supply

+115 VAC Power (BP1, BP7) The target line impedance should be as low as possible; 1 Ohm preferred maximum;

should not exceed 4 Ohms. Required current capability for the Circuit Breaker: 300 W @ 90 VAC which equals 3.33 A at the required environmental conditions. A suitable circuit breaker is Klixon 2TC series with 5 A current rating. Important Use a separate 5 A circuit breaker for the AC input. Chassis Ground (BP8) The chassis connection makes sure that the cabinet and the installation tray has the same potential, and that there is a connection from the wiring shields to the cabinet for EMC

(ElectroMagnetic Compatibility) purposes. Connect the wire directly to the installation tray, and to aircraft chassis. Cable requirements, MCHPA power supply (AC) Cablea

[1] 115 VAC Line and neutral

[2] Chassis Ground Maximum resistance 1 , incl. circuit breaker Other Requirements 25 m Connect directly to the aircraft chassis. Table 4-4: Requirements to CSDU power cables (AC input) a. The cable numbers refer to the numbers stated on the wiring drawing in the section To wire the MCHPA with AC input on page 4-10. Note Maximum cable lengths are calculated and listed in the section Allowed cable lengths for power cables on page 4-37. 98-158751-C Chapter 4: Installation 4-11 Electrical installation and wiring 4.3.5 To wire the SCM Wiring diagram The following drawing shows the wiring of the SCM to the CSDU. The SCM connector pin-out is compliant with ARINC-781. 10 meter Interconnecting Cable:

Carlisle (Tensolite) P/N NF24Q100-01 100Base-T Ethernet Cable. 100ohm 10%, 13pF/ft, AVG24 DB15 FEMALE

(Rear view) 1 9 15 8 3 4 1 2 8 15 Red Blue Yellow Green White White w/blue stripe MP03D MP04D MP05D MP06D MP01D MP02D Interconnecting Cable:

Carlisle (Thermax) M27500-22 WJ 2 S 24 (MIL-DTL-22759/86 wire)

(Silver plated shield) Figure 4-5: To wire the SCM Maximum cable length: 10 m (ARINC-781) Pins for the SCM CSDU pin Description MP01D SCM Power, +8 to 18 V MP02D SCM Power return 0V MP03D CSDU data to SCM A MP04D CSDU data to SCM B MP05D SCM data to CSDU A MP06D SCM data to CSDU A Mating connector The mating connector for use on the SCM cable harness is a 15 position D-subminiature receptacle (sockets), MIL DTL-24308 M24308/2-2 or equivalent. 4.3.6 To wire the MCHPA ARINC-781 compliant. There is only one coaxial cable between CSDU and MCHPA. 4-12 Chapter 4: Installation 98-158751-C Electrical installation and wiring Cable losses Note During installation, measure and write down the cable loss of the RF cables. See section 4.3 for the maximum loss requirement at 1.6 GHz. Wiring diagram See Figure 4-1: AVIATOR 700S system (minimum, AC powered) for the wiring for an AVIATOR 700S System with the HPA-5015 MCHPA For the requirements to RF cable see Recommended RF cables on page 4-38 on pin TP71. Pins for the MCHPA/CSDU From To Description CSDU-TP71 MCHPA-MP71 MCHPA-TP71 MCHPA RF input from CSDU MCHPA RF output to DLNA DLNA 4.3.7 To wire the MCDU 1, 2 and 3 ARINC-781 compliant. The CSDU has interfaces for three high or low speed ARINC-429 interfaces for communication with MCDU #1, MCDU #2 and MCDU #3. For cable requirements see Recommended cables for ARINC 429 on page 4-38. Description The Multi Control and Display Unit (MCDU) interfaces allow the CSDU to be managed from a cockpit control panel. The CSDU uses MCDU protocol standards defined in ARINC Characteristic 739 or WSCI (see ARINC 741, Part 2, Attachment 2F-42.1). Display and control details may be manufacturer-specific. Wiring diagram See Wiring overview on page 4-7. Pins for MCDU 1, 2 and 3 CSDU pin Description MP10J MP10K MP01A MP01B MP01J MP01K MP10A MP10B Data to MCDU 1,2,3. A. (A429 output) Data to MCDU 1,2,3. B. (A429 output) Data from MCDU 1. A. (A429 input) Data from MCDU 1. B. (A429 input) Data from MCDU 2. A. (A429 input) Data from MCDU 2. B. (A429 input) Data from MCDU 3. A. (A429 input) Data from MCDU 3. B. (A429 input) 98-158751-C Chapter 4: Installation 4-13 Electrical installation and wiring 4.3.8 To wire the CMU 1 and 2 ARINC-781 compliant. Description The Communications Management Unit (CMU) or equivalent is responsible for integrating data communications or datalinks on the aircraft. The CMU manages communication across multiple subnetworks, including VHF and SATCOM networks. Wiring diagram See Wiring overview on page 4-7. Pins for CMU 1 and 2 CSDU pin Description MP07J MP07K MP03A MP03B MP03J MP03K Data to CMU 1 and 2. A. (A429 output) Data to CMU 1 and 2. B. (A429 output) Data from CMU 1. A. (A429 input) Data from CMU 1. B. (A429 input) Data from CMU 2. A. (A429 input) Data from CMU 2. B. (A429 input) 4.3.9 To wire aircraft AES ID ARINC-781 compliant. Description of the aircraft AES ID AES ID input for reception of a unique aircraft identification code. Wiring diagram See Wiring overview on page 4-7 Pins for aircraft AES ID CSDU pin Description MP07A MP07B Data from AES ID. A. (A429 input) Data from AES ID. B. (A429 input) 4.3.10 To wire cockpit audio 1 and 2 ARINC-781 compliant. See also the wiring of the cockpit audio discrete interfaces in section 4.3.13. 4-14 Chapter 4: Installation 98-158751-C Electrical installation and wiring Description of the cockpit audio 1 and 2 There are two 4-wire interfaces to be connected to a headset. Wiring diagram See Wiring overview on page 4-7 Pins for cockpit audio 1 and 2 CSDU pin Description MP04A MP04B MP05A MP05B MP04J MP04K MP05J MP05K Cockpit audio input 1. High. Cockpit audio input 1. Low. Cockpit audio output 1. High. Cockpit audio output 1. Low. Cockpit audio input 2. High. Cockpit audio input 2. Low. Cockpit audio output 2. High. Cockpit audio output 2. Low. 4.3.11 To wire IRS/GNSS Wiring diagram See Wiring overview on page 4-7. Pins for IRS/GNSS CSDU pin Description MP02A MP02B MP02J MP02K MP06J MP06K Data from primary IRS/GNSS A Data from primary IRS/GNSS B Data from secondary IRS/GNSS A Data from secondary IRS/GNSS B Data from GNSS to CSDU A Data from GNSS to CSDU B 4.3.12 To wire antenna BITE ARINC-781 compliant. Description of the antenna BITE CSDU receives antenna BITE data on this arinc 429 input. 98-158751-C Chapter 4: Installation 4-15 Electrical installation and wiring Wiring diagram See Wiring overview on page 4-7 Pins for antenna BITE CSDU pin Description MP08C MP08D Data from antenna BITE. A. (A429 input) Data from antenna BITE. B. (A429 input) 4.3.13 To wire EICAS/FWS ARINC-781 compliant. Description of the EICAS/FWS CSDU sends data for ECAM/FWS alert. Wiring diagram See Wiring overview on page 4-7 Pins for EICAS/FWS CSDU pin Description MP05G MP05H Data to EICAS/FWS. A. (A429 output) Data to EICAS/FWS. B. (A429 output) 4.3.14 To wire discrete inputs and outputs ARINC-781 compliant. Description Various discrete interfaces are available, as listed here. Wiring diagram See Wiring overview on page 4-7 Pins for discrete inputs and outputs CSDU Pin Description MP01C Call Place End Discrete Input 1, Cockpit Voice discrete input MP01H Call Place End discrete Input 2. Cockpit Voice discrete input MP01G External reset Discrete Input MP02C Cockpit Voice Chime signal contact 1. Discrete "relay" contact MP02H Cockpit Voice Chime Signal Contact 2. Discrete "relay" contact 4-16 Chapter 4: Installation 98-158751-C Electrical installation and wiring Cockpit Voice Call Light output 1. Cockpit Voice discrete output ACARS Service Available discrete output (spare) CSDU Pin Description MP03C MP03E MP03H Cockpit Voice Call Light output 2. Cockpit Voice discrete output MP04C MP04E MP04H Cockpit Voice Mic On input 2. Cockpit Voice discrete input MP05C Cockpit Voice Mic On input 1. Cockpit Voice discrete input Spare Cockpit Voice Go Ahead Chime reset 1. Cockpit Voice discrete input Spare discrete output #3 MP05E MP06A Chime/Lamps Inhibit Discrete Input (generic input) MP07C MP07D WOW input1 MP08E MP08F MP09E MP09F MP11E MP11F MP12E MP12F Data loader link A. Discrete input TX mute input. Discrete input Dual System Select Discrete I/O (provision) Dual System Disable Discrete I/O (provision) Service Availability Discretes 1 - Cockpit Service Available (spare) Service Availability Discretes 2 - Cabin Service Available (spare) Service Availability Discretes 3 - Cabin Incoming Call (spare) Service Availability Discretes 4 - System FAIL (spare) Spare discrete input #4 4.3.15 To wire airborne data loader ARINC-781 compliant. Description of the data loaded Supports ARINC 429 data loaders compliant to ARINC 615-3. Wiring diagram See Wiring overview on page 4-7 Pins for airborne ARINC 429 (ARINC 615-3) data loader CSDU pin Description MP09A MP09B MP09J From airborne data loader A From airborne data loader B To airborne data loader A 98-158751-C Chapter 4: Installation 4-17 Electrical installation and wiring CSDU pin Description MP09K To airborne data loader B 4.3.16 To wire Antenna multi control ARINC-781 compliant. Description of the antenna multi control Arinc 429 output to control High Gain Antenna. Wiring diagram See Wiring overview on page 4-7 Pins for antenna multi control CSDU pin Description MP01E MP01F Data to HGA. A. (A429 output) Data from HGA. B. (A429 output) 4.3.17 To wire fault/health reporting (CFDS) ARINC-781 compliant. Description of the fault/health reporting The CSDU communicates Built-In Test Equipment (BITE) reporting to the aircraft Centralized Fault Display System (CFDS) or Central Maintenance Computer (CMC). Wiring diagram See Wiring overview on page 4-7 Pins for fault/health reporting CSDU pin Description MP08A MP08B MP08J MP08K Data from CFDS A Data from CFDS B Data to CFDS A Data to CFDS B 4.3.18 To wire Ethernet 1 (AISD#1 or EFB 1) ARINC-781 compliant. 4-18 Chapter 4: Installation 98-158751-C Electrical installation and wiring Ethernet Port Definition: Electronic Flight Bag 1 Security Domain: Airline Information Services Domain (AISD) Ethernet 11 (AISD#2):

Description of Ethernet 1 (AISD#1 or EFB 1) The EFB 1 interface is for cockpit (AISD) applications which require an IP data connection, for example for EFB connectivity. Wiring diagram See Wiring overview on page 4-7 Pins for Ethernet 1 (AISD#1 or EFB 1) CSDU pin Description TP03A TP03B TP04B TP04A Ethernet 1 from CSDU to User + (AISD#1) Ethernet 1 from User to CSDU + (AISD#1) Ethernet 1 from CSDU to User - (AISD#1) Ethernet 1 from User to CSDU - (AISD#1) 4.3.19 To wire Ethernet 11 (AISD#2 or EFB2) The Ethernet 11 interface is ARINC-781 compliant, but reserved for flight test use only and disabled for general use. Ethernet Port Definition: Electronic Flight Bag 2 Security Domain: Airline Information Services Domain (AISD) Description of Ethernet 11 (AISD#2 or EFB 2) This interface is for test purposes only and is only accessible when the aircraft is in flight test mode. Wiring diagram See Wiring overview on page 4-7 Pins for Ethernet 11 (AISD#2 or EFB 2) CSDU pin Description TP03J TP03K TP04K TP04J Ethernet 11 from CSDU to User + (AISD#2) Ethernet 11 from User to CSDU + (AISD#2) Ethernet 11 from CSDU to User - (AISD#2) Ethernet 11 from User to CSDU - (AISD#2) 98-158751-C Chapter 4: Installation 4-19 Electrical installation and wiring 4.3.20 To wire Ethernet 3 (ADL in ACD) ARINC-781 compliant. Description Ethernet Port Definition: Airborne Data Loader Security Domain: Aircraft Control Domain (ACD) Wiring diagram See Wiring overview on page 4-7 Pins for Ethernet 3 (ACD) Quadrax connector CSDU pin Description MP 1T 1 Ethernet 3 from CSDU to ADL +

MP 1T 2 Ethernet 3 from ADL to CSDU +

MP 1T 3 Ethernet 3 from CSDU to ADL -

MP 1T 4 Ethernet 3 from ADL to CSDU -

4.3.21 To wire Ethernet 2 (PIESD#1 or Cabin1) Ethernet Port Definition: Cabin 1 Security Domain: Passenger Information Entertainment Services Domain (PIESD) Description of Ethernet 2 (PIESD#1) This interface is for cabin (PIESD) applications. Wiring diagram See Wiring overview on page 4-7 Pins for Ethernet 2 (PIESD#1) CSDU pin Description TP06A TP06B TP07B TP07A Ethernet 2 from CSDU to User + (PIESD#1) Ethernet 2 from User to CSDU + (PIESD#1) Ethernet 2 from CSDU to User - (PIESD#1) Ethernet 2 from User to CSDU - (PIESD#1) 4.3.22 To wire Ethernet 12 (PIESD#2 or Cabin2) The Ethernet 12 interface is ARINC-781 compliant, but reserved for flight test use only and disabled for general use. Ethernet Port Definition: Cabin 2 4-20 Chapter 4: Installation 98-158751-C Electrical installation and wiring Security Domain: Passenger Information Entertainment Services Domain (PIESD) Description of Ethernet 12 (PIESD#2) This interface is for cabin (PIESD) applications. Future use of the Cabin 2 interface is Crosstalk master/slave interface to other CSDU. Wiring diagram See Wiring overview on page 4-7 Pins for Ethernet 12 (PIESD#2) CSDU pin Description TP06J TP06K TP07K TP07J Ethernet 12 from CSDU to User + (PIESD#2) Ethernet 12 from User to CSDU + (PIESD#2) Ethernet 12 from CSDU to User - (PIESD#2) Ethernet 12 from User to CSDU - (PIESD#2) 4.3.23 To wire Ethernet 4 (ACD#1) ARINC-781 / ARINC-771 compliant, 10/100BASE-TX, Cabin 2. Description of Ethernet 4 (ACD#1) This interface is software disabled and reserved for future use. Ethernet Port Definition: Cockpit Priority Data 1 Security Domain: Aircraft Control Domain (ACD) Wiring diagram See Wiring overview on page 4-7 Pins for Ethernet 4 (ACD#1) Quadrax connector CSDU pin Description MP 2T 1 MP 2T 2 MP 2T 3 MP 2T 4 Ethernet 4 from CSDU to User +

Ethernet 4 from User to CSDU +

Ethernet 4 from CSDU to User -

Ethernet 4 from User to CSDU -

4.3.24 To wire Ethernet 5 (ACD#2) The Ethernet 5 interface is ARINC-781 compliant, but reserved for flight test use only and disabled for general use. 98-158751-C Chapter 4: Installation 4-21 Electrical installation and wiring Description This interface is test purposes only and is only accessible when the aircraft is in Flight Test mode. Wiring diagram See Wiring overview on page 4-7 Pins for Ethernet 5 (ACD#2) CSDU pin Description MP06E Ethernet 5 (Spare) from CSDU to User +

(ACD#2) Ethernet 5 (Spare) from User to CSDU +

(ACD#2) Ethernet 5 (Spare) from CSDU to User - (ACD#2) Ethernet 5 (Spare) from User to CSDU - (ACD#2) MP07E MP06F MP07F 4.3.25 To wire the Maintenance interfaces Important Make sure that there is no cable connected to the CSDU Maintenance connector when the aircraft is airborne. SDU-5045 Compact Satellite Data Unit The CSDU Front Panel Ethernet interface is for shop maintenance use only and disabled for general use. The following drawing shows the wiring of the Maintenance PC connection on the CSDU front via Micro USB. Micro USB CSDU 1 2 3 4 5 VCC D-

D+

GND ID Not used Maintenance PC 1 2 3 4 5 Figure 4-6: Wiring Maintenance PC via Micro USB Figure 4-7: Micro USB maintenance connector of the CSDU, face view of engaging end 4-22 Chapter 4: Installation 98-158751-C Electrical installation and wiring The following list shows the pins used for the Micro USB interface (Front connector on the CSDU). Pin 1 2 3 4 5 Pin Name Description VCC D-

D+

ID GND

+5 VDC Data -

Data +

Not Used Signal ground Description of the maintenance interfaces on the CSDU Use the maintenance interface on the front of the CSDU or the AISD 1/EFB 1 (Ethernet 11) interface for maintenance purposes. These interfaces are only accessible for maintenance when the aircraft is on the ground. The interfaces can be accessed from a PC with Ethernet interface or a Micro USB connector. The maintenance interface has the following characteristics:

Ethernet 11 (AISD 1 / EFB 1):100 Base-T /10 Base-T Ethernet / IEEE 802.3 Front Panel Micro USB (115200 bps) Person Activated Self Test (PAST) Push-To-Test button The CSDU resets the system and initiates a Person Activated Self-Test "PAST" when the Push-To-Test button on the front panel is pressed for at least 2 seconds and less than 20 seconds and while in Maintenance Allowed mode (i.e. a PC is connected via the Micro USB maintenance interface on the front of the CSDU or via the AISD 1 / EFB 1 Ethernet interface). Figure 4-8: SDU-5045 Front plate 98-158751-C Chapter 4: Installation 4-23 Electrical installation and wiring The front panel status LEDs (see Status signalling with LEDs on page 7-8) will display the following:

Steady red: A fault, which may degrade the system operation, is present in the CSDU. Flashing short green/long pause: Power On Self-Test (POST) or Person Activated Self-Test (PAST) is in progress. Flashing long green/short orange: No failure, but a BITE failure/warning is logged in the BITE log, severity ERROR. Steady green: No faults. Off->orange->off->red->off->green->off: Indicator Test When powering up the initial color of the 3 LEDs is orange. 4-24 Chapter 4: Installation 98-158751-C Electrical installation and wiring 4.3.26 CSDU ARINC 600 connector block ARINC 600 connector drawing - overview 1 2 3 4 5 6 7 1 2 3 4 5 6 7 8 9 10 11 Pin 71 A B C D E F G H J K A B C D E F G H J K 2 3 12 13 14 15 1 4 1T 2 1 3 4 2T 2 4 7 9 8 10 11 12 5 1 3 6 Size 2 Shell receptacle Top Plug (TP):

Insert arrangement 08 Receptacles 1 Size 1 Coax cavity 50 Size 22 sockets

= empty cavity Middle Plug (MP):

Insert arrangement 120Q2 Receptacles 2 Size 8 Quadrax cavities 118 Size 22 sockets Index pin code 81 (5,2,2) Light areas are key holes in receptacle. Bottom Plug (BP):

Insert arrangement 12F5C2 Receptacles 4 Size 12 pins 1 Size 16 pin, 2 Size 5 coax cavities 5 Size 16 optical cavities (not used) Figure 4-9: CSDU ARINC 600 connector specifications 98-158751-C Chapter 4: Installation 4-25 Electrical installation and wiring ARINC 600 connector drawings with functions The following drawing shows the top plug, middle plug and bottom plug of the SDU rear receptacle with pin functions. For wiring details of this connector see Electrical installation and wiring on page 4-6. Note The pins in grey colour are not used or empty cavity and not connected inside CSDU. A B C D E F G H J K RF TX Pin 71 To HPA 1 2 3 4 5 6 7 ATE Pin 1

(5V on BP6 Discrete Input) ATE Pin 2

(26V on BP6 Discrete Input) ATE Pin 3 GND)

(Remote WLU ATE Pin 11

(Empty Cavity) ATE Pin 12

(Empty Cavity) ATE Pin 13

(Empty Cavity) ATE Pin 4

(Cabin Domain disable Discrete Input) ATE Pin 14 ATE Pin 5 Output) ATE Pin 15 ATE Pin 6 Output) ATE Pin 16

(Slave CSDU Reset Discrete

(Fall-back SDU Reset Discrete

(Remote WLU Status Discrete Input)

(Remote WLU PSU Status Discrete Input)

(Remote WLU Spare Control Discr. Output) Ethernet 1 from CSDU to EFB1 +

(AISD) Ethernet 1 from EFB1 to CSDU -

(AISD) Ethernet 1 from EFB1 to CSDU +

(AISD) Ethernet 1 from CSDU to EFB1 -

(AISD) Empty Cavity Empty Cavity Ethernet 2 from CSDU to Cabin 1 +

(PIESD) Ethernet 2 from Cabin 1 to CSDU -

(PIESD) Ethernet 2 from Cabin 1 to CSDU +

(PIESD) Ethernet 2 from CSDU to Cabin 1 -

(PIESD) Empty Cavity Empty Cavity Empty Cavity Empty Cavity Empty Cavity Config Pin 1

(0V Common) Config Pin 5 SDU Number Config Pin 9 Config Pin 13

[SPARE]

Config Pin 17

[SPARE]

Config Pin 2 Config Pin 6 Config Pin 10 Config Pin 14

[SPARE]

Config Pin 18

[SPARE]

Config Pin 3 Config Pin 7 Config Pin 11 Config Pin 15

[SPARE]

Config Pin 19

[SPARE]

ATE Pin 7

(ATE pin A) ATE Pin 8

(ATE pin B) ATE Pin 9

(28V DC Fan Power) ATE Pin 10

(Fan Return) ATE Pin 17

(Remote WLU PSU Control Discr. Output) Config Pin 4 SCM installed Config Pin 8 Config Pin 12 Config Pin 16

[SPARE]

Config Pin 20

[SPARE]

ATE Pin 18

(Empty Cavity) ATE Pin 19

(Empty Cavity) ATE Pin 20

(Empty Cavity) Empty Cavity Empty Cavity Empty Cavity Empty Cavity Empty Cavity Ethernet 11 From CSDU to EFB 2 +

(AISD) Ethernet 11 From EFB 2 to CSDU -

(AISD) Ethernet 11 From EFB 2 to CSDU +

(AISD) Ethernet 11 From CSDU to EFB 2 -

(AISD) Empty Cavity Empty Cavity Ethernet 12 From CSDU to Cabin 2 +

(PIESD) Ethernet 12 From Cabin 2 to CSDU +

(PIESD) Ethernet 12 From Cabin 2 to CSDU -

(PIESD) Ethernet 12 From CSDU to Cabin 2 -

(PIESD) Figure 4-10: CSDU Top Plug in rear receptacle with pin functions 4-26 Chapter 4: Installation 98-158751-C Electrical installation and wiring H Call Place/End Discrete Input 2 J K Data from MCDU 2 A Data from MCDU 2 B Cockpit Voice Chime Signal Contact 2 Data from Secondary IRS A Data from Secondary IRS B Resv Ext Reset Discrete Input Rsvd Mfr-Specific 0-28V Discrete Output A B Data from MCDU 1 A Data from MCDU 1 B C Call Place/End Discrete Input 1 D E F G SCM Pwr

+8 to 15V Multi-Control Multi-Control Output A Output B 1 2 3 4 5 6 7 8 9 Data from Primary IRS/GNSS A Data from Primary IRS/GNSS B Cockpit Voice Chime Signal Contact 1 SCM Pwr Return 0V Data from CMU 1 A Data from CMU 1 B Cockpit Voice Call Light Output 1 SDU Data to SCM A Cockpit Audio Input 1 High Cockpit Audio Output 1 High Cockpit Audio Input 1 Low Cockpit Audio Output 1 Low Spare or Chime/Lamps Inhibit Discrete Input Spare or Wifi Disable Discrete Input Cockpit Voice Mic-On Input 1 SDU Data to SCM B Cockpit Voice Go Ahead Chime Reset 1 Spare or LSWD Discrete Input SCM Data to SDU A SCM Data to SDU B AES ID Input A AES ID Input B Spare Discrete Input WOW Input 1 BITE Input A BITE Input B From HPA From HPA Spare/ACARS Service Avail. Discrete Output Spare/Slave TX Mute Discrete Output Spare Discrete Output Spare Discrete Input Spare Discrete Input Spare Discrete Input Ethernet 5 10 Ethernet T from CSDU to Prio. Data +

Ethernet 5 10 Ethernet T from CSDU to Prio. Data -

(ACD2) Ethernet 5

(ACD2) Ethernet 5 10 Ethernet T from Prio. Data 10 Ethernet T from Prio. Data to CSDU +

(ACD2) to CSDU -

(ACD2) Data from CFDS A Data from CFDS B BITE Input Top/Port BSU/Ant A BITE Input Top/Port BSU/Ant B Data Loader Link A TX Mute Input From Airborne A From Airborne B Crosstalk from other SDU A Crosstalk from other SDU B Dual System Dual System Select Discrete I/O Disable Discrete I/O Data Loader Data Loader 10 Data from MCDU 3 A Data from MCDU 3 B Port BSU HPA Mute Input A Port BSU HPA Mute Input B Cabin CEPT-E1 Data Output B 11 POTS 1 A POTS 1 B Cabin CEPT-E1 Data Output A 12 13 14 15 1T 1 Ethernet 3 from CSDU to ADL +

2 Ethernet 3 from ADL to CSDU +

4 Ethernet 3 from ADL to CSDU -

3 Ethernet 3 from CSDU to ADL -

(ACD) LGA LNA On/Off Control Service Availability Discretes 1 Service Availability Discretes 3 Service Availability Discretes 5 Service Availability Discretes 7 Service Availability Discretes 9 BITE Input from LGA LNA Service Availability Discretes 2 Service Availability Discretes 4 Service Availability Discretes 6 Service Availability Discretes 8 Service Availability Discretes 10 SPARE Cockpit Voice Call Light Output 2 Data from CMU 2 A Data from CMU 2 B AUDIO GND Cockpit Voice Mic-On Input 2 Data to EICAS/FWS A Data to EICAS/FWS B Cockpit Audio Input 2 High Cockpit Audio Output 2 High Cockpit Audio Input 2 Low Cockpit Audio Output 2 Low Spare ARINC 429 Input A Spare ARINC 429 Input B Data from GNSS to SDU A Data from GNSS to SDU B 429 Output 429 Output Spare ARINC BITE Input A A Spare ARINC BITE Input B B STBD BSU STBD BSU Data to CMU 1 & 2 A Data to CFDS A Data to CMU 1 & 2 B Data to CFDS B Crosstalk to other SDU A Crosstalk to other SDU B To Airborne Data Loader A To Airborne Data Loader B STBD BSU HPA Mute Input A Cabin CEPT-E1 Data Input A STBD BSU HPA Mute Input B Cabin CEPT-E1 Data Input B Data to MCDU 1, 2, 3 A Data to MCDU 1, 2, 3 B POTS 2 A POTS 2 B 2 Ethernet 4 from ACD1 to CSDU +

3 Ethernet 4 from CSDU to ACD1 -

1 Ethernet 4 from CSDU to ACD1 +

4 Ethernet 4 from ACD1 to CSDU -

(ACD) 2T Figure 4-11: CSDU Middle Plug in rear receptacle with pin functions 98-158751-C Chapter 4: Installation 4-27 Electrical installation and wiring 28V HOT 28V GND 2 4 7 9 8 No Connect 11 No Connect 10 No Connect No Connect 12 No Connect 5 115v HOT 115V COLD Chassis GROUND 1 3 6 DLNA Ant. Control Figure 4-12: CSDU Bottom Plug in rear receptacle with pin functions 4-28 Chapter 4: Installation 98-158751-C Electrical installation and wiring Pin-out for CSDU rear receptacle (top plug) Pin TP71 TP01A TP01B TP01C TP01D TP01E TP01F TP01G TP01H TP01J TP01K TP02A TP02B TP02C TP02D TP02E TP02F TP02G TP02H TP02J TP02K TP03A TP03B TP03C TP03D TP03E TP03F TP03G TP03H TP03J TP03K TP04A TP04B TP04C TP04D TP04E Pin name RF TX or RX/TX, to HPA ATE pin 1 ATE pin 2 ATE pin 3 ATE pin 4 ATE pin 5 ATE pin 6 (Spare Discrete Output #5) ATE pin 7 (ATE Pin A Discrete Input) ATE pin 8 (ATE Pin B Discrete Input) ATE pin 9 ATE pin 10 Empty Cavity Empty Cavity Empty Cavity ATE pin 14 ATE pin 15 ATE pin 16 ATE pin 17 ATE pin 18: Empty Cavity ATE pin 19: Empty Cavity ATE pin 20: Empty Cavity Ethernet 1 from CSDU to User + (AISD#1) Ethernet 1 from User to CSDU + (AISD#1) Empty cavity Config Pin 1 (0V Common) No Connect No Connect Config Pin 4 (SCM Presence) Empty Cavity Ethernet 11 from CSDU to EFB2+ (AISD#2) Ethernet 11 from EFB2 to CSDU+ (AISD#2) Ethernet 1 from EFB1 to CSDU - (AISD#1) Ethernet 1 from CSDU to EFB1 - (AISD#1) Empty cavity!

Config Pin 5 (SDU Number) No Connect Pin TP04F TP04G TP04H TP04J TP04K TP05A TP05B TP05C TP05D TP05E TP05F TP05G TP05H TP05J TP05K TP06A TP06B TP06C TP06D TP06E TP06F TP06G TP06H TP06J TP06K TP07A TP07B TP07C TP07D TP07E TP07F TP07G TP07H TP07J TP07K Pin name No Connect No Connect Empty Cavity Ethernet 11 from EFB2 to CSDU- (AISD#2) Ethernet 11 from CSDU to EFB2- (AISD#2) Empty Cavity Empty Cavity Empty Cavity No connect No connect No connect No connect Empty Cavity Empty Cavity Empty Cavity Ethernet 2 from CSDU to User+ (PIESD#1) Ethernet 2 from User to CSDU+ (PIESD#1) Empty Cavity No connect No connect No connect No connect Empty Cavity Ethernet 12 from CSDU to User+ (PIESD#2) Ethernet 12 from User to CSDU+ (PIESD#2) Ethernet 2 from User to CSDU- (PIESD#1) Ethernet 2 from CSDU to User- (PIESD#1) Empty cavity No connect No connect No connect No connect Empty Cavity Ethernet 12 from User to CSDU- (PIESD#2) Ethernet 12 from CSDU to User- (PIESD#2) Table 4-5: Pin allocation for the CSDU top plug 98-158751-C Chapter 4: Installation 4-29 Electrical installation and wiring Pin-out for CSDU rear receptacle (middle plug) Pin MP01A MP01B MP01C MP01D MP01E MP01F MP01G MP01H MP01J MP01K MP02A MP02B MP02C MP02D MP02E MP02F MP02G MP02H MP02J MP02K MP03A MP03B MP03C MP03D MP03E MP03F MP03G MP03H MP03J MP03K MP04A Pin name and description Data from MCDU 1 A Data from MCDU 1 B Call Place End Discrete Input 1 SCM Power output 15 V Multi Control output A429 High Multi Control output A429 Low Ext Reset Discrete Input Call Place End discrete Input 2. Data from MCDU 2 A Data from MCDU 2 B Data from Primary IRS/ GNSS A Data from Primary IRS/ GNSS B Cockpit Voice Chime signal contact 1 SCM Power return 0 V No Connect No Connect No Connect Cockpit Voice Chime Signal Contact 2 Data from Secondary IRS A Data from Secondary IRS B Data from CMU 1 A Data from CMU 1 B Cockpit Voice Call Light output 1 Data to SCM A ACARS Service available discrete output No Connect No Connect Cockpit Voice Call Light output 2 Data from CMU 2 A Data from CMU 2 B Cockpit audio input 1 High Pin MP04B MP04C MP04D MP04E MP04F MP04G MP04H MP04J MP04K MP05A MP05B MP05C MP05D MP05E MP05F MP05G MP05H MP05J MP05K MP06A MP06B MP06C MP06D MP06E MP06F MP06G MP06H MP06J MP06K Pin name and description Cockpit audio input 1 Low Cockpit Voice Mic On Input 1 SDU Data to SCM B Spare No Connect Audio Ground Cockpit Voice Mic On input 2 Cockpit audio input 2 High Cockpit audio input 2 Low Cockpit audio output 1High Cockpit audio output 1Low Cockpit Voice Go Ahead Chime reset 1 SCM Data to SDU A Spare discrete output #3 No Connect Spare ARINC 429 Output #1 A Spare ARINC 429 Output #1 B Cockpit Audio Output 2 High Cockpit Audio Output 2 Low Chime/Lamps Inhibit Discrete input Spare Spare SCM Data to SDU B Ethernet 5 Ethernet F from SDU to User+

(ACD2) Ethernet 5 Ethernet F from SDU to User-

(ACD2) Spare ARINC 429 Input A. Spare ARINC 429 Input B. Data from GNSS to SDU A Data from GNSS to SDU B Table 4-6: Pin allocation for the CSDU middle plug 1/2 4-30 Chapter 4: Installation 98-158751-C Pin name and description AES ID input A AES ID input B Spare discrete input #4 Pin MP07A MP07B MP07C MP07D WOW input 1 MP07E Ethernet 5, Ethernet T from User to SDU+

(ACD2) Ethernet 5, Ethernet T from User to SDU-

(ACD2) Spare ARINC 429 Output #2 A - Not Used Spare ARINC 429 Output #2 B - Not Used Data to CMU 1 & 2. A Data to CMU 1 & 2. B Data from CFDS A Data from CFDS B BITE Input Top/Port BSU/Ant A BITE Input Top/Port BSU/Ant B Data loader link A TX mute input Spare Arinc input A Spare Arinc input B Data to CFDS A Data to CFDS B From airborne data loader A. From airborne data loader B Crosstalk from other SDU A Crosstalk from other SDU B Dual System Select Discrete I/O Dual System Disable Discrete Input Crosstalk to other SDU A Crosstalk to other SDU B To airborne data loader A To airborne data loader B Data from MCDU 3 A Data from MCDU 3 B Data from BSU HPA Mute A MP07F MP07G MP07H MP07J MP07K MP08A MP08B MP08C MP08D MP08E MP08F MP08G MP08H MP08J MP08K MP09A MP09B MP09C MP09D MP09E MP09F MP09G MP09H MP09J MP09K MP10A MP10B MP10C Electrical installation and wiring Pin MP10D MP10E MP10F MP10G MP10H MP10J MP10K MP11A MP11B MP11C MP11D MP11E MP11F MP11G MP11H MP11J MP11K MP12E MP12F MP13E MP13F MP14E MP14F MP15E MP15F MP1T 1 MP1T 2 MP1T 3 MP1T 4 MP2T 1 MP2T 2 MP2T 3 MP2T 4 Pin name and description Data from BSU HPA Mute B LGA LNA On/Off Control discrete output BITE Input from LGA LNA Data from STBD BSU HPA Mute A Data from STBD BSU HPA Mute B Data to MCDU 1, 2, 3 A Data to MCDU 1, 2, 3 B POTS1 A (TIP) (Spare-Not used) POTS1 B (RING) (Spare-Not used) No Connect No Connect Service Availability Discretes 1 Service Availability Discretes 2 No Connect No Connect POTS 2. A (TIP) (Spare-Not used) POTS 2 B (RING) (Spare-Not used) Service Availability Discretes 3 Service availability discretes 4. Discrete output. System fail. No Connect No Connect No Connect No Connect No Connect No Connect Ethernet 3 from CSDU to ADL + (ACD) Ethernet 3 from ADL. to CSDU + (ACD) Ethernet 3 from CSDU to ADL - (ACD) Ethernet 3 from ADL to CSDU - (ACD) Ethernet 4 from CSDU to ACD1 + (ACD1) Ethernet 4 from ACD1 to CSDU + (ACD1) Ethernet 4 from CSDU to ACD1 - (ACD1) Ethernet 4 from ACD1 to CSDU - (ACD1) Table 4-7: Pin allocation for the CSDU middle plug 2/2 98-158751-C Chapter 4: Installation 4-31 Electrical installation and wiring Pin-out for CSDU rear receptacle (bottom plug) Pin name and description 115 V COLD. 115 VAC power return 28 V HOT. 28 VDC power (No Connect - Provision only) Chassis Ground 28 V GND. 28 VDC power return (No Connect - Provision only) 115V HOT. 115 VAC power No Connect DLNA No Connect Pin BP1 BP2 BP3 BP4 BP5 BP6 BP7 BP8 BP9 BP10 BP11 BP12 4-32 Chapter 4: Installation 98-158751-C Electrical installation and wiring 4.3.27 MCHPA ARINC 600 connector block ARINC 600 connector drawing - overview Figure 4-13: MCHPA ARINC 600 connector specifications Note Other pins are not used by MCHPA. 98-158751-C Chapter 4: Installation 4-33 Electrical installation and wiring Pin-out for MCHPA rear receptacle (top plug) Pin TP71 TP01A TP01B TP01C TP01D TP01E TP01F TP01G TP01H TP01J TP01K TP02A TP02B TP02C TP02D TP02E TP02F TP02G TP02H TP02J TP02K TP03A TP03B TP03C TP03D TP03E TP03F TP03G TP03H TP03J TP03K TP04A TP04B TP04C TP04D TP04E Pin name RF IN from CSDU No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No Connect Pin TP04F TP04G TP04H TP04J TP04K TP05A TP05B TP05C TP05D TP05E TP05F TP05G TP05H TP05J TP05K TP06A TP06B TP06C TP06D TP06E TP06F TP06G TP06H TP06J TP06K TP07A TP07B TP07C TP07D TP07E TP07F TP07G TP07H TP07J TP07K Pin name No Connect No Connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect Factory use only Factory use only Factory use only No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect Table 4-8: Pin allocation for the MCHPA top plug 4-34 Chapter 4: Installation 98-158751-C Pin-out for MCHPA rear receptacle (middle plug) Electrical installation and wiring Pin name RF OUT to DLNA Pin MP71 MPMP01A No connect MP01B No connect No connect MP01C No connect MP01D MP01E No connect No connect MP01F No connect MP01G MP01H No connect No connect MP01J No connect MP01K MP02A No connect No connect MP02B No connect MP02C MP02D No connect No connect MP02E No connect MP02F MP02G No connect No connect MP02H No connect MP02J MP02K No connect No connect MP03A No connect MP03B No connect MP03C MP03D No connect No connect MP03E No connect MP03F MP03G No connect No connect MP03H No connect MP03J MP03K No connect No connect MP04A No connect MP04B MP04C No connect No connect MP04D MP04E No Connect Pin MP04F MP04G MP04H MP04J MP04K MP05A MP05B MP05C MP05D MP05E MP05F MP05G MP05H MP05J MP05K MP06A MP06B MP06C MP06D MP06E MP06F MP06G MP06H MP06J MP06K MP07A MP07B MP07C MP07D MP07E MP07F MP07G MP07H MP07J MP07K Pin name No Connect No Connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect Factory use only Factory use only Factory use only No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect Table 4-9: Pin allocation for the MCHPA middle plug 98-158751-C Chapter 4: Installation 4-35 Electrical installation and wiring Pin-out for MCHPA rear receptacle (bottom plug) Pin name and description 115 V HOT. 115 VAC power 115 V COLD. 115 VAC power return Chassis Ground No Connect Pin BP1 BP7 BP8 BP2 BP3 BP4 BP5 BP6 BP9 BP10 BP11 BP12 BP13 4-36 Chapter 4: Installation 98-158751-C Recommended cables 4.4 4.4.1 Recommended cables Introduction This section lists recommended cables and allowed cable lengths for the cables in the AVIATOR 700S system. Important For specific cable requirements see the applicable section in 4.3 Electrical installation and wiring. 4.4.2 Allowed cable lengths for power cables Cable type: unshielded Allowed cable lengths for CSDU The following table can be used to calculate the allowed CSDU cable lengths for selected AWG types. Note It is generally recommended to keep cable lengths as short as possible, specially on cables for Chassis GND. Description Pin Contact size 115 VAC Line BP1 16 BP5 12 115 VAC Neutral Chassis BP3 12 Total maximum resistance (Hot and cold) 650 m 1 -350 m in circuit breaker 25 m

(Max. 1 m) x = not suitable for this contact size. Example m/m (at 70C) AWG12 AWG14 AWG16 AWG18 AWG20 x 5.7 5.7 x 9 9 14.3 x x 22.9 x x 36.3 x x Requirement for maximum total resistance: 650 m Selected wire for Line: AWG 16 (14.3 m/m) Selected wire for Neutral: AWG 12 (5.7 m/m) 650m Maximum length

14 3m m 5 7m

32,5m 98-158751-C Chapter 4: Installation 4-37 Recommended cables 4.4.3 4.4.4 4.4.5 4.4.6 4.4.7 Recommended power cables The cable types must meet the following standards:

M27500 for shielded wire. M22759 for single wire. AC Power:

Single unshielded wire 18 AWG (Hot) & 12 AWG (Cold) Manufacturer: Carlisle (Thermax) MIL-DTL-22759/86-18 Manufacturer: Carlisle (Thermax) MIL-DTL-22759/86-12 Recommended RF cables Recommended cables for AVIATOR 700S must be compliant with ARINC Characteristic 781-7 [3]. Recommended cables for ARINC 429 The cables for the ARINC 429 interfaces must be twisted and shielded. They must conform to the standards for aeronautical use. Use a cable that meets the following standard:

M27500 for shielded wire The cables for the ARINC 429 interfaces must be twisted and shielded and conform to the standards for aeronautical use. ARINC-429 Data Bus Cable 2 Conductor 24AWG shielded Manufacturer: Carlisle (ECS) P/N 522402 Recommended cables for Ethernet Use an Ethernet cable that meets one of the following standards:

TIA/EIA568-A CAT5 Requirements FAR 25.869(a) The following cable types meet the requirements:

100ohm +-10%, 13pF/ft, 24 AWG shielded Manufacturer: Carlisle (Tensolite) P/N NF24Q100-01 100Base-T Ethernet Cable Recommended cables for discrete signals Use cables for discrete wiring that meet the following standard:

M27500 for shielded wire 2 Conductor Cable 22 AWG shielded Manufacturer: Carlisle (Thermax) M27500-22 WJ 2 S 24 4-38 Chapter 4: Installation 98-158751-C Verifying the installation 4.4.8 4.5 4.6 Recommended cable between the SCM and the CSDU Use the following cables to connect the SCM to the CSDU:

Communication cable (LAN). Data to and from the SCM: Carlisle (Tensolite) 100Base-T Ethernet Cable, 100 Ohm 10%, 13 pF/ft, AVG24 Part number: NF24Q100-01 Twisted pair shield cable for power source and power return: Carlisle (Thermax) M27500-22 WJ 2 S 24 (MIL-DTL-22759/86 wire), silver plated shield Verifying the installation You must perform certain check procedures during and after installation of the AVIATOR 700S system. The first check procedures are performed after wiring, but before inserting LRUs.For information on the required and recommended check procedures, refer to Verification on page 6-1. Activation of airtime services Before the AVIATOR 700S system becomes operational, the aircraft owner or operator must establish a contract with an Inmarsat Service Provider (ISP) so the system can be activated. The airtime provider handles terminal activation, billing and technical support that is related to the communication network. The activation process may take some time, so to make sure it is ready in time, start the activation procedure some time before the installation on the aircraft begins. 4.6.1 ID numbers for the AVIATOR 700S system ICAO address / AES ID The ICAO address (International Civil Aviation Organization) is unique and assigned to an aircraft by the civil aviation authority of the state in which the aircraft is registered. This number is the same number used for the Mode S transponder and the TCAS system and in some countries it's calculated from the tail no. In the Inmarsat world, this is also referred to as the AES ID (Airborne Earth Station ID). The ICAO address is normally noted in Oct (octal), but in some cases Hex is also used. The CSDU has an ARINC-429 compliant AES ID input for reception of a unique aircraft identification code. ARINC 600 connector, rear receptacle, middle plug: MP07A, MP07B. Label 275 and 276 The ICAO address can also be received from the CMU (label 214 and 216). IMSI The IMSI (International Mobile Subscriber Identity) is the ID for the SwiftBroadband service and is tied to the SDU Configuration Module (SCM). 98-158751-C Chapter 4: Installation 4-39 Activation of airtime services SwiftBroadband USIM cards The AVIATOR 700S system is delivered with four USIM cards permanently installed in the SCM. The USIM cards are pre-authenticated by Inmarsat and identified by their unique IMSI (International Mobile Subscriber Identity) number. The length of the IMSI is 15 digits. The SCM is delivered with the USIM cards not yet activated for SwiftBroadband services. For details how to activate the USIM cards contact your airtime provider. The IMSI number is needed to activate the satellite communication service. A fifth card is a Security SmartCard. The SCM is delivered with all five cards installed and these cannot be replaced in the field. The contract for SwiftBroadband services with your airtime provider contains among other items the following phone number: Direct phone numbers that is associated with the IMSI numbers of the installation. Typically the service provider provisions the USIMs for both circuit switched and packet switched services. Service providers You find a list of Service providers on Inmarsats web site under Aviation, Aviation Connectivity

((https://www.inmarsat.com/aviation/complete-aviation-

connectivity/). services To retrieve the USIM card ID (IMSI number) With the system you receive the IMSI numbers of the USIM cards that are installed in the SCM. Important The USIM cards are permanently installed in the SCM. Do not remove or replace the USIM cards. Note The IMSI numbers are printed on a label on the SCM enclosure and printed on the Certificate of Conformity letter belonging to the SCM. 4-40 Chapter 4: Installation 98-158751-C Chapter 5 5 Setup of the system This chapter has the following sections:

Software upload SATCOM system ready for use Note Line of sight You can configure the system while the aircraft is in the hangar. Note that you cannot typically check the satellite communication while the aircraft is still in the hangar. There must be a line of sight between the SATCOM antenna and the satellite in order to register and use the satellite service. 5.1 5.1.1 Antenna Figure 5-1: Line of sight when communicating with the satellite Software upload Overview After the physical installation of the system it must be loaded with the following files:

Software image for the system, i.e. CSDU, SCM and MCHPA (typically factory loaded) Secure ORT (Owner Requirements Table) User ORT Software image files should only be loaded via Ethernet (ARINC 615A) data loader as an ARINC 429 data loader (A615-3) would require more than 2 hours. All ORT files are loaded using an ARINC 429 or Ethernet (A615A) data loader. The software image makes the system ready for configuration to the specific aircraft installation and application requirements. The ORT files contain the settings for the individual aircraft. The Secure ORT contains all aircraft specific settings. The User ORT contains user data, e.g. a telephone directory. 98-158751-C 5-1 SATCOM system ready for use Secure ORT The Secure ORT contains all settings for the connected units, including the antenna setup, cable losses and navigational input, interfaces to connected avionics equipment (e.g. CMU, MCDU, audio management panels etc.). This file is locked and cannot be edited. The Secure ORT file is generated with an ORT tool and loaded using an ARINC 429

(ARINC 615-3) or Ethernet (ARINC 615A) compliant data loader. User ORT The User ORT can be edited using the ORT tool (refer to ORT Tool User Guide (99-

168498) [9]), you can add a telephone directory. The User ORT file is loaded using an ARINC 429 (ARINC 615-3) or Ethernet (ARINC 615A) compliant data loader. 5.1.2 Uploading software Note Note Before you start loading the software files, make sure that the SCM is connected to the CSDU. Software upload should only be done by qualified personnel. To upload software, do as follows:

1. Make sure you have access to the following files:

Software image for each LRU, i.e. CSDU and MCHPA (typically factory loaded) Secure ORT (Owner Requirements Table) User ORT 2. Upload the files using a compliant data loader, see the data loaders instruction manual. 5.2 SATCOM system ready for use Having installed the AVIATOR 700S system and loaded the necessary software, verify that the system is fully operational. Note Line of sight during operation!

Make sure that there is a line of sight between the SATCOM antenna and the satellite in order to logon to and use the SATCOM service. To verify the system, refer to chapter 6, Verification. 5-2 Chapter 5: Setup of the system 98-158751-C Chapter 6 6 Verification This chapter has the following sections:

Basic check flow Pre-Installation Check Functional Test, on Ground Functional test, airborne Interference Test 6.1 Basic check flow Important None of the check procedures described in this chapter can serve as a replacement for any of the required approvals and certifications. 6.1.1 Check procedures In order to ensure the correct function of the system, follow the below check flow. 1. Pre-Installation Check. Perform this check after wiring, but before inserting the LRUs. This is a check of the most important connections, the circuit breakers, cable losses etc. Refer to Pre-Installation Check on page 6-2. 2. Configuration. After performing the Pre-Installation Check, load the Secure ORT and the User ORT files. Refer to Setup of the system on page 5-1. 3. Functional Test, on Ground. When the system is configured and activated, make a functional test on ground. The functional test should check all user interfaces, such as voice, data, annunciators, etc. Refer to Functional Test, on Ground on page 6-3. 4. Interference Test. After the functional test, make an interference test. This test is to verify that transmission from the AVIATOR 700S system has no effect on the avionics of the aircraft, particularly navigation equipment. Refer to Interference Test on page 6-4. If additional avionics are installed in the aircraft at a later stage, repeat the interference test to ensure compatibility. Note 5. Functional Test, Airborne. After the interference test, do a functional test while the aircraft is airborne. This test is basically the same as the functional test on ground. Refer to Functional test, airborne on page 6-5. 98-158751-C 6-1 Pre-Installation Check 6.2 Pre-Installation Check It is recommended to check the installation before inserting LRUs. The following list provides some of the most important issues, but other additional checks may be relevant for the specific installation. Item Description of Check Reference Section Value/

Comment Mounting trays Coding of tray connectors Grounding stud Circuit breaker rating AC power Ensure service/maintenance accessibility. Check orientation of coding pins in both CSDU and MCHPA tray connectors Check that the grounding stud on both CSDU and MCHPA are connected correctly to the aircraft chassis. Check the circuit breaker. Check AC power on CSDU tray connector BP5: +115 VAC Line (Hot) BP1: +115 VAC Neutral (Cold) Check AC power on MCHPA tray connector BP1: +115 VAC Line (Hot) BP7: +115 VAC Neutral (Cold) RF cable losses Measure and note the cable loss for all coaxial cables. See section 4.4.4. Software version Check the software version of the CSDU and the MCHPA. Table 6-1: Check Sheet: Installation Check before inserting LRUs. After a successful check of the installation, you must load the secure ORT and the user ORT with a data loader. For further information, refer to Setup of the system on page 5-1. 6-2 Chapter 6: Verification 98-158751-C Functional Test, on Ground 6.3 6.3.1 6.3.2 Functional Test, on Ground Before you start The system must be activated before performing this test. For further details see Activation of airtime services on page 5-49. Check list for functional test on ground The following list provides some of the most important checks to perform after power-up, but other additional checks may be relevant for the specific installation. If you already know that certain interfaces or services are not going to be used, it is not necessary to perform tests on these specific interfaces or services. Item Description of Check Reference Value/

Comment CSDU LEDs MCDU headsets #1 to

#3 Ethernet ACARS /

AFIS / CMU Check that the Power LED is green Check that the Fail/Pass LED is green Check that the Logon LED is green Make an aircraft to ground call Make a ground to aircraft call AVIATOR 700S User Manual [7]

AVIATOR 700S User Manual [7]

AVIATOR 700S User Manual [7]

AVIATOR 700S User Manual [7]

Connect to the Internet from a laptop, using the Ethernet AISD 1 / EFB 1 connection. Connect to the Internet from a laptop, using the Ethernet PIESD 1 / Cabin 1 connection. Send a test message and verify the reply or request for weather data and verify the data is downloaded. Both is done from the CDU / MCDU. Table 6-2: Check Sheet: Functional test, on Ground CDU / MCDU Manual [7]

98-158751-C Chapter 6: Verification 6-3 Interference Test 6.4 6.4.1 6.4.2 Interference Test Introduction It is recommended to do an interference test to ensure that transmission from the AVIATOR 700S system does not influence any of the primary avionics on the aircraft. Important This test is not a replacement for any EMC tests in connection with e.g. an STC (Supplemental Type Certificate), TC (Type Certificate) or Field Approval. It is only an additional practical test of the application. Test procedure During the test, the aircraft must be on ground. A skilled person should be observing the instruments. Important Make sure that all possible avionics/equipment are powered on when A/C in ground state. 1. Determine the approximate location and direction towards the relevant satellite to be used. 2. Position the aircraft so that the SATCOM antenna transmits in the direction of the other antennas on the aircraft. Example:

If the satcom antenna is tail-mounted, place the aircraft with the nose pointing in the direction of the satellite. The antenna will then transmit in the direction of the other antennas located in front of it. 3. You can establish a transmission by, for example, making a video call or sending a large file via a laptop that is connected to the EFB 1 Ethernet interface. 4. While transmission is ongoing, observe all primary navigation instruments, autopilot, VOR/ILS, ADF and DME etc. and make sure none of the instruments are influenced by the AVIATOR 700S transmission. 5. Check aircraft GPS signal-to-noise ratio. 6. Monitor all VHF communication and make sure squelch is not opened unintentionally. 7. If TCAS/ACAS is installed, verify that it is not flagged FAILED during SATCOM transmission. Note If any additional avionics are installed at a later stage, do the interference test again. 6-4 Chapter 6: Verification 98-158751-C Functional test, airborne 6.5 6.5.1 Functional test, airborne The following list provides some of the most important checks to do while the aircraft is airborne, after all on-ground tests are passed. Other additional checks may be relevant for the specific installation. Before you start If you already know that certain interfaces or services are not going to be used, it is not necessary to perform tests on these specific interfaces or services. 6.5.2 Check list for functional test, airborne Item Description of Check Reference Value/

Comment MCDU headsets #1 to #2 Make an air to ground call and keep it up during a 360 turn. Make a ground to air call Ethernet ACARS /

AFIS / CMU Connect to the Internet from a laptop, using the Ethernet connection. Send a test message and verify reply or request for weather data and verify the data is downloaded. Both is done from the CDU / MCDU. AVIATOR 700S User Manual [7]

AVIATOR 700S User Manual [7]

AVIATOR 700S User Manual [7]

CDU / MCDU Manual [7]

Table 6-3: Check Sheet: Functional test, Airborne 98-158751-C Chapter 6: Verification 6-5 Functional test, airborne 6-6 Chapter 6: Verification 98-158751-C Chapter 7 Maintenance and troubleshooting 7 This chapter has the following sections:

Continued Airworthiness Helpdesk Software update To exchange an LRU Troubleshooting Returning units for repair Disposal of electrical and electronic equipment 7.1 Continued Airworthiness 7.1.1 General Maintenance Maintenance requirements and instructions for continued airworthiness of the Cobham Aerospace Communications units in the AVIATOR 700S System are defined here. The AVIATOR 700S System (CSDU, SCM and MCHPA) requires no periodic scheduled servicing tasks. Note When replacing the CSDU, it is important to leave the SCM installed in the aircraft, because the SCM contains the aircraft-specific configuration data. The CSDU is a Line-Replaceable Unit (LRU) and constructed for factory repair only. Defective units must be returned to the factory for investigation, repair and test. The SCM is a Line-Replaceable Unit (LRU) and constructed for factory repair only. Defective units must be returned to the factory for investigation, repair and test. The MCHPA is a Line-Replaceable Unit (LRU) and constructed for factory repair only. Defective units must be returned to the factory for investigation, repair and test. See also the installation manual of the HGA and DLNA, refer to [8]. 98-158751-C 7-1 Continued Airworthiness Technical support Web address: https://www.cobhamaerospacecommunications.com/en/contact-us/

E-mail to Cobham technical support: CAC.Customersupport@cobham.com. Telephone numbers for technical support:

EMEA: +27(78) 458 7412 or +33(0) 6 75 79 20 15 (8am to 4 pm, European Time Zone) Americas: +1 (757) 753-2098 (8am to 5 pm, Eastern Time) Technical Training E-mail to Cobham technical support: CAC.Customersupport@cobham.com. AOG desk OEM Services Telephone: +33 1 72 02 23 23 E-mail: aog@oemservices.aero 7.1.2 Maintenance instructions Documentation Maintenance information for the AVIATOR 700S System is contained in this manual. Place the wiring diagram information in this manual in the aircraft operator's appropriate aircraft wiring diagram manuals. Inoperative units If a system component is inoperative, remove or replace the unit. Secure all cables, collect applicable switches and circuit breakers, and label them inoperative. Revise the equipment list and weight and balance as applicable prior to flight and make a log book entry that the unit was removed. For information on how to return a unit for repair, see Returning units for repair on page 7-10. Once repaired, reinstall the unit in the aircraft in accordance with the instructions in this Installation and Maintenance Manual. Scheduled Maintenance Program The AVIATOR 700S System components are considered on-condition units and no additional maintenance is required other than a check for security and operation at normal inspection intervals. The recommended periodic scheduled maintenance tasks to be added to the aircraft operator's appropriate aircraft maintenance program are as follows:

CSDU Not required Table 7-1: Periodic scheduled maintenance tasks 7-2 Chapter 7: Maintenance and troubleshooting 98-158751-C Continued Airworthiness SCM MCHPA Not required Not required Table 7-1: Periodic scheduled maintenance tasks The recommended periodic scheduled inspection tasks to be added to the aircraft operator's appropriate aircraft maintenance program are as follows:

CSDU SCM MCHPA Not required Not required Not required Table 7-2: Periodic scheduled inspection tasks The recommended periodic scheduled preventative maintenance tasks to be added to the aircraft operator's appropriate aircraft maintenance program are as follows:

(Tests to determine system condition and latent failures) CSDU SCM MCHPA Not required Not required Not required Table 7-3: Periodic scheduled preventative maintenance tasks 98-158751-C Chapter 7: Maintenance and troubleshooting 7-3 Helpdesk 7.2 7.2.1 7.2.2 Helpdesk If this manual does not provide the remedies to solve your problem, you may want to contact your Airtime Provider or your local distributor. System support If you need assistance with problems caused by the CSDU, SCM or MCHPA, call a distributor in your area. See Technical support on page 7-2. Security log and system log files For instructions how to retrieve security and system log files, see the AVIATOR S Operational User Guidance [10]. 7-4 Chapter 7: Maintenance and troubleshooting 98-158751-C Software update 7.3 7.4 7.4.1 7.4.2 Software update See Software upload in chapter 5. To exchange an LRU This document describes the procedures for removal and re-installation of the AVIATOR 700S LRUs:

CSDU (405045-vvccc). SCM (405055-vvccc). MCHPA (405015-vvccc). Time required The time required for removal and re-installation of an LRU is estimated to 15 minutes. Tools required CSDU: No tools required. SCM: No special tools required. Screw driver if fixed with a screw or bolt. 7.4.3 Removal and re-installation of the CSDU (SDU-5045) Removal To remove the CSDU do as follows:

1. Ensure that power is removed from the SATCOM system before removing any LRU. 2. Pull and turn to loosen the knurled knob(s) that retain(s) the LRU in the tray. 3. Pull the LRU straight out from the tray by the handle. Be careful not to drop the unit. Re-installation To re-install the CSDU do as follows:

1. Insert the LRU straight in the tray by the handle. Be careful not to drop the unit. 2. Make sure that the LRU is completely seated against the mating connector. 3. Pull and turn to fasten the knurled knob(s) that retain(s) the LRU in the tray. 98-158751-C Chapter 7: Maintenance and troubleshooting 7-5 To exchange an LRU 7.4.4 Removal and re-installation of the SCM (SCM-5055) Removal 1. Ensure that power is removed from the SATCOM system before removing the SCM. 2. Release the screw-locks on the D-sub connector and remove the 15 pin D-sub connector from the SCM. 3. Remove the four fasteners holding the SCM in place through its mounting flange. Re-installation 1. Mount the SCM to the aircraft structure with the four fasteners through its mounting flange.SCM. 2. Connect the 15 pin D-sub connector to the SCM and tighten the connector screw-locks to 0.32 Nm. 7.4.5 Removal and re-installation of the MCHPA (HPA-5015) Removal To remove the MCHPA do as follows:

1. Ensure that power is removed from the SATCOM system before removing any LRU. 2. Pull and turn to loosen the knurled knob(s) that retain(s) the LRU in the tray. 3. Pull the LRU straight out from the tray by the handle. Be careful not to drop the unit. Re-installation To re-install the MCHPA do as follows:

1. Insert the LRU straight in the tray by the handle. Be careful not to drop the unit. 2. Make sure that the LRU is completely seated against the mating connector. 3. Pull and turn to fasten the knurled knob(s) that retain(s) the LRU in the tray. 7-6 Chapter 7: Maintenance and troubleshooting 98-158751-C Troubleshooting 7.5 Troubleshooting 7.5.1 Status signalling Built-In Test Equipment (BITE) The CSDU provides a Built-In Test Equipment (BITE) function in order to make fault diagnostics easy during service and installation. The BITE test is done during:

Power On Self Test (POST), which is automatically performed each time the system is powered on. Person Activated Self Test (PAST), which is initiated by pressing the Push To Test button on the front panel of the CSDU. Also, during operation a Continuous Monitoring BITE function is performed. Each LRU in the AVIATOR 700S system has its own BITE function but they are all controlled and monitored by the CSDU in the system. Results from the BITE tests for the complete AVIATOR 700S system are shown as four digit error codes. The two most significant digits represent the main group. The two least significant digits give further details. The CSDU BITE codes inform you that there are errors in the CSDU. Use the CSDU diagnostic report for further information on the BITE errors. Means of signalling The AVIATOR 700S System provides various methods for signalling the status of the system. LEDs on the front panel of the CSDU are used to signal:

Power on/off Logon Fail/Pass Connected display units (e.g. MCDU) display messages concerning:

information from the services status information from the system to the user equipment errors. Security and system log files: In Maintenance allowed mode. Messages in the MCDU display Two types of messages are displayed:

Cause codes are information from the services or status information from the system to the user. BITE codes are information about errors in the equipment. For further information and lists of the possible error codes, refer to the appendix System messages on page B-1. 98-158751-C Chapter 7: Maintenance and troubleshooting 7-7 Troubleshooting 7.5.2 Status signalling with LEDs LEDs on CSDU During the power-up procedure all LEDs on the front plate are orange. If all 3 LEDs on the front stay orange after power up, check the AC supply of the CSDU. If the wiring is good, the CSDU software may be corrupted. If the wiring is good, the CSDU software is corrupted. Contact your local distributor for instructions how to proceed. Logon LED on CSDU Behaviour Description Red Orange Green Off Acquiring satellite network Network synchronization Network logon No acquired satellite/logged off Table 7-4: Function of the CSDU Logon LED Fail/Pass LED on CSDU Behaviour Steady red Description A fault which may degrade the system operation is present in the SDU Flashing: short green/ long pause Power On Self Test (POST) or Person Activated Self Test (PAST) in progress Flashing: long green/ short orange No current failure, but a BITE failure / warning is logged in the error log Steady green No faults Table 7-5: Function of the CSDU Fail/Pass LED 7-8 Chapter 7: Maintenance and troubleshooting 98-158751-C Troubleshooting 7.5.3 Initial troubleshooting Overview This section describes an initial check of the primary functions of the AVIATOR 700S System, and provides some guidelines for troubleshooting, if one of the checks should fail. Means available for troubleshooting The following means are available for troubleshooting:

LEDs and BITE messages. Generally, if a fault occurs without any obvious reason, it is always recommended to observe the LED behaviour. For information on the function of the LEDs refer to Status signalling on page 7-7. For a list of all the BITE codes and Cause codes, refer to the appendix System messages on page B-1. Maintenance interface. For troubleshooting errors in the CSDU, connect to the Micro USB maintenance port on the front plate of the CSDU and extract the relevant log files. Refer to the Operational User Guidance [10] for instructions how to extract and analyze the log files. Problem No GPS signal:

Interference from satcom antenna on GPS antenna Registration for voice or data on the BGAN network not possible What to do If the existing GPS antenna on board the aircraft does not provide sufficient filtering of the satcom antenna signal to provide a usable GPS signal, you must replace the existing GPS antenna with a GPS antenna that has a satcom filter. In case the system cannot register properly for voice or data service, check with your Service provider that the USIM cards in the SCM are not blocked. Table 7-6: Initial troubleshooting 98-158751-C Chapter 7: Maintenance and troubleshooting 7-9 Returning units for repair 7.6 7.6.1 Returning units for repair Repackaging requirements Should you need to send the product for repair, please read the below information before packing the product. The shipping carton has been carefully designed to protect the AVIATOR 700S and its accessories during shipment. This carton and its associated packing material should be used when repacking for shipment. Attach a tag indicating the type of service required, return address, part number and full serial number. Mark the carton FRAGILE to ensure careful handling. Note Correct shipment is the customers own responsibility. If the original shipping carton is not available, the following general instructions should be used for repacking with commercially available material. Note The packaging must meet at least ATA 300 CATEGORY III. 1. Protect the connectors of the CSDU, MCHPA and SCM with plastic connector protection. 2. Wrap the defective unit in heavy paper or plastic. Attach a tag indicating the type of service required, return address, part number and full serial number. 3. Use a strong shipping container, e.g. a double walled carton. 4. Protect the front- and rear panel with cardboard and insert a layer of shock-absorbing material between all surfaces of the equipment and the sides of the container. 5. Seal the shipping container securely. 6. Mark the shipping container FRAGILE to ensure careful handling. Failure to do so may invalidate the warranty. 7-10 Chapter 7: Maintenance and troubleshooting 98-158751-C Disposal of electrical and electronic equipment 7.7 Disposal of electrical and electronic equipment Old electrical and electronic equipment marked with this symbol can contain substances hazardous to human beings and the environment. Never dispose these items together with unsorted municipal waste (household waste). In order to protect the environment and ensure the correct recycling of old equipment as well as the re-utilization of individual components, use either public collection or private collection by the local distributor of old electrical and electronic equipment marked with this symbol. Contact the local distributor for information about what type of return system to use. 98-158751-C Chapter 7: Maintenance and troubleshooting 7-11 Disposal of electrical and electronic equipment 7-12 Chapter 7: Maintenance and troubleshooting 98-158751-C Appendix A Equipment specifications A A.1 Introduction This appendix has the following sections:

SDU-5045 Compact Satellite Data Unit SCM-5055 Configuration Module HPA-5015 Multi-Carrier High Power Amplifier Important note!

The information, drawings, and wiring diagrams contained in this manual are intended as a reference for engineering planning only. It is the installers responsibility to compose installation drawings specific to the aircraft. Cables and connectors are not included. For specifications of the antenna see the documentation provided with the antenna. 98-158751-C A-1 SDU-5045 Compact Satellite Data Unit A.2 SDU-5045 Compact Satellite Data Unit Characteristics Dimensions

(L x W x H) Weight Mounting Supply voltage Specification 2 MCU ARINC 600 enclosure 319.50 mm x 61.00 mm x 199.70 mm (12.58" x 2.40"

x 7.86") 4.2 kg (9.26 lbs) Guaranteed weight max 4.4 kg (9.7 lbs) Mount in an ARINC 600 2 MCU tray. Controlled-temperature locations and convection airflow cooling Non-controlled-temperature locations and forced airflow cooling (Tray with fan/plenum) Non-controlled-temperature location and supplied airflow cooling (tray integrated onto a shelf racking system) Non-pressurized locations. Pressurized locations. Nominal AC supply: 115 VAC (360 - 800Hz) Continuous operation: +90 V to 134 V Short time operation: +70.0 V - 170 V (30ms) Transparency time 200 ms Typical Power Consumption:

CSDU alone in a Class 6 system

(AVIATOR 700S) AC: 44 W Power provided for SCM: 4.5 W Maximum heat dissipation

<50 W Connectors Rear: ARINC 600 Attachment 11 Front: micro USB (for maintenance). Operating temperature Convection airflow cooling Forced airflow cooling Supplied airflow cooling

-40 to +40 C (+40C/20 hours; +55C/30 minutes)

-40 to +70 C

-40 to +70 C Ground survival temperature

-55 to +85 C Shelf life Max. 7 years at max. 35 C Table A-1: CSDU specifications A-2 Chapter A: Equipment specifications 98-158751-C SDU-5045 Compact Satellite Data Unit Characteristics Specification Maximum resistance, AC input

< 1.0 Ohm Altitude Decompression Overpressure For installation in non-pressurized locations: Max. 55000 ft (Cat-F2) For installation in pressurized locations: 55000 ft

(Cat. A2) For installation in pressurized locations: -15000 ft

(Cat. A2) Relative humidity 95% non-condensing at +50C Environmental categories See appendix C, DO-160G specifications, Compact Satellite Data Unit (CSDU) on page C-2. Table A-1: CSDU specifications 98-158751-C Chapter A: Equipment specifications A-3 SCM-5055 Configuration Module A.3 SCM-5055 Configuration Module Characteristics Dimensions (L x W x H) Weight Mounting Supply voltage Connectors Specification 114.30 mm x 101.60 mm x 25.78 mm (4.50" x 4.00" x 1.015") 200 30 g Controlled and Non-controlled temperature locations with convection airflow cooling Non-pressurized locations. Pressurized locations. The SCM is connected to and powered by the CSDU. 15 position D-subminiature plug (pins) with 4-

40 UNC female screw-locks, equivalent to MIL-DTL-24308 M24308/24-26 and M24308/26-115

(ARINC 781 compliant) Operating temperature Ground survival temperature

-40 to +70 C

-55 to +85 C Shelf life Altitude Decompression Overpressure Environmental categories Max. 7 years at max. 35 C For installation in non-pressurized locations:

Max. 55000 ft (Cat. F2) For installation in pressurized locations: 55000 ft (Cat. A2) For installation in pressurized locations: -15000 ft (Cat. A2) See appendix C, DO-160G specifications, Configuration Module (SCM) on page C-5. Table A-2: SCM specifications A-4 Chapter A: Equipment specifications 98-158751-C HPA-5015 Multi-Carrier High Power Amplifier A.4 HPA-5015 Multi-Carrier High Power Amplifier Characteristics Dimensions

(L x W x H) Weight Mounting Supply voltage Specification 2 MCU ARINC 600 enclosure 323.00 mm x 61.00 mm x 199.70 mm (12.72" x 2.40"

x 7.86") The maximum weight of the MCHPA is 5.0 kg (11 lbs) Mount in an ARINC 600 2 MCU tray. Non-controlled-temperature location and supplied airflow cooling, with tray integrated onto a shelf rack system Non-pressurized locations. Pressurized locations. Nominal AC supply: 115 VAC (360 - 800Hz) Continuous operation: +90 V to 134 V Short time operation: +70.0 V - 170 V (30ms) Transparency time 200 ms Typical Power Consumption AC: 240 W Connectors Rear: ARINC 600 Attachment 11 Operating temperature Convection airflow cooling Forced airflow cooling Supplied airflow cooling

-40 to +40 C (+40C/20 hours; +55C/30 minutes)

-40 to +70 C

-40 to +70 C Ground survival temperature

-55 to +85 C Shelf life Max. 7 years at max. 35 C Maximum resistance, AC input

< 1.0 Ohm Altitude Decompression Overpressure For installation in non-pressurized locations: Max. 55000 ft (Cat-F2) For installation in pressurized locations: 55000 ft

(Cat. A2) For installation in pressurized locations: -15000 ft

(Cat. A2) Table A-3: MCHPA specifications 98-158751-C Chapter A: Equipment specifications A-5 HPA-5015 Multi-Carrier High Power Amplifier Characteristics Relative humidity Environmental categories Specification 95% non-condensing at +50C See appendix C, DO-160G specifications, Multi-

Carrier High Power Amplifier (MCHPA) on page C-

8. Table A-3: MCHPA specifications A-6 Chapter A: Equipment specifications 98-158751-C Appendix B System messages B This appendix has the following sections:

BITE error codes The AVIATOR 700S system shows system messages in connected display units (e.g. MCDU) or in the security and system log files of the CSDU when extracted in maintenance-allowed mode. B.1 BITE error codes BITE error codes contain information from the AVIATOR 700S system. This information is a result of a POST or PAST sequence or Continuous Monitoring performed by the Built-In Test Equipment. BITE error codes and explanation is shown in the MDCU display. B.1.1 List of BITE error codes Fault message subject Failure cause Consequences on the system Fault message code 1 SDU1(5RV1) Faulty SDU One or more system functions will be significantly degraded, possibly to the extend of being unable to communicate with other A/C LRUs, unable to log onto Inmarsat network or unable to support cockpit and/or cabin voice/data calls depending on the failure One or more system functions may suffer minor degradations, depending on the specific failure cause. FDCE type 1 SATCO M Fault Loss of AISD or PIESD Communi cation SATCO M Fault SATCO M Fault 2 SDU1(5RV1) Faulty SDU 4 7 SDU1(5RV1) Faulty SDU Loss of all communications SCM1(78RV1

) SCM failure Probable loss of all communications Table B-1: BITE error codes 98-158751-B B-1 BITE error codes Fault message code 8 Fault message subject MCDU1

(2CA1) Failure cause Consequences on the system SATCOM system receives an ARINC 429 message from MCDU1 with a SSM set to NCD/FW/FT MCDU1 is unusable for control/status of the SATCOM system. If available, MCDU2 or MCDU3 may be used if their SDU interfaces have not failed. MCDU2 is unusable for control/status of the SATCOM system. If available, MCDU1 or MCDU3 may be used if their SDU interfaces have not failed. MCDU3 is unusable for control/status of the SATCOM system. If available, MCDU1 or MCDU2 may be used if their SDU interfaces have not failed. Probable loss of all communications Probable loss of all communications The SDU will attempt to obtain all inertial data from its other IRS input, resulting in loss of all satellite communications only if an independant and healthy second ADIRU is unavailable. The SDU will attempt to obtain all inertial data from its other IRS input, resulting in loss of all satellite communications only if an independant and healthy second ADIRU is unavailable. Probable loss of all communications MCDU1 is unusable for control/status of the SATCOM system FDCE type 1 Loss of HMI Loss of HMI Loss of HMI SATCO M Fault SATCO M Fault Loss of Communi cation Loss of Communi cation SATCO M Fault Loss of HMI 9 MCDU2

(2CA2) SATCOM system receives an ARINC 429 message from MCDU2 with a SSM set to NCD/FW/FT 10 MCDU3

(2CA3) SATCOM system receives an ARINC 429 message from MCDU3 with a SSM set to NCD/FW/FT 11 12 13 ATSU1

(1TX1) ATSU2

(1TX2) ADIRU1

(1FP1) SATCOM system receives an ARINC 429 message from ATSU1 with a SSM set to NCD/FW/FT which lead to the Loss of Labels 214 and 216 SATCOM system receives an ARINC 429 message from ATSU1 with a SSM set to NCD/FW/FT which lead to the Loss of Labels 214 and 216 SATCOM system receives an ARINC 429 message from ADIRU1 with a SSM set to NCD/FW/FT 14 ADIRU2

(1FP2) SATCOM system receives an ARINC 429 message from ADIRU2 with a SSM set to NCD/FW/FT 18 ATSU1(1TX1

)/SDU1(5RV1

)/WRG 19 MCDU1(2CA 1)/SDU1(5RV 1)/WRG SATCOM system receives an ARINC 429 message from ATSU1 with a SSM set to SILENT SATCOM system receives an ARINC 429 message from MCDU1 with a SSM set to Silent Table B-1: BITE error codes (Continued) B-2 Chapter B: System messages 98-158751-B Fault message Fault message subject 21 code 20 MCDU2(2CA 2)/SDU1(5RV 1)/WRG ATSU2(1TX2

)/SDU1(5RV1

)/WRG HPA-HI GAIN(7RV1)/

SDU1(5RV1)/

WRG(41RV) SDU1(5RV1)/

SCM1(78RV1

)/WRG 24 25 26 MCDU3(2CA 3)/SDU1(5RV 1)/WRG ATSU1(1TX1

) ATSU2(1TX2

) 27 28 45 90 91 94 POWER SUPPLY INTERRUPT ADIRU1(1FP 1)/SDU1(5RV 1)/ WRG ADIRU2(1FP 2)/SDU1(5RV 1)/ WRG AUTO RESET 95 MANUAL RESET BITE error codes Failure cause Consequences on the system SATCOM system receives an ARINC 429 message from MCDU2 with a SSM set to Silent SATCOM system receives an ARINC 429 message from ATSU2 with a SSM set to SILENT No data from HPA to CSDU MCDU2 is unusable for control/status of the SATCOM system Probable loss of all communications Probable loss of communications SATCO M fault No data from SCM to the CSDU Loss of communications SATCOM system receives an ARINC 429 message from MCDU3 with a SSM set to Silent Loss of label 270 MCDU3 is unusable for control/status of the SATCOM system None Loss of label 270 None 41 WRG (42RV) Failure in the DLNA-CSDU Coaxial Cable Power interrupt Loss of communications Loss of communications SATCOM system receives an ARINC 429 message from ADIRU1 with a SSM set to Silent SATCOM system receives an ARINC 429 message from ADIRU2 with a SSM set to Silent Probable loss of all communications Probable loss of all communications Loss of communications during the reset Loss of communications during the reset Probable loss of all communications 96 HI GAIN ANTENNA-

TOP (16RV1) HGA Failure Table B-1: BITE error codes (Continued) 98-158751-B Chapter B: System messages B-3 FDCE type 1 Loss of HMI SATCO M Fault SATCO M fault Loss of HMI NONE NONE SATCO M Fault Loss of Communi cation Loss of Communi cation Loss of Communi cation Loss of Communi cation Loss of Communi cation SATCO M Fault BITE error codes Fault message code 97 98 99 Fault message subject SCM1

(78RV1)/

OVER TEMPERA HPA-HI GAIN(7RV1)/

OVER TEMPERA SDU1(5RV1)/

OVER TEMPERA Failure cause Consequences on the system FDCE type 1 The SCM is overheated Probable loss of communications SATCO M Fault The HPA is overheated Probable loss of communications SATCO M Fault The SDU is overheated Loss of AISD and/or PIESD communication Loss of AISD and/or PIESD Communi cation Probable loss of communications SATCO M Fault Loss of AISD or PIESD communication 101 WRG:

CONFIG PIN PROG/SDU1(

5RV1) SDU1(5RV1) Faulty SDU 102 Configuration HPP Parity error, Configuration HPP combination not plausible, ATE HPP parity error 103 SCM1(78RV1

) AISD/PIESD user ORT failure Loss of AISD or PIESD communication SCM Failure 104 SCM1(78RV1

) SOFTWARE COMP 105 HPA-HI MCHPA Failure GAIN(7RV1) SOFTWARE COMP SCM1(78RV1

) Probable loss of all communications Probable loss of all communications 107 Cabin USIM interface Failure Loss of Cabin communications 108 SCM1(78RV1

) SECURE ORT/ ACD user ORT failure Loss of all communications Table B-1: BITE error codes (Continued) Loss of AISD or PIESD Communi cation Loss of AISD or PIESD Communi cation SATCO M Fault SATCO M Fault Loss of PIESD Communi cation SATCO M Fault B-4 Chapter B: System messages 98-158751-B BITE error codes Fault message code 109 Fault message subject SDU1(5RV1)/

WRG Failure cause Consequences on the system Discrete Output failure No light indication of incomming call on channel 2 or No light indication of incomming call on channel 1 110 SCM1(78RV1

) SOFTWARE COMP 111 SCM1(78RV1

)/REGISTRA TION 112 XPDR-

1(1SH1) 113 XPDR-

1(1SH1)/SDU 1(5RV1)/WR G SCM Failure Loss of Cabin Communications SCM Registration Failure SATCOM system receives an ARINC 429 message from XPDR1 with a SSM set to NCD/FW/FT SATCOM system receives an ARINC 429 message from XPDR1 with a SSM set to Silent Probable loss of all communications Probable loss of all communications Probable loss of all communications Table B-1: BITE error codes (Continued) FDCE type 1 No light indication of incoming call on channel 2 or No light indication of incoming call on channel 1 Loss of AISD or PIESD communi cation SATCO M Fault SATCO M Fault SATCO M Fault 98-158751-B Chapter B: System messages B-5 BITE error codes B-6 Chapter B: System messages 98-158751-B Appendix C DO-160G specifications C This appendix has the following sections:

General DO-160 information Compact Satellite Data Unit (CSDU) Configuration Module (SCM) Multi-Carrier High Power Amplifier (MCHPA) C.1 C.1.1 C.1.2 Refer to HGA-7001 and DLNA installation manual [8] for DO-160 specifications of the antenna. General DO-160 information Certifying agency Approval of the installation of the AVIATOR 700S system is not authorized by this installation manual. Acceptance for the installation and use of the AVIATOR 700S system and its associated components must be obtained through the appropriate offices of the FAA or other certifying agency. It is recommended that all proposed installations be coordinated with the local jurisdiction of the FAA or other certifying agency prior to performing the installation. Environmental Qualification Forms The Environmental Qualification Forms list the environmental categories under which all Cobham SATCOM components of the AVIATOR 700S system are approved. Please refer to RTCA DO-160G for further details on the following Environmental Qualification Forms. 98-158751-C C-1 Compact Satellite Data Unit (CSDU) C.2 Compact Satellite Data Unit (CSDU) Part Number: SDU-5045 Environmental variable DO160 G section

(Unless otherwise specified) Category and requirements Temperature and Altitude Ground Survival Low Temperature Test -

55C Short-Time Operating Low Temperature Test -40C Operating Low Temperature Test -40C Ground Survival High Temperature Test

+85C Short-Time Operating High Temperature Test +70C Operating High Temperature Test +70C In Flight Loss of Cooling Altitude Test +55.000ft Decompression Test Overpressure Test Temperature Variation (-40C to +70C) Humidity Operational Shocks and Crash Safety Operational Shocks Crash Safety (Impulse) Crash Safety (Sustained) Bench Handling Shocks Vibration Standard Random Vibration 4 4.5.1 4.5.1 4.5.2 4.5.3 4.5.3 4.5.4 4.5.5 4.6.1 4.6.2 4.6.3 5 6 7 7.2 7.3.1 7.3.3

[(A2F2)Z]

A2 A2 A2 A2 A2 A2 Z F2 A2F2 A2 B A

E / B E / B Aircraft Type 5, Orientation:

Random MIL-STD 810G, Method 516.6, Proc. VI MIL-STD 810G, Method 516.6, Proc. VI 8 8.5

S(B3) Table C-1: Common environmental conditions and tests (DO160G) for CSDU C-2 Chapter C: DO-160G specifications 98-158751-C Compact Satellite Data Unit (CSDU) Environmental variable DO160 G section

(Unless otherwise specified) Category and requirements High-Level, Short Duration Vibration Explosion Atmosphere Waterproofness Fluids Susceptibility Sand & Dust Fungus Resistance Salt Fog Magnetic Effect Power Input Voltage Spike Audio Frequency Conducted Susceptibility AC Power Induced Signal Susceptibility Magnetic Fields Induced into Equipment. Magnetic Fields Induced into Interconnecting Cables Electrical Fields Induced into Interconnecting Cables Spikes Induced into Interconnecting Cables Radio Frequency Susceptibility

(Conducted & Radiated) Conducted Radiated Radio Frequency Emission Conducted Radiated 8.6 9 10 11 12 13 14 15 16 17 18 18.3.2 19 19.3.1 19.3.3 19.3.4 19.3.5 20 20.4 20.5 21 21.4 21.5 H(R) E Y F D F X Z A(WF)HLPI A R(WF) CWX CWX CWX CWX

T T

M M Lightning Induced Transient Susceptibility AZZZLZ Table C-1: Common environmental conditions and tests (DO160G) for CSDU (Continued) 22 98-158751-C Chapter C: DO-160G specifications C-3 Compact Satellite Data Unit (CSDU) Environmental variable DO160 G section

(Unless otherwise specified) Category and requirements Lightning Direct Effects Icing Electrostatic Discharge Fire, Flammability Federal Aviation Regulation 23 24 25 26 X X A C FAR 25.853(a) &

Appendix F, part I,

(a)(1)(ii) FAR 25.853(a) &

Appendix F, part I,

(a)(1)(v) FAR 25.869 (a)(1) &

Appendix F, part I Table C-1: Common environmental conditions and tests (DO160G) for CSDU (Continued) C-4 Chapter C: DO-160G specifications 98-158751-C Configuration Module (SCM) C.3 Configuration Module (SCM) Part Number: SCM-5055 Environmental variable DO160 G section

(Unless otherwise specified) Category and requirements Temperature and Altitude Ground Survival Low Temperature Test -

55C Short-Time Operating Low Temperature Test -40C Operating Low Temperature Test -40C Ground Survival High Temperature Test

+85C Short-Time Operating High Temperature Test +70C Operating High Temperature Test +70C In Flight Loss of Cooling Altitude Test +55.000ft Decompression Test Overpressure Test Temperature Variation (-40C to +70C) Humidity Operational Shocks and Crash Safety Operational Shocks Crash Safety (Impulse) Crash Safety (Sustained) 4 4.5.1 4.5.1 4.5.2 4.5.3 4.5.3 4.5.4 4.5.5 4.6.1 4.6.2 4.6.3 5 6 7 7.2 7.3.1 7.3.3

A2 A2 A2 A2 A2 A2 X F2 A2 A2 B A

B, E B, E Aircraft Type 5

(Helicopter and All Fixed-Wing) Orientation:

Random Functional Test before and after, not during Table C-2: Common environmental conditions and tests (DO160G) for SCM 98-158751-C Chapter C: DO-160G specifications C-5 Configuration Module (SCM) Environmental variable DO160 G section

(Unless otherwise specified) Category and requirements Bench Handling Shocks Vibration Standard Random Vibration High-Level, Short Duration Vibration Explosion Atmosphere Waterproofness Fluids Susceptibility Sand & Dust Fungus Resistance Salt Fog Magnetic Effect Induced Signal Susceptibility Magnetic Fields Induced into Equipment. Magnetic Fields Induced into Interconnecting Cables Electrical Fields Induced into Interconnecting Cables Spikes Induced into Interconnecting Cables Radio Frequency Susceptibility

(Conducted & Radiated) Conducted Radiated Emission of Radio Frequency Energy Conducted Radiated Lightning Induced Transient Susceptibility MIL-STD 810G, Method 516.6, Proc. VI 8 8.5 8.6 9 10 11 12 13 14 15 19 19.3.1 19.3.3 19.3.4 19.3.5 20 20.4 20.5 21 21.4 21.5 22

S(B3) H(R) X Y F S F X Z

CWX CWX CWX

T T

M (modified)a M A3 (Level 3, WF3 & WF4) Table C-2: Common environmental conditions and tests (DO160G) for SCM (Continued) C-6 Chapter C: DO-160G specifications 98-158751-C Configuration Module (SCM) Environmental variable DO160 G section

(Unless otherwise specified) Category and requirements Electrostatic Discharge (DO-160) Fire, Flammability (DO-160) Federal Aviation Regulation 25 26 A C FAR 25.853(a) &

Appendix F, part I,

(a)(1){ii) FAR 25.853(a) &

Appendix F, part I,

(a)(1)(v) FAR 25.869 (a)(1) &

Appendix F part I Table C-2: Common environmental conditions and tests (DO160G) for SCM (Continued) a. Category M modified by testing up to 200 MHz (instead of 152 MHz) and with a more severe level. 98-158751-C Chapter C: DO-160G specifications C-7 Multi-Carrier High Power Amplifier (MCHPA) C.4 Multi-Carrier High Power Amplifier (MCHPA) Part Number: HPA-5015 Environmental variable DO160 G section

(Unless otherwise specified) Category and requirements Temperature and Altitude Ground Survival Low Temperature Test -

55C Short-Time Operating Low Temperature Test -40C Operating Low Temperature Test -40C Ground Survival High Temperature Test

+85C Short-Time Operating High Temperature Test +70C Operating High Temperature Test +70C In Flight Loss of Cooling Altitude Test +55.000ft Decompression Test Overpressure Test Temperature Variation (-40C to +70C) Humidity Operational Shocks and Crash Safety Operational Shocks Crash Safety (Impulse) Crash Safety (Sustained) Bench Handling Shocks Vibration Standard Random Vibration 4 4.5.1 4.5.1 4.5.2 4.5.3 4.5.3 4.5.4 4.5.5 4.6.1 4.6.2 4.6.3 5 6 7 7.2 7.3.1 7.3.3

[(A2F2)Z]

A2 A2 A2 A2 A2 A2 Z F2 A2F2 A2 B A

E / B E / B Aircraft Type 5, Orientation:

Random MIL-STD 810G, Method 516.6, Proc. VI MIL-STD 810G, Method 516.6, Proc. VI 8 8.5

S(B3) Table C-3: Common environmental conditions and tests (DO160G) for MCHPA C-8 Chapter C: DO-160G specifications 98-158751-C Multi-Carrier High Power Amplifier (MCHPA) Environmental variable DO160 G section

(Unless otherwise specified) Category and requirements High-Level, Short Duration Vibration Explosion Atmosphere Waterproofness Fluids Susceptibility Sand & Dust Fungus Resistance Salt Fog Magnetic Effect Power Input Voltage Spike Audio Frequency Conducted Susceptibility AC Power Induced Signal Susceptibility Magnetic Fields Induced into Equipment. Magnetic Fields Induced into Interconnecting Cables Electrical Fields Induced into Interconnecting Cables Spikes Induced into Interconnecting Cables Radio Frequency Susceptibility

(Conducted & Radiated) Conducted Radiated Radio Frequency Emission Conducted Radiated Lightning Induced Transient Susceptibility 8.6 9 10 11 12 13 14 15 16 17 18 18.3.2 19 19.3.1 19.3.3 19.3.4 19.3.5 20 20.4 20.5 21 21.4 21.5 22 H(R) E Y F D F X Z A(WF)HLPI A R(WF) CWX CWX CWX CWX

T T

M M AZZZLZ Table C-3: Common environmental conditions and tests (DO160G) for MCHPA (Continued) 98-158751-C Chapter C: DO-160G specifications C-9 Multi-Carrier High Power Amplifier (MCHPA) Environmental variable DO160 G section

(Unless otherwise specified) Category and requirements Lightning Direct Effects Icing Electrostatic Discharge Fire, Flammability Federal Aviation Regulation 23 24 25 26 X X A C FAR 25.853(a) &

Appendix F, part I,

(a)(1)(ii) FAR 25.853(a) &

Appendix F, part I,

(a)(1)(v) FAR 25.869 (a)(1) &

Appendix F, part I Table C-3: Common environmental conditions and tests (DO160G) for MCHPA (Continued) C-10 Chapter C: DO-160G specifications 98-158751-C References Appendix D D D.1 Applicable standards

[1] AC 43.131B/2B; Acceptable Methods, Techniques, and Practices - Aircraft Inspection Repair and Alterations, U.S. Department of Transportation, FAA

[2] ARINC Characteristic 743-A GNSS sensor

[3] ARINC Characteristic 781-7 Mark3 Aviation Satellite Communication Systems, August 9, 2017

[4] ARINC 600-19 Air Transport Avionics Equipment Interfaces

[5]

RTCA DO-160G: Environmental Conditions and Test Procedures for Airborne Equipment, December 8, 2010

[6] ARINC 429P1-19 Digital Information Transfer System (DITS), Part 1, Functional Description, Electrical Interfaces, Label Assignments and Word Formats, January 22, 2019 D.2 Other references

[7] AVIATOR 700S User Manual*

[8] HGA-7001 Installation Manual (862-A0089_IM)

[9] ORT Tool User Guide*

[10] AVIATOR Operational User Guidance (99-157303)

*: Contact your supplier for a copy of the User Manual 98-158751-C D-1 Other references D-2 Chapter D: References 98-158751-C Glossary 5 Aeronautical Administrative Communications Aircraft Communications Addressing And Reporting System Aircraft Collision Avoidance System.. Aircraft Control Domain Audio Control Panel Avionics Communication Router Automatic Direction Finder. A navigation receiver based on the AM radio band. A very simple device which literally points towards the station that is tuned in. Air Data Inertial Reference Unit Airborne Data Loader Automatic Dependent Surveillance - Contract Aeronautical Earth Station Airborne Flight Information System Aircraft Information Services Domain Audio Management System Audio Management Unit Airline Operational Control Aircraft On Ground Airline / Aeronautical Passenger Communication Aeronautical Radio Incorporated Aircraft Traffic Service Air Traffic Service Unit American Wire Gauge Broadband Global Area Network Built-In Test Equipment Control Display Unit Central Fault and Display System Central Maintenance Computer Communications Management Unit Controller to Pilot Data Link Communications Compact Satellite Data Unit Distance Measuring Equipment Electronic Centralized Aircraft Monitor Electronic Flight Bag Engine-Indicating and Crew-Alerting System Enhanced Low Gain Antenna Electro Magnetic Compatibility Federal Aviation Administration Future Air Navigation System Flight Deck and Cabin Effect Flight Warning Computer Flight Warning System Glossary A AAC ACARS ACAS ACD ACP ACR ADF ADIRU ADL ADS-C AES AFIS AISD AMS AMU AOC AOG APC ARINC ATS ATSU AWG B BGAN BITE C CDU CFDS CMC CMU CPDLC CSDU D DME E ECAM EFB EICAS ELGA EMC F FAA FANS FDCE FWC FWS 98-158751-C Glossary-1 Glossary H HELGA HLD I ICAO ILS IMSI IPSEC L LGA LGCIU LGERS LRU M MCDU MCU O ORT P PAST PIESD PTT R RF RMA RMP Rx S SATCOM SB SCDU SCM SDU SSPC STC T TC TCAS TCP TX U USB USIM Glossary-2 HLD Enhanced Low Gain Antenna High Power Amplifier, Low Noise Amplifier and Diplexer International Civil Aviation Organization Instrument Landing System. A system of tightly focused transmitters located at the end of a runway that provides flight guidance information to flight crews. International Mobile Subscriber Identity Internet Protocol Security Low Gain Antenna Landing Gear Control and Interface Unit Landing Gear Extension and Retraction System Line Replaceable Unit. A separate unit or module which can easily be replaced. Multi-Function Control Display Unit Modular Component Unit Owners Requirements Table Person Activated Self Test Passenger Information and Entertainment Services Domain Push To Talk Radio Frequency (signal) Return Material Authorization Radio Management Panel Receive (signal) Satellite Communications Swift Broadband Satellite Control/Display Unit SDU Configuration Module Satellite Data Unit Solid State Power Controller Supplemental Type Certificate. Type Certificate Traffic Alert and Collision Avoidance System. A system which warns pilots of potential conflicts with other aircraft. Tuning Control Panel Transmit (signal) Universal Serial Bus Universal Subscriber Identity Module 98-158751-C V VHF VOR VPN W WoW WSC Very High Frequency. 30-300 MHz. VHF Omnidirectional Range Virtual Private Network Weight on Wheels Williamsbrug SDU Controllers 98-158751-C Chapter Glossary:

Glossary-3 Glossary-4 Chapter Glossary:

98-158751-C Index Index 6 A about this manual 1-1 activation SIM card 4-40 address manufacturer -ii airtime services 4-39 Airworthiness, Continued 6-1, 7-1 antenna systems 2-6 wiring 4-12, 4-13 recommended cables 4-38 ARINC 429 B BITE codes list of B-1 C cable cable loss cables RF cables 4-13 SCM, data to and from CSDU 4-39 SCM, power source, power return 4-39 allowed lengths, power 4-37 ARINC 429 4-38 ARINC 429, recommended types 4-38 discrete signals 4-39 Ethernet, recommended 4-38 power, recommended types 4-38 recommended 4-37 RF, recommended types 4-38 SCM to CSDU 4-39 SDU power supply 4-9, 4-11 check procedures after power-up 6-3 airborne 6-5 before inserting LRUs 6-2 interference with other systems on air-

craft 6-4 Circuit breaker specifications 2-9 Coax 4-6 Configuration Module 2-6 connectors part number 2-9 SDU rear receptacle 4-25 contact address -ii contact information 7-4 Continued Airworthiness 6-1, 7-1 D defect units 7-2 discrete signals recommended cables 4-39 DO-160 forms C-1 SDU C-2 drawings 3-1 SDU Tray connector 3-10, 3-11 E electrical installation 4-6 Environmental Qualification Forms C-1 SDU C-2 error codes B-1 Ethernet recommended cables 4-38 exchanging units 7-2 F Fail/Pass LED, SDU 7-8 fluid drippage 4-4, 4-5 functional test, airborne 6-5 functional test, on ground 6-3 H HLD mounting 4-5 I IMSI number 4-40 inoperative units 7-2 installation kit part number 2-9 interfaces 4-1 L LEDs on SDU Fail/Pass 7-8 Logon 7-8 Power 7-8 system ready 5-2 location SDU temperature controlled 4-4 98-158751-C Index-1 Logon LED on SDU 7-8 M Maintenance connector PC and Reset, wiring 4-22 mounting considerations 4-3 manufacturer address -ii messages B-1 minimum system drawing 4-2 HLD 4-5 SDU 4-3, 4-4, 4-5 O operation 2-7 outline drawings 3-1 P part numbers connector 2-9 installation kit 2-9 PAST 7-7 PC, Maintenance wiring 4-22 Person Activated Self Test 7-7 POST 7-7 power cables recommended 4-38 Power LED on SDU 7-8 Power On Self Test 7-7 provisioning 4-40 R references D-1 repair 7-2 returning units 7-10 Reset wiring 4-22 returning units 7-10 RF cables recommended 4-38 RS-232 Maintenance wiring 4-22 RTCA DO-160 forms C-1 S satcom antennas 2-6 SCM cable data to and from CSDU 4-39 Index-2 Chapter Index:

98-158751-C power source, power return 4-39 recommended 4-39 SDU DO-160 form C-2 Environmental Qualification Form C-2 location in aircraft 4-4 mounting 4-3, 4-4, 4-5 power cables 4-9, 4-11 rear receptacle 4-25 Tray connector, outline drawing 3-10, 3-11 SIM card activation 4-40 software update 7-5 specifications A-1 circuit breaker 2-9 standards, applicable D-1 support contact details 7-2 contact information 7-4 system drawing minimum 4-2 system messages B-1 system ready 5-2 T temperature controlled SDU 4-4 test procedures after power-up 6-3 airborne 6-5 before inserting LRUs 6-2 interference with other systems on aircraft 6-4 troubleshooting 7-7 U updating software 7-5 W wiring 4-1, 4-6 antenna 4-12, 4-13 data cable for front connector 4-22 Maintenance PC and Reset 4-22 symbols 4-6 wiring symbol Coax 4-6 Ground 4-6 Shield 4-6 Twisted and shielded 4-6 98-158751-C Chapter Index:

Index-3 Index-4 Chapter Index:

98-158751-C 98-158751-C www.cobhamaerospacecommunications.com Cobham Public

 

 

AVIATOR 700S User Manual Document Revision

: 98-181261

: A Activity Function Role Name Date Signature Prepared System Engineer SE Adrian Erasmus Reviewed System Engineer SE Mohammed Saadi Reviewed Program Manager PM Kim Harder Released Configuration Management CM Gitte Coucke Copyright Cobham Aerospace Communications ALL RIGHTS RESERVED COBHAM PRIVATE

(T: 99-161853) AVIATOR 700S User Manual REVISION HISTORY Revision Author Draft-A1 Draft-A2 AER AER Draft-A3 A AER AER Date Jul 2023 Aug 2023 Nov 2023 Nov 2023 Section All All 10

Description of Change Draft-A1 for internal review. Inclusion of peer review comments. Added of section 10.1.3 PIMBIT. Template updated. Release of revision A as per Draft-A3. Cobham Aerospace Communications This Document and any other appended documents and drawings are of copyright to Cobham Aerospace Communications. It contains proprietary information which is disclosed for information purposes only. The contents of this document shall not in whole or in part be used for any other purpose; be disclosed to any member of the recipients organisation not having a need to know such information or to any third party, individual, organisation or Government; be stored in any retrieval system or be produced or transmitted in any form by photocopying or any optical, mechanical or other means without prior permission of Cobham Aerospace Communications. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 2 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual TABLE OF CONTENTS PAGE 1 INTRODUCTION ..................................................................................................................... 10 1.1 GENERAL ................................................................................................................................... 10 1.1.1 Purpose ............................................................................................................................ 10 1.1.2 Scope ............................................................................................................................... 10 1.2 GLOSSARY ................................................................................................................................. 10 1.2.1 Acronyms ......................................................................................................................... 10 1.3 REFERENCES .............................................................................................................................. 13 1.3.1 External References .......................................................................................................... 13 1.3.2 Internal References ........................................................................................................... 13 2 REGULATORY INFORMATION ................................................................................................ 14 2.1 RADIOFREQUENCY RADIATION EXPOSURE INFORMATION ........................................................................ 14 2.1.1 AVIATOR 700S .................................................................................................................. 14 2.2 2.3 2.4 FEDERAL COMMUNICATIONS COMMISSION (FCC) ................................................................................ 14 JAPANESE RADIO LAW AND JAPANESE TELECOMMUNICATIONS BUSINESS LAW COMPLIANCE ............................ 15 INNOVATION, SCIENCE AND ECONOMIC DEVELOPMENT CANADA (ISED) .................................................... 15 CHANGES OR MODIFICATIONS MADE TO THIS EQUIPMENT NOT EXPRESSLY APPROVED BY COBHAM MAY VOID THE FCC AUTHORIZATION TO OPERATE THIS EQUIPMENT .............................................................................................. 15 3 SWIFTBROADBAND SAFETY SYSTEM OVERVIEW ................................................................. 16 3.1 INMARSAT SATELLITE NETWORK ................................................................................................... 16 3.1.1 SwiftBroadband-Safety (SB-S) for the Cockpit ..................................................................... 16 3.1.2 SwiftBroadband (SBB) for the Cabin ................................................................................... 16 3.1.3 SwiftBroadband Satellites and Coverage Map ...................................................................... 16 3.2 AVIATOR S SATCOM SYSTEM FUNCTIONS AND FEATURES ................................................................... 17 3.2.1 System Overview AVIATOR 700S .................................................................................... 17 3.2.2 Configuration .................................................................................................................... 18 3.3 SAFETY VOICE SERVICES ............................................................................................................... 18 3.3.1 Call Priorities - Ground-to-Air (G2A) .................................................................................... 18 3.3.2 Call Priorities - Air-to-Ground (A2G) .................................................................................... 19 3.3.3 Pre-emption ...................................................................................................................... 19 3.4 SAFETY DATA SERVICES ................................................................................................................ 19 3.4.1 ACARS Data ...................................................................................................................... 19 3.5 NON-SAFETY DATA SERVICES ......................................................................................................... 19 COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 3 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 3.5.1 Electronic Flight Bag (EFB) ................................................................................................. 19 3.5.2 Cabin Data........................................................................................................................ 20 3.5.2.1 Service Class .............................................................................................................................. 20 3.5.2.2 Service Class Selection ................................................................................................................ 20 4 SERVICE ACTIVATION ........................................................................................................... 21 4.1 4.2 IMSI AND SMART CARD INFORMATION ............................................................................................. 22 PUBLIC KEY INFRASTRUCTURE (PKI) SECURITY CERTIFICATE.................................................................. 22 5 INTERPRETING THE SYSTEM STATUS ................................................................................... 23 5.1 VOICE AVAILABILITY .................................................................................................................... 24 5.1.1 Not Ready ........................................................................................................................ 24 5.1.2 Safety Voice Services - Ready ............................................................................................ 25 5.1.3 Safety Data Services - Available ......................................................................................... 25 5.2 5.3 SWIFTBROADBAND (SBB) SERVICE AVALABILITY ................................................................................. 26 SATCOM LOG ........................................................................................................................... 27 5.3.1 Logging On/Logged On/Logged Off/Standby/Rejected ......................................................... 27 5.3.2 SATCOM INOP .................................................................................................................. 28 5.3.3 ICAO ................................................................................................................................ 28 6 SATELLITE SELECTION .......................................................................................................... 29 6.1.1 Log Off & Auto/Manual Log On .......................................................................................... 29 6.1.2 Ocean Region Change (ORC) ............................................................................................. 29 7 SAFETY VOICE SERVICES ...................................................................................................... 30 7.1 MCDU INTERFACE ....................................................................................................................... 30 7.1.1 Outgoing Calls - Air-to-Ground (A2G) ................................................................................. 30 7.1.1.1 Manual Entry .............................................................................................................................. 30 7.1.1.2 Directory Dial ............................................................................................................................. 31 7.1.1.3 Initiating an Outgoing Call ........................................................................................................... 32 7.1.1.4 Ending an Outgoing Call .............................................................................................................. 33 7.1.2 Incoming Calls - Ground-to-Air (G2A) ................................................................................. 34 7.1.2.1 Cockpit Alerting .......................................................................................................................... 34 7.1.2.2 Identifying the calling party and priority ........................................................................................ 34 7.1.2.3 Answering an Incoming Call ......................................................................................................... 35 7.1.2.4 Rejecting an Incoming Call .......................................................................................................... 36 7.1.2.5 Ending an Incoming Call .............................................................................................................. 36 7.1.2.6 Preemption ................................................................................................................................ 36 8 SAFETY DATA SERVICES ........................................................................................................ 37 COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 4 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 8.1 ACARS DATA ............................................................................................................................. 37 9 NON-SAFETY DATA SERVICES ............................................................................................... 38 9.1 9.2 ELECTRONIC FLIGHT BAG (EFB) CONNECTIVITY .................................................................................. 38 CABIN DATA CONNECTIVITY ........................................................................................................... 38 9.2.1 PPPoE Connections ............................................................................................................ 39 9.2.2 Connection Authentication ................................................................................................. 40 9.2.3 PPPoE Service Name ......................................................................................................... 40 9.2.4 Connection Control using TELNET ...................................................................................... 41 9.2.4.1 Primary PDP Contexts ................................................................................................................. 41 9.2.4.2 Secondary PDP Contexts ............................................................................................................. 41 9.2.4.3 Out-of-band Control Port Connection and Configuration ................................................................. 42 9.2.4.4 List of Supported AT-Commands .................................................................................................. 42 9.2.4.5 Binding to an active Primary PDP context ...................................................................................... 43 9.2.4.6 Adding a Secondary PDP Context ................................................................................................. 43 9.2.4.7 Traffic Flow Templates ................................................................................................................ 43 9.2.4.8 Modifying/Scaling of Streaming Class PDP Contexts ....................................................................... 44 9.2.4.9 Deactivating PDP contexts ........................................................................................................... 44 10 TROUBLESHOOTING ........................................................................................................... 45 10.1 BITE .................................................................................................................................... 45 10.1.1 BITE Scanning - Troubleshooting Code ............................................................................... 46 10.1.2 PAST ................................................................................................................................ 47 10.1.3 PIMBIT ............................................................................................................................. 49 10.1.4 LEGS ................................................................................................................................ 51 10.2 10.3 10.4 10.5 SATCOM CONFIG .................................................................................................................. 52 LOG FILE EXTRACTION VIA THE ETHERNET DATALOADER INTERFACE ...................................................... 53 LOG FILE EXTRACTION VIA THE MAINTENANCE USB .......................................................................... 53 SYSTEM TEST - FLASHING CALL LIGHTS ......................................................................................... 53 APPENDIX A. AISD SNMP INTERFACE ...................................................................................... 54 APPENDIX B. PIESD SNMP INTERFACE .................................................................................... 61 APPENDIX C. SNMP OBJECT ID DEFINITIONS ......................................................................... 68 APPENDIX C.1. ASLIACTLINKSTATUS(4) .................................................................................................. 68 APPENDIX C.2. ASLIHISTLINKENTRYNUMBERS(6) ...................................................................................... 68 APPENDIX C.3. ASUSDUINFOVENDOR(2) ................................................................................................. 68 APPENDIX C.4. ASUSDUINFOFAILURECODE(11) ........................................................................................ 68 COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 5 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual APPENDIX C.5. ASUSDUINFOFAILUREREASON(12) ..................................................................................... 69 APPENDIX D. AT-COMMANDS ................................................................................................... 70 APPENDIX D.1. GENERAL COMMANDS ...................................................................................................... 70 List all Available AT Commands ............................................................................. 70 Command Echo .................................................................................................... 70 APPENDIX D.2. SYSTEM INFORMATION .................................................................................................... 71 Request Manufacturer Identification ...................................................................... 71 Request Model Identification ................................................................................. 71 Request Revision Identification ............................................................................. 72 Request Serial Number Identification ..................................................................... 72 Request International Mobile Subscriber Identity .................................................... 72 APPENDIX D.3. PACKET DATA CONNECTIONS ............................................................................................ 73 Define Primary PDP Context .................................................................................. 73 3G Quality of Service Profile (Requested) ............................................................... 75 2G Quality of Service Profile (Requested) ............................................................... 79 3G Quality of Service Profile (Negotiated) .............................................................. 83 3G Quality of Service Profile (Minimum Acceptable) ................................................ 86 PDP Context Activation ......................................................................................... 90 Show PDP IP Address ........................................................................................... 90 Define Secondary PDP Context .............................................................................. 91 Define Traffic Flow Template ................................................................................ 93 Modify PDP Context ............................................................................................ 95 Binding a TCP Session to a Primary PDP Context .................................................. 96 APPENDIX E. TROUBLESHOOTING & MAINTENANCE ACTIONS .............................................. 97 APPENDIX E.1. FAULT DISPLAY SYSTEM (FDS) ......................................................................................... 98 COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 6 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual LIST OF FIGURES PAGE Figure 3-1: INMARSAT SwiftBroadband Coverage ................................................................................... 17 Figure 3-2: AVIATOR 700S SATCOM System ........................................................................................... 17 Figure 4-1: AVIATOR S SCM | IMSI & Smart Card Identification ............................................................... 22 Figure 5-1: ARINC 739A MCDU .............................................................................................................. 23 Figure 5-2: SATCOM Page Layout........................................................................................................... 23 Figure 5-3: MCDU - SAT-PHONE 1/2 - NOT READY .................................................................................. 24 Figure 5-4: MCDU - SAT-PHONE 2/2 ....................................................................................................... 24 Figure 5-5: MCDU - SAT-PHONE - Ready ................................................................................................ 25 Figure 5-6: MCDU - SAT-LOG 1/2 - Safety Data Available ........................................................................ 25 Figure 5-7: MCDU - SBB - Service Availability .......................................................................................... 26 Figure 5-8: MCDU - SAT-LOG 1/2 - Status - Logging On .......................................................................... 27 Figure 5-9: MCDU - SAT-LOG 1/2 - Status - Logged On ........................................................................... 27 Figure 5-10: MCDU - SAT-LOG 1/2 - Status - Logged Off ......................................................................... 27 Figure 5-11: MCDU - SAT-LOG 1/2 - Status - Rejected ............................................................................ 27 Figure 5-12: MCDU - SAT-LOG 1/2 - Status - SATCOM INOP .................................................................... 28 Figure 5-13: MCDU - SAT-LOG 2/2 - ICAO .............................................................................................. 28 Figure 7-1: MCDU - SAT-PHONE 1/2 - Manual Entry - International Number - Scratchpad.......................... 30 Figure 7-2: MCDU - SAT-PHONE - Manual Entry - Short Code - Pre-selected ............................................. 30 Figure 7-3: MCDU - SAT DIRECTORY INDEX 1/2 ..................................................................................... 31 Figure 7-4: MCDU - SAT DIRECTORY X/Y ............................................................................................... 31 Figure 7-5: MCDU - SAT-PHONE 1/2 - Outgoing Call - Make Call .............................................................. 32 Figure 7-6: MCDU - SAT-PHONE 1/2 - Outgoing Call - Dialing .................................................................. 32 Figure 7-7: MCDU - SAT-PHONE 1/2 - Outgoing Call - Ringing ................................................................. 32 Figure 7-8: MCDU - SAT-PHONE 1/2 - Outgoing Call - Answered .............................................................. 32 Figure 7-9: MCDU - SAT-PHONE 1/2 - Outgoing Call - Call Failed ............................................................. 33 Figure 7-10: MCDU - SAT-PHONE - Ending a call ..................................................................................... 33 Figure 7-11: MCDU - SAT-PHONE - Call ended ........................................................................................ 33 Figure 7-12: MCDU - SAT-PHONE - Incoming Call - Caller Identity ........................................................... 34 Figure 7-13: MCDU - SAT-PHONE - Incoming Call - Answer ..................................................................... 35 Figure 7-14: MCDU - SAT-PHONE - Incoming Call - Answered .................................................................. 35 Figure 7-15: MCDU - SAT-PHONE - Incoming Call - Rejected ................................................................... 36 Figure 7-16: MCDU - SAT-PHONE - Incoming Call - Preempted ................................................................ 36 COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 7 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual Figure 7-17: MCDU - SAT-PHONE - Incoming Call - Preemption Caller ID.................................................. 36 Figure 8-1: MCDU - SAT-LOG - ACARS Data Available .............................................................................. 37 Figure 9-1: MCDU - SAT-LOG- Cabin Comm enabled ............................................................................... 39 Figure 9-2: MCDU - SAT-LOG - Cabin Comm disabled .............................................................................. 39 Figure 10-1: MCDU - SAT-PHONE 2/2 ..................................................................................................... 45 Figure 10-2: MCDU - BITE OK ............................................................................................................. 45 Figure 10-3: MCDU - BITE - FAIL ........................................................................................................... 45 Figure 10-4: MCDU - BITE - BITE SCANNING .......................................................................................... 46 Figure 10-5: MCDU - BITE - BITE SCANNING DETAILS ............................................................................ 46 Figure 10-10: MCDU - BITE - PAST ........................................................................................................ 47 Figure 10-11: MCDU - BITE - PAST STARTED ......................................................................................... 47 Figure 10-12: MCDU - BITE - PAST REPORT - Not Run ............................................................................ 47 Figure 10-13: MCDU - BITE - PAST IN PROGRESS ................................................................................... 47 Figure 10-14: MCDU - BITE - PAST REPORT - Passed .............................................................................. 48 Figure 10-15: MCDU - BITE - PAST REPORT - Failed ............................................................................... 48 Figure 10-16: MCDU - BITE - PAST - Not Possible ................................................................................... 48 Figure 10-13: MCDU - BITE - PIMBIT ..................................................................................................... 49 Figure 10-14: MCDU - BITE - PIMBIT - PIMBIT TEST STARTED ................................................................ 49 Figure 10-15: MCDU - BITE - PIMBIT - PIMBIT TEST PROGRESS ............................................................. 49 Figure 10-16: MCDU - BITE - PIMBIT - PIMBIT TEST RESULT - TEST PASSED .......................................... 49 Figure 10-17: MCDU - BITE - PIMBIT - PIMBIT TEST RESULT - TEST FAILED ........................................... 49 Figure 10-18: MCDU - BITE - PIMBIT - PIMBIT TEST RESULT - PIMBIT TEST DATA .................................. 49 Figure 10-19: MCDU - BITE - PIMBIT - PIMBIT TEST RESULT - PIMBIT TEST EXIT ................................... 50 Figure 10-20: MCDU - BITE - LEGS ........................................................................................................ 51 Figure 10-21: MCDU - BITE - LEGS - GROUND FAULTS ........................................................................... 51 Figure 10-22: MCDU - BITE - LEGS - LAST LEG ....................................................................................... 51 Figure 10-23: MCDU - BITE - LEGS - PREVIOUS LEGS ............................................................................. 51 Figure 10-24: MCDU - SAT-CONFIG 1/5 .................................................................................................. 52 Figure 10-25: MCDU - SAT-CONFIG 2/5 .................................................................................................. 52 Figure 10-26: MCDU - SAT-CONFIG 3/5 .................................................................................................. 53 Figure 10-27: MCDU - SAT-CONFIG 4/5 .................................................................................................. 53 Figure 10-28: MCDU - SAT-CONFIG 5/5 .................................................................................................. 53 Figure 10-29: MCDU - BITE - Troubleshooting Code ................................................................................ 97 Figure 10-30: BITE - FDS - Troubleshooting Code Example ...................................................................... 97 COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 8 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual LIST OF TABLES PAGE Table 1-1: Document Scope ................................................................................................................... 10 Table 1-2: List of Acronyms ................................................................................................................... 10 Table 1-3: List of External References .................................................................................................... 13 Table 1-4: List of Internal References ..................................................................................................... 13 Table 3-1: Call Priorities ........................................................................................................................ 18 Table 9-1: PPPoE Service Name Options ................................................................................................. 41 Table 9-2: AVIATOR S Supported AT-Commands .................................................................................... 42 Table 10-1: AISD SNMP MIB OID Support .............................................................................................. 54 Table 10-2: PIESD SNMP MIB OID Support ............................................................................................. 61 Table 10-3: Failure group of asuSduInfoFailureCode ............................................................................... 68 Table 10-4: TFT Parameter Combinations ............................................................................................... 95 Table 10-5: Troubleshooting codes and recommended maintenance actions ............................................. 98 COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 9 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 1 INTRODUCTION 1.1 GENERAL 1.1.1 Purpose This document provides a guide for users intending to make voice calls or data connections via the AVIATOR 700S SATCOM System. The use of voice and data services as well as the use of advanced data features is demonstrated by means of examples. An installed and configured Aeronautical Earth Station (AES) is assumed throughout. 1.1.2 Scope This document is scoped to the items defined in Table 1-1. Table 1-1: Document Scope Equipment Part Number Description SDU-5045 405045-0100x Compact Satellite Data Unit HPA-5015 405015-0100x High Power Amplifier SCM-5055 405055-0100x SDU Configuration Module DLNA HGA 173628-101 677-A0193 405013A 804-10-0015 822-2236-501 4141-89-99 677-A0173 405017A 1.2 GLOSSARY 1.2.1 Acronyms ARINC 781 Type F Diplexer/LNA ARINC 781 High Gain Antenna Table 1-2: List of Acronyms Acronym Description A2G AAC Air-to-Ground Airline Administrative Control ACARS Aircraft Communications, Addressing and Reporting System ACD ACP ADL AES AISD AMER AOC Aircraft Control Domain Audio Control Panel Airborne Data Loader Aircraft Earth Station Airline Information and Services Domain Americas Aeronautical Operational Control COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 10 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual Table 1-2: List of Acronyms Acronym Description APAC APN ATA ATC AUTO CDU CFDS CHAP CID CMU CSDU CSP CSR Asia-Pacific Access Point Name Air Transport Association Air Traffic Control Automatically Control & Display Unit Central Fault Display System Challenge Handshake Authentication Protocol Context ID Communication Management Unit Compact Satellite Data Unit Communication Service Provider Certificate Signing Request CTTIC China Transport Telecommunications & Information Centre dB DL DLNA EFB EMEA FDS FWS G2A GES HDR HGA HLD HMI HPA Hz IANA ICAO ID IFE IM IMSI INOP Decibels Downlink Diplexer/Low Noise Amplifier Electronic Flight Bag Europe, Middle East and Africa Fault Display Specification Flight Warning System Ground-to-Air Ground Earth Station High Data Rate High Gain Antenna HPA/LNA/Duplexer Human Machine Interface High Power Amplifier Hertz Internet Assigned Numbers Authority International Civil Aviation Organisation Identity In-Flight Entertainment Installation Manual International Mobile Subscriber Identity Inoperable COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 11 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual Table 1-2: List of Acronyms Acronym Description IP IPCP LNA LRU LSK MB MCDU MEAS MIB NAT ORC OID OPS ORT PAP PDL PDP Internet Protocol Internet Protocol Control Protocol Low Noise Amplifier Line Replaceable Unit Line Select Key Megabyte Multi-purpose Control and Display Unit Middle East and Asia Management Information Base Network Address Translation Ocean Region Change Object ID Operational Program Software Owner Requirements Table Password Authentication Protocol Portable Data Loader Packet Data Protocol PIMBIT Passive Intermodulation Built In Test PKI QoS SAT SATCOM SB / SBB SB-S SCM SDU SNMP SPI TFT UHF UL UM UMTS VHF VPN Public Key Infrastructure Quality of Service Satellite Satellite Communication SwiftBroadband SwiftBroadband-Safety SDU Configuration Module Satellite Data Unit Simple Network Management Protocol Security Parameter Index Traffic Flow Template Ultra High Frequency Uplink User Manual Universal Mobile Telecommunications System Very High Frequency Virtual Private Network COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 12 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 1.3 REFERENCES 1.3.1 External References Table 1-3: List of External References Reference Tag Document Revision Document Title

[3GPP_TS27]

3GPP TS 27.007 10.3.0

[A781]

ARINC 781 7 Digital cellular telecommunications system (Phase 2+);

Universal Mobile Telecommunications System (UMTS);

AT command set for User Equipment (UE) ARINC Characteristic 781 - Mark 3 Aviation Satellite Communication Systems

[ITU-T_V.250]

ITU-T V.250 Serial asynchronous automatic dialing and control

[PKI_CON]

PKI CONOPS

[PKI_OPS]

PKI INMARSAT

[GOLD]

ICAO GOLD

[SVGM]

ICAO SVGM

[A739]

ARINC 739

[A739A]

ARINC 739A

[A615]

ARINC 615

[A615A]

ARINC 615A

[A665]

ARINC 665 0.3 0.9 Second Edition First Edition 1 1 4 2 2 SwiftBroadband Safety 2.0 Overview and PKI Concept of Operations Inmarsat SB-S Service - Airline Ops Handbook International Civil Aviation Organization (ICAO) - Global Operational Data Link Document (GOLD) International Civil Aviation Organization (ICAO) - Satellite Voice Guidance Material (SVGM) ARINC Characteristic 739 - Multi-purpose Control and Display Unit ARINC Characteristic 739A - Multi-purpose Control and Display Unit Airborne Computer High Speed Data Loader Software Data Loader Using Ethernet Interface Loadable Software Standards 1.3.2 Internal References Table 1-4: List of Internal References Reference Tag Document Revision Document Title

[700S_IM]

98-158751 Latest AVIATOR 700S Installation Manual

[SORT_UG]

99-181291 Latest AVIATOR 700S ORT Tool - Secure & User Guide

[UORT_UG]

99-181292 Latest AVIATOR 700S ORT Tool - User Guide

[LET]

99-178150 Latest AVIATOR S Log Extraction Tool User Guide COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 13 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 2 REGULATORY INFORMATION 2.1 RADIOFREQUENCY RADIATION EXPOSURE INFORMATION 2.1.1 AVIATOR 700S This equipment complies with FCC and IC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance of 235 cm between the radiator and your body. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. Cet quipement est conforme aux limites d'exposition aux rayonnements IC tablies pour un environnement non contrl. Cet quipement doit tre install et utilis avec un minimum de 235 cm de distance entre la source de rayonnement et votre corps. Ce transmetteur ne doit pas etre place au meme endroit ou utilise simultanement avec un autre transmetteur ou antenne. 2.2 FEDERAL COMMUNICATIONS COMMISSION (FCC) This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. NOTICE:

Changes or modifications made to this equipment not expressly approved by Cobham may void the FCC authorization to operate this equipment. NOTICE:

This device complies with Part 15 of the FCC Rules and with Industry Canada license-exempt RSS standard(s). Operation is subject to the following two conditions:

(1) this device may not cause harmful interference, and

(2) this device must accept any interference received, including interference that may cause undesired operation. Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes:

(1) l'appareil ne doit pas produire de brouillage, et

(2) l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 14 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 2.3 JAPANESE RADIO LAW AND JAPANESE TELECOMMUNICATIONS BUSINESS LAW COMPLIANCE This device is granted pursuant to the Japanese Radio Law (

) and the Japanese Telecommunications Business Law (

). This device should not be modified (otherwise the granted designation number will become invalid). 2.4 INNOVATION, SCIENCE AND ECONOMIC DEVELOPMENT CANADA (ISED) NOTICE:

This device contains licence-exempt transmitter(s)/receiver(s) that comply with Innovation, Science and Economic Development Canadas licence-exempt RSS(s). Operation is subject to the following two conditions:

1. This device may not cause interference. 2. This device must accept any interference, including interference that may cause undesired operation of the device. Lmetteur/rcepteur exempt de licence contenu dans le prsent appareil est conforme aux CNR dInnovation, Sciences et Dveloppement conomique Canada applicables aux appareils radio exempts de licence. Lexploitation est autorise aux deux conditions suivantes :

1. Lappareil ne doit pas produire de brouillage. 2. Lappareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible den compromettre le fonctionnement. NOTICE:

Changes or modifications made to this equipment not expressly approved by Cobham may void the FCC authorization to operate this equipment COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 15 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 3 SWIFTBROADBAND SAFETY SYSTEM OVERVIEW 3.1 INMARSAT SATELLITE NETWORK 3.1.1 SwiftBroadband-Safety (SB-S) for the Cockpit SB-S is a comprehensive upgrade of the Classic Aero service, which is a voice and data safety service, used by more than 200 major airlines, jet operators and government agencies, onboard over 13,000 aircraft, processing over 50 million position reports annually. Classic Aero has been the gold standard for aviation safety communications for the past three decades. However, technology has evolved and SB-S promises to revolutionize the safe flight of airplanes through the skies. SB-S has global coverage, abundant capacity, full redundancy, unrivalled cybersecurity, and over 99.9%

availability worldwide, meeting International Civil Aviation Organization (ICAO) GOLD communications and surveillance performance requirements. Refer to the INMARSAT website for further information: https://www.inmarsat.com/

3.1.2 SwiftBroadband (SBB) for the Cabin SwiftBroadband enables passengers to access online services from anywhere in the sky and provides flight crews with real-time information to improve flight operations. SwiftBroadband is secure, functional and compatible with government-grade encryption standards. Delivering up to 432 kbps (AVIATOR 700S configuration), its always on to meet the needs of its customers. SwiftBroadband solutions provide IP data communication capability to the crew and passengers - from full access to on-board router, email, media streaming services to in-seat mobile phone and text services. Refer to the INMARSAT website for further information: https://www.inmarsat.com/

3.1.3 SwiftBroadband Satellites and Coverage Map The INMARSAT Satellite Network provides near-global coverage between +/-76 degrees latitude from satellites in geostationary orbit. The SwiftBroadband satellites are a combination of 4th and 6th generation (I-4, I-6) Inmarsat satellites, nominally located at the following longitudes:

Indian Ocean East Europe, Middle East and Africa (EMEA) 25 degrees East Asia-Pacific Americas 83.7 degrees East 143.5 degrees East 98 degrees West

(IOR)

(APAC)

(AMER) Each satellite provides a large number of overlapping beams (similar to cells) on the earth for users to access the network, similar in operation to terrestrial cellular networks. The part of the earth's surface covered by each satellite is termed its "footprint". COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 16 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual Figure 3-1: INMARSAT SwiftBroadband Coverage 3.2 AVIATOR S SATCOM SYSTEM FUNCTIONS AND FEATURES 3.2.1 System Overview AVIATOR 700S The AVIATOR 700S System services the Cockpit by providing SB-S (refer to section 3.1.1) voice and data connectivity to keep the aircraft connected, even in areas with a high concentration of aircraft. In addition there is a dedicated Cabin Data connection (refer to section 3.1.2) through a separate channel card:

Two simultaneous voice calls supported by multiple aircraft audio configurations. Aircraft Communications, Addressing and Reporting System

(ACARS) and Aeronautical Telecommunication Network Open System Interconnection (ATN/OSI) Data capability for secure message exchanges between Air Traffic Control (ATC), Aeronautical Operational Control (AOC) and Airline Administrative Control (AAC). Cockpit Data connectivity (up to 432 kbps) for Electronic Flight Bag (EFB) applications keeping the crew informed and up-to-date at all times. Cabin Data connectivity (up to 432 kbps) for Cabin Router or In-Flight Entertainment (IFE) applications. Figure 3-2: AVIATOR 700S SATCOM System COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 17 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 3.2.2 Configuration The AVIATOR S SATCOM System configuration is managed by loading Owner Requirement Tables (ORT) via the Airborne Data Loader (ADL) or Portable Dataloader (PDL). The configuration is made up of two parts (separate ARINC 665 [A665] Media):

Secure ORT User ORT The Secure ORT is typically managed by the aircraft manufacturer and forms part of the certified installation. The Secure ORT configures the AVIATOR S SATCOM System for a specific aircraft configuration. The User ORT is typically managed by the airline or aircraft operator. The User ORT does not form part of the certified aircraft configuration, but is often important in ensuring the system operates in the desired way. Changes to the User ORT may be frequent, potentially based on aircraft route or charter. The User ORT also defines the phonebook/directory available to the crew with a list of pre-programmed numbers with associated call priority (refer to section 3.3.1). A laptop computer with an installation of the ORT Tool may be used to modify and create ARINC 665 [A665]

media for use with the ADL/PDL. Refer to the ORT Tool User Guides [SORT_UG][UORT_UG] for further guidance. 3.3 SAFETY VOICE SERVICES 3.3.1 Call Priorities - Ground-to-Air (G2A) In order to keep communication towards the aircraft (including voice calls) controlled and secure, a particular Aircraft (identified by its ICAO address) may be reached by placing a call through a two-stage dialer managed by SITA or ARINC (CSP). In order to access these services, the caller (or organization) must be registered (for billing purposes) with the selected Communication Service Provider (CSP) in order to be granted access in the form of a unique pin code(s). Calls placed over the SB-S network require a call priority1 and is selected by the calling parting at the time of dialing. In some cases, a unique pin code may be linked to a particular call priority. Table 3-1: Call Priorities Description Emergency / Distress High / Safety Low / Company / Non-Safety Priority Level Highest Priority Number P1/Q15 P2/Q12 P3/Q10 Public Lowest P4/Q9 Public priority calls may not be permitted to reach the cockpit and may be disabled through User ORT configuration (refer to section 3.2.2). 1 Refer to the ICAO document [SVGM] for further clarification of the call priority definition. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 18 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 3.3.2 Call Priorities - Air-to-Ground (A2G) Calls initiated by the crew on-board the aircraft are assigned a call priority (refer to Table 3-1), typically selected on the CDU before initiating the call. The default call priority is configured by Secure ORT configuration. Outgoing Public priority calls may not be permitted and may be disabled through User ORT configuration (refer to section 3.2.2). 3.3.3 Pre-emption Four levels of call priority (described in section 3.3.1) allows for call pre-emption2, where an incoming call may only reach and alert the crew when all the available channels are in-use and the incoming call priority is higher than the current active calls. When a lower priority call is pre-empted, the CDU will display the updated incoming call information. 3.4 SAFETY DATA SERVICES 3.4.1 ACARS Data One of the fundamental communication systems in the aircraft is the Aircraft Communications, Addressing and Reporting System (ACARS). This messaging system, managed by the Communication Management Unit (CMU), is key to the efficient and safe operation of the aircraft on the ground as well as in the air. The CMU may select between various communication systems on-board in order to send ACARS messages, one of those being the AVIATOR S SATCOM System. The benefit of the INMARSAT SB-S network is the improved speed, availability and reliability over the legacy VHF, UHF and Classic Aero systems. The ACARS data connection is connected to the AVIATOR S Aircraft Control Domain (ACD) which segregates this and all other secure data streams from the AISD (EFB) data traffic. All ACARS data exchanged with the ground network is secured via a Virtual Private Network (VPN). Refer to [GOLD] for further information regarding data link operations and capabilities. 3.5 NON-SAFETY DATA SERVICES 3.5.1 Electronic Flight Bag (EFB) The EFB data connection is connected to the AVIATOR S Airline Information and Services Domain (AISD) Ethernet port, which segregates AISD (EFB) data traffic from the secure data streams (ACD). AISD Clients are required to have a known static IPv4 configuration (defined by User ORT) for its Ethernet interface in order to access a routed and network address translated (NAT) Background Class data connection. A Simple Network Management Protocol (SNMP) interface provides the capability for retrieving AVIATOR S SATCOM System and operational status information as well as link status and history (refer to Appendix A). 2 Refer to the ICAO document [SVGM] for further clarification on call pre-emption. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 19 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 3.5.2 Cabin Data The cabin data connection is connected to the AVIATOR S Passenger Information and Entertainment Services Domain (PIESD) Ethernet port which segregates PIESD (cabin) data traffic from all other data streams (ACD, AISD). A Point-to-Point Protocol over Ethernet (PPPoE) capable client is required to access the PIESD channel card. The cabin router is responsible for managing the data connection availability and Quality of Service (QoS). A Simple Network Management Protocol (SNMP) interface provides the capability for retrieving AVIATOR S SATCOM System and operational status information as well as link status and history (refer to Appendix B). An out-of-band control interface provides status monitoring of established SB packet data connections as well as connection control using AT-commands over a Telnet/TCPIP/Ethernet connection (refer to section 9.2.4). Out-of-band refers to the control session being independent of the PPPoE session carrying the user data. Refer to Appendix D for the list of supported AT-commands. The PIESD Ethernet port and related services may be configured through the User ORT (see section 3.2.2). 3.5.2.1 Service Class The INMARSAT non-safety SwiftBroadband (SBB) network provides two classes (types) of data connections:

Background Class o A pay per usage service where the user is charged per Megabyte (MB) for the combined amount of data transferred (both the upload/download directions). o The maximum data rate (speed) is determined by the class of system installed:

AVIATOR 700S | Class 6 | Up to 432 kbps o Background Class is a contended service where a number of users (aircraft) may share network resources. The network manages the available resources to ensure best effort for all users within the same region. Streaming Class o A pay per minute service where the user is charged for the time duration of the connection. o The available data rates (speed) are class specific:

AVIATOR 700S | Class 6 8/16/32/64/128 kbps X-Stream/Half-HDR/Full-HDR 3 o Data rates for the download/upload (forward/return) direction may be symmetric (identical) or asymmetric (different). 3.5.2.2 Service Class Selection The default4 PPPoE service class may be configured through the User ORT (refer to section 3.2.2). If preferred, the user may select a specific service class when creating the PPPoE (refer to section 9.2.3). 3 If required, check with your selected CSP for activation of these high data rate services. 4 The User ORT configured default is used when a PPPoE connection is created using a blank (empty) service name field. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 20 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 4 SERVICE ACTIVATION In order to access the INMARSAT SB-S/SBB Network, an active service agreement is required between the aircraft owner/operator and a Communication Service Provider (CSP):

SwiftBroadband-Safety (SB-S) | Flight Deck Services:

o Primary ARINC DIRECT https://www.arincdirect.com SITA https://www.sita.aero o Regional China Transport Telecommunications & Information Centre (CTTIC) SwiftBroadband (SBB) | Passenger Services o Primary ARINC DIRECT https://www.arincdirect.com SITA https://www.sita.aero o Regional China Transport Telecommunications & Information Centre (CTTIC) The CSP and the appointed Airline Designator/Device Sponsor (See section 4.2) will require the following information during the activation process:

AVIATOR S Information o System Type AVIATOR 700S (Class 6) o SIM Card Information International Mobile Subscriber Identity (IMSI) IMSI 0 is for Cockpit Voice and Data IMSI 1 is for Cabin Data IMSI 2 is reserved for future use IMSI 3 is reserved for future use

| ACD + AISD

| PIESD o Smart Card Information The smart card serial number for the PKI Security Certificate

| ACD Aircraft or Owner Information International Civil Aviation Organization (ICAO) Address o o Registered Aircraft Identity | Tail Number o Billing information As an outcome of the activation process, the CSP must provide the permitted Access Point Name (APN) for the AVIATOR S EFB (AISD) connection. The APN provided by the CSP must be configured in the User ORT

(refer to section 3.2.2). COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 21 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 4.1 IMSI AND SMART CARD INFORMATION The IMSI and smart card information is typically available through the following methods:

Documentation included with the Satellite Data Unit (SDU) Configuration Module (SCM) SATCOM->CDU Screens reflecting the IMSI and Smart Card information Label information on the SCM itself (see Figure 4-1) Figure 4-1: AVIATOR S SCM | IMSI & Smart Card Identification 4.2 PUBLIC KEY INFRASTRUCTURE (PKI) SECURITY CERTIFICATE SwiftBroadband Safety security measures include a smart card inserted into each SCM, used to authenticate the AVIATOR S SATCOM System when connecting to the INMARSAT SB-S network. A valid digital public key infrastructure (PKI) security certificate is required before SB-S connectivity is available. The User ORT configured Airline Designator (See section 3.2.2) will receive a certificate signing request

(CSR) when the AVIATOR S SATCOM System has successfully acquired the satellite and attempts to authenticate SB-S services. The Airline Designator will appoint a Device Sponsor who is responsible for the issuing of the PKI certificate. Once the Device Sponsor has issued the certificate, the AVIATOR S SATCOM System will automatically retrieve the certificate, allowing SB-S services to proceed. Refer to the INMARSAT PKI - Airline Ops Handbook [PKI_OPS] and the INMARSAT PKI Concept of Operations [PKI_CON] for more details regarding PKI activation and usage. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 22 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 5 INTERPRETING THE SYSTEM STATUS This User Manual provides operational descriptions to allow flight crew to manage the AVIATOR S SATCOM System. Depending on the aircraft configuration, the control & display unit installed may be slightly different to the representations provided in this section. Multi-purpose Control and Display Unit Figure 5-1: ARINC 739A MCDU The SAT-PHONE pages are accessed by pressing the <SAT prompt from the MCDU main menu (Figure 5-1). Depending on the Aircraft configuration a different LSK location may be used. Refer to Figure 5-2 for the MCDU display unit menu tree. Figure 5-2: SATCOM Page Layout COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 23 of 99 CC: 1

(T: 99-161853-I) SAT-PHONE1/2SAT-PHONE2/2DIRECTORY INDEX X/YDIRECTORYX/YSBBBITESAT-LOGX/2CONFIGX/5BITE SCANNINGPASTLEGSGROUNDLAST LEGPREVIOUS LEGSPASTREPORT AVIATOR 700S User Manual 5.1 VOICE AVAILABILITY The AVIATOR S voice availability status indicates when the system is able to initiate a voice call. The availability status is associated to the voice channel number:

MCDU: SAT-PHONE page 1 of 2, SAT-1 for the first5 voice channel, and SAT-2 for the second voice channel. 5.1.1 Not Ready When the AVIATOR S SATCOM System and/or other aircraft systems (e.g. navigation data) are initializing or unable to provide service:

MCDU: SAT-PHONE page 1 of 2, SAT-1 and SAT-2 status indicates NOT READY (See Figure 5-3). Figure 5-3: MCDU - SAT-PHONE 1/2 - NOT READY To establish a cause for the NOT READY state, navigate to the pages described further in the following sections:

MCDU: Press NEXT/PREV PAGE key on the MCDU to display the SAT-PHONE page 2 of 2 (See Figure 5-4). Figure 5-4: MCDU - SAT-PHONE 2/2 5 The preferred Cockpit Audio Channel is Secure ORT configurable. Refer to [SORT_UG] for further configuration guidance. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 24 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 5.1.2 Safety Voice Services - Ready When the AVIATOR S SATCOM System has successfully acquired and registered on the INMARSAT network:

MCDU: SAT-PHONE page 1 of 2 SAT-1 and SAT-2 status indicates READY (See Figure 5-5). The AVIATOR S SATCOM System is now able to make or receive safety voice calls. Figure 5-5: MCDU - SAT-PHONE - Ready 5.1.3 Safety Data Services - Available When the AVIATOR S SATCOM System has created the virtual private network (VPN) (described in section 3.4.1), the Ground Earth Station (GES) assigned6 by the INMARSAT network is displayed on the:

MCDU: Press LSK-L2 on SAT-PHONE page 2 of 2 (Figure 5-4)SAT-LOG page 1 of 2 at position LSK-L4

(Figure 5-6). Refer to section 8.1 for further information. Figure 5-6: MCDU - SAT-LOG 1/2 - Safety Data Available 6 The SwiftBroadband GES is not user selectable as in Classic Aero systems. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 25 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 5.2 SWIFTBROADBAND (SBB) SERVICE AVALABILITY When the AVIATOR S SATCOM System has successfully acquired and registered on the INMARSAT network the current status and SwiftBroadband services may be reviewed by navigating to the:

MCDU: SAT-PHONE page 2 of 2SBB page (See Figure 5-7) by pressing LSK-L3 (see Figure 5-4). Figure 5-7: MCDU - SBB - Service Availability CS Voice:

- NOT AVAILABLE

- AVAILABLE PS Voice:

- NOT AVAILABLE

- AVAILABLE ACARS:

IDLE

- WAITING CMU

- WAITING VPN

- LOGGED OFF

- LOGGED ON SEC GW:

- LOGGED OFF

- ENROLLING

- LOGGING ON

- LOGGED ON Circuit Switched voice service is currently not available. Ensure the system is Logged On to the Satellite. Refer to the SATCOM Log page, section 5.3. Circuit Switched voice service is available. Packet Switched voice service is currently not available. Ensure the system is Logged On to the Satellite and the SEC GW is LOGGED ON. Refer to the SATCOM Log page, section 5.3. Packet Switched voice service is available. ACARS service is not active. Ensure the system is Logged On to the Satellite. Refer to the SATCOM Log page, section 5.3. No CMU is detected. For further troubleshooting, refer to BITE, section 10.1. A logon request has been sent. Waiting for the response from ground. ACARS Data service is currently not available. Ensure the system is Logged On to the Satellite. Refer to the SATCOM Log page, section 5.3. ACARS data service is available. Security Gateway service is currently not available. Ensure the system is Logged On to the Satellite. Refer to the SATCOM Log page, section 5.3. Security Gateway has initiated a request for the initial PKI certificate. Refer to section 4.2, Public Key Infrastructure (PKI) Security Certificate. Security Gateway service is establishing the connection. Security Gateway service is available. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 26 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 5.3 SATCOM LOG Navigate to the SATCOM LOG page for further satellite network status and management functions:

MCDU: SAT-PHONE page 2 of 2SAT-LOG page by pressing LSK-L2 (Figure 5-4). 5.3.1 Logging On/Logged On/Logged Off/Standby/Rejected View the status of the connection to the INMARSAT satellite shown at LSK-L2 on the MCDU. The system will perform an automatic (AUTO) log on after initial power on (Figure 5-8, Figure 5-9). By pressing LOG-OFF (LSK-R6 on MCDU), the AVIATOR S SATCOM system will disconnect from the INMARSAT network, and all services are unavailable (Figure 5-10). This is termed a manual log off. Press AUTO LOG-ON (LSK-R5 on MCDU) to reconnect to the INMARSAT network. The system status will indicate LOGGING ON while reconnecting, followed by the LOGGED ON status when complete. Refer to section 6 for additional guidance relating to a manual log on procedure. If the IMSI is not activated with a Communication Service Provider (CSP), the SATCOM is unable to register on the satellite network. The status REJECTED is displayed (Figure 5-11). Figure 5-8: MCDU - SAT-LOG 1/2 - Status -

Figure 5-9: MCDU - SAT-LOG 1/2 - Status -

Logging On Logged On Figure 5-10: MCDU - SAT-LOG 1/2 - Status -

Figure 5-11: MCDU - SAT-LOG 1/2 - Status -

Logged Off Rejected COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 27 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 5.3.2 SATCOM INOP When the AVIATOR S SATCOM System has an error and unable to provide service, the voice channel status will indicate that calls are not possible (refer to section 5.1.1). By accessing the SATCOM Log page, the system will indicate if it is attempting to log on or has declared a fault condition with the status SATCOM INOP (See Figure 5-12). Further troubleshooting to determine the failure related to the SATCOM INOP state may be performed via the BITE pages as per section 10.1. Figure 5-12: MCDU - SAT-LOG 1/2 - Status - SATCOM INOP 5.3.3 ICAO The SATCOM Log page 2 of 2 provides the active ICAO address for activation or troubleshooting purposes

(See Figure 5-13):

MCDU: Press NEXT/PREV PAGE key on the MCDU to display the SAT-LOG page 2 of 2 (See Figure 5-13). Figure 5-13: MCDU - SAT-LOG 2/2 - ICAO COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 28 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 6 SATELLITE SELECTION 6.1.1 Log Off & Auto/Manual Log On The INMARSAT satellite used by the AVIATOR S SATCOM system can be automatically or manually selected through the SATCOM Log page. Typical system configuration is to perform automatic (AUTO) logon. When the aircraft is operating in a region where more than one satellite may be used, a situation may arise where the current satellite is not the preferred satellite. An example of this would be a known flight path where a particular satellites footprint does not provide full coverage, and switching to an alternate satellite may provide extended coverage without the need for changing satellites, termed an ocean region change (ORC), mid-flight or at an inconvenient time or position. The selected satellite may be modified through the following sequence:

1. LOG-OFF from the SAT-LOG 1/2 page by pressing LSK-R6 on the MCDU (Figure 5-9). 2. Once in the LOGGED OFF state, modify the selected satellite page by pressing LSK-L3 on the MCDU. 3. Once the desired satellite is displayed, the decision must be made to perform an AUTO or MANUAL LOG-ON on by one of the following:

a. Pressing AUTO LOG-ON from the SAT-LOG 1/2 page for MCDU (Figure 5-10). i. The AVIATOR S SATCOM System will select the INMARSAT satellite. b. Pressing MANUAL LOG-ON from the SAT-LOG 1/2 page for MCDU (Figure 5-10). i. The crew must select the desired INMARSAT satellite. 6.1.2 Ocean Region Change (ORC) An ocean region change (ORC) occurs when the AVIATOR S SATCOM System transitions from one satellite coverage area into another. This action may be performed manually or automatically as described in section 6.1.1. In both cases, voice and data services are disconnected for the duration of time the AVIATOR S SATCOM System requires to complete the ORC. When the aircraft flight path or position has left the coverage area of the current satellite, the system will experience a loss of signal scenario and automatically search for alternate satellites that may be in view, or attempt to re-acquire the satellite that was lost in order to resume communications. When the AVIATOR S SATCOM System experiences loss of coverage (no signal), the MCDU display will indicate NOT READY as described in section 5.1.1. In a typical ORC scenario, voice and data services may be restored in under 5 minutes. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 29 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 7 SAFETY VOICE SERVICES The AVIATOR S SATCOM System supports up to two simultaneous voice calls (incoming/outgoing/mixed) and various aircraft audio configurations:

1) Audio via the Audio Control Panel (ACP) and call management functions performed via the Multi-

purpose Control and Display Unit (MCDU). Refer to section 7.1. 7.1 MCDU INTERFACE 7.1.1 Outgoing Calls - Air-to-Ground (A2G) In order to place an outgoing call, often referred to as an Air-to-Ground call, the crew can choose between:

Manual Entry - a phone number7 or short code8 may be entered via the MCDU (Figure 7-1, Figure Directory Dial - select the identity from the directory list defined by User ORT (see section 3.2.2 for 7-2), 7.1.1.1 Manual Entry ORT Configuration). 1. From the SAT-PHONE page 1 of 2 enter the destination number into the scratchpad (max 18 digits) and press LSK-L1 to pre-select the number to SAT-1 or LSK-L4 to SAT-2:

a) International number - must begin with the prefix 00 followed by the country code (Figure 7-1). The + character is not accepted. b) Short code - must be 2 to 6 digits in length (Figure 7-2) 2. The default call priority is applied each time a new manual entry is performed. To modify the call priority, press LSK-R1/R4 to toggle through the available9 call priorities. a) The default call priority is configurable by Secure ORT. Refer to section 7.1.1.3 for guidance on dialing/initiating the call. Figure 7-1: MCDU - SAT-PHONE 1/2 - Manual Figure 7-2: MCDU - SAT-PHONE - Manual Entry -

Entry - International Number - Scratchpad Short Code - Pre-selected 7 User ORT configuration may limit manual dialing to short codes only. 8 A short code number is defined as between 2 and 6 digits. 9 Outgoing Public priority calls may be disabled by User ORT configuration. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 30 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 7.1.1.2 Directory Dial NOTE: The directory group names and entries are User ORT configurable and may differ from the examples. 1. From the SAT-PHONE page 1 of 2, press LSK-R3 to enter the SAT DIRECTORY INDEX page 1 of 2

(Figure 5-5). 2. Press the LSK matching the group name to be accessed. a. For example, press LSK-L2 to access the HIGH group (Figure 7-3). 3. Browse the directory using the NEXT/PREV PAGE keys to display the various pages of the directory. a. The current page / total page count is shown in the top right corner of the display. 4. Once the desired entry name is displayed on the screen press the corresponding LSK-L to pre-select the entry to SAT-1, or LSK-R to SAT-2. a. For example, press LSK-L3 to pre-select the third entry in the list to SAT-1 (Figure 7-4). Refer to section 7.1.1.3 for guidance on dialing/initiating the call. Figure 7-3: MCDU - SAT DIRECTORY INDEX 1/2 Figure 7-4: MCDU - SAT DIRECTORY X/Y COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 31 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 7.1.1.3 Initiating an Outgoing Call Once the outgoing calling information has been pre-selected (Figure 7-5) as described in sections 7.1.1.1 the call can be initiated by pressing the associated audio channel MAKE CALL button on the MCDU, LSK-L1 for SAT-1 or LSK-L4 for SAT-2. In order to hear the SATCOM audio, the appropriate SAT audio channel must also be selected on the ACP. Once the call has been initiated, the SAT-PHONE page 1 of 2 will display the call progress:

DIALING (Figure 7-6)

- The number has been dialed and a connection to the called party is being attempted. RINGING (Figure 7-7)

- Ringing may be heard by the crew before the call is answered.

- The call may be cancelled by pressing the associated audio channel END CALL button on the MCDU, LSK-L1 for SAT-1 or LSK-L4 for SAT-2. ANSWERED (Figure 7-8)

- The connection to the called party has been established.

- Voice communication between the two parties is now possible using the ACP to control the audio path and volume functions. Figure 7-5: MCDU - SAT-PHONE 1/2 - Outgoing Figure 7-6: MCDU - SAT-PHONE 1/2 - Outgoing Call - Make Call Call - Dialing Figure 7-7: MCDU - SAT-PHONE 1/2 - Outgoing Figure 7-8: MCDU - SAT-PHONE 1/2 - Outgoing Call - Ringing Call - Answered COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 32 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual In some instances, the call may not be connected and the SAT-PHONE page 1 of 2 SAT channel will display CALL FAILED (Figure 7-9). Ensure the number entered is correct and press MAKE CALL to redial. Figure 7-9: MCDU - SAT-PHONE 1/2 - Outgoing Call - Call Failed 7.1.1.4 Ending an Outgoing Call Calls may be ended (terminated) by either the calling party (airborne side) or the called party (ground side):

To release the call from the airborne side using the MCDU press the associated audio channel (SAT-

1/2) END CALL button on the MCDU, LSK-L1 for SAT-1 or LSK-L4 for SAT-2 (Figure 7-10).

- Call ended side tone may be heard by the crew.

- The SAT-PHONE page 1 of 2 SAT channel will return to READY, with an additional status line indicating CALL ENDED. This status will automatically clear after 20 seconds, but may also be cleared by pressing CLR STATUS at LSK-L1 for SAT-1 or LSK-L4 for SAT-2 (Figure 7-11). To release the call from the airborne side using the ACP press the END CALL button on the ACP10.

- Call ended side tone may be heard by the crew.

- The SAT-PHONE page 1 of 2 SAT channel will return to READY, with an additional status line indicating CALL ENDED. This status will automatically clear after 20 seconds, but may also be cleared by pressing CLR STATUS at LSK-L1 for SAT-1 or LSK-L4 for SAT-2 (Figure 7-11). When released from the ground side:

- Call ended side tone may be heard by the crew.

- The SAT-PHONE page 1 of 2 SAT channel will return to READY, with an additional status line indicating CALL ENDED. This status will automatically clear after 20 seconds, but may also be cleared by pressing CLR STATUS at LSK-L1 for SAT-1 or LSK-L4 for SAT-2 (Figure 7-11). Figure 7-10: MCDU - SAT-PHONE - Ending a call Figure 7-11: MCDU - SAT-PHONE - Call ended 10 Secure ORT Configuration Option. Refer to the [SORT_UG] for additional configuration guidance. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 33 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 7.1.2 Incoming Calls - Ground-to-Air (G2A) 7.1.2.1 Cockpit Alerting As described in section 3.3.1, calls towards the aircraft may only be placed through controlled access measures. When a call reaches the aircraft, it may alert the crew:

1. Audibly - though a single stroke chime11 2. Visually - Call information displayed on the SATCOM->MCDU page (Figure 7-12).

- The audio channel (SAT-1/2) call indication on the ACP.

- Aircraft fitted with an Engine Indication and Crew Alerting System (EICAS), Flight Warning System (FWS) or similar function will receive notification relevant to the call priority. 7.1.2.2 Identifying the calling party and priority When an incoming call (G2A) is in the alerting (ringing) phase, the SAT-PHONE page 1 of 2 will display the incoming call priority and the identity of the calling party:

Call Priority

- Refer to section 3.3.1, Table 3-1. Caller Identity

- The calling parties phone number is displayed when the number does not exist in the directory.

- When the calling parties number is in the directory, the associated identity is displayed in

place of the number. If the calling party has disabled their phone number presentation, the caller identity line is blank. Figure 7-12: MCDU - SAT-PHONE - Incoming Call - Caller Identity 11 In some aircraft, the chime alert (managed external to the AVIATOR S system) may be inhibited during critical phases of flight. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 34 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 7.1.2.3 Answering an Incoming Call An incoming call may be answered in multiple ways:

1. To answer the call, press the associated audio channel (SAT-1/2) ANSWER button on the MCDU, LSK-

L1 for SAT-1 or LSK-L4 for SAT-2 (Figure 7-13).

In order for the calling party (ground side) to hear the SATCOM audio, the appropriate SAT audio channel must also be selected on the ACP.

- Voice communication between the two parties is now possible using the ACP to control the audio path and volume functions.

- The SAT-PHONE page 1 of 2 status will show ANSWERED (Figure 7-14). 2. Press the associated audio channel (SAT-1/2) on the ACP.

- The ACP SAT call button will stop flashing and show steady state indicating the SAT channel is active and connected.

- Voice communication between the two parties is now possible using the ACP to control the audio path and volume functions.

- The SAT-PHONE page 1 of 2 status will show ANSWERED (Figure 7-14). 3. If the SAT-1/2 channel that is being alerted (as per 7.1.2.1) is already selected on the ACP, the incoming call is automatically answered12.

- Voice communication between the two parties is now possible using the ACP to control the audio path and volume functions.

- The SAT-PHONE page 1 of 2 status will show ANSWERED (Figure 7-14). Figure 7-13: MCDU - SAT-PHONE - Incoming Call Figure 7-14: MCDU - SAT-PHONE - Incoming Call

- Answer

- Answered 12 Secure ORT Configuration Option. Refer to the [SORT_UG] for additional configuration guidance. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 35 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 7.1.2.4 Rejecting an Incoming Call An incoming call may be rejected by pressing the associated audio channel (SAT-1/2) REJECT button on the MCDU, LSK-L2 for SAT-1 or LSK-L5 for SAT-2 (Figure 7-13). The SAT-PHONE page 1 of 2 SAT channel will return to READY, with an additional status line indicating CALL ENDED. This status will automatically clear after 20 seconds, but may also be cleared by pressing CLR STATUS at LSK-L1 for SAT-1 or LSK-L4 for SAT-2. Figure 7-15: MCDU - SAT-PHONE - Incoming Call - Rejected 7.1.2.5 Ending an Incoming Call Refer to section 7.1.1.4, Ending an Outgoing Call. 7.1.2.6 Preemption When pre-emption occurs (see section 3.3.3), one of the active calls is disconnected and the SAT-PHONE page 1 of 2 SAT-1/2 channel status will briefly show PREEMPTED (Figure 7-16) followed by presentation of the caller identity (Figure 7-17). Answering a preempted call is as per section 7.1.2.3, Answering an Incoming Call. Figure 7-16: MCDU - SAT-PHONE - Incoming Call Figure 7-17: MCDU - SAT-PHONE - Incoming Call

- Preempted

- Preemption Caller ID COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 36 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 8 SAFETY DATA SERVICES 8.1 ACARS DATA This messaging system is automatically managed by the Communication Management Unit (CMU) and requires no crew interaction through the CDU SATCOM pages13 provided that:

1. The system is Logged On (Auto or Manual) as described in section 6.1.1, 2. The Ground Earth Station (GES) assigned by the INMARSAT network is displayed on the SATCOM LOG page at position LSK-L4 for MCDU (Figure 8-1):

a. XXX-BRM b. XXX-PMLU c. XXX-LNDN

(BURUM)

(PAUMALU)

(LONDON14) NOTE: XXX is the octal GES ID number (e.g. 274). Figure 8-1: MCDU - SAT-LOG - ACARS Data Available 13 The CMU may be accessed by its own dedicated MCDU pages or HMI. 14 The London site is restricted for test purposes only. Operational aircraft will use Burum and Paumalu. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 37 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 9 NON-SAFETY DATA SERVICES 9.1 ELECTRONIC FLIGHT BAG (EFB) CONNECTIVITY The AVIATOR S Airline Information and Services Domain (AISD) provides a routed Ethernet interface with access to a Background Class connection that is managed by the Aircraft Control Domain (ACD). When enabled by Secure ORT (see section 3.2.2), this domain provides segregated data capability to the cockpit for EFB applications via a dedicated Ethernet interface. ACD Voice and data traffic has a higher priority than AISD data traffic, ensuring that all SB-S functions are not impacted by AISD data requests. The AISD/EFB data connection availability is linked to the ACD connectivity state:

When the AVIATOR S ACD is logged on the AISD data connection is active. Similarly, when the AVIATOR S ACD is logged off the AISD data connection is inactive. Refer to section 6.1.1 for further guidance regarding logging off/on. The AISD/EFB Ethernet interface provides read only access to a Simple Network Management Protocol

(SNMP) for retrieving AVIATOR S SATCOM System and operational status information as well as link status and history. Refer to Appendix A for the list of available Object Identifiers (OIDs). For further guidance, refer to the [UORT_UG] for configuration of the AISD/EFB data connection. 9.2 CABIN DATA CONNECTIVITY The cabin data connection, connected to the AVIATOR S Passenger Information and Entertainment Services Domain (PIESD) Ethernet port, segregates PIESD (cabin) data traffic from all other data streams through a separate channel card, only available in the AVIATOR 700S system configuration. The Cabin Data connection availability is however linked to the ACD connectivity state:

When the AVIATOR S ACD is logged on the PIESD data connection will be active. Similarly, when the AVIATOR S ACD is logged off the PIESD data connection will be inactive. Refer to section 6.1.1 for further guidance regarding logging off/on. Additionally, cabin audio communication can be enabled/disabled through the SAT-LOG page by:

MCDU: Pressing LSK-R4 to toggle the Cabin Comm state (Figure 9-1 & Figure 9-2)15. The PIESD Ethernet interface provides read only access to a Simple Network Management Protocol (SNMP) for retrieving AVIATOR S SATCOM System and operational status information as well as link status and history. Refer to Appendix B for the list of available Object Identifiers (OIDs). 15 Cabin Comm enable/disable functionality is only visible in the AVIATOR-700S system configuration when PIESD is enabled by Secure ORT configuration. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 38 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual Figure 9-1: MCDU - SAT-LOG- Cabin Comm Figure 9-2: MCDU - SAT-LOG - Cabin Comm enabled disabled 9.2.1 PPPoE Connections A Point-to-Point Protocol over Ethernet (PPPoE) capable client is required to access the PIESD channel card. The cabin router is responsible for managing the data connection availability and Quality of Service (QoS). PPPoE Access allows a Client to obtain one or more dedicated data connections, not shared by other users on the aircraft, with direct control over the key characteristics of each connection:

Choose the Class (Background or Streaming Class) of every connection, and the required bit rate for each Streaming Class Packet Data Protocol (PDP) context. Associate and direct the data for a particular application to go over a specific connection. Individual connections may then be optimised for their intended use, for example by setting up one Background Class connection for browsing and e-mail and another simultaneous Streaming Class connection for audio or video applications. Select a specific network Access Point Name (APN) specified by the Communication Service Provider

(CSP), as opposed to the default configured by the System Administrator. (APNs are the gateways available to access the Internet, and a CSP may allocate these depending on specific service or performance requirements.) Access services which require authentication by the CSP. Change or modify the connection type and bandwidths mid-stream as required. Create secondary PDP contexts and Traffic Flow Templates (TFT). It is assumed that the user is familiar with the concepts outlined in [3GPP_TS27], and has a working knowledge of the Hayes AT command set. There is a one-to-one mapping between each PPPoE connection and each primary PDP context activated by the AVIATOR S SATCOM system. A maximum of 11 PDP contexts is supported, comprising of both primary and secondary contexts. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 39 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 9.2.2 Connection Authentication User Authentication may be required for some connections. In such cases, a user name and password may be supplied in the PPPoE connection instance. Before attempting such connections, the user should verify with their Communication Service Provider (CSP) whether authentication is required for a particular service or type of IP address. The AVIATOR S SATCOM System supports the exchange of a username and password during the PPPoE/PPP negotiation (IPCP Phase) using PAP/CHAP authentication. 9.2.3 PPPoE Service Name A PPPoE service name may be used to customize the connection type, properties and quality-of-service (QoS) by specifying a series of AT strings or parameters in the Service Name field of by the PPPoE client connection properties (the connecting device). When the service name is left blank/empty, User ORT configured defaults are used in order to create the PDP context with known properties. Refer to Table 9-1 for the list of supported service name options. As an alternative to a predefined service name option, the PPPoE client may define the full AT string. The letters AT must be present and the command string needs to specify both the CGEQREQ and CGEQMIN to ensure the desired QoS is provided. See [A781] section 3.3.11.3.1. Example:

SBB:AT+CGDCONT=1,bgan.inmarsat.com;+CGEQREQ=1,1,64,64,64,64;+CGEQMIN=1,1,64,64,64,64 COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 40 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual Table 9-1: PPPoE Service Name Options IP Service Service Name Option Description IP Background SBB:BACKGROUND Places a Primary Background PDP Context 8 kbps Streaming SBB:STREAM8K 16 kbps Streaming SBB:STREAM16K 32 kbps Streaming SBB:STREAM32K 64 kbps Streaming SBB:STREAM64K 128 kbps Streaming SBB:STREAM128K BGAN X-Stream SBB:XSTREAM Places a Primary Streaming class PDP Context at the data rate of 8 kbps. Places a Primary Streaming class PDP Context at the data rate of 16 kbps. Places a Primary Streaming class PDP Context at the data rate of 32 kbps. Places a Primary Streaming class PDP Context at the data rate of 64 kbps. Places a Primary Streaming class PDP Context at the data rate of 128 kbps. Places a Primary Streaming class PDP Context with a dedicated 200 kHz bearer. Elevation angle dependant, with max data rate of 512 kbps. HDR Half symmetric N/A No SBB Option Name defined. Use AT-Commands. HDR Full symmetric N/A No SBB Option Name defined. Use AT-Commands. HDR Half asymmetric N/A No SBB Option Name defined. Use AT-Commands. HDR Full asymmetric N/A No SBB Option Name defined. Use AT-Commands. 9.2.4 Connection Control using TELNET 9.2.4.1 Primary PDP Contexts Primary PDP contexts must be created through the establishment of a PPPoE connection between the AVIATOR S SATCOM System and the Client. 9.2.4.2 Secondary PDP Contexts Secondary PDP contexts are used if differentiated QoS characteristics are desired for different traffic types. Although they share the APN and IP address of the primary PDP context to which they have been associated, each secondary PDP context may be specified to have a different QoS. A Traffic Flow Template (TFT) must be specified for each secondary PDP context to inform both the network and the AVIATOR S SATCOM System about the different types of traffic filter to each PDP context. All traffic that is not explicitly filtered (tied) into a secondary PDP context is sent via the associated primary PDP context by default. Different traffic types are typically identified by application (strictly protocol type), although filtering by IP address and TCP/UDP port numbers is also possible. Secondary PDP Contexts and associated Traffic Flow Template (TFT) may be created, modified, activated and de-activated using the out-of-band control interface. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 41 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 9.2.4.3 Out-of-band Control Port Connection and Configuration The out-of-band control port is User ORT configurable (refer to section 3.2.2). The following parameters must have a known configuration to connect to the interface:

AVIATOR S PIESD Ethernet interface IPv4 IP address AVIATOR S PIESD Ethernet interface IPv4 subnet mask

AVIATOR S PIESD Out-of-band control/TELNET port number |

192.168.0.200 (Default Value) 255.255.255.0 (Default Value) 22222

(Default Value) A TELNET client/application is required to connect to the out-of-band control port at the configured IP address and port number. The client/application must be connected to the PIESD Ethernet interface with static IPv4 configuration in the defined subnet. 9.2.4.4 List of Supported AT-Commands The out-of-band control interface provides status monitoring as well as connection control using 3G/INMARSAT AT-commands over a Telnet/TCPIP/Ethernet connection. Out-of-band refers to independent of the PPPoE session carrying the user data. Table 9-2 lists the AT-commands supported by the AVIATOR S PIESD out-of-band control interface. Refer to Appendix D for the detailed definition of each AT-command. Table 9-2: AVIATOR S Supported AT-Commands AT-Command Description

+CLAC List all available AT-commands E

+CGMI

+CGMM

+CGMR

+CGSN

+CIMI _IPDPS Local Echo Request Manufacturer Identification Request Model Identification Request Revision Identification Request Product Serial Number Identification Request International Mobile Subscriber Identity Binding Telnet session to PPPoE context

+CGDCONT Define PDP Context (Read only)

+CGDSCONT Define Secondary PDP Context

+CGTFT Traffic Flow Template

+CGEQREQ 3G Quality of Service Profile, Requested

+CGQREQ 2G Quality of Service Profile, Requested

+CGEQMIN 3G Quality of Service Profile, Minimum

+CGEQNEG 3G Quality of Service Profile, Negotiated

+CGACT PDP Context Activate or Deactivate

+CGCMOD PDP Context Modify

+CGPADDR Show PDP Address COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 42 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 9.2.4.5 Binding to an active Primary PDP context Before being able to modify, control or add a secondary PDP to a primary PDP context, the TELNET session needs to be linked to a primary PDP through the use of the AT_IPDS AT-command. This indicates that all subsequent AT commands are related to the chosen PPPoE session and related PDP contexts. A connection to the out-of-band control interface must be established as described in section 9.2.4.3. Refer to Appendix D.3.11 for further guidance regarding the AT_IPDPS AT-command. 9.2.4.6 Adding a Secondary PDP Context As described in section 9.2.1, a secondary PDP context and Traffic Flow Template (TFT) may be used to isolate specific traffic types or data that require a different QoS. Example: A 16 kbps streaming class PDP context for UDP type traffic in the port range 50000 to 50005. Method 1 The AT-commands may be sent separately:

AT+CGDSCONT=2,1 Attached a secondary CID to the primary CID number 1. AT+CGEQREQ=2,1,16,16,16,16 Defines the PDP context type and the requested maximum AT+CGEQMIN=2,1,16,16,16,16 Defines the requested minimum QoS. AT+CGTFT=2,1,0,,17,50000.50005 Defines the downlink TFT (UDP port range 50000 to 50005). AT+CGACT=1,2 Activates the secondary PDP context. and guaranteed QoS. Method 2 The AT commands may be sent together, separated by a ;:

AT+CGDSCONT=2,1;+CGEQREQ=2,1,16,16,16,16;+CGEQMIN=2,1,16,16,16,16;+CGTFT=2

,1,0,,17,50000.50005;+CGACT=1,2 9.2.4.7 Traffic Flow Templates A Traffic Flow Template (TFT) is used in conjunction with a secondary PDP context. Multiple TFTs may be linked to the same secondary PDP context, however each must be uniquely identified by:

<packet_filter_identifier>

TFT identifier between 1 & 8. Multiple (max 8) TFTs may be applied to a single secondary. Starts with 1. Does not indicate TFT precedence, only identifier. Multiple TFTs may be added the

<packet_filter_identifier> allowing multiple groups of traffic to be routed to the secondary context. to a single secondary context by incrementing

<evaluation_precedence_index>

The index must be a unique number within all TFTs associated with the same primary PDP. The evaluation precedence index defines the precedence given to a filter when routing traffic. The filter with the precedence index of 0 is the first to be applied; the filter with the precedence index of 1 is next and so on. The lowest possible evaluation precedence index is 255. Traffic that may be applicable to more than one TFT will be routed over the TFT with the highest precedence i.e. whichever TFT is evaluated first. Refer to Appendix D.3.9 for further guidance reading the +CGTFT AT-command. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 43 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 9.2.4.8 Modifying/Scaling of Streaming Class PDP Contexts The requested bit rates of an active Streaming Class PDP context may be re-negotiated, while the context remains active. The Context Identifier (CID) for the connection must be known in order to modify the correct PDP context. To renegotiate a specific PDP context the following AT-command is used:

AT-command: AT+CGEQREQ=<CID#>, <Connection_Class>, <Max_Bitrate_Up>,

<Max_Bitrate_Down>,<Guaranteed_Bitrate_Up>,

<Guaranteed_Bitrate_Down>

AT-response: <echo response of command>

OK Where:

<Connection_Class> is defined by:

1 = Streaming Class, 3 = Background Class

<Max_Bitrate_Up> and <Max_Bitrate_Down> specify the requested Maximum Bitrate (the preferred bitrate).

<Guaranteed_Bitrate_Up> and <Guaranteed_Bitrate_Down> specify the requested Guaranteed Bitrate (acceptable bitrate). After the AT+CGEQREQ command has been sent, the context will not immediately use the rates requested. An additional command is required to modify the context. To action the modification the following AT-command must be used:

AT-command: AT+CGCMOD=<CID#>

AT-response: <echo response of command>

OK At this point, the renegotiation will take place and if successful, the new bitrate request will be applied. Verify that the re-negotiation was successful using the AT+CGEQNEG=<CID#> command. 9.2.4.9 Deactivating PDP contexts Deactivation of a PDP context may be performed using AT-commands. The CID for the connection must be known in order to deactivate the correct primary or secondary PDP context, primary or secondary. To deactivate a specific PDP context the following AT-command may be used:

AT-command: AT+CGACT=0,<CID#>

AT-response: <echo response of command>

OK COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 44 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 10 TROUBLESHOOTING 10.1 BITE In order to troubleshoot the AVIATOR S SATCOM system, navigate to the BITE pages:

MCDU: SAT-PHONE page 2 of 2, LSK-R2 (Figure 10-1) Figure 10-1: MCDU - SAT-PHONE 2/2 Review the BITE summary status displayed on row 2 & 3 (Figure 10-2, Figure 10-3):

CURRENT BITE:

- OK

- FAIL No active BITE faults are present. See Figure 10-2. There is an active fault in the BITE SCANNING page. See Figure 10-3. Refer to section 10.1.1 for further detail on BITE SCANNING and troubleshooting. STRAPPING PARITY:

- OK

- FAIL Parity check is OK Parity check is FAIL and a wiring fault is present.

(ODD)

(EVEN) Figure 10-2: MCDU - BITE OK COBHAM PRIVATE Document: 98-181261 Revision:

A Figure 10-3: MCDU - BITE - FAIL Page:

Level: COM 45 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 10.1.1 BITE Scanning - Troubleshooting Code Access BITE SCANNING by pressing LSK-R2 to review active faults:

The ATA code, failure description (accused LRU or Wiring) and severity is shown for each failure

(Figure 10-4). o The Air Transport Association (ATA) code identifies the Line Replaceable Unit (LRU) or wiring

(WRG) that is affected by the fault condition. Refer to Appendix E.1 for the list of ATA codes and fault descriptions. Use the NEXT/PREV PAGE keys to navigate multiple pages. View the BITE SCANNING DETAILS page for each fault by pressing LSK-R2 or LSK-R4 (Figure 10-4).

- Note the UTC date and time information as well as troubleshooting code (Figure 10-5). Figure 10-4: MCDU - BITE - BITE SCANNING Figure 10-5: MCDU - BITE - BITE SCANNING DETAILS COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 46 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 10.1.2 PAST To initiate a Person Activated Self-Test (PAST) from the BITE page (Figure 10-2), navigate to the PAST page by pressing LSK-R3:

Press START to initiate the test (Figure 10-6). The PAST STARTED page indicates that the test is now in progress (Figure 10-7).

If the test could not be activated a page indicating TEST NOT POSSIBLE and a reason is displayed (Figure 10-12). The AVIATOR S SATCOM system will reboot as part of the test sequence. Once the SATCOM is available on the MCDU return to the PAST page to access the PAST REPORT.

If PAST has not been executed in the current power cycle, the PAST REPORT page will indicate that the self-test has not been run (Figure 10-8). If PAST is still executing, the TEST IN PROGRESS page is presented (Figure 10-9).

- When the PAST is completed the PAST REPORT will either state TEST PASSED (Figure 10-10) or TEST FAILED (Figure 10-11), and present the PAST REPORT failure information. Figure 10-6: MCDU - BITE - PAST Figure 10-7: MCDU - BITE - PAST STARTED Figure 10-8: MCDU - BITE - PAST REPORT - Not Figure 10-9: MCDU - BITE - PAST IN PROGRESS Run COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 47 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual Figure 10-10: MCDU - BITE - PAST REPORT -

Figure 10-11: MCDU - BITE - PAST REPORT -

Passed Failed Figure 10-12: MCDU - BITE - PAST - Not Possible COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 48 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 10.1.3 PIMBIT To initiate a passive intermodulation built-in test (PIMBIT) from the BITE page (Figure 10-2, Figure 10-3), navigate to the PIMBIT TEST page by pressing LSK-R4:

Ensure that the aircraft position is at least 200 meters away from the nearest building and orientation/heading is north facing if in the northern hemisphere or south facing if in the southern hemisphere of the globe. Press START at LSK-R6 to initiate the PIMBIT Test (Figure 10-13). The AVIATOR S SATCOM system will automatically restart as part of the test process (Figure 10-14). Figure 10-13: MCDU - BITE - PIMBIT Figure 10-14: MCDU - BITE - PIMBIT - PIMBIT TEST STARTED Each MCDU will indicate that the PIMBIT Test is in progress (Figure 10-15). When the PIMBIT TEST is completed the PIMBIT TEST RESULT will either state TEST PASSED (Figure 10-16) or TEST FAILED (Figure 10-17), and present the TEST DATA (Figure 10-18). Figure 10-15: MCDU - BITE - PIMBIT - PIMBIT TEST PROGRESS Figure 10-16: MCDU - BITE - PIMBIT - PIMBIT TEST RESULT - TEST PASSED Figure 10-17: MCDU - BITE - PIMBIT - PIMBIT Figure 10-18: MCDU - BITE - PIMBIT - PIMBIT TEST RESULT - TEST FAILED TEST RESULT - PIMBIT TEST DATA COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 49 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual The TEST FAILED result page (Figure 10-17) will include a reason for the test failure at LSK-L3:

- ANTENNA NOT AVAILABLE

- CSDU INTERNAL ERROR

- DATE/TIME NOT AVAILABLE

- HPA NOT AVAILABLE Failure to communicate with the Antenna. Refer to the BITE SCANNING pages for further troubleshooting (section 10.1.1). Correct the fault and repeat the PIMBIT Test. An internal CSDU fault has occurred which prohibits the test. Refer to the BITE SCANNING pages for further troubleshooting

(section 10.1.1). Replace the CSDU if persistent. Verify the aircraft interface operation. Refer to the BITE SCANNING pages for further troubleshooting (section 10.1.1). Correct the fault and repeat the PIMBIT Test. Failure to communicate with the High Power Amplifier. Refer to the BITE SCANNING pages for further troubleshooting (section 10.1.1). Correct the fault and repeat the PIMBIT Test.

- NAV DATA NOT AVAILABLE

- TEST DATA LIMIT EXCEEDED INMARSAT PARAM NOT AVAIL Ensure the AVIATOR S SATCOM system is able to acquire the satellite in order to receive the Inmarsat PIMBIT test parameters before initiating the PIMBIT Test. Verify the aircraft interface operation. Refer to the BITE SCANNING pages for further troubleshooting (section 10.1.1). Correct the fault and repeat the PIMBIT Test. The measured PIMBIT Test Data exceeds the defined threshold. Ensure the PIMBIT test is performed where the aircraft is not located close to any buildings (>200 meters) or other reflective surfaces. Repeat the test for additional data evaluation. Degraded SATCOM performance may occur. Perform antenna sub-system inspections to remove or correct potential passive inter-modulation source(s). The PIMBIT Test Data is determined to be invalid. Ensure the PIMBIT test is performed where the aircraft is not located close to any buildings (>200 meters) or other reflective surfaces. Repeat the test for additional data evaluation.

- TEST DATA INVALID To EXIT the PIMBIT TEST press LSK-L6 on the PIMBIT TEST RESULT page (Figure 10-16, Figure 10-17). To CONFIRM press LSK-R6 on the PIMBIT TEST EXIT page (Figure 10-19) to initiate an AVIATOR S SATCOM System restart to restore normal operation. Figure 10-19: MCDU - BITE - PIMBIT - PIMBIT TEST RESULT - PIMBIT TEST EXIT COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 50 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 10.1.4 LEGS Access the LEGS page (Error! Reference source not found.) by pressing LSK-L2 from the BITE page (Figure 10-2 or Figure 10-3) to review historical data:

- GROUND

- LAST LEG

- PREVIOUS LEG All AVIATOR S SATCOM System internal BITE events that are active or have occurred for the current on ground state (Error! Reference source not f ound.). All BITE events that occurred in the most recent flight leg (Error! R eference source not found.). Review the High Severity (Class 1) events that occurred in previous legs

(Error! Reference source not found.). NOTE: A complete flight leg is the transition from on ground to in air and back to on ground. The transition from in air to on ground initiates a new flight leg. Figure 10-20: MCDU - BITE - LEGS Figure 10-21: MCDU - BITE - LEGS - GROUND FAULTS Figure 10-22: MCDU - BITE - LEGS - LAST LEG Figure 10-23: MCDU - BITE - LEGS - PREVIOUS LEGS COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 51 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual 10.2 SATCOM CONFIG In order to review the AVIATOR S SATCOM system configuration, navigate to the CONFIG pages:

MCDU: SAT-PHONE page 2 of 2, LSK-R3 (Figure 10-1) Page 1/5 (Figure 10-24):

SAT-L or SAT-R determined by the SDU Config Strapping

- SW LOCATION

- SW LOCATION ID SW Location Identity determined by the SDU Config Strapping Part Number of the SDU Operational Program Software (OPS)

- SW P/N OPS Page 2/5 (Figure 10-25):

- SW SDU SORT

- SD SDU UORT Part Number of the SDU Secure Owner Requirements Table (SORT) Part Number of the SDU User Owner Requirements Table (UORT) Page 3/5 (Figure 10-26):

- SDU P/N

- SDU S/N

- SCM P/N

- SCM S/N Part Number of the SDU hardware Serial Number of the SDU hardware Part Number of the SDU Configuration Module (SCM) hardware Serial Number of the SDU Configuration Module (SCM) hardware Page 4/5 (Figure 10-27):

- ANT P/N

- ANT S/N

- ANT SW Part Number of the Antenna hardware Serial Number of the Antenna hardware Part Number of the Antenna Operational Program Software Page 5/5 (Figure 10-28):

IMSI

- SMART CARD S/N Serial Number of the Smart Card. International Mobile Subscriber Identity number. Figure 10-24: MCDU - SAT-CONFIG 1/5 COBHAM PRIVATE Document: 98-181261 Revision:

A Figure 10-25: MCDU - SAT-CONFIG 2/5 Page:

Level: COM 52 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual Figure 10-26: MCDU - SAT-CONFIG 3/5 Figure 10-27: MCDU - SAT-CONFIG 4/5 Figure 10-28: MCDU - SAT-CONFIG 5/5 10.3 LOG FILE EXTRACTION VIA THE ETHERNET DATALOADER INTERFACE The AVIATOR S log files may be retrieved via the Ethernet dataloader interface using the ARINC 615A

[A615A] Operator Defined Download Protocol. Log file extraction via the Ethernet dataloader interface is only permitted when Data Load mode has been activated. Further guidance with respect to aircraft maintenance system functions and operation is beyond the scope of this document. 10.4 LOG FILE EXTRACTION VIA THE MAINTENANCE USB For AVIATOR S log file extraction via the front USB interface, refer to [LET]. 10.5 SYSTEM TEST - FLASHING CALL LIGHTS While performing an AVIATOR S SATCOM System Test, the call lights are flashed. When the test has completed, additional crew action may be required to clear the call lights before the system can return to the operational state:

Clear the ACP call lights by pressing the SAT-1 and SAT-2 call buttons. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 53 of 99 CC: 1

(T: 99-161853-I) AVIATOR 700S User Manual Appendix A. AISD SNMP Interface Table 10-1: AISD SNMP MIB OID Support Level 1 Level 2 Level 3 Level 4 Level 5 Description

.asLinks(2)

.aslServices(1) .aslsNumbers(1)

.aslsTable(2)

.aslsIndex(1)

.aslsName(2)

.aslsInUse(3)

.aslsAvailable(4)

.aslsMaxChannels(5)

.aslInfos(2)

.asliSatState(1)

.asliSatID(2) COBHAM PRIVATE Document:

Revision:

98-181261 A The number of data services types available. Integer = 1 Index number to each service. Integer = 1 Name for each index. Index 1 = "SBB:BACKGROUND"

Number of instances of this service currently in use. Integer [0..1]

Number of instances of this service currently available. Integer [0..1]

Max number of instances of this service available. Integer = 1 This object shows, if the satellite is locked or not. The type is an enumerated integer value. 1 = Connected to Sat, 2 = Not connected. This object shows, which satellite is connected by the AVIATOR S SATCOM system:

EMEA MEAS AMER APAC String [0..32]

Page:

Level: COM 54 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

.asliSatIDNum(3)

.asliActLinkEntryNumbers(4)

.asliActLinkTable(5)

.asliActLinkIndex(1)

.asliActLinkReleaseType(2)

.asliActLinkReleaseReason(3)

.asliActLinkStatus(4)

.asliActLinkChanNo(5)

.asliActLinkContextID(6) COBHAM PRIVATE Document:

Revision:

98-181261 A Unique numeric identifier for the connected satellite: 3 (MEAS) 6 (EMEA) 5 (APAC) 7 (AMER) Integer [0..63]

Indicates the number of the entries in the first table and has a range from 0 to 50. Integer [0..50]

This object is a unique identifier for the current link entry and can be considered a handle for the session. With each new link, this number is to be incremented by one, wrapping around (but avoiding conflicts). Integer [1..32767]

This object shows the release type of the current link as numeric codes as described in

[A781] Attachment 5, Section 6. Integer [1..32767]

Variable string based on asliActLinkReleaseType String [0..128]

This object shows if the current link is up or not. Because entries are only removed 30 seconds after going down, it is important to check this field while reading the active link table. This object shows which channel is being used by the current link:

Integer = 1 (AISD) Virtual context ID specific to that user session

(tied to a primary PDP). Integer [0..255]

Page:

Level: COM 55 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

.asliActLinkActualContextID(7)

.asliActLinkConnectionID(8)

.asliActLinkNegotiatedBW(9)

.asliActLinkIpAddress(10)

.asliActLinkTxTrafficVol(11)

.asliActLinkRXTrafficVol(12)

.asliActLinkBeamID(13)

.asliActLinkSigQual(14)

.asliActLinkMaxSigQual(15)

.asliActLinkMainIndex(16)

.asliActLinkStartTime(20) COBHAM PRIVATE Document:

Revision:

98-181261 A The NSAPI used over the air. This ID is unique per channel card in the system while it is active. The association between a ContextID and the ActualContextID remains for the duration of the primary PDP. Integer [0..255]

Variable string used when creating the PPPoE session. String [0..128]

Integer = 0 (Best effort connection) This object contains the IP-Address of the current link. E.g. aaa.bbb.ccc.ddd. This object contains the information about the total transmitted bytes over this link in kBytes This object contains the information about the total received bytes over this link in kBytes This object shows, which beam ID is connected by the current link. Integer [0..255]

This object shows the Quality in dBHz*10 of the current link. Integer [0..32767]

Expected maximum values for Link Signal Quality in dBHz*10. 64 dBHz BGAN Global Beam 68 dBHz BGAN Regional Beam 80 dBHz BGAN Narrow Beam Integer [0..32767]

Integer = 0 (No secondary PDP contexts) UTC Time at which the link was brought up. AS_Datetime [RFC3339]

Page:

Level: COM 56 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

.asliHistLinkEntryNumbers(6)

.asliHistLinkTable(7)

.asliHistLinkIndex(1)

.asliActLinkEndTime(21)

.asliActLinkPPPoEID(22)

.asliActLinkNegotiatedBWUp(25)

.asliActLinkNegotiatedBWDown(26)

.asliActLinkPeerIP(27)

.asliActLinkDNS1(28)

.asliActLinkDNS2(29)

.asliActLinkRequestSource(30)

.asliHistLinkReleaseType(2)

.asliHistLinkReleaseReason(3)

.asliHistLinkStatus(4) COBHAM PRIVATE Document:

Revision:

98-181261 A UTC Time at which the link was brought down. AS_Datetime [RFC3339]

PPPoE Session ID which started the call. Integer [0..32767]

Integer = 0 (Best effort connection) Integer = 0 (Best effort connection) This object contains the IP-Address of the current link. E.g. aaa.bbb.ccc.ddd. This object contains the IP-Address of the first DNS Server. E.g. aaa.bbb.ccc.ddd. This object contains the IP-Address of the second DNS Server. E.g. aaa.bbb.ccc.ddd. The manner and interface through which this link was brought up. E.g. NAT, AISD Indicates the number of the entries in the second table. Integer [0..250]

This object is a unique identifier for the link entry and can be considered a handle for the session. With each new link, this number is to be incremented by one, wrapping around (but avoiding conflicts). Integer [0..32767]

This object shows the release type of the link as numeric codes as described in [A781]

Attachment 5, Section 6. Integer [1..32767]

Variable string based on asliHisLinkReleaseType String [0..128]

This object shows if the link is up or not. Page:

Level: COM 57 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

.asliHistLinkChanNo(5)

.asliHistLinkContextID(6)

.asliHistLinkActualContextID(7)

.asliHistLinkConnectionID(8)

.asliHistLinkNegotiatedBW(9)

.asliHistLinkIpAddress(10)

.asliHistLinkTxTrafficVol(11)

.asliHistLinkRXTrafficVol(12)

.asliHistLinkBeamID(13)

.asliHistLinkSigQual(14)

.asliHistLinkMaxSigQual(15) COBHAM PRIVATE Document:

Revision:

98-181261 A This object shows which channel is being used by the link:

Integer = 2 (AISD) Virtual context ID specific to that user session

(tied to a primary PDP). Integer [0..255]

The NSAPI used over the air. This ID is unique per channel card in the system while it was active. The association between a ContextID and the ActualContextID remains for the duration of the primary PDP. Integer [0..255]

Variable string used when creating the PPPoE session. String [0..128]

Integer = 0 (Best effort connection) This object contains the IP-Address of the link. E.g. aaa.bbb.ccc.ddd. This object contains the information about the total transmitted bytes over this link in kBytes This object contains the information about the total received bytes over this link in kBytes This object shows, which beam ID is connected by the link. Integer [0..255]

This object shows the Quality in dBHz*10 of the link. Integer [0..32767]

Expected maximum values for Link Signal Quality in dBHz*10. 64 dBHz BGAN Global Beam 68 dBHz BGAN Regional Beam 80 dBHz BGAN Narrow Beam Page:

Level: COM 58 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

.asliHistLinkMainIndex(16)

.asliHistLinkStartTime(20)

.asliHistLinkEndTime(21)

.asliHistLinkPPPoEID(22)

.asliHistLinkNegotiatedBWUp(25)

.asliHistLinkNegotiatedBWDown(26)

.asliHistLinkPeerIP(27)

.asliHistLinkDNS1(28)

.asliHistLinkDNS2(29)

.asliHistLinkRequestSource(30)

.asliSatHandoverPending(8)

.asliSatNetworkName (9)

.asSystem(3) . assInfos(2) assiHealthStatus(1)

.asUnits(4)

.asuSDU(2)

.asuSduInfo(1)

.asuSduInfoTableNumbers(1) COBHAM PRIVATE Document:

Revision:

98-181261 A Integer [0..32767]

Integer = 0 (No secondary PDP contexts) UTC Time at which the link was brought up. AS_Datetime [RFC3339]

UTC Time at which the link was brought down. AS_Datetime [RFC3339]

PPPoE Session ID which started the call. Integer [0..32767]

Integer = 0 (Best effort connection) Integer = 0 (Best effort connection) This object contains the IP-Address of the historic link. E.g. aaa.bbb.ccc.ddd. This object contains the IP-Address of the first DNS Server. E.g. aaa.bbb.ccc.ddd. This object contains the IP-Address of the second DNS Server. E.g. aaa.bbb.ccc.ddd. The manner and interface through which this link was brought up. E.g. NAT, AISD Set if the system believes it will need to do a handover soon:

1 ~ True 2 ~ False Indicates to which satellite network the SDU is connected. E.g. SBB System Overall Status:

1 ~ Passed 2 ~ Failed 3 ~ Absent (Initial) Indicates the number of entries in the table. Integer [1]

Page:

Level: COM 59 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual COBHAM PRIVATE Document:

Revision:

98-181261 A

.asuSduInfoTable(2)

.asuSduInfoIndex(1) This object describes the unique identifier for the current unit. Integer [1..2]

.asuSduInfoOverallStatus(8) CSDU Overall Status:

1 ~ Passed 2 ~ Failed 3 ~ Absent (Initial)

.asuSduInfoFailureCode(11)

.asuSduInfoFailureReason(12)

.asuSduInfoCC1Status(15)

.asuSduInfoCC2Status(16) CSDU overall status failure code - see Appendix C. Integer [0..32767]

CSDU overall status failure group based on the failure code - see Appendix C. String [0..255]

Cockpit Channel Card overall status:

1 ~ Passed 2 ~ Failed 3 ~ Absent (initial value) Cabin Channel Card overall status:

Integer [3] (Absent)

.asuSduInfoUTCDateTime(35) Current UTC date and time in RFC3339 format. Indicates the number of entries in the table. Integer [1]

This object describes the unique identifier for the current antenna. Integer [1]

.asuAntInfoTable(2)

.asuAntInfoIndex(1)

.asuAntInfoOverallStatus(8) Overall Antenna status 1 ~ Passed 2 ~ Failed 3 ~ Absent (initial value)

.asuAntInfoGain(10) The antenna gain (dB/10) currently utilized from 0.0 to 31.5 dB. (-1 indicates invalid data). Integer [-1..315]

Page:

Level: COM 60 of 99 CC: 1

(T: 99-161853-H)

.asuAntenna(8) .asuAntInfo(1)

.asuAntInfoTableNumbers(1) AVIATOR 700S User Manual Appendix B. PIESD SNMP Interface Table 10-2: PIESD SNMP MIB OID Support Level 1 Level 2 Level 3 Level 4 Level 5 Description

.asLinks(2) .aslServices(1)

.aslsNumbers(1)

.aslsTable(2)

.aslsIndex(1)

.aslsName(2)

.aslsInUse(3)

.aslInfos(2)

.asliSatState(1)

.asliSatID(2)

.asliSatIDNum(3) COBHAM PRIVATE Document:

Revision:

98-181261 A The number of data services types available. Integer [7]

Index number to each service. Integer [1..7]

Name for each index. Index 1 = SBB:BACKGROUND Index 2 = SBB:STREAM8K Index 3 = SBB:STREAM16K Index 4 = SBB:STREAM32K Index 5 = SBB:STREAM64K Index 6 = SBB:STREAM128K Index 7 = SBB:XSTREAM Number of instances of this service currently in use. Integer [0..127]

This object shows, if the satellite is locked or not. The type is an enumerated integer value. 1 = Connected to Sat, 2 = Not connected. This object shows, which satellite is connected by the AVIATOR S SATCOM system:

EMEA MEAS AMER APAC String [0..32]

Unique numeric identifier for the connected satellite: 3 (MEAS) Page:

Level: COM 61 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Level 1 Level 2 Level 3 Level 4 Level 5

.asliActLinkEntryNumbers(4)

.asliActLinkTable(5)

.asliActLinkIndex(1)

.asliActLinkReleaseType(2)

.asliActLinkReleaseReason(3)

.asliActLinkStatus(4)

.asliActLinkChanNo(5)

.asliActLinkContextID(6)

.asliActLinkActualContextID(7) COBHAM PRIVATE Document:

Revision:

98-181261 A Description 6 (EMEA) 5 (APAC) 7 (AMER) Integer [0..63]

Indicates the number of the entries in the first table and has a range from 0 to 50. Integer [0..50]

This object is a unique identifier for the current link entry and can be considered a handle for the session. With each new link, this number is to be incremented by one, wrapping around (but avoiding conflicts). Integer [1..32767]

This object shows the release type of the current link as numeric codes as described in [A781]

Attachment 5, Section 6. Integer [1..32767]

Variable string based on asliActLinkReleaseType String [0..128]

This object shows if the current link is up or not. Because entries are only removed 30 seconds after going down, it is important to check this field while reading the active link table. This object shows which channel is being used by the current link:

Integer = 2 (PIESD) Virtual context ID specific to that user session

(tied to a primary PDP). Integer [0..255]

The NSAPI used over the air. This ID is unique per channel card in the system while it is active. Page:

Level: COM 62 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Level 1 Level 2 Level 3 Level 4 Level 5 Description

.asliActLinkConnectionID(8)

.asliActLinkNegotiatedBW(9)

.asliActLinkIpAddress(10)

.asliActLinkTxTrafficVol(11)

.asliActLinkRxTrafficVol(12)

.asliActLinkBeamID(13)

.asliActLinkSigQual(14)

.asliActLinkMaxSigQual(15)

.asliActLinkMainIndex(16) COBHAM PRIVATE Document:

Revision:

98-181261 A The association between a ContextID and the ActualContextID remains for the duration of the primary PDP. Integer [0..255]

Variable string used when creating the PPPoE session. String [0..128]

This object shows the currently negotiated bandwidth of the link in this table entry. Integer [0..2048]

0 ~ Background Class / Best effort connection This object contains the IP-Address of the current link. E.g. aaa.bbb.ccc.ddd. This object contains the information about the total transmitted bytes over this link in kBytes This object contains the information about the total received bytes over this link in kBytes This object shows, which beam ID is connected by the current link. Integer [0..255]

This object shows the Quality in dBHz*10 of the current link. Integer [0..32767]

Expected maximum values for Link Signal Quality in dBHz*10. 64 dBHz BGAN Global Beam 68 dBHz BGAN Regional Beam 80 dBHz BGAN Narrow Beam Integer [0..32767]

If this link entry is part of bundle (e.g., a secondary context), this object refers the main entry (e.g., the primary context) in this table to Page:

Level: COM 63 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Level 1 Level 2 Level 3 Level 4 Level 5 Description

.asliHistLinkEntryNumbers(6)

.asliHistLinkTable(7)

.asliHistLinkIndex(1)

.asliActLinkServiceIndex(17)

.asliActLinkStartTime(20)

.asliActLinkEndTime(21)

.asliActLinkPPPoEID(22)

.asliHistLinkReleaseType(2)

.asliHistLinkReleaseReason(3) which this subentry is related. Integer [0..32767]

This object is a link to the aslsIndex by referring the used Service. Integer [0..100]

UTC Time at which the link was brought up. AS_Datetime [RFC3339]

UTC Time at which the link was brought down. AS_Datetime [RFC3339]

PPPoE Session ID which started the call. Integer [0..32767]

This object is a unique identifier for the link entry and can be considered a handle for the session. With each new link, this number is to be incremented by one, wrapping around (but avoiding conflicts). Integer [1..250]

This object is a unique identifier for the link entry and can be considered a handle for the session. With each new link, this number is to be incremented by one, wrapping around (but avoiding conflicts). Integer [1..32767]

This object shows the release type of the link as numeric codes as described in [A781]

Attachment 5, Section 6. Integer [1..32767]

Variable string based on asliHisLinkReleaseType String [0..128]

.asliHistLinkStatus(4) This object shows if the link is up or not. COBHAM PRIVATE Document:

Revision:

98-181261 A Page:

Level: COM 64 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Level 1 Level 2 Level 3 Level 4 Level 5 Description

.asliHistLinkChanNo(5)

.asliHistLinkContextID(6)

.asliHistLinkActualContextID(7)

.asliHistLinkConnectionID(8)

.asliHistLinkNegotiatedBW(9)

.asliHistLinkIpAddress(10)

.asliHistLinkTxTrafficVol(11)

.asliHistLinkRxTrafficVol(12)

.asliHistLinkBeamID(13)

.asliHistLinkSigQual(14) COBHAM PRIVATE Document:

Revision:

98-181261 A This object shows which channel is being used by the link:

Integer = 2 (PIESD) Virtual context ID specific to that user session

(tied to a primary PDP). Integer [0..255]

The NSAPI used over the air. This ID is unique per channel card in the system while it was active. The association between a ContextID and the ActualContextID remains for the duration of the primary PDP. Integer [0..255]

Variable string used when creating the PPPoE session. String [0..128]

This object shows the negotiated bandwidth of the link in this table entry. Integer [0..2048]

0 ~ Background Class / Best effort connection This object contains the IP-Address of the link. E.g. aaa.bbb.ccc.ddd. This object contains the information about the total transmitted bytes over this link in kBytes This object contains the information about the total received bytes over this link in kBytes This object shows, which beam ID is connected by the link. Integer [0..255]

This object shows the Quality in dBHz*10 of the link. Integer [0..32767]

Page:

Level: COM 65 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Level 1 Level 2 Level 3 Level 4 Level 5 Description

.asliHistLinkMaxSigQual(15)

.asliHistLinkMainIndex(16)

.asliHistLinkServiceIndex(17)

.asliHistLinkStartTime(20)

.asliHistLinkEndTime(21)

.asliHistLinkPPPoEID(22)

.asUnits(4) .asuSDU(2)

.asuSduInfo(1)

.asuSduInfoTableNumbers(1) Expected maximum values for Link Signal Quality in dBHz*10. 64 dBHz BGAN Global Beam 68 dBHz BGAN Regional Beam 80 dBHz BGAN Narrow Beam Integer [0..32767]

If this link entry is part of bundle (e.g., a secondary context), this object refers the main entry (e.g., the primary context) in this table to which this subentry is related. Integer [0..32767]

This object is a link to the aslsIndex by referring the used Service. Integer [0..100]

UTC Time at which the link was brought up. AS_Datetime [RFC3339]

UTC Time at which the link was brought down. AS_Datetime [RFC3339]

PPPoE Session ID which started the call. Integer [0..32767]

Indicates the number of entries in the table. Integer [1]

This object describes the unique identifier for the current unit. Integer [1..2]

COBHAM PRIVATE Document:

Revision:

98-181261 A

.asuSduInfoTable(2)

.asuSduInfoIndex(1)

.asuSduInfoVendor(2) Short Name of the LRU supplier. String [0..22] = "Cobham Aerospace"

.asuSduInfoOverallStatus(8) CSDU Overall Status:

1 ~ Passed 2 ~ Failed 3 ~ Absent (Initial)

.asuSduInfoFailureCode(11) CSDU overall status failure code - see Appendix C. Page:

Level: COM 66 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Level 1 Level 2 Level 3 Level 4 Level 5 Description Integer [0..32767]

.asuSduInfoFailureReason(12) CSDU overall status failure group based on the failure code - see Appendix C. String [0..255]

.asuSduInfoCC1Status(15)

.asuSduInfoCC2Status(16) Cockpit Channel Card overall status:

Integer [3] (Absent) Cabin Channel Card overall status:

1 ~ Passed 2 ~ Failed 3 ~ Absent (initial value)

.asuSduInfoUTCDateTime(35) Current UTC date and time in RFC3339 format. asuAntenna(8) .asuAntInfo(1)

.asuAntInfoTableNumbers(1) Indicates the number of entries in the table. Integer [1]

This object describes the unique identifier for the current antenna. Integer [1]

.asuAntInfoTable(2)

.asuAntInfoIndex(1)

.asuAntInfoOverallStatus(8) Overall Antenna status Integer [3] (Absent)

.asuAntInfoGain(10) The antenna gain (dB/10) currently utilized from 0.0 to 31.5 dB. (-1 indicates invalid data). Integer [-1..315]

Page:

Level: COM 67 of 99 CC: 1

(T: 99-161853-H) COBHAM PRIVATE Document:

Revision:

98-181261 A AVIATOR 700S User Manual Appendix C. SNMP Object ID Definitions asliActLinkStatus shows if the current link is up or not. The values are:

Up(1) Down(2) Unconnected(3) asliHistLinkEntryNumbers(6) indicates the number of the entries in the second table and has an open range. The value is maximum 250. asuSduInfoVendor is the name of the AVIATOR S supplier and has the value Cobham Aerospace. asuSduInfoFailureCode indicates a unique failure code. The failure code consists of a fault group and a fault bit to indicate individual faults. The value range of the failure code determines the fault group as listed in Table 10-3. Table 10-3: Failure group of asuSduInfoFailureCode Failure Code Fault Group (in prioritized order) 1000 - 1999 No Power 2000 - 2999 Critical Temperature 3000 - 3999 No SATCOM 4000 - 4999 External Interface Failed 5000 - 5999 No ACARS 6000 - 6999 No Cockpit Voice 7000 - 7999 No Cockpit Data 8000 - 8999 Reserved for future use For the No Power fault group the following fault bits are defined:

DegradedPowerHoldUp (Bit 0) For the Critical Temperature fault group the following fault bits are defined:

DegradedACDTemperatureCriticalHigh (Bit 0) DegradedACDTemperatureShutdownHigh (Bit 1) DegradedCockpitRMTempCriticalHigh (Bit 2) DegradedPSMTemperatureCriticalHigh (Bit 3) DegradedAISDTemperatureCriticalHigh (Bit 4) Reserved for future use (Bit 5) DegradedHPATemperatureCriticalHigh (Bit 6) COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 68 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual For the No SATCOM fault group the following fault bits are defined:

DegradedNoSATCOM (Bit 0) DegradedPosLost (Bit 1) DegradedNO_ORT (Bit 2) For the External Interface Failed fault group the following fault bits are defined:

DegradedNo615-3 (Bit 0) Degraded615-3Lost (Bit 1) DegradedCMULost (Bit 2) DegradedMCDULost (Bit 3) DegradedCFDSLost (Bit 4) DegradedFWSLost (Bit 5) DegradedMCDUFailure (Bit 6) For the No ACARS fault group the following fault bits are defined:

DegradedNoACARS (Bit 0) For the No Cockpit Voice fault group the following fault bits are defined:

DegradedCockpitVoiceFailure (Bit 0) For the No Cockpit Data fault group the following fault bits are defined:

DegradedAISDNotWorking (Bit 0) DegradedAISDFailure (Bit 1) DegradedNoCockpitData (Bit 2) As an example:

If the CMU and MCDU are lost, it will set the fault bits 2 and 3 in the External Interface Failed fault group to combine into failure code 400C. asuSduInfoFailureReason is a failure message equal to the failure code in asuSduInfoFailureCode(11). COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 69 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Appendix D. AT-Commands List all Available AT Commands List all available AT commands. Ref : [3GPP_TS27]

Command

+CLAC

+CLAC=?

Defined Values:

<AT Command >:

Possible response(s)

<AT Command1> [<CR> <LF> <AT Command2>[...]]

+CME ERROR: <err>

Defines the AT command including the prefix AT. Text shall not contain the sequence 0<CR> or OK<CR>

Command Echo Command Echo. Ref : [ITU-T_V.250]

Command ATE[<value>]

Defined Values:

<value>

Possible response(s) OK 0 DCE does not echo characters during command state and online command state. 1 DCE echoes characters during command state and online command state. Recommended default setting :

1 DCE echoes characters during command state and online command state Supported Values:

(0,1) COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 70 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Request Manufacturer Identification Request Manufacturer Identification. Ref : [3GPP_TS27]

Command

+CGMI

+CGMI=?

Defined Values:

<manufacturer>

Possible response(s)

<manufacturer>

+CME ERROR: <err>

the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. Text shall not contain the sequence 0<CR> or OK<CR>

Request Model Identification Request Model Identification. Ref : [3GPP_TS27]

Command

+CGMM

+CGMM=?

Defined Values:

<model>

Possible response(s)

<model>

+CME ERROR: <err>

The total number of characters, including line terminators, in the information text shall not exceed 2048 characters. Text shall not contain the sequence 0<CR> or OK<CR>

COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 71 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Request Revision Identification Request Revision Identification. Ref : [3GPP_TS27]

Possible response(s)

<revision>

+CME ERROR: <err>

Command

+CGMR

+CGMR=?

Defined Values:

<revision>

The total number of characters, including line terminators, in the information text shall not exceed 2048 characters. Text shall not contain the sequence 0<CR> or OK<CR>. Request Serial Number Identification Request Product Serial Number Identification. Ref : [3GPP_TS27]

Command

+CGSN

+CGSN=?

Defined Values:

<sn>

Possible response(s)

<sn>

+CME ERROR: <err>

the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. Text shall not contain the sequence 0<CR> or OK<CR>

Request International Mobile Subscriber Identity Request International Mobile Subscriber Identity. Ref : [3GPP_TS27]

Command

+CIMI

+CIMI=?

Defined Values:

<IMSI>

Possible response(s)

<IMSI>

+CME ERROR: <err>

International Mobile Subscriber Identity (string without double quotes) COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 72 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Define Primary PDP Context Define PDP Context. [3GPP_TS27]

Command Possible response(s)

+CGDCONT=[<cid> [,<PDP_type>[,

<APN> [,<PDP_addr> [,

<d_comp> [,<h_comp> [,

<pd1> [,[,pdN]]]]]]]]]

OK ERROR

+CGDCONT?

+CGDCONT=?

Defined Values:

<cid>

+CGDCONT: <cid>, <PDP_type>, <APN>,

<PDP_addr>, <data_comp>,

<head_comp>[,<pd1>[,[,pdN]]]

+CGDCONT: (range of supported <cid>s),

<PDP_type>,,,(list of supported

<d_comp>s),

(list of supported <h_comp>s)[,

(list of supported <pd1>s)[,[,

(list of supported <pdN>s)]]]

(PDP Context Identifier) a numeric parameter which specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. The range of permitted values (minimum value = 1) is returned by the test form of the command.

<PDP_type>

(Packet Data Protocol type) a string parameter which specifies the type of packet data protocol IP Internet Protocol (IETF STD 5) IPV616 Internet Protocol, version 6 (IETF RFC 2460) PPP Point to Point Protocol (IETF STD 51)

<APN>

(Access Point Name) a string parameter which is a logical name that is used to select the GGSN or the external packet data network. If the value is null or omitted, then the subscription value will be requested.

<PDP_address>

a string parameter that identifies the MT in the address space applicable to the PDP. If the value is null or omitted, then a value may be provided by the TE during the PDP startup procedure or, failing that, a 16 IPv6 is not supported by the Inmarsat network. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 73 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual dynamic address will be requested. The read form of the command will continue to return the null string even if an address has been allocated during the PDP startup procedure. The allocated address may be read using the +CGPADDR command.

<d_comp>

a numeric parameter that controls PDP data compression 0 off (default if value is omitted) 1 on Other values are reserved.

<h_comp>

a numeric parameter that controls PDP header compression 0 off (default if value is omitted) 1 on Other values are reserved. NOTE: At present only one data compression algorithm (V.42bis) is provided in SNDCP. If and when other algorithms become available, a command will be provided to select one or more of these.

<pd1>, <pdN>

zero to N string parameters whose meanings are specific to the <PDP_type>

For PDP type OSP:IHOSS the following parameters are defined:

<pd1> = <host>

the fully formed domain name extended hostname of the Internet host

<pd2> = <port >

the TCP or UDP port on the Internet host

<pd3> = <protocol>

the protocol to be used over IP on the Internet - "TCP" or "UDP COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 74 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Supported Values:

<cid>

(1-11)

<PDP_address>

<d_comp>

<PDP_type>

0 off (default if value is omitted)

"IP"

<APN>

<h_comp>

0 off (default if value is omitted) 1 on 3G Quality of Service Profile (Requested) 3G Quality of Service Profile (Requested). Ref : [3GPP_TS27]

Command Possible response(s)

+CGEQREQ=[<cid> [,

<Traffic class>[,

<Maximum bitrate UL>[,

<Maximum bitrate DL>[,

<Guaranteed bitrate UL>[,

<Guaranteed bitrate DL>[,

<Delivery order>[,

<Maximum SDU size>[,

<SDU error ratio>[,

<Residual bit error ratio>[,

<Delivery of erroneous SDUs>[,

<Transfer delay>[,

<Traffic handling priority>

+CGEQREQ?

+CGEQREQ=?

OK ERROR

+CGEQREQ: <cid>, <Traffic class> ,

<Maximum bitrate UL> ,

<Maximum bitrate DL> ,

<Guaranteed bitrate UL> ,

<Guaranteed bitrate DL> ,

<Delivery order> ,

<Maximum SDU size> ,

<SDU error ratio> ,

<Residual bit error ratio> ,

<Delivery of erroneous SDUs> ,

<Transfer delay> ,

<Traffic handling priority>

+CGEQREQ: <PDP_type>,

(list of supported <Traffic class>s) ,

(list of supported <Maximum bitrate UL>s),

(list of supported <Maximum bitrate DL>s),

(list of supported <Guaranteed bitrate UL>s),

(list of supported <Guaranteed bitrate DL>s),

(list of supported <Delivery order>s) ,

(list of supported <Maximum SDU size>s) ,

(list of supported <SDU error ratio>s) ,

(list of supported <Residual bit error ratio>s) ,

(list of supported <Delivery of erroneous SDUs>s)

, (list of supported <Transfer delay>s) ,

(list of supported <Traffic handling priority>s) COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 75 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Defined Values:

<cid>

a numeric parameter which specifies a particular PDP context definition (see+CGDCONT and +CGDSCONT commands). The following parameters are defined in 3GPP TS 23.107 -

<Traffic class>

a numeric parameter that indicates the type of application for which the UMTS bearer service is optimised. 0 conversational 1 streaming 2 interactive 3 background 4 subscribed value Other values are reserved.

<Maximum bitrate UL>

a numeric parameter that indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQREQ=,32, ).

<Maximum bitrate DL>

a numeric parameter that indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQREQ=,32, ). If the parameter is set to '0' the subscribed value will be requested.

<Guaranteed bitrate UL>

a numeric parameter that indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as

'32' (e.g. AT+CGEQREQ=,32, ). If the parameter is set to '0' the subscribed value will be requested.

<Guaranteed bitrate DL>

a numeric parameter that indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQREQ=,32, ). If the parameter is set to '0' the subscribed value will be requested. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 76 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

<Delivery order>

a numeric parameter that indicates whether the UMTS bearer shall provide in- sequence SDU delivery or not. 0 no 1 yes 2 subscribed value. Other values are reserved.

<Maximum SDU size>

a numeric parameter (1,2,3,) that indicates the maximum allowed SDU size in octets. If the parameter is set to '0' the subscribed value will be requested.

<SDU error ratio>

a string parameter that indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined only for conforming traffic. The value is specified as 'mEe'. As an example a target SDU error ratio of 5o10-3 would be specified as '5E3' (e.g. AT+CGEQREQ=,"5E3",).

'0E0' means subscribed value.

<Residual bit error ratio>

a string parameter that indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value is specified as 'mEe'. As an example a target residual bit error ratio of 5o10-3 would be specified as '5E3' (e.g. AT+CGEQREQ=,"5E3",). '0E0' means subscribed value.

<Delivery of erroneous SDUs>

a numeric parameter that indicates whether SDUs detected as erroneous shall be delivered or not. 0 no 1 yes 2 no detect 3 subscribed value Other values are reserved. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 77 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

<Transfer delay>

a numeric parameter (0,1,2,) that indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the other SAP, in milliseconds. If the parameter is set to '0' the subscribed value will be requested.

<Traffic handling priority>

a numeric parameter (1,2,3,) that specifies the relative importance for handling of all SDUs belonging to the UMTS bearer compared to the SDUs of other bearers. If the parameter is set to '0' the subscribed value will be requested.

<PDP_type> (see +CGDCONT and +CGDSCONT commands). If a value is omitted for a particular class then the value is considered to be unspecified. Supported Values:

<cid>

(1-11)

<Traffic class>

(0-4)

<Maximum bitrate UL>

(0-8640)

<Maximum bitrate DL>

(0-8640)

<Guaranteed bitrate UL>

(0-8640)

<Guaranteed bitrate DL>

(0-8640)

<Delivery order>

(0-2)

<Maximum SDU size>

(0-1520)

<SDU error ratio>

("1E6"-"1E1","0E0").

<Residual bit error ratio>

("6E8"-"5E2","0E0")

<Delivery of erroneous SDUs>

(0-3)

<Transfer delay>

(0-4000)

<Traffic handling priority>

(0-3)

<PDP_type>

"IP"

COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 78 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual 2G Quality of Service Profile (Requested) 2G Quality of Service Profile (Requested). Ref : [3GPP_TS27]

Command Possible response(s)

+CGQREQ=[<cid> [,

<Traffic class>[,

<Maximum bitrate UL>[,

<Maximum bitrate DL>[,

<Guaranteed bitrate UL>[,

<Guaranteed bitrate DL>[,

<Delivery order>[,

<Maximum SDU size>[,

<SDU error ratio>[,

<Residual bit error ratio>[,

<Delivery of erroneous SDUs>[,

<Transfer delay>[,

<Traffic handling priority>

+CGQREQ?

+CGQREQ=?

OK ERROR

+CGQREQ: <cid>, <Traffic class> ,

<Maximum bitrate UL> ,

<Maximum bitrate DL> ,

<Guaranteed bitrate UL> ,

<Guaranteed bitrate DL> ,

<Delivery order> ,

<Maximum SDU size> ,

<SDU error ratio> ,

<Residual bit error ratio> ,

<Delivery of erroneous SDUs> ,

<Transfer delay> ,

<Traffic handling priority>

+CGQREQ: <PDP_type>,

(list of supported <Traffic class>s) ,

(list of supported <Maximum bitrate UL>s),

(list of supported <Maximum bitrate DL>s),

(list of supported <Guaranteed bitrate UL>s),

(list of supported <Guaranteed bitrate DL>s),

(list of supported <Delivery order>s) ,

(list of supported <Maximum SDU size>s) ,

(list of supported <SDU error ratio>s) ,

(list of supported <Residual bit error ratio>s) ,

(list of supported <Delivery of erroneous SDUs>s)

, (list of supported <Transfer delay>s) ,

(list of supported <Traffic handling priority>s) COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 79 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Defined Values:

<cid>

a numeric parameter which specifies a particular PDP context definition (see+CGDCONT and +CGDSCONT commands). The following parameters are defined in 3GPP TS 23.107 -

<Traffic class>

a numeric parameter that indicates the type of application for which the UMTS bearer service is optimised. 0 conversational 1 streaming 2 interactive 3 background 4 subscribed value Other values are reserved.

<Maximum bitrate UL>

a numeric parameter that indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGQREQ=,32, ).

<Maximum bitrate DL>

a numeric parameter that indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGQREQ=,32, ). If the parameter is set to '0' the subscribed value will be requested.

<Guaranteed bitrate UL>

a numeric parameter that indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as

'32' (e.g. AT+CGQREQ=,32, ). If the parameter is set to '0' the subscribed value will be requested.

<Guaranteed bitrate DL>

a numeric parameter that indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGQREQ=,32, ). If the parameter is set to '0' the subscribed value will be requested. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 80 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

<Delivery order>

a numeric parameter that indicates whether the UMTS bearer shall provide in- sequence SDU delivery or not. 0 no 1 yes 2 subscribed value. Other values are reserved.

<Maximum SDU size>

a numeric parameter (1,2,3,) that indicates the maximum allowed SDU size in octets. If the parameter is set to '0' the subscribed value will be requested.

<SDU error ratio>

a string parameter that indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined only for conforming traffic. The value is specified as 'mEe'. As an example a target SDU error ratio of 5o10-3 would be specified as '5E3' (e.g. AT+CGQREQ=,"5E3",).

'0E0' means subscribed value.

<Residual bit error ratio>

a string parameter that indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value is specified as 'mEe'. As an example a target residual bit error ratio of 5o10-3 would be specified as '5E3' (e.g. AT+CGQREQ=,"5E3",). '0E0' means subscribed value.

<Delivery of erroneous SDUs>

a numeric parameter that indicates whether SDUs detected as erroneous shall be delivered or not. 0 no 1 yes 2 no detect 3 subscribed value Other values are reserved. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 81 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

<Transfer delay>

a numeric parameter (0,1,2,) that indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the other SAP, in milliseconds. If the parameter is set to '0' the subscribed value will be requested.

<Traffic handling priority>

a numeric parameter (1,2,3,) that specifies the relative importance for handling of all SDUs belonging to the UMTS bearer compared to the SDUs of other bearers. If the parameter is set to '0' the subscribed value will be requested.

<PDP_type> (see +CGDCONT and +CGDSCONT commands). If a value is omitted for a particular class then the value is considered to be unspecified. Supported Values:

<cid>

(1-11)

<Traffic class>

(0-4)

<Maximum bitrate UL>

(0-8640)

<Maximum bitrate DL>

(0-8640)

<Guaranteed bitrate UL>

(0-8640)

<Guaranteed bitrate DL>

(0-8640)

<Delivery order>

(0-2) COBHAM PRIVATE Document: 98-181261 Revision:

A

<Maximum SDU size>

(0-1520)

<SDU error ratio>

("1E6"-"1E1","0E0").

<Residual bit error ratio>

("6E8"-"5E2","0E0")

<Delivery of erroneous SDUs>

(0-3)

<Transfer delay>

(0-4000)

<Traffic handling priority>

(0-3)

<PDP_type>

"IP"

Page:

Level: COM 82 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual 3G Quality of Service Profile (Negotiated) 3G Quality of Service Profile (Negotiated) Ref : [3GPP_TS27]

Command Possible response(s)

+CGEQNEG =[<cid>[,<cid>[,]]]

+CGEQNEG=?

Defined Values:

<cid>

+CGEQNEG: <cid>, <Traffic class> ,

<Maximum bitrate UL>,

<Maximum bitrate DL> ,

<Guaranteed bitrate UL>,

<Guaranteed bitrate DL> ,

<Delivery order> ,

<Maximum SDU size> ,

<SDU error ratio> ,

<Residual bit error ratio> ,

<Delivery of erroneous SDUs> ,

<Transfer delay> ,

<Traffic handling priority>

+CGEQNEG: (list of <cid>s associated with active contexts) a numeric parameter which specifies a particular PDP context definition (see +CGDCONT and

+CGDSCONT commands). The following parameters are defined in 3GPP TS 23.107 -

<Traffic class>

a numeric parameter that indicates the type of application for which the UMTS bearer service is optimised. 0 conversational 1 streaming 2 interactive 3 background Other values are reserved.

<Maximum bitrate UL>

a numeric parameter that indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. +CGEQNEG:,32, ).

<Maximum bitrate DL>

a numeric parameter that indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP As an example a bitrate of 32kbit/s would be specified as '32' (e.g. +CGEQNEG:,32, ). COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 83 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

<Guaranteed bitrate UL>

a numeric parameter that indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as

'32' (e.g. +CGEQNEG:,32, ).

<Guaranteed bitrate DL>

a numeric parameter that indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. +CGEQNEG:,32, ).

<Delivery order>

a numeric parameter that indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not. 0 no 1 yes Other values are reserved.

<Maximum SDU size>

a numeric parameter that (1,2,3,) indicates the maximum allowed SDU size in octets.

<SDU error ratio>

a string parameter that indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined only for conforming traffic. The value is specified as 'mEe'. As an example a target SDU error ratio of 5o10-3 would be specified as '5E3' (e.g. +CGEQNEG:,"5E3",).

<Residual bit error ratio>

a string parameter that indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value is specified as 'mEe'. As an example a target residual bit error ratio of 5o10-3 would be specified as '5E3' (e.g. +CGEQNEG:,"5E3",).

<Delivery of erroneous SDUs>

a numeric parameter that indicates whether SDUs detected as erroneous shall be delivered or not. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 84 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual 0 - no 1 - yes 2 - no detect Other values are reserved.

<Transfer delay>

a numeric parameter (0,1,2,) that indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the other SAP, in milliseconds.

<Traffic handling priority>

a numeric parameter (1,2,3,) that specifies the relative importance for handling of all SDUs belonging to the UMTS bearer compared to the SDUs of other bearers. If a value is omitted for a particular class then the value is considered to be unspecified. Supported Values:

<cid>

(1-11) COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 85 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual 3G Quality of Service Profile (Minimum Acceptable) 3G Quality of Service Profile (Minimum acceptable). Ref : [3GPP_TS27]

Command Possible response(s)

+CGEQMIN=[<cid> [,

<Traffic class> [,

<Maximum bitrate UL>[,

<Maximum bitrate DL>[,

<Guaranteed bitrate UL>[,

<Guaranteed bitrate DL>[,

<Delivery order>[,

<Maximum SDU size>[,

<SDU error ratio> [,

<Residual bit error ratio> [,

<Delivery of erroneous SDUs> [,

<Transfer delay> [,

<Traffic handling priority>]]]]]]]]]]]]]

+CGEQMIN?

+CGEQMIN=?

Defined Values:

<cid>

+CGEQMIN: <cid>, <Traffic class> ,

<Maximum bitrate UL>,

<Maximum bitrate DL> ,

<Guaranteed bitrate UL> ,

<Guaranteed bitrate DL>,

<Delivery order> ,

<Maximum SDU size> ,

<SDU error ratio> ,

<Residual bit error ratio> ,

<Delivery of erroneous SDUs> ,

<Transfer delay> ,

<Traffic handling priority> [<CR><LF>+CGEQMIN:

<cid>,

<Traffic class> ,

<Maximum bitrate UL> ,

<Maximum bitrate DL> ,

<Guaranteed bitrate UL> ,

<Guaranteed bitrate DL>,

<Delivery order> ,

<Maximum SDU size> ,

<SDU error ratio> ,

<Residual bit error ratio> ,

<Delivery of erroneous SDUs> ,

<Transfer delay> ,

<Traffic handling priority>

+CGEQMIN: <PDP_type>,

(list of supported <Traffic class>s) ,

(list of supported <Maximum bitrate UL>s) ,

(list of supported <Maximum bitrate DL>s),

(list of supported <Guaranteed bitrate UL>s),

(list of supported <Guaranteed bitrate DL>s) ,

(list of supported <Delivery order>s) ,

(list of supported <Maximum SDU size>s) ,

(list of supported <SDU error ratio>s) ,

(list of supported <Residual bit error ratio>s) ,

(list of supported <Delivery of erroneous SDUs>s) ,

(list of supported <Transfer delay>s) ,

(list of supported <Traffic handling priority>s) a numeric parameter which specifies a particular PDP context definition (see +CGDCONT and

+CGDSCONT commands). The following parameters are defined in 3GPP TS 23.107 -

COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 86 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

<Traffic class>

a numeric parameter that indicates the type of application for which the UMTS bearer service is optimised. 0 conversational 1 streaming 2 interactive 3 background Other values are reserved.

<Maximum bitrate UL>

a numeric parameter that indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=,32, ).

<Maximum bitrate DL>

a numeric parameter that indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=,32, ).

<Guaranteed bitrate UL>

a numeric parameter that indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as

'32' (e.g. AT+CGEQMIN=,32, ).

<Guaranteed bitrate DL>

a numeric parameter that indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=,32, ).

<Delivery order>

a numeric parameter that indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not. 0 no 1 yes Other values are reserved. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 87 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

<Maximum SDU size>

a numeric parameter (1,2,3,) that indicates the maximum allowed SDU size in octets.

<SDU error ratio>

a string parameter that indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined only for conforming traffic. The value is specified as 'mEe'. As an example a target SDU error ratio of 5o10-3 would be specified as '5E3' (e.g. AT+CGEQMIN=,"5E3",).

<Residual bit error ratio>

a string parameter that indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value is specified as 'mEe'. As an example a target residual bit error ratio of 5o10-3 would be specified as '5E3' (e.g. AT+CGEQMIN=,"5E3",).

<Delivery of erroneous SDUs>

a numeric parameter that indicates whether SDUs detected as erroneous shall be delivered or not. 0 no 1 yes 2 no detect Other values are reserved.

<Transfer delay>

a numeric parameter (0,1,2,) that indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the other SAP, in milliseconds.

<Traffic handling priority>

a numeric parameter (1,2,3,) that specifies the relative importance for handling of all SDUs belonging to the UMTS bearer compared to the SDUs of other bearers.

<PDP_type>

(see +CGDCONT and +CGDSCONT commands). If a value is omitted for a particular class then the value is considered to be unspecified. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 88 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Supported Values:

<cid>

(1-11)

<Traffic class>

(0-3)

<Maximum SDU size>

(1-1520)

<SDU error ratio>

("1E6"-"1E1").

<Maximum bitrate UL>

<Residual bit error ratio>

(1-8640)

("6E8"-"5E2")

<Maximum bitrate DL>

<Delivery of erroneous SDUs>

(1-8640)

<Guaranteed bitrate UL>

(1-8640)

(0,1,2)

<Transfer delay>

(1-4000)

<Guaranteed bitrate DL>

<Traffic handling priority>

(1-8640)

<Delivery order>

(0,1)

(1-3)

<PDP_type>

"IP"

COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 89 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual PDP Context Activation PDP context activate or deactivate. Ref : [3GPP_TS27]

Command Possible response(s)

+CGACT=[<state> [,<cid>[, <cid>[,.]]]] OK ERROR

+CGACT: <cid>, <state>

[<CR><LF>+CGACT: <cid>,<state>[...]]

+CGACT: (list of supported <state>s)

+CGACT?

+CGACT=?

Defined Values:

<state>

indicates the state of PDP context activation 0 deactivated 1 activated Other values are reserved and will result in an ERROR response to the execution command.

<cid>

a numeric parameter which specifies a particular PDP context definition (see the +CGDCONT and

+CGDSCONT commands). Show PDP IP Address Show PDP address. Ref : [3GPP_TS27] section 10.1.14 Command Possible response(s)

+CGPADDR=[<cid> [,<cid> [,]]]

+CGPADDR=?

Defined Values:

<cid>

+CGPADDR: <cid>,<PDP_addr> [...]

+CGPADDR: (list of defined <cid>s) a numeric parameter which specifies a particular PDP context definition

(see the +CGDCONT and +CGDSCONT commands). If no <cid> is specified, the addresses for all defined contexts are returned.

<PDP_address>

a string that identifies the MT in the address space applicable to the PDP. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 90 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual The address may be static or dynamic. For a static address, it will be the one set by the +CGDCONT and

+CGDSCONT commands when the context was defined. For a dynamic address it will be the one assigned during the last PDP context activation that used the context definition referred to by <cid>.

<PDP_address> is omitted if none is available. Supported Values

<cid>

(1-11)

<PDP_address>

(0.0.0.0-255.255.255.255) Define Secondary PDP Context Define Secondary PDP Context. Ref : TS 27.007 - 460 section 10.1.2 Command Possible response(s)

+CGDSCONT=[<cid> ,<p_cid> [,

<d_comp>

[,<h_comp>]]]

+CGDSCONT?

+CGDSCONT=?

Defined Values:

<cid>

OK ERROR

+CGDSCONT: <cid>, <p_cid>, <data_comp>,

<head_comp>

+CGDSCONT: (range of supported <cid>s),

(list of <cid>s for active primary contexts),

<PDP_type>,,,(list of supported <d_comp>s),

(list of supported <h_comp>s)

(PDP Context Identifier) a numeric parameter which specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. The range of permitted values (minimum value = 1) is returned by the test form of the command.

<p_cid>

(Primary PDP Context Identifier) a numeric parameter which specifies a particular PDP context definition which has been specified by use of the +CGDCONT command. The parameter is local to the TE-MT interface. The list of permitted values is returned by the test form of the command. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 91 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual

<PDP_type>

(Packet Data Protocol type) a string parameter which specifies the type of packet data protocol IP Internet Protocol (IETF STD 5) IPV617 Internet Protocol, version 6 (IETF RFC 2460) PPP Point to Point Protocol (IETF STD 51)

<d_comp>

a numeric parameter that controls PDP data compression (applicable to GPRS only) 0 off (default if value is omitted) 1 on Other values are reserved.

<h_comp>

a numeric parameter that controls PDP header compression 0 off (default if value is omitted) 1 on Other values are reserved. NOTE. At present only one data compression algorithm (V.42bis) is provided in SNDCP. If and when other algorithms become available, a command will be provided to select one or more of these.

(GPRS only) Supported Values:

<cid>

(1-11)

<p_cid>

(1-11)

<PDP_type>

PPP Point to Point Protocol (IETF STD 51)

<d_comp>

17 IPv6 is not supported by the Inmarsat network. COBHAM PRIVATE Document: 98-181261 Revision:

A 0 off (default if value is omitted)

<h_comp>

0 off (default if value is omitted) 1 on Page:

Level: COM 92 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Define Traffic Flow Template Define Traffic Flow Template. Ref : [3GPP_TS27]

NOTE: source and destination fields are from the networks perspective. Command

+CGTFT=[<cid>, [<packet filter identifier>, <evaluation precedence index> [,<source address and subnet mask> [,<protocol number (ipv4) / next header (ipv6)> [,<destination port range> [,<source port range> [,<ipsec security parameter index (spi)> [,<type of service (tos) (ipv4) and mask /

traffic class (ipv6) and mask> [,<flow label (ipv6)> ]]]]]]]]]

+CGTFT?

+CGTFT=?

Possible response(s) OK ERROR

+CGTFT:

<cid>,

<packet filter identifier>, <evaluation precedence index>, <source address and subnet mask>, <protocol number (ipv4) / next header (ipv6)>, <destination port range>, <source port range>, <ipsec security parameter index (spi)>, <type of service (tos) (ipv4) and mask /

traffic class (ipv6) and mask>, <flow label (ipv6)>

+CGTFT: <PDP_type>, (list of supported

<packet filter identifier>s), (list of supported

<evaluation precedence index>s), (list of supported <source address and subnet mask>s), (list of supported <protocol number (ipv4) /

next header (ipv6)>s), (list of supported <destination port range>s),

(list of supported <source port range>s), (list of supported <ipsec security parameter index (spi)>s),

(list of supported <type of service

(tos) (ipv4) and mask / traffic class

(ipv6) and mask>s), (list of supported

<flow label (ipv6)>s) COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 93 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Defined Values:

<cid>: a numeric parameter which specifies a particular PDP context definition (see the +CGDCONT and

+CGDSCONT commands).

<packet filter identifier>: Numeric parameter, value range from 1 to 8.

<source address and subnet mask>: Consists of dot-separated numeric (0-255) parameters on the form

'a1.a2.a3.a4.m1.m2.m3.m4', for IPv4 and

'a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16. m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14.m15.m16', for IPv618.

<protocol number (ipv4) / next header (ipv6)18>: Numeric parameter, value range from 0 to 255. Refer to the Assigned Internet Protocol Number as defined by the Internet Assigned Numbers Authority (IANA). http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml

<destination port range>: Consists of dot-separated numeric (0-65535) parameters on the form 'f.t'.

<source port range>:Consists of dot-separated numeric (0-65535) parameters on the form 'f.t'.

<ipsec security parameter index (spi)>: Hexadecimal parameter, value range from 00000000 to FFFFFFFF.

<type of service (tos) (ipv4) and mask / traffic class (ipv6)18 and mask>:

Dot-separated numeric (0-255) parameters on the form 't.m'.

<flow label (ipv6)>: Hexadecimal parameter, value range from 00000 to FFFFF. Valid for IPv6 only.

<evaluation precedence index>: Numeric parameter, value range from 0 to 255. In addition to the Packet Filter and Evaluation Precedence Index, each TFT must contain at least one of the following parameters. Some parameters are mutually exclusive; the table below shows which parameters can be used together. 18 IPv6 is not supported by the Inmarsat network. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 94 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual For example, if you want to define a Source address and subnet mask, and an IPSec SPI, the only combination that allows the use of these two parameters together is combination 2. Combination 2 also gives you the option to define Protocol number and Type of service, if required, but no other parameter is available in this combination. Table 10-4: TFT Parameter Combinations Modify PDP Context PDP Context Modify. Ref : [3GPP_TS27]

Command Possible response(s)

+CGCMOD=[<cid>[,<cid>[,]]]

+CGCMOD=?

Defined Values:

<cid>

OK ERROR

+CGCMOD: (list of <cid>s associated with active contexts) a numeric parameter which specifies a particular PDP context definition (see the +CGDCONT and

+CGDSCONT commands). Supported Values:

<cid>

(1-11) COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 95 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Binding a TCP Session to a Primary PDP Context The AT command for binding between a TCP Session and one or more PPPoE Sessions is _IPDPS. _I means it is part of the Inmarsat BGAN AT command extension. PDPS means Primary PDP Context Select. The purpose of this select command is to select a particular PPPoE Session from one or more PPPoE Sessions established with the Server. This AT command/response shall be used over a TCP session; it shall not be available via PPPoE. Command Possible response(s) _IPDPS=<IP_addr>

_IPDPS=PPPoE_Session_ID _IPDPS?

_IPDPS=?

OK ERROR _IPDPS:

<PPPoE_Session_ID>,<IP_addr>

ERROR The set command can select the primary PDP using either:

The PPPoE Session ID. The IPv4 address obtained by the PPPoE client in the IPCP phase of the PPP set up. All subsequent PDP Context related AT commands from the TCP Session are applicable to the specified PPPoE Session. AT commands that are unrelated to PDP Context are not affected by the set command. Returns ERROR if the primary PDP does not exist. If the primary PDP is already in use, the previous owner of the primary PDP is notified of the loss of ownership through at spontaneous _IPDPS:0,0.0.0.0 message. The same _IPDPS:0,0.0.0.0 is also used when the call is torn down (as it is not possible to send further commands to a call which no longer exists). The read command returns the currently selected primary PDP by the TCP Session that sends the read command. If no PPPoE Session selected, 0, 0.0.0.0 is returned. Defined Values

<PDP_addr>: a string parameter that identifies the PPPoE by the address of the Primary PDP Context. Two values are possible, the PPPoE session ID or the IP address associated with that primary PDP. The two are recognized by their format. The PPPoE session ID is a simple number, while the IP address is an IPv4 address in the form aaa.bbb.ccc.ddd. COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 96 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Appendix E. Troubleshooting & Maintenance Actions Each fault detected by the AVIATOR S SATCOM System is identified by a unique troubleshooting code (Figure 10-29). Refer to section 10.1.1, BITE Scanning - Troubleshooting Code for guidance in obtaining the troubleshooting code for events detected and listed in the BITE Scanning page. Figure 10-29: MCDU - BITE - Troubleshooting Code Using the troubleshooting code as a reference, refer to Table 10-5 in Appendix E.1 to determine the recommended maintenance action. Identification Reported to CMS Recommended maintenance action Maintenance Message Troubleshooting Code List of Accused Elements

(LRU/WRG) Severity ATA First step Second Step Third Step 5140 MCDU3/CSDU/WRG LOW 3461 Replace CSDU Replace MCDU 2 Check Wiring Figure 10-30: BITE - FDS - Troubleshooting Code Example COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 97 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Table 10-5: Troubleshooting codes and recommended maintenance actions Identification Reported to CMS Recommended maintenance action Maintenance Message Troubleshooting Code List of Accused Elements

(LRU/WRG) Severity ATA First step Second Step Third Step 5101 5107 5108 510D 510E 510F 511A 511B 5130 5134 5138 513C 5140 5154 5158 5160 5163 5164 5165 5166 5170 5171 5172 5173 517A 517B 517C 517D 517E 517F 5501 5506 590B CSDU FAULT CSDU FAULT CSDU FAULT CSDU FAULT HIGH HIGH HIGH HIGH 2315 Reload CSDU SW Replace CSDU 2315 Reload CSDU SW Replace CSDU 2315 Reload CSDU SW Replace CSDU 2315 Reload CSDU SW Replace CSDU SCM SORT INTEG HIGH 2315 SCM UORT INTEG LOW 2315 Reload Secure ORT Reload USER ORT Replace SCM Replace SCM CSDU FAULT CSDU FAULT LOW LOW 2315 Replace CSDU 2315 Replace CSDU IRS1/CSDU/WRG HIGH 3421 Replace CSDU Replace IRS 1 Check Wiring IRS2/CSDU/WRG HIGH 3421 Replace CSDU Replace IRS 2 Check Wiring MCDU1/CSDU/WRG LOW 3461 Replace CSDU Replace MCDU 1 Check Wiring MCDU2/CSDU/WRG LOW 3461 Replace CSDU Replace MCDU 2 Check Wiring MCDU3/CSDU/WRG LOW 3461 Replace CSDU Replace MCDU 3 Check Wiring CMU1/CSDU/WRG HIGH 2327 Replace CSDU Replace CMU1 Check Wiring CMU2/CSDU/WRG HIGH 2327 Replace CSDU Replace CMU2 Check Wiring ATC HIGH 3453 Replace AESID CSDU OVER TEMP LOW 2315 Replace CSDU CSDU OVER TEMP LOW 2315 Replace CSDU CSDU OVER TEMP LOW 2315 Replace CSDU CSDU OVER TEMP LOW 2315 Replace CSDU SCM ACTIVATION HIGH 2315 Replace SCM HIGH 2315 N\A POWER SUPPLY INTERRUPT MANUAL RESET AUTO RESET CMU1 CMU1 CMU1 CMU2 CMU2 CMU2 CSDU FAULT CSDU FAULT HIGH HIGH LOW LOW LOW LOW LOW LOW LOW LOW 2315 N\A 2315 N\A 2327 Replace CMU1 2327 Replace CMU1 2327 Replace CMU1 2327 Replace CMU2 2327 Replace CMU2 2327 Replace CMU2 2315 Reload CSDU SW Replace CSDU 2315 Replace CSDU SCM FAULT HIGH 2315 Replace SCM COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 98 of 99 CC: 1

(T: 99-161853-H) AVIATOR 700S User Manual Table 10-5: Troubleshooting codes and recommended maintenance actions Identification Reported to CMS Recommended maintenance action Maintenance Message Troubleshooting Code List of Accused Elements

(LRU/WRG) Severity ATA First step Second Step Third Step CSDU FAULT LOW 2315 Replace CSDU CSDU/SCM/WRG HIGH 2315 Replace CSDU Replace SCM Check Wiring SCM OVER TEMP HIGH 2315 Replace SCM SCM FAULT HIGH 2315 Replace SCM SCM FAULT LOW 2315 Replace SCM SCM FAULT HIGH 2315 Replace SCM SCM ACTIVATION HIGH 2315 Replace SCM DLNA FAULT HIGH 2315 Replace DLNA Replace HGA Check Wiring POWER SUPPLY INTERRUPT HIGH 2315 N\A HPA OVER TEMP HIGH 2315 Replace HPA HPA FAULT HPA FAULT HPA FAULT HPA FAULT HPA FAULT HPA FAULT HIGH HIGH HIGH HIGH HIGH HIGH 2315 Replace HPA 2315 Replace HPA 2315 Replace HPA 2315 Replace HPA 2315 Replace HPA 2315 Replace HPA HPA/DLNA/WRG HIGH 2315 Replace HPA Check Wiring HGA FAULT HGA FAULT HGA FAULT HGA FAULT HGA FAULT HGA FAULT HGA FAULT HIGH HIGH HIGH HIGH HIGH HIGH LOW 2315 Replace HGA Replace HPA 2315 Replace HGA 2315 Replace HGA 2315 Replace HGA 2315 Replace HGA 2315 Replace CSDU Replace HGA Check Wiring 2315 Replace HGA HGA/CSDU/WRG HIGH 2315 Replace CSDU Replace HGA Check wiring CSDU/SCM/WRG HIGH 2315 Replace CSDU Replace SCM Check Wiring CSDU/HPA/WRG HIGH 2315 Replace CSDU Replace HPA Check Wiring MMR HIGH 3458 Replace GNSS MMR/CSDU/WRG HIGH 3458 Replace CSDU Replace GNSS Check Wiring 5A06 6002 6003 6101 6103 6104 6105 7101 7301 7303 7304 7305 7306 7307 7308 7309 730A 7401 7402 7403 7404 7405 7407 7408 7409 8101 8103 9001 9002 9102 ETH2/CSDU/WRG LOW 2315 Replace CSDU 9103 ETH3/CSDU/WRG LOW 2315 Replace CSDU Replace PIESD/Cabin Interface Device Replace Ethernet Dataloader Check wiring Check wiring COBHAM PRIVATE Document: 98-181261 Revision:

A Page:

Level: COM 99 of 99 CC: 1

(T: 99-161853-H)

 

 

 

 

 

 

__| Black printing on white label. 8 7 6 5 VW 4 3 | 2 | 1 REVISIONS N OTES . REV | DESCRIPTION DATE DRAWN NO APPROVED

, | AA | LABEL PRINTING aaa A. CARON 2D DATAMATRIX :

Digits-only for PNR : 822-341 7-501 Alphanumeric characters for encoding. MFR, SER, PNR, DMF e Variable for 822-3417-501 : SER, DMF. Example :

MFR 51351/SER SSSSSSSSSSSSSSS/PNR 822-341 7-501/DMF MMYYYY _

MCHPA AVIATOR 700S (HPA-3001 combined with PNR 822-3417-601 SDU-3001 and Type F DLNA) FCC ID : 2ZA6TS-AVIATOR700S SER XXXXXXXXxXx IC: 28544-AVIATOR700S ome aaa er 202-SMIK046 INSPECT OMI MMYYYY =

DO178C-DO160G ENV CAT. COMANT INDUSTRIES, INC DBA COBHAM 677 Burning Tree Road, Fullerton, CA $2833 USA Weight : 11 Lb Produced Month/Year Example : 042019 For insoection stameo Letters and symbols shall appear black on a white background. THESE COMMODITIES, TECHNOLOGY OR SOFTWARE ARE CONTROLLED IN NAME DATE ia ee WHEN EXPORTED FROM THE UNITED States, |DRAWN A. CARON 08/26/22 Comant Industries, Inc. DIVERSION CONTRARY TO U.S. LAW IS Fullerton, CA iA Po PROHIBITED. ~ CHECKED I ENG APPR. ei) i TITLE SET ere eal eerie men ZO LABEL PRINTING S/N, HPA-5015, ANGLES #0.5 ne High Power Amplifier INCHES "B CAGE CODE | DWG NO s DO NOT SCALE DRAWING . 156-200021 NEXT ASSY USED ON | x 405 | 5 51351 THE INFORMATION CONTAINED IN THIS DRAWING XXX 0.008 xX 0.2 TYPED SIGNATURES INDICATE APPROVAL. IS THE PROPERTY OF COBHAM, ANY REPRODUCTION HANDWRITTEN SIGNATURE APPROVAL OF IN PART OR AS A WHOLE WITHOUT WRITTEN PERMISSION OF COBHAM IS PROHIBITED. XXXX +0.004 XXX +0.1 IRDUSTRIES ING, FLESH, Corrpanra, | SCALE: 2:1 | WEIGHT: NA SHEET: 1 OF 1 TEMPLATE 150-744514-01 REV F 7 6 5 LA 4 | 3 2 | 156-200021.AA.DWG

 

 

8 7 6 5 4 3 P/N: 822-3417-501 BOTTOM VIEW AC NON-ENVIRONMENTAL CONNECTOR RADIALL PART NUMBER: 620601355 CAVITY A : 1C71 CAVITY B : 71C1 CAVITY C : 13C2 REAR VIEW DETAIL A SCALE 2 : 1 SEE NOTE 3 POLARIZATION CODE : 08 DETAIL C SCALE 2 : 1 D C B A 0,591 15,000 CONDUCTIVE FACE FOR EARTH BOND TEST

. x a m 7 2

. 2

. x a m 6

. 7 5 CHEMICALLY CONVERTED TO MIL-DTL-5541F TYPE II CLASS 3 TOP AC

2 DESCRIPTION REV AA HPA Outline Drawing AB Revised by ECN 22-168 AC Revised by ECN 23-073 1 REVISIONS DRAWN A. Caron I. Demirel A. Caron DATE 09/13/22 11/29/22 11/03/23 CHECKED A. Bond A. Bond APPROVED D. Holloway D. Holloway SEE NOTE 7 DETAIL F SCALE 2 : 1 FRONT VIEW DETAIL B SCALE 2 : 1 B F BLACK ANODIZED FACE PLATE 6 8

, 7 7

, 9 9 1 4 8

, 1 8

, 6 4 7 9 1

, 0 6 6

, 3 5 3 9 2,40 61,0 NOTES :

1. 2. 3. 4. 5. 6. 7. 8. MASS : 5.0 KG [11 LB] MAX. APPROXIMATE CENTER OF GRAVITY INDICATED BY DARK PORTION INDICATES SOLID PART OF POLARISING KEYWAYS. ALL EXTERNAL DIMENSIONS CONFORM TO ARINC 600-19 SPECIFICATIONS FOR LRU CASE SIZE 2. LABEL DETAILS ON PAGE 2. ENVIRONMENTAL CHARACTERISTICS OF THE HPA IS SUMMARIZED IN THE QTS DOCUMENT: 871-A1853 QTS Generic HPA-3001 IS THE CUSTOMER TYPE NUMBER AND HPA-5015 IS THE MANUFACTURER TYPE NUMBER ALL DIMENSIONS NOT BALLOONED ARE REFERENCE ONLY. MATERIAL & FINISH :

9. MATERIAL :

SIDE COVERS, BACK PLANE : 1.5mm THICK ALUMINIUM ALLOY GRADE 5754 H22 AS PER EN 485 (EN AW-5082) FRONT FACE: ALUMINIUM ALLOY 6082 T6 AS PER EN 485 (EN AW-6082) FINISH : CHEMICAL CONVERSION TO MIL-DTL-5541F TYPE II CLASS 3. PRIMER : DESOPRIME CF/CA7502E CHROME-FREE EPOXY PRIMER. TOPCOAT : CA8311 HS POLYURETHANE TOPCOAT BLACK MATTE. 10. 11. 12. COLOR DESIGNATION FS37038. 13. FACEPLATE : ANODIZED BLACK. 14. ALL SURFACES NOT INDICATED ARE PAINTED. THESE COMMODITIES, TECHNOLOGY OR SOFTWARE ARE CONTROLLED IN ACCORDANCE WITH THE UNITED STATES EXPORT ADMINISTRATION REGULATIONS. WHEN EXPORTED FROM THE UNITED STATES, DIVERSION CONTRARY TO U.S. LAW IS PROHIBITED. UNLESS OTHERWISE SPECIFIED:

DIMENSIONS ARE IN INCHES [MM]

TOLERANCES:

ANGLES 0.5 INCHES

.XX 0.02

.XXX 0.008

.XXXX 0.004 mm

.X 0.5

.XX 0.2

.XXX 0.1 NAME I. Demirel DATE 11/29/22 SEE MATERIAL & FINISH SEE MATERIAL & FINISH DRAWN CHECKED ENG APPR. Q.A. MATERIAL:

FINISH:

DO NOT SCALE DRAWING TYPED SIGNATURES INDICATE APPROVAL. HANDWRITTEN SIGNATURE APPROVAL OF THIS DOCUMENT IS ON FILE AT COMANT INDUSTRIES, INC., FULLERTON, CALIFORNIA. NEXT ASSY USED ON THE INFORMATION CONTAINED IN THIS DRAWING IS THE PROPERTY OF COBHAM. ANY REPRODUCTION IN PART OR AS A WHOLE WITHOUT WRITTEN PERMISSION OF COBHAM IS PROHIBITED. Comant Industries, Inc Fullerton, CA TITLE OUTLINE DRAWING, HPA-5015, SIZED High Power Amplifier CAGE CODE 51351 1:5 DWG NO. 154-200005 SHEET:

11 Lb 154-200005.AC.DWG REV AC 1 OF 2 WEIGHT:

SCALE:

D C B A A C BOTTOM 6,97 0,197 177 5 12,72 max. 323,0 max. 13,70 max. 348,0 max. TOP VIEW

, 7 9 1 0 6 0 1

, 5 7 2 TEMPLATE 150-744516-01 REV F 8 7 6 RFID TAG 0,079 max. 2,00 max. 5 4 3 2 1 11/29/2311/05/2312/6/23 8 7 6 5 4 3 2 1 D C B A D AC RFID TAG E DETAIL E SCALE 2 : 1 DETAIL D SCALE 2 : 1 THESE COMMODITIES, TECHNOLOGY OR SOFTWARE ARE CONTROLLED IN ACCORDANCE WITH THE UNITED STATES EXPORT ADMINISTRATION REGULATIONS. WHEN EXPORTED FROM THE UNITED STATES, DIVERSION CONTRARY TO U.S. LAW IS PROHIBITED. THE INFORMATION CONTAINED IN THIS DRAWING IS THE PROPERTY OF COBHAM. ANY REPRODUCTION IN PART OR AS A WHOLE WITHOUT WRITTEN PERMISSION OF COBHAM IS PROHIBITED. D C B A Comant Industries, Inc Fullerton, CA TITLE OUTLINE DRAWING, HPA-5015, SIZED High Power Amplifier CAGE CODE 51351

DWG NO. 154-200005 SHEET:

11 Lb 154-200005.AC.DWG REV AC 2 OF 2 WEIGHT:

SCALE:

TEMPLATE 150-744516-01 REV F 8 7 6 5 4 3 2 1

 

 

8 ARINC 600 CONNECTOR NON ENVIRONMENTAL AMPHENOL PART NO :

AJ2-203CF-40081577 CAVITY A : 71W1A CAVITY B : 120Q2 CAVITY C : 12F5C2 D CONNECTING PART NON ENVIRONMENTAL AMPHENOL PART NO :

AD2-203CF-30081510 CAVITY A : 71W1A CAVITY B : 120Q2 CAVITY C : 12F5C2 7 6 5 4 3 BOTTOM VIEW NOTE 4 AB 0.16 4.0 P/N: 822-3418-501 2 DESCRIPTION REV AA SDU Outline Drawing AB Revised by ECN 22-170 1 REVISIONS DRAWN A. Caron I. Demirel DATE 09/08/22 29/11/22 CHECKED A. Bond APPROVED D. Holloway REAR VIEW B See Sheet 2 F D See Sheet 2 TOP FRONT VIEW FRONT REAR A See Sheet 2 AB 1 7

. 6 4

. 0 7 1 AB 9 4 2

. 2 3 6 6 3 0

. 1 9

. AB AB B SEE NOTE 3 INDEX CODE 81 AB AB 1.476 max. 37.49 max. 1 0

. 0 4

. 2 3

. 0 0

. 1 6 AB C B A 0 2 0

. 4 7 5 5 9

. 3 0.38 0.02 9.65 0.5 B BOTTOM 6.54 0.2 166 5 AB 12.58 0.04 319.5 1 13.52 0.04 343.5 1 NOTE 4 E TOP VIEW 2

. 0 2 1

. 1 5

. 4 8 2 AB 0.59 15.0 CONDUCTIVE FACE FOR EARTH BONDING TEST MAINTENANCE CONNECTOR 10/100 BASE-T ETHERNET CONNECTOR CONNECTING PART :

10/100 BASE-T ETHERNET CONNECTOR RJ45 MALE MICRO USB 2.0 TYPE B CONNECTOR CONNECTING PART MICRO USB 2.0 TYPE B PLUG MAINTENANCE CONNECTOR COVER ARINC PULL HANDLE OMNIPLESS PART NO. 500-A0521 3 0

. 0 4 6

. 7 8

. 0 0

. 4 9 1 AB C See Sheet 2 E W/2 0.02 W/2 0.5

. 5 0 5 1

. 7 5 2 0

. 0 5 2 2 W

. 1 0

. 0 6 8

. 7 3

. 0 7

. 9 9 1 AB NOTE 16 NOTES :

PRESSURE DROP 26 2 PA @ 13.7 CUBIC FEET PER MINUTE / 40C (0.104" OF WATER). UNIT MASS 4.2 KG (9.26 LB). GUARANTEED MAX MASS 4.4 KG (9.7 LB). INDICATES APPROXIMATE CENTER OF GRAVITY (COG). DARK PORTION INDICATES SOLID PART OF POLARISING KEYWAYS (INDEX CODE 81). DO NOT BLOCK COOLING AIR HOLES. 1. 2. 3. 4. AIRFLOW RATE IN BLOW-THROUGH COOLING MODE 26 KG/HR @ 40C (13.7 CUBIC FEET PER MINUTE). AIRFLOW RATE IN DRAW-THROUGH COOLING MODE 20.3 KG/HR @ 40C. 5. PRESSURE DROP IS 5 3 MM OF WATER @ THE STANDARD AIRFLOW RATE. 6. 7. 8. ALL EXTERNAL DIMENSIONS CONFORM TO ARINC 600-19 SPECIFICATIONS FOR LRU CASE SIZE 2. INSTALLATION CLEARANCE : AS PER ARINC 600. NOMINAL POWER INPUT 93W (0.80 A @ 115 VAC). POWER FACTOR 0.98. MAXIMUM POWER DISSIPATION :

40W. NO INTERNAL FAN. NO FILTRATION OF AIR REQUIRED. ENVIRONMENTAL CHARACTERISTICS OF THE CSDU ARE SUMMARIZED IN THE QTS/QTR DOCUMENTS SDU-3001 IS CUSTOMER TYPE NUMBER AND SDU-5045 IS MANUFACTURER TYPE NUMBER ALL DIMENSIONS NOT BALLOONED ARE REFERENCE ONLY. MATERIAL AND FINISH :

MATERIAL :

14. SIDE COVERS, BACK PLANE, FRONT COVER : ALUMINIUM ALLOY 5052 H32 AS PER EN 485 (EN AW-5052). FRONT FACE : ALUMINIUM ALLOY 6082 T6 AS PER EN 485 (EN AW-6082). 15. 16. PRIMER : DESOPRIME CF/CA7502E. TOPCOAT : DESOTHANE CA8311 HS POLYURETHANE BLACK MATT. 17. FINISH : CHEMICAL CONVERSION TO MIL-DTL-5541F TYPE II CLASS 3. PAINT : PPG AEROSPACE COATING. FRONT FACE BLACK ANODIZED ALUMINIUM. 9. 10. 11. 99-165878. 12. 13. AB D C B A BLOW THROUGH DRAW THROUGH AIRFLOW DIRECTION FRONT HOOK NAS622-CT3 DIMENSIONS ARE MILLIMETERS. DIMENSIONS IN BRACKETS ARE INCHES. NEXT ASSY USED ON THE INFORMATION CONTAINED IN THIS DRAWING IS THE PROPERTY OF COBHAM. ANY REPRODUCTION IN PART OR AS A WHOLE WITHOUT WRITTEN PERMISSION OF COBHAM IS PROHIBITED. TEMPLATE 150-744516-01 REV F 8 7 6 5 4 3 2 1 THESE COMMODITIES, TECHNOLOGY OR SOFTWARE ARE CONTROLLED IN ACCORDANCE WITH THE UNITED STATES EXPORT ADMINISTRATION REGULATIONS. WHEN EXPORTED FROM THE UNITED STATES, DIVERSION CONTRARY TO U.S. LAW IS PROHIBITED. UNLESS OTHERWISE SPECIFIED:

DIMENSIONS ARE IN INCHES [MM]

TOLERANCES:

ANGLES 0.5 INCHES

.XX 0.02

.XXX 0.008

.XXXX 0.004 mm

.X 0.5

.XX 0.2

.XXX 0.1 NAME DATE I. Demirel 11/29/22 SEE NOTE 13 SEE NOTE 14 DRAWN CHECKED ENG APPR. Q.A. MATERIAL:

FINISH:

DO NOT SCALE DRAWING TYPED SIGNATURES INDICATE APPROVAL. HANDWRITTEN SIGNATURE APPROVAL OF THIS DOCUMENT IS ON FILE AT COMANT INDUSTRIES, INC., FULLERTON, CALIFORNIA. Comant Industries, Inc Fullerton, CA Compact Satellite Data Unit TITLE OUTLINE DRAWING, SDU-5045, SIZED DWG NO. 154-200004 9.26 Lbs CAGE CODE 51351 1:1.5 REV AB SHEET: 1 OF 2 154-200004.AB.DWG WEIGHT:

SCALE:

8 7 6 5 4 3 2 1 DETAIL A SCALE 2 : 1 AB D C B A DTAIL D ECHELLE 3 : 1 DETAIL C SCALE 3 : 1 SEE NOTE 12 DETAIL B SCALE 3 : 1 THESE COMMODITIES, TECHNOLOGY OR SOFTWARE ARE CONTROLLED IN ACCORDANCE WITH THE UNITED STATES EXPORT ADMINISTRATION REGULATIONS. WHEN EXPORTED FROM THE UNITED STATES, DIVERSION CONTRARY TO U.S. LAW IS PROHIBITED. THE INFORMATION CONTAINED IN THIS DRAWING IS THE PROPERTY OF COBHAM. ANY REPRODUCTION IN PART OR AS A WHOLE WITHOUT WRITTEN PERMISSION OF COBHAM IS PROHIBITED. D C B A Comant Industries, Inc Fullerton, CA Compact Satellite Data Unit TITLE OUTLINE DRAWING, SDU-5045, SIZED CAGE CODE 51351 DWG NO. 154-200004 SHEET:

9.26 Lbs 154-200004.AB.DWG REV AB 2 OF 2 WEIGHT:

SCALE:

TEMPLATE 150-744516-01 REV F 8 7 6 5 4 3 2 1

 

 

8 NOTES:

D C B A 7 6 5 4 3 2D DATAMATRIX :

Digits-only for PNR : 405045-01000 Alphanumeric characters for encoding. MFR, SER, PNR, DMF Variable for 405045-01000 : SER, DMF. Example :

MFR 51351/SER SSSSSSSSSSSSSSS/PNR 405045-01000/DMF MMYYYY DESCRIPTION REV AA Initial Release 2 REVISIONS DATE 12/07/23 DRAWN A. CARON 1 CHECKED APPROVED Amendment plate 2,68 68 8 1

, 1 0 3 For inspection stamp Produced Month/Year Example : 042019 Black printing on white label. Letters and symbols shall appear black on a white background. Font: ARIAL - Font Size = 0.05 [1.28 mm]

THESE COMMODITIES, TECHNOLOGY OR SOFTWARE ARE CONTROLLED IN ACCORDANCE WITH THE UNITED STATES EXPORT ADMINISTRATION REGULATIONS. WHEN EXPORTED FROM THE UNITED STATES, DIVERSION CONTRARY TO U.S. LAW IS PROHIBITED. UNLESS OTHERWISE SPECIFIED:

DIMENSIONS ARE IN INCHES [MM]

TOLERANCES:

ANGLES 0.5 INCHES

.XX 0.02

.XXX 0.008

.XXXX 0.004 mm

.X 0.5

.XX 0.2

.XXX 0.1 NAME DATE A. CARON 08/24/23 140000AA00 NA DRAWN CHECKED ENG APPR. Q.A. MATERIAL:

FINISH:

DO NOT SCALE DRAWING TYPED SIGNATURES INDICATE APPROVAL. HANDWRITTEN SIGNATURE APPROVAL OF THIS DOCUMENT IS ON FILE AT COMANT INDUSTRIES, INC., FULLERTON, CALIFORNIA. NEXT ASSY USED ON THE INFORMATION CONTAINED IN THIS DRAWING IS THE PROPERTY OF COBHAM. ANY REPRODUCTION IN PART OR AS A WHOLE WITHOUT WRITTEN PERMISSION OF COBHAM IS PROHIBITED. TEMPLATE 150-744514-01 REV F 7 6 5 4 3 2 Comant Industries, Inc. Fullerton, CA SIZE TITLE LABEL PRINTING S/N, SDU-5045, Compact Satellite Data Unit B DWG NO. 156-200039 SHEET:

NA 156-200039.AA.DWG CAGE CODE 51351 2:1 WEIGHT:

REV AA 1 OF 1 SCALE:

D C B A

 

 

Cobham Aerospace ApS dba. Cobham Aerospace Communications Lyngby Hovedgade 94, 4. 2800 Kgs. Lyngby Denmark Federal Communication Commission Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, MD 21046 USA February 28 2024 Attestation Statement according to 2.911(d)(5)(i) and 2.911(d)(5)(ii) FCC ID: 2A6TS-AVIATOR700S TO WHOM IT MAY CONCERN:

Hereby we certify that the equipment for which authorization is sought is not covered equipment prohibited from receiving an equipment authorization pursuant to section 2.903 of the FCC rules. Further we certify that, as of the date of the filing of the application, Cobham Aerospace Aps

(FRN 0032387763) is not identified on the Covered List as an entity producing covered equipment. Sincerely, _______________

(signature & company stamp) Marcin Kazmierczak Cobham Aerospace ApS dba. Cobham Aerospace Communications FCC Registration Number: 0032387763 Lyngby Hovedgade 94, 4. 2800 Kgs. Lyngby Denmark Phone: +45 32740620 E-Mail: Marcin.kazmierczak@cobham.com Cobham Aerospace ApS dba Cobham Aerospace Communications Registered no.: DK 41 93 36 90. Registered address: Lyngby Hovedgade 94, 2800 Kgs. Lyngby, Denmark www.cobham.com

 

 

Cobham Aerospace ApS Lyngby Hovedgade 94, 4. 2800 Kgs. Lyngby Denmark Cobham Aerospace ApS dba. Cobham Aerospace Communications Lyngby Hovedgade 94, 4. 2800 Kgs. Lyngby Denmark Federal Communication Commission Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, MD 21046 USA Attestation Statement according to 2.911(d)(7) FCC ID: 2A6TS-AVIATOR700S TO WHOM IT MAY CONCERN:

February 28 2024 We, Cobham Aerospace Aps (FRN 0032387763), designate Comant Industries Inc, to act as U.S. agent for service of process. Comant Industries Inc hereby acknowledges the obligation of the U.S. agent for service of process. Further Comant Industries Inc accepts to maintain an agent for no less than one year after the grantee has terminated all marketing and importation or the conclusion of any Commission-related proceeding involving the equipment. Sincerely Signature/company stamp Marcin Kazmierczak Cobham Aerospace Aps dba. Cobham Aerospace Communications Lyngby Hovedgade 94, 4., 2800 Lyngby Denmark Phone: +45 32740620 Mail: marcin.kazmierczak@cobham.com Signature/company stamp Nathaniel Hayes Comant Industries, Inc 577 Burning Tree Road California, 92833 USA Phone: +1 714 870 2420 x123 Mail : Nathaniel.Hayes@cobham.com 2/28/202414 March 2024