Project Files of WeMos D1 R2 Library for Proteus: ESP8266 Wi-Fi Simulation

WEMOS D1 R2 LIBRARY FOR PROTEUS - V1.0 (ESP8266 IN THE UNO SIZE, WI-FI SCANNER, SIGNAL METER, LAPTOP + PHONE)
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/wemos-d1-r2-library-for-proteus.html
Report a bug or suggest a feature (our forum):
  https://www.theengineeringprojects.com/forum/category/wemos-d1-r2-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 other ESP8266 boards on the same board package, our WeMos D1 Mini and NodeMCU ESP8266 V3:
  https://www.theengineeringprojects.com/2026/10/wemos-d1-mini-library-for-proteus.html
  https://www.theengineeringprojects.com/2026/10/nodemcu-esp8266-v3-library-for-proteus-v2-0.html
Support us (the libraries are free):
  https://www.theengineeringprojects.com/donate

FILE STRUCTURE
WeMos-D1-R2-TEP-v1.0/
|-- Proteus Library Files/
|   |-- TEPD1R2.LIB                                            34.7 KB   the WeMos D1 R2 board, to LIBRARY
|   |-- TEPLAPTOP.LIB                                          39.5 KB   our Laptop WiFi Monitor (the demo), to LIBRARY
|   |-- TEPMOBILE.LIB                                          13.1 KB   our Mobile WiFi Monitor (the demo), to LIBRARY
|-- Proteus Model Files/
|   |-- TEPNET.DLL                                             1.88 MB   the boards + the Wi-Fi network, to MODELS
|-- Proteus Simulation/
|   |-- D1R2_WiFi_Scanner.hex                                  64.3 KB   U1 of both demos
|   |-- D1-R2-WiFi-Scanner-with-Laptop-and-Mobile.pdsprj       24.5 KB   demo 2: scanner + signal bars + laptop + phone
|   |-- TEPNET.DLL                                             1.88 MB   copy of the model
|   |-- WeMos-D1-R2-Board.pdsprj                               16.1 KB   demo 1: the board alone
|-- Arduino Code/
|   |-- D1R2_WiFi_Scanner/D1R2_WiFi_Scanner.ino                 8.2 KB   the D1 R2 sketch
|   |-- TEP Boards for Proteus/hardware/tep/avr/              529.1 KB   the Arduino IDE add-on 1.8.0 (134 files)
|-- README.txt                                                ~20.7 KB   this file
Total: 4.50 MB (unzipped). The C++ source code of the models is not included.

WHAT IS IT?
Proteus 8 has no ESP8266 processor model (the ESP8266's Tensilica L106 core is not in Proteus), so this is NOT a
real ESP8266 chip. It is the WeMos D1 R2 - the ESP-12F module and the CH340 USB chip on a board with the Arduino
UNO's size, shape and headers - that runs YOUR ESP8266 Arduino sketch in Proteus:
  * You write a normal ESP8266 sketch (D0 .. D15, A0, LED_BUILTIN, ESP8266WiFi with scanNetworks and RSSI,
    ESP8266WebServer, ESP8266mDNS, ESP8266HTTPClient, WiFiClient, WiFiServer, WiFiUDP, EEPROM, configTime and
    time(), analogRead 0-1023 ...) and compile it in the Arduino IDE with our board package "TEP Boards for Proteus"
    1.8.0 (in Arduino Code - see INSTALLATION).
  * Inside the board, Proteus's own ATmega2560 model runs the compiled sketch at 16 MHz; our model (TEPNET.DLL)
    wraps it: the D1 R2's UNO-style headers with their GPIO numbers, A0 (0 .. 1023 for 0 .. 3.2 V, the board's
    divider), the RESET button, the ESP-12F's blue LED on GPIO2 (D9, lit when LOW), a red PWR LED, the built-in
    serial monitor and the Wi-Fi radio. The real D1 R2 has no FLASH button, and neither has ours (D8 = GPIO0 is a
    plain pin).
  * Wi-Fi: a virtual router (TEP-WiFi, password 12345678 - the WIFISSID / WIFIPASS properties) with DHCP
    (192.168.1.101 for U1, .102 for U2 ...), a scan list (TEP-WiFi and two neighbours), RSSI, mDNS names
    (meter.local), NTP time, TCP and UDP between all the TEP Wi-Fi parts in the design (boards, modules, the Laptop
    and Mobile WiFi Monitors), and a virtual internet host that answers HTTP.
