| |
ZL3AI > APRDIG 05.05.07 07:56l 237 Lines 8848 Bytes #999 (0) @ WW
BID : 10100-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 34 #24, 1/5
Path: DB0FHN<DB0FOR<DB0SIF<HB9EAS<DB0FSG<DB0PV<OE5XBL<OE6XPE<IW2OHX<I0TVL<
DK0WUE<DB0RES<F5GOV<F4BWT<F6KMO<7M3TJZ<ZL2BAU
Sent: 070505/0543Z @:ZL2BAU.#79.NZL.OC #:46302 [Waimate] $:10100-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Today's Topics:
1. Re: Amateur spam (Chris Kantarjiev)
2. Tactical call signs (Stephen Brown Jr)
3. Re: Tactical call signs (Matt Werner)
4. Re: Tactical call signs (Curt, WE7U)
5. RE: KPC-9612 Loader (Robert Bruninga)
6. Wide-Area APRS Call-up Channel (Robert Bruninga)
7. Re: Tactical call signs (John Habbinga)
8. Re: Tactical call signs (Matt Werner)
9. Re: Wide-Area APRS Call-up Channel (Josh Freeman)
10. Re: Tactical call signs (Curt, WE7U)
11. RE: Tactical call signs (Herb Gerhardt)
12. Re: Tactical call signs (John Habbinga)
13. Re: Tactical call signs (Matt Werner)
14. Re: Tactical call signs (Matt Werner)
15. RE: Tactical call signs (Robert Bruninga)
16. Re: Tactical call signs (John Habbinga)
17. Re: Voice Alert (was: PL 100 on a base station) (Jan T. Pharo)
18. Re: Voice Alert (Jan T. Pharo)
19. Re: Tactical call signs (Matt Werner)
20. Re: Tactical call signs (John Habbinga)
21. Re: Tactical call signs (Eric Christensen)
22. Re: Tactical call signs (John Habbinga)
23. Re: Amateur spam (Eric Weber)
24. Re: Tactical call signs (Chris Rose)
25. RE: Voice repeater objects (Robert Bruninga)
26. Re: Tactical call signs (Matt Werner)
27. Re: Tactical call signs (Joel Maslak)
28. RE: Amateur spam (Dave Baxter)
29. ADMIN: RE: [aprssig] Amateur spam (Stan Horzepa, WA1LOU)
30. FW: Garmin Rino protocol (Robert Bruninga)
31. RE: "Local Info" confusion... (Robert Bruninga)
32. Re: FW: Garmin Rino protocol (Wes Johnston, AI4PX)
33. Re: Tactical call signs (Curt, WE7U)
34. Re: Tactical call signs (Curt, WE7U)
35. Re: Tactical call signs (Curt, WE7U)
36. Re: Tactical call signs (Curt, WE7U)
37. Re: Tactical call signs (Curt, WE7U)
38. Re: RE: "Local Info" confusion... (Keith VE7GDH)
----------------------------------------------------------------------
Message: 1
Date: Mon, 23 Apr 2007 10:50:55 -0700 (PDT)
From: Chris Kantarjiev <cak_at_dimebank.com>
Subject: Re: [aprssig] Amateur spam
It seems that a large portion of the spam I get these days contains email
addresses that are amateur call signs. Don't know if they're being mined
from the TAPR archives or somewhere else, but...
73 de chris K6DBG
------------------------------
Message: 2
Date: Mon, 23 Apr 2007 13:54:52 -0400
From: "Stephen Brown Jr" <stephen.brown75_at_gmail.com>
Subject: [aprssig] Tactical call signs
Are these legal on the APRS-RF network? For example, let's say I wanted my
igate to beacon on the RF network as "LNXIGT" or "ETNIGT", as long as I
inserted my callsign in the comments field would that satisfy ID
requirements? Would this be an acceptable practice? I've toyed with the idea
of changing it on my D7 as well to something like "LNXMOBL" or "LNXPRTBL"
tnx
Stephen
K1LNX
------------------------------
Message: 3
Date: Mon, 23 Apr 2007 13:04:35 -0500
From: "Matt Werner" <kb0kqa_at_gmail.com>
Subject: Re: [aprssig] Tactical call signs
I have done it and seen it done in northern Minnesota for digis, yes.
The callsign of the digi is listed in the beacon which goes out every
9 minutes or so.
We started doing it here after I witnessed it throughout Oklahoma. It
makes it much easier at quick glance to know where the digi is if you
are familiar with the area. If you're not then you still have the
lat/long...
------------------------------
Message: 4
Date: Mon, 23 Apr 2007 11:06:13 -0700 (PDT)
From: "Curt, WE7U" <archer_at_eskimo.com>
Subject: Re: [aprssig] Tactical call signs
On Mon, 23 Apr 2007, Stephen Brown Jr wrote:
>Are these legal on the APRS-RF network? For example, let's say I wanted my
>igate to beacon on the RF network as "LNXIGT" or "ETNIGT", as long as I
>inserted my callsign in the comments field would that satisfy ID
>requirements? Would this be an acceptable practice? I've toyed with the idea
>of changing it on my D7 as well to something like "LNXMOBL" or "LNXPRTBL"
Yep. Legal. Not only that, you can even identify in Morse code every 10
minutes and keep everything tactical. That satisfies the FCC
identification rules. Of course that last would probably be considered bad
practice, but it's certainly allowed.
Also, you don't have to identify with the same path or even any path at
all, so your FCC identification w/callsign can be simplex w/no digipeater,
while the rest of the packets could be 2 or 3 hops. Again, probably not
best practice, but legal.
I think most on here suggest that you DO put your real callsign in your
comment or status packets, and then of course make sure those packets go
out at least every ten minutes.
--
Curt, WE7U. APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
------------------------------
Message: 5
Date: Mon, 23 Apr 2007 14:09:35 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] KPC-9612 Loader
Apparently the KPC-9612 (non-plus) can only be a first-hop WIDE1-1 digi and
a cross-baud 9600-to-1200 baud digipeater. It does not digipeat on its
MYNODE as I had hoped below.
>-----Original Message-----
>>port 1 is 144.390 _at_ 1200 and Port 2 is 430.100 _at_ 9k6.
>
>...It has none of the special APRS digipeating modes,
>...set it up as a WIDE1-1 fill in digi only.
>
>MYALIAS WIDE1-1
* MYNODE WIDE2-2 <== this does not work
>BTEXT !DDMM.hhN1DDDMM.hhW#W1,W2 only. comments
>B E 10
>UNPROTO AP9612
>MYGATE WIDE1-1
>
>...The above settings will allow it to do these things:
>1) Beacon its position every 10 minues DIRECET only
>2) It will digipeat only the first hop (W1-1)
>3) It will gateway 9600 baud packets to 1200 baud
>4) It will appear as s DIGI icon with an overlay of "1"
>
>Tell all mobiles in the area to use the path of VIA
>WIDE1-1,WIDE2-1 if your area is a 2 hop area. If it
>permits 3 hops then they use VIA WIDE1-1, WIDE2-2.
>
>9600 baud users on the UHF channel should also use
>WIDE1-1,WIDE2-2 and they will be cross linked from UHF at
>9600 to the 144.39 at 1200
------------------------------
Message: 6
Date: Mon, 23 Apr 2007 14:22:10 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: [aprssig] Wide-Area APRS Call-up Channel
Wide-Area APRS Call-up Channel:
This system allows for instant back-channel contact to all APRS operators
no matter what they are doing with Band B. Band A of coruse is doing APRS
and is monitoring Voice Alert.
If you live in a wide area, where most APRS folks are not all in the same
club and are not all monitoring the same general repeaters, you can set up
a Wide-Area APRS Call-up channel for instant call-up throughout the region.
Simply put up a tall central cross band repeater that listens on an unused
UHF channel (PL 100) and cross bands to APRS Voice Alert on 144.39 (PL100).
In effect this extends the range of Voice Alert from Simplex to wide area.
Of course this must not be abused, and only used for brief contact
(emergency call-up, then QSY).
It may meet your area emergency response needs and may be worth doing. But
if two guys use it everyday to make contact, it might be detrimental, since
it will cause people to turn down their VoiecAlert and then that system is
disfunctional.
Anyway, it you need a means for wide-area-call-up of all APRS mobiles (that
are running Voice-Alert), it is pretty easy to do, and requires no change
in routine by the APRS operators.
Bob, WB4APR
------------------------------
Message: 7
Date: Mon, 23 Apr 2007 13:42:51 -0500
From: "John Habbinga" <kc5zrq_at_gmail.com>
Subject: Re: [aprssig] Tactical call signs
This might be legal as long as you don't setup your path for digipeating
and you don't use APRS messaging through an I-Gate to RF.
>Yep. Legal. Not only that, you can even identify in Morse code
>every 10 minutes and keep everything tactical. That satisfies the
>FCC identification rules. Of course that last would probably be
>considered bad practice, but it's certainly allowed.
------------------------------
Message: 8
Date: Mon, 23 Apr 2007 13:48:19 -0500
From: "Matt Werner" <kb0kqa_at_gmail.com>
Subject: Re: [aprssig] Tactical call signs
Neither of those would affect the legalities of it.
If it's digipeated then it's 3rd party traffic and the digipeater is
responsible for IDing itself. Same goes for an I-Gate.
On 4/23/07, John Habbinga <kc5zrq_at_gmail.com> wrote:
>This might be legal as long as you don't setup your path for digipeating and
>you don't use APRS messaging through an I-Gate to RF.
>
>>Yep. Legal. Not only that, you can even identify in Morse code
>>every 10 minutes and keep everything tactical. That satisfies the
>>FCC identification rules. Of course that last would probably be
>>considered bad practice, but it's certainly allowed.
------------------------------
Read previous mail | Read next mail
| |
