For some reason and I don’t know why l32 is experiencing a run time error. It pops up when I try to load l32 up, The error is error 13 - type mismatch. Anyone have any ideas nothing has change

Bob; Thanks again for all your help. I did learn a lot about SDRs and logger 32 configuration. I looked at some other loggers to see if they might work. In the end, I made up my mind that if it was a

Chuck, OK I think. I had to Google FT-1000 IF tap. If it were me, I'd simply connect the SDR to an antenna using an SDR Tx/Rx switch (I have read reports they provide in the order of 90dB

Well, while that did fix the problem with the erratic frequency, it turns out that since I am using a "IF" tap from the Yaesu, Omni-Rig has to talk directly to the FT-1000mp or it doesn't get any RF

But wait, yesterday configuration was just a simple Yaesu on the CAT port and SDR connected to the Slave port. Because the messages to the SDR where incorrectly formatted, the SDR did not QSY

Well I've finally got it to work by connecting it backwards. I can't do it the way Rick does, I don't think he uses an if tap. I have one installed in the Yaesu, and SDR-console has to talk directly

I’m not sure what you mean Ian. I have never had a download with a wrong call picked up in bad adi, they don’t get sent... to the best of my knowledge... But these did 73 Pete G4RRM

I have had lotw reports sent to me and the Bad .Adi file says, "not in log" and sure enough the call is not in my log, not the details. Am I missing the point here? Ian Sent from my mobile phone

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