<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, linéale;font-size:13px"><div id="yui_3_16_0_ym19_1_1479397967113_4818" abp="3067"><br abp="3068">I maintain a large network of repeaters that extends to over 1000 km</div><div id="yui_3_16_0_ym19_1_1479397967113_5043" abp="3067">Many repeaters in our network are based on asterisk rpt.</div><div id="yui_3_16_0_ym19_1_1479397967113_5047" abp="3067">The hardest part of my job is to get rid of ping pong problem.</div><div id="yui_3_16_0_ym19_1_1479397967113_5046" abp="3067">The typical system would be a repeater with to links facing east and west directions, enabling a region to access the network and also relaying east-west conversations.</div><div id="yui_3_16_0_ym19_1_1479397967113_5045" abp="3067">According to the documentation, the RxOnDelay should be the solution to block ping pong, and it does.</div><div id="yui_3_16_0_ym19_1_1479397967113_5044" abp="3067">But the problem is that it also degrades communications that should not be affected.</div><div id="yui_3_16_0_ym19_1_1479397967113_5104" abp="3067">According to de definition, the RxOnDelay should occur after the release of PTT on a radio by disabling COR detection on the same radio for a certain duration.</div><div id="yui_3_16_0_ym19_1_1479397967113_5105" abp="3067">But what I observe is different: the delay applies as soon as the COR is released, even if there is no PTT applied.</div><div id="yui_3_16_0_ym19_1_1479397967113_5129" abp="3067">As an example, if there is a conversation on the east side, the direction of the traffic will only be from east to west.</div><div id="yui_3_16_0_ym19_1_1479397967113_5130" dir="ltr" abp="3067">There will not be any PTT applied to the radio facing east, so the RxOnDelay should not activate on that radio.</div><div id="yui_3_16_0_ym19_1_1479397967113_5177" dir="ltr" abp="3067">But I observe the RxOnDelay is actvated between each reception and even with picket fence, which is quite annoying.</div><div id="yui_3_16_0_ym19_1_1479397967113_5247" dir="ltr" abp="3067">At some locations, we need 500 to 1000ms to block squelch tail.</div><div id="yui_3_16_0_ym19_1_1479397967113_5246" dir="ltr" abp="3067">So if that delay should only occurs when the conversation switcth from east to west, not if it is on the same side.</div><div id="yui_3_16_0_ym19_1_1479397967113_5245" dir="ltr" abp="3067">The actual implementation is affecting the quality of the system in situations where it should not.</div><div id="yui_3_16_0_ym19_1_1479397967113_5320" dir="ltr" abp="3067">Roger</div><div dir="ltr" abp="3067">VE2DBE</div><div dir="ltr" abp="3067">www.ve2dbe.com</div><div id="yui_3_16_0_ym19_1_1479397967113_5131" dir="ltr" abp="3067"> </div><div id="yui_3_16_0_ym19_1_1479397967113_5178" dir="ltr" abp="3067"> </div><div id="yui_3_16_0_ym19_1_1479397967113_5172" abp="3067"> </div></div></body></html>