| |
ZL3AI > APRDIG 27.02.04 15:40l 47 Lines 1269 Bytes #999 (0) @ WW
BID : 2910-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 24, 6/6
Path: DB0FHN<DB0RGB<DB0MRW<DB0ERF<DB0FBB<DB0GOS<DB0EEO<DB0RES<ON0AR<ZL2BAU<
ZL2BAU<ZL3VML
Sent: 040227/1314Z @:ZL3VML.#80.NZL.OC #:19951 [Chch-NZ] FBB7.00i $:2910-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: APRS Client Survey (this has lots of lines!)
From: "Christensen, Eric" <CHRISTENSENE@MAIL.ECU.EDU>
Date: Tue, 24 Feb 2004 23:44:47 -0500
X-Message-Number: 40
Okay... I took all those destinations and have them in Excel... Interesting
but too many "1"s in there...
73s,
Eric KF4OTN
----------------------------------------------------------------------
Subject: Re: APRS Client Survey
From: James Jefferson <jj@aprsworld.net>
Date: Tue, 24 Feb 2004 22:47:13 -0600
X-Message-Number: 41
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
---
END OF DIGEST
Read previous mail | Read next mail
| |
