Hello,
I have an odd issue that I haven't noticed before.
I am running CQRLOG 2.5.2 (001)
TQSL is 2.5.9.
I was in the RTTY contest last weekend. I worked a particular call on 3 bands (20M,40M and 80M)
After downloading from LOTW, only the 20M contact shows confirmed.
When I log on to the LOTW site, all 3 bands show confirmed for that callsign.
I looked at the lotw_error.txt file and for the 40M and 80M contacts (based on time and date) show the band as blank.
Who generates this lotw_error.txt ?
I did goto Preferences -> Bands -> Frequencies to make sure that was set correctly.
RTTY: (f>RTTY and f<=SSB) is true for 20M, 40m and 80M.
I did notice that on some other calls on 40M and 80M did have EQSL confirmations. Again I checked the LOTW site for these and they do show confirmed.
I was able to download a report from LOTW. I found one of the non-confirmed contacts.
Here are a couple of the fields that look important. I am not sure which ones CQRLOG is looking at.
BAND:3 80M
QSL_RCVD:1 Y
APP_LoTW_2xQSL:1 Y
I could use some guidance on how to troubleshoot this issue.
Thanks, Dave
Hi Dave!
Could you compare your lotw-error file against your downloaded lotw adif file, please.
You will find all lotw files that cqrlog has up- or downloaded from ~/.config/cqrlog/lotw folder.
File names include date and time and are ending ".adi"" Downloaded files do not have equally named "child" files with ".tq8" (those are uploaded files)
Open corresponding download file with text editor and compare it to your error file. Are the bands ok in downloaded adi file there?
If the band is ok in downloaded adi file, but it also exist in lotw_error file without band info please send both files to me for check. You find my email from qrz or Hamqth.
If the band is missing from downloaded adi file it certainly will cause error and end to error file.
--
Saku
OH1KH
Hello Saku!
I just emailed the files. I forgot to mention in the email that I just ran the report from 2022-01-01 to keep it small.
Thanks, Dave
Another thing !
>"I did goto Preferences -> Bands -> Frequencies to make sure that was set correctly. RTTY: (f>RTTY and f<=SSB) is true for 20M, 40m and 80M."
Did you also check 80m and 40m band "start" and "end" ?
They are by Region1 as default.
This should not matter with lotw import as there only band is given, not frequency that could go over band start and end limits.
And RTTY frequencies at 80 and 40m are same in both regions, I think.
--
Saku
OH1KH
I did have that problem many many years ago but I thought we had fixed it back then.
I attached (I hope) a screen snapshot of what I have for those values.
Thanks,
Dave
File:
Hello,
I was wondering if you had a chance to look at this issue. I am up to about 6000 QSOs that show up in this error file. Most of them are because of this "Mode" issue.
Thanks, Dave
Hi Dave!
I have not received any mail from you!
Did you zip files? Otherwise plain text file may be too big, or captured by some spam filter between.
Please try once again and zip all files together.
Actually bands/frequencies band start and end are important ones. They cause errors to adif import.
As far as I have looked at source code the mode limits are used only for setting proper mode to rig when double click on DX spot or bandmap callsign.
--
Saku
OH1KH
Hello Saku,
Oh no. I had sent them the same day we discussed this. I will look for the files and try again!
Thanks, Dave
Saku,
I just resent it. The file was gzipped. I sent in on 24-JAN2022.
It is coming from my yahoo account, that "could" be a problem?
Thanks, Dave