| |
ZL3AI > APRDIG 07.02.03 11:53l 254 Lines 10214 Bytes #999 (0) @ WW
BID : 844-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 01, 3/5
Path: DB0FHN<DB0RGB<OE5XBL<OE3XSR<OK0PBX<OK0PHL<OK0PCC<OK0PAD<OK0PPL<RZ6HXA<
IK1ZNW<IK6PYS<VK3TE<ZL2BAU<ZL3VML
Sent: 030204/0925Z @:ZL3VML.#80.NZL.OC #:58790 [Chch-NZ] FBB7.00i $:844-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: RE: Hurricane Symbols...
From: "Bob D." <n2iph@comcast.net>
Date: Sat, 01 Feb 2003 08:49:30 -0500
X-Message-Number: 15
>>See the screen capture at: ...~bruninga/aprs/symbols.html
This is something I truly miss in all the versions of APRS that I have
tried, and its why I prefer to stick with APRSdos as the software used
in our EOC.
I like UI-View very much after using it for the past week or so and
really getting to know its features, including those offered in the
add-ons like UIpath, UI-NWS, etc.
UIpath is a great add-on but lacks documentation/help (on the web or in
the program) and some has a few quirks (like stealing focus when
updating maps) that are an annoyance (to me) though they don't seem to
affect operability.
But I miss important features (to me) like PHG plotting, Range circles
with AZ/Dist to an object, DF plots, and other features that have not
been implemented as yet, so I go back to APRSdos time and again when I
need these features.
Also, when you view the APRS symbols page look in the lower right corner
and you will see that there is (and has been for a long time) a SkyWarn
symbol. I mention this because someone recently said there was no
SkyWarn symbol in APRS.
-----
And please would people stop including entire previous posts when
replying (when it has no relevance). It makes the subject difficult to
follow in digest mode, especially when two or three previous posts are
encapsulated in your reply. Can't we learn (or practice what we have
learned) to be more efficient communicators? When you post a 10 line
reply and include 50 lines from previous posts its not very efficient
nor does it make it easy to read.
Bob D.
N2IPH
----------------------------------------------------------------------
Subject: Columbia Lost Over Texas
From: docfester@mindspring.com
Date: Sat, 1 Feb 2003 09:36:59 -0500 (EST)
X-Message-Number: 16
CNN and other news agencies are reporting that the space shuttle Columbia
lost contact over Texas at 0900 ESt. The space shuttle was to land at
0916. People are reporting multiple trails over Texas and now are stating
that there is an impact zone in Texas.
KD4SFD
----------------------------------------------------------------------
Subject: Shuttle Emergency!!
From: "Rich Garcia" <k4gps@bellsouth.net>
Date: Sat, 1 Feb 2003 09:37:43 -0500
X-Message-Number: 17
Tune to the news.
At 9:15am it looks as if the shuttle was breaking up upon re-entry in the
Dallas area.
It's does not look good..But nothing is being released by NASA and NASA
select is off the air.
Rich
----------------------------------------------------------------------
Subject: Shuttle Lost update
From: docfester@mindspring.com
Date: Sat, 1 Feb 2003 10:14:05 -0500 (EST)
X-Message-Number: 18
For those with satellite tv, NASA select is still on air, for those who
want just NASA TV, but do not have Nasa Select, but have CSPAN, you can tune
into that, especially if you do not want to hear endless speculation from
the talking heads.
For those in the Dallas TX, if you have found debris, DO NOT APPROACH IT.
NOTIFY YOUR POLICE/FIRE IMMEDIATELY.
Les
KD4SFD
----------------------------------------------------------------------
Subject: Re: Thanks-Re: Unproto path ?
From: "Pat Karp" <pkarp@conwaycorp.net>
Date: Sat, 1 Feb 2003 10:19:05 -0600
X-Message-Number: 19
Thanks everyone for the responses. 8)
----------------------------------------------------------------------
Subject: Re: Shuttle Lost update
From: "Mark Fellhauer" <sparkfel@qwest.net>
Date: Sat, 01 Feb 2003 10:19:10 -0600
X-Message-Number: 20
Tragic News...
Someone correct me if I'm wrong, but Columbia is (was) our oldest shuttle,
first orbited in 1981 (4/12/81). Her "keel" was layed in 1975 and she flew
27 successful missions. I wonder if 22 years is too old for a machine to be
in space...
Regards,
Mark
KC7BXS
----------------------------------------------------------------------
Subject: RE: Input needed
From: Henk de Groot <henk.de.groot@hetnet.nl>
Date: Sat, 01 Feb 2003 17:00:52 +0100
X-Message-Number: 21
At 20:32 30-1-03 -0500, Ramon F. Kolb wrote:
>Just a question... If we use a different PID in AX.25, will this affect
>the "digipeatability" of the frame by (especially) "dumb" digi's, such
>as simple TNC's? I suspect that this is NOT the case, if I remember from
>the "old" (1980s) days that NET/ROM, IP, etc. frames are as well
>digipeated as a "text" frame. Right?
I guess so. But more advanged digipeates may have restriction because they
do more funny things to the packet's path than just simple digipeating.
DIGI_NED is more strict and only allows the PIDs for normal AX.25 (0xf0),
IP datagram (0xcc), ARP packets (0xcd) and NetRom (0xcf). Reason for this
is because messing with the path requires that you absolutely know that it
doesn't do harm. For packets other than normal AX.25 (0xf0) there is a
restriction, digipeating on SSID shall not be done, the destination SSID
should obviously not be changed for IP, ARP and NetRom packets or funny
things happen (for these packets the destination is a real target address,
changing the SSID just destroys the adressing).
WIth the default configurstion DIGI_NED also restricts the packet lenght to
the absolute maximum that the TH-D7 can handle, to avoid that they lock up
on long packets and keep working. This works very well, but for this only
normal AX.25 (0xf0) can be accepted. IP, ARP and NetRom packets should not
be truncated of course, it will not work correct and damage the data. Note
that no APRS packet should be that long, so truncating those to a safe
lenght will worse case just cut some of the excessive comment text. Better
that than hangup every TH-D7 in the area where the packet is broadcasted.
I have no idea how other digis do it, but due to the nature of how
digipeating works in APRS I expect that they only allow packed with
PID=0xf0 for all the advanged digipeating.
Of course when a new PID is assigned to a new APRS protocol, I will add it.
Note also that when it is a binary format a normal TNC might be able to
digipeat, but how to identify the station. They cannot send a status in
this new format. In fact such a standalone TNC can only generate packets
with PID=0xf0.
The only feasible solution I see is to use the TNC's in KISS and use an
external device (simple controller, PDA or of course a PC) to handle
digipeating; or design new TNC's for this.
Frankly the only feasible solution I see is to use the existing APRS and
have a new identifier for the binary format. For example every packet could
start with the top bit of the first data-byte set (first byte after the
PID) followed by the binary content. Existing implementations will ignore
this data since all start bytes in existing APRS are in the range 0x00 to
0x7f. This way you can slowly move over to a new protocol.
Of course the real question is what benefit a new protocol has. I can think
of some good reasons but they have to be very big step forward before
people switch. In the real world it is very hard to change a well
estiblished protocol. For example TCP/IP is not the most briliant protocol,
there is on official OSI protocol, used by for example Digital Equipment
Corporation, that is about 4 times faster and has a better layering than
TCP/IP. Still it did not survive on big scale due to the alreadly long
standing TCP/IP standard. TCP/IP was not designed by a standarisation
committy but just disigned and add on and became defacto standard and is
good enough for most networking. IP V6 now expands on that instead of
designing something new. I think for APRS it should be the same; extend to
add things that can not be done today, just like IP V6 brought mobility to
TCP/IP that was not possible with IP V4.
Kind regards,
Henk.
----------------------------------------------------------------------
Subject: RE: New spec - working notes
From: Henk de Groot <henk.de.groot@hetnet.nl>
Date: Sat, 01 Feb 2003 17:07:27 +0100
X-Message-Number: 22
At 21:25 30-1-03 -0500, Bob Bruninga wrote:
>To my knowledge, every client program supports it including the Kenwoods.
>So if someone wants to build a tracker to transsmit it, then all existing
>stuff should receive it. And it should be doable in a PIC...
I think WinAPRS is the only one that doesn't, but maybe that knowledge is
outdated. If so, then start using compressed mode!
DIGI_NED includes a decoder for compressed packets to calculate distance to
the station for DX, so no problem there to start using it. Designing the
beacon is of course a little more work since it is not directly readable
but can be done also (just like MIC-E for that matter). Just look the
algotithm up in the APRS Spec and use a calculator and ASCII table to do it.
Kind regards,
Henk.
----------------------------------------------------------------------
Subject: Re: New spec - working notes
From: Henk de Groot <henk.de.groot@hetnet.nl>
Date: Sat, 01 Feb 2003 17:20:20 +0100
X-Message-Number: 23
At 01:14 31-1-03 -0600, M. Schneider wrote:
>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.
If the new format is a binary format then the client needs to process it
anyway, the binary rubish will not be human readable anyway.... So it that
case I would say go wih ISO standards. Of course I would not mind to go to
"mm" rain, "km/h" speed and degrees centigrade temperature for a readable
format...
Last year we changed from Dutch Guilders to Euro's and everybody here
experienced first hand its very hard to change a unit of measure. A lot of
people still convert Euro values back to Guilders to know how much
something costs. I try to avoid this but even I do this. On the other hand,
our understanding of the value of a Dollar raised a lot since the Euro and
US Dollar have a similar value...
Kind regards,
Henk.
----------------------------------------------------------------------
Read previous mail | Read next mail
| |