I have been struggling the last couple of days to get my Argon One IR Remote to work. I have followed countless articles that either don’t work or break the OS. But finally I got the irrecord to work and output a lircd.conf file, however the remote still does not work under OSMC. Am I missing something? What else can I check?
- ArgonForty Argon One M.2 Case https://www.argon40.com/argon-one-m-2-case-for-raspberry-pi-4.html (IR receiver pad provided by the Argon One case is connected to GPIO 23 (physical
pin 16. Its on the hat PCB and cannot be changed) and appears to provide a 10k Ohm pull up resistor. The supply voltage for the IR receiver is 3.3 Volts. I guess it is TL1838)
- Argon IR Remote for Argon ONE V2 and M.2 Cases https://www.argon40.com/argon-ir-remote-for-argon-one-v2-and-m-2-cases.html
- Raspberry Pi 4 booting of SD card
- OSMC November 2020 2020.11-1 ([TESTING] Kodi v19 builds for Raspberry Pi 2/3/4)
- OSMC Updated (25.5.2021)
osmc@osmc:~$ sudo nano /boot/config.txt
# Warning: do not edit this file, or it could prevent your OSMC system from starting. # If you wish to make changes, you should do so via My OSMC or edit the config-user.txt file in this directory # Any changes that you make here will be overwritten as this file is managed by the OSMC via the update system [pi4] dtoverlay=rpivid-v4l2 arm_64bit=1 kernel=kernel.img [all] dtoverlay=vc4-kms-v3d,cma-512,lirc-rpi,gpio-ir,gpio_pin=23 disable_overscan=0 start_x=1 disable_splash=1 disable_fw_kms_setup=1 include config-user.txt
osmc@osmc:~$ sudo systemctl stop lircd_helper@lirc0
osmc@osmc:~$ sudo irrecord -d /dev/lirc0 /home/osmc/lircd.conf Running as regular user osmc Using driver devinput on device /dev/lirc0 irrecord - application for recording IR-codes for usage with lirc Copyright (C) 1998,1999 Christoph Bartelmus(firstname.lastname@example.org) This program will record the signals from your remote control and create a config file for lircd. A proper config file for lircd is maybe the most vital part of this package, so you should invest some time to create a working config file. Although I put a good deal of effort in this program it is often not possible to automatically recognize all features of a remote control. Often short-comings of the receiver hardware make it nearly impossible. If you have problems to create a config file READ THE DOCUMENTATION at https://sf.net/p/lirc-remotes/wiki If there already is a remote control of the same brand available at http://sf.net/p/lirc-remotes you might want to try using such a remote as a template. The config files already contains all parameters of the protocol used by remotes of a certain brand and knowing these parameters makes the job of this program much easier. There are also template files for the most common protocols available. Templates can be downloaded using irdb-get(1). You use a template file by providing the path of the file as a command line parameter. Please take the time to finish the file as described in https://sourceforge.net/p/lirc-remotes/wiki/Checklist/ an send it to <email@example.com> so it can be made available to others. Press RETURN to continue. Usually you should not create a new config file for devinput devices. LIRC is installed with a devinput.lircd.conf file which is built for the current system which works with all remotes supported by the kernel. There might be a need to update this file so it matches the current kernel. For this, use the lirc-make-devinput(1) script. Press RETURN to continue. Checking for ambient light creating too much disturbances. Please don't press any buttons, just wait a few seconds... No significant noise (received 0 bytes) Enter name of remote (only ascii, no spaces) :argonforty Using argonforty.lircd.conf as output filename Hold down an arbitrary key ................................................................................ Found gap (107949 us) Please enter the name for the next button (press <ENTER> to finish recording) KEY_UP Now hold down button "KEY_UP". Please enter the name for the next button (press <ENTER> to finish recording) KEY_RIGHT Now hold down button "KEY_RIGHT". Please enter the name for the next button (press <ENTER> to finish recording) KEY_DOWN Now hold down button "KEY_DOWN". Please enter the name for the next button (press <ENTER> to finish recording) KEY_LEFT Now hold down button "KEY_LEFT". Please enter the name for the next button (press <ENTER> to finish recording) KEY_OK Now hold down button "KEY_OK". Please enter the name for the next button (press <ENTER> to finish recording) KEY_INFO Now hold down button "KEY_INFO". Please enter the name for the next button (press <ENTER> to finish recording) KEY_HOME Now hold down button "KEY_HOME". Please enter the name for the next button (press <ENTER> to finish recording) KEY_BACK Now hold down button "KEY_BACK". Please enter the name for the next button (press <ENTER> to finish recording) KEY_VOLUMEUP Now hold down button "KEY_VOLUMEUP". Please enter the name for the next button (press <ENTER> to finish recording) KEY_VOLUMEDOWN Now hold down button "KEY_VOLUMEDOWN". Please enter the name for the next button (press <ENTER> to finish recording) KEY_POWER Now hold down button "KEY_POWER". Please enter the name for the next button (press <ENTER> to finish recording) Successfully written config file argonforty.lircd.conf
osmc@osmc:~$ sudo systemctl start lircd_helper@lirc0
Then I went to My OSMC > Remotes > Browse and import argonforty.lircd.conf, unfortunately it just not work. I have tried rebooting, recreating the lircd.conf file but OSMC just doesn’t respond to the IR remote.
# Please take the time to finish this file as described in # https://sourceforge.net/p/lirc-remotes/wiki/Checklist/ # and make it available to others by sending it to # <firstname.lastname@example.org> # # This config file was automatically generated # using lirc-0.9.4c(devinput) on Tue May 25 12:17:02 2021 # Command line used: -d /dev/lirc0 /home/osmc/lircd.conf # Kernel version (uname -r): 5.10.32-1-osmc # # Remote name (as of config file): argonforty # Brand of remote device, the thing you hold in your hand: # Remote device model nr: # Remote device info url: # Does remote device has a bundled capture device e. g., a # usb dongle? : # For bundled USB devices: usb vendor id, product id # and device string (use dmesg or lsusb): # Type of device controlled # (TV, VCR, Audio, DVD, Satellite, Cable, HTPC, ...) : # Device(s) controlled by this remote: begin remote name argonforty driver devinput bits 56 eps 30 aeps 100 one 0 0 zero 0 0 pre_data_bits 72 pre_data 0x23 gap 107949 toggle_bit_mask 0x0 frequency 38000 begin codes KEY_UP 0x3F010000001197 KEY_RIGHT 0x5B01000000118C KEY_DOWN 0x59010000001193 KEY_LEFT 0x5701000000119C KEY_OK 0x51010000001198 KEY_INFO 0x57010000001196 KEY_HOME 0x56010000001181 KEY_BACK 0x57010000001197 KEY_VOLUMEUP 0x5A010000001194 KEY_VOLUMEDOWN 0x50010000001198 KEY_POWER 0x55010000001197 end codes end remote
I read some threads that you have to disable the HiFiberry in dtoverlay as it is in colflict with PIN23. I don’t know if that is my problem or not. I don’t have a HiFiberry in there, but I also cannot find the command to do it. But its strange that irrecord works and OSMC does not. Is there maybe another place that I need to set Pin23 in OSMC for IR?
Thanks in advance!