A shorter answer: It is WAD (Working As Designed). Local fill-in digis should only react to WIDE1-1 Higher digis will react to any WIDEn-N including WIDE1-1.
Lynn (D) - KJ4ERJ PS. I've always wondered why it's WIDEn-N instead of WIDEN-n since the number before the dash should be greater than or equal to the number after the dash, but then I guess it would be hard to tell the difference between WIDEN-n (WIDEN with an -SSID of n) and WIDEN-n (the WIDE alias level N with n hops left, expressed correctly as WIDEn-N). James Ewen wrote: > On Mon, Aug 31, 2009 at 8:30 AM, > usna71<[email protected]> wrote: > > >> Hello, I am running a T2-135 and am a bit concerned about our local network. >> My path is WIDE1-1, WIDE2-1 and my mobile call is KB1MOV-1 and I am >> seeing the following from our local very high digi, W1UWS >> It seems to me that W1UWS is responding on WIDE1? Is that true? >> Should it be? I think he has a Kantronics. I just don't know how to read >> the >> paths from aprs.fi. Can you help me? >> >> 2009-08-31 10:20:05 EDT: >> KB1MOV-1>APOT2A,W1UWS,WIDE1,KA2QYE-10,WIDE2*,qAR,N2QDK-1:/141958h4341.68N/07216.83W>000/000/A=000602 >> HDOP01.2 SATS06 P1 Good Fix >> >> 2009-08-31 10:21:36 EDT: >> KB1MOV-1>APOT2A,W1UWS*,WIDE1*,KQ1L-1*,WIDE2*,qAR,N1JOV-9:/142131h4341.68N/07216.82W>000/000/A=000516 >> HDOP01.6 SATS06 P1 Good Fix >> > > Slow down there Henny Penny! 8) Your sky is not falling! > > The APRS digipeater have always been set up to act upon both the > "RELAY" and "WIDE" style aliases. I emphasize these generic names, as > they are not actual aliases in use anymore. > > All high digipeaters need to be able to act upon the usual WIDEn-N > alias, of which WIDE1-1 is a subset. Fill-in digipeaters which are > designed to help low powered stations into the main digipeaters should > only act upon WIDE1-1. > > When you are running a path of WIDE1-1,WIDE2-1 from your low powered > handheld/mobile station, you are asking for 2 hops, with the option of > having the first hop going through a fill-in digipeater. If you are > within range of a high main digipeater, then your first hop will be > through that main digi. > > There's no need to have fill-in digipeaters inside the footprint of a > strong main digi, just to handle the WIDE1-1 path elements. The whole > reason behind using the somewhat confusing WIDE1-1 alias for fill-in > digipeaters is so that the main digipeaters WILL act upon that element > using the same anti-duping routine that the usual WIDE2-2 or WIDE3-3 > path elements activate. > > The use of WIDE1-1,WIDE2-1 as a "normal" path request is a work around > to get the main digipeaters to give 2 hops, one when the WIDE1-1 is > acted upon, and a second when the WIDE2-1 is acted upon. It is > functionally equivalent to WIDE2-2 as far as the main digipeaters are > concerned. The explicit WIDE1-1 element allows fill-in digipeaters to > boost only on the first path element. If we ran WIDE1-1,WIDE1-1 as an > outgoing path, then you could end up activating 2 fill-in digipeaters > in a row, 2 main digipeaters in a row, a fill-in digipeater then > maindigipeater, or a main digipeater then fill-in digipeater. > > There is a method to the madness! > > James > VE6SRV > > > ------------------------------------ > > Yahoo! Groups Links > > > > >
