Version 2.10.0.0 - Double click on Bandmap not working - SOLVED

[F4HGU]

Hello,

I am a regular user of Log4om V2. I updated to version 2.10.0.0 this morning. I am always very reluctant to update anything when I am happy with the current version. But I had time and decided to do this update !

What a bad idea ! I am not able to double-click on the band-map any more to go to the rigth band, frequency, and mode.... It works somethimes, but most of the time it does'nt. The call is updated in the QSO window but the transceiver doesnt't go the the rigth place...

I have an FT1000MP with Omnirig. Everything was a pleasure before this update !

Any idea ?

73 Patrice F4HGU

[G4POP]

Please check the Omnirig polling interval, it should be set to 100

[F4HGU]

Here is the config:

omnirig.PNG (6.15 KiB) Viewed 4392 times

[G4POP]

Have you restarted the pc?

[F4HGU]

Yes. I also uninstalled LOG4OM + omnirig, then re-insall everything... Same behaviour...

[G4POP]

Have you tried setting log4om and Omnirig to Run as an administrator?

[F4HGU]

I did not try. I will run that test and let you know.

I have just moved back to version 2.9.0.0 to be sure the issue was not on my RIG or its interface. And it is rock stable in that version, it works like a charme !

So I would tend to an issue on the new release. I'll tell you aout running as admin in a few minutes.

[G4POP]

I did not try. I will run that test and let you know.

I have just moved back to version 2.9.0.0 to be sure the issue was not on my RIG or its interface. And it is rock stable in that version, it works like a charme !

So I would tend to an issue on the new release. I'll tell you aout running as admin in a few minutes.

I could agree with you except your the only user reporting this and 2.10 is being used by thousands of users

[F6FLU]

Salut Pat

what worries me in your omnirig settings :

For me DTR and RTS have to set "Low" not "High"
AND
You have the same value for the Polling interval and the Timeout Interval
For me the Timeout MUST be higher than the Polling ...
73

[F4HGU]

I am back in 2.10.0.0 and experiencing the issue again even running the app as admin.

I noticed that a mode change works. It's a frequency change in a given mode that doesn't work.