ZL2AFP FSM Form Messaging

Setup and Help Information

V0.04, 20.06.2015

MENU
Introduction	Installation	Generating a Message	Sending	Receiving

Introduction

FSQ is a Fast Simple QSO mode for MF/HF. It works well under NVIS and sunrise/sunset conditions on the lower bands, and also works well for short skip on higher bands. It can also be used on VHF FM, and clearly has a much wider useful range of operating conditions that other more conventional digital modes. What's more, it's just plain fun to use.
FSQ was specifically designed for Emergency Comms applications, and can be used for net management, automatic station status query, personnel management, transmission of images and files, as well as simple chat. It's the file transfer capability that concerns us here. FSQ can direct files to be stored at any individual station, or all stations on the channel.
FSQ, in association with FSM, uses this file transfer technique to send formal messages, formatted in a pre-determined manner. Because the format and many of the form details (everything but the actual message) are known by sender and receiver, message transmission is very efficient. The Form Manager program is of course called FSM - Fast Simple Messaging!
Message Form
The Message Form consists of two parts, both known before-hand to all stations within a network. These are the message template xxxx.defs, and the corresponding image file yyyy.gif, whose name will be defined in the first line of the .defs file. The definitions file specifies the image file name, and defines where to place the fields within the document, when it is displayed either by the sender or recipient. The image file is a bitmap, displaying all the non-transmitted information, such as titles, field names, lines, boxes, borders and even a logo. The filled-out forms can be saved for transmission as text files, saved as images, which can be sent as FAX pictures (via FSQ) or printed out for delivery. The ability to send the messages as a FAX is a 'belt and braces' fallback method, useful where the recipient does not have the appropriate Message Form. Using the form method is preferred however, as transmission is much faster and reception is far more reliable.

Message Text Files
Because all message files are plain text, they can be sent very easily by FSQ, using the 'File Send' command (the '#' command). The files are saved automatically on receipt, and their receipt is acknowledged by a short automatic transmission by the recipient. The files are human-readable (with or without formatting), and consist of a predetermined number of fields of text separated by a '`' (back quote) symbol. A maximum of 20 fields can be accommodated, although 10 - 12 is more usual.
In keeping with the whole FSQ philosophy, FSM is kept very simple, and the process is completely manual.
Multi-function Program
FSM performs all the required functions in a single program. Message files are filled out using FSM, edited by the operator to add destination and time, and after transmission and reception using FSQ, messages are subsequently loaded back into FSM for receive operator editing, reading, saving or printing.

Installation

Download the latest zipped archive from the ZL1BPU website at ZL2AFP FSM.

Unzip the archive into the same folder used for FSQ. The archive includes sample forms, related definition files, and help information.
Right-click on the executable FSMvnnn.exe, select 'Create Shortcut', then drag the shortcut to the desktop or your menu.
When first started, the program will create the required sub-folders.
Start FSM, and it show you the default message form. In order to select the form you need (typically as instructed by the Net Manager) use File/Open message form template from the menu. Select the appropriate file, for example AREC.defs. If all is well, the message form should open, allowing you to either start typing a message, or load a received message for viewing and/or editing.

The FSM program window, ready to be filled out

FSM (and any typical Emergency Messaging Service) has four distinct functions. In the field, a single-operator station will probably perform all these functions at various times. At a busy base station, the functions may well be separated and performed by different team members, using different computers, even in different locations. The four functions are:

Message Entry
Here a typist types from a hand-written message, or types in the message verbatim from the sender.
Message Transmission
A radio operator decides (or is told by a manager) which station to send the message to, fills in the message preamble appropriately, and then saves and sends the message using FSQ.
Message Reception
A radio operator loads the received message, edits the preamble appropriately, and saves the message.
Message Delivery
The operator or a runner prints out the message and delivers it. If no printer is available, the recipient can view it on screen, or the operator can fill out a copy of the form by hand for delivery. The message can also be saved a graphics file and delivered to the recipient on a memory stick, or attached to an email if appropriate (but don't rely on the internet in times of emergency).

Typical Message Handling Protocol
Guided Tour
The FSM program is very straightforward. All of the window is taken up by the message form, on which you type, edit, or view the messages (see picture above). There is a simple menu system at the top, with File, Options and Help items. From the File menu you can open the template (or a different template), clear the form, open and display an incoming text (.fsm) message, save a message you enter as a text file (.fsm), save the complete form as an image (.gif), and print the message on the form to a printer. (Preferably use A5 paper).
From the Options menu you can select the font used to display the message. The default font is Arial 10 Bold. The font has no effect on the transmitted file or message, only presentation, saving as an image, and printing. It can be very useful to use a larger, clearer font, if you are forced to deliver the message via FSQFAX.
The process of handling the messages correctly (see diagram above) is much more complicated than using the actual program. FSM is very simple to use, for all the functions listed above. We'll now cover each of these in detail.

1. Generating a Message

Message Entry
Start the FSM Form Manager program. Open the appropriate Form Definition (.defs) file. If you've had previous messages viewed, first clear the Form Manager (File/Clear message form), then start typing. Type the message into the program, starting at the TO field. (Everything above the TO/FROM line is for the radio operators' exclusive use). Ideally TO and FROM should be identifiable persons' names. If necessary, a title may be used for the recipient instead, such as 'Stage Marshall' or 'Fire Chief'.
Fill out the message NUMBER using the next available number from your message log (kept separately). Fill out the UTC DATE/TIME, preferably in standard ITU-R RFC-3339 format (YYYY-MM-DDTHH:MMZ), or other local standard. Use the CHECK box to mark the entry operators initials once you've checked that the message is correct. This is your signature testifying that the message is correct, so do the job properly!
Add the recipient's ADDRESS. This may be a street address, or a less formal one (e.g. 'Start Stage 15') if more appropriate.
Fill out the message, and sign it with the sender's name (the FROM person), and/or title. Save the message as a .frm file (File/Save message text to send), using the the operator check initials and message number as the file name (e.g. jfk0034.frm). Save it in the 'Outgoing' folder, or on a memory stick, depending on the station setup.
Deliver (if necessary) the file to the transmit operator, if the function is separate. This can be done via network, or via 'foot net' using a memory stick. Mark the message entry log as 'sent for transmission', with the time.