The board is drawn our way at its real proportions (the UNO's 68.6 x 53.3 mm outline with its step, blue), seen from
above as the UNO: the micro-USB and the DC jack on the left, RESET in the top-left corner, the CH340G, the MP2307
regulator, the PANEL pad and the ESP-12F with its blue LED (D9) and its PCB antenna on the right; the digital header
along the top (D15/SCL D14/SDA NC GND D13/SCK D12/MISO D11/MOSI D10/SS D9 D8 | D7 D6 D5 D4 D3 D2 TX D1 RX D0), the
power and analog headers along the bottom (NC IOREF RST 3V3 5V GND GND VIN | A0 and five NC pins).
TEP additions: the antenna changes colour (gold not joined, green on Wi-Fi, orange sending, cyan receiving), the red
PWR LED, the PANEL pad (or the ESP-12F) opens the board's panel, the micro-USB opens the serial monitor.
Limits (say them before you start): 16 MHz, 8 KB of RAM, 256 KB of flash, int is 16 bits (use long / int32_t for
big numbers), no FreeRTOS tasks, no Bluetooth, no SPIFFS / LittleFS, no OTA, no real TLS, no soft AP. See MODEL
SCOPE AND LIMITS.

ONE DEVICE (search "D1 R2" in Pick Devices):
  WEMOS D1 R2  "WeMos D1 R2" V1.0 (category Microprocessor ICs > ESP8266 Boards), prefix U, model TEPNET.DLL
  The panel (a TEP pop-up window, the look of the TEP Serial Monitor; it opens at Run, the PANEL pad opens it
  again). Tabs:
    Wi-Fi     a phone with three tabs - BROWSER (OPEN D1 R2 PAGE: the phone opens the sketch's web page, tap its
              links), ROUTER (the DHCP list of every board and phone), CLOUD (the internet host's requests); WI-FI
              SIGNAL GOOD / WEAK / OUT OF RANGE; the cards BOARD, WI-FI, TRAFFIC
    Pins      the 12 GPIOs live (HIGH, LOW, PWM with its duty, interrupt, input, pull-up) and A0 with its voltage
              and its 0-1023 reading
    Test      Web request test (the phone opens the page n times - measured) and Wi-Fi re-join test
    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) has its own window with Monitor, Plotter and Board tabs (the Board tab
  shows the PWR and D9 LEDs, the RESET button and every pin).
The same TEPNET.DLL also runs our WeMos D1 Mini, NodeMCU ESP8266 V3 and V2, the ESP32 boards, the ESP-01 / ESP-07 /
ESP-12 modules, the AirLift and WiFi shields 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 (the two demo projects as shipped, the window off-screen, posted clicks
and keys).
What the runs showed:
  * At the start the sketch scanned: "Scan: 3 networks" - TEP-WiFi -46 dBm (channel 6, WPA2, 100 %),
    Neighbour_WiFi -79 dBm (42 %) and Guest_Network -88 dBm (open, 24 %).
  * The D9 LED blinked while the board joined, then stayed on: joined TEP-WiFi in 2.2 s (IP 192.168.1.101, MAC
    84:F3:EB:02:00:01, mDNS meter.local); "Signal GOOD: -45 dBm, 100 % - BAR 1 ON, BAR 2 ON" - both LEDs lit.
  * The laptop (192.168.1.21) opened http://192.168.1.101/api (HTTP 200, 327 bytes of JSON: the SSID, the RSSI,
    the quality, the level and the three networks); the phone (192.168.1.41) opened http://meter.local/.
  * The panel's WI-FI SIGNAL WEAK: "Signal WEAK: -80 dBm, 40 % - BAR 1 ON, BAR 2 OFF" - only BAR 1 stayed on.
  * OUT OF RANGE: "Wi-Fi lost - searching", both bars off, the D9 LED blinking; SCAN found only the two neighbours
    and STATUS answered "Not on Wi-Fi: searching for TEP-WiFi".
  * GOOD again: the board joined again on its next try (every 15 s), both bars came back on.
  * Speed: about 0.4 x real time with the two monitors.

