You are on page 1of 22

3G ALE

APPLICATION NOTE
What is 3G ALE?
3G ALE is a call system that conforms to STANAG 4538. It provides rapid
on-air linking with a high degree of link security and optional secure data
transfer. It uses fast link setup and a voice or data traffic type.
Stations that communicate with the 3G ALE call system may be set to scan a
set of channels, listening on each channel at precisely the same time. This is
known as synchronous mode. The sending station uses its LQA data to
ensure that the preamble burst is sent on the best quality channel for the
receiving station. This minimises the length of preamble transmissions and
maximises network availability. 3G ALE stations may also communicate
asynchronously, however, preamble times will be longer.
A link may be point-to-point, point-to-multipoint (voice only), or broadcast.
The link may be 1-way or 2-way. Multiple stations may be grouped under a
common address, so a call to this one address attempts to create a link with
all member stations.
STANAG 4538 refers to the initial part of the link establishment as a
Protocol Data Unit (PDU). It contains the type of traffic to be carried on the
link, the addresses of entities that are invited to join the link, and whether or
not the station is required to send an acknowledgement to the invitation. This
portion of a call is notionally similar to Codan’s Selcall or ALE/CALM
preamble, except the content is different. In this document, the term
preamble is used instead of the STANAG 4538 term of PDU.
When the 3G ALE call system operates in synchronous mode, the
transceiver actively selects the best channel for the receiving station and
confirms that a link is established before any voice or data (for example,
message text or GPS information) is transferred. Figure 1 on page 2 shows a
simplified diagram of the process to send a Message call in a 3G ALE
network (as described in Appendix C, STANAG 4538). The initial link
request and acknowledgement may utilise link protection. The data part of
the call is not transmitted until the link is established. It may be transmitted
in clear or with AES-256 encryption.

© 17-60148 Issue 1, September 2014 Page 1 of 22


Head office Asia Pacific Europe and Africa Americas and Middle East

Codan Limited Codan Limited Codan (UK) Ltd Codan US, Inc.
ABN 77 007 590 605 81 Graves Street Unit 4, Endeavour Place 1 Fishers Road
81 Graves Street Newton SA 5074 Coxbridge Business Park Pittsford NY 14534
Newton SA 5074 AUSTRALIA Farnham Surrey GU10 5EH USA
AUSTRALIA UNITED KINGDOM
Telephone +61 8 8305 0311 Telephone +61 8 8305 0311 Telephone +44 1252 717 272 Telephone +1 585 419 9970
Facsimile +61 8 8305 0411 Facsimile +61 8 8305 0411 Facsimile +44 1252 717 337 Facsimile +1 585 419 9971
www.codanradio.com asiassales@codanradio.com uksales@codanradio.com ussales@codanradio.com
3G ALE

When data is transferred, it is sent using one of three data traffic types: Codan Adaptive
Signalling Technology (CAST), high-throughput data link (HDL), or low-latency data
link (LDL). CAST provides the fastest method for transferring large amounts of data,
and is adaptive to changing channel conditions. The LDL traffic type is the slowest
method for transferring data, however, it is the most robust and provides
communications in extremely poor channel conditions.

Figure 1: Sending a Message call in a 3G ALE network

Tx station Data
tune and LBT acknowledged

All stations are


synchronously Called
scanning the station(s) Called station(s)
channels with a tune and return to
dwell time of acknowledge synchronous
1.35 sec/channel link request scanning

Channel
dwell 5 5 5
slots

4 4

3 3

EOM
Tune

Tune

Term
Msg

Msg
Req

Ack

Ack

Ack
fwd

fwd

2 2 ... 2

1 1 1

Time
Call initiated Data End of
on Ch 2 transmitted message
dwell slot and
termination
Calling station
requests link

Data sent in
Link establishment
clear or with
and protection
AES-256 encryption

Scanning for incoming calls,


