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 F-10
3 JUN 10
D. Understanding the Solo Word
If the data the HSD-440 Mark 2 Terminal is sending consists of only 1 or 2 octets, then
the data can be sent blind using the solo word instead of obtaining a CTS. Solo words
conform to the following rules:
• The solo word contains a 16 bit data field in bits 24–9
• Bits 31–29 are permanently set to 101b
• Solo words are not acknowledged at the link level
• Solo words are not interleaved with data file words during a data file transfer, however
if the HSD-440 Mark 2 Terminal receives a solo word during data transfer, the
HSD-440 Mark 2 Terminal shall process the solo word normally and resume file
transmission or reception.
The solo word also performs test and loop back functions to test the integrity of the ARINC
429 bus interconnection between the HSD-440 Mark 2 Terminal and the CMU.
The HSD-440 Mark 2 Terminal can send a 16 bit loop test pattern word (TEST) on the
ARINC 429 TX bus. The CMU then responds with the identical loop test pattern word
(LOOP) on the ARINC 429 RX bus. If the LOOP does not match the TEST, the HSD-440
Mark 2 Terminal indicates a TEST failure.
If the HSD-440 Mark 2 Terminal receives a TEST on its ARINC 429 RX bus, it responds
by transmitting an identical LOOP on the ARINC 429 TX bus.
A 4 bit identifier (bits 28–25) identifies the nature of the data being sent by the solo word.
The three types of data are shown in
Table F-10.
SYN The HSD-440 Mark 2 Terminal transmits a SYN word to inform the CMU
that the construction of the last file that was transmitted is confused. The
reception of a SYN word causes the CMU to abort any reception or
transmission in progress. In addition, if the CMU was transmitting, it
should re-initiate transmission of the file that was aborted.
Destination code RTS, CTS, and NTCS words use a destination code. The destination
code field (when used, bits 24–17) indicates the final destination of the
LDU. If the LDU will be used in the HSD-440 Mark 2 Terminal, the
destination code can be set to 00h. If the LDU is intended to be passed
on to another onboard system, the destination code indicates that
system.
Word count RTS and CTS words use a word count. The word count field (bits 16–9)
reflects the number of ARINC 429 words that will be transmitted in a
subsequent LDU. The maximum word count value is 255 ARINC 429
words.
Table F-9 Protocol Words and Uses (Continued)
Protocol word Uses
Table F-10 Data Types
Purpose Bits 28-25b Description
Test 0000b 16 Bit Test Pattern