Update JT-Alert 2.16.0 – 07/03/2020


 Includes Callsign database file version 2020-03-05 (2020-March-05)

New Features:

  • New Alert Type: Wanted Canadian (VE) Province Alert. Full support with Province 2 character indicator, individual voiced Province sounds, and updating of needed Provinces via a “Scan Log and Rebuild” or manual setting. Individual voiced Province alert files are included in the 2.5.2 Sound files package.
  • Clear B4 Cache Menu: A user can now force a clearing of the internal worked B4 cache via the “Alerts -> Clear B4 Cache” menu. Clearing the cache will force all new decodes to get a new B4 status via a Log lookup that is then cached.


    • Callsigns Cleared: Callsigns display is now automatically cleared after logging a new QSO. This is not optional.
    • State Dropdown: The log fields display State dropdown list now automatically adjusts the list of 2 character codes to show only US State (and KL7, KH6) or VE Province codes depending on the Country of your current QSO partners. The dropdown is cleared for non VE or US callsigns.
  • Wanted State Alert: US State Alerts now consider “DC” for alerting and Scanning. If you don’t want to chase “DC” as a separate alert-able State you don’t need to take any action. If you do want to chase “DC” then un-tick the “Consider DC as MD” checkbox on the Wanted States Scan Log section, then run a Scan. A voiced alert wave file for “District of Columbia” is included in the 2.5.2 Sound files package.


  • B4 indicator: Newly logged Callsigns not displaying the “B4” indicator when the Callsign is next decoded after logging. (2.15.11 defect)
  • Fatal Error: Line 11057 or 11247 error when the Wanted State Alert is set to use individual State Name announcments and the Alert is triggered. (2.15.11 defect)

Update LOG4OM V2 – 2.4.0 -03/03/2020


1. Version 1 SQLite database is not compatible with Version 2
2. An ADIF file in ADIF 3.0 format must be exported from Version 1 of Log4OM
3. A new database must be created in Version 2 and the ADIF file then imported 
4. Version 2 configuration is different to version 1 so needs setting up newIf all else fails read the user guides and watch the YouTube tutorials


  • [NEW] Added Clublog/CTY file exception correction on all cluster items
  • [NEW] LazyLog massive data entry interface added
  • [NEW] ADIF export can now produce files with a reduced, user selectable, range of fields (File -> Export ADIF)
  • [NEW] Added CSV export with user selectable/sortable fields (File -> Export CSV)
  • [NEW] Option to invert FREQUENCY/MODE order in message sent to radio (Settings – CAT)
  • [NEW] Added native support for network connected rigs through Hamlib (FLEX and similar)
  • [NEW] Added SOTA Chaser/S2S/SWL TSV/CSV file format export capabilities (Award Statistics screen -> Export)
  • [NEW] Added “stay on top” option on contest and winkeyer screens
  • Added management of award reference alias. Will affect correct identification of USA-CA award references and others.
  • ADIF and CSV export is now available also in QSO Management with full output filters
  • Improved EQSL and LOTW import performances
  • Improved WSJT/JTAlert ADIF inbound message performances
  • Improved reactivity of QSO add function. QSO save is made asynchronously respect main UI
  • Added management of the (now deprecated) QSL_SEND status “Validated”. This will mark all LOTW and WAS references as VALIDATED.
  • New option in Alerts: Ignore statistics. Trigger the alert under any condition of worked/confirmed for the country
  • Import of QSL_RCVD status Verified (actually deprecated in ADIF standard) now set the QSO as VERIFIED for DXCC and WAS
  • Added option to start Hamlib application hidden (not shown on taskbar)
  • Previous QSO and Worked Before no more on top by default
  • small fixes in LOTW download interface
  • QSO filters improved: Added capability to explicitly exclude QSO that have a specific award in the myReference/contactReference. Useful to extract chaser without ref2ref contacts.
  • Clearing Callsign field in main UI resets map to station home QTH
  • Updated SOTA routines to support new summits csv file from SOTA website
  • [FIX] Massive QSO update performance issue fixed
  • [FIX] grid field editor no more stay behind the parent screen if parent is set to stay on top
  • [FIX] Length reported in ADIF format for frequency was incorrect
  • [FIX] Omnirig dual radio – one off issue fixed
  • [FIX] Award statistics view (chaser / activator / reference2reference filters)
  • [FIX] Prevented removal of QSO primary keys (date/callsign/band/mode) at database level
  • [FIX] My Rig and My Antenna not correctly retrieved when using a different profile in QSO Edit
  • [FIX] Reported length of ADIF fields now consider // as start of the comment and exclude comment length from adif field calculation
  • [FIX] Hrdlog sends online status even with not active.
  • [FIX] Changes in Winkeyer UI won’t trigger main UI interface refresh, stealing focus
  • [FIX] Current references in QSO under edit are not cleared if main parameters (band/mode) changes. User must check if current awards registered are still valid for the QSO even under new parameters. DXCC change always clear preselected awards

