[arm-allstar] Rx On Delay Future Implementation
wa3dsp at gmail.com
Mon Mar 18 15:10:31 EDT 2019
This could be easily done but I am not understanding the utility of having
to wait 5 seconds to be able to talk. That is an eternity and seems like
it would cause more trouble then help. What system needs 5 seconds to
propagate a keyup? It seems more like a system problem that should be
corrected. So if someone keys up they have to wait 5 seconds to talk? You
know that the majority of people will have 5 seconds of their audio cutoff
if they don't do that and it totally precludes moderately fast back and
On Mon, Mar 18, 2019 at 3:05 PM "Henry Hamblin via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
> As a multiple repeater system owner, I would like the ability to extend
> the Rx On Delay beyond what the firmware currently allows, approx 2
> seconds. I realize that this is more than a sufficient amount for a vast
> of nodes, but if your node is connected to a repeater or multiple
> then you know some situations that the extra delay would be an asset.
> If the Max delay could be extended to 250, 5 seconds, that would be great.
> I am well aware of the drawbacks of an extended Rx on delay, but I feel
> in some situations that repeater system operators experience, the delay
> would outweigh the disadvantage.
> I really appreciate all of the time and effort that goes into the ham.voip
> All Star image. Great job by the ham.voip development team.
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
More information about the ARM-allstar