Downloaded eQSL entry before start date shows up in error log as not in CQRlog

2 posts / 0 new
Last post
WB0NRE
Downloaded eQSL entry before start date shows up in error log as not in CQRlog

Raspberry Pi 4 running Bullseye 32-bit
Cqrlog Ver:2.5.1 (001) Date:2021-01-24

I have over 1000 entries in eQSL, the vast majority of them from before I started using CQRlog in mid-February 2022.

When I download with the starting date set as 2022-02-15, I can successfully download any new QSLs; but I also get an annoying error message claiming that I have QSOs that are not in my log. When I check the eQSL_error.txt, the entries are clearly not after my CQRlog start date. And oddly enough they are both from the same call, but over a year apart.

Any thoughts?

Rich

oh1kh
Downloaded eQSL entry before start date shows up in error log as

HI Rich!

There has been bug fixes for eQSL download in Jan 27 and latest just few days ago Mar 9.
See: https://github.com/ok2cqr/cqrlog/commits/master
There click the "..." after subject texts to see more information.

Specially click "..." after these subjects to see explanations:
Mar 7 2022: Fix for LoTW/eQSL download ...
Jan 27 2022 : Fixes to eQSL and LoTW import ...

After the latest fixes you can ADIF import the errors_eQSL.adi (Note: name has changed) if you want so.
There can be qsos from time before you have used cqrlog, or maybe SWL eQSLs. After importing them you do not have those errors any more.
But be aware that importing them may effect to your DXCC status report if error file contains qso(s) (fake or not in cqrlog) that contain countries not worked.
Importing those error eQSLs does not cause uploading back to eQSL or LoTW (qsl sent flags are set to Y).

Does this help ?

--
Saku
OH1KH