OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   18.04.03 11:53l 252 Lines 9163 Bytes #999 (0) @ WW
BID : 1170-ZL3AI
Read: GUEST
Subj: TAPR Digest, Apr 15, 1/4
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<SP7MGD<ZL3VML
Sent: 030417/1032Z @:ZL3VML.#80.NZL.OC #:64062 [Chch-NZ] FBB7.00i $:1170-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

TAPR APRS Special Interest Group Digest for Tuesday, April 15, 2003.

1. Re: Opening up the proverbial can o' worms
2. HF APRS Suggestion
3. Re: Hiking/Backpacking symbol...
4. Re: HF APRS Suggestion
5. aprs events calendar
6. aprs events calendar
7. Re: aprs events calendar
8. 802.11 APs
9. reducing hidden transmitter problems
10. Re:reducing hidden transmitter problems
11. Cool APRS idea
12. Re: Cool APRS idea
13. Re: Cool APRS idea
14. Re: reducing hidden transmitter problems
15. Re: reducing hidden transmitter problems
16. Re: Cool APRS idea
17. Re: HF APRS Suggestion
18. Re: Opening up the proverbial can o' worms
19. Re: HF APRS Suggestion
20. Re: HF APRS Suggestion
21. Re: HF APRS Suggestion
22. Re: HF APRS Suggestion
23. Re: Cool APRS idea
24. QSL Question
25. Re:QSL Question
26. Fw: Re:QSL Question
27. Re: HF APRS Suggestion
28. Re: HF APRS Suggestion

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

Subject: Re: Opening up the proverbial can o' worms
From: "Doug Younker" <dougy@ruraltel.net>
Date: Tue, 15 Apr 2003 00:58:47 -0500
X-Message-Number: 1

Thing is that the smaller Red Cross chapters rely on amateurs to provide
communications totally.  Yes even for them numbers initially should be
sufficient untill names could be delivered in another manner.--73
Doug, N0LKK
 dougy@ruraltel.net

----- Original Message -----
From: "Ronald Reams" <wa4mjf@worldnet.att.net>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Monday, April 14, 2003 6:45 PM
Subject: [aprssig] Re: Opening up the proverbial can o' worms

: I'm wonderin' what organization you're providin' commo
: for that wants you to send initial reports of death by name.
:
: It would seem that mumbers of dead and injured would
: be sufficient for most planners/decision makers.
:
: I'd leave it to the Red Cross or other competent organization,
: to get in to names of dead and/or injured persons.
:
: 73 de Ronnie

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

Subject: HF APRS Suggestion
From: "Ev Tupis (W2EV)" <w2ev@arrl.net>
Date: Tue, 15 Apr 2003 06:29:45 -0400
X-Message-Number: 2

What with the proliferation of digipeating and RF Bridging on 20 meters, it
is often difficult to know on what band a particular transmission
originated.  It makes things like propagation paths difficult to analyze.

There is hope.

Here is a 100% APRS-compatible solution.

Place a 2-byte "band designation" in your Destination Field.  Doing this
will allow users to automatically "filter" what is displayed (as an
ALTNET), by band of interest.  Don't want to filter?  Turn "ALTNET" off.
Easy, huh?

Examples below:

W2EV>VK,GATE,ECHO:.....
     ^^
In the case above, V=VHF, K=140-150 MHz.

W2EV>HK,...
     ^^
20-m: H=HF, K=14-15 MHz

W2EV>HY,...
     ^^
10m: H=HF, Y=28 MHz

W2EV>HG,...
     ^^
30m: H=HF, G=10-11 MHz

The full chart for a much more broad spectrum of RF is shown below.  Please
consider doing this.  If enough people do, I'll share other hints that can
further enhance HF APRS operation.

Ev, W2EV

