[arm-allstar] Picket fencing (correction)

Fri Sep 18 13:41:45 EST 2015

I am trying to help. I just pointed out that if those things were changed it could cause a problem so you would check it. If you TX is keying up and down at a rate faster than 400ms, which you say you have the unkeywait set to that then there is something else wrong. It is hard to understand when you don't describe exactly what the problem is and then change the problem mid stream.  The courtesy tone does add to the delay so maybe you need to up the unkeywait if you are not using it. The URI is just reading a bit (COS) and conveying it to the SW. It has a very fast response so it would follow any up or down from COS. If the COS is not giving a good high or low depending on which direction it goes for your radio that could also be an issue. It needs .5 volts or less for a low and greater than 2 volts for a high.
If you don't like my answer maybe you should go over on app_rpt and ask your question since it has nothing to do specifically with the RPi2 or BBB!!!!

73 Doug
WA3DSP
http://www.crompton.com/hamradio

Date: Fri, 18 Sep 2015 13:33:44 -0400
From: N1XBM at amsat.org
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] Picket fencing (correction)

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 Doug
WA3DSP
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

_______________________________________________

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/99e4ebc5/attachment.html>