Jotron Beacon Coding Procedure

Jotoron Beacon
Coding Procedure
Tron 40VDR (VR-7021F)

Tron 40Smk2
Tron 40GPSmk2
Tron 60S
Tron 60GPS
Model
1st Edition 2014/10
Attached;
C/S T.001
MSC Circ. 1040
MSC Circ. 1039
MSC Cir.c 1222
Res. MSC. 333(90)
Res. A. 810(19)
CONFIDENTIAL (internal use only)
This confidential document is used only by FURUNO authorized persons. It is strictly prohibited to
reproduce the document in whole or in part without prior written permission of FURUNO.
The paper used in this manual
is elemental chlorine free.
・FURUNO Authorized Distributor/Dealer
9-52 Ashihara-cho,
Nishinomiya, 662-8580, JAPAN
All rights reserved. Printed in Japan A : NOV . 2014
Pub. No. TIE-56820-A

TRON40SMK2
Contents
Contents
Summary
1. Installation flow chart of Beacon ······································································· 1
2. Coding ·············································································································· 2
2.1 Coding protocols ························································································· 2
2.2 Selecting a Coding protocol ········································································ 3
3. Beacon Operating····························································································· 5
3.1 Maintenance of Beacon ·············································································· 6
3.2 Self test ······································································································· 7
4．Other Information ····························································································· 8

4.1 For Vessel Classification Test ····································································· 8
4.2 Cayman Island: Guide to Applicants for a Maritime ICT
(Ship Radio Station) License ············· 10
4.3 Summary of User Protocols Coding Options ············································· 11
4.4 Outline of Location Protocols ···································································· 12
5. Beacon Installation ························································································· 13
Chapter 1. Installing the PRU-50 S/W

1.1 Installing the PRU-50 driver software ·························································· 1-1
1.2 Boot up the Beacon Programmer ································································ 1-2
Chapter 2. Beacon Programmer

Screens of the Beacon Programmer·································································· 2-1
2.1 Screens of the Beacon Programmer···························································· 2-2

2.1.1 Beacon information area ······································································· 2-2
2.1.2 Bracket information area ······································································· 2-3
2.1.3 MID/Country Code information area ······················································ 2-3
2.1.4 Protocol information area ······································································ 2-4
2.1.5 Battery information area ······································································ 2-10
2.1.6 Vessel information area······································································· 2-11
2.1.7 Additional information area ·································································· 2-11
2.1.8 Coding message information area ······················································ 2-12
i
This confidential document is used only by FURUNO authorized persons.
It is strictly prohibited to reproduce the document in whole or in part without prior written permission of FURUNO.
Contents
2.2 [Program], [Read] and [Report] buttons ····················································· 2-14

2.2.1 [Program] button ················································································· 2-14
2.2.2 [Read] button ······················································································ 2-18
2.2.3 [Report] button ···················································································· 2-20
2.3 Menu bar ··································································································· 2-22

2.3.1 Menu tree ···························································································· 2-22
2.4 Details of the menus ·················································································· 2-26

2.4.1 Beacon menu ······················································································ 2-26
2.4.1.1 Tron 40S～Tron40VDR(40S Capsule) ·········································· 2-26
2.4.1.2 Program························································································ 2-27
2.4.1.3 Read ····························································································· 2-27
2.4.1.4 Program Report (Jotron) ······························································· 2-28
2.4.1.5 Programming report (UK, US, Australia or NZ registration) ·········· 2-28
2.4.1.6 Save in database (without programming) ····································· 2-29
2.4.2 Bracket menu ······················································································ 2-29
2.4.3 Protocol menu ····················································································· 2-30
2.4.4 Options menu······················································································ 2-31
2.4.4.1 Program/Report.. ·········································································· 2-31
1) Programming -> Perform ID Check ··················································· 2-31
2) Report ······························································································· 2-32
3) Protocols allowed ············································································· 2-34
4) Location protocols allowed ······························································· 2-34
2.4.4.2 Beacon/Brackets.. ········································································ 2-35
1) Beacon serial number ······································································· 2-35
2) Bracket serial number ······································································· 2-36
3) Beacons allowed··············································································· 2-36
2.4.4.3 Country ························································································· 2-37
1) Countries ·························································································· 2-37
2.4.4.4 PRU ······························································································ 2-39
2.4.4.5 PRU-30························································································· 2-39
2.4.5 Operator menu ···················································································· 2-40
2.4.6 Database menu ··················································································· 2-41
2.4.6.1 View database ·············································································· 2-41
1) [Beacon List] tab ··············································································· 2-41
2) [Beacon ] tab ···················································································· 2-41
3) [Import from JOT file] tab ·································································· 2-42
4) [Export] tab ······················································································· 2-44
・[Export to .txt file] button ·································································· 2-44
・[Export to .JOT file] button ······························································· 2-44
2.4.6.2 Jotron report(generate) ······························································· 2-45
1) [Send Email] button ·········································································· 2-45
2) [Copy to Disk] button ········································································ 2-45
2.4.7 Help menu··························································································· 2-46
2.4.7.1 Contents ······················································································· 2-46
2.4.7.2 Register ························································································ 2-47
ii
Contents
Chapter 3. Coding Procedure

3.1 Coding procedure ························································································ 3-1
3.1.1 Edit the Coding data·············································································· 3-2
3.1.2 Coding ·································································································· 3-8
3.1.3 Create Programming report ·································································· 3-9
3.1.4 Create JOT file (Only Tron 40VDR) ····················································· 3-11
3.2 Beacon Test ······························································································· 3-12

3.2.1 Self test ······························································································· 3-12
3.2.2 EPIRB Tester: BT-100A, check the Power and Frequency ·················· 3-13
3.3 Labeling ····································································································· 3-16

3.3.1 Label information items ······································································· 3-16
3.3.2 Battery Service life ·············································································· 3-17
3.3.3 Hydrostatic Release Unit (HRU) ·························································· 3-18
3.3.4 Mounting the Beacon ·········································································· 3-19
Chapter 4. Outline of the Beacon

4.1 Tron 60S, Tron 60GPS ················································································ 4-1
4.2 Tron 40VDR: VR-7021F(Float –Free Data Recoding Unit) ·························· 4-6
Appendix 1. C/S T.001 SPECIFICATION FOR

COSPAS-SARSAT 406 MHz DISTRESS BEACONS
1. INTRODUCTION ··························································································· 1-1
2. SYSTEM REQUIREMENTS ·········································································· 1-1
3. DIGITAL MESSAGE STRUCTURE ······························································· 3-2
4. ENVIRONMENTAL AND OPERATIONAL REQUIREMENTS························ 4-1
ANNEX A BEACON CODING ·········································································· A-1
A1 GENERAL ································································································· A-1
A2 USER PROTOCOLS ················································································· A-5
A3 LOCATION PROTOCOLS ······································································· A-17
ANNEX B SAMPLE BOSE-CHAUDHURI-HOCQUENGHEM
ERROR-CORRECTING CODE CALCULATION ·················· B-1
B1 Sample 21-Bit BCH Code Calculation ······················································· B-1
B2 Sample 12-Bit BCH Code Calculation ······················································· B-4
ANNEX C LIST OF ACRONYMS ····································································· C-2
iii
Contents
Appendix 2. MSC Circ/Res

MSC Circ. 1040
REVISED GUIDELINES ON ANNUAL TESTING OF
406 MHz SATELLITE EPIRBs ········ AP2-2
MSC Circ. 1039

GUIDELINES FOR SHORE-BASED MAINTENANCE OF
SATELLITE EPIRBs ········· AP2-4
MSC Circ. 1222

GUIDELINES ON ANNUAL TESTING OF VOYAGE DATA RECORDERS
(VDR) AND
SIMPLIFIED VOYAGE DATA RECORDERS (S-VDR) ······················ AP2-10
RESOLUTION MSC.333(90) (adopted on 22 May 2012)

ADOPTION OF REVISED PERFORMANCE STANDARDS FOR
SHIPBORNE VOYAGE DATA RECORDERS (VDRs) ··············· AP2-15
RESOLUTION A.810(19)
Performance Standards for Float-Free Satellite Emergency
Position-Indicating Radio Beacons(EPIRBs) Operating on 406MHz ··· AP2-22
COMSAR/Circ.32
HARMONIZATION OF GMDSS REQUIREMENTS FOR RADIO
INSTALLATIONS ON BOARD SOLAS SHIP ······ AP2-26
Appendix 3. MSC 1039, 1040 Test Reprts

Form MSC 1040 (0704) ················································································ AP3-2
Form MSC 1039 (0704) ················································································ AP3-3
Annual Testing of 406MHz EPIRBS ······························································ AP3-4
406MHz Satellite EPIRB Annual Test Report ················································ AP3-5
iv
Summary
Summary
1. Installation flow chart of Beacon

Manufacturer Ship Owner
FURUNO Furuno Subsidiaries /Distributors
ELECTRIC CO., LTD. Installation companies Ship Yard &
Jotron AS Ship
Ship Managiment Company
Getting of
Ship's Informotion
Ship's Informotion
Manufactureing &
1. Name of ship
Shipment
2. MMSI
3. IMO No.
Beacon Test 4. Callsign
Results
5. Flag
6. Hull No
Yes
Float Free Acceptance Test
Capsule & Shipment
Beacon Test
No Results
Coding & Labeling
Yes No
Float Free
Capsule
Installation
Filing of data sheet

Installation
on board for SR Survey
Furuno Subsidiaries/ Distributors Programming Programming

Report Report
FNDs upload data to SMS
Beacon Test Beacon Test
Programming Results Results
Report
JOT file
Note)
For Furuno subsidiaries/distributers;
Attach Coding data of Float-Free Capsule(Tron 40VDR: VR-7021F) to SMS in one
week since coding has taken place. It is not necessary to attach Satellite EPIRB(W/O
Tron 40VDR: VR-7021F to SMS as integrated data.
Name each file to save it as the same format as below.

- Programming Report:
Name a file as “Beacon serial No._Ship’s name_Hex(UNI).pdf”, not including “”.
Ex. “00082_FURUNO_205C3C481EFFBFF.pdf”
- Jot file:
Name *.jot file as “Beacon serial No._Ship’s name.jot”, not including “”.
Ex. “00082_FURUNO.jot”
1
It is strictly prohibited to reproduce the document in whole or in part without prior written permission of FURUNO
Summary
2. Coding
Make sure that Beacon Programmer S/W is installed in PC.
For instructions for S/W installation, see “Chapter 1. Installing PRU-50 S/W.”
Most of the countries where vessels are registered use the coding using Maritime User
Protocol or protocol of MMSI Standard Location Long. On the other hand, certain
countries such as Cayman Islands use Serial No. for the coding. Make sure to Ship’s
owner/Ship management company/Ship yard which kind of protocol vessels are using
for the coding. For the protocol required by each country, see “C/S S.007
HANDBOOK OF BEACON REGULATIONS” for Cospas/Sarsat.
The coded “Programming reports” should be handed over to the ship’s owner/operator.
This report is used for registering the EPIRB in the database.
2.1 Coding protocols

They are classified into two types:
▪ Protocol that does not contain positional data (User Protocol)
They are applicable for Beacons without GPS functions. They include Maritime
User Protocol, Radio Call Sign User Protocol and Serial User Protocol. They are a
short message of 112 bits. For structures, see “Summary of User Protocols Coding
Options”.
The position of the Beacon can be determined by using the doppler effect of the
signal from the Beacon to a LEOSAR (Low Earth Orbit Search and Rescue)
satellite.
▪ Protocol that contains positional data (Location Protocol)
They are applicable for Beacons with GPS functions. They include User Location
Protocol, Standard Location Protocol and National Location Protocol. They are a
long message of 144 bits. For structures, see “Summary of User Protocols Coding
Options”.
The position of the Beacon can be determined by a geostationary satellite
(GEOSAR) using positional data from the Beacon.
Position
Beacon Protocol Satellite
Resolution
Beacon without
User Protocol 5 km LEOSAR
GPS
MMSI Standard Location Protocol 120 m GEOSAR (LEOSAR)
Beacon with GPS
Marin User Location Protocol 7 km GEOSAR (LEOSAR)
2
Summary
2.2 Selecting a Coding protocol

Use an MMSI protocol except for ships having a flag of the Cayman Islands, Canada
or the USA.
If it is necessary to use a coding protocol other than MMSI based ones, see Handbook
of Beacon Regulations C/S S.007 published by COSPAS-SARSAT to identify the
protocols that have been approved by the country concerned.
http://www.cospas-sarsat.int/en/documents-pro/beacon-regulations-handbook
1) Beacon without GPS
Use the Maritime User Protocol (needs the MMSI to be entered).
In the Jotron’s Cospas/Sarsat Beacon Programmer, select a type of Beacon from
[Beacon] menu and select “Maritime” from [Protocol] menu.
2) Beacon with GPS

Use the Standard Location Protocol (needs the MMSI to be entered).
In the Jotron’s Cospas/Sarsat Beacon Programmer, select a type of Beacon from
[Beacon] menu and select “MMSI Standard Location Long” from [Protocol] menu.
3) The Cayman Islands

Encode the Beacon Serial No. and (automatically assigned) C/S Approved No.
The Cayman Islands do not accept coding based on the data of MMSI or Radio
CallSign. See an attachment “Guide to Applicants for a Maritime ICT (Ship Radio
Station) License.”
▪ For Beacon without GPS, use Serial EPIRB: “Serial User Protocol”.
▪ For Beacon with GPS, use “Serial EPIRB Standard Location Protocol” (Serial
Number needs to be entered).
Note)
MID/Country Code of Cayman Island
- 319/232 Cayman Is-UK serial
Appears of “Country” column in the Programming Report -> “232”
- 319/366 Cayman I-USA serial
Appears of “Country” column in the Programming Report -> “366”
And, PRU S/W output the “Registration Form” automatically when you carried out
Coding.
3
Summary
Table 2.2.1 Protocol Classification

Types of
Satellite EPIRB without GPS Satellite EPIRB with GPS
EPIRB
Major
User Protocol Location Protocol
grouping of
(For short message) (For long message)
protocol
Types of User-Location
Radio call Standard National
protocol Serial User Protocol
Maritime User sign User Location Protocol Location
Protocol
Protocol Protocol Protocol
(Maritime/Serial
Naming per (MMSI/Serial
(Serial EPIRB/Radio Call
PR40 is (Maritime) EPIRB)
(Radio
sign User
EPIRB Standard (Without
shown in ( ). Callsign) Location Long) selector)
Protocol)
Input
[1] [2] [3] [2] [1] [2] [3] [1] [3] N/A
information
Usable Usable
Usable for Usable
subject for ships
ships flying subject to
to Usable subject to flying the
Normal the flag of approval Normal
Use approv approval by the flag of N/A
use the by the flag use
al by flag state the
Cayman state
the flag Cayman
Islands
state Islands
Input information
[1] MMSI
[2] Radio Call Sign
[3] EPIRB (C/S Approved No.) with Serial Number
4
Summary
3. Beacon Operating
A 406 MHz beacon message, and 121.5 MHz signal as well, will be sent when the
Beacon is removed from the Bracket and immersed in the water, or when the Beacon is
removed from the Bracket and switched ON. The 406 MHz beacon message will be
sent at intervals of 50 seconds ± 5%.
After the 406 MHz beacon message is sent, a 121.5 MHz homing signal (sweep signal)
will be sent. Tron 40VDR sends a Morse code “V” before the 121.5 MHz homing
signal. As an optional function, other Beacons can send a Callsign by means of Morse
code before sending the homing signal.
The homing signal is a down-sweep signal. To make it an up-sweep signal, set MID to
America.
406 MHz 406 MHz
Test MSG Real MSG
ON
121.5 MHz Sweep Sig.
5-8s 50s
5-8 min. 8-16min.
Default Pos. Pos. fix Pos. update
Information) Difference between Beacon test message and real message
406 Hex message: See FFFE2F9B026F85507FDFFB7A6BF783E0F66C.

The underlined numbers differ depending on whether the message is Normal Message
or Selftest Message.
▪ For Selftest Message: A message starting with FF FE D0---- will be repeated.
▪ For Normal Message: A Selftest Message starting with FF FE D0---- will occur
and then a Normal Message starting with FF FE 2F ------
will be repeated.
5
Summary
3.1 Maintenance of Beacon

3.1.1 Every month
A Self test will be performed.
The Beacon should be checked using the means provided for testing on the equipment.
Note that the 406 MHz beacon message is a Test message, so that the Cospas/Sarsat
system does not recognize it.
Furthermore, the following check is recommended;
- Visually check the Beacon.
Check that the Beacon can be easily detached from the Bracket; Beacon and
Bracket are not damaged; they are not stained or smeared with paint, oil or
chemicals; and verifying the presence of a firmly attached lanyard in good
condition.
- Check the expiry date of the Battery and the Hydrostatic Release Unit(HRU).
3.1.2 Every year

The Tron 40 VDR Float Free Capsule is under the regulation of the IMO MSC.1/Circ
1040 rev.1 annual test performed by authorized radio-surveyor or authorized personal
trained. Additional requirement for testing Tron 40VDR: VR-7021F Float Free
Capsule is IMO MSC.1/Circ.1222. Important to clean the surface on the VDR
docking-module and VDR storage module (apply Silicon grease), fitted on the FB-40
bracket and the Tron 40VDR: VR-7021F Float Free Capsule lower part, so to obtain
secure and safe data transmission.
3.1.3 Every 2 year

Replace the Hydrostatic Release Unit(HRU). Mark the expiry date on HRU after
replacement.
3.1.4 Every 5 year (Shore Based Maintenance: SBM)

The Beacon is under the regulation according to SOLAS Chap.IV reg.15.9.2and IMO
MSC.Circ 1039 guideline: SBM (Shore Base Maintenance). There is only Authorized,
trained and certified personal. The interval is dependent on the flag-state
administration. For these IMO Circulars, see “Appendix 2”.
Replace the battery and other parts according to the instructions of the manufacturers.
Mark the expiration date of the battery on the beacon after replacement.
3.1.5 Inspection every decade

Recommended to replace both the Beacon and Bracket.
6
Summary
3.2 Self test

The Self test procedure is the same for all types of Beacons.
406 MHz
Test ON
Test Msg Test ON 406 MHz
6-8s Test Msg
6-8s
121.5 MHz
Sweep Sig.
Tron 60S, Tron 60GPS, Tron 40Smk2, Tron 40GPSmk2

Tron 40VDR
3.2.1 Self test

Procedure)
1. Remove the Beacon from the Bracket.
2. Slide the operation SW from [READY] to [TEST] position and keep the position
for about 15 seconds.
3. OK if the LED at the tip of the antenna is flashed on one time.

If the test found the Beacon defective, the LED at the tip of the antenna is flashed on
multiple times. The number of repeats of the LED being flashed on depends on the
type of errors as shown below.
Number of
Fault indication;
flashes
1 No Error, the unit is OK
2 Low power, 406 MHz transmitter
3 Low battery voltage
4 Low power, 121.5 MHz transmitter
5 Transmitter failure, 406 MHz
6 Transmitter failure, 121.5 MHz
EPIRB module not programmed or programming not
7
completed.
4. After the test, return the SW to [READY] position.
7
Summary
3.2.2 GPS test

Procedure)
For Tron 60GPS, Tron 40VDR:VR-7021F, the GPS test (up to 2 minutes) should be
limited to max 60 times for saving battery. The GPS test should be performed once a
month. Note that if it becomes 60 times or more, it will become the normal self test.
1. Slide the operation SW to [TEST] position twice within a period of 3 seconds.
2. A short beep is heard repeatedly at three seconds intervals until the GPS determines
the position.
3. OK if two beeps are heard.
If it fails to measure the position, five beeps are heard. If 10 beeps are heard, the
maximum limit of the number of repeats of the GPS test (60 times) has been
exceeded.
4．Other Information
4.1 For Vessel Classification Test
Below is data necessary for SR.
- Beacon Test Results (Factory data)
- Beacon Programming Report
- Beacon Test Report
- MSC. 1040 Annual Maintenance Report
Note:
- For annual performance test, Beacon Test Results data is not necessary.
- When SBM has been carried out, MSC. 1039 SBM Maintenance Report data is
required.
1．ex; Beacon Test Results 2．ex; Beacon Programming
8
Summary
3．ex; Beacon Test Repot
4．ex; MSC. 1040 Annual Maintenance report

(Furuno Form)
5. ex; MSC. 1039 SBM Maintenance report

(Furuno Form)
9
Summary
4.2 Cayman Island: Guide to Applicants for a Maritime ICT

(Ship Radio Station) License
10
Summary
4.3 Summary of User Protocols Coding Options
11
Summary
4.4 Outline of Location Protocols
12
Summary
5. Beacon Installation
1. Installation place;
Installation place is mentioned in COMSAR/Circ.32. Appropriate place is near the
Navigation bridge such as a wing area, or Compass deck which can be accessed by
stairs.
Don’t install the Beacon in places as below.
1) Places where the Beacon is hooked so that it can’t come to the surface when a ship
sinks.
2) Places where the Beacon can’t be taken out to a Survival craft easily, such as the
place where can be only accessed by a vertical ladder.
2. Mounting;
Install the Beacon in a vertical direction.
When installing the Beacon in a handrail of wing, weld a metal plate bigger than the
Beacon bracket and install the Beacon in the metal plate. Also, make the grounding
route from the Beacon to ship hull as short as possible.
One of a VR-7021F: Tron 40VDR screw for attaching a Bracket is also a ground
terminal. Make sure to ground it.
3. Installation of Junction Box: VR7022F (VR-7021F: Tron 40VDR only)

Make sure to ground.
4. For prevent RFI from VHF, MH/HF system (VR-7021F: Tron 40VDR only)
Keep VR-7021F at least 5 m away from a VHF antenna to prevent radio frequency
interference of VHF radio telephone. Log is not recorded correctly with the
interference. Install VR-7021F in the opposite direction from the place where a MF/HF
antenna is installed. For example, if a MF/HF antenna is installed in the port side,
install VR-7021F in the starboard side.
13
Summary
5. Mounting Beacon in Bracket (VF-7021F: Tron 40VDR only)

Apply silicone grease to the contact surface between VDR storage module and VDR
docking module, and make sure there is no space in between. Otherwise, log is not
recorded correctly because it is recorded in the VDR storage module through the VDR
docking module.
It is necessary to announce customers how to mount the beacon.
Apply silicone grease

to contact surface
between VDR storage
module and VDR
VDR storage docking module so that
Module they are stuck tight.
Silicone grease
VDR Docking
Module
6. Instruction panel
Install the attached acrylic instruction panel in where close to the Beacon is installed.
For example, attach the panel with silicone sealant, or attach it with double-sided
adhesive tape and then apply silicone sealant around the panel.
14
Chapter 1. Installing Chapter
the 1.PRU-50 S/W
Installing the PRU-50 S/W
1.1 Installing the PRU-50 driver software

For some PCs, a “Virtual COM port driver” requires to be installed. Connect the PC
which the driver is installed in, to the Internet in order to search the “Virtual COM port
driver” from the Internet and install.
Procedure)
1. Double-click on “setup.exe” located in the PRU-40 folder (Ver3.8.2 2014/10).
2. An Install Wizard will boot up.
3. Proceed according to the instructions given in the screen.
1-1
4. The software installed will be saved as a folder name “Jotron -> PR40” in the
Program File folder. The figure below shows the contents of the folder.
1.2 Boot up the Beacon Programmer

Procedure)
1. Connect PRU-50 to a USB port on the PC.
2. Note the number of the COM port to which PRU-50 was connected. To do this
check, open the “Device manager” and see “USB Serial Port (COMx).”
3. Double-click “PR40” that appears in [Start] -> Program -> Jotron Beacon
Programmer folder. The following screen “PR40 REGISTRATION” will appear.
Note that this screen appears automatically at the first boot.
After all entries are made, press [Register later].
Information)
To open a screen “PR40 REGISTRATION”, select “Help -> Register” from the
menu bar in the Beacon Programmer screen.
The following input data are those necessary for registering

with Jotron though they are presently not used. However,
some inputted data is reflected in Programming report.
▪ Name: Enter the name of the PR40 Registration person.
▪ Company: Enter the name of the company.

(Max. 25 characters, reflected in “Programming report”)
▪ Jotron dealer(Furuno) number: Enter 15050.

