Warn: eQSL Dupe upload (JTDX).

You may post here if you are having problems with Winlog32 that others may be able to help you with. You may also report bugs so that the author may act upon them.
Post Reply
atlantikman
New user
Posts: 2
Joined: Fri May 01, 2020 1:39 pm

Warn: eQSL Dupe upload (JTDX).

Post by atlantikman »

Hello,
I'm getting the above message when using JTDX and sending a log entry after a FT8 contact. Also noticed that I have no Date showing in the QSL Out column for each contact. Didn't have this problem with WSJT-X. I'm sure my settings are ok in JTDX. I've even transfered everything to another Laptop, with a new install, but it still does it. The relevant eQSL's are in my OutBox ok. So is it a problem with JTDX? In JTDX my Reporting settings are:
Prompt me to log QSO
Recording to ALL.TXT decoded messages
Enable eQSL sending (Username, Password, QTH Nickname)
Accept UDP requests
Notify on accepted UDP request
Enable sending logged QSO ADIF data.

73's de Paul.
atlantikman
New user
Posts: 2
Joined: Fri May 01, 2020 1:39 pm

Re: Warn: eQSL Dupe upload (JTDX).

Post by atlantikman »

Hi again, Think I've sorted it. My JTDX Reporting settings are:
Prompt me to log QSO - ticked.
Enable eQSL sending - unticked.
Accept UDP requests - ticked.
Notify on acceped UDP request - ticked.
Accepted UDP request restores window - ticked.
Enable sending logged QSO ADIF data - ticked.
Prevent spotting messages with the unconfirmed callsigns via UDP - ticked.
I don't now get the Dupe message, and the QSL Out date field is working again.
73's de Paul.
G0CUZ
Site Admin
Posts: 461
Joined: Wed Jan 02, 2002 7:12 am

Re: Warn: eQSL Dupe upload (JTDX).

Post by G0CUZ »

Hi Paul

Sorry I didn't get back to you quick enough, but yes, what was happening was that JTDX was uploading the QSO first then Winlog32 attempted to upload the same QSO and got the dupe message, so one of the upload options needed disabling.

Incidentally these options

Accept UDP requests - ticked.
Notify on accepted UDP request - ticked.

Do not need to be enabled for logging, I don't think it makes any difference whether they are are or not as far as Winlog32 is concerned, I don't enable these setting myself for JTDX or WSJT.
Post Reply