Project Files of Raspberry Pi 4 Model B Library for Proteus: RFID RC522, Web Server

RASPBERRY PI 4 MODEL B LIBRARY FOR PROTEUS - V1.0 (BCM2711 1.5 GHZ, 4 GB, GIGABIT ETHERNET, WI-FI, 40-PIN HEADER)
YOUR PYTHON PROGRAM RUNS ON THE BOARD - DEMO: AN RFID ATTENDANCE STATION (RC522 READER, DS3231 CLOCK, A WEB PAGE)
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/raspberry-pi-4-model-b-library-for-proteus.html
Report a bug or suggest a feature (our forum):
  https://www.theengineeringprojects.com/forum/category/raspberry-pi-4-model-b-proteus-library
The demo's parts are our libraries (included) - their articles:
  MFRC522:  https://www.theengineeringprojects.com/2026/09/mfrc522-rfid-proteus-library.html
  DS3231:   https://www.theengineeringprojects.com/2026/10/ds3231-rtc-module-library-for-proteus-v1-0.html
  Laptop:   https://www.theengineeringprojects.com/2026/10/laptop-wifi-monitor-library-for-proteus.html
  Phone:    https://www.theengineeringprojects.com/2026/10/mobile-wifi-monitor-library-for-proteus.html
The earlier boards of this series:
  https://www.theengineeringprojects.com/2026/10/raspberry-pi-model-b-library-for-proteus.html
  https://www.theengineeringprojects.com/2026/10/raspberry-pi-1-model-b-plus-library-for-proteus.html
  https://www.theengineeringprojects.com/2026/10/raspberry-pi-2-model-b-library-for-proteus.html
  https://www.theengineeringprojects.com/2026/10/raspberry-pi-3-model-b-library-for-proteus.html
  https://www.theengineeringprojects.com/2026/10/raspberry-pi-3-model-b-plus-library-for-proteus.html
  https://www.theengineeringprojects.com/2026/10/raspberry-pi-3-model-a-plus-library-for-proteus.html
Support us (the libraries are free):
  https://www.theengineeringprojects.com/donate

FILE STRUCTURE
Raspberry-Pi-4-Model-B-TEP-v1.0/
|-- Proteus Library Files/
|   |-- TEPDS3231.LIB                                    68.9 KB   the DS3231 clock (demo), to LIBRARY
|   |-- TEPLAPTOP.LIB                                    39.5 KB   the laptop (demo), to LIBRARY
|   |-- TEPMFRC522.LIB                                   92.2 KB   the RC522 reader (demo), to LIBRARY
|   |-- TEPMOBILE.LIB                                    13.1 KB   the phone (demo), to LIBRARY
|   |-- TEPRPI4B.LIB                                     60.2 KB   the Raspberry Pi 4 Model B, to LIBRARY
|-- Proteus Model Files/
|   |-- TEPDS3231.DLL                                   321.5 KB   the DS3231 clock, to MODELS
|   |-- TEPMFRC522.DLL                                  336.5 KB   the RC522 reader, to MODELS
|   |-- TEPNET.DLL                                       2.37 MB   the Pi + monitors + network, to MODELS
|   |-- TEPPi/python/                                   17.54 MB   Python 3.11.9 embeddable (33 files)
|   |-- TEPPi/runtime/                                  856.3 KB   TEP Pi runtime, gpiozero (61 files)
|-- Python Code/
|   |-- attendance.py                                     9.9 KB   the demo
|   |-- blink.py                                          0.3 KB   an LED on GPIO17 (the default)
|-- Proteus Simulation/
|   |-- attendance.py                                     9.9 KB   the program of the demo
|   |-- Pi-4-Model-B-RFID-Attendance.pdsprj              32.7 KB   the demo: RFID attendance station
|   |-- TEPDS3231.DLL                                   321.5 KB   copy of the model
|   |-- TEPMFRC522.DLL                                  336.5 KB   copy of the model
|   |-- TEPNET.DLL                                       2.37 MB   copy of the model
|-- README.txt                                          ~19.5 KB   this file
Total: 24.75 MB (unzipped). The source code of the models and of the TEP Pi runtime is not included.

