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

David McGough kb4fxc at inttek.net
Thu May 21 22:40:08 EST 2015


Neil,

The solid (or no) blue LED, rather than the typical heartbeat, indicates 
the BBB has crashed.  Enabling the watchdog should help the BBB to reboot 
after a crash/lockup.

Note that almost all crash scenarios I've ever encountered were due to
either a poor quality 5V power supply or due to ground potential bumps on
the USB interface, via the URI adapter. Assuming that the BBB power is
separate from the radio/repeater power, one test to try is power-cycling
the radio power while watching for any BBB issues--there should not be any
interaction. If there is interaction, you need to improve the ground
bonding and/or USB isolation.

This is one area where the RPi2's are far supperior to BBB's---the USB is
MUCH less sensitive to bumps/surges.


73, David KB4FXC




On Thu, 21 May 2015, Neil k8it wrote:

> I will answer the questions when it happens again.
> I did notice that the BBB blue led becomes solid when it happens
> 73 neil k8it 41838 or echolink k8it-L
> 
> 
> 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
> 



More information about the arm-allstar mailing list