Difference between revisions of "Documentation/Nightly/Extensions/LightWeightRobotIGT"
Line 14: | Line 14: | ||
{{documentation/{{documentation/version}}/module-introduction-row}} | {{documentation/{{documentation/version}}/module-introduction-row}} | ||
{{documentation/{{documentation/version}}/module-introduction-logo-gallery | {{documentation/{{documentation/version}}/module-introduction-logo-gallery | ||
− | | | + | |[[File:imesLogo.png]] |
}} | }} | ||
{{documentation/{{documentation/version}}/module-introduction-end}} | {{documentation/{{documentation/version}}/module-introduction-end}} |
Revision as of 09:18, 18 September 2014
Home < Documentation < Nightly < Extensions < LightWeightRobotIGT
For the latest Slicer documentation, visit the read-the-docs. |
Introduction and Acknowledgements
Module Description
The LightWeightRobotIGT module allow to communicate with a light weight robot (LWR iiwa, KUKA Laboratories GmbH, Germany, Augsburg) using a open interface concept based on the OpenIGTLink protocol (LWROpenIGTIF). Therefor, a state machine example is available at Git Hub containing the necessary interface classes for the communication on the robot control. A tutorial on how to set up the robotic system for the use with this 3D Slicer module see Tutorial-LightWeightRobot-getting started. For an introduction of the interface concept see Tutorial-LightWeightRopbotIGT-Introduction. The module provides the following features:
- Communication with the robot control
- Bidirectional cyclic communication with a state control running on the robot control. Command strings of the type "CommandName;p1;...;pn;" with the parameters needed to initialise the state p1-pn are sent to the robot control and acknowledge strings are received (see table below for a list of all supported command and acknowledge strings and their parameters).
- Receiving the transformation matrix containing the pose of each robot joint in robot base coordinate frame and a matrix containing a similar transformation including information about the force direction, absolute value and application point.
- Send the transformation matrix describuing the transformation between robot base coordinate frame to image space or CT base coordinate frame
- Visualisation
- a 3D model of the robot can be loaded and is automatically connected to the corresponding transformation matrices received from the robot control.
- the estimated force at the tool center point, e.g. the tool tip can be visualized by an scaled 3D arrow in the force direction.
- the color of the robot model changes the color due to the current robot state received in the acknowledge string, and, hence, gives a direct feedback to the user of the current robot state
- active virtual fixtures in relation to the robot and the target region changing their color to red when robot reach the fixtures
Use Cases
N/A
Tutorials
- General interface concept and communication overview: LightWeightRopbotIGT-Introduction
- Tutorial on how to set up your system and start the example: LightWeightRobotIGT-getting started
- and how to add new states to the exemplary state machine LightWeightRobotIGT-add state
Panels and their use
- Start Communication: Starts the cyclic communication with the state machine on the robot control
- Start Visualisation: Send a command to the robot control to activate the Visualisation
- Stop Visualisation: Send a command to the robot control to deactivate the Visualisation
- Load Robot: Loading the stl-File of the robot and the tool in the path defined by "Path". The part shuld be named ....
- Show TCP Force: Visualizing the estimate force at the tool center point by a scaled 3D arrow pointing in force direction.
- Registration:
- Free: Sending a transition request to the free state to the robot control in which the robot can be moved freely and manually
- Get Fiducial: Saves the current position in a fiducial list which can be used for a fiducial registration using modul XY
- Prepositioning:
- Virtual Fixture: Sending a transition request to the VirtualFixtures state to the robot control in which the robot can be moved freely and manually in work space restricted by active constraints. The supported virtual fixtures geometries are plane and cone.
- PathImp: Sending a transition request to the Path state to the robot control in which the robot can be moved on a linear path from the current position towards a target position.
- Targeting:
- Move To: Sending a transition request to the MoveTo state to the robot control in which the robot moves position controlled towards a target position.
- Reset Robot to Idle: Sending a transition request to the Idle state to the robot control
- Shut Down state machine: Sends a command to shut down the state machine running on the robot control
Similar Modules
N/A
References
Tauscher S, Tokuda J, Schreiber G, Neff T, Hata N, Ortmaier T. OpenIGTLink interface for state control and visualisation of a robot for image-guided therapy systems. Int J Comput Assist Radiol Surg. 2014 Jun 13.
Information for Developers
Section under construction. |