[arm-allstar] cop 48?

[David McGough]

Hi Stephen,

Yes, I expect the MDC code is likely impacted, too.

BTW, I've found a bug with submitting long COP argument sequences. This 
problem is in the app_rpt code, not the channel driver (simpleusb, etc.).
I'm looking for this problem now and will fix.

73, David KB4FXC



On Wed, 14 Mar 2018, Stephen - K1LNX wrote:

> Hi David,
>      For what it's worth, I believe I've seen these on MDC decodes as well.
> I'm not at home to double check, but I can.
> 
> I've always ignored them as there never seemed to be any operational
> impact.
> 
> 73
> Stephen
> K1LNX
> 
> On Mar 14, 2018 17:14, David McGough via arm-allstar <
> arm-allstar at hamvoip.org> wrote:
> 
> >
> > Almost as soon as I sent this message, I spotted a problem with Motorola
> > style paging sequences---silence periods, in particular (like: !0/100),
> > seem not to behave correctly. I'll take a look at this code.
> >
> > But, DTMF sequences, etc., seem fine to me.
> >
> >
> > 73, David KB4FXC
> >
> >
> >
> > On Wed, 14 Mar 2018, "David McGough via arm-allstar" wrote:
> >
> > >
> > > Hi Guys,
> > >
> > > I tested COP 48 and it seems to work properly for me----with the side
> > > effect of scrolling "USB may be stuck" messages for each 20ms audio
> > > frame....That warning can be ignored, it's just "noise" in this
> > situation.
> > >
> > > I just added a simple patch to the chan_simpleusb driver to hush those
> > > messages when they are bogus---they will still get printed for real
> > > situations where the USB interface is having problems.
> > >
> > > Also, by hushing those messages, it cleaned up some small audio glitches
> > > that got produced as a side effect of burning unneeded CPU cycles in that
> > > critical section of code.
> > >
> > > I'll include the simpleusb patch in the next package update, coming later
> > > today. This next package update includes yet another chan_echolink
> > update,
> > > improving stability even further.
> > >
> > > BTW, what tone sequences seemed to be causing problems?? Everything I've
> > > tested so far seems to work??
> > >
> > >
> > > 73, David KB4FXC
> > >
> > >
> > > On Tue, 13 Mar 2018, "David McGough via arm-allstar" wrote:
> > >
> > > >
> > > > Hi,
> > > >
> > > > Yes, COP 48 should work fine. Nothing related to that code has changed
> > > > recently. I'm not sure about the USB stuck messages.
> > > >
> > > > I'll test here...
> > > >
> > > > 73, David KB4FXC
> > > >
> > > >
> > > >
> > > > On Wed, 14 Mar 2018, "[UTF-8] Roger Coudé via arm-allstar" wrote:
> > > >
> > > > > We use cop 48Â to control some remote repeaters equipped with RLC
> > > > controlers.We see those error messages on the cli console, but the
> > tones
> > > > are ok on the air.We tried cop 48 on Xelatec and it caused astrpt to
> > > > crash.That is the main reason why we switched to allstar version a few
> > > > years ago.Roger
> > > >
> > > >
> > > >
> > > >       De : Ken via arm-allstar <arm-allstar at hamvoip.org>
> > > >  À : arm-allstar at hamvoip.org
> > > > Cc : Ken <ke2n at cs.com>
> > > >  Envoyé le : mardi 13 mars 2018 20h36
> > > >  Objet : [arm-allstar] cop 48?
> > > >
> > > > I have an RPI3 driving a single RIM interface and running the latest
> > update
> > > > (3/10/2018).
> > > >
> > > > I am trying to send some DTMF digits out the transmit audio port using
> > a
> > > > function that calls cop,48.
> > > >
> > > >
> > > >
> > > > The result is a whole string of  'USB may be stuck - not it's not
> > stuck "
> > > > messages on the CLI;Â  the tones may, or may not, go out and Asterisk
> > may
> > > > stop and need to be restarted.
> > > >
> > > >
> > > >
> > > > This is the first time I have tried to use this function, so I have to
> > ask:
> > > > is cop 48 supported by hamvoip? If so, is it broken in the latest
> > update?
> > > >
> > > >
> > > >
> > > > Ken
> > > >
> > > > KE2N
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > >
> > > > 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
> > > >
> > >
> > > _______________________________________________
> > >
> > > 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
> >
>