Inconsistant mode selection from cluster spot

[n5tm]

I've been using the antique Logger32 software which is written in VB6. It works very well with the K3, however I've been hoping to find a program written in this century.

I'm experiencing the same issue with clicking the spots. It will change the freq the first time, then the mode the second time. I could probably live with this if you could tell me how to force the K3 mode to DATA, not USB on Digital spots. I've tried changing the Modulation Type in the bandplan_r2.xml to DATA, DATA-A, DIG_U, and nothing changes. Clicking on a spot in the defined digital band switches the radio to USB. Doesn't seem to matter if I'm using Omnirig or Hamlib.

The reason for needing this is that the K3 automatically switches to Line In instead of Mic in when you are in DATA mode vs USB mode.

I'm a software developer and very adept at C#, C++ and VB coding. Perhaps you can let me take a go at this issue.


Thank you,

Dan N5TM

[n5tm]

Ok, here's an observation and a work-around.
If you set the Omnirig poll = 100 and also time out = 100ms it works most of the time. You will get frequency change and mode change on the first double click.

So the work-around for the Digital mode:
1) Modify the K3.ini file in the Omnirig Rigs folder -
Since it is very unlikely that you would be clicking on an FM spot, change the mpFM command to MD6 instead of MD4.

2) Modify the dxcc291.xml file and the dxcc221.xml (changing the bandplan_r{1,2,3}.xml doesn't seem to do anything)::
For each digital band section, change the Modulation Type from USB to FM.

Dan n5tm

[NN7D]

Hi Dan,

You might find it interesting to read a previous discussion thread on how Log4OM and OmniRig handle mode selection when double clicking on a spot. It covers the existing limitation which OmniRig has regarding modes, specifically a generic "Digital" mode, and some possible ways for a better solution. viewtopic.php?f=11&t=2198

I hope this helps.

Doug - W7DRM

[IW3HMH]

By enabling the "debug mode" log, you can see each command sent to Omnirig.
Usually Log4Om sends "generic" freq and mode messages to Omnirig, that is able to switch the right function in the external rig.

The only think i can say it's to check the log, and see what kind of messages are provided to Omnirig. It's up to Omnirig send the correct message to the radio (or it's up to the radio to correctly read the request).
Log4OM is totally agnostic about the rig, it's simply sends commands to Omnirig that does the trick. No changes are made in Log4OM if you work with a FT897, a K3 or a IC7000