[arm-allstar] Tx/Rx Timeout Revisited

[Doug Crompton]

A note on timeouts as I think there may be some confusion about them.
Hamvoip has BOTH TX and RX timeouts. In addition most radios also have TX
timeouts.

Since most repeaters typically have 3 minute timeouts the TX timeout in
Hamvoip is often set to 3 minutes. Times are in milliseconds so this would
be 180000.  The RX timeout is used to protect a channel from a errant
lockup due to someone either inadvertently or purposely holding key down
(COS keyed). This is generally set to some value greater than 3 minutes.
When this happens the RXKEY to the world is dropped until it clears. This
essentially takes this node offline until the problem is cleared freeing
other connections to operate normally.

Hardware TX timeouts are set in your rig and would be a backup to the SW TX
timeout Hamvoip provides. They are typically set to something greater than
the SW timeout, say  4 minutes in the above case.

RX and TX timeouts are settable in rpt.conf and have millisecond resolution
which is way more than needed but very accurate.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Tue, Jun 2, 2020 at 11:48 PM "Tony via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Greetings David,
>
> May I be involved with the testing please? My Icom ID-51 has Tx timeouts
> of 1,3,5 mins. etc., but I could very much use finer granularity with an
> Rx timeout. I was informed by a CO yesterday that my 180 sec. TOT
> exceeded that of several ASL 2560 linked repeaters.
>
>      Tony  W7EFS
>
> On 6/1/20 3:19 AM, "David McGough via ARM-allstar" wrote:
> > Hi David,
> >
> > Okay, you asked for it!
> >
> > This feature has been in the To-Do queue for a while, with some test code
> > already in recent alpha releases.  I went ahead and completed this code,
> > so that it exposes both TX and RX/COS timeouts to the rpt events
> > mechanism, from which you can run scripts, etc.  I've tested it fairly
> > well and it seems to work, so I moved the package to the beta repository.
> > We'll do a little more testing some production systems, before full
> > release.
> >
> > If you would like to try this code now, send me a direct e-mail, and I'll
> > explain how to install (it's easy) and how to use the features. And,
> maybe
> > give me some feedback as to whether it solves your problems....
> >
> >
> > 73, David KB4FXC
> >
> >
> >
> >
> > On Sun, 31 May 2020, "kg5rdf via ARM-allstar" wrote:
> >
> >> Using Allstar for repeater controllers, I having issues not having down
> > time after timeout. I looked through everything but it hard coded. Is it
> > possible for tx/rx timeout not to call ulaw, but rather call a
> > script? With 24 repeaters in the system, its possible for a failure to
> > dead key the system. Non allstar controllers got this handled with down
> > time. Thanks David KG5RDF
> > _______________________________________________
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
> >
> > _______________________________________________
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
>
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org