| |
ZL3AI > APRDIG 07.09.03 10:08l 270 Lines 9556 Bytes #999 (0) @ WW
BID : 1871-ZL3AI
Read: GUEST
Subj: TAPR Digest, Sep 04, 1/3
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<ZL2BAU<ZL3VML
Sent: 030906/1335Z @:ZL3VML.#80.NZL.OC #:7868 [Chch-NZ] FBB7.00i $:1871-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Thursday, September 04, 2003.
1. RE: Echo Link Lookups?
2. Re: PCsat telemetry
3. Re: PCsat telemetry
4. RE: I think I got it!
5. Help with Time Stamp
6. APRS Map
7. Re: APRS Map
8. Re: APRS Map
9. Re: APRS Map
10. Fw: Re: APRS Map
11. Re: APRS Map
12. aprsfl.net appearing as "port-scanner"
13. RE: aprsfl.net appearing as "port-scanner"
14. RE: aprsfl.net appearing as "port-scanner"
15. Re: APRS Map
16. Re: aprsfl.net appearing as "port-scanner"
17. Re: Help with Time Stamp
----------------------------------------------------------------------
Subject: RE: Echo Link Lookups?
From: "Bob D." <n2iph@comcast.net>
Date: Thu, 4 Sep 2003 05:49:42 -0400
X-Message-Number: 1
Try the EchoLink web site, where you can view a list of currently
connected station.
Other than that you could try the k4tlh.net web site or email
kc4toc@earthlink
----------------------------------------------------------------------
Subject: Re: PCsat telemetry
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 4 Sep 2003 08:41:59 -0400 (EDT)
X-Message-Number: 2
On Wed, 3 Sep 2003 wa6ylb@theworks.com wrote:
>>http://www.ew.usna.edu/~bruninga/pcsat/3s031205.txt
>>
>>The file is just a text capture of the entire pass...
>
>Hmm. Looks like PASSALL is on your tnc. Right?
>
>[12:15:45] PCSAT-12>BEACON,SGATE:T#063,081,069,081,098,213,00110111,0110,1
>[12:15:46] W3ADO-1>BEAEON,SGATE/1:T#070,08<,072,08:,101,213,00110111,010141
Yep. I hate to miss anything...
bob
de WB4APR@amsat.org, Bob
PCsat WEB page http://www.ew.usna.edu/~bruninga/pcsat.html
ISS-APRS FAQ: http://www.ew.usna.edu/~bruninga/iss-faq.html
CUBESAT Designs http://www.ew.usna.edu/~bruninga/cubesat.html
APRS LIVE pages http://www.ew.usna.edu/~bruninga/aprs.html
APRS SATELLITES http://www.ew.usna.edu/~bruninga/astars.html
MIM/Mic-E/Mic-Lite http://ssdl.stanford.edu/mims/
----------------------------------------------------------------------
Subject: Re: PCsat telemetry
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 4 Sep 2003 08:43:02 -0400 (EDT)
X-Message-Number: 3
On Thu, 4 Sep 2003, Andrew VK4TEC wrote:
>How is the next sat coming along Bob ?
Its done. Its now in Thermal Vac testing. But launch is delayed until
shulttle launches...>
de WB4APR@amsat.org, Bob
PCSAT2 WEB page http://www.ew.usna.edu/~bruninga/pcsat2.html
----------------------------------------------------------------------
Subject: RE: I think I got it!
From: "Phil Pacier, AD6NH" <ad6nh@arrl.net>
Date: Thu, 4 Sep 2003 11:42:56
X-Message-Number: 4
Just as a side note abput port 1314 here - it is probably the best choice
for unattended IGates. If you are not running a program that supports
mapping (like aprsD) or if you are not interested in looking at icons on
your IGate interface (i.e. it's in a closet or a hilltop somewhere) then I
would recommend connecting to port 1314. It is the best choice for
unattended IGates as far as bandwidth and usefulness is concerned.
73
Phillip Pacier - AD6NH
http://www.aprs2.net
----------------------------------------------------------------------
Subject: Help with Time Stamp
From: "Michael J. Wolthuis" <wolthui3@msu.edu>
Date: Thu, 4 Sep 2003 12:44:46 -0400
X-Message-Number: 5
Everyone,
For some reason my time in APRS+SA is off by 4 hours. My system time is
right, but the APRS+ time shows ahead 4 hours. Is there a setting I
have to set, or a separate time? I need to know exactly when Weather
stations are reporting and having it off by 4 hours makes that
difficult.
Thanks,
Mike
Kb8zgl
----------------------------------------------------------------------
Subject: APRS Map
From: "Richard Hughes" <rhughes@cableone.net>
Date: Thu, 4 Sep 2003 12:56:9
X-Message-Number: 6
I am trying to understand the APRS routing at least in my state of Arizona.
Where can I see (on a map) the active digipeaters in Arizona? I looked at
one map of digipeaters, and it showed only one digipeater in the entire
state. I would like to be able to do this via Internet rather than by
radio.
Also, where are the Igates located in the U.S.?
----------------------------------------------------------------------
Subject: Re: APRS Map
From: Robbie <mwrobertson@comcast.net>
Date: Thu, 04 Sep 2003 15:36:51 -0500
X-Message-Number: 7
Hi Richard,
First of all, I am going to assume you are running winaprs, a late
edition.. Even after 2.5.1 I think will work.. Connect to the APRS-IS, a
full feed port.. After an hour or so, giving most i-gates a chance to be
heard on the APRS-IS feed.. Show only the state of Arizona, then hit the
letter "i" on the keyboard.. All I-Gates should have red coverage
circles around them. Works for me, :-)
Robbie, wa9inf
----------------------------------------------------------------------
Subject: Re: APRS Map
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 4 Sep 2003 17:36:49 -0400 (EDT)
X-Message-Number: 8
On Thu, 4 Sep 2003, Richard Hughes wrote:
>Where can I see (on a map) the active digipeaters in Arizona? I looked at
>one map of digipeaters, and it showed only one digipeater in the entire
>state.
I have heard that recently a number of unique changes were made to some
digis in AZ to disable some of the standard APRS functionality.
1) disabled TRACE on W7DXJ-1 which 'sees' about a 250 mile radius.
2) Digi BEACON posits were changed from every 10 minutes to every 29 mins
3) WIDE was removed from UIDIGI
Thus further fractionalizing APRS into disjoint inconsistent areas which
defeats the whole purpose of a national network. These changes were made
in good faith to "fix" some path problems, but the solution in my opinion
should be to fix the path problems at the source, not screw-up the
network...
My recommendations to properly solve each of these problems would be:
1) Get users and digis that are using TRACE too much, to cut back
2) Digis should only ID local evy 10m. Evy 30 mins via a longer path.
3) WIDE is the universal APRS path. WHatever is the problem, fix it
another way.
Just an opinion.
Bob, WB4APR
----------------------------------------------------------------------
Subject: Re: APRS Map
From: "Sean \\The RIMBoy\\" <sean@rimboy.com>
Date: Thu, 4 Sep 2003 17:15:51 -0500 (CDT)
X-Message-Number: 9
On Thu, 4 Sep 2003, Bob Bruninga wrote:
>1) disabled TRACE on W7DXJ-1 which 'sees' about a 250 mile radius.
>2) Digi BEACON posits were changed from every 10 minutes to every 29 mins
>3) WIDE was removed from UIDIGI
>
>My recommendations to properly solve each of these problems would be:
>
>1) Get users and digis that are using TRACE too much, to cut back
>2) Digis should only ID local evy 10m. Evy 30 mins via a longer path.
>3) WIDE is the universal APRS path. WHatever is the problem, fix it
> another way.
Bob,
1. It was announced at Dayton this year that Trace was depreciated in
use. It was mentioned at the forum at Hara and IIRC later at the pizza
bash. I don't recall who made that statement, but as most if not all of
us understood it, Trace was being phased out. I believe TRACE is still
used on digi's KQ4TV maintains in order to see where packets are getting
during a band opening. These beacons with TRACE occur infrequently (once
maybe twice an hour, Bruce knows best). Best I can say is that there was
not much if any dissention when these statements were made. I don't
recall anyone at these places being unhappy with these statements.
2. I won't disagree with this, however I think most of our digi's are
not doing it that frequent in part because they do callsign replacement
and in part to minimize bandwidth whereever possible. It's not like those
digi's will move in an hour.
3. Again, I believe this was announced at Dayton, but I was (and I
believe others) under the understanding that we should be or have moved to
WIDEn-n support only. We've suggested to all of our users to go to a
RELAY,WIDE2-2 path for mobiles and WIDEn-n of some sort for a fixed
station.
I wish I remember who made these statements (anyone else care to comment?)
but the Nashville area (and others I believe) been pushing ourselves to
this point. We're not fully compliant (then again, we don't maintain
those digi's) but we're moving towards this. We were under the impression
that others were too.
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: Fw: Re: APRS Map
From: "VE4HGD" <ve4hgd@mts.net>
Date: Thu, 4 Sep 2003 19:34:47 -0500
X-Message-Number: 10
>3. Again, I believe this was announced at Dayton, but I was (and I
>believe others) under the understanding that we should be or have moved to
>WIDEn-n support only. We've suggested to all of our users to go to a
>RELAY,WIDE2-2 path for mobiles and WIDEn-n of some sort for a fixed
>station.
This would be wonderful if the world were perfect and we all used Kan TNCs
of current vintage. But in the real world there are many older and non cam
TNCs being used. Putting a restriction like that on use of A PRS will just
kill it in some areas. Her we have long distances to cove and limited funds
and uses you use what you got and that means TNC that do not support the
wideX-X
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
