I actually had a look at the esp_wifi_set_max_tx_power function this time and it seems fairly clear to me, though I agree the values seem rather arbitrary. Here's my understanding as an amateur: esp_wifi_set_max_tx_power takes a int8_t as a parameter indicating the desired power level. So acceptable...

At the same link you provided there's also esp_wifi_get_max_tx_power(int8_t *power) which seems to complement the function to set it.
https://demo-dijiudu.readthedocs.io/en/ ... erP6int8_t

So I think 78 is your answer.

You should only be flagging it in the interrupt routine (eg. _goToSleep=true;). That's all.

Then handle it in the loop: if(_goToSleep)...

I'd suggest an external pulldown too.

I was playing with the pulse counter module a little while ago for something different. Upload this and see if it's useful for you: #include "driver/pcnt.h" #define ENCODER_PIN_A GPIO_NUM_13 #define ENCODER_PIN_B GPIO_NUM_14 #define PULSE_COUNT_UNIT PCNT_UNIT_0 int16_t theCounter = 0; static void in...

ESP_igrr wrote: ↑

Mon Dec 10, 2018 2:54 pm

This is a regression in recent versions of ESP-IDF. We are working on a fix. For now you can add a call 'adc_power_off();' (from driver/adc.h) right before entering deep sleep.

Tested and confirmed! Thankyou!

I have a ULP program that reads a rotary encoder and wakes the cores when input is detected, then WiFi is connected to do work, then back into Deep Sleep. While testing low power consumption, I observed this (where 'WiFi.begin?' = Whether or not WiFi.begin() was called before entering Deep Sleep; 'U...

Well what happens if you send the exact same request composed with your browser or Fiddler or similar? That's the first thing I would try, then you'll know if the issue is with your ESP32 code or the server.

Can you confirm that you ran the i2c scanner on the ESP32? And it found the accelerometer? It's unlikely to be a hardware issue if that is working fine. In that case, I would be double-checking the address. I suspect it's expecting 0x1D but your accelerometer is at 0x1C (or vice versa). Run the scan...

Select the correct board and it will be fine. The WROVER boards have a flag in boards.txt, "-DBOARD_HAS_PSRAM".

There's sample code that does exactly this:

https://gist.github.com/igrr/54f7fbe051 ... d7fbecfeab