<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
The VHF model is available, but we're out of stock as of Wednesday.
Should have more in a couple of weeks. There's also a new FC-302
out, but it's not in VHF yet.<br>
<br>
They work great for 9600 baud, though you do still have to pay
attention to setting the deviation properly. We sell the bare
radios and we also sell them with a Tracker3, but the T3 has never
had more than experimental 9600 baud support so you'd need to use it
with the KPC-9612 or something.<br>
<br>
Scott<br>
N1VG<br>
<br>
<div class="moz-cite-prefix">On 5/6/2016 6:10 AM, Robert Bruninga
wrote:<br>
</div>
<blockquote
cite="mid:9093d7cb7f132f7d5cc48d2331f81199@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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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";
color:black;}
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";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle22
{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">Scott,</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I
have several of your VHF Data Radios FC-301/D. I assume
they would work fine?</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">When
I google the model number, your current radios under the
same model number come up as UHF.</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">Are
VHF still available?</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">Its
just the Radio right? I assume I hook up an external
KPC-9612 to do the AX.25 and modem functions?</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</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<div>
<div style="border:none;border-top:solid #b5c4df
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
aprssig [mailto:<a moz-do-not-send="true"
href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a>]
<b>On Behalf Of </b>Scott Miller via aprssig<br>
<b>Sent:</b> Thursday, May 05, 2016 2:35 PM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br>
<b>Subject:</b> Re: [aprssig] The East will Rise again!
(at 9600?)</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal" style="margin-bottom:12.0pt">If we're going
to push for expanded 9600 baud implementation, can we pretty
please enforce some more rigorous technical standards than on
144.39? For 1200 baud APRS you never know if you're going to
see Bell 202 or V.23, pre-emphasized or flat, deviation could
be anything, the HDLC reset sequence is awful for fast clock
recovery but there's no other standard preamble, you don't
know if the receiving TNC is going to choke on non-printable
characters in the payload or if it's even checking FCS or PID,
and you've got tens of thousands of Kenwood devices that have
a fixed 500 ms TXD.<br>
<br>
At 9600 baud there doesn't seem to be much agreement on filter
selection and documentation is scarce.<br>
<br>
You could probably match 1200 baud's Eb/N0 advantage just by
requiring certain basic technical standards on a 9600 baud
network. <br>
<br>
Scott<br>
N1VG</p>
<div>
<p class="MsoNormal">On 5/5/2016 10:59 AM, Brian D Heaton via
aprssig wrote:</p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">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:</p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<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 and
although APRS is alive and well, it is specific and only
operates at 1200 baud. Although all fully integrated
APRS radios work perfectly well at 1200 and 9600 baud,
all of the existing APRS network is 1200 because all the
digipeaters (not integrated APRS radios) operate at 1200
and the majority of all home APRS stations and IGates
use TNC’s that operate at 1200. 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 from Maine to
Georgia which could be a significant boost to Packet
radio emergency operations. The network would not
operate as APRS digipeaters but as KAnodes. As we all
knew back in the 1990’s link-by-link acknowledgment was
vastly superior to end-to-end. </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>
<p class="MsoNormal"><br>
<br>
<br>
</p>
<pre>_______________________________________________</pre>
<pre>aprssig mailing list</pre>
<pre><a moz-do-not-send="true" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a></pre>
<pre><a moz-do-not-send="true" href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a></pre>
</blockquote>
<p> </p>
<p class="MsoNormal"><br>
<br>
<br>
</p>
<pre>_______________________________________________</pre>
<pre>aprssig mailing list</pre>
<pre><a moz-do-not-send="true" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a></pre>
<pre><a moz-do-not-send="true" href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a></pre>
</blockquote>
<p class="MsoNormal"> </p>
</div>
</blockquote>
<br>
</body>
</html>