solarian-arm1
solarian-arm1 is a 6-DOF arm module for Solarian. It is a modification of an
existing open-source arm, the SO-100 by The Robot Studio.
The mod adds one degree of freedom in the wrist, a yaw joint the original design
does not have. Joints use Feetech STS servos
(shoulder_pan, shoulder_lift, elbow_flex, wrist_flex, wrist_yaw,
wrist_roll). The gripper is a separate module — typically
solarian-gripper1,
mated flange-to-flange.
Installation
pip install -e plugins/solarian-feetech
pip install -e plugins/solarian-arm1
Module
| Entry point | Class | Role |
|---|---|---|
arm-1 |
Arm1Module |
6 joints + Mink IK (x..rz) |
Default YAML lives at solarian_arm1/conf_arm.yaml. Copy it into a project's
conf/ (for example right_arm.yaml) and set the serial port / servo ids.
from solarian.core.robot import Robot
from solarian.sim import SceneConfig, ModuleAttachment
from solarian_arm1 import ARM_MJCF_PATH
from solarian_arm1.arm import Arm1Module
from solarian_gripper1 import MJCF_FEETECH_PATH as GRIPPER_MJCF
from solarian_gripper1.gripper_feetech import Gripper1FeetechModule
class Arm1Robot(Robot):
right_arm = Arm1Module(ik_tcp=Gripper1FeetechModule.tcp_from_flange)
right_gripper = Gripper1FeetechModule()
scene = SceneConfig(
attachments=[
ModuleAttachment(
module="right_arm",
mjcf=ARM_MJCF_PATH,
prefix="right/",
),
ModuleAttachment(
module="right_gripper",
mjcf=GRIPPER_MJCF,
parent_site="right/flange",
child_site="flange",
prefix="right_gripper/",
),
],
)
The arm MJCF exports a flange site (CAD Frame). Attach a gripper by aligning
both models' flange frames. IK tracks flange plus the tool's
tcp_from_flange offset (CAD tcp in the gripper's mate frame). The scene
still attaches the gripper MJCF for physics and cameras.
Onshape export
Re-export after a CAD change (needs Onshape API credentials):
solarian onshape-export plugins/solarian-arm1/solarian_arm1/assets/arm1_description
solarian onshape-export plugins/solarian-arm1/solarian_arm1/assets/arm1_description --clean-only
That writes solarian_arm1/assets/arm1.xml. Use --update-yaml to sync
joint limits into a project's arm config:
solarian onshape-export plugins/solarian-arm1/solarian_arm1/assets/arm1_description \
--update-yaml projects/arm1/conf/modules/right_arm.yaml
CAD mates should be named shoulder_pan … wrist_roll. Keep a Frame named
flange on the wrist for gripper attachment. Put the tool TCP Frame on the
gripper assembly (name it tcp), not on the arm.
wrist_roll is 0-centered (±π) in arm1.xml / config.json even though
CAD exports [-2π, 0]. solarian.prefer_config_limits keeps that override
on re-export so home can roll both ways.
License
Apache License 2.0. Copyright 2026 PrimaryKey Inc. The mechanical
design and meshes in solarian_arm1/assets/ are derived from the
SO-ARM100 by The Robot Studio
(Apache 2.0) and modified; see NOTICE. solarian-arm1 is not
affiliated with, sponsored by, or endorsed by The Robot Studio or Hugging Face.
Solarian, Solarian Arm and the Solarian logo are trademarks of PrimaryKey Inc. See the trademark policy.
Metadata
Release files for solarian-arm1 0.2.2
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_arm1-0.2.2.tar.gz | 13.4 MB | With provenance | Details for solarian_arm1-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| solarian_arm1-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for solarian_arm1-0.2.2-py3-none-any.whl |
Total release size: 26.8 MB
Release files / solarian_arm1-0.2.2.tar.gz
| Download URL | solarian_arm1-0.2.2.tar.gz |
|---|---|
| Size | 13.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc61b03b04e02b5aea26d03f823f3e6e8d6de0abd4c8e67f463566aefbbe6491
|
|
BLAKE2b-256 checksum How to use checksums |
03ddfa5acb055cc4ccca2862baaa97b20db8332fda009d6849462249eb0bd31b
|
| 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 16, 2026.
Transparency logRelease files / solarian_arm1-0.2.2-py3-none-any.whl
| Download URL | solarian_arm1-0.2.2-py3-none-any.whl |
|---|---|
| Size | 13.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
427984bc0e816def4a51f45437d33561890fcbd98a0f0b6c68611fea0d2fbf83
|
|
BLAKE2b-256 checksum How to use checksums |
45aacca3b7e23fb178b7c295ca7772a307e2577b03a9dfead0a7d288282fdea1
|
| 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 16, 2026.
Transparency logSecurity for solarian-arm1 0.2.2
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_arm1-0.2.2.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 16, 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.