[aprssig] TNCX setups?

[Cap Pennell]

Right, but...  If the local IGate station can use the digi, or can use
another higher digi that the fill-in digi's users can also hear, then such
messaging (with stations more than one digi hop away) can still work.

The only problem is we simply can't fit everything on only 1200baud VHF all
the time.
  
Often, things can be setup in one manner for "duration of demonstrated true
need" and then conscientiously reduced to be more courteous to all the other
VHF users afterward.
73, Cap

> -----Original Message-----
> From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On
> Behalf Of The Bland Ranch
> Sent: Thursday, July 16, 2009 4:57 PM
> To: aprssig at tapr.org
> Subject: Re: [aprssig] TNCX setups?
> 
> Quoting Cap Pennell <cap at cruzio.com>:
> 
> "Most often these days, a simple traceable fill-in digi is far better
> for our
> shared VHF network.  A traceable fill-in digi operates packets
> addressed via
> WIDE1-1 or it's own callsign ONLY, as in the final (second one below)
> sample
> setup."
> 
> Ya.....but.......
> 
> We learned this Field Day that if you want to send queries to use other
> APRS
> features that send back replies, a fill-in digi does not help you,
> since the
> returning data has no knowledge that it HAS to use that fill-in digi to
> get
> back to you.
> 
> Another factor to consider when planning the network.
> 
> Chuck Bland
> 
> Quoting Cap Pennell <cap at cruzio.com>:
> 
> > I'd extend the Beacon 3 and Beacon 4 intervals out even further,
> and/or
> > reduce their paths.  No help (for it's VHF users) for a digi to
> transmit
> > it's own position packet more broadly than across the next digi hop
> in all
> > directions.  Only reduces available airtime for all the other _users_
> of the
> > VHF freq.
> >
> > A full service WIDEn-N/SSn-N digi like this sample setup (first one
> below)
> > will be in a very good wide area network location, in cooperation
> with all
> > the neighbors, and so will surely be seen on the internet too with
> only a
> > minimal VHF digipath.
> >
> > Most often these days, a simple traceable fill-in digi is far better
> for our
> > shared VHF network.  A traceable fill-in digi operates packets
> addressed via
> > WIDE1-1 or it's own callsign ONLY, as in the final (second one below)
> sample
> > setup.
> > (UICall 1: WIDE1-1 and have UIFlood and UITrace empty.)
> >
> > 73, Cap KE6AFE
> >
> > > -----Original Message-----
> > > From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On
> > > Behalf Of Kai Gunter Brandt
> > > Sent: Thursday, July 16, 2009 1:21 PM
> > > To: bruninga at usna.edu; TAPR APRS Mailing List
> > > Subject: Re: [aprssig] TNCX setups?
> > >
> > > Robert Bruninga wrote:
> > > >> TNC-X with the XDigi module is great as long as the latest
> > > > firmware is
> > > >> used. Now its possible to remote configure it too.
> > > >>
> > > >> It's easy to setup as a Fill-In or a WideN digi with the SSn
> > > >> possibility
> > > >> too.
> > > >
> > > > Can you send us the setup commnds to make it New-N compliant?
> > > > Does it use UIFLOOD and UITRACE? Etc
> > > >
> > > > Bob, WB4APR
> > > >
> > >
> > > A bit modified from www.aprsla.net
> > >
> > >               C.     Set Digipeater Callsign.         :URCALL
> > > A.     Set Digipeater Alias.            :URDIGI
> > > F.     Set UIFlood Callsign.            :NOR (Norway use this as
> SSn)
> > > L.     Set UIFlood Limit.               :7
> > > T.     Set UITrace Callsign.            :WIDE
> > > M.     Set UITrace Limit.               :3
> > > 1.     Set UICall 1.                    :
> > > 2.     Set UICall 2.                    :
> > > 3.     Set UICall 3.                    :
> > > 4.     Set UICall 4.                    :
> > > 5.     Set UICall 5.                    :
> > > 6.     Set UICall 6.                    :
> > > 7.     Set UICall 7.                    :
> > > 8.     Set UICall 8.                    :
> > > D.     Set Dupe Time (x5 secs).         :2
> > >
> > > B.     Set Beacons
> > > 0. Beacon Destination Call :APNX01
> > > 1. Beacon 1 Path :                    (direct path)
> > > 2. Beacon 2 Path :WIDE2-1
> > > 3. Beacon 3 Path :WIDE2-2
> > > 4. Beacon 4 Path :NOR3-3
> > >
> > > 5. Beacon 1 inteval (x5 secs) :00120 Offset :0       (10.min)
> > > 6. Beacon 2 inteval (x5 secs) :00360 Offset :240     (30.min)
> > > 7. Beacon 3 inteval (x5 secs) :00720 Offset :120     (60min)
> > > 8. Beacon 4 inteval (x5 secs) :00720 Offset :255     (60min)
> > >
> > > A. Beacon 1 text:
> > > ;LA7BR *111111z6023.06N/00514.98Er434.700MHz T097 -2000kHz
> > >
> > > (The modified RX/TX TM-D710 requires the split in kHz as MHz
> doesn't
> > > work)
> > >
> > > B. Beacon 2 text:!0000.00NS00000.00E#PHG0000 W3,NORn SomePlace
> > > C. Beacon 3 text:!0000.00NS00000.00E#PHG0000 W3,NORn SomePlace
> > > D. Beacon 4 text:!0000.00NS00000.00E#PHG0000 W3,NORn SomePlace
> > >
> > > Q. Quit
> > >
> > >
> > > For a Fill-In i use UICall 1: WIDE1-1 and have UIFlood and UITrace
> > > empty.
> > >
> > > Kai Gunter
> > > LA3QMA
> > >
> > > _______________________________________________
> > > aprssig mailing list
> > > aprssig at tapr.org
> > > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >
> >
> > _______________________________________________
> > aprssig mailing list
> > aprssig at tapr.org
> > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >
> 
> 
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig