[arm-allstar] The word locked (or blocked) every few minutes

[Kevin Custer]

CTCSS decoders will false - its a fact of the matter.  How frequently 
depends on several things - that I won't get into - unless you want me to.

If you didn't see COS becoming activate - maybe you're only using the 
CTCSS logic signal to tell the application that the receiver is active.  
ASL is written to act upon COS and CTCSS as logic "AND", and if 
configured correctly - requires BOTH COS and CTCSS logic signals to be 
present to validate receiver activity.  Doing so usually cuts down on 
the squelch crash at the end of a transmission as it usually takes much 
less time for COS to change states as compared to CTCSS - due to the 
flywheel effect.  You only need to lose one of the two to invalidate 
receiver activity.

Kevin W3KKC

On 11/29/2023 3:22 PM, John Hogenmiller via ARM-allstar wrote:
> Thanks for the replies. I do indeed have a brandmeister bridge. And the
> repeater in question is a 6m and at times does seem to pick up sporadic
> kerchunking, even with the pl tone.
>
> In this case, I didn't see COS activate, but everything else fits. We've
> had other issues with this repeater and have to hard power cycle the entire
> setup every few months.
>
> Thanks for the feedback.
>
> John/kb3dfz
>
>
>
> On Wed, Nov 29, 2023, 11:15 Dustin Perdue <borrisinabox at gmail.com> wrote:
>
>> Sounds like something on your system is connected to Brandmeister via
>> MMDVM.
>> It does that when you key up more than 5 times in 30 seconds.
>>
>> Sent from my zippo
>>
>>
>>> On Nov 29, 2023, at 09:50, John Hogenmiller via ARM-allstar <
>> arm-allstar at hamvoip.org> wrote:
>>> I need some help troubleshooting a weird issue.
>>>
>>> We have this occasional issue, including this morning where all 4 of our
>>> linked repeaters will key up seemingly at random every few minutes and
>> say
>>> the word "locked".  It's possible it's the word "blocked" with the "b"
>>> being cut-off because the word is said immediately on key-up.
>>>
>>> If I watch the supermon pages or the asterisk cli with rpt debug level 5,
>>> this is not being caused by COS or anything on the RF side.  I can't
>> really
>>> see anything corresponding to the actual key-ups themselves.  This
>> happened
>>> once a month ago, we tried restarting asterisk and it eventually went
>> away.
>>> This morning it happened again, but didn't go away and I did some further
>>> diving in.
>>>
>>> When the message plays, the only thing I see on the asterisk CLI is a
>>> hangup like this:
>>>
>>>     -- Hungup 'DAHDI/pseudo-1140051181'
>>>
>>> I did isolate it to one individual repeater controller.   Once I unlinked
>>> that controller, then I can isolate the issue to just that repeater.
>>> Restarting asterisk doesn't resolve it.  This repeater doesn't get much
>>> traffic, so I can shut asterisk down. Power cycling may or may not
>> resolve
>>> the issue for a few weeks, but I'd really like to figure out what's
>>> throwing out the "locked/blocked" message.
>>>
>>> Thanks in advance,
>>> John/KB3DFZ
>>> _______________________________________________
>>>
>>> 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