Greetings, Thanks to Joe for taking his valuable time to respond. I didn't realize that the Enable TX should stop after each QSO. Apparently it does in V2.0.0-rc1. However, tonight I am back running V.1.9.1. I have made 5 QSOs in a row on 160m with out having to do anything other than select TX6 CQ after each QSO--the ENABLE TX glows red all the time just fine. I am that good! I guess I broke the software! I don't see a problem, however.
"An automated QSO machine" I'm not even sure what that means I guess. The software user still has to perform functions to get things to dance. If there is a problem with user abuse of the software limiting the software/user interface isn't the solution IMHO. Another HAM in my region suggested a potential abuse of the DXpedition mode that I hadn't considered. DXpedition is on say 30m and it is after midnight local time. HAM starts calling the DX and goes off to bed. Wakes up fresh in the morning and sees DXpedition in his log. This could be a "problem". If I am sitting in the chair, interacting via the interface screen (could be tested for) then don't turn the ENABLE TX button off after each QSO. My biggest interest is using WSJT-X and my stations equipment to make contacts over circuits that are on "dead" bands, or where my antenna is a compromise, etc. Thanks to the WSJT-X team for their efforts. 73, Jim, N8OQ
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
