Project Files of Arduino Nano 33 IoT Library for Proteus: WiFiNINA UDP Simulation

ARDUINO NANO 33 IOT LIBRARY FOR PROTEUS - V1.0 (YOUR NANO 33 IOT SKETCH, WIFININA, UDP, 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/arduino-nano-33-iot-library-for-proteus.html
Report a bug or suggest a feature (our forum):
  https://www.theengineeringprojects.com/forum/category/arduino-nano-33-iot-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 NINA-W102 module and WiFiNINA on an UNO-size board, our Arduino UNO WiFi Rev2:
  https://www.theengineeringprojects.com/2026/10/arduino-uno-wifi-rev2-library-for-proteus.html
Support us (the libraries are free):
  https://www.theengineeringprojects.com/donate

FILE STRUCTURE
Arduino-Nano-33-IoT-TEP-v1.0/
|-- Proteus Library Files/
|   |-- 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
|   |-- TEPNANO33IOT.LIB                                           26.8 KB   the Arduino Nano 33 IoT board, to LIBRARY
|-- Proteus Model Files/
|   |-- TEPNET.DLL                                                 1.89 MB   the boards + the Wi-Fi network, to MODELS
|-- Proteus Simulation/
|   |-- Arduino-Nano-33-IoT-Board.pdsprj                           14.9 KB   demo 1: the board alone
|   |-- Nano33IoT_UDP_Remote.hex                                   46.8 KB   U1 of both demos
|   |-- Nano-33-IoT-UDP-Remote-with-Laptop-and-Mobile.pdsprj       22.2 KB   demo 2: UDP remote + laptop + phone
|   |-- TEPNET.DLL                                                 1.89 MB   copy of the model
|-- Arduino Code/
|   |-- Nano33IoT_UDP_Remote/Nano33IoT_UDP_Remote.ino               6.3 KB   the Nano 33 IoT sketch
|   |-- TEP Boards for Proteus/hardware/tep/avr/                  570.6 KB   the Arduino IDE add-on 1.12.0 (145 files)
|-- README.txt                                                    ~19.9 KB   this file
Total: 4.53 MB (unzipped). The C++ source code of the models is not included.

WHAT IS IT?
Proteus 8 has no Microchip SAMD21 (Arm Cortex-M0+) model and no ESP32 (the heart of the u-blox NINA-W102 Wi-Fi module), so this is
NOT a real SAMD21. It is the Arduino Nano 33 IoT - the Nano's size and 2 x 15 pins, the SAMD21 and the NINA-W102 Wi-Fi module -
that runs YOUR Nano 33 IoT sketch in Proteus:
  * You write a normal Nano 33 IoT sketch (D0 .. D13, A0 .. A7, LED_BUILTIN, Serial, Serial1, Wire, SPI, WiFiNINA with WiFi.begin,
    WiFi.getTime, WiFi.ping, WiFiServer, WiFiClient, WiFiUDP, analogRead 0-1023 ...) and compile it in the Arduino IDE with our
    board package "TEP Boards for Proteus" 1.12.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
    Nano's pins, 3.3 V logic, A0 .. A7 (0 .. 1023 for 0 .. 3.3 V), the RESET button, the L LED on D13, the ON LED, the built-in
    serial monitor on the USB (Serial) and the Wi-Fi radio (the NINA-W102's job on the real board).
  * 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, RSSI, NTP time (WiFi.getTime), ping, TCP and UDP (broadcasts too) 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 and
    ping.
The board is drawn our way at its real proportions (the Nano's 45 x 18 mm, Arduino teal), lying with micro-USB on the left:
RESET, the SAMD21, the ON and L LEDs, the PANEL pad and the NINA-W102 with its antenna at the right end; the rows D12 .. D2, GND,
RST, RX0, TX1 (top) and D13, 3.3V, AREF, A0 .. A7, +5V, RST, GND, VIN (bottom).
TEP additions: the antenna changes colour (gold not joined, green on Wi-Fi, orange sending, cyan receiving), the PANEL pad (or
the NINA-W102) opens the board's panel, the micro-USB opens the serial monitor.
Limits (say them before you start): 16 MHz, 8 KB of RAM (the real SAMD21: 48 MHz, 32 KB), int is 16 bits (the real board: 32 bits
- use long / int32_t for big numbers), no FreeRTOS tasks, no Bluetooth, no IMU (the real board's LSM6DS3 is not drawn and not
modelled), no real TLS, no soft AP. See MODEL SCOPE AND LIMITS.

ONE DEVICE (search "NANO 33" in Pick Devices):
  ARDUINO NANO 33 IOT  "Arduino Nano 33 IoT" V1.0 (category Microprocessor ICs > Arduino Wi-Fi 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 NANO 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 22 pins live (HIGH, LOW, PWM with its duty, interrupt, input, pull-up) and A0 .. A7 with their voltage
    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 ON
  and L LEDs, the RESET button and every pin). Like every TEP window it has no Windows title bar - only our header.
The same TEPNET.DLL also runs our Arduino UNO WiFi Rev2, UNO R4 WiFi and Nano ESP32, the WeMos and NodeMCU boards, 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 24 Oct 2026 (the two demo projects as shipped, the window off-screen, posted clicks and keys).
What the runs showed:
  * The monitor printed "Connecting to TEP-WiFi"; L stayed off, the board joined TEP-WiFi in 2.18 s (IP 192.168.1.101, MAC
    D4:CA:6E:02:00:01) and started UDP on port 4210.
  * The laptop (192.168.1.21, UDPPORT 4210) received the heartbeat every 5 s: "Nano 33 IoT #2: LED OFF, RSSI -46 dBm, 0
    commands, last: none".
  * From the laptop's UDP terminal (sent to 192.168.1.255:4210): LED ON lit L and came back as "OK LED ON"; BLINK 3 blinked L
    three times ("OK BLINK 3"); STATUS answered "LED ON, RSSI -47 dBm, 2 commands, last: BLINK 3 from 192.168.1.21".
  * The phone (192.168.1.41) opened the page (HTTP 200, 359 bytes); LED OFF turned L off.
  * In the monitor: LED ON ("OK LED ON"), STATUS ("LED ON, RSSI -45 dBm, 4 commands, last: LED ON from monitor") and HELP.
  * 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). TEPNANO33IOT.LIB is the Nano 33 IoT; 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 Nano 33 IoT).
4. Delete TEPNANO33IOT.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).
   WiFiNINA is inside the package - nothing else to install.
   Tools > Board > TEP Boards for Proteus > Arduino Nano 33 IoT (TEP Proteus).
