Re: [Elecraft] K3: send RTTY using KEY IN?
DOUGLAS ZWIEBEL wrote: > > OK...so we can send RTTY using the paddle in. What about sending RTTY > using the KEY IN (as in, use an outboard contest program to send CW > and have the K3 convert it to RY). > > I know that this was supposed to be "on the list" but was this ever > implemented? > > It was never implemented and I doubt if it has ever been "on the list". In order for this to work, the K3 would have to decode your manual sending. When sending with a paddle, it generates the text itself from paddle closures so no decoding is necessary. - Julian, G4ILO. K2 #392 K3 #222. http://www.g4ilo.com/ G4ILO's Shack http://www.g4ilo.com/blog.html G4ILO's Bloghttp://www.g4ilo.com/kcomm.html KComm for Elecraft K2 and K3 -- View this message in context: http://n2.nabble.com/K3%3A-send-RTTY-using-KEY-IN--tp2328715p2329236.html Sent from the Elecraft mailing list archive at Nabble.com. __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Elecraft] K3: send RTTY using KEY IN?
> It was never implemented and I doubt if it has ever been "on the list". In > order for this to work, the K3 would have to decode your manual sending. > When sending with a paddle, it generates the text itself from paddle > closures so no decoding is necessary. > > - > Julian, G4ILO. K2 #392 K3 #222. Julian, the paddle generates only dots and dashes, so the decoding is necessary anyway. But this is not a problem, after K3 has decoding capability. 73 Val, LZ1VB __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Elecraft] K3: send RTTY using KEY IN?
Val-12 wrote: > > Julian, the paddle generates only dots and dashes, so the decoding is > necessary anyway. But this is not a problem, after K3 has decoding > capability. > Yes, but it can quickly work out what the character is from the dots and dashes. With hand-sent morse it has to figure out what is a dot and what is a dash. This is the hard part, the reason why decoders don't work so well on hand sent morse. Yes, the K3 has decoding capability that works on audio from the receiver. Wiring that up (or the software equivalent) so it works from input from the key socket as well is not as trivial as it may seem to someone who is not the rig designer. Believe me. I asked pretty much the same question a while ago when I wondered why the K3 decoder could not display the code I was sending from the straight key, as it does with the paddle, and that was what I was told. - Julian, G4ILO. K2 #392 K3 #222. http://www.g4ilo.com/ G4ILO's Shack http://www.g4ilo.com/blog.html G4ILO's Bloghttp://www.g4ilo.com/kcomm.html KComm for Elecraft K2 and K3 -- View this message in context: http://n2.nabble.com/K3%3A-send-RTTY-using-KEY-IN--tp2328715p2329639.html Sent from the Elecraft mailing list archive at Nabble.com. __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
Re: [Elecraft] K3: send RTTY using KEY IN?
While such a capability would be nice to have in an emergency, there are much better tools to allow one to operate RTTY... like MMTTY which is free to download. I would suggest a review of AA5AU's excellent RTTY tutorial web site for details: http://www.aa5au.com/rtty.html 73, Bob W5OV (NJ5DX in WPX RTTY) -Original Message- From: elecraft-boun...@mailman.qth.net [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Julian, G4ILO Sent: Sunday, February 15, 2009 7:00 AM To: elecraft@mailman.qth.net Subject: Re: [Elecraft] K3: send RTTY using KEY IN? Val-12 wrote: > > Julian, the paddle generates only dots and dashes, so the decoding is > necessary anyway. But this is not a problem, after K3 has decoding > capability. > Yes, but it can quickly work out what the character is from the dots and dashes. With hand-sent morse it has to figure out what is a dot and what is a dash. This is the hard part, the reason why decoders don't work so well on hand sent morse. Yes, the K3 has decoding capability that works on audio from the receiver. Wiring that up (or the software equivalent) so it works from input from the key socket as well is not as trivial as it may seem to someone who is not the rig designer. Believe me. I asked pretty much the same question a while ago when I wondered why the K3 decoder could not display the code I was sending from the straight key, as it does with the paddle, and that was what I was told. - Julian, G4ILO. K2 #392 K3 #222. http://www.g4ilo.com/ G4ILO's Shack http://www.g4ilo.com/blog.html G4ILO's Bloghttp://www.g4ilo.com/kcomm.html KComm for Elecraft K2 and K3 -- View this message in context: http://n2.nabble.com/K3%3A-send-RTTY-using-KEY-IN--tp2328715p2329639.html Sent from the Elecraft mailing list archive at Nabble.com. __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
