Fleetbb Training Manual

FleetBroadband Installation
Commissioning and On Board repair

Training manual
Cobham SATCOM
FleetBroadband Installation,
Commissioning and On Board repair
Training Manual
SAILOR 150 FleetBroadband

®

®

®
EXPLORER 727 BGAN

EXPLORER 325 BGAN
TT-100-MSO-030207
Document number:
2013-04-18
Release date:
i
Contents
FleetBroadband Installation, ...............................................................................iii
Commissioning and On Board repair..................................................................iii
1 Inmarsat Network
1.1 Overview............................................................................................... 1
1.2 Beam types........................................................................................... 3
1.2.1 Global Beam............................................................................................. 3
1.2.2 Regional Beams....................................................................................... 3
1.2.3 Narrow Beams.......................................................................................... 4
1.2.4 Beam Hierarchy........................................................................................ 4
1.2.5 Elevation bands........................................................................................ 5
1.3 BGAN-X units........................................................................................ 6
1.3.1 BGAN-X Terminal classes and capabilities............................................... 6
1.3.2 Subscription and Quality of Service (QoS)............................................... 7
1.4 RAN (Radio Access Network)............................................................... 8
1.5 Core Network...................................................................................... 10
1.5.1 HLR (Home Location Registry)............................................................... 10
1.5.2 MSC/VLR/MGW/SMSC/FRINs............................................................... 10
1.5.3 SGSN..................................................................................................... 11
1.5.4 GGSN..................................................................................................... 11
1.6 Distribution architecture...................................................................... 12
1.6.1 RNC Recourse Management Entities..................................................... 13
1.7 Bearers............................................................................................... 17
1.7.1 Forward direction Bearer types.............................................................. 18
1.7.2 Forward direction coding and multiplexing............................................. 19
1.7.3 Return direction Bearer types................................................................. 20
1.7.4 Return direction coding, multiplexing and synchronisation..................... 21
1.7.5 Forward direction layout......................................................................... 21
1.7.6 Return direction layout............................................................................ 23
1.7.7 Lease mode scenario............................................................................. 25
2 Product Presentation
2.1 SAILOR® 500 FleetBroadband............................................................ 29
2.1.1 System overview.................................................................................... 29
2.1.2 Above Deck Units (ADU)........................................................................ 31
2.1.3 Below Deck Units (BDU) /Terminal......................................................... 40
2.1.4 Thrane IP Handset.................................................................................. 41
2.2.1 System overview.................................................................................... 42
2.2.2 Above Deck Unit (ADU).......................................................................... 43
2.3.1 System overview.................................................................................... 50
2.3.2 Above Deck Unit (ADU).......................................................................... 51
2.4 AC/DC Power Supply.......................................................................... 58
2.5 Alarm Panel FleetBroadband.............................................................. 59
ii Content
3 Installation
3.1 Content of the package....................................................................... 63
3.2 Tools needed....................................................................................... 67
3.3 Installation precautions....................................................................... 68
3.3.1 Radiation hazard.................................................................................... 68
3.3.2 Antenna Cable........................................................................................ 68
3.3.3 Obstruction............................................................................................. 69
3.3.4 Interference............................................................................................ 69
3.4 Installation of the ADU........................................................................ 72
3.4.1 Antenna grounding................................................................................. 72
3.4.2 Important mounting notes....................................................................... 73
3.4.3 Mounting the antenna............................................................................. 74
3.5 Installation of the BDU /Terminal......................................................... 78
3.5.1 Where to install?..................................................................................... 78
3.5.2 How to install.......................................................................................... 78
3.5.3 Antenna cable grounding........................................................................ 80
3.5.4 BDU/Terminal grounding........................................................................ 81
3.5.5 BDU /Terminal power connection........................................................... 82
3.6 Installation of the AC/DC Power Supply.............................................. 84
3.7 Installation of the Thrane IP Handset.................................................. 87
3.8 Installation of the Alarm Panel FleetBroadband ................................. 89
3.8.1 Connectors............................................................................................... 89
3.8.2 LAN (PoE) interface................................................................................. 89
3.8.3 DC Power input (optional)........................................................................ 90
3.8.4 Cable requirements.................................................................................. 91
3.8.5 Connecting the Alarm Panel..................................................................... 91
3.8.6 Verifying the installation............................................................................ 92
3.9 To install the Alarm Panel..................................................................... 93
3.9.1 General installation requirements............................................................. 93
3.9.2 Mounting the Alarm Panel........................................................................ 93
4 Interfaces
4.1 Antenna Connector........................................................................... 101
4.2 L-band output.................................................................................... 101
4.3 Phone/Fax interface.......................................................................... 102
4.3.1 Configuring the Phone/Fax interface.................................................... 103
4.4 SIM-Card reader............................................................................... 104
4.5 ISDN interface................................................................................... 105
4.5.1 Configure the ISDN interface................................................................ 106
4.6 LAN Interface, VOIP.......................................................................... 107
4.6.1 Local exchange.................................................................................... 110
4.6.2 Supplementary services........................................................................111
4.7 LAN interface, Data........................................................................... 113
4.7.1 Connecting a computer to the LAN interface........................................ 113
4.7.2 The Network Management system....................................................... 114
4.8 DC Input............................................................................................ 119
4.9 I/O ports............................................................................................ 119
4.10 Grounding......................................................................................... 121
5 Troubleshooting
5.1 Status signalling .............................................................................. 125
5.2 Status signalling .............................................................................. 127
iii
5.3 Dash Board ...................................................................................... 127

5.4 Help desk.......................................................................................... 129
5.4.1 Event List.............................................................................................. 129
5.4.2 Event Log............................................................................................. 129
5.4.3 Extended status.................................................................................... 130
5.5 Maintenance page.............................................................................. 132
5.6 Diagnostic report: ’Report in a file’.................................................... 134
5.7 DEBUG SHELL: ’Online reporting’................................................... 135
5.8 Error log............................................................................................ 136
5.9 Call Log............................................................................................. 149
5.10 Error result code .............................................................................. 152
5.11 Troubleshooting................................................................................ 153
5.12 Troubleshooting Antenna Failure...................................................... 170
6 Removal & Replacement

6.1 R&R of SAILOR® 500 FleetBroadband............................................. 179
6.1.2 R&R of BDU /Terminal Power Supply Module...................................... 179
6.2 TT-3740A SAILOR® 500 FleetBroadband ADU................................. 180
6.2.1 R&R of Radome Top............................................................................. 181
6.2.2 R&R of Antenna Tracking Board /Low Noise Amplifier Module............ 182
6.2.3 R&R of Cross-Elevation Motor............................................................. 182
6.2.4 R&R of GPS Module (Global Position System Module)....................... 184
6.2.5 R&R of Elevation Motor........................................................................ 184
6.2.6 R&R of HPA Module (High Power Amplifier)......................................... 186
6.2.7 R&R of Azimuth Stepmotor................................................................... 187
6.3 TT-3740B and TT-3740C SAILOR® 500 FleetBroadband ADU......... 189
6.3.1 R&R of Radome Top (for ADU ver. B)................................................... 189
6.3.2 R&R of Radome Top (for ADU ver. C).................................................. 190
6.3.2 R&R of Antenna Tracking Receiver Module (ATR)............................... 191
6.3.3 R&R of Antenna Tracking Module (ATM).............................................. 192
6.3.4 R&R of GPS Module (Global Position System).................................... 193
6.3.5 R&R of HPA Module (High Power Amplifier)......................................... 194
6.4.1 R&R of BDU /Terminal Power Supply Module...................................... 195
6.4.2 TT-3742A SAILOR 250 FleetBroadband ADU..................................... 196
®

6.5.1 TT-3744A SAILOR 150 FleetBroadband ADU..................................... 201
®
7 Software Upload
7.1 Uploading software from your computer........................................... 212
7.2 Downloading software from the WEB MMI....................................... 212
7.3 Forced Software upload Broadband 500 / 250 / 150 / E727 / E325 Terminals... 213
7.4 Forced Software upload Via USB for BGAN / E700 / E500 Terminal............215
8 System Test
9 Abbreviation
10 R&R of EXP. 727 Antenna
10.1 R&R of EXPLORER 727................................................................... 235
10.1.1 S-403053B-THR EXPLORER 727 Antenna Complete......................... 235
11.1 R&R of EXPLORER 325................................................................... 248
11.2 Remove & replacement of Radome Top........................................... 249
11.3 Remove & replacement of Elevation motor...................................... 250
11.4 Remove & replacement of GPS Module (Global Position System Module).251
11.5 Remove & replacement of Azimuth Motor........................................ 252
11.6 Remove & replacement of ATB (Antenna Tracking Board) - OR Rotary Joint... 254
11.7 Remove & replacement of HPA Board.............................................. 256
11.8 Guide in arranging cables................................................................. 257
Inmarsat Network
SAILOR FleetBroadBand 1
Training Manual
1 Inmarsat Network
BGAN-X (SAILOR 500 FleetBroadband, SAILOR 250
FleetBroadband and SAILOR 150 FleetBroadband) is a platform
delivering “always-on” Internet service, telephony /fax and ISDN.
1
The BGAX-X platform delivers a higher data rate than any of the
previous Inmarsat systems by the use of their I4 (Inmarsat 4)
satellites, the BGAN network and a new generation of small and
light user terminals.
1.1 Overview
UT’s (BGAN-X User Terminals, SAILOR 500 FleetBroadband,
SAILOR 250 FleetBroadband and SAILOR 150 FleetBroadband)
offer communications through a microwave link anywhere with a
line-of-sight to one of the Inmarsat-4 geostationary satellites.
The I-4 satellites (APAC (Asia-Pacifi c) @ 143ºE, Americas @
98ºW and EMEA (Europe-Middle East-Africa) @ 25ºE) relays
traffi c between the UT’s and the SAS (Satellite Access Stations).
Figure 1-1: BGAN-X network overview

A SAS is a BGAN-X Earth Station, of which there are three – one
in Burum in the Netherlands and two on Hawaii.
The SAS houses the RNS (Radio Network Stations) and the CN
(Core Network) mainframes.
The RNS’, there are three of them (one in Burum, the Netherlands
and two on Hawaii) manages the radio traffi c to and from the satellite
whereas the CN provides the terrestrial telecommunications
infrastructure and switching.
All traffi c passes through the RNS and CN where it is interconnected
the DP’s IP networks (IP traffi c = PS (Packet Switch)) or the public
telephone network (voice, fax, ISDN = CS (Circuit Switch)).
2 Chapter 1
Inmarsat Network
Figure 1-2: BGAN-X Radio Access Network

The CN consists of four modules, MGW (Media GateWay), MSC
(Mobile Switch Center), VLR (Visitor Location Register), SGSN
(Service GPRS Support Node) and GGSN (Gateway GPRS
Support Node).
The I-4 satellite communicates with UTs using spectrum in the L-
band (around 1.6 GHz).
The I-4 satellite communicates with SAS’s using spectrum in the
C-band (4-8 Ghz).
The I-4 satellite subdivides its L-band spectrum into a total of
approximately 600 channels in the forward (RNC to UT) direction
and the same number in the return (from UT to RNC) direction.
Each slot or ‘sub-band’ is 200 kHz wide.
The I-4 satellite increases the total channel capacity by means of
frequency reuse.
By subdividing the coverage into different beams, the same channel
frequencies can be reused many times. The same frequencies
cannot be used in overlapping beams to avoid interference but
where beams are spatially separated frequency reuse is used
extensively. Beams serving a wide coverage area offer lower data
rates and less frequency reuse. Beams serving a concentrated
coverage area offer high data rates and high frequency reuse.
Training Manual
1.2 Beam types

Each Inmarsat-4 satellite provides the following beams /coverage.
1
1.2.1 Global Beam
Global beams:
Figure 1-3: EMEA Figure 1-4: APAC Figure 1-5: AMERICAS

The Global beams are used only for tracking signal and Bulletin
Board transmissions from Inmarsat.
There are only one Global beam from each satellite.
1.2.2 Regional Beams

Regional beams:

The Regional beams are used for registration after power up, Call
Announcements and Call set-up when signed in.
The actual Regional beam is selected on basis of the GPS position
of the FleetBroadband.
When the FleetBroadband is in idle mode, it is “resting in the
Regional beam. Also if the FleetBroadband has a data session
up running, but is not transferring any data up or down, the
FleetBroadband is returned to Regional beam to free resources
for other users, though the network is aware of the allocated
channel, which will be given back as soon as a data transfer is
started again.
There are 19 Regional beams from each satellite, covering the
entire satellite footprint.
4 Chapter 1
Inmarsat Network
1.2.3 Narrow Beams
1 Narrow beams:

The Narrow beams are used for the actual communication, data,
voice and fax. The communication is taking place on a shared
channel, which can be the reason for a lower throughput that
expected.
The actual Narrow beam is selected on basis of the GPS position
of the FleetBroadband.
There are >200 Narrow beams from each satellite, covering the
entire satellite footprint.
1.2.4 Beam Hierarchy

When a BGAN-X is terminating its traffic connection in a Narrow
Beam, it is immediately transferred back to the Regional Beam.
When the last BGAN-X has left a Narrow Beam, the Forward
Carrier in that beam is removed and the Forward and Return
Channels are returned to the pool of free satellite capacity.
To avoid congestion in Narrow Beam by idle IP connections, the
RNS will also time-out a variable bit rate connection if no packets
are exchanged for a period of time and then hand back the
BGAN-X to the Regional Beam. If packets subsequently arrives
at the BGAN-X or the RNS for this connection, then the satellite
channels are immediately allocated in the Narrow Beam (if they
are not already there), and the BGAN-X is returned to the Narrow
Beam and the connection is restored, ready to exchange traffic.
The BGAN-X does not need to use a keep-alive mechanism to
keep the connection open.
Training Manual
BGAN-X Satellite Beam hierarchy and functions:
Figure 1-12: Beam hierarchy
1.2.5 Elevation bands

The observed performance or speed of the IP data connection is
infl uenced by many factors.
With the three different antenna sizes, of the three classes, the
achievable data rates will differ. Essentially, the larger the antenna
the greater the achievable bit rate, particularly in the uplink or
return direction. Larger antennas will also enable higher bit rates in
more demanding ‘edge of beam’ locations and will provide service
to lower elevation angles towards the satellite and in conditions of
high fading (e.g. calm water conditions (mirror effect)). In addition
the performance of the antenna in terms of gain, G/T and ability to
reject multipath will also affect the achievable bit rate.
6 Chapter 1
Inmarsat Network
Elevation bands:

End users will also experience that the number of users sharing
the bearer, at any particular time, will have an impact on the
achievable bit rate, along with at low elevation angles for a
specific terminal/link conditions. Each 512 kbps bearer needs to
accommodate some system overheads, meaning the maximum
theoretical bandwidth available for users will be 432 kbps. As has
been said previously, many actors will influence the achieved bit
rate experienced by end users.
Max. bit rate, Max. bit rate,

downlink uplink
SAILOR 500
432 kbps 432 kbps
FleetBroadband
SAILOR 250
284 kbps 284 kbps
FleetBroadband
SAILOR 150
150 kbps 150 kbps
FleetBroadband
Figure 1-16: Maximum bit rate

The BGAN-X network maximises the use of this satellite capacity
by dynamic re-allocation to meet the demand, to ensure bandwidth
is always available when and where the users need it.
1.3 BGAN-X units

1.3.1 BGAN-X Terminal classes and capabilities
The BGAN-X system supports a range of FleetBroadband types
with differing capabilities. The BGAN service is launched with
three FleetBroadband classes, all maritime devices, i.e. tracking
units automatically pointing towards the satellite during use.
The Class 8 system (SAILOR 500 FleetBroadband) is a high
performance terminal with a large antenna (16 patches (the old
antenna has 19 patches)) supporting the maximum data rates.
The Class 9 system (SAILOR 250 FleetBroadband) is the same
terminal as SAILOR FB500 but has a somewhat smaller antenna
(three helixes) and can support marginally lower data rates.
The Class 14 system (SAILOR 150 FleetBroadband) has an even
smaller antenna (two helixes) supporting the lowest data rates.
Training Manual
Under ideal conditions the most powerful FleetBroadband can
1
transmit and receive at a data rate of 492 kb/s before subtracting
signalling overheads.
Each of the FleetBroadband will have different capabilities. Sharing
capacity efficiently among different populations of system classes
with different capabilities and in different link conditions across
the satellite coverage requires considerable flexibility in managing
channel capacity. There are a number of capabilities shared by all
the current three FleetBroadband classes.
A FleetBroadband system can transmit bursts of up to 200 kHz in
bandwidth and can receive one or two carriers at a time (typically
one) also within a 200 kHz band.
The frequency tuning of a FleetBroadband transmitter and receiver
operate independently.
FleetBroadband can transmit and receive simultaneously.
FleetBroadband receive continuous forward transmissions but
transmit in 5 msec. or 20 msec. bursts in the return direction.
FleetBroadband transmit either intermittently or up to a 100% duty
cycle.
Once the FleetBroadband has acquired the global beam carrier
all subsequent FleetBroadband receive or transmit tuning is
commanded by the RNS.
FleetBroadband can support multiple traffic connections
simultaneously.
Different FleetBroadband classes have different capabilities in
terms of numbers of connections that they can support. As far
as the RNS QoS (Quality of Service)management is concerned
these connections are managed no differently to connections from
separate FleetBroadband’s.
At present the network supports no more than one circuit
switched call per unit.
Up to eleven simultaneous IP connections are supported
(FleetBroadband class permitting).
1.3.2 Subscription and Quality of Service (QoS)

When a traffic connection is initiated the BGAN Core Network
checks that the user has subscribed to the service that they have
requested. For IP services, the subscription dictates which IP
networks the user is permitted to access via BGAN (e.g. corporate
VPNs). For each of these networks the subscription sets the
maximum quality of service (bit rate, traffic class etc.) that the
user is permitted to request when initiating a packet session to
that network. The QoS (Quality of Service) parameters supported
in BGAN follow the UMTS Release 4 as specified by the UMTS
standardisation body, 3GPP.
The subscription sets the maximum QoS for an IP connection but a
user may choose to connect using a lower value. E.g. a subscriber
can use a variable bit rate connection even if the subscription to
the IP network permits a guaranteed bit rate but not vice versa.
8 Chapter 1
Inmarsat Network
Alternatively there could be choose a 64 kb/s guaranteed bit
1
rate bearer even when the subscription permits 256 kb/s, but not
vice versa. The FleetBroadband supports a number of advanced
packet fi ltering techniques which allow precise control of IP Quality
of Service. Depending on the capabilities of the system class it is
possible to connect multiple computers to a single FleetBroadband
and run separate connections to different networks with different
QoS handling. IP packets to and from a FleetBroadband can be
de-multiplexed onto multiple simultaneous BGAN connections
each with separate QoS handling. This allows, e.g. video packets
to be carried on a guaranteed bit rate bearer at the same time as
TCP packets are carried on a variable bit rate bearer where both
types of traffi c are sent to and from a computer connected to a
FleetBroadband with a single IP address.
• Spacecraft specifi cation maximum number of channels per
narrow beam = 25.
• Practical maximum number of channels per narrow beam =
10.
BGAN Service Offering is 492 kbps per channel in each direction
(forward and return).
Total in the forward and return directions per channel is 984
kbps.
Calculations (total forward and return directions):
• Spacecraft specifi cation maximum capacity in a single narrow
beam = 25 channels x 984 kbps = 24,600 kbps or 24.6 Mbps.
• Practical maximum capacity in a single narrow beam = 10
channels x 984 kbps = 9,840 kbps or 9.84 Mbps.
1.4 RAN (Radio Access Network)

The RAN (Radio Access Network) consists of the following:
RFS (Radio Frequency System): Is responsible for transmission
and reception of RF signalling.
Figure 1-17: RAN

