From: Bengt M. <bu...@be...> - 2014-06-22 22:01:20
|
Hi, the configuration file looks ok; it is NEC1-codes in the first part (with the exception of KEY_DOWN, which is NEC2, probably an unclean capture), the last 4 are NEXx2. In detail: KEY_UP: NEC1 Device: 130.19 Function: 19 KEY_LEFT: NEC1 Device: 130.19 Function: 21 KEY_DOWN: NEC2 Device: 130.19 Function: 23 KEY_RIGHT: NEC1 Device: 130.19 Function: 22 KEY_HOME: NEC1 Device: 130.19 Function: 17 KEY_MODE: NEC1 Device: 130.19 Function: 18 KEY_PROGRAM: NEC1 Device: 130.19 Function: 20 KEY_POWER: NECx2 Device: 7.7 Function: 2 KEY_VOLUMEUP: NECx2 Device: 7.7 Function: 7 KEY_VOLUMEDOWN: NECx2 Device: 7.7 Function: 11 KEY_MUTE: NECx2 Device: 7.7 Function: 15 Given that the sending works on an x86 but not an RPi, the problem is likely either in the USB drivers or in the TIRA driver. > Hm... when sending data, lirc tries to encode it using lircd.conf which > otherwise is used to decode. From the log we can see that this does not > work. As a shot in the dark, what happens if you convert the raw codes > in lircd.conf to a regular file using irrecord -a and then tries to send > using this config file? Unlikely... If it still does not work, perhaps you could > make it happy by modifying the eps/aeps values. these parameters are using when attempting decoding, not sending. |