[App_rpt-users] Command Mode Timeout

Kent Ochs kentochs at sbcglobal.net
Wed Dec 26 21:16:19 EST 2012

Our repeater (A two node system consisting of VHF 27833 node linked to a UHF receiver on node 1998) recently experienced a random false dtmf *40 decode.  This put the repeater into transmit mode.  What bothers me most, is that while in command mode, the transmit timeout parameter (totime) appears to be ignored, not good if there isn't someone around that knows to send "#" or otherwise shutdown the machine.  In normal operating mode, totime works as expected, and try as I may, I have not been able to find a "command mode timeout" parameter.  

Have I missed or mis-configured something to cause this behavior?  

Is there a problem with the command function not honoring the transmit timeout parameter?  

I understand that *4 is a mandatory command, but could someone enlighten me as to why I shouldn't just disable this command altogether?

An inquired mind wants to know and appreciates your feedback.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20121226/991233b9/attachment.html>

More information about the App_rpt-users mailing list