no link activity
Source: Annex C to STANAG 4538

Page 2 of 22 17-60148 Issue 1, September 2014


3G ALE

Comparison between 3G ALE and 2G ALE (ALE/CALM)

Linking probability

Codan has performed link comparison tests using 3G ALE and 2G ALE calling systems.

Figure 2: Probability of linking

Figure 2 shows the probability of successfully establishing a link between two stations
under varying channel conditions using 3G ALE and 2G ALE.
A disturbed channel is a simulation of a fast-fading, multipath HF channel. These are the
typical conditions encountered during propagation of HF sky waves. An AWGN channel
is a simulation of a non-fading, single-path channel with added noise. Similar conditions
may be encountered during propagation of short-distance ground waves. For more
information on HF channel simulations refer to ITU Recommendation F.1487.
The curves show that 3G ALE linking (blue curves) is approximately 6 dB better than
2G ALE linking (brown curves) using sky wave propagation on a typical HF channel.
This translates to a 3G ALE station requiring only one quarter of the power required by a
2G ALE station to propagate a sky wave with the same channel conditions.

17-60148 Issue 1, September 2014 Page 3 of 22


3G ALE

Calling times

Figure 3 shows the average calling times for different call types using 3G ALE and
2G ALE protocols.

Figure 3: Calling times between 3G ALE and 2G ALE

The call times are an average of 100 calls of each call type using a typical 3G ALE
network with synchronous scanning of 5 channels.
Apart from the ‘Failed Call’ category, the times shown are for a successful link
establishment on the first channel attempt without any repeats. In quickly changing sky
wave conditions, typically experienced by a manpack or mobile station on-the-move, the
LQA database loses accuracy quickly and linking on the first channel attempt is rare.
The time required to send a 3G ALE Channel Test call followed by a 3G ALE voice link
is similar to the time required for a 2G ALE voice link to be established on the third
channel attempt. The 3G ALE link is established on the best available channel at the
time, as determined by the preceding Channel Test call, whereas the 2G ALE link made
on the third channel attempt is not guaranteed to be the best channel.
As well as being quicker across all call types, the 3G ALE protocol can send much larger
Message calls than the Codan Selcall or 2G ALE protocols. Text messages of up to
250 characters can be sent and received via the front panel of the transceiver. By default,
the data traffic type used is LDL. If you are sending larger messages of up to
5900 characters via Codan’s Computer Interface Command Set (CICS), you should
consider changing the data traffic type to a higher throughput or CAST. For more
information refer to Application Note: Operating a transceiver via a computer and CICS
(Codan part number 17-60149).

Page 4 of 22 17-60148 Issue 1, September 2014


3G ALE

Figure 4: Calling times for a 90 character 3G ALE message sent using LDL
traffic type over varying channel conditions

Figure 4 shows how the transmission time of a Message call in a 3G ALE network
decreases with improving channel conditions. The 3G ALE protocol incorporates
Automatic Repeat Request (ARQ) to resend errors. The 2G ALE protocol uses Forward
Error Correction (FEC) and does not resend errors.
The 3G ALE protocol provides a more robust system than the 2G ALE protocol in
deteriorating channel conditions. As channel conditions deteriorate, the 2G ALE system
will fail to send messages, whereas the 3G ALE continues to successfully transfer
messages, with longer transmission times.

17-60148 Issue 1, September 2014 Page 5 of 22


3G ALE

Figure 5: 3G ALE data traffic types and RC50-C performance

Figure 5 compares the time taken to transmit a 5 kB text message using the different
3G ALE data traffic types with the time taken to send an email with a 5 kB attachment
using RC50-C, over varying channel conditions.
The RC50-C email system reached a data transmission rate of 4800 bit/s. Although it is
possible for the 2G ALE data system to transmit at higher data rates, the amount of data
being sent was not enough to allow the system to reach the higher rates. The curves in
Figure 5 show that for data amounts of 5 kB, the 3G ALE data traffic types outperform
the 2G ALE data system.

