CW Rise Time?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

CW Rise Time?

John Huffman-3
My call - K1ESE - is misinterpreted in CW as - K1EST - when  my keying
is too soft.  I cured this on my Orion by setting the CW rise/fall time
from 7ms to 5ms.

I can't find the parameter to set the rise/fall time on my K3.

How do you do that?

73 de K1ESE
John
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: CW Rise Time?

P.B. Christensen
> My call - K1ESE - is misinterpreted in CW as - K1EST - when  my keying
> is too soft.  I cured this on my Orion by setting the CW rise/fall time
> from 7ms to 5ms. I can't find the parameter to set the rise/fall time on
> my K3.

John,

I found that in the last K3 F/W release (or perhaps the one just before it),
the K3's CW rise/fall time is now roughly 2.5 ms compared to the previous
5-6 ms.  I had to verify my scope settings on another time base to ensure I
had not misinterpreted the measured result.

That being the case, it seems to me that the K3's CW envelope has gone
through two evolutionary changes.  The first occurred a while back with a
hardware fix and that mod is documented on the Elecraft website.  Prior to
the fix, CW rise was about 8 ms or perhaps a bit longer.  After the hardware
fix, the rise went to about 5-6 ms.  And now, we seem to be down to about
2.5 ms.

Whether intentional or not by Elecraft, that is what I now measure on my K3.
Perhaps this is not representative of other K3s.  Also, I do not detect an
increase in the amount of keying sidebands with the faster ramping/decay.
So, the ALC is still preserving the raised cosine function very well.

Long story short -- if Elecraft did in fact accelerate the ramping/decay
time of the CW envelope down to about 2.5 ms, I can't imagine why anyone
would want keying any harder and faster than that.  I am very happy with
what I'm seeing.

Paul, W9AC
 

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: CW Rise Time?

John Huffman-3
In reply to this post by John Huffman-3
Paul -

My K3 SN 2533 is running FW 3.19.  If the rise is 2.5ms, I sure don't
want to try anything shorter.

On the Orion messing with the weighting didn't solve the problem, just
the ris/fall time.  I'll set the K3 weighting to .90 and see if that helps.

I wonder if the change in rise to 2.5ms has effected the key line to the
amp?

Thanks for the info.

73 de K1ESE
John


 > My call - K1ESE - is misinterpreted in CW as - K1EST - when  my keying
 > is too soft.  I cured this on my Orion by setting the CW rise/fall time
 > from 7ms to 5ms. I can't find the parameter to set the rise/fall time on
 > my K3.

John,

I found that in the last K3 F/W release (or perhaps the one just before
it), the K3's CW rise/fall time is now roughly 2.5 ms compared to the
previous 5-6 ms.  I had to verify my scope settings on another time base
to ensure I had not misinterpreted the measured result.

  .....

Paul, W9AC

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Reply | Threaded
Open this post in threaded view
|

Re: CW Rise Time?

P.B. Christensen
In reply to this post by John Huffman-3
> "My K3 SN 2533 is running FW 3.19.  If the rise is 2.5ms, I sure don't
want to try anything shorter.  I wonder if the change in rise to 2.5ms has
effected the key line to the
amp?"

I went back to old K3 F/W version 2.19 and the CW rise/fall time on my K3
lengthened back to 6 ms.  So, my guess is that it changed somewhere around
the release of version 3 since version 3.14 also shows the faster CW
rise/fall time of ~ 2.5 ms.

John, I think you'll be fine now when sending K1ESE at any speed as long as
you're using a newer firmware release.

Paul, W9AC



On the Orion messing with the weighting didn't solve the problem, just
the ris/fall time.  I'll set the K3 weighting to .90 and see if that helps.

I wonder if the change in rise to 2.5ms has effected the key line to the
amp?

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html