As a Rover in the June VHF Contest this weekend, I had nothing but problems
with FT8, and it cost me andothers many QSOs, especially when I operated from a
semi-rare grid. And I was not alone. K5ND has thiswrite up on his blog.
Scroll down to WSJT Burn Up
https://www.k5nd.net/2018/06/k5nd-r-in-arrl-june-2018-vhf-contest/
OK, as the ARRL contest rules require, I entered my call as N6GP/R into the
WSJT-X setup. I now know that this is a
Type 2 compound callsign. I am not sure what the consequences are of being a
Type 2 in NA Contest mode. Is this notsupported?
The main problem was that, as K5ND noted, the TX3 message was always coming
back to people who called me, like "DE N6GP/R R DM23". Nobody knew that I was
working them, because I wasn't sending their callsign. Additionally,there was
a problem that I could not double click on a callsign. I had to manually type
it into the callsign box.
After suffering through this from 2 grids, I experimented with turning NA VHF
Contest mode off, and that did not cure the problem, and it just made ops mad
at me. So, finally I had to strip the /R from my callsign, and things worked
reasonablly well for the rest of the contest. I then wrote a waiver letter to
the ARRL for myself and all the other rovers, and they are taking it into
consideration.
So, I think I don't understand this problem completely. Is /R not supported,
and we need to ask the ARRL for a rule change? Or, are there bugs in the WSJT
mode?
I will address the general problems with NA Contest mode in another post.
Thanks & 73,
Tim N6GP/R
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
