# GPIO fan control script now available **URL:** \ **Category:** AllStarLink\ **Created:** [January 29, 2012, 2:41am UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244 "2012-01-29T02:41:04Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![K0KN](https://community.allstarlink.org/user_avatar/community.allstarlink.org/k0kn/32/1887_2.png) [@K0KN](https://community.allstarlink.org/u/K0KN)\ **Post date:** [January 29, 2012, 2:41am UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/1 "2012-01-29T02:41:04Z")
Hello, I spent some time today modifying the fan control script TXFAN, and am happy to say that I've managed to get it working under app\_rpt. I'm sure that there is a more elegant way to accomplish this in software, but as I mentioned before, I'm no programmer. For those that are interested, this script is used to control a cooling fan via GPIO. I am using the parallel port, but I'm sure USB GPIO would also work. No modifications to node radios is required, and because the fan is controlled via GPIO, the fan may be manually turned on or off via DTMF, macro, or script. I am currently using this script with 3 RF nodes and a single large fan. Add the following to the events stanza for any/all of your RF nodes: touch /etc/asterisk/~pttstate = s|t|RPT\_TXKEYED rm -f /etc/asterisk/~pttstate = s|f|RPT\_TXKEYED The script TXFAN runs in a background process, and will activate the fan after X seconds of transmitting. The fan will continue to run until X seconds after transmitting ceases. The modified TXFAN script can be found at: [http://www.qsl.net/k0kn/txfan](http://www.qsl.net/k0kn/txfan) Sample GPIO control scripts are also available: [http://www.qsl.net/k0kn/aux1on](http://www.qsl.net/k0kn/aux1on) [http://www.qsl.net/k0kn/aux1off](http://www.qsl.net/k0kn/aux1off) 73, Kyle Yoksh K0KN Olathe, KS Allstar 2210-2219 ---
**Author:** ![Bryan\_D\_Boyle](https://community.allstarlink.org/user_avatar/community.allstarlink.org/bryan_d_boyle/32/22_2.png) [@Bryan\_D\_Boyle](https://community.allstarlink.org/u/Bryan_D_Boyle)\ **Post date:** [January 30, 2012, 1:36pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/2 "2012-01-30T13:36:52Z")
> > Thanks for the links and birddogging this. > > You're welcome, and thanks for the email.. The group didn't really seem > to think that my idea was worth pursuing, > but I did. It's always nice to hear when someone else benefits from it, > too.. My motto (stolen happily from Lotus Cars founder Colin Chapman): "Simplify and add lightness". We (using the pontifical "we") tend to complicate things (either through an inveterate drive to turn a simple problem into a complex engineering exercise or 'can't put it down...' nature)...another cliche is 'inside every complex engineering problem is a simple solution struggling to get out...'. Sometimes, it is not as complex, in the final analysis, as it seems. 😉 (And, big props to Jim, Steve, and the rest of the contributors to the base code who have developed a SIMPLE way to interact with a complex system...that is the definition of elegant...) > > (we really need a repository somewhere with people's scripts, etc to > > share the collective knowledge...and it shouldn't fall on Duuuude or the > > other folks..) > > I agree.. FWIW, I ended up putting a few more on my web page... > Basically just > my Random Allstar connect script and Random Echolink connect script. > They are > pretty crude, but they work.. I've been using them for a year or two.. I think I've posted my weather and wx alert scripts somewhere...and a couple are actually using them...😉 Yours is online out here on the east coast, I know KB2EAR has a repository for the nodename audio files...we have the start, anyway... > **···** > > On 1/29/12 11:34 PM, K&R Yoksh wrote: > > -- > Bryan > In this world, you must be oh so smart or oh so pleasant. > Well, for years I was smart. I recommend pleasant. > You may quote me. > > Sent from my MacBook Pro. ---
**Author:** ![Kh2d](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/ecb155/32.png) [@Kh2d](https://community.allstarlink.org/u/Kh2d)\ **Post date:** [January 30, 2012, 4:50pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/3 "2012-01-30T16:50:34Z")
I'm new on the list as of last night. A couple of questions. Where do you hide the scripts? And is it OK to post links on the list? 73, Jim KH2D > **···** > > On 1/30/2012 8:36 AM, Bryan D. Boyle wrote: > > > I think I've posted my weather and wx alert scripts somewhere...and a couple are actually using them...😉 Yours is online out here on the east coast, I know KB2EAR has a repository for the nodename audio files...we have the start, anyway... ---
**Author:** ![Bryan\_D\_Boyle](https://community.allstarlink.org/user_avatar/community.allstarlink.org/bryan_d_boyle/32/22_2.png) [@Bryan\_D\_Boyle](https://community.allstarlink.org/u/Bryan_D_Boyle)\ **Post date:** [January 30, 2012, 5:08pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/4 "2012-01-30T17:08:55Z")
Welcome to the collective. We're a pentium borg. You will be approximated...😉 Seriously, hop on and enjoy the ride. Hide as in where it is on your system, or where we're all hiding the juicy stuff we've developed? The NJPAASTERISK group, of which I'm one of the operators, have standardized on a scripts directory in the /etc/asterisk hierarchy (well, most of us have anyway..) to make it easier to backup the configuration and shorten deployment cycle time. Others put them in /etc or /usr/sbin or ??? Guess it goes where you feel it should be. Just be consistent. That means that, when you write something, you're pretty sure of where it should reside, and makes it easier to find 'stuff' that's directly applicable to your operation. It also means that, if you glom on to a script or app that someone else has written, you have to do some editing to make it work (pretty much standard when using others' works...) in your operation. As to the latter question...well, that topic came up yesterday, with no resolution. I have a repository for my weather scripts that I hacked/wrote/modified at [WB0YLE Repeater Weather Scripts](http://www.wb0yle.com/weather.htm), Kyle has some stuff on his site...I'm sure others will chime in (hint, hint...) if they have anything they'd like to make public... And, I don't think there is any blanket prohibition against posting links. > **···** > > On 1/30/12 11:50 AM, Jim Kehler wrote: > > > I'm new on the list as of last night. A couple of questions. Where do you > > hide the scripts? And is it OK to post links on the list? > > -- > Bryan > In this world, you must be oh so smart or oh so pleasant. > Well, for years I was smart. I recommend pleasant. > You may quote me. > > Sent from my MacBook Pro. ---
**Author:** ![KE6PCV](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ke6pcv/32/429_2.png) [@KE6PCV](https://community.allstarlink.org/u/KE6PCV)\ **Post date:** [January 30, 2012, 5:59pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/5 "2012-01-30T17:59:18Z")
Maybe I don't understand how things work as I am not a Linux power user by any means. But can't documentation, information and scripts be posted on this website which was setup by the app\_rpt creators? > **[ohnosec.org - ohnosec Resources and Information.](http://ww1.ohnosec.org/drupal/?usid=22&utid=2463353656)** > > ohnosec.org is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, ohnosec.org has it all. We hope you find what you are searching for! After all, isn't this site kind of the unofficial "Official" site for support? It would sure be nice to keep all this great information in one place. Marshall - ke6pcv > **···** > > > -----Original Message----- > > From: app\_rpt-users-bounces@ohnosec.org > > [mailto:app\_rpt-users-bounces@ohnosec.org] On Behalf Of Bryan D. Boyle > > Sent: Monday, January 30, 2012 9:09 AM > > To: app\_rpt mailing list > > Subject: Re: [App\_rpt-users] GPIO fan control script now available > > > > On 1/30/12 11:50 AM, Jim Kehler wrote: > > \> I'm new on the list as of last night. A couple of > > questions. Where do > > \> you hide the scripts? And is it OK to post links on the list? > > > > Welcome to the collective. We're a pentium borg. You will be > > approximated...😉 Seriously, hop on and enjoy the ride. > > > > Hide as in where it is on your system, or where we're all > > hiding the juicy stuff we've developed? > > > > The NJPAASTERISK group, of which I'm one of the operators, > > have standardized on a scripts directory in the /etc/asterisk > > hierarchy (well, most of us have anyway..) to make it easier > > to backup the configuration and shorten deployment cycle > > time. Others put them in /etc or /usr/sbin or ??? Guess it > > goes where you feel it should be. > > Just be consistent. > > > > That means that, when you write something, you're pretty sure > > of where it should reside, and makes it easier to find > > 'stuff' that's directly applicable to your operation. It > > also means that, if you glom on to a script or app that > > someone else has written, you have to do some editing to make > > it work (pretty much standard when using others' works...) in > > your operation. > > > > As to the latter question...well, that topic came up > > yesterday, with no resolution. I have a repository for my > > weather scripts that I hacked/wrote/modified at > > [WB0YLE Repeater Weather Scripts](http://www.wb0yle.com/weather.htm), Kyle has some stuff on his > > site...I'm sure others will chime in (hint, hint...) if they > > have anything they'd like to make public... > > > > And, I don't think there is any blanket prohibition against > > posting links. > > > > -- > > Bryan > > In this world, you must be oh so smart or oh so pleasant. > > Well, for years I was smart. I recommend pleasant. > > You may quote me. > > > > Sent from my MacBook Pro. > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@ohnosec.org > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![N3XCC](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n3xcc/32/5099_2.png) [@N3XCC](https://community.allstarlink.org/u/N3XCC)\ **Post date:** [January 30, 2012, 6:00pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/6 "2012-01-30T18:00:58Z")
> I'm sure others will chime in (hint, hint...) \<-- Since allstarnode.com was designed to be a peer-to-peer BB system for ALL flavors of AllStar builds, I can make public FTP space available on there if it's needed/desired. Scott Scott Zimmerman Amateur Radio Call N3XCC 474 Barnett Road Boswell, PA 15531 > **···** > > On 1/30/2012 12:08 PM, Bryan D. Boyle wrote: > > > On 1/30/12 11:50 AM, Jim Kehler wrote: > > > > > I'm new on the list as of last night. A couple of questions. Where do you > > > hide the scripts? And is it OK to post links on the list? > > > > Welcome to the collective. We're a pentium borg. You will be approximated...😉 Seriously, hop on and > > enjoy the ride. > > > > Hide as in where it is on your system, or where we're all hiding the juicy stuff we've developed? > > > > The NJPAASTERISK group, of which I'm one of the operators, have standardized on a scripts directory > > in the /etc/asterisk hierarchy (well, most of us have anyway..) to make it easier to backup the > > configuration and shorten deployment cycle time. Others put them in /etc or /usr/sbin or ??? Guess > > it goes where you feel it should be. Just be consistent. > > > > That means that, when you write something, you're pretty sure of where it should reside, and makes > > it easier to find 'stuff' that's directly applicable to your operation. It also means that, if you > > glom on to a script or app that someone else has written, you have to do some editing to make it > > work (pretty much standard when using others' works...) in your operation. > > > > As to the latter question...well, that topic came up yesterday, with no resolution. I have a > > repository for my weather scripts that I hacked/wrote/modified at [WB0YLE Repeater Weather Scripts](http://www.wb0yle.com/weather.htm), > > Kyle has some stuff on his site...I'm sure others will chime in (hint, hint...) if they have > > anything they'd like to make public... > > > > And, I don't think there is any blanket prohibition against posting links. ---
**Author:** ![Bryan\_D\_Boyle](https://community.allstarlink.org/user_avatar/community.allstarlink.org/bryan_d_boyle/32/22_2.png) [@Bryan\_D\_Boyle](https://community.allstarlink.org/u/Bryan_D_Boyle)\ **Post date:** [January 30, 2012, 6:36pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/7 "2012-01-30T18:36:55Z")
> Thanks Bryan. I'm new to Linux so I'm looking for examples. Got the basic > node up and going no problems, but it needs tuning. Things aren't fun > unless you can tune them.... su - radio-tune-menu is a great thing to play with...😉 The rest? Well...dive in. > Your Read Me First files seems to be MIA, I got a 404 when I tried to > read it. thanks for reminding me...was in a rush to get the other stuff up before the cold winds started blowing back in Nov., and never got a Round Tuit. > **···** > > On 1/30/12 1:31 PM, Jim Kehler wrote: > > -- > Bryan > In this world, you must be oh so smart or oh so pleasant. > Well, for years I was smart. I recommend pleasant. > You may quote me. > > Sent from my MacBook Pro. ---
**Author:** ![App\_Rpt](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@App\_Rpt](https://community.allstarlink.org/u/App_Rpt)\ **Post date:** [January 30, 2012, 7:06pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/8 "2012-01-30T19:06:16Z")
Introducing the Commons Script House which will be located at: [http://scripts.asteriskradio.net](http://scripts.asteriskradio.net) Script builders can show case their scripts and users can comment about the scripts presented. Mars - N0PCO ALERTradio ERC [www.alertradio.net](http://www.alertradio.net) | [www.asteriskradio.net](http://www.asteriskradio.net) | [www.darnsimple.net](http://www.darnsimple.net) Technology resources for public safety. It's all about being ready. ---
**Author:** ![KE6PCV](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ke6pcv/32/429_2.png) [@KE6PCV](https://community.allstarlink.org/u/KE6PCV)\ **Post date:** [January 30, 2012, 7:18pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/9 "2012-01-30T19:18:29Z")
Scott, That is a very generous offer on your part, but wouldn't it be better to keep everything all in one place for folks to go use as a reference? Especially new allstar node owners? So, I will state this question again. Am I missing something? Why doesn't anyone want to use the official help site? If you go to the allstar.org webpage and click on the link that says "help" it will take you to the another page. If you click on "Links To Helpful Things Pertaining to this Technology" The first thing that comes up is "Asterisk/app\_rpt project -- Lots of good documentation on the Asterisk app\_rpt application" You click on that link and it takes you to [ohnosec.org](http://ohnosec.org/drupal/) So why can't documentation, information and scripts be posted on this website which was setup by the app\_rpt creators? After all, isn't this site kind of the "Official" site for support? I don't think it's a good idea to have several fragmented websites with information when we already have the official one that is pretty good. Having multiple websites will confuse new users on where to get information. 73 Marshall - ke6pcv > **···** > > > -----Original Message----- > > From: app\_rpt-users-bounces@ohnosec.org > > [mailto:app\_rpt-users-bounces@ohnosec.org] On Behalf Of Scott > > Zimmerman > > Sent: Monday, January 30, 2012 10:01 AM > > To: app\_rpt mailing list > > Subject: Re: [App\_rpt-users] GPIO fan control script now available > > > > \> I'm sure others will chime in (hint, hint...) > > \<-- Since allstarnode.com was designed to be a peer-to-peer > > BB system for ALL flavors of AllStar builds, I can make > > public FTP space available on there if it's needed/desired. > > > > Scott > > > > Scott Zimmerman > > Amateur Radio Call N3XCC > > 474 Barnett Road > > Boswell, PA 15531 > > > > On 1/30/2012 12:08 PM, Bryan D. Boyle wrote: > > \> On 1/30/12 11:50 AM, Jim Kehler wrote: > > \>\> I'm new on the list as of last night. A couple of > > questions. Where do > > \>\> you hide the scripts? And is it OK to post links on the list? > > \> > > \> Welcome to the collective. We're a pentium borg. You will be > > \> approximated...😉 Seriously, hop on and enjoy the ride. > > \> > > \> Hide as in where it is on your system, or where we're all > > hiding the juicy stuff we've developed? > > \> > > \> The NJPAASTERISK group, of which I'm one of the operators, have > > \> standardized on a scripts directory in the /etc/asterisk hierarchy > > \> (well, most of us have anyway..) to make it easier to backup the > > \> configuration and shorten deployment cycle time. Others put > > them in /etc or /usr/sbin or ??? Guess it goes where you feel > > it should be. Just be consistent. > > \> > > \> That means that, when you write something, you're pretty > > sure of where > > \> it should reside, and makes it easier to find 'stuff' > > that's directly > > \> applicable to your operation. It also means that, if you > > glom on to a > > \> script or app that someone else has written, you have to do > > some editing to make it work (pretty much standard when using > > others' works...) in your operation. > > \> > > \> As to the latter question...well, that topic came up > > yesterday, with > > \> no resolution. I have a repository for my weather scripts that I > > \> hacked/wrote/modified at [WB0YLE Repeater Weather Scripts](http://www.wb0yle.com/weather.htm), > > \> Kyle has some stuff on his site...I'm sure others will > > chime in (hint, > > \> hint...) if they have anything they'd like to make public... > > \> > > \> And, I don't think there is any blanket prohibition against > > posting links. > > \> > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@ohnosec.org > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![N3XCC](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n3xcc/32/5099_2.png) [@N3XCC](https://community.allstarlink.org/u/N3XCC)\ **Post date:** [January 30, 2012, 8:53pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/10 "2012-01-30T20:53:46Z")
> So, I will state this question again. Am I missing something? Why doesn't anyone want to use \> the official help site? \<-- Well..... Quite frankly Marshall, I don't give a damn where it's located. There was a need and I made an offer. Don't bite my head off about it! It seems like if the ohnosec.org/drupal/ site was the place to be putting stuff, others would have done it before now. \> After all, isn't this site kind of the "Official" site for support? \<-- Yep, it's SUPPOSED to be. When I was starting out that site left LOTS to be desired, hence why I created the allstarnode.com BB site. \> Having multiple websites will confuse new users on where to get information. \<-- Google will find GOOD information no matter WHERE it's located. Back to sleep, Scott Scott Zimmerman Amateur Radio Call N3XCC 474 Barnett Road Boswell, PA 15531 > **···** > > On 1/30/2012 2:18 PM, Marshall Oldham wrote: > > > Scott, > > > > That is a very generous offer on your part, but wouldn't it be better to keep everything all in one place for folks to > > go use as a reference? Especially new allstar node owners? > > > > So, I will state this question again. Am I missing something? Why doesn't anyone want to use > > the official help site? > > > > If you go to the allstar.org webpage and click on the link that says "help" it will take you to the another page. > > > > If you click on "Links To Helpful Things Pertaining to this Technology" > > > > The first thing that comes up is "Asterisk/app\_rpt project -- Lots of good documentation on the Asterisk app\_rpt application" > > > > You click on that link and it takes you to [ohnosec.org](http://ohnosec.org/drupal/) > > > > So why can't documentation, information and scripts be posted on this website which was setup by the app\_rpt creators? > > > > After all, isn't this site kind of the "Official" site for support? > > > > I don't think it's a good idea to have several fragmented websites with information when we already have the official one that is > > pretty good. > > Having multiple websites will confuse new users on where to get information. > > > > 73 > > > > Marshall - ke6pcv > > > > > -----Original Message----- > > > From: app\_rpt-users-bounces@ohnosec.org > > > [mailto:app\_rpt-users-bounces@ohnosec.org] On Behalf Of Scott > > > Zimmerman > > > Sent: Monday, January 30, 2012 10:01 AM > > > To: app\_rpt mailing list > > > Subject: Re: [App\_rpt-users] GPIO fan control script now available > > > > > >   \> I'm sure others will chime in (hint, hint...) > > > \<-- Since allstarnode.com was designed to be a peer-to-peer > > > BB system for ALL flavors of AllStar builds, I can make > > > public FTP space available on there if it's needed/desired. > > > > > > Scott > > > > > > Scott Zimmerman > > > Amateur Radio Call N3XCC > > > 474 Barnett Road > > > Boswell, PA 15531 > > > > > > On 1/30/2012 12:08 PM, Bryan D. Boyle wrote: > > > > > > > On 1/30/12 11:50 AM, Jim Kehler wrote: > > > > > > > > > I'm new on the list as of last night. A couple of > > > > > > questions. Where do > > > > > > > > you hide the scripts? And is it OK to post links on the list? > > > > > > > > Welcome to the collective. We're a pentium borg. You will be > > > > approximated...😉 Seriously, hop on and enjoy the ride. > > > > > > > > Hide as in where it is on your system, or where we're all > > > > > > hiding the juicy stuff we've developed? > > > > > > > The NJPAASTERISK group, of which I'm one of the operators, have > > > > standardized on a scripts directory in the /etc/asterisk hierarchy > > > > (well, most of us have anyway..) to make it easier to backup the > > > > configuration and shorten deployment cycle time. Others put > > > > > > them in /etc or /usr/sbin or ??? Guess it goes where you feel > > > it should be. Just be consistent. > > > > > > > That means that, when you write something, you're pretty > > > > > > sure of where > > > > > > > it should reside, and makes it easier to find 'stuff' > > > > > > that's directly > > > > > > > applicable to your operation. It also means that, if you > > > > > > glom on to a > > > > > > > script or app that someone else has written, you have to do > > > > > > some editing to make it work (pretty much standard when using > > > others' works...) in your operation. > > > > > > > As to the latter question...well, that topic came up > > > > > > yesterday, with > > > > > > > no resolution. I have a repository for my weather scripts that I > > > > hacked/wrote/modified at [WB0YLE Repeater Weather Scripts](http://www.wb0yle.com/weather.htm), > > > > Kyle has some stuff on his site...I'm sure others will > > > > > > chime in (hint, > > > > > > > hint...) if they have anything they'd like to make public... > > > > > > > > And, I don't think there is any blanket prohibition against > > > > > > posting links. > > > > > > > > > > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > > App\_rpt-users mailing list > > > App\_rpt-users@ohnosec.org > > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@ohnosec.org > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![KE6PCV](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ke6pcv/32/429_2.png) [@KE6PCV](https://community.allstarlink.org/u/KE6PCV)\ **Post date:** [January 30, 2012, 9:23pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/11 "2012-01-30T21:23:06Z")
> \> So, I will state this question again. Am I missing > something? Why doesn't anyone want to use \> the official help site? > \<-- Well..... Quite frankly Marshall, I don't give a damn > where it's located. There was a need and I made an offer. > Don't bite my head off about it! Scott, Sorry, if you miss interpreted my question about using the official help site as biting your head off. If was not my intent when I asked the question, I just wanted to know why folks where against using the site. > It seems like if the ohnosec.org/drupal/ site was the place > to be putting stuff, others would have done it before now. I gather that there is some type of technical issue that is preventing folks from posting information to this site??? Or is it, that they just do not like the way the information is presented? > \> After all, isn't this site kind of the "Official" site for support? > \<-- Yep, it's SUPPOSED to be. When I was starting out that > site left LOTS to be desired, hence why I created the > allstarnode.com BB site. If everyone helped add info to the ohnosec.org/drupal/ site, it would soon be MORE desired site and in one place. > \> Having multiple websites will confuse new users on where > to get information. > \<-- Google will find GOOD information no matter WHERE it's located. Yes, I understand that one can Google and find just about anything. But the point that I was trying to make is, that for a beginner to much information on several websites can be confusing. Again, I am not trying to get on anyone's case or bite anyone's head off. Just thought it would be easier for the new folks to have an official place to go to get answers to questions. 73 Marshall - ke6pcv > **···** > > > Back to sleep, > > Scott > > > > Scott Zimmerman > > Amateur Radio Call N3XCC > > 474 Barnett Road > > Boswell, PA 15531 > > > > On 1/30/2012 2:18 PM, Marshall Oldham wrote: > > \> Scott, > > \> > > \> That is a very generous offer on your part, but wouldn't it > > be better > > \> to keep everything all in one place for folks to go use as > > a reference? Especially new allstar node owners? > > \> > > \> So, I will state this question again. Am I missing something? Why > > \> doesn't anyone want to use the official help site? > > \> > > \> If you go to the allstar.org webpage and click on the link > > that says "help" it will take you to the another page. > > \> > > \> If you click on "Links To Helpful Things Pertaining to this > > Technology" > > \> > > \> The first thing that comes up is "Asterisk/app\_rpt project > > -- Lots of good documentation on the Asterisk app\_rpt application" > > \> > > \> You click on that link and it takes you to > > [ohnosec.org](http://ohnosec.org/drupal/) > > \> > > \> So why can't documentation, information and scripts be > > posted on this website which was setup by the app\_rpt creators? > > \> > > \> After all, isn't this site kind of the "Official" site for support? > > \> > > \> I don't think it's a good idea to have several fragmented websites > > \> with information when we already have the official one that > > is pretty good. > > \> Having multiple websites will confuse new users on where to > > get information. > > \> > > \> 73 > > \> > > \> Marshall - ke6pcv > > \> > > \>\> -----Original Message----- > > \>\> From: app\_rpt-users-bounces@ohnosec.org > > \>\> [mailto:app\_rpt-users-bounces@ohnosec.org] On Behalf Of Scott > > \>\> Zimmerman > > \>\> Sent: Monday, January 30, 2012 10:01 AM > > \>\> To: app\_rpt mailing list > > \>\> Subject: Re: [App\_rpt-users] GPIO fan control script now available > > \>\> > > \>\> \> I'm sure others will chime in (hint, hint...) > > \>\> \<-- Since allstarnode.com was designed to be a > > peer-to-peer BB system > > \>\> for ALL flavors of AllStar builds, I can make public FTP space > > \>\> available on there if it's needed/desired. > > \>\> > > \>\> Scott > > \>\> > > \>\> Scott Zimmerman > > \>\> Amateur Radio Call N3XCC > > \>\> 474 Barnett Road > > \>\> Boswell, PA 15531 > > \>\> > > \>\> On 1/30/2012 12:08 PM, Bryan D. Boyle wrote: > > \>\>\> On 1/30/12 11:50 AM, Jim Kehler wrote: > > \>\>\>\> I'm new on the list as of last night. A couple of > > \>\> questions. Where do > > \>\>\>\> you hide the scripts? And is it OK to post links on the list? > > \>\>\> > > \>\>\> Welcome to the collective. We're a pentium borg. You will be > > \>\>\> approximated...😉 Seriously, hop on and enjoy the ride. > > \>\>\> > > \>\>\> Hide as in where it is on your system, or where we're all > > \>\> hiding the juicy stuff we've developed? > > \>\>\> > > \>\>\> The NJPAASTERISK group, of which I'm one of the operators, have > > \>\>\> standardized on a scripts directory in the /etc/asterisk > > hierarchy > > \>\>\> (well, most of us have anyway..) to make it easier to backup the > > \>\>\> configuration and shorten deployment cycle time. Others put > > \>\> them in /etc or /usr/sbin or ??? Guess it goes where you feel it > > \>\> should be. Just be consistent. > > \>\>\> > > \>\>\> That means that, when you write something, you're pretty > > \>\> sure of where > > \>\>\> it should reside, and makes it easier to find 'stuff' > > \>\> that's directly > > \>\>\> applicable to your operation. It also means that, if you > > \>\> glom on to a > > \>\>\> script or app that someone else has written, you have to do > > \>\> some editing to make it work (pretty much standard when > > using others' > > \>\> works...) in your operation. > > \>\>\> > > \>\>\> As to the latter question...well, that topic came up > > \>\> yesterday, with > > \>\>\> no resolution. I have a repository for my weather scripts that I > > \>\>\> hacked/wrote/modified at [WB0YLE Repeater Weather Scripts](http://www.wb0yle.com/weather.htm), > > \>\>\> Kyle has some stuff on his site...I'm sure others will > > \>\> chime in (hint, > > \>\>\> hint...) if they have anything they'd like to make public... > > \>\>\> > > \>\>\> And, I don't think there is any blanket prohibition against > > \>\> posting links. > > \>\>\> > > \>\> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > \>\> App\_rpt-users mailing list > > \>\> App\_rpt-users@ohnosec.org > > \>\> [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) > > \>\> > > \> > > \> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > \> App\_rpt-users mailing list > > \> App\_rpt-users@ohnosec.org > > \> [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) > > \> ---
**Author:** ![Kh2d](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/ecb155/32.png) [@Kh2d](https://community.allstarlink.org/u/Kh2d)\ **Post date:** [January 30, 2012, 9:47pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/12 "2012-01-30T21:47:49Z")
Look at it this way, Marshal. Let's say you get up on Friday morning and your wife wants to go out to dinner that night. At 6 PM you find out that every restaurant within 500 miles of your house has closed up and gone out of business, with the exception of one; Freddy's Diner. So you have no choice. You have to take the wife to Freddy's. And the only thing you'll get to eat at Freddy's is whatever Freddy decides to feed you. If Freddy doesn't want you have Apple Pie, you aren't going to get any Apple Pie. No matter how much you beg Freddy..... I've only been playing with this stuff for about a month. I'd never seen Linux. Some documentation I found assumed that I was proficient with Linux, which I'm not. So banging around in Google finding bits and pieces was a learning experience; I don't like to just make something work, I want to know how it works so that if it breaks, I can fix it. Documentation at all levels is a good thing. The more the merrier. As long as Google is still in business, it's available to anybody that wants to go find it. All the scripts in one place sounds like a terrific idea to me. Hopefully the guys who wrote them won't assume I know how to use them when I find them. That being said, does anybody know where I can find the fan script? My radio is hot.... 73, Jim KH2D > **···** > > On 1/30/2012 2:18 PM, Marshall Oldham wrote: > > > Scott, > > > > That is a very generous offer on your part, but wouldn't it be better to keep everything all in one place for folks to > > go use as a reference? Especially new allstar node owners? > > > > So, I will state this question again. Am I missing something? Why doesn't anyone want to use > > the official help site? > > > > If you go to the allstar.org webpage and click on the link that says "help" it will take you to the another page. > > > > If you click on "Links To Helpful Things Pertaining to this Technology" > > > > The first thing that comes up is "Asterisk/app\_rpt project -- Lots of good documentation on the Asterisk app\_rpt application" > > > > You click on that link and it takes you to [ohnosec.org](http://ohnosec.org/drupal/) > > > > So why can't documentation, information and scripts be posted on this website which was setup by the app\_rpt creators? > > > > After all, isn't this site kind of the "Official" site for support? > > > > I don't think it's a good idea to have several fragmented websites with information when we already have the official one that is > > pretty good. > > Having multiple websites will confuse new users on where to get information. > > > > 73 > > > > Marshall - ke6pcv > > > > > -----Original Message----- > > > From: app\_rpt-users-bounces@ohnosec.org > > > [mailto:app\_rpt-users-bounces@ohnosec.org] On Behalf Of Scott > > > Zimmerman > > > Sent: Monday, January 30, 2012 10:01 AM > > > To: app\_rpt mailing list > > > Subject: Re: [App\_rpt-users] GPIO fan control script now available > > > > > >   \> I'm sure others will chime in (hint, hint...) > > > \<-- Since allstarnode.com was designed to be a peer-to-peer > > > BB system for ALL flavors of AllStar builds, I can make > > > public FTP space available on there if it's needed/desired. > > > > > > Scott > > > > > > Scott Zimmerman > > > Amateur Radio Call N3XCC > > > 474 Barnett Road > > > Boswell, PA 15531 > > > > > > On 1/30/2012 12:08 PM, Bryan D. Boyle wrote: > > > > > > > On 1/30/12 11:50 AM, Jim Kehler wrote: > > > > > > > > > I'm new on the list as of last night. A couple of > > > > > > questions. Where do > > > > > > > > you hide the scripts? And is it OK to post links on the list? > > > > > > > > Welcome to the collective. We're a pentium borg. You will be > > > > approximated...😉 Seriously, hop on and enjoy the ride. > > > > > > > > Hide as in where it is on your system, or where we're all > > > > > > hiding the juicy stuff we've developed? > > > > > > > The NJPAASTERISK group, of which I'm one of the operators, have > > > > standardized on a scripts directory in the /etc/asterisk hierarchy > > > > (well, most of us have anyway..) to make it easier to backup the > > > > configuration and shorten deployment cycle time. Others put > > > > > > them in /etc or /usr/sbin or ??? Guess it goes where you feel > > > it should be. Just be consistent. > > > > > > > That means that, when you write something, you're pretty > > > > > > sure of where > > > > > > > it should reside, and makes it easier to find 'stuff' > > > > > > that's directly > > > > > > > applicable to your operation. It also means that, if you > > > > > > glom on to a > > > > > > > script or app that someone else has written, you have to do > > > > > > some editing to make it work (pretty much standard when using > > > others' works...) in your operation. > > > > > > > As to the latter question...well, that topic came up > > > > > > yesterday, with > > > > > > > no resolution. I have a repository for my weather scripts that I > > > > hacked/wrote/modified at [WB0YLE Repeater Weather Scripts](http://www.wb0yle.com/weather.htm), > > > > Kyle has some stuff on his site...I'm sure others will > > > > > > chime in (hint, > > > > > > > hint...) if they have anything they'd like to make public... > > > > > > > > And, I don't think there is any blanket prohibition against > > > > > > posting links. > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > > App\_rpt-users mailing list > > > App\_rpt-users@ohnosec.org > > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@ohnosec.org > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![Bbrown](https://community.allstarlink.org/user_avatar/community.allstarlink.org/bbrown/32/812_2.png) [@Bbrown](https://community.allstarlink.org/u/Bbrown)\ **Post date:** [January 30, 2012, 10:00pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/13 "2012-01-30T22:00:07Z")
How about reading the archive of this thread and you will find your fan script. The link was provided in a previous post… I am done… > **···** > > – ---
**Author:** ![Bryan\_D\_Boyle](https://community.allstarlink.org/user_avatar/community.allstarlink.org/bryan_d_boyle/32/22_2.png) [@Bryan\_D\_Boyle](https://community.allstarlink.org/u/Bryan_D_Boyle)\ **Post date:** [January 30, 2012, 11:38pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/14 "2012-01-30T23:38:48Z")
Since it's my suggestion that started this little lit match discussion...let me explain my reasoning. Feel free to send flames to /dev/null. We're all in this together, ok? 1. I'm not speaking for Jim; he and perhaps one or two other people maintain the [allstarlink.org](http://allstarlink.org) site. I'm assuming it is NOT their day job. And, when they do maintain it, it's FOR FREE. I dislike imposing on ANYONE, especially one who has done so much to help US that we should expect him (or them, for that matter) to add to their responsibilities and develop an interactive site for US, THE USERS to swap the fruits of our labor from THEIR efforts. Links are cheap. Maintaining a site isn't; it takes time, effort, disk space, bandwidth, dealing with the clueless, etc. Got to help out those who help us. 2. The analogy, stated by another is apt. If you're going to put all your eggs in one basket, make sure it's a damn strong basket. And the internet ain't, regardless of what we think. DNSs get scrogged, disks go tango uniform, firewalls get dain bramaged, people fatfinger URLs...you name it. Resilient, it ain't. So, like many sites, there are mirrors, off-site repositories, etc. It's not a big deal. Done all the time. And is no reflection on the 'mother ship'. 3. Scott's offer was made in a gentlemanly manner IMHO (and he has a day job too...) of assistance and in the spirit of open source cooperation. Thank you, Scott. 4. It does no good to jump to conclusions, etc. as to motives or agendas, or what have you. Different sites? That's what the bookmark/favorites/etc tab is for in the browser. Even better, do what lots of folks who've been on the web since the 90s do, and make a local web page with links to ALL of your interests (mine range from restoring british sports cars to medieval theology to broadcast engineering to amateur radio to the american civil war...) in it, store it on the local machine (well, I actually store it on my server and load from there...) with all the requisite links. You'd be amazed how easy it is, and, instead of being handed a fish, you build your own pole and go out and grab what you want. 5. We're hams. We build stuff, make it work, and keep tweaking till we're done. Well...there's a wealth of knowledge out there, neat things we've all done, insights into how the system operates, or how we can twist its dongles a little more to our liking. In that spirit...it makes sense to share what we've all accomplished. For the good of all of us. 5. Thank you, Jim, for letting us fill up your mailbox today with something that really didn't need to go to the level it did. Bryan WB0YLE 27294, 27295, 27673, 27720, 37774, 90102 ---
**Author:** ![Bryan\_D\_Boyle](https://community.allstarlink.org/user_avatar/community.allstarlink.org/bryan_d_boyle/32/22_2.png) [@Bryan\_D\_Boyle](https://community.allstarlink.org/u/Bryan_D_Boyle)\ **Post date:** [February 1, 2012, 2:07pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/15 "2012-02-01T14:07:30Z")
In hacking (thanks, Kyle) through getting both the script working (hey, had to modify it for my own install, which is a good thing...:)) and addressing the proper node/dongle number...and getting the parts to build the circuit (at Radio Shack, believe it or not...) as shown at the DMK site so I could actually drive my cooling fans (with 3 repeaters, a 100w amp, and batwing spectra transmitter that gets Real Toasty even at 12w out, the amount of constant noise is a bit much, even in the basement...not to mention the electricity consumption), it's all up and working. However, in talking with Scott KB2EAR, he brought up the issue of the possibility (not remote..) of the controller or a dongle hanging or going brain dead in between the time that the radio keys up and the fan controller script turns on the relay...with the possibility that the radio would key (along with the amp...) but the fans would never come up. So...belt and suspenders time. I have an extra box of shalco thermoswitches...NO contacts, close at 115c, reopen at 95c or thereabouts. Since the relay (I like electromechanical stuff, ok? Nothing like the sound of contactors closing all around the shack when you press one button...brings me back to the days of running BIG transmitters and the plate contactor closing when you pressed 'PLATE ON' and saw the plate voltage meter swing to 18KV @ 2.6A) that's being driven by the DMK circuit is actually controlling the B+ to the fan string...putting one of the thermo switches across the armature and NO contact of the relay...well, if the computer hangs, or the relay fails, and the transmitter and amps are up...when they get warm enough, the secondary mechanical (rather than logical) circuit takes over and STILL turns the fan on. I'd rather fail, if that's the scenario, with cooling flow across the heat sinks than not. Obviously, this implies that the logical circuit is driven from the same power supply as the fans (mine are...) to eliminate that issue. Anyway...wired that up as an addition to the relay circuit; actually, it's just a pair of wires coming back from the shalco and paralleled across the leads from the relay. Just throwing that out there for y'all's consideration, if you're building the circuit from DMK to do something like this. (Still have to mount the DMK circuit on perfboard in a small project box and clean up the wiring...right now, it's just hanging by its wires in front of the repeater shelving unit (plastic...one of those Sears 5-shelf organizers...). Final cost, by the by, of the DMK circuit, using bits and pieces from the Shack, was under $10 USD, btw. And the biggest cost was the big piece of perfboard (which I cut down, so I have lots extra to use for other projects) and the small DPDT relay. Bought the 10-pack of transistors, 10-pack of diodes, and couple sleeves of the 4.7K resistors, so, have some extras to build other interfaces... 73 > **···** > > -- > Bryan > In this world, you must be oh so smart or oh so pleasant. > Well, for years I was smart. I recommend pleasant. > You may quote me. > > Sent from my MacBook Pro. ---
**Author:** ![Bbrown](https://community.allstarlink.org/user_avatar/community.allstarlink.org/bbrown/32/812_2.png) [@Bbrown](https://community.allstarlink.org/u/Bbrown)\ **Post date:** [February 1, 2012, 4:10pm UTC](https://community.allstarlink.org/t/gpio-fan-control-script-now-available/9244/16 "2012-02-01T16:10:48Z")
Hey Bryan Send me a picture of your “Rube Goldberg Special” With the wires hanging out of course 🙂 > **···** > > – > Thanks in Advance > > Bob Brown, WØNQX > > Kansas City Metro Area > > [http://sm0kenet.net](http://sm0kenet.net/) > > [http://byrg.net](http://byrg.net/) > > [http://kcdstar.byrg.net](http://kcdstar.byrg.net/) > > [http://w0nqx.blogspot.com](http://w0nqx.blogspot.com/) > > Quis custodiet ipsos custodes? > > Its not how many watts you have, > its the SIZE of your watts that matter! – Johnny Marshall, W0JM-SK > > – > > On Wed, Feb 1, 2012 at 8:07 AM, Bryan D. Boyle [bdboyle@bdboyle.com](mailto:bdboyle@bdboyle.com) wrote: > > > In hacking (thanks, Kyle) through getting both the script working (hey, had to modify it for my own install, which is a good thing…:)) and addressing the proper node/dongle number…and getting the parts to build the circuit (at Radio Shack, believe it or not…) as shown at the DMK site so I could actually drive my cooling fans (with 3 repeaters, a 100w amp, and batwing spectra transmitter that gets Real Toasty even at 12w out, the amount of constant noise is a bit much, even in the basement…not to mention the electricity consumption), it’s all up and working. > > > > However, in talking with Scott KB2EAR, he brought up the issue of the possibility (not remote…) of the controller or a dongle hanging or going brain dead in between the time that the radio keys up and the fan controller script turns on the relay…with the possibility that the radio would key (along with the amp…) but the fans would never come up. > > > > So…belt and suspenders time. I have an extra box of shalco thermoswitches…NO contacts, close at 115c, reopen at 95c or thereabouts. Since the relay (I like electromechanical stuff, ok? Nothing like the sound of contactors closing all around the shack when you press one button…brings me back to the days of running BIG transmitters and the plate contactor closing when you pressed ‘PLATE ON’ and saw the plate voltage meter swing to 18KV @ 2.6A) that’s being driven by the DMK circuit is actually controlling the B+ to the fan string…putting one of the thermo switches across the armature and NO contact of the relay…well, if the computer hangs, or the relay fails, and the transmitter and amps are up…when they get warm enough, the secondary mechanical (rather than logical) circuit takes over and STILL turns the fan on. I’d rather fail, if that’s the scenario, with cooling flow across the heat sinks than not. > > > > Obviously, this implies that the logical circuit is driven from the same power supply as the fans (mine are…) to eliminate that issue. > > > > Anyway…wired that up as an addition to the relay circuit; actually, it’s just a pair of wires coming back from the shalco and paralleled across the leads from the relay. > > > > Just throwing that out there for y’all’s consideration, if you’re building the circuit from DMK to do something like this. > > > > (Still have to mount the DMK circuit on perfboard in a small project box and clean up the wiring…right now, it’s just hanging by its wires in front of the repeater shelving unit (plastic…one of those Sears 5-shelf organizers…). > > > > Final cost, by the by, of the DMK circuit, using bits and pieces from the Shack, was under $10 USD, btw. And the biggest cost was the big piece of perfboard (which I cut down, so I have lots extra to use for other projects) and the small DPDT relay. Bought the 10-pack of transistors, 10-pack of diodes, and couple sleeves of the 4.7K resistors, so, have some extras to build other interfaces… > > > > 73 > > > > – > > Bryan > > In this world, you must be oh so smart or oh so pleasant. > > Well, for years I was smart. I recommend pleasant. > > You may quote me. > > > > Sent from my MacBook Pro. > > > > * * * > > > > App\_rpt-users mailing list > > [App\_rpt-users@ohnosec.org](mailto:App_rpt-users@ohnosec.org) > > [http://ohnosec.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users)