| |
ZL3AI > APRDIG 19.02.04 14:14l 268 Lines 9596 Bytes #999 (0) @ WW
BID : 2866-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 17, 5/7
Path: DB0FHN<DB0FOR<DB0MRW<DB0ERF<DB0FBB<DB0BI<DB0NOS<DB0EA<DB0RES<ON0AR<
LZ3NP<VK6ISP<ZL2TZE<ZL3VML
Sent: 040219/1151Z @:ZL3VML.#80.NZL.OC #:19406 [Chch-NZ] FBB7.00i $:2866-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: TCP/IP operation - NOT
From: "Phil Pacier, AD6NH" <ad6nh@arrl.net>
Date: Tue, 17 Feb 2004 12:33:11
X-Message-Number: 35
On 02/17/04, "Glenn Wiebe <gswiebe@mb.sympatico.ca>" wrote:
>Hi all:
>
>I've been using WinAprs (registered, now 2.7.2) for many years and the
>only ports as listed under Settings>TCP/IP Connections I've ever been
>able to open are: 1) Secondary APRS Net Server 2) second.aprs.net 10151
>APRServe - backup: (I suspect they are the same) 3) 204.118.115.12 23
>west usa:. The first two rapidly fill the screen with world wide
>stations and the last one does nothing. All the rest - and there are
>dozens including a local feed that others can open - come up with: TCP
>Open Failed. Yes I am on line. Any suggestions?
>
>73 de Glenn...VE4GN
As with the many other things in WinAPRS that are not updated, this is
another area that needs a personal tweak (referring to the default
aprserve.txt file). What you are connecting to is the core worldwide feed.
Basically, you are seeing every packet that is on the APRS-IS at a time.
It can get pretty crazy, and will eat memory like potato chips. There are
two quick suggestions. First, add ontario.aprs2.net:14579 to the list.
This will give you APRS stations in all of Canada, with the ability to send
and receive messages worldwide. The other thing you might want to try is
looking for another existing aprserve.txt file. Try
http://www.ahubswe.net/APRServe.txt and then edit that file to suit your
needs.
Enjoy! 73
Phillip Pacier - AD6NH
http://www.aprsca.net
----------------------------------------------------------------------
Subject: aprsworld Maps
From: "Phil Pacier, AD6NH" <ad6nh@arrl.net>
Date: Tue, 17 Feb 2004 12:38:5
X-Message-Number: 36
Hi James, great job on the map database! I wanted to make one suggestion;
I'm not sure if you can control this or not, but it is regarding the
labeling of the Interstate highways on the maps. Currently, the maps are
showing the letter "I" in front of the interstate number. Perhaps I'm the
only one, but I find this confusing when I look at the maps. Particularly
for those of us in the southwest, where most of the single-digit or
double-digit beginning with "1" interstates are located. For example, on
many maps that I call up for this area, both Interstate 5 and Interstate 15
are visible. On quick glance, though, I see I5 and I15 and it looks like
Interstate 15 and 115. The insterate shield is unique enough that the "I"
indicator is ambiguous and, at least to me, confusing. Is there a way
and/or a desire to remove the "I" label from the Interstates?
Thanks! I appreciate the effort here. We at the Tier 2 networks are
working on a mapping database as well. I look forward to sharing ideas and
goofs!
73
Phillip Pacier - AD6NH
http://www.aprsca.net
http://www.aprs2.net
----------------------------------------------------------------------
Subject: Re: APRS enabled balloon on 144.39 over Colorado
From: "Scott Miller" <scott@opentrac.org>
Date: Tue, 17 Feb 2004 10:39:54 -0800
X-Message-Number: 37
>And with the OpenTracker, you can write your own firmware as well, plus you
You also have the option of asking nicely for the required firmware mods,
though I also accept bribes. Dr. Pepper or Jolt Cola, for instance.
I was hoping to be able to implement a very simple scripting language that'd
let you do stuff like the flying/landed/battery save mode selection, but I
really don't think I'll be able to squeeze it in this version.
Seeing as I've got trackers slated for a couple of upcoming balloon
launches, I think I will at least implement the path max altitude function,
though.
Scott
N1VG
----------------------------------------------------------------------
Subject: RE: Mythbusters
=?ISO-8859-1?B?oENlbGwgcGhvbmVzIFZzIEdhcyBTdGF0aW9ucw==?=
From: Kf6myv@aol.com
Date: Tue, 17 Feb 2004 13:51:11 -0500
X-Message-Number: 38
One thing the didn't do though was have the phone near the gas
transmitting. All they did was make it ring. Wouldn't there be more power
coming off of it if it were picked up? I still don't think it would cause a
fire though.
----------------------------------------------------------------------
Subject:
=?iso-8859-1?Q?RE=3A_=5Baprssig=5D_RE=3A_Mythbusters_=A0Cell_p?= =?iso-8859-1?Qo
?hnes_Vs_Gas_Stations?=
From: "Christensen, Eric" <CHRISTENSENE@MAIL.ECU.EDU>
Date: Tue, 17 Feb 2004 13:55:25 -0500
X-Message-Number: 39
I think what they are talking about is its' intrinsic (sp?) ability. The
radios and pagers that we use on Hazardous Material scenes MUST be
intrinsically safe meaning they will not spark when operated (and other
things, too). When a cellphone rings there is the possibility of an
internal spark that could ignite the gasoline fumes (which is the ONLY
component of gasoline that will burn) and could cause an explosion.
73s,
Eric KF4OTN
ARRL Member
AMSAT Member: 35360
TAPR Member: 8869
Support your Hobby! Join a club.
All contact logs are uploaded to the ARRL LoTW and eQSL.
----------------------------------------------------------------------
Subject: Re: aprsworld Maps
From: Steve Dimse <k4hg@tapr.org>
Date: Tue, 17 Feb 2004 14:04:37 -0500
X-Message-Number: 40
On 2/17/04 at 12:38 PM Phil Pacier, AD6NH <ad6nh@arrl.net> sent:
>Thanks! I appreciate the effort here. We at the Tier 2 networks are
>working on a mapping database as well. I look forward to sharing ideas and
>goofs!
I'm certainly interested in hearing details! Please share!
Steve K4HG
----------------------------------------------------------------------
Subject: ISS <> PCSAT Accesses
From: "Scott Miller" <scott@opentrac.org>
Date: Tue, 17 Feb 2004 11:19:49 -0800
X-Message-Number: 41
Well, I can't remember how to constrain access opportunities for PCsat to
sunlight only, but here's the raw list of times over the next month when ISS
and PCsat are in view of each other. Average duration is 12.7 minutes, max
duration is 24.5 minutes on 29 March. Looks like the contacts get longer
toward the end of the period.
You'll need to correlate this with your local ISS and PCsat predictions.
Don't forget to limit PCsat operation to daylight only, even for indirect
access!
http://n1vg.net/iss-to-pcsat.txt
Scott
N1VG
----------------------------------------------------------------------
Subject:
=?iso-8859-1?Q?Re:_=5Baprssig=5D_RE:_=5Baprssig=5D_RE:_Mythbusters_?= =?iso-8851
9-?Q?=A0Cell_phones_Vs_Gas_Stations?=
From: "Scott Miller" <scott@opentrac.org>
Date: Tue, 17 Feb 2004 11:26:55 -0800
X-Message-Number: 42
>things, too). When a cellphone rings there is the possibility of an
>internal spark that could ignite the gasoline fumes (which is the ONLY
>component of gasoline that will burn) and could cause an explosion.
Unless you've got a big, old-fashioned mechanical ringer on your cellphone I
don't think it's the ringer that's a problem. Maybe the vibrator motor
might generate some sparks.
In any case, it's not anywhere near as dangerous as static electricity.
Apparently it's mostly women that get in trouble with this, because they
tend to get back in the car and sit down. Getting out is what usually
builds up a charge. I always grab the door frame just to avoid zapping
myself.
And never, ever fill portable containers without grounding them first. They
had an incident at Lackland Air Force Base not too long ago where someone
blew up their pickup truck by neglecting to take the containers out of the
bed.
They really need to start teaching some risk management concepts to high
school students. Have them figure out the probability of an accident in
transporting one of those indestructible casks of nuclear waste they're
always protesting, compared to the probability of an accident involving one
of the thousands of gasoline tankers driving through city streets every day.
Then compare that to the probability that they'll be injured while driving
due to their own carelessness or stupidity.
People spend too much time worrying about the wrong stuff.
Scott
N1VG
----------------------------------------------------------------------
Subject: KC*UCH-11
From: Ronald Armstrong <rsarmstrong@videotron.ca>
Date: Tue, 17 Feb 2004 14:33:24 -0500
X-Message-Number: 43
Anyone know the LAT/LONG off the KC8HCH-11 where it landed
Ronald
----------------------------------------------------------------------
Subject: RE: KC*UCH-11
From: "Rochte, Robert" <rrochte@gpacademy.org>
Date: Tue, 17 Feb 2004 14:43:24 -0500
X-Message-Number: 44
>Anyone know the LAT/LONG off the KC8HCH-11 where it landed
You can see it on Findu right now - the payload is still transmitting from
the ground:
http://www.findu.com/cgi-bin/find.cgi?call=kc8uch-11
If you're in the area and plan to recover, please let me know!
Regards,
Robert
KC8UCH
----------------------------------------------------------------------
Subject: RE: KC*UCH-11
From: Steve Dimse <k4hg@tapr.org>
Date: Tue, 17 Feb 2004 15:00:33 -0500
X-Message-Number: 45
On 2/17/04 at 2:43 PM Rochte, Robert <rrochte@gpacademy.org> sent:
>You can see it on Findu right now - the payload is still transmitting from
>the ground:
>
>http://www.findu.com/cgi-bin/find.cgi?call=kc8uch-11
From there click on the aerial photo link, and pretty much see which tree
it is in!
http://www.acme.com/mapper/?lat=42.88050&long=-71.97500&scale=10&them=
e=Image&
width=3&height=2&dot=Yes
Sure wish I lived near there, this would be fun!
Steve K4HG
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
