[CQ-Contest] Spacing note for RBN users

[N4ZR]

Hi Joe - to be honest with you, I don't know.  The details of VE3NEA's 
decoding algorithms are proprietary.  Just from experience, I'd say that 
the most important thing is to be regular, and not to drop spaces 
between words.  Longer spaces between words than normal probably 
shouldn't be a problem.  I know that too much speed variation in a 
single transmission can be a problem, but I'd be surprised if the sort 
of variations you describe will be an issue.

The best way to be sure, of course, is to try them on the air, while 
watching the RBN web site.  You should be able to tell quickly if there 
is an issue with a particular technique.

73, Pete N4ZR
Check out the new Reverse Beacon Network
web server at <http://beta.reversebeacon.net>.
For spots, please use your favorite
"retail" DX cluster.

On 4/22/2021 12:08 PM, Joe wrote:
> Hello Pete,
>
> Two questions.
>
> Does Farnsworth spacing's have any effect?  I like to run my letter 
> speed at 25 to 30 wpm, but the say "Word" speed at 20 to 25 wpm.
>
> and
>
> Varying spacing's, Like our club call W9ET if i run it "as is" I get a 
> LOT more repeats.
>
> But in like N1MM+ if I use W9~e~T  insert the half spacings, I almost 
> never ever get any repeat requests.
>
> One More I havent tried it yet, but to emphasize the "T" in the call,  
> say I'm running at 25 wpm,  but just for the "T" I drop to 20 or even 
> 15 to emphasize that it is a dash. and make it really obvious the 
> difference between the "E & "T"
>
> Joe WB9SBD
>
> On 4/22/2021 9:35 AM, N4ZR wrote:
>> When trying to decode callsigns for the RBN, the CW Skimmer Server 
>> software developed by VE3NEA relies on proper CW spacing to determine 
>> what is part of a callsign and what isn't.  This can result in 
>> problems in contests where abbreviations of the contest name are 
>> commonly part of the CQ and sent just before the callsign.  For 
>> example, "CWT" is often run together with the sender's callsign, 
>> resulting in spots of K4 stations with prefixes like "TK4". "WW", 
>> "MM", and other contest abbreviations, when run together with the 
>> sender's callsign, can have a similar effect.  The resulting spurious 
>> spots can replace what should be good spots - for example in the 
>> Available and Bandmap windows in N1MM+ - so it would be very much in 
>> senders' interest to correct their spacing if they see this happening.
>>
>