Rp3 b+ - irrecord issue - Something went wrong. Please try again

Help and Support Raspberry Pi
1

Hi,

System: Linux osmc 4.19.55-6-osmc #1 SMP PREEMPT Sun Nov 3 22:15:28 UTC 2019 armv7l GNU/Linux

I try to configure my remote SAMSUNG AK59-00148A but i encounter an issue when i recording the keys with irrecord.

$ mode2 -d /dev/lirc0
...
pulse 542
space 1465
pulse 546
space 1469
pulse 540
pulse 119002

$ irrecord -d /dev/lirc0 ~/remote.conf
Press RETURN now to start recording.
................................................................................
Found const length: 120493
Please keep on pressing buttons like described above.
................................................................................
Space/pulse encoded remote control found.
Signal length is 77.
Found possible header: 4571 4467
Found trail pulse: 551
No repeat code found.
Signals are space encoded.
Signal length is 37
Now enter the names for the buttons.

Please enter the name for the next button (press <ENTER> to finish recording)
KEY_0

Now hold down button "KEY_0".
Something went wrong. Please try again. (9 retries left)
Something went wrong. Please try again. (8 retries left)
Something went wrong. Please try again. (7 retries left)

I found this topic so I patched/compiled locally the LIRC Libraries and tools to use a fixed irrecord but I still have the error.

My ir receiver reference is TSOP2238 - 38kHz. Plugged on GPIO 18. Here my settings in osmc.

Any help is welcome.

2

It’s hard to say without knowing what changes you’ve made to LIRC or even which versions of LIRC you now have on your system.

Sam

3

As I said, I just proceeded to local compilation and patching of the lirc lib for test only. So the lirc lib and tools used by the system is unchanged.

4

I think the whole LIRC package may need to be replaced.

You could try building the armv7-lirc-osmc package with the patch you referred to and see if this helps. It would also be good to know if we need this patch for recording only and if receiving is otherwise fine. It may be difficult for us to ship this patch included by default as the armv7-lirc-osmc package is shared across other systems.

5

Hi, sorry for the delay.

So, I successfully built and installed the armv7-lirc-osmc from lirc 0.9.4c with the corresponding patches. I was able to create a configuration file with irrecord -d /dev/lirc0 with the devinput driver but not with the default driver.

Anyway, once the remote config file is selected and the two services up (eventlircd and lircd_helper@lirc0), it seems that my remote controller is still not recognized. I loose my mind…

Here my remote config file:

# 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
# <lirc@bartelmus.de>
#
# This config file was automatically generated
# using lirc-0.9.4c(devinput) on Sat Jun 13 20:45:19 2020
# Command line used: -d /dev/lirc0 remote.conf
# Kernel version (uname -r): 4.19.122-1-osmc
#
# Remote name (as of config file): samsung-ak59-00148a
# 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  samsung-ak59-00148a
  driver devinput
  bits           56
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  pre_data_bits   72
  pre_data       0x11
  gap          29767
  toggle_bit_mask 0x0
  frequency    38000

      begin codes
          KEY_OK                   0xDD010000001174
          KEY_UP                   0xD301000000117C
          KEY_DOWN                 0xDA010000001177
          KEY_RIGHT                0xD9010000001175
          KEY_LEFT                 0xD4010000001177
          KEY_BACK                 0xD8010000001175
          KEY_EXIT                 0xDA010000001173
          KEY_INFO                 0xD301000000117A
          KEY_TITLE                0xD4010000001174
          KEY_POWER                0xD0010000001177
          KEY_NUMERIC_1            0xDB010000001177
          KEY_NUMERIC_2            0xD001000000117B
          KEY_NUMERIC_3            0xE8010000001165
          KEY_NUMERIC_4            0xD3010000001171
          KEY_NUMERIC_5            0xE201000000116D
          KEY_NUMERIC_6            0xD5010000001183
          KEY_NUMERIC_7            0xD101000000117A
          KEY_NUMERIC_8            0xD601000000116B
          KEY_NUMERIC_9            0xD5010000001172
          KEY_NUMERIC_0            0xD4010000001178
          KEY_PLAY                 0xCE010000001173
          KEY_PAUSE                0xF0010000001156
          KEY_STOP                 0xDC010000001171
          KEY_HOME                 0xD8010000001172
      end codes

end remote
6

Do you have another remote that you could check with?

7

Same issue with an another remote. I can create a configuration file with irrecord -d /dev/lirc0 but the remote is not recognized. I don’t understand what is wrong.

8

What do you mean by the remote is not recognised? Key presses don’t register at all?

9

I mean when i press the keys previously registered with irrecord and stored in the config file, nothing happens.

10

Are you perhaps testing for recognition when the services and Kodi are running? You would need to stop eventlircd and Kodi to test on the command line.

11

Yes, in OSMC.

Ok I will try.