[Elecraft] K3 QSK CW Audio Dropouts

[Vic Rosenthal]

I tried to hear this and didn't succeed. And I'm the world's most finicky QSK user.

Vic 4X6GP/K2VCO 

> On 7 Nov 2015, at 3:04 AM, Wayne Burdick <n6kr at elecraft.com> wrote:
> 
> We're talking about two different things.
> 
> What OK1RP may be hearing is the ATU switching its relays when he first transmits in a band segment that requires new LC settings. The firmware attempts to do that between CW elements (in RX mode). This should be extremely rare. (If it's happening more frequently, it could be related to particular combination of AGC and QSK menu settings along with high QRM/QRN on a given frequency. I would try selecting "OLD QSK" or "NEW QSK" to see if that has any impact, and/or increase the AGC THR value.)
> 
> The PA temperature anomaly reported earlier should also be extremely rare, and in fact no one had even mentioned it in years. Nothing has changed in this firmware recently. But I'm working on a firmware improvement for that and will discuss it later after testing.
> 
> Wayne
> N6KR
> 
> 
>> On Nov 6, 2015, at 9:45 AM, Don Wilhelm <w3fpr at embarqmail.com> wrote:
>> 
>> Petr,
>> 
>> Yes, Wayne' explanation was that the PA Temp is sampled between characters in CW, so if one uses QSK and listens closely, you can hear the gaps in the audio when the K3 returns to receive.
>> 
>> You may find a change in a firmware upgrade coming soon, but I don't know when.
>> 
>> 73,
>> Don W3FPR
>> 
>>> On 11/6/2015 12:05 PM, ok1rp wrote:
>>> Hi all,
>>> 
>>> few days ago I realized on K3 (using latest MCU/FPF) weird receive audio
>>> dropout problem.
>>> It happends during QSK CW operation and it is hearable in audio in between
>>> TX periods > time to time but it is repeatable. I did not heard these
>>> dropouts during receiving only mode...
>>> Simply when I am listenning on K3 all is ok but when I am starting to call
>>> CW or I am making QSO then dropouts in audio are readable in between TX
>>> periods with QSK.
>>> 
>>> Is there someone with similar effect please?
>>> Is there chance that it is linked to K3S weird transmit audio dropout
>>> problem discussed in different threat?
>>