| |
ZL3AI > APRDIG 03.02.03 14:30l 283 Lines 11202 Bytes #999 (0) @ WW
BID : 799-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 27, 4/10
Path: DB0FHN<DB0ZWI<DB0HST<ON0DXC<WA7V<WB0TAX<HB9OK<IK6PYS<VK7AX<ZL2BAU<
ZL3VML
Sent: 030131/0923Z @:ZL3VML.#80.NZL.OC #:58516 [Chch-NZ] FBB7.00i $:799-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: ARRL Public Service Manual regarding RACES
From: "Ronald Reams" <wa4mjf@worldnet.att.net>
Date: Mon, 27 Jan 2003 09:39:29 -0500
X-Message-Number: 14
The RACES fequncies for liasion to the military
are 3997 kHz and 53.30 MHz.
73 de Ronnie
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Mon, 27 Jan 2003 09:03:40 -0600
X-Message-Number: 15
Thanks, Pat, for saying much more concisely what I was addressing. I
fully agree with your statements (I snipped some below so this post will
be accepted by the list server).
Since APRS is now public domain with the publishing of the
specification, we need to continually look at our applications for ways
of improvement within the constraints of time, display limitations,
intended audience, intended use, etc. This means that there must also
be some allowance for variation but standardization where possible
should be strived for. And this standardization, as you pointed out so
well, should be in the specification which is what programmers will use
when developing new software or modifying existing software.
It also means that tolerance should be displayed by the various authors
when other authors don't implement one aspect or another that they have
implemented, especially if that aspect is not in the specification.
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Juergen Frank <db2fm@jfsattv.de>
Date: Mon, 27 Jan 2003 17:11:25 +0100
X-Message-Number: 16
Hello list-members,
I joined this list some weeks ago and found it very interesting to follow
the discussions.
I did my way to APRS in small steps: more than 10 years ago (when studying
commuication technics) i was active in packet radio, because of getting a
company car and the upcoming GSM mobile phones in Europe and some other
reasons I haven't been on the air for several years. I still had some
equipment (including TNCs) and two years ago I read something about APRS in
the internet (and in the ham-magazine CQ-DL). I collected everything I
could get about it, including APRS Protocol Reference (Approved Version
1.0.1) and read everything. At the end I started to use UI-View (after
testing some other SW and feeling comfortable with UI-View and it's fee,
although I'm a Mac User) and also bought one of Kenwood's TM-D700 for my
car (DB2FM-9).
What I must read the last days under this subject was not was I expected of
a communicating group trying to make APRS better and better. Everybody
following this discussion knows what I mean. It was no discussion anymore
and it was a little bit of a shame...
I'm not a programmer, I'm only a user (who has sometimes also ideas to make
things better). Things should be cleared to be beneficial for the whole
community.
So, please, calm down and come back to an open discussion!
73 de Juergen db2fm
P.S. What about the idea of using a small triangel that indicates status at
a stations icon - sorry - symbol, like a hand of a clock. The good
thing would be: colo(u)r could be used for different things and isn't
needed to see the status (also good for B&W displays!)?
For the 9 stati mentioned by Bob we could use 45=B0 steps (plus triangel
missing).
--
DB2FM
Juergen Frank
mailto: db2fm@amsat.org
mailto: db2fm@darc.de
mailto: db2fm@jfsattv.de
ICQ: 144135020
----------------------------------------------------------------------
Subject: T-238 weather station wind speed...
From: "Mike Yetsko" <myetsko@insydesw.com>
Date: Mon, 27 Jan 2003 11:15:24 -0500
X-Message-Number: 17
I have the ORIGINAL wind instrument on a T-238 with the 4-line display.
Occasionally (twice now) I've seen wind gust listed on the display at
99mph. (For the whole day)
Just wondering... Is this just a noise hit, or could it be rollover
handling in the wind speed counter?
Mike
----------------------------------------------------------------------
Subject: RE: installed infrastructure, WAS: Symbols/Icons wa s something else
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Mon, 27 Jan 2003 16:40:00 -0000
X-Message-Number: 18
So if there's not an established standard, can someone point me to a good
reference on best practices? I'm pretty new to this aspect of the hobby
(though I've got a strong data networking background), and an opportunity
just came up to help install a new mountain digi. It's a long drive up a
really nasty road to get there, and I'd like to get it right the first time.
Scott / N6UQE
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: "stan horzepa" <stanzepa@earthlink.net>
Date: Mon, 27 Jan 2003 12:24:7
X-Message-Number: 20
On 01/27/03, "Bob Bruninga <bruninga@usna.edu>" wrote:
>
>And a LOT of these are NOT in the spec, becuase the TAPR guidelines for
>the SPEC held that nothing could go into the SPEC if it was only in
>APRSdos (the original APRS)... and not yet implemented by the other
>authors at the time.
Bob,
Please don't blame TAPR. TAPR was only a facilitator for the APRS Spec
Working Group. It provided a forum (the Working Group's e-mail list) and
Web space for the group. It never specified any guidelines for the spec.
The Working Group specified the guidelines, not TAPR.
Stan Horzepa, WA1LOU
APRS Working Group Secretary
----------------------------------------------------------------------
Subject: RE: Incident Command Post Symbol
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Date: Mon, 27 Jan 2003 11:11:01 -0800 (PST)
X-Message-Number: 21
On Mon, 27 Jan 2003, Spider wrote:
>Thanks Curt, I posted the symbols for BASE, CAMP and STAGING areas. Did
>you see that post? There is also Helibases and Helispots. Although a
>CASUALTY COLLECTION POINT (CCP) is not official, it has been written about
>and given serious thought and is followed. A CCP would include areas for
>triage and can be quite large.... I = Immediate Treatment, D = Delayed
>Treatment, DECEASED (for the morgue), MINOR = Minor Treatment
Could that be handled nicely with area objects? You can objects of
different colors/sizes, filled or non-filled. In Xastir they get a small
red dot for the object "handle", and the object name is attached to that
dot. You use that dot as a handle in order to modify/delete/move the
object.
I just added some Base/Camp/Staging objects around the ICP object you
placed. I can add some area objects there for CCP's in order for people to
see what they look like in different software packages (or whether they're
shown at all).
--
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: Re: FT-100 operations.
From: "Demetre Valaris" <sv1uy@sv1uy.ampr.org>
Date: Mon, 27 Jan 2003 22:20:12 +0200
X-Message-Number: 22
On 27 Jan 2003 at 0:01, TAPR APRS Special Interest Group digest wrote:
>Subject: FT-100 operations.
>From: Bob Bruninga <bruninga@usna.edu>
>Date: Sun, 26 Jan 2003 20:41:45 -0500 (EST)
>X-Message-Number: 30
>
>I hate to ask a general question to the SIG, but I need to know quickly if an
>FT-100 can be listening to HF and at the same time can be transmitting on 2
>meters FM.
>
>Dont know anyone else to ask but the sig.
>Sorry,.
>
>Bob
No Bob,
Not possible with the FT-100. It is a great radio but it can do one thing
at a time. It has one RX and one TX.
73 de Demetre SV1UY
e-mail sv1uy@sv1uy.ampr.org
http://www.athnet.ampr.org/~sv1uy
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Steve Dimse <k4hg@tapr.org>
Date: Mon, 27 Jan 2003 15:33:44 -0500
X-Message-Number: 23
On 1/27/03 at 12:52 AM bruninga@usna.edu (Bob Bruninga) sent:
>And a LOT of these are NOT in the spec, becuase the TAPR guidelines for
>the SPEC held that nothing could go into the SPEC if it was only in
>APRSdos (the original APRS)... and not yet implemented by the other
>authors at the time.
As Stan pointed out, this is not TAPR's problem.
For those unfamiliar, the APRS WG was formed when things like this were
threatening to tear APRS apart. TAPR only facilitated the process, flying
out at their expense most of the APRS authors to Baltimore (I paid my own
way, and of course Bob lives nearby). I think Bob blames TAPR because it
was in no small part my dissatisfaction that led to this meeting, and John
Ackerman facilitated this process. Despite his recollection, the guidelines
were not TAPR's.
This thread is dredging up many of those old, unpleasant, and still
unsettled issues. Bob created APRS, and deserves every bit of credit for
his idea, but even at the point of the formation of the APRS WG nearly 4
years ago, he was far from the only driving force behind it. This is even
more true now, largely because of the public recognition the APRS WG
provided that APRS had reached the point where one person could no longer
dictate the course of APRS.
User interface is one thing people disagree strongly over, then as now. In
order to end up producing the APRS spec, it was clear that those things
which we were most devisive, like the UI stuff, needed to be left out of
the spec. That decision was pragmatic.
I still maintain they need to be left out of the spec...it is up to each
individual developer/project and their users to decide those things which
are important to them. Each fresh developer (don't forget the key
disagreement leading to the formation of the APRS WG was that anyone that
wanted to could be an APRS developer, they did not need a license from Bob)
brings a fresh viewpoint, and it is much to limiting to force them to fit
their ideas into Bob's or the APRS WG's idea of what APRS should be.
Bob didn't invent the APRS Internet System, he didn't invent Propnet, he
didn't invent the HamHud, and dozens of other innovations that have made
APRS what it is today. Similarly, neither he nor anyone else in APRS has
the foresight and wisdom to say what will be useful in the future. Lacking
that foresight, the spec should provide as little limitation on future
growth as possible. That is why the spec only covers the nuts and bolts of
the actual on-the-air protocol. IMHO, the scope of the spec is a feature,
not a bug!
A quick rebuttal of something someone else said earlier, APRS is not in the
public domain. First "APRS" itself is a registered trademark of Bob, and
deserves to be treated as such. Next, there are limitation on the protocol,
see the APRS WG charter on the TAPR web site for those.
Steve K4HG
----------------------------------------------------------------------
Read previous mail | Read next mail
| |