月: 2018年7月

Plans for WSJT-X Version 2.0
—————————-

This white paper describes a number of important enhancements planned
for WSJT-X Version 2.0. Most of them involve the FT8 and MSK144
protocols, which will be upgraded to use use 77-bit information
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 and transparent support of grid
locators and “/R” (Rover) callsigns

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

4. ARRL RTTY Roundup operation with standard contest exchanges

5. Better and more user-friendly support for compound and nonstandard
callsigns

6. A special “telemetry” message format for exchange of arbitrary
information (up to 71 bits)

Decoding sensitivity for the new messages will be essentially the same
as for the FT8 and MSK144 modes presently in WSJT-X v1.9.1. The
existing FT8 DXpedition mode will still be supported, and a more
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 support for old-style 72- and
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
FT8+ and MSK144 in WSJT-X v2.0. The list is not exhaustive.
Parameters i3 and n3 (shown in column 1) 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.2 PA9XYZ 590003 IO91NP EU VHF Contest
0.3 K1ABC W9XYZ 6A WI ARRL Field Day
0.3 W9XYZ K1ABC R 2B EMA ARRL Field Day
0.5 123456789ABCD Telemetry (18 hex digits)
1. W9XYZ Compound call
1. W9XYZ 73
1. CQ FD K1ABC FN42
1. CQ K1ABC FN42
1. CQ TEST K1ABC FN42 NA VHF Contest (“TEST” is optional)
1. CQ TEST K1ABC/R FN42
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. 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
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. W9XYZ K1ABC R 589 MA ARRL RTTY Roundup
4. CQ KH1/KH7Z Compound call
4. CQ YW18FIFA Nonstandard call
———————————————————————————-