(Reflected in “Programming report”)
▪ Email for updates: Entry unnecessary.
1-2
4. A screen “Enter operator initials” will pop up. Enter the name of the person
responsible for coding, and then press [OK].
The name entered here will be automatically taken as the entry of the
“Programming by” field in the screens “Programming Report” and “Data
programmed data in EPIRB/PLB.”
Information)
Another way for opening “Enter operator initials” is to select "Operator" from
the menu bar in the Beacon Programmer screen.
5. The following screen “Beacon Programmer” will appear.
1-3
6. Select “Options” from the menu bar and then select PRU. A pull down menu will
appear. Select the COM port no. that you have checked in “the Step-2”, and then
press “OK”.
Now you are ready for programming and reading using PRU-50 S/W.
1-4
Chapter 2. Beacon
Chapter Programmer
2. Beacon Programmer
Screens of the Beacon Programmer

Booting up the installed PR-50 S/W will open the following Beacon Programmer
screen. Using the data boxes in this screen, perform coding for the Beacon.
This chapter shows how to use information entry areas, menu bars and [Programming],
[Read] and [Report] buttons.
2.3 Menu bar 2.1.2 Bracket information area

2.2 [Programming],
[Read] and [Report]
2.1.1 Beacon
information area
2.1.5 Battery information area

2.1.6 Vessel information area
2.1.3. MID/Country
Code information area
2.1.4 Protocol information
2.1.7 Additional information area

2.1.8 Coding message information area
Table 2.1 Screens of the Beacon Programmer
2-1
2.1 Screens of the Beacon Programmer

2.1.1 Beacon information area
First, select a type of Beacon from the [Beacon] menu. The Beacon list contains
Beacons selected from the Beacon/Bracket menu. To access to the menu, click on
[Options] tab.
• Version: Enter “000” in the Beacon Version number entry field.
Beacon type Beacon Version

Tron 40VDR: VR-7021F 000
Tron 40Smk2 000
Tron 40GPSmk2 000
Tron 60GPS 000
Tron 60S 000
• Serial number:
Enter the Serial number. of the Beacon (marked on the surface of the
Beacon).
Note) For Tron 40VDR: VR-7021F, this is not the Serial number.
shown in the nameplate of “VR-7021F”.
Serial number
Note: this is not the Serial number.

Shown in the nameplate of VR-7021F.
• Label:
Automatically created using the entries of “Version” and “Serial number”
and marked as “Version + Serial number.”
• Replace beacon:
This is an event record of replacement of the Beacon. If this is a new
installation, choose “None” in the pull down menu. If this is a
replacement, choose a Beacon type among options of Tron 30S, Tron
30Smk2 --- and Other contained in the pull down menu.
For example, if KANND Beacon is to be replaced, choose “Other.”
2-2
2.1.2 Bracket information area

First, select a Bracket type from the [Bracket] menu. The Bracket list differs depending
on the type of the Beacon you chose. Note that the type of the Bracket is marked on
the surface of the Bracket.
Bracket
Beacon type Bracket type Serial number
Version
Tron 40VDR: Marked on the VDR
FB-40VDR
VR-7021F Docking Module
N/A:
Tron 40Smk2 FB-6
Entry
Tron 40GPSmk2 FB-6 N/A:
unnecessary
Tron 60GPS FB-60 Entry unnecessary
Tron 60S FB-60
• Version:
This is an entry field for Bracket Version number However, no entry is
necessary in this case.
• Serial number:
This is an entry field for Bracket Serial number However no entry is
Note)
In case of Tron 40VDR: VR-7021F, enter the Serial number. The Serial
number is marked on the surface of the VDR Docking module.
• Label:
Automatically created using the entries of “Version" and “Serial number,”
and marked as “Version + Serial number.”
2.1.3 MID/Country Code information area

MID of the flag state: Choose a country code from the pull down menu.
You may customize the MID list so that it includes such MIDs that you often use. To
do this, select [Options] -> Countries.. For details, see page 2-37.
Tron 40VDR Beacons other than

Tron 40VDR: VR-7021F
2-3
• MID/Country Code:
Choose a MID (country code) from the pull down menu, or enter the number
directly. For example, enter 431 or 432 for Japanese ships, 354 through 357
for Panamanian ships.
Note that MID is shown by the first three digits of the MMSI number. of
nine digits.
Information)
MMSI is a number of nine digits. The first three digits represent an MID
(Maritime Identification Digit; country code), and the following six digits
represent a Ship station identification.
Therefore, for MID/Country Code, enter the first three digits of the MMSI
number. The remaining six digits should be entered in the Protocol
information field.
• Send morse code on 121.5 MHz:
For a Beacon other than Tron 40VDR: VR-7021F, select this check box.
If this check box is selected, the Callsign specified in “Vessel information
area” will be sent by means of Morse code before the 121.5 MHz Homing
signal is sent.
Note that sending a Callsign is optional, not obligatory.
For a Beacon of Tron 40VDR: VR-7021F, chosen, this option is unavailable.
In this case, a code “V” will be sent before the 1215 MHz homing signal is
sent.
2.1.4 Protocol information area

To choose a protocol, use [Protocol] menu. However, available protocol options differ
depending on the type of the Beacon you chose from the [Beacon] menu.
The following figure shows a case of using Tron 40VDR: VR-7021F,.
If you chose a Beacon without GPS, such as Tron 60S, you must use the “User
Protocol” applicable for short messages not containing positional data. Most countries
(flag states) require “Maritime User Protocol” to be used.
If you chose a Beacon with GPS, such as Tron 60GPS and Tron 40VDR: VR-7021F,
you must use the “Location Protocol” applicable for long messages containing
positional data. Most countries (flag states) require “MMSI Location Protocol” to be
used.
Remember that available protocols depend on the flag of the ship.
2-4
Shown below is the structure of messages for each type of protocol.
MARITIME USER PROTOCOL

Bits 25 26 27 36 37 39 40 81 82 83 84 85
MMSI or Radio
Country
..... 0 1 010 Call Sign 0 0 RL
Code
(42 bits)
RADIO CALL SIGN USER PROTOCOL

Bits 25 26 27 36 37 39 40 81 82 83 84 85
Radio Call Sign
..... 0 1 Country Code 110 0 0 RL
(42 bits)
SERIAL USER PROTOCOL

Bits 25 26 27 36 37 39 40 42 43 44 73 74 83 84 85
Serial C/S Cert. No
Country
..... 0 1 011 TTT C Number and or National RL
Code
other Data Use
Notes:
- RL = Auxiliary radio-locating device (01: 121.5 MHz)
- TTT = 010 - float free EPIRB with serial number
- C = C/S Type Approval Certificate Flag:
"1" = C/S Type Approval Certificate number encoded in bits 74 to 83
"0" = other national use
- F = Format Flag ("0" = short message, "1" = long message)
User Location Protocols

bit 26 27-39 40-83 84-85 86-106 107 108-132 133-144
Identification 21-Bit Posit. Position Data to 4
Radio-locating 12-Bit
... 1 ....... Data BCH Data min Resolution
Device BCH code
(44 bits) code Source (25 bits)
Standard Location Protocols

bit 26 27-40 41-64 65-85 86-106 107-112 113-132 133-144
Position Data
Identification 21-Bit Position Data to 4 12-Bit
to 15 min Supplemen
... 0 ....... Data BCH sec Resolution BCH
Resolution tary Data
(24 bits) code (20 bits) code
(21 bits)
Notes:
BCH: Bose-Chaudhuri-Hocquenhem
- 21 bit BCH: The code is used to detect and correct up to three error in
the 25-106 bit
- 12 bit BCH: The code is used to detect and correct up to two error in the
107-144 bit
2-5
Table 2.1.1 Protocol Selection Overview
Beacon type Protocol selection

Remarks
Most countries other than the Cayman Islands require MMSI
based coding. Select this protocol for cases where MMSI or a
Maritime
Call-sign of four to five characters (max six characters) is
Tron 60S required.
Tron 40Smk2 Select this protocol for the Cayman Islands’ ships that are
Serial EPIRB
required to code a Serial number.
Select this protocol for cases where a Callsign of seven
Radio Call sign
characters of four letters and three digits is required.
MMSI Standard
based coding. Select this protocol for cases where MMSI based
Location Long
coding is required.
Serial EPIRB Select this protocol for the Cayman Islands’ ships that are
Standard Location Long required to code a Serial number.
Tron 60GPS
Select this protocol for cases where a Callsign of four to five
Tron 40GPSmk2 Maritime User Location
characters (max six characters) is required.
Serial EPIRB User Select this protocol for cased where coding a Serial number is
Location required.
Radio Call sign Select this protocol for cases where a Callsign of seven
User protocol characters of four letters and three digits is required.
MMSI Standard
based coding. Select this protocol for cases where MMSI based
Tron 40VDR: Location Long
coding is required.
VR-7021F
Serial EPIRB Standard Select this protocol for the Cayman Islands’ ships that are
Location Long required to code a Serial number.
Table 2.1.2 Protocol Types and Those Contained in Menu

Screen,
Positional
Beacon type Available protocol, see Note 1) Input items see
data Note 2)
MMSI/
Maritime (Maritime Use-> MMSI) Callsign: max 6 A
Without
characters
Tron 60S positional
Serial EPIRB Beacon Serial No. or
Tron 40Smk2 data B
(Serial User -> EPIRB with Serial Number) Serial ID Code
Short MSG.
Radio Callsign Radio Callsign
C
(Radio Callsign -> Radio Call Sign) (4 letters + 3 digits)
With MMSI Standard Location Long
MMSI D
Tron 40VDR: positional (Standard Location -> MMSI)
VR-7021F data Serial EPIRB Standard Location Long Beacon Serial No. or
E
Long MSG. (Standard Location -> Serial Number) Serial ID Code
MMSI Standard Location Long
MMSI D
(Standard Location -> MMSI)
Serial EPIRB Standard Location Long Beacon Serial No.
E
(Standard Location -> Serial Number) or Serial ID Code
With
MMSI/
Tron 60GPS positional Maritime User Location
Call-sign: max 6 A
Tron 40GPSmk2 data (User Location -> MMSI)
characters
Long MSG.
Serial EPIRB User Location Beacon Serial No. or
B
(User Location -> EPIRB with Serial Number) Serial ID Code
Radio Call sign User protocol Radio Callsign
C
(User Location -> Radio Call sign) (4 letters + 3 digits)
2-6
Note-1)
In Table 2.1.2, the protocols shown in “C/S S.007 HANDBOOK OF BEACON
REGULATIONS” for Cospas/Sarsat are shown in ( ).
Japan EPIRB Coding Methods
USER PROTOCOLS LOCATION PROTOCOLS

Serial Radio Standard National
Maritime User User Location
Country User Call Sign Location Location
Code EPIRB Serial Number
EPIRB
Radio with Radio Radio Serial Assigned by
MMSI MMSI with Serial MMSI
Call Sign Serial Call Sign Call Sign Number Competent
Number
Number Administration
431,432 Y N N N Y N N Y N N
Panama EPIRB Coding Methods
USER PROTOCOLS LOCATION PROTOCOLS

Serial Radio Standard National
Maritime User User Location
Country User Call Sign Location Location
Code EPIRB Serial Number
EPIRB
Radio with Radio Radio Serial Assigned by
MMSI MMSI with Serial MMSI
Call Sign Serial Call Sign Call Sign Number Competent
Number
Number Administration
351,352,
353,
354,
Y N/A N N/A * * * * * *
355,
356,
357,370
Y: Used. N: Not used. NA: Not available

*: Information not provided in IMO GMDSS Master Plan.
Note-2)
The following protocol screen shows that of “Table 2.1.2.”
Screen A Screen B Screen C
Screen D Screen E
2-7
Screens A and C accept entry of a Radio Callsign. To enter a Callsign of four or five
characters, use the screen A. To enter a Callsign of four letters and three digits, use
the screen C.
A2.2 Maritime User Protocol
The maritime user and the Radio Callsign user protocols may be used for
Beacons that require coding with a Radio Callsign. The Maritime user protocol
may be used for Radio Callsigns of 6 or fewer characters. Radio callsigns of 7
characters must be encoded using the Radio Callsign User protocol.
A2.3 Radio Callsign User Protocol
The Radio Callsign User protocol is intended to accommodate a vessel's Radio
Callsign of up to seven characters, where letters may be used only in the first four
characters, thereby complying with the ITU practice on formation of Radio
Callsigns.
Entries in the protocol information area

• C/S approval no: xxx
A Cospas/Sarsat approval number that differs depending on the type of Beacon
chosen is shown.
• User Beacon serial no.
With 5 in the check box, “the serial number” that has been entered in the Beacon
information area will be automatically taken. Deselecting the check box will
accept entry of “serial ID codes”.
• Beacon number
Give the first EPIRB a Beacon number of “0” and second EPIRB a Beacon
number of “1.”
However, for Tron 40VDR: VR-7021F, enter “15.” For example, to install each
one of Tron 40VDR:VR-7021F and Tron 60GPS, enter a Beacon number of “15”
for Tron 40VDR: VR-7021F and “0” for Tron 60GPS.
2-8
Enter data according to the protocol.
Tron 40VDR: VR-7021F;

Example: selecting “MMSI Standard Location Long”
Example: MMSI Location Protocol
• MMSI number:
Enter a Ship station ID. (6 digits).
• Beacon number:
For Tron 40VDR: VR-7021F,
enter "15."
Tron 60S
Example: selecting “Maritime”
Example: Maritime User Protocol
• MMSI/Callsign:
Enter a Ship station ID. (6 digits)/
Callsign (max 6 characters).
• Beacon number:
Enter "0" for the first unit and "1"
for the second unit.
Tron 60S
Example: selecting “Serial EPIRB”
(Serial User Protocol)
• Serial ID Code:
Enter the Serial ID code.
• C/S approval no:
Automatically set by the Beacon
• Beacon S no:
Selecting the check box will
automatically choose the serial no.
specified in the Beacon information
area as an entry of the "Serial ID
Code" field.
Tron 60S
Example: selecting “Serial EPIRB”
(Serial User Protocol)
• Serial ID Code:
Enter the Beacon’s Serial
number.
• Beacon S no:
Deselecting the check box will
automatically choose the
Serial ID. code as an entry of
the "Serial ID Code" field.
2-9
2.1.5 Battery information area

Enter the expiry date of the battery. This information will not be contained in the
coding data of the Beacon. It will be taken into the “Programming Report.”
Note: the battery will be replaced by SBM (Shore Based maintenance) that is carried
out normally every five year. The Battery service life is five years after it is installed
on condition that the Shelf life specified is not expired.
Table 2.1.3 Battery service life and Shelf life
Shelf life Service life
Type of Beacon Battery type P/N
(month) (year)
Tron 40Smk2 12 5 Lithium (12 V/2900 mAh) P/N 83056
Tron 40GPSmk2 12 5 Lithium (12 V/2900 mAh) P/N 83056
Tron 60S 24 5 Lithium (12 V/2900 mAh) P/N 86225
Tron 60GPS 24 5 Lithium (12 V/2900 mAh) P/N 86225
Tron 40VDR:
18 5 Lithium (12 V/2900 mAh) P/N 87457
VR-7021F
Jotron Beacon have a label showing the battery production date. Start using battery
before the Shelf life is expired. Indicate the Battery service life in the “label: battery
service life indication” supplied as an accessory of the Beacon and apply the label to
the Beacon. Indicate also the name of the Service provider and date(year/month) of
next SBM on the label.
When SBM has been carried out, record the company name that carried out SBM and
the date of next SBM.
Battery production date label

Mark the production date.
Mark the Battery service life
(5 years after Beacon
installed)
AUG 2013
FURUNO-NISHINOMIYA
NEXT SBM: AUG/2019
Battery service life label
Serviced by;
Indicate the name of the
Service provider and date
(year/month) of next SBM
2-10
2.1.6 Vessel information area

Enter information about the ship.
This information will be entered in “the Vessel information” column in “the
Programming Report.”
Selecting the [Send Morse code on 121.5MHz] check box in the MID/Country Code
information area will send the Callsign once by means of Morse code before sending a
121.5 MHz Homing signal.
As for the ship’s name, when the name of vessel is over 15 letters, enter the ship’s
name in “Additional information” column, too.
• Call Sign:
Enter the present Callsign (7 characters).
• Ex Call Sign:
Enter the former Callsign (7 characters)
assigned before the flag was changed.
• Name:
Enter the ship’s name.
• Ex Name:
Enter the former ship’s name before the flag
was changed.
• IMO number:
Enter the IMO number. (7 digits).
• Hull Id Number:
Enter the ship number. (7 characters).
2.1.7 Additional information area

This is an area where you can enter comments.
This information will not be contained in the Coding data of the Beacon. It will be
taken as “Additional information” in the “Programming Report”.
The title of the “Additional information” column differs depending on the type of the
Beacon.
• Tron 40VDR -> VDR/SVDR system info/Additional info
• Other beacons -> Additional information
For Tron 40VDR, enter the following comments. For other beacons, no entry is
required. When the name of vessel is over 15 letters, enter the vessel name as a
comment, too.
For Tron 40VDR: VR-7021F;
FURUNO_VR-7000 SNo.100019-xxxxxx -> Enter DCU S No.
VR-7021F SNo. xxxxxx ; -> Enter the S No. shown in the
Nameplate of the Beacon.
Ship's name is described

when the Ship's name
exceeds 15 characters.
2-11
2.1.8 Coding message information area

“Hex message” and “Hex Code (UNI): (Beacon ID 15 Hex)” including a sync code
that starts with “FFFE2F,” and “Long message data (positional data)” are displayed.
Every time when a data is entered, the display is updated. This information will be
taken in “the Programming Report.”
Indicate the Hex Code (UNI) on the surface of the Beacon.
Beacon message
Indicate this data on the Beacon.
For a Beacon with a built-in GPS,
mark this data.
For a short message not containing positional data e.g. for Tron 40Smk2 or Tron 60S:
• Hex message : Hex code of “28” in length
• Hex code(UIN) : Hex code of “15” in length (bits 25 through 85)
• Long msg data : Blank
For a long message containing positional data e.g. for Tron 40GPSmk2, Tron 60GPS
or Tron 40VDR: VR-7021F:
• Hex message : Hex code of “36” in length
• Hex code(UIN) : Hex code of “15” in length (bits 25 through 85)
• Long msg data : Hex code of “7” in length
The Hex code (UIN) of e.g. Vessel’s name and MMSI/call sign should be indicated on
the Beacon e.g. using a tape printing machine. The label (e.g. printed tape) should be
covered with the protective transparent sheet, an accessory of the equipment.
Indicate e.g. Vessel Name,

MMSI/Callsign.
Protect the label with a
transparent sheet.
2-12
Information)
To decode Hex codes (UIN), see the following Cospas/Sarsat URL:
http://www.cospas-sarsat.int/en/beacon-decode-program
Example: decoding a long message Example: decoding a short message
2-13
2.2 [Program], [Read] and [Report] buttons
2.2.1 [Program] button

Using [Program] button, the data edited by using the Beacon Programmer can be
coded.
Entering all data required will change the color of the [Program] button from “red” to
“green”.
If invalid data are contained, or part of the required data is missing, an error message
will appear in “red” at the bottom of the screen.
For example, if the required entry for MMSI is missing, an error message “Invalid
MMSI” will appear.
Error message field
2-14
Coding procedure
1. Click on [Program] button. A pop up screen “Coding in progression (xx %)” and
“photos for coding operation” will also appear.
To encode, make the PRU-50 contact (touch) with the Beacon. Note that the
orientation of the PRU-50 relative to the surface of the unit is important.
Note)
If [Connected] or [USB power available] is displayed in red, no connection has
been made between the PC and PRU-50. Select [Options] -> PRU... from the
menu bar, and check that the PRU-50 connected COM port is selected.
The green lamps lighting continuously

means that PRU-50 is connected
with PC properly. The green lamps
blinking (red) means that PRU-50 is
not connected properly.
2. Make the PRU-50 contact with the Beacon in place at the position marked with
“{{.” Orient PRU-50 as shown in the photo.
TEST
Example: for Tron 40VDR: VR-7021F
2-15
3. Slide the operation switch on the Beacon to the right and keep it at [TEST]
position.
When the progression indicator bar has reached 100% several times, the test is
completed.
When the test is completed, a screen “Data programmed data in EPIRB/PLB” will
appear. Return the switch to [RADY] position.
Note)
If the RPU-50 is drawn away from the Beacon before coding is completed, the
progression indicator bar will cease. In this case, return the operation switch
to [READY] position and restart programming.
Coded data
2-16
4. Then work on the screen “Data programmed data in EPIRB/PLB.”

For the use of [Save PDF] and [Close] buttons, see the figure below.
For the use of the “Database” menu, see Page 2-41.
The coded data can be saved as a PDF file of “Programming Report.” The file can
be printed out. The filename is determined after the ship’s name specified in “the
Vessel Information” field and Hex code (UIN). For example, it is “FURUNO
205C3C481EFFBFF.pdf.”
File handling;
Change the file name and format as “Beacon serial number._vessel name_Hex
code(UNI).pdf” (not including “”) and follow the procedure (Attaching to SMS).
Ex. “00082_FURUNO_205C3C481EFFBFF.pdf”
Press Press
[Save PDF] File save operation [Close]
Save Cancel
PDF file name;
Saved
Beacon S No.+Ship
name+Hex code (UIN). Pop-up: No Pop-up:
Open PDF in external viewer? Store program data in beacon database?
Yes No
Yes
Display pdf file Close Save in [Database] menu Closed pop-up

(No action)
Fig. 2.2.1 Overview of post-coding operation on the screen
Important)
Handle Programming Report data following the procedure. Copy the file and give it to
the vessel for storage. In case of Tron 40VDR: VR-7021F, attach “Programming
Report” and “JOT” file to SMS, too. For JOT file handling, see the page 2-44.
Note)
[Miscellanous data] of Programming Report is shown as “Beacon has been
programmed and verified!”. That indicates Programming Report is created using a
“Programming” function.
Indication of Miscellanous Data;

Beacon has been programmed and verified!
Example: Programming Report
2-17
2.2.2 [Read] button

Using [Read] button, the coded data can be read out, and then can be saved as a PDF
file of “Programming Report.” The file can be printed out.
How to read out:
1. Click on [Read] button. Slide the operation switch on the Beacon to the right and
keep it at [TEST] position. When the progression indicator bar has reached 100%
several times, the read out operation is completed.
When the operation is completed, a screen “Data programmed data in EPIRB/PLB”
will appear. Return the switch to [RADY] position.
Note)
If the RPU-50 is drawn away from the Beacon while reading is in operation,
the progression indicator bar will cease. In this case, return the operation
switch to [READY] position and restart “reading.”
Coded data (read out)
2-18
2. Then work on screen “Data programmed data in EPIRB/PLB.”

Press Press
Save Cancel
Saved
PDF file name;
Beacon S No.+Ship
Pop-up: No
name+Hex code (UIN). Open PDF in external viewer? Sub window closed
Yes
Display pdf file Close
Fig. 2.2.2 Overview of post-reading operation on the screen
Note)
[Miscellanous data] of Programming Report is shown as “Data read from beacon!”.
That indicates Programming Report is created using a “Read” function.

Data read from beacon!
2-19
2.2.3 [Report] button

Using [Report] button, it is possible to create a report of the data being edited by the
Beacon Programmer.
How to create a report:

1. Click on [Report] button.
A screen “Data programmed data in EPIRB/PLB” will appear. The data shown
here are those to be encoded.
Data to be encoded are

displayed.
2-20
2. Then work on the screen “Data programmed data in EPIRB/PLB.”

Press Press
Save Cancel
PDF file name; Saved
Beacon S No.+Ship
name+Hex code (UIN). Pop-up: No
Open PDF in external viewer? Sub window closed
Yes
Display pdf file Close
Fig. 2.2.3 Overview of post-reporting operation on the screen
Note)
[Miscellanous data] of Programming Report is shown as “WARNING: Report mode
only – beacon must be programmed!”. That indicates Programming Report is
created using a “Report” function.

WARNING: Report mode only - beacon must be programmed!
2-21
2.3 Menu bar
2.3.1 Menu tree

Table 2.3.1 List of menus
Main Sub-Menu 1 Sub-Menu 2 Sub-Menu 3 Remarks

Tron 30SmkII
Tron 40S
Tron 40SmkII
Tron 40GPS
Tron 40GPSmkII
A Beacon selected by
Tron 45S
Option ->Beacon/Brackets
Tron 45SX
-> Beacon allowed is
Tron 60S displayed.
Tron 60GPS
Tron SVDR capsule
(30S capsule)
Tron 40VDR capsule
Beacon (40S capsule)
Program Ctrl+P Same as [Program] button
Read Ctrl+R Same as [Read] button
Programming
Report(Jotron) Same as [Report] button
Ctrl+E
Programming Report(UK, The registration form
US, Australia or NZ applicable for UK, US,
Registration) Australia or NZ is displayed.
Ctrl+U (MID shall be the same.)
A report of data other than
Save in database(without
those coded is created and
programming) Ctrl+S
saved.
Exit Alt+X
FB-1
FB-2 Tron 30Smk II
FB-3
FBR-3 Tron 30SmkII, SVDR
Bracket
FB-4
Choose for Tron 40S,
FBH-4
40Smk II, 40GPS and
FB-5
40GPSmk II
FB-6
2-22
FBH-3 Tron 30Smk II

