[aprssig] [APRS] Announcement of WA1PLE-15 digipeater in SW Boston Area (NOT)

Tony VE6MVP tony at ve6mvp.com
Tue Sep 24 16:23:22 CDT 2013


At 03:18 PM 2013-09-24, Tony VE6MVP wrote:
> >So let me see if I can reword this for clarity (check me on this):
> >
> >The digi should announce a voice repeater that is useful _in_ _the_
> >_coverage_ _area_ _of_ _the_ _digi_.
> >
> >As such, if several short-range digis (out of range of each other)
> >were scattered around the same long-range repeater, could (and should)
> >they all announce the same repeater (using no digipeat aliases in
> >their announcement packets)? Seems like that would ensure the traveler
> >would hear about the repeater from one of the digis he was passing
> >(regardless of which direction he was relative to the repeater)?
> >
> >But then who decides _which_ of the multiple digis should do it?

<snip>

>In the event that the digi's can't all see the originating digi I 
>might set a chain of digi's in the path so the packet "bounces" from 
>one to the next in the ring.   Again Bob and I disagree on that.

Actually when I think about it I'm wrong on that one.  At least in 
highly utilized areas.  You would be best putting the repeater object 
with no path in each of those digi's whether they can hear each other 
or not.   Now what will happen is the repeater object would 
undoubtedly be heard outside the voice repeaters range.  But given 
that my primary APRS object source is the Nuvi 360 list sorted by 
distance to me that isn't a problem for me.

And the reality is that is what we should be doing out here.   But 
it's more convenient to update just one digi than multiple digi's 
with the repeater object.

Tony 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20130924/d378b6e5/attachment.html>


More information about the aprssig mailing list