First, my apologies to all that received funny looking signal reports from
me in the XE contest. Some dummy (me) had the USOS (Unshift On Space)
option in the cocoaModem RTTY configuration panel unchecked. Per W7AY's note
this was why many of you were seeing P's rather than zeros in my reports.
The USOS option has been checked (and saved) and will be double-checked
before that start of the CW WPX next week.
I learn something new in each RTTY contest.
73 de Dick, AA5VU
------ Forwarded Message
From: Kok Chen <chen@mac.com>
Date: Sun, 6 Feb 2005 11:22:12 -0800
To: "Dick Kriss, AA5VU" <aa5vu@sbcglobal.net>
The problem is not with cocoaModem, but the fact that most contesters
run USOS (as everyone should) and you are not.
They have unshifted to LTRS mode when they saw the space between the
numbers, so when they saw the following zero, it is treated as a P
since zero and P share the same Baudot code (one in FIGS and the other
in LTRS shift), and you, running without USOS are not sending a FIGS
shift between the space and the following zero.
73 de w7ay
> From: "<Dick Kriss>" , AA5VU <aa5vu@sbcglobal.net>
> Date: Sun, 06 Feb 2005 12:53:06 -0600
> To: "Kok Chen, W7AY" <chen@mac.com>
> Subject: USOS control of Ps and 0'
>
> Chen,
>
> I just checked my RTTY config panel and I was running with the Unshift
> On Space ?not¹ checked. Your user¹s manual shows USOS checked as a
> default. I wonder if this could cause the %n macro to send a ³P² rather
> than a ³0²?
>
> Dick
------ End of Forwarded Message
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|