Endaq-device

Latest version: v1.3.2

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

Scan your dependencies

Page 1 of 2

1.3.2

User-facing changes:
* Fixes an issue with imported configuration combining with, rather than replacing, current configuration.

Notable internal changes:
* Configuration file I/O abstracted for future remote configuration functionality.
* Added new `SystemStateCode` element to the command/response schema (used by upcoming firmware).
* Standardized EBML `DocType` naming scheme.
* Cleanup (docstrings, type annotations, etc.)

1.3.1

What's Changed
* Changes the version requirements for `psutil` to handle changes in version 6.


**Full Changelog**: https://github.com/MideTechnology/endaq-device/compare/1.3.0...1.3.1

1.3.0

Version 1.3.0 primarily fixes bugs, makes improvements, and paves the way for future hardware/firmware features.

* Adds `timeout` parameter to several device clock-based commands.
* Adds device status codes generated by new enDAQ firmware.
* Abstracts the mechanism for retrieving device information (for upcoming remote device control).
* Fixes occasional timeout issues with commands that reset devices, or start/stop recording.
* Fixes `endaq.device.fromRecording()` issue that caused problems in enDAQ Lab's *Recording Properties*.
* Expands compatibility for devices with various combinations of old hardware and old firmware.
* Fixes/improves configuration import/export.
* Makes various command method signatures match across `CommandInterface` subclasses.
* Includes various documentation edits and improvements.
* Other minor bug fixes and improvements.

Existing scripts using previous versions of `endaq.device` should still work. However, the fixes to certain command timeouts constitute a minor change in behavior, and existing scripts that rely upon/work around the previous timeout behavior may need minor refactoring.

**Full Changelog**: https://github.com/MideTechnology/endaq-device/compare/1.2.0...1.3.0

1.2.0

Version 1.2.0 adds several new features supporting an upcoming firmware release.

* Support for finding and identifying devices connected via their serial command interface, but not mounted as drives (e.g., devices currently recording).
* Lock ID support in `CommandInterface` (`getLockID()`, `setLockID()`, `clearLockID()`): A weakly-enforced mechanism for one process to 'claim' a recording device.
* `CommandInterface.stopRecording()`: Devices that maintain a serial connection while recording can now be stopped via software.
* More consistent exception handling.
* More consistent use of command `callback` and `timeout` parameters.
* Various optimizations and minor bug fixes.
* Documentation and annotation improvements.

Additionally, several internal systems have been refactored for future firmware support. These should not affect functionality of existing code, provided it does not access 'private' attributes and methods.

1.1.1

What's Changed
* Improved thread safety.
* Callback functions and timeouts in the command interfaces now handled more consistently.
* Command status/response codes now use `enum`s; they are functionally identical, but more clear to humans.
* Various documentation fixes and improvements.

**Full Changelog**: https://github.com/MideTechnology/endaq-device/compare/1.1.0...1.1.1

1.1.0

* Several `CommandInterface` additions and changes were made. The changes may create minor incompatibilities with existing code that uses `Recorder.command`.
* The 'timeout' behavior for commands has been made more consistent. The `SerialCommandInterface` attribute `timeout` is now exclusively the low-level serial timeout, and is no longer the default timeout for some commands.
* Commands that do not require a response will return a response if one is received. These commands will still return `None` if no response is received before timing out.
* Added the `blink()` command, intended for indicating specific devices when multiple recorders are plugged in. Note that the current firmware does not support the command, and only devices with a `SerialCommandInterface` will accept it.
* `endaq.device.findDevice()` now has the keyword argument `chipId` for getting an attached recording device by its unique processor ID.
* Documentation has been expanded and improved.

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.