TecoRoute
The TecoRoute package provides software components for better usability of the TecoRoute service from Teco a.s. It consists of TecoRoute server and EPSNET connector.
For the proxy server, which automatically authenticates the user to the TecoRoute web interface, see TecoRoute Proxy.
Components
TecoRoute server
With the SetPlcIp utility, it is possible to set the address of TecoRoute server for the PLC, so there is no restriction to using Teco's TecoRoute service, but it is possible to have a private server.
The TecoRoute server is not fully opensourced yet. Please contact Czetech at hello@cze.tech for this component first.
TecoRoute EPSNET connector
The TecoRoute connector provides various types of EPSNET access to the PLC via the TecoRoute service. By default, the connector is authenticated as Teco's Mosaic, so on the portal this application must be enabled for the user.
Command-line interface
The basic functionality of the components can be invoked from the command-line. Currently, there is only one mode of operation, which is the UDP connector.
Connector
Connector locally opens UPD port 61682, which can be accessed in the same way as the PLC in a local network (e.g. communicate using EPSNET or connect to Mosaic). Example:
tecoroute connector \
--mode udp \
--username BroukPytlik \
--password ferda1 \
--plc AB_1234
The program terminates in case of any error (for example, temporary loss of connection), so it is up to the user to start the program again.
For all options, run tecoroute connector --help.
Library API
Thanks to the library's asynchronous design, it is possible to operate thousands of connections at the same time very efficiently.
As in the command-line example, in Python the UDP connector starts with the code:
from asyncio import run
from logging import INFO, basicConfig
from tecoroute.connector import UdpConnector
basicConfig(level=INFO)
async def main():
connector = UdpConnector(username='BroukPytlik', password='ferda1',
plc='AB_1234')
await connector.run()
run(main())
There is an example of the implementation of simultaneously running connectors according to the data from the MariaDB table at https://github.com/czetech/tecoroute-manager.
See full documentation at https://tecoroute.readthedocs.io.
Installing
Install from PyPI
Requirements:
Installation using pip is done with:
pip install tecoroute
Run from Docker Hub
Run the image from Docker Hub:
docker run czetech/tecoroute
Support
Professional support by Czetech is available at hello@cze.tech.
Source code
The source code is available at https://github.com/czetech/tecoroute.
Metadata
Release files for tecoroute 0.1.0
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 | |
|---|---|---|---|---|
| tecoroute-0.1.0.tar.gz | 12.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tecoroute-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.0 kB
Release files / tecoroute-0.1.0.tar.gz
| Download URL | tecoroute-0.1.0.tar.gz |
|---|---|
| Size | 12.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e041ebacc5428f82bca6b8490d7c0db5ff165de0ca20bd1d6300205fa6f39f5b
|
|
BLAKE2b-256 checksum How to use checksums |
e09df75487aef581f7c1ee5341da81f0e1eb612b240e8e56451a2397ef0eefff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.1
|
Release files / tecoroute-0.1.0-py3-none-any.whl
| Download URL | tecoroute-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e67ad530a267500221da1ef3fadbb3be0251e166d5abd2d7817f50acf53186b4
|
|
BLAKE2b-256 checksum How to use checksums |
7043edd2022d58764e8394ec4e9944e172aa4b5495d80992392cdbefb463dd05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.1
|
Security for tecoroute 0.1.0
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.