>
Thanks, Tom NB5Q
> I was glad to see Wayne's post describing the fix for my problem, which > should work on the K3S. However, I am still not able to get the K3S paddle > input to the K3S keyer to appear in the K3 utility. I see the commands TT1; > or TT0; appear in the Command Tester window but still the K3S paddle keying > does not show up in the K3 Utility Terminal window. > > I am following Mr Cady's directions in his K3S and P3 book pgs 53 and > 81... I have re-installed the K3 Utility and retried several times but no > luck. The results remain as I described in my previous post below. > > > ------------------------------ > > Message: 5 > Date: Fri, 2 Mar 2018 21:06:41 -0700 > From: Tom Norris <[hidden email]> > To: Elecraft List Server <[hidden email]> > Subject: [Elecraft] K3 utility to monitor extended display of > characters sent from K3S keyer problem > Message-ID: > <CAMi8m32RoBetqvt86gxA8HcGCkKz7o3q3yoqdYg0FvA653o3iQ@mail. > gmail.com> > Content-Type: text/plain; charset="UTF-8" > > I'm beginning my learning curve with my new K3S Kit (after a trip to > Elecraft for them to correct the 400hz filter I put in backwards! Otherwise > it was a good, fun build). I'm wanting to practice CW sending and I am able > to see my K3S paddle input characters in the K3S VFO B. But I am not able > to receive the K3S paddle entered characters in the K3 Utility display. I > can enter and transmit characters via the keyboard in the K3 utility, see > them in the K3 Utility window and the K3S VFO B. I've tried the various > K3S Text Decode settings but was no help. I'm sure it's a setting > someplace, I've tried to search the archives but the posts I've found do > not address that part of the problem. > Thanks, Tom NB5Q > > > ------------------------------ > > Message: 23 > Date: Sat, 3 Mar 2018 09:08:25 -0800 > From: Gary Hawkins <[hidden email]> > To: Wayne Burdick <[hidden email]> > Cc: Elecraft Reflector <[hidden email]> > Subject: Re: [Elecraft] Terminal decoding on KX3 paddle generated CW > Message-ID: <[hidden email]> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Wayne, > > Many thanks for that - this works a treat :). > > 73, > > Gary K6YOA > > > On 3/3/2018 8:05 AM, Wayne Burdick wrote: > > Gary, > > > > There is a way to do this. It works equally well on the K2, K3, K3S, > KX2, and KX3. > > > > 1. Go into the KX3 Utility ?Command Tester? window. (Or use any terminal > emulator application of your choice.) > > > > 2. Send the command ?TT1;? to the radio from the computer. This will put > the rig into a mode where both transmitted and received characters are > outputted to the serial port, including those sent with the keyer paddle or > message memories. > > > > 3. To turn this mode off, send ?TT0;?. > > > > Note that this feature works with the built-in PSK31/PSK63 and RTTY > modes of all of the rigs as well. > > > > If you decide to try making contacts using CW or the built-in data > modes, check out the ?Terminal? function of the Utility. It allows you to > use the computer?s keyboard rather than the keyer paddle. > > > > 73, > > Wayne > > N6KR > > > **************************************** > Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Tom,
Go to the K3 Utility Terminal and in the SEND window, type in "TT1;" and then hit the Enter button. Then key the K3S and you should see your CW decoded. 73, Don W3FPR On 3/3/2018 5:55 PM, Tom Norris wrote: >> >> I was glad to see Wayne's post describing the fix for my problem, which >> should work on the K3S. However, I am still not able to get the K3S paddle >> input to the K3S keyer to appear in the K3 utility. I see the commands TT1; >> or TT0; appear in the Command Tester window but still the K3S paddle keying >> does not show up in the K3 Utility Terminal window. >> >> I am following Mr Cady's directions in his K3S and P3 book pgs 53 and >> 81... I have re-installed the K3 Utility and retried several times but no >> luck. The results remain as I described in my previous post below. >> > Thanks, Tom NB5Q > > > >> >> ------------------------------ >> >> Message: 5 >> Date: Fri, 2 Mar 2018 21:06:41 -0700 >> From: Tom Norris <[hidden email]> >> To: Elecraft List Server <[hidden email]> >> Subject: [Elecraft] K3 utility to monitor extended display of >> characters sent from K3S keyer problem >> Message-ID: >> <CAMi8m32RoBetqvt86gxA8HcGCkKz7o3q3yoqdYg0FvA653o3iQ@mail. >> gmail.com> >> Content-Type: text/plain; charset="UTF-8" >> >> I'm beginning my learning curve with my new K3S Kit (after a trip to >> Elecraft for them to correct the 400hz filter I put in backwards! Otherwise >> it was a good, fun build). I'm wanting to practice CW sending and I am able >> to see my K3S paddle input characters in the K3S VFO B. But I am not able >> to receive the K3S paddle entered characters in the K3 Utility display. I >> can enter and transmit characters via the keyboard in the K3 utility, see >> them in the K3 Utility window and the K3S VFO B. I've tried the various >> K3S Text Decode settings but was no help. I'm sure it's a setting >> someplace, I've tried to search the archives but the posts I've found do >> not address that part of the problem. >> Thanks, Tom NB5Q >> >> >> ------------------------------ >> >> Message: 23 >> Date: Sat, 3 Mar 2018 09:08:25 -0800 >> From: Gary Hawkins <[hidden email]> >> To: Wayne Burdick <[hidden email]> >> Cc: Elecraft Reflector <[hidden email]> >> Subject: Re: [Elecraft] Terminal decoding on KX3 paddle generated CW >> Message-ID: <[hidden email]> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> Hi Wayne, >> >> Many thanks for that - this works a treat :). >> >> 73, >> >> Gary K6YOA >> >> >> On 3/3/2018 8:05 AM, Wayne Burdick wrote: >>> Gary, >>> >>> There is a way to do this. It works equally well on the K2, K3, K3S, >> KX2, and KX3. >>> >>> 1. Go into the KX3 Utility ?Command Tester? window. (Or use any terminal >> emulator application of your choice.) >>> >>> 2. Send the command ?TT1;? to the radio from the computer. This will put >> the rig into a mode where both transmitted and received characters are >> outputted to the serial port, including those sent with the keyer paddle or >> message memories. >>> >>> 3. To turn this mode off, send ?TT0;?. >>> >>> Note that this feature works with the built-in PSK31/PSK63 and RTTY >> modes of all of the rigs as well. >>> >>> If you decide to try making contacts using CW or the built-in data >> modes, check out the ?Terminal? function of the Utility. It allows you to >> use the computer?s keyboard rather than the keyer paddle. >>> >>> 73, >>> Wayne >>> N6KR >>> >> **************************************** >> > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] > Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Does this only work with the internal keyer??
> > Go to the K3 Utility Terminal and in the SEND window, type in "TT1;" and then hit the Enter button. > Then key the K3S and you should see your CW decoded. > Grant NQ5T K3 #2091, KX3 #8342 ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Free forum by Nabble | Edit this page |