OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   03.02.03 14:28l 205 Lines 9231 Bytes #999 (0) @ WW
BID : 768-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 23, 2/7
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<IK1ZNW<IR0NET<VK3TE<VK4TUB<ZL2BAU<ZL3VML
Sent: 030128/1051Z @:ZL3VML.#80.NZL.OC #:58322 [Chch-NZ] FBB7.00i $:768-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

Subject: Re: ID Digipeaters
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 23 Jan 2003 10:33:48 -0500 (EST)
X-Message-Number: 9

On Thu, 23 Jan 2003, Bruce W. Martin, KQ4TV wrote:

>but I am confused on this ID stuff. I thought that callsign substitution
>was a good thing so that actual digipeater paths could be observed.

No, ID causes the digi to FORCE its own callsign into every packet and to
overwrite and obliterate any previous path data that usually contains the
originating DIGI.  Thus the much more valuable information on where the
packet -entered- the APRS network, is obliterated by these "ID" digis that
show you that they were the LAST digi to handle the packet.

If you are in range of DIGIx, then every single packet you see will show
"DIGIx" which is totally useless info.  You already should know that you
are receiving all packets from DIGIx, and if you dont know that, you can
instantly find out by sending out a packet via WIDE and see how it comes
back...

>You infer that this makes the network "broken" because packets get
>longer.

No, it makes it broken, because it is obliterating useful data (that
can not be obtained any other way) with useless data (that can be easily
gotten by the receiver at any time.)

>This seems to defeat the purpose of the WideN-N capabilities.

Yes, having "ID" digipeaters obliterating useful PATH data is defeating
the inherrent flexibility in the APRS WIDEn-N network to carry the source
information as to where a packet originated.  Or to keep the path shorter.
But in either case, it preserves the right of the sender to choose.

Thanks for asking!  OK, try this one...
-------------------------------------------------------------------------
Here is what I wrote the last time this came up:

WHY UIFLOOD WAS DESIGNED TO DEFAULT TO NOID:

The setting of ID has always been very controversal because it is NOT how
APRS WIDEn-N digipeating was designed to work.  When new digi owners in
the West were the first to start putting up WIDEn-N digis, they
thought it made sense to turn ID on.  It took years to get them to
understand that that is not the intent, was not the design, and was not
how WideN-N is supposed to work.  The default for the UIDIGI command is
NOID.  That is how it is supposed to work.

Notice, that slowly but surely most regions of the country have now
switched back to NOID.  And now, finally Jeff Brenton changed his
recommendations on the dididahdahdidit web page so that this
confusing information is finally out of the way.

Here is the rationale for three very reasonable USER paths lets say for a
user in the vicinity of his local DIGI1.

A) VIA WIDEn-N          User chose shortest possible path
B) VIA DIGI1,WIDEn-N    includes originating digi for return path info
C) VIA WIDE,WIDEn-N     Same as B, but user is not sure of his digi
D) VIA RELAY,WIDEn-N    Same as C, but user may need to use a home stn.

Now lets look at how these are displayed after going through a WIDEn-N
digi, (lets call it DIGIz) with each of the two settings of ID and NOID:

If ID is set on DIGIz:
A) WIDEn-N       arrives as DIGIz*,WIDEn-X  making all packets longer
B) DIGI1,WIDEn-N arrives as DIGIz*,WIDEn-X  and source info is lost
C) WIDE,WIDEn-N  arrives as DIGIz*,WIDEn-X  and source info is lost
D) RELAY,WIDEn-N arrives as DIGIz*,WIDEn-X  and source info is lost

In other words the ID digi obliterates ALL useful prior path information
and OVERWRITES its call on every packet.  Useless redundant info because
since EVERY packet arrives at most end users by their nearest digi, they
ALREADY know that.  And it PREVENTS any other use of PATH data.

If NOID is set on DIGIz, however:
A) WIDEn-N       arrives as WIDEn-X         preserving shortness
B) DIGI1,WIDEn-N arrives as DIGI1*,WIDEn-X  and source info is kept
C) WIDE,WIDEn-N  arrives as DIGI1*,WIDEn-X  and source info is kept
D) RELAY,WIDEn-N arrives as DIGI1*,WIDEn-X  and source info is kept

Thus, the NOID setting preserves the original intent of the sender.
The ID setting destroys the intent of the sender.

THus having NOID set is the way APRS WIDEn-N digipeating was designed.  It
has many,many advantages:

