From e60ad6d344d75f458d8f9fee2cd25bbbc5391216 Mon Sep 17 00:00:00 2001 From: Anton Deguet Date: Thu, 30 Nov 2023 21:45:39 -0500 Subject: [PATCH] Update README.md #48 --- dvrk_python/README.md | 105 +----------------------------------------- 1 file changed, 1 insertion(+), 104 deletions(-) diff --git a/dvrk_python/README.md b/dvrk_python/README.md index cdf928e8..f53efe2c 100644 --- a/dvrk_python/README.md +++ b/dvrk_python/README.md @@ -1,104 +1 @@ -## Introduction - -The dVRK Python package is based on the CRTK Python ROS client library: https://github.com/collaborative-robotics/crtk_python_client. The API is following the CRTK conventions: https://github.com/collaborative-robotics/documentation/wiki/Robot-API-motion. - -This directory contains: -* dvrk_python module. This modules defines the class `robot` which uses the dVRK ROS topics to communicate with the `dvrk_console_json` application included in the `dvrk_robot` ROS package. -* tutorial examples. Python scripts using the `dvrk_python` module. - -## Requirements - -You will need to build the dVRK software stack using the ROS catkin build tools, see https://github.com/jhu-dvrk/sawIntuitiveResearchKit/wiki/CatkinBuild - -The `dvrk_python` package is included in the `dvrk_ros` git repository. Please checkout the whole `dvrk_ros` repository and build it using the catkin build tools (don't use `catkin_make`). - -The dVRK Python ROS client now relies on CRTK so you will also need the following packages: -* https://github.com/collaborative-robotics/crtk_msgs -* https://github.com/collaborative-robotics/crtk_python_client - -If you followed the dVRK build instructions above, these CRTK packages are likely already installed in your workspace - -## Runtime - -You first need to start the dVRK console application: -```sh - rosrun dvrk_robot dvrk_console_json -j your_console_config_file.json -``` - -Once the console is running, you can check which arms are available using the `rostopic` command: -```sh - rostopic list -``` - -You should see one namespace per arm, e.g. `/PSM1`, `/MTML` and/or `/ECM` based on your console configuration. - -Then in Python: -```python -import dvrk -# Create a Python proxy for PSM1, name must match ros namespace -p = dvrk.psm('PSM1') - -# You can home from Python -p.enable() -p.home() - -# retrieve current info (numpy.array) -p.measured_jp() -p.measured_jv() -p.measured_jf() - -# retrieve PID desired position and effort computed -p.setpoint_jp() -p.setpoint_jf() - -# retrieve cartesian current and desired positions -# PyKDL.Frame -p.measured_cp() -p.setpoint_cp() - -# move in joint space -# move is absolute (SI units) - -# move multiple joints -import numpy -p.move_jp(numpy.array([0.0, 0.0, 0.10, 0.0, 0.0, 0.0])) - -# move in cartesian space -import PyKDL -# start position -goal = p.setpoint_cp() -# move 5cm in z direction -goal.p[2] += 0.05 -p.move_cp(goal).wait() - -import math -# start position -goal = p.setpoint_cp() -# rotate tool tip frame by 25 degrees -goal.M.DoRotX(math.pi * 0.25) -p.move_cp(goal).wait() -``` - -To apply wrenches on MTMs, start ipython and type the following commands while holding the MTM (otherwise the arm will start moving and might bang itself against the console and get damaged). - -```python -# load and define the MTM -from dvrk import mtm -m = mtm('MTML') - -# When True, force direction is constant. Otherwise force direction defined in gripper coordinate system -m.set_wrench_body_orientation_absolute(True) - -# about 2N force in y direction -m.body.servo_cf(numpy.array([0.0, 0.0, 2.0, 0.0, 0.0, 0.0])) - -# lock the MTM wrist orientation -m.lock_orientation_as_is() - -# turn gravity compensation on/off -m.set_gravity_compensation(True) - -# turn off forces -self.arm.body.servo_cf(numpy.array([0.0, 0.0, 0.0, 0.0, 0.0, 0.0])) -``` -To access arm specific features (e.g. PSM, MTM, ...), you can use the derived classes `psm` or `mtm`. For example `from dvrk.psm import *`. +See https://github.com/jhu-dvrk/sawIntuitiveResearchKit/wiki/PythonOverROS