Bill, sorry, you recall wrong. As the contest sponsor and receiver of scores
and
soapbox comments, there were no complaints about excessive errors. To the
contrary, the only complaints were the exchanges zipped across the screen so
fast the operators were not used to the quick pace of TX, RX, and LOG.
Please don't manufacture (false) facts to support your beliefs.
Shelby, you're certainly correct, if I come across a 45 baud RTTY signal my
100 baud setting won't decode it. But I am wondering where has the spirit of
experimentation and technology advancement gone in ham radio? You recited
the "we've always done it this way" paradigm. Who says anything has to be
broken before we can "try something different"?
73 de Bob - KØRC in MN
----- Original Message -----
From: "Bill, W6WRT" <dezrat1242@yahoo.com>
To: "RTTY Reflector" <rtty@contesting.com>
Sent: Wednesday, January 27, 2010 6:32 AM
Subject: Re: [RTTY] Dashes in Contest Reports - SOLUTION!
> ORIGINAL MESSAGE:
>
> On Tue, 26 Jan 2010 22:49:17 -0600, "Robert Chudek - K0RC"
> <k0rc@citlink.net> wrote:
>
>>
>>They ALL specify RTTY as a mode for the contest. But not a single one of
>>them specified a specific speed. So in the spirit of the old High Speed
>>RTTY
>>Sprint that my brother and I experimented with in the late 90's, everyone
>>can simple set their speed to 75 or 100 baud for the next contest.
>
> REPLY:
>
> As I recall, after the High Speed Sprints of the 1990's, the general
> consensus was there were too many errors caused by propagation
> vagaries. 45 baud simply prints better in most cases.
>
> However, it would be fun to do it again just to see.
>
> 73, Bill W6WRT
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|