<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Doug,<br>
There is no other controller. The exec II is a mobile radio
converted to a repeater. It will be controlled directly with
allstar. I curently have 2 repeaters running on allstar and will
soon have 3 or 4 more running on allstar.<br>
<br>
Allstar will switch direction (usb or usb invert) but since the
radio gives +10v when unsquelched, I will need to make a buffer
because the raspberry pi needs to see the input go to ground.<br>
<br>
The TS64 signal is an open collector to ground so it interfaces
well with allstar.<br>
<br>
LaRoy McCann, K5TW<br>
<br>
<br>
<br>
<br>
On 5/13/2016 9:47 AM, Doug Crompton via arm-allstar wrote:<br>
</div>
<blockquote cite="mid:BLU171-W101DD78BB9DB3A14DD0E08EBA740@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr"><font style="" face="Tahoma,sans-serif"
color="#000000">LaRoy<br id="FontBreak">
</font><br>
I have never interfaced what you are talking about but I see no
reason why you would need the squelch input as well as PL. The
TS64 works well and the audio delay (squelch tail elimination)
setting in simpleusb.conf should get rid of any squelch tail. <br>
<br>
I assume you are using a separate repeater controller and not
using Allstar as the controller? If you are using Allstar you
can configure the COS direction. Also I thought maybe the TS64
had both high and low going outputs but maybe not. <br>
<br>
Allstar makes a great repeater controller but there are some
pros and cons to using it. The big pro is that you don't have to
worry about physical ports like you do on a dedicated
controller. Each port is a node and can be configured and
connected easily via SW, a big plus for Allstar. It is also a
lot less expensive. <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"><a class="moz-txt-link-freetext" href="http://www.crompton.com/hamradio">http://www.crompton.com/hamradio</a></font></b><font
style="font-size:16pt;" size="4"><br>
</font><br>
<br>
<div>> To: <a class="moz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
> Date: Fri, 13 May 2016 09:32:27 -0500<br>
> Subject: [arm-allstar] Using PL instead of COS<br>
> From: <a class="moz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
> CC: <a class="moz-txt-link-abbreviated" href="mailto:lmccann@dtisp.com">lmccann@dtisp.com</a><br>
> <br>
> I'm interfacing a ge mastr exec II to raspberry pi. I
have one I've <br>
> done previously where I have both cos and pl inputs.<br>
> <br>
> I'm going to have to make a cos buffer interface to
change the cos_high <br>
> from the radio to cos_low for the controller which is no
problem,<br>
> <br>
> We will always us PL on the input so I was wondering if I
could just get <br>
> by with using the TS64 PL signal for the cos input on the
controller?<br>
> <br>
> Does anyone know of any reasons not to use only PL signal
for cos?<br>
> <br>
> Would there be any longer squelch tail?<br>
> <br>
> <br>
> LaRoy McCann, K5TW<br>
> <br>
> <br>
> ---<br>
> This email has been checked for viruses by Avast
antivirus software.<br>
> <a class="moz-txt-link-freetext" href="https://www.avast.com/antivirus">https://www.avast.com/antivirus</a><br>
> <br>
> _______________________________________________<br>
> <br>
> arm-allstar mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
>
<a class="moz-txt-link-freetext" href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>
> <br>
> Visit the BBB and RPi2 web page - <a class="moz-txt-link-freetext" href="http://hamvoip.org">http://hamvoip.org</a><br>
> <br>
</div>
</div>
<br>
-- <br>
This message has been scanned for viruses and
<br>
dangerous content by the
<a moz-do-not-send="true" href="http://www.dtisp.com/"><b>DTISP
MailScanner</b></a>, and is
<br>
believed to be clean.
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
arm-allstar mailing list
<a class="moz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>
<a class="moz-txt-link-freetext" href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>
Visit the BBB and RPi2 web page - <a class="moz-txt-link-freetext" href="http://hamvoip.org">http://hamvoip.org</a></pre>
</blockquote>
<p><br>
</p>
<br />
<table style="border-top: 1px solid #aaabb6;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon" target="_blank"><img src="https://ipmcdn.avast.com/images/2016/icons/icon-envelope-tick-round-orange-v1.png" /></a></td>
<td style="width: 470px; padding-top: 15px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link" target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</table></body>
</html>