I can switch my TV on using the following command:
irsend SEND_ONCE LG_AKB72915207 KEY_POWER
This is how I set it up.
I am using a Raspberry Pi P1 2011.12.
The bare Infrared LED connected to GPIO#18 and GND.
sudo apt-get install lirc -y
sudo nano /etc/modules
And add the following lines which ...
Please note that the infrared device has recently changed from lirc-rpi to
gpio-ir. As confirmed by @Pascal in his comment the setup also works with the new device name.
Here is how I got it to work. First of all: I use the latest Raspbian Stretch Lite 2018-03-13. With this version there is no /etc/lirc/hardware.conf anymore if you ...
No, your RS component is working fine, it's just that you have configured the LIRC driver and test it if it work. You got:
$ mode2 -d /dev/lirc0
It means that it's working.
The next step is to configure the remote controller before test it with the irw command. Use irrecord as below to generate the ...
Okay, I found the answer, or rather someone much more knowledgeable about Linux than me (https://raspberrypi.stackexchange.com/users/49162/jonathan-dieter) found it. :)
Rather than loading the lirc_rpi module in /etc/modules or /etc/rc.local, he suggested adding a new config file to /etc/modprobe.d/ (in my case /etc/modprobe.d/ir-remote.conf) with the ...
You need to place the lircd.conf file that you have recorded into /etc/lirc and then restart the service :
# Make a backup of the original lircd.conf file
sudo mv /etc/lirc/lircd.conf /etc/lirc/lircd_original.conf
# Copy over your new configuration file
sudo cp ~/lircd.conf /etc/lirc/lircd.conf
# Restart service
sudo /etc/init.d/lirc restart
@Besi thank you so much. It was really helpful for me.
For me I still have a problem when I reboot my rasp.
I think it's better to use to enable it on startup
systemctl enable lirc.service
sudo lircd --device /dev/lirc0
And now you needn't to edit the /etc/modules.
Here my install script :
# Echo in Blue
function echoBlue ()...
So apparently the only problem is that the lirc drivers are outdated and not present in newer versions of raspbian. Just change that to the new gpio-ir-tx driver and all will work fine. Also note the syntax for the pins changed slightly. I.e, this is what you need in your /boot/config.txt
I just want to record some IR signals so I can use them for a project.
Now I have written a short python function to write to TxD the IR code of Button Digit 1: b'\xa1\xf1\x00\xff\xa6'. I have also used a scope to display the wave form, to make sure it is clear an sharp.
Just had the same problem:
mode2 showed keypresses, but irw showed nothing.
No toggle bit mask found.
But I know for sure that RC6 has a toggle bit!
Kodi was reacting on some keys, not on others.
This entry in /boot/config.txt resolved my issue:
The answer to this was a very simple (and even dumber) one. It turns out that I was following the model B+'s pinout. The pin number 26 of raspberry pi 2 is somewhere else. I am posting the new pi's pinout here, just for future reference:
I have used an IR LED from a discarded remote to create an IR blaster.
You just need suitable resistors and a transistor to interface it to a Pi. I power mine from the Pi's 5V rail and switch it using a GPIO.
I used a NPN BC548 transistor.
The LED is driven from the 5V line. As I had no details on the IR LED I assumed it had a forward voltage of 1.7V and ...
So my Pi was configured correctly. Problem was at wiring. Transistor on DIOD was accidentally to big ant no signal goes through. I hope my debugging will help to solve similiar problems. Thanks for your time
Instead of running two instances on my pi I opted to make what is essentially a transistor switchboard (on a breadboard). I call each send command from a script which first runs another script that turns on one of three GPIOs, activating one of three transistors, and thus exposing one of three IR transmitters to receive signal from the single LIRC gpio.
You should always check that tutorials are up to date.
You should now be using device tree.
Remove the LIRC entries from /etc/modules.
Add the following line to /boot/config.txt and reboot.
NOTE: You MUST use GPIO numbers not physical pin numbers. There is no user GPIO36 so I assume you mean pin 36 on ...
After following this guide: http://www.raspberrypiwiki.com/index.php/Raspberry_Pi_IR_Control_Expansion_Board I encountered the same issue as stated in this question:
irsend: hardware does not support sending
I tried adding this line:
options lirc_rpi gpio_in_pin=18 gpio_out_pin=17
in /etc/modprobe.d/ir-remote.conf, but that didn't help either.
When I ...
I got an universal remote and recorded it with irrecord. Here is the config:
# Please make this file available to others
# by sending it to <email@example.com>
# this config file was automatically generated
# using lirc-0.9.1-git(default) on Tue Aug 30 18:19:24 2016
# contributed by
# brand: /storage/.config/tv.conf
Confirmed - Yes, this will work with the Raspberry Pi, and LIRC.
Plug it into the appropriate GPIO ports (3.3V, ground, and GPIO 17), with the Pi off.
Updated "/etc/modules" to include:
Recorded IR from a separate IR receiver (on port 18)
sudo /etc/init.d/lirc stop
irrecord -H default -d /dev/lirc0 -f NEW.conf
Copied the LIRC ...
Are there any other components on the module? From the dx.com page it looks like it's a bare LED. The 5V connection may not go anywhere.
IR LEDs are pretty current-hungry, and that's why the examples have a transistor to beef up the current. You may get a faint flicker connecting it directly (most cellphone cameras detect IR from LEDs quite well, btw), but ...
I had the same problem.
the services lirc reads the data which come from the driver of your ir receiver and transforms it into a VALUE (depending on your lircd.conf) and write it on a SOCKET which is located at /var/run/lirc/lircd by default.
Then the value written in the socket is transformed to a string interpreted by an an lirc client (an application), ...
supposedly 60mA max per pin
No, this is one figure sometimes floated as a total maximum for all GPIO pins. Note the pure 3.3V/5V power pins are not considered GPIOs and can supply much more than this, perhaps 1 A in total. In the picture you are using a 5V pin, which should be fine.
I've routinely drawn 100-150 mA total without issues (but YMMV!). The ...
I suggest you monitor the commands you are sending and compare them to the commands received from a unit known to work.
You can use my piscope to monitor the pulses. An alternative terminal based script is monitor.py.
Both programs require the pigpio daemon to be running (sudo pigpiod).
It's also worth checking to see if the range is the problem, i.e. ...
The electrical setup described in your link is defective by design: it relies on unspecified parameters of the transistor to regulate LED current. As a result, depending on the individual transistor you use, the current through the LED may be either excessive or not sufficient, so the circuit will work well for some people but not for others.
Using 5V line ...
Yes, it is possible to configure LIRC to use other GPIO pins. In /boot/overlays/README there is an example just about this:
Overlays are loaded using the "dtoverlay" directive. As an example, consider the popular lirc-rpi module, the Linux Infrared Remote Control driver. In the pre-DT world this would be loaded from /etc/modules, with an explicit "...