Log4OM

G4POP wrote:

w8msp wrote:

G4POP wrote:What interfaces between the computer and the radio are you two guys using?

And what version of Windows

I am using the Log4OM CAT with this parameter
--model=229 --rig-file=COM5 --serial-speed=38400 --port=4532 --set-conf=stop_bits=2,dtr_state=ON,rts_state=ON --ptt-file=COM5 --ptt-type=RIG -v

The K3S USB cable to the PC which is running
Windows 10 Home Version 1607 OS Build 14393.85
Intel i-3 3240 CPU @ 3.4 GHz with 8 Gig Ram

Please change to Omnirig in Log4OM not the Hamlib that you are currently using

OK I will make the change tonight when I get home.

Thanks

Les

The excellent K3 Config utility http://nf4l.com/k3c/ by Mike NF4L reads 236 (all?) K3(S) parameters and allows an easy comparison between 2 captured states.

Run it once before using Log4OM, run it again after the problem occurred.

Markus HB9BRJ

HB9BRJ wrote:The excellent K3 Config utility http://nf4l.com/k3c/ by Mike NF4L reads 236 (all?) K3(S) parameters and allows an easy comparison between 2 captured states.

Run it once before using Log4OM, run it again after the problem occurred.

Markus HB9BRJ

Markus,

Send you an e-mail with the DTA and TXT files from my K3 with "before" and "after" running Log4OM. Some changes noted, but I'm not sure quite what to make of them.

When I started the K3 Utility for the readings after closing Log4OM the audio came back up immediately just as if I had slightly touched either the Shift or Width knobs or the XFIL key.

I'm still trying to decipher the log information gathered from my K3 via the routine that Markus advised me of. BTW - He is on a SOTA trec at present.

In continued 'testing' of Log4OM and my K3 it appears to be a "hit and miss" hiccup. Sometimes (almost quite consistently and repeatable) the 'audio' will close down when Log4OM shuts down.

I've tried changing bands, modes mostly via the Cluster (I connect with ve7cc.net:23) and sometimes it will not shut down the audio when I disconnect the cluster, but that just doesn't stick in all cases.

I've tried the Super Cluster and it is also hit and miss there as well.

A few times when I've shut down Log4OM and the audio closes down/off I'll just leave it and then reload Log4OM and the minute it starts up and the cluster re-engages the audio comes back up.

So ... I've not been able to lock onto a 'solid' failure that is even close to 100% consistent.

When the audio drops one can bring it back up with a very "slight" touch to the Shift of Width knobs or the XFIL key on the K3 ... I'm sure the K3S has a similar response.

I'm using a USB connection between the rig and my PC as I do have the upgraded I/O board on my K3 and no longer have to use the 'serial' connection between the two.

I've done a lot of testing and have had some great offline support from Markus in Switzerland.

We're both still scratching our heads on this one.

I've sent a technical support message to Elecraft in California and have a bunch of data for them to look at to maybe help resolve.

It may still be something I have in my setup (as minimal as it is), but just have not "nailed it" to get the solution.

For the short term I've reconnected my laptop to the K3 via the Serial port (now an RJ style jack) and (so far) the audio has NOT reduced or shut down when turning off Log4OM.

Still some weird anomaly (it appears) with the USB connectivity.

More to come as I continue to dig and learn more.

"Audio Drops" when Log4OM shuts down ... UPDATE.

Well, no solid results for resolution as of this writing. Elecraft tech support has suggested several items and I've tried them all without any "for sure" results.

I've used both serial and USB port connections and get the same "audio drop" when I shut down Log4OM.

What is frustrating is that it is not consistent. The problem did not occur for almost two days with 4-6 operating hours each day and I purposely shut Log4OM off several times to see what would happen. I was feeling good and somewhat optimistic.

Then last evening with a 4-hour operating span the "audio drop" came back to haunt me when I turned off Log4OM.

Basic "audio drop" is almost as if the bandwidth control has been turned down to zero. Adjusting bandwidth controls (shift/width) bring the audio back up without fail.

Thanks to Markus in CH for also helping me trouble-shoot.

It is not a huge deal so will certainly keep trying different things and see if I can land upon an answer or find what I might have done with my system to cause such to occur. Doing a reset on my K3 might also be one step. I might have some weird setting that is acting out of whack.

I have narrowed the 'dropped audio' problem with the K3 and Log4OM to what appears to be a hiccup with the Elecraft firmware updates (MCU 5.50 and DSP 2.87) that were made available on 05/17/16.

I loaded those updates to my K3 on 07/26/16 and that is when I started seeing the "intermittent" drop of audio when shutting down Log4OM.

Les' details in the OP gave me the clue that something was/is up.

Yesterday I restored firmware Versions MCU 5.38 and DSP 2.86 ... that that change the audio has not dropped off once.

I've sent a message again to Elecraft support so will wait to see what the next suggestions may be.

Log4om doesn't interact with your rig in any way.
It sends his requests to Hamlib/Omnirig, that filters the commands, decide what to do, and send the command to the rig.

On closure, Log4OM is sending a "shutdown command" to hamlib. This *could* produce some kind of effects on hamlib side.

Try starting Log4OM in TRACE mode. This will produce a detailed log of EACH command Log4OM sends to the CAT system.
Here you can find "unwanted" messages.

Filter messages are NOT supported by Log4OM, so Log4OM will not send commands that can change filter settings to your rig.
Anyway, the log of sent commands is reported in the program log (trace mode enabled)

One of owners/engineer at Elecraft sent me a beta release of the firmware for the K3 and I've been testing it with excellent results. Issue appears to have been handled with whatever changes might have been made in this beta version of firmware for the K3 and K3S.

Great news