[arm-allstar] Receive PL control with simpleusb

Cole Cunningham colecaz at gmail.com
Sun Mar 1 11:17:46 EST 2015


James,

 

Thanks for the suggestion.  I went back and looked at the schematic of our setup again with a different perspective and now see a circuit I can use to accomplish Rx PL control using IO lines and COP commands like yours.

 

Cole

AA7RD

 

From: arm-allstar-bounces at hamvoip.org [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of James K4JK
Sent: Sunday, March 01, 2015 5:43 AM
To: BeagleBone Black ARM Allstar
Subject: Re: [arm-allstar] Receive PL control with simpleusb

 

Cole,

 

You may have figured this out already but I was going through the archives and thought I'd chime in.

 

I think you're trying to accomplish what I've done with the repeater I'm building... I have a comm spec TS-64WDS that is connected to the discriminator of my receiver.

 

The TS-64 has a Mic Hang up feature that is designed to control whether the RX Mute Output pin goes into Channel monitoring mode. In the default configuration when the input pin for this feature (Pin 2, violet) is grounded the tone decode function on the tone board behaves normally. If you float or apply a voltage to this pin, the Channel Monitoring feature will turn on and the RX Mute output will behave as if the board is decoding CTCSS.

 

I use RX Mute Output #2 (Pin 7, Brown) for CTCSS input to the URI (Pin 7.) It grounds when the board is decoding CTCSS so I have ctcssfrom=usbinvert in my simplusb.conf.

 

Also in simpleusb.conf I have gpio2=out0, which initializes the GPIO pin and is hooked to pin 2 of the ctcss board.

 

I have a couple of commands in my rpt.conf that control this GPIO pin:

 

60=cop,62,GPIO2=0 ; Turn off GPIO 2

61=cop,62,GPIO2=1 ; Turn on GPIO 2

 

So *60 will enable CTCSS decode, *61 will put the repeater into carrier-only mode.

 

Eventually I will try to setup voice confirmation of the tone decode going on and off.

 

73

James

K4JK

 

 

 

 

On Wed, Feb 4, 2015 at 8:59 AM, Cole C <colecaz at gmail.com> wrote:

Ah,ha.  I believe you just told me the answer.  ctcssfrom=usb and carrierfrom=none changes receiver operation from carrier squelch control to CTCSS control.  Correct? We have a lot of noise spikes and momentary interference at our sites that override carrier squelch so we run CTCSS squelch almost always.

Now to figure out a macro to switch back and forth from COR to CTCSS via DTMF.

I understand the fob and simple usb don't decode or encode CTCSS.  We use Comm Spec encode/decode modules for CTCSS and thus have separate lines for COR and CTCSS. 

Thanks.
Cole, AA7RD


_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150301/d42e989d/attachment.html>


More information about the arm-allstar mailing list