-
Notifications
You must be signed in to change notification settings - Fork 803
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
IRremoteESP8266 library sending wrong when send signal of 32 bits #2049
Comments
What is the full output that gave you the original 0xE0E0E01F ? You can see in tests that we are confident that sending the data will be received the same, given default parameters IRremoteESP8266/test/ir_Samsung_test.cpp Line 123 in a295f87
Maybe you can post full output from the dump program, (as requested in the issue template) |
Yes, that's right, I was sending lowercase letters, not capital letters , I thought they were the same because we send hex code |
If this is in code, then it is your compiler that deals with 0x.. to be converted to integer. You might have a compiler that does this differently, but that's unlikely, ther emust be something else, or are you sending this as text somewhere? |
Can you please post the minimalist code that reproduces the issue you have? |
Version/revision of the library used
v2.8.6
Describe the bug
when store signal of 32 bits of Samsung that read by irrecv.decode(&results) function , then when sending that signal by irsend.sendSAMSUNG(0xE0E0E01F, 32 );
then read it by irrecv.decode(&results) function again , the results not same between signal i store and signal i send
please help me
thanks
The text was updated successfully, but these errors were encountered: