Skip to main content

epicsdev

epicsdev is a Python framework designed for rapidly developing EPICS PVAccess servers using the p4p library.

Device process variables (PVs) are defined using a compact format:

[name, description, initial_value, attributes]

Device-specific logic resides within a small, well-structured Python file following a predictable pattern. Given an instrument programming manual, an LLM assistant (such as GitHub Copilot) can easily leverage this pattern to spin up initial support for new hardware in under an hour.


Key Features

  • High-Bandwidth Data Streaming: Minimizes packet overhead and uses the optimized p4p bindings to move complex data structures directly.
  • Built-in Services: Out-of-the-box support for autosave/restore, IocStats, heartbeat monitoring, and PV-put logging.
  • Rapid Prototyping: Simple, declarative format for PV definitions.
  • LLM-Friendly: Highly predictable boilerplate that allows AI code assistants to write drivers effortlessly.
  • OPI Integration: Automated operator interface generation for Phoebus.

Getting Started

1. Generate a PVAccess Server

Follow the Detailed Server Generation Guide to bootstrap a functional PVAccess server supporting your instrument's core functions.

2. Generate an OPI Display

You can automatically create an operator interface (OPI) layout using phoebusgen. See the OPI Generation Instructions for details.

3. Quick Test (Simulation Mode)

To see the framework in action without physical hardware, you can launch a simulated multi-channel waveform generator, which can be useful for stress-testing EPICS installations. The following command generates 100 noisy waveforms (1,000 points each) alongside 300 scalar parameters:

python -m epicsdev.multiadc -C 100 -n 1000

To change the data publication frequency, modify the sleep PV: pvput multiadc:0:sleep .1.

Quick GUI

To control and plot the server's PVs, you can use the pypeto and pvplot modules.

pip install pypeto pvplot
python -m pypeto -f config/multiadc_pp

Other examples include a single-waveform generator and a multi-peak image generator:

python -m epicsdev.epicsdev
python -m epicsdev.imagegen

See imagegen usage for more details.

4. Continuous Integration

To package epicsdev-based PVAccess servers as standalone Linux executables in your build pipeline, see the Continuous Integration Guide for PyInstaller build instructions and dependency requirements.

Fully Functional PVAccess Servers Developed Using epicsdev

Power Supplies

Oscilloscopes

Signal Generators

Data Acquisition Instruments

Magnetometers

Vacuum Gauge Controllers

Simulation Utilities

Metadata

Release files for epicsdev 3.3.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for epicsdev 3.3.4
File Size Uploaded Provenance Actions
epicsdev-3.3.4.tar.gz 60.1 kB Without provenance Details for epicsdev-3.3.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for epicsdev 3.3.4
File Interpreter ABI Platform Actions
epicsdev-3.3.4-py3-none-any.whl Python 3 none any Details for epicsdev-3.3.4-py3-none-any.whl

Total release size: 85.1 kB

Release files / epicsdev-3.3.4.tar.gz

Download URL epicsdev-3.3.4.tar.gz
Size 60.1 kB
Tags Source
SHA-256 checksum
How to use checksums
7030939852e1ab352071164695740f23614ec690ce9e3e57c5be2c1529724bcb
BLAKE2b-256 checksum
How to use checksums
aa02b322920afbe5e1de327a2ce9d69edb05e194efc4fcfe045fa9f230f48e54
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Red Hat Enterprise Linux","version":"9.7","id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / epicsdev-3.3.4-py3-none-any.whl

Download URL epicsdev-3.3.4-py3-none-any.whl
Size 25.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a630bb19c94004824abff76f1fb5195e1018f73ba014df86cbf4007aba4c435b
BLAKE2b-256 checksum
How to use checksums
4105edbd673bf2611caae2c1c9aced63948bd97cf6abcb94df97012d1addc541
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Red Hat Enterprise Linux","version":"9.7","id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for epicsdev 3.3.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page