Log4OM

but if you give us references to be downloaded and some info on the award (like a website) we can do that easily

Your QSO frequency is 7.300, that is out of band in IARU Region 1, according to your callsign this QSO should not have been made. If you set IARU REGION 2 or 3, where bandplan covers through 7.3MHz the application will correctly load the QSO's [IMPORT ADIF FORM] Begin ADIF import task TM17FFF|06/10/...

There is a clublog callsign exception that works in that case, as shown in the last screen.
Is your clublog database updated?

Your config seems ok, but the application is not able to find those QSO's in your log.
Can you get the ADIF of one or two contacts in the SOTA list and post it here, so i can load both file and adif and check?

Is the "cluster throttling" message displayed on cluster screen (bottom area)? While throttling is enabled, the map is not updated to avoid stressing the system with several graphics updates on the background (until i'll move to DirectX...) if a skimmer is in use this is a common scenario....

something optimized too much...

I'll add them back soon

Done in next alpha/beta/release

Log4Om downloads LOTW data for LOTW handled QSO, including credited paper QSO's if any this option is enabled through a flag in the lotw download page and goes to this URL: https://lotw.arrl.org/lotwuser/logbook/qslcards.php Unfortunately there is not a login parameter, so the user must enter on LoT...

I'm investigating on those issues. It seems happens only when releasing a major version, but our internal alpha testings are using exactly the same release process as the main release...

Search found 2469 matches

Re: request for new award database

Re: Can't import adif from HamLog

Re: Callsign Mapping

Re: Unexpected Date Format

Re: Cluster Map not showing spotted station

Re: Cluster Map not showing spotted station

Re: SHA-256 hashes?

Re: Alerts - Removing a Callsign

Re: Retrieve CREDITED QSL's

Re: automatic upload settings not working