[arm-allstar] Confirmed node connect & disconnect bug

[Doug Crompton]

Chris,

 Did you put the "T" in the script as I directed? When a permanent connect
is lost it goes from transceive to a connect state.


*73 Doug*

*WA3DSP*

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


On Sun, Mar 18, 2018 at 7:29 PM, "chris novara via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Many hours of testing and with a second node in Washington state.
>
> If you use a startup macro to connect to your hub or node at boot all
> works fine and CT tones (and LED) change to the correct connected
> sound/light
>
> However,
> If the connection fails, the node auto retries (as it should) until the
> connection is resumed. Problem is, the CT tones and led scrip do not revert
> back to a disconnected tone!!  If supermon shows a red connection auto
> retry then CT tones are still linked even though connection is down....
>
> Only,
> If there is NO connections AND no retry attempts to connect, does the CT
> tone and led script revert back to unlink tone and no led light.
>
> So,
> How do we change this so even if the node is in auto retry mode that we
> don’t get a ct tone change (to linked)  UNTIL the node connection is
> established!
>
> This would fix the CT tone and led script that both don’t work if you use
> a startup macro using *73xxxxxxx
>
> Chris Novara
> Phone: 541-778-1175
> Eugene, Oregon
> Email-Chris at redcrosscommunications.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 web page - http://hamvoip.org