Page 6 of 22 17-60148 Issue 1, September 2014


3G ALE

3G ALE communication
Each station in the 3G ALE network may be pre-programmed with a list of member
stations, and/or a station may be set up to send calls to and receive calls from unknown
stations. Each station has its own individual self address. This self address must be
allocated to the specific 3G ALE network in the Address entry in the Control List, for
example 110/3G ALE or 110/All. Once added as a member of the network, each station
may be called simultaneously via the 3G ALE broadcast address 1023. The network may
be broken down into smaller groups, each with selected members, and each group has a
group address that may be used to call the member stations of the group.

For information on calling across the network, and between and within
NOTE
groups, see page 16, Station address settings.

Figure 6: Simple 3G ALE communication network

3G network
Network Address: 4576 Broadcast Address: 1023

710
Group
Name: EAST
Address: 101

Group
Name: CENTRAL
600 900
Address: 111
210

610 100
110
200

500 Group
Name: WEST 700
Address: 121

300 800
400
510
310

810
410

3G ALE communication network

3G ALE station

TOD master station

3G ALE groups

17-60148 Issue 1, September 2014 Page 7 of 22


3G ALE

Codan’s 3G ALE option


Codan’s 3G ALE option is implemented in the 2110 and 2110M Manpack Transceivers
using the internal 3G ALE module. This module may also provide optional AES-256
encryption.

Network configuration
In the 2110/2110M transceivers, a call system is associated with a network and scan
channels. The network is set up in exactly the same way as any other network in the
transceiver, except that a 3G ALE network has some extra settings that define link
protection, synchronisation, addressing, and calling requirements. Some of these settings
must be identical across all stations that communicate using the 3G ALE network, and
some settings are specific to each station.

Figure 7: Network List in NSP

Page 8 of 22 17-60148 Issue 1, September 2014


3G ALE

Figure 8: 3G Network Configuration window

Call system

The 3G ALE call system is available when the 3G ALE option is enabled in the
transceiver. When you use NSP to create a network that uses the 3G ALE call system, the
3G Network button is available to access the specific entries required to set up your
3G ALE network (see Figure 7 and Figure 8). When you use the front panel to create a
network that uses the 3G ALE call system, as you scroll through the settings you are
prompted to View 3G ALE details (see Figure 9).

Figure 9: Viewing 3G ALE details

Channels

3G ALE operation requires a wideband filter. When the wideband filter is enabled,
USBW, LSBW, USB 3k, and LSB 3k modes are available for allocation to the channels.

17-60148 Issue 1, September 2014 Page 9 of 22


3G ALE

Scanning

Only one 3G ALE network may be scanned at a time. This is the active network and is
indicated on the 3G ALE scanning screen (see Figure 10). If several 3G ALE networks
are set to be scanned, the transceiver selects the first alphabetically listed 3G ALE
network.

Figure 10: 3G ALE scanning screen

If there are no 3G ALE networks set to be scanned, the internal 3G ALE module is
switched off to conserve battery power. The transceiver continues to operate with
programmed Codan Selcall and ALE/CALM networks. If a call is initiated via a 3G ALE
network, the 3G ALE module is switched on.
Only the channels that are included in the currently selected 3G ALE network are
scanned and can receive calls. If these channels are common to 2G ALE and Codan
Selcall networks that are set to be scanned also, and the address for that network matches
the address of the incoming call, the transceiver receives the call via the matching call
system and network. A 3G ALE network can scan up to 64 channels.

Figure 11: Use of channels in a transceiver with multiple scanned networks

3G ALE Open Selcall Codan Selcall ALE/CALM


Ch 1 Ch 5 Ch 1 Ch 1
Ch 2 Ch 7 Ch 5 Ch 3
Ch 3 Ch 8 Ch 10
Ch 4
Ch 5