MB-1 Tron 30Smk II
MB-3 Tron 30Smk II
MB-4 Choose for Tron 40S,
MB-5 40Smk II, 40GPS and
MB-6 40GPSmk II
MB-45S Tron 45S
MB-45SX Tron 45SX
FB-40VDR Tron 40VDR
FB-60 Tron 60S, 60GPS
MB-60 Tron 60S, 60GPS
Maritime Choose for Tron 30Smk II,
40S, 40Smk II, 45S, 45SX
Serial EPIRB
and 60S.
Choose for Tron 45S and
Serial PLB
45SX.
Choose for Tron 30Smk II,
Radio Callsign 40S, 40Smk II, 45S, 45SX
and 60S.
Protocol MMSI Standard Location
Choose for Tron 40GPS,
Long
40GPSmk II, 60GPS, SVDR
Serial EPIRB Standard
and 40VDR.
Location Long
Marin User Location
Serial EPIRB User
Choose for Tron 40GPS,
Location
40GPSmk II and 60GPS.
Radio Callsign User
Protocol
This is to check MMSI and
Programming Perform ID Check Beacon number. while
coding is in operation.
Maritime user
Protocol
Serial User Protocol
(Maritime)
Protocols
Serial User Protocol
allowed
(PLB)
Options Radiocallsign User
Program/Reports.. Protocol Affects the Protocol menu;
Cont'd Test Protocols optional protocols depend
MMSI Standard on the type of the Beacon
Location chosen.
Serial EPIRB
Location Standard location
protocols Maritime User
allowed Location
Serial user Location
Radio Callsign User
Location
2-23
After coding, the Serial

Always blank number of the Brackets is
blanked out.
Beacon After coding, the Serial
serial Increment by 1 number of the Brackets
numbers increases by one.
After coding, the Serial
Leave unchanged number of the Brackets
remains unchanged.
Bracket Always blank The same function as that
serial Increment by 1 for the Beacon Serial
Beacon/Brackets.. number Leave unchanged numbers
Tron40S
Tron40S mk II
Tron40GPS
TronGPS mk II
Tron40VDR The Beacon type chosen
Beacon
Tron60S here affects the Beacon
allowed
Tron60GPS menu.
Tron30S mk II
Options Tron45SX
TronSVDR capsule
L-3 FFSVR
Affects "MID/Country Code"
Use default country in the Beacon Programmer
list(all countries) screen; all MIDs are
displayed.
Countries Affects "MID/Country Code"
in the Beacon Programmer
Use custom country
screen; MIDs chosen from
Countries.. list(select countries)
the Edit selected country list
are displayed.
Displays the default MID list.
All country list (the list is displayed only
Edit selected
when PRU-50 is connected)
country list
Selected Displays MIDs chosen from
countries(custom) the default MID list.
Configures the COM port
PRU
PRU connection between PRU-50
comport
and PC.
PRU parallel
PRU30
port
Enter the name of the
creator of the Programming
Report.
Operator Enter operator initials (Same as the screen that
pops up when the Beacon
Programmer S/W is booted
up.)
2-24
List of the Beacons that

Beacon List
have been coded
Erases or reports a Beacon
Beacon
list
View database
Import from
Database Import
JOT files
Export to .txt file,
Export
Export to .JOT file
Send Email, Copy
Jotron report(generate)
to Disk
Keywords
Displays instruction manuals
Contents Text-based
of the Beacon Programmer
search
Help A screen used for
registering the Beacon
Register
Programmer S/W with
Jotron; not used
2-25
2.4 Details of the menus
2.4.1 Beacon menu

2.4.1.1 Tron 40S~Tron40VDR(40S Capsule)
Select a Beacon type that is to be coded. The Beacon selected will affect the Beacon
information area in the Beacon Programming screen.
2-26
The [Beacon] menu will include beacons chosen from the “Beacon allowed” list. To
access to the list, select [Option] -> Beacon/Bracket...
Wrong programming operations will lead to the following “Warning message”. Choose
proper Beacon types.
2.4.1.2 Program
This is the same as [Program] button. See “2.2.1 [Program] button” in Page 2-14.
When “Program” is not displayed (gray), the required data are yet to be entered.
And the [Program] button is in red.
2.4.1.3 Read
This is the same as [Read] button. See “2.2.2 [Read] button” in Page 2-18.
2-27
2.4.1.4 Program Report (Jotron)

This is the same as [Report] button. See “2.2.3 [Report] button” in Page 2-20.
2.4.1.5 Programming report (UK, US, Australia or NZ registration)

Selecting UK (232-235), USA (338, 366-368), Australia (503) or New Zealand (512)
for MID/Country Code will allow the PC to create a PDF file of the country’s
“Registration form” containing the input data. The PDF file can be viewed.
The following figure shows the “Registration form” of each country.
Programming report (UK, US, Australia or NZ registration) -> “Save”-> a pop up
massage “Open PDF in external viewer” will appear. Clicking on “Yes” will open the
“Registration form” of the country chosen.
UK Registration form
AU, NZ Registration form USA Registration form
2-28
2.4.1.6 Save in database (without programming)

When “Save in database (without programming)” is not displayed, the required data
are yet to be entered.
The screen “Data programmed data in EPIRB/PLB” will appear normally after coding
operation. However, if this function has been selected, the screen can be viewed even
if the coding operation is not performed.
Therefore, the data edited/obtained via the Beacon Programmer screen can be used for
creating reports and saved in the database.
2.4.2 Bracket menu

Selecting a Beacon from the [Beacon] menu will change the [Bracket] menu so that it
can correspond to the Beacon selected and automatically select an appropriate type of
Bracket as an entry of the Bracket information area.
If the actual Bracket is different from the entry, reselect a correct type of Bracket from
the “Bracket” menu.
Beacon type chosen Bracket types contained in the Bracket menu

Tron 30SmkII FB-1, FB-2, FB-3, FBH-3, MB-1, MB-3
Tron 40S FB-4, FBH-4, FB-5, FB-6, MB-4, MB-5, MB-6
Tron 40SmkII FB-4, FBH-4, FB-5, FB-6, MB-4, MB-5, MB-6
Tron 40GPS FB-4, FBH-4, FB-5, FB-6, MB-4, MB-5, MB-6
Tron 40GPSmkII FB-4, FBH-4, FB-5, FB-6, MB-4, MB-5, MB-6
Tron 45S MB-45S
Tron 45SX MB-45SX
Tron 60S FB-60, MB-60
Tron 60GPS FB-60, MB-60
Tron SVDR(30S Capsule) FBR-3
Tron 40VDR(40S Capsule) FB-40VDR
▪ FB-xx, FBH-xx : Float-Free Bracket type

▪ MB-xx : Manual Bracket type
2-29
2.4.3 Protocol menu

Select a Protocol. Enter MMSI, Serial ID Code, Beacon Serial number. or Callsign.
Most countries, except certain ones, require MMSI to be entered.
If choosing a Beacon without a built-in GPS, such as Tron 60S, the menu of protocols
will change so that inapplicable protocols are excluded from the menu. This protocol
supports short messages.
• Maritime: Maritime user protocol
• Serial: Serial user protocol
• Radio Callsign: Radio Call sign protocol
Selecting the “Location protocol allowed” check box for a protocol will cause the
protocol to be included in the menu of protocols applicable for Beacons with a built-in
GPS such as Tron 60S GPS and Tron 40VDR: VR-7021F.
This protocol supports long messages.
• MMSI Standard Location Long
• Serial EPIRB Standard Location Long
For Tron 60GPS For Tron 60S For Tron 40VDR:

VR 7021F
Information)
To select a protocol to be included in the menu, select [Option] -> Program/Reports..
Then select “Protocol allowed” or “Location protocol allowed.”
See “2.4.4 Options menu” in Page 2-31.
2-30
2.4.4 Options menu

2.4.4.1 Program/Report..
This is to configure programming environment. Deselect “Test Protocols” check box
located in the “Protocol allowed” area.
Deselect “Test Protocols” check box.
1) Programming -> Perform ID Check

Select “Perform ID Check” check box.
For the Maritime user protocol or MMSI Standard Location Long protocol, if you
attempt to program the “MMSI” or “Beacon Number” of a formerly programmed
Beacon, a “Warning message” will appear.
In this case, check the MMSI and Beacon number.
2-31
When the “Warning message” is given, pressing [Ignore] button to continue

programming will cause the following warning message to appear.
Check the MMSI and Beacon number and the Beacon’s serial number as well. And
redo programming.
2) Report
▪ Print graphic
To use a slow printer to print out the Programming Report, choose “Disable.”
2-32
▪ Beacon History
Selecting this check box will add a “Beacon history” field to the Programming Report.
The field can contain “date (month and year) information and Beacon’s serial no.” to
show that programming has been already performed.
▪ Create "txt" Report

A report is created as a text file.
After coding, selecting [Database] -> Jotron report (generate) will open the “Save text
file” screen. Using this screen, save the file.
Note)
The file of this file format does not use it.
2-33
3) Protocols allowed
Enter MMSI, Serial ID Code, Beacon Serial number or Callsign. Selecting this check
box will affect the menu of protocols applicable for Beacons without a built-in GPS
such as Tron 60S so that the protocol is included in the menu.
This changes the environment for choosing protocols that support short messages
“without positional data.”
Shown below is a list of options contained in the Protocol menu.
• Maritime User Protocol -> Maritime
• Serial User Protocol (Maritime) -> Serial EPIRB
• Serial User Protocol (PLB) -> Serial PLB
• Radio Call sign User Protocol -> Radio Callsign
4) Location protocols allowed

Enter MMSI, Serial ID Code, Beacon Serial number or Callsign. Selecting this check
box will affect the menu of protocols applicable for Beacons with a built-in GPS such
as Tron 60SGPS and Tron 40VDR: VR-7021F so that the protocol is included in the
menu. This changes the environment for choosing protocols that support long
messages “with positional data.”
Shown below is a list of options contained in the Protocol menu.
• MMSI Standard Location -> MMSI Standard Location Long
• Serial EPIRB Standard Location -> Serial EPIRB Standard Location Long
• Maritime User Location -> Maritime User Location
• Serial User Location -> Serial EPIRB User Location
• Radio Call sign User Location -> Radio Call sign User Protocol
Note)
For Tron 40VDR: VR-7021F, only MMSI Standard Location and Serial EPIRB
Standard Location are selectable.
This is define in IEC61996-1 ed2.
5.2.2.3 Locating transmitter
The float-free capsule shall be capable of resolving and transmitting its last
received Position or its current position with a minimum accuracy of 4 s of arc
and conform to the relevant requirements of IEC 61097-2.
2-34
2.4.4.2 Beacon/Brackets...
This is to configure the procedure for handling Beacon and Bracket numbers and
configure the Beacons list contained in the Beacon menu.
1) Beacon serial number

This is to configure the post-coding procedure for handling the Serial number of “the
Beacon.” Choose one of the following options. However, you had better choose
“Leave unchanged.”
• Always blank
After coding, the Serial number of the Beacon is “blanked out.”
• Increment by 1
After coding, the Serial number of the Beacon increases “by one.”
• Leave unchanged
After coding, the Serial number of the Beacon “remains unchanged.”
2-35
2) Bracket serial number

This is to configure the post-coding procedure for handling the Serial number of the
Bracket.
Choose one of the following options. However, you had better choose “Always blank.”
• Always blank
After coding, the Serial number of the Bracket is “blanked out.”
• Increment by 1
After coding, the Serial number of the Bracket increases “by one.”
• Leave unchanged
After coding, the Serial number of the Bracket “remains unchanged.”
3) Beacons allowed
Select Beacon types to be contained in the Beacon menu. You had better choose
beforehand the types of Beacon for which coding applies.
2-36
2.4.4.3 Country
Select “MID/Country Code” options to be included in the pull down menu.
You had better choose beforehand MIDs that you will use frequently.
1) Countries
• Use default country list (all countries)
“The MID/Country Code” pull down menu list contains all MID lists.
Information)
The installed PRU-50 S/W will be saved as a name “Jotron -> PR40” in the
Program File folder. This folder includes a Country.txt file that contains “the
default country list.”
New MIDs should be added to the file.
2-37
• Use custom country list (select countries)

Use this for selecting MIDs to be included in “the MID/Country Code” pull down
menu list. Use [>] button to move your desired MID from the [All countries
(default)] box in “the Edit selected country list” in the Country list option screen to
the [Selected countries (custom)] box.
To delete an MID, select the MID and return it to the [All countries (default)] box
using [<] button.
2-38
2.4.4.4 PRU
Configure the serial connection between PRU-50 and PC.
Select the number of the COM port used for connecting the PRU-50 from the pull
down menu.
To check the COM number of the PRU-50 driver that has been installed in the PC,
open the device manager and see “USB Serial Port.”
Note)
While the PRU-50 is not connected to the PC, pressing [Programming] and [Read]
buttons will pop up the following window and the “Connected” button displayed
in “red.” While the PRU-50 connection has been established, the button is
“green.”
2.4.4.5 PRU-30
Not used
2-39
2.4.5 Operator menu

Opening the [Operator] menu will pop up a screen “Enter operator initials.” The screen
pops up also when the Beacon Programmer S/W is booted up.
The name entered here will be automatically taken as the entry of the “Program by:”
field in the “Data programmed data in EPIRB/PLB” in the Programming Report.
2-40
2.4.6 Database menu

2.4.6.1 View database
It is possible to retrieve data from the database, display it in the “Data programmed
data in EPIRB/PLB” screen and use it for creating a Programming report. The data can
be saved as a text file.
1) [Beacon List] tab

The data list stored in PR-40: Programming Programmer will be displayed. To create a
Programming Report etc., select the relevant data.
2) [Beacon] tab
Data chosen from the Beacon list will be displayed. To delete the data, click on [Erase]
-> [OK]. To create a Programming Report, click on [Report] -> [OK]. “Data
programmed data in EPIRB/PLB” screen will appear. Press [Save PDF] button to
create a Programming Report.
Note)
[Miscellanous data] of Programming Report is shown as “Data from database,
programmed yyyy/mm/dd”. That indicates Programming Report is created using a
“Report” function of Database menu.
Press [Save PDF] button to

create a Programming Report.
[Report]
2-41
3) [Import from JOT file] tab

For example, it is possible to import a JOT file containing code data into a database in
the Beacon Programmer that allows you to view the data.
Procedure)
1. Select “C” drive -> Program Files -> Jotron -> PR40 -> Report folder and place the
JOT file containing the code data in the folder.
2. Select the View database from the [Database] menu.
3. Click on the “Import from JOT file” tab and select the Report folder in which the
JOT file is placed.
4. Click on [Import] button.

5. The [BeaconList] tab opens. This contains a list containing the JOT files imported.
2-42
6. Click on the Beacon that you want to open. The [Beacon] tab opens. This contains
the code data.
Code data
Information to be
contained in the
Additional Information
column in the
Programming Report can
be entered.
7. To create a report, click on [Report] button. A screen “Data programmed data in

EPIRB/PLB” will appear.
8. To create/display a Programming Report (PDF file), click on [Save PDF] button

and follow the instructions shown in the screen.
Note)
[Miscellanous data] of Programming Report is shown as “Data from database,
programmed yyyy/mm/dd”. That indicates Programming Report is created
using a “Report” function of Database menu.

Data from database, programmed yyyy/mm/dd
2-43
4) [Export] tab
It is possible to save the data chosen via “the Beacon List Tag” in the text file or JOT
file format.
• [Export to .txt file] button

Using “Export to .txt file,” you can save the data chosen from the Beacon List as a text
file in the specified folder in the PC.
To save a file, give it a filename by substituting your appropriate characters for “*” in
the filename format of *.txt.
• [Export to .JOT file] button

Using “Export to .JOT file,” you can save the data chosen from the Beacon List as a
JOT file at the specified directory in the PC.
To save a file, give it a filename by substituting your appropriate characters for “*” in
the filename format of “*.JOT.” You may use the “Serial no. of the Beacon + Ship’s
name.jot” as a filename. ex; 00082_FURUNO_jot
Important)
For the handling of JOT file, follow the procedure (Attaching to SMS) as
Programming Report. JOT file format is used for sending Programming Report to
Jotron via e-mail, but currently, there is no need to send the report to Jotron.
2-44
2.4.6.2 Jotron report(generate)
1) [Send Email] button

This button is used for sending a Jotron file (.JOT file) by e-mail. However, presently
you are not required to send these files to Jotron.
2) [Copy to Disk] button

Use this button to copy a Jotron file (.JOT file) to the specified folder.
2-45
2.4.7 Help menu
2.4.7.1 Contents
Displays instruction manuals of the Beacon Programmer
Keywords-based search screen
Text-based search screen
2-46
2.4.7.2 Register
“PR40 REGISTRATION” screen appears also when the Beacon Programmer is first
booted up.
This screen is used for registering a Beacon Programmer. However, you may not
have to use this screen since registering Beacon Programmers with Jorton is presently
not required. However, some inputted data is reflected in Programming report.
The following input data are those necessary for registering

with Jotron though they are presently not used. However,
some inputted data is reflected in Programming report.
▪ Name: Enter the name of the PR40 Rejistration person.
▪ Company: Enter the name of the company.

(Max. 25 characters, reflected in “Programming report”)
▪ Jotron dealer(Furuno) number: Enter 15050.

(Reflected in “Programming report”)
▪ Email for updates: Entry unnecessary.
After all entries are made, press [Register later].
2-47
3.1 Coding procedure
After coding, make sure that the label is stuck on the surface of the Beacon. For the
handling of Programming report and JOT file, follow the procedure; attaching to SMS.
Table 3.1.1 Overview of entries for coding
Input Info.
Setup item Value Remarks
area
Version 000
Serial number Enter the Beacon’s serial number
Beacon Beacon’s id consisting of [Version
(select from Label Entry unnecessary information + Serial number] is
the Beacon automatically generated
menu) For replacement, select the Beacon
Replaces
For new installation, select "None" from the menu; if a Beacon other than
beacon
Jotron make is used, select "Other."
Version Entry unnecessary: Blank
For Tron 40VDR: VR-7021F only,
Bracket The Serial number of Tron 40VDR is
Serial number enter this data; for other Beacons,
(select from indicated on the VDR Docking Module
no entry shall be made
the Bracket
Beacon’s id consisting of [Version
menu)
Label Entry unnecessary information + Serial number] is
automatically generated
Call Sign Enter the Callsign. Uppercase letters
EX Call Sign Enter the former Callsign. For changing flag states
Uppercase letters (More than 15
Name Enter the name of the ship.
Vessel char., input to Additional info. column)
information EX Name Enter the former name of the ship. For changing flag states
IMO number Enter the IMO No. 7 digits
Enter the Ship No. specified by the
Hull Number
shipyard.
MID Select MID (three digits) MID is the first three digits of MMSI
MID/Country Send morse If a Callsign has been entered in
Code code on the Vessel information column, Tron 40VDR is not selectable
121.5 MHz select this check box.
MMSI number Enter a ship ID. (6 digits). For MMSI Location Protocol
For Maritime User Protocol (Most
MMSI/Callsign Enter a ship id. (6 digits) or Callsign
countries require MMSI to be shown)
Protocol Basically enter the Beacon’s Serial
Serial ID code For Serial Protocol
(select from number
the Protocol Enter a Callsign of four letters and
Radio Callsign For Radio Callsign Protocol
menu) three numerals
“15” for Tron 40VDR "1" for second unit for Beacon other
Beacon number
“0” for other than Tron 40VDR than Tron 40VDR
Test Protocol Deselect the check box.
Shelf life) Tron 40VDR: 1.5 years
The battery service life is five years
Battery Expiry date Tron 60S/60GPS: 2 years
after it is installed
Tron 40S/40mk2/40GPS mk2: 1 year
For Tron 40VDR only, enter the
Additional following information.
info. FURUNO_VR-7000 SNo.xxxxx
VR-7021F SNo. xxxxxx
Note) Tron 40VDR: VR-7021F
3-1
3.1.1 Edit the Coding data

Procedure)
1. Boot up Beacon Programmer. A screen “Enter operator initials” will pop up. Enter
the name of the person in charge for coding. This information will be taken in the
Programming Report.
The following “COSPAS/SARSAT Beacon Programmer” screen will appear.
Menu bar Bracket information area
Program, Read and

Report buttons
Beacon 2.
information area
Fig. 3.1.1 Beacon Programmer (Ver3.8.2) screen

Battery information area
Vessel information area
MID/Country Code
information area Protocol information area
Coding information area Additional information area
Table 3.1.1 Screen of Beacon Programmer (Ver.3.8.2)
3-2
2. Select a type of Beacon to be coded from the Beacon menu.
3. Enter “Beacon information”
x Version
Enter “000.” See the following Versions list.
Beacon type Beacon Version

Tron 40VDR: VR-7021F 000
Tron 40Smk2 000
Tron 40GPSmk2 000
Tron 60GPS 000
Tron 60S 000
3-3
x Serial number
Enter the Serial no. of the Beacon.
Note)
For Tron 40VDR: VR-7021F, this is not the Serial numbero. shown in
the nameplate of “VR-7021F.”
Note: this is not the Serial

No. shown in the
nameplate of VR-7021F. Serial No.
x Label
Entry is unnecessary. Automatically created using the entries of “Version” and
“Serial number,” and marked as “Version + Serial number.”
x Replace beacon
This is an event record of replacement of the Beacon. If this is a new
installation, choose “None.” If this is a replacement, choose a Beacon type
from the pull down menu.
For example, if KANND Beacon is to be replaced, choose “Other.”
4. Select a Bracket type from the [Bracket] menu. To know the type, see the
information marked on the surface of the Bracket.
Beacon type Bracket Type

Tron 40VDR:
FB-40VDR
VR-7021F
Tron 40SMK2 FB-6
Tron 40GPSMK2 FB-6
Tron 60GPS FB-60
Tron 60S FB-60
5. Enter “Bracket information.”

Beacon Bracket Bracket Serial
Type Type Version number
Marked on
Tron 40VDR:
FB-40VDR the Docking
VF-7021F
N/A: Module
Tron 40Smk2 FB-6 Entry
N/A:
Tron 40GPSmk2 FB-6 unnecessary
Entry
Tron 60GPS FB-60
unnecessary
Tron 60S FB-60
3-4
x Version
This Version information for the Bracket is not required to be entered.
x Serial number
This is an entry field for Bracket Serial number. However, no entry is
For Tron 40VDR: VR-7021F, enter the Serial number of the Bracket.
The Serial number is marked on the surface of the VDR Docking
module.
x Label
Entry is unnecessary. Automatically created using the entries of “Version”
and “Serial number,” and marked as “Version + Serial number.”
6. Enter “Vessel information.”
x Call Sign: Enter the Callsign.

x Ex Call Sign: Enter the former Callsign available
before the flag was changed.
x Name: Enter the ship’s name
x Ex Name: Enter the former ship’s name before the
flag was changed.
x IMO number: Enter the IMO number.
x Hull Id Number: Enter the Ship number.
7. Select “MID/Country Code” from the pull down menu.

If you have entered the correct Callsign as “Vessel Information,” mark the check
mark in the [Send morse code on 121.5 MHz] box.
However, if you have selected Tron 40VDR: VR-7021F, this box is unavailable.
Tron 40VDR Beacons other than Tron 40VDR
3-5
8. Select a protocol from the Protocol menu. Note that the options contained in the
menu depend on the type of the protocol chosen. The following figure is applicable
for Tron 40VDR: VR-7021F.
For most countries, follow the following instructions for selecting protocols:
x Beacon with GPS: select “MMSI Standard Location Long” -> Enter MMSI
x Beacon without GPS: select “Maritime” -> Enter MMSI
For the Cayman Islands, since it is required to code a Serial No., follow the
following instructions for selecting protocols:
x Beacon with GPS: select “Serial EPIRB Standard Location Long”
x Beacon without GPS: select “Serial EPIRB”
9. Enter in the Protocol information area. Setup items depend on the type of the
protocol chosen in the Step-8 above.
For a protocol of “Maritime” or “MMSI Standard Location Long”;
Beacon with GPS: Tron 40VDR, Tron 60GPS etc. Beacon without GPS: Tron 40Smk2, Tron 60S etc.
MMSI Standard Location Long Maritime
x MMSI
Enter the Ship ID. that is represented by the fourth and later digits of the MMSI
of nine digits.
x Beacon number
For Tron 40VDR: VR-7021F, enter “15.” For other than Tron 40VDR:
VR-7021F, enter “0.” For a second unit, enter “1.”
x Test Protocol
Deselect the check box.
3-6
For a protocol of “Serial EPIRB” or “Serial EPIRB Standard Location Long”;
Beacon with GPS: Tron 40VDR etc. Beacon without GPS: Tron 60S etc.
Serial EPIRB Standard Location Long Serial EPIRB
x Serial ID code
Basically enter the Beacon’s Serial number.
x Use Beacon Serial number, Beacon Serial number
If the check box is checked, the Beacon’s “Serial number” entered as the
“Serial ID code” in the step-3 will be automatically taken, not allowing
entering the Serial ID code here.
x Test Protocol
Deselect the check box.
10. Enter battery information.

