| Name | pycomm3 JSON |
| Version |
1.2.14
JSON |
| download |
| home_page | https://github.com/ottowayi/pycomm3 |
| Summary | A Python Ethernet/IP library for communicating with Allen-Bradley PLCs. |
| upload_time | 2023-08-27 15:50:12 |
| maintainer | |
| docs_url | None |
| author | Ian Ottoway |
| requires_python | >=3.6.1 |
| license | MIT |
| keywords |
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
=======
pycomm3
=======
.. <<start>>
.. image:: https://img.shields.io/pypi/v/pycomm3.svg?style=for-the-badge
:target: https://pypi.python.org/pypi/pycomm3
:alt: PyPI Version
.. image:: https://img.shields.io/pypi/l/pycomm3.svg?style=for-the-badge
:target: https://pypi.python.org/pypi/pycomm3
:alt: License
.. image:: https://img.shields.io/pypi/pyversions/pycomm3.svg?style=for-the-badge
:target: https://pypi.python.org/pypi/pycomm3
:alt: Python Versions
|
.. image:: https://img.shields.io/pypi/dm/pycomm3?style=social
:target: https://pypi.python.org/pypi/pycomm3
:alt: Downloads
.. image:: https://img.shields.io/github/watchers/ottowayi/pycomm3?style=social
:target: https://github.com/ottowayi/pycomm3
:alt: Watchers
.. image:: https://img.shields.io/github/stars/ottowayi/pycomm3?style=social
:target: https://github.com/ottowayi/pycomm3
:alt: Stars
.. image:: https://img.shields.io/github/forks/ottowayi/pycomm3?style=social
:target: https://github.com/ottowayi/pycomm3
:alt: Forks
|
.. image:: https://readthedocs.org/projects/pycomm3/badge/?version=latest&style=for-the-badge
:target: https://pycomm3.readthedocs.io/en/latest/
:alt: Read the Docs
.. image:: https://img.shields.io/badge/gitmoji-%20%F0%9F%98%9C%20%F0%9F%98%8D-FFDD67.svg?style=for-the-badge
:target: https://gitmoji.dev
:alt: Gitmoji
Introduction
============
``pycomm3`` started as a Python 3 fork of `pycomm`_, which is a Python 2 library for
communicating with Allen-Bradley PLCs using Ethernet/IP. The initial Python 3 port was done
in this `fork`_ and was used as the base for ``pycomm3``. Since then, the library has been
almost entirely rewritten and the API is no longer compatible with ``pycomm``. Without the
hard work done by the original ``pycomm`` developers, ``pycomm3`` would not exist. This
library seeks to expand upon their great work.
.. _pycomm: https://github.com/ruscito/pycomm
.. _fork: https://github.com/bpaterni/pycomm/tree/pycomm3
Drivers
=======
``pycomm3`` includes 3 drivers:
- `CIPDriver`_
This driver is the base driver for the library, it handles common CIP services used
by the other drivers. Things like opening/closing a connection, register/unregister sessions,
forward open/close services, device discovery, and generic messaging. It can be used to connect to
any Ethernet/IP device, like: drives, switches, meters, and other non-PLC devices.
- `LogixDriver`_
This driver supports services specific to ControlLogix, CompactLogix, and Micro800 PLCs.
Services like reading/writing tags, uploading the tag list, and getting/setting the PLC time.
- `SLCDriver`_
This driver supports basic reading/writing data files in a SLC500 or MicroLogix PLCs. It is
a port of the ``SlcDriver`` from ``pycomm`` with minimal changes to make the API similar to the
other drivers. Currently this driver is considered legacy and it's development will be on
a limited basis.
.. _CIPDriver: https://docs.pycomm3.dev/en/latest/usage/cipdriver.html
.. _LogixDriver: https://docs.pycomm3.dev/en/latest/usage/logixdriver.html
.. _SLCDriver: https://docs.pycomm3.dev/en/latest/usage/slcdriver.html
Disclaimer
==========
PLCs can be used to control heavy or dangerous equipment, this library is provided "as is" and makes no guarantees on
its reliability in a production environment. This library makes no promises in the completeness or correctness of the
protocol implementations and should not be solely relied upon for critical systems. The development for this library
is aimed at providing quick and convenient access for reading/writing data inside Allen-Bradley PLCs.
Setup
=====
The package can be installed from `PyPI`_ using ``pip``: ``pip install pycomm3`` or ``python -m pip install pycomm3``.
.. _PyPI: https://pypi.org/project/pycomm3/
Optionally, you may configure logging using the Python standard `logging`_ library. A convenience method is provided
to help configure basic logging, see the `Logging Section`_ in the docs for more information.
.. _logging: https://docs.python.org/3/library/logging.html
.. _Logging Section: https://docs.pycomm3.dev/en/latest/getting_started.html#logging
Python and OS Support
=====================
``pycomm3`` is a Python 3-only library and is supported on Python versions from 3.6.1 up to 3.10.
There should be no OS-specific requirements and should be able to run on any OS that Python is supported on.
Development and testing is done primarily on Windows 10. If you encounter an OS-related problem, please open an issue
in the `GitHub repository`_ and it will be investigated.
.. attention::
Python 3.6.0 is not supported due to ``NamedTuple`` not supporting
`default values and methods <https://docs.python.org/3/library/typing.html#typing.NamedTuple>`_ until 3.6.1
.. _GitHub repository: https://github.com/ottowayi/pycomm3
.. <<end>>
Documentation
=============
This README covers a basic overview of the library, full documentation can be found on
`Read the Docs`_ or by visiting `https://pycomm3.dev <https://pycomm3.dev>`_.
.. _Read the Docs: https://pycomm3.readthedocs.io/en/latest/
Contributions
=============
If you'd like to contribute or are having an issue, please read the `Contributing`_ guidelines.
.. _Contributing: CONTRIBUTING.md
Highlighted Features
====================
- ``generic_message`` for extra functionality not directly implemented
- working similar to the MSG instruction in Logix, arguments similar to the MESSAGE properties
- See the examples section for things like getting/setting drive parameters, IP configuration, or uploading an EDS file
- used internally to implement some of the other methods (get/set_plc_time, forward open/close, etc)
- simplified data types
- allows use of standard Python types by abstracting CIP implementation details away from the user
- strings use normal Python ``str`` objects, does not require handling of the ``LEN`` and ``DATA`` attributes separately
- custom string types are also identified automatically and not limited to just the builtin one
- BOOL arrays use normal Python ``bool`` objects, does not require complicated bit shifting of the DWORD value
- powerful type system to allow types to represent any CIP object and handle encoding/decoding the object
LogixDriver
-----------
- simple API, only 1 ``read`` method and 1 ``write`` method for tags.
- does not require using different methods for different data types
- requires the tag name only, no other information required from the user
- automatically manages request/response size to pack as many requests into a single packet
- automatically handles fragmented requests for large tags that can't fit in a single packet
- both support full structure reading/writing (UDTs, AOIs, etc)
- for ``read`` the ``Tag.value`` will be a ``dict`` of ``{attribute: value}``
- for ``write`` the value should be a dict of ``{attribute: value}`` , nesting as needed
- does not do partial writes, the value must match the complete structure
- not recommended for builtin type (TIMER, CONTROL, COUNTER, etc)
- both require no attributes to have an External Access of None
- uploads the tag list and data type definitions from the PLC
- no requirement for user to determine tags available (like from an L5X export)
- definitions are required for ``read``/``write`` methods
- automatically enables/disables different features based on the target PLC
- Extended Forward Open (EN2T or newer and v20+)
- Symbol Instance Addressing (Logix v21+)
- detection of Micro800 and disables unsupported features (CIP Path, Ex. Forward Open, Instance Addressing, etc)
LogixDriver Overview
====================
Creating a driver is simple, only a ``path`` argument is required. The ``path`` can be the IP address, IP and slot,
or a full CIP route, refer to the documentation for more details. The example below shows how to create a simple
driver and print some of the information collected about the device.
::
from pycomm3 import LogixDriver
with LogixDriver('10.20.30.100/1') as plc:
print(plc)
# OUTPUT:
# Program Name: PLCA, Device: 1756-L83E/B, Revision: 28.13
print(plc.info)
# OUTPUT:
# {'vendor': 'Rockwell Automation/Allen-Bradley', 'product_type': 'Programmable Logic Controller',
# 'product_code': 166, 'version_major': 28, 'version_minor': 13, 'revision': '28.13', 'serial': 'FFFFFFFF',
# 'device_type': '1756-L83E/B', 'keyswitch': 'REMOTE RUN', 'name': 'PLCA'}
Reading/Writing Tags
--------------------
Reading or writing tags is as simple as calling the ``read`` and ``write`` methods. Both methods accept any number of tags,
and will automatically pack multiple tags into a *Multiple Service Packet Service (0x0A)* while making sure to stay below the connection size.
If there is a tag value that cannot fit within the request/reply packet, it will automatically handle that tag independently
using the *Read Tag Fragmented (0x52)* or *Write Tag Fragmented (0x53)* requests.
Both methods will return ``Tag`` objects to reflect the success or failure of the operation.
::
class Tag(NamedTuple):
tag: str # the name of the tag, does not include ``{<# elements>}`` from request
value: Any # value read or written, may be ``None`` if an error occurred
type: Optional[str] = None # data type of tag, including ``[<# elements>]`` from request
error: Optional[str] = None # ``None`` if successful, else the CIP error or exception thrown
``Tag`` objects are considered successful (truthy) if the ``value`` is not ``None`` and the ``error`` is ``None``.
Examples::
with LogixDriver('10.20.30.100') as plc:
plc.read('tag1', 'tag2', 'tag3') # read multiple tags
plc.read('array{10}') # read 10 elements starting at 0 from an array
plc.read('array[5]{20}) # read 20 elements starting at elements 5 from an array
plc.read('string_tag') # read a string tag and get a string
plc.read('a_udt_tag') # the response .value will be a dict like: {'attr1`: 1, 'attr2': 'a string', ...}
# writes require a sequence of tuples of [(tag name, value), ... ]
plc.write('tag1', 0) # single writes do not need to be passed as a tuple
plc.write(('tag1', 0), ('tag2', 1), ('tag3', 2)) # write multiple tags
plc.write(('array{5}', [1, 2, 3, 4, 5])) # write 5 elements to an array starting at the 0 element
plc.write('array[10]{5}', [1, 2, 3, 4, 5]) # write 5 elements to an array starting at element 10
plc.write('string_tag', 'Hello World!') # write to a string tag with a string
plc.write('string_array[2]{5}', 'Write an array of strings'.split()) # write an array of 5 strings starting at element 2
plc.write('a_udt_tag', {'attr1': 1, 'attr2': 'a string', ...}) # can also use a dict to write a struct
# Check the results
results = plc.read('tag1', 'tag2', 'tag3')
if all(results):
print('They all worked!')
else:
for result in results:
if not result:
print(f'Reading tag {result.tag} failed with error: {result.error}')
.. Note::
Tag names for both ``read`` and ``write`` are case-sensitive and are required to be the same as they are named in
the controller. This may change in the future.
Unit Testing
============
``pytest`` is used for unit testing. The ``tests`` directory contains an L5X export of the testing program
that contains all tags necessary for testing. The only requirement for testing (besides a running PLC with the testing
program) is the environment variable ``PLCPATH`` for the PLC defined.
User Tests
----------
These tests are for users to run. There are a few tests that are specific to a demo
plc, those are excluded. To run them you have the following options:
with `tox`:
- modify the ``PLCPATH`` variable in ``tox.ini``
- then run this command: ``tox -e user``
or with ``pytest``:
.. code-block::
set PLCPATH=192.168.1.100
pytest --ignore tests/online/test_demo_plc.py
*(or the equivalent in your shell)*
.. Note::
Test coverage is not complete, pull requests are welcome to help improve coverage.
License
=======
``pycomm3`` is distributed under the MIT License
Raw data
{
"_id": null,
"home_page": "https://github.com/ottowayi/pycomm3",
"name": "pycomm3",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.6.1",
"maintainer_email": "",
"keywords": "",
"author": "Ian Ottoway",
"author_email": "ian@ottoway.dev",
"download_url": "https://files.pythonhosted.org/packages/3f/b2/df114dbd89e5d76b0095c4d10b981da11d788962fe325e6df349fe31698b/pycomm3-1.2.14.tar.gz",
"platform": null,
"description": "=======\r\npycomm3\r\n=======\r\n\r\n.. <<start>>\r\n\r\n.. image:: https://img.shields.io/pypi/v/pycomm3.svg?style=for-the-badge\r\n :target: https://pypi.python.org/pypi/pycomm3\r\n :alt: PyPI Version\r\n\r\n.. image:: https://img.shields.io/pypi/l/pycomm3.svg?style=for-the-badge\r\n :target: https://pypi.python.org/pypi/pycomm3\r\n :alt: License\r\n\r\n.. image:: https://img.shields.io/pypi/pyversions/pycomm3.svg?style=for-the-badge\r\n :target: https://pypi.python.org/pypi/pycomm3\r\n :alt: Python Versions\r\n\r\n|\r\n\r\n.. image:: https://img.shields.io/pypi/dm/pycomm3?style=social\r\n :target: https://pypi.python.org/pypi/pycomm3\r\n :alt: Downloads\r\n\r\n.. image:: https://img.shields.io/github/watchers/ottowayi/pycomm3?style=social\r\n :target: https://github.com/ottowayi/pycomm3\r\n :alt: Watchers\r\n\r\n.. image:: https://img.shields.io/github/stars/ottowayi/pycomm3?style=social\r\n :target: https://github.com/ottowayi/pycomm3\r\n :alt: Stars\r\n\r\n.. image:: https://img.shields.io/github/forks/ottowayi/pycomm3?style=social\r\n :target: https://github.com/ottowayi/pycomm3\r\n :alt: Forks\r\n\r\n|\r\n\r\n.. image:: https://readthedocs.org/projects/pycomm3/badge/?version=latest&style=for-the-badge\r\n :target: https://pycomm3.readthedocs.io/en/latest/\r\n :alt: Read the Docs\r\n\r\n.. image:: https://img.shields.io/badge/gitmoji-%20%F0%9F%98%9C%20%F0%9F%98%8D-FFDD67.svg?style=for-the-badge\r\n :target: https://gitmoji.dev\r\n :alt: Gitmoji\r\n\r\n\r\nIntroduction\r\n============\r\n\r\n``pycomm3`` started as a Python 3 fork of `pycomm`_, which is a Python 2 library for\r\ncommunicating with Allen-Bradley PLCs using Ethernet/IP. The initial Python 3 port was done\r\nin this `fork`_ and was used as the base for ``pycomm3``. Since then, the library has been\r\nalmost entirely rewritten and the API is no longer compatible with ``pycomm``. Without the\r\nhard work done by the original ``pycomm`` developers, ``pycomm3`` would not exist. This\r\nlibrary seeks to expand upon their great work.\r\n\r\n\r\n.. _pycomm: https://github.com/ruscito/pycomm\r\n\r\n.. _fork: https://github.com/bpaterni/pycomm/tree/pycomm3\r\n\r\n\r\nDrivers\r\n=======\r\n\r\n``pycomm3`` includes 3 drivers:\r\n\r\n- `CIPDriver`_\r\n This driver is the base driver for the library, it handles common CIP services used\r\n by the other drivers. Things like opening/closing a connection, register/unregister sessions,\r\n forward open/close services, device discovery, and generic messaging. It can be used to connect to\r\n any Ethernet/IP device, like: drives, switches, meters, and other non-PLC devices.\r\n\r\n- `LogixDriver`_\r\n This driver supports services specific to ControlLogix, CompactLogix, and Micro800 PLCs.\r\n Services like reading/writing tags, uploading the tag list, and getting/setting the PLC time.\r\n\r\n- `SLCDriver`_\r\n This driver supports basic reading/writing data files in a SLC500 or MicroLogix PLCs. It is\r\n a port of the ``SlcDriver`` from ``pycomm`` with minimal changes to make the API similar to the\r\n other drivers. Currently this driver is considered legacy and it's development will be on\r\n a limited basis.\r\n\r\n.. _CIPDriver: https://docs.pycomm3.dev/en/latest/usage/cipdriver.html\r\n\r\n.. _LogixDriver: https://docs.pycomm3.dev/en/latest/usage/logixdriver.html\r\n\r\n.. _SLCDriver: https://docs.pycomm3.dev/en/latest/usage/slcdriver.html\r\n\r\nDisclaimer\r\n==========\r\n\r\nPLCs can be used to control heavy or dangerous equipment, this library is provided \"as is\" and makes no guarantees on\r\nits reliability in a production environment. This library makes no promises in the completeness or correctness of the\r\nprotocol implementations and should not be solely relied upon for critical systems. The development for this library\r\nis aimed at providing quick and convenient access for reading/writing data inside Allen-Bradley PLCs.\r\n\r\n\r\nSetup\r\n=====\r\n\r\nThe package can be installed from `PyPI`_ using ``pip``: ``pip install pycomm3`` or ``python -m pip install pycomm3``.\r\n\r\n.. _PyPI: https://pypi.org/project/pycomm3/\r\n\r\nOptionally, you may configure logging using the Python standard `logging`_ library. A convenience method is provided\r\nto help configure basic logging, see the `Logging Section`_ in the docs for more information.\r\n\r\n.. _logging: https://docs.python.org/3/library/logging.html\r\n\r\n.. _Logging Section: https://docs.pycomm3.dev/en/latest/getting_started.html#logging\r\n\r\n\r\nPython and OS Support\r\n=====================\r\n\r\n``pycomm3`` is a Python 3-only library and is supported on Python versions from 3.6.1 up to 3.10.\r\nThere should be no OS-specific requirements and should be able to run on any OS that Python is supported on.\r\nDevelopment and testing is done primarily on Windows 10. If you encounter an OS-related problem, please open an issue\r\nin the `GitHub repository`_ and it will be investigated.\r\n\r\n.. attention::\r\n\r\n Python 3.6.0 is not supported due to ``NamedTuple`` not supporting\r\n `default values and methods <https://docs.python.org/3/library/typing.html#typing.NamedTuple>`_ until 3.6.1\r\n\r\n.. _GitHub repository: https://github.com/ottowayi/pycomm3\r\n\r\n.. <<end>>\r\n\r\nDocumentation\r\n=============\r\n\r\nThis README covers a basic overview of the library, full documentation can be found on\r\n`Read the Docs`_ or by visiting `https://pycomm3.dev <https://pycomm3.dev>`_.\r\n\r\n.. _Read the Docs: https://pycomm3.readthedocs.io/en/latest/\r\n\r\nContributions\r\n=============\r\n\r\nIf you'd like to contribute or are having an issue, please read the `Contributing`_ guidelines.\r\n\r\n.. _Contributing: CONTRIBUTING.md\r\n\r\n\r\nHighlighted Features\r\n====================\r\n\r\n- ``generic_message`` for extra functionality not directly implemented\r\n - working similar to the MSG instruction in Logix, arguments similar to the MESSAGE properties\r\n - See the examples section for things like getting/setting drive parameters, IP configuration, or uploading an EDS file\r\n - used internally to implement some of the other methods (get/set_plc_time, forward open/close, etc)\r\n- simplified data types\r\n - allows use of standard Python types by abstracting CIP implementation details away from the user\r\n - strings use normal Python ``str`` objects, does not require handling of the ``LEN`` and ``DATA`` attributes separately\r\n - custom string types are also identified automatically and not limited to just the builtin one\r\n - BOOL arrays use normal Python ``bool`` objects, does not require complicated bit shifting of the DWORD value\r\n - powerful type system to allow types to represent any CIP object and handle encoding/decoding the object\r\n\r\nLogixDriver\r\n-----------\r\n\r\n- simple API, only 1 ``read`` method and 1 ``write`` method for tags.\r\n - does not require using different methods for different data types\r\n - requires the tag name only, no other information required from the user\r\n - automatically manages request/response size to pack as many requests into a single packet\r\n - automatically handles fragmented requests for large tags that can't fit in a single packet\r\n - both support full structure reading/writing (UDTs, AOIs, etc)\r\n - for ``read`` the ``Tag.value`` will be a ``dict`` of ``{attribute: value}``\r\n - for ``write`` the value should be a dict of ``{attribute: value}`` , nesting as needed\r\n - does not do partial writes, the value must match the complete structure\r\n - not recommended for builtin type (TIMER, CONTROL, COUNTER, etc)\r\n - both require no attributes to have an External Access of None\r\n- uploads the tag list and data type definitions from the PLC\r\n - no requirement for user to determine tags available (like from an L5X export)\r\n - definitions are required for ``read``/``write`` methods\r\n- automatically enables/disables different features based on the target PLC\r\n - Extended Forward Open (EN2T or newer and v20+)\r\n - Symbol Instance Addressing (Logix v21+)\r\n - detection of Micro800 and disables unsupported features (CIP Path, Ex. Forward Open, Instance Addressing, etc)\r\n\r\nLogixDriver Overview\r\n====================\r\n\r\nCreating a driver is simple, only a ``path`` argument is required. The ``path`` can be the IP address, IP and slot,\r\nor a full CIP route, refer to the documentation for more details. The example below shows how to create a simple\r\ndriver and print some of the information collected about the device.\r\n\r\n::\r\n\r\n from pycomm3 import LogixDriver\r\n\r\n with LogixDriver('10.20.30.100/1') as plc:\r\n print(plc)\r\n # OUTPUT:\r\n # Program Name: PLCA, Device: 1756-L83E/B, Revision: 28.13\r\n\r\n print(plc.info)\r\n # OUTPUT:\r\n # {'vendor': 'Rockwell Automation/Allen-Bradley', 'product_type': 'Programmable Logic Controller',\r\n # 'product_code': 166, 'version_major': 28, 'version_minor': 13, 'revision': '28.13', 'serial': 'FFFFFFFF',\r\n # 'device_type': '1756-L83E/B', 'keyswitch': 'REMOTE RUN', 'name': 'PLCA'}\r\n\r\n\r\nReading/Writing Tags\r\n--------------------\r\n\r\nReading or writing tags is as simple as calling the ``read`` and ``write`` methods. Both methods accept any number of tags,\r\nand will automatically pack multiple tags into a *Multiple Service Packet Service (0x0A)* while making sure to stay below the connection size.\r\nIf there is a tag value that cannot fit within the request/reply packet, it will automatically handle that tag independently\r\nusing the *Read Tag Fragmented (0x52)* or *Write Tag Fragmented (0x53)* requests.\r\n\r\nBoth methods will return ``Tag`` objects to reflect the success or failure of the operation.\r\n\r\n::\r\n\r\n class Tag(NamedTuple):\r\n tag: str # the name of the tag, does not include ``{<# elements>}`` from request\r\n value: Any # value read or written, may be ``None`` if an error occurred\r\n type: Optional[str] = None # data type of tag, including ``[<# elements>]`` from request\r\n error: Optional[str] = None # ``None`` if successful, else the CIP error or exception thrown\r\n\r\n``Tag`` objects are considered successful (truthy) if the ``value`` is not ``None`` and the ``error`` is ``None``.\r\n\r\n\r\nExamples::\r\n\r\n with LogixDriver('10.20.30.100') as plc:\r\n plc.read('tag1', 'tag2', 'tag3') # read multiple tags\r\n plc.read('array{10}') # read 10 elements starting at 0 from an array\r\n plc.read('array[5]{20}) # read 20 elements starting at elements 5 from an array\r\n plc.read('string_tag') # read a string tag and get a string\r\n plc.read('a_udt_tag') # the response .value will be a dict like: {'attr1`: 1, 'attr2': 'a string', ...}\r\n\r\n # writes require a sequence of tuples of [(tag name, value), ... ]\r\n plc.write('tag1', 0) # single writes do not need to be passed as a tuple\r\n plc.write(('tag1', 0), ('tag2', 1), ('tag3', 2)) # write multiple tags\r\n plc.write(('array{5}', [1, 2, 3, 4, 5])) # write 5 elements to an array starting at the 0 element\r\n plc.write('array[10]{5}', [1, 2, 3, 4, 5]) # write 5 elements to an array starting at element 10\r\n plc.write('string_tag', 'Hello World!') # write to a string tag with a string\r\n plc.write('string_array[2]{5}', 'Write an array of strings'.split()) # write an array of 5 strings starting at element 2\r\n plc.write('a_udt_tag', {'attr1': 1, 'attr2': 'a string', ...}) # can also use a dict to write a struct\r\n\r\n # Check the results\r\n results = plc.read('tag1', 'tag2', 'tag3')\r\n if all(results):\r\n print('They all worked!')\r\n else:\r\n for result in results:\r\n if not result:\r\n print(f'Reading tag {result.tag} failed with error: {result.error}')\r\n\r\n.. Note::\r\n\r\n Tag names for both ``read`` and ``write`` are case-sensitive and are required to be the same as they are named in\r\n the controller. This may change in the future.\r\n\r\n\r\nUnit Testing\r\n============\r\n\r\n``pytest`` is used for unit testing. The ``tests`` directory contains an L5X export of the testing program\r\nthat contains all tags necessary for testing. The only requirement for testing (besides a running PLC with the testing\r\nprogram) is the environment variable ``PLCPATH`` for the PLC defined.\r\n\r\nUser Tests\r\n----------\r\n\r\nThese tests are for users to run. There are a few tests that are specific to a demo\r\nplc, those are excluded. To run them you have the following options:\r\n\r\nwith `tox`:\r\n\r\n - modify the ``PLCPATH`` variable in ``tox.ini``\r\n - then run this command: ``tox -e user``\r\n\r\nor with ``pytest``:\r\n\r\n.. code-block::\r\n\r\n set PLCPATH=192.168.1.100\r\n pytest --ignore tests/online/test_demo_plc.py\r\n\r\n*(or the equivalent in your shell)*\r\n\r\n\r\n.. Note::\r\n Test coverage is not complete, pull requests are welcome to help improve coverage.\r\n\r\n\r\nLicense\r\n=======\r\n``pycomm3`` is distributed under the MIT License\r\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "A Python Ethernet/IP library for communicating with Allen-Bradley PLCs.",
"version": "1.2.14",
"project_urls": {
"Homepage": "https://github.com/ottowayi/pycomm3"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "a851b6311236a3799e2432343a249f6f6628f4160b44881381433739c85eccd2",
"md5": "9c9d9e9c61e1aa8c7cf26936cbb16c4c",
"sha256": "49cd78b13bddf2ff234f77dc1d9048f5e139ac6fa2b77c7320aa2b90eb5c4ace"
},
"downloads": -1,
"filename": "pycomm3-1.2.14-py3-none-any.whl",
"has_sig": false,
"md5_digest": "9c9d9e9c61e1aa8c7cf26936cbb16c4c",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.6.1",
"size": 99070,
"upload_time": "2023-08-27T15:50:10",
"upload_time_iso_8601": "2023-08-27T15:50:10.849785Z",
"url": "https://files.pythonhosted.org/packages/a8/51/b6311236a3799e2432343a249f6f6628f4160b44881381433739c85eccd2/pycomm3-1.2.14-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "3fb2df114dbd89e5d76b0095c4d10b981da11d788962fe325e6df349fe31698b",
"md5": "6d2a6628007a8b4a2f979d3c7d94b751",
"sha256": "ffabe89cda3df733fc046e261c15d263134f2f35d7dbb6aedf788203a10615b7"
},
"downloads": -1,
"filename": "pycomm3-1.2.14.tar.gz",
"has_sig": false,
"md5_digest": "6d2a6628007a8b4a2f979d3c7d94b751",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.6.1",
"size": 82534,
"upload_time": "2023-08-27T15:50:12",
"upload_time_iso_8601": "2023-08-27T15:50:12.516002Z",
"url": "https://files.pythonhosted.org/packages/3f/b2/df114dbd89e5d76b0095c4d10b981da11d788962fe325e6df349fe31698b/pycomm3-1.2.14.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-08-27 15:50:12",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "ottowayi",
"github_project": "pycomm3",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"tox": true,
"lcname": "pycomm3"
}
