Major new feature is the support for logging
WSJT-X 2.0.0 contest QSOs (RTTY Roundup, NA VHF & Field Day
contests only) to N3FJP Contest loggers. See the JTAlert Help
file, "Tutorials -> N3FJP Contest Logs Logging" topic.
for the download link and upgrade/install instructions
This release is available in
two builds, the traditional build (menus and band activity
displayed on the titlebar) plus a new "Alternate Layout" build
created for those Win10 users who are experiencing missing menus
and band activity display with the traditional JTAlert build.
- Logging WSJT-X 2.0.0 Special Operation Mode
Contest QSOs (RTTY Roundup,
Field Day & NA VHF) to N3FJP Contest Logs
(ARRL RTTY Roundup, ARRL Field
Day & VHF respectively). Important: See
JTAlert Help File for setup & usage.
("Tutorials -> N3FJP Contest Logs Logging"
- WSJT-X 2.0.0 Special Operation Mode shown in
JTAlert titlebar status text.
[RU] = RTTY Roundup, [FD] = Field Day, [EU] =
EU VHF, [NA] = NA VHF
[FOX] = Fox, [HND] = Hound.
- Option to log WSJT-X 2.0.0 Contest exchanges
(rcvd & sent) to N3FJP ACLog
(Default: OFF, Window: Settings, Section:
Logging -> ACLog -> Other Fields).
- Maximum number of auto-start applications
entries changed from 10 to 30.
- Incorrect Log4OM Sqlite Log file mismatch
warning shown at JTAlert startup
when file paths contain non-english accented
- FT8 Decodes containing two callsigns only,
incorrectly flags the 2nd
callsign as a gridsquare (when it is a
compound callsign that follows
gridsquare formatting) and incorrectly flags
the fist callsign as the
transmitting callsign. eg. "VK3AMA AA12BB"
when AA12BB is transmitting.
- Address data containing single quotes
(apostrophe) logged with multiple
single quotes to DXKeeper & HRDLogbook V6.
- Callsign of directional CQ decode with 3 &
4 character direction word
incorrectly displayed with standard CQ
indicator ("*") and colored border.
de Laurie VK3AMA