|
| |
The Brass Pounders Quarterly
is an Electronic Newsletter of the ARRL National Traffic
System
Richard Webb, NF5B, editor
PUBLISHED BY TRAFFIC HANDLERS FOR TRAFFIC HANDLERS
Volume III Issue 1
Copyright 2009 by The ARRL National Traffic System
Contents
Editor's corner
NTS news briefs
From the editor's email inbox
General articles: Become a better noise detective
NTS Training: Better traffic = better training
BPQ features: Computer logging and the public service operator
How to submit an article
Where to get BPQ
This electronic newsletter is free to all who may
wish to receive it. You may upload it to bulletin board systems; ftp sites etc.
so long as no fees are charged for access to it. Individual articles retain the
copyright of the author.
EDITOR'S CORNER
More options mean more opportunities
As I put fingers to keyboard, it's Christmas Eve of 2008. We've seen
the ice storms hit New England, lots of nasty weather in the Midwest.
We had thunderstorms early this morning here east of Memphis, TN.
As my XYL prepares for family later today, I sit here with a coffee cup
in hand, check into the local hospitals net, from home today instead
of going up to the hospital to fire up their station as I normally
would on a Wednesday at noon. Meanwhile, I'm reading fidonet
conference mail, including the current issue of ARRL contest update
which I've received via internet email and have broken into parts to
post on fidonet in a public conference.
So now you're asking yourself what the contesting newsletter has
relevant to a traffic handlers' newsletter. Well folks, the editorial
comments were quite appropriate and caused me to cogitate on the words
of the editor. His editorial was entitled "another golden age" and he
posits that we're on the cusp of another golden age of amateur radio
and gives reasons why he believes this. TO make it more interesting,
I've drunk the Kool-Aid. so, you've found the editorial I speak of on
the web, and read it. You might be taking the curmudgeon's view that
this may be true for the technical types who like to build and
experiment. You acknowledge that DX spotting with packet clusters and
the internet has changed the game of the op in pursuit of awards. But,
you then state, and correctly so, that folks perceive traffic handling
to be a part of antiquity.
I must agree. Sending that message via radio relays one operator to
another might seem rather quaint to our emergency managers, our
teachers, and our neighbors. but, when that nasty smelling stuff hits
the fan these otherwise average folks have become accustomed to, and hooked on,
instant in touch. Mom is only a cell phone call away. In
fact, we're so "in touch" all the time that some folks can't seem to
walk down the street without walking into a wall because they were
paying more attention to their text on their cell phone than watching
where they're going. That constant ability to remain "in touch" is
addictive though, just like heroin cigarettes or alcohol. I watched
people hand over $5 and $10 bills for a chance to "try" to get a
connection on another's cell phone during Katrina. NO successful
connection with a cell site, that $10 bill still changed hands.
When that disaster grabs these folks, the loss of that ability takes
on oversized proportions when it's become part of your daily life. The
ability to call and check on that aging parent from a thousand miles
away becomes routine, and a part of one's day. Take that ability away,
and put that person in a situation where getting the necessities is
even a problem and the concern about whether mom's being adequately
cared for or just knows I'm safe becomes more important than it
otherwise would. IN fact, it becomes so important that it can keep the
individual from paying attention to those things which should be high
priority.
As Ward posits in his editorial, we're on the cutting edge of a new
era for the tinkers and do-it-yourself types. Yes, you can capture
images on your cell phone and nearly instantaneously upload them to
YouTube, Look through the webcam at your deck by your pool and be sure
that the noise you heard through its audio wasn't an intruder. But
when the lights go out and the cell towers aren't responding your
properly prepared and trained neighborhood ham has the resources you
need to get the word out to your family and friends that you're
alright, or to advise those outside the disaster zone what sort of
assistance is needed. But, to be that resource for your neighbor with
the can-do it himself attitude who recorded his son's band in the
garage, and built his own boat, and ... you can guess the rest ... we
need to maintain our level of readiness so that we can indeed do what
he expects of us. This means we educate our neighbors about amateur
radio, and participate in activities such as traffic handling which
hone and build the necessary skills.
First we need to be sure that we can deliver what we advertise, and
this means taking part in activities that keep us trained and ready.
It means that instead of complaining that there is no good traffic for
folks to handle we originate some. It means taking an assignment as
region or area liaison from our section nets, or taking a TCC
assignment one day a week.
But, to be that resource for our neighbors when their instant in touch
no longer works we need to do a bit of education. This means that we
take every opportunity to talk with our neighbors about what all those
antennas actually do, and what they'll do for him personally
when instant in-touch isn't. When the cell towers go down, the lights
go out and the immediate future is uncertain.
Even if we don't spend a lot of time educating our neighbors and
coworkers you can bet that sooner or later when the DSL modem connects
them with nothing and the cell towers don't respond he's going to
eventually come to the realization that the resource which can help
him reestablish that connection just might be next door in the person
of that ham radio operator whose car looks like a strange creature
from another world thanks to all the antennas it carries, and whose
yard sports a tower, A couple of masts and lots of wires. When that
neighbor asks you for help, you want the answer to be yes. That yes
answer might mean that he's in your corner the next time you want to
put up the bigger tower instead of fighting you at the city zoning
board.
This, dear reader, is why I began this newsletter and why I'll continue
to be an active traffic handler and public service operator so long as
I'm alive and there is an amateur radio service for me to utilize.
The following information received from Steve Ewald,
the Field Organization team supervisor at ARRL HQ.
NTS Resources Web Page is Now Active on the ARRL Web.
The ARRL National Traffic System Resources Web page is now up and
running as part of the Amateur Radio Public Service Web page.
The specific link to the NTS Resources is:
http://www.arrl.org/FandES/field/pubservice.html#ntsr
Visitors to the ARRL Web's "Amateur Radio Public Service" Web page
(http://www.arrl.org/FandES/field/pubservice.html) will find this
information when they scroll down the page and they spot the NTS logo.
The first link takes one to an Excel file that shows the available 2009
monthly NTS Area, Region Net and Transcontinental Corps statistics as
reported by NTS officials.
http://www.arrl.org/FandES/field/NTS-stats.xls
We expect to update this file each month. Please send monthly NTS net
and TCC activity reports, updates or corrections to Steve Ewald, WV1X,
at sewald@arrl.org.
On the Web page, you will also find a link to "NTS Methods and Practices
Guidelines," an introductory PowerPoint presentation about the NTS by
Dave, WB2FTX, and Greg, N2GS, as well as other related links about
traffic handling.
We are hoping to develop more resources related to the NTS, and then
make them available on the NTS Resources Web page.
--
Daytime region nine reactivates ...
Region nine daytime net can be found operating on 7280 kHz at 1700 UTC daily.
This may change with the time change, as daytime Region 9
follows at the top of the hour following Region 5 morning
session.
Alternate frequency is 3910 kHz.
New DRN9 manager will be NA9L. Since they are still finalizing schedules and other operational
details contact na9l@arrl.net for further information.
--
On Friday, March 27, Central Area net Cycle two activated on 7280 kHz to
assist North Dakota section with outbound health & welfare traffic as
well as long haul tactical traffic when needed.
Carl, WB9YBI, and some of the newcomers to Region 9 activities sure put
out a great effort in this activation.
--
From the editor's email inbox
A sampling of both positive and negative feedback we receive here
at BPQ from time to time will appear in BPQ.
We welcome your comments suggestions and items for publication.
The editor reserves the right to edit letters to fit available
space. Even though we're an electronic newsletter, we're not trying to
write a book. Honest folks <grin>. Send your comments to elspider@bellsouth.net and please indicate
in the subject line that this is a letter to the editor.
Now, on with the mail.
Steve, k6jt writes:
Thanks, Richard, for a very good and thoughtful newsletter. I am also very
concerned about the lack of activity and representation in the Central Area.
However, I am more familiar with the nighttime nets on CW than daytime voice
or digital. We do continue to have liaisons from Region 9 and 10 on CAN,
but it is often the same 2 or 3 stations. I have two TCC schedules (echo
and fox), so I check in to both CAN and PAN. I have noticed the level of
activity on PAN is much higher than CAN, although Region 6 in California and
Nevada seldom has even as much traffic as we do on the TEX net -- I get the
newsletters from RN6 since the manager is an old friend of mine. At least
all region nets are still operating in the CAN and PAN areas. I recently
received word that the Arkansas CW NTS net has been terminated and the
remaining operators have joined with the Mississippi net.
Would agree, at all levels above section which are still functioning
it seems to be the same few operators. I do think that CW nets
below region level will find themselves phasing out, leaving the
old school die-hards to operate region level and up. At least they still
operate.
By maintaining their net schedules newcomers have a chance to learn.
Also thanks for forwarding the newsletter to emergency coordinators
as you noted.
I hadn't heard about the phasing out of Arkansas CW net, but applaud
the Mississippi net's welcoming their Arkansas colleagues.
Again, thanks for the positive feedback Steve. I'm glad someone
out there appreciates these quarterly publications.
Rodney, w5dy writes:
Since the changes were made taking away exclusive use of the 3600-3700
portion of the 80 meter band for CW, I have done extensive monitoring in
it. There is very little use of this portion of the band now. I have heard
some SSB activity in the upper 25 kHz (3675-3700). Percentage of use during
a one month period is less than 10%. From 3650-3675, percentage is less
than 7%. From 3600-3650, percentage is less than 4%.
That is an awful waste of band space. There has been ample time for someone
to make use of these frequencies. Since they are not being used enough, I
think it should be given back to CW/RTTY/Digital. During contest weekends,
the present allocation of frequencies for CW, etc. makes it almost unusable
for net operation and QSO's.
Who else should I contact with these recommendations and statistics? I will
be glad to do so. Me and thousands of other CW ops would like to see this
portion given back to us.
Thanks for your help and 73,
Rodney Baker, W5DY
STX Section Traffic Manager
Tex CW Asst Net Manager
TCC Member
ORS
I would agree with your comments Rodney. During the fall and winter
months I end up operating on the Geratol net which is a worked all
states awards net which offers lots of endorsements. The Geratol net
meets in the Extra Class phone portion of the 75 meter band. Since the
expanded phone band the Geratol net has been meeting on 3668 kHz.
Is it underutilized currently? Indeed it is. One thing I've noted
during phone contests is that contesters seem to at least leave the
upper portion of 75 alone more now.
But, having CW and narrow digital modes all crammed into that bottom
100 kHz of 80 meters doesn't seem quite productive to me and I think
that regaining at least the bottom 50 kHz from 3600 to 3650 would be
quite reasonable, if not the whole segment.
I note some am operators with their vintage gear also meeting at night
around 3660, sometimes rather close to 3668 for our comfort on Geratol. Why so close when there's so much room there?
Like you I think CW and the narrow digital modes should be afforded
more protection than is offered by the bottom 100 kHz of 80 meters
only. Lobby your ARRL director to support this, and get others to do
the same.
------------------------
The late January ice storms that gave Arkansas, Kentucky, and other
states a pretty good kick this past January sure saw us miss some good
chances to shine. I was remiss in not bringing up central area daytime
under emergency operating conditions, i.e. stand by on same frequency
as daytime rn5 and encourage stations to utilize us, both inside and
outside the affected area. A local op sent me Kentucky health and
welfare on 2 meters, arranged on DRN5 which then hopefully moved into
the affected area Saturday night the 31st. I did hear service nets and
independent nets moving some as well. Speaking of which: Stations in
the central time zone with 40 meter capability with capability to be
net control are always welcome. When can daytime goes into emergency
operations we're going to need some NCS stations at least to man the
40 meter frequency.
Net managers should formulate an emergency operations policy and
publicize it widely within their coverage areas so that ARES officials
and others are aware that our nets can swing into action with expanded
hours and capabilities when the need arises. As the saying goes,
"build it and they will come."
Become a better noise detective
By Richard Webb, nf5b
Many of us live in urban environments where we are plagued with
numerous noise sources from nearby neighbors' equipment and the
power grid. For many of us BPL is the least of our worries.
Oftentimes these noise sources make it virtually impossible for us
to perform our duties on the nets as well as make operating an
unpleasant chore.
If the noise source is generated by a neighbor's equipment or
apparatus often it becomes a matter of gentle diplomacy to solve
the problem. If on the other hand the source is from a public
utility we find it even more difficult to get to the stage of
diplomacy. These folks though have at least a bit of knowledge
about the regulators they must deal with and can be convinced to
work on solving the problem eventually with some persistence on
your part.
Your first task however is to actually hunt down that dastardly
noise source and be able to state unequivocally where it's located.
This is often the frustrating part.
Peace and quiet, like charity often begins at home. Start with
electronics around your own home. TO make things easier switch
your radio equipment to your emergency battery power if available.
Does this quiet things down?
If not start by disabling circuits in your home. This includes
lighting circuits. IF it's generated in your home you'll get peace
and quiet. Now gradually bring circuits and electronics up
until the noise returns.
If powering down all circuits and electronics in your home doesn't
restore peace it's time to go hunting around your neighborhood. Lots of folks start with a portable AM broadcast radio. That can
be effective, those little ferrite rod antennas are somewhat
directional and can help localize the source of that pesky noise.
However, I use a technique that's a bit different.
Many of us have one of those little handheld radios that gives us
vhf and uhf capability and can listen in on the vhf aircraft band
in am mode. IF you have a portable receiver for this band you're
in business. Tune to a frequency in the vhf air band and open
the squelch all the way. Now utilize the same techniques you
learned over the years hunting hidden transmitters. IF you've a
local ham that's a pretty good fox hunter enlist his or her
assistance, especially if you've never done this before.
Using the vhf air band can provide a couple of advantages. First
and foremost, vhf signals don't carry as well as signals on the am
broadcast band. this helps you by giving you a higher level of
certainty that you've actually found the source of your problem.
The second advantage is on the legal front. Once you've localized
that noise source using the vhf air band you have some powerful
ammunition in your fight to get the problem corrected.
For you folks that are fairly new to the world of radio it goes
like this. the FCC and FAA are rather particular about noise
sources that might interfere with the frequencies used by aircraft.
Such interference can be considered a hazard to safety if present
in the air bands. Hence, electric utilities cable TV providers and
others are quick to solve such problems when brought to their
attention so as to avoid hefty forfeitures levied by the
appropriate regulatory agencies. IN fact, chances are the person
from the electric utility uses equipment in this band to hunt down
noise sources when he or she shows up at your door to follow up on
your complaint. So, usually a mention that you're hearing the
noise source in the air band will get somebody's attention right away
with nothing further needing to be said.
This is another reason you should get involved with your local
radio group's hidden transmitter hunts. IF your local group
doesn't do them, encourage them to start. Not just can these
techniques hunt down that jammer or illegal operator, but they can
save a life in an emergency, and help you restore peace and quiet
making operating a pleasure again. Along with this, they're just
plain fun!
Can't find it with your vhf air band receiver? GO back to the
portable AM receiver and that ferrite loop antenna. I'm going to
have to do this myself to sleuth an intermittent source out.
Hopefully by the time this issue sees publication I'll have found
that little problem and can report it. I've found enough nearby
arcing insulators and other things, but they're not the real
problem. This guy is a pulsating noise which only appears
occasionally and so far has eluded my fox hunting on vhf. Hence
I'm going to have to go out with the ferrite loop on a little
portable AM receiver and hunt that bugger down. Once I get close
enough I can then use my aero band receiver to actually zero in on
it, and report it.
Thankfully I've got one of those little human powered am/fm
receivers. You know the guys with the little crank on the side.
If you don't have one for this purpose, get one. When the power is
out and you'd like to tune into regular broadcast radio
periodically to get news and local info . You can save those
alkaline batteries for other purposes, like flashlights. I played
lending library with the one that lived in the radio room at
University hospital during Katrina.
So, don't just sit back and complain when those pesky noises would
drive you off the air. Get out there and do some hunting. If it's
a public utility such as the electrical or cable company then
you've got some leverage when you complain. IF it's a neighbor's
equipment, then put your diplomat's hat on and see if you can't
arrange "quiet hours" so that you can handle your nets and net
assignments. You might also be able to help your neighbor solve a
knotty problem which could be dangerous. Often such conditions will
manifest themselves as RFI before they become dangerous. An example
of such a condition is a loose service ground.
While you're talking to the neighbor whose equipment is the source
you can also do a bit of education about emergency preparedness and
what ham radio offers him and others who live near you. get him
and other neighbors thinking about utilizing those little FRS
transceivers they have around to help each other. IF you don't
have one, get one, and tell them that when the tornado or other
emergency strikes your neighborhood yours will be tuned to FRS
channel 1 and your station on the air and available to get them the
assistance they need.
Finally, in your quest for peace and quiet don't forget the resources
that ARRL HQ has developed over the years. Some hunting on the ARRL
web and a possible consultation with the folks at the ARRL lab can
often provide you additional information, or advise on tools and
techniques that will enable you to find, and eliminate that pesky
noise maker.
Better traffic = better training
With the reactivation of region 9 daytime again we find ourselves
discussing the bulk book traffic issue. Since that also means we've got
some new readers here your editor will use this space to discuss the
training aspect of what we do, and ways we can be part of the
solution, and not part of the problem.
First, I have little objection to birthday greetings. Most times I've
received a word of thanks for that reminder of a license expiration.
The congratulatory messages on license renewals are a bit redundant,
and I've attempted to contact more than one silent key regarding the
expiration notifications.
The problem I have with most of this bulk book traffic is the poor
training it offers regular NTS stations. I've utilized some strategies
over the years to combat this, and would like to tell you about them.
The radiogram QSL. When working for awards by making contact with U.S.
and Canadian stations I'll often send a radiogram confirming the
contact before I send a QSL card. some QSL bureau managers are also
known to use NTS to remind folks that there are cards on file for
him/her at the bureau. I would encourage much more of this.
Waiting for that one card to get a coveted operating award? Why not
send a radiogram to the party you worked asking him/her to please QSL
so that you can send in your entry? Maybe your card and SASE got lost
in the mail.
Did your group operate a special event station? notice some log
entries where the station you worked didn't send that SASE or follow
instructions to get a card or certificate? send the operator a
radiogram reminding him or her how to redeem that special card or
certificate.
Finally don't forget those special days such as your brother Bill's
birthday, holidays, etc. People are always glad to get these.
It's been discussed here before, but your club or emergency
comms group can always put on a message fair at some public place or
special event. see earlier issues of BPQ for more on this topic.
Don't forget Field Day! When inviting those officials and news
media people to your FD location show them how the system works for
originating and handling third party traffic. Offer to send a message
for them.
You'll never hear this operator complain about filling an assignment
as a TCC rep or liaison and having no traffic to handle. I'll still
show up just in case. I'm even more glad when I get good third party
traffic that will offer some training to the participants. When I do
take some of the bulk book traffic I get more complaints than anything
else when I endeavor to bring it to my section net.
SO, be a part of the solution. Originate some messages now and then.
It's been said that showing up at a potluck dinner without bringing a
dish is considered to be bad form. Bring a message to your section or
region net regularly and you'll note others doing the same.
Computer logging and the public service operator
by Richard Webb, nf5b
Have you ever really looked for programs that suit public service
operating? Some folks have written their own applications for favorite
spreadsheets or database managers for net control work. But, most of
the software for station recordkeeping is geared for the awards
chaser, DX hunter or contester. They've even got the Cabrillo format
to standardize contest log entries. However, our needs as public
service operators vary from individual to individual. what is the
perfect interface for you might drive me crazy, or cause me more
bother while operating than it should. IF it's a bother to me, I won't
use it, because it hampers my effectiveness on the air. The same holds
true for every public service operator I know. since this is true it
seems that BPQ could provide a valuable service to the public service
operator and traffic handler by discussing computerized logging and
record keeping solutions and how they're customized to suit our
purposes.
For a period of three or four years I operated a dial-up bulletin
board which carried a wide variety of files and programs of interest
to radio amateurs. When I'd get these new programs in I'd note what
they were useful for. After a time I started wondering why nobody
was writing software to assist the public service operator or net
control with logging and recordkeeping. Then as I upgraded and began
doing a lot of this work myself I realized why. The needs and desires
of the public service operator who would use it were all over the
map. I tried one program specially written for a net I controlled
regularly and found it didn't meet my needs. More on that shortly.
As I noted earlier, many write their own applications to handle the
duties of net control or handle other logging chores. My current
system has evolved over the better part of a decade. IT serves me
quite well, and is still evolving.
When I started with the traffic handling game I was still using the
old blind man's version of the pencil and paper. Effective, no
batteries or generator power needed. Information at my fingertips,
literally.
But as I started doing a variety of tasks in my public service ham
radio life, more computers came into my home. No longer was I
relegated to one computer for my recording studio's mix automation and
one for my XYL to use. There was now one for the shack. Yes, an older
286 machine, even older by year 2000 standards. Hey it worked, it
interfaced with my braille printer just fine.
the old thing ran my copy of Dbase just fine too. Anyone remember
dBase? well, I like it, still do. But, I found for some work as net
control dBase worked, but it was a bit cumbersome to use on the fly.
I played a little bit, using my computer with my favorite text editor
after the fact to transcribe info from my paper logs. Yes I'd copy
formal written traffic on the computer keyboard. After all, I can type
about 70 wpm. Easy to keep up with somebody sending a message.
I had a look at a friend's homebrew logging program for the Maritime
Mobile Service Net. I'm very active as a net control for them, as I
was then. Nice interface, with data on lots of stations that regularly
make use of the net, who has phone patch capability, and those abroad
or at sea who might use our services. But, stumbling around with text
to speech reading the screen, tab here and there, etc. wasn't conducive to
hearing those weak stations that might need the net. To
work most efficiently I would need something that worked from the
command line.
I took a couple of stabs at it, but found I still preferred to log
sessions as net control on paper. I had most of my compilation for my
monthly region net stats automated, but was entering the data manually
after each session.
In early 2002 I moved to New Orleans from southeastern Iowa. My
office was my radio room, and audio recording studio as well. Now I've
three computers in this office space, transceivers and other gear, and
a shortage of good table space for my equivalent of paper and pencil.
Push having come to shove at the NF5B shack it was time to implement a
system that would serve my needs when net control.
Back in Iowa I'd already implemented a system to deal with formal
written traffic I handled. A simple little batch script allowed me to
bring up my text editor, type in the message. The special formatting
commands for my Braille translator were stripped out and the message
moved to a "pending" file, and from this file then moved to an archive
file after sent or delivered. I could easily track my statistics for
station activity and PSHR reports as well as have records of formal
traffic I'd handled over the years. At the beginning of each month my
previous month's traffic file and station log were renamed showing the
month day and year and moved to an archival directory for eventual
backup.
I started with the simple stuff first, getting lists of check-ins
while providing the ability to make notes in the check-ins portion
that would not be counted when the number of stations participating
was tallied. I also desired a time stamp for each station joining the
net.
With any software designed to handle logging for net control it's
important that a traffic list be maintained separately and easily
manipulated. In days of hardcopy and the pencil equivalent I used to
use index cards. One listing per card. Yes, it seems wasteful, but I
could easily keep a "pending" pile to list on the air, and "cleared
traffic moved to another location. I knew that whatever I created for
NCS logging had to allow easy viewing and manipulation of that
traffic list. None of the shrink wrapped programs I attempted to adapt
to the purpose was suitable in this regard. Although I liked handling
session data as a net manager it didn't lend itself to net control
functions quite so well.
So, as long as I had to roll my own anyway ... you get the idea.
I cut my teeth on computers on an old IBM XT running DOS 3.3 then DOS
5.0. Then my own machine, and a landline BBS. This meant I was
learning a bunch over the years about the power of the .bat file for
dos and eventually windows. I don't use windows of any flavor, but
the .bat file is still a powerful tool for ms windows users, with some
limitations in newer versions such as XP, NT, and Vista.
I also wanted a way to note when traffic was presented, and when it
was cleared, and to whom sent. Also easy to accomplish. Along with
this, simple keystroke combinations to view either my check-ins list
or my traffic list. Easily done, a few little batch files and I was on
my way. For anybody else there would be a bit of a learning curve
but as I was writing it over time the learning curve was built in.
Even though I was no longer a region net manager after my move to New
Orleans I found myself taking responsibility for management of two
traffic nets. This meant I would need to compile reports on a monthly
basis. Of course, I wanted some automation to go along with this.
The regular batch language provided with Microsoft operating systems
is quite powerful, even with the limitations inherent in later
versions of windows. Many hobbyists and professionals have written
enhancements for the batch language which add additional
functionality, such as easier time and date stamping; text search and
replace capability; some rudimentary reformatting capability as well
as file management tools. Being a fan of the batch file I'd followed
the fidonet conference devoted to this topic and a couple of internet
forums as well. so, as you can guess, my little bare bones logging and
report generation suite has grown in complexity and capability over
the years.
Then came the upgrade of my XYL and I needed to go back to the drawing
board and write a menu driven interface for her. At this writing
most of its functions will work for her.
With the tools I've created I can output comma delimited data suitable
for import into database and spreadsheet programs if the need arises,
as well as generate regular plain ASCII text which is readable by
anyone on any platform.
As soon as I've done some better documentation I plan to provide a zip
archive of some samples of my work to the fidonet ham file
distribution network, where it can then make its way to other ftp
sites and file distributors. When this happens I'll post a note here
in BPQ letting those interested know it's available, and where.
So, now good reader, tell us here at BPQ how you manage your logging
and station record keeping chores for public service work. You just
may have the solution another reader needs.
********
How to submit an article
Send a file attach of a straight ASCII file to the editor at
elspider@bellsouth.net for
inclusion.
Brief items for our news section should be sent as a regular email.
Again, attach plain ASCII files only. If using MS Word choose the save-as option
to save as plain text, possibly called dos text. Check your favorite word
processor's documentation on creating ASCII files.
No graphics files, pdf etcetera please!
This electronic newsletter is
intended to be machine readable. This newsletter may be distributed on packet
and other radio systems where system operators and relay stations wish to
closely monitor content of transmissions. It is intended to be platform
independent which is not possible with graphical file formats. Even the operator
with the old commodore or Apple II should be able to read this newsletter, or
the fellow using the old dumb terminal. Text to speech systems etcetera should
have no problems reading this newsletter.
If possible use a file extension of .art for your article. If it fits one of
these categories use the category name as the file name. Regular categories for
which we seek articles are as follows:
General : articles of general interest to traffic handlers. Use a file name of
general.art
Training : Articles regarding training hints and tips. As above, use
training.art if possible.
Outreach : articles on ways to reach out to the public and promote NTS and
amateur radio message handling capabilities. As with the above examples,
outreach.art.
Using these naming conventions allows your editor to automatically process your
article.
Type the title twice, the first time at left margin preceded by a * character.
The second time centered as you'd like it to appear. The line with the * will be
used to automatically build a table of contents and the asterisk removed. Your
article will then appear with title centered.
Immediately below the centered title please place your name and call sign so
that folks will know who authored the article. If you have an email address
please provide it as well. Though often these can be looked up the information
provided in call sign databases is often incorrect. If you are a net manager or
hold an ARRL field organization position please provide this information as
well.
If possible keep line lengths to 70 characters or fewer. Again remember that we
are attempting to be platform independent. Many of our readers will wish to view
this on their screens instead of printing it out.
If you cannot save your article as plain text paste the text into an email and
send it. Your editor will do his best to format it properly for display on most
computer systems. If you do this state in the subject line that text enclosed in
email is an article for BPQ.
Although you retain the copyright on your work, submission of any articles
implies permission to publish them in BPQ and distribute said work
electronically without remuneration to you or BPQ. No fee may be charged to
receive BPQ.
Where to get BPQ
Many fine internet connected bulletin boards also carry BPQ in the hamnews file
area as a zip file using the same naming conventions as the text files within
them. These files are distributed by the ham-fdn and the International FIlegate
Project. Visit www.filegate.net/
FidoNet: Many fine bulletin board systems available via telnet www and dial-up
can link to the ham-fdn described above. If you don't see it on your favorite
fido board ask the sysop to link to the hamnews area through his/her regular
files link.
The headquarters of the ham-fdn can be accessed as follows:
Waldo's place USA. modem 12am-6pm EST. (919) 774-5930
telnet://bbs.wpusa.dynip.com
http://www.wpusa.dynip.com/
ftp://ftp.wpusa.dynip.com
RADIO RESCUE NET OPERATIONS BBS
Modem only 0600-1200 UTC 28.8 kbps n81 (901) 465-9921
If you are the system operator of a BBS (either landline or radio) and cannot
get BPQ through your regular links it can be sent you via email as either
regular email or a file attach. Send an email to bpq.distro@116-901.ftn.wpusa.dynip.com
Provide your email address in the text and tell us how you'd like to receive BPQ.
Also tell us what kind of BBS system you operate, its frequencies of operation
if a packet board or its dial-up/telnet info etc. Also, please give us your
callsign.
We wish to keep the email distribution list fairly small, so look to your
favorite internet dial-up or packet connections first if at all possible.
Thanks for reading and 73
Richard Webb, NF5B
Send correspondence to the editor via email using
the following email address:
elspider@bellsouth.net OR using plain text only to: bpq.editor@116-901.ftn.wpusa.dynip.com
All file attached article submissions should be sent to the bellsouth address.
See the earlier section on how to submit an article.
Place BPQ feedback or similar text in the subject line so that it receives
proper attention from the editor.
Readers are encouraged to create a hardcopy of this newsletter for those who do
not have computer access, but have an interest in the material within.
Reproduction of articles in club newsletters is permitted so long as BPQ and the
original author are credited.
For more information contact the
editor.
BRASS POUNDERS' QUARTERLY
Published by traffic handlers for traffic handlers
Copyright ARRL National Traffic System, electronic distribution encouraged.
|
