| |
ZL3AI > APRDIG 27.07.03 12:52l 259 Lines 9937 Bytes #999 (0) @ WW
BID : 1680-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jul 24, 2/4
Path: DB0FHN<DB0RGB<DB0MRW<OK0PKL<OK0PCC<OK0NAG<OK0PPL<DB0RES<ON0BEL<ZL2BAU<
ZL3VML
Sent: 030726/1338Z @:ZL3VML.#80.NZL.OC #:5038 [Chch-NZ] FBB7.00i $:1680-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Trucks with 7 and more Wides
From: "Dick Stanich" <dick@kb7zva.com>
Date: Thu, 24 Jul 2003 3:10:28
X-Message-Number: 7
>The SEA digi in Seattle, WA is already doing this. As are a couple of other
>local digi_ned digi's. I'm currently trimming anything I see wider than
>wide4-4 to an approriate number. In other words a packet arriving at SEA as
>wide7-7 leaves as wide4-3. No hops used when it arrives. One hop used when
>it leaves. A packet arriving as wide7-2 with 5 hops used is simply dropped
>on the floor and ignored.
>
>Key is to get these brain damaged Kantronics TNC's off of the mountain tops
>and replace them with something that has a little more smarts in it.
Trying to understand why it would be ok for someone in Seattle to produce a
WIDE7-7 that is converted to WIDE4-3, but it's not ok for a distant packet
to arrive as WIDE7-2 and be dumped. If you were going to strictly enforce
APRS in Seattle shouldn't it be the other way around?
Dick, KB7ZVA
APRSWest.net
----------------------------------------------------------------------
Subject: Re: aprs2.net Tier 2 Update
From: "hasan schiers" <schiers@netins.net>
Date: Wed, 23 Jul 2003 09:04:36 -0500
X-Message-Number: 8
Dick said,
"Far more hams are finding that they don't want or even need the full feed.
They decided to use Tier 2 servers because of choice, nothing else."
Presactly, Dick!
I have no idea what the overall distribution of use is regarding full vs.
limited feed, but I can say that nearly everyone in Iowa that I know is
using the filtered ports of a tier2 server. Why?
It isn't largely about bandwidth...although that could play a factor. A
bigger issue is loading down the aprs cleint with 4 or 5 THOUSAND
stations....screen redraws become problematic, and the maps are a garbled
clutter. What we are seeing locally is setting a filter to the range of
interest. I have mine set to 175 miles, but pass NWS warnings and messages
outside the filter. Quite frankly, I don't care what is going on with
stations in Florida, and don't want the aprs client to have to bother with
it.
Now...that could be construed as a pretty narrow interest...however...
If one examines the stacked filtering capabilities of the tier2 servers, one
can isolate areas all over the country that may be of interest and still
keep clutter and bandwidth down. The filtered servers, are to my use of
aprs, the best thing since sliced bread. I get to choose how far, where,
who, what...all with the parms sent to the filtered server.
To me, the primary issue isn't bandwidth, its clutter, and bogging down the
aprs client with useless information. The CORE servers have their main
purpose, but the real functionality is sitting on the filtered tier2
servers. If a person hasn't played with them yet, he doesn't know what he is
missing. The configurability, along with increased reliability is just
amazing.
I guess I would make the opposite assumption that Steve is making...most
aprs users DON'T want the whole data stream...it is pointless. They can't
possibly process that much info, and neither can their aprs client
(efficiently) n.b. With a reasonably fast machine, and a VERY GOOD video
card and driver, UI-View32 can process immense amounts of data, but I don't
find such video performance on most of my machines.. Having access to the
full stream is important, but actually using it may be counterproductive.
Hence, the best of both worlds: a customizable data stream.....err....the
tier2 servers on port 14580!
At least that's the view from here.
....hasan, N0AN
----------------------------------------------------------------------
Subject: Re: Master HF TUNE station--was Bimini
From: Rich Garcia <k4gps@bellsouth.net>
Date: 24 Jul 2003 08:08:54 -0400
X-Message-Number: 9
Ah... many many yarns ago...I forgot that we had actually moved to that
process, my brain must be fried.
Rich K4GPS
Ex: N2CZF A.K.A. TUNE1
P.S. Anyone heard from Peter W7LUS latley ?
----------------------------------------------------------------------
Subject: Re: Trucks with 7 and more Wides
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 24 Jul 2003 09:20:27 -0400 (EDT)
X-Message-Number: 10
On Wed, 23 Jul 2003, Tim Schall wrote:
>The SEA digi in Seattle, WA is already doing this. As are a couple of other
>local digi_ned digi's. I'm currently trimming anything I see wider than
>wide4-4 to an approriate number. In other words a packet arriving at SEA as
>wide7-7 leaves as wide4-3.
But doesnt feed back to the user his error. I wonder if it would be worth
replacing the WIDE7-7 with LID7-7,WIDE4-4? Or JERK7-7,WIDE4-4. But since
we shouldnt criticize on the air, maybe the right one would be
WAS7-7,WIDE4-4...
Bob
----------------------------------------------------------------------
Subject: Re: GPS thoughts
From: "Bud Talbot" <kb9wvg@arrl.net>
Date: Thu, 24 Jul 2003 8:48:7
X-Message-Number: 11
STitching the digitraveler into the pack top pocket sounds good. I found
that the digitraveler fits into the top pocket of my Camelback perfectly.
The lower mesh pocket holds my D7 and since the two are so close the cable
mess is kept to a minimum.
PocketAPRS is a great program. I use it in my truck and also with he D7 if
I want a display, as you mentioned. It interfaces well with the D7 and
provides good flecibility (messaging, etc) that isn't there with the D7
alone.
Yea, the digitraveler's small size has certainly helped me to have a less
complex, more compact pedestrian APRS setup.
73 de Bud
KB9WVG
home.houston.rr.com/kb9wvg
----------------------------------------------------------------------
Subject: Re: Trucks with 7 and more Wides
From: "Daniel H. Brown" <brown@brauhausdc.org>
Date: Thu, 24 Jul 2003 10:15:55 -0400 (EDT)
X-Message-Number: 12
On Thu, 24 Jul 2003, Bob Bruninga wrote:
>Subject: [aprssig] Re: Trucks with 7 and more Wides
>
>On Wed, 23 Jul 2003, Tim Schall wrote:
>
>>The SEA digi in Seattle, WA is already doing this. As are a couple of other
>>local digi_ned digi's. I'm currently trimming anything I see wider than
>>wide4-4 to an approriate number. In other words a packet arriving at SEA as
>>wide7-7 leaves as wide4-3.
>
>But doesnt feed back to the user his error. I wonder if it would be worth
What is the recommended method of feedback?
--
Dan Brown
brown@brauhausdc.org
----------------------------------------------------------------------
Subject: Re: Trucks with 7 and more Wides
From: "Ken Patterson" <kenp@etex.net>
Date: Thu, 24 Jul 2003 14:55:34 -0000
X-Message-Number: 13
Ok, since we now have smart digis, after the digi receives an outlandish
path, the digi could send the user an APRS message with the suggested path.
Obviously, TinyTraks, & the like would not receive the message. Seems like
some feedback is better than none.
Just my $0.02.
de Ken,
N5EQT
----------------------------------------------------------------------
Subject: Re: Trucks with 7 and more Wides
From: "Sean \\The RIMBoy\\" <sean@rimboy.com>
Date: Thu, 24 Jul 2003 09:32:49 -0500 (CDT)
X-Message-Number: 14
On Thu, 24 Jul 2003, Ken Patterson wrote:
>Ok, since we now have smart digis, after the digi receives an outlandish
>path, the digi could send the user an APRS message with the suggested path.
>Obviously, TinyTraks, & the like would not receive the message. Seems like
>some feedback is better than none.
>----- Original Message -----
>From: "Bob Bruninga" <bruninga@usna.edu>
>>But doesnt feed back to the user his error. I wonder if it would be worth
>>replacing the WIDE7-7 with LID7-7,WIDE4-4? Or JERK7-7,WIDE4-4. But since
>>we shouldnt criticize on the air, maybe the right one would be
>>WAS7-7,WIDE4-4...
Well, more often than not they've got an email address. It's not the best
but at least saves them potential public humiliation (of course, everyone
sees their insane path anyway) It's about the only way to easily address
the problem.
I've often pointed people to this page in the past which does a pretty
good job of pointing out some problems.
http://www.aprs.net/vm/digipath.htm
Sean...
--
Believing I had supernatural powers, I slammed into a brick wall.
--Paul Simon
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
KG4NRC http://www.rimboy.com Your source for the crap you know you need.
----------------------------------------------------------------------
Subject: Question on I-gate
From: "Dave Thege" <dthege@conpoint.com>
Date: Thu, 24 Jul 2003 11:28:12 -0500
X-Message-Number: 15
I posted this a couple of days ago and got no response. What prevents a
local digipeater from repeating traffic a home station gates to rf from the
internet.? Our digester does a good job of sending traffic but is weak on
the receive side. We'd like to see traffic and messages from the big cities
to the southeast of us where the majority of APRS activity is in Nebraska
occurs.
Dave N0XBN
----------------------------------------------------------------------
Subject: Re: Trucks with 7 and more Wides
From: "B. Hildebrand" <bhildebrand@earthlink.net>
Date: Thu, 24 Jul 2003 09:30:56 -0700
X-Message-Number: 16
>>The SEA digi in Seattle, WA is already doing this. As are a couple of other
>>local digi_ned digi's. I'm currently trimming anything I see wider than
>>wide4-4 to an approriate number. In other words a packet arriving at SEA as
>>wide7-7 leaves as wide4-3.
>
>But doesnt feed back to the user his error. I wonder if it would be worth
>replacing the WIDE7-7 with LID7-7,WIDE4-4? Or JERK7-7,WIDE4-4. But since
>we shouldnt criticize on the air, maybe the right one would be
>WAS7-7,WIDE4-4...
WAS, is that WIDE APRS SPAM?
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