INSTALLATION (about 3 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). TEPD1R2.LIB is the D1 R2; TEPLAPTOP.LIB and TEPMOBILE.LIB are our Laptop WiFi
   Monitor and Mobile WiFi Monitor (the demo's tools).
3. Copy TEPNET.DLL from "Proteus Model Files" to the MODELS folder (...\Proteus 8 Professional\MODELS) - replace an
   older TEPNET.DLL (this one is the first that knows the D1 R2).
4. Delete TEPD1R2.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): copy the folder
   "Arduino Code\TEP Boards for Proteus\hardware" into your sketchbook folder (normally Documents\Arduino), so that
   Documents\Arduino\hardware\tep\avr\boards.txt exists (replace an older copy); restart the IDE. The Arduino AVR
   Boards platform must be installed (it comes with IDE 1.8.x; in IDE 2.x install "Arduino AVR Boards" from the
   Boards Manager once). The ESP8266 libraries of the sketch (ESP8266WiFi, ESP8266WebServer, ESP8266mDNS) are inside
   the package - nothing else to install.
   Tools > Board > TEP Boards for Proteus > WeMos D1 R2 (TEP Proteus).
6. Start Proteus. In Pick Devices (P) search "D1 R2".

RUN THE DEMOS
Keep the .hex file and TEPNET.DLL beside the projects in "Proteus Simulation".
1. WeMos-D1-R2-Board.pdsprj - the board alone (D1R2_WiFi_Scanner.hex): press Run. The monitor and the panel open
   (move them aside); the scan table appears, D9 blinks while the board joins, then stays on. Type SCAN, STATUS or
   HELP in the monitor; the panel's phone (OPEN D1 R2 PAGE) shows the scanner page. (There are no bar LEDs here:
   watch the Pins tab, D5 and D6 go HIGH.)
