Steve,

Did you not have a Yellow Triangle on the Main UI? Left clicking on that triangle will show you updates and data files that have been updated (IE: SOTA, IOTA, etc.)

Check out Users Guide on Page 30 as well.

Wolfgang,

That is picking up the ADIF feed from WSJT-x and filling in the last QSO you had via that APP.

w9mdb wrote: ↑

22 Jan 2020, 20:12

Yup...had the older version....Seems that V2 doesn't check for updates?

Mike,

Yes it does. I noted the Yellow Triangle in the post above and you can check the Users Guide on Page 30.

No F10 tab to be seen... I removed the Roaming\LOGOM2 folder and still no F10 tab. What determines the presence of the F10 tab? Untitled.png Mike, Then you need to update your V2 installation. You must still be running the very first release we did last week. F10 Tab was added at input from users o...

Frankie, Are you logging into the same cluster from the two separate machines? If you are you should use an SSID identifier with your cluster logins. Reason being as that some clusters will fuss at you when using the same login from two different machines. In my case I will use: KI5IO-0, KI5IO-1, KI...

Mike, When you select View/Worked Before it will be empty. Then you can enter call sign in to populate. That is by design as that stand-a-lone Worked Before Window can also work with Contest and other features. Also ... on your Main UI there are five tabs ... the last tab is: Worked Before (F10) It ...

Hi Daniele, Bug with the filling of the dropdown list for the awards. How to reproduce: - Select a callsign from the cluster by clicking once - Go to F3 - Select an award In the dropdown list it can be populated 2, 3 or 4 times Thanks Greg, UPDATE: Has been fixed and will be in next release.

Mike,

On the Main UI simply click on the Worked Before (F10) Tab.

There is also a separate window you can open at: View/Worked Before

Tom,

It could also be that you have enable reading an ADIF file from WSJT-x or JTAlert.

That will also cause the double-logging.

When you get the prompt to save the QSO (if you use that option) do you then get an error or warning message indicating that JTAlert can't confirm being able to log to the Log4OM2 SQLite file? And then a moment or two later the QSO does appear in the F7 Recent QSOs Tab. Log4OM V2 is slower in writi...