Enter the Battery service life (expiration date). If the Shelf life has not expired, the
Battery service life (expiration date) should be five years since the date of coding.
This should be the case for replacing battery. If the Shelf life of the new battery has
not expired, the Battery service life (expiration date) should be five years since the
date of coding (replacement).
Check that the above mentioned “Battery service life” entry agrees with the
“Battery service life” shown in the label stuck on the battery.
11. Additional Information column:

For Tron 40VDR: VR-7021F, enter “FURUNO_VR-7000 SNo.100019-xxxx” in a
row and “VR-7021F SNo. xxxxxx” in the next row. For other than Tron 40VDR:
VR-7021F, no entry is required. For other Beacons, no entry is required. When the
name of vessel is over 15 letters, enter the vessel name as a comment, too. For
example, M/V PACIFIC ADVENTURE.
For Tron 40VDR:

FURUNO_VR-7000 SNo. 100019-xxxxxx -> Enter DCU S No.
VR-7021F SNo. xxxxxx ->
Enter the S No. shown in the nameplate of the beacon.
3-7
3.1.2 Coding
Procedure)
1. Click on [Program] button.
If [Connected] or [USB power available] is displayed in red, no connection has
been made between the PC and PRU-50. Select [Options] -> PRU.. from the menu
bar, and check that the PRU-50 connected COM port is selected.
With the Green lamps lighting

continuously, PRU-50 is
connected properly. With the
Green lamps blinking, PRU-50 is
not connected properly.
2. Make the PRU-50 contact with the Beacon in place at the specified position. Orient
PRU-50 as shown in the photo.
TEST
For Tron 40VDR and Tron 40Smk2
TEST
Place the PRU-50 so that it

covers the dent.
Tron 60GPS
3-8
3. Slide the Operation switch on the Beacon to the right and keep it at “TEST”
position. When the progression indicator bar has reached 100% several times, the
coding is completed. If you drew away the PRU-50 or operation stopped halfway,
redo coding from the beginning.
When the operation is completed, a screen “Data programmed data in EPIRB/PLB”
will appear. Return the switch to RRADY position.
3.1.3 Create Programming report

Procedure)
1. When the operation is completed, a screen “Data programmed data in EPIRB/PLB”
will appear.
Coded data
2. Click on [Save pdf].

On the screen that appears, save the coded data. The filename is determined
automatically after the Vessel’s name specified in the Vessel Information field and
Hex code (UIN).
However, you should modify the name by adding the Serial number of the Beacon
for the sake of management. For example, it can be “00082 FURUNO MARU
205C3C481EFFBFF.pdf.”
3-9
3. On a screen “Open PDF in external viewer” that pops up, click on [Yes].
4. A PDF file of “Programming Report” will appear.

For the handling of Programming Report, follow the procedure (Attaching to
SMS).And the coded programming reports should be handed over to the ship’s
owner/operator.
5. Together with “the Programming Report”, a window “Store program data in

Beacon database” will pop up. Click on [Yes].
3-10
3.1.4 Create JOT file (Only Tron 40VDR: VR-7021F)

Coding data can also be created by the JOT format other than the “Programming
Report” format, but data contents cannot be checked even if the JOT file is opened.
When using Tron 40VDR: VR-7021F, handle this file as Programming Report file,
following the procedure (Attaching to SMS).
Procedure)
1. After completing the step-5 in Section “3.1.3 Create Programming Report,” select
“View database” from the [Database] menu.
2. Select the data that has been coded, click on “Export” tab and then click on [Export
to JOT file] box.
3. On the screen that appears, save the data using a filename format of “*.jot.”
To save a file, give it a filename by substituting your appropriate characters for “*”
in the filename format of “*.JOT.” You may use the “Serial no. of the Beacon +
Ship’s name.jot” as a filename. ex; 00082_FURUNO_jot
4. For the handling of JOT file, follow the procedure (Attaching to SMS) as
Programming Report.
3-11
3.2 Beacon Test

3.2.1 Self test
Perform a Beacon Self test. The Self test procedure is the same for all types of
Beacons.
406 MHz
Test ON 406 MHz
Test Msg Test ON
5-8s Test Msg
5-8s
121.5 MHz
Sweep Sig.
Tron 60S, Tron 60GPS, Tron 40SMK2, Tron 40GPSmk2
Tron 40VDR
Fig. 3.2.1 Self test
Self test Procedure)

1. Remove the Beacon from the Bracket.
2. Slide the operation SW from [READY] to [TEST] position and keep the position for
about 15 seconds.
3. OK if the LED at the tip of the antenna is flashed one time.

If the test found the Beacon defective, the LED at the tip of the antenna is flashed on
multiple times. The number of repeats of the LED being flashed on depends on the
type of errors as shown below.
Number of
Fault indication;
flashes
1 No Error, the unit is OK
2 Low power, 406 MHz transmitter
3 Low battery voltage
4 Low power, 121.5 MHz transmitter
5 Transmitter failure, 406 MHz
6 Transmitter failure, 121.5 MHz
7 EPIRB module not programmed or programming not completed.
4. After the test, return the SW to [READY] position.
3-12
GPS test procedure)

For Tron 40VDR: VR-7021F, Tron 60GPS (with GPS), the GPS test (up to 2 minutes)
should be limited to max 60 times for saving battery. The GPS test should therefore be
performed once a month. Note that if it becomes 60 times or more, it will become the
normal self test.
Procedure)
1. Slide the operation SW to [TEST] position twice within a period of 3 seconds.
2. A short beep is heard repeatedly at three seconds intervals until the GPS determines
the position.
3. OK if two beeps are heard.
If it fails to measure the position, five beeps are heard.
If 10 beeps are heard, the maximum limit of the number of repeats of the GPS test
(60 times) has been exceeded.
3.2.2 EPIRB Tester: BT-100A, check the Power and Frequency

Using EPIRB Tester: BT-100A, check errors in sending power and frequency, and
errors contained in the result of coding.
Procedure)
1. Start BT-100A.
2. See the Receive screen to check that [INT ANT] and [INT REF] are selected. For
example, if [INT ANT] is [5 Watt] or [EXT COAX], click on the button and select
“Internal Antenna.”
3-13
3. Separate BT-100A from the Beacon by about 50 cm, and start the Self test.
Slide the operation switch on the Beacon to [TEST] position and keep the position.
4. After checking that 406 MHz and 121.5 MHz are received satisfactorily, return the
switch to [READY] position.
5. See the coding information for 406 MHz to see that it agrees with the result of the
coding operation performed. Pay attention especially to Hex Code.
Information)
Hex Code, UIN: ex, 3604DF0AA0FFBFF
Mark the code on the Beacon using a tape printing machine.
406 Hex message: FFFE2F9B026F85507FDFFB7A6BF783E0F66C
The underlined numbers differ depending on whether the message is Normal
Message or Selftest Message.
- For Selftest Message: A message starting with FF FE D0---- will be
repeated.
- For Normal Message: A Selftest Message starting with FF FE D0---- will
occur and then a Normal Message starting with FF FE 2F ------ will be
repeated.
3-14
6. Check the power for 406 MHz and 121.5 MHz. All power values shown are
relative percentages (%). They may vary depending on the distance or angle
between the Tester and Beacon, and/or errors in the sending power. However, for a
distance of about 50 cm, around 80% for 406 MHz and 70% for 121.5 MHz can be
considered normal.
406 MHz: 5 W ± 2 dB (35 ~ 39 dBm),

121.5 MHz: 50 mW ± 3 dB (14 ~ 20 dBm),
7. Check errors in the frequency and other parameters of 406 MHz and 121.5 MHz
signals. For measuring items, see the following table.
Table 3.2.1 Check points for 406 MHz signal characteristics

406 MHz Details
screen
(common for both Check points
Long and Short
MSGs)
406.025 MHz + 2 kHz 406.028 MHz + 1 kHz
406 Frequency
406.037 MHz + 1 kHz 406.040 MHz + 1 kHz
The relative values are for reference only.
406 Power
Standard: 5 W + 2 dB (35 ~ 39 dBm)
Power Rise Time Max. 5ms
Phase Deviation 1.1 + 0.1 rads (Min.: -x.xx / Max.: +x.xx)
Mod Raise Time 150 + 100 μs
Mod Fall Time 150 + 100 μs
Mod Symmetry Max. 5%
Mod Bit Rate 400 bps + 1%
Table 3.2.2 Check points for 121.5 MHz signal characteristics
For 121.5 MHz Check points

121 Frequency 121.5 MHz + 0.006 MHz (+50 ppm)
The relative values are for reference only.
121 Power
Standard value: 50 mW + 3 dB(14 ~ 20 dBm)
Sweep Direction Upward (USA) or Downward
Audio Freq 300 Hz - 1600 Hz
Sweep Range Min. 700 Hz
Sweep Rep Rate 2-4 Hz
Mod Factor 85%-100%
Duty Cycle Min. 40%
3-15
3.3 Labeling
3.3.1 Label information items
Mark the related information such as 15 Hex code, ship’s name, Callsign, MMSI and
Battery service life on the surface of the Beacon using a tape printing machine. Cover
the label with the transparent tape to prevent its coming off. The transparent tape is an
accessory of the Beacon.
Table 3.3.1 Label information

Marked on the
Item surface of the Remarks
Beacon
Already labeled by the
Beacon S No. 9
manufacturer
Information required to be
MMSI 9
Callsign 9
15 Hex Code 9
5 years after it is installed
Battery service life 9
(replace at 5-year intervals)
For a case of performing SBM
Next SBM 9 SBM at 5-year(depend on
labeled
countries) intervals
Name of the SBM/service
SBM provider 9
provider
Ship’s name 9
Marked on the
HRU Replace at 2-year intervals
sensor
Flag state 9
▪ Hex Code/UIN ▪ Vessel name

▪ MMSI ▪ Callsign
▪ Country
Tron 60GPS
3-16
In Case of Tron VDR;

「VDR System」 -> FURUNO_VR-7000
▪ Hex Code/UIN ▪ Vessel name

▪ MMSI ▪ Callsign
▪ Country
Tron 40Smk2, Tron 40VDR: VR-7021F
3.3.2 Battery Service life

Mark the Battery service life (expiry date).
The Battery life is five years after it is installed that the Shelf life specified is not
expired. See “the Battery production date label” stuck on the Beacon.
In addition, indicate the Name of the SBM/service provider, and SBM next time in the
Battery service life label.
Battery production date label
Battery service life indication label ; FURUNO-NISHINOMIYA

- Battery expiry date NEXT SBM: AUG/2019
- Next SBM date
- SBM/Service provider
ex; Battery
Tron 60GPS service life label
Tron 40VDR
3-17
3.3.3 Hydrostatic Release Unit (HRU)

The life of the HRU is 2 years after it is put in service.
The numbers shown under the year and month label that correspond to the life (expiry
date) should be painted out in black with an oil marker pen, or cut out.
3-18
3.3.4 Mounting the Beacon

1. Remove the yellow “warning sheet.” Make sure that the Beacon is set in place in
the Bracket.
Warning sheet
Important) For Tron 40VDR: VR-7021F

Apply the silicone grease on the surface of the VDR storage module and
VDR Docking Module. Then mount the Beacon in place in the Bracket.
Apply the silicone grease on the surface of

VDR storage Module the VDR storage module and VDR Docking
Module. Make sure of intimate contact
between the two modules.
VDR Docking Module
2. Make sure that “the instructions board made of acrylic plate” supplied as an
accessory is put up near the Beacon mounting position.
Instructions board
made of acrylic plate
3-19
Chapter 4. Outline of the
Chapter Beacon
4. Outline of Beacon
4.1 Tron 60S, Tron 60GPS
The bracket cover is held The opposite end of the bracket

in place with a cotter pin cover is held in place with a hook.
Bracket Size (Weight=1.53 kg)

L=385 x W=151 x H=153
Water sensor
switch
Fig. 4.1.1 Bracket cover removed
211
Hydrostatic Release
Unit(HRU) fastened
in place (looking 90
from the bottom)
Insert a bush (5 mmφ) in each of the four

mount holes and fasten the beacon
bracket using 5 mm bolts (4).
Magnet for beacon internal
safety switch
Fig. 4.1.2 Lower bracket
4-1
Chapter 4. Outline of Beacon
When the Hydrostatic Release Unit(HRU) is activated, the bar attached thereto is
broken whereby the top cover of the bracket is released, which in turn releases the
spring to push the beacon out. The following figure shows the Hydrostatic Release
Unit that has been released and sprung.
To remove the HRU, slide it.
To fasten the HRU, depress the spring

(panel) and insert the sensor in the
hole and then slide it toward the
bottom of the lower bracket.
Fig. 4.1.3 Removing the Hydrostatic Release Unit(HRU)
Beacon
When the bar attached to the

HRU is broken, the top cover of
the bracket is released, which
in turn releases the spring to
push the beacon out.
Fig. 4.1.4 Lower bracket
4-2
4-3
4-4
4-5
4.2 Tron 40VDR: VR-7021F (Float –Free Data Recording Unit)
(5) (5)
(1) (2)
(4)
(3)
(1) Instructions board: Put it up near the location of Beacon.

(2) Transparent sheet: Beacon Cording Label protective sheet
(3) Battery expiry label: apply near the beacon instructions label
(4) Silicone grease: Apply the Beacon VDR storage Module and Docking Module
(5) Test result (Factory acceptance test sheet)
Fig. 4.2.1 Accessories list
532.6
237.3
H=215.5
LAN cable: 2 m
Fig. 4.2.2 Appearance of EPIRB
4-6
6.5 φ x 6
157.2 157.2
163.3 91. 2
172.0
Fig. 4.2.3 Bottom of Bracket
Fig. 4.2.4 Nameplate of Bracket
4-7
Fig. 4.2.5 Top cover removed
VDR Storage Module: 64 GB

IP Address: 10.0.0.150
VDR Docking Module
Fig. 4.2.6 Docking Module and VDR Storage Module
4-8
Hydrostatic Release Unit(HRU)

Magnet for beacon
internal safety switch
Fig. 4.2.7 Lower bracket-1
GND point of the VDR

Docking Module
Fig. 4.2.8 Lower bracket-2
4-9
When the Hydrostatic Release Unit(HRU) is activated, the bar attached thereto is
broken whereby the top cover of the bracket is released, which in turn releases the
spring to push the beacon out. The following figure shows the Hydrostatic Release
Unit that has been released and sprung.
Push the beacon out

from the bracket by
means of spring force.
Fig. 4.2.9 Operation of the Hydrostatic Release Unit(HRU)
VDR Storage Module

Sealing bracket
To fasten the sealing

bracket, hammer it.
Wrench open the sealing

bracket.
Separated
Fig. 4.2.10 Dismounting the VDR storage Module and Docking Module
4-10
Apply the silicone grease supplied

as an accessory on the surface of
VDR storage Module the VDR storage module and VDR
docking module.
Make sure closely contact between
the two modules.
VDR Docking Module
Fig. 4.2.11 VDR storage Module and VDR Docking Module
Fig. 4.2.12 JUNCTION BOX: VR7022F
Table 4.2.1 Beacon LAN cable signal names:

Signal
Cable color Cable color Signal name
name
White/Orange Rx + Blue DC + (PoE : Not used)
Orange Rx - White/Brown DC + (PoE : Not used)
White/Green Tx + White/Blue 24V dc+ (External Power)
Green Tx - Brown 24V dc- (External Power)
Shield GND
4-11
4-12
SPECIFICATION FOR
COSPAS-SARSAT
406 MHz DISTRESS BEACONS
C/S T.001
Issue 3 – Revision 14
October 2013
-i- C/S T.001 – Issue 3 – Rev.14
October 2013
SPECIFICATION FOR COSPAS-SARSAT 406 MHz DISTRESS BEACONS
History
Issue Revision Date Comments
1 - April 1986 Approved by the Cospas-Sarsat Steering Committee

(CSSC-15)
2 - November 1988 Approved by the Cospas-Sarsat Council (CSC-1)
3 - November 1995 Approved by the Cospas-Sarsat Council (CSC-15)
3 1 January 1998 Approved by the Cospas-Sarsat Council (CSC-19)
3 2 October 1998 Approved by the Cospas-Sarsat Council (CSC-21)
3 3 October 2000 Editorial changes, approved by the Cospas-Sarsat
Council (CSC-25) as Corrigendum to C/S T.001
Issues 3 - Rev.3
3 7 November 2005 Approved by the Cospas-Sarsat Council (CSC-35)
3 8 November 2007 Approved by the Cospas-Sarsat Council (CSC-39)
- ii - C/S T.001 – Issue 3 – Rev.14
October 2013
TABLE OF CONTENTS
Page
Revision History ............................................................................................................................ i

Table of Contents .......................................................................................................................... ii
List of Figures................................................................................................................................ v
List of Tables ................................................................................................................................. v
1. Introduction ......................................................................................................................... 1-1
1.1 Purpose ........................................................................................................................... 1-1

1.2 Scope .............................................................................................................................. 1-1
2. System Requirements ......................................................................................................... 2-1
2.1 Beacon Functional Elements ......................................................................................... 2-1

2.2 Digital Message Generator ............................................................................................ 2-1
2.2.1 Repetition Period ................................................................................................. 2-1

2.2.2 Total Transmission Time ..................................................................................... 2-1
2.2.3 Unmodulated Carrier ........................................................................................... 2-1
2.2.4 Digital Message.................................................................................................... 2-1
2.3 Modulator and 406 MHz Transmitter ........................................................................... 2-3
2.3.1 Transmitted Frequency ........................................................................................ 2-3

2.3.2 Transmitter Power Output ................................................................................... 2-4
2.3.3 Antenna Characteristics ....................................................................................... 2-4
2.3.4 Spurious Emissions .............................................................................................. 2-5
2.3.5 Data Encoding ...................................................................................................... 2-5
2.3.6 Modulation ........................................................................................................... 2-6
2.3.7 Voltage Standing-Wave Ratio ............................................................................. 2-7
2.3.8 Maximum Continuous Transmission .................................................................. 2-7
3. Digital Message Structure.................................................................................................. 3-1
3.1 Basic Structure ............................................................................................................... 3-1

3.2 Beacon Coding ............................................................................................................... 3-2
.../...
- iii - C/S T.001 – Issue 3 – Rev.14
October 2013
TABLE OF CONTENTS (Continued)

Page
4. Environmental and Operational Requirements ............................................................ 4-1
4.1 General .......................................................................................................................... 4-1

4.2 Thermal Environment ................................................................................................... 4-1
4.2.1 Operating Temperature Range ........................................................................... 4-1

4.2.2 Temperature Gradient ......................................................................................... 4-1
4.2.3 Thermal Shock .................................................................................................... 4-2
4.3 Mechanical Environment.............................................................................................. 4-2

4.4 Other Environmental Requirements ............................................................................. 4-2
4.5 Operational Requirements ............................................................................................ 4-2
4.5.1 Duration of Continuous Operation ..................................................................... 4-2

4.5.2 Other Operational Requirements ........................................................................ 4-2
4.5.3 Auxiliary Radio-Locating Device ...................................................................... 4-2
4.5.4 Beacon Self-Test Mode ...................................................................................... 4-3
4.5.5 Encoded Position Data ........................................................................................ 4-4
4.5.6 Beacon Activation ............................................................................................... 4-7
Annex A - Beacon Coding
A1 General ....................................................................................................................... A-1
A1.1 Summary......................................................................................................... A-1

A1.2 Message Format Flag, Protocol Flag, and Country Code ............................. A-2
A1.2.1 Format Flag ........................................................................................ A-2

A1.2.2 Protocol Flag ...................................................................................... A-2
A1.2.3 Country Code ..................................................................................... A-2
A1.3 Protocol Codes ............................................................................................... A-3
A2 User Protocols ........................................................................................................... A-5
A2.1 Structure of User Protocols ............................................................................ A-5

A2.2 Maritime User Protocol .................................................................................. A-7
A2.3 Radio Call Sign User Protocol ....................................................................... A-8
A2.4 Aviation User Protocol ................................................................................... A-9
.../...
- iv - C/S T.001 – Issue 3 – Rev.14
October 2013

Page
A2.5 Serial User Protocol ....................................................................................... A-9
A2.5.1 Serial Number .................................................................................. A-10

A2.5.2 Aircraft 24-bit Address .................................................................... A-11
A2.5.3 Aircraft Operator Designator and Serial Number ........................... A-11
A2.6 Test User Protocol .......................................................................................... A-12

A2.7 Orbitography Protocol .................................................................................. A-12
A2.8 National User Protocol ................................................................................. A-13
A2.9 Non-Protected Data Field............................................................................. A-14
A2.9.1 Maritime Emergency code .............................................................. A-14

A2.9.2 Non-Maritime Emergency code ...................................................... A-14
A2.9.3 National Use..................................................................................... A-15
A3 Location Protocols .................................................................................................. A-17
A3.1 Summary....................................................................................................... A-17

A3.2 Default Values in Position Data................................................................... A-17
A3.3 Definition of Location Protocols ................................................................. A-19
A3.3.1 Position Data .......................................................................................... A-19

A3.3.2 Supplementary Data ............................................................................... A-20
A3.3.3 Test Location Protocols ......................................................................... A-20
A3.3.4 User-Location Protocols ........................................................................ A-22
A3.3.5 Standard Location Protocols .................................................................. A-24
A3.3.6 National Location Protocol .................................................................... A-27
A3.3.7 RLS Location Protocol .......................................................................... A-30
Annex B - Sample Bose-Chaudhuri-Hocquenghem Error-Correcting Code Calculation
B1 Sample 21-Bit BCH Code Calculation ..................................................... B-1
B2 Sample 12-Bit BCH Code Calculation ..................................................... B-4
Annex C - List of Acronyms................................................................................................. C-1

-v- C/S T.001 – Issue 3 – Rev.14
October 2013

Page
List of Figures:
Figure 2.1: Short-Message Format .............................................................................. 2-2

Figure 2.2: Long-Message Format ............................................................................... 2-2
Figure 2.3: Spurious Emission Mask for 406.0 to 406.1 MHz Band ......................... 2-5
Figure 2.4: Data Encoding and Modulation Sense ...................................................... 2-5
Figure 2.5: Definition of Modulation Rise and Fall Times ......................................... 2-6
Figure 2.6: Definition of Modulation Symmetry ........................................................ 2-6
Figure 4.1: Temperature Gradient................................................................................ 4-1
Figure A1: Data Fields of the Short Message Format ................................................ A-3
Figure A2: Data Fields of the Long Message Format ................................................ A-3
Figure A3: Bit Assignments for the First Protected Data Field (PDF-1) of
User Protocols ........................................................................................... A-6
Figure A4: Summary of User Protocols Coding Options ........................................ A-16
Figure A5: Outline of Location Protocols ................................................................ A-18
Figure A6: General Format of Long Message for Location Protocols .................... A-21
Figure A7: User-Location Protocols ......................................................................... A-23
Figure A8: Standard Location Protocols .................................................................. A-26
Figure A9: National Location Protocol .................................................................... A-29
Figure A10: RLS Location Protocol ............................................................................. A-32
Figure B1: Sample 21-Bit BCH Error-Correcting Code Calculation ........................ B-3
Figure B2: Sample 12-Bit BCH Error-Correcting Code Calculation ........................ B-5
List of Tables:
Table A1: Format Flag and Protocol Flag Combinations ......................................... A-3
Table A2: Protocol Codes Assignments.................................................................... A-4
Table A3: Modified-Baudot Code ............................................................................. A-7
Table A4: Maritime Emergency Codes in Accordance with the
Modified IMO Nature of Distress Indication ........................................ A-15
Table A5: Non-Maritime Emergency Codes .......................................................... A-15
1-1 C/S T.001 – Issue 3 – Rev.14
October 2013
1. INTRODUCTION
1.1 Purpose
The purpose of this document is to define the minimum requirements to be used for the
development and manufacture of 406 MHz Emergency Locator Transmitters (ELTs),
Emergency Position-Indicating Radio Beacons (EPIRBs), and Personal Locator Beacons
(PLBs). In this document, the term ELT indicates an aviation distress beacon, an EPIRB a
maritime distress beacon, and a PLB a distress beacon for personal use.
Specifications that are critical to the Cospas-Sarsat System are defined in detail; specifications
which could be developed by the national authorities are identified in more general terms.
1.2 Scope
This document contains the minimum requirements that apply to Cospas-Sarsat 406 MHz
distress beacons. It is divided into the following sections:
a) Section 2 gives the system requirements applicable to all types of beacons. When
met, these requirements will enable the beacons to provide the intended service in
terms of location probability and accuracy and will not disturb the system operation.
b) Section 3 deals with the beacon message content. Basic message structure is defined.
Assignment and meaning of the available data bits are defined in Annex A to this
specification.
c) Section 4 defines a set of environmental and operational requirements. These

