From ebeab718d7b50010c5fc8420d6b79900dc7ee4c1 Mon Sep 17 00:00:00 2001 From: Joe Taylor Date: Tue, 13 Feb 2018 15:55:10 +0000 Subject: [PATCH] Add basic info on definition of one of the "three extra bits". git-svn-id: svn+ssh://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx@8505 ab8295b8-cf94-4d9e-aec4-7959e3be5d79 --- doc/user_guide/en/protocols.adoc | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/user_guide/en/protocols.adoc b/doc/user_guide/en/protocols.adoc index a25df3f22..805ef2e3d 100644 --- a/doc/user_guide/en/protocols.adoc +++ b/doc/user_guide/en/protocols.adoc @@ -9,9 +9,11 @@ additional bit flags a message containing arbitrary alphanumeric text, up to 13 characters. Special cases allow other information such as add-on callsign prefixes (e.g., ZA/K1ABC) or suffixes (e.g., K1ABC/P) to be encoded. The basic aim is to compress the most common messages -used for minimally valid QSOs into a fixed 72-bit length. Information -payloads in FT8 include 3 additional bits (75 bits total), with -definitions yet to be defined. +used for minimally valid QSOs into a fixed 72-bit length. The +information payload in FT8 includes 3 additional bits (75 bits total). +One of the added bits is used to flag special messages used by the +DXpedition station in FT8 DXpedition Mode. Uses for the remaining two +bits are yet to be defined. A standard amateur callsign consists of a one- or two-character prefix, at least one of which must be a letter, followed by a digit