OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   12.05.04 10:25l 243 Lines 9146 Bytes #999 (0) @ WW
BID : 3207-ZL3AI
Read: GUEST
Subj: TAPR Digest, Apr 22, 1/10
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<ON0AR<ON0AR<WB0TAX<VK7AX<ZL2BAU<
      ZL3VML
Sent: 040512/0738Z @:ZL3VML.#80.NZL.OC #:23785 [Chch-NZ] FBB7.00i $:3207-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

TAPR APRS Special Interest Group Digest for Thursday, April 22, 2004.

1. got it!
2. Re: Introduction
3. RE: got it!
4. kallen2@bellsouth.net
5. The APRS-WG and spec improvements.
6. RE: The APRS-WG and spec improvements.
7. Re: kallen2@bellsouth.net
8. From: "KC2MMi" display the position data?
9. Re:Website for APRS station info
10. Re:Website for APRS station info
11. Re: APRS greater precision
12. Re: Additional thoughts on the great debate....
13. Re: Additional thoughts on the great debate....
14. Re: APRS greater precision
15. Re: APRS greater precision
16. Re: APRS greater precision
17. Re: Additional thoughts on the great debate....
<LYR36507-195826-2004.04.22-12.06.35--mikejp#videotron.ca@lists.tapr.org>
18. compatibility question
19. Re: The APRS-WG and spec improvements.
20. Re: Additional thoughts on the great debate....
<LYR36507-195826-2004.04.22-12.06.35--mikejp#videotron.ca@lists.tapr.org>
21. Re: Additional thoughts on the great debate....
22. Re: Additional thoughts on the great debate....
<LYR36507-195826-2004.04.22-12.06.35--mikejp#videotron.ca@lists.tapr.org>
23. Re: Additional thoughts on the great debate....
24. Re: compatibility question
25. Re: compatibility question
26. Re: The APRS-WG and spec improvements.
27. Re: APRS Kenwood Radios
28. Re: Additional thoughts on the great debate....
<LY	R36507-195826-2004.04.22-12.06.35--mikejp#videotron.ca@lists.tapr.org>
29. Re: Ambiguity?
30. RE: The APRS-WG and spec improvements.
31. Re: Kenwood MObile APRS
32. Re: From: "KC2MMi" display the position data?
33. Re: APRS greater precision
34. Re: APRS greater precision
35. Re: Additional thoughts on the great debate....
36. Pocket Tracker Question for the group
37. Re: Additional thoughts on the great
debate....	<LYR36507-195826-2004.04.22-12.06.35--mike
38. Re: Pocket Tracker Question for the group
39. Re: APRS greater precision
40. Re: Additional thoughts on the great debate....
41.  Pocket Tracker Question for the group
42. Re: Additional thoughts on the great debate....
43. Re: Additional thoughts on the great debate....
44. Re: Additional thoughts on the great debate
45. Re: compatibility question
46. Re: Additional thoughts on the great debate....
47. Re: Ambiguity?
48. Re: Kenwood MObile APRS
49. Re: Ambiguity?
50. Re: Additional thoughts on the great debate....
<LYR36507-195826-2004.04.22-12.06.35--mike
51. Re: Additional thoughts on the great debate....
<LYR36507-195826-2004.04.22-12.06.35--mike
52. Balloon schedule e-mail list
53. Re: Additional thoughts on the great debate....
54. Re: Additional thoughts on the great debate....
55. Re: Additional thoughts on the great debate....
56. Re: The APRS-WG and spec improvements.
57. Re: Additional thoughts on the great debate....
58. Re: Additional thoughts on the great
debate....	<LYR36507-195826-2004.04.22-12.06.35--mike

----------------------------------------------------------------------

Subject: got it!
From: "Spider" <spider@rivcom.net>
Date: Wed, 21 Apr 2004 20:39:16 -0700
X-Message-Number: 1

I received my OpenTracker today.  Hooked it up to an ADI 201 HT and it works
like a charm.

I am using this in the compressed posit mode.  I found the firmware load
gets hosed up if I try smart beaconing.  Went back to timed beacons and
everything aok.  Used a Garmin Rino 120 to test with and everything seems
AOK!

This is what UI-View did:

0:23:55R WA6OFT-8>APOT01,WIDE,SAR <UI Len=36>:!/=6D^1X;cj7!G 14.0V 36CLPSO
SAR 117

I do notice in the packet voltage and temp....my my...I LIKE THIS!!!!
However....need a space added between
C (celsius) and the rest of the comment.  No big deal though...just download
new firmware when it's fixed and Bam!
Need to get some sleep, but will mount is as soon as I find a plastic screw.

Anyway, very cool, Scott!  Will start testing locally, soon!

Jim, WA6OFT

----------------------------------------------------------------------

