As I read Rich's message in digest format, a response may already be given, so my apologies if I repeat a previous reply.
It seems like the check box under Settings - General - "Disable Tx after sending 73" repeatedly creates some confusion. The mouse-over help text describes exactly what checking this box does: "Turns off automatic transmission after sending 73 or any other free text message". Nothing more is implied, and specifically this does *not* mean that *un*checking (the default state) it *en*ables automatic transmissions after sending 73. The opposite, or the antithethical interpretation if you like, just does not apply, nor does the mouse-over help text indicate that it applies. Specifically, unchecking this box is no workaround to automatically create a red "Enable TX" button again after sending 73. That would possibly create an FT8 QSO robot enabling operations with no operator in attendance/control, which is illegal in many (most/almost all?) countries. WSJT-X includes considerably more demanding modes than FT8, e.g. meteor modes, where repeating the message after sending 73 may be required to complete a QSO and is normal until a return 73 has been received. However, sometimes the conditions are good even for these modes, and then it may be desirable to not transmit again after sending 73. That is a case when you check the box "Disable Tx after sending 73". For FT8 the general disabling of "Enable TX" after sending your 73 is desired actions and cannot overridden in standard WSJT-X, which has not prevented operators from creating robots. Having not worked as a Fox, I am not in a position to jugde whether clicking the "Enable TX" button is a sufficient PITA to enable DXpedition QSO robots. However, even for expeditions to very rare DXCC entities (for which FT8 DXpedition mode is created), the requirement for a control operator applies. Unattended FT8 QSO robots are no more legal in exotic places than other places. I understand the clicking inconvenience, but as far as I understand, all other modes used by DXpeditions require the operator to key the transmitter for *each* exchange in a QSO, either by stepping on a foot switch or a mike PTT button or by pressing a function key on a keyboard, so I don't know if clicking the "Enable TX" button once per QSO is widely different or too much to ask for FT8 Fox operations. man. 18. nov. 2019 kl. 01:03 skrev Rich Zwirko - K1HTV <[email protected]>: > Grant, > By any chance could the problem described have been caused because under > Settings, General tab you had the "Disable Tx after sending 73' check box > checked? I don't know if this might be bypassed in the Fox mode. If not, it > should be disabled automatically when the Fox mode is used. > > 73, > Rich - K1HTV > > = = = > > VK5GR wrote: > > 2. Secondly, and this was a MOST frustrating aspect of using the > software. No matter what we did we couldn’t seem to find any settings that > would stop the “Enable TX” button from being cancelled *every time* the > FOX sent RR73 on any channel. Now it appears as though this is by design > although I hope it is in fact a bug. Our view is that if the FOX operator > had made the deliberate effort to load a station into the calling queue > then *the enable TX button should remain active until the last station > leaves the calling queue.* > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
