[OZAPRS] European v USnewparadigmand pathlimiting +confusion....

[Chris Hill]

Hi Andrew,

The first hop does work, courtesy of the following workaround:

# WIDE1-1 means that the simple old "APRS v WIDE" will work, 
# despite a bug in 8.2 firmware
# WIDE5-5, 6-6, 7-7 means that greedy paths are only accorded a single
hop!
UIDIGI   ON WIDE1-1,WIDE5-5,WIDE6-6,WIDE7-7


I really think it's a bad idea to get all home users to configure their
home
stations as a WIDE digi.  I don't see how it is any different to
suggesting
that home stations be configured as WIDE digis under the old paradigm.


Regards,



Chris
vk6kch

-----Original Message-----
From: ozaprs-bounces at aprs.net.au [mailto:ozaprs-bounces at aprs.net.au] On
Behalf Of Andrew McDade
Sent: Tuesday, 7 November 2006 4:36 PM
To: VK / ZL APRS Users
Subject: Re: [OZAPRS] European v USnewparadigmand pathlimiting
+confusion....


Gday Chris,

Having the wide1-1 as the fiirst hop, allows home stations and dumb tnc 
digipeaters to be put into service as a RELAY ( well the old equivalent 
anyway ) in an exceptional circumstance. Special event / emergency / 
exercise etc.

The other issue is when using kpc3's with ver8.2 rom's ( I think there may

be a few people using these as digipeaters about the place ) .. I believe
, 
that there is an issue with the first hop not being traced correctly when 
the WIDE parameter is employed in the UItrace config. I think Bob has 
touched on this before as well.

Regards .. Andrew




----- Original Message ----- 
From: "Chris Hill" <chris.hill at crhtelnet.com.au>
To: "'VK / ZL APRS Users'" <ozaprs at aprs.net.au>
Sent: Tuesday, November 07, 2006 5:14 PM
Subject: Re: [OZAPRS] European v USnewparadigmand pathlimiting 
+confusion....


> Hi Andrew,
>
> Is there an advantage to having a path of "WIDE1-1, WIDE2-2", instead of
> "WIDE3-3"?
>
> I would have thought that the slightly shorter packet (approx 10%
shorter)
> would be preferable, as it has a slightly better chance of being decoded
> error free at the first digipeater (and hence accessing the network).
>
> Am I missing something, or is "APRS v WIDE1-1, WIDE2-2" a carry over
from
> the old paradigm?
>
>
> Regards,
>
>
>
> Chris
> vk6kch
>
>
>
> -----Original Message-----
> From: ozaprs-bounces at aprs.net.au [mailto:ozaprs-bounces at aprs.net.au] On
> Behalf Of Andrew McDade
> Sent: Tuesday, 7 November 2006 2:36 PM
> To: VK / ZL APRS Users
> Subject: Re: [OZAPRS] European v USnewparadigmand pathlimiting
> +confusion....
>
> Gday Dion,
>
> As per you previous email , transient / mobile aprs users would use the
> WIDE1-1,WIDE2-2 generic National config.. Whereas home stations,
> digipeaters, special nets, non -interstate ( inter-zone) mobile users 
> could
> perhaps use the ZONEn-n config. So getting on the boat shouldn't cause
too
> much grief for the would-be interstate traveler !!.  In fact most 
> trackers,
> D700's D7's etc etc. all have at least two configs that can be setup, So
> users could possibly utilize a local zonen-n config and an interstate 
> travel
>
> config being wide1-1,wide2-2 within their tracker etc.
>
> Regards .. Andrew .. VK5EX
>
>
>
> ----- Original Message ----- 
> From: "Dion Bramich" <vk7ybi at yahoo.com.au>
> To: "VK / ZL APRS Users" <ozaprs at aprs.net.au>
> Sent: Tuesday, November 07, 2006 4:43 PM
> Subject: Re: [OZAPRS] European v USnewparadigmand pathlimiting
> +confusion....
>
>
>> On Tue, 07 Nov 2006 16:58:34 +1100, Andrew McDade 
>> <amcdade at iprimus.com.au>
>> wrote:
>>
>>> Gday Richard and all,
>>>
>>>> Zoning would make more sense. We use a different implementation of 
>>>> Zones
>>>> in
>>>> VK3 already
>>>
>>> Noting your comment above. I think that we should be trying to
>>> standardize
>>> on one form or another of a zoning system that will best suit the
whole
>>> of
>>> Australia. You could say that each region / zone is independent, and
so
>>> it
>>> doesn't really matter which way this is setup. However it would be
nice
>>> from
>>> a documentation and new user setup point of view, if a standard set of
>>> guidelines is developed with regards to this.
>>
>> Nicer, eg, if someone down here could get on the boat, drive and be
seen
>> without the need for him to take all his documentation to learn how to
>> reprogram, and his laptop to do the programming?
>>
>>>
>>> BTW... perhaps you could tell us more about the Vic zoning
>>> implementation.
>>> Perhaps , it'll suit the rest of us as well !!.
>>
>> Dion.
>>
>>>
>>> Regards .. Andrew
>>>
>>>
>>> _______________________________________________
>>> Ozaprs mailing list
>>> Ozaprs at aprs.net.au
>>> http://aprs.net.au/mailman/listinfo/ozaprs
>>
>>
>>
>> -- 
>> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
>> Send instant messages to your online friends 
>> http://au.messenger.yahoo.com
>> _______________________________________________
>> Ozaprs mailing list
>> Ozaprs at aprs.net.au
>> http://aprs.net.au/mailman/listinfo/ozaprs
>>
>>
>> -- 
>> No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.1.409 / Virus Database: 268.13.28/518 - Release Date: 
>> 11/4/2006
>>
>>
> _______________________________________________
> Ozaprs mailing list
> Ozaprs at aprs.net.au
> http://aprs.net.au/mailman/listinfo/ozaprs
>
> _______________________________________________
> Ozaprs mailing list
> Ozaprs at aprs.net.au
> http://aprs.net.au/mailman/listinfo/ozaprs
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.409 / Virus Database: 268.13.28/518 - Release Date:
11/4/2006
>
> 
_______________________________________________
Ozaprs mailing list
Ozaprs at aprs.net.au
http://aprs.net.au/mailman/listinfo/ozaprs

_______________________________________________
Ozaprs mailing list
Ozaprs at aprs.net.au
http://aprs.net.au/mailman/listinfo/ozaprs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://second.aprs.net.au/pipermail/ozaprs/attachments/20061107/6ef826d5/attachment.htm