[arm-allstar] The RxOnDelay issue

[David McGough]

Hi Roger,

You've got an interesting idea for improving the operation of RxOnDelay. 
I'll definitely add this to the feaure request list and take a look at how 
to implement.


73, David KB4FXC



On Thu, 5 Jul 2018, "[UTF-8] Roger Coudé via arm-allstar" wrote:

> 

(I am sorry, there was an issue with characters sets in my last)The actual implementation of RxOnDelay in simpleusb is that it is applied each time the Rx keys on. That is overkill to prevent ping pong between remote systems since it is required only immediately after Tx unkey event.
The consequence is that when a mobile does not have a steady signal, each little break in the cor is translated into a long muting on the allstar net.
When a conversation is heard on a duplex=0 transceiver talking to a link-to-link repeater, if no party is involved behind (the radio only receives), there is no reason to have the RxOnDelay being activated.
On the other hand, if the conversion involves that a transceiver transmits toward the link-to-link repeater, the RxOndelay should starts just after Tx keys down, and expire after the proper delay to block the unwanted squelch tail.
The communications on our large network would be improved a lot. If you need the actual implementation to remain the same, then i would suggest a new parameter like «TailEliminator»
73Roger VE2DBE
_______________________________________________

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