VHFcontesting
[Top] [All Lists]

Re: [VHFcontesting] FT8 contest mode incompatibly

To: "'vhfcontesting@contesting.com'" <VHFcontesting@contesting.com>
Subject: Re: [VHFcontesting] FT8 contest mode incompatibly
From: "Lloyd - N9LB" <lloydberg@charter.net>
Date: Mon, 22 Jul 2019 11:14:05 -0500
List-post: <mailto:vhfcontesting@contesting.com>
I experienced this all weekend too - about 50% of attempted contacts.
I also observed this after the contest when people were still calling "CQ
Test" to indicate that a quick QSO, w/o the funny numbers, was being
solicited.  
This also happens to stations operating as "Grid Expeditions" who are
experiencing pile-ups and therefore operate in "Contest" mode and need a
quicker QSO turn-around time.

Yes, I like the idea of an additional button to allow completion of the QSO
between normal and contest modes.

Lloyd - N9LB

-----Original Message-----
From: VHFcontesting [mailto:vhfcontesting-bounces@contesting.com] On Behalf
Of Jay RM
Sent: Monday, July 22, 2019 10:36 AM
To: nmvhf@groups.io; vhfcontesting@contesting.com
Subject: [VHFcontesting] FT8 contest mode incompatibly

Anyone seriously operating this weekends contest and using FT8 probably had
this happen.

You're cruising .313 looking for those new mults or whatever, you see
someone CQing WITHOUT the word TEST in the CQ message and you instinctively
know they're not in contest mode.  No worries, you think.  The WSJTX boffins
have tuned the program to compensate for the difference in exchange and you
know autosequence will seamlessly pull you through.  You call and, sure
enough, back comes the 'funny little number' exchange.  You reply with a NA
contest mode exchange (because you're contesting, right ?) and....
back comes a repeat - no autosequence.  What ??  OK, maybe I got QRMed.
Try again, and same thing.  You can't progress to the finish.

What you do now is left to the individual.  What I did was terminate the Q
and moved on.  You might have fiddled with the setup to switch out of
contest mode.  Whatever... the Q was either made or not.

What this did, other then temporarily piss me off and cause name calling
that nobody heard but me and the shack spiders, was confused me.  HOW could
this happen....the boffins....they fixed this.  Was the other guy manually
interfering with autosequence ?  Was the other guy that insistent on his
funny number ?  I started ignoring those obviously not in contest mode.

This morning, after reading a soapbox comment on 3830, it finally hit me....
(I'm pretty focused on operating during the 'test).  It's.....The Clones !!
Those knock-offs of WSJT - JTDX, MHSV !  THEY don't have contest
mode !   They can't autosequence past TX2.  So, what to do about this
incompatibly ?  It's pretty obvious the clones aren't going to add CM if
they haven't already and there are those contest haters that wouldn't use it
anyway, but still insist on trying to WORK contesters.

I'm thinking maybe the solution is to add some kind of 'quick button'
behavior to WSJTX that drops the program out of contest mode for just one Q
and resets back into CM after the 73 (or something).  Does anyone have
another idea ?  If a number of high level contesters presented such a
request maybe the WSJT powers would respond.  Or, maybe you think it's a
non-issue....or maybe a quick work around all ready exists that doesn't
require a guy to drop in and change his setup and I'm just clueless ?

-W9RM



Keith Morehouse
via MotoG
_______________________________________________
VHFcontesting mailing list
VHFcontesting@contesting.com
http://lists.contesting.com/mailman/listinfo/vhfcontesting

_______________________________________________
VHFcontesting mailing list
VHFcontesting@contesting.com
http://lists.contesting.com/mailman/listinfo/vhfcontesting

<Prev in Thread] Current Thread [Next in Thread>