Pycomm3

Latest version: v1.2.14

Safety actively analyzes 633433 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 9

0.5.5

- fix for single or fragmented failed reads not showing the service/command error properly
- it would try and parse a non-existent value, any exceptions thrown during that would override the CIP error

0.5.4

- fixed issue for reading the tag list on PLCs below v18.
- ExternalAccess attribute 10 for the Symbol Object was added in v18, it will be skipped if firmware is below that version
- required ``init_info`` to be True to work automatically, else set ``plc.info['version_major'] = 17``

0.5.3

- minor refactoring
- added initial string support for Micro800s
- minor updates to documentation
- started adding examples to docs, still very early and will be adding more thorough documentation in the future

0.5.2

- fix for bug introduced in 0.5.1
- micor800 flag disables use of instance ids and read of plc name on init

0.5.1

- added ``micro800`` option to LogixDriver, support needs testing
- added automatic retry of with a standard Forward Open if and Extended Forward Open fails
- removes requirement to set ``large_packets=False`` in constructor
- module refactoring
- some initial documentation started
- removed the COM server stuff, if this is a wanted feature it may be re-added in the future.

0.5.0

- replaced the separate ip address and slot args with a single required path argument.
- the new path arg allows full CIP paths, see readme for examples

After adding CIP routing support it seemed unnecessary to have separate ip address and slot arguments, so I chose to remove them and replace with a single path variable. Unfortunately, this is a breaking change for anyone using a PLC not in slot 0. The idea was that the path would look similar to what shows up in Logix. I kept shortcuts for just the IP address or 'IP/slot', so you will not need to add the backplane part to the path if staying the same rack. Hopefully this does not cause many issues, I believe this change was the better approach and it provides a cleaner solution.

Page 7 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.