Or am I wrong? 73 Pete G4RRM Begin forwarded message:

But it doesn’t usually work like this.. you don’t get a qsl if details aren’t right, I’ve had instances of no matches, change a letter in call and it’s ok you get a qsl They have NEVER

I see it this way. Think of QSL cards. I can send you a QSL card even if I never contacted you. I just address it to your call saying we had a qso on such and such a date. You check your log and see

I’d really like to know for curiosity why LOTW offers a match when one of the Basic elements of a QSO (Callsign) is wrong? As I said below, I’ve had no matches before because of a wrong letter

Hi All Almost got to the bottom of the issue. I emailed the station in question and he kindly responded to my mail, via google translate (so a little bit sketchy), with a brief explanation of

I'll stick my nose in here to say: 1) I rarely see errors or bad matches with LOTW. Usually I can find the cause; and, 2) I like the repetition because I have more than one way to view new matches,

Pete, to put your mind at rest. I have just downloaded a new lotwreport 18th, which includes a couple of QSOs already matched in a previous file 17th, and those QSOs pop up in a BAD.ADI file that have

The other thing to do is go to the LoTW site and click on the "Your QSOs" tab. On the Select QSOs to list form enter either of the call signs causing the confusion into the "Call sign worked" box and

Well the bad adi calls are not in log to check, suspect the dates times match the call below, will check later. His other call OZ30EU in log already have lotw match for those. But why only flagged

Like David I regularly get errors resulting in BAD.ADI. Usually the errors are US counties and I just deleted the county info, save and rename the BAD ADI file and import it into L32 to synchronise

Terry Agreed, but bad adi states Not In Log... and they aren’t.. So why does it send them? As mike says I’ll mail arrl when home later 73 Pete G4RRM

David, I have over 200K downloads from LOTW and have never received a QSO that was not in my log. What is in the "BAD" file are QSO's that are in my log but the

Hi David Thanks, yes he’s not in log but how do I stop it downloading the info each time? There must be a way to delete or you’d get a bad adi everytime you update! 73 Pete G4RRM

I make many thousands of contest QSOs every year and a few guys thought they worked me but didn't. LOTW still sends me those when I ask for a report and they land up in the BAD file. I do look through

How about emailing the ARRL LoTW help desk. Regards, Mike VP8NO

Hi Dave Yes it’s something like that but I don’t get why LOTW is sending QSOs that aren’t a call sign match! I have OZ30 LOTW already for my Qs and OZ3O is not in my log. How do I stop those

Hi Pete, The only thing that looks obvious is the callsign. Is the problem that one is OZ "Three Oscar Echo Uniform" whilst the other is OZ "Three Zero Echo Uniform"? I have had a couple of 'busted'

Yes I realise the difference between O and 0 (zero) but why does LOTW / Logger download a call which is not in my log and can’t be a LOTW match? Am I missing the point guys? Surely no match = no

Hi, Pete, What I saw, ( OZ3OEU not in my log), BUT, OZ30EU is and I already have an LOTW match for them. O Z 3 O E U is different from O Z 0(Zero) E U,... Here is the dog,... Vesko LZ2JE

Hi Villi Thanks and I agree, but how do I stop them downloading each time? And out of interest WHY do they down load if no match? 73 Pete G4RRM