| |
ZL3AI > APRS 29.10.00 15:51l 238 Lines 8030 Bytes #999 (0) @ WW
BID : 34157_ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 25, 3/6
Path: DB0MRW<OK0PKL<OK0PPR<OK0PRG<OK0POK<9A0YRB<HI8GN<KP4IG<WB0TAX<WB7AWL<
WA7V<KB7FRV<VK4WIT<ZS6RO<ZL3VML
Sent: 001027/0850Z @:ZL3VML.#80.NZL.OC #:45144 [Chch-NZ] FBB7.00g25 $:34157_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRS@WW
> > I was going to have my ususal display of APRS running inside the
symposium
> > showing all local activity.. but a blank screen is not gonna look very
> > good...
----------------------------------------------------------------------
Subject: Question about I-Gating
From: Ralph Milnes <milnes1@rcn.com>
Date: Wed, 25 Oct 2000 12:56:30 -0400
X-Message-Number: 14
A question to help me understand IGATE operations and its affect on the
local RF net.
If an IGATE hears a station direct, does the IGATE then put all messages to
that station onto the local RF net?
(Any difference if the station is heard via a relay?)
If so, say some distant station is heard direct by an IGATE, either because
it's using high power or because of propagation anomalies. Does that mean
the local net will start to clog with all messages to that distant station.
Do I have the premise right? If so, that's another argument for the ham
maxim of running *minimum* power. You want just enough power to get to the
nearest WIDE and not distant WIDES. Right? Let your *path* do the work, not
your output power.
Are there other techniques for the IGATES to be set to prevent this? Some
sort of BUDLIST?
The question comes up as a result of discussions about channel loading
problems and getting message and acks to stations that are out of the area.
Ralph, KC2RLM
----------------------------------------------------------------------
Subject: Re: Not-so-smart Digipeating?
From: Roger Barker <roger@peaksys.co.uk>
Date: Wed, 25 Oct 2000 18:09:29 +0100
X-Message-Number: 15
In article <LYR1643-116468-2000.10.25-11.10.32--ROGER#PEAKSYS.CO.UK@list
s.tapr.org>, Ralph Milnes <milnes1@rcn.com> writes
>>Let's assume A can hit two WIDEs, B and C, but can't hit D or E, and D
>>and E can only hear C not B.
>> A
>>
>> B C
>> D
>>
>> E
>A sends a packet via WIDE2-2.
>B happens to digi the packet first, decrementing the path to WIDE2-1
>(meaning one digi left to go).
>C sees that B has digid the original WIDE2-2 packet already so it doesn't
>digi a WIDE2-1,
That is not how a normal WIDEn-N works. If B and C are normal WIDEn-N's,
then they will both digipeat the frame they hear from A. Dupe
suppression stops a digi digipeating the same frame more than once, so
it should prevent B and C from digipeating the "WIDE2-1" frames they
hear from each other.
So the behaviour you describe - C not digipeating the frame heard from A
if it hears B digipeat it first - is based on C possessing a level of
smartness (?) that a normal WIDEn-N digi wouldn't have.
--
Roger Barker, G4IDE - roger@peaksys.co.uk
For UI-View go to - http://www.packetradio.org.uk
For WinPack go to - http://www.peaksys.co.uk
----------------------------------------------------------------------
Subject: Re: Not-so-smart Digipeating
From: Roger Barker <roger@peaksys.co.uk>
Date: Wed, 25 Oct 2000 18:23:05 +0100
X-Message-Number: 16
In article <LYR1643-116469-2000.10.25-11.27.15--ROGER#PEAKSYS.CO.UK@list
s.tapr.org>, Ralph Milnes <milnes1@rcn.com> writes
>
>But I thought the WIDEN-n intelligence allows you specify a wait time
>(UIWAIT), and that time is used to check if another digi already has digid
>the packet (to prevent a dupe)?
>
>So if C has a longer wait time, it won't send a WIDE2-1 because it sees
>that B has already done that. It will, however, send a WIDE2-0 when it
>hears B's WIDE2-1.
UIDWAIT helps to prevent collisions of digipeated packets, it doesn't do
what you describe.
If UIDWAIT is ON, then the same channel access algorithm is used for
digipeated packets as for all other packets (DWAIT, or SLOTTIME /
PERSIST). IF UIDWAIT is OFF then the digipeater will access the channel
immediately it becomes clear.
--
Roger Barker, G4IDE - roger@peaksys.co.uk
For UI-View go to - http://www.packetradio.org.uk
For WinPack go to - http://www.peaksys.co.uk
----------------------------------------------------------------------
Subject: Next Layer of Standards
From: "Sadowski, Allan" <allan.sadowski@ncshp.org>
Date: Wed, 25 Oct 2000 14:15:32 -0400
X-Message-Number: 17
I apologize for the repetative nature of this request... but now that it
seems most have accepted the APRS "standard" as now published.... maybe the
next layer of standardization can begin...
I'd like to throw an "issue" into the debate ring for consideration....
Everyone standardize on GMT/Zulu/CUT/moniker of choice that we all know is
the same but called different things... the name isn't what's important...
but rather that we are all on the same clock.... and that applications that
recieve local data that can't (or won't) be changed by the originator...
(NWS weather I think I've heard is one example) all be changed to the same
clock...
ALOHA
AH6LS
"Safeguarding the rights of others is the most noble and beautiful end of a
human being." Kahlil Gibran.
----------------------------------------------------------------------
Subject: Re: Question about I-Gating
From: Bruno Quesnel <quesnelb@ve2.ele.etsmtl.ca>
Date: Wed, 25 Oct 2000 14:33:04 -0400
X-Message-Number: 18
--------------19857FDF90A9DBD1F6CF6269
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi Ralph,
For those out there, please correct me if I'm wrong on any point...
Ralph Milnes wrote:
> A question to help me understand IGATE operations and its affect on the
> local RF net.
>
> If an IGATE hears a station direct, does the IGATE then put all messages to
> that station onto the local RF net?
> (Any difference if the station is heard via a relay?)
>
Yes it will propagate the all messages that it will hear on the net interface
to that station if any heard
>
> If so, say some distant station is heard direct by an IGATE, either because
> it's using high power or because of propagation anomalies. Does that mean
> the local net will start to clog with all messages to that distant station.
>
Yes it will, that is for the time that the IGATE will hear that station. If
it is due to an anomolie in propagation, it will last for the time of the
propagation. Otherwise, if a station is really powerfull, the IGATE will
deffinatly transmit the information
>
> Do I have the premise right? If so, that's another argument for the ham
> maxim of running *minimum* power. You want just enough power to get to the
> nearest WIDE and not distant WIDES. Right? Let your *path* do the work, not
> your output power.
>
Cant agree more on this
>
> Are there other techniques for the IGATES to be set to prevent this? Some
> sort of BUDLIST?
Not on the RF side. You can limit the users (in fact call sign) to connect on
the net, but until the station expires into the history, no way can be
prevented.
>
> The question comes up as a result of discussions about channel loading
> problems and getting message and acks to stations that are out of the area.
>
I would agree for the channel loading. But for now, I don't know if anything
could be done. Any suggestions ?
>
> Ralph, KC2RLM
>
> ---
> You are currently subscribed to aprssig as: quesnelb@ve2.ele.etsmtl.ca
> To unsubscribe send a blank email to leave-aprssig-18700I@lists.tapr.org
> Questions regarding the SIG go to the SIG administrator: wa1lou@tapr.org
--
Bruno Quesnel bruno.quesnel@mindready.com
VA2BMG quesnelb@ve2.ele.etsmtl.ca
Stagiaire - MindReady Solutions
Solutions Mindready Inc. tel.: 514-636-6886 ext 5171
2196 32ieme Avenue
Lachine (Quebec)H8T 3H7
[html deleted]
----------------------------------------------------------------------
Subject: RE: Next Layer of Standards
From: Bill Diaz <billdiaz@megsinet.net>
Date: Wed, 25 Oct 2000 13:48:19 -0500
X-Message-Number: 19
llan,
If a standard for time is adopted, we should also provide a universal method
to allow users to set their clocks to the correct time. Presently, it is not
Read previous mail | Read next mail
| |