On 21/07/2017 06:41, Mark Turner via wsjt-devel wrote:
Hi Bill,
could it be implemented it such that, if set, "Skip Tx 1" is simply
ignored if the dx call is a compound callsign?
In fact the whole Tx1/RR73 thing might be boiled down to a more
generic option, like "minimal", or "optimise", or similar - i.e.
attempt to use the least number of exchanges to achieve a valid qso,
that would automatically take things like compound callsigns into
account. Sounds very tweaky though...
Regards, Mark
Hi Mark,
you may have missed the significance of my comments about compound call
holders. There are circumstances where compound call holders cannot send
their fully qualified callsign, this constraint is due the the nature of
the information compression used in the mode's protocols. What I don't
want to do is formalize an exchange procedure that excludes them from a
QSO because there is no obvious way for them to send their full
callsign. I think skipping Tx1/grid replies is ok and I think using RR73
to finish a QSO is ok but I need to work through the possible scenarios
to check. There are many combinations of which a split frequency
JT65/JT9/FT8 QSO on a busy sub-band is probably the most complex.
You suggest that an option can be ignored in the case of the DX call
being compound but sometimes you do not know the DX call is compound
until later in the QSO exchange. It may seem trivial and unnecessary
most of the time but when that rare prefix we all need gets activated
with a compound callsign the complaints will be loud if they cannot use
WSJT-X fro normal QSOs even if they have a callsign that the software
accepts as valid.
73
Bill
G4WJS.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
