This is a client library for the PILS PLC interface specification, found here: https://forge.frm2.tum.de/public/doc/plc/master/html/
A minimal example of usage:
import logging
import zapf.scan
# Connection via different protocols is abstracted via URIs.
# Here we connect via Modbus/TCP using slave number 0.
URI = 'modbus://my.plc.host:502/0'
# The Scanner allows reading the PLC's "indexer" which provides
# all metadata about the PLC and its devices.
scanner = zapf.scan.Scanner(URI, logging.root)
plc_data = scanner.get_plc_data()
print('connected to PLC:', plc_data.plc_name)
# For each found device, this will create a client object and
# read the most basic property - the current value.
for dev in scanner.scan_devices():
print('got a device:', dev)
print('device value:', device.read_value())
Metadata
Release files for zapf 0.5.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zapf-0.5.2.tar.gz | 436.1 kB | Without provenance | Details for zapf-0.5.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zapf-0.5.2-py3-none-any.whl | Python 3 | none | any | Details for zapf-0.5.2-py3-none-any.whl |
Total release size: 505.2 kB
Release files / zapf-0.5.2.tar.gz
| Download URL | zapf-0.5.2.tar.gz |
|---|---|
| Size | 436.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
025b88f95b3ba95eb0e238434f3803247ba1d25ce7b3d6af86f6ab39c868edb2
|
|
BLAKE2b-256 checksum How to use checksums |
b16e5b1b024917bd68c240df783d891833bcefc4bb7ba14821409e1f859ce1ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.11
|
Release files / zapf-0.5.2-py3-none-any.whl
| Download URL | zapf-0.5.2-py3-none-any.whl |
|---|---|
| Size | 69.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef33df02c72a1cafedc22f944f8793b06fa687e5d9e6c5564df67764da737914
|
|
BLAKE2b-256 checksum How to use checksums |
87bcc7ce5119e1dca92badc2b68e4d9c9a6dad6d60f9b3bf3d723920e6bf2d4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.11
|
Security for zapf 0.5.2
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.