Lag time after clicking spot

[VE3CT]

Hello,

I am new to Log4OM. I have everything working. However, I cannot understand why it takes from 10 sec to over 20 sec after double clicking a cluster spot before Log4OM changes frequency and display. My PC is very fast running Win 10 Pro with a Ryzen 5 3600 CPU and 16 GB of high speed memory and CPU running on average less than 5%. With N1MM or Logger32 the same process is instantaneous.

What am I missing?

Thanks for any hints,
Art - VE3CT / W1AJT

[G4POP]

Which version of Log4OM are you using? actual release number please - Not 'its the latest'

[VE3CT]

Hi Terry,

It's version 2.26.

Art

[VE3CT]

To refine the problem the issue is that the callsign populates immediately but the frequency display sometimes never changes although the rig changes frequency. Every indicator is green CAT, Winkey, cluster. I ma using Omnirig v2.1.

[G4POP]

To refine the problem the issue is that the callsign populates immediately but the frequency display sometimes never changes although the rig changes frequency. Every indicator is green CAT, Winkey, cluster. I ma using Omnirig v2.1.

First please revert to the original Omnirig by Alex its version 1.2, the Swiss one has issues

Also update Log4OM to Beta 2.26.0.3

What radio do you use and what connection to your PC (USB, Interface to ACC or what)

[VE3CT]

Hello Terry,

I backed up my log and downloaded the beta version 2.26.0.3 along with Omnirig v1.2. Install no problem. All previous settings and log automatically migrated to beta version.

Lag time between double-click spot and transceiver (K3) frequency change plus L4 callsign box population average 3 seconds with an average of a total of 6 seconds to change the frequency display of L4.

Thanks for trying,
Art

[G4POP]

Art
Email me so that I can get to the bottom of this

g4pop (AT) arrl.net