Additional testing shows a few things on this issue:
Much of it depends on your power supply to the Pi board.
When you reach the limit of current from the power supply, the connection can get 'noisy'
meaning that the switching transistors in regulation start showing 'pulses' that are never good for a computer with a timing clock.
So a quick check to just the voltage is not always enough. But
needs to be done in any case.
Just additional info to look at/for.
...mike/kb8jnm
I agree on this point. I was running my 28599 node on a usb power supply where I thought for sure it had enough smoke. Nope. The board did odd stuff even shut down a few times. Changed the power supply... not a problem since. Though this may not be your issue, Mike has a good point
George CsahaninRetiredSent from my iPhoneWell,
this may not be relevant, but worth saying at this point.
I have found that if you initialize a pi node while not supplying the Pi board with enough current
during the initial start-up. Many things seem to go wrong.
I'm building a bigger 5v power supply to handle 2 or three of these at once to verify what I'm thinking,
but not tested anything yet.
In my case, it is Dahdi
So, just something to look at and if it appears to be likely,
I would say get the required current supplied and start anew with a fresh img.
Not sure if it helps, but something to look for.
...mike/kb8jnm
On 7/8/2018 9:44 AM, JJC wrote:
Not sure why but the /dev/dsp1 seems to be missing... I've installed oss-compat and tried a number of things.. see below output...
$ sudo uridiagURIDiag, diagnostic program for the DMK Engineering URIUSB Radio Interface, version 0.9, 08/14/15
Found CM119 USB Radio Interface at 001/005Unable to re-open DSP device 1: /dev/dsp1
On Sat, Jul 7, 2018 at 10:44 PM JJC <cummingsj@gmail.com> wrote:
Didi a fresh install of the latest ASL from the repo on a fresh install of raspbian on an RPI 3. The issue is simple... the pi sees the URI but ASL seems to have issues..
I have included sample output from a variety of commands below which clearly details the underlying OS sees the URI as it should, and the given address etc...
see the example output below...
taken from /var/log/asterisk/messages[Jul 7 22:19:46] WARNING[6703] chan_usbradio.c: Loaded parameters from usbradio_tune_usb.conf for device usb .[Jul 7 22:19:46] WARNING[6703] chan_usbradio.c: Unable to re-open DSP device 1 (usb): No such file or directory
$ cat /proc/asound/cards0 [ALSA ]: bcm2835_alsa - bcm2835 ALSAbcm2835 ALSA1 [Device ]: USB-Audio - USB PnP Sound DeviceC-Media Electronics Inc. USB PnP Sound Device at usb-3f980000.usb-1.1.3, full s
$ lsusbBus 001 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-TBus 001 Device 005: ID 0d8c:013a C-Media Electronics, Inc.Bus 001 Device 006: ID 0424:7800 Standard Microsystems Corp.Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 HubBus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 HubBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ cat /etc/asterisk/usbradio_tune_usb.conf[usb]; name=usb; devicenum=1devstr=1-1.1.3:1.0rxmixerset=500txmixaset=450txmixbset=500rxvoiceadj=0.557342rxctcssadj=0.930165txctcssadj=220rxsquelchadj=754fever=1
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.