[App_rpt-users] AllStar as Repeater Controller Connect to Duplex Hub

[Jim Aspinwall No1PC]

 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.  

Thinking this needs local node duplex repeat but half-duplex node-to-node.


    On Friday, November 23, 2018, 1:00:49 PM PST, David McGough <kb4fxc at inttek.net> wrote:  
 
 
Perhaps try duplex=3 .....Works just like duplex=2, but audio isn't 
repeated.



On Fri, 23 Nov 2018, Jim Aspinwall No1PC wrote:

> 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.
> 
> Simply connect the repeater radio to the AllStar interface, re-configure the node to duplex=2 - tah-dah - repeater!!
> 
> Then, connect the repeater node to the hub so it can be linked to the other sites.  Connects as before, not unexpected. Great.
> 
> 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...
> 
> 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.    
> 
> Is this a hang-time thing?   Am I missing something?  Expected behavior - don't try this at home?
> 
> 
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20181123/f9d81e1f/attachment.html>