Project Files of WT32-ETH01 Library for Proteus: ESP32 Ethernet Board (LAN8720)

WT32-ETH01 LIBRARY FOR PROTEUS - V1.0 (THE ESP32 BOARD WITH ETHERNET ON IT: LAN8720 + RJ45, THE ETH LIBRARY)
Designed by The Engineering Projects www.TheEngineeringProjects.com

IMPORTANT LINKS
Article (read it first - pictures, step by step, every feature explained):
  https://www.theengineeringprojects.com/2026/10/wt32-eth01-library-for-proteus.html
Report a bug or suggest a feature (our forum):
  https://www.theengineeringprojects.com/forum/category/wt32-eth01-proteus-library
The demo talks to our Laptop WiFi Monitor and Mobile WiFi Monitor (both included) - their articles:
  https://www.theengineeringprojects.com/2026/10/laptop-wifi-monitor-library-for-proteus.html
  https://www.theengineeringprojects.com/2026/10/mobile-wifi-monitor-library-for-proteus.html
The same LAN8720 as a separate module for our ESP32-DevKitC V4:
  https://www.theengineeringprojects.com/2026/10/lan8720-ethernet-module-library-for-proteus.html
Support us (the libraries are free):
  https://www.theengineeringprojects.com/donate

FILE STRUCTURE
WT32-ETH01-TEP-v1.0/
|-- Proteus Library Files/
|   |-- TEPLAPTOP.LIB                                                39.5 KB   the laptop, to LIBRARY
|   |-- TEPMOBILE.LIB                                                13.1 KB   the phone, to LIBRARY
|   |-- TEPWT32ETH01.LIB                                             35.5 KB   the WT32-ETH01 board, to LIBRARY
|-- Proteus Model Files/
|   |-- TEPNET.DLL                                                   2.19 MB   board + network, to MODELS
|-- Proteus Simulation/
|   |-- TEPNET.DLL                                                   2.19 MB   copy of the model
|   |-- WT32_ETH_Relay_Controller.hex                                65.8 KB   U1 of both demos
|   |-- WT32-ETH01-Board.pdsprj                                      16.0 KB   demo 1: the board alone
|   |-- WT32-ETH01-Relay-Controller-with-Laptop-and-Mobile.pdsprj    24.5 KB   demo 2: + laptop + phone
|-- Arduino Code/
|   |-- WT32_ETH_Relay_Controller/WT32_ETH_Relay_Controller.ino       6.1 KB   the WT32-ETH01 sketch (ETH)
|   |-- TEP Boards for Proteus/hardware/tep/avr/                    610.5 KB   the Arduino IDE add-on 1.15.0 (153 files)
|-- README.txt                                                      ~18.8 KB   this file
Total: 5.20 MB (unzipped). The C++ source code of the models is not included.

