| |
ZL3AI > APRDIG 07.02.03 11:48l 226 Lines 9751 Bytes #999 (0) @ WW
BID : 843-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 01, 2/5
Path: DB0FHN<DB0RGB<DB0SL<DB0FSG<DB0GAP<DB0GPP<DB0LX<DB0CZ<DB0GE<LX0PAC<
LX0HST<HA3PG<HB9OK<IK6PYS<VK3TE<ZL2BAU<ZL3VML
Sent: 030204/0922Z @:ZL3VML.#80.NZL.OC #:58789 [Chch-NZ] FBB7.00i $:843-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Unproto path ?
From: Bob Bruninga <bruninga@usna.edu>
Date: Sat, 1 Feb 2003 07:49:26 -0500 (EST)
X-Message-Number: 10
>Hey Bob, how about explain to the nice people that putting multiple
>"GATE"s in their path won't help either... esp if they are on VHF...
APRSdos has always Blasted a big RED warning box that obliterates
whatever is on the screen whenever a user has set a path that contains
even one GATE on VHF, to make sure he understands that this is NOT good
practice. It will still send the packet (he may have a need)... but it
sure makes the point that such operation is not normal...
I hope all APRS client software gives such FORCED guidance to users who
attempt to use inherrently damaging paths..
I had hoped to get things like that in the spec too, but could not find
consensus..
Bob
----------------------------------------------------------------------
Subject: Re: SV: RE: javAPRSFilter Features Now on CORE-2
From: "Bill Guthrie" <willy3jax@covad.net>
Date: Sat, 1 Feb 2003 07:56:12 -0500
X-Message-Number: 11
Does this preclude WinAPRS? The address window for sending messages does not
seem to be large enogh to get the entire address entered?
----------------------------------------------------------------------
Subject: Re: SV: RE: javAPRSFilter Features Now on CORE-2
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Sat, 1 Feb 2003 07:13:40 -0600
X-Message-Number: 12
>-----Original Message-----
>From: Bill Guthrie [mailto:willy3jax@covad.net]
>Posted At: Saturday, February 01, 2003 6:58 AM
>Subject: [aprssig] Re: SV: RE: javAPRSFilter Features Now on CORE-2
>
>Does this preclude WinAPRS? The address window for sending
>messages does not seem to be large enogh to get the entire
>address entered?
Not sure what you are saying (I don't have WinAPRS set up here)? Is
WinAPRS somehow limiting the size of the callsign in the To field of a
message? Even if it is, CORE-2 should work when you are connected to
second.aprs.net. Most applications allow up to 9 characters in the To
field of a message (and per the spec, there should be no limit on these
characters other than the 9 character limit).
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
Subject: Intro to AX.25, APRS Authors, APRS and BEACONet.25 unproto [was:
Unproto path ?]
From: "Ev Tupis (W2EV)" <w2ev@arrl.net>
Date: Sat, 01 Feb 2003 08:22:23 -0500
X-Message-Number: 13
** I'm bcc:ing this to another list (besides the APRS list) because I was
** offering help to newcomers there...and this reply is a natural continuation
** of that discussion.
"Well from what Bob stated the answer to my question is yes! Not at all
likely but possible under perfect conditions. hehe You have come closer to
giving me the details I was looking for. Now the maximum of 7 entries does
that mean I can use wide7-7 seven times and AX.25 would attempt to carry me
packet through 49 hops? or is that a total of 7 hops? I understand Bobs
math on this and Have no intentions of playing those odds hehe better odds
in Vegas. Just wondering!"
Hi Pat,
You are asking insightful questions. Again, though, you are asking two
different things. Answers to "AX.25" questions are quite different from
answers to "APRS" questions. Don't forget that APRS is a service, and
AX.25 is a protocol on which APRS is built.
Think of AX.25 as a 4-wheel automobile chassis. Think of APRS as an
ambulance that uses the 4-wheel chassis. Think of an APRS user as the
ambulance driver.
The ambulance manufacturer (APRS) has chosen to build on a 4-wheel
automobile chassis (AX.25). The chassis manufacturer has defined a spec
for their chassis which may include the ability to carry a certian weight
and provide stability up to a certain speed. It is still up to the
ambulance manufacturer to design their product so that it doesn't violate
these specs. Can they? Of course! Who's to blame if they do? Not the
chassis manufacturer. :o)
Take this one step farther. Once the ambulance is sold, it has a further
variable: the person who is behind the wheel. They trust that the
ambulance maufacturer (the APRS software/firmware author) followed the spec
of the chassis manufacturer (the AX.25 protocol spec). However, there is
nothing to say that the driver (the APRS user) must use the ambulance in
the way it was intended...other than that is the tennant on which society
is built...we follow the rules of the road. If they don't, who's to blame?
Not the ambulance manufacturer -or- the chassis manufacturer. :o)
Lastly, is it possible that this same ambulance may be legally driven
differently in different countries? Absolutly. Such is the difference
between APRS and BEACONet.25, by the way. Launching a frame with TRACE7-7
on APRS is a "no-no" by convention. Yes, I've done it...but never for
extended periods of time. I was simply exploring the network. Launching a
frame with HOP7-7 (it's the same function as TRACE7-7, just called
something different) on BEACONet.25 is fine. The two services are
different (even though they both use the same chassis (AX.25) and body
(UI-View software), yet _reside_ on different frequencies.
So...to answer your two questions:
>Now the maximum of 7 entries [in an unproto path,] does that mean I can
>use wide7-7 seven times and AX.25 would attempt to carry me
>packet through 49 hops? or is that a total of 7 hops?
The following answer is based on a frame-of-reference of the AX.25 protocol
(the chassis) only: It is a total of 7-hops in all directions. Think of
the way a pebble dropped in a pond will radiate ripples. The only
difference is that it is necessary to have a digipeater in place, in order
to be digipeated in that particular area. For instance, an unproto of
WIDE3-3 in a "perfect world", with digi's equally spread around would do
this (very oversimplified, but conceptually accurate):
WIDE3 WIDE3 WIDE3
WIDE3-1 WIDE3-1 WIDE3-1
WIDE3-2 WIDE3-2 WIDE3-2
WIDE3 WIDE3-1 WIDE3-2 YOU WIDE3-2 WIDE3-1 WIDE3
WIDE3-2 WIDE3-2 WIDE3-2
WIDE3-1 WIDE3-1 WIDE3-1
WIDE3 WIDE3 WIDE3
>I understand Bobs math on this and Have no intentions of playing those
>odds hehe better odds in Vegas. Just wondering!
Bob's reply came from the frame of reference of APRS (the ambulance and the
conventions of the country called "APRS"), where channel load is a large
consideration when it comes to the progability of a packet getting through.
Of course, the item was brought up on the APRS list, so that is what one
would expect. Such is not the case "in other countries" (such as
BEACONet.25), where the "driving" rules are different.
'hope this helped.
Kind regards,
Ev Tupis, W2EV
--
What's cool in Amateur Radio?
http://www.BEACONet.org or join the on-line community by
sending a blank eMail to: BEACONet-subscribe@yahoogroups.com
----------------------------------------------------------------------
Subject: Re: Unproto path ?
<LYR30523-118307-2003.01.31-21.51.53--kb2scs#optonline.net@lists.tapr.org>
From: kb2scs@optonline.net
Date: Sat, 01 Feb 2003 08:33:38 -0500
X-Message-Number: 14
Hi Pat
From what I have read about AX25 the total digipeaters is 8 not 7.
The rest of this email is about AX25 not APRS.
In AX25 you can have 8 digipeaters in your Unproto path. Also in AX25
the following UI frame is valid.
KB2SCS>APRS,WIDE15-15,WIDE15-15,...WIDE15-15:!aprsdata
You can have 8 WIDE15-15.
In AX25 a digipeat alias cannot have more than 6 characters so since
WIDE15 is not more than 6 characters it is valid. Each digipeat alias can
also have a ssid of no more than 15. So WIDE15-15 is a valid
digipeat alias.
Now in APRS from what I have read we have limited the path to
WIDE7-7.
But that is not an AX25 limitation. Now As everyone else has said
Do Not Do This At Home Or Any Other Place For That Matter.
It is interesting to know why AX25 limites the SSID to 15.
A simplified explanation is the ssid is held in one Byte.
A ssid of 15 would be a Byte containing 0F hex.
Now due to two reserved bits the ssid byte has the dec number 96 added to
it so the 0F hex becomes 6F hex.
Then the SSID Byte is Bit Stuffed. Which means that the 6F Byte is shifted
to the left one bit. Which makes the Byte 7E hex.
This is so that the least significant bit is zero. This least significant
bit is used to signal that the digipeater-ssid is the last Digipeater in
the path. If this bit is zero then there are more digipeaters in the path.
If this bit contains a one then this is the last digipeater.
So lets say that this is the last digipeater. So our Byte that contained 7E
hex has a 1 added to it. The 7E hex now becomes 7F hex.
The most significant bit is called the H bit. It is used to signal that the
digipeater has been digipeated. This bit contains a zero if it has not
been digipeated. It contains a one if it has been digipeated. Which is the
same as adding 128 dec to our Byte that contains 7F hex which now makes the
Byte FF hex. Which is the highest number that a Byte can contain. In other
words all 8 bits of the Byte contain a one.
So the Dec number 15 is the highest number that could be used for a SSID.
A Dec 16 for example would make the Byte contain 100 hex.
Which is more than a Byte can contain.
Let us hope we never witness the "Silence Of The Hams"
73 DE John KB2SCS
Mail To: kb2scs@wa2pnu.#nli.ny.usa.noam
E-Mail: kb2scs@arrl.net
----------------------------------------------------------------------
Read previous mail | Read next mail
| |