| |
ZL3AI > APRDIG 27.02.04 15:49l 327 Lines 9178 Bytes #999 (0) @ WW
BID : 2914-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 25, 3/6
Path: DB0FHN<DB0THA<DB0ERF<DB0FBB<DB0GOS<ON0AR<ON0AR<WB0TAX<ZL2TZE<ZL3VML
Sent: 040227/1333Z @:ZL3VML.#80.NZL.OC #:19956 [Chch-NZ] FBB7.00i $:2914-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Destination Addresses
From: "Stephen H. Smith" <WA8LMF2@aol.com>
Date: Wed, 25 Feb 2004 01:59:56 -0800
X-Message-Number: 17
Christensen, Eric wrote on 2/24/2004, 9:00 PM:
>Does this list agree with everyone? Any additions?
>
>APA A-Filter, Alinco, etc
>APAFxx AFilter.
>APAGxx AGATE
>APAXxx AFilterX.
>APAHxx AHub
>APB avail
>APC Windows CE, etc
--SNIP--
I have made up APTIGR for my TigerTronics TigerTrak.
----------------------------------------------------------------------
Subject: Re: Wider paths than Wide2-2
From: "Chris Rose" <kb8uih@sbcglobal.net>
Date: Wed, 25 Feb 2004 06:39:43 -0500
X-Message-Number: 18
Hello,
I will enter the fray and say that I would be happy to receive packets from
other than the local neighborhood where I am. I am not in a heavy
population center but am within 100 mi of one (Detroit). When the band
opens up I receive packets from the Carribean, Fla, Ga, Tx, etc. It doesn't
bother me. I am not TCPIP just rf with a 20' eleveation above ground
antenna(copper cactus) and a 10watt output. I see traffic from the North
East and East and Central US consistantly. I limit my stations at a 1000
and dump my message and stations lists occasionally to rebuild the data when
I think the computer needs a break. I am one of the "home stations"
beaconing @hour with relay,wide,wide. I can use relay,wide as there is an I
gate one hop away in the same county. If that goes down there are other
digis in adjacent counties but my limited power and low antenna can't hit
them reliably. Is anyone seeing my packets down South?
Good luck to all,
Chris
KB8UIH
----------------------------------------------------------------------
Subject: XML and findu
From: "Brad McConahay N8QQ" <brad@n8qq.com>
Date: Wed, 25 Feb 2004 08:21:37 -0500
X-Message-Number: 19
There is a site set up for anybody who can make use of findu.com data in an
XML format.
http://xml.n8qq.com/aprs
It's possible I may be the only one who finds this useful for homebrew
internet/aprs applications, but it's available for anybody else who may
prefer xml for data exchange.
Brad N8QQ
----------------------------------------------------------------------
Subject: RE: APRS Client Survey
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Wed, 25 Feb 2004 08:29:39 -0500
X-Message-Number: 20
>Attention all APRS Users. By popular demand, I am conducting a survey.
>In the message, include the client software that you are using.
>will run this survey for one week or until the messages stop...
A complete waste of time. Just moitor the APRS-IS for an hour, a day,
or whatever you want, and then sort by TOCALL. Bingo, there are
te facts. The TOCALL identifies the software in use.
de Wb4APR, Bob
----------------------------------------------------------------------
Subject: Re: Uncompressed vs Compressed formats
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Wed, 25 Feb 2004 08:33:10 -0500
X-Message-Number: 21
>>One thing to remember is that not all APRS software "reads"
>>compressed format correctly...
>It's been in the spec forever though. Update your APRS software or
>switch to a different one that handles it.
EXCEPT please dont use compressed objects. The Kenwood displays them with
the callsign of the sending station and not the name of the object. Thus,
the information intended to be conveyed to the end user does not show up
where the sender expects it to be seen...
de WB4APR, Bob
----------------------------------------------------------------------
Subject: RE: Spam:XML and findu
From: "Sadowski, Allan" <allan.sadowski@ncshp.org>
Date: Wed, 25 Feb 2004 08:41:44 -0500
X-Message-Number: 22
BRAD
AWESOME
We've just completed our third XML project... and it isn't any more
painful than the typical data translation project the first time you do
it.. but WOW... does it make life better the second time.. and each
additional time you need to translate data... it (dare I say) becomes
almost trivial.
This is the way ALL DATA should be moved around - IF YOU HAVE THE
BANDWIDTH. To heck with fixed fields and separate field/data definition
files. Labels and data... life is good... no implicits - now there is
cooking with gas !!!
I had to do a double take... your effort returns LOTS of data... all
nicely tagged... I didn't know what to expect at first.. but good job...
Now if the maps were so defined... !!! ha ha ha
ALOHA
AH6LS
-----Original Message-----
Subject: Spam:[aprssig] XML and findu
It's possible I may be the only one who finds this useful for homebrew
internet/aprs applications, but it's available for anybody else who may
prefer xml for data exchange.
Brad N8QQ
----------------------------------------------------------------------
Subject: DIGIpeater TOCALL Standard please
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Wed, 25 Feb 2004 08:49:14 -0500
X-Message-Number: 23
The database at:
>http://db.aprsworld.net/tmp/destinations.out
Shows the single largest is "APRS" at 3271.
Which can be just about anything (usually Digis). That is why I asked
several years ago that DIGI owners use the TOCALL of APNxxx as follows:
APN Network nodes, digis, etc
APN3xx Kantronics KPC-3 rom versions
APN9xx Kantronics KPC-9612 Roms
APNAxx WB6ZSU's APRServe
APNMxx MJF TNC roms
APNPxx Paccom TNC roms
APNDxx DIGI_NED
APNUxx UIdigi
From the list then we can see only the following
digis conform to that standard...
APN050 1
APN123 2
APN3 1
APN382 16
APN383 10
APN390 1
APN82 3
APN83 1
APND03 1
APND0P 5
APND0R 8
APND0S 2
APND0U 32
APND0V 16
APND0W 50
APND0X 108
APND0Y 2
APNDOU 1
APNDOW 1
APNDS 1
APNEP 2
APNK 1
APNLNX 1
APNLS 1
APNMFJ 2
APNORW 1
APNRR 1
APNRW 3
APNSMW 1
APNT0U 1
APNU18 51
APNU19 178
APNU19-6 1
APNU1w-15 1
APNU86 1
APNWI 1
APNY 1
----------------------------------------------------------------------
Subject: Re: APRS Client Survey
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Wed, 25 Feb 2004 08:58:22 -0500
X-Message-Number: 24
>>>"Scott Miller" <scott@3xf.com> 2/24/04 10:10:10 PM >>>
>Woo hoo! I made the list:
>
>Is that excluding SSIDs?
Remember, the TOCALL SSID is used EXCLUSIVELY for SSID ROUTING. It should
never be used any other way or the packets will go strange places...
de WB4APR, Bob
----------------------------------------------------------------------
Subject: Re: Uncompressed vs Compressed formats
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Wed, 25 Feb 2004 09:01:37 -0500
X-Message-Number: 25
>>>Jeff King pointed out Bob's line:
>That should take 1 line of assembler
OOPS, sorry.... That line was supposed to have been deleted from the
email. I had started to write about how it only takes on line of assembler
to convert from Base 91 to binary. But then there are the other steps
involved and started all over on the message.
But somehow that line didnt get erased.
Thanks for catching it. It was wrong.
Bob
----------------------------------------------------------------------
Subject: Re: APRS Client Survey
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Wed, 25 Feb 2004 09:12:37 -0500
X-Message-Number: 26
For parsing TOCALLS, all packets that begin with either a ' or ` have to be
ignored from the list. Since those are MIC-E and the TOCALL is encoded
LAT.
Fortunately, only TOCALLS that start with AP should be included in the
list. Somone can do a quick Mic-E encoding and see what latitudes in Mic-E
format would appear as an APxxxxx and ignore them...
Bob
>>>James Jefferson <jj@aprsworld.net> 2/24/04 11:47:13 PM >>>
I'm confused. Can you elaborate?
Most PC based stations (which I think it what this thread started about)
are not sending MIC-E packets and most of those are sending destination.
As far as I know there isn't any "true destination address" in MIC-E
packets. There are some peculiarities that can be used to determine common
types of MIC-E hardware, but nothing beyond that.
FWIW,
-Jim
On Tuesday 24 February 2004 21:40, you wrote:
>What needs to happen is NOT to look at the destination address first, the
>query should decode the raw packet (since it already has to for position
>information) then the true destination address even in MIC-E packets could
>be seen.
>
>Mark Cheavens
>KC5EVE
----------------------------------------------------------------------
Subject: Re: Destination Addresses
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Wed, 25 Feb 2004 09:23:31 -0500
X-Message-Number: 27
The latest TOCALL assignments are always up-to-date on
http://www.ew.usna.edu/~bruninga/aprs/errata.html
de Wb4APR, Bob
----------------------------------------------------------------------
Subject: APRS Destination Holes
From: "Christensen, Eric" <CHRISTENSENE@MAIL.ECU.EDU>
Date: Wed, 25 Feb 2004 09:27:44 -0500
X-Message-Number: 28
I'm missing definitions for the following:
APE*
APF*
APB*
APQ*
APRS(followed by letter) APRSdos???
APRU*
APRV*
APRW*
APRY
APV#
APY*
AP#
Any help???
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
