Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
Yes, I noticed this on my bug also. This happens almost entirely on characters that start with a 'dah'. I think this is because the index finger is off the paddle between characters and the initial attack is a little more forceful. Subsequent dahs in the same character sound fine, but that first one has a 'tick' (a spike by the sound of it). No problem at all with the dits. BTW, I don't think this is a matter of bug adjustment; you can get the same effect by tapping down on a straight key from a slight distance. So it is a matter of technique. I can avoid it on the bug by keeping my index finger resting against the paddle all the time and avoiding that first hard strike, but can't send as well that way; maybe with practice... 73, Drew AF2Z lstavenhagen wrote: Heh. The new QSK is so fast it picks up bounce on the Dah contact on my Vibroplex, hi hi. Zowie 73, LS W5QD -- View this message in context: http://elecraft.365791.n2.nabble.com/K3-Beta-Firmware-Rev-4-03-CW-mode-Ultra-fast-break-in-VOX-CW-up-to-100-WPM-tp5178377p5198534.html Sent from the [K3] 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 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
I've noticed this as well. For me it's a Tick sound EVERY time I hit the Dah side of my bug. Nothing on the dit side, regardless of the speed or preasure. I thought at first it was the force that I was using.. So I tried pushing the lever slowly and carefully against the Dah contact, and it didn't make the sound.. So then I tried lighting my touch on the dah side while I was sending, and sure enough it was still there. So, I switched from my Begali Intrepid to my Vibroplex Original, and then I found that the ticking sound was GONE all together! Now I'm competely confused. What does the one dah side have that the other bug's doesn't??? Gold Contacts? A bad ground connection? More surface contact area, a larger area? You tell me. I LOVE the new QSK (QRQ), but if I had to deal with that Tick sound on the dah contact, I would just not use it. Shame. Date: Sat, 19 Jun 2010 05:37:18 -0700 From: drew...@verizon.net To: elecraft@mailman.qth.net Subject: Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM) Yes, I noticed this on my bug also. This happens almost entirely on characters that start with a 'dah'. I think this is because the index finger is off the paddle between characters and the initial attack is a little more forceful. Subsequent dahs in the same character sound fine, but that first one has a 'tick' (a spike by the sound of it). No problem at all with the dits. BTW, I don't think this is a matter of bug adjustment; you can get the same effect by tapping down on a straight key from a slight distance. So it is a matter of technique. I can avoid it on the bug by keeping my index finger resting against the paddle all the time and avoiding that first hard strike, but can't send as well that way; maybe with practice... 73, Drew AF2Z _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3 __ 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 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
For speeds that people can send with a bug (usually) the regular CW seems to work quite fine. CW plus is primarily intended to support very fast speeds, often heard now with operators sending with keyboards and other electronic keying devices. Debouncing a bug to prevent false starts when someone has poor contacts on one side is not one of the design goals for CW plus I've heard passed about, though the buffering of keying circuits used in most transmitters now has a small amount of debouncing effect which has likely been hiding the glitch. This would include the regular CW of the K3. With CW plus, however, that small false start has to be taken as legitimate, because pausing a small amount to make sure that the operator really means it, would make high speed CW sound jerky. CW plus was made to faithfully reproduce the keying at very high speeds, and has to take the blip seriously. Cleaning and proper adjustment of bug contacts were always needed in the day, because the condition you are talking about would result in scratchy keying...which was never blamed on the transmitter, only on the op who was not keeping his bug greased. The need is greater now because noone is keying the +100V or more found on the old open cathode circuits any more, and bad bug contacts will easier bother a mere 12 volts on the key, and bother 5 volts even worse. 73, Guy. On Sat, Jun 19, 2010 at 11:11 AM, The Smiths notforc...@hotmail.com wrote: I've noticed this as well. For me it's a Tick sound EVERY time I hit the Dah side of my bug. Nothing on the dit side, regardless of the speed or preasure. I thought at first it was the force that I was using.. So I tried pushing the lever slowly and carefully against the Dah contact, and it didn't make the sound.. So then I tried lighting my touch on the dah side while I was sending, and sure enough it was still there. So, I switched from my Begali Intrepid to my Vibroplex Original, and then I found that the ticking sound was GONE all together! Now I'm competely confused. What does the one dah side have that the other bug's doesn't??? Gold Contacts? A bad ground connection? More surface contact area, a larger area? You tell me. I LOVE the new QSK (QRQ), but if I had to deal with that Tick sound on the dah contact, I would just not use it. Shame. Date: Sat, 19 Jun 2010 05:37:18 -0700 From: drew...@verizon.net To: elecraft@mailman.qth.net Subject: Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM) Yes, I noticed this on my bug also. This happens almost entirely on characters that start with a 'dah'. I think this is because the index finger is off the paddle between characters and the initial attack is a little more forceful. Subsequent dahs in the same character sound fine, but that first one has a 'tick' (a spike by the sound of it). No problem at all with the dits. BTW, I don't think this is a matter of bug adjustment; you can get the same effect by tapping down on a straight key from a slight distance. So it is a matter of technique. I can avoid it on the bug by keeping my index finger resting against the paddle all the time and avoiding that first hard strike, but can't send as well that way; maybe with practice... 73, Drew AF2Z _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3 __ 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 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
I was not complaining about the K3 QSK+ or requesting that Elecraft do anything at all about this. Merely commenting on the curious effect (because it is the dit contact on bugs that is typically screwed up; not the dahs). I noted that it was a matter of technique, and I've found that I can reduce the dah 'tick' entirely by keeping my index finger on the paddle instead of slamming it like you do with the dit side. Actually, I think this may be better bug technique in any case because it is only the dit side that you need to inject the kinetic energy into. Eliminating the unnecessary finger travel on the dah side might allow greater speed (if I can get used to it...) Yes, you can use a bug in normal QSK mode perfectly well for all intents and purspses. But the QSK+ mode does sound better, even at non-QRQ speeds. 73, Drew AF2Z On Sat, 19 Jun 2010 12:09:31 -0400, Guy.wrote: For speeds that people can send with a bug (usually) the regular CW seems to work quite fine. CW plus is primarily intended to support very fast speeds, often heard now with operators sending with keyboards and other electronic keying devices. Debouncing a bug to prevent false starts when someone has poor contacts on one side is not one of the design goals for CW plus I've heard passed about, though the buffering of keying circuits used in most transmitters now has a small amount of debouncing effect which has likely been hiding the glitch. This would include the regular CW of the K3. With CW plus, however, that small false start has to be taken as legitimate, because pausing a small amount to make sure that the operator really means it, would make high speed CW sound jerky. CW plus was made to faithfully reproduce the keying at very high speeds, and has to take the blip seriously. Cleaning and proper adjustment of bug contacts were always needed in the day, because the condition you are talking about would result in scratchy keying...which was never blamed on the transmitter, only on the op who was not keeping his bug greased. The need is greater now because noone is keying the +100V or more found on the old open cathode circuits any more, and bad bug contacts will easier bother a mere 12 volts on the key, and bother 5 volts even worse. 73, Guy. __ 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 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
Drew, you have been watching the lady operator with the long finger nails on the Night-of-Nights Utube video too much. You don't need all that hand waving and finger motion to send with a bug! Willis 'Cookie' Cooke K5EWJ From: drewko drew...@verizon.net To: Guy Olinger K2AV olin...@bellsouth.net Cc: Elecraft@mailman.qth.net Sent: Sat, June 19, 2010 11:58:02 AM Subject: Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM) I was not complaining about the K3 QSK+ or requesting that Elecraft do anything at all about this. Merely commenting on the curious effect (because it is the dit contact on bugs that is typically screwed up; not the dahs). I noted that it was a matter of technique, and I've found that I can reduce the dah 'tick' entirely by keeping my index finger on the paddle instead of slamming it like you do with the dit side. Actually, I think this may be better bug technique in any case because it is only the dit side that you need to inject the kinetic energy into. Eliminating the unnecessary finger travel on the dah side might allow greater speed (if I can get used to it...) Yes, you can use a bug in normal QSK mode perfectly well for all intents and purspses. But the QSK+ mode does sound better, even at non-QRQ speeds. 73, Drew AF2Z On Sat, 19 Jun 2010 12:09:31 -0400, Guy.wrote: For speeds that people can send with a bug (usually) the regular CW seems to work quite fine. CW plus is primarily intended to support very fast speeds, often heard now with operators sending with keyboards and other electronic keying devices. Debouncing a bug to prevent false starts when someone has poor contacts on one side is not one of the design goals for CW plus I've heard passed about, though the buffering of keying circuits used in most transmitters now has a small amount of debouncing effect which has likely been hiding the glitch. This would include the regular CW of the K3. With CW plus, however, that small false start has to be taken as legitimate, because pausing a small amount to make sure that the operator really means it, would make high speed CW sound jerky. CW plus was made to faithfully reproduce the keying at very high speeds, and has to take the blip seriously. Cleaning and proper adjustment of bug contacts were always needed in the day, because the condition you are talking about would result in scratchy keying...which was never blamed on the transmitter, only on the op who was not keeping his bug greased. The need is greater now because noone is keying the +100V or more found on the old open cathode circuits any more, and bad bug contacts will easier bother a mere 12 volts on the key, and bother 5 volts even worse. 73, Guy. __ 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 Beta Firmware Rev. 4.03: CW+ mode(Ultra-fastbreak-in; VOX-CW up to 100 WPM)
CW plus was made to faithfully reproduce the keying at very high speeds, and has to take the blip seriously. This sounds like an identical thread from last August. Just as some CW keyer circuits require debouncing when using paddle contacts having dissimilar metals, debouncing a bug is a good idea when used in the CW + application. My preferred method of debouncing uses a Schottky hex buffer with a 2N7000 on the key line. In my experience with this circuit, it completely smoothes the key contact transitions on a bug. Another option that may work comes from microHam. K1EL developed a PIC-based debouncing circuit powered by a coin battery. It was initially used when users of certain Begali paddles were experiencing contact bounce resulting from dissimilar metals being used on early Begali key contacts. I suspect that the microHam de-bouncer would be an excellent off-the-shelf solution to key bounce problems. http://www.microham-usa.com/Products/Begali.html 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 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
I'm sorry Guy, but I'm not hearing bounce on my key. And I can assure you that my bug doesn't have poor contacts on either side. I get ONE single Dah when sending a Dah.. What I hear is a TICK sound, and not a tone when I first key down. If speed and bounce were the issue than I would be sure to hear it on the dit side regardless of the speed... This problem is something else. Furthermore I don't see why QRQ type QSK mode is ONLY for people going fast.. Personally I send as slow as 18wpm and as high as 35 wpm on my bugs, and enjoy the fast switching of the new CW+ mode. In my opinion THIS is what QSK SHOULD sound like.. I would recommend that someone actually look into keying with more than just the paddles or keyboards. Perhaps you have misunderstood that people are not trying to complain here Guy, yet let the Elecraft guys know that they should look into this. That's why it's still BETA software at this point... Don't poo poo it so fast. Date: Sat, 19 Jun 2010 12:09:31 -0400 Subject: Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM) From: olin...@bellsouth.net To: notforc...@hotmail.com CC: drew...@verizon.net; elecraft@mailman.qth.net For speeds that people can send with a bug (usually) the regular CW seems to work quite fine. CW plus is primarily intended to support very fast speeds, often heard now with operators sending with keyboards and other electronic keying devices. Debouncing a bug to prevent false starts when someone has poor contacts on one side is not one of the design goals for CW plus I've heard passed about, though the buffering of keying circuits used in most transmitters now has a small amount of debouncing effect which has likely been hiding the glitch. This would include the regular CW of the K3. With CW plus, however, that small false start has to be taken as legitimate, because pausing a small amount to make sure that the operator really means it, would make high speed CW sound jerky. CW plus was made to faithfully reproduce the keying at very high speeds, and has to take the blip seriously. Cleaning and proper adjustment of bug contacts were always needed in the day, because the condition you are talking about would result in scratchy keying...which was never blamed on the transmitter, only on the op who was not keeping his bug greased. The need is greater now because noone is keying the +100V or more found on the old open cathode circuits any more, and bad bug contacts will easier bother a mere 12 volts on the key, and bother 5 volts even worse. 73, Guy. On Sat, Jun 19, 2010 at 11:11 AM, The Smiths notforc...@hotmail.com wrote: I've noticed this as well. For me it's a Tick sound EVERY time I hit the Dah side of my bug. Nothing on the dit side, regardless of the speed or preasure. I thought at first it was the force that I was using.. So I tried pushing the lever slowly and carefully against the Dah contact, and it didn't make the sound.. So then I tried lighting my touch on the dah side while I was sending, and sure enough it was still there. So, I switched from my Begali Intrepid to my Vibroplex Original, and then I found that the ticking sound was GONE all together! Now I'm competely confused. What does the one dah side have that the other bug's doesn't??? Gold Contacts? A bad ground connection? More surface contact area, a larger area? You tell me. I LOVE the new QSK (QRQ), but if I had to deal with that Tick sound on the dah contact, I would just not use it. Shame. Date: Sat, 19 Jun 2010 05:37:18 -0700 From: drew...@verizon.net To: elecraft@mailman.qth.net Subject: Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM) Yes, I noticed this on my bug also. This happens almost entirely on characters that start with a 'dah'. I think this is because the index finger is off the paddle between characters and the initial attack is a little more forceful. Subsequent dahs in the same character sound fine, but that first one has a 'tick' (a spike by the sound of it). No problem at all with the dits. BTW, I don't think this is a matter of bug adjustment; you can get the same effect by tapping down on a straight key from a slight distance. So it is a matter of technique. I can avoid it on the bug by keeping my index finger resting against the paddle all the time and avoiding that first hard strike, but can't send as well that way; maybe with practice... 73, Drew AF2Z _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3 __ Elecraft mailing list Home: http
Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode(Ultra-fastbreak-in; VOX-CW up to 100 WPM)
This sounds like an identical thread from last August. Just as some CW keyer circuits require debouncing when using paddle contacts having dissimilar metals, debouncing a bug is a good idea when used in the CW + application. The dissimilar metals issue was not one of bounce. It was (and still is) because many of the new alloys include aluminum or other metals that produce a semiconducting oxide. That oxide results in a diode junction at the contacts with an offset (minimum contact voltage) of about 0.5V which upsets low power CMOS inputs or PIC devices that rely on differences in voltages to detect left, right, and both paddle closures on a single input pin. I suspect that the microHam de-bouncer would be an excellent off-the-shelf solution to key bounce problems. While the K1EL PIC has some debouncing properties, I suspect the real benefit is due to providing a buffered output that goes completely to ground (clean contacts). All current microHAM products that use the original K1EL WinKey now contain buffers (voltage comparators) to raise the switching threshold, eliminating any problem with offset due to the diode effect. 73, ... Joe Subich, W4TV microHAM America, LLC. http://www.microHAM-USA.com http://groups.yahoo.com/group/microHAM On 6/19/2010 2:18 PM, Paul Christensen wrote: CW plus was made to faithfully reproduce the keying at very high speeds, and has to take the blip seriously. This sounds like an identical thread from last August. Just as some CW keyer circuits require debouncing when using paddle contacts having dissimilar metals, debouncing a bug is a good idea when used in the CW + application. My preferred method of debouncing uses a Schottky hex buffer with a 2N7000 on the key line. In my experience with this circuit, it completely smoothes the key contact transitions on a bug. Another option that may work comes from microHam. K1EL developed a PIC-based debouncing circuit powered by a coin battery. It was initially used when users of certain Begali paddles were experiencing contact bounce resulting from dissimilar metals being used on early Begali key contacts. I suspect that the microHam de-bouncer would be an excellent off-the-shelf solution to key bounce problems. http://www.microham-usa.com/Products/Begali.html 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 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
Hi Cookie, I have seen that video and it is well beyond the degree of motion that I use on the bug. In fact, I have a Viz right-angle bug which is a lighter key and requires a lighter touch than the typical Vibroplex. And I use it without benefit of any epoxy, superglue, and/or anchor bolts holding it down to the desk as a lot of bug users seem to do. If I was really slamming it like in the video it would walk off the desk in short order, haha! Even so, that slight initial tap on the leading dahs is enough to make my K3 go TICK! 73, Drew AF2Z On Sat, 19 Jun 2010 10:05:52 -0700 (PDT), you wrote: Drew, you have been watching the lady operator with the long finger nails on the Night-of-Nights Utube video too much. You don't need all that hand waving and finger motion to send with a bug! Willis 'Cookie' Cooke K5EWJ __ 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 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
Well, the Elecraft is getting the signal from both your bug's dit and your dah contact on the same lead. And if your closures are perfect, by what process is the K3 able to determine that the contact is from only one side of a bug to give just that one side a tick? And when the tick can be cured as was posted by changing hand technique? The closure waveform is clearly not the same for dit and dah. If you were sending code on an old 807 rig, one of the old time locals would be on your case for scratchy keying, and tell you which contact on your bug it was. Your denials of bug contact complicity at the club meeting would just get you looks. What I find interesting out of this is that there is enough interest in using bugs, that a debouncer option for mechanical keys is a reasonable request. Getting bug contacts correct for using on low voltage circuits IS and HAS BEEN a real PITA, never needing to be broached by the old-timers that designed the bugs. The CW+ was introduced particularly to serve high speed CW interests that were not being addressed, with dits at some speeds pretty close to a click. Not that someone else shouldn't use it. The current settings are wonderful for the very high speed stuff and I do hope that Wayne will not degrade it to debounce mechanical bugs being operated at speeds serviced well at the regular CW. Just improve the QSK at the regular CW setting, although I know he is fighting state change processing budgets. 73, Guy On Sat, Jun 19, 2010 at 2:27 PM, The Smiths notforc...@hotmail.com wrote: I'm sorry Guy, but I'm not hearing bounce on my key. And I can assure you that my bug doesn't have poor contacts on either side. I get ONE single Dah when sending a Dah.. What I hear is a TICK sound, and not a tone when I first key down. If speed and bounce were the issue than I would be sure to hear it on the dit side regardless of the speed... This problem is something else. Furthermore I don't see why QRQ type QSK mode is ONLY for people going fast.. Personally I send as slow as 18wpm and as high as 35 wpm on my bugs, and enjoy the fast switching of the new CW+ mode. In my opinion THIS is what QSK SHOULD sound like.. I would recommend that someone actually look into keying with more than just the paddles or keyboards. Perhaps you have misunderstood that people are not trying to complain here Guy, yet let the Elecraft guys know that they should look into this. That's why it's still BETA software at this point... Don't poo poo it so fast. Date: Sat, 19 Jun 2010 12:09:31 -0400 Subject: Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM) From: olin...@bellsouth.net To: notforc...@hotmail.com CC: drew...@verizon.net; elecraft@mailman.qth.net For speeds that people can send with a bug (usually) the regular CW seems to work quite fine. CW plus is primarily intended to support very fast speeds, often heard now with operators sending with keyboards and other electronic keying devices. Debouncing a bug to prevent false starts when someone has poor contacts on one side is not one of the design goals for CW plus I've heard passed about, though the buffering of keying circuits used in most transmitters now has a small amount of debouncing effect which has likely been hiding the glitch. This would include the regular CW of the K3. With CW plus, however, that small false start has to be taken as legitimate, because pausing a small amount to make sure that the operator really means it, would make high speed CW sound jerky. CW plus was made to faithfully reproduce the keying at very high speeds, and has to take the blip seriously. Cleaning and proper adjustment of bug contacts were always needed in the day, because the condition you are talking about would result in scratchy keying...which was never blamed on the transmitter, only on the op who was not keeping his bug greased. The need is greater now because noone is keying the +100V or more found on the old open cathode circuits any more, and bad bug contacts will easier bother a mere 12 volts on the key, and bother 5 volts even worse. 73, Guy. On Sat, Jun 19, 2010 at 11:11 AM, The Smiths notforc...@hotmail.com wrote: I've noticed this as well. For me it's a Tick sound EVERY time I hit the Dah side of my bug. Nothing on the dit side, regardless of the speed or preasure. I thought at first it was the force that I was using.. So I tried pushing the lever slowly and carefully against the Dah contact, and it didn't make the sound.. So then I tried lighting my touch on the dah side while I was sending, and sure enough it was still there. So, I switched from my Begali Intrepid to my Vibroplex Original, and then I found that the ticking sound was GONE all together! Now I'm competely confused. What does the one dah side have that the other bug's doesn't??? Gold Contacts? A bad ground connection? More surface contact
Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
From the time of CW key closure to RF, I measure a blistering 7 ms, beating the IC-7700 I measured by a solid 2 ms. It's that kind of transition that makes for super-fast QSK. Well done. Paul, W9AC - Original Message - From: Hector Padron ad4c2...@yahoo.com To: elecraft@mailman.qth.net Sent: Monday, June 14, 2010 6:53 PM Subject: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM) I just finished to install beta 4.03 and the process was nice and easy,no problems at all,radio works as it supouse to work,now I can send 70 wpm with an extremly fast brake-in,I set the delay at zero and its instantaneous the receiver cuts,I can hear anybody if he brakes me no matter how fasta I could be going,I love it once again Elecraft team did a good job,thanks AD4C If you see a woman handling a cell phone on her hands while she is driving,do please stay away from her.!! --- On Mon, 6/14/10, Wayne Burdick n...@elecraft.com wrote: From: Wayne Burdick n...@elecraft.com Subject: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fast break-in; VOX-CW up to 100 WPM) To: Elecraft Reflector elecraft@mailman.qth.net, elecraft...@yahoogroups.com, elecr...@yahoogroups.com Date: Monday, June 14, 2010, 5:02 PM K3 beta-test firmware revision 4.02 (with DSP rev. 2.60) is now available. See full release notes below. The most significant addition is CW+ mode. CW+ provides extremely fast break-in (receive recovery between code elements up to about 70 WPM) as well as VOX CW operation at speeds up to 100 WPM. We added CW+ mode primarily for high-speed (QRQ) operators, but the new, faster break-in applies at slower speeds, as well. Please give it a try. NOTE: There are significant limitations to CW+ mode at present, as described below. Please review them carefully. Please send any questions to k3supp...@elecraft.com. For instructions on how to load beta firmware, see: http://www.elecraft.com/K3/k3_software.htm 73, Wayne N6KR * * * MCU 4.03 / DSP 2.60, 6-10-2010 * 75 BAUD (100 WPM) RTTY SUPPORT: The built-in encoder/decoder (DATA/FSK-D) now supports both 45 and 75 baud. To select the desired rate, hold the DATA MD switch, then rotate VFO A. * ULTRA-FAST BREAK-IN AND QRQ CW (“CW+”): If you set CONFIG:CW QRQ to ON in the menu, the K3 will provide extremely fast break-in at all CW speeds. It will also allow both the internal keyer and external keying to work at up to 100 WPM. (Be sure to turn on both QSK and VOX.) The “+” mode icon turns on when CW+ is in effect. Tip: You may want to assign the CW QRQ menu entry to a programmable switch function (e.g., PF1) for quick access. This can be done by locating the CW QRQ menu entry, then holding PF1 until you see “PF1 SET”. Note 1: There are limitations to QRQ CW mode at present. You cannot use SHIFT, or turn on RIT, XIT, or SPLIT. However, you can still use splits, in effect, if you have the sub receiver installed: Turn the SUB on, and use VFO B as the receive VFO. (In a subsequent firmware release, RIT/XIT will be usable over a small range in QRQ mode.) Note 2: If you use CONFIG:TX DLY to set external keying delay, you may need to adjust its setting for QRQ CW use. Also, any increase in the default (8 ms) may decrease the maximum available CW speed. * AF BALANCE CONTROL IMPROVED: The SUB AF control can be used as a main/sub RX balance control (see CONFIG: SUB AF). Previously, when the control was rotated fully clockwise, main receiver audio would not be fully turned off. This has been corrected. * ADDED ERROR CODE “ERR RXF”. This message is flashed if you switch to a crystal filter that is too wide for the present settings. For example, ERR RXF will flash if you are in QRQ CW mode and select a filter wider than 2.8 kHz. To correct this, you'll need to turn off wider-bandwidth crystal filters either manually (using CONFIG:FLx ON) or via K3 Utility. * FIXED FSK-D STUCK TONE: Occasionally, sending RTTY using the keyer paddle (FSK-D) would leave sidetone on. __ 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
Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
WOW I knew it was fast when I tested but not so fast,I had a QSO with friend of mine who can receive by ears up to 75 and I sent him for few minutes at 70wpm,he said the tone is pure,no keyer clicks at all,the braking was perfect,he interupted me several times while I was sending and I heard him inmediately,it was like be talking on ssb with a very fast vox,thanks again Elecraft. AD4C If you see a woman handling a cell phone on her hands while she is driving,do please stay away from her.!! --- On Mon, 6/14/10, Paul Christensen w...@arrl.net wrote: From: Paul Christensen w...@arrl.net Subject: Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM) To: elecraft@mailman.qth.net Date: Monday, June 14, 2010, 11:15 PM From the time of CW key closure to RF, I measure a blistering 7 ms, beating the IC-7700 I measured by a solid 2 ms. It's that kind of transition that makes for super-fast QSK. Well done. Paul, W9AC - Original Message - From: Hector Padron ad4c2...@yahoo.com To: elecraft@mailman.qth.net Sent: Monday, June 14, 2010 6:53 PM Subject: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM) I just finished to install beta 4.03 and the process was nice and easy,no problems at all,radio works as it supouse to work,now I can send 70 wpm with an extremly fast brake-in,I set the delay at zero and its instantaneous the receiver cuts,I can hear anybody if he brakes me no matter how fasta I could be going,I love it once again Elecraft team did a good job,thanks AD4C If you see a woman handling a cell phone on her hands while she is driving,do please stay away from her.!! --- On Mon, 6/14/10, Wayne Burdick n...@elecraft.com wrote: From: Wayne Burdick n...@elecraft.com Subject: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fast break-in; VOX-CW up to 100 WPM) To: Elecraft Reflector elecraft@mailman.qth.net, elecraft...@yahoogroups.com, elecr...@yahoogroups.com Date: Monday, June 14, 2010, 5:02 PM K3 beta-test firmware revision 4.02 (with DSP rev. 2.60) is now available. See full release notes below. The most significant addition is CW+ mode. CW+ provides extremely fast break-in (receive recovery between code elements up to about 70 WPM) as well as VOX CW operation at speeds up to 100 WPM. We added CW+ mode primarily for high-speed (QRQ) operators, but the new, faster break-in applies at slower speeds, as well. Please give it a try. NOTE: There are significant limitations to CW+ mode at present, as described below. Please review them carefully. Please send any questions to k3supp...@elecraft.com. For instructions on how to load beta firmware, see: http://www.elecraft.com/K3/k3_software.htm 73, Wayne N6KR * * * MCU 4.03 / DSP 2.60, 6-10-2010 * 75 BAUD (100 WPM) RTTY SUPPORT: The built-in encoder/decoder (DATA/FSK-D) now supports both 45 and 75 baud. To select the desired rate, hold the DATA MD switch, then rotate VFO A. * ULTRA-FAST BREAK-IN AND QRQ CW (“CW+”): If you set CONFIG:CW QRQ to ON in the menu, the K3 will provide extremely fast break-in at all CW speeds. It will also allow both the internal keyer and external keying to work at up to 100 WPM. (Be sure to turn on both QSK and VOX.) The “+” mode icon turns on when CW+ is in effect. Tip: You may want to assign the CW QRQ menu entry to a programmable switch function (e.g., PF1) for quick access. This can be done by locating the CW QRQ menu entry, then holding PF1 until you see “PF1 SET”. Note 1: There are limitations to QRQ CW mode at present. You cannot use SHIFT, or turn on RIT, XIT, or SPLIT. However, you can still use splits, in effect, if you have the sub receiver installed: Turn the SUB on, and use VFO B as the receive VFO. (In a subsequent firmware release, RIT/XIT will be usable over a small range in QRQ mode.) Note 2: If you use CONFIG:TX DLY to set external keying delay, you may need to adjust its setting for QRQ CW use. Also, any increase in the default (8 ms) may decrease the maximum available CW speed. * AF BALANCE CONTROL IMPROVED: The SUB AF control can be used as a main/sub RX balance control (see CONFIG: SUB AF). Previously, when the control was rotated fully clockwise, main receiver audio would not be fully turned off. This has been corrected. * ADDED ERROR CODE “ERR RXF”. This message is flashed if you switch to a crystal filter that is too wide for the present settings. For example, ERR RXF will flash if you are in QRQ CW mode and select a filter wider than 2.8 kHz. To correct this, you'll need to turn off wider-bandwidth crystal filters either manually (using CONFIG:FLx ON) or via K3 Utility. * FIXED FSK-D STUCK TONE: Occasionally, sending RTTY using the keyer paddle (FSK-D) would leave sidetone on. __ Elecraft mailing list Home: http://mailman.qth.net/mailman
Re: [Elecraft] K3 Beta Firmware Rev. 4.03: CW+ mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
Heh. The new QSK is so fast it picks up bounce on the Dah contact on my Vibroplex, hi hi. Zowie 73, LS W5QD -- View this message in context: http://elecraft.365791.n2.nabble.com/K3-Beta-Firmware-Rev-3-57-Synchronous-AM-Detection-AM-S-misc-improvements-tp3983997p5180105.html Sent from the [K3] 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
