ESP32 Forum

Hello,

I'm building a simple project using the ESP32 WeMos LOLIN32 board.
I was looking for a good library to be able to interface with an IR remote (the one which you can see here: https://www.circuitbasics.com/wp-conte ... trol-3.jpg)
The receiver that I'm using is this one:

I tried using this example library: https://github.com/husarnet/esp-idf/blo ... nec_main.c, however the issue is that it seems like
it is failing to perform the initial NEC handshake (see nec specification here: https://www.sbprojects.net/knowledge/ir ... 201.125ms.. It seems like the duration of when my remote is sending signal is different from the one specified: One thing to note is that I needed to override the tolerance for the initial 9000 / 4500 header signal (Target duration duration: 9350 +- 400[/color]). The default target duration specified by the library is 9000 +- 20 which wouldn't work in my case. Similarly in the following logs you can see that sometimes the duration of the item is close to the 562 us, however the specification would expect the 1690 us in that moment (expecting a logical 1 signal).
Three questions:
-> Do you know if there is some preferred library for using IR remotes with esp-idf?
-> Could it be the case that my remote isn't using the NEC protocol but something else (e.g. Sony)?
-> Is it possible that the different durations are because of the 3.3V voltage of the microcontroller and it somehow messes up the calculation of the duration of the signal?

Thank you,
Szymon

Quick follow up:
Today I tried reading the inputs from the remote again and it seems to have fixed itself. ^ it correctly registered the button press.
The problem is that I still need to have those overrides for the expected durations of the initial transmission header.
Would you say that the discrepancy in those durations could be because the remote is of low quality / or the battery is running low?
Thanks

You can try the corresponding IDF example: https://github.com/espressif/esp-idf/tr ... ransceiver

Thanks for suggesting this.
In the end I managed to get the initial library to work.
It seems like offsetting the expected durations of the header signal has fixed all issues and now it is able to receive both the address and the data successfully.