Posts by HiassofT

In most cases you don't need lirc, the majority of remotes are supported directly by the linux kernel.

It's main purpose is to support rather odd remotes that aren't supported by the kernel and to use standard remotes with older IR receiver drivers (like lirc_rpi on the Raspberry Pi) that don't offer in-kernel decoding of remote signals - therefore lirc currently ships with a default config that is similar to the kernel default IR config.

In LE9 support for those older lirc-only IR drivers will be dropped and the plan is to use Lirc only for those "odd remotes" and only if the user installed a custom lirc configuration file.

so long,

Hias

Disable Lirc in LE settings -> Services and reboot.

Not sure why it's causing 100% CPU usage though.

so long,

Hias

It's a simple static configuration via /etc/rc_maps.cfg, loading a "multi-table" when an IR receiver uses the rc-rc6-mce table. See this section in the wiki for details: infrared_remotes [LibreELEC]

so long,

Hias

Drop the rc-map-name DT parameter. Without that gpio-ir will default to the rc-rc6-mce table and LE will apply a default config that supports the xbox one remote out of the box.

so long,

Hias

First thing to check is to make sure you are using an adequate power supply. The official 5.1V 2.5A one is known to work fine.

Even small voltage dips can cause the USB network chip to "fall off the bus" or lock up.

When this has happened you could try to enable wifi in LE settings, this should allow you to get access to the RPi again and provide logfiles. Use the LE Settings addon or Samba method as described in the wiki how_to:provide_logfile [LibreELEC] - these methods include the system logs which are important to diagnose your issue (a kodi log alone won't be enough).

so long,

Hias

Check if eventlircd is running - if you stopped eventlircd that socket won't be there. run "systemctl start eventlircd" or reboot.

so long,

Hias

The socket is named /run/lirc/lircd, not /run/lircd/lircd. You can simply run "irw", as it will use /run/lirc/lircd per default.

See this wiki page for more info: infrared_remotes [LibreELEC]

so long,

Hias

You could try to alter the default lircd.conf file, there are some comments in it regarding repeats. First copy it over to /storage/.config

cp /etc/lirc/lircd.conf.d/xbox-dvd.conf /storage/.config/lircd.conf

Please keep in mind that the lirc_xbox driver which you are currently using for the xbox IR receiver won't be supported in LE9 - we removed it from our current development tree because it never made it upstream and started to make troubles. So you might be better off switching to a different remote or using another IR receiver (on the RPi a simple GPIO IR receiver should do fine).

so long,

Hias

please also post output of

journalctl -a | paste

plus a kodi debug log after this has happened.

Ah, and make sure lirc is disabled in libreelec settings.

so long,

Hias

ati_remote is the driver responsible for handling your RF receiver. rc_core is the base remote driver and rc_medion_x10 the keymap for your remote.

I'm not really familiar with the ati_remote driver, one thing that's a bit puzzling is that it has a repeat_delay option - usually that's handled by the input layer (you can configure delay and period eg via ir-keytable). Not sure at all what the repeat_filter option is for.

I still suspect the core issue is bad RF reception. Mounting a receiver inside a case isn't ideal - I even had problems with a Logitech unifying receiver if it was plugged into the back of a PC (and the whole metal case shielding off quite some of the RF signals from my K400 keyboard)., Plugging it into a front USB port made a huge difference.

so long,

Hias

Very odd. You could play around a bit with the gap between the signals, you can also edit the .raw files and change the "space 90000" in the middle of the files to something else.

Maybe we missed something with lirc. Could you retest that config and describe exactly which remote signals you transmitted via irsend and/or ir-ctl?

The way I checked with lirc was this:

- use the PHILIPS1 lircd.conf from your post #21

- after boot up / lirc start call "irsend SEND_ONCE PHILIPS1 KEY_INPUT_HDMI1

No other ir-ctl / irsend calls before, between or after that.

so long,

Hias

The processes you are seeing are normal. eventlircd is needed to translate the devinput event into lirc events for kodi.

As for your observations: this sounds a bit like you have wireless reception problems with the receiver - to weak signal or interference. Try to move the wireless remote receiver to some other location and also try replacing the batteries in your remote.

Other than that the ati_remote kernel module seems to have 2 parameters you could try playing with, repeat_filter and repeat_delay. Not sure what they actually do, just noticed these in modinfo

# modinfo ati_remote
...
parm:           channel_mask:Bitmask of remote control channels to ignore (ulong)
parm:           debug:Enable extra debug messages and information (int)
parm:           repeat_filter:Repeat filter time, default = 60 msec (int)
parm:           repeat_delay:Delay before sending repeats, default = 500 msec (int)
parm:           mouse:Enable mouse device, default = yes (bool)

Create a /storage/.config/modprobe.d/atiremote.conf file like this:

options ati_remote repeat_filter=XXX repeat_delay=YYY

so long,

Hias

I'm not sure if the toggle bit really is the problem here. With min_repeat=1 lirc will transmit 2 identical signals. On the next irsend invocation it'll again transmit 2 identical signals, but with the toggle bit flipped - this is also how normal rc5 IR remotes work.

You can try with the attached raw files - use "ir-ctl -s hdmi1.raw" or "ir-ctl -s hdmi1-toggle.raw" to send these.

hdmi1.raw is identical to what you'd get from sending rc5:0x304 twice. hdmi1-toggle.raw has the toggle bit flipped.

On the first irsend invocation lirc sends a signal identical to hdmi1-toggle.raw, on the second invocation it's identical to hdmi1.raw.

so long,

Hias

Can you post the output of

journalctl -a | paste

and a kodi debug log after you pressed some buttons - see here for details how_to:provide_logfile [LibreELEC]

so long,

Hias

Please post the output of the following commands

dmesg | paste
cat /proc/bus/input/devices | paste
ir-keytable
lsusb

Also provide a kodi debug log where you press several keys - see here for instructions: how_to:provide_logfile [LibreELEC]

so long,

Hias

The ir-ctl code 0x0304 looks about right, this is also the same code I'm seeing when testing with your lircd.conf file.

lirc however sends the signal 2 times (because of min_repeat 1). With ir-ctl you have to use a gap of about 90000 to get identical timing (rc5 has a fixed signal length of about 25ms and repeats every 114ms)

ir-ctl -g 90000 -S rc5:0x304 -S rc5:0x304

Converting between lirc codes and ir-ctl ones is a bit tricky. Lirc uses a raw representation of the received bits and ir-ctl a "logical" one - which means bit positions are shuffled around a bit or, like with the sony protocol, also in reversed order.

Actually, 0x304 in ir-ctl is the same as 0x10c4 in lirc, except for the toggle bit (which changes on every other button press and IIRC can't currently be changed in ir-ctl)

so long,

Hias

You can do that by creating a custom keymap file - this also allows you to select a different protocol. See the wiki page I linked above for details.

so long,

Hias

MCE keyboard is different to the standard rc6 MCE remote protocol. You could get it to work with a custom ir-keytable configuration (you receiver supports the mce_kbd protocol), but it'd be a lot easier if you just configured your harmony remote to use the standard MCE remote setup.

so long,

Hias