Log4OM

I am chasing the DXCC band awards, and I find that the Log4OM Awards status view does not agree with my counts on the LoTW web site. In particular, compare the totals for 40m:
I have tracked down the discrepancy to two problems:

1. Two of my QSOs have been allocated to the wrong DXCC country. The awards status has allocated NL7XT to Alaska (DXCC=6), but LoTW allocates him to USA (DXCC=291). It has also allocated KH6M to Hawaii (DXCC=110), and similarly LoTW has allocated him to USA (DXCC=291). Looking at the QSO manager and qrz.com, they are both DXCC=291. So why does the Award status view count them as separate countries, and how do I correct it?

2. For two countries, Azebaijan and [Cueta & Melilla], I have paper QSL cards but no LoTW confirmation. The paper card have not yet been submitted to ARRL. Aren't these supposed to be included in the "confirmed" total, but not in the "validated" total? How can I correct this?

Thanks in advance.
Kevin, LX2KD, G4AZO

Re item 1

1. Did you check those calls in Clublog for the date and time you worked them?

2. Where did those QSO's originate, Import, FT8, direct QSO entry into Log4OM?

Re Item 2

1. Have you checked and edited the QSL confirmation status to show QSL received status to Y-Yes in Log4OM and then rebuilt the awards?

Hi Terry, and thank you for the reply. I have done some further investigation now, so here are the answers to your questions:

All these QSOs came from FT8. I use the WSJT-X program. I have set up Log4OM to monitor the file wsjtx_log.adi, and the QSO seem to get read correctly. It looks like the only location data in the .adi file is the callsign and the gridsquare. I guess that Log4OM uses the callsign prefix as a basis to deduce the DXCC entity. (Does it do that from an internal table, or by looking it up in QRZ.com?)

The interesting thing is that in the case of NL7XT (for example), if I look at the "Award Refs." tab, I see both DXCC@291 and DXCC@6. So it has counted the QSO as valid for both USA and for Alaska. Looking at NL7XT's web page on QRZ.com, I see is not in Alaska. So I have a workaround solution which is to delete the DXCC@6 reference from the QSO record. Same applies to the KH6M QSO.

Now, concerning the QSO that have been confirmed by card but not by LoTW, I would like those to be registered as DXCC "Confirmed" when I register that I have received the paper card, but not "Validated" until ARRL actually validates them. I have a workaround, which is to manually edit those QSOs back to "Confirmed", but I want to avoid doing that for every paper card I receive.

I have another question concerning DXCC "submitted" QSOs, but I shall put that on another thread.

Thanks in advance.

73, Kevin, LX2KD, G4AZO.

1. Why don't you use the UDP method of integration I describe in the user guide it has far more Che is than a basic ADIF scrape?

2. Download today s release and install it

3. When your updated do a full LOTW download in our QSO manager with a start date of your earliest qso in your log but make sure you check the download card confirmations box

4. Restart Log4OM and check your statistics again