User's Manual
Table Of Contents
- Customer Response Form
- Record of Revisions
- Service Bulletin List
- List of Effective Pages
- Introduction
- System Description
- 1. Inmarsat System Overview
- 2. Equipment Overview
- 3. Equipment Specifications
- 4. System Interfaces
- 5. User Interfaces
- 6. Software Description
- System Operation
- 1. Registering and Activating Terminals
- 2. Configuring Terminals
- A. Setting up Airborne Networks
- B. Mapping User Devices for ISDN Services
- C. IMNs
- D. MSNs
- E. Configuring User ORT Parameters with the Maintenance Port Utility (MPU)
- F. Configuring Secure ORT Parameters with the Maintenance Port Utility (MPU)
- G. Creating ORTs with the Maintenance Port Utility (MPU)
- H. Understanding CMU Messages
- I. Configuring Swift 64 LES Access Codes
- J. Removing the LED Label
- K. Activating Configurations
- L. Verifying Configurations
- 3. Using Terminals
- Installation
- 1. Advisories
- 2. Pre-Installation Inspection
- 3. Mechanical Installation
- 4. Electrical Installation
- A. Cabling and Connector Requirements
- B. Installation Wiring Notes
- (1) Source/Destination Identification
- (2) Maintenance Port Interface
- (3) Antenna Subsystem RF Interface
- (4) WOW Pins
- (5) ICAO IDs
- (6) Remote Status Panel (Optional)
- (7) System Configuration Strapping
- (8) System Mode Strap Pins Coding
- (9) Call Light Activation Strapping
- (10) Hookswitch Strapping
- (11) Priority 4 Call Strapping
- (12) Cockpit Voice Strapping
- (13) User Interfaces
- (14) System Interfaces
- C. Connection Details
- 5. Passive Intermodulation (PIM) Test
- 6. Installation and Engineering Diagrams
- 7. Connection Details
- Test and Fault Isolation
- Maintenance and Repair
- Configuring the Owners Requirements Table (ORT)
- 1. Configuring ORT Parameters Using the MPU
- A. Connecting to the MPU
- B. Configuring the ORT Part Number
- C. Configuring Cockpit Communication Parameters
- D. Configuring 4-wire Parameters
- E. Configuring POTS Parameters
- F. Configuring CEPT-E1 Parameters
- G. Configuring High Speed Data Services
- H. Configuring Ethernet Parameters
- I. Configuring Networking Parameters For Ethernet 1 and Ethernet 2
- (1) Configuring the Host Name
- (2) Configuring the Access Concentrator Name
- (3) Configuring the SNMP Server
- (4) Configuring the SNMP Community String
- (5) Configuring the TFTP Server
- (6) Configuring the DHCP Client
- (7) Configuring the DHCP Server
- (8) Configuring Telnet Access
- (9) Configuring the Managed Range
- (10) Configuring the Number of Managed Addresses
- (11) Configuring the Access Point Name
- J. Configuring Avionics Parameters
- K. Configuring Satellite Service ORT Parameters
- (1) Configuring the Forward ID
- (2) Configuring Satellite Information
- (3) Configuring GES Service Provider Information
- (4) Configuring the Frequency Table
- (5) Configuring LES Service Provider Information
- (6) Configuring the SwiftBroadband Timing Mode
- (7) Configuring the Priority Service for Channel Card One
- (8) Configuring the Service Type Priority
- L. Configuring Antenna ORT Parameters
- M. Configuring MCDU ORT Parameters
- (1) Configuring MCDU Wiring
- (2) Configuring the MCDU Input Speed
- (3) Configuring the MCDU Output Speed
- (4) Configuring the MCDU Controller Type
- (5) Configuring the MCDU Type
- (6) Configuring the MCDU Font Colour
- (7) Configuring Manual Dialing
- (8) Configuring Outgoing Call Pre-Selection
- (9) Configuring the Address Book Categories
- N. Configuring the CMU
- O. Configuring Terminal Operation
- (1) Configuring Air/Ground Status Restrictions
- (2) Configuring Transmit on Ground
- (3) Configuring Self-test in Air
- (4) Configuring Maintenance Command Execution in Air
- (5) Configuring MCDU PAST
- (6) Configuring Field Loadable Software
- (7) Configuring the Logon/Handover Policy
- (8) Configuring Logon Interrogation
- (9) Configuring High-rate R/T in Global Beam
- (10) Masking Position in Logs
- (11) Configuring HSD SAL
- P. Configuring Passive Intermodulation (PIM) Parameters
- (1) Configuring PIMBIT HGA Azimuth Offset Angle
- (2) Configuring PIMBIT IGA Azimuth Offset Angle
- (3) Configuring PIMBIT IGA Elevation Offset Angle1
- (4) Configuring PIMBIT IGA Elevation Offset Angle2
- (5) Configuring PIMBIT HGA Elevation Offset Angle1
- (6) Configuring PIMBIT HGA Elevation Offset Angle2
- (7) Configuring PIMBIT Measurement Discard Ratio
- (8) Configuring PIMBIT Failure Threshold
- (9) Configuring PIMBIT Pointing Failure Threshold
- 2. Configuring ORT Parameters Using the EMS ORT Application
- 1. Configuring ORT Parameters Using the MPU
- Appendix A: Inmarsat Satellite Beam Coverage
- Appendix B: Troubleshooting Checklist
- 1. Have you registered with a service provider to activate service?
- 2. Has your account been activated?
- 3. Is the HSD-440 Mark 2 Terminal seated properly?
- 4. Is all cabling attached correctly and securely?
- 5. Have any changes to the system been made?
- 6. Are your Primary and Secondary LES/GES Access Codes programmed for all ORs?
- 7. Was the operational mode of the system strapped or configured correctly?
- 8. Are the SIM cards activated?
- 9. Is the APN set?
- 10. Are GES preferences correctly set?
- Appendix C: RJ45 Cable Termination Details
- Appendix D: Installation Planning Checklist
- Appendix E: Installation Checklist
- Appendix F: CMU Messages
- Appendix G: International Access and Country Codes
- Appendix H: Inmarsat Cause Codes
SYSTEM DESCRIPTION, INSTALLATION, AND MAINTENANCE MANUAL
eNfusion® HSD-440 Mark 2 Terminal
23-15-30 1-11
3 JUN 10
For more information about using the CMC, refer to the CMC manufacturer’s
documentation.
B. Source Destination Identification (SDI)
The SDI is strapped to indicate the installation type.
C. FWD IDs, ICAO IDs, and IMSI
The HSD-440 Mark 2 Terminal uses two 24-bit IDs called Forward/Return Link Pairs
(FRLPs) for the Swift 64 service: a Forward ID (FWD ID) and a Return ID (RTN ID). The
HSD-440 Mark 2 Terminal reads the FWD ID from the EEPROM and performs a look-up
for the RTN ID. The terminal obtains the second FRLP from the table based on the first
FRLP. For security reasons, each assembly contains an encrypted look-up table with the
whole addressing space assigned to the product by Inmarsat. To minimize the risk of
unauthorized use of its contents, the table is not accessible to the user.
The ISN consists of the type approval number and the FWD ID address. Each FRLP is
associated with Inmarsat Mobile Numbers (IMNs), which are the numbers that a user
dials from the ground to reach a terminal on an aircraft. There is a unique IMN for each
of the service types (for example, data or voice).
The HSD-440 Mark 2 Terminal provides IMEI and IMSI for SBB. The IMEI identifies the
equipment type to the network . The equipment types identity is hard coded in the
equipment. The IMSI identifies the subscriber. This identity is contained within the USIM
housed in the SCM.
The HSD-440 Mark 2 Terminal provides two ways to define the ICAO ID—by strapping
or over the secondary IRS bus. You can select strapping or the IRS bus as the source
of the ICAO ID by the secure ORT parameter ICAO CODE SOURCE.
NOTE: If the ICAO address source is set to the IRS bus, the secondary IRS type ORT
parameter must be set to AES ID.
The 24-bit ICAO ID forms part of the Inmarsat Serial Number (ISN).
The HSD-440 Mark 2 Terminal uses the International Mobile Subscriber Identity (IMSI)
number for access to SBB services. The IMSI is stored in the terminal’s SIM card, and
is printed on the SCM. Register your IMSI with your service provider to begin using SBB
services.
D. Weight-On-Wheel (WOW) Pin Wiring
WOW discretes indicate when an aircraft is on the ground or in the air, and are used for
flight data-logging purposes. Since data that the aircraft is airborne is supplied to the
HSD-440 Mark 2 Terminal by other equipment, this information from the discretes is not
required. However, EMS Aviation recommends wiring the WOW discretes if you plan to
load software while the HSD-440 Mark 2 Terminal is installed in the aircraft.
WOW is only used to determine aircraft on-ground status if the Inertial Reference System
(IRS) has no valid data, and the CMC is not installed, or if the CMC is not providing valid
data.
Note 40 of the ARINC 741 specification documentation defines the requirement for WOW
data.