CQ-Contest
[Top] [All Lists]

NAQP QSY TECHNIQUES

Subject: NAQP QSY TECHNIQUES
From: BK1ZX70SFL@aol.com (BK1ZX70SFL@aol.com)
Date: Fri Aug 9 01:58:47 1996
I guess i am missing something...my ole KC keyer has 4 memories and one was
loaded with:
pse QSY to 28050 nw ok ? bk

....and the others were 21050/3550/1830....mebbe my approach was wrong and i
should manually send with a paddle "same vfo"...oh well, the paddle is still
necessary i guess :-)

zx
---------------------
Forwarded message:
From:   KWIDELITZ@delphi.com
Sender: owner-cq-contest@tgv.com
Reply-to:       KWIDELITZ@delphi.com
To:     aa9ax@iglou.com, CQ-CONTEST@tgv.com

The only problem with "pre-set" QSY frequencies is that when they are in use
it undermines the purpose of the QSY request. You want to make it fast, so
you pick a frequency that is empty. QSYs in NAQP are often marginal, running
low power to a band with little propagation and you probably wouldn't make
the QSO if you didn't know what you were listening for. I had a few
occasions where I thought I picked a clear QSY frequency, but it turned out
not to be the case and I couldn't make the QSO. Finding the QSY frequency is
busy and moving up one or two just isn't going to be productive, cause the
guy you are moving isn't going to have the patience to look for you.

73. Ken, AB6FO, KWIDELITZ@DELPHI.COM


>From tomf@neca.com (Tom Francis)  Fri Aug  9 04:59:47 1996
From: tomf@neca.com (Tom Francis) (Tom Francis)
Subject: RF Exposure Comments
References: <20960809020302/0006008716DC6EM@MCIMAIL.COM>
Message-ID: <320AB7B3.32D6@neca.com>

Doug Grant wrote:

> p.s Did anyon else notice that the IRS guy was "putting his two cents' worth
> in". What's the deal here? DO they get a discount?

        Doug:

        No, but I'd be willing to bet that the first lawyer
        who tackles him in a RF exposure case is going to 
        have a very interesting tax audit, heh heh heh...

        73

        Tom, NM1Q (tomf@neca.com)

<Prev in Thread] Current Thread [Next in Thread>
  • NAQP QSY TECHNIQUES, BK1ZX70SFL@aol.com <=