Forwarded by Bunshiro Tamura
\n———————– Original Message ———————–
\nFrom: “Joe Taylor joe@Princeton.EDU [wsjtgroup]”
\nTo: wsjtgroup@yahoogroups.com
\nDate: Tue, 24 Jul 2018 16:37:16 -0400
\nSubject: [wsjtgroup] Plans for WSJT-X Version 2.0
\n—-<\/p>\n
Hi to all,<\/p>\n
Of course we are well aware of the issues many have experienced when
\nusing WSJT modes in North American VHF contests. To summarize, there
\nare two main problem areas:<\/p>\n
– Decoding of messages with two callsigns followed by “R ” and a
\n4-character grid, and the related auto-sequencing, depend of proper
\nand coordinated setting of a checkbox at both stations.<\/p>\n
– There is a crying need for transparent support of “\/R” (Rover)
\ncallsigns in all standard messages, during contests.<\/p>\n
Here’s some background information aimed at relative newcomers and
\ncasual users of WSJT, followed by a brief preview of program features we
\nplan to make available in Version 2.0 of WSJT-X.<\/p>\n
\nContest Mode
\n————<\/p>\n
Standard JT-style messages (those used in all of the structured WSJT
\nmodes) have 71 information bits: two 28-bit callsigns and a 15-bit grid
\nlocator. The 15-bit field can alternatively convey a signal report
\n(with optional “R”), or “RRR”, “RR73”, or “73”. One additional bit
\nre-purposes the 71 bits to carry a 13-character free test message. In a
\n72-bit packet there are NO free bits available to insert “R ” before a
\ngrid locator, or “\/R” after a callsign.<\/p>\n
The “NA VHF Contest” checkbox presently in WSJT-X is a stop-gap feature
\nadded in 2016 to the MSK144 mode, and later to FT8. These modes
\nconventionally use 15-second T\/R intervals and offer semi-automated
\nmessage sequencing. NA VHF contests require the exchange of 4-character
\ngrid locators. Signal reports are OK, but not required. Contesters
\nwanted a way to send messages like “K1ABC W9XYZ R EN37”, thereby
\nincreasing their QSO rates by eliminating some transmissions from the
\nstandard minimal-QSO sequence.<\/p>\n
\nRovers
\n——
\nRovers move from grid to grid and must append “\/R” to their callsign
\nduring the contest. These hardworking folks definitely need some help
\nif they are to use WSJT modes effectively.<\/p>\n
All structured modes currently supported in WSJT-X permit messages like
\nthese:<\/p>\n
CQ K1ABC\/R FN41
\nDE K1ABC\/R 73<\/p>\n
…. but you can’t use a second callsign in place of the “CQ” or “DE”.
\nOnce again, there is no room for such information in a 72-bit packet.<\/p>\n
Some time ago we created workarounds that enable QSOs using a “\/R”
\ncallsign or an “R+grid” message fragment. But these capabilities are
\nlimited and necessarily somewhat clumsy. Users must understand what’s
\npossible and what’s not, and they must be careful about some necessary
\nprogram settings. Decoding “R+grid” messages requires ticking a
\ncheckbox, and if someone else sends you standard signal reports you need
\nto uncheck the box or manually edit your messages. Also, for reasons
\nexplained in the WSJT-X User Guide, this feature cannot work well when
\nworld-wide propagation is possible — as it has been recently on 6 meters.<\/p>\n
All in all, it’s not a happy situation — especially when considering
\nthe typical presence of many casual operators who happen upon a contest
\nand just want to make a few QSOs.<\/p>\n
\nRecently K9AN, G4WJS, and I have been developing enhanced versions of
\nthe MSK144 and FT8 protocols that extend the message payload to 77 bits.
\nFor a taste of what’s to come, here’s a brief list of things made
\npossible by the extra bits:<\/p>\n
1. NA VHF Contest operation with full support of grid exchanges and
\n“\/R” (Rover) callsigns<\/p>\n
2. EU VHF Contest operation with the exchange of 6-digit grids, 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
7. The existing FT8 DXpedition mode will be supported, and a more
\npowerful DXpedition mode may be offered as well.<\/p>\n
All of these features work seamlessly and automatically. No “contest
\nmode” checkboxes are needed. In most situations decoding sensitivity
\nwill be slightly better than at present for FT8; for MSK144 it will
\nsometimes be about 0.5 dB worse. Occupied bandwidths will be the same
\nas they are now, and false-decode rates will be significantly lower.<\/p>\n
Much of the necessary programming is finished. Many of the new features
\nhave been tested on the air, and we find them to work well.<\/p>\n
Don’t rush to download something — these capabilities are not yet
\npublicly available. There is more testing and code optimization to do.
\nWith summer vacation plans, etc., our current plans call for a
\nbeta-testing period probably starting in mid to late September. A full
\nrelease should then be possible a couple of months later.<\/p>\n
In particular: we are planning to make WSJT-X Version 2.0 available in
\ntime for you to read its new documentation and practice using it before
\n(for example) the ARRL RTTY Roundup, January 5-6, 2019, and the ARRL VHF
\nSweepstakes, January 19-21, 2019.<\/p>\n
THIS IS IMPORTANT: The new protocols cannot be backward compatible with
\nthe existing ones. We will probably provide some temporary “bi-lingual”
\ncapability for FT8, but not for MSK144. It will be essential for users
\nto upgrade to Version 2.0 in order to use the new features and
\ncommunicate with others who have made the upgrade.<\/p>\n
We will provide plenty of advance notice about a transition interval and
\nan essential “must upgrade by” date.<\/p>\n
— 73, Joe, K1JT<\/p>\n
——————— Original Message Ends ——————–<\/p>\n","protected":false},"excerpt":{"rendered":"
Forwarded by Bunshiro Tamura ———————– Original Message — … <\/p>\n