-
Notifications
You must be signed in to change notification settings - Fork 10
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
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit #1
Comments
Don't expect real compatibility with IRRemote- the similarity is quite superficial. If you look at the headers, you can see that more complicated configurations will look nothing like IRRemote. |
Thanks for the quick reply. Yeah, I know there are very different kinds of remote codes, I guess I'm just lucky that for NEC they work exactly the same with your lib and the IRRemote lib I was using. Makes it convenient to be able to re-use the same codes. |
as you guessed, switching to 3.3V power helped a bit, especially with RMT. With one IR receiver, I'm seeing an endless list of those With another one, those go away, but I'm still seeing spam lines when proper codes are received and decoded: I hate to comment it out altogether as it would be nice for it to trigger only at the right times. I'm using this receive only code I sent you as PR: Also, please check that I didn't mess anything up when I cleaned all compile errors |
When using my TV remote it doesn't know how to decode, I see Doesn't need to be fixed, pasting just in case |
What is the tv remote? I don't have all the signal groups in there. If you can get IRremote to work with it on a 8266 or the like, you can figure out what the timing rates should be, and add it into IR32.h. |
mmmh, that was in April, I don't remember which remote I used, nor do I really need it to work, I was just testing it to see if it was my NEC remote that had an issue or any remote. |
The length 2 items are just a start seq and end seq and I think that this is a repeat code. |
First, thanks for this code, it works ok enough for me and is the first code I could find that worked with RMT.
Also, thank you for making the output compatible with IRRemote.
When I use it though, I get a lot of these output lines. Is that expected spam or an issue with my receiver?
I tried switching to another IR receiver that worked ok with the interrupt code, and I get almost no output from it (95% failure), just more lines of spam.
I do power it from 5V and have its output line connected directly to the ESP32 input 34.
This uses digitalread equivalent, so it's not impacted by the analog input issues on ESP32, and therefore which input pin I use shouldn't matter, correct?
Received: NEC/0xff827d
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
Received: NEC/0xff827d
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
Received: NEC/0xff827d
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
Received: NEC/0xff827d
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
Received: NEC/0xff827d
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
[E][IRRecv.cpp:93] rx_parse_items(): Item length was only 2 bit
The text was updated successfully, but these errors were encountered: