| |
ZL3AI > APRDIG 11.02.04 12:08l 234 Lines 9187 Bytes #999 (0) @ WW
BID : 2818-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 09, 2/5
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<7M3TJZ<SP7MGD<ZL2TZE<ZL3VML
Sent: 040211/0954Z @:ZL3VML.#80.NZL.OC #:18867 [Chch-NZ] FBB7.00i $:2818-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Questions one digi setup
From: "Tim Cunningham" <tim_cunningham@mindspring.com>
Date: Mon, 9 Feb 2004 11:31:10 -0600
X-Message-Number: 8
John,
There are a few things I need to update on the web site regarding the
configuration to bring it back up to date with the latest paradigm changes.
We are implementing these changes over the next month. Some systems here
already have the changes implemented in North Alabama.
We are actually in the process of swapping the function of the UIFloodCall
and UITraceCall to UITraceCall = WIDE and UIFloodCall = ALA for our region
or the state of Alabama. This conforms to Bob Bruninga's latest proposal to
bring some sanity to the APRS network. This eliminates the TRACE function
by moving it to the UIFloodCall under a different name that depicts the
Flood region. We have encouraged digi owners in the state of Alabama to
adopt ALA as the UIFloodCall. Thus, EMA operations and weather station
users can use a path of ALAn-n and the traffic does not spill out of our
region defined as ALA.
The WIDEn-n now works under the UITraceCall. Callsign substitution will
take place when WIDEn-n is used. The whole reason for the changes were some
of the digi users would not conform to the NOID plan so Bob came up with
the idea to create regions that work under the Flood call and push the
WIDEn-n to replace the TRACE function with little impact on the network
except cleaning up duplicates generated by other improperly configured
systems.
All the other settings should be explained on the web site. If you have any
questions, just drop me a note.
http://www.qsl.net/n8deu/uidigi_eprom_settings.htm
73's
Tim - N8DEU
Huntsville, Alabama
----------------------------------------------------------------------
Subject: Re: APRS objects
From: isobar@bcpl.net
Date: Mon, 09 Feb 2004 12:52:33 -0500
X-Message-Number: 9
Bob... What Garmins seem to be affected? The local Columbia repeater has
been pitting out its objects as 147.135+ without bothering my Garmin GPS
III+.
Secondly, do you think it's wise to put repeater freqs on 144.39 as a
general rule? (Columbia only did it for a short time.)
Seems like qrm on a busy net, but I haven't thought about it much. I
notice, though, that they put TCPIP in their oath so it shows up on the
internet, too.
Bob
N3OZB
----------------------------------------------------------------------
Subject: Re: APRS objects
From: "Curt, WE7U" <archer@eskimo.com>
Date: Mon, 9 Feb 2004 10:03:41 -0800 (PST)
X-Message-Number: 10
On Mon, 9 Feb 2004, Robert Bruninga wrote:
>There were some questions comments about APRS objects...
>
>Please, if you are generating LOCAL Objects for your club
>repeater or events, please do NOT put decimal points in
>for frequencies. An Object with the name of 146.525
>locks up everyone's Garmin GPS with a display:
>
>"Revceived Invalid Waypoint, Press ENTER to resume"...
>
>Every time it is sent. This is very frustrating for mobiles...
>
>Instead, just list 145535 including the Khz digit whether it
>is a 5 or 0, and everyone will understand: 156520 for example.
Is this a problem in the firmware of the Kenwoods, or is it being done by
one of the APRS client programs that can generate the Garmin Waypoints,
like Xastir? I haven't looked at that code for a while, but perhaps we're
not filtering out the '.' character?
--
Curt, WE7U archer at eskimo dot com
Arlington, WA, USA http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
----------------------------------------------------------------------
Subject: Repeater Objects [WAS: APRS objects]
From: "Christensen, Eric" <CHRISTENSENE@MAIL.ECU.EDU>
Date: Mon, 9 Feb 2004 13:03:49 -0500
X-Message-Number: 11
Just my two cents worth...
I would like to see repeater objects on the air for the local area. That
way I know what repeaters are nearby when I come into a new town. BUT, I
don't think they should be propagated like traditional stations. Maybe one
hop, maybe no hops! If a digipeater is located at the same location as the
repeater then no hops would let you know there was a repeater nearby and
wouldn't clutter up the network all that bad.
What I don't like is text information without the object formatting coming
from these stations. There is a digipeater local to me that also sends out
frequency information about the repeater that it is collocated. The only
problem with this is that if I miss it I can't go back into the station list
and find that data (on the D-700 when mobile). Now if it created an object
then I'd be able to go back in and get that information easily. If I can't
go back and see that information easily then it is just adding to the
existing problem of traffic overload.
73s,
Eric KF4OTN
ARRL Member
AMSAT Member: 35360
TAPR Member: 8869
Support your Hobby! Join a club.
All contact logs are uploaded to the ARRL LoTW and eQSL.
----------------------------------------------------------------------
Subject: Re: APRS objects
From: "Scott Miller" <scott@opentrac.org>
Date: Mon, 9 Feb 2004 10:23:01 -0800
X-Message-Number: 12
One of the big things we're hoping to do with OpenTRAC is to define a
repeater data element that'll provide that sort of information in a format
that can be used to automatically program a radio. Hopefully static objects
like that could be intelligently queued by the digi and transmitted together
in a block to limit bandwidth usage. A small external device could probably
program a D700, but the hope is that manufacturers would build in support
with new radios. You could drive into an unfamiliar area and have a special
bank of channels auto-programmed, showing repeater callsign, frequencies,
CTCSS tones, a short description, and maybe icons showing things like
autopatch, ARES/RACES mode, and so on. Even range and bearing if your
radio's got a GPS.
I think this would be an awesome feature to have on a radio. Beats hauling
around an outdated repeater guide and manually entering frequencies. So far
I've had no luck getting manufacturer input. Not that we necessarily have
to get it, but I'd rather have their input during the design phase to make
sure it addresses their needs. If anyone out there has contacts with these
people (in particular, Yaesu, Icom, Kenwood, and Alinco) please let me know!
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: APRS objects
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Mon, 09 Feb 2004 14:00:46 -0500
X-Message-Number: 13
>>>"Curt, WE7U" <archer@eskimo.com> 2/9/04 1:03:41 PM >>>
On Mon, 9 Feb 2004, Robert Bruninga wrote:
>"Revceived Invalid Waypoint, Press ENTER to resume"...
>
>Instead, just list 145535 including the Khz digit whether it
>is a 5 or 0, and everyone will understand: 156520 for example.
Is this a problem in the firmware of the Kenwoods, or is it being done by
one of the APRS client programs that can generate the Garmin Waypoints,
like Xastir? I haven't looked at that code for a while, but perhaps we're
not filtering out the '.' character?
Its a problem in the Garmins that dont want to see anything but
alphanumerics in the object (waypoint) names. The Kenwood just passes
along the object name as received to the Garmin (which then protests)...
Bob
----------------------------------------------------------------------
Subject: Re: Repeater Objects [WAS: APRS objects]
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Mon, 09 Feb 2004 14:08:03 -0500
X-Message-Number: 14
>>>"Christensen, Eric" <CHRISTENSENE@MAIL.ECU.EDU> 2/9/04 1:03:49 PM
>>>
I would like to see repeater objects on the air for the local area.
That way I know what repeaters are nearby when I come into a new town.
COMMENT:
But only if it has "significance" to APRS. there are 20,000 repeaters on
the air. As an APRS mobile, I am totally dissinterested in them on my APRS
mobile unless they have APRS significance (or are the local IRLP or
ECHOlink access point.. That is why the ARRL Repeater directory is quite
useless for the traveler, because only about one repeater out of about
every 10 listed is actually used by most locals or travelers in the area.
THe rest are just chaff...
And in my opinion they should definately be LOCAL, DIRECT so that they are
only seen in the RF area where they can be hit solidly.. (Though you may
have to digi them once to get them out of your basement, depending on
source)...
WB4APR, Bob
----------------------------------------------------------------------
Subject: RE: Repeater Objects [WAS: APRS objects]
From: "Christensen, Eric" <CHRISTENSENE@MAIL.ECU.EDU>
Date: Mon, 9 Feb 2004 14:10:42 -0500
X-Message-Number: 15
Bob,
I agree but what criteria would a repeater have to make in order to have
APRS significance? I was thinking of the wide area repeaters being on board
or maybe the ones that have people monitoring most of the time.
Eric KF4OTN
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
