<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><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;}
/* 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-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></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">APRSdos maintained separate paths for VHF and HF ports. And strongly discouraged the insertion of any generic DIGI hops on HF with a nuisance box and obnoxious beep every time it transmitted with one. HF goes where it goes, and doubling the QRM and halving the throughput on an already slow channel by generic digipeating is absurd.</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">If you missed it, I deplore generic digipeating on HF.</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">Sure, it might help in some cases, but the equivalent is wanting to send a letter to a friend in NYC and deciding that printing up a thousand copies and tossing the two reams of paper off the empire state building is a good way to improve your chances of her getting it.</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"><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"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a> [mailto:<a href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a>] <b>On Behalf Of </b>Andrew P.<br><b>Sent:</b> Thursday, January 15, 2015 8:20 AM<br><b>To:</b> TAPR APRS Mailing List<br><b>Subject:</b> Re: [aprssig] HF packet (Was Re: weak signal ISS packet)</span></p></div></div><p class="MsoNormal"> </p><div><p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Calibri","sans-serif"">Hi, Dave.<br><br>You bring up an interesting point regarding selective transmission over only one of multiple TNC connections. YAAC does properly support digipeating to avoid WIDEn-N over HF when both HF and VHF ports are available, but there's no equivalent for locally originated or Tx-I-gated messages.<br><br>How do other APRS client programs handle this issue? Or do they ignore the issue and assume you will run separate copies of the program for HF and VHF?<br><br>Andrew, KA2DDO<br>author of YAAC</span></p><div><p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Calibri","sans-serif"">> Date: Thu, 15 Jan 2015 12:34:08 +0000<br>><br>> Monitoring 300bd AFSK, I often see digi hops (sometimes multiple!) specified. I <br>> also found that problem when trying to use YAAC with DireWolf for both HF and <br>> VHF tracking. At the time, I couldn't see a way to have a WIDE2-1 path on VHF, <br>> and keep that away from HF. Andrew has done a lot of work since then, so <br>> when I get time I'll take another look at that.<br>> <br>> That's the problem for me, as before, never enough of "the right sort of <br>> contiguious time" is ever available, to fully get up-to-speed with this stuff..<br>> <br>> 73.<br>> <br>> Dave G0WBX.</span></p></div></div></div></body></html>