Outgoing calls may be made on any channels that are included with a network. In the
scanned networks shown in Figure 11, incoming calls may only be received on the
channels that are included with the 3G ALE network: Ch 1, Ch 2, Ch 3, Ch 4 and
Ch 5. Although Ch 7, Ch 8, and Ch 10, are included in the scanned non-3G ALE
networks, they are not scanned because they are not included in the 3G ALE network.
An effective programming practice is to include all channels on which you expect to
receive calls (regardless of a network’s call system) in the network channel list for the
3G ALE network.
The channel for a synchronous 3G ALE call is automatically selected based on
information stored in the LQA database in the transceiver. The LQA information is
updated whenever a station hears a call or sounding, regardless of whether the station
hearing the call has been addressed or not.
Page 10 of 22 17-60148 Issue 1, September 2014
3G ALE

Network Address
The Network Address setting must be the same across all transceivers
CAUTION
that want to use the 3G ALE network.

The network address is the unique address that may be used as part of the seed for
encrypting the preamble during link establishment. The network address must be in the
range 0 to 8191.

You cannot make a call to the network address. If you want to call all
NOTE stations in the 3G ALE network, make a broadcast call to the broadcast
address 1023.

Link protection settings


When you establish a communication link in an ALE/CALM or Codan Selcall network,
you cannot be assured of the authenticity of the station entering the link. 3G ALE offers
link protection, which at a basic level uses the network address to encrypt the preamble,
and at an advanced level, also incorporates the link protection key into the encrypting
algorithm.
The preamble is the initial linking part of a 3G ALE call. It contains the addresses of all
the stations called in the link, whether or not the station is required to send an
acknowledgement to the invitation to link, and the type of traffic that the link will carry.
This information may be encrypted with the use of the network address and/or a link
protection key. Using the network address and link protection key to encrypt the
preamble can provide some degree of anti-spoofing during link establishment. It gives
the called stations a level of certainty that the incoming link request is from a known
station, not an impersonating station.

Link Protection Mode

The Link Protection Mode setting must be the same across all
CAUTION
transceivers that want to use the 3G ALE network.

The link protection mode determines the method used to encrypt the transmitted
preamble. It is set up for each 3G ALE network.
There are three methods that may be used:
• the preamble is encrypted with the network address and link protection key
(Address + key)
• the preamble is encrypted with the network address (Address only)
• the preamble is not encrypted (Disabled)

17-60148 Issue 1, September 2014 Page 11 of 22


3G ALE

Link Protection Key

The Link Protection Key setting must be the same across all
CAUTION
transceivers that want to use the 3G ALE network.

The link protection key is a 56-bit key (hexadecimal string) entered as 14 hexadecimal
digits (A to F, 0 to 9). The default value is 0. It adds further security to the preamble
during link establishment.

Synchronisation settings
3G ALE usually operates in a synchronous manner using the channels associated with
the currently scanned 3G ALE network. During scanning, all stations within the 3G ALE
network dwell on the same channel at the same time. When a call is made, the sending
transceiver knows when the best channel is available and the required tune time for the
network, so can calculate the precise moment to send the preamble of the call to request
the link.
Synchronised scanning is typically achieved using UTC time derived from a GPS signal
as the time reference in the TOD master station in a 3G ALE network. In this instance,
the TOD master station must have reliable GPS reception to ensure accurate UTC. The
synchronisation mode in the TOD master station is set to GPS, and the Time GPS
Updates entry is set to Enabled (default setting).
The time reference within each transceiver and its drift from the time reference of the
TOD master station is critical to synchronous operation in the 3G ALE network. As the
TOD master station responds to requests for TOD updates, the time reference in this
transceiver sets the time reference for the 3G ALE network. The time reference for a
transceiver is shown in the Time Screen in the Control List.

Figure 12: Time reference for a transceiver

time reference for a transceiver

