• Changelog 18th January
    - relaxed 'Automatic RX frequency filter' Filter button activation
    - more events added to ALL.TXT
    - some Clear DX and Halt TX patches applied
    - 'status', 'decode' and 'reply' UDP messages updated to WSJT-X format
    - some tweaks to '73' free messages handling by AutoSeq
    - WSPR RX message truncation bug is fixed
    - 'Answer worked B4' option is implemented to all AutoSeq modes

  • Changelog 13th January
    - sound input/output buffer size is changed back to WSJT-X values
    - software is built using FFTW v3.3.5 library, updated it in JTSDK from v3.3.4
    - FFTW dynamic multithreading is recovered, up to 12 threads is allowed now in non JT65 modes (up to 3 in WSJT-X), up to 11 threads is allowed in JT65 mode
    - minor code clean up



  • Changelog 10th January
    - more tweaks to AutoFilter functionality
    - changed documentation link
    - added optional automatic 'Erase band activity window at start of decoder' functionality, it can be activated in Misc action list, main window UI.
    - implemented partial AutoSeq processing for decoded on the RX frequency addressed and unaddressed free messages containing '73':
    - after sending RR73,RRR,73 standard message any decoded nonstandard message with '73' inside will be processed
    - after sending REPORT or ROGER+REPORT standard message decoded nonstandard message with 'myCall' and '73' inside will be processed

 

  • Changelog 6th January
    - AutoSeq patch to prevent unexpected stopping TX if RR73 message is being used for transmission while QSO is not finished (message 73 is not received from QSO party operator)
    - color background for TX messages is aligned
    - AutoSeq patch to this scenario where directional CQ was used:

    20180105_035400 -4 -0.2 2140 ~ AG2T CM2RSV EL83
    20180105_035415 Transmitting 7.074 MHz FT8: CM2RSV AG2T -04
    20180105_035430 0 -0.2 2140 ~ AG2T CM2RSV EL83
    user disabled TX at 035445 035515 035545
    directional CQ message is generated and transmitted by user:
    20180105_035615 Transmitting 7.074 MHz FT8: CQ DX AG2T FN30
    unexpected RR73 message is triggered by AutoSeq:
    20180105_035615 Transmitting 7.074 MHz FT8: CM2RSV AG2T RR73
    20180105_035630 1 -0.1 2141 ~ AG2T CM2RSV RRR
    20180105_035645 Transmitting 7.074 MHz FT8: CM2RSV AG2T 73



  • Changelog 4th January
    - Patch applied to AutoSeq handling possible gaps in the incoming audio stream: AutoSeq shall not change during the QSO style of operation(message sequence) from 'calling CQ' to 'answering to CQ'. In addition to the previously described reasons of audio gaps there is scenario where user has single audio device that is set as default one by MS Windows operating system and user doing Web browsing during the QSO.
    - Minor SWL functionality is implemented to FT8 mode, raises FT8 decoding efficiency approximately 1% up, SWL functionality is not dedicated for on air operation
    - Text is set to blue color on the AutoSeq button if 'Single shot QSO' option is activated
    - No TX audio issue: there are two possible reasons,
       -- first is where user accepting Settings change dialog with OK button, patch is applied to this issue in scenario where there is no audio device changed
      --  second reason is that between consecutive pushing of buttons Halt Tx and Enable TX at message transmission shall be at least 2 second gap, if user does it faster it resulting in no TX audio in this TX interval. So far I don't know how to deal with this scenario.
    - New functionality for audio device change during message transmission: transmission will be stopped, Enable TX button will get yellow colr for couple seconds and message transmission will be restarted
    - Last logged callsign label is implemented in the status bar
    - Several errors fixed in the code, input signal array handling is changed at entry point of the FT8 decoder

  • Changelog 3rd January
    There is 'Single shot QSO' option implemented to let users switch off Enable Tx button automatically when QSO is finished.
    This functionality can be activated in the AutoSeq action list in main window UI.

  • Changelog 31th December

    - bug is fixed where SW did QSO in semi-automatic way while AutoSeq button was switched off
    - QSO party's callsign is being cleaned up from QSO history at 'hisCall myCall grid' message transmission

    Both changes can eliminate some wrong QSO sequences in AutoSeq mode.

  • Changelog 30th December

    AutoSeq wrong handling of received RR73 message is fixed
    Some more tweaks done to prevent unexpected AutoSeq transmissions on the frequency of ex- QSO party
    Bug is fixed in AutoSeq mode selection logic
    SWL mode is blocked in FT8 decoder to prevent it's unintended usage
    Band scheduler functionality is recovered
    Recovered passing DX Call decoded 73 message to RX frequency window in scenario where Enable Tx is switched off
    Fixed bug for "reading wav file" event and added Filter ON/OFF event into ALL.TXT
    Deleted JTDX version number from widegraph window title, as it caused compatibility issue with JTAlert software
    Added "QRZ " as trigger for AutoSeq
    Implemented new AutoFilter functionality for AutoSeq, it is dedicated for slow CPUs and may be used in AutoSeq 1,2,3 modes
    AutoFilter can be activated in the AutoSeq action list of main window UI

    Known unresolved issues:

    Enable Tx button is switched off after QSO  in calling CQ operation and early QSO logging using "Prompt me to log QSO" scenario
    Free messages / TX macros functionality is partially broken
    AutoSeq can fail while handling compound callsigns
    AutoSeq can fail if called operator changed his TX frequency and has answered on some other frequency (?)

    Decoder latency, AutoSeq design and CPU processing speed related issue:
    Late interval decoding by CPU. AutoFilter functionality is implemented as workaround for this issue.

    JTDX.INI structure is changed, added new parameter "AutoFilter". JTDX.INI file from v18.1.0.58 can be used and shall not trigger any issues

  • Changelog 28th December

    Common version number being used for all UI windows and pskreporter,

    Now fixed unexpected RX frequency jumps from selected RX frequency to TX frequency if Enable TX button is turned off
    AutoSeq operation mode is named from 1 to 7, where 'and search CQ' is being used as 4 + any basic AutoSec number
    logging mode is being indicated as coloured background of QSO counter label (status bar)
    direction of CQ is being propagated to tx6 button (tab 1) on program initialization
    tooltips changed for Clear DX / Erase / Filter buttons and 'Halt Tx if operator I called answered to other operator' checkbox
    AutoSeq2 is set as default option
    changed functionality for Erase button: left mouse button will clean up left window, right mouse button will clean up right window, any mouse button double click will clean up both windows
    Currently unused Sequencing tab controls are disabled and greyed out

    Known issues:
    free messages / TX macros functionality is partially broken
    AutoSeq can fail while handling compound callsigns
    AutoSeq can fail if called operator changed his TX frequency

  • Changelog 25th December (compact and not all changes are shown)

    In answering to CQ operation and 'Prompt me to log QSO' logging mode:
    Enable TX button will always be switched off after QSO if TX frequency is equal to RX frequency
    Enable TX button will be switched off if TX frequency is not equal to RX frequency and user has accepted QSO logging when QSO is finished (73 message is received)
    Enable TX button will not be switched off if TX frequency is not equal to RX frequency and user has accepted QSO logging until QSO is finished (73 message is received), in this scenario after QSO JTDX will move RX frequency to TX frequency and will start calling CQ on the TX frequency

  • Changelog 23th December (compact and not all changes are shown)

    AutoSeq is always using priority, if there is any 'new one' criterion is set in Notifications tab then AutoSeq will be ignoring B4 calls and manual intervention will be required to answer it.
    There have been many changes, and selection changes can be seen in Mainwindow UI top tab under Sequencing.
    Any push buttons that are greyed are currently disabled for mode and or this step.

  • Changelog: 22th December

    Tx watchdog operation, now a double click on decoded line will trigger watchdog timer reset
    Default setting is now Call 1st
    If you experience any delay in decoding on busy bands, please use Call 1st
    Please copy a section of your all.txt file and post this privately or in group if you experience and issues.

  • Changelog 21th December (compact and not all changes are shown)

    AutoSeq Call 1st option is implemented, dedicated for usage on slow processors
    Skip TX1 functionality is supported now, sending report first
    FT8 wrong SNR reporting under Filter is fixed
    Directional CQ generation is changed in tab2
    Changed date/time format in ALL.TXT file to "yyyymmdd_hhmmss"
    Directional CQ, this allows user to input preferred calling area, and replaced CQ DX option in Tab 2

    Some features that use previous calls for priority may use more processing power, as it is performing more tasks; this is dependent on the station preferences in configuration filtering and Dx call, wanted call and worked B4 station in filters and notifications tab.

  • Changelog: 19th December

    Patch applied by Arvo for free text messages under Autoseq control
    Also the version number for PSK Reporter is now 18.1

    There have been many changes and additions these are a compact description.
    Action call priority and CQ 
    This feature now will auto call stations in a sequence that have not already logged, allowing those stations who seek new call only to do so.
    This feature will also not reply to any calls already showing in log again this feature will prevent Dx or Dx expos from double logging and wasting valuable time on repeat callers

    Filter function is now available in FT8
    The clearing of Dx windows and the ability to send and RRR then a 73 has also been addressed
    There have been cosmetic features add at user requests

  • Changelog: 12th December

    The goal is to keep callsign in DX Call window if you called DX and DX operator has answered to other operator.
    So you could wait for his 73/RR73 message and call him again. Now 73/RR73 message in such scenario will be printed in the RX frequency messages window, with no respect to the real frequency this signal is decoded.
    There is now 4-period guard timer that will ban auto prompt to log QSO or automatic QSO logging if you transmitting 73/RRR/RR73 message again to the same callsign that has just been logged.
    Also other modifications are being worked on currently to further enhance user features and prevention of QRM and ease of use.
    Please use the QRM prevention features available. Configuration window: Sequencing "halt Tx", this will make all users experience pleasant
    Tx watchdog: will have Tx after 7 transmissiom (current implementation)

  • Changelog: 10th December

    Reworked replyToCQ() method responsible for getting control from external software, like JTAlert

  • Changelog: 9th December

    T10 symbol is changed to +, FT8 to ~, posting decoded messages via UDP is open there and this step will work with the latest JTAlert 2.10.6.
    Also this step shall work with Logger32 and Swisslog.

  • Changelog 8th December

    FT8 is currently partly implemented in JTDX 8th December.
    There is still development work to be done to fully implement all current JTDX features for FT8.
    FT8 credits to K1JT and the WSJT-X development team, Copyright notice included

  • Changelog: 25th November

    Addition of content filtering in configuration setting, please follow link for full instructions and examples.
    Show content related to messages in Rx window.
    Code optimization and removal of redundant code and features in JTDX

  • Changelog: 19th November

    JTDX AutoSeq and correct logging corrected.
    There has been many changes and testing, please post any issues in the group
    Please see previous step release posting for full changelogs from previous steps
    FT8 is not currently implemented in JTDX and should be included in next JTDX release
    FT8 credits to K1JT and the WSJT-X development team, Copyright notice included

  • Changelog: 15th November

    More improved accuracy of the QSO start/end time logging.
    Following a post from Steve VK3SIR, JTDX Autoseq can handle many different forms of reply as expected or unexpected during a QSO.

  • Changelog: 14th November

    There is better handling of QSO time_on: callsign checking added at report and roger+report message transmission.
    This patch shall fix an issue where two contacts in the log have the same QSO time_on.