[arm-allstar] Issue with USB fob going offline.

Sat Feb 16 23:27:58 EST 2019

Simon,

 Great to hear you are making progress. The issue of FOB's going offline
had been a problem many years ago when we first started our code adventure
until we forced a reset in the SW. As you probably know you can hot pull a
FOB and plug it back in or plug another one back in and it will come right
back up to heartbeat.

Often the problem is power spikes between differing power supplies. If you
are using a 25 watt radio it is likely you are using a different supply for
it.  Bonding grounds is very important.  It could be RF but if you antenna
is outside or a great distance away from the FOB and your coax is good I
doubt there woul be enough RF to cause a problem. It might be those
particular FOBS also.

*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Sat, Feb 16, 2019 at 11:22 PM "zl1sww via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Hi Doug,Thanks for the tips. I have been playing around with several
> things and doing several tests.One of the test was just to see if it was a
> power related issue was to not linked to anything for twenty four hours and
> see if the system I still stable. It seems stable so moved to the next
> test. This test was to run at low power which is 5 Watts as opposed to
> running 25 watts beforehand. This seemed to make the system more stable so
> all I can guess is that I'm getting RF into the USB fob somehow. I've added
> some ferrites and also rerouted the antenna cable to keep away from the
> Raspberry Pi box.The USB fob is made by Sanwu. They seem to be the most
> common with the CM108 as an smd chip.  I have ordered 5 more off Ebay just
> in case. Might do a small pcb in place of the sockets to make things tidier
> instead of vero board and smd components i am using at the moment.  The
> antenna would be about 3 m away from the node and is separated by a tin
> roof. So far things are looking quite stable and hopefully it'll stay like
> that way. Thanks once again for the good tips. Cheers, Simon Sent from my
> Samsung Galaxy smartphone.
> -------- Original message --------From: Doug Crompton via ARM-allstar <
> arm-allstar at hamvoip.org> Date: 14/02/19  5:41 AM  (GMT+12:00) To: ARM
> Allstar <arm-allstar at hamvoip.org> Cc: Doug Crompton <wa3dsp at gmail.com>
> Subject: Re: [arm-allstar] Issue with USB fob going offline. Simon,  There
> could be several causes for this but most involve hardware issuesnot
> software.  Here is a list of things that could cause it:- A bad FOB - even
> if it works sometimes it might be flaky- Bad power - This is often an
> issue. Make sure you Pi power supply issufficient. Try another one.- Power
> glitches - ground differentials can cause problems. Make surethings are
> bonded.- RF - This is not only from HF but also from the node radio
> especially ifusing a close by antenna.- Possibly corrupt code. Try setting
> up another SD card and using it.- A bad Pi or USB port. Try a different
> port, different PiWhat power are you using and what FOB are you using?*73
> Doug**WA3DSP**http://www.crompton.com/hamradio <
> http://www.crompton.com/hamradio>*On Wed, Feb 13, 2019 at 9:12 AM "Simon
> - ZL1SWW via ARM-allstar" <arm-allstar at hamvoip.org> wrote:> Hi all,>> I
> have had an allstar node running quite well for some time like 6 months>
> or> so. Up till now, it has been going well.>>>> As of about 3 week ago, I
> have been having issues where the USB sound fob> drops off and non
> responsive to or from the attached radio. An asterisk> restart won't work
> but a warm boot from the menu will restore the usb fob> and the radio works
> again. It will last a day or so and then die.>> I can connect via my cell
> using DVswitch  and all runs fine from the> asterisk point of view. I can
> even reboot via the IAX client and all is> good> again for a while.>>>> I
> thought some power glitches / outages may have corrupted the SD card>
> image> and so rebuilt it. The day after the rebuild, it's failing again
> just as> before. Using the latest image off the site. It's an RPi 2 with a
> USB wlan> dongle working ok.>>>> The messages file shows many entries as
> below:>> [Feb 13 21:53:09] ERROR[14444] chan_simpleusb.c: Not able to
> detach the USB> device>> [Feb 13 21:53:10] ERROR[14444] chan_simpleusb.c:
> Not able to detach the USB> device>>>>>> Asterisk CLI console shows loads
> of:>> [89837.644648] usb 1-1.5: 1:1: usb_set_interface failed (-32)>>
> [89837.652889] usb 1-1.5: 2:1: usb_set_interface failed (-32)>>
> [89837.660900] usb 1-1.5: 2:1: usb_set_interface failed (-32)>>>> And>>>>
> [Feb 13 21:58:01] NOTICE[14444]: chan_simpleusb.c:1488 hidthread: Loaded>
> parameters from simpleusb_tune_usb.conf for device usb .>> [Feb 13
> 21:58:01] WARNING[14444]: chan_simpleusb.c:1789 setformat: Unable> to>
> re-open DSP device 0 (usb): Device or resource busy>>   == Set device
> 1-1.5:1.0 to usb>> [Feb 13 21:58:01] NOTICE[14444]: chan_simpleusb.c:1488
> hidthread: Loaded> parameters from simpleusb_tune_usb.conf for device usb
> .>> [Feb 13 21:58:01] WARNING[14444]: chan_simpleusb.c:1802 setformat:
> Unable> to> set format to 16-bit signed>>   == Set device 1-1.5:1.0 to
> usb>> [Feb 13 21:58:02] NOTICE[14444]: chan_simpleusb.c:1488 hidthread:
> Loaded> parameters from simpleusb_tune_usb.conf for device usb .>> [Feb 13
> 21:58:02] WARNING[14444]: chan_simpleusb.c:1802 setformat: Unable> to> set
> format to 16-bit signed>>>> It seems to show up as a module from lsusb.>>
> [root at zl1sww-47563 asterisk]# lsusb>> Bus 001 Device 005: ID 0d8c:0012
> C-Media Electronics, Inc.>> Bus 001 Device 004: ID 148f:5370 Ralink
> Technology, Corp. RT5370 Wireless> Adapter>> Bus 001 Device 003: ID
> 0424:ec00 Standard Microsystems Corp. SMSC9512/9514> Fast Ethernet
> Adapter>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
> SMC9514 Hub>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root
> hub>> [root at zl1sww-47563 asterisk]#>>>> In the simpleusbtune menu it
> shows as not available.>>>>>>>> Note this is a clean build so should be
> fine. Don't think it is hardware as> the thing runs fine after a warm boot.
> The warm boot most likely power> cycles the USB subsystem though. Hope it's
> not the URI piece as it is home> built and a pain to change.>>>> Any ideas
> or someone who has had the same issue?>> Any extra debugging I can do?>>>>
> Cheers and thanks,>>>> Simon>> ZL1SWW.>>>>>>>>
> _______________________________________________>> 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 web page - http://hamvoip.org>_______________________________________________ARM-allstar
> mailing listARM-allstar at hamvoip.orghttp://
> lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstarVisit the BBB and
> RPi2/3 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 web page - http://hamvoip.org