[OZAPRS] Fw: RGI/RBM/Griffith digis

Wed Nov 1 11:07:43 AEDT 2017

Hi Glen,

Whilst I doubt there's much local interest here in your region's activities, 
if the internet fails either in your area or the Wagga area then the design 
concept of 2 hops could become useful in emergencies.  Ginini appeared to be 
the only link south and west of your area but most certainly the only link 
west.

The Griffith digi mostly fails to hear transmissions (wide2-1 & wide2-2) 
from the Wagga digi although Wagga mostly hears Griffith, which results in 
Griffith digi not hearing Wagga repeated packets that emanated from Ginini 
with unused hops. Ginini out of service meant that neither Wagga nor 
Griffith heard the packets although as most previously only had 1 hop left, 
Griffith would not have repeated them anyway.

The Wagga digi was temporarily relocated some years ago to a less than 
favourable location but if moved to the preferred location of Bethungra then 
Wagga and Griffith digis should hear each other reliably, as well as provide 
more coverage of the Hume and possibly provide a 2nd east-west link via 
Goulburn.

Graeme VK2HFG

-----Original Message----- 
From: Glen English VK1XX
Sent: Wednesday, November 1, 2017 10:08 AM
To: ozaprs at aprs.net.au
Subject: Re: [OZAPRS] Fw: RGI/RBM/Griffith digis

Hi Graeme
OK, so what's the function of Ginini in your region/community  ?

This info helps make decisions about radiation patterns, etc...

As there is an Igate in every town, it gets into the net. Although
without the stitching together (by ginini ?) you dont have location
awareness of others without the net OR you need 2 wide hops.

However I think Josh mentioned that " and Graeme noted that when RGI
went off-air, it effectively
isolated Griffith's APRS RF traffic IIRC."  but you mentioned "Wagga
hears Ginini but Griffith does not "

So Wagga digi is not reliably hearing Griffith  digi ?  confused.

-g

On 1/11/2017 7:41 AM, Graeme wrote:
> By Wagga I meant the Wagga digi.  My igate north of Wagga hears
> Ginini, Wagga and Griffith digis so I see what Wagga and Griffith
> repeat.  My igate is mostly secondary to other igates at Wagga and
> Griffith.
>
> Graeme VK2HFG
>
> -----Original Message----- From: Graeme
> Sent: Wednesday, November 1, 2017 7:32 AM
> To: Australian APRS Users
> Subject: Re: [OZAPRS] RGI/RBM/Griffith digis
>
> Hello Glen,
>
> Wagga hears Ginini but Griffith does not, hearing only via Wagga if a
> repeat
> is still available.  Albury also hears Wagga hence Ginini too if
> repeated.
>
> Graeme VK2HFG
>
> -----Original Message----- From: Glen English VK1XX
> Sent: Wednesday, November 1, 2017 7:12 AM
> To: ozaprs at aprs.net.au
> Subject: Re: [OZAPRS] RGI/RBM/Griffith digis
>
> Hi Josh
>
> thanks for the comments and suggestions on the delay question. Ginini
> will have IP access so we can tweak the cfg.
>
> OK so you are saying Griffith <> Wagga Igate relies on Ginini to pass
> the APRS traffic ?
>
> IE : USER >> Griffith Digi  >> Ginini  Digi >> Wagga Igate
>
> ? that's a long way round , and sees all the CBR basin traffic as
> contention I guess.
>
>
> On 31/10/2017 8:47 PM, Josh wrote:
>> Hi Glen,
>>
>> I'm sort of familiar with the RGI digi, Graeme VK2HFG runs an igate
>> north of Wagga and noted that when RGI went off-air, it effectively
>> isolated Griffith's APRS RF traffic IIRC.
>>
>> I would not recommend adding a delay before digipeating. WB4APR outlined
>> a number of reasons against that approach here -
>> http://www.tapr.org/pipermail/aprssig/2013-March/041554.html
>>
>> If you did want to implement a delay on digipeated frames you'd have to
>> set a DWAIT value on the channel, because digi'd frames are marked as
>> high priority so bypass the normal SLOTTIME and PERSIST delays. That
>> would also impact connected mode packets, and you wouldn't want that.
>>
>> Direwolf has a default DEDUPE value of 30 seconds, but it only applies
>> to transmitted packets - not heard.
>> DEDUPE *will* prevent RGI from digipeating as WIDE1 and then again as
>> WIDE2 when RBM digis the original frame though because it only checks
>> the from, to and body fields for duplicates, ignoring the path.
>>
>> - Josh VK2HFF
>>
>>
>> On 31/10/2017 7:13 PM, Glen English VK1XX wrote:
>>> Hi Josh
>>>
>>> thanks. yeah lots of what I read is workarounds to deal with old TNC on
>>> mountains.
>>>
>>> So with our canberra / ACT infrastructure, with have right now
>>> VK1RBM-1,
>>> it's an old TNC . I dont know how it is configured, precisely.
>>>
>>> It has pretty good canberra metro coverage, right slap bang in the
>>> middle of town.
>>>
>>> Then, a MACRO over all that is Mt Ginini, which the voice repeater on
>>> the site has a reliable 100km range, 200km to average base stations....
>>> (RHR is about 200km). it is REALLY wide.
>>> coverage over canberra metro is pretty reasonable also, but it is 50km
>>> from town.
>>>
>>> Ginini I was told had rather outdated setups, from the 90s. As you
>>> know,
>>> a new dire wolf box and radio is ready to go, takes a bit of
>>> organisation to get to Ginini. 85km , weather etc
>>>
>>> My question is how should I configure this up, IE specifically the UI
>>> DWAIT time- I think that's the parameter (or the Kantronics name for
>>> it)
>>> , IE do I want to have a long delay after it hears something to whether
>>> it decides to repeat it ? IE so the local RBM in metro canberra does
>>> the
>>> bulk of the UI work . But if say a 2 seconds goes past , ginini says,
>>> OK, no one local heard it, I will digipeat it
>>>
>>> or is that sort of operation problematic ?
>>>
>>> Or should locals have a specific configuration ?
>>>
>>> ginini is often used for connected mode traffic from east (on the
>>> coast)
>>> to west of the country (say wagga, albury) . but it does its share of
>>> Hume Highway APRS work .
>>>
>>> have more questions about this, but this is part 1.
>>>
>>> wisdom sought.
>>>
>>> with thanks,
>>>
>>> glen
>>>
>>>
>>>
>>> _______________________________________________
>>> OZAPRS mailing list
>>> OZAPRS at aprs.net.au
>>> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>>>
>> _______________________________________________
>> OZAPRS mailing list
>> OZAPRS at aprs.net.au
>> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>
>
> _______________________________________________
> OZAPRS mailing list
> OZAPRS at aprs.net.au
> http://lists.aprs.net.au/mailman/listinfo/ozaprs
> _______________________________________________
> OZAPRS mailing list
> OZAPRS at aprs.net.au
> http://lists.aprs.net.au/mailman/listinfo/ozaprs

_______________________________________________
OZAPRS mailing list
OZAPRS at aprs.net.au
http://lists.aprs.net.au/mailman/listinfo/ozaprs 