Releases: ottowayi/pycomm3
Releases · ottowayi/pycomm3
0.11.0
- mypy support added @EduardoHi
LogixDriver
- added array support for non-string data types for the
data_format
ingeneric_message
- e.g.
data_format=[('example', 'SINT[5]'), ]
- e.g.
- added
string
(2-byte len) andlogix_string
(4-byte len) support fordata_format
ingeneric_message
- improved error messages for bad tag names, fix ambiguous
'Invalid tag request - 'plc_tag'
error message
SLCDriver
- added
get_file_directory
- confirmed working for SLC and MLX1100, other MLX models will require help from someone with the hardware to debug against
- added r/w support for L/ST/A files
0.10.2
0.10.1
0.10.0
0.9.2
0.9.1
- removed autologging dependency
- changed minimum Python version to 3.6.1 due to bug w/ NamedTuples
- some internal restructure and refactoring
- improved some exception handling and raising
- multi-request read/write calls now only filter RequestError and DataError, other exceptions will have to be handled by the user
0.9.0
- restructured some modules, there is now a CIPDriver class that LogixDriver inherits from
- CIPDriver handles session registrations, forward open/close, generic_message, etc
- possibly to be used as a base for a SLC/Micrologix driver
- fixed issue with improper unpacking of session ID that would sometime cause a crash
- set minimum Python version to 3.6.1
- 3.6 had a bug with overloading methods in NamedTuple that broke checking validity of Tag objects
- [Breaking Change] list_identity method now returns a dict with the full identity object, not just a string of the product name
0.8.1
- replaced the generic_read/generic_write method with a single generic_message method
- it should now work properly, the previous methods did not always
- replaced some internal methods to use generic_message instead of manually building the requests
- tested getting/setting drive parameters from a PF525
- updated documentation
- lots of internal changes and restructuring
0.7.1
0.7.0
- fix for incorrectly parsing arrays of structures inside structures
- fix for improper packing/parsing strings with lengths not aligned to 4-byte boundaries
- [EXPERIMENTAL] added support for writing of full structures
- value should be a sequence of values for each tag in a structure, nesting as needed
- does not read tag first, starts with a zero-filled struct. application responsibility to get the current values.
- does not validate value matches data type definition, only throws exception if unable to pack value using definition
- not recommended for built-in types (TIMER, COUNTER, etc)