requirements are not intended to be exhaustive and may be complemented by more
detailed national or international standards (e.g. RTCA standards for ELTs).
However, they represent the minimum environmental and operational performance
requirements for a 406 MHz beacon to be compatible with the Cospas-Sarsat System.
d) Annex A defines the beacon coding.
e) Annex B provides samples of error correcting code calculations.
f) Annex C provides a list of acronyms used in this document.
- END OF SECTION 1 -
1-1 C/S T.001 – Issue 3 – Rev.14
October 2013
2. SYSTEM REQUIREMENTS
2.1 Beacon Functional Elements
This section defines the requirements for the two following functional elements of a 406 MHz
distress beacon:
a) digital message generator; and
b) modulator and 406 MHz transmitter.
2.2 Digital Message Generator
The digital message generator will key the modulator and transmitter so that the message
defined in section 3 is transmitted.
2.2.1 Repetition Period
The repetition period shall not be so stable that any two transmitters appear to be
synchronized closer than a few seconds over a 5-minute period. The intent is that no two
beacons will have all of their bursts coincident. The period shall be randomised around a
mean value of 50 seconds, so that time intervals between transmission are randomly
distributed on the interval 47.5 to 52.5 seconds.
2.2.2 Total Transmission Time
The total transmission time, measured at the 90 percent power points, shall be
440 ms +1 percent for the short message and 520 ms +1 percent for the long message.
2.2.3 Unmodulated Carrier
The initial 160 ms +1 percent of the transmitted signal shall consist of an unmodulated
carrier at the transmitter frequency measured between the 90 percent power point and the
beginning of the modulation.
2.2.4 Digital Message
a. Short Message
The final 280 ms +1 percent of the transmitted signal shall contain a 112-bit message
at a bit rate of 400 bps +1 percent;
b. Long Message
2-2 C/S T.001 – Issue 3 – Rev.14
October 2013
The final 360 ms +1 percent of the transmitted signal shall contain a 144-bit message
at a bit rate of 400 bps +1 percent.
2.2.4.1 Bit Synchronization
A bit-synchronization pattern consisting of "1"s shall occupy the first 15-bit positions.
2.2.4.2 Frame Synchronization
A frame synchronization pattern consisting of 9 bits shall occupy bit positions

16 through 24. The frame synchronization pattern in normal operation shall be
000101111. However, if the beacon radiates a modulated signal in the self-test mode, the
frame synchronization pattern shall be 011010000 (i.e. the last 8 bits are complemented).
2.2.4.3 Format Flag
Bit 25 is a format (F) flag bit used to indicate the length of the message to follow. Value
"0" indicates a short message; value "1" indicates a long message.
2.2.4.4 Message Content
The content of the remaining 87 bits (short message - see Figure 2.1) or 119 bits (long
message - see Figure 2.2) is defined in section 3.
160 ms 15 9 87 BITS (SEE SECTION 3)

CARRIER BITS BITS
NOTE: (1) (2) (3)
Figure 2.1: Short Message Format
160 ms 15 9 119 BITS (SEE SECTION 3)

CARRIER BITS BITS
NOTE: (1) (2) (3)
Figure 2.2: Long Message Format

Notes: (1) Bit Synchronization : 15 "1" bits
(2) Frame Synchronization : 000101111 (except as in section 4.5.4)
(3) "0" bit indicates short-message format
"1" bit indicates long-message format
2-3 C/S T.001 – Issue 3 – Rev.14
October 2013
2.3 Modulator and 406 MHz Transmitter
2.3.1 Transmitted Frequency*
To ensure adequate System capacity and an efficient use of the available frequency
spectrum in the band 406.0 - 406.1 MHz allocated by the ITU for the operation of low-
power satellite emergency position-indicating radiobeacons, a number of channels have
been defined in the allocated band and will be assigned by Cospas-Sarsat from time to
time, as necessary to satisfy capacity requirements.
The frequency channels in the band 406.0 - 406.1 MHz are defined by the centre
frequency of the channels, as assigned by Cospas-Sarsat.
Except as provided below for beacons type approved by Cospas-Sarsat for operation at
406.025 MHz and 406.028 MHz, the beacon carrier frequency shall be set in accordance
with the Cospas-Sarsat 406 MHz Channel Assignment Table, as provided in document
C/S T.012 “Cospas-Sarsat 406 MHz Frequency Management Plan”, at the designated
centre frequency of the appropriate channel + 1 kHz, and shall not vary more than
+ 5 kHz from that channel centre frequency in 5 years.
The carrier frequency of beacons operating in the 406.025 MHz channel in accordance
with the Cospas-Sarsat 406 MHz Channel Assignment Table shall be set at 406.025 MHz
+ 2 kHz. The carrier frequency shall not vary more than + 5 kHz from 406.025 MHz in
5 years.
The carrier frequency of beacons operating in the 406.028 MHz channel in accordance
with the Cospas-Sarsat 406 MHz Channel Assignment Table shall be set at
406.028 + 1 kHz. The carrier frequency shall not vary more than +2 kHz /-5 kHz from
406.028 MHz in 5 years.
The transmitted frequency short-term variations shall not exceed 2 parts in 109 in 100 ms.
The transmitted frequency medium-term stability shall be defined by the mean slope of
the frequency versus time over a 15-minute period and by the residual frequency variation
about the mean slope. The mean slope shall not exceed 1 part in 109 per minute, except
as noted below. The residual frequency variation shall not exceed 3 parts in 109.
After allowing 15-minutes for beacon warm-up, the medium-term frequency stability
requirements shall be met for all defined environmental conditions, except for the
temperature gradient and the thermal shock as defined in sections 4.2.2 and 4.2.3
respectively.
__________________
* This section of the beacon specification does not apply to Cospas-Sarsat System beacons (i.e.
orbitography or calibration beacons). The transmitted frequency requirements for orbitography
beacons are detailed in document C/S T.006.
2-4 C/S T.001 – Issue 3 – Rev.14
October 2013
The mean slope of the medium-term frequency stability measurements shall not exceed
2 parts in 109 per minute, and the residual frequency variation shall not exceed 3 parts
in 109:
 during the variable temperature conditions of the temperature gradient (+/- 5 C/h
slope) defined in section 4.2.2 and for the 15 minute periods immediately after the
temperature had stabilised at the maximum or minimum values; and
 during the thermal shock defined in section 4.2.3.
It is recommended that distress transmissions commence as soon as possible after

activation, but in accordance with section 4.5.6.
The mean slope and the residual frequency variation shall be measured as follows: Data
shall be obtained by making 18 sequential frequency measurements, one every repetition
period (50 sec +5 percent, see section 2.2.1) over an approximate 15 minute interval; each
measurement shall be a 100-ms frequency average performed during the modulated part
of the message.
The mean slope is defined as that of the least-squares straight-line fit to the 18 data points.
Residual frequency variation is defined as the root mean square (RMS) error of the points
relative to the least-squares estimate.
2.3.2 Transmitter Power Output
The transmitter power output shall be within the limits of 5 W + 2 dB (35 to 39 dBm)
measured into a 50-Ohm load. This power output shall be maintained during 24-hour
operation at any temperature throughout the specified operating temperature range.
Power output rise time shall be less than 5 ms measured between the 10% and 90% power
points. The power output is assumed to rise linearly from zero and therefore must be zero
prior to about 0.6 ms before the beginning of the rise time measurement; if it is not zero,
the maximum acceptable level is -10 dBm.
2.3.3 Antenna Characteristics
The following antenna characteristics are defined for all azimuth angles and for elevation
angles greater than 5° and less than 60°:
- Pattern : hemispherical
- Polarization : circular (RHCP) or linear
- Gain : between -3 dBi and 4 dBi over 90% of the above region
- Antenna VSWR : not greater than 1.5:1
The antenna characteristics should be measured in a configuration as close as possible to

its operational condition.
2-5 C/S T.001 – Issue 3 – Rev.14
October 2013
2.3.4 Spurious Emissions
The in-band spurious emissions shall not exceed the levels specified by the signal mask in
Figure 2.3, when measured in a 100 Hz resolution bandwidth.
Pc
(POWER OUTPUT OF 0 dBc

UNMODULATED CARRIER)
- 20 - 20
dBc dBc
- 30 - 30
dBc dBc
- 35 dBc - 35 dBc
- 40 - 40
dBc dBc
- 24 kHz - 12 - 7 - 3 fc 3 7 12 24 kHz
kHz kHz kHz kHz kHz kHz
406.1 MHz
406.0 MHz
FREQUENCY (fc = BEACON CARRIER FREQUENCY)
Figure 2.3: Spurious Emission Mask for 406.0 to 406.1 MHz Band
2.3.5 Data Encoding
The data shall be encoded biphase L, as shown in Figure 2.4.
Figure 2.4: Data Encoding and Modulation Sense

2-6 C/S T.001 – Issue 3 – Rev.14
October 2013
2.3.6 Modulation
The carrier shall be phase modulated positive and negative 1.1 + 0.1 radians peak,
referenced to an unmodulated carrier. Positive phase shift refers to a phase advance
relative to nominal phase. Modulation sense shall be as shown in Figure 2.4.
The rise (R) and fall (F) times of the modulated waveform, as shown in Figure 2.5, shall
be 150 + 100 s.
Modulated Signal
Time
Figure 2.5*: Definition of Modulation Rise and Fall Times
1   2
Modulation symmetry (see Figure 2.6) shall be such that:  0.05
1   2
Modulated Signal
Time
Figure 2.6*: Definition of Modulation Symmetry

__________________
* Figure not to scale.
2-7 C/S T.001 – Issue 3 – Rev.14
October 2013
2.3.7 Voltage Standing-Wave Ratio
The modulator and 406 MHz transmitter shall be able to meet all requirements, except for
those in paragraph 2.3.2 (transmitter power output), at any VSWR between 1:1 and 3:1,
and shall not be damaged by any load from open circuit to short circuit.
2.3.8 Maximum Continuous Transmission
The distress beacon shall be designed to limit any inadvertent continuous 406 MHz
transmission to a maximum of 45 seconds.
3-2 C/S T.001 – Issue 3 – Rev.14
October 2013
3. DIGITAL MESSAGE STRUCTURE
3.1 Basic Structure
The digital message which is transmitted by the 406 MHz beacon consists of:
a) 112 bits for the short message; and
b) 144 bits for the long message.
These bits are divided into five groups:
(1) The first 24 bits transmitted, positions 1 through 24, are system bits; they are defined
in section 2 and are used for bit and frame synchronization.
(2) The following 61 bits, positions 25 through 85, are data bits. This bit group is
referred to as the first protected data field (PDF-1). The first data bit (position 25)
indicates if the message is short or long: "0" = short message, "1" = long message.
(3) The following 21 bits, positions 86 through 106, are a Bose-Chaudhuri-Hocquenhem

or BCH (82,61) error-correcting code. This bit group is referred to as the first BCH
error-correcting field (BCH-1). This code is a shortened form of a BCH (127,106)
triple error-correcting code, as described in Annex B. This code can detect and
correct up to three bit errors in the 82 bits of (PDF-1 + BCH-1). The combination
of PDF-1 and BCH-1 is referred to as the first protected field.
(4) The following group consists of data bits, the number and definition of these bits
depends on the message format, as follows:
a) Short message: the last 6 bits of the message in positions 107 through 112,
these data bits are not protected. This bit group is referred
to as the non-protected data field;
b) Long message: the following 26 bits of the message in positions 107

through 132. This bit group is referred to as the second
protected data field (PDF-2).
(5) The last 12 bits of the long message, positions 133 through 144, are a Bose-
Chaudhuri-Hocquenhem or BCH (38,26) error-correcting code. This bit group is
referred to as the second BCH error-correcting field (BCH-2). This code is a
shortened form of a BCH (63,51) double error-correcting code, as described in
Annex B. This code can detect and correct up to 2 bit errors in the 38 bits of
(PDF-2 + BCH-2). The combination of PDF-2 and BCH-2 is referred to as the
second protected field.
3-3 C/S T.001 – Issue 3 – Rev.14
October 2013
3.2 Beacon Coding
Beacon coding methods are defined in Annex A to this specification. Specific operational
requirements for beacon coding, such as the self-test mode and the encoding of position data,
are defined in section 4 of this specification.
Beacon message protocols that support encoded location information (e.g. User-Location,
Standard Location and National Location) shall only be used in beacons that are designed to
accept encoded location information from a navigation system.
The 15 hexadecimal characters that uniquely identify each 406 MHz beacon are called the
beacon identification or beacon 15 Hex ID. This beacon identification comprises bits 26 to 85
of PDF-1. For location protocols, the position data bits in PDF-1 are set to the default values
specified in Annex A. It is recommended that the beacon 15 Hex ID be permanently marked
on the exterior of the beacon.
4-1 C/S T.001 - Issue 3 – Rev. 14
October 2013
4. ENVIRONMENTAL AND OPERATIONAL REQUIREMENTS
4.1 General
As explained in section 1.2, the environmental and operational requirements defined in this
section are not intended to be exhaustive. They are minimum requirements, which may be
complemented by national or international standards.
4.2 Thermal Environment
4.2.1 Operating Temperature Range
Two standard classes of operating temperature range are defined, inside which the system
requirements of section 2 shall be met:
Class 1: -40°C to +55°C
Class 2: -20°C to +55°C
The operating temperature range shall be permanently marked on the beacon.
4.2.2 Temperature Gradient
All system requirements of section 2, including the frequency requirements defined in

section 2.3.1, shall be met when the fully packaged beacon is subjected to the temperature
gradient shown in Figure 4.1.
+55 2h
twarm-up = 15 min
1h
Tmin 2h 2h
TIME
ton tmeas
NOTES: Tmin = - 40C (Class 1 beacon)
Tmin = - 20C (Class 2 beacon)
ton = beacon turn-on time after 2 hour “cold soak”
tmeas = start time of frequency stability measurement (ton + 15 min)
Figure 4.1: Temperature Gradient

4-2 C/S T.001 - Issue 3 – Rev. 14
October 2013
4.2.3 Thermal Shock
All system requirements of section 2 shall be met, including the mean slope of the
medium-term frequency stability measurements which shall not exceed 2.0 parts in 109
per minute, for measurements beginning 15 minutes after simultaneously activating the
beacon and applying a thermal shock of 30°C within the specified operating temperature
range of the beacon. Subsequently, system requirements shall continue to be met for a
minimum period of two (2) hours.
4.3 Mechanical Environment
Beacons shall be submitted to vibration and shock tests consistent with their intended use.
Internationally-recognized standards such as RTCA/DO-183 for ELTs could be used by the

national authorities.
4.4 Other Environmental Requirements
Other environmental requirements such as humidity tests, altitude tests, over/under pressure
tests, waterproofness tests, sand and dust tests, fluids susceptibility tests, etc., may be defined by
national authorities, preferably using internationally-recognized standards.
4.5 Operational Requirements
4.5.1 Duration of Continuous Operation
The minimum duration of continuous operation shall be at least 24 hours* at any

temperature throughout the specified operating temperature range. This characteristic
shall be permanently marked on the beacon.
4.5.2 Other Operational Requirements
Other operational requirements such as installation and maintenance methods, remote

monitoring, activation methods on planes or boats, etc. may be defined by national
authorities.
4.5.3 Auxiliary Radio-Locating Device
The distress beacon may incorporate an auxiliary radio-locating device at another

frequency (121.5 MHz, 9 GHz SART, etc.) which is compatible with existing
radio-locating equipment.
__________________
* For installations meeting IMO GMDSS requirements, a minimum operating lifetime of 48 hours at any
temperature throughout the specified operating temperature range is necessary.
4-3 C/S T.001 - Issue 3 – Rev. 14
October 2013
Any such auxiliary radio-locating device must satisfy all the national performance
standards applicable to radio-locating devices at the selected auxiliary frequency.
4.5.4 Beacon Self-Test Mode
All beacons shall include a self-test mode of operation.
In the self-test mode beacons shall transmit a digital message encoded in accordance with
Annex A to this specification. The content of the self-test message shall always provide
the beacon 15 Hex ID, except for location protocol beacons when transmitting a GNSS
self-test message encoded with location data.
In the self-test mode the signal must have a frame synchronization pattern of 011010000.
This bit pattern complements the last 8 bits of the normal frame synchronization pattern so
that this test burst will not be processed by the satellite equipment.
The complete self-test transmission must be limited to one burst only. The maximum
duration of the self-test mode transmission should be 440 ms (+1%) for a short message
and 520 ms (+1%) for a long message. If a 440 ms transmission is used for beacons
encoded with the long format messages, it is recommended that the message be truncated
without changing the format flag bit.
The self-test mode shall be activated by a separate switch position
The self-test function shall perform an internal check and provide distinct indication that:
a) the self-test mode has been initiated;
b) RF power is being emitted at 406 MHz and at 121.5 MHz, if applicable;
c) the internal check has passed successfully, or has failed; and
d) the beacon battery may not have sufficient energy to support beacon operation
for the declared operating lifetime.(1)
The beacon shall be designed to ensure an automatic termination of the self-test mode
immediately after completion of the self-test cycle and indication of the self-test results.
For location protocol beacons the content of the encoded position data field of the self-test
message shall be the default values specified in Annex A. Additionally, location protocol
beacons may optionally provide for the transmission of a GNSS self-test message encoded
with location data.
__________________
(1)
Only mandatory to new beacon models submitted for type approval testing after 1 November 2015.
4-4 C/S T.001 - Issue 3 – Rev. 14
October 2013
Location protocol beacons which provide for the transmission of an encoded position in a
GNSS self-test message shall:
a) activate the GNSS self-test mode via a distinct operation from the normal self-
test mode, but the GNSS self-test mode may be activated via the same self-test
switch(es) or operation provided that it shall require a separate, deliberate action
by the user that would limit the likelihood of inadvertent activation, and shall
not result in more than a single self-test burst;
b) provide for that in the case of internal GNSS receivers powered by the
primary(1) beacon battery the number of GNSS self-tests shall be limited by the
beacon design to prevent inadvertent battery depletion;
c) provide a distinct indication to register successful completion or failure of the

GNSS self-test;
d) provide, for beacons with internal navigation devices:
- a separate distinct indication that the limited number of GNSS self-test

attempts has been attained, which shall be immediately indicated to the user
once the GNSS Self-test has been initiated,
- once the GNSS Self-test limit has been reached, further GNSS Self-test
activations shall not result in any RF-transmissions or further GNSS receiver
power drain;
e) ensure that the duration of the GNSS self test is limited to a maximum time
duration set by the manufacturer, noting that:
- in the case where the beacon fails to encode the location into the 406 MHz
message within this time limit the GNSS self-test shall cease, the beacon
shall indicate a GNSS self-test failure and may transmit a single self-test
burst with default location data,
- in the case where the beacon encodes the location into the 406 MHz message
within this time limit the GNSS self-test shall cease at that time (before the
time limit is reached), indicate a GNSS self-test pass and may transmit a
single self-test burst containing the valid location data; and
f) include instructions for the GNSS self-test in the Beacon Instruction Manual
which shall include a clear warning on the use and limitations of this function,
noting that instructions for the GNSS self-test shall not be included on the
beacon itself.
__________________
(1)
The primary battery is the battery which is powering the 406 MHz function.
4-5 C/S T.001 - Issue 3 – Rev. 14
October 2013
4.5.5 Encoded Position Data*
4.5.5.1 General
Beacon position data, obtained from a navigation device internal or external to the beacon,
may be encoded in the beacon message. Position data can be encoded in either the PDF-2
part of the message, or in both PDF-1 and PDF-2 parts of the message.
Three levels of position resolution can be encoded in the beacon message:
 position data with resolution of 4 seconds in PDF-2, given as an offset of the position
data provided in PDF-1 with a resolution of either 15 minutes or 2 minutes;
 position data with resolution of 4 minutes in PDF-2, together with any of the user
protocol identification methods used in PDF-1; and
 position data in the short message with a resolution of either 15 minutes or 2 minutes,
together with a subset of the beacon identification methods (i.e. with shortened
identification data).
Operation or failure of an internal or external navigation device providing position data to

the beacon shall not degrade beacon performance.
4.5.5.2 Message Content and Timing
Position data shall be encoded into the beacon message according to one of the methods
specified in Annex A. The identification data and encoded position data are protected by a
BCH error-correcting code. A 21-bit BCH code protects the data of the first protected
field (PDF-1 and BCH-1) and a 12-bit BCH code protects the data of the second protected
field (PDF-2 and BCH-2). The BCH codes shall always match the message content. The
beacon shall recompute these codes each time the message content is changed.
The beacon shall commence transmissions upon activation even if no valid position data
are available. Until valid data is available, the content of the encoded position data field of
the message shall be the default values specified in Annex A. The first input of position
data into the beacon message shall occur as soon as valid data is available. If the beacon
has the capability to provide updated position data, subsequent transmissions of the
updated position shall not occur more frequently than every 5 minutes.
If, after providing valid data, the navigation input fails or is not available, the beacon
message shall retain the last valid position for 4 hours ( 5 min) after the last valid position
data input. After 4 hours the encoded position shall be set to the default values specified in
Annex A.
_________________________________
* ELTs carried to satisfy the requirements of ICAO Annex 6, Parts I, II and III shall operate in
accordance with ICAO Annex 10.
4-6 C/S T.001 - Issue 3 – Rev. 14
October 2013
When the beacon radiates a 406 MHz signal in the self-test mode, the content of the
encoded position of the self-test message shall be set to the default values specified in
Annex A, except for location protocol beacons when transmitting an optional GNSS self-
test when the beacon shall radiate a single self-test message with encoded position.
4.5.5.3 Internal Navigation Device Performance
An internal navigation device shall be capable of global operation and shall conform to an
applicable international standard. An internal navigation device shall incorporate self-
check features to ensure that erroneous position data is not encoded into the beacon
message. The self-check features shall prevent position data from being encoded into the
beacon message unless minimum performance criteria are met. These criteria could
include the proper internal functioning of the device, the presence of a sufficient number of
navigation signals, sufficient quality of the signals, and sufficiently low geometric dilution
of precision.
The distance between the position provided by the navigation device, at the time of the
position update, and the true beacon position shall not exceed 500 m for beacons
transmitting the Standard or National location protocols, or 5.25 km for beacons
transmitting the User-Location protocol. The encoded position data shall be provided in
the WGS 84 or GTRF geodetic reference systems.
The internal navigation device shall provide valid data within 10 minutes after its
activation.
Internal navigation device cold start shall be forced at every beacon activation. Cold start
refers to the absence of time dependent or position dependent data in memory, which
might affect the acquisition of the GNSS position.
4.5.5.4 External Navigation Device Input
It is recommended that beacons, which are designed to accept data from an external
navigation device, be compatible with an applicable international standard, such as the IEC
Standard on Digital Interfaces (IEC Publication 61162).
Features should be provided to ensure that erroneous position data is not encoded into the
beacon message.
For a beacon designed to operate with an external navigation device, if appropriate

navigation data input is present, the beacon shall produce a digital message with the
properly encoded position data and BCH code(s) within 1 minute after its activation.
If a beacon is designed to accept position data from an external navigation device prior to
beacon activation, navigation data input should be provided at intervals not longer than:
 20 minutes for EPIRBs and PLBs; or
 1 minute for ELTs.
4-7 C/S T.001 - Issue 3 – Rev. 14
October 2013
4.5.6 Beacon Activation
The beacon should be designed to prevent inadvertent activation.
After activation, the beacon shall not transmit a 406 MHz distress message until at least
one repetition period (as defined in section 2.2.1) has elapsed.
– END OF SECTION 4 –
ANNEXES
TO THE SPECIFICATION FOR
COSPAS-SARSAT
406 MHz DISTRESS BEACONS
A-1 C/S T.001 - Issue 3 - Rev.14
October 2013
ANNEX A
BEACON CODING
A1 GENERAL
A1.1 Summary
This annex defines the 406 MHz beacon digital message coding. The digital message is
divided into various bit fields as follows:
Short Message Format (see Figure A1)
Bit Field Name Bit Field Location

