July 2018 - App_rpt-users - lists.keekles.org

Replay of June 26th Net at 8pm EDT (tonight) on 29999
by Mike 12 Jul '18

12 Jul '18

So we are live testing our NET Playback script from the June 26th NET on node 29999 at 8pm EDT "tonight: July 10th". I will take a moment to talk about what is coming up in our next net and a little about the playback script. Q&A if any before running it. It will sound as good/or bad as the original. So if you missed that net or are curious how well this works, TUNE IN ! 73 ...mike/kb8jnm

1 1

URI-X Issues With New Raspbian build
by JJC 10 Jul '18

10 Jul '18

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/cards 0 [ALSA ]: bcm2835_alsa - bcm2835 ALSA bcm2835 ALSA 1 [Device ]: USB-Audio - USB PnP Sound Device C-Media Electronics Inc. USB PnP Sound Device at usb-3f980000.usb-1.1.3, full s $ lsusb Bus 001 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T Bus 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 Hub Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ cat /etc/asterisk/usbradio_tune_usb.conf [usb] ; name=usb ; devicenum=1 devstr=1-1.1.3:1.0 rxmixerset=500 txmixaset=450 txmixbset=500 rxvoiceadj=0.557342 rxctcssadj=0.930165 txctcssadj=220 rxsquelchadj=754 fever=1

4 20

// REMINDER - Node Load Test Day This Sat -14th Sign-up by Thurs 12th
by Mike 10 Jul '18

10 Jul '18

NODE LOAD TEST DAY THIS SAT 14th @ 5pm EDT Details www.29999.link You must submit a request for testing by thurs 12th... see details in link. ...mike/kb8jnm

1 0

Re: [App_rpt-users] URI-X Issues With New Raspbian build
by Mike 10 Jul '18

10 Jul '18

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 On 7/9/2018 7:30 PM, George Csahanim wrote: > 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 Csahanin > Retired > Sent from my iPhone > > On Jul 8, 2018, at 10:44 AM, Mike <mm(a)midnighteng.com > <mailto:mm@midnighteng.com>> wrote: > >> Well, >> >> 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 uridiag >>> URIDiag, diagnostic program for the DMK Engineering URI >>> USB Radio Interface, version 0.9, 08/14/15 >>> >>> Found CM119 USB Radio Interface at 001/005 >>> Unable to re-open DSP device 1: /dev/dsp1 >>> >>> On Sat, Jul 7, 2018 at 10:44 PM JJC <cummingsj(a)gmail.com >>> <mailto: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/cards >>> 0 [ALSA ]: bcm2835_alsa - bcm2835 ALSA >>> bcm2835 ALSA >>> 1 [Device ]: USB-Audio - USB PnP Sound Device >>> C-Media Electronics Inc. USB PnP Sound >>> Device at usb-3f980000.usb-1.1.3, full s >>> >>> $ lsusb >>> Bus 001 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. >>> RTL2838 DVB-T >>> Bus 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 Hub >>> Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB >>> 2.0 Hub >>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>> >>> $ cat /etc/asterisk/usbradio_tune_usb.conf >>> [usb] >>> ; name=usb >>> ; devicenum=1 >>> devstr=1-1.1.3:1.0 >>> rxmixerset=500 >>> txmixaset=450 >>> txmixbset=500 >>> rxvoiceadj=0.557342 >>> rxctcssadj=0.930165 >>> txctcssadj=220 >>> rxsquelchadj=754 >>> fever=1 >>> >>> >>> >>> >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users(a)lists.allstarlink.org >>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users >>> >>> To unsubscribe from this list please visithttp://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. >>

1 0

Some General Announcements & Net Tues July 17th @ 8:30pm edt - Open Source Engineering -Show & Tell
by Mike 10 Jul '18

10 Jul '18

*Some general announcements and more:* *Don't forget to sign-up for node load testing by/on thurs* - 'details' @ *www.29999.link* Testing on Sat. --- The previous net from *Tues June 26 2018* will be 'played back' to * * *"any & all connected stations"* to *_node 29999 _**starting at 8pm edt* Tues July 10 This is one more beta test of our new playback script. More details to follow. (no, it will not time-out your node... just connect to witness how it works... A brief explanation before starting) --- WX8L/Sean is at least one of the guest speakers for the *coming net on July 17*. (there will be other material) So if you have been planning a ASL Micro/HotSpot, look at this and tune-in the the net 'NEXT' tues . *https://wx8l.blogspot.com/2018/06/personal-allstar-pocket-node-based-on.html* *Sean is eager to answer questions and help you along in your quest !* --- I will have some follow-up info for the group before the next (real/not playback) net. See Ya Real Soon... ...Yes we are doin' 'STUFF' ...mike/kb8jnm

1 0

PI3 Audio Gaps
by David Osborn 08 Jul '18

08 Jul '18

