When downloading from lotw I get a message box saying 2 qso's were not found in your log.
When I look at the lotw_error.txt file, both the qso's there are in my log and one has been confirmed by lotw and eqsl and so marked in my log. The dates, times, mode and call match so I wonder what I have wrong in my log? Can anyone help please?
73 Graeme
Same thing here, must be bug inthe new version, only 1 for me though.
Tom K8WDX
I think there is something related fact that Lotw uses time format with seconds but unfortunately cqrlog uses only hours and minutes. If you have upload the specific qsos to Lotw using another program which uses seconds before, the cqrlog won't match qsl data from Lotw as the one qso. Please look up directly into file downloaded from Lotw and check the time field it it contain any seconds.
Darek SP2MKI
Hi Darek,
Thanks for your response. Copied below is the relevant data from the lotw download file and the lotw_error.txt file (which of course match). All the times end with 00 seconds as does every item in the lotw download so I don't think that is the problem. Also before the upgrade these qso's did not throw an error message and I have done many downloads since the qso's as one was back in 2006. I deleted the NH8S qso and manually entered it again but still the error message. Maybe you can spot the problem in the attached error and lotw messages.
73 Graeme ZL2APV
From lotw download
NH8S
40M
SSB
20120914
085900
Y
20130114
515
NH8
32
OC-200
AH48
SM2EKM
80M
SSB
20061226
091200
Y
20111119
284
14
18
KP05uw
From lotw_error.txt
QSO NOT FOUND in log
Call: NH8S
Band: 40M
Mode: SSB
QSO_date: 2012-09-14
Time_on: 085900
QSLR: Y
QSLRDate: 2013-01-14
CQZ: 32
ITUZ:
IOTA: OC-200
Grid: AH48
State:
County:
------------------------------------------------
QSO NOT FOUND in log
Call: SM2EKM
Band: 80M
Mode: SSB
QSO_date: 2006-12-26
Time_on: 091200
QSLR: Y
QSLRDate: 2011-11-19
CQZ: 14
ITUZ: 18
IOTA:
Grid: KP05uw
State:
County:
------------------------------------------------
I have the same problem after updating to 1.5.5 version.
Me to.
73! Pawel
Hi,
could you please send me the ADIF file from LoTW? Please look if all QSO has time also with seconds or not. I'll look at my files but maybe it's not the problem.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
It seems that seconds in the QSO time is not the problem. All QSO in ADIF from LoTW have seconds and it works.
When CQRLOG imports ADIF data from LoTW, it's trying to find related QSO according to QSODATE, MODE, BAND and CALLSIGN. So please look at your log if all these values are really correct (and the same).
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Hi, Peter when i check all rejected confirmation i found one dependencies.
Mode: JT65A
for example:
----
QSO NOT FOUND in log
Call: W3BI
Band: 40M
Mode: JT65A
QSO_date: 2012-01-17
Time_on: 001200
QSLR: Y
QSLRDate: 2012-06-08
CQZ: 5
ITUZ: 2
IOTA:
Grid: FN20en
State: PA
County: PA,LEHIGH
73! Pawel
In my log mode is JT65 (without A)
73! Pawel
I also had the same issue, now solved.
Previously JT65 would match to JT65A, no longer it seems.
Changed mine to JT65A and all's good.
73 Iain
Iain G4SGX
I also have the same issue. I have 131 Qso's not found in log. All of them are listed as JT65A in lotw_error, but are JT65 in CQRlog as imported from JT65-HF.
73 Shawn - AD4SB
I took Iain G4SGX's advice. I made a Group Edit on all of my JT65 contacts, and changed them all to JT65A. LoTW updated just fine with no errors.
73 Shawn AD4SB
OK Shawn, good solution tnx for description.
I think about this problem comes from the new version CQRLOG or LoTW?
73! Pawel
What I saw was
Creating a QSO labeled as JT65A for the mode was then flagged as an error by the export routine when I exported it to LOTW as a local file.
Then, when I imported a LOTW file, all the LOTW generated data showed the mode as JT65 - BUT - none of the JT65 data was accepted as a match to the log. Then, when I read the error report, the mode was listed as JT65A and NOT the JT65 (without the "A") that was in the original LOTW file.
I there somehow a translate in the mode column that is now an issue in the latest version?
Thanks for any suggestions.
Jobst
AC0LP
My import error has been corrected with the new version.
Thanks
Jobst
AC0LP
Recently I have an error as well. Three QSO's are in lotw_error.txt. When I compare them to my log I see different date and band respectively. There is also one QSO I never made.
I don't believe that, in my case, CQRlog messed up since even in my oldest backups the date and time are accurate and also LOTW confirmed. So, either LOTW or the other operators messed up.
I realize CQRlog does the matching instead of LOTW. In my Windows era DX-lab was my logger which used lotwreport.adi if I'm correct. This is a file that can be downloaded from the same LOTW site and contains the matching QSO's.
Not sure if this is any easier to use though.
73, Tjalling PA3GOS
Hi,
got this error from LOTW today:
-----------------
File was rejected with this error:
301 Moved Permanently
Moved Permanently
The document has moved here.
----------------
Seems like they put a 301 redirect.
Any idea where the lotw url is encoded in the software so we can change it if necessary.(ie if I get the same error from now on)
Iain
Iain G4SGX
##adi report from lotw, is html file with new URL, for download, true adi report..
--------------------------------------
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://lotw.arrl.org/lotwuser/lotwreport.adi?login=cx1fk&password=X...
<hr>
<address>Apache/2.0.53 (Fedora) Server at p1k.arrl.org Port 443</address>
</body></html>
Same error here. Below is the file I tried to upload. eQSL.cc is going fine and lotw downloads are OK apart from my mysterious error message which Petr and Darek are looking at.
73 Graeme ZL2APV
2.2.1
ADIF export from CQRLOG for Linux version 1.5.5
Copyright (C) 2013 by Petr, OK2CQR and Martin, OK1RR
Internet: http://www.cqrlog.com
20130515
0424
FO/KH0PR
CW
20M
14.04
599
599
20130515
0427
VA2WDQ
CW
20M
14.0226
599
589
Hi Graeme,
your lotw download problem should be already fixed.
It seems LoTW already changed the upload address. I'll fix it and new version will be released during this week or weekend.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Thanks Petr, you are the best!
Sorry about doing my previous post in filtered html and losing the angle braces.
73 Graeme ZL2APV
No problem Graeme.
Just strange thing happned to me. Today I made a few QSO and uploaded it LoTW without any problem. Also download almost worked. Program freezed because ADIF file didn't have <EOR> at the end of last QSO ...
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
1.5.6 is installed and working just great. All problems gone and a pleasure to use. I wonder how the failed to be at the end of the ADIF. Maybe there is still a little to do at lotw.
Many thanks and best wishes to all involved.
73 Graeme ZL2APV
73 Graeme
Ivalid adif header...yes is html file, with extension .adi
Hello,
Please read message on ARRL Lotw web site:
Apr 28, 2013: LoTW Offline Messages -- While you are using the LoTW webpages, if you see a message on a white screen that says LoTW is Offline, please just refresh the page and your desired page should come up. The problem is at HQ and staff is investigating. Sorry for the inconvenience.
I have checked my last dowloaded .adi file. It contains the html with exactly the message 'LoTW is Offline' The work around is in my case: simply press the dowload data from Lotw again. The second try was ssuccesful.
I think it is no Cqrlog problem. So be patient and wait for HQ staf find the resolution.
73 Darek SP2MKI
I saw the following posted on QRZ about a change to the ARRL download URL and how it is affecting HRD. Anyone see any problems in CQRlog? Could it be related to the other LoTW problems recently???
73,
Dave
K3DCW
<<<<<It appears that the ARRL changed the URL of the LoTW servers from p1k.arrl.org to lotw.arrl.org, but even after changing the URL in HRD's setup, LoTW uploads and downloads are still broken.
Anyone have a work-around for this? >>>>