EQSL Download Confirmations

[G4DZU]

Hi,

I've transferred my logbook to V2 with no problems using a V3 ADIF file.

LOTW is FB, but have a problem with EQSL when downloading confirmations.

After pressing the button, I get below every time.

It appears to be parsing the whole of my logbook and goes on through the whole of my log book displaying errors with the locator etc. it does indicate that it is updating, but next time i try to download confirmations it goes through the whole process again putting pages of errors on the screen.

Am I doing something wrong, I didn't have this with V1

73s
Doug
G4DZU


13:21:46: Request link: https://www.eqsl.cc/qslcard/DownloadInB ... 1904040000 ***** passwords etc blanked ****
13:21:46: Sending ADIF generation request...
13:21:49: Downloading ADIF document from https://www.eqsl.cc/downloadedfiles/GDW447121.adi ...
13:21:49: Parsing ADIF file...
13:22:18: ADIF document parsed: 720 qso found.
13:22:18: QSO NOT FOUND: EA1AHY|22/10/2019 08:58:00|30m|FT8
13:22:18: QSO NOT FOUND: F2YT|22/10/2019 09:01:00|30m|FT8
13:22:18: QSO NOT FOUND: G4DZU|22/10/2019 12:17:00|20m|SSB
13:22:18: Updating WA8MCD|22/10/2019 20:31:00|30m|FT8...
13:22:18: Saved QSO locator (EN72) appears valid (not country default EM19FA) but different from EQSL reported (en50mm). Keeping saved
13:22:18: QSO updated
13:22:18: Updating K1FT|22/10/2019 20:53:00|30m|FT8...
13:22:18: QSO updated
13:22:18: Updating PP5XA|22/10/2019 20:56:00|30m|FT8...
13:22:18: QSO updated
13:22:18: QSO NOT FOUND: G4DZU|23/10/2019 09:25:00|20m|SSB
13:22:18: Updating OK1WCF|23/10/2019 17:20:00|30m|FT8...
13:22:18: QSO updated
13:22:18: Updating EB5RR|23/10/2019 17:23:00|30m|FT8...
13:22:18: QSO updated
13:22:18: Updating EA5HRM|23/10/2019

[G4POP]

Looks like you did not select Last download and the received since date, its downloading everything since 2019

[G4DZU]

Thanks Terry,

I had selected Last Download & Received Since 4/4/2019

Have you any other thoughts please, I've been reading the manual and double checking things for hours

73s
Doug

[G4POP]

Once you have downloaded the full log you should have the since date set to the date of last download not sometime back in 2019

[G4DZU]

thanks Terry,

I certainly have problems with what day it is, buts its the first time I've not known what year it is!

that's cured it, I knew it would be operator error, I just couldn't see it

73s
Doug

[G4POP]

May not be operator error just keep an eye on that date when downloading the next time

[DF5WW]

Hello Doug,

you´re right, there is a mismatch from time to time. I have the same mostly if i download
more at one time a day. At LotW i do the same and all is fine there. I have told this to our
Skype group with different Screenshots and a logfile. Let´s see what happens.

Today my V2 for eQSL DL has setted down to 2019 2 times ....

[WS2K]

I have the same situation. Last download date for EQSL always reverts to 2019. With that date, I keep getting error messages from QSOs long past. If I force to 2020, those errors do not show up.

LOTW is always good.

[KI5IO]

I have the same situation. Last download date for EQSL always reverts to 2019. With that date, I keep getting error messages from QSOs long past. If I force to 2020, those errors do not show up.

LOTW is always good.

Joe,

What version of Log4OM V2 are you using? I'm pretty sure this issue has been resolved.

Go to: Help / About and the version number you have installed is noted there.

If you are not using the current Version 2.6.1.0 then you need to download and install this release.

You might find your issue has been resolved, but if it still persits please add updated information to this thread for support.

[WS2K]

Hi and thanks for the quick reply! I am running the latest version, 2.6.1.0. Do I need to delete some .ini file so that this version can overwrite with a fresh start?

Thanks again!
73
Joe WS2K