w4kek/WSJT-X
1
0
Fork 0
mirror of https://github.com/saitohirga/WSJT-X.git synced 2024-11-22 04:11:16 -05:00
Code Issues Packages Projects Releases Wiki Activity

Add to User Guide a caution about using nonstandard callsigns.

Browse Source
This commit is contained in:
Joe Taylor 2018-12-14 14:13:19 -05:00
parent e74c1b942a
commit c28208431d
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/user_guide/en/make-qso.adoc
View File

@ -126,12 +126,12 @@ Either callsign (or both) may have /P appended.
K1ABC W9XYZ RR73
[[COMP-CALL]]
=== Compound Callsigns
=== Nonstandard Callsigns
*FT8 and MSK144*
Compound callsigns like xx/K1ABC or K1ABC/x and nonstandard callsigns
like YW18FIFA are supported for normal QSOs but not for the special
Compound callsigns like xx/K1ABC or K1ABC/x and special event
callsigns like YW18FIFA are supported for normal QSOs but not for
contest-style messages. Model QSOs look something like this:
CQ PJ4/K1ABC
@ -159,6 +159,11 @@ Except for the special cases involving /P or /R used in VHF
contesting, _WSJT-X {VERSION_MAJOR}.{VERSION_MINOR}_ offers no support
for two nonstandard callsigns to work each other.
TIP: Using a nonstandard callsign has definite costs. It restricts
the types of information that can be included in a message. It
prevents including your locator in standard messages, which
necessarily impairs the usefulness of tools like PSK Reporter.
*JT4, JT9, JT65, and QRA64*
In the 72-bit modes, compound callsigns are handled in one of two