1. Bit synchronization bit 1 through bit 15
2. Frame synchronization bit 16 through bit 24
3. First protected data field (PDF-1) bit 25 through bit 85
4. First BCH error correcting field (BCH-1) bit 86 through bit 106
5. Non-protected data field bit 107 through bit 112
Long Message Format (see Figure A2)
Bit Field Name Bit Field Location

1. Bit synchronization bit 1 through bit 15
2. Frame synchronization bit 16 through bit 24
3. First protected data field (PDF-1) bit 25 through bit 85
4. First BCH error correcting field (BCH-1) bit 86 through bit 106
5. Second protected data field (PDF-2) bit 107 through bit 132
6. Second BCH error correcting field (BCH-2) bit 133 through bit 144
The bit synchronization and frame synchronization fields are defined in sections 2.2.4.1 and
2.2.4.2, respectively.
The first protected data field (PDF-1) and the non-protected data field of the short message are
defined in section 3.1 and section A2 of this Annex, and shown in Figures A1, A3 and A4.
The first protected data field (PDF-1) and the second protected data field (PDF-2) of the long
message are defined in section 3.1 and section A3 of this Annex, and shown in Figures A2, A5,
A6, A7, A8 and A9.
The BCH error correcting fields BCH-1 and BCH-2 fields are defined in section 3.1 and the
corresponding 21 bit BCH error-correcting code and 12 bit BCH error-correcting code are
described at Annex B.
A-2 C/S T.001 - Issue 3 - Rev.14
October 2013
A1.2 Message Format Flag, Protocol Flag, and Country Code
The bit allocations for the message format flag, protocol flag and country code are identical in
all beacon protocols. They are assigned in PDF-1 of the short and the long messages as
follows:
Bits Usage
25 format flag (F)
26 protocol flag (P)
27-36 country code
A1.2.1 Format Flag
The format flag (bit 25) shows whether the message is short or long using the following
code:
F=0 short format
F=1 long format
A1.2.2 Protocol Flag
The protocol flag (bit 26) indicates which type of protocol is used to define the structure of
encoded data, according to the following code:
P=0 standard location protocols or national location protocol

P=1 user protocols or user-location protocols.
The various protocols are identified by a specific protocol code, as described in

section A1.3.
A1.2.3 Country Code
Bits 27-36 designate a three-digit decimal country code number expressed in binary
notation. Country codes are based on the International Telecommunication Union (ITU)
Maritime Identification Digit (MID) country code available on the ITU website
(www.itu.int/cgi-bin/htsh/glad/cga_mids.sh). National administrations allocated more
than one MID code may opt to use only one of these codes. However, when the 6 trailing
digits of a MMSI are used to form the unique beacon identification, the country code shall
always correspond to the first 3 digits of the MMSI code.
For all types of protocols, except the test protocols, the country code designates the
country of beacon registration, where additional information can be obtained from a
data base.
A-3 C/S T.001 - Issue 3 - Rev.14
October 2013
A1.3 Protocol Codes
Each coding protocol is identified by a unique protocol code defined as follows:
- 3-bit code in bits 37 to 39 for user and user-location protocols;
- 4-bit code in bits 37 to 40 for standard location and national location protocols.
Table A1 shows the combinations of the format flag and the protocol flag which identify each
category of coding protocols. The protocol codes assignments are summarized in Table A2.
Table A1: Format Flag and Protocol Flag Combinations
Format Flag (bit 25)  0 1

Protocol Flag (bit 26)  (short) (long)
0 Standard Location Protocols

(protocol code: bits 37-40) Not Used National Location Protocol
RLS Location Protocols
1 User Protocols
(protocol code: bits 37-39) User Protocols User-Location Protocols
Figure A1: Data Fields of the Short Message Format
Bit Frame Non-Protected

First Protected Data Field (PDF-1) BCH-1 Data Field
Synchronization Synchronization
Unmodulated Bit Frame Identification or 21-Bit Emergency Code/

Format Protocol Country
Carrier Synchronization Synchronization Identification BCH National Use or
Flag Flag Code
(160 ms) Pattern Pattern plus Position Code Supplement. Data
Data
Bit No. 1-15 16-24 25 26 27-36 37-85 86-106 107-112
15 bits 9 bits 1 bit 1 bit 10 bits 49 bits 21 bits 6 bits
Figure A2: Data Fields of the Long Message Format
Bit Frame Second Protected

Synchronization Synchronization First Protected Data Field (PDF-1) BCH-1 Data Field (PDF-2) BCH-2
Unmodulated Bit Frame Identification or 21-Bit Supplementary and 12-Bit

Format Protocol Country
Carrier Synchronization Synchronization Identification BCH Position or National BCH
Flag Flag Code
(160 ms) Pattern Pattern plus Position Code Use Data Code
Data
Bit No. 1-15 16-24 25 26 27-36 37-85 86-106 107-132 133-144
15 bits 9 bits 1 bit 1 bit 10 bits 49 bits 21 bits 26 bits 12 bits

A-4 C/S T.001 - Issue 3 - Rev.14
October 2013
Table A2: Protocol Codes Assignments

A2-A: User and User-Location Protocols (F=0, P=1) short message
(F=1, P=1) long message
Protocol Codes
(Bits 37 - 39)
1. EPIRB - Maritime User Protocol: (MMSI, 6 digits) 010
(radio call sign, 6 characters) 010
2. EPIRB - Radio Call Sign User Protocol 110
3. ELT - Aviation User Protocol (aircraft registration markings) 001
4. Serial User Protocol: 011
bits 40, 41, 42 used to identify beacon type:
000 ELTs with serial identification number;
001 ELTs with aircraft operator designator & serial number;
010 float free EPIRBs with serial identification number;
100 non float free EPIRBs with serial identification number;
110 PLBs with serial identification number;
011 ELTs with aircraft 24-bit address;
101 & 111 spares.
bit 43 = 0: serial identification number is assigned nationally; or
bit 43 = 1: identification data include the C/S type approval certificate
number.
5. Test User Protocol 111
6. Orbitography Protocol 000
7. National User Protocol * 100
8. Spare 101
A2-B: Standard Location and National Location Protocols (F=1, P=0) long message
Protocol Codes
(Bits 37 - 40)
Standard Location Protocols
1. EPIRB - MMSI/Location Protocol 0010
2. ELT - 24-bit Address/Location Protocol 0011
3. Serial Location Protocols a) ELT - serial 0100
b) ELT - aircraft operator designator 0101
c) EPIRB-serial 0110
d) PLB-serial 0111
4. Ship Security 1100
5. National Location Protocol
a) ELT 1000
b) EPIRB 1010
c) PLB 1011
6. Test location Protocols
a) Standard Test Location Protocol 1110
b) National Test Location Protocol 1111
7. RLS Location Protocol 1101
8. Reserved (orbitography) 0000, 0001
9. Spare 1001
* The National User Protocol has certain bits which are nationally defined, as described in section A2.8.
A-5 C/S T.001 - Issue 3 - Rev.14
October 2013
A2 USER PROTOCOLS
This section defines the user protocol message formats which can be used to encode the
beacon identification and other data in the message transmitted by a 406 MHz distress
beacon.
A2.1 Structure of User Protocols
The user protocols have the following structure:
bits usage
25 format flag (short message=0, long message =1)
26 protocol flag (=1)
27-36 country code
37-39 protocol code
40-83 identification data
84-85 auxiliary radio-locating device type(s)
Bits 37-39 in the protocol code field designate one of the user protocol codes as listed in
Table A2-A, and indicate how the remaining bits of identification data are encoded/decoded.
Bits 40-83 are used to encode the identification data of the beacon and, together with the
protocol flag, the country code, the protocol code, and bits 84-85, shall form a unique
identification for each beacon, i.e. the beacon 15 Hex ID. They will be discussed separately
for each user protocol.
Bits 84-85 are used to indicate for all user protocols excluding the orbitography protocol, the
type of auxiliary radio-locating device(s) forming part of the particular beacon. The
assignment of bits is as follows:
bits 84-85 auxiliary radio-locating device type

00 no auxiliary radio-locating device
01 121.5 MHz
10 maritime 9 GHz Search and Rescue Radar Transponder (SART)
11 other auxiliary radio-locating device(s)
If other auxiliary radio-locating device(s) is (are) used in addition to 121.5 MHz, the code for
121.5 MHz (i.e. 01) should be used.
The bit assignments for user protocols, in PDF-1 of the 406 MHz beacon digital message, are
summarized in Figure A3.
A-6 C/S T.001 - Issue 3 - Rev.14
October 2013
Figure A3: Bit Assignment for the First Protected Data Field (PDF-1) of User Protocols
1. MARITIME USER PROTOCOL

Bits 25 26 27 36 37 39 40 81 82 83 84 85
..... 0 1 Country Code 0 1 0 MMSI or Radio Call Sign (42 bits) 0 0 R L
2. RADIO CALL SIGN USER PROTOCOL

Bits 25 26 27 36 37 39 40 81 82 83 84 85
..... 0 1 Country Code 1 1 0 Radio Call Sign (42 bits) 0 0 R L
3. SERIAL USER PROTOCOL

Bits 25 26 27 36 37 39 40 42 43 44 73 74 83 84 85
..... 0 1 Country Code 0 1 1 T T T C Serial Number and other Data C/S Cert. No or R L
National Use
4. AVIATION USER PROTOCOL

Bits 25 26 27 36 37 39 40 81 82 83 84 85
1
..... 0 1 Country Code 0 0 1 Aircraft Registration Marking (42 bits) EN R L
5. NATIONAL USER PROTOCOL

Bits 25 26 27 36 37 39 40 85
...... F 1 Country Code 1 0 0 National Use (46 bits)
6. TEST USER PROTOCOL

Bits 25 26 27 36 37 39 40 85
..... F 1 Country Code 1 1 1 Test Beacon Data (46 bits)
7. ORBITOGRAPHY PROTOCOL
Bits 25 26 27 36 37 39 40 85
...... F 1 Country Code 0 0 0 Orbitography Data (46 bits)
Notes: RL = Auxiliary radio-locating device (see section A2.1)

TTT = 000 - ELT with serial number 010 - float free EPIRB with serial number
011 - ELT with 24-bit aircraft address 100 - non float free EPIRB with serial number
001 - ELT with aircraft operator 110 - personal locator beacon (PLB) with serial number
designator and serial number
C = C/S Type Approval Certificate Flag:
"1" = C/S Type Approval Certificate number encoded in bits 74 to 83
"0" = other national use
F = Format Flag ("0" = short message, "1" = long message)
EN = Specific ELT number on designated aircraft (see section A2.4) 1
1
Effective as of 1 November 2011.
A-7 C/S T.001 - Issue 3 - Rev.14
October 2013
Table A3: Modified-Baudot Code
Letter Code Letter Code Figure Code

MSB LSB MSB LSB MSB LSB
A 111000 N 100110 ( )* 100100

B 110011 O 100011 ( - )** 011000
C 101110 P 101101 / 010111
D 110010 Q 111101 0 001101
E 110000 R 101010 1 011101
F 110110 S 110100 2 011001
G 101011 T 100001 3 010000
H 100101 U 111100 4 001010
I 101100 V 101111 5 000001
J 111010 W 111001 6 010101
K 111110 X 110111 7 011100
L 101001 Y 110101 8 001100
M 100111 Z 110001 9 000011
MSB: most significant bit * Space

LSB: least significant bit ** Hyphen
Note: The modified-Baudot code is used to encode alphanumeric characters in EPIRB messages containing
MMSI or radio call sign identification, and in ELTs containing the aircraft registration marking or the
3-letter aircraft operator designator.
A2.2 Maritime User Protocol
The maritime user protocol has the following structure:
Bits Usage
25 format flag (=0)
27-36 country code
37-39 user protocol code (=010)
40-75 radio call sign or trailing 6 digits of MMSI
76-81 specific beacon number
82-83 spare (=00)
Bits 40-75 designate the radio call sign or the last 6 digits of the 9 digit maritime mobile
service identity (MMSI) using the modified-Baudot code shown in Table A3.
A-8 C/S T.001 - Issue 3 - Rev.14
October 2013
This code enables 6 characters to be encoded using 36 bits (6x6 = 36). This data will be right
justified with a modified-Baudot space (100100) being used where no character exists. If all
characters are digits, the entry is interpreted as the trailing 6 digits of the MMSI.
Bits 76 to 81 are used to identify specific beacons on the same vessel (the first or only float
free beacon shall be coded with a modified-Baudot zero (001101); additional beacons shall
be numbered consecutively using modified-Baudot characters 1 to 9 and A to Z).
The maritime user and the radio call sign user protocols may be used for beacons that require
coding with a radio call sign. The maritime user protocol may be used for radio call signs of
6 or fewer characters. Radio call signs of 7 characters must be encoded using the radio call
sign user protocol.
A2.3 Radio Call Sign User Protocol
The radio call sign user protocol is intended to accommodate a vessel's radio call sign of up
to seven characters, where letters may be used only in the first four characters, thereby
complying with the ITU practice on formation of radio call signs.
The radio call sign user protocol has the following structure:
Bits Usage
25 format flag (=0)
27-36 country code
40-75 radio call sign
 40-63 first 4 characters (modified-Baudot)
 64-75 last 3 characters (binary-coded decimal)
76-81 specific beacon number
82-83 spare (=00)
Bits 40 to 75 contain the radio call sign of up to 7 characters. Radio call signs of fewer than
7 characters should be left justified in the radio call sign field (bits 40-75) and padded with
"space" (1010) characters in the binary-coded decimal field (bits 64-75).
Bits 76 to 81 are used to identify specific beacons on the same vessel (the first or only float
free beacon shall be coded with a modified-Baudot zero (001101); additional beacons shall
be numbered consecutively using modified-Baudot characters 1 to 9 and A to Z).
A-9 C/S T.001 - Issue 3 - Rev.14
October 2013
A2.4 Aviation User Protocol
The aviation user protocol has the following structure:
Bits Usage
25 format flag (=0)
27-36 country code
40-81 aircraft registration marking
82-83 specific ELT number 
Bits 40-81 designate the aircraft registration marking which is encoded using the modified-
Baudot code shown in Table A3. This code enables 7 characters to be encoded using 42 bits
(6x7=42). This data will be right justified with a modified-Baudot space (100100) being used
where no character exists.
Bits 82-83 are used to create a unique ELT identification when several ELTs coded with the
Aviation User protocol are installed on the same aircraft. “00” indicates the first ELT on the
aircraft coded with this protocol and “01”, “10” and “11” identify additional ELTs, all coded
with the Aviation User protocol. 1
A2.5 Serial User Protocol
The serial user protocol is intended to permit the manufacture of beacons whose 15 Hex ID
will be identified in a data base giving specifics about the unit. The following types of serial
identification data can be encoded in the beacon:
 serial number
 24-bit aircraft address number
 aircraft operator designator and a serial number.
Bits 40-42 indicate the beacon type with serial identification data encoded, as follows:
000 indicates an aviation ELT serial number is encoded in bits 44-63

010 indicates a maritime float free EPIRB serial number is encoded in bits 44-63
100 indicates a maritime non float free EPIRB serial number is encoded in bits 44-63
110 indicates a personal locator beacon (PLB) serial number is encoded in bits 44-63
011 indicates the aircraft 24-bit address is encoded in bits 44-67 and specific ELT
number in bits 68-73 if several ELTs, encoded with the same 24 bit address, are
carried in the same aircraft
001 indicates an aircraft operator designator and a serial number are encoded in bits
44-61 and 62-73, respectively.
Bit 43 is a flag bit to indicate that the Cospas-Sarsat type approval certificate number is
encoded.

A - 10 C/S T.001 - Issue 3 - Rev.14
October 2013
If bit 43 is set to 1:
- bits 64-73 should either be set to all 0s or allocated for national use and control (and
will be made public when assigned by the responsible administration) or used as
defined for coding the aircraft 24-bit address or aircraft operator designator;
- bits 74-83 should be encoded with the Cospas-Sarsat type approval certificate number
which is assigned by the Cospas-Sarsat Secretariat for each beacon model approved
according to the type approval procedure of document C/S T.007. The certificate
number is to be encoded in binary notation with the least significant bit on the right.
If bit 43 is set to 0:
- bits 64-83 are for national use and control (and will be made public when assigned by
the responsible administration) or used as defined for coding the aircraft 24-bit address
or aircraft operator designator.
Details of each type of serial identification data are given hereunder.
A2.5.1 Serial Number
The serial user protocol using a serial number encoded in the beacon message has the
following structure:
Bits 25 26 27 36 37 40 44 63 64 73 74 83 85
---+--+--+------------+-----+-----+-+-----------------+-------------+-------------+---+-
¦ ¦ ¦ Country ¦ ¦ ¦ ¦ (20 bits) ¦ All "0" or ¦ C/S cert. No. ¦
¦0 ¦1 ¦ Code ¦0 1 1¦T T T¦C¦ Serial Number ¦ Nat. Use ¦ or Nat. Use ¦R L¦
---------------------------------------------------------------------------------------
Bits Usage
25 format flag (= 0)
27-36 country code
40-42 beacon type (=000, 010, 100 or 110)
43 flag bit for Cospas-Sarsat type approval certificate number
44-63 serial number
64-73 all 0s or national use
74-83 C/S type approval certificate number or national use
Bits 44-63 designate a serial identification code number ranging from 0 to 1,048,575
(i.e. 220-1) expressed in binary notation, with the least significant bit on the right.
This serial number encoded in the beacon message is not necessarily the same as the
production serial number of the beacon.
A - 11 C/S T.001 - Issue 3 - Rev.14
October 2013
A2.5.2 Aircraft 24-bit Address
The serial user protocol using the aircraft 24-bit address has the following structure:
Bits 25 26 27 36 37 40 44 67 68 73 74 83 85
---+--+--+------------+-----+-----+-+-----------------+-------------+-------------+---+-
¦ ¦ ¦ Country ¦ ¦ ¦ ¦ Aircraft ¦ Additional ¦ C/S Cert.No.¦ ¦
¦0 ¦1 ¦ Code ¦0 1 1¦0 1 1¦C¦ 24-bit Address ¦ ELT No.s ¦ or Nat. Use ¦R L¦
---------------------------------------------------------------------------------------
Bits Usage
25 format flag (= 0)
27-36 country code
40-42 beacon type (=011)
44-67 aircraft 24-bit address
68-73 specific ELT number, if several ELTs encoded with the
same 24-bit address are carried in the same aircraft
Bits 44-67 are a 24-bit binary number assigned to the aircraft. Bits 68-73 contain the
6-bit specific ELT number, in binary notation with the least significant bit on the right,
which is an order number of the ELT in the aircraft or default to “0” when only one
ELT is carried; the purpose of this specific number is to produce different 15 Hex
numbers containing the same 24-bit address.
A2.5.3 Aircraft Operator Designator and Serial Number
The serial user protocol using the aircraft operator designator and serial number has the
following structure:
Bits 25 26 27 36 37 40 44 61 62 73 74 83 85
---+--+--+------------+-----+-----+-+-------------------+-----------+-------------+---+-
¦ ¦ ¦ Country ¦ ¦ ¦ ¦ Operator 3-letter ¦ Serial ¦ C/S Cert. No. ¦
¦0 ¦1 ¦ Code ¦0 1 1¦0 0 1¦C¦ Designator ¦ Number ¦ or Nat. Use ¦R L¦
---------------------------------------------------------------------------------------
Bits Usage
25 format flag (=0)
27-36 country code
40-42 beacon type (=001)
44-61 aircraft operator designator
62-73 serial number assigned by operator
A - 12 C/S T.001 - Issue 3 - Rev.14
October 2013
Bits 44-61 are a 3-letter aircraft operator designator from the list* of "Designators for
Aircraft Operating Agencies, Aeronautical Authorities and Services" published by the
International Civil Aviation Organization (ICAO). The 3 letters are encoded using the
modified-Baudot code of Table A3.
Bits 62 to 73 are a serial number (in the range of 1 up to 4095) as designated by the
aircraft operator, encoded in binary notation, with the least significant bit on the right.
A2.6 Test User Protocol
The test user protocol will be used for demonstrations, type approval, national tests, training
exercises, etc.. Mission Control Centres (MCCs) will not forward messages coded with this
protocol unless requested by the authority conducting the test.
The test user protocol has the following structure:
Bits Usage
25 format flag (short message = 0, long message = 1)
27-36 country code
37-39 test user protocol code (=111)
40-85 national use
2.7 Orbitography Protocol
The orbitography protocol is for use by special system calibration transmitters and is intended
for use only by operators of the Local User Terminals. Therefore, it is not further described
in this document.
_________________
* The list of designators, comprising about 3000 operating agencies, authorities or services world-wide, is
published by ICAO in document 8585, and can be purchased from ICAO in printed and electronic form.
A - 13 C/S T.001 - Issue 3 - Rev.14
October 2013
A2.8 National User Protocol
The national user protocol is a special coding format having certain data fields, indicated as
"national use", which are defined and controlled by the national administration of the particular
country which is coded into the country code field.
The national user protocol may be either a short or a long message, as indicated by the format flag
(bit 25). The correct BCH code(s) must be encoded in bits 86-106, and in bits 133-144 if a long
message is transmitted.
The national user protocol has the following structure:
Bits 25 26 27 36¦37 ¦40 85 86 106 107 132¦133 144¦

---+--+--+----------+-----+---------------------------+-------------+-------------¦--------¦
¦ ¦ ¦ Country ¦ ¦ National Use ¦ BCH Code ¦National Use BCH Code¦
¦F ¦1 ¦ Code ¦1 0 0¦ (46 bits) ¦ (21 bits) ¦ (26 bits) ¦(12 bits)
---------------------------------------------------------------------------------¦--------¦
Bits Usage
25 format flag (short message =0, long message =1)
27-36 country code
37-39 national user protocol code (=100)
40-85 national use
86-106 21-bit BCH code
107-112 national use
113-132 national use (if long message)
133-144 12-bit BCH code (if long message)
Once the beacon has been activated, the content of the message in bits 1 to 106 must remain fixed,
but bits 107 onwards are permitted to be changed periodically, provided the correct 12-bit BCH
code is also recomputed and that such changes do not occur more frequently than once every 20
minutes.
It should be noted that distress alert messages encoded with the national user protocol can be
passed within the Cospas-Sarsat System only as hexadecimal data, and the content of the message
can only be interpreted by the appropriate national administration.
A2.9 Non-Protected Data Field
The non-protected data field consists of bits 107 to 112, which can be encoded with emergency
code / national use data as described below. However, when neither the emergency code nor the
national use data have been implemented, nor such data entered, the following default coding
should be used for bits 107 to 112:
A - 14 C/S T.001 - Issue 3 - Rev.14
October 2013
000000: for beacons that can be activated only manually, i.e.

bit 108 = 0 (see below)
010000: for beacons that can be activated both manually and automatically, i.e. bit 108 =
1 (see below).
Bit 107 is a flag bit that should be automatically set to (=1) if emergency code data has been
entered in bits 109 to 112, as defined below.
Bit 108 indicates the method of activation (the switching mechanism) that has been built into the
beacon:
bit 108 set to (=0) indicates that a switch must be manually set to “on” after the time of the
distress to activate the beacon;
bit 108 set to (=1) indicates that the beacon can be activated either manually or
automatically.
A float-free beacon shall have bit 108 set to 1.
A2.9.1 Maritime Emergency code
The emergency code is an optional feature that may be incorporated in a beacon to permit
the user to enter data in the emergency code field (bits 109-112) after beacon activation of
any maritime protocol (i.e. maritime user protocol, maritime serial user protocols, and radio
call sign user protocol). If data is entered in bits 109 to 112 after activation, then bit 107
should be automatically set to (=1) and bits 109 to 112 should be set to an appropriate
maritime emergency code shown in Table A4. If a beacon is pre-programmed, bits 109 to
112 should be coded as "unspecified distress" (i.e. 0000).
A2.9.2 Non-Maritime Emergency code
The emergency code is an optional feature that may be incorporated in a beacon to permit
the user to enter data in the emergency code field (bits 109-112) of any non-maritime
protocol (i.e. aviation user protocol, serial user aviation and personal protocols, or other
spare protocols). If data is entered in bits 109 to 112, then bit 107 should be automatically
set to (=1) and bits 109 to 112 should be set to an appropriate non-maritime emergency code
shown in Table A5.
A - 15 C/S T.001 - Issue 3 - Rev.14
October 2013
Table A4: Maritime Emergency Codes in Accordance with the

