<html><head></head><body><div class="ydp234ee7edyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>Well, sort of good idea, tried that, but going through the duplex hub means we get delayed local repeat, and when you unkey you get to hear a bit of yourself repeated back due to the path and processing delay. <br><br>Thinking this needs local node duplex repeat but half-duplex node-to-node.</div><div><br><br></div><div><br></div>
</div><div id="ydp67869c20yahoo_quoted_3907358116" class="ydp67869c20yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, November 23, 2018, 1:00:49 PM PST, David McGough <kb4fxc@inttek.net> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr"><br clear="none">Perhaps try duplex=3 .....Works just like duplex=2, but audio isn't <br clear="none">repeated.<br clear="none"><br clear="none"><br clear="none"><div class="ydp67869c20yqt6049865346" id="ydp67869c20yqtfd69237"><br clear="none">On Fri, 23 Nov 2018, Jim Aspinwall No1PC wrote:<br clear="none"><br clear="none">> I thought I was going to be ingenious and replace a few RLC multi-port controllers that each have one of the link ports tied to an AllStar node that runs in non-duplex, and the node connects to another AllStar hub (running in duplex) that is used as the 'link' to feed other repeaters in similar configuration.<br clear="none">> <br clear="none">> Simply connect the repeater radio to the AllStar interface, re-configure the node to duplex=2 - tah-dah - repeater!!</div><br clear="none">> <br clear="none">> Then, connect the repeater node to the hub so it can be linked to the other sites. Connects as before, not unexpected. Great.<br clear="none">> <br clear="none">> What I did not account for is that the hub is running in duplex, so whatever the repeater sends to it comes back, delayed of course. Sounds like an undesired configuration...<br clear="none">> <br clear="none">> However that doesn't seem to account for the fact in the prior configuration the duplex hub traffic never came back into the half-duplex node and echo'd.  <br clear="none">> <br clear="none">> Is this a hang-time thing?  Am I missing something? Expected behavior - don't try this at home?<div class="ydp67869c20yqt6049865346" id="ydp67869c20yqtfd56836"><br clear="none">> <br clear="none">> <br clear="none"></div></div></div>
</div>
</div></body></html>