[aprssig] New n-N settings for ui-digi

[Bruce, KQ4TV]

On Apr 5, 2005, at 8:19 PM, Brian Webster wrote:

> Can anyone point me to a web page that will show settings for ui-digi 
> to set
> it up properly to use the new wide-n scheme?
>
>
>
> Brian, N2KGC
>

I will post an example here for discussions sake. Later I will put this 
on a web page.
N8DEU's web page has a good explanation of UIdigi parameters.
Hopefully he will update it if he chooses to adopt the changes for the 
new paradigm.

/*
	UIDIGI Configuration source file
         Version 1.9 BETA 3 20040101
	Written by Marco Savegnago IW3FQG
*/
DigipeaterCallsign     =       WB0NOO-2
DigipeaterAlias        =       UIDIGI
BeaconDestination      =       APZ193
InfoText               =       UIDIGI1.9BETA3 LastMod20050303 
kq4tv.at.bwm.us see www.nashvilleaprs.net
NorthPath              =
SouthPath              =
EastPath               =
WestPath               =
BudList                =
UIDigiCall             =       
RELAY,OHX,TN,WIDE3-3,WIDE4-4,WIDE5-5,WIDE6-6,WIDE7-7
UIDIGICallSubstitution =       1
UIFloodCall            =       TN
UIFLOODOptions         =       1
UITraceCall            =       WIDE
UITRACEOptions         =       0
TxDelay                =       30
FullDuplex             =       0
PPersistance           =       255
SlotTime               =       1
Frack                  =       5
Maxframe               =       4
Retry                  =       10
RespTime               =       100
LinkCheck              =       18000
DuplicateSuppression   =       30
LoopSuppression        =       3
HandleUISSID           =       0
ReplyToQuery           =       1
PreemptCalls           =
PreemptAdd             =
PreeemptedDigipeat	    =       0
UIMessage              =       1
UIOnly                 =       1
UIPID                  =       0
SysopPassword          =       yes there is something here
Beacon1Interval        =       1200
Beacon2Interval        =       2400
Beacon3Interval        =       4800
Beacon1Offset          =       0
Beacon2Offset          =       600
Beacon3Offset          =       1800
Beacon1Text            =       
!3615.49NS08654.31W#PHG5560/W-R-TN-OHX-Wn-N Nashville,TN
Beacon2Text            =       
!3615.49NS08654.31W#PHG5560/W-R-TN-OHX-Wn-N Nashville,TN
Beacon3Text            =       
!3615.49NS08654.31W#PHG5560/W-R-TN-OHX-Wn-N Nashville,TN
BeaconDestination      =       APNU193
Beacon1Path            =
Beacon2Path            =       WIDE
Beacon3Path            =       WIDE2-2
AuxPath                =
AuxDestination         =       AUX
AuxRate                =       0

For Northern Middle Tennessee I am inclined to make the following 
changes:

UIDigiCall             =      
RELAY,OHX,TN,WIDE1-1,WIDE2-1,WIDE2-2,WIDE3-1,WIDE3-2
UITraceCall            =      OHX

This is to allow wide dissemination of OHX WX information without it 
traveling outside the interested area.
I see BMX Bulletins in Nashville So I suppose that they might be seeing 
OHX Bulletins in Birmingham.
I am hoping that this might work to keep the packets closer to the OHX 
coverage area.

Comments are welcome.

Bruce, KQ4TV

--
Bruce W. Martin, KQ4TV
Trustee for NT4UX
Nashville Linux User Group - Amateur Radio- Special Interest Group
NLUG-AR-SIG