| |
ZL3AI > APRDIG 07.02.03 11:58l 277 Lines 9999 Bytes #999 (0) @ WW
BID : 837-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 31, 2/5
Path: DB0FHN<DB0ZWI<DB0HST<ON0DXC<WA7V<WB0TAX<SV1AAW<IK6PYS<VK3TE<ZL2BAU<
ZL3VML
Sent: 030204/0911Z @:ZL3VML.#80.NZL.OC #:58784 [Chch-NZ] FBB7.00i $:837-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Paccomm List?
From: "Dakota Summerhawk" <dakotas@hotpop.com>
Date: Thu, 30 Jan 2003 21:13:18 -0700
X-Message-Number: 9
Is there a list that has information on the TNC? I am looking for tech info
on the units and such. If someone can provide some info?
Thanks
Peter N0WRE
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: Alex <kr1st@amsat.org>
Date: Fri, 31 Jan 2003 12:40:56 -0500
X-Message-Number: 10
Miller Scott Contr 30SCS/FTI wrote:
>
>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.
I'm sure you could, no one was questioning that. The actual question
arose from the current spec and available implementations of said
compression algorithms, and had nothing to do with what you are doing.
>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.
We? Ev?
73,
--Alex KR1ST
----------------------------------------------------------------------
Subject: Re: New spec - working notes
From: Alex <kr1st@amsat.org>
Date: Fri, 31 Jan 2003 12:42:10 -0500
X-Message-Number: 11
Miller Scott Contr 30SCS/FTI wrote:
>(the military has
>long understood the need for common symbology and terminology)
Good grieve! I'm glad they've caught on; the principle exists since
human development of language.
73,
--Alex KR1ST
----------------------------------------------------------------------
Subject: Re: New spec - working notes
From: "M. Schneider" <msokla@brightok.net>
Date: Fri, 31 Jan 2003 12:09:49 -0600
X-Message-Number: 12
Scott & others,
That's what I thought at first, but after reading Ramon Kolb's comments
about dropping the English measurements in favor of Metric, I became
concerned about the end display being firmed up without any flexibility.
You guys are the big guns, I'm just an end user, but occasionally something
goes by I feel the need to comment on. The whole UHF backbone concept is
very interesting here in Oklahoma, where individual digis may be separated
by 60-80 miles or more in some cases, and igates are few and far between
outside of the metro areas.
Mark Schneider K5MAR
----------------------------------------------------------------------
Subject: Re: Expiration of Objects
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Date: Fri, 31 Jan 2003 10:07:05 -0800 (PST)
X-Message-Number: 13
On Thu, 30 Jan 2003, Bob Bruninga wrote:
>Cleaning out old email, Did any software implement this proposed addition
>to the spec?
>
>>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:
>Or did this die on the vine?
Xastir project: It's still on our TODO list, but it's been there for a
while. It's a good idea and I still think it's worth supporting.
--
Curt Mills, WE7U hacker_NO_SPAM_@tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto: A tax on people who are bad at math!"
"Windows: Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
----------------------------------------------------------------------
Subject: More questions for the list
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Fri, 31 Jan 2003 18:44:33 -0000
X-Message-Number: 14
(For those just tuning in, this is for a proposed
backbone/adjunct/replacement binary protocol)
Ok, I've changed the spec from ellipsoid height to MSL for altitude, since
the NMEA GPGGA sentence outputs it that way and barometric altimeters are
calibrated that way. Temperatures will be in Kelvins. Speeds are in m/s.
By popular demand, I've added a Maidenhead field.
Here are some more items I'd like input on:
GPS status message - no more raw GPGGA data, but some people still might
want quality data with their fix. Horizontal DOP is included in GPGGA, so
that would be easy to include. Number of satellites in use is also in
GPGGA. VDOP and especially PDOP might be nice to have, but they'd require a
tracker to parse the GPGSA sentence. Is it worth including them in the
spec? Right now I'm thinking HDOP and # of sats should be mandatory for the
format, and VDOP and PDOP could be optionally added to the end for those who
choose to parse GPGSA. I'm not including the 'satellites in view' data,
because it's just too much data, and anyone who really cares can model it in
Satellite Toolkit and figure it out themselves.
FireNet - I don't really know much about this, and it looks like the website
is down. Are there any FireNet-specific additions that would make sense in
the spec? (Thanks to Ev for providing BEACONet info.)
Rainfall - How's fractional millimeters? What about the time scales? I see
right now we've got '1 hour', '24 hour', and 'since midnight' slots. How's
this system working out so far? Is it worth keeping, or does it need
replacement?
Earthquakes - My understanding is that earthquakes are represented as
objects with magnitude and depth in the comment field. I'm planning to make
an earthquake-specific object type to hold these attributes. Any
suggestions on other object types which need common attributes associated
with them would be appreciated.
Any spacecraft data items? Besides Keplerian elements. Parameters that are
common to all sats could go here.
Thanks...
Scott / N1VG
----------------------------------------------------------------------
Subject: Re: WinAPRS-Deleting tracks
From: "Germino" <mgermino@inreach.com>
Date: Fri, 31 Jan 2003 11:01:12 -0800
X-Message-Number: 15
I first asked the question.
>>Is there an easy way to clear the tracks in WinAPRS, without clearing all
>>the stations?
>>
>>Mike
>>73, AD6AA
I guess I wasn't clear. What is needed is to clear the tracks (or trackers)
from the memory, not from the map screen. I would like to hit show all
tracks and see the movements for the last 12 hours. (The ability to see a
fresh set of tracks everyday.) If I clear stations everyday, I also clear
the WX stations, which I want to see several days of data.
If WinAPRS can not do this is there a program that will?
Also, thank you to those who replied to the previous unclear question.
Mike
73, AD6AA
----------------------------------------------------------------------
Subject: Re: WinAPRS-Deleting tracks
From: Keith Sproul <ksproul@rci.rutgers.edu>
Date: Fri, 31 Jan 2003 14:14:08 -0500
X-Message-Number: 16
Select the station that you want to clear (in any of the LISTS) and
hit 'C' for clear.
This clears everything, the track, any alarms you might have set on
that station and the FLAGGED flag..
Keith Sproul
--
Keith Sproul ksproul@rci.rutgers.edu WU2Z
Student Housing Network Coordinator 732 445-3695 W
Rutgers University Computing Services
----------------------------------------------------------------------
Subject: Re: New spec - working notes
From: "Ramon F. Kolb" <ramon@ieee.org>
Date: Fri, 31 Jan 2003 14:55:29 -0500
X-Message-Number: 17
Just to make sure... After re-reading my original email, I think it may
have been read by some that I'd want to force DISPLAY of metric units on
the end-user's user interface. That's not what I meant... The end-user
interface can do a conversion into whatever unit that is suitable for
the target audience as far as I am concerned. However I do stay with my
comment on using a SINGLE WORLDWIDE standard for the units that the
protocol uses. I've seen too many commercial and non-commercial snafu's
just because protocols con confused. SI is the closest we can probably
get to international standards, and really... Outside the US and UK
nobody has a clue about miles, gallons, etc.
I am not sure how far to the extreme we should take this. For example:
-temperature in Kelvin, I can agree to the argument. (Celsius would be
my alternative choice)
-speed in m/s I see as well
-Angle in radiants is more difficult, since you probably have to do
conversion to get to RAD in the first place.
One of the things you may think of, is the source unit of the data. For
example, if your source is NMEA-0184 (from a GPS device or so), you'd
probably put that data in that format. This means speed in knots,
altitude in meters, and hodgepodge of other units. This would be of the
advantage of "microcontroller" powered devices, as they don't have to do
any online conversion.
Again, I don't want to say that my opinion is the only one with merit:
I'm just bringing out some ponts for thought.
73s,
--Ramon
Ramon F. Kolb, W1/PA3EUG, Boston, MA, USA [FN42KI]
ICQ:77117744; MSNMGR:legalalien30@hotmail.com
http://kolb.webhop.org
----------------------------------------------------------------------
Subject: Re: New spec - working notes
From: WA8LMF2@aol.com
Date: Fri, 31 Jan 2003 15:08:03 EST
X-Message-Number: 18
In a message dated 1/31/2003 11:58:23 AM Pacific Standard Time,
ramon@ieee.org writes:
>I've seen too many commercial and non-commercial snafu's
>just because protocols con confused.
Just ask NASA about the Mars Polar Lander ! !
>SI is the closest we can probably
>get to international standards, and really... Outside the US and UK
>nobody has a clue about miles, gallons, etc.
Even the UK is now officially metric. The only other country that still
uses the US customary system, AFAIK, is the country formerly known as Burma
(a vestige of the British colonial era).
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
----------------------------------------------------------------------
Read previous mail | Read next mail
| |