Order Tray | Contact Us | Home | SIG Lists

[aprssig] New DIGI Setup

Robert Bruninga bruninga at usna.edu
Sun Nov 16 18:27:54 UTC 2008


Regarding Digi Ltexts:

And of course, the LTexts should also have the proper BLT's and
LPT's to properly implement Proportional Pathing of the data.
This makes the digi ID itself locally (direct simplex) every 10
minutes to help passing mobiles, but then 1 hop and 2 hop QRM is
drastically reduced to once every 30 and once an hour
respectively.  
See www.aprs.org/newN/ProportionalPathing.txt

BLT 1    EVERY 00:30:00 START 00:00:00
BLT 2    EVERY 00:30:00 START 00:10:00
BLT 3    EVERY 01:00:00 START 00:20:00
BLT 4    EVERY 01:00:00 START 00:50:00
LTP 1    APN383 
LTP 2    APN383 
LTP 3    APN383 VIA WIDE2-1  <== notice this is a 1 hop path.
LTP 4    APN383 VIA WIDE2-2 

Bob, Wb4APR  

> -----Original Message-----
> From: aprssig-bounces at tapr.org 
> [mailto:aprssig-bounces at tapr.org] On Behalf Of Robert Bruninga
> Sent: Sunday, November 16, 2008 1:02 PM
> To: 'TAPR APRS Mailing List'
> Cc: miaprs at yahoogroups.com
> Subject: Re: [aprssig] New DIGI Setup
> 
> > trying to set up my KPC 3+ TNC, version 8.3.  
> > http://www.aprs.org/kpc3/kpc3+WIDEn.txt
> > 
> > I am confused on the Location Texts...
> 
> Towards the end of the file are exact examples of the four
> location texts.  All you have to do is enter your LAT/LONG and
> name of your state or section "SS" or "SSS" etc.  Everything
> after the SSn-N is free field.
> 
> LT  1 !DDMM.hhNSDDDMM.hhW#PHGphgd W2, SSn-N, ...
> LT  2 !DDMM.hhNSDDDMM.hhW#PHGphgd W2, SSn-N, ...
> LT  3 !DDMM.hhNSDDDMM.hhW#PHGphgd W2, SSn-N, ...
> LT  4 !DDMM.hhNSDDDMM.hhW#PHGphgd W2, SSn-N, ...
> 
> All of the LTexts should be identical so the Position Beacon
is
> not always changing and using up the new-posit LOG files on
> every user's PC... Also, notice that the " W2, SSn-N" is
exactly
> 10 spaces and so good placement of the next ten text or the
next
> 18 characters can be formatted to show up nicely on the D7 and
> D700 10x10x... Displays.
> 
> Also be sure that your BEACON TEXT has the local Frequency
> Object for the coverage area of that digi.  See
> www.aprs.org/localinfo.html
> 
> Hope that helps.
> 
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 




More information about the aprssig mailing list