OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   07.02.03 12:01l 272 Lines 9329 Bytes #999 (0) @ WW
BID : 860-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 04, 1/3
Path: DB0FHN<DB0RGB<DB0SL<DB0FSG<DB0GAP<DB0GPP<DB0LX<DB0CZ<DB0GE<LX0PAC<
      LX0HST<HA3PG<HB9OK<IR0NET<VK3TE<ZL2BAU<ZL3VML
Sent: 030206/0929Z @:ZL3VML.#80.NZL.OC #:58843 [Chch-NZ] FBB7.00i $:860-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

TAPR APRS Special Interest Group Digest for Tuesday, February 04, 2003.

1. QRZ.COM???
2. RE: QRZ.COM???
<LYR31120-118765-2003.02.04-00.20.36--kc2tn#comcast.net@lists.tapr.org>
3.  RE: QRZ.COM???
4. RE: Capabilities announcement
5. APRS SAR efforts in East TX
6. Re:  RE: QRZ.COM???
7. RE: APRS SAR efforts in East TX
8. Re: APRS SAR efforts in East TX
9. APRS / new protocol and ICS
10. Re: APRS SAR efforts in East TX
11. Re:  Xastir Up and Running ... Sort of
12. Re: Xastir Up and Running ... Sort of
13. RE: JAVA-capable Radio
14. KISS TNC nearly a digipeater...
15. Re: KISS TNC nearly a digipeater...
16. ARLB012 Texas amateurs aid in shuttle debris recovery, cataloging
17. FW: [Ham-Radio-News] (unknown)
18. Re: ARLB012 Texas amateurs aid in shuttle debris recovery,  cataloging
19. Re: KISS TNC nearly a digipeater...
20. Re: FW: [Ham-Radio-News] (unknown)
21. Re: KISS TNC nearly a digipeater...
22. Re: [Ham-Radio-News] (unknown)
23. A brief explanation
24. Re: Words of Warning
25. RE: FW: [Ham-Radio-News] (unknown)
26. ISS ?
27. RE: FW: [Ham-Radio-News] (unknown)
28. Etrex and Low temps

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

Subject: QRZ.COM???
From: Jim Duncan <jdbandman@earthlink.net>
Date: Mon, 03 Feb 2003 23:30:18 -0600
X-Message-Number: 1

What's happened to www.qrz.com???  (Sorry, I know it's off-topic, sort
of...)
-- 
73 de Jim, KU0G
Chairman/Coordinator
Kansas City APRS Working Group, W0APR
First Alert Storm Team KMBC-TV9
Mailto:ku0g@kcaprs.org
Webpage: http://www.kcaprs.org

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

Subject: RE: QRZ.COM???
<LYR31120-118765-2003.02.04-00.20.36--kc2tn#comcast.net@lists.tapr.org>
From: KC2TN <KC2TN@comcast.net>
Date: Tue, 04 Feb 2003 00:39:09 -0500
X-Message-Number: 2

They must be doing an upgrade or they lost a server???
I just lost it too.

Joe - KC2TN

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

Subject:  RE: QRZ.COM???
From: "Matthew Stennett" <wa4tkg@iwon.com>
Date: Tue,  4 Feb 2003 07:04:56 -0500 (EST)
X-Message-Number: 3

I'm on ComCast cable, and it's working fine now/for me.

07:05a.m.EST

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

Subject: RE: Capabilities announcement
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Tue, 4 Feb 2003 16:51:44 -0000
X-Message-Number: 4

>You might as well plan for DCSS (aka DCS, DPL) as well. It used, though 
>not widely.

Dang it, why can't this ever be easy?  =]  I knew I was going to get into
trouble here, trying to describe all this in one place.  I'll have to look
that up and see what it'll take to represent it.

>It might be wise to have a leading flag bit that makes this table 
>driven, or selects the full descriptor.  99-44/100 % of all cases will 
>probably fall into a couple of dozen basic categories.

Yeah, but it'd still need to support the full descriptor, so it's easier to
have an implementation do only the single format.  A user interface could
give you a drop-down menu with things like FM voice or SSB, with an option
to enter a full descriptor.  Likewise, a receiving device might have a
lookup table with a few common modes, so that it knows, for example, what
F3F is.

The intent here is to not necessarily describe every possible emission mode
conceivable, but to let you click on a station's map icon and see, for
example, that it's running sideband voice on 10 meters, or data on 20
meters, or whatever.  Or for a satellite, to have it announce what
transponders and beacons are operating.  You should be able to drive into an
unfamilliar area, and have your Kenwood D800 or whatever automatically learn
about all of the local repeaters.

I think a table lookup for bandwidth might be warranted... there's not a lot
of reason for a voice station to specify 5010 hz instead of 5000 hz, for
example.  The problem then becomes compiling a list of common bandwidths.

Blech.  I think I'm just going to aim for 98% or 99% coverage, and anything
else can go in a comment field.  =]