Training Manual
RAN Host, which has the RNS (Radio Network Station central
1
control roles of both resource (HW and SW) allocation and control
Bearer Service provision.
GRM (Global Resource Manager): Handles Carrier resource
allocation.
CUE (Channel Unit Equipment) that consists of: PU (Patch Unit),
MCU (Master Channel Unit), Rx and Tx Channel Units (CU).
MCU (Master Channel Unit): Terminating and handling of IAI-2
interface protocol, IAI-2 interface signalling and takes care of some
essential functions of UE traffic setup. Handling of SIB (System
Information Broadcast), Control ciphering, Authentication, Integrity
check, UE position, Link adaptation, Load report, Radio resource
management, user plane interface to CNGW, and control plane
interface to RAN Host.
CU (Rx and Tx Channel Units), which take care of data and
signalling transmission and reception from RF to RNS.
The TX/RX CU is responsible of the following functions:
• Build and pack up the control PDU.
• Transmit physical frames made by the Bearer Control layer.
• Calculation of CRC.
• Frame timing Generation (TX only).
• Collect status/Statistic data.
• Control of RF up/down-converter, RAN Host that has the RNS
central control roles of both resource (HW and SW) allocation
and control Bearer Service provision.
CNGW (Core Network Gateway), which has responsibly of
connection toward CN, handling of RANAP protocol, setup and
release IU signalling and RABs CNGW functions as a gateway
from RNC to UMTS Core Network. It takes care of:
• Terminating Iu connection for both CS and PS UE user plane
toward CN MSC (in case of CS connection) and SGSN (in case
of PS connection).
• ATM connection toward CN.
• Mapping RANAP operations/messages into RNC internal (LAN)
operations/messages and vice versa.
10 Chapter 1
Inmarsat Network
1.5 Core Network

1
Figure 1-18: Core Network
1.5.1 HLR (Home Location Registry)

A database residing in the BGAN network that contains Service
profi les:
• The “identity” of a local subscriber SIM card details:
• Home country
• Details of every SIM card
• ICC-ID
• stored MSISDN
• AMSISDNs
Figure 1-19
• IMSI
The HLR provides routing information for MT (Mobile Terminated)
calls and SMS (Short Message Service).
The HLR is also responsible for the maintenance of user
subscription information. This is distributed to the relevant VLR
(Visitor Location Register) or SGSN (Serving GPRS Support
Node) through the attach process and mobility
management procedures such as Location Area and Routing Area
updates.
1.5.2 MSC/VLR/MGW/SMSC/FRINs
MSC (Mobile Switching Centre):
Switch within a cellular network which can internetwork with
location data bases
VLR (Visitors Location Register):
The Visitors Location Register contains all subscriber data
required for cs-call handling and mobility management for mobile
subscribers currently located in the area controlled by the VLR.
MGW (Media Gateway):
Figure 1-20
A gateway that supports both bearer traffi c and signalling traffi c.
Training Manual
SMSC (Short Messaging Service Centre):

Short Messaging Service Centre- requires an smsc number which
instructs all sms’ from your mobile to be sent to this centre. This
then forwards the message to the destination number.
1
FRINs (Forced Routing Inmarsat Management System).
1.5.3 SGSN
SGSN (Servicing GPRS Support Node):
The SGSN registers a user onto the network, checks with HLR to
verify that the user is a valid user/subscriber and creates billing
files (CDRs).
The SGSN keeps track of the location of the individual MS’s and
performs security functions and access control.
A SGSN is responsible for the delivery of data packets to and from
the mobile stations within its geographical service area.
The tasks of the SGSN include packet routing and transfer, mobility
management (attach/detach and location management), logical
link management, and authentication and charging functions.
GPRS security functionality is equivalent to the existing GSM Figure 1-21
security.
The SGSN performs authentication and cipher setting procedures
based on the same algorithms, keys, and criteria as in existing
GSM.
GPRS uses a ciphering algorithm optimised for packet data
transmission.
1.5.4 GGSN
GGSN (Gateway GPRS Support Node):
The GGSN provides interaction with external packet-switched
networks, and is connected with SGSN’s via an IP-based GPRS
backbone network.
The GGSN acts as an interface between the GPRS backbone
network and the external packet data networks. It converts the
GPRS packets coming from the SGSN into the appropriate PDP
(Packet Data Protocol) format, e.g. IP, and sends them out on the
corresponding packet data network. In the other direction, PDP
addresses of incoming data packets are converted to the GSM
address of the destination user. The re-addressed packets are
sent to the responsible SGSN. For this purpose, the GGSN stores
the current SGSN address of their profile in its location register. Figure 1-22
The GGSN also performs authentication and charging functions.
The GGSN is uniquely identified by an APN (Access Point
Name).
It also creates billing files (CDR’s).
12 Chapter 1
Inmarsat Network
1.6 Distribution architecture

1 BGAN radio resource is managed by a group of distributed entities
which control satellite the capacity collectively.
Figure 1-23: Radio Recourse Management

RNC (Radio Network Controller) at the SAS manages the radio
resource for individual FleetBroadband Terminals. The LRM (Local
Resource Manager) is an entity within the RNC. It continuously
measures the demand in each spot beam and decides if the
number of satellite channels serving each regional or narrow
beam is adequate to meet demand. If there is unmet demand in a
beam the LRM will ask the GRM (Global Resource Manager) for
more channels. If the LRM has unused channels it will return them
to the GRM.
The GRM manages the radio resource for the entire satellite. Its
role is to arbitrate between the competing demands of the various
services on the satellite. The GRM provides fi xed capacity (used
by FleetBroadband in the global beam and regional beams). It also
maintains a pool of dynamic satellite channels which it supplies
to LRMs when they make requests (such as the FleetBroadband
traffi c bearers in the narrow beams which are deployed on
demand). If an LRM makes a request for capacity in a beam where
the GRM has no capacity, the GRM will ask the PCS (Payload
Control System) to switch a satellite channel into the beam. Such
reconfi gurations take no more than a couple of seconds. It is
not possible to anticipate precisely how many channels an LRM
needs because instantaneous demand for channels is inherently
unpredictable. However approximate estimates are useful for
planning purposes. The GRM gathers utilisation statistics from the
LRMs. These statistics are used for capacity planning by the FPS
(Frequency Planning System).
Training Manual
The FPS analyses the trends in demand and uses the results
1
to forecast demand over the next 24 hours and further into the
future. The FPS then periodically issues updated frequency plans
to the GRM. The GRM then applies these plans, reconfi guring the
channels used on the satellite payload and the LRMs to ensure
that capacity is available in beams ahead of peaks in demand. By
anticipating peaks and troughs by pre-confi guring approximately
the correct number of channels to each beam over the course of a
day, satellite capacity can be deployed more quickly with greater
frequency re-use and less congestion.
1.6.1 RNC Recourse Management Entities

The resource management entities, within the RNC, manage the
satellite capacity with a fi ne level of granularity than is visible to the
GRM. Below fi gure illustrates a simplifi ed view of the architecture
of the RNC resource management entities.
Figure 1-24: RNC Recourse Management

In each beam FleetBroadband Terminals and bearers are managed
collectively by an RNC function known as a “bearer control”. A
bearer control manages the bearers in a beam and allocates
capacity to the various connections such as circuit switched calls
and packet data sessions. A single FleetBroadband Terminal may
have one or more active connections. Multiple FleetBroadband
Terminals and their associated connections are concurrently
served by a bearer control. The bearer control will periodically
retune FleetBroadband Terminals between bearers to ensure that
demand is distributed to where there is most unused capacity. If
the load on a bearer control could be supported on fewer satellite
channels it will move FleetBroadband Terminals to concentrate
them on fewer bearers and return the unused channels to the
GRM. FleetBroadband Terminals with ongoing circuit switched
calls are locked to the same bearer for the duration of the call so
both of these load smoothing techniques have to wait until the
call has ended before moving a FleetBroadband Terminal. There
is no restriction on moving a FleetBroadband Terminal with an
IP connection. Forward and return load smoothing is carried out
independently.
14 Chapter 1
Inmarsat Network
Admission Control:
1 The RNC performs admission control when deciding whether to

allow a new connection onto a bearer control. If a connection can
be added without violating the quality of service of the existing
connections, it is permitted. If capacity is not available then the
RNC requests extra capacity from the GRM. If there is no extra
capacity then the connection must be rejected.
FleetBroadband Terminal reporting to RNC:
The FleetBroadband RRM centralises all resource handling
intelligence at the RNC. The FleetBroadband Terminals simply
follow the RNC’s instructions. The FleetBroadband Terminal RRM
is relatively simple and is primarily concerned with complying
with contention slot usage rules, measuring and reporting the
queue size of the data awaiting return transmission and making
and reporting link quality measurements of the received forward
direction bearer. The RNC instructs the FleetBroadband Terminal
how frequently it should make these measurements and takes all
the decisions on the basis of them.
Multiplexing:
The approach BGAN network used, uses to group traffic from
many FleetBroadband Terminals onto bearers, is complex. To
provide an overview of this mechanism we will discuss in basic
terms how capacity is allocated in the narrow beams since this
is where the user traffic is carried. In this section we discuss how
bearers are managed and how multiple users share bearers. As
we have described, narrow beams are illuminated with bearers
only when there is traffic to send or receive. When traffic increases
bearers are added to the beam. When traffic reduces, bearers
are removed. There is no pairing of forward and return bearers
– if there is more forward demand than return demand then more
forward bearers will be added to the beam.
Link Adaptation:
The BGAN network air interface uses link adaptation to increase the
capacity of BGAN bearers. Rather than fixing the data rates for all
FleetBroadband Terminals, link adaptation gives higher data rates
to those FleetBroadband Terminals with a better radio link. Thus
larger FleetBroadband Terminals and those with good pointing,
perhaps located in the centre of a beam can take advantage of
favourable link conditions to send or receive at a higher data rate.
The receiver (either the RNC or the FleetBroadband Terminal
depending on the direction of transmission) constantly measures
the received link quality and periodically reports this information
back to the sender. If the average link quality rises above the level
required to achieve a packet error rate of 0.1% (10-3), the sender
increases the transmission rate. If the average error rate falls
below 0.1% then the sender reduces the transmission rate. The
sender adjusts its transmission rate by selecting one of a range of
puncturing matrices to apply each turbo-coded block of data prior
to sending it.
Training Manual
The air interface can operate with a coding rate as low as 1/3 (i.e.
1
sending two bits of redundancy in addition to each bit of data)
and as high as nearly 1 (i.e. negligible redundancy). We can thus
operate over a wide range of link conditions from 42.0 dB C/No in
the worst case (for decoding the global beam forward bearer with
the class 14 FleetBroadband Terminal at the edge of coverage) to >
71.0 dB C/No in the best case (for decoding the narrow beam traffic
bearer with the class 8 FleetBroadband Terminal in the centre of
beam, centre of coverage). Although there is no scope to vary the
data rate delivered by a circuit switched connection such as voice
or ISDN, link adaptation ensures that circuit switched connections
consume as little capacity as possible to meet the target grade
of service. For variable bit rate packet switched connections (i.e.
background and interactive class IP), link adaptation constantly
delivers a peak bit rate to each connection as high as permitted by
its link quality. The target loss rate of 0.1% is not appropriate for
some types of traffic. Voice traffic is fine – error concealment in the
voice codec masks lost frames. ISDN needs a bit error rate of less
than 1 in a million (10-6), so we give ISDN data special treatment
to reduce the error rate.
Packet traffic is transmitted in “reliable mode”, (error correction).
½ i.e. any packets lost on the satellite link are automatically
retransmitted and re-ordered before being delivered. The residual
error rate after retransmission is thus negligible. Reliable mode will
incur a certain amount of random delay jitter when retransmissions
occur but this does not significantly add to the inherent jitter that
occurs in a packet data connection over a satellite link using TCP.
For users that need to minimize delay jitter on their IP traffic and
can tolerate a packet loss rate of 0.1% (e.g. certain real-time
applications or transport protocols) we offer a guaranteed bit rate
service that operates in unreliable mode. The RNC dictates what
code rate the FleetBroadband Terminal must use in the return
bursts to maintain the target packet error rate of 0.1%. Only if
a FleetBroadband Terminal has less data to send than the burst
size can it choose to lower the code rate and simultaneously
reduce the transmit power by an equivalent amount to achieve
the same target error rate. When retransmissions occur this does
not significantly add to the inherent jitter that occurs in a packet
data connection over a satellite link using TCP. For users that
need to minimize delay jitter on their IP traffic and can tolerate
a packet loss rate of 0.1% (e.g. certain real-time applications or
transport protocols) we offer a guaranteed bit rate service, (QOS)
that operates in unreliable mode (no error correction). The RNC
dictates what code rate the FleetBroadband Terminal must use in
the return bursts to maintain the target packet error rate of 0.1%.
Only if a FleetBroadband Terminal has less data to send than the
burst size can it choose to lower the code rate and simultaneously
reduce the transmit power by an equivalent amount to achieve the
same target error rate. This allows the FleetBroadband Terminal
to save some battery power.
16 Chapter 1
Inmarsat Network
Return Direction Queue Reporting:
1 For variable bit rate IP services the capacity available in

the return direction needs to be allocated according to the
competing demands of the connections sharing the channel.
The slotted ALOHA mechanism used for the contention slots in
the return direction is highly inefficient for bulk traffic so instead
FleetBroadband Terminals send small status messages to the
RNC listing the current amount of data queued for each of their
connections and how long that data has been waiting. The RNC
then uses this information to allocate return capacity taking into
account the needs of every other connection. The decisions taken
by the RNC are then reflected in the subsequent return schedules
issued to the FleetBroadband Terminals. When variable bit rate
data first appears in a FleetBroadband Terminals transmit queue
there is at least a satellite round-trip delay before the RNC can
acknowledge the status message and reserve bursts for the
connection in the return schedule. Once reserved bursts are
allocated to the FleetBroadband Terminal subsequent changes to
the queue size are sent in status messages along with the reserved
bursts on the connection, thus irrespective of the queue size at the
FleetBroadband Terminal the RNC’s record of how much data is
waiting to be sent is never older than a round trip time.
Scheduling:
Scheduling for Circuit Switched calls is rigid; however IP
connections must use a more flexible scheduling scheme. BGAN
network offers two IP traffic classes: Background IP Class and
Streaming IP Class. The scheduling discipline that the RNC
uses to allocate bandwidth between different IP connections is
derived from Worst Case Weighted Fair Queuing, one of a class
of algorithms designed to emulate a theoretical fairness ideal
known as Generalised Processor Sharing. At the start of each
connection the FleetBroadband Terminal requests a Quality of
Service (QoS) level for the connection which is constrained by
the user’s subscription and the available capacity. For circuit calls
and Streaming Class services, where the data rate requirement is
fixed and must be guaranteed, the connection will not be admitted
unless capacity is available.
The QoS level does not specify a minimum rate for Background
IP services i.e. variable bit rate connections (instead it specifies
a traffic class and a peak bit rate). Here, the RNC translates the
QoS into an internal bit rate target. This target rate is used by RNC
to control congestion in the network and is not advertised to the
user. A connection will not be admitted if the spare capacity in the
system is lower than this target. After a connection is admitted, at
every scheduling interval the RNC calculates the latest delivery
time that each packet would need to achieve the target rate. The
packets are then scheduled in the order of these delivery times
with the packet with the soonest delivery time scheduled first. This
approach is memory-less and independent of reported back-log.
Training Manual
Hence connections that exceed their target rate target in one
1
scheduling interval are not punished in subsequent scheduling
intervals. Any remaining capacity after all the target rates are
serviced is shared between the connections weighted by the
connection’s traffic class, a component of the connection’s 3G QoS
parameters. There are three degrees of congestion for variable bit
rate IP traffic – no congestion, acute congestion and moderate
sharing. If a FleetBroadband Terminal is the sole user of a bearer,
i.e. no congestion then the peak bit rate it achieves on a variable
bit rate packet connection will be limited by the available capacity
in the bearer and the FleetBroadband Terminals link quality. At
the other extreme under acute congestion conditions where all
FleetBroadband Terminals are sending or receiving, the RNC will
only try to service at the target rate for each connection. Note that
under acute congestion all connections with the same QoS receive
the same target rate irrespective of the FleetBroadband Terminals
link quality – weaker FleetBroadband Terminals get the same data
rates in these circumstances. In between these two extremes there
is moderate sharing state where capacity in excess of the target
rates is shared between the connections. Where connections have
the same QoS the excess slots or busts are allocated equally.
FleetBroadband Terminals with better link quality use the slots/
blocks more efficiently so the excess translates into higher bit
rates for the more powerful FleetBroadband Terminal classes.
1.7 Bearers
The Forward and Return Bearers have different layouts.
Forward Bearer Return Bearer

Frequency L-band: 1525,000 Frequency L-band: 1626,500
MHz - 1559,000 MHz MHz - 1660,500 MHz
TDM (Time Division Multiplex) TDMA (Time Division
Multiplex Access.
Total of 170 sub-bands (max. Total of 170 sub-bands
5% of max. power per spot)
200 KHz bandwidth (10.5 - 21 200 KHz bandwidth(10.5 - 21
- 42 - 84 - 189 KHz) - 42 - 84 - 189 KHz)
Modulation: 16QAM or QPSK Modulation: 16QAM or QPSK
Symbol rate: 8.4 - 16.8 - 33.6 Symbol rate: 16.8 - 33.6 -
- 67.2 - 151.2 kSym/sec 67.2 - 151.2 kSym/sec
Variable code rate Variable code rate
Data rate: 4.5 - 512 kbps Data rate: 8.4 - 492.8 kbps
5 msec or 20 msec burst
slots
C/No: 55 - 65 (4.5X8B)
Figure 1-25: Entries of the Forward and Return Bearers

18 Chapter 1
Inmarsat Network
1.7.1 Forward direction Bearer types
1 Beam Forward carrier
type
FEC blocks
per 80 msec
frame
Normal
satellite EIRP
/carrier dBW
Band-
width
KHz
Modulation
scheme
Symbol
rate kSym/
sec
Bit rate
kb/sec
Global F80T0.25Q1B 1 25.5 QPSK 8.4 8.4 4.5
Regional F80T1Q4B 4 29.2 QPSK 33.6 40 21.6 to
55.6 (link
adaptation)
F80T1X4B 4 29.2 16-QAM 33.6 30.4 42.8 to
109.2 (link
adaptation
Narrow F80T4.5X8B 8 40.5 16-QAM 151.2 41.2 113.6
Figure 1-26: Forward direction Bearer types
Forward carrier type C/No

F80T0.25Q1B 41.5  48.5 dBHz
F80T1Q4B 46.5  54.0 dBHz
F80T1X4B 51.0  59.5 dBHz
F80T4.5X8B 57.0  65.5 dBHz
Figure 1-27: Forward carrier type related to C/No
The BGAN network air interface offers a range of forward direction
bearers. For each type of beam (global, regional, narrow) Inmarsat
has selected appropriate forward direction bearers on the basis
of the satellite EIRP, FleetBroadband Terminal receive sensitivity
and required data rate. A forward direction bearer is a carrier
transmitting a continuous stream of 80 ms data frames at constant
power. Each of the 80 ms frames consists of one, four or eight
blocks of data (“FEC blocks”) each separately turbo-coded. Each
80 ms frame is preceded by a unique-word pattern. Pilot symbols
are interspersed throughout the frame to assist the FleetBroadband
Terminal with channel estimation and synchronisation.
A single forward bearer type has been chosen for use in the
global beam. This bearer has a bandwidth of 10.5 kHz, uses
QPSK modulation (2 bits per symbol) and has a bit rate of 4.5
kbps. (F80T0.25Q) There are two choices of forward bearer in
the regional beam. The Class 14 FleetBroadband Terminal cannot
decode the higher data rate 16 QAM (4 bits per symbol) bearer
because the antenna is too small, however the QPSK bearer is
inefficient for the FleetBroadband Terminal classes with larger
antennas – hence we retain the option to transmit both bearer
types in the regional beams with the Class 14 FleetBroadband
Terminals tuned to the QPSK bearer with a bit rate of 26.1-55.6
kbps, and the Class 8 and Class 9 FleetBroadband Terminals
tuned to the 16 QAM bearer with a bit rate of 42.8-109.2 kbps
(F80T1Q and F80T1X).
A single forward bearer type has been chosen for use in the narrow
beam. This bearer has a bandwidth of 189 kHz and uses 16 QAM
modulation with a bit rate of 200-492 kbps (F80T4.5X).
Training Manual
On each forward bearer the RNS plans the data and signalling to
1
be sent in advance, once every layout period. The layout period is
typically 40 ms or 80 ms.
System signalling and circuit switched connections require the
most rigid timing. Circuit switched calls are placed in the same
FEC blocks in consecutive frames so their position is fi xed before
deciding where to place other traffi c. The guaranteed bit rate
(streaming class) IP traffi c will be laid out next (the bit rate is
constant but averaged over a longer period so packets may not
appear in the same FEC block in consecutive frames). Lastly the
Standard Data packets, selected by the scheduling algorithm, is
slotted around the other traffi c and signalling.
1.7.2 Forward direction coding and multiplexing

A FleetBroadband Terminal tunes to a forward bearer and decodes
every FEC block on the bearer unless the code rate of the block is
too high. A FleetBroadband Terminal is permitted to save power
by receiving intermittently only when idle in a regional beam. The
RNS will never send data to a FleetBroadband Terminal in a
block with a code rate the FleetBroadband Terminal could not be
expected to receive given its link conditions.
A checksum is appended to every data unit. FleetBroadband
Terminals check all incoming data units against the checksum. If a
data unit fails the checksum the FleetBroadband Terminal discards
it and all that follow in the same FEC block. Only ISDN connections
are permitted to process data that failed the checksum because
discarding chunks of ISDN data would cause an unacceptably
high bit error rate for this type of service.
Figure 1-28: Payload

All data units are either addressed to a unique connection (i.e. a
circuit switched call or packet switched connection for a specifi c or
are broadcast to all FleetBroadband Terminals (e.g. bulletin board
signalling) or are ‘common signalling’ (e.g. paging messages).
The most common forward frame format in a narrow beam is
F80T4.5X8B. In this bearer type the 80 ms frame starts with a
unique word followed by eight individually turbo-coded blocks
(FEC blocks). Interspersed throughout the frame at equal intervals
(not shown) are pilot.
20 Chapter 1
Inmarsat Network
80ms forward frame illustrating how the frame is divided into
1
blocks of different code rates carrying traffi c for FleetBroadband
Terminals with differing link conditions. In this example, traffi c
connections for the FleetBroadband Terminals with the best link
conditions are carried in FEC blocks 2 and 6 in which the code
rate and consequently the data rate are highest.
Broadcast signalling and traffi c for the FleetBroadband Terminals
with the weakest link conditions are carried on FEC blocks 0 and 4
where the code rate and hence data rate are lowest. The remaining
FEC blocks carry traffi c for the FleetBroadband Terminals with link
conditions between the two extremes.
The code rates used in successive frames will change constantly
as the amount of data sent to the FleetBroadband Terminals
changes and their link conditions vary.
Figure 1-29: Forward bearer
1.7.3 Return direction Bearer types

Beam Return Bandwidth Burst Modulation Symbol Minimum Maximum
burst type KHz duration scheme rates kb/sec kb/sec
msec. ksym/sec
Regional R20T0.5Q 21 20 Pi&4 QPSK 16.8 8.4 22.4
Narrow R20T1X 42 20 16 / QAM 33.6 40 101.6
R5T1X 42 5 16 / QAM 33.6 30.4 75.2
R20T2Q 84 20 Pi&4 QPSK 67.2 41.2 113.6
R5T2Q 84 5 Pi&4 QPSK 67.2 30.4 86.4
R20T2X 84 20 16 / QAM 67.2 83.6 211.2
R20T4.5Q 189 20 Pi&4 QPSK 151.2 116.8 252.8
R20T4.5X 189 20 16 /QAM 151.2 192.8 492.8
Figure 1-30: Return direction Burst types
Forward carrier type C/No

F80T0.25Q1B 41.5  48.5 dBHz
F80T1Q4B 46.5  54.0 dBHz
F80T1X4B 51.0  59.5 dBHz
F80T4.5X8B 57.0  65.5 dBHz
Figure 1-31: Return burst type related to C/No
Training Manual
In the return direction the BGAN air interface operates in TDMA
1
(Time Division Multiple Access). A range of bearer types are
supported in the return direction. FleetBroadband Terminals
transmit bearers in bursts of either 5 msec. or 20 msec. in duration.
There are four possible symbol rates, two modulation schemes
and a variable coding scheme that is used to improve the data rate
in favourable link conditions.
1.7.4 Return direction coding, multiplexing and

synchronisation
Figure 1-32: Return bearer

Each FleetBroadband Terminal return burst is sent at a coding rate
appropriate to the FleetBroadband Terminals currently reported
link conditions (the link adaptation mechanism is described later
in this document) FleetBroadband Terminals transmit traffi c bursts
when instructed to by a schedule of timeslots broadcast by the RNS
(note that there is no return direction traffi c in the global beam so,
no return schedule is broadcast in the global beam). The schedule
tells the FleetBroadband Terminals which return direction timeslots
are reserved for each connection and what bearer type should
be used for each. The return schedule advertises a proportion of
timeslots available for all FleetBroadband Terminals to use i.e.
contention capacity for random access. BGAN network uses a
slotted ALOHA mechanism for random access.
1.7.5 Forward direction layout

On each forward bearer the RNC plans the data and signalling to
be sent in advance, once every layout period. The layout period is
typically 40 msec. or 80 msec.
System signalling and circuit switched connections require the
most rigid timing. Circuit switched calls are placed in the same
FEC blocks in consecutive frames so their position is fi xed before
deciding where to place other traffi c. The guaranteed bit rate
(streaming class) IP traffi c will be laid out next (the bit rate is
constant but averaged over a longer period so packets may not
appear in the same FEC block in consecutive frames. Lastly the
variable bit rate packets selected by the scheduling algorithm is
slotted around the other traffi c and signalling.
22 Chapter 1
Inmarsat Network
Figure 1-33: Forward direction connection bearers

Above fi gure illustrates how the resulting layout mechanism time-
slices capacity on the forward bearers for the various connections
active on each FleetBroadband Terminal.
The forward frame in the narrow beam has several FEC blocks and
each may have a different code rate. In the case of F80T4.5X8B
bearer there are 8 FEC blocks in each 80 msec. frame. The RNC
scheduler must decide what code rates each of the FEC blocks
must use by examining how much data each FleetBroadband
Terminal is to receive during the scheduling period and what their
current link conditions are.The fi rst FEC block includes broadcast
signalling so it must always be sent with a code rate low enough
for the least capable FleetBroadband Terminal.
Training Manual
Subsequent FEC blocks may have different code rates for more
1
capable FleetBroadband Terminals. The layout algorithm tries
to minimise wasted space in the frame by grouping connections
for FleetBroadband Terminals with similar link conditions into the
same FEC blocks.
1.7.6 Return direction layout

Like the forward direction, the RNC prepares the return layout
at regular intervals, typically every 40 msec. or 80 msec. The
goal of the layout algorithm is to organise time slots for the
FleetBroadband Terminal bursts to squeeze the maximum
capacity out of each satellite channel over the period of the layout
interval. Slots for three burst types for the connections that the
scheduling algorithm has chosen to serve during the interval.
Each reserved slot is assigned to a specific connection belonging
to a single FleetBroadband Terminal. FleetBroadband Terminals
are permitted to send small amounts of signalling (such as status
messages) to the RNC along with return bursts to reduce the load
on the contention slots. Circuit switched connections (i.e. ISDN
and voice in the narrow beams) are allocated return direction
slots in a rigid layout every 20 msec. or 40 msec. respectively in
order to minimise delay jitter. Contention slots can be used by any
FleetBroadband Terminal for sending status messages or other
signalling. The quantity and grouping of contention slots in each
layout period is calculated by the RNC on the basis of the number of
FleetBroadband Terminals listening to the corresponding forward
bearer, their expected signalling requirements and the proportion
that require un-timed access. Slots reserved for packet traffic are
laid out around the circuit switched calls and contention capacity.
When the return direction layout is complete, it is broadcast to
all the FleetBroadband Terminals listening to the corresponding
forward bearer. A forward bearer may broadcast schedules for
more than one return channel to allow asymmetric traffic to be
carried more efficiently.
24 Chapter 1
Inmarsat Network
Figure 1-34: Return direction connection bearers

Training Manual
1.7.7 Lease mode scenario

In the example below there are a total of four forward bearers and
three return bearers a beam. One forward and one return bearer is
used by public users. The remaining bearers in the beam are used
1
by two separate lease groups. The FleetBroadband Terminals
belonging to the separate lease groups have exclusive use of their
bearers and do not share capacity with members of other lease
groups or with the public users.
Lease Mode allows organisations to procure satellite capacity
in a cost effi cient fashion. Within the lease group the capacity is
shared and managed using the standard BGAN radio resource
mechanisms but the lease capacity is available to the lease group
members alone. It is as if the lease group members have access
to a separate BGAN network exclusively for their use.
If leased capacity becomes too congested to admit new
connections in a beam but capacity is still available to the public
users then lease group members will be admitted to the public
bearers. Conversely, public users will not be permitted to use the
lease capacity if public bearers are heavily congested.
Figure 1-35: Lease groups

Product Presentation
Training Manual
2 Product Presentation
The main difference between the SAILOR 500 FleetBroadband
systems and the SAILOR 250 FleetBroadband system lies in the
antenna.
2
• SAILOR® 500 FleetBroadband uses the TT-3052A/B/C
antenna, which is a maritime BGAN Class 8 antenna.
The TT-3052A/B/C antenna is larger and provides more
bandwidth than the TT-3050A antenna used for the SAILOR
250 FleetBroadband system.
• SAILOR® 250 FleetBroadband uses the TT-3050A antenna,
which is a medium size, maritime BGAN Class 9 antenna.
• SAILOR® 150 FleetBroadband uses the TT-3050C antenna,
which is a small size, maritime BGAN Class 14 antenna.
The SAILOR 500 FleetBroadband system and the SAILOR 250
FleetBroadband system basically use the same type of terminal,
except that the SAILOR 500 FleetBroadband offers a few more
features than the SAILOR 250 FleetBroadband. See later in this
chapter.
2.1 SAILOR 500 FleetBroadband

®
2.1.1 System overview
Figure 2-1: Figure 2-2:

SAILOR 500 FleetBroadband, antenna ver. A SAILOR 500 FleetBroadband, antenna ver. B
30 Chapter 2
Figure 2-3: SAILOR 500 FleetBroadband, antenna ver. C

SAILOR 500 FleetBroadband is a maritime broadband system,
providing simultaneous high-speed data and voice communication
via satellite through the BGAN (Broadband Global Area Network).
The SAILOR 500 FleetBroadband system offers the following
features and interfaces:
• Simultaneous voice (up to 9 voice calls) and data communication
over BGAN.
Full duplex, single or multi-user, up to: 432 kbps
• Support for streaming IP at: 8, 16, 32, 64, 128, 256 kbps
• ISDN (Integrated Services Digital Network) service: 64 kbps
• Voice: Standard Voice (4 kbps) or 3.1 kHz Audio
• 4 LAN (Local Area Network) ports with PoE (Power over
Ethernet) for computers, e-hubs, IP handsets etc.
• 2 Standard Phone/Fax ports for standard phones or fax
machines
• 1 Euro ISDN port for ISDN phones or G4 fax or ISDN modem
• 1 L-Band output for connecting a broadcast receiver for maritime
data
• 1 multi-purpose I/O connector with 5 configurable inputs/
outputs
• 1 SIM slot for your FleetBroadband SIM card
• Built-in DHCP /NAT router
• Built-in web interface allowing you to manage your phone book,
messages and calls, and customize the terminal to your specific
needs
• Remote access to the web interface
• Input power: 10.5 - 32 V DC (14 A - 5.5 A)
• CE certified
Training Manual
2.1.2 Above Deck Units (ADU)

The SAILOR 500 FleetBroadband exists in three different ADU’s,
which all will be described here.
Figure 2-4: TT-3052A ADU

TT-3052A SAILOR 500 FleetBroadband ADU (Above Deck Unit)
is the first version of antenna for the SAILOR 500 FleetBroadband
system. Last delivery of this antenna was January 2010.
The antenna contains all functions for satellite tracking including a
GPS system. A single coax RF cable carries all RF communication,
supply voltage for the antenna modules and internal modem
communication between the antenna and the Terminal.
Figure 2-5: TT-3052A ADU, opened and rear view

• Antenna Tracking Board (ATB) is a multipurpose unit which is
receiving, filtering and tracking on the signal from the satellite.
It is also calculating and adding input from sensors in order to
power the motors and thereby always orientate the Antenna
Panel towards the satellite.
32 Chapter 2
Figure 2-6: TT-3052A ADU, Antenna Tracking Board

• High Power Amplifier (HPA) purpose in primary operation
is to handle the communication between the Antenna and
the BDU /Terminal. It also is amplifying the RF signals from
the satellite to an adequate level for transmission to the
BDU /Terminal and from the BDU /Terminal a RF output
signal strong enough to reach the satellite out in space.
• Secondary the HPA is transforming and distributing the power

input from the BDU /Terminal to internal use in the HPA and to
the peripheral Antenna modules. Finally it is the HPA that stores
the information regarding the type of Antenna of the SAILOR
500 FleetBroadband version A. The HPA PCB is identical in all
three antenna versions of SAILOR 500 FleetBroadband ADU,
though the metal box cover is slightly different.
Figure 2-7: TT-3052A ADU, High Power Amplifier

• Global Positioning System (GPS) module has on the one
side a receiver /antenna and on the other side the engine /
processor. It is receiving the signals from the GPS satellites
and if more than four (4) satellites signals are available, the
GPS module can calculate a longitude and a latitude position.
The SAILOR 500 FleetBroadband system requires a GPS fix
in order to operate, as it needs to be positioned into a regional
spot beam or a narrow spot beam of the satellite. The GPS
module is identical for all five (5) SAILOR FleetBroadband
antennas (and for SAILOR 900 VSAT antenna).
Training Manual
Figure 2-8: TT-3052A ADU, Global Position System

• Motors (Elevation, Cross-Elevation and Azimuth Motor) are
used to orientate the antenna panel towards the satellite.
The Elevation Motor and the Azimuth Motor are used as the
main orientation motors, whereas the Cross-Elevation Motor
is basically used to fine adjust the bearing when the antenna
is in track of the satellite. The Elevation Motor and the Cross-
Elevation Motor are identical.
Figure 2-9: TT-3052A ADU, Elevation motor
Figure 2-10: TT-3052A ADU, Cross-Elevation motor

34 Chapter 2
Figure 2-11: TT-3052A ADU, Azimuth motor

• Rotary Joint is not only the de facto Pedestal and mounting of
the antenna to the vessel. It is also providing the RF signals,
internal modem communication and power from the Terminal,
through the stationary platform of the antenna to the rotating
part of the antenna. Last it is providing RF signals and internal
modem communication from the antenna to the Terminal.
Figure 2-12: TT-3052A ADU, Rotary Joint
Figure 2-13: TT-3052B ADU

Training Manual
TT-3052B SAILOR 500 FleetBroadband ADU is the of antenna

for the SAILOR 500 FleetBroadband system completely designed
and manufactured by Cobham SATCOM. This antenna had first
customer delivery January 2010.
The antenna is a maritime 3-axis controlled BGAN antenna. The
2
antenna contains all functions for satellite tracking, including a
GPS (Global Positioning System). A single coax RF cable carries
all RF communication, supply voltage for the antenna modules and
modem communication between the antenna and the Terminal.
Figure 2-14: TT-3052C ADU

TT-3052C SAILOR 500 FleetBroadband ADU is the latest version
of antenna for the SAILOR 500 FleetBroadband system completely,
where only the top and bottom dome differs from the TT-3052B
ADU. All content (modules) inside the TT-3052C is identical with
the TT-3052B.
Figure 2-15: TT-3052B/C ADU, opened and rear view

• Antenna Tracking Receiver (ATR) is connected to the two
halves of the antenna panel for both transmit and receive.
36 Chapter 2
In transmit direction, the RF is received from the HPA and

distributed to all the patches of the antenna panel. In receive
direction RF signal from the satellite is picked up by the antenna
patches of the panel and is amplified before sent to the HPA.
Additional the ATR is handling the sum and the differential
signal of the L-band signal from the satellite, provided from
2 the antenna panel, to be used for tracking purpose. Both these

signals are sent to the ATM for further action. The ATR is
powered from the ATM.
Figure 2-16: TT-3052B/C ADU, Antenna Tracking Receiver

• Antenna Tracking Module (ATM) consists of two (2) parts and
is combining several actions. One of the activities is sensing
the antenna movements in order to hold the antenna panel
beam horizontal at all times. Another activity is the motor control
and drive of the three stepper motors (azimuth, elevation and
cross-elevation). Last it is also the antenna control, where it is
combining all input from the sources to point the antenna panel
towards the satellite. The input are received from the Terminal,
the GPS, the ATR and the sensors. Finally it is the ATM that
stores the information regarding the type of Antenna in the
version B and C of the SAILOR 500 FleetBroadband.
Figure 2-17 and 2-18: TT-3052B/C ADU, Antenna Tracking Module

• High Power Amplifier (HPA) purpose in primary operation is
to handle the communication between the Antenna and the
BDU /Terminal. It also is amplifying the RF signals from the
satellite to an adequate level for transmission to the BDU /
Terminal and from the BDU /Terminal a RF output signal strong
enough to reach the satellite out in space. Secondary the HPA
is transforming and distributing the power input from the BDU /
Terminal to internal use in the HPA and to the peripheral Antenna
modules. The HPA PCB is identical in all three antenna versions
of SAILOR 500 FleetBroadband ADU, though the metal box
cover is slightly different.
Training Manual
Figure 2-19: TT-3052B ADU, High Power Amplifier

processor. It is receiving the signals from the GPS satellites and
if more than four (4) satellites are available, the GPS module
can calculate a longitude and a latitude position. The SAILOR
500 FleetBroadband system requires a GPS fix in order to
operate, as it needs to be positioned into a regional spot beam
or a narrow spot beam of the satellite. The GPS module is
identical for all five (5) SAILOR FleetBroadband antennas (and
for SAILOR 900 VSAT antenna).
Figure 2-20 and 2-21: TT-3052B/C ADU, Global Position System

• Stepper motors for orientating the antenna is positioned in
the three axis: azimuth, elevation and cross-elevation. The
elevation motor and the cross-elevation motor is the same type,
while the azimuth motor is unique for the antenna. The motors
are controlled by the ATM, and no feedback is provided. The
motor power is transferred into antenna movement by means
of drive belts.
38 Chapter 2
Figure 2-22: TT-3052B/C ADU, Azimuth Motor
Figure 2-23: TT-3052B/C ADU, Elevation Motor
Figure 2-24: TT-3052B/C ADU, Cross-Elevation Motor

• Antenna Panel is equipped with 16 patches to receive and
transmit the RF signals to and from the satellite. On the antenna
panel also is mounted the splitter for the sum and the differential
satellite signals, to be sent further on to the ATR.
Training Manual
Figure 2-25: TT-3052B/C ADU, Antenna Panel

• Rotary Joint is providing the RF signals, internal modem
communication and power from the Terminal, through the
stationary platform of the antenna to the rotating part of the
antenna. Last it is providing RF signals and internal modem
communication from the antenna to the Terminal.
Figure 2-26: TT-3052B/C ADU, Rotary Joint
Figure 2-27: SAILOR FleetBroadband 500 antenna ver. C

40 Chapter 2
• TT-3052C SAILOR 500 FleetBroadband ADU is the latest

version of antenna for the SAILOR 500 FleetBroadband
system, generally the same antenna as the 3052B, though
only the dome (top and bottom) is different. This antenna had
first customer delivery August 2011.
2 NOTE!
The IP Handset has some
2.1.3 Below Deck Units (BDU) /Terminal
BGAN terminal control The SAILOR 500 FleetBroadband exists in two different BDU’s
functions. If configured as
handset with the local number
/Terminals, which both will be described here.
0501, you can use the
handset to start and stop data
connections (background or
streaming) for all network user
groups.
NOTE!
To improve overall system
overview the IP Handset
displays active, critical alarms
from the BGAN terminal to
keepyou informed about the
status of the BGAN terminal.
Figure 2-28: TT-3738A BDU

SAILOR FleetBroadband Terminal TT-3738A is the controlling
unit in the SAILOR FleetBroadband system. It contains the primary
electronic parts, all user interfaces and LED indicators and it stores
configuration data.
The DC input for the SAILOR FleetBroadband Terminal is designed
for 24 VDC nominal.
The SAILOR FleetBroadband Terminal supplies 18-29 VDC to the
antenna through a single coaxial cable.
The Terminal is basically the same for SAILOR 500 FleetBroadband
system and the SAILOR 250 FleetBroadband system.
Figure 2-29: TT-3738A-T19 BDU, 19” rack version

SAILOR FleetBroadband Terminal TT-3738A-T19 is a terminal
available as a 19” Rack version. The 19” Rack Terminal is the
same as the basic version, except for the housing which fits in a
19” rack and has an additional power switch on the front panel.
Training Manual
2.1.4 Thrane IP Handset

The IP Handset is used for making phone calls over an IP based
network. When used with a BGAN terminal, the communication is
only IP based between the handset and the BGAN terminal.
2
From the BGAN terminal, the call is transmitted as a normal circuit-
switched call.
The handset is designed specifically for use in harsh environments
and it is dust proof and splash proof.
Excellent sound quality is achieved by including a state-of-the-art
echo canceller and noise suppression software.
On the large 2.2” colour TFT screen, a graphical user interface
provides easy access to all functions including contacts and
settings. The user interface also provides direct access to certain
features of a connected BGAN terminal.
There are two variants of the handset: A wired model TT-3672A
and a wireless model TT-3672B.
Figure 2-30: TT-3672A IP Handset

TT-3670A Thrane IP Handset is delivered as standard with the
SAILOR FleetBroadband system comes as a wired handset,
which is powered directly from the LAN interface of the SAILOR
FleetBroadband Terminal, using Power over Ethernet (PoE), so
an external power supply is not needed.
The TT-3670A Thrane IP Handset, wired, includes the following
main units:
• TT-3672A Thrane IP Handset, wired
• TT-3674A Thrane IP cradle, wired
The IP Handset connects to the cradle with a coil cord. The cradle
connects with a fixed LAN cable to a LAN port with PoE, for satellite
communication.
42 Chapter 2

®
Figure 2-31: SAILOR 250 FleetBroadband

via satellite through the BGAN (Broadband Global Area
Network).
over BGAN.
• Full duplex, single or multi-user, up to: 284 kbps
• Support for streaming IP at: 8, 16, 32, 64, 128 kbps
• Voice: Standard Voice (4 kbps) or 3.1 kHz Audio
• 2 Standard Phone/Fax ports for standard phones or fax
machines
• 1 Euro ISDN port, unsupported
• 1 L-Band output for connecting a broadcast receiver for maritime
data
outputs
needs
• CE certified
Training Manual
2.2.2 Above Deck Unit (ADU)

TT-3050A SAILOR 250 FleetBroadband ADU (Above Deck
Unit) contains all functions for satellite tracking including a GPS
system. A single coax RF cable carries all RF communication,
Figure 2-33: TT-3050A ADU, opened

• Antenna Control Module (ACM), located on the bottom side of
the Top Housing Cover, is sensing the attitude and accelerations
of the ADU, and controls the stepper motors which is moving
the pedestal accordingly.
The ACM is comprised of:
• Inertial Navigation Unit circuit
The Inertial Navigation Unit senses the position and motions
44 Chapter 2
of the vessel and calculates the azimuth and elevation angles

(in the antenna coordinate system) necessary to point the
antenna towards the satellite.
It is made as a “strap down” type placed inside the radome
on the base.
2
The sensors is solid state (MEMS) accelerometers and rate
gyros.
The sensor inputs to the ACM are:
• 3 axis Rate Gyro (for roll, pitch and yaw)
• 3 axis Accelerometer (for roll, pitch and yaw)
• GPS
• Stepper Motor Control circuit
A pointing routine is calculating the pointing direction and
controls the stepper motor drivers.
A special care has be taken when the antenna pointing is
close to gimbal lock, where the wide antenna beam width is
used to reduce fast azimuth motions.
• Zero reference circuit
The zero reference circuit senses when the antenna element
is in its “zero” position, meaning heading and 0º elevation.
• Power Supply circuit
Is receiving several power supplies from the HPA, in the
antenna, and is distributing internally in the ACM and to the
MDM, GPS Module and the Zero Reference Board.
Figure 2-34: TT-3050A ADU, Antenna Control Module

• Motor Drive Module (MDM) also located on the bottom side
of the Top Housing Cover, and contains the Stepper Motor
Driver circuits, which is receiving the step- and direction
commands from the ACM and drive the two (2) Stepper Motors
accordingly.
The MDM also contains the identity of the antenna in a E2PROM
circuit, meaning that it stores the information regarding the
type of Antenna of the SAILOR 250 FleetBroadband
Training Manual
Figure 2-35: TT-3050A ADU, Motor Drive Module

2
• ACM / MDM Combo is the Antenna Control Module and Motor
Driver Module combined as one module, but it has the same
functionality as the two modules. This ACM /MDM Combo
has been introduced late 2009 in production SAILOR 250
FleetBroadband, and is backward compatible with the versions
of individual modules.
Figure 2-36: TT-3050A ADU, Antenna Control Module /Motor Drive Module Combo
• Zero Reference Board (ZRB) contains two hall sensors
sensing the “Zero” position, heading and 0º elevation, by means
of a small magnet in each drive wheel. The “Zero” position
information is sent to the ATM and at the same time lit a LED
on the ZRM it self for each sensor.
Figure 2-37: TT-3050A ADU, Zero Reference Board

46 Chapter 2

2 operate, as it needs to be positioned into a regional spot beam

identical for all five (5) SAILOR FleetBroadband antennas.
Figure 2-38 and 2-39: TT-3050A ADU, Global Position System antenna and engine
• High Power Amplifier (HPA), located in the bottom of the
Bottom Radome, has the purpose in primary operation is to
handle the communication between the Antenna and the
modules. In principle, the HPA is identical to the one used in the
SAILOR 500 FleetBroadband ADU, though not installed in the
box and without cooling fan.

• Duplexer & Low Noise Amplifier (DLNA), located in the
bottom of the Bottom Radome, has the purpose of amplify an
route the RF signals in both RX and TX direction. In the TX
direction it is routing the RF signal directly from the HPA to the
Pedestal through the duplexer. In the RX direction the RF signal
is routed from the Pedestal through the Low Noise Filters and
amplifier to the HPA.
Training Manual
2
Figure 2-41: TT-3050A ADU, Duplexer & Low Noise Amplifier
• Drive Motors there are two (2) of which in combination is
orientating the antenna panel towards the by the command of
the ATM and the drive of the MDM. The transfer of movement
from the motors to the pedestal is done via drive belts, tensioned
automatically by the drive belt tensioner seen at the top side of
the Top Housing Cover, one for each motor.
Figure 2-42: TT-3050A ADU, drive belt tensioner

• Rotary Joints two (2) of them is situated in the pedestal and
one is for azimuth motion (vertical positioned) and the other is
elevation motion (horizontal positioned).
Figure 2-43: TT-3050A ADU, Rotary Joints

• Antenna Panel of the SAILOR 250 FleetBroadband ADU is a
three (3) helix construction.
48 Chapter 2
Figure 2-44: TT-3050A ADU, Antenna Panel

The SAILOR 250 FleetBroadband exists in two different BDU’s
/Terminals versions, actually the same as for SAILOR 500
FleetBroadband, which both will be described here.
NOTE!
The IP Handset has some
BGAN terminal control
functions. If configured as
handset with the local number
0501, you can use the
handset to start and stop data
connections (background or
streaming) for all network user Figure 2-45: TT-3738A BDU
groups.
NOTE! electronic parts, all user interfaces and LED indicators and it stores
To improve overall system
overview the IP Handset
configuration data.
displays active, critical alarms The DC input for the SAILOR FleetBroadband Terminal is designed
from the BGAN terminal to for 24 VDC nominal.
keepyou informed about the
status of the BGAN terminal. The SAILOR FleetBroadband Terminal supplies 18-29 VDC to the
Figure 2-46: TT-3738A-T19 BDU, 19” rack version

SAILOR FleetBroadband Terminal TT-3738A-T19 is a terminal
Training Manual
available as a 19” Rack version. The 19” Rack Terminal is the

same as the basic version, except for the housing which fits in a
19” rack and has an additional power switch on the front panel.

only IP based between the handset and the BGAN terminal.
2

main units:
communication.
50 Chapter 2

®
Figure 2-48: SAILOR 150 FleetBroadband

via satellite through the BGAN (Broadband Global Area
Network).
over BGAN.
• Full duplex, single or multi-user, up to: 150 kbps
• Voice: Standard Voice (4 kbps)
• 1 Standard Phone port for standard
outputs
needs
• CE certified
Training Manual
2.3.2 Above Deck Unit (ADU)

TT-3050C SAILOR 150 FleetBroadband ADU (Above Deck
Unit) contains all functions for satellite tracking including a GPS
system. A single coax RF cable carries all RF communication,
The functionality and hardware are pretty much identical to the
SAILOR 250 FleetBroadband ADU.
Figure 2-50: TT-3050C ADU, opened

• Antenna Control Module (ACM), located on the bottom side of
the Top Housing Cover, is sensing the attitude and accelerations
of the ADU, and controls the stepper motors which is moving
the pedestal accordingly.
52 Chapter 2
The ACM is comprised of:

• Inertial Navigation Unit circuit
The Inertial Navigation Unit senses the position and motions
of the vessel and calculates the azimuth and elevation angles
(in the antenna coordinate system) necessary to point the
2
antenna towards the satellite.
It is made as a “strap down” type placed inside the radome
on the base.
The sensors is solid state (MEMS) accelerometers and rate
gyros.
The sensor inputs to the ACM are:
• 3 axis Rate Gyro (for roll, pitch and yaw)
• 3 axis Accelerometer (for roll, pitch and yaw)
• GPS
• Stepper Motor Control circuit
A pointing routine is calculating the pointing direction and
controls the stepper motor drivers.
A special care has be taken when the antenna pointing is
close to gimbal lock, where the wide antenna beam width is
used to reduce fast azimuth motions.
• Zero reference circuit
The zero reference circuit senses when the antenna element
is in its “zero” position, meaning heading and 0º elevation.
• Power Supply circuit
Is receiving several power supplies from the HPA, in the
antenna, and is distributing internally in the ACM and to the
MDM, GPS Module and the Zero Reference Board.
Figure 2-51: TT-3050C ADU, Antenna Control Module

• Motor Drive Module (MDM) also located on the bottom side of
the Top Housing Cover, and contains the Stepper Motor Driver
circuits, which is receiving the step- and direction commands
from the ACM and drive the two (2) Stepper Motors accordingly.
• The MDM also contains the identity of the antenna in a E2PROM
circuit, meaning that it stores the information regarding the type
of Antenna of the SAILOR 150 FleetBroadband.
Training Manual
Figure 2-50: TT-3050C ADU, Motor Drive Module

2
• ACM / MDM Combo is the Antenna Control Module and Motor
Driver Module combined as one module, but it has the same
functionality as the two modules. This ACM /MDM Combo
has been introduced late 2009 in production SAILOR 150
FleetBroadband, and is backward compatible with the versions
of individual modules.
Figure 2-52: TT-3050C ADU, Antenna Control Module /Motor Drive Module Combo
• Zero Reference Board (ZRB) contains two hall sensors
sensing the “Zero” position, heading and 0º elevation, by means
of a small magnet in each drive wheel. The “Zero” position
information is sent to the ATM and at the same time lit a LED
on the ZRM it self for each sensor.
Figure 2-53: TT-3050C ADU, Zero Reference Board

54 Chapter 2

2 operate, as it needs to be positioned into a regional spot beam

identical for all five (5) SAILOR FleetBroadband antennas.
Figure 2-54 and 2-55: TT-3050C ADU, Global Position System antenna and engine
• High Power Amplifier (HPA), located in the bottom of the
Bottom Radome, has the purpose in primary operation is to
handle the communication between the Antenna and the
modules. In principle, the HPA is identical to the one used in the
SAILOR 500 FleetBroadband ADU, though not installed in the
box and without cooling fan.
Figure 2-56: TT-3050C ADU, High Power Amplifier

• Duplexer & Low Noise Amplifier (DLNA), located in the
bottom of the Bottom Radome, has the purpose of amplify an
route the RF signals in both RX and TX direction. In the TX
direction it is routing the RF signal directly from the HPA to the
Pedestal through the duplexer. In the RX direction the RF signal
is routed from the Pedestal through the Low Noise Filters and
amplifier to the HPA.
Training Manual
2
Figure 2-57: TT-3050C ADU, Duplexer & Low Noise Amplifier
• Drive Motors there are two (2) of which in combination is
orientating the antenna panel towards the by the command of
the ATM and the drive of the MDM. The transfer of movement
from the motors to the pedestal is done via drive belts, tensioned
automatically by the drive belt tensioner seen at the top side of
the Top Housing Cover, one for each motor.
Figure 2-58: TT-3050C ADU, drive belt tensioner

• Rotary Joints two (2) of them is situated in the pedestal and
one is for azimuth motion (vertical positioned) and the other is
elevation motion (horizontal positioned).
Figure 2-59: TT-3050C ADU, Rotary Joints

• Antenna Panel of the SAILOR 150 FleetBroadband ADU is a
two (2) helix construction.
56 Chapter 2
2
Figure 2-60: TT-3050C ADU, Antenna Panel

The SAILOR 150 FleetBroadband is different in design, with no
LED indicators and with only interfaces needed for its more limited
functionality.
Figure 2-61: TT-3739A BDU

electronic parts, all user interfaces and it stores configuration
data.
The DC input for the SAILOR FleetBroadband Terminal is designed
for 24 VDC nominal.
The SAILOR FleetBroadband Terminal supplies 18-29 VDC to the
Training Manual

only IP based between the handset and the BGAN terminal. From
the BGAN terminal, the call is transmitted as a normal circuit-
2
switched call.

main units:
communication.
58 Chapter 2
2.4 AC/DC Power Supply

TT-6080A AC/DC Power Supply is designed to deliver 300W
output power on average, and with a peak of 370 W for approx.
two (2) minutes. It is AC powered, but also designed with a battery
switch-over function. The input power to the power supply is 100 -
2 240 VAC or 28 VDC battery power, and the power output from the
power supply is 28.7 - 31.2 VDC.
The Power Supply has an On/Off switch, which is lit when power is
turned on. All connectors are placed at the same end of the power
supply to simplify installation and wiring. The connector panel is
protected by a semi-transparent cover. The power supply is also
delivered with a Basic Relief Bracket, similar to the Basic Relief
Bracket for the SAILOR 500 /250 FleetBroadband BDU /Terminal.
To secure an installation with heavy cables, an optional Extended
Cable Relief Bracket can be purchased and installed.
When mounted vertically the TT-6080A AC/DC Power Supply fulfils
an IP32 rating in areas with more than 42 V, and an IP22 rating in
other areas. This means that the power supply is protected against
intrusion of solid objects (including body parts, like fingers), dust,
water etc.
Figure 2-63: TT-6080A,AC/DC Power Supply

TT-6080A AC/DC Power Supply is delivered as standard with
the SAILOR 500 FleetBroadband system and is optional for the
SAILOR 250 /150 FleetBroadband system.
Training Manual
2.5 Alarm Panel FleetBroadband

The SAILOR 3771 Alarm Panel is primarily used for initiating
Distress andUrgency calls using the FleetBroadband service.
Figure 2-64: TT-3771A Alarm Panel FleetBroadband

The Alarm Panel is supplied with power through the Ethernet
interface using PoE (Power over Ethernet), which is available in
all the FleetBroadband systems, or alternatively from a DC supply
(10.8 - 32 V DC). The DC input is protected against reverse polarity.
The Alarm Panel is used together with a SAILOR 150, 250 or
500 FleetBroadband system and an IP handset designated for
Distress use. A push on the red FB Distress button on the Alarm
Panel initiates a Distress call from the Distress IP Handset. For
further information on the use of the Alarm Panel and the Voice
Distress (Non-SOLAS) system, see the user manual for the Voice
Distress (Non-SOLAS) System.
Figure 2-65: TT-3771A Alarm Panel FleetBroadband, system setup

For information on the FleetBroadband systems and the IP
Handset see the manuals for these products.
Installation
Training Manual
3 Installation
3.1 Content of the package
Figure 3-1: TT-3740A SAILOR 500 FleetBroadband system

The SAILOR 500 FleetBroadband system TT-3740A, not
delivered anymore, includes the following components as standard
delivery:
• TT-3052A Antenna (ADU)
• TT-3738A Terminal (BDU)
• TT-6080 Power Supply
• TT-3674A Cradle for Thrane IP Handset
• User Manual, IP Handset
• 30 m RG214 antenna cable (incl. loose connectors)
Accessory kit:
• Power connector w/ 1.5 m power cable
• I/O connector
• Mounting bolts
• Basic cable support
• User Manual, SAILOR 500 /250 FleetBroadband
• Installation Manual, SAILOR 500 /250 FleetBroadband
• FleetBroadband CD-ROM (SW and manuals)
Options for the SAILOR 500 FleetBroadband system TT3740A:

• TT-3771 Alarm Panel FleetBroadband
• S-67-127570 Grounding Kit
• 403738A-940 Extended Cable Support Kit
64 Chapter 3
Installation
3 Figure 3-2: TT-3740B SAILOR 500 FleetBroadband system

The SAILOR 500 FleetBroadband system TT-3740B, not
delivered anymore, includes the following components as standard
delivery:
• TT-3052B Antenna (ADU)
• TT-3738A Terminal (BDU) alternatively TT-3738A-T19 Terminal
(BDU) 19” Rack version
• 30 m EcoFlex 10 antenna cable (incl. loose connectors)
Accessory kit:
• I/O connector
• Mounting bolts

Training Manual
Figure 3-3: TT3740C SAILOR 500 FleetBroadband system

The SAILOR 500 FleetBroadband system TT-3740C includes
the following components as standard delivery:
• TT-3052C Antenna (ADU)
• 30 m EcoFlex 10 antenna cable (incl. loose connectors)
• Accessory kit:
• I/O connector
• Mounting bolts
Options for the SAILOR 500 FleetBroadband system TT3740C:

66 Chapter 3
Installation
3 Figure 3-4: TT-3742A SAILOR 250 FleetBroadband system

The SAILOR 250 FleetBroadband system TT-3742A includes
• TT-3050A Antenna (ADU)
• 25 m RG223 antenna cable (incl. loose connectors)
Accessory kit:
• I/O connector

SAILOR 250 /150 FleetBroadband Mast Mount Kit
Training Manual
3
Figure 3-5: TT-3744A SAILOR 150 FleetBroadband system
The SAILOR 150 FleetBroadband system TT-3744A includes
• TT-3050C Antenna (ADU)
• TT-3739A Terminal (BDU)
• 10 m RG223 antenna cable
Accessory kit:
• I/O connector

• SAILOR 250 /150 FleetBroadband Mast Mount Kit
3.2 Tools needed

In order to be able to install the SAILOR 500 /250 /150
FleetBroadband, the following tools will be needed:
• Flat-head screwdrivers
• Allen keys (mm)
• Adjustable spanner
• Wire cutter
• Crimping tools
• Multi-meter
• Laptop
Latest version of:
• SAILOR 500/250/150 FleetBroadband software
• Thrane IP Handset software
68 Chapter 3
Installation
3.3 Installation precautions

3.3.1 Radiation hazard
The SAILOR FleetBroadband antennas is radiating RF energy
harmful to the human body. Therefore whenever the system is
powered, make sure that personnel is not near the antenna.
Though it is only when the SAILOR FleetBroadband antenna is
transmitting, and then only in front of the antenna. But as the is not
visible by the antenna to see when it is transmitting and in which
3 direction a whole circle around the antenna should be considered

as a hazard zone.
Bare in mind that the antenna panel can be elevated to below
horizontal as follows:
• SAILOR 500 FleetBroadband = -25º
SAILOR 500 FleetBroadband antennaa are radiating up to
22 dBW EIRP (158.5 W). This translates to a minimum safety
distance of 1.3 m from the antenna based on a radiation level of
10 mW/cm2.
SAILOR 250 FleetBroadband antenna is radiating up to 16.1
dBW EIRP (41 W). This translates to a minimum safety distance of
0.6 m from the antenna based on a radiation level of 10 mW/cm2.
SAILOR 150 FleetBroadband antenna is radiating up to 16.1
dBW EIRP (41 W). This translates to a minimum safety distance of
0.6 m from the antenna based on a radiation level of 10 mW/cm2.
Radiation level Minimum safe distances
SAILOR 500 FB SAILOR 250 FB SAILOR 150 FB
100 W/m 2
0.4 m 0.2 m 0.2 m
10 W/m 2
1.3 m 0.6 m 0.6 m
Figure 3-6: SAILOR FleetBroadband safe distance matrix
3.3.2 Antenna Cable

The table below is indicating recommended coax cable types
and their maximum length for all three SAILOR FleetBroadband
systems. Not all types of the mentioned cables can be delivered
by Cobham SATCOM, so please contact your local cable supplier.
Cable type Absolute maximum length

G02232-D 6m
RG223-D 25 m
RG214/U 50 m
S 07272B-05 95 m
Figure 3-7: SAILOR FleetBroadband recommended coax cables
Training Manual
Check the data sheet available from your local cable supplier that
both the RF attenuation and the DC resistance are kept within the
maximum specified levels:
Antenna cable specification Maximum value

RF attenuation @ 1.6 GHz 20 dB
Modem attenuation @ 54 MHz 4 dB
Modem attenuation @ 36 MHz 3 dB
DC resistance (Looped) 1Ω
3
Figure 3-8: SAILOR FleetBroadband antenna cable specification
Also ensure that the specified minimum bending radius of the NOTE!
Check the instruction from the
antenna cable is respected. If this is not the case, the loss in the cable supplier.
cable will increase.
3.3.3 Obstruction
Place the antenna with a free line of sight towards the satellite in
all directions to make sure that there is maximum reception of the
satellite signal. Do not place the antenna close to large objects
that may block the signal.
The antennas are rotating 360º in azimuth and down to -25º
elevation for the SAILOR 500 FleetBroadband and down to -60º
elevation for the SAILOR 250 /150 FleetBroadband, when pitching
and rolling, to allow the continuous pointing towards the satellite in
heavy sea states.
The amount of degradation of the signal depends on the size of
the obstruction and the distance from the antenna. As a rule of
thumb, any obstruction that subtends an angle of less than 3º at
the antenna is not seen as an obstruction and has limited effect.
The table below provides a guideline for obstruction sizes and
maximum distance to the object, which will cause only limited
degradation, as the angle will be less than 3º.
Distance to obstruction Width of obstruction

3m 16 cm
5m 26 cm
10 m 52 cm
20 m 104 cm
Figure 3-9: SAILOR FleetBroadband maximum obstruction
3.3.4 Interference
The antenna must be mounted as far away as possible from
the ship’s radar and high power radio transmitters (including
other Inmarsat based systems), because they may compromise
the antenna performance. RF emission from radars might
actually damage the antenna. The RF emission from SAILOR
FleetBroadband antennas itself may also interfere with other radio
systems. Especially other Inmarsat systems and GPS receivers
with poor frequency discrimination are vulnerable to the radiation
generated by the SAILOR FleetBroadband antennas.
70 Chapter 3
Installation
Radar interference
It is difficult to give exact guidelines for the minimum distance
between radar and the SAILOR FleetBroadband antenna because
radar power, radiation pattern, frequency and pulse length/shape
vary from radar to radar. Further, the antenna is typically placed
in the near field of the radar antenna and reflections from masts,
decks and other items in the vicinity of the radar are different from
ship to ship. However, it is possible to give a few guidelines:
Since a radar radiates a fan beam with a horizontal beam width
3
of a few degrees and a vertical beam width of up to +/- 15°, the
worst interference can be avoided by mounting the SAILOR
FleetBroadband antenna at a different level – meaning that the
SAILOR FleetBroadband antenna is installed minimum 15° above
or below the radar antenna. Due to near field effects the benefit
of this vertical separation could be reduced at short distances
(below approximately 10 m) between radar antenna and the
SAILOR FleetBroadband antenna. Therefore it is recommended
to ensure as much vertical separation as possible when the
SAILOR FleetBroadband antenna has to be placed close to a
radar antenna.
Radar distance
Figure 3-10: SAILOR FleetBroadband radar distance

The minimum acceptable separation (d minimum) between a radar
and the SAILOR FleetBroadband antenna is determined by the
radar wavelength /frequency and the power emitted by the radar.
The tables below show some “rule of thumb” minimum separation
distances as a function of radar power at X-band and S-band. If the
d minimum separation listed below is applied, antenna damage is
normally avoided. “d minimum” is defined as the shortest distance
between the radar antenna (in any position) and the surface of the
SAILOR FleetBroadband antenna.
Training Manual
X-band (~ 3 cm / 10 GHz) damage distance

Radar power. d min at d min at d min at d min at d min at d min at
15º vertical 60º vertical 15º vertical 60º vertical 15º vertical 60º vertical
separation. separation. separation. separation. separation. separation.
0 - 10 kW 0.8 m 0.4 m 0.8 m 0.4 m 0.8 m 0.4 m
30 kW 2.4 m 1.2 m 2.4 m 1.2 m 2.4 m 1.2 m
50 kW 4.0 m 2.0 m 4.0 m 2.0 m 4.0 m 2.0 m
Figure 3-11: SAILOR FleetBroadband radar safe distances (X-band)
3
S-band (~ 10 cm / 3 GHz) damage distance
Radar power. d min at d min at d min at d min at d min at d min at
15º vertical 60º vertical 15º vertical 60º vertical 15º vertical 60º vertical
separation. separation. separation. separation. separation. separation.
0 - 10 kW 0.4 m 0.2m 0.4 m 0.2 m 0.4 m 0.2 m
30 kW 1.0 m 0.5 m 1.0 m 0.5 m 1.0 m 0.5 m
50 kW 2.0 m 1.0 m 2.0 m 1.0 m 2.0 m 1.0 m
Figure 3-12: SAILOR FleetBroadband radar safe distances (S-band)

The separation distance for C-band (4-8 GHz) radars should
generally be the same as for X-band radars.
Even at distances greater than “d minimum” in the previous section
the radar might still be able to degrade the performance of the
SAILOR FleetBroadband system.
The presence of one or more X-band radars within a radius up to
100 m could cause a minor degradation of the signal-to-noise ratio
during high speed and data calls. The degradation will be most
significant at high radar pulse repetition rates.
As long as receiving conditions are favourable, this limited
degradation is without importance. However, if receiving conditions
are poor – e.g. due to objects blocking the signal path, heavy
rainfall or icing, low satellite elevation and violent ship movements
– the small extra degradation due to the radar(s) could cause poor
call quality. A voice call might become noisy and perhaps fail while
a data connection might decrease in speed and performance. CAUTION!
The antenna must never be
The presences of S-band radar(s) are unlikely to cause any installed closer to a radar
performance degradation – as long as the minimum distances (d than “d minimum” - even if
minimum) listed in the previous section are applied. experiments show that
interference free operation can
It is strongly recommended that interference free operation is be obtained at shorter
verified experimentally before the installation is finalized. distances than “d minimum” in
the previous section.
Other systems
Inmarsat: Recommended minimum safe distance to other
Inmarsat antennas is 10 m.
GPS receivers: Good quality GPS receivers will work properly
very close to the antenna - typically down to one meter outside
the main beam, and down to a few meters inside the main beam.
However, simple GPS receivers with poor frequency discrimination
could be affected at longer range (typically 10 m). It is always
recommended to test the GPS performance before the installation
is finalized.
72 Chapter 3
Installation
VSAT systems: For optimum performance we recommend a

minimum distance of 3 meters from the BGAN antenna to VSAT
antennas.
Other transmitters: For minimum recommended distance to
transmitters in the frequency range below 1000 MHz. See figure
below.
Figure 3-13: SAILOR FleetBroadband minimum distance to

transmitters
3.4 Installation of the ADU

3.4.1 Antenna grounding
You may ground the antenna using the mounting bolts.
If the antenna cannot or should not be electrically connected directly
to the mounting surface, you can use a separate grounding cable
to make the connection between the antenna and the common
ground to which the terminal is also connected. For example,
you can connect a separate grounding cable if or when vibration
isolators are used at the mounting bolts.
To obtain a good ground connection, the metal underneath the
head of at least one bolt must be clean of insulating protective
coating and corrosion and a serrated washer should be used. After
tightening the bolts we recommend that you seal the area suitably
in order to avoid corrosion of the grounding point.
Use stainless steel bolts and washers.
For further grounding information read Appendix C Grounding and
RF protection in the Installation Manual.
Training Manual
Why grounding?
The reason for grounding the ADU is due to these three (3)
points:
• Safety: Lightning protection of personnel and equipment.
First of all grounding of the ADU is required for safety reasons.
In the event of a lightning strike at the ADU, a proper grounding
of the system will provide a low resistance path to divert the
strike discharge to seawater.
• Protection: ESD (ElectroStatic Discharge) protection of
equipment.
Secondly the ESD protection circuits in the system is relying
on a proper grounding in order to work properly. Otherwise
3
sensitive circuits within the system might be damaged due to
ESD when handling the equipment.
• Performance: Interference free communication between BDU
and ADU.
Finally a proper grounding of the system will enhance RF
immunity thus ensuring interference free modem communication
between BDU and ADU. This modem communication is
essential for the performance of the SAILOR FleetBroadband
system.
3.4.2 Important mounting notes

Line of sight
Place the antenna with free line of sight towards the satellite in all
directions to ensure proper reception of the satellite signal. Do not
place the antenna close to large objects that may block the signal.
Water intrusion
After having connected the antenna cable to the antenna - ensure
that the connector assembly is properly protected against seawater
and corrosion. As a minimum, use self-amalgamating rubber.
If possible, install the radome such that direct spray of sea water
is avoided.
Make sure that the gasket between top radome and bottom radome NOTE!
is properly in position and is intact. Do not close the drainage
holes of the antenna with
It is recommended not to use pneumatic tools for cleaning the silicone, glue, foam or other
radome, especially at a short distance and directly at the split materials, as water from the
between top and bottom and directly into the drainage holes. inside of the antenna have to
be able to be drained out.
Make sure the requirements to drainage are met.
74 Chapter 3
Installation
Condensation
In some cases there will be condensation inside the radome.
The gasket in the bottom center of the SAILOR FleetBroadband
antenna ver. A & B is designed to lead any water away from the
radome.
Make sure this draining gasket is not blocked. If the SAILOR 500
FleetBroadband antenna is mounted on a pole, make sure the
pole is hollow inside and open at the bottom, allowing water from
the gasket to escape and providing ventilation for the antenna.
3
If the SAILOR 500 FleetBroadband antenna is mounted on a flat
surface, use 10 mm spacers (washers) at each bolt so that the
gasket in the center of the antenna bottom is free and water can
escape.
The SAILOR 500 FleetBroadband antenna ver. C is equipped with
a dranage tube which should not be bended, but remain straight
and free of the platform to allow dranage of any condensation.
Vibration
Install the antenna where vibrations are limited to a minimum.
Always use all 4 screws when installing. It is recommended to use
screws delivered with the SAILOR FleetBroadband system or else
screws of A4 quality /stainless steel.
3.4.3 Mounting the antenna

Provide a proper platform to install the antenna, that be in the
mast or at a pole or directly at fly bridge /hull etc., some guidelines
have to be taken into consideration.
For the SAILOR 500 FleetBroadband it is:
• The antenna weight is approx. 16 kg, for TT-3052A, approx.
19 kg for TT3052B and approx. 23 kg for TT-3052C, so the
installation point have to be able to carry this weight.
• The flange diameter should have a diameter at least 300 mm
(see figure below) for TT-3052A/B and at least 320 mm (see
figure below) for TT-3052C.
• The antenna is provided all required input /output, through one
(1) interface, which is centred in the bottom of the antenna.
Therefore a center hole for the antenna cable have to be made
(see figure below) in the mounting platform.
• The antenna is fixed to the platform surface by 4 x M10 studs
(part of the delivery). Insert the shortest threaded piece of
the bolt into the antenna (ver. A) base. The antenna (ver. B
& C) is delivered with M10 bolts, which have to be inserted
into the bushing minimum 10 mm 1nd maximum 25 mm). As
there are no heading of the antenna, it is not important how the
configuration of the four holes for the bolts are positioned (see
figure below).
• The antenna (ver. A & B) is equipped with drainage hole, well
protected versus direct water injection, at the center of the
antenna bottom, and therefore either the hole in the platform
should be able to drain out the water from the antenna or the
antenna have to have a clearance at about 10 mm from the
Training Manual
platform by means of spacers (see figure below), not included

by delivery and not available from Cobham SATCOM. The
antenna (ver. C) is equipped with a dranage tube that have to
be positioned outside the mounting platform.
There are no wire restraints on the antenna components, so it is
not necessary to remove the antenna dome for the installation.
Figure 3-14: TT-3052A Footprint Figure 3-15: TT-3052B footprint.
Figure 3-16: TT-3052C Footprint
Figure 3-17: TT-3052A and TT-3052B spacer for water drainage

For the SAILOR 250 FleetBroadband and the SAILOR 150
FleetBroadband it is:
• The weight of the antenna is approx. 4 kg, for both TT-3050A
and TT-3050C, so the installation point have to be able to carry
this weight.
76 Chapter 3
Installation
NOTE! • It is recommended to use our Mast Mount Kit, available from

The Mast Mount kit is not a our eShop.
part of the standard deliver, but
have to be ordered /purchased
separately.
NOTE!
The SAILOR Mini-M Mast
3
Mount Kit can not be used,
though looking rather similar,
as it is not strong enough
for the SAILOR 250 /150
FleetBroadband ADU.
Figure 3-18: SAILOR 250 /150 FleetBroadband Mast Mount kit
Training Manual
Figure 3-19 and 3-20: SAILOR 250 /150 FleetBroadband ADU on Mast Mount kit
• Alternatively a platform should have a diameter at least 200
mm (see figure below).
• The antenna is fixed to the platform surface by 4 x M6 bolts.
As there are a heading of the antenna, make sure that the
configuration of the four holes in the platform, for the bolts, are
positioned so the “FORE” “AFT” markers in the bottom of the
antenna is able to point towards these directions (see figure
below).
Figure 3-21: TT-3050A and TT-3050C footprint

Make sure that the antenna cable connector is fitted before the NOTE!
antenna is mounted in its position. It is recommended not to
use water jet for cleaning the
Having connected the antenna cable to the antenna - ensure that radome, specially at a short
the connector assembly is properly protected against seawater distance and directly at the
and corrosion. As a minimum, use self-amalgamating rubber. split between top and bottom
radome, draining valve and
There are no wire restraints on the antenna components, so it is antenna cable connector.
not necessary to remove the antenna dome for the installation.
78 Chapter 3
Installation
3.5 Installation of the BDU /Terminal

CAUTION!
If the BDU /Terminal is installed 3.5.1 Where to install?
in a location where the ambient
temperature may exceed As the name it self is stating, BDU, the unit have to be installed
+50ºC, we are recommending indoor and must be placed in a ventilated area with free space
to place the BDU /Terminal around all sides of the unit, except the bottom side, to apply
where unintentional contact is
avoided.
adequate air flow coolant. The ambient temperature at an operating
BDU /Terminal should be between -25ºC and +55ºC.
If the maximum ambient
3
temperature does not exceed The BDU /Terminal and all the external units (IP Handset, IP
+50ºC, the BDU /Terminal can Handset Cradle, Alarm Panel and Power Supply) delivered by
be placed in a public area. Cobham SATCOM, must be placed with a minimum safe distance
of at least 1.25 m to magnetic steering compass.
3.5.2 How to install

The BDU /Terminal can mounted horizontal or vertical, on the bulk
head or on the desk /shelf or under the desk /shelf, as long as
there are free space around the BDU /Terminal (minimum 5 cm to
all sides) to be able free airflow for coolant of the BDU /Terminal.
Before installing the BDU /Terminal on the bulk head /desk/shelf,
install the Supplied Basic Cable Support on the bottom side of the
BDU /Terminal.
NOTE!
The TT-3739A SAILOR 150
FleetBroadband BDU /Terminal
also can be equipped with this
Basic Cable Support.
Figure 3-22: TT-3738A BDU /Terminal with Basic Cable Support

The purpose of the Basic Cable Support is a relief of the cables,
to prevent that all tension from the cables connected is put to the
connectors or connections of the BDU /Terminal. The cables are
to be fixed to the “teeth” of the Basic Cable Support with cable-
ties.
Training Manual
Installation of the Basic Cable Support

Install the Basic Cable Support to the BDU /Terminal before
installing the BDU /Terminal to its location.
1. Remove the two (2) rubber feet from the bottom of the BDU
/Terminal, at the connector panel end (the mounting bushings
are underneath the rubber feet.
2. Fastening the Basic Cable Support to the two (2) revealed
bushings, using the two (2) delivered M4 x 6 mm countersunk
screws.
Figure 3-23: Basic Cable Support installation

As an option an Extended Cable Support kit can be ordered, and
here the BDU /Terminal are installed directly on the Extended
Cable Support. In that case the Basic Cable Support is not to be
installed.
NOTE!
The TT-3739A SAILOR 150
FleetBroadband BDU /Terminal
can not be installed on the
Extended Cable Support.
Figure 3-24: TT-3738A BDU /Terminal on Extended Cable Support

The purpose /benefit of the Extended Cable Support is again to
put a relief on the cables. But also extend the two (2) analogue
ports and the one (1) ISDN port from RJ11 /RJ45 to terminal joints
with screws. Last the kit also provide an antenna cable adaptor
from TNC-connector to N-connector.
80 Chapter 3
Installation
Installation of the Extended Cable Support.

Install the Extended Cable Support to the BDU /Terminal before
installing the BDU /Terminal to its location.
1. Remove the wing nut of the BDU /Terminal from the grounding
screw.
2. Fasten the Extended Cable Support to the BDU /Terminal,
from the bottom side, with the screws provided in the Extended
Cable Support kit.
3. Replace the wing nut on the grounding screw.
3 4. Install the “pig-tail” adaptor between the BDU /Terminal TNC

connector and the cable support of the Extended Cable
Support.
5. If needed, install the two (2) 2-wire adaptors between the two
(2) analogue ports of the BDU /Terminal and RJ11 ports on
the interface board of the Extended Cable Support.If needed,
install the one (1) 4-wire adaptor between the ISDN port of the
BDU /Terminal and the RJ45 port on the interface board of the
Extended Cable Support.
The SAILOR 500 /250 FleetBroadband 19” rack mounted BDU
/Terminal fits into a 19” Rack with 1U (unit) height, and in depth
minimum 450 mm (inclusive Cable Relief Bracket) which is fitted
directly to the rear side of the BDU /Terminal.
Figure 3-25: TT-3738A-19 BDU /Terminal with Basic Cable Support
3.5.3 Antenna cable grounding

At the BDU /Terminal end of the antenna cable it is strongly
recommended to ground the antenna cable.
• If the SAILOR FleetBroadband BDU /Terminal is not installed
on the Extended Cable Support it is strongly recommended to
connect the antenna cable to common ground at the BDU /
Terminal end. By use of a short coax cable (pig-tail adaptor)
from the BDU /Terminal to the grounding point, where the “pig-
tail” adaptor is connected to the antenna cable.
Training Manual
NOTE!
For SAILOR 500 /250 /150
FleetBroadband system the
Grounding kit have to be
purchased from our eShop as:
S-67-127570.
Figure 3-26: SAILOR FleetBroadband BDU /Terminal, Grounding kit

Figure 3-28: S-67-127570, Grounding kit
3
1. Ground wire to BDU /Terminal wing nut.
2. Grounding block.
3. “Pig-tail” adaptor.
4. Antenna cable to /from ADU.
• If the SAILOR FleetBroadband BDU /Terminal is installed on
the Extended Cable Support, the TNC connector is grounded
through the Cable Support, which again must be connected to
hull or common ground.
3.5.4 BDU/Terminal grounding

The BDU /Terminal in all configurations (for all SAILOR
FleetBroadband systems) have to be provided ground /hull directly
to the wing nut of the BDU /Terminal.
Figure 3-27: SAILOR FleetBroadband BDU /Terminal, power and ground

Why grounding?
The reason for grounding the BDU /Terminal is due to these two
(2) points:
• Protection: ESD (ElectroStatic Discharge) protection of
equipment.
The ESD protection circuits in the terminal rely on proper
grounding of the system in order to work properly. Otherwise
sensitive circuits within the terminal might be damaged due to
ESD when you are handling the equipment.
82 Chapter 3
Installation
• Performance: Interference free communication between BDU

/Terminal and ADU.
A proper grounding of the system will enhance RF immunity thus
ensuring interference free modem communication between
BDU /Terminal and ADU. This modem communication is
essential for the performance of the SAILOR FleetBroadband
system.
3.5.5 BDU /Terminal power connection
3
The SAILOR FleetBroadband systems need to be connected
to nominal input power 12VDC /24 VDC (10.5 - 32 VDC; 14A -
5.5A).
Whether the SAILOR FleetBroadband system is connected to the
vessels own DC supply or to a Power Supply, this power delivery
should be stable and noise free.
The length of the power cable depends on the type of cable used
and the source impedance of the DC power installation in the
vessel.
The maximum allowed source impedance depends on the
utilization of the power range of the terminal DC input (10.5 -
32 V DC; 14 - 5.5 A). Select a power outlet from the DC system
and measure the source impedance of the ship installation
Power connector: as described in “Measuring the ship source impedance” in
Chapter 3 and Appendix B in the Installation Manual.
Connect the power cable
• Connect the delivered power cable (length = 1 m) to the
supply power of the vessel or a Power Supply, according the
recommendation in the previous chapter.
Figure 3-26a: Power connector
Power connector pin-out

Pin Function Colour
A1 V in+ Red
Figure 3-29: SAILOR FleetBroadband power cable
A2 V in- Black
1 NC (Black) • If the delivered cable is not long enough, a terminal point
have to be connected and the cable has to be extended
2 Remote Green
from here (according the recommendation in the previous
On/Off
chapter).
3 NC (Brown)
• The cable delivered with the SAILOR FleetBroadband 19”
4 NC (Red)
Rack BDU /Terminal is slightly different as the two (2) wires
5 Remote Orange (green and orange) for Remote On/Off is extracted directly
On/Off from the power connector (see connection description of
Figure 3-30: Power connector pin-out
these in next sub-chapter “Connecting a Remote On/Off
switch”).
Training Manual
Figure 3-31: SAILOR FleetBroadband BDU /Terminal, power and ground

• Connect the D-sub connector on the power cable to the DC
input port of the BDU /Terminal.
Connecting a Remote On/Off switch
The BDU /Terminal is equipped with a Remote On/Off function.
Only the SAILOR FleetBroadband 19”Rack BDU /Terminal is
3
delivered with a switch, is already installed and only need to be
connected. For all other SAILOR FleetBroadband BDU /Terminals
a switch have to be provided locally (it is not a part available from
eShop).
Figure 3-32: SAILOR FleetBroadband BDU /Terminal, power and Remote On/Off switch
By installing the switch, which can “short-circuit” the Remote On/
Off pins (pin 2 and pin 5) of the power connector /cable, the BDU /
Terminal can be powered on and off other places than on the BDU
/Terminal. The BDU /Terminal Power ON/Off switch have to be set
to On inputting 24 VDC (nominal power) to the BDU /Terminal.
• When the switch is opened (not “short-circuit”), the BDU /
Terminal is in On.
• When the switch is closed (“short-circuit”), the BDU /Terminal
is in Off.
In the SAILOR FleetBroadband 19” Rack BDU /Terminal a switch
is already installed on the front side of the unit and wired up inside
the unit to a set of terminals on the rear side. Here the two (2)
extracted wires of the Power cable is to be installed.
Figure 3-33: SAILOR FleetBroadband 19” Rack BDU /Terminal, power and Remote On/Off switch
84 Chapter 3
Installation
3.6 Installation of the AC/DC Power

Supply
Figure 3-34: SAILOR AC/DC Power Supply, block diagram

The SAILOR AC/DC Power Supply contains an input filter followed
by a rectifier and a boost converter producing the unregulated DC
voltage: this will be lead through a transformer and a output filter
for an output voltage at 28.7 - 31.2 VDC 0 - 11A. The output DC
voltage is galvanic isolated from the input voltage and chassis
(ground).
The SAILOR AC/DC Power Supply has automatic selection of
input voltage, and is equipped with an input fuse at 6.3A, an On/
Off switch with lamp and two (2) 30A fuses securing the battery
input.
The SAILOR AC/DC Power Supply can be installed in a 1U rack
mount in the hight, but is not delivered with, or as option able to
get delivered, rack mount. It have to be fixed (screws or double-
sticky tape) to a plate in teh rack.
Training Manual
Figure 3-35: SAILOR AC/DC Power Supply, drill plan

How to install
The SAILOR AC/DC Power Supply can be mounted vertical or
horizontal. When mounted in vertical position, with the connector
panel pointing downwards, the unit fulfils IP32 in areas with more
than 42 V and IP 22 in other areas.
To ensure adequate coolant of the SAILOR AC/DC Power Supply,
an unobstructed space of minimum 5 cm must be maintained
around all sides of the unit, except the bottom side.
• Installed the delivered Cable Support bracket on the surface
(bulk head or desk) so the “comb” sticking out in front of the
connector panel.
• Mount the delivered four (4) bolts M6x55 (DIN912 Unbraco) or
the delivered four (4) screws in the mounting holes.
• Remove the protective cover to gain access to the connections
for the cables by removing the two (2) Torx 8 screws, safe the
screws for later use.
86 Chapter 3
Installation
3
Figure 3-36: SAILOR AC/DC Power Supply, protection cover
NOTE!
The SAILOR AC/DC Power
• Connect the mains power cable (100 - 240 VAC) and ground to
Supply is fused by a 6.3A fuse, the connector marked Mains AC.
located to the right of the On/
Off switch.
• Wire size: ≤ 2.5 mm2.
Figure 3-37: SAILOR AC/DC Power Supply, interface

• Remove the U-shaped cut-out, for this cable run, from the
protective cover.
• Connect the output cable (28.7 - 31.2 VDC) and ground to the
connector marked DC1.
• Wire size: ≤ 6 mm2.
• Maximum load: 30A.
protective cover.
• If needed /wanted, connect emergency battery power cable (24
NOTE!
The SAILOR AC/DC Power
V) to the connector marked BATTERY (please bare in mind
Supply is fused by two (2) 30A that this is not according to the GMDSS regulation).
fuses (one for battery+ and • Wire size: ≤ 6 mm2.
one for battery-), located to the
right of the protective cover. • The battery input is protected versus reversed polarity.
protective cover.
Training Manual
3
Figure 3-38: SAILOR AC/DC Power Supply, alarm circuit.
• If needed /wanted, connect wiring for alarm output, to an
external alarm source (relay, lamp, buzzer), to the connector
marked AC ALARM.
3.7 Installation of the Thrane IP

Handset
The wired Thrane IP Handset connects to the cradle with a coil
cord. The IP Handset cradle connects with a fixed LAN cable to
a LAN port with PoE (Power over Ethernet) on a the SAILOR
FleetBroadband BDU /Terminal or a switch (not provided by
Cobham SATCOM). The Thrane IP Handset is powered directly
from the LAN (PoE) interface.
Figure 3-39: TT-3672A Thrane IP Handset

88 Chapter 3
Installation
How to install
Follow the procedure for installation, of the Thrane IP Handset
Cradle and the Thrane IP Handset, here:
• A LAN (CAT5) cable have to be installed into the IP Handset
Cradle by:
Figure 3-40: TT-3674A IP Handset Cradle, installation

• Remove the two (2) screws holding the centre cover in the
bottom of the cradle and take off the cover.
• Connect the coil cord from the Thrane IP Handset to the
cradle connector marked J103. Then fit the cable relief,
mounted on the coil cord, into the groove at the cable exit.
• Then install the external LAN cable by connecting it to the
connector marked J102 in the cradle. This is the cable to be
connected to the SAILOR FleetBroadband LAN interface 1 -
4 (1 - 2 on the BDU /Terminal for Sailor 150 FleetBroadband)
or an Ethernet switch LAN (PoE) interface.
• Alternatively connect the wires of a LAN cable to the
terminal block, in the cradle, marked J101. A text next
to the terminal block indicates signal input/output of the
connectors.
• Install the cable relief at the cable exit.
• Re-install the cover and fasten the two (2) screws.
• Install the Cradle on the wall or a desktop with the three (3)
screws, fitting in the holes of the cradle.
Training Manual
3.8 Installation of the Alarm Panel

FleetBroadband
3.8.1 Connectors
Overview
The drawing below shows the connectors on the Alarm Panel.
3
Ethernet Power
Figure 3-41: TT-3771A Alarm Panel, connectors
3.8.2 LAN (PoE) interface
Overview
There is one Ethernet (10/100 MB) connector on the rear panel of
the Alarm Panel, used for communicating with the FleetBroadband
terminal.
The interface supports PoE (Power over Ethernet), which means
the Alarm Panel can be powered from the FleetBroadband
NOTE!
terminal through the Ethernet. When you are using PoE to power If you are using PoE, the
the Alarm Panel, the DC input is disabled and the DC power cable Remote on/off function is
is optional. (may be used for backup). disabled.
Pin-out
The figure and table below show the connector outline and pin
assignments.
90 Chapter 3
Installation
Pin function RJ-45 Female

Pin 10/100 10/100 mixed DC &
number DC on spares data
1 Rx+ Rx+ DC+ (PoE)
2 Rx- Rx- DC+ (PoE)
3 Tx+ Tx+ DC- (PoE)
4 DC+ (PoE) unused
5 DC+ (PoE) unused
3 6
7
Tx-
DC- (PoE)
Tx- DC- (PoE)
unused
8 DC- (PoE) unused
Figure 42: Ethernet Connector Alarm Panel, Pin configuration
3.8.3 DC Power input (optional)
Overview
NOTE! The DC Power input connects to a DC supply with 24 V DC
When you are using PoE, the nominal (10.8 to 32 V DC). The interface also has a “remote on/
DC input is disabled and the off” function.
state of the input pins and the
power cable is ignored. IMPORTANT!
If you are not using PoE and you are not going to use the
remote on/off function, you must connect pin 3 (ON_IN) to pin
2 (DC-) permanently.
The Power connector is a custom connector; a matching cable
with connectoris included in the delivery.
Pin-out
The figure and table below show the connector outline on the
Alarm Panel, pin assignments and wire color in the power cable
delivered with the Alarm Panel.
Front view on
Pin Wire color in Alarm Panel
Pin function
number power cable Panel lock,
4 pin maile
1 DC+ (10.8 - 32 V DC) Red
2 DC- (0 V DC) Black
ON_IN
3 White
(see below)
4 Not connected Blue
Figure 43: Power Connector Alarm Panel, Pin configuration
Remote on/off (ON_IN)

With the Remote on/off function you can switch the Alarm Panel
on and off from a remote location, using a switch. Note that the
Training Manual
Alarm Panel does not have a power button, so it is always on,

unless you use the remote on/off function.
To use the Remote on/off function in the Alarm Panel, do as follows:
1. Connect a switch to the white wire in the power cable (pin 3,
ON_IN, in the Power connector.)
2. Connect the other side of the switch to the black wire in the
power cable (DC- (0 V DC) in the Power connector), so that
pin 3 in the Power connector is connected to DC- (with a
resistance less than 10 kohm when the switch is closed.
• Switch closed: Alarm Panel is on
• Switch open: Alarm Panel is off 3
3.8.4 Cable requirements
Before using the Alarm Panel for the first time, check that all cables
arecorrectly wired and fastened.
Grounding
All cables attached to the Alarm Panel must be shielded.
• The shield of the Ethernet cable must be connected to ship
ground via the FleetBroadband terminal or Ethernet switch to
which the Alarm Panel is connected.
• If the DC power cable is used, the shield of the cable must be
connected to ship ground at the power supply.
Cable requirements
The power cable supplied with your system is 2.5 m long with AWG
16 wires and a custom connector at one end. If you are going to
use another cable or extend the supplied cable, make sure the
cables are dimensioned correctly. When the cable is connected
to the power supply, there must be minimum 10.8 V at the end of
the cable.
The Ethernet cable must be shielded Cat. 5E or higher. Max.
length is 100 m.
3.8.5 Connecting the Alarm Panel

To connect the Alarm Panel, do as follows:
1. Connect an Ethernet cable to the LAN connector on the Alarm
Panel.
2. If you are using the DC input, connect the power cable to the NOTE!
PWR connector according to the description in DC Power If you are using PoE as your
input (optional) in the chapter 3.7.3 power source for the Alarm
Panel, the DC cable is not
3. Attach the cable(s) with cable straps as shown below required, but may optionally be
connected for backup.
92 Chapter 3
Installation
3
Figure 3-44: TT-3771A Alarm Panel, connecting the Alarm Panel
4. Connect the other end of the Ethernet cable to one of the LAN
connectors on the FleetBroadband terminal or an Ethernet
switch or PoE switch connected to the FleetBroadband
terminal. Note that the below example is a SAILOR 250/500
terminal; if you have a SAILOR 150 terminal, there are only
two LAN interfaces.
Figure 3-45: FleetBroadband terminal, LAN connectors

5. Connect the Distress IP Handset to another Ethernet interface
on the FleetBroadband terminal or a switch in the same
network.
When connected and powered, all the units are automatically set
up to communicate with each other in the Ethernet network.
You must configure the FleetBroadband terminal to enable the
Voice Distress function and to designate an IP Handset for
Distress. For information on how to configure the system, see the
user manual for the Voice Distress (Non-SOLAS) system.
3.8.6 Verifying the installation
Testing the Alarm Panel

You can test the function of the Alarm Panel using the Test button.
NOTE! To test the light and sound indicators in the Alarm Panel, do as
This test only verifies the follows:
function of the Alarm Panel
itself, not of any connected 1. Press and hold the Test button.
equipment nor the total Verify that all light indicators and alarm buttons are flashing.
system. For the total system,
see the next section. 2. While holding the Test button, press any other button, including
the Distress button.
The buzzer sounds to indicate that the pressed button and
the buzzer is working.
Training Manual
3.9 To install the Alarm Panel

3.9.1 General installation requirements
The Alarm Panel must be placed close to the IP Handset
designated for Distress calls. You can mount the Alarm Panel as a
flush-mounted unit integrated in a console, on a desktop or in an
overhead position.
Make sure the Compass Safe Distance 55 cm is maintained.
3.9.2 Mounting the Alarm Panel

The next pages describe how to mount the Alarm Panel on a
3
desktop, in an overhead position and flush mounted in a console.
Desktop mounting
You can mount the Alarm Panel on a desktop using the mounting
bracket.
Figure 3-46: TT-3771A Alarm Panel, desktop mounting

94 Chapter 3
Installation
Overhead mounting
You can mount the Alarm Panel in an overhead position using
the mounting bracket.
Figure 3-47: TT-3771A Alarm Panel, overhead mounting
Mounting the Alarm Panel with the mounting bracket

To mount the Alarm Panel using the mounting bracket, do as
follows:
1. Find a suitable location to
mount the Alarm Panel.
Make sure there is
minimum 80 mm of free
space for cable access
behind the Alarm Panel.
2. Use the four holes to fasten
the mounting bracket to the
mounting surface. Screws
are included with the
mounting bracket.
3. Place the Alarm Panel in the
mounting bracket.
4. Mount the two knobs on the
sides of the bracket, but do
not tighten them yet.
5. Connect the cables.
Training Manual
6. Adjust the angle of the

Alarm Panel to the wanted
position. The bracket can
be adjusted ± 20°.
7. Tighten the two knobs on
the sides of the bracket
when the Alarm Panel is
in the correct position.
Figure 3-48: TT-3771A Alarm Panel, mounting bracket 3

Flush mount
You can mount the Alarm Panel in a flat surface, e.g. in a console,
using the Flush mount bracket and screws included with the Alarm
Panel.
To mount the Alarm Panel in a console, do as follows:
1. Find a suitable location in the console. Check that there is
enough space for the Alarm Panel and an additional 80 mm
space for cable entry.

Figure 3-49: TT-3771A Alarm Panel, flush mount
2. Cut a hole of 89 mm x 108 mm for the Alarm Panel.
96 Chapter 3
Installation
IMPORTANT!
The scale in the below drawing is not 1:1! Do not use it as a
template without checking the dimensions.
3
Figure 3-50: TT-3771A Alarm Panel, flush mount cut out
3. Place the 4 square nuts in the cut-outs on the sides of the
Alarm Panel, two on each side.
4. Ensure that the flush mount gasket is placed correctly on the
Alarm Panel.
5. Fit the Alarm Panel into the cut-out in the console.
6. Mount the flush mount bracket on the back of the Alarm Panel
by mounting the 4 Torx screws through the bracket and into
the square nuts placed in the Alarm Panel.
7. Fasten the 4 Torx screws.
8. Connect the cables as described in chapter 3.7.5
Figure 3-51: TT-3771A Alarm Panel, flush mount installation

Training Manual
3
Interfaces
Training Manual
4 Interfaces
4.1 Antenna Connector
Figure 4-1
4
Antenna cable RF-attenuation at 1660 MHz: max. 20 dB incl.
connector. NOTE!
Connector: TNC female
Antenna cable modem-attenuation at 54 MHz: max. 4 dB.
Antenna cable modem-attenuation at 36 MHz: max. 3 dB.
Antenna cable loop DC-resistance max: 1 ohm.
Also ensure that the specified minimum bending radius is respected.
If this is not the case, the loss in the cable will increase.
Check the instructions from the cable supplier.
Cable Type Absolute maximum length

G02232-D 6m
RG223-D 25 m
RG214/U 50 m
S0272B-05 95 m
Figure 4-2
4.2 L-band output
Figure 4-3
The terminal has an L-Band output for automatic delivery of
maritime broadcast data. Use a coax cable with an SMA connector NOTE!
to connect a broadcast receiver for maritime data to the L-band Connector: SMA female
output.
102 Chapter 4
Interfaces
Figure 4-4
It is important to understand that the FBB only acts an ’antenna’
and the L-band signal is not (to our knowledge) a part of the
Inmarsat I4 setup.
Important:
Check, with the provider of the L-band equipment/signal,
whether the signal is transmittet from the I4 satellites.
4 4.3 Phone/Fax interface
Figure 4-5
The Phone/Fax connectors are RJ-11, 6/4 female connectors. The
NOTE! table and figure below show the pin-out for the connectors.
2-wire telephone interface
Two connectors: RJ-11 female. Pin number Pin function
600 ohm, ITU-T Rec. G. 473,
standard DTMF telephone. 1 -
Supported cable length: up to 2 Not connected
100 meters.
3 Tip
4 Ring
5 Not connected Figure 4-7
6 -
Figure 4-6
Port 1 is the connector closest to the antenna connector, and Port
2 is the connector closest to the ISDN connector.
Making a call
You have different options for making a call:
Short Dial:
If the number is in the phone book of the terminal, you can use the
Short Dial number, which is found in the first column of the phone
book in the web interface.
Training Manual
Example: To call entry number 4 in the phone book,

dial 004 followed by #
Manual Dial:
00 <country code> <phone number> followed by #
Example: To call Cobham SATCOM in Denmark (+45 39558800)
from an analog or ISDN phone, dial 00 45 39558800 #
4.3.1 Configuring the Phone/Fax interface

Select SETTINGS > Phone/Fax from the left navigation pane.
For each Phone/Fax port, set the call type for incoming and
outgoing calls.
4
For Incoming calls, you can select Standard or 3.1 kHz Audio or
both.
If you select both, any device connected to the Phone/Fax interface
will react (ring) on incoming calls.
If you select e.g. Standard, the Phone/Fax interface will only react
on calls made to the Standard phone number.
For Outgoing calls, you can select either Standard or 3.1 kHz
Audio. The selected type will be used by default, if possible, for
any outgoing call.
Fax machines must use 3.1 kHz Audio.
You can override the default setting for outgoing calls by dialing
1* (force the call to Standard) or 2* (force the call to 3.1 kHz
Audio) before the number.
Example:
NOTE!
Services:
Phone: standard voice,
Fax: 3.1khz
Incoming std. voice will ring
port #1
Incoming Fax/3.1khz will ring
port # 2
Figure 4-8
Figure 4-9
104 Chapter 4
Interfaces
4.4 SIM-Card reader

The SIM card is provided by your Airtime Provider. Insert the SIM
card as follows:
1. Open the SIM cover in the

left side of the connector
panel.
2. Insert the SIM card into the SIM

slot.
4
Place the card with the chip
side facing up as shown.
3. Press gently until it clicks.
4. Slide the lock in front of the SIM

card.
5. Close the cover for the SIM slot.

The SIM card is provided by your Airt ime Provider and should be
a FB SIM card.
Training Manual
4.5 ISDN interface
NOTE!
Figure 4-10: Connector panel ISDN interface One connector:
The terminal has one ISDN connector for connecting an ISDN RJ-45 female.
Conforms with CCITT I.430,
phone or an ISDN modem. The ISDN interface supports 56/64 ETSI ETS300012, ANSI
kbps data rate. It is configured as the network side, i.e. Rx is an T1.605.
4
input and Tx is an output
Pin number Pin function

1 TxD+input
(Positive PoE)
2 TxD-input
(Positive PoE)
3 RxD+output
(Negative PoE)
4 Not connected
5 Not connected
6 RxD-output Figure: 4-12 ISDN
(Negative PoE) connector
7 Not connected
8 Not connected
Figure 4-11: Connector configuration, ISDN
Making a call
You have different options for making a call:
Short Dial:
If the number is in the phone book of the terminal, you can use the
Short Dial number, which is found in the first column of the phone
book in the web interface.
Example: To call entry number 4 in the phone book,
dial 004 followed by off-hook key.
Manual Dial:
00 <country code> <phone number> followed by
off hook key
Example: To call Cobham SATCOM in Denmark (+45 39558800)
from an analog or ISDN phone, dial 00 45 39558800
106 Chapter 4
Interfaces
4.5.1 Configure the ISDN interface

Incoming calls.
NOTE!
Connected devices will only
You can select Standard, 3.1 kHz Audio, UDI and/or RDI. Note
receive incoming calls with the that SAILOR 250 FleetBroadband only supports Standard or 3.1
call types that are selected kHz Audio. Set the MSN (Multiple Subscriber Number) numbers
here. that are to be assigned to each call type.
For example, if only Standard
is selected, and a G4 fax call Note that this setting only applies to the call type selected above
(using call type UD I) arrives, a the MSN number, and only if the connected device supports
fax connected to the ISDN port the call type used. You have the following options with the MSN
will not receive the incoming
call.
numbers:
<None>. No MSN numbers are used.
An incoming call is accepted in all devices connected to this port.
4
1*, 2*, 3* or 4*: If, for example, you select 1* at Standard call
NOTE! type, an incoming Standard call is accepted by all devices that
If you set an MSN number to are programmed with the number 1* and connected to the ISDN
anything other than <None>, interface.
connected devices must be
programmed with these MSN 0401 - 0408: These are local numbers for separate devices
numbers. connected to the ISDN interface.
An incoming call is accepted by devices that are programmed with
the selected number and connected to the ISDN interface.
You can combine the MSN settings.
Outgoing calls.
NOTE!
You can override the call type
Automatic, the call type will be determined by the calling device.
setting for outgoing calls by (voice = standard voice, Data = UDI)
dialing one of the following
prefixes before the number:
Standard, all outgoing calls, except UDI/RDI, will use the call type
• 1* (force the call to Standard) Standard. If you make a 3.1 kHz Audio call it will be converted to
• 2* (force the call to 3.1 kHz
a Standard call.
Audio) Outgoing UDI or RDI sessions will be not be influenced by this
setting.
3.1 kHz Audio, all outgoing calls, except UDI/RDI, will use the call
type 3.1 kHz Audio. If you make a Standard call it will be converted
to a 3.1 kHz Audio call. Outgoing UDI or RDI sessions will be not
be influenced by this setting.
Example:
NOTE!
Services:
Phone: standard voice
Fax: 3.1khz
Modem: 64kbps - UDI
(56kbps—RDI)
Incoming std voice will ring
0401
Incoming fax/3.1kh will ring
0402
Figure 4-13
Training Manual
Figure 4-14
4.6 LAN Interface, VOIP
4
Figure: 4-15
Connection IP handset to the LAN interface
To connect the Thrane IP Handset to the terminal, do as follows:
Connect the cable from the IP cradle to one of the LAN connectors
on the terminal, preferably port 1. In case of insufficient power to
the LAN PoE the LAN ports are prioritized, so that port 1 is the
last to be shut down. Note that the handset and terminal must
be set up to be able to communicate with each other. For further
information, refer to the user manual for the handset.
Setting up the IP handsets:
NOTE!
Select SETTINGS > IP handsets. Default SIP profile—0501
Select Edit next to a handset to change the password of the Incoming 3.1khz call disabled.
handset. Remember that you must enter the same password and
local number (user name) in the IP handset.
Figure 4-16
Add a IP handset; NOTE!
The first IP handset that is
Select – Settings / IP handsets connected to the LAN interface
on the terminal is automatically
The Username / Number is predefine to 0501-0516 registered in the terminal and
Default to set incoming / outgoing calls, select “call settings” assigned the local number
0501 and password 0501.
The IP handset will show as user “0501” password “0501” Change SIP profiled 0502—0516
password To connect IP handset #2 must be setup in handset and
Connect the IP handset to the terminal. Find the IP address of the terminal SIP profiles , though
a setting up in the IP Handset
new IP handset, open LAN / Network devices. can make this procedure
The IP handset #2 will show in the Network device list. [linieskift automatic, so that the following
IP Handsets will automatically
be given the next free number
(0502 - 0516). See more in
setting up the IP Handset in the
Thrane IP Handset Manual
108 Chapter 4
Interfaces
og mellemrum] The terminal has a built-in DHCP server which can

be used to dynamically assign IP addresses to devices connected
to the terminal.
(In above it is 192.168.0.9) Configure the new IP handset (All T&T
IP handset is default configured as 0501 – 0501
Using a browser enter the IP address for the new IP handset i.e.
192.168.0.9. This will open the WEB MMI for the IP handset.
Select SIP Settings
Click “edit” and change the User name to 0502 -> 0516
(The Users in the SIP server is predefined to 0501 – 0516)
Enter a password (in this case 0502)
Click “save” to save the entry.
4 Setting the call types for IP handsets

Select SETTINGS > IP handsets > Call settings.
For each handset, select the call types you want to enable for
incoming and outgoing calls.
Figure 4-17
For Incoming calls, you can select Standard or 3.1 kHz Audio
or both. If you select both, the handset will react (ring) on any
incoming call. If, for example, you select Standard, the handset
will only react on calls made to the Standard phone number.
For Outgoing calls, you can select either Standard or 3.1 kHz
Audio. The selected type will be used by default, if possible, for
any outgoing call.
Setting up the IP handset compatibility
If you are connecting your Thrane IP Handset(s) to the terminal
through a separate router with NAT, you must use IP handsets with
software version 1.8 or newer and set up the handset compatibility
in the web interface of the terminal as described below.
To see the software version of your IP handset, select
Figure 4-18
MENU > Status > Software version in the IP handset.
To change the IP handset compatibility:
Select Settings > IP handsets > Server settings.
Version 1.8 or newer and use IP handsets with software version
1.8 or newer. If you are connecting your IP handset(s) directly to
the terminal or through a switch without NAT, select Version 1.7
or older. In this case you can use IP Handsets with any software
version.
Training Manual
IP handser WEB MMI:

Select Configure next to a handset to access the built-in web
interface of the IP handset. The web interface of the IP handset
opens. It is very similar to the web interface of the terminal, but
has a handset icon in the top left corner. With the web interface
of the IP handset you can access the internal settings of the IP
handset. For further information, refer to the user manual for the
IP handset.
To add a new SIP profile in the IP handset:
Figure 4-19
Add a new SIP profile if you want to connect the SIP client of the
IP Handset to a SIP server. You need to enter several network
specific values so the IP Handset can communicate with the SIP
server. The IP Handset can hold up to 10 profiles.
4
Profile name, SIP server and port, User name, Password, Codec
priority, STUN server, Reregister interval,
To add a new SIP profile:
Select Options (left select key).Type in the name to use for the
new profile and select OK.
Select Edit. Server name / IP:, select Edit again.
Type in the server name (URL) or IP address and select OK.
Type in the port number for the SIP server and select OK.
Select Back to continue the set up of the remaining parameters.
User name: When connecting to a BGAN terminal, the user name
should be the same as the local number for the handset. NOTE!
If Multi-voice is enabled, the
Password: When connecting to a BGAN terminal, the password local exchange function is not
must match the IP Handset password entered in the terminal. available.
Codec priority: Select the codec type that should have the highest
priority. You may select G.711 or G.729 A/B.
STUN server: If your SIP telephony installation requires a STUN
server name, you can enter it here.
Use ut.bgan as stun server name when using the 1.8 server
version. (Handset connected behind a NAT router)
Reregister every: This settings sets the time interval in which
the IP Handset registers with the SIP server it is connected to. If
the SIP server is the BGAN terminal, you don’t need to change
this setting. The interval is set to 120 seconds (default). The
maximum value is 86400 seconds (24 hours). If the IP Handset
registers with the SIP server over a satellite connection or other
telecommunications network you may set this time interval to a
larger value to avoid unintended use of bandwidth.
110 Chapter 4
Interfaces
Example:
NOTE!
IP handset 0501
Rings on incoming standard
voice.
IP handset 0502
Rings on incoming standard
voice. Figure 4-20
Incoming 3.1khz audio will not
make any of the ip handsets
ring.
Outgoing call will be standard
voice.
4
Figure 4-21
Figure 4-22
4.6.1 Local exchange

If the local exchange is not used, the default behavior is such that
NOTE!
If Multi-voice is enabled, the incoming calls will cause all connected phones to ring. If you want
local exchange function is not to be able to call a specific phone connected to the terminal, you
available. must use the local exchange function. With this function enabled,
when you dial the mobile number of the terminal, a recorded
message guides you to dial the number for the local phone you
want to call. Your call is then transferred to the requested phone.
To set up the local exchange, do as follows:
Select SETTINGS > Common > Local exchange from the left
navigation panel.
Type in the default number.
Incoming calls are transferred to this local number if the caller
dials * after calling the mobile number, or the caller dials nothing
after the recorded message.
Figure 4-23
Select the call types you want to direct to the local exchange.
For example, if you use 3.1 kHz Audio for a fax machine only, you
do not want to use the local exchange for 3.1 kHz Audio.
If no call type is selected, the local exchange function is disabled.
Training Manual
Example:
NOTE!
All incoming call to standard
voice msisdn will be answered
by the ’local exchange.
Default 0501 will ring if * is
dialed or after 10 sec.
All incoming to the 3.1khz
audio AMSISDN (fax) will
not be answered by the local
exchange.
Figure 4-24
4.6.2 Supplementary services

Setting up call services
4
The setup of call services is also common for all interfaces.
In the web interface you can set up the following supplementary
services:
• Call forwarding
• Call barring
• Call waiting
• Line identification
• Closed user group Figure 4-25
Note that, depending on the network, some of these call service
settings may prevent others from being activated.
The settings apply for all connected devices using a circuit-
switched service.
Call forwarding
You can set up the terminal to automatically forward incoming calls
to another phone number. This information is saved in the BGAN
network so it is available when the call cannot be put through and
must be forwarded. This service is usually set up by the airtime
provider.
Select SETTINGS > Common > Call forward from the left
navigation pane.
Click OK next to Read current settings to display the phone
numbers for call forwarding for the subscription. These numbers
are operator controlled and come with your airtime subscription
(default). A message saying
Operation in progress, please wait is displayed.
For each call type, select Enabled next to the situation(s) in which
you want to forward incoming calls.
Figure 4-26
112 Chapter 4
Interfaces
Next to the enabled items, you can type in the phone number you
want to forward the call to.
If you have selected Forward if no reply, select from the drop-
down list the period of time the system should wait before
forwarding the call.
Call barring
Do as follows to bar incoming and/or outgoing calls to and from
the terminal:
Select SETTINGS > Common > Call barring from the left
navigation pane.
Click OK next to Read current settings, to make sure the page is
updated. For each call type, select which calls should be barred. In
the Barring PIN field, type in the PIN for your call barring setup.
4
Figure 4-27
Call waiting
You can set up whether or not you want to receive notification of
waiting calls while you are making a call or transmitting data.
Select SETTINGS > Common > Call waiting from the left
navigation pane.Click OK next to Read current settings to make
sure the page is updated.
For each call type, select Call waiting enabled if you want to get
notification of waiting calls while you are making a call or
transmitting data.
Figure 4-28
Line identification
You can set up the terminal to show your number when you are
making a call or transmitting data.
Select SETTINGS > Common > Line identification from the left
navigationpanel. Select Show my number and click Apply.
Closed user group
Your subscription may include one or more closed user groups. A
closed user group is a group of users permitted to make calls to
Figure 4-29 each other but not to users outside the group.
To define the settings for these user groups, do as follows:
Select SETTINGS > Common > Closed user group from the left
navigation panel. Type in your user group number(s) under Group
no.
Your airtime subscription lists your user group number(s).
3. Select which group(s) should be active.
If you select Subscribed, the group(s) included in your subscription
will be Active
To allow outgoing access for the activated user group(s), select
Outgoing Access under SETTINGS FOR ACTIVE CLOSED
USER GROUP.
Figure 4-30 Note that if you selected Subscribed above, this setting will not be
used.
Training Manual
Select Preferential if you want the activated user group to

be selected when a member of a user group does not specify
the group number during call set up. Note that if you selected
Subscribed above, this setting will not be used.
4.7 LAN interface, Data
Pin number Pin function

1 Not
connected
4
Figure 4-31: 2 Not
connected
One power supply powers all four interfaces with a floating 48
3 Rx+(c) input
V DC supply (44 - 57 V DC). Therefore, the interfaces are not
galvanically separated from each other. All Tx signals are DC 4 Tx+(d) output
connected to the Positive PoE Voltage and all Rx signals to the 5 Tx-(e) output
Negative PoE Voltage. The total output power from all 4 interfaces 6 Rx-(f) input
is 7 Not
64 W at 24 V DC power supply connected
8 Not
32 W at 12 V DC power supply
connected
All interfaces can support devices of power class 1, 2 and 3 (4,
7 and 15.4 Watt), as long as the total power consumption does Figure 4-32
not exceed the above limits. If the limits are exceeded, the LAN
ports are prioritized so that LAN port 1 has the highest priority. For
example, if all ports are used and the total power consumption is
too high, port 4 is closed down. In case of power hold-up (failure
on input power), PoE will be turned off.
Figure 4-33: RJ-45 female connector
The terminal has four Ethernet LAN ports with Power overEthernet
(PoE). The Ethernet ports are standard IEEE 802.3 af ports using NOTE!
RJ-45 connectors. Services IP devices:
Standard data.
Streaming data.
4.7.1 Connecting a computer to the LAN interface 8/16/32/64/128/256
Services IP handset:
Connect your LAN cable between the network connector on your CS: standard voice—3.1khz
computer and one of the LAN connectors on the terminal. VOIP: G711—G729
When the computer and the terminal are ready, check the
connection e.g. by accessing the built-in web interface of the NOTE!
Microsoft Internet Explorer:
terminal with your browser. Tools > Internet Options >
You will have to disable the Proxy server settings in your browser. Connections> LAN Settings.
2. Clear the box labeled Use a
proxy server for your LAN.
3. Click OK.
When the proxy server
settings are disabled, close
your browser. You may need
to change this setting back
on return to your Internet
connection.
114 Chapter 4
Interfaces
4.7.2 The Network Management system

With the built-in router functionality the system offers a flexible
use of the data channel of the BGAN service. You can configure
the use of the data channel by defining network user groups
and profiles. The following picture gives an overview over the
parameters involved. The network user group you belong to is
determined by one or more of the following:
• The IP address of the device you are using
• The MAC address of the device you are using
Figure 4-34
• The LAN port you connect to
A connected IP device will automatically be assigned to the default
network user group, if it is not specified otherwise.
4
For specific purposes like video streaming, a server on the
network, a fixed IP address on the connected device or changing
the startup mode of a connection, you must set-up network groups
with specific primary and/or secondary profiles. How to do this is
described in the following sections.
Network User Groups (NUG)
The network management system divides the users of the terminal
into network user groups. Each network user group has a profile
which determines how the users connect to the Inmarsat BGAN
network. The network user groups can allow or restrict certain
services for different users.
You can have up to 11 network user groups and global IP
addresses.
Figure 4-35 Defining a Network User Group
The network user groups determine settings such as:
QoS (Standard/Streaming),
IP addressing (Static/Dynamic)
Internet access mode (Router Mode/Bridge Mode/No Internet
Access)
Identifying a network device
Figure 4-36
The network devices are identified by their IP address, MAC
address and (optionally) device name.
Associating the network user group and the network device
The network classification table determines which devices should
belong to which network user group. When a network device is
connected, the terminal runs through the network classification
table to check if the new connection matches any of the entries
in the table. When a match is found, the terminal establishes a
packet data connection (PDP context) with the settings defined in
the belonging network user group, and the device is ready for use
with the terminal.
Training Manual
Access to the network management settings

Access to the network management settings requires an
administrator password. The default user name is admin and the
default password is 1234.
The administrator can create and manage network user groups
and set up a network classification table defining priorities for
devices, network user groups and LAN ports.
Setting up the network user groups
A network user group, in this context, is a group of network
users sharing the same Quality of Service profile and network
parameters. There are 11 configurable network user groups. For
the Default network user group certain settings are locked to make
sure there is always one functional network user group available.
4
For example, the Default network user group cannot be disabled
and does not allow you to select a Bridge mode connection.
Editing a network user group
Select SETTINGS > LAN > Network user groups.
When you are prompted, enter the administrator user name
and password. The default user name is admin and the
default password is 1234. Type in a name for the group.
Select Enabled or Disabled.
Internet connection
Router mode means the connection will be shared with other
users, and the NAT module of the terminal will make the necessary
address translations. Use this mode if one or more computers are
connected using the LAN interface, and the terminal should act as
a router.
Bridge mode is an exclusive connection, with NAT disabled. Use
this mode together with a network classification entry that selects a
single computer. This mode is not available in the Default network
user group.
No Internet access means no connection to the Internet is allowed.
Use this setting e.g. for IP handsets, where an Internet connection
is not required. The external voice connection is still available; this
setting only affects communication over the Internet.
Dynamic IP address
This is the IP address used externally on the satellite network.
Refer to the next step for Static IP.
If you want to use a static IP address, you must have it included
in your airtime subscription and use that address as follows: Figure 4-37
Leave the Dynamic, do not select Static IP.

Select SIM default.
Type in the APN user name and password from your provider.Your
terminal will then use the static IP address set up for your SIM
card. Static IP is handled by the service provider.
116 Chapter 4
Interfaces
Do not type in a static

IP address in the Static IP address field; a manually typed IP
address will currently not be used by the network.
There are four options for setting the APN. Unless you have special
requirements, it is recommended to use the SIM default, or to set
the common APN to SIM default, and then select Common here.
You have the following options:
Common. The APN is taken from the Common APN defined under
SETTINGS > Common.
SIM default. The APN is taken from the SIM card. If you want to
use a static IP address on the external network, select this option
either here or in the Common setting.
4
Network assigned. The APN is assigned from the network.
User defined. Type in the APN. APNs are provided from the
Airtime Provider.
Figure 4-38
User name: If your APN uses a user name, type in the user name
provided from the Airtime Provider.
NOTE! Password: If your APN a password, type in the password provided
If you have selected and from the Airtime Provider.
started a Streaming connection
as your primary profile, the
Automatic activation: Select whether the profile selected in the
LAN interface will be running next step should be activated automatically or manually.
a Streaming connection until
you stop it or disconnect the
Primary profile
interface. However, if you Select a profile from the Primary scroll list. This profile is used by
select one or more secondary
profiles, you can set up your
this network user group as a first choice, when possible.
traffic flow filter so that it will There are several predefined profiles: Standard, Streaming 8
only use the Streaming profile
for certain types of traffic.
kbps, Streaming 16 kbps, Streaming 32 kbps, Streaming 64 kbps,
Streaming 128 kbps and Streaming 256 kbps (only SAILOR 500
FleetBroadband). Additionally, you can define your own custom
NOTE! profiles.
If you have selected both Secondary profile
a primary and one or more
secondary profiles you must To select more than one secondary profile, press and hold Ctrl or
define a traffic flow filter before Shift while selecting.
you can establish a valid
connection. Managing network devices
NOTE!
A network device, in this context, is an Ethernet hardware device,
Only network devices that runs identified by its unique MAC address.
DHCP are listed here.
Devices running with a static
When a network device with dynamic IP address is connected to
setup will not show in the list. the terminal, it is automatically listed in the Network devices list.
To view the list of network devices, select SETTINGS > LAN >
Network devices.
Locking an IP address to a MAC address
When the device is locked to an IP address, the terminal will
always assign this IP address to the MAC address of this device
(if DHCP is enabled and the Internet connection is not a Bridge
mode connection).
Training Manual
To lock a device to its current IP address, click the link next to

the device. The device is then locked to the current IP address and
added to the list of locked IP addresses at the top of the page.
To unlock a device from the IP address, click Delete next to the
device in the
Using the network classification table
The network classification table is used to define which network
devices, IP addresses and/or LAN ports are associated with which NOTE!
network user groups. By means of the Network
Classification Table a Network
Each entry in the table shows MAC address, IP address, LAN port devices is associated with one
and network user group. or more Network User Groups
When a network device is connected, the terminal runs through the If you leave a field empty, it is
the same as a “wild card” and it
network classification table to check if the new connection matches
4
will be shown as an Asterisk in
MAC address, IP address and LAN port in any of the entries in the Network classification table.
the table. When a match is found, the terminal establishes a PDP Unless you are using a Static
context with the settings of the network IP address, the IP address field
should always be left empty.
user group assigned in the matching entry. The device is now
ready for use with the terminal.
To add a new entry to the table or to edit an existing entry, do
as follows: Select SETTINGS > LAN > Network classification
table.
The network classification table shows which devices are
associated with which LAN ports and network user groups. An
Asterisk (*) is a “wild card”, meaning that any value is accepted.
Click Edit next to the entry you want to edit, or click Add at the
bottom of the list. Click Add next to a network device you want to
use, or type in the MAC address manually at the top of the page.
Select the LAN port and Network user group you want to
associate with the device.
Figure 4-39
Network user groups are created and defined in the Network user
group page.
In the network classification table, click Delete next to the entry
you want to delete.
118 Chapter 4
Interfaces
To change the priority of an entry, click the up or down arrow next

to the entry. Connections are evaluated in the order they are listed.
The first entry (and only the first entry) that matches the properties
of the connected device is applied, meaning that the connection
will be using the settings of the network user group assigned to
that entry.
The Default network user group is always last, so it is only used
if none of the other entries match the properties of the connected
device, or if the other network user groups are disabled.
Example:
NOTE!
User group Captain:
Primary PDP, Std data + QOS
256kbps. Static public IP.
(Bridge Mode)
4 User group Bridge:

Primary PDP, Standard Data.
Dyn. Ip / NAT (Bridge mode)
User group Crew_D:
Primary PDP, Standard Data.
Dyn. Ip / NAT (Router mode)
User group Crew_C
Only internal connection and
VOIP handset to SIP server
(none)
User group Default
Only internal connection.
Figure 4-40
Figure 4-41
Figure 4-42
Training Manual
4.8 DC Input
See Chapter 3.5.5 BDU/Terminal power connection.
4.9 I/O ports
4
Figure 4-43 NOTE!
Do not use the Ringer output
Pin 1: Ringer output if you have enabled Local
exchange. For information on
Pin 1 acts as a built-in switch in the terminal. You can configure Local exchange, refer to the
Pin 1 to be Normally closed or Normally open. User manual.
Pin 2: Warning/Error output
NOTE!
Pin 2 acts as a built-in switch in the terminal. Pin 2 can be used • Normally Closed:
to provide an external signal that indicates active warning/error The internal switch at pin X is
condition(s). You can configure pin 2 to be Normally closed or normally closed (connected
Normally open. to ground). When the function
is activated the switch opens
Pin 3: Mute output (no connection to ground).
When the function is cleared
Pin 3 acts as a built-in switch in the terminal. Pin 3 can be used to the switch is closed again.
provide an external signal that is active during a phone call. The • Normally Open:
signal can be used to mute external equipment. You can configure The internal switch at pin X is
pin 3 to Normally closed or Normally open. normally open (no connection
to ground). When the function
Pin 4: Radio silence input is activated the switch closes
connection to ground). When
Activation of this pin causes the system to assume radio silence, the function is cleared the
i.e. to stop all transmission from the system. The terminal gracefully switch will open.
closes all open connections, and deregisters from the BGAN
network. No transmission is allowed until the pin is deactivated.
NOTE!
You can configure pin 4 to Active low or Active high. • Active low (default): Connect
pin 4 to ground (< 1.2 V DC)
Pin 5/8: Ignition input when it should be activated.
The ignition function can be used to turn on/off the terminal by • Active high: Connect pin
means of an external signal. The external signal that triggers the 4 to ground (< 1.2 V DC).
When it should be activated,
ignition function can be either positive DC voltage or ground. The disconnect it from ground.
ignition function uses pin 5 together with pin 8 (DC in). Connect
the appropriate pin to the ignition switch as follows: indicated in
NOTE!
the Note!- box. • Active high (default): Connect
pin 5 permanently to Ground.
Pin 6: Ground Connect pin 8 to positive DC
voltage (10.5-32 V DC) when
(Non-configurable) Pin 6 can be used as an external connection to the ignition is on. To switch
ground. Pin 6 is connected to Ground inside the terminal. off, disconnect pin 8 from the
positive DC voltage.
Pin 7: DC output
• Active low: Connect pin 8
(Non-configurable) Pin 7 can be used as a DC output. The voltage permanently to positive DC
on pin 7 is 9-15 V and the output can supply up to 50 mA. Pin 7 voltage (10.5-32 V DC).
Connect pin 5 to Ground
can be used as power supply to a relay, ringer or similar. (< 1.2 V DC).
120 Chapter 4
Interfaces
Example:
Figure 4-46: WieCon Type 8513S connector
Pin Connection Default

number confi gurationa
1 GPIO1 Ringer
output,
active high
2 GPIO2 Warning/
Error output
3 GPIO3 Mute output
4
4 GPIO4 Radio
silence input
5 GPIO5 Ignition input
6 Chassis Chassis
GND GND Figure 4-44
7 DC out 9-15 V DC,
50mA
8 DC in (Ignition
input)
Figure 4-47
Figure 4-48
Figure 4-45
Training Manual
4.10 Grounding
Figure 4-43
DC Negative
Actually not a ground but a current-carrying conductor which
carries the same current that flows in the positive conductor. The
4
DC Negative may be electrically connected to seawater (at one
point only, via the engine negative terminal though the shaft and
the propeller) or left completely floating.
Lightning Ground
Ground potential immersed in seawater. Provides a path to ground
lightning strike energy. Please note that this is not a functional part NOTE!
of any other electrical system. Bonding arrangement that ensures Safety:
equal electrical potential for all dissimilar underwater metal parts First of all grounding of the
system is required for safety
and provides galvanic protection by means of sacrificial anodes. reasons. In the event of a
Corrosion System Ground lightning strike at the antenna a
proper grounding of the system
Ground potential immersed in seawater (typically the hull for will provide a low resistance
steel and aluminum vessels). Serves as safety ground (protective path to divert the strike
discharge to seawater.
earth) thus preventing shocks or electrocution in the event of a
fault situation. ESD Protection:
The ESD protection circuits
AC Ground (Protective Earth) in the terminal rely on proper
grounding of the system
Underwater ground potential that is capacitively coupled to in order to work properly.
seawater ground. Typically numerous pieces of bonded underwater Otherwise sensitive circuits
metal parts such as keel (isolated), water tank, engine block etc. within the terminal might be
will act as a capacitive RF ground (that is; no DC connection to damaged due to ESD when
you are handling the
seawater). Often referred to as “counterpoise” for the SSB/HF equipment.
aerial system.
RF Ground (Capacitive)
Underwater ground potential that is electrically coupled to seawater
ground by means of a separate ground plate (e.g. Dynaplate).
Also referred to as “counterpoise” for the SSB/HF aerial system.
RF Ground (Electrical)
Underwater ground potential that is electrically coupled to seawater
ground by means of a separate ground plate (e.g. Dynaplate).
Also referred to as “counterpoise” for the SSB/HF aerial system.
Repair
Training Manual
5 Troubleshooting
5.1 Status signalling
FBB 500 / 250
The SAILOR FleetBroadband system uses event messages and
light indicators to display the status of the system.
Light indicators
The terminal has a number of light indicators, placed in the panel
at the top of the terminal:
• a green/orange Power indicator,
• a green/red/orange Terminal indicator,
• a green/red/orange Antenna indicator, Figure 5-3
• a green Message indicator and
3 LAN indicators for each LAN interface, showing Activity (Green),
5
Link/Speed (Green/Yellow) and PoE (Green/Yellow).
Power indicator
Behavior Meaning
Steady green Power OK
Flashing green The terminal is powering up
Flashing orange The terminal is closing down
Off No power
Figure 5-1 Figure 5-4
Behavior Meaning
Steady green Ready. BGAN registration
completed
Flashing green Please wait - process in
progress. BGAN registration
ongoing.
Orange Warning - temporary
malfunction. User action is Figure 5-5
required.
Red Critical error. Check the event
log. If the problem is in the
SAILOR FleetBroadband
system and you cannot solve
it, contact your distributor and
return the unit for repair if
necessary.
Figure 5-2
126 Chapter 5
Troubleshooting
Antenna indicator
Behavior Meaning
Steady green Tracking. The antenna is ready for use.
Flashing green Please wait - process in progress.
Slow fl ashing: The antenna is starting up.
Rapid fl ashing: Sky scan.
Orange Warning - temporary malfunction. User
Figure 5-10
action is required.
Red Critical error. Check the event log. If the
problem is in the SAILOR FleetBroadband
system and you cannot solve it, contact your
distributor and return the unit for repair if
necessary.
Figure 5-6
Status Antenna indicator Terminal indicator

The antenna is Flashing slowly Flashing green
5
starting up green
The antenna is Flashing rapidly Flashing green
performing a green
Figure 5-11 sky scan
The antenna is Steady green Flashing green
tracking
The terminal is Steady green Flashing green
registering on
the network
The system is Steady green Steady green
registered and
ready for use
Figure 5-7
Message indicator
Behavior Meaning
Flashing green A new SMS message has
arrived.
Off No new message, or the unit is
off.
LAN indicator functions
Behavior Meaning
Flashing green The LAN port is active.
Figure 5-9
Figure 5-13
Training Manual
Link/Speed indicator
Behavior Meaning
Green Link speed is 100 Mbps.
Yellow Link speed is 10 Mbps.
Off The link is down
Figure 5-14
Figure 5-17
PoE - Power Over Ethernet
Behavior Meaning
Green The terminal is supplying power to the
LAN port.
Red The connected device requires more
power than the terminal can supply to
the LAN port.
Off The terminal is not supplying power to Figure 5-18
the port.
5.2 Status signalling

Figure 5-15
5
FBB 150
Behavior Meaning
Steady green Power OK
Flashing green The terminal is powering up
Flashing orange The terminal is closing down
Off No power
5.3 Dash Board

Several information is available on the Dash Board:
• Properties:
• Airtime provider:
Thrane
• GPS position:
• Will show ’Acquiring’ when no GPS fi x has been obtained
• Will show ’Acquired’ if GPS fi x is obtained, but no I4 satellite
has been found yet, or if the GPS pos. is not allowed to be
shown
• Will show the GPS pos. when I4 satellite is found and GPS
pos. is allowed to be shown.
128 Chapter 5
Troubleshooting
• System status:
• Will show Scanning until a I4 satellite is found.
• Will show ’registering’ untill system has been registered with
the network
• Will show ’Ready’ ready for voice and data.
• Will show ’ data Active’ when a data connection is active.
• Satellite selection:
• Will show the selection mode. Auto / EMEA / A-Pac /
Americas
• Current Satellite:
• Will show the I4 satellite the system is tracking.
• Local IP address:
• Show the IP address of the terminal. (Standard Gateway)
• Antenna status:
5
• Will show the status of the antenna: No antenna found / sky
scan / tracking
Figure 5-20
Training Manual
5.4 Help desk

• Event list
• Event log
• Extented status
• Diagnostic report
Figure 5-22
Figure 5-21
Figure 5-23
5.4.1 Event List

The terminal can detect events during POST (Power On Self Test),
NOTE!
PAST (Person Activated Self Test) or CM (Continuous Monitoring).
5
You can see the active Alarms /
When the terminal detects an event that requires your action, it Warnings (red or orange LED)
issues an event message. in the web interface by clicking
the warning symbol in the
When your terminal issues an event message, the Terminal icon bar at the top in the web
indicator or the Antenna indicator in the LED panel on top of the interface.
terminal signals the event, according to the tables.
Terminal indicator and Antenna indicator in the previous section.
5.4.2 Event Log

The event log holds information of all registered events in the
terminal or antenna. The log includes the time of the occurrence,
a short description, location of the error etc. This information can
help troubleshooting errors in the system.
The event log will contain information of the current power cycle.
(Reboot will clear the event log). For further information on the
web interface, see the user manual. Figure 5-24
130 Chapter 5
Troubleshooting
NOTE!
The failed antenna firmware
upload is also logged in the
event log.
NOTE!
Sky Scan
Registrering proces
First cs/ps connection
Handover from regional beam
to spot beam. And visa versa.
Every time a data connection is
started/stopped/suspended.
(suspended = idling for more
that 90 sec)
Voice / fax calll is made
5
Figure 5-25
5.4.3 Extended status

”AWAIT_ALL_PLMN_SEARCH”
REGM has not initiated any idle mode procedure and it is waiting
for a PLMN selection command from the NAS.
”ALL_PLMNSEARCH_PSAB_DISCOVERY”
REGM has initiated the PSAB Discovery procedure and is waiting
to receive a response from the Bearer Control layer.
”ALL_PLMNSEARCH_SYSTEM_INFORMATION”
Figure 5-26 The PSAB Discovery procedure has completed successfully and
REGM is waiting to receive System Information from the Bearer
Control layer.
”ALL_PLMNSEARCH_INITIAL_POSITION_REQUEST”
REGM has requested the Bearer Control layer to provide the UE
GPS Position and is waiting for a response.
Below same, only regarding the PLMN ID.
”AWAIT_SPECIFIC_PLMN_SEARCH”
”SPEC_PLMNSEARCH_PSAB_DISCOVERY”
”SPEC_PLMNSEARCH_SYSTEM_INFORMATION”
”SPEC_PLMNSEARCH_INITIAL_POSITION_REQUEST”
Figure 5-27
Training Manual
”NETWORK_FOUND”
The UMTS network selected by the Non-Access Stratum has been
found and REGM is ready to initiate the Registration procedure
with the RNC.
”REG_STARTED”
REGM has received a request to establish a UE-Specific signalling
connection by either GMMH or MMH and is currently performing
the Registration procedure.
”CONNECTION_CREATION”
REGM has requested SSR to connect to the SIG-SAP and is
waiting for confirmation.
”CONDITIONAL_REG”
The UE is registered with the RNC and a UE-Specific signalling
connection between the UE and RNC has been established but Figure 5-28
the RNC has indicated that validation of the UE position is required
before the UE can access network services (Registration Mode
0).
”POSITION_REQUESTED”
REGM has received the UEPositionRequest message from its
5
peer in the RNC.
”REGISTRATION_UPDATE”
REGM has received and responded to the UEPositionRequest
message and is waiting for validation from the RNC.
”REGISTERED”
The UE is registered with the RNC, a UE-Specific signalling
connection between the UE and RNC has been established, and
the UE has full access to network services (Registration Mode 3).
”DEREGISTER_COMPLETE”
The UE has been Deregistered from the RNC. 
”HANDOVER”
REGM has informed the Bearer Connection layer of an intra-
RNC handover and is waiting for confirmation that the handover
procedure in the lower layers (Bearer Connection/Bearer Control)
has been completed.
”HANDOVER_LEASE”
REGM has informed the Bearer Connection layer of an intra-RNC
handover to a bearer allocated to the current subscriber’s Lease
Group and is waiting for confirmation that the handover procedure
in the lower layers (Bearer Connection/Bearer Control) has been Figure 5-29
completed.
132 Chapter 5
Troubleshooting
5.5 Maintenance page

http://192.168.0.1/index.lua?pageID=Maintenance
NOTE!
Maintanence page
Hidden maintenance page.
Use the below URL.
http://192.168.0.1/index.
lua?pageID=Maintenance
Java engine will
have to be installed.
Figure 5-30
Figure 5-31
The maintenance page contains information about:
System:
• Software version and build no
• IMAI number
• IMSI number
• Terminal Class (class 8 is a FBB 500)
Figure 5-32 • Terminal temperature
• Uptime (time since last reboot)
GPS:
• Type of fix (3D means at least 4 satellites)
• Position
• Position age (time since last fix)
• Speed
Figure 5-33 • Heading
USIM:
• Card status
• Pin 1 status
Figure 5-34
Training Manual
Antenna:
• Type
• Status
• Temperature HPA Figure 5-35
• Temperature ACM (will not show on a 3252A ver)
Satellite:
• Satellite name: (EMEA—Americas—A-Pac)
• Position: Figure 5-36
• Elevation:
• Elevation band:
NAS: (non access stratum)
• RX: Figure 5-37
• TX:
• PS status:
• CS status:
• PLMN status: 5
• Session Status: (1 = one data connection running) Figure 5-38
IAI2:
• Status: (AL layer)
• Status: (bcn-bct layer)
• Beam Type: (regional / narrow)
Figure 5-39
• Spot id: (ID of the regional / narrow beam. (ID >19 = narrow)
• CN/o: (C/No on the regional / narrow beam)
• Fwd(rx) Frq: (the frq, of the forward bearer)
• Channel no:
• Fwd(rx) bytes: (receiver bytes. Signaling + payload)
• Rtn(tx) bytes: (transmittet bytes. Signaling + payload)
• Tx queue: (bytes, in buffer, waiting to be transmittet)
• Ciphering: (encryption. on / of)
Figure 5-40
• Dropped packetes: (incoming packets)
• CRC errors: (incoming packets)
• Rx retramsmission:
• Tx retransmission:
• BCn status: (active connections. Minimum a signaling
connection active)
Figure 5-41
134 Chapter 5
Troubleshooting
C/No:
• The C/No plot show the C/No, ’signal to noise’, over time.
• The normal C/No is for the regional beam around 60dbhz,
but the C/No will vary depending of the terminal class and the
beam type.
• To the left a C/No has been monitored. Between 9.17 and 9.18
Figure 5-43 the terminal was idling and no PS or CS connecton was up.
• At 9.18 a data connection was started, and the C/No raised
from 60 to 70 dbhz, once the beam type changet from regional
beam to spot beam (spot id 8 to spot id 100. Spot 8 is the
regional beam covering Denmark and spot id 100 is the narrow
beam covering Denmark)
Rates:
• The rate plot show the data throughput
• Red is receiver data kbps (RxRate)
• Blue is transmittet data kbps (TxRate)
5 Explanation
Reset X and Y ranges to their
original values
Button
Figure 5-44
Rescale the plot to fit to data
Center current X values
Figure 5-42
Figure 5-45
5.6 Diagnostic report: ’Report in a file’
To view the diagnostic report click the ’Generate report’.
Figure 5-46
Open the diagnostic report using for example ’wordpad MFC’. The
Diagnostic report is a very big text fiel containing a lot of system
information. (250 pages of txt).
One important thing to know is that there is very little history in the
log. All the system information is a ’snapshot’ of now and some
minutes back. (A few traces will hold history. Like the errorlog).
Therefor it is important that the report is generated right after a
problem has occured.
It is also important to know that the diagnostic report, and a detailed
Figure 5-47 fault description are not mutually exclusive. In other words: You
will have to know what to look for.
Training Manual
The easiest way of using the diagnostic report is to search for a

specific key word like ’errorlog’.
Below is the start of the dignostic report:
Date:
Tue Dec 29 08:32:13 2009
Debug:/$ uptime:
Uptime is 0 days 20:34:08.678
Debug:/$ ver:
Software: 1.11, build Build-bganx_bdu_ak-16, UTC Wed Nov
11 07:29:52 2009
eCos TT3710A HAL version 0.80 (eCos for Monroe Main Application Figure 5-48
compiled Aug 10 2009, 12:23:40) running at 167.997 MHz
BBIC01 ID: 128, Rev 1.1 (ASIC-B)
____________________________________________________
Unit Serial number: 07441420

PCB ID:
Type of device:
00000000000315000221
6. S250/S500
5
Class of device: 8. FB500
____________________________________________________ Figure 5-49
5.7 DEBUG SHELL: ’Online reporting’

Previous we have been looking at the errorlog contained in the
diagnostic report. If you are online with the system there is an
easier way to view the errorlog.
In this description windows Hyper Terminal is used as a terminal
program. Any other terminal program with telnet support will
work.
Open Hyper term.
Name the Connection
Connect using: TCP/IP (winsock) Figure 5-50
Host address: 192.168.0.1
Port number: 23
Click: OK
Figure 5-51
136 Chapter 5
Troubleshooting
Type in username and password.

Username: admin
Password: 1234
Welcome to the Thrane & Thrane shell
telnet:/$
To view the errorlog, use the cmd: errorlog
telnet:/$ errorlog
Error Log for Unit Serial number: 07441420
Figure 5-52 Error Log from previous power cycles
Version: 1.11, build Build-bganx_bdu_ak-16, UTC Wed Nov 11
07:29:52 2009
____________________________________________________
NOTE! Error Log from current power cycle
5
Help errorlog
Errorlog delete:
Delete error log in ram and 07:29:52 2009
flash. ____________________________________________________
Errorlog noreboot:
Do not reboot on fatal error.
Errorlog stoptrace: telnet:/$
Do not add new trace lines
after a fatal error. To delete the errorlog type: errorlog delete
Errorlog allowreboot:
Allow reboot on fatal error. telnet:/$ errorlog delete
Errorlog allowtrace:
Allow adding new trace lines Delete error log from FLASH
after a fatal error.
telnet:/$
5.8 Error log

NOTE! debug:/$ errorlog
Search for: Error Log for Unit Serial number: 07441420
Errorlog
The error log holds the first 50 Error Log from previous power cycles
fatal /non fatal events + the
events from the current power Version: 1.11, build Build-bganx_bdu_ak-16, UTC Wed Nov 11
cycle. 07:29:52 2009
NOTE!
021:01:55.002 FATAL Thread: Alive UTC Tue Dec 29 09:00:01
Fatal error when the antenna 2009
fails to respond. Fatal error will
cause a reboot as the system
[pollTimeout, ld/build/source/p-bganx_bdu_ak/modules/
will try to recover. applications/bgan_ut/alive/src/alive.cpp line 97]:
ALIVE: Module ADU_MANAGER failed to answer poll request
SW Version: 1.11, build x_bdu_ak-16, UTC Wed Nov 11 07:29:52
2009 Prev. entry: 6 First
Training Manual
000:00:27.933 NON FATAL Thread: POST Estimated UTC Mon NOTE!

Dec 28 11:58:51 2009 Fatal error when the antenna
fails to respond. Fatal error will
[PostLogErr, build/build/source/p-bganx_bdu_ak/modules/ cause a reboot as the system
system/bgan_ut/base/post/src/post.cpp line 583]: will try to recover.
POST Failed: [0550] - Antenna Present
NOTE!
SW Version: 1.11, build x_bdu_ak-16, UTC Wed Nov 11 07:29:52 Doing the power op self test,
2009 Prev. entry: 7 First POST, the antenna is not
found. Causing a:
000:05:00.193 NON FATAL Thread: POST Estimated UTC Mon POST Failed: [0550] - Antenna
Dec 28 11:58:51 2009 Present.
[PostLogErr, build/build/source/p-bganx_bdu_ak/modules/ NOTE!

system/bgan_ut/base/post/src/post.cpp line 583]: And caused by that the
communicatiom with ATC/ACM
POST Failed: [0602] - ACM/ATB POST fails. Causing a :
SW Version: 1.11, build x_bdu_ak-16, UTC Wed Nov 11 07:29:52 POST Failed: [0602] - ACM/
ATB POST
2009 Prev. entry: 8
Error Log from current power cycle NOTE!
And caused by that the
5
communicatiom with ATC/ACM
07:29:52 2009 fails. Causing a :
POST Failed: [0602] - ACM/
____________________________________________________ ATB POST
Module: PSM_CONTROL, Status: Ok, Message: NOTE!

Current uptime: 0 days 2:47:57.701 Search for:
PSM_Control
Current time: Mon Nov 09 13:03:00 2009 This will hold information
about the system uptime, and
Approximate boot time: Mon Nov 09 10:15:03 2009 the type of reboots previus
performed.
Last reboot type: REBOOT_TYPE_FATAL_ERROR [0x02]
Reboot type counters:
Requested 14
Sudden powerloss 18
Watchdog 0
Fatal error 4
Module: IAI2-AL_REGM, Status: Ok, Message:

NOTE!
Model Ref: 6, MODEL_REF_TT3738, SAILOR 250/500. Model: Search for:
SAILOR. UT Class Type: 3, UT_CLASS_TYPE_MARITIME. The IAI2-AL_REGM
This statuis will hold
ManualPointing: 0 informationsof what kind of
System: 3, SYSTEM_SAILOR_500. SAILOR 500 FleetBroadband. ’satellite selection’ is made
and witch Inmarsat satellite the
UT Class: 8, maritime-high-gain (8),UTCLASS_MARITIME_HIGH terminal has found.
(8)
Satellite Selection - Preferred: AUTO, Auto selection. MMI code: 4 NOTE!
FBB 500 = class 8
DSP Allocation State: BCt. No maintained radio silence. Satelitte selection = AUTO
Satellite found = EMEA
GlobalDiscoverCause:
UNI_REGM_SATELLITE_SELECTION_INITIAL.
138 Chapter 5
Troubleshooting
Satellite Selection - Frequency: EMEA, I-4 satellite F2: EMEA

Region, 25.0E Sat Id: 6 Primary: TRUE Channel: 11168
Satellite Selection - AVP param: EMEA, I-4 satellite F2: EMEA
Region, 25.0E Sat Id: 6 Satellite Id Counter: 1
REGM Current state: REGISTERED
usimAvail: TRUE. Latest USIM Event: USIM_EVENTID_USIM_
VALID.
System Info Counters. Total:2 AllPlmn:1 SpecPlmn:1
NetworFound:0 Registered:0 Default:0
NOTE!
Module: Temperature, Status: Ok, Message:
Search for: Temperature reported by sensors (unit °C)
Temperature
This statuis will hold sensor unit temp min max alarm
informations of the terminal hpa 514 -5 -6 -5 0
and antenna. acm 515 -4 -6 -4 0
mainboard 0 27 25 27 0
NOTE!
In the Diagnostic reportSearch
debug:/$ post
5
for: post POST results from last boot (NORMAL):
____________________________________________________
[0001] Passed - IMEI Programmed

[0002] Passed - MAC ETH0 Programmed
[0004] Passed - Unit Serial Number Programmed
[0006] Passed - USIM device id test
[0010] Passed - Temperature sensor
[0010:1 ] Passed mainboard
[0012] Passed - Type of Device Programmed
[0016] Passed - rx dsp
[0016:1 ] Passed FrameSyncSignalTest.lua
[0016:2 ] Passed pllLockedDetect_LMX2470_BGANX.lua
[0017] Passed - tx dsp
[0017:1 ] Passed RFIC03_chipID.lua
[0017:2 ] Passed RFIC03_resetValues.lua
[0017:3 ] Passed RFIC03_registers_access.lua
[0017:4 ] Passed RFIC03_1765MHz_PLL_lock.lua
[0017:5 ] Passed MSIC01_chipID.lua
[0017:6 ] Passed MSIC01_resetValuesTx.lua
[0017:7 ] Passed MSIC01_registers_access.lua
[0020] Passed - Watchdog
[0022] Passed - PCB ID Programmed
[0027] Passed - TX VCOBANK. BM0: 1950195312.
Range: 1845000000..2045000000
Training Manual

Range: 1800000000..2000000000
Range: 1760000000..1960000000
Range: 1725000000..1925000000
Range: 1685000000..1885000000
Range: 1650000000..1850000000
Range: 1620000000..1820000000
Range: 1585000000..1785000000
[0036] Passed - Test of interface to SI3220 chip
[0037] Passed - ISDN interface test 5
[0043] Passed - TX CABLE LOSS: 745. Range: -200..2200
NOTE!
[0044] Passed - Marvell ethernet switch This status will hold the result
of the Power up self Test.
[0045] Passed - Clock PLL U2500/U2502
If some test in ongoing then
[0046] Passed - Point of load converter the report has beed generated
to soon after the power up.
[0047] Passed - RX AD9864 COARSE: 3. Range: 1..6
If some of the test fails then
[0048] Passed - RX AD9864 FINE: 42. Range: -1..64 the same error will show in the
event list.
[0049] Passed - RX AD9864 RC: 16. Range: 5..250
In the POST it is possible to
[0050] Passed - PoE Controller (TPS2384) see the cable loss. The loss
will have to be within the range
[0051] Passed - TX CABLE LOSS DIFF: 20. Range: -200..200 of –200..2200
[0500] Passed - PSM AVR The Loss Diff. Is an indication
of hos much the loss changes.
[0501] Passed - I2C AVR (Cable loss is messured on
every reboot).
[0502] Passed - Discrete IO AVR
[0503] Passed - PSU AVR
[0504] Passed - PSM PCB ID Programmed
[0505] Passed - Antenna SOT
[0550] Passed - Antenna Present
[0600] Not tested - HPA_POST
[0601] Passed - ADU POST
[0601:10] Passed Production data
[0601:12] Passed Antenna interface
[0601:13] Passed GPS board detection
[0601:14] Passed FPGA test
140 Chapter 5
Troubleshooting
[0602] Passed - ACM/ATB POST

[0603] Passed - GPS POST
Test summary: 0 failed of 40 test
Like with the error log it is possible to monitor the post status
online. In the debug shell use the cmd: post
telnet:/$ post
POST results from last boot (NORMAL):
____________________________________________________
[0001] Passed - IMEI Programmed

[0002] Passed - MAC ETH0 Programmed
[0004] Passed - Unit Serial Number Programmed
[0006] Passed - USIM device id test
[0010] Passed - Temperature sensor
5
[0010:1 ] Passed mainboard
[0012] Passed - Type of Device Programmed
[0020] Passed - Watchdog
[0022] Passed - PCB ID Programmed
[0027] Ongoing - TX VCOBANK. BM0: ONGOING
[0036] Passed - Test of interface to SI3220 chip
[0043] Ongoing - TX CABLE LOSS: ONGOING
[0045] Passed - Clock PLL U2502
[0046] Passed - Point of load converter
[0047] Ongoing - RX AD9864 COARSE: ONGOING
[0048] Ongoing - RX AD9864 FINE: ONGOING
[0049] Ongoing - RX AD9864 RC: ONGOING
[0050] Passed - PoE Controller (TPS2384)
[0051] Ongoing - TX CABLE LOSS DIFF: ONGOING
[0500] Passed - PSM AVR
[0501] Passed - I2C AVR
[0502] Passed - Discrete IO AVR
[0503] Passed - PSU AVR
Training Manual
[0504] Passed - PSM PCB ID Programmed

[0505] Passed - Antenna SOT
[0550] Passed - Antenna Present
[0600] Not tested - HPA_POST
[0601] Passed - ADU POST
[0601:10] Passed Production data
[0601:12] Passed Antenna interface
[0601:13] Passed GPS board detection
[0602] FAILED!!!! - ACM/ATB POST NOTE!
[0602:10] Passed Production data Case where the GPS module
fails to respond on power up.
[0602:11] Passed xDM eeprom + tx gain That causes the ACM/ATB
Post to fail.
[0602:12] Passed Antenna type test
[0602:13] Passed Antenna calibration
[0602:14] Passed Sensor sanity check
[0602:16] FAILED!!!! - GPS alive failed 5
[0603] Not tested - GPS POST
PDP/Profile/Connection status
Module: UMTS-SM, Status: Ok, Message: NOTE!
Status for all PDP contexts: The UMTS-SM status will show
the state of the 11 possible
CONTROL PLANE: PDP’s / Profiles / Connections
The command gives you two
lists one related to the control
plane and one related to the
user plane (UMTS terms for
control and data).
Figure 5-53
142 Chapter 5
Troubleshooting
NOTE! Control Plane:

Control plane: PDP_INACTIVE = 0,
Retrans:
Retransmissions. PDP_ACTIVE_ATTACHING
upTime:
Uptime for the PDP / profile / waiting for umts-reg to make an attach in PS domain
connection
Class: PDP_ACTIVE_PENDING,
B = background data. waiting for PDP context request accept from CN
S = Streaming data
maxRateUp: PDP_ACTIVE,
Maximum number of kbits/s
delivered to UMTS (up-link PDP context is active
traffic)
maxRateDn PDP_INACTIVE_PENDING,
delivered to UMTS (Down-link
deactivating, waiting for PDP context deactivation accept
traffic) PDP_RELEASE_PENDING,
minRateUp:
Maximum number of kbits/s local release of PDP context, waiting for PDP context deactivation
delivered to UMTS (Down-link accept (connection to ethernet already disconnected)
traffic)
minRateDn: PDP_MODIFY_PENDING,
5
delivered to UMTS (Down-link modifying PDP context, waiting for modify accept from CN
traffic)
maxSdu:
PDP_REACTIVE_PENDING
Indicates the maximum re-activation of PDP context (streaming), waiting for modify
allowed SDU size.
Delay:
accept
Error corr. / no error corr.4000
/ 500
Pri:
Traffic handling priority
Figure 5-54
User Plane:
NOTE!
User Plane: DATA_CONN_INACTIVE = 0
Compress:
Data comp. Type. connection idle/not active
hC:
Header comp. On-Of DATA_CONN_ACTIVE_PENDING
RxCnt: waiting for a connection to be established (from the CN/RAN)
RX counter kps.
TxCnt: DATA_CONN_ACTIVE
TX counter kps.
RxComp: connection established
Comp in %,
TxComp: DATA_CONN_SUSPEND
Comp. In % connection suspended, i.e currently no connection to CN/RAN
TxQueue:
Packets in the TX queue DATA_CONN_INACTIVE_PENDING
TxBufdiscard:
Packets discharged. waiting for CN/RAN to release connection
Like with the error log it is possible to monitor the UMRS-SM status
online.
In the debug shell use the cmd:
telnet:/$ stat -m umts-sm -l full
Training Manual
NOTE!
RX/TX data rate over 60 sec.
5
Figure 5-55
System status
Module: UMTS-REG, Status: Ok, Message:
NOTE!
Attached status CS domain: Attached Attach status:
Idle
Attached status PS domain: Attached Attaching
Attached
PLMN currently selected (MCC-MNC): 901-11F Rejected
Home PLMN IMSI (usim): 901-112
Last registered PLMN from SIM: 901-11F
GPS / POS
Module: CNAV, Status: Ok, Message:
NOTE!
55.79417 (lat) 12.52299 (lon) 46.66m (hmsl) (3D) 55.79417 (lat)
12.52299 (lon)
Fix at: Mon Nov 09 13:02:59 2009 46.66m (hmsl)
(3D)
System time: Mon Nov 09 13:03:00 2009
Satellites 11
ECEF x: 3508366.870000 y: 779263.550000 z: 5251665.620000
Must be displayed: yes
Satellites 11 ‘(must be displayed’ means
that the pos is allowed to be
Must be displayed: yes shown in the handset and web
mmi . It is the network that.
Time to first fix 00:01.11 Based on the pos, decides
whether the terminal is allowed
to show the pos).
144 Chapter 5
Troubleshooting
telnet:/$ cnav -m pos

55.79411 (lat) 12.52293 (lon) 50.49m (hmsl) (3D)
Fix at: Tue Jan 05 11:50:25 2010
System time: Tue Jan 05 11:50:26 2010
ECEF x: 3508374.790000 y: 779261.320000 z: 5251665.320000
Satellites 8
Time to first fix 00:01.01+-
**
Signal / C/No status: debug:/$ iai2_cn0_show
NOTE!
C/No for all data received on
the forward bearer.
’All data’ is ’my data’ + ’data to
other terminals’ on the same
forward bearer.
5
Figure 5-56
NOTE!
C/No for data, only for me,
received on the forward beare.
’Data for me’ is ’all data—’data
for other terminals’.
Figure 5-57
CRC error is calculated for each FEC block.
If for example E6 FEC blocks is received and one FEC block has
one or more CRC error THEN CRC errors = 1 ppm.
High CRC error indicates a poor signal.
To give an indication on the load of the forward bearer compare
the ’all data received’ with ’data only for me’.
Small difference = low load. (only me on the bearer)
Big difference = high load. (more terminal on the forward bearer)
Like with the error log it is possible to monitor the C/No status
online.
telnet:/$ iai2_cn0_show (where 0 = digit 0)
Training Manual
Antenna status: S-500 - 3252A NOTE!

Module: ATB, Status: Ok, Message: State
State = Tracking Current frequency
atb_motors_stopped: 0 ATB state
garage_mode: 0 Elevation
debug_mode: 0
Failure conditions
Current frequency: 11168
time_start_of_tracking: 10807 seconds
time_start_of_blocking: 10831 seconds
time_start_of_last_scan_req: 10831 seconds
time_end_of_last_scan_req: 10807 seconds
time_last_track_to_block: 10831 seconds
time_last_gps_pos: 10831 seconds
time_last_atb_status: 0 seconds
gps_pos x,y,z: 0,0,0
latest_heading: 0 last_tracked_heading: 0
ATB state: 7 (0=Idle, 1-4=Searching, 5-7=Tracking, 8=Blocked, NOTE!
9=Freeze)
5
A-PAC:
Elevation: 25 Frq: 12330 – Chan: 15825
Channel : 12920 Frq: 10994 - Chan: 12485
Failure conditions (no of errors): 0 Americas:
Frq: 10828 – Chan: 12070
ScanType: 1 (Full=0, Fixed=1) Frq: 12292 – Chan: 15720
Current Freq_index: 0
EMEA:
____________________________________________________ Frq: 11168 – Chan: 12920
Frq: 12446 – Chan: 16115
Index: 0 , freq: 11168, chan: 12920, elevation: 25
____________________________________________________
ATB interface counters

ATB_FREQ_UPDATE: 0
ATB_FREQ_ELEVATION: 1
ATB_STATUS: 10826
TU_SIGNAL_STAT: 0
ATB_FAILURE_REQ: 0
Total ATB-msg sent: 10827
Correct recieved ATB messages: 0
Discarded ATB messages: 0
Like with the error log it is possible to monitor the ATB status
online.
telnet:/$ stat - m atb
146 Chapter 5
Troubleshooting
Antenna status: TT-500 - 3252B

Module: ACM, Status: Error, Message:
NOTE!
Uptime Time (since startup): 1040280
ACM state
Time since first non-retry sky scan: 38
ACM IF State: TRACKING
Elevation
Azimuth: 0
Current frequency Elevation: 27
C/No (global beam—ATR) ACM temperature: 19
ACM temperature state: 0
Es/No Counters:
Total: 0
Valid: 0
Blocked: 0
Tuning: 0
Searching: 0
Negative: 0
Pos limit: 0
5
Neg limit: 0
Time Statistics:
TotalTime Count Average
Sky Scan 6821 1 6821
Power 4193 110 38
C/No 2313 5 462
NOTE! Next Step 25984 110 236
A-PAC:
Frq: 12330 – Chan: 15825 Move to pos 9268 10 926
Frq: 10994 - Chan: 12485 Start Sky Scan Data:
Americas: Channel # Elevation Longitude
Frq: 10828 – Chan: 12070 11168 25 25
Frq: 12292 – Chan: 15720 Current scan freq: 11168,
EMEA: BGAN channel candidates:
Frq: 11168 – Chan: 12920
Frq: 12446 – Chan: 16115
Current position: 1
Position Channel# pwrNarrow pwrWide pwr200 C/No
0 11168 2360377 2325324 19926 587 1.015074
1 11168 806522 879640 8246 0 0.916877
21 11168 540264 606444 7116 0 0.890872
20 11168 90219 189280 4443 0 0.476643
Like with the error log it is possible to monitor the ACM status
online.
telnet:/$ stat –m acm
Training Manual
Antenna status: S-250 - 3050A

Module: ACM, Status: Error, Message: NOTE!
Time (since startup): 522972 ACM state
Time since first non-retry sky scan: 489097 Azimuth, Elevation
ACM IF State: TRACKING Current frequency
Azimuth: 39
C/No (current beam)
Elevation: 26
ACM temperature: -4
Es/No Counters:
Total: 16944
Valid: 16875
Blocked: 0
Tuning: 50
Searching: 19
Negative: 0
Pos limit: 0
5
Neg limit: 0
Time Statistics:
Sky Scan 5879 1 5879
Power 532 14 38
C/No 483 1 483
Next Step 4432 14 316 NOTE!
A-PAC:
Move to pos 1280 2 640 Frq: 12330 – Chan: 15825
Start Sky Scan Data: Frq: 10994 – Chan: 12485
Channel# Elevation Longitude Americas:
11168 25 25 Frq: 10828 – Chan: 12070
Current scan freq: 11168, Frq: 12292 – Chan: 15720
BGAN channel candidates: EMEA:
Frq: 11168 – Chan: 12920
Current position: 1 Frq: 12446 – Chan: 16115
1 11168 699880 780901 7412 537 0.896247
0 11168 658588 757037 6965 0 0.869955
13 11168 120926 434459 6109 0 0.278337
12 11168 112478 354408 5482 0 0.317369
3 11168 103125 229698 4002 0 0.448959
7 11168 98801 217104 3548 0 0.455086
4 11168 90960 220359 3623 0 0.412781
2 11168 89712 219268 4643 0 0.409143
5 11168 85579 212233 3608 0 0.403231
9 11168 83274 216147 3750 0 0.385266
11 11168 83164 255361 5013 0 0.325672
8 11168 74488 206546 3737 0 0.360636
10 11168 72415 214399 3776 0 0.337758
6 11168 65755 188333 3539 0 0.349142
148 Chapter 5
Troubleshooting
Antenna status: S-150 - 3050C

NOTE! Module: ACM, Status: Error, Message:
ACM state Time (since startup): 522676
Azimuth, Elevation Time since first non-retry sky scan: 488801
Current frequency
ACM IF State: TRACKING
Azimuth: 147
C/No (current beam)
Elevation: 27
ACM temperature: 4
Es/No Counters:
Total: 51881754
Valid: 51844417
Blocked: 0
Tuning: 25618
Searching: 11719
Negative: 579
Pos limit: 0
5
Neg limit: 0
Time Statistics:
Sky Scan 6577 1 6577
Power 8161 210 38
C/No 42106 116 362
NOTE! Next Step 36131 112 322
A-PAC:
Frq: 12330 – Chan: 15825 Move to pos 52993 118 449
Frq: 10994 - Chan: 12485 Start Sky Scan Data:
Americas: Channel# Elevation Longitude
Frq: 10828 – Chan: 12070 11168 25 25
Frq: 12292 – Chan: 15720 12446 25 25
EMEA: Current scan freq: 11168, 12446,
Frq: 11168 – Chan: 12920
Frq: 12446 – Chan: 16115
BGAN channel candidates:
Current position: 6
6 11168 788665 879351 8653 547 0.896872
7 11168 441538 544196 6397 0 0.811358
6 12446 243248 641587 6787 0 0.379135
8 12446 217718 386150 6281 0 0.563817
7 12446 208017 435745 6013 0 0.477382
5 11168 198476 415470 6277 0 0.477714
4 11168 121499 379110 6349 0 0.320485
13 11168 112222 241167 3947 0 0.465329
Training Manual
5.9 Call Log

To view the call log click the Export call log to file.
To open, use same procedure it as for the diagnostic report.
(Call log is also contained in the diagnostic report)
Call log:
____________________________________________________ Figure 5-58
____________________________________________________
ID: 210 NOTE!

Direction: Outgoing Cause: Network failure
Type: PS DATA (In this case it was caused
be the 128kbp streaming was
APN: bgan.inmarsat.com activated while a 256kbps
TrafficClass: Streaming 128 streaming already running)
bitRateUp: 128
bitRateDown: 128
Received: 0
Transmitted: 0
Start time:
Stop time:
15:01:53 11 Jan 2010
15:01:54 11 Jan 2010
5
Duration: 1
Cause: Network failure
150 Chapter 5
Troubleshooting
____________________________________________________
ID: 209
Direction: Outgoing
Type: PS DATA
APN: bgan.inmarsat.com
TrafficClass: Streaming 16
bitRateUp: 16
bitRateDown: 16
Received: 0
Transmitted: 0
Start time: 14:51:05 11 Jan 2010
Stop time: 14:51:33 11 Jan 2010
Duration: 28
Cause: Normal deactivation
____________________________________________________
5
NOTE! ID: 208
Cause: Connection without Direction: Outgoing
TFT already activated. Type: PS DATA
(This was caused no TFT,
Trafic Flow Filters, linked to the APN: bgan.inmarsat.com
64 kbps streaming profile) TrafficClass: Streaming 64
bitRateUp: 64
bitRateDown: 64
Received: 0
Transmitted: 0
Start time: 14:51:16 11 Jan 2010
Stop time: 14:51:17 11 Jan 2010
Duration: 1
Cause: PDP connection without TFT already activated
Like with the error log it is possible to monitor the call logonline.
Call_log
telnet:/$ call_log
Call log:
____________________________________________________
NOTE! ID: 210

The online log will show the Call ref: 5
call log in more details. Direction: MO
Device ID: 0x00000000
Type: PS DATA
Priority: 0
PLMN: 901-11
Remote APN: bgan.inmarsat.com TrafficClass:S, Delay:0,
bitRateUp: 128, bitRateDown:128, Compressed:no
Training Manual
Received: 0
Transmitted: 0
Start time: Mon Jan 11 15:01:53 2010
Stop time: Mon Jan 11 15:01:54 2010
Duration: 0:00:01
Cause: 38 (0x26) - Network failure
____________________________________________________
ID: 209
Call ref: 11
Direction: MO
Type: PS DATA
Priority: 1
PLMN: 901-11
bitRateUp: 16, bitRateDown:16, Compressed:no
Received: 0
Transmitted: 0
Start time:
Stop time:
Mon Jan 11 14:51:05 2010
Mon Jan 11 14:51:33 2010
5
Duration: 0:00:28
Cause: 36 (0x24) - Normal deactivation
____________________________________________________
ID: 208
Call ref: 4
Direction: MO
Type: PS DATA
Priority: 0
PLMN: 901-11
bitRateUp:64, bitRateDown:64, Compressed:no
Received: 0
Transmitted: 0
Duration: 0:00:01
Cause: 46 (0x2e) - PDP connection without TFT already
activated
____________________________________________________
152 Chapter 5
Troubleshooting
5.10 Error result code

+CME ERROR
General errors
0 phone failure
1 no connection to phone
2 phone-adaptor link reserved
3 operation not allowed
4 operation not supported
5 PH-SIM PIN required
6 PH-FSIM PIN required
7 PH-FSIM PUK required
10 SIM not inserted (Note)
11 SIM PIN required
5
12 SIM PUK required
13 SIM failure (Note)
14 SIM busy (Note)
15 SIM wrong (Note)
16 incorrect password
17 SIM PIN2 required
18 SIM PUK2 required
20 memory full
21 invalid index
22 not found
23 memory failure
24 text string too long
25 invalid characters in text string
26 dial string too long
27 invalid characters in dial string
30 no network service
31 network timeout
32 network not allowed - emergency calls only
40 network personalization PIN required
41 network personalization PUK required
42 network subset personalization PIN required
43 network subset personalization PUK required
44 service provider personalization PIN required
45 service provider personalization PUK required
46 corporate personalization PIN required
Training Manual
47 corporate personalization PUK required

48 hidden key required (NOTE: This key is required when accessing
hidden phonebook entries.)
49 EAP method not supported
50 Incorrect parameters
Errors related to a failure to perform an Attach
103 Illegal MS (#3)
106 Illegal ME (#6)
107 GPRS services not allowed (#7)
111 PLMN not allowed (#11)
112 Location area not allowed (#12)
113 Roaming not allowed in this location area (#13)
Errors related to a failure to Activate a Context
132 service option not supported (#32)
5
133 requested service option not subscribed (#33)
134 service option temporarily out of order (#34)
149 PDP authentication failure
151 VBS/VGCS not supported by the network
152 No service subscription on SIM
153 No subscription for group ID
154 Group Id not activated on SIM
155 No matching notification
156 VBS/VGCS call already present
157 Congestion
158 Network failure
159 Uplink busy
160 No access rights for SIM file
161 No subscription for priority
162 operation not applicable or not possible
5.11 Troubleshooting
How to troubleshoot the FBB system
To troubleshoot a Bgan-X system is basic the same regardless to
witch terminal / system has the problem.
There are a handful of steps one must perform. And again those
steps are more or less the same regardless to what system it is.
(Explorer 300-325--500-570-700-727. Fbb 500-250-150.)
The flowchart is a guideline in how the work your way through the
troubleshooting, and witch information is needed in the different
situations.
154 Chapter 5
Troubleshooting
The first step is to get a detailed description of the problem.

Next step is to verify the problem by testing the system.
After troubleshooting it is also important to make a system test to
verify that the problem is solved.
Once the problem is verified you can start the troubleshooting.
First thing is to check the system status by looking at the LED’s
on the terminal.
Based on the state of the LED’s you can decide how to proceed.
Red LED’s is an indication of a warning / error, witch will show in
the Event list, Event log, and in the IP handset / Active alarms.
Flashing green LED’s is an indication of ongoing events like sky
scan, registering, attaching
Steady green LED’s is an indication of a system witch has passed
the ‘sky scan, registering, attaching part and is online.
5
Training Manual
Figure 5-59
156 Chapter 5
Troubleshooting
Example: Terminal LED- Slow fl ashing. Antenna LED- Rapid

fl ashing
Figure 5-61
Status Antenna Terminal

indicator indicator
The Flashing Flashing
antenna is slowly green
starting up green
The Flashing Flashing
antenna is rapidly green
performing green
a sky scan
The Steady Flashing
antenna is green green Figure 5-60
tracking Signaling status
The Steady Flashing
terminal is green green
Antenna is performing a sky scan.
registering Check the Dash Board for info.
on the
network
GPS position: Acquired = System has a GPS fi x.
The Steady Steady Status: scanning = No sat. found
system is green green
Satellite selection: Auto = problem is not a wrong entry in satellite
registered
selection.
and ready
for use Current satellite: None = no satellite found.
Figure 5-62 Antenna status: sky scan = scanning for a satellite.
Training Manual
View the Event log for further details: No further info in Event log.
View the diagnostic report or Debug shell for verification of GPS.
System has GPS fix.
View the location of the antenna to verify the clear view the
satellite.
If system has GPS fix and a clear view to satellite, a hardware
problem in the RX chain or in the tracking / motor drive, must be
the problem.
Check that the antenna is performing a sky scan.
If scanning replace module, in the RX chain, one by one.
Figure 5-64
If not scanning replace the pcb’s, in the tracking / motor drive, one
by one.
5
Figure 5-65
Figure 5-63
Like with the error log it is possible to monitor the eventhandler NOTE!
log online. In the Diagnostic report search
for: eventhandler
In the debug shell use the cmd: Eventhandler - l
Like with the error log it is possible to monitor the GPS status
online.
In the debug shell use the cmd: Cnav - m pos NOTE!
telnet:/$ cnav - m pos In the Diagnostic report
search for: CNAV
55.79389 (lat) 12.52116 (lon) 110.44m (hmsl) (3D)
Fix at: Tue Jan 12 12:33:20 2010 NOTE!
System time: Tue Jan 12 12:34:20 2010 GPS FIX:
The GPS position will not be
ECEF x: 3508429.250000 y: 779159.437500 z: 5251666.500000 shown until the terminal is
registered with the network.
Satellites 4 It is the network witch ’informs’
the terminal that it is allowed
Must be displayed: no to show GPS position. (in
some countries it is not allowed
Time to first fix 00:00.25 to show the GPS position)
So until the network has
allowed the GPS position to be
shown it will be hidden, and not
shown.
158 Chapter 5
Troubleshooting
Example: Terminal LED stready RED
Figure 5-67
5
Figure 5-68
Behavior Meaning
Steady Ready. BGAN
green registration
completed.
Flashing Please wait
green - process in
progress. BGAN
registration
ongoing.
Orange Warning
- temporary
malfunction. User Figure 5-66
action is required. Signaling status
Red Critical error.
Chritical error:
Check the event
log. If the problem Check status on Dash Board:
is in the SAILOR
Not registered.
FleetBroadband
system and you View Event list:
can not solve Error in Registering for Voice and Data. (CS and PS)
it, contact your
destributor and View event log
return the unit for Network found but failing an registation for Voice and Data
repair if necessary.
View Maintenance page: PS status = Blocked, CS status = idle
Figure 5-69
Training Manual
Figure 5-73
Figure 5-70
Figure 5-74
Figure 5-71
NOTE!
Maintanence page
Hidden maintenance page.
Use the below URL.
http://192.168.0.1/index.
lua?pageID=Maintenance
Figure 5-72
160 Chapter 5
Troubleshooting
NOTE! Like with the error log it is possible to monitor the call log online.
In the Diagnostic report search In the debug shell use the cmd:
for: Call_log
Call_log
telnet:/$ call_log
Call log:
____________________________________________________
ID: 8
Call ref: 1
Direction: MO
Type: PS DATA
Priority: 0
PLMN: 901-11
Remote APN: BGAN.INMARSAT.COM TrafficClass: B, Delay: 0,
bitRateUp:0, bitRateDown: 0, Compressed: no
5
Received: 0
Transmitted: 0
Start time: Tue Jan 12 14:53:00 2010
Stop time: Tue Jan 12 14:53:00 2010
Duration: 0:00:00
Cause: 262147 (0x40003) - PS attach rejected
____________________________________________________
ID: 7
Call ref: 1
Direction: MO
Type: CS VOICE
Priority: 0
PLMN: 901-11
Call type: Speech
Connected number
{
Number: 004539558760
TypeOfNumber: 0
Numbering plan: 1
Presentation: 0
}
Duration: 0:00:00
Cause: 213251 (0x34103) - Other, code 0x34103
____________________________________________________
Training Manual
Like with the error log it is possible to monitor the umts-reg status NOTE!
online. In the Diagnostic report search
for: Umts-reg
Stat –m umts-reg
telnet:/$ stat -m umts-reg
STAT Report
Module: UMTS-REG, Status: Ok, Message:
Attached status CS domain: Idle
Attached status PS domain: Blocked
PLMN currently selected (MCC-MNC): 901-11F
Home PLMN IMSI (usim): 901-112
Last registered PLMN from SIM: not available
Verify that the terminal has a valid GPS fix
Like with the error log it is possible to monitor the GPS status NOTE!
5
for: CNAV
Cnav-pos
telnet:/$ cnav -m pos
55.79379 (lat) 12.52278 (lon) 77.92m (hmsl) (3D)
Fix at: Tue Jan 12 14:33:46 2010
System time: Tue Jan 12 14:34:41 2010
ECEF x: 3508397.750000 y: 779256.750000 z: 5251634.000000
Satellites 7
Time to first fix 00:00.24
Verify the SIM card
(Use a known working test sim card)
Check with the Airtime provider to verify SIM card registering.
162 Chapter 5
Troubleshooting
Example: Problem related to the Network User Group setup.

Terminal LED steady green. Antenna LED steady green.
Voice call OK.
Figure 5-76
Figure 5-75
Training Manual
Like with the error log it is possible to monitor the post status NOTE!
for: Call_log
Call_log
telnet:/$ call_log
Call log:
____________________________________________________
ID: 208
NOTE!
Call ref: 4 Eksample 1:
Direction: MO A secondary PDP/connection,
Device ID: 0x00000000 64kbps streaming, is started
with any ling made to a TFT
Type: PS DATA filter.
Priority: 0
PLMN: 901-11
Remote APN: bgan.inmarsat.com, TrafficClass: S, Delay: 0,
5
bitRateUp: 64, bitRateDown: 64, Compressed: no
Received: 0
Transmitted: 0
Duration: 0:00:01
Cause: 46 (0x2e) - PDP context without TFT already
activated
Setup a TFT filter and link it toi the profile
telnet:/$ call_log
Call log:
____________________________________________________
ID: 3 NOTE!
Call ref: 1 Eksample 2:
Direction: MO A standard data PDP /
connection is rejected do to
Device ID: 0x00000000 wrong username-password in
Type: PS DATA network user group setup.
Priority: 0
PLMN: 901-11
Remote APN: BGAN.INMARSAT.COM, TrafficClass: B, Delay: 0,
Received: 0
Transmitted: 0
Start time: Thu Jan 07 12:36:45 2010
Stop time: Thu Jan 07 12:36:48 2010
Duration: 0:00:03
Cause: 29 (0x1d) - User authentication failed
Verify the username and password in the NUG.
164 Chapter 5
Troubleshooting
Example: Terminal LED steady green. Antenna LED steady green
Figure 5-78
Figure 5-77
Training Manual
Like with the error log it is possible to monitor the post status NOTE!
for: Call_log
Call_log
telnet:/$ call_log
Call log:
____________________________________________________
ID: 8
Call ref: 1
Direction: MO
Type: PS DATA
Priority: 0
PLMN: 901-11
Remote APN: BGAN.INMARSAT.COM, TrafficClass: B, Delay: 0,
5
Received: 0
Transmitted: 0
Duration: 0:00:00
Cause: 262147 (0x40003) - PS attach rejected
The 6 digit cause code is an internal cause code.
That means that the cause code is not coming from the network,
and the terminal most likely has lost the connection to the network,
the signal is too weak, the GPS fix is too old.
Check C/No, check GPS, check event log, varify SIM card.
166 Chapter 5
Troubleshooting
Example: Stay in scan mode
Figure 5-80
5 NOTE!
View the LED’s
View the Signaling status
Terminal LED is solid RED
Antenna LED fl ashing
View the Event list
Figure 5-79
Training Manual
Figure 5-84
Figure 5-81

Error Log from current power cycle
Version: 1.11, build Build-bganx_bdu_ak-16, UTC Wed Nov 11 NOTE!
No entry in the error log for the
07:29:52 2009 current power cycle.
____________________________________________________
telnet:/$
5
Figure 5-83
Select AUTO mode. Or select the satellite for your OR.
168 Chapter 5
Troubleshooting
Example: GPS module defective
Figure 5-88
Figure 5-86
Figure 5-89
Figure 5-87
Training Manual
Error Log from current power cycle NOTE!

Version: 1.11, build Build-bganx_bdu_ak-16, UTC Wed Nov 11 To view the ERRORLOG from
the debug shel, use the cmd:
07:29:52 2009 Errorlog
____________________________________________________ To view it from the diagnostic
report, search for:
errorlog
000:00:32.933 NON FATAL Thread: POST (*** No UTC time
available ***)
[PostLogErr, build/build/source/p-bganx_bdu_ak/modules/
system/bgan_ut/base/post/src/post.cpp line 581]:
POST Failed: [0602:16] - ACM/ATB POST: GPS alive failed
SW Version: 1.11, build x_bdu_ak-16, UTC Wed Nov 11 07:29:52
2009 Curr. entry: 0 First
telnet:/$ post
NOTE!
POST results from last boot (NORMAL): To view the POST from the
debug shel, use the cmd:
____________________________________________________ post

[0602] FAILED!!!! - ACM/ATB POST
To view it from the diagnostic
report, search for:
post 5
After a while it is normal that
[0602:10] Passed Production data the faiied test in post will
increase.
[0602:11] Passed xDM eeprom + tx gain
In this case the failing GPS
[0602:12] Passed Antenna type test module will stop the system
from finishing the tests.
[0602:13] Passed Antenna calibration
Therefore is is important to look
[0602:14] Passed Sensor sanity check for the first event in the EVENT
LIST/ERREO LOG
[0602:16] FAILED!!!! GPS alive failed
[0603] Not tested - GPS POST
Replace the GPS module:
170 Chapter 5
Troubleshooting
5.12 Troubleshooting Antenna Failure

The SAILOR Fleet Broadband 500 system is experiencing a fault
that needs to be diagnosed and the solution found to make the
system operational.
Reported Problem
The terminal has been losing connection with the network and
there is a RED LED on the terminal.
Terminal Indicator
Behavior Meaning
Steady green Ready. BGAN registration completed.
Flashing green Please wait - process in progress. BGAN
registration ongoing.
action is required.
Red Critical error.
5
Check the event log. If the problem is in the
SAILOR FleetBroadband system and you
cannot solve it, contact your destributor and
Figure 5-92 return the unit for repair if necessary.
Figure 5-90
Antenna indicator
Behavior Meaning
Steady green Tracking. The antenna is ready for use
Flashing green Please wait - process in progress.
Slow fl ashing: The antenna is starting up
Rapid fl ashing: Sky scan
action is required.
Red Critical error.
Check the event log. If the problem is in the
SAILOR FleetBroadband system and you
cannot solve it, contact your destributor and
return the unit for repair if necessary.
Figure 5-91
Training Manual
The VoIP Handset displays a message Identifying a problem with

the Fleet Broadband system. In this case the error text “ERROR :
Antenna Failure” Identifi es a failure with one of the modules in the
ADU (antenna).
Press the Menu Key on the Handset for more details about the
Alarm. This will provide more details about the error occurring in
the Antenna.
Figure 5-94
The Alarm Details on the Display read; BGAN alarm
WARNING: Antenna Cross-elevation motor.
VoIP Handset Messages
This texture tells you an area to focus on in the troubleshooting
process.
Connect a computer to the FBB Terminal to gain access to the
Web interface. After you have obtained an IP address, open your
web browser to address http://192.168.0.1 (default) to review the
Dashboard. There is information here that can help troubleshooting
the terminal error.
Web Interface
5
Figure 5-95
Figure 5-96
Figure 5-93
172 Chapter 5
Troubleshooting
Event List
You can see the active Alarms / Warnings (red or orange LED) in
the web interface by clicking the warning symbol in the icon bar at
the top in the web interface.
Figure 5-99
Figure 5-97
Event Log
Figure 5-100
5
NOTE!
The antenna is searching
for the Nework signal and
attempting to register on the
network.
NOTE!
Warning is reported that the
Antenna Cross elevation motor
has insuffi cient voltage or load
current.
Figure 5-98
Training Manual
Antenna Failure Troubleshooting Results

VoIP Handset: “ERROR : Antenna Failure”
BGAN alarm
WARNING: Antenna Cross-elevation motor.
Event List: Figure 5-103
Figure 5-101
Event Log:
Diagnostic Report:
debug:/$ eventhandler -l
5
Event log:
Time [id subid unit] (severity state occurence) text
Wed Jan 06 19:17:22 2010 [09009 0 204] (WARNING OFF
1) EV_ATB_CROSS_ELEVATION_MOTOR_VOLTAGE NOTE!
Wed Jan 06 19:17:23 2010 [09009 0 204] (WARNING ON The Event Log identifies a
problem in the Cross Elevation
2) EV_ATB_CROSS_ELEVATION_MOTOR_VOLTAGE motor which is not using the
correct Voltage.
Wed Jan 06 19:21:16 2010 [09009 0 204] (WARNING OFF
3) EV_ATB_CROSS_ELEVATION_MOTOR_VOLTAGE
Wed Jan 06 19:29:32 2010 [08027 0 1 ] (INFO NONE
4) EV_BDU_AL_REGM_HANDOVER (156)
Figure 5-102
All errors reported by the Fleet broadband system are indicating a
problem with the Cross Elevation Motor. We will need to physically
inspect the ADU Cross Elevation Motor.
Additional Equipment Needed
• Torx-screwdriver, size: No. 8
• Torx-screwdriver, size: No. 25
• 1.5 mm Allen wrench
174 Chapter 5
Troubleshooting
Remove the Antenna dome to inspect the Cross Elevation

Motor
• Turn off power to the Fleet Broadband System.
• Using the torx 25 screwdriver carefully remove the 10 torx 25
screws that secure the dome.
• Remove the top of the radome to access the antenna modules.
Lift the dome straight off to avoid damaging the antenna
panel.
• Rotate the antenna panel to gain access to the cross elevation
motor to the rear of the Antenna panel.
• Visually inspect the cross elevation motor. No Indication of a
problem is evident.
Figure 5-104 • Try and turn the gear on the motor. Motor is frozen/ locked up
and will not turn. Replace the Motor.
Replace the Cross Elevation Motor
• Disconnect the power plug going to the Elevation Motor.
5 NOTE! Please remember to release the connector latch on the

connector. Do not use the wires to pull out the plug.
• Loosen the four (4) screws by use of the Torx-8 screwdriver.
• Remove the tension of the belt, and remove it from the pulley
Figure 5-105 of the motor.
• Remove the two 1.5mm allen screws from the pulley gear.
• Remove the pulley gear from the shaft.
• Remove the four (4) screws by use of the Torx-8 screwdriver.
• Retract the motor and pulley from the antenna pedestal.
• Replace all items in the reverse order.
Figure 5-106 NOTE! The tension of the belt should be identical to the rest of
the belts.
Apply power to the terminal and confirm the error is resolved /
cleared from the Fleet BroadBand system.
Ensure the status LEDs on the terminal is reporting normal
operation.
Figure 5-107
Training Manual
NOTE!
Event list and Event log:
Ensure the logs have no
reported errors.
Figure 5-108
NOTE!
Extended Status: Ensure the
terminal is registered on the
network.
Figure 5-109
Removal & Replacement
Training Manual
6 Removal & Replacement NOTE!

Parts not available on the
This chapter will describe removal and replacement (R&R) of eShop is not considered as a
Spare Part, and we can not
some of the parts of the SAILOR FleetBroadband systems, which deliver these items.
by Cobham SATCOM is considering as Spare Parts, that can be
found on our eShop (http://shop.thrane.com/).
6.1 R&R of SAILOR 500 ®
FleetBroadband
Only the Power Supply Module (PSM) within the BDU /Terminal
can be replaced. The Main Board is not a replacable item. If a
BDU /Terminal problem is not solved or to be solved by PSM
replacement, the complete BDU /Terminal should be replaced.
The Thrane IP Handset is seen as one closed unit, which does
not contain replaceable parts. If defective, replace the Thrane IP
Handset complete.
The Cradle for Thrane IP Handset is seen as one closed unit,
which does not contain replaceable parts. If defective, replace the
Cradle complete.
The AC/DC Power Supplies PS-4655 and TT-6080A are seen
as closed units, which except fuses does not contain replaceable
6
parts. If defective, replace the AC/DC Power Supply complete.
The repair and replacement of the SAILOR 500 FleetBroadband
ADU is divided into two sections, one for TT-3740A and one for
TT-3740B.
6.1.2 R&R of BDU /Terminal Power Supply Module

Removal:
1. Remove the six (6) Philips screws at the bottom of the BDU /
Terminal. Put aside the screws as they are going to be reused
in the replacement of the PSM.
2. Remove the two times five (2 x 5) Torx 10 screws on the right
and left bracket on the top of the BDU /Terminal. Put aside
the screws and brackets as they are going to be reused in the
replacement of the PSM.
3. Separate top and bottom of the BDU /Terminal.
4. PSM is located in the top of the casing.
5. Disconnect the wires (connector) for the Power Switch.
Release the latch by pressing down and slide connector
towards teh switch.
6. Remove the two (2) special screcs at either side of the Power
connector. Put aside the screws as they are going to be reused
7. Remove nineteen (19) Philips screws from the PSM PCB.
Put aside the screws as they are going to be reused in the
8. Remove PSM PCB.
180 Chapter 6
Replace:
1. Insert the Power Supply Module (S-60-124511) into the top
casing of the BDU /Terminal.
2. Insert the nineteen (19) Philips screws on the PSM PCB and
tighten with no more that 1 Nm.
3. Insert the two (2) special screws on either side of the Power
connector. Tighten with no more than 1 Nm.
4. Connect the connector for the Power switch. A click should be
heard.
5. Carefully assemble the two halves of the BDU /Terminal.
6. Insert the six (6) Philips screws at the bottom of the BDU /
Terminal. Tighten the screws with no more than 1 Nm.
7. Insert the two times five (2 x 5) Torx 10 screws on the two
brackets on either side of the BDU /Terminal at the front. Do
not tighten with more than 1 Nm.
6.2 TT-3740A SAILOR 500 ®
FleetBroadband ADU
Figure 6-1 and 6-2: TT-3052A ADU, rear and front

Training Manual
Following items are described:

1. S-41-127510-A Radome Top
2. S-88-126533-A ATB /LNA Module
3. S-88-127532-A X-Elevation Motor
4. S-60-124765 GPS Module
5. S-88-127532-A Elevation Motor
6. S-62-124671 HPA Module
7. S-88-127261-A Azimuth Stepmotor
6.2.1 R&R of Radome Top
6
Figure 6-3: TT-3052A ADU, radome top
Remove:
1. Remove the antenna Radome Top starting with removing the
ten (10) M5 Allen screws from the bottom side of the ADU,
around the rim.
CAUTION!
2. Lift straight up the Radome Top, to get it free of the pedestal Take care that the Radome
and antenna panel. Gasket (S-41-127508-A) is not
being or getting damaged.
Replace:
1. Clean and check for damage the Radome Gasket (S-41-
127508-A) around the rim of the Radome bottom.
If the gasket is dried out, a thin layer of silicone grease should
be applied. If cracked or other vise damaged, the gasket
should be replaced.
2. Lower the Radome Top over the pedestal and antenna panel.
3. Align the labels on the Radome Top so the SAILOR labels are
parallel to the centre line of the vessel and the yellow warning
label towards the rear of the vessel.
4. Insert the ten (10) M5 Allen screws and tighten to 2.5 Nm.
Cross-tightening the screws.
182 Chapter 6
6.2.2 R&R of Antenna Tracking Board /Low Noise

Amplifier Module
1
4 2
Figure 6-4a: LNA close-up.

1. From antenna panel (right Figure 6-4: TT-3052A ADU, ATB/LNA Module
side seen from rear)
Removal:
2. Brown cable from HPA (TX)
3. From antenna panel (left side
1. Remove the Radome Top as described in the previous section
seen from rear) Remove & replacement of Radome Top.
4. Black cable to HPA (RX) 2. Disconnect the six (6) plugs indicated above.
NOTE! 3. Carefully lift the cable holder, positioned at the bottom of the
Remember to release
connector latches on the plugs
ATB/LNA Module, and release the cables.
(the two (2) squared plugs) 4. Unscrew and remove the two (2) big finger nuts, put aside as
before pulling them off.
they are going to be reused in the replacement of the ATB/
NOTE! LNA.
6
Do not pull the wires - pull the
plugs. 5. Carefully remove the ATB/LNA from the antenna panel.
Replace:
1. Carefully position the new ATB/LNA (S-88-126533-A) over the
studs on the antenna frame.
2. Fasten the two (2) finger nuts (removed in above Removal:
step 4) with no more than 1.2 Nm.
NOTE! 3. Reconnect the plugs (follow the note above), make sure that
A click should be heard when
the plug is fully inserted.
they are properly fitted.
4. Carefully lift the cable holder and fit the cables in the holder.
5. Reinstall the Radome Top as described in previous section
Removal & replacement of Radome Top.
6.2.3 R&R of Cross-Elevation Motor
Figure 6-5 and 6-6: TT-3052A ADU, Cross-Elevation Motor

The Cross-Elevation Motor and the Elevation Motor are identical
type of motors.
Training Manual
Removal:
Remove & replacement of Radome Top.
NOTE!
2. Disconnect the plug from the Cross-Elevation Motor and the Remember to release
jack, assembled behind the Cross-Elevation Motor on the connector latch on the plug
bracket holding the motor. before pulling it off.
3. Loosen the two (2) 1.5 mm pilot screws on the gear wheel NOTE!
(pulley) at the shaft of the Cross-Elevation Motor. Do not pull the wires - pull the
plug.
4. Unscrew the four (4) Torx-8 screws holding the Cross-Elevation
Motor in position, put aside as they are going to be reused in
the replacement of the Cross-Elevation Motor.
5. Pull down and out the Cross-Elevation Motor.
6. Remove the now free pulley from top of the motor bracket.
Replace:
1. Insert the new pulley inside the Cross-Elevation drive belt.
2. Insert the new Cross-Elevation Motor (S-88-127532-A) from NOTE!
below, through the hole in the motor bracket, and catch the Orientate the Cross-Elevation
centre hole of the pulley. Motor so that the wires from
the motor can reach the
3. Insert, but do not tighten, the four (4) Torx-8 screws (removed connection point.
in above Removal: step 4) fixing the Cross-Elevation Motor to
6
the motor bracket.
4. Adjust the position of the pulley on the shaft of the Cross-
Elevation Motor, so that the drive belt has a straight line
between the drive pulleys. NOTE!
The tension of the drive belt
5. Tighten the two (2) 1.5 mm pilot screws no more than 1.0 should be identical to the
Nm. rest of the drive belts in the
antenna.
6. Tighten the four (4) Torx-8 screws with no more than 1.2 Nm.
7. Connect the plug from the Cross-Elevation Motor to the jack.
8. Manually check the movement of the antenna panel to verify NOTE!
no jam. the plug is fully inserted.
184 Chapter 6
6.2.4 R&R of GPS Module (Global Position

System Module)
Figure 6-7: TT-3052A ADU, Global Position System Module

Removal:
NOTE! 2. Disconnect the plug and wires from the GPS Module (rear left
Remember to release hand side of the module).
connector latch on the plug
before pulling it off. 3. Unscrew the four (4) Torx-8 screws holding the GPS Module
NOTE! in position.
6
Do not pull the wires - pull the 4. Remove the GPS Module.
plug.
Replace:
NOTE!
Orientate the GPS Module so
1. Insert the new GPS Module (S-60-124765) and position on
that the wires from the HPA the nuts.
can reach the connector of the
GPS Module.
2. Insert the four (4) new Torx-8 screws and tighten with no more
than 1.0 Nm.
3. Connect the plug and wires from the HPA.
NOTE!
the plug is fully inserted. Remove & replacement of Radome Top.
6.2.5 R&R of Elevation Motor
Figure 6-8 and 6-9: TT-3052A ADU, Elevation Motor

The Cross-Elevation Motor and the Elevation Motor are identical
type of motors.
Training Manual
Removal:
Remove & replacement of Radome Top.Disconnect the plug
from the Elevation Motor and the jack, assembled in front of NOTE!
the Elevation Motor on the bracket. Remember to release
connector latch on the before
2. Unscrew the four (4) Torx-8 screws holding the Elevation pulling it off.
Motor in position, put aside as they are going to be reused in NOTE!
the replacement of the Elevation Motor. Do not pull the wires - pull the
plug.
3. Remove the tension of the drive belt by pushing the Elevation
Motor forward and remove the drive belt from the pulley (gear
wheel).
4. Retract the motor with pulley through the hole in the pedestal.
Replace:
1. Measure the distance (d) from motor housing to the pulley
of the removed Elevation Motor. (See Figure 6-9a: Elevation
Motor)
2. Measure the distance d found (in Replace, step 1) and mark
it up on the shaft of the new Elevation Motor (S-88-127532-A).
3. Install the new pulley on the new Elevation Motor, and tighten
the two (2) 1.5 mm pilot screws no more than 1.0 Nm.
6
4. Install the Elevation Motor through the hole in the pedestal. Figure 6-9a: Elevation Motor
5. Thread the drive belt over the pulley.

6. Insert, but do not tighten, the four (4) Torx-8 screws (removed NOTE!
Orientate the Elevation
in above Removal: step 2) fixing the Elevation Motor to the Motor so that the wires from
pedestal. the motor can reach the
connection point.
7. Check the position of the pulley on the shaft of the Elevation
Motor, so that the drive belt has a straight line between the
drive pulleys.
NOTE!
8. Tighten the four (4) Torx-8 screws with no more than 1.2 Nm. The tension of the drive belt
9. Connect the plug from the Elevation Motor to the jack. should be identical to the
rest of the drive belts in the
10. Manually check the movement of the antenna panel to verify antenna.
no jam.
NOTE!
11. Reinstall the Radome Top as described in previous section A click should be heard when
Remove & replacement of Radome Top. the plug is fully inserted.
186 Chapter 6
6.2.6 R&R of HPA Module (High Power Amplifier)
Figure 6-10: TT-3052A ADU, HPA

Removal:
NOTE!
Remember to release
2. Disconnect the seven (7) plugs indicated above.
connector latches on the plugs 3. Carefully lift the four (4) cable holders two (2) on the front of
(the seven (7) squared plugs)
the HPA and two (2) at by the top left corner and release the
cables.
NOTE!
Do not pull the wires - pull the 4. At the rear side of the HPA, unscrew the four (4) big finger nuts,
plugs. put aside as they are going to be reused in the replacement
6 of the HPA.
5. Carefully remove the HPA from the pedestal (the fan of the
HPA is to be slide out the pedestal).
Replace:
1. Slide carefully the new HPA (S-62-124671) into position with
the fan of the HPA into the pedestal. Fit the studs on the rear
side of the HPA into the pedestal.
NOTE!
2. Fasten the four (4) finger nuts (removed in above Removal:
A click should be heard when step 4) with no more than 1.2 Nm. Reconnect the plugs make
the plug is fully inserted. sure that they are properly fitted.
3. Carefully lift the cable holders and fit the cables in the
holders.
Training Manual
6.2.7 R&R of Azimuth Stepmotor
Figure 6-11 and 6-12: TT-3052A ADU, Azimuth Stepmotor

Removal:
Remove & replacement of Radome Top. NOTE!
Remember to release
2. Disconnect the plug from the Azimuth Stepmotor and the jack, connector latch on the before
6
assembled in right hand side of the Azimuth Motor arm. pulling it off.
3. Unscrew the four (4) M4 Allen screws (one in each corner NOTE!
of the motor) holding the Azimuth Stepmotor in position, put Do not pull the wires - pull the
plug.
aside as they are going to be reused in the replacement of the
Azimuth Stepmotor.
4. Remove the tension of the drive belt by unscrewing the four (4)
Torx-8 screws (located at the side of the arm fixing the motor-
“sledge” to the arm) and slide the motor-“sledge” towards the
Rotary Joint. Put aside the Torx-8 screws as they are going to
be reused in the replacement of the Azimuth Stepmotor.
5. Unstring the drive belt from the Azimuth Stepmotor pulley.
6. Retract the motor with pulley through the hole in the motor-
“sledge”.
Replace:
NOTE!
1. Install the new Azimuth Stepmotor (S-88-127261-A) through Orientate the Elevation
the hole in the motor-”sledge”. Motor so that the wires from
the motor can reach the
2. Thread the drive belt over the pulley. connection point.
3. Insert, but do not tighten, the four (4) Torx-8 screws (removed
in above Removal: step 4) fixing the motor-”sledge” to the
arm. NOTE!
4. Check the position of the pulley on the shaft of the Azimuth should be identical to the
Stepmotor, so that the drive belt has a straight line between rest of the drive belts in the
the drive pulleys. antenna.
188 Chapter 6
6. Insert, and tighten, the four (4) M4 Allen screws (removed in

above Removal: step 3) fixing the Azimuth Stepmotor to the
arm.
7. Connect the plug from the Azimuth Stepmotor to the jack.
NOTE!
8. Manually check the movement of the antenna pedestal to
the plug is fully inserted. verify no jam.
6
Training Manual
6.3 TT-3740B and TT-3740C SAILOR ®
500 FleetBroadband ADU
Figure 6-13 and 6-14: TT-3052B ADU, rear and front

1. S-41-130520-A Radome Top (for ADU ver. B)
2. S-82-130946 Radome Top (for ADU ver. C)
6
3. S-62-128257 Antenna Tracking Receiver ATR
4. S-62-128256 Antenna Tracking Module ATM
6. S-62-129951 HPA Complete
Please be informed that neither of the motors or drive belts are
spare parts or replaceable items.
6.3.1 R&R of Radome Top (for ADU ver. B)
Figure 6-15: TT-3052B ADU, radome top

Removal:
ten (10) M5 Allen screws from the bottom side of the ADU,
around the rim.
190 Chapter 6
CAUTION! 2. Lift straight up the Radome Top, to get it free of the pedestal
Take care that the Radome and antenna panel.
Gasket (S-41-127508-A) is not
being or getting damaged.
Replace:
1. Clean and check for damage the Radome Gasket S-41-
129829 around the rim of the Radome bottom.
be applied. If cracked or other vise damaged, the gasket
should be replaced.
3. Align the labels on the Radome Top so the SAILOR labels are
parallel to the centre line of the vessel and the yellow warning
4. Insert the ten (10) M5 Allen screws and tighten to 2.5 Nm.
Cross-tightening the screws.
6.3.2 R&R of Radome Top (for ADU ver. C)
Figure 6-16: TT-3052C ADU, radome top.

Removal:
1. Remove the antenna radome Top starting with removing the
twelve (12) M5 Allen screws from the bottom side of the ADU,
around the rim.
2. Lift straight up the Radome Top, to get it free of the pedestal
and antenna panel.
Replace:
1. Lover the Radome Top over the pedestal and antenna panel.
2. Align the label on the Radome Top so the SAILOR labels are
parallel to the center line of the vessel and the yellow warning
3. Insert the twelve (12) M5 Allen screws and tighten to 2.5 Nm.
Cross-tighten the screws.
Training Manual
6.3.2 R&R of Antenna Tracking Receiver Module

(ATR)
Figure 6-17: TT-3052B/C ADU, Antenna Tracking Receiver Module

Removal:
1. Remove the Radome Top as described in the previous section NOTE!
Remove & replacement of Radome Top. Take a note of the exact
position of each plug.
2. Disconnect the five (5) plugs of the ATR Module, two (2) on the
left hand side and three (3) on the right hand side. NOTE!
3. Unscrew the two (2) 5 mm hex screws on either side of the plugs.
ATR Module, put aside the screws as they are going to be
reused in the replacement of the ATR Module.
4. Carefully remove the ATR Module.
Replace:
6
1. Carefully position the new ATR Module (S-62-128257) over
the studs on the antenna frame.
2. Fasten the two (2) 5 mm HEX screws (removed in above
Removal: step 3) with no more than 1.2 Nm.
NOTE!
3. Reconnect the plugs (follow the diagram below), make sure A click should be heard when
that they are properly fitted. the plug is fully inserted.
Figure 6-18: TT-3052B/C ADU, ATR to ATM connection

192 Chapter 6
6.3.3 R&R of Antenna Tracking Module (ATM)
Figure 6-19 and 6-20: TT-3052B/C ADU, Antenna Tracking Module and its Sensor PCB
The Sensor PCB is a part of the Antenna Tracking Module and
they will be replaced together.
Remove:
2. Unscrew the three (3) Torx-10 screws, holding the Sensor PCB
to the cross-elevation mechanism, put aside the screws as
they are going to be reused in the replacement of the Antenna
Tracking Module.
6
NOTE! 3. Cut the cable ties fixing the Sensor cable to the cross-elevation
Take a note of the exact beam and the antenna beam.
position of each plug.
4. Carefully lift the cable holders, positioned on the cross-
NOTE! elevation beam.
Remember to release
connector latches on the plugs 5. Carefully slide the out under the cross-elevation beam.
before pulling it off. 6. Disconnect the seven (7) plugs on the Antenna Tracking
NOTE! Module (three (3) on top and four (4) on front of the Antenna
Do not pull the wires - pull the Tracking Module).
plugs.
7. Unscrew the six (6) 5 mm hex screws holding the Antenna
NOTE! Tracking Module to the cross-elevation beam, put aside the
The Sensor PCB have to be screws as they are going to be reused in the replacement of
slided through the big squared the Antenna Tracking Module.
hole in the antenna beam.
8. Carefully remove the Antenna Tracking Module and the Sensor
PCB.
Replace:
1. Carefully guide the Sensor PCB through the squared hole
in the antenna beam and position the Antenna Tracking
Module (S-62-128256) and insert the six (6) 5 mm hex screws
(removed in above Removal: step 7) and tighten with no more
than 1.2 Nm.
2. Reconnect the plugs (follow the diagram in Figure 6-18a ATM
connectors) make sure that they are properly fitted.
3. Carefully slide the Sensor PCB under the cross-elevation
beam and install it with the three (3) Torx-10 screws (removed
in above Removal: step 2) and tighten with no more than 1.0
Nm.
Figure 6-19a: ATM connectors
4. Carefully lift the cable holders (opened in above Removal:
Training Manual
step 4) and fit the cables in the holder.

5. Refit cable ties and make sure that the Antenna Panel can
move freely, without the Sensor PCB cable is obstructing the
movements (both elevation and cross-elevation).
6. Reinstall the Radome Top as described in previous section NOTE!
Remove & replacement of Radome Top. A click should be heard when
6.3.4 R&R of GPS Module (Global Position

System)
Removal:
Figure 6-21: TT-3052B/C ADU, GPS Module
6
NOTE!
2. Disconnect the plug from the GPS Module (located under the Remember to release
plate through the squared hole). connector latch on the plug
before pulling it off.
3. Unscrew the four (4) Torx-10 screws (from below side),
put aside the screws as they are going to be reused in the NOTE!
replacement of the GPS Module. Do not pull the wires - pull the
plug.
4. The GPS Module is now free and can be removed.
Replace:
1. Place the GPS Module (S-60-124765) under the hole in the
frame with the GPS antenna pointing upwards.
2. Insert the four (4) Torx-10 screws (removed in above Removal:
step 3) and tighten no more than 1.0 Nm.
3. Reconnect the plug.
Remove & replacement of Radome Top. A click should be heard when
194 Chapter 6
6.3.5 R&R of HPA Module (High Power Amplifier)
Figure 6-22 and 6-23: TT-3052B/C ADU, High Power Amplifier Module, front and rear view
Removal:
NOTE! 1. Remove the Radome Top as described in the previous section
Remember to release Remove & replacement of Radome Top.
6
before pulling it off. 2. Disconnect seven (7) plugs (two (3) at the top, two (2) at the
NOTE! bottom left hand side, one (1) at the bottom and one (1) at the
Do not pull the wires - pull the front) at the High Power Amplifier Module.
plugs.
3. Cut the cable ties holding the wires from the fan, on
the rear side of the High Power Amplifier Module.
4. Carefully lift the cable holders, positioned on the front side of

the High Power Amplifier Module and on the rear side of the
pedestal.
5. Unscrew the six (6) 6 mm nuts on the rear side of the High
Power Amplifier Module, put aside the nuts as they are going
to be reused in the replacement of the High Power Amplifier
Module.
6. Carefully slide out the High Power Amplifier Module until the
fan of the HPA is free, Remove the HPA.
Replace:
1. Carefully slide in the fan of the High Power Amplifier (S-62-
129951), through the hole in the pedestal.
2. Fit the six (6) 3 mm nuts (removed in above Removal: step 5)
and tighten with no more than 1.2 Nm.
3. Reconnect the seven (7) plugs.
NOTE!
A click should be heard when 4. Carefully lift the cable holders (opened in above Removal:
the plug is fully inserted. step 4) and fit the cables in the holder.
5. Fit new cable ties (cut in above Removal: step 3) on the wires
from the fan.
Training Manual
FleetBroadband
Only the Power Supply Module (PSM) within the BDU /Terminal
can be replaced. The Main Board is not a replacable item. If a
BDU /Terminal problem is not solved or to be solved by PSM
replacement, the complete BDU /Terminal should be replaced.
6.4.1 R&R of BDU /Terminal Power Supply

Module.
Removal:
1. Remove the six (6) Philips screws at the bottom of the BDU /
Terminal. Put aside the screws as they are going to be reused
2. Remove the two times five (2 x 5) Torx 10 screws on the right
and left bracket on the top of the BDU /Terminal. Put aside
the screws and brackets as they are going to be reused in the
3. Separate top and bottom of the BDU /Terminal.
4. PSM is located in the top of the casing.
6
5. Disconnect the wires (connector) for the Power Switch.
Release the latch by pressing down and slide connector
towards teh switch.
6. Remove the two (2) special screcs at either side of the Power
connector. Put aside the screws as they are going to be reused
7. Remove nineteen (19) Philips screws from the PSM PCB.
Put aside the screws as they are going to be reused in the
8. Remove PSM PCB.
Replace:
1. Insert the Power Supply Module (S-60-124511) into the top
casing of the BDU /Terminal.
2. Insert the nineteen (19) Philips screws on the PSM PCB and
tighten with no more that 1 Nm.
3. Insert the two (2) special screws on either side of the Power
connector. Tighten with no more than 1 Nm.
4. Connect the connector for the Power switch. A click should be
heard.
5. Carefully assemble the two halves of the BDU /Terminal.
6. Insert the six (6) Philips screws at the bottom of the BDU /
Terminal. Tighten the screws with no more than 1 Nm.
7. Insert the two times five (2 x 5) Torx 10 screws on the two
brackets on either side of the BDU /Terminal at the front. Do
not tighten with more than 1 Nm.
196 Chapter 6

Handset complete.
Cradle complete.
ADU is described here.
6.4.2 TT-3742A SAILOR 250 FleetBroadband ADU

®
6
1. S-62-126078 Radome Top
2. S-62-126083 Assembled Electronic Cover Unit
4. S-60-124671 BGAN-X HPA
5. S-60-124898 DLNA
6.4.2.1 R&R of Radome Top
Figure 6-25: TT-3050A ADU, radome top

Training Manual
Removal:
six (6) M5 Allen screws from the bottom side of the ADU,
around the rim. Put aside the screws as they are going to be
reused in the replacement of the Radome Top.
2. Lift straight up the Radome Top, to get it free of the pedestal
and antenna panel.
Replace:
1. Clean and check for damage the Radome Gasket around the
rim of the Radome bottom.
be applied.
3. Align the labels on the Radome Top so the SAILOR label is
towards the bow of the vessel and the yellow warning label
towards the rear of the vessel.
4. Insert the six (6) M5 Allen screws (removed in above Removal:
step 1) and tighten to 2.5 Nm. Cross-tightening the screws.
6.4.2.2 R&R of Assembled Electronic Cover Unit
Figure 6-26: TT-3050A ADU, Assembled Electronic Cover Unit

Removal:
2. Unscrew the eighteen (18) Torx-8 screws at the rim of the
Assembled Electronic Cover Unit, put aside the screws as they
are going to be reused in the replacement of the Assembled NOTE!
Electronic Cover Unit. Remember to release
3. Lift carefully the Assembled Electronic Cover Unit a few before pulling it off.
centimetres and tilt it to the side to gain access to the cables.
NOTE!
4. Disconnect the plug from the High Power Amplifier at the Do not pull the wires - pull the
printed circuit board of the Assembled Electronic Cover Unit. plug.
198 Chapter 6
Replace:
1. Check and clean the rim of the new Assembled Electronic
Cover Unit (S-62-126083) and the inside rim of the Radome
Bottom.
2. Reconnect the cable from the High Power Amplifier to the
printed circuit board of the Assembled Electronic Cover Unit.
3. Orientate the Assembled Electronic Cover Unit so the arrow
NOTE! marking with the text “FORE” on the top cover is pointing in
A click should be heard when same direction as the arrow marking with the text “FORE” on
the plug is fully inserted. the bottom of the Radome Bottom.
4. In this position, lower the Assembled Electronic Cover Unit
straight down onto the Radome Bottom and provide a light
pressure to the cover.
5. Fit the eighteen (18) Torx-8 screws (removed in above
CAUTION! Removal: step 2) and tighten with no more than 1.0 Nm.
The RF connector of the Tighten the screws over cross.
Assembled Electronic Cover
Unit and the DLNA is being 6. Reinstall the Radome Top as described in previous section
mated by assembling the Remove & replacement of Radome Top.
Assembled Electronic Cover
and the Radome Bottom.
6.4.2.3 R&R of GPS Module (Global Position System)
Figure 6-27: TT-3050A ADU, GPS Module

Removal:
2. Remove the Assembled Electronic Cover Unit as described in
the previous section Remove & replacement of Assembled
Electronic Cover Unit.
3. Disconnect the plug from the printed circuit board of the
Assembled Electronic Cover Unit at the GPS Module.
4. Unscrew the four (4) Torx-10 screws, put aside the screws as
they are going to be reused in the replacement of the GPS
Module.
5. Remove the GPS Module.
Replace:
1. Insert the new GPS Module (S-60-124765) with the connector
pointing towards the “LOW”-marked motor, and fix it with the
four (4) Torx-10 screws (removed in above Removal: step 4).
Training Manual
Tighten with no more than 1.0 Nm.

2. Reconnect the plug (disconnected in above Removal: step
3).
3. Reinstall the Assembled Electronic Cover Unit as described
in previous section Remove & replacement of Assembled
4. Reinstall Radome Top as described in previous section
6.4.2.4 R&R of BGAN-X HPA (High Power Amplifier)
6
Removal:
3. Disconnect the five (5) plugs at the High Power Amplifier.
NOTE!
4. Unscrew the twelve (12) Torx-8 screws, put aside the screws Remember to release
as they are going to be reused in the replacement of the High connector latch on the plug
Power Amplifier. before pulling it off.
5. Remove the High Power Amplifier from the Radome Bottom. NOTE!
Replace: plug.
1. Apply a layer of Thermal paste (eShop type no.: S-34-201823-
035 or equivalent) on the cooling ribs in the Radome Bottom.
2. Insert the High Power Amplifier (S-60-124671) into the
Radome Bottom.
3. Fit the twelve (12) Torx-8 screws (removed in above Removal:
step 4) and tighten with no more than 1.0 Nm.
4. Reconnect the five (5) plugs (disconnected in above Removal:
step 3). NOTE!
5. Reinstall the Radome Top as described in previous section the plug is fully inserted.
200 Chapter 6
6.4.2.5 R&R of DLNA (Diplexer Low Noise Amplifier)
Figure 6-29: TT-3050A ADU, Diplexer Low Noise Amplifier

Removal:
6 NOTE!
3. Disconnect the two (2) plugs on the Diplexer Low Noise
Do not pull the wires - pull the Amplifier.
plug.
4. Unscrew the five (5) Torx-8 screws, put aside the screws as
they are going to be reused in the replacement of the Diplexer
Low Noise Amplifier.
5. Remove the Diplexer Low Noise Amplifier from the Radome
Bottom.
Replace:
2. Insert the Diplexer Low Noise Amplifier (S-60-124898) into the
Radome Bottom.
3. Fit the five (5) Torx-8 screws (removed in above Removal:
NOTE!
A click should be heard when 4. Reconnect the two (2) plugs (disconnected in above Removal:
the plug is fully inserted. step 3).
Training Manual
FleetBroadband
The BDU /Terminal is seen as one closed unit, which does not
contain replaceable parts. If defective, replace the BDU /Terminal
complete.
Handset complete.
Cradle complete.
ADU is described here.
6.5.1 TT-3744A SAILOR 150 FleetBroadband ADU

®

1. S-62-129156 Radome Top
2. S-62-129082 Assembled Electronic Cover Unit
4. S-60-124671 BGAN-X HPA
5. S-60-124898 DLNA
202 Chapter 6
6.5.1.1 R&R of Radome Top
Figure 6-31: TT-3050C ADU, Radome Top

Removal:
six (6) M5 Allen screws from the bottom side of the ADU,
around the rim. Put aside the screws as they are going to be
reused in the replacement of the Radome Top.
6 2. Lift straight up the Radome Top, to get it free of the pedestal

and antenna panel.
Replace:
1. Clean and check for damage the Radome Gasket around the
rim of the Radome bottom.
2. If the gasket is dried out, a thin layer of silicone grease should
be applied.
4. Align the labels on the Radome Top so the SAILOR label is
towards the bow of the vessel and the yellow warning label
towards the rear of the vessel.
5. Insert the six (6) M5 Allen screws (removed in above Removal:
step 1) and tighten to 2.5 Nm. Cross-tightening the screws.
Training Manual
6.5.1.2 R&R of Assembled Electronic Cover Unit
Figure 6-32: TT-3050C ADU, Assembled Electronic Cover Unit

Removal:
2. Unscrew the eighteen (18) Torx-8 screws at the rim of the
Assembled Electronic Cover Unit, put aside the screws as they
6
are going to be reused in the replacement of the Assembled
3. Lift carefully the Assembled Electronic Cover Unit a few
centimetres and tilt it to the side to gain access to the cables.
NOTE!
4. Disconnect the plug from the High Power Amplifier at the Remember to release
printed circuit board of the Assembled Electronic Cover Unit. connector latch on the plug
Replace:
NOTE!
1. Check and clean the rim of the new Assembled Electronic Do not pull the wires - pull the
Cover Unit (S-62-129082) and the inside rim of the Radome plug.
Bottom.
2. Reconnect the cable from the High Power Amplifier to the NOTE!
printed circuit board of the Assembled Electronic Cover Unit. the plug is fully inserted.
3. Orientate the Assembled Electronic Cover Unit so the arrow
marking with the text “FORE” on the top cover is pointing in CAUTION!
same direction as the arrow marking with the text “FORE” on The RF connector of the
the bottom of the Radome Bottom. Assembled Electronic Cover
Unit and the DLNA is being
4. In this position, lower the Assembled Electronic Cover Unit mated by assembling the
straight down onto the Radome Bottom and provide a light Assembled Electronic Cover
and the Radome Bottom.
pressure to the cover.
5. Fit the eighteen (18) Torx-8 screws (removed in above
Removal: step 2) and tighten with no more than 1.0 Nm.
Tighten the screws over cross.
204 Chapter 6
6.5.1.3 R&R of GPS Module (Global Position System)
Figure 6-33: TT-3050C ADU, GPS Module

Removal:
3. Disconnect the plug from the printed circuit board of the
NOTE! Assembled Electronic Cover Unit at the GPS Module.
6
Remember to release
connector latch on the plug 4. Unscrew the four (4) Torx-10 screws, put aside the screws as
before pulling it off. they are going to be reused in the replacement of the GPS
NOTE! Module.
Do not pull the wires - pull the 5. Remove the GPS Module.
plug.
Replace:
1. Insert the new GPS Module (S-60-124765) with the connector
pointing towards the “LOW”-marked motor, and fix it with the
four (4) Torx-10 screws (removed in above Removal: step 4).
Tighten with no more than 1.0 Nm.
2. Reconnect the plug (disconnected in above Removal: step 3).
NOTE!
the plug is fully inserted. in previous section Remove & replacement of Assembled
4. Reinstall Radome Top as described in previous section
Training Manual
6.5.1.4 R&R of BGAN-X HPA (High Power Amplifier)
Figure 6-34: TT-3050C ADU, High Power Amplifier

Removal:
3. Disconnect the five (5) plugs at the High Power Amplifier.
6
NOTE!
4. Unscrew the twelve (12) Torx-8 screws, put aside the screws Remember to release
as they are going to be reused in the replacement of the High connector latch on the plug
Power Amplifier. before pulling it off.
5. Remove the High Power Amplifier from the Radome Bottom. NOTE!
Replace: plug.
2. Insert the High Power Amplifier (S-60-124671) into the
Radome Bottom.
3. Fit the twelve (12) Torx-8 screws (removed in above Removal:
NOTE!
4. Reconnect the five (5) plugs (disconnected in above Removal: A click should be heard when
step 3). the plug is fully inserted.
206 Chapter 6
6.5.1.5 R&R of DLNA (Diplexer Low Noise Amplifier)
Figure 6-35: TT-3050C ADU, Diplexer Low Noise Amplifier

Removal:
6
NOTE!
Do not pull the wires - pull the 3. Disconnect the two (2) plugs on the Diplexer Low Noise
plug. Amplifier.
4. Unscrew the five (5) Torx-8 screws, put aside the screws as
they are going to be reused in the replacement of the Diplexer
Low Noise Amplifier.
5. Remove the Diplexer Low Noise Amplifier from the Radome
Bottom.
Replace:
2. Insert the Diplexer Low Noise Amplifier (S-60-124898) into the
Radome Bottom.
3. Fit the five (5) Torx-8 screws (removed in above Removal:
NOTE!
A click should be heard when 4. Reconnect the two (2) plugs (disconnected in above Removal:
the plug is fully inserted. step 3).
Training Manual
6
Software Upload
Training Manual
Figure 7-1
212 Chapter 7
Software Upload
7 Software Upload
7.1 Uploading software from your
computer
To upload software from your computer to the terminal, do as
follows:
Download the latest software as described in the next section, or
acquire the software from Cobham SATCOM Download centers
at: http://esupport.thrane.com/index.php?_m=downloads&_
a=view&parentcategoryid=542&pcid=369&nav=0,819,369&
group=default or http://www.cobham.com/about-cobham/
aerospace-and-security/about-us/satcom/lyngby/service-
and-support.aspx Technical Downloads. and save it on your
computer.
Figure 7-2
Open the web interface and do one of the following:
If the PIN has been accepted (or a PIN is not required), select
SETTINGS -> Upload from the left navigation pane.
If a PIN is required and the PIN has not been entered, select
ADMINISTRATION, enter the Administration PIN and password
and click Logon.The default user name is admin and the default
password is 1234.
Then select Upload from the left navigation pane in the fi eld
UPLOAD SOFTWARE TO TERMINAL, click Browse. Browse to
the new software version and accept it.
7
Click the Upload button. Note that the upload procedure takes a
couple of minutes.
7.2 Downloading software from the

WEB MMI
To download the latest software from the Internet to the terminal,
do as follows:
Make sure you have a connection to the Internet from your terminal.
Open the web interface and select SETTINGS > Upload from the
left navigation pane.
Click Check for updates.
The terminal will now connect to the Internet through the BGAN
network, using your airtime subscription. It may take a minute or
two to obtain the new software version.
When the new software version is found, the web interface
shows the new software version and a link for downloading the
software.
Click the link to download the new software to your computer.
After saving the software, follow the procedure in the previous
section (Uploading software from your computer) to upload the
software from the computer to your terminal.
Training Manual
7.3 Forced Software upload NOTE!
Broadband 500 / 250 / 150 / E727 / To activate the reset button,

use a point pen or a paper clip.
E325 Terminals:
In cases where there is no access to the WEB MMI, it will be
necessary to use the building TPTP client to upload the software.
Action Function
With the terminal running, The terminal IP address and IP
press the Reset button netmask are temporarily set to the
normally. default value (default IP address:
Figure 7-4
192.168.0.1).
With this function, even if the IP
adress has been changed and
you do not remember the new IP
address, you can still access the
web interface and see your current
configuration. The default value is
not saved in the configuration, but is
only valid until next reboot.
With the terminal running, The terminal restores factory
press and hold the Reset settings and reboots the system.
button for 30 seconds,
until the Power indicator
on the terminal is flashing
orange.
7
While the terminal is For service use only!
booting, press and hold The bootloader initiates software
the Reset button. upload.
Connect the computer containing
the required software and run a
Telnet session with the terminal
Figure 7-3
1. Prepare the Sailor FBB software image.
2. Download latest version Sailor FBB Software.
3. Rename the file to ttexp.dl
4. Have a TFTP server installed on your pc.
Setup the static IP adr:
On the PC which shall be used to upload the new software image,
change he TCP/IP to Static – 192.168.0.2/24 (disable DHCP)‫‏‬.
Figure 7-5
214 Chapter 7
Software Upload
Setup the TFTP server: (Theo TFTPD32 by Ph. Jounin)

1. Store the Sailor FBB software image to the PC. (In this case
Desktop).
2. Start the TFTP server.
3. Press the Settings button.
4. In the settings page press Browse for Base Directory and
select the folder where the ttexp.dl software image was stored.
(In this case on the Desktop).
Uploading software:
1. Switch OFF the Sailor FBB terminal.
2. Connect the PC to one of the four LAN ports on the Sailor FBB
terminal.
Figure 7-6
3. Switch ON the Sailor FBB terminal while keeping the reset
button pressed.
4. File transfer start.
5. Observe that the terminal located the TFTP server and the file
transfer starts.
6. Release the reset button.
7. File transfer completed.
8. Wait until the file transfer has completed, which takes about 2
Figure 7-7 minutes.
The system will reboot and the software version is updated.  
7
Before using the terminal:
Wait until the terminal has finished uploading antenna
software.
Training Manual
7.4 Forced Software upload Via USB

for BGAN / E700 / E500 Terminal
Uploading software from your computer:
In cases where there is no access to the WEB MMI, it will be
necessary to force the software upload to the terminal.
1. Install USB driver.
2. Prepare the software image.
3. Download latest version Software.
4. Rename the file to ttexp.dl
5. Have a Hyperterminal program installed on your pc.
USB setup (first time only)
Important!!
• The installation procedure is based on a pc running Windows
XP Professional Service Pack 2.
• Make sure that the windows driver usbser.sys is located in the
C:\windows\system32\drivers folder. If not, locate the usbser.
sys driver on the hard drive, and copy it to the C:\windows\
system32\drivers folder.
• If the usbser.sys driver is not located in the C:\windows\
system32\drivers the installation will fail. “not able to install
modem”
How to locate the usbser.sys driver, running Windows XP
7
Professional Service Pack 2.
• The usbser.sys driver is to be found in the directory C:\
WINDOWS\Driver Cache\i386\
• Search on the filename usbser.sys and then copy it to following
destination: C:\WINDOWS\system32\drivers\
• Sometimes Windows can not find it with the search function
because it is inside a CAB file. In that case you need to open
the CAB file:
C:\WINDOWS\Driver Cache\i386\Driver.CAB
and extract the file usbser.sys manually and copy it to following
destination:
C:\WINDOWS\system32\drivers\
216 Chapter 7
Software Upload
Install the USB drivers.

1. Power on the computer.
2. Connect the USB cable to the computer and the terminal USB
port.
3. Power up the terminal.
4. The computer should automatically detect New Hardware is
connected.
5. Follow the New Hardware Wizard steps (Win XP)
• Select NO, not this time when promted if Windows can search
for software.
• Click Next.
Insert Thrane CD-ROM or location of USB driver if downloaded
from the extranet.
When asked ‘What do you want the wizard to do?’
• Select ‘Install from a list or specific location (Advanced)
• Select ‘Next’
When asked ‘Don’t search. I will choose the driver to install’
• Select ‘Have Disk…’
In the new window ‘Install From Disk’
• Select ‘Browse…’
7
• Open the local folder
• Select ‘OK’
In the new window ‘Hardware Installation’

If warning appears the software has not passed Windows
logo testing, click continue anyway.
Click finish when installation is complete.
Note: This process may need to be repeated several (3)

times.
Go to the Device Manager on the computer and verify that

the list of modems in the Device Manager list two ports
called Thrane & Thrane Explorer port 1 and Thrane & Thrane
Explorer port 2.
Go to the Phone and Modem Options in the Control Panel
to verify what COM port has been assigned to the Thrane &
Thrane Explorer port 1, as this will vary on each PC.
Note: that the Thrane & Thrane Explorer port 1 has been
Training Manual
assigned Com port 12 in this example.
Configure HyperTerminal Settings
You must first create a Hyperlink connection from your computer to

the terminal using your COM port connection on your computer.
On Your Computer:
Go to: Start, Programs, Accessories, Communications,
HyperTerminal and press Enter.
Name your HyperTerminal connection and press OK.
3. In the HyperTerminal menu

Select ‘File->Properties’
Select in ‘Connect using’ the new COM port which appeared in
your COM port list of ‘Phone and Modem Options’ above.
Do not select ‘Thrane & Thrane EXPLORER port x’, you have to
select a ‘COM’ port (in this example COM 12).
4. Test that you have selected the right COM port.

Write in HyperTerminal the AT command ‘ATI’.
7
Response from the AT shell ‘Thrane & Thrane’
Software Upload Procedure
Set up.
Power down the terminal (remove battery and install it again), press
the C key and keep it pressed while switching ON the terminal.
Release the C bottom after 5 sec.
This shall bring the terminal into ”software upload mode”
Connect the terminal to a pc via USB.

Start the Hyper Terminal program.
When C C C C appears, start transferring the downloaded
software.
If the CCCCCCC do not appear, ship the terminal to repair!
The procedure is based on Windows XP running in windows

‘Classic Start menu’
218 Chapter 7
Software Upload
Upgrade Applications Code
Download the latest Explorer software from the T&T Extranet.

Store it in a local folder, and unzip it. The software file has the
extension .dl
Write in HyperTerminal ‘ATE1’ in order to enable echo (allowing to
see what is written in terminal mode)
Write in HyperTerminal ‘at+thrane’
Username = admin
Password = 1234 (unless password has been changed from
default 1234)
Now in debug shell type: ‘at-usb0:/$’
Write in HyperTerminal in the debug shell prompt ‘download 30’
You have now started the ‘EXPLORER’ for downloading the new
Applications code within a period of 30 seconds.
Important: From the time of entering the command ‘download 30’ -

Section 4 and 5 above needs to be performed within the specified
time; in this case 30 seconds.
If you get an error message ‘Cxmodem error’ from the debug shell
just repeat the download again starting from the step above but
7
this time with a higher delay value.
5. In the HyperTerminal menu

Select ‘Transfer->Send File…’
6. Select in the new window ’Send File’
Select ‘Browse..’
Open the downloaded file
Select ‘Protocol: 1K Xmodem’
Select ‘Send’
Now the new Applications code is downloaded with the xmodem
1-k protocol from HyperTerminal.
The terminal will now reboot. DO NOT SWITCH
OF THE TERMINAL. The Terminal must be allowed to reboot.
In the HyperTerminal menu
Select ‘Call->Disconnect
Training Manual
Confirm Software Upload
Using the keypad to confirm the software upload was sucessful,

go to:
Press the Down arrow until PROPERTIES is displayed.
Press OK.
Press the Down arrow until TERMINAL is displayed.
Press OK.
Press the Down arrow until SOFTWARE is displayed.
Press OK.
Confirm the latest software is displayed.
7
System Test
Training Manual
8 System Test
To test the RJ11 interface: (if installed)
• Connect an analog phone to the RJ11#1:
• Call from the RJ11#1 interface to a landline.
• Call from a landline to the ship, using the standard voice service
(MSISDN number).
Example:
To make a call to Thrane & Thrane in Denmark dial 004539558800
followed by #.
To make a call to the terminal dial 0087077xxxxxxx.
To test the Fax: (if installed)
• Connect a G3 fax to the RJ11#2.
• Send a fax from the ship to a landline.
• Send a fax to the ship from a landline, using the 3.1 kHz service
(AMISDN number).
Example:
followed by #.
To test the IP handset:
• Select the bgan menu.
• Read out the C/No.
• Call from the IP handset to a landline.
8
(MSISDN number).
Example:
To make a call to Thrane & Thrane in Denmark 004539558800
followed by off-hook key.
To test the ISDN interface: (if installed)
• Connect an isdn phone to the ISDN interface.
• Call from the ISDN interface to a landline.
(MSISDN number).
Example:
followed by #.
224 Chapter 8
System Test
To test the Local Exchange: (if selected)

• With standard enabled and 3.1khz disabled.
(MSISDN number).
• Note thet you get the voice prompt from the terminal.
Figure 8-1
• Dial a local extension.
• Terminate the call.
(MSISDN number)
• Wait 10 sec, and note that the default number is called.
• Call from a landline to the ship, using the 3.1khz audio service
(AMSISDN number)
• Note that the Local Exchange do not response.
To test the data connection:
• Connect a pc to the terminal.
• Open a browser. i.e 192.168.0.1
• Click the “Start Standard” to start the data connection.
• Observe that “Outgoing Data Session” goes “Standard data”
with an IP address.
Figure 8-2 • (Click Refresh a couple of times)
Connect to www.thrane.com.
To test the SMS service:
• Connect a pc.
• Open a browser. i.e 192.168.0.1.
• Sending an SMS message.
8 Figure 8-3
• Click MESSAGES from the left navigation pane.
• This page contains new incoming messages.
• In the left navigation pane, click Write message.
• Type in the message in the Write new message field.
• If the message text is too long for one SMS, the message is sent
as two or more SMS messages. The field below the message
field shows the number of SMS messages used to send the
Figure 8-4 message.
• Type in the phone number in the Recipient field.
• Remember 00 and country code (e.g. 00 45 to call Denmark
or 00 1 to call USA).
• Click Send.
Training Manual
Receiving a message:
• If a message has arrived, the icon bar at the top of the web
interface shows an unopened envelope. Click the envelope to
see the new message(s). Otherwise, to see new messages
click MESSAGES from the left navigationpane.
• The page shows new incoming messages.
• If the message is not an SMS message but information of voice Figure 8-5
mail, call your voice mail service number to hear the voice mail.
To find your voice mail number, select MESSAGES > Message
settings from the left navigation pane and locate the Voice mail
number. Note that the voice mail number is only shown if it is
available on the SIM card. Otherwise, refer to the information
included with your Airtime subscription.
8
Abbreviation
Training Manual
9 Abbreviation
AC Alternating Current
Americas: I4 satellite at 98W
A-Pac: I4 satellite at 143E
APN Access Point Name
Azimuth horizontal direction angle between north and, e.g. the
direction to the satellite.
Bit rate the number of bits transmitted per second (bps).
Bluetooth Wireless computer interface.
Bps Bits per second.
BGAN Inmarsat Broadband Global Area Network, mobile
communications service
providing simultaneous voice and data.
BT Bluetooth
CBR Constant Bit Rate
CHV2 higher access level on the SIM card.
CS Circuit Switched service.
DC Direct Current.
Dongle Bluetooth device that connects to the PC.
DP Distribution Partner
DSP Digital Signal Processor.
DTE Data Terminal Equipment.
DUN Dial Up Network.
Elevation vertical angle to the satellite, i.e. the height of the satellite
above the horizon.
EMEA: I4 satellite at 25E
Ethernet Local Area Network (LAN)
GPRS General Packet Radio Service.
GPS Global Positioning System.
IMN Inmarsat Mobile Number, a unique 9-digit number which
9
identifi es each device connected to the Nera WorldPro terminal.
Inmarsat International Maritime Satellite Organisation.
IMEI International Mobile Equipment Identifi er, a unique number
that can be found on
the label inside the battery compartment of the Interface Unit.
IMSI a unique SIM card number
IP Internet Protocol
ISDN Integrated Services Digital Network.
ISN Inmarsat Serial Number, individual number assigned to each
WorldPro terminal.
230 Chapter 9
Abbreviation
ITU International Telecommunications Union

Kbps Kilobits per second.
LAN Local Area Network.
LaunchPad Inmarsat BGAN PC software.
LED Light Emitting Diode
MES Mobile Earth Station, a user terminal for an Inmarsat system;
the Nera WorldPro terminal is an MES for the Inmarsat BGAN
system.
Modem Device/driver for conveying digital data.
MSN Multiple Subscriber Number, the extension number that
connected equipment responds to.
OSI: Open Systems Interconnection (OSI) standard
Ocean Region the coverage area of an Inmarsat satellite.
PABX Private Automatic Branch Exchange.
PDU: Protocol Data Units
PIN Personal Identifi cation Number.
PoE: Power over Ethernet
PPP Point-to-Point Protocol used for serial data communication.
PPPoE: Point-to-Point Protocol over Ethernet. PPP over
Ethernet.
PS Packet Switched data service.
PSTN Public Switched Telephone Network
PUK Personal Unblocking Key, code that allows unblocking
a SIM card.
QoS Quality of Service
RF Radio Frequency.
SAS Satellite Access Station, a station that interconnects fixed
telecommunications networks with the Inmarsat system.
9
SIM Subscriber Identity Module
SMS Short Message System.
DP: Distribution partner = Service Provider
Spot Beam an Ocean Region is divided into subregions,
each “spotlighted” by a beam from the region satellite.
Terrestrial Network a fi xed telecommunications network,
such as a telephone network or a data network,
which connects to the Inmarsat system at an SAS.
UDI Unrestricted Digital Information.
UMTS Universal Mobile Telecommunications System.
USB Universal Serial Bus.
USIM SIM card designed for 3G mobile telephony.
Training Manual
UTC Coordinated Universal Time, referenced to Greenwich

Mean Time (GMT).
VBR Variable Bit Rate.
VoIP Voice over Internet Protocol, broadband internet
telephone communications.
VPN Virtual Private Network.
9
R&R of EXP. 727Antenna
Training Manual

NOTE!
This chapter will describe removal and replacement (R&R) of Parts not available on the
some of the parts of the EXPLORER 727 - 403722A-00700, which eShop is not considered as a
by Thrane & Thrane is considering as Spare Parts, that can be Spare Part, and we can not
deliver these items.
found on our eShop (http://shop.thrane.com/).
10.1 R&R of EXPLORER 727

complete.
Handset complete.
Cradle complete.
Figure 10-1 and 10-2: TT-3053B Antenna, front and rear
10.1.1 S-403053B-THR EXPLORER 727 Antenna Complete

1. S-41-130921-A Radome Kit Beige
S-41-130922-A Radome Kit White
2. S-88-130920-A ATB /LNA Module
4. S-41-130914-A Elevation Motor
10
6. S-41-130893-A Azimuth Stepmotor
7. S-67-131214 Rotary Joint Kit
8. S-41-130889-A Belt Kit
236 Chapter 10
Removal & replacement EXPLORER 727 Antenna
10.1.1.1 Removal & replacement of Radome Top
Figure 10-3: 403053B Antenna, Radome Top

Removal:
12 M3 Allen screws from the top side of the antenna, around
the rim.
2. Lift straight up the Radome Top, to get it free of the antenna
panel.
Replace:
CAUTION! 1. Clean and check for damage the Radome Gasket around the
Take care that the Radome rim of the Radome bottom.
Gasket is not being or getting
damaged. If the gasket is dried out, a thin layer of silicone grease should
be applied.
3. Insert the twelve (12) M3 Allen screws and nuts by cross-tighten
the screws to 0.8 Nm. Screws, nuts and washers are included
in the Assembly kit S-67-131215.
10.1.1.2 Removal & replacement of ATB/LNA Module

(Antenna Tracking Board /Low Noise
Amplifier Module)
10
Figure 10-4: ATB/LNA Modules

Training Manual
Removal: NOTE!
2. Remove the HPA Module as explained in section Removal &
replace of HPA Module.
Figure 10-9: LNA close-up

1. From HPA top. Black cable.
2. Brown cable from HPA
bottom.
3. From ATB brown cable
Other two short black cables to
antenna panel as shown.
Figure 10-5 and 10-6
NOTE!
3. Disconnect the plugs/cables as indicated above. Remember to release
(the two (2) squared plugs)
NOTE!
plugs.
NOTE!

4. Release the ATB and LNA by removing the screws & nuts as
indicated above.
5. Carefully lift/release the cable holders, securing the cables
going to ATB and HPA.
6. Carefully remove the ATM/LNA without stressing the cables.
Replace:
1. Position the new ATB/LNA modules and carefully align the
cables going to ATB and HPA module.
2. Fasten the screws & nuts for ATB/LNA.
10
3. Reconnect the plugs & cables (follow the note above), make
sure that they are properly fitted.
238 Chapter 10
10.1.1.3 Removal & replacement of GPS Module

(Global Position System Module)
NOTE!
Remember to release
NOTE!
plug.
Figure 10-10: Global Position System Module

Removal:
2. Disconnect the plug from the GPS Module.
3. Unscrew the four (4) Torx-8 screws holding the GPS
Module in position.
4. Remove the GPS Module.
Replace:
1. Insert the new GPS Module and position on the nuts.
2. Insert the four (4) new Torx-8 screws and tighten with no more
than 1.0 Nm.
3. Connect the plug from the HPA.
10.1.1.4 Removal & replacement of Elevation Motor

NOTE!
10 NOTE!
should be identical to the
antenna.
Figure 10-11 and 10-12: Elevation Motor

Removal:
2. Disconnect the plug from the Elevation Motor and the jack,
assembled in front of the Elevation Motor on the bracket.
Training Manual
3. Unscrew the four (4) Torx-8 screws holding the Elevation

Motor in position, put aside as they are going to be reused in
the replacement of the Elevation Motor.
4. Remove the tension of the drive belt by pushing the Elevation
Motor forward and remove the drive belt from the pulley (gear
wheel).
5. Retract the motor with pulley through the hole in the pedestal.
Replace:
1. Measure the distance (d) from motor housing to the pulley of
the removed Elevation Motor. Figure 10-13: Elevation Motor
2. Measure the distance d found (in Replace: step 1) and mark it NOTE!
up on the shaft of the new Elevation Motor. Orientate the GPS Module so
that the wires from the HPA
3. Install the new pulley on the new Elevation Motor, and tighten can reach the connector of the
the two (2) 1.5 mm pilot screws no more than 1.0 Nm. GPS Module.
4. Install the Elevation Motor through the hole in the pedestal.
NOTE!
5. Thread the drive belt over the pulley. A click should be heard when
6. Insert, but do not tighten, the four (4) Torx-8 screws (removed
in above Removal: step 3) fixing the Elevation Motor to the
pedestal.
7. Check the position of the pulley on the shaft of the Elevation
Motor, so that the drive belt has a straight line between the
drive pulleys.
9. Connect the plug from the Elevation Motor to the jack.
10. Manually check the movement of the antenna panel to verify
no jam.
10
240 Chapter 10
10.1.1.5 Removal & replacement of HPA Module (High

Power Amplifier)
NOTE!
Remember to release
pulling it off.
NOTE!
plug.
Figure 10-14 and 10-15: HPA

Removal:
NOTE! 1. Remove the Radome Top as described in the previous section
Remember to release the Remove & replacement of Radome Top.
cables from retainer before
removing module. 2. At the rear side of the HPA, unscrew the four (4) big finger nuts,
put aside as they are going to be reused in the replacement
NOTE! of the HPA.
plug. 3. Carefully remove the HPA from the pedestal (the fan of the HPA
is to be slide out the pedestal). Carefully release the cables.
Replace:
1. Slide carefully the HPA into position with the fan of the HPA
into the pedestal. Fit the studs on the rear side of the HPA into
the pedestal.
NOTE! 2. Fasten the four (4) finger nuts (removed in above Removal:
Orientate the Elevation step 2) with no more than 1.2 Nm.
Motor so that the wires from
the motor can reach the 3. Reconnect the plugs and cables making sure they are properly
connection point. fitted.
NOTE!
rest of the drive belts in the 10.1.1.6 Removal & replacement of Azimuth Stepmotor
antenna.
NOTE!
10
Figure 10-16
Training Manual
Removal: NOTE!
1. Remove the Radome Top as described in the previous section Remember to release
Removal & replacement of Radome Top. before pulling them off.
2. Disconnect the plug from the Azimuth Stepmotor and release NOTE!
the cable located to the right of the Stepmotor as shown above. Do not pull the wires - pull the
plugs.
3. Release (not remove) the four (4) Torx10 screws (one in each
corner of the motor) holding the Azimuth Stepmotor in position,
and remove the belt which has now been released.
4. Remove the four (4) Torx10 screws for the mounting plate
and carefully extract/remove the motor including the mounting
plate as shown to the right.
5. Remove the (4) Torx10 screws and the mounting plate from
the motor. Put aside all the Torx10 screws and the mounting
plate as they are going to be reused in the replacement of the
Azimuth Stepmotor.
Replace:
1. Mount the plate on the motor as shown to the right with (4)
Torx10 screws. Do not fasten the screws.
2. Position the motor w. plate and fasten the (4) Torx10 screws
Figure 10-19: Azimuth motor
holding the mounting plate to the pedestal. Reposition and close-up incl. mounting plate
thread the drive belt over the pulley.
3. Check the position of the pulley on the shaft of the Azimuth
Stepmotor, so that the drive belt has a straight line between
the drive pulleys.
NOTE!
It must not be possible to twist
the drive belt more than 90°.
Figure 10-17 and 10-18: Azimuth Stepmotor - Tension of Belt

4. Tighten the four (4) Torx10 screws holding the Azimuth motor NOTE!
while straitening the tension belt with a screwdriver as shown Remember to release
above. connector latch on the before
10
pulling it off.
5. Connect the plug from the Azimuth Stepmotor to the jack. NOTE!
6. Manually check the movement of the antenna pedestal to verify Do not pull the wires - pull the
plug.
no jam.
Removal & replacement of Radome Top. A click should be heard when
242 Chapter 10
10.1.1.7 Removal & replacement of Rotary Joint kit

Removal:
2. Release the upper and lower Azimuth belts as shown.
Figure 10-24
NOTE!
Start by releasing both the
upper and lower belt by
releasing these screws!
Figure 10-20 and 10-21: Removing Rotary Joint Top and accessing Rotary Joint bottom
3. Remove plug/release cable and unscrew the four (4) M3 Allen
screws holding the Rotary Joint Top as shown above.
4. Carefully lift off - and remove the Rotary Joint Top.
5. Remove the six (6) M4 Allen screws from bottom of
the antenna as shown to the left.
6. Remove the four (4) M3 Philips screws for accessing
the Rotary Joint bottom as shown above (fig. 10-21).
Please note the two inner screws are for countersunk
Figure 10-25 holes.
NOTE! 7. Carefully extract the round bottom plate together with the belt-
The inner parts/pedestal will be wheel.
released when removing the
bottom screws!!
Remove screws while antenna
is oriented on a flat surface i.e.
accessing the screws over the
edge of a table!!
NOTE!
Places where Silicone glue Figure 10-22 and 10-23: Release of Rotary Joint Bottom part
10
carefully must be removed
and renewed when replacing 8. Unscrew the four (4) Torx-8 screws for releasing the Rotary
Rotary Joint kit! Joint Bottom part as shown above.
9. Unscrew the TNC connector and remove the Silicone
glue for removing the Rotary Joint kit Bottom part incl.
cable w. TNC.
Figure 10-26
Training Manual
Replace: NOTE!
1. Leading the cable through the square hole of the bottom plate Remember the Centre Pin and
Spring!!
- fasten the TNC connector from the Rotary Joint and apply
silicone glue in the areas shown above.
2. Tighten the four (4) Torx-8 screws for the Rotary Joint Bottom
part as shown in fig. 10-22. Remember the small centre pin
and spring!!
3. Carefully assemble the wheel belt with the round Rotary Joint
lower plate using the two outer screws.
4. With the belt in position, carefully align the assembled part
and fasten it with the two inner screws which are for the
countersunk holes (fig. 10-21).
Figure 10-29
NOTE!
Remember to release
pulling it off.
NOTE!
plug.
NOTE!
It must not be possible to twist
the drive belt more than 90°.
Figure 10-27 and 10-28: Adjusting tension of lower Azimuth Belt
5. Adjust the correct tension of the lower Azimuth Drive Belt using NOTE!
a tool as shown above and tightening the screw pointed out. The tension of the drive belt
6. Check the tension of the upper Azimuth Drive Belt like shown rest of the drive belts in the
in fig. 10-17 and 10-18. antenna.
7. With caution, position the complete assembled inner
part and tighten the six (6) M4 Allen screws from
bottom of the antenna. Do this while antenna is
oriented on a flat surface i.e. accessing the screws
over the edge of a table!
Removal & replacement of Radom Top.
10
244 Chapter 10
10.1.1.8 Removal & replacement of Belt Kit
NOTE! Removal:
A click should be heard when 1. Remove the Radome Top as described in the previous section
2. For removal & replacement of Belts for the Azimuth motor,
please follow the guidelines in:
10.1.1.6 Removal & replacement of Azimuth Stepmotor
Remove: step 1 and 3
Replace: step 3,4,6 and 7
3. For removal & replacement of Belts for Elevation Motor - follow
the guidelines in:
10.1.1.4 Removal & replacement of Elevation Motor
Remove: step 3 and 4 (only loosen the screws).
Figure 10-30 and 10-31: Release of Elevation Belt for Antenna Panel
4. Unscrew the nut (size 5.5) with wheel - and the two Torx10
screws with pins holding the Belt fastened to the antenna panel
as shown above. Put aside as these parts are going to be
reused in the replacement of the Belt.
Replace:
1. Loosen (not remove) the two screws indicated above
with circles.
2. Check that the four (4) screws holding the elevation motor (fig.
10-12) are loose (not removed) - and put the proper belt in
position around the pulley for the motor and Belt-wheel.
3. Put the second Belt in position and fasten the two Torx10
screws with pins making sure the Belt stretched firmly around
10
the area shown above (fig. 10-31). Fasten the nut (size 5.5)
with wheel.
NOTE! 4. Apply the correct tension for the Antenna Panel Belt, by using
It must be possible to twist the a tool next to the left screw indicated with a circle - and tighten
drive belt no more than 90°. the two screws with a circle.
5. In section: 10.1.1.4 Remov & replacement of Elevation Motor
- follow step 7, 8 and 10.
Training Manual
10
R&R of EXP. 325Antenna
248 Chapter 11
Removal & replacement EXPLORER 325 Antenna TT-3058A
NOTE!
Parts not available on the
eShop is not considered as a This chapter will describe removal and replacement (R&R) of
Spare Part, and we can not
deliver these items.
some of the parts of the EXPLORER 325 Antenna - 403058A,
which by Thrane & Thrane is considering as Spare Parts — found
on our eShop (http://shop.thrane.com/).
11.1 R&R of EXPLORER 325

complete.
Handset complete.
Cradle complete.
Figure 11-1 and 11-2: TT-3058A Antenna, front and rear.

1. S-41-131912 Radome Compl. Expl325

2. S-88-131908 Antenna Tracking Board—ATB, 325
4. S-36-131910 Elevation Motor Expl. 325
6. S-36-131909 Azimuth Stepmotor Expl 325
7. S-41-131907 Rotary Joint Kit Expl 325
8. S-41-131911 Motor Belt set/Kit
9. S-37-131913 Cable Set Expl325
11
Training Manual
11.2 Remove & replacement of Radome Top
Figure 11-3: 403053B Antenna, Radome top

Remove:
1. Remove the antenna Radome Top starting with removing
the 12 M3 Torx screws from the buttom side of the antenna,
around the rim.
2. Lift straight up the Radome Top, to get it free of the antenna
panel.
CAUTION!
Replace: Take care that the Radome
Gasket is not getting damaged!
1. Clean and check for damage on the Radome Gasket around
the rim of the Radome bottom.
be applied.
2. Lower the Radome Top over the pedestal and antenna panel
3. Insert the twelve (12) M3 Torx screws and nuts by cross-tighten
the screws to 1.0Nm. Screws are included in the Assembly kit
S-67-131215.
CAUTION!
Make sure that arrows on
Radome & bottom are aligned!
11
250 Chapter 11
11.3 Remove & replacement of Elevation motor
Figure 11-4: Elevation Motor.

Removal:
2. Disconnect the plug and cut the strip as indicated below.
3. Remove the Elevation Motor by removing the screws as
indicated below.
NOTE!
Use a screwdriver or similar to
push the Elevation Motor and
strengthening the Belt.
NOTE!
The adequate tension is when
the belt can be turned appr. 90
degr. “without too much force”-
and the antenna panel can be
turned “rather smooth”!!
11 Figure 11-5: Replace elevation Motor.

Training Manual
Replace:
1. Position the new Motor and tighten the four (4) 5mm Torx
screws while checking the tension of Elevation Belt.
2. Connect the plug and secure wires with a cable tie. NOTE!
3. Reinstall the Radome Top as described in previous section the plug is fully inserted.
11.4 Remove & replacement of GPS Module

(Global Position System Module)
Figure 11-6: Global Position System Module.

Removal:
2. Disconnect the plug from the GPS Module.
3. Unscrew the two 8mm Torx screws holding the GPS
Module/plate in position. NOTE!
Remember to release
4. Remove the four ‘lock-nuts’ holding the GPS Module. connector latch on the plug
Replace: before pulling it off.
1. Assemble the new GPS Module with the mounting plate using NOTE!
4 new ‘lock-nuts’ Do not pull the wires - pull the
plug.
2. Tighten the two 8mm Torx screws with no more than 1.0 Nm.
3. Connect the plug for the GPS module.
11
252 Chapter 11
11.5 Remove & replacement of Azimuth Motor.

Removal:
2. Disconnect the plug from the Azimuth Motor and cut the three
(3) strips holding the wires in position.
3. Unscrew the two (2) 8mm Torx screws holding the mounting
plate for the Azimuth Motor.
4. Unscrew the four (4) Torx screws securing the Motor to the
Mounting Plate.
NOTE!
should be identical to the Figure 11-8: Azimuth Motor.
antenna.
11
Training Manual
NOTE!
Orientate the Motor so that
the wires are in the direction
Figure 11-9: Azimuth Motor removal. towards the middle of Antenna.
Replace:
1. Fasten the four (4) screws securing the motor to the Azimuth
Mounting Plate.
2. When inserting the Motor with Mounting Plate, use a tool to
wrap the Drive Belt around the Pulley. Figure 11-10.
3. Insert the two (2) screws and tighten them when the Drive Belt
has the correct tension. Adjust the tension of Drive Belt by
using a tool as shown below.
4. Connect the plug in the socket marked AZ and secure the
wire with cable ties as shown in figure 11-9.
5. Reinstall the Radome Top as described in previous s e c t i o n
Figure 11-10: Azimuth Motor Drive Belt.
11
254 Chapter 11
11.6 Remove & replacement of ATB (Antenna

Tracking Board) - OR Rotary Joint
Removal:
Remove & replacement of Radome Top
2. Remove the Elevation and Azimuth motor as described in
section 11.1.1.2 and 11.1.1.5 and release the TNC connection
from the Radome-bottom. See above.
3. Turn the antenna around by holding/supporting the antenna
part carefully in one hand while removing the 6 M4x10 Eco-fix
screws from the bottom and lay the antenna on the table as
shown above.
4. Carefully remove the Azimuth Drive Belt.
5. Cut the cable ties and release the two black antenna panel
cables from their plugs. Remove the two ‘lock nuts’ holding the
antenna panel and extract the long screw from the left side of
antenna panel and remove the antenna panel.
6. Remove the M3-8 size screws indicated above. 5 screws
holding the bracket to the right (for Azimuth motor) —and 3
screws to the left. All mounted on the Rotary Joint assembly.
See figure 11-13.
7. On the ATB Board—unplug the cables coming from
the HPA Assembly and carefully release the HPA
Assembly from the Rotary Joint/ATB Board.
8. Remove the 25 M2,5x8 size Screws holding the ATB Board to
NOTE! the Rotary Joint.
Remember to release
pulling it off.
NOTE!
plug.
NOTE!
When removing the Azimuth
Drive Belt—make use of the
‘slit’ of the Rotary Joint lower
part!!
Figure 11-11:
11
Training Manual
ATB—Antenna Tracking Board

mounted on Rotary Joint with
25 Screws size M2,5x8 rotary
Replace:
1. Carefully align the ATB Board into position on the Rotary joint, Note !
and tighten the 25 M2,5x8 size screws. The Rotary Joint spare part is
a complete unit!!
2. Position the HPA Assembly on the Rotary Joint and fasten the
5 screws incl bracket for Azimuth Motor as shown in figure
11-13
3. Mount the Antenna panel as shown in figure 11-12 + 11-14. The
two spacers must have the countersink towards the screws head.
Use only new ‘lock-nuts’.
4. Reconnect the plugs and cables making sure they are
properly fitted. See also 11.1.1.8 Guide in arranging
cables
5. Turn antenna assembly around and carefully mount the
radome bottom with the parts shown in fig. 11-11.
6. Follow the guidelines Replace: in sections 11.1.1.1, 11.1.1.2,
11.1.1.4 and 11.1.1.5
11
256 Chapter 11
Make sure the small black

plastic disc is in position when
fastening the screw/nut holding
the right side of the antenna
panel.
Replace:
1. Carefully align the ATB Board into position on the Rotary joint,
and tighten the 25 M2,5x8 size screws.
2. Position the HPA Assembly on the Rotary Joint and fasten the
5 screws incl bracket for Azimuth Motor as shown in figure
11-13
3. Mount the Antenna panel as shown in figure 11-12 + 11-14. The
NOTE!
— the counter-sink must be two spacers must have the countersink towards the screws head.
orientated away from the plate/ Use only new ‘lock-nuts’.
nut.
4. Reconnect the plugs and cables making sure they are
properly fitted. See also 11.1.1.8 Guide in arranging
cables
5. Turn antenna assembly around and carefully mount the
radome bottom with the parts shown in fig. 11-11.
6. Follow the guidelines Replace: in sections 11.1, 11.2, 11.4 and
11.5
NOTE: Remove & replacement of Radome Top.
Socket marked
EL: For Elevation motor
AZ. For Azimuth motor 11.7 Remove & replacement of HPA Board.
Removal:
1. Remove the Rotary Joint with ATB Board as
described in section 11.1.1.6 Remove & replace
ment of ATB (Antenna Tracking Board) - OR Rotary
Joint.
2. Remove the Cover and Brackets as shown below by
releasing 9 screws.
3. Remove the HPA Board from the heat sink by releasing the 12
Torx M3x6 size screws .
11
Training Manual
NOTE:
The 12 screws for the HPA
Board.
Replace:
1. When carefully replacing the HPA board on the heat sink,
make sure there is adequate amount of cooling paste. Apply
if necessary and tighten the 12 Torx M3x6 size screws 1Nm
2. Assemble as described in section “11.6 Remove & replacement
of ATB (Antenna Tracking Board) - OR Rotary Joint” under
Replace. See also 11.8 Guide in arranging cables.
11.8 Guide in arranging cables

1. Arrange the coax cables from the antenna panel seen from
behind of antenna panel as shown in fig 11-17. L (left) goes to
ANT2. R (right) goes to ANT1. Note the brown long thin coax
cable.
Brown long thin cable from
2. Connect the coax cable ATB to HPA and the 10 wire ATB board.
comm. cable as shown in fig 11-18 and 11-19
3. Fit cable ties as shown in figure 11-20. Make sure
that all cables/wires are ‘softly’ bent and not touching
metal edges.
L R
Note !
Secure cables with a cable tie
as shown.
Figure 11-18 cables from antenna panel.

11
258 Chapter 11
Note!
The 4 wire plug coming from
the comm. cable fig. 11-19
must be arranged in this way!
Figure 11-18 Coax and 11-19 Comm. cable

1. Arrange the coax cables from the antenna panel seen from
behind of antenna panel as shown in fig 11-17. L (left) goes to
ANT2. R (right) goes to ANT1. Note the brown long thin coax
cable.
2. Connect the coax cable ATB to HPA and the 10 wire
comm. cable as shown in fig 11-18 and 11-19
3. Fit cable ties as shown in figure 11-20. Make sure
that all cables/wires are ‘softly’ bent and not touching
metal edges.
Note!
Correct use of cable tie for
comm. cable and cables for
motors.
Figure 11-20: cable ties
11
TT-100-MSO-030207
www.cobham.com/satcom

Fleetbb Training Manual

Uploaded by

Copyright:

Available Formats

Fleetbb Training Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fleetbb Training Manual

Uploaded by

Copyright:

Available Formats

FleetBroadband Installation

Commissioning and On Board repair

SAILOR 150 FleetBroadband

SAILOR 250 FleetBroadband

SAILOR 500 FleetBroadband

EXPLORER 727 BGAN

5.3 Dash Board ...................................................................................... 127

6 Removal & Replacement

6.5 R&R of SAILOR® 150 FleetBroadband............................................. 201

Figure 1-1: BGAN-X network overview

Figure 1-2: BGAN-X Radio Access Network

1.2 Beam types

Figure 1-3: EMEA Figure 1-4: APAC Figure 1-5: AMERICAS

1.2.2 Regional Beams

Figure 1-6: EMEA Figure 1-7: APAC Figure 1-8: AMERICAS

1.2.3 Narrow Beams

Figure 1-9: EMEA Figure 1-10: APAC Figure 1-11: AMERICAS

1.2.4 Beam Hierarchy

BGAN-X Satellite Beam hierarchy and functions:

Figure 1-12: Beam hierarchy

1.2.5 Elevation bands

Figure 1-13: EMEA Figure 1-14: APAC Figure 1-15: AMERICAS

Max. bit rate, Max. bit rate,

Figure 1-16: Maximum bit rate

1.3 BGAN-X units

Under ideal conditions the most powerful FleetBroadband can

1.3.2 Subscription and Quality of Service (QoS)

Alternatively there could be choose a 64 kb/s guaranteed bit

1.4 RAN (Radio Access Network)

Figure 1-17: RAN

1.5 Core Network

Figure 1-18: Core Network

1.5.1 HLR (Home Location Registry)

SMSC (Short Messaging Service Centre):

1.6 Distribution architecture

Figure 1-23: Radio Recourse Management

1.6.1 RNC Recourse Management Entities

Figure 1-24: RNC Recourse Management

1 The RNC performs admission control when deciding whether to

Return Direction Queue Reporting:

1 For variable bit rate IP services the capacity available in

Hence connections that exceed their target rate target in one

Forward Bearer Return Bearer

Figure 1-25: Entries of the Forward and Return Bearers

1.7.1 Forward direction Bearer types

1 Beam Forward carrier

Global F80T0.25Q1B 1 25.5 QPSK 8.4 8.4 4.5

Regional F80T1Q4B 4 29.2 QPSK 33.6 40 21.6 to

Narrow F80T4.5X8B 8 40.5 16-QAM 151.2 41.2 113.6

Figure 1-26: Forward direction Bearer types

Forward carrier type C/No

1.7.2 Forward direction coding and multiplexing

Figure 1-28: Payload

80ms forward frame illustrating how the frame is divided into

Figure 1-29: Forward bearer

1.7.3 Return direction Bearer types

Figure 1-30: Return direction Burst types

Forward carrier type C/No

In the return direction the BGAN air interface operates in TDMA

1.7.4 Return direction coding, multiplexing and