Towertalk
[Top] [All Lists]

Re: [TowerTalk] CM Choke Cookbook

To: Grant Saviers <grants2@pacbell.net>
Subject: Re: [TowerTalk] CM Choke Cookbook
From: Stan Stockton <wa5rtg@gmail.com>
Date: Fri, 22 Sep 2017 18:21:16 -0500
List-post: <mailto:towertalk@contesting.com>
RG-400 is way better in my opinion because of stranded center conductor.

Stan, K5GO

> On Sep 22, 2017, at 6:01 PM, Grant Saviers <grants2@pacbell.net> wrote:
> 
> I've made 20+ with RG142 using the "cookbook" smaller coax turns and core 
> counts, 160 to 10.  Measured with my VNWA the L & R values are near the 
> expected.   The TFE is UV resistant and some chokes are in PVC junction boxes 
> and some not.  At 6m the RG142 is at its QRO limit, below that it is fine 
> QRO+.  My 142 is the double braid silver plated version, it comes both ways 
> with the same obsolete RG unless it is MIL marked as mine is.
> 
> Grant KZ1W
> 
>> On 9/22/2017 13:48 PM, Jim Brown wrote:
>>> On 9/22/2017 8:16 AM, David Needham wrote:
>>> I have made several full power CM chokes for 80m and 160 m using RG213 and
>>> Mix 31 toriods per your articles. Do the number of cores or turns count
>>> change if I use RG142 for lighter weight?
>> 
>> Dielectric and o.d. of the coax both affect resonance. I have no data for 
>> RG142, but I suggest that you start with the guidelines for RG59/RG8X.
>> 
>> 73, Jim K9YC
>> 
>> _______________________________________________
>> 
>> 
>> 
>> _______________________________________________
>> TowerTalk mailing list
>> TowerTalk@contesting.com
>> http://lists.contesting.com/mailman/listinfo/towertalk
>> 
> 
> _______________________________________________
> 
> 
> 
> _______________________________________________
> TowerTalk mailing list
> TowerTalk@contesting.com
> http://lists.contesting.com/mailman/listinfo/towertalk
_______________________________________________



_______________________________________________
TowerTalk mailing list
TowerTalk@contesting.com
http://lists.contesting.com/mailman/listinfo/towertalk

<Prev in Thread] Current Thread [Next in Thread>