| |
ZL3AI > APRDIG 07.02.03 11:58l 203 Lines 8550 Bytes #999 (0) @ WW
BID : 862-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 04, 3/3
Path: DB0FHN<DB0RGB<OE5XBL<OE3XSR<OK0PBX<OK0PHK<OK0PRG<OK0NAG<OK0PPL<RZ6HXA<
IK1ZNW<IR0NET<VK3TE<ZL2BAU<ZL3VML
Sent: 030206/0935Z @:ZL3VML.#80.NZL.OC #:58845 [Chch-NZ] FBB7.00i $:862-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: A brief explanation
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Wed, 5 Feb 2003 00:30:51 -0000
X-Message-Number: 23
A number of people have asked for clarification on what exactly I'm trying
to do with a new protocol spec, so I'll try to explain my goals here, simply
and briefly.
Scope:
The new protocol is designed to be usable over the Internet, VHF packet, HF,
UHF backbone, or whatever. I don't have plans to immediately start putting
it on 144.39, but there are plenty of places it can be used, and if it
proves to be a big improvement, then people will have a reason to consider
it for broader application.
Consistency:
The APRS spec was developed largely through evolution. It's been made to do
far more than I think Bob ever imagined, or at least originally intended.
As a result, the spec is really hairy, uses features in ways you wouldn't
always expect, and is generally difficult to implement.
Extensibility:
APRS basically sends a single message type in a packet. It can be a
position message, position with timestamp, weather with position, weather
with position and timestamp, and so on. Data extensions give you a little
bit of mix-and-match capability, but not enough, and they tend to complicate
decoding even more. My proposed protocol uses a building block approach,
with all of the basic elements clearly defined, identified, and delimited.
The initial spec defines all of the existing APRS functionality, plus a bit,
and leaves room for new message types to be added. APRS lets you define
your own message format, but then existing clients won't know how to extract
anything at all from your message. If you wanted to define, say, a
radiation measurement message, you'd either have to create an entirely new
message type and get everyone to decode it, or just tack it on to the
comment field, which is what everyone does now. Then you've got to worry
about parsing your custom data out of the comment. The new spec allows you
to still use a standard position, timestamp, weather report, and whatever
else you want, and add on your custom message as well.
Ease of Processing:
As I've already said, decoding (and to some extend, encoding) APRS data can
be a real pain, especially for small microcontroller-based devices. My
protocol is made to be very micro-friendly, making it easier to develop and
debug new applications.
Efficiency:
The use of a pure 8-bit binary format has some gains in bandwidth
efficiency, though for over-the-air use it's admittedly not a huge
improvement. The protocol could be made more efficient, but not without
sacrificing ease of decoding and/or reducing precision.
Hindsight, and new features:
APRS has been in use for over a decade now. We've seen what it can do, we
know what we want it to do, and we've got lots of ideas for what we'd like
to do in the future. Yes, it's true that we'll never foresee every possible
use for a new technology, but why not take into account what we've learned?
Imagine driving into an unfamiliar area and having your mobile rig
automatically learn the local repeaters and their CTCSS tones, even when
they're not transmitting. Or looking at a map display at in incident
command post, and being able to filter the display based on each unit's
place in the ICS hierarchy. There are lots of things that can be done with
a system like this (what the industry is calling 'location-based services'
now, and trying to cram down our throats in consumer form through our cell
phones), but they're going to be hard to do with APRS as it stands now, and
I'm not aware of any existing protocol that really fills the niche, and is
free from patent or copyright encumberment.
And one last comment to the nay-sayers:
Yeah, it's very possible that the protocol will never catch on, at least not
for primary APRS use. But you know what? I don't care, and I'm going to
work on it anyway. It WILL be used, even if only for my own backbone links
and SAR applications. But the more input I can get from people, the better
the chances are that it'll turn out to be something really useful, and worth
adopting. This isn't just MY protocol, it's YOURS, too. It'll be there for
all the Amateur community to use, and for that matter, commercial interests
as well.
Please, give me your thoughts and suggestions. And to those that already
have, thank you.
(Ok, so it's less a brief explanation and more a lengthy rant, but what did
you expect from a ham?)
73
Scott / N1VG
-----Original Message-----
From: John B. Leonard, Jr [mailto:w9jbl@attbi.com]
Sent: Thursday, January 30, 2003 4:32 PM
To: 'Miller Scott Contr 30SCS/FTI'
Subject: RE: [aprssig] RE: Input needed
Scott, can you put the concept simply for us dummies so we can follow this
thread? From my POV, what started by APR in the early nineties got so
cluttered trying to accommodate new features, and the various authors all
tried to hammer out a protocol to suit everybody that the whole thing got
screwed up. <snip>
----------------------------------------------------------------------
Subject: Re: Words of Warning
From: Rich Osman <Rich@osman.com>
Date: Tue, 04 Feb 2003 18:44:15 -0600
X-Message-Number: 24
LDE
Alex wrote:
>Steve Dimse wrote:
>
>>When talking about a binary protocol, think carefully about why most
>>interoperating protocols on the internet are text based. FTP, HTTP, HTTPS,
>>POP, SMTP, etc. If binary is such a good thing, why were these designed in
>>text, and why, after decades of use for some, do they remain in text?
>
>I honestly don't know and would appreciate at least a hint to why that
>is. We do many things a certain way for years on end without questioning
>its efficiency. There's probably a good reason why the above mentioned
>protocols are in text, but I wouldn't know why that is. I also don't
The simple answer is provided in the earliest RFCs, text is human
readable and therefore easy and practical to debug without special
display tools. Existing text filters work well, and the redundancy that
text provides is helpful, too. It's not particularly efficient in terms
of memory, but is that the only measure? How siginificant is that
efficiency in light of the other overhead issues, like TX turnaround.
>believe in changes just because we feel there's a need to shake up
>things a bit, or because we're simply dissatisfied with the current
>system, without a very clear goal in mind.
If the lesson is forgotten, it might be time to learn it again.
--
mailto:Rich@Osman.com http://www.rich.osman.com
Rich Osman; POB 93167; Southlake, TX 76092 (Near DFW Airport) ARS: N1OZ
If you receive something that says "Send this to everyone you know,"
PLEASE pretend you don't know me.
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: ISS ?
From: Kevin Deckert <kdeckert@mercuryspeed.com>
Date: Tue, 04 Feb 2003 19:02:17 -0800
X-Message-Number: 26
other than the ham voice and APRS frequencies anyone know the "other"
frequencies the ISS uses to communicate?
ve7whk
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: Etrex and Low temps
From: "Brian Riley (maillist)" <n1bq_list@wulfden.org>
Date: Tue, 04 Feb 2003 23:15:54 -0500
X-Message-Number: 28
There was some discussion earlier about the functionality of the Etrex at
low temperatures. I stated then that both my wife and I run Etrexes in our
respective vehicles with D700's. It is our habit to leave the Etrex running
(using the Garmin power/pc cable) 24/7 shutting our D700s off each night.
Back then I said that my Etrex was up and running after some -8F nights.
Here in the NE we just go through a 29 days with the temperature below
freezing (32F), the reality was about 24 days with the temp at 20F or lower
and one 5 day stretch where the temperature never got above 0F with night
time lows between -15F and -27F.
Both Etrexes were still running every morning duirng this cold snap - albeit
the displays on the Etrexes and the D700s were sluggish until they vehicle
interior warmed up a bit. I have no idea what the story would have been if
hey had not been running. They may have needed to warm up some even to start
up, but that is speculation.
cheers ... 73 de brian, n1bq
---
END OF DIGEST
Read previous mail | Read next mail
| |