This release is a pre-release and may not be stable for production use.
menlo-sdk
Python SDK for Menlo robots. Supports Asimov 1.
Requirements
- Python 3.12 or newer.
- Optional, only for the calls that use them: Pillow for
Frame.to_jpeg(), NumPy forFrame.to_numpy(), OpenCV (opencv-python) forClip.save_mp4().
Installation
pip install menlo-sdk
Usage
Connect with the robot's address:
from menlo.asimov import ConnectionConfig, NotReadyError, Robot, UdpConfig
config = ConnectionConfig(udp=UdpConfig(host="192.168.22.32"))
Read the robot's state. This sends nothing:
with Robot(config).connect() as robot:
print(robot.get_state().mode.name) # DAMP, STAND or MOVE
Put the robot in STAND: the actuators hold a standing pose, with no balancing. The robot
must hang from its gantry hook with both feet on the floor. stand() returns once the robot
is in STAND and armed:
with Robot(config).connect() as robot:
robot.stand()
Put the robot in MOVE: the walking policy balances it in place. balance() returns once the
robot reports MOVE:
with Robot(config).connect() as robot:
robot.balance()
Walk: in MOVE the robot follows the velocity you send, here 0.3 m/s forward for 3 s. A walk
needs 2 m of clear floor ahead, and Asimov Manager open at the E-Stop. set_velocity()
returns once the 3 s are over and zero velocity is sent. balance() keeps the robot in MOVE
at zero velocity, balancing in place:
with Robot(config).connect() as robot:
robot.set_velocity(vx=0.3, duration=3.0)
robot.balance()
Put the robot in DAMP: every actuator stops holding its position, so a standing robot falls. Only do this with the robot supported, hanging from its gantry hook or seated on a bench:
with Robot(config).connect() as robot:
robot.damp()
When the robot cannot do a command now, the command raises NotReadyError and sends nothing:
with Robot(config).connect() as robot:
try:
robot.set_velocity(vx=0.3, duration=3.0)
except NotReadyError as exc:
print(exc) # not ready to move: the robot is in STAND; balance() it first (wrong_mode)
Documentation
- Python SDK on Asimov 1: installing the SDK and running the examples on Asimov 1.
- Python SDK guide: the full documentation.
- Safety: what to check before a script moves the robot.
- Examples: demos of the SDK's features.
- Changelog: the changes in each release.
Security
To report a vulnerability, see SECURITY.md.
License
Apache License 2.0. See LICENSE.
Metadata
Release files for menlo-sdk 0.1.0rc8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| menlo_sdk-0.1.0rc8.tar.gz | 255.5 kB | With provenance | Details for menlo_sdk-0.1.0rc8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| menlo_sdk-0.1.0rc8-py3-none-any.whl | Python 3 | none | any | Details for menlo_sdk-0.1.0rc8-py3-none-any.whl |
Total release size: 366.3 kB
Release files / menlo_sdk-0.1.0rc8.tar.gz
| Download URL | menlo_sdk-0.1.0rc8.tar.gz |
|---|---|
| Size | 255.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c6d07a18e057b1773739ec4667f300c0bfc10aed55e989b0602beb220642849
|
|
BLAKE2b-256 checksum How to use checksums |
dccc795983f76356064c74965ed5c250125259cd5221d5b4e257548ee83bcff1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / menlo_sdk-0.1.0rc8-py3-none-any.whl
| Download URL | menlo_sdk-0.1.0rc8-py3-none-any.whl |
|---|---|
| Size | 110.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
41d48f942fd688c457c10640bb0cff91be04483a63f88cb187abdaf3f21dbdcd
|
|
BLAKE2b-256 checksum How to use checksums |
da68fe23fc06151216d9a55563f52b579326384690a8094ff3b86ff6f9cacd99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logSecurity for menlo-sdk 0.1.0rc8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for menlo_sdk-0.1.0rc8.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.