| |
ZL3AI > APRDIG 03.02.03 07:29l 290 Lines 12226 Bytes #999 (0) @ WW
BID : 811-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 28, 4/6
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<IK1ZNW<IR0NET<VK3TE<ZL2BAU<ZL3VML
Sent: 030201/0948Z @:ZL3VML.#80.NZL.OC #:58558 [Chch-NZ] FBB7.00i $:811-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: SATELLITE RADIO STATION
From: "Jake" <snakyjake2@hotmail.com>
Date: Tue, 28 Jan 2003 08:38:59 -0800
X-Message-Number: 21
I am able to hear satellite packets from my TH-D7A(G) with a 1/4 antenna.
Still trying to find a way to transmit APRS packets to the satellites
though. Also, I really need a good pass and be outside in order to hear the
satellites.
Jake
WA7JAK
----------------------------------------------------------------------
Subject: D700 and VS3
From: "Paetzold, Kevin" <Kevin.Paetzold@stratus.com>
Date: Tue, 28 Jan 2003 12:03:17 -0500
X-Message-Number: 22
It took me a couple days to get things fixed up so that I could submit to
the list. As a result I was off the list for about a week and I do not
know if anyone else replied to the question about D700 and the VS3. my
original message is below. 73,
K1KWP
-----Original Message-----
From: Paetzold, Kevin
Sent: Wednesday, January 22, 2003 10:53 AM
To: 'TAPR APRS Special Interest Group'
Subject: D700 and VS3
I bought a used TMV7A recently. Imagine my surprise when I reset it and
found out that there was a VS3 (i.e. voice module) installed. It was
actually pretty annoying and I turned it off (although Japanese mode was
somewhat interesting :-)
This weekend I took the VS3 out of the TMV7A and put it in the D700. The
sum total of the APRS support seems to be that it will announce the
callsign of a station that sends a message to you (does not seem to
announce for bulletins etc..). If the received message starts with a "%"
it will also be spelled out (not pronounced but spelled). So, I think you
could probably find better use for $xx (or whatever) than buying a VS3 for
APRS use (I am glad I did not really pay for the one I have).
I will however say that the D700 makes much better use of the VS3 in
general than the TMV7A. If I was sight impaired I do not think that the
TMV7A voice support would be all that much help. The D700 voice support
seems much better. It actually is not even annoying to have all the voice
stuff enabled fulltime.
73,
K1KWP
----------------------------------------------------------------------
Subject: OnStar GPS for APRS
From: "Tom Nenno" <nennotw@hotmail.com>
Date: Tue, 28 Jan 2003 12:25:23
X-Message-Number: 23
I found a web page that documents how to get the NEMA GPS signals from the
GM OnStar.
See http://members.cox.net/onstar.
I haven't had a chance to try it yet.
Tom AA3VO
----------------------------------------------------------------------
Subject: client software testers needed
From: "Spider" <spider@rivcom.net>
Date: Tue, 28 Jan 2003 11:39:57 -0700
X-Message-Number: 24
I need a few testers...would really like the software authors themselves
excluding UI-VIEW and XASTIR.
If you write APRS User Software...I need help in testing....wont take
long.....about 1/2 hour's worth of your time.
Very simple tests
I apologize for not knowing all the software authors out there.
Email me off this list if you can help jim@wa6oft.com
Jim, WA6OFT
----------------------------------------------------------------------
Subject: Re: APRS Symbols (versus Windows ICONS)..
From: Mark Sproul <msproul@jove.rutgers.edu>
Date: Tue, 28 Jan 2003 14:18:06 -0500
X-Message-Number: 25
At 6:32 PM -0500 1/26/03, Bob Bruninga wrote:
>On Sun, 26 Jan 2003, Spider wrote:
>
>>In APRSdos (never have seen it) how does it handle several stations
>>within a few feet of each other? How do you seperate stations?
>
>Several methods in APRSdos:
>
>1) Zoom in until they separate. APRSdos can zoom to the 1/32nd mile scale
> on any screen meaning a pixel represents about a foot.
>
>2) OBJECTS and STATIONS use different LABELing conventions. Station Calls
>always show to upper right of Symbol, Object names always show to lower
>right of symbol. Thus if an OBJECT and STATION are at the same location,
>you will see both labels, (but ICONS are superimposed).
>
>3) Press > or < keys which cycle through every station on the screen
>displaying on the bottom line all the attributes of each station. So if
>you zoom in so that only a few stations are on the sceen, and then cycle
>through the < or >keys, any statiosn stacked on top of each other very
>quicly become apparent.
>
>4) Move cursor nearby, hit ENTER to select it, move cursor, hit Insert key
>to move it over a few feet so you can see if anyone is underneath...
>
>Thats all that come to mind...
I dont see how this is different than double clicking on a station to
see the details.
Mark Sproul
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 28 Jan 2003 14:28:50 -0500 (EST)
X-Message-Number: 26
On Tue, 28 Jan 2003, Steve Dimse wrote:
>I really don't want to rehash what brought us to that point, but in
>brief my motiviation was that I was tired of you making unilateral
>changes in the APRS spec, and trying to dictate the way things were to
>happen, and who should be allowed to write a program using the APRS
>protocol.
I was proposing additions to the spec where I felt it was deficient.
Just because I was predominantly the 'only' person making such proposals,
doesn't make them 'unilateral changes'. They wouldn't go into the spec
unless they were agreed by the WG.
>>And the total inability of that APRS-Working Group (as a group) to agree
>>to absolutely anything since and make one single formal change to the SPEC
>>..., is a testament to the validity of that last sentence.
>>
>Generally Bob, problems like this start at the leadership. If the APRS
>WG has done nothing, maybe you should look to yourself...
The main thing that APRS needs is an APRS-IS spec and a BACKBONE SPEC to
lead us through the future of APRS which is so intimately tied into the
internet and so totally saturated on RF. There have been three attempts at
an IS-Spec, but to date, nothing has been presented to the APRS-WG for
deliberation and acceptance. On the backbone issue, I have been
attempting to lead discussions as to how to do RF backboning (and in most
cases, it relies on APRS-IS kinds of routing)...
Bob
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 28 Jan 2003 15:09:54 -0500 (EST)
X-Message-Number: 27
On Tue, 28 Jan 2003, Steve Dimse wrote:
>...The alternative explanation to a lack of leadership is that no one
>else thinks of these proposed changes as being important. Understand,
>this is in large part what we were aiming to stop, the willy-nilly
>alteration of APRS to suit your latest whim...
None of them were latest whims. Please see below.
They were fundamental to the basis of APRS and had been in there all
along. I was just trying to make sure that APRS would allow users of
different systems to be able to communicate information end-to-end and
have the same interpretation at the receiving end as the intent of the
sender.
>> 4) All users regardless of who's applications software in that
>> same area will "see" the same information displayed as intended
>> by the originator of that information.. (Again, I am not saying
>> 'how', just 'what' should be displayed)...
>
>[I cannot agree]. This is simply not possible...
Maybe not, but it should be a goal towards which every aspect of APRS
across platforms are measured.
>...The success of APRS means that displaying information has become like
>drinking from a firehose. There are many different philosophies for user
>interface, many different ideas that can and should be tried. It is up
>to the programmer to invent and implement them, and for the users to
>choose which suits their needs. It should not be up to you, or anyone
>else, to dictate how data is to be displayed on-screen.
Again, I NEVER suggest "how". I am more interested in "what" gets
displayed. Always have been. Here are some of the most controversal
"issues" I raised and which have been fought tooth-and-nail by some people
on the APRS-WG. These are "information content" that should be displayed
and preferably graphically:
MAPS: Maps should have a means to display the range scale of the view
so that distant users can "view" the same area of interest by
easily referring to a single variable called "range scale".
POSITIONS/OBJECT PACKETS: APRS positions or objects (they are the same)
convey several attributes. They are: CALL, POSIT, SYMBOL, TYPE,
a "leader" showing course and speed, and any OVERLAY characters.
In addition they should have a means to uniquely display these
additional attributes that *are included* in every APRS position
or object packet:
AMBIGUOUS POSITIONS: Not all positions are known precisely. Any
position that is displayed that is not known to the general
precision of GPS (nearest .01 degree) must have some indication
to the viewing end-user that this position is not precise and
also convey to that viewer the degree of ambiguity.
MOVING STATIONS: Any object that is moving at the time of its
packet must be displayed to the end viewer in a manner that is
separate and distinct from a similar display of a non moving
station.
DEAD RECKONING: Any object that is dead-reckoned must be displayed
in a distinct manner and both the last-known position and present
estimated position must be shown so there is no ambiguity in
interpretation. Or altenativly, maybe the display of an elapsed
time, or an error elipse. Again, how it is displayed is up to the
author, but it MUST be displayed.
>... Specs should specify the interchange of data, and the programmer
>should be free to offer his own UI.
And I have always agreed to that 100%! Authors may use any device
available to them to display this information, but I only insist that
those are the items of information included in an APRS position/object
packet, and they must be displayed somehow. This is essential if we
expect different users of APRS on different software platforms to arrive
at the same "meaning" of the "information" intended by the sender.
I can give numerous examples where the lack of display of some of the
these information variables on different platforms can give TOTALLY
MISSLEADING interpretations to different viewers of different "APRS"
implementations. This must not be allowed to happen in a "communication"
system designed to help amateurs communicate reliably... or else the
integrity of the whole system is compromised.
And I suggest, that at this date in the evolution of APRS, that it's
integrity is quite compromised because the only way to get consistent
display of the fundamentals of "situational awareness" between end users
is for them to both use the same software program. That is the only way
they can be assured of consistency. So you see, I am actually fighting so
that every author's program can be used equally, and so that APRS does not
fractionalize down lines of program-specific usages in local areas.
So it is not "do it Bob's way", its "lets do it in a consistent way that
is platform independent"... If I come across as telling someone
how to do it, ignore that interpretation, Focus instead of
figuring out how to accomplish the objective, not the details...
The above items are fundamental to -any- tactical navigation and display
system (I do have 20 years experience as a Naval Combat Systems Officer
and have spent all of my at-sea time involved in the tactical real-time
display of information to a variety of users on a variety of platforms).
Any display system of tactical real-time moving stations/objects
(depenedent on infrequent input) must have at least the above common
standards of elements displayed to the end user if common interpretations
of that information are expected... That is why the APRS POSITION report
contains that information. It was INTENDED to be displayed to the
receipent.
de WB4APR@amsat.org, Bob
----------------------------------------------------------------------
Read previous mail | Read next mail
| |