solarian-gripper1
A parallel gripper module for the Solarian framework. Two fingers, one actuator; you command it by the desired finger aperture in millimetres and the module handles the conversion for both real hardware and simulation.
The plugin ships two actuator variants that share the same finger kinematics and aperture command space:
| Variant | Module | Default config | MJCF |
|---|---|---|---|
| Feetech STS | Gripper1FeetechModule |
conf_gripper_feetech.yaml |
assets/gripper1.xml |
| Robstride L7 | Gripper1RobstrideModule |
conf_gripper_robstride.yaml |
assets/gripper1_robstride.xml |
Installation
pip install solarian-gripper1 # Feetech variant
pip install "solarian-gripper1[hardware]" # plus the Feetech servo SDK, on the machine wired to the gripper
The Robstride variant needs solarian-robstride, which is not on PyPI yet.
Install it from source alongside the gripper:
pip install -e "plugins/solarian-robstride[hardware]"
pip install -e "plugins/solarian-gripper1[robstride]"
How it works
- Each module exposes a single actuator (
gripper), matching the single physical servo. It converts an aperture command (mm) into the servo's normalized command space and writes that. Each backend maps normalized → physical:- Real: normalized → servo counts via the actuator calibration.
- Sim: normalized → the
left_manifold_to_railprismatic joint via thesim:block in the variant's yaml.
- Each MuJoCo model actuates only that one joint; an
<equality>constraint (ratio −1, generated by onshape-to-robot from the CAD mate relation) drives the opposite finger, so one command opens/closes both jaws symmetrically.
Regenerating the sim model from Onshape
Each variant has its own CAD assembly (mates + limits + the linear finger relation). Re-export after a CAD change with:
# Feetech
solarian onshape-export plugins/solarian-gripper1/solarian_gripper1/assets/gripper1_description
solarian onshape-export plugins/solarian-gripper1/solarian_gripper1/assets/gripper1_description --clean-only
# Robstride
solarian onshape-export plugins/solarian-gripper1/solarian_gripper1/assets/gripper1_robstride_description
solarian onshape-export plugins/solarian-gripper1/solarian_gripper1/assets/gripper1_robstride_description --clean-only
The Feetech export writes solarian_gripper1/assets/gripper1.xml; the Robstride
export writes solarian_gripper1/assets/gripper1_robstride.xml. The driven joint
left_manifold_to_rail has range [0, 0.0545] m (0 = fingers apart / open,
0.0545 = fingers together / closed).
Using it in a robot
- Attach the model in your robot's sim
SceneConfig, with aprefixmatching the one in the gripper yaml (gripper/):
from solarian.sim import SceneConfig, ModuleAttachment
from solarian_gripper1 import MJCF_FEETECH_PATH as GRIPPER_MJCF
from solarian_gripper1.gripper_feetech import Gripper1FeetechModule
class MyRobot(Robot):
is_sim = True
gripper = Gripper1FeetechModule()
scene = SceneConfig(
attachments=[
ModuleAttachment(
module="gripper",
# Loaded straight from the installed plugin (meshes resolve
# relative to the MJCF) -- no need to copy the model into your
# project, so there's a single source of truth.
mjcf=GRIPPER_MJCF,
parent_body="right/wrist_flange", # the arm flange body
prefix="gripper/",
),
],
)
For the Robstride variant, import Gripper1RobstrideModule and
MJCF_ROBSTRIDE_PATH instead. The Feetech MJCF attaches at the flange site;
the Robstride MJCF attaches at the base site.
The Feetech MJCF exports CAD Frames as sites: flange (mate to the arm),
camera (wrist lens), and tcp (tool center point). Pass
Gripper1FeetechModule.tcp_from_flange to the arm as ik_tcp so IK tracks
the flange plus that CAD offset.
Site-mate example (solarian-arm1 and this gripper both export a flange Frame):
ModuleAttachment(
module="right_gripper",
mjcf=GRIPPER_MJCF,
parent_site="right/flange",
child_site="flange",
prefix="right_gripper/",
)
-
Copy the matching yaml (
conf_gripper_feetech.yamlorconf_gripper_robstride.yaml) into your project'sconf/and set the realport/id, then runsolarian calibrateon the gripper: sweep the full closed↔open travel, then move to the fully closed pose when asked sodrive_modematchesaperture_closed_mm/aperture_open_mm. -
Run
solarian calibrate-gripper-rangesand read a ruler at each stop. This recordsaperture_table, the measured aperture curve. Skipping it leaves the module interpolating a straight line between the two endpoints, which the linkage does not follow. -
Command the gripper by aperture in mm — send a waypoint whose
grippervalue is the aperture (e.g.85= fully open,0= closed). Read the current aperture withmodule.read_aperture().
Configuration
Fields specific to both modules:
aperture_table— ruler-measurednorm/aperture_mmpairs written bysolarian calibrate-gripper-ranges. When present it defines the travel and the mm ↔ normalized map, superseding the two endpoint fields below.aperture_closed_mm/aperture_open_mm— physical fingertip separation at the two ends of travel, used for a straight-line map until a table is measured. Keep them consistent with the servo calibration and thesim:joint range.actuators.gripper.sim— maps the servo togripper/left_manifold_to_rail,range_min: 0.0/range_max: 0.0545(the joint limits),drive_mode: 1so normalized -100 = closed, 100 = open.interpolator_type: scalar— GripperModule interpolates aperture in mm.
License
Apache License 2.0. Copyright 2026 PrimaryKey Inc. Parts of the
mechanical design and meshes in solarian_gripper1/assets/ are derived from
the UMI Gripper
and UMI Soft Finger
of the Universal Manipulation Interface (UMI)
project, and the Robstride L7 drive from RobStride's
EDULITE_A3 (MIT), and modified; see
NOTICE. solarian-gripper1 is not affiliated with, sponsored by, or
endorsed by UMI, its authors, Stanford University, Columbia University, Toyota
Research Institute or RobStride.
Solarian and the Solarian logo are trademarks of PrimaryKey Inc. See the trademark policy.
Metadata
Release files for solarian-gripper1 0.2.1
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 |
|---|---|---|---|---|
| solarian_gripper1-0.2.1.tar.gz | 3.1 MB | With provenance | Details for solarian_gripper1-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| solarian_gripper1-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for solarian_gripper1-0.2.1-py3-none-any.whl |
Total release size: 6.1 MB
Release files / solarian_gripper1-0.2.1.tar.gz
| Download URL | solarian_gripper1-0.2.1.tar.gz |
|---|---|
| Size | 3.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
597fbc56d80e41d5f5457e08e78cda2c112cbb99fa5ac20ea769f460606c7805
|
|
BLAKE2b-256 checksum How to use checksums |
1576c09deeabb05fc334d3c0da77fc0d7389a86139664c43d28068bca3e9c65a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 13, 2026.
Transparency logRelease files / solarian_gripper1-0.2.1-py3-none-any.whl
| Download URL | solarian_gripper1-0.2.1-py3-none-any.whl |
|---|---|
| Size | 3.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f73a914adca502dd2983e6b526857c24f7742eca75b4edf1813b636e0e7bde20
|
|
BLAKE2b-256 checksum How to use checksums |
7d37c6a7da2403d5ffa4b1814fab3ce8a25c212d8381ba343a98e02c1bbd5525
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 13, 2026.
Transparency logSecurity for solarian-gripper1 0.2.1
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
Both files in this release have been uploaded with provenance metadata.
Attestation for solarian_gripper1-0.2.1.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 Nov 13, 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.