Page 1 of 1

Strange CAT behaviour with K3s

Posted: 16 Feb 2021, 11:15
by dk2lo
I am now on the latest LOG4OM V2 release. It works fine but I experience strange CAT behaviour:

CAT from Cluster works only when mode changes. E. g. current mode is LSB and the wanted spot has different mode as USB, CW, FT8... I cannot get any changes when the mode stays the same, independent of band. I can only circumvent this by first going to a spot with different mode and then go back to the wanted spot.
On the band map it works better. I can change to a different spot with the same but need two attempts but at least it works.

I am on the last Omnirig Version 1.19 and running on direct Com-port. With LOG4OM V1.41 CAT works without any problems.

I tried already different settings for: CAT delay btween commands and polling intervall in Omnirig. But no success.

Any ideas are appreciated very much.

Re: Strange CAT behaviour with K3s

Posted: 16 Feb 2021, 12:14
by HB9BRJ
I vaguely remember that the sequence in which data is sent over CAT matters. In Program Configuration > Hardware Configuration > CAT interface, try the "Send MODE before FREQ to radio" option.

73, Markus HB9BRJ

Re: Strange CAT behaviour with K3s

Posted: 16 Feb 2021, 12:55
by dk2lo
Thank you Markus,

I tried this already but it did not solve the problem.

I saved all the settings from V1 which worked. There is in the CAT options "Special functions for Elecraft and others" with
1. Send FREQ before MODE (seems now the default)
2. Add delay between FREQ and MODE msg (missing in V2 but a general delay is now available and I tested several values - but unsuccessful)

Re: Strange CAT behaviour with K3s

Posted: 16 Feb 2021, 15:45
by dk2lo
Addendum:

CAT from Bandmap window works with double-clicks with spots with the same mode. Just the first try from Bandmap needs two double-clicks.

Till now no success for double-clicks from Cluster window with spots with the same mode testing several CAT-options.