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?
My understanding...
Yes, your hub is full duplex.
Your repeater should be full duplex as well.
You should not be getting anything 'back from' the hub that is generated at the repeater. It Should output from the repeater only. Anything originating or broadcasting to the hub would be shared with a link from the hub to the repeater except if it comes from the repeater.
So if I understand, perhaps the duplex mode of the actual uri ?
duplex = 1 ; Duplex / 0 - half duplex / 1 - full duplex
As I said, I may not understand the exact issue.
If nobody else gives any better guidance, perhaps just re-phrase the issue without the history of it.
...mike/kb8jnm
···
On 11/23/2018 2:42 PM, 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?
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users 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.
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?
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.
Perhaps try duplex=3 …Works just like duplex=2, but audio isn’t
repeated.
···
On Friday, November 23, 2018, 1:00:49 PM PST, David McGough kb4fxc@inttek.net wrote:
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?
Might just be me but I’m having hard time understanding your setup. Any chance you could provide a drawing or more detailed explanation of what you’re trying to do?
···
On Fri, Nov 23, 2018 at 1:42 PM Jim Aspinwall No1PC no1pc@yahoo.com 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?
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.
Might just be me but I’m having hard time understanding your setup. Any chance you could provide a drawing or more detailed explanation of what you’re trying to do?
On Fri, Nov 23, 2018 at 1:42 PM Jim Aspinwall No1PC no1pc@yahoo.com 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?
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.
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users 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.