Hello Development team, while I know any QSO automation features are out of the question I would like to ask that a 'dead band beacon' be considered for some future release of WSJT-X.
My thought process sort of goes along these lines. Enable Deadband beacon option tick box, and set "enable. TX" to be on. WSJT-X send's text in TX 6, waits for 45 seconds and sends text from TX6 again but in the opposite time slot. WSJT-X then sleeps the "Enable TX" function for xx minutes (user or system set value) while keeping an eye on all incoming decodes. Should any decode occur in a specified time window from the last Transmit sequence then the next Transmit function is cancelled or delayed (selectable option?). WSJT-X again looks at any incoming decodes and if no RX decode has occurred during the last specified time window, the Beacon sequence occurs again, in the same manner as earlier. By WSJT-X checking for any incoming decodes, it should stop the dead band beacon from becoming annoying to other users. Having the ability to 'deadband beacon' on bands like 50 /144 / 432 MHz where openings can flit past in minutes would be a great plus for weak signal operators. I am in no way advocating for the 'dead band beacon' to answer other callers, I will leave that part to the carbon life forms operating the keyboards : -) Hope you will take some time to consider this during your conversations on what goes into new versions. I am happy to discuss this further should the need arise. Regards, Peter, vk5pj
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
