W2RU Comments and suggestions - NET relocation and operation
This matrix has two primary purposes:
1. (Short term) to help net managers who have not yet
selected post-12/14/2006 frequencies for their nets to do so with
as much information as possible; and
2. (Long term) to provide an easily-accessible reference for
NTS participants to see where their net and other nets have moved
after 12/14/2006.
To satisfy both objectives above as best we can, it will be important
for each net manager to communicate his or her plans as soon as they
are determined -- even if only tentative at this time.
I encourage all net managers and other informed persons to please send W0UCE (W0UCE@nc.rr.com) the following information:
a. The 80-meter net frequency you expect your net session(s) to be using after December 14th;
b. The start and end times for your net session(s), where the
"end" time is the time you would expect each net session to be complete
90% of the time.
c. Any information you may have as to other *regular,
scheduled* uses of any of the frequencies found in the
matrix. (Example: Empire Slow Speed Net, ESS, is an
independent net covering New York State; it used to meet on 3590 at
6:00 p.m., or 2300Z, in winters, but recently decided to move to
3576. We have added it to the matrix so it is fully known that a
net, NTS or otherwise, already plans to operate on
3576 at that time. Similarly, we are noting that 3592 will likely be a frequency of continuing digital activity.)
The purpose of publishing this matrix this way is to make it easily
available to every interested person "24/7" and to encourage NTS nets
to determine their new operating frequencies ASAP, with full knowledge
of all previously selected net frequencies, and with a minimum of
conflicts. Jack will update the matrix as quickly as possible.
Please note the following:
1. These are winter times we're listing; we assume all nets shift
during Daylight Savings Time by one hour with respect to GMT unless you
tell us otherwise.
2. If you haven't yet decided what frequency to put your
(section) net on after 12/14, consider sharing a frequency with, or
snuggling up close to, your (region) net, or vice versa.
3. Under certain circumstances it is possible for two or more
nets to occupy the same frequency at the same time. For instance,
a west coast section net that happens to meet at 6 p.m. PST could
possibly co-exist with EAN. Similarly, a 7 p.m. PST west coast
"early" section net could probably co-exist with a 10:00 p.m. EST east
coast "late" section net. In either case, one net or the other
sliding perhaps 500 Hz from its nominal published frequency would
probably solve any co-channel interference problems. We have
designed the matrix to allow for multiple nets to occupy the same
frequency-time rectangles, with the intent that each rectangle
with multiple nets will be analyzed by the involved net managers for
possible changes in frequency.
4. In an ideal world, it would be nice if we ended up clustering
as many NTS net callup frequencies as possible within a small portion
of the 80-meter band -- say, for example, 20 kHz between 3660 and 3680
(example only -- don't get crazy on me). Two big benefits,
as espoused by Guy, K2AV, are: a.) over time, certain frequencies
will be seen by other users of 80 meters as being primarily utilized in
the evenings for
traffic-related
communications; and b.) NTS operations will be minimally disruptive of
other frequencies. Consider two football teams. One spreads
its offensive line all across the football field, from sideline to
sideline. The other clusters its linemen around the
quarterback. Which team do you think advances the ball
better? (Unless it's Syracuse....)
5. As suggested in the notes accompanying the matrix on the
4RN/C4 webpage, net control stations should think in terms of
side frequencies being increments of no more than 2 or 3 kHz each from
the net callup frequency. Using 3 kHz spacing, for instance, EAN
can usually exist in a 10 kHZ wide "band" probably 90% of the
time (net + 3 side frequencies). However, net managers and
net controls will need to alter their chosen side frequencies based on
a knowledge of when and where neighboring nets are operating. When EAN
is running, so are the region nets in the Central Area, so each must be
cognizant of the others' callup frequencies and assign pairings
accordingly. The use of a second receiver or pandapter band
scanner by net control stations is highly encouraged, as is the use of
500 Hz or narrower filters by net members.
6. This matrix is designed to be used by net managers in *all*
three NTS areas. I hope recipients will see that availability of
the matrix is communicated to NTS net managers *every*where.
7. Nothing in this matrix or our support of it is intended to
discourage or dissuade net managers and net control stations from
utilizing other bands, especially 160, when desired and
appropriate. Section and region net managers may well find, for
instance, that moving an entire net session to 160 on Friday and/or
Saturday night of major CW contest weekends is preferable to dealing
with the rapid-fire coming and going of
contesters across the 80-meter net frequencies.
