From: Bengt M. <bu...@be...> - 2014-06-25 17:44:22
|
Hi Joel, On 06/25/14 06:20, Joel Ebel wrote: > On Sat, May 3, 2014 at 1:06 PM, Bengt Martensson > <bu...@be... <mailto:bu...@be...>> wrote: > > Remains to find out what the original Roku really is sending (and why). > Lacking one such, I cannot directly help. Possibly you can capture some > sequences with another tool, like mode2? > > > I got my hands on a real roku remote, and what it's doing is surprising > to me, and I'm not sure how to express it in an lircd.conf. irrecord > gave me the same double codes as I got before. Looking at mode2, the > roku remote sends only the first code for a momentary press, and for a > held down button, it repeats the second code as long as you hold it > down. For instance, for Blockbuster, which is 0x04FB 0x05FA, If I hit > the button briefly, it sends only 0x04FB. If I hold it down, it sends a > single 0x04FB, then 0x05FA over and over. This is very different from > what lirc transmits from the same config, which you observed to be > always sending and repeating the pair. A consequence of this also seems > to be that lirc doesn't detect the roku remote signal unless I hold it > down long enough to send the second code at least once, and then, no > matter how long I hold it down, lirc only detects the code a single time. Thanx for verifying this. It is essentially consistent with the "Pronto Hex" signals here; http://www.remotecentral.com/cgi-bin/mboard/complete/thread.cgi?keywords=5178&highlight=roku The sad fact is that, at least as I understand it, LIRC cannot reproduce this kind of signals. It can either repeat the whole payload, or it can repeat a short "ditto" signal, (like in NEC1) given by the many parameters. It can not, as opposed to other systems, have one reasonably complex "intro" sequence, and another, reasonably complex "repeat sequence". LIRC was written at a point of time when we knew much less about IR signals than we do today. Sorry. Bengt |