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 verification and unit test workflow, illustrating the economics of finding defects early, supported by GSAS Micro Systems in India
Technical Guides

Verification Economics: What a Late Defect Actually Costs, and What the Evidence Really Says

Finding a defect in month 2 instead of month 14 is a budget decision before it is a quality decision. This sets out what the published evidence supports, what it does not, including the 100x multiplier that traces back to a course handout rather than a study, and how an Indian embedded team builds the case on its own numbers.

21 Sept 2026 · 14 min read
Horizontal stacked bar showing where an ADAS test vehicle's bandwidth budget is spent, split into cameras, lidar, radar and bus traffic, with the logger uplink limit drawn as a vertical rule crossing the bar, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

ADAS Sensor Data Logging: Bandwidth Budgets That Add Up

Every page that tells you an ADAS test vehicle produces terabytes a day states the headline and skips the arithmetic, so you cannot redo it for your own sensor set. This article publishes the arithmetic instead: one formula, every table row derived on the page, a worked eight-hour drive that chains those rows into a sustained write rate, a media count and an offload window, and the five places bandwidth budgets go wrong. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 15 min read
The bench to harness adapter path drawn left to right: the ECU connector, a test lead, a media converter or pluggable T1 module, RJ45, and the host, showing where each connector family sits between the device under test and the laptop, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Ethernet Connectors: H-MTD, MATEnet, MQS

An ECU arrives on the bench with a connector nobody has a mate for, and the day is gone. Search the family names and you get connector product pages that describe their own part and stop there. This article puts the families side by side in one table using only what their public pages state, then makes the point those pages leave out: the IEEE link segment definition, not the connector, is what sets reach and loss limits, and shielding is a channel decision rather than a preference. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 12 min read