A station with reliable synchronisation can lose reception of the GPS signal and maintain
synchronisation for at least 22 hours before its synchronisation accuracy is degraded to
the point of operating asynchronously.
Slave stations that temporarily lose GPS reception can send a TOD Request Get Status
call manually to the network using the broadcast address 1023, if synchronisation is
required. The TOD master station responds by broadcasting a TOD update to the
network. Any station that does not have GPS reception adjusts its time reference when it
hears the broadcasted TOD update. If the TOD master station does not respond, a TOD
update can be requested from a neighbouring station that lays within a confident zone of
communication by individually addressing that station at the time of the manual TOD
Request Get Status call.

Page 12 of 22 17-60148 Issue 1, September 2014


3G ALE

A 3G ALE network can also operate synchronously using the internal clock source of the
TOD master station as the time reference for the network. This method of
synchronisation is totally dependent on manual over-the-air TOD broadcasts and is not
as reliable as the UTC time reference provided via a GPS signal.
A station receiving an over-the-air TOD update from the TOD master station can operate
synchronously for at least 12 hours before its synchronisation accuracy is degraded to the
point of operating asynchronously.
The time reference in each transceiver must be within 30 minutes of the time reference in
the TOD master station, regardless of its synchronisation mode. Calling activity requires
that the time references of participating stations are within 30 minutes.

There is a limitation in STANAG 4538 that may lead to a false indication


of synchronisation (see Figure 13 on page 14) when the difference in the
CAUTION time reference in a transceiver is greater than 30 minutes from the time
reference in the TOD master station. For more information see page 21,
Limitations in STANAG 4538.

The real time clock in the transceiver can drift over time if it is switched off for many
months. It may be kept up-to-date with correct GPS fixes if the Time GPS Updates
entry in the Control List is Enabled. In other cases, as a minimum, Codan recommends
that the TOD master station should maintain an accurate UTC time and that a schedule of
regular, manual, over-the-air polling to the TOD master station is implemented by
member stations. If the time reference for the network is maintained using the internal
clock source of the TOD master station, and this time is not based on UTC time, then the
Time GPS Updates entry should be set to Disabled.
It is also possible to operate a 3G ALE network in asynchronous mode. The member
stations do not scan the channels in the 3G ALE network at the same time, so the calling
station cannot determine the precise time to send the preamble to establish the link. As
such, any call made in an asynchronous 3G ALE network uses an extended preamble to
cover the scanning cycle. Asynchronous calling activity requires that the time references
of participating stations are within 30 minutes.

Sync Mode

The synchronisation mode defines how stations maintain the time reference to ensure
that scanning is synchronous, or disables the need for synchronous scanning by operating
in asynchronous mode. If all stations have their own GPS receiver, then the
synchronisation mode is GPS. One of these stations is nominated as the TOD master
station, even though each station is able to maintain synchronisation using the UTC time
in the GPS signal.
If a station manually requests a TOD update to the broadcast address 1023, the TOD
master station responds automatically with the required information. If there is no
response from the TOD master station due to propagation conditions, a station can
manually request a TOD update from a neighbouring station that lays within a confident
zone of communication.
Stations that do not have a GPS receiver should set the synchronisation mode to Master
GPS, Master loc clock, or Master ext clock.

17-60148 Issue 1, September 2014 Page 13 of 22


3G ALE

When synchronisation is maintained using over-the-air broadcasts, that is, the


synchronisation mode is set to Master GPS or Master loc clock, the TOD master
station makes an automatic TOD broadcast on one channel (rotational basis) prior to a
scheduled sounding.

Figure 13: Synchronous operation

synchronisation has been


received over-the-air
or via a GPS receiver,
but does not have a valid fix

The level of confidence of synchronisation is indicated by the number of vertical bars


visible after Sync.
If there are no stations with GPS receivers in your 3G ALE network, set the
synchronisation mode to Always async. A longer preamble is used to establish the
call, however, you can still utilise the link protection feature.

