| |
ZL3AI > APRDIG 04.02.03 10:04l 242 Lines 9089 Bytes #999 (0) @ WW
BID : 832-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 30, 6/8
Path: DB0FHN<DB0RGB<DB0MRW<OK0PPL<RZ6HXA<SP7MGD<WB0TAX<HA3PG<HB9OK<IR0NET<
VK3TE<VK4TUB<ZL2BAU<ZL3VML
Sent: 030203/0917Z @:ZL3VML.#80.NZL.OC #:58725 [Chch-NZ] FBB7.00i $:832-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: RE: Input needed
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 30 Jan 2003 23:22:48 -0000
X-Message-Number: 41
Right, it's still going in an AX.25 UI frame, though most likely tagged as a
distinct layer-3 protocol rather than UNPROTO like the current system. No
one's really answered my previous question about it, but from what I can see
it looks like UNPROTO was used because there was no way to tell an existing
TNC to route 'APRS' traffic when it would have no idea what protocol 'APRS'
was.
Not that there isn't a lot of room for improvement in layer 1 and layer 2.
=] That's beyond the scope of what I'm working on right now. I AM hoping,
however, to reduce the use of the AX.25 address header for things other than
addressing (e.g., symbols, software versions, etc).
Scott / N1VG
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 30 Jan 2003 18:38:04 -0500 (EST)
X-Message-Number: 42
On Thu, 30 Jan 2003, Jeff King wrote:
>>The big problem with APRS is total overload on the national user channel,
>>and I dont see that any of that is a significant "protocol" problem.
>
>What?!? Lets not continue this group psychosis. There are *serious* flaws in
>the level one and level two implementations of APRS, and these are a
>fundamental part of the protocol.
I'd be interested in knowing what they are so we are all working from the
same baseline..
>More to the point, lets compare two *micro-controller friendly* protocols
>that give the positional accuracy in the meter or less range....on the
>other hand the base 2 protocol Scott is suggesting around 18 bytes. At level
>two of the protocol, that is about a 75% decrease in packet size.
Hummh... my APRS Mic-E format puts these items in a PIC-friendly format
and only takes 9 bytes and is used in every Kenwood and Mic-E type device:
CALL, LAT/LONG, CSE, SPEED, ICON, and one-of-7 messages.
If you want 1 foot accuracy, then use my APRS Compressed format that can
put all of the same info into 14 bytes...
Again, I have nothing against inovation, just clairfying that a new
protocol will have to get down to a payload smaller than 9 bytes before it
can claim to be more "efficient"...
Bob
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 30 Jan 2003 18:43:31 -0500 (EST)
X-Message-Number: 43
On Thu, 30 Jan 2003, Jeff King wrote:
>>All the code to convert a NMEA string into the Mic-E, and transmit in AX-25
>>fits in a 1k PPIC controller, presently costing a couple bucks...
>If your happy with 60 foot granularity...
APRS COmpressed format gives 1 foot accuracy in 14 bytes.
>... and trackers in the atlantic and lost in china, then by all means,
>stay with MIC-E.
All of those problems are problems with different authors deconding
software, nothing attributable to the protocol. If you implmenet a new
protocol, every new author will have the same kinds of problems till they
get it right..
>Keep the good ideas coming Scott and don't let the naysayers discourage you.
>Iam following your project with great interest.
No one is naysaying the project, just trying to save him some develpment
time by pointing out what has already been done...
Bob
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: Jeff King <jeff@aerodata.net>
Date: Thu, 30 Jan 2003 19:03:30 -0500
X-Message-Number: 44
On Thu, 30 Jan 2003 18:43:31 -0500 (EST), Bob Bruninga wrote:
>On Thu, 30 Jan 2003, Jeff King wrote:
>
>>>All the code to convert a NMEA string into the Mic-E, and transmit in AX-25
>>>fits in a 1k PPIC controller, presently costing a couple bucks...
>
>>If your happy with 60 foot granularity...
>
>APRS COmpressed format gives 1 foot accuracy in 14 bytes.
Yeap. Does it fit on 1K PIC controller? (no) What trackers presently
support the compressed format "BASE-91" implementation? (none) What client
programs support this?
>>... and trackers in the atlantic and lost in china, then by all means,
>>stay with MIC-E.
>
>All of those problems are problems with different authors deconding
>software, nothing attributable to the protocol.
Technically, yes, yet that doesn't negate the reality of the problem. It is
because of the non-standard use of the AX.25 address field by the MIC-E
format that the authors have had so many problems. And the fact that is is
"a problem", a chronic problem, is enough, regardless of the reason or
excuse.
-Jeff
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Date: Thu, 30 Jan 2003 16:08:24 -0800 (PST)
X-Message-Number: 45
On Thu, 30 Jan 2003, Jeff King wrote:
>Yeap. Does it fit on 1K PIC controller? (no) What trackers presently
>support the compressed format "BASE-91" implementation? (none) What client
>programs support this?
Xastir for one. Perhaps the only one.
--
Curt Mills, WE7U hacker_NO_SPAM_@tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto: A tax on people who are bad at math!"
"Windows: Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: James Jefferson <jjeffers@aprsworld.net>
Date: Thu, 30 Jan 2003 18:10:09 -0600
X-Message-Number: 46
I'm not aiming for more efficient with my support for Scott's proposal. I'm
aiming for a distribution mechanism for internet and inter-node linking ...
an easy to parse protocol (APRS is not by any strech of the imagination ...
parseable by humans, sure ... but a real PITA in software) ...
-Jim
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: "Pat Karp" <pkarp@conwaycorp.net>
Date: Thu, 30 Jan 2003 18:13:35 -0600
X-Message-Number: 47
Bob wrote-
>No one is naysaying the project, just trying to save him some develpment
>time by pointing out what has already been done...
>
>Bob
Naysaying can be interpeted from the fact that several post have done
nothing but attempt to point out reason for not persueing a new APRS like
system. All of the post do have good information that he should consider
(which I believe Scott is). At this point I don't think Scott is going to
let any Naysayers affect his going forward with his project. ;-)
Pat
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Fri, 31 Jan 2003 00:15:05 -0000
X-Message-Number: 48
The current revision of the position format yeilds sub-centimeter resolution
in position and centimeter resolution in altitude (to +/- 83 km) using 13
bytes (course and speed will cost you another 6). Not that you'd really
need that much resolution in practice, but the point is that it's really
simple to decode (no packed bits, power-of-two divisions only) and
reasonably compact. Mic-E has its place on voice channels (though I'd
venture to say you'd be better off not using AX.25 at all for that), but
that's not my concern right now.
Complexity increases the chance of implementation errors (which is why we've
got Mic-E stations in the Atlantic) and requires more processing resources.
For my goals, it's worth sacrificing a bit of bandwidth efficiency for
simplicity and ease of implementation.
Including positional ambuguity for GPS EPE will optionally add another 4
bytes to your position... just added that message type to the spec. Half of
that is header information, but again, it's a sacrifice for simplicity and
flexibility.
Scott / N1VG
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: James Jefferson <jjeffers@aprsworld.net>
Date: Thu, 30 Jan 2003 18:13:58 -0600
X-Message-Number: 49
On Thursday 30 January 2003 06:03 pm, you wrote:
>>APRS COmpressed format gives 1 foot accuracy in 14 bytes.
>
>Yeap. Does it fit on 1K PIC controller? (no) What trackers presently
>support the compressed format "BASE-91" implementation? (none) What client
>programs support this?
I agree with Jeff on this.
aprsworld.net supports display of the compressed packets and that has been
tested in conjunction with Xastir. So I'm somewhat familar with it. And I
suspect that implementing such a compression routine in an 8-bit
microcontroller would be extremely difficult. Not to say impossible, but
there probably wouldn't be much code space left once you got done.
Of course I would love for somebody to prove me wrong and come up with a
the BASE-91 compressor / encoder for an 8-bit micro.
-Jim
----------------------------------------------------------------------
Read previous mail | Read next mail
| |