---
title: "How to Add Wired Ethernet to an ESP32 Industrial PLC with W5500: Hoffer HF-006Enet"
url: "https://maker.wiznet.io/jakelee/resellers/how-to-add-wired-ethernet-to-an-esp32-industrial-plc-with-w5500-hoffer-hf-006enet/"
markdown_url: "https://maker.wiznet.io/jakelee/resellers/how-to-add-wired-ethernet-to-an-esp32-industrial-plc-with-w5500-hoffer-hf-006enet/md"
type: "VAR: Value-Added Reseller Products"
author: "Hoffer Automacao"
author_url: "https://www.hofferautomacao.com.br/clp-esp32-hf-006enet"
editor: "WIZnet"
editor_url: "https://maker.wiznet.io/"
original_author: "Hoffer Automacao"
original_url: "https://www.hofferautomacao.com.br/clp-esp32-hf-006enet"
published: "2026-11-23"
language: "en"
tags: ["Arduino IDE", "Industrial PLC"]
hardware: ["Espressif ESP32", "WIZnet W5500"]
likes: 0
views: 2
comments: 0
source: "WIZnet Makers (https://maker.wiznet.io/)"
---

# How to Add Wired Ethernet to an ESP32 Industrial PLC with W5500: Hoffer HF-006Enet

> Hoffer HF-006Enet combines ESP32 and W5500 SPI Ethernet with eight isolated inputs, six relays, Wi-Fi and RS485 for industrial control.

