Back to Home
|
Writing for Repeater-Builder
How to make it easier for the volunteer editors / webmasters...
|
|
First of all, Repeater-Builder is always looking for articles on various topics - everything
from increasing the effectiveness of repeater and base station antenna systems to linking systems
to newer repeater technology (like P25 digital) to NXDN, IDAS, Fusion, IRLP, repeater jammer
hunting, to... ???
There is a list of topics at this article ideas page, but
if you have an idea on anything else that you feel should be on repeater-builder (or added to the
ideas page), please let us know by sending an email to one of the web masters
(see the "Contacting Us" page here) and run your idea
past us. We can tell you if anybody else is already working on it, or share some ideas.
And If you see an error, or multiple errors, on an existing page don't be afraid to contact the
author. Even spelling errors.
Since all of the work on Repeater-Builder is done by volunteers, here are some
guidelines that will make their life much easier (and while it looks lengthy there is good stuff here,
please read it all the way to the end):
- The article has to be repeater oriented (note that we didn't say amateur radio repeater oriented).
This web site has info that is applicable to public safety systems (i.e. police / fire / ambulance / etc. service),
GMRS (General Mobile Radio Service), Civil Air Patrol (CAP) and Military Affilliate Radio System (MARS) repeaters as well.
- Consider what your audience already knows about the subject. Assume nothing other than what he or she would
learn by being a repeater user. Those that know more won't be offended by a one-paragraph review of the relevant basics in the
beginning of the article, they will just skip ahead.
- The article is written with the understanding that this is a USA web site on the World Wide Web
and not every reader is in the USA. If it's a modification article the local Rules may not be relevant, but if it's an article
on point-to-point links there might be a Rules-relevant portion. If something in the article relates to rules, please add
a short paragraph that presents a bit of backgrouned and title it something like "Background Information".
For example:
- Band edges can cause confusion:
- The USA two-meter amateur band is 144 to 148 MHz, but in many other parts
of the world it's 144 to 146 MHz.
- The USA Civil Air Patrol is part of the Air Force, and MARS repeaters are also military. Most of the repeaters
in both services straddle the amateur band(s), with most having an input on one side of the ham band
(i.e. 143.something) and an output on the other side (i.e. 148.something or 149.something), but a few have both the
input and the output in the 148‑150 MHz range.
- The USA UHF amateur band is 420‑450 MHz, elsewhere it's 420‑440 MHz
or 420‑430 MHz.
- The repeater segment of the USA UHF amateur band is 440‑450 MHz, with a 5 Mhz offset.
Some areas have the repeater inputs from 445‑450 Mhz with the outputs 5 MHz lower (sometimes
referred to as in‑high, out‑low). Other areas have the inputs from 440‑445 MHz, with the
outputs 5 Mhz higher (in‑low, out‑high). If your article would be affected by a "upside
down" UHF repeater you would need to mention that fact, and why.
- In the USA the commercial and public safety UHF band is 450‑470 MHz and
depending on the area can extend as high as 512 MHz (in 6 MHz increments).
In other countries it's very different.
- The narrower amateur bands in other countries forces different interchannel spacing and
different repeater offsets, which can cause problems in equipment conversions. For example,
in England the UHF repeaters live in the 433‑434 MHz area with a 1.6 MHz
offset.
- If your article is, for example, about moving a USA UHF radio from 472 MHz to 444
MHz, you'll have to change the repeater offset from 3 MHz to 5 MHz, and might have to
change the offset from plus to minus. So you'll have to mention in passing that: (a) the 470 MHz
range in the USA is commercial two-way and public safety, (b) the standard repeater offset in that range
is 3 MHz (c) at USA amateur 440‑450 MHz frequencies it's 5 MHz. and maybe
(d) in your area it's a minus offset.
- Sometimes legalities come into play and need to be mentioned. For example in England the repeater
has to ID every 15 minutes around the clock whether the repeater has been used / is being used or not.
At the opposite extreme, a GMRS repeater (460 range) in the USA doesn't have to ID at all! Both of
these issues caught a couple of amateur radio repeater controller manufacturers by surprise... Some units
were designed with only a usage based ID mode (the USA FCC amateur repeater rules), and the design
had to be revised to offer two additional modes: a "never ID" mode and a "beacon ID" mode.
- In Europe subaudible tone squelch is not as common as it is in the USA, and a 1750 Hz tone burst
is still used in some areas. Very few repeater controllers availble in the USA support tone burst, Arcom is one
that does.
- A telephone interconnect (autopatch) is almost illegal in Australia - a repeater running in unattended mode
(regardless of whether the owner is actually present or not) is not allowed to be connected to a public
telecommunications network, not even indirectly.
- Sometimes the radio environment differences can be unusually difficult - in Australia and New Zealand
there is a radio service called PRS that has 40 channels of FM simplex and repeaters at 476 and 477 MHz,
and the repeaters use a 750 KHz offset... That's right, a UHF repeater with way less than 1 MHz split,
which requires a completely different thinking about duplexer design and antenna system engineering. See
https://www.vkham.com/resources/cb-uhf-vhf-marine/frequency-usage for info.
Update: In 2019 they went to narrowband and doubled the channels to 80.
- In all of the above examples, to the local hams, that's what they are used to... it's the way it is, that's the way
it's always been, and will be for quite a while. As you write the article (regardless if you are in the USA or not),
just make sure that someone not familiar with your local situation can understand why you are doing
what you are doing.
- Consider equipment manuals and parts availability... in the USA you find GE, Motorola, Icom, Kenwood
and Yaesu/Vertex to be the common names. Consider that someone outside the USA may have seen a GE radio
only on an American TV show or in an American movie.
In England you will find Pye and other brands are common. In Australia and New Zealand you find that Tait is
common. Here in the USA you don't find ANY of the PYE radios and I've seen exactly four Tait radios (of two
different models) in 40+ years. And parts and manuals for many brands are unavailable.
- What background information will you have to include? An article on controlling RF
power level with a DAC will need a few sentences describing just what a DAC is. If
there is a good overview article at another web site, then provide a link to it. An
article describing modifications to a tube-type RF power amplifier might need a paragraph
on why neutralization is necessary. Also, as mentioned above, if local regulations
influence the circumstances under which the work described in your article was done,
mention that.
- Assess how your audience will read your article. Will they read it straight through
just once like a fiction story or will they read it slowly like a textbook? Will they
return to reread specific sections? If it's going to be something that they will come
back to regularly, you might want to put a table of contents in it with the list comprised
of section jumps (look at the Antenna Systems page as an example of inside-the-page jumps).
- Lastly, note that you, the author, retain all rights to your article. The repeater-builder
web site is full of copyright notices only because a while back there was a gentleman selling
CD copies of the entire GE section on eBay, making a serious profit off of our work, and it
took involving the legal system to get it stopped. On the advice of counsel the repeater-builder
web site is copyrighted on every page, but the author's copyright supercedes the web site
copyright - which is designed only to cover any material that is not copyrighted by someone else.
What we would like to see:
- Articles that include the basic W's of writing: who, what, when, where, why. Not every
article needs the "who", or the "when" or the "where", but some articles will...
- A conversational, down-to-earth style which avoids pontificating.
- Any interesting details that make the story come alive. Like why you jumpered the DC power switch on the link radio.
- What terms will you have to define? The standard New York Times writer's guide (originally written in the 1930s,
occasionally updated and still in use) specified that the writers would spell out every abbreviation the first time it was
used in an article, followed by the abbreviation in parentheses, and only then could the writer use that abbreviation
later in the article. Many of today's newspapers, like the Wall Street Journal have a similar policy. We do the same with
any uncommon abbreviations like digital-to-analog converter (DAC).
- Your article should pass the "I'll have someone who isn't an expert on the topic read it and let me know if it's
understandable" test. Structure it as if you would be explaining the topic to a bunch of students in a lecture hall.
Spell words out if necessary. Please don't use "texting" abbreviations like LOL, BTW or FYI.
The actual submission:
Obviously you would have been in contact with a staff member during the article discussion. Please just send him/her
an email with an attached zip file. Inside the zip file is the article file and a any other relevant files... JPGs, whatever is
appropriate. The article file woudl be a Word or similar document.
- To help the staff keep track of the files, please format the first few lines of the main article file something like this:
- The article title
- The author's name, callsign, email address, phone number. And after the phone number please put a "time
window" where it would be OK to call you, something like 9a-7p Central Time Zone. The editors are probably
not in your time zone and we don't want to call too early or too late. And yes, the editor already has that info but this
is just in case your article gets separated or forwarded to another editor.
- How many additional files are in the Zip file and what they are... images, manual PDF, component spec sheet PDFs,
whatever.
- Then a separator line... like this... just a separator between the header and the body of the article...
- - - - -
- Then the text of your article
The information above the "- - -" separator line will not be included in the final article; it is for the repeater-builder
staff during article preparation. We're just making sure that we can contact you from the info in the article file just
in case it gets separated from the email that it was attached to.
- You have considerable flexibility in your presentation... you can vary the font
size, boldface, underline, italics, embed pointers to youtube
videos, use tables (even nested tables) and more.
- You can use ordered or bulleted lists (like this bulleted list and the ordered (numbered) list above).
-
Web browsers default to font size 3, and can be changed to anything from 1 to 6 and you can change size between characters on a line.
This is a size 2 sample, this is in italics and this part is in bold.
This is a size 3 (normal) sample, this is in italics and this part is in bold.
This is a size 4 sample, this is in italics and this part is in bold.
This is a size 5 sample, this is in italics and this part is in bold.
This is a size 6 sample, this is in italics and this part is in bold.
And there is nothing preventing you from using bold or even bold underlined italics.
- Don't indent with spaces on the first line of each paragraph.
- Please shoot lots (and lots) of digital pictures - they really help, especially on modification or construction
articles. Obviously there is no film or developing expense on digital pictures and shooting extras costs nothing
but a little more time and some bytes of memory. Please shoot the photos at the highest resolution (i.e. the
biggest file size) that your digital camera can do, and let us resize them. Watch for simple things that can
ruin a picture (i.e. focus, glare and reflections); use an off-angle light source so the glare bounces somewhere
else, and if needed use two lighting sources (one on each side) to cancel the shadows. If you use fluorescent
lighting please test it - in many cases it makes the pictures come out with a green tint - just use LED, incandescent
or sunlight.
- If a measurment is significant in your photo (like of an antenna, a critical length cable or a cavity) please
position a ruler or tape measure in the picture. If you have one please use a double scaled ruler (centimeters
and inches) as a courtesy to the 90% of the planet that thinks in metric.
- If the intent of a certain picture is to direct the readers attention to a specific item - like a certain component
on a circuit board, or a section of an antenna, or a component inside a mobile radio chassis then please include
a pointer of some kind - a pencil, anything (even a small triangle or arrow cut from blue masking tape).
- Pictures need to be in PNG, JPG or GIF format for the web and we can convert TIFs / TIFFs
from your scanner. 99% of the digital cameras out there generate JPG files, and no conversion is necessary.
PNGs and JPGs are preferred since they have a much wider color spectrum than GIFs which are limited to
256 colors (or 255 colors plus transparent).
- Please preview your photos on your laptop or desktop as the little screen on the back of the digital camera
or your cellphone screen hides a lot of problems - and being out of focus being the biggest one.
- When your article appears on the web page your photos will usually be positioned between paragraphs, and
where a picture or schematic image is supposed to appear in your text just drop two lines, insert the phrase
"((photo N goes here))" or "((schematic N goes here))", where N is the number - then drop two more lines and
start the next paragraph. As the editor converts your file to the web page he or she will find the "((" markers and
replace them with the HTML code that will call and display the appropriate image file. The "((" and "))" just makes
it easier for him / her to find the image insert locations.
- Please DO NOT embed photos, images, or drawings inside the DOC file. As mentioned above please send the
graphics as separate files and use a line of text marked with (( and )) as a place-holder. Make sure the names match.
You don't have to go crazy with the file names either; "photo27.jpg" is just as good as "This Photo Shows How I
Modified The Interconnect Cable.jpg".
- If you are going to include schematics, please scan them at the highest Dots Per Inch (DPI) that your scnaner
can do (at least 600, and some scanners can do 1200 or even 2400). We ran into this issue in the Astron schematics
page, a low resolution scan made a "3" or a "6" look like an "8". We will resize each image for the preview that
appears inside the article and can include the large files for download in the article. Some schematics use color to
highlight things like voltages, some board layouts use color to clarify which side of a board has the component.
Please scan those in color, otherwise please use the monochrome mode on your scanner software as there is no
need to include useless binary color info in the scan file, as it makes the file much larger... and in some parts of
the world the internet charges are based on the megabytes transferred. These charges are why repeater-builder
tries to list the file sizes on the download pages.
- If you are going to send us an executable file (a .com or a .exe) you will find that most email systems (especially
gmail) will not co-operate. Let us know, there are ways around that issue.
- Then create a single zip file containing your article DOC file and any image files (photos, schematics, charts,
drawings, etc) or other files. Even if the Word file has images inside it, please include the original
image files separately. Think of the zip file as being the envelope for
an entire article package.
- Then send the article zip file attached to a covering email that mentions
who you are, what the article is and how the editor should contact you.
No, that last part is not obvious... we have had several submissions from folks
that normally use a home dialup connection, and they have used a thumb drive
or a floppy to take their zip file to work and used the work email address, or
a public library computer (that has a high speed connection) or used a friend's
cable modem to send us the article zip file. In those cases the email account
that sent the zip file is not the author's preferred contact address, so please
make sure that the body of the email (that the zip file is attached to) contains
your preferred contact address. As I said before, we're just making sure that we
have a good way to contact you either from the email or from the header inside
the article itself.
- Once the article is in the editor's hands, he'll convert it to HTML, upload
it to the repeater-builder server, then send you an email with a link to that
private web page. You will be able to click on that link and see your article as
others will see it so you and the editor can email each other back and forth and
"fine tune" the article, making the changes that are necessary to get your point(s)
across. Once you are happy the editor will add the article to the appropriate
Index page, where everyone can now find it.
- Another option that has been used to get a large quantity of information to
the repeater-builder staff is to burn a CD and mail it. Most of the GE radio
documentation showed up on CDs in ex-AOL mailers.
That's about it...
/s/ The repeater-builder staff...
Kevin W3KKC,
Scott N3XCC,
Mike WA6ILQ,
and the other editors.
This page first posted 14-Oct-2004.
Back to the top of the page
Back to Home
Text and hand-coded HTML © Copyright 2004 and date of last update by Mike Morris WA6ILQ.
This web page, this web site, the information presented in and on its pages and
in these modifications and conversions is © Copyrighted 1995 and (date of
last update) by Kevin Custer W3KKC and multiple originating authors. All Rights
Reserved, including that of paper and web publication elsewhere.