Thanks Jim,
After doing a more detailed search I discovered about half the errors were
due to a bad frequency in the Freq (khz) box and the other half were bad
calls. The bad calls were actually years of Armed Forces Day calls such as
WAR, AIR, NNVR, NMC, NBM, etc, etc. I log them the same as regular calls but
they don't match the normal callsign format so LOTW rejects them. No problem
there as I would guess the Armed Forces Day special stations don't use LOTW
so I will just ignore those errors.
The bad frequency errors came from a 2004 IOTA contest log when I used the
free ED5DI IOTA Contest logger program. I forgot if I used the ED5DI ADIF or
Cabrillo file to upload to DX4WIN (this was before your great ADIF to DXQ
program). What it did was to cut off the actual frequency. Example, instead
of 14250.0 it downloaded the freq as 14.250 and then after the import in the
DX4WIN Freq (khz) window it became 0.01425 and so the error. Since they were
all in one group I just scanned through each QSO and wiped out the Freq
(khz) box and left it blank. I then resubmitted those corrected only QSO's
to LOTW and this time they were accepted using just the BAND info.
Every day you learn something new!
I have now submitted 26,254 LOTW QSO's for K7ACZ with 12,394 QSL matches. I
know many DX stations don't use LOTW so I won't have a match. But what if I
messed up the time or freq and that is why there is no match? Is there an
easy way to determine if the DX did use LOTW but my QSO does not match his
info? I will continue further with your Compare DX4WIN DXCC Credit Status
with LoTW program but it does not appear to be able to help me with
mis-matched contacts.
I have another 40K or so from K6ACZ in Calif before 2003 but I know I need
another certificate for a different call. I won't worry about those older
QSO's before 2003.
Thanks for all the help!
73, Alan, K7ACZ
-Original Message-
From: jjreis...@gmail.com [mailto:jjreis...@gmail.com] On Behalf Of Jim
Reisert AD1C
Sent: Thursday, May 15, 2014 3:15 PM
To: k7...@cox.net
Cc: DX4WIN Group
Subject: Re: DX4WIN to LOTW
Alan, I think that's the best you can do. The program for signing/uploading
logs does compare the BAND against the FREQUENCY if both fields are present
in the ADIF file, and reports errors if they don't match, as you saw. In
your case, you'll have to assume BAND field is correct.
Are these from QSOs you logged in real time, or ones you imported? If the
QSOs were imported, and you have the original source, we can try to find out
how to fix them.
Also note that if you export your log to ADIF or DX4WIN8 format, then import
the resulting file into a new DX4WIN log, it will also help identify these
kinds of problems.
73 - Jim AD1C
On Thu, May 15, 2014 at 3:10 PM, ALAN ZACK k7acz wrote:
> I recently made a submission to LOTW using the instruction by Jim AD1C:
>
> WORKING WITH LOTW and DX4WIN
>
> I got many error messages tagged as ERROR: FREQUENCY 0.01431 (and
> other such freq notations) IS OUT OF RANGE FOR BAND 20M ON LINE
> xxx
>
> When I look up the QSO record on DX4WIN I see in the Freq (khz) box
> that I had entered 14.31. I suppose I meant to enter 14.310.0 but for
> whatever reason it shows 14.31. Others show 14.01 instead of 14.010.0,
> 14.19 instead of 14.190.0, etc. When the QSO record is converted to
> the ADIF file for the LOTW TQSL conversion it is changed to the 0.01431
notation.
>
> I printed out the list of errors and it appears I have about 100 of
> these error messages. It seems LOTW rejected the QSO's with these
> errors as when I am in the LOTW webpage YOUR LOGBOOK QSO's and search
> for these calls with error messages they do not show up even though on
> the page Here you can query Logbook to find out the last time log data
> was uploaded for a particular call sign the station in question did
> upload his QSO's to LOTW in the timeframe to be a match for me. So it
> appears I must go into DX4WIN, search for the calls showing this error
> message, correct or blank out the Freq (khz) box, and resubmit a corrected
file to LOTW.
>
> Is this correct? If so, is there an easier way of doing this other
> than doing 100 or so individual callsign searches for the offending
entries?
>
> What is interesting is that with many of my QSO entries I had left the
> Freq
> (khz) block blank but LOTW seems to have accepted those QSO's. I am
> guessing it just accepted the entries in the BAND box as the frequency.
--
Jim Reisert AD1C, , http://www.ad1c.us
__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
