[arm-allstar] BBB node problems

Doug Crompton doug at crompton.com
Wed Jun 3 11:49:31 EST 2015


Ken,

 It looks like the ip address is correct.  See if you can ping at the linux prompt -  ping ucsd.edu

Also go into the client - asterisk -rvvv   and  type  iax2 show registry

and see if you are registering.

The example you gave didn't show the actual tones in the display???  It should print the DTMF key you press.

simpleusb-tune-menu is  a linux command - not in the client.

I don't recommend usbradio on any of the small boards at this time. I am surprised you were using it on version 1.0

Do keep in mind that simpleusb requires a COS signal from the transceiver or receiver indicating carrier. It also has to be set properly in simpleusb.conf   -  carrierfrom=  usb  or usbinvert    -  usb if high on signal and usbinvert if low (0v).  If this is not set properly it will not work or work in weird ways.

carrierfrom   works with pin 8 on the DMK-URI.   Pin 8 should go to the rigs cos output.

This is all in the setup docs at hamvoip.org  - did you read them?

73 Doug
WA3DSP
http://www.crompton.com/hamradio


From: ken at mirlaw.co.uk
To: arm-allstar at hamvoip.org
Date: Wed, 3 Jun 2015 17:26:16 +0100
Subject: Re: [arm-allstar] BBB node problems

Hi Doug, Thanks for the prompt reply, I have a static IP address 192.168.1.75 Here is the result from IP a Last login: Wed Jun  3 15:26:53 2015 from 192.168.1.80[root at bbb-allstar ~]# ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00    inet 127.0.0.1/8 scope host lo       valid_lft forever preferred_lft forever    inet6 ::1/128 scope host       valid_lft forever preferred_lft forever2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000    link/ether 78:a5:04:c8:d8:d6 brd ff:ff:ff:ff:ff:ff    inet 192.168.1.75/24 brd 192.168.1.255 scope global eth0       valid_lft forever preferred_lft forever    inet 192.168.1.70/24 brd 192.168.1.255 scope global secondary eth0       valid_lft forever preferred_lft forever    inet6 fe80::7aa5:4ff:fec8:d8d6/64 scope link       valid_lft forever preferred_lft forever All seems ok when I do asterisk –rvvv Verbosity is at least 3    -- Hungup 'DAHDI/pseudo-985034602'    -- Hungup 'DAHDI/pseudo-924804522'    -- Hungup 'DAHDI/pseudo-1001637878'    -- Hungup 'DAHDI/pseudo-1877326597'    -- Hungup 'DAHDI/pseudo-1381211970'    -- Hungup 'DAHDI/pseudo-1329465520'    -- Hungup 'DAHDI/pseudo-1997402920'    -- Hungup 'DAHDI/pseudo-423654540'    -- Hungup 'DAHDI/pseudo-106808402'    -- Hungup 'DAHDI/pseudo-1603112224'    -- Hungup 'DAHDI/pseudo-1147840309'    -- Hungup 'DAHDI/pseudo-1486191162' That’s just going through the keypad on my handheldWhen I try simpleusb-tune-menu I get “no such command”When I had vers. 1 I used usb radio, not simpleusb I’m not sure if that makes a difference Yes I do realise that it takes time to register the node and it shows as live on the asterisklink websiteIt will send my callsign out at intervals but no speech at all RegardsKen G0LCE From: arm-allstar-bounces at hamvoip.org [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of Doug Crompton
Sent: 03 June 2015 17:04
To: ARM Allstar
Subject: Re: [arm-allstar] BBB node problems Ken, 

 If it doesn't give the IP address then it is not getting one properly. 

At the Linux prompt of the BBB do

ip a

You should see an eth0 IP address there. It should be a valid IP address in your routers range. At boot the system should DHCP an address from your router unless you set it to static.

As far as tones and connections are concerned it will not connect anywhere if it does not have a good internet connection. You should check that the tones are being decoded properly though. Go into the asterisk client -

asterisk -rvvv

then watch the screen as you key up and push each tone. The proper response should  be seen on the screen. You should not get any bounces (double or more characters with one press) and each should decode properly. If not you either have a level problem (check your levels with simpleusb-tune-menu) or an equalization problem.

Because you apparently had your original V1.0 system working properly there is no reason why this one should not do the same. Perhaps you set something wrong in the setup in the IP address? Did you use static or DHCP?
You also need to wait up to 10 minutes at boot for the database to update at both ends before you can connect out.

I would recommend running the setup again from the beginning if you cannot get anywhere. Run  firsttime.sh at the BBB prompt.

73 Doug
WA3DSP
http://www.crompton.com/hamradio

From: ken at mirlaw.co.uk
To: arm-allstar at hamvoip.org
Date: Wed, 3 Jun 2015 15:38:30 +0100
Subject: [arm-allstar] BBB node problemsHi, I have finally got round to upgrading my bbb node to ver 1.2.1. It installed ok apart from the fact I cannot connect to anyone, any dtmf command I send to the radio returns a short tone and that is all.On my last setup a *7 would give me the status of the node likewise *3 and the node number would connect me. When the node first starts it gives my callsign in morse then I get a short tone a gap then a spoken “ip address” it doesn’t give the ip address The node number is 28468 and its callsign MB7ICE Ken  
_______________________________________________ arm-allstar mailing list arm-allstar at hamvoip.org http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/ 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150603/fa105c55/attachment.html>


More information about the arm-allstar mailing list