[aprssig] Viscous digipeating (was: Digi Question)

Samúel Úlfr Þór Guðjónsson tf2sut at ulfr.net
Tue Mar 19 18:22:23 CDT 2013


Oh yeah, and actually to be more accurate, it'd have to check APRS IS and
see if the packet *really* went from RF to IS.
Maybe that's an idea? But that would require that digipeater to have IGate
functionality, or at least be able to listen to APRS IS. That could
perhaps, improve the QRM even more? And it wouldn't stop NOGATE or RFONLY
from digipeating again...

I do however think that this problem can be improved, so to speak, with
tactical positions of digipeaters. So that every fillin would be able to
hear at least one high level digipeater (actually, why set up a fillin if
you can't reach a high level digipeater?) but wont be able to throw the
packet to too many high levels (decrease TX power perhaps if necessary?)

This may need some thinking, hi hi.

73 de TF2SUT - Samúel


On 19 March 2013 21:13, Lynn W. Deffenbaugh (Mr) <ldeffenb at homeside.to>wrote:

> On 3/19/2013 4:01 PM, Samúel Úlfr Þór Guðjónsson wrote:
>
>>
>> That way, the digipeater will only digipeat if no other digi hears the
>> packet, but does not add extra traffic to RF if the packet is received by
>> another digi. TX IGate would also be good within that setup, with or
>> without the digipeater functions.
>>
>
> Well, at least that's the hope of viscous digipeating.  It would be more
> accurate to say:
>
>  A viscous digipeater will only digipeat a packet if it doesn't decode
>> another digipeat of the packet within the delay period.
>>
>
> It is completely based on receiving and decoding the remote digipeater's
> packets as there is no way to truly know that "no other digi" heard and/or
> digipeated the packet.
>
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
>
> ______________________________**_________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/**listinfo/aprssig<http://www.tapr.org/mailman/listinfo/aprssig>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20130319/401ca18a/attachment.html>


More information about the aprssig mailing list