| |
ZL3AI > APRDIG 04.02.03 10:04l 125 Lines 4189 Bytes #999 (0) @ WW
BID : 834-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 30, 8/8
Path: DB0FHN<DB0RGB<OE5XBL<OE2XOM<DB0PV<DB0MRW<OK0PPL<RZ6HXA<SP7MGD<WB0TAX<
HB9OK<IR0NET<VK3TE<VK4TUB<ZL2BAU<ZL3VML
Sent: 030203/0923Z @:ZL3VML.#80.NZL.OC #:58727 [Chch-NZ] FBB7.00i $:834-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: New spec - working notes
From: "Ronald Reams" <wa4mjf@worldnet.att.net>
Date: Thu, 30 Jan 2003 21:12:10 -0500
X-Message-Number: 58
Well, Ramon, when in Rome.......
73 de Ronnie
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 30 Jan 2003 21:25:13 -0500 (EST)
X-Message-Number: 59
On Thu, 30 Jan 2003, Jeff King 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?
To my knowledge, every client program supports it including the Kenwoods.
So if someone wants to build a tracker to transsmit it, then all existing
stuff should receive it. And it should be doable in a PIC...
>>>... 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.
I think you missunderstand the problem. None of the errors you see are in
LATITUDE which is the only portion of the Mic-E format that goes in the
TOCALL. Thus, that is not an issue to anyone. In fact, the latitude of
3859.11N transmitting an emergency message comes across as the TOCALL sign
of "385911". What could be easier to encode or decode.
THe problem is that some programs do not properly decode the CUSTOM
message bits or the Longitude. But its all there in the spec...
Bob
----------------------------------------------------------------------
Subject: Expiration of Objects
From: Bob Bruninga <bruninga@usna.edu>
Date: Thu, 30 Jan 2003 22:53:13 -0500 (EST)
X-Message-Number: 60
Cleaning out old email, Did any software implement this proposed addition
to the spec?
On Sat, 26 Jan 2002, Bob Bruninga wrote:
>Authors,
>
>I am finally getting around to updating APRSdos and the only things I've
>seen that we have added is the /Exxx expiration format for Positisn and
>objects as shown below:
>On Thu, 12 Apr 2001, Bob Bruninga wrote about /ExxY Expirations:
>
>>THe intent is to have a mechanism for the originator of clutter to help
>>make it go away. So I want him able to include an expiration even in
>>onetime packets with or without a time stamp...
>>
>>Format is /E=xxY Where xx is a 2 byte digital number and Y is units.
>>
>>Thus /E=01M is one minute
>> /E=15H is 15 hours
>> /E=05D is 5 days
>
>This format may appear anywhere in the comment field of an object or
>position. ARGH! With only 20 bytes avail in the D7 comment field, why
>not make it /ExxY? The equal sign is just superfluous.
>
>Has anyone already done it the other way?
>
>Bob
Or did this die on the vine?
Bob
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: Neil Johnson <njohnsn@iowatelecom.net>
Date: Thu, 30 Jan 2003 22:20:17 -0600
X-Message-Number: 61
On Thursday 30 January 2003 07:31 pm, Ramon F. Kolb wrote:
>Last, let's PLEAZZZZZZZ stop using Feet, Miles, Fahrenheit, etc. This
>confuses the heck out of any non-US based person, HAM or not... After 7
>years in this country, I still have no clue how far a highway exit at
>1500ft actually is.... Eh.... 1500 ft divided by 3 is about 500 meters,
>right? By the time I've done that, I passed the exit :)
And if you tell the average American (who hasn't been in the millitary) that
the exit is 500 meters away, they'll miss the exit too. :)
(I do think that standardizing on SI units is a good idea for the protocol,
let the apps do the conversion)
--
Neil Johnson, N0SFH
http://www.iowatelecom.net/~njohnsn
http://www.njohnsn.com/
PGP key available on request.
---
END OF DIGEST
Read previous mail | Read next mail
| |