Order Tray | Contact Us | Home | SIG Lists

[aprssig] NEW PARADIGM Settings for Digi's

Robert Bruninga bruninga at usna.edu
Tue Apr 19 23:10:21 UTC 2005


I thought I would share this Question/Answer:

>Why do we need the W3,SSn in the new DIGI beacons?
>It really, truly, doesn't help me while I'm driving, since I 
>already know our digis support WIDEn-N, and I'm 
>probably not going  to change my outgoing path to SSn-N

This info is for the traveler, and for the Network designer
and for everyone else that cares about the network.
Without this, no one but the SYSOP knows for sure what 
is in the digi.  ALso add ",WX" if the digi also has a WX
station.  For example ...PHG5630/W3,MDn,WX... would
be a New Paradigm Digi in Maryland supporting WIDEn-N
up to 3, and MDn-N and has a remote WX station attached.

Most of the problem we have with all of today's digis is 
that NO ONE but the sysops know what each digi does, 
and  MOST of the sysops have forgotten even what
they set it to.  Thus our network is a big unknown.

It only makes sense for the digi itself to announce
its capabilities for *everyone* to be kept informed.
And for the SYSOP to keep this info current with
the current settings so that anyone can see what the
network capabilities are in an area.

Including those of us that kibitz from afar...

Also, if nothing else, since it is a new standardized way
of reporting the New n-N Paradigm, it gives a quick
visual clue that the digi has been upgraded and is
not still showing "W-R-T" which was the old way.

And of course, put these in the first bytes of the beacon
(after the PHG) so that it shows up on the front panel
of the mobiles with front panel displays so they can see
what kind of network they are in...

de Wb4APR, Bob



>>> David Dobbins <ddobbins at gmail.com> 4/19/05 6:13:06 PM >>>
 On 4/19/05, Robert Bruninga <bruninga at usna.edu> wrote: 
> 
> Comments on DIGIS with WX:
> 
> >>> David Dobbins <ddobbins at gmail.com> 4/19/05 5:00:53 PM >>>
> > For the remote WX digipeaters, which we have probably
> >15 of across the region, I need some help to verify this will work:
> >This is for a WX WIDEn-N combo, other settings as in regular
WIDEn-N:
> > BLT 1 E 00:20:00 START 00:00:00
> >BLT 2 E 00:20:00 START 00:10:00
> > LTP 1 APN382 VIA WIDE2-2
> > LTP 2 APN382 VIA WIDE2-2
> > LT 1 (data automatically parsed from weather station)
> >LT 2 !4720.20NS12320.45W#PHG5660/Ko Peak APRS K7GPS
> 
> First you need to include in this POSIT the W3,WAn to
> show what its capabilities are. I'd make them say something
> like PHG..../W3,WAn,WX Ko Peak... K7GPS
> which will show like this on the Kenwood:
> DIGICALL:
> W3,WAn,WX
> Ko Peak...
> K7GPS
> 
> which is very valuable info for the mobile
> 
> >We need to make sure these get into a nearby iGate
> >so the data can be uplinked to NWS. In some rural cases we may
> >need to extend the path to WIDE3-3.
> 
> Remember that WIDE2-2 from a digi goes just as far as
> WIDE3-3 does from a user on the ground... For those
> digis that are only 1 digi hop away from an Igatre
> use WIDE2-1.
> 
> Bob
> 
> > I see no need for the 3rd and 4th slots used here.
> 
> On 4/19/05, Robert Bruninga <bruninga at usna.edu> wrote:
> >
> > >>> "Herb Gerhardt" <hgerhardt at wavecable.com> 4/19/05 1:01:18 AM
>>>
> > > Bob, can you help with this paragraph.
> >
> > > RELAY ONLY DIGIPEATERS: There will be occasion when coverage of
a
> > WIDE
> > >digi isn't complete, but another WIDE digi would/might interfere
> with
> > the
> > >other's operation, e.g. too close in proximity. In that case you
> may
> > need
> > >the help of a RELAY digi to get your signal out to the world. You
> > would
> > >configure your digipeater near identical to the WIDE settings,
> except
> > with
> > >UIDIGI should be RELAY (leave off WIDE and TRACE).
> >
> > Yes, I would word it this way:
> >
> > FILL-IN DIGIPEATERS: There will be occasion when coverage
> > of a WIDEn-N digi isn't complete, but another WIDEn-N digi
> > would just add additional QRM to the channel. In that case you
> > may need the help of a ONE-HOP digi to get your signal out to
> > the world. You would configure your digipeater near identical to
> > the WIDEn-N digi settings, except with UIDIGI should be set
> > to WIDE1-1 (leave off WIDE and TRACE and do not enable
> > UIFLOOD nor UITRACE. This digi will only respond as a first
> > hop and only to mobiles with the path of WIDE1-1,WIDE2-1.
> >
> > Bob
> >
> 
> --
> David Dobbins
> Medical Lake, WA
> 



-- 
David Dobbins
Medical Lake, WA




More information about the aprssig mailing list