Turn amplifier ON/OFF via relay

nico

Hi guys,
I've installed Runeaudio and am starting to test it.
Since the RPi (and BBB I think?) has GPIO pins, could we have a feature to turn ON/OFF a pin when we start /stop playback?

The idea is to have the amplifier connected to a relay, which would be controlled by a pin on the computer. When we start playing music, the amplifier turns on, and when we stop it turns off. This would allow us to hide the amplifier in a cupboard or such, and control everything remotely - while being relatively energy efficient.

If there were plans to implement this, it would be greatly appreciated

Cheers and thanks for the good work!

nico

edit: of course the amp should only turn off after the player being idle for some time (hopefully configurable from the Settings page)

ACX

Hi nico,
this feature is currently not on our roadmap, as it is very equipment-specific. Buf if someone comes out with a nice solution for that, we could consider to integrate it as an option in the Settings page.

krischan

Hi Guys,

my first post here (and a big Thank You for developing Rune Audio), but the feature is quite interesting for me too.

Maybe you can offer an option to automatically start a script when music playback is started and another when it's stopped. The scripts can be filled by oneself. So one can put in what ever one want. The users can post some examples in the forum for the ones with less knowledge.

E.g., modern (AV-)Receivers are controllable via TCP and in respect via shell script too. As a consequence another volume control method could be provided by calling a script, which is setting the level directly in the receiver. (I also use rune audio on a pi with a recent av-receiver, because I don't like the DLNA etc. things and have a sane folder structure for audio)

Also one or more buttons in the playback view can be provided to start scripts and it would be nice to make the script accessible via smb folder.

OK, many wishes... Maybe you can pick the first regarding to nico's original request.

gswg

The IQaudIO Pi-DAC uses GPIO22 as mute signal to a suitably configured amp and the same is true for the Pi-DAC+ when headphones are inserted, the same pin is used to allow a suitably equipped amp to mute. Obviously this would need software support to enable / disable the amp too but we're working towards similar goals at least....

Gordon@IQaudIO.com

skrodahl

This may be a very simple way of looking at it, but it would be useful and simple to implement:

In the settings, have a number of GPIO pins that can be set or unset. Then choose some simple triggers, like "IF music is playing THEN set GPIO# high ELSE set GPIO# low".

That would be sufficient for the original poster, who could then add a relay to that GPIO pin (it would even turn off the amp when the RPi is shut down), and it could be expanded to suit different ideas.

Midnight

I'd rather put the player and the amp together in a case and turn both on/off with a single power switch

skrodahl

Midnight wroteI'd rather put the player and the amp together in a case and turn both on/off with a single power switch

I wouldn't recommend that to anyone though. Just powering off the RPi with a power button could corrupt the Linux installation. Granted, it would have to be during a write operation (or before a disk flush), but you can never be sure. Besides, the RPi takes a while to boot and the amp is virtually instant on. There would be a wait before the system is in a usable state.

Another, and a much simpler idea, is to have a GPIO pin go HIGH/LOW from Menu -> Turn Off. Call it "AUX Power", "AUX Signal" or something similar, and make the pin user configurable. That's something that could be implemented and tested in a very short time, and I have a hard time imagining that it could introduce any bugs or put unwanted load on the system.

That idea is hardly the automatic feature that nico requested, it still is a simplified version and it doesn't require much imagination to make it a useful feature.

Midnight

skrodahl wrote
Midnight wroteI'd rather put the player and the amp together in a case and turn both on/off with a single power switch
I wouldn't recommend that to anyone though. Just powering off the RPi with a power button could corrupt the Linux installation.

Of course that's a problem, but still I just power off my Runeaudios. For the unlikely case that the file system gets corrupted I still can just flash the SD card with the recent version

It's not a device that is sold to customers and has to be 100 % rock solid.

Midnight

Maybe someone is interested in this board: http://www.msldigital.com/

The RemotePi Board is an intelligent infrared remote controlled power switch add-on board for the Raspberry Pi. It is mainly intended to remote control and power off/on a mediacenter system (i.e OpenELEC, Raspbmc, XBian, RasPlex, Raspbian), making your mediacenter easier, more convenient and more intuitive to use for all members of your family.

cmh714

Heres another one I was looking at....wont deal with the amp, but works on Pi

http://www.amazon.com/dp/B00BB0ETW8/ref=wl_it_dp_o_pC_nS_ttl?_encoding=UTF8&colid=VAMOR35LATA3&coliid=I25UJ0AY2MQDC1&psc=1

Midnight

But this one won't power off the RPi

cmh714

Midnight wroteBut this one won't power off the RPi

Fair enough, I did not look that far Midnight. TY

frengo

Hello.

I read the thread thinking it were a system to power cycle an audio amplifier or other analog parts of the system, but I understand that we are talking about turning on / off the raspberry.

Do you know if someone has made a script to change how you want the logic state at will of one or more outputs of the GPIO connector, maybe on ODROID C1 +?

Thank you.

Eph

I wrote a simple script "gpio_toggle.sh" to toggle the state of one GPIO connected to a relay that toggle the power to my DAC. This works
however I fill my implementation into the WebUI is sloppy at best. I compaired cyber7 "Volume Fade Over Time" to the unmodified webui.

Would someone give me an example of how to properly execute
sysCmdAsync('sh /var/www/command/XXXXX.sh');
whiten /srv/http/app/templates/header.php
without redirecting or any popups? just a click and execute, no feedback on the current state needed.
Can a function be implemented directly in header.php?

As it is, I added
<li class="<?=$this->uri(1, 'dac', 'active')?>"><a href="/dac/"><i class="fa fa-power-off"></i> DAC Power</a></li>
to header.php
I'm calling another dac.php and having that execute and redirect back. this is noticeable on mobile devices, as it's opening a new window. sloppy, I won't pretend to know php at all.

<div id="menu-top">
    <div class="dropdown">
        <a id="menu-settings" class="dropdown-toggle" role="button" data-toggle="dropdown" data-target="#" href="#">MENU <i class="fa fa-bars dx"></i></a>
        <ul class="dropdown-menu" role="menu" aria-labelledby="menu-settings">
            <li class="<?=$this->uri(1, '', 'active')?>"><a href="/"><i class="fa fa-play"></i> Playback</a></li>
            <li class="<?=$this->uri(1, 'sources', 'active')?>"><a href="/sources/"><i class="fa fa-folder-open"></i> Sources</a></li>
            <li class="<?=$this->uri(1, 'mpd', 'active')?>"><a href="/mpd/"><i class="fa fa-cogs"></i> MPD</a></li>
            <li class="<?=$this->uri(1, 'settings', 'active')?>"><a href="/settings/"><i class="fa fa-wrench"></i> Settings</a></li>
            <li class="<?=$this->uri(1, 'network', 'active')?>"><a href="/network/"><i class="fa fa-sitemap"></i> Network</a></li>
            <li class="<?=$this->uri(1, 'debug', 'active')?>"><a href="/debug/"><i class="fa fa-bug"></i> Debug</a></li>
            <li class="<?=$this->uri(1, 'credits', 'active')?>"><a href="/credits/"><i class="fa fa-trophy"></i> Credits</a></li>
            <li class="<?=$this->uri(1, 'dac', 'active')?>"><a href="/dac/"><i class="fa fa-power-off"></i> DAC Power</a></li>
            <li><a href="#poweroff-modal" data-toggle="modal"><i class="fa fa-power-off"></i> Turn off</a></li>
        </ul>
    </div>
    <div class="playback-controls">    
        <button id="previous" class="btn btn-default btn-cmd" title="Previous" data-cmd="previous"><i class="fa fa-step-backward"></i></button>
        <button id="stop" class="btn btn-default btn-cmd" title="Stop" data-cmd="stop"><i class="fa fa-stop"></i></button>
        <button id="play" class="btn btn-default btn-cmd" title="Play/Pause" data-cmd="play"><i class="fa fa-play"></i></button>
        <button id="next" class="btn btn-default btn-cmd" title="Next" data-cmd="next"><i class="fa fa-step-forward"></i></button>
    </div>
    <a class="home" href="/"><img src="<?=$this->asset('/img/logo.png')?>" class="logo" alt="RuneAudio"></a>
</div>

This calls dac.php which includes:

<div class="container credits">
<form action="/dac/" method="post">
        <h2><b>Toggeling DAC Power </b><?php
                        $myscript= sysCmdAsync('sh /var/www/command/gpio_toggle.sh');
                        ?>
        </h2></p>


                </ul>
</form>
<head>
  <meta http-equiv="refresh" content="0;url=/">
  </meta>
</head>

: 001.jpg (26.97 KiB) Viewed 3042 times

: 002.jpg (104.81 KiB) Viewed 3042 times

: 003.jpg (129.57 KiB) Viewed 3042 times

Yes, this is old tech. it was my Grammy's. So many records, so many memories... and now it's brought up to date with AirPlay, webradio, and NAS thanks to all the hard work from the Devs @ RuneAudio, cyber7's example in fade over time

and the creator of RPI's
It's a good time to be alive.

rern

How about this one?

RuneUI GPIO for power on / off audio equipments