[Elecraft] Elecraft - K3 - FW 5.5 issue ..

[Nolan Kienitz]

FWIW the BETA 5.54 appears to have resolved an issue some of us were having with our K3 (with the KIO3B Interface Option installed) and the K3S with the KIO3B as a standard part of the rig.

 

In that … a logging program (Log4OM) when shutting down would drop the audio on the K3 and K3S to nil.  A slight touch of the shift or width knob or the XFIL key would restore the audio.  I had posted about this issue on this reflector a while back with no replies.

 

Reverting back to FW 5.33 or 5.38 would seem to resolve the issue.  FW 5.50 and up seemed to introduce the problem.

 

I tested with two different computers and reloaded the logging s/w, replaced cables and more all to no avail.

 

Granted a logging program shutting down audio on a rig is small potatoes among many of the issues I read and learn about here and everyone’s operations, but it still was a valid problem.  I’m glad it appears that the Beta 5.54 has possible cured my (and a number of others) hiccup.

 

I know the great folks at Elecraft will get the bugs worked out … sometimes it just takes additional steps and time.

 

73,

                Nolan Kienitz  KI5IO

                SKCC - 9532C

                NAQCC - 6230

                FISTS - 14948

 

 

Message: 25

Date: Sat, 1 Oct 2016 11:57:54 -0500

From: "Jim McDonald" <jim at n7us.net>

To: "'Elecraft Reflector'" <elecraft at mailman.qth.net>

Subject: Re: [Elecraft] [K3] FW 5.5 issue??

Message-ID: <008c01d21c04$f4cb0b40$de6121c0$@n7us.net>

Content-Type: text/plain;            charset="utf-8"

 

I installed the newest K3 firmware, 5.54, reset DXLab, MMTTY, and the K3 to 2125 and still get the 850 Hz error when transferring a spot from SpotCollector to the radio.

 

I changed all back to low tones, 1225/1445, and get the same error.

 

Tony, K4QE, reported that he had the problem until he reverted back to K3 firmware release, 5.38, so the firmware must be the problem.

 

I need the newer firmware for my K-Pod, so I'll live with the apparent defect RTTY in 5.54 until it's resolved.

 

73, Jim N7US