- Why do we need this AsyncUDP_ESP32_Ethernet library
- Changelog
- Prerequisites
- Installation
- Libraries' Patches
- HOWTO Fix
Multiple Definitions
Linker Error - HOWTO Use analogRead() with ESP32 running WiFi and/or BlueTooth (BT/BLE)
- HOWTO Setting up the Async UDP Client
- How to connect W5500, W6100 or ENC28J60 to ESP32
- Examples
- Example AsyncUdpNTPClient
- Debug Terminal Output Samples
- Troubleshooting
- Issues
- TO DO
- DONE
- Contributions and Thanks
- Contributing
- License
- Copyright
Why do we need this AsyncUDP_ESP32_Ethernet library
This AsyncUDP_ESP32_Ethernet library is a fully asynchronous UDP library, designed for a trouble-free, multi-connection network environment, for ESP32
boards using LwIP
W5500, W6100 or ENC28J60 Ethernet. The library is easy to use and includes support for Unicast
, Broadcast
and Multicast
environments.
This library is based on, modified from:
to apply the better and faster asynchronous feature of the powerful AsyncUDP into ESP32
boards using LwIP
W5500, W6100 or ENC28J60 Ethernet.
- Using asynchronous network means that you can handle more than one connection at the same time
- You are called once the request is ready and parsed
- When you send the response, you are immediately ready to handle other connections while the server is taking care of sending the response in the background
- Speed is OMG
- After connecting to a UDP server as an Async Client, you are immediately ready to handle other connections while the Client is taking care of receiving the UDP responding packets in the background.
- You are not required to check in a tight
loop()
for the arrival of the UDP responding packets to process them.
- ESP32-based boards using
LwIP
W5500, W6100 or ENC28J60 Ethernet
FULL_DUPLEX, 100Mbps
FULL_DUPLEX, 100Mbps
FULL_DUPLEX, 10Mbps
Arduino IDE 1.8.19+
for ArduinoESP32 Core 2.0.6+
for ESP32-based boards.WebServer_ESP32_W5500 library 1.5.2+
. To install, checkWebServer_ESP32_W6100 library 1.5.2+
. To install, checkWebServer_ESP32_ENC library 1.5.1+
. To install, check
The suggested way to install is to:
The best way is to use Arduino Library Manager
. Search for AsyncUDP_ESP32_Ethernet
, then select / install the latest version. You can also use this link for more detailed instructions.
- Navigate to AsyncUDP_ESP32_Ethernet page.
- Download the latest release
AsyncUDP_ESP32_Ethernet-main.zip
. - Extract the zip file to
AsyncUDP_ESP32_Ethernet-main
directory - Copy the whole
AsyncUDP_ESP32_Ethernet-main
folder to Arduino libraries' directory such as~/Arduino/libraries/
.
- Install VS Code
- Install PlatformIO
- Install AsyncUDP_ESP32_Ethernet library by using Library Manager. Search for AsyncUDP_ESP32_Ethernet in Platform.io Author's Libraries
- Use included platformio.ini file from examples to ensure that all dependent libraries will installed automatically. Please visit documentation for the other options and examples at Project Configuration File
To fix ESP32 compile error
, just copy the following file into the ESP32
cores/esp32 directory (e.g. ./arduino-1.8.19/hardware/espressif/cores/esp32) to overwrite the old file:
The current library implementation, using xyz-Impl.h
instead of standard xyz.cpp
, possibly creates certain Multiple Definitions
Linker error in certain use cases.
You can include this .hpp
file
// Can be included as many times as necessary, without `Multiple Definitions` Linker Error
#include "AsyncUDP_ESP32_Ethernet.hpp" //https://github.com/khoih-prog/AsyncUDP_ESP32_Ethernet
in many files. But be sure to use the following .h
file in just 1 .h
, .cpp
or .ino
file, which must not be included in any other file, to avoid Multiple Definitions
Linker Error
// To be included only in main(), .ino with setup() to avoid `Multiple Definitions` Linker Error
#include "AsyncUDP_ESP32_Ethernet.h" //https://github.com/khoih-prog/AsyncUDP_ESP32_Ethernet
Check the new multiFileProject example for a HOWTO
demo.
Please have a look at ESP_WiFiManager Issue 39: Not able to read analog port when using the autoconnect example to have more detailed description and solution of the issue.
ADC1
controlsADC
function for pins GPIO32-GPIO39ADC2
controlsADC
function for pins GPIO0, 2, 4, 12-15, 25-27
Look in file adc_common.c
In ADC2, there're two locks used for different cases:
lock shared with app and Wi-Fi: ESP32: When Wi-Fi using the ADC2, we assume it will never stop, so app checks the lock and returns immediately if failed. ESP32S2: The controller's control over the ADC is determined by the arbiter. There is no need to control by lock.
lock shared between tasks: when several tasks sharing the ADC2, we want to guarantee all the requests will be handled. Since conversions are short (about 31us), app returns the lock very soon, we use a spinlock to stand there waiting to do conversions one by one.
adc2_spinlock should be acquired first, then adc2_wifi_lock or rtc_spinlock.
- In order to use
ADC2
for other functions, we have to acquire complicated firmware locks and very difficult to do - So, it's not advisable to use
ADC2
with WiFi/BlueTooth (BT/BLE). - Use
ADC1
, and pins GPIO32-GPIO39 - If somehow it's a must to use those pins serviced by
ADC2
(GPIO0, 2, 4, 12, 13, 14, 15, 25, 26 and 27), use the fix mentioned at the end of ESP_WiFiManager Issue 39: Not able to read analog port when using the autoconnect example to work with ESP32 WiFi/BlueTooth (BT/BLE).
You can change the INT
pin to another one. Default is GPIO4
// Must connect INT to GPIOxx or not working
#define INT_GPIO 4
FULL_DUPLEX, 100Mbps
FULL_DUPLEX, 100Mbps
FULL_DUPLEX, 10Mbps
W5500, W6100 or ENC28J60 | <---> | ESP32 |
---|---|---|
MOSI | <---> | GPIO23 |
MISO | <---> | GPIO19 |
SCK | <---> | GPIO18 |
CS/SS | <---> | GPIO5 |
INT | <---> | GPIO4 |
RST | <---> | RST |
GND | <---> | GND |
3.3V | <---> | 3.3V |
- AsyncUDPClient
- AsyncUdpNTPClient
- AsyncUdpSendReceive
- AsyncUDPServer
- AsyncUDPMulticastServer
- multiFileProject
Example AsyncUdpNTPClient
AsyncUDP_ESP32_Ethernet/examples/AsyncUdpNTPClient/AsyncUdpNTPClient.ino
Lines 11 to 358 in c63051f
This is terminal debug output when running AsyncUdpNTPClient on ESP32_W6100 (ESP32_DEV + W6100). It connects to It connects to NTP Server 0.ca.pool.ntp.org
(IP=208.81.1.244), using AsyncUDP_ESP32_Ethernet
library, and requests NTP time every 60s. The packet is then received and processed asynchronously to print current UTC/GMT time.
Start AsyncUdpNTPClient on ESP32_DEV with ESP32_W6100
WebServer_ESP32_W6100 v1.5.2 for core v2.0.0+
AsyncUDP_ESP32_Ethernet v2.1.0 for core v2.0.0+
[UDP] Default SPI pinout:
[UDP] SPI_HOST: 2
[UDP] MOSI: 23
[UDP] MISO: 19
[UDP] SCK: 18
[UDP] CS: 5
[UDP] INT: 4
[UDP] SPI Clock (MHz): 25
[UDP] =========================
ETH Started
ETH Connected
ETH MAC: 0C:B8:15:D8:01:D7, IPv4: 192.168.2.34
FULL_DUPLEX, 100Mbps
AsyncUdpNTPClient started @ IP address: 192.168.2.34
UDP connected
============= createNTPpacket =============
Received UDP Packet Type: Unicast
From: 208.81.1.244:123, To: 192.168.2.34:55314, Length: 48
Seconds since Jan 1 1900 = 3882392659
Epoch/Unix time = 1673403859
The UTC/GMT time is Wed 2023-01-11 02:24:19 GMT
This is terminal debug output when running AsyncUDPSendReceive on ESP32_W6100 (ESP32_DEV + W6100). It connects to NTP Server 0.ca.pool.ntp.org
(IP=208.81.1.244) using AsyncUDP_ESP32_Ethernet
library, and requests NTP time every 60s. The packet is received and processed asynchronously to print current UTC/GMT
time. The ACK packet is then sent to give acknowledge to the NTP server
Start AsyncUDPSendReceive on ESP32_DEV with ESP32_W6100
WebServer_ESP32_W6100 v1.5.2 for core v2.0.0+
AsyncUDP_ESP32_Ethernet v2.1.0 for core v2.0.0+
[UDP] Default SPI pinout:
[UDP] SPI_HOST: 2
[UDP] MOSI: 23
[UDP] MISO: 19
[UDP] SCK: 18
[UDP] CS: 5
[UDP] INT: 4
[UDP] SPI Clock (MHz): 25
[UDP] =========================
ETH Started
ETH Connected
ETH MAC: 0C:B8:15:D8:01:D7, IPv4: 192.168.2.34
FULL_DUPLEX, 100Mbps
AsyncUDPSendReceive started @ IP address: 192.168.2.34
Starting connection to server...
UDP connected
============= createNTPpacket =============
Received UDP Packet Type: Unicast
From: 208.81.1.244:123, To: 192.168.2.34:62164, Length: 48
Seconds since Jan 1 1900 = 3882392738
Epoch/Unix time = 1673403938
The UTC/GMT time is Wed 2023-01-11 02:25:38 GMT
============= sendACKPacket =============
============= createNTPpacket =============
Received UDP Packet Type: Unicast
From: 208.81.1.244:123, To: 192.168.2.34:62164, Length: 48
Seconds since Jan 1 1900 = 3882392797
Epoch/Unix time = 1673403997
The UTC/GMT time is Wed 2023-01-11 02:26:37 GMT
============= sendACKPacket =============
This is terminal debug output when running AsyncUdpNTPClient on ESP32_W5500 (ESP32_DEV + W5500). It connects to NTP Server using AsyncUDP_ESP32_Ethernet
library, and requests NTP time every 60s. The packet is then received and processed asynchronously to print current UTC/GMT time.
Start AsyncUdpNTPClient on ESP32_DEV with ESP32_W5500
WebServer_ESP32_W5500 v1.5.2 for core v2.0.0+
AsyncUDP_ESP32_Ethernet v2.1.0 for core v2.0.0+
[UDP] Default SPI pinout:
[UDP] SPI_HOST: 2
[UDP] MOSI: 23
[UDP] MISO: 19
[UDP] SCK: 18
[UDP] CS: 5
[UDP] INT: 4
[UDP] SPI Clock (MHz): 25
[UDP] =========================
ETH Started
ETH Connected
ETH MAC: 0C:B8:15:D8:01:D7, IPv4: 192.168.2.34
FULL_DUPLEX, 100Mbps
AsyncUDPSendReceive started @ IP address: 192.168.2.34
UDP connected
============= createNTPpacket =============
Received UDP Packet Type: Unicast
From: 208.81.1.244:123, To: 192.168.2.34:62164, Length: 48
Seconds since Jan 1 1900 = 3882392857
Epoch/Unix time = 1673404057
The UTC/GMT time is Wed 2023-01-11 02:27:37 GMT
This is terminal debug output when running AsyncUDPSendReceive on ESP32_ENC28J60 (ESP32_DEV + ENC28J60). It connects to NTP Server 0.ca.pool.ntp.org
(IP=208.81.1.244) using AsyncUDP_ESP32_Ethernet
library, and requests NTP time every 60s. The packet is received and processed asynchronously to print current UTC/GMT
time. The ACK packet is then sent to give acknowledge to the NTP server
Start AsyncUDPSendReceive on ESP32_DEV with ESP32_ENC28J60
WebServer_ESP32_ENC v1.5.1 for core v2.0.0+
AsyncUDP_ESP32_Ethernet v2.1.0 for core v2.0.0+
[UDP] Default SPI pinout:
[UDP] SPI_HOST: 2
[UDP] MOSI: 23
[UDP] MISO: 19
[UDP] SCK: 18
[UDP] CS: 5
[UDP] INT: 4
[UDP] SPI Clock (MHz): 25
[UDP] =========================
ETH Started
ETH Connected
ETH MAC: 0C:B8:15:D8:01:D7, IPv4: 192.168.2.34
FULL_DUPLEX, 10Mbps
AsyncUDPSendReceive started @ IP address: 192.168.2.34
Starting connection to server...
UDP connected
============= createNTPpacket =============
Received UDP Packet Type: Unicast
From: 208.81.1.244:123, To: 192.168.2.34:62164, Length: 48
Seconds since Jan 1 1900 = 3882392797
Epoch/Unix time = 1673403997
The UTC/GMT time is Wed 2023-01-11 02:26:37 GMT
============= sendACKPacket =============
Debug is enabled by default on Serial. To disable, use level 0
#define ASYNC_UDP_ESP32_ETHERNET_DEBUG_PORT Serial
// Use from 0 to 4. Higher number, more debugging messages and memory usage.
#define _ASYNC_UDP_ESP32_ETHERNET_LOGLEVEL_ 1
You can also change the debugging level from 0 to 4
#define ASYNC_UDP_ESP32_ETHERNET_DEBUG_PORT Serial
// Use from 0 to 4. Higher number, more debugging messages and memory usage.
#define _ASYNC_UDP_ESP32_ETHERNET_LOGLEVEL_ 4
If you get compilation errors, more often than not, you may need to install a newer version of Arduino IDE, the Arduino ESP32
core or depending libraries.
Sometimes, the library will only work if you update the ESP32
core to the latest version because I am always using the latest cores /libraries.
Submit issues to: AsyncUDP_ESP32_Ethernet issues
- Fix bug. Add enhancement
- Add support to more
LwIP Ethernet
shields, such as W5100, W5100S, etc.
- Initial port to
ESP32
-based boards usingLwIP W5500, W6100 or ENC28J60 Ethernet
- Use
allman astyle
and addutils
. Restyle the library
- Based on and modified from Hristo Gochkov's AsyncUDP. Many thanks to Hristo Gochkov for great AsyncUDP Library
⭐️⭐️ Hristo Gochkov |
If you want to contribute to this project:
- Report bugs and errors
- Ask for enhancements
- Create issues and pull requests
- Tell other people about this library
- The library is licensed under GPLv3
Copyright (c) 2018- Hristo Gochkov
Copyright (c) 2023- Khoi Hoang