VHFcontesting
[Top] [All Lists]

Re: [VHFcontesting] WA2UMX beacons are now K2DLL

To: "Jim McKnight" <k2lm@nycap.rr.com>, <vhfcontesting@contesting.com>, "Ron Klimas WZ1V" <wz1v@sbcglobal.net>
Subject: Re: [VHFcontesting] WA2UMX beacons are now K2DLL
From: "Steve Tripp \(K1IIG\)" <stephen.tripp@snet.net>
Date: Tue, 1 Sep 2009 16:53:47 -0400
List-post: <vhfcontesting@contesting.com">mailto:vhfcontesting@contesting.com>
 Jim,
It was very interesting to not you are using a design by a good friend of 
mine who I have known for 40 years. He and I have been in the repeater game 
for almost that long and he is no longer an active ham. I forwarded you 
comments to him. I am sure Ron knows him living in the same town.

Steve
K1IIG


> Jim: I am hearing K2DLL/b 539 on 222.051, and 559 on 1296.300
> tonight, but no sign of the 144.290 beacon here. Congrats on FB new call.
> -73 TNX, Ron WZ1V FN31mp
>
> At 01:06 PM 8/30/2009, Jim McKnight wrote:
>>OM:
>>
>>As of Sunday, 30 Aug. 2009, the WA2UMX beacons on 144.290 MHz,
>>222.050 MHz and 1296.3 MHz are now back on the air sending "K2DLL/B
>>FN23XC". The club changed their callsign from WA2UMX to K2DLL, a
>>founding member of the group. All three are still keyed
>>simultaneously using a design by WA1LMV from a December 1978 QST article.
>>
>>The ERP for the 144 and 1296 should be the same as before, but the
>>222 will be down about 2 db because we have lost one of the stacked
>>"big wheels".  Since the building housing the beacons has no
>>temperature control, each beacon may be slightly off frequency. I
>>will check their frequencies as soon as the building cools down to a
>>more reasonable level.
>>
>>Jim K2LM
>>Trustee K2DLL
> _______________________________________________
> VHFcontesting mailing list
> VHFcontesting@contesting.com
> http://lists.contesting.com/mailman/listinfo/vhfcontesting 

_______________________________________________
VHFcontesting mailing list
VHFcontesting@contesting.com
http://lists.contesting.com/mailman/listinfo/vhfcontesting

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