From 53c090853311a76e4d2218563674f5f27cc98dcd Mon Sep 17 00:00:00 2001 From: Joe Taylor Date: Thu, 13 Sep 2018 09:56:20 -0400 Subject: [PATCH] Editorial changes to planning and development documents. --- lib/77bit/77bit.txt | 24 ++-- lib/77bit/New_Features_WSJT-X_2.0.txt | 164 ++++++++++++++------------ 2 files changed, 100 insertions(+), 88 deletions(-) diff --git a/lib/77bit/77bit.txt b/lib/77bit/77bit.txt index 727f614a6..8854ddcf0 100644 --- a/lib/77bit/77bit.txt +++ b/lib/77bit/77bit.txt @@ -13,17 +13,17 @@ i3.n3 Example message Bits Total Purpose 0.2 PA3XYZ/P R 590003 IO91NP 28 1 1 3 12 25 70 EU VHF contest 0.3 WA9XYZ KA1ABC R 16A EMA 28 28 1 4 3 7 71 ARRL Field Day 0.4 WA9XYZ KA1ABC R 32A EMA 28 28 1 4 3 7 71 ARRL Field Day -0.5 0123456789abcdef01 71 71 Telemetry (18 hex) -0.6 -0.7 +0.5 123456789ABCDEF012 71 71 Telemetry (18 hex) +0.6 ... tbd +0.7 ... tbd 1 WA9XYZ/R KA1ABC/R R FN42 28 1 28 1 1 15 74 Standard msg 2 PA3XYZ/P GM4ABC/P R JO22 28 1 28 1 1 15 74 EU VHF contest 3 TU; W9XYZ K1ABC R 579 MA 1 28 28 1 3 13 74 ARRL RTTY Roundup 4 PJ4/KA1ABC RR73 12 58 1 2 1 74 Nonstandard calls -5 -6 -7 +5 ... tbd +6 ... tbd +7 ... tbd ---------------------------------------------------------------------------------- In case we need them, later: @@ -40,7 +40,7 @@ Facts about the 28-bit integers used to encode standard callsigns: 6,257,896 Difference 2^22 = 4,194,304 Used for 22-bit hash codes ----------- - 2,063,592 available for CQ, CQ xx, CQ nnn, QRZ, etc. + 2,063,592 available for CQ, CQ nnn, CQ xxxx, QRZ, ... Further details: @@ -51,7 +51,8 @@ i3.n3 0.1 DXpedition mode as developed for KH1/KH7Z. -0.2 Report, QSO serial number, 6-digit grid, and Roger for EU VHF contests. +0.2 Report, QSO serial number up to 4095, 6-character grid, and Roger + for EU VHF contests. 0.3 ARRL Field Day exchange (1-16 transmitters). @@ -66,15 +67,16 @@ i3.n3 2. Same as Type 1, but uses /P instead of /R. For European VHF contests. 3. Standard message for ARRL RTTY Roundup. Optional "TU;" at - beginning to finish a previous QSO; then two standard callsigns, + beginning to finish a previous QSO. Then two standard callsigns, optional "R", a 3-bit report (529 to 599), and 13 bits to indicate - US state, Canadian province/territory, or DX serial number. + US state, Canadian province/territory, or DX serial number up + to 7999. 4. One hashed call; one standard, compound, or nonstandard call with up to 11 characters; and an optional RRR, RR73, or 73. --------------------------------------------------------------------------- -The following are tentative: not to be included in first release. +The following are tentative and not included in first release. 5. CQ WW RTTY - US/Can: RST CQZ state/prov R 579 5 NJ R1 r3 z6 u7 DX: RST + CQzone R 559 15 R1 r3 z6 diff --git a/lib/77bit/New_Features_WSJT-X_2.0.txt b/lib/77bit/New_Features_WSJT-X_2.0.txt index 209db71e2..26c293050 100644 --- a/lib/77bit/New_Features_WSJT-X_2.0.txt +++ b/lib/77bit/New_Features_WSJT-X_2.0.txt @@ -2,17 +2,19 @@ -------------------------- This document is an update to the white paper "Plans for WSJT-X -Version 2.0", publicly distributed on July 26, 2018. It describes the -most important enhancements in WSJT-X 2.0 relative to WSJT-X 1.9.1. +Version 2.0" that was publicly distributed on July 26, 2018. It +describes the most important enhancements in WSJT-X 2.0 relative to +version 1.9.1. -A majority of the new features involve the FT8 and MSK144 protocols. -Both have been upgraded to use use 77-bit information payloads rather -than the 75 bits of the older FT8 protocol or 72 bits of JT4, JT9, -JT65, MSK144, and QRA64. Cyclic redundancy checks (CRCs) that protect -against false decodes have been increased from 12 to 14 bits (FT8) and -from 8 to 12 bits (MSK144). These changes bring many benefits, -including support of messages for the following special types of QSOs -and exchanged information: +A majority of new program features involve the FT8 and MSK144 +protocols. Both modes have been upgraded to use use 77-bit +information payloads rather than the 75 bits of the older FT8 protocol +or 72 bits of JT4, JT9, JT65, MSK144, and QRA64. Cyclic redundancy +checks (CRCs) that protect against false decodes have been increased +from 12 to 14 bits (FT8) and from 8 to 13 bits (MSK144). These +changes bring many benefits, including support of structured messages +optimized for the following special types of QSOs and exchanged +information: 1. NA VHF Contest operation with full and transparent support of grid locators and "/R" (Rover) callsigns @@ -26,95 +28,102 @@ and exchanged information: 4. ARRL RTTY Roundup operation with standard contest exchanges such as "579 NJ" or "559 0071" -5. Much better and more user-friendly support for compound and - nonstandard callsigns +5. Compound and nonstandard callsigns (up tp 11 characters); no need + for distinctions about "Type 1" or "Type 2" prefixes/suffixes 6. A special "telemetry" message format for exchange of arbitrary - information (up to 71 bits) + information up to 71 bits 7. All features of FT8 DXpedition mode, as in WSJT-X v1.9.1 Enhancements to the FT8 decoder ensure that in most situations -decoding sensitivity is slightly better than for the old FT8 protocol. -Sensitivity for MSK144 can be up to 0.4 dB worse. Symbol rates and -occupied bandwidths are the same as for the older protocols, and -false-decode rates are significantly lower. +decoding sensitivity is slightly better than for the old protocol. +Symbol rates and occupied bandwidths are the same as before, and +false-decode rates are significantly lower. The decoding threshold +for MSK144 is a fraction of a dB higher than before, owing to the +slightly larger message payload and higher code rate. -IMPORTANT: For the convenience of beta-testers, the first and second -"release candidates" -- releases with "-rc1" or "-rc2" in their names --- will have Rx and Tx capability for both the new FT8 protocol and -the older one. Starting with the third release candidate ("-rc3"), -and in the general-availability full release of WSJT-X 2.0, only the -new protocol will be supported. In contrast, the new MSK144 protocol -replaces the old one from the outset, without backward compatibility. -To minimize on-the-air confusion, it's important that users be aware -of these distinctions and our planned schedule for the release of -WSJT-X 2.0, as detailed below. - -OTHER PROGRAM ENHANCEMENTS: Several other new features should be -mentioned, even in this brief overview. The WSPR decoder has -significantly better sensitivity, by about 1 dB. Color highlighting -of decoded messages provides "worked before" status for callsigns, -grid locators, and DXCC entities on a "by band" basis. Color -highlighting can also identify stations that have (or have not) -uploaded their logs to "Logbook of the World" (LoTW) within the past -year. (Information from LoTW for this purpose can be downloaded from -the ARRL web site.) +OTHER PROGRAM ENHANCEMENTS: WSJT-X 2.0 has several other new features +and capabilities. The WSPR decoder has significantly better +sensitivity, by about 1 dB. Color highlighting of decoded messages +provides worked-before status for callsigns, grid locators, and DXCC +entities on a "by band" basis. Color highlighting can also identify +stations that have (or have not) uploaded their logs to "Logbook of +the World" (LoTW) within the past year. (Recent information from LoTW +for this purpose can be downloaded from the ARRL web site.) WSJT-X 2.0 introduces no significant changes to any of the modes JT4, JT9, JT65, QRA64, ISCAT, Echo, or FreqCal. -The following table shows examples of message formats supported by the -new FT8 and MSK144 protocols. Parameters i3 and n3 (shown in the -first column) are used in the software to define major and minor -77-bit message types. +IMPORTANT: For the convenience of beta-testers, the first and second +release candidates -- releases with "-rc1" or "-rc2" in their names -- +will have Rx and Tx capability for both the new FT8 protocol and the +older one. Starting with the third release candidate ("-rc3"), and in +the general-availability full release of WSJT-X 2.0, only the new +protocol will be supported. In contrast, the new MSK144 protocol +replaces the old one from the outset, without backward compatibility. +To minimize on-the-air confusion, it's important that users be aware +of these distinctions and the schedule for release of WSJT-X 2.0, as +detailed below. + +MESSAGE FORMATS: The following table shows examples of message formats +supported by the new FT8 and MSK144 protocols. Parameters i3 and n3 +(shown in the first column) are used in the software to define major +and minor 77-bit message types. ---------------------------------------------------------------------------------- i3.n3 Example Messages Comments ---------------------------------------------------------------------------------- 0.0 TNX BOB 73 GL Free text - 0.1 K1ABC RR73; W9XYZ -08 DXpedition Mode (sent only by Fox) - 0.2 G4ABC/P R 570007 JO22DB EU VHF Contest + 0.1 K1ABC RR73; W9XYZ -08 DXpedition Mode 0.2 PA9XYZ 590003 IO91NP EU VHF Contest + 0.2 G4ABC/P R 570007 JO22DB EU VHF Contest 0.3 K1ABC W9XYZ 6A WI ARRL Field Day 0.3 W9XYZ K1ABC R 2B EMA ARRL Field Day - 0.5 123456789ABCDEF012 Telemetry (up to 18 hex digits) - 1. W9XYZ Compound call - 1. W9XYZ 73 - 1. CQ FD K1ABC FN42 + 0.5 123456789ABCDEF012 Telemetry (71 bits, 18 hex digits) + 1. CQ FD K1ABC FN42 ARRL Field Day + 1. CQ RU K1ABC FN42 ARRL RTTY Roundup 1. CQ K1ABC FN42 1. CQ TEST K1ABC FN42 NA VHF Contest - 1. CQ TEST K1ABC/R FN42 + 1. CQ TEST K1ABC/R FN42 NA VHF Contest 1. K1ABC W9XYZ EN37 1. K1ABC W9XYZ -09 1. K1ABC W9XYZ R-17 1. K1ABC W9XYZ RRR 1. K1ABC W9XYZ 73 1. K1ABC W9XYZ RR73 - 1. K1ABC/R W9XYZ EN37 - 1. K1ABC W9XYZ/R RR73 + 1. K1ABC/R W9XYZ EN37 NA VHF Contest + 1. K1ABC W9XYZ/R RR73 NA VHF Contest + 1. W9XYZ Compound call + 1. W9XYZ 73 Compound call 1. W9XYZ -13 Nonstandard call - 1. W9XYZ R+02 - 1. W9XYZ RRR - 1. W9XYZ RR73 - 2. CQ G4ABC/P IO91 - 2. G4ABC/P PA9XYZ JO22 - 2. PA9XYZ G4ABC/P RR73 + 1. W9XYZ R+02 Nonstandard call + 1. W9XYZ RRR Nonstandard call + 1. W9XYZ RR73 Nonstandard call + 2. CQ G4ABC/P IO91 EU VHF contest + 2. G4ABC/P PA9XYZ JO22 EU VHF contest + 2. PA9XYZ G4ABC/P RR73 EU VHF contest 3. K1ABC KA0DEF 559 MO ARRL RTTY Roundup 3. K1ABC W9XYZ 579 WI ARRL RTTY Roundup 3. KA1ABC G3AAA 529 0013 ARRL RTTY Roundup - 3. TU; G3AAA K1ABC R 559 MA ARRL RTTY Roundup 3. TU; KA0DEF K1ABC R 569 MA ARRL RTTY Roundup + 3. TU; K1ABC G3AAA R 559 0194 ARRL RTTY Roundup 3. W9XYZ K1ABC R 589 MA ARRL RTTY Roundup 4. CQ KH1/KH7Z Compound call 4. CQ YW18FIFA Nonstandard call ---------------------------------------------------------------------------------- -Minimal QSO sequences that take advantage of the new 77-bit messages -are illustrated below. Model QSOs 1 and 2 are the same as those used -by the old FT8 and MSK144 protocols, and QSO number 3 is the same as -the existing FT8 DXpedition Mode. Model QSOs 4 through 8 were not -possible with the old protocols. +In the above list, callsigns enclosed in angle brackets (e.g., +, ) are transmitted as hash codes. They will be +displayed correctly by any receiving station that has copied the full +callsign (without brackets) in a previous transmissiion. Otherwise +the receiving software will display <...>. + +Some minimal QSO sequences that take advantage of the new 77-bit +messages are illustrated below. Model QSOs 1 and 2 are the same as +those used by the old FT8 and MSK144 protocols, and QSO number 3 is +the same as the existing FT8 DXpedition Mode. Model QSOs 4 through 9 +were not possible with the old protocols. ---------------------------------------------------------------------------------- 1. Standard QSO @@ -204,14 +213,14 @@ YW18FIFA RRR ---------------------------------------------------------------------------------- -SCHEDULE FOR PROGRAM RELEASE: Candidate releases of WSJT-X 2.0 will -have built-in expiration dates after which they cannot be used. -Target dates for planned releases are as follows: +RELEASE SCHEDULE: Candidate releases of WSJT-X 2.0 will have built-in +expiration dates after which they cannot be used. Target dates for +planned releases are as follows: -Monday, September 17: -rc1 (expires Oct 31) -Monday, October 15: -rc2 (expires Nov 30) -Monday, November 12: -rc3 (expires Dec 31) -Monday, December 10: GA full release of WSJT-X 2.0 +September 17: -rc1 (expires Oct 31) +October 15: -rc2 (expires Nov 30) +November 12: -rc3 (expires Dec 31) +December 10: GA Full release of WSJT-X 2.0 WSJT-X 2.0-rc1 provides the first chance for beta testers to use the new 77-bit messages. It supports the old (v1.9.1) FT8 protocol as @@ -219,21 +228,22 @@ well as the new message types illustrated above. To avoid QRMing legacy FT8 users with incompatible messages they can't decode, and to help concentrate testing activity into a few sub-bands, we recommend using the new FT8 capabilities on the 40- or 20-meter bands at dial -frequencies 7.078 or 14.078 MHz. These frequencies are offered as -FT8 alternatives on the drop-down frequency-selection control +frequencies 7.078 or 14.078 MHz. These frequencies are offered as FT8 +alternatives on the drop-down frequency-selection control on the main +window. The new MSK144 is fully functional for QSOs between any two stations using a WSJT-X v2.0 release. MSK144 is not backward compatible with -that in v1.9.1 or earlier program versions. Therefore during the -testing period, approximately Sept 17 through December 10, we -recommend using the new MSK144 capabilities on 50.380 MHz in IARU -Region 1 or 50.280 in Regions 2 and 3. As soon as most regular users +earlier program versions. Therefore during the testing period, +approximately Sept 17 through December 10, we recommend using the new +MSK144 capabilities on 50.380 MHz (IARU Region 1) or 50.280 (Regions 2 +and 3). By specific arrangement, or as soon as most regular users have upgraded to a v2.0 release, MSK144 activity can be moved back to 50.360 (Region 1) or 50.260 (Regions 2 and 3). By design, our proposed release schedule will make WSJT-X 2.0 usable -for all relevant ARRL operating events and Eurpoean VHF contests in -2019. +for all relevant ARRL operating events and Eurpoean VHF contests after +January 1, 2019. Dates of relevant upcoming ARRL contests ----------------------------------------