I wrote the original mess (the key handler inside computer) and I can tell you I HATED IT from day one. Now MUCH changed after I wrote it. TC Systems released their full "pal" handler and "midi" was no longer required. The driver and interface got better and better and better. But I made a very big mistake. There were three asynchronous clocks in that thing and no way to keep them all straight at all times.
The new keyer does away with the much of the problem by relying on the correct clock for the base timing, and compressing the necessary events in a good way to handle low impact through the system to maintain state and give you tone. This is a COMPLETELY new keyer, literally written from the ground up. I didn't understand it for two weeks, and then all of a sudden got it. By then, Steve and Eric were half through the basic state machine and it has taken a long time to track down and eliminate all of the ugly band aids we place on the old code to handle the mess, and to fix up corner cases introduced by the new code. I made a few hundred contacts in the ARRL on my 5000,3000, and 1500 and all were FLAWLESS CW. ON PURPOSE, I didn't use a logging program, but my bencher hex paddle. It was like night and day from before. This is a major breakthrough and will end completely this set of complaints and can only get better as things are tweaked. Bob N4HY On Tue, Feb 22, 2011 at 8:20 AM, Jason Burgess <[email protected]>wrote: > Hi all, > > Not trying to be a troll or a start flame here... but, I have to ask... > > I've been watching the lists for days for the FLOOD of "amazing CW > performance" messages and tears of joy from people who have had to shelf > their units for 18 or more months while the CW problem was worked on. > > Now, we have a release which seems to fix the issue according to a > surprisingly few positive reports (no offense to the 10 or 15 people who > have already posted positive reports on the installation and operation of > 2.19 RC1). Is the CW issue still an issue or is it fixed? The amount of > complaining I have seen on these lists relating to the CW issue would seem > to me to cause a FLOOD of positive emails now that the newly rewritten code > has been released. The amount of griping about "such a simple issue not > working out of the box" where other radios worked fine, etc etc etc.... in > my mind there should be a LOT of happy people now... correct? > > So, either people only speak up when they have a problem (myself included I > guess since that is what this email is addressing LOL), or the CW issue has > not gone away? All I see now is postings about problems... what about all > the success stories? Where are the floods of "thank you" and "this is the > best software release ever" and on and on I think we should be seeing? > > Come on people! If you are CW happy and you know, post a message!! LOL > > Let's show the people at Flex we can praise as well as we gripe!! LOL > > (again, apologies to those who have already posted and if you are wondering > why I haven't posted my CW success, that is because I am the worst type of > HAM... a no-code appliance operator... I only work PSK and RTTY at the > moment LOL, can just barely solder wires together (but getting better) and > buy everything I need from someone else who knows how to assemble it.. I > weep for the future! LOL) > > Jason > -VA1JSN > > _______________________________________________ > FlexRadio Systems Mailing List > [email protected] > http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz > Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ > Knowledge Base: http://kc.flexradio.com/ Homepage: > http://www.flexradio.com/ > _______________________________________________ Flexedge mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used for posting topics related to SDR software development and experimentalist who are using beta versions of the software.
