MCEUSB IR blasting in Libreelec

Here's the link to the testbuild:

LibreELEC-RPi2.arm-8.2-devel-20171130133422-r26229-ga24418465c.tar

ir-ctl doesn't to any automatic repeat handling, it just transmits each scancode once.

With the new version you can specify the delay (gap) between signal transmits on the command line. It should be about 25000.

To send out 3 repeats with 25ms inbetween do this:

ir-ctl -g 25000 -S sony12:0x100015 -S sony12:0x100015 -S sony12:0x100015

You can also store scancodes in a file, like this:

LibreELEC:~ # cat sony-power.irctl
scancode sony12:0x100015
scancode sony12:0x100015
scancode sony12:0x100015

and transmit that with ir-ctl

ir-ctl -g 25000 -s sony-power.irctl

As an alternative you can specify the delay between scancodes in the file

scancode sony12:0x100015
space 25000
scancode sony12:0x100015
space 25000
scancode sony12:0x100015

In that case the -g option of ir-ctl is not needed

One thing to keep in mind is that when sending a file all of it will be transmitted in a single call - and you can run into the limit of the lirc device. When using -s or -S multiple times each of the scancodes / files are transmitted in separate calls, so you don't run into the limits that easily.

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

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

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

HiassofT

Sorry for resurrecting this topic

I have a Philips SRM-5100 / MCE universal remote control

That was saved for a long time!

This one works with LibreELEC perfectly.

I do not need to do anything at all.

Plus the power button does not turn on the box, it just turns off.

My question, it is possible to edit any key if yes how to proceed.

Thank you,

What box are you using?

On PCs power on by USB or CIR usually has to be enabled in the BIOS.

On AML boxes this is would be handled by u-boot, the vendor u-boot version might be tied to the remote that came with the box, not sure if power on by USB is supported. Not really my area

so long,

Hias

Quote from HiassofT

What box are you using?

On PCs power on by USB or CIR usually has to be enabled in the BIOS.

On AML boxes this is would be handled by u-boot, the vendor u-boot version might be tied to the remote that came with the box, not sure if power on by USB is supported. Not really my area

so long,

Hias

Good friend I'm using KI Pro mecool!

We did not need the usb, the controller picked up right without accessories

Well, thank you for clarifying.

The easiest way to do that with ir-ctl would be to capture the raw signals to a file and then send those. for example:

record a button to file "tv-power"

ir-ctl -1 --receive=tv-power

transmit the signal:

ir-ctl --send=tv-power

An alternative would be to use lircd if you can find a lircd.conf with the signals/codes for your TV.

Converting those various "ir codes" you find on the net to a format suitable for ir-ctl or lircd isn't easy as there's no real standard for them.

so long,

Hias

It could be that you need to transmit the IR code multiple times - my old Panasonic CRT TV only powered up if the power button was held down for about 0.5-1 seconds.

You could try something like this:

ir-ctl -g 75000 --send=button-power--send=button-power--send=button-power--send=button-power--send=button-power

"-g 75000" sets the gap / pause between IR signals to 75ms - that's about the value I see with my panasonic remote. You can also try other values in the range of (about) 50000 to 100000.

To add more repeats just add --send... more often - maybe try with 10 instead of 5 if it doesn't work.

It's a bit odd though that the TV didn't blink when you sent the code (IIRC my old CRT TV blinked shortly, multiple times when powering up).

It could be that the recorded signals aren't accurate enough - MCEUSB has 50µs resolution and this page Description of the panasonic infrared protocol (REC-80) says the intervals are about 420µs in USA and 450 in europe (not sure if that's correct, different lengths are quite odd).

so long,

Hias