[WT-support] Win-Test and contest numbers, proposal
Tõnno Vähk
tonno.vahk at gafm.ee
Tue May 29 13:25:24 CEST 2012
I see a very interesting and needed discussion here. We just completed
another MS operation in WPX which now has one numbering sequence only and
running with 5 stations you need all them to coordinate numbers. It is a
mess as often the number is stolen from the RUN station or another station
after it has given it out but before he has pressed Enter and then the
wrong sent number gets into the log. We do use $NEXTSERIAL, etc... But a
lot of human mistakes happen. And unfortunately it is the innocent caller
who gets punished as he will lose the QSO because “wrongly copied“ exchange.
I have seen the opinion of WT guys and solutions proposed and arguments
presented to protect the current system. Well, obviously a critical mass of
people have huge problems with this thing and we would need at least some
optional solution. It is clear that none of the contest organizers require
perfect line of numbers and what is important is that the numbers match in
logs. So preserving a clean sequence is not an argument.
Reserving the number somehow when it is sent does not quite work as in SSB
it won’t work and even in CW some guys send with paddle, etc.. Bob’s idea
abut the program checking what was sent and logging it is interesting but
again not universal.
It seems to me that the best option is to have a following tickable option
in WT:
ONLY INCREMENT SERIAL NUMBER WHEN CALLSIGN FIELD IS EMPTY
That’s it. Let the station who has something on the callsign field keep the
number. This way it can never happen that you log a different number from
what is sent! If the QSO does not happen and you clear the callsign field
the number gets immidiately synchronized again! Can someone point out when
this solution would not work?
If only it would not require rewriting the whole code of the program! Does
it??
73
Es5tv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20120529/a0996596/attachment.html>
More information about the Support
mailing list