RTTY
[Top] [All Lists]

Re: [RTTY] ARRL willful interference

To: rtty@contesting.com
Subject: Re: [RTTY] ARRL willful interference
From: W0MU <w0mu@w0mu.com>
Date: Tue, 10 Jun 2014 13:30:46 -0600
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
Why do we keep having to cover or make excuses for rule violations?

For the record I am complaining about the willful interference by the ARRL W1AW control operators. The bulletins and code practice are quite legal. Willful interference is not.


On 6/10/2014 11:23 AM, Kok Chen wrote:
On Jun 10, 2014, at 9:32 AM, Paul Stoetzer wrote:

You are one of about two people in the world complaining about the
ARRL's bulletin service.
This is really no different from the NCDXF beacons, which by gentlemen's 
agreement operate at known fixed frequencies. (And there are probably also at 
least two people in the world who complain about them.)

If you are near 14100 kHz and a beacon fires up, it may legally be interfering 
with you, but it is for the good of the community that you don't operate there. 
 We avoid the beacon frequencies even though, just like the case for W1AW, the 
NCDXF beacons are no longer very useful in the internet age (think WSPR).

You can see the statement from NCDXF regarding interference here:

http://www.ncdxf.org/beacon/beaconinterference.html

Just treat the NCDXF and W1AW frequencies as part of a general band plan.

Indeed, as a low power operator, I would rather know precisely where W1AW might 
fire up and avoid those frequencies, rather than have them QSY from known 
frequencies and land on top of me when they attempt to avoid interfering with 
some other station.  More likely than not, I am too weak for W1AW to hear me.

73
Chen, W7AY

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

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