- Important Change from v3.5.0
- Why do we need this UPnP_Generic library
- Changelog
- Prerequisites
- Installation
- Packages' Patches
- 1. For Adafruit nRF52840 and nRF52832 boards
- 2. For Teensy boards
- 3. For Arduino SAM DUE boards
- 4. For Arduino SAMD boards
- 5. For Adafruit SAMD boards
- 6. For Seeeduino SAMD boards
- 7. For STM32 boards
- 8. For RP2040-based boards using Earle Philhower arduino-pico core
- 9. For Portenta_H7 boards using Arduino IDE in Linux
- 10. For RTL8720DN boards using AmebaD core
- 11. For SAMD21 and SAMD51 boards using ArduinoCore-fab-sam core
- 12. For Seeeduino RP2040 boards
- Libraries' Patches
- HOWTO Use analogRead() with ESP32 running WiFi and/or BlueTooth (BT/BLE)
- Configuration Notes
- 1. How to use built-in WiFi in ESP8266/ESP32
- 2. How to select which built-in Ethernet or shield to use
- 3. How to select which built-in WiFi or shield to use
- Important
- 4. How to select another CS/SS pin to use
- 5. How to use W5x00 with ESP8266
- 6. How to increase W5x00 TX/RX buffer
- 7. How to use SPI2 for ESP32 using W5x00 and Ethernet_Generic Library
- 8. How to use SPI1 for RP2040 using W5x00 and Ethernet_Generic Library
- HOWTO Usage
- Examples
- Example nRF52_SimpleServer
- Debug Terminal Output Samples
- 1. SAMD_SimpleServer on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
- 2. nRF52_SimpleServer on Adafruit NRF52840_FEATHER with W5500 using Ethernet_Generic Library
- 3. nRF52_SimpleServer on Adafruit NRF52840_FEATHER with W5500 using Ethernet_Generic Library
- 4. STM32_SimpleServer on STM32F7 Nucleo-144 NUCLEO_F767ZI with W5500 using Ethernet_Generic Library
- 5. SAMD_SimpleServer on Adafruit SAMD51 ITSYBITSY_M4 with ESP8266_AT shield
- 6. PWM_LEDServer_ESP32 on ESP32_DEV
- 7. RP2040_PWM_LEDServer on MBED NANO_RP2040_CONNECT with WiFiNINA using WiFiNINA_Generic Library
- 8. RP2040_PWM_LEDServer on RASPBERRY_PI_PICO with W5x00 using Ethernet_Generic Library
- 9. RP2040_SimpleServer on MBED RASPBERRY_PI_PICO with W5x00 using Ethernet_Generic Library
- 10. PWM_LEDServer_ESP32 on ESP32S2_DEV
- 11. PWM_LEDServer_ESP8266 on ESP8266_NODEMCU_ESP12E
- 12. SimpleServer_WT32_ETH01 on WT32-ETH01 with ETH_PHY_LAN8720
- 13. Portenta_H7_SimpleServer on PORTENTA_H7_M7 using Portenta_H7 WiFi
- 14. Portenta_H7_SimpleServer on PORTENTA_H7_M7 using Ethernet
- 15. T41_QNEthernet_SimpleServer on TEENSY 4.1
- Debug
- Troubleshooting
- Issues
- TO DO
- DONE
- Contributions and Thanks
- Contributing
- License
- Copyright
Please have a look at HOWTO Fix Multiple Definitions Linker Error
Why do we need this UPnP_Generic library
Many of us are manually port-forwarding in Internet Gateway Device (IGD, Router) in order to provide access to local Web Services from the Internet.
This library provides the easier way to automatically port-forward by using the Simple Service Discovery Protocol (SSDP), running on nRF52, SAMD21/SAMD51, STM32F/L/H/G/WB/MP1, Teensy, ESP8266/ESP32, WT32_ETH01, Portenta_H7, etc. using ESP WiFi, WiFiNINA, Ethernet W5x00, LAN8720, ESP8266/ESP32 AT-command WiFi supporting UDP Multicast.
The SSDP provides a mechanism whereby network clients, with little or no static configuration, can discover network services. SSDP accomplishes this by providing for multicast discovery support as well as server based notification and discovery routing.
The SSDP is used for advertisement and discovery of network services and presence information. It accomplishes the task without assistance of server-based configuration mechanisms, such as Dynamic Host Configuration Protocol (DHCP) or Domain Name System (DNS), and without special static configuration of a network host. SSDP is the basis of the discovery protocol of Universal Plug and Play (UPnP) and is intended for use in residential or small office environments.
This UPnP_Generic library is created to automatically update your IGDs with the requested port-forward information, using one of the many available boards / shields. See Currently Supported Boards.
The time between checks to update the UPnP Port Mappings is configurable to match your use case, and is set in the examples at 10 minutes. The LEASE_DURATION is also configurable and default to 10hrs (36000s). The Virtual Server Name can also be specified in the sketch and is shown in the IGD, e.g. NRF52-W5X00 or ESP8266-WIFI as in the following picture:
The UPnP_Generic code is very short, can be immersed in your Projects and to be called in the loop() code.
This UPnP_Generic library is based on and modified from Ofek Pearl's TinyUPnP Library to add support to many boards and shields besides ESP32 and ESP8266.
-
ESP8266
-
ESP32
-
AdaFruit Feather nRF52832, nRF52840 Express, BlueFruit Sense, Itsy-Bitsy nRF52840 Express, Metro nRF52840 Express, NINA_B302_ublox, NINA_B112_ublox etc..
-
Arduino SAMD21 (ZERO, MKR, NANO_33_IOT, etc.).
-
Adafruit SAM21 (Itsy-Bitsy M0, Metro M0, Feather M0, Gemma M0, etc.).
-
Adafruit SAM51 (Itsy-Bitsy M4, Metro M4, Grand Central M4, Feather M4 Express, etc.).
-
Seeeduino SAMD21/SAMD51 boards (SEEED_WIO_TERMINAL, SEEED_FEMTO_M0, SEEED_XIAO_M0, Wio_Lite_MG126, WIO_GPS_BOARD, SEEEDUINO_ZERO, SEEEDUINO_LORAWAN, SEEED_GROVE_UI_WIRELESS, etc.)
-
STM32 (Nucleo-144, Nucleo-64, Nucleo-32, Discovery, STM32F1, STM32F3, STM32F4, STM32H7, STM32L0, etc.).
-
STM32F/L/H/G/WB/MP1 (Nucleo-64 L053R8,Nucleo-144, Nucleo-64, Nucleo-32, Discovery, STM32Fx, STM32H7, STM32Lx, STM32Gx, STM32WB, STM32MP1, etc.) having 64K+ Flash program memory.
-
RP2040-based boards, such as Nano RP2040 Connect, using Arduino mbed OS for Nano boards.
-
RP2040-based boards, such as RASPBERRY_PI_PICO, ADAFRUIT_FEATHER_RP2040 and GENERIC_RP2040, using Arduino-mbed RP2040 core or Earle Philhower's arduino-pico core.
-
WT32_ETH01 boards using ESP32-based boards and LAN8720 Ethernet
-
Portenta_H7 using either
Murata WiFiorVision-shield Ethernet -
SAM DUE
-
Teensy (4.1, 4.0, 3.6, 3.5, 3,2, 3.1, 3.0)
-
AVR Mega1280, 2560, ADK.
- ESP8266 built-in WiFi
- ESP32 built-in WiFi
- WiFiNINA using WiFiNINA or WiFiNINA_Generic library.
- ESP8266-AT, ESP32-AT WiFi shields using WiFiEspAT or ESP8266_AT_WebServer library.
- Portenta_H7 built-in Murata WiFi
- W5x00's using
Ethernet_GenericLibrary. - Ethernet2 Library is also supported after applying the fix to add Multicast feature. See Libraries' Patches
- ENC28J60 using EthernetENC and UIPEthernet library are not supported as UDP Multicast is not available by design.
- LAN8742A using STM32Ethernet / STM32 LwIP libraries is not supported as UDP Multicast is not enabled by design, unless you modify the code to add support.
- LAN8720A in WT32-ETH01 using
WebServer_WT32_ETH01. - Teensy 4.1 built-in Ethernet using
NativeEthernetlibrary - Teensy 4.1 built-in Ethernet using
QNEthernetlibrary - Portenta_H7 using Ethernet from Portenta Vision shields
-
ESP32 Core 2.0.2+for ESP32-based boards. -
ESP8266 Core 3.0.2+for ESP8266-based boards.. To use ESP8266 core 2.7.1+ for LittleFS.
-
Arduino AVR core 1.8.5+for Arduino (Use Arduino Board Manager) for AVR boards. -
Arduino SAM DUE core v1.6.12+for SAM DUE ARM Cortex-M3 boards. -
Arduino SAMD core 1.8.13+for SAMD ARM Cortex-M0+ boards. -
Adafruit SAMD core 1.7.10+for SAMD ARM Cortex-M0+ and M4 boards (Nano 33 IoT, etc.). -
Seeeduino SAMD core 1.8.2+for SAMD21/SAMD51 boards (XIAO M0, Wio Terminal, etc.). -
Adafruit nRF52 v1.3.0+for nRF52 boards such as Adafruit NRF52840_FEATHER, NRF52832_FEATHER, NRF52840_FEATHER_SENSE, NRF52840_ITSYBITSY, NRF52840_CIRCUITPLAY, NRF52840_CLUE, NRF52840_METRO, NRF52840_PCA10056, PARTICLE_XENON, NINA_B302_ublox, etc. -
Arduino Core for STM32 v2.2.0+for STM32F/L/H/G/WB/MP1 boards. -
ArduinoCore-mbed mbed_rp2040, mbed_nano, mbed_portenta core 3.0.1+for Arduino (Use Arduino Board Manager) Portenta_H7, RP2040-based boards, such as Nano_RP2040_Connect, RASPBERRY_PI_PICO. -
Earle Philhower's arduino-pico core v1.13.1+for RP2040-based boards such as RASPBERRY_PI_PICO, ADAFRUIT_FEATHER_RP2040 and GENERIC_RP2040, etc. -
Teensy core v1.56+for Teensy (4.1, 4.0, 3.6, 3.5, 3,2, 3.1, 3.0) boards. -
Depending on which Ethernet card you're using:
Ethernet_Generic library v2.0.1+for W5100, W5200 and W5500/WIZ550io/WIZ850io/USR-ES1 with Wiznet W5500 chip.
WiFiNINA_Generic library v1.8.14-3+to use WiFiNINA modules/shields. To install. checkif using WiFiNINA for boards such as Nano 33 IoT, nRF52, Teensy, etc.
WiFiWebServer library v1.7.0+to use WiFi/WiFiNINA modules/shields. To install, checkEthernetWebServer library v2.1.2+to use Ethernet modules/shields on boards other than STM32F/L/H/G/WB/MP1. To install. check.
EthernetWebServer_STM32 library v1.4.0+to use Ethernet modules/shields on STM32F/L/H/G/WB/MP1 boards. To install, check.
ESP8266_AT_WebServer library v1.5.3+to use ESP8266-AT/ESP32-AT WiFi modules/shields. To install, checkDDNS_Generic library v1.6.1+to use examples. To install, checkWebServer_WT32_ETH01 library v1.4.1+to use WT32_ETH01 (ESP32 + LAN8720). To install, check.
QNEthernet Library version v0.14.0+for Teensy 4.1 built-in Ethernet. UDP multicast has been supported. New
The best and easiest way is to use Arduino Library Manager. Search for UPnP_Generic, then select / install the latest version.
You can also use this link
Another way to install is to:
- Navigate to UPnP_Generic page.
- Download the latest release
UPnP_Generic-master.zip. - Extract the zip file to
UPnP_Generic-masterdirectory - Copy whole
UPnP_Generic-master/srcfolder to Arduino libraries' directory such as~/Arduino/libraries/.
- Install VS Code
- Install PlatformIO
- Install UPnP_Generic library by using Library Manager. Search for UPnP_Generic 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 be able to compile, run and automatically detect and display BOARD_NAME on nRF52840/nRF52832 boards, you have to copy the whole nRF52 Packages_Patches directory into Adafruit nRF52 directory (~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0).
Supposing the Adafruit nRF52 version is 1.3.0. These files must be copied into the directory:
~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/platform.txt~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/boards.txt~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/cores/nRF5/Udp.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/cores/nRF5/Print.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/cores/nRF5/Print.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B302_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B302_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B112_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/variants/NINA_B112_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/1.3.0/cores/nRF5/Udp.h
Whenever a new version is installed, remember to copy these files into the new version directory. For example, new version is x.yy.z These files must be copied into the directory:
~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/platform.txt~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/boards.txt~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Udp.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Print.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Print.cpp~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B302_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B302_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B112_ublox/variant.h~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/variants/NINA_B112_ublox/variant.cpp~/.arduino15/packages/adafruit/hardware/nrf52/x.yy.z/cores/nRF5/Udp.h
To be able to compile and run on Teensy boards, you have to copy the files in Packages_Patches for Teensy directory into Teensy hardware directory (./arduino-1.8.19/hardware/teensy/avr/boards.txt).
Supposing the Arduino version is 1.8.19. These files must be copied into the directory:
./arduino-1.8.19/hardware/teensy/avr/boards.txt./arduino-1.8.19/hardware/teensy/avr/cores/teensy/Stream.h./arduino-1.8.19/hardware/teensy/avr/cores/teensy3/Stream.h./arduino-1.8.19/hardware/teensy/avr/cores/teensy4/Stream.h
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz These files must be copied into the directory:
./arduino-x.yy.zz/hardware/teensy/avr/boards.txt./arduino-x.yy.zz/hardware/teensy/avr/cores/teensy/Stream.h./arduino-x.yy.zz/hardware/teensy/avr/cores/teensy3/Stream.h./arduino-x.yy.zz/hardware/teensy/avr/cores/teensy4/Stream.h
To be able to compile and run on SAM DUE boards, you have to copy the whole SAM DUE directory into Arduino sam directory (~/.arduino15/packages/arduino/hardware/sam/1.6.12).
Supposing the Arduino SAM core version is 1.6.12. This file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/sam/1.6.12/platform.txt
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz This file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/sam/x.yy.zz/platform.txt
To be able to compile, run and automatically detect and display BOARD_NAME on Arduino SAMD (Nano-33-IoT, etc) boards, you have to copy the whole Arduino SAMD Packages_Patches directory into Arduino SAMD directory (~/.arduino15/packages/arduino/hardware/samd/1.8.13).
Supposing the Arduino SAMD version is 1.8.13. Now only one file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/samd/1.8.13/platform.txt
Whenever a new version is installed, remember to copy this files into the new version directory. For example, new version is x.yy.zz
This file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/samd/x.yy.zz/platform.txt
Supposing the Arduino SAMD version is 1.8.9. These files must be copied into the directory:
~/.arduino15/packages/arduino/hardware/samd/1.8.9/platform.txt~/.arduino15/packages/arduino/hardware/samd/1.8.9/cores/arduino/Arduino.h
Whenever a new version is installed, remember to copy these files into the new version directory. For example, new version is x.yy.z
These files must be copied into the directory:
~/.arduino15/packages/arduino/hardware/samd/x.yy.z/platform.txt~/.arduino15/packages/arduino/hardware/samd/x.yy.z/cores/arduino/Arduino.h
This is mandatory to fix the notorious Arduino SAMD compiler error. See Improve Arduino compatibility with the STL (min and max macro)
...\arm-none-eabi\include\c++\7.2.1\bits\stl_algobase.h:243:56: error: macro "min" passed 3 arguments, but takes just 2
min(const _Tp& __a, const _Tp& __b, _Compare __comp)
Whenever the above-mentioned compiler error issue is fixed with the new Arduino SAMD release, you don't need to copy the Arduino.h file anymore.
To be able to compile, run and automatically detect and display BOARD_NAME on Adafruit SAMD (Itsy-Bitsy M4, etc) boards, you have to copy the whole Adafruit SAMD Packages_Patches directory into Adafruit samd directory (~/.arduino15/packages/adafruit/hardware/samd/1.7.9).
Supposing the Adafruit SAMD core version is 1.7.9. This file must be copied into the directory:
~/.arduino15/packages/adafruit/hardware/samd/1.7.9/platform.txt~/.arduino15/packages/adafruit/hardware/samd/1.7.9/cores/arduino/Print.h~/.arduino15/packages/adafruit/hardware/samd/1.7.9/cores/arduino/Print.cpp
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz This file must be copied into the directory:
~/.arduino15/packages/adafruit/hardware/samd/x.yy.zz/platform.txt~/.arduino15/packages/adafruit/hardware/samd/x.yy.zz/cores/arduino/Print.h~/.arduino15/packages/adafruit/hardware/samd/x.yy.zz/cores/arduino/Print.cpp
To be able to compile, run and automatically detect and display BOARD_NAME on Seeeduino SAMD (XIAO M0, Wio Terminal, etc) boards, you have to copy the whole Seeeduino SAMD Packages_Patches directory into Seeeduino samd directory (~/.arduino15/packages/Seeeduino/hardware/samd/1.8.2).
Supposing the Seeeduino SAMD core version is 1.8.2. This file must be copied into the directory:
~/.arduino15/packages/Seeeduino/hardware/samd/1.8.2/platform.txt~/.arduino15/packages/Seeeduino/hardware/samd/1.8.2/cores/arduino/Arduino.h~/.arduino15/packages/Seeeduino/hardware/samd/1.8.2/cores/arduino/Print.h~/.arduino15/packages/Seeeduino/hardware/samd/1.8.2/cores/arduino/Print.cpp
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz This file must be copied into the directory:
~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/platform.txt~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/cores/arduino/Arduino.h~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/cores/arduino/Print.h~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/cores/arduino/Print.cpp
To use LAN8720 on some STM32 boards
- Nucleo-144 (F429ZI, NUCLEO_F746NG, NUCLEO_F746ZG, NUCLEO_F756ZG)
- Discovery (DISCO_F746NG)
- STM32F4 boards (BLACK_F407VE, BLACK_F407VG, BLACK_F407ZE, BLACK_F407ZG, BLACK_F407VE_Mini, DIYMORE_F407VGT, FK407M1)
you have to copy the files stm32f4xx_hal_conf_default.h and stm32f7xx_hal_conf_default.h into STM32 stm32 directory (~/.arduino15/packages/STM32/hardware/stm32/2.2.0/system) to overwrite the old files.
Supposing the STM32 stm32 core version is 2.2.0. These files must be copied into the directory:
~/.arduino15/packages/STM32/hardware/stm32/2.2.0/system/STM32F4xx/stm32f4xx_hal_conf_default.hfor STM32F4.~/.arduino15/packages/STM32/hardware/stm32/2.2.0/system/STM32F7xx/stm32f7xx_hal_conf_default.hfor Nucleo-144 STM32F7.
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz, these files must be copied into the corresponding directory:
~/.arduino15/packages/STM32/hardware/stm32/x.yy.zz/system/STM32F4xx/stm32f4xx_hal_conf_default.h- `~/.arduino15/packages/STM32/hardware/stm32/x.yy.zz/system/STM32F7xx/stm32f7xx_hal_conf_default.h
To use Serial1 on some STM32 boards without Serial1 definition (Nucleo-144 NUCLEO_F767ZI, Nucleo-64 NUCLEO_L053R8, etc.) boards, you have to copy the files STM32 variant.h into STM32 stm32 directory (~/.arduino15/packages/STM32/hardware/stm32/2.2.0). You have to modify the files corresponding to your boards, this is just an illustration how to do.
Supposing the STM32 stm32 core version is 2.2.0. These files must be copied into the directory:
~/.arduino15/packages/STM32/hardware/stm32/2.2.0/variants/STM32F7xx/F765Z(G-I)T_F767Z(G-I)T_F777ZIT/NUCLEO_F767ZI/variant.hfor Nucleo-144 NUCLEO_F767ZI.~/.arduino15/packages/STM32/hardware/stm32/2.2.0/variants/STM32L0xx/L052R(6-8)T_L053R(6-8)T_L063R8T/NUCLEO_L053R8/variant.hfor Nucleo-64 NUCLEO_L053R8.
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz, these files must be copied into the corresponding directory:
~/.arduino15/packages/STM32/hardware/stm32/x.yy.zz/variants/STM32F7xx/F765Z(G-I)T_F767Z(G-I)T_F777ZIT/NUCLEO_F767ZI/variant.h~/.arduino15/packages/STM32/hardware/stm32/x.yy.zz/variants/STM32L0xx/L052R(6-8)T_L053R(6-8)T_L063R8T/NUCLEO_L053R8/variant.h
8. For RP2040-based boards using Earle Philhower arduino-pico core
To be able to automatically detect and display BOARD_NAME on RP2040-based boards (RASPBERRY_PI_PICO, ADAFRUIT_FEATHER_RP2040, GENERIC_RP2040, etc) boards, you have to copy the file RP2040 platform.txt into rp2040 directory (~/.arduino15/packages/rp2040/hardware/rp2040/1.4.0).
Supposing the rp2040 core version is 1.4.0. This file must be copied into the directory:
~/.arduino15/packages/rp2040/hardware/rp2040/1.4.0/platform.txt
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz This file must be copied into the directory:
~/.arduino15/packages/rp2040/hardware/rp2040/x.yy.zz/platform.txt
With core after v1.5.0, this step is not necessary anymore thanks to the PR Add -DBOARD_NAME="{build.board}" #136.
Some libraries, such as Adafruit DHT-sensor-library, require the definition of microsecondsToClockCycles(). To be able to compile and run on RP2040-based boards, you have to copy the files in RP2040 Arduino.h into rp2040 directory (~/.arduino15/packages/rp2040/hardware/rp2040/1.4.0).
Supposing the rp2040 core version is 1.4.0. This file must be copied to replace:
~/.arduino15/packages/rp2040/hardware/rp2040/1.4.0/cores/rp2040/Arduino.h
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz This file must be copied to replace:
~/.arduino15/packages/rp2040/hardware/rp2040/x.yy.zz/cores/rp2040/Arduino.h
With core after v1.5.0, this step is not necessary anymore thanks to the PR Add defs for compatibility #142.
To be able to upload firmware to Portenta_H7 using Arduino IDE in Linux (Ubuntu, etc.), you have to copy the file portenta_post_install.sh into mbed_portenta directory (~/.arduino15/packages/arduino/hardware/mbed_portenta/3.0.0/portenta_post_install.sh).
Then run the following command using sudo
$ cd ~/.arduino15/packages/arduino/hardware/mbed_portenta/3.0.0
$ chmod 755 portenta_post_install.sh
$ sudo ./portenta_post_install.sh
This will create the file /etc/udev/rules.d/49-portenta_h7.rules as follows:
# Portenta H7 bootloader mode UDEV rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="2341", ATTRS{idProduct}=="035b", GROUP="plugdev", MODE="0666"
Supposing the ArduinoCore-mbed core version is 3.0.0. Now only one file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/mbed_portenta/3.0.0/portenta_post_install.sh
Whenever a new version is installed, remember to copy this files into the new version directory. For example, new version is x.yy.zz
This file must be copied into the directory:
~/.arduino15/packages/arduino/hardware/mbed_portenta/x.yy.zz/portenta_post_install.sh
To avoid compile error relating to PROGMEM, you have to copy the file Realtek AmebaD core pgmspace.h into Realtek AmebaD directory (~/.arduino15/packages/realtek/hardware/AmebaD/3.1.2/cores/arduino/avr/pgmspace.h).
Supposing the Realtek AmebaD core version is 3.1.2. This file must be copied into the directory:
~/.arduino15/packages/realtek/hardware/AmebaD/3.1.2/cores/arduino/avr/pgmspace.h
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz This file must be copied into the directory:
~/.arduino15/packages/realtek/hardware/AmebaD/x.yy.zz/cores/arduino/avr/pgmspace.h
To avoid compile error relating to SAMD21/SAMD51, you have to copy the file ArduinoCore-fab-sam core pgmspace.h into ArduinoCore-fab-sam samd directory (~/.arduino15/packages/Fab_SAM_Arduino/hardware/samd/1.6.18-alpha2/boards.txt).
Supposing the ArduinoCore-fab-sam samd core version is 1.6.18-alpha2. This file must be copied into the directory:
~/.arduino15/packages/Fab_SAM_Arduino/hardware/samd/1.6.18-alpha2/boards.txt
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz This file must be copied into the directory:
~/.arduino15/packages/Fab_SAM_Arduino/hardware/samd/x.yy.zz/boards.txt
To be able to compile, run and automatically detect and display BOARD_NAME on Seeeduino RP2040 (XIAO RP2040, Wio RP2040 Mini) boards, you have to copy the whole Seeeduino RP2040 Packages_Patches directory into Seeeduino samd directory (~/.arduino15/packages/Seeeduino/hardware/rp2040/2.7.2).
Supposing the Seeeduino SAMD core version is 2.7.2. This file must be copied into the directory:
~/.arduino15/packages/Seeeduino/hardware/rp2040/2.7.2/boards.txt~/.arduino15/packages/Seeeduino/hardware/rp2040/2.7.2/variants/Seeed_XIAO_RP2040/pins_arduino.h
Whenever a new version is installed, remember to copy this file into the new version directory. For example, new version is x.yy.zz This file must be copied into the directory:
~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/boards.txt~/.arduino15/packages/Seeeduino/hardware/samd/x.yy.zz/variants/Seeed_XIAO_RP2040/pins_arduino.h
If your application requires 2K+ HTML page, the current Ethernet library must be modified if you are using W5200/W5500 Ethernet shields. W5100 is not supported for 2K+ buffer. If you use boards requiring different CS/SS pin for W5x00 Ethernet shield, for example ESP32, ESP8266, nRF52, etc., you also have to modify the following libraries to be able to specify the CS/SS pin correctly.
To fix Ethernet library, just copy these following files into the Ethernet library directory to overwrite the old files:
To fix EthernetLarge library, just copy these following files into the EthernetLarge library directory to overwrite the old files:
To fix Ethernet2 library, just copy these following files into the Ethernet2 library directory to overwrite the old files:
To add UDP Multicast support, necessary for the UPnP_Generic library:
- To fix
Ethernet3 library, just copy these following files into theEthernet3 librarydirectory to overwrite the old files:
To be able to compile and run on nRF52 boards with ENC28J60 using UIPEthernet library, you have to copy these following files into the UIPEthernet utility directory to overwrite the old files:
To fix ESP32 compile error, just copy the following file into the ESP32 cores/esp32 directory (e.g. ./arduino-1.8.12/hardware/espressif/cores/esp32) to overwrite the old file:
Check if you need to install the UIPEthernet patch new STM32 core F3/F4 compatibility to avoid errors #include HardwareSPI.h on some STM32 boards (Nucleo-32 F303K8, etc.)
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 use
#include <UPnP_Generic.hpp> //https://github.com/khoih-prog/UPnP_Generic
in many files. But be sure to use the following #include <NTPClient_Generic.h> 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 <UPnP_Generic.h> //https://github.com/khoih-prog/UPnP_Generic
Check examples multiFileProject_Ethernet and multiFileProject_WiFiNINA for a demo how to avoid multiple-definitions linker error for multiple-file project
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 controls ADC function for pins GPIO32-GPIO39
- ADC2 controls ADC 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).
It's taken care automatically.
In examples' defines.h
- Define UPNP_USING_ETHERNET == true and UPNP_USING_WIFI == false
// Select UPNP_USING_WIFI for boards using built-in WiFi, such as Nano-33-IoT
#define UPNP_USING_WIFI false
#define UPNP_USING_ETHERNET true- To use W5x00 Ethernet, for example using Ethernet_Generic library
// Only one if the following to be true
#define USE_UIP_ETHERNET false
#define USE_ETHERNET_PORTENTA_H7 false
#define USE_NATIVE_ETHERNET false
#define USE_QN_ETHERNET false
#define USE_ETHERNET_GENERIC true
#define USE_ETHERNET_ESP8266 false
#define USE_ETHERNET_ENC false
#define USE_CUSTOM_ETHERNET falseIn examples' defines.h
- Define UPNP_USING_WIFI == true and UPNP_USING_ETHERNET == false
// Select UPNP_USING_WIFI for boards using built-in WiFi, such as Nano-33-IoT
#define UPNP_USING_WIFI true
#define UPNP_USING_ETHERNET false- To use WiFiNINA, with WiFiNINA_Generic library => Define USE_WIFI_NINA == true
#define UPNP_USING_ETHERNET false
#define UPNP_USING_WIFI true
// Select one to be true: USE_WIFI_NINA, UPNP_USING_WIFI_AT or USE_WIFI_CUSTOM
#define USE_WIFI_NINA true
// If not USE_WIFI_NINA, you can USE_WIFI_CUSTOM, then include the custom WiFi library here
#define USE_WIFI_CUSTOM false
...
#include <WiFiWebServer.h>- The Ethernet_Shield_W5200, EtherCard, EtherSia libraries are not supported. Don't use unless you know how to modify those libraries.
- Requests to support for any future custom Ethernet library will be ignored. Use at your own risk.
The default CS/SS pin is GPIO4(D2) for ESP8266, GPIO22 for ESP32, 10 for all other boards.
If the default pin is not correct, the easiest way is to change is to use
// To override the default CS/SS pin. Don't use unless you know exactly which pin to use
#define USE_THIS_SS_PIN 10To avoid using the default but not-working Ethernet library of ESP8266, rename the Ethernet.h/cpp to Ethernet_ESP8266.h/cpp to avoid library conflict if you're using the Arduino Ethernet library. The Ethernet2, Ethernet3, EthernetLarge library can be used without conflict.
These pins are tested OK with ESP8266 and W5x00
// For ESP8266
// Pin D0(GPIO16) D1(GPIO5) D2(GPIO4) D3(GPIO0) D4(GPIO2) D8
// Ethernet 0 X X X X 0
// Ethernet2 X X X X X 0
// Ethernet3 X X X X X 0
// EthernetLarge X X X X X 0
// Ethernet_ESP8266 0 0 0 0 0 0
// D2 is safe to used for Ethernet, Ethernet2, Ethernet3, EthernetLarge libs
// Must use library patch for Ethernet, EthernetLarge libraries
//Ethernet.setCsPin (USE_THIS_SS_PIN);
Ethernet.init (USE_THIS_SS_PIN);
- For Ethernet3 library only, use as follows
// Use MAX_SOCK_NUM = 4 for 4K, 2 for 8K, 1 for 16K RX/TX buffer
#ifndef ETHERNET3_MAX_SOCK_NUM
#define ETHERNET3_MAX_SOCK_NUM 4
#endif
Ethernet.setCsPin (USE_THIS_SS_PIN);
Ethernet.init (ETHERNET3_MAX_SOCK_NUM);- For Ethernet_Generic library only, to use
SPI2for ESP32
#define USING_SPI2 true
Pin to use for SPI2
MOSI: 13
MISO: 12
SCK: 14
SS: 5
- For Ethernet_Generic library only, to use
SPI1for RP2040 using arduino-pico core
#define USING_SPI2 true
Pin to use for SPI1
MOSI: 15
MISO: 12
SCK: 14
SS: 13
#include "UPnP.h"
#include <DDNS_Generic.h> // optional
UPnP* uPnP;
...
uPnP = new UPnP(30000); // -1 means blocking, preferably, use a timeout value (ms)
// you may repeat 'addPortMappingConfig' more than once
uPnP->addPortMappingConfig(localIP, LISTEN_PORT, RULE_PROTOCOL_TCP, LEASE_DURATION, FRIENDLY_NAME);
// finally, commit the port mappings to the IGD
int result = uPnP->commitPortMappings();
portMappingAdded = ( (result == PORT_MAP_SUCCESS) || (result == ALREADY_MAPPED) );
// update UPnP port mapping every ms internal
// you can provide an optional method for reconnecting to the WiFi (otherwise leave as NULL)
uPnP->updatePortMappings(600000); // 10 minutes
This is specific for the nRF52_PWM_LEDServer example to set the percentage to control the brightness of an LED:
http://<IP or DDNS>:<LISTEN_PORT>/?percentage=<0..100>
such as
http://192.168.2.132:5990/?percentage=20
or
http://account.duckdns.org:5990/?percentage=30
// print all the port mappings that were configured using 'addPortMappingConfig' in the setup step
uPnP->printPortMappingConfig();
// print all the current port mappings from the IGD
uPnP->printAllPortMappings();
Example nRF52_SimpleServer
1. File nRF52_SimpleServer.ino
2. File defines.h
UPnP_Generic/examples/Generic/Ethernet/nRF52/nRF52_SimpleServer/defines.h
Lines 15 to 199 in 702dd28
Debug terminal output when running example SAMD_SimpleServer on SAMD21 SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
Start SAMD_SimpleServer on SAMD_NANO_33_IOT with WiFiNINA using WiFiNINA_Generic Library
UPnP_Generic v3.5.0
Connecting to HueNet1
IP address: 192.168.2.128
Add Port Forwarding, Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. SAMD-WIFI-ESPAT 192.168.2.134 5990 5990 TCP 22410
10. NRF52-WIFI-ESPAT 192.168.2.101 7052 7052 TCP 22110
11. STM32-WIFI-ESPAT 192.168.2.133 7032 7032 TCP 12315
12. STM32-W5X00 192.168.2.85 6032 6032 TCP 34005
13. NRF52-W5X00 192.168.2.85 5952 5952 TCP 32340
14. STM32-LED-W5X00 192.168.2.85 6033 6033 TCP 34455
15. SAMD-WIFININA 192.168.2.128 5995 5995 TCP 35970
UPnP done
HTTP WiFiNINAWebServer is @ IP : 192.168.2.128, port = 5995
[DDNS] Access whatismyipaddress
Connected
[DDNS] httpCode = 200
HttpClient::responseBody => bodyLength =14
[DDNS] Current Public IP = aaa.bbb.ccc.ddd
[DDNS] response = aaa.bbb.ccc.ddd
Connected
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example nRF52_SimpleServer on Adafruit NRF52840_FEATHER with W5500 & Ethernet_Generic Library
Start nRF52_SimpleServer on NRF52840_FEATHER with W5x00 & Ethernet_Generic Library
UPnP_Generic v3.5.0
Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. SAMD-WIFI-ESPAT 192.168.2.101 5990 5990 TCP 35940
10. NRF52-W5X00 192.168.2.99 5952 5952 TCP 35985
UPnP done
HTTP EthernetWebServer is @ IP : 192.168.2.99
[DDNS] Access whatismyipaddress
[DDNS] httpCode = 200
[DDNS] Current Public IP = aaa.bbb.ccc.ddd
[DDNS] response = aaa.bbb.ccc.ddd
[DDNS] Sending HTTP_GET to duckdns
[DDNS] HTTP_GET = http://www.duckdns.org/update?domains=account.duckdns.org&token=12345678-1234-1234-1234-123456789012&ip=aaa.bbb.ccc.ddd
[DDNS] httpCode = 200
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example nRF52_SimpleServer on Adafruit NRF52840_FEATHER with W5500 using Ethernet_Generic Library
Start nRF52_SimpleServer on NRF52840_FEATHER with W5x00 & Ethernet_Generic Library
UPnP_Generic v3.5.0
_pinCS = 0
W5100 init, using SS_PIN_DEFAULT = 10, new ss_pin = 10, W5100Class::ss_pin = 10
W5100::init: W5500, SSIZE =4096
**[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. SAMD-LED-W5X00 192.168.2.85 5999 5999 TCP 25355
10. SAMD-LED-WIFININA 192.168.2.128 5996 5996 TCP 31330
11. ESP8266-LED-WIFI 192.168.2.81 8267 8267 TCP 32265
12. ESP32-LED-WIFI 192.168.2.82 5933 5933 TCP 33995
13. NRF52-LED-W5X00 192.168.2.88 5953 5953 TCP 34230
14. SAMD-W5X00 192.168.2.84 5990 5990 TCP 35450
15. nRF52-W5X00 192.168.2.93 5991 5991 TCP 35970
UPnP done
HTTP EthernetWebServer is @ IP : 192.168.2.84
[DDNS] Access whatismyipaddress
[DDNS] httpCode = 200
[DDNS] Current Public IP = aaa.bbb.ccc.ddd
[DDNS] response = aaa.bbb.ccc.ddd
[DDNS] Sending HTTP_GET to duckdns
[DDNS] HTTP_GET = http://www.duckdns.org/update?domains=account.duckdns.org&token=12345678-1234-1234-1234-123456789012&ip=aaa.bbb.ccc.ddd
[DDNS] httpCode = 200
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
and screenshot for nRF52840 NINA_B302_ublox with W5500 & Ethernet_Generic Library
Debug terminal output when running example STM32_SimpleServer on STM32F7 Nucleo-144 NUCLEO_F767ZI with W5500 using Ethernet_Generic Library
Start STM32_SimpleServer on NUCLEO_F767ZI with W5x00 & Ethernet_Generic Library
UPnP_Generic v3.5.0
Add Port Forwarding, Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. SAMD-LED-WIFI-ESPAT 192.168.2.134 5991 5991 TCP 30045
10. SAMD-WIFI-ESPAT 192.168.2.134 5990 5990 TCP 34800
11. ESP32-LED-WIFI 192.168.2.82 5933 5933 TCP 32295
12. STM32-W5X00 192.168.2.85 6032 6032 TCP 35985
UPnP done
HTTP EthernetWebServer is @ IP : 192.168.2.85, port = 6032
[DDNS] Access whatismyipaddress
[DDNS] httpCode = 200
[DDNS] Current Public IP = 216.154.52.212
[DDNS] response = 216.154.52.212
[DDNS] Sending HTTP_GET to duckdns
[DDNS] HTTP_GET = http://www.duckdns.org/update?domains=account.duckdns.org&token=12345678-1234-1234-1234-123456789012&ip=216.154.52.212
[DDNS] httpCode = 200
DDNSGeneric - IP Change Detected: 216.154.52.212
[DDNS] Updated IP = 216.154.52.212
Debug terminal output when running example SAMD_SimpleServer on Adafruit SAMD51 ITSYBITSY_M4 with ESP8266_AT shield using ESP8266_AT_WebServer Library
Start SAMD_SimpleServer on ITSYBITSY_M4 with ESP8266_AT shield
UPnP_Generic v3.5.0
WiFi shield init done
Connected to HueNet1
IP address: 192.168.2.134
Add Port Forwarding, Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. ESP8266-WIFI 192.168.2.81 8266 8266 TCP 18695
10. ESP32 192.168.2.82 5932 5932 TCP 23755
11. SAMD-LED-WIFININA 192.168.2.128 5996 5996 TCP 29355
12. ESP32-LED-WIFI 192.168.2.82 5933 5933 TCP 31275
13. NRF52-LED-W5X00 192.168.2.88 5953 5953 TCP 32205
14. SAMD-W5X00 192.168.2.84 5990 5990 TCP 33075
15. SAMD-LED-W5X00 192.168.2.93 5991 5991 TCP 33645
16. SAMD-WIFI 192.168.2.128 5995 5995 TCP 35860
17. SAMD-WIFI-ESPAT 192.168.2.134 5990 5990 TCP 35985
UPnP done
HTTP EthernetWebServer is @ IP : 192.168.2.134, port = 5990
[DDNS] Access whatismyipaddress
[DDNS] httpCode = 200
[DDNS] Current Public IP = aaa.bbb.ccc.ddd
[DDNS] response = aaa.bbb.ccc.ddd
[DDNS] Sending HTTP_GET to duckdns
[DDNS] HTTP_GET = http://www.duckdns.org/update?domains=account.duckdns.org&token=12345678-1234-1234-1234-123456789012&ip=aaa.bbb.ccc.ddd
[DDNS] httpCode = 200
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example PWM_LEDServer_ESP32 on ESP32_DEV
Start PWM_LEDServer_ESP32 on ESP32_DEV
UPnP_Generic v3.5.0
Connecting to HueNet1
..
IP address: 192.168.2.82
Add Port Forwarding, Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. ESP8266-WIFI 192.168.2.81 8266 8266 TCP 8895
10. ESP32 192.168.2.82 5932 5932 TCP 27705
11. SAMD-LED-WIFININA 192.168.2.128 5996 5996 TCP 29955
12. ESP8266-LED-WIFI 192.168.2.82 5933 5933 TCP 31575
13. NRF52-LED-W5X00 192.168.2.88 5953 5953 TCP 32205
14. SAMD-W5X00 192.168.2.84 5990 5990 TCP 33075
15. SAMD-LED-W5X00 192.168.2.93 5991 5991 TCP 33645
16. SAMD-WIFI 192.168.2.128 5995 5995 TCP 35460
17. ESP32_DEV-LED-WIFI 192.168.2.81 8267 8267 TCP 35970
UPnP done
HTTP EthernetWebServer is @ IP : 192.168.2.82, port = 5932
Gateway Address: 192.168.2.1
Network Mask: 255.255.255.0
[DDNS] Current Public IP = aaa.bbb.ccc.ddd
[DDNS] Sending HTTP_GET to duckdns
[DDNS] HTTP_GET = http://www.duckdns.org/update?domains=account.duckdns.org&token=12345678-1234-1234-1234-123456789012&ip=aaa.bbb.ccc.ddd
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example RP2040_PWM_LEDServer on MBED NANO_RP2040_CONNECT with WiFiNINA using WiFiNINA_Generic Library
Start RP2040_PWM_LEDServer on MBED NANO_RP2040_CONNECT with WiFiNINA using WiFiNINA_Generic Library
UPnP_Generic v3.5.0
Connecting to HueNet1
IP address: 192.168.2.153
Add Port Forwarding, Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. RP2040-LED-WIFININA 192.168.2.153 6053 6053 TCP 35985
UPnP done
HTTP WiFiWebServer is @ IP : 192.168.2.153, port = 6053
[DDNS] Access whatismyipaddress
Connected
[DDNS] httpCode = 200
HttpClient::responseBody => bodyLength =14
[DDNS] Current Public IP = aaa.bbb.ccc.ddd
[DDNS] response = aaa.bbb.ccc.ddd
Connected
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example RP2040_PWM_LEDServer on RASPBERRY_PI_PICO with W5x00 using Ethernet_Generic Library
Start RP2040_PWM_LEDServer on RASPBERRY_PI_PICO with W5x00 using Ethernet_Generic Library
UPnP_Generic v3.5.0
Connected! IP address: 192.168.2.117
Add Port Forwarding, Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. RP2040-LED-WIFININA 192.168.2.153 6053 6053 TCP 32580
10. RP2040-WIFININA 192.168.2.153 6052 6052 TCP 32850
11. RP2040-LED-W5X00 192.168.2.117 5953 5953 TCP 35970
UPnP done
HTTP EthernetWebServer is @ IP : 192.168.2.117, port = 5953
Gateway Address: 192.168.2.1
Network Mask: 255.255.255.0
[DDNS] Access whatismyipaddress
Connected
[DDNS] httpCode = 200
HttpClient::responseBody => bodyLength =14
[DDNS] Current Public IP = aaa.bbb.ccc.ddd
[DDNS] response = aaa.bbb.ccc.ddd
Connected
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example RP2040_SimpleServer on MBED RASPBERRY_PI_PICO using W5x00 using Ethernet_Generic Library
Start RP2040_SimpleServer on MBED RASPBERRY_PI_PICO using W5x00 using Ethernet_Generic Library
UPnP_Generic v3.5.0
Connected! IP address: 192.168.2.92
Add Port Forwarding, Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. RP2040-LED-WIFININA 192.168.2.153 6053 6053 TCP 32070
10. RP2040-WIFININA 192.168.2.153 6052 6052 TCP 32340
11. RP2040-LED-W5X00 192.168.2.117 5953 5953 TCP 35460
12. RP2040-W5X00 192.168.2.92 5952 5952 TCP 35985
UPnP done
HTTP EthernetWebServer is @ IP : 192.168.2.92, port = 5952
[DDNS] Access whatismyipaddress
Connected
[DDNS] httpCode = 200
HttpClient::responseBody => bodyLength =14
[DDNS] Current Public IP = aaa.bbb.ccc.ddd
[DDNS] response = aaa.bbb.ccc.ddd
Connected
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example PWM_LEDServer_ESP32 on ESP32S2_DEV
Start PWM_LEDServer_ESP32 on ESP32S2_DEV
UPnP_Generic v3.5.0
Connecting to HueNet1
.......
IP address: 192.168.2.190
Add Port Forwarding, Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. RP2040-LED-WIFININA 192.168.2.153 6053 6053 TCP 11610
10. RP2040-WIFININA 192.168.2.153 6052 6052 TCP 11880
11. RP2040-W5X00 192.168.2.92 5952 5952 TCP 15525
12. RP2040-LED-W5X00 192.168.2.119 5953 5953 TCP 16575
13. ESP32S2_DEV-WIFI 192.168.2.190 5932 5932 TCP 35295
14. ESP32S2_DEV-WIFI 192.168.2.190 5933 5933 TCP 35970
UPnP done
HTTP WiFiWebServer is @ IP : 192.168.2.190, port = 5933
Gateway Address: 192.168.2.1
Network Mask: 255.255.255.0
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example PWM_LEDServer_ESP32 on ESP8266_NODEMCU_ESP12E
Start PWM_LEDServer_ESP8266 on ESP8266_NODEMCU_ESP12E
UPnP_Generic v3.5.0
Connecting to HueNet1
...........
IP address: 192.168.2.135
Add Port Forwarding, Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. RP2040-LED-WIFININA 192.168.2.153 6053 6053 TCP 11310
10. RP2040-WIFININA 192.168.2.153 6052 6052 TCP 11580
11. RP2040-W5X00 192.168.2.92 5952 5952 TCP 15225
12. RP2040-LED-W5X00 192.168.2.119 5953 5953 TCP 16275
13. ESP32S2_DEV-WIFI 192.168.2.190 5932 5932 TCP 34995
14. ESP32S2_DEV-WIFI 192.168.2.190 5933 5933 TCP 35670
15. ESP8266_NODEMCU_ESP12E-WIFI 192.168.2.135 8267 8267 TCP 35910
UPnP done
HTTP WiFiWebServer is @ IP : 192.168.2.135, port = 8267
Gateway Address: 192.168.2.1
Network Mask: 255.255.255.0
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example SimpleServer_WT32_ETH01 on WT32-ETH01 with ETH_PHY_LAN8720
Start SimpleServer_WT32_ETH01 on WT32-ETH01 with ETH_PHY_LAN8720
WebServer_WT32_ETH01 v1.4.1
DDNS_Generic v1.6.1
UPnP_Generic v3.5.0
ETH MAC: A8:03:2A:A1:61:73, IPv4: 192.168.2.232
FULL_DUPLEX, 100Mbps
IP address: 192.168.2.232
[UPnP] UDP_TX_PACKET_MAX_SIZE= 1000
[UPnP] UDP_TX_RESPONSE_MAX_SIZE= 8192
[UPnP] newUpnpRule= 0.0.0.0
Add Port Forwarding, Try # 1
[UPnP] Testing WT32_ETH01 Ethernet connection for IP : 192.168.2.232
==> GOOD
[UPnP] Internet connection GOOD
[UPnP] isGatewayInfoValid : 0.0.0.0 , port : 0
[UPnP] Path : , actionPort : 0
[UPnP] actionPath : , serviceTypeName :
[UPnP] Gateway info not valid
[UPnP] GW IP = 192.168.2.1
[UPnP] Sending M-SEARCH to : 239.255.255.250 , Port : 1900
[UPnP] Received packet, size = 331 , IP = 192.168.2.1
[UPnP] Port = 1900
[UPnP] IGD found
[UPnP] IGD location found : http://192.168.2.1:5431/dyndev/uuid:2166898a-7de8-40ed-a1e1-b29a1d140d04
[UPnP] 192.168.2.1
[UPnP] 5431
[UPnP] /dyndev/uuid:2166898a-7de8-40ed-a1e1-b29a1d140d04
[UPnP] Connecting to IGD with host : 192.168.2.1 , port : 5431
[UPnP] Connected to IGD
[UPnP] called getIGDEventURLs
[UPnP] deviceInfo->actionPath : , deviceInfo->path : /dyndev/uuid:2166898a-7de8-40ed-a1e1-b29a1d140d04
[UPnP] URLBase tag found : http://192.168.2.1:5431/
[UPnP] Translated to base host : 192.168.2.1 and base port : 5431
[UPnP] urn:schemas-upnp-org:service:WANPPPConnection:1 service found!
[UPnP] controlURL tag found! Setting actionPath to : /uuid:a4781538-557f-46eb-91f0-c898f3a661d5/WANPPPConnection:1
[UPnP] Port : 5431 , actionPort : 5431
[UPnP] isGatewayInfoValid : 192.168.2.1 , port : 5431
[UPnP] Path : /dyndev/uuid:2166898a-7de8-40ed-a1e1-b29a1d140d04 , actionPort : 5431
[UPnP] actionPath : /uuid:a4781538-557f-46eb-91f0-c898f3a661d5/WANPPPConnection:1 , serviceTypeName : urn:schemas-upnp-org:service:WANPPPConnection:1
[UPnP] Gateway info valid
[UPnP] Verify port mapping for rule : ESP32_DEV-WT32_ETH01
[UPnP] Apply action : GetSpecificPortMappingEntry on port mapping : ESP32_DEV-WT32_ETH01
[UPnP] Connecting to IGD with host : 192.168.2.1 , port : 5431
[UPnP] Connected to IGD
[UPnP] Host: 192.168.2.1:5431
[UPnP] Port mapping found in IGD
[UPnP] All port mappings found in IGD, doing nothing
[UPnP] isGatewayInfoValid : 192.168.2.1 , port : 5431
[UPnP] Path : /dyndev/uuid:2166898a-7de8-40ed-a1e1-b29a1d140d04 , actionPort : 5431
[UPnP] actionPath : /uuid:a4781538-557f-46eb-91f0-c898f3a661d5/WANPPPConnection:1 , serviceTypeName : urn:schemas-upnp-org:service:WANPPPConnection:1
[UPnP] Gateway info valid
[UPnP] Connecting to IGD with host : 192.168.2.1 , port : 5431
[UPnP] Connected to IGD
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. ESP8266_NODEMCU_ESP12E-WIFI 192.168.2.36 8266 8266 TCP 33690
76. ESP32_DEV-WT32_ETH01 192.168.2.232 5931 5931 TCP 35070
UPnP done
HTTP WiFiWebServer is @ IP : 192.168.2.232, port = 5931
Gateway Address: 192.168.2.1
Network Mask: 255.255.255.0
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example Portenta_H7_SimpleServer on PORTENTA_H7_M7 using Portenta_H7 WiFi
Start Portenta_H7_SimpleServer on PORTENTA_H7_M7 using Portenta_H7 WiFi
UPnP_Generic v3.5.0
Connecting to HueNet1
IP address: 192.168.2.130
Add Port Forwarding, Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. Portenta_H7-WIFI 192.168.2.130 6032 6032 TCP 35970
UPnP done
HTTP WiFiWebServer is @ IP : 192.168.2.130, port = 6032
[DDNS] Access whatismyipaddress
Connected
[DDNS] httpCode = 200
HttpClient::responseBody => bodyLength =15
[DDNS] Current Public IP = aaa.bbb.ccc.ddd
[DDNS] response = aaa.bbb.ccc.ddd
Connected
DDNSGeneric - IP Change Detected: aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example Portenta_H7_SimpleServer on PORTENTA_H7_M7 using Ethernet using Portenta_Ethernet Library
Start Portenta_H7_SimpleServer on PORTENTA_H7_M7 using Ethernet using Portenta_Ethernet Library
UPnP_Generic v3.5.0
Add Port Forwarding, Try # 1
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. Portenta_H7-LED-WIFI 192.168.2.130 6033 6033 TCP 35040
10. Portenta_H7-ETH 192.168.2.132 6032 6032 TCP 35970
UPnP done
HTTP EthernetWebServer is @ IP : 192.168.2.132, port = 6032
[DDNS] Access whatismyipaddress
Connected
[DDNS] httpCode = 200
HttpClient::responseBody => bodyLength =15
[DDNS] Current Public IP = aaa.bbb.ccc.ddd
[DDNS] response = aaa.bbb.ccc.ddd
Connected
DDNSGeneric - IP Change Detected: oldIP = , newIP = aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug terminal output when running example T41_QNEthernet_SimpleServer on Teensy 4.1 using built-in Ethernet with QNEthernet Library
Start T41_QNEthernet_SimpleServer on TEENSY 4.1
UPnP_Generic v3.5.0
IP Address = 192.168.2.123
[UPnP] UDP_TX_PACKET_MAX_SIZE= 1000
[UPnP] UDP_TX_RESPONSE_MAX_SIZE= 8192
[UPnP] newUpnpRule= 0.0.0.0
Add Port Forwarding, Try # 1
[UPnP] Internet connection GOOD
[UPnP] isGatewayInfoValid : 0.0.0.0 , port : 0
[UPnP] Path : , actionPort : 0
[UPnP] actionPath : , serviceTypeName :
[UPnP] Gateway info not valid
[UPnP] GW IP = 192.168.2.1
[UPnP] Sending M-SEARCH to : 239.255.255.250 , Port : 1900
[UPnP] Received packet, size = 331 , IP = 192.168.2.1
[UPnP] Port = 1900
[UPnP] IGD found
[UPnP] IGD location found : http://192.168.2.1:5431/dyndev/uuid:23a5ccd0-54ea-4ff8-9607-26c3b838e44c
[UPnP] 192.168.2.1
[UPnP] 5431
[UPnP] /dyndev/uuid:23a5ccd0-54ea-4ff8-9607-26c3b838e44c
[UPnP] Connecting to IGD with host : 192.168.2.1 , port : 5431
[UPnP] Connected to IGD
[UPnP] called getIGDEventURLs
[UPnP] deviceInfo->actionPath : , deviceInfo->path : /dyndev/uuid:23a5ccd0-54ea-4ff8-9607-26c3b838e44c
[UPnP] URLBase tag found : http://192.168.2.1:5431/
[UPnP] Translated to base host : 192.168.2.1 and base port : 5431
[UPnP] urn:schemas-upnp-org:service:WANPPPConnection:1 service found!
[UPnP] controlURL tag found! Setting actionPath to : /uuid:3e3d865a-8e93-453c-998d-0049f6ff26f5/WANPPPConnection:1
[UPnP] Port : 5431 , actionPort : 5431
[UPnP] isGatewayInfoValid : 192.168.2.1 , port : 5431
[UPnP] Path : /dyndev/uuid:23a5ccd0-54ea-4ff8-9607-26c3b838e44c , actionPort : 5431
[UPnP] actionPath : /uuid:3e3d865a-8e93-453c-998d-0049f6ff26f5/WANPPPConnection:1 , serviceTypeName : urn:schemas-upnp-org:service:WANPPPConnection:1
[UPnP] Gateway info valid
[UPnP] Verify port mapping for rule : T41-QNEth
[UPnP] Apply action : GetSpecificPortMappingEntry on port mapping : T41-QNEth
[UPnP] Connecting to IGD with host : 192.168.2.1 , port : 5431
[UPnP] Connected to IGD
[UPnP] Host: 192.168.2.1:5431
[UPnP] Port mapping found in IGD
[UPnP] All port mappings found in IGD, doing nothing
[UPnP] isGatewayInfoValid : 192.168.2.1 , port : 5431
[UPnP] Path : /dyndev/uuid:23a5ccd0-54ea-4ff8-9607-26c3b838e44c , actionPort : 5431
[UPnP] actionPath : /uuid:3e3d865a-8e93-453c-998d-0049f6ff26f5/WANPPPConnection:1 , serviceTypeName : urn:schemas-upnp-org:service:WANPPPConnection:1
[UPnP] Gateway info valid
[UPnP] Connecting to IGD with host : 192.168.2.1 , port : 5431
[UPnP] Connected to IGD
[UPnP] IGD current port mappings:
0. Blynk Server 192.168.2.110 9443 9443 TCP 0
1. Blynk WebServer 192.168.2.110 80 80 TCP 0
2. Blynk Hardware Server 192.168.2.110 8080 8080 TCP 0
3. Blynk Server 192.168.2.110 9443 1443 TCP 0
4. Blynk Secondary Server 192.168.2.112 9443 2443 TCP 0
5. Blynk Sec. Hardware Server 192.168.2.112 8080 1080 TCP 0
6. Blynk Server SSL 192.168.2.110 9443 443 TCP 0
7. MariaDB / MySQL 192.168.2.112 5698 5698 TCP 0
8. MariaDB / MySQL 192.168.2.112 3306 3306 TCP 0
9. T41-QNEth 192.168.2.123 6032 6032 TCP 35355
UPnP done
HTTP EthernetWebServer is @ IP : 192.168.2.123, port = 6032
[DDNS] Access ifconfig.me
Connected
[DDNS] httpCode = 200
HttpClient::responseBody => bodyLength =-1
[DDNS] Current Public IP = aaa.bbb.ccc.ddd
[DDNS] response = aaa.bbb.ccc.ddd
Connected
DDNSGeneric - IP Change Detected: oldIP = , newIP = aaa.bbb.ccc.ddd
[DDNS] Updated IP = aaa.bbb.ccc.ddd
Debug is enabled by default on Serial. To disable, add at the beginning of sketch
/* Comment this out to disable prints and save space */
// Debug Level from 0 to 4
#define _DDNS_GENERIC_LOGLEVEL_ 1
#define _UPNP_LOGLEVEL_ 3If you get compilation errors, more often than not, you may need to install a newer version of the board's core, dependent libraries or this library version.
Sometimes, the library will only work if you update the core to the newer or older version because some function compatibility.
Submit issues to: UPnP_Generic issues
- Bug Searching and Killing
- Support more non-compatible Ethernet Libraries such as Ethernet_Shield_W5200, EtherCard, EtherSia
- Add support to Arduino SAMD21 (ZERO, MKR, NANO_33_IOT, etc.)
- Add support to Adafruit SAMD21 (Itsy-Bitsy M0, Metro M0, Feather M0 Express, etc.).
- Add support to Adafruit SAMD51 (Itsy-Bitsy M4, Metro M4, Grand Central M4, Feather M4 Express, etc.).
- Add support to Adafruit nRF52 ( Feather nRF52832, nRF52840 Express, BlueFruit Sense, Itsy-Bitsy nRF52840 Express, Metro nRF52840 Express, NINA_B302_ublox, NINA_B112_ublox, etc.
- Add support to Seeeduino SAMD21/SAMD51 boards (SEEED_WIO_TERMINAL, SEEED_FEMTO_M0, SEEED_XIAO_M0, Wio_Lite_MG126, WIO_GPS_BOARD, SEEEDUINO_ZERO, SEEEDUINO_LORAWAN, SEEED_GROVE_UI_WIRELESS, etc.)
- Add support to STM32F/L/H/G/WB/MP1 (Nucleo-144, Nucleo-64, Nucleo-32, Discovery, STM32Fx, STM32H7, STM32Lx, STM32Gx, STM32WB, STM32MP1, etc.) having 64K+ Flash program memory.
- Add support to Ethernet W5x00, using either
Ethernet,Ethernet2,Ethernet3orEthernetLargelibrary - Add support to WiFiNINA using WiFiNINA or WiFiNINA_Generic library.
- Add support to ESP8266-AT, ESP32-AT WiFi shields using ESP8266_AT_WebServer or WiFiEspAT library.
- Add support to RP2040-based boards, such as RASPBERRY_PI_PICO, ADAFRUIT_FEATHER_RP2040 and GENERIC_RP2040, using Earle Philhower's arduino-pico core.
- Add support to RP2040-based boards, such as NANO_RP2040_CONNECT, RASPBERRY_PI_PICO, ADAFRUIT_FEATHER_RP2040 and GENERIC_RP2040, using Arduino-mbed RP2040 core.
- Add Version String and Table of Contents
- Add support to WT32_ETH01 boards using ESP32-based boards and LAN8720 Ethernet
- Add support to Portenta_H7, using either
Murata WiFiorVision-shield Ethernet - Use new Ethernet_Generic library as default for W5x00.
- Support SPI2 for ESP32
- Add support to SPI1 for RP2040 using arduino-pico core
- Add example multiFileProject_Ethernet and multiFileProject_WiFiNINA to demo how to avoid
multiple-definitionslinker error for multiple-file project - Add support to Teensy 4.1 built-in Ethernet using
NativeEthernetlibrary - Add support to Teensy 4.1 built-in Ethernet using
QNEthernetlibrary
Many thanks for everyone for bug reporting, new feature suggesting, testing and contributing to the development of this library.
- Based on and modified from the Ofek Pearl's TinyUPnP Library to add support to many boards and shields besides ESP32 and ESP8266
- Thanks to good work of Miguel Wisintainer for working with, developing, debugging and testing.
 ⭐️ Ofek Pearl |
 ⭐️ Miguel Wisintainer |
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.0
Copyright 2020- Khoi Hoang