Proteus does not have feature to include external libraries for Raspberry Pi.
Hardware Driver Library (or Peripheral Driver Directory) Folder:
This folder is for the Raspberry Pi simulation engine in Proteus and located at:
C:\Program Files (x86)\Labcenter Electronics\Proteus 8 Professional\DATA\VSM Studio\drivers\RaspberryPi
That folder contains the native peripheral drivers, breakout board libraries, and sample code provided by Labcenter Electronics for simulating a Raspberry Pi inside Proteus VSM Studio.
When you use the Proteus "Visual Designer" or "VSM Studio" workflow to write Python code for a simulated Raspberry Pi, Proteus relies on the files in this directory to bridge your script with the graphical schematic components.
Here is a breakdown of what is inside that directory based on your image and how Proteus uses it:
1. Hardware Interface Modules (The Core Drivers)
The root files like cpu.py, Timer.py, UART.py, I2C.py, and SPI.py are custom-written wrapper scripts by Labcenter.
What they do: They map standard Python commands to the simulated pins on the Proteus schematic. For example, calling an internal method from
cpuor using the underlying hardware abstractions tells Proteus to change a physical pin's voltage on your screen.
2. Built-in HAT and Breakout Board Drivers
You can see folders like adafruit_blink_led, grover_relay, PimoroniMotorHat, and Grove_Buzzer.
What they do: These are pre-configured python libraries matching popular physical hardware add-on boards (HATs) or Grove sensors. If you place an Adafruit or Grove breakout board from the Proteus library into your schematic, Proteus pulls the matching Python driver from this folder so you can interact with it using pre-made functions without writing low-level I2C or SPI protocols from scratch.
3. VSM Interprocess Communication (VFP, FileStore)
Files like VFP (Virtual Front Panel) and FileStore handle the communication layer.
What they do: Standard desktop Python packages expect to talk directly to a real Linux operating system kernel. Since the Raspberry Pi in Proteus is running as a simulated process inside a Windows application, these files redirect inputs, outputs, file management, and terminal strings (
VFP) between your script execution engine and the Proteus application window.
Why this matters for your scripts:
When you configure a Proteus project using Python 3 (Proteus) as the toolchain, Proteus automatically appends this folder to Python’s internal search path (sys.path). That is why a default Proteus template can import libraries like import cpu or find specialized breakout board drivers instantly, but standard desktop packages like import RPi.GPIO may conflict or behave erratically depending on how the internal template structure passes instructions to the execution engine.
I tried using the following methods.
Use pip to install external python libraries.
C:\WINDOWS\system32>pip install adafruit-circuitpython-ads1x15 rpi.gpio
