[Lowfer] Looking for input on measuring changes to the beacon

[N8OOU]

Jay, thanks for the comments.  I understand, and agree that Antenna 
Current is a factor.  I have a current meter inline with the feed going 
to the antenna, as well as a clamp on, which I can use between the PA 
and loading coil or exciter/PA.  So far, I trust these to guide me in 
adjusting the tuning.  But nearby body movement or wind blowing antenna 
wires causes significant reading variances.

It may be my inexperience and/or lack of trust in these devices, that I 
am looking into the remote receiver idea.  Also over the past couple 
months, I have made changes to antenna heights, materials, and 
dimensions.  So I am looking for a measurement of the complete package.

The point you make about keeping the 1 watt power level is one which I 
need to pay more attention to. I have assumed it was proper, but I know 
the definition of assume. Hi Hi.

Again, Thanks for the comments.


73   de   N8OOU - Mike Meek

On 02/02/2015 08:42 AM, jrusgrove at comcast.net wrote:
> Assuming a constant (maximum allowable) antenna height, just look at
> antenna current. Keep transmitter power at 1 watt for all measurements.
> Worthwhile changes to the antenna system will be indicated as an
> increase in current.
>
> Jay W1VD  WD2XNS  WE2XGR/2
>
>
> ----- Original Message ----- From: "N8OOU" <n8oou at meekfarm.us>
> To: "lowferlist" <lowfer at mailman.qth.net>
> Sent: Monday, February 02, 2015 9:26 AM
> Subject: [Lowfer] Looking for input on measuring changes to the beacon
>
>
>> I have been trying to develop a way to measure gains or losses in the
>> changes I make over time, to the Wm Beacon.  Being a genuine
>> cheapskate I am trying to use just the equipment I have at hand. I
>> have come up with this idea.
>>
>> My equipment includes the Kenwood TS-480 interfaced to the computer
>> with argo and other common software. I also have a Kay model 432d
>> attenuator which I believe to be accurate.  I can use either a
>> multiband trap vertical (80m - 10m) or a pa0rdt mini whip, both
>> mounted about 100 ft. away from the beacon antenna.
>>
>> The Kenwood has a digital rf gain control which steps from 100, down
>> to 0.  As the numbers go down the s-meter bars go up.  I assume the
>> incoming signal must be stronger than the indicated bars to be heard.
>> At 36 the s-meter is full scale at 60dB over 9. As you go lower in
>> numbers the sensitivity continues to be reduced with no change on the
>> s-meter. I am currently measuring in the 22 range, and have not yet
>> needed to put the attenuator in-line.
>>
>> With argo set to display the beacon in the band mode screen it
>> indicates the peak signal frequency and strength in dB at the top of
>> the screen. As I drop the rf gain, I hit a point where argo loses the
>> beacon lock and seems to hunt for a signal to lock onto. If I raise
>> the gain back up argo seems to lock back on to the beacon again. That
>> rf gain setting / argo reaction, seems to be reliable and consistent.
>>
>> What is the opinion to logging the gain setting / argo signal strength
>> reading to benchmark changes to the beacon system?  Any thoughts about
>> consistency over the long term?  Is there a flaw I am missing?
>> --
>> 73   de   N8OOU - Mike Meek
>> ______________________________________________________________
>> Lowfer mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/lowfer
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:Lowfer at mailman.qth.net
>> Post must be less than 50KB total for message plus attachment!
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>
> ______________________________________________________________
> Lowfer mailing list
> Home: http://mailman.qth.net/mailman/listinfo/lowfer
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Lowfer at mailman.qth.net
> Post must be less than 50KB total for message plus attachment!
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>
>