Scott / N1VG

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

Subject: APRS SAR efforts in East TX
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 4 Feb 2003 12:14:58 -0500 (EST)
X-Message-Number: 5

Using AE5PL's excellent WEB site, I zoomed into east texas and see a few
mobiles in the vicinity of Nacadoches and Lufkin, presumably helping in
the East Texas search for shuttle debris.

I bet there maybe more mobiles, but since there are no digipeaters in the
area, we probably cannot see them...  Setting up a few termporary digis
may help...  I see the IGate is in Lufkin, somewhat south.

One thing of note when using maps like these is the absence of the APRS
"range scale" to give the viewer a clue as to the distances involved on
the map view.  One thing I'd like to see (if not the APRS Range Scale
legend on every map) is a command key that would at least display 4
concentric circles of ranges as an aid to the viewer or some other simple
means of visually conveying distances on every map view.

I added a note on the errata page about the importance of Range Scales:
and an image of how APRSdos does it..

   http://web.usna.navy.mil/~bruninga/aprs/errata.html

Just something thats useful when presenting map displays to viewers...

Bob

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

Subject: Re:  RE: QRZ.COM???
From: "Mike Yetsko" <myetsko@insydesw.com>
Date: Tue, 4 Feb 2003 13:01:48 -0500
X-Message-Number: 6

>I'm on ComCast cable, and it's working fine now/for me.
> 
>07:05a.m.EST

We see this a lot on this forum.  QRZ has a hiccup and I guess some
people are addicted to it and panic.

Mike

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

Subject: RE: APRS SAR efforts in East TX
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Tue, 4 Feb 2003 12:37:30 -0600
X-Message-Number: 7

I have just set up a special page for viewing APRS activities in and
around the primary recovery area.  It is
http://www.aprs-is.net/ColumbiaSAR.htm

This page requires a Java enabled browser for viewing and uses highly
accurate and zoomable maps.  The stations you see will be updated via a
live feed in real-time.

73,

Pete Loveall AE5PL
pete@ae5pl.net

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

Subject: Re: APRS SAR efforts in East TX
From: Bill Owens <owens@nysernet.org>
Date: Tue, 4 Feb 2003 13:44:05 -0500
X-Message-Number: 8

At 12:14 -0500 2/4/03, Bob Bruninga wrote:
>Using AE5PL's excellent WEB site, I zoomed into east texas and see a few
>mobiles in the vicinity of Nacadoches and Lufkin, presumably helping in
>the East Texas search for shuttle debris.

I used a central-Texas javAPRS page to look at activity on saturday morning
but didn't see anything that looked unusual, though it would be difficult
to tell what a debris recovery operation really looked like. At that time
the news media were reporting that FEMA and NASA did not want volunteer
assistance, but given the report on the ARRL website that must have
changed. . .

Bill N2RKL

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

Subject: APRS / new protocol and ICS
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Tue, 4 Feb 2003 18:58:51 -0000
X-Message-Number: 9

I'm looking for input on:

- How APRS is used within the Incident Command System
- What ICS-specific features need to be supported
- Any good, complete references on ICS

I haven't been to an ICS training since SAR City '93 or so, and I think I
slept through part of that.  =]  What I'm looking for in particular is how
to associate stations with a particular incident, and to place them within
the ICS hierarchy.

Also, submitted for your review, is the latest addition to the proposed
protocol spec.  This message type is for reporting GPS signal quality, which
may be of interest for some applications.  Mapping debris fields, for
instance.  I know someone's going to bring up the fact that values over 25
are possible for dilution of precision, but from my experience, anything
over 7 isn't acceptable for mapping applications, and beyond 25 it's
probably not going to be much use for anything.

Filling this message out fully requires both GPGGA and GPGSA sentences to be
parsed, but that's why the last three fields are optional, and a 'not
available' type is provided for the fix type.

MSG #10 - GPS Data Quality

[Fix Type] 2 bits
[Validity] 2 bits
[Satellites] 4 bits
<PDOP> 8 bits
<HDOP> 8 bits
<VDOP> 8 bits

Values for Fix Type:

00 - Unknown / Not available
01 - No fix
02 - 2D fix
03 - 3D fix

Values for Validity:

00 - Invalid
01 - Valid SPS
02 - Valid DGPS
03 - Valid PPS

The Satellites field indicates the number of satellites in use, as reported
by the NMEA 0183 $GPGGA sentence.  PDOP, HDOP, and VDOP optionally indicate
the position, horizontal, and vertical dilution of precision, respectively.
DOP values are represented as integers equal to ten times the GPS-reported
DOP.  DOP values over 25.5 are reported as 255.

Example:

05 10 D8 19 0D 15 (Valid 3D GPS fix, PDOP = 2.5, HDOP = 1.3, VDOP = 2.1)

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



Read previous mail | Read next mail


 16.11.2026 03:58:12lGo back Go up