Pcale User Guide
Pcale User Guide
1
Last Edited
24 JUNE 2014
PC-ALE v1.08
User Guide
For v1.08 Build 1.0.0.0
POC for this document is:
N2CKH
Support site:
https://groups.yahoo.com/neo/groups/PCALEDOCS/info
TABLE OF CONTENTS
PREFACE………………………………………………… x
OVERVIEW……………………………………………… x
ALE FREQUENCY SELECTION……………………….. x
ALE OPERATIONAL LIMITATIONS………………….. x
INSTALLING THE SOFTARE…………………….. xx
STARTING THE PROGRAM……………..…………….. xx
PC-ALE CONFIGURATION………………………... xx
MIL-STD-188-141A OPTIONS MENU…………………. xx
MIL-STD-188-110 OPTIONS MENU…………………… xx
FS-1052 APPENDIX B OPTIONS MENU………………. xx
SOUND CARD CONFIGURE…………………………… xx
TRACING MENU………………………………………... xx
CURRENT GROUP SETUP……………………………... xx
ADD CHANNEL…………………………………………. xx
ALE ADDRESSES……………………………………….. xx
ADD ADDRESSES………………………………………. xx
PC SOUNDS AND ALE MODEM………………………. xx
SETTING UP TX AUDIO………………………………... xx
SETTING UP RX AUDIO………………………………... xx
TUNE WINDOW…………………………………………. xx
HOW SYNC WORKS…………………………………….. xx
TRACING DETAILS……………………………………... xx
DATA MODES…………………………………………… xx
RADIO ADJUSTMENTS…………………….…………... xx
ACCELERATOR KEYS AND FRONT PANEL
CONTROLS …………………………………………….. xx
QUIET SCANNING/SOUDNING………………………... xx
TBD……………………………………………………….. xx
TBD……………………………………………………….. xx
TBD……………………………………………………….. xx
TBD……………………………………………………….. xx
TBD……………………………………………………….. xx
ALTERNATE QUICK CALL (ALE)…………………….. xx
PREFACE
At a minimum an AC’97 compatible PC Sound Device along with one RS-232 port or USB 1.1
or later port with RS-232 adapter. An HF SSB transceiver supporting remote control (where 4800
baud minimum for the 2 ch/sec scan rate) is required for full multi-channel ALE operation.
OVERVIEW
By reading and following the directions outlined within this document and the PC-ALE Radio
Control Guide you should be able to start using PC-ALE shortly after installing the software. If
your radio station is already configured for digital communications using the PC Sound Device
(a.k.a. Sound Card) as the Modem and you have a CAT capable HF SSB radio configured for PC
control, then configuring the PC-ALE parameters to your station capabilities and either loading a
properly edited .QRG file or using Channel Add to populate the needed channels for an ALE
Scan Group is all that is required for ALE operation.
This guide is designed for the first time user of PC-ALE who preferably has experience using
other PC Sound Device Modem (PCSDM) software and modes ( e.g. MT-63). However the user
should NOT make any assumptions that their existing PC to radio interfacing and sound device
levels as configured for other digital communication applications previously used will work
properly with PC-ALE. It is STRONGLY recommended that all directions as to how to
configure your audio levels and radio parameters for PC-ALE be followed to obtain the best
results as PC-ALE is not just another sound card digital mode program.
PC-ALE STANDARD ALE FEATURES SUPPORTED
INDIVIDUAL CALLS
GROUP CALLS
NET CALLS
GLOBAL ALLCALLS
GLOBAL ANYCALLS
SELECTIVE ALLCALLS
SELECTIVE ANYCALLS
WILDCARD ADDRESSING
AMD Mode
Automatic Storage of last 10 AMD messages where in PC-ALE 100 are retained
16 Scan Groups
100 scan channels maximum which in PC-ALE can be in 1 scan group or over all total.
100 Other Addresses where in PC-ALE 1,000 Other Addresses are supported
20 Own addresses
20 Net addresses
SOUNDING
SOUNDING POLLING
SINGLE CHANNEL OPERATION
MULTI CHANNEL SCANNING OPERATION
BUSY CHANNEL DETECTION
Computer Aided Transceiver (CAT) control (to include Memory Channel support for
some make/model radios) for stand alone Transceiver, Receiver and paired
Transceiver/Receiver or Exciter/Amplifier/Receiver combinations.
Support for “Split Frequency and Split Mode” channel operation for those make/model
radios that provide the capability.
CAT radio interface D.C. power via RS-232 RTS or DTR lines.
CAT Radio Dedicated Digital Port support.
Muting of receiver audio during scanning via RS-232 RTS or DTR line or CAT control
(for radios with the required remote control support).
RESOURCES release of Sound Device and Serial I/O ports for 3rd Party Software use
either manually or used in LINKED.DAT and UNLIKED.DAT
Radio Emulation Port (RAD) in support of 3rd Party Software for ALE follow on digital
mode support to control PTT ON/OFF and when configured for Radio Server operation,
Frequency and Mode as well. PC-ALE via the REM port automatically appears down to
detail as an ICOM IC-746PRO and KENWOOD TS-480.
TCP/IP Remote Control via Man Machine Interface (MMI) commands.
User entered MACRO commands using MMI commands on the fly and from various
command and control files (.DAT and .MAC) and keyboard entered MARCO’s.
LDG RS-232 ATU control
GPS support via RS-232 for NMEA-0183 devices
GPS based Geographic Position Reporting (GPR)
Manual Sounding (MAN SOUND) button for user initiated single channel sounding
AMBUSH Linking Call
RAPID Linking Call
No Sounding on a channel by channel basis
No (GPR) Reporting on a channel by channel basis
No Calling on a channel by channel basis
Advanced ALE LQA based Linking Calls with user control of the number of attempted
calls on the best LQA channel and or all channels.
QRZ Display of calling stations ALE ID when linking call fails to achieve a link.
E-mail Client and E-mail Server support
Huffman text compress support for all supported internal data modes for ALE follow on.
Incoming ALE link and AMD message Alarms
GPS based World Wide Mapping via Google Earth in support of Region of Interest (ROI)
for tactical station visualization of ALE network stations via the intercept of network
Soundings, Calls and Two-Way ALE communications involving transmitting GPS
information using the GPR sounding selection. This feature is a key Search and Rescue
capability for stations a field.
Logging of all Incoming and Outgoing Messages using any ALE internal data mode.
ALE Inlink state and Inlink clear use of MMI Commands via LINKED.DAT and
UNLINKED.DAT
ALE Inlink state and Inlink clear use of use of child process shell via LINKED.BAT and
UNLINKED.BAT
INSTALLING PC-ALE FOR THE FIRST TIME
1. Unzip the distribution archive file, PC-ALE_INSTALL_xxx.zip which contains two files,
a read_me.txt and setup_xxx.exe into a temporary directory.
2. Next run the setup program and accept the license agreement, then follow all the on
screen prompts. When installing PC-ALE under Vista or Windows 7, ***DO NOT***
install to the default C:\PROGRAM FILES\ path. Vista and later require programs that
are in the "Program Files" or "Program Files (x86)" folders to write data to the
"ProgramData" folder. PC-ALE does not support that convention. To overcome the
limitation, just install PC-ALE to its own unique folder under the root folder of your main
drive. One suggestion is to install it to a "C:\PC_ALE\" folder but any meaningful name
will do.
3. Place any existing PC-ALE .QRG file into the QRG subdirectory and using an ASCII
Editor, edit the SELCAL to your Callsign and then save the file.
The software is now installed and awaiting configuration, skip the next section and proceed to
STARTING THE PROGRAM.
NOTE: If the install used is not the most recent, then before running the ALE.EXE file, acquire
an updated version and place it into the sub directory where PC-ALE was installed on your
computer.
NOTE: Do NOT just drop the update version into your pre-existing PC-ALE directory as any
release may have a changed ALE.DAT file structure, thus your pre-existing ALE.DAT file will
be considered corrupt and will be over written if present by the new version when started.
2. Next depending on the distribution, either run an update install program or just copy the files
provided for the update to the directory desired.
3. If the update has not been announced as having a new ALE.DAT structure, when run PC-ALE
you will immediately be able to use the new features of the tool. If a new ALE.DAT structure is
the case or if for some reason your existing ALE.DAT is not recognized, you will need to then
load your .QRG file and perform the other needed configuration steps.
FIRST TIME STARTING THE PROGRAM
NOTE: Under newer updates of Windows a Security Alert screen may be displayed when
starting PC-ALE for the first time or when updated. Just click “Unblock” to continue.
Additionally, MS-Windows or 3rd party add-on Anti-Virus programs or other such tools may also
need adjusting to allow the PC-ALE executable to run.
Before starting PC-ALE for the first time it is best to create or edit a .QRG file for loading which
contains at least one Scan Group, one Channel and your Callsign.
TBD ADDS
ALE ADDRESSES
The Primary ALE Address is entered into the OWN ADDRESS database in slot 00 as your
primary PC-ALE Address. It is the Primary ADDRESS that is normally used as your OWN for
all Amateur Radio uses of PC-ALE and is selected for use with all Channels in all Scan Groups.
When making ALE Linking Calls to OTHER stations the Address entered for that channel will be
seen when your station is making an ALE Linking Call or Sounding. However, any OWN address
in the database is active to receive a call at all times. The software on the calling station side will
limit the OWN and OTHER Addressing permitted to only 6 character of less Addresses for AQC-
ALE operations and will advise when an OWN Address for the current GROUP/Channel is not
suitable for AQC-ALE operation.
All ALE Addresses should be 6 characters (2 ALE words) or less as such addressing provides the
greatest probability of achieving and maintaining an ALE linked state. The use of 6 character
Addressing also supports the use of MIL-STD-188-141B Alternate Quick Call ALE (AQC-ALE)
which only supports a 6 character (2 word) maximum address. However, for ALE, an address can
be as long as 15 characters (5 ALE words), but such an address provides poor results in linking.
An Address should always be as short as possible and on even ALE Words (3 characters) if
possible. The ALE standard provides automatic stuffing of one or more @ signs on the end of an
address that is not an even ALE Word, which the user never sees displayed, but which does make
the Address longer and thus less efficient.
Enter your callsign as your ALE OWN Address and click OK to move forward..
After your callsign entered for first time above the screen will appear as seen below.
Add Addresses
The OWN Address is your callsign and any extension or modification as directed by operational
directives for use by stations that will be calling you and for your station to identify with during
all ALE transmissions such as Linking Calls, Sounding (TIS and TWS) and the sending of all
ALE 8FSK modem protocol based messages.
The OTHER address is the SELCALL of the station that you will be calling.
The TT and TWR parameters on the “Add Other Address” dialog are TT: tune-up time delay of
antenna tuner or coupler and TWR: wait for reply time. The default values are acceptable for both
ALE and AQC-ALE. These parameters if not set the same by all stations within a group of
stations can cause failures in timing needed for Linking and Messaging, its best for all to use the
defaults.
Click on “Add”, "Own" Enter Address Insert your ALE SELCAL Address as the
PRIMARY address, which is address 00. For
AQC-ALE the currently active OWN must be 6
characters or less.
Click on “Add”, "Other" Enter Address Here you enter any legitimate ALE SELCAL,
Primary or Secondary for stations that you will be
calling, must be 6 characters or less for AQC-
ALE.
Before the software can be used it must be configured. At least one channel must be properly
configured with transmit rights before the software will transmit.
The “Current Group Setup” dialog provides for both the selection of the current default GROUP
with associated Channel(s) for use as well as to edit the naming convention of any of the 16
GROUPS using “Edit Current Group Text”.
The “Add Channel” dialog (Edit Channel is basically the same) provides access to the selected
GROUP to add an additional channel. At least one GROUP must be selected to add channel
parameters. From 1 to 16 GROUPS may be selected to associate the channel parameters being
added.
Parameter Value Parameter Description, Comments and
Notes
Add Channel: These are the steps to Main Menu, select Channels, click on
add a Channel to a “Add”
GROUP.
The “Fill” menu selection is utilized to load GROUPS/Channels from an existing .QRG file, as
well as to add OWN, OTHER and NET addresses. This can done from a .QRG that is user
exported to restore a system configuration or from a distribution .QRG from a third party such as
Hflink (where you MUST edit your OWN address with NOTEPAD.EXE before using) provided
with the distribution of the tool.
Next if you are beginning with a distribution .QRG file, be sure to use an ASCII editor (such as
NOTEPAD.EXE) and edit the OWN to that of your station and save the resulting edited .QRG
file.
Next run the PC-ALE software, check that the license passes and then use Fill > Load to read the
.QRG file to be used, at that point your OWN ADDRESS and all of your Scan GROUPS have
been configured.
All items added from an imported .QRG file and all changes to configuration made manually are
saved to the tools ALE.DAT database file which is automatically created if missing or corrupt
with default settings for most parameters, however many parameters must still be user entered.
The only time all changes to data affecting the ALE.DAT file are written is when the tool is
normally terminated. Changes made by loading a .QRG will NOT be made until normal program
termination. Changes made while using the MIL-STD-188-141 or MIL-STD-188-10 Options
dialog are made when OK is selected on the respective dialog.
If a preexisting .QRG file is used and is edited from within PC-ALE, the OWN callsign may not
easily be changed depending on how many callsigns are being used, which for Amateur Radio is
usually just one and if a Scan Group using that callsign is selected for use, which will be the case
if all 16 Scan Groups are populated and all with the same call sign. This is the case with the
Hflink .QRG files found at: http://hflink.com/pcale/
The easiest way to make your callsign the 0 slot OWN is to use the DataBar at PC-ALE screen
bottom, check MMI, a single MMI command can be entered and the COMMAND button can be
clicked for processing the command and its arguments.
Once you have loaded a .QRG file, such as the HFN distribution .QRG file where the OWN
Address is NOCALSIGN you can then enter and execute the following via the DataBar to change
NOCALSIGN to what you want, here is an example using N2CKH as the new self address to
replace NOCALSIGN:
Now the only OWN in the database is N2CKH. If you wanted to add another you would simply
issue another ADD OWN <self address> to add one to slot 01 and so on. For Amateur Radio use
slot 00 is all that would normally be needed.
After you verify that you have succeeded in changing over to your Callsign you want to save an
updated .QRG file.
PC Sound Device Configuration
MARS-ALE v3.00 Test Build #1 May 2013 debuted a new approach to Sound Device Setup that
continues to support the direct level control overall as well as output level control on-the-fly on a
scan group channel by channel basis when so configured. The features of this new approach that
apply to the current features of PC-ALE has now been implemented.
In the past the previous approach to sound device setup was problematic with some make/model
sound devices due to their drivers not being MS-Windows signed. Then too this was compounded
by changes invoked by Microsoft with newer releases of Windows OS versions beginning with
XP Professional and then the sweeping changes to audio support in Vista. The on-board or plug-
in sound devices and their drivers than came with a new computer and Windows OS even to this
day with Windows 8 mostly worked fine even with the old approach. The development of the
Windows Universal USB driver and various manufacturers of sound devices targeting the
Amateur Radio market compounded the issues.
The symptoms were many, most notably was the output of the sound device going to zero or
being muted or the inability to retain the user desired selected device upon restart or some
combination thereof. Then too there was the challenge of properly selecting the desired device
when there were two or more of the same device installed.
Some of these issues plague other software tools as well, such as device retention on restart and
selecting the proper one from many of the same make/model installed. However most Amateur
Radio applications do not directly control the mixer settings but rather simple shell the Windows
mixer.
It was only when setting the levels at program start in PC-ALE or during setup that these issues
where seen as PC-ALE unlike MARS-ALE, cannot be configured to automatically control the
output level on a channel by channel basis.
As other applications some may use appear to work properly, it is not really the case as the
applications actual use the Windows Sound Device control panel. As such users think MARS-
ALE or PC-ALE is at fault, which is not the case. This was long ago verified with other
applications against offending sound devices combinations using programs such as QuickMix
(http://www.ptpart.co.uk/assets/unsupported/quickmixin.zip) RoMac Sound Card Manager
(http://www.romacsoftware.com/SoundManagement.htm) and others that directly control the
sound device levels as does MARS-ALE and PC-ALE.
NEW APPROACH
The new approach provides additional options for Sound Device selection and retention for
reselection by either Number (as it has always been) or Name. In addition it is planned to export
the sound device selected along with all other user configurable parameters to a new Options
Parameters Setup (.ops) file in Man Machine Interface (MMI) “Set” commands format for later
reuse to automate reconfiguration should the ALE.DAT or planned ALE2.DAT database files
become corrupted or outdated. Additional selections are provided to defeat level control to point
of no level control being accomplished by the ALE software if that is what it takes to make a
given sound device usable.
All of the selections made on the PC Sound Device Setup dialog are now made and saved in real
time and not on clicking the OK button. Thus while using the dialog, the Windows control panels
can be opened and observed while making initial configuration selections. For example you may
see the Mute checked on the Windows Output Device panel each time you change the Input
Device level for the Signalink USB or other device or when the ALE starts and then uncheck it on
the Windows panel and then you can check “Disable Input Level Control” and this issue will go
away.
The popular Signalink USB units will be listed as “USB Audio Codec” and “USB Audio Codec
(2)” which Windows uses as the naming convention when two devices as installed. For the
Signalink the proper setup is where “Disable Input Level” is checked as the Signalink USB does
not expose a control panel for its input which can only be adjusted on the device itself.
The new “PC Sound Device Setup” dialog differ slightly between MARS-ALE and PC-ALE due
to the features of the two tools, below is the panel for MARS-ALE shown when the software is
started for the first time with its extra selections.
The selection “Save Levels on Start and Reset on Exit” is currently TBD in MARS-ALE and not
present in PC-ALE at the moment. When completed, at program start, enabling this selection will
cause the software to read the Input and Output devices levels if enabled and save them to reset
them as found at normal program termination. It will not do so on the first use of the software, it
will only do so on the subsequent use of the software after a restart after having been enabled.
The selection of the PC Sound Device “By Number or By Name” as implemented in MS-DMT,
which depending on the Sound Device hardware and driver used as well as the Windows
operation system in use, provides the user with the ability to configure so that the desired Sound
Device is always reselected properly on restart for both the Input and Output device. This
approach also deals with having more than one of the same make/model sound device installed,
especially with some challenging USB port devices. Devices that carry different names for the
Input and Output device under Windows Vista and later are best dealt with using “By Name”.
However, in systems with multiple sound devices, usually no more than two or three, they will
not always be in the correct sort order on boot, especially when dealing with removable sound
devices, such as USB port devices. Thus the use of “By Name” is much better than “By Number”
in such cases. All removable sound devices should always be plugged into the computer when the
computer boots up or should always be plugged in by the same order if “By Number” is used
prior to starting the software.
The interface provides selection of the “Input Device” to accept Receiver audio output via either
“Line In” or “Mic In” as well as supporting the level control of the Input Device. Should the
actual sound device expose an input panel under Windows (which all devices do not provide, e.g.
Signalink USB) and should it actually work with any program other than the Windows control
panel for the given version of Windows, MARS-ALE works properly as well. Optional settings
are also provided to deal with devices that do not provide or do not work correct for 3rd party
control in attempting to change the Input Device level.
In testing with 3rd party tools for Input Level control, the software has now been found to work as
well in controlling challenging devices in this regard as do all the tools tested to include the
“RoMac Sound Card Manager” ( http://www.romacsoftware.com/SoundManagement.htm or the
direct link http://www.romacsoftware.com/default.aspx ) which is about the best program that I
have found to do so other than the ALE tools at this point. Just how the Windows Sound Device
Panel does better may never be known unless they release the source code for review as
everything is being done to their documentation and with their Visual Studio development tools.
There is no list being maintained of suitable sound devices or the settings required with the new
configuration interface to make use of them for ALE. Pretty much any sound device that natively
supports a 48kHz sample rate or better and has a reasonable amount of sample clock error, drift,
noise etc. can be used for ALE (as long a VOX is not used for PTT). The new configuration
options now allow for addressing the issues presented by a given sound device driver and
Windows combination so that it can be pressed into use. However some features desirable for
ALE operations such as on-the-fly TX level control to maintain a constant RF output across the
spectrum may need to be forfeited when that feature comes to PC-ALE.
For those devices with no Input Device panel exposed (e.g. Signalink USB) or for those devices
where the Input Device does not work with other than the windows control panel (e.g. RigBlaster
Advantage) the selection “Disable Input Level Control” is provided, which for such units, if this
option is not used, then the Mute will get enabled on the Output Device automatically. All Man
Machine Interface (MMI) use of “SET RXAL x” is also disabled as long as “Disable Input Level
Control” is checked. When “Disable Input Level Control” is selected, “Disable Level Control”
check box is disabled.
The interface provides selection of the “Output Device” that drives the Transmitter. Support is
provided for level control in the software as an overall setting as well as configuration for drive
levels setup on a channel by channel basis to maintain a constant RF level across MF/HF
channels as has been supported for years now. However the “Disable Level Control”
configuration option is provided to disable level control in the software altogether should it be
desired so as to perform all level control via an external means. When “Disable Level Control” is
selected, the sliders will not respond on this dialog. The selection “Use GROUP/Channel TX
Audio Level” on the MIL-STD-188-141A options dialog will become unchecked. However
rechecking it will not enable that support as long as “Disable Level Control” is checked. All Man
Machine Interface (MMI) use of “SET RXAL x”, “SET TXAL x” and “SET MXAL x” is also
disabled as long as “Disable Level Control” is checked. When “Disable Level Control” is
selected, the “Disable Input Level Control” check box is disabled.
ALE RADIO CONTROL THEORY
QUIET SCANNING/SOUNDING
Most Amateur Radio grade transceivers and many Commercial and even some Military
make/models use Band Pass Filters (BPF) to meet spectral purity which are either switched with
diodes or relays. With ALE operations employing Scanning/Sounding those relays will take one
heck of a beating in a relatively short period of time.
The TX frequency is sent to the transceivers TX VFO just before TX during Sounding or any
type of Call or other transmission under computer control for the given GROUP/Channel
selected. That frequency change will only cause the BPF relays to work if the frequency is
different from the last TX frequency sent to the transceiver.
In addition, it is planned that for those radios which support computer control of the internal
antenna tuner (ATU), that when the program has been coded to support the addition of ATU
information on the GROUP/Channel setup dialog, that the program will also manage the state for
the ATU so that it is only engaged when the TX is called.
Most modern Amateur Grade radios use mechanical relays for BPF switching (some use
expensive linear or less expensive non-linear semi-conductors, which can cause distortion if the
best devices are not used, which are costly) as these less expensive mechanical relay prevent 2nd
order distortion at the primary stage of signal processing, most manufacturers use relays.
However, when the radio is subjected to rapid frequency changes that exceed the current BPF
range, the relays switch this switching is audible. The use of these types of radios with an ALE
controller (hardware or software) can make these relays sound a bit like a machine gun cycling.
In addition, the extra amount of relay activation decreases the
overall life of the relays.
However, as these BPF are used for filtering transmitted signals, they are engaged on the transmit
VFO of most radios that offer split frequency operation, thus, if we operate the radio in SPLIT
MODE, the BPF relays for most make/model radios will not come into play during
Scanning/Sounding. If split mode is selected, then during Scanning and Sounding these BPF
relays are not energized until the radio in Sounding goes into transmit mode, thus the noise is
reduced and the wear and tear on the life of the relays is minimized.
The SDT has found that the QS/S approach works perfectly on many of the newer radios,
however it does not work on all radios, examples being the Ten Tec radios, the ICOM Marine
Grade radios and most Yaesu radios fail to comply, many of the Commercial radios tested also
fail to comply. The ICOM IC-7800 partially supports QS/S in that the BPF relays work for QS/S
by there are front end mixer relays still be switched with relays. When you start software, it
announces if the radio selected for use complies for QS/S at program. A comprehensive list of
radios know to comply is provided in Appendix A of the Radio User Help Guide.
Another issue is where QS/S would work, but we have not found any such radios where it is
needed yet, is where SPLIT MODE cannot be enabled automatically, thus the user would NEED
to enable split mode manually. For these radios, the software will send the frequency and mode
information to both VFO A and B even if SPLIT MODE is not enabled, in such cases it’s in the
user’s hands to enable SPLIT mode for Scanning.
Also, if the radio has an ATU and it is engaged, it will still be playing while Scanning and
Sounding, some will only do so at TX, but most internal ones will do so during RX, some are
only in line in the TX, but some are in line during both RX and TX. It is planned to code to only
enable the ATU just prior to TX for those radios that support bus control of the internal ATU, not
all do and some may be to slow to be ready, experimentation is still required in this area.
The approach taken to make QS/S work via SPLIT VFO is:
1. At startup, the radio is placed into normal VFO operation, whenever Scanning/Sounding
operation is started, SPLIT VFO mode operation is invoked. “VFO A” is the RX VFO and “VFO
B” is the TX VFO. When Scanning/Sounding operation is terminated, normal VFO operation is
automatically resumed.
2. During Scanning/Sounding and any frequency selection for most radios, the RX frequency is
written to the radio “A VFO” along with the mode.
3. When it comes time to transmit the radios frequency is written to the radio “B VFO” along
with the mode if the TX frequency is not the same as last used.
A simple test to determine if a radio will work with QS/S or not is to turn your internal ATU OFF
and RIT/XIT OFF, using ‘VFO A’ change frequency on your radio using what ever means
desired, until your hear the BFO relays come into play. Then back up in frequency and you will
hear the relay’s again, then enabled “SPLIT VFO” and once again tune through the frequency
cross over point that the BPF relays previously activated, if nothing is hear, your radio is QS/S
qualified, if its not listed as such in Appendix A herein, please send a message to the SDT so
that it can be added to the QS/S routines and list. Like wise, if you radio is on the list, but
does not work, please inform the SDT so that it can be removed.
MIL-STD-188-141A Options Dialog
As this menu is where the “Radio Type” and its com port are selected, there is also a hot link to
the “Radio Help Operator Guide” (another Adobe .PDF file) which provides full details on radio
related matters, “Appendix A” provides a full listing of all supported radios and which selections
support various make/models that are not specifically listed on the “Radio Type” pull down
menu.
No parameters selected on this dialog are changed until the used selects “OK”. As a MARS-ALE
build release usually leads documentation release, screen captures herein may not 100% match
the latest software screen.
MIL-STD-188-141A Options Dialog
Parameter Value Parameter Description, Comments and
Notes
MIL-STD-188-141
Options:
Scan Rate 2 A setting of 2 ch/sec is pretty much the standard
used and all radios operating at 4800 baud or better
should support it. Don’t use 5 ch/sec unless the
radio operates at 9600 baud and above. The ‘141B
“To Do” of 10 ch/sec will require 19200 baud
minimum.
Set to 0 for automatic When set to 0, the tool automatically calculates the
operation based on length based on the number of channels in the scan
the number of GROUP being used, if that is the same number of
channels in the channels as the station you are attempting to link
current Scan Group in with and that station is not being paused during
use. For other settings scanning through the channels then automatic will
use a value between work well most of the time.
4-12.
For single channel operation it can be set to
anything, the lower the better, 4 works well.
However it needs to be longer when calling a
station operating in Scanning/Sounding. 8 works
well, however for the best chance of capturing a
station that is Scanning/Sounding 12-16 is better. At
times 20 or greater may be needed as the station you
are attempting to call may be scanning a large group
and/or being paused on one or more channels due to
activity.
Automatically set to Set to zero (0) your LINK will never time out. Set
180 if 0 at Scan Start higher for unattended operation, such as 180 (3
minutes) or 300 (6 minutes).
Range: 3..100,000 May need to be higher than the default when using a
linear amplifier, external ATU or other in-line
switching devices for settling, please check your
equipment manuals for settling time
recommendations.
Frame Votes 30
Maximum number of non unanimous votes allowed
Range 0..30 when receiving a frame.
TX Audio Level 1..10 typical PC Sound Device (Sound Card) drive level output
to transmitter from Line-Out or Speaker-Out as
Range 1..99 labeled.
NOTE: Most ICOM NOTE: Set radio RF power control for full output
radios require higher and all speech processors, compressor’s OFF and
drive levels. mic gain for good ALC range with normal SSB
voice transmissions. Then with the PC Sound
device control panel Main/Speaker/Playback or
whatever the course output level control is called
and the PC-ALE TX audio level (you will see the
WAVE control on the sound panel change) control,
adjust for about 35% or less of your full SSB RF
output power level while checking for NO ALC
moment.
On the MIL-STD-188-141 options menu next to the “Radio Type” pull down menu there is a “Radio
Port” button.
When the Radio Port button is selected the “Custom Radio Port Setup” dialog will appear.
The first field on Custom Radio Port Setup dialog is the “Setup Note”, where the user can enter a
free style 38 character text note as to what make/model radio the custom parameters pertain to
should the user at times switch between radio types they may own.
Custom Radio Port parameters will affect any radio type selected. Thus when Custom Radio Port
settings are changed for the currently selected radio type selected, thus if the parameters selected
do not apply, they would need to be updated or disabled.
The Custom Radio Port Setup dialog supports entering four parameters in support of any
make/model radio that provides for more than one configuration:
Baud Rate
Data Bits
Stop Bits
Parity
Also provided in support of older ICOM radio models only when radio type “GENERIC ICOM”
is selected are the selections:
Radio Address
Split VFO
When “GENERIC ICOM” is the selected radio type, other than the default ICOM radio address
may be configured in the radio and PC-ALE. When “Split VFO” is checked, the software will
control the radio in VFO A for receive and VFO B for transmit.
NOTE: Many features of newer ICOM radios such as Data Ports, USB Port and other support are
not provided when “GENERIC ICOM” is used as the radio type.
The Custom Radio Port parameter settings are only enabled when the “Baud Rate” is other than
0, which tells the tool not to use the hard coded parameters, when 0 ( regardless of other entries
on this dialog) the default coded parameters are used if the make/model radio type selected
supports other than one configuration, else the software ignores the settings. If a particular radio
model supports more than one configuration then the Baud Rate, Stop Bits, Data Bits and Parity
can be entered to match the radio configuration.
NOTE: The use of Custom Radio Port settings is a must for any Kenwood radio that supports
greater than 4800 baud if such higher baud rate operation is desired as the default baud rate for all
Kenwood models in PC-ALE, the starting default is 4800 baud regardless of what the factory
setting may be due all the years of that baud rate being the only one supported and these
selections supporting all Kenwood models.
It is recommended that the highest baud rate be used which any particular make/model radio
supports for the best channel scan rate performance. Typically all baud rates support 1 ch/sec,
4800 baud or better is recommended for 2 ch/sec, 4800 baud or better is recommended for 5
ch/sec, 19200 baud or better is recommended for the To DO 10 ch/sec of MIL-STD-188-141B.
Some radios due to their CPU ability to process serial port data may not meet a given Scan Rate
regardless of the RS-232 baud rate being used.
REPORT
A non-proprietary standard for Geographic Position Reporting (GPR) via Automatic Link
Establishment is supported by the amateur radio ALE community and various ALE controller
systems. The standard is called ALE Geo Position Report or ALE-GPR. To make the ALE-GPR
"universal" for ALE transceivers and controllers, the coordinates and other information of the
GPR is converted to plain text and contained within an AMD message.
Standard Use of Geo Position Report with NETCALL and AMD TWS: Net name: GPR
By using NETCALL for GPR, the receiving stations must "opt in" to the GPR Net rather than
everyone else having to "opt out" in the case of a GPR as an ALLCALL. Individual stations can
exchange GPRs using Individual Calls.
Manual keypad entry of ALE-GPR limits the characters that can be used. It is important for ALE-
GPR that the operator of the ALE transceiver, having knowledge of their own position, be able to
manually enter the GPR as an AMD on the keypad of the ALE transceiver and send it. This
manual entry method would not require the electronic connection of a GPS receiver to the HF
transceiver or ALE controller, or modification of the ALE controller software/firmware. Displays
on the front panels of some ALE transceivers use simple LCD readouts with about 10 to 20
characters displaying on a line. The AMD text is read by scrolling left/right with an arrow key on
the keypad.
There are limitations on what characters read out on ALE transceivers. The
following characters are common to all ALE displays and most transceiver keypads:
Any other character sent in the AMD has a risk that it might not show on the display.
A proposal has been made for a simplified format for the ALE-GPR with only 7 fields; using the
* character as a de-limiter:
Example:
GPR*KQ6XA*37N654321*122W987654*000003M*20050821Z135235*EVERYTHING FINE
ALE-GPR Fields
Field Field Characters Description Format Example
Position Name
1 GPR 3 "GPR" preamble to signify GPR
Geo Position Report follows.
Since it is only 3 characters, it
becomes part of the [CMD
AMD] command word in the
ALE protocol.
2 OBJECT 3 to 15 Object being reported. ABCDE0123456789
Normally this is your Callsign (reporting an object
or Own ALE Address. It could with the name
alternatively be the name or ABCDE0123456789)
callsign of another object
being reported (or relayed).
Use of the # character in this
field indicates the slant bar /
commonly used in callsigns.
3 LATITUDE Up to 9 Degrees and decimal degrees; 37N654321
with decimal point replaced by (Latitude 37.654321
N or S for North or South. If degrees North)
this field is stuffed, mimumum
field characters are 2 digits of
degrees followed by the
separator. The presence of the
# character in any part of the
latitude field indicates a
manual entry or a non-valid
position in the GPS receiver.
4 LONGITUDE Up to 10 Degrees and decimal degrees; 122W987654
with decimal point replaced by (Longitude
E or W for East or West. If 122.987654 degrees
this field is stuffed, minimum West)
field characters are 3 digits of
degrees followed by the
separator. The presence of the
# character in any part of the
longitude field indicates a
manual entry or a non-valid
position in the GPS receiver.
5 ALTITUDE Up to 7 Altitude; with suffix M for 0000003M
meters or F for feet. Minimum or
field character is 1 digit for 3M
altitude plus the suffix. The (Altitude 3 meters)
presence of the # character in
any part of the altitude field
indicates a manual entry or a
non-valid position in the GPS
receiver.
6 YYYYMMDDZhhmmss 15 DATE-TIME Stamp. 20050821Z135235
Year,Month,Day,Hour,Minute, (2005 August 21 at
Second; With "A-Z" as the 13hours 52minutes
timezone separator between 25seconds UTC zulu)
date and time.
Z=UTC (zulu)
J=Local Time, etc.
WXxxx.x*xxx.x*xxx*xxxx.xx
FIELD:
1. WX
2. Temp outdoors in Degrees xxx.x F range 000.0- ?
3. Wind Speed in xxx.x MPH range 000.0- ?
4. Wind Direction in xxx Degrees range 000-360
5. Barometric Pressure in xxxx.xx MilliBars range 000.00- ?
A legal WX report must start with WX and all fields after it must be present according to
the rules.
The * character will be used to delineate fields but not before field 1 or after field 5.
No WX data will be present from the WX station when the WX station port is not active.
However manually entered WX data can also be sent.
The presence of the # character in all digits of the Temp, Wind Speed, Wind Direction or
Barometric Pressure fields indicates a non-valid return of data by the WX station such as
a failed or missing sensor when the WX station port is active. For a manual entry the user
will fill in the field(s) for which they have no data with the # character for all digits.
As fixed location based stations can just enter GPS data, no GPS receiver is required for
GPR-WX support.
Initial WX station support in PC-ALE will be the Peet Bros. models which I am the most
familiar with from past development of my old SkyWarn2001 software, were I can lift
some algorithms but no code as it was mostly Visual Basic with Assembly and C based
objects where needed. There may be some conceptual aspects of that software which we
may be interested in applying to the visualization of the WX data when ALE stations are
active within the ROI of a WX event in progress, the manual for that software can be
found archived at:
http://www.qsl.net/n2ckh/SWDOWNLOAD/manual.pdf
HF-ALE Basic Requirements
The one undisputable aspect of an ALE network is that all stations within the network must be
configured the same as to ALE operational parameters for interoperability.
An ALE network requires that a number of parameters be set the same across all ALE controllers
in the ALE network. These settings are determined by a number of considerations; the size of the
network (e.g. number of stations), the number of channels, the planned ALE calling types
authorized for use, the use of automatic antenna tuners by any stations, the common features
supported between the make/model of ALE controllers being used, and others.
At a minimum, a fully functional ALE station must consist of the following system components:
When it comes to ALE modem/controller selection, it must be said that all ALE controllers are
not created equal. There are some ALE controllers that have non-standard features that add
operational benefits which do not negatively affect ALE controllers meeting published standards.
Then again there are some ALE controllers with non-standard features that have been found to
negatively affect a standards compliant ALE controller. There have been some ALE controllers
sold on U.S. markets commercially have been found incompatible with even FED-STD-1045A
basic requirements.
The most popular makes of 2G ALE SSB transceivers which are readily available new and used
in the U.S. markets that have been found to be interoperable based on both the authors hands on
use and the feedback of others with basic FED-STD-1045A and MIL-STD-188-141A
requirements are:
1
RS-232 based remote control at 4800 baud or better. Capable of scanning at a rate of 2, 5 or 10 channel
per second 24/7 without inflicting damage to the radio. The components most affected are the PA section
band switching relays in the transmitter section of the typical ham and commercial HF transceiver. There are
a limited number of ham transceiver models that can do this without modification.
2 Generic make/model external hardware based ALE modem/controllers supporting common Commercial
and Amateur grade HF SSB radios do not address PA section band switching relays. The ALE controller
features of MARS-ALE does address the issue of PA section band switching relays for a limited number of
HF SSB transceivers via various means depending on the make/model radio.
KENWOOD
MICOM (Mobat in U.S. for all models except MICOM-Z)
There are other makes of ALE transceivers that run up here in the U.S. as well in the used market,
such as Bendix, Rockwell-Collins, Rhode & Swartz, Sunair, Tadiran (Elbit Systems), Thales and
others. However these make/model radios and their documentation is difficult to acquire new or
used and expensive to service.
ALE Basic Operation
ALE Addressing
An ALE Address consists of one ALE word (3 characters) and is termed a "basic" address. If an
ALE Address exceeds the one word, it is an "extended" address.
Technically, an ALE Address can be 1 character as the quantity of available addresses within an
ALE system and the flexibility of assigning addresses, are significantly increased by the use of
address character stuffing.
Character stuffing allows address lengths which are not multiples of three characters to be
compatibly contained within ALE word address fields by "stuffing" the empty trailing positions
of the ALE word with the utility symbol “@” which is automatic. Thus for a single character
address of “A”, stuffing would result in an address of “A@@”. The “@” character is hidden from
view of all ALE stations in any ALE data displayed including the ALE Address.
Stuffing is of real importance in Amateur Radio use of 2G ALE. This is not so much of an issue
in MARS operations as MARS callsigns lead themselves to being standardized on 6 characters
normally and 3 characters for special tactical applications. However in radios services such as
Amateur Radio where an odd number of characters are used in assigned callsigns then stuffing is
a must have feature. For example, the Amateur Radio callsign “N2CKH” automatically
represented as “N2CKH@” as the 5 characters must become 6 characters for two ALE Words.
The use of Amateur Radio practices to designate a 2nd station on the air or a portable or mobile
station would in most cases cause stuffing as well as long than 2 ALE word addresses and should
be avoided for efficiency.
An ALE Address can only consist of the Basic 38 ASCII subset that includes all capital letters
(A-Z) and all digits (0-9) and the designated utility and wildcard symbols “@” and “?”.
An ALE Address assigned to a single station is an "Individual" address. The Individual ALE
Address is referred to in many different ways. At each local ALE station the reference to the
stations is often Self Address or Self ID or Own ID. In PC-ALE the Own ID is used with the
assigned Amateur callsign. The remote ALE station is often referred to as the Other Address,
Other ID, Remote ID.
All ALE Addresses must be unique within each ALE network of stations. This is not a big
challenge to achieve in some operations, however it depends on the scale of which ALE networks
may operate and what the basis of ALE Address assignments are based.
However the ALE basic address structure is based on single words that, in themselves, provide
multiples of three characters. Thus a three character ALE word is the minimum ALE Address,
and it is also the most efficient when it comes to establishing an ALE inlink state. However for a
callsign based service such as Amateur Radio a single ALE word address cannot be used.
No greater than a 6 character ALE address should ever be used as each additional ALE Word
used in addressing weakens the potential for establishing an ALE inlink state. However for for
normal 2G ALE up to 15 characters are legal, which is a throwback to early ALE support for
Integrated Services Digital Network (ISDN) support. However most Military and Government 2G
ALE addresses are 3 character single ALE word. In AQC-ALE it is illegal to use greater than 6
character ALE Addressing as AQC-ALE is all about efficiency and speed of calling and linking.
The special addressing modes include Wildcards, Self-address, Null address, Allcalls and
Anycalls.
A caller may use the Wildcard character (“?”) to address multiple stations with a single wildcard
address. Responses to a call containing an address with wildcard characters are generated in
pseudorandom slots to avoid collisions.
For self-test, maintenance, and other purposes, stations should be capable of using and responding
to their own Self-Addresses.
For test, maintenance, buffer times, and other purposes, stations may use a Null Address which is
not directed to, accepted by, or responded to by any station.
An "Allcall" is a general broadcast which does not request responses and does not designate any
specific address. The “Allcall” is required for emergencies ("HELP!"), sounding-type data
exchanges, and propagation and connectivity tracking.
An “Anycall” permits an ALE station to call and receive responses from essentially unspecified
stations and it thereby can identify new stations and connectivities. An "Anycall" is a general
broadcast which requests responses without designating any specific address(es). An “Anycall” is
required for use in emergencies, reconstitution of network and systems, and creation of new
networks.
Allcalls and Anycalls shall be further discussed in the “ALE Linking Calls” section herein.
ALE Channel
ALE is a Channelized system where Upper Sideband (USB) mode channels are grouped together
and scanned.
The Scan Rate at which channels are scanned depends on the ALE mode of operation as well as
the features of the ALE controller being used. For example, MARS-ALE in accordance with the
published U.S. Military standards provides for 1, 2, 5 and the MS188-141B “To Do” 10 channels
per second (ch/sec.) scan rates for Normal ALE and all except 1 ch/sec. for AQC-ALE operation.
Some 2G ALE controllers provide for non-standard scan rates.
MARS-ALE can be operated in Single Channel where all features except those specific to Multi-
Channel Scanning can be utilized.
Most ALE modem/controllers provide for Memory Channel and non-Memory Channel operation.
However ALE modem/controllers will usually not permit two-way ALE operation if the channel
has not been entered into the system and selected as the current channel. MARS-ALE is no
exception, a Scan Group with one or more channels must exist where the channel of interest is
selected to facilitate two-way ALE operation.
Multi-Channel ALE
tbd
Listen Before Transmit (LBT)
The ALE standards require a Channel Occupancy Detection capability which the user can enable
or disable, thus all ALE hardware radios and MARS-ALE provide Listen Before Transmit (LBT)
detector support. Listen Before Transmit should always be enabled in any ALE controller.
The ALE standards stipulate analog SSB Voice detection and ALE and a number of Military
serial tone waveforms (also used for Military Digital Voice) or digital modes if you prefer. The
LBT detection must detect within a 3Khz AWGN channel within a specific dwell time and meet
the probability of doing to achieve ALE system certified. The military waveforms are listed in the
current MIL-STD-188-141C section A.4.2.2 Occupancy detection, Table A-1, listed below as
Table 1 of this document.
The probability requirements based on SNR are from a low of 80% for low range of SNR listed to
a high of 99% for the high range of SNR listed for each waveforms with a false alarm rate of no
more than 1 percent. In the standard it is stipulated that there shall be no use of Fading or
Multipath in the AGWN channel, but still, the challenge in meeting 80-99% with 20% or 1%
falsing is daunting.
The 2G LBT in MARS-ALE v3.00 not only meets but exceeds the MIL-STD Channel Occupancy
detection requirements. In addition the MARS-ALE LBT detects addition Military waveforms
and all Commercial and Amateur waveforms commonly used by MARS.
tbd
Sounding
Sounding is the periodic broadcast of a station’s address, so that other stations can evaluate the
quality of the frequency carrying the sound for future link establishment to the sounding station.
Multi-Channel Sounding –
A mandatory 2G ALE requirement where during ALE Channel Scanning, when enabled, a
Sounding will take place on each channel enabled for Sounding at the defined time interval.
Sounding Period or Interval: The time to wait to perform a follow-up Sounding transmission after
Sounding has begun. The normal selection in most ALE networks is 60 minutes.
Resounding Interval or Period: This is the time to wait before attempting to Sound on a channel
that was previously occupied during the last attempt. The normal selection in most ALE networks
is 5 minutes, which will continue to repeat the Sounding attempt until the next Sounding Period
on the channel comes about. If Listen-Before-Transmit, is not enabled, a Resound event will
never occur.
The required rate of sounding is determined by how busy the intended recipients are, and the
maximum acceptable probability that the most recent sounds received from some stations are
older than some maximum acceptable age. For example, if B is the probability that a receiver is
busy when a sound is sent, A is the maximum acceptable age (in hours), and P is the maximum
acceptable probability that an entry is older than that age, then R sounds will be sent per hour,
where:
Alog B
R = log P
A and P are chosen by the network manager to satisfy network performance goals. B is measured
from actual network operation. Specifically, B is the fraction of time during a measurement
period that the observed radio is not able to receive sounds; this usually means the fraction of
time that the radio is not scanning. Note that B includes both traffic and overhead (e.g., sounding
and polling) busy time. For example, if polling is not used to fill in gaps in sounding data, the
system may be willing to accept only a 10 percent probability that each entry in the LQA matrix
is over 1 hour old. Then R is a function of B as shown in table
B R
(Prob. Station Busy) (Minimum Maximum Sounding
Sounds/Hr/Chan) Interval
1% 0.5 2 hr.
10% 1 1 hr.
32% 2 30 min.
36% 3 20 min.
46% 4 15 min.
58% 6 10 min.
Some, but not all ALE controllers support Single Channel Sounding while in single channel
operation.
In PC-ALE Single Channel Sounding makes use of the Multi-Channel Sounding Period and
Resounding Period which can be enabled at all times. However it will only operate when in
Single Channel operation and when not involved in any other two-way ALE communications. A
Single Channel (SC SOUND) button is provided to enable automatic single channel sounding
mode where the sounding period is the same as selected on the MIL-STD188-141 options dialog
for multi-channel sounding.
Manual Sounding -
Some, but not all ALE controllers support manual Sounding while in single channel operation.
Manual Sounding is operator initiated on the currently selected channel.
The time to wait to perform a follow-up Sounding transmission is completely up to the operator.
In PC-ALE a Manual Sounding (MAN SOUND) button is provided to initiate a manual sounding
event.
tbd
NOTE: Both Manual Sounding and automated Single Channel Sounding methods have many
applications MARS two-way communications, propagation studies. Also in Emergency location
beacons when coupled with ALE reporting features using GPS or manually entered position
coordinates. They also serve the user as backup capabilities when an ATU fails or a no-tune
broadband antenna fails and a makeshift tunable single band dipole, v-beam or random wire type
antenna (e.g. 18TD, 637T-2, AN/GRA-50, HA-4000, LW8, TD-1 and other manually tunable
military types commonly used by MARS members) pressed into service afield to continue active
participation in the ALE network.
ALE Linking Calls
INDIVIDUAL CALLS –
The protocol for this type of call consists of three 3-part handshake:
1. The linking call where the calling station addresses and sends a calling frame to the
called station being addressed.
2. If the called station decodes the linking call, it sends a response frame addressed to the
calling station
3. If the calling station receives the acknowledgement response, a bilateral link resulting in
the establishment of the ALE inlink state has been achieved. However, the called station
does not yet know this, so the calling station sends an acknowledgement frame addressed
to the called station.
tbd
NET CALLS –
The purpose of a “Net Call” is to rapidly and efficiently establish contact with multiple
prearranged stations by the use of a single net address. The “Net Address” is an address assigned
to all net members in common in addition to their individual addresses.
As a prearranged collection of stations, a net is organized and managed with significant prior
knowledge of the net member stations. A “Net Call” setup in the ALE Controller lists all net
member stations.
The net address structure is identical to that of individual station addresses, basic or extended, as
necessary. At a net member's station, each assigned net address is associated with a response slot
identifier to allow each station to respond to the net controller in a systematic manner. All stations
belonging to the net that hear the net call send their response frames in prearranged time slots.
The calling station then completes the handshake by sending an acknowledgement frame as usual.
tbd
GROUP CALLS –
The purpose of a “Group Call” is to establish contact with multiple nonprearranged (group)
stations (simultaneously if possible) rapidly and efficiently by the use of a compact combination
of their own addresses which are assigned individually.
The Group Call is optional in FED-STD-1045A and thus not found in all commercial radios. In
2G AQC-ALE there is no support for the Group Call feature.
A Group Call works similar to a Net Call, except that an arbitrary collection of stations is named
in the call vs. a specific single address. Because no pre-arranged net address has been set up, each
station must be individually named. Called stations respond in slots, determining their slot
positions by reversing the order that stations were named in the call. The calling station sends an
acknowledgement as usual.
Unlike a net, a group is not prearranged. In many cases, little or nothing is known about the
stations except their individual addresses and scanned frequencies. The ALE group addressing
mechanism provides a means to create a new group where none existed.
This mechanism uses a standardized protocol that is compatible with virtually all automated
stations, regardless of their individual, net, and other characteristics. The purpose of a group call
is to establish contact with multiple non-prearranged stations rapidly and efficiently by the use of
a compact combination of their own individual addresses. A group address is formed from a
sequence of the actual individual station addresses of the called stations, in the manner directed
by the specific standard protocol.
tbd
GLOBAL ALLCALLS –
An “Allcall” is a general broadcast that does not request responses and does not
designate any specific address. This mechanism is provided for emergencies, broadcast
data exchanges, and propagation and connectivity tracking.
The “Global Allcall” special address pattern is "TO @?@".
tbd
GLOBAL ANYCALLS –
An “Anycall” is a general broadcast that requests responses without designating any specific
addressee(s). It is required for emergencies, reconstitution of systems, and creation of new
networks. An ALE station may use the “Anycall” to generate responses from essentially
unspecified stations, and it thereby can identify new stations and connectivities.
The “Global Anycall” special address pattern is "TO @@?"
tbd
SELECTIVE CALLS -
Selective calling in an ALE system involves the exchange of ALE frames among stations. This
selective calling capability supports all higher level ALE functions, including link establishment
and data transfer. The general structure of an ALE frame consists of one or more destination
addresses, an optional message section, and a frame conclusion which contains the address of the
station sending the frame.
SELECTIVE ALLCALLS -
An “Allcall” is a general broadcast that does not request responses and does not
designate any specific address. This mechanism is provided for emergencies, broadcast
data exchanges, and propagation and connectivity tracking.
tbd
SELECTIVE ANYCALLS -
The selective Anycall is a selective general broadcast that is identical in structure, function, and
protocol to the “Global Anycall”, except that it specifies the last single character of the addresses
of the desired subset of receiving station (1/36 of all).
An “Anycall” is a general broadcast that requests responses without designating any specific
addressee(s). It is required for emergencies, reconstitution of systems, and creation of new
networks. An ALE station may use the “Anycall” to generate responses from essentially
unspecified stations, and it thereby can identify new stations and connectivities. The selective
Anycall is a selective general broadcast that is identical in structure, function, and protocol to the
global anycall, except that it specifies the last single character of the addresses of the desired
subset of receiving station (1/36 of all).
tbd
tbd
ALE Message Protocols
However, some ALE controllers allow for disabling AMD operation. In addition, some ALE
controllers that support one or more of the optional DBM or DTM ALE protocols do so in a way
that a selection must be made between AMD or DBM or DTM that remains constant until the
operator changes the selection.
The AMD protocol is a rather robust 125 baud (375 bps) or about 100wpm FEC protocol.
An AMD message can be up to 90 characters in length and supports the ALE 64-ASCII character
set consisting of only Upper Case characters A..Z, numbers 0..9, the SPACE (ASCII 20)
character and the utility symbols "@" and "?" and the punctuation characters in the table below.
! “ # $ % & ‘ ( ) *
+ , - . / : ; < = >
] \ [ ^ _
Decoded AMD messages as a mandatory standard requirement are required to be stored with
respect to the last 10 messages received as a minimum for later review by the receiving linked
station operator. In MARS-ALE the last 100 AMD messages are retained.
An AMD message can be intercepted by any 3rd party not part of the ALE inlink for display when
not compressed, Link Protected or otherwise encrypted.
DTM is an optional ALE protocol which was not provided in many ALE modem/controller
implementations for two-way messaging.
Being an optional ALE feature DTM is not a tested JITC capability for certification. Due some
vagueness in the standards, interoperability issues between different vendors DTM
implementations exist. MARS-ALE has been tested against some DTM ARQ hardware
implementations and found to be compatible.
The U.S. Military, U.S. Government and NATO users never made much use of DTM in
preference to high speed military data modem protocols.
DTM messages received are not required to be stored for later review as are AMD messages.
There are DTM FEC only Broadcast (BRD) and a full DTM ARQ modes. However, many
hardware implementations only provided one mode. In MARS-ALE both BRD and ARQ mode
are provided for DTM. DTM BRD can be used as specifically configured without the need of an
ALE link first.
>>>>> supports the ALE 128-ASCII character set
LQA data is also conveyed in the DTM frames in addition to the user entered message content
which follows the LQA report data in the frame transmission. The unilateral LQA data derived
from measurements on traffic and sounds received on several channels can be exchanged among
the stations sending and measuring those transmissions to provide each with bilateral LQA data
for those channels.
DTM messages are normally only displayed on the terminal of the parties to the ALE inlink state
regardless of being ARQ or BRD.
In MARS-ALE DTM messages, when not compressed, Link Protected or otherwise encrypted,
DTM messages can be displayed by intercept. DTM messages can be displayed regardless of
being ARQ or BRD mode when “Listen Mode” is enabled in single channel ALE operation only.
A resumption of Multi-Channel ALE operation automatically disables “Listen Mode”. The DTM
ARQ message frames may repeated during use of “Listen Mode” due to the nature of ARQ
request for resend operation between the parties of the ALE inlink being intercepted.
DBM is an optional ALE protocol which was not provided in many military or commercial ALE
modem/controller implementations. As with DTM, being an optional ALE feature DBM is not a
tested JITC capability for certification. Due some vagueness in the standards, interoperability
issues between different vendors DBM implementations exist and they seem to be greater than
with DTM.
As with DTM, the U.S. Military, U.S. Government and NATO users never made much use of
DBM in preference to high speed military data modem protocols.
DBM messages received are not required to be stored for later review as are AMD messages.
There are both DBM FEC only Broadcast (BRD) and a full DBM ARQ modes. However, many
hardware implementations only provided one mode. In most hardware implementations the
operator must select between DBM and AMD for both receive as well as transmit. In MARS-
ALE both BRD and ARQ as well as an FTP mode are provided for DBM. In MARS-ALE DBM
BRD can be used as specifically configured without the need of an ALE link first. MARS-ALE
has not been found to be 100% compatible with any DBM ARQ equipped hardware ALE
controller tested.
LQA data is also conveyed in the DBM frames in addition to the user entered message content
which follows the LQA report data in the frame transmission. The unilateral LQA data derived
from measurements on traffic and sounds received on several channels can be exchanged among
the stations sending and measuring those transmissions to provide each with bilateral LQA data
for those channels.
DBM messages are normally only displayed on the terminal of the parties to the ALE inlink state
regardless of being ARQ or BRD.
In MARS-ALE DBM messages, when not compressed, Link Protected or otherwise encrypted,
DBM messages can be displayed by intercept. DBM messages can be displayed regardless of
being ARQ or BRD mode when “Listen Mode” is enabled in single channel ALE operation only.
A resumption of Multi-Channel ALE operation automatically disables “Listen Mode”. The DBM
ARQ message frames may repeated during use of “Listen Mode” due to the nature of ARQ
request for resend operation between the parties of the ALE inlink being intercepted.
ALTERNATE QUICK CALL (AQC) ALE
PC-ALE provides support of Alternate Quick Call ALE (AQC-ALE) which is an optional form of
ALE detailed in MIL-STD-188-141B, Appendix A.
AQC-ALE provides a link establishment technique that requires significantly less time to link
than the normal ALE system and is significantly better at establishing and maintaining a link on
under poor channel conditions. The “ALE Mode” indicated on the main panel of PC-ALE will list
NORMAL for standard ALE and ALTERNATE for AQC-ALE once a link has been created.
AQC-ALE uses technology where some of the lesser used functions of the baseline ALE system
are trading-off for a faster linking process. The primary focus of AQC-ALE is to establish a link
between two or more stations as rapidly as possible. Once linked, information can be exchanged
in the most efficient manner as is common between stations. AQC-ALE is basically a tactical
tool, in that although it supports Scanning/Sounding and most things that baseline (a.k.a.
NORMAL ALE) supports, AQC-ALE is usually used in small tactical network operations rather
than fixed point 24/7 ALE Network operations.
PC-ALE is always listening for the normal ALE call as well as AQC-ALE call when in AQC-
ALE mode and shall automatically respond and operate in the mode called. However, to initiate
an AQC-ALE contact, the operator must select AQC from the MIL-STD-188-141 Options menu
by checking AQC. Most but not all normal ALE systems will completely ignore AQC-ALE
activity, however older versions of PC-ALE when not in AQC-ALE will not it as Link Protected
ALE activity.
AQC-ALE allows for a maximum of a 6 character (2 ALE word) address for both the OWN,
OTHER and NET address (MARS-ALE has been written to fully trap for any addressing in
excess of 6 characters, PC-ALE has not yet been so updated).
AQC-ALE does NOT support AMD, DTM or DBM during link set up, or an AMD at link clear
or an MOTD or initiating an AQC-ALE link by use of a MIL-STD-188-110 modem associated
link request. PC-ALE has been written to exclude these types of messages when initiating or
clearing an AQC-ALE link, however it is up to the user NOT to use MOTD when using AQC-
ALE.
It is permitted to make an AQC-ALE linking call to any AQC-ALE station that supports AQC-
ALE, be that a PC-ALE based or hardware (such as Harris tactical radios) based AQC-ALE
station that is Scanning/Sounding, as AQC-ALE stations can always receive and reply to either a
baseline ALE or AQC-ALE call.
AQC-ALE has a very fast calling handshake and all parties must be using FAST AGC and the
Scanning/Sounding station MUST be operating at a 5 ch/sec scan rate for best results. A 2 ch/sec
scan rate will work depending on the number of channels in the Scan Group and timing
considerations as to when the calling station starts transmitting and when the Scanning station
comes to that channel next, a 1 ch/sec. scan rate will not work reliably. An AQC-ALE call will
reliably capture a station Scanning that is using a 6 channel or less Scan Group at a 2 ch/sec. scan
rate and has “Listen Calls” checked and “Listen Time” set to 400.
Quick AMD Dictionary
AQC-ALE offers additional tactical features not found in baseline ALE, such as Quick AMD
Dictionary operation. The code in PC-ALE at present has bugs in this area which have been fixed
in MARS-ALE and will be fixed in PC-ALE in the future.
QAMD works from three dictionaries in a code book fashion where no actual text of the message
is being sent out over the air. It is a table lookup value in the code book which are the
dictionaries. There is no data encryption going on here. Using a combination of a fixed
dictionaries for most commonly needed words and mission specific expressions in the additional
two dictionaries, which can be changed to fit the scenario of ALE use. When started for the first
time without the optional dictionary files place holders are displayed for Dictionary 2 and 3 as
seen below.
The words “Dictionary 0” are standard, Dictionary 1 and 2 are from custom files need to be
created in order to make use of AMD Dicitionary where the two files required which must be
pure ASCII created with NOTEPAD.EXE or other ASCII editor. The files are named dic1.txt and
dic2.txt and are placed in the same directory as the ALE.EXE. Below is a screen capture were the
two files exist that have been setup for use with terms commonly used in MARS
communications.
AMD Dictionary is a quick mouse double click system of selecting words and phrases to create
an AMD when using AQC-ALE. The operator can not enter any words on the fly, the word or
phrase must pre-exist in the dictionaries. In the example below, the message “SEND WATER
AND FOOD ON TRUCK WITH MEDICINE AND RADIO ZOF FEMA ZEK ZEU” was created
pretty fast and when sent would be pretty secure.
.
If all the users are not using the same dictionaries then the receiving station will not print the
proper message, thus if a station does not have or is not using the proper Dictionary files they will
not be able to intercept the message in whole. All users must be using the same set of
Dictionaries, it’s a tactical thing.. If you do not have the proper set of dictionary files you will still
print words, just the wrong words, of if you have no dictionary files installed or too few words in
your dictionary then you will just print the place holder index location such as {1,96} for should
have been a word at that location in your dictionary, which is the place holder of the word in the
dictionary that is missing in your dictionary.
For testing the Dictionary capability a sample integral Dictionary (DICT0) which is the same for
all users and two sample external Dictionaries (DICT1 and DICT2) which must all always named
the same. These files in content and format are subject to change, they are only for testing at this
time. You will note that Q and Z signals are used in the sample DICT 2. These dictionaries can
hold 32 words each up to 10 characters long as the tool is currently coded. The number of
entries can not be changed, so 32 entries by 3 dictionaries yields a total of 96 selections.
However, the number of characters per selection for longer phrases can be changes.
AQC-ALE MEET ME
AQC-ALE provides the “Meet Me” dialog for rapid frequency changes that can steer an entire net
on the fly, the “Meet Me” Orderwire command capability.
The “Meet Me” capability requires that all stations in the link be under computer control and all
are using the exact same GROUP/Channels configuration, then the NCS or any station can steer
the group (or individual station) to a new channel instantly without the need for a voice
announcement or even an AMD message.
The process simply requires entering the RX and TX frequency in Hz (channel based pull down
from current GROUP is planned) and checking LSB if required and clicking OK, then an
Ordewire message is sent and all the stations will QSY to the new frequency/mode pair if entered
correctly and if existing in the current GROUP of all linked stations. Optionally stations may be
added or deleted from the linked stations and an acknowledgement (Ack This) may be requested.
ALE BASICS
The basic operation of ALE involves a calling station attempting to establish a link with a remote
ALE station where an ALE linking call is placed, where upon the successful completion of a 3-
way handshake, the HF radios will have the ability to exchange information using the frequency
selected for the ALE link until such time interference and or propagation conditions result in
unreliable information exchange or the ALE link state times out due to lack of data
communications.
The information exchange can be in the form of Voice or Data. If Voice is the follow on mode of
communications and the PC-ALE RED PTT is not used to key the radio, the ALE link timer is
counting down, thus the TWA during the link should be changed to 0 to hold off a the timer
expiring.
Any supported Data modes used, either native ALE FSK signaling protocols or higher data
throughput rates available with MIL-STD-188-110 PSK modem and optional protocols or via
external TNC/Modem protocols. In addition, other PC Sound Device communications software
can be used for attended follow on data communications. The RESOURCES button in PC-ALE
can be used to release PCSDM and CAT RS232 resources if required to make use of 3 rd part
communications software.
DATA MODES
Below are the combinations of supported data protocol modes within PC-ALE and their current
status.
Automatic Message Display (AMD) - This message protocol is mandatory for all ALE
controllers. NOTE: The confirmation handshake, referred to in PC-ALE as “Linked TWX”, often
referred in the ALE hardware world as “Orderwire Handshake” is not supported by all hardware
controllers or is often not enabled for more efficient usage of on-the-air channel time. In PC-ALE
the last 100 received AMD messages are available for review and will be over written in FIFO
order and can optionally be deleted with user confirmation from the Data > AMD MSG menu
selection.
NOTE: For ALE, the DBM, DTM and FS-1052 as well as the FTP modes if selected without
first having an ALE LINK established, all have the ability to establish the LINK and then send
the message and then automatically CLEAR the LINK. For FS-1052 Immediate Mode must be
selected on from the FS-1052 Options menu and ALWAYS must be checked on the MIL-STD-
188-110 menu. As AQC-ALE does not support this, these features are grayed out.
Data Block Message (DBM) - This is an optional message protocol that most ALE
hardware systems do not provide as standard. DBM messages can be up to 32KB in size
in PC-ALE.
NOTE: ALE hardware units tested to date are not compatible with PC-ALE ( or MARS-
ALE) DBM ARQ.
DBM ARQ
- This protocol will send a short message of EEI length usually in one piece, however
longer messages will display piece by piece depending on the size, the system may
exchange multiple ACK/NAK sequences prior to completion.. This protocols has a
musical quality to it toward the end, the sending station will get a confirmation message
similar to:
DBM BRD
- Broadcasts the message, no automatic feedback regarding success.
- LINKED TWX is NOT to be checked. If you have it checked you will receive a
HANDSHAKE FAILED indication for the number of retries you have set and you will
always get a MSG SENT indication as seen below:
File Transfer Protocol (FTP) - This capability is only for use between stations using
PC-ALE. It is not to the RFC-959 File Transfer Protocol standard specified in MIL-STD-
188-141B Appendix E.
DBM FTP -
- LINKED TWX is REQUIRED checked at both sending and receiving stations.
- This is not the fastest way to send a file with the tool. It will support sending a binary file
or ASCII file. It is best to only send small files. I would not send anything larger than
10Kb at present. The maximum FTP file size as coded is 500KB.
- The receiving station will find the file, it successful, in their \DOWNLOAD directory
with ALE.EXE is located. The sending and receiving station may get a lot of messages
during this one.
- You may get HANSHAKE FAILED you may and recover a number of times depending
on retries. When completed successfully the sending station will get a message similar to:
Data Terminal Message (DTM) – This is an optional message protocol that most ALE
hardware systems do not provide as standard. DTM messages can be up to 32KB in size.
DTM BRD
- LINKED TWX is NOT to be used. The sending station end will default to OFF. When
active on the receiving end it will signal a handshake failure as the receiving station its
not to send a confirmation handshake for DTM BRD.
DTM ARQ
- LINKED TWX is REQUIRED checked at both sending and receiving stations. During
the sending of the message, depending on the size, the system may exchange multiple
ACK/NAK sequences prior to completion. The receiving station will see even short
messages of a few lines display piece by piece on their terminal.
NOTE: ALE hardware DTM ARQ tested to date is 100% compatible with PC-ALE.
FS-1052 FTP -
- This is the fastest way to send a file with the tool. It will support sending a binary file or
ASCII file. It is best to only send small files no larger than 10Kb at this time. The
maximum FTP file is 500Kb as coded.
- At this time, after each FS-1052 FTP message the transmitting station needs to break the
link, then reestablish the link to send the next message.
- The receiving station will find the file, if successful, in their \DOWNLOAD directory
where the PC-ALE executable (.EXE) file is located. The sending and receiving station
may get a lot of messages during this one.
- When completed successfully the sending station will get a message similar to:
FED-STD-1052 Protocols - Messages under PC-ALE FS-1052 can be up to 32KB in size and
“Terminate when done” works will clear the ALE link when the message has been sent.
Broadcast (BRD) will send the message for as many re-transmissions are selected under the FS-
1052 DLP Appendix B Options menu, the default being 1. There is no handshake with BRD.
In ARQ mode the message is sent once and the speed can be locked or allow to change with
channels conditions in an async manor. The number or re-transmissions for errors are selected
under the FS-1052 DLP Appendix B Options menu. There is no handshake with BRD.
Any non-ALE data mode can be used for ALE follow on to an ALE inlink state. However to
retain the ALE inlink state one of two approaches much be taken. Either TWA=0 or the
RESOURCES button must be used, which is a must if any hardware TNC/Modem use is to be
made. If another sound device based application is to be used, the Radio Emulation (REM) port
must be used.
RESOURCES BUTTON APPLICATION
TBD
TBD
MESSAGING INTERFACES
The front panel as detailed elsewhere proves main menu, the TUNE window, MIL-STD-188-110
status window, Scan Group and ALE mode windows, in addition front panel controls are
provided in support of rapidly changing some parameters on the fly that are found on the MIL-
STD-188-141 Options menu.
The name entered for the currently selected Scan GROUP will always be displayed in the “Scan
Group” window. The current ALE mode will always be displayed in the “ALE Mode” window,
where “NEITHER” indicates that since the tool has been started it has not heard any ALE and has
not been used to make any ALE call, thus it is not committed to either mode. NORMAL indicates
that the tool is in baseline ALE mode from either an intercept of an ALE transmission, or having
made and ALE call. ALTERNATE indicates that the tool is in AQC-ALE mode from either an
intercept of an ALE transmission, or having made and ALE call.
The four push button controls below the “ALE Mode” window are toggles for AQC, AQC-
BURST, SOUNDING and Linked TWX enabled/disabled status. When a push button is pressed,
the state will toggle and a message will appear in the lower Engineering window that announces
the change of the state for the particular parameter. In the future, the state of the push buttons
being depressed will indicate that the parameters is Enabled, at present there is no correlation.
The two list box controls provide for the selection of values for TWA and SCLC, a mouse double
click of the left mouse button will cause the selection of the highlighted parameter and a message
in the lower engineering window indicating the change has taken place.
The Icon Tool Bar as seen above resides just above the two messaging windows, from left to right
icons are:
Clear Screen - [White Square icon]: Clears all text from both the Message window and Monitor
windows.
Toggle Receiver Muting - [Black Speaker icon]: Mutes receiver audio as operator has configured.
Push-To-Talk - [Red Square icon]: Immediately toggles the Radio PTT line that the user has
configured for PTT. This Push-To-Talk button MUST be used for all ALE inlink PTT for Voice
follow on if the TWA has not been set to zero (0) to prevent a link timeout and return to ALE
scanning during Voice operation. For some make/model radios as detailed in RHUG Appendix A,
this is the only Voice Push-To-Talk when the software is running regardless of being in ALE
inlink or just being paused single channel.
Step Back a Channel - [Less Than symbol]: Causes the controller to reset the radio frequency and
move to the most previous channel in the currently selected GROUP. (not used for single channel
operation).
Pause Scan - [Double Vertical Bars]: Causes SCANNING or SOUNDING to Pause (not used
forsingle channel operation).
Step Forward a Channel - [Greater Than symbol]: Causes the controller to reset the radio
frequency and move to the next channel in the currently selected GROUP (not used for single
channel operation).
Resume Scan - [Double Greater Than symbols]: Causes SCANNING or SOUNDING to Resume.
Individual Clear - [Telephone OFF Hook icon]: When LINKED, clears the LINK.
Kill Current Link or Outgoing Call - [Black Axe icon]: When LINKED, KILLS the LINK.
Manually Control Radio Assets - [Keypad icon]: Initiates the "Manually Control Radio Assets"
operator interface panel. (not used for single channel operation).
Manual Voice ID - [ID icon]: Initiates the sending of the voice_id.wav file by placing the radio
into PTT for as long as it requires to the play the voice_id.wav file. If the voice_id.wav is NOT
present, it will simply cause the radio to toggle PTT. NOTE: Do NOT click the ID icon unless
you desire to make an on-the-air transmission of the contents of the voice_id.wav file.
DATA BAR
The PC-ALE Data Bar provides the facility for rapid messaging using any supported protocol
where the entire message to be sent is typed into the MGS/CLI area of the Data Bar, this
facilitates rapid sending or resending of a message without the need to navigate the menu’s for
access to the Data Dialogs. In addition the Data Bar provides for direct entry of MMI commands
by the operator where an Enter key stroke completes the command sequence. Here is the Data
Bar docked at bottom of the tool display:
Just as can the Tool Bar, the Data Bar can be docked or floating or closed altogether. Code has
been added for a new menu selection of Dialog Bars which replaces the previous Tool Bar menu
selection for the docking and access of the bars if closed.
The Tool Bar could be floated and docked top (default), bottom, left or right, but if closed it could
not be accessed again without restarting the tool. I have added code to re-launch the tool bar that
works up to a point at present, the buttons work, but all the icons are grayed out. The Data Bar on
the other hand will reopen without any issues and it can be docked at bottom (default) or top.
Charles Brain first added a Data Bar to PC-ALE some time back, but his implementation and ours
is somewhat quite different. Those differences run much deeper than just appearances and the fact
that his Tool Bar and Data Bar not static.
First, to undock either of these you either double click on area where there is no control or you
click on the same area and drag the bar away from its docked position. Both bars can be docked
top or bottom together by the way. Both bars can be some what resized in centering but not
increased or decreased in overall size. Both bars can be floated completely off the tool if it is not
opened to full screen and re-docked by dragging into position of via use of the Dialog Bars menu.
The bars function 100% when docked or not and the Data Bar being closed does not create any
issues with OWN ADDRESS data being sent to it. However, if the Data Bar is closed and your
station becomes ALE linked and you then re-open the Data Bar, the OWN ADDRESS of the
linked station will not appear in the ADDRESS window of the Data Bar, you will need to
manually type in for Data Bar use (which is always the case with the PC-ALE Data Bar). To see
all stations that you are INLINK with if more than one you must still use the menu ADDRESS >
LINKED or the MMI command LINKED.
The Data Bar has a few command buttons on it as follows: REUSE LAST, CLEAR MSG,
RESET MODEM and MILS BRD, the later of which will only be displayed if your increase the
default size of the tool on your desktop. REUSE LAST when clicked will paste the last MSG/CLI
text back into the MSG/CLI text entry window for editing or immediate reuse, which is very
handy, especially if using an AMD and you did not hear the other station respond at all. CLEAR
MSG just clears the Message Window and updates the log if Log to Disk is active. RESET
MODEM is the same as using Tools > Reset Modem, except now its real handy when/if needed.
The Data Bar operates in three modes, one is as an Man Machine Interface (MMI) Command
Line Interface (CLI) when MMI CLI is checked where you can enter any MMI commands and
then just hit ENTER ( the ENTER key is also supported in the CLI under the TUNE display now)
to execute the MMI command. As the Data Bar can be closed and will like be for most stations
running as BBS stations as it takes up valuable Engineering Window area, the small CLI will be
retained. With the new Data Bar MMI CLI you just type the commands and any supporting
arguments and don't need to worry about text case.
The Data Bar operates in a keyboard fashion when in a normal ALE or AQC-ALE linked state for
the PCSDM modem protocols where all that is sent via the MSG/CLI text entry ( AMD's are
limited to 90 characters no matter how many are typed and the text is converted to upper case
automatically) as a single line message when ENTER is hit is displayed as an outgoing message
in the Message Window intermixed with any responses from a Remote ALE station, thus if Log
to Disk is enabled, you get a full two-way exchange log. The Data Bar is in data mode by default
at program start and is in ARQ mode, for BRD mode you need to check BRD/FEC which only
affects PCSDM protocols. Any use of the Data Bar for the external TNC/Modem support can be
made at anytime, whether ALE linked or not. When not ALE linked, entering an OTHER
ADDRESS into ADDRESS and selecting AMD, DTM, DBM or FS-1052 and entering a
message, will cause an ALE linking call to commence ( this is NOT supported for AQC-ALE
with an AMD as you can NOT send an AMD during an AQC-ALE linking call ) and after the
ALE link the message in the selected mode will be sent and the link will be maintained as there is
no provision at this time for a "Terminate when done" selection as there is on the Data Dialogs
for the PCSDM protocols. You can not at this time enter an ADDRESS and have TNC selected to
initiate an external TNC/Modem link unless you use the MMI CLI interface selection. The use of
DBM is in my opinion the better choice vs. DTM or AMD for FSK modem keyboarding, be it
BRD or ARQ, with the default Retries and Frame Size settings now being used, a typical 80-90
character or less line of text fires off fast and both stations can go back and forth at a nice rate in
keyboard to keyboard. The selection of BRD vs. ARQ when ALE linked will automatically
ENABLE/DISABLE the LinkedTWX setting for BRD vs. ARQ for DTM and DBM, however the
AMD support is locked into LinkedTWX via the Data Bar, also the tool will now automatically
set up in LinkedTWX at both program start and when Scanning is started if it was turned off. To
use the FS-1052 support the MIL-STD-188-110 modem must be in LINKED or ALWAYS, at
this time we still ask that if be set to OFF for all multi-channel use of PC-ALE.
MAN MACHINE INTERFACE (MMI)
PC-ALE provides a Man Machine Interface (MMI) which is a command interpreter that
processes structured text commands from specific system files (.DAT, .MAC or .QRG) or via
Data Bar user entered commands that PC-ALE executes to bring about either configuration or
operational command and control.
Complete details on the MMI and all the commands can be found in the PC-ALE Man Machine
Interface Guide. Herein we shall cover a few MMI commands either must be understood by all
users or will be of interest to many users.
There are four automated PC-ALE system files that can contain MMI commands that must exist
with or without commands else a file not found error messages will display, the files and their
purpose are:
Example files for all four are provided with the latest full install of PC-ALE where no commands
are active, thus they are dummy files and need to be present to suppress the error messages.
The format of these MMI files is that a pound sign (#) is a remark and all after it on the line is
ignored by the MMI interpreter. For a line without a pound sign an MMI command string is
expected with no more than 20 words or 1,000 characters which ever comes first, with a
maximum limit of 255 lines per file.
When MMI commands are processed, an error message will be displayed in the engineering
window for each MMI command line when the line contains an error. Any illegal commands will
result in SYNTAX ERROR. Any command that is legal but not in the correct order will generate
an AMBIGUOUS COMMAND. Any command that requires parameters after will generate NOT
ENOUGH PARAMETERS when the arguments are missing.
LIMIT CALLING:
LDG AT200PC:
The line LDG MANAUAL when not remarked out places the LDG AT200PC ATU into
MANUAL When an ALE link takes place. It will automatically go back into AUTO when the
ALE link is cleared
#
# LDG MANUAL
MACRO files…………………………….
# MACRO1.MAC
#
# Enable Listen Mode
#
ENABLE LISTEN
#
# MACRO1.MAC END
TO DO ADDS TO ADDITIONAL SECTIONS TBD:
AMBUSH:
The Ambush Linking Call which supports target stations sounding with "THIS IS"
automatically from a list of addresses you add, where if a "THIS IS" sound is heard from
one of them, it causes your station to respond at the end of the THIS IS.
So you can in effect "Ambush" a station with a linking call automatically with no manual
call on your part. The station is then deleted from the list after the successful link.
You can also configure to attach an AMD message to be sent automatically so that if you
are not at the station during the Ambush link, you can convey your intent of the call if not
the full details to be conveyed. The idea is that a station can scan covertly link when it
hears the station of interest and even send an AMD to it (which when Ambush is added to
MARS-ALE will work even better with AMD Retries). When sounding using THIS IS,
that station listens on the channel for 2 seconds after the sounding, thus this is why
Ambush only listens for THIS is as with THIS WAS it resumes scanning immediately.
A THIS WAS indicates the sounding station is leaving the channel immediately. Whereas
a THIS IS indicates the station will monitor the channel after the sound. The ALE
standard infers that what has been implemented as an Ambush Call is a design goal for
ALE by the way. There may be some ALE hardware radio that offers a similar feature
that does what the PC-ALE Ambush Call provides, but I am not aware one to offer up as
an example as I am not familiar with each and every make/model of ALE radios, I did
just recently learn that Datron 7000 ALE radios provide a Manual Sounding feature
which I added to both PC-ALE and recently the developing MARS-ALE v3.00 baseline,
again, how many other ALE radios offer that I do not know, these are all examples of
features not required by the ALE standards.