k3 CAT

[EA7LL]

Hi, I have a problem with the CAT of my Elecraft K3, I use Omnirig with the following parameters: Baud rate: 38.400; Data bits: 8; Parity: None; Stop bits: 1; RTS: Handshake; DTR: Low; Poll: 200ms; Timeout: 4000
Everything seems to be ok, I can use others logging program's CAT without problem but if I try to use the CAT of Log4OM, the K3 is immediately keyed with a tone and I have to turn off the transeiver and delete the omnirig configuration otherways if I turn on the K3 it get keyed again.

Any clue of what I am doing wrong?

[KI5IO]

Hi, I have a problem with the CAT of my Elecraft K3, I use Omnirig with the following parameters: Baud rate: 38.400; Data bits: 8; Parity: None; Stop bits: 1; RTS: Handshake; DTR: Low; Poll: 200ms; Timeout: 4000
Everything seems to be ok, I can use others logging program's CAT without problem but if I try to use the CAT of Log4OM, the K3 is immediately keyed with a tone and I have to turn off the transeiver and delete the omnirig configuration otherways if I turn on the K3 it get keyed again.

Any clue of what I am doing wrong?

Manolo,

I also use OmniRig with my K3 (not K3S) ... a "mature" rig as I call it
Below is a screen clip of my OmniRig settings. Make sure you are using the most recent OmniRig V1.19 as well as the most current rig 'ini' files.

I've never had any problems with OmniRig and my K3 save for some CW reverse settings I had to adjust in the 'ini' file, but that was many years ago and has since been resolved. I've never been able to get HamLib to function on my K3 so I gave up trying for that CAT s/w a long time ago.

With your current situation are you running just Log4OM V2 and your K3? Or are you also running additional APPs connected to Log4OM V2 such as WSJTx or JTDX and/or JTAlert? Also, what version of Log4OM V2 are you running? Make sure you have installed the most recent release.

If you are running the other digital APPs at the same time as Log4OM V2 and OmniRig you will have to run them all with Administrative or elevated privileges as OmniRig requires that for the multi-threading function used when all those APPs seek to use the OmniRig CAT features.

But ... first let's just run Log4OM V2 and the K3 and get the basics ironed out.

[EA7LL]

Thank you Nolan,

I have tried the Omnirig settings you use without success. I don't have any other App running with Log4OM
Log4OM version 2.4.0.0
Omni-rig versión 1.19 with nost recents"ini" files

Log4Om CAt shows the frecuencies (VFO A & B) correctly but as soon as I connect the CAT the k3 get keyed

Manolo ea7ll

[KI5IO]

Thank you Nolan,

I have tried the Omnirig settings you use without success. I don't have any other App running with Log4OM
Log4OM version 2.4.0.0
Omni-rig versión 1.19 with nost recents"ini" files

Log4Om CAt shows the frecuencies (VFO A & B) correctly but as soon as I connect the CAT the k3 get keyed

Manolo ea7ll

Manolo,

Now you have me scratching my head. I've quickly looked in my K3 Users Manual and will next go through the Fred Cady book for K3 and see if anything pops up.

Have you turned on the PTT key in Log4OM V2? That is on the Configuration / CAT interface page and on the somewhat upper right side of that page.

What type of line are you using between your PC and the K3? USB to USB into the KIO3B board in your K3? Assuming you may have upgraded to the KIO3B module. Or a USB to Serial cable to the K3? If so, what chipset is in that USB to Serial Cable/Connector?

Have you run the Elecraft K3 Utility to do some tests from your PC to the K3?

Do you have the most recent firmware on the K3?

[KI5IO]

Manolo,

One thing to at least also try would be to ensure that you have PTT-Key turned off in the K3 Config Menu. At least you can turn it off and "try".

From the Cady K3 Manual: PTT-KEY Config Menu / Turn to PTT-KEY and then select OFF-OFF.

Save and then try again from Log4OM V2. Personally I would restart the K3 (I don't believe that is necessary, but can't hurt) and then try to enable CAT.