[arm-allstar] Hang Time (?) Problem - K5FOY
Doug Crompton
wa3dsp at gmail.com
Sun Dec 11 20:55:12 EST 2016
John,
You said this -
(1) Checked COS voltage. Changes from .5 to 2.7V upon receipt of a signal.
But the key thing is does it return to .5 right at the loss of signal or
very close to it. You need to check this because Allstar's COS determines
end of signal on that voltage going back low. If it is not then that is
your problem.
As for wifi problems - this would have nothing to do with an RF incoming
signal on an Allstar repeater listening on the output of that same
repeater. Over the network it might be a different story but if the audio
is clean thru the network the control signals should be working OK.
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Sun, Dec 11, 2016 at 4:44 PM, "John via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> Thanks for the guidance, Doug. So far, no joy.
>
> *Summary of problem:*
>
> If Dave is in QSO with another station, when that station stops
> transmitting, PTT on his node stays up for 10 seconds after the individual
> stops transmitting. Since it is a simplex node, this makes operation
> difficult.
>
> *What he has done:*
>
> (1) Checked COS voltage. Changes from .5 to 2.7V upon receipt of a signal.
> (2) Tested squelch. Squelch was off, but it WAS working correctly with the
> squelch off. Node is normally in CTCSS operation.
> (3) Checked all wiring including connectors and plugs. Shortened wires
> where possible, added ferrite chokes.
> (4) Turned off all other devices on the wireless network to check for
> interference. Tried a different router. Then tried the node with a direct
> ethernet connection.
>
> *Other Info (potential clues?)*
>
> If Dave uses the IAX-Rpt client into his node rather than coming in via RF,
> everything is fine - no delay.
> If he issues *70 for node status the node returns "repeat only". The node
> number is not heard. If he is logged in with the IAX client, the audio is
> heard correctly. The same is true for any command that returns audio. For
> instance, if he keys *A1 - it returns only part of the IP address.
>
> Any other thoughts?
>
> Thanks!
>
> John
>
>
>
> On Thu, Dec 8, 2016 at 10:44 AM, "Doug Crompton via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > John,
> >
> > It is possible that his hardware COS signal is not dropping for some
> > reason. This often happens with squelch problems and noise on the input.
> I
> > am assuming he is using simpleusb and hardware COS from the radio.
> >
> > The first thing to do is check the COS line - pin 8 on the DMK-URI - and
> > see if it follows his input signal to the node. There could be a slight
> > delay measured in milliseconds on key up/down but it should not be long.
> >
> > If that looks fine then we will go on with other things but if nothing
> else
> > changed I am guessing that is what it is. If it does turn out to be that
> > then you need to look at what the node RX is doing when he unkeys. Turn
> the
> > volume up on the node radio and listen. He should be using PL. Even if he
> > is using PL the squelch needs to be set properly.
> >
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Thu, Dec 8, 2016 at 12:32 PM, "John via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > I'm attempting to assist a friend with a problem that started on his Pi
> > > node about a month ago. It acts as if the hang-time was increased to
> > about
> > > 10 seconds. Because it is a simplex node, he has to wait for transmit
> to
> > > drop on every transmission. He had not made any software changes to his
> > > node when the problem occurred. He tried booting with his backup SSD
> > (from
> > > a time when everything was working properly) and still had the same
> > > problem. He has added toroids on wires and cables - no change. The
> delay
> > is
> > > evident both on Allstar connections and Echolink. He is using a DMK URI
> > > attached to a 2 meter mobile.
> > >
> > > Any thoughts on how to continue to troubleshoot this problem would be
> > > greatly appreciated.
> > >
> > > Thanks!
> > >
> > > John
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 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/3 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/3 web page - http://hamvoip.org
>
>
More information about the arm-allstar
mailing list