Hello Toby In my current project I had some problems with BT and I found that the way you put the wroom module on your board or what else is close to it has a really big impact on BT performance. Check the esp32_hardware_design_guidelines_en.pdf it has some tips on how to place your board, In my cas...

Hello I have a project where I have to use a 12V power supply to power a wroom module in active mode with BT (not deep-sleep or light sleep), the problem is that my voltage regulator (UTC1117AL 3.3V Dpack) gets really hot. I was able to reduce some current consumption running at 80Mhz, now my module...

Great

Thanks

Hello

I saw in the power management documentation that we can control the clock, but it says that for ESP32 the values are 240/160/80 could I go lower then 80? Like 40Mhz?

Thanks

I would like: Hardware 1- A better ADC (more accurate) in my current project I had to add an external ADC because each esp32 had a different reading for ADC 2- Option to lower power consumption 20mA with BT (no sleep) Software 1- Better documentation more detail / explanation 2- More sample code wit...

Hi roland

I found the problem, I am using version 3.2 of IDF but was looking at the docs for version 4.0.

The docs for version 3.2 is correct

Thanks

I think that idf.py monitor --print-filter is wrong in the DOCs but I found

idf_monitor.py --port /dev/cu.SLAB_USBtoUART --print_filter "*:N" ./build/myproject.elf

That works

[]s

Hello I am trying to filter the output of monitor. I found in the documentation "IDF monitor can be invoked as idf.py monitor --print-filter="xyz", where --print-filter is the parameter for output filtering." But when I run it I got "idf.py: error: unrecognized arguments: --print-filter='*:N'" Witho...

Hello vangalvin I think you need to specify how much data you will produce and how often you will collect it. If low power is a need, having the the unit wake every second to check for a wifi that will be close once per week is a waste of power. I am working in a project where I use a beacon to wake...

Even with calibration I could not make sense from the values, each board has a different result