| |
ZL3AI > APRDIG 04.10.03 11:19l 242 Lines 9391 Bytes #999 (0) @ WW
BID : 2083-ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 01, 8/11
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<VK6HGR<ZL2BAU<ZL3VML
Sent: 031003/1407Z @:ZL3VML.#80.NZL.OC #:9643 [Chch-NZ] FBB7.00i $:2083-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Correctly IDing weather stations
From: Bob Bruninga <bruninga@usna.edu>
Date: Wed, 1 Oct 2003 18:10:53 -0400 (EDT)
X-Message-Number: 51
On Wed, 1 Oct 2003, Michael J. Wolthuis wrote:
>2) What if I set the unproto of the weather data instead of WX VIA
>WIDE,WIDE to MYCALL VIA WIDE, WIDE (ie. KB8ZGL VIA WIDE,WIDE) Now I have
>IDed the transmission in the weather data string and I have left the
>county identifier intact as a tactical callsign.
Wont work. An APRS packet to be decoded by APRS must have the TOCALL
begin with CQ, APxxxx, QST, or ALL... SO no one with spec coompliant
software will see you.
Bob
----------------------------------------------------------------------
Subject: Re: [amsat-bb] PCsat 2 year anniversary.
From: Bob Bruninga <bruninga@usna.edu>
Date: Wed, 1 Oct 2003 18:15:55 -0400 (EDT)
X-Message-Number: 52
On Thu, 2 Oct 2003, ZL2CIA - Sil wrote:
>There are, as I'm sure you know, more users of PCsat than what show
>up on pcsat.aprs.org.
>
>Signals from stations down here (ZL), are Sgated onto the APRS network, but
>fail to appear at http://www.findu.com/cgi-bin/pcsat.cgi
>(http://pcsat.aprs.org).
Ah, yes. If they are not gated directly into the APRS-IS (internet
system) by the satgate, but go to local RF first, then FINDU will not see
the PCSAT-1* indication that it was digipeated by the satellite and will
not flag it for the pcsat.aprs.org site.
THanks,
I had not thought of that.
Bob, WB4APR
----------------------------------------------------------------------
Subject: Re: FW: RE: FIX APRSdos RELAYS
From: Bob Bruninga <bruninga@usna.edu>
Date: Wed, 1 Oct 2003 18:20:19 -0400 (EDT)
X-Message-Number: 53
On Wed, 1 Oct 2003 BobDonnell@arkalmus.com wrote:
>If APRSDOS (or a version of it) supported using a KISS TNC (or a TNC in
>KISS mode), APRSDOS would be able to do the right thing internally, i.e.
>callsign substitution/insertion.
But then I would have to do a lot of other things in code as well and I
am line-by-line out of room...
Bob
----------------------------------------------------------------------
Subject: New TRACEn-N (LANn-N) Paradigm
From: Bob Bruninga <bruninga@usna.edu>
Date: Wed, 1 Oct 2003 18:25:56 -0400 (EDT)
X-Message-Number: 54
On Wed, 1 Oct 2003, Keith Sproul reminded me that my CRITICAL new LANn-N
paradigm using the UITRACE function message may have been filtered by many
SPAM filters because I included *** in the SUBJECT.
The subject line was
Re: [aprssig] ***New*** TRACEn-N (LANn-N) Paradigm :
If you are following this thread and give a hoot and missed this critical
ALL NEW concept for local LAN-s on APRS then lemme know and Ill send you a
personal copy. But most of the concept has now been integrated into the
http://www.ew.usna.edu/~bruninga/aprs/fix14439.html
page anyway though it is a little buried in there...
Bob
----------------------------------------------------------------------
Subject: New Mexico LANn-N?
From: Bob Bruninga <bruninga@usna.edu>
Date: Wed, 1 Oct 2003 18:40:35 -0400 (EDT)
X-Message-Number: 55
I am always amazed at the APRS system in New Mexico that grew up almost
overnight years ago when they activated over a dozen digipeaters for APRS
service almost overnight to serve the SAR mission.
Back then they had more digipeaetrs in the whole state than users.
Since they are a very focused group with a single cohesive plan for their
system, I thought they might also be a great place to investigate the new
n-N paradigm. SO I zoomed in today and wow!
Interesting facts:
-The 100 station radius around Albuquerque goes out almost 300 miles...
-Of the 100 stations, 40% of them are ALL DIGIPEATERS!
-looking at the users themselves, I see paths of W3-3 to W7-7.
I think they have a well defined area of interest in their state. Here is
how the new LANn-N paradigm might work in such an area:
- Make all digis of interest use UITRACE NM <=supports the NMn-N net=>
- Leave WIDEn-N ON in the first few tiers of digis radiating outward from
- ALbuquerque so that WIDEn-N can still be used easily within their area
- On the OUTER BOUNDARY of all digis under their control, convert
the UIFLOOD paramater from WIDEn-N to something else or off.
This way, out of state stuff that is flooding them (if that is the case)
will not get in. But they can still leave some WIDEn-N digis in place to
bring in a LINEAR shot of stuff from distant corners or adjacent states
which would not harm them wherever they like. But it will squelch the
hundreds of copies of every DX packet that may not need to FLOOD their
system
So many opportunities...
I wonder...
de WB4APR@amsat.org, Bob
----------------------------------------------------------------------
Subject: RE: Correctly IDing weather stations
From: "Michael J. Wolthuis" <wolthui3@msu.edu>
Date: Wed, 1 Oct 2003 18:49:44 -0400
X-Message-Number: 56
Okay, so I can not do it via the second method. If I ID the station
every 10mins with a btext and just do not have the callsign in the
weather data string is this acceptable practice per the understanding of
the FCC rules?
Trying to be legal and get rid of headaches.
Mike
Kb8zgl
----------------------------------------------------------------------
Subject: Re: Silk Purses
From: <BobDonnell@arkalmus.com>
Date: Wed, 1 Oct 2003 16:03:20 -0700
X-Message-Number: 57
Except that you don't really need an extremely accurate technique to get
a lot closer than you are. You can get close by connecting an
oscilloscope to speaker audio, then:
1) Adjust the test receiver's audio level so that the loudest signals
move the trace up and down 5-6 divisions.
2) Put your TNC/radio in CAL mode and adjust your transmit audio level
for about up and down 3 divisions, when using a 'diddle' calibrate
signal - one that switches between the high and low tones rapidly.
This works on the presumption that no matter where you are, if you can
hear a number of other stations, at least one will be driving his/her
radio to 5 kHz or greater deviation. The deviation limiter in their
transmitter should have been set for 5 kHz deviation, but that setting
may not have been terribly accurate, and it can drift over time too. So
you're setting your transmitter to produce about 60% of the loudest
signal in your area, which should park you near 3 kHz deviation, and
that should be well within the unclipped response range of the deviation
limiter circuitry. You can test this by increasing the output (AFSK)
level of your TNC to find the point at which your own radio limits, then
by decreasing the output level until it's 60% of the limiting value, as
seen on the oscilloscope connected to your test receiver's receive
audio. Perhaps not as precise as using a deviation meter, but you'll be
a lot closer than any of those stations up at 5 kHz deviation, and more
of your packets will be copied.
73, Bob, KD7NM - once an AEA customer service staff member
----------------------------------------------------------------------
Subject: APRS Linux digi, was: Re: DigiNed, was: Re: Take Control of your DIGI
part 4
From: "Scott Miller" <scott@opentrac.org>
Date: Wed, 1 Oct 2003 16:17:29 -0700
X-Message-Number: 58
I just ordered a Soekris net4501 - essentially a 486-133 with 64 megs of
RAM. It's got a CF socket built in, and I'll probably by testing it with
the 16 meg card I've already got on hand, but 128's are pretty cheap these
days. Any suggestions for a distro to start with? I was looking at Bering,
but it's probably too small. I'd rather have something that doesn't cut so
many corners trying to squeeze onto a single floppy. The board's got 8
general purpose I/O lines, so it ought to be able to support at least two
Baycom modems, though the drivers might need some modifications to talk to
the right ports.
It's also got two serial ports, so you can connect an external TNC and still
have a console port. And three 10/100 Ethernet ports, so it can be an IGATE
as well. The newer net4801 has USB, which might be useful for connecting
802.11b links for backbone connections.
For those just tuning in, the purpose of this excercise is to develop a
Linux mini-distro with DIGI_NED and maybe aprsd preloaded, all in a form
that can be deployed on readily available, fairly cheap hardware.
So far I've only spent $220, and that includes a spiffy metal case. That
still leaves a comfortable margin before the setup even matches the price of
a new 9612+.
Scott
N1VG
----------------------------------------------------------------------
Subject: RE: Correctly IDing weather stations
From: "Scott Miller" <scott@opentrac.org>
Date: Wed, 1 Oct 2003 16:21:59 -0700
X-Message-Number: 59
It's done all the time. If you watch some of the big APRS-tracked events
on FindU, you'll see that they use lots of tactical callsigns, and the real
calls never make it to the 'net. They're just beaconing to local RF every
10 minutes like the FCC rules require. Now, my problem with that is that
beyond the direct RF range, digipeaters just blindly digipeat the tactical
callsigns and you have no idea what the real call is. My personal feeling
is that you ought to make sure your ID goes out as far as the message is
going, but I don't know if there's any legal requirement for that.
Scott
N1VG
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
