| |
ZL3AI > APRS 06.10.00 06:36l 168 Lines 5487 Bytes #999 (0) @ WW
BID : 33778_ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 03, 1/2
Path: DB0MRW<DB0ERF<DB0ROF<DB0SRS<DB0AIS<DB0ZDF<DB0SEL<DB0RBS<DB0LX<DB0CZ<
DB0GE<LX0PAC<LX0HST<HA3PG<WB0TAX<VK3BBS<VK2CZR<VK2IO<VK2GJB<ZL2TZE<
ZL2TZE<ZL2WA<ZL2BAU<ZL3VML
Sent: 001004/0942Z @:ZL3VML.#80.NZL.OC #:42391 [Chch-NZ] FBB7.00g25 $:33778_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRS@WW
TAPR APRS Special Interest Group Digest for Tuesday, October 03, 2000.
1. Re: aprssig digest: October 02, 2000
2. Re: Old motherboards for free
3. Decaying Packet Periods
4. RE: [aprsspec] Re: Call Test
5. Re: Old motherboards for free
6. "Tiered" aliasing for digis
7. SUNSAT in HT APRS mode!
8. Garmin 12MAP NEMA input
9. Distribution list
10. Re: SUNSAT in HT APRS mode!
11. Re: SUNSAT in HT APRS mode!
----------------------------------------------------------------------
Subject: Re: aprssig digest: October 02, 2000
From: "Eduardo PY2RN" <radioamador@hotmail.com>
Date: Tue, 03 Oct 2000 09:53:57 EDT
X-Message-Number: 1
ftp://aprs.rutgers.edu/pub/hamradio/APRS/map02/World_Countries.map
73
>Subject: World Maps for WINAPRS??
>From: "Lee H. Dahlen" <kd4tqz@qsl.net>
>Date: Mon, 2 Oct 2000 04:53:39 -0400
>X-Message-Number: 2
>
>Are there any world maps available to add to WINAPRS?? In light of the
>Sydney Games and the ever increasing amount of ww APRS traffic, it would
>seem fit. Any help would be appreciated. BTW Just clarify, I mean ONE
>WORLD map that I can zoom in on anywhere.
>
>Lee/KD4TQZ
>
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
----------------------------------------------------------------------
Subject: Re: Old motherboards for free
From: "Hare, Ed, W1RFI" <w1rfi@arrl.org>
Date: Tue, 3 Oct 2000 09:45:46 -0400
X-Message-Number: 2
> Ah yes, the Hamfest mentality...
> I just got back from the Sioux Falls SEARC Hamfest. We took
> a trailer with about 18 386 and 486 computers . All working.
> I couldn't sell the 486's for $10 apiece.
I had a similar problem at the ARRL Hudson Division Hamfest. I had brought a
UHaul full of classic junque, including about 25 older Tektronix
oscilloscopes, ranging from 5 MHz to 85 MHz capability. I brought back all
but two of the 'scopes, and I was offering the 85 MHz units for $20.00.
(They are really too big to ship -- sorry. But if anyone lives near
Newington...) What was really surprising is that the cheap audio scopes (I
got $5 a pop for them) went, but the hams didn't want to spend another $10
to get a 30 MHz unit. :-)
73,
Ed Hare, W1RFI
ARRL Lab
----------------------------------------------------------------------
Subject: Decaying Packet Periods
From: Bob Bruninga <bruninga@nadn.navy.mil>
Date: Tue, 3 Oct 2000 11:44:33 -0400 (EDT)
X-Message-Number: 3
On Mon, 2 Oct 2000 Boudinotr@aol.com asked:
> ...I would like for a system to "know" whether it is moving or not...
> If moving, it would ... transmit APRS position often. If not moving
> [it] would ... limit transmissions to every 6 hours. What do you think?
APRSdos has always done that. Every packet in APRSdos is repeated on a
decaying time period. Whenever any new info is put into APRSdos, the
packet is sent once, then 8 secs later, then 16, then 30, then 1 min,
then 2 mins and so forth down to the max period (30 min or 10 min).
This is why APRSdos really flies in a MSG dialog, because of the high rate
for new data...
For GPS, the minimum is not 8 secs, but is the alt-S-POSRATE, Usually set
by users to 1, 2 or 5 minutes. But any time your posit is not changing,
then the pos rate decays just like any other packet to a longer and longer
period. As soon as you move, it is a new posit, so therefore the rate
jumps back the high rate.
This variable decaying time period to update new data frequently
and old data less frequently was fundamental to the APRS concept.
Unfortunately, very few authors except for the original APRSdos fully
implemented this technique...
de WB4APR, Bob
----------------------------------------------------------------------
Subject: RE: [aprsspec] Re: Call Test
From: Bill Diaz <billdiaz@megsinet.net>
Date: Tue, 3 Oct 2000 13:11:55 -0500
X-Message-Number: 4
Jim,
It is not unusual for packets coming from APRServe to be fractured, or
corrupted. This is not the fault of APRServe.
Some validation should be performed to ensure that calls do not contain such
things as punctuation (excepting -), spaces, and non-alphaNumeric characters.
The application must also deal with non-compliant orginating calls. Some
stations have SSID's > 15, or Alpha characters where an SSID is expected.
Examples include aprsd-YYC, and KB2EAR-IP.
Validation of calls in headers may be required in some form to detect fractured
or malformed packets. Examples include
WIDE>CQ:,
KC0HMX>APM345,K0having FUN yet??W0HII-9>APRS,K0BOY-1,K0BOY-2*:
N0GGU>APR817,N0GAI0N-9>T1PP5Y,K0BOY-2*,WIDE:'{Q6l"`>/]
W4KNC-9>WA4BWB-3* <UI R,APRS:
WB4IUY>WIDE6-1 <UI,APR810,WA4BWB-3*:
Packets are sometimes received without headers :
=4147.25N/10714.56WIPHG2150/WinAPRS 2.4.7 -WYCARRAWLINS -247-<530>
Packets are sometimes received with control characters in headers or characters
with ascii values > 126.
HTH,
Bill KC9XG
On Tuesday, October 03, 2000 12:19 PM, Woodrick, Ed [SMTP:ewoodrick@ed-com.com]
wrote:
> Jim,
Snip
> Callsign restriction adds a level of complexity that just really isn't
> needed. If I just had to do some filtering, I'd probably go for NOCALL
> and that's about it.
>
> Ed Woodrick
>
----------------------------------------------------------------------
Subject: Re: Old motherboards for free
Read previous mail | Read next mail
| |