I disagree. Being able to operate outside the "automatic sub-bands" is an
incentive for operators to preferentially choose servers that include an
effective automatic busy frequency detector and to keep that busy frequency
detector enabled.
We're in a deep hole dug by those who ran (and continue to run) servers
(e.g. WinLink PMBOs) without busy frequency detectors. This has generated
enormous frustration over the years, to the point where some operators now
intentionally QRM such servers. This intentional QRM is as disgusting as
running a server without a busy frequency detector, and provides a
convenient excuse for server operators to continue avoiding or disabling
busy frequency detectors.
The first step in escaping from a deep hole is to stop digging. In our case,
this means that
1. servers with effective busy frequency detectors enabled should be welcome
across the full range of frequencies available to them as specified in the
applicable regulations
2. the intentional QRM must stop
3. servers without busy frequency detectors (e.g. WinLink PMBOs) should
immediately be retrofitted with effective busy frequency detectors -- a
possibility that Rick KN6KB stated here a few months ago that he would
investigate
73,
Dave, AA6YQ
-----Original Message-----
From: [email protected] [mailto:[email protected]]on
Behalf Of KH6TY
Sent: Sunday, June 27, 2010 9:25 AM
To: [email protected]
Subject: Re: [digitalradio] Busy detect screenshot for Winmor
Thanks, Andy.
Unless it is not impossible to disable busy detect, to answer your previous
question about where to operate with Winmor, I personally think that Winmor
frequencies should ALL be kept within the automatic subbands, since the
tendency is going to be to disable it due to the uncertainty if there is
malicious blocking or not. This way, busy detect can still be useful in
enabling frequency sharing with other Winmor stations, and if someone
disables busy detect, the effect on the rest of the hams will not be
significant. This brings to mind the edict by Winlink that busy detect must
not be enabled because of others trying to harm Winlink. It is highly
unlikely that any malicious blocking will be done in the automatic subbands,
because there is no reason to do so. The only blocking will be if the
frequency is already in use by another mailbox.
The recently reported problem with a PSKmail server still interfering with
JT65 points up to another reason that ALL mailbox stations need to be in the
same area, regardless of bandwidth. The more narrow the bandwidth, the
easier it is to find a clear frequency there, so there is still an advantage
to using a more narrow bandwidth.
The frustration of being blocked too often if operating in the general use
areas is, sooner or later, going to result in operator deactivation of the
busy detection, especially as more and more Winmor mailboxes are set up.
Before things get to that point, I think that it would be wise for early
adopters, such as yourself, to set a good example by operating Winmor only
in the automatic subbands and using the busy detection feature to more
efficiently share frequencies there.
73, Skip KH6TY
On 6/27/2010 8:46 AM, Andy obrien wrote:
Skip (and anyone else interested), see the attached screenshot showing
the Winmor server busy detect
Andy K3UK