Figure 14: Asynchronous operation

The synchronisation mode, and hence the time reference that is used for synchronisation,
may be different for each 3G ALE network in a transceiver. If you are changing from one
network to another, and the synchronisation mode is the same, for example GPS, then
synchronisation can be maintained. If the synchronisation mode is different, for example
GPS in one network and Master loc clock in the second network, then
synchronisation cannot be maintained and the transceivers must revert to asynchronous
scanning and calls until the transceivers regain synchronisation.

Table 1: Synchronisation modes

Synchronisation mode Description


GPS The time reference for the network is UTC time. This station uses a GPS
signal as its primary means of maintaining accurate synchronisation.
Master GPS The time reference for the network is UTC time. This station uses manual
over-the-air TOD updates from the TOD master station as its primary
means of maintaining accurate synchronisation.

Page 14 of 22 17-60148 Issue 1, September 2014


3G ALE

Table 1: Synchronisation modes (cont.)

Synchronisation mode Description


Master loc clock The time reference for the network is derived from the internal clock source
of the TOD master station. Each station in the network uses manual over-
the-air TOD updates from the TOD master station as its primary means of
maintaining accurate synchronisation.
Master ext clock The time reference for the network is derived from an external clock source
at the TOD master station. This method is not possible on a Codan
transceiver, however, it may be needed for interoperation with other third-
party transceivers using 3G ALE. Each station in the network uses over-the-
air TOD updates from the TOD master station as its primary means of
maintaining accurate synchronisation.
Always async The network does not maintain any synchronisation. All calling is made
asynchronously. The time to link and make calls is increased when using
this method.

TOD Master

It is preferable that all non-GPS synchronised transceivers take their timing from the
TOD master station, however, due to geographical location, a station may have to send a
manual TOD Request Get Status call to a neighbouring station. A transceiver that is
designated as the TOD master for the 3G ALE network has its synchronisation status
highlighted on the scanning screen (see Figure 15).
Stations that do not have GPS synchronisation may start a Get Status call and select
5: TOD Request to poll the TOD master station using a broadcast call to 1023 (only
the TOD master responds), or specifically to any station that has an accurate time
reference above the confidence threshold. The call address defaults to the last address
used, but may be changed at the time of the call. The TOD master station can broadcast
TOD to the 3G ALE network by starting a TOD Request Get Status call to the broadcast
address 1023.

Figure 15: TOD master station with synchronisation

17-60148 Issue 1, September 2014 Page 15 of 22


3G ALE

Tune Time

The Tune Time setting must be the same across all transceivers that want
CAUTION
to use the 3G ALE network.

The tune time is the time taken for the slowest antenna tuner in the 3G ALE
communication network to tune its antenna.

Table 2: Typical tune times for antennas

Antenna Tune time


(msec)
Broadband 0
2110 internal ATU 720 (tune from memory)
3040/3042/3046 200 (tune from memory)
3048 300 (tune from memory)
9350 6520
not recommended for
3G ALE networks
9103 not suitable for
3G ALE networks

Station address settings


It is useful to think about each unique address in the 3G ALE network as being an entity.
An address may relate to the physical station, or it may be a group address.
Each station in the network has an address. These addresses are included in the Network
Members list. In Figure 6 on page 7, there are 17 stations and 3 groups within the
network. Each station and group has its own address. For this 3G ALE network there are
20 address entities. Each address entity must be in the range 0 to 1022. Address 1023 is
reserved for broadcast calls.
Each station may be called using its address or its name. In a point-to-multipoint call, a
station may be called using its group address or group name, or via the broadcast address
of 1023. In a 2110/2110M Manpack Transceiver, each of these calls may be set up in the
Address List.

Page 16 of 22 17-60148 Issue 1, September 2014


3G ALE

Network Members

