v0.16.4 Extra Space on CW?

Brad - N6SPM

Al, anybody? I don't have a lot of time this evening and I'm wondering if anyone else tried CW around 20wpm? I jumped on and worked a South Pacific station and I'm fairly certain I experienced the extra space (P turned to E G) that some of us found in the last version. I then went to monitoring without keying the Xmit and replicated it again off the air. I'm starting to anticipate this and I'm wondering if it is just me and this keyer's idiosyncrasies? I don't see this with my Kenwood and the same paddle(s)? Thx, Brad _ N6SPM

Al_NN4ZZ

Brad, Yes I had one Q on the new version tonight and it happened ONE time. I was going to wait and do some more testing before commenting to be sure. But It felt the same. The extra space was added after the last DOT in a BT ( - . . . - came out as - . . . - ). I think it is still there. I'm going to get a scope at some point to catch it. I have a new Rigol on my xmas list. (maybe someone else can do it first ). It would be good to catch it and provide FRS with the trace and shows that paddle transition from DOT to DASH is good but a space gets inserted. Regards, Al / NN4ZZ

Gerald-K5SDR

This is fixed in the version we are testing this week. Our CW hound was testing it at K5FRS today and he says it passes muster.

Brad - N6SPM

Gerald, Thank you and the FRS CW Hound for working through this. I realize the priorities you all face ( I was an EE Fellow in DSP hardware engineering), and these days I'm sure CW fixes/enhancements face tough competition for their place in the queue. BTW, great incremental update! 73, Brad - N6SPM

Gerald-K5SDR

Actually CW has a high priority in this rig. We have one of the >100 WPM QRQ Russian operators testing the radio in full QSK mode. It does require a separate receive antenna to work at those speeds though.

Al_NN4ZZ

Gerald, Thank for the update, it's good to hear that it's fixed in the next release. I did some more testing this morning and can confirm that the SPACE problem is still happening in 0.16.4. Here are a few notes: - tested at medium speed (20 WPM) - tested with RF power set to zero - in my testing it happens about once per 200 characters - when it does happen, it often happens again immediately if you try to resend the affected character - in my testing happens when transitioning from the DOT paddle to the DASH paddle in the middle of a character It does appear that the other keyer issues are resolved (side tone latency and missing DOTs). With the SPACE issue fixed it will be easier to more fully test at various speeds, etc. Once the keyer issues are resolved there are only a few remaining feature deficiencies from a basic CW operating standpoint. (e.g. RIT/XIT and memory keyer buttons) Regards, Al / NN4ZZ For Example: Program Button 1 to send 599 TU

Ken - NM9P

100 WPM ?!?.... I can't even move my fingers that fast, and I am a guitar player! At 100 WPM I can't even separate the dots and dashes, let alone hear between them! That is impressive, and so it the growing performance of this rig! When you all get it tweaked just right it is going to be a lot of fun. Thanks for all the hard work.

Ed, K0KC

Gerald, Please ensure that the fix works for us slow-pokes. I really admire the skill exhibited by the 100 wpm guy, but I loaf along at 18 wpm. I just had time for one cw contact last night and this problem was still evident in 0.16.4. The cw performance otherwise seemed to be improved over previous versions, however. Although I am mostly a digital guy these days, I do enjoy an occasional cw contact. Ed, K0KC