Update JTDX v2.1.0-rc148 – 21/02/2020

JTDX 2.1.0 Change logs


– reordered launching of threads in FT8 decoder
– minor changes to Spt/Menu controls view, reversed broken Pwr slider appearance
– ‘fusion’ is set as default JTDX style, ‘-style=windows’ key in JTDX launching shortcut will switch ‘fusion’ style off
– crossband 160m band operation with Japan is moved to option for all scenarios but EU-JA QSO, by default crossband is enabled, can be switched off in Misc tab of main window UI
– patch to possible marker misalignment in QSO RX frequency messages window triggered at double click on message
– messages like ’73’ shall not be treated as ‘reply to other’ while correspondent using multislot transmission
– prevent calling on Fox frequency when user resuming TX after three unsuccessful TX attempts
– added optional broadcast of logged QSO ADIF message to secondary UDP server, the same message format as in WSJT-X being used, controls are in ‘Reporting’ tab of configuration settings, same message format as in WSJT-X is used
– ‘Logged ADIF’ UDP message addressed to primary UDP server now is optional, can be activated in ‘Reporting’ tab of configuration settings
– main frequencies introduced, marked in frequency list by asterisk. At mode change JTDX will be selecting main frequency rather than Fox frequency.
  Some frequently used DXpedition frequencies added as default values in the frequency list. Main mode&band frequencies can be deleted by user, ‘reset frequency list’ will recover default frequencies
– six-pass SWL option is withdrawn from FT8 decoder
– implemented up to 3 cycles of FT8 decoding (each cycle has three decoding passes, six-pass SWL mode was two cycle decoding), one cycle is set by default, two or three cycles can be activated independently for operation and SWL modes.
  Withdrawn multicycle FT8 decoding dependency on number of running JTDX instances. Still there shall be more than 3 threads used in FT8 decoder to get multicyle decoding active in SWL mode.
– Hint button shall be switched on in FT8 mode by default(first launch of JTDX or if .ini file is deleted)
– automatic FT8 decoder thread selection shall spare one thread to other tasks if CPU has more than 2 logical cores. If user sure in flawless CPU & software functionality he|she can bring back decoding time selecting manually number of FT8 decoder threads equal to number of CPU logical cores.
 – FT8 decoder AP masks related code cleanup
– main window UI: CAT recovery button is moved up close to frequency label, minor changes to top/right side buttons allocation
– thinning FT8 candidate list based on the sync pattern quality: 3..15% decrease of decoding time of FT8 interval
– upon accepting configuration settings JTDX shall retain current VFO frequency if it matches to a frequency in the list, else shall set main mode&band frequency
– patch for counters when doubleclicked on call which is not in history (no CQ or 73 like messages received from this callsign), first counter did not work in such scenario
– ALLCALL7.TXT is now being used for filtering false FT8 decodes with support of 7-char Australian callsigns, ALLCALL.TXT is not used anymore
– filtering false decodes: faster callsign search in the ALLCALL7 based list via block data access
– added checking for false FT4 decodes starting from “TU; “
– added SNR and DT criteria for checking FT8 false decodes containing ” R “
– one more attempt to eliminate ‘CQ DE AA00’ false FT8 decode, it was likely coming from OSD decoder with AP mask in presence of strong signal on the band
– LoTW users list is updated, cty.dat file is updated to version CTY-3004
– ALLCALL7.TXT is updated to 111851 callsigns
– rc148 is built with modified Hamlib code v20200123 

Log4OM V2 Released 04/02/2020


Release note – Version

  • CAT frequency display is now user configurable for best visual comfort in Settings -> CAT
  • Added viewable Clublog Sent, QRZCom Sent, HamQTH Sent fields to the list of available fields in grid.
  • Faster LOTW download. “paper qsl confirmation download” made optional. You should use it only when you have new paper qsl registered and validated by ARRL. Download is disabled by default.
  • Alert engine fixes and optimizations.
  • JT interface message parser has been completely rewrited.
  • Added capability to read ADIF message 12 directly from WSJT-x (ADIF message).
    Note: This option (new in configuration screen) should NOT be used with JTAlert automatic log options, JTAlert UDP ADIF send and WSJT-x native UDP ADIF send or you will probably log twice the same QSO.
  • Small label fixes on User Interface.
  • Popup alert for new releases added.
  • Added supercluster connection status on cluster screen.
  • Detailed logs added in case of failed upload to external services  (payload provided is always saved when upload fails).
  • UDP logs now shown on logfile only in DEBUG mode. That will provide better performances.
  • EQSL data matching improved. Now received “SSB” will be searched also as “USB” and “LSB”. USB and LSB are now searched in log as SSB also.
  • Added 45 seconds maximum wait for TQSL to complete operations on program closure.
  • [FIX] LOTW Upload confirmation from QSO Edit form fixed.
  • [FIX] QSO already marked as received no more updated (initial eqsl download date preserved) in EQSL download.
  • [FIX] Audio keyer won’t stop PTT when message finishes.
  • [FIX] Cluster visualization issue related to VOACAP calculations prevented data visualization.
  • [FIX] Fixed issue on user specified login/password when connecting to cluster service.
  • [FIX] Revised internal conversion from number to strings (ex. ADIF FREQ EXPORT).
  • [FIX] Start-end date format fixed in contest configuration screen.

