User Manual ABT-1103 Ed1 G ENG

________________________________________
USER MANUAL
AIS BASE STATION TRANSPONDER
model ABT-1103
________________________________________
USER MANUAL
AIS BASE STATION TRANSPONDER

model ABT-1103
Ed. 1 rev. G
REVISIONS AND APPROVALS
S.r.l.
Via di Valle Caia, km 4.700. Zona Ind.le S. Palomba
00040 Pomezia (RM)
Ph. 06-9194405
Fax 06-9194306
Web: www.elmansrl.it
E-mail: elman@elmansrl.it
List of revisions
Ed. Rev. Issue date Description of Change
I G 30/03/2016 Added description of Receiver Manager function.
I F 16/02/2016 Improved descriptions of DGNSS related functions. Updated Restriction of use.
Description of CBM legacy sentence. Minor corrections.
I E 29/10/2014 Added DoC and restrictions of use
I D 01/03/2013 Minor corrections, updated BCS images
I C 14/03/2011 Corrected wrong PBS and updated IEC 61162-1 edition in chapter 2
I B 04/01/2011 Updated to reflect changes introduced with firmware version 1.1
I A 16/11/2010 First issue
Approvals
Drawn up (U.T. Operator) Control (Project Manager) Approval (U.T. Manager)
ABT-1103 AIS Base Station User Manual Pag. 2 of 105

INTRODUCTION
This USER MANUAL, supplied with the ABT-1103 AIS Base Station, was written to
provide operators with all the useful and essential information and indications needed, in
particular to correctly configure and operate the ABT-1103.
This manual refers to hardware revision C6 (configuration index 6) and firmware

revision 1.1.x of the ABT-1103.
Read this manual before use.
A Technical Manual of the ABT-1103 is also available including all the needed
instructions for a correct installation and maintenance of the unit.
Warning:
Even though our company is extremely careful when producing its publications, this
manual may contain errors or omissions, and may be changed without warning. Elman S.r.l.
cannot be held responsible for any damages resulting from the use of this manual.
MANUAL LAYOUT
The manual has been split into 6 chapters to make it easier to consult. The chapters
respectively contain the following information:
 An introduction to AIS.
 An overview of the ABT-1103.
 A description of possible modes of operation.
 Detailed configuration instructions.
 Detailed instruction for the normal operation of the device.
 A list of all the supported IEC sentences with content description.
Each page (with the exception of the title page) includes a footer section featuring:
 the title of the manual

 the current page
 the overall number of pages in the document

DECLARATION OF CONFORMITY

INTENDED USE
The ABT-1103 and LBT-1103 devices are intended to operate as AIS (Automatic
Identification System) Base Stations on fixed installations (e.g. land based). The ABT-1103
and LBT-1103 are designed to participate in the AIS according to the Commission Decision
2005/53/CE, operating in the VHF marine band (156.025 ÷ 162.025 MHz).
NOTIFIED COUNTRIES
The ABT-1103 and LBT-1103 devices may be operated in Austria, Belgium, Bulgaria,
Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary,
Ireland, Iceland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Portugal,
Romania, Sweden, Switzerland/Liechtenstein, Slovenia, Slovak Republic, Spain, United
Kingdom and Morocco.
MARKING
The ABT-1103 and LBT-1103 devices are classified as Class 2 radio equipment
according to the 1999/5/EC Directive. The warning symbol indicates that these devices
operate on non harmonised frequency bands and that they are subjected to licensing
conditions and restrictions in the country of use.
RESTRICTIONS OF USE
A licence is required to operate an AIS Base Station. The licence, to be provided by
the National Competent Authority (NCA) in the country of use, is associated to a radio
identity (MMSI, Maritime Mobile Service Identity). Operating an AIS Base Station
without written permission from the NCA is persecuted in several countries.
Other restrictions on the usage may apply depending on the country of usage. Be sure
that you have all the necessary prerequisites and permissions to comply with national
licensing requirements.
LIMITED AIS BASE STATION

The fully featured AIS Base Station ABT-1103 should only be used by NCA operators
or by authorized and trained personnel to prevent any harmful interference to the AIS.
The limited AIS Base Station LBT-1103 may be operated by organizations other
than the NCA, but only if the license has been obtained and the necessary authorizations
have been received from competent authorities.

LIST OF CONTENTS
REVISIONS AND APPROVALS 2

INTRODUCTION 3
MANUAL LAYOUT 3
DECLARATION OF CONFORMITY 4
INTENDED USE 5
NOTIFIED COUNTRIES 5
MARKING 5
RESTRICTIONS OF USE 5
LIMITED AIS BASE STATION 5
LIST OF CONTENTS 6
GLOSSARY OF TERMS AND ABBREVIATIONS 9
CHAPTER 1 AN INTRODUCTION TO AIS 11
1.1 THE AIS BASICS 11

1.2 THE AIS BASE STATION 12
1.3 THE ROLE OF IALA 12
1.4 THE ROLE OF IMO 12
1.5 THE ROLE OF ITU 13
1.6 THE ROLE OF IEC 13
CHAPTER 2 ABT-1103 OVERVIEW 15
2.1 GENERAL DESCRIPTION 15

2.2 MAIN FEATURES 16
2.2.1 VHF RECEIVERS 17
2.2.2 VHF TRANSMITTER 17
2.2.3 PRESENTATION INTERFACE 17
2.2.4 TYPE OF OPERATION MODES 18
2.2.5 DGPS UNIT 18
2.3 PRODUCT BREAKDOWN STRUCTURE (PBS) 19
2.4 APPLICABLE REGULATIONS AND STANDARDS 20
CHAPTER 3 MODES OF OPERATION 22
3.1 INTRODUCTION 22
3.2 RECEIVE ONLY MODE 22
3.3 DEPENDENT MODE 22
3.4 INDEPENDENT MODE 23
CHAPTER 4 CONFIGURATION 25
4.1 INTRODUCTION 25
4.2 INSTALLATION PARAMETERS 26
4.2.1 BAUD RATES OF PI PORTS 26

4.2.2 BAUD RATES OF SENSOR PORTS 27
4.2.3 DGNSS OUT PORT 27
4.2.4 RTCM / DGNSS IN PORT 27
4.2.5 RMC SENTENCE OVER PI PORTS 28
4.2.6 PPS OUT ENABLE 28
4.2.7 PPS IN INVERSION 28
4.2.8 VDM OUT FILTER 28
4.3 VERSION INFORMATION 29
4.4 BASE STATION IDENTIFIERS 30
4.4.1 TALKER IDENTIFIER 30
4.4.2 UNIQUE IDENTIFIER 30
4.4.3 MMSI 31
4.4.4 STATION NAME 31
4.5 BASIC CONFIGURATION 32
4.5.1 POSITION SOURCE 32
4.5.2 UTC SOURCE 33
4.5.3 VHF CHANNELS 33
4.5.4 TRANSMITTED POWER 33
4.5.5 RATDMA CONTROL 33
4.5.6 VDL MESSAGE RETRIES 33
4.5.7 MESSAGE REPEAT INDICATOR 34
4.5.8 ADS INTERVAL 34
4.5.9 COMMENT BLOCKS 34
4.6 FATDMA CONFIGURATION 36
4.7 CHANNEL MANAGEMENT 38
4.8 PROCESSING AND OUTPUT SELECTION 39
4.9 DGNSS CORRECTIONS 41
4.9.1 TRANSMISSION 41
4.9.2 RECEPTION 42
4.10 RECEIVER MANAGER 43
4.11 FIRMWARE UPGRADES 44
CHAPTER 5 OPERATING THE ABT-1103 45
5.1 INTRODUCTION 45
5.2 RESTART AND RESET 45
5.3 AIS DATA RECEIVED FROM THE VDL 46
5.4 AIS DATA TRANSMITTED TO THE VDL 47
5.4.1 PERIODIC TRANSMISSIONS 47
5.4.1.1 Independent mode 48
5.4.1.2 Dependent mode 48
5.4.2 NON PERIODIC TRANSMISSIONS 49
5.4.2.1 Scheduled transmissions 49
5.4.2.2 Unscheduled transmissions 49
5.4.2.3 Binary and safety messages 50
5.4.2.4 Interrogations 51
5.4.2.5 Assignment message 51
5.4.2.6 Addressed channel management 52
5.4.2.7 Other automatic transmissions 52
5.4.2.8 Transmit slot prohibit 53
5.5 GNSS FUNCTIONALITIES 54
5.5.1 INTERNAL GPS RECEIVER 54
5.5.2 DGNSS CORRECTIONS 54
5.6 STATUS MONITORING 56

5.6.1 AIS DEVICE STATUS 56
5.6.2 ALARMS 56
5.6.3 STATUS MESSAGES 57
5.6.4 MEASUREMENTS 57
CHAPTER 6 SUPPORTED IEC 61162 SENTENCES 59
6.1 PRESENTATION INTERFACE PORTS 59

6.1.1 INTRODUCTION 59
6.1.2 VALID CHARACTERS FOR TEXT 62
6.1.3 STANDARD SENTENCES 63
6.1.3.1 Queries 63
6.1.3.2 ABK – Addressed binary acknowledgment 64
6.1.3.3 ABM – Addressed binary message 65
6.1.3.4 ACA – AIS channel assignment 66
6.1.3.5 ACK – Acknowledge alarm 67
6.1.3.6 ACM – Addressed channel management message 68
6.1.3.7 ADS – AIS device status 69
6.1.3.8 AGA – Group assignment message 70
6.1.3.9 AIR – AIS interrogation request 71
6.1.3.10 ALR – Alarm state 72
6.1.3.11 ASN – Assignment VDL Message 16 73
6.1.3.12 BBM – Broadcast binary message 74
6.1.3.13 BCE – Extended general Base Station configuration 75
6.1.3.14 BCF – General Base Station configuration 76
6.1.3.15 CAB – Control AIS Base Station 77
6.1.3.16 CBM – Broadcast rates for Base Station messages 78
6.1.3.17 DLM – Data link management slot allocations for Base Station 79
6.1.3.18 ECB – Broadcast rates for Base Station messages 81
6.1.3.19 FSR – Frame summary of AIS reception 83
6.1.3.20 RMC – Recommended minimum specific GNSS data 84
6.1.3.21 SID – Installation of a station‟s identification 85
6.1.3.22 SPO – Select AIS device‟s processing and output 86
6.1.3.23 SSD - Ship static data 87
6.1.3.24 TFR – Transmit feed-back report 88
6.1.3.25 TSA – Transmit slot assignment 90
6.1.3.26 TSP – Transmit slot prohibit 91
6.1.3.27 TSR – Transmit slot prohibit status report 92
6.1.3.28 TXT – Text transmission 93
6.1.3.29 VDM – VHF data link message 94
6.1.3.30 VDO – VHF data link own message 95
6.1.3.31 VER – Version 96
6.1.3.32 VSI – VDL signal information 97
6.1.3.33 ZDA – Time and date 98
6.1.4 PROPRIETARY SENTENCES 99
6.1.4.1 Queries 99
6.1.4.2 PELMAIS – AIS Installation Settings 99
6.1.4.3 PELMDGC – DGNSS service configuration 101
6.1.4.4 PELMMEA – Measurements 102
6.1.4.5 PELMRXM – Receiver manager settings 103
6.2 SENSOR PORTS 104
6.3 DGNSS OUT PORT 105

GLOSSARY OF TERMS AND ABBREVIATIONS
Name Description
A/B (A+B) AIS Channel 1 / AIS Channel 2
AC Alternative Current
ACK Acknowledgement
AIS Automatic Identification System
AIS_ChAs AIS Channel Assignment Sentence
ALR Alarm
AS Assigned
AU Autonomous
BcastChM Broadcast Channel Management
BIIT Built-In Integrated Test
BRG Vessel True Bearing
BS Base Station
Call Sign International name of a boat
CB Comment Blocks
COG Course Over Ground
DC Direct Current
Dest Destination
DGNSS Differential Global Navigation Satellite Service
DGPS Differential Global Positioning System
Dist Distance
DSC Digital Selective Calling
DTE Data Terminal Equipment
ECDIS Electronic Chart Display
EPFD Electronic Position Fixing Device
EPFS Electronic Position Fixing Sensor
ETA Estimated Arrival Time
ExtGPS External Global Positioning System
ExtHDT External Heading True
ExtSOG External Speed Over Ground
GNSS Global Navigation Satellite Service
GPS Global Positioning System
GYRO Gyrocompass
IALA International Association of Lighthouse Authorities
IMO International Maritime Association
IMO No International Maritime Association Number
IN Interrogation/Polled Mode
IntCOG Internal Course Over Ground
IntGPS Internal Global Positioning System
ITU International Telecommunication Union
LAT Latitude
LON Longitude
LR Long Range
LRI Long Range Interrogation
LSS Logical Shore Station
MMSI Maritime Mobile Service Identity

MOB Man Over Board
Mod Mode
NavStat Navigational Status
Nm Nautical Miles
OpManual Operator Manual
PBS Product Breakdown Structure
PCB Printed Circuit Board
PCU PSS Control Unit
PPS Pulse Per Second
PSS Physical Shore Station
PI Presentation Interface
PoB Persons on Board
Pos Position
PosAcc Position Accuracy
RAIM Receiver Autonomous Integrity Monitor
RF Radio Frequency
RI Repeat Indicator
RNG Rating
Rng Vessel Range
ROT Rate of Turn
RxA Receiving AIS Channel
RxB Broadcasting AIS Channel
RXVe Received vessels
SOG Speed Over Ground
SOLAS Safety Of Life At Sea
SOTDMA Self-Organizing Time Division Multiple Access
SRM Safety Related Message
Syn synchronisation
TDMA Time Division Multiple Access
TrZone Transitional Zone
TxA Transmitting on Channel A
TxB Transmitting on Channel B
UTC Universal Time Coordinated
VDL VHF Data Link
VHF Very High Frequency
W-AIS Warship AIS

CHAPTER 1
AN INTRODUCTION TO AIS
1.1 THE AIS BASICS

The aim of the Automatic Identification System (AIS) is to enhance the safety of
navigation by improving the prevention of collisions and the availability of information. AIS
can be easily integrated in the existing navigation control systems (e.g. radar), providing
information on the position and more detailed and reliable voyage data without requiring the
intervention of operators, and making it easily accessible to all the ships in the surrounding
area fitted with an AIS system.
Figure 1 – The AIS system

The AIS is a shipboard broadcast transponder system in which ships continually
transmit their ID, position, course, speed and other data to all other nearby ships and to the
coast authorities on common VHF radio channels.
The AIS foresees different types of stations which may be installed on vessels (Class A
and Class B stations), ashore (Base stations), on aircrafts (SAR - Search And Rescue –
stations) and on Aids to Navigation (AtoN stations). All the stations transmits on the same
maritime VHF channels which have been worldwide reserved for the AIS service, although
local authorities may locally adopt different channels through appropriate configuration of
transmissions from their Base Stations.

1.2 THE AIS BASE STATION
The AIS Base Station is the basic element of a land based AIS system. The AIS Base
Station can receive all the data transmitted by AIS equipped vessels and provide them through
a convenient interface to the shore system enabling processing and correlation with data
coming from other sensors. The Base Station also features a standard interface for the
management of Base Stations, including its transmissions. Transmissions from Base Stations
may be used to implement a number of services dedicated to the management of the AIS
service itself or to the interaction with the remote targets (i.e. ships).
1.3 THE ROLE OF IALA

The International Association of Marine Aids to Navigation and Lighthouse Authorities
(IALA) is a non profit making international technical association. Established in 1957, it
gathers together marine aids to navigation authorities, manufacturers and consultants from all
parts of the world and offers them the opportunity to compare their experiences and
achievements.
IALA has been the primary organisation sponsoring and co-ordinating the development
of the Automatic Identification System (AIS). In 1996, the Vessel Traffic Services (VTS) and
Radionavigation Committees (RNAV) of IALA prepared a draft recommendation that, with
further refinement within IMO NAV, became the basis for the IMO Performance Standard on
AIS. In October 1997, at the request of several emerging AIS equipment manufacturers,
IALA hosted a working group of manufacturers and maritime administrations to agree on a
standard technology for AIS stations. The group, which was formally designated the IALA
AIS Working Group, completed a draft recommendation, which was submitted by Sweden,
on behalf of Finland, Germany, Canada, South Africa, and the United States to the
International Telecommunications Union – Sector for Radiocommunications (ITU-R).
IALA continued the development of system standards and applications as well as the
“IALA Guidelines on the Automatic Identification System (AIS)”, a significant project in
itself.
1.4 THE ROLE OF IMO

One of the more widely known IMO (International Maritime Organisation) conventions
is the International Convention for the Safety of Life at Sea (SOLAS) 1974, better known as
SOLAS 74.
The necessity of a system which could enable the automatic identification of vessels has
been raised since the early 1990‟s. The limitations of technology available then (like for
instance DSC) prevented the implementation of an Identification System which was
automatic in operation, suitable for ship to shore and ship-to-ship purposes, and coped with
the density and movement of shipping in congested areas.
IMO eventually decided to adopt an AIS based on a Scandinavian proposal which
fulfilled the above requirements. The system was called a Universal Ship-borne Automatic
Identification System but now is simply called AIS.
The IMO Recommendation on Performance Standards for a Ship-borne AIS was
subsequently approved by the IMO Maritime Safety Committee (MSC) at its sixty-ninth

session (May 1998) under resolution MSC.74 (69) (Annex 3). The Performance Standard
specifies the requirements for AIS, including the functionality and capability of the system. In
particular, the following functional requirements should be satisfied:
1. in a ship-to-ship mode, for collision avoidance;
2. as a means for littoral States to obtain information about a ship and its cargo; and
3. as a VTS tool, i.e. ship-to-shore (traffic management).
According to the revised SOLAS carriage requirements, all ships of 300 gross tonnage
and upwards engaged on international voyages and cargo ships of 500 gross tonnage not
engaged on international voyages and passenger ships irrespective of size had to be fitted with
AIS, at the latest by 31 December 2004.
After the AIS Performance Standards promulgation, IMO requested the International
Telecommunications Union (ITU) to prepare a Recommendation on the Technical
Characteristics for the AIS.
1.5 THE ROLE OF ITU

The ITU (International Telecommunications Union) is a specialised agency of the
United Nations within which the public and private sectors co-ordinate global
telecommunication issues and services. At the ITU World Radiocommunication Conference
(WRC) in Geneva during October/November 1997, IMO requested that two maritime VHF
channels be assigned for AIS. The channels allocated are: AIS 1 (161.975 MHz) and AIS 2
(162.025 MHz). Under the auspices of IALA, the ITU Radiocommunication Study Group,
Working Party 8B prepared a new Recommendation ITU–R M.1371-1 which was formally
approved by ITU (November 1998) and is now the adopted technical standard for AIS.
Revised editions of the document were eventually approved. The latest revision of the
recommendation is the ITU-R M.1371-4, emitted in 2010.
This Recommendation specifies the following technical criteria, among others:
• Transceiver characteristics;
• Modulation;
• Data format, messages and packaging;
• Time Division Multiple Access (TDMA);
• Channel management.
1.6 THE ROLE OF IEC

Founded in 1906, the International Electrotechnical Commission (IEC) is the world
organisation that prepares and publishes international test standards (and required test results)
for electrical, electronic and related equipment. IEC also prepares type approval test
specifications for mandatory ships equipment.
Following the adoption of the IMO Performance Standard and the ITU Technical
Characteristics for the AIS, there remained one more standard to prepare and adopt.
This was the IEC Standard entitled “IEC 61993 Part 2: Ship-borne Automatic
Identification System (AIS). Operational and Performance Requirements, Methods of Testing
and Required Test Results”. This Standard is to be used by Administrations to “type
approve” AIS equipment fitted on ships to which SOLAS Chapter V applies (Class A AIS).
The IEC Technical Committee 80 Working Group 8 (IEC/TC80/WG8) carried out the
work, and the Standard was adopted in 2001. It includes, for example, the following:
• Test specification;

• Data in/out standard;
• Connector standard;
• Built-in Test Unit details.
In the following years, other AIS related standards have been approved by the IEC to
account for types of AIS stations other than Class A: IEC 62287-1 (Class B, 2006), IEC
62320-1 (Base Stations, 2007), IEC 62320-2 (Aids to Navigation, AtoN, 2008).
Regulation 19 of SOLAS Chapter V - Carriage requirements for shipborne navigational

systems and equipment - sets out navigational equipment to be carried on board ships,
according to ship type. In 2000, IMO adopted a new requirement (as part of a revised new
chapter V) for all ships to carry automatic identification systems (AISs) capable of providing
information about the ship to other ships and to coastal authorities automatically.

CHAPTER 2
ABT-1103 OVERVIEW
2.1 GENERAL DESCRIPTION

According to IMO recommendations, the AIS system may be used by Coastal
Authorities to improve monitoring of maritime traffic and VTS (Vessel Traffic Services)
operations. The AIS technology exploits Time Division Multiple Access (TDMA)
transmissions over marine VHF channels and the utilization of GNSS (Global Navigation
Satellite Systems) receivers like the GPS (Global Positioning System) for positioning and
timing. Transmissions of position information occur in automated, safe and accurate fashion.
In addition to this, the AIS system integrates position information with static and dynamic
data which enable full identification of vessels.
The ABT-1103 base station has been designed according to the international regulations
(ITU-R M.1371 and IEC 62320-1) and is fit to be integrated both in local port systems and in
wide regional monitoring systems. The Base Station will receive data from AIS equipped
vessel and it will provide these data on its external interfaces. The Base Station is also able to
transmit data to the vessels, according to the relevant IEC and ITU standards. The exchange
of data between the base station and the monitoring system is carried out through a serial port
(RS232 or RS422); the operating mode of the transponder can be configured using the same
port by means of a dedicated management software.
The ABT-1103 is an independent Base Station (see ITU-R M.1371 for detailed
description). Therefore, the ABT-1103 does not require an external controlling entity to
manage its transmissions but it only needs to be configured (once). Dependent behaviour is
supported for enhanced compatibility with external systems.
The ABT-1103 can also be directly interfaced to one of the PCU (Physical Shore
Station Control Unit) produced by Elman, like the BCS-1135 or the BCD-1135. Those units
expand the ABT-1103 functionalities, by providing:
 a network interface enabling exchange of AIS data using TCP/IP communications;
 an embedded web server with convenient GUI for the configuration and monitoring
of the ABT-1103;
 data filtering;
 support for multiple Base Stations and management of redundancy
 SNMP agent for enhanced and centralized monitoring services;
Refer to the relevant manuals for a detailed description of those PCU units.
When a BCx-1135 controller is not available, the AisConfig software provides a web
based interface to configure every aspects of the ABT-1103 through an available serial or
TCP connection. Contact Elman for details on the AisConfig software.
Finally, the Control Switch Unit CSU-1103 produced by Elman can be used to manage
the redundancy of PSS sites featuring two Base Stations.

2.2 MAIN FEATURES
The following figure shows the main functional blocks of a Base Station as envisioned
by IEC (Ref. Fig. 1, IEC 62320-1).
The ABT-1103 features the following functional elements:
 Two multi-channel VHF receivers for parallel receiving processes on channel A

(default channel is 2087, according to ITU-R M.1084 channel numbering) and
channel B (default channel is 2088). A third VHF receiver can be optionally
installed to enable reception of DSC (Digital Selective Calls) messages or AIS
messages from a third user-selectable channel.
 One multi-channel VHF transmitter which is used for transmissions on both
channel A and channel B. Receivers and transmitter share the same antenna, so AIS
messages cannot be received during own transmissions on any channel.
 Transmissions can occur by using the Fixed Access TDMA (FATDMA) or
Random Access TDMA (RATDMA) as configured by the user and as appropriate.
 A Presentation Interface (PI) which enables the Base Station to exchange data with
external devices. Usually, in a shore based AIS implementation, the Base Station
will exchange data with the Physical Shore Station (PSS) Control Unit which
controls the Base Station or directly with a Logical Shore Station (LSS). The PI can
be used by external devices to configure the Base Station and to read status
information. 1 RS-232 and 3 IEC 61162-2 (RS-422 compatible) serial ports are
provided to physically implement the PI. Default speed is 38400 baud, as per IEC
61162-2 standard, but it is configurable up to 115200 baud.
 A control unit which manages all the other functional blocks, forwards the data
