There are two functionalities being used for operation: autoselection while DX Call window is empty and autosequencing if there is any callsign in the DX Call window. Autosequencing will not be transmitting CQ if there is a callsign in DX Call window.
Autosequencing functionality in JTDX is based on QSO history data structure where all decoded CQ messages and messages containing user's callsign being recorded. QSO history data structure will be cleaned up if band is changed, specific callsign can be cleaned up from the history using click of the right mouse's button on the Clear DX button.
Also previous attempts to make QSO to specific callsign will be cleaned up from the history at 'hisCall myCall myGrid' message transmission to this callsign.
Autoselection functionality is based on JTDX notifications, using criteria and priorities selected by user in Notifications tab of the settings.
Autoselection will ignore any 'worked B4' call if there is any 'new one' criterion is selected in Notifications tab of the settings. 'Worked B4' is being recognized by Notifications functionality on residual principle after checking to all selected 'new one' criteria using wsjtx_log.adi file.
Autoselection will be considering every decoded callsign as ‘new one’ if there is not any 'new one' criterion selected in the Notifications tab of settings.
Autoselection will be choosing signal with the best SNR while getting two or more incoming calls with equal priority or if there is not any 'new one' criterion is selected in the Notifications tab.
JTDX providing several autoselection modes where user can choose the best one according to the processing power of the CPU and user's needs.
Autoselection functionality has two parts: searching for incoming calls(AutoSeq1,2,3) and searching through received CQ messages(AutoSeq4+).
AutoSeq1 'Call First'.
In this mode software will respond to the first incoming answer to your CQ. AutoSeq1 will change message being transmitted if first answer to CQ or message at QSO is decoded after beginning of TX interval. AutoSeq1 works in similar way to AutoSeq WSJT-X.
AutoSeq2 'Call decoded till start of TX interval'.
In this mode software will be searching for any incoming call till start of TX interval, then will answer to the best one in terms of priority and/or SNR.
All incoming calls or received messages at QSO, decoded during message transmission will be ignored.
AutoSeq3 'Call based on end of decoding'.
Fast CPU needed to operate in AutoSeq3 if there is wide bandwidth being used for decoding.
Software will be waiting till end of decoding then will answer to the best incoming call in terms of priority and/or SNR.
In this mode software can start transmission with previously transmitted message and may change message during transmission.
If AutoSeq3 is being used on slow CPU, a change of TX message beyond 2nd..3rd second of TX interval will decrease chances of getting this message decoded.
AutoSeq4+ 'Search through received CQ messages'.
This mode can only be used together with mode 2 (AutoSeq4+2) or mode 3 (AutoSeq4+3).
If there is no answer came to user’s CQ message, software will search through all decoded CQ messages to select the best one in terms of priority and/or SNR and will answer to selected CQ message.
Received directional CQ messages being processed acording to the direction, incoming calls being processed according to direction of user’s transmitted directional CQ message.
For instance, AutoSeq6,7 will not respond to received ‘CQ NA’ message if user is located in Europe, and any AutoSeq mode will not answer to incoming call from Europe if it is coming in response to ‘CQ NA’ message transmitted by user.
This option providing very efficient operation in terms of the QSO ratio.
In scenario where user answered to someone's CQ, when QSO is finished JTDX will transmit CQ message if TX signal is not being overlapped with the last QSO party operator's signal. To avoid CQ message transmission after the QSO user can activate 'Single shot QSO' option.
When user’s signal is being overlapped with QSO party operator’s signal and if AutoSeq making decision that user is not owner of the frequency then QSO party operator’s callsign is being not cleaned up from DX Call window. That is the way CQ message transmisson is being avoided on the QSO party operator’s frequency after QSO is finished.
Sometimes it is not possible to recognize who is owner of the frequency, for this reason we recommend to use TX/RX Split mode with AutoSeq, where user’s signal is being not overlapped with QSO party’s signal, at split operation user can prevent unintended transmission of CQ message on the QSO party’s frequency after QSO is finished.
JTDX AutoSeq operation depends on the logging mode:
To prevent fully automatic(unattended) JTDX operation autosequencing+autoselection cycle shall be interrupted if there is no operator's action is performed.
- In autologging mode (Enable automatic logging of QSO) software switches off Enable Tx button when QSO is finished and action from user is required to switch Enable TX button back on to continue operation.
- In 'Prompt me to log QSO' or manual logging software will brake cycle (will switch Enable TX button off) if QSO is not logged before end of QSO (73 message is decoded). Hence software will not let to the setup operate while being unattended. Software will continue cycle of operation if user accepted QSO prior to decoding of the final 73 message.
If QSO is logged before getting ending QSO '73' message, upon decoding this message:
JTDX in AutoSeq1 mode will answer to the first valid incoming call or will continue to call CQ if there is no valid incoming calls received.
JTDX in AutoSeq2 and AutoSeq3 modes will search for any new best incoming call and will answer it. It will continue to call CQ if there is no any valid incoming call received.
JTDX in AutoSeq(4+2) and AutoSeq(4+3) modes will search for any new best incoming call and will answer it. It will find and answer to the best CQ message if there is no any valid incoming call received. It will continue to call CQ if there is no valid incoming call and no any valid CQ message received.
Directional CQ RX/TX messages.
Directional CQ message transmission and AutoSeq1,2,3:
Autoselect recognizes incoming calls according to the transmitted direction in the user’s message: CQ DX, CQ + continent, CQ + (two character prefix) directions are being supported, where continent is [SA NA EU AS OC AN AF].
Software will answer those incoming calls that matching to the transmitted direction, and will not answer other calls with exception to the new DXCC country.
If user called (CQ + common country prefix), where country prefix being taken from cty.dat file, software will answer to the best incoming call from this country and will ignore other incoming calls.
If user called (CQ + not common country prefix) software will answer to exactly matching prefix.
For instance, if user called CQ JH, autoselection will answer to any callsign starting from JH. It will answer to JH1AAA, but will ignore any other prefixes from Japan, for example JA1AAA.
AutoSeq 4+ support of received directional CQ messages processing:
Processing of CQ DX, CQ + continent, CQ + (two character main country prefix) received messages is supported, where continent is [SA NA EU AS OC AN AF].
Autoselection will process received CQ message according to it's direction and according to direction of CQ message transmitted by user.
Additional AutoSeq related options:
'Strict directional CQ operation' option allows to ignore incoming calls from new DXCC country if it does not match to direction of user’s CQ message. Can be activated in Sequencing tab of the settings.
'Max distance instead of best SNR’ option allows autoselection to use maximum distance criterion for the same priority calls instead of the best SNR.
'Answer worked B4 calls' option can be activated to provide operation with the worked B4 calls in AutoSeq mode.
'Single shot QSO' option can be activated to turn of 'Enable Tx' button and prevent any message transmission when QSO is finished.
'Auto RX frequency filter' option is implemented to assist users with slow CPUs, it will switch on Filter button when any incoming call is received or if 'hisCall myCall myGrid' message is transmitted and will handle this frequency Filter switched on until QSO is finished. CQ message transmission and Halt TX will trigger switching off of the Filter button. Narrow frequency filter lets user to decode signals quickly, and AutoSeq3 mode can be used together with AutoFilter on the slow CPU.
Blacklist functionality is dedicated to prevent cyclic AutoSeq response to incoming call if calling operator left his setup unattended.
Also user can use blacklist to prevent selection of CQ message and answering to it if there were several unsuccessful attempts to answer to CQ message of this operator before.
User can add a callsign from DX Call window to the blacklist with CTRL+ mouse's right button click on Clear DX button, this will also clean up DX Call and DX Grid windows and this callsign from the QSO history.
User can remove callsign located in DX Call window from blacklist using mouse's right button click on Clear DX button, this will also clean up DX Call and DX Grid windows and this callsign from the QSO history.
All data in the blacklist will be automatically cleaned up at band change, configuration change and restart of JTDX.
Recommended settings: at wideband decoding one can use AutoSeq1 on slow CPUs, AutoSeq2,6 on average CPUs and AutoSeq3,7 on average and fast multicore CPUs.
We recommend to use Tx/Rx Split of AF frequency while operating with AutoSeq.
AutoTx button shall be switched on to provide proper autosequencing operation.