[arm-allstar] Question about timing/responsiveness

[Chuck Kelsey]

I'll try to shed more light.

The original setup was using a desktop configured with Zipar. Same link 
radio for both configurations, so nothing there is different. It worked 
fine with that setup. The only change was going to a Raspberry Pi2.

The repeater is on a hardware-based controller (no Internet available). 
When a user brings it up, the repeater transmits PL the entire time the 
user is there. When the user unkeys, the PL stops encoding, but the 
repeater's hang timer keeps it transmitting for the predetermined 
length. During the hang time there is the courtesy tone and possibly ID 
(without tone).

Using the Raspberry Pi, I can sometimes hear a brief burst of the 
beginning of the repeater's courtesy tone. With the desktop 
configuration that did not happen. Again, using the Raspberry Pi it also 
sometimes "hangs" the AllStar side for a second or two. So there's two 
things happening with this part of the issue.

Hope this helps.

Chuck
WB2EDV





On 3/5/2016 1:08 PM, Doug Crompton via arm-allstar wrote:
> Chuck,
>
>  To start with the drop outs. This is more than likely an Internet 
> problem and that would be the first place to start looking. Not 
> knowing anything more about his system like what the Internet 
> connection is, etc. It would be hard to suggest anything.
>
> The other problem may or may not be related to a poor connection. When 
> the PL input to the repeater  drops it should immediately drop the COS 
> signal. The first place to check would be to make sure this is 
> happening. If there is some kind of delay in the repeater and COS is 
> staying true then it would have nothing to do with Allstar. When I say 
> "true" that could be a high or low depending on the configuration. Put 
> a meter on COS and key into the repeater and see how it follows.
>
> Again not knowing his configuration it is hard to know what is 
> actually happening. Is another controller in the loop? The best and 
> simplest way to use Allstar as a repeater controller is to do it 
> exclusively. The input PL drives COS  and the PTT output drives TX PTT 
> and TX PL. All the timing, ID's etc. are done in Allstar.
>
> *73 Doug
> WA3DSP
> http://www.crompton.com/hamradio*
>
>
> > To: arm-allstar at hamvoip.org
> > Date: Sat, 5 Mar 2016 12:40:13 -0500
> > Subject: [arm-allstar] Question about timing/responsiveness
> > From: arm-allstar at hamvoip.org
> > CC: wb2edv at roadrunner.com
> >
> > I'm new to this list, but didn't see this question addressed in the
> > archives.
> >
> > When using a Raspberry Pi2, as a link connection to a repeater, here's
> > what happens:
> >
> > The repeater transmits PL only during an active transmission (no tone
> > after user unkeys). However, there seems to be a slow response time for
> > the Raspberry to cease sending the transmission over AllStar when the
> > user drops key. It is causing the node at "the other end" to continue
> > transmitting as if there was a hang time.
> >
> > Also, when a user comes through from the AllStar network, there are
> > audio dropouts some of the time.
> >
> > This setup is not mine, I'm asking for a friend that owns it.
> >
> > Chuck
> > WB2EDV
> > _______________________________________________
> >
> > 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/20160305/7ef79876/attachment.html>