[aprssig] aprssig Digest, Vol 180, Issue 6

[Mary O'Neill]

Please unsubscribe me from your mailing list.

On Fri, Jun 21, 2019 at 12:00 PM <aprssig-request at lists.tapr.org> wrote:

> Send aprssig mailing list submissions to
>         aprssig at lists.tapr.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
> or, via email, send a message with subject or body 'help' to
>         aprssig-request at lists.tapr.org
>
> You can reach the person managing the list at
>         aprssig-owner at lists.tapr.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of aprssig digest..."
> Today's Topics:
>
>    1. Denver APRS saturation? (Robert Bruninga)
>    2. Re: Denver APRS saturation? (Bud Talbot)
>
>
>
> ---------- Forwarded message ----------
> From: Robert Bruninga <bruninga at usna.edu>
> To: TAPR APRS Mailing List <aprssig at lists.tapr.org>
> Cc:
> Bcc:
> Date: Thu, 20 Jun 2019 20:24:22 -0300
> Subject: [aprssig] Denver APRS saturation?
> A user reported poor APRS performance after moving from Maryland to Denver.
>
> I just took a look at APRS.fi at Denver within the range of just two
> 12,000 foot digis and I cannot believe the system works at all.  There are
> hundreds of users in the same footprint of those digis.
>
> No wonder the performance is so poor!
>
> Have the digi operators done anything in the area to restrict hops like we
> did in Los Angles a decade ago?  Back then, the solution was to force every
> digi to be ONE HOP ONLY.
>
> Is anyone working on this problem out there?
>
> Bob, WB4APR
>
>
>
> ---------- Forwarded message ----------
> From: Bud Talbot <W0RMT.1 at gmail.com>
> To: Robert Bruninga <bruninga at usna.edu>
> Cc: TAPR APRS Mailing List <aprssig at lists.tapr.org>
> Bcc:
> Date: Thu, 20 Jun 2019 20:10:14 -0600
> Subject: Re: [aprssig] Denver APRS saturation?
> Bob-
>
> as a resident of the Denver-Boulder metro area, I can confirm the poor
> APRS network reports. We had a third high site digi about 8-10 years ago on
> Mt Thorodin (a great site) , but after that one was lost (not sure why) and
> with the increase in population the network has suffered. We have many
> RX-only i-gates to fill in gating, but I'm not aware of any coordinated
> effort to improve the network digipeaters. Then again, I've never reached
> out to the digi sysops to inquire, so I'm not sure if they are working on
> it or not.
>
> N0NHJ is the call on the Bakerville digi (BVILLE) which receives a lot
> (most?) of the Denver traffic, except those closer to the foothills as they
> are shadowed for that site. I do not know him nor have I talked to him.
> We've got a couple of digis down lower (like N2XGL-5 up near me) but again
> I do not know if they have coordinated their efforts.
>
> Hopefully somebody else from our area who is better connected can shed
> some light on the subject?
>
> 73 de Bud
> W0RMT
> ----------------------------------------------
> Robert (Bud) M. Talbot III
> W0RMT
> DMR: Brandmeister TG 31088, 31084
> NXDN: 8328 on TG 31088
> P25: 31088
> YSF: 99256, 18262
> DSTAR: XRF303B/D
> APRS: W0RMT-3, -5, -7, -9, -11
> FM voice in Denver/Boulder area: 145.310 (Colorado Connection
> <http://www.colcon.org/index.html>), 146.700, or 146.760
> 303-668-1322
> -----------------------------------------------
>
>
> On Thu, Jun 20, 2019 at 5:26 PM Robert Bruninga <bruninga at usna.edu> wrote:
>
>> A user reported poor APRS performance after moving from Maryland to
>> Denver.
>>
>> I just took a look at APRS.fi at Denver within the range of just two
>> 12,000 foot digis and I cannot believe the system works at all.  There are
>> hundreds of users in the same footprint of those digis.
>>
>> No wonder the performance is so poor!
>>
>> Have the digi operators done anything in the area to restrict hops like
>> we did in Los Angles a decade ago?  Back then, the solution was to force
>> every digi to be ONE HOP ONLY.
>>
>> Is anyone working on this problem out there?
>>
>> Bob, WB4APR
>> _______________________________________________
>> aprssig mailing list
>> aprssig at lists.tapr.org
>> http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
>>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20190621/97507247/attachment.html>