| |
ZL3AI > APRDIG 26.05.03 22:05l 245 Lines 9671 Bytes #999 (0) @ WW
BID : 1385-ZL3AI
Read: GUEST
Subj: TAPR Digest, May 23, 3/5
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<ZL2BAU<ZL3VML
Sent: 030525/1338Z @:ZL3VML.#80.NZL.OC #:940 [Chch-NZ] FBB7.00i $:1385-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Digi-ing?
From: Jim Sanford <wb4gcs@amsat.org>
Date: Fri, 23 May 2003 11:09:09 -0400
X-Message-Number: 15
TC:
Relay and Wide are generic digi callsigns.
From the hip, Relay is for the typical base station with "moderate"
coverage. WIDE is for the carefully constructed wide-area coverage digi.
Whether a given installation is a relay or wide is best coordinated with
the local group, 2 wides too close together actually hurt channel
throughput.
I'd guess from your email that you didn't set the UIDIGI callsign, which
is why the 700 isn't doing anything. You have 3 choices:
one of your calls (if this is an up and down or "private" or temporary use)
relay
wide (as discussed above)
UIDIGICALL is in the APRS menu on the 700, and is a SEPARATE item from
UIDIGI ON/OFF
At various occasions, I've used my D700 as a relay, or with my call on
it for use with D7s in a specific event without corrupting the local
network for other users. Works GREAT.
Hope this helps, good luck.
73,
Jim
wb4gcs@amsat.org
----------------------------------------------------------------------
Subject: Re: Digi-ing?
From: Wes Johnston <wes@johnston.net>
Date: 23 May 2003 11:17:54 -0400
X-Message-Number: 16
It's a two part thing... the kenwood has to be set to TX over "some path",
and the digipeater nearest you has to have one of the names listed in your
path programmed into it.
In this example, set your kenwood's path to RELAY (only the word RELAY)
Set the digipeater up with the command MYALIAS RELAY .
When you transmit a position report, the nearest digipeater to you which is
programmed to respond to RELAY will repeat your packet. Your kenwood radio
will beep and show "my pos" on the display indicating that you were heard
and digipeated.
It is possible to program digipeaters to respond to many names used in the
path... such as WIDE and WIDE2-2 and TRACE and GATE... but that's a lesson
for another day. Usually, a "filler" digipeater like you are trying to
setup ONLY responds to RELAY. All big boy digi's respond to RELAY and
WIDE. It's a sort of hierarchy. Generally speaking, the taller your digi,
the more "names" it responds to.
In the olden days of packet, you had to specify the actually callsign of
the digipeater(s) you wanted your packet to travel thru on the way to it's
destination. Digipeaters then , and now only respond to the first callsign
in your path which does not contain an asterisk.
For example, if you sent out a packet like this:
K4LID>APRS V KD4RDB-1, KR4FT-1
and my station (rdb-1) heard that packet it would digipeat it like this:
K4LID>APRS V KD4RDB-1*, KR4FT-1
Then and ONLY then if kr4ft-1 heard the packet, he would digipeat it
like this:
K4LID>APRS V KD4RDB-1*, KR4FT-1*
The problem with this system is that you need to know the callsigns of
all the digipeaters. AND they have to hear the packet in the right
order. What if kr4ft heard the packet the first time, and kd4rdb-1
didn't? kr4ft-1 would never digipeat the packet because it didn't think
it was it's turn yet. The packet would never get digipeated.
Bob Burninga came up with the GREAT FABULOUS idea of naming all the
digipeaters the SAME THING... RELAY. So now when you transmit a packet,
you send it out like this:
K4LID>APRS V RELAY, RELAY (don't use this on the air... this is only an
example).
Since both kr4ft-1 and kd4rdb-1 are programmed to respond to the fake
callsign RELAY, it won't matter which of them hears it first, that
digipeater will think it has exclusive rights to that packet and will
digipeat it.
So if you are nearer to kd4rdb's station.... and TX that packet....
K4LID>APRS V RELAY, RELAY
it comes out as
K4LID>APRS V kd4rdb-1*, RELAY
and them kr4ft hears it, and digipeats it too....
K4LID>APRS V kd4rdb-1*, kr4ft-1*.
Everyone near to kr4ft and kd4rdb has now heard your position.
If you are on the other side of town, nearer to kr4ft, the SAME packet
will go like this:
K4LID>APRS V RELAY, RELAY
K4LID>APRS V kr4ft-1*, RELAY
K4LID>APRS V kr4ft-1, kd4rdb-1*
Everyone near to kr4ft and kd4rdb has now heard your position.
By using generic names, you can transmit a packet from any location, in
any town without regard for changing your path.
There is an order to this though.... generally, if your packet can be
digipeated by teh tallest digipeater in your area, everyone in your town
will hear it. This is where a lot of new people have a misconception.
They think that they must transmit their position TO every station when
in fact, they may only need to bounce it off one local guy's house to
the tallest digipeater. Once the tallest digipeater has "spoken"
everyone has received a copy of the packet. Never put the word RELAY in
your path unless it's in the first position.
In the above example, I transmitted a packet that traveled thru two
stations. But if you used the path RELAY, WIDE this would happen....
K4LID>APRS V RELAY, WIDE
K4LID>APRS V kd4rdb-1*, WIDE
K4LID>APRS V kd4rdb-1*, k4big* (k4big is the tallest digi in your town)
Now, EVERYONE has heard your packet. kr4ft-1 heard it too, but since the
word RELAY wasn't in there, it did not digipeat the packet - besides
there was no need.... everyone in town already heard a copy of it.
Once again, if you were on the other side of town,
K4LID>APRS V RELAY, WIDE
K4LID>APRS V kr4ft-1*, WIDE
K4LID>APRS V kr4ft-1*, k4big*
Now, EVERYONE has heard your packet - and it didn't have to use the
digipeaters at both ham's houses.... it just uses the nearest one to you
as a springboard to get to the local tallest digipeater.
Now let's say that you are north of town, and out of range of the two
home stations in the other examples.... you transmit a packet like this:
K4LID>APRS V RELAY, WIDE
and only the local tallest digipeater hears you. Because the tallest
digipeater is programmed to respond to RELAY or WIDE, it will digipeat
your packet like this:
K4LID>APRS V k4big*, WIDE
Now it is possible that the tallest digipeater in the next town will
hear this packet and see that WIDE hasn't been used up yet, so it will
also digipeat....
K4LID>APRS V k4big*, n8twn*
Now everyone in two towns has heard your packet. Now consider that a
WIDE digipeater can usually hear it's neighboring WIDE digipeaters.
Let's just say that there are 4 WIDE digipeaters 25 miles north south
east and west of your town.
Each of those digipeaters hears your packet via k4big and sees the
unused WIDE callsign. Each of them thinks that it has precedence over
that packet, and each one digipeats it at the same time.
So your packet which started as
K4LID>APRS V RELAY, WIDE
was heard in your local town as
K4LID>APRS V k4big*, WIDE
and _that_ packet was heard by 4 other WIDE digipeaters in four towns
and all of them created these 4 packets....
K4LID>APRS V k4big*, k8north*
K4LID>APRS V k4big*, k4south*
K4LID>APRS V k4big*, n5west*
K4LID>APRS V k4big*, n2east*
Now you have been heard by every station in 5 towns with a simple
RELAY,WIDE path in your kenwood radio. Do *not* get overzealous and
think you can ever put three WIDE's in a row... Never never, not ever do
you put three of any name in a row in your path.
This should get you started.
Wes
----------------------------------------------------------------------
Subject: RE: Broadband on Power --City(not FCC) enforces radio law and busts
CBer
From: "Mark Fellhauer" <sparkfel@qwest.net>
Date: Fri, 23 May 2003 10:39:39 -0500
X-Message-Number: 17
At 05:20 AM 5/23/2003, WA8LMF2@aol.com wrote:
>James A. Disbennet, 48, 427 Harrison Ave., is charged with operating a CB
>radio exceeding 4 watts, a first-degree misdemeanor, and two counts of
>operating
>a CB radio without certification, a fourth-degree misdemeanor. Disbennet,
>whose handle is "Sugar Bear," answered a summons in Fairfield County
>Municipal
>Court last Tuesday and was released on a recognizance bond.
Maybe Kraft Foods/Post Cereals should go after him for copyright
infringment for his handle? :)
"Can't get enough of that Sugar Crisp...Oh sorry, super GOLDEN Crisp..."
Mark
KC7BXS
----------------------------------------------------------------------
Subject: Re: Voice Alert on 144.39
From: Bill Vodall <wa7nwp@jnos.org>
Date: Fri, 23 May 2003 08:51:17 -0700
X-Message-Number: 18
At 07:48 AM 5/23/03 +0600, Ramsay D. Seielstad, KC2GMW wrote:
>I have also read of FCC enforcement actions being initiated against
>amateurs for not observing band plans, which I believe someone mentioned
>the APRS frequency is recognized in the band plan as a digital data
>frequency.
Riley (?) sent letters to folks carrying on extended conversations on the
calling frequency of 146.52. He later essentially apologized with the
statement that "band plans" are a matter of good manners, not law.
Carrying on an extended voice conversation on 144.39 MHz would be,
just like on 146.52, inconsiderate but not illegal. (At least in the U.S.)
> We, as amateurs, have plenty of 6m, 2m, 220 & 440 mhz simplex and repeater
>frequencies going unused for voice at all times of the day and night, but
>only one frequency for APRS data that is constantly being utilized.
The first comment about the vast range of amateur spectrum going unused is
certainly true. We have one (inter)national base frequency for APRS data.
There is no reason not use some of the other underutilized channels for
local APRS activity. It's easy and it opens the mode up to many more
functions when you're not faced with the inherent bandwidth limitations of
1200 baud and digipeaters.
73,
Bill - WA7NWP
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
