HamApps Support (VK3AMA)
On 10/01/2019 8:25 am, Dave AA6YQ wrote:
JTAlert is not a Contest Logger. It simply acts as logging bridge between WSJT-X and DXKeeper. There are no attempts to validate the Contest exchange based on different Contest rules or extract data from the Contest exchange. There is no attempt to include missing data within the exchange. JTAlert is a bridge, it simply passes through the WSJT-X Contest exchange.It means that if JTAlert is going to log contest QSOs in a manner that will enable DXKeeper to subsequently generate a Cabrillo file, JTAlert must log those contest QSOs in the manner described in
If DXKeeper is not utilising a valid Contest exchange for the Contest enabled within DXKeeper, eg. WSJT-X and DXKeeper are both set for RTTY Roundup, and a valid Roundup Exchange is passed to DXKeeper, unchanged by JTAlert, there is not point in logging the exchange, IMO.
The next release of JTAlert will no longer automatically log Contest exchanges (valid or invalid) to DXKeeper (whether in Contest mode or not). The JTAlert user will need to enable an option to permit logging of these unused (by DXKeeper) Contest exchanges.
de Laurie VK3AMA