toggle quoted messageShow quoted text
I use WSJT-X almost exclusively for very long haul DX on 160 and chasing grids on 6M. I don't use FT4, so this is not an issue for me. But a point of information for you -- last year, many 6M ops started using both WSJT-X and JTDX simultaneously, because both programs (but most often JTDX), catch a weak decode that the other misses.
73, Jim K9YC
In recent weeks there have been a number of
users repeatedly spotting FT4 spots to HamSpots as Q65.
This is caused by the user using the JTAlert WSJT-X shortcut when
The problem stems from changes the JTDX people made to the WSJT-X
UDP protocol. Specifically, the UDP decode message contains a
single character that identifies the mode for the decode. The
WSJT-X standard uses ":" to identify Q65, but JTDX chose to use
":" to identity FT4 decodes.
JTAlert overcomes this by using an alternate character to mode
mapping table for JTDX users.
To change the character to mode mapping JTAlert needs to know what
application you have JTAlert working against, WSJT-X or JTDX, this
is why there are different shortcuts to start JTAlert, the Red "X"
icon for WSJT-X and the Blue "X" icon for JTDX. This has been in
place for quite some time.
Recently a number of users have been using the WSJT-X shortcut
when running JTDX, as a result, if they are working FT4 all spots
to HamSpots are flagged as Q65.
The fix is simple, use the correct JTAlert shortcut.
de Laurie VK3AMA