[aprssig] UI question

[Steve Noskowicz]

Thanks Kai

Later I found that Argent's explanation seems to have a summary.  UIflood is not traceable and UItrace is traceable  I wasn't sure if that was all of it, so I kept quiet:
http://wiki.argentdata.com/index.php/APRS_digipeaters

-- 73, Steve, K9DCI
  http://k9dci.home.comcast.net/


--- On Mon, 4/12/10, Kai Gunter Brandt <kai.brandt at hjemme.no> wrote:

> Steve Noskowicz wrote:
> >   I may have been premature on Cap's
> reference.  It doesn't appear to fully explain UIFLOOD

> Probably easier to understand by some aprs examples:
> 
> Two digipeaters with UIFLOOD as WIDE and with callsign
> DIGI1 and DIGI2
> 
> Sending a packet like WIDE2-2 from i.e LA3QMA is going via
> DIGI1:
> LA3QMA,DIGI1*,WIDE2-1
> 
> Then via DIGI2:
> LA3QMA,DIGI2*,WIDE2
> 
> in other words not tracable.
> 
> Doing the same with UITRACE like WIDE
> 
> Sending a packet like WIDE2-2 from i.e LA3QMA is going via
> DIGI1:
> LA3QMA,DIGI1*,WIDE2-1
> 
> Then via DIGI2:
> LA3QMA,DIGI1,DIGI2*,WIDE2
> 
> and is tracable.
> 
> The bug in the TM-D700 is that "ID" is not working so when
> it digipeats it sends out the same thing as it hears i
> think. so it works more like NOID and that bad even in
> UIFLOOD
> 
> The TM-D710 do not have this bug. Anyhow to use the TM-D700
> (standalone)you need to configure it via a terminal software
> as turning it on in the menu is not the correct method.
> 
> Kai Gunter
> LA3QMA
> 
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>