Locked Re: WSJT-X Incorrectly Reporting "New DXCC on Band" #TechnicalHelpQuestion

Dave Garber <ve3wej@...>

I found that wsjt ( using the wsjt_log.adi keeps track of calls worked
before, jtalert scans your actual log. if one entry did not get into
actual log, it will still be in wsjt's log adi file so it will report as
worked, where jtalert had no idea...

also you can check the all.txt file(s) for the callsign to see if you ever
tried, but thought it was incomplete

Dave Garber

On Thu, Feb 17, 2022 at 8:53 PM Richard Wall <richard.k1xe@...> wrote:

Hello All,

This probably sounds like a repeat issue .. but I don't see a current
posting that cures my problem.

I've reinstalled all my software, and everything is working fine,
"except" WSJT-X incorrectly flags some entity CQs as "New DXCC on Band",
when in fact I've already confirmed contacts on that band for that entity.

I'm using:

DXLab DXKeeper 16.4.5
WSJT-X 2.5.4
JTAlert 2.50.9

In the few instances when WSJT-X incorrectly flags a CQ as New DXCC on
Band, JTAlert "correctly" displays the call as simply a new CQ, and "not"
as a new entity for that band.

As suggested in other postings, I have created an export file in DX
Keeper. Then renamed that file as wsjtx_log.adi. And then put that file
in the proper WSJT-X directory.

When I startup WSJT-X, I briefly see the total of records that are read
in the startup process. A slight oddity .. I've tried the export, and file
move a couple of times. Each time the WSJT-X startup display is a few
records lower then the DX Keeper total. For example in the last try ... DX
Keeper record total was 18891 and WSJT-X was 18617.

As I work new stations ... the totals for both applications increase.
(DX Keeper and WSJT-X) i.e. they do seem to be synchronizing properly.

Any thoughts?

Dick, K1XE

Join main@WSJTX.groups.io to automatically receive all group messages.