| |
ZL3AI > APRDIG 11.07.03 09:09l 228 Lines 9527 Bytes #999 (0) @ WW
BID : 1592-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jul 08, 1/2
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<HA3PG<KD4GBA<ZL2BAU<ZL3VML
Sent: 030710/1328Z @:ZL3VML.#80.NZL.OC #:4072 [Chch-NZ] FBB7.00i $:1592-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Tuesday, July 08, 2003.
1. callsign of "IRLP" in APRS
2. Re: NMO mount GPS (not just antenna) ???
3. Re: callsign of "IRLP" in APRS
4. hidden transmitter problems
5. Wxsvr Icons & Claudette
6. Re: hidden transmitter problems
7. Re: hidden transmitter problems
8. Re: hidden transmitter problems
9. Re: hidden transmitter problems
10. Re: hidden transmitter problems
11. Re: hidden transmitter problems
----------------------------------------------------------------------
Subject: callsign of "IRLP" in APRS
From: "Sean \\The RIMBoy\\" <sean@rimboy.com>
Date: Tue, 8 Jul 2003 00:37:39 -0500 (CDT)
X-Message-Number: 1
I don't know if this has happened to anyone else, but we've either had a
band opening or an IRLP node excessively wide. As a result, outside of
the btext it's difficult if not impossible to determine a station's
location (aside from knowing it's node number and home). The question is,
what is the standard protocol? I've noticed some nodes using IRLP-node
number and others using IRLPnodenumber. A good albiet not complete
listing and examples can be found at:
http://db.aprsworld.net/datamart/switch.php?call=IRLP%25&table=position
What is the accepted protocol? In the case of the station tonight, the
station "IRLP" (with callsign in the btext) was in EM60 and I was seeing
it in EM66. The problem is, there's an IRLP station in Canada that seems
to take precedence when you query station IRLP. Were it not for the
callsign in the btext I may not have figured out the nodes home (yes, I
could have researched via node number, but this is APRS). So, what is the
accepted protocol, IRLP-#### or IRLP#### or both ? I'd like to make sure
any users in our area that want to do this are aware of what they need to
do. Likewise, what can be done, if anything, about those stations
beaconing as IRLP? To me it would seem that those in the know would not
need the node number in btext because it's already beaconed as the
callsign or ssid. That leaves room for a callsign and pl tone in the
btext and ideally reducing the packet size (slightly).
thoughts, comments, suggestions?
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: NMO mount GPS (not just antenna) ???
From: Bill Herrmann <bherrman@spro.net>
Date: Mon, 07 Jul 2003 23:44:51 -0600
X-Message-Number: 2
At 03:42 PM 7/7/2003 -0500, tvsjr@sprynet.com wrote:
>Please keep in mind that an NMO mount uses a 3/4" diameter hole, whereas
>this GPS uses a 7/8". If you install one of these and want to put an NMO
>hole mount in later, you'll be sunk.
It'll fit in a just barely oversized 3/4" hole if you really have to. (as
in I filed the edges of a 3/4" hole and threaded it in)
>I would also be a little concerned about the depth of the GPS in the
>headliner (with the Mini-DIN connector, wing nut, etc.)
As Stephen already mentioned it's a right angle connector so it barely adds
any height there. The wing nut doesn't add any over the "bolt" part. I've
got one mounted on my Isuzu Rodeo and had no clearance problems there. I
think the web site mentions the dimensions. It's definitely deeper than an
NMO mount though.
>I know that, especially with the rear air ductwork above the headliner in
>my Expedition, there is very little clearance (at times barely enough for
>NMO mounts).
One thing I did for my installation was go talk to the parts guys at my
dealer. They made a copy out of one of their parts books that showed where
the ribs in the roof were. It didn't have measurements but it was enough to
give me a better visualization of where things were before I pulled the
headliner down.
>A 8-pin Mini-DIN connector in the center of the stud mates with a 14-foot
>cable. The other end of this cable has the forked DB9 RS-232 connector/
Minor note here - I think they've gone to a 10' cable. I know the Canadian
dealer will measure it for you if you ask nicely. (I'm in the US, but
bought it from the Canadian dealer 'cause they answered their phone and
answered my questions.)
Other minor note - The picture on the website showed it as black. They're
really white. They are paintable as long as you stay away from metallic
paint. I had a body shop paint mine when they were painting a vehicle a
similar color.
I haven't had mine as long as Stephen has, but it's been installed just
under a year now and works great. I heartily second his recommendation.
Bill
----------------------------------------------------------------------
Subject: Re: callsign of "IRLP" in APRS
From: Dennis Hudson <n2lbt@n2lbt.com>
Date: Tue, 8 Jul 2003 10:50:17 -0400
X-Message-Number: 3
There is only a few stations using the IRLP* method. In the example you
posted many are old station reports. More stations are using
aprs_status script that shows up as STN* written by Geoff VK2XJG. The
script can be found at
http://redhat.irlp.net/irlp/custom/vk2xjg_scripts/aprs_status/
aprs_status-1.0.tar.gz
Examples of the packets that made it to the APRS-IS can be found at
http://www.findu.com/cgi-bin/find.cgi?STN*
Dennis, N2LBT
----------------------------------------------------------------------
Subject: hidden transmitter problems
From: wes@johnston.net
Date: Tue, 08 Jul 2003 12:39:11 -0400 (EDT)
X-Message-Number: 4
My latest kick is about hidden transmitter problems. I'd be willing to bet
that there are a large percentage of you who never even wonder why every
packet of your doesn't get thru. Then there are the folks who just think
it's poor coverage (ie you were in a hole and the digi didn't hear your
tracker).
I started pulling data from findu, and discovered that over 90 days,
statistically, my tracker had sucessfully made it into the network at
something like 1/10th mile increments on my entire journey to work. Then
the lightbulb came on... we have good coverage and don't need any more
digipeaters. What we have is a case of the digipeaters not hearing my
packets _not_ because of my location, but rather because of NETWORK
CONGESTION.
Just this morning I tracked kc4pl-9 on his trip to work (he travels the
same route I do, just travels a greater distance). I first pulled a 90day
graphic of all of his positions.
http://imscorporation.com/kd4rdb/hidden_tx_control.png and called this the
"control group". This shows a long term average if you will, of where
netowrk coverage exists. In other words, where it is POSSIBLE to hit a
digipeater. By using only his station in this control group, I elliminate
variations due to power and antenna differences.
Next, I pulled the last 4 hours of data representing one day's travel to
work and annotated it with times in UTC as reported by findu.
http://imscorporation.com/kd4rdb/hidden_tx_case1.gif . Green dots
represent findu's logged positions, red dots are missing position reports.
In the case1.gif, I have made some guesses as to where he would have been
if his posit reports had actually gotten into the network. If you flip
back and forth between the two images quickly, you will see that there is
coverage in those places. He didn't get in to the network because a digi
didn't hear him.
I counted 18 good position hits and 13 missed positions, a 58% sucess rate.
Why is this such a big deal? APRS uses unconnected packets. There are no
ACKs and no RETRIES. You've got one chance to get your position in. If we
give up and use connected mode, we just doubled our netowrk overhead and
that is not acceptable.
More on this later....
Wes
----------------------------------------------------------------------
Subject: Wxsvr Icons & Claudette
From: dale huguley <kg5qd@wxsvr.net>
Date: Tue, 08 Jul 2003 21:06:53 +0000
X-Message-Number: 5
Hi All-
I changed the way the Hazardous Weather outlook is done by Wxsvr. Now
if the Spotter information is parsed to "No Activation" , the Icon is a
wx overlay of "O" (outlook). If the Spotter info is something
different- then the icon is the Skywarn logo. Easy way to see if you
need to put your ears up and your head down. I noticed that UI-view
doesn't have the Skywarn Logo as an icon- so there is a replacement
symbols2.bmp available at :
http://wxsvr.net
right at the top. Save your old one just in case.
Flood Messages now carry the Flood icon rather than the "G" overlay.
Tropical Storm Claudette has formed in the Carribean. Remember this is
the first year of 120 hour predictions- the 120 and 96 hour positions
are highly suspect- take them as guidence only.
73 de kg5qd Dale
----------------------------------------------------------------------
Subject: Re: hidden transmitter problems
From: "Richard Amirault" <ramirault@erols.com>
Date: Tue, 8 Jul 2003 18:17:47 -0400
X-Message-Number: 6
I don't understand .. what has all this to do with "hidden transmitter
problems"?
And, I also don't understand your question "Why is this such a big deal?"
... Why is *what* such a big deal? You gave some examples .. but didn't
make a "big deal" out of anything.
Richard Amirault N1JDU Boston,
MA, USA
www.erols.com/ramirault "Go Fly A Kite"
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
