Multiple USB interfaces

I can’t find anything in the Wiki (or here) about this.

Currently running the Repeater Builder RIM Lite on a Pi and would like to add a 2nd one for a different radio on the same node.

Is this possible?

I think you will need 2 nodes as I believe there can only be one rxchannel driver per node.

Same server but different node, correct?

yes .
One node, one rxchannel
You can have as many nodes as the computer will support in bandwidth. (memory, cpu and network)
I have used intel atom boards with 2.1 ghz @ 4gb ram for the last 8 years and easily supports 4 nodes and could support perhaps 8 with activity of multiple connects.

If you are using multiple uri’s
Be sure that their description in usbradio are uniquely different.

Thanks, I did find some info in the Wiki after all, about how to set things up. Thanks!

(I’m using a Pi4 for this as it serves as a hub for my 5 node repeater system)

On a Pi3b
I Know they will support 2 radio nodes. I have herd as many as 4, but I would caution how many if they have many connects, but can’t give you a definite number.
A Pi 4 with 2gb may be a better choice for 4 and up.

My Pi4 has 4 gb and works well (5 private nodes linked via our local AREDN Mesh network)

The reason for the addition of another node is to add SAME WX Alert capabilities to my system without needing an external controller to tie it in

if your running Hamvoip you don’t need SAME. all you need to do is configure the AUTOSKYWARN program that comes with it

I’m running ASL latest Beta but have considered “stealing” the scripts from the HamVoiP distro (if that’s “allowed”)

Auto-SkyWarn website

Thanks Steve, I’ll check it out

Just a little feedback. I’ve emailed both of his available email addresses and no response…yet

I found the scripts and sound files on GitHub and have it basically running. Except messages are only sent out to the USB interface (which I do want) but I also want them sent to the other connected nodes.

Without any knowledge of the script, I might say,
look closely at it for ‘localplay’.
If that is how it is being sent through asterisk, change it to ‘playback’
Would help if that is the method used.
Otherwise, no suggestions without a peek at it.

Interestingly, I’ve never been able to make playback work as advertised. Thanks for the info

First I might say, I believe it is ‘Playback’ not playback. (might make a difference)
Then the name of the file without .extension (see how asterisk sorts through system codecs)

If using duplex=0 then you might try linktolink=yes for a fix

As I remember it, localplay is a app_rpt function to play into the local extension and not the conference and Playback is pure asterisk playing into the conference. That may help you debug ?

Important to remember that asterisk is expecting full duplex everywhere always.
We are really just hijacking asterisk and it does not work well in all of our needed full half duplex modes.

It seems to work whether ‘Playback’ or ‘playback’ and with the same results. Regardless of linktolink status, if duplex=0 it only plays locally. A shame as there is too much hangtime, even if duplex=0. If set to 2, hangtime is actually longer (despite zeroing out everything) and not really workable for my system.

I shall continue to trudge forward

Well, I can only say the framework to help you think about it.

What you see in hangtime may not be what you think. You are likely describing overall ‘DELAY’ and just a observation on my part, it may be more on the usb/uri side of the equation as I have noticed,
perhaps incorrectly? not all uri’s appear to act the same.
Can’t explain it but have hunches. I have nothing that gets that critical so I do not investigate.

Good luck with the wx scripts.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.