[RTTY] More on the KH6ZM mystery
Larry
lknain at nc.rr.com
Wed Jan 12 03:39:01 PST 2011
I saw KH6Z, KH6ZN, and KH6ZM on the East Coast. KH6Z would
be an unusual call but the signal struck me as being truncated. KH6ZN
was heard once and it too sounded truncated. So I had to listen a few
times but finally got KH6ZM (which I recognize as well) a couple of times
and went with that.
Some programs have a setting for PTT drop delay (and some the leading
pick time). Perhaps Alex needs a bit more delay in the drop. Some
people do sequence the radio and amp timing so that could be another
possibility as suggested.
73, Larry W6NWS
----- Original Message -----
From: "Kok Chen" <chen at mac.com>
To: "RTTY Reflector" <RTTY at contesting.com>
Sent: Wednesday, January 12, 2011 3:49 AM
Subject: Re: [RTTY] More on the KH6ZM mystery
>
> On Jan 11, 2011, at 10:13 PM, Jim W7RY wrote:
>
>> I have him on 20 and 40 as KH6ZM.
>
> I copied him on 15m and 40m as KH6ZM also, and more than once when I click
> on him again.
>
> Based on the waveform K2BB has recorded, I suspect there could be 4
> answers (two of which produces KH6ZM :-).
>
> You can print him as 1) KH6Z if the character with the truncated bit is
> squelched away, 2) print him as KH6ZN if the demodulator decoded the
> trailing noise as a zero, 3) print him as KH6ZM if the demodulator decoded
> the trailing noise as a one, or 4) his amplifier was cut off but somehow
> his exciter is not, in which case, people who get really good signal to
> noise ratio from his signal, will always print KH6ZM correctly.
>
> If most of the west coast prints him as KH6ZM, then (4), unlikely as it
> might me, may be the correct guess.
>
> The recorded signal dropping is so very clean that there is almost no
> chance that it is caused by propagation.
>
> 73
> Chen, W7AY
>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
More information about the RTTY
mailing list