OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   08.02.03 09:36l 244 Lines 9510 Bytes #999 (0) @ WW
BID : 836-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 31, 1/5
Path: DB0FHN<DB0ZWI<DB0HST<ON0DXC<WA7V<VE1ATT<HA3PG<7M3TJZ<ON0BEL<VK7AX<
      ZL2BAU<ZL3VML
Sent: 030204/0908Z @:ZL3VML.#80.NZL.OC #:58783 [Chch-NZ] FBB7.00i $:836-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

TAPR APRS Special Interest Group Digest for Friday, January 31, 2003.

1. Re: New spec - working notes
2. Paccomm TNC list?
3. Re: New spec - working notes
4. Re: New spec - working notes
5. RE: New spec - working notes
6. RE: New spec - working notes
7. Re: New spec - working notes
8. RE: New spec - working notes
9. Paccomm List?
10. RE: New spec - working notes
11. Re: New spec - working notes
12. Re: New spec - working notes
13. Re: Expiration of Objects
14. More questions for the list
15. Re: WinAPRS-Deleting tracks
16. Re: WinAPRS-Deleting tracks
17. Re: New spec - working notes
18. Re: New spec - working notes
19. Re: New spec - working notes
20. Re: New spec - working notes
21. Re: New spec - working notes
22. Re: New spec - working notes
23. Re: New spec - working notes
24. Re: New spec - working notes
25. Re:  Icons
26. Unproto path ?
27. Re:  Icons
28. Re:  Icons
29. Hurricane Symbols...
30. Re: Hurricane Symbols...
31. Re: Hurricane Symbols...
32. Re: Hurricane Symbols...
33. Re: Hurricane Symbols...
34. Re: Unproto path ?
35. Re: Hurricane Symbols...
36. Re: Unproto path ?
37. Re: Unproto path ?

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

Subject: Re: New spec - working notes
From: "M. Schneider" <msokla@brightok.net>
Date: Fri, 31 Jan 2003 01:14:52 -0600
X-Message-Number: 1

>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.

I think Neil has a good idea here.  It's a question of defining who your
end-users are and what they expect to see.  Obviously, American amateurs are
going to be most comfortable with feet, miles, Fahrenheit, etc.  Amateurs in
other parts of the world will want meters, kilometers, Celsius, etc.  Let
the apps do the conversion while maintaining the information display at a
level the user is most familiar with.  I've spent a great deal of time
living and working in Western Europe, and can deal with KPH and Celsius,
although I'm more comfortable with MPH and Fahrenheit.  But if you put it in
m/s and degrees Kelvin, you are going to lose a LOT of people.  As useful as
all this sounds, if it presents data that the end-user can't easily
assimilate, it won't gain wide acceptance.

Mark Schneider  K5MAR

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

Subject: Paccomm TNC list?
From: "Dakota Summerhawk" <dakotas@hotpop.com>
Date: Fri, 31 Jan 2003 01:24:30 -0700
X-Message-Number: 2

Is there a list for the TNC? I would like some tech questions answered by
the techies out there if possible. Let me know off the list.
Thanks
Peter N0WRE

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

Subject: Re: New spec - working notes
From: Steve Dimse <k4hg@tapr.org>
Date: Fri, 31 Jan 2003 05:04:50 -0500
X-Message-Number: 3

On 1/31/03 at 1:14 AM msokla@brightok.net (M. Schneider) sent:

>I think Neil has a good idea here.  It's a question of defining who your
>end-users are and what they expect to see.  Obviously, American amateurs are
>going to be most comfortable with feet, miles, Fahrenheit, etc.  Amateurs in
>other parts of the world will want meters, kilometers, Celsius, etc.  Let
>the apps do the conversion while maintaining the information display at a
>level the user is most familiar with.  

This is hardly a new idea, it is what the spec has done all along. The spec
only deals with the on-the-air protocol, it is up to the client programs to
do the conversion to whatever units the end user chooses. It makes no
different what units are picked on the air, only that it is explicit and
consistent.

Steve K4HG

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

