motor-drive-layer
Python bindings for the Motor-Drive-Layer native C++ Damiao motor driver.
The package loads the two bundled native ABI libraries through Python ctypes and exposes
SocketCAN, SocketCAN-FD, Damiao serial bridge, and optional DM_Device transports.
libmotor_abi is the generic motor layer; libarticore_runtime is the separately versioned
product safety runtime consumed by Articore SDKs.
Use articore_runtime_abi_version() and articore_runtime_capabilities() to inspect that product
runtime independently from abi_version() and abi_capabilities(). Runtime ABI 1.3 exposes the
native latest-value joint mailbox and single active trajectory engine in addition to
current_position_hold: arm safe hold snapshots fresh cached positions and rejects stale or
faulted feedback instead of replaying the previous user target.
Published wheels cover Linux x86_64/ARM64, macOS Intel/Apple Silicon, and Windows x64. The serial
transport is cross-platform; SocketCAN transports remain Linux-only.
DM-USB2FDCAN Dual works with its original dual_app firmware through
Controller.from_dm_device(device="usb2canfd-dual", channel=0, bitrate=1_000_000, data_bitrate=5_000_000). CH0 and CH1 are independently selectable, old positional arguments remain
compatible, and the loader probes both vendor v1.0 and v1.1 ABIs. The matching vendor runtime is
included in every platform wheel; no separate download command is required. Set
MOTOR_DM_DEVICE_LIB only when intentionally overriding the packaged runtime.
The current official macOS v1.1 dylib requires macOS 26, and the packaged wheel is tagged
accordingly rather than claiming compatibility with an older system.
Linux ARM64 wheels include a private libusb 1.0.27 build so the vendor v1.1 runtime can use
libusb_init_context on Ubuntu 22.04 without replacing the host's libusb 1.0.25 package.
Linux x86_64 wheels contain both v1.0 and a complete v1.1 environment using the same private
libusb together with a private compatible libstdc++. v1.0 remains the default on x86_64 because
the official v1.1 runtime batches receive callbacks at roughly 100 ms with dual_app v1.0.0.3;
set MOTOR_DM_DEVICE_ABI=v1.1 to opt in without installing any host runtime.
On final Controller close, v1.1 fully tears down its device session. The Linux v1.0 runtime instead
closes the selected channels and motor-layer resources but retains its legacy context/device until
process exit, allowing a later Controller.from_dm_device(...) call to reconnect reliably in the
same Python process. The operating system reclaims those retained vendor objects at exit because
calling the vendor destructor during static teardown can race libusb thread cleanup.
Use Motor.request_fresh_state(timeout_ms=50) when the caller must wait for a newly requested
feedback frame. For multiple motors, Controller.request_feedback_all(timeout_ms=50) sends every
request with the configured TX pacing and waits against one shared deadline; a timeout reports the
missing motor IDs. The public method internally uses the structured native entry point and raises
typed FeedbackTimeoutError, IncompleteFeedbackError, FeedbackTransportError, or
FeedbackMotorFaultError exceptions. Each remains a CallError subclass and carries a stable
error_code plus a FeedbackReport containing timeout, expected/received/missing counts, and
missing motor IDs; no caller needs to use an _ex Python method. The lower-level
request_feedback(), get_state(), and
poll_feedback_once() methods remain non-blocking asynchronous/cache operations.
For synchronized multi-channel control, ControllerGroup([ch0, ch1]) creates one persistent
native worker per Controller. send_pos_vel([...]) and send_mit([...]) dispatch typed
PosVelCommand or MitCommand values across their owning controllers, overlap independent TX
pacing waits, and return after every controller finishes. Errors retain the controller/channel,
motor ID, and native reason.
For fixed high-rate layouts, prepare_pos_vel(motors) and prepare_mit(motors) reuse one validated
ctypes command array across calls. Controller.transport_capabilities() reports the active
transport's CAN-FD, channel, parallel-send, reconnect, session-reuse, and timestamp capabilities.
Controller.transport_health() reports live connection state, TX/RX counters, errors, and last
activity ages without adding robot-product policy to the transport layer.
The motor-drive-layer-stress command provides a feedback-only DM_Device load/reconnect test and
reports latency plus Linux file-descriptor/thread counts. It never enables or commands motors.
The CLI scan command similarly uses one Controller and one batch
discover_damiao_motors() call for its entire candidate range, then uses
close_bus() plus close() so scanning never emits disable frames. The repository's
scripts/test_dm_device_scan_lifecycle.py runs 100 scan-process/CH0+CH1-reader-process cycles.
The wheel includes py.typed and .pyi declarations for editor completion and static type
checking. The main public APIs are:
Controller(...),from_socketcanfd(...),from_dm_serial(...), andfrom_dm_device(...).Controller.add_damiao_motor(...),enable_all(),disable_all(),request_feedback_all(),set_tx_gap_us(),transport_capabilities(),shutdown(), andclose_bus().ControllerGroup(...),send_pos_vel(...), andsend_mit(...)for persistent native multi-controller dispatch, plus reusable prepared batches for fixed layouts.Motor.enable(),disable(),ensure_mode(), all four control-mode send methods, fresh/cached feedback methods, typed register access, parameter aliases, andstore_parameters().MitCommand,PosVelCommand,MotorState,FeedbackStats,Mode, register metadata/constants, and SDK exception classes.
Motor is a logical child of its creating Controller. After the parent closes, motor operations
raise CallError; motor.close() can still release the handle. Both classes support context
managers. Leaving a Motor context only frees its handle, while leaving a Controller context attempts
to disable all motors before closing the bus.
See the project README for build instructions, architecture, configuration, safety guidance, and examples.
This package is distributed under the MIT License. The optional DM_Device vendor runtime is distributed separately and may have its own license terms.
1 maintainer
Metadata
1 maintainer
Release files for motor-drive-layer 0.7.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| motor_drive_layer-0.7.6-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| motor_drive_layer-0.7.6-py3-none-manylinux_2_35_aarch64.whl | Python 3 | none | Linux glibc 2.35+ ARM64 | Details |
| motor_drive_layer-0.7.6-py3-none-manylinux_2_34_x86_64.whl | Python 3 | none | Linux glibc 2.34+ x86-64 | Details |
| motor_drive_layer-0.7.6-py3-none-macosx_26_0_x86_64.whl | Python 3 | none | macOS 26.0+ x86-64 | Details |
| motor_drive_layer-0.7.6-py3-none-macosx_26_0_arm64.whl | Python 3 | none | macOS 26.0+ ARM64 | Details |
Total release size: 2.9 MB
Release files / motor_drive_layer-0.7.6-py3-none-win_amd64.whl
| Download URL | motor_drive_layer-0.7.6-py3-none-win_amd64.whl |
|---|---|
| Size | 319.4 kB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
99d46d458db5492bdb4098dde448cc1f14ebfa6b6f840913ac5169fae242a225
|
|
BLAKE2b-256 checksum How to use checksums |
0d553f9b49e2756d845849fc17ac16e7b8c0c4817cc36b2148d8b9cf9d4b8b9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Release files / motor_drive_layer-0.7.6-py3-none-manylinux_2_35_aarch64.whl
| Download URL | motor_drive_layer-0.7.6-py3-none-manylinux_2_35_aarch64.whl |
|---|---|
| Size | 514.9 kB |
| Tags | Linux glibc 2.35+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
58fa7df94e9a1d76f9fcebdd69380cb50d5701715a74d0bbed61b4e5e7c0981b
|
|
BLAKE2b-256 checksum How to use checksums |
2b1bfb8580efc3f95cc185b192ac10b2344e8195e26e97f1b01505f7c5256cc4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Release files / motor_drive_layer-0.7.6-py3-none-manylinux_2_34_x86_64.whl
| Download URL | motor_drive_layer-0.7.6-py3-none-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | Linux glibc 2.34+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
fa7e94939e18e36752a0ef36f6a348c5247473db29c496a782985c0c6e719cd8
|
|
BLAKE2b-256 checksum How to use checksums |
fa3cec64278087775632d2f93868d34653c7cb2d158c0ad7e00eb6d2844db06c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Release files / motor_drive_layer-0.7.6-py3-none-macosx_26_0_x86_64.whl
| Download URL | motor_drive_layer-0.7.6-py3-none-macosx_26_0_x86_64.whl |
|---|---|
| Size | 306.4 kB |
| Tags | Python 3 macOS 26.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
ebd8f7c2d962b19cbc492a32818f7b4a202bd9eef391097d506337e52832a930
|
|
BLAKE2b-256 checksum How to use checksums |
5807f73af72d508452ae27d05c297097784d6be9baef69dc1fb05fb413dad0ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Release files / motor_drive_layer-0.7.6-py3-none-macosx_26_0_arm64.whl
| Download URL | motor_drive_layer-0.7.6-py3-none-macosx_26_0_arm64.whl |
|---|---|
| Size | 292.0 kB |
| Tags | Python 3 macOS 26.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
52e338c67f24b3aa5c1fb92327fbe0bc553dbb94d6898b03c46c1b35e3880501
|
|
BLAKE2b-256 checksum How to use checksums |
dec3a533d6394b334036fecbfe8d1ecc3bebfd37f6778f672d49b5d6b8a378af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
