Hi Terry
The N1MM integration is great. Makes life easier than importing.

One thing I noticed, which I hope you may have an answer/solution to....

The QSO END time doesn't populate for me.....it never did when importing either.
Is this "as is" or have I missed something?

Is there a way, or might it be a possible consideration, that the cluster can be configured for multilpe sources. ie, only showing the SOTA spots and RDA spots as reported on their sights. I acknowledge there is a way to have an expression to show these...but this relies on stations making the spot ...

re-download of the db cured it

Uploaded the latest version this morning.
Entered in AN1WHC who are on EU-080 but nothing shows in the IOTA dropdown for me

yes, I am a subscriber.

this morning I exchanged with 4U24OCT....JJ00BK was populated in the grid field but his correct grid according to QRZ is JN80XP

strange!

I checked the QRZ API (but I don't auto upload anyway) and the usename/pwd in setting 1 section...all are correct.
So I am not too sure what else to look at as this continues to intermittently occur.

Hi terry,
Today I exchanged with 5A1AL ....according to the Log4OM he was in grid JJ00BH...but according to QRZ he is in JM62ov

Hi, Where does the program get the locator from? I have noticed recently that the wrong locator appears in the QSO details window (the one where you can review or edit etc). It puts in the JJ00AA square. When i check in QRZ.com, the locator shows, what I expect to be, the correct locator one. curiou...

It appears the band/mode switching issue K3 owners experience has been resolved (at least I have not had it since clicking the two extra functions in the setup). Are other K3 users seeing this?

Hi terry, yes I have the updates set to auto but also did an individual update....and on both counts, I don't see the RDA in the dropdown but I think I might have resolved my issue... The original country for the station is Asiatic Russia and the RDA will therefore be incorrect. Seeing as I couldn't...