Update the White Paper describing features of WSJT-X Version 2.0.

lib/77bit/wsjt-x_v2.0.txt

@@ -8,10 +8,10 @@ payloads rather than the present 72 or 75 bits.  This modest increase
 in information content will make possible new message types that
 support the following special types of QSOs and exchanged information:
 
-1. NA VHF Contest operation with full support of grid exchanges and
+1. NA VHF Contest operation with full and transparent support of grid
-   "/R" (Rover) callsigns
+   locators and "/R" (Rover) callsigns
  
-2. EU VHF Contest operation with the exchange of 6-digit grids, QSO
+2. EU VHF Contest operation with the exchange of 6-digit locators, QSO
    serial numbers, and "/P" (portable) callsigns
 
 3. ARRL Field Day operation with standard Field Day exchanges
@@ -22,68 +22,34 @@ support the following special types of QSOs and exchanged information:
    callsigns
 
 6. A special "telemetry" message format for exchange of arbitrary
-   information up to 71 bits
+   information (up to 71 bits)
 
-Decoding sensitivity for the new messages will be atleast as good as
+Decoding sensitivity for the new messages will be essentially the same
-for the FT8 and MSK144 modes presently in WSJT-X v1.9.1.  The existing
+as for the FT8 and MSK144 modes presently in WSJT-X v1.9.1.  The
-FT8 DXpedition mode will be supported, and a more powerful DXpedition
+existing FT8 DXpedition mode will still be supported, and a more
-mode may be offered as well.
+powerful DXpedition mode may be offered as well.
 
 In this document we'll call the new FT8 protocol "FT8+".  It will be a
 superset of the FT8 implemented in v1.9.1, providing at least
 temporary compatibility and inter-operability with older program
-versions.  We may decide to remove the support for backward
+versions.  We may decide to remove support for old-style 72- and
-compatibility in FT8 after a specified switchover interval.
+75-bit messages after a specified switchover interval.
 
 In contrast, the new MSK144 protocol will replace the old one without
 backward compatibility.  We believe the smaller and more specialized
 group of MSK144 users will upgrade quickly and not find this
 restriction to be a problem.
 
-
+Here are some examples of message formats that will be supported by
-To minimize any confusion that may arise during a switchover from
+FT8+ and MSK144 in WSJT-X v2.0.  The list is not exhaustive.
-v1.9.1 to v2.0, we tentatively propose the following schedule:
+Parameters i3 and n3 (shown in column 1) are used in the software to
-
+define major and minor 77-bit message types.
-September 15, 2018:
--------------------
-
-A beta-test version v2.0.0-rc1 will be made available for download.
-FT8+ will support the old (v1.9.1) protocol as well as the new message
-types described below.  Frequencies formerly used for JT9 on the HF
-and VHF bands will be recommended for testing the new features in
-FT8+.  MSK144 will be fully functional between any two stations using
-v2.0.0-rc1, but will not be backward compatible with earlier program
-versions.  The original MSK144 protocol will be declared obsolete.
-
-Program version v2.0.0-rc1 (and any subsequent versions 2.0.0-rc#)
-will probably include an automatic "timeout date" or other mechanism
-to force upgrading when newer versions become available.
-
-November 1, 2018:
------------------
-Official GA release of WSJT-X v2.0.0.
-
-
-Dates of relevant upcoming ARRL contests
------------------------------------------
-VHF QSO Party:   September 8-10, 2018
-RTTY Roundup:    January 5-6, 2019
-VHF SS:          January 19-21, 2019
-
-Note that our proposed schedule makes v2.0 available for relevant ARRL
-contests in 2019.  However, the ARRL September 2018 VHF QSO Party will
-need to use v1.9.1.
-
-
-Here are some examples of messages that will be supported by FT8+ and
-MSK144 in WSJT-X v2.0.  The list is not exhaustive.  Parameters i3 and
-n3 are used in the software to define major and minor message types.
 
 ----------------------------------------------------------------------------------
 i3.n3     Example Messages                    Comments
 ----------------------------------------------------------------------------------
  0.0      TNX BOB 73 GL                       Free text
- 0.1      K1ABC RR73; W9XYZ <KH1/KH7Z> -08    DXpedition Mode (Fox only)
+ 0.1      K1ABC RR73; W9XYZ <KH1/KH7Z> -08    DXpedition Mode (sent only by Fox)
  0.2      G4ABC/P R 570007 JO22DB             EU VHF Contest
  0.2      PA9XYZ 590003 IO91NP                EU VHF Contest
  0.3      K1ABC W9XYZ 6A WI                   ARRL Field Day
@@ -122,7 +88,11 @@ i3.n3     Example Messages                    Comments
 
 
 Here are some examples of minimal QSO sequences that take advantage
-(where necessary) of the new protocol capabilities:
+(where necessary) of the new protocol capabilities.  Model QSOs number
+1 and 2 are supported already, with the present FT8 and MSK144
+protocols, and number 3 with the existing FT8 DXpedition Mode.  Model
+QSOs 4-8 (and others not illustrated here) require the new protocols
+with 77-bit messages.
 
 ----------------------------------------------------------------------------------
 1. Standard QSO
@@ -151,6 +121,7 @@ CQ KH1/KH7Z
 K1ABC KH7Z -12
                                    KH7Z K1ABC R-14
 				   KH7Z W9XYZ EN37
+				   ... possibly other callers ...
 K1ABC RR73; W9XYZ <KH1/KH7Z> -08
 
 ----------------------------------------------------------------------------------
@@ -187,7 +158,7 @@ PA9XYZ 590003 IO91NP
 PA9XYZ G4ABC/P RR73
 
 ----------------------------------------------------------------------------------
-8. Compound calls
+8. Compound call
 ----------------------------------------------------------------------------------
 CQ PJ4/K1ABC
                                    <PJ4/K1ABC> W9XYZ
@@ -195,3 +166,47 @@ W9XYZ K1ABC -11
                                    K1ABC W9XYZ R-09
 W9XYZ <PJ4/K1ABC> RRR
                                    <PJ4/K1ABC> W9XYZ 73
+----------------------------------------------------------------------------------
+
+
+To minimize confusion that's likely to arise during a switchover from
+v1.9.1 to v2.0, we propose to follow a well advertised schedule:
+
+"RC1 Date"  --  perhaps as early as September 15, 2018?
+-------------------------------------------------------
+
+This will be the first chance for beta testers to try WSJT-X using the
+77-bit messages.  We may restrict this opportunity to specific
+volunteer testers, and we'll probably include an "upgrade by
+xxxx_date" message to remind people that they are using a release
+intended only for testing.
+
+FT8+ will support the old (v1.9.1) protocol as well as the new message
+types outlined above.  To avoid QRMing legacy FT8 users with messages
+they can't decode, we'll recommend testing FT8+ on frequencies
+formerly used for JT9.
+
+MSK144 will be fully functional between any two stations using the RC1
+software, but it will not be backward compatible with earlier program
+versions.  
+
+"RC2, RC3,... Date"  --  perhaps in October?
+--------------------------------------------
+
+As needed, depending on results of testing.
+
+GA Release Date      --  perhaps in November?
+---------------------------------------------
+
+Official General Availability release of WSJT-X v2.0.0.  The original
+MSK144 protocol will be declared obsolete.
+
+
+For reference: Dates of relevant upcoming ARRL contests
+-------------------------------------------------------
+VHF QSO Party:   September 8-10, 2018
+RTTY Roundup:    January 5-6, 2019
+VHF SS:          January 19-21, 2019
+
+Our proposed schedule should make WSJT-X Version 2.0 usable for
+relevant ARRL operating events in 2019.