decoded by the TDMA receivers to the PI, and encodes the messages to be
transmitted by the TDMA transmitter whenever requested by messages received on
the PI or by the automatic transmission processes.

 A Differential GPS receiver (DGPS) which provides the internal synchronization
source; the GPS receiver can also be used as the main or the back-up position
source of the Base Station, according to the user desired configuration.
 A Built-In Integrity Test (BIIT) unit which performs self-tests of the main
functionalities of the Base Station and produces appropriate status information that
is routed to the Presentation Interface.
 A power supply.
 An IEC 61162 port to optionally use position data coming from an external sensor.
Also the timing information can be provided by an external unit feeding the
synchronization signal (Pulse Per Second, PPS) to the provided port. This approach
enables the use of a single external position fixing unit for two or more Base
Stations and can simplify the installation.
 An IEC 61162 port to optionally provide to external units the GPS data coming
from the internal sensor. Also the timing information can be provided to external
units using the synchronization signal (PPS) from the provided port. This approach
enables the use of a single internal position fixing unit for two or more Base
Stations and can simplify the installation. The same port can also be configured to
provide RTCM messages to external position sensors if differential information is
received from the AIS VDL.
 An RTCM SC-104 port to enable DGNSS (Differential GNSS) transmissions from
the Base Station to other AIS stations connecting a DGNSS station. The same
signal can also be used to enhance the position fix of the embedded GPS receiver.
The following sections will describe in greater details some of the main functionalities
and features of the ABT-1103 Base Station, focusing mainly on the enhancements in respect
to the IEC 62320-1 standard.
2.2.1 VHF Receivers

The VHF receivers can be used on all the channels defined inside marine VHF band
(156 - 162.025 MHz). Sensitivity has been enhanced to reach -112 dBm @ 20% PER (Packet
Error Rate). All the VDL messages defined by ITU-R 1371-4 are supported.
2.2.2 VHF transmitter

The VHF transmitter can support transmission power levels defined by the user in
addition to the standard defined ones (2 and 12.5 W). Output power level can reach 30 W. All
the VDL messages defined by ITU-R 1371-4 are supported.
2.2.3 Presentation Interface

Data format is as defined by the IEC 61162 standard. All the sentences defined inside
the IEC 62320-1 standard are supported. Thus the ABT-1103 can be configured completely
using the PI and additional information can be presented to the user enabling the output of
FSR (VHF data link statistics) and VSI (additional information related to AIS messages)
sentences.

Standard IEC sentences like ABM, BBM and VDM can be sent on the PI to have
addressed binary and safety messages, broadcast binary and safety messages and transparent
AIS messages, respectively, to be transmitted by the Base Station. Other peculiar Base Station
message transmissions can be triggered using the ACM, AGA, ASN and DLM sentences, as
defined inside IEC 62320-1 standard.
In addition to the standard sentences, customized IEC 61162 sentences are available.
Most significantly, the firmware of the ABT-1103 can be upgraded during normal operation
using IEC 61162 sentences, avoiding any service interruption and enabling the firmware
upgrade using remote devices. Moreover, customized IEC 61162 sentences are provided to
support non standard optional features like secure transmissions. These options need to be
installed to be operational (refer to relevant appendices if provided by the manufacturer).
2.2.4 Type of operation modes

The ABT-1103 supports both the dependent and the independent operation as defined in
the IEC 62320-1 standard. When operated as dependent station, the PSS is responsible to
control completely the transmission operations of the Base Station by using TSA + VDM
sentences pair. When operated as independent station the Base Station will organize
autonomously its transmissions according to the configured Fixed Access TDMA (FATDMA)
plan; moreover Random Access TDMA (RATDMA) can be enabled to let the Base Station
chose the appropriate slots for its non-periodic transmissions.
2.2.5 DGPS unit

Thanks to the modular design, the embedded GPS unit can be replaced by enhanced
compatible models when they will be available.

2.3 PRODUCT BREAKDOWN STRUCTURE (PBS)
The following diagram shows the complete structure of the ABT-1103 Base Station.
The ABT-1103 is mainly made of the AMT-1103 which implements the AIS transponder
proper and the DCI-103 subsystem which is the AC/DC power supply for the transponder.
AIS Base Station ABT-1103
SYSTEM DEVICES SUBSYSTEMS MODULES ACCESSORIES
ABT-1103
AMT-1103
MCU-103
Firmware
GPS Rx
TXV-103
RXV-103
RXV-103
AFL-103
VCR-103
ICB-103
DCI-103
Cabling
AC power cord
Optional DC
power cord
Optional PI to
PC serial cable
VHF antenna
GPS antenna
Figure 2 – ABT-1103 product breakdown structure

The AMT transponder is built upon a modular architecture which allows for easy
replacement of the subsystems when needed. The following subsystems can be located inside
the AMT-1103:
 The MCU-103 is a PCB featuring the main processor of the AIS transponder and
the hardware for the interface ports. The MCU-103 carries the internal GPS module
which can be easily replaced. The firmware of the whole device is stored on non-
volatile memory and can be easily upgraded without interrupting the normal
working behaviour.
 The TXV-103 is a PCB implementing the VHF transmitter hardware including the
RF power amplifier.
 The RXV-103 is a PCB implementing a VHF receiver hardware. Two RXV
receivers are normally located inside the AMT, a third can be installed if requested
to implement a third AIS or a DSC receiver.
 The VCR-103 is a PCB featuring the internal power supply of the unit.
 The ABT-1103 is delivered together with a power supply cable and the VHF and
GPS antennas. Refer to the install section for detailed instructions on how to
properly connect these parts.
2.4 APPLICABLE REGULATIONS AND STANDARDS

The ABT-1103 has been designed and manufactured in compliance with the following
standards and recommendations:
 ITU-R M.1371-4 (04/2010) – ITU Recommendation on the technical characteristics
for a universal shipborne Automatic Identification System (AIS) using time division
multiple access in the Maritime Mobile Band.
 IEC 62320-1 (Ed.1 2007-02 + Amendment 1 2008-10) – Maritime navigation and
radiocommunication equipment and systems – Automatic identification system (AIS) –
Part 1: AIS Base Stations –Minimum operational and performance requirements,
methods of testing and required test results.
 IEC 61108-1 (Ed.2 2003-07) – Maritime navigation and radiocommunication equipment
and systems – Global navigation satellite systems (GNSS) – Part 1: Global positioning
system (GPS) – Receiver equipment – Performance standards, methods of testing and
required test results.
 IEC 61162-1 (Ed.4 2010-11) – Maritime navigation and radiocommunication equipment
and systems – Digital interfaces – Part 1: Single talker and multiple listeners.
 IEC 61162-2 (Ed.1 1998-09) – Maritime navigation and radiocommunication
equipment and systems – Digital interfaces – Part 2: Single talker and multiple
listeners, high-speed transmission.
 ITU-R M.1084-4 (2001) – Interim solutions for improved efficiency in the use of the
band 156-174 MHz by stations in the maritime mobile service.
 IEC 60950-1 (2005-12) – Information technology equipment – Safety – Part 1:
General requirements.
 EN 55022 (2006 + Amendment 1 2007) – Information technology equipment – Radio
disturbance characteristics – Limits and methods of measurement.
 EN 61000 – Electromagnetic compatibility (EMC) – Parts:
3-2 (2006) – Limits for harmonic current emissions.

3-3 (1995 + Amendment 1 2001 + Amendment 2 2005) – Limitation of voltage changes, voltage
fluctuations and flicker.
4-2 (2000) – Electrostatic discharge immunity test.
4-3 (2008) – Radiated, radio-frequency, electromagnetic field immunity test.
4-4 – Fast transient common mode.
4-5 – Surge.
4-6 – Common mode RF injection.
4-11 – Voltage dips.
The ABT-1103 has been designed and manufactured also considering and applying the
following international regulations, recommendations and standards when appropriate:
 1974 Solas Convention - Chapter V.
 IMO Recommendation on Performance Standards for a Universal Shipborne
Automatic Identification System (AIS) - MSC. 74 (69), Annex 3.
 ITU Radio Regulations, Appendix S18, Table of Transmitting Frequencies in the VHF
Maritime Mobile Band.
 IALA Guidelines on the Universal Automatic Identification System (Volumes 1 and
2).
 ITU-R M.825-3 (1998) – Characteristics of a transponder system using Digital
Selective Calling techniques for use with vessel traffic services and ship-to-ship
identification.
 IEC 61993-2 (2001-12) – Maritime navigation and radiocommunication equipment
and systems – Automatic identification systems (AIS) – Part 2: Class A shipborne
equipment of the universal automatic identification system (AIS) – Operational and
performance requirements, methods of test and required test results.
 IEC 62287-1 (2006-03) – Maritime navigation and radiocommunication equipment
and systems – Class B shipborne equipment of the automatic identification system
(AIS) – Part 1: Carrier-sense time division multiple access (CSTDMA) techniques.
 IEC 60945 Ed.4 (2002-08) – Maritime navigation and radiocommunication equipment
and systems – General requirements – Methods of testing and required test results.
 IALA Recommendation A – 123 on the Provision of Shore Based Automatic
Identification Systems (AIS).
 IALA Recommendation A – 124 on AIS Shore Stations and Networking Aspects
Related to the AIS Service.

CHAPTER 3
MODES OF OPERATION
3.1 Introduction
The ABT-1103 is fully compliant to an independent AIS Base Station, as defined in the
IEC 62320-1 standard. Therefore, the behaviour of the ABT-1103 can be fully configured
using standard IEC 61162 sentences on any of the included PI ports.
The mode of operation of the ABT-1103 may be set to receive only, to dependent
behaviour and to independent behaviour, depending on the operator requirements and on the
available infrastructure.
3.2 Receive only mode

The ABT-1103 needs only a few configuration steps to be operated in receive only
mode. When leaving the factory, the ABT has all the automatic transmissions disabled and it
is configured to receive on the two AIS standard channels (2087 and 2088 as defined by the
ITU-R M.1084).
As transmissions may be requested also by sending appropriate messages on the PI

ports, at least one of the following actions is required to force all transmissions off:
 Set the MMSI number to undefined (this is the default factory setting, refer to the
identifier configuration section in this manual);
 Disable transmissions using the standard CAB sentence (refer to the basic
configuration section in this manual);
 Use the hardware TX INHIBIT pin on the ALARM & SENSOR connector.
Messages received from the VDL will be automatically output by the Base Station on
the Presentation Interface using VDM standard sentences. See the relevant AIS data section in
this manual for a detailed description on this matter.
Additional information on received messages can be provided together with the VDM
sentences enabling the additional output using the standard SPO configuration sentence (see
relevant section in this manual).
3.3 Dependent mode

The dependent mode is an operation mode where the AIS Base Station operates like a
slave transmitting device. In dependent mode, all the TDMA processes and algorithms are
executed outside the Base Stations. The Base Station will transmit only if and at the exact
time it is requested to do it. Therefore, the dependent mode requires typically a software
process outside the AIS Base Station which is capable of generating the appropriate messages
with proper content as defined by the ITU-R M.1371 recommendation and the IEC 62320-1
standard. See the relevant section in this manual for detailed instructions on how to generate
the proper sentence sequences using TSA + VDM messages.

