visitoolkit_connector
client-side implementation of 'DMS JSON Data Exchange'
(most parts of specification v1.4 is already implemented,
but my code currently contains many rough edges...)
Installation via pip
https://pypi.org/project/visitoolkit-connector
(runs on Python 3)
description
An INOFFICIAL OpenSource client library written in Python to
ProMoS NT (c) AKA Saia Visi.Plus (c) version 1.7 or higher
- search for datapoints
- manipulations on datapoints (get, set, delete)
- retrieving of trend data
- retrieving of alarms and protocols
- event-based monitoring of datapoints
visitoolkit_connector communicates over websockets to DMS and implements the official 'DMS JSON Data Exchange' protocol.
All JSON objects (requests and responses) are mapped to instances of Python classes.
All JSON values are mapped to attributes.
Events from datapoint subscriptions are handled by visitoolkit_eventsystem for executing your Python callbacks in a background thread.
documentation for this protocol is without any warranty temporary available under
https://github.com/stefanbraun-private/stefanbraun-private.github.io/tree/master/ProMoS_dev_docs
All rights reserved by the respective owner 'MST Systemtechnik AG'
usage
from visitoolkit_connector import connector
TODO: add examples...
=>at the moment you find minimal usage examples at the end of the main Python script:
https://github.com/stefanbraun-private/visitoolkit_connector/blob/master/visitoolkit_connector/connector.py
Increasing logging level for bughunting:
import logging
logging.getLogger('visitoolkit_connector').setLevel(logging.DEBUG)
background information
visitoolkit_connector is a core part of visitoolkit.
visitoolkit is written for the proprietary Building and Process Management System
'ProMoS NT' (c) MST Systemtechnik AG'
(also known as 'Saia Visi.Plus' (c) Saia-Burgess Controls AG)
Intention:
Support creator of visualisation projects...
Add efficiency...
Reduce manual error-prone processes...
Add missing features...
Disclaimer:
'visitoolkit' is an open source homegrown hobby project
without any warranty and liability.
=>Use 'visitoolkit' at your own risk!
Metadata
Release files for visitoolkit-connector 0.1.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 |
|---|---|---|---|---|
| visitoolkit-connector-0.1.2.tar.gz | 37.2 kB | Without provenance | Details for visitoolkit-connector-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| visitoolkit_connector-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for visitoolkit_connector-0.1.2-py3-none-any.whl |
Total release size: 57.8 kB
Release files / visitoolkit-connector-0.1.2.tar.gz
| Download URL | visitoolkit-connector-0.1.2.tar.gz |
|---|---|
| Size | 37.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0cceba88d70484449fda9037c31f3cd88636b21f4ebf394b5d05601c716259c2
|
|
BLAKE2b-256 checksum How to use checksums |
86f2bff4a2520d3169fdd33ecb6c53f5fe0613da3051e9933fb760f0b3bd9dd5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.2.0 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.7.0
|
Release files / visitoolkit_connector-0.1.2-py3-none-any.whl
| Download URL | visitoolkit_connector-0.1.2-py3-none-any.whl |
|---|---|
| Size | 20.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b00382040008f5f87273472e1ea0a58de33016e2eb2c75d3e83127d69fa6018c
|
|
BLAKE2b-256 checksum How to use checksums |
67a598b97fb229ccc20e641e45088604647e3ba4c1633f9dbc31fa9a9759d5c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.2.0 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.7.0
|
Security for visitoolkit-connector 0.1.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.