<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Why KPC9612s and 2M?<br>
      <br>
      Commercial TNC/Node combos (KPC9612 and others) - Small computers
      are available which can provide all the needed/desired functions
      and interface to multiple TNCs or sound interfaces. Recent testing
      shows that QPSK/4800 is quite reliable via a sound interface to a
      radio with a 9600 data port. 9600 is just a step up the chain from
      that. I expect xPSK (likely OQPSK or 8PSK) rates of around 19200
      are quite achievable. You can still use KPC9612s if sticking to
      9600.<br>
      <br>
      Many (I will guess "the vast majority") of EOCs already have
      issues with desense from multiple radios on 2M. If the supporting
      rationale that may make more sites available is EMCOMM support, I
      would put the backbone links on either 1.25M or 70cm with a
      preference for 1.25M. I would keep the backbone frequency clear of
      users to avoid additional congestion and hidden transmitters.
      Users could access on 2M/1.25M/70cm (whichever band the backbone
      link(s) aren't running on) at either 1200 or 9600. Why kill
      performance of an engineered and well adjusted backbone
      link/network with user stations?<br>
      <br>
      73-KY9K/Brian<br>
      <br>
      <br>
      On 5/5/2016 10:29, Robert Bruninga via aprssig wrote:<br>
    </div>
    <blockquote
      cite="mid:1f0c8c0cacd9f4f6e69b6a1c7e07b1d0@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style>
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">SAVE
            your KPC9612’s Boys, the East will RISE AGAIN!</span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">The
            Golden Packet team is toying with the idea of making our
            annual Appalachian mountain digipeater string from Maine to
            Georgia permament and making it a 9600 baud network for
            emergency and ham radio disaster response and play.  We
            already have 3 of the 14 sites with approval for
            installations…</span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Lets
            face it, traditional packet networks are dead</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
            and</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
          </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">although
          </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">APRS
            is alive and well</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">,
            it is specific and</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
            only operates at 1200 baud.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> 
            Although all fully integrated APRS radios work perfectly
            well at 1200 and 9600 baud, </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">all
            of the existing APRS network is 1200</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
            because </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">all
            the digipeaters (not integrated APRS radios) operate at 1200
            and the majority of all home APRS stations</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
            and IGates</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
            use TNC’s</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
            that operate</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
            at 1200</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">. 
            A huge legacy.  Besides, going to 9600 only barely doubles
            APRS speeds while degrading link reliability.</span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">So,
            since we have already shown for 6 years now, that this long
            2000 mile linear chain of mountains and valleys can support
            a 2000 mile network with only 14 digis,  why not establish a
            long haul 9600 baud Node chain</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
            from Maine to Georgia</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
            which could be a </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">significant
            boost to Packet radio emergency operations. </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">The
            network would not operate as APRS digipeaters but as
            KAnodes.  </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> As
            we all knew back in the 1990’s link-by-link acknowledgment
            was vastly superior to end-to-end. </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">We
            already have three sites in MD, and PA …  But we need more
            than hikers, to get us access to some existing ham radio
            maintained sites.  We do NOT want nodes to branch off down
            into the plains.  These nodes would bog down the network. 
            No, the main backbone would be to support emergency
            operations with beams that can point up to the mountains to
            pass traffic.</span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">So,
            we are splashing this onto the APRSSIG to see if people have
            SITE access and/or have unused 9600 baud KPC-9612’s to step
            up and lets see what we got.  Also will need a freq.  I’m
            thinking 145.01 but every time I think of it, people give
            feedback, and I LOSE or forget the feedback as to what
            existing systems are already on 145.01, such as DX clusters,
            etc…</span></p>
        <p class="MsoNormal"><span style="color:#1f497d"> </span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Every
            day we get MORE AND MORE addicted to our wireless
            infrastructure, which we all know, will be hard to access in
            a real emergency.  We need to keep the Ham radio Plan-B
            alive…</span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Bob,
            WB4APR</span></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>