[Elecraft] [Elecraft-K4] K4 AT tune problems with KAT500 firmware 213

[Dave New, N8SBE]

Bob,

Yeah, I flashed to 2.13 from 1.75 this weekend, and at first things 
seemed to be OK, but last night when running the 80M SSB net, I kept 
having the tuning change unexpectedly and my KPA500 kept faulting out.  
This was the issue I was seeing on 2.05, which caused me to move back to 
1.75 several months ago.  I had not had any recent issues on 80M until 
re-flashing to 2.13.  It got so bad, that at some point, the K4D stopped 
putting out ANY power, and I had to re-boot the K4D to get my power 
back.  I don't use the TUNE LP, but rather hit the TUNE button on the 
KAT500, then tap TUNE on the K4D to start the tuning cycle.  The K4D ATU 
is bypassed.

No, I haven't erased all my KAT5000 tune memories - that would entail a 
lengthy re-learning process that I was not keen to do, yet.

There is definitely a change in tuning behavior going from 1.75 to 2.13, 
and at least for me, it's definitely NOT an improvement.

73,

-- Dave, N8SBE

On 2023-09-25 00:05, Bob Wilson - N6TV wrote:

> Are you holding down TUNE LP for the entire tune cycle, waiting for a 
> match?  That's not how it works.
> 
> Also, did you try clearing tuner memories as I previously suggested?  
> Or using a dummy load?  It may help since the tuner may start the 
> search at a poor match solution from memory.
> 
> Does the same problem happen if you use CW mode or FSK mode to produce 
> a carrier (tap XMIT in FSK)?
> 
> If so, and if the K4 ATU bypassed, it sounds like you have found a new 
> bug in the new KAT500 firmware that cannot be resolved by posting to 
> this group.
> 
> Anyone else here using KAT500 Beta firmware 2.13?  Do you see the same 
> problem?
> 
> Please report all the details to Elecraft support.  They may ask for a 
> log trace if the KAT500 supports that.
> 
> Good luck.
> 
> 73,
> Bob, N6TV
> 
> On Sun, Sep 24, 2023, 8:48 PM Dave Barnes - WB4KDI <wb4kdi at arrl.net> 
> wrote:
> 
>> Bob the KAT500 tuner works perfectly with firmware 175.  Firmware 213 
>> seems to converge to an asymptotic reactance instead of 50 ohm match.  
>> The bad reactance is what causes the K4 to abort the tune cycle.  The 
>> KAT500 stays in tune unless I clear it.
>> 
>> I've checked everything else numerous times.  Yes the K4 tuner can 
>> find a match always with no problem,
>> 
>> Bob, the only thing I am changing is the KAT500 firmware.  No cables 
>> or settings on the K4 are changed.
>> 
>> Getting the hi swr message for tune mode and aborting the K4 tune 
>> cycle  is going to make it very hard to use an external tuner 
>> automatic or otherwise.  What does the K4 need to do about high swr in 
>> tune mode?
>> 
>> Unless there were some hardware changes to the KAT500 that I am 
>> unaware I suspect the KAT500 2xx firmware has a serious bug.
> 
> 73,
> Bob, N6TV
> _._,_._,_
> -------------------------
> Groups.io Links:
> 
> You receive all messages sent to this group.
> 
> View/Reply Online (#26608) [1] | Reply To Group | Reply To Sender | 
> Mute This Topic [2] | New Topic [3]
> Your Subscription [4] | Contact Group Owner | Unsubscribe [5] 
> [n8sbe at densbe.com]
> 
> _._,_._,_



Links:
------
[1] https://groups.io/g/Elecraft-K4/message/26608
[2] https://groups.io/mt/101567389/439435
[3] https://groups.io/g/Elecraft-K4/post
[4] https://groups.io/g/Elecraft-K4/editsub/439435
[5] 
https://groups.io/g/Elecraft-K4/leave/12322551/439435/1385384913/xyzzy