[arm-allstar] Second USB Rim-LIte Causes the new one to not pass audio.
ARM Allstar
arm-allstar at hamvoip.org
Mon Nov 9 14:42:48 EST 2020
I realized I sent this from the wrong email address but I'll press forward
from this one regardless.
David,
Yes I did those steps multiple times just to be sure including restarting
each time as well as following the steps in the config guide starting on
page 10. Both USB fobs are properly detected and work except for passing
audio to the second node and the degradation of audio as described. If I
unplug either one once set up, whichever once is left plugged in behaves
properly. My only guess is some kind of power issue.
Is there any way to see what's happening to the audio from the Asterisk CLI?
Mike
WG5EEK
On Mon, Nov 9, 2020 at 11:19 AM "ARM Allstar via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
>
> Mike,
>
> Using two USB fobs on an RPi3B should work fine, I've got many setup this
> way. Did you use the simpleusb-tune-menu program to setup the fobs?
>
> The procedure is to plug in only the first fob, select the proper
> simpleusb device (menu option 's'), perform setup and save (menu option
> 'w'). Then, plug in the second fob as well (both now plugged in), select
> the second simpleusb device (menu option 's'), perform setup and save.
> Exit out of the simpleusb-tune-menu program and restart....The fobs should
> both now be happy.
>
> 73, David KB4FXC
>
>
>
> On Mon, 9 Nov 2020, "ARM Allstar via ARM-allstar" wrote:
>
> > I'm running a Pi3B with the latest fully upgraded version of HamVOIP.
> >
> > I followed the steps in the guide to add a second USB FOB. Both are
> USB-RIM
> > Lites. I was able to add the second RIM-Lite and set up my second node
> > number. The second USB RIM-Lite worked for audio receive, and can PTT
> just
> > fine. So I know the edits of my iax and rpt and simple usb config files
> are
> > all correct. However, when the second RIM-Lite is connected, no audio
> > passes to the mic input of the second radio, no voice, no tones. just a
> > carrier when it is keyed. Both will work just fine when one is connected
> > at a time. For a test, I disconnected the second RIM-LIte, connected my
> > second harness and radio to the first RIM-Lite and everythng worked fine,
> > PTT, Audio is passed, the COR worked, everything. I even created a whole
> > new setup on a seperate Pi and confirmed that the Rim-Lite works on that
> > one as well. So I know for certain that the RIM-Lite works, the cable is
> > wired correctly, and the radio works.
> >
> > I also noticed on the DVSwitch mobile app that when the second RIM-Lite
> was
> > connected the audio suffered harshly from the first RIM-Lite, it was
> > cutting in and out, very choppy, and as soon as I disconnected the second
> > one, the audio on the first returned to normal. I also had someone
> > connected through EchoLink and they said the same thing, choppy audio.
> >
> > I also tried setting up the second RIM-Lite on a different port, again
> > following the instructions to stop asterisk connect, start asterisk and
> use
> > the Asterisk CLI again to activate and tune. Same results as before. No
> > audio is passed and the first RIM-Lite had degraded audio.
> >
> > Is this a power issue? Should I try using a powered USB hub? Nothing
> else
> > is connected to the origianal Pi besides the RIM-Lites. Too much power
> > draw is my only guess. The power supply I'm using is outputting 5V 3A.
> >
> > I appreciate everyones thoughts or ideas as I'd really like to use the
> same
> > Pi for both RIM-Lites.
> >
> > Mike
> > WG5EEK
> > _______________________________________________
> >
> > 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
>
More information about the ARM-allstar
mailing list