Order Tray | Contact Us | Home | SIG Lists

[aprssig] Digi handling of WIDEn-N packets

Stephen H. Smith wa8lmf2 at aol.com
Sun Aug 21 02:30:03 UTC 2005


pagreen at gmail.com wrote:

>Hi All,
>
>  I noticed that I when I stopped using Xastir as a digi and let
>Digi_ned do it that the WIDE1-1 packets are call substituted AND
>WIDE1* added whereas before the call was substituted only with no
>WIDE1.  I want to know if there something special on why the UIDIGI
>and DIGI_NED flavors and possibly the stand alone KPC3's use the path
>of digicall,wide1* to complete the digipeat.  It makes the packet
>longer if I can omit it.  Is this a part of the UIFLOOD spec?
>
>73 de Pat --- KA9SCF.
>  
>
This is what WIDEn-N is supposed to do -- the first digi to process the 
N-n sequence is supposed to insert it's own call AS WELL AS decrementing 
the n-N.  No further digis farther down the n-N chain should do this.  
The intent is to allow users several hops away to know the general 
location that the packet originated from.  [ Obviously a position packet 
would already have this info, but a status or telemetry packet might not. ]



Stephen H. Smith    wa8lmf (at) aol.com
EchoLink Node:      14400    [Think bottom of the 2M band]
Home Page:          http://wa8lmf.com

"APRS 101"  Explanation of APRS Path Selection & Digipeating
  http://webs.lanset.com/wa8lmf/DigiPaths

Updated APRS Symbol Chart
  http://webs.lanset.com/wa8lmf/miscinfo/APRS_Symbol_Chart.pdf   

New/Updated "Rev G" APRS     http://webs.lanset.com/wa8lmf/aprs
Symbols Set for UI-View,
UIpoint and APRSplus:






More information about the aprssig mailing list