the only problems I had in this contest and other contests on
receive were the letters sent instead of numbers (either dashed or
spaced) I received them fine...and the only time I had to ask for a
repeat was from the garbled mass of letters that were sent for the
Serial No. number........and when asked for a repeat...the numbers
were sent instead of the letters...and it came through fine...again
either dashed or spaced....so if numbers were sent first (either
dashed or spaced) I would have saved more time with that rather than
worrying about if my contact was using a --wait for it---a dash or a
space in the exchange....
You miss the entire point - *nobody* is sending letters instead of
numbers in their exchanges. The letters you receive are due to a
receiving error on your end - you missed a FIGS code (due to noise,
fade, QRM, etc.) and your decoder printed the LTRS case rather than
in FIGS case.
There is a slight chance that the other station did not enable USOS
(unshift on space) in his transmit software and thus is not sending
the FIGS character before the numbers - but that is not likely if
you copy the repeats correctly.
73,
... Joe, W4TV
On 2/11/2013 5:53 PM, W2GR@aol.com wrote:
Because I am sort of a neophyte in regards to RTTY and I guess not a
"real" RTTY operator according to Chen......why are the letters sent anyway from
some ops?....programs in use from days of old?....the only problems I had
in this contest and other contests on receive were the letters sent instead
of numbers (either dashed or spaced) I received them fine...and the only
time I had to ask for a repeat was from the garbled mass of letters that were
sent for the Serial No. number........and when asked for a repeat...the
numbers were sent instead of the letters...and it came through fine...again
either dashed or spaced....so if numbers were sent first (either dashed or
spaced) I would have saved more time with that rather than worrying about if
my contact was using a --wait for it---a dash or a space in the
exchange....
I tried the shift/click route but the numbers ended up in the 599 line of
Writelog. So I guess if I want to decode the exchange with SH/cl I have to
tab over to the number line and do it?...and hope I click on the right mass
of letters .....but seems kinda slow when I can just click on the ser. no
and it goes where I need it....or maybe I dont know what I am doing as a
neophyte?....
Please don't spank me for asking stupid questions but there are no RTTY
elmers around here that I know of and I am picking this stuff up on my own
and finding I like RTTY a lot ....and having a lot of fun with it...
Maybe someday I will be a "real" RTTY operator...whatever that is.
Mike W2GR
---------------------------------------------------
In a message dated 2/10/2013 7:19:42 P.M. Eastern Standard Time,
dezrat1242@yahoo.com writes:
ORIGINAL MESSAGE:
On Sun, 10 Feb 2013 12:45:55 -0800, W7AY wrote:
So, if you see "599 QWE 123" (and assuming one is ignorant of the QWERTY
mapping), that will still trigger a request for a repeat.
REPLY:
Here's where we part company. If I see 599 QWE 123 I will not ask for a
repeat. I will click on the 123 just as if the sender had sent only that.
Is it perfect? No. Is it close enough? Yes.
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
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|