| |
ZL3AI > APRDIG 03.02.03 14:28l 257 Lines 9159 Bytes #999 (0) @ WW
BID : 762-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 22, 1/5
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<IK1ZNW<ON0AR<ZL2BAU<ZL3VML
Sent: 030125/1011Z @:ZL3VML.#80.NZL.OC #:58081 [Chch-NZ] FBB7.00i $:762-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Wednesday, January 22, 2003.
1. APRS for OziExplorer...
2. RE: proxyAPRS...
3. Re: VS3 Voice Chip for D700 Worthwhile?
4. MIC-E Conversion?
5. Re: Map of hops (cool)
6. RE: MIC-E Conversion?
7. Fw: Stolen Packet Node Equipment
8. RE: Low-cost telemetry transceivers
9. RE: MIC-E Conversion?
10. Findu and Icons
11. RE: MIC-E Conversion?
12. new IGATE on the way!
13. ARRL Public Service Manual regarding RACES
14. Re: new IGATE on the way!
15. Re: new IGATE on the way!
16. Re: new IGATE on the way!
17. Re: new IGATE on the way!
18. Re: new IGATE on the way!
19. Re: new IGATE on the way!
20. Re: Map of hops (cool)
21. Re: new IGATE on the way!
22. Re: new IGATE on the way! (CQ AA3JY)
23. HF APRSers
24. Re: new IGATE on the way!
25. Re: new IGATE on the way!
26. UI-View32 question
27. Re: new IGATE on the way!
28. Re: new IGATE on the way!
29. Re: new IGATE on the way!
30. Re: UI-View32 question
31. Re: new IGATE on the way!
32. Re: Findu and Icons
33. WX directional antenna options
34. Re: new IGATE on the way! (CQ AA3JY)
35. Change in APRSEast Configuration (APRS IS)
36. Re: ID Digipeaters
37. Re: WX directional antenna options
38. Re: new IGATE on the way! (CQ AA3JY)
39. Re: new IGATE on the way! (CQ AA3JY)
40. Re: ID Digipeaters
41. Re: ID Digipeaters
42. Re: new IGATE on the way! (CQ AA3JY)
43. Re: new IGATE on the way! (CQ AA3JY)
44. Re: WX directional antenna options
----------------------------------------------------------------------
Subject: APRS for OziExplorer...
From: "Darryl Smith" <Darryl@radio-active.net.au>
Date: Wed, 22 Jan 2003 16:05:24 +1100
X-Message-Number: 1
People
I have just placed a copy of the ALPHA version of my APRS for OziExplorer.
This software will connect to an iGATE and display positions in
OziExplorer. It will also allow a single station to be tracked.
At the moment there is an issue with OziExplorer, and any stations uploaded
to OziExplorer after the first 999 have been uploaded will result in
undefined results.
Some screen dumps and software is available from
http://www.radio-active.net.au/web/gpsaprs/oziaprs.html
Darryl VK2TDS
---------
Darryl Smith, VK2TDS POBox 169 Ingleburn NSW 2565 Australia
Mobile Number 0412 929 634 [+61 4 12 929 634 International]
Darryl@radio-active.net.au | www.radio-active.net.au
----------------------------------------------------------------------
Subject: RE: proxyAPRS...
From: "Bob D." <n2iph@comcast.net>
Date: Wed, 22 Jan 2003 05:11:42 -0500
X-Message-Number: 2
But do we really need IPv6 addressing? Are there not more than enough
addresses in the IPv4 network 44 for all the Hams in the world now
and in the future. A class 'A' address scheme can support up to
16,777,216 nodes, that's about 10x the number of Hams in the world
now.
----------------------------------------------------------------------
Subject: Re: VS3 Voice Chip for D700 Worthwhile?
From: "Joel Black" <w4jbb@charter.net>
Date: Wed, 22 Jan 2003 05:48:40 -0600
X-Message-Number: 3
Tnx to all who sent the information regarding D700 speech.
73,
Joel B. Black, W4JBB
w4jbb@charter.net
----------------------------------------------------------------------
Subject: MIC-E Conversion?
From: Juergen Frank <db2fm@jfsattv.de>
Date: Wed, 22 Jan 2003 15:27:38 +0100
X-Message-Number: 4
Hello group,
because of some problems we found I'd like to ask what the official
statement for MIC-E Conversion in APRS internet servers (aprsd) is.
Problems, I think, are well known:
- mobile stations travelling at 9=B0E (TM-D700) show up in Mongolia (104=B0E)
because of the ASCII-7F
- "armada" of US-stations has been seen off the coast of Spain in the
Atlantic ocean
- height data isn't correct (341 m instead of 509 m e.g.)
Most of servers here in Germany have MIC-E conversion enabled (e.g. DB0LJ
running aprsd 2.1.5.b9, DB0ZWI running aprsd 2.1.5.b8)
Also QRM is increased by enabling conversion:
MIC-E is heard on 144.800 (EU-APRS-qrg)
IGATE sends MIC-E to APRS-IS
APRS-IS converts packet
IGATE sends converted packet out on VHF (because it's a new packet after
conversion has been done)
So, what is the official statement to this (I think all guys, who developed
APRS or APRS-IS are here in this group)?
73 de Juergen db2fm
--
DB2FM
Juergen Frank
mailto: db2fm@amsat.org
mailto: db2fm@darc.de
mailto: db2fm@jfsattv.de
ICQ: 144135020
----------------------------------------------------------------------
Subject: Re: Map of hops (cool)
From: Bob Bruninga <bruninga@usna.edu>
Date: Wed, 22 Jan 2003 09:36:30 -0500 (EST)
X-Message-Number: 5
On Tue, 21 Jan 2003, Byron Smith wrote about Hop Analysis to reach Igates:
>QRM?
>That depends.
>What are we trying to do here?
>Is APRS an RF application that's
>meant to feed the Internet as efficiently as possible, or perhaps APRS is
>an real time RF application that just happens to be monitored by the Internet
>IGATES?...
I am quite pleased that so far, although I never dreamed of the internet
connectivity when I designed APRS in 1992, that the #1 OBJECTIVE of APRS
is tactical real-time digital communications in a local area in support of
local events. And that amazingly, that objective has not been affected or
undermined by the Vast extent of the internet.
Said another way, The objective remains, tactical real-time local
communications. The Internet just makes it possible to view such
activity or to participate in it at a distance.
One thing APRS NEVER was intended to be, and CANNOT be, is a high density
network with hundreds or thousands or people all over a state connceted by
WIDE7-7 paths all on 144.39. It just violates the laws of physics.
Yes, as APRS was growing, it was fun to run long paths in sparse areas
just to show some activity and to allow users to find fellow APRS folks.
But it cannot work that way all on 144.39 in dense areas. The reach of
digis must get smaller as the number of users goes up..
The golden rule is the limit on the number of random stations that can
occupy a given channel and get reliable throughput. This is the ALOHA
limit. Any more than that number on a single channel can't work reliably.
So, people may define what they want APRS to do, but it can never support
more than the ALOHA channel capacity in any given geographical area on
144.39. And we have shown in the last several emails, that that ALOHA
limit is easy to calculate, and now its range in any dense area is easy
to plot. It may be as low as 10 miles in LA and as high as 150 in
Wyoming.
So people can argue all they want about what they think APRS should do,
but they must fix the network, the applications, or their expectations to
limit the 144.93 channel load to something similar to the ALOHA limit in
each area if they want it to work right for everyone in that area (not
just the strongest stations)...
So, If one's objective is to get ANYTHING out of your area or ALOHA
circle, then it must be by GATEWAY, either RF backbones or IGates.
It seems to me that that pretty well lays the ground work for how to make
144.39 work in your area for what you want it to do. If you want to track
over a great distance significantly greater than the ALOHA circle in any
given populated area, then it must be by backbone or internet...
Im repeating myself...
To read about the ALOHA limits and fixing 144.39, see:
http://web.usna.navy.mil/~bruninga/aprs/fix14439.html
Bob, WB4APR
----------------------------------------------------------------------
Subject: RE: MIC-E Conversion?
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Wed, 22 Jan 2003 09:10:13 -0600
X-Message-Number: 6
I am not the "official" word on this, but past threads on this topic
encouraged IGate authors to turn off Mic-E conversion in their software.
Mic-E conversion was originally put in place due to some deficiencies in
certain clients. Those deficiencies no longer exist and Mic-E conversion
no longer serves any purpose. You are correct in stating that Mic-E
conversion increases bandwidth requirements on APRS-IS as well as
potentially increasing RF bandwidth requirements due to the converted
packets being gated back to RF.
The problem with Mic-E packets getting "mangled" reaches deeper than Mic-E
conversion. The default setting in aprsD for FILTER is ON. This filtering
by the TNC causes the Mic-E packet seen by the IGate to be mangled if it
contains certain non-printable ASCII characters such as 0x7f. All IGate
operators should check their configuration files to ensure that FILTER is
set to OFF on Kantronics TNC's and set to nothing on TNC-2 type TNC's.
Capitalization is not used for emphasis here, but to reflect the
manufacturer's documentation.
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
Subject: Fw: Stolen Packet Node Equipment
From: "John Becker" <w0jab@big-river.net>
Date: Wed, 22 Jan 2003 10:35:33 -0600
X-Message-Number: 7
----- Original Message -----
From: "ARES/RACES Oregon - ASEC - N7QQU" <sysop@arespacket.com>
To: <ARES/RACES@ehlo.donobi.com>
Sent: Tuesday, January 21, 2003 19:24 PM
Read previous mail | Read next mail
| |