[arm-allstar] Picket fencing (correction)

n3fe at repeater.net n3fe at repeater.net
Fri Sep 18 10:27:14 EST 2015

A few things to think about.  The repeater is only encoding during that active signal.  There for if they are picketing fencing there is a slight time duration to have it start encoding.  Then you have the Amount of time it takes the link radio to start decoding the pl.  that is one of the down falls of on band linking.  It does work but can act funny on mobile flutter, more so the higher the frequency where the wave length is shorter.

Corey  N3FE

Sent from my iPhone

> On Sep 18, 2015, at 10:59 AM, Robert Newberry <N1XBM at amsat.org> wrote:
> I thought about this more. So when my link radio is receiving traffic from the network it is in transmit. The remote audio coming from the network starts to picket fence because that person is in the fringe where ever they happen to be.
> So it appears when my link radio is hit in rapid fire succession attempting to TX that is where the problem is. I've noticed the URI has a recovery time switching from TX to RX. If a request comes during that recovery no TX will happen.
> I think I need a TX delay or hangtime to keep the node in TX when a user is "in and out" of a remote repeater.
> I hope this explains it better.
> Apparare Scientor
> Paratus Communicare
> Allstar Node # 27086, 41540, 41812, 42086
> _______________________________________________
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> Visit the BBB and RPi2 web page - http://hamvoip.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150918/6351adfa/attachment-0001.html>

More information about the arm-allstar mailing list