My rpt.conf:
duplex = 0
linktolink = yes
Doesn’t seem to actually be full duplex. In other words, I have a multiport controller.
Port 1 is a repeater
Port 2 is a RB RIM Lite connected to Port 2 (let’s call this Node A) and I have both Ports linked. If P1 is receiving a signal, obviously both Port 1 & 2 are “transmitting”. If I transmit into Node B and A& B are connected, nothing is heard out the repeater on Port 1.
Does full duplex mean something else in the ASL world?
What is it exactly you are calling ‘ports’ so we are talking the same language?
State the duplex modes of the three systems you mention and if they are all ASL nodes &
the duplex setting in your URI for each
After a look in the wiki, as I did not think duplex 0 was fulll duplex, I was correct.
https://wiki.allstarlink.org/wiki/Rpt.conf#duplex.3D
I believe 0 is full half duplex.
Link to link is to make it full duplex, but you must consider the other links are not part of that process.
Just the node with the settings to the linktolink output.
At least that seems clear to me anyway.
You might experiment with link to link in other nodes. Not sure what to expect though. Worth a try.
Ken, That set up works perfectly at my House. I’d be more suspect of either Node A COS or Node B PTT issues. However I have never used a RIM so possibly there is something there. I’m certain you have audio lines connected properly right?. Also does Tone controll come into play anywhere on either Node?
Larry - N7FM
Mike, the ports I’m referring to are the port to which radios/repeaters/VoiP hardware connects to on a repeater controller.
As for the duplex setting, the Wiki says the same thing as the comments in the rpt.cong file say:
Half duplex with no telemetry tones or hang time. Special Case: Full duplex if linktolink is set to yes. This mode is preferred when interfacing with an external multiport repeater controller. Comment out idrecording and idtalkover to suppress IDs.
As my settings are as I stated in my OP, clearly the ASL node I have to connected to the controller should be capable of “receiving” incoming audio from the node even while PTT is asserted on that Port. But it doesn’t appear to be working that way.
I run 4 separate nodes (each with their own server) and each one is configured identically (duplex=0 linktolink=yes)
Larry, I’ll have to check with Scott and see if the RIM Lite is the issue. I guess much depends if the CM119 it uses is capable of full duplex operation
(and yes, the audio lines are correct as things work fine if P2 isn’t asserting PTT. Audio from the other nodes is heard just fine then). Things have been working fine for months but today I had a reason to specifically check for full duplex operation of my nodes and discovered this issue
Ken,
Your definition of ports tells me nothing if you dont state what a port is connected to
ie a hardware controller PORT or a asl node PORT/uri ?
All this stuff connects to radio, repeaters and voip hardware.
The linktolink was created to run a node in somewhat a parallel mode to interface to a hardwired controller. I know that I did the same back in 2012 or so with the acid version to a cat-1000’s remote base port. But I don’t think I used duplex=0. As I remember, I had to double invert the cos &/or ptt logic as well to get it right with audio gate’ing.
But your connection needs are likely different than I had.
Take some time and think about what is happening.
Well best I can say from here Ken … Mine works as you want. Using URIx which is also CM119.
In simpleusb.conf or your usbradio.conf which ever you use do you have duplex = 1 ; for full duplex?
Larry - N7FM
Dam I hate this convoluted mail system. Ken make sure the duplex setting in the usb sound driver you are using didn’t get accidentally set to duplex=0 it needs to be duplex=1 for full duplex sound
Larry - N7FM
I believe he is using duplex 0 for other reasons, but I’m not sure the wiki is correct on this, but I can’t find my old notes for this. I do have them somewhere. #!@!
Not that you can’t do this, but the behavior is different in my thinking.
But my memory has been scrambled before.
Back in the earlier days of the program, most systems were repeaters, and many did not want to give-up their hardware controllers, and this (linktolink) was intended to be a method to get asl network attached and keep the hardware controller.
Mike
I believe there are two “duplex” setting. One is in the sound driver and the other in rpt.conf.
Different functions in different places with the same name. Perhaps the duplex=1 setting got changed in the sound driver. The one he has set in rpt.conf does work as he wants provided the sound driver passes incoming audio.
Larry - N7FM
I did miss the setting in usbradio.conf (the driver I’m using) but changing it didn’t make any difference - the ASL interface still doesn’t do full duplex operation. I tried this on the 2 nodes I have connected together for testing this.
I’m out of time for playing with it today but I’ll have a look again tomorrow
Yes Mike, that would be my position. I’m using a Arcom RC210 controller with my ASL interface on Port 2.