Re: [Elecraft] K3 choppy CW
Erik, Yes, you can use paddles with the WinKeyer, and IMHO the big advantage of a WinKeyer for this is that the paddles are integrated with computer CW. That is, if the computer is sending CW, a touch of the paddle instantly stops outgoing computer-generated CW so you can carry on with the paddle. If you find you hit the wrong function key and it starts sending CQ whan you wanted to send TU, for example, you can just grab the paddle and send TU and that will abort the unwanted message. You can also use a paddle plugged directly into the back of the K3, but that is not integrated in the sense that CW input from the paddle and from the computer are wire-Ored inside the radio, i.e. if you key the paddle while the computer is sending, all you get is a mess. You have to hit ESC first to stop the computer-generated CW before carrying on with the paddle. One of the things you are looking for, if I understand correctly, is to be able to enter information into N1MM Logger using the paddle. This is *not* possible. There is no CW decoder in the Logger. Even if there were, paddle input into the WinKeyer is not passed back to the computer, it only goes forward to the radio. As a result, the paddle is not usable for entering logged data. For that matter, when you send free-form CW from the keyboard by typing into the Ctrl+K window, that information is not entered into the log either. If you want information to be logged, you have to type it into the appropriate box in the Entry window, and then the function key message macros can incorporate that information when they are sent. One other convenience feature of the WKUSB is that it can be used as a stand-alone keyer without computer control. You can power it either from a battery or from a USB port without any transfer of data from the computer. So you can use it without firing up the logging program, e.g. if you are randomly tuning the band and hear someone you want to work. In this mode, without software controlling it, the WKUSB has four programmable memory buttons. Warning: these four memory buttons cannot be used when the WKUSB is under computer control - you have to use messages programmed into the software instead. This limitation is programmed into the WinKeyer. You can also use the memory buttons on the K3, but one peculiarity is that these have lower priority than computer or paddle input, so you cannot use the memory buttons to interrupt computer CW. You have to hit ESC first (or touch the WinKeyer's paddle) before using the K3's memories. This makes them less useful than having the same messages programmed into function keys in N1MM Logger. HTH. 73, Rich VE3KI __ 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 choppy CW
Erik, No you can use the paddles with N1MM and just the K3. The K1EL is for computer generated CW. Some of us have a hard enough time typing, tuning, using a key AND keeping up a decent rate ;o) For casual contesting, without using computer generated CW, you really don't need WKUSB, the paddles will do it. Julius Fazekas N2WN Tennessee Contest Group http://www.k4ro.net/tcg/index.html Tennessee QSO Party http://www.tnqp.org/ Elecraft K2/100 #4455 Elecraft K3/100 #366 --- On Thu, 2/26/09, Erik N Basilier wrote: > From: Erik N Basilier > Subject: Re: [Elecraft] K3 choppy CW > To: "Andrew Faber" , "Julius Fazekas n2wn" > , elecraft@mailman.qth.net > Date: Thursday, February 26, 2009, 3:20 PM > Andy, > > Thanks for your input, it is helpful to me. Sorry if this > is too much OT, but I see an additional benefit in the > WinKeyer in that it lets you use paddles. I don't know > how deep into contest-land I will go, but at this point it > feels like cheating to use the keyboard, even though it is > much less stressful than paddles. Not yet familiar with > N1MM, I simply assume that you can't use paddles with it > unless you have the WinKeyer. Anyone please correct me if I > am wrong. > > 73, > Erik > > > > Julius, > > Though we're now drifting off topic from > Elecraft, WinKey USB works fine on my Vista laptop keying my > K3. It also has the advantage of not tying up any serial > ports, since it runs off the USB port (the driver creates a > "virtual" serial port). You can also use it for > PTT, thus avoiding using another serial port for that > function. > > 73,andy, ae6y __ 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 choppy CW
Hi Andy, No argument on the advantages/disadvantages of using WKUSB with the K3. But you don't "have" to have it, even with a USB to serial interface. Too, I haven't any experience with Vista and WKUSB, so can't make an experienced comment on that combo. My experiences with loading the drivers is simply noted to save someone else the headache some of us have had... Cheers, Julius Julius Fazekas N2WN Tennessee Contest Group http://www.k4ro.net/tcg/index.html Tennessee QSO Party http://www.tnqp.org/ Elecraft K2/100 #4455 Elecraft K3/100 #366 --- On Thu, 2/26/09, Andrew Faber wrote: > From: Andrew Faber > Subject: Re: [Elecraft] K3 choppy CW > To: "Erik N Basilier" , "Julius Fazekas n2wn" > , elecraft@mailman.qth.net > Date: Thursday, February 26, 2009, 2:53 PM > Julius, > Though we're now drifting off topic from Elecraft, > WinKey USB works fine on my Vista laptop keying my K3. It > also has the advantage of not tying up any serial ports, > since it runs off the USB port (the driver creates a > "virtual" serial port). You can also use it for > PTT, thus avoiding using another serial port for that > function. > 73,andy, ae6y > - Original Message - From: "Erik N > Basilier" > To: "Julius Fazekas n2wn" > ; > > Sent: Thursday, February 26, 2009 11:47 AM > Subject: Re: [Elecraft] K3 choppy CW > > > > Julius, > > > > Thanks for the heads-up. I did order the USB version, > and just assumed that > > it would not be a problem since so many people have > said good things about > > them. Did you install successfully on Vista 32? > > > > 73, > > Erik K7TV > > > > - Original Message - From: "Julius > Fazekas n2wn" > > To: > > Sent: Thursday, February 26, 2009 12:42 PM > > Subject: Re: [Elecraft] K3 choppy CW > > > > > >> > >> Eric, > >> > >> Something to keep in mind with the WKUSB keyer, at > least the one I > >> installed > >> two years ago, is that the driver installation can > be very unforgiving. I, > >> and others, had a heck of a time with them IF one > doesn't EXACTLY follow > >> the > >> installation instructions. Read, read and read > again before doing > >> anything... Once installed the unit seems > bulletproof. > >> > >> This may not hold true with the latest models. I > just bought a new one, > >> for > >> mobile use with my K2. > >> > >> Hope to catch you in the contests.. soon to be > RTTY enabled here (FSK of > >> course) ;o) > >> > >> 73, > >> Julius > >> > >> > > > > > > > __ > > 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
Re: [Elecraft] K3 choppy CW
Hi Erik, I haven't, I'm still using Win2K predominately on my contest computer. So far my experiences have bee negative with Vista, but that may be as much due to our IT Department "making things safe". One of the gents in our contest group has put it on Vista, but he had to get some help to do so. The K1EL Yahoo group is very helpful if you run into any problems. Don't get me wrong, it's a good piece of equipment and I know more folks who haven't had problems than those of us who did, but it is a possibility, so take your time with the driver install. The kit is a quick and easy build. Cheers, Julius Julius Fazekas N2WN Tennessee Contest Group http://www.k4ro.net/tcg/index.html Tennessee QSO Party http://www.tnqp.org/ Elecraft K2/100 #4455 Elecraft K3/100 #366 --- On Thu, 2/26/09, Erik N Basilier wrote: > From: Erik N Basilier > Subject: Re: [Elecraft] K3 choppy CW > To: "Julius Fazekas n2wn" , elecraft@mailman.qth.net > Date: Thursday, February 26, 2009, 2:47 PM > Julius, > > Thanks for the heads-up. I did order the USB version, and > just assumed that it would not be a problem since so many > people have said good things about them. Did you install > successfully on Vista 32? > > 73, > Erik K7TV > > - Original Message - From: "Julius Fazekas > n2wn" > To: > Sent: Thursday, February 26, 2009 12:42 PM > Subject: Re: [Elecraft] K3 choppy CW > > > > > > Eric, > > > > Something to keep in mind with the WKUSB keyer, at > least the one I installed > > two years ago, is that the driver installation can be > very unforgiving. I, > > and others, had a heck of a time with them IF one > doesn't EXACTLY follow the > > installation instructions. Read, read and read again > before doing > > anything... Once installed the unit seems bulletproof. > > > > This may not hold true with the latest models. I just > bought a new one, for > > mobile use with my K2. > > > > Hope to catch you in the contests.. soon to be RTTY > enabled here (FSK of > > course) ;o) > > > > 73, > > Julius > > > > __ 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 choppy CW
Group, I am sorry to harp on this, but it seems someone thought I was not thinking I could key the K3 directly when using N1MM. Of course one could do that. But I was assuming that running through N1MM would give me a specific benefit: Not to have to enter callsigns and exchange info twice (once to transmit, once to log). To me it seems obvious that any contest logging program should do this; after e.g. a callsign has been entered through the keyboard, there is no ambiguity about it, and the program should transmit it as well as log it. Now N1MM claims to be integrated with WinKeyer, so my expectation is that I should be able to do the same using the paddles to enter the callsign. Admittedly, that involves some CW decoding in software, but if I select the type of data item by selecting an input field by mouse on the screen, the program should have a leg up for a good guess, which I could verify by one glance, and the exchange information would probably be generated automatically anyway. Before I put more time into this, would somebody familiar with N1MM please let me know if any of my expectations are unrealistic. Thanks in advance, Erik K7TV > Andy, > > Thanks for your input, it is helpful to me. Sorry if this is too much OT, > but I see an additional benefit in the WinKeyer in that it lets you use > paddles. I don't know how deep into contest-land I will go, but at this > point it feels like cheating to use the keyboard, even though it is much > less stressful than paddles. Not yet familiar with N1MM, I simply assume > that you can't use paddles with it unless you have the WinKeyer. Anyone > please correct me if I am wrong. > > 73, > Erik __ 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 choppy CW
Andy, Thanks for your input, it is helpful to me. Sorry if this is too much OT, but I see an additional benefit in the WinKeyer in that it lets you use paddles. I don't know how deep into contest-land I will go, but at this point it feels like cheating to use the keyboard, even though it is much less stressful than paddles. Not yet familiar with N1MM, I simply assume that you can't use paddles with it unless you have the WinKeyer. Anyone please correct me if I am wrong. 73, Erik > Julius, > Though we're now drifting off topic from Elecraft, WinKey USB works fine > on my Vista laptop keying my K3. It also has the advantage of not tying up > any serial ports, since it runs off the USB port (the driver creates a > "virtual" serial port). You can also use it for PTT, thus avoiding using > another serial port for that function. > 73,andy, ae6y __ 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 choppy CW
Julius, Though we're now drifting off topic from Elecraft, WinKey USB works fine on my Vista laptop keying my K3. It also has the advantage of not tying up any serial ports, since it runs off the USB port (the driver creates a "virtual" serial port). You can also use it for PTT, thus avoiding using another serial port for that function. 73,andy, ae6y - Original Message - From: "Erik N Basilier" To: "Julius Fazekas n2wn" ; Sent: Thursday, February 26, 2009 11:47 AM Subject: Re: [Elecraft] K3 choppy CW > Julius, > > Thanks for the heads-up. I did order the USB version, and just assumed > that > it would not be a problem since so many people have said good things about > them. Did you install successfully on Vista 32? > > 73, > Erik K7TV > > - Original Message - > From: "Julius Fazekas n2wn" > To: > Sent: Thursday, February 26, 2009 12:42 PM > Subject: Re: [Elecraft] K3 choppy CW > > >> >> Eric, >> >> Something to keep in mind with the WKUSB keyer, at least the one I >> installed >> two years ago, is that the driver installation can be very unforgiving. >> I, >> and others, had a heck of a time with them IF one doesn't EXACTLY follow >> the >> installation instructions. Read, read and read again before doing >> anything... Once installed the unit seems bulletproof. >> >> This may not hold true with the latest models. I just bought a new one, >> for >> mobile use with my K2. >> >> Hope to catch you in the contests.. soon to be RTTY enabled here (FSK of >> course) ;o) >> >> 73, >> Julius >> >> > > > __ > 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
Re: [Elecraft] K3 choppy CW
Julius, Thanks for the heads-up. I did order the USB version, and just assumed that it would not be a problem since so many people have said good things about them. Did you install successfully on Vista 32? 73, Erik K7TV - Original Message - From: "Julius Fazekas n2wn" To: Sent: Thursday, February 26, 2009 12:42 PM Subject: Re: [Elecraft] K3 choppy CW > > Eric, > > Something to keep in mind with the WKUSB keyer, at least the one I > installed > two years ago, is that the driver installation can be very unforgiving. I, > and others, had a heck of a time with them IF one doesn't EXACTLY follow > the > installation instructions. Read, read and read again before doing > anything... Once installed the unit seems bulletproof. > > This may not hold true with the latest models. I just bought a new one, > for > mobile use with my K2. > > Hope to catch you in the contests.. soon to be RTTY enabled here (FSK of > course) ;o) > > 73, > Julius > > __ 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 choppy CW
Eric, Something to keep in mind with the WKUSB keyer, at least the one I installed two years ago, is that the driver installation can be very unforgiving. I, and others, had a heck of a time with them IF one doesn't EXACTLY follow the installation instructions. Read, read and read again before doing anything... Once installed the unit seems bulletproof. This may not hold true with the latest models. I just bought a new one, for mobile use with my K2. Hope to catch you in the contests.. soon to be RTTY enabled here (FSK of course) ;o) 73, Julius K7TV wrote: > > Hi Vic, > > In my opinion, Kok Chen and you have said it best so far. > The bottom line is that someone could get perfect CW (without using audio) > from older as well as newer computers, and could repeat the feat over and > over > on different machines, while another person has the opposite experience, > and, > as you point out, the difference has a *lot* to do with what else is > running > on > the computer. It is very easy to assume that just because something is > working > repeatedly for one person, it would for another person. The computer > industry > has in effect promoted the belief that you just have to have a program and > a > computer that are compatible, and you do the installation correctly, you > can > forget about what else you have on the computer. Not so. Even in the > absence > of unrelated software and hardware, small changes in the basic hardware > configuration > can make a big difference in outcome; a faster processor or larger memory > is > likely to work for you, but *can* work against you in some cases. > What is the best approach depends a lot on personal circumstances. You > mention gadget overload in the shack, and I have that too. You are > apparently > willing to strip your shack computer of all non-ham activities, and the > computer > then is a ham gadget, great! I assume you have another computer for email > etc. > In my case, my main computer is quite fast (quad 6600 processor) and it is > located right next to my radios. It has 4 GB of memory, more than Vista 32 > can use. All the time I run several resource-heavy programs on it. Most of > the time > I get on the radio without any PC use at all, but I do use that same > computer when > once in a while I get on the digital modes. If I were to shut down a bunch > of software > before doing running ham software, I would be too lazy to bother doing it > at > all. > I could add another computer for hamming, but that computer would then be > a > ham gadget, and a much bulkier one than a WinKeyer. Now it so happens, > maybe > because of the many contesters on this list, I am beginning to get the > itch > to try > contesting with software. The other day I downloaded and installed N1MM. > The same day I placed an order for a WinKeyer. While my software and > hardware today might allow me to be one of the lucky users who don't need > the WinKeyer, the odds are against it, and I don't want to waste the time > trying > it, expecially since I frequently change the software I run, and I don't > want to > revisit the issue. > > 73, > Erik K7TV > > - Original Message - > From: "Vic K2VCO" > To: "W0MU Mike Fatchett" > Cc: > Sent: Thursday, February 26, 2009 10:25 AM > Subject: Re: [Elecraft] K3 choppy CW > > >> W0MU Mike Fatchett wrote: >>> The key is a decent computer. There are many people using very old >>> computers with minimal ram and cpu speed and they wonder why they have >>> issues. >>> >>> Some people do not have days and hours to figure out why something won't >>> work especially leading up to a contest, for them a WinKeyer might be a >>> great solution. To each their own. >> >> It's an interesting problem. I have an old Windows 2000 800 MHz laptop >> which sends perfect >> CW on my K3 from N1MM at 30 wpm. I did have to set the weight parameter >> in >> N1MM to 55. >> >> Interestingly, I once had a problem of horrible CW with variable-length >> elements, etc. I >> discovered that it was because my wireless network was *not* connected -- >> and therefore >> was continuously scanning. Probably the driver was disabling interrupts >> for long periods. >> I simply turned the wireless back on and solved the problem. >> >> This is just one possible issue. Anti-malware programs can also interfere >> with CW >> generation. Since I don't do email on my shack computer and only >> minimally >> access the web, >> I've removed the anti-virus software and kept only a fire
Re: [Elecraft] K3 choppy CW
I am a doubter and avid contester. I've had zero negative comments about my keying using simply a serial cable from a COM port direct to the K3 RS232 port. That's 8000 plus CW QSOs and who knows how many unanswered CQs and wing and a prayer repeats over the past year. Win2K and N1MM mostly, some XP with a laptop (yes one blessed with a real serial port). Yes, I have three K1EL keyers, but only use the USB keyer with the K2. YMMV, but I'm a happy camper on CW with a very simple no interface setup with my K3. 73, Julius n2wn R. Kevin Stover wrote: > > Everybody should be using a Winkey to key CW. > > Some people will deny that keying directly from an serial port > controlled by windows causes keying errors. When we ran DOS, the > applications could have unfettered access to the ports. You could also > easily harness the system clock and use it rather than the OS to supply > the timing for CW. It was easy to background a process like sending CW > knowing you had control of the port when you needed it. Not so with > Windows98 and up. XP is especially bad. > > Ever had an application or the OS grab a hold of a USB, serial or > parallel port and not let go when the application or process terminated? > It never happened in DOS. > > One question for the doubters. If a winkey like device isn't necessary > to send properly timed CW, why do several hardware manufacturers, Micro > Ham, US Interface, Rig Expert, and nearly all general and contest > logging applications support it? Just to make K1EL rich? > > W0MU Mike Fatchett wrote: >> N1MM users have had similar issues. I don't know if AB7R's fix works but >> many have just gone to a Winkey keyer as a solution. I have one built >> into >> my SO2R MK2R+ Microham devices so I have never seen this issue. >> >> >> "A slip of the foot you may soon recover, but a slip of the tongue you >> may >> never get over." Ben Franklin > > -- > R. Kevin Stover, ACØH > __ > 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 > > - Julius Fazekas N2WN Tennessee Contest Group http://www.k4ro.net/tcg/index.html Tennessee QSO Party http://www.tnqp.org/ Elecraft K2/100 #4455 Elecraft K3/100 #366 -- View this message in context: http://n2.nabble.com/Re%3A-K3-choppy-CW-tp2386856p2391682.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 choppy CW
Hi Vic, In my opinion, Kok Chen and you have said it best so far. The bottom line is that someone could get perfect CW (without using audio) from older as well as newer computers, and could repeat the feat over and over on different machines, while another person has the opposite experience, and, as you point out, the difference has a *lot* to do with what else is running on the computer. It is very easy to assume that just because something is working repeatedly for one person, it would for another person. The computer industry has in effect promoted the belief that you just have to have a program and a computer that are compatible, and you do the installation correctly, you can forget about what else you have on the computer. Not so. Even in the absence of unrelated software and hardware, small changes in the basic hardware configuration can make a big difference in outcome; a faster processor or larger memory is likely to work for you, but *can* work against you in some cases. What is the best approach depends a lot on personal circumstances. You mention gadget overload in the shack, and I have that too. You are apparently willing to strip your shack computer of all non-ham activities, and the computer then is a ham gadget, great! I assume you have another computer for email etc. In my case, my main computer is quite fast (quad 6600 processor) and it is located right next to my radios. It has 4 GB of memory, more than Vista 32 can use. All the time I run several resource-heavy programs on it. Most of the time I get on the radio without any PC use at all, but I do use that same computer when once in a while I get on the digital modes. If I were to shut down a bunch of software before doing running ham software, I would be too lazy to bother doing it at all. I could add another computer for hamming, but that computer would then be a ham gadget, and a much bulkier one than a WinKeyer. Now it so happens, maybe because of the many contesters on this list, I am beginning to get the itch to try contesting with software. The other day I downloaded and installed N1MM. The same day I placed an order for a WinKeyer. While my software and hardware today might allow me to be one of the lucky users who don't need the WinKeyer, the odds are against it, and I don't want to waste the time trying it, expecially since I frequently change the software I run, and I don't want to revisit the issue. 73, Erik K7TV - Original Message - From: "Vic K2VCO" To: "W0MU Mike Fatchett" Cc: Sent: Thursday, February 26, 2009 10:25 AM Subject: Re: [Elecraft] K3 choppy CW > W0MU Mike Fatchett wrote: >> The key is a decent computer. There are many people using very old >> computers with minimal ram and cpu speed and they wonder why they have >> issues. >> >> Some people do not have days and hours to figure out why something won't >> work especially leading up to a contest, for them a WinKeyer might be a >> great solution. To each their own. > > It's an interesting problem. I have an old Windows 2000 800 MHz laptop > which sends perfect > CW on my K3 from N1MM at 30 wpm. I did have to set the weight parameter in > N1MM to 55. > > Interestingly, I once had a problem of horrible CW with variable-length > elements, etc. I > discovered that it was because my wireless network was *not* connected -- > and therefore > was continuously scanning. Probably the driver was disabling interrupts > for long periods. > I simply turned the wireless back on and solved the problem. > > This is just one possible issue. Anti-malware programs can also interfere > with CW > generation. Since I don't do email on my shack computer and only minimally > access the web, > I've removed the anti-virus software and kept only a firewall. If you use > packet while > contesting (I don't), the load on the computer will be increased. And as > someone > mentioned, SO2R is another factor. > > Personally, I am suffering from gadget overload in my shack, and the more > gadgets there > are, the wider you open the door to Murphy. So I don't use Winkey or > similar devices. > > What I suggest is that you a) use a reasonably powerful computer, b) > remove unnecessary > software running in the background (MSCONFIG will show you much of it), > and turn off > unneeded Windows services, and c) look for problems like a wireless > adapter scanning. > > If you still have a problem, then maybe Winkey is the solution for you. > -- > 73, > Vic, K2VCO > Fresno CA > http://www.qsl.net/k2vco > __ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:Elecra
Re: [Elecraft] K3 choppy CW
W0MU Mike Fatchett wrote: > The key is a decent computer. There are many people using very old > computers with minimal ram and cpu speed and they wonder why they have > issues. > > Some people do not have days and hours to figure out why something won't > work especially leading up to a contest, for them a WinKeyer might be a > great solution. To each their own. It's an interesting problem. I have an old Windows 2000 800 MHz laptop which sends perfect CW on my K3 from N1MM at 30 wpm. I did have to set the weight parameter in N1MM to 55. Interestingly, I once had a problem of horrible CW with variable-length elements, etc. I discovered that it was because my wireless network was *not* connected -- and therefore was continuously scanning. Probably the driver was disabling interrupts for long periods. I simply turned the wireless back on and solved the problem. This is just one possible issue. Anti-malware programs can also interfere with CW generation. Since I don't do email on my shack computer and only minimally access the web, I've removed the anti-virus software and kept only a firewall. If you use packet while contesting (I don't), the load on the computer will be increased. And as someone mentioned, SO2R is another factor. Personally, I am suffering from gadget overload in my shack, and the more gadgets there are, the wider you open the door to Murphy. So I don't use Winkey or similar devices. What I suggest is that you a) use a reasonably powerful computer, b) remove unnecessary software running in the background (MSCONFIG will show you much of it), and turn off unneeded Windows services, and c) look for problems like a wireless adapter scanning. If you still have a problem, then maybe Winkey is the solution for you. -- 73, Vic, K2VCO Fresno CA http://www.qsl.net/k2vco __ 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 choppy CW
The key is a decent computer. There are many people using very old computers with minimal ram and cpu speed and they wonder why they have issues. Some people do not have days and hours to figure out why something won't work especially leading up to a contest, for them a WinKeyer might be a great solution. To each their own. Just because it works for one does not mean it works for all. Shall we talk about slopers? :) "A slip of the foot you may soon recover, but a slip of the tongue you may never get over." Ben Franklin -Original Message- From: elecraft-boun...@mailman.qth.net [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Jim Brown Sent: Thursday, February 26, 2009 9:17 AM To: Elecraft List Subject: Re: [Elecraft] K3 choppy CW On Thu, 26 Feb 2009 08:24:30 -0500, Ed K1EP wrote: >Because many hams today like to buy neat gadgets, many times without >understanding what they do. I key my K3 direct from my XP PC using the >serial line. I run speeds in the 30+ wpm. I can achieve rates of over >200+ Q/hour, and I have a very good UBN record. Applications support >it because the interfaces are out there. There are situations in which >you may actually need such a device, but a properly outfitted PC can >support direct keying. I use N1MM, CT, DxBase and other programs with >no problems. Just because something exists, doesn't make it necessary. >Existence is not proof of necessity, and I don't even play a lawyer on >TV. Everyone is free to decide for themselves what is necessary for >their particular situation. YES! I'm a very active contester, and I've never used anything but serial port keying when using a single radio from a single computer. CW sounds just fine at any reasonable contesting speed. The ONLY time I've ever had choppy CW is running TWO radios from the same laptop computer on two ports. It worked, but it was choppy in the way, and to about the same degree, that ZM1A was choppy last weekend. That's a limitation of how the logging programs send CW. So I broke down and bought a WinKey -- ONLY so that I could run SO2R. There is NO GOOD REASON to buy a WinKey to run one K3. There is also no good reason to use expensive interfaces (or transformers) to connect your computer to your radio. All you need are properly wired cables and simple bonding between the chassis of the computer and the chassis of the radio. See http://audiosystemsgroup.com/HamInterfacing.pdf (Power Point) and http://audiosystemsgroup.com/RFI-Ham.pdf (text to go with it) 73, Jim Brown K9YC __ 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
Re: [Elecraft] K3 choppy CW
On Thu, 26 Feb 2009 08:24:30 -0500, Ed K1EP wrote: >Because many hams today like to buy neat gadgets, many times without >understanding what they do. I key my K3 direct from my XP PC using >the serial line. I run speeds in the 30+ wpm. I can achieve rates >of over 200+ Q/hour, and I have a very good UBN record. Applications >support it because the interfaces are out there. There are >situations in which you may actually need such a device, but a >properly outfitted PC can support direct keying. I use N1MM, CT, >DxBase and other programs with no problems. Just because something >exists, doesn't make it necessary. Existence is not proof of >necessity, and I don't even play a lawyer on TV. Everyone is free to >decide for themselves what is necessary for their particular situation. YES! I'm a very active contester, and I've never used anything but serial port keying when using a single radio from a single computer. CW sounds just fine at any reasonable contesting speed. The ONLY time I've ever had choppy CW is running TWO radios from the same laptop computer on two ports. It worked, but it was choppy in the way, and to about the same degree, that ZM1A was choppy last weekend. That's a limitation of how the logging programs send CW. So I broke down and bought a WinKey -- ONLY so that I could run SO2R. There is NO GOOD REASON to buy a WinKey to run one K3. There is also no good reason to use expensive interfaces (or transformers) to connect your computer to your radio. All you need are properly wired cables and simple bonding between the chassis of the computer and the chassis of the radio. See http://audiosystemsgroup.com/HamInterfacing.pdf (Power Point) and http://audiosystemsgroup.com/RFI-Ham.pdf (text to go with it) 73, Jim Brown K9YC __ 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 choppy CW
On Feb 26, 2009, at 7:01 AM, Brian Alsop wrote: > I think it is a bit ironic that for RTTY, external TNC's have become > passe in favor of direct computer decode/encode. Just a property of how computers handle audio. USB Sound Cards go through what are called Isochronous Transfer of USB. These are handled by very high priority tasks, with sufficient audio buffering in the kernel ensure that there are no audio drop outs. Ditto FireWire sound cards, and on-board codecs. This is one reason why I had implemented CW in cocoaModem by using J2A emission (i.e., audio generated CW) instead of A1A emission. It is the only way, short of using WinKey for A1A keying, to ensure that kernel swaps do no interfere with inter-element Morse spacings. (J2A also allows one to implement arbitrary waveshaping of the "keying" waveform. cocoaModem uses a Blackman window to waveshape the CW pulses.) Now, the ironic part is that older operating systems such as MS-DOS and Mac OS 9 work fine with A1A "bit banging" up to very high CW speeds. With today's computers, assuming you can still run those operating system, you can probably run 1000 wpm and still achieve close to perfect Morse inter-element timing. The problem with modern operating systems is that whatever that is running in "user space" can be preempted by the kernel. A key-up or key-down could therefore be delayed just slightly -- but often perceptible by an ear listening to the CW. One way to get around modern operating systems is to write a Morse "device" to run in the kernel (for example, running a WinKey emulator in the kernel). For Mac OS X, this would be a "kernel extension" (kext). Running as a kernel process comes with the associated complexity and dangers (a bug can cause the entire computer to crash). The µH Router, which I wrote for Mac OS X to allow different programs to share a microHAM keyer, actually has a built in "WinKey" emulator, for use with the digiKEYER that does not have a built-in WinKey chip. However, this emulator runs in user space, and now and then you can hear a Morse element being stretched so the rhythm is not perfectly right all the time when running CW even at a slow 25 wpm, even on a dual core computer and even when the emulator is running on a separate high priority (user) thread. 73 Chen, W7AY __ 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 choppy CW
> I think it is a bit ironic that for RTTY, external TNC's have > become passe in favor of direct computer decode/encode. However, > for CW the direction is to the equivalent of a CW TNC-- at least > for the transmit side. Ah, but you are mixing apples and oranges. Even in PC RTTY, bit timing has always been done in hardware. It is handled in the UART (typically an 8250 compatible UART) and not done using a software timing loop that can be effected by operating system loading. Before you point to EXTFSK ... EXTFSK uses a hardware timer in the motherboard chipset - it does not rely on a software timing loop like all of the CW software. > -Original Message- > From: elecraft-boun...@mailman.qth.net > [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Brian Alsop > Sent: Thursday, February 26, 2009 10:02 AM > To: elecraft@mailman.qth.net > Subject: Re: [Elecraft] K3 choppy CW > > > Agree with Ed. If you need WINKEY do it, if you don't why add to > complication? > Many of us don't. KIS. > > I think it is a bit ironic that for RTTY, external TNC's have become > passe in favor of direct computer decode/encode. > However, for CW the direction is to the equivalent of a CW TNC-- at > least for the transmit side. So today we have to go via keyboard, > computer, computer program, PC port, PIC, PIC program and > transistor to > emulate closing a J-38 key or bug. > > 73 de Brian/K3KO > > Hi tech still uses 4 billion year old quartz and silicon to > get their > performance. > The K3 is made up of pre Sol stardust. > > Ed K1EP wrote: > > >At 2/26/2009 08:05 AM, R. Kevin Stover wrote: > > > > > >>Everybody should be using a Winkey to key CW. > >> > >> > > > >Why? > > > > > > > >>Some people will deny that keying directly from an serial port > >>controlled by windows causes keying errors. When we ran DOS, the > >>applications could have unfettered access to the ports. You > could also > >>easily harness the system clock and use it rather than the OS to > >>supply the timing for CW. It was easy to background a process like > >>sending CW knowing you had control of the port when you > needed it. Not > >>so with Windows98 and up. XP is especially bad. > >> > >>Ever had an application or the OS grab a hold of a USB, serial or > >>parallel port and not let go when the application or process > >>terminated? It never happened in DOS. > >> > >>One question for the doubters. If a winkey like device > isn't necessary > >>to send properly timed CW, why do several hardware manufacturers, > >>Micro Ham, US Interface, Rig Expert, and nearly all general and > >>contest logging applications support it? Just to make K1EL rich? > >> > >> > > > >Because many hams today like to buy neat gadgets, many times without > >understanding what they do. I key my K3 direct from my XP PC using > >the serial line. I run speeds in the 30+ wpm. I can achieve rates > >of over 200+ Q/hour, and I have a very good UBN record. > Applications > >support it because the interfaces are out there. There are > >situations in which you may actually need such a device, but a > >properly outfitted PC can support direct keying. I use N1MM, CT, > >DxBase and other programs with no problems. Just because something > >exists, doesn't make it necessary. Existence is not proof of > >necessity, and I don't even play a lawyer on TV. Everyone > is free to > >decide for themselves what is necessary for their particular > situation. > > > > > >__ > >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 __ 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 choppy CW
Agree with Ed. If you need WINKEY do it, if you don't why add to complication? Many of us don't. KIS. I think it is a bit ironic that for RTTY, external TNC's have become passe in favor of direct computer decode/encode. However, for CW the direction is to the equivalent of a CW TNC-- at least for the transmit side. So today we have to go via keyboard, computer, computer program, PC port, PIC, PIC program and transistor to emulate closing a J-38 key or bug. 73 de Brian/K3KO Hi tech still uses 4 billion year old quartz and silicon to get their performance. The K3 is made up of pre Sol stardust. Ed K1EP wrote: >At 2/26/2009 08:05 AM, R. Kevin Stover wrote: > > >>Everybody should be using a Winkey to key CW. >> >> > >Why? > > > >>Some people will deny that keying directly from an serial port >>controlled by windows causes keying errors. When we ran DOS, the >>applications could have unfettered access to the ports. You could also >>easily harness the system clock and use it rather than the OS to supply >>the timing for CW. It was easy to background a process like sending CW >>knowing you had control of the port when you needed it. Not so with >>Windows98 and up. XP is especially bad. >> >>Ever had an application or the OS grab a hold of a USB, serial or >>parallel port and not let go when the application or process terminated? >>It never happened in DOS. >> >>One question for the doubters. If a winkey like device isn't necessary >>to send properly timed CW, why do several hardware manufacturers, Micro >>Ham, US Interface, Rig Expert, and nearly all general and contest >>logging applications support it? Just to make K1EL rich? >> >> > >Because many hams today like to buy neat gadgets, many times without >understanding what they do. I key my K3 direct from my XP PC using >the serial line. I run speeds in the 30+ wpm. I can achieve rates >of over 200+ Q/hour, and I have a very good UBN record. Applications >support it because the interfaces are out there. There are >situations in which you may actually need such a device, but a >properly outfitted PC can support direct keying. I use N1MM, CT, >DxBase and other programs with no problems. Just because something >exists, doesn't make it necessary. Existence is not proof of >necessity, and I don't even play a lawyer on TV. Everyone is free to >decide for themselves what is necessary for their particular situation. > > >__ >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
Re: [Elecraft] K3 choppy CW
Elecrafters: About a year ago, I finally hooked up my K2 to a computer. Following the advice of several list members, I got a WinKey keyer instead of trying to run CW keying through the serial port. The WinKey is inexpensive, easy to set up with the N1MM contest program, and provides flawless keying. (I have no financial interest in WinKey; I'm merely a happy customer.) In the interest of full disclosure, I have not attempted to key my K2 directly through the serial port. At the time we were discussing this on the list, there was a minority opinion that the WinKey was not really necessary. The argument was that with modern high speed computers the serial port can handle everything. Nevertheless, if you're keying a computer controlled Elecraft rig via the serial port and you get "choppy" CW, and you install a WinKey and the problem vanishes, it looks like the result speaks for itself. 73, Steve Kercel AA4AK R. Kevin Stover wrote: > Everybody should be using a Winkey to key CW. > > Some people will deny that keying directly from an serial port > controlled by windows causes keying errors. When we ran DOS, the > applications could have unfettered access to the ports. You could also > easily harness the system clock and use it rather than the OS to supply > the timing for CW. It was easy to background a process like sending CW > knowing you had control of the port when you needed it. Not so with > Windows98 and up. XP is especially bad. > > Ever had an application or the OS grab a hold of a USB, serial or > parallel port and not let go when the application or process terminated? > It never happened in DOS. > > One question for the doubters. If a winkey like device isn't necessary > to send properly timed CW, why do several hardware manufacturers, Micro > Ham, US Interface, Rig Expert, and nearly all general and contest > logging applications support it? Just to make K1EL rich? > > W0MU Mike Fatchett wrote: > >> N1MM users have had similar issues. I don't know if AB7R's fix works but >> many have just gone to a Winkey keyer as a solution. I have one built into >> my SO2R MK2R+ Microham devices so I have never seen this issue. >> >> >> "A slip of the foot you may soon recover, but a slip of the tongue you may >> never get over." Ben Franklin >> > > __ 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 choppy CW
>One question for the doubters. If a winkey like device isn't necessary >to send properly timed CW, why do several hardware manufacturers, Micro >Ham, US Interface, Rig Expert, and nearly all general and contest >logging applications support it? Just to make K1EL rich? In addition to correct CW timing irrespective of the PC interface, the Winkey chip allows the user to fine-tune keying compensation to offset the effect of the so-called "dit shortening" in QSK mode, an anomaly that exists on nearly all high-end transceivers today. Much of my operating is conducted over the Internet where timing latencies can be bad enough that CW will oftentimes "stutter" without some means of synchronizing the path. With Winkey, CW is perfectly timed over the Internet when using a pair Winkey devices -- and they don't even need to be matched across manufacturers. For example, I am using a microHam interface at the host end and it synchronizes perfectly with a WinkeyerUSB device at the client end. For what it does, Winkey is an exceptional value for contesters, Internet users, and even folks whose operating is limited to casual CW QSOs. Paul, W9AC __ 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 choppy CW
At 2/26/2009 08:05 AM, R. Kevin Stover wrote: >Everybody should be using a Winkey to key CW. Why? >Some people will deny that keying directly from an serial port >controlled by windows causes keying errors. When we ran DOS, the >applications could have unfettered access to the ports. You could also >easily harness the system clock and use it rather than the OS to supply >the timing for CW. It was easy to background a process like sending CW >knowing you had control of the port when you needed it. Not so with >Windows98 and up. XP is especially bad. > >Ever had an application or the OS grab a hold of a USB, serial or >parallel port and not let go when the application or process terminated? >It never happened in DOS. > >One question for the doubters. If a winkey like device isn't necessary >to send properly timed CW, why do several hardware manufacturers, Micro >Ham, US Interface, Rig Expert, and nearly all general and contest >logging applications support it? Just to make K1EL rich? Because many hams today like to buy neat gadgets, many times without understanding what they do. I key my K3 direct from my XP PC using the serial line. I run speeds in the 30+ wpm. I can achieve rates of over 200+ Q/hour, and I have a very good UBN record. Applications support it because the interfaces are out there. There are situations in which you may actually need such a device, but a properly outfitted PC can support direct keying. I use N1MM, CT, DxBase and other programs with no problems. Just because something exists, doesn't make it necessary. Existence is not proof of necessity, and I don't even play a lawyer on TV. Everyone is free to decide for themselves what is necessary for their particular situation. __ 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 choppy CW
Everybody should be using a Winkey to key CW. Some people will deny that keying directly from an serial port controlled by windows causes keying errors. When we ran DOS, the applications could have unfettered access to the ports. You could also easily harness the system clock and use it rather than the OS to supply the timing for CW. It was easy to background a process like sending CW knowing you had control of the port when you needed it. Not so with Windows98 and up. XP is especially bad. Ever had an application or the OS grab a hold of a USB, serial or parallel port and not let go when the application or process terminated? It never happened in DOS. One question for the doubters. If a winkey like device isn't necessary to send properly timed CW, why do several hardware manufacturers, Micro Ham, US Interface, Rig Expert, and nearly all general and contest logging applications support it? Just to make K1EL rich? W0MU Mike Fatchett wrote: > N1MM users have had similar issues. I don't know if AB7R's fix works but > many have just gone to a Winkey keyer as a solution. I have one built into > my SO2R MK2R+ Microham devices so I have never seen this issue. > > > "A slip of the foot you may soon recover, but a slip of the tongue you may > never get over." Ben Franklin -- R. Kevin Stover, ACØH __ 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] K3 Choppy CW
>At ZM1A (multi-two) during the ARRL DX CW contest we received some reports >of "choppy" CW when CT was keying via the 'Key' socket... During the same contest, I used NA under DOS in an older computer, with NA sending via a W9XT contest card. I could have sworn (actually, I did) that my weighting was lighter than 'normal' (I prefer it slightly on the 'heavy' side). I had to increase the NA keyer weighting from 55% to 60% for it to sound right to me. This exact computer set-up has worked to my satisfaction for years, using radio "Y". (It has transmit inhibit until the amp has switched.) I'll try fiddling with TX DLY as AB7R suggested. Mine is set at 10, and the Acom 1000 doesn't seem to mind. I don't recall this 'light keying' situation using a K3 with N1MM and a MicroHam keyer at VP5W, but there, ALL the hardware was different. Ralph, VE7XF __ 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 choppy CW
Hi Greg, Many thanks indeed - setting the TX DLY to 10 restored the CW to normal operation. I had set TX DLY to 20 to protect the amp antenna relays (open-frame), of which we have lost three in two amps during 2008. I'll install vacuum relays before ARRL SSB. Thanks again. 73, Ken ZL1AIH --- On Thu, 26/2/09, Greg - AB7R wrote: From: Greg - AB7R Subject: Re: [Elecraft] K3 choppy CW To: elecraft@mailman.qth.net, "Robert Mccormack" Received: Thursday, 26 February, 2009, 12:49 PM Set the TX DLY menu item to a lower settingI found that anything below 10 worked OK. - 73, Greg - AB7R Whidbey Island WA NA-065 On Wed Feb 25 15:41 , Robert Mccormack sent: >At ZM1A (multi-two) during the ARRL DX CW contest we received some reports of "choppy" CW when CT was keying via the 'Key' socket. >Monitoring the signal with a K2 (dummy load in antenna socket) __ 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 choppy CW
N1MM users have had similar issues. I don't know if AB7R's fix works but many have just gone to a Winkey keyer as a solution. I have one built into my SO2R MK2R+ Microham devices so I have never seen this issue. "A slip of the foot you may soon recover, but a slip of the tongue you may never get over." Ben Franklin -Original Message- From: elecraft-boun...@mailman.qth.net [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Robert Mccormack Sent: Wednesday, February 25, 2009 4:42 PM To: elecraft@mailman.qth.net Subject: Re: [Elecraft] K3 choppy CW At ZM1A (multi-two) during the ARRL DX CW contest we received some reports of "choppy" CW when CT was keying via the 'Key' socket. Monitoring the signal with a K2 (dummy load in antenna socket) confirmed the reports. CW sent using the paddle was normal. Both 'station one' K3 and 'station two' K3 had the same problem - substituting a spare K3 made no difference. BTW, it's not RF getting into the computer - the keying is just as bad at 5 watts out. We continued operating, using the K3 memories for CQing and the exchange - luckily it wasn't a serial number. I don't know when this "choppy" keying problem started because the K3s are only keyed by CT during contests, but today we tried a spare 746Pro which eliminated the problem. So the problem is specific to our K3s, all of which had MCU 2.67 installed plus the 'CW rise time' and RS-232 RF immunity mods in early February... Anyone else had this problem? 73, Ken ZL1AIH (ZM1A in contests) __ 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
Re: [Elecraft] K3 choppy CW
On Thu, 26 Feb 2009 10:41:43 +1100 (EST), Robert Mccormack wrote: >So the problem is specific to our K3s I suggest that you try the K9YC serial cable. http://audiosystemsgroup.com/HamInterfacing.pdf http://audiosystemsgroup.com/RFI-Ham.pdf The first reference consists of Power Point slides, and the serial cable is near the end. The second reference is a tutorial, and the serial cable is in Chapter 8 -- Solving Problems in the Shack. 73, Jim K9YC __ 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 choppy CW
Set the TX DLY menu item to a lower settingI found that anything below 10 worked OK. - 73, Greg - AB7R Whidbey Island WA NA-065 On Wed Feb 25 15:41 , Robert Mccormack sent: >At ZM1A (multi-two) during the ARRL DX CW contest we received some reports of "choppy" CW when CT was keying via the 'Key' socket. >Monitoring the signal with a K2 (dummy load in antenna socket) confirmed the reports. CW sent using the paddle was normal. >Both 'station one' K3 and 'station two' K3 had the same problem - substituting >a spare K3 made no difference. BTW, it's not RF getting into the computer - the keying is just as bad at 5 watts out. > >We continued operating, using the K3 memories for CQing and the exchange - >luckily it wasn't a serial number. > >I don't know when this "choppy" keying problem started because the K3s are >only keyed by CT during contests, but today we tried a spare 746Pro which eliminated the problem. > >So the problem is specific to our K3s, all of which had MCU 2.67 installed >plus the 'CW rise time' and RS-232 RF immunity mods in early February... > >Anyone else had this problem? > >73, >Ken ZL1AIH (ZM1A in contests) > > > > > > >__ >Elecraft mailing list >Home: http://mailman.qth.net/mailman/listinfo/elecraft >Help: http://mailman.qth.net/mmfaq.htm >Post: Elecraft@mailman.qth.net','','','')">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
Re: [Elecraft] K3 choppy CW
At ZM1A (multi-two) during the ARRL DX CW contest we received some reports of "choppy" CW when CT was keying via the 'Key' socket. Monitoring the signal with a K2 (dummy load in antenna socket) confirmed the reports. CW sent using the paddle was normal. Both 'station one' K3 and 'station two' K3 had the same problem - substituting a spare K3 made no difference. BTW, it's not RF getting into the computer - the keying is just as bad at 5 watts out. We continued operating, using the K3 memories for CQing and the exchange - luckily it wasn't a serial number. I don't know when this "choppy" keying problem started because the K3s are only keyed by CT during contests, but today we tried a spare 746Pro which eliminated the problem. So the problem is specific to our K3s, all of which had MCU 2.67 installed plus the 'CW rise time' and RS-232 RF immunity mods in early February... Anyone else had this problem? 73, Ken ZL1AIH (ZM1A in contests) __ 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
