开云体育

Frequently when I run Sync LotW QSO's in DXK it will flag conflicts between what I have logged and what LotW says for US call sign CQ and ITU zones.? Almost all of the time when this happens the LotW is correct.? I usually take the time to fix the DXK log info.? ?I looked in the help files to try to find where DXK gets the CQ and ITU zones when logging when I don't enter them myself, but no joy.? Can someone explain this to me and is there a way to reduce these occurrences?

Tnx,

Dale AA1QD

+ DXKeeper comments below

Frequently when I run Sync LotW QSO's in DXK it will flag conflicts between what I have logged and what LotW says for US call sign CQ and ITU zones. Almost all of the time when this happens the LotW is correct. I usually take the time to fix the DXK log info. I looked in the help files to try to find where DXK gets the CQ and ITU zones when logging when I don't enter them myself, but no joy. Can someone explain this to me and is there a way to reduce these occurrences?

+ Possible sources:

1. an Override (if you've specified one)

2. previously-logged QSOs with the callsign (if you've configured DXKeeper to display previous QSOs with the callsign)

3. a Callbook (if you configured DXKeeper to query a callbook and populate newly logged QSOs with information from the callbook)

4. the USAP database (if you've installed it)

5. the DXCC database (if unambiguous)

+ Note that ops sometimes operate from locations from other than their "home QTH".

73,

Dave, AA6YQ