WHAT IS IT?
The Raspberry Pi 4 Model B (2019) as one Proteus part - and a way to run Raspberry Pi programs in Proteus 8.5.
Proteus cannot run Raspberry Pi OS, so this library does not emulate Linux. It does what matters for electronics: the
board runs YOUR PYTHON PROGRAM (a .py file, the PROGRAM property) against the circuit on the sheet, with the Python
libraries a Pi uses for its pins, its I2C / SPI / UART buses and its network.
  * At Run the board starts Python 3.11 (included: the TEPPi folder) with our TEP Pi runtime, then your program.
    The program and Proteus work in lockstep: while the program runs, Proteus waits; while the program sleeps, waits
    for a pin, a bus or the network, Proteus runs. So time.sleep(0.5) is 0.5 s of simulation, a busy loop still moves
    the clock (about 1.5 us per GPIO call, as Python on the Pi 4's 1.5 GHz Cortex-A72), and every edge is on time.
    time.time(), time.monotonic(), time.strftime() and datetime.now() follow the simulation's clock too.
  * The network: eth0 when the Ethernet cable is in at Run (ETHERNET IN, the default; a click on the RJ45 plugs or
    unplugs it), wlan0 when it is out - wlan0 then joins the network in the WIFISSID / WIFIPASS properties (default: our
    router "TEP-WiFi", password 12345678 - the network of our ESP32 / Arduino Wi-Fi parts and the Laptop / Mobile WiFi
    Monitors) 2.3 to 3.5 s after Run. One network interface at a time; the Pi is 192.168.1.51 (192.168.1.(50 + the
    part's number)), the name raspberrypi.local. The wired Pi and the Wi-Fi monitors meet on the same router.
  * Threads work (gpiozero's threads, your own threading.Thread, Timer, Queue, Lock): every wait is in simulation time;
    an error in a thread is printed as Python prints it ("Exception in thread ...").
  * The Python libraries for the pins (the same names, numbers and messages as on a Pi):
      RPi.GPIO      setmode, setup and output with one pin or a list (and a list of values), input, cleanup,
                    add_event_detect / event_detected / wait_for_edge with callbacks and bouncetime, PWM (software PWM
                    made by the board, steady while the program sleeps)
      gpiozero      LED, PWMLED, Button, OutputDevice, Buzzer, Servo, AngularServo, MotionSensor, DistanceSensor,
                    CPUTemperature and the rest (gpiozero 2.0.1, unchanged, on RPi.GPIO)
      spidev        SPI0 on GPIO11 (SCLK), GPIO10 (MOSI), GPIO9 (MISO), CE0 = GPIO8, CE1 = GPIO7, modes 0 to 3, up to
                    8 MHz; xfer / xfer2 take up to 4096 bytes (spidev's bufsiz), writebytes2 any length
      smbus2 / smbus  I2C bus 1 on GPIO2 (SDA) / GPIO3 (SCL) at 100 kHz, the Pi's 1.8 k pull-ups: read_byte,
                    write_byte, the byte / block reads and writes, write_quick, i2c_rdwr with i2c_msg; a device that
                    does not answer gives OSError [Errno 121] Remote I/O error
      serial        pyserial on /dev/serial0 (on a Pi 4 = /dev/ttyS0, the mini UART; /dev/ttyAMA0 is accepted too):
                    TXD GPIO14, RXD GPIO15, any baud rate, timeouts, back-to-back bytes
      1-Wire        the DS18B20's files under /sys/bus/w1/devices (w1-gpio on GPIO4), as the kernel makes them
      Adafruit_DHT, adafruit_dht + board   DHT11 / DHT22 on any GPIO
      socket        TCP and UDP on eth0 or wlan0, http.server / socketserver, urllib.request, select
  * The Pi's own files: /proc/cpuinfo (Revision c03114, four ARMv8 processors), /proc/device-tree/model ("Raspberry Pi
    4 Model B Rev 1.4"), the CPU temperature in /sys/class/thermal (gpiozero's CPUTemperature), /proc/loadavg,
    /proc/meminfo (4 GB).
  * The Pi Terminal (our TEP window, no Windows title bar): the shell prompt (pi@raspberrypi:~ $ python3 ...), the
    program's output (OUT) and errors (ERR, as Python prints them on a Pi), a line for input() (IN); its Board tab
    shows the GPIOs (BCM numbers), the LEDs, the supply pins and RESTART PROGRAM. Click a micro-HDMI socket or the
    processor to open it.
  * The LEDs: PWR (red) and ACT (green: it flickers while the board boots and when the program prints) standing at the
    left edge above the USB-C socket, and the RJ45 jack's own LEDs - LNK (green) and 100 (yellow), lit with the cable
    in.
  * The header's supply pins power the modules wired to them, as on the bench: 5V, 3V3 and GND as logic levels (an
    analog VCC reading sees 5 V on either rail).
The board is drawn our way at its real size (85 x 56 mm, rounded corners, four mounting holes) from the Raspberry Pi 4
Model B drawing: the 40-pin header along the top edge, the metal shield can of the dual-band Wi-Fi / Bluetooth 5.0
module under pin 1 with the raspberry logo below it, the DSI display connector and the microSD card on the left, the
RUN / GLOBAL_EN pads, the BCM2711 under its silver heat spreader with the 4 GB LPDDR4 beside it, the 4-pin PoE header
under the top-right mounting hole, the RJ45 at the top of the right edge (the Pi 4 swapped it with the USB ports) with
the Broadcom Gigabit PHY beside it, the blue USB 3.0 pair and the black USB 2.0 pair below it with the VL805 USB 3.0
controller, and along the bottom the USB-C power socket, the two micro-HDMI sockets, the CSI camera connector and the
black 4-pole A/V jack; the MaxLinear MxL7704 power chip by the USB-C, PWR / ACT at the left edge. The 40 pins leave
the top edge as one comb 50 thou apart, each with a colour-coded tag: 5V red, 3V3 orange, GND black, GPIO green, I2C
blue, SPI pink, UART purple, ID_SD / ID_SC grey.

ONE DEVICE (search "RASPBERRY" in Pick Devices):
  RASPBERRY PI 4 MODEL B  "Raspberry Pi 4 Model B" V1.0 (category Microprocessor ICs > Raspberry Pi), prefix PI,
                          model TEPNET.DLL (with the TEPPi folder)
The same TEPNET.DLL also runs our Raspberry Pi Model B, 1 Model B+, 2 Model B, 3 Model B, 3 Model B+ and 3 Model A+,
our Ethernet and Wi-Fi shields, modules and boards and the Laptop / Mobile WiFi Monitors; 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 with the demo project as shipped. What the Proteus runs showed:
* Pi-4-Model-B-RFID-Attendance: eth0 is up 1.6 s after Run (the RJ45's LNK and 100 lit); the program prints "MFRC522
  version 0x92 on SPI0 (CE0), RST on GPIO25", the DS3231's time (the PC's clock, TIME = PC) with 25.00 C, then
  "serving on http://192.168.1.51:8000/".
* The laptop and the phone open http://192.168.1.51:8000/ (Browser, Go): the RTC time, the DS3231's temperature,
  "In now: 0 of 0", no scans yet, REFRESH / ENROL NEXT CARD / CLEAR LOG - text links on the laptop, buttons on the
  phone.
* CARD 1 (DE AD BE EF) tapped: "unknown", the LED blinks three times. ENROL NEXT CARD on the phone ("the page:
  /enrol", the page says "ENROL: tap a new card"), CARD 1 again: "Ayesha enrolled". ENROL NEXT CARD on the laptop,
  CARD 4 (A1 B2 C3 D4): "Bilal enrolled". CARD 1 and CARD 4: Ayesha IN, Bilal IN (D1 lit 1 s each); CARD 2
  (12 34 56 78): unknown; CARD 1: Ayesha OUT. REFRESH on both monitors: "In now: 1 of 2", the seven scans newest first
  with the DS3231's time, "Enrolled: Ayesha, Bilal".
* The MFRC522's pop-up: antenna on, VersionReg 92, SPI at 1.00 MHz, card 1 halted by the reader after each read (HLTA),
  last UID DE AD BE EF. The DS3231's pop-up: RUNNING, OSF 0, 25.00 C, 0 sets; each page and scan reads the time
  (register pointer 00, 7 bytes) and the temperature (11, 2 bytes) at 0x68.
* The Board tab: the BCM2711 at 1.5 GHz, GPIO2 / GPIO3 pulled up, GPIO8 (CE0) and GPIO25 (RST) HIGH, GPIO10 / GPIO11
  and GPIO17 LOW at rest, PWR, LNK and 100 lit, 5V 5.00 V, 3V3 3.30 V, "No errors".
* Speed on our test PC: about 24 to 33 % of real time with the two pop-ups, the two monitors and the Pi Terminal open.

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). TEPRPI4B.LIB is the Pi; TEPMFRC522.LIB (the RC522 reader), TEPDS3231.LIB (the DS3231
   clock), TEPLAPTOP.LIB and TEPMOBILE.LIB are the demo's parts.
3. Copy everything in "Proteus Model Files" - the DLLs AND the TEPPi folder - to the MODELS folder:
     C:\Program Files (x86)\Labcenter Electronics\Proteus 8 Professional\MODELS
   TEPPi holds Python 3.11 and the TEP Pi runtime; the Pi finds it next to TEPNET.DLL, in MODELS or next to your
   project. Replace an older TEPNET.DLL and TEPPi folder (these are the newest).
4. Delete TEPRPI4B.IDX (and the .IDX of a part library you replaced) from the LIBRARY folder if it is there.
5. Start Proteus. In Pick Devices (P) search "RASPBERRY".
Nothing else to install: Python is in TEPPi (no Python on the PC needed, none is changed).

RUN THE DEMO
Keep the .py file and the DLLs beside the project in "Proteus Simulation" (the TEPPi folder in MODELS).
  Pi-4-Model-B-RFID-Attendance.pdsprj - PI1 runs attendance.py on Ethernet (the cable in): U1 = an RC522 RFID reader
  (MFRC522) on SPI0 (SDA on GPIO8 CE0, SCK on GPIO11 SCLK, MOSI on GPIO10, MISO on GPIO9, RST on GPIO25, 3.3V on 3V3),
  U2 = a DS3231 real-time clock (SDA / SCL on GPIO2 / GPIO3, VCC on 3V3, address 0x68), D1 = a green LED on GPIO17
  through R1 330R; PC1 = the Laptop WiFi Monitor and MOB1 = the Mobile WiFi Monitor on the same network. The reader and
  the clock are the Advance parts: their pop-up windows open at Run.
  Press Run: eth0 is up in about 1.6 s; the Pi Terminal shows the reader's version (0x92 = MFRC522 v2.0), the DS3231's
  time and temperature and "serving on http://192.168.1.51:8000/". On the laptop or the phone open that address
  (Browser, the address, Go): the page shows the DS3231's time and temperature, who is in, the last 8 scans and the
  enrolled names, with REFRESH, ENROL NEXT CARD and CLEAR LOG (text links on the laptop, buttons on the phone).
  Put a card on the reader: in the MFRC522's pop-up (Cards) press Tap on CARD 1 - 4 (0.5 s on the reader) or Hold.
  A new card is "unknown" and the LED blinks three times. Press ENROL NEXT CARD on the page, then tap the card: it gets
  the next name (Ayesha, Bilal, Chen, Dina, Emre, Farah). An enrolled card toggles IN and OUT, each scan stamped with
  the DS3231's time, and the LED lights for 1 s. REFRESH reloads the page; CLEAR LOG empties the list of scans.
  The program is pure Python - spidev with its own MFRC522 driver (REQA, anticollision, SELECT with the CRC_A, HLTA;
  4- and 7-byte UIDs), smbus2 for the DS3231 (the BCD time, the temperature, the oscillator-stop flag: a DS3231 that
  lost its time gets the Pi's clock), gpiozero's LED, a thread for the reader and http.server.

YOUR OWN PROGRAMS
Write the program with any editor, put the .py next to your project and set the Pi's PROGRAM property to its name (or
a full path). Start from Python Code\blink.py (an LED on GPIO17). Python's standard library is there; other
pure-Python packages work when you copy them next to your program. Use BCM numbers (GPIO.setmode(GPIO.BCM),
gpiozero's LED(17)) or GPIO.setmode(GPIO.BOARD) with the header's pin numbers.
A program that never sleeps and never touches a pin for 3 real seconds is left running on its own (the simulation
goes on); input() waits for a line typed in the Pi Terminal.

THE 40-PIN HEADER (BCM numbers - the tags on the board)
   1 3V3        2 5V          3 GPIO2 SDA    4 5V          5 GPIO3 SCL    6 GND         7 GPIO4 (1-Wire)
   8 GPIO14 TXD 9 GND        10 GPIO15 RXD  11 GPIO17     12 GPIO18      13 GPIO27     14 GND
  15 GPIO22    16 GPIO23     17 3V3         18 GPIO24     19 GPIO10 MOSI 20 GND        21 GPIO9 MISO
  22 GPIO25    23 GPIO11 SCLK 24 GPIO8 CE0  25 GND        26 GPIO7 CE1   27 ID_SD      28 ID_SC
  29 GPIO5     30 GND        31 GPIO6       32 GPIO12     33 GPIO13      34 GND        35 GPIO19
  36 GPIO16    37 GPIO26     38 GPIO20      39 GND        40 GPIO21
3.3 V logic: GPIO2 / GPIO3 have the Pi's 1.8 k pull-ups to 3.3 V; RPi.GPIO's pull-ups / pull-downs are weak drives.
ID_SD / ID_SC (27, 28, GPIO0 / GPIO1) are kept for a HAT's ID EEPROM; leave them free, as on a real Pi.
The 4-pin PoE header and the RUN / GLOBAL_EN pads are drawn, not pins of the part (a PoE HAT is not modelled).

PROPERTIES (double-click the Pi > Edit Properties)
  PROGRAM    the Python program (default blink.py; a name next to the project or a full path)
  AUTOOPEN   the Pi Terminal at Run: YES (default) or NO
  ETHERNET   the cable to the router at Run: IN (default: eth0) or OUT (the network on wlan0)
  WIFISSID   the Wi-Fi network wlan0 joins (default TEP-WiFi)
  WIFIPASS   its password (default 12345678)
  PYTHON     a python.exe of your own (empty: TEPPi's)
  RUNTIME    the TEP Pi runtime folder (empty: TEPPi's)

TROUBLESHOOTING
* "TEP Pi: the TEPPi folder ... was not found": copy the TEPPi folder from "Proteus Model Files" into MODELS (or next
  to the project).
* "python3: can't open file": the PROGRAM file is not next to the project - put it there or give a full path.
* ModuleNotFoundError for a package: only the libraries above are built in; copy a pure-Python package's folder next to
  your program.
* The reader's version reads 0x00 or 0xFF: check the SPI wires (SDA on CE0 = GPIO8, MOSI to MOSI, MISO to MISO, SCK on
  SCLK), 3.3V on 3V3 and RST HIGH (GPIO25); the register address goes out as (reg << 1) with bit 7 set for a read.
* A card held on the reader is read once: the program halts it (HLTA) after each read, as a real reader does. Tap it
  again (or remove it and put it back) to read it again.
* OSError: [Errno 121] Remote I/O error: the DS3231 does not answer at 0x68 - check its VCC / GND and SDA / SCL.
* The RTC shows 2000-01-01: the DS3231's TIME property is LOST (a new module) and the program found OSF set - it sets
  the clock from the Pi's time; with TIME = PC the coin cell kept the PC's time.
* The page does not open: the address is http://192.168.1.51:8000/ (the port the program serves), and the program must
  have printed "serving on". A monitor sometimes needs Go a second time. Use the page's REFRESH link to see new
  scans (the monitors' Reload repeats the last link, e.g. ENROL NEXT CARD).
* A paused simulation shows the SIMULATION LOG: click the Schematic Capture tab.

BUG REPORTS AND FEATURE REQUESTS
Please post them in our forum with a screenshot, the program, the Pi Terminal's text and the simulation log:
  https://www.theengineeringprojects.com/forum/category/raspberry-pi-4-model-b-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 Raspberry Pi board model, the TEP Pi runtime, the Pi Terminal and the network (TEPNET.DLL, the compiled .pyc files
  in TEPPi\runtime with the stand-ins RPi, smbus2, smbus, spidev, serial, Adafruit_DHT, adafruit_dht, board), the
  symbols and artwork (TEPRPI4B.LIB), the part models (TEPMFRC522 and TEPDS3231 .DLL / .LIB, the Laptop and Mobile
  WiFi Monitors' TEPLAPTOP.LIB / TEPMOBILE.LIB in TEPNET.DLL) and the demo program are made by The Engineering
  Projects. Our stand-ins follow the APIs of RPi.GPIO, smbus2, py-spidev, pyserial, Adafruit_DHT and
  adafruit-circuitpython-dht; none of their code is copied. The source code of the models is not included (nor the
  runtime's: it ships compiled for the included Python 3.11).
* TEPPi\python is the official embeddable Python 3.11.9 for Windows (32-bit) from python.org, unchanged, under the
  Python Software Foundation License (TEPPi\python\LICENSE.txt).
* TEPPi\runtime\gpiozero is gpiozero 2.0.1.post3 and TEPPi\runtime\colorzero is colorzero 2.0, unchanged, under the BSD
  3-Clause licence (their LICENSE files in the dist-info folders).
* Proteus is a product of Labcenter Electronics and is not included. Raspberry Pi is a trademark of Raspberry Pi Ltd.
  This library is not made or endorsed by Raspberry Pi Ltd or Labcenter.

MODEL SCOPE AND LIMITS
Modelled: the 26 GPIOs of the 40-pin header (inputs, outputs, RPi.GPIO's pull-ups / pull-downs, edges, software PWM),
the I2C, SPI, UART, 1-Wire and DHT buses as the Pi's drivers drive them, the supply pins, Ethernet (eth0, the cable)
and Wi-Fi (wlan0: the join, DHCP, TCP and UDP to every TEP network part), one interface at a time, the LEDs, a 0.5 s
boot before the program starts, the Pi's /proc and /sys files above, the Pi Terminal. Not modelled: Raspberry Pi OS
(no desktop, no shell commands, no apt, no os.system), Bluetooth, the 5 GHz band and the Gigabit speed (the network is
the same TEP network at any band), PoE, wlan0 and eth0 at the same time, Wi-Fi scanning from the program, the four
cores (one program, its threads take turns), the Pi 4's extra UART, I2C and SPI buses (device-tree overlays), the
micro-HDMI and A/V outputs, the camera and display connectors, USB 2.0 / 3.0, the microSD card's files, hardware PWM
(GPIO18 is software PWM here), a HAT's ID EEPROM, C programs and C extensions, the real CPU's speed (each GPIO call
takes about 1.5 us; pure Python code takes no simulation time), real-time jitter. The model's own choices: the
board's IP address (192.168.1.51 for PI1), the boot time, the router; the simulation runs below real time.

VERSION
TEP Raspberry Pi 4 Model B library V1.0 (Oct 2026). Device RASPBERRY PI 4 MODEL B (TEPRPI4B.LIB / TEPNET.DLL with
TEPPi: Python 3.11.9 and the TEP Pi runtime 0.2). Demo program attendance.py V1.0, blink.py.