Skip to main content
pyPicoSDK

pyPicoSDK

GSAS Engineering · · 2 min read

pyPicoSDK: Getting started

Introduction

Pico Technology provides a wide range of PC-based oscilloscopes that can be controlled and automated using software. For Python developers, pyPicoSDK offers a convenient way to interface with PicoScope devices, enabling tasks such as data capture, automation, and analysis directly within Python scripts.

This approach is especially useful for engineers and researchers who want to integrate oscilloscope measurements into automated test setups, signal processing workflows, or data analysis pipelines.

Step 1: Install PicoSDK

Before using pyPicoSDK, you need to have the official PicoSDK drivers installed. These drivers act as the communication layer between your computer and the PicoScope hardware.

  • The SDK can be downloaded from Pico Technology’s official website.

  • Choose the installer that matches your operating system (Windows, Linux, or macOS).


Step 2: Install pyPicoSDK (Python Wrapper)

Once the drivers are ready, you can install the Python wrapper using pip:

pip install pypicosdk

This package provides Python bindings for the C-based PicoSDK libraries.


Step 3: Import pyPicoSDK in Your Python Project

After installation, you can start writing Python scripts. To load the library, simply import it:

import pypicosdk as psdk

Step 4: Quick Test Script

Here’s a minimal script to test your setup:

scope = psdk.ps6000a()
scope.open_unit()
print(scope.get_unit_serial())
scope.close_unit()

If everything is working correctly, this script will open the oscilloscope, print the device’s serial number, and then close the connection.


Step 5: Explore Example Scripts

pyPicoSDK includes a set of example scripts on GitHub that demonstrate how to configure the scope, capture signals, and process the data. Running these examples is the best way to get familiar with the library’s capabilities.

Supported Devices

Currently, pyPicoSDK supports:

  • PicoScope 6000E Series (via the ps6000a driver)

  • PicoScope 3000E Series (via the psospa driver)

More device families are expected to be added in the future as development progresses.


Why Use pyPicoSDK? (Theory)

Traditionally, oscilloscopes are controlled through vendor-specific GUI applications. While convenient, this limits flexibility in automated testing and integration with custom workflows. By exposing the hardware API through Python:

  • Engineers can integrate oscilloscopes into larger automated test systems.

  • Researchers can directly analyze captured data using libraries like NumPy, SciPy, or Matplotlib.

  • Developers can build custom measurement solutions that go beyond the scope of standard oscilloscope software.

In short, pyPicoSDK bridges the gap between PicoScope hardware and Python’s powerful ecosystem for scientific computing.

Interested in Pico Technology tools?

Talk to our application engineers for personalized tool recommendations.

Stay in the Loop

Get monthly compliance updates, product insights, and engineering best practices delivered to your inbox.

Related Articles

Embedded engineering bench in India, illustrating the hardware a developer can act on today, supported by GSAS
Technical Guides Arm

Arm's Agentic AI Push: What Indian Embedded Teams Can Actually Use Today

Arm has set out its platform strategy for the agentic era, putting inference everywhere it has compute. Indian embedded teams can start on that direction this quarter with the Cortex-M toolchain they already own: Helium, CMSIS-NN, Ethos-U and Vela, on boards you can order today.

13 Sept 2026 · 7 min read
Storage sizing ladder for automotive data logging: four rungs stepping from an aggregate link rate of 1 Gbit/s to 125 MB per second, then 450 GB per hour, then 3.6 TB per eight-hour shift, then 18 TB per five-day week, in decimal units, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Data Loggers: Capture Without Loss

Search for an automotive data logger and the results split into cheap OBD dongles at one end and enterprise ADAS recorders at the other, with nothing in between explaining the engineering that decides whether you lose frames. This is the loss budget end to end: mirror oversubscription upstream of the logger, encapsulation overhead on the capture path, sustained write rate against burst rate, rotation stalls, and storage arithmetic worked in full so you can redo it with your own numbers instead of trusting ours. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 13 min read
Two test paths leaving the same device under test, one into a conformance suite that returns a passed report and one into a partner node that surfaces a field defect, showing why an ECU can clear a published suite and still fail in a vehicle, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Ethernet Conformance: TC8 and Testing Above It

Summarising TC8 as a layer 1 to layer 4 suite is wrong in both directions. The public OPEN Alliance ECU test documents run from transmitter distortion up to a SOME/IP chapter with its own standardised test stub, and they contain exactly one time synchronisation test case. This is what those documents enumerate, chapter by chapter, what genuinely lives above their boundary, why a passing ECU can still fail against a partner node, and how much pre-compliance work a Tier-1 in India can honestly do in-house before a test house visit. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 12 min read