OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   20.05.07 01:57l 151 Lines 5145 Bytes #999 (0) @ WW
BID : 10186-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 35 #10, 3/3
Path: DB0FHN<DB0MRW<DK0WUE<7M3TJZ<ZL2BAU
Sent: 070519/2347Z @:ZL2BAU.#79.NZL.OC #:48667 [Waimate] $:10186-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To  : APRDIG@WW

Message: 16
Date: Fri, 11 May 2007 09:45:24 -0600
From: Earl Needham <needhame1_at_plateautel.net>
Subject: Re: [aprssig] Missing posts???

Already did -- the missing messages aren't anywhere that I can access.
Maybe Yahoo lost them or something.  Again...

Earl

KD5XB -- Earl Needham
Clovis, New Mexico DM84jk
http://groups.yahoo.com/group/cw_bugs

At 08:06 AM 5/11/2007, KEVIN KIBBE wrote:
>Have a look in your "Spam" filter. My Rogers email account tags some 
>of the aprssig emails as spam and puts them into the web based email 
>spam folder.
>
>Kevin
>VA3SU
>
>>Thanks, David -- something weird is going on here, I'm
>>missing a LOT of email it appears.

KD5XB -- Earl Needham
Clovis, New Mexico DM84jk
http://groups.yahoo.com/group/cw_bugs 

------------------------------

Message: 17
Date: Fri, 11 May 2007 12:14:52 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] APRS and the Interstates

>What about putting local Highway Patrol offices
>out as an object?... in an emergency it might
>be nice to know where they are...

I donno, I'd probably not want to see these clutter up my radio's list and
my map.  These are the kinds of things that should be in the local APRSdata
base so that they will show up from a Query. (Assuming someone is running
the APRSdata engine in the area, or the comparable APRSkiosk program.

Three Reminders:

1)  There is only one Btext available in each digipeater.  The best use of
this in every digi, is the locally recommended voice-repeater-object, which
is of great value to a traveler entering the area.

2)  These local Btext objects are sent DIRECT so they cover only the area
of immediate interest that can hit the voice repeater, and since they are
originated by the DIGI, they add zero congestion load to the channel.

3)  Conversly we generally do *not* want to see permanent local voice
repeater objects originated by home stations and other clients.  These are
usually transmitted more than one hop (QRM), go outside the area where they
have any value (SPAM), and are originated at the home station where they
cannot hear what the digi hears, and so they add a load to the congested
channel (QRM).

We have a voice repeater object in our area 443.XX MHz, that is being sent
out by a local client via WIDE2-2 (which is almost 100 miles from where the
repeater is..  This packet covers 5 states and about 40,000 square miles of
the highest density APRS network in the world.  Yet, a mobile can only work
it if it is within 20 miles of it.

And it is colocated with a digi at the same site.  It would be better for
everyone and the network if only that digi transmitted that object as a
BText and only DIRECT to the same RF coverage area where it can be used.
Not the 5 states surrounding it.

Bob, WB4aPR

>>--- Rusty Hemenway <rhemen_at_roadrunner.com> wrote:
>>>
>>>I'd love to have the freq/pl of a wide area repeater
>>>(possibly one with Skywarn)
>>>
>>>Rusty
>>
>>
>>Yep, I already do that....and another ham puts up the
>>Lincoln NE repeater....
>>
>>What else would be useful?
>>
>>While your zipping through on Interstates, what would
>>you like to see?
>>
>>73's
>>Eric
>>kc0ahk

------------------------------

Message: 18
Date: Fri, 11 May 2007 11:37:59 -0500
From: "Matt Werner" <kb0kqa_at_gmail.com>
Subject: Re: [aprssig] Lasting Compatibility of the D700a

Some of the Garmin updates (maybe half of what I've seen) are *bug fixes*
as well as bells and whistles.  The Kenwood doesn't deal with compressed
objects, correct?  It sure would have been nice to be able to update one to
comply with the published spec...

You talk about maintaining on-air-compatibility - that's something the
Kenwood lacks in some areas BECAUSE of it's lack of updates.  On top of
that, we're now left with a spec that is catering to a device that can't be
updated.  We're left with a system that will never evolve with the times.

On 5/11/07, Robert Bruninga <bruninga_at_usna.edu> wrote:
>>... the only bad thing about the d700a is the
>>fact you cant flash it.   The way Garmin
>>does updates works VERY well...
>
>Garmin's are personal devices that have no need to be compatible
>with each other.  On the other hand, the stability of APRS as a
>common protocol instead of a constantly moving target of bell's
>and whistles has a certain value in maintining
>on-air-compatibility.
>
>As a communicaitons system, the intent of APRS was to make sure
>that all recepients saw the same tactical info in the same
>context.  Without consistency, a tower-of-babble results and
>communications reliability is deminished in some cases instead
>of enhanced.
>
>In that sense, there is value in the fact that the radio cannot
>be flashed and will always be compatible with all the other
>tens' of thousands of D700's out there, without having to
>download a new "version" every month or so for the life of the
>radio.
>
>Just the flip side.
>
>Bob, WB4APR

------------------------------

aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig

End of aprssig Digest, Vol 35, Issue 10



Read previous mail | Read next mail


 18.05.2024 15:34:50lGo back Go up