Back in the 70's I thought it was real cool to have a call sign with my initials in the suffix. Since then I have been increasingly concerned that I have a horrible call for CW contests, due to the l
Hans, I too have been thinking about my callsign and the "H" in the suffix being incorrectly copied during contests, a few things come to mind: If you know your CW computer keying is not chopping off
Hi, More... K0HB here on my PC is KRHB ;>) http://lists.contesting.com/mailman/listinfo/cq-contest __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experie
Author: gissel@fh-ludwigshafen.de (Prof. Dr. Andreas Gissel)
Date: Tue May 14 10:41:45 2002
On the other hand, be careful trying to optimize your call by maximizing the dah's in your suffix, hi. That's what I got, and sending this in CW tests is no fun, too. Might reduce the error-rate, how
Just examined my LCR for last November ARRL SS contest. I found that 28 one key Too late for that !!! 73 Rag LA5HE also JW5HE OZ8RO located in Telemark - home of skiing. My antenna "farm" can be foun
Since he is using computer keying, why not simply slow the speed slightly for the H, with an extra dit length, pause before and after the H... Obviously a lot of guys got his computer perfect CW righ
28 folks out of over a thousand screwed up the either the "H" or the "B" (or both). Sorry, but playing games with timing would likely cause a LOT more problems. I set my delay so that there is no dro
Hey Hans: Did you lose those 28 QSOs or did they? How does the ARRL penalize for that, I honestly dont know. How can you be held responsible for others inability to copy CW? You shouldnt lose any poi
This question got me thinking. The SS is/was unique in that it awarded one point for receiving the exchange, and one point for sending it. It seems like there should never be 2 point penalties in SS
The following message was sent by "KN5H" <kn5h@earthlink.net> on Tue, 14 May 2002 20:58:34 -0700. This information (on how the "other guy" busts your QSO is provided to you really as a "service". It'
<<E as normal I as normal 4 as normal H <added delay> Q as normal>> This is a real rythym breaker for me (especially when tired...). I'd be more likely to bust a varying speed call (exchange, report
Hi Hans, et al Not really. People kept busting the "H" in the middle of my call time after time when operating at a fast clip. I use TRLog and started slowing the "H" down in the call and the errors
Have to second Tom's experience. I have borrowed the call NV4X from a local club a couple of times. Slowing down the "V" on CW, using TR's features, really dropped the number of repeats/mistakes on t
Actually the most common mistake was copying N4VX instead of NV4X The way that finally fixed it was: Normal "N", slower "V" with an extra long dah, 1/2 longer space between "V" and "4", faster "4", f
With all the automated keying, it's hard to find an actual recognizable FIST anymore, but a few guys still do it the "hard" way by hand. My dear friend K3II is unmistakeable with his ever-so-slight p
Why not just keep the dits, but send them more slowly? Seems like error rates could go way down by QRSing just a bit. Bill Coleman, AA4LR, PP-ASEL Mail: aa4lr@arrl.net Quote: "Not within a thousand y