pfeiffer-turbo
Python interface for RS485 connections to Pfeiffer HiPace turbo drive units. Supports the TM700 and TC110 electronic drive units, and can also communicate through a TCP/IP socket, for example when using a serial-to-TCP/IP converter for the turbo controller.
Supported drive units
- TM700
- TC110
Examples
RS485 connection example
from pfeiffer_turbo import TC110, SerialTransport
pump = TC110(address=1, transport=SerialTransport(port="COM9"))
# or: pump = TC110.from_serial("COM9", address=1)
# get the rotation speed in Hz
pump.actual_spd
# start the pump
pump.start()
# stop the pump
pump.stop()
TCP/IP connection example
from pfeiffer_turbo import TM700, TcpTransport
pump = TM700(address=1, transport=TcpTransport(host="10.10.222.8", port=12345))
# or: pump = TM700.from_tcp("10.10.222.8", 12345, address=1)
# get the rotation speed in Hz
pump.actual_spd
# start the pump
pump.start()
# stop the pump
pump.stop()
Writable parameters and validation
Parameters marked read-write or write-only by the parameter metadata can be assigned. When assigning values, the library validates:
- type (bool/int/float/str as defined per parameter)
- allowed options (
optionsmap when present) - value limits (
min/maxwhen present)
Write-only parameters raise AttributeError when read.
Example:
# writable
pump.set_rot_spd = 600
pump.error_ackn = True
# raises ValueError (invalid option)
# pump.gas_mode = 999
# raises AttributeError (write-only parameter)
# pump.error_ackn
Implementation
A baseclass DriveUnit:
class DriveUnit:
def __init__(
self,
transport: BaseTransport,
address: int,
supported_parameters: Sequence[int],
):
takes a set of integers that correspond to Pfeiffer vacuum parameters supported by a particular drive unit. Implemented vacuum parameters are defined in parameters.py. Getters and setters are then generated dynamically from supported_parameters and the metadata in parameters.py.
The enum Parameters contains all implemented Pfeiffer vacuum parameters, and the dictionary parameters maps Parameters values to ParameterInfo objects, where ParameterInfo is a dataclass containing the implementation details for a particular parameter:
@dataclass
class ParameterInfo:
designation: str
data_type: DataType
access: Access | str
min: Optional[Union[int, float]] = None
max: Optional[Union[int, float]] = None
unit: Optional[str] = None
default: Optional[Union[int, float, str]] = None
options: Optional[dict[int, str]] = None
New drive units can be implemented by inheriting from DriveUnit and specifying which Pfeiffer parameters are supported by the model. New parameters can be implemented by extending the Parameters enum and the parameters dictionary. Generated class attributes are named similarly to the Pfeiffer parameter names, with underscores inserted between uppercase-to-lowercase transitions and all letters lowercased, for example GasMode becomes gas_mode.
Release files for pfeiffer-turbo 0.3.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pfeiffer_turbo-0.3.3.tar.gz | 17.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pfeiffer_turbo-0.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:32.2 kB
Release files / pfeiffer_turbo-0.3.3.tar.gz
| Download URL | pfeiffer_turbo-0.3.3.tar.gz |
|---|---|
| Size | 17.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
61471b2b941f0ca6e0333e0ff4001bd9658625eaab2382444f35b36e6a785876
|
|
BLAKE2b-256 checksum How to use checksums |
e0009cd08a2d848c4e68cc52a8abbf4a0e6624ee0d559d4448bfcc4e55a16fe0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logRelease files / pfeiffer_turbo-0.3.3-py3-none-any.whl
| Download URL | pfeiffer_turbo-0.3.3-py3-none-any.whl |
|---|---|
| Size | 15.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a97f41be67948e24466854a725693653ef85257c5821a08dd5d8ef262aa4eb2
|
|
BLAKE2b-256 checksum How to use checksums |
15a52f69a108b445936cf87218919a3c67c51f2f9a8fc9e1948717690502a361
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency log