<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Right now, APRSISCE/32 uses a single
outbound path for packets, regardless of the port. I have some
plans to support port-specific outbound paths, but in the
meantime, I suggest running multiple instances with a single port
per instance especially if said ports are on different bands.<br>
<br>
Also currently APRSISCE/32 doesn't track which port copied a
station so when a message is gated from -IS to RF, it goes out all
transmit-enabled ports with the (single) configured beacon path.
This will also need to change to better handle multiple ports in a
single instance.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
Win32<br>
<br>
On 1/15/2015 8:20 AM, Andrew P. wrote:<br>
</div>
<blockquote cite="mid:BLU179-W4604928A7B846B50687321B84E0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<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>
<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>
<br>
</body>
</html>