[aprssig] Functional path to hit both WIDE and WIDEn-n digis?

[Robert Rochte]

I'm thinking that the situation is much the same around here (the Detroit
area) as well...  On my last APRS-carrying balloon flight, the digis in the
immediate area completely ignored the packets.  It took a digi about 25
miles away to get the balloon on the Internet.

My guess is that this happened because we used the WIDE2-2 path (actually,
WIDE1-1,WIDE2-1 at low altitude) and the digis here didn't understand the
path.

So I second the question - how to get them all to listen??


On 4/25/07, Alex Carver <kf4lvz at yahoo.com> wrote:
>
> A significant number of the digis in my area are using
> WIDE or RELAY and not WIDEn-n.  I don't think any
> amount of email is going to convince them to change so
> I'd like to find out if anyone has a path suggestion
> for my D7/700 that will hit both types.
>
> Right now I have just WIDE1-1,WIDE2-1 and I get
> digipeated by my own unit and once in a great while
> when I'm driving.  I don't even make it to the APRS-IS
> because I have Xastir back at my place showing tracks
> and it only shows a couple posits for me even after a
> 100 mile round trip.  The posits happen only when I
> was in range of a WIDEn-n digi.
>
> When I'm mobile, I hear plenty of other position
> beacons coming in but mine never seem to get anywhere.
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20070425/a5918a86/attachment.html>