[arm-allstar] Looping problem

[Patrick Perdue]

And also, if you can, use gated PL on the repeater such that only PL 
comes through with voice, not telemetry. This way, IDs, hangtime  and 
repeater tones won't come back across the network. If you can't directly 
connect the node to a controller and must use an RF link, this is the 
next best thing. Not only will this (hopefully) eliminate pingponging, 
it will also make things much more responsive for remote users.

This is a problem I see with many remote echolink connections. No gated 
PL, and driven by vox. Makes for a pretty painful experience.



On 5/5/2021 6:20 AM, "Don Rolph via ARM-allstar" wrote:
> Try setting duplex to 0.
>
> If you set duplex to 1, turn off courtesy tones with nounkeyct=1. This
> however results in ping ponging of the 10 minute id of the repeater and the
> AllStar node.
>
> This is a deep nagging problem with using AllStar on a repeater link.
>
>
>
> On Tue, May 4, 2021 at 7:45 PM "Mark Richardson via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> I am setting up an AllStar node with the plan to link it to our local
>> repeater by RF.
>>
>>
>>
>> Everything is working fine if I put the radio on a Simplex frequency, but
>> if
>> I use a Repeater split I get a looping where the radio cycles between
>> transmit and receive and a beep is heard with each cycle. It seems to begin
>> the first time the radio transmits and then continues.
>>
>> I'm hoping someone has encountered something like this before and will have
>> some suggestions for me.
>>
>>
>>
>> I am using a Standard GX3000V radio with a Masters Communications AR-35
>> interface and a Raspberry PI 3.
>>
>>
>>
>> Thanks in advance,
>>
>> Mark Richardson
>>
>> VA3OBO
>>
>>
>>
>> _______________________________________________
>>
>> 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
>>
>