ESP32-S3 NEC code not sent correctly #1169

cytan299 · 2023-09-19T01:54:49Z

cytan299
Sep 19, 2023

HI,
Thanks for writing this library. It's greatly appreciated.

Unfortunately, I'm having problems sending IR codes with the ESP32-s3. (It's probably pilot error).

First I used ReceiveDemo.ino to get the IR code for vol+ for my Vizio TV (note: I used D12 for receive)

Protocol=NEC Address=0x4 Command=0x2 Raw-Data=0xFD02FB04 32 bits LSB first
Send with: IrSender.sendNEC(0x4, 0x2, <numberOfRepeats>);

Then for sending, I did the following in my ESP32 (I disabled receive and used D12 for transmit)

#define DISABLE_CODE_FOR_RECEIVER
#define NO_LED_FEEDBACK_CODE
#define IR_SEND_PIN 12
#include <IRremote.hpp>

void setup(){
...
IrSender.begin(DISABLE_LED_FEEDBACK);
....
}

void doit()
{
...
IrSender.sendNEC(0x4,0x2,3);
...
}

Unfortunately the above code didn't change the volume of my TV. So, I programmed another ESP32 to read the IR with RecevieDemo.ino. I got the following result from the above ESP32:

20:01:18.889 ->
20:01:18.889 -> Protocol=Onkyo Address=0xFBFC Command=0xFDFA Raw-Data=0xFDFAFBFC 32 bits LSB first
20:01:18.889 -> Send with: IrSender.sendOnkyo(0xFBFC, 0xFDFA, );
20:01:18.939 ->
20:01:18.939 -> Protocol=UNKNOWN Hash=0x0 2 bits (incl. gap and start) received
20:01:18.939 -> Received noise or an unknown (or not yet enabled) protocol
20:01:18.939 -> rawData[4]:
20:01:18.939 -> -23400
20:01:18.939 -> +9000,-3000
20:01:18.939 -> + 600
20:01:18.939 -> Sum: 12600
20:01:19.019 ->
20:01:19.019 -> Protocol=UNKNOWN Hash=0x0 2 bits (incl. gap and start) received
20:01:19.052 -> Received noise or an unknown (or not yet enabled) protocol
20:01:19.052 -> rawData[4]:
20:01:19.052 -> -99400
20:01:19.052 -> +9000,-3000
20:01:19.052 -> + 600
20:01:19.052 -> Sum: 12600
20:01:19.151 ->
20:01:19.151 -> Protocol=UNKNOWN Hash=0x0 2 bits (incl. gap and start) received
20:01:19.151 -> Received noise or an unknown (or not yet enabled) protocol
20:01:19.151 -> rawData[4]:
20:01:19.151 -> -99400
20:01:19.151 -> +9000,-3000
20:01:19.151 -> + 600

At first, I thought it looked the address and command bits were not'ed:
0x04 ->0xFC

but
0x02 does not map to 0xFA

so there goes that theory.

Is there some flag I need to throw to get the bits sent out correctly?

Thanks for any help.

cytan

ArminJo · 2023-09-19T07:04:08Z

ArminJo
Sep 19, 2023
Maintainer

Please post the timing dump of the received protocol, using debug pin of RecevieDemo.ino.
The timing seems to be totally broken.
Check the distance to receiver and power of the sending LED.

7 replies

cytan299 Sep 20, 2023
Author

Yes, I'm using Wifi with this project. I can comment out the Wifi to see if the timing improves. I'll do that tonight. But I am not running any Wifi server or looping to check for packets during this test. But I'll comment the Wifi code out for the test.

However, my project requires Wifi and so if IRremote works without Wifi, then it is not that useful for me. So, is there a timing parameter I can tweak to make IRremote work if that's the problem?

cytan

cytan299 Sep 21, 2023
Author

Hi Armin,
I've commented out my WIFI code and tried again. This is the result, which is a little bit different than before, but obviously incorrect:

Protocol=Onkyo Address=0xFBFC Command=0xFDFA Raw-Data=0xFDFAFBFC 32 bits LSB first
Send with: IrSender.sendOnkyo(0xFBFC, 0xFDFA, <numberOfRepeats>);
rawData[68]:
-3276750
+9800,-4450
+1500,- 550 +1500,- 500 +1500,-1950 + 600,-1400

600,-1400 + 600,-1400 + 600,-1400 + 600,-1400
600,-1650 + 550,-1700 +1500,- 550 +1450,-2000
600,-1650 + 600,-1650 +1500,-2000 + 600,-1650
600,-1150 + 600,-1650 + 600,-1150 + 550,-1450
550,-1450 + 550,-1450 + 550,-1450 + 550,-1450
550,-1700 + 600,-1150 + 600,-1650 + 600,-1650
+1500,-2000 + 550,-1700 + 600,-1650 +1550,-1950
600
Sum: 88350

