[aprssig] HF packet (Was Re: weak signal ISS packet)

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Thu Jan 15 11:09:04 EST 2015

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.

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.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/15/2015 8:20 AM, Andrew P. wrote:
> Hi, Dave.
> 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.
> 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?
> Andrew, KA2DDO
> author of YAAC
> > Date: Thu, 15 Jan 2015 12:34:08 +0000
> >
> > Monitoring 300bd AFSK, I often see digi hops (sometimes multiple!) 
> specified. I
> > also found that problem when trying to use YAAC with DireWolf for 
> both HF and
> > VHF tracking. At the time, I couldn't see a way to have a WIDE2-1 
> path on VHF,
> > and keep that away from HF. Andrew has done a lot of work since 
> then, so
> > when I get time I'll take another look at that.
> >
> > That's the problem for me, as before, never enough of "the right 
> sort of
> > contiguious time" is ever available, to fully get up-to-speed with 
> this stuff..
> >
> > 73.
> >
> > Dave G0WBX.
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20150115/98ff2a7f/attachment.html>

More information about the aprssig mailing list