Log4OM

Terry,

I'm using Log4OM 1.23.0.0. One year ago when I started using Log4OM, I didn't succeed to make OmniRig work so I went with Hamlib. After having seen discussions here encouraging users to use OmniRig I took a fresh approach. In order to familiarize with OmniRig I followed VE3NEA's "OmniRig Tester's Guide". It describes how to use the Client.exe program available in the OmniRig program folder.

The Client.exe GUI includes an event log of the communication between OmniRig and the TRX. It was in this event log where I discovered sporadic "Rig is not responding" entries. The frequency at which these entries occur depends on the polling rate (see my earlier post). However they don't seem to affect the CAT functionality of Log4OM in any way, except maybe a short delay while such a hiccup is occurring on the interface.

73, Markus

HB9BRJ wrote:Terry,

I'm using Log4OM 1.23.0.0. One year ago when I started using Log4OM, I didn't succeed to make OmniRig work so I went with Hamlib. After having seen discussions here encouraging users to use OmniRig I took a fresh approach. In order to familiarize with OmniRig I followed VE3NEA's "OmniRig Tester's Guide". It describes how to use the Client.exe program available in the OmniRig program folder.

The Client.exe GUI includes an event log of the communication between OmniRig and the TRX. It was in this event log where I discovered sporadic "Rig is not responding" entries. The frequency at which these entries occur depends on the polling rate (see my earlier post). However they don't seem to affect the CAT functionality of Log4OM in any way, except maybe a short delay while such a hiccup is occurring on the interface.

73, Markus

Marcus,
What you are seeing in the client software is the response report for rig 2 because you only have one radio connected, just ignore this if everything works as it should with the connected radio all is OK

And yes these responses are directly geared to the polling rate so the more frequently the radio is polled (Interrogated) the more of these reports will be displayed

Your worrying about nothing

HB9BRJ wrote: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

Markus,

I'm still curious as to why Log4OM doesn't default a Cluster Spot (double click) to the CW - Normal as opposed to CW-REV?

I've used another logging program for 8+ years and it never set the CW mode to CW-REV.

KI5IO wrote:

HB9BRJ wrote: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

Markus,

I'm still curious as to why Log4OM doesn't default a Cluster Spot (double click) to the CW - Normal as opposed to CW-REV?

I've used another logging program for 8+ years and it never set the CW mode to CW-REV.

Because unlike Alex at Omnirig who conformed to the K3 command structure other software did not

However its a really easy fix to edit the K3.ini for Omnirig so that it conforms to normal CW practice

G4POP wrote:

KI5IO wrote:

HB9BRJ wrote: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

Markus,

I'm still curious as to why Log4OM doesn't default a Cluster Spot (double click) to the CW - Normal as opposed to CW-REV?

I've used another logging program for 8+ years and it never set the CW mode to CW-REV.

Because unlike Alex at Omnirig who conformed to the K3 command structure other software did not

However its a really easy fix to edit the K3.ini for Omnirig so that it conforms to normal CW practice

Terry,

Thanks for further clarification about following the basic command structure. With your support and that of Doug and Markus I've modified the Elecraft K3.ini file.

Just been working to get my gray matter wrapped around seeing the CW and CW-REV.

FYI - I'm going through a list of testing various apps as well as the beta with suggestions from Doug. Working on a list of observations.

Log4OM is not able to deal in detail with the rig. It simply ask Omnirig to switch to CW... and Omnirig does the trick.

Having trouble with the omirig and my k3 and downloaded new omirig and rigini files and still don't work. see terry says look for old post to edit file and not sure what to type for it to come up, couldn't find. using windows 10. so was hoping could get more help, THANKS...

Having trouble with the omirig

What sort of trouble?

1. You cant connect to the radio
2. You connect but the connection drops out
3. You connect but the frequency does not change when clicking a cluster spot
4. You connect but Log4OM does not follow and changed made manually on the radio
5. You can synchronise other software with Omnirig and Log4OM
6. Another CAT issue not mentioned above?

everything connects ok. but having the same issue of not putting the k3 into the right mode. and its happening to ssb lsb/usb as well as cw/cwr.

Have you set the polling rate in Omnirig to 100 yet