IR Remote Configuration & Commands

PeteB

I finally found some time to hook up an IR sensor, and realized that what this forum really needs is another IR Remote thread, so here it is:

I have been experimenting with different remotes and I am wondering if other forum members would like to contribute their lircrc files, explanation of how they mapped the buttons, the commands used, or any tips on using an IR Remote with Rune Audio.

So far I have only mapped a few buttons to basic mpc commands (edited May 4, 2016):

Button: mpc command

Play/Pause: mpc toggle
Skip forward: mpc next
Skip back: mpc prev
Forward: mpc seek +00:00:10
Rewind: mpc seek -00:00:10
Volume up: mpc volume +2
Volume down: mpc volume -2
Stop: mpc stop

My lircrc file came from a tutorial by forum member Xplod:
http://buzzthisnow.com/ir-remote-with-lirc-on-raspberry-pi-2-running-runeaudio-archlinux/

I am wondering how best to map other Rune Audio functions to a typical IR remote, or what other people are doing with their remotes?

PeteB

My lircrc file, so far. This is where a button on the remote is mapped to an action in the RuneAudio Playback Screen. (edited May 4, 2016)

# Contributed by: Xplod, Rune Audio Forum
# Last change: PeteB May 03, 2016

begin
prog = irexec
button = KEY_PLAY
config = mpc toggle
repeat = 0
end

begin
prog = irexec
button = KEY_STOP
config = mpc stop
repeat = 0
end

begin
prog = irexec
button = KEY_NEXT
config = mpc next
repeat = 0
end

begin
prog = irexec
button = KEY_PREVIOUS
config = mpc prev
repeat = 0
end

begin
prog = irexec
button = KEY_FORWARD
config = mpc seek +00:00:10
delay = 2
repeat = 4
end

begin
prog = irexec
button = KEY_REWIND
config = mpc seek -00:00:10
delay = 2
repeat = 4
end

begin
prog = irexec
button = KEY_UP
config = mpc volume +2
delay = 2
repeat = 4
end

begin
prog = irexec
button = KEY_DOWN
config = mpc volume -2
delay = 2
repeat = 4
end

The pushbutton and cap in the pic below are part of my external supply and a different function, NOT part of the IR circuit, and the voltage display in the pic below is monitoring the USB 5V rail, NOT the 3.3V supply.

The IR sensor would normally be connected directly to the GPIO header. In my pics, it is on a proto board, for convenience, and to avoid having to solder directly to the Pi, or using jumpers. It is the only sensor I have tested with. The range with a Western Digital stock remote and new-ish batteries is at least 25 feet at 45 degrees (probably more head-on), and indoor lighting.

rastus

I'll be watching this thread closely, I have the PiFi DAC+ (and also have a PiFi DIGI+ not used right now). They both come with lircrc sensors built on to the board, and a remote is also supplied. I have read many threads elsewhere, have not attempted anything. I use my Pi setup with Openelec, so I don't need this setup for that, I use the TV remote with CEC. But for music this may be interesting, though without a display it would be useless. So far using only a remote web browser to control Rune. I'm just on my way out, when I return I'll try find the links I have for setting up the lircrc, these will be specific to the PiFi only. Anyway, good call on the thread.

TommyBoy

I allready have the whole table full of IR remotes, so please no more

I use Ipad and UI to control rune, the ipad runs days on its battery,
and I can still sit and surf on the net while rune plays my favorite music,
so what is the motivation of the IR ?
if you dont own an ipad or other "pad" then a cellphone with anykind of web browser is fine.

IF, I should ever think about implementing IR function of my rune player,
I suggest to map a few of the unused buttons on some of my Ir remotes allready laying on the table.
however each manufacturer uses their own command system, so a "learn" feature will be the COOLEST thing to implement !!
this way not so advanced users will be able to learn and store buttons and map their numbers, to a rune function.
no commandline coding needed, please, just setup and handle via UI

else many people will not know how to handle this.

PeteB

TommyBoy wrote...so what is the motivation of the IR ?

I don't want to tell anyone to abandon their ipad in favor of an old IR remote (!) That is definitely NOT my intention, at all, since I have a Nexus tablet sitting on the coffee table next to the remote.

I started this thread in the hopes of learning what functions other people are adding to their remotes (assuming they have one) so I don't have to reinvent the wheel (or remote

)

It is true that you have to edit a text file (lircrc file) to add functions, but so far I just cut and pasted mce commands into mine. I am hoping someone else will contribute a few new tricks, so I don't have to.