Hi Guys, I've built a few nodes over the years, with PC's, Thin Clients, and now the Pi3. I have three Pi3 nodes running nicely, but the one I'm currently working on has me foxed. The problem is "gapping" on receive audio. When in talkthrough, there are very short but unmissable breaks in the incoming audio. Even on an unmodulated carrier, one can hear short silences in the background noise. There are sometimes no gaps for several seconds, other times there are two or three breaks per second. There is no obvious pattern and they are somewhat erratic. It doesn't seem to matter if there's audio present or not, but a tone on the incoming signal makes the issue really obvious. Link audio is fine as are Alison's chants, it's just local RX audio. Reports indicate that a remote node can hear these gaps as well. I connected my CM108 dongle to a recently retired node computer - a Wyse Thin Client PC running Limey Linux - and it was flawless with no gaps and good quality. When re-connected to the Pi, there are the gaps again. The only difference I can find between this new node and previous pi-based ones is that I'm using WiFi on this one; the others being hard-wired. (If anyone can suggest how to get WiFi working on Limey, that would do nicely!) I've tried SimpleUSB and "full fat" USB, and also tried different variations of carrierfrom and ctcssfrom in USBRadio.conf but I cannot discern a difference in behaviour regardless of the configuration. I'm tempted to get an image from one of my other nodes and plug it in to this one to see if that makes a difference. Has anyone had this issue and what was the solution? David - GD4HOZ

2 2

***********- National 'Node Load Test' Day - Sat July 14th
by Mike 05 Jul '18

05 Jul '18

- National 'Node Load Test' Day - Catchy title ?? O.K. ... I have mentioned this before and during our nets. Here is the scoop to get your node 'load tested' You need to send a email to: kb8jnm [AT] uswx.mobi -<notice that is a dot-mobi and not dot-com Subject does not matter but you might use 'node data' In this email, I only want / need this info (no correspondence please) Your Callsign ! Then : One Line for each node to be tested Node# <> #CPU Cores OR 'Pi-node' <> amount of memory in the system ------------------- n1ham 12345 4 cores 4gb 23456 Pi 1gb -------------------- Be sure your node# is correct ! As many nodes as you wish to test in the same email in that format. Email these more than 2 days in advance so I can get the list compiled for test day.(by/on July 12) Note: you are really testing the server, so only one node per server/computer should be tested. ====================== How we will test the nodes: Everyone can check-in with only one/any node to 29999 in call zones 0-3 and 41546 in zones 4-9 (early please) The 2 will be linked. You check-in so I can make a list of testers to send to the designated nodes. So each of you is also a tester. Anyone is welcome to join the net as a 'Load Tester". When you have completed a connect test on one node, come back and re-check the net for next assignment. At varying intervals and amounts, I will have you connect your/any node to the 'target test node', a little at a time based on your resources you sent in that email, till we get a report back that you have crashed or you send info back to abort (cry mercy). You need to talk to the connected stations on your node to be tested as they check-in with you. You will be informed when it is your turn next and must verify you are ready. This should not create any issues breaking your install but, please be prepared to 'reboot' your node if needed and help out connecting down the list -by making yourself available by check-in to the net. You come back to us and report how many before the limits were met. Probably need to monitor allmon for accurate results. Be honest about it. We will not publish your specific result. You may send that info to the same address as above (mycall)(a)uswx.mobi But if you are uncertain on the actual number, please state that. Give me a range in any case (29-31 ?). The data will be compiled and sorted by cpu type and memory and the amount of nodes it supported. With this info, you will be able to judge your resource much more effectively. I will share the compiled data when complete. Also in the future, I want to write a script to limit the number of inbound connects. (Think ecom purposes) What good is a node that crashes when needed. You will not know how many nodes may try to connect at any given time in a real emergency. Know your limits, and protect them. I think we will actually have some fun doing this ! Break-out the hot-dogs and marshmallow's. I may have a few things to help keep it more interesting. If something is not clear or you have questions, please reply to this email directly, off-list. Save/print this for future reference. Do not send correspondence to the above email please. Just Node Data. -- NATIONAL 'NODE LOAD TEST' DAY -- Sat July 14th @ 5pm eastern 2pm pacific / 21:00 UTC Zones 0-3 connect on 29999 and zones 4-9 connect on 41546 Connect and check-in early please. Yes.... we are doin' 'STUFF' !!! ...mike/kb8jnm

1 0

Need method for in shell script command line "active TX'
by Mike 05 Jul '18

05 Jul '18

So I am working on nearly a dozen scripts right now that are of interest to all to be released when all the bugs are out. In one of them, I need a way to determine when a node is in active tx OR when it is 'not' TXing at all. Either will do. I remember years ago that I got this data from somewhere in a asterisk cmd and was able to sort it to create the var I needed. but I can not find it in any of my old scripts for the easy 'remember this' type guidance. Probably there, but I can't find it. I just need to find that data so I can extract it as a var brought forward in my script. No need for help on my script. Probably the same place allmon gets it. Any help ? ...mike/kb8jnm

1 1

re dial install fail on hp thin client
by Redbutton_Ctrl 03 Jul '18

03 Jul '18

Im trying to install the latest Dial for x 386 on an HP thin client and got as far as "select and install software". Any ideas on where to go from here? I used "ASL_1.01-20180417-amd64-i386-debian-stretch-netinst" and trying to install from usb stick. Jon RQ --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 3

echolink asked to disconnect a node from there network
by Pierre Martel 03 Jul '18

03 Jul '18

Received a message from a friend that he was asked to disconnect his allstarlink node from the echolink network. Anyone got this type of message before?

4 4