Order Tray | Contact Us | Home | SIG Lists

[aprssig] Device Capabilities & proportional pathing

Bob Bruninga bruninga at usna.edu
Thu Nov 10 17:05:55 UTC 2011

I think the easy answer to why PP and SB are not combined is that it takes more than a few lines of code, and I think the D710 is smack out of code space.  So if anyone can think of things we can give up in the D710, then that might free up some code space for my long list of wishes...

I suppose I should look at the SPEC, and see if there are not some more things that we can deprecate now that we have new coders with new clients that can keep up with small changes...


-----Original Message-----
From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf Of Tom Hayward
Sent: Thursday, November 10, 2011 11:14 AM
To: TAPR APRS Mailing List
Subject: Re: [aprssig] Device Capabilities & proportional pathing

On Wed, Nov 9, 2011 at 14:46, Lynn W. Deffenbaugh (Mr)
<ldeffenb at homeside.to> wrote:
> So, consider the following SB-triggered and PP-modified transmissions:
> SB sees you turn (from a stop), PP sends it out local
> SB sees you turn onto the highway, PP sends it out 1 hop
> SB sees you turn onto the Interstate, PP sends it out local
> You drive a (relatively) straight line, so SB goes onto a (fairly) long
> timer and PP sends it out 2 hops (finally, the world knows!)
> The Interstate turns, SB transmits, and PP sends it out no hops
> You drive straight again, so the long timer applies, PP sends it out 1 hop
> Another long time, PP sends out local
> You turn again, PP sends it out 2 hops
> You complete the turn (a broad sweeping 90), PP sends it out local
> ...
> It makes no sense (to me at least) to mix the two.
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

This sounds perfect to me! I just wish it was an option. Many times I
don't care how frequently "the world" hears me, but while I'm moving,
every 10 minutes or so would be nice. It's the stations within simplex
range that benefit from knowing every single turn I make. I find
myself running no-hops and SmartBeaconing occasionally because I don't
want to spam the digipeater network with each turn, but I do want the
event coordinator / incident commander to see the turn.

The reasoning behind Proportional Pathing is that the more local
information is, the more important it is. Using SmartBeaconing doesn't
make my information any more important to a station 30 miles away, so
why shouldn't I be able to use Proportional Pathing to variably limit
my hops? (rhetorical, I know you just gave your answer)

I understand there are many use cases that benefit from having
Proportional Pathing and SmartBeaconing mutually exclusive, but there
are also use cases that benefit from both features.


aprssig mailing list
aprssig at tapr.org

More information about the aprssig mailing list