Re: scancodes identified as invalid (I found the problem)

Hi John, On Mon, Jul 22, 2019 at 11:44:02AM +, John G wrote: > Hi Sean, > Using s = 0x20df10ef, protocol_scancode_valid() will return false (meaning it > is not a valid scancode). > > s>>24 = 0x0020 > s>>16 = 0x20df > ~(0x20df) = 0xdf20 > ( 0x0020 ^ 0xdf20) = 0xdf00 > 0xdf00 & 0xff

Re: scancodes identified as invalid

Hi, On Sun, Jul 21, 2019 at 11:33:54PM +, John G wrote: > Hi Sean, > > Thank you for the reply and the links! (difficult to find with Google) > > >  I'm not sure what the nec1 protocol is exactly. This sounds like a > >AnalysIR invention. > > Actually, NEC1 is noted at irdb.tk (IR code d

Re: scancodes identified as invalid

Hi, On Fri, Jul 19, 2019 at 06:50:05AM -0500, JohnG wrote: > I have POWER_KEY scancodes, that work as RAW data with ir-ctl -s [file], but > are not working with ir-ctl -S: > >     0x20df10ef (POWER_KEY for my LG tv) >     0x02FD48B7 (POWER_KEY for my Toshiba tv) As you can see here https://www.s

scancodes identified as invalid

I have POWER_KEY scancodes, that work as RAW data with ir-ctl -s [file], but are not working with ir-ctl -S:     0x20df10ef (POWER_KEY for my LG tv)     0x02FD48B7 (POWER_KEY for my Toshiba tv) rc6_mce:0x800f0410 works, as does nec32:0x800f0410 (though not nec:0x800f0410), so it doesn't seem t