| |
ZL3AI > APRDIG 29.10.03 22:32l 256 Lines 10296 Bytes #999 (0) @ WW
BID : 2229-ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 27, 1/5
Path: DB0FHN<DB0FOR<DB0SIF<HB9EAS<DB0FSG<DB0SL<DB0RGB<OK0PPL<DB0RES<ON0AR<
VK3TE<ZL2BAU<ZL2BAU<ZL3VML
Sent: 031029/1233Z @:ZL3VML.#80.NZL.OC #:11552 [Chch-NZ] FBB7.00i $:2229-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Monday, October 27, 2003.
1. Re: The real problem.
2. KPC-3 digital outputs
3. More Bad Space Wx
4. 0 channel load APRS Steward (New concept)
5. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
6. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
7. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
8. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
9. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
10. Re: 0 channel load APRS Steward (New concept)
11. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
12. Re: [Kenwood] Power Supply ?
13. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
14. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
15. APRS bulletins
16. USA Stations showing up in Japan
17. messages on kenwood
18. Re: USA Stations showing up in Japan
19. RE: USA Stations showing up in Japan
20. RE: USA Stations showing up in Japan
21. RE: USA Stations showing up in Japan
22. RE: USA Stations showing up in Japan
23. Re: messages on kenwood
24. Re: messages on kenwood
25. RE: USA Stations showing up in Japan
26. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
27. An idea, or do they have this already?
28. Re: An idea, or do they have this already?
29. Re: An idea, or do they have this already?
30. Re: San Diego firestorm
31. Re: An idea, or do they have this already?
32. Check this out
33. Re: [Kenwood] Power Supply ?
34. Re: An idea, or do they have this already?
35. Re: San Diego firestorm
36. Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
37. Re: San Diego firestorm
38. The point is NOT use of BLN, it's RF User Education
39. Re: 0 channel load APRS Steward (New concept)
40. Re: 0 channel load APRS Steward (New concept)
41. Re: 0 channel load APRS Steward (New concept)
42. Re: 0 channel load APRS Steward (New concept)
43. FW: RE:
44. Re: 0 channel load APRS Steward (New concept)
45. APRS coverage in Hawaii
----------------------------------------------------------------------
Subject: Re: The real problem.
From: Tim Schall <grover@fortgirlfriend.com>
Date: Sun, 26 Oct 2003 22:45:15 -0800
X-Message-Number: 1
That's precisely my point. Or one of them anyways. They're NOT failing.
It's just that we keep heaping stuff on them that we want (expect?) them to
do. The idea about having findu look and see if a path is 'excessive' and
scolding a user about it is a fine idea but it takes CPU cycles on a system
that is already working very hard. Plues, that system is located someplace
that doesn't have access to the RF network in Western Washington or Chicago
or Buffalo or Easter Island or anyplace else except where it physically is.
Offload some of that to local or regional server systems that are located
where the RF is. These systems would have access to the RF networks and be
able to be tuned to the local requirements. Not to mention the fact that
'back hoe fade' or terrorist activity or somebody forgetting to pay the bill
or whatever would not affect the whole network.
Keep the national assetts such as findu and aprsworld in the loop. Absolutly.
They can act as a central repository and a gathering place for information on
a national level but off-load some of the extra work to regional or local
systems.
An example of what I'm talking about are the HOG counters we're running out
here in Western Washington. Take a look at
http://www.fortgirlfriend.com/nwprs_usage.html or
http://www.jnos.org/nwprs_usage.html These pages are based on local RF
monitored packets and list the most active users of our local RF network.
While you're at it, if you'd like to attach to the Western Washington RF
network, take a look at the aprsd system at fortgirlfriend.com Standard aprs
server ports apply there.
----------------------------------------------------------------------
Subject: KPC-3 digital outputs
From: "Darryl Smith" <Darryl@radio-active.net.au>
Date: Mon, 27 Oct 2003 21:32:05 +1100
X-Message-Number: 2
People
I seem to remember someone mentioning that some outputs on the KPC-3 could
be set somehow remotely... Does anyone have any information on this?
Also, does anyone know if it is possible for changes in telemetry values to
automatically send a packet... Or for a button press to schedule a
tramission... sort of like a panic alarm on a MIC-E device...
Darryl
---------
Darryl Smith, VK2TDS POBox 169 Ingleburn NSW 2565 Australia
Mobile Number 0412 929 634 [+61 4 12 929 634 International]
www.radio-active.net.au - www.radio-active.net.au\tracking
----------------------------------------------------------------------
Subject: More Bad Space Wx
From: dale huguley <kg5qd@wxsvr.net>
Date: Mon, 27 Oct 2003 13:32:33 +0000
X-Message-Number: 3
Hi All-
from http://www.dxlc.com this morning:
The geomagnetic field is expected to be unsettled to active on October
27 until the possible arrival late in the day or on October 28 of a fast
CME observed early on October 26. When this CME arrives severe
geomagnetic storming is likely for 12-18 hours. Another CME impact could
occur on October 28 after the expected arrival of a CME associated with
an X1 long duration proton flare in region 10484 on October 26.
CME is a Coronal Mass Ejection.
The solar flux reached an astonishing 389 late yesterday.
This can cause bizarre momentary DX up into the VHF region- May see
some DX into your local Lan on 144.390 MHZ - and normal paths may not be
there.
BTW- I am very impressed with the way Ui-View handles message groups-
great for separating the SECALT group for solar wx.
73 de kg5qd Dale
----------------------------------------------------------------------
Subject: 0 channel load APRS Steward (New concept)
From: John Kraus <flyfisher452@cox.net>
Date: Mon, 27 Oct 2003 08:39:26 -0500
X-Message-Number: 4
I have been following the APRS steward thread for a few days and I had a
brain fart.
It is not necessary to add BLN's or other message strings to convey useful
information to the end user about local path recommendations. Just change
the beacon and status strings of the digi to provide a suggestion for MAX
routine path length in hops.
Below are the strings from my digi's as currently set up and captured from
FINDU. Below will be the new ones when I make my proposed changes. This
will allow me to convey suggested paths with NO increase in beacon rate or
channel load.
KC4ZGQ-2
Status: DIGI_NED:KC4ZGQ-2 Macon Georgia W-R-T GAARES Digipeater
Raw packet: KC4ZGQ-2>APND0X,WIDE,qAo,KC4ZGQ-10:!3257.84ND08348.48W#Contact
KC4ZGQ@hotmail.com subject APRS
KG4OLD-2
Status: DIGI_NED: See KG4OLD or KC4ZGQ for information.
Raw packet:
KG4OLD-2>APND0W,KC4ZGQ-2,WIDE2-1,qAo,KC4ZGQ-10:=3250.22ND08337.63W#PHG5530/D
owntown Macon Digi_Ned Digipeater Relay,Wide,Trace N-N
KC4ZGQ-2
Status: Three hops will cover most of Georgia. Please set path accordingly. 73
Raw packet: KC4ZGQ-2>APND0X,WIDE,qAo,KC4ZGQ-10:!3257.84ND08348.48W#THREE
HOPS MAX ROUTINE PATH
KG4OLD-2
Status:Three hops will cover most of Georgia. Please set path accordingly. 73
Raw packet:
KG4OLD-2>APND0W,KC4ZGQ-2,WIDE2-1,qAo,KC4ZGQ-10:=3250.22ND08337.63W#PHG5530/W
-R-T THREE HOPS MAX ROUTINE PATH
The original packets are filled with redundant information. The Icon and
TOCALL show the digi type so there is no need for this in the text. The
LAT/LONG show where it is so the location as MACON is redundant as well.
The new texts provide me an opportunity to communicate useful information
to the end user of the system. The benefit to putting this in the BTEXT of
the digi is that the user can read it from any receive capable client or
from findu without having to look for it.
Personally I think we need to agree on a maximum length for a routine posit
as a national standard. If someone wants to exceed that length it is ok to
do so but that person should be prepared to justify the need. This would
provide the end user with a coherent goal and the information to
intelligently modify their path to meet their defined needs.
I think for most areas and most purposes -- given the local tactical ideal
of APRS -- three hops is a workable start. These hops can be in any sane
APRS format.
RELAY,WIDE,WIDE
RELAY,WIDE2-2
WIDE3-3
Or similar paths using TRACE instead of WIDE or using LANn-N or any other
locally defined 3 hop path.
The key as I see it is to define a path (defined by hops) that can be
agreed on as a national standard.
Ok now I'm off to find a brain plug.
----------------------------------------------------------------------
Subject: Re: Whoa, wait a minute [was: A Low-Tech APRSteward Proposal]
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 27 Oct 2003 08:45:29 -0500 (EST)
X-Message-Number: 5
On Sun, 26 Oct 2003, Tim Schall wrote about supporting the BEST-PATH
BULLETINS concept:
>And I suppose that if 80% of the people on this list jumped off a bridge the
>rest of us would be expected to follow them.
No, the rest of the unselfish ones would look for ways to help them.
>Refusing a good idea, like transmitting 'good' local paths as a bulletin
>simply because the Kenwood is gonna keep ten copies of it and,
>apparently, doesn't do dupe checking on the messages is generally poor
>management. Not to mention extremly poorly designed hardware.
You need to operate a Kenwood like the vast majroity of APRS mobile
operators so you would understand what you are talking about. 1) It
doesnt keep 10 copies, and 2) it does perfect dupe checking and keeps no
dupes.
For example, your email even though it has no 10 message limitation, would
you like for me to send you an Email SEVERAL TIMES EVERY DAY telling you
what I think your best APRS path is? I dont think so.
Why do you think Mobile operators would want this on their radio that they
have to KILL EVERY SINGLE ONE OF!!!
Common guys, remember the Golden Rule. Do unto others what you would have
them do unto you...
I dont want SPAM on my APRS mobile, I want tactical real-time live
local information about what is happening in HAM radio all around me...
de WB4APR, BOb
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