Form after message entry - message number 'mg002'

2. Message Transmission

Start the FSM Form Manager program. Open the appropriate Form Definition (.defs) file. Open the .fsm message file that is to be transmitted (should be in the 'Outgoing' folder or delivered on a memory stick). This will display the message.
Read the message addressee and address, and determine how best to deliver it, according to available resources (Use the Heard List for currently available stations, and check their QTH using the @ command). You may need to relay the message via another station. You may also be instructed separately where to send messages (for example a field station usually sends all messages to base). Using FSQ, check that the station is still available and in FSQCall Directed Mode, by sending it a '*' command. The station should reply 'Active'.
As transmitting operator, now fill in the fields at the top of the form: TRANSMITTED TO, and TIME OF TRANSMISSION. Use UTC time.
Now save the message in the 'Outgoing' folder again, and in FSQ, type the callsign of the TRANSMITTED TO station in the TX pane, followed by '#'; thus:
callsign#
Now use 'File/File to send' on the FSQ menu, and select the file to be transmitted (from the 'Outgoing' folder). The filename should be a concatination of the originator's initials and message number, with the suffix .frm. The file name and the message will be appended to the direction automatically. Once the message is loaded into the buffer, press ENTER, and the message will be sent.
Below is an example of an FSM file as it is actually transmitted (it is the file mg002.fsm used as an example in the above picture, but with FROM and TX Time time appended):

` `ZL2AFP`18:29`09/06/15 18:27 UTC`Con`Murray`002` `1 Norwood Rd, Kaiti, Gisborne`Hello Con This is a first test message using FSM V0.00. From zl1bpu... I will be home this morning until about 10am, then I have an appointment at the Eye Clinic in Manukau, and won't be home again until mid afternoon. - 73 - Murray` ` ` ` ` ` ` ` `

3. Message Reception

The receiving operator will be alerted to the arrival of a stored message by the FSQ MSG RX button glowing red. At this time you can check the incoming message by clicking on the button, and reading the raw message in Notepad. If the message seems uncorrupted, save the message (via Notepad) in the 'Incoming' folder. (Hint: set the default program to open .fsm files to be Notepad).
If there are minor and obvious errors in the message, you will be able to correct them in the next step. If there is any doubt, or the errors are more substantial, contact the sending station and ask for the message to be resent.
Start the FSM Form Manager program. Open the appropriate Form Definition (.defs) file. Open the .fsm message file that has been received (should be in the 'Incoming' folder). This will display the message. Edit the RECEIVED FROM field to show the station callsign which sent you the message (it will be in the Receive Pane), and the TIME OF RECEIPT.
If there are really minor errors, such as word corruptions, correct these at this time. Do not attempt to correct gross errors, instead have the message sent again. Save the message again, but in the 'Completed Messages' folder.

The completed received message ready for delivery

4. Message Delivery

To deliver a printed copy of the messages received, you will need a printer capable of printing on A5 paper, and a source of paper. A cheap black-and white ink jet printer will be best for field use, as they use little power and can be run off a 12V inverter. At base, an AC operated laser printer will be preferred, as the running costs are lower. (Remember also that ink jet printing is not waterproof).
To print an incoming message, start the FSM Form Manager program. Open the appropriate Form Definition (.defs) file. Open the .fsm message file that has been received (should now be in the 'Completed Messages' folder). This will display the message. Select 'File/Print message form' to print the message. The message can now be delivered by hand to the address and addressee shown on the form (use a runner or courier as available).
If the message cannot be printed, it may be possible to have the recipient view the message on screen. If this is not possible, use a message pad and manually copy the complete message off the screen for delivery. In some cases the recipient may have a computer available. In this case, save the message on a memory stick using 'File/Save entire message form', and deliver it on the memory stick.

What if the destination station doesn't have FSM, or is missing the correct form?

This is not a preferred scenario, but the message can still be delivered. The transmitting operator opens the message with FSM, and selects the largest font that allows the whole message to be seen on the screen. He then saves the message (say as jfk0002.gif) from FSM, using File/Save entire message form. The operator then uses the FSQ-FAX transmission facility to deliver the message. This will be slower, and reception quality can suffer if the signal is noisy or the path has significant multi-path.
The receiving operator can correct the Phase and Slant, save the image, open the received image with Paint (or similar graphics program) and print the message for delivery. You can copy and paste directly from the received image into Paint, but it's best to save the image anyway, in case you need another copy.

Software Compatibility

This Windows™ software is written in ANSI C, and is compatible with Windows Vista, WinXP, Win7 and Win8. It also runs under Linux using Wine. Processor speed and memory requirements are minimal, and the program size is under 100kB.
The program window is small, and fixed in size, about the size of the corresponding Radiogram form.
The program consists of just one file, and no changes are made to the computer's registry or anywhere else. To remove the program, simply delete the files made during installation.
Developers interested in writing software for FSQ (FSQCall or FSM) should contact ZL2AFP (zl2afp "at" xtra.co.nz) for source code and other details.