| |
ZL3AI > APRDIG 28.09.03 12:04l 244 Lines 9306 Bytes #999 (0) @ WW
BID : 2003-ZL3AI
Read: GUEST
Subj: TAPR Digest, Sep 25, 3/11
Path: DB0FHN<DB0RGB<DB0MRW<DB0SON<DB0ERF<DB0FBB<DB0IUZ<DB0GOS<DB0ACC<ON0RAT<
ON0DXC<WA7V<WB0TAX<LZ3NP<W4JAX<KD4GBA<ZL2BAU<ZL3VML
Sent: 030927/1144Z @:ZL3VML.#80.NZL.OC #:9136 [Chch-NZ] FBB7.00i $:2003-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: NDGPS
From: Gerry Cerager <gerry.creager@tamu.edu>
Date: Thu, 25 Sep 2003 08:21:25 -0500
X-Message-Number: 14
Doing this with WAAS would require a major system signal spec change.
Doing it with DGPS requires a change within a civil organization.
'Nuff said?
73, gerry
----------------------------------------------------------------------
Subject: what am I missing in this?
From: "JBCrafts" <jbcraft@adelphia.net>
Date: Thu, 25 Sep 2003 10:25:53 -0400
X-Message-Number: 15
Hey Guys, where do I find the callsign of the orginating station in this
line?
7193LV>APT310,N4CRT-1,WIDE2*,qAS,KG4NRC:/165723h3655.10N/08621.10Wk000/000/A
=000620
73 Bob K8YS
----------------------------------------------------------------------
Subject: (no subject)
From: Estelle & Richard <rjhoward@execulink.com>
Date: Thu, 25 Sep 2003 10:39:39 -0400
X-Message-Number: 16
leave -aprssig-25818a
----------------------------------------------------------------------
Subject: RE: what am I missing in this?
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Thu, 25 Sep 2003 10:04:00 -0500
X-Message-Number: 17
This is an unidentified tracker. While tactical callsigns can be used
under FCC rules, proper station identification is still required. This
could be as simple as adding the callsign to the comment field of the
position report. (Sorry to the international community about referring
to FCC rules, but this packet appears to be of USA origin.)
Looking at
http://www.findu.com/cgi-bin/raw.cgi?call=7193LV&start=48&length=24 it
appears that the tracker is set up to periodically add the callsign to the
comment field (KF4QZN) though the id may not be sufficient to meet the
every 10 minutes rule or the last transmission rule.
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
Subject: Packet Stats
From: wes@johnston.net
Date: Thu, 25 Sep 2003 11:55:27 -0400 (EDT)
X-Message-Number: 18
I collected data for 46 hours (begin and end was late evening, so I caught
the drive time traffic coming and going to work). The two columns in the
chart are a)everything heard by my station, b)what would have been heard if
I only listened to the 50 closest stations to me.
Number of Bytes: 4.9M 1.57M
Packets: 55971 18706
Packets / Minute 20.21 6
Avg Packet Length 87 83
Bytes / Minute 1775 568
Utilization: 73% 23%*
The disclaimers...
1. 1200 baud = 120 characters/sec * 60 seconds = 7200 characters / minute
2. 100% utilization is considered to be 2400 characters / second to allow
breathing space for original packet plus 2 digipeats
3. There is no way to record or count damaged or QRMed packets. None of the
figures here were adjusted to accomidate packets lost to collisions.
Wes
----------------------------------------------------------------------
Subject: RE: what am I missing in this?
From: wes@johnston.net
Date: Thu, 25 Sep 2003 12:21:41 -0400 (EDT)
X-Message-Number: 19
You can also get the times packets hit the APRS-IS by adding time=1 to the
CGI query.
http://www.findu.com/cgi-bin/raw.cgi?call=7193LV&start=48&length=24&time=1
I drove some locals to budlist me in a nearby town once(a la packet police)
by running a tactical call on a tracker which ID'ed via 0 hops every 10
minutes. They were far enough away that they didn't see the ID and it
melted down into a pissing contest. In the end, tactical calls are legal
(how many of us remember connecting to a BBS which had your town's name?),
but to keep the peace, I found that using a tactical call on the findu end
works just as well... so I created a domain name "hop" call wes.kd4rdb.com
which directs users to this URL:
http://www.findu.com/cgi-bin/find.cgi?call=kd4rdb-14!Wes' Van
Wes
----------------------------------------------------------------------
Subject: Re: what am I missing in this?
From: "Sean \\The RIMBoy\\" <sean@rimboy.com>
Date: Thu, 25 Sep 2003 09:44:59 -0500 (CDT)
X-Message-Number: 20
On Thu, 25 Sep 2003, JBCrafts wrote:
>Hey Guys, where do I find the callsign of the orginating station in this
>line?
>
>7193LV>APT310,N4CRT-1,WIDE2*,qAS,KG4NRC:/165723h3655.10N/08621.10Wk000/000/A
>=000620
Looking at more than one packet for starters. Likewise, we hashed this
issue out with this tracker several weeks ago.
And someone pointed out that it's unidentified, thought it does send out
a packet on occasion with the callsign in the BTEXT. It would still be a
valid packet though if the station did it's id in CW. In which case
you'd have to be able to hear that station locally.
Let's not let not start this thread again. I'm hoping that people
suggesting DNS was not reliable in another thread were doing so tongue in
cheek.
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: RE: JFindu Has Moved
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 25 Sep 2003 12:37:04 -0400 (EDT)
X-Message-Number: 21
I tell people to GOOGLE jfindu. I just gave a presentation at the IEEE in
Wash DC on Monday and published that technique to find it. I hope
eventually GOOGLE will find the new site. If you know any magic bullets
to make sure that GOOGLE finds JFINDU first (as it did before), then shoot
one of those silver bullets..
Thanks!
Great site
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: Part 2/2 -Re: Take Control - oh let's just go backwards on things,
that's the solution NOT
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 25 Sep 2003 12:29:12 -0400 (EDT)
X-Message-Number: 22
On Wed, 24 Sep 2003, Dennis Hudson wrote:
>I guess I'm confused here. I don't see where WIDEn-N or RELAY, WIDE
>have anything to do with "Smart" or legacy. WIDEn-N was a packet size
>reducing mechanism not a smart or modern alias replacement. I think
>that something is broken on your digis if it transmits dupes for the
>same packet with RELAY, WIDE, and WIDEn-N. Dupe checking should work
>regardless of the actual alias used. Consider fixing your digi, don't
>break your network by removing the base WIDE or RELAY. Am I incorrect
>about this?
You hit the nail on the head. What I am trying to solve with this new
tier of WIDEn-N long haul digis is to give locals another option to help
reduce DX traffic load in their area so that local areas will stop HACKING
away at the fundamentals of APRS to serve the local area (RELAY,WIDE and
WIDE,WIDE routing)...
>If I am then our problems are much larger than I even possibly imagined.
>I can see 4 promenant digis that run UI-DIGI prom for TINY-2 clones with
>my iGate and do not see these type of dupe problems. Our problems stem
>from to many dx stations running excessive paths. WIDEn-N or WIDE or
>TRACEn-N appear have no affect on the problem
Now that statement is a non-sequitur because it is the long haul WIDEn-N
and TRACEn-N packets coming in from hundreds of miles away that "IS" the
problem. Or at least is an "external" problem to a local area that CAN
be fixed locally if needed by turning off WIDEn-N on those digis bringing
all that junk into the area...
>>On Tuesday, Sep 23, 2003, at 10:33, Jeff Thomas - > KD4EVB wrote:
>
>>I'm currently running thru several weeks of off-n-on logs from our rf
>>network around here as I identify where the current problems are and
>>soon will be turning WIDE back off on our digi's here in NKY and doing
>>some filtering of a few problems I found. I can only suggest that
>>sysops do a lot of logging and studying of what the problem really is
>>in their area before just jumping in focusing on one particular path
>>that seems to irritate you and making drastic changes to your local
>>rf/igate archetecture.
Turn off WIDEn-N. Dont turn off WIDE.
In looking at the Washington DC area, in the surrounding 64 mile radius
we have 30+ digipeaters. HALF are callsign-substituting WIDE's only.
And only half are WIDEn-N. Fortunately, these WIDEn-N's are mostly in a
chain up the underpopulated I-81 valley and the underpopulated Eastern
Shore. THus we have only 1 WIDEn-N in the metro area and in looking at
user paths, I was surprised to see that MOST people are using WIDE,WIDE
as their paths. And this seems to work quite well.
So in effect, we are not flooded by too much WIDEn-N traffic, yet on the
long distance interstates, one can use WIDEn-N to go several hops if they
need to without QRM'ing the downtown area.
This is exactly what we are talking about.
de WB4APR@amsat.org, Bob
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