Modified (1) IMO Nature of Distress Indication
IMO Binary Usage

Indication(2) Code
1 0001 Fire/explosion
2 0010 Flooding
3 0011 Collision
4 0100 Grounding
5 0101 Listing, in danger of capsizing
6 0110 Sinking
7 0111 Disabled and adrift
8 0000 Unspecified distress (3)
9 1000 Abandoning ship
1001 to 1111 Spare (could be used in future for assistance
desired or other information to facilitate the
rescue if necessary)
(1)
Modification applies only to code "1111", which is used as a "spare" instead of as the "test" code.
(2)
IMO indication is an emergency code number, it is different from the binary encoded number.
(3)
If no emergency code data has been entered, bit 107 remains set to (=0).
Table A5: Non-Maritime Emergency Codes
Bits Usage (1)

109 No fire (=0); fire (=1)
110 No medical help (=0); medical help required (=1)
111 Not disabled (=0); disabled (=1)
112 Spare (=0)
(1)
If no emergency code data has been entered, bit 107 remains set to (=0).
A2.9.3 National Use
When bit 107 is set to (=0), codes (0001) through (1111) for bits 109 to 112 may be used for
national use and should be set in accordance with the protocol of an appropriate national
authority.
Figure A4: Summary of User Protocols Coding Options
b 25: Message format flag: 0 = short message, 1 = long message
b 26: Protocol flag: 1 = User protocols
b 27 - b 36: Country code number: 3 digits, as listed in Appendix 43 of the ITU Radio Regulations
b 37 - b 39: User protocol code: 000 = Orbitography 110 = Radio call sign
001 = Aviation 111 = Test
010 = Maritime 100 = National
011 = Serial 101 = Spare
b 37 - b 39: 010 = Maritime user 110 = Radio call sign user 011 = Serial user 001 = Aviation user 100 = National User
b 40 - b 75: Trailing 6 digits of b 40 - b 63: First four characters b 40 - 42: Beacon type b 40 - b 81: Aircraft Registration b 40 - 85:
MMSI or radio call (modified-Baudot) 000 = Aviation Marking (modified - National use
sign (modified- 001 = Aircraft Operator Baudot)
Baudot) 011 = Aircraft Address
010 = Maritime (float free)
100 = Maritime (non float free)
110 = Personal
b 43: C/S Certificate flag

b 64 - b 75: Last three characters b 44 - b 73: Serial No. and
(binary coded decimal) other data
A - 16
b 76 - b 81: Specific beacon b 76 - b 81: Specific beacon b 74 - b 83: C/S Cert. No. or
(modified-Baudot) (modified-Baudot) National use
b 82 - b 83: 00 = Spare b 82 - b 83: 00 = Spare b 82 - b 83: Specific ELT
number
b 84 - 85: Auxiliary radio-locating device type(s): 00 = No Auxiliary radio-locating device
01 = 121.5 MHz
10 = Maritime locating: 9 GHz SART
11 = Other auxiliary radio-locating device(s)
b 86 - b 106: BCH code: 21-bit error-correcting code for bits 25 to 85
b 107: Emergency code use of b 109 - b 112: 0 = National use, undefined (default = 0) b 107 - 112:
1 = Emergency code flag National use
b 108: Activation type: 0 = Manual activation only
1 = Automatic and manual activation
b 109 - b 112: Nature of distress: Maritime emergency codes (see Table A.4) (default = 0000)
Non-maritime emergency codes (see Table A5) (default = 0000)

October 2013
C/S T.001 - Issue 3 - Rev.14

A - 17 C/S T.001 – Issue 3 – Draft Rev.14
October 2013
A3 LOCATION PROTOCOLS
This section defines the protocols which can be used with the 406 MHz beacon message formats
for encoding beacon position data, as well as the beacon identification data, in the digital
message transmitted by a 406 MHz distress beacon.
A3.1 Summary
Four types of location protocols are defined for use with the long message†, as shown in
Figure A5.
User-Location Protocols. These location protocols are for use with the long message
format. The beacon identification data is provided in PDF-1 by one of the user protocols
defined in section A2 (see Figure A3). Position data is provided as latitude and longitude,
to 4-minute resolution, encoded into PDF-2.
Standard Location Protocols. These location protocols are for use with the long message
format. The beacon identification data is provided in a standardized format in 24 bits of
PDF-1. Position data to 15-minute resolution is also given in PDF-1, with position offsets
to 4-second resolution in PDF-2.
National Location Protocol. This location protocol is for use with the long message
format. The beacon identification data is provided in a nationally-defined format in 18 bits
of PDF-1. Position data, to 2-minute resolution, is given in PDF-1, with position offsets to
4-second resolution in PDF-2.
Return Link Service (RLS) Location Protocol‡. This location protocol is for use with
the long message format. The beacon identification data is provided in 18 bits of PDF-1
where the first two bits define the beacon type and the remaining 16 bits are nationally
defined. Position data, to 2-minute resolution, is given in PDF-1, with position offsets to
4-second resolution in PDF-2.
A3.2 Default Values in Position Data
The following default values shall be used in all encoded position data fields of the location
protocols, when no valid data is available:
a) all bits in degrees fields set to "1", with N/S, E/W flags set to "0";
b) all bits in the minutes fields set to "0", with  signs set to "1"; and
c) all bits in the seconds fields set to "1" (the value "1111" = 60 sec is out of range).
†
Cospas-Sarsat no longer permits the use of short format location protocols. Information on these protocols is
available in C/S T.001, Issue 3- Revision 7.
‡
These protocols will be effective as of 1 November 2015.
A - 18 C/S T.001 – Issue 3 – Draft Rev.14
October 2013
This pattern shall also be transmitted if the beacon radiates a 406 MHz message in the self-test
mode. Additionally, if a location protocol beacon includes an optional GNSS self-test and this
fails to provide a valid location to encode into the transmitted self-test message, then the beacon
may radiate a single self-test message with the above default data. However if a location
protocol beacon with optional GNSS self-test obtains a location, then the beacon may radiate a
single self-test message with encoded position.
Figure A5: Outline of Location Protocols
U s e r - L o c a t i o n P r o t o c o l s
bit bits bits 40-83 bits bits 86-106 bit 107 bits 108-132 bits
26 27-39 84-85 133-144
Radio-
Identification Data (44 bits) locating 21-Bit Posit. Data Position Data to 4 min 12-Bit
1 ....... Device BCH code Source Resolution (25 bits) BCH code
S t a n d a r d L o c a t i o n P r o t o c o l s
bit bits bits 41-64 bits 65-85 bits 86-106 bits 107-112 bits 113-132 bits
26 27-40 133-144
Identification Data Position Data to 15 min 21-Bit Supplementary Position Data to 4 sec 12-Bit
0 ....... (24 bits) Resolution (21 bits) BCH code Data Resolution (20 bits) BCH code
N a t i o n a l L o c a t i o n P r o t o c o l
bit bits bits 41-58 bits 59-85 bits 86-106 bits 107-112 bits 113-126 bits bits
26 27-40 127-132 133-144
Identification Data Position Data to 2 min 21-Bit Supplementary Position Data to 4 sec National 12-Bit
0 ....... (18 bits) Resolution (27 bits) BCH code Data Resolution (14 bits) Use BCH code
RLS L o c a t i o n P r o t o c o l
bit bits Bits bits 43-58 bits 59-85 bits 86-106 bits 107-112 bits 113-126 bits bits
26 27-40 41-42 127-132 133-144
Beacon Identification Position Data to 2 min 21-Bit Supplementary Position Data to 4 RLS Use 12-Bit
0 ....... Type Data Resolution BCH code sec Resolution (14 BCH code
Data bits)
(2 bits) (16 bits) (27 bits)
A - 19 C/S T.001 – Issue 3 – Draft Rev. 14
October 2013
A3.3 Definition of Location Protocols
The general structure of location protocols is illustrated in Figure A6.
A3.3.1 Position Data (1)
All position information is encoded as degrees, minutes and seconds of latitude or

longitude, or as fractions of these units. Latitude and longitude data are rounded off
(i.e. not truncated) to the available resolution. All rounding shall follow normal rounding
conventions, for example with a resolution of 4, 0.000 to 1.999 shall be rounded down to 0
and 2.000 to 3.999 shall be rounded up to 4. In each location field the Most Significant Bit
(MSB) is the lowest numbered bit in the message which is not a N/S, E/W or Δ sign flag
bit.
For User Location Protocols, the position encoded in PDF-2 shall be as close as possible to
the actual position.
For Standard Location, National Location, and RLS Location Protocols the position is
encoded as follows. The coarse position encoded in PDF-1 is selected to be as close as
possible to the actual position. The actual position is then rounded following the above
rules to the nearest 4 second. The offset to be encoded in PDF-2 is then calculated by
subtracting the coarse position encoded in PDF-1 from the rounded position, ensuring that
the sign of the offset is included in PDF-2 (2). If there is no offset in either latitude or
longitude (or both) in PDF-2 (i.e. the offset minutes and seconds are all zeroes) then the
appropriate offset data flag shall be set to its default value (i.e. 1).
When a position is encoded in PDF-1, the higher resolution information given in PDF-2 is
an offset ( latitude and  longitude) relative to position provided in PDF-1.
The latitude and longitude values contained in PDF-1 are positive numbers regardless of
their directions. The offset is applied by adding or subtracting the offset value in
accordance with the offset sign in PDF-2. For example:
100° E. longitude + 30 offset = 100° 30 E. longitude

100° W.longitude + 30 offset = 100° 30 W. longitude (not 99° 30 W. longitude)
100° W.longitude - 30 offset = 99° 30W. longitude (not 100° 30 W. longitude).
________________________
(1)
Beacons submitted for type approval testing prior to 1 November 2010 may at manufacturers choice
use the location protocol coding system defined in A3.3.1 or the previous system as defined in section A3.3.1 of
document C/S T.001, Issue 3 - Revision 8. Manufacturers who choose to use the location encoding system
defined in A3.3.1 may use the answer sheets in C/S T.007, Issue 3 - Revision 9. Manufacturers who submit for
type approval testing after 1 November 2010 must use the answer sheets in C/S T.007, Issue 3 - Revision 10.
(2)
Note that the encoded location in PDF-1 will be closest to the actual, but in some cases may not be the
closest location to the rounded location.
A - 20 C/S T.001 – Issue 3 – Rev. 14
October 2013
A3.3.2 Supplementary Data
The following supplementary data are provided in location protocols, in addition to the
required identification data and available position data.
A3.3.2.1 Source of Position Data
This information is encoded in bit 107 for the user-location protocol or bit 111 for the
standard and national location protocols with the following interpretation:
"0" = the encoded position data is provided by an external navigation device

"1" = the encoded position data is provided by an internal navigation device
.
A3.3.2.2 Auxiliary Radio Locating Device (homing transmitter) Code
The "121.5 MHz homing" data is encoded in bit 112 for the standard and national location
protocols (short and long versions) where:
"1" = indicates a 121.5 MHz auxiliary radio locating device

"0" = indicates other or no auxiliary radio locating devices;
and in bits 84-85 for the user-location protocols as follows:
"00" = no auxiliary radio locating device

"01" = 121.5 MHz auxiliary radio locating device
"10" = maritime locating: 9 GHz Search and Rescue Radar Transponder (SART)
"11" = other auxiliary radio-locating device(s).
A3.3.3 Test Location Protocols
The test protocol for all coding methods (i.e. "user" and "location" protocols) is encoded by
setting bits 37-39 (protocol code) to "111". In addition, bit 40 is used to distinguish
between the test format of the standard location protocols (bit 40 = "0") and national
location protocols (bit 40 = "1").
Figure A6: General Format of Long Message for Location Protocols
1 25 27 37 40 41 84 86 107 113 133
24 26 36 39  83 85 106 112  132 144

----------- 61 BITS ---------- BCH-1 ------ 26 BITS ------ BCH-2
PDF-1 PDF-2
2 10 4 45 21 6 20 12
3 USER-LOCATION PROTOCOLS 2 USER-LOCATION PROTOCOLS

F (P=1)
O C 010
R O 110 Identification Data Latitude / Longitude Data
M U 001 (same as User Protocols) (4 Minute Resolution)
A N 011
T T 111 See Figure A7 See Figure A7
BIT & FRAME R 4 STANDARD LOCATION PROTOCOLS 21-BIT BCH ERROR STANDARD LOCATION PROTOCOLS 12-BIT BCH ERROR
P &
& Y 0010 (P=0) CORRECTING CODE CORRECTING
SYNCHRONIZAT.
R 0011  Latitude /  Longitude CODE
PATTERNS
E P 0100 Identification & Position Data (4 Second Resolution)
A - 21
A R 0101 (1/4 Degree Resolution) + Supplementary Data

M O C 0110
B T O 0111 See Figure A8 See Figure A8
L O D 1100
E C E 1110
O
4 NATIONAL LOCATION PROTOCOLS NATIONAL LOCATION PROTOCOLS
L
(P=0)
1000  Latitude /  Longitude
1001 Identification & Position Data (4 Second Resolution)
1010 (2 Minute Resolution) + Supplementary Data
F 1011
L 1111 See Figure A9 See Figure A9
A
G 4 RLS LOCATION PROTOCOLS RLS LOCATION PROTOCOLS
S (P=0)
 Latitude /  Longitude
Identification & Position Data (4 Second Resolution)
1101 (2 Minute Resolution) + Supplementary Data
See Figure A10 See Figure A10
 
F= 1 PROTOCOL CODE LONG MESSAGE FORMAT - 144 BITS
P= 0 or 1 See Table A2
October 2013
C/S T.001 – Issue 3 – Rev.14
A - 22 C/S T.001 – Issue 3 – Rev. 14
October 2013
A3.3.4 User-Location Protocols (See Figure A7)
A3.3.4.1 These protocols (identified by F=1, P=1) provide for encoding latitude / longitude
data with resolution to 4 minutes in PDF-2. Beacon identification data shall be
encoded in PDF-1 using any of the user protocols defined in section 2, except the
orbitography protocol and the national user protocol which are specific to a
particular application or a particular country.
A3.3.4.2 The protocol codes (bits 37 to 39) are defined in Table A2-A for user and
user-location protocols.
A3.3.4.3 The 26 bits available in PDF-2 are defined as follows:
a) bit 107: encoded position data source

"1" = the encoded position data is provided by an internal navigation device;
b) bits 108 to 119: latitude data (12 bits) with 4 minute resolution, including:
 bit 108: N/S flag (N=0, S=1)

 bits 109 to 115: degrees (0 to 90) in 1 degree increments
 bits 116 to 119: minutes (0 to 56) in 4 minute increments
(default value of bits 108 to 119 = 0 1111111 0000); and
c) bits 120 to 132: longitude data (13 bits) with 4 minute resolution including:
 bit 120: E/W flag (E=0, W=1)

 bits 121 to 128: degrees (0 to 180) in 1 degree increments
 bits 129 to 132: minutes (0 to 56) in 4 minute increments
(default value of bits 120 to 132 = 0 11111111 0000).
Figure A7: User-Location Protocols
1 25 27 37 | 86 107 113 133

|40 85
24 26 36 39| 83| 106 112 132 144
------ 61 BITS ----- BCH-1 ------ 26 BITS ----- BCH-2

PDF-1 PDF-2
2 10 3 44 2 21 1 12 13 12
F C P
O O R
IDENTIFICATION DATA POSITION DATA
R U O
(ALL USER-LOCATION PROTOCOLS)
M N T
A T O
T R C
Y O
BIT & FRAME & L 21-BIT BCH ERROR 12-BIT BCH
P MARITIME USER PROTOCOL 1
SYNCHRONIZ. C CORRECTING CODE ERROR
R (MMSI OR RADIO CALL SIGN) LATITUDE LONGITUDE
O C CORRECTING
E
PATTERNS P D O CODE
A (PC=010)
R E D
M
B O E
RADIO CALL SIGN USER PROTOCOL 1 7 4 1 8 4
L T
(PC) (PC=110)
A - 23
E O
C
O
AIRCRAFT NATIONALITY AND
L N DEG MIN E DEG MIN
REGISTRATION MARKINGS
/ 0 - 90 0 - 56 / 0 - 180 0 - 56
(PC=001)
S (1 deg.) (4min) W (1 deg.) (4min)
F
L
SERIAL USER PROTOCOL
A
(ELTs, PLBs, EPIRBs)
G
(PC=011)
S
    84,85 = Homing  107 = Encoded Position Data source: 1= Internal, 0 = external
F=1 See See Figure A3 for details
P=1 Table A2 of identification data
October 2013
C/S T.001 - Issue 3 - Rev.14
A - 24 C/S T.001 – Issue 3 – Rev. 14
November 2013
A3.3.5 Standard Location Protocols (see Figure A8)
A3.3.5.1 The standard location protocols, identified by the flags F=1, P=0 and the protocol
codes no. 1 to 4 of Table A2-B, have the following structure:
a) PDF-1:
bits 37 to 40: 4-bit protocol code as defined in Table A2-B

bits 41 to 64: 24 bits of identification data
bits 65 to 85: 21 bits of encoded position data to 15 minute resolution;
b) PDF-2:
bits 107 to 112: 4 fixed bits and 2 bits of supplementary data

bits 113 to 132 20-bit position offset ( latitude,  longitude), to 4 second
resolution.
A3.3.5.2 The 24 bits of identification data (bits 41 to 64) can be used to encode:
a) (PC=0010) the last six digits of MMSI in binary form in bits 41 to 60 (20 bits), plus
a 4-bit specific beacon number (0 to 15) in bits 61 to 64, to distinguish between
several EPIRBs on the same ship;
b) (PC=0011) a 24-bit aircraft address (only one ELT per aircraft can be identified
using this protocol); or
c) (PC=01xx, see Note 1) a 24-bit unique serial identification including:
(i) the 10-bit Cospas-Sarsat type approval certificate number of the beacon
(1 to 1,023) in bits 41 to 50, and a 14 bit serial number (1 to 16,383) in
bits 51 to 64; or
(ii) a 15-bit aircraft operator designator (see Notes 1 & 2) in bits 41 to 55, and a 9-
bit serial number (1 to 511) assigned by the operator in bits 56 to 64.
d) (PC=1100) the last six digits of MMSI in binary form in bits 41 to 60 (20 bits), plus
four spare fixed bits, 61 to 64, set to “0000”.
A3.3.5.3 The 21 bits of position data in PDF-1 are encoded as follows:
a) bits 65 to 74: latitude data (10 bits) providing 15 minute resolution, including:
• bit 65: N/S flag (N=0, S=1)
• bits 66 to 74: degrees (0 to 90) in 1/4 degree increments
(default value of bits 65 to 74 = 0 111111111); and
________________
Notes: 1. The last two bits of the protocol code (bits 39-40) are used as follows (see also Table A2):
00 ELT-serial 10 EPIRB-serial
01 ELT-aircraft operator designator 11 PLB-serial
2. The aircraft operator designator (3 letters) can be encoded in 15 bits using a shortened form of
the modified-Baudot code (i.e.: all letters in the modified-Baudot code are coded in 6 bits, with
the first bit = "1". This first bit can, therefore, be deleted to form a 5-bit code).
b) bits 75 to 85: longitude data (11 bits) providing 15 minute resolution, including:
• bit 75: E/W flag (E=0, W=1)
• bits 76 to 85: degrees (0 to 180) in 1/4 degree increments
(default value of bits 75 to 85 = 0 1111111111).
a) bits 107 to 109: ="110" (fixed);
b) bit 110: ="1" (fixed);
c) bit 111: encoded position data source

d) bit 112: 121.5 MHz auxiliary radio locating device included in beacon (1 = yes, 0 = no); 121.5 MHz auxiliary radio locating devices
are not authorised for beacons coded with the ship security format (i.e. when bits 37 – 40 = 1100);
e) bits 113 to 122:  latitude with 4 second resolution:

• bit 113:  sign (0 = minus, 1 = plus)
• bits 114 to 118: Minutes (0 to 30) in 1 minute increments *
• bits 119 to 122: Seconds (0 to 56) in 4 second increments
f) bits 123 to 132:  longitude with 4 second resolution:

• bits 124 to 128: Minutes (0 to 30) in 1 minute increments *
• bits 129 to 132: Seconds (0 to 56) in 4 second increments
A3.3.5.5 The test protocol using the above format is encoded by setting bits 37-39 to "111" and bit 40 to "0".
__________________________
* A3.3.5 defines the coding scheme for all Standard Location Protocols, some newer beacons where the coarse position in PDF-1 is always selected to be as close as possible to
the actual position will have a maximum offset in PDF-2 of +/- 7 minutes 30 seconds, in which case bits 114, 115, 124 and 125 of the message will not be used and should be
permanently set to “0”. Figure A8: Standard Location Protocols
1 25 27 37 86 107 113 133
24 26 36 40|41 85 106 112 132 144

|
----------- 61 BITS ------------ BCH-1 ------- 26 BITS -------- BCH-2

PDF-1 PDF-2
2 10 4 45 21 6 20 12
F PC 24 BITS 21 BITS S  LATITUDE  LONGITUDE

O IDENTIFICATION DATA LATITUDE U
R LONGITUDE P
M C P
A O 20 4 1 9 1 10 L 1 5 4 1 5 4
T U E
N 00 10 MMSI B.No M M S M S
& T (last 6 digits, binary) 0 -15 LAT LON E I E I E
BIT & FRAME R N - N C - N C 12-BIT BCH
SYNCHRONIZ Y 00 11 AIRCRAFT 24 BIT ADDRESS DEG DEG 21-BIT BCH ERROR T U O U O ERROR
P N E CORRECTING CODE A + T N + T N CORRECTING
PATTERNS R R E D E D CODE
O C Y S S S S
15 9 S W
A - 26
T O 0 - 90 0 - 180
O D 01 01
C E AIRCRAFT OPER. SERIAL No D 0 - 30 0-56 0-30 0-56
O DESIGNATOR 1 - 511 A
L (1/4 d.) (1/4 d.) T (1min) (4s) (1min) (4s)
00 10 14 A
F 01 10
L 11 C/S TA No SERIAL No
A 1 - 1023 1 - 16383
G
20 4
11 00 MMSI Fixed
(last 6 digits, binary) 0000
  107 = “1”
F=1 0100 ELT-Serial  108 = “1”
P=0 0110 EPIRB-Serial  109 = “0”
0111 PLB  110 = “1”
 111 = Encoded Position Data Source: 1= int., 0 = ext.
1110 Test  112 = 121.5 MHz Homing: 1=Yes, 0 = No
October 2013
C/S T.001 - Issue 3 - Rev.14
NOTE: A3.3.5 defines the coding scheme for all Standard Location Protocols, some newer beacons where the coarse position in PDF-1 is always selected to be as
close as possible to the actual position will have a maximum offset in PDF-2 of +/- 7 minutes 30 seconds, in which case bits 114, 115, 124 and 125 of the
message will not be used and should be permanently set to “0”.
A - 27 C/S T.001 – Issue 3 – Rev. 14
October 2013
A3.3.6 National Location Protocol (see Figure A9)
A3.3.6.1 The national location protocol, identified by the flags F=1, P=0 and the protocol
codes in series no. 4 of Table A2-B, has the following structure:
a) PDF-1:
bits 37 to 40: 4-bit protocol code as defined in Table A2-B,
bits 41 to 58: 18-bit identification data consisting of a serial number

assigned by the appropriate national authority,
bits 59 to 85: 27 bits of position data to 2 minute resolution;
b) PDF-2:
bits 107 to 112: 3 fixed bits set to "110", 1-bit additional data flag, describing
the use of bits 113 to 132, and 2 bits of supplementary data,
bits 113 to 126: 14-bit position offset ( latitude,  longitude) to 4 second

resolution, or alternate national use, and
bits 127 to 132: 6 bits reserved for national use (additional beacon type
identification or other).
a) bits 59 to 71: latitude data (13 bits) with 2 minute resolution:

• bit 59: N/S flag (N=0, S=1)
• bits 60 to 66: degrees (0 to 90) in 1 degree increments
• bits 67 to 71: minutes (0 to 58) in 2 minute increments
b) bits 72 to 85: longitude data (14 bits) with 2 minute resolution:

• bit 72: E/W flag (E=0, W=1)
a) bit 107 to 109: ="110" (fixed);
b) bit 110: additional data flag (1 =  position data as described below in

bits 113 to132; 0 = other to be defined nationally);
A - 28 C/S T.001 – Issue 3 – Rev. 14
October2013
c) bits 111: encoded position data source

