1. posterid:239412
  2. JT-Alert 2.2.3: DXKeeper logging, fooled into wrong DXCC Entity

locked Re: JT-Alert 2.2.3: DXKeeper logging, fooled into wrong DXCC Entity

Jim - N4ST
 

I have done this before also. I suspect it is a function of JT65-HF, and a fix is not likely. Best advice is "don't do that". Hi Hi

73,
Jim - N4ST

--- In Ham-Apps@..., "g4wjs" <bill.8@...> wrote:

Hi,

I normally complete the logging before trying to work another station, but today I saw a new one come up before I'd finished inputting a comment on a log entry for a UA station. I double clicked a US station calling CQ in WSJT-X and then clicked the log QSO button a bit later.

I ended up with the DXCC Entity in the log record being set to 'K' rather than UA.

I have the JT-Alert-X Pathfinder lookup set on and FWIW DXKeeper also does a Pathfinder lookup to get callbook details when saving the QSO.

73
Bill.
Join Support@HamApps.groups.io to automatically receive all group messages.