Protocol=UNKNOWN Hash=0x0 2 bits (incl. gap and start) received
Received noise or an unknown (or not yet enabled) protocol
rawData[4]:
-98450
+9000,-3000

600
Sum: 12600

Protocol=UNKNOWN Hash=0x0 2 bits (incl. gap and start) received
Received noise or an unknown (or not yet enabled) protocol
rawData[4]:
-98400
+9000,-3000

600
Sum: 12600

So, is there a way to tune the timing?

cytan

ArminJo Sep 23, 2023
Maintainer

How will you tune random timing errors?

cytan299 Sep 23, 2023
Author

The output looks random may be due to some type of clock slippage, i.e. the frequency is not quite right between the sender and the receiver causing synchronization problems. Perhaps a tweak in the mark and space widths, and the clock divider will fix the problem. See below.

In the mean time, I decided to try the RMT module (remote control transceiver) that is already built into the ESP32:

https://docs.espressif.com/projects/esp-idf/en/v4.4/esp32/api-reference/peripherals/rmt.html

and actually got my ESP32 to spit out the correct code.

Raw data sent:

uint16_t rawData[67]={9000,4400,
600, 550, 550, 550, 600,1600, 600, 550,
600, 500, 600, 500, 600, 500, 600, 550,
600,1600, 600,1650, 600, 500, 600,1650,
600,1600, 600,1650, 600,1600, 600,1650,
600, 500, 600,1650, 600, 500, 600, 500,
600, 550, 600, 500, 600, 500, 600, 550,
600,1600, 600, 500, 600,1650, 600,1600,
600,1650, 600,1650, 600,1600, 600,1650,
600};

which I then tweaked in the RMT settings:


void buildItem(rmt_item32_t &item,int high_us,int low_us){
  item.level0 = 1;
  item.duration0 = high_us - 50; // remove 50 us
  item.level1 = 0;
  item.duration1 =  low_us + 50; // add 50 us
}

and then I got nearly perfect reception:

Received:

Protocol=NEC Address=0x4 Command=0x2 Raw-Data=0xFD02FB04 32 bits LSB first
Send with: IrSender.sendNEC(0x4, 0x2, <numberOfRepeats>);
rawData[68]:
-3276750
+9000,-4400

600,- 550 + 550,- 550 + 600,-1600 + 600,- 550
600,- 500 + 600,- 500 + 600,- 500 + 600,- 550
600,-1600 + 600,-1650 + 550,- 550 + 600,-1650
600,-1600 + 600,-1650 + 600,-1600 + 600,-1650
600,- 500 + 600,-1650 + 600,- 500 + 600,- 500
600,- 550 + 600,- 500 + 600,- 500 + 600,- 550
600,-1600 + 600,- 500 + 650,-1600 + 550,-1650
600,-1650 + 600,-1650 + 600,-1600 + 600,-1650
600
Sum: 67500

BUT I had to change the clock divider to 40 (I started with 80) to get the above to work! This means that the clock is at 40 MHz???
Somewhere in the compile, there is a message that said this:

esptool.py v4.2.1
Serial port /dev/cu.usbmodem14201
Connecting...
Chip is ESP32-S3
Features: WiFi, BLE
Crystal is 40MHz

Where does this 40 MHz come from and is it affecting the timings?

Anyway, food for thought. I'll be monkeying with it some more to understand what's going on. And, it still doesn't change the volume of my TV yet, because I'll have to figure out the NEC repeat waveform for the RMT.

cytan

P.S. I'd be glad to share the RMT code with you, when I'm happy with the result.

ArminJo Sep 23, 2023
Maintainer

Wow 😲

cytan299 · 2023-09-23T02:20:01Z

cytan299
Sep 23, 2023
Author

This may be a long shot, but the esp32-s3 runs at 240 MHz. Is there something that needs to be changed because of this clock frequency?

cytan

0 replies

AnalysIR · 2023-09-23T14:42:58Z

AnalysIR
Sep 23, 2023

ESP clock speed can be selected in the tools menu of the Arduino IDE...you may have selected 40Mhz before

2 replies

cytan299 Sep 24, 2023
Author

It looks like one of the Adafruit libraries, I think it is the NeoPixel library (I am not flashing the NeoPixel when I use the RMT library) which also uses the RMT feature of the ESP32, is setting this to the XTAL clock, which is 40 MHz. My solution is for me to set it back to the 80 MHz clock before I send out the pulses.

