[arm-allstar] how can i determine why a bbb node goes to sleep

Fri May 22 17:02:47 EST 2015

Neil,

 It is often hard to diagnose problems like this remotely. If you are running the 1.2.1 BBB version the green light stopping blinking should not happen. Test this by removing the USB to the DMK-URI on a working system. When you plug it back in it should recover and start blinking again. I suspect it will because I think this problem is not in the USB. If you are losing Ethernet (login) also then it is a more serious problem.

The Internet should have nothing to do with the RF side not working. What you are seeing is obviously not normal and not usual by any means. It could be a bad power supply to the BBB. It could be a bad image. It could be bad hardware - the BBB itself. Often the only way to find out is to substitute. I would start with a different power supply. That is the most critical on the BBB.

Another thing you could try is another SD card. Put the card you have programed aside and a minimal setup just to get you registered and able to connect. Run that for a few days and see if it happens again.

There is no easy fix. You need to take it one step at a time. I am sorry you are having this problem. There are hundreds of BBB's out there running Allstar and it is not something that I have ha reported to me before.

If you do decide to buy another board make it an RPi2. Not that there is anything wrong with the BBB but any future buys should be the RPi2.
73 Doug
WA3DSP
http://www.crompton.com/hamradio

From: k8it at cac.net
To: arm-allstar at hamvoip.org
Date: Fri, 22 May 2015 14:15:17 -0400
Subject: Re: [arm-allstar] how can i determine why a bbb node goes to sleep

it happened again. I checked it about 16 hours of on time and all was well. 
now the status shows that the node is not online.
The beagle bone blue led is flashing but the URI light green  is solid 
on. I have no linux login when I try to connect using putty. so by my estimate 
it occurred in the last 3.5 hours. the on time should be about 19.5 hours if it 
was working. The node has no output right now.
I just rebooted the node about 2pm Eastern time and all is well and it is 
back online.
My daughter did tell me that the internet did get real slow for a few 
minutes when we where out.
Could this be the cause? and if so what can I do to tell the BBB to retry 
the internet connection until it reconnects, and why would this lock up the rf 
side of the simplex node? id;s for example should still work.

73 Neil k8it 41838

From: Doug Crompton 
Sent: Thursday, May 21, 2015 10:39 PM
To: ARM Allstar 
Subject: Re: [arm-allstar] how can i determine why a bbb node goes 
to sleep

Neil,

There is 
nothing that should go to sleep on the BBB or RPi2 assuming you are using a 
wired connection. I do have some questions about what you mean by going to 
sleep.

Do you lose connection to the linux prompt or just the local 
connection via radio?

If you do have the linux prompt can you ping to 
somewhere and get a response?

ping ucsd.edu

I am not sure if you 
can answer this question but does the blinking green light on the USB FOB go 
solid or out when this happens?

If 
you go into the Asterisk client can you see the hungup line when you release the 
PTT of the radio you are talking to your node with?

Does the node ID or give any output when this "sleep" 
happens?

In the Asterisk 
client  you can key and unkey the radio manually to see if you have 
control. The command is -

susb 
key   
susb unkey

This should key the radio and turn on the red PTT LED. 
Make sure to unkey.

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

From: k8it at cac.net
To: arm-allstar at hamvoip.org
Date: Thu, 21 May 2015 
22:06:47 -0400
Subject: [arm-allstar] how can i determine why a bbb node goes 
to sleep

I have noted a "sleeping node" or node lockup issue 
after extended hours of no activity. I try to key up the node when this occurs 
and get nothing. the status of the node shows connected and not keyed up. the 
timing of these sleeping periods seem random. some people have suggested 
starting a cron job to reboot on a regular schedule. rebooting the node does 
bring it back 100%
Are there any thoughts or best practices to 
share?
73 k8it 41838 or Echolink k8it-l

_______________________________________________ 
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/ 

No virus found in this 
message.
Checked by AVG - www.avg.com
Version: 2015.0.5941 / Virus 
Database: 4347/9837 - Release Date: 05/22/15

_______________________________________________

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/20150522/9302373a/attachment.html>