is your xmtr on the rtcm or are you using voted receivers and one xmtr directly connected to a URI? 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. 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. 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). 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. -- Bryan Sent from my iPhone 6S...No electrons were harmed in the sending of this message.
On Aug 1, 2016, at 20:57, Stephen - K1LNX <k1lnx@k1lnx.net> wrote:
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:
http://www.qsl.net/k0kn/txfan http://latinovoip.net/allstar-and-the-gpio-fan-script-for-dmk-engineering-ur...
I setup the following in my node stanza:
[2376] events = events2376
[events2376] touch /tmp/RPT_TXKEYED2376 = s|t|RPT_TXKEYED rm -f /tmp/RPT_TXKEYED2376 = s|f|RPT_TXKEYED
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":
as2376*CLI> rpt showvars 2376 Variable listing for node 2376: XX_RPT_TXKEYED=1 RPT_ETXKEYED=1 RPT_TXKEYED=1 RPT_RXKEYED=1 RPT_NUMLINKS=0 RPT_LINKS=0 RPT_NUMALINKS=0 RPT_ALINKS=0 RPT_AUTOPATCHUP=0 -- 9 variables
Everything suggests this should work, but it is not for whatever reason, which leads me to two possible guesses:
- the logic is not placed correctly where it needs to be in rpt.conf - chan_voter does not talk to the event management subsystem
Any ideas? Kinda lost...
Thanks, Stephen K1LNX
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" 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.