6. Start Proteus. In Pick Devices (P) search "NANO 33".

RUN THE DEMOS
Keep the .hex file and TEPNET.DLL beside the projects in "Proteus Simulation".
1. Arduino-Nano-33-IoT-Board.pdsprj - the board alone (Nano33IoT_UDP_Remote.hex): press Run. The monitor and the panel open (move
   them aside). Type LED ON, BLINK 3, STATUS or HELP in the monitor; the panel's phone (OPEN NANO PAGE) shows the page with the
   LED buttons.
2. Nano-33-IoT-UDP-Remote-with-Laptop-and-Mobile.pdsprj - U1 the Nano 33 IoT (Nano33IoT_UDP_Remote.hex); PC1 the Laptop WiFi
   Monitor (UDP on port 4210 - the UDPPORT property) and MOB1 the Mobile WiFi Monitor (home page http://192.168.1.101/) - no
   wires, they are on TEP-WiFi.
   Press Run. On the laptop: Terminal > UDP shows the heartbeat every 5 s; type LED ON, LED OFF, BLINK 3 or STATUS and press
   Enter - it goes to 192.168.1.255:4210 (every device on port 4210), and the board answers to the laptop. On the phone: Browser >
   Go opens the page - tap LED ON, LED OFF or BLINK.
Closed a window? The micro-USB of the board opens the monitor, the PANEL pad the panel.

PINS (the label on the board, what it can do in the simulation)
  RX0 / TX1          D0 / D1: Serial1 (as on the Nano 33 IoT), GPIO, interrupt
  D2 .. D13          GPIO, interrupt; analogWrite on 2, 3, 5, 6, 9 .. 12 (and A2, A3, A5) as on the real board; D13 lights L
  D10 .. D13         also SPI SS / MOSI / MISO / SCK
  A0 .. A7           analogRead: 0 .. 1023 for 0 .. 3.3 V (analogRead(0) is A0 too); also GPIO; A4 / A5 = Wire SDA / SCL
  3.3V / +5V         3.3 V (the board's logic) and 5 V (the USB's, as the real board's +5V pad)
  GND, RST           ground; reset (LOW holds the board in reset; the RESET button does the same)
  AREF, VIN          drawn, not modelled
Serial is the USB (the board's monitor), not D0 / D1 - Serial1 on D0 / D1, as on the real Nano 33 IoT. The pins are 3.3 V logic.

WIFININA (WiFiNINA.h, the same as on our UNO WiFi Rev2)
  WiFi.begin(ssid, pass)      waits until the board has joined or failed (about 10 s at most) and returns the status
  WiFi.status()               WL_CONNECTED, WL_NO_MODULE (no board model), WL_CONNECT_FAILED ...
  WiFi.firmwareVersion()      "1.5.0" (= WIFI_FIRMWARE_LATEST_VERSION)
  WiFi.getTime()              Unix time in UTC from NTP; 0 until the board has the time
  WiFi.ping(host)             the round trip in ms; WL_PING_UNKNOWN_HOST, WL_PING_TIMEOUT (after 5 s), WL_PING_ERROR
  WiFiUDP                     begin(port), parsePacket, read, remoteIP / remotePort, beginPacket / print / endPacket; broadcasts
                              to x.x.x.255 reach every TEP device listening on that port
  WiFiServer, WiFiClient, WiFiSSLClient (no real TLS: https reaches the virtual internet host without encryption)
Not in V1.0: the soft AP (WiFi.beginAP), WPA2 Enterprise, the NINA's own pins (WiFiDrv), Bluetooth (ArduinoBLE).

THE DEMO SKETCH (Arduino Code)
  Nano33IoT_UDP_Remote  WiFiNINA + WiFiUDP: WiFi.begin() in a loop; a WiFiUDP on port 4210: each packet is a command (LED ON,
                        LED OFF, BLINK <n>, STATUS) and the answer goes back to the sender's address and port; a heartbeat to the
                        laptop 192.168.1.21:4210 every 5 s; a WiFiServer on port 80 that reads the request line itself: / the
                        page, /led?on, /led?off, /blink; the same commands from the serial monitor (and HELP).

PROPERTIES (double-click the board > Edit Properties)
  PROGRAM   the sketch's HEX (Arduino IDE: Sketch > Export Compiled Binary with the board Arduino Nano 33 IoT (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 the USB (Serial)
  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. One Nano 33 IoT per design: its USB serial pins are hidden pins, and Proteus joins hidden pins
of the same name across parts.

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
  Arduino Nano 33 IoT (TEP Proteus) and export the binary again.
* "WiFiNINA.h: No such file": an older add-on is installed - 1.12.0 is the first with the Nano 33 IoT.
* The compile fails inside Arduino's own WiFiNINA (its SPI / nina driver files): the IDE took the copy in
  Documents\Arduino\libraries - move that folder out while you compile for Proteus (keep it for real boards).
* The board gets no UDP from the laptop: the laptop sends to the port in its "Send to" box (4210 by default) - the sketch must
  listen there (udp.begin(4210)); the laptop's UDPPORT must be on (not 0).
* The laptop sees no heartbeat: its UDPPORT must be the port the sketch sends to (4210), and the laptop must be on Wi-Fi.
* 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.
* An integer goes wrong above 32767: int is 16 bits on the hidden AVR (32 on the real SAMD21) - 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/arduino-nano-33-iot-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 (TEPNANO33IOT.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,
  WiFiNINA, WiFiS3, Arduino_LED_Matrix, WebServer, HTTPClient, ESPmDNS, ESP8266WiFi, ESP8266WebServer, ESP8266HTTPClient,
  ESP8266mDNS, Preferences, ESP32Servo and Servo libraries and our core files are MIT (LICENSE-MIT.txt). The API follows
  Arduino's WiFiNINA library (names only - no Arduino, Microchip, u-blox or Espressif code).
* Proteus is a product of Labcenter Electronics and is not included. Arduino and Nano are trademarks of Arduino SA, SAMD21 a name
  of Microchip Technology, NINA-W102 of u-blox, LSM6DS3 of STMicroelectronics. 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\Nano33IoT_UDP_Remote, select Arduino Nano 33 IoT (TEP Proteus) and use Sketch > Export Compiled Binary.
Flash / RAM: Nano33IoT_UDP_Remote 17,042 / 2,211 bytes.
Put the exported HEX in place of the simulation's .hex. For a real Nano 33 IoT select "Arduino NANO 33 IoT" of the Arduino SAMD
Boards package, install Arduino's WiFiNINA library and upload as usual - the same sketch, no change.

MODEL SCOPE AND LIMITS
Modelled: the Nano 33 IoT's header pins on a hidden ATmega2560 (Proteus's AVR model, 16 MHz, 3.3 V); digital I/O,
analogRead(A0 .. A7) 0-1023 for 0-3.3 V (the board model reads the pin's voltage), PWM (analogWrite) and attachInterrupt on any
pin through the board model; the RESET button, the L LED on D13, the ON LED; Serial (the USB, the board's monitor), Serial1 on
D0 / D1, Wire on A4 / A5 and SPI on D10 .. D13 (the AVR's hardware), EEPROM; Wi-Fi station mode (WiFiNINA: begin waits for the
join, status, scan, RSSI, getTime, ping, disconnect, re-join), DHCP addresses, TCP client and server, UDP with broadcasts, NTP
time, the virtual internet host; the other TEP Wi-Fi parts on the same network.
Not modelled: the SAMD21 itself (Arm Cortex-M0+, 48 MHz, 32 KB of RAM, 32-bit int, its DAC on A0, its own peripherals), the
NINA-W102 as a processor and its firmware updates, the LSM6DS3 IMU, the crypto chip, Bluetooth, real TLS. 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; 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 Arduino Nano 33 IoT library V1.0 (Oct 2026). Device ARDUINO NANO 33 IOT (TEPNANO33IOT.LIB / TEPNET.DLL, which also runs our
Arduino UNO WiFi Rev2, UNO R4 WiFi and Nano ESP32, the WeMos and NodeMCU boards, 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.12.0 (adds the Nano 33
IoT).
Demo sketch Nano33IoT_UDP_Remote V1.0 (a UDP heartbeat to the laptop, LED commands by UDP, the page and the monitor).
Demo tools: LAPTOP WIFI MONITOR and MOBILE WIFI MONITOR (TEP Laptop / Mobile WiFi Monitor libraries V1.0).