Problems decoding Sharp TV code. #351
Comments
|
Hi @jorgecis Just a quick observation, while you say it's using v2.2 of the library, I think the compiled code you are running is older than that. Versions v2.2 and newer don't have timing values rounded to the nearest 50 anymore. You might want to check you have the latest version (currently v2.2.1) and recompile/upload the dumpV2 example program. Can you please try doing that, and we can see where we are at after that? In the meantime I'll try to simulate what I can based on the data you've provided. |
|
Hi, Sorry, I was a victim of platformio, I have to force the update, anyway, using the last version looks a lot better. I got 3 times the following codes Encoding : SHARP
Encoding : UNKNOWN Code : 6322900E (16 bits)
The first one is detected as sharp but not the second one, also not sure why I got 3 pairs of codes every time. |
|
Phew. That looks a lot better. The multiple codes are explained (in part) by the comments here: https://github.com/markszabo/IRremoteESP8266/blob/master/src/ir_Sharp.cpp#L63 As you have a Sharp remote, that matches this protocol, can you please do me a favour and capture the entire output of the dumpV2 program just for a single button press? Oh, also what model remote control and TV it is would be a bonus too. Don't worry so much that it isn't recognising the second 'inverted' message, that's expected/normal operation at this point. The code it gives you for the first "chunk" is what matters when it comes to using the appropriate send() routine. |
|
Yes sure, here is the full output for a Sharp POWER TOGGLE, the model tv is Sharp LC-52D62U |
|
Interesting. Thanks for that. It seems to send a pair of (normal + inverted) messages 3 times. I might need to change/set the repeats to 2. (initial pair + 2 more pairs) Re: sendSharp() vs. sendSharpRaw() Yep, I get that it's confusing. I'll try to explain it a different way, if you then understand it, please feel free to come up with wording that will make it easier to understand of others. Send it as a PR, or put it here and I'll update the comments etc. Long story short, once upon a time, there was only Soooo ... TL;DR: If you are using our library to decode, the result should go into And if you don't get what I mean by bit order. try this |
|
Oh @jorgecis Could you please edit your previous message and add code block quotes around the output you supplied? i.e. https://help.github.com/articles/creating-and-highlighting-code-blocks/ It will stop the output from being mangled. Thanks in advance. |
|
Sure I already edit my comment, also in your comment you wrote: TL;DR: If you are using our library to decode, the result should go into use the same function in both cases❓ hehehe |
|
Yes, I meant it. In short, |
|
Just following up. How did you go? |
|
Using the sendSharpRaw everything works fine. the code is decode correctly and the send function works perfect. |
|
I'm glad it's working for you. Feel free to spread the word. ;-) |
|
In case useful for someone, I can confirm that in version 2.7.18 the command
works for Sharp Aquos LE835X, with data in the format e.g.
|
Lib Version
Lib Version 2.2
Expected behavior
Decode the infrared code as Sharp,
Actual behavior
The code is detected as unknown,
Output of raw data from IRrecvDumpV2.ino (if applicable)
Response from the Power Toggle
Encoding : UNKNOWN
Code : 6D5D1DB3 (16 bits)
Timing[31]:
+ 300, -1850 + 300, - 800 + 300, - 800 + 300, - 800
+ 300, - 800 + 300, - 800 + 300, -1850 + 300, -1850
+ 300, - 800 + 300, -1850 + 300, - 800 + 300, - 800
+ 300, - 800 + 300, -1850 + 300, - 800 + 300
uint16_t rawData[31] = {300,1850, 300,800, 300,800, 300,800, 300,800, 300,800, 300,1850, 300,1850, 300,800, 300,1850, 300,800, 300,800, 3
00,800, 300,1850, 300,800, 300}; // UNKNOWN 6D5D1DB3
Encoding : UNKNOWN
Code : 6322900E (16 bits)
Timing[31]:
+ 300, -1850 + 300, - 800 + 300, - 800 + 300, - 800
+ 300, - 800 + 300, -1850 + 300, - 800 + 300, - 800
uint16_t rawData[31] = {300,1850, 300,800, 300,800, 300,800, 300,800, 300,1850, 300,800, 300,800, 300,1850, 300,800, 300,1850, 300,1850,
300,1850, 300,800, 300,1850, 300}; // UNKNOWN 6322900E
Encoding : UNKNOWN
Code : 6D5D1DB3 (16 bits)
Timing[31]:
+ 300, -1850 + 300, - 800 + 300, - 800 + 300, - 800
+ 300, - 800 + 300, - 800 + 300, -1850 + 300, -1850
+ 300, - 800 + 300, -1850 + 300, - 800 + 300, - 800
+ 300, - 800 + 300, -1850 + 300, - 800 + 300
uint16_t rawData[31] = {300,1850, 300,800, 300,800, 300,800, 300,800, 300,800, 300,1850, 300,1850, 300,800, 300,1850, 300,800, 300,800, 3
00,800, 300,1850, 300,800, 300}; // UNKNOWN 6D5D1DB3
Encoding : UNKNOWN
Code : 6322900E (16 bits)
Timing[31]:
+ 300, -1850 + 300, - 800 + 300, - 800 + 300, - 800
+ 300, - 800 + 300, -1850 + 300, - 800 + 300, - 800
uint16_t rawData[31] = {300,1850, 300,800, 300,800, 300,800, 300,800, 300,1850, 300,800, 300,800, 300,1850, 300,800, 300,1850, 300,1850,
300,1850, 300,800, 300,1850, 300}; // UNKNOWN 6322900E
Encoding : UNKNOWN
Code : 6D5D1DB3 (16 bits)
Timing[31]:
+ 300, -1850 + 300, - 800 + 300, - 800 + 300, - 800
+ 300, - 800 + 300, - 800 + 300, -1850 + 300, -1850
+ 300, - 800 + 300, -1850 + 300, - 800 + 300, - 800
+ 300, - 800 + 300, -1850 + 300, - 800 + 300
uint16_t rawData[31] = {300,1850, 300,800, 300,800, 300,800, 300,800, 300,800, 300,1850, 300,1850, 300,800, 300,1850, 300,800, 300,800, 3
00,800, 300,1850, 300,800, 300}; // UNKNOWN 6D5D1DB3
Encoding : UNKNOWN
Code : 6322900E (16 bits)
Timing[31]:
+ 300, -1850 + 300, - 800 + 300, - 800 + 300, - 800
+ 300, - 800 + 300, -1850 + 300, - 800 + 300, - 800
uint16_t rawData[31] = {300,1850, 300,800, 300,800, 300,800, 300,800, 300,1850, 300,800, 300,800, 300,1850, 300,800, 300,1850, 300,1850,
300,1850, 300,800, 300,1850, 300}; // UNKNOWN 6322900E
Steps to reproduce the behavior
To repeat the issue you will use a real sharp remote control and the example. Looks like the code is there, becasue I got 3 times the same 2 raw codes.
The text was updated successfully, but these errors were encountered: