Difference between revisions of "Bin Picking Tutorial: Introduction to Robot Interfaces"

From 3D scanning Knowledge base - Photoneo wiki
Jump to: navigation, search
Line 41: Line 41:
 
5. '''YASKAWA''' - YRC1000 Controller v.1.34 and higher (DX100, DX200, FS100 controllers are currently not supported)
 
5. '''YASKAWA''' - YRC1000 Controller v.1.34 and higher (DX100, DX200, FS100 controllers are currently not supported)
  
6. '''MITSUBISHI''' - Robot Controller Type - CR750-D + Software version - H7 and higher  
+
6. '''MITSUBISHI''' - CR750-D Controllers + Software version - H7 and higher  
  
 
7. '''OMRON/ADEPT''' - Both s650 + s850 Adept Viper manipulators
 
7. '''OMRON/ADEPT''' - Both s650 + s850 Adept Viper manipulators
  
8. '''UNIVERSAL ROBOT''' - Version 1.8 and higher
+
8. '''UNIVERSAL ROBOT''' - System Version 1.8 and higher
  
 
== Where to go next ==
 
== Where to go next ==

Revision as of 23:51, 19 December 2017

The main goal of this tutorial is to provide general introduction for interfacing Photoneo Bin Picking System with industrial manipulators.

It is highly recommended to read this tutorial before proceeding to particular robot interface installation !!!

General principles:

Photoneo Bin Picking System is compatible with industrial manipulators of various robotic robotic vendors. Each robotic implementation is different, however five high-level principles are common for all of them:

1. State server + Bin Picking Client

Robot Interface of Photoneo Bin Picking System always consists of two processes - State Server + Bin Picking Client. Both processes needs to run in parallel on the target control robot controller. State Server reports current joint and tool pose coordinates and usually runs in background, while Bin Picking Client is responsible for the request/response transfers between Vision and Robot controller and resulting motion executions.

2. TCP/IP protocol

TCP/IP is utilized for communication between Photoneo Vision Controller and particular Robot controller. It is usually possible to configure additional industrial fieldbus for basic robot control (ON/OFF, robot program selection, safety purposes etc.), however replacing TCP/IP communication between Robot controller and Photoneo Vision controller by other industrial fieldbus is currently not supported.

3. Full Operator Control

Photoneo BP Client does not take over the control of the robot. It is always the robot Programmer/Operator who decides when to perform bin picking related actions by calling particular jobs/routines/program provided by robot interface API. It is also the robot Programmer/Operator who selects the speed of motion execution and implements the gripper commands with respect to the particular application. Photoneo BP Client always enables Programmer/Operator to track the current robot program execution directly on the pendant and take appropriate actions. Motion is never performed in background tasks and out of the Programmer/Operator reach.

4. Easy to Integrate

Robot Interfaces for Photoneo Bin Picking solution were developed with respect to be easily integrated into existing robotic applications written in standard robotic languages. From robot programming point of view, Photoneo BP interface is just a set of jobs/routines/programs that are available for the robot Programmer/Operator to be called when bin picking operation is about to be executed. For example when a next object needs to be picked, operator calls a job/routine/program named requestTrajectory() or similar. Robot interface transmits this request to the Vision Controller, Vision Controller performs requested action (Scan & Motion Planning) and the result (set of trajectories and gripper commands) is transmitted back to the robot controller. Robot Programmer/Operator is notified by predefined register or flag that new motion data are available and it is up to him when he decides to perform the bin picking movement. This is realized by calling another job/routine/program usually named executeTrajectory() or similar. See particular vendor configuration for further information about available robotic API.

5. Trajectory validation

Bin picking procedure is mostly composed of four trajectories (approach, grasp, deapproach and end) and two or three gripper commands. Each trajectory consists of several waypoints (usually 10-100) defined as joint positions which robot is trying to reach during the movement. Photoneo BP Client leverage downloading approach (in contrast to streaming one) meaning that each trajectory is downloaded from the Vision Controller and verified by the Robot controller before its execution. No motion is executed until each robot controller checks whether each received waypoint matches the waypoint originally send by the Vision Controller.

Supported Robotic Systems & Prerequisites:

Following list summarizes currently supported robotic systems:

1. ABB - RobotWare OS > 5.13 + PC-Interface (616-6) + Multitasking Module (672-1) options

2. KUKA - KUKA System Software 8.2 + EthernetKRL option

3. FANUC - System version 8.10 or higher + R632 - KAREL + R648 - User Socket Messaging options

4. STAUBLI - Staubli CS8 controller and higher + VAL3 version s7.7.2 or higher

5. YASKAWA - YRC1000 Controller v.1.34 and higher (DX100, DX200, FS100 controllers are currently not supported)

6. MITSUBISHI - CR750-D Controllers + Software version - H7 and higher

7. OMRON/ADEPT - Both s650 + s850 Adept Viper manipulators

8. UNIVERSAL ROBOT - System Version 1.8 and higher

Where to go next

1. Setting up Photoneo Bin Picking Solution with ABB robots

2. Setting up Photoneo Bin Picking Solution with KUKA robots

3. Setting up Photoneo Bin Picking Solution with FANUC robots

4. Setting up Photoneo Bin Picking Solution with STAUBLI robots

5. Setting up Photoneo Bin Picking Solution with YASKAWA robots

6. Setting up Photoneo Bin Picking Solution with MISTUBISHI robots

7. Setting up Photoneo Bin Picking Solution with OMRON/ADEPT robots

8. Setting up Photoneo Bin Picking Solution with UR robots