Bill et. al.,
I have identified another problem with autoseqencing with compound
calls, that can generate and log invalid QSOs.
It seems that when someone responds to my CQ with TX2, the resulting
standard TX3 response from me enables someone else to hijack the QSO.
Here is an example of the problem, cut and pasted from the RX freq window:
130430 -3 0.3 1417 ~ W7RI K0GK -15 (K0GK responds to my CQ)
130430 7 -0.5 1518 ~ W7RI N3OUC FN20 (Call 1st is on, so this call is
ignored. It's supposed to. So far, so good.)
130445 Tx 1415 ~ DE TI3/W7RI R-03 (I respond to K0GK with TX3)
130500 6 -0.5 1518 ~ W7RI N3OUC R-08 (N3UOC continues to call, even
though I am in QSO with someone else. He is ignored. Great! So far, so
good.)
130515 Tx 1415 ~ DE TI3/W7RI R-03 (K0GK has failed to respond, so
I resend TX3)
130545 Tx 1415 ~ DE TI3/W7RI R-03 (K0GK has failed to respond, so
I resend TX3)
130615 Tx 1415 ~ DE TI3/W7RI R-03 (K0GK has failed to respond, so
I resend TX3)
130630 -4 0.7 1416 ~ W7RI JA2XYO RRR (Because, for compound call
users, TX3 does not send the call of the station I am working, JA2YXO
responds, thinking mistakenly that I am in QSO with HIM rather than K0GK)
130645 Tx 1415 ~ DE TI3/W7RI 73 (Hearing the RRR sequence from
JA2YXO, my software responds with the Log QSO dialog box, but populated
with JA2YXO's callsign, and K0GK's signal report - an invalid QSO.)
This problem happens with enough frequency to be something of an issue,
particularly when I am working a large pileup as I was this morning,
which is a good deal of the time.
Whenever someone responds with TX2 and I send TX3, there's enough people
out there attempting to call me that this will happen with some
frequency - maybe once in 15 or 20 QSOs. Configuration does not allow
me to work around this by changing the TX3 standard message without
forcing me to change others I don't want to change.
Maybe the software should test to see if the callsign was changed since
the last signal report has been received before sequencing to TX5 and
bringing up the dialog box, and not advance the sequence or allow
logging if it has.
Regards and 73,
Scott Bidstrup
TI3/W7RI
------------------------------------------------------------------------------
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
