[arm-allstar] Can simpleusb and usbradio coexist in the same RPi3b+?

Fri Dec 22 17:43:48 EST 2023

Thank you for the response.

Just for background, I have 4 repeater systems across the state each with 2
repeaters (VHF Kenwood TKR750 and UHF Kenwood TKR850) and a frequency agile
remote base (Kenwood TMv71A). Each of these systems consists of 1 RPi3b+
(up to date with the latest updates) and 3 DMK-URI sound fob devices each
of which is connected to the one each repeater and the remote base. I have
never experienced any issues with audio or timing that would indicate
resource limitations. I understand that this is likely because of the fact
that I am using the "simpleUSB" driver on each node and they do not really
need that much resource.

Today I am building a new system using the latest ARM-allstar image (and up
to date with the latest updates) on another RPi3b+ and RIM-MAXTRC sound
fobs to host 2 Motorola GM300 simplex radios (one is UHF and the other is
VHF) and one more pair of UHF Motorola GM300's in a repeater configuration.
The simplex motorola GM300 radios each are to support channel steering. To
support channel steering on these radios with the RIM-MAXTRAC sound fob I
am limited to only specific i/o pins on controllable from the RIM-MAXTRA. 2
of these pins conflict with COR and CTCSS and have forced me to abandon the
simpleUSB driver and configure the USBradio driver in its place and have
this driver process and decode the COR and CTCSS. I know that to support
this driver, I will require much more processing power from the RPi3b+.

My problem is that I cannot control what USB sound fob gets applied to what
node with both drivers configured. When i configure only the simpleUSB
driver I seem to always be able to get the GM300 repeater to work and when
i replace that configuration and only use the USBradio driver, I can get
both the simplex GM300 radios to work, but when I try to build a rpt.conf
configuration to include both simpleUSB and USBradio, Each drivers
configuration had its devstr= variable set the messages indicate that they
are not assigned the way they are configured.

I was trying to verify that both simpleUSB and USBradio drivers are
supported simultaneously in one RPi3b+ and that both configurations
supported the variable devstr= ?

Maybe it is as simple as I am using the wrong devstr= detail in the
configuration.

[root at Node1506 asterisk]# grep Assign /var/log/asterisk/messages
[Dec 22 09:54:58] NOTICE[30450] chan_usbradio.c: Assigned USB device
1-1.5:1.0 to usbradio channel usb_1506
[Dec 22 09:54:58] NOTICE[30453] chan_simpleusb.c: Assigned USB device
1-1.5:1.0 to simpleusb channel usb_1706
[Dec 22 09:54:58] NOTICE[30452] chan_usbradio.c: Assigned USB device
1-1.4:1.0 to usbradio channel usb_1606

[root at Node1506 asterisk]# grep *devstr* *tune_usb_*.conf
simpleusb_tune_usb_1706.conf:*devstr=1-1.2:1.3 *;C-Media Electronics, Inc.
/usb1/1-1/1-1.2/1-1.2:1.3//0003:0D8C:013A.0001
usbradio_tune_usb_1506.conf:*devstr=1-1.4:1.3* ; C-Media Electronics, Inc.
/usb1/1-1/1-1.4/1-1.4:1.3/0003:0D8C:013A.0002
usbradio_tune_usb_1606.conf:*devstr=1-1.5:1.3* ;C-Media Electronics, Inc.
/usb1/1-1/1-1.5/1-1.5:1.3/0003:0D8C:013A.0003

Jeff

On Fri, Dec 22, 2023 at 1:50 PM David McGough via ARM-allstar <
arm-allstar at hamvoip.org> wrote:

>
> The RPi4B for hardware revisions <= 1.2 has some type of hardware bug
> (apparently?), where only a single USB audio FOB will work correctly.
> Note that this "bug" is not limited to audio FOBs, but is also seen with
> other USB peripherals, too, like USB-SATA adapters, USB-serial, etc.
>
> The RPi3B+ works fine with multiple USB FOBS.  However, the kernel USB
> drivers seem to start "running out of gas" when you've got > 2 FOBs in
> continuous use....They still work, but, some brief audio drop-outs may
> occur, accompanied by a kernel message indicating an USB data overrun.
>
> So, for the RPi3 boards, the issue is much different than with the RPi4.
>
>
> Merry Christmas and Happy Holidays!
>
> 73, David K4FXC
>
>
>
>
> On Fri, 22 Dec 2023, Rich Ball via ARM-allstar wrote:
>
> > David,
>
> I thought the rpi4b had an issue with more than on fob but, rpi3â€™s were
> ok.
>
> Btw, Tnx for all you do. Very much appreciated!
>
> Regards,
> Rich
> Sent from my iPhone
>
> > On Dec 22, 2023, at 3:56 PM, David McGough via ARM-allstar <
> arm-allstar at hamvoip.org> wrote:
> >
> > ï»¿
> > Jeff,
> >
> > Yes, this should work. However, there may be performance problems trying
> > to use more than 2 USB FOBs on a single RPi3B+ device.
> >
> > I'll take a look at your config files, if you send them to me directly
> as
> > a tarball or zipfile.
> >
> > Merry Christmas and Happy Holidays!
> >
> > 73, David K4FXC
> >
> >
> >> On Fri, 22 Dec 2023, Jeff Jurenka via ARM-allstar wrote:
> >>
> >> Oh wait. I just realized that it (*devstr* variable) does not seem to
> work
> > in usbradio_tune.conf correctly either.
> >
> > On Fri, Dec 22, 2023 at 10:03â€¯AM Jeff Jurenka <
> ayrton.productions at gmail.com>
> > wrote:
> >
> >>
> >> Can simpleusb and usbradio coexist in the same RPi3b+?
> >>
> >> I cannot seem to find a way to make the *devstr* variable in
> >> simpleusb_tune.conf force assign the desired USB device. It appears that
> >> usbradio_tune.conf may be working correctly.
> >>
> >>
> >> [root at Node1506 asterisk]# grep Assign /var/log/asterisk/messages
> >> [Dec 22 09:54:58] NOTICE[30450] chan_usbradio.c: Assigned USB device
> >> 1-1.5:1.0 to usbradio channel usb_1506
> >> [Dec 22 09:54:58] NOTICE[30453] chan_simpleusb.c: Assigned USB device
> >> 1-1.5:1.0 to simpleusb channel usb_1706
> >> [Dec 22 09:54:58] NOTICE[30452] chan_usbradio.c: Assigned USB device
> >> 1-1.4:1.0 to usbradio channel usb_1606
> >>
> >> [root at Node1506 asterisk]# grep devstr *tune_usb_*.conf
> >> simpleusb_tune_usb_1706.conf:devstr=1-1.2:1.3 ;C-Media Electronics, Inc.
> >> /usb1/1-1/1-1.2/1-1.2:1.3//0003:0D8C:013A.0001
> >> usbradio_tune_usb_1506.conf:devstr=1-1.4:1.3 ; C-Media Electronics, Inc.
> >> /usb1/1-1/1-1.4/1-1.4:1.3/0003:0D8C:013A.0002
> >> usbradio_tune_usb_1606.conf:devstr=1-1.5:1.3 ;C-Media Electronics, Inc.
> >> /usb1/1-1/1-1.5/1-1.5:1.3/0003:0D8C:013A.0003
> >>
> > _______________________________________________
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
> >
> > _______________________________________________
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
>
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
>

-- 
Pursuant to U.S. Code, title 47, Chapter 5, Sub chapter II, ß227,
"Any and all non solicited commercial E-mail sent to this address is
subject to a download and archival fee of $500.00 U.S.". E-mailing denotes
acceptance of these terms.