Here are some examples of minimal QSO sequences that take advantage
(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
———————————————————————————-
CQ K1ABC FN42
K1ABC W9XYZ EN37
W9XYZ K1ABC -11
K1ABC W9XYZ R-09
W9XYZ K1ABC RRR
K1ABC W9XYZ 73

———————————————————————————-
2. Short-cycle QSO
———————————————————————————-
CQ K1ABC FN42
K1ABC W9XYZ -09
W9XYZ K1ABC R-11
K1ABC W9XYZ RR73
W9XYZ K1ABC 73

———————————————————————————-
3. FT8 DXpedition Mode
———————————————————————————-
CQ KH1/KH7Z
KH7Z K1ABC FN42
K1ABC KH7Z -12
KH7Z K1ABC R-14
KH7Z W9XYZ EN37
… possibly other callers …
K1ABC RR73; W9XYZ -08

———————————————————————————-
4. ARRL Field Day
———————————————————————————-
CQ FD K1ABC FN42
K1ABC W9XYZ 6A WI
W9XYZ K1ABC R 2B EMA
K1ABC W9XYZ RR73

———————————————————————————-
5. ARRL VHF Contests
———————————————————————————-
CQ TEST K1ABC/R FN42
K1ABC/R W9XYZ EN37
W9XYZ K1ABC/R R FN42
K1ABC/R W9XYZ RR73

———————————————————————————-
6. ARRL RTTY Contest
———————————————————————————-
CQ TEST K1ABC FN42
K1ABC W9XYZ 579 WI
W9XYZ K1ABC R 589 MA
K1ABC W9XYZ RR73

———————————————————————————-
7. EU VHF Contest
———————————————————————————-
CQ TEST G4ABC/P IO91
G4ABC/P PA9XYZ JO22
PA9XYZ 590003 IO91NP
G4ABC/P R 570007 JO22DB
PA9XYZ G4ABC/P RR73

———————————————————————————-
8. Compound call
———————————————————————————-
CQ PJ4/K1ABC
W9XYZ
W9XYZ K1ABC -11
K1ABC W9XYZ R-09
W9XYZ RRR
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.

Forwarded by Bunshiro Tamura
———————– Original Message ———————–
From: “Joe Taylor joe@Princeton.EDU [wsjtgroup]”
To: wsjtgroup@yahoogroups.com
Date: Tue, 24 Jul 2018 16:37:16 -0400
Subject: [wsjtgroup] Plans for WSJT-X Version 2.0
—-

Hi to all,

Of course we are well aware of the issues many have experienced when
using WSJT modes in North American VHF contests. To summarize, there
are two main problem areas:

– Decoding of messages with two callsigns followed by “R ” and a
4-character grid, and the related auto-sequencing, depend of proper
and coordinated setting of a checkbox at both stations.

– There is a crying need for transparent support of “/R” (Rover)
callsigns in all standard messages, during contests.

Here’s some background information aimed at relative newcomers and
casual users of WSJT, followed by a brief preview of program features we
plan to make available in Version 2.0 of WSJT-X.

Contest Mode
————

Standard JT-style messages (those used in all of the structured WSJT
modes) have 71 information bits: two 28-bit callsigns and a 15-bit grid
locator. The 15-bit field can alternatively convey a signal report
(with optional “R”), or “RRR”, “RR73”, or “73”. One additional bit
re-purposes the 71 bits to carry a 13-character free test message. In a
72-bit packet there are NO free bits available to insert “R ” before a
grid locator, or “/R” after a callsign.

The “NA VHF Contest” checkbox presently in WSJT-X is a stop-gap feature
added in 2016 to the MSK144 mode, and later to FT8. These modes
conventionally use 15-second T/R intervals and offer semi-automated
message sequencing. NA VHF contests require the exchange of 4-character
grid locators. Signal reports are OK, but not required. Contesters
wanted a way to send messages like “K1ABC W9XYZ R EN37”, thereby
increasing their QSO rates by eliminating some transmissions from the
standard minimal-QSO sequence.

Rovers
——
Rovers move from grid to grid and must append “/R” to their callsign
during the contest. These hardworking folks definitely need some help
if they are to use WSJT modes effectively.

All structured modes currently supported in WSJT-X permit messages like
these:

CQ K1ABC/R FN41
DE K1ABC/R 73

…. but you can’t use a second callsign in place of the “CQ” or “DE”.
Once again, there is no room for such information in a 72-bit packet.

Some time ago we created workarounds that enable QSOs using a “/R”
callsign or an “R+grid” message fragment. But these capabilities are
limited and necessarily somewhat clumsy. Users must understand what’s
possible and what’s not, and they must be careful about some necessary
program settings. Decoding “R+grid” messages requires ticking a
checkbox, and if someone else sends you standard signal reports you need
to uncheck the box or manually edit your messages. Also, for reasons
explained in the WSJT-X User Guide, this feature cannot work well when
world-wide propagation is possible — as it has been recently on 6 meters.

All in all, it’s not a happy situation — especially when considering
the typical presence of many casual operators who happen upon a contest
and just want to make a few QSOs.

Recently K9AN, G4WJS, and I have been developing enhanced versions of
the MSK144 and FT8 protocols that extend the message payload to 77 bits.
For a taste of what’s to come, here’s a brief list of things made
possible by the extra bits:

1. NA VHF Contest operation with full support of grid exchanges and
“/R” (Rover) callsigns

2. EU VHF Contest operation with the exchange of 6-digit grids, QSO
serial numbers, and “/P” (portable) callsigns

3. ARRL Field Day operation with standard Field Day exchanges

4. ARRL RTTY Roundup operation with standard contest exchanges

5. Better and more user-friendly support for compound and nonstandard
callsigns

6. A special “telemetry” message format for exchange of arbitrary
information up to 71 bits

7. The existing FT8 DXpedition mode will be supported, and a more
powerful DXpedition mode may be offered as well.

All of these features work seamlessly and automatically. No “contest
mode” checkboxes are needed. In most situations decoding sensitivity
will be slightly better than at present for FT8; for MSK144 it will
sometimes be about 0.5 dB worse. Occupied bandwidths will be the same
as they are now, and false-decode rates will be significantly lower.

Much of the necessary programming is finished. Many of the new features
have been tested on the air, and we find them to work well.

Don’t rush to download something — these capabilities are not yet
publicly available. There is more testing and code optimization to do.
With summer vacation plans, etc., our current plans call for a
beta-testing period probably starting in mid to late September. A full
release should then be possible a couple of months later.

In particular: we are planning to make WSJT-X Version 2.0 available in
time for you to read its new documentation and practice using it before
(for example) the ARRL RTTY Roundup, January 5-6, 2019, and the ARRL VHF
Sweepstakes, January 19-21, 2019.

THIS IS IMPORTANT: The new protocols cannot be backward compatible with
the existing ones. We will probably provide some temporary “bi-lingual”
capability for FT8, but not for MSK144. It will be essential for users
to upgrade to Version 2.0 in order to use the new features and
communicate with others who have made the upgrade.

We will provide plenty of advance notice about a transition interval and
an essential “must upgrade by” date.

— 73, Joe, K1JT

——————— Original Message Ends ——————–

　西日本各地での豪雨で被害に見舞われた地域の皆様、心よりお見舞い申し上げます。

　僕の家の前も国道を挟んで千丈川が流れていまして生きた心地がしない数時間ではありましたが、おかげさまで何も被害もなく嵐は通り過ぎました。

　本来ならば後片付けを手伝いに行きたいし行かなければならないのですが失礼をせざるをえませんのでよろしくお願いします。

　熱中症に気をつけて頑張って後片付けしてください。

　本当に、心よりお見舞い申し上げます。

　田村文史郎／ＪＡ５ＦＮＸ／Ｂｕｎ