On Sat, May 9, 2020 at 09:50 AM, jjpurdum wrote:
The ESP32 is quirky and has pin placements that vary among manufacturers making it difficult to use.
Yes, I agree that this is a issue. One big problem is the ESP32 relies in external memory chips and it is easy to accidentally use one of the pins required for the external memory interface as an I/O pin. Although some ESP32 boards designer were smart enough not to route those pins as user I/O pins. But not all.?
What I really like about the ESP32 is it has enough resources to run a web server and provide an embedded UI that I can access from my smartphone. Additionally, there are libraries that allow you to connect to your ESP32 contraption directly with a "hot spot" style WiFi connection or attach it to your WiFi network, that you can choose to configure from your smartphone once you make the "hot spot" connection.?
Apparently the interrupt response time is rather variable. Likely due to a RTOS running on the chip as it splits time between the WiFi radio and your code. Here is a video that provides some information about how the ESP32 does in real time IOT applications.?
He did imply that the testing he did was done with the primary core of the ESP32 and somehow did not utilize the second core.?
Tom, wb6b
