This is a multi-part message in MIME format.
--part0_907000568_boundary
Content-ID: <0_907000568@inet_out.mail.aol.com.1>
Content-type: text/plain; charset=US-ASCII
--part0_907000568_boundary
Content-ID: <0_907000568@inet_out.mail.interserv.com.2>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
Return-Path: <owner-towertalk@contesting.com>
Received: from relay20.mx.aol.com (relay20.mail.aol.com [172.31.106.66]) by
air09.mail.aol.com (v50.15) with SMTP; Mon, 28 Sep 1998 12:00:27
-0400
Received: from dayton.akorn.net (dayton.akorn.net [205.217.100.11])
by relay20.mx.aol.com (8.8.8/8.8.5/AOL-4.0.0)
with ESMTP id MAA29617;
Mon, 28 Sep 1998 12:00:12 -0400 (EDT)
Received: from dayton.akorn.net (dayton.akorn.net [205.217.100.11])
by dayton.akorn.net (8.8.5/8.8.5) with SMTP id MAA10679;
Mon, 28 Sep 1998 12:00:11 -0400 (EDT)
Received: by dayton.akorn.net (TLB v0.10a (1.23 tibbs 1997/01/09 00:29:32));
Mon, 28 Sep 1998 12:00:05 -0400 (EDT)
From: force12@interserv.com
To: <towertalk@contesting.com>
Date: Mon, 28 Sep 1998 08:59:50 -0700 (PDT)
Message-Id: <199809281559.IAA03739@m4.interserv.com>
Subject: Re: [TowerTalk] Force 12 C-31XR
To: CQK8DO@aol.com, towertalk@contesting.com
Cc: "Natan Huffman"<force12e@lightlink.com>
In-Reply-To: <ba81d6d5.360f85cd@aol.com>
X-Mailer: SPRY Mail Version: 04.00.06.21
Sender: owner-towertalk@contesting.com
Precedence: bulk
X-List-Info: http://www.contesting.com/towertalkfaq.html
X-Sponsor: W4AN, KM3T, N5KO & AD1C
Mime-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
Good morning.
Haven't located the original beginning of this thread, but will jump in here!
First, the 100' feedline comment in the our manuals is not a big deal.
Referencing a feedline length was noted many years ago in some commercial
specs
and it seemed like a good addition. This length was selected as a typical
installation length, so that a customer would have an idea of what to expect.
As
most people know, coax has a small amount of loss (some more than others), so
the VSWR curves will be slightly broader than if measured directly at the
feedpoint. For our testing, we use 100' of new RG-213; however, always
desiring
to be conservative in specifications, the VSWR data is done using a 50'
section
of line.
Regarding the C-31XR and 15 mtrs, there is a paragraph that was added to the
manual in perhaps mid-late August. It relates to the positioning of the
parallel
feedlines between the 10 mtr and 20 mtr drivers. (The 15 mtr driver is open
sleeve coupled to the 20.) The manual and accompanying photos and drawings
apparently did not convey the instruction to not spread them apart. If they
are
spread apart in this manner, the 15 mtr VSWR curve will be low in frequency
and
also high in value. They need to be either parallel, or a pulled close
together
(bowed inward).
Had an installer call me on Friday from atop a tower with this exact
condition.
He "squeezed" them back together (they were pulled apart as far as they would
go) while we were talking and 15 came right in. He then tweeked the 20 mtr a
little and came down. This was the second C-31XR he has installed and had done
the first one "right." He vowed to read the manual when he puts his own up in
the next week or two!
Have a great day & 73,
Tom Schiller, N6BT
President, Force 12, Inc.
Amateur Antennas, Commercial Towers & Antennas
P.O. Box 1349 Paso Robles, CA 93447
Phone: 805.227.1680 FAX 805.227.1684
Web Site: http://www.QTH.com/force12
--
FAQ on WWW: http://www.contesting.com/towertalkfaq.html
Submissions: towertalk@contesting.com
Administrative requests: towertalk-REQUEST@contesting.com
Problems: owner-towertalk@contesting.com
Search: http://www.contesting.com/km9p/search.htm
--part0_907000568_boundary--
--
FAQ on WWW: http://www.contesting.com/towertalkfaq.html
Submissions: towertalk@contesting.com
Administrative requests: towertalk-REQUEST@contesting.com
Problems: owner-towertalk@contesting.com
Search: http://www.contesting.com/km9p/search.htm
|