<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><font style="" color="#000000" face="Tahoma,sans-serif">OK, Understood. I just wanted to make the bits clear. <br><br>I have never personally used ctcssfrom or carrierfrom in conjunction wiith ctcssfrom but I understand from others that there are issues with it. The code is somewhat spaghetti and often hard to understand. We are working on clearing that up and may have a better resolution in the future.<br><br>I think what I would do if using the RPi2 is use a GPIO bit to achieve your goal. If there is a way to enable or disable the CTCSS with a level shift that would be easy to accomplish and even easier to actually use. The gpio commands we built into the RPi2 are so nice. <br><br>Say you want to turn something on or off or whatever with a bit. First select the bit. GPIO uses the wiringpi pinout but can also use the BCM standard pinout. To see the pins on the RPi2 do - <br><br>gpio readall<br><br>Suppose you want to use GPIO22 (wiringpi 3) actual pin #15 on the 40 pin connector. The commands would be -<br><br>gpio mode 3 out<br>gpio write 3 1|0 (1|0 meaning 1 or 0)<br id="FontBreak"></font><br><font style="" face="Tahoma,sans-serif">Easy to put in a script and call from a DTMF command</font><font style="" face="Tahoma,sans-serif">. </font><font style="" face="Tahoma,sans-serif"><br></font><br><font style="" face="Tahoma,sans-serif">Of course you can use the bits on the RPi2 to do lots of things both input and output</font>. <font style="" face="Tahoma,sans-serif">Just remember the bits are 3.3V level max and should not be directly couple to anything that goes above that level. </font><font style="" face="Tahoma,sans-serif"><br></font><br><font style="" face="Tahoma,sans-serif">Similarly if you are using the DMK-URI there are output bits on it that could be used to control external things.</font><br><br><font style="" face="Tahoma,sans-serif">I plan on doing a how-to on GPIO soon and in a few weeks or so we are coming out with an update of the RPi2 code which includes GPIO for PTT, COS, CTCSS.</font><br><br><b><font style="font-size:16pt;" size="4">73 Doug</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">WA3DSP</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">http://www.crompton.com/hamradio</font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div>> From: lmccann@dtisp.com<br>> To: arm-allstar@hamvoip.org<br>> Date: Fri, 15 May 2015 21:18:53 -0500<br>> Subject: Re: [arm-allstar] [Spam?] Re: Is CTCSS enable/disable possible using dtmf?<br>> <br>> Doug,<br>> I totally understand that the carrierfrom and ctcssfrom are just logic inputs.<br>> I know you can use either or both to trigger the controller to key-up.<br>> <br>> What I am trying to do is have the repeater normally only use just the carrier input to key the <br>> repeater. In times of band openings or interference, we want to require the additional use of ctcss <br>> along with carrier.<br>> <br>> I found the cop,56 and cop,57 commands to enable/disable the use of ctcss input.<br>> The only way I can make the commands work is to have ctcssfrom=usb in simple use.conf, then <br>> have the startup macro disable ctcss with the cop,57 command. This allows the repeater to <br>> startup without requiring carrier and ctcss input, just carrier input.<br>> I can then use the cop,56 command to enable the ctcss input.<br>> <br>> If I have ctcssfrom=no, I can not issue a cop,56 command to enable ctcss input required.<br>> Not sure if its suppose to work that way, but that is how it works.<br>> <br>> I could not find any documentation on the use of cop,56 and cop,57 but I finally figured out how it <br>> works.<br>> --<br>> LaRoy McCann, K5TW<br>> <br>> <br>> ---------- Original Message -----------<br>> From: Doug Crompton <doug@crompton.com><br>> To: ARM Allstar <arm-allstar@hamvoip.org><br>> Sent: Fri, 15 May 2015 21:22:47 -0400<br>> Subject: [Spam?] Re: [arm-allstar] Is CTCSS enable/disable possible using dtmf?<br>> <br>> > carrierfrom= and ctcssfrom= are really meaningless in that they <br>> > are just bits that are set high or low when an outside event occurs.<br>> > <br>> > We generally use carrierfrom= which corresponds to pin 8 of the DMK-<br>> > URI. It is just a bit that you read. This bit in turn is connected <br>> > to a receiver (transceiver) that asserts that bit either positive <br>> > (usb) or negative (usbinvert) with RX signal generally PL decoded.<br>> > <br>> > Some radios (not many) have the ability to provide both squelch and <br>> > CTCSS decode levels. This would allow you to connect both bits and <br>> > have the capability to turn off PL decode if desired by not "anding" <br>> > the two bits.<br>> > <br>> > In most cases you would use carrierfrom=usb|usbinvert that is <br>> > asserted when the RX receives the set PL tone. In simpleusb that <br>> > tone is set in the receiver or transceiver. CTCSS would be left set <br>> > to 'no'<br>> > <br>> > If you so desired you could use the ctcssfrom=usb|usbinvert (pin 7 <br>> > of the DMK-URI and set carrierfrom=no It makes no difference which <br>> > you use. We have just generally standardized in using carrierfrom <br>> > and leaving ctcssfrom set to no.<br>> > <br>> > Bottom line is they are just bits and neither have anything to do <br>> > with CTCSS directly. Both CTCSS encode and decode is done in your <br>> > transceiver or receiver/transmitter. 73 Doug WA3DSP http://www.crompton.com/hamradio<br>> > <br>> > Date: Fri, 15 May 2015 10:50:57 -0500<br>> > From: lmccann@dtisp.com<br>> > To: arm-allstar@hamvoip.org<br>> > Subject: Re: [arm-allstar] Is CTCSS enable/disable possible using dtmf?<br>> > <br>> > OK, I figured it out.<br>> > <br>> > I had ctcssfrom=no in simpleusb.conf.<br>> > <br>> > We normally would leave tone off, but want to turn it on if there<br>> > was interference issues.<br>> > <br>> > I was trying to turn ctcss on with the cop,56 command. This would<br>> > not work.<br>> > <br>> > But, If if set ctcssfrom=usb, then I can turn it off with the<br>> > cop,57 command.<br>> > <br>> > So, you can turn it off if it is on by default, but you can't turn<br>> > it on if it is off by default.<br>> > <br>> > Thanks,<br>> > <br>> > LaRoy McCann, K5TW<br>> > <br>> > On 5/15/2015 10:34 AM, Corey Dean wrote:<br>> > <br>> > I just looked at my configurations and these are what I<br>> > have for enable and disable. It does work as it should on<br>> > mine.<br>> > <br>> > 920=cop,56<br>> > <br>> > 921=cop,57<br>> > <br>> > Corey N3FE<br>> > <br>> > On Fri, May 15, 2015 at 11:29 AM, LaRoy<br>> > McCann <lmccann@dtisp.com><br>> > wrote:<br>> > <br>> > Corey,<br>> > <br>> > Thanks for the reply.<br>> > <br>> > I did not realize the reload only reloaded rpt.conf. <br>> > Good to know.<br>> > <br>> > As for enabling and disabling ctcss, it looks like there<br>> > should be someway to do that . Most dedicated repeater<br>> > controllers have that capability.<br>> > <br>> > I think I'll start digging thru the source to see if <br>> > I can figure out how it works.<br>> > <br>> > LaRoy McCann, K5TW<br>> > <br>> > On 5/15/2015 10:14 AM, Corey Dean wrote:<br>> > <br>> > I use those commands with no issues, but I am<br>> > also using DSP and Xipar on the node I do this on.<br>> > <br>> > the rpt reload will only reload the rpt.conf file. <br>> > The file you are changing is simpleusb.conf so the <br>> > rpt reload wouldn't read that.<br>> > <br>> > On Fri, May 15, 2015 at 11:10<br>> > AM, LaRoy McCann <lmccann@dtisp.com><br>> > wrote:<br>> > <br>> > I<br>> > posted this to the app_rpt list but got no<br>> > response so I am posting here.<br>> > <br>> > First, I am using RPI2 for the controller but I<br>> > think this is more a generic question than a<br>> > specific RPI2 question.<br>> > <br>> > I can set "ctcssfrom=usb" in simpleusb.conf and<br>> > then I have to use tone to make the controller<br>> > receive commands or key the repeater.<br>> > <br>> > After changing simpleusb.conf I issued the command<br>> > 'asterisk -rx "rpt reload"'. This would not make<br>> > ctcss be required to key the repeater.<br>> > <br>> > I had to 'astres.sh' before it would require tone<br>> > to key the repeater. Not sure if the 'asterisk<br>> > -rx "rpt reload"' should have worked or there <br>> > is a bug somewhere?<br>> > <br>> > Doing this shows that the CTCSS input does work.<br>> > <br>> > What I am actually trying to be able to do is <br>> > to enable/disable Rx CTCSS from dtmf commands.<br>> > <br>> > I have configured a function for the cop=56(Rx<br>> > CTCSS enable) and cop=57(Rx CTCSS disable)<br>> > commands.<br>> > <br>> > When I enter the dtmf for the cop=56 function the<br>> > controller talks back "rx pl ena", so I know <br>> > the function is working. But I can still <br>> > access the repeater without a CTCSS tone.<br>> > <br>> > Are cop=56 and cop=57 commands supposed to work<br>> > when using simpleusb.conf?<br>> > <br>> > I have searched and can not find any reference <br>> > to using these commands.<br>> > <br>> > LaRoy McCann, K5TW<br>> > <br>> > ---<br>> > <br>> > This email has been checked for viruses by <br>> > Avast antivirus software.<br>> > <br>> > http://www.avast.com<br>> > <br>> > _______________________________________________<br>> > <br>> > arm-allstar mailing list<br>> > <br>> > arm-allstar@hamvoip.org<br>> > <br>> > http://lists.hamvoip.org/cgi-<br>> > bin/mailman/listinfo/arm-allstar<br>> > <br>> > Visit the BBB web page - <br>> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> > <br>> > --<br>> > <br>> > This message has been scanned for viruses and<br>> > <br>> > dangerous content by the DTISP<br>> > MailScanner, and is<br>> > <br>> > believed to be clean.<br>> > <br>> > _______________________________________________<br>> > <br>> > arm-allstar mailing list<br>> > arm-allstar@hamvoip.org<br>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> > <br>> > Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> > <br>> > This email has been checked for viruses by Avast<br>> > antivirus software.<br>> > <br>> > www.avast.com<br>> > <br>> > _______________________________________________<br>> > <br>> > arm-allstar mailing list<br>> > <br>> > arm-allstar@hamvoip.org<br>> > <br>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> > <br>> > Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> > <br>> > --<br>> > <br>> > This message has been scanned for viruses and<br>> > <br>> > dangerous content by the<br>> > DTISP<br>> > MailScanner, and is<br>> > <br>> > believed to be clean.<br>> > <br>> > _______________________________________________<br>> > <br>> > arm-allstar mailing list<br>> > arm-allstar@hamvoip.org<br>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> > <br>> > Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> > <br>> > <br>> > <br>> > <br>> > <br>> > <br>> > <br>> > <br>> > <br>> > This email has been checked for viruses by Avast antivirus software.<br>> > <br>> > www.avast.com<br>> > <br>> > <br>> > <br>> > <br>> > _______________________________________________<br>> > <br>> > arm-allstar mailing list<br>> > arm-allstar@hamvoip.org<br>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> > <br>> > Visit the BBB web page - <br>> > http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/ <br>> > -- <br>> > This message has been scanned for viruses and<br>> > dangerous content by the DTISP MailScanner, and is<br>> > believed to be clean.<br>> ------- End of Original Message -------<br>> <br>> _______________________________________________<br>> <br>> arm-allstar mailing list<br>> arm-allstar@hamvoip.org<br>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> <br>> Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> <br></div> </div></body>
</html>