I just noticed this on hamapps.com
"New JTAlert 2.10.0 is available for download.
This version has full support for FT8 and the 15sec T/R period.
HRD v6 logging is again supported. HRD v5 and V6 users need to upgrade their JTAlert version to 2.10.0 to avoid logging and spotting the wrong mode (FT8 spotted/logged as T10 or JT9).
Visit HamApps.com for the download link and upgrade instructions.
Please review these release notes for 2.10.0
**** HRD V6 logging is again supported by JTAlert.
**** The HRD V6 logging support in this release is a one-time event.
**** Releases after 2.10.0 will again no longer have HRD V6 support.
New Features:
- Full FT8 mode support and its 15 sec T/R period.
- All the Wanted alert types support FT8 mode tracking.
- Scan Log supports FT8 mode for all Alert types.
- Additional Alert tracking option, "Any WSJT-X Mode (JT65 or JT9 or FT8)".
- FT8 mode statistics from HamSpots included in Band Activity displays.
- Call History popup & standalone window support FT8 data from Log lookup.
- WSJT-X mode character included in JTAlert titlebar (before the Band).
Character matches that used in WSJT-X, "#" = JT65, "@" = JT9, "~" = FT8.
Changes:
- Macros window single instance setting removed. Each JTAlert instance must
open its own Macro window for each WSJT-X/JTDX instance.
- End TX/RX Period alert disabled for FT8 mode.
- Auto-Halt after current TX is disabled for FT8 mode.
- Confirmed Bands Display (below log fields) right area will display Bands
worked/confirmed matching WSJT-X TX mode JT9 or FT8
- Many internal code changes to support FT8 mode and 15s T/R period and to
correctly distinguish between WSJT-X and JTDX running processes.
(** The JTDX program calls itself wsjtx.exe which it isn't **)
- The multi-instance support has also been changed. Running multiple copies
of JTAlert against both WSJT-X and JTDX simultaneously is not supported.
You can run multiple instances of JTAlert against either WSJT-X OR JTDX
only. Both types of applications can be running simultaneously on the PC,
but only one JTAlert operating mode (against WSJT-X or JTDX) is allowed.
Fixes:
- WSJT-X docking stops when a WSJT-X Configuration switch is made.
- DXKeeper Capture window inadvertently populated when DXKeeper is instructed
to filter its display on a new DX Call change.
de Laurie VK3AMA"
One time event? I'm not sure what is going on there and I actually don't care. I now use the excellent QSO Relay as a go between to allow JTAlert and HRD logging to function
No comments:
Post a Comment