The Network Members list includes the address and name of each station. The address
and name of each station must be unique. The name must be at least 3 upper-case
characters.
The 3G ALE network shown in Figure 6 on page 7 has the following network members.

Table 3: Network members

Station address Station name Station address Station name


100 JOEL 110 BENE
200 BILT 210 SIMP
300 JOHD 310 JONE
400 TOD 410 JIMT
500 MIKT 510 ROBI
600 DALW 610 ZOEA
700 TRIM 710 PETB
800 JIMD 810 MARW
900 RHEN

These network members are listed in the 3G Network Configuration window shown in
Figure 8 on page 9.

Groups

A group is a notional subset of member stations that may be addressed by their group
address or group name. You may have as many groups as required per 3G ALE network.
A station may belong to more than one group.
The group address and name must be unique to the 3G ALE network. The group
member’s address and name is selected from the pre-defined list of network members.
The 3G ALE network shown in Figure 6 on page 7 has the following groups.

Table 4: Groups and group members

Group 101/EAST Group 1 111/CENTRAL Group 2 121/WEST


Station Station Station Station Station Station
address name address name address name
210 SIMP 200 BILT 300 JOHD
900 RHEN 210 SIMP 510 ROBI
610 ZOEA 800 JIMD

17-60148 Issue 1, September 2014 Page 17 of 22


3G ALE

These groups and group members are listed in the 3G Network Configuration window
shown in Figure 8 on page 9.

Address List

NSP may be used to profile a transceiver with a 3G ALE network. When you allocate the
3G ALE call system to the network, the 3G Network button is available to set up the
3G ALE settings via the 3G Network Configuration window (see Figure 8 on page 9).
The Update Address List button copies or merges entries from this 3G ALE network
to the Address List with No Call Type selected for the corresponding entries. Once the
profile is programmed to a transceiver, this enables the operator to select the call type at
the time of the call. If only one call type is used, then this can be selected for the call in
the Address List in NSP prior to programming the transceiver.

Call settings
STANAG 4538 specifies that calls may only be made to and from stations that are
members of the 3G ALE network. Codan’s 3G ALE networks may be set up to operate in
this manner, or you can allow calls to and from stations that are not members of the
network. This is defined separately for calls to the network from non-member stations,
and calls from the network to non-member stations. If you choose to set up your 3G ALE
network without any member stations, these call settings must be set to Allow to enable
calls into and out of the network.

Calls to Unknown

If you want a member station to be able to make a call to a station that is not included in
the list of network members, you should set Calls to Unknown to Allow. If you want
the station to operate as per STANAG 4538, set Calls to Unknown to Deny.

If Calls to Unknown is set to Deny, you must include all of the stations
CAUTION
with which you want to communicate in the Network Members list.

Calls from Unknown

If you want a member station to be able to receive a call from a station that is not
included in the list of network members, you should set Calls from Unknown to
Allow. If you want the station to operate as per STANAG 4538, set Calls from
Unknown to Deny.

If Calls from Unknown is set to Deny, you must include all of the
CAUTION stations with which you want to communicate in the Network Members
list.

Page 18 of 22 17-60148 Issue 1, September 2014


3G ALE

Typical operation
In a GPS-synchronised network, a station becomes synchronised when the transceiver’s
internal GPS module acquires a location fix. This may take several minutes. You can
send calls to other stations before the station synchronises, however, the preamble will be
longer.

Pre-tuning channels in a 3G ALE network


Optimal 3G ALE communications occur when the antenna tuner, if used, has the tuning
requirements for the channels in the network stored in its memory. Codan recommends
that you pre-tune all channels in the 3G ALE network at start-up and periodically
thereafter if tune errors are reported.

To manually pre-tune a channel:


1 Scroll to a channel.
1 Press TUNE.
The PTT tunes screen is displayed with the SWR and battery voltage on the
bottom line. For example:

If you do not press PTT within 30 seconds you are returned to the
NOTE
screen from which you began.

