[OZAPRS] NEW Digi settings as currently used in VK6 (for peerreview)

Chris Hill chris.hill at crhtelnet.com.au
Thu Nov 2 23:30:32 EST 2006


Hi All,

 

Here is the way I've configured some of the key settings in a couple of
the
key APRS digis here in VK6.  The example is for VK6KRB-2 (covering the
metro
area), however similar settings have been applied to VK6KSB-1, and will be
applied to VK6RLK-1 next week. I seem to have killed VK6RLK-1 when
reprogramming over the air :-(

 

 

# Beacon timings

BEACON   EVERY 18 min

BLT 1 EVERY 00:09:42

BLT 2 EVERY 00:29:00

BLT 3 EVERY 01:00:00

BLT 4 EVERY 01:00:10

BTEXT    Testing in Lesmurdie

CD       SOFTWARE

CTEXT    Messages and info to aprs at vhf.wirelessplanet.com.au

# Useful for timestamping of the "j l" command when connected to the PBBS

DAYTIME  10/30/06 23:00:52

DIGIPEAT ON

FLOW     OFF

HBAUD    1200

# Note that there is a space between ".4" and "SN", and between ".3" and
"E#"

# Note also that Power Height Gain (PHG) is defined, 

# as per tool at http://www.nashvilleaprs.net/apps/phgcalc.php 

LT 1 !3200.4 SN11602.3 E#PHG5650/WIDE Mazenod College

LT 2 !3200.4 SN11602.3 E#PHG5650/WIDE Mazenod College, Lesmurdie

LT 3 

LT 4 

# "APN382" means Kantronics KPC3+ with firmware 8.2

# As per http://www.ew.usna.edu/~bruninga/aprs/kpc3+WIDEn.txt 

LTP 1 APN382 VIA WIDE1-1

LTP 2 APN382 VIA WIDE2-2

LTP 3 APN382 VIA WIDE3-3

LTP 4 APN382 VIA WIDE4-4

LTRACK   0

# This is the nasty one.  must be set to OFF, otherwise stops working when
buffer fills!

MONITOR  OFF

MYCALL   VK6KRB-2

MYALIAS  disabled

MYDROP   0

MYNODE   %

MYPBBS   %

# Enabled mini PBBS, so can connect to VK6KRB-2 to issue "J L" command, 

# (to see what stations have been heard)

PBBS     1

# Sending telemetry every 30 minutes makes it easy to see reliability via

# number of consecutive telemetry messages that appear in (eg):

# http://www.findu.com/cgi-bin/raw.cgi?call=VK6KRB-2 

TELEMTRY 180 (1800 sec)

# Maybe 300ms is a bit slow, but at least we are pretty safe that remote
mute will be open!

TXDELAY  30 (300 msec)

# Standard beacon goes out via one digi hop

UNPROTO  APN382 VIA WIDE1-1

# This is important.

# WIDE1-1 means that the simple old "APRS v WIDE" will work, despite a bug
in 8.2 firmware

# WIDE5-5, 6-6, 7-7 means that greedy paths are only accorded a single
hop!

UIDIGI   ON WIDE1-1,WIDE5-5,WIDE6-6,WIDE7-7

# Helps two digis to TX at the same time.  "beneficial fratricide"!

UIDWAIT  OFF

# I'm not confident that "VK6" is correct here :-(

UIFLOOD  VK6,30,ID

# This is important.  pretty much the core of the new paradigm.

# WIDE, WIDE2-2 etc are given callsign substitution and the SSID is
decremented

UITRACE  WIDE,30

USERS    2

 

 

 

Any feedback, suggestions, clarification and/or criticisms will be happily
received!

 

 

Regards,

 

 

 

 

Chris

vk6kch

 

 

 

 

-----Original Message-----
From: ozaprs-bounces at aprs.net.au [mailto:ozaprs-bounces at aprs.net.au] On
Behalf Of Dion Bramich
Sent: Thursday, 2 November 2006 8:22 PM
To: VK / ZL APRS Users
Subject: Re: [OZAPRS] European v US newparadigmand pathlimiting
+confusion....

 

I'll get it organised for you.

 

On Thu, 02 Nov 2006 23:19:45 +1100, Chris Hill  

<chris.hill at crhtelnet.com.au> wrote:

 

> Hi Dion,

> 

> Can you give us all some worked examples?

> 

> What settings did you use in your TNC for UIFLOOD, etc?

> 

> 

> Regards,

> 

> 

> 

> Chris

> vk6kch

> 

> 

> -----Original Message-----

> From: ozaprs-bounces at aprs.net.au [mailto:ozaprs-bounces at aprs.net.au] On

> Behalf Of Dion Bramich

> Sent: Thursday, 2 November 2006 10:46 AM

> To: VK / ZL APRS Users

> Subject: Re: [OZAPRS] European v US new paradigmand pathlimiting

> +confusion....

> 

> Zone or state based routing needs to be implemented, it should be

> mandatory.  We are using it here, its excellent.  There will be no near

> border confsuion, it'll solve problems.  It could indeed be taken out

> further to major population areas, it allows so much more control over  

> the

> network than other systems proposed.  I really do believe its easier to

> understand than the old RELAY WIDE TRACE arrangement, newcomers would  

> pick

> it up quicker.

> 

> Dion.

> VK7YBI.

> 

> On Thu, 02 Nov 2006 10:41:59 +1100, Ron Perry <ronk at sunlinux.com.au>  

> wrote:

> 

>> On Thu, 2006-11-02 at 09:32 +1030, Andrew McDade wrote:

>>> Gday all,

>>> 

>>> What are the requirements with regards to the number of path hops we

>>> would

>>> require Nationally. I would see this being a bit of a comprise so as
to

>>> maintain a standard.

>>> There is talk about a maximum of two hops .. i.e.. using WIDE2-2 for

>>> home

>>> stations and perhaps WIDE1-1,WIDE2-1 for mobiles.  Will this suffice

>>> for all

>>> of Australia or do we look at 3 hops WIDE3-3 for home stations and

>>> WIDE1-1,WIDE2-2 for mobiles.

>>> 

>>> Points taken regarding Not utilizing SSn-n , as Ron mentions, this  

>>> would

>>> certainly be a problem for networks close to state borders etc.

>>> 

>>> What about a zone or region based system used in conjunction with the

>>> generic WIDEn-n system. If we want to cellularize the network, if  

>>> indeed

>>> this is what we want to do, then probably the best way to do it would

>>> be to

>>> use a zone or region based system. ie.. Utilize the first 4 letters of

>>> the

>>> major centre containing the regions Igate. ie. ADEL3-3, MILD3-3,

>>> MELB3-3,

>>> HOBA3-3 etc etc. Home stations , digipeaters and mobiles that don't

>>> frequently travel out of the region would ( could ) utilize the path

>>> ZONE3-3. Mobiles and portable stations that are traveling nation wide

>>> could

>>> use the generic path of WIDE3-3 or WIDE1-1,WIDE2-2. New aprs users,

>>> utilizing information gleaned from the net etc. would probably utilize

>>> WIDE1-1,WIDE2-2 or WIDE3-3 which would work anywhere  all of the time.

>>> The

>>> zonen-n based paths could be gradually implemented within each region

>>> and

>>> would probably be utilized initially by more established aprs users.

>>> 

>> Maybe the Zone based system could also be not "mandatory", and

>> implemented as time and regional activity needed.

>> 

>>> Its something to have a think about anyway

>>> 

>> 

>> Well worth thinking about.  I like it.

>> 

>> And the bike (VK3ECV-9) will be out and about from Friday until
Tuesday.

>> Marlene and I are spending 4 nights at Mt Beauty.

>> 

>> 

>> Regards,

>> Ron

>> vk3ecv

>> 

>> 

>> 

>> 

>> _______________________________________________

>> Ozaprs mailing list

>> Ozaprs at aprs.net.au

>> http://aprs.net.au/mailman/listinfo/ozaprs

>> 

>> 

> 

> 

> 

 

 

 

-- 

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Send instant messages to your online friends http://au.messenger.yahoo.com


_______________________________________________

Ozaprs mailing list

Ozaprs at aprs.net.au

http://aprs.net.au/mailman/listinfo/ozaprs

_______________________________________________
Ozaprs mailing list
Ozaprs at aprs.net.au
http://aprs.net.au/mailman/listinfo/ozaprs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://second.aprs.net.au/pipermail/ozaprs/attachments/20061102/54e33ec0/attachment.htm 


More information about the Ozaprs mailing list