The ABT-1103 can store, queue, and schedule transmissions up to 100 messages at the
same time, allowing for relaxed time constraints on the external software.
In order to enable transmissions in dependent mode, the following actions are required:
 Define the MMSI number (refer to the identifier configuration section in this
manual);
 Enable transmissions using the standard CAB sentence (refer to the basic
 Leave unconnected or set to inactive state the hardware TX INHIBIT pin on the
ALARM & SENSOR connector.
 All the automatic transmissions should be disabled by proper configuration of
FATDMA settings (this is the default factory setting, see relevant section on ECB
messages). Note that dependent mode and independent mode can also be mixed
together, having part of the transmissions generated automatically and part
triggered by messages received on the PI by the Base Station.
Note that reception of messages from the VDL is always enabled as long as proper
channels are selected for that. Messages received from the VDL will be automatically output
by the Base Station on the Presentation Interface using VDM standard sentences; messages
transmitted to the VDL will be automatically output by the Base Station on the Presentation
Interface using VDO standard sentences. See the relevant AIS data section in this manual for
a detailed description on this matter.
Additional information on received and transmitted messages can be provided together
with the VDM and VDO sentences enabling the additional output using the standard SPO
configuration sentence (see relevant section in this manual).
Always consider that AIS is a safety related system and that an AIS Base Station
has an important role in the AIS system. A wrong configuration of Base Station’s
transmissions may locally disrupt the AIS service, hence affecting the safety of
navigation. Therefore the AIS Base Station should only be used and configured by
trained personnel of authorized administrations.
3.4 Independent mode

The independent mode is an operation mode where the AIS Base Station operates like
an autonomous transmitting device. In independent mode, once configured, the ABT-1103
can schedule and generate automatically all the user specified messages.
The TDMA processes and algorithms are all executed inside the Base Stations,
simplifying the requirements on external devices and software. External users connected to
the Base Station will still be able to trigger additional transmissions sending the appropriate
messages on the PI ports. See the relevant section in this manual for detailed instructions on
how to generate the proper sentence sequences using TSA + VDM, ABM, BBM, AIR, ACM,
AGA, ASN and VDM messages.
In order to enable transmissions in the independent mode, the following actions are
required:
 Define the MMSI number (refer to the identifier configuration section in this
manual);

 Enable transmissions using the standard CAB sentence (refer to the basic
 Leave unconnected or set to inactive state the hardware TX INHIBIT pin on the
ALARM & SENSOR connector.
 Enable automatic transmissions by proper configuration of FATDMA settings (this
is the default factory setting, see relevant section on ECB messages). Note that
dependent mode and independent mode can also be mixed together, having part of
the transmissions generated automatically and part triggered by messages received
on the PI by the Base Station.
Note that reception of messages from the VDL is always enabled as long as proper
channels are selected for that. Messages received from the VDL will be automatically output
by the Base Station on the Presentation Interface using VDM standard sentences; messages
transmitted to the VDL will be automatically output by the Base Station on the Presentation
Interface using VDO standard sentences. See the relevant AIS data section in this manual for
a detailed description on this matter.
Additional information on received and transmitted messages can be provided together
with the VDM and VDO sentences enabling the additional output using the standard SPO
configuration sentence (see relevant section in this manual).

CHAPTER 4
CONFIGURATION
4.1 Introduction
The ABT-1103 is fully compliant to an independent AIS Base Station, as defined in the
IEC 62320-1 standard. Therefore, the behaviour of the ABT-1103 can be configured using
standard IEC 61162 sentences on any of the included PI ports.
Proprietary Elman sentences have been introduced to allow the configuration of aspects
which are not covered by standard sentences. Refer to the section on IEC data sentences for a
detailed explanation on this matter.
The ABT-1103 includes 4 PI ports all with the same functionalities. Multiple PI ports
can be used at the same time. The HSPORT2 is an RS-232 port, while the other PI ports
(HSPORT0, HSPORT1 and KDS port are IEC 61162-2 ports, electrically compliant to RS-
422). Refer to the Technical Manual for detailed electrical specifications of the PI ports and
for a description of the available connectors and pin-outs.
Note that the configuration information received is stored in non volatile memory and is
retained after a software reset and after a power cycle. The configuration can be reset to
default values with the CAB sentence (refer to the relevant section in this manual).
The available information and the current settings can be read performing queries on the
PI ports. The format of a query for a standard sentence is defined in the IEC 61162-1, while
an Elman proprietary sentence can be queried sending the same sentence with all the fields
kept empty. Refer to the section on IEC data sentences for a detailed explanation on this
matter. Note that a standard query requires to know the talker identifier assigned to the Base
Station, which is “AB” by default but can be changed by the user. The talker identifier can be
known observing the sentences output on the PI.
Software compliant to the IEC 62320-1 and IEC 61162-1 standards should be able to
configure and manage all the aspects of the ABT-1103 with the exception of what is covered
by proprietary Elman sentences. Elman is specialized in delivering customized solutions for
the infrastructure of land based AIS; please, contact Elman if you need support on this aspect.
The ABT-1103 can also be directly interfaced to one of the PCU (Physical Shore
Station Control Unit) produced by Elman, like the BCS-1135 or the BCD-1135. Those units
expand the ABT-1103 functionalities, by providing:
 a network interface enabling exchange of AIS data using TCP/IP communications;
 an embedded web server with convenient GUI for the configuration and monitoring
of the ABT-1103;
 data filtering;
 support for multiple Base Stations and management of redundancy
 SNMP agent for enhanced and centralized monitoring services;
Refer to the relevant manuals for a detailed description of those PCU units.
In particular the embedded web server can be extremely useful to configure the AIS
Base Station without having to implement the IEC protocol.

4.2 Installation parameters
The PELMAIS proprietary sentence can be used to read and configure some installation
related parameters. These include:
 baud rates of the serial ports of the ABT-1103;
 functions assigned to the DGNSS ports;
 GPS data on the PI port enabling;
 Pulse Per Second (PPS) In and Out enabling;
 VDM out filter level.
Refer to the section on IEC data sentences for a detailed explanation on the format of
this sentence.
Figure 3 – Installation settings
If the ABT-1103 is connected to a BCS-1135, the installation settings can be displayed

and modified accessing the web interface as displayed in the figure above.
4.2.1 Baud rates of PI ports

By factory default, all the PI ports baud rates are set to 38400, in compliance to IEC
61162-2 standard. It is normally recommended to keep the default setting.

However, there are some situations where different settings may be used.
For instance, if the AIS data output on the PI must be transmitted over a radio link with
limited dedicated capacity, the baud rate may be decreased. It should be kept in mind that
baud rates below 38400 may cause loss of data if the ABT-1103 radio coverage includes a
vessel crowded area or the ABT-1103 is frequently polled on the PI.
On the contrary, when the ABT-1103 receives many messages from vessels and/or the
ABT-1103 has been configured to generate additional information and Comment Blocks it is
highly suggested to increase the baud rate to the maximum available in order to minimize the
risk of saturating the port capacity.
Refer to the section on IEC data sentences for a list of values for possible baud rates.
4.2.2 Baud rates of Sensor ports

By factory default, all the Sensor ports baud rates are set to 38400, in compliance to
IEC 61162-2 standard. Sensor ports are typically not used in normal PSS.
A sensor port may be used to provide position and time information from an external
sensor. In this case, the baud rate should match that of the sensor and the sensor should
provide standard sentences as GBS (RAIM and accuracy); GGA, GLL, GNS or RMC
(position and time); ZDA (time).
Refer to the section on IEC data sentences for a list of values for possible baud rates.
4.2.3 DGNSS OUT port

By factory default, the DGNSS OUT port baud rate is set to 38400, in compliance to
IEC 61162-2 standard.
The DGNSS OUT port can be configured to output the IEC 61162 sentences from the
internal GPS so that the ABT-1103 can act as a position sensor for external devices, including
other Base Stations.
The DGNSS OUT port can also be configured to output DGNSS corrections in RTCM
formatted messages, as received from the ABT-1103 on the VDL link (refer to message 17 as
defined in ITU-R M.1371). Hence the ABT-1103 can provide correction information to
external devices, including other Base Stations or external GPSs. Note that this service
requires that remote Base Stations are broadcasting the DGNSS correction on the AIS
channels.
Refer to the section on IEC data sentences for a list of values for possible baud rates and
options for the DGNSS OUT port.
4.2.4 RTCM / DGNSS IN port

The ABT-1103 includes a dedicated port (DGNSS IN) that can accept DGNSS
corrections in RTCM formatted messages.
Alternatively, any PI or sensor port can be used also as the RTCM input port. This
allows using a single port when the DGNSS corrections are available from the same interface
used to connect the ABT-1103 to a PI application or an external sensor.
The RTCM input port can be configured to forward DGNSS corrections in RTCM
formatted messages, as received from the port, to the GPS internal to the ABT-1103. Hence
the internal GPS can be corrected enabling an augmented and more precise position fix.

The RTCM input port can also be used to provide the DGNSS information to be
transmitted on the VDL by the Base Station using message 17, as defined by ITU. This
service is configured using the PELMDGC sentence.
Refer to the section on IEC data sentences for a list of values for possible baud rates and
options for the DGNSS in port.
4.2.5 RMC sentence over PI ports

The ABT-1103 can be configured to transmit once per second the standard IEC RMC
sentence including the position and time information currently stored in the AIS over any of
the PI ports. This configuration can be useful to provide position and time information to
external devices (for instance PCU units).
Refer to the section on IEC data sentences for a list of possible values.
4.2.6 PPS out enable

The ABT-1103 can be configured to output the Pulse Per Second signal from the GPO0
pin to enable time synchronization of external devices, like other Base Stations. This service
requires that proper UTC synchronization is achieved by the internal GPS receiver. The PPS
signal can be temporary replaced by other test signals.
Refer to the section on IEC data sentences for a list of possible values. Refer to the
Technical Manual for electrical specifications of the GPO0 pin.
4.2.7 PPS in inversion

The ABT-1103 can be configured to invert the Pulse Per Second signal received from
the GPI0 pin. This may be needed if the ABT-1103 is configured to use an external time
source instead of the internal GPS receiver.
Refer to the section on IEC data sentences for a list of possible values. Refer to the
Technical Manual for electrical specifications of the GPI0 pin.
4.2.8 VDM out filter

The ABT-1103 can be configured to filter out the VDM messages to be sent on the PIs.
Typically the ABT-1103 outputs all the messages received from the VDL as VDM sentences.
However it may be selected to discard VDL messages addressed to other stations and/or
informative VDL messages. Informative messages usually don‟t contain information relevant
for the user as are related to the internal AIS management rather than to the targets
information.
Refer to IEC 61993-2, table 7 for a list of informative messages. Refer to the section on
IEC data sentences for a list of possible values.

4.3 Version information
The version information of the ABT-1103 can be accessed by querying the standard
VER sentence. Accessing the version information is particularly useful to know the current
UniqueID of the Base Station.
Figure 4 – Version information
The figure above shows the version information as showed by the BCS-1135 unit,
including UniqueID, type of station, Vendor ID, Model code, Hardware and Software
revisions and serial number.

4.4 Base Station Identifiers
4.4.1 Talker Identifier

The talker identifier (TID) of a IEC 61162 compliant device is a two letter code which
is output at the start of every standard sentence.
Note that a standard query is required to use the talker identifier assigned to the Base
Station, which is “AB” by default but can be changed by the user using the BCF sentence.
Queries will not be answered by the ABT-1103 if the TID used in the query does not match
the TID configured for the BS.
The talker identifier can be known observing the sentences output on the PI. The
UniqueID identifier should be preferred over the talker identifier to address different Base
Stations over a network. Especially for large networks including several Base Stations, it is
recommended to use Unique Identifiers to address the BSs and leave the talker ID to the
default setting. A valid talker identifier shall not start with the letter „P‟ (capital p).
Figure 5 – Configuration of IDs using the BCS-1135 unit
4.4.2 Unique Identifier

The Unique Identifier, or UniqueID, is the main identifier of an AIS Base Station on the
Presentation Interface. It can be used to address a message to a specified Base Stations on
complex networks. Other device and software processes may identify themselves using
UniqueIDs during data exchange with the ABT-1103, ensuring safer communications.
Some of the messages needed to configure the AIS Base Stations require that the
UniqueID of the addressed station is explicitly specified. The ABT-1103 rejects messages if
the included UniqueID for the recipient is different from its own. It is suggested to use the
Comment Block extension to the IEC 61162 standard to enforce UniqueID usage also for all
the exchanged messages. Refer to the Comment Block section in this manual for details.

By factory default, the UniqueID of an ABT-1103 is set to ELMx where x is the serial
number of the unit. The current UniqueID can be read by querying the VER message as
described in the previous section.
4.4.3 MMSI
The MMSI number is the main identifier of an AIS station on the VDL. The MMSI of a
transmitting station is always included inside the AIS messages transmitted on the VDL. The
MMSI of other stations can be used to address transmissions on the VDL to selected
recipients. The MMSI is released by the National Competent Authority and it is a 9 digit
number; Base Stations MMSIs always start with 2 leading zeroes.
A Base Station needs to be programmed with an MMSI number in order to be enabled
to transmit. An AIS Station should always be programmed with an MMSI released by a
Competent Authority to prevent misleading information to be received by other stations.
A Base Station can also be instructed to transmit messages including different MMSIs
using VDM sentences on the PI.
Note that executing unauthorized AIS transmissions and using a not properly
assigned MMSI is considered illegal in many nations and as such subject to persecution.
The UniqueID and MMSI identifiers can be changed using the standard SID sentence.
Note that it is required to know the current value of the UniqueID in order to be enabled to
change the identifiers.
4.4.4 Station Name

The ABT-1103 supports the transmission of message 24A to allow remote stations to
associate a name to the Base Station MMSI number. The name can be up to 20 characters
long and it is transmitted every 6 minutes alternating on enabled channels. If the name is set
to not available, periodic message 24A transmissions are stopped.
The ABT-1103 may use available FATDMA slots or slots chosen using the RATDMA
algorithm, if enabled, for message 24A transmissions. Refer to the basic configuration section
for details. Message 24A can also be polled by remote stations using the interrogation
message 15.
The Station Name can be configured on the ABT-1103 using the SSD sentence. Refer to
the section on IEC data sentences for additional information.

4.5 Basic configuration
The basic configuration of the ABT-1103 Base Station can be set by using the standard
BCF, BCE and CAB sentences.
Figure 6 - Configuration of basic settings using the BCS-1135 unit
4.5.1 Position source

By default, Base Stations transmit surveyed positions. The latitude, longitude and
accuracy of the position should be properly configured using the standard BCF sentence.
Alternatively, the position may be dynamically calculated by the internal GPS receiver
or input using one of the PI or sensor ports and a connected external device. The ABT-1103
can also be configured to use fallback mechanisms between the possible position sources.
Note that the ABT-1103 transmits the configured or calculated position only if a
transmission plan for message 4 has been set. Refer to the FATDMA configuration for details.

4.5.2 UTC source
By default, Base Stations acquire time synchronization using their internal GPS
receiver. The ABT-1103 supports also an external time source that can be enabled by using
the standard BCE sentence and connecting an external sensor to one of the PI or sensor ports
and the GPI0 pin. Time information should be input using standard IEC sentences together
with an accurate PPS pulse. It is highly recommended that the PPS jitter plus error is less than
1 us.
The ABT-1103 can also be configured to use fallback mechanisms between the possible
time sources.
Note that the in PSS made of multiple Base Stations, the ues of external sources for time
(and position if needed) can minimize the installation of GPS antennas. For instance a single
GPS receiver can be used to provide timing to all the Base Stations.
4.5.3 VHF Channels

The two VHF channels to operate the ABT-1103 can be configured using the standard
BCF sentence. Refer to the section on IEC data sentences for details.
Note that a Base Station should always use the standard AIS channels (2087 and
2088) for both receptions and transmissions, unless explicitly authorized by a competent
authority. Failing to do so may disrupt safety services managed on VHF channels, thus
impacting on the safety of navigation.
4.5.4 Transmitted power

The radiated power can be selected between high (12.5 W, default) and low (2 W) for
each of the two VHF channels using the standard BCF sentence.. The ABT-1103 may be
factory configured to transmit at power levels different from the default ones. Contact Elman
for details.
4.5.5 RATDMA control

Transmissions using Random Access TDMA may be enabled or disabled using the
standard BCE sentence. RATDMA transmissions don‟t require FATDMA allocations; hence
enabling RATDMA may facilitate the transmissions of user requested messages through, for
instance, standard VDM, ABM, BBM or AIR sentences.
Disabling RATDMA prevents the ABT-1103 to transmit on slots other than the ones
allocated with DLM and ECB sentences.
4.5.6 VDL message retries

The ABT-1103 can send addressed messages to remote AIS stations if so requested
through a standard ABM on a PI port. Addressed messages are automatically retransmitted up
to 3 times if an acknowledgement is not received from the remote station.
The default behaviour can be changed setting the number of retries to the desired value
using the standard BCF sentence.
4.5.7 Message Repeat Indicator

The Repeat Indicator (RI) is a field included in all the VDL messages transmitted by
AIS stations. The default value is zero. Values above zero mean that the message is being
retransmitted RI times by repeater stations. Receiving stations use the RI field to understand if
the message has been broadcast by the genuine station or by an AIS station acting as a
repeater. In the latter case, the message is disqualified to be used for synchronization
purposes. Up to 3 retransmissions of the same message may occur.
The ABT-1103 can be forced to use value of RI greater than zero in its own transmitted
messages using the standard BCF sentence. This is only suggested if the BS is used as a
repeater or must be disqualified as synchronization source.
4.5.8 ADS Interval

The ABT-1103 periodically outputs on the PI ports the ADS sentence which provides a
brief snapshot of the status of the device. The ADS sentence is also output whenever there is a
change in the device status. The ADS sentence may prove particularly useful for monitoring
software linked to the ABT-1103.
The interval between two ADS sentence can be configured using the BCE sentence. The
recommended interval is 60 seconds. A value of zero disables periodic ADS sentences.
Refer to the section on IEC data sentences for details.
4.5.9 Comment blocks

The ABT-1103 support comment blocks extension to standard IEC sentence in
compliance with IEC 62320-1 standard. Refer to sections A.2 and A.3 of the IEC 62320-1
standard for detailed information on comment blocks.
Comment Blocks (CB) may enhance the protocol of PI ports by:
 Attaching additional information (like e.g. timestamps) to sentences;
 Managing conveniently recipients and senders by using UniqueIDs;
 Enforcing integrity of data exchange by encapsulating multi sentence messages in
groups.
The ABT-1103 can be configured to require the usage comment blocks with the BCE
sentence.
If CBs are not required, the IEC sentences received without CB extensions will be
accepted by the device and CB extensions to IEC sentences will not be normally output by the
Base Station. If the ABT-1103 receives from a PI port IEC sentences extended with CBs, they
will also be accepted and if answers are required they will include CB extensions.

If CBs are required, only IEC sentences received with CB extensions will be accepted
by the device and CB extensions to IEC sentences will be always output by the Base Station.
The bandwidth requirements on PI ports may substantially increase when CBs are required;
therefore an increase of the baud rate should be considered for BSs which cover highly
populated areas. Note that IEC sentences without CB extensions are always accepted if
received from the KDS port, even when CBs are required; thus the KDS port may be used to
connect legacy applications and devices which do not support CBs.
The ABT-1103 supports the following parameters inside CBs:

 Group (xGy) – A CB group is transmitted on a PI port whenever IEC sentences
need to be logically grouped together. For instance, this is the case for multi
sentence messages like VDM or VDO, linked sentence like VDM and VSI, or
multi-sentence answers to query like DLM and ECB lists. A CB group must be
completely and correctly received from a PI port for the linked IEC sentences to be
processed. All the sentences in the group inherit the CB parameter set of the group.
Parameters may be specified in each CB line of the group but it is suggested to
keep all the parameters in the first line of the group. If the same parameter is
included more than once in the same group, only the last occurrence will be used.
 Time stamp (c) – Time in seconds calculated from January 1, 1970 at 00:00:00. If
time information is available, the time stamp is included in all the CBs generated. It
can be particularly useful when associated to received VDM messages, as it
represents the time of reception from VDL in a convenient format. It is ignored
when received.
 Source (s) – identification of the talker. It is included in all the CBs generated from
the ABT-1103, the UniqueID is used as identifier. When received from the Base
Station, the source field is associated to the linked IEC sentence(s). If answers are
generated on the PI port as result of the sentence processing, the CB extension of
the answering sentences will include the destination parameter filled with the
source identifier in order to provide a correctly addressed response.
 Destination (d) – identification of the recipient. It is included in the CBs generated
from the ABT-1103 only if they are produced as the response to a query as
explained above. When received from the Base Station, the destination field is
associated to the linked IEC sentence(s). If the destination field is different from the
Base Station own Unique ID, associated IEC sentences are discarded. Even if the
destination parameter is not included in the CB or matches the Base Station‟s
Unique ID, associated sentences may be discarded because of their content. For
instance, queries will be discarded because of talker IDs mismatch and sentences
like ECB may be discarded for UniqueIDs mismatch.
 Information (i) – The information field may be used to transparently associate
additional data to sentences. It is used in some extension to standard behaviour.
Refer to relevant documentation for details.

4.6 FATDMA configuration
Base Stations use the Fixed Access TDMA scheme for their periodic transmissions.
FATDMA transmissions from the BSs in the AIS are regulated as follows:
 Base Stations should reserve a number of slots from the TDMA frame for their
transmissions. Slots can be reserved also for transmissions from other stations, if
needed. Typically, on each channel, equally spaced slots should be reserved for
message 4 transmissions, with a 250 slot interval to account for semaphore
transmissions. At least one slot per frame should be reserved for message 20
transmissions and the other messages. Standard DLM sentences are used to
configure reservation; refer to the section on IEC data sentences for a list of
possible values.
 Base Stations should plan transmissions of their required periodic messages basing
upon the slot reserved for own transmissions. Periodic messages include:
- Base Station Report (message 4); message 4 is used to transmit position and time information. The
report rate of message 4 should always set to 10 seconds. The report rate is automatically set by the
BS to 3⅓ seconds when the BS behaves as a semaphore.
- Data Link Management (message 20); message 20 is used to broadcast the reservations configured
with the DLM sentences to remote stations. At least one transmission for epoch (6 minutes) should
be enabled.
- DGNSS Broadcast message (message 17); message 17 is used to broadcast DGNSS corrections if
available.
- Channel Management (message 22); message 22 is used to broadcast the parameters for the AIS
channels to be used by remote stations.
- Group Assignment Command (message 23); message 23 is used to assign report rates to groups of
remote stations.
Message 4 and 20 should always be transmitted by BS in order to allow remote
stations to properly detect the BS and execute actions as commanded, like slot
reservations, changes of report rate, changes of VHF channels, etc. Standard ECB
sentences are used to configure automatic and periodic transmissions; refer to the
section on IEC data sentences for a list of possible values. Slot planned for
transmission using ECB sentences should always have associated local reservation
made with DLM sentences.
 Administrators of AIS systems should always consider VDL load implications of
reservations from Base Stations. As reserved slots will not be available for
transmissions from other stations in a 120 nautical miles range from the reserving
BS, having several BS each with many reserved slots in the same area may impact
in the overall operation of AIS.
 Administrators should also consider regional cooperation to avoid overload of the
VDL and conflicts in the reservation of slots. Refer to the FATDMA section in
IALA A.124 guideline for recommendations on how to reserve and use slots
depending on Base Station geographical position.
 For the reasons above, a FATDMA plan should always be developed at the higher
possible administrative level to allow for consistent and safe transmissions from
BSs in the interested area.

Figure 7 - Configuration of FATDMA using the BCS-1135 unit
Note that FATDMA configuration of the ABT-1103 is not needed if Receive only or
Dependent Mode are used; in this case all the reservations and all the transmission plans
should be deleted from the configuration of the device. However, consider that a FATDMA
plan should still be implemented when Dependent Mode is used and properly deployed on the
device or software controlling the transmissions of the ABT-1103.
If you need assistance in configuring the FATDMA of Base Stations, you can contact
Elman. Also refer to the FATDMA section in IALA A.124 guideline for a detailed
explanation of the FATDMA issues.

4.7 Channel management
Channels AIS1 (2087) and AIS2 (2088) have been internationally reserved to AIS
transmissions. By default, all the AIS stations transmit and receive on both the AIS channels.
However, local authorities may decide to use a different pair of maritime VHF channels for
AIS transmissions in a specified region. Shore stations should communicate to remote stations
the local channel settings through DSC, AIS transmissions or both.
Local AIS channel settings may be configured on the ABT-1103 using the standard
ACA sentence. Refer to the section on IEC data sentences for a list of possible values.
The ABT-1103 supports up to 8 local channel settings at the same time. Transmissions
of message 22 should be enabled by proper FATDMA configuration using the ECB sentence.
Refer to FATDMA configuration section for additional information. Use of DSC service
should be considered alongside AIS transmissions to enforce the reception of channel
management messages in cases where AIS stations are not using the VHF channels where
AIS message 22 is transmitted.
Figure 8 - Configuration of channel managementusing the BCS-1135 unit
Note that a Base Station should always use the standard AIS channels (2087 and
2088) for both receptions and transmissions and should avoid changing other stations’
frequencies, unless explicitly authorized by a competent authority. Failing to do so may
disrupt safety services managed on VHF channels, thus impacting on the safety of
navigation.

4.8 Processing and Output Selection
Figure 9 - Configuration of processing and output using the BCS-1135 unit
The ABT-1103 can be optionally configured to output additional information related to

messages received and transmitted on the VDL and general statistics on the VDL status using
the standard SPO sentence. Refer to the section on IEC data sentences for a list of possible
values.
The operator can enable the generation of a linked VSI sentence for each VDM sentence
generated after the reception of a message from the VDL. The VSI can be configured to
include:
 UTC time of reception with resolution up to 100 ns;
 number of first slot of received message in the TDMA frame;
 received signal strength (RSSI)
The measure of Signal to Noise ratio is not supported by the ABT-1103.
The operator can enable the generation of a linked VSI sentence for each VDO sentence
generated after the transmission of a message on the VDL. The VSI can be configured to
include:
 UTC time of transmission;
 number of first slot of transmitted message in the TDMA frame.
The operator can enable the generation of FSR sentences at the start of a TDMA frame
for each channel. The FSR can be configured to include a user-specified set of statistics on the
VDL usage including:

 the number of slots occupied by valid received messages in the previous frame;
 the number of slots occupied by own transmission in the previous frame;
 the number of slots with CRC failures in the previous frame;
 the number of slots with received signal strength (at least 10 dB above the average
noise) in the previous frame;
 average noise in the previous frame;
 the number of slots reserved with transmissions from other stations in current
frame;
 the number of slots reserved with own transmissions in current frame.
The additional information can be enabled for any or both the VHF channels, only for a
single frame or continuously. Refer to the section on IEC data sentences for detailed
information on the content of VSI and FSR sentences.
The bandwidth requirements on PI ports may substantially increase when VSI are
enabled; therefore an increase of the baud rate should be considered for BSs which cover
highly populated areas.

4.9 DGNSS corrections
4.9.1 Transmission
The ABT-1103 can be configured to transmit on the VDL through message 17 the
DGNSS corrections received from the RTCM port using the proprietary sentence PELDGC.
Refer to the section on IEC data sentences for detailed information.
This service requires that a Differential Station providing messages in RCTM format is
connected to the ITU-R M.823 compliant RTCM input port. Only the RTCM messages 1 and
9 (for GPS) and 31 and 34 (for GLONASS) are eligible to be transmitted through the AIS
service. Other messages will be quietly dropped. The RTCM input port can be configured as
described in the section 4.2.4.
This service also requires that the automatic transmission of message 17 is enabled by
appropriate configuration of the transmission plan (refer to the FATDMA configuration
section).
The ABT-1103 must be configured with the Reference Station ID and the position of
the Station providing the RTCM messages; if the configured position is not valid or the
configured Reference Station ID mismatch the one in RTCM messages, the messages will be
discarded. Alternatively, the position of the specified Reference Station can be acquired from
the RTCM data stream. Message 3 for GPS corrections or message 32 for GLONASS
corrections should be delivered in the RTCM stream to allow for the dynamic acquisition of
the Reference Station position.
Once accepted an RTCM messaged is queued for transmission and it is actually
transmitted when a slot with a scheduled transmission of message 17 is reached. A timeout
may be configured to drop RTCM messages if not transmitted in the specified time. The
default timeout is 60 seconds as specified in the IEC 62320-1 standard and it should be
changed only by authorized administrators.
New RTCM messages overwrite the old ones in the queue so that only the most current
one is transmitted. The same RTCM message can be transmitted several times if not
overwritten before the timeout expiration.
A timeout may be configured so that the appropriate alarm message is generated by the
BIIT if no correct RTCM messages are received from the RTCM input port in the specified
time.
Note that DGNSS corrections may also be transmitted by the ABT-1103 if delivered
through VDM messages on a PI port. TSA+VDM pairs cause transparent transmission on the
specified slots and do not require other configurations.
VDM sentences (no TSA) encapsulating a message 17 may be:
 Transmitted in slots dedicated to message 17 as specified with the ECB sentence, in
this case the same timeout considerations of RTCM messages from RTCM input
port apply;
 Transmitted in slots reserved with DLM sentences for own broadcasts and not yet
assigned to any transmission, if no plan for message 17 transmissions was
configured;
 Transmitted through RATDMA if enabled and the two options above failed;
 Discarded if none of the option above was available.

Figure 10 – Configuration of DGNSS service using the BCS-1135 unit
4.9.2 Reception
The ABT-1103 is also capable of receiving and processing DGNSS corrections
broadcasted by remote stations on the AIS channels. Only the RTCM messages 1 and 9 (for
GPS) and 31 and 34 (for GLONASS) are eligible to be transmitted through the AIS service.
If so configured the received DGNSS messages are sent to the DGNSS OUT port as
RTCM formatted messages so that external devices may use them. Refer to the Installation
parameters section for more information.
DGNSS corrections are also sent to the internal GPS receiver (only the RTCM
messages 1 and 9) to enhance the precision and the integrity of the calculated position. If
multiple Differential Stations are received from the AIS channels and the RTCM input port in
the last 360 seconds, only messages from the best one are sent to the internal GPS receiver
basing upon station health and, in second instance, distance from own station.

4.10 Receiver manager
Usually, each physical receiver of the ABT-1103 is assigned to a specific task: the first
two receivers are dedicated to AIS1 and AIS2 channels reception. If the ABT-1103 is
equipped with a third receiver, this is dedicated either to DSC or WAIS reception or is idle,
depending on the specific set of functions and on the configuration of the AIS station.
The receiver manager function allows changing the default assignment of physical
receivers to tasks so that the operator may reallocate them according to the operational
priority in case of failures.
The receiver manager is only supported by AIS stations including 3 receivers and may
not be enabled if not explicitly required by the customer.
The PELMRXM message allows the configuration of the Receiver manager settings.
Refer to the section on IEC data sentences for a detailed description. The Receiver manager
can also be configured through the WUI of the BCx-1135 controllers or through the
AisConfig software.
Figure 11 - Configuration of the Receiver manager using AisConfig software

4.11Firmware upgrades
The firmware of the ABT-1103 can be easily upgraded even during normal function
time using dedicated software. If the ABT-1103 is connected to an IP network, by using the
BCx-1135 controller or a serial to IP transducer, the upgrade can be managed by a remote PC
connected to the network running the dedicated software.
Contact Elman if you need an upgrade in order to receive instructions and dedicated
software.
Figure 12 - Firmware Upgrade using AisConfig software

CHAPTER 5
OPERATING THE ABT-1103
5.1 Introduction
The ABT-1103, once properly configured as described in the previous section, may not
require any other action from human operators as it is capable of automatically organize its
transmissions, process received messages and detect failures.
Yet, the configuration of the ABT-1103 may be changed anytime it is required without
stopping the normal working processes. Users may interact with the station and the data it
provides by requiring additional transmissions, by polling remote stations and by monitoring
the ABT-1103 status. This section is dedicated to the normal operation of the device.
5.2 Restart and reset

The ABT-1103 may be restarted by issuing a proper CAB sentence on a PI port.
Though it is very rare that a restart command needs to be sent to an ABT-1103 station, it may
be desired to clean up the status of a Base Station after major changes in its configuration or
after that many errors have been detected from the BIIT unit. The configuration is retained
after a restart. Transmissions, if scheduled, are resumed after a minute from the restart.
The configuration status of the ABT-1103 may be to the factory default by issuing a
proper CAB sentence on a PI port. Installation parameters and identifiers are retained after a
configuration reset, while all the other values are reset to the factory default. A configuration
reset deletes all the scheduled transmissions, impacting on the normal Base Station behaviour.
The reset should only be used when the ABT-1103 needs to be reconfigured from scratch.

5.3 AIS data received from the VDL
Receiving AIS data from remote AIS stations, especially from AIS on vessels, is of
course the main function of a Base Station. The ABT-1103 does not need any configuration in
order to receive AIS data from the standard AIS channels.
All the messages received from the VHF Data Link are processed and output to all the
PI ports as standard VDM sentences so that they can be processed, stored and/or displayed by
external devices and systems.
The VDM sentence is widely used as a mean to transport encapsulated AIS messages. A
VDM sentence includes the whole binary content of the associated AIS message. Actual data
transmitted from remote station should be decoded basing upon the process described in
section B.3 of the IEC 61993-2 standard and the encapsulated message format as described in
Annex 8 of the ITU-R M.1371-4. Though the decoding process is not straightforward,
basically all the AIS related commercial solutions support the VDM sentence format. Please
contact Elman if you need help in choosing the best solution for your needs.
The data output on PI ports may be extended by enabling VSI sentences and/or
comment blocks to be linked to VDM sentences. In particular, convenient time tagging of the
VDM sentences is useful when the data is to be transmitted over networks, as normally AIS
messages inside VDM sentences do not feature complete time information. See the
configuration section for details on VSI sentences and comment blocks.
VDM sentences which contain AIS messages addressed to other stations or informative
AIS messages may be filtered out from the data output to the PI ports, if needed. Refer to
VDM out filter paragraph in the section on installation parameters.
Receiving data may fail if:
 The VHF antenna of the AIS unit is not properly installed or positioned. Refer to
the Technical manual for details on installation.
 The AIS channels for reception are not properly configured. Refer to the basic
configuration section for details.
 Strong interference from other transmitters occurs.
 There is no AIS remote station in proximity.
 A failure on the ABT-1103 has occurred. Refer to the alarms and status section for
details.

5.4 AIS data transmitted to the VDL
All the messages transmitted to the VHF Data Link are also output to all the PI ports as
standard VDO sentences so that they can be processed, stored and/or displayed by external
devices and systems.
The VDO sentence has the same format of the VDM sentence which is widely used as a
mean to transport encapsulated AIS messages. A VDO sentence includes the whole binary
content of the associated AIS message. Actual data transmitted from own station should be
decoded basing upon the process described in section B.3 of the IEC 61993-2 standard and
the encapsulated message format as described in Annex 8 of the ITU-R M.1371-4. Though
the decoding process is not straightforward, basically all the AIS related commercial solutions
support the VDM/VDO sentence format. Please contact Elman if you need help in choosing
the best solution for your needs.
The data output on PI ports may be extended by enabling VSI sentences and/or
comment blocks to be linked to VDO sentences. In particular, convenient time tagging of the
VDO sentences is useful when the data is to be transmitted over networks, as normally AIS
messages inside VDO sentences do not feature complete time information. See the
configuration section for details on VSI sentences and comment blocks.
Transmitting data may fail if:

 The VHF antenna of the AIS unit is not properly installed or positioned. Refer to
the Technical manual for details on installation.
 A valid MMSI has not been configured.
 The AIS channels for transmission are not properly configured. Refer to the basic
configuration section for details.
 The ABT-1103 has just been switched on or restarted. Allow at least 1 minute
before transmissions start.
 Transmission has been disabled using the CAB sentence.
 Transmission has been disabled using the hardware TX INHIBIT port.
 A failure on the ABT-1103 has occurred. Refer to the alarms and status section for
details.
The ABT-1103 can be commanded to execute different types of transmissions. The

following paragraphs describe the properties of the possible transmissions and how the user
should interact with the ABT-1103 for proper behaviour.
5.4.1 Periodic transmissions

An AIS Base Station proper should always periodically transmit at least the Base
Station Report (message 4) and the Data Link Management message (message 20). Other
periodic message which may be transmitted if required are the DGNSS Broadcast (message
17), Channel Management (message 22), and the Group Assignment Command (message 23).

5.4.1.1 Independent mode
Periodic transmission may be configured as described in the FATDMA configuration
section in this manual (independent mode). Once properly configured, all the transmissions
are completely managed by the ABT-1103 without the need of other actions. The FATDMA
configuration can be changed at any time during the normal working time of the Base Station,
by enabling / disabling transmissions of messages or by modifying their transmission plans.
The ABT-1103 also support periodic transmissions of the Static Data Report (message
24A), but this is transmitted using RATDMA and so it requires either RATDMA to be
enabled (refer to the basic configuration section) or available FATDMA slots reserved with
DLM sentences (at least a slot every 4 seconds should be reserved for this kind of
transmissions).
When the independent mode is used, the content of the message to be transmitted is
determined as follows:
 Message 4:
o UTC time: internally calculated from time source.
o Position, position accuracy, RAIM and type of EPFS: internally calculated
from position source or as set by basic configuration if a surveyed position is
used.
o Communication State: internally calculated using the current synchronization
status and the transmission plan configured with the ECB sentence for
message 4.
 Message 17: the content is as provided with a VDM sentence received from a PI
port or as calculated from a RTCM sentence received from the DGNSS IN port and
the DGNSS configuration.
 Message 20: the content is as provided with DLM sentences.
 Message 22: the content is as provided with the ACA sentence.
 Message 23: the content is as provided with the AGA sentence.
 Message 24A: the content (name of the station) is as provided with the SSD
sentence.
The MMSI and Repeat Indicator fields are always set as configured (refer to the
Identifiers and Basic configuration sections respectively).
5.4.1.2 Dependent mode

Alternatively periodic transmissions may be completely managed outside the ABT-1103
(dependent mode). Note that FATDMA configuration of the ABT-1103 is not needed if
dependent mode is used; in this case all the reservations and all the transmission plans should
be deleted from the configuration of the device. However, consider that a FATDMA plan
should still be implemented and properly deployed on the device or software controlling the
transmissions of the ABT-1103. This external entity should also consider the external
allocations and reservations determined by processing received messages in order to avoid
transmission conflicts on the VDL.
When the dependent mode is used, the content of the message to be transmitted and the
time of transmission are completely determined by the TSA+VDM pairs received from PI
ports. Up to 100 messages can be queued inside ABT-1103. Refer to the Scheduled
transmissions section below for additional information.
Dependent and independent mode can be used at the same time, having some of the
periodic messages transmitted basing upon the internal FATDMA plan and others transmitted
as commanded by the TSA+VDM pairs.

5.4.2 Non periodic transmissions
Non periodic transmissions are typically requested by an external user sending an
appropriate sentence to a PI port. The type of message transmitted and its contents are
determined by the sentence formatter and its content.
5.4.2.1 Scheduled transmissions

TSA+VDM sentence pairs are a convenient mean to schedule a transmission at a user
specified time and slot. The content of the message to be transmitted is completely
determined by the VDM sentence, allowing for the transmission of any type of message. In
fact, the ABT-1103 does not modify in any way the VDM content prior to transmission.
As explained in the Dependent mode section above, the TSA+VDM sentences can also
be used to generate periodic transmissions, by using a controlling device or software capable
of timely generating the sentence pairs.
When the ABT-1103 receives a TSA+VDM sentence pair, it immediately respond with
a TFR sentence on the same PI port which includes a status field indicating whether the
transmission request has been accepted or not. A transmission request may be rejected if, for
instance, overlaps with an already scheduled transmission with higher priority. Scheduled
transmissions may be queued up to 24 hours in advance; up to 100 messages can be queued
inside ABT-1103. A queued scheduled transmission may be cancelled sending a TSA
sentence properly referencing the addressed transmission.
5.4.2.2 Unscheduled transmissions

VDM sentences (without a linked TSA sentence) are a convenient mean to request a
general transmission. The content of the message to be transmitted is almost completely
determined by the VDM sentence, allowing for the transmission of almost any type of
message.
If a message 4, 11 or 20 or a message providing slot offsets (15 or 16) is included in the
VDM sentence, the transmission request is rejected.
If the message to be transmitted includes a communication state (refer to ITU-R M.1371
recommendation), the communication state is recalculated setting the synchronization status
to that of the Base Station and resetting all the other bits to zero. The repeat indicator field in
the message is always incremented (up to 3).
Once the message has been accepted, the ABT-1103 would schedule the message,
using:
 Free FATDMA slots which have been reserved for local transmissions with DLM
sentences, if available within 4 seconds.
 RATDMA selected slots if RATDMA is enabled and the option above is not
available.
 Free FATDMA slots which have been reserved for local transmissions with DLM
sentences, if available within 6 minutes and the options above are not available.
If none of the options is available, the transmission request is rejected.
When the ABT-1103 has processed the VDM sentence, it immediately respond with a
TFR sentence on the same PI port which includes a status field indicating whether the
transmission request has been accepted or not, and the time and slot at which the message has
been scheduled (if FATDMA slots will be used).

5.4.2.3 Binary and safety messages
Binary messages (messages 6, 8, 25 and 26) are a convenient mean to exchange
application data between AIS stations using the stations as transparent radio modem. A set of
international applications has been defined by IMO, other applications exist or may be
introduced at regional or national level. Binary messages allow extending the functionality of
AIS in many ways: person on board, route information, weather and hydro data, non AIS
targets positions are common examples of data that can be exchanged between applications
external to the AIS using the AIS Base Stations.
A competent authority should always consider the impact of the transmission of

binary messages on the AIS VDL load as AIS is mainly a safety related system: hence
AIS vessel reports should not be constrained by non safety related applications using
AIS.
Safety messages (messages 12 and 14) can be used to transmit text messages related to
safety aspects to remote stations.
Both safety and binary messages can be addressed to a specified remote station as
specified by its MMSI, or be in broadcast.
Addressed binary (message 6) or safety (message 12) messages can be transmitted by

sending an ABM sentence to a PI port. The content of the message is as specified inside the
ABM sentence. The transmission may occur on a specified channel, on both or as determined
by the ABT-1103 basing upon last reception of the addressed station. The transmission is
automatically repeated by the ABT-103 if no acknowledge is received by the addresses
station. The maximum number of retries can be configures as specified in the basic
configuration section. At the end of the transmission process or if the transmission has been
rejected, an acknowledgement is returned on the same PI port through an ABK sentence. The
ABK returns the status of the transmission process specifying whether the message has been
received by the remote stations, it has been transmitted but not acknowledged or if it has not
been transmitted at all.
Broadcast binary (message 8) or safety (message 14) messages can be transmitted by

sending a BBM sentence to a PI port. The content of the message is as specified inside the
BBM sentence. The transmission may occur on a specified channel, on both or as determined
by the ABT-1103 basing upon considerations on load balance. At the end of the transmission
or if the transmission has been rejected, an acknowledgement is returned on the same PI port
through an ABK sentence. The ABK returns the status of the transmission process specifying
whether the message has been transmitted or not. No acknowledge is foreseen for broadcast
messages.
The transmission of binary and safety messages upon reception of ABM and BBM
sentences requires RATDMA to be active or available FATDMA slots reserved with DLM
sentences (at least a slot every 4 seconds should be reserved for this kind of transmissions).
Note that binary and safety messages can also be sent by using TSA+VDM or VDM as
described in the previous sections on scheduled and unscheduled transmissions. Binary
messages 25 and 26 can only be transmitted by using TSA+VDM or VDM sentences. Refer to
the section on IEC data sentences for detailed information on ABM, BBM and ABK
sentences.

5.4.2.4 Interrogations
It is possible to poll (message 15) remote stations for specified messages by sending an
AIR sentence to a PI port. The content of the message is as specified inside the AIR sentence.
The transmission may occur on a specified channel or as determined by the ABT-1103 basing
upon last reception of the addressed station(s). Up to 2 remote stations can be polled with the
same message; the first remote station can be polled for 2 different messages.
The shore station may also force the polled stations to transmit the response messages
on specified slots. This may protect the transmissions from remote stations if slots reserved by
making them transmit on slots reserved by the Base Station. In this case, this slots should be
concurrently protected from the BS own transmissions by sending a TSP sentence with
appropriate contents to the ABT-1103.
At the end of the transmission or if the transmission has been rejected, an

acknowledgement is returned on the same PI port through an ABK sentence. The ABK
returns the status of the transmission process specifying whether the message has been
transmitted or not. No acknowledge is foreseen for interrogations apart from the transmission
(or the lack of) of the polled message(s) from the remote stations.
The transmission of interrogations upon reception of AIR sentences requires RATDMA

to be active or available FATDMA slots reserved with DLM sentences (at least a slot every 4
seconds should be reserved for this kind of transmissions). Note that interrogations can also
be sent by using TSA+VDM or VDM as described in the previous sections on scheduled and
unscheduled transmissions (in the latter case, it is not allowed to specify the slots for the
responses). Refer to the section on IEC data sentences for detailed information on AIR, TSP,
and ABK sentences.
The following table lists the types of messages that can be successfully polled from
remote stations, depending on their type, as described in ITU-R M.1371-4.
Type of station Messages Remarks

Class A 3, 5
Class B-SO 18, 19
Class B-CS 18, 19, 24 Slots for the transmission of message 19 should be assigned
in the interrogation as ClassB-CS cannot otherwise broadcast
multi-slot transmissions.
SAR-aircraft 9, 24 An Interrogation for Message 24 should be answered with a
Part A and depending on its own capability with a Part B.
AtoN 21
Base Station 4, 24 An Interrogation for Message 24 should be answered with a
Part A and depending on its own capability with a Part B.
Table 1 – Interrogation of AIS stations
5.4.2.5 Assignment message

Assignment messages (message 16) can be transmitted by sending an ASN sentence to a
PI port. The content of the message is as specified inside the ASN sentence. The transmission
may occur on a specified channel or as determined by the ABT-1103 basing upon last

reception of the addressed station(s). Up to 2 remote stations can be addressed with the same
message.
Assignment messages may contain hard or soft assignments. Hard assignments are used
to command a remote station to transmit in the exact slots specified in the assignment
message. Soft assignments are used to command a remote station to transmit at the
transmission rate specified in the assignment message. In the latter case, the remote station
will choose autonomously the transmission slots, as usual. As assignments time out randomly
between 4 and 8 minutes, they need to be timely refreshed if needed. Note that the
transmission rate of Class cannot be lowered through assignment messages.
The transmission of assignments upon reception of ASN sentences requires or available

FATDMA slots reserved with DLM sentences (at least a slot every 4 seconds should be
reserved for this kind of transmissions) to be active. Note that assignments can also be sent by
using TSA+VDM or VDM as described in the previous sections on scheduled and
unscheduled transmissions (in the latter case, it is not allowed to specify hard assignments).
Refer to the section on IEC data sentences for detailed information on ASN sentences.
5.4.2.6 Addressed channel management

Addressed channel management messages (message 22) can be transmitted by sending
an ACM sentence to a PI port. The content of the message is as specified inside the ACM
sentence. The transmission may occur on a specified channel, on both or as determined by the
ABT-1103 basing upon last reception of the addressed station(s). Up to 2 remote stations can
be addressed with the same message.
Addressed channel management messages may be useful to make specified remote
stations to transmit on protected channels or revert misconfigured channel settings on to the
correct ones.
Note that AIS Stations should always use the standard AIS channels (2087 and
2088) for both receptions and transmissions, unless explicitly authorized by a competent
authority. Failing to do so may disrupt safety services managed on VHF channels, thus
impacting on the safety of navigation.
The transmission of addressed channel management messages upon reception of ACM

sentences requires RATDMA to be active or available FATDMA slots reserved with DLM
sentences (at least a slot every 4 seconds should be reserved for this kind of transmissions).
Note that addressed channel management messages can also be sent by using TSA+VDM or
VDM as described in the previous sections on scheduled and unscheduled transmissions Refer
to the section on IEC data sentences for detailed information on ACM sentences.
5.4.2.7 Other automatic transmissions

Being an independent Base Station, if the RATDMA is active or FATDMA slots
reserved with DLM sentences are available (at least a slot every 4 seconds should be reserved
for this kind of transmissions), the ABT-1103 automatically transmits a response message
when it receives the following messages from a remote station on a VDL channel:
 A binary message (message 6) addressed to its own MMSI; message 7 is
transmitted on the same AIS channel to acknowledge the remote station.
 A safety text (message 12) addressed to its own MMSI; message 13 is transmitted
on the same AIS channel to acknowledge the remote station.

 An interrogation (message 15) addressed to its own MMSI; if message 4 was
requested, it is transmitted on the same AIS channel to answer the remote station.
Other requests are not served; message 17, 20, 22 and 23 are transmitted only of
properly set through FATDMA configuration in the next occurrence of the
FATDMA plan.
 An UTC and date inquiry (message 10) addressed to its own MMSI; message 4 is
transmitted on the same AIS channel to answer the remote station.
5.4.2.8 Transmit slot prohibit

A set of slots in the TDMA frame may be protected from the ABT-1103 transmissions
by sending a TSP sentence to a PI port. If the TSP is accepted, the next occurrence of the
indicated slots will not be used by the BS own transmissions. This may be particularly useful
to protect slots reserved for other transmissions, for instance when they are allocated for the
polled transmissions of remote stations (refer to the Interrogations section for details).
When the ABT-1103 receives a TSP sentence, it immediately respond with a TSR
sentence on the same PI port which includes a status field indicating whether the prohibition
request has been accepted or not. A prohibition request may be rejected if, for instance, the
slots to be prohibited are already allocated for internal FATDMA transmissions..
Refer to the section on IEC data sentences for detailed information on TSP and TSR
sentences.

5.5 GNSS functionalities
5.5.1 Internal GPS receiver

The ABT-1103 includes an internal GPS receiver compliant to the IEC 61108-1
standard. A correct GPS antenna installation is required for a proper operation of the internal
GPS. Refer to the Technical Manual for related information.
By default, the internal GPS receiver provides the UTC synchronization required for
Base Station transmissions; the ABT-1103 may also be configured to use the position as
calculated by the internal GPS receiver for its Base Station Reports. Note that in absence of
internal UTC synchronization, the ABT-1103 can use external synchronization to local
devices (as for instance another ABT-1103) if properly configured and installed (refer to the
Technical Manual for related information). Even in absence of any local synchronization, the
ABT-1103 is capable to synchronize to UTC using the transmissions from remote stations.
The ABT-1103 can output the data collected from the internal GPS receiver to the
DGNSS OUT port (refer to the configuration section), so that the BS can be used as an EPFS
by external device. In addition, the PPS signal from the GPS receiver can be output on the
GPO0 pin, permitting the UTC synchronization of external devices. GPS data are output as
standard IEC 61162-1 sentences referenced to WGS84 datum. The sentences output by the
GPS are DTM, GBS, GGA, GLL, GNS, GSA, GSV, RMC, VTG and ZDA. Output rate is 1
Hz. Refer to the IEC 61162-1 standard for details on these sentences.
The ABT-1103 can also output time and position information to any of the PI ports
(refer to the configuration section), so that the BS can provide time and position information
to external devices. The RMC sentence can be output at 1 Hz rate on the PI ports. Moreover,
the ABT-1103 is also capable of answering to standard queries for RMC and ZDA sentences
on any PI port.
The internal GPS receiver supports Satellite-Based Augmentation Systems (SBAS), like
EGNOS and WAAS, to receive correction data (DGPS) and integrity information without the
need of external hardware to enhance the accuracy, reliability and integrity of positioning and
timing. For the same purpose, the GPS receiver can also use DGNSS corrections coming from
external DGPS reference stations through the available RTCM input port or from AIS Base
Stations through message 17.
5.5.2 DGNSS corrections

The ABT-1103 may transmit, receive, and/or use DGNSS correction messages both to
improve the quality and/or integrity of its internal GPS and that of remote targets.
DGNSS corrections may be provided both from external DGPS reference stations
through the available RTCM input port or from remote AIS Base Stations through message
17.
DGNSS corrections received from the specified RTCM input port may be forwarded to
the internal GPS receiver and/or transmitted on the VDL link. DGNSS corrections received

from remote AIS Base Stations may be forwarded to the internal GPS receiver and/or to the
DGNSS OUT port for monitoring or for enhancing external GNSS receivers.
Refer to the related configuration section for details.

5.6 Status monitoring
5.6.1 AIS Device Status

The ABT-1103 features a BIIT unit capable of detecting malfunctions internal to the
unit and forward warning messages on the PI ports whenever a relevant change in the status is
detected. Refer to the Troubleshooting section in the Technical manual for additional
description on the identification of typical issues and fixing procedures.
The ADS sentence is used to deliver a brief snapshot of the internal conditions of the
ABT-1103 to external devices or software processes. It is output every time there is a change
in the status and at regular intervals if so configured.
The ADS contains a global alarm status which is active if one or more malfunctions are
detected. The same global alarm status is reported by the BITE LEDs in the front and rear
panel of the unit (LEDs are turned on if alarms are active). Refer to the Technical manual for
additional information on these LEDs.
The ADS also includes the UTC synchronization status of the device, and the indication
of what sensors are used to gain UTC timing and position. Refer to the section on IEC data
sentences for detailed information on ADS sentence.
5.6.2 Alarms
The ABT-1103 features a BIIT unit capable of detecting malfunctions internal to the
unit and forward warning messages on the PI ports whenever a relevant change in the status is
detected.
Alarm sentences (ALR) are generated whenever a malfunctioning is detected; they are
repeated at 60 seconds intervals until the alarm condition remains active. An alarm is
identified by the alarm ID and may be linked through its ID to following TXT sentences
providing an expanded description on the cause of the defect.
Alarms can be acknowledged by means of sending an ACK sentence with the same ID
on a PI port. Only when the active condition ceases, the ALR sentence is sent one last time
with the flag active set to not valid.
The ABT-1103 can be queried in order to obtain a list of ALR sentences related to all
the active alarms. Refer to the section on IEC data sentences for detailed information on ALR
sentence.
The following table contains alarm descriptions and their consequences on the BS
behaviour.

Alarms description text ID Reaction of the ABT-1103
AIS: Tx malfunction 001 Stop transmission
AIS: Antenna VSWR exceeds limit 002 Continue operation
AIS: Rx channel A malfunction 003 Stop transmission on affected channel
AIS: Rx channel B malfunction 004 Stop transmission on affected channel
AIS: general failure 006 Stop transmission
AIS: UTC clock lost 007 Follow synchronization rules
AIS: no sensor position in use 026 Continue operation
AIS: Frame synchronisation failure 037 Stop transmission
AIS: DGNSS input failed 038 Continue operation
AIS: internal GNSS failure 052 Continue operation
Continue operation, configuration may
AIS: configuration memory error 054
be lost after a reset
Table 2 – Alarms
Figure 13 – Display of device status using BCS-1135
5.6.3 Status messages

Status messages (TXT) are generated whenever a significant change, which does not
affect the normal BS behaviour, in the ABT-1103 is detected. The ABT-1103 can be queried
in order to obtain a list of TXT sentences related to the current BS status. Refer to the section
on IEC data sentences for detailed information on TXT sentence.
5.6.4 Measurements
Internal measures performed by the ABT-1103 can be polled using the PELMMEA
proprietary sentence to obtain details on the internal hardware status of the BS. Refer to the
section on IEC data sentences for detailed information on PELMMEA sentence.

Figure 11 – Display of measures using BCS-1135

CHAPTER 6
SUPPORTED IEC 61162 SENTENCES
6.1 Presentation Interface ports
6.1.1 Introduction
Presentation Interface (PI) ports enable the Base Station to exchange data with external
devices. Usually, in a shore based AIS implementation, the Base Station will exchange data
with the Physical Shore Station (PSS) Control Unit which controls the Base Station or directly
with a Logical Shore Station (LSS). The PI can be used by external devices to acquire AIS
data from remote stations, configure the Base Station and to read status information. 1 RS-232
and 3 RS-422 serial ports are provided to physically implement the PI. Speed is configurable
up to 115200 baud.
The format of data exchanged on PI ports is as defined by the IEC 61162-1 standard. By
consequence, all the data packets are organized in sentences which have well defined
structure. The content of each sentence is defined by its type which is identified by 3
alphanumeric codes, called formatter. The ABT-1103 supports all the standard formatters
which have been defined for AIS Base Stations, allowing for easy interoperability with
external devices and software which support AIS standards. Standard sentences have the
following structure:
$<aa><ccc>,...,...,...*hh<CR><LF>
where <aa> are two alpha characters identifying the talker, <ccc> are three
alphanumeric characters identifying the formatter; after the formatter may follow several
fields of data whose number and content depends on the formatter. The „*‟ char precedes the
checksum field (2 hex digits) and the carriage return plus line feed terminators.
However, to access some features of the ABT-1103 which expand over the standard BS
functionalities, proprietary Elman sentences must be used. The Elman proprietary sentences
respect the standard IEC 61162 format for proprietary messages and have the following
structure:
$PELM<ccc>,...,...,...*hh<CR><LF>
where <ccc> identify the Elman proprietary formatter code and the other fields have the
same meaning they have in standard sentences.
Comment block extension to IEC 61162 standard is supported over all the PI ports and
can be forced as described in the basic configuration section. Refer to that section for
additional details on how CBs and their parameters are generated and processed by the ABT-
1103.

The following tables list all the supported sentences specifying if they can be accepted
as input (I) or they are autonomously output (O) by the ABT-1103 or and if they can be
queried (Q).
Sentence
I O Q Description
formatter
ABK X Addressed binary acknowledgment
ABM X Addressed binary message
ACA X X AIS channel assignment
ACK X Acknowledge alarm
ACM X Addressed channel management message
ADS X AIS device status
AGA X X Group assignment message
AIR X AIS interrogation request
ALR X X Alarm state
ASN X Assignment VDL Message
BBM X Broadcast binary message
BCE X X Extended general Base Station configuration
BCF X X General Base Station configuration
CBM X X Deprecated, it is recommended to use ECB sentence
CAB X X Control AIS Base Station
DLM X X Data link management slot allocations for Base Station
ECB X X Broadcast rates for Base Station messages
FSR X Frame summary of AIS reception
GBS X External sensor data, refer to section on sensor ports
GGA X External sensor data, refer to section on sensor ports
GLL X External sensor data, refer to section on sensor ports
GNS X External sensor data, refer to section on sensor ports
External sensor data, refer to section on sensor ports
RMC X X X
Internal position, time and date when output
SID X X Installation of a station‟s identification
SPO X X Select AIS device‟s processing and output
SSD X X Ship static data
TFR X Transmit feed-back report
TSA X Transmit slot assignment
TSP X Transmit slot prohibit
TSR X Transmit slot prohibit status report
TXT X X Text transmission
VDM X X VHF data link message
VDO X VHF data link own message
VER X Version
VSI X VDL signal information
External sensor data, refer to section on sensor ports
ZDA X X
Internal time and date when queried
Table 3 – Supported standard PI sentences

Sentence
I O Q Description
formatter
PELMAIS X X AIS Installation Settings
PELMDGC X X DGNSS service configuration
PELMMEA X X Measurements
PELMRXM X X Receiver manager settings
Table 4 – Supported proprietary PI sentences

6.1.2 Valid characters for text
Some AIS messages include character data, such as station‟s name, destination, call
sign, safety text message and more. The text is coded in 6-bit ASCII, which is limited to 64
characters, as listed in the Char columns of the Table below.
6-Bit ASCII Standard ASCII 6-Bit ASCII Standard ASCII

Char Char
Dec Hex Dec Dec Dec Hex Dec Hex
@ 0 0x00 64 0x40 Space 32 0x20 32 0x20
A 1 0x01 65 0x41 ! 33 0x21 33 0x21
B 2 0x02 66 0x42 ” 34 0x22 34 0x22
C 3 0x03 67 0x43 # 35 0x23 35 0x23
D 4 0x04 68 0x44 $ 36 0x24 36 0x24
E 5 0x05 69 0x45 % 37 0x25 37 0x25
F 6 0x06 70 0x46 & 38 0x26 38 0x26
G 7 0x07 71 0x47 ` 39 0x27 39 0x27
H 8 0x08 72 0x48 ( 40 0x28 40 0x28
I 9 0x09 73 0x49 ) 41 0x29 41 0x29
J 10 0x0A 74 0x4A * 42 0x2A 42 0x2A
K 11 0x0B 75 0x4B ? 43 0x2B 43 0x2B
L 12 0x0C 76 0x4C , 44 0x2C 44 0x2C
M 13 0x0D 77 0x4D - 45 0x2D 45 0x2D
N 14 0x0E 78 0x4E . 46 0x2E 46 0x2E
O 15 0x0F 79 0x4F / 47 0x2F 47 0x2F
P 16 0x10 80 0x50 0 48 0x30 48 0x30
Q 17 0x11 81 0x51 1 49 0x31 49 0x31
R 18 0x12 82 0x52 2 50 0x32 50 0x32
S 19 0x13 83 0x53 3 51 0x33 51 0x33
T 20 0x14 84 0x54 4 52 0x34 52 0x34
U 21 0x15 85 0x55 5 53 0x35 53 0x35
V 22 0x16 86 0x56 6 54 0x36 54 0x36
W 23 0x17 87 0x57 7 55 0x37 55 0x37
X 24 0x18 88 0x58 8 56 0x38 56 0x38
Y 25 0x19 89 0x59 9 57 0x39 57 0x39
Z 26 0x1A 90 0x5A : 58 0x3A 58 0x3A
[ 27 0x1B 91 0x5B ; 59 0x3B 59 0x3B
\ 28 0x1C 92 0x5C < 60 0x3C 60 0x3C
] 29 0x1D 93 0x5D = 61 0x3D 61 0x3D
^ 30 0x1E 94 0x5E > 62 0x3E 62 0x3E
– 31 0x1F 95 0x5F ? 63 0x3F 63 0x3F
Table 5 – Valid text characters
IEC sentences used to input these character data (like e.g. SSD, ACE) must only use the
corresponding standard ASCII characters. Note that, as some characters included in the 6-bit

ASCII table are reserved in the IEC 61162-1 standard, it is possible that the three character
sequence shall be used in some cases.
For example, to send the text:
^MAYDAY!
the field in the IEC 61162 sentence must be composed as
^5EMAYDAY^21
Refer to the IEC 61162-1 standard for additional details.
6.1.3 Standard sentences

In this section, the sentences as defined in the IEC 61162-1, 61993-2 and 62320-1
standards are described.
6.1.3.1 Queries
IEC standard sentences may be queried using the IEC standard query format:
$<aa><aa>Q,<ccc>*hh<CR><LF>
where <aa><aa> are talker identifiers of the talker and recipient respectively and <ccc>
is the formatter identifying the requested sentence. Note that the ABT-1103 default talker
identifier is “AB” but it may be configured differently. The ABT-1103 does not respond to
queries if its talker identifier is not addressed correctly.

6.1.3.2 ABK – Addressed binary acknowledgment
The ABK-sentence is generated when a transaction, initiated by reception of an ABM,
AIR, or BBM sentence, is completed or terminated.
This sentence provides information about the success or failure of a requested ABM
broadcast of either ITU-R M.1371 messages 6 or 12. The ABK process utilizes the
information received in ITU-R M.1371 messages 7 and 13. Upon reception of either a VHF
Data-link message 7 or 13, or the failure of messages 6 or 12, the AIS unit delivers the ABK
sentence to the external application.
This sentence is also used to report to the external application the AIS unit's handling of
the AIR (ITU-R M.1371 message 15) and BBM (ITU-R M.1371 messages 8 and 14)
sentences. The external application initiates an interrogation through the use of the AIR-
sentence, or a broadcast through the use of the BBM sentence. The AIS unit generates an
ABK sentence to report the outcome of the AIR or BBM broadcast process.
$--ABK,xxxxxxxxx,a,x.x,x,x*hh<CR><LF>
│ │ │ │ │
│ │ │ │ └── Type of acknowledgement (Note 5)
│ │ │ └──── Message Sequence Number (Note 4)
│ │ └── ITU-R M.1371 message ID (Note 3)
│ └──── AIS channel of reception (Note 2)
└─ MMSI of the addressed destination AIS unit (Note 1)
NOTE 1 1 Identifies the distant addressed AIS unit involved with the acknowledgement. If more than one MMSI
are being addressed (ITU-R M.1371 message 15), the MMSI of the first distant AIS unit, identified in the
message, is the MMSI reported here. When the Message ID is a general broadcast (ITU-R M.1371
messages 8 or 14), this field is null.
NOTE 2 Indication of VDL channel upon which Message ID 7 or 13 acknowledgement was received. An "A"
indicates reception on channel A. A "B" indicates reception on channel B. If not available, field is null.
NOTE 3 This indicates to the external application the type of ITU-R M.1371 message that this ABK sentence is
addressing. Also see the message IDs listed in NOTE 4.
NOTE 4 The message sequence number, together with the ITU-R M.1371 message ID and MMSI of the
addressed AIS unit, uniquely identifies a previously received ABM, AIR, or BBM sentence. Generation of
an ABK sentence makes a sequential message identifier available for reuse. The ITU-R M.1371 Message
ID is used to determine the origin of the message sequence identifier number. The following table lists the
origins by message ID:
ITU-R M.1371 Message ID Message Sequence Number source

6 sequential message identifier from ABM-sentence, IEC 61162-1
7 addressed AIS unit's message 7, sequence number, ITU-R M.1371
8 sequential message identifier from BBM-sentence, IEC 61162-1
12 sequential message identifier from ABM-sentence, IEC 61162-1
13 addressed AIS unit's message 13, sequence number, ITU-R M.1371
14 sequential message identifier from BBM-sentence, IEC 61162-1
15 no source, field shall be null
NOTE 5 Acknowledgements provided are:
0 = message (6 or 12) successfully received by the addressed AIS unit,
1 = message (6 or 12) was broadcast, but no acknowledgement by the distant addressed AIS unit,
2 = message could not be broadcast,
3 = requested broadcast of message (8, 14, or 15) has been successfully completed,
4 = late reception of a message 7 or 13 acknowledgement "addressed to own-ship" MMSI – identified by;
destination MMSI, acknowledgement source MMSI, message sequence identifier, and message type. Late
reception means that the AIS unit did not have an acknowledgement process active for the
acknowledgement that was received.

6.1.3.3 ABM – Addressed binary message
This sentence supports ITU-R M.1371 messages 6 and 12. It provides an external
application with a means to exchange data using an AIS. The message data is defined by the
application only – not the AIS. This message offers great flexibility for implementing system
functions that use the AIS like a communications device. After receiving this sentence, the
AIS initiates a radio broadcast on the VHF Data Link (VDL) of either message 6 or 12. The
AIS will make up to four broadcasts of the message. The actual number will depend on the
reception of an acknowledgement from the addressed "destination" AIS. The default time
between retries is 4 s. Retries will not be attempted more frequently than 4 s. Retries stop
when the appropriate acknowledgement (See ITU-R M.1371 messages 7 and 13.) is received.
The AIS will make up to 4 broadcasts, original broadcast plus three retires. This process could
take 32 s to complete.
The success or failure of the reception of this broadcast by the intended AIS unit is
confirmed through the use of the "Addressed and binary Broadcast Acknowledgement
(ABK)" sentence formatter, and the processes that support the generation of an ABK-
sentence. The AIS is also limited in the amount of encapsulated data that can be sent. If the
length of the message would exceed five slots the AIS will return an ABK-sentence with an
acknowledgement of "2" – message could not be broadcast.
!--ABM,x,x,x,xxxxxxxxx,x,x.x,s--s,x*hh<CR><LF>
│ │ │ │ │ │ │ │
│ │ │ │ │ │ │ └── Number of fill-bits, 0 to 5 (Note 6)
│ │ │ │ │ │ └──── Encapsulated data (Note 5)
│ │ │ │ │ └── ITU-R M.1371 message ID (6 or 12)
│ │ │ │ └── AIS channel for broadcast of the radio message (Note 4)
│ │ │ └────── The MMSI of destination AIS unit for the ITU-R M.1371 (Note 3)
│ │ └──── Sequential Message identifier, 0 to 3 (Note 2)
│ └──────── Sentence number (Note 1)
└──── Total number of sentences needed to transfer the message, 1 to 9 (Note 1)
NOTE 1 The total number of sentences required to transfer the binary message data to the AIS unit. The first field
specifies the total number of sentences used for a message, minimum value 1. The second field identifies
the order of this sentence in the message, minimum value 1. All sentences contain the same number of
fields. Successive sentences may use null fields for fields that have not changed, such as fields 4, 5, and 6.
NOTE 2 This sequential message identifier serves two purposes. It is both an IEC 61162-1 "sequential message
identifier field," and it is the "sequence number" utilised by the ITU-R M.1371 in message types 6 and 12.
The range of this field is restricted by ITU-R M.1371 to the range of 0 to 3. This sequential message
identifier and the destination MMSI uniquely identifies a message. The sequential message identifier may
be reused after the "ABK" acknowledgement for that sequence number is provided by the destination AIS
unit. (See the ABK-sentence formatter.
NOTE 3 The MMSI of the AIS unit which is the destination of the message.
NOTE 4 The AIS channel that shall be used for the broadcast: 0 = no broadcast channel preference, 1 = Broadcast
on AIS channel A, 2 = Broadcast on AIS channel B, 3 = Broadcast two copies of the message – one copy
sent on channel A and another copy sent on channel B.
NOTE 5 This is the content of the "binary data" parameter for ITU-R M.1371 message 6, or the "Safety related
Text" parameter for message 12. The first sentence may contain up to 47 "6-bit" symbols (288 bits).
Following sentences may contain up to 59 valid "6-bit" symbols (360 bits), if fields 4, 5, and 6 are
unchanged from the first sentence and set to null. The actual number of "6-bit" symbols in a sentence must
be adjusted so that the total number of characters in a sentence does not exceed the "82-character" limit.
NOTE 6 To encapsulate, the number of binary bits must be a multiple of six. If it is not, one to five "fill bits" are
added. This parameter indicates the number of bits that were added to the last 6-bit coded character. This
value shall be set to zero when no "fill bits" have been added. This cannot be a null field.

6.1.3.4 ACA – AIS channel assignment
This sentence can be used to provide the ABT-1103 with the information needed to
broadcast a “channel assignment Message 22”. Upon receiving this sentence, the ABT-1103
will store the information and use it in scheduled broadcasts of message 22 (if any).
The ABT-1103 can store and transmit up to 8 different sets of channel management data
at the same time. If a new set is provided to the ABT-1103 through an ACA sentence, channel
management settings already in memory will be deleted if their area overlaps the area of the
new set. If memory is full or the ACA sentence has the In-Use Flag set to 0, the new set will
not be stored. Thus, ACA sentences with In-Use Flag set to 0 may be used to delete existing
channel settings with overlapping areas.
When the ABT-1103 is queried for ACA sentence, it responds by outputting an ACA
sentence for each of the region with associated channel management settings.
$--ACA,x,llll.ll,a,yyyyy.yy,a,llll.ll,a,yyyyy.yy,a,x,xxxx,x,xxxx,x,x,x,a,x,hhmmss.ss*hh
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └── (Note 9)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └── (Note 8)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └── (Note 7)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └── (Note 6)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ └── (Note 5)
│ │ │ │ │ │ │ │ │ │ │ │ │ └── Channel B BW (N. 4)
│ │ │ │ │ │ │ │ │ │ │ │ └── Channel B (Note 3)
│ │ │ │ │ │ │ │ │ │ │ └── Channel A BW(Note 4)
│ │ │ │ │ │ │ │ │ │ └── Channel A (Note 3)
│ │ │ │ │ │ │ │ │ └── Transition Zone Size (Note 2)
│ │ │ │ │ │ │ └─────┴─ Region SW corner latitude – N/S
│ │ │ │ │ └────┴── Region SW corner latitude – N/S
│ │ │ └─────┴─ Region NE corner longitude – E/W
│ └─────┴─ Region NE corner latitude – N/S
└── Sequence Number (Note 1)
NOTE 1 Sequence number 0 to 9. Ignored by the ABT-1103. It is automatically incremented by the ABT-1103
when ACA sentences are output as a response to a query; thus the Sequence number will vary from zero to
the number of in use channel management settings.
NOTE 2 Value of 1 nautical mile to a value of 8 nautical miles (with a resolution of 1 nautical mile).
NOTE 3 VHF channel number, see ITU-R M.1084, Annex 4
NOTE 4 Value of 0, bandwidth is specified by channel number, see ITU-R M.1084, Annex 4
Value of 1, bandwidth is 12,5 kHz.
NOTE 5 Tx/Rx mode control
Value of 0, transmit on channels A and B, receive on channels A and B
Value of 1, transmit on channel A, receive on channels A and B
Value of 2, transmit on channel B, receive on channels A and B
Value of 3, do not transmit, receive on channels A and B
Value of 4, do not transmit, receive on channel A
Value of 5, do not transmit, receive on channel B
NOTE 6 Power level control
Value of 0, high power
Value of 1, low power
NOTE 7 Information source
This field should be left null when the sentence is sent to the ABT-1103. Always „C‟ (ACA sentence)
when the sentence is sent by the ABT-1103.
NOTE 8 In-Use Flag
This field should be left null or set to 1 when the sentence is sent to the ABT-1103 in order to provide new
settings: it should be set to zero to delete existing settings. Always 1 when the sentence is sent by the
ABT-1103.
NOTE 9 Time of In-Use Flag change
This field is not used by the ABT-1103 and should be left null.

6.1.3.5 ACK – Acknowledge alarm
Acknowledge device alarm. This sentence is used to acknowledge an alarm condition
reported by a device.
$--ACK,xxx*hh<CR><LF>
│
└─ Local alarm number – identification number of alarm source

6.1.3.6 ACM – Addressed channel management message
transmit an addressed VDL Message 22. This contains settings that are transmitted to one or
two specified AIS station(s). Upon receiving this sentence, the ABT-1103 will prepare and
make the appropriate transmission (See ITU-R M.1371 Message 22).
$--ACM,xxxxxxxxx,xxxxxxxxx,xxxx,x,xxxx,x,x,x,x,x*hh<CR><LF>
│ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ └── Transition Zone (Note 7)
│ │ │ │ │ │ │ │ └──── Broadcast channel for Base Station
│ │ │ │ │ │ │ │ (Note 6)
│ │ │ │ │ │ │ └── Power level control (Note 5)
│ │ │ │ │ │ └──── TX/RX mode control (Note 4)
│ │ │ │ │ └── Channel B bandwidth (Note 3)
│ │ │ │ └────── Channel B (Note 2)
│ │ │ └──── Channel A bandwidth (Note 3)
│ │ └──────── Channel A (Note 2)
│ └──── MMSI of the second addressed AIS unit (Note 1)
└────────────── MMSI of the first addressed AIS unit (Note 1)
NOTE 1 Identifies the distant addressed AIS unit(s) intended to receive the ITU-R M.1371 Message 22. The first
MMSI field (field 1) identifies the first AIS unit. The second MMSI field (field 2) identifies the second
AIS unit, and may be set to null if only one AIS unit is being addressed.
NOTE 2 VHF channel number, see ITU-R M.1084, Annex 4
NOTE 3 0 = bandwidth is specified by channel number, see ITU-R M.1084, Annex 4
1 = bandwidth is 12,5 kHz
NOTE 4 0 = transmit on channels A and B, receive on channels A and B
1 = transmit on channel A, receive on channels A and B
2 = transmit on channel B, receive on channels A and B
NOTE 5 0 = high power
1 = low power
NOTE 6 The field identifies the channel that the Base Station should use to broadcast the ITU-R M.1371 Message
22. (This field cannot be a “null” field)
0 = No broadcast channel preference
1 = broadcast on AIS channel A
2 = broadcast on AIS channel B
3 = broadcast on both AIS channel A and AIS channel B
NOTE 7 Value of 1 nautical mile to a value of 8 nautical miles (with a resolution of 1 nautical mile)

6.1.3.7 ADS – AIS device status
The ABT-1103 uses this sentence to output, autonomously and periodically, the current
AIS station status condition. The interval for automatic output of this sentence is defined
using the BCE sentence. The ADS sentence is output at the defined interval or when there is a
change in status. Null data fields are not allowed. The ADS sentence is invalid if it contains a
null data field.
$--ADS,c--c,HHMMSS.SS,x,x,x,x*hh<CR><LF>
│ │ │ │ │ │
│ │ │ │ │ └── UTC timing source (Note 5)
│ │ │ │ └──── Position source (Note 4)
│ │ │ └──── Synchronization State (Note 3)
│ │ └────── Alarm status (Note 2)
│ └──── Time (hour, minute, second) of status report
└─────────── Unique identifier (Note 1)
NOTE 1 The unique identifier is used for system level identification of a station with a maximum of 15 alphanumeric
characters (see the SID sentence formatter).
NOTE 2 A = active
V = not active
NOTE 3 0 = UTC direct
1 = UTC indirect
2 = station synchronised to a Base Station
3 = station is semaphore
4 = no VDL synchronisation reference
NOTE 4 I = internal
E = external
S = surveyed
N = none
NOTE 5 E = external
I = internal
N = none

6.1.3.8 AGA – Group assignment message
broadcast a “group assignment Message 23”. Upon receiving this sentence, the ABT-1103
will store the information and use it in scheduled broadcasts of message 23 (if any).
$--AGA,c--c,x.x,xxx,llll.ll,a,yyyyy.yy,a,llll.ll,a,yyyyy.yy,a,xx,x,xx*hh<CR><LF>
│ │ │ │ │ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ │ │ │ │ └── Quiet time
│ │ │ │ │ │ │ │ │ │ │ │ │ (Note 5)
│ │ │ │ │ │ │ │ │ │ │ │ └── Tx/Rx mode (Note 4)
│ │ │ │ │ │ │ │ │ │ │ └───── Reporting interval
│ │ │ │ │ │ │ │ │ │ │ (Note 3)
│ │ │ │ │ │ │ │ │ └─────┴── Region SW corner
│ │ │ │ │ │ │ │ │ longitude – E/W
│ │ │ │ │ │ │ └────┴───────────── Region SW corner
│ │ │ │ │ │ │ latitude – N/S
│ │ │ │ │ └─────┴── Region NE corner longitude – E/W
│ │ │ └────┴───────────── Region NE corner latitude – N/S
│ │ └──── Type of ship and cargo type (see ITU-R M.1371)
│ └──────── Type of mobile stations (Note 2)
└───────────── Unique identifier (Note 1)
NOTE 1 The unique identifier is used for system level identification of a station with a maximum of 15
alphanumeric characters and identifies the Base Station to which the information in this AGA sentence is
intended (see SID sentence formatter). This data field should match the Base Station‟s unique identifier.
The ABT-1103 will ignore this sentence when this data field does not match the Base Station‟s unique
identifier.
NOTE 2 The field identifies the group of mobile stations for the group assignment.
0 = all types of mobiles, except Class A (default)
1 = reserved for future use
2 = all types of Class B mobiles
3 = SAR airborne mobiles
4 = A to N stations
5 = Class B“CS” stations
6 = Inland waterway stations
7-9 = for regional use
10-15 = for future use
NOTE 3 The field identifies the reporting interval as defined in Table 17 of IEC 62287.
0 = as defined in autonomous mode
1 = 10 min
2 = 6 min
3 = 3 min
4 = 1 min
5 = 30 s
6 = 15 s
7 = 10 s
8=5s
9 = next shorter interval
10 = next longer interval
11 = 2 s
12-15 = reserved for future use
NOTE 4 0 = transmit on channels A and B, receive on channels A and B (default)
1 = transmit on channel A, receive on channels A and B
2 = transmit on channel B, receive on channels A and B
3 = reserved for future use
NOTE 5 0 = no quiet time (default)
1-15 = quiet time 1min to 15 min

6.1.3.9 AIR – AIS interrogation request
This sentence supports ITU-R M.1371, Message 15. It provides an external application
with the means to initiate requests for specific ITU-R M.1371 messages, from distant mobile
or Base Station, AIS units. A single sentence can be used to request up to two messages from
one AIS unit and one message from a second AIS unit, or up to three messages from one AIS
unit. The message types that can be requested are limited. The complete list of messages that
may be requested can be found within the Message 15 description in ITU-R M.1371.
Improper requests may be ignored. The external application initiates the interrogation.
The external application is responsible for assessing the success or failure of the interrogation.
After receiving this sentence, the AIS unit initiates a radio broadcast (on the VHF Data Link)
of a Message 15 - Interrogation. The success or failure of the interrogation broadcast is
determined by the application using the combined reception of the ABK-sentence and VDM
sentences provided by the AIS unit. After receiving this AIR-sentence, the AIS unit shall take
no more than 4 s to broadcast the Message 15, and the addressed distant unit(s) shall take no
more than another 4 s to respond - a total of 8 s.
Message station-2 reply slot (see Note 6) ───────┐
Second message station-1 reply slot (see Note 6)─┐ │
First message station-1 reply slot (see Note 6) ┐ │ │
Channel of interrogation (see Note 5) ────┐ │ │ │
│ │ │ │
$--AIR,xxxxxxxxx,x.x,x,x.x,x,xxxxxxxxx,x.x,x,a,x.x,x.x,x.x*hh<CR><LF>
│ │ │ │ │ │ │ │
│ │ │ │ │ │ │ └────────── Message sub-section (see Note 3)
│ │ │ │ │ │ └────── Message number requested from station-2
│ │ │ │ │ │ (see Note 2)
│ │ │ │ │ └────── MMSI of interrogated station-2 (see Note 4)
│ │ │ │ └───────── Message sub-section (see Note 3)
│ │ │ └─ Second message number requested from station-1 (see Note 2)
│ │ └── Message sub-section (see Note 3)
│ └── First message number requested from station-1(see Note 2)
└──── MMSI of interrogated station-1 (see Note 1)
NOTE 1 Identifies the first distant AIS unit being interrogated. A single AIR sentence can be used to request two
message numbers from the first AIS unit.
NOTE 2 The following are examples of messages that may be requested from a distant mobile AIS unit. See
ITU-R M.1371, Message 15 description for the actual message numbers.
Message 3 (Position report)
Message 5 (Ship static and voyage related data, see additional information in Note 3)
Message 9 (Standard SAR aircraft position report)
Message 18 (Standard Class B equipment position report)
Message 19 (Extended Class B equipment position report)
Message 21 (Aids-to-navigation report)
Message 24 (Static-data report)
Examples of messages that may be requested from a distant AIS Base Station include:
Message 4 (Base Station report)
Message 24 (Static-data report)
NOTE 3 This field is used to request a message that has been further sub-divided into alternative data structures.
When requesting a message with alternative data structures, this message sub-section field must be
provided, so that the correct sub-division of the message data is provided. If the message structure is not
sub-divided into different structures, this field should be null.
NOTE 4 This identifies the second distant AIS unit being interrogated. Only one message may be requested from
the second AIS unit. The MMSI of the second AIS unit may be the same MMSI as the first AIS unit.
NOTE 5 A = Channel A
B = Channel B
NOTE 6 Start slot number of interrogation reply, 0 to 2249. Null if interrogation reply slot not being assigned. AIS
mobile stations should ignore this data field.

6.1.3.10 ALR – Alarm state
Local alarm condition and status. This sentence is used to report an alarm condition on a
device and its current state of acknowledgement. One or more TXT sentences may follow the
ALR to add details on the alarm cause; in this case the local alarm number and the text
identifier fields will contain the same value.
$--ALR,hhmmss.ss,xxx,A,A,c--c*hh<CR><LF>
│ │ │ │ │
│ │ │ │ └─ Alarm’s description text
│ │ │ └─ Alarm’s acknowledge state A = acknowledged, V = unacknowledged
│ │ └─ Alarm condition (A = threshold exceeded, V = not exceeded)
│ └─ Local alarm number – identification number of alarm source
└─ Time of alarm condition change, UTC

6.1.3.11 ASN – Assignment VDL Message 16
This sentence is used to provide the ABT-1103 with the information needed to
broadcast an “assignment VDL Message 16”. This contains settings that are broadcast to the
specified AIS station(s). Upon receiving this information, the ABT-1103 will prepare and
make the appropriate broadcast (see ITU-R M.1371, Message ID 16).
$--ASN,xxxxxxxxx,x.x,x.x,x,xxxxxxxxx,x.x,x.x,x,x*hh<CR><LF>
│ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ └─── Broadcast channel for Base Station
│ │ │ │ │ │ │ │ (Note 5)
│ │ │ │ │ │ │ └─ Increment for AIS unit 2 (Note 4)
│ │ │ │ │ │ └─ Start slot assignment for AIS unit 2
│ │ │ │ │ │ (Note 3)
│ │ │ │ │ └───── Soft assigned reporting rate for AIS unit 2
│ │ │ │ │ (Note 2)
│ │ │ │ └──────────── MMSI of the addressed AIS unit 2 (Note 1)
│ │ │ └──── Increment for AIS unit 1(Note 4)
│ │ └─────── Start slot assignment for AIS unit 1 (Note 3)
│ └─────────── Soft assigned reporting rate for AIS unit 1 (Note 2)
└────────────────── MMSI of the addressed AIS unit 1 (Note 1)
NOTE 1 Identifies the distant addressed AIS unit(s) for the VDL assignment. The first set of four fields apply to a
single AIS unit, while the second set of four fields (fields 5 – 8) apply to a second AIS unit. When only one
AIS unit‟s assignment schedule is being provided, the second set of four fields (fields 5 – 8) may be set to
null.
NOTE 2 This field corresponds to the ITU-R M.1371 Message 16 Offset field. The Base Station will only use this
field if the “increment for AIS” field (fields 4 and 8 of this sentence) for the same AIS unit is set to zero;
the value in this field is interpreted as the number of transmissions in 10 minutes. The range of values for
this field consists of multiples of 20, between and including 20 to 600. Values that are less then 600 but
are not multiples of 20 will be interpreted as the next higher multiple of 20. Values above 600 will be
interpreted as 600. This field should be set to null when the “increment for AIS” field (fields 4 and 8 of
this sentence) for the same AIS unit is set to a non-zero value.
NOTE 3 When the increment field is non-zero, this field is the start slot for assigned reports. The Base Station
should provide the proper Message 16 off-set at time of broadcast to accomplish this assignment. The
Base Station calculates the Message 16 “off-set” as the difference of this start slot and the slot of the
broadcast. The range of values for this field consists 0 to 2249 in units of slots. This field should be set to
null when the “increment for AIS” field (fields 4 and 8 of this sentence) for the same AIS unit is set to a
zero value.
NOTE 4 This field identifies the increment parameter in units of slots for the associated values of this field. The
range of values is from 0 to 6. Note that a value of zero does not provide an increment, Note 2 above. This
field shall not be set to null, unless the entire four field set for this AIS unit is not provided, because the
Base Station may invoke two distinctly different assignment methods based on a zero or non-zero value.
The values and their meanings are:
0 = Reporting rate is based upon the “soft assigned reporting rate for same AIS unit” (fields 2 and 6)
1 = 1125 slots
2 = 375 slots
3 = 225 slots
4 = 125 slots
5 = 75 slots
6 = 45 slots
NOTE 5 The field identifies the channel that the Base Station should use to broadcast the ITU-R M.1371 Message
16. A null value in this field indicates no change from previous received value when this sentence is sent
to a Base Station and indicates unknown when this sentence is received from a Base Station. The values
and their meanings for this are:
0 = no broadcast channel preference
1 = broadcast on AIS channel A
2 = broadcast on AIS channel B

6.1.3.12 BBM – Broadcast binary message
This sentence supports generation of an ITU-R M.1371 Binary Broadcast Message
(message 8) or Safety Related Broadcast Message (message 14). It provides an external
application with a means to broadcast data, as defined by the application only – not the AIS.
This message offers great flexibility for implementing system functions that use the AIS
like a digital broadcast device. After receiving this sentence, the AIS initiates a VHF
broadcast of either message 8 or 14 within 4 s. (Also, see the ABK-sentence.)
The success or failure of the broadcast confirmed through the use of the "Addressed and
binary Broadcast Acknowledgement (ABK)" sentence formatter, and the processes that
support the generation of an ABK-sentence. The AIS is limited in the amount of encapsulated
data that can be sent in each slot. If the length of the message would exceed five slots, the AIS
will return an ABK-sentence with an acknowledgement of "2" message could not be
broadcast.
!--BBM,x,x,x,x,x.x,s--s,x*hh<CR><LF>
│ │ │ │ │ │ │
│ │ │ │ │ │ └─ Number of fill-bits (Note 5)
│ │ │ │ │ └─ Encapsulated data (Note 4)
│ │ │ │ └─ ITU-R M.1371 message ID, 8 or 14
│ │ │ └─ AIS channel for broadcast of the radio message (Note 3)
│ │ └─ Sequential message identifier (Note 2)
│ └─ Sentence number (Note 1)
└─ Total number of sentences needed to transfer the message, 1 to 9 (Note 1)
NOTE 1 The total number of IEC 61162-1 sentences needed to transfer the contents of the binary message to the
AIS. The first field specifies the total number of sentences used for a message, minimum value 1. The
second field identifies the order of this sentence in the message, minimum value 1. All sentences contain
the same number of fields. Successive sentences may use null fields for fields that do not change – such as
fields 4 and 5.
NOTE 2 The Sequential Message Identifier provides a message identification number from 0 to 9 that is
sequentially assigned as needed. Note that this is only a sequential message identifier. This is used
differently than the "Message sequence identifier" of an ABM sentence. This identifier is incremented for
each new multisentence message. The count resets to 0, after 9 is used. For the contents of a message 8 or
14 requiring multiple sentences, each sentence of the message contains the same Sequential Message
Identification number. This number is used to link the separate sentences containing portions of the same
encapsulated data. This allows for the possibility that other sentences might be interleaved with the
message sentences that, taken collectively, contain a single message 8 or 14. This number also links a
future ABK-sentence acknowledgement to the appropriate BBM-sentence. (See ABK, NOTE 4.)
NOTE 3 The AIS channel that shall be used for the broadcast: 0 = no broadcast channel preference, 1 = Broadcast
on AIS channel A, 2 = Broadcast on AIS channel B, 3 = Broadcast two copies of the message – one on
channel A and another sent on channel B.
NOTE 4 This is the content of the "binary data" parameter for ITU-R M.1371 message 8 or the "Safety related
Text" parameter for message 14. The first sentence may contain up to 58 "6-bit" symbols (348 bits). The
following sentences may contain up to 60 "6-bit" symbols (360 bits), if fields 4 and 5 are unchanged from
the first sentence and set to null. The actual number of "6-bit" symbols in a sentence must be adjusted so
that the total number of characters in a sentence does not exceed the "82-character" limit.

6.1.3.13 BCE – Extended general Base Station configuration
This sentence and the BCF sentence are used to configure the ABT-1103 parameters
when it is initially installed, and later in order to make changes to the way it operates. This
sentence is also used to monitor the UTC synchronisation source being used by the Base
Station.
$--BCE,c--c,a,a,x.x,x*hh<CR><LF>
│ │ │ │ │
│ │ │ │ └──────────── Comment block control (Note 5)
│ │ │ └───────────── ADS interval (seconds) (Note 4)
│ │ └────────────── UTC source selection (Note 3)
│ └─────────────── RATDMA control (Note 2)
└──────────────── Unique identifier of the Base Station (Note 1)
alphanumeric characters and identifies the Base Station to which the information in this BCE sentence is
identifier.
NOTE 2 Controls the Base Station‟s ability to use RATDMA access to the VDL:
0 = off (Base Station cannot use RATDMA access to VDL)
1 = on (Base Station may use RATDMA access to VDL)
NOTE 3 Controls the UTC synchronisation source used by the Base Station:
E = external UTC source
I = internal UTC source
X = external UTC source with fallback to internal UTC source
Y = internal UTC source with fallback to external UTC source, if available
NOTE 4 The recommended interval is 60 s. This data field sets the interval between the output of “AIS device
status” sentences (see ADS sentence.). If the value of this data field is zero or negative, the ADS sentences
should not be provided. When the data field is zero or negative, the ADS will still be provided when there
is a change in the status.
NOTE 5 Comment blocks:
0 = off (not required). Comment blocks are not generated by default and not required. If comment blocks
are received from PI ports are processed and used also in the responses, if any.
1 = on (required). Comment blocks are always generated and required. If comment blocks are not received
from PI ports, linked sentences are discarded.

6.1.3.14 BCF – General Base Station configuration
This sentence and the BCE sentence are used to configure the static ABT-1103
parameters when it is initially installed, and later in order to make changes to the way it
operates. Dynamic parameters (e.g. UTC and position of a moving Base Station) are input in a
different way. This sentence supports system administration of the AIS Base Station
operation.
$--BCF,xxxxxxxxx,x,llll.ll,a,yyyyy.yy,a,x,xxxx,xxxx,xxxx,xxxx,x,x,x,x,aa*hh<CR><LF>
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ Base Station
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └─ Talker ID
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ (Note 7)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ └─ Message repeat
│ │ │ │ │ │ │ │ │ │ │ │ │ │ indicator
│ │ │ │ │ │ │ │ │ │ │ │ │ └─ VDL message retries
│ │ │ │ │ │ │ │ │ │ │ │ └─ Power level channel B
│ │ │ │ │ │ │ │ │ │ │ │ (Note 6)
│ │ │ │ │ │ │ │ │ │ │ └─── Power level channel A
│ │ │ │ │ │ │ │ │ │ │ (Note 6)
│ │ │ │ │ │ │ │ │ │ └─ Tx channel B (Note 5)
│ │ │ │ │ │ │ │ │ └────── Tx channel A (Note 5)
│ │ │ │ │ │ │ │ └─────────── Rx channel B (Note 5)
│ │ │ │ │ │ │ └──────────────── Rx channel A (Note 5)
│ │ │ │ │ │ └── Position accuracy (Note 4)
│ │ │ │ └─────┴──── Longitude – E/W (Note 3)
│ │ └────┴─────────────── Latitude – N/S (Note 3)
│ └───────────────────────── Position source (Note 2)
└─────── MMSI of the Base Station (Note 1)
NOTE 1 This data field is the MMSI of the Base Station. This data field is not used when the sentence is provided
to the ABT-1103. The attached “comment block” parameter-code “d:” is used to test if this sentence is
intended for this Base Station. The Base Station will ignore this sentence if the parameter-code “d:” value
in the attached comment block does not match the internal unique identifier (also, see the SID sentence).
NOTE 2 Identifies the source of the position:
0 = surveyed position (should always be used for Fixed AIS Base Station)
1 = internal EPFS in use
2 = external EPFS in use
3 = internal EPFS in use with automatic fall back to surveyed position
4 = internal EPFS in use with automatic fall back to external EPFS upon failure of internal EPFS
5 = external EPFS in use with automatic fall back to surveyed position
6 = external EPFS in use with automatic fall back to internal position source upon failure of external
position source
Position sources 1, 2, 4 or 6 use automatic fall back to invalid position (181 degrees Longitude and 91
degrees Latitude). When external EPFS is used (position sources 2, 4, 5 and 6), type of electronic position
fixing device is provided by talker ID of the EPFS to be used in Message 4.
NOTE 3 Surveyed position of the Base Station. When a surveyed position is entered using the BCF sentence, the
„Type of electronic position fixing device‟ parameter broadcast by the Base Station in the VDL message 4
should be „7‟ (surveyed). When a surveyed position is provided as an automatic fall back (reference BCF
Note 2; 3 – internal EPFS in use with automatic fall back to surveyed position), the „Type of electronic
position fixing device‟ parameter broadcast by the Base Station in the VDL message 4 should be „7‟
(surveyed).
NOTE 4 0 = low >10m
1 = high <10m; differential mode of DGNSS
NOTE 5 VHF channel number, see ITU-R M.1084, Annex 4.
NOTE 6 0 = high power (Nominal 12,5 W)
1 = low power (Nominal 2 W)
2 to 9 = not used
NOTE 7 The Base Station talker identifier should be set to the primary design of the equipment:
AB = AIS Base Station
AL = limited Base Station

AS = simplex repeater station
AD = duplex repeater station
AR = receiving stations
The ABT-1103 has AB as default talker identifier. Talker identifiers starting with the letter „P‟ (capital p)
are not accepted by the ABT-1103.
6.1.3.15 CAB – Control AIS Base Station

This sentence is used to turn on or off the transmission of Channels A and B on the
ABT-1103 and may also command a restart of the Base Station. This sentence supports
system administration of the AIS Base Station operation.
$--CAB,x,x,x,x*hh<CR><LF>
│ │ │ └─ Reset (Note 3)
│ │ └─── Restart (Note 2)
│ └── Channel B transmission (Note 1)
└──── Channel A transmission (Note 1)
NOTE 1 The field commands the Base Station to turn on or off transmissions on the selected channel (fields 1 and
2). There are two valid values for this field:
0 = off
1 = on
NOTE 2 This field commands the Base Station to restart operations to last known configuration. The value of “1”
indicates a restart. If a restart is not being indicated, this field is null.
NOTE 3 This field commands the Base Station to reset all configuration information to undefined, with exception
of receive only on AIS1 and AIS2. The value of “1” indicates a reset. If a reset is not being indicated,
this field is null.

6.1.3.16 CBM – Broadcast rates for Base Station messages
This sentence assigns the schedule of slots that will be used to broadcast the specified
Message 4, 17, 20, and 22. It provides the Starting Slot (SS) and interval between the slots
(SI) used for consecutive transmissions for the message.
The ABT-1103 will apply the information provided by this sentence to autonomously
and continuously transmit the VDL message indicated until revised by a new CBM sentence.
The ABT-1103, upon receipt of a CBM query for this information, will generate sentences for
all Message types (4, 17, 20, 22, and 23) providing the current broadcast schedule. New CBM
assignments will override existing CBM assignments. DLM assignments shall be made before
CBM assignments.
Note: CBM sentence use is deprecated; this sentence is supported only for legacy
reasons. ECB sentences should be used to configure the broadcast rates. The CBM
sentence do not support broadcast schedules based upon a 6 min FATDMA epoch;
customised message 4 schedules and message 23 schedules.
$--CBM,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x,x.x *hh<CR><LF>
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ │ │ │ │ │ └─ Msg 22 ch B SI (Nt3)
│ │ │ │ │ │ │ │ │ │ │ │ │ └─ Msg 22 ch B SS (Note 2)
│ │ │ │ │ │ │ │ │ │ │ │ └─ Msg 20 ch B SI (Note 3)
│ │ │ │ │ │ │ │ │ │ │ └─ Msg 20 ch B SS (Note 2)
│ │ │ │ │ │ │ │ │ │ └─ Msg 17 ch B NS (Note 4)
│ │ │ │ │ │ │ │ │ └─ Msg 17 ch B SI (Note 3)
│ │ │ │ │ │ │ │ └─ Msg 17 ch B SS (Note 2)
│ │ │ │ │ │ │ └─ Msg 22 ch A SS (Note 3)
│ │ │ │ │ │ └─ Msg 22 ch A SS (Note 2)
│ │ │ │ │ └─ Msg 20 ch A SI (Note 3)
│ │ │ │ └─ Msg 20 ch A SS (Note 2)
│ │ │ └─ Msg 17 ch A NS (Note 4)
│ │ └─ Msg 17 ch A SI (Note 3)
│ └─ Msg 17 ch A SS (Note 2)
└─ Msg 4 broadcast SS (Note 1)
NOTE 1 For Message 4, starting slot (SS) ranging from –1 to 374 should be used. The first broadcast will occur on
channel A, the second on channel B, and the following broadcasts alternate between the channels A and B
through the end of the frame. The increment may vary; see ITU-R M.1371 (standard broadcast interval is
10 seconds corresponding to a 20 seconds SI for each channel). A value of –1 discontinues broadcasts of
message 4 when the CBM sentence is sent to the AIS equipment, and indicates that Message 4 has been
turned off if the CBM sentence is received from the Base Station. A null field indicates no change to the
current start slot setting when sent to the Base Station, and indicates that the start slot has not been set
when the CBM sentence is received from the Base Station.
NOTE 2 For Messages 17, 20, or 22, starting slot (SS) ranging from –1 to 2249 should be used. A value of –1
discontinues broadcasts of message 4 when the CBM sentence is sent to the AIS equipment, and indicates
that Message 4 has been turned off if the CBM sentence is received from the Base Station. A null field
indicates no change to the current start slot setting when sent to the Base Station, and indicates that the
start slot has not been set when the CBM sentence is received from the Base Station.
NOTE 3 Slot interval (SI) ranging from 0 to 1125 in slots between broadcasts of ITU-R M.1371 Messages 17, 20,
or 22 on channels “A” or “B”. Interval selection for Message 17 should consider the timing needs for both
DGNSS corrections and integrity warnings. 5 s or less is recommended. A value of 0 indicates only one
broadcast per frame. A null field indicates no change to the current slot interval setting when sent to the
ABT-1103, and indicates that the slot interval has not been set, i.e. is unavailable, when the CBM sentence
is received from the Base Station. The SI should satisfy the formula; 2 250 mod SI. = 0 to ensure the slot
schedule is periodic from frame to frame. When the interval is not a permissible interval as defined above
the CBM sentence shall be rejected.
NOTE 4 For Message 17, the Number of Slots (NS) may range from 1 to 4 consecutive slots. A maximum of 3
slots is recommended for each DGNSS service. A null field indicates no change to the number of
consecutive slots reserved when sent to the ABT-1103, and indicates that the number of consecutive slots
has not been set, i.e. is unavailable, when the CBM sentence is received from the Base Station.

6.1.3.17 DLM – Data link management slot allocations for Base Station
This sentence provides the ABT-1103 with the slot allocations to be reserved for
FATDMA Base Station broadcasts. This sentence provides the Base Station with the
information necessary to broadcast an ITU-R M.1371 Message 20 Data link management
message, which informs mobile AIS units of the reserved FATDMA slots. Upon receipt of
this sentence the Base Station will reserve the provided FATDMA slot allocations within its
frame map, and will be ready to generate Message 20 when instructed to do so via the ECB
sentence. This is the information that is broadcast on the VDL using Message 20 (Reference
ITU-R M.1371, also see the ECB sentence).
The shore station is responsible for filtering out slot reservation conflicts that may exist.
The ABT-1103 will not detect conflicts that may exist on slot reservations. These conflicts in
the shore station
network should be resolved separately from entering the data. The ABT-1103, upon
receipt of a query for this sentence, will generate a response to the requestor consisting of
multiple DLM sentences containing all the FATDMA reserved slots.
$--DLM,x,a,a,x.x,x,x,x.x,a,x.x,x,x,x.x,a,x.x,x,x,x.x,a,x.x,x,x,x.x*hh<CR><LF>
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └─ Increment for res. 4
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ (Note 7)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └─ Time out for reserv. 4
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ (Note 6)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └─ Number of slots for res. 4
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ (Note 5)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └─ Start slot for reservation 4
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ (Note 4)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └─ Ownership for reserv. 4 (Note 3)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └─ Increment for reserv. 3 (Note 7)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └─ Time out for reservation 3 (Note 6)
│ │ │ │ │ │ │ │ │ │ │ │ │ │ └─ Number of slots for reserv. 3 (Note 5)
│ │ │ │ │ │ │ │ │ │ │ │ │ └─Start slot for reservation 3 (Note 4)
│ │ │ │ │ │ │ │ │ │ │ │ └─ Ownership for reservation 3 (Note 3)
│ │ │ │ │ │ │ │ │ │ │ └─ Increment for reservation 2 (Note 7)
│ │ │ │ │ │ │ │ │ │ └─ Time out for reservation 2 (Note 6)
│ │ │ │ │ │ │ │ │ └─ Number of slots for reservation 2 (Note 5)
│ │ │ │ │ │ │ │ └─ Start slot for reservation 2 (Note 4)
│ │ │ │ │ │ │ └─ Ownership for reservation 2 (Note 3)
│ │ │ │ │ │ └─ Increment for reservation 1 (Note 7)
│ │ │ │ │ └─ Time out for reservation 1 (Note 6)
│ │ │ │ └─ Number of slots for reservation 1 (Note 5)
│ │ │ └─ Start slot for reservation 1 (Note 4)
│ │ └─ Ownership for reservation 1 (Note 3)
│ └─ AIS channel (Note 2)
└─ Sequence number (0 – 9) (Note 1)
NOTE 1 The sequence number is used to identify and address each DLM sentence record stored in the Base
Station. The sequence number is also used to associate the DLM field data with each of the AIS VDL
“Message 20‟s” that are broadcast by the Base Station.
NOTE 2 The AIS channel that the FATDMA reservation information is to be applied to. The character “A”
indicates Channel A and “B” indicates Channel B. This cannot be a null field when sent to the Base
Station. When received from a Base Station, this field may be null, indicating that no FATDMA slots have
been reserved on either Channel A or Channel B.
NOTE 3 This field identifies the ownership of the reservation. Possible values are as follows:
L = Local ownership: the ABT-1103, upon receiving this sentence, owns and may utilize these FATDMA
slots and will broadcast these FATDMA slot reservations.
R = Remote ownership: remote AIS Stations own and may use these FATDMA slots; the ABT-1103 will
broadcast these FATDMA slot reservations.
C = Clear the reservation: the ABT-1103 will clear this reservation from its frame map; when this field is
set to “C”, then the following four fields should be set to null, and will be ignored if set otherwise.

NOTE 4 Starting slot ranging from 0 to 2249. A null field indicates no change to the staring slot for this FATDMA
reservation. When received from the ABT-1103, a null field indicates that the start slot has not been set.
NOTE 5 The number ranging from 1 to 5 of consecutive slots reserved for FATDMA broadcasts. A null field
indicates no change to the number of consecutive slots reserved when sent to the ABT-1103, and indicates
that the number of consecutive slots has not been set, i.e. is unavailable, when the DLM sentence
is received from the ABT-1103.
NOTE 6 The time out in minutes ranging from 0 to 7 for the slots reserved for FATDMA broadcasts. A null field
indicates no change to the number of consecutive slots reserved when sent to the ABT-1103, and indicates
that the number of consecutive slots has not been set, i.e. is unavailable, when the DLM sentence is
received from the ABT-1103.
NOTE 7 Slot increment ranging from 0 to 1125 in slots. A value of 0 indicates only one broadcast is scheduled in
the frame. A null field indicates no change to the current slot increment setting when sent to the ABT-
1103, and indicates that the slot increment has not been set, i.e. is unavailable, when the DLM sentence is
received from the ABT-1103. When the increment is not “0”, the following formula should apply: 2250
mod increment = 0.

6.1.3.18 ECB – Broadcast rates for Base Station messages
This sentence assigns the schedule of slots that will be used to broadcast the specified
Message 4, 17, 20, 22, and 23. It provides the start slot and interval between the slots used for
consecutive transmissions for the message. The interval span supports creation of broadcast
schedules based upon a 6 min FATDMA epoch. The ABT-1103 will apply the information
provided by this sentence to autonomously and continuously transmit the VDL message
indicated until revised by a new ECB sentence. The ABT-1103, upon receipt of an ECB query
for this information, will generate sentences for all Message types (4, 17, 20, 22, and 23)
providing the current broadcast schedule. Even unscheduled messages will be reported. New
ECB assignments will override existing ECB assignments. DLM assignments shall be made
before ECB assignments.
The interval span in this sentence supports FATDMA planning where 6 min epochs are
used. When planning the FATDMA use of VDL slots, time must be organized into 6 min
periods identified using FATDMA “epoch numbers” (0 to 9). The start of a FATDMA epoch
is correlated with the beginning of the hour. A FATDMA epoch starts with the first second of
the first minute, and ends with the end of second 59 of the sixth minute of the epoch. The
FATDMA epoch number of each FATDMA epoch in 1 h is correlated to an absolute start
minute within the hour (FATDMA epoch number × 6). For example, FATDMA epoch “0” is
minute 0 through 5, and FATDMA epoch “9” is minute 54 through 59.
$--ECB,c--c,x,x.x,x,x,x,x.x,x,x,x*hh<CR><LF>
│ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ └─ Number of slots Channel B (Note 5)
│ │ │ │ │ │ │ │ └─ Slot interval Channel B (Note 4)
│ │ │ │ │ │ │ └─ Start slot Channel B (Notes 2 and 3)
│ │ │ │ │ │ └── UTC minute for Channel B start slot
│ │ │ │ │ └── Number of slots Channel A (Note 5)
│ │ │ │ └── Slot interval channel A (Note 4)
│ │ │ └── Start slot Channel A (Notes 2 and 3)
│ │ └─── UTC minute for Channel A start slot
│ └──── Message type
└──── Unique identifier (Note 1)
alphanumeric characters and identifies the Base Station to which the information in this ECB sentence is
identifier.
NOTE 2 For Message 4, starting slot ranging from –1 to 749 should be used. The broadcasts should alternate
between the channels A and B. The increment may vary; see ITU-R M.1371 for details. A value of –1
discontinues broadcasts of Message 4 when the ECB sentence is sent to the ABT-1103, and indicates that
Message 4 has been turned off if the ECB sentence is received from the Base Station. A null field
start slot has not been set when the ECB sentence is received from the Base Station.
NOTE 3 For Messages 17, 20, 22, or 23, starting slot ranging from –1 to 2249 should be used. A value of –1
discontinues broadcasts of the message when the ECB sentence is sent to the ABT-1103, and indicates
that no message has been broadcast if the ECB sentence is received from the Base Station. A null field
start slot has not been set, i.e. is unavailable, when the ECB sentence is received from the Base Station.
NOTE 4 Slot interval ranging from 0 to 13500 in slots (epoch of 6 min), between broadcasts of ITU-R M.1371
Messages 17, 20, 22, or 23 on channels “A” or “B”. Interval selection for Message 17 should consider the
timing needs for both DGNSS corrections and integrity warnings. 5 s or less is recommended. A value of
0 indicates only one broadcast. A null field indicates no change to the current slot interval setting when
sent to the ABT-1103, and indicates that the slot interval has not been set, i.e. is unavailable, when the
ECB sentence is received from the Base Station.
When the value is 1 to 2 249, the interval (int.) should satisfy the formula; 2 250 mod int. = 0 to ensure

the slot schedule is periodic from frame to frame. When the interval is greater than 2 249 the only
permissible intervals are 2 250, 4 500, 6 750 and 13 500. When the interval is not a permissible interval as
defined above the ECB sentence shall be rejected.
NOTE 5 For messages other than Message 17, this field is null. For Message 17, the number may range from 1 to 4
consecutive slots. A maximum of 3 slots is recommended for each DGNSS service. A null field indicates
no change to the number of consecutive slots reserved when sent to the ABT-1103, and indicates that the
number of consecutive slots has not been set, i.e. is unavailable, when the ECB sentence is received from
the Base Station.

6.1.3.19 FSR – Frame summary of AIS reception
The ABT-1103 may be configured to generate the FSR sentence to provide the
following statistics for the AIS channel specified by the user: the average noise level and a
summary of slot use during the previous frame and expected slot use for the current frame.
The sentence is output once at the start of the current frame (see diagram below). Data fields 4
through 10 are enabled using data fields in the SPO sentence. If a data field is not enabled, the
data field should contain the IEC 61162-1 “null field” notation for no information.
$--FSR,c--c,HHMMSS.SS,a,x.x,x.x,x.x,x.x,x.x,x.x,x.x*hh<CR><LF>
│ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ └─ Number of slots with received signal
│ │ │ │ │ │ │ │ │ strength (Note 9)
│ │ │ │ │ │ │ │ └─ Average noise level during previous
│ │ │ │ │ │ │ │ frame (dBm) (Note 5)
│ │ │ │ │ │ │ └─ Total slots reserved by this station for
│ │ │ │ │ │ │ current frame (Note 7)
│ │ │ │ │ │ └─ Total external slot reservations for current
│ │ │ │ │ │ frame (Note 6)
│ │ │ │ │ └─ Number of slots with CRC failures in the previous
│ │ │ │ │ frame (Note 8)
│ │ │ │ └─ Total slots occupied by this station’s transmissions in
│ │ │ │ previous frame
│ │ │ └─ Total slots occupied by valid messages received in the
│ │ │ previous frame (Note 4)
│ │ └─ Channel being reported (Note 3)
│ └─ Hour, minute, and second of report generation (Note 2)
└─ Unique identifier (Note 1)
alphanumeric characters and identifies the Base Station to which the information in this FSR sentence is
identifier.
NOTE 2 The time (UTC) when this sentence is assembled. This sentence is assembled at the beginning of a frame.
B = Channel B
NOTE 4 Exclude slots occupied by this station‟s transmissions.
NOTE 5 Measured value is always negative.
0 = requested by data field setting in SPO-sentence, but not available.
NOTE 6 Total external slot reservations, including FATDMA reservations. Exclude slots reserved by this station.
The calculation of the current frame‟s slot reservations should be done during the first slot. The total
should not include additional reservations made for slots in the current frame by messages received during
the current frame.
NOTE 7 The total number of reservations for the current frame. The total should not include reservations made in
the current frame.
NOTE 8 Number of slots occupied by received signals in the previous frame. This count includes all slots where a
AIS signal is detected but fails the Cyclic Redundancy Check (CRC).
NOTE 9 Number of slots with received signal strength (at least 10 dB) above the average noise level during
previous frame.

6.1.3.20 RMC – Recommended minimum specific GNSS data
The RMC sentence can be queried to obtain position, course and speed over ground and
UTC time and date of position fix from the ABT-1103. The ABT-1103 can also be configured
to output the RMC sentence once per second on any PI port. Some or all the RMC fields may
be null if the information is not available. ABT-1103 may acquire the position from manual
input, the internal GPS receiver, external sensors or, if the other options fail, from remote AIS
targets.
$--RMC,hhmmss.ss,A,llll.ll,a,yyyyy.yy,a,x.x,x.x,xxxxxx,x.x,a,a*hh<CR><LF>
│ │ │ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ │ │ └─ Mode indicator (Note 1,2)
│ │ │ │ │ │ │ │ │ └──┴─ Not supported, always null
│ │ │ │ │ │ │ │ └─ Date: ddmmyy
│ │ │ │ │ │ │ └─ Course over ground, degrees true
│ │ │ │ │ │ └─ Speed over ground, knots
│ │ │ │ └───┴─ Longitude, E/W
│ │ └───┴─ Latitude, N/S
│ └─ Status (see Note 1)
└─ UTC hour, minute, second, and milliseconds of position fix
NOTE 1 The positioning system status field is supplemented by the Mode indicator field, see Note 2. The status
field is set to V = Invalid for all values of indicator mode except for A= Autonomous and D = Differential.
The positioning system mode indicator and status fields are never null fields.
NOTE 2 Positioning system Mode Indicator:
A = Autonomous. Satellite system used in non-differential mode in position fix;
D = Differential. Satellite system used in differential mode in position fix;
E = Estimated (dead reckoning) mode;
F = Float RTK. Satellite system used in real time kinematic mode with floating integers;
M = Manual input mode;
N = No fix. Satellite system not used in position fix, or fix not valid;
P = Precise. Satellite system used in precision mode. Precision mode is defined as: no deliberate
degradation (such as selective availability) and higher resolution code (P-code) is used to compute
position fix. P is also used for satellite system used in multi-frequency, SBAS or Precise Point Positioning
(PPP) mode;
R = Real time kinematic. Satellite system used in RTK mode with fixed integers;
S = Simulator mode.

6.1.3.21 SID – Installation of a station‟s identification
This sentence is used to configure the ABT-1103 unique identifier and MMSI. The
unique identifier is used for system level identification of a station with a maximum of 15
alphanumeric characters. The base station‟s current unique identifier is required by the SID
sentence to ensure that the station is the correct recipient of the sentence. It shall be the same
value as returned in the VER sentence from the base station. If the “current unique identifier”
field does not match the station‟s unique identifier, then the station will ignore the sentence.
The MMSI is not required to change the unique identifier. The current unique identifier and
the current MMSI are required by the SID sentence to change the MMSI. If the current MMSI
field does not match the station‟s MMSI, then the station will ignore the sentence. Proper
installation of a station‟s identification may be confirmed using a query for a VER and BCF
sentences.
$--SID,c--c,c--c,xxxxxxxxx,xxxxxxxxx*hh<CR><LF>
│ │ │ │
│ │ │ └─ New MMSI (Notes 3 and 4)
│ │ └─ Current MMSI (Note 3)
│ └─ New unique identifier (Notes 1 and 2)
└─ Current unique identifier (Note 1)
alphanumeric characters and identifies the Base Station to which the information in this SID sentence is
identifier.
NOTE 2 The new unique identifier field is used to change the unique identifier of the ABT-1103. The new unique
identifier shall become current when the SID acknowledgement sentence is output on the PI. If not used,
then this field shall be a null field.
NOTE 3 This is a nine-digit number. If needed to maintain nine digits, leading zeros are required. Co-located
transmitting devices may have the same MMSI. If not used, then these fields shall be a null field.
NOTE 4 The new MMSI will become current when the SID acknowledgement sentence is output on the PI.

6.1.3.22 SPO – Select AIS device‟s processing and output
This sentence is used to configure the content and output for measurements made on
selected channels during operation of the ABT-1103. When a data field(s) is selected, the
corresponding VSI and/or FSR sentence(s) will be output following the rules for those
sentence formatters.
$--SPO,c--c,a,x,x,x,x,x,x,x,x,x.x,x,x,x*hh<CR><LF>
│ │ │ │ │ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ │ │ │ │ └─ Provide FSR sentence after each frame (Note 5)
│ │ │ │ │ │ │ │ │ │ │ │ └─ Provide VSI sentence with each VDO sentence
│ │ │ │ │ │ │ │ │ │ │ │ output (Note 5)
│ │ │ │ │ │ │ │ │ │ │ └─ Provide VSI sentence with each VDM sentence output
│ │ │ │ │ │ │ │ │ │ │ output (Note 5)
│ │ │ │ │ │ │ │ │ │ └─ Received signal strength
│ │ │ │ │ │ │ │ │ │ (Note 4, see FSR data field 10)
│ │ │ │ │ │ │ │ │ └─ Average noise level (Note 4, see FSR data field 9)
│ │ │ │ │ │ │ │ └─ Forecast channel load (Note 4, see FSR data fields 7 and 8)
│ │ │ │ │ │ │ └─ Number of messages with bad CRC
│ │ │ │ │ │ │ (Note 4, see FSR data field 6)
│ │ │ │ │ │ └─ Previous frame channel load
│ │ │ │ │ │ (Note 4, see FSR data fields 4 and 5)
│ │ │ │ │ └─ Signal to noise ratio (Note 3, see VSI data field 6)
│ │ │ │ └─ Time of message arrival (Note 3, see VSI data field 3)
│ │ │ └─ First slot number of each received message (Note 3)
│ │ │ (Note 3, see VSI data field 4)
│ │ └─ Received signal strength of each VDL message
│ │ (Note 3, see VSI data field 5)
│ └─ Channel selection (Note 2)
alphanumeric characters and identifies the Base Station to which the information in this SPO sentence is
identifier.
B = Channel B
E = every channel
NOTE 3 0 = no output
1 = continuous output
2 = output next frame only
NOTE 4 0 = no output
1 = output once per frame
2 = output next frame only
NOTE 5 0 = off, disabled
1 = on, enabled

6.1.3.23 SSD - Ship static data
This sentence is used to enter the name parameter for the ABT-1103. All the other
parameters are ignored and should be left null. The name, if set, is used in transmissions of
message 24A.
$--SSD,c--c,c--c,xxx,xxx,xx,xx,c,aa*hh<CR><LF>
│
└─ Station Name, 1 to 20 characters (Note 1)
NOTE 1 The characters that can be used in the name are listed in the ITU-R M.1371, table 14 (6-bit ASCII). Some
of the acceptable characters in this 6-bit ASCII table are reserved characters under IEC 61162-1. They must
be represented using the "^-method" (See IEC 61162-1, section 5.1.3.). A null field indicates that the
previously entered name is unchanged.
The string of characters "@@@@@@@@@@@@@@@@@@@@" is used to indicate that the ship's
name is not available. If name is not available, periodic transmission of message 24A is discontinued.

6.1.3.24 TFR – Transmit feed-back report
The TFR sentence is automatically generated by the ABT-1103 to report to the Physical
Shore Station the scheduled slot use and status of a requested transmission. Several data fields
are copied from the TSA and VDM sentences responsible for this TFR. They are provided to
assist in linking this Base Station response to the responsible TSA+VDM sentence(s). After
receiving associated TSA and VDM sentences, the ABT-1103 responds with a TFR sentence
that provides status information about the requested transmission. After receiving a VDM
sentence without an associated TSA sentence (as when requested transmissions are not
assigned to a specific starting slot), the ABT-1103 responds with a TFR sentence to report the
scheduled channel, assigned time, assigned slot number, and status of the requested
transmission.
$--TFR,x,x,a,c—c,HHMM,x.x,HHMM,x.x,x,x,x.x*hh<CR><LF>
│ │ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ │ └─ Status (Note 11)
│ │ │ │ │ │ │ │ │ └─ Transmission priority (Note 10)
│ │ │ │ │ │ │ │ └─ Number of consecutive time slots for message
│ │ │ │ │ │ │ │ (Note 9)
│ │ │ │ │ │ │ └─ Start slot number assigned to requested transmission
│ │ │ │ │ │ │ (Note 8)
│ │ │ │ │ │ └─ UTC hour and minute assigned to requested transmission
│ │ │ │ │ │ (Note 7)
│ │ │ │ │ └─ Start slot number of requested transmission (Note 6)
│ │ │ │ └─ UTC hour and minute of requested transmission (Note 5)
│ │ │ └─ Unique identifier (Note 4)
│ │ └─ Channel requested for message being reported (Note 3)
│ └─ Sequential message identifier used with message being reported (Note 2)
└─ Total number of sentences used to transfer the message being reported (Note 1)
NOTE 1 Exact copy of the first data field of the VDM sentence to which this TFR is responding – “total number of
sentences needed to transfer the message.”
NOTE 2 Exact copy of the third data field of the VDM sentence to which this TFR is responding – “sequential
message identifier”.
NOTE 3 Actual channel scheduled for the requested transmission. It is the exact copy of the fourth data field of the
VDM sentence to which this TFR is responding – “AIS channel.”
NOTE 4 The unique identifier is used for system level identification of the station with a maximum of 15
alphanumeric characters (see the SID sentence formatter).
NOTE 5 UTC hour and minute scheduled for the requested transmission. This is the exact copy of the fourth data
field of the TSA sentence to which this TFR is responding – “ UTC hour and minute of requested
transmission.” This is null when there is no TSA sentence with the VDM sentence.
NOTE 6 This is the exact copy of the fifth data field of the TSA sentence to which this TFR is responding – “start
slot number of requested transmission.” This is null when there is no TSA sentence with the VDM
sentence.
NOTE 7 UTC hour and minute assigned for the requested transmission. This is determined by the Base Station for a
received VDM sentence when no associated TSA sentence is received. This is null when associated TSA
and VDM sentences are received.
NOTE 8 Start slot number assigned for requested transmission. This is determined by the Base Station for a received
VDM sentence when no associated TSA sentence is received. This is null when associated TSA and VDM
sentences are received.
NOTE 9 Actual number of slots that are scheduled for the transmission of the requested message. This takes into
consideration bit stuffing.
NOTE 10 Priority is either that requested in the TSA sentence or that assigned by the Base Station.
1 = high priority
2 = low priority (default value)
NOTE 11 0 = successfully scheduled for transmission
1 = successfully scheduled for transmission by overriding an internal message with a lower priority (valid
for independent base station only)

2 = successfully scheduled for a transmission time greater than 12 h from the present time
3 = not scheduled because requested transmission exceeded available memory
4 = successfully removed from schedule
5 = not scheduled because requested transmission conflicted with slot(s) requested by an internal Base
Station process that has the same or higher priority (valid for independent base station only)
6 = not scheduled because requested message type is not allowed by the Base Station configuration (valid
for independent base station only)
7 = not scheduled because requested message conflict to prohibit slots (valid for independent base station
only)
8 = configuration error (see linked configuration sentence). Linked to this error should be the appropriate
sentence containing the current configuration values for all fields
9 = not scheduled because requested transmission is for a disabled channel
10 = not scheduled because of invalid TSA content (e.g. invalid slot number)
NOTE The VDO+VSI will provide verification of the transmission itself.

6.1.3.25 TSA – Transmit slot assignment
This sentence can be used by the Physical Shore Station to command the ABT-1103 to
transmit the VDL message encapsulated in the associated VDM sentence(s) beginning in the
specified time slot. The TSA+VDM sentence combination is used for individual message
transmissions only. The TSA sentence should appear first, and the VDM sentence(s) second.
A long VDL message may require the use of several VDM sentences.
NOTE Normally, when a received VDL message fits into one VDM sentence, the third
VDM data field, sequential message identifier, is a null field. However, when a VDM
sentence is used to command the ABT-1103 to transmit a VDL message, the sequential
message identifier must always contains a value – even when the message fits into one VDM
sentence. The sequential message identifier in the TSA sentence is identical to the sequential
message identifier in the associated VDM sentence(s). The “comment block” parameter-code
“xGy:” can also be used to “group” TSA and VDM sentences.
$--TSA,c—c,x,a,HHMM,x.x,x*hh<CR><LF>
│ │ │ │ │ │
│ │ │ │ │ └─ Priority (Note 4)
│ │ │ │ └─ Start slot number of requested transmission
│ │ │ └─ UTC hour and minute of requested transmission
│ │ └─ Channel selection (Note 3)
│ └─ Sequential message identifier (Note 2)
alphanumeric characters and identifies the Base Station to which the information in this TSA sentence is
identifier.
NOTE 2 The sequential message identifier provides a message identification number from 0 to 9 that is
sequentially assigned and is incremented for each new message. The count should reset to 0 after 9 is
used. Each sentence of a message must contain the same sequential message identification number – the
TSA sentence and each of the VDM sentences that are needed. Note that linking a TSA sentence with a
VDM sentence(s) results in the need for the VDM sentence(s) to have the same Sequential message
identifier as in the TSA sentence – even when only one VDM sentence is used.
NOTE 3 This should be the same channel as indicated in the following VDM sentence.
A = Channel A
B = Channel B
NOTE 4 0 = cancel the transmission identified by the channel selection, UTC hour and minute, and start slot
Number.
1 = high priority, the rquired transmission can overrule the internal Base Station schedule. It will not
interfere with multi-slot transmissions already in progress.
2 = low priority, the required transmission will be executed if slot is available. This is the default priority.

6.1.3.26 TSP – Transmit slot prohibit
This sentence is used to prohibit the ABT-1103 from transmitting in the specified slots.
The AIS station receiving this sentence should not use the next occurrence of the indicated
slots. This sentence is designed to be used to protect interrogation responses from interference
from Base Station transmissions.
$--TSP,c--c,xx,a,HHMMSS.SS,x.x,x.x,x.x,x.x,x.x,x.x,x.x*hh<CR><LF>
│ │ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ │ └─ Consecutive time slots in third
│ │ │ │ │ │ │ │ │ │ block (Note 7)
│ │ │ │ │ │ │ │ │ └─ Slot offset of third block of
│ │ │ │ │ │ │ │ │ consecutive time slots (Note 6)
│ │ │ │ │ │ │ │ └─ Consecutive time slots in second block
│ │ │ │ │ │ │ │ (Note 7)
│ │ │ │ │ │ │ └─ Slot offset of second block of consecutive
│ │ │ │ │ │ │ time slots (Note 6)
│ │ │ │ │ │ └─ Consecutive time slots in first block (Note 7)
│ │ │ │ │ └─ Slot offset of first block of consecutive time slots
│ │ │ │ │ (Note 6)
│ │ │ │ └─ Reference slot (Note 5)
│ │ │ └─ UTC hour, minute, and second of requested blocking of slot use
│ │ │ (Note 4)
│ └─ Sequential identifier (Note 2)
alphanumeric characters and identifies the Base Station to which the information in this TSP sentence is
identifier.
NOTE 2 The sequential identifier provides an identification number from 0 to 99 that is sequentially assigned and is
incremented for each new TSP sentence. The count resets to 0 after 99 is used. This sequential identifier
should be used to identify the Base Station‟s response to a slot prohibit status report (TSR).
B = Channel B
NOTE 4 This is for record keeping. It contains the hour, minute, and second of this request.
NOTE 5 This is the slot from which the following slot offsets are referenced. This is frequently the slot assigned to a
message 15 interrogation.
NOTE 6 Slot offset of the first slot in the block of slots to be blocked from use by the Base Station. 0 indicates no
prohibited slots.
NOTE 7 Total number of consecutive slots to be blocked from use by the Base Station. The first slot of the block is
also part of the count. Therefore, the minimum value is 1.
0 = no prohibited slots
1-5 = number of prohibited slots

6.1.3.27 TSR – Transmit slot prohibit status report
This sentence is automatically generated by the ABT-1103 to report the results of a TSP
sentence.
$--TSR,c--c,xx,a,HHMMSS.SS,x*hh<CR><LF>
│ │ │ │ │
│ │ │ │ └─ Status of prohibit request (Note 5)
│ │ │ └─ UTC hour, minute, and second of requested blocking of slot use
│ │ │ (Note 4)
│ └─ Sequential identifier (Note 2)
NOTE 2 Exact copy of the second data field (sequential identifier) provided in the TSP sentence to which this TSR
is responding. It is an identification number from 0 to 99 that is sequentially assigned and is incremented
for each new TSP sentence. The count resets to 0 after 99 is used. This sequential identifier should be used
to identify the Base Station‟s TSR transmit slot prohibit status report.
NOTE 3 Exact copy of the third data field (channel selection) provided in the TSP sentence to which this TSR is
responding.
A = Channel A
B = Channel B
NOTE 4 Exact copy of the fourth data field (hour, minute, and second) provided in the TSP sentence to which this
TSR is responding.
NOTE 5 0 = successfully blocked prohibited slots
1 = not successful because of internal reservation
2 = not successful because action is not allowed by the Base Station configuration
3 = not successful because action is for a disabled channel
4 = not successful because of invalid TSP content (e.g. invalid slot number)

6.1.3.28 TXT – Text transmission
TXT are used for the transmission of short text messages related to status changes and
alarm descriptions (see also ALR sentence). Longer text messages may be transmitted by
using multiple sentences.
$--TXT,xx,xx,xx,c--c*hh<CR><LF>
│ │ │ │
│ │ │ └─ Text message (see note 3)
│ │ └─ Text identifier (see note 2)
│ └─ Message number (see note 1), 01 to 99
└─ Total number of messages (see note 1), 01 to 99
NOTE 1 Text messages may consist of the transmission of multiple messages all containing identical field formats.
The first field specifies the total number of messages, minimum value = 1. The second field identifies the
order of this message (message number), minimum value = 1. For efficiency, it is recommended that null
fields be used in the additional sentences, otherwise data is unchanged from the first sentence.
NOTE 2 The text identifier is a number, 01 to 99, used to identify different text messages.
NOTE 3 ASCII characters, and code delimiters.

6.1.3.29 VDM – VHF data link message
This sentence is used to transfer the entire contents of a received AIS message packet,
as defined in ITU-R M.1371 and as received on the VHF Data Link (VDL), using the "6-bit"
field type. The structure provides for the transfer of long binary messages by using multiple
sentences.
!--VDM,x,x,x,a,s--s,x*hh<CR><LF>
│ │ │ │ │ │
│ │ │ │ │ └─ Number of fill-bits, 0 to 5 (see note 5)
│ │ │ │ └─ Encapsulated ITU-R M.1371 radio message (see note 4)
│ │ │ └─ AIS Channel 3, "A" or "B" (see note 3)
│ │ └─ Sequential message identifier (see note 2)
│ └─ Sentence number, 1 to 9 (see note 1)
└─ Total number of sentences needed to transfer the message, 1 to 9 (see note 1)
NOTE 1 The length of an ITU-R M.1371 message may be long and may require the use of multiple sentences. The
first field specifies the total number of sentences used for a message, minimum value 1. The second field
identifies the order of this sentence in the message, minimum value 1. These cannot be null fields.
NOTE 2 The Sequential message identifier provides a message identification number from 0 to 9 that is sequentially
assigned and is incremented for each new multi-sentence message. The count resets to 0 after 9 is used. For
a message requiring multiple sentences, each sentence of the message contains the same sequential
message identification number. It is used to identify the sentences containing portions of the same message.
This allows for the possibility that other sentences might be interleaved with the message sentences that,
taken collectively, contain a single message. This field shall be a null field when messages fit into one
sentence.
NOTE 3 The AIS message reception channel is indicated as either "A" or "B." This channel indication is relative to
the operating conditions of the AIS when the packet is received. This field shall be null when the channel
identification is not provided. The VHF channel numbers for channels "A" and "B" are obtained by using
an ACA-sentence "query" of the AIS
NOTE 4 The maximum string length of encapsulation is limited such that the total number of sentence characters
does not exceed 82. This field supports a maximum of 60 valid characters for a message transferred using
multiple sentences, and 61 valid characters for a message using a single sentence.
value shall be set to zero when no "fill bits" have been added. This cannot be a null field

6.1.3.30 VDO – VHF data link own message
This sentence is used to provide the information assembled for broadcast by the AIS. It
uses the six-bit field type for encapsulation. The sentence uses the same structure as the VDM
sentence formatter.
!--VDO,x,x,x,a,s--s,x*hh<CR><LF>
│ │ │ │ │ │
│ │ │ │ │ └─ Number of fill-bits, 0 to 5 (see note 5)
│ │ │ │ └─ Encapsulated ITU-R M.1371 radio message (see note 4)
│ │ │ └─ AIS Channel 3, "A" or "B" (see note 3)
│ │ └─ Sequential message identifier (see note 2)
│ └─ Sentence number, 1 to 9 (see note 1)
└─ Total number of sentences needed to transfer the message, 1 to 9 (see note 1)
NOTE 1 The length of an ITU-R M.1371 message may be long and may require the use of multiple sentences. The
first field specifies the total number of sentences used for a message, minimum value 1. The second field
identifies the order of this sentence in the message, minimum value 1. These cannot be null fields.
NOTE 2 The Sequential message identifier provides a message identification number from 0 to 9 that is sequentially
assigned and is incremented for each new multi-sentence message. The count resets to 0 after 9 is used. For
a message requiring multiple sentences, each sentence of the message contains the same sequential
message identification number. It is used to identify the sentences containing portions of the same message.
This allows for the possibility that other sentences might be interleaved with the message sentences that,
taken collectively, contain a single message. This field shall be a null field when messages fit into one
sentence.
NOTE 3 This is the channel used to broadcast the AIS message. The AIS channel field, set to either "A" or "B",
indicates that the message was broadcast. If the message is not broadcast, the "AIS Channel" field shall be
null. The VHF channel numbers for channels "A" and "B" are obtained by using an ACA-sentence "query"
of the AIS.
NOTE 4 The maximum string length of encapsulation is limited such that the total number of sentence characters
does not exceed 82. This field supports a maximum of 60 valid characters for a message transferred using
multiple sentences, and 61 valid characters for a message using a single sentence.

6.1.3.31 VER – Version
This sentence is used to provide identification and version information about the ABT-
1103. This information is obtained by the use of a query sentence. All data fields, except the
unique identifier, are manufactured into the station. The unique identifier may be changed
using the SID sentence.
$--VER,x,x,aa,aaa,c--c,c--c,c--c,c--c,c--c*hh<CR><LF>
│ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ └─ Hardware revision (32 character maximum)
│ │ │ │ │ │ │ │ (Note 3)
│ │ │ │ │ │ │ └─ Software revision (32 character maximum) (Note 3)
│ │ │ │ │ │ └─ Model code (product code) (32 character maximum)
│ │ │ │ │ │ (Note 3)
│ │ │ │ │ └─ Manufacturer serial number (32 character maximum)
│ │ │ │ │ (Notes 3 and 4)
│ │ │ │ └─ Unique identifier (15 characters) (Note 2)
│ │ │ └─ Vendor ID (7 character maximum) (Note 5)
│ │ └─ Device type (2 characters) (Note 1)
│ └─ Sentence number (Note 7)
└─ Total number of sentences (Note 6)
NOTE 1 This device type is defined by IEC 61162-1, Table 4 – talker identifier mnemonics. It is set into the
equipment based upon the primary purpose of the station and remains constant even if the user defined
talker identifier is changed.
AB = AIS Base Station
AL = limited Base Station
AS = simplex repeater station
AD = duplex repeater station
AR = receiving station
AI = mobile class A or B (see IEC 61993-2 and IEC 62287)
AN = aids to navigation
NOTE 3 The data field length may be 32 characters maximum. When large character lengths are used and the 80
character sentence limit would be exceeded for a single sentence, a series of successive VER sentences are
used to avoid the problem (using fields 2 and 3 to ensure the correct sequence). Null fields are used for data
fields contained in other sentences of the series. Every VER sentence contains the unique identifier.
NOTE 4 The manufacturer‟s serial number for the unit.
NOTE 5 Vendor identification of the unit as defined by the manufacturer.
NOTE 6 The total number of sentences required to transmit the information.
NOTE 7 Sentence number refers to the sequence number of the sentence within the total number of sentences.

6.1.3.32 VSI – VDL signal information
This sentence provides optional measurement information associated with a received
AIS message. This sentence is also used to identify the first slot of an AIS message
transmission (linked to a VDO sentence). It is output in combination with either a VDM or
VDO sentence. Content of the VSI is defined using the SPO sentence.
$--VSI,c--c,x,HHMMSS.SS,x.x,x.x,x.x*hh<CR><LF>
│ │ │ │ │ │
│ │ │ │ │ └─ Signal to noise ratio (dB) (Note 6)
│ │ │ │ └─ Receiver input signal strength (dBm) of received message
│ │ │ │ (Note 5)
│ │ │ └─ First slot number of message (Note 4)
│ │ └─ UTC hour, minute, second, and fractional-second of measurement
│ │ (Note 3)
│ └─ Sequential message identifier (Note 2)
NOTE 2 The sequential message identifier provides a message identification number from 0 to 9 that is sequentially
assigned and is incremented for each new message. The count resets to 0 after 9 is used. Each sentence of a
message contains the same sequential message identification number – the VSI-sentence and each of the
VDM or VDO sentences that are needed. Note that linking a VSI sentence with a VDM or VDO
sentence(s) results in the need for the VDM or VDO sentence(s) to have the same “Sequential message
identifier” as in the VSI sentence – even when only one VDM or VDO sentence is used.
NOTE 3 This is the hour, minute, and second of a measurement. The fractional portion of a time of arrival (TOA)
measurement is given with a resolution of 100 ns for received messages, if the ABT-1103 has access to an
internal or external accurate timing source (e.g. the internal GPS receiver is receiving satellites signals).
Otherwise TOA is given with a 1 second resolution.
NOTE 4 9999 = requested but not available. This data field should be null (comma comma) if the SPO sentence‟s
data field, “first slot number of each received message,” is set to “no output.”
NOTE 5 0 = requested but not available. This data field should be null (comma comma) if the SPO sentence‟s data
field, “received signal strength of each VDL message,” is set to “no output.”
NOTE 6 0 = enabled (or requested) but not available. SNR measure is not supported by ABT-1103.

6.1.3.33 ZDA – Time and date
The ZDA sentence can be queried to obtain full UTC time and date from the ABT-
1103. Some or all the ZDA fields may be null if time information is not available. ABT-1103
obtains UTC from the internal GPS receiver, external sensors or, if the other options fail, from
remote AIS targets.
$--ZDA,hhmmss.ss,xx,xx,xxxx,xx,xx*hh<CR><LF>
│ │ │ │ │ │
│ │ │ │ │ └─ Local zone minutes (not supported, always null)
│ │ │ │ └─ Local zone hours (not supported, always null)
│ │ │ └─ UTC year
│ │ └─ UTC month
│ └─ UTC day
└─ UTC hour, minute, second, and milliseconds (resolution is 27 ms)

6.1.4 Proprietary sentences
6.1.4.1 Queries
As proprietary sentences cannot be queried using the standard query mechanism, unless
otherwise noted, they are queried sending the same proprietary sentence with all the fields
empty. For instance to read the AIS Installation Settings, the same PELMAIS sentence must
be sent with empty fields on a PI port:
$PELMAIS,,,,,,,,,,,,,,.,,,,*hh<CR><LF>
The ABT-1103 will answer on the same port with a PELMAIS sentence carrying
current status for installations settings parameters.
6.1.4.2 PELMAIS – AIS Installation Settings

This sentence enable the configurations of the ABT-1103 parameters which are
typically related to the installation layout. When the ABT-1103 receives the PELMAIS
sentence on a PI port, all the parameters being provided in the sentence fields are set; the
ABT-1103 replies with a PELMAIS sentence on the same port with the new accepted values.
When empty fields are provided to the ABT-1103, current settings for those parameters
remain unchanged. When empty fields are provided by the ABT-1103, it means that those
parameters are not supported.
$PELMAIS,x,x,x,x,x,x,x,x,x,x,x,x,x,x.x,x.x,x,x,x,x*hh<CR><LF>
| | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | +---- RTCM input10
| | | | | | | | | | | | | | | | | +---- Long range auto reply9
| | | | | | | | | | | | | | | | +---- VDM out filter8
| | | | | | | | | | | | | | | +---- Invert PPS in7
| | | | | | | | | | | | | | +---- Enable PPS out6
| | | | | | | | | | | | | +---- Enable RMC sentence on HS ports5
| | | | | | | | | | | | +---- Enable RTCM from RTCM input port to GPS4
| | | | | | | | | | | +---- Enable RTCM from MSG 17 on DGNSS out3
| | | | | | | | | | +---- Enable GPS on DGNSS OUT2
| | | | | | | | | +---- Longrange baudrate1
| | | | | | | | +---- DGNSS IN baudrate1
| | | | | | | +---- DGNSS OUT baudrate1
| | | | | | +---- Sens2 baudrate1
| | | | | +---- Sens1 baudrate1
| | | | +---- Sens0 baudrate1
| | | +---- KDS baudrate1
| | +---- HS2 baudrate1
| +---- HS1 baudrate1
+---- HS0 baudrate1
NOTE 1 This fields allow to read/set the baud rate of related ports. The possible values range from 0 to 7 with the
following meaning: 0=1200, 1=2400, 2=4800, 3=9600, 4=19200, 5=38400, 6=57600, 7=115200 baud.
Note that PI ports (HS0, HS1, HS2 e KDS) should be set to 38400 baud in compliance to IEC 61162-2
standard. In some particular conditions, where CB and VSI sentences are used and hundreds of targets are
being received, it may be useful to increase the PI baud rate to 115200. Sensor ports (Sens0, Sens1 e
Sens2) should be set to 4800 or 38400 baud in compliance to IEC 61162-1 e -2 standards; the baud rate
should anyway match that of the connected sensor. Long Range port is not supported, the field should be
left null.

NOTE 2 This field is used to enable the output of IEC sentences from the internal GPS receiver to the DGNSS OUT
port. Possible values are: 0=disabled, 1= enabled.
NOTE 3 This field is used to enable the output of RTCM messages received from the VDL to the DGNSS OUT
port. Possible values are: 0=disabled, 1= enabled.
NOTE 4 This field is used to enable the forwarding of RTCM messages received from the selected RTCM input port
to the internal GPS receiver (this service requires that the ABT-1103 is receiving DGNSS corrections from
a remote station). Possible values are: 0=disabled, 1= enabled.
NOTE 5 This field is used to enable the output of RMC sentences at 1 Hz rate to any of the PI ports. RMC contents
will be determined by position and time as calculated by the AIS. Possible values are as in the following
table:
Value RMC output on PI ports

0 None
1 HS0
2 HS1
3 HS0 and HS1
4 HS2
5 HS0 and HS2
6 HS1 and HS2
7 HS0, HS1 and HS2
8 KDS
9 HS0 and KDS
10 HS1 and KDS
11 HS0, HS1 and KDS
12 HS2 and KDS
13 HS0, HS2 and KDS
14 HS1, HS2 and KDS
15 HS0, HS1, HS2 and KDS
NOTE 6 This field is used to enable the output of Pulse Per Second (PPS) signal on GPO0 pin on “Alarm & Sensor”
connector. For test purposes, it is also possible to enable other signals on pin GPO0, but not permanently
(test settings will be lost after a restart). Possible values are: 0=disabled, 1=PPS out, 2=PPS out, inverted,
3=SlotStart out (test mode), 4=TxSlotStart out (test mode).
NOTE 7 This field is used to enable the inversion of an external Pulse Per Second (PPS) signal if input on GPI0 pin
on “Alarm & Sensor” connector. 0=disabled (no inversion), 1=enabled (PPS inverted).
NOTE 8 This field is used to set the VDM out filter level. Possible values: 1=send to PI ports VDM including AIS
messages addressed to other stations and informative messages, 2=don‟t send to PI ports VDM including
AIS messages addressed to other stations, send informative messages, 3=don‟t send to PI ports VDM
including AIS messages addressed to other stations and informative messages.
NOTE 9 Not supported, leave empty.
NOTE 10 This field is used to set the RTCM input port. Possible values are listed in the following table:
Value RTCM input port

0 DGNSS IN (default)
1 HS0
2 HS1
3 HS2
4 MKD
5 SENS0
6 SENS1
7 SENS2
255 RTCM Input port disabled

6.1.4.3 PELMDGC – DGNSS service configuration
The PELMDGC proprietary sentence enables the configuration of the service which
manages the transmissions of DGNSS correction messages received from the ITU-R M.823
compliant DGNSS IN port. When the ABT-1103 receives the PELMDGC sentence on a PI
port, all the parameters being provided in the sentence fields are set; the ABT-1103 replies
with a PELMDGC sentence on the same port with the new accepted values. When empty
fields are provided to the ABT-1103, current settings for those parameters remain unchanged.
When empty fields are provided by the ABT-1103, it means that those parameters are not
available or undefined.
$PELMDGC,x.x,llll.ll,a,yyyyy.yy,a,x.x,x.x,x*hh<CR><LF>
| | | | | | | |
| | | | | | | +-- Get Ref Station pos from RTCM2
| | | | | | +-- DGNSS alarm timeout4
| | | | | +-- DGNSS message timeout3
| | | +----+-- Longitude, E/W of Reference Station ID2
| +----+-- Latitude, N/S of Reference Station ID2
+-- Reference Station ID1
NOTE 1 This field specifies the Reference Station identifier. The ABT-1103 will transmit on the VDL only RTCM
messages sent by a matching Reference Station. The Reference Station ID may range between 0 and 1023;
values above 1023 reset the configured Reference Station ID to undefined. If the configured Reference
Station ID is not defined, transmissions of message 17 from RTCM messages are disabled.
NOTE 2 These fields specify the position of the Reference Station. The position in these fields is loaded statically
on the ABT-1103 if the "Get Ref Station pos from RTCM" field is set to 0 or is not included in the
command. If the "Get Ref Station pos from RTCM" field is set to 1, the position in these fields is ignored
and the ABT-1103 will set the Reference Station position according with the content of RTCM message 3
or 32. Note that if a valid position for the Reference Station ID is not correctly configured or acquired by
the ABT-1103, the transmissions of message 17 from RTCM messages are disabled. Latitude and
Longitude are rounded to one tenth of minute.
If the "Get Ref Station pos from RTCM" field is set to 1, the Latitude and Longitude fields will contain the
position acquired from the RTCM stream when the PELMDGC sentence is output by the ABT-1103.
NOTE 3 This field specifies the number of seconds for the transmission timeout of RTCM messages. When the
timeout interval expires from the RTCM message reception and no new messages have been received, the
message is dropped and transmission of message 17 stops. Values from 0 to 65535 are accepted. Zero
timeout means that timeout is disabled and the RTCM messages never expire. Note that the default value is
60 seconds as specified by the IEC 62320-1 standard and it should not be changed unless explicitly
authorized by system administrators. This field is never null when sent by the AIS.
NOTE 4 This field specifies the number of seconds for the reception timeout of RTCM. If the timeout interval
expires between the reception of two valid RTCM messages, the appropriate alarm sentence is generated
(DGNSS input failed , see alarms section). Values from 0 to 65535 are accepted. Zero timeout means that
timeout is disabled and the alarm sentence is never generated. This field is never null when sent by the AIS,
the default value is 0 seconds (alarm disabled).

6.1.4.4 PELMMEA – Measurements
This sentence may be used to read the internal measurements performed by the ABT-
1103. Sending an empty PELMMEA sentence to the ABT-1103, perform a read of all the
measurements: the ABT will respond with a PELMMEA sentence for each measurement.
Sending a PELMMEA sentence with the total number of sentences set to N, perform a read of
up to N measurements. Sending a PELMMEA sentence with the sequential number of
sentences set to M, perform a read starting from measure M. All other parameters are ignored
by the ABT-1103 and should be set to null.
$PELMMEA,x.x,x.x,hhmmss.ss,c--c,c--c,x.x,x.x,x.x,x.x,x*hh<CR><LF>
│ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ └─ Status (Note 8)
│ │ │ │ │ │ │ │ └─ Last measured value (Note 7)
│ │ │ │ │ │ │ └─ Max value in the valid range (Note 6)
│ │ │ │ │ │ └─ Minimum value in the valid range (Note 6)
│ │ │ │ │ └─ Nominal value (expected value) (Note 6)
│ │ │ │ └─ unit name (Note 5)
│ │ │ └─ name (Note 4)
│ │ └─ UTC of measurement (Note 3)
│ └─ sequential (Note 2)
└─ total (Note 1)
NOTE 1 Total number of sentences performed by the ABT-1103 when sent by the BS, or number of measures to be
read when sent by the control unit. A null value means that all the measurements must be read.
NOTE 2 Index of measure performed by the ABT-1103 when sent by the BS, or first measure to be read when sent
by the control unit. A null value means that the read must start from the first measure.
NOTE 3 Time of execution of the measurement. It is usually null, but it can be used for measures which are only
executed on events (like transmissions).
NOTE 4 Name of measurement.
NOTE 5 Name of measure units.
NOTE 6 Null if not available or unmeaningful.
NOTE 7 Null if never measured yet.
NOTE 8 Status as evaluated by the BIIT:
0 = ok
1 = warning
2 = error.
Example of “12VI” measurement :
$PELMMEA,11,7,,12VI,V,12.0,10.8,13.2,11.8,0*hh<CR><LF>
as read by performing the query:
$PELMMEA,1,7,,,,,,,,*hh<CR><LF>

6.1.4.5 PELMRXM – Receiver manager settings
The PELMRXM proprietary sentence allows the configuration of the receiver manager.
The receiver manager is only supported by AIS stations including 3 receivers and may not be
enabled if not explicitly required by the customer.
Usually, each physical receiver of the ABT-1103 is assigned to a specific task: the first
two receivers are dedicated to AIS1 and AIS2 channels reception. The third receiver is
dedicated either to DSC or WAIS reception or is idle, depending on the specific set of
functions and on the configuration of the AIS station.
The PELMRXM message allows different associations between hardware receivers and
receiver tasks so that the operator may reallocate them according to the operational priority in
case of failures.
When a PELMRXM sentence is sent to the ABT-1103 on a PI port, all the fields should
be set and all receivers should be assigned to different tasks, otherwise the settings will be
rejected; in any case the ABT-1103 replies with a PELMRXM sentence on the same port with
the possibly updated values. If empty fields are provided by the ABT-1103, it means that the
receiver manager is not supported by the AIS station (default assignments are used).
$PELMRXM,x.x,x.x,x.x*hh<CR><LF>
│ │ │
│ │ └─ Task assigned to hardware receiver 3 (Note 1)
│ └─ Task assigned to hardware receiver 2 (Note 1)
└─ Task assigned to hardware receiver 1 (Note 1)
NOTE 1 This field specifies the task ID assigned to each receiver. The task ID may range between 0 and 2:
0: AIS1 receiver
1: AIS2 receiver
2: other tasks (WAIS, DSC, idle) depending on enabled functions and configuration.
Each task can only be assigned to one receiver.

6.2 Sensor ports
Sensor ports enable the ABT-1103 to receive data from external devices which may
provide position and time information if the ABT-1103 is so configure (by default, time
synchronization is given by the internal GPS, while the position is manually configured).
Sensor ports are compliant to IEC 61162-2/-1 standards. Time information should
always be in UTC and position must be referenced to WGS84 datum. The ABT-1103 only
accepts the standard IEC sentences listed in the table below. Fields marked with an asterisk
are not required by the ABT-1103 so that devices compliant with older editions of the IEC
61162-1 standard can be supported.
Sentence Fields used by ABT-

Updated internal parameters
formatter 1103
Expected errors for Position accuracy
GBS
latitude and longitude RAIM flag (set to 1 if GBS is being received)
Talker ID
Latitude EPFS type
Longitude Position
GGA
Altitude Position accuracy
UTC time UTC time
GPS Quality indicator
Talker ID
Latitude EPFS type
Longitude Position
GLL
UTC time Position accuracy
Status UTC time
Mode indicator*
Talker ID
Latitude EPFS type
Longitude Position
GNS
Altitude Position accuracy
UTC time UTC time
Mode indicator
Talker ID
Latitude
EPFS type
Longitude
Position
RMC UTC time
Position accuracy
UTC date
UTC time and date
Status
Mode indicator*
UTC time
ZDA UTC time and date
UTC date
Table 6 – Sensor ports supported sentences
At least one type between GGA, GLL, GNS and RMC sentences should be sent to the
ABT-1103 in order to acquire a valid position an external sensor. Proper time synchronization

requires at least one type between ZDA and RMC and the provision of a PPS pulse on the
GPI0 pin. Refer to the IEC 61162-1 standard for detailed information on the format and
content of the above sentences.
Note that Presentation Interface ports may also be used to input external sensor data to
the ABT-1103 allowing for simplified connection schemes. The PI ports supports all the
sentences listed in table 4.
6.3 DGNSS OUT port

The ABT-1103 can be configured to send the internal GPS output to the DGNSS OUT
port. Data from the internal GPS is compliant to IEC 61162-1 standards. Time information is
always sent in UTC and position is referenced to WGS84 datum. The following sentences are
generated on the DGNSS OUT port: DTM, GBS, GGA, GLL, GNS, RMC, VBW, VTG,
ZDA.
Refer to the IEC 61162-1 standard for detailed information on the format and content of
the above sentences.

User Manual ABT-1103 Ed1 G ENG

Uploaded by

Copyright:

Available Formats

You might also like

User Manual ABT-1103 Ed1 G ENG

Uploaded by

Document Information

Original Title

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

User Manual ABT-1103 Ed1 G ENG

Uploaded by

Copyright:

Available Formats

________________________________________

AIS BASE STATION TRANSPONDER

REVISIONS AND APPROVALS

ABT-1103 AIS Base Station User Manual Pag. 2 of 105

This manual refers to hardware revision C6 (configuration index 6) and firmware

Read this manual before use.

 the title of the manual

ABT-1103 AIS Base Station User Manual Pag. 3 of 105

ABT-1103 AIS Base Station User Manual Pag. 4 of 105

LIMITED AIS BASE STATION

ABT-1103 AIS Base Station User Manual Pag. 5 of 105

REVISIONS AND APPROVALS 2

CHAPTER 1 AN INTRODUCTION TO AIS 11

1.1 THE AIS BASICS 11

CHAPTER 2 ABT-1103 OVERVIEW 15

2.1 GENERAL DESCRIPTION 15

CHAPTER 3 MODES OF OPERATION 22

ABT-1103 AIS Base Station User Manual Pag. 6 of 105

CHAPTER 5 OPERATING THE ABT-1103 45

ABT-1103 AIS Base Station User Manual Pag. 7 of 105

CHAPTER 6 SUPPORTED IEC 61162 SENTENCES 59

6.1 PRESENTATION INTERFACE PORTS 59

ABT-1103 AIS Base Station User Manual Pag. 8 of 105

ABT-1103 AIS Base Station User Manual Pag. 9 of 105

ABT-1103 AIS Base Station User Manual Pag. 10 of 105

1.1 THE AIS BASICS

Figure 1 – The AIS system

ABT-1103 AIS Base Station User Manual Pag. 11 of 105

1.3 THE ROLE OF IALA

1.4 THE ROLE OF IMO

ABT-1103 AIS Base Station User Manual Pag. 12 of 105

1.5 THE ROLE OF ITU

1.6 THE ROLE OF IEC

ABT-1103 AIS Base Station User Manual Pag. 13 of 105

Regulation 19 of SOLAS Chapter V - Carriage requirements for shipborne navigational

ABT-1103 AIS Base Station User Manual Pag. 14 of 105

2.1 GENERAL DESCRIPTION

ABT-1103 AIS Base Station User Manual Pag. 15 of 105

The ABT-1103 features the following functional elements:

 Two multi-channel VHF receivers for parallel receiving processes on channel A

ABT-1103 AIS Base Station User Manual Pag. 16 of 105

2.2.1 VHF Receivers

2.2.2 VHF transmitter

2.2.3 Presentation Interface

ABT-1103 AIS Base Station User Manual Pag. 17 of 105

2.2.4 Type of operation modes

2.2.5 DGPS unit

ABT-1103 AIS Base Station User Manual Pag. 18 of 105

AIS Base Station ABT-1103

SYSTEM DEVICES SUBSYSTEMS MODULES ACCESSORIES

Figure 2 – ABT-1103 product breakdown structure

ABT-1103 AIS Base Station User Manual Pag. 19 of 105

2.4 APPLICABLE REGULATIONS AND STANDARDS

ABT-1103 AIS Base Station User Manual Pag. 20 of 105

ABT-1103 AIS Base Station User Manual Pag. 21 of 105

3.2 Receive only mode

As transmissions may be requested also by sending appropriate messages on the PI

3.3 Dependent mode