Easy on that cool-aid.... It's irregular, almost sounds like a bug. Take a look at it on one of the scope programs. Steve N4LQ ----- Original Message ----- From: "Guy Olinger K2AV" <olin...@bellsouth.net> To: "Steve Ellington" <n...@carolina.rr.com> Cc: <Elecraft@mailman.qth.net> Sent: Friday, May 14, 2010 2:51 PM Subject: Re: [Elecraft] K3 Link to QRQ CW RECORDING
> Well, yes, I can hear that, barely, in the recording, but at 45 WPM? > And that doesn't sound irregular to me, it sounds shortened. Add a > little weight to it. Hate to say it, but ain't this started off in the > direction of the Princess and the Pea? You DID have to run it slow to > make it apparent. > > The real problem is that by pushing that speed you are working against > the absolutely pure, artifact-free, soft QSK that everyone seems to > want, along with all the features that pull CPU time away from state > changes. AND we are talking about resource- and time-constrained > HARDWARE code, the most difficult kind of coding on the planet. AND > from a company that doesn't have the resources to spend on a couple > hundred salaried programmers and testers to work on it. > > The degree of tricky I don't believe can be appreciated by anybody > that hasn't written and debugged hardware code in a production > environment. You guys are really lucky that Wayne appears to enjoy > such stuff. Hardware code is seriously deranged work. The > alternative is guess who, and we all know how that has turned out for > innovation and RX performance. I got the K3 for the RX, and if he > ever does manage to do artifact-free 50 wpm state changes with RX > between the dits and microscopically perfect CW shaping, then bully > for him and I owe him a few rounds somewhere. But reality beckons... > Get your KPA's and P3's and other stuff out there to keep up the > revenue stream so we get to keep this string of innovation some take > for granted. > > That off my chest, I'm in favor of an option for those of us that > would rather have HARD QSK instead of the squeaky clean, absolutely no > artifact "QSK" that so many seem to want. I had 60 wpm QSK, clean > between the bauds, with a tube electronic TR switch and a separate RX, > TX (SB 300/400), and an AGC and audio gain clamp circuit added to the > RX, driven off the TX key circuit, and you could hear between all the > dits at 60 wpm. But ARTIFACT-FREE? Surely you jest. Another > approach might be at some set WPM, to drop out of state changes INSIDE > the letter. > > 73, Guy. > > On Fri, May 14, 2010 at 1:31 PM, Steve Ellington <n...@carolina.rr.com> > wrote: >> This file was made about a year ago and sent to Elecraft. >> A Winkeyer USB was used to generate 45 wpm and key the K3. This playback >> has been slowed so you can hear the uneven elements. >> The second half shows how the problem goes away when the K3 is locked in >> Transmit mode. >> http://docs.google.com/leaf?id=0By_pJYMIPoenM2FhNDE0ZDQtNzdkMy00ZjIyLWJmOWItNGFjZTI0ZWJhYWMy&hl=en >> Steve >> N4LQ >> ______________________________________________________________ >> 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
