<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><br>
</p>
<b><font face="Calibri, sans-serif"></font></b>><a id="LPlnk68603" href="http://www.aprs.org/"> http://www.aprs.org/</a><br>
<div style="color: rgb(0, 0, 0);">
<div class="qtdSeparateBR" id="yui_3_16_0_1_1452096248696_2962"><br>
Well, that's the most obvious raw source of information, but it is not organized as a clear and efficient tutorial for the newbie, hence my proposed documentation project. I expect much information from WB4APR's website would be included or referenced in the
proposed document, but not in the order presented on the website.<br>
<br>
Andrew, KA2DDO<br>
<br>
</div>
<div>
<div style="color:#000; background-color:#fff; font-family:HelveticaNeue-Light,Helvetica Neue Light,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; font-size:16px">
<div class="yahoo_quoted" id="yui_3_16_0_1_1452096248696_2909" style="display:block">
<div id="yui_3_16_0_1_1452096248696_2908" style="font-family:HelveticaNeue-Light,Helvetica Neue Light,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; font-size:16px">
<div id="yui_3_16_0_1_1452096248696_2907" style="font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; font-size:16px">
<div id="yui_3_16_0_1_1452096248696_2965" dir="ltr"><font id="yui_3_16_0_1_1452096248696_2964" size="2" face="Arial">
<hr id="yui_3_16_0_1_1452096248696_2963" size="1">
<b><span style="font-weight:bold">From:</span></b> Andrew P. via aprssig <aprssig@tapr.org><br>
<b><span style="font-weight:bold">To:</span></b> "aprssig@tapr.org" <aprssig@tapr.org>
<br>
<b><span style="font-weight:bold">Sent:</span></b> Tuesday, January 5, 2016 9:36 PM<br>
<b><span style="font-weight:bold">Subject:</span></b> [aprssig] is there a complete APRS primer out there?<br>
</font></div>
<div class="y_msg_container" id="yui_3_16_0_1_1452096248696_2906"><br>
<div id="yiv7824433691">
<div id="yui_3_16_0_1_1452096248696_2967" dir="ltr">
<div id="yiv7824433691divtagdefaultwrapper" style="color:rgb(0,0,0); font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; background-color:rgb(255,255,255)">
<div id="yui_3_16_0_1_1452096248696_2966">Greetings, all.</div>
<div id="yui_3_16_0_1_1452096248696_2968"><br>
</div>
<div id="yui_3_16_0_1_1452096248696_2969">I've been receiving complaints/suggestions from my software users regarding the difficulty of properly configuring an APRS station to "play nicely" with others. Does anyone know of a good complete summary for the APRS
newbie that explains how (and why) they should set up their station a particular way so both they and other users will have optimal use of the APRS network? Things like:</div>
<ul id="yui_3_16_0_1_1452096248696_2971">
<li id="yui_3_16_0_1_1452096248696_2970">symbol choices,</li><li id="yui_3_16_0_1_1452096248696_2972">SSID preferences,</li><li id="yui_3_16_0_1_1452096248696_2973">tocall values,</li><li id="yui_3_16_0_1_1452096248696_2974">propagation, bandwidth, and local capacity (aloha limit) issues,<br>
</li><li id="yui_3_16_0_1_1452096248696_2975">beaconing rates and digipeat paths, especially for the special cases of fixed station, mobile station, and fixed digipeater announcing Local Information about repeaters for mobile users,<br>
</li><li>transmit power and antenna height,</li><li>geographically where it is good vs. bad to deploy a digipeater, Rx-only I-gate, or Tx I-gate,</li><li>special rules for the balloon and rocket trackers, and even for ground-based Tx-only trackers,<br>
</li><li>etc., etc., etc.</li></ul>
<div>If no one knows of a good document that I can point them at, I would like to start composing/compiling one, based on the collected (or, more accurately, scattered) wisdom we've accrued over the past 20+ years of APRS operations. In the latter case, suggestions
of good partial documents that I can draw upon for wisdom would also be appreciated. I'm looking to end up with a single document (or small set of linked web pages) that isn't product-specific, but applies to all vendors and types of hardware and software,
doing special cases by function (tracker vs. digipeater, for example) rather than by specific product instances.</div>
<div><br>
</div>
<div>If we can come up with something like this, we should then reference it from everywhere to cut down on the repeated "How do I set up my station?" requests we keep getting because it _is_ difficult to figure out until you become a wizard that understands
in detail the innards of how the network works.</div>
<div><br>
</div>
<div>Just my $.02.</div>
<div><br>
</div>
<div>Andrew Pavlin, KA2DDO</div>
<div>author of YAAC ("Yet Another APRS Client")</div>
<div>http://www.ka2ddo.org/ka2ddo/YAAC.html<br>
</div>
</div>
</div>
</div>
<br>
_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br>
<a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>