I use the same IR remote to control Kodi/Xbian, so my "motivation" (not sure I had any, tbh), was just to use the same remote for both. I am sure it would be a lot cooler with a Harmony remote, but my motivation may not stretch that far...

An IR sensor must me one of the easiest hardware features to add ($1 and three jumpers), if you do not have one already.

Other streaming players usually come with some kind of remote, IR or 2.4GHz, or the MCE-type remotes that plug into a USB port (MCE may be the best option for a learning remote). The IQAudio boards have a header for an IR sensor, I think. Odroid comes with one, and an OdroidC2/NEC remote is a $5 option.

rastus

Motivation: Because you can... why else does anyone do anything, because it can be done.

YannM

TommyBoy wrote...so what is the motivation of the IR ?

To skip a track in a romantic setting? Holding its tablet, enter the pin code, see the notifications/emails,... It can be a mood breaker

rastus

PeteB > This is the one I was going to follow, when I get around to it, don't know if it's of any help to you....

Kodi Audio Heaven With Pifi Digi+ and External DAC
http://www.nielsmayer.com/xwiki/bin/view/Raspberry+Pi/Kodi+Audio+Heaven+With+PiFi+Digi+SPDIF+HAT+and+External+DAC

Edit: Scroll down to "Using IR remote controls with PiFi Digi+ IR receiver with lirc(1)".

TommyBoy

thanks alot for all the feedback about the motivation to have an IR remote,
I tottally dig it

many of my IR remotes allready floating my table, have some unused buttions,
for hardware I dont own, I am sure the buttons send out codes,
so it could be the coolest thing, if my rune-player
could : skip track, mute, fastforward (ups not possible since the WAV bug is not solved yet)
when I press this buttons.
Allright :
The problem: all remotes use all sorts of own format,
so how do I teach rune, the pulse format and its code ?
here a listen and learn feature is a MUST ??
or a listen and debug mode ? to reveal the code, then I be happy to input it
manually into some config txt file.

PeteB

Programming buttons to control play/pause, skip, stop is fairly easy, because there is already a one-to-one correspondence to mpc commands which control play. In my first post in this thread I listed the ones I found in the tutorial by Xplod.

In addition to those, I have been able to use the un-assigned (Red/Grn/Yellow/Blue) buttons to play radio streams, so now radio works a little more like my old car stereo. I turn on power, push a button, and a station plays.

@Tommy: The remote codes are in a file called /etc/lirc/lircd.conf.d/lirc.conf, here is an example:

      begin codes
.
.
.
          KEY_STOP                 0x20DF
          KEY_PLAY                 0x50AF
          KEY_PREVIOUS             0x40BF
          KEY_NEXT                 0x807F
.
.
      end codes

You can record the codes yourself (extra work) or you can just search online for a file called lirc.conf for your remote. I did a search for "WDTV Live remote lirc.conf" and found plenty to choose from to get me started.

Basically one file (/etc/lirc/lircd.conf.d/lirc.conf) has the IR codes and key names. A second file (/etc/conf.d/lircrc) contains the key names and what action you want them to perform. In lircrc the section that corresponds to the play key looks like this:

.
.
.
begin
prog = irexec
button = KEY_PLAY
config = mpc toggle
repeat = 0
end
.
.
.

When I press the play/pause key, the remote sends out 0x50AF and lirc matches it to KEY_PLAY from the first file. Then, irexec executes the "mpc toggle" command, which controls the play/pause function.

AxelFendersson

Here's my lircrc:

begin
prog = irexec
button = KEY_RIGHT
config = mpc next
repeat = 0
end

begin
prog = irexec
button = KEY_LEFT
config = mpc prev
repeat = 0
end

begin
prog = irexec
button = KEY_UP
config = mpc volume +5
delay = 2
repeat = 4
end

begin
prog = irexec
button = KEY_DOWN
config = mpc volume -5
delay = 2
repeat = 4
end

begin
prog = irexec
button = KEY_PLAY
config = mpc toggle
repeat = 0
end

begin
prog = irexec
button = KEY_MENU
config = mpc stop
repeat = 0
end

begin
prog = irexec
button = KEY_OK
config = mpc play 1
repeat = 0
end

It's fairly basic. I only really want an IR remote for quick access to basic things like play/pause, skip, etc.; for anything more complicated it makes more sense to use the web/mobile interface. So I got an Apple remote, as it only had a relatively small number of buttons. I've modified mine slightly by painting over the 'menu' button with a 'stop' symbol.

Also, although I have mapped the up and down buttons to control the volume, I don't actually use them. I've disable software volume control as my RPi outputs into my hi-fi and I use the volume control on that.