Posts by HiassofT

  • Classic Xbox remote control phantom clics

    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

    Code
    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

  • remote double button press

    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

  • MCEUSB IR blasting in Libreelec

    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

  • remote double button press

    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

    Code
    # 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:

    Code
    options ati_remote repeat_filter=XXX repeat_delay=YYY

    so long,

    Hias

  • MCEUSB IR blasting in Libreelec

    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

  • MCEUSB IR blasting in Libreelec

    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)

    Code
    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

  • MCE remote some key presses not recognized

    EV_MSC / scancode events are decoded IR signals, you get these whenever an ir signal is successfully received.

    Usually you also get EV_KEY (keyup/down) events - see the wiki page for details infrared_remotes [LibreELEC]

    If you see EV_KEY and EV_MSC for working buttons but nothing at all for the non-working ones something very odd is going on.

    In that case also check with "ir-ctl -r" (or mode2) if any signals are received at all.

    BTW: what kind of remote (manufacturer, model) are you using?

    so long,

    Hias

  • 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:

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

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

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


    and transmit that with ir-ctl

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

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

    Code
    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

  • MCEUSB IR blasting in Libreelec

    Thanks for the info, it could well be that the lirc hanging-bug causes it to somehow see and decode it's own signals.

    If that's the case you could try to disable the lircd-uinput service. This'll prevent the decoded signals to reach kodi, but it also means that controlling kodi via IR remote is no longer possible:

    Code
    systemctl mask lircd-uinput

    To re-enable lircd-uinput use "systemctl unmask lircd-uinput".

    Composing the sony scancodes for irctl is rather simple: the scancode is a 6-digit hex number, the first 2 digits are the device address (00-1f for sony12, 00-ff for sony15), next 2 digits are 00 (IIRC they'd be the 5 highest address bits in sony20) and the last 2 digits are the command (00-7f).

    So the KEY_POWER scancode I used for testing, 0x100015 means device address 0x10 (16 decimal) and command 0x15 (21 decimal).

    Just play around with the last 2 (command) digits, seems the first table on that webpage (sony 16) is the correct one for your receiver.

    BTW: Sean sent me a fix for ir-ctl and it's now also easier to send repeated commands. Which system are you using? If it's RPi2/3 I could upload you a 8.2.1 build with the fix included for testing.

    so long,

    Hias