Subject: Re: New spec - working notes
From: James Jefferson <jjeffers@aprsworld.net>
Date: Fri, 31 Jan 2003 07:07:21 -0600
X-Message-Number: 4

>of time living and working in Western Europe, and can deal with KPH and
>Celsius, although I'm more comfortable with MPH and Fahrenheit.  But if you
>put it in m/s and degrees Kelvin, you are going to lose a LOT of people.
>As useful as all this sounds, if it presents data that the end-user can't
>easily assimilate, it won't gain wide acceptance.

This is simply the underlaying transport protocol. It would be the the
final application to display meaningful results to the end user. With units
like m/s it doesn't take any effort to convert that to MPH. On aprsworld
everything that goes into the database is in metric. I convert every weird
APRS unit to metric (not nescessarly SI base units). On the preferences
page the user gets to choose if they want metric or imperial units. This is
the same concept. Transport the information in the most general format and
then convert to whatever the end user wants to see.

-Jim KB0THN

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

Subject: RE: New spec - working notes
From: Alex <kr1st@amsat.org>
Date: Fri, 31 Jan 2003 08:11:25 -0500
X-Message-Number: 5

Steve Dimse wrote:

>>Xastir for one.  Perhaps the only one.
>>
>FindU and UIView do for sure, dunno about others.

UI Messenger (Cybiko) does as well. However, I think Jeff meant
applications that actually transmit the compressed format, almost all
applications would decode I'd think. 

Especially with PICs and many other microcontrollers out there, I think
we should match the processor with the spec, and not the spec to the
processor. It is not the Spec's fault that a $3 processor can't handle
its requirements. The beauty of the current spec is that it offers
choices. I'm sure there are plenty of cheap microcontrollers out there
that could handle Base-91 encoding, they just don't happen to carry the
name PIC and maybe only a few folks on this list know how to program the
alternatives.

73,
--Alex KR1ST

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

Subject: RE: New spec - working notes
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Fri, 31 Jan 2003 16:41:31 -0000
X-Message-Number: 6

You know, I don't know what the big deal is with Americans and SI units.
After just a few days driving around New Zealand, I was pretty comfortable
with speeds in kph and distances in kilometers.  Though I did have to mash
on the brakes a couple of times going into tight turns labeled '45'.  =]

I think the question now is whether to use the common form or the
scientific/engineering form... kilometers per hour or meters per second,
degrees C or Kelvins, etc.  I'm leaning toward the latter, since it's just
going to be a different conversion factor, and using Kelvins for temperature
would eliminate the need for negative numbers in that field.

Another question I'm debating is the scaling of units.  For example, my spec
currently uses centimeters for altitude to provide the required resolution,
but it could just as well use 1/128ths of a meter and possibly save some
computation for microcontrollers.  Does anyone have any thoughts on this
subject?

Thanks to everyone for the input and support!

Scott / N1VG

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

Subject: Re: New spec - working notes
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Fri, 31 Jan 2003 16:47:54 -0000
X-Message-Number: 7

I've got no intention of forcing a DISPLAY format on anyone, just in case
that wasn't clear.  As Bob's pointed out, that might be a job for someone
else down the road and it's certainly worth thinking about (the military has
long understood the need for common symbology and terminology), but as far
as I'm concerned, you can have your client program convert m/s to mph,
knots, or furlongs per fortnight if you want.  I bigger concern for me is
what it's going to take to have a PIC plugged into a weather station
translate incoming data to the appropriate format for transmission.

Scott / N1VG

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

Subject: RE: New spec - working notes
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Fri, 31 Jan 2003 16:54:29 -0000
X-Message-Number: 8

I'm sure I could program a $5 MC68HC908KX8 to do Base-91 encoding, but for a
new spec designed for 8-bit binary, there's no reason I'd want to.

Bottom line:  When we've got a working translation gateway, then we'll see
what the efficiency is like.  But beyond that, we've already established
that applications like BEACONet with less-established infrastructures are a
prime candidate for implementation of a more flexible protocol.

Scott / N1VG

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



Read previous mail | Read next mail


 16.11.2026 03:42:17lGo back Go up