CT-User
[Top] [All Lists]

[ct-user] Paddle input- Why?

To: <ct-user@contesting.com>
Subject: [ct-user] Paddle input- Why?
From: Dave Sublette <k4to@meginc.com> (Dave Sublette)
Date: Fri, 01 Jun 2001 13:33:16 -0400
I use a keying cable from DX Solutions, Huntsville, AL, which has a
parallel female quarter inch jack for an input from an external keyer. I
use the external keyer a lot during repeats...etc. It should be a simple
task to add a parallel jack to your radio....maybe even a "Y" connector of
the correct sex from Radio Shack would do it.

73,

Dave, K4TO

alsopb wrote:

> I'll plead ignorance this issue.
>
> Why does the CT program have to have paddle input?  Can't a separate
> keyer in parallel with the key jack perform the same function?
>
> Are some people out there entering the call into the call field via
> the keyer?
>
> I guess I just type in the call/exchage and use the separate keyer
> only for fills.  It certainly can be set at a lower speed.
>
> As for the extra hardware required by a keyer,  Heck, I have a Curtis
> keyer chip mounted on top of the paddle. It runs for years on a 9 volt
> battery.
>
> It seems that short of implementing artificial intelligence, it would
> be difficult for the program to sort out field info entered from the
> paddle vs other "fill" type info.
>
> If you have to toggle it on and off via something like ALT-K, it would
> seem to be a bigger pain than it's worth.
>
> I'd really appreciate knowing why this is "needed".  I understand
> other contest programs have a paddle input function.  What does it
> exactly do other than sending CW?
>
> 73 de Brian/K3KO
>
> --
> WWW:                      http://www.k1ea.com/
> Submissions:              ct-user@contesting.com
> Administrative requests:  ct-user-REQUEST@contesting.com
> Problems:                 owner-ct-user@contesting.com


--
WWW:                      http://www.k1ea.com/
Submissions:              ct-user@contesting.com
Administrative requests:  ct-user-REQUEST@contesting.com
Problems:                 owner-ct-user@contesting.com


<Prev in Thread] Current Thread [Next in Thread>