I use the #-# and prefer to Rcv it that way in crowded band condx. (N1MM/MMTTY
here also). I think it jumps out against that solid backdrop of garbage under
busy/noisy condx.
My F2/Exch macro set to use #-#. However, for fills, or to send "extra" #'s, I
set my F7 with "<sp>#<sp>". If I want to sent the number three times on a fill
request, I punch "only" F7 three times and get "# # #". Admittedly it sends
2 spaces between the #'s (by choice), but at that point the quick QSO is blown
anyway.
But the larger problem, IMO: Sending macros without a space "before and after"
the text strings, especially callsigns. In the non-stop garbage, any speed
gained by leaving out that "space" is lost quickly.
Steve, W5KI
Date: Mon, 25 Jan 2010 05:57:09 -0800 (PST)
From: "B. Smith" <billn3xl@yahoo.com>
Subject: Re: [RTTY] Dashes in Contest Reports
To: RTTY Reflector <rtty@contesting.com>
Message-ID: <958001.2182.qm@web84402.mail.ac2.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1
There was comment in a thread awhile back about a dash being an easier/faster
decode than a space and recommended using it in place of a space to improve the
data transmission. My preference has always been to use a space, because my
signal reports seem to get through just fine and I prefer the way it looks. I'm
glad this pleases writelog users - but I must say N1MM picks out the number
amidst the dashes just fine - fyi.
73
Bill
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|