I did too. I stopped and keyboarded him to tell him that because I
asked him for his call about 5 times before he sent it manually.
I was S&P at the time and moved on after that so I don't know if he
fixed it.
Les W2LK
On 1/10/2011 8:42 PM, David Levine wrote:
> Speaking of KH6ZM, did anyone notice his macro was only sending KH6 or if it
> wasn't his macro, his amp/transmission was ending before it finished
> sending? When I look in the MMTTY log file I see over and over just KH6
> being printed with a rare ZM once every 5-10 times. When a KH6ZM finally
> showed up he had a mini pileup for a bit. I'm guessing those that called him
> when KH6 was coming out had KH6ZM on the cluster they were using to
> determine the full call.
>
> Anyone else notice that on the first day?
>
> K2DSL - David
>
>
>
> On Mon, Jan 10, 2011 at 8:30 PM, Kok Chen<chen@mac.com> wrote:
>
>> On Jan 10, 2011, at 2:18 PM, Phil Cooper wrote:
>>
>>> I missed out on VE6WQ, but maybe propagation didn't favour the path. I
>> did
>>> see VE7CC calling folk, but never found him CQ'ing.
>> VE3WQ was there... worked him on 20m towards the end of the first UTC day.
>> But didn't work VE7CC until almost the end of the second UTC day, on 15m no
>> less.
>>
>>> I did keep checking 10m, but it was dead, apart from one time when I
>> heard some weak RTTY, and then saw it was V5/DJ2HD.
>>
>> The one time I checked 10m and found it to not be dead, I worked one
>> station in Oregon, and one station all the way in Florida. Go figure.
>>
>>> I did get WV and RI, but they weren't easy to find!
>> I thought KU1T sent me WV very early in the contest so I just logged it as
>> WV. I never did find a RI station calling CQ, but saw a number of them
>> answering CQ. Infuriating :-).
>>
>> I was semi drooling when I saw J39BS answer a couple of CQ. Then finally
>> found him CQ'ing. He was already at QSO 985! KH2JU was a good catch, he
>> was only at QSO 31 at the start of the second UTC day. When I found ZM4M at
>> around the same time, he was at QSO number 12 and FO8RZ was at QSO 31.
>>
>> The surprise this time was I only found two Hawaii stations, KH6ZM, who was
>> pulling in a large QSO number, and KH6CO who had a much lower QSO count.
>>
>>> I really cannot understand what makes someone call again and again. UU9JQ
>> did this to me on at least 4 or 5 occasions, possibly more, and it got to be
>> a real nuisance.
>>
>> I saw one frequency brawl where one side asked the other to be a gentleman
>> and move.
>>
>> As a contesting teetotaler, I never could understand why some station would
>> choose to stay around to fight. Bill W9OL can count up the milliseconds
>> lost :-) :-). I would just QSY myself. Since I use a waterfall display, I
>> could see that one side of the passband they were fighting over was
>> unoccupied in the Pacific Northwest (unless there is a station within skip
>> distance from me). Some of my best catches during a contest came from stuff
>> above 14100 anyway. Lots of space up above 14100 and if you didn't go up
>> there to look, you could have missed 4U1WB :-). And if you don't tune low
>> enough on 20m, you could have missed P49X. I go to where the DX is, and
>> often, they are not in the RTTY alley.
>>
>> BTW, I did look for PSK31 stations, but they all seem to be involved in
>> some "PSKFEST" and sending RSQ :-). So I passed.
>>
>> 73
>> Chen, W7AY
>>
>>
> _______________________________________________
> 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
|