[OZAPRS] VK2RHR-1 raw

Wed Nov 15 18:42:18 AEDT 2017

Forgot to mention .....a V1.09 FW is in dev. But we have not tried it as yet.

Justin Albury
J Albury Communications
justin at jacomms.com
0417246791

-----------------------------------------------------------------
This email, and any attachments are for the use of the intended
recipient(s) and may contain confidential/privileged information.
If you have received this email in error, please notify the sender
immediately and then delete it. If you are not the intended recipient,
you must not copy, disclose or distribute its contents to any other
person. We do not accept any liability in connection with transmitting,
unauthorised access to, or viruses in this email and its attachments.
This notice should not be removed.
----------------------------------------------------------------------------------

-----Original Message-----
From: OZAPRS [mailto:ozaprs-bounces at aprs.net.au] On Behalf Of Justin Albury
Sent: Wednesday, 15 November 2017 6:41 PM
To: Australian APRS Users <ozaprs at aprs.net.au>
Subject: Re: [OZAPRS] VK2RHR-1 raw

Hi guys

Just to bring you all up to speed, both RHR-1 & JUZ-1 run a WX3in1 Plus 2.0 with Firmware V1.00/12.01.14

http://microsat.com.pl/product_info.php?cPath=21&products_id=100&osCsid=8d7143064eba3f527940d477dbe49732

Both Dom & I are open to config suggestions.  Both are WIDE1-1 Digi/iGates.  JUZ-1 will go back to the top of the hill in the next few month as RGN-1 and will give full coverage back towards Canberra along the lake that RGI-1 can't cover.
This will be the same north of Goulburn as RHR-1 fails to cover a lot of the highway around Marulan and out to Crookwell.

As I said we are open to ideas.

Justin Albury
J Albury Communications
justin at jacomms.com
0417246791
VK2JUZ
-----------------------------------------------------------------
This email, and any attachments are for the use of the intended
recipient(s) and may contain confidential/privileged information.
If you have received this email in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not copy, disclose or distribute its contents to any other person. We do not accept any liability in connection with transmitting, unauthorised access to, or viruses in this email and its attachments.
This notice should not be removed.
----------------------------------------------------------------------------------

-----Original Message-----
From: OZAPRS [mailto:ozaprs-bounces at aprs.net.au] On Behalf Of Peter VK2MPJ
Sent: Wednesday, 15 November 2017 4:38 PM
To: Australian APRS Users <ozaprs at aprs.net.au>
Subject: Re: [OZAPRS] VK2RHR-1 raw

Just quickly while i have a few minutes

This idea of region or area based digipeating is something I tried to implement a while ago, but it fell by the wayside This is where the “SENSW” came from. Back when I first become involved with RGI-1 & RBM-1, it was when we were upgrading to the “new” WIDEn-N paradigm.
The idea behind SENSW would serve an area of VK1, Riverina, the Snowy region, and out towards the coast with Nowra being the eastern most point. 
Riverina though by the looks of it only adopted “NSW"

Then from memory there was “SYD” which I THINK also incorporated down into the highlands?? I cannot remember for certain.

Looking at the BTEXT coming from RHR-1, it says it’s a W1 digi aka Fill-In, but it’s overlay does not agree. The overlay should be a ‘1’
If it was a WIDE1-1, then it should only respond to stations with a path of WIDE1-1 and nothing else. The quick cursory look I just had, seems to indicate this is so, I’ll look closer later

If a station were to hit RHR-1 with a path of WIDE1-1,WIDE2-1, then yep it’ll hit RGI-1 and RGI will digi accordingly, there endeths the packet though.

I think the traffic issue is more to do with users and their paths rather than digi configs.  WIDE1-1,WIDE2-2 is excessive to many stations.

Pete
2MPJ

> On 15 Nov 2017, at 4:20 pm, Glen English VK1XX <glenlist at pacificmedia.com.au> wrote:
> 
> With well sited digipeaters that look over populated areas as well as 
> gateways inland I am sure this is not a new problem, like all the 
> canberrra UI aprs traffic being digi'ed over into the riverina.
> 
> Over the next couple of months, we'll fix that with a combination user 
> education, user path change (like WIDE1-1, CBR) etc, UHF facility, in 
> addition to more certain measures (temporal filters, !budlists....)
> 
> -glen
> 
> On 15/11/2017 4:06 PM, Josh VK2HFF wrote:
>> Maybe we south-western sydney folk should adopt a path of just
>> WIDE1-1 for fixed stations etc, to reduce the amount of unnecessary 
>> traffic sent south with hops remaining?
>> A quick check of my last few months logs shows that only about 100 
>> unique VK2 callsigns have been digipeated by RHR.
>> I'm #6 on the list by packet count, so will change my path tonight.
>> 
>> - Josh VK2HFF
>> 
>> 
>> On 15/11/2017 2:43 PM, Graeme wrote:
>>> Hello Glen,
>>> 
>>> Sydney proper does not hit RHR - it's mostly only after leaving 
>>> Sydney that RHR comes into play and vehicles travelling south are 
>>> not necessarily heading into Canberra, bypassing Canberra mostly 
>>> past or through the Riverina heading into Victoria or SA, with 
>>> others heading west from Yass. Users wouldn't reconfigure their 
>>> paths for out of Sydney travelling so would remain wide1, wide2-1 
>>> then get dropped prematurely by RGI after only having been first heard by RHR.
>>> 
>>> I don't agree with VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,WIDE2-1 being 
>>> dropped/ignored by RGI unless all people who might travel out of 
>>> urban areas change to wide1,wide2-2 permanently which I suspect will 
>>> cause far more congestion.
>>> 
>>> Graeme
>>> 2HFG
>>> 
>>> -----Original Message----- From: Glen English VK1XX
>>> Sent: Wednesday, November 15, 2017 1:32 PM
>>> To: ozaprs at aprs.net.au
>>> Subject: Re: [OZAPRS] VK2RHR-1 raw
>>> 
>>> Hi Graeme ,
>>> 
>>> I take ur point. we'll see what overs have to say .
>>> 
>>> The thing is the SPIRIT of WIDE2-1 in sydney would not include 
>>> Ginini .....
>>> 
>>> For that, a user could run WIDE2-2
>>> 
>>> so, if I treat WIDE2-1 out of RHR as a drop  but 22-2 from RHR as a 
>>> pass, that will be fine.
>>> 
>>> on receipt of this :
>>> VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,WIDE2-1:
>>> 
>>> RGI should treat as DROP/IGNORE
>>> 
>>> on receipt of this :
>>> VK2XRX-9>S3T8P9,VK2RHR-1,WIDE1*,WIDE2-2:
>>> 
>>> RGI would generate this : (as it considers RHR a WIDE2)
>>> 
>>> VK2XRX-9>S3T8P9,VK2RHR-1,VK2RGI-1*,
>>> 
>>> you would get the traffic that way.
>>> 
>>> comments ?
>>> 
>>> 
>>> On 15/11/2017 12:59 PM, Graeme wrote:
>>>> Glen,
>>>> 
>>>> RHR only draws from south of Sydney from around the 
>>>> Campbelltown/Camden area which is easily a day's return drive that 
>>>> I do myself from the eastern Riverina and therefore of interest to 
>>>> people in the Riverina.  I don't think that RGI should exclude 
>>>> RHR's messages.
>>>> 
>>>> Graeme
>>>> 2HFG
>>> 
>>> _______________________________________________
>>> 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
_______________________________________________
OZAPRS mailing list
OZAPRS at aprs.net.au
http://lists.aprs.net.au/mailman/listinfo/ozaprs