WHAT IS IT?
The WT32-ETH01 of Wireless-Tag as one Proteus part: an ESP32 board with wired Ethernet on it. The black board carries
the WT32-S1 module (an ESP32 with 4 MB flash and a PCB antenna), a Microchip LAN8720A 10/100 Ethernet PHY with its
50 MHz oscillator, a HanRun RJ45 MagJack with a green link / activity LED and a yellow speed LED, an AMS1117 3.3 V
regulator, a red PWR LED and two 13-pin headers. The real board has no USB: it is programmed through TXD / RXD with a
USB-serial adapter (IO0 to GND for the download mode).
  * The ESP32's own Ethernet MAC talks to the LAN8720A on the board's RMII lines (GPIO19, 21, 22, 25, 26, 27, the 50
    MHz clock into GPIO0, enabled by GPIO16; MDC GPIO23, MDIO GPIO18; PHY address 1). These GPIOs are used inside the
    board: they are not on the headers. The sketch's ETH library does the rest (DHCP or a fixed address, TCP, UDP -
    the same WiFiClient / WiFiServer / WebServer classes as on Wi-Fi).
  * ETH.begin() needs no arguments with the board WT32-ETH01 (TEP Proteus) of our TEP Boards for Proteus add-on
    1.15.0 (included): its ETH_PHY_* defaults are the board's (ETH_PHY_ADDR 1, ETH_PHY_POWER 16, ETH_PHY_MDC 23,
    ETH_PHY_MDIO 18, ETH_CLOCK_GPIO0_IN). The model checks them as the real driver finds the PHY: another address,
    another MDC / MDIO or no ETH_PHY_POWER 16 (the oscillator stays off, no 50 MHz clock) and ETH.begin() returns
    false; Proteus's simulation log says why.
  * The events, as on a real ESP32: ETH_START (ETH.begin), ETH_CONNECTED (the cable's link: 1.2 s of
    auto-negotiation, 100 Mbit/s full duplex), ETH_GOT_IP (DHCP 0.9 s later: 192.168.1.(100 + the board's number), or
    at once with ETH.config()), ETH_DISCONNECTED (the cable out: the connections wait; back within 20 s they carry
    on, after 20 s without a link they are dropped and ETH_LOST_IP comes), ETH_STOP (ETH.end). WiFi.onEvent() (core
    2.x) and Network.onEvent() (core 3.x) handlers are called between loop() runs and while the sketch waits in
    delay().
  * The LEDs: the jack's green LINK / ACT LED (on with the link, blinking with the frames), its yellow 100M LED (the
    speed), the red PWR LED; the cable's blue plug in the port.
  * The cable: the CABLE property (IN / OUT), a click on the RJ45 jack, or CABLE IN / CABLE OUT in the panel.
The part is drawn our way at the real board's proportions (60 x 26 mm, smaller than an Arduino UNO), turned on its
side: the RJ45 jack at the left end, the LAN8720A, its oscillator and the regulator in the middle, the WT32-S1 module
and its antenna at the right end, one header along the top, the other along the bottom, each pin named on the board.

