[Elecraft] Bug mode on K3?

[Ian White]

>Ian,
>
>The K14 and its kin are devices specializing in
>being keyers; and that's all they were intended to
>do. Expecting the K3 to have the keying
>capabilities of one of the specialized K1EL
>products seems a bit much.
>
>A better 'industry-wide benchmark' might be to
>compare the K3 with other high-end ham
>transceivers with regard to the keying modes they
>provide.
>
>Phil W7OX
>

I wouldn't ever ask for all the facilities of a specialized keyer. The
wider range of timing options is the only  exception, because
significant numbers of K3 users NEED a specific timing mode other than
Curtis A or Curtis B in order to gain full access to the K3's internal
keyer. This is particularly important for the K3 because paddle-sent
RTTY and PSK are accessible only through the internal keyer. 

As regards the comparisons with other high-end transceivers, I would
NEVER expect Elecraft to settle for being 'ordinary' or 'average' - not
in this way or any other. 


73 from Ian GM3SEK


>-----Original Message-----
>From: Elecraft [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of
>Phil Wheeler
>Sent: 10 December 2014 14:41
>To: elecraft at mailman.qth.net
>Subject: Re: [Elecraft] Bug mode on K3?
>
>On 12/10/14 12:44 AM, Ian White wrote:
>> Ed - KL7UW wrote:
>>> The K14 offers six keying modes:
>>> 1- Iambic-A
>>> 2- Iambic-B
>>> 3- Ultimatic
>>> 4- straight key
>>> 5- Dit priority
>>> 6- Dash priority
>>>
>> And others have also identified:
>> 7- Mechanical bug
>> 8-  CMOS Superkeyer (Logikeyer)
>>
>> That list would be a reasonable 'industry-wide benchmark' for the
>> keying/timing modes that a premium CW transceiver like the K3 should
>> offer as built-in options.
>>
>> Each one of those keying modes has a significant real-world
following.
>> Translation: there are significant numbers of K3 users who NEED that
>> specific timing mode in order to operate close to their personal top
>> speed.
>>
>> What K3 users *don't* need is to be told to use an external keyer, an
>> adapter or some other workaround. We already know the workarounds
>> because - even after 7 years - the K3 still needs them.
>>
>>
>> 73 from Ian GM3SEK
>