• Changelog January 18th (2.0.1 rc125)

          - added support to nonstandard callsigns for QSO messages processing by FT8 Hint decoder on the RX frequency
          - updated LoTW users file
          - changes in the RX frequency tracking functionality
          - patch to the beep sound notification
          - cty.dat file is updated to version CTY-2901
          - implemented dynamic FT8 Hint decoder for messages with standard callsigns. This decoder being not activated while playing wav files, partially activated at attempt to decode last period again

        • Changelog January 12th (2.0.1 rc124)

          - 'LoTW user' notification symbols are changed
          - sybmol • this operator loaded his log into LoTW
          - symbol ° this operator loaded his log into LoTW and this is Hint decode (FT8 AP or matched filter based decoder in JT65 JT9 T10 modes)
          - symbol * - Hint decode (FT8 AP or matched filter based decoder in JT65 JT9 T10 modes)
          - If prefix starting from symbol * (first char position of the prefix) then it is notification about an entity from the WAE award list, this notification coming from the cty.dat file
          - Grid notification is improved: QSO history shall be searched for grid for notification to messages with report
          - improved QSO messages processing by FT8 Hint decoder
          - extended FT8 SNR reporting range down to -26 dB for FT8 Hint decoder

        • Changelog 8th January (2.0.1 rc123)

          - disabled data writing into %TMP%/JTDX/decoded.txt file
          - extended reported FT8 SNR range down to -24dB for FT8 AP decoder
          - candidates on the QSO frequency shall be sorted in the decreasing sync order
          - updated ALLCALL.TXT file, containing 76731 callsigns
          - added 'LoTW user' notification: symbol '@' means LoTW user, symbol '¤' means LoTW user and FT8 AP decode.
          This special symbols are displayed in decoded text and RX frequency windows only.
          LoTW notification is used in autoselection with this priority order: 'new one' has highiest priority, next priority is LoTW, SNR/distance has the lowest priority.
          File lotw-user-activity.csv is used to store information on the LoTW users, this file can be updated by user in the same way as cty.dat file in the log directory.
          LoTW notification can be disabled if user will put empty lotw-user-activity.csv file in the log directory.
          - added more filters to eliminate false FT8 decodes

        • Changelog 2nd January (2.0.1 rc122)

          - one more patch for correct FT8v2 message generation for combined callsign with 3 digit prefix + '/' + base callsign starting from 'P' or 'R' char (for instance DU6/PA3AAA, KH6/RA3AAA)
          - added FT8v2 signal simulation with recording to the wav audio files
          - user's callsign and first two chars of grid in configuration shall be converted to upper case while being typed
          - support to up to 200 decoded FT8 messages including dupes
          - asterisk for FT8 AP(Hint) and JT/T10 Hint decodes shall be diplayed in the decoded text window
          - updated ALLCALL.TXT file, containing 75877 callsigns
          - autoselection functionality is improved: decoded '73' messages will be processed in addition to the 'CQ' messages in AutoSeq6,7 modes
          - autoselection will now be applied of any of counters is triggered (criteria by priorities + SNR/distance).
          - In AutoSeq 1,2,3 modes any possible incoming calls fill be searched, if there is no valid incoming call found then 'CQ' message will be transmitted.
          - In AutoSeq 6,7 modes any possible incoming calls fill be searched, if there is no valid incoming call found then autoselection will process decoded '73' and 'CQ' messages, if there is no any configured criterion met then 'CQ' message will be transmitted.
          - in scenario where user called someone and correspondent answered to other operator: one of the first two counters will be triggered respectively to the transmitted by user message
          - QSO data sending to eQSL server is moved to own thread
          - 1908 kHz subband is added to the frequency list to support making FT8 QSO with Japan on 160m band. Please use 'Reset' button once in the Frequencies tab of the settings to update current frequency list in JTDX. automatic subband split via CAT interface to support FT8 crossband operation with Japan on the 160m band: user with non Japanese callsign shall select in JTDX UI 1908000 Hz frequency for signal reception, JTDX will trigger VFO frequency change to 1840 kHz for message transmission user with Japanese callsign shall select in JTDX UI 1840000 Hz frequency for signal reception, JTDX will trigger VFO frequency change to 1908 kHz for message transmission
          - patch to prevent wrong processing of the 'callsign1 + callsign2' message
          - patch to early counter triggering in AutoSeq3,7 modes in scenario where message transmission started before decoding has been finished
          - patch to prevent message cycling in JTDXJTDX pair at scenario where user changed 'grid' message to 'report' or 'R+report' message while calling correspondent
          - more filters added to eliminate false FT8 decodes

        • Changelog 24th December (2.0.1 rc117)

          - more filters to false decodes
          - patch to AutoSeq message sequence: scenario when two incoming calls received where one of them is with report
          - ALLCALL.TXT file is updated, containing 75435 callsigns
          - combined callsign with 3 digit prefix + '/' + base callsign starting from 'P' or 'R' char (for instance DU6/PA3AAA, KH6/RA3AAA) shall be handled correctly

        • Changelog 19th December (2.0.1 rc115)

          - AutoSeq shall handle free text messages at QSO with nonstandard or combined callsign
          - filter out some more false FT8 decodes, now using data from ALLCALL.TXT to filter out some false decodes
          - ALLCALL.TXT file is updated, containing 75243 callsigns
          - cty.dat file is updated to version CTY-2815