Message-ID: <4714BDA7.8030908@sighthound.demon.co.uk>
Date: Tue, 16 Oct 2007 14:33:27 +0100
From: John GM4SLV <gm4slv@sighthound.demon.co.uk>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To:  rsgb_lf_group@blacksheep.org
References: <000701c80e86$d700cea0$48e4fc3e@g3kev> <338459.59210.qm@web28106.mail.ukl.yahoo.com> <20071014193031.07a5ae31@lurcher.twatt.local> <20071014231737.jr38sns9bio8s4kg@webmail.versatel.de> <003c01c80f53$ab27e5c0$70e4fc3e@g3kev> <0Xyo0YAVyKFHFwoO@g4dmp.fsnet.co.uk>
In-Reply-To: <0Xyo0YAVyKFHFwoO@g4dmp.fsnet.co.uk>
Subject: Re: LF: MF acty
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


David Pratt wrote:

> The definition of a Beacon is in clause 17(g) of the Amateur Licence and 
> is covered by clause 10 and Schedule 2. 

Oh and I forgot.... a beacon is (as defined) "automatic transmitting 
only Radio Equipment"... I guess then if there's a receiver capable (as 
required in the regs) of receiving on the frequency of transmission, in 
the mode of transmission then it can't be a "beacon" as defined.

The duty cycle of TX to RX isn't defined in the rules.

My own station occasionally operates in TX mode (an "initial call") from 
2300UTC to 0700UTC and then in RX mode "listening for replies" (as 
observable via http://www.sighthound.demon.co.uk/gm4slv/grabber.htm ) 
between 0700UTC and 2300UTC.

Unless of course it's being used for QSOs at times within these windows.

That should just about cover it?

Now. How about we get on and do some actual "self-training and 
investigations of a technical nature"?

John