| |
ZL3AI > APRDIG 03.02.03 14:27l 500 Lines 17086 Bytes #999 (0) @ WW
BID : 751-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 19, 4/5
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<SP7MGD<WB0TAX<ON0AR<ZL2BAU<ZL3VML
Sent: 030123/1044Z @:ZL3VML.#80.NZL.OC #:57977 [Chch-NZ] FBB7.00i $:751-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Backbone SPec
From: Bob Bruninga <bruninga@usna.edu>
Date: Sun, 19 Jan 2003 13:08:19 -0500 (EST)
X-Message-Number: 19
Lets add one thing more to the BACKBONE SPEC:
7) It should suport call-by-call digiepating so that the user does have
the ability to send out a packet to arrive at a digi of his choice through
the backbone. THUS, each BACKBONE CLUSTER that serves a major population
density has a 6 character NAME that can be used as if it were a digipeater
callsign so that the end user can still hav econtrol over his direced
packets.
8) complementary to this of course is the assumption that the Backbone
will do NO WIDE, WIDEn, or any other generic FLOODING routing back to
144.39...
Lastly, do not think of my use of the term BACKBONE as being a linear pipe
for moving traffic from LA to San Francisco (though it could), think of
it more as a HIGH Population Density Area system for making sure that
everyone in the very large, very dense area has access to APRS data
without collisions...
EXAMPLE: The Backbone in LA might be called CALA and in San Diego will be
SDIEGO. Each will contain every packet collected by the lower shorter
range RELAY/WIDE digis in their area.... But they stay in their area
unless requested or directed. But packets only go back to RF using the
rules below. But a person in San Diego knwoing he is traveling to see
someone in LA, might use the path RELAY,CALA,LBEACH. The RELAY gets him
into his local system and onto the SDIEGO Backbone. The CALA gets it into
the CALA Backbone and the LBEACH directs it so that his friend in LBEACH
can watch him coming.
But a Path of RELAY,LBEACH,WIDE will make it to LBEACH, but the WIDE is
ignored by all backbones as are WIDEn-N and anything after a BACKBONE
path. This packet will still be "availalbe" in LA, but will only go back
to 144.39 in LA, if it meets the usual GATE-to-RF rules below.
----------------------------------------------------------------------
Subject: Re: Next Generation TNC -- a "real" TNC, please
From: John Hansen <hansen@fredonia.edu>
Date: Sun, 19 Jan 2003 13:20:53 -0500
X-Message-Number: 20
>I am interested the mobile part of this thread. Look what is out there:
>
>Transmit only :
> TinyTrack ($35)
> PIC-E ($65)
> Stand-alone TNC ($150)
> Alinco radios with TNC ($290)
>
>With receive + Display:
>
> Kenwood TH-D7A ($400)
> Kenwood TM-D700A ($600)
> HamHud HUD+TNC ($250)
> Palm/Pocket/Notebook ($250++)
>
>So IMHO there is a need for a device that can receive AND display packets
>that fits better into our budget.
The PIC KISS TNC has an APRS mode that works as a tracker and will also
receive and display frames on any terminal. It's $xx in kit
form. http://john.hansen.net
John, W2FS
----------------------------------------------------------------------
Subject: Schematic Software
From: Bob Bruninga <bruninga@usna.edu>
Date: Sun, 19 Jan 2003 16:22:27 -0500 (EST)
X-Message-Number: 21
Does anyone have a good simple public domain schematic drawing package?
(that runs on windows)...
I just need somthing simple to give the students to draw up some simple
schematics but that can then be edited by moving things arond a bit as we
hone in on what works.
Thanks
Bob
----------------------------------------------------------------------
Subject: Re: Schematic Software
From: Adi Linden <adi@adis.on.ca>
Date: Sun, 19 Jan 2003 15:38:49 -0600
X-Message-Number: 22
>Does anyone have a good simple public domain schematic drawing package?
>(that runs on windows)...
>
>Ijust need somthing simple to give the students to draw up some simple
>schematics but that can then be edited by moving things arond a bit as we
>hone in on what works.
I am using the freeware version of Eagle. This are the limitations of the
freeware version:
The following limitations apply to the EAGLE Light Edition in general:
The useable board area is limited to 100 x 80 mm (4 x 3.2 inches).
Only two signal layers can be used (Top and Bottom).
The schematic editor can only create one sheet.
The URL: http://www.cadsoft.de/freeware.htm
Adi
va3adi
----------------------------------------------------------------------
Subject: Re: DFing on APRS+
From: Skip Allison <skipk9sa@ameritech.net>
Date: Sun, 19 Jan 2003 15:52:24 -0600
X-Message-Number: 23
Richard Amirault wrote:
>
>----- Original Message -----
>From: "Skip Allison" <skipk9sa@ameritech.net>
>Subject: [aprssig] DFing on APRS+
>
>>I'm starting to use APRS+ for fox hunting since it's the only APRS
>>program that supports DFing.
>(snip)
>
>AMAZING! I coulda sworn that APRSDos "supports DFing".
Well, APRS DOS probably does more to support DFing - except adequate maps.
Skip
K9SA
----------------------------------------------------------------------
Subject: Re: Schematic Software
From: Bob Nielsen <nielsen@oz.net>
Date: Sun, 19 Jan 2003 14:10:36 -0800
X-Message-Number: 24
Bob,
The freeware "light" version of Eagle (http://www.cadsoftusa.com)
should work for this.
Bob, N7XY
----------------------------------------------------------------------
Subject: GPS device makes local news
From: "Wes Johnston" <wes@johnston.net>
Date: Sun, 19 Jan 2003 17:19:16 -0500
X-Message-Number: 25
http://www.theitem.com/CityDesk/030118a_news.cfm
The short version is that the bomb squad was called out to a local hardware
store when a man found a device which was described to be "two sticks of
dynamite with a blinking light" under his car. This was pretty exciting as
I listened on the police scanner! Turns out it was a covert GPS tracker
placed on the man's vehicle by his wife.
Wes
----------------------------------------------------------------------
Subject: APRS County Maps- for WINAPRS/APRSCE
From: "Dakota Summerhawk" <wypcguy@hotmail.com>
Date: Sun, 19 Jan 2003 15:38:25 -0700
X-Message-Number: 26
I found this site in a google search for County level maps. It has all the
states and a few more that are of other areas. It is hit or miss for getting
in and seems to be best to hit it at night.
http://www.cnunix.com/ftp/hamradio/rutgers.mirror/maps/
Thought this might be of interest.
Peter N0WRE
----------------------------------------------------------------------
Subject: Re: Schematic Software
From: "Ryan Wilkins" <ryan@deadfrog.net>
Date: Sun, 19 Jan 2003 19:42:04 -0500 (EST)
X-Message-Number: 27
There's also ExpressPCB which now includes ExpressSCH. Perhaps this may
do what you want as well. It's available for free at
http://www.expresspcb.com and if you get some circuit made up that you
want pressed to a board, these people do that too.
Ryan K9ZOE
----------------------------------------------------------------------
Subject: Posted APRS+SA v2.21
From: "The Hildebrands" <b.hildebrand@verizon.net>
Date: Sun, 19 Jan 2003 16:49:05 -0800
X-Message-Number: 28
APRS+SA v2.21 posted.
Brent Hildebrand, KH2Z
http://www.tapr.org/~kh2z/aprsplus
ftp://ftp.tapr.org/aprssig/winstuff/aprsplus
[]
Current version is 2.21 found in APRSPLUS221.zip
2003.01.19 V2.21
Added - programmable timeout time for Internet connection in Settings.
[Internet]Timeout.
Added - Support for Server Filters are implimented by Roger Bille,
SM5NRK on javAPRServe. See the file JavAPRSFilters.txt
Changed - Extension of MessageForm files has been changed from FRM to MFORM.
Changed - When an Icon overlay is specified, the primary symbol table is
now used for the base Icon, not the secondary symbol table.
Changed - KipSS connections no longer require being registered, for use
with KipSS/PE.
2002.11.17 v2.20
Added - Message Forms. See the file, MessageForms.txt. MSXML4 is
required in order to save data in MessageForms. See MessageForms.txt
for information on installing MSXML4 from Microsoft.
APRS+SA and javAPRServe Filters.
Certain APRS-IS servers and ports now provide a way to filter the
outgoing data stream to client programs. Below is a now from the author
of javAPRSFilter and the specifications for the design of a filter
string. Note - only the most recent filter string sent to a server is
used to define the filter action. In APRS+SA, there are two ways to
specify a Filter for the server: [1] In the APRServe.TXT file, or [2]
as a global setting in Settings, Internet section, Filter key. If the
method [2] is used, it overrides method [1]. Method [1] can be used to
specify different filters for different servers.
Method 1 - APRServe.txt
Each entry in the APRS+SA APRServe.txt file contains the following
information:
ServerAddress ServerPort Server Description # filter specification
Note that the "#" symbol is used to separate the server information from
the filter specification.
Example of Method 1:
aprswest.net:14580 APRS West Filtered Port # filter r/34/-117/1000
r/55/-4/600 p/F b/AE5PL t/s
Method 2 - Global setting in Settings. [Internet]Filter
filter specification
Example of Method 2:
filter r/34/-117/1000 r/55/-4/600 p/F b/AE5PL t/s
NOTE: in APRS+SA, you must include the word "filter"in the
specification in both methods [1] and [2] above.
See the note from Roger, SM5NRK on the APRSSIG, dated 01/18/2003.
All,
I have today released a new version of the filter software javAPRSFilter
to
the server operators. The new version is fixing some problems with
missing
weather stations for t/w filter. All stations with symbols /W, \W and
'overlay'W was not passed. Raw weather packets what not passed either.
Several changes to improved performance has also been done.
4 new filters have also been added. Area, symbol, digipeater and q
Construct. See the full Users Guide below. The new filters are #5 - #8.
Somne of these has been reuqested by you out there. Keep up let me know
about problems and suggestions.
73 de sm5nrk/Roger
==========================
==========================
===============
1.2 javAPRSFilter Users Guide.
Introduction:
The APRS-IS full feed today have a lot of traffic and require a high
bandwidth, in particular for the APRS-IS server sites, but also for some of
you that connect that are only interested in the particular traffic. To
accommodate this a number of servers have special regional feeds which
filter the traffic. There are also some weather specific feeds available.
But all these are setup according to what the server operator "thinks" will
be good for the users. Now we can take this one step further.
Now will each of you be able to select what traffic you are interested in
and the server will create a unique feed for you. There is great flexibility
to construct your personal feed.
How does it work?
Pete Loveall AE5PL have written the APRS-IS server software javAPRSSrvr in
java which is used by a number of servers. Pete has been kind to create some
hooks into his server software so I have been able to write a filter add-on,
javAPRSFilter (also in java). These 2 applications work together to provide
this filtering. Status on the APRS-IS servers can be found here:
<http://ahubswe.net/aprs_stat.asp>
You define the filter by doing the following:
1. Connect and logon to a filter enabled port on a server
2. Send an APRS message to the server requesting the filter you want
Filter commands
There are 4 different kinds of filters that can be used in any combination.
Each filter is working independent and is additive to the feed. This mean if
the filter finds a match it will be passed to you. The filter commands in
the APRS message to the servers call is starting with the word 'filter'
(without quotes) and each filter command is delimited by a single space. A
message with just 'filter?' (without quotes) will return the current filter
definition.
#1 Range filter
The range filter will pass all stations and their beacons, status, messages
etc within a distance from a set location. It will also pass messages to
stations within the filter and positions of the message sender even if they
are outside the range. Up to 3 range filters can be used at the same time to
extend the areas when you have problem to find a good circle match.
Syntax: r/lat/lon/dist [r/lat1/lon2/dist2 [[r/lat2/lon2/dist2]]
Where: r = range command
lat = latitude in degrees (no decimals). Negative for south
lon = longitude in degrees (no decimals). Negative for west
dist = distance in kilometers from lat/lon.
I'm sorry we don't use miles here in Sweden ;-)
Samples: r/55/-4/600 This will pass all traffic for UK
r/37/-81/1500 This will pass all east cost US traffic
#2 Prefix filter
The prefix filter will pass traffic based on if the sender's call starts
with a specific pattern. Up to 10 patterns can be defined at the same time.
Syntax: p/p1/p2/p3... (up to 10)
Where: p = prefix command
p# = The prefix (starting) pattern
Samples: p/K This will pass all traffic from stations starting with K
p/SK/F This will pass stations starting with either SK or F
p/SM5NRK This will pass all traffic from SM5NRK and any SSID at the end
#3 Budlist filter
The budlist filter will pass traffic based on exact match of the sender's
call. Also the SSID is part of the exact match. If you want all SSID use
prefix filter above. Up to 10 calls can be defined at the same time (if they
can fit in a single APRS message).
Syntax: b/call1/call2/call3... (up to 10)
Where: b = budlist command
call# = The prefix (starting) pattern
Samples: b/SM5NRK This will pass all traffic from SM5NRK without any SSID
b/SM5NRK-5/SK5UM This will pass all traffic from SM5NRK-5 and SK5UM
#4 Type filter
The type filter will pass traffic depending on the packet type. More than
one type can be defined in one single command.
Syntax: t/type
Where: t = type command
type = is one or more of the following letters
p = Position packets
o = Objects
i = Items
m = Message
n = NWS Weather
w = Weather
t = Telemetry
q = Query
s = Status
u = User-defined
Samples: t/p This will pass all traffic with a position
t/w This will pass all weather traffic. For
positionless weather objects the corresponding
position packet will also be sent when it is
next heard
t/mos This will pass all messages, objects and
status
traffic
Remeber that the APRS message must start with the word filter and the the
commands.
The above filters can be combined as explain above. Each filter will
however working independent of the others, for example:
filter r/63/16/1000 r/55/-4/600 p/F b/AE5PL t/s
The above filter will pass all traffic within Nordic (range#1) AND UK
(range#2) AND stations starting with F (prefix) AND from AE5PL (budlist) AND
all status traffic (type).
#5 Symbol filter
The symbol filter will pass traffic based on the symbol in the packet.
Syntax: s/pri/alt/over
Where: s = symbol command
pri = symbols in primary table
alt = symbols in alternate table
over = overlay character (case sensitive)
Samples: s/-> This will pass all House and Car symbols
(primary table)
s//# This will pass all Digi with or without overlay
s//#/T This will pass all Digi with overlay of capital T
#6 Digipeater filter
The digipeater filter will pass all packets that have been digipeated by a
particular station(s). Remember that a packet can many time go different
routes to get to APRS-IS and might be digipeated by other stations that is
shown. These packets are filtered out by various filters/application as
duplicates. More that one digipeater can be entered and each are OR
together.
Syntax: d/digi1/digi2...
Where: s = digipeater command
digi# = digipeater call
Samples: d/SM5NRK-2 Pass all packets digipeated by SM5NRK-2
d/SM5NRK-2/SK5UM Pass all packets digipeated by SM5NRK-2 or SK5UM
#7 Area filter
The area filter works the same as rang filter but the filter is defined as
a box of coordinates. The coordinates can also been seen as upper left
coordinate and lower right. Lat/lon are integer (no decimal) degress. South
and west are negative. Up to 3 area filters can be defined at the same
time.
Syntax: a/latN/lonW/latS/lonE
Where: a = area command
latN = North latitude border (-90 to 90)
lonW = West longitude border (-180 to 180)
latS = South latitide border (-90 to 90)
lonE = East longitude border (-180 to 180)
Sample: a/50/-130/20/-70 This will pass all traffic in US
#8 q Contruct filter
The q Construct filter will base all filtering on the q Construct used on
the APRS-IS. For more information about q Contract look here:
<http://www.aprs-is.net/q.htm>
Syntax: q/con/ana
Where: q = q Construct command
con = list of q Construct to pass (case sensitive)
ana = analysis based on q Construct.
i = Pass positions from IGATES identified by qAr or qAR.
Sample: q/C Pass all traffic with qAC
q/rR Pass all traffic with qAr ot qAR
q//i Pass all position packets from IGATES indentified in other packets by
qAr or qAR
Where to connect?
This is up to each server operator if/when they will provide this type of
service. The following servers and ports have this enabled as far as I
know.
ahubswe.net:14580
aprsca.net:14580
aprseast.net:14580
aprswest.net:14580
----------------------------------------------------------------------
Read previous mail | Read next mail
| |