Hi Dave,
On 12/3/2018 19:25, Dave Hachadorian K6LL wrote:
There were major issues with RST not getting filled in, both sent and
received. I’ve got about 200 dupes in my Cabrillo because one line has
no RST, and the next line has the RST typed in manually. It was a major
pain during the contest. While filling in the data manually,
Transmitting is disabled, so it further slows down the RATE.
Also, when you get a repeat of the exchange, as frequently happens, the
RST can change, so there may be a discrepancy between two logs,
depending on which version of the RST was logged. If I were the
software programmer, I would make everybody 599 in contest mode, just as
God intended.
It is interesting that it was only the sent/received RST that acted this
way. States/provinces and serial numbers were solid.
Dave Hachadorian, K6LL
Yuma, AZ
I have 638 QSOs in my log and only 14 dues. I think all of these (or
maybe all but one?) were "legitimate" dupes, by which I mean the same
guy called me again, on the same band. I had only a handful of
semi-broken QSOs that required intervention to fill in a part of the
exchange. In no case was RST missing from information send to N1MM+.
If we are to help you diagnose what created your problem, we'll need
more information about how you operated. Could your SO2R operating
technique have contributed that many Op errors?
Be aware: As clearly stated in the "Quick-Start Guide to WSJT-X 2.0",
existing features for contesting are no more than a starting point.
So far we have given zero thought to conveniences for SO2R operating.
As usual, any and all suggestions for improvement are welcome.
-- 73, Joe, K1JT
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
