Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The IR Protocol nec32 is not correctly handled in ir.py #42

Open
davecrump opened this issue Jul 17, 2020 · 2 comments
Open

The IR Protocol nec32 is not correctly handled in ir.py #42

davecrump opened this issue Jul 17, 2020 · 2 comments

Comments

@davecrump
Copy link

Apple TV remotes use nec32 protocol, which is handled with the 'nec' protocol setting of ir-keytable.

The IR code for Menu on my example remote is 0x87eede02. This seems to be correctly read from the handset.yaml file and is entered in the keytable (line 45 of ir.py) as 2280578562 (which is 0x87eede02 in decimal).

However, when the handset key is pressed, event.value (line 244 of ir.py) has the value -2014388734. I suspect that it is an overflow of some sort as 2280578562+2014388734=4294967296 which is 0x19999999.

Low priority.

@G0MJW
Copy link

G0MJW commented Jul 20, 2020

I noticed my Octagon remote is a little unreliable also - perhaps this is an issue. I found that when testing with the utility sometimes pressing a new button initially gave the previous button data. I assumed this was just a bug in the testing utility but maybe it is something more, like an uninitialised variable perhaps.

@davecrump
Copy link
Author

The testing utility is directly displaying the output of the Linux "ir-keytable -t" command, so very unlikely to be buggy. I would suspect your remote. The nec32 bug is deterministic, not random.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants