# FSQCALL Operating Rules

## Maximising the benefits of FSQCall

V0.41, 21.10.2016

### FSQCALL Operating Rules

> 1. In Active mode, 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 "/" or "\" or "-" as callsign extension separators (e.g. zl1xyz/2) for various reasons to do with parsers and file naming. The only universally safe separator is underscore "_".
> 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. 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. This also applies to allcall and cqcqcq which are also considered its own callsigns by the receiving station.
> 7. You should not include your own callsign, or another callsign, more than once, in a relay message (! or ~ command).
> 8. You should always wait until the channel is clear before transmitting.
> 9. FSQCALL commands will not work unless both originating station and recipient (and any relay station) are in Active 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 FSQ' mode, by releasing the SELCAL button. You don't need Active mode to chat, but in doing so you lose a lot of features, and Directed messages will not occur unless originating and recipient stations are in Active mode.
> 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. By the same token, Telemetry transmissions should not be used on busy channels. In most circumstances a 30 minute transmission period is plenty.

### Calling Frequencies

> > Region 1
> > 80m 3588 kHz USB (sunset to sunrise)
> > 40m 7044 kHz USB (sunrise to sunset)
> > 30m 10144 kHz USB (local day, DX night)
> > Region 2
> > 80m 3594 kHz USB (sunset to sunrise)
> > 40m 7104 kHz USB (sunrise to sunset)
> > 30m 10144 kHz USB (local day, DX night)
> > Region 3
> > 80m 3580 kHz USB (sunset to sunrise)
> > 40m 7105 kHz USB (sunrise to sunset)
> > 30m 10149 kHz USB (local day, DX night)

> Calling frequencies quoted are 'dial' frequencies for default 1500 Hz centred tones. If you need to use 1150 Hz centred tones for technical reasons, you should set the 'dial' frequency 350 Hz higher. Note that all operation is on USB.

> It is suggested that working frequencies (where needed) be 1 kHz above or below the calling frequencies. Local arrangements can be made for other bands. The 60m band would be a good choice for late afternoon in winter.

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