| |
ZL3AI > APRDIG 26.09.03 12:18l 278 Lines 10099 Bytes #999 (0) @ WW
BID : 1982-ZL3AI
Read: GUEST
Subj: TAPR Digest, Sep 23, 2/7
Path: DB0FHN<DB0RGB<DB0FSG<DB0PV<DB0MRW<OK0PKL<OK0PPL<DB0RES<ON0AR<ZL3VML
Sent: 030925/1502Z @:ZL3VML.#80.NZL.OC #:9010 [Chch-NZ] FBB7.00i $:1982-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Another Aircraft Record attempt
From: "Kurt O. Jauss" <kf6hjo@earthlink.net>
Date: Mon, 22 Sep 2003 23:13:18 -0700
X-Message-Number: 5
Well;
my Uncle Wayne Woollard, is off for another aircraft record attempt. He
plans to leave Salinas Ca. on Tuesday enroute to Kitty Hawk Nc. He is
flying an Aircoupe Alon A-2. He has a tracker onboard with a TT3. This
time he is using his own callsign. KG6PEN-7 To track him and some
pictures, go to;
http://64.167.54.202/home/Aircoupehome.htm
Kurt
----------------------------------------------------------------------
Subject: Re: Excessive Paths WAS WIDE5-5 (Now CHEAP?)
From: "Dick Stanich" <dick@kb7zva.com>
Date: Tue, 23 Sep 2003 1:17:19
X-Message-Number: 6
Sorry, I forgot that the URL in the previous message may not work for
some... unless you copy and paste the entire line. Try this:
http://lostinspace.kb7zva.com
Dick
----------------------------------------------------------------------
Subject: Re: Another Aircraft Record attempt
From: "Dick Stanich" <dick@kb7zva.com>
Date: Tue, 23 Sep 2003 2:36:43
X-Message-Number: 7
On 09/23/03, ""Kurt O. Jauss" <kf6hjo@earthlink.net>" wrote:
>Well;
>my Uncle Wayne Woollard, is off for another aircraft record attempt. He
>plans to leave Salinas Ca. on Tuesday enroute to Kitty Hawk Nc. He is
>flying an Aircoupe Alon A-2. He has a tracker onboard with a TT3. This
>time he is using his own callsign. KG6PEN-7 To track him and some
>pictures, go to;
>
>http://64.167.54.202/home/Aircoupehome.htm
>
> Kurt
This is a great opportunity to try out one of the new filters I was talking
about. Connect to aprswest.net port 14580.
Send a message to SERVER after you are connected. The text of the message
should be:
filter f/KG6PEN-7/200
This is what will happen... Once he sends a valid position report, he will
appear on your map and stations within 200 kilometers around him. As he
moves, the filter will follow him based on his last known position. It's
like tracking a station in Ui-View32... but the server is ONLY going to
send you that data.
Friend Range Filter
Syntax: f/call/dist
Where:
f=friend range command
call=call to be used as center of the range
dist=distance in kilometers from his last lat/lon.
Might as well say something about another filter....
My Range Filter
Syntax: m/dist
Where:
m=my range command
dist=distance in lat/lon kilometers
Same deal, connect to aprswest.net port 14580 Send a message to SERVER and
the text is:
filter m/500
or what ever distance you want to see from your last known position. It
will use the location sent for the same call as you used when you logged on
to the server. The only things that will appear on your map is YOU and
everything around you within 500 kilometers. Regardless of the type of
filter you use, you can still send messages anywhere you want.
There are 11 different filter types. I'm not sure how many servers are up
to speed on this. This is all part of the User Definable Filter Ports that
are available on servers that support javAPRSSrvr and javAPRSFilter. I
prepared a down and dirty text file on why and how this all works:
http://personal.riverusers.com/~aprswest/ports.txt
Dick, KB7ZVA
APRSWest
----------------------------------------------------------------------
Subject: Re:A couple of beginner's questions...
From: WB4GQK@aol.com
Date: Tue, 23 Sep 2003 07:35:01 EDT
X-Message-Number: 8
Regards your USB connection. That should be your highest priority. Garnin
builds several types of cables from their GPS units to USB ports. They also
manufacture a USB to RS232 converter cable (model 010-10310-00) with a
really great CD driver that will handle all Windows operating systems. I
have two of them. It's a tad expensive (there are cheaper ones) but you get
what you pay for.
Congrats on becoming a ham
Good luck
Jim
----------------------------------------------------------------------
Subject: Re:A couple of beginner's questions...
From: "Mike Yetsko" <myetsko@insydesw.com>
Date: Tue, 23 Sep 2003 07:51:26 -0400
X-Message-Number: 9
While there are some differences in USB to serial cables, it's not the
biggest piece of the problem.
It's the software. Brain dead software that insists on working in it's own
little world. And that little world means com ports the way the software
wants them to be.
Ironically, software that has few protections may even work better.
And... With some of the new hardware that has no com ports on the machine
at all, only USB, if the USB to com port can be configured to virtualize
COM1 when it is plugged in, it may actually work better than the same
hardware on machines that have a com port or modem where the USB-COM cable
forces the com port to be 5 or greater.
The reason is some old software still tries to talk to an I/O address and
use an interrupt. If you plug in a USB-COM cable that is allowed to grab
'COM1', and it virtualizes the I/O and interrupt, then the older software
just may work.
Mike
----------------------------------------------------------------------
Subject: Re: Take control <g>
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 23 Sep 2003 08:28:29 -0400 (EDT)
X-Message-Number: 10
On 22 Sep 2003, Byron Smith wrote:
>...Only the Paccomm firmware digis callsign swap the MYALIAS. Its
>probably best not to even mention using MYALIAS for anything, because
>most of the user base of tncs do not callsign swap. This goes for plain
>TNC2's, tnc2 clones (such as 1270's etc), Kantronics (all), etc.
>
>Of course, those digis are Trace digis, and should be
>upgraded to at least UI-DIGI.
Yes, if they need WIDEn-N. But in local areas where WIDEn-N will b e
disabled, then a Paccomm TNC will do perfectly.
Thanks for the info
Bob
----------------------------------------------------------------------
Subject: Take Control of your digi REV(1)
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 23 Sep 2003 08:44:34 -0400 (EDT)
X-Message-Number: 11
As we learn from more discussion, I am modifying my proposal for turning
off WIDEn-N to a different statement. The statement will be:
Take control of your LOCAL DIGI.
If your LAN is overloaded with DX packets from out of area:
1) Disable WIDEn-N and be sure to support RELAY/WIDE call substitution
2) Install a second TNC with WIDEn-N capability that listens to the same
144.39 but Transmits on a local UHF packet frequency.
This removes long haul packets from your LAN, but allows in-town IGates
to pick up the packets on the UHF freq and also allows anyone interested
to "read the long distance mail"...
de WB4APR, Bob
----------------------------------------------------------------------
Subject: Re: WIDEn-N to-UHF path splitters
From: wes@johnston.net
Date: Tue, 23 Sep 2003 09:24:32 -0400 (EDT)
X-Message-Number: 12
I've been thinking about this one....
Given that 70cm has a smaller coverage area, if we did aprs on 70cm
LOCALLY, the coverage area would be smaller and less subject to distant QRM
from another town. The idea here is that if you cut off WIDEn-n at the
edge of your town on 2m, your local digipeater can still hear all the DX
coming in on 144.39. My contention is that even though it will get quiet
inside a city when you cut off widen-n, you will still have to compete with
the DX stations for access to your local WIDE digi. The digi may not hear
you with the distant posit reports booming in. This will do nothing for
getting mobiles into a wide digi... it'll just make the band inside a city
very quiet for the mobiles.
If you make a special MAN (metro network) on some other frequency then the
digipeaters for the local area aren't subject to hearing the distant posit
reports on 144.39. Further, I am NOT specifying a local 70cm frequency...
because the local area frequencies could be coordinated so that city A and
city B do not have their LOCAL users on the same freq's. Of course 144.39
will still be available for travellers.
Such a digipeater would consist of two TNCs and 2m and 70cm radio. The
70cm radio/tnc will digipeat only wide and relay packets. It will also
gate those packets to the 2m radio/tnc. Packets hear on 2m radio/TNC will
stay there.... the 2m radio/tnc will relay,wide and widen-n (if you want),
but will NOT gate anything heard to 70cm... except message traffic intended
for someone heard on 70cm. We really need this type of segmentation.. just
like an IGATE segments the APRS IS from RF.
Folks, the day of a frequency agile APRS radio is closer than you might
think. It is entirely possible to have a local area's bounds specified in
such a way that a tracker (ham hud or kenwood) could QSY and change paths
to suit local customs.
Wes
*If Schwarzenegger is elected we will finally have someone in power who can
read Ashcroft's plan for a safer America in it's native German*
ham callsign: kd4rdb
find me: http://wesvan.zapto.org
----------------------------------------------------------------------
Subject: Re: A couple of beginner's questions if I May.
From: Dave VanHorn <dvanhorn@cedar.net>
Date: Tue, 23 Sep 2003 08:59:58 -0500
X-Message-Number: 13
>1) You absolutely have to resolve the issue of USB-to-serial conversion
>before you go any farther. Virtually none of the GPS / APRS / ham-related
>devices
>will be useable without serial ports.
I've mentioned this before, but it bears repeating. XP's plug and play will
see a newly discovered usb serial port with gps information, as a Microsoft
ballpoint mouse. it will install the driver for that, and take the com port
away.
worse, i've seen cases where it does not make the port busy, but you can
connect with hyperterminal to the port, but you won't see any gps info,
it's being stolen by the mouse driver, and your output goes nowhere.. this
will also happen with a kpc-3, since it's outputting gps data to you..
IONetworks edgeport serial ports have the option to disable plug and play
on their ports. highly desirable.
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