Unfortunately, it looks like there is some power problems with my IR LED, sometimes it changes the volume of my TV, sometimes it doesn't although IRremote::ReceiveDemo seems to see the correct codes + 1 repeat. Have you ever seen this type of problem before?

cytan

cytan299 Sep 25, 2023
Author

It looks the intermittent problem (which I'm only about 1 m away from the TV) was that simply driving the IR diode with a current limiting resistor (150 ohms) just doesn't give me enough range. Then I tried a transistor circuit recommended by the ESP8266 authors:
https://github.com/crankyoldgit/IRremoteESP8266/wiki#ir-sending
Doing it this way still didn't give enough range.

Finally with the constant current circuit
https://www.analysir.com/blog/2013/11/22/constant-current-infrared-led-circuit/
I was able to get the range and I am now able to get the TV to see the IR signal when I'm only about 1 m away. Very strange.

cytan

cytan299 · 2023-10-16T12:42:20Z

cytan299
Oct 16, 2023
Author

10000

As promised here's the code using the onboard ESP32-S3 RMT for sending NEC codes (IR_TX.cpp and IR_TX.hpp)

https://github.com/cytan299/Ultrasonic_Screwdriver/tree/main/ultrasonic_screwdriver

I only did the transmit part because that was what I needed.

Hopefully, it'll help with your code for the ESP32.

cytan

2 replies

ArminJo Oct 16, 2023
Maintainer

Thanks for contributing.
Normally *.hpp are *cpp code sources which must be included to enable evaluation of macros, set before the include (especially required for Arduino!).
Your IR_TX.hpp looks more than an old plain IR_TX.h file.

cytan299 Oct 17, 2023
Author

Hi Armin,
I'm actually not sure what you mean because the preprocessor will run before the compiler is run, so the source code will be unmangled for the compiler with whatever preprocessor commands that were embedded in the code.

In my style of writing, I always use *.hpp as headers for C++ sources. *.h should work as well. IR_TX.hpp is just simply included in the ino file as a declaration of the IR_TX class. For example, in ultrasonic_screwdriver.ino, I have this:

.
.
.

/*
  The IR diode
*/

#include "IR_TX.hpp"

IR_TX ir_tx(RMT_CHANNEL_0, GPIO_NUM_12);

.
.
.

Anyway, I hope that my code is useful for your ESP32 implementation.

cytan

vednildip · 2024-11-12T03:56:57Z

vednildip
Nov 12, 2024

On Arduino IDE environment receiver code :- ESP32 S3 Liligo T HMI (Used Pin 18 receiver) - when Remote operated Guru Meditation - Reboot error

1 reply

cytan299 6D4E Nov 12, 2024
Author

Sorry, hard to know why it's Guru meditation. Unfortunately, I've given away my sonic screwdriver and with it the ESP32-S3 so I cannot test.

cytan

ESP32-S3 NEC code not sent correctly #1169

Uh oh!

cytan299 Sep 19, 2023

Replies: 5 comments · 12 replies

Uh oh!

ArminJo Sep 19, 2023 Maintainer

Uh oh!

cytan299 Sep 20, 2023 Author

Uh oh!

cytan299 Sep 21, 2023 Author

Uh oh!

ArminJo Sep 23, 2023 Maintainer

Uh oh!

cytan299 Sep 23, 2023 Author

Uh oh!

ArminJo Sep 23, 2023 Maintainer

Uh oh!

cytan299 Sep 23, 2023 Author

Uh oh!

AnalysIR Sep 23, 2023

Uh oh!

Uh oh!

cytan299 Sep 24, 2023 Author

Uh oh!

Uh oh!

cytan299 Sep 25, 2023 Author

Uh oh!

cytan299 Oct 16, 2023 Author

Uh oh!

ArminJo Oct 16, 2023 Maintainer

Uh oh!

Uh oh!

cytan299 Oct 17, 2023 Author

Uh oh!

vednildip Nov 12, 2024

Uh oh!

cytan299 6D4E Nov 12, 2024 Author

cytan299
Sep 19, 2023

Replies: 5 comments 12 replies

ArminJo
Sep 19, 2023
Maintainer

cytan299 Sep 20, 2023
Author

cytan299 Sep 21, 2023
Author

ArminJo Sep 23, 2023
Maintainer

cytan299 Sep 23, 2023
Author

ArminJo Sep 23, 2023
Maintainer

cytan299
Sep 23, 2023
Author

AnalysIR
Sep 23, 2023

cytan299 Sep 24, 2023
Author

cytan299 Sep 25, 2023
Author

cytan299
Oct 16, 2023
Author

ArminJo Oct 16, 2023
Maintainer

cytan299 Oct 17, 2023
Author

vednildip
Nov 12, 2024

cytan299 6D4E Nov 12, 2024
Author