Problem is some people run software to copy the beacons to track
propagation. I normally avoid 14.100 +/- and the JT area at 14076,
the JT can be weak and you don't know it's there if you're not running
the software. The JT guys usually won't complain if they have a bit of
room to work and if things get really busy they move to the WARC bands,
they know they may not be heard.
It's very dangerous territory above 14.100, HFlinkers
claim 14.100.5, Winlink is all over the place with Pactor and now ROS.
ROS ops have been known to test new software versions during
contests to prove how robust their mode is, not just RTTY contests
either. Tread lightly, you're dealing with some enormous egos and
an over abundance of arrogance with this lot. During WPX I watched
a Winmor station come up and crush at least 5 RTTY signals, this was
below 14.100 too.....they're everywhere. Sorry hot button thing here,
rant over.
Ron
K0IDT
----- Original Message -----
From: "Gary AL9A" <al9a@mtaonline.net>
To: <rtty@contesting.com>
Sent: Wednesday, March 21, 2012 5:05 PM
Subject: Re: [RTTY] [Bulk] ROS policeman on 14101
> Per the information at http://www.ncdxf.org/beacon/beaconinterference.html
> the beacon folks are asking for a clear frequency from 14099.5 to 14100.5.
> They do recognize that someone trying to monitor the beacon with a SSB
> receiver with a 2.8 kHz bandwidth is still going to have a problem and
> recommend using the CW mode with a 500 Hz filter. Duh!
>
> Let's try another suggestion. If you are trying to copy the beacons on a
> weekend and can't hear the CW signals due to the interference from
> contesting stations all over the world, THE BAND IS OPEN!
>
> 73,
> Gary AL9A
>
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|