2. D1-R2-WiFi-Scanner-with-Laptop-and-Mobile.pdsprj - U1 the D1 R2 (D1R2_WiFi_Scanner.hex) with the two signal bars:
   D5 - R1 (220R) - the green LED D1 (BAR 1) - ground and D6 - R2 (220R) - the green LED D2 (BAR 2) - ground; PC1 the
   Laptop WiFi Monitor (home page http://192.168.1.101/api) and MOB1 the Mobile WiFi Monitor (home page
   http://meter.local/) - no wires, they are on TEP-WiFi.
   Press Run. On the laptop: Browser > Go reads the JSON API; on the phone: Browser > Go opens the scanner page (SCAN
   AGAIN, JSON, REFRESH). On the board's panel, WI-FI SIGNAL WEAK leaves only BAR 1 on, OUT OF RANGE turns both bars
   off (D9 blinks while the board searches), GOOD brings them back.
Closed a window? The micro-USB of the board opens the monitor, the PANEL pad the panel.

PINS (the label on the board, the GPIO, what it can do in the simulation)
  D0 (RX) / D1 (TX)  GPIO3 / 1: Serial (the micro-USB, the board's monitor)
  D2                 GPIO16: digital I/O only (no PWM, no interrupt)
  D3 / D15 (SCL)     GPIO5: Wire SCL, GPIO, PWM, interrupt (the same pin twice, one net)
  D4 / D14 (SDA)     GPIO4: Wire SDA, GPIO, PWM, interrupt (the same pin twice, one net)
  D5 / D13 (SCK)     GPIO14: SPI SCK, GPIO, PWM, interrupt (D5 is BAR 1 in the demo)
  D6 / D12 (MISO)    GPIO12: SPI MISO, GPIO, PWM, interrupt (D6 is BAR 2 in the demo)
  D7 / D11 (MOSI)    GPIO13: SPI MOSI, GPIO, PWM, interrupt
  D8                 GPIO0: GPIO with a 10k pull-up (the ESP8266's boot pin; no button on the D1 R2)
  D9                 GPIO2: the ESP-12F's blue LED (lit when LOW, LED_BUILTIN), Serial1 TX, GPIO with a pull-up
  D10 (SS)           GPIO15: SPI SS, GPIO, PWM, interrupt
  A0                 analogRead(A0): 0 .. 1023 for 0 .. 3.2 V (the board's 220k / 100k divider)
  3V3 / IOREF        3.3 V (IOREF shows the 3.3 V logic level, as on the real board)
  5V / GND           5 V (USB), ground
  RST                reset (LOW holds the ESP8266 in reset; the RESET button does the same)
  VIN / NC           the DC jack's input and the unused pins: drawn, not modelled
analogWrite works on every output GPIO but D2 (analogWriteRange 255 and analogWriteFreq 1 kHz by default, as the
ESP8266 core 3.x); attachInterrupt on every GPIO but D2. The pins are 3.3 V logic (not 5 V like the UNO's).

THE DEMO SKETCH (Arduino Code)
  D1R2_WiFi_Scanner     ESP8266WiFi + ESP8266WebServer + ESP8266mDNS: at the start WiFi.scanNetworks() prints every
                        network in range (SSID, RSSI, channel, security, quality); joins TEP-WiFi as "meter" (D9
                        blinks, then stays on); the signal meter: BAR 1 (D5) lights from -85 dBm, BAR 2 (D6) from
                        -67 dBm, with a line in the monitor when the level changes (GOOD, FAIR, WEAK, VERY WEAK, NO
                        WI-FI); the page / with the signal and the last scan, /scan to scan again, /api with the same
                        in JSON; when the router is out of range it keeps running, blinks D9 and tries again every 15 s;
                        SCAN, STATUS and HELP in the serial monitor.

PROPERTIES (double-click the board > Edit Properties)
  PROGRAM   the sketch's HEX (Arduino IDE: Sketch > Export Compiled Binary with the board WeMos D1 R2 (TEP Proteus))
  WIFISSID  the router in range (default TEP-WiFi)
  WIFIPASS  its password (default 12345678); a sketch with another name or password gets WL_NO_SSID_AVAIL /
            WL_CONNECT_FAILED, as on the bench
  MONITOR   YES = the built-in serial monitor on TX / RX
  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. The IP address follows the part's number: U1 192.168.1.101, U2 .102 ...
- give every Wi-Fi part its own number.

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
* Nothing happens at Run / "the sketch's core is link version ...": the HEX was not built with TEP Boards for
  Proteus - select WeMos D1 R2 (TEP Proteus) and export the binary again.
* "D15 was not declared": an older add-on is installed - 1.8.0 is the first with the D1 R2 and its D0 .. D15 names.
* The board stays on "Connecting to TEP-WiFi .....": the sketch's SSID / password differ from the WIFISSID /
  WIFIPASS properties, or the panel's WI-FI SIGNAL is OUT OF RANGE.
* A bar does not light: D5 (or D6) - 220R - LED anode, the LED's cathode to ground; the bar lights when its pin is
  HIGH. Check the WI-FI SIGNAL buttons: WEAK leaves only BAR 1 on.
* A sketch written for the D1 Mini uses the wrong pins: the names differ (the D1 Mini's D4 is GPIO2, the D1 R2's D4
  is GPIO4). Use the GPIO numbers, or the names of the board you selected.
* An integer goes wrong above 32767: int is 16 bits on the hidden AVR - use long.
* No monitor window: click the micro-USB; 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/wemos-d1-r2-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 board model and the Wi-Fi network (TEPNET.DLL), the symbols and artwork (TEPD1R2.LIB, TEPLAPTOP.LIB,
  TEPMOBILE.LIB) are made by The Engineering Projects. The board's processor is Proteus's own ATmega2560 model
  (Labcenter's AVR model). The model uses 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\TEP Boards for Proteus): its core (cores\tep32), the variants and the EEPROM,
  SPI and Wire libraries are modified copies of the Arduino AVR core 1.8.6 - GNU Lesser General Public License 2.1
  (the licence text is included: LICENSE-LGPL-2.1.txt; the original source:
  https://github.com/arduino/ArduinoCore-avr/tree/1.8.6). Its WiFi, WebServer, HTTPClient, ESPmDNS, ESP8266WiFi,
  ESP8266WebServer, ESP8266HTTPClient, ESP8266mDNS, Preferences, ESP32Servo and Servo libraries and our core files
  are MIT (LICENSE-MIT.txt). The API follows the ESP8266 Arduino core and the Arduino-ESP32 core (names only - no
  Espressif or ESP8266 community code).
* Proteus is a product of Labcenter Electronics and is not included. WeMos and LOLIN are names of WEMOS Electronics,
  ESP8266 and ESP-12F names of Espressif Systems (the module by Ai-Thinker), CH340 of WCH, Arduino and UNO trademarks
  of Arduino SA. This library is not made or endorsed by them or by Labcenter.

REBUILDING THE FIRMWARE (OPTIONAL)
The HEX file is supplied; the Arduino IDE is not needed to run the demos. Install TEP Boards for Proteus
(INSTALLATION step 5), open Arduino Code\D1R2_WiFi_Scanner, select WeMos D1 R2 (TEP Proteus) and use
Sketch > Export Compiled Binary. Flash / RAM: D1R2_WiFi_Scanner 23,404 / 2,842 bytes.
Put the exported HEX in place of the simulation's .hex. For a real D1 R2 select "LOLIN(WEMOS) D1 R1" of the ESP8266
core (the D1 R2's pin names) and upload as usual - the same sketch, no change.

MODEL SCOPE AND LIMITS
Modelled: the D1 R2's header pins with the ESP8266's GPIO numbers on a hidden ATmega2560 (Proteus's AVR model,
16 MHz); digital I/O, analogRead(A0) 0-1023 for 0-3.2 V (the board model reads the pin's voltage), PWM (analogWrite
with analogWriteRange / analogWriteFreq) and attachInterrupt on every GPIO but GPIO16 through the board model; the
RESET button, the blue LED on GPIO2, the PWR LED; Serial, Serial1 TX on GPIO2, Wire and SPI (the AVR's hardware),
EEPROM (EEPROM.begin / commit accepted; kept through RESET within one run); ESP.getChipId, getChipModel,
getFlashChipRealSize, getResetReason, restart, getVcc (ADC_MODE(ADC_VCC)); the clock (configTime, time(),
localtime(), getLocalTime); Wi-Fi station mode (begin, status, scanNetworks with SSID / RSSI / channel / encryption,
RSSI, hostname, disconnect, re-join), DHCP addresses, TCP client and server, HTTP client, UDP, mDNS names, NTP time,
the virtual internet host; the other TEP Wi-Fi parts on the same network.
Not modelled: the ESP8266's own processor (Tensilica L106, 80 / 160 MHz, 80 KB RAM), the CH340 and its auto-reset,
the DC jack and its MP2307 regulator (VIN), the flash file systems (SPIFFS / LittleFS), OTA updates, deep sleep
timing (the board restarts), the soft AP and WiFi events, real TLS (BearSSL), the radio's real timing. Upload over
USB is not used (Proteus loads the HEX).
The model's own choices: every board in the design sees the same router and the same two neighbour networks; the
WI-FI SIGNAL buttons set the router's RSSI (GOOD about -46 dBm, WEAK about -81 dBm, OUT OF RANGE gone); the internet
host answers HTTP on ports 80 and 443 (no certificates); the clock starts from the PC's time or the TIME property;
the simulation runs below real time.

VERSION
TEP WeMos D1 R2 library V1.0 (Oct 2026). Device WEMOS D1 R2 (TEPD1R2.LIB / TEPNET.DLL, which also runs our WeMos
D1 Mini, NodeMCU ESP8266 V3 and V2, the ESP32 boards, the ESP-01 / ESP-07 / ESP-12 modules, the AirLift and WiFi
shields and the Laptop / Mobile WiFi Monitors), TEP Boards for Proteus 1.8.0 (adds the WeMos D1 R2 with D0 .. D15).
Demo sketch D1R2_WiFi_Scanner V1.0 (the scan, the two signal bars on D5 / D6, the page at meter.local, the JSON API).
Demo tools: LAPTOP WIFI MONITOR and MOBILE WIFI MONITOR (TEP Laptop / Mobile WiFi Monitor libraries V1.0).