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

Robert Bruninga bruninga at usna.edu
Thu Jan 15 08:11:54 CST 2015


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.



If you missed it, I deplore generic digipeating on HF.



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.



Bob, Wb4aPR



*From:* aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] *On
Behalf Of *Andrew P.
*Sent:* Thursday, January 15, 2015 8:20 AM
*To:* TAPR APRS Mailing List
*Subject:* Re: [aprssig] HF packet (Was Re: weak signal ISS packet)



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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20150115/3f87d713/attachment.html>


More information about the aprssig mailing list