FlexSEA Python device interface
SoftwareFlexSEA provides a Python device interface for Dephy wearable robotics, including data acquisition and controller-facing calls. [1] [2] [3] [4] [5] [6]
Installation & first result →Official websiteGetting started
- Source rights
- Named licenses are documented by part. Review licenses
- Unknowns
- operating system, compute requirements not fully established. Review gaps
Source researched · Not tested by us
Sources checked · Research details
Licenses & related hardware
Overview
FlexSEA provides a Python device interface for Dephy wearable robotics, including data acquisition and controller-facing calls. Its concrete contribution is inspectable Python device/version/platform handling. It is not evidence that the complete device engine, firmware or physical wearable design is released as source. [1] [4] [5]
Is this for you?
- Known limitations
- ReleasedPythoninterface delegates devicecore toprecompiledsharedlibrary; completeengine source/terms notestablished.
- Pythoninstallation alone doesnotvalidatebinarycompatibility, motorcontrol or error-triggeredshutdown.
- Selecteddemo activelyrampsvoltage; normal-end cleanup and stopMotorOnDisconnectFalse are not safeinterruption proof.
Editorial assessment of cited source; no runtime or hardware test.
What you need
Installation & first result
Open the upstream getting-started guide [1] [2] [3] [4] [5] [6]
- Inspect demos/demo1_open_control.py without executing it; match firmwareVersion/port toDevice and the selected sharedlibrary.
- Review baudRate/libFile/s3Timeout and disconnect/exception cleanup before any connected-device experiment; demo activelycommandsvoltage.
Editorial assessment of cited source; no runtime or hardware test.
- Installation
Python ^3.11 per Poetry metadata; selected Device interface additionally loads a version/platform-specific precompiled library lazily from S3 or a local libFile. No binary/environment installed.
Documented source requirements/route, not installation or compatibility reproduced by this catalog.
Project notes
A Python environment does not supply the whole device stack
The selected Poetry metadata declares flexsea 12.2.3 and Python ^3.11, with platform/version-sensitive dependencies such as pyudev and pendulum. Preserve that metadata with the chosen source rather than applying a historical Python requirement to the current checkout. The README links installation and quickstart documentation; those linked full procedures were not reproduced here. [1] [3]
The Device source explicitly explains that its C/C++ shared library is precompiled and downloaded lazily from S3. The library utility resolves a requested version/platform and loads it with ctypes, with a local-library path as another configuration boundary. Inspect device firmware, host architecture and the selected library identity before treating a successfully installed Python package as a usable device interface. The source expands partial version requests and can substitute another version within the requested major version. Starting with v12, development-version matching affects motor commands; the library utility notes different development builds uploaded under 12.0.0 with different exposed functions. Matching the firmware version alone therefore does not establish development-build compatibility or motor-command availability. This review did not resolve the correct binary for a particular device, or download/load one. [4] [5]
Inspect the demo and failure behavior for the chosen device
The README orders its demos progressively and distinguishes developer unit tests from integration scripts. A test filename or an example controller does not establish that a wearable was connected or its shutdown behavior works. A concrete inspection route is demos/demo1_open_control.py: it asks for firmwareVersion and port, constructs Device with those fields, opens the connection and actively ramps commanded motor voltage. It is not a passive connection check. The Device constructor additionally exposes baudRate, libFile for a local shared-library override and s3Timeout; stopMotorOnDisconnect defaults to false. Match firmware/library identity and inspect failure cleanup before considering this demo. Its explicit stop_motor/close calls occur at normal completion rather than inside an encompassing finally block. These are source behaviors, not shutdown testing or recommended voltage settings. No device, data acquisition, controller loop or integration test was exercised here. [4] [6] [1] [4]
The Python contribution has an MIT notice. That declaration should not be transferred automatically to the separately obtained binary core, firmware, hardware or recordings. No complete binary-engine source, physical safety, calibration or medical suitability was established. [2] [4]
What we checked
Source/document review only; no build, installation, binary/device/network execution, control commissioning or performance test.
Not yet established
- Requirements: operating system, host computer
- Version-specific hardware compatibility (ecosystem tags alone do not establish it)
Updates
- Upstream last updated
- Not established
- Latest release
- Not established
- Profile updated
- Nov 1, 2026
- Sources last checked
- Nov 1, 2026
- Next review
- Dec 1, 2026
- Reviewed revision
0129afc
Source files and licenses
Narrow source-available robotics interface or research implementation; gaps in licensing, binary core or physical setup are explicitly separate from the inspectable contribution.
| Layer | Availability / license |
|---|---|
| software | available · MIT Python interface; external binary core separate Scoped repository declaration; external binary engines, firmware, hardware and dependencies retain separate rights. No full-stack openness or operational claim. [1] [2] [3] [4] [5] [6] |
| documentation | available · MIT Python interface; external binary core separate Scoped repository declaration; external binary engines, firmware, hardware and dependencies retain separate rights. No full-stack openness or operational claim. [1] [2] [3] [4] [5] [6] |
No separate physical design, pretrained distribution or dataset is selected as the released contribution in this scoped software review.
References
Each source links to the exact revision we read. “Used for” shows where this page relies on it.
- S001 README.md
Revision, date & where cited
DephyInc/actuator-package contributors · github.com · revision
0129afc· README.md at · Accessed Nov 1, 2026
Used for: Overview, Is this for you?, What you need, Installation & first result and 3 more - S002 LICENSE
Revision, date & where cited
DephyInc/actuator-package contributors · github.com · revision
0129afc· LICENSE at · Accessed Nov 1, 2026
Used for: Is this for you?, What you need, Installation & first result, Inspect the demo and failure behavior for the chosen device and 1 more - S003 pyproject.toml
Revision, date & where cited
DephyInc/actuator-package contributors · github.com · revision
0129afc· pyproject.toml at · Accessed Nov 1, 2026
Used for: Is this for you?, What you need, Installation & first result, A Python environment does not supply the whole device stack and 1 more - S004 flexsea/device.py
Revision, date & where cited
DephyInc/actuator-package contributors · github.com · revision
0129afc· flexsea/device.py at · Accessed Nov 1, 2026
Used for: Overview, Is this for you?, What you need, Installation & first result and 3 more - S005 flexsea/utilities/library.py
Revision, date & where cited
DephyInc/actuator-package contributors · github.com · revision
0129afc· flexsea/utilities/library.py at · Accessed Nov 1, 2026
Used for: Overview, Is this for you?, What you need, Installation & first result and 2 more - S006 demos/demo1_open_control.py
Revision, date & where cited
DephyInc/actuator-package contributors · github.com · revision
0129afc· demos/demo1_open_control.py at · Accessed Nov 1, 2026
Used for: Is this for you?, What you need, Installation & first result, Inspect the demo and failure behavior for the chosen device and 1 more
Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5