On 01/01/2017 22:08, Jay Hainline wrote:
I don’t know for certain why this was changed in the first place except the JT65 HF crowd is always looking for a way to sidestep a sequence to shorten the time for a QSO. This does not work in the meteor scatter VHF world where you are relying on random data bits to fly in on a meteor for less than 1 second and you are trying to decode just what the guy on the other end has received. If it aint broke, don’t fix it.
Hi Jay,Joe changed this reluctantly under incessant pressure from HF JT65 and JT9 users who, in general, are not working "weak signals" and therefore see no need to ever repeat any message apart from CQ. This already leads to incomplete QSOs where a message is not received or an out of sequence message is sent (e.g. R+<snr> before a QSO partner has sent any report at all). It is particularly frustrating when stations in a hurry ignore requests for a repeat message because they assume everything they send has been received.
It is not only MS operators that will have problems with this change, EME operators and tropo or rain scatter ops who may spend many, many minutes trying to complete with a weak or variable signal at or near the decoding threshold.
Just my 2 pence, I think there is always time to send a 73 message after a RRR message and it allows other stations to tail end in which case no time is actually wasted anyway when signals are strong enough for first time decodes. Operators running a frequency have always had the option to click "Log QSO" at any time including after sending an RRR message if they wish.
The auto log pop up and disable auto Tx makes most sense to me as that happens first for the calling station who should be stopping and looking elsewhere for another QSO. The running station is, well, running and will almost always continue transmitting on the frequency so Log->pick next message->wait for reply seems right to me.
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
