I have received several emails from people having their log rejected by the robot. It seems they were not submitting the log via the ARRL web page for log submissions: https://contest-log-submission.
The ARRL RTTY Roundup Rule 7.4 is explicit about using WSJT-X is mandatory and puts you in Single Operator Unlimited, or Multi-Op. JT Alert is irrelevant. 73,Ed W0YK -- Original message --From: Jef
For another perspective, read the P49X 3830 soapbox for ARRL RTTY Roundup. Ed W0YK _________________________________________________________________ Anything you can't hear with your human ears isn'
The Raw Scores page has been updated for last weekends contest. Raw Scores are scores generated by the log checking software before any reductions for errors and omissions. The order of finish usuall
Plan on joining the NA RTTY Sprint this Saturday, NA time (0000-0400 UTC, Sunday, 10 March). This 4-hour mini-contest is a lot of fun and builds operating skill as well. If you're new to the Sprint f
We are testing the log submittal and log checking process for the upcoming WW Digi DX Contest at the end of August. We need logs to test with. At the end of May 2019, I worked over 600 QSOs on FT8 an
Hi Ken. Good question and there are many more about the new WW Digi contest. The website (ww-digi.com <http://www.ww-digi.com> ) is an evolving source of answers. The best email list for discussion o
Hi Ed. The RTTYdigital@groups.io email list is probably a better place for discussion of RTTY and other digital mode-specific topics. For more information on the WW Digi contest, ww-digi.com is an ex
Both W9ET and N9UDO contributed to this "less than ideal" QSO sequence. W9ET didn't follow the default message sequence which required N9UDO to take abnormal action. N9UDO failed to take that abnorma
W9ET's 73 message was a QSL that he received N9UDO's report. It would have been clearer had the default message of "RR73" been sent, but nonetheless, W9ET's message was more than a "courtesy" because
Yes, "73" is not explicitly required. However, that's only part of the issue here. Long-time QSO convention is that both sides QSL (confirm) the contact, specifically that they received the required
WSJT-X pre-loads the following default messages for the NA VHF Contest mode, which is the recommended WSJT-X mode for the 2019 WW Digi contest: Tx 1: W9ET N9UDO EN53 Tx 2: W9ET N9UDO EN53 Tx 3: W9ET
To repeat a third time, sending '73' is not being advocated. Rather confirmation of receipt of the exchange is being recommended. Confirmation can be done any number of ways, including 'TU', 'R', '73
Here's some data from to illustrate and expand on the "key point": 2018 WW RTTY 2018 FT8 Roundup Dupes: 0.7% 3.0% Busted Exchange: 0.7 1.0 Busted Call: 1.0 0.0 NIL: 1.8 5.1 Total Error Rate: 3.5 6.1
To clarify, the TU in 4. is only superfluous because the confirmation (of receipt of report) is implied by the fact that W1AW probably wouldn't be sending his report if he hadn't received NC6K's repo
Good to hear the interest in practicing for WW Digi. It's been the plan since the press release in late June. Meanwhile, the various software developers have been adding their support for the contest
Two one-hour practices each week leading up to the contest (8 total practice sessions): Fridays (9, 16, 23, 30 August) 19-20 UTC (EU evening) Saturdays (10, 17, 34, 31 August) 01-02 UTC (NA Friday ev
This is an example of the DXpedition "Fox and Hound" mode where the DXpedition station is the Fox and transmits 2-5 distinct audio frequencies within his TX passband using a single suppressed carrier
Thanks to everyone that submitted a practice log and let us know what didn't work. Here is a summary: ADIF Converter 1. Not accepting the official ADIF standard for the FT4 mode: <MODE:4>MFSK <SUBMOD
Two one-hour practices again this Friday: Friday 16 August 19-20 UTC (EU evening) Friday 16 August) 23-00 UTC (NA evening) [NOTE THIS 2nd SESSION IS 2 HOURS EARLIER THAN THE ORIGINAL SCHEDULE DUE TO