Plans for WSJT-X Version 2.0
\n—————————-<\/p>\n
This white paper describes a number of important enhancements planned
\nfor WSJT-X Version 2.0. Most of them involve the FT8 and MSK144
\nprotocols, which will be upgraded to use use 77-bit information
\npayloads rather than the present 72 or 75 bits. This modest increase
\nin information content will make possible new message types that
\nsupport the following special types of QSOs and exchanged information:<\/p>\n
1. NA VHF Contest operation with full and transparent support of grid
\nlocators and “\/R” (Rover) callsigns<\/p>\n
2. EU VHF Contest operation with the exchange of 6-digit locators, QSO
\nserial numbers, and “\/P” (portable) callsigns<\/p>\n
3. ARRL Field Day operation with standard Field Day exchanges<\/p>\n
4. ARRL RTTY Roundup operation with standard contest exchanges<\/p>\n
5. Better and more user-friendly support for compound and nonstandard
\ncallsigns<\/p>\n
6. A special “telemetry” message format for exchange of arbitrary
\ninformation (up to 71 bits)<\/p>\n
Decoding sensitivity for the new messages will be essentially the same
\nas for the FT8 and MSK144 modes presently in WSJT-X v1.9.1. The
\nexisting FT8 DXpedition mode will still be supported, and a more
\npowerful DXpedition mode may be offered as well.<\/p>\n
In this document we’ll call the new FT8 protocol “FT8+”. It will be a
\nsuperset of the FT8 implemented in v1.9.1, providing at least
\ntemporary compatibility and inter-operability with older program
\nversions. We may decide to remove support for old-style 72- and
\n75-bit messages after a specified switchover interval.<\/p>\n
In contrast, the new MSK144 protocol will replace the old one without
\nbackward compatibility. We believe the smaller and more specialized
\ngroup of MSK144 users will upgrade quickly and not find this
\nrestriction to be a problem.<\/p>\n
Here are some examples of message formats that will be supported by
\nFT8+ and MSK144 in WSJT-X v2.0. The list is not exhaustive.
\nParameters i3 and n3 (shown in column 1) are used in the software to
\ndefine major and minor 77-bit message types.<\/p>\n
———————————————————————————-
\ni3.n3 Example Messages Comments
\n———————————————————————————-
\n0.0 TNX BOB 73 GL Free text
\n0.1 K1ABC RR73; W9XYZ -08 DXpedition Mode (sent only by Fox)
\n0.2 G4ABC\/P R 570007 JO22DB EU VHF Contest
\n0.2 PA9XYZ 590003 IO91NP EU VHF Contest
\n0.3 K1ABC W9XYZ 6A WI ARRL Field Day
\n0.3 W9XYZ K1ABC R 2B EMA ARRL Field Day
\n0.5 123456789ABCD Telemetry (18 hex digits)
\n1. W9XYZ Compound call
\n1. W9XYZ 73
\n1. CQ FD K1ABC FN42
\n1. CQ K1ABC FN42
\n1. CQ TEST K1ABC FN42 NA VHF Contest (“TEST” is optional)
\n1. CQ TEST K1ABC\/R FN42
\n1. K1ABC W9XYZ EN37
\n1. K1ABC W9XYZ -09
\n1. K1ABC W9XYZ R-17
\n1. K1ABC W9XYZ RRR
\n1. K1ABC W9XYZ 73
\n1. K1ABC W9XYZ RR73
\n1. K1ABC\/R W9XYZ EN37
\n1. K1ABC W9XYZ\/R RR73
\n1. W9XYZ -13 Nonstandard call
\n1. W9XYZ R+02
\n1. W9XYZ RRR
\n1. W9XYZ RR73
\n2. CQ G4ABC\/P IO91
\n2. G4ABC\/P PA9XYZ JO22
\n2. PA9XYZ G4ABC\/P RR73
\n3. K1ABC KA0DEF 559 MO ARRL RTTY Roundup
\n3. K1ABC W9XYZ 579 WI ARRL RTTY Roundup
\n3. KA1ABC G3AAA 529 0013 ARRL RTTY Roundup
\n3. TU; G3AAA K1ABC R 559 MA ARRL RTTY Roundup
\n3. TU; KA0DEF K1ABC R 569 MA ARRL RTTY Roundup
\n3. W9XYZ K1ABC R 589 MA ARRL RTTY Roundup
\n4. CQ KH1\/KH7Z Compound call
\n4. CQ YW18FIFA Nonstandard call
\n———————————————————————————-<\/p>\n
\nHere are some examples of minimal QSO sequences that take advantage
\n(where necessary) of the new protocol capabilities. Model QSOs number
\n1 and 2 are supported already, with the present FT8 and MSK144
\nprotocols, and number 3 with the existing FT8 DXpedition Mode. Model
\nQSOs 4-8 (and others not illustrated here) require the new protocols
\nwith 77-bit messages.<\/p>\n
———————————————————————————-
\n1. Standard QSO
\n———————————————————————————-
\nCQ K1ABC FN42
\nK1ABC W9XYZ EN37
\nW9XYZ K1ABC -11
\nK1ABC W9XYZ R-09
\nW9XYZ K1ABC RRR
\nK1ABC W9XYZ 73<\/p>\n
———————————————————————————-
\n2. Short-cycle QSO
\n———————————————————————————-
\nCQ K1ABC FN42
\nK1ABC W9XYZ -09
\nW9XYZ K1ABC R-11
\nK1ABC W9XYZ RR73
\nW9XYZ K1ABC 73<\/p>\n
———————————————————————————-
\n3. FT8 DXpedition Mode
\n———————————————————————————-
\nCQ KH1\/KH7Z
\nKH7Z K1ABC FN42
\nK1ABC KH7Z -12
\nKH7Z K1ABC R-14
\nKH7Z W9XYZ EN37
\n… possibly other callers …
\nK1ABC RR73; W9XYZ -08<\/p>\n
———————————————————————————-
\n4. ARRL Field Day
\n———————————————————————————-
\nCQ FD K1ABC FN42
\nK1ABC W9XYZ 6A WI
\nW9XYZ K1ABC R 2B EMA
\nK1ABC W9XYZ RR73<\/p>\n
———————————————————————————-
\n5. ARRL VHF Contests
\n———————————————————————————-
\nCQ TEST K1ABC\/R FN42
\nK1ABC\/R W9XYZ EN37
\nW9XYZ K1ABC\/R R FN42
\nK1ABC\/R W9XYZ RR73<\/p>\n
———————————————————————————-
\n6. ARRL RTTY Contest
\n———————————————————————————-
\nCQ TEST K1ABC FN42
\nK1ABC W9XYZ 579 WI
\nW9XYZ K1ABC R 589 MA
\nK1ABC W9XYZ RR73<\/p>\n
———————————————————————————-
\n7. EU VHF Contest
\n———————————————————————————-
\nCQ TEST G4ABC\/P IO91
\nG4ABC\/P PA9XYZ JO22
\nPA9XYZ 590003 IO91NP
\nG4ABC\/P R 570007 JO22DB
\nPA9XYZ G4ABC\/P RR73<\/p>\n
———————————————————————————-
\n8. Compound call
\n———————————————————————————-
\nCQ PJ4\/K1ABC
\n W9XYZ
\nW9XYZ K1ABC -11
\nK1ABC W9XYZ R-09
\nW9XYZ RRR
\n W9XYZ 73
\n———————————————————————————-<\/p>\n
\nTo minimize confusion that’s likely to arise during a switchover from
\nv1.9.1 to v2.0, we propose to follow a well advertised schedule:<\/p>\n
“RC1 Date” — perhaps as early as September 15, 2018?
\n——————————————————-<\/p>\n
This will be the first chance for beta testers to try WSJT-X using the
\n77-bit messages. We may restrict this opportunity to specific
\nvolunteer testers, and we’ll probably include an “upgrade by
\nxxxx_date” message to remind people that they are using a release
\nintended only for testing.<\/p>\n
FT8+ will support the old (v1.9.1) protocol as well as the new message
\ntypes outlined above. To avoid QRMing legacy FT8 users with messages
\nthey can’t decode, we’ll recommend testing FT8+ on frequencies
\nformerly used for JT9.<\/p>\n
MSK144 will be fully functional between any two stations using the RC1
\nsoftware, but it will not be backward compatible with earlier program
\nversions.<\/p>\n
“RC2, RC3,… Date” — perhaps in October?
\n——————————————–<\/p>\n
As needed, depending on results of testing.<\/p>\n
GA Release Date — perhaps in November?
\n———————————————<\/p>\n
Official General Availability release of WSJT-X v2.0.0. The original
\nMSK144 protocol will be declared obsolete.<\/p>\n
\nFor reference: Dates of relevant upcoming ARRL contests
\n——————————————————-
\nVHF QSO Party: September 8-10, 2018
\nRTTY Roundup: January 5-6, 2019
\nVHF SS: January 19-21, 2019<\/p>\n
Our proposed schedule should make WSJT-X Version 2.0 usable for
\nrelevant ARRL operating events in 2019.<\/p>\n","protected":false},"excerpt":{"rendered":"
Plans for WSJT-X Version 2.0 —————————- This white paper … <\/p>\n