locked JTAlert 2.15.9 is available. New Features & Fixes. #Announcement #NewRelease

HamApps Support (VK3AMA)

The Latest JTAlert version 2.15.9 is now available @

*** Important for "NO Log" users ***. Users who don't have a logger enabled in JTAlert rely on the JTAlert maintained B4 Log Database for Worked B4 alerting.
This database file has changed significantly and requires that "NO Log" users only, perform an ADIF import to pre-populate the database with QSO data from their primary logger. If an import is not done, than B4 alerting will consider all decodes as new and never worked. This adif import is only required once after which JTAlert automatically updates the database with each QSO logged. See the "Logging ->
Log B4 Database" section of the Settings.

New features include:
  • Continent of origin filtering of callsigns.
  • B4 alerting can now consider the on-air grid used (handy for catching roving stations that frequently change gridsquare).
Please review the Release notes at the end of this message.

de Laurie VK3AMA

Release Notes.

2.15.9 (06-FEB-2020)

  *** Includes Callsign database file version 2020-02-06 (2020-February-06)

  New Features:

    - Continent filtering of Callsigns: New filtering (hiding) of Callsigns based on
       Continent of origin of the callsign. All Continents by default are enabled.
       When one or more Continents are unchecked, any decodes originating from that
       Continent will not be displayed on the main JTAlert window REGARDLESS of any
       Alert they may have generated or any of the other Filters set. This does not
       affect the Decodes window which already has its own method of hiding decodes
       based on Continent of origin, it is not compatible with the Main window filter.

    - Worked B4: New "Ignore Grid" option to consider on-air grid when performing
       B4 checks against the Log. A previously worked station that normally produces
       a B4 will now generate an alert if their on-air grid is different from previous
       QSOs in your Log and this option is OFF (unticked).
       (Default: ON, Window: Settings, Section: Alerts, Worked B4).

    - B4 Log Database: Now records the Date and Grid of QSOs logged. This will allow
       "NO Log" users to utilise the "Ignore Grid" and "Ignore Date" options for the
        Worked B4 alert. IMPORTANT, this only applies to "NO Log" users.

    - Sound Device: A sound keep-alive added to try and prevent sound devices going
       into power-save mode. This is useful for those Audio drivers that put the
       device to sleep if no audio has been played for some time causing the first
       part of the sound to be lost as the card comes out of sleep.
       (e.g. NVidia HDMI card drivers that don't provide a power-save setting but
        set the power-save on in the Registry, so not user adjustable).


    - MySQL support: libmysql.dll file (used by HRD and Log4OM MySQL logs) has
       been downgraded to the version used in all JTAlert releases except the
       recent 2.15.8 public release. A small number of users experienced MySQL
       errors when trying to open the JTAlert Settings.

    - B4 Log Database: The B4log.mdb file used for B4 checks when running with no
       logger enabled ("NO Log" in the titlebar) is now named B4logV2.mdb and is
       NOT compatible with the old B4log.mdb file. This will require "NO Log" users
       to perform an ADIF import to pre-populate the file with their B4 QSO data.
       See the "Logging -> Log B4 Database" section of the Settings.

    - JTAlertV2.Manager: Process is now forcibly terminated if found to be running
       when JTAlert is first started.

    - Text Messages: Long received messages that were not originally sent with
       embedded carriage returns are now automatically wrapped when being displayed.

    - Highlight WSJT-X DT: The option "Highlight Band Activity DT values that
       exceed threshold" has been removed. Highlighting DT values is still available
       in the JTAlert Decodes window.


    - MySQL: "MySql Start Failure" message when trying to open the Settings window.

    - IOTA data: Not logged for Log4OM V1 & V2 MySQL logs.

    - Decodes Window: When running multiple JTAlert instances, decodes from one
       or more instances were not being displayed depending on startup sequence
       and if the Decodes window was closed and reopened during a JTAlert session.

    - Decodes Window: Missing decodes when running multiple JTAlert instances
       against several very busy bands resulting in UDP receive buffer overflow.

    - Alerting incorrect callsign: Decodes containing two callsigns only, flags
       the 2nd callsign as a gridsquare (when it is a non-standard callsign and
       the first 4 characters follow valid grid formatting) and incorrectly
       flags the 1st callsign as the transmitting callsign.
       eg. "P29ZL OL725PLZ" when OL725PLZ is Tx, JTAlert will alert on P29ZL.

    - Worked B4: Callsigns signing /MM, /R, /A, /P and /M failing worked B4 check.

    - Cocos Island: TI9A incorrectly shown as Cocos (Keeling) Islands. This is a
       cosmetic display defect only. All alerting and logging correctly used the
       dxcc #37 which is Cocos Island.