Log4OM

Does someone have the fix for the Omnirig K3 (and KX3) file. When I double-click a CW spot, my KX3 is tuned to the correct frequency but the mode is CW-REV instead of CW. I have to manually switch it to CW normal from CW reverse.
I believe someone had mentioned how to edit the Omnirig file for the K3/KX3 to make it work correctly, but I can't find anything on it now.
73, AL - VE3RRD

Just edit the file by swapping the CW mode parameters

If you search the forum you will find files that I have posed for this in the past

Thanks Terry, I located the "Elecraft K3.ini" file in the "Afreet/OmniRig/Rigs" directory and opened it in Notepad++ for editing. Under "Set Mode" I swapped the two commands for pmCW_U and pmCW_L (MD7 and MD3).
Seems to have fixed my problem.
73, AL - VE3RRD

ve3rrd wrote:Thanks Terry, I located the "Elecraft K3.ini" file in the "Afreet/OmniRig/Rigs" directory and opened it in Notepad++ for editing. Under "Set Mode" I swapped the two commands for pmCW_U and pmCW_L (MD7 and MD3).
Seems to have fixed my problem.
73, AL - VE3RRD

That's all it takes - Easy Peasy

Just downloaded OmniRig and the latest RigIni.zip (date 2015-09-28).
The "Elecraft K3.ini" config file in the zip archive dates from 2012-01-09.

My experiments have shown that CW_U (MD3;) and CW_L (MD7;) are not only swapped in the "set mode" section, but also in the "read status" section (Flag9 and Flag13). After these corrections, CW and CW REV modes are correctly set and also identified by OmniRig.

Update after an email exchange with Alex VE3NEA:
With the K3, CW is LSB and CW-REV is USB. Never realized this before. So the provided INI file seems to be OK. Please apologize my "false alarm".

So far I used hamlib with Log4OM because the log in the Omni-Rig Client shows these 2 lines about every 5 seconds:

Status: Rig is not responding
Status: On-line

Any ideas?

Markus HB9BRJ

What is your polling interval with omnirig?

IW3HMH wrote:What is your polling interval with omnirig?

Default values: 500ms polling, 4s timeout. When running Log4OM with OmniRig the "Cat status" indicator remains green all the time, so I guess these are sporadic hickups which do not have an impact on the function.
Some time ago you encouraged users to use OmniRig. Therefore I gave it another try. Looks like I will stay with OmniRig...

73, Markus

reduce polling rate to 100 ms

G4POP wrote:reduce polling rate to 100 ms

Changed polling rate and counted how many times the "rig not responding" message appeared in the event log during a 1-minute interval:

• 100ms: 13 times
  500ms: 3 times
  1000ms: 4 times

Since the CAT functionality in Log4Om seems not to be suffering from these hiccups, I will stay with 500ms and simply ignore these event log messages shown by the Omni-Rig testing client.

73, Markus

HB9BRJ wrote:

G4POP wrote:reduce polling rate to 100 ms

Changed polling rate and counted how many times the "rig not responding" message appeared in the event log during a 1-minute interval:

• 100ms: 13 times
  500ms: 3 times
  1000ms: 4 times

Since the CAT functionality in Log4Om seems not to be suffering from these hiccups, I will stay with 500ms and simply ignore these event log messages shown by the Omni-Rig testing client.

73, Markus

Marcus

What version of Log4OM are you using?

Why are you watching the log file is the CAT control not working correctly?