| |
ZL3AI > APRS 29.10.00 16:00l 204 Lines 7049 Bytes #999 (0) @ WW
BID : 34189_ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 26, 9/9
Path: DB0MRW<OK0PKL<OK0PPR<OK0PPL<OK0POK<9A0YRB<HI8GN<KP4IG<7M3TJZ<IK1ZNW<
VE1DRG<WA7V<KB7FRV<VK4WIT<ZS6RO<ZL3VML
Sent: 001027/1210Z @:ZL3VML.#80.NZL.OC #:45160 [Chch-NZ] FBB7.00g25 $:34189_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRS@WW
in appropriately shielded boxes, away from buildings that can store, and
re-radiate heat. Otherwise their readings are somewhat skewed. The should
NOT be mounted at other heights, as this gets you into other layers of air.
(He had a more complicated explanation)
Wind sensors should be mounted as high as practical, to get above the
"urban clutter and trees".
Wind direction sensor north should be geographic north, NOT magnetic.
In summary, he thinks that the system has great promise, and could be a
"killer app" for storm chasing, skywarn, and emergency management, but in
it's current state, is almost useless for severe weather events of short
duration. (It's not JUST tornadoes)
I can't promise for anyone else, but I'd gladly pay another registration
fee for WAPRS-II if that's what it takes to get the new features that I
mentioned, but I do think that the features that you have in WAPRS as it
is, ought to work properly. You do owe us that, and quite honestly, you owe
it to yourselves.
----------------------------------------------------------------------
Subject: Re: Hyper-Jumps strike again in southern California ......
From: "Brent Hildebrand" <bhildebrand@earthlink.net>
Date: Thu, 26 Oct 2000 20:30:39 -0700
X-Message-Number: 32
I tried to do some sluthing to determine what the cause of these jumps =
were. Byon suggested that WinAPRS v2.4.6 was the/a cause. So this is =
what I did. I wrote a program to capture data from www.aprs.net port =
14502, which is running APRSD. Port 14502 tells where various packets =
came from. I put in my program a parser to capture packets, and then =
look for packets from Southern California Mic-E type stations ( I had a =
list of callsigns to look for). I then parsed the Mic-E packets, and =
the reformatted packets. At about 6:30 PM, bad packets began to =
appear. My simple "police" program output looked something like this:
KG6CNL-2
second.aprs.net:IGATE <---> KG6CNL-2>S3TPPU,N6EX-4*,WIDE:'-Vl!ij/]"4O}
33.6675 =AF117.9831667 0 177 184 j/'TM-D700:IN SERVICE: SPD=3D0 =
TRK=3D177 ALT=3D184
KG6CNL-2
second.aprs.net:IGATE <---> =
KG6CNL-2>APK101,N6EX-4*,WIDE:@270407z3340.05N/01758.98Wj177/000/Mic-E/M2/=
In Service>
33.6675 =AF17.983 177 0 /Mic-E/M2/In Service>
The bad packets were coming from a station connected to second.aprs.net. =
It does not mean that second.aprs.net is the originating source of =
these packets.
Note that the Longitude from the Mic-E packet itself had a Longitude of =
117.9832W. The reformulated packet had a Longitude of 17.983W. =
Obviously wrong, and a cause for "jumps". Note that is the reformulated =
packet comes after the original Mic-E packet, then FindU will show the =
most recent position which would be wrong. Noting that the Unproto TO =
field was APK101, characteristic of WinAPRS I believe when it is doing =
the reformulating, I logged on to APRServe at second.aprs.net port 14501 =
to see who was logged into it. I scanned the callsigns of connected =
stations, with particular interest in WinAPRS v2.4.6 and noted that one =
station in SoCal had logged on at approximately the right time as when I =
began to see the bad packets. I have tried to contact that station, but =
he has not returned my email/aprs messages yet.=20
Byon indicated that this is a known problem with WinAPRS v2.4.6. =
Perhaps Keith can comment? There appear to be a large number of users =
of v246. Perhaps it is time to update copies of WinAPRS to 247 ?? =20
Note that Greg, WB6ZSU and I did do some testing with MacAPRS, v3.4.6 =
(or was it 5?) and it appears to not cause severe jumps in Position, but =
did show to be 0.01 minute low in Lat and Long conversion when =
converting Mic-E to and APRS packet, almost insignificant in affect on =
position. It did pass Mic-E data correctly. =20
My final comment is, do we really need to convert Mic-E packets??? I =
say, it is time to eliminate the conversion of Mic-E when IGating Mic-E =
packet to the Internet.
Brent KH2Z
----- Original Message -----=20
From: <WA8LMF1@aol.com>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Thursday, October 26, 2000 1:24 PM
Subject: [aprssig] Hyper-Jumps strike again in southern California =
.......
> >From Findu as of 1:21 PDT Friday
>=20
> (About 500 miles west of the Portuguese coast in the Atlantic)
>=20
> Call msg wx lat lon distance Last Position =20
> <A HREF=3D"http://64.34.101.121/cgi-bin/find.cgi?WA8LMF">WA8LMF</A> =
<A=20
> HREF=3D"http://64.34.101.121/cgi-bin/msg.cgi?WA8LMF">**</A> . =
34.04800 =20
> -18.16967 0.0 00:00:12:15 =20
> <A =
HREF=3D"http://64.34.101.121/cgi-bin/find.cgi?WB6DAO-5">WB6DAO-5</A> . =
=20
> 34.05833 -18.08167 5.3 00:00:10:36 =20
----------------------------------------------------------------------
Subject: Boat Trip
From: "Charles H. Rahe, II" <crahe@lancnews.infi.net>
Date: Thu, 26 Oct 2000 23:45:02 -0400
X-Message-Number: 33
This is a multi-part message in MIME format.
--------------16AC138A5F9335E0FDAD9EB8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
For those interested. I will be departing Sun 10/29 to help take a boat
to Ft Pierce, FL. Hope to have a D700 operating with APRS under the call
AI3L-14. Tentative itinerary is:
Sunday 10/29 Depart Baltimore, MD, brief stop in Annapolis, than on to
the Rappannock River in VA.
Mon. 10/30 thru Norfolk, VA & down Intracoastal Waterway to Manteo, NC
Tue. 10/31 continue down ICW to Beaufort or Swansboro, NC
Wed. 11/1 Out into Atlantic & down to Charleston, SC.
Thru 11/2 to St. Augustine, FL
Fri. 11/3 to Ft Pierce, FL
Of course weather may well change this schedule and planned routes.
Probably won't be able to respond to messages, but will try to confirm
all contacts after the trip, if not during.
--------------16AC138A5F9335E0FDAD9EB8
Content-Type: text/x-vcard; charset=us-ascii;
name="crahe.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Charles H. Rahe, II
Content-Disposition: attachment;
filename="crahe.vcf"
begin:vcard
n:Rahe, II;Charles H.
x-mozilla-html:FALSE
url:http://www.findu.com/cgi-bin/track1.cgi?ai3l-8
org:M/V Lady J (AI3L-8)
adr:;;;Middle River, MD;;;
version:2.1
email;internet:crahe@lancnews.infi.net
fn:Charlie Rahe, AI3L
end:vcard
--------------16AC138A5F9335E0FDAD9EB8--
----------------------------------------------------------------------
Subject: Digi Down
From: "Darrell Sutton" <dsutton2@home.com>
Date: Fri, 27 Oct 2000 00:37:49 -0400
X-Message-Number: 34
This is a multi-part message in MIME format.
------=_NextPart_000_001A_01C03FAE.222FEF00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The N4EVA-10 digi is down in Toano VA. Not sure yet what has happened =
but we are awaiting contact from the Site Tech. Hope to get back up =
asap.
Darrell kf4hjw
Chairman Eastern VA APRS Group
[html deleted]
---
END OF DIGEST
Read previous mail | Read next mail
| |