ESP32TimerInterrupt Library

<a href="https://www.buymeacoffee.com/khoihprog6" title="Donate to my libraries using BuyMeACoffee"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png" alt="Donate to my libraries using BuyMeACoffee" style="height: 50px !important;width: 181px !important;" ></a> <a href="https://www.buymeacoffee.com/khoihprog6" title="Donate to my libraries using BuyMeACoffee"><img src="https://img.shields.io/badge/buy%20me%20a%20coffee-donate-orange.svg?logo=buy-me-a-coffee&logoColor=FFDD00" style="height: 20px !important;width: 200px !important;" ></a>

---

---

Table of Contents

• Important Breaking Change from v2.0.0
• Why do we need this ESP32TimerInterrupt library
  • Features
  • Why using ISR-based Hardware Timer Interrupt is better
  • Currently supported Boards
  • Important Notes about ISR
• Changelog
• Prerequisites
• Installation
  • Use Arduino Library Manager
  • Manual Install
  • VS Code & PlatformIO
• Note for Platform IO using ESP32 LittleFS
• HOWTO Fix Multiple Definitions Linker Error
• HOWTO Use analogRead() with ESP32 running WiFi and/or BlueTooth (BT/BLE)
  • 1. ESP32 has 2 ADCs, named ADC1 and ADC2
  • 2. ESP32 ADCs functions
  • 3. ESP32 WiFi uses ADC2 for WiFi functions
• More useful Information
• How to use
• Examples
  • 1. Argument_None
  • 2. Change_Interval
  • 3. ISR_16_Timers_Array
  • 4. ISR_16_Timers_Array_Complex
  • 5. RPM_Measure
  • 6. SwitchDebounce
  • 7. TimerInterruptTest
  • 8. multiFileProject More complex
  • 9. ISR_16_Timers_Array_OneShot New
  • 10. ISR_16_Timers_Array_Complex_OneShot New
• Example ISR_16_Timers_Array_Complex
• Debug Terminal Output Samples
  • 1. TimerInterruptTest on ESP32C3_DEV
  • 2. Change_Interval on ESP32C3_DEV
  • 3. Argument_None on ESP32S3_DEV
  • 4. ISR_16_Timers_Array_Complex on ESP32S3_DEV
  • 5. ISR_16_Timers_Array on ESP32S3_DEV
  • 6. ISR_16_Timers_Array_Complex on ESP32C3_DEV
• Debug
• Troubleshooting
• Issues
• TO DO
• DONE
• Contributions and Thanks
• Contributing
• License
• Copyright

---

---

Important Breaking Change from v2.0.0

Please have a look at HOWTO Fix Multiple Definitions Linker Error

---

---

Why do we need this ESP32TimerInterrupt library

Features

This library enables you to use Interrupt from Hardware Timers on an ESP32-based board.

As Hardware Timers are rare, and very precious assets of any board, this library now enables you to use up to 16 ISR-based Timers, while consuming only 1 Hardware Timer. Timers' interval is very long (ulong millisecs).

Now with these new 16 ISR-based timers, the maximum interval is practically unlimited (limited only by unsigned long milliseconds) while the accuracy is nearly perfect compared to software timers.

The most important feature is they're ISR-based timers. Therefore, their executions are not blocked by bad-behaving functions / tasks. This important feature is absolutely necessary for mission-critical tasks.

The ISR_Timer_Complex example will demonstrate the nearly perfect accuracy compared to software timers by printing the actual elapsed millisecs of each type of timers.

Being ISR-based timers, their executions are not blocked by bad-behaving functions / tasks, such as connecting to WiFi, Internet and Blynk services. You can also have many (up to 16) timers to use.

This non-being-blocked important feature is absolutely necessary for mission-critical tasks.

You'll see blynkTimer Software is blocked while system is connecting to WiFi / Internet / Blynk, as well as by blocking task in loop(), using delay() function as an example. The elapsed time then is very unaccurate

Why using ISR-based Hardware Timer Interrupt is better

Imagine you have a system with a mission-critical function, measuring water level and control the sump pump or doing something much more important. You normally use a software timer to poll, or even place the function in loop(). But what if another function is blocking the loop() or setup().

So your function might not be executed, and the result would be disastrous.

You'd prefer to have your function called, no matter what happening with other functions (busy loop, bug, etc.).

The correct choice is to use a Hardware Timer with Interrupt to call your function.

These hardware timers, using interrupt, still work even if other functions are blocking. Moreover, they are much more precise (certainly depending on clock frequency accuracy) than other software timers using millis() or micros(). That's necessary if you need to measure some data requiring better accuracy.

Functions using normal software timers, relying on loop() and calling millis(), won't work if the loop() or setup() is blocked by certain operation. For example, certain function is blocking while it's connecting to WiFi or some services.

The catch is your function is now part of an ISR (Interrupt Service Routine), and must be lean / mean, and follow certain rules. More to read on:

HOWTO Attach Interrupt

---

Currently supported Boards

1. ESP32 boards, such as ESP32_DEV, etc.
2. ESP32_S2-based boards, such as ESP32S2_DEV, ESP32_S2 Saola, Adafruit QTPY_ESP32S2, ESP32S2 Native USB, UM FeatherS2 Neo, UM TinyS2, UM RMP, microS2, etc.
3. ESP32_C3-based boards, such as ESP32C3_DEV, LOLIN_C3_MINI, DFROBOT_BEETLE_ESP32_C3, ADAFRUIT_QTPY_ESP32C3, AirM2M_CORE_ESP32C3, XIAO_ESP32C3, etc. New
4. ESP32_S3-based boards, such as ESP32S3_DEV, ESP32_S3_BOX, UM TINYS3, UM PROS3, UM FEATHERS3, FEATHER_ESP32S3_NOPSRAM, QTPY_ESP32S3_NOPSRAM, etc. New

---

Important Notes about ISR

1. Inside the attached function, delay() won’t work and the value returned by millis() will not increment. Serial data received while in the function may be lost. You should declare as volatile any variables that you modify within the attached function.

2. Typically global variables are used to pass data between an ISR and the main program. To make sure variables shared between an ISR and the main program are updated correctly, declare them as volatile.

---

---

Prerequisites

1. Arduino IDE 1.8.19+ for Arduino.
2. ESP32 Core 2.0.5+ for ESP32-based boards. .
3. SimpleTimer library to use with some examples.

---

---

Installation

Use Arduino Library Manager

The best and easiest way is to use Arduino Library Manager. Search for ESP32TimerInterrupt, then select / install the latest version. You can also use this link for more detailed instructions.

---

Manual Install

Another way to install is to:

1. Navigate to ESP32TimerInterrupt page.
2. Download the latest release ESP32TimerInterrupt-master.zip.
3. Extract the zip file to ESP32TimerInterrupt-master directory
4. Copy whole ESP32TimerInterrupt-master folder to Arduino libraries' directory such as ~/Arduino/libraries/.

---

VS Code & PlatformIO

1. Install [V