# WSQCall Operating Rules

## Maximising the benefits of WSQCall

V1.20, 24.03.2018

### WSQCall Operating Rules

> 1. In CALL mode (SELCAL ON), you must use a Direction (target) callsign in the message body of every sentence for the other station to see a message. The primary recipient callsign must be the first thing placed in the sentence.
> 2. All users should set their callsign (Menu/Options/Callsign) in lower case. The command parser is case sensitive, so using upper case or mixed case callsigns leads to confusion. The callsign thus set becomes the station's Direction (target) callsign, and must not include any forbidden characters (the trigger characters and reserved characters etc). There can be unexpected results if you use some callsign extension separators (e.g. zl1xyz#2) for various reasons to do with parsers and file naming. Both '/' and '_' are safe.
> 3. The Direction (target) callsign used in commands will only work if it matches the case used by the intended recipient. Some stations may not be following Rule B. Check the callsign in your Heard List, or call it from there with the mouse.
> 4. The Direction (target) callsign MUST be followed immediately by a specified trigger character, or the command will be ignored by the intended recipient. 'Space' is considered the trigger only for chat sentences and may not be used before, or in conjunction with, other command triggers.
> 5. All stations within a network must have unique callsigns. Calls such zl1ee_1 and zl1ee/p are permitted, and are treated as different to zl1ee.
> 6. You should not give two commands to the same station within the same sentence. Only one will be actioned, and results may not be as expected. This also applies to allcall, which is also considered its own callsign by the receiving station.
> 7. You should not include your own callsign, or another callsign, more than once, in a relay message (! command).
> 8. You should always wait until the channel is clear before transmitting.
> 9. WSQCall commands will not work unless both originating station and recipient (and any relay station) are in CALL mode. If you are not confident you can abide by the rules, and follow the appropriate syntax (if for example you are a beginner), change to 'vanilla WSQ' mode, by releasing the CALL button. You don't really need CALL mode to chat (the QSO will be faster without the CALL mode overhead), but in doing so you lose automated features, as well as logging. Directed messages will not function properly unless originating and recipient stations are in CALL mode (Selective Calling ON).
> 10. Sounding should be kept to a minimum on calling channels. A 30 minute period is plenty. Smart Sounding and extended Sounding messages should not be used on busy channels.
> 11. Don't send files larger than just a few words, as this would tie up the transmitter and channel for long periods. Some transmitters may get very hot after even a few minutes operation.

### Non-Directed Chat

> WSQCall transmit and receive behaviour depends on the setting of the CALL button.

> 1. Directed Mode (CALL mode, default)

> - CALL button will be bright blue.
> - Transmission starts with callsign and checksum preamble (e.g. zl1ee:fc any text or command)
> - Reception is screened by Selective Calling and only placed on receive pane (in blue) if message is for recipient. If it is not for the recipient, or the sender's call and check sum don't match, the text will be placed on receive pane (in green)
> - Heard Log and WSQPlot report incoming stations.
> - Soundings and other non-directed text will be placed on the receive screen in green.
> 2. Non-Directed Mode (CALL released)
> - CALL button will appear dark, and crossed out with a red circle and line.
> - Transmission starts with no preamble at all (e.g. any text)
> - Everything received is placed on receive screen (in green).
> - Heard Log and WSQPlot are ineffective.
> Use Mode (1) whenever practical, and always return to it when the station is unattended.

> The purpose of mode (2) is to reduce the overhead in quick exchanges. If you use this mode, transmissions need to be manually identified by other means as often as legally required. Preferably don't use this mode with more than two stations on the channel. The Heard Log and WSQplot do not work with stations in this mode.

### Calling Frequencies

> > Region 1
> > 630m To be advised
> > 2200m To be advised
> > Region 2
> > 630m To be advised
> > 2200m To be advised
> > Region 3
> > 630m 474.000 kHz
> > 2200m To be advised

> Calling frequencies quoted are 'dial' frequencies for 1500 Hz centred tones. Note that all operation is on USB.

> It is suggested that working frequencies (where needed) be 100 Hz above or below the calling frequencies. Local arrangements can be made for all LF/MF bands. Check with your LF/MF mail group. In VK/ZL and across the Pacific we use the Yahoo 600m group, groups.yahoo.com/neo/groups/600m/.

Copyright © Murray Greenman and Con Wassilieff 2013-2018. All rights reserved.