1) It preserves the intent of the sender
2) It preserves the source digipeater if used
3) It allows everyone to see their OUTGOING path successes.  (It is
the success of your OUTGOING path that determines your ability to
communicate, not your incoming path).

4) It allows tracking any TNC without a GPS or position data to the
nearest digipeater anywhere in the world.  I can build a cigarette pack
sized TNC tracker (with no GPS) that will wake up and send a packet once
an hour for a YEAR on 4 AA batteries.  I can track it anywhere in the
world if digis use NOID.  Because I can always see which digi HEARD IT
first.  Compare that to a tracker that can only last 5 hours on the same
4 AA batteries because of the GPS..

5) It allows reverse pathing for sending back efficient messages. All I
need to see is ONE packet from you and I can see what digi you are near.
Even without any POSITION info from you, I can look at a map, see where
that digi is, and send you back a reply.

6) If a person uses a HOME digi to get out of a canyon or a building in an
"ID" network, no one will ever be able to send him anything, because they
do not know that they must include WIDEn-X,HOME as the return path.
Conversly, In a NOID network, his packets all arrive everywhere as
HOME,WIDEn-X so everyone knows you must reverse the path via WIDEn-X,HOME
to get back to him...

Note, the ONLY advantage of "ID" is so that you can see what your local
digipeater is.  But Geeze.  That is  easy.  And not worth the
destruction of all other path data...  If you want to see what your local
digi is, send a packet via WIDE and it should come back with its callsign
inserted.

Please consider changing your digis to the way WIDEn-N was designed and
intended and all of its advantages...  Thanks!

But I am no longer being emotional about this.  If you have good reason to
have set ID, then at least mark those digis with the "I" overlay so that
users will know how to interpret packets in your area.  Because without
this knowledge, then the following packet can mean two TOTALLY different
things:

      WB4APR,DIGIX,WIDE3-2:Anybody copy?

Did it begin in a NOID network with the first hop of DIGIX?
or did it end in an ID network via  the last  hop of DIGIX?

The difference can be several hundred miles and tell you a LOT about the
packet...

Thanks, for  your consideration...

Bob

----------------------------------------------------------------------

Subject: Re: Symbols/Icons was something else
From: "Pat Karp" <pkarp@conwaycorp.net>
Date: Thu, 23 Jan 2003 10:15:24 -0600
X-Message-Number: 10

>No doubt some stations using certain symbols are pretty much
>worthless/pointless to the rest of the APRS community.

That's a pretty bold statement!

Its all on a matter of opinion.  If I'm running an Igate/WX station.  Which
Icon should I use?  My personal opinion is that the Igate Icon is the most
important.  For the simple reason that it helps to distinguish a path.
However If my interest in weather is greater then my interest in the path WX
icon would be my choice.  How about running an HF gate and a Igate?   Which
do you chose?  Or maybe you setup a station at the hospital and attach a
weather station to it.  Does the WX station over ride the Hospital?

The fact is, is that there are many combinations of tasks that each station
can perform.  One Icon is not going to provide a good identification for all
of them.    That's not to say we should not try to use an Icon that best
soot's the type of station.  But because of the fact you have no idea on
what tasks a station is performing it is impossible to judge the stations
ability by just its Icon.   Tracker and stand alone digies  can use the Icon
as part of the identification.  For any computer operated station the
program should allow for multiple beacon text.   This will allow for proper
identification of stations abilities and purpose.  Then limit the icons
programs can use to prohibit the icons trackers and stand alone digies use.
Then you would come closer to being able to determine the stations purpose.

I guess the final word here is to use the Icon that YOU feel best fits your
station.  And ignore blanket statements such as if your running an Igate use
the blue diamond with and "I".   Until a system is in place that can
properly identify every station then the Icon can only be used as a guess as
to what the ability of a station is.

73
Pat

----------------------------------------------------------------------

Subject: Re: Symbols/Icons
From: "Don" <kyham@alltel.net>
Date: Thu, 23 Jan 2003 11:29:47 -0500
X-Message-Number: 11

I use UI-VIEW and have a STAR-I as an icon but when a WX is sent, the icon
changes to a Blue Circle with WX.   To indicate my system is an Igate,
UI-VIEW indicates this by putting a Blue Square outline box around the icon.
UI-View indicates most Igates this way on the map display.

Don            K9SOA   (EM77EX)
HF-2m-70cm-APRS
www.k9soa.net

----------------------------------------------------------------------



Read previous mail | Read next mail


 16.11.2026 12:49:42lGo back Go up