[aprssig] D700 digi and unproto

[Greg Noneman]

Just to clarify this... All the LA/OC area high-level digipeaters  
respond to WIDE1-1,WIDE2-1, WIDE2-2 and WIDE3-3.  The metro area  
digis force one-hop digipeating to minimize channel loading.   
Outlying digis allow two-hop digipeating and trap high digi-hop paths.


73,
Greg
WB6ZSU
SoCal digi sysop

On Feb 13, 2006, at 4:03 PM, Steve Sobodos wrote:

>  Interesting, how is the message getting out that 2-2 is the ONLY  
> valid path
>  in So cal? I just monitored for a few minutes and many are using
> non-WIDE2-2
>  paths. The comments on one of the four highest Digi's in So Cal  
> (N6EX-1)
>  says ">WIDE2-2 is best path in SoCal". I don't read that as "The only
> path".
>  Also the Yahoo Group for California APRS (ca_aprs) has no postings  
> saying
>  that 1-1 or 2-1 will be ignored. To the contrary, they are still
>  recommending WIDE1-1, WIDE2-1.
>
>
>> ----- Original Message -----
>> From: <wa8lmf2 at aol.com>
>> To: <aprssig at lists.tapr.org>; <steve at scsvideo.com>
>> Sent: Monday, February 13, 2006 1:26 PM
>> Subject: Re: [aprssig] D700 digi and unproto
>>
>>
>>>
>>>
>>> -----Original Message-----
>>> From: Robert Bruninga <bruninga at usna.edu>
>>> To: aprssig at lists.tapr.org; steve at scsvideo.com
>>> Sent: Mon, 13 Feb 2006 15:21:16 -0500
>>> Subject: Re: [aprssig] D700 digi and unproto
>>>
>>>
>>> All digis everywhere should also respond to WIDE1-1.
>>> THat is the beauty of it.  If the big digi hears it first,
>>> it sends the packet on its way.  If the mobile D700
>>> also hears it, it will digipeat it once, but the big
>>> digi (UIDWAIT set to zero) will have alrady sent it
>>> and so the big digi will not duplicate it a second time.
>>>
>>> But if the big digi did not hear it the firs time, then
>>> it will digipeat it from the D700.  THis is how the
>>> WIDE1-1 fill-in-digi system works.
>>>
>>> Bob, Wb4APR
>>>
>>> ==================
>>>
>>> Except that the SoCal/L.A.-area high-level digis now ONLY respond to
>>> WIDE2-2 -- nothing else.....
>>>
>>>
>>> Stephen H. Smith    wa8lmf (at) aol.com