<div dir="ltr">Thanks Bryan, let's try this again... my original email was a total edit fail lol.. so I can see where it would be confusing. I had first sent this to someone else prior to posting to the list. <div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">is your xmtr on the rtcm or are you using voted receivers and one xmtr directly connected to a URI?</span></blockquote><div><br></div><div>I am running a pair of CDM1550's UHF in full duplex off of an RTCM. The URI will be used to for another yet be implemented application, but the idea was to use one of the GPIO pins from it to drive my fan. </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div style="font-size:12.8px">Are you running the background script that k0kn has on his website? just because you set the gpio pins and the event subsystem sets the flag, asterisk doesn't directly flip those pins; you need a separate control script to do what you need, which is sense that the tx flag has been set (the file in /tmp), output a command to close the relay, and then unset the pin when the flag gets erased and back to idle when done.</div></blockquote><div> </div><div>Copy that... my issue is that I can't get past the first part, the event management subsystem does not appear to be picking up the key/unkey events. When I have played around with this in the past on a URI and simpleusb, I would see debug messages indicating as such on the Asterisk console. </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">google k0kn for the scripts from the source, not someone's interpretation (however well meaning, it is what HE did and may not be useful for your particular situation).</span><br style="font-size:12.8px"><br style="font-size:12.8px"><span style="font-size:12.8px">Been running k0kn's scripts to drive fans (and some other things: relay logic has a certain solid feeling to do things like turn things on and off...) since '11...hasn't failed yet. Go to the source, and build from there.</span></blockquote><div><br></div><div>Got those already. </div><div><br></div><div> David McGough wrote: </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">Here is another simple solution, rather than using a relay, etc....Just</span><br style="font-size:12.8px"><span style="font-size:12.8px">use a high-efficiency DC-DC switcher that includes a logic-level</span><br style="font-size:12.8px"><span style="font-size:12.8px">enable/disable. I'm using a handful of quarter-sized boards similar to</span><br style="font-size:12.8px"><span style="font-size:12.8px">these:</span><br style="font-size:12.8px"><br style="font-size:12.8px"><a href="http://www.ebay.com/itm/310925788373" rel="noreferrer" target="_blank" style="font-size:12.8px">http://www.ebay.com/itm/310925788373</a></blockquote><div><br></div><div>Those are pretty neat! I've run into similar, I actually just replaced the relay board I was going to use with one of these instead, it's a 3 output MOSFET breakout board that will turn on each output with 2.5v or higher on the microcontroller pins: <br><br><a href="http://www.ebay.com/itm/301357646243?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT">http://www.ebay.com/itm/301357646243?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT</a></div><div><br></div><div>I haven't tried it yet, but it looks very promising. The relay board I had was giving me fits with the GPIO pins so I started searching for a replacement and decided to give this a try instead. I will miss the click sound though... or well maybe not ;) <br><br>So in summation, pair of radios running full duplex on an RTCM, trying to use the event management subsystem to toggle a GPIO pin off a URI. As explained above, I can not appear to get the event debug messages to show up in the asterisk console on key/unkey events. That leaves me to the guessed conclusion that either my configs are wrong (they don't appear to be) or chan_voter does not talk to the event management subsystem? </div><div><br></div><div>73</div><div>Stephen</div><div>K1LNX</div><div> </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 1, 2016 at 10:35 PM, Bryan D. Boyle <span dir="ltr"><<a href="mailto:bdboyle@bdboyle.com" target="_blank">bdboyle@bdboyle.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>is your xmtr on the rtcm or are you using voted receivers and one xmtr directly connected to a URI?</div><div><br></div><div>Are you running the background script that k0kn has on his website? just because you set the gpio pins and the event subsystem sets the flag, asterisk doesn't directly flip those pins; you need a separate control script to do what you need, which is sense that the tx flag has been set (the file in /tmp), output a command to close the relay, and then unset the pin when the flag gets erased and back to idle when done.</div><div><br></div><div>Since hams are notoriously cheap, the circuit to control a relay with a gpio pin is on DMK's website. About $5. in parts if you don't already have them.</div><div><br></div><div>google k0kn for the scripts from the source, not someone's interpretation (however well meaning, it is what HE did and may not be useful for your particular situation).<br><br>Been running k0kn's scripts to drive fans (and some other things: relay logic has a certain solid feeling to do things like turn things on and off...) since '11...hasn't failed yet. Go to the source, and build from there.<br>--<div>Bryan</div><div>Sent from my iPhone 6S.<span style="font-size:13pt">..No electrons were harmed in the sending of this message.</span></div><div><br><div><br></div></div></div><div><div class="h5"><div><br>On Aug 1, 2016, at 20:57, Stephen - K1LNX <<a href="mailto:k1lnx@k1lnx.net" target="_blank">k1lnx@k1lnx.net</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div>Hey guys... I have a fan on the transmit radio, but as I don't want to run it all the time, only when transmitting, I'm going to drive a relay from a GPIO pin off of a URI instead. I found two excellent resources as a basis for what I'm after: <br></div><div><br></div><div><a href="http://www.qsl.net/k0kn/txfan" target="_blank">http://www.qsl.net/k0kn/txfan</a><br></div><div><a href="http://latinovoip.net/allstar-and-the-gpio-fan-script-for-dmk-engineering-uri/" target="_blank">http://latinovoip.net/allstar-and-the-gpio-fan-script-for-dmk-engineering-uri/</a><br></div><div><br></div><div>I setup the following in my node stanza:</div><div><br></div><div>[2376]</div><div>events = events2376</div><div><br></div><div>[events2376]</div><div><div>touch /tmp/RPT_TXKEYED2376 = s|t|RPT_TXKEYED</div><div>rm -f /tmp/RPT_TXKEYED2376 = s|f|RPT_TXKEYED</div></div><div><br></div><div>As you can see, this is pretty simple, write RPT_TXKEYED2376 when the RPT_TXKEYED variable is true, remove when false. I even checked for the presence of those variables when the repeater is keyed/active from doing a "rpt showvars 2376":<br></div><div><br></div><div><div>as2376*CLI> rpt showvars 2376</div><div>Variable listing for node 2376:</div><div> XX_RPT_TXKEYED=1</div><div> RPT_ETXKEYED=1</div><div> RPT_TXKEYED=1</div><div> RPT_RXKEYED=1</div><div> RPT_NUMLINKS=0</div><div> RPT_LINKS=0</div><div> RPT_NUMALINKS=0</div><div> RPT_ALINKS=0</div><div> RPT_AUTOPATCHUP=0</div><div> -- 9 variables</div></div><div><br></div><div>Everything suggests this should work, but it is not for whatever reason, which leads me to two possible guesses: </div><div><br></div><div>- the logic is not placed correctly where it needs to be in rpt.conf</div><div>- chan_voter does not talk to the event management subsystem</div><div><br></div><div>Any ideas? Kinda lost... </div><div><br></div><div>Thanks, </div><div>Stephen </div><span><font color="#888888"><div>K1LNX</div><div><br></div></font></span></div>
</div><br></div>
</div></blockquote></div></div><blockquote type="cite"><div><span>_______________________________________________</span><br><span>App_rpt-users mailing list</span><br><span><a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a></span><br><span><a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a></span><br><span></span><br><span>To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"</span><br><span>You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. </span></div></blockquote></div></blockquote></div><br></div>