---
title: "How to Add Wired Ethernet with WIZnet W5500 to an ESP32-Based Industrial IoT Control Panel?"
url: "https://maker.wiznet.io/jaden/resellers/how-to-add-wired-ethernet-with-wiznet-w5500-to-an-esp32-based-industrial-iot-control-panel/"
markdown_url: "https://maker.wiznet.io/jaden/resellers/how-to-add-wired-ethernet-with-wiznet-w5500-to-an-esp32-based-industrial-iot-control-panel/md"
type: "VAR: Value-Added Reseller Products"
author: "Akıllı Pano"
author_url: "https://www.akillipano.com/urun/akilli-kapi-kontrol-panosu/"
editor: "WIZnet"
editor_url: "https://maker.wiznet.io/"
original_author: "Akıllı Pano"
original_url: "https://www.akillipano.com/urun/akilli-kapi-kontrol-panosu/"
published: "2026-11-05"
language: "en"
likes: 0
views: 5
comments: 0
source: "WIZnet Makers (https://maker.wiznet.io/)"
---

# How to Add Wired Ethernet with WIZnet W5500 to an ESP32-Based Industrial IoT Control Panel?

> ESP32-WROOM-32E, W5500 Ethernet, and 5-Channel Relay Automation

Original author: Akıllı Pano (source: https://www.akillipano.com/urun/akilli-kapi-kontrol-panosu/)

## Article

## **How to Add Wired Ethernet with WIZnet W5500 to an ESP32-Based Industrial IoT Control Panel?**

Technical Case Study: Akıllı Pano Nilo — ESP32-WROOM-32E, W5500 Ethernet, and 5-Channel Relay Automation

### **1. Summary**

The **Nilo Akıllı Pano**, developed by Turkish automation equipment supplier Akıllı Pano, is an ESP32-WROOM-32E-based industrial IoT control panel designed to manage pumps, valves, fans, lighting, and other electrical equipment. It provides five relay outputs with modular expansion and supports multiple communication interfaces, including Wi-Fi, Bluetooth, RS485, CAN Bus, and LoRa. An optional **WIZnet W5500 Ethernet module** enables wired TCP/IP networking for integration with local networks, web interfaces, and MQTT servers. The W5500 handles hardware TCP/IP communication, allowing the ESP32 to focus on device control and field data processing. The manufacturer confirms W5500 availability as an option, although its PCB connections and firmware implementation have not been publicly verified.

### **2. What the Project Does**

Nilo Akıllı Pano combines local equipment control, industrial field communication, and optional remote connectivity in a modular automation panel.

The ESP32-WROOM-32E serves as the main controller. It can process data from connected sensors and field devices, execute control logic, and operate relay outputs. Applications described by the manufacturer include agricultural irrigation, greenhouse automation, pump management, building automation, ventilation, and lighting control.

The standard configuration provides five independent relay outputs. Expansion modules allow the system to scale in five-channel increments to 10, 15, 20, or more outputs.

#### **Hardware specifications**

| **Component** | **Manufacturer-stated specification** |
| --- | --- |
| Product | Nilo Akıllı Pano |
| Product code | 101 |
| Main MCU | ESP32-WROOM-32E |
| Memory | 16 MB; memory type not specified |
| Control power | 24V DC |
| Standard outputs | 5 independent relay channels |
| Expansion | Additional 5-channel modules |
| Industrial interfaces | RS485 and CAN Bus |
| Wireless interfaces | Wi-Fi, Bluetooth, and LoRa |
| Wired networking | Optional WIZnet W5500 Ethernet module |
| Field protocol | Modbus RTU |
| Enclosure | IP65-rated |
| Installation | Wall or field installation |

These specifications are described in the manufacturer's [official product listing](https://www.akillipano.com/urun/akilli-kapi-kontrol-panosu/?utm_source=chatgpt.com).

#### **Industrial IoT application**

A greenhouse automation installation illustrates how the hardware can be used.

Temperature and humidity sensors provide environmental measurements, while additional devices monitor conditions such as rainfall, wind, or water flow. The ESP32 processes the available measurements and operates relays connected to equipment such as ventilation fans, irrigation valves, or pump contactors.

RS485 provides an interface for compatible Modbus RTU field devices, while an Ethernet-connected configuration can exchange operational information with an IP-based monitoring system.

This architecture separates three responsibilities: field data acquisition, local equipment control, and network communication.

### **3. Where WIZnet Fits**

![2Pcs W5500 LQFP-48 Ethernet ICs 3in1 Enet Controller TCP/IP +MAC+PHY | eBay](https://images.openai.com/static-rsc-4/fUuuUojqQVdBvvhRjVcQ95x_hlulx1l69ptC9U_RqzAnLQ_xY5AOHRhKa5rJ8FFzcjArgcn-3ja7S0fepaBE7GZKiWAQofVG-hhhLt1qJfj623fYsuzTs2skh03cj4AFU2Zo6GVfT-sSXkSM-lH8z67gfgygrt254Zh6H1ttJrI?purpose=inline)

**WIZnet W5500**

The W5500 is a hardwired TCP/IP Ethernet controller integrating an Ethernet MAC, PHY, socket management, and packet buffers. It communicates with an external microcontroller through SPI.

#### **Confirmed W5500 support**

The manufacturer's product description explicitly identifies the following option:

> “Opsiyonel W5500 Ethernet modülü”

This means *optional W5500 Ethernet module*.

The manufacturer also describes using the Ethernet option to connect the panel to a local wired network and communicate with web panels, MQTT servers, mobile applications, or cloud systems.

This establishes the W5500 as a documented hardware option, rather than a hypothetical component introduced solely for this article.

However, the listing does not establish that every Nilo panel contains a W5500, and the publicly available material does not establish the controller's exact PCB connections or firmware configuration.

#### **Technical role of the W5500**

The W5500 provides a hardware TCP/IP interface between the ESP32 controller and an Ethernet network.

## **8**

Independent hardware sockets

## **32 KB**

Internal TX/RX buffer memory

## **80 MHz**

Maximum SPI clock

## **10/100**

Mbps Ethernet PHY

W5500 specifications from [WIZnet official documentation](https://docs.wiznet.io/Product/Chip/Ethernet/W5500?utm_source=chatgpt.com).

The W5500 implements TCP/IP functions in dedicated hardware, including socket operations and packet buffering. This reduces the amount of TCP/IP processing that must be performed directly by the host MCU.

For an ESP32-based control panel, that division of work is useful because the application may need to handle fieldbus communication, sensor processing, and relay control while maintaining network connections.

The benefit should not be overstated. The manufacturer does not publish benchmark results demonstrating CPU utilization reductions, lower latency, or improved control-loop timing specifically attributable to W5500 integration.

#### **Communication architecture**

Functional architecture derived from the documented product features. This is not a manufacturer-provided wiring diagram or verified firmware data-flow trace.

#### **Wired Ethernet versus Wi-Fi**

The Nilo platform offers both Wi-Fi connectivity and a W5500 Ethernet option, allowing the network interface to be selected according to installation requirements.

| **Consideration** | **W5500 Ethernet** | **ESP32 Wi-Fi** |
| --- | --- | --- |
| Physical connection | Wired Ethernet cable | Wireless radio |
| TCP/IP processing | Dedicated W5500 hardware | ESP32 wireless/network stack |
| RF interference | No direct wireless channel dependence | Affected by RF conditions |
| Installation | Requires Ethernet cabling | Requires wireless coverage |
| Device mobility | Restricted by cable routing | More flexible |
| Failure conditions | Cable, connector, switch, power | RF interference, AP, signal coverage |
| Infrastructure | Ethernet switch and LAN | Access point and wireless network |

For fixed industrial installations with existing Ethernet infrastructure, W5500 can reduce dependence on RF conditions and wireless access-point management.

Wi-Fi may be more practical where Ethernet cabling is difficult, costly, or incompatible with equipment mobility.

Neither interface inherently guarantees uninterrupted communication or deterministic application-level latency. Those characteristics depend on the complete network, firmware, and control-system design.

### **4. Implementation Notes**

#### **ESP32-to-W5500 hardware interface**

The manufacturer's product documentation identifies the ESP32-WROOM-32E as the main controller and the W5500 Ethernet module as an optional network interface.

However, it does not provide a public schematic identifying the GPIO assignments, SPI clock configuration, reset circuit, or interrupt connections used in the commercial product.

According to WIZnet's official documentation, the W5500 communicates with its host MCU over SPI.

| **W5500 signal** | **ESP32 interface** | **Purpose** |
| --- | --- | --- |
| SCLK | SPI clock | Synchronizes SPI transfers |
| MOSI | SPI controller output | Transfers data from ESP32 to W5500 |
| MISO | SPI controller input | Transfers data from W5500 to ESP32 |
| CSn | GPIO chip select | Selects the W5500 for SPI communication |
| RSTn | GPIO or reset circuit | Hardware reset |
| INTn | Optional GPIO input | Interrupt notification |
| VDD / GND | Appropriate power supply | Power and ground |

This table describes the general W5500 interface, not the verified pin assignments of Nilo Akıllı Pano.

The W5500 chip operates at 3.3V. The power-input requirements of a complete Ethernet module must be checked against that module's documentation.

#### **Network initialization**

WIZnet provides the open-source [ioLibrary_Driver](https://github.com/Wiznet/ioLibrary_Driver?utm_source=chatgpt.com) for implementing Ethernet communication with its controllers.

The library supports network configuration, socket operations, and related functions. It can serve as a technical reference for integrating W5500 with an ESP32-based application.

A typical integration sequence includes:

**Initialize the SPI peripheral.** Configure the MCU interface, chip-select handling, and W5500 reset sequence.

**Initialize the W5500.** Confirm device communication and configure internal socket memory.

**Configure network addressing.** Assign a MAC address and configure DHCP or static IPv4 parameters.

**Check Ethernet link status.** Detect physical connection changes and handle loss of connectivity.

**Establish network sockets.** Allocate TCP or UDP sockets for the required application protocols.

**Exchange application data.** Transfer sensor readings, equipment status, and control messages between the ESP32 application and network services.

This is an architecture-level integration sequence, not code extracted from the Nilo firmware. The manufacturer has not publicly identified the software library or initialization sequence used in its W5500 option.

#### **Separating field communication from Ethernet communication**

Nilo supports Modbus RTU communication through RS485 and offers Ethernet connectivity through its optional W5500 module.

These interfaces serve different purposes.

Modbus RTU can connect industrial sensors, meters, inverters, and other compatible field devices to the ESP32 controller.

Ethernet can provide an upstream connection to an IP-based monitoring system or MQTT broker.

For example, a possible implementation would read a pressure measurement through RS485, process it in the ESP32, and publish the resulting status through a TCP connection managed by W5500.

The manufacturer's documentation supports the availability of these interfaces, but does not establish this specific data-transfer sequence as an implemented firmware feature.

Similarly, the presence of RS485 Modbus RTU and Ethernet does not independently establish support for Modbus TCP.

### **5. Practical Tips / PitfallsVerify the installed hardware option.** W5500 is optional rather than standard equipment. Confirm that the purchased configuration includes the Ethernet module.

**Validate SPI wiring and electrical compatibility.** Check SCLK, MOSI, MISO, CS, reset, and power connections against the actual hardware design. Avoid assuming GPIO assignments from generic ESP32 examples.

**Plan socket and buffer allocation.** The W5500 supports eight hardware sockets and 32 KB of internal TX/RX buffer memory. Concurrent MQTT, web, and other TCP/UDP connections must fit within those resources.

**Handle IP configuration and network recovery.** Choose static addressing or DHCP according to deployment requirements. Implement recovery from cable disconnection, link loss, and server failures.

**Keep safety-critical control local.** A network outage must not cause unsafe relay behavior. Define control timeouts, fallback states, and independent protective mechanisms where required.

**Protect against electrical interference.** Pumps, motors, and contactors can generate switching transients. Review power-supply protection, grounding, cable routing, and surge suppression.

**Preserve the enclosure protection rating.** Ethernet cabling must enter the IP65 enclosure through suitable sealed fittings. Cable entries and unused openings require appropriate sealing.

### **6. FAQQ1. Why does Nilo Akıllı Pano support the WIZnet W5500?**

The W5500 provides an optional wired Ethernet interface for connecting the ESP32-based control panel to local IP networks, web interfaces, and MQTT servers. Its hardware TCP/IP architecture can reduce network-processing responsibilities on the host MCU. Wired Ethernet also removes dependence on wireless signal coverage and RF channel conditions, which can be useful in fixed industrial installations.

**Q2. How does the W5500 connect to the ESP32-WROOM-32E?**

The W5500 uses SPI, including SCLK, MOSI, MISO, and CS signals. Reset and interrupt connections may also be used depending on the implementation. Although the manufacturer confirms W5500 module support, the specific GPIO mapping, SPI clock rate, and circuit configuration used in Nilo have not been publicly verified.

**Q3. What exactly does the W5500 do in this project?**

The W5500 serves as the optional wired Ethernet controller. According to the manufacturer, it allows the panel to connect to local networks and communicate with web panels, MQTT servers, mobile applications, and cloud systems. The ESP32 remains responsible for application logic, sensor processing, and relay control.

**Q4. Can beginners build a similar ESP32 and W5500 control panel?**

Developers familiar with SPI and basic TCP/IP networking can begin with an ESP32 development board, a W5500 module, and WIZnet's official driver library. Building an industrial control panel comparable to Nilo requires additional knowledge of relay circuits, power distribution, electrical isolation, electromagnetic compatibility, and equipment safety. Low-voltage development hardware is the appropriate starting point.

**Q5. When should W5500 Ethernet be selected instead of ESP32 Wi-Fi?**

W5500 Ethernet is useful when equipment is installed in a fixed location, wired infrastructure is available, and dependence on wireless coverage or RF conditions should be minimized. Wi-Fi is more suitable where cable installation is difficult or equipment mobility is important. Ethernet still requires link-failure detection, network recovery, and appropriate system-level safety measures.

### **7. SourceOriginal Product — Akıllı Pano**

[Nilo Akıllı Pano Industrial Automation Control Panel](https://www.akillipano.com/urun/akilli-kapi-kontrol-panosu/?utm_source=chatgpt.com)

Manufacturer product listing for product code 101. The published specifications identify the ESP32-WROOM-32E, five independent relay outputs, 24V DC control power, RS485, CAN Bus, LoRa, and the optional W5500 Ethernet module.

The manufacturer also describes potential connectivity to web panels, MQTT servers, mobile applications, and cloud platforms.

**WIZnet W5500 Technical Documentation**

[W5500 Official Documentation — WIZnet](https://docs.wiznet.io/Product/Chip/Ethernet/W5500?utm_source=chatgpt.com)

Technical reference for the W5500 hardware TCP/IP architecture, SPI interface, internal buffers, socket resources, and Ethernet capabilities.

**WIZnet Ethernet Driver**

[WIZnet ioLibrary_Driver — GitHub](https://github.com/Wiznet/ioLibrary_Driver?utm_source=chatgpt.com)

Official driver repository supporting WIZnet Ethernet controllers, including the W5500. It is provided as an implementation reference; its use in the commercial Nilo firmware has not been confirmed.

**License:** A public reuse license for the Nilo commercial product documentation or firmware has not been identified. The WIZnet driver is distributed under the license included in its repository.

### **8. Tags**

#W5500 #WIZnet #ESP32 #ESP32WROOM32E #IndustrialIoT #Ethernet #HardwareTCPIP #MQTT #ModbusRTU #IndustrialAutomation #RelayControl #AkilliPano

---

Source: https://maker.wiznet.io/jaden/resellers/how-to-add-wired-ethernet-with-wiznet-w5500-to-an-esp32-based-industrial-iot-control-panel/