Duplex set to 1 (half-duplex) but node is full-duplex

App_rpt-users
1

Trying ASL3 on a Pi 3B+. I have the Pi connected to the link port of a CAT-250 controller. I have used this setup (no hardware changes) with HamVOIP and ASL2 without issue using the Simple USB interface (CM based FOB). While setting the levels into and out of the Pi I noticed, using the V menu, that is activating the PTT and passing audio as would be expected for full-duplex mode when, in fact, I have set it up for half-duplex. Writing the values, exiting the setup menu and restarting asterisk, ASL3 remains in full-duplex mode.

I have verified that in my node stanza in rpt.conf that duplex = 1 is present. Given that the template section has duplex = 2 I changed it to 1 and restarted Asterisk. Unfortunately, the node still is stuck in full-duplex. I can confirm from my main repeater, which is setup the same way hardware wise to the link port of a CAT-200B controller, that audio and supervision are being passed correctly and the node I am working with transmits an MCW ID when necessary.

I don’t want to say this is a bug but this setup worked as intended with previous versions for about the past four years and the only change is the new ASL3 image so it would seem things are pointing that way unless I missed something completely obvious.

2

For repeater controller interfacing the recommended way is to use duplex=0 and linktolink=yes. Is there a reason that won’t work?

What indication do you have that it’s not half duplex?

Could you post your node [xxxx](node-main) stanza, please?

3

Thank you. Setting linktolink = yes is the key to making it work now. That was a setting I didn’t need to touch in the past.

I do set duplex = 1 as I do want certain telemetry to be transmitted from the node to the repeater. I do set hangtime = 100 and idtime = 0. Perhaps if I had set the hangtime very short first I would not have noticed the failure to set linktolink = yes. Perhaps that is why I never changed that setting before.

Always learning.

4

Setting duplex=1 and linktolink=yes is a combination I never heard of. I always assumed linktolink was a duplex=0 override only. I don’t know that it will change the behavior of duplex=1. But give it a try.

5

Of course, with so many configuration parameters, combinations will likely interact in different, perhaps undefined way. I’ve a long history of discovering such combinations!