Difference between revisions of "2016 Summer Project Week/Integrating/Using OpenIGTLink for the communications of Robotics devices"
From NAMIC Wiki
(adding more details for Approach) |
|||
Line 28: | Line 28: | ||
<h5>MLab Interface</h5> | <h5>MLab Interface</h5> | ||
*Design and implement a generic interface for using OpenIGT commands in MeVislab network layer. | *Design and implement a generic interface for using OpenIGT commands in MeVislab network layer. | ||
+ | **Create Client /Server | ||
+ | ***Name, show status, | ||
+ | **Define Datatypes: Vector position, Status, etc.. | ||
+ | **Communication: Send and recieve: | ||
+ | ***Massages | ||
+ | ***Data-sets | ||
+ | ***Images | ||
+ | **Control commands | ||
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> |
Revision as of 09:09, 10 June 2016
Home < 2016 Summer Project Week < Integrating < Using OpenIGTLink for the communications of Robotics devicesKey Investigators
- Scheherazade Kraß
- Longquan Chen
Project Description
Objective
- Obtaining a better understanding of OpenIGTLink:
- How to use and integrate it in different robotic devices using:
- MeVisLab applications
- Slicer
Approach, Plan
Robotic Devices
- Defining different workflows for communication between robotic device and MeVislab applications, including sending/receiving strings, image sets and control commands for:
- The Kuka LBR robot used in a MeVislab based research project.
- The MRI compatible Manipulator, a 5 DoF robot for performing transrectal prostate biopsies.
- Defined Scenarios :
- Workflow01:
MLab Interface
- Design and implement a generic interface for using OpenIGT commands in MeVislab network layer.
- Create Client /Server
- Name, show status,
- Define Datatypes: Vector position, Status, etc..
- Communication: Send and recieve:
- Massages
- Data-sets
- Images
- Control commands
- Create Client /Server
Progress
- to be defined in the project week.