| |
ZL3AI > APRDIG 04.02.03 10:05l 210 Lines 9400 Bytes #999 (0) @ WW
BID : 829-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 30, 3/8
Path: DB0FHN<DB0RGB<DB0MRW<OK0PPL<RZ6HXA<SP7MGD<WB0TAX<HB9OK<IR0NET<VK3TE<
ZL2BAU<ZL3VML
Sent: 030203/0908Z @:ZL3VML.#80.NZL.OC #:58722 [Chch-NZ] FBB7.00i $:829-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: RE: New spec - working notes
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Thu, 30 Jan 2003 19:44:57 -0000
X-Message-Number: 20
I'm trying to make a protocol that is consistent, extensible, flexible, and
easy for microcontrollers to deal with. As for doubling the load, no - the
converted standard APRS message ONLY would be retransmitted, though the
binary message might go out over a backbone. It's just an idea to let
people use binary-format trackers without a total system replacement.
You mention the frequency overloading... this spec would help to a small
degree just by being more efficient. Of course, you're still stuck with 300
ms transmit delays, but then the spec also specifically addresses
aggregation of messages to save overhead.
And beyond trying to solve specific problems, I'm most interested in
building a framework that gives developers the TOOLS to fix those problems.
APRS is a great idea, Bob, and you did a hell of a job designing a powerful
system within the constraints of existing infrastructure. But you know
better than anyone the compromises and kludges it took to do that. I'm not
expecting everyone to jump on the bandwagon here and ditch the existing
system, but I want the community's help in designing the best system we can,
to be used as an adjunct to APRS for backbone connections, for use in local
operations, or whatever. If it works out well, then maybe we can worry
about replacing things, but I think that's a long way off.
Scott / N1VG
----------------------------------------------------------------------
Subject: Re: Routing question
From: WA8LMF2@aol.com
Date: Thu, 30 Jan 2003 14:46:45 EST
X-Message-Number: 21
In a message dated 1/30/2003 1:50:20 AM Pacific Standard Time,
kd7nm@pugetsound.net writes:
>At best guess, you're probably seeing a packet that's arriving after the
>one that's being placed into the network locally, i.e. the last "copy" of
>that packet to arrive at findu.
This is exactly what happens to me here in Los Angeles.
If I set my path to WIDE1-1, I get into one or more local Igates (and show
up on findu as having been injected into the Internet System in the L.A.
area) almost instantly, either directly or on only one digi hop. If I
set my path to WIDE2-2 or WIDE3-3, findu shows me as inserted into the IS
in San Diego, about a hundred miles down the California coast.
It takes many seconds for packets to be retransmitted a couple of hops to
San Diego, due to the high volume of traffic causing digis to delay
transmitting. The result is that the San Diego igate insertion always is
several seconds up to half a minute AFTER the Los Angeles insertion.
Since findu always picks the most recent IS record for a particular
callsign, San Diego always shows as the point of entry.
Stephen H. Smith wa8lmf @ aol.com
Home Page: http://wa8lmf.com
Ham Radio/Mobile SSTV page: http://members.aol.com/wa8lmf/ham
APRS Stuff
http://members.aol.com/wa8lmf/aprs
----------------------------------------------------------------------
Subject: Words of Warning
From: Steve Dimse <k4hg@tapr.org>
Date: Thu, 30 Jan 2003 14:53:55 -0500
X-Message-Number: 22
As people proceed with a new APRS spec, a few things for you to think
about, to learn from the successes and failures of those who went before.
Good redesign starts with careful analysis of the original, a complete
cataloging of what is right and wrong. I've not seen an explanation of
exactly what problem you are aiming to solve.
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?
When talking about conversions to and from another format, look closely at
the problems that the one conversion we tried previously in the APRS IS
(Mic-E), and why it was a failure. Your proposal seems to include
interconversions of ALL APRS traffic, which has the real potential to cause
grief.
Consider carefully the "second system effect". If you don't understand it,
read up on it, it is important.
Finally, take to heart a central tenet of my profession, expressed
elegantly by Hippocrates: "Primum Non Nocere", or first, do no harm.
Steve K4HG
----------------------------------------------------------------------
Subject: Re: GPS Jammed by junk consumer electronics...
From: "Mike Yetsko" <myetsko@insydesw.com>
Date: Thu, 30 Jan 2003 13:35:09 -0500
X-Message-Number: 23
>I seem to recall from the archives deep in the back of my memory, that in
>about 1978 or so, some one (Winegard perhaps) had a problem with installers
>of mast mounted pre-amps. What was happening was the IN was being connected
>to the OUT and thus radiating all over the place via the TV antenna.
>
>This caused havoc with VHF/UHF Ham and Public Service agencies...
>
>Could this be the event that is being discussed here?
>
>Bob K8YS
Well, think about that for a moment. If you did that, there'd be no
problem because there'd be no power. (And if I remember correctly, the
'input' from the Jerrold and RCA amps from that period were all 'balun'
inputs which would actually short out the power supply if you hooked it to
the input by mistake.
But what people were doing was bringing up twinlead to the amp. They'd
use the correct standoffs and all. Then they'd take a short length of
twinlead to tie the antenna to the amp input. But this would flap in the
breeze. So, to make it look 'neat', they'd make the 'drip loop' as the
instructions said, but they'd 'tape' the loop to the twinlead hooked to
the output.
The result was the output coupled back through to the input.
And the problem came to a head with Radio Shack. At least, that's
where I picked it up at. It was found by a repeater group after they
were repeatedly wiped out from one of these things miles away.
Once it was discovered, then a number of other instances of this
occurring were identified.
The problem was 'generic' in that almost any 300ohm in and out amp
could do it. (Not all did, but most had some form of the problem)
Mike
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: Steve Dimse <k4hg@tapr.org>
Date: Thu, 30 Jan 2003 15:20:58 -0500
X-Message-Number: 24
On 1/30/03 at 7:44 PM Scott.Miller@vandenberg.af.mil (Miller Scott Contr
30SCS/FTI) sent:
>I'm trying to make a protocol that is consistent, extensible, flexible, and
>easy for microcontrollers to deal with. As for doubling the load, no - the
>converted standard APRS message ONLY would be retransmitted, though the
>binary message might go out over a backbone. It's just an idea to let
>people use binary-format trackers without a total system replacement.
It will be quite a while, if ever, that someone sending a binary format
message can expect that all digis will be converting their position. Given
that, few people will field binary trackers. Without trackers, no incentive
for digis to upgrade. Chicken-Egg.
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. Even if you
could make it easier to do the conversion (which I doubt), where is the
need? Why should a tracker use a new format, when the old one works fine?
>You mention the frequency overloading... this spec would help to a small
>degree just by being more efficient. Of course, you're still stuck with 300
>ms transmit delays, but then the spec also specifically addresses
>aggregation of messages to save overhead.
How will the new format be more efficient? Given that 7 or 8 bytes of payload
gives you a position course/speed currently.
>And beyond trying to solve specific problems, I'm most interested in
>building a framework that gives developers the TOOLS to fix those problems.
Again, I ask what specific problems are you aiming to fix, or to develop the
framework to fix?
>APRS is a great idea, Bob, and you did a hell of a job designing a powerful
>system within the constraints of existing infrastructure. But you know
>better than anyone the compromises and kludges it took to do that. I'm not
>expecting everyone to jump on the bandwagon here and ditch the existing
>system, but I want the community's help in designing the best system we can,
>to be used as an adjunct to APRS for backbone connections, for use in local
>operations, or whatever. If it works out well, then maybe we can worry
>about replacing things, but I think that's a long way off.
First off, until the old system is scraped, the new protocol increases the
amount of work of writing a parser. Until everyone is running software that
is known to handle the new protocol, anyone running the old software may
well be missing important data and not know it. Even worse, can you
guarantee that the new protocol you propose, when used on the air, will not
cause crashes in the present applications?
I see this last concern as a serious danger, and should not be
underestimated.
Steve K4HG
----------------------------------------------------------------------
Read previous mail | Read next mail
| |