d) bit 112: 121.5 MHz auxiliary radio locating device included in beacon
(1 = yes, 0 = no);
e) bits 113 to 119: if bit 110 = 1,  latitude with 4 second resolution:

• bits 114 to 115: minutes (0 to 3) in 1 minute increments *
• bits 116 to 119: seconds (0 to 56) in 4 second increments
(default value of bits 113 to 119 = 1 00 1111);
bits 113 to 119: if bit 110 = 0, national use;
f) bits 120 to 126: if bit 110 = 1,  longitude with 4 second resolution:

• bits 121 to 122: minutes (0 to 3) in 1 minute increments *
bits 120 to 126: if bit 110 = 0, national use; and
g) bits 127 to 132: Additional beacon identification (national use)

(default value of bits 127 to 132 = 000000).
A3.3.6.4 The test protocol using the above format is encoded by setting bits 37-39 to "111"
and bit 40 to "1".
________________________
* A3.3.6 defines the coding scheme for all National Location Protocols, some newer beacons where the
coarse position in PDF-1 is always selected to be as close as possible to the actual position will have a
maximum offset in PDF-2 of +/- 1 minute, in which case bits 114 and 121 of the message will not be
used and should be permanently set to “0”.
Figure A9: National Location Protocol
1 25 27 37 86 107 113 133
24 26 36 40|41 85 106 112 132 144

|
------ 61 BITS ----- BCH-1 ------ 26 BITS ----- BCH-2

PDF-1 PDF-2
2 10 4 45 21 6 7 7 6 12
18 BITS 27 BITS
F
O S
IDENTI- LATITUDE  LATITUDE  LONGITUDE
R U
FICATION LONGITUDE
M P
P
A C P P N
R 18 1 7 5 1 8 5 1 2 4 1 2 4
T O R L A
E
A U O E T
D M D M M S M S
BIT & M
FRAME & N T 21-BIT BCH M I 12-BIT BCH ERROR
E I E I I E I E
B T O NATIONAL ID ERROR E O CORRECTING
SYNCHRONIZ. P N G N E G N - N C - N C
L R C NUMBER CORRECTING N N CODE
R U R U U O U O
PATTERNS
E R Y O CODE T A
E T E T + T N + T N
O L A L
S E E W E E E D E D
A - 29
T C R
S S S S S S S S
O O C Y U
C D O S
0 - 90 0 - 58 0 - 180 0 - 58 0 - 3 0 - 56 0 - 3 0 - 56
O E D D E
L E A
T
(1 deg) (2 m) (1 deg) (2m) (1m) (4 s.) (1m) (4 s.)
F A
L
A
G
   107 = “1”
F=1 See  108 = “1”
P=0 Table A2  109 = “0”
1000 ELT  110 = Additional Data Flag: 1 =  Position, 0 = Nat. Assignment
1010 EPIRB  111 = Encoded Position Data Source: 1 = Internal, 0 = external
1011 PLB  112 = 121.5 MHz Homing: 1= Yes, 0 = No
1111 Test
NOTE: A3.3.6 defines the coding scheme for all National Location Protocols, some newer beacons where the coarse position in PDF-1 is always selected to be as close as possible
to the actual position will have a maximum offset in PDF-2 of +/- 1 minute, in which case bits 114 and 121 of the message will not be used and should be permanently set
October 2013
C/S T.001 – Issue 3 – Rev.14
to “0”.
A - 30 C/S T.001 – Issue 3 – Rev. 14
October 2013
A3.3.7 RLS Location Protocol (see Figure A10)
A3.3.7.1 The RLS location protocol, identified by the flags F=1, P=0 and the protocol
code in series no. 7 of Table A2-B, has the following structure:
a) PDF-1:
bits 37 to 40: 4-bit protocol code defined as 1101,
bits 41 to 42: 2-bit beacon type data set to “00” for ELT, “01” for EPIRB
and “10” for PLB.
bits 43 to 58: 16-bit identification data consisting of a serial number

assigned by the appropriate national authority,
bits 59 to 85: 27 bits of position data to 2 minute resolution;
b) PDF-2:
bits 107 to 112: 3 fixed bits set to "110", 1-bit additional data flag, describing
the use of bits 113 to 132, and 2 bits of supplementary data,
bits 113 to 126: 14-bit position offset ( latitude,  longitude) to 4 second

resolution, or alternate national use, and
bits 127 to 132: 6 bits reserved for RLS Data.
a) bits 59 to 71: latitude data (13 bits) with 2 minute resolution:

• bit 59: N/S flag (N=0, S=1)
b) bits 72 to 85: longitude data (14 bits) with 2 minute resolution:

• bit 72: E/W flag (E=0, W=1)
a) bit 107 to 109: ="110" (fixed);

A - 31 C/S T.001 – Issue 3 – Rev. 14
October 2013
b) bit 110: additional data flag (1 =  position data as described below in

bits 113 to132; 0 = other to be defined nationally);
c) bits 111: encoded position data source

d) bit 112: 121.5 MHz auxiliary radio locating device included in beacon
(1 = yes, 0 = no);
e) bits 113 to 119: if bit 110 = 1,  latitude with 4 second resolution:

• bit 114: set to 0 *
• bit 115: minute (0 or 1)
bits 113 to 119: if bit 110 =0, national use data;
f) bits 120 to 126: if bit 110 = 1,  longitude with 4 second resolution:

• bit 121: set to 0 *
• bits 122: minute (0 or 1)
(default value of bits 120 to 126 = 1 00 1111)
bits 120 to 126: if bit 110 =0, national use data; and
g) bits 127 to 132: RLS Data

100000 RLM-Request Type-1 only
010000 RLM-Request Type-2 only
110000 RLM-Request Type-1 + Type-2 (default)
A3.3.7.4 The RLS location protocol does not have a specific test protocol. Users should
utilize the National Test Location protocol described in section A3.3.6.4 when
testing beacon with RLS location protocols.
______________________
* Section A3.3.7 defines the coding scheme for all RLS Location Protocols. For these new beacons the
coarse position in PDF-1 is always selected to be as close as possible to the actual position and will
have a maximum offset in PDF-2 of +/- 1 minute, in which case bits 114 and 121 of the message will
not be used and should be permanently set to “0”.
Figure A10: RLS Location Protocol
1 25 27 37 86 107 113 133
24 26 36 40|41 85 106 112 132 144

|
 ------ 61 BITS ----- BCH-1 ------ 26 BITS ----- BCH-2

PDF-1 PDF-2
2 10 4 45 21 6 7 7 6 12
F
18 BITS 27 BITS
O
R IDENTIFICATION LATITUDE LONGITUDE  LATITUDE  LONGITUDE
S
M
C P U R
P A 2 16 1 7 5 1 8 5 1 2 4 1 2 4
T O R P L
R
U O NATIONAL P S
E D M D M M S M S
FRAME & N T B ID 21-BIT BCH L 12-BIT BCH ERROR
BIT & A E I E I I E I E
T O E ERROR E D CORRECTING
SYNCHRONIZ.
M P NUMBER N G N E G N - N C - N C
R C A CORRECTING M A CODE
B
PATTERNS R R U R U U O U O
Y O C CODE E T
L O E T E T + T N + T N
T
L O N A
E S E E W E E E D E D
O C N T
S S S S S S S S
A - 32
C O C A
O D O T R
L
0 - 90 0 - 58 0 - 180 0 - 58 0 - 1 0 - 56 0 - 1 0 - 56
E D Y Y
E P
F E D
L (1 deg) (2 m) (1 deg) (2m) (1m) (4 s.) (1m) (4 s.)
A
A
G T
A
    107 = “1”
F=1 1101 “00” =ELT  108 = “1”
P=0 “01”=EPIRB  109 = “0”
“10”=PLB  110 = Additional Data Flag: 1 =  Position, 0 = Nat. Assignment
“11”=SPARE  111 = Encoded Position Data Source: 1 = Internal, 0 = external
 112 = 121.5 MHz Homing: 1= Yes, 0 = No
NOTE: Section A3.3.7 defines the coding scheme for all RLS Location Protocols. For these new beacons the coarse position in PDF-1 is always selected to be as
close s possible to the actual position and will have a maximum offset in PDF-2 of +/- 1 minute, in which case bits 114 and 121 of the message will not be
October 2013
C/S T.001 – Issue 3 – Rev.14
used and hould be permanently set to “0”.
- END OF ANNEX A
B-1 C/S T.001 – Issue 3 – Rev.14
October 2013
ANNEX B
SAMPLE BOSE-CHAUDHURI-HOCQUENGHEM
ERROR-CORRECTING CODE CALCULATION
B1 Sample 21-Bit BCH Code Calculation
The error-correcting code used in the first protected field of all 406 MHz messages is a
shortened form of a (127,106) Bose-Chaudhuri-Hocquenghem (BCH) code. The shortened
form (82,61) consists of 61 bits of data followed by a 21-bit triple error-correcting code. The
code is used to detect and correct up to three errors in the entire 82-bit pattern
(bits 25 through 106 of the 406 MHz message).
Note: For the purpose of error correction, all calculations shall be performed with the full
length code. Therefore, 45 zeros are placed before the 61 data bits to form the 106 bit pattern
of the (127,106) BCH code. These padding zeros do not affect the generation of the
BCH code as described below.
For the (82,61) BCH code, a generator polynomial g(X) (the same as for (127,106) BCH
code) is defined as follows:
g(X) = LCM (m1 (X) , m3 (X) , m5 (X))
where LCM = Least Common Multiple.
In the above case:

m1 (X) = X7 + X3 + 1
m3 (X) = X7 + X3 + X2 + X + 1
m5 (X) = X7 + X4 + X3 + X2 + 1
from which,
g(X) = m1 (X) m3 (X) m5 (X)
= X21 + X18 + X17 + X15 + X14 + X12 + X11+ X8 + X7 + X6 + X5 + X + 1
a determination of g(X) results in the following 22-bit binary number:
g(X) = 1001101101100111100011
To generate the BCH code, an information polynomial, m(x) is formed from the 61 data bits
as follows:
m(X) = b1 X 60 + b 2 X 59 + .... + b60 X + b61
where b1 is the first bit (i.e. format flag), and b61 is the
last bit of PDF-1.
B-2 C/S T.001 – Issue 3 – Rev.14
October 2013
m (X) is then extended to 82 bits by filling the least significant bits with 21 "0". The
resulting 82-bit binary string is then divided by g(X) and the remainder, r(X), becomes the
BCH code (the quotient portion of the result of the module-2 binary division is discarded).
The above process may be clarified by the following example:
Message Format Short Message

Protocol Flag User Protocol
Country Code 366 (USA)
User Protocol Type Serial
Beacon Type Float free EPIRB
Manufacturer's ID 002
Sequence Number 1
Beacon Model Number 1
Production Run Number 1
National Use Bits 00000000
Homing 121.500 MHz
Emergency/National Use Not Used
Beacon Activation Automatic or Manual
for which:
Beacon 15 Hex ID: ADCD0 08004 40401 (bits 26-85)

Short Message: 56E68 04002 20200 96552 50 (bits 25-112)
Bits 25-112: 0101 0110 1110 0110 1000 0000 0100
0000 0000 0010 0010 0000 0010 0000
0000 1001 0110 0101 0101 0010 0101
0000
The division1 described above is shown in Figure B1 and results in a remainder of:
0001011001010101001001
The most significant bit position of the remainder will always be a "0" and is deleted to
obtain the 21-bit BCH code:
BCH Error-Correcting Code: 001011001010101001001
REFERENCE
An Introduction to Error Correcting Codes, Shu Lin, Prentice-Hall 1970
1
Modulo 2 division prohibits a "borrow" in the subtraction portion of the long division
B-3 C/S T.001 – Issue 3 – Rev.14
October 2013
| | |
---->|<------------- Bits 25 - 85 ------------------------------>|<---Bits 86-106---->|
45’0’| (Data bits) | (21 "0"s) |
m(X)=0101011011100110100000000100000000000010001000000010000000001000000000000000000000
g(X)= 1001101101100111100011
001101101010101010001100
1001101101100111100011
0100000111001101101111
1001101101100111100011
0001100011111100111100000
1001101101100111100011
01011100100000000000110
1001101101100111100011
001000100110011110010100
1001101101100111100011
0001001011111001110111000
1001101101100111100011
00001100101010010110110001
1001101101100111100011
01010001111100010100100
1001101101100111100011
001110001000010100011100
1001101101100111100011
01111001011100111111111
1001101101100111100011
01101001100000000111000
1001101101100111100011
01001000011001110110110
1001101101100111100011
00001011101010010101010000
1001101101100111100011
001000011111001011001101
1001101101100111100011
0001110010101100101110000
1001101101100111100011
01111110000000100100110
1001101101100111100011
01100111011000110001010
1001101101100111100011
01010101101000011010010
1001101101100111100011
001100000010010011000100
1001101101100111100011
01011011111101001001110
1001101101100111100011
001011001000111010110110
1001101101100111100011
001010010101110101010100
1001101101100111100011
001111100001001011011100
1001101101100111100011
01100011001011001111110
1001101101100111100011
01011101001111100111010
1001101101100111100011
001000010001101101100100
1001101101100111100011
0001111100001010000111000
1001101101100111100011
01100011001101110110110
1001101101100111100011
01011101000010010101010
1001101101100111100011
001000010111010100100100
1001101101100111100011
0001111010110011000111000
1001101101100111100011
01101110111111110110110
1001101101100111100011
01000110100110010101010
1001101101100111100011
22-bit remainder = 0001011001010101001001
| |
|<------ BCH ------>|
| (last 21 bits) |
Figure B1: Sample 21-Bit BCH Error-Correcting Code Calculation

B-4 C/S T.001 – Issue 3 – Rev.14
October 2013
B2 Sample 12-Bit BCH Code Calculation
The BCH error correcting code (bits 133-144) used in the second protected field of the long
message is capable of detecting and correcting up to two bit errors in the bits 107-144. The
generator polynomial used as a basis for this code is:
g(x) = (1 + x + x6) (1 + x + x2 + x4+ x6)

= (1 + x3 + x4 + x5 + x8 + x10 + x12)
An example of the 12-bit BCH code which protects the 38-bit second protected field (i.e. bits
107 through 144) is shown below for the user-location protocol. The position in this example
is as follows:
actual latitude: 4333.63' N

actual longitude: 001 28.85' E
latitude rounded to nearest 4' increment: 4332' N

longitude rounded to nearest 4' increment: 00128' E
binary message:
- Encoded Position Data Source is Internal bit 107: 1

- North latitude bit 108: 0
- Latitude 43 bits 109-115: 0101011
- Latitude 32' bits 116-119: 1000
- East longitude bit 120: 0
- Longitude 1 bits 121-128: 00000001
- Longitude 28' bits 129-132: 0111
- BCH code bits 133-144: (see Figure B2)
Placing the binary bits 107-132 in order gives:
10 0101 0111 0000 0000 0001 0111
and the BCH code is calculated as shown in Figure B2. The resultant 12-bit BCH code is:
0001 0101 0001

B-5 C/S T.001 – Issue 3 – Rev.14
October 2013
| | |
---->|<---Bits 107-132------ - > | <-133-144->|
25’0’| (Data bits) | (12 "0"s) |
m(X)=10010101110000000000010111000000000000
g(X)=1010100111001
1111000000100
1010100111001
1011001111010
1010100111001
1101000011000
1010100111001
1111001000010
1010100111001
1011011110110
1010100111001
1111001111101
1010100111001
1011010001001
1010100111001
1110110000100
1010100111001
1000101111010
1010100111001
1000100001100
1010100111001
1000011010100
1010100111001
1011110110100
1010100111001
1010001101000
1010100111001
13-bit remainder = 0000101010001
| |
|<---BCH-->|
| (12 bits)|
Figure B2: Sample 12-Bit BCH Error-Correcting Code Calculation
- END OF ANNEX B -
C-2 C/S T.001 – Issue 3 – Rev. 14
October 2013
ANNEX C
LIST OF ACRONYMS
BCD binary-coded decimal

BCH Bose-Chaudhuri-Hocquenghem (code)
BCH-1 first BCH error correcting field
BCH-2 second BCH error correcting field
C/S Cospas-Sarsat
ELT emergency locator transmitter
EPIRB emergency position indicating radio beacon
F format flag
GHz gigahertz
GNSS Global Navigational Satellite System
Hex Hexadecimal
ICAO International Civil Aviation Organization
IMO International Maritime Organization
ITU International Telecommunication Union
LSB least significant bit
LUT local user terminal
MHz megahertz
MID maritime identification digits
MMSI maritime mobile service identity
ms millisecond
MSB most significant bit
P protocol flag
PC protocol code
PDF-1 first protected data field
PDF-2 second protected data field
PLB personal locator beacon
RHCP right hand circular polarization
RLS return-link service
RMS root mean square
RTCA Radio Technical Commission for Aeronautical Services
(USA)
SART search and rescue radar transponder
TAC type approval certificate
VSWR voltage standing-wave ratio
- END OF ANNEX C -
- END OF DOCUMENT -
Cospas-Sarsat Secretariat
700 de la Gauchetière West, Suite 2450, Montreal (Quebec) H3B 5M2 Canada
Telephone: +1 514 954 6761 Fax: +1 514 954 6750
Email: [email protected]
Website: www.cospas-sarsat.org
Appendix 2. MSC Circ/Res
MSC Circ. 1040

REVISED GUIDELINES ON ANNUAL TESTING OF 406 MHz SATELLITE
EPIRBs
MSC Circ 1039

GUIDELINES FOR SHORE-BASED MAINTENANCE OF SATELLITE
EPIRBs
MSC Circ 1222

GUIDELINES ON ANNUAL TESTING OF VOYAGE DATA RECORDERS
(VDR) AND
SIMPLIFIED VOYAGE DATA RECORDERS (S-VDR)
RESOLUTION MSC.333(90) (adopted on 22 May 2012)

ADOPTION OF REVISED PERFORMANCE STANDARDS FOR
SHIPBORNE VOYAGE DATA RECORDERS (VDRs)
Res A.810(19)
Performance Standards for Float-Free Satellite Emergency
Position-Indicating Radio Beacons(EPIRBs) Operating on 406MHz
COMSAR/Circ.32
HARMONIZATION OF GMDSS REQUIREMENTS FOR RADIO
INSTALLATIONS ON BOARD SOLAS SHIPS
AP2-1
AP2-2
AP2-3
AP2-4
AP2-5
AP2-6
AP2-7
AP2-8
AP2-9
AP2-10
AP2-11
AP2-12
AP2-13
AP2-14
AP2-15
AP2-16
AP2-17
AP2-18
AP2-19
AP2-20
AP2-21
AP2-22
AP2-23
AP2-24
AP2-25
AP2-26
4.10 Satellite float-free EPIRB
The satellite float-free EPIRB should be located/installed so that the following
requirements are fulfilled:
.1 The EPIRB should, with greatest possible probability, float-free and avoid being
caught in railings, superstructure, etc., if the ship sinks.
.2 The EPIRB should be located so that it may be easily released manually and
brought to the survival craft by one person. It should therefore not be located in a
radar mast or any other places which can only be reached by vertical ladder.
(SOLAS 1974, as amended, regulations IV/7.1.6, 8.1.5.2, 9.1.3.1, 10.1.4.1, 10.2.3.1
and IMO resolutions A.763(18), A.810(19), as amended, and A.812(19))
Note:
- A float-free EPIRB may also be used to fulfil the requirements for one piece of
equipment (of two), which is capable of transmitting distress alert to shore from or
near the navigating bridge of the ship. Under such conditions the float-free EPIRB
should fulfil the following additional requirements with regards to
location/installation:
.3 The EPIRB must be installed in the vicinity of the navigation bridge, i.e. on the
wings of the navigation bridge. Access via vertical ladder should not be accepted.
A location on the top of the wheelhouse may be accepted to fulfil the requirement
if accessible by stairs; or
(SOLAS 1974, as amended, regulation IV/7 and COM/Circ.105)

.4 It may be possible to activate the EPIRB remotely from the bridge. If remote
activation is used, the EPIRB should be installed so that it has unobstructed
hemispherical line of sight to the satellites.
Note:
- It should be considered that the main function of the EPIRB is float-free
activation. If the additional requirements mentioned above cannot be met without
reducing the reliability of the float-free activation, priority should be given to this
requirement. Alternatively, two float-free EPIRBs should be installed.
.5 The EPIRB should be equipped with a buoyant lanyard suitable for use as a tether
to life raft etc. Such buoyant lanyard should be so arranged as to prevent its being
trapped in the ship.s structure.
(IMO resolutions A.810(19) and A.812 (19), as amended)

.6 The EPIRB should be marked with the ship.s call sign, serial number of EPIRB,
MMSI number (if applicable),15 Hex ID, and battery expiry date.
AP2-27
Appendix 3. MSC 1039,Appendix
10403. MSC
Test Reports
1039, 1040 Test Report
Ship
MSC Test Report
Class
MSC-1039 (SBM) Furuno form: MSC 1039(0704)
NK
MSC-1040 (Annual Maintenance Report) Furuno form: MSC 1040(0704)
LR
MSC-1040 (Annual Maintenance Report) Furuno form MSC 1040(0704)
DNV
MSC-1040 (Annual Maintenance Report) Annual Testing of 406MHz EPIRBS
BV
ABS
DNV GL
MSC-1040 (Annual Maintenance Report) 406MHz Satellite EPIRB Annual Test Report
KR MSC-1040 (Annual Maintenance Report) Furuno form: MSC 1040(0704)
MSC-1040 (Annual Maintenance Report)
AP3-1
Appendix 3. MSC 1039, 1040 Test Report
AP3-2
AP3-3
AP3-4
AP3-5
AP3-6

Jotron Beacon Coding Procedure

Uploaded by

Copyright:

Available Formats

Jotron Beacon Coding Procedure

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Jotron Beacon Coding Procedure

Uploaded by

Copyright:

Available Formats

Jotoron Beacon

Tron 40VDR (VR-7021F)

・FURUNO Authorized Distributor/Dealer

All rights reserved. Printed in Japan A : NOV . 2014

Pub. No. TIE-56820-A

4．Other Information ····························································································· 8

5. Beacon Installation ························································································· 13

Chapter 1. Installing the PRU-50 S/W

1.2 Boot up the Beacon Programmer ································································ 1-2

Chapter 2. Beacon Programmer

2.1 Screens of the Beacon Programmer···························································· 2-2

2.2 [Program], [Read] and [Report] buttons ····················································· 2-14

2.3 Menu bar ··································································································· 2-22

2.4 Details of the menus ·················································································· 2-26

Chapter 3. Coding Procedure

3.2 Beacon Test ······························································································· 3-12

3.3 Labeling ····································································································· 3-16

Chapter 4. Outline of the Beacon

Appendix 1. C/S T.001 SPECIFICATION FOR

Appendix 2. MSC Circ/Res

MSC Circ. 1039

MSC Circ. 1222

RESOLUTION MSC.333(90) (adopted on 22 May 2012)

Appendix 3. MSC 1039, 1040 Test Reprts

Form MSC 1039 (0704) ················································································ AP3-3

Annual Testing of 406MHz EPIRBS ······························································ AP3-4

406MHz Satellite EPIRB Annual Test Report ················································ AP3-5

1. Installation flow chart of Beacon

Coding & Labeling

Filing of data sheet

Furuno Subsidiaries/ Distributors Programming Programming

Name each file to save it as the same format as below.

2.1 Coding protocols

2.2 Selecting a Coding protocol

2) Beacon with GPS

3) The Cayman Islands

Table 2.2.1 Protocol Classification

Information) Difference between Beacon test message and real message

406 Hex message: See FFFE2F9B026F85507FDFFB7A6BF783E0F66C.

3.1 Maintenance of Beacon

3.1.2 Every year

3.1.3 Every 2 year

3.1.4 Every 5 year (Shore Based Maintenance: SBM)

3.1.5 Inspection every decade

3.2 Self test

Tron 60S, Tron 60GPS, Tron 40Smk2, Tron 40GPSmk2

3.2.1 Self test

3. OK if the LED at the tip of the antenna is flashed on one time.

4. After the test, return the SW to [READY] position.

3.2.2 GPS test

1．ex; Beacon Test Results 2．ex; Beacon Programming

3．ex; Beacon Test Repot

4．ex; MSC. 1040 Annual Maintenance report

5. ex; MSC. 1039 SBM Maintenance report

4.2 Cayman Island: Guide to Applicants for a Maritime ICT

4.3 Summary of User Protocols Coding Options

4.4 Outline of Location Protocols

3. Installation of Junction Box: VR7022F (VR-7021F: Tron 40VDR only)

5. Mounting Beacon in Bracket (VF-7021F: Tron 40VDR only)

Apply silicone grease