Determing where YJ0ADJ is listening has proven to be a challenge.
Sometimes he's listening on his own freq, sometimes up 1 or 2, and
sometimes up around 1910 in the JA window. When things are slow (when
he's working stateside), he seems to be listening on his own frequency.
As soon as things heat up, he'll go split. . . plus there's a natural
tendency for the calling stations to start moving up a bit.
Then sometimes he just disappears for a few minutes. About the time you
think you should give up because he's gone QRT, he's back again.
Anyway, was happy to work him this morning, in spite of nasty QRN due to
a major storm system that had just passed through.
By the time I got finished with the YJ0 (at 11:34z), I moved down to try
working FO0FI, only to have them go QRT. I think they QSYd to 75. Oh
well, another day.
73. . . Dave
W0FLS
> ----------
> Then the fun with YC0ADJ started. Heard some people calling around
> 1829 and after a few minutes, I could heard ADJ calling CQ on 1828.
> He didn't seem to be hearing anyone and after a few CQs, he was
> listening in the JA window. I heard lots of JAs up there calling
> and he was hearing JA3ONB - who didn't seem to be hearing ADJ much.
> I tired a few calls up there, but wasn't sure of the frequency.
>
> After about 10 minutes of that, he returned to listening somewhere (he
> never sent "up" which made it a mystery to me where he was listening
> since no QSOs were being made).
>
> He did come back to someone for a quick QSO, but not sure who it was.
>
> After about 30 minutes of calling with him only working one or two
> stations, (W0FLS provided proof where he was listening), my head was
> ready to hit the table and it was becoming clear that this was
> pointless.
>
> However, even when it is clear that it is pointless (take W4ZV's post
> for example), the topband disease kicks in and you just keep calling.
> . .
>
> 73 Tree N6TR
> tree@contesting.com
>
--
FAQ on WWW: http://www.contesting.com/topband.html
Submissions: topband@contesting.com
Administrative requests: topband-REQUEST@contesting.com
Problems: owner-topband@contesting.com
|