[arm-allstar] Picket fencing (correction)

[Robert Newberry]

The only thing I have done is disable the courtesy tone. Unkeywait is 400.

One thing I am growing tired of is posting a question to this list and
immediately the assumption is that I had to have done something to screw up
your image.

It is entirely possible that you have not experienced every variable
possible. I've noticed I'm not the only one on this growing tired of your
immediate finger pointing.

N1XBM
Apparare Scientor
Paratus Communicare
Allstar Node # 27086, 41540, 41812, 42086

On Sep 18, 2015 1:03 PM, "Doug Crompton" <doug at crompton.com> wrote:

> Well if in band linking is setup correctly the PL from the repeater should
> follow the incoming station not the output of the repeater. The bottom line
> is it should not be doing what he says it is doing if timings were setup
> correctly. The COS might follow the longer duration flutter but not the
> transmit on his end which should be delayed somewhat from end of COS. You
> do not want 0 or near 0 tx unkeywait.
>
> I run an inband link here and I have not seen this problem. I am using
> basically stock timings and courtesy tone.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> From: n3fe at repeater.net
> Date: Fri, 18 Sep 2015 11:27:14 -0400
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Picket fencing (correction)
>
> 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.
>
> N1XBM
> 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
>
>
> _______________________________________________ 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
>
> _______________________________________________
>
> 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/20ab85da/attachment.html>