1 Press PTT to tune the antenna.


Tuning... is displayed, and the transceiver makes a series of short beeps.

17-60148 Issue 1, September 2014 Page 19 of 22


3G ALE

An SWR of less than 2.5:1 is acceptable.


If a message is displayed while you are tuning, you can remove it by
pressing .
If tuning continues for more than 2 minutes, tuning is automatically
NOTE aborted. The transceiver displays a message to inform you of this,
makes an error beep, and returns you to the screen from which you
began.
If tuning is unsuccessful, refer to the Quick Reference Card supplied
with the antenna.

1 Press PTT to stop tuning.


1 Press TUNE to return to the screen from which you began.

Sending or requesting a TOD Request Get Status call


If a station operator wants the transceiver to synchronise before a GPS fix is available, a
TOD request can be made to the TOD master station or any other station in the network
that is already synchronised.

An unsynchronised station in a synchronised network is unlikely to


CAUTION receive incoming calls, so it is important to actively maintain
synchronisation.

To manually request a TOD update or send a TOD update from the TOD master station:
1 Press CALL.
1 Scroll to the Get Status? call type.
1 Enter the broadcast address (1023), or the address of a station that has an accurate
time reference above the confidence threshold.
1 Press CALL.
1 Scroll to 5: TOD Request, then press CALL.
1 Scroll to the 3G ALE network that you want to use, then press CALL.

Making calls in a 3G ALE network


Typically, calling between stations using a 3G ALE network is similar to making calls in
an ALE/CALM network. The same process is used to start the call.
If you are making a call from a synchronised station to a station that is operating
asynchronously, you should append ! to the destination address, for example 110!. This
informs the calling transceiver to make the call asynchronously.

Page 20 of 22 17-60148 Issue 1, September 2014


3G ALE

Limitations in STANAG 4538


STANAG 4538 specifies that only minutes and seconds are sent as part of the TOD
update. Codan has implemented measures to reduce the chance of false synchronisation,
however, there are some instances in which the transceiver will indicate that it is
synchronised when it is not synchronised. This is easily identified by viewing the Time
Screens in the remote station and the TOD master station. If the time reference of the
remote station differs by greater than 30 minutes from the time reference of the TOD
master station, the time reference of the remote station needs to be adjusted.
The simplest way of overcoming false synchronisation is to use UTC (via a GPS signal)
as the time reference for the network, and to set the Time GPS Updates entry in the
Control List to Enabled.
Administrators of 3G ALE networks that do not use UTC as the time reference for the
network should check the time reference in the Time Screen of each remote station
annually to ensure that it has not drifted by greater than 30 minutes from the time
reference in the TOD master station.

Troubleshooting
Table 5 describes common troubleshooting issues that may impact upon calling using
3G ALE networks.

Table 5: Common troubleshooting issues

Issue Cause Action


The link works in one direction The tune time is set to a different See Table 2 on page 16 to
only value in each transceiver determine the tune time
recommended for the slowest
antenna tuner in your 3G ALE
network, then set the tune time for
all transceivers to this value
You can hear the call transmission The time reference in your Ensure that the time reference in
but your transceiver does not transceiver is greater than the station is within 30 minutes of
respond 30 minutes from the time the time reference of the TOD
reference at the TOD master master station
station
The link protection mode is not
the same in the transceivers
The network address is not the
same in the transceivers
The link protection key is not the
same in the transceivers

17-60148 Issue 1, September 2014 Page 21 of 22


3G ALE

Table 5: Common troubleshooting issues (cont.)

Issue Cause Action


The 3G ALE network does not The 3G ALE network does not Enter the self address into the
scan have a self address allocated Address entry in the Control
List and allocate it to the 3G ALE
network
Called station does not reply The called station has lost Try calling the station
synchronisation asynchronously, that is, append !
to the call address

Page 22 of 22 17-60148 Issue 1, September 2014

You might also like