Skip to main content

Physical layer for using a Moxa devices for IEC870REE library

Using:

from iec870ree_moxa import Moxa
from iec870ree.ip import Ip
from iec870ree.protocol import LinkLayer, AppLayer
import iec870ree.protocol
import datetime

ip_layer = iec870ree.ip.Ip(('127.0.0.1', 40001))
physical_layer = Moxa('PHONENUMBER', ip_layer)
link_layer = iec870ree.protocol.LinkLayer(10345, 1)
link_layer.initialize(physical_layer)
app_layer = iec870ree.protocol.AppLayer()
app_layer.initialize(link_layer)
physical_layer.connect()
link_layer.link_state_request()
link_layer.remote_link_reposition()
logging.info("before authentication")
resp = app_layer.authenticate(1)
logging.info("CLIENTE authenticate response {}".format(resp))
logging.info("before read")

start_date = datetime.datetime(2018, 4, 1, 0, 0)
end_date = datetime.datetime(2018, 4, 2, 1, 0)

for resp in app_layer.read_integrated_totals(start_date, end_date):
    logging.info("read response {}".format(resp))
physical_layer.disconnect()

Metadata

Release files for iec870ree-moxa 0.5.2

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

Source distribution (sdist)

Source distribution for iec870ree-moxa 0.5.2
File Size Uploaded Provenance Actions
iec870ree_moxa-0.5.2.tar.gz 3.3 kB Without provenance Details for iec870ree_moxa-0.5.2.tar.gz

Release files / iec870ree_moxa-0.5.2.tar.gz

Download URL iec870ree_moxa-0.5.2.tar.gz
Size 3.3 kB
Tags Source
SHA-256 checksum
How to use checksums
752ba6b3884ab3b9c7494b42ac3072c068e1e70e88597b5e2c108c3c9b63c8e8
BLAKE2b-256 checksum
How to use checksums
b47f32c1c3a42efc48b9a6dfb518d987014322145edde360d6771c0d0042594d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.8.0 pkginfo/1.10.0 readme-renderer/34.0 requests/2.23.0 requests-toolbelt/1.0.0 urllib3/1.26.18 tqdm/4.64.1 importlib-metadata/4.8.3 keyring/23.4.1 rfc3986/1.5.0 colorama/0.4.5 CPython/3.6.9

Security for iec870ree-moxa 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.

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