On Sep 27, 2009, at 3:28 PM, Bill, W6WRT wrote:
> If you fill your
> exchange with hyphens you will soon start seeing TOOAWT and other
> mysterious
> exchanges. Let USOS do its job!
Lets use rational dialog instead of scare tactics.
You seem to think that a FIGS before the 599 can get wipe out by noise
and thus cause an "TOOAWT." And yet a FIGS after a space character in
a USOS exchange does not?
With that extra FIGS in your exchange, you are just introducing a
higher probability of a bad exchange, Bill.
Moreover, if that FIGS is not received correctly, it won't be of the
benign "TOOAWT" kind either, since that extra FIGS can turn the
exchange into something completely misleading -- like "599 WWU".
In case you wonder why I had chosen a "W" after the space -- "W" and
<FIGS> have a Hamming distance of one.
If an error in the <FIGS> after the space causes an "599 27" exchange
to be turned into "599 WWU," are you going to log it as 599 227? No,
any rational person would ask for a repeat. This is why adding non-
printing characters in the middle of an exchange is not a good idea.
I can easily guess what "TOOAWT" means and don't need to ask for a
repeat.
A "TOOAWT" will also rectify itself into a Japanese exchange when you
ask for a repeat (most RTTY ops can do that translation in their head
and don't need the repeat anyway), whereas a "599 PR 03" from a non
USOS station will keep printing "599 PR 03" to a USOS station until
the cows come home.
The only reason this keeps coming up is that you keep insisting that a
space character is the only delimiter that should ever be used in
exchanges. Instead of believing your own mantra, do the math for
various random character error scenarios, Bill.
73
Chen, W7AY
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|