<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
No reason for a hub to have hang time. Nor should the link radios
from the "client" repeaters.<br>
<br>
73, Steve N4IRS<br>
<br>
<div class="moz-cite-prefix">On 8/26/2016 7:49 AM, Stephen - K1LNX
wrote:<br>
</div>
<blockquote
cite="mid:CABbxpd-DuBpjGJd7ww-iNwsZuSfcZT4BLgDxbfP7u5Y8CMggXQ@mail.gmail.com"
type="cite">
<div dir="ltr">David,
<div> Yes, this is the exact scenario. I think it can be
solved by eliminating the hangtime from propagating across the
hub alltogether, but not sure what the best approach is. </div>
<div><br>
</div>
<div>Thanks,<br>
Stephen</div>
<div>K1LNX</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Aug 26, 2016 at 6:58 AM, David
McGough <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:kb4fxc@inttek.net" target="_blank">kb4fxc@inttek.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi Stephen,<br>
<br>
I guess, in your scenario, the ping-pong is generated from
repeater TX<br>
hang times? So, something like:<br>
<br>
1) User keys up "Repeater A" directly.<br>
<br>
2) Simplex AllStar link "Radio 1" hears "Repeater A" TX
audio and/or hang<br>
time and repeats to the hub.<br>
<br>
3) Simple AllStar link "Radio 2" connected to same hub keys
and brings up<br>
"Repeater B"<br>
<br>
4) "Repeater A" unkeys, "Radio 1" COS goes inactive, "Radio
2" unkeys.<br>
<br>
5) "Radio 2" hears "Repeater B" TX audio and/or hang time,
keys hub,<br>
"Radio 1" and "Repeater A".<br>
<br>
6) "Repeater B" unkeys, "Radio 2" COS goes inactive, "Radio
1" unkeys.<br>
<br>
7) Goto 2 and repeat forever<br>
<br>
<br>
73, David KB4FXC<br>
<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
On Fri, 26 Aug 2016, Stephen - K1LNX wrote:<br>
<br>
> Hi guys... I am in the midst of deploying a 5 site
system. All of the sites<br>
> with the exception of my own will be using link
radios sitting on the<br>
> repeater pair, some sites do not have internet
access so this is the only<br>
> option. Each node will be permalinked to our hub.<br>
><br>
> What we discovered when we brought site number 3
online was the dreaded<br>
> "ping-pong" effect, and I did some digging and
found out about the<br>
> rxondelay parameter, that seems to be the place to
start with this.<br>
><br>
> The other option we are considering is dropping the
hang time off each<br>
> repeater and using app_rpt to do hang time and
courtesy tones instead<br>
> (duplex = 1 instead of 0) but not sure that would
work real well or be<br>
> optimal.<br>
><br>
> Anyone have any experience with a setup like this
that can offer some<br>
> advice? This is my first foray into this
unfortunately, I've always just<br>
> interfaced the radio or repeater directly to
app_rpt in the past or through<br>
> a controller so it's been a bit of a challenge.<br>
><br>
> 73<br>
> Stephen<br>
> K1LNX<br>
><br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
App_rpt-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a>
<a class="moz-txt-link-freetext" href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
To unsubscribe from this list please visit <a class="moz-txt-link-freetext" href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
"Just say no to world domination"
</pre>
</body>
</html>