Update JTDX v2.1.0-rc147 – 26/01/2020

JTDX v2.1.0-rc147


– major defect in FT8 decoder fixed for 64bit builds, affected all previous Linux/Mac 64bit     JTDX builds: improved FT8 decoder efficiency and decreased decoding time
– JTDX-win64 build is made under Qt 5.14.0, approximately 1.6 times faster in decoding FT8 signals (tested with 4 threads) on overcrowded band versus JTDX-win32 built under Qt 5.5
– reworked meter stuff, now should be also bulletproof around enabling meter for rigs where it is not supported. RF output power indication should work with Icoms: ic7000, ic7100, ic7200, ic7300, ic7410, ic756pro3, ic7600, ic7610, ic7700, ic7800, ic785x with new introduced RFPOWER_METER level function.
– attempt to get S-meter indication for Yaesu ft100,ft450,ft600,ft736,ft757gx,ft950,ft1000mp,ft1200,ft2000,ft5000,ft9000
– attempt to enable RF output power indication for new Yaesu radios using newcat protocol
– reworked S-meter indication for any new Yaesu radio where newcat protocol being used
– FT8 FT4 decoders shall clear in current interval audio frames received prior to the band change
– attempt to prevent “CQ DE AA00” false message created by FT8 decoder
– allow to set AF RX frequency below 200 Hz
– status bar: date format is changed to DD.MM.YYYY
– LoTW users file is updated, cty.dat is updated to CTY-3001 version
– JTDX 2.1.0-rc147 is built with modified Hamlib v20200123 

Update LOG4OM V2 – – 26/01/2020



1. Version 1 SQLite database is not compatible with Version 2
2. An ADIF file in ADIF 3.0 format must be exported from Version 1 of Log4OM
3. A new database must be created in Version 2 and the ADIF file then imported into it
4. Version 2 configuration is different to version 1 so needs setting up new

If all else fails read the user guides and watch the YouTube tutorials

  • Enhanced Omnirig error handling
  • HAMLIB logics reworked to make it working as it should
  • HAMLIB PTT parameters correctly saved fix
  • Cluster interlock enhancements
  • Cluster data visualization improvements
  • Info provider page now shows the details of connection errors
  • Added selected/total counter in qso grids
  • Cluster start button now can be used to stop cluster in main UI
  • Send spot button disabled when cluster is not connected
  • Added 2 new buttons to force SPOT send from popup screen with notes
  • [FIX] Removed worked before refresh button
  • [FIX] Alert filters doesn’t trigger if reporter continent is set under some circumstances
  • [FIX] Added missing password encoding on some external calls
  • [FIX] Added ADIF check on import for empty file/incomplete basic data provided
  • [FIX] Main UI labels fixed
  • [FIX] Multiple award list in dropdown menu
  • [FIX] CQ and ITU zones fixed in QSO EDIT
  • [FIX] HRDLog status update
  • [FIX] [OmniRig] Fixed issue on RIG2 when RIG1 is not available
  • [FIX] Spot incorrectly reports TX VFO frequency during SPLIT operations on 2 VFO rigs

Update JT-Alert 2.15.8 – 25/01/2020



*** Includes Callsign database file version 2020-01-24 (2020-January-24)

New Features:

Log4OM V2: Full support for Log4OM V2, both SQLite and MySQL logs.

Log4OM V1/V2 SQLite logs: “Test” button to check log file selected is a valid SQLite file for the Log4OM version and contains QSO records.
See Settings window, “Logging -> Log4OM…” sections.

– Logging option: New “Do not check or report logging success/failure”. This option when ticked (off by default) instructs JTAlert to not try and confirm that a QSO was logged by reading the Loggers log directly. Once the logging instruction has been sent, JTAlert goes back to normal operation, there are no delays or hangs as JTAlert is stuck waiting to confirm the QSO was logged. JTAlert will however still report a logging failure when it could not initially establish the TCP or UDP connection to the target logger.


– MySQL support: libmysql.dll file updated to v6.1.10 (previously v5.1.37)


