[arm-allstar] CTCSS detect ping-pong - stumped

[Doug Crompton]

Robert,

 That is a strange one. Question do you really need noise squelch and PL'ed
squelch? If you just need PL'ed squelch connect the CTCSS output of the
repeater to COS of input pin 8 of the DMK and select the appropriate phase
in simpleusb-tune menu for COS and the CTCSS set to no.

The inputs to the cm1xx chip have internal weak pullups, probably something
like 47K or more so it would be a high impedance to any input signal so I
can't imagine the chip actually having any influence on the input. Low is
anything under about .5v but you would want it to be as close to 0 as
possible.  Just to be sure there is no relation does this ping pong happen
when Asterisk is not running measured at the COS or CTCSS inputs? Also with
Asterisk running and the heartbeat going but both COS and CTCSS set to NO
or one or the other set to NO?


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Fri, Oct 26, 2018 at 10:10 PM "Robert Conklin via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Greetings all. I'm stumped on a ping-pong PTT issue when using ctcss detect
> output from my repeater's receiver.
>
> Here's the layout:
> Hamvoip 1.5 code, fresh image w/latest updates.
> DMK URI
> Motorola MTR2000 repeater in base mode. Programmed for PL on input and
> output.
> The MTR's CTCSS and COS detect outputs are active high (5vdc), I use a 10k
> resistor to pull them low when inactive.
> When using CTCSSFROM in usb mode, the CTCSS signal pin-pongs in fairly (not
> perfectly) regular intervals, at about 1Hz, thus the PTT ping-pongs with
> it. If I use COS, no ping pong. Transmission coming from telemetry or from
> links are unaffected so it appears to be a repeater issue.
> I scoped the COR and CTCSS signals and they appear completely identical in
> amplitude, accept the CTCSS signal drops in and out BUT it only does that
> when it's hooked up to the URI. That's the kicker, that CTCSS signal is
> solid as a rock when I take it of the URI. I tried another URI with the
> same result. I cannot see anything in the RSS programming for the MTR that
> would change that CTCSS pin's behavior.
> Would be very appreciative of any thoughts or ideas, thank you!
>
> --
> Robert Conklin
> *N4WGY <http://qrz.com/db/N4WGY>*
> _______________________________________________
>
> 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
>