[Elecraft] K3 TX delay

[Brian Alsop]

Don,

It isn't the 8ms that is relevant, it is how the K3's coding behaves in 
subsequent CW characters when the TXDLY is varied from 8 -20 ms.   PTT 
is irrelevant.

Higher values produce QSD regardless of how the amp is keyed.  It occurs 
regardless if one is using the K3's internal keyer or an external keyer.


Speculation:
It appears the delay affects other timings within the K3.   It appears 
that at high values of TXDLY and CW speed the keying character timings 
get messed up.  In otherwords, TDXLY isn't like a simple delay line.  It 
is most likely an attempt to approximate the input TDXLY value by 
changing the timings in many routines.

Only Elecraft knows for sure how TXDLY is implemented in code.

73 de Brian/K3KO

On 2/17/2012 18:58, Don Wilhelm wrote:
> Igor,
>
> Please explain how the 8 ms is relevant when using PTT instead of VOX.
>
> In PTT state, Keyout follows PTT (not the keyclosure) - so the amplifier
> relay circuit should be closed
> as long as the operator closes the footswitch or whatever is used for
> PTT first.  Keying will most likely begin long after the footswitch is
> activated.  In other words, the 8 ms is not relevant, and no hot
> switching should occur.
>
> 73,
> Don W3FPR
>
> On 2/17/2012 10:51 AM, Igor Sokolov wrote:
>> That is right Nick. That is because your TX delay is set at 8 ms. But if
>> Rx/Tx  transition time of your AL-811 is greater then 8 ms you get "hot
>> switching" every time your start to transmit.
>>
>>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 10.0.1424 / Virus Database: 2112/4815 - Release Date: 02/17/12
>
>



-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1424 / Virus Database: 2112/4815 - Release Date: 02/17/12