Just to clarify, for CW and data modes (including RTTY/FSK), you can use:

  - external PC + keyboard (either with a terminal program or using KX3/KX2 
Utility)

  - external keyer paddle
 
  - attached keyer paddle (KXPD2/KXPD3)

73,
Wayne
N6KR




> On Mar 19, 2018, at 5:05 PM, Don Wilhelm <[email protected]> wrote:
> 
> Noel,
> 
> The KX3 does not have an FSK input.  You will have to move up to the K3S to 
> have that.
> 
> You cannot use a CW Keyer (external) for FSK - you must use paddles directly 
> attached to the internal keyer in the KX3.
> 
> The easiest way is to use AFSK A data submode along with a soundcard and a 
> computer.
> 
> If you have a computer application that can send ASCII text (via the "KY" 
> commands (see the programmers reference manual), then you can send in FSK D 
> mode.
> 
> Despite what is often said about soundcard generated AFSK, in the K3/K3S, it 
> is actually cleaner than FSK.  I figure that is also true of the KX3, 
> although I do not have any data on that.
> 
> 73,
> Don W3FPR
> 
> On 3/19/2018 7:12 PM, NOEL POULIN wrote:
>> Hello,
>> I was reading the KX3 manual, and I  do not see how to hook an FSK interface 
>> to the KX3,.
>> I want to use it in RTTY (FSK) and I am looking where should I connect the 
>> interface.
>> I do not want t o use a cw keyer to for rtty....
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[email protected]
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [email protected]

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

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]

Reply via email to