www.dl2rum.de

I have about 11 QSOs out of 165 that show confirmed in LOTW but not in RUMlog. I tried forcing a download again but they stay at S.

I can't see any rhyme or reason why this would happen. Are there any known problems in this area?

Thanks
Ken

When you do a full download (reset the date in the LoTW preferences), not recognized QSOS in the log should be alerted.

I tired that. No love. I found the problem because LOTW said I was eligible for DXCC phone but RUMlog had me at 95 confirmed. I have been resetting the QSOs to X by by hand but still can't find a pattern.

Just a thought - maybe others could double check their confirmed list with LOTW and see if there are any differences??

Do you have ex callsigns?

No. Not with lotw.

When reading the LoTW data, RUMlog shows clearly how many QSO recodes were read and how many weren't recognized.
You should be able to find out if the missing QSOs are (1.) not downloaded or (2.) not found in your log (shown in red).

This is what it looks like before I did a reload from LOTW During the reload I get this error after the reload it looks like this - note one less confirmed. but LOTW still says 116 Maybe I am misunderstanding something in how this all works but I would think the LOTW count and RUMlog counts would match. Initially it was off by more than 3. I went in and edited by hand to get this close.

Thinking that it might be the DXCC file I used the new application to do an update. No change.

Thanks for considering all of this.

The problem with K2V could point you in the correct direction. Do have got more messages like this? Follow the tip and enter the irregular call sign K2V into your dxcc.rsd database under the calls tab using the application 'EditDXCC'. See the documentations. When you have made the changes restart RUMlog and select Menu-->File-->Recount DXCCs

The K2V problem seemed to be self healing and never occurs again. It was the only error message.

I forced the recount and the DXCC count is now 112.