| |
ZL3AI > APRDIG 29.05.03 09:06l 230 Lines 9826 Bytes #999 (0) @ WW
BID : 1399-ZL3AI
Read: GUEST
Subj: TAPR Digest, May 26, 1/4
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<ZL2BAU<ZL3VML
Sent: 030528/1330Z @:ZL3VML.#80.NZL.OC #:1182 [Chch-NZ] FBB7.00i $:1399-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Monday, May 26, 2003.
1. Re: weekend lawyer question
2. Re: I-GATEing?
3. RE: My wandering car
4. Re: I-GATEing?
5. Unproto Path
6. Re: Unproto paths, some observations from the Dayton Hamfest traffic
7. RE: My wandering car
8. RE: My wandering car
9. Re: I-GATEing?
10. DB-9 pin outs
11. RE: My wandering car
12. D700 Question
13. Re: D700 Question (height ques nmea)
14. RE: My wandering car
15. RE: Garmin Rhino?
16. Jerry Schmitt KK5YY -- SK & Memorial Service
17. Re: 60 buck 120GB Hard Drive
18. Re: DB-9 pin outs
19. RE: My wandering car
20. Re: DB-9 pin outs
21. RE: My wandering car
22. Garmin GPS/FRS RINO
----------------------------------------------------------------------
Subject: Re: weekend lawyer question
From: "Doug Younker" <dougy@ruraltel.net>
Date: Sun, 25 May 2003 15:41:14 -0500
X-Message-Number: 1
----- Original Message -----
From: "Bob Bruninga" <bruninga@usna.edu>
:
: To me position information gleaned from a NON HAM source is not a
: "program" or "signal". It is information. Taking the raw Rhino waveform
: and "relaying" it onto HAM frequencies would be against the
: rule. But taking the information a position object received from one
: service and originating it on APRS is fine. Heck we do that with
: Hurricane data all the time!
:
: de WB4APR@amsat.org, Bob
Heck Bob AR operators transmit information gleaned information from a
radio/TV program on a daily basis. Hey "Joe just heard on the news that
I -** Eastbound is closed because of an accident". No one I know gives a
second thought about it. Surely the spirit of the law is directed towards
the ham who would patch the audio from his broadcast receiver to a ham
transmitter during the noon news. So I agree with directly relaying the
Rhino transmission on Amateur bands would be a violation and
processing/relaying the information provided the same transmission would not
be. Another possible stickler would be processing information from
non-amateur rhino users. Could it be we see screwball legislation similar
to that "protecting"the "privacy" of cell phone user?--73
Doug, N0LKK
dougy@ruraltel.net
----------------------------------------------------------------------
Subject: Re: I-GATEing?
From: "Dakota Summerhawk" <dakotas@dotorg.org>
Date: Sun, 25 May 2003 23:30:31 -0600
X-Message-Number: 2
I got lost I thought you had to have the Igate program in the tapr section
to gate it all to the net, or did I miss something here?
Dakota
----------------------------------------------------------------------
Subject: RE: My wandering car
From: "Dakota Summerhawk" <dakotas@dotorg.org>
Date: Sun, 25 May 2003 23:50:36 -0600
X-Message-Number: 3
My GPS12 does the same thing, it will from time to time wander around the
block when the car is shut off and the GPS has full sky view all the time.
Might be inherent for GPS sats maybe?
Dakota
----------------------------------------------------------------------
Subject: Re: I-GATEing?
From: "Dick Stanich" <dick@kb7zva.com>
Date: Mon, 26 May 2003 8:29:20
X-Message-Number: 4
What IGate program? WinAPRS is an IGate program. So are most others, if you
register them.
Dick, KB7ZVA
APRSWest
----------------------------------------------------------------------
Subject: Unproto Path
From: James Smith <k9apr@sbcglobal.net>
Date: Mon, 26 May 2003 08:49:12 -0500
X-Message-Number: 5
Hi All,
This message is for those that live in the general area of Indiana,
East Central Illinois, Southern Michigan, West Virginia, Kentucky, Ohio,
Central and Western Tennessee. Over the years our network has grown to
accommodate a lot of stations in this vast area of the country.( Some
300+ nightly) This area is also covered by 3 different groups Kentucky
APRS Group, Nashville APRS Network, and the Tri-State APRS Working Group
( which needs a new name since we serve outside Indiana, Ohio, &
Kentucky area. ) And their isn't a Power struggle between us for more
area or users of APRS. But we're working together to help the user of
APRS to reduce their unproto's in this area. Which really needs to take
affect soon, the following recommendation have been suggested by myself,
NashvilleAPRS, and a few others. Which will be posted below. :-)
Mobile User's
Please use the unproto of Relay,Wide2-2 all of this area discussed is
Widen / Tracen complaint.
Home User's
Please use the following Wide2-2 or Wide3-3 if your able to get into a
digipeater direct. If not than use Relay,Wide2-2 or Relay,Wide3-3. This
unproto is more than enough to communicate through the vast network.
Digi Operator's
Unproto should be set to Wide2-2 or Wide3-3 any higher than this is a
waste of bandwidth...
To contact groups I discussed goto the links below.
http://kaprs.tripod.com Kentucky APRS
http://www.nashvilleaprs.net NashvilleAPRS
http://www.tawg.org Tri-State APRS Working Group
If you have any comments or questions, please don't hesitate to ask.
Please pass this message to other's that may not be on the list in this
area. To those who have already made the change Thanks!!!!
--
73, James, K9APR Webmaster Webmaster
Chairman \ Coordinator Indiana Repeater Council Henry Co.
Amateur Radio Club
Tri-State APRS Working Group http://www.ircinc.org
http://www.qsl.net/hcara
http://www.tawg.org
mailto:k9apr@tawg.org
Run a APRS Website? Why not join the APRS Webring. http://www.tawg.org/join.htm
----------------------------------------------------------------------
Subject: Re: Unproto paths, some observations from the Dayton Hamfest traffic
From: "Jeff Thomas - KD4EVB" <kd4evb@hotmail.com>
Date: Mon, 26 May 2003 11:02:00 -0400
X-Message-Number: 6
Excellent, I couldn't agree more that we all need to rethink our paths, trim
back on bandwidth used, and consider the impact of how we operate can affect
other users on the systems. Even as many other facets of the hobby are
slowing down or have faded away, APRS continues to grow even in a bad
economy. Looks like the economy is starting to rebound and with that we can
only expect an increase in growth in APRS over the upcoming years. The need
to operate considerately, effectively, and as efficiently as possible will
only continue to be more and more important. Many areas have already seen
what happens when you hit the bandwidth brick wall of 1200 baud packet.
User education, standards, and digi's filtering off troublemakers will be
even more important over the upcoming years.
From looking thru the logs for the Dayton Hamfest traffic passing thru
Northern KY where "WIDE" is no longer a supported path on the digi's, I
noticed that no one that wasn't at least running RELAY in the front of their
paths so they got out at least one hop if they were running the older paths
of RELAY,WIDE or RELAY,WIDE,WIDE. It also looked like the usual slamming of
the network with Dayton traffic wasn't a problem this year, the channel was
busy no doubt, but seemed to be under control and reliable. I did note a
couple mobile stations running horribly convoluted paths like:
RELAY,WIDE,WIDE,WIDE,WIDE good lord! (didn't do much good around here,
RELAY got digi'ed, the rest died as WIDE isn't supported here so one hop is
all he got)
RELAY,WIDE,WIDE3-3,TRACE3-3 geesh, try a bit harder to use the worlds
worst path, grin. (didn't do much good around here, RELAY got digi'ed, the
rest died as WIDE isn't supported here so one hop is all he got)
I think a lot of users don't realize that the path is processed from left to
right by the digi's and think tossing every possible path option in there
will get one of them digi'd wherever they are. Sorry folks, it's left to
right and the next step isn't processed till the one to the left has been
processed by a digi. Not to mention that as you lenghten your path, you
lengthen your packet and the odds of collision go up with packet size.
Of the mobile traffic I watched over the Dayton weekend, probably 60-70%
were running some form of RELAY,WIDEn-n path (a very good mobile path around
here). And notably a good 10% or so were running pure WIDEn-n mobile.
Probably about 20-25% were running the older paths and were only getting out
one hop (RELAY,WIDE or RELAY,WIDE,WIDE).
I've generally found that anything more than 3 hops around here on our
congested airwaves is a waste of time and bandwidth as it's very unlikely
you can get packets much father than that before the likelihood of a
collision takes it out anyways. Most areas around here are within 2-3 hops
of an I-Gate and frankly that's all the distance you really need anyways.
I know this often becomes a controversial topic with some folks saying they
will stay non WIDEn-n for whatever their reasons. Oh well, as some have
noted before with the battle when we went from 145.790 to 144.390, the folks
that refused to move found that evneetually someone else put up a compliant
digi and the world moved on without them. ARPS is a Widen-n world anymore
for the most part, it's high time to operate smarter bandwidth wise and get
rid of old inefficient paths such as WIDE. Many parts of the country with
channel bandwidth issues are already doing what James has suggested here
(and often more strict, I've been in places where you run WIDEn-n only or
you just don't get out at all). We can all use to reevaluate our beacon
rates and paths, myself included as I think I've got WIDE4-4 in a lot of
stuff...not for much longer, grin. Many folks are already operating
compliant with this request with maybe needing to just trim back the WIDEn-n
counts a bit, at least that's what I've observed anyways.
73 de Jeff, KD4EVB
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
