| |
ZL3AI > APRDIG 04.07.03 09:12l 280 Lines 11437 Bytes #999 (0) @ WW
BID : 1564-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jul 01, 3/4
Path: DB0FHN<DB0RGB<DB0MRW<OK0PKL<OK0PPL<DB0RES<ON0BEL<VK7AX<ZL2BAU<ZL3VML
Sent: 030703/1331Z @:ZL3VML.#80.NZL.OC #:3659 [Chch-NZ] FBB7.00i $:1564-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Please Write!
From: Stan Horzepa <stanzepa@earthlink.net>
Date: Tue, 01 Jul 2003 20:24:55 -0400
X-Message-Number: 17
Here is your chance to become rich and famous! Well, maybe not rich, but
certainly famous.
The editorial board of Packet Status Register (PSR, TAPR's quarterly
newsletter) is now soliciting articles, news items, etc. for the next issue
of the newsletter. Topics related to digital Amateur Radio will be given
preference and the editorial board reserves the right to determine what is
suitable for publication.
E-mail your contributions to wa1lou@tapr.org ASAP because the deadline for
the next issue of the newsletter is July 24.
[commercial content deleted]
73,
Stan Horzepa, WA1LOU, PSR Editor
----------------------------------------------------------------------
Subject: American Solar Challenge & APRS
From: Bruno Quesnel <va2bmg@ve2.ele.etsmtl.ca>
Date: 01 Jul 2003 21:03:05 -0400
X-Message-Number: 18
Hi To all,
This year, one competition that will involve Solar powered cars &
university that designs them will be held between July 13th to 23rd.
The main site is www.americansolarchallenge.org.
This year, one of Montreal team will be followed with APRS from
Montreal to Chicago which is the start of the race. The race will cover
the Chicago,IL to Claremont, CA. Tracking will be done with APRS and
maps will be available on the school team web site. The web site is as
following : http://ve2.ele.etsmtl.ca and follow the links to Eclipse V.
For now, the maps are snapshot of FindU maps that traks the station
callsign (VE2ETS-9). If you are interested by this project, please
visit either of the different sites of the respective teams and
university.
--
Bruno Quesnel <va2bmg@ve2.ele.etsmtl.ca>
----------------------------------------------------------------------
Subject: Re: MObile APRS services
From: Gerry Creager N5JXS <gerry.creager@tamu.edu>
Date: Tue, 01 Jul 2003 20:35:38 -0500
X-Message-Number: 19
Er... you have to be old enough to recall when repeaters were novel.
The recommendation in question hasn't changed since then.
When I first started playing with 'em, repeaters didn't enjoy the
stellar sites a lot of them do today, and a fixed station who was on 2m
FM, likely as not, had as good a signal as the repeater. Hence:
encourage the mobiles to use the repeater, tell the bases to talk to
them direct or move 'em to 146.52. Not too many of the folks I knew
then bought that theory, either.
gerry
--
Gerry Creager -- gerry.creager@tamu.edu
Network Engineering -- AATLT, Texas A&M University
Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.847.8578
Page: 979.228.0173
Office: 903A Eller Bldg, TAMU, College Station, TX 77843
----------------------------------------------------------------------
Subject: RE: American Solar Challenge & APRS
From: "Martin Maxwell" <maxwell679@cox.net>
Date: Tue, 1 Jul 2003 18:49:18 -0700
X-Message-Number: 20
Will they come through AZ?
Martin
N7HAB
----------------------------------------------------------------------
Subject: CTCSS & CU2QSO (simplex APRS for contesters)
From: "Ev Tupis (W2EV)" <w2ev@arrl.net>
Date: Tue, 01 Jul 2003 22:12:51 -0400
X-Message-Number: 21
Preface: Imagine APRS without digipeaters, and where the only signals being
transmitted are from mobiles. Those mobiles happen to find hilltops to
park on and operate for several hours, before hitting the road again in
search of the next high spot. Home stations only lurk...no TXing unless
done manually.
This is "CU2QSO" (an outcrop of the BEACONet project) and it operates on
147.585 FM simplex during VHF contests. With that in mind...
>AH, but Ev, remember, the only reason this works is because the Kenwood
>TNC is tapped off the discriminator before the CTCSS and Squelch circuits,
>Thus the Radio can have CTCSS to squelch all packet noise, yet still let
>voice through. A normal packet set up connected to the speaker cannot do
>this or the TNC wont hear anything...
Aren't the FT-1500m and FT-2600m transceivers configured in a way to allow
a TNC to be connected, while keeping the microphone attached for voice
QSO's? (I ask out of ignorance).
How cool would it be to have a Rover pop-up on your computer screen, and
all you needed to do is pick up your CTCSS-enabled transceiver's mic and
give 'em a call right on 147.585?!?
This seems to be predicated on these transceivers functioning as you
mention above. Am I missing anything? I think your idea is very cool, and
am trying to exploit it for an entirely new audience.
Ev, W2EV
----------------------------------------------------------------------
Subject: Re: MObile APRS services
From: Alex <kr1st@amsat.org>
Date: Sun, 29 Jun 2003 04:37:40 -0400
X-Message-Number: 22
Bob Bruninga wrote:
>The "voice packet" takes under 4
>seconds total and only QRM's about a 5 mile radius.
Yes, you can give it a cute name like "voice packet" to make it sound
more acceptable, it's still wrong. The problem in this whole scheme is
that you, Bob Bruninga, have declared that it is OK to QRM a digital
signal on a de facto digital frequency with a voice mode. That is what
makes it it bad amateur radio practice. Intentional interference is
never ok unless perhaps in an emergency situation, no matter how long
the interference lasts.
>One has to keep things in
>persepective. The concept is... "W3ABC, voice-alert. What freq U on?"
>and the "ack" is "146.94 QSY!"
A conversation is not ok, but a call to QSY is, according to the
concept. Why is another operator allowed to make the decision that it is
perfectly fine to intentionally QRM my telemetry packet on a digital
frequency with a voice transmission? What gives this operator that
right? Bob Bruninga's blessing?
The question is simple and fundamental, why would intentional QRM be
allowed at all? This needs to be put in the *right* perspective, not
just *a* perspective that only serves the purpose of supporting a
desired effect or goal.
Let's try it the other way around. I mean, if you want a nice radar
system, then why not simply move mobile APRS operations to 146.52? As
soon as your squelch breaks (not even a PL is needed!) with some packet
racket you know that a fellow ham is nearby. Not only would this
attract the attention of fellow APRSers, but any other ham that may be
monitoring this frequency. The QRM would only last for about half a
second and only within 5 miles. No-one could object to such a use of
146.52 I would think.
73,
--Alex KR1ST
----------------------------------------------------------------------
Subject: Re: MObile APRS services
From: Mark Earle <wa2mct@mearle.com>
Date: Tue, 01 Jul 2003 21:45:02 -0500
X-Message-Number: 23
Another aspect of this discussion is, it seems to be geared to Kenwood D700
users. There are a lot of us who do not use this particular radio. For
those with other configurations, this mode is much more difficult to
consider using, without causing (potentially) more interference, or,
missing a call, negating the benefit of this "service".
I prefer just to listen on 156.52 for voice calls if not in range of one of
the meany FM repeaters, or, use the scan function to monitor a repeater and
146.520.
>Bob Bruninga wrote:
>
>>The "voice packet" takes under 4
>>seconds total and only QRM's about a 5 mile radius.
) ) de WA2MCT Mark
( (
) ) You will be assimilated... oooh, coffee!!
_|****| http://www.findu.com/cgi-bin/find.cgi?wa2mct-8 Home
( | | http://www.findu.com/cgi-bin/find.cgi?wa2mct-9 Mobile
`|____| wa2mct@mearle.com wa2mct@juno.com www.mearle.com/mark
----------------------------------------------------------------------
Subject: voice alert system solution.
From: "Wes Johnston" <wes@johnston.net>
Date: Tue, 1 Jul 2003 22:45:38 -0400
X-Message-Number: 24
Kenwood needs to add a software function which will list the B side
frequency to your status on aprs... that way we can know what freq the voice
side of the radio is on.. and avoid using 144.39 for voice traffic. Of
course this option should be ON/OFF selectable via menu.
***************************
Now that there are two other mobiles in my town running voice alert, I find
it V.A. very useful to see when another guy is in his car. Since we usualy
frequent one or two local repeaters, it's an easy job to find the other
guy... just a matter of knowing he's in his car. The three of us here have
programmed our d700 radios with three main PM modes. (in no particular
order)..
PM1 = one minute beacon rate, PL tone 100.0hz, status is enroute, PTT Auto.
Used for listening not talking, general driving.
PM2 = one minute beacon rate, PL tone 100.0hz, status is enroute, PTT
MANUAL. This one used for talking on local repeater. It only TX's on 144.39
when I unkey from the other side of the radio. Prevents me from missing
random bits of QSO on voice repeater... instead I only miss an occasional
courtesey beep when I unkey.
PM3= 30 min beacon rate, PL tone NOT 100hz, status is off duty, PTT Auto.
Used when car is parked.. By using an off the wall PL tone in this mode,
people listening on 144.39 voice alert won't hear these packets. In other
words, when you are not in the car, I don't hear your packets because you
are not sending 100hz pl tone. I also run a random PL tone on my digipeater
at home so I can hear it's coverage when I'm bored riding around town -
thanks Jeff Brenton for that idea.
Extra credit bonus round:
PM4= beacon rate 0.2 minute, callsign set to ALERTx-y, status text set to my
callsign, BCN button NOT pushed (must do it manually after selecting PM4).
This one is used to quickly create an object on another station's GPS... ie
wreck or speed trap. Note that BCN mode is stored in the off position.
This gives you to option to change the callsign before TX'ing and also to
prevent false alerts going out on the air if you accidentally select PM4.
Also a good idea to set the callsign last when programming this PM mode....
that way when you call it up, if you hit MENU, the callsign is the first
item which pops up - and that makes for easy editing if needed.
Now I see this voice alert topic dragging out....
Bob says voice alert only screws up 5 miles around you, but it's ok b/c you
can setup a QSO by voice in 3 seconds. True, but voice alert can prevent a
digipeater from hearing a station 30 miles away... so voice alert *could*
qrm a 30 mile radius around a wide node.
Alex says voice alert kills the frequency b/c digipeaters are mostly using
software DCD and don't back off when voice is on the air... the wide nodes
don't hear any carrier in a person's voice and will not back off and operate
CDMA. He's right... but how often is voice alert used? Once or twice a
day? I wish I *only* lost two packets a day to hidden transmitter problems!
Guys, you are both right .... in my mind, the word would be common sense...
the average user should REALIZE that they are QRMing the network and keep
it's usage to an absoulte minmum.... a quick call on voice is sure safer
than trying to steer a car and keying in an aprs message on the mic. Lee
Dahlen kd4tqz is excluded from this b/c he's the only person I know who can
type 30 to 35 wpm on a kenwood mic and generally wears out the DTMF pad in 3
months <grin>
Wes
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
