Control of Mitsubishi RV6S robot at CIIRC CTU
How to start the robot
- Turn the robot power using the white switch on the front panel of the control unit.
- Make sure robot is set to Automatic mode (or Ext. Automatic mode) - modes are controlled by key switch on the front panel.
Quick example
from ctu_mitsubishi import Rv6s, Rv6sGripper
gripper = Rv6sGripper()
gripper.open()
gripper.close()
robot = Rv6s()
robot.initialize()
q = robot.get_q()
q[0] += 0.1
robot.move_to_q(q)
robot.stop_robot()
robot.close_connection()
See more examples in the examples folder.
For the complete documentation see https://robotics-robot-stations.readthedocs.io/
For developers
git clone git@github.com:CTURobotics/ctu_mitsubishi.git
cd ctu_mitsubishi
uv sync
uv pip install -e ".[dev]"
pre-commit install
Metadata
Release files for ctu-mitsubishi 0.1.5
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 |
|---|---|---|---|---|
| ctu_mitsubishi-0.1.5.tar.gz | 9.6 kB | With provenance | Details for ctu_mitsubishi-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ctu_mitsubishi-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for ctu_mitsubishi-0.1.5-py3-none-any.whl |
Total release size: 19.3 kB
Release files / ctu_mitsubishi-0.1.5.tar.gz
| Download URL | ctu_mitsubishi-0.1.5.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60c18992d25d5a333759f9eea9b1f2e8c79bc1348717fd5bee8fe91bcd173fa8
|
|
BLAKE2b-256 checksum How to use checksums |
341fb7e86f3e15bbf563da9ad92261418d778998089382dbfecd93419addc619
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 9, 2025.
Transparency logRelease files / ctu_mitsubishi-0.1.5-py3-none-any.whl
| Download URL | ctu_mitsubishi-0.1.5-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eea7782b1b55651eb1f566eb0b3bc63eb837f32730302bf0cb883d129ff346f8
|
|
BLAKE2b-256 checksum How to use checksums |
dfd8ba08dba5e86570c6c81137a18a15990029c97588b70a821e201bca9346cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 9, 2025.
Transparency logSecurity for ctu-mitsubishi 0.1.5
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 ctu_mitsubishi-0.1.5.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 9, 2025.
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.