==============================================================================
TABLE 1 -- Embedding Transmit Frequency [Band & Segment]
------------------------------------------------------------------------------
B->(B)ase (A)udio (X)tra  (L)ow  (M)ed.  (H)igh  (V)ery (U)ltra(S)uper  (E)xtr
S                    Low                           High    High   High    High
|
v
0   30-hz  300-hz  3-kHz  30-kHz 300-kHz  3-MHz  30-MHz 300-MHz  3-GHz  30-GHz
A   40-hz  400-hz  4-kHz  40-kHZ 400-kHz  4-MHz  40-MHz 400-MHz  4-GHz  40-GHz
B   50-hz  500-hz  5-kHz  50-kHz 500-kHz  5-MHz  50-MHz 500-MHz  5-GHz  50-GHz
C   60-hz  600-hz  6-kHz  60-kHz 600-kHz  6-MHz  60-MHz 600-MHz  6-GHz  60-GHz
D   70-hz  700-hz  7-kHz  70-kHz 700-kHz  7-MHz  70-MHz 700-MHz  7-GHz  70-GHz
E   80-hz  800-hz  8-kHz  80-kHz 800-kHz  8-MHz  80-MHz 800-MHz  8-GHz  80-GHz
F   90-hz  900-hz  9-kHz  90-kHz 900-kHz  9-MHz  90-MHz 900-MHz  9-GHz  90-GHz
G  100-hz 1000-hz 10-kHz 100-kHz   1-MHz 10-MHz 100-MHz   1-GHz 10-GHz 100-GHz
H  110-hz 1100-hz 11-kHz 110-kHz 1.1-MHz 11-MHz 110-MHz 1.1-GHz 11-GHz 110-GHz
I  120-hz 1200-hz 12-kHz 120-kHz 1.2-MHz 12-MHz 120-MHz 1.2-GHz 12-GHz 120-GHz
J  130-hz 1300-hz 13-kHz 130-kHz 1.3-MHz 13-MHz 130-MHz 1.3-GHz 13-GHz 130-GHz
K  140-hz 1400-hz 14-kHz 140-kHz 1.4-MHz 14-MHz 140-MHz 1.4-GHz 14-GHz 140-GHz
L  150-hz 1500-hz 15-kHz 150-kHz 1.5-MHz 15-MHz 150-MHz 1.5-GHz 15-GHz 150-GHz
M  160-hz 1600-hz 16-kHz 160-kHz 1.6-MHz 16-MHz 160-MHz 1.6-GHz 16-GHz 160-GHz
N  170-hz 1700-hz 17-kHz 170-kHz 1.7-MHz 17-MHz 170-MHz 1.7-GHz 17-GHz 170-GHz
O  180-hz 1800-hz 18-kHz 180-kHz 1.8-MHz 18-MHz 180-MHz 1.8-GHz 18-GHz 180-GHz
P  190-hz 1900-hz 19-kHz 190-kHz 1.9-MHz 19-MHz 190-MHz 1.9-GHz 19-GHz 190-GHz
Q  200-hz 2000-hz 20-kHz 200-kHz 2.0-MHz 20-Mhz 200-MHz 2.0-GHz 20-GHz 200-GHz
R  210-hz 2100-hz 21-kHz 210-kHz 2.1-MHz 21-MHz 210-MHz 2.1-GHz 21-GHz 210-GHz
S  220-hz 2200-hz 22-kHz 220-kHz 2.2-MHz 22-MHz 220-MHz 2.2-GHz 22-GHz 220-GHz
T  230-hz 2300-hz 23-kHz 230-kHz 2.3-MHz 23-MHz 230-MHz 2.3-GHz 23-GHz 230-GHz
U  240-hz 2400-hz 24-kHz 240-kHz 2.4-MHz 24-MHz 240-MHz 2.4-GHz 24-GHz 240-GHz
V  250-hz 2500-hz 25-kHz 250-kHz 2.5-MHz 25-MHz 250-MHz 2.5-GHz 25-GHz 250-GHz
W  260-hz 2600-hz 26-kHz 260-kHz 2.6-MHz 26-MHz 260-MHz 2.6-GHz 26-GHz 260-GHz
X  270-hz 2700-hz 27-kHz 270-kHz 2.7-MHz 27-MHz 270-MHz 2.7-GHz 27-GHz 270-GHz
Y  280-hz 2800-hz 28-kHz 280-kHz 2.8-MHz 28-MHz 280-MHz 2.8-GHz 28-GHz 280-GHz
Z  290-hz 2900-hz 29-kHz 290-kHz 2.9-MHz 29-MHz 290-MHz 2.9-GHz 29-GHz 290-GHz
==============================================================================

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

