Windows:
\nVersion 2.0.0-rc1: wsjtx-2.0.0-rc1-win32.exe. (runs on Vista, Win 7, Win 8, Win10, both 32- and 64-bit).<\/p>\n
\nhttps:\/\/physics.princeton.edu\/pulsar\/k1jt\/wsjtx.html<\/p>\n
http:\/\/physics.princeton.edu\/pulsar\/k1jt\/Quick_Start_WSJT-X_2.0.pdf<\/p>\n
https:\/\/physics.princeton.edu\/pulsar\/k1jt\/New_Features_WSJT-X_2.0.txt<\/p>\n
New Features in WSJT-X 2.0
\nSeptember 17, 2018
\n————————–<\/p>\n
This document is an update to the white paper “Plans for WSJT-X
\nVersion 2.0″ that was publicly distributed on July 26, 2018. It
\ndescribes the most important enhancements in WSJT-X 2.0 relative to
\nversion 1.9.1.<\/p>\n
A majority of new program features involve the FT8 and MSK144
\nprotocols. Both modes have been upgraded to use use 77-bit
\ninformation payloads rather than the 75 bits of the older FT8 protocol
\nor 72 bits of JT4, JT9, JT65, MSK144, and QRA64. Cyclic redundancy
\nchecks (CRCs) that protect against false decodes have been increased
\nfrom 12 to 14 bits (FT8) and from 8 to 13 bits (MSK144). These
\nchanges bring many benefits, including support of structured messages
\noptimized for the following special types of QSOs and exchanged
\ninformation:<\/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 such as
\n“6A SNJ”<\/p>\n
4. ARRL RTTY Roundup operation with standard contest exchanges such as
\n“579 NJ” or “559 0071”<\/p>\n
5. Compound and nonstandard callsigns (up tp 11 characters); no need
\nfor distinctions about “Type 1” or “Type 2” prefixes\/suffixes<\/p>\n
6. A special “telemetry” message format for exchange of arbitrary
\ninformation up to 71 bits<\/p>\n
7. All features of FT8 DXpedition mode, as in WSJT-X v1.9.1<\/p>\n
Enhancements to the FT8 decoder ensure that in most situations
\ndecoding sensitivity is slightly better than for the old protocol.
\nSymbol rates and occupied bandwidths are the same as before, and
\nfalse-decode rates are significantly lower. The decoding threshold
\nfor MSK144 is a fraction of a dB higher than before, owing to the
\nslightly larger message payload and higher code rate.<\/p>\n
OTHER PROGRAM ENHANCEMENTS: WSJT-X 2.0 has several other new features
\nand capabilities. The WSPR decoder has significantly better
\nsensitivity, by about 1 dB. Color highlighting of decoded messages
\nprovides worked-before status for callsigns, grid locators, and DXCC
\nentities on a “by band” basis. Color highlighting can also identify
\nstations that have (or have not) uploaded their logs to “Logbook of
\nthe World” (LoTW) within the past year. (Recent information from LoTW
\nfor this purpose can be downloaded from the ARRL web site.)<\/p>\n
WSJT-X 2.0 introduces no significant changes to any of the modes JT4,
\nJT9, JT65, QRA64, ISCAT, Echo, or FreqCal.<\/p>\n
IMPORTANT: For the convenience of beta-testers, the first and second
\nrelease candidates — releases with “-rc1” or “-rc2” in their names —
\nwill have Rx and Tx capability for both the new FT8 protocol and the
\nolder one. Starting with the third release candidate (“-rc3”), and in
\nthe general-availability full release of WSJT-X 2.0, only the new
\nprotocol will be supported. In contrast, the new MSK144 protocol
\nreplaces the old one from the outset, without backward compatibility.
\nTo minimize on-the-air confusion, it’s important that users be aware
\nof these distinctions and the schedule for release of WSJT-X 2.0, as
\ndetailed below.<\/p>\n
MESSAGE FORMATS: The following table shows examples of message formats
\nsupported by the new FT8 and MSK144 protocols. Parameters i3 and n3
\n(shown in the first column) are used in the software to define major
\nand 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
\n0.2 PA9XYZ 590003 IO91NP EU VHF Contest
\n0.2 G4ABC\/P R 570007 JO22DB EU VHF Contest
\n0.3 K1ABC W9XYZ 6A WI ARRL Field Day
\n0.3 W9XYZ K1ABC R 2B EMA ARRL Field Day
\n0.5 123456789ABCDEF012 Telemetry (71 bits, 18 hex digits)
\n1. CQ FD K1ABC FN42 ARRL Field Day
\n1. CQ RU K1ABC FN42 ARRL RTTY Roundup
\n1. CQ K1ABC FN42
\n1. CQ TEST K1ABC FN42 NA VHF Contest
\n1. CQ TEST K1ABC\/R FN42 NA VHF Contest
\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 NA VHF Contest
\n1. K1ABC W9XYZ\/R RR73 NA VHF Contest
\n1. K1ABC\/R W9XYZ\/R RR73 NA VHF Contest
\n1. W9XYZ Compound call
\n1. W9XYZ 73 Compound call
\n1. W9XYZ -13 Nonstandard call
\n1. W9XYZ R+02 Nonstandard call
\n1. W9XYZ RRR Nonstandard call
\n1. W9XYZ RR73 Nonstandard call
\n2. CQ G4ABC\/P IO91 EU VHF contest
\n2. G4ABC\/P PA9XYZ JO22 EU VHF contest
\n2. PA9XYZ G4ABC\/P RR73 EU VHF contest
\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; KA0DEF K1ABC R 569 MA ARRL RTTY Roundup
\n3. TU; K1ABC G3AAA R 559 0194 ARRL RTTY Roundup
\n3. W9XYZ K1ABC R 589 MA ARRL RTTY Roundup
\n4. CQ PJ4\/K1ABC
\n4. CQ YW18FIFA Nonstandard call
\n4. YW18FIFA RR73 Nonstandard call
\n4. PJ4\/K1ABC RRR Nonstandard call
\n4. YW18FIFA Nonstandard call
\n4. YW18FIFA 73 Nonstandard call
\n4. PJ4\/K1ABC Nonstandard call
\n4. PJ4\/K1ABC 73 Nonstandard call
\n4. YW18FIFA RRR Nonstandard call
\n———————————————————————————-<\/p>\n
In the above list, callsigns enclosed in angle brackets (e.g.,
\n, ) are transmitted as hash codes. They will be
\ndisplayed correctly by receiving stations that have copied the full
\ncallsign without brackets in a previous transmissiion. Otherwise the
\nreceiving software will display . Hash collisions are possible
\nbut should be rare, and extremely rare within a particular QSO.<\/p>\n
Some minimal message sequences that take advantage of the new 77-bit
\nformats are illustrated below. Model QSOs 1 and 2 are the same as
\nthose used by the old FT8 and MSK144 protocols, and QSO number 3 is
\nthe same as the existing FT8 DXpedition Mode. Model QSOs 4 through 9
\nwere not possible with the old protocols.<\/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 “\/R” is optional
\nK1ABC\/R W9XYZ EN37 on either callsign
\nW9XYZ K1ABC\/R R FN42
\nK1ABC\/R W9XYZ RR73<\/p>\n
———————————————————————————-
\n6. ARRL RTTY Roundup
\n———————————————————————————-
\nCQ TEST K1ABC FN42
\nK1ABC W9XYZ 579 WI
\nW9XYZ K1ABC R 589 MA
\nK1ABC KA0DEF 559 MO
\nTU; KA0DEF K1ABC R 569 MA
\nKA1ABC G3AAA 529 0013
\nTU; G3AAA K1ABC R 559 MA<\/p>\n
———————————————————————————-
\n7. EU VHF Contest
\n———————————————————————————-
\nCQ TEST G4ABC\/P IO91 “\/P” is optional
\nG4ABC\/P PA9XYZ JO22 on either callsign
\nPA9XYZ 590003 IO91NP
\nG4ABC\/P R 570007 JO22DB
\nPA9XYZ G4ABC\/P RR73<\/p>\n
———————————————————————————-
\n8. Compound or nonstandard callsign calling CQ
\n———————————————————————————-
\nCQ PJ4\/K1ABC
\nPJ4\/K1ABC
\nW9XYZ -11
\n W9XYZ R-09
\n PJ4\/K1ABC RRR
\nPJ4\/K1ABC 73<\/p>\n
———————————————————————————-
\n9. Compound or nonstandard callsign answering CQ
\n———————————————————————————-
\nCQ W9XYZ EN37
\n YW18FIFA
\n W9XYZ -11
\nW9XYZ R-09
\nYW18FIFA RRR
\n YW18FIFA 73
\n———————————————————————————-<\/p>\n
\nRELEASE SCHEDULE: Candidate releases of WSJT-X 2.0 will have built-in
\nexpiration dates after which they cannot be used. Target dates for
\nplanned releases are as follows:<\/p>\n
September 17: -rc1 (expires Oct 31)
\nOctober 15: -rc2 (expires Nov 30)
\nNovember 12: -rc3 (expires Dec 31)
\nDecember 10: GA Full release of WSJT-X 2.0<\/p>\n
WSJT-X 2.0-rc1 provides the first chance for beta testers to use the
\nnew 77-bit messages. It supports the old (v1.9.1) FT8 protocol as
\nwell as the new message types illustrated above. To avoid QRMing
\nlegacy FT8 users with incompatible messages they can’t decode, and to
\nhelp concentrate testing activity into a few sub-bands, we recommend
\nusing the new FT8 capabilities on the 40- or 20-meter bands at dial
\nfrequencies 7.078 or 14.078 MHz. These frequencies are offered as FT8
\nalternatives on the drop-down frequency-selection control on the main
\nwindow.<\/p>\n
The new MSK144 is fully functional for QSOs between any two stations
\nusing a WSJT-X v2.0 release. MSK144 is not backward compatible with
\nearlier program versions. Therefore during the testing period,
\napproximately Sept 17 through December 10, we recommend using the new
\nMSK144 capabilities on 50.380 MHz (IARU Region 1) or 50.280 (Regions 2
\nand 3). By specific arrangement, or as soon as most regular users
\nhave upgraded to a v2.0 release, MSK144 activity can be moved back to
\n50.360 (Region 1) or 50.260 (Regions 2 and 3).<\/p>\n
By design, our proposed release schedule will make WSJT-X 2.0 usable
\nfor all relevant ARRL operating events and Eurpoean VHF contests after
\nJanuary 1, 2019.<\/p>\n
Dates of relevant upcoming ARRL contests
\n—————————————-
\nRTTY Roundup: January 5-6, 2019
\nVHF Sweepstakes: January 19-21, 2019<\/p>\n","protected":false},"excerpt":{"rendered":"
Windows: Version 2.0.0-rc1: wsjtx-2.0.0-rc1-win32.exe. (runs on Vista, Win 7, Win 8, Win10, both 32- and 64-bi … <\/p>\n