Original author: Hoffer Automacao (source: https://www.hofferautomacao.com.br/clp-esp32-hf-006enet)

## Components

- **Espressif ESP32** x 1 ([docs](https://www.espressif.com/en/products/socs/esp32))
- **WIZnet W5500** x 1 ([docs](https://docs.wiznet.io/Product/Chip/Ethernet/W5500))

WIZnet parts: W5500 ([Datasheet](https://docs.wiznet.io/Product/Chip/Ethernet/W5500/datasheet?utm_source=maker&utm_medium=project&utm_campaign=w5500), [product hub](https://maker.wiznet.io/products/w5500/))

## Article

## Step 1: Understanding the HF-006Enet Hardware

Hoffer Automação’s commercially offered **HF-006Enet** is an ESP32-based programmable controller designed around industrial digital I/O and network connectivity. Its dual-core 240 MHz ESP32 provides application control and Wi-Fi; a **WIZnet W5500** supplies wired 10/100 Mbps Ethernet over SPI.

- **Controller:** ESP32, dual-core, 240 MHz.

- **Inputs:** eight optocoupled digital inputs for 12 V or 24 V signals.

- **Outputs:** six relays with individual status indicators.

- **Networking:** W5500 10/100 Ethernet, RJ45, and ESP32 Wi-Fi.

- **Additional interfaces:** RS485, TTL serial and level-shifted I²C; RS485 and TTL serial share UART0.

- **Supply:** separate 12 V DC and 24 V DC board versions; not a documented universal 12–24 V input.

The HF-006Enet differs from the HF-006: the manufacturer’s manual states that the Ethernet version **replaces the HF-006 analog inputs and PWM output** with W5500 Ethernet. Do not assume those removed functions are present.

## Step 2: Connecting ESP32 to W5500 over SPI

The documented network path is **ESP32 → SPI → W5500 → RJ45 → local Ethernet LAN**. The manufacturer’s manual (page 50) and supplied sketch agree on the following SPI assignments:

| W5500 signal | ESP32 GPIO |
| --- | --- |
| MOSI | GPIO13 |
| MISO | GPIO12 |
| SCK | GPIO14 |
| CS | GPIO15 |

![Manual page 50 excerpt listing W5500 MOSI GPIO13, MISO GPIO12, SCK GPIO14 and CS GPIO15](https://maker.wiznet.io/upload/ckeditor5/5b0ff7b338c0475a810c08f80bd2ca0f.png)

*Manufacturer manual, page 50: W5500 SPI pin assignments. Reset pin documentation differs from the test sketch.*

## Step 3: Initializing Ethernet in Arduino Firmware

Hoffer provides a board-test sketch rather than a complete production PLC application. Its documented SPI initialization includes the following **source-derived code excerpt**:

```cpp
// From Hoffer HF-006Enet board-test sketch (SPI setup excerpt)
SPI.begin(14, 12, 13, 15);  // SCK, MISO, MOSI, CS
Ethernet.init(15);          // W5500 chip-select GPIO
```

The sketch also exercises DHCP and Ethernet status checks. Firmware developers must implement and validate any required MQTT, Modbus TCP, web service or SCADA integration separately. The presence of W5500 hardware does not establish that these application protocols are already implemented.

**Pin-mapping caution:** The manual’s Ethernet table assigns W5500 RESET to GPIO0, while the supplied sketch defines GPIO27. Its consolidated GPIO appendix also differs from the sketch’s digital-input mapping. Confirm the exact hardware revision and pinout before deployment. Although Hoffer describes an HSPI design intended to leave VSPI available, the sample uses the global `SPI` object; verify actual bus configuration in the selected software environment.

## Step 4: Understanding W5500 Ethernet Capabilities

The W5500 integrates an Ethernet MAC/PHY, a 10/100 Mbps physical interface, an SPI host interface, **32 KB internal packet buffer** and **eight hardware sockets**. The W5500 datasheet specifies SPI operation up to **80 MHz**. These are chip-level capabilities, *not measured HF-006Enet throughput or verified SPI clock settings*.

W5500 supports hardwired TCP/IP functions, but the manufacturer’s public test sketch does not establish which socket or network stack configuration a final customer application uses. Firmware, network architecture and deployment testing determine practical latency, security and reliability.

![WIZnet’s generic W5500 block diagram showing the chip’s SPI, networking and Ethernet functions](https://maker.wiznet.io/upload/ckeditor5/9752f5f874bc4336b1482dff89a5a8b6.png)

*WIZnet W5500 chip-level architecture showing SPI interface, socket/TCP-IP logic and 10/100 Ethernet MAC/PHY. This is not the HF-006Enet schematic.*

## Step 5: Applying the Controller to Industrial Automation

HF-006Enet combines a wired network connection with field-facing inputs and relays, making it a candidate for machine-status monitoring, digital I/O endpoints, and serial-to-IP gateway development. Hoffer also presents SCADA integration, MQTT dashboards and remote monitoring as application targets. These are **potential firmware-driven uses**, not separately verified applications in this review.

Hoffer states Ethernet and Wi-Fi can operate simultaneously. This should not be interpreted as proven automatic failover, secure segmentation or uninterrupted service. The manufacturer’s test materials do not include measured Ethernet throughput, switching-load endurance or production failover results.

## FAQ

### Q1. Why use W5500 in the Hoffer HF-006Enet ESP32 PLC?

**W5500 provides dedicated wired 10/100 Mbps Ethernet connectivity to the ESP32 over SPI.** It integrates the Ethernet MAC and PHY as well as hardware TCP/IP socket functionality, reducing the need for a separate Ethernet networking subsystem. On HF-006Enet, the ESP32 remains responsible for application logic and field I/O. The available documentation confirms the chip’s presence, not an application-level performance improvement.

### Q2. How is W5500 connected to the ESP32 in HF-006Enet?

**W5500 connects through SPI using GPIO14 for SCK, GPIO12 for MISO, GPIO13 for MOSI and GPIO15 for chip select.** These four assignments agree between the manufacturer’s manual and test sketch. The sample initializes them using `SPI.begin(14, 12, 13, 15)` and `Ethernet.init(15)`. However, the reset pin and some digital-input mappings conflict across documents, so a revision-specific pinout is necessary before installation.

### Q3. What throughput or latency benefits does W5500 deliver?

**W5500 supports 10/100 Mbps Ethernet and an SPI host interface specified up to 80 MHz.** It also has 32 KB of internal packet memory and eight hardware sockets. These figures describe the W5500 IC, not measured HF-006Enet performance. Actual application throughput and latency depend on ESP32 firmware, SPI configuration, packet sizes and network conditions. Hoffer’s public board-test sketch does not report benchmark results.

### Q4. Does W5500 make the PLC more secure or stable?

**W5500 offers a wired interface and hardwired networking functions, but these do not automatically guarantee system security or uptime.** Wired Ethernet can avoid dependence on Wi-Fi radio conditions. However, authentication, access control, safe relay behavior, recovery logic and network isolation must be implemented and tested at system level. The manufacturer states that Ethernet and Wi-Fi may run together, but automatic failover has not been demonstrated in the reviewed materials.

### Q5. How does W5500 compare with Wi-Fi or a software TCP/IP implementation?

**W5500 adds a physical Ethernet path alongside the ESP32’s native Wi-Fi.** Its integrated MAC/PHY and hardware TCP/IP resources can simplify certain embedded networking architectures compared with a separate MAC/PHY plus software stack. The HF-006Enet product confirms the wired interface, but the reviewed sketch does not establish a controlled comparison against Wi-Fi or lwIP. Choose the interface based on wiring, firmware, security and installation requirements.

## References

1. [Hoffer Automação — HF-006Enet product page](https://www.hofferautomacao.com.br/clp-esp32-hf-006enet)

2. [Hoffer — Official downloads](https://www.hofferautomacao.com.br/arquivos-para-download)

3. [HF-006Enet manual and TESTE_HF006enet_2026.ino archive](https://drive.google.com/file/d/15L0EgIoybn_fYRZGFvkn-XeFQFWEIena/view)

4. [WIZnet W5500 product documentation](https://docs.wiznet.io/Product/Chip/Ethernet/W5500)

5. [W5500 datasheet v1.1.0](https://docs.wiznet.io/assets/files/W5500_ds_v110e-226ffec190c588b69f88d629789585e1.pdf)

---

Source: https://maker.wiznet.io/jakelee/resellers/how-to-add-wired-ethernet-to-an-esp32-industrial-plc-with-w5500-hoffer-hf-006enet/
