| |
ZL3AI > APRDIG 04.05.03 19:04l 253 Lines 9349 Bytes #999 (0) @ WW
BID : 1234-ZL3AI
Read: GUEST
Subj: TAPR Digest, Apr 26, 4/5
Path: DB0FHN<DB0ZWI<DB0CHZ<DB0ERF<DB0FBB<DB0GOS<ON0AR<ON0AR<7M3TJZ<ON0BEL<
VK3TE<ZL2BAU<ZL3VML
Sent: 030429/2243Z @:ZL3VML.#80.NZL.OC #:64838 [Chch-NZ] FBB7.00i $:1234-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Recommendations
From: Rich Osman <Rich@osman.com>
Date: Sat, 26 Apr 2003 13:49:06 -0500
X-Message-Number: 24
I know you are right about this. I've heard this as a management adage
"That which is measured becomes the goal." I've seen it proven time and
again.
Maybe we could even generate the top 5 traffic sources, or those 2 sigma
off mean or something. I seem to remember UIView has something that
will do this. It might be that just publishing the information would
provide enough feedback to influence behavior. The trick is to set it
up to have information value and not be the 'hall of shame.'
----------------------------------------------------------------------
Subject: Relaying traffic between two AGWPE ports
From: Alex <kr1st@amsat.org>
Date: Fri, 25 Apr 2003 01:34:13 -0400
X-Message-Number: 25
Hi there,
Is anyone aware of a piece of software that could connect two KISS ports
in AGWPE without having to use digipeating? I'm talking about something
similar to mkiss and kissattach in Linux. I've looked at DIGIplex and
AGWDigi, but they like to act as digis.
If there's a way to use UI-View (or an add on) to do this then that
would be really great. But as far as I can see it only allows you to set
it up as a digi. I just need something that relays traffic from one AGW
port to the other AGW port and vice versa.
Thanks and 73,
--Alex KR1ST
----------------------------------------------------------------------
Subject: Re: Just trying to understand.
From: John Ackermann N8UR <jra@febo.com>
Date: Sat, 26 Apr 2003 16:06:56 -0400
X-Message-Number: 26
The Digi_NED config at W8APR has been changed. I honestly don't remember
ever setting the path to TRACE6-6, but there it was. It's now running
WIDE2-2.
Just as a comment on Digi-NED stability, the W8APR location is falling into
some disrepair (the whole kit and kaboodle is moving to a new location
later this year, and we're just nursing things along until then), and there
hasn't been any climate control since the weather started turning warm.
There's a leak in the roof, and some other moisture is getting in so the
relative humidity in the little 8x10 building is about 98%. The power
supply fan on the computer burned out long ago, and the thing is running
with the case open. The machine is a 486/100 with 32MB of RAM and an old
Seagate SCSI drive. (When we move later this year, that'll all be replaced
with something more modern like a Pentium 100 :-) )
But despite that harsh environment and ancient hardware, and the fact that
the logs had filled all available space and trashed the filesystem, the
Linux box and Digi_NED had an uptime of 143 days, and Digi_NED was still
digi'ing packets.
73,
John
----------------------------------------------------------------------
Subject: RE: Recommendations; Was: Just trying to understand.
From: "Cap Pennell" <cap@cruzio.com>
Date: Sat, 26 Apr 2003 13:48:20 -0700
X-Message-Number: 27
Rich K4GPS wrote:
<snip>
>ANOTHER problem with dumb trackers is that not every area of the
>country can
>handle WIDEx packets. Many digi's were built before those capabilities and
>are not upgraded due to costs, lack of activity or just lack of knowledge.
>Even if 1 digi owner is willing to upgrade what is the point
>unless all the
>surrounding digi's are willing to do the same ?
FYI, despite some small risk of "over-generalizing" here, I'll say:
Everything West of the Rocky Mountains uses WIDEn-N.
73, Cap KE6AFE
----------------------------------------------------------------------
Subject: Re: Recommendations
From: "Rich Garcia" <k4gps@bellsouth.net>
Date: Sat, 26 Apr 2003 12:52:11 -0400
X-Message-Number: 28
I agree...BUT I can see some areas where a WIDEx will probably never happen.
Now if all WIDEx digi's also answer to WIDE, RELAY and TRACE then I can see
movement towards the final goals. Backward compatability for a few years and
eventually MAYBE it will work.
Again in some areas I find it hard to believe that someone will change out
the TNC or go to Digi-Ned when there are no or few (2-3) stations on the air
and sometimes less trackers than that. If the demand is so low how can you
get a digi owners (sometimes who are no longer on APRS!) to spend $150 on a
KPC-3+ and the effort to change out a cable? I may... but what good is that
if surrounding digi's would not. Hence my "may" instead of would...
Rich
----------------------------------------------------------------------
Subject: Re: Recommendations
From: Rich Garcia <k4gps@bellsouth.net>
Date: 26 Apr 2003 14:53:50 -0400
X-Message-Number: 29
Maybe but it would be good to see what the percentage is out there of
WIDEx digi's and what is not. It is also more than just 1 digi at least
in this state. Other than on the west coast of Florida and Jacksonville
I don't know of any WIDEx
Rich
----------------------------------------------------------------------
Subject: Re: Weather Watches Not Showing Up On APRS
From: Steve Dimse <k4hg@tapr.org>
Date: Sat, 26 Apr 2003 14:16:53 -0400
X-Message-Number: 30
On 4/26/03 at 2:02 PM kg5qd@wxsvr.net (dale huguley) sent:
>Christensen, Eric Harlan wrote:
>
>>Currently we in Eastern (and surrounding) North Carolina are under a Severe
>>T-Storm Watch. I was curious why it didn't show up on APRS like all the
>>other advisories and warnings. Attached are three bulletins that I received
>>that outline the area that the watch covers.
>>
>The first two aren't parsable to anything in APRS
>
>The last one was sent as:
>
>SPCSVR>APRS:;SPCS1528z*262100z3500.00NS07730.00WWSvr TStormWatch #174
>}e0]FgcBS6:W{QFSAA
>
>which can only be seen by xastir and possibly aprs+.
And findU, it appears on the watch page:
http://www.findu.com/cgi-bin/warn-near.cgi
and the text is available:
http://www.findu.com/cgi-bin/warn-text.cgi?id=SPCS1528z
(These will go away at 2100 UTC when this watch expires.)
Steve K4HG
----------------------------------------------------------------------
Subject: Re: Recommendations
From: "Cap Pennell" <cap@cruzio.com>
Date: Sat, 26 Apr 2003 15:50:34 -0700
X-Message-Number: 31
Out in California, the older digis have migrated from "pre WIDEn-N" to
WIDEn-N over time. Seems once the hams with good digi sites find out why
that N overlay is showing up on the neighbor's green digi star, they tend to
want one for themselves. Imagine.
Except for some around Los Angeles area, most of California's WIDEn-N digis
also do RELAY/WIDE/TRACE/TRACEn-N and many do CA (our two-letter State
abbreviation) too. These are mostly Kantronics except for some UIDIGIs
(Cheaper!).
73, Cap KE6AFE
----------------------------------------------------------------------
Subject: Fw: NSTAR 03-A successfully recovered
From: "Mark Conner" <n9xtn@cox.net>
Date: Sat, 26 Apr 2003 17:56:30 -0500
X-Message-Number: 32
A quick summary.......
Right after launch this morning, we had an extremely slow ascent rate. For
the first 20 minutes or more the average was less than 200 ft/min, and at
times was as little as 70 ft/min. Since even a 200 ft/min ascent rate
would have yielded a six hour flight, we thought there was a possibility of
a very long-distance chase. This is why I put the call out to the APRSSIG
at about 1300 UTC.
As the flight progressed, we saw the ascent rate increase to 300 ft/min
once we got above 15,000 ft or so, and to 400+ ft/min above 40,000 ft. This
made our chase a lot shorter than I was expecting right after launch. As
it turned out, the landing was 14 miles north of Lamoni IA, near the town
of Grand River.
The payloads landed in an open cow pasture and no damage was observed. We
learned a number of lessons today, one being (again) that using too little
helium is very often worse than using too much. The other is the
importance of written checklists, as I forgot to activate the still camera
before release.
Bad: Too little helium, backup beacon performed poorly again, forgot to
activate still camera
Good: SSTV system (camcorder and VCH1) performed better than expected,
primary beacon was nearly flawless
I'll have more on the website later on. E-mail of APRS logs or SSTV images
appreciated.
73 de Mark N9XTN
http://members.cox.net/mconner1/nstar.html
----------------------------------------------------------------------
Subject: Re: Recommendations
From: "Spider" <spider@rivcom.net>
Date: Sat, 26 Apr 2003 17:05:41 -0700
X-Message-Number: 33
----- Original Message -----
From: "Cap Pennell" <cap@cruzio.com>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Saturday, April 26, 2003 3:50 PM
Subject: [aprssig] Re: Recommendations
>Except for some around Los Angeles area, most of California's WIDEn-N digis
>also do RELAY/WIDE/TRACE/TRACEn-N and many do CA (our two-letter State
>abbreviation) too. These are mostly Kantronics except for some UIDIGIs
>(Cheaper!).
>73, Cap KE6AFE
There be a few in AZ that do "SAR" and only SAR and do not do anything but
that! You never see them they never make a squeak
.....cause the idea of having to know where the digi's are is not worth a
hill of beans or even a cup of coffee in their applications.
Disclaimer: Other applications may vary!
That's my story, and I am sticking to it!
Jim, OFT
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
