Return to KLUBNL.PL main page
| To: | [email protected] |
|---|---|
| Subject: | Re: LF: MF acty |
| From: | John GM4SLV <[email protected]> |
| Date: | Tue, 16 Oct 2007 14:33:27 +0100 |
| In-reply-to: | <[email protected]> |
| References: | <000701c80e86$d700cea0$48e4fc3e@g3kev> <[email protected]> <[email protected]> <[email protected]> <003c01c80f53$ab27e5c0$70e4fc3e@g3kev> <[email protected]> |
| Reply-to: | [email protected] |
| Sender: | [email protected] |
| User-agent: | Thunderbird 2.0.0.0 (Windows/20070326) |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: LF: MF acty, John GM4SLV |
|---|---|
| Next by Date: | Re: LF: slv and dpe, xgj and xes, John Andrews |
| Previous by Thread: | Re: LF: MF acty, John GM4SLV |
| Next by Thread: | Re: LF: MF acty, David Pratt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |