It is easy to sync it to the keyboard speed, or set it to its own speed. The
real issue is the UI part. Should I use text command to slave and un-slave
the speeds? I'm running out of key combinations to do this with function
keys.
By input, I mean you "type" into the callsign field by sending code with the
paddle. I suppose this is for guys who are answering CQs and would rather
send by hand.
N6TV's source code emulatates the timing for all the major keyers. I suppose
I could put in a selection box at startup, but my inclination is just
support the Logikey 3, as close as we can get it.
- Ken
-----Original Message-----
From: Ed Parish K1EP [mailto:k1ep@arrl.net]
Sent: Sunday, March 16, 2003 9:19 AM
To: Dallas Carter; ken@k1ea.com; 'ct user list'
Subject: Re: [ct-user] Paddle intout to the computer
At 09:12 AM 3/16/03 -0500, Dallas Carter wrote:
>Yes and Yes. It is also quite handy if the paddle input
>is set to stop the canned transmission. makes for a nice
>added feature.
Would the paddle input be at the same speed as the computer generated code?
Does it have to be?
>Dallas W3PP
>
>----- Original Message -----
>From: Ken Wolff <ken@k1ea.com>
>To: 'ct user list' <ct-user@contesting.com>
>Sent: Sunday, March 16, 2003 8:51 AM
>Subject: [ct-user] Paddle intout to the computer
>
>
>> Thanks to N6TV, I've been experimenting with adding paddle support to CT.
>> Have other programs been reading the paddle to generate input? Is it
>> effective?
>>
>> - Ken
>>
|