ONE DEVICE (search "WT32" in Pick Devices):
  WT32-ETH01  "WT32-ETH01 (ESP32 + LAN8720 Ethernet)" V1.0 (category Microprocessor ICs > ESP32 Boards), prefix U,
              model TEPNET.DLL
  The panel (a TEP pop-up window, the look of the TEP Serial Monitor - our own header, no Windows title bar; it opens
  at Run, the PANEL pad opens it again). Tabs:
    Wi-Fi     a phone with three tabs - BROWSER (OPEN WT32 PAGE: the phone opens the sketch's web page, tap its
              links), ROUTER (the router's DHCP clients - a board with a fixed address is not among them) and
              CLOUD (the internet host's requests); ETHERNET CABLE IN / OUT; the cards BOARD, ETHERNET (router,
              status, address, the link, DHCP or the static address) and TRAFFIC
    Pins      the 15 GPIOs of the headers live (HIGH, LOW, PWM, input, touch) with the ADC pins' voltage and reading
    Test      web request test (the phone opens the page n times, measured) and cable test (the cable pulled for 3 s,
              measured)
    Settings  theme, text size, open at Run, window size
    Help      report a bug, suggest a feature, article, updates, donate, forum; Copy diagnostics
  The serial monitor (115200 baud by default, on TXD / RXD - the SERIAL pad opens it) has its own window with
  Monitor, Plotter and Board tabs.
The same TEPNET.DLL also runs our LAN8720 Ethernet Module, the other ESP32, ESP8266, Arduino and Pico W boards, our
Ethernet and Wi-Fi shields, modules and breakouts and the Laptop / Mobile WiFi Monitors (TEPLAPTOP.LIB, TEPMOBILE.LIB,
included for the demo); it replaces any older TEPNET.DLL (keep only this newest one in MODELS).

TEST STATUS
V1.0: verified in Proteus 8.5 on 23 Oct 2026 with the two demo projects as shipped (the windows off-screen, posted
clicks and keys). What the Proteus runs showed:
  * Run (the board alone): the monitor shows WT32-ETH01 Relay Controller, mDNS: http://wt32.local/, ETH started,
    ETH link up: 100 Mbit/s and ETH address 192.168.1.50 (fixed, ETH.config) - on the LAN at 1.3 s of simulation (the
    1.2 s link, then the fixed address at once); the PWR LED, the jack's green LINK / ACT and yellow 100M LEDs light,
    the cable's plug is in the port.
  * The demo: the panel shows the board on the LAN (static address, 100 Mbit/s full duplex, the board's LAN8720). The
    laptop's browser opens http://192.168.1.50/status (HTTP 200, 129 bytes in 0.05 s: OUT1 OFF, OUT2 OFF, 0
    switches); its TCP terminal connects to 192.168.1.50:5000 and gets the command list; 1 ON answers "OK OUT1 ON,
    OUT2 OFF, 1 switches, 192.168.1.50" and D1 on IO32 lights; STATUS answers the same state.
  * The phone opens http://wt32.local/ (HTTP 200, 450 bytes in 0.13 s): OUT1 ON, OUT2 OFF, the five links, the fixed
    address and the link; its 2 ON link lights D2 on IO33 ("OUT2 ON (the web page)" in the monitor).
  * The cable out (CABLE OUT in the panel): "ETH link down - the cable is out" at once, the jack's LEDs off, the plug
    out of the port; the cable back in: the link and the address 192.168.1.50 again. The laptop's terminal stayed
    connected through it: ALL OFF and STATUS answered "OUT1 OFF, OUT2 OFF, 4 switches".
  * The monitor's 2 ON, STATUS and HELP answer ("OK OUT1 OFF, OUT2 ON, 5 switches, 192.168.1.50"); the Pins page shows
    CFG (IO32) driven LOW and 485EN (IO33) driven HIGH.
  * The panel's Test page: the web request test answered 3 of 3 (connect 4.0 ms, first byte 32.6 ms, full page 47.6
    ms, 450 bytes); the cable test (3 pulls of 3 s) put the board back on the LAN 1.205 s after the cable went back in
    each time (the fixed address: no DHCP).
  * Speed: about 0.3 x real time with the board's sketch, the laptop and the phone running (the sketch runs on the
    hidden ATmega2560 of the board).

