<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>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<br><br><div>> 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.<br><br></div> </div></body>
</html>