| |
ZL3AI > APRDIG 28.10.03 14:51l 235 Lines 9747 Bytes #999 (0) @ WW
BID : 2222-ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 26, 1/5
Path: DB0FHN<DB0FOR<DB0SIF<DB0NHM<DB0ERF<DB0FBB<DB0GOS<ON0AR<ON0AR<7M3TJZ<
IK1ZNW<ZL2TZE<ZL3VML
Sent: 031028/1236Z @:ZL3VML.#80.NZL.OC #:11453 [Chch-NZ] FBB7.00i $:2222-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Sunday, October 26, 2003.
1. RE: APRSteward and the Interstate Roadway System
2. Proposal (v2.0): APRSignposts and APRStewards
3. Clock Changes
4. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
5. RE: Coiled Coax Loss
6. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
7. Re: Coiled Coax Loss
8. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
9. BASIC program for TNC use
10. Test Message
11. Re: Using a BS2 to gerate packet tones ?
12. Re: Using a BS2 to gerate packet tones ?
13. The real problem.
14. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
15. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
16. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
17. San Diego firestorm
18. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
19. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
20. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
21. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
22. Re: The real problem.
23. Re: 48V Powerpoles?
24. Re: San Diego firestorm
25. Re: The real problem.
26. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
27. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
28. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
29. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
30. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
31. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
----------------------------------------------------------------------
Subject: RE: APRSteward and the Interstate Roadway System
From: "Eric Christensen" <kf4otn@earthlink.net>
Date: Sun, 26 Oct 2003 01:10:10 -0400
X-Message-Number: 1
How about a program that will send the abuser a message via APRS and by
email informing them of their bad choice of path or tx rates??? Then
maybe a bulletin to all every-so-often...
----------
Eric Harlan Christensen
kf4otn@arrl.net
----------------------------------------------------------------------
Subject: Proposal (v2.0): APRSignposts and APRStewards
From: "Ev Tupis (W2EV)" <w2ev@arrl.net>
Date: Sun, 26 Oct 2003 08:30:49 -0500
X-Message-Number: 2
Eric Christensen wrote:
>How about a program that will send the abuser a message via APRS and by
>email informing them of their bad choice of path or tx rates??? Then
>maybe a bulletin to all every-so-often...
Yes, you've got the idea right. Actually the two ideas...
o Tell the folks the "rules of the LAN" (Education)
o Enforce the "rules of the LAN" (Persuasion)
After thinking about this a little more, it may break down like this:
Any individual APRS station in a LAN can function as shown below. There is
no special software necessary to do this. The only requirement is that the
settings TX'd are agreed to be the correct ones for a given LAN.
APRSignpost: A station (not limited to digi's, btw) who RF TX's periodically
(at a rate that makes sense given the level of the LAN's need)
with an UNPROTO of APRS,TRACEn-N,LOCKED (where n-N is locally
determined to be seen throughout a LAN + 1 or 2 more so as to
inform those 'just outside' of the LAN, too).
Features:
o NO use of RELAY...this station must see digi's directly
o Using TRACEn-N, it provides good information for UNPROTO
savvy LAN members to view and determine their own best
UNPROTO paths to use
o Periodically (locally determined interval), it TX's the
following single BLN: (with locally determined values):
UNPROTO Guide: Mobiles-RELAY,WIDE,WIDE. TX rate while in
motion- 5 min. Fixed/Home-RELAY,WIDE3-3.
TX rate >= 15 min. All- Set TXD to 100ms.
o Less-periodically, it TX's the following single BLN:
Area 24/7/365 IGATE and VIA digi list: N3XJT-3 VIA N3KTX-2.
The following requires development, but the concept is outlined below:
APRSteward: An APRS "sniffer" that collects TX's from RF LAN participants
and compares what it "sniffs" to a set of LAN-defined trigger-
events/levels. When the APRSteward's trigger-point is reached
(a violation of a LAN standard is observed), it sends either an
e-mail message or an RF-based APRS message to the offending
station to repoint them to the LAN standard; offering suggestions
in a kind way.
Trigger events could include (and may vary by LAN):
o TX interval
- by station type
+ roving mobiles <n-Min, stationary/parked mobiles <15-min
+ home/fixed <15-min
o UNPROTO path chosen
- by length (R,W7-7) or content (R,W,G,G,W)
While the details can be worked out (and will vary by LAN even then), this
proposal includes two facets:
o Signposts on the "APRS Interstate"
o Gentle nudging to point participants to the right way to use the "road"
Regards,
Ev Tupis, W2EV
----------------------------------------------------------------------
Subject: Clock Changes
From: Randy Allen <ka0azs@earthlink.net>
Date: Sun, 26 Oct 2003 08:33:08 -0500
X-Message-Number: 3
Just a reminder to all that were affected by the switch back to Standard
Time in the US, reset your APRS station local times or adjust UTC
offsets as appropriate.
Since most of us usually only do this twice a year, heres how to do it
for the D-700 (From the Kenwood TMD-700A Specialized Communications
Manual, Page13).
Setting UTC Offset
1 Press [MNU] to enter Menu mode.
2 Press [c]/ [d] to select “RADIO (1–)ö, then press [OK].
3 Press [c]/ [d] to select “TNC (1–6–)ö, then press [OK].
4 Select Menu 1–6–5 (TIME ZONE), then press [OK].
5 Press [c]/ [d] to select the appropriate UTC offset, then press [OK].
The selectable range is from +12:00 to -12:00 in steps of 30 minutes.
6 Press [MNU] to exit Menu mode.
--
Randy Allen, KAŘAZS
EC, Montgomery CO Ohio
OH Dist. 3 ARES Web Page:
http://www.qsl.net/ohd3ares/
----------------------------------------------------------------------
Subject: Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
From: Bob Bruninga <bruninga@usna.edu>
Date: Sun, 26 Oct 2003 08:43:11 -0500 (EST)
X-Message-Number: 4
On Sat, 25 Oct 2003, Ev Tupis (W2EV) wrote:
>Bob Bruninga wrote:
>>No, it adds 30% SPAM to everyone who uses the system and adds to great
>>frustration of the 90% of everyone who doesnt need it!
>
>If 3 BLN's add 30% to the channel's traffic, then there is NO problem to
>fix and NO need to send them. This is not a one-size-fit's-all
>proposal. It allows for LAN's to setup their APRSteward to TX only as
>often as it makes sense in the LAN. Geez, this is much too simple.
Transmit it only once during the day, and my radio captures it and that
is one less message I can get from anyone else. Once my memory is full,
then I cannot receive any other messages from anyone.
APRS was not designed to have nice-to-have routine bulletins forced into
everyone's system. It is designed so that a Tactical-Real-Time bulletin
of immediate importance to eveyrone will be seen by everyone immediately.
>What is most disturbing is that you seem to be saying that you want the
>entire APRS infrastructure to change (ie--Firewall Digi's) because 10%
>of APRS users abuse the system? What kind of sense is that?
No, I am syaing that ANY SYSOP that wants to take control of the flooding
in his area, can do so with the techniques I am offering. And it does
not require the impossible dream of expecting users to make the changes.
My suggestions put the power to improve in thehands of the SYSOPS in a
consistent way.
>This SCREAMS the need for APRSteward. A MINORITY of people need to fix
>their UNPROTO's? Start by educating them. Those that don't listen can
>be personally visited, taken out for a cup of coffee or SUPLISTed.
>Either way, the "problem" that we all assumed existed because of your
>proposal is addressed now, allowing the APRS network to grow into the
>firewall vision that you seem so convinced needs to be installed
>(because of those 10% of users).
We have been trying for 5 years to solve the problems by user education
and it has not worked AT ALL. AND we also have SOLID EVIDENCE that
attempting to send users "corrective info" over the air has not worked
either. So I am not "opposed" to your idea, its just that we have every
indication that it will do nothing to solve the problems an dwill only add
more problems than it is worth.
Nothing personal, that's just the facts...
Bob
----------------------------------------------------------------------
Subject: RE: Coiled Coax Loss
From: David VanHorn <dvanhorn@cedar.net>
Date: Sun, 26 Oct 2003 08:54:15 -0500
X-Message-Number: 5
At 04:13 PM 10/25/2003 -0400, JBCrafts wrote:
>is this "coax" radio shack or is it Belden RG-55BU (double shielded silver
>plated).
>
>Is the SWR low?
>
>Sounds to me as if your coax is radiating... cheap coax, high swr, poor
>impedance matching at the feed point.
Not coupling to the antenna properly, and lots of RF on the coax, it may be
that in this situation the coax shield IS the only effective antenna.
Low SWR just says the load is near 50 ohms. It may be hellishly reactive,
and it may not be radiating, but it's near 50 ohms.
If the length of your coax, or what you do with it makes a difference, you
have problems.
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
