User's Manual

ManualsBrandsThrane & Thrane ManualsElectronicsSatellite transceiver for Inmarsat Swift Broadband service

COBHAM PRIVATE

(T: 99-161853-F)

AVIATOR 200S/700S

User Manual

Document

98-158752

Revision

Activity

Function

Role

Name

Date

Signature

Prepared

System Engineer

Adrian Erasmus

Reviewed

System Engineer

CVE

Jorge Perez

Reviewed

Program Manager

Marcin Kazmierczak

Thrane & Thrane A/S

Lundtoftegaardsvej 93D, DK-2800 Kgs. Lyngby, Denmark

29-OCT-2021

Type text here

29-OCT-2021

Summary of content (105 pages)

PAGE 1
AVIATOR 200S/700S User Manual Document : 98-158752 Revision : B Type text here Activity Function Role Name Date Prepared System Engineer DE Adrian Erasmus 29-OCT-2021 Reviewed System Engineer CVE Jorge Perez 29-OCT-2021 Reviewed Program Manager PM Marcin Kazmierczak Signature 29-OCT-2021 Copyright© Thrane & Thrane A/S Lundtoftegaardsvej 93D, DK-2800 Kgs.
PAGE 2
AVIATOR 200S/700S User Manual REVISION HISTORY Revision Author Date Section A B AER AER 21 Apr 2021 28 Oct 2021 All 2.1 Description of Change Initial release. Update to the RF Exposure safe distances.  Thrane & Thrane A/S trading as Cobham Aerospace Communication This Document and any other appended documents and drawings are of  copyright to Thrane & Thrane A/S. It contains proprietary information which is disclosed for information purposes only.
PAGE 3
AVIATOR 200S/700S User Manual TABLE OF CONTENTS PAGE 1 INTRODUCTION ..................................................................................................................... 11 1.1 GENERAL ................................................................................................................................... 11 1.1.1 Purpose ............................................................................................................................ 11 1.1.2 Scope ...............
PAGE 4
AVIATOR 200S/700S User Manual 3.5.2 4 5 3.5.2.1 Service Class .............................................................................................................................. 22 3.5.2.2 Service Class Selection ................................................................................................................ 22 SERVICE ACTIVATION ........................................................................................................... 23 4.
PAGE 5
AVIATOR 200S/700S User Manual 7.2.1 Outgoing Calls – Air-to-Ground (A2G) ................................................................................. 43 7.2.1.1 Manual Dial ................................................................................................................................ 43 7.2.1.2 Directory Dial ............................................................................................................................. 44 7.2.1.3 Initiating an Outgoing Call ......
PAGE 6
AVIATOR 200S/700S User Manual APPENDIX C.1. ASLIACTLINKSTATUS(4) .................................................................................................. 72 APPENDIX C.2. ASLIHISTLINKENTRYNUMBERS(6) ...................................................................................... 72 APPENDIX C.3. ASUSDUINFOVENDOR(2) APPENDIX C.4. ASUSDUINFOFAILURECODE(11) APPENDIX C.5. ASUSDUINFOFAILUREREASON(12) ......................................................................................
PAGE 7
AVIATOR 200S/700S User Manual Appendix E.3.2 Make new log file ............................................................................................... 104 Appendix E.3.3 Add a text line in current log ...............................................................................
PAGE 8
AVIATOR 200S/700S User Manual LIST OF FIGURES PAGE Figure 3-1: INMARSAT SwiftBroadband Coverage ................................................................................... 18 Figure 3-2: AVIATOR 200S SATCOM System – Block Diagram .................................................................. 19 Figure 3-3: AVIATOR 700S SATCOM System ........................................................................................... 19 Figure 4-1: AVIATOR S SCM | IMSI & Smart Card Identification ........
PAGE 9
AVIATOR 200S/700S User Manual Figure 7-4: MCDU - SATCOM Directory Entries ........................................................................................ 35 Figure 7-5: ACP - Initiating a call............................................................................................................ 36 Figure 7-6: ACP - Call connected - Steady green .....................................................................................
PAGE 10
AVIATOR 200S/700S User Manual Figure 9-2: MCDU - SATCOM Config - Cabin calls disabled ....................................................................... 52 Figure 9-3: RMP - SATCOM Config - Cabin calls enabled .......................................................................... 52 Figure 9-4: RMP - SATCOM Config - Cabin calls disabled.......................................................................... 52 Figure 10-1: USB connector under the maintenance connector cover .....................
PAGE 11
AVIATOR 200S/700S User Manual 1 INTRODUCTION 1.1 1.1.1 GENERAL Purpose This document provides a guide for users intending to make voice calls or data connections via the AVIATOR S 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.
PAGE 12
AVIATOR 200S/700S User Manual Table 1-2: List of Acronyms Acronym Description ATC Air Traffic Control AUTO Automatically CFDS Central Fault Display System CHAP Challenge Handshake Authentication Protocol CID Context ID CMU Communication Management Unit CSDU Compact Satellite Data Unit CSP Communication Service Provider CSR Certificate Signing Request CTTIC China Transport Telecommunications & Information Centre dB Decibels DL Downlink DLNA Diplexer/Low Noise Amplifier EFB Elect
PAGE 13
AVIATOR 200S/700S User Manual Table 1-2: List of Acronyms Acronym Description MB Megabyte MCDU Multi-purpose Control and Display Unit MEAS Middle East and Asia MIB Management Information Base NAT Network Address Translation ORC Ocean Region Change OID Object ID ORT Owner Requirements Table PAP Password Authentication Protocol PDL Portable Data Loader PDP Packet Data Protocol PIESD Passenger Information and Entertainment Services Domain PKI Public Key Infrastructure PPPoE Point-
PAGE 14
AVIATOR 200S/700S User Manual 1.3 REFERENCES 1.3.1 External References Table 1-3: List of External References Reference Tag Document Revision [3GPP_TS27] 3GPP TS 27.007 10.3.0 [A781] ARINC 781 7 [ITU-T_V.250] ITU-T V.250 [PKI_CON] PKI CONOPS 0.3 SwiftBroadband Safety 2.0 Overview and PKI Concept of Operations [PKI_OPS] PKI INMARSAT 0.9 Inmarsat SB-S Service – Airline Ops Handbook [GOLD] ICAO GOLD [SVGM] ICAO SVGM [A739A] ARINC 739A 1.3.
PAGE 15
AVIATOR 200S/700S User Manual 2 REGULATORY INFORMATION 2.1 2.1.1 RADIOFREQUENCY RADIATION EXPOSURE INFORMATION AVIATOR 200S 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 50 cm between the radiator and your body. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.
PAGE 16
AVIATOR 200S/700S User Manual 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.
PAGE 17
AVIATOR 200S/700S User Manual 3 SWIFTBROADBAND SAFETY SYSTEM OVERVIEW 3.1 3.1.1 INMARSAT SATELLITE NETWORK 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.
PAGE 18
AVIATOR 200S/700S User Manual Figure 3-1: INMARSAT SwiftBroadband Coverage 3.2 3.2.1 AVIATOR S SATCOM SYSTEM FUNCTIONS AND FEATURES System Overview – AVIATOR 200S The AVIATOR 200S 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:    Two simultaneous voice calls supported by multiple aircraft audio configurations.
PAGE 19
AVIATOR 200S/700S User Manual Figure 3-2: AVIATOR 200S SATCOM System – Block Diagram 3.2.2 System Overview – AVIATOR 700S The AVIATOR 700S System improves on the SB-S (refer to section 3.1.1) services provided by the AVIATOR 200S configuration with increased data capability for the EFB connection and 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.
PAGE 20
AVIATOR 200S/700S User Manual 3.2.3 Configuration The AVIATOR S 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 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 System for a specific aircraft configuration.
PAGE 21
AVIATOR 200S/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 MCDU before initiating the call 2. The default MCDU 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.3). 3.3.
PAGE 22
AVIATOR 200S/700S User Manual A Simple Network Management Protocol (SNMP) interface provides the capability for retrieving AVIATOR S system and operational status information as well as link status and history (refer to Appendix A). 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).
PAGE 23
AVIATOR 200S/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.
PAGE 24
AVIATOR 200S/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) Label information on the SCM itself (see Figure 4-1) SATCOM->MCDU Screens reflecting the IMSI information8 Figure 4-1: AVIATOR S SCM | IMSI & Smart Card Identification 4.
PAGE 25
AVIATOR 200S/700S User Manual 5 INTERPRETING THE SYSTEM STATUS This User Manual provides operational descriptions to allow flight crew to manage the AVIATOR S system. Depending on the aircraft type, one of the following control & display units may be installed:   5.1 Multi-purpose Control and Display Unit (MCDU) o Refer to section 5.1 for the MCDU pages menu tree. Radio Management Panel (RMP) o Refer to section 5.2 for the RMP pages menu tree.
PAGE 26
AVIATOR 200S/700S User Manual 5.3 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: Select the “SATCOM MAIN MENU” page. “SAT 1” is for the first voice channel, and “SAT 2” for the second voice channel. RMP: 5.3.1 Select the “TEL” page. “TEL1” is for the first voice channel, and “TEL2” for the second voice channel.
PAGE 27
AVIATOR 200S/700S User Manual 5.3.2 Safety Voice Services - Ready to Connect When the AVIATOR S system has successfully acquired and registered on the INMARSAT network: MCDU: SAT 1 and SAT 2 status will indicate “READY TO CONNECT” (See Figure 5-7). RMP: TEL1 and TEL2 status will indicate that dialling is permitted (See Figure 5-8). The AVIATOR S system is now able to make or receive voice calls. Figure 5-7: MCDU - SATCOM Main Menu - Safety Voice Availability - Ready to Connect 5.3.
PAGE 28
AVIATOR 200S/700S User Manual 5.4 SATCOM CONFIG The SATCOM CONFIG page provides further system information and functions: MCDU: SATCOM MAIN MENUSATCOM CONFIG page by pressing LSK-L6. RMP: 5.4.1 MENUSATCOM CONFIG page by pressing LSK-R3. Logging On Auto/Logged On Auto/Logged Off The status of the connection to the INMARSAT satellite is shown at LSK-L1. The system will perform an automatic (AUTO) log on after initial power on.
PAGE 29
AVIATOR 200S/700S User Manual Figure 5-14: RMP - SATCOM Config - Status Logging On Figure 5-15: RMP - SATCOM Config - Status Logged On Auto Figure 5-16: RMP - SATCOM Config - Status - Logged Off COBHAM PRIVATE Document: 98-158752 Revision: B Page: Level: COM 29 of 105 CC: 1 (T: 99-161853-F)
PAGE 30
AVIATOR 200S/700S User Manual 5.4.2 SATCOM INOP When the AVIATOR S system has an error and unable to provide service, the voice channel status will indicate that calls are not possible (refer to section 5.3.1). By accessing the SATCOM CONFIG page, the system will indicate if it is attempting to log on or has declared a fault condition with the status “SATCOM INOP” 9 (See Figure 5-17).
PAGE 31
AVIATOR 200S/700S User Manual 5.5.1 IMSI Config The IMSI CONFIG page11 (accessed by pressing LSK-R6) provides the IMSI information for activation or troubleshooting purposes (See Figure 5-20 and Figure 5-21). Figure 5-20: AVIATOR 200S - IMSI Config 11 Figure 5-21: AVIATOR 700S - IMSI Config This page is not available in aircraft fitted with Radio Management Panels (RMP).
PAGE 32
AVIATOR 200S/700S User Manual 6 SATELLITE SELECTION 6.1.1 Log Off & Auto/Manual Log On The INMARSAT satellite used by the AVIATOR S system can be automatically or manually selected through the SATCOM SETTINGS page. Typical system configuration will be 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.
PAGE 33
6.1.2 Ocean Region Change (ORC) An ocean region change (ORC) occurs when the AVIATOR S 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 (Cockpit and Cabin) are disconnected for the duration of time the AVIATOR S system requires to complete the ORC.
PAGE 34
AVIATOR 200S/700S User Manual 7 SAFETY VOICE SERVICES The AVIATOR S 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 Multipurpose Control and Display Unit (MCDU). Refer to section 7.1. 2) Audio and call management functions performed via the Radio Management Panel (RMP). Refer to section 7.2. 7.1 7.1.
PAGE 35
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 SATCOM MAIN MENU, press LSK-R6 to enter the SATCOM DIRECTORY page. 2. Press the LSK matching the group name to be displayed. a. For example, press LSK-L3 to access the NON-SAFETY group. 3. Browse the directory using the “page up” and “page down” buttons to display the various pages of the directory. a.
PAGE 36
AVIATOR 200S/700S User Manual 7.1.1.3 Initiating an Outgoing Call Once the outgoing calling information has been pre-selected as described in sections 7.1.1.1 or 7.1.1.2 the call can be initiated by: 1. Press the associated audio channel (SAT 1/2) call button on the ACP. Once the call has been initiated, the SATCOM MAIN MENU will display the call progress:  CONNECTING (Figure 7-7) - The number has been dialled and a connection to the called party is being attempted.
PAGE 37
AVIATOR 200S/700S User Manual In some instances, the call may not be connected and the SATCOM MAIN MENU will display CALL FAILED and a cause on the line below:  CALL FAILED (Figure 7-9) - INVAL NUMBER | Number entered is invalid. - NO SERVICE | Number entered could not be reached. - GRND FAILURE | An error occurred in the ground network. - GRND CONGEST | Calling party could not be reached due to user busy/congestion.
PAGE 38
AVIATOR 200S/700S User Manual 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). In both cases, the airborne side (the crew) must: 1. Release the call by pressing the associated audio channel (SAT 1/2) call button on the ACP, else the channel will remain active/engaged and may prevent incoming calls from alerting the crew.
PAGE 39
AVIATOR 200S/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 chime14 2. Visually - Call information displayed on the SATCOM->MCDU page (Figure 7-14). - The audio channel (SAT 1/2) call button on the ACP flashes amber (Figure 7-15).
PAGE 40
AVIATOR 200S/700S User Manual 7.1.2.3 Answering an Incoming Call To answer the incoming call: 1. Press the associated audio channel (SAT 1/2) on ACP. - The ACP SAT call button will stop flashing amber and show steady green state indicating the SAT channel is active and connected (Figure 7-16). - Voice communication between the two parties is now possible using the ACP to control the audio path and volume functions. - The SATCOM MAIN MENU SAT 1/2 status will show “CONNECTED” (Figure 7-17).
PAGE 41
AVIATOR 200S/700S User Manual 7.1.2.4 Ending an Incoming Call Calls may be ended (terminated) by either the calling party (ground side) or the called party (airborne side). In both cases, the airborne side (the crew) must: 1. Release the call by pressing the associated audio channel (SAT 1/2) call button on the ACP, else the channel will remain active/engaged and may prevent incoming calls from alerting the crew.
PAGE 42
AVIATOR 200S/700S User Manual 7.1.2.5 Pre-emption When pre-emption occurs (see section 3.3.3), an active call will be disconnected and the SATCOM MAIN MENU SAT 1/2 status will show “CALL FAILED” with the reason “PRE-EMPTED” on the line below (Figure 7-22). To answer a pre-emption incoming call: 1. Press the associated audio channel (SAT 1/2) on the ACP. - The ACP SAT call button will stop flashing amber and show steady green state indicating the SAT channel is active and connected.
PAGE 43
AVIATOR 200S/700S User Manual 7.2 7.2.1 RMP INTERFACE 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 Dial - a phone number16 or short code may be entered via the RMP, or Directory Dial - select the identity from the directory list defined by User ORT (see section 3.2.3 for ORT Configuration). 7.2.1.1 Manual Dial 1. The SATCOM telephone page is accessible by pressing the TEL page button. 2.
PAGE 44
AVIATOR 200S/700S User Manual 7.2.1.2 Directory Dial NOTE: The directory entries are User ORT configurable and may differ from the examples. 1. From the TEL page, select the desired audio channel by pressing the TEL1/TEL2 button. Press the “down” button to enter the directory pages with entries sorted in alphabetical order. 2.
PAGE 45
AVIATOR 200S/700S User Manual 7.2.1.3 Initiating an Outgoing Call Once the outgoing calling information has been pre-selected as described in sections 7.2.1.1 or 7.2.1.2 the call can be initiated by: 1. Press the Dial button (LSK-L1/2) of the associated audio channel (TELx) on the radio management panel (RMP), Figure 7-26.
PAGE 46
AVIATOR 200S/700S User Manual Figure 7-29: RMP - TEL Page - Outgoing Call - Call Failed COBHAM PRIVATE Document: 98-158752 Revision: B Page: Level: COM 46 of 105 CC: 1 (T: 99-161853-F)
PAGE 47
AVIATOR 200S/700S User Manual 7.2.1.4 Ending an Outgoing Call Calls may be ended (terminated) by either the calling party (airborne side) or the called party (ground side). For an airborne side release (initiated by the crew): 1. Press the End button (LSK-L1/2) of the associated audio channel (TELx) on the radio management panel (RMP) - Call ended side tone may be heard by the crew. - The TELx status will display “CALL ENDED” once the channel has been released (Figure 7-31).
PAGE 48
AVIATOR 200S/700S User Manual 7.2.2 Incoming Calls – Ground-to-Air (G2A) 7.2.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 chime17 2. Visually - Call information displayed on the RMP TEL page (Figure 7-32). - The TELx call button on the Radio Management Panel (RMP) flashes amber (Figure 7-32).
PAGE 49
AVIATOR 200S/700S User Manual 7.2.2.3 Answering an Incoming Call To answer the incoming call: 1. Press the associated audio channel (TELx) on the RMP. - Voice communication between the two parties is now possible using the RMP to control the audio path and volume functions. - The TELx status will show “CONNECTED” (Figure 7-33). Figure 7-33: RMP - TEL Page - Incoming Call - Connected 7.2.2.
PAGE 50
AVIATOR 200S/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 MCDU SATCOM pages18 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 SETTINGS page at position LSK-L4: a. BURUM, or b. PAUMALU. NOTE: The GES ID number (e.g.
PAGE 51
AVIATOR 200S/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.3), this Ethernet interface provides segregated data capability to the cockpit for EFB applications.
PAGE 52
AVIATOR 200S/700S User Manual Figure 9-1: MCDU - SATCOM Config - Cabin calls enabled Figure 9-2: MCDU - SATCOM Config - Cabin calls disabled Figure 9-3: RMP - SATCOM Config - Cabin calls enabled Figure 9-4: RMP - SATCOM Config - Cabin calls 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).
PAGE 53
AVIATOR 200S/700S User Manual 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 SATCOM system. A maximum of 11 PDP contexts is supported, comprising of both primary and secondary contexts. 9.2.2 Connection Authentication User Authentication may be required for some connections.
PAGE 54
AVIATOR 200S/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 Places a Primary Streaming class PDP Context at the data rate of 8 kbps. 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 HDR Half symmetric N/A No SBB Option Name defined.
PAGE 55
AVIATOR 200S/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.3). 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.
PAGE 56
AVIATOR 200S/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.
PAGE 57
AVIATOR 200S/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.
PAGE 58
AVIATOR 200S/700S User Manual 10 TROUBLESHOOTING 10.1 LOG FILE EXTRACTION For AVIATOR S log file extraction, refer to Appendix E. 10.2 SYSTEM TEST - FLASHING CALL LIGHTS While performing a 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: MCDU: Clear the ACP call lights by pressing the SAT 1 and SAT 2 call buttons. RMP: No further action required.
PAGE 59
AVIATOR 200S/700S User Manual Appendix A. AISD SNMP Interface Table 10-1: AISD SNMP MIB OID Support Level 1 Level 2 Level 3 Level 4 .aslInfos(2) Description The number of data services types available. Integer = 1 .asLinks(2) .aslServices(1) .aslsNumbers(1) .aslsTable(2) Level 5 .aslsIndex(1) Index number to each service. Integer = 1 .aslsName(2) Name for each index. Index 1 = "SBB:BACKGROUND" .aslsInUse(3) Number of instances of this service currently in use. Integer [0..1] .
PAGE 60
AVIATOR 200S/700S User Manual 6 (EMEA) 5 (APAC) 7 (AMER) Integer [0..63] .asliActLinkEntryNumbers(4) Indicates the number of the entries in the first table and has a range from 0 to 50. Integer [0..50] .asliActLinkTable(5) .asliActLinkIndex(1) 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] .
PAGE 61
AVIATOR 200S/700S User Manual .asliHistLinkEntryNumbers(6) COBHAM PRIVATE Document: 98-158752 Revision: B .asliActLinkConnectionID(8) Variable string used when creating the PPPoE session. String [0..128] .asliActLinkNegotiatedBW(9) Integer = 0 (Best effort connection) .asliActLinkIpAddress(10) This object contains the IP-Address of the current link. E.g. aaa.bbb.ccc.ddd. .asliActLinkTxTrafficVol(11) This object contains the information about the total transmitted bytes over this link in kBytes .
PAGE 62
AVIATOR 200S/700S User Manual .asliHistLinkTable(7) COBHAM PRIVATE Document: 98-158752 Revision: B .asliHistLinkIndex(1) 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] .asliHistLinkReleaseType(2) This object shows the release type of the link as numeric codes as described in [A781] Attachment 5, Section 6. Integer [1..32767] .
PAGE 63
AVIATOR 200S/700S User Manual .asUnits(4) .asuSDU(2) .asuSduInfo(1) .asliHistLinkRxTrafficVol(12) This object contains the information about the total received bytes over this link in kBytes .asliHistLinkBeamID(13) This object shows, which beam ID is connected by the link. Integer [0..255] .asliHistLinkSigQual(14) This object shows the Quality in dBHz*10 of the link. Integer [0..32767] .asliHistLinkMaxSigQual(15) Expected maximum values for Link Signal Quality in dBHz*10.
PAGE 64
AVIATOR 200S/700S User Manual String [0..255] .asuSduInfoCC1Status(15) Cockpit Channel Card overall status: 1 ~ Passed 2 ~ Failed 3 ~ Absent (initial value) .asuSduInfoCC2Status(16) Cabin Channel Card overall status: Integer [3] (Absent) .asuSduInfoUTCDateTime(35) Current UTC date and time in RFC3339 format. .asuAntenna(8) .asuAntInfo(1) .asuAntInfoTable(2) COBHAM PRIVATE Document: 98-158752 Revision: B Indicates the number of entries in the table. Integer [1] .asuAntInfoTableNumbers(1) .
PAGE 65
AVIATOR 200S/700S User Manual Appendix B. PIESD SNMP Interface Table 10-2: PIESD SNMP MIB OID Support Level 1 Level 2 .asLinks(2) .aslServices(1) Level 3 Level 5 Description The number of data services types available. Integer [7] .aslsNumbers(1) .aslsTable(2) .aslInfos(2) Level 4 .aslsIndex(1) Index number to each service. Integer [1..7] .aslsName(2) Name for each index.
PAGE 66
AVIATOR 200S/700S User Manual .asliSatIDNum(3) Unique numeric identifier for the connected satellite: 3 (MEAS) 6 (EMEA) 5 (APAC) 7 (AMER) Integer [0..63] .asliActLinkEntryNumbers(4) Indicates the number of the entries in the first table and has a range from 0 to 50. Integer [0..50] .asliActLinkTable(5) .asliActLinkIndex(1) This object is a unique identifier for the current link entry and can be considered a handle for the session.
PAGE 67
AVIATOR 200S/700S User Manual The association between a ContextID and the ActualContextID remains for the duration of the primary PDP. Integer [0..255] COBHAM PRIVATE Document: 98-158752 Revision: B .asliActLinkConnectionID(8) Variable string used when creating the PPPoE session. String [0..128] .asliActLinkNegotiatedBW(9) This object shows the currently negotiated bandwidth of the link in this table entry. Integer [0..2048] 0 ~ Background Class / Best effort connection .
PAGE 68
AVIATOR 200S/700S User Manual .asliActLinkServiceIndex(17) This object is a link to the aslsIndex by referring the used Service. Integer [0..100] .asliActLinkStartTime(20) UTC Time at which the link was brought up. AS_Datetime [RFC3339] .asliActLinkEndTime(21) UTC Time at which the link was brought down. AS_Datetime [RFC3339] .asliActLinkPPPoEID(22) PPPoE Session ID which started the call. Integer [0..32767] .
PAGE 69
AVIATOR 200S/700S User Manual Integer [0..255] COBHAM PRIVATE Document: 98-158752 Revision: B .asliHistLinkActualContextID(7) 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] .asliHistLinkConnectionID(8) Variable string used when creating the PPPoE session. String [0..128] .
PAGE 70
AVIATOR 200S/700S User Manual .asUnits(4) .asuSDU(2) .asuSduInfo(1) .asliHistLinkMainIndex(16) 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] .asliHistLinkServiceIndex(17) This object is a link to the aslsIndex by referring the used Service. Integer [0..100] .asliHistLinkStartTime(20) UTC Time at which the link was brought up. AS_Datetime [RFC3339] .
PAGE 71
AVIATOR 200S/700S User Manual .asuAntenna(8) .asuAntInfo(1) .asuSduInfoUTCDateTime(35) Current UTC date and time in RFC3339 format. Indicates the number of entries in the table. Integer [1] .asuAntInfoTableNumbers(1) .asuAntInfoTable(2) COBHAM PRIVATE Document: 98-158752 Revision: B .asuSduInfoCC2Status(16) Cabin Channel Card overall status: 1 ~ Passed 2 ~ Failed 3 ~ Absent (initial value) .asuAntInfoIndex(1) This object describes the unique identifier for the current antenna. Integer [1] .
PAGE 72
AVIATOR 200S/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.
PAGE 73
AVIATOR 200S/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 bi
PAGE 74
AVIATOR 200S/700S User Manual Appendix D. AT-Commands Appendix D.1.1 List all Available AT Commands List all available AT commands. Ref : [3GPP_TS27] Command Possible response(s) +CLAC [ [...]] +CME ERROR: +CLAC=? Defined Values: : Defines the AT command including the prefix AT. Text shall not contain the sequence 0 or OK Appendix D.1.2 Command Echo Command Echo. Ref : [ITU-T_V.
PAGE 75
AVIATOR 200S/700S User Manual Appendix D.2.1 Request Manufacturer Identification Request Manufacturer Identification. Ref : [3GPP_TS27] Command Possible response(s) +CGMI +CME ERROR: +CGMI=? Defined Values: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. Text shall not contain the sequence 0 or OK Appendix D.2.2 Request Model Identification Request Model Identification.
PAGE 76
AVIATOR 200S/700S User Manual Appendix D.2.3 Request Revision Identification Request Revision Identification. Ref : [3GPP_TS27] Command Possible response(s) +CGMR +CME ERROR: +CGMR=? Defined Values: The total number of characters, including line terminators, in the information text shall not exceed 2048 characters. Text shall not contain the sequence 0 or OK. Appendix D.2.4 Request Serial Number Identification Request Product Serial Number Identification.
PAGE 77
AVIATOR 200S/700S User Manual Appendix D.3.1 Define Primary PDP Context Define PDP Context.
PAGE 78
AVIATOR 200S/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. a numeric parameter that controls PDP data compression 0 off (default if value is omitted) 1 on Other values are reserved.
PAGE 79
AVIATOR 200S/700S User Manual Supported Values: (1-11) 0 off (default if value is omitted) "IP" Appendix D.3.2 0 off (default if value is omitted) 1 on 3G Quality of Service Profile (Requested) 3G Quality of Service Profile (Requested).
PAGE 80
AVIATOR 200S/700S User Manual Defined Values: 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 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.
PAGE 81
AVIATOR 200S/700S User Manual 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. 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.
PAGE 82
AVIATOR 200S/700S User Manual 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. 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.
PAGE 83
AVIATOR 200S/700S User Manual Appendix D.3.3 2G Quality of Service Profile (Requested) 2G Quality of Service Profile (Requested).
PAGE 84
AVIATOR 200S/700S User Manual Defined Values: 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 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.
PAGE 85
AVIATOR 200S/700S User Manual 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. 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.
PAGE 86
AVIATOR 200S/700S User Manual 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. 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.
PAGE 87
AVIATOR 200S/700S User Manual Appendix D.3.
PAGE 88
AVIATOR 200S/700S User Manual 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, …). 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).
PAGE 89
AVIATOR 200S/700S User Manual 0 - no 1 - yes 2 - no detect Other values are reserved. 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. 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.
PAGE 90
AVIATOR 200S/700S User Manual Appendix D.3.5 3G Quality of Service Profile (Minimum Acceptable) 3G Quality of Service Profile (Minimum acceptable).
PAGE 91
AVIATOR 200S/700S User Manual 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. 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, …).
PAGE 92
AVIATOR 200S/700S User Manual a numeric parameter (1,2,3,…) that indicates the maximum allowed SDU size in octets. 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",…).
PAGE 93
AVIATOR 200S/700S User Manual Supported Values: (1-11) (0-3) (1-8640) (1-8640) (1-8640) (1-8640) (0,1) COBHAM PRIVATE Document: 98-158752 Revision: B (1-1520) ("1E6"-"1E1").
PAGE 94
AVIATOR 200S/700S User Manual Appendix D.3.6 PDP Context Activation PDP context activate or deactivate. Ref : [3GPP_TS27] Command Possible response(s) +CGACT=[ [,[, [,.]]]] OK ERROR +CGACT: , [+CGACT: ,[...]] +CGACT: (list of supported s) +CGACT? +CGACT=? Defined Values: 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.
PAGE 95
AVIATOR 200S/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 . is omitted if none is available. Supported Values (1-11) (0.0.0.0-255.255.255.255) Appendix D.3.
PAGE 96
AVIATOR 200S/700S User Manual (Packet Data Protocol type) a string parameter which specifies the type of packet data protocol IP Internet Protocol (IETF STD 5) IPV621 Internet Protocol, version 6 (IETF RFC 2460) PPP Point to Point Protocol (IETF STD 51) 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.
PAGE 97
AVIATOR 200S/700S User Manual Appendix D.3.9 Define Traffic Flow Template Define Traffic Flow Template. Ref : [3GPP_TS27] NOTE: source and destination fields are from the networks perspective.
PAGE 98
AVIATOR 200S/700S User Manual Defined Values: : a numeric parameter which specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). : Numeric parameter, value range from 1 to 8. : 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 IPv6 22.
PAGE 99
AVIATOR 200S/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 Appendix D.3.10 Modify PDP Context PDP Context Modify.
PAGE 100
AVIATOR 200S/700S User Manual Appendix D.3.11 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.
PAGE 101
AVIATOR 200S/700S User Manual Appendix E. Log File Extraction This section describes how to collect System, Security logs and Diagnostic reports from the AVIATOR S CSDU. The system and security logs are collected in system and security log files that are captured per concluded flight leg; one per Air and Ground segment. A snapshot of the troubleshooting data is captured per System Emergency Event in a diagnostic report. 1.
PAGE 102
AVIATOR 200S/700S User Manual Log files are extracted from each of the two (AVIATOR 200S) or three (AVIATOR 700S) domain processors (ACD, AISD, PIESD) located in the CSDU. 6. When the PC is connected to the CSDU USB port, four new serial ports will appear. 7. Connect an instance of the terminal program to each of the serial ports using 115.200 baud, 8 databits, 1 stopbit, no parity. 8. Press enter to display a command prompt.
PAGE 103
AVIATOR 200S/700S User Manual Appendix E.2.1 Find system log entries on the LRU unit Use "system -d 6" command to displays the last 6 system log files. Figure 10-2: Find System log entries on the LRU unit - Maintenance phase Appendix E.2.2 Select file and export Select a file (highlight the file name) and use the command "system –x " and add filename (paste in). (with TeraTerm configured to auto receive and save into default directory).
PAGE 104
AVIATOR 200S/700S User Manual The same commands are used for system log, security log and diagnostic log/report. Appendix E.3.1 List of commands available Figure 10-5: List of commands available - Maintenance phase System log and Maintenance phase have the same command set. Appendix E.3.2 Make new log file Use the command "system -n filename" to save the current log in filename and start new logfile. If file name is not provided in the entered command (e.
PAGE 105
AVIATOR 200S/700S User Manual Appendix E.3.3 Add a text line in current log Use command "system -l text" to add a comment in the current logfile. Figure 10-7: Add a text line in current log - Maintenance phase The result is a new line in the log without log level <-> and with process ACD13, see example below: <->1 1970-01-01T00:07:30.814Z - ACD 13 - - (55.793896,12.523556,39.014400) Screendump_test <4>1 1970-01-01T00:07:30.814Z CSDU ACD 13 1003 - (55.793896,12.523556,39.