| |
ZL3AI > APRDIG 25.09.06 01:15l 306 Lines 9678 Bytes #999 (0) @ WW
BID : 8819-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 27 #23, 1/4
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<ON0AR<IW2OAZ<ZL2BAU
Sent: 060924/2313Z @:ZL2BAU.#87.NZL.OC #:6215 [Waimate] $:8819-ZL3AI
From: ZL3AI@ZL2BAU.#87.NZL.OC
To : APRDIG@WW
Today's Topics:
1. Re: RE: New EU Paradigm also Uiview32 and New-N for the USA (Ron Stordahl)
2. Re: RE: New EU Paradigm also Uiview32 and New-N for the USA (John Habbinga)
3. Re: RE: New EU Paradigm also Uiview32 and New-N for the USA (Ron Stordahl)
4. RE: RE: New EU Paradigm also Uiview32 and New-N for the USA (Jim)
5. Re: RE: New EU Paradigm also Uiview32 and New-N for the USA (Ron Stordahl)
6. RE: [ui-view] Re: [aprssig] RE: New EU Paradigm also Uiview32 and New-N
for the USA (Cap Pennell)
7. RE: RE: New EU Paradigm (Robert Bruninga)
8. Re: RE: New EU Paradigm (Jan T. Pharo)
9. Re: RE: New EU Paradigm also Uiview32 and New-N for the USA (Jan T. Pharo)
10. RE: RE: New EU Paradigm also Uiview32 and New-N for the USA (Cap Pennell)
11. Re: [ui-view] Re: [aprssig] RE: New EU Paradigm also Uiview32 and New-N
for the USA (Ron Stordahl)
12. Re: RE: New EU Paradigm also Uiview32 and New-N for the USA (Ron Stordahl)
13. RE: [ui-view] Re: [aprssig] RE: New EU Paradigm also Uiview32 and New-N
for the USA (Robert Bruninga)
14. Re: RE: New EU Paradigm also Uiview32 and New-N for the USA (John Habbinga)
15. Re: RE: New EU Paradigm also Uiview32 and New-N for the USA (Ron Stordahl)
16. RE: [ui-view] Re: [aprssig] RE: New EU Paradigm also Uiview32 and New-N
for the USA (Cap Pennell)
17. RE: [ui-view] Re: [aprssig] RE: New EU Paradigm also Uiview32 and New-N
for the USA (David Huff)
18. New EU final summary...? (Robert Bruninga)
19. RE: New EU final summary...? (Cap Pennell)
20. Re: New EU final summary...? (Andy Pritchard)
21. Re: New EU final summary...? (John Ronan)
22. Re: New EU Paradigm (final comment) (Jan T. Pharo)
23. WINE for LINUX (Andrew Rich)
24. Re: WINE for LINUX (VE7GDH)
25. Re: Inexpensive Deviation Meter - Wrapup (Jim Campbell)
26. Re: New EU final summary...? (Ron Stordahl)
----------------------------------------------------------------------
Message: 1
Date: Thu, 21 Sep 2006 12:55:45 -0500
From: Ron Stordahl <ron.stordahl_at_digikey.com>
Subject: Re: [aprssig] RE: New EU Paradigm also Uiview32 and New-N for the USA
Here is the pertinent section of the Uiview32.ini file for digipeating
which I believe is in accordance with the New-N Paradigm for the USA:
[DIGI_OPTIONS]
DIGI_ENABLED=TRUE
UI_ONLY=FALSE
ALIAS_SUBSTITUTION=TRUE
DUPE_SUPPESS_SECONDS=30
ALIAS=N5IN-4,WIDE4-4,WIDE4-3,WIDE4-2,WIDE4-1,WIDE5-5,WIDE5-4,WIDE5-3,WIDE5-2,WI5
DE-1,WIDE6-6,WIDE6-5,WIDE6-4,WIDE6-3,WIDE6-2,WIDE6-1,WIDE7-7,WIDE7-6,WIDE7-5,WI7
DE-4,WIDE7-3,WIDE7-2,WIDE7-1
UIFLOOD=MN
UITRACE=WIDE
WIDEN-N=TRUE
TRACEN-N=TRUE
SUBST_ALIAS=N5IN-4
EXCLUDED=""
[DIGI_ROUTES]
1=""
2=2
3=""
4=""
5=""
6=""
7=""
8=""
9=""
10=""
11=""
12=""
13=""
14=""
15=""
16=""
This configuration allows up to WIDE3-3. It will digipeat (and decrement)
WIDE1-1,WIDE2-2 and (unfortunately perhaps) also WIDE1-1,WIDE3-3. WideN-n
is traced. In this case SS is MN (Minnesota).
If someone believe this configuration is incorrect I would like to know.
Perhaps column width issues with e-mail will mess up this info above. I
could attach the entire Uiview32.ini file or better yet, those who want to
see it can pick it up here:
http://dxspots.com/uiview32.ini
Ron, N5IN
Andy Pritchard wrote:
>Hi All
>
>======================
>European APRS Guidelines
>======================
>
>http://www.apritch.myby.co.uk/uiview_neweu.htm
>
>This page contains guidelines on maximising the capacity of our
>European APRS network (144.800Mhz).
>
>======================
>Fixing the APRS Network
>======================
>
>http://www.apritch.myby.co.uk/uiview_newn-n.htm
>
>The APRS network in some parts of the USA suffer from major
>congestion.This is mainly due to the nature of the original design of
>the APRS network combined with a dupe check issue found in stand alone
>KPC3's (apparently).
>
>I hope that helps...
>
>Andy, M0CYP - Telford
>http://www.apritch.myby.co.uk/uiview.htm
>http://www.apritch.myby.co.uk/radioprop.htm
------------------------------
Message: 2
Date: Thu, 21 Sep 2006 13:08:38 -0500
From: "John Habbinga" <kc5zrq_at_gmail.com>
Subject: Re: [aprssig] RE: New EU Paradigm also Uiview32 and New-N for
the USA
You do not need to include WIDE7-1,WIDE6-1,WIDE5-1, or WIDE4-1. These will
decrement once and terminate. Including them only serves to further
inhibit duplicate checking amongst other digipeaters in the area.
On 9/21/06, Ron Stordahl <ron.stordahl_at_digikey.com> wrote:
ALIAS=N5IN-4,WIDE4-4,WIDE4-3,WIDE4-2,WIDE4-1,WIDE5-5,WIDE5-4,WIDE5-3,WIDE5-2,WI5
DE-1,WIDE6-6,WIDE6-5,WIDE6-4,WIDE6-3,WIDE6-2,WIDE6-1,WIDE7-7,WIDE7-6,WIDE7-5,WI7
DE-4,WIDE7-3,WIDE7-2,WIDE7-1
------------------------------
Message: 3
Date: Thu, 21 Sep 2006 13:33:52 -0500
From: Ron Stordahl <ron.stordahl_at_digikey.com>
Subject: Re: [aprssig] RE: New EU Paradigm also Uiview32 and New-N for
the USA
Group <ui-view_at_yahoogroups.com>
John
That's a good point (although how that effects duplicate checking I do not
understand). But I do see that WIDE7-1 etc would be used up and thus need
not be in the list. Thus this should be revised to:
ALIAS=N5IN-4,WIDE4-4,WIDE4-3,WIDE4-2,WIDE5-5,WIDE5-4,WIDE5-3,WIDE5-2,WIDE6-6,WI6
DE-5,WIDE6-4,WIDE6-3,WIDE6-2,WIDE7-7,WIDE7-6,WIDE7-5,WIDE7-4,WIDE7-3,WIDE7-2
Ill update my uiview32.ini file accordingly.
Beyond that change doesn't anyone else see anything out of compliance with
New-N?
It still does irk me that WIDE1-1,WIDE3-3 gets 4 digipeats on an N=3
limited digipeater. Seems to me that the recommendation should be to
configure the digipeater for N=2 and then recommend WIDE1-1,WIDE2-2 to get
3 digipeats if you need it.
Ron, N5IN
John Habbinga wrote:
>You do not need to include WIDE7-1,WIDE6-1,WIDE5-1, or WIDE4-1. These
>will decrement once and terminate. Including them only serves to
>further inhibit duplicate checking amongst other digipeaters in the
>area.
>
>On 9/21/06, Ron Stordahl <ron.stordahl_at_digikey.com> wrote:
>ALIAS=N5IN-4,WIDE4-4,WIDE4-3,WIDE4-2,WIDE4-1,WIDE5-5,WIDE5-4,WIDE5-3,WIDE5-2,WE
ID5-1,WIDE6-6,WIDE6-5,WIDE6-4,WIDE6-3,WIDE6-2,WIDE6-1,WIDE7-7,WIDE7-6,WIDE7-5,WE
ID7-4,WIDE7-3,WIDE7-2,WIDE7-1
------------------------------
Message: 4
Date: Thu, 21 Sep 2006 19:42:14 +0100
From: "Jim" <jim_at_stuckinthemud.org>
Subject: RE: [aprssig] RE: New EU Paradigm also Uiview32 and New-N for
the USA
Why do any of these need to be put in as aliases?
Surely the whole point of the n-n system is that the smart part of the digi
recognises it and processes accordingly. If its traceability that's required
then just enable callsign substitution on WIDE as well as TRACE.
Jim, G1HUL
....trying to understand the odd things in life!
-----Original Message-----
>John
>
>That's a good point (although how that effects duplicate checking I do not
>understand). But I do see that WIDE7-1 etc would be used up and thus need
>not be in the list. Thus this should be revised to:
>
>ALIAS=N5IN-4,WIDE4-4,WIDE4-3,WIDE4-2,WIDE5-5,WIDE5-4,WIDE5-3,WIDE5-2,WIDE6-6
>,WIDE6-5,WIDE6-4,WIDE6-3,WIDE6-2,WIDE7-7,WIDE7-6,WIDE7-5,WIDE7-4,WIDE7-3,WID
>E7-2
>
>Ill update my uiview32.ini file accordingly.
>
>Beyond that change doesn't anyone else see anything out of compliance with
>New-N?
>
>It still does irk me that WIDE1-1,WIDE3-3 gets 4 digipeats on an N=3 limited
>digipeater. Seems to me that the recommendation should be to configure the
>digipeater for N=2 and then recommend WIDE1-1,WIDE2-2 to get 3 digipeats if
>you need it.
>
>Ron, N5IN
------------------------------
Message: 5
Date: Thu, 21 Sep 2006 13:48:22 -0500
From: Ron Stordahl <ron.stordahl_at_digikey.com>
Subject: Re: [aprssig] RE: New EU Paradigm also Uiview32 and New-N for
the USA
The reason as I understand it is that one of the 'excessive' paths, say
WIDE7-7 will be thus repeated only a single time. By including it as a
'alias' it is not processed by the decrementing procedure.
Ron, N5IN
------------------------------
Message: 6
Date: Thu, 21 Sep 2006 11:55:14 -0700
From: "Cap Pennell" <cap_at_cruzio.com>
Subject: RE: [ui-view] Re: [aprssig] RE: New EU Paradigm also Uiview32
and New-N for the USA
Right, for a MiNnesota (UIFLOOD=MN) "Wn,MNn" digi. And to make it a
"W2,MNn" digi you could add WIDE3-3,WIDE3-2 to the list already at ALIAS
And in the UI-View32 program:
Setup,Station Setup,Beacon comment:PHG5110/W2,NCAn/Minneapolis <substitute
your actual PHG and City here>
Setup,Station Setup,Symbol:No.Digi O'ly:S
73, Cap KE6AFE
>-----Original Message-----
>
>Here is the pertinent section of the Uiview32.ini file for digipeating
>which I believe is in accordance with the New-N Paradigm for the USA:
>
>[DIGI_OPTIONS]
>DIGI_ENABLED=TRUE
>UI_ONLY=FALSE
>ALIAS_SUBSTITUTION=TRUE
>DUPE_SUPPESS_SECONDS=30
>ALIAS=N5IN-4,WIDE4-4,WIDE4-3,WIDE4-2,WIDE4-1,WIDE5-5,WIDE5-4,WIDE5
>-3,WIDE5-2,WIDE5-1,WIDE6-6,WIDE6-5,WIDE6-4,WIDE6-3,WIDE6-2,WIDE6-1
>,WIDE7-7,WIDE7-6,WIDE7-5,WIDE7-4,WIDE7-3,WIDE7-2,WIDE7-1
>UIFLOOD=MN
>UITRACE=WIDE
>WIDEN-N=TRUE
>TRACEN-N=TRUE
>SUBST_ALIAS=N5IN-4
>EXCLUDED=""
>[DIGI_ROUTES]
>1=""
>2=2
>3=""
>4=""
>5=""
>6=""
>7=""
>8=""
>9=""
>10=""
>11=""
>12=""
>13=""
>14=""
>15=""
>16=""
>
>This configuration allows up to WIDE3-3. It will digipeat (and
>decrement) WIDE1-1,WIDE2-2 and (unfortunately perhaps) also
>WIDE1-1,WIDE3-3. WideN-n is traced. In this case SS is MN (Minnesota).
>
>If someone believe this configuration is incorrect I would like to
>know. Perhaps column width issues with e-mail will mess up this info
>above. I could attach the entire Uiview32.ini file or better yet, those
>who want to see it can pick it up here:
>
>http://dxspots.com/uiview32.ini
>
>
>Ron, N5IN
------------------------------
Read previous mail | Read next mail
| |
