[arm-allstar] TX time out

[Doug Crompton]

Matt,

 It is a pretty rare occurrence for this to happen without the disconnect conditions I pointed out. I suppose there could be some instability in your system due to other things. The number one problem is power supply issues but that to is also rare. Also outside RF sources such as Higher power HF or VHF/UHF. These frequencies can couple into long leads. Using ferrite chokes on all leads has helped.

It also could be the radio. Malfunctioning there could cause the COS output signal to hang. 

There is no log entry that would tell you anything other than COS was asserted which you of course already would know. If it was external from an external source Allstar would have no knowledge of whether it was truly a valid COS or not. 
73 Doug
WA3DSP
http://www.crompton.com/hamradio


Date: Sat, 27 Aug 2016 06:49:49 +0100
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] TX time out
From: arm-allstar at hamvoip.org
CC: matt at m0lmk.co.uk



Thanks for the 
comprehensive reply Doug. I appreciate the time it must take to help out
 with everyones issues.



I can confirm that the node radio was not turned off at any time. Is 
there a log somewhere that may show why the node went into this mode?



I'll set the rx_timeout down to 3 minutes just as a precaution and my 
radio (Motorola GM340) already has a 3 minute time out so that should be
 all good to go.



Thanks,



Matt

M0LMK





 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160827/55cf362e/attachment-0001.html>