Subject: Re: Hiking/Backpacking symbol...
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 15 Apr 2003 09:47:01 -0400 (EDT)
X-Message-Number: 3

On Mon, 14 Apr 2003, Jeffrey P. Nast wrote:

>I don't see a standard APRS symbol for "Backpacking/Hiking" in either
>the primary or alternate symbol table. Any room for one that would
>resemble the hiking symbol found here:
>http://www.wy.blm.gov/cyfo/rec/rec.htm

That was supposed to be what the "runner" or "jogger" symbol is for.  It
is also for "hiker"..  We made sure it was one of the 16 supported by the
Kenwoods too...

Bob

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

Subject: Re: HF APRS Suggestion
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 15 Apr 2003 10:09:18 -0400 (EDT)
X-Message-Number: 4

On Tue, 15 Apr 2003, Ev Tupis (W2EV) wrote:

>What with the proliferation of digipeating and RF Bridging on 20 meters,
>it is often difficult to know on what band a particular transmission
>originated.
>
>Here is a 100% APRS-compatible solution.
>Place a 2-byte "band designation" in your Destination Field.  Doing this
>will allow users to automatically "filter" what is displayed (as an
>ALTNET), by band of interest.  Don't want to filter?  Turn "ALTNET" off.
>Easy, huh?

Problem is, that ALTNET is exclusive.  That is, if you set to an ALTNET of
"HK" then the only thing you will receive is other "HK" stations and no
others.  ALTNET is not a "display" option, but an exclusive filter option.

But if you put APHK as an "ALTNET" then, because it begins with the
standard "AP", everyone will reveive it because it is in the general APRS
network category and then you can "select" to display or sort by the next
two bytes which will let you then see only the "APHK" stations for
example...

Bob

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

Subject: aprs events calendar
From: wes@johnston.net
Date: Tue, 15 Apr 2003 10:47:39 -0400 (EDT)
X-Message-Number: 5

OK, I revamped the site from yesterday and added a calendar. 
wes.johnston.net/aprs

It supports:
1) Reoccurring events

2) filtering of events (only see server downtime if that's all you
interested in)

3) text list and regular calendar grid format.

4) searchable

5) It can send email reminders to you for events (don't wanna forget dayton!)

Any fields that are missing, let me know.

Wes

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

Subject: aprs events calendar
From: wes@johnston.net
Date: Tue, 15 Apr 2003 12:07:40 -0400 (EDT)
X-Message-Number: 6

Anyone wishing to include the aprs events calendar in thier home page may
do so with this link...
http://aprs.optic-solutions.com/cgi-bin/calendar/calendar.cgi?fromTemplate=logih
n.tml&template=default.html&view=Four-Week&command=login&username=radio&passworr
d=adio

For example, you could include it in an iframe.....

<iframe name="mapI" ID="mapI" width=100% height=85%
src="http://aprs.optic-solutions.com/cgi-bin/calendar/calendar.cgi?fromTemplateo
=lgin.html&template=default.html&view=Four-Week&command=login&username=radio&paw
ssord=radio" frameborder=0 marginheight=0 marginwidth=0 scrolling="yes">

In this way, everyone's aprs calendar would pull from the same source.
Maybe someone has a domain which is easier to remember than mine?

Wes

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




Read previous mail | Read next mail


 15.11.2026 03:18:12lGo back Go up