– ADIF logging: Excessive time to confirm QSO logged successfully when using large adif files. 200,000 record check now takes ~1 sec (previous ~45 secs)

Update Log4OM V2 – – 21/01/ 2020

Release note – Version


  • [NEW] Added capability to run multiple instances
  • [NEW] Added “Select required” button for quick QSL upload. Required status is based on user preferences expressed in SETTINGS -> USER CONFIGURATION -> CONFIRMATIONS menu option
  • [NEW] Incremental worked before search in worked before grids. [WORKED BEFORE] notification will appears only on exact callsign match.
  • [NEW] Added worked before screen in main UI (F10)
  • [NEW] Unlocked command line arguments:
    /RESETLAYOUT -> remove all configured layouts in data grids
    /REMOVEUSERFILES -> remove all user edited files in the settings folder
    /RESETMAPCACHE -> reset the google maps map cache and reduce it’s size
    /SCHEDULER -> reset internal operation scheduler to factory
    /FACTORYRESET -> remove all user configurations except saved backups
    Usage: L4ONG.exe <parameter1> … <parameterX> eg: L4ONG.exe /RESETLAYOUT
  • Improved logging on UDP parser
  • [FIX] files marked with “_user” suffix not correctly retrieved under some circumstances.
  • [FIX] cluster time was not correctly sorted after first couple of QSO’s.
  • [FIX] my references is not shown when editing a QSO. This may result in a loss of information.
  • [FIX] IARU region not correctly read when different from country value
  • [FIX] Clustermanagement menu Exit now working

Log4OM V2 OUT Now!!


Welcome to Log4OM V2.

Log4OM support is direct from the development team and the user community, this guarantees to all users the best experience and a fast resolution of any problems. If you are an experienced user and can help, please do so!

If you need help please ask for support, however please be polite and provide a comprehensive description of the issue. The team dedicate their free time to support Log4OM users so please ensure that you read the forums and manuals before requesting support.

Like any software, Log4OM V2 is not perfect, despite the best efforts of the team! To avoid and reduce problems Log4OM has a wide range of functions which support the user and a very aggressive backup policy. However users are ultimately responsible for their own logs so always make sure to periodically check the creation of backups and activate, if possible, the secondary backup function on to a different disk or into a synchronized folder in the cloud (Google Drive, Dropbox, etc.). Finally upload your logs regularly to one or more of the online services, Log4OM will do these uploads automatically.

Log4OM is as free, however if you want to support future development a small donation to cover license and hosting costs will be very welcome,

Finally thank you for your support during the last eight years, the team will endeavour to justify your future confidence in Log4OM.

Best 73

Daniele Pistollato – IW3HMH & The Team

Update JT-Alert 2.15.6 – 02/01/2020

Update JT-Alert 2.15.6 voor WSJT-X

*** Includes Callsign database file version 2020-01-01 (2020-January-01)

New Features:

– Length of time old decoded callsigns will remain visible when there are no new incoming decodes is now configurable from 1 to 10 mode periods. A setting of 1 period will give a similar result to previous JTAlert versions where callsigns are displayed for one period only. (Default: 2 periods, Window: Settings, Section: “Window”).

– JTAlert will detect any changes in Windows audio output device ordering, which typically happens when the default device is changed. JTAlert will adjust to using any new device id assigned to your named JTAlert audio device. There can be up to a 60 sec delay before device reordering is detected. Note: any addition or removal of Windows audio devices while JTAlert is running is not handled and may break JTAlert audio, JTAlert will need to be restarted to account for the changes in number of Windows output devices.


– JTAlert no longer preemptively clears the callsigns prior to a new batch of decodes is received from WSJT-X, instead the Callsigns are cleared just prior to a new batch of Callsigns is to be displayed. If WSJT-X fails to decode a period or monitoring is turned off, the last batch of displayed Callsigns will remain visible, matching the last batch of decodes displayed in WSJT-X.

– Cached callsign data (dxcc, zones, state, etc) now reused across JTAlert sessions (previously cleared at start of each session). Callsign data is auto-cleared after 7 days which will trigger a new lookup when the call is next decoded. This will help reduce alerting delays during the initial decode periods when JTAlert is first started on very busy bands.

– Faster display of the decoded Callsigns at the end of an Rx period.

– “Check QSO Log Record” time setting moved from the “Performance” section to the “Logging” section of the Settings window.


– Band Activity popup window showing an unwanted taskbar button.

– Decodes database storing decode data from instance #1 only. (2.15.4 defect)

– Decodes distance column header text showing “km” instead of “Miles” after loading a Layout file when the settings specify miles display.

– Decodes Layout not restored correctly. Note: The default all columns layout may be shown when this version is run for the first time, with future runs the last used layout will be correctly shown.

Copyrighted Image

error: No Way Protected !!