[arm-allstar] node insists on sending CW ID every idtime

[Doug Crompton]

Steve,

 If you are sending a Courtesy tone (nounkeyct=0) then it will give a tail
Courtesy tone at each key. This would be an RF key and count towards ID
time. Someone does not have to actually talk. So if someone kerchiunks the
repeater it will still ID. This would be the same on any repeater. You can
somewhat eliminate kerchunks by setting rxondely in simpleusb-tune-menu to
some value higher than the default 0.  5 might be a good number. Setting it
too high though will result in cutting off audio of a real station. The
timers in hamvoip Allstar are very accurate due to a change about a year
ago to use the high resolution timer on the Pi. So you could probably time
to the second the 10 minute timer and if you have multiple nodes connected
and can hear all their RF's they will ID at the same time.


*73 Doug*

*WA3DSP*

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


On Wed, Dec 12, 2018 at 5:47 PM "Steve Goldsmith via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> I spent a bit more time looking at this today and it seems that there’s a
> couple of things that are not behaving quite as expected with regard to the
> id timer.
>
> First, the ider_state (aka Identifier State) seems to be setting on
> receive from the rf channel rather than only when the node actually
> transmits on an rf channel.  Ie, if I kerchunk an allstar node’s rf
> channel, ider_state gets set to “QUEUED FOR CLEANUP” (rpt status Identifier
> State: QUEUED FOR CLEANUP).  This makes sense if I am running a full duplex
> node and always transmit on an rf channel when I receive.  However, if I am
> not keying a physical radio it shouldn’t be starting the id timer as I’m
> not transmitting on rf, therefore no need to identify on the rf side.
>  Seems that the id timer should be tied to when I transmit, not when I
> receive.
>
> Second, If I set idtime to 60000 (1 minute) and duplex=0 or 1 (only two i
> tested with) and then restart asterisk, the ider_state will get set to
> QUEUED FOR CLEANUP when I kerchunk the node.  When idtime is reached it
> will set to CLEAN (and if duplex=1 send cw id as expected). However, if you
> ignore it for at least 5 minutes, kerchunking the node no longer sets
> ider_state to QUEUED FOR CLEANUP, it stays CLEAN until the node transmits
> on the rf channel (say in response to *70). It will then set to QUEUED FOR
> CLEANUP if kerchunked again, until ignored for 5 minutes and then it stays
> CLEAN, so there’s another timer that is interacting with the id timer.
>
>
> --
> 73,
> /steve - W1HS
>
> _______________________________________________
>
> 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