INSTALLATION (about 5 minutes)
1. Close Proteus. Extract the WHOLE ZIP to a normal folder (e.g. Desktop).
2. Copy everything in "Proteus Library Files" to the LIBRARY folder of Proteus, for example:
     C:\Program Files (x86)\Labcenter Electronics\Proteus 8 Professional\LIBRARY
   (on some PCs: C:\ProgramData\Labcenter Electronics\Proteus 8 Professional\LIBRARY - use the folder that already
   holds Proteus's own .LIB files). TEPWT32ETH01.LIB is the board; TEPLAPTOP.LIB and TEPMOBILE.LIB our Laptop WiFi
   Monitor and Mobile WiFi Monitor.
3. Copy TEPNET.DLL from "Proteus Model Files" to the MODELS folder (...\Proteus 8 Professional\MODELS) - replace
   older copies (this TEPNET.DLL is the first one with the WT32-ETH01; it still runs every part of the series).
4. Delete TEPWT32ETH01.IDX, TEPLAPTOP.IDX and TEPMOBILE.IDX from the LIBRARY folder if they are there.
5. The Arduino IDE (only to compile your own sketches - the demos have their HEX file): the add-on is in "Arduino
   Code\TEP Boards for Proteus". The Arduino AVR Boards platform must be installed (IDE 2.x: Boards Manager, "Arduino
   AVR Boards"). Copy the folder "hardware" into your sketchbook folder - the result:
     Documents\Arduino\hardware\tep\avr\boards.txt
   (an older TEP Boards for Proteus there: replace it - 1.15.0 has the WT32-ETH01 board). Restart the IDE and pick
   Tools > Board > TEP Boards for Proteus > WT32-ETH01 (TEP Proteus).
6. Start Proteus. In Pick Devices (P) search "WT32".

RUN THE DEMOS
Keep the .hex file and TEPNET.DLL beside the projects in "Proteus Simulation".
  WT32-ETH01-Board.pdsprj - the board alone (WT32_ETH_Relay_Controller.hex): press Run, the monitor shows ETH
  started, the link and the fixed address; click the RJ45 jack to pull the cable.
  WT32-ETH01-Relay-Controller-with-Laptop-and-Mobile.pdsprj - U1 the WT32-ETH01 (WT32_ETH_Relay_Controller.hex, its
  monitor at 115200 bps) with R1 (220R) + D1 (LED-GREEN) on IO32 (CFG, OUT1) and R2 (220R) + D2 (LED-GREEN) on IO33
  (485_EN, OUT2). PC1 the Laptop WiFi Monitor (its TCP terminal to 192.168.1.50:5000, home page
  http://192.168.1.50/status) and MOB1 the Mobile WiFi Monitor (home page http://wt32.local/) - no wires, they are on
  the router's network; the board's own RJ45 is its cable to the router.
  Press Run. The monitor shows ETH started, ETH link up: 100 Mbit/s and ETH address 192.168.1.50 (fixed,
  ETH.config). In the laptop's Terminal tab press Connect and type 1 ON, 2 ON, ALL OFF, STATUS or HELP; the phone's
  Browser (Go) shows the page with the 1 ON, 1 OFF, 2 ON, 2 OFF and ALL OFF links; the laptop's Browser shows /status.
  Pull the cable (CABLE OUT in the panel, or click the jack): ETH link down; put it back: the link and the address
  again - the laptop's terminal stays connected. The monitor takes the same commands.

PINS (the real board turned on its side: its left header is the top row, its right header the bottom row)
  Top row, left to right:    LINK 5V GND 3V3 GND TXD(IO17) RXD(IO5) 485_EN(IO33) CFG(IO32) EN 3V3 GND EN
  Bottom row, left to right: GND IO2 IO4 IO35 IO12 IO14 IO15 IO36 IO39 GND IO0 RXD(IO3) TXD(IO1)
  5V, 3V3, GND      power: 5 V into the AMS1117, or 3.3 V straight to the 3V3 pins (in the simulation the board runs
                    without wires to them)
  EN                the ESP32's enable (both EN pins: LOW holds the board in reset)
  TXD / RXD (IO1 / IO3)  Serial (the monitor; the programming port of the real board)
  TXD / RXD (IO17 / IO5) Serial2
  485_EN, CFG       IO33 and IO32 - free GPIOs for your sketch (the names come from the board's serial-to-Ethernet
                    firmware)
  IO35, IO36, IO39  inputs only (ADC)
  IO0               the boot strap and the LAN8720's 50 MHz clock input - leave it free
  LINK              the LAN8720's link LED signal (not driven in the simulation)

THE DEMO SKETCH (Arduino Code)
  WT32_ETH_Relay_Controller  #include <ETH.h>; WiFi.onEvent(onEvent); ETH.begin() with no arguments (the board's
                    defaults); ETH.config(192.168.1.50, gateway 192.168.1.1, 255.255.255.0, DNS 192.168.1.1); MDNS
                    wt32.local. Two outputs, OUT1 on IO32 and OUT2 on IO33 (say two relay drivers - LEDs in the demo),
                    switched from the web page on port 80 (/, /1on, /1off, /2on, /2off, /alloff; /status as
                    text/plain), the TCP terminal on port 5000 and the serial monitor: 1 ON, 1 OFF, 2 ON, 2 OFF, ALL
                    OFF, STATUS, HELP. The event handler prints ETH started, the link speed and the address.
  The same sketch compiles for a real WT32-ETH01 with Espressif's core 3.x and its board "WT32-ETH01 Ethernet Module".
  On the core 2.x write ETH.begin(1, 16, 23, 18, ETH_PHY_LAN8720, ETH_CLOCK_GPIO0_IN) (its defaults are another
  board's).

PROPERTIES (double-click the board > Edit Properties)
  PROGRAM   the sketch's HEX (Arduino IDE: Sketch > Export Compiled Binary with the board WT32-ETH01 (TEP Proteus))
  CABLE     the Ethernet cable at Run: IN (default) or OUT
  WIFISSID  the router in range (default TEP-WiFi) - the router the cable goes to is the same one
  WIFIPASS  its password (default 12345678; for a sketch that uses Wi-Fi instead of the cable)
  MONITOR   YES = the built-in serial monitor on TXD / RXD
  BAUD      the monitor's speed (115200 by default, or AUTO)
  AUTOOPEN  YES = the monitor window opens at Run (the demos: YES)
  TIME      the clock NTP gives the sketch: PC (the PC's clock) or a fixed start time YYYY-MM-DD HH:MM:SS in UTC
Every run starts again from the properties. With DHCP the address follows the board's number: U1 192.168.1.101, U2
.102 ... - give every network part its own number. The laptop is 192.168.1.21, the phone 192.168.1.41.

LINKS.INI (OPTIONAL)
The Help page cards open web pages. To point them somewhere else without a new DLL, put a text file named links.ini
next to TEPNET.DLL with lines KEY=URL, for example:
  ARTICLE=https://www.theengineeringprojects.com/...
Keys: WEBSITE, FORUM, BUG_REPORT, FEATURE_REQUEST, ARTICLE, USER_GUIDE, UPDATE_CHECK, DONATE. Only http:// and
https:// links are used; lines starting with # are comments.

TROUBLESHOOTING
* ETH.begin() returns false: read Proteus's simulation log (it names the reason) - with the board WT32-ETH01 (TEP
  Proteus) the defaults are right; your own ETH_PHY_ADDR, ETH_PHY_MDC, ETH_PHY_MDIO or ETH_PHY_POWER must be 1, 23,
  18 and 16. (ETH.h needs TEP Boards for Proteus 1.14.0 or newer; the WT32-ETH01 board needs 1.15.0.)
* No events at all: the handler must be added with WiFi.onEvent() / Network.onEvent() before ETH.begin(), and the
  sketch must return from loop() or call delay() now and then (the events run there).
* The page never opens: the cable is out (the panel shows CABLE OUT) or the board is not on the LAN yet.
* The laptop's terminal does not connect: press Connect after the board is on the LAN (the address 192.168.1.50,
  port 5000).
* WiFi.begin() is ignored: in this model a board uses one network at a time - the cable (ETH) or Wi-Fi.
* A paused simulation shows the SIMULATION LOG: click the Schematic Capture tab.
* No panel: click the PANEL pad, or turn "Open the panel at Run" back on (Settings).

BUG REPORTS AND FEATURE REQUESTS
Please post them in our forum with a screenshot, the serial monitor text, the simulation log and the Copy diagnostics
text of the panel:
  https://www.theengineeringprojects.com/forum/category/wt32-eth01-proteus-library

SUPPORT US
This library is free. If it saves you time, please support our work:
  https://www.theengineeringprojects.com/donate

WEBSITE
  https://www.theengineeringprojects.com/

LICENCES AND THIRD-PARTY NOTES
* The WT32-ETH01 model, the other boards, the Laptop / Mobile WiFi Monitors and the network (TEPNET.DLL), the symbols
  and artwork (TEPWT32ETH01.LIB, TEPLAPTOP.LIB, TEPMOBILE.LIB) are made by The Engineering Projects. The board runs
  the sketch on Proteus's own ATmega2560 model (Labcenter); R1, R2, D1 and D2 are Proteus's own parts. The models use
  only standard Windows libraries; no Visual C++ redistributable is needed. The C++ source code of the models is not
  included.
* TEP Boards for Proteus (Arduino Code): its core, the EEPROM, SPI and Wire libraries and the variants are modified
  copies of the Arduino AVR core 1.8.6 (https://github.com/arduino/ArduinoCore-avr/tree/1.8.6, GNU Lesser General
  Public License 2.1, LICENSE-LGPL-2.1.txt); its ETH, WiFi, WebServer, ESPmDNS and the other libraries are ours (MIT,
  LICENSE-MIT.txt). WT32_ETH_Relay_Controller.hex contains that core with the ETH, WiFi, WebServer and ESPmDNS
  libraries.
* Proteus is a product of Labcenter Electronics and is not included. WT32-ETH01 and WT32-S1 are names of Shenzhen
  Wireless-Tag Technology; LAN8720 and Microchip of Microchip Technology; ESP32 of Espressif Systems; HanRun of
  Zhongshan HanRun Electronic. This library is not made or endorsed by Wireless-Tag, Microchip, Espressif or
  Labcenter.

REBUILDING THE FIRMWARE (OPTIONAL)
The HEX file is supplied; the Arduino IDE is not needed to run the demos. Open the sketch in Arduino Code with Tools >
Board > TEP Boards for Proteus > WT32-ETH01 (TEP Proteus), then Sketch > Export Compiled Binary (Ctrl+Alt+S).
Flash / RAM: WT32_ETH_Relay_Controller 23,958 / 2,571 bytes (of the hidden ATmega2560's 253,952 / 8,192). Put the
exported HEX in place of the simulation's .hex. It is not a real ESP32 binary: the board in Proteus is NOT a real
ESP32 chip (no Xtensa model in Proteus) - the sketch runs on a hidden ATmega2560 at 16 MHz with 8 KB of RAM, int is
16 bits, and there are no FreeRTOS tasks.

MODEL SCOPE AND LIMITS
Modelled: the board's LAN8720A between the ESP32's Ethernet MAC and the router's LAN - ETH.begin() checking the PHY
address, MDC / MDIO and the oscillator's enable (ETH_PHY_POWER 16); the PHY's link (the cable, 1.2 s of
auto-negotiation, 100 Mbit/s full duplex); DHCP or ETH.config(); the ETH events; the jack's LINK / ACT and speed LEDs,
the PWR LED and the cable; the header GPIOs, the ADC and touch pins, Serial and Serial2, EN; TCP and UDP of the
ESP32's sockets with the router, the phone, the laptop and the internet host shared with every TEP network part. Not
modelled: the RMII frames bit by bit and the 50 MHz clock, the MDIO bus waveform, 10 Mbit/s or half duplex links,
IPv6, Bluetooth, the download mode on IO0 (the HEX is loaded by Proteus), the LINK pin's output. The model's own
choices: the cable goes to the same router as the Wi-Fi parts; with the cable out the connections are kept for 20 s;
the board uses the cable or Wi-Fi, not both; the simulation runs below real time.

VERSION
TEP WT32-ETH01 library V1.0 (Oct 2026). Device WT32-ETH01 (TEPWT32ETH01.LIB / TEPNET.DLL, which also runs our
LAN8720 Ethernet Module, the ESP32, ESP8266, Arduino and Pico W boards, our Ethernet and Wi-Fi shields, modules and
breakouts, the ESP-01 family and the Laptop / Mobile WiFi Monitors), with the Laptop WiFi Monitor / Mobile WiFi
Monitor (TEPLAPTOP.LIB / TEPMOBILE.LIB); TEP Boards for Proteus 1.15.0. Demo sketch WT32_ETH_Relay_Controller V1.0.