Subject: Re: Introduction
From: "Scott Miller" <scott@3xf.com>
Date: Wed, 21 Apr 2004 21:09:05 -0700
X-Message-Number: 2

But with existing TNCs, they're not going to be looking for a PUI frame.
They'll see a valid HDLC frame that starts and ends with a FLAG, and has a
valid FCS.  But when they try to grab the address fields, control, and PID,
at best they're just going to generate an error and throw out the packet.
Worst case, they pass on trashed packets or they lock up completely.

Not a problem if it's never going to share a channel with older equipment,
but if it is, you'd better look out.

Scott
N1VG

----------------------------------------------------------------------

Subject: RE: got it!
From: "Scott Miller" <scott@3xf.com>
Date: Wed, 21 Apr 2004 21:17:16 -0700
X-Message-Number: 3

>I am using this in the compressed posit mode.  I found the firmware load
>gets hosed up if I try smart beaconing.  Went back to timed beacons and

Whoops.  I'll have to check that out.  I was in a hurry to get the fixed
compressed firmware out and forgot to test it with smartbeaconing enabled.
I also once had it fail to compress a position properly and it dumped me in
Canada briefly.  Not sure what happened there, but I'm working on it.  I
think it may be a stack allocation problem.

>However....need a space added between
>C (celsius) and the rest of the comment.  No big deal though...just download
>new firmware when it's fixed and Bam!

Easy workaround for now is to put a space at the start of your comment.

>Anyway, very cool, Scott!  Will start testing locally, soon!

Thanks, keep the feedback coming.

Scott
N1VG

----------------------------------------------------------------------

Subject: kallen2@bellsouth.net
From: WB4GQK@aol.com
Date: Thu, 22 Apr 2004 08:17:18 EDT
X-Message-Number: 4

Keith has an excellent point in his message, however I believe everyone 
should be aware of the actual accuracy that is being acheived from GPS. In
my early engineering career I was a registered mine surveyor. I later was
connected with the US Geodetic Survey operations. As a consequence I still
receive symposium papers and occasionally visit with old friends.  Last
year I had the opportunity to watch a new Navcom RT-3010S GPS surveying
instrument locate itself within CENTIMETERS of a geodetic survey mark!
Totally astounding! 

Obviously this instrument is way out of the price range of we amateurs, but 
the point is the GPS accuracy that is attainable today is in the centimeter 
range. Perhaps by tomorrow it will be in the millimeter range..

You can obtain more info from:

www.navcomtech.com

Jim

**********************************cpy >
 I think APRS is a fun and useful thing as is.  But realize that GPS
accuracy has it's limits also.

----------------------------------------------------------------------

Subject: The APRS-WG and spec improvements.
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Thu, 22 Apr 2004 09:43:01 -0400
X-Message-Number: 5

>>>Jim Duncan <jdbandman@earthlink.net> 4/21/04 9:23:12 PM >>>
>...It means, simply, that what Bob says goes...

As the technical chair for the APRS-WG, I try to make sure that the on-air
protocol remains compatible.  And document the improvements since
publication.  This is important for a service where multiplle authors bring
multiple ideas to the table.  The last thing we want is multiple
incompatibilities.

>Abandon the APRS Spec and develop a new way of doing 
>things. Who says that we HAVE to continue using APRS?

I also strive to incorporate new needs into the protocol but it is hard
when I cannot get agreement from the individual authors.  If we cannot get
agreement, then we cannot put it in the spec.  This is as frustrating to me
as it is to you...

In response to the demand for more precision, for example, I immediately
made a working proposal for the !XYZ! construct that gives precision to 1
foot and also includes the DATUM information AND is fully backwards
compatible with all existing applications.  Yet, it was ignored... and
there were no alternatives offered other than:

"my software can do it better..."  Mine has precision to 1 cm, "Mine can do
anything"..  Lets abandon the kenwoods... "We must abandon the protocol"...
"Radios that cost $475 are too expensive..."

etc.  You see why it is so hard to get ANY change to the APRS protocol?
Many people that could make it work are only in it for themselves...
instead of working as a group for the best for all of us..

de WB4APR, Bob

----------------------------------------------------------------------

Subject: RE: The APRS-WG and spec improvements.
From: "Scott Miller" <scott@3xf.com>
Date: Thu, 22 Apr 2004 07:14:33 -0700
X-Message-Number: 6

>In response to the demand for more precision, for example,
>I immediately made a working proposal for the !XYZ!
>construct that gives precision to 1 foot and also includes
>the DATUM information AND is fully backwards compatible

So give us some properly constructed example packets, show how it'll appear
on the D700 screen, and let us test the proposed format with our clients of
choice.

Scott
N1VG

----------------------------------------------------------------------




Read previous mail | Read next mail


 24.11.2025 13:35:16lGo back Go up