1

Version V1.0-EN, March 2020

© Commonplace Robotics GmbH, 2011 – 2020

igus® and robolink® are registered trademarks of igus GmbH.

igus® GmbH
Spicher Str. 1a
51147 Cologne
Germany
Phone Support: +49 (0) 2203-96498-255
ww-robot-control@igus.net
www.igus.de, www.igus.eu

2
Table of Contents

Safety Instructions.............................................................................................................................. 5
Quick Start Guide ................................................................................................................................. 6
2.1. Set up and Connections.............................................................................................................................6
2.2. Switching on ....................................................................................................................................................6
2.3. Connect and Move the Robot ................................................................................................................ 7
Introduction ............................................................................................................................................ 8
3.1. System Overview..........................................................................................................................................8
3.2. Glossary and Abbreviations....................................................................................................................9
3.3. Specifications................................................................................................................................................ 11
3.4. Mechanical Dimensions .......................................................................................................................... 12
Electrical Connections ..................................................................................................................... 14
4.1. Overview.......................................................................................................................................................... 14
4.2. Pinout: Stepper Module .......................................................................................................................... 15
4.3. Pinout: Support Module .......................................................................................................................... 16
4.4. Pinout: Digital Input/Output Module ................................................................................................17
4.5. Connect Sensors and Actors to the DIO Module ...................................................................... 18
4.6. Option: Control Cabinet ......................................................................................................................... 20
4.7. Option: Embedded Computer .............................................................................................................. 21
4.8. Option: Operating Panel......................................................................................................................... 24
Safety ....................................................................................................................................................... 25
5.1. Safety-Related Features of the Modular Robot Controller .............................................. 25
5.2. CE Certification .......................................................................................................................................... 25
5.3. Integration of SIL-Rated Safety Components .......................................................................... 25
Software Installation ....................................................................................................................... 27
6.1. Installation of the iRC - igus® Robot Control ...............................................................................27
6.2. Licensing ......................................................................................................................................................... 29
6.3. Setting up the Ethernet Connection to the Embedded Computer................................. 29
6.4. Installing the CAN-to-USB Driver ..................................................................................................... 30
Moving the Robot with iRC ............................................................................................................. 31
7.1. The iRC Graphical User Interface ...................................................................................................... 31
7.2. Connecting the Robot ............................................................................................................................. 34
7.3. Referencing the Robot ........................................................................................................................... 35
7.4. Moving the Robot with Gamepad or Software Buttons .......................................................37
7.5. Starting Robot Programs ...................................................................................................................... 38
7.6. Digital Inputs and Outputs .................................................................................................................... 39
7.7. Software Interfaces ................................................................................................................................ 40
3
7.8. Updating the Software .......................................................................................................................... 40
Programming the Robot with iRC .............................................................................................. 41
8.1. The Program Editor ................................................................................................................................... 41
8.2. Comments and information in programs..................................................................................... 44
8.3. Variables and Variable Access .......................................................................................................... 46
8.4. Execution flow ............................................................................................................................................. 50
8.5. Motion .............................................................................................................................................................. 58
8.6. Gripper and digital I/O............................................................................................................................ 64
8.7. Camera ............................................................................................................................................................ 65
Stand-alone Operation with Embedded Computer and the Operating Panel ..... 66
9.1. Reset Errors/Enable Robot ................................................................................................................. 67
9.2. Moving the robot with the 3-Axis Joystick .................................................................................. 67
9.3. Referencing.................................................................................................................................................. 68
9.4. Starting and Stopping a Program .................................................................................................... 69
9.5. Manually Setting the Digital Inputs/Outputs............................................................................ 69
9.6. Display of Status Information ............................................................................................................ 70
9.7. Organize Programs on the Embedded Control ......................................................................... 70
Project Configuration....................................................................................................................... 72
10.1. Program ...........................................................................................................................................................72
10.2. Tool .....................................................................................................................................................................72
10.3. Inputs / Outputs...........................................................................................................................................73
10.4. Virtual Box ......................................................................................................................................................73
Advanced Robot Configuration .................................................................................................. 74
Interfaces Configuration ................................................................................................................ 75
12.1. Cameras ...........................................................................................................................................................75
12.2. PLC Interface ................................................................................................................................................75
12.3. CRI Ethernet Interface............................................................................................................................ 76
Troubleshooting...................................................................................................................................77
13.1. Support Contacts ....................................................................................................................................... 77
13.2. Online Tool - Fault Identification and Recovery ........................................................................ 77
13.3. Configuration of the Stepper Modules ......................................................................................... 78
13.4. Calibration of the Robot ........................................................................................................................ 79
13.5. Error Codes .................................................................................................................................................. 80

4
 Safety Instructions
Operate the Robot safely!
Always ensure personal safety of users and others while operating
a Robot Arm or commissioning a robot cell! In particular, no person
or obstructions may be present in the working area of the Robot.

 In its basic version the Robot Controller package does not contain safety related
functionality. Depending on the application, these may need to be added. See “CE
marking” below and section 5.
 CE marking: Robot Arm and the Robot Controller are a part of one system, which must be
risk assessed in its entirety and comply with the current safety regulations to ensure
personal safety. Depending on the result of the assessment further safety components
must be integrated. These are usually safety relays and door switches. Responsible is the
commissioning engineer of the system.
 The Robot Controller contains a 24V power supply unit that itself requires mains voltage
(120 / 240 V), depending on the configuration. Please check the label on the power supply.
Only qualified personnel may connect the power supply to the mains and put it into
operation.
 Work on the robot electronics should only be carried out by qualified personnel. Check
current electrostatic discharge (ESD) guidelines.
 Always disconnect the Robot Controller from the mains (120 / 240 V) when working in the
Control Cabinet or any electronics connected to the Robot Controller.
 Do NOT hot-plug! It may cause permanent damage to the motor modules. Do not install
or remove any modules or plug/unplug connectors (e.g. Operating Panel, Emergency Stop
Button, DIO Modules or external relays, motor connectors) while powered on.
 The Robot Arm must be set up on a sturdy surface and bolted down or otherwise secured.
 Only use and store the system in a dry and clean environment.
 Only use the system at room temperature (15° to 32°C).
 The ventilation of the system must be able to operate without hindrance, to ensure
sufficient airflow to cool the Stepper Motor Driver Modules. There must be at least
10 cm of space next to the fan of the Robot Controller. The fan must, ideally, point
upwards or to the side (reduced efficiency). The fan must not point down.
 Backup important data prior to installing the igus® Robot Control software.

5
 Quick Start Guide

2.1. Set up and Connections

 Follow Safety Instructions, Section 1.
 Make sure that the on/off switch on the Control Cabinet is set to "off".
 Mount the Robot on a suitable base. Make sure that there is no tension on the cables and
that the sheet-metal reference plate of Axis 1 is not bent.

 Feed the Robot cables through the large circular hole in the Control Cabinet and plug them
into the Stepper Modules. Each motor is
connected to its Stepper Module via 4
connectors.
All connectors are labeled and coded to aid
this process (see Section 4):
o Motor cable (labelled Motor)
o Encoder cable (2 connectors labelled
ENC-1 and ENC-2)
o Reference sensor (labelled End-Stop)
 Secure the robot cables against tension, e.g. with a cable tie to one of the holes in the
Control Cabinet. If available, plug in the display cable and secure it via the screw
connection.
 After that the Robot can be connected to the mains.

2.2. Switching on
 Switch on the Robot using the on/off switch on
the Control Cabinet.
 The green light-emitting diodes (LEDs) on the
modules are now on, also most red LEDs and
potentially some of the yellow LEDs.
 Optional: When shipped with an Embedded
Computer, the green LEDs will start flashing after
approx. 20 s. This shows communication, now the
Robot Controller is up and running. If available,
you can now move the Robot using the Operating Panel (optional). Details can be found in
Section 8.

6
2.3. Connect and Move the Robot
2.3.1. Preparation using the Embedded Computer
 Connect your PC to the Robot Controller via an
Ethernet cable. Use the Ethernet port located
directly next to the USB socket on the embedded
computer of the Robot Controller.
 Set the IP address of the PC to:
static and 192.168.3.1
with subnet mask of 255.255.255.0

2.3.2. Preparations using the USB-CAN adapter

 Connect the USB-CAN-Adapter to a computer (USB port) and the Robot Controller (D-Sub-
9 port with “CAN” marking. Install the necessary driver from the USB memory stick, see
Section 6.2.

2.3.3. Connect and Move the Robot

 Install the igus® Robot Control software on your
PC, see Section 6.1.
 Start the igus® Robot Control software. On
Start-up you can choose the project suitable for
your Robot. Please refer to the igus product
number, the project names are based on these.
 You can now activate the Robot by pressing
o “Connect”,
o “Reset” and
o “Enable” in sequence.
 Now the status LED light on the left of CPRog
should be green, status “No Error”.
 You can now move the joints of the robot using the
buttons in the “Jog” tab.
 Referencing is mandatory prior to moving in
cartesian coordinates or executing a program.

For details, please refer to Section 7.

7
 Introduction

3.1. System Overview

The robot system consists of four basic components:
1. Robot Arm : the mechanical robolink DP
2. Robot Controller : modular motor controller and IO modules
3. Robot Control Software: control software to execute robot programs
4. Programming Environment: graphical software to set up robot programs

There are two basic system configurations available:

Configuration A uses an Embedded Computer with Robot Control Software to run the
Modular Robot Controller. This set up can execute robot programs without an external
Windows PC connected. For programming an external PC can be connected via Ethernet.

Figure 3.1: robolink DP with Embedded Computer running the Robot Control Software.

In configuration B a Windows PC serves both as programming environment and to command

the Modular Robot Controller via a USB-CAN adapter. This setup is often used in educational
settings.

Figure 3.2: robolink DP with Robot Control Software and Programming Environment

8
3.2. Glossary and Abbreviations

Image Name Abbrev. Description

igus® robolink® Robot Mechanical robot
Robot Arm arm including
structure, motors
and cables

Modular Robot Robot Consists of:

Controller Controller  1 Support
Module
 3 or more
Stepper Modules
 1-3 DIO Modules

Control Cabinet - Steel cabinet that

the Robot
Controller can be
mounted in.
Includes a 24V /
10A power supply.
Embedded - Optional
Computer Embedded
Computer with
Linux operating
system and the
TinyCtrl Robot
Control Software

Operating - Optional operating

Panel hand-held device
with 3.5’’ capacitive
touchscreen
display and 3-axis
joystick

9
 Emergency - Single-channel
Stop Button emergency stop

Electronic Control Modules

Digital DIO Reads 7 digital
Input/Output Module inputs on 24V level.
Module Sets 7 digital
output channels
based on Solid
State Relays.

Steppermotor Stepper Versions:

Driver Module Module  Motor Encoder
(ME):
- high current (HC)
- low current (LC)
 Output Encoder
(AE):
- high current (HC)
- low current (LC)
Support - Provides 5 V logic
Module voltage, max. 2 A.
Interface for single-
channel Emergency
Stop Button.
Interface for
additional e.g. dual
channel safety
relays.

10
3.3. Specifications
Robot Arm (if included)
Type igus® robolink®
Number of axes Depending on version: 4 or 5
Payload Depending on version: 2.5 to 3 kg

Modular Robot Controller

Power supply 24 V at 10 A
Type DIN rail modules ME format with 5-pin bus connector
Communication Controller Area Network (CAN) Fieldbus 500 kBit
USB-to-CAN Adapter PCAN-USB from Peak Systems
Ethernet
Support Modules Provision of 5 V logic voltage: max. 2 A.
SoftStart to prevent overloading the power supply.
1-channel emergency stop function without safety
classification
Provision to connect external safety relays.
Steppermotor Driver Modules For operating a bipolar stepper motor with
(Stepper Modules) quadrature encoder RS422
24 V reference switch input
Digital In/Out Modules 7 digital inputs, 12 – 24 V, optocoupled
(DIO Module) 7 digital outputs, solid state relays, max. 500 mA

Embedded Computer (if included)

Platform Phytec Regor or comparable,
CPU e.g. Texas Instruments AM3352
Operating system Linux
Software TinyCtrl Robot Control Software
Interfaces Control of the drives and DIO Modules via the CAN bus
Connection to igus® Robot Control via Ethernet
RS232 display connection

Programming and Robot Control Software

igus® Robot Control
Recommended System PC with e.g. Intel i5 CPU (minimum i3) and Windows 10,
requirements free USB 2.0 port, ethernet port, 500 MB disk space

11
3.4. Mechanical Dimensions
For more information see the igus® manual “Technical Documentation robolink® DP Version”.

Figure 3.3 Schematic of operating range of igus® robolink® DP, 5-axis version.

12
Figure 3.4 igus® robolink® DP of: A) Robot base; B), hole pattern flange of the 5th axis (five axes
version); C) Gripper adapter (four axes version). Dimensions are depicted in mm.

13
 Electrical Connections

4.1. Overview

Figure 4.1 Overview of electrical connections.

14
4.2. Pinout: Stepper Module
Each Stepper Module drives a bipolar stepper motor with Motor Encoders. The encoder signals
are evaluated by a line driver (RS422).
Signals to each axis travel via three cables: the motor cable, encoder cable and reference
switch cable.
The motor cable is connected to a plug labelled “Motor”, the encoder cable is connected to two
plugs labelled ENC-1 and ENC-2 and the reference switch cable is connected to the plug labelled
“End-Stop”.

Motor connector:
Connects a bipolar stepper motor.
Pin 1 (left): blue B
Pin 2: white A
Pin 3: black B/
Pin 4: brown A/

Encoder connector 1 (ENC-1):

Connects a quadrature encoder to a line driver.
Pin 1 (left): white A
Pin 2: red 5 V DC
Pin 3: green B
Pin 4: grey 0V
Encoder connector 2 (ENC-2):
Connects a quadrature encoder to a line driver.
Pin 1 (left): brown A-N
Pin 2: yellow B-N
Pin 3: blue index
Pin 4: pink index-N
All eight wires (encoder connectors 1 and 2) must be
connected to read the encoder.

End-Stop connector:
Connects to an end-stop or reference switch.
Pin 1 (left): brown 24 V
Pin 2: blue ground (GND)
Pin 3: black signal
Pin 4 do not connect

15
4.3. Pinout: Support Module
The Support Module provides 5 V logic voltage, a single-channel emergency stop relay,
a SoftStart relay. It feeds the signals into the DIN rail bus system.

Supply voltage connector:

Pin 1 (left): red 24 V
Pin 2: black GND
Pin 3: do not connect -
Pin 4: do not connect -

Controller Area Network ( CAN) connector:

Connects controller and CAN-interface of Embedded
Computer.
Pin 1 (left) 5 V to Embedded PC
Pin 2: black CAN-GND
Pin 3: orange CAN-L
Pin 4: red CAN-H

Emergency stop (E-Stop) connector:

Connects the Emergency Stop Button.
Pin 1 (left): blue E-Stop channel 1
Pin 2: brown 24 V output signal
Pin 3: black E-Stop channel 2
Pin 4: do not connect -
This is a single channel setup, adapt this to your
safety requirements! The options for connecting a
safety relay are described below and in Section 5.

Motor power bridge:

Allows the motor current to be interrupted by
external safety switches, see Section 5.
Pin 1 (left): motor power-out
Pin 2: do not connect
Pin 3: motor-power in
Pin 4: do not connect

16
4.4. Pinout: Digital Input/Output Module
The DIO Module provides input and output channels, e.g. to operate a gripper valve. The
outputs can switch up to 500 mA. The inputs use optocouplers and are compatible to for input
Voltages between 12 and 24 V.
A circuit switched by the output relays must not contain any larger capacitors.
If the current exceeds 500 mA, the solid-state relays can suffer damage.

For safety reasons, the inputs and outputs of the DIO Module are electrically isolated. This
means that the circuits of the inputs and outputs are not connected to the internal circuits of
the controller.
It is, therefore, necessary to connect a supply voltage for the outputs and a ground line for the
inputs. For this purpose, the 24 V available in the robot controller can be used, but also an
external independent voltage source. In Software the inputs and outputs of the first
DIO Module are numbered 21-27; the second DIO Module (if supplied) has numbers 31-37; and
the third 41-47.
Digital Out connector A (D-out A):
The output relays connect the pin of the power
supply with the corresponding output pins.
Pin 1 (left): Input voltage (for all seven channels)
Pin 2: D-Out channel 1 (in software: Dout21)
Pin 3: D-Out channel 2 (in software: Dout22)
Pin 4: D-Out channel 3 (in software Dout23)
Digital Out connector B (D-out B):
The D-out B pins are (from left to right) the
Digital Out channels 4-7 (picture not shown).

Digital In connector A (D-in A):

Pin 1 of D-In A is the corresponding GND pin for all
input pins.
Pin 1 (left): Signal GND (for all seven channels)
Pin 2: D-In channel 1 (in software DIn21)
Pin 3: D-In channel 2 (in software DIn22)
Pin 4: D-In channel 3 (in software Din23)
Digital In connector B (D-in B):
The D-in B pins are (from left to right) the Digital In
channels 4-7 (picture not shown).

17
4.5. Connect Sensors and Actors to the DIO Module
The easiest way to connect a programmable logic controller (PLC) is via digital inputs and
outputs. Each Robot Controller comes with one DIO Module.This provides 7 inputs and 7
outputs (see Section 4.4). If additional inputs and outputs are required, up to two additional
DIO Modules can be integrated, see section 10.1. A total of up to 3 DIO Modules can be
controlled.

The outputs are controlled via solid state relays and can switch up to 500 mA. This value must
not be exceeded during the switching process (e.g. by charging currents of capacitors) to
prevent damage to the relays.

Figure 4.2: Internal set up of a DIO module

The inputs and outputs are galvanically separated from the robot control. A power supply
(labelled “IO Supply” in the Image above) must be connected. The integrated 24V supply may
also be used.

18
4.5.1.1. To connect a sensor

 Pin 1 (GND) of the D-In 1 connector must be connected to GND of the power supply of
the sensor.
 The sensor signal (positive) must be connected to an input pin D-In 1 connector pins 2-
4 or D-In 2 connector pins 1-4.the positive side of the sensor has to be connected to
VDD of the power supply
 The status of the inputs can be monitored in the "Input/Output" tab at the bottom of
iRC, see Section 7.1
 In a robot program inputs can be queried and reacted upon e.g. in a if-then-else
command, see Section 0.

4.5.1.2. To connect an actor (LED, pneumatic valve, relay…)

 Pin 1 (Supply) of the D-Out 1 connector must be connected to a power supply (e.g. 24V)
 The actor (relay, etc.) is then powered from a free pin of the D-Out connectors (D-Out
1 pin 2-4 and D-Out 2 pin 1-4).
 You can set the outputs manually in the “Input / Output” tab on the bottom of iRC, see
section 7.1
 In a robot program you can set the state of the outputs using the digital-out
command, see section 8.6.

Figure 4.3: Connection of an input and output to the DIO module

19
4.6. Option: Control Cabinet
The Modular Robot Controller can be ordered in a steel cabinet. The cabinet shields the control
from dust, humidity and accidental access.

The dimensions of the control cabinet are W x L x H: 600 x 200 x 125 mm

Figure 4.4: Control cabinet, closed. On the lower left the mains IEC connector / switch / fuse and
the cable fittings can be seen.

The cabinet includes a 24V / 10A power supply for 220V / 110V input. A fuse (8A). Distribution
blocks are included. A small fan is mounted on the left side of the cabinet.

Figure 4.5: Control cabinet with Power Supply, without Modular Control Electronics.

20
4.7. Option: Embedded Computer
An Embedded Computer can be combined with Modular Robot Controller, so that an external
computer is just required for programming but not for day to day operation. This resembles
“Configuration A” in the introduction, section 3.1.
The Embedded Computer is a single board computer with Linux operating system, running the
TinyCtrl robot control software. It is used to:
 Operate the robot arm
 Replay programs
 Connect with iRC on a Windows computer via Ethernet for programming
The Embedded Computer communicates with the Modular Control Electronics on the DIN rails.

Figure 4.6 Embedded Computer with Ethernet cable connected to the ETH0 socket.

4.7.1. Ethernet Connection

ETH0 Connection to PC for Standard Ethernet
Primary Ethernet Port programming via IP 192.168.3.11
(next to the USB port) igus® Robot Control
ETH1 Usually none. Can be used to Standard Ethernet
Secondary Ethernet Port connect a camera IP 192.168.4.11

4.7.2. Operating Panel Connection

An operating panel can be connected, see section 4.8
RS232 connection RS232 connection to the Lead 1: UART2-TX
operating panel Lead 2: UART-2-RX

21
 The 2 leaded ribbon cable of the Embedded Computer is
the RS232 connection for the Operating Panel. One lead is
marked black (lead 1).
It is connected via a distribution block to a 9-pin D-Sub
connector.
Lead 1 (black) D-Sub conn. Orange
Lead 2 D-Sub conn. Brown

To provide power to the display, the black and red lead of

the D-Sub connector are connected to GND and 24 V
respectively.

Figure 4.7: D-Sub connector to the Operating panel

The pinout of the connector is as follows:

Caution! The connection is proprietary.

It is not suitable for a null modem cable or the like.

Pin 1: 24V
Pin 3: RS232-TX
Pin 6: GND
Pin 7: RS232-RX
All remaining pins are not connected

22
4.7.3. CAN Connection
CAN ribbon cable Establishes the CAN Lead 1: GND (black)
(three conductors) connection to the Stepper Lead 2: CAN-L
Modules. To be connected to Lead 3: CAN-H
the Support Module

The 3 leaded ribbon cable of the Embedded Computer is

the CAN connection. It has one lead marked in black
(lead 1, GND). Leads 2 and 3 are CAN-L and CAN-H
respectively.
The leads are connected to the support board as
follows:
Lead 1 (black) Support Board CAN Port Pin 2
Lead 2 Support Board CAN Port Pin 3
Lead 4 Support Board CAN Port Pin 4

4.7.4. Power Supply

Power supply 5 V Supplies the Linux Board Pin 1: 5V
with 5 V DC Pin 2: GND

The connector has a white (5 V) and a black (GND)

wire. When the module is mounted on the DIN rail,
blue (5 V) is towards the bottom of the cabinet.
The 5 V (white) cable is connected to the Support
Module 5 V port (Pin 1 of the CAN connector).
The black cable is connected to the power
common GND distribution blocks of the DIN rail.

Double check the polarity of the connection before switching on.

23
4.8. Option: Operating Panel
The Operating Panel is used to control the Robot via the Embedded Computer. For operating
instructions see section 9.
The connection of the D-Sub-9 connector is mating to the D-Sub-9 socket of the Control
Cabinet section 4.7.2.

Figure 4.8: Operating panel with touch screen and 3 axis joystick.

24
 Safety

5.1. Safety-Related Features of the Modular Robot Controller

The Modular Control Electronics have provision for the connection of external safety
components. However, external safety relays/switches can be connected to interrupt motor
power. The emergency stop is a 1 channel device and does not comply to a SIL level.

5.2. CE Certification
The components of this robot system are provided with CE marking as requested by the
European machinery directive. Responsible for the components are:
 igus GmbH: robolink DP robot arm
 Commonplace Robotics GmbH: Modular robot control
These CE markings confirm the adherence of these parts of the final machine to the necessary
standards. The final machine, i.e. the complete robot cell, is not covered by these CE markings.

5.3. Integration of SIL-Rated Safety Components

The Modular Robot Controller does not provide any safety-relevant functions. The integrated
emergency stop function is single channel.

In order to operate the complete, customer-specific robot system, the

commissioning engineer must carry out a risk assessment as part of the
CE certification and, depending on the result, integrate additional safety
components. These are usually safety relays, fence and door switches.

Safety relays can be connected in series with the motor power bridge connector (section 4.3)
of the Support Module (Figure 5.1). The connector is labelled “Ext Rel”. Via this connector the
motor supply is routed out of the module and via a jumper lead back into the module and then
into the bus. If this connection is interrupted, no active movement of the motors is possible.
This enables the implementation of safety features with the safety integrity level (SIL)
required by the application.

25
Figure 5.1 Schematic wiring of the safety components with the Support Module.

26
 Software Installation

 Backup important data before installing the igus® Robot Control software.
 Before updating the igus® Robot Control software, create a backup of the
current version, e.g. by renaming the folder C:\ iRC-igusRobotControl\ to
C:\iRC-igusRobotControl_BAK\.

6.1. Installation of the iRC - igus ® Robot Control

Insert the igus® Robot Control USB

memory stick. Start the installer:
D:\Installer_IRC_V11-nnn.exe
You may have to allow changes on
your system.

After starting the installation, you

have to choose between German and
English language.

Then confirm the license agreement.

27
 In the next step you can choose where
igus® Robot Control should be
installed. The recommended directory
is
C:\iRC-igusRobotControl

When installing igus® Robot Control in

a Windows program directory like
C:\Programs
it is possible that igus® Robot Control
can only be started as administrator.

The installation usually only takes

a few seconds.

After finishing the installation, you can

start igus® Robot Control.

Now you can start igus® Robot Control via the link on the desktop or via the start menu.

Installation error:
The installation wizard checks whether all necessary extensions are available, especially the
.NET framework. If this is not the case, an error message appears. The .NET framework must
be installed manually:
 Search the network for "Microsoft .NET download" and install it.

28
6.2. Licensing
 The igus® Robot Control software requires a license key to be started.
 This key is installed automatically during the installation version of igus® Robot Control.
 Please do not change the content of the license file, otherwise it will become invalid!
 The included standard license allows the installation and use of igus® Robot Control on
any number of computers in the company or organization of the licensee.

6.3. Setting up the Ethernet Connection to the Embedded

Computer
 Connect the Ethernet port (ETH0, adjacent to the USB socket) of the Robot to a Windows
PC using a standard LAN cable.

 Set the IP of the PC to 192.168.3.1 (the Robot has IP 192.168.3.11). Further assistance on
how to change the IP address can be found online.

From this point on the igus® Robot Control programming environment can be used to operate
the connected robot.

29
6.4. Installing the CAN-to-USB Driver
When no Embedded Computer has been supplied, a CAN to USB adapter is supplied that
connects the Modular Robot Controller and a computer. It requires the appropriate driver. The
Robot Control Software is delivered with the PCAN-USB driver from www.peak-system.com,
which can also be found igus® Robot Control installation USB memory stick (directory PCAN-
USB-Adapter) or the installation CD of the manufacturer.
After starting the installation, you must:
 accept the license agreement,
and
 specify the installation folder.

In the next step, please check whether the PCAN-USB device and the PCAN-View CAN-Bus
Monitor are selected for installation as shown below.

Choose both for the installation:

 PCAN-USB
 PCAN-View

The PCAN-View CAN-Bus Monitor

allows you to check whether the
adapter is correctly connected but is
not required in day to day operation.

30
 Moving the Robot with iRC
igus® Robot Control is a control and programming environment for robots. The 3D user
interface should help to get the robot up and running quickly. Due to its modular design
different kinematics and motor drivers can be controlled.

These operating instructions are supplemented with the respective robot-specific operating
instructions.

7.1. The iRC Graphical User Interface

This section explains the igus® Robot Control software. Without the Robot connected all steps
can be simulated. In Section 7.2 the real Robot is then connected and moved.
The igus® Robot Control programming environment allows control and programming of the
Robot. igus® Robot Control is a Windows software. You can work both online and offline, i.e.
with the robot or in simulation (with the robot switched off or disconnected).

Figure 7.1 igus® Robot Control user interface.

In the upper left corner, the three tabs "File", "Scene" and "Motion" provide access to the main
function-sets. In the left corner, information about the current state of the physical Robot is

31
displayed. Additional functions such as loading another project ("Open project") or "Reference
robot" can be found in the "File" tab (Figure 7.1).

There are five tabs at the bottom of the window:

 "Log messages": messages from the program about status or errors.
 "Infocenter": shows axis values, the cartesian position and further information.
 "Jogging": keys to move the Robot.
 "Input/Output": display and set the DIO of the Robot Controller.
 "Programs & Variables": displays the current state of program variables.

The "Help" icon can be found in the bottom right corner and contains links to the
Wiki pages (related to "Online documentation", "Software updates", "Examples",
"Examples", "Troubleshooting") and link to "Contact support".

7.1.1. Selecting the Robot Type

igus® Robot Control offers project-related settings for different types of Robots, such as 4- or
5-axis Robots. Click on the "File" tab in the upper left corner and select "Open project". Select
Robot group e.g. "igus-robolink". Now click at the named image that fits your specific Robot,
e.g. RL-DP-5.

Figure 7.2 Selecting Robot type of the "File" tab in the "Open project".

32
7.1.2. Mouse: Navigation and Moving Robot in the User Interface
To navigate in the igus® Robot Control 3D environment, a 3-button mouse is recommended:
 Left button:
o Selection of icons and features in the software ribbon.
o Moving a Robot axis: place cursor over a joint (it will highlight), then click and move the
cursor up and down while holding down the left mouse button.
 Middle button/wheel:
o Navigation in the scene to turn the Robot: move the cursor while holding down the
middle mouse button.
o Mouse wheel: zoom in/out to the current cursor position.
 Right key: pan

The function of the left/middle mouse button can be changed in

the "Scene" tab under "Navigation", with movement options:
"Select", "Pan", "Rotate", "Zoom" and "Reset".

33
7.2. Connecting the Robot
7.2.1. Connection to Hardware
The real Robot can be controlled like the simulated one, only the hardware has to be connected
first by clicking "Connect", "Reset " and "Enable" icons in the "Physical robot" ribbon group in
the "Motion" tab (see Figure 7.3). After that the robot needs to be referenced.

Figure 7.3 Icons for connecting to the hardware, resetting errors and enabling the motors;
referencing icon; and "Status" indicator.

1. "Connect ": Establish connection to the hardware.

 This step initializes the USB CAN interface or the Ethernet connection.
 The "Status" indicator on the left side changes from grey to red.
 Several error messages are displayed below the "Status" indicator.
2. "Reset ": Reset the errors.
 This key is used to reset the error memories of the electronic modules of the Robot
Controller.
 The axis positions are transferred from the real Robot to the simulation
environment. The 3D visualization of the Robot should now correspond to the
current position of the real Robot.
This must be checked with every error reset! If the values do not
match, a referencing must be performed, described in Section 7.3.


The "Status" indicator remains red. The error messages are deleted, only "Motors not
enabled" remains. If other error messages are displayed, try again and follow the
instructions in the Robot documentation.
3. "Enable": Activation of the motors.
 The "Status" indicator is now green.

34
7.2.2. Moving the Robot
It is now possible to move the Robot with: jog buttons, a mouse in the user interface or
a gamepad, see sections 7.1.2 and 7.4.

7.3. Referencing the Robot

 After startup the Robot needs to be referenced. Prior to referencing, the
axes of the Robot can only perform movements in "Joint" mode. This is to
avoid collisions during un-referenced robot operation.
 Only after referencing, cartesian movements or the start of a program are
allowed.
 The reference status is displayed on the left side of igus® Robot Control.
The Stepper Modules store the motor position in an EEPROM. However, due to gravity or other
forces, the joints can move and drop while motor-power is off. In that case, the Stepper
Modules will no longer report the correct position to the software, because they were switched
off, while the robot has moved. In order to synchronize the position between software, Stepper
Motor Module and Robot Axis, a referencing operation must be carried out.

7.3.1. Axis 1-4: Referencing via half disc-triggered reference sensors

 The axes of the Robot are equipped with inductive sensors. These are triggered by a metal
disc on one half of the axis and free on the other half. During referencing, the Robot moves
in the direction of the transition between half-disc/no-half-disc. Once the transition point
has been found, it carries out a smaller, slower motion to find the exact midpoint of that
Figure 7.4 Referencing tools of Axis 5.At that transition point, the offset-corrected
encoder reading read and defined as zero position. The offset, i.e. the difference between
the position of the reference switch and 0° of the axis, can be changed, see Section 13.4.

7.3.2. Axis 5 – Referencing via pin-triggered reference sensors

 The 5th axis of the Robot is unusual: there is no half disc, but a "referencing pin".
 This pin should ideally be jogged close to the "referencing position sensor" before starting
the referencing (Figure 7.4). This speed up the referencing process of this particular axis.

35
 Figure 7.4 Referencing tools of Axis 5.

7.3.3. Steps to Referencing

1. Start the Robot Controller and igus® Robot Control.
2. Press the "Connect", "Reset" and "Enable" buttons (Figure 7.3).
3. Move the 5th axis of the Robot close to the reference position.
4. Click on "Reference" icon (Figure 7.3) in the "Physical robot" ribbon group in the "Motion"
tab (or "Reference robot" via "File" tab) to open the referencing window.
5. Click the buttons to start referencing the axes, see Figure 7.5. Several joints can perform
the referencing in parallel.
6. You can also click on "Reference all", then the axes start referencing in a sequence
defined in the project file.
7. As soon as all joints have stopped, click "Reset" and "Enable". Now the Robot is fully
operational.

Figure 7.5 Referencing window.

36
7.4. Moving the Robot with Gamepad or Software Buttons
The Robot can be moved (or "jogged") manually while no program is running. The two main
controls can be found in "Motion" ribbon:
 "Input" (to connect to a gamepad),
 "Motion parameters" (to choose motion modes and speed with software buttons).

Figure 7.6 Control panel for moving the Robot (marked in blue).

A gamepad is potentially the most intuitive way to move the Robot. Figure 7.7 shows the key
assignments. By pressing "Connect Controller", igus® Robot Control connects to a gamepad.
If the connection was successful, an OK sign is displayed on the controller icon. The device
must be of the "Joystick" or "Gamepad" type. You can find further information on establishing
a connection in the "LogMessages" tab (on the bottom of the screen).

Legend:
1. Change motion type
2. Change key assignments:
Switching between X, Y, Z and A, B, C
in Cartesian motion mode, or A1,2,3
and A4,5,6 in Joint motion mode.

Figure 7.7 Key assignments of the Gamepad

2. Software buttons allow to select "Motion Type", which include three modes and in each
case the movement speed can be changed between 0 and 100% (Figure 7.6):
 "Joint": A click on A1 to A6 moves the corresponding robot axis (if available). E1-E3 move
the external joints. This could be a linear axis, rotational (Figure 7.8).

37
  "Base" (cartesian mode), the Robot moves in straight lines along the X, Y and Z axes of
the base coordinate system.
 "Tool" (cartesian mode), the Robot moves in X, Y and Z of the current tool coordinate
system.

Figure 7.8 The software buttons for "Joint" movements in "Jogging" tab. In both cartesian modes,
the buttons change to X, Y, Z, A, B and C.

7.5. Starting Robot Programs

The robot program must be loaded and started.
1. Load the program: click the "Load" folder icon in the "Current program" ribbon group of
the "Motion" tab and select a program, e.g. igus5DOF_TestMotion. xml

Figure 7.9 Loading a new program (marked in blue).

38
2. Adjust the speed-override:

 Before starting a new program, set the speed to

e.g. 20%.
 Be particularly attentive during the first complete
program run and keep the Emergency Stop Button
ready.

3. Start the program:

 Click the "Play" icon in the "Program execution"
ribbon group of the "Motion" tab.

4. Stop or pause the program:

 After pressing the "Pause" icon, the Robot can continue with the program by clicking
the "Play" icon again.
 After pressing the "Stop" icon, the program starts with the first command when the
"Play" icon is clicked again.
 The "Replay Mode" can be set to:
o Single (program stops after a single cycle).
o Repeat (program does not stop until "stop" or "pause" is pressed).
o Step (program steps line-by-line. This is useful for debugging a program).

7.6. Digital Inputs and Outputs

The easiest way to connect a programmable logic controller (PLC) is via digital inputs and
outputs. Each Robot Controller comes with one DIO Module.This provides 7 inputs and 7
outputs (see Section 4.4). If additional inputs and outputs are required, up to two additional
DIO Modules can be integrated, see section 10.1. A total of up to 3 DIO Modules can be
controlled.

The state of the inputs and outputs can be monitored in the “Input / Output” section of iRC.
Both inputs and outputs can be set manually:
 Outputs can be set manually, when no program is running.
 Inputs can be set only in simulation when there is no robot connected. Hence one
can test the reaction of programs on different inputs in the absence of hardware.

39
 Figure 7.10: Input / Output section of the iRC software.

See section 4.5 on how to set up the electrical connections and section 10.1 on how to extend
the number of available digital Inputs / Outputs. It is also possible rename the different inputs
/ outputs.
The programming with digital Inputs / Outputs is shown in sections 0 and 8.6.

7.7. Software Interfaces

Various interfaces are available from the Robot Controller:
 PLC interface for controlling the Robot via a PLC, in particular for starting and stopping
programs.
 Plug-in interface to integrate e.g. cameras. The plug-in then transmits target positions to
the Robot Controller.
 Container Runtime Interface (CRI) to enable further interaction. This interface can be used,
for example, to generate workpiece-specific programs from a database.
 ROS interface to integrate the Robot into the Robot Operating System (www.ros.org).

See section 10 for the configuration of these interfaces.

7.8. Updating the Software

Updates of the iRC software can be found on the igus LowCostAutomation website.
BackUp: Please rename your old iRC-igusRobotControl folder to e.g. C:\ iRC-igusRobotControl
_BAK before starting the installation. This way, you can switch back to the old version in case of
doubt. The following has to be transferred from the previous installation:
 The created robot programs;
 Changes in the project or robot configurations.

40
 Programming the Robot with iRC
igus® Robot Control allows the creation of robot programs. The type of programming is called
“Teach-In-Programming”, which works as follows:
1. Move the robot manually to the position you want to record
2. Record the position and define how to reach this position (linear/joint motion)
3. Repeat these steps and in between add digital output commands or program flow
commands.
The integrated Program Editor is provided for setting up and editing these robot programs.

8.1. The Program Editor

In the robot program each command consists of one line, e.g. “Joint Motion” or “Wait”. Only
commands that direct the program flow are separated into several lines, e.g. “Loop” and
“EndLoop”. The program editor is opened with the “Edit” button in the “Motion” tab.

Figure 8.1: Opening the program editor with the “Edit” button.

Then the following window opens, here with a short program:

Figure 8.2: Program editor with a short program.

The following sections show how to write programs with the editor.

41
8.1.1. Changing the Command Sequence

To move the command down, click on “Move down”, on “Move up” to move up. It is also possible
to use the arrows on the right side of the commands.

The Program Editor will prevent commands that would render the structure of a program
illegal. If moving of a command in a up or down is impossible, the respective buttons and menu
items will be greyed out.

8.1.2. Touching up commands

Certain commands require position constants as parameter. Often, it is desirable to use the
current position of the robot. Entering it by hand can take quite some time and is error-prone.
For such cases the possibility to “Touch up” the command is offered. You can do this by
 selecting the command (see section 1.3.1) and then pressing Ctrl+T
 clicking “Touch up!” in the context menu that pops up when clicking on the header
with the right mouse button:

This functionality is also found in the menu: “Edit”->”Touch up!”

The Program Editor will then replace the position constant in the command with the current
position of the robot.
42
8.1.3. Current starting command
It is possible to execute programs command-wise, or to pick a specific command as starting
point of a program for debugging purposes.
The command that will be executed first, next time the program is started, or – if the program
is currently running – the currently executed command is indicated in the Program Editor.
The subprogram that contains this command is designated by a filled black circle in front of the
Program Name:

The command itself is designated by a filled black circle in the header bar of the command:

To choose a specific command as starting point for execution, click on “Start here” in the
context menu that pops up when clicking on the header with the right mouse button:

43
8.1.4. Undo and Redo

All changes made in the Program Editor can be undone / redone.

To undo you can To redo a previously undone change

you can
 Press Ctrl+Z.  Press Ctrl+Y
 Click on the menu item  Click on the menu item
“Edit”->”Undo” (it will be greyed “Edit”->”Redo” (it will be greyed
out if no changes have been out if no changes have been
performed so far). undone before)

8.2. Comments and information in programs

8.2.1. Program information
The Program Editor will introduce the Start pseudo-command at the beginning of each
program. It does not represent a real command in the sense that it will not be executed in any
way. Its purpose is to display information about the current hardware, software and kinematic.
It is not possible to move or remove it.

8.2.2. Descriptions
Any command of a program contains a description. It can be filled with any text and should be
used to describe what the intention behind the respective command is to other programmers.

44
8.2.3. Comments
The Comment command can be used to include pure descriptions into programs. It has no
effect on the robot during execution, its sole purpose is to provide a Description.

It is accessible in iRC’s Program Editor through the menu entry “Special”->”Comment:

45
8.3. Variables and Variable Access
Two types of variables are supported in programs for iRC and TinyCtrl:
 Number variables: these can be used to store integer or floating point numbers
 Position variables: these can be used to store Cartesian positions and joint
positions. Whether such a variable will be interpreted as cartesian position or joint
position depends on context.

8.3.1. User Variables

It is possible to define user-variables with the Store command, which is accessible in iRC’s
Program Editor through the menu entries under “Special”->”Variable definition”.

It is possible to choose three types of Store operations:

 “Current position”:

A position variable will be initialized with the cartesian and joint position that the
robot has when the command is being executed.

 “Number constant”:

A number variable will be initialized with the constant given under “Value”.

46
  “Position constant”:

A position variable will be initialized with the constants given under “Cartesian
position”, “Joint position” and “External axes”. Depending on the kinematic model of
the current robot certain axes may be unavailable.

The name of the variable can be set under “Variable”. If a variable with the same name has
already been defined its value and type will be overwritten. All variables are global, i.e. they will
also be accessible from subprograms.

8.3.2. System Variables

The following predefined variables are available without the need to define them:
 #position
The current position of the robot. The units of the Cartesian position are mm for the
components x,y,z and degrees for the Euler angles A,B,C. Joint values are measured in mm
or degrees, depending on the type of the joint.
Note that the system controls the values of predefined variables – they cannot be changed by
the program. The names of predefined variables always start with a “#”.

8.3.3. Element Access

The following elements of the variables can be accessed with the “.” Operator:
 Position : x, y, z E.g.: myvariable.x
 Rotation : A, B, C E.g.: myvariable.a
 Joints : A1, A2, A3, A4, A5, A6, E1, E2, E3 E.g.: myvariable.a5

47
8.3.4. Operations on variables
Operations on variables can be performed by using the Math command, which is accessible in
iRC’s Program Editor through the menu entries under “Special”->”Variable operation”.

“Operand 1” defines the first operand of the operation that is to be performed. It will also be
used to store the result of the operation. Only names of user-defined number variables or
components of user-defined position variables are allowed.
“Operand 2” defines the second operand of the operation. It can contain numeric constants,
names of number variables or components of position variables.

The following operations are supported and can be chosen under “Operation”:
 Set:
This will set the first operand to the value of the second operand.
 Add:
This will increment the first operand by the value of the second operand.
 Subtract:
This will decrement the first operand by the value of the second operand.
 Multiply:
This will multiply the first operand by the value of the second operand.
 Divide :
This will divide the first operand by the value of the second operand.
 Modulus:
This will store the remainder of the division of the first operand by the second
operand into the first operand.

48
8.3.5. Monitoring variables
You can monitor the current values of all defined variables under iRC in the variables tab:

49
8.4. Execution flow
8.4.1. Conditional expressions
Conditional expressions can be used in if-then-else commands, conditional loops and as abort
conditions in motion commands. The conditional statements can be combinations of digital
inputs, global signals, Boolean operations and comparisons. Examples:
 DIn23 True, if digital input 23 is high
 DIn23 AND !DIn27 True, if digital input 23 is high and digital input 27 is not high
 modelclass = 31 True, if variable modelclass is 31
 mempos.x > 350.0 True, if the x component of the position variable mempos is
higher then 350

The syntax of conditional statements is given by the following EBNF definition:

Expression := [ "!" ] <Boolean> { <BooleanOperator> <Boolean> } ...
Boolean := <BooleanConstant> | <Expression> | "(" <Expression> ")" |
CompExpression | "(" <CompExpression> ")" | <DigitalInputs> |
“(“ <DigitalInputs> “)”
BooleanOperator := "And" | "Or"
BooleanConstant := "True" | "False"
DigitalInputs := <ChannelType> <ChannelId>
ChannelType := “Din” | “GSig”
Channeld := an integer value
CompExpression := <CompValue> <Comparator> <CompValue>
CompValue := <Variable> | <Number>
Variable := <NumberVariable> | <PositionComponent>
NumberVariable := Name of a number variable
PositionComponent := <PositionVariable> “.” <Component>
PositionVariable := Name of a position variable
Component := “x” | “y” | “z” | “A” | “B” | “C” | “A1” | “A2” | “A3” | “A4” | “A5” | “A6” | “E1”
| “E2” | “E3”
Number := Integer or Float number
Comparator := "=" | ">" | "<" | ">=" | "<="

50
8.4.2. Stop
The Stop command stops the program execution.

It is available through the menu entry “Flow”->”Stop”.

8.4.3. Pause
The Pause command pauses execution of the program. Execution can later be resumed by the
user.

It is available through the menu entry “Flow”->”Pause”.

8.4.4. Wait
The Wait command allows the robot to wait for a fixed amount of time or until a conditional
statement evaluates to true. It is accessible though the menu entries under “Flow”->”Wait” in
iRC’s Program Editor.

51
The different modes can by chosen under “Type”:
 “Timeout”:
This will cause the robot to wait for the time that is given under “Duration”.

 “Condition”:
This will case the robot to wait until the conditional statement given under
“Condition” evaluates to “True”.

52
8.4.5. If-then-else
The If command branches execution of the program depending on the value of a conditional
expression. It is accessible through the menu entry “Flow”-“If…then..else” in iRC’s Program
Editor.

The conditional expression given under “Condition” must match the syntax described in section
Fehler! Verweisquelle konnte nicht gefunden werden. . The branch between “If” and “Else” will
be executed if it evaluates to true, the branch between “Else” and “EndIf” will be executed
otherwise.

53
8.4.6. Loops
The Loop command allows to define execution loops. It is possible to choose between the
following types of loops under “Type”:
 “Condition”
The loop will repeat until the conditional expression given under “Condition”
evaluates to “True”. It must follow the syntax described in section Fehler!
Verweisquelle konnte nicht gefunden werden. .

 “Counter”
The loop will repeat the number of times that is specified under “Count”.

The loop command is accessible via the menu items “Flow”->”Loop”->”Condition” and “Flow”-
>”Loop”->”Counter”.

54
8.4.7. Matrix loops
The Matrix command is designed to execute loops that allow the robot to perform raster-
movements, for example for palletizing tasks. It can be accessed through the menu item
“Flow”->”Matrix”.

The illustration below shows the movement pattern that can be achieved by using the Matrix
command.

The position variables given as “Position A”, “Position B” and “Position C” define the corners of
the area that will be covered by the matrix loop (see illustration above). The number of steps
that are to be made are given by “X (from A to B)” and “Y (from A to C)”. For example, in the
illustration above, X would be 4 and Y would be 3.

55
The block between “Matrix” and “Matrix End” will be executed for each step. The position
variable given to “Target” will contain the position of the current target point for the current
step. Row and column of the current step will be stored in the number variables given to
“Counter X” and “Counter Y” respectively.

56
8.4.8. Subprograms
The Sub command can be used to call subprograms.

The path to the file of the subprogram is given under “Filename”. It is relative to the Programs
subfolder of iRC’s Data folder. The command can be accessed via the menu item “Flow”-
>”Subprogram”.

57
8.5. Motion
8.5.1. Abort conditions
An abort condition can be given to any motion command. It is a conditional expression,
following the syntax described in section Fehler! Verweisquelle konnte nicht gefunden
werden. . During the execution of the motion command the statement is continuously
evaluated, and the moment it evaluates to “True” the robot will stop moving. It can be specified
under “Abort condition” for each motion command respectively:

8.5.2. Acceleration and smoothing

In Motion commands joint accelerations can be defined, to prevent abrupt movement of the
robot. This can be done for a single motion command, but also for a combination of up to a
maximum of 10 commands. It is also possible to smooth out the corners within the path defined
by blocks of consecutive motion commands. This allows the robot to go through the corners
without coming to a full stop. If corner smoothing is set to 0% the robot stops at every corner
for a short moment. This leads to a more abrupt motion.

Any non-motion command will divide such a motion set and interrupt smoothing.
Parameters:

 “Acceleration”:
Percentage of the maximally possible acceleration.
 “Smoothing”:
Scope of the smoothing in percent.

58
8.5.3. Joint motion
The Joint command moves the robot to a (absolute) target position given in joint coordinates.
The resulting motion of the TCP will typically be a curve and not a straight line. The target
position can be given in the following ways (choose corresponding “Source”):

 “Constant”: The target position is a constant value for each axis.

 “Variable”: The target position is taken from the position variable given to
“Variable”.

The movement speed is given by “Velocity”. It is measured in percent of the maximally allowed
movement speed for the respective robot axes.
The joint command can be accessed in iRC’s Program Editor under the menu entries “Action”-
>”Joint motion” and “Action”->”Variable motion”->”Joint”.

59
8.5.4. Linear motion
The Linear command moves the robot to an (absolute) target position given in Cartesian
coordinates. The resulting motion of the TCP will follow a straight line. The target position can
be given in the following ways (choose corresponding “Source”):
 “Constant”:
The target position is a constant given by Cartesian coordinates x,y,z and Euler
Angles A,B,C and positions of external axes if supported by the current robot
kinematic.

 “Variable”:
The target position is taken from the position variable given to “Variable”.

60
The movement speed is given by “Velocity”. It is measured in mm/s, if it exceeds the maximally
allowed movement speed of the robot it will cause a kinematic error during execution.
The joint command can be accessed in iRC’s Program Editor under the menu entries “Action”-
>”Linear motion” and “Action”->”Variable motion”->”Linear”.

8.5.5. Relative motion

The Relative command allows to move the robot relative to its current position. It can be
accessed via the menu items under “Action”->”Relative motion”.

The following modes of relative motion can be chosen under “Type”:

 “Joint”:
The relative offset is specified in joint coordinates. The movement speed is given by
“Velocity”. It is measured in percent of the maximally allowed movement speed for
the respective robot axes.
61
 “Linear – Base”:
A linear movement with an offset specified in Cartesian coordinates will be
performed. The coordinate system used for the offset is the robot coordinate
system. The speed is given by “Velocity”. It is measured in mm/s, if it exceeds the
maximally allowed movement speed of the robot, it will cause a kinematic error
during execution.

62
 “Linear – Tool”:
A linear movement with an offset specified in Cartesian coordinates will be
performed. The coordinate system used for the offset are tool coordinates. The
movement speed is given by “Velocity”. It is measured in mm/s, if it exceeds the
maximally allowed movement speed of the robot it will cause a kinematic error
during execution.

63
8.6. Gripper and digital I/O
8.6.1. Digital inputs
Digital inputs and global signals are accessible as reserved words in conditional statements as
expressions in section 4.1. For global signals these are GSig1, GSig2, … , for digital inputs these
are Din1, Din2, … . Depending on the state they will either evaluate to “True” or to “False”.

8.6.2. Digital outputs

The Digital Output command can be used to set the states of digital outputs and global signals.

Under “Channel type” it is possible to specify if a digital output or a global signal are to be set.
“Channel ID” specifies the channel of the digital output or global signal. Under “State” the
desired state after execution of the command is specified. The command is accessible in iRC’s
Program Editor by the menu entry “Action”->”Digital output”.

8.6.3. Opening/closing the gripper

The Gripper command allows to control the gripper of the robot. It is accessible in iRC’s
Program Editor by the menu entry “Action”->”Gripper”.

64
You can set the desired aperture, measured in percent, under “Aperture”. A value of 0%
represents a fully closed gripper, 100% represents a fully opened gripper. For grippers that can
only be either fully opened or fully close the threshold between these states is at 50%
aperture.

8.7. Camera
We are currently working on this feature. The command specification will follow soon.

65
 Stand-alone Operation with Embedded Computer
and the Operating Panel
To run the robot without a Windows PC connected, the Embedded Computer is necessary. It
runs the TinyCtrl software as Robot Control Software. The Embedded Computer allows to jog
the robot arm (using the Operating Panel), and to replay robot programs. To set up new
programs it is connected via Ethernet to a Windows Computer running iRC.

Figure 9.1: robolink DP with Embedded Computer as Robot Control

This section shows how to operate the robot with Embedded Computer and Operation Panel.

After all electrical connections to the Robot have been established, the Robot has been
switched on and the Emergency Stop Button has been released, the errors first need to be
"reset" and then the robot needs to be "enabled".

When moving the Robot, always keep a hand on the Emergency Stop Button to prevent it from
hitting an object unexpectedly, for example if it is about to collide with the table.

66
9.1. Reset Errors/Enable Robot
On the touchscreen display,
press the "Enable" button in the upper menu (top
right) to get to the Enable page.

Now press "Reset":

The status changes to "MNE" (Motor Not Enabled)

Press "Enable":
The status changes to "No Error".
"Not ref'd!" (in red) means not referenced.

9.2. Moving the robot with the 3-Axis Joystick

Once the Robot is enabled, the axes of the Robot can be moved.

1. To do this, press the "Jog" button at the top of

the display

2. Press A1.
Then move and turn the joystick.
You can now move the axes 1, 2 and 3.

3. Press A4.
Now, move axes 4 and 5 by moving and rotating
the joystick.

67
 4. Repeat steps 2 and 3 until:
 the Robot is roughly in a "gallows position" and
 the "reference pin" (Figure 7.4) on the flange of
5th axis points towards the Robot base.

9.3. Referencing
To enable an automatic program sequence, the Robot electronics must be referenced.
The type of referencing movement depends on the Robot or encoder type.

1. To do this, press the square "Enable" button at

the top edge of the display.

2. The Robot must be in "NoError" status. If it is in

an error state, enable it by pressing the round
"Reset" button followed by the "Enable" button.

3. Now press the "Ref All" button to reference all

axes. The Robot now carries out search
movements for each axis.

4. Referencing is complete when there is a 1 next

to Ref A1-A5 respectively.
For a 4-axis Robot, Ref A5 will remain at 0. Ref
E1 is intended for additional external axes.

5. After referencing, the axes are in the error

state. This is necessary because the actual
position has changed in the referencing process.

68
 6. Now press the round "Reset" button, followed
by the round "Enable" button. The Robot is now
referenced.

9.4. Starting and Stopping a Program

1. To do this, press the "Play" button at the top
edge of the display and use the "prev" and
"next" buttons to select the
Igus5DOF_TestMotion program.

2. Load the program using the "Load" button

3. Let the program play once using "Single Play".

4. "Cont. Play" plays the loaded program

continuously.

5. "Stop" stops the movement.

6. The slider "Override" can be moved to the

right to increase the speed of the movement
or to the left to decrease it.

9.5. Manually Setting the Digital Inputs/Outputs

The digital outputs can be activated and deactivated by pressing the illustrated switches.

If e.g. a gripper is connected to the DIO Module, this

can be activated or deactivated by switching the
illustrated switches.

If a signal is present at the digital input, it will be

displayed in the digital inputs field at the bottom
edge of the display.

69
The three buttons on the left side allow you to switch between several DIO Modules.

If a signal is present at the digital input, it will be displayed in the digital inputs field at the
bottom edge of the display.

9.6. Display of Status Information

Status information can be displayed by pressing the "Status" button at the top left corner of
the display.

The name of a program is displayed, e.g. while a

program is running.

The axis positions of axes 1-5 (or 1-4 for 4-axis

Robots) are displayed (A1-A5).

The temperature of the Stepper Modules is

also displayed. Due to the varying loads on the
individual axes different holding currents are
applied, which lead to changing temperatures
of the Stepper Modules.

9.7. Organize Programs on the Embedded Control

This iRC function is only available in combination with the Embedded Computer. When writing
programs on the Windows iRC software, these programs are automatically also downloaded
to the Embedded Computer.
With time there might be the necessity to re-organize these programs, e.g. to delete some of
them. This is possible with the button “Manage Programs” in the “Motion” tab.

70
Figure 9.2 igus® Robot Control Windows software with "Manage programs" icon (circled in blue).

71
 Project Configuration

10.1. Program
With “Configure Project / Program” the starting set up can be defined:
 File: which program to load during startup
 File logic: which logic program to load during startup. The logic file runs parallel to the
main program allowing e.g. to set lights.
 Override: the override (speed) that is set after startup.
 Replay mode: the replay mode that is set after startup

Figure 10.1:Configuration of the starting program in the backstage area.

10.2. Tool
With “Configure Project / Tool” the tool attached to the robot is chosen.
This setting changes the robot kinematic. Programs written using a different kinematic setting
cannot be replayed because this might lead to a collision.

Figure 10.2:Configuration of the tool in the backstage area.

72
10.3. Inputs / Outputs
With “Configure Project / IOs” the number of available inputs and outputs can be configured
and renamed. The corresponding names will show up in the Input/Output tab.

Figure 10.3:Configuration of Inputs / Outputs in the backstage area.

For the robolink robot control the base IO area is not used. Relevant is the DIN rail IO section.
The standard robot control comes with one DIO module with 7 inputs and 7 outputs. You can
define names for the IO here.
If another DIO module is added, then the setting has to be changed to “2 modules”, or “3
modules”.
The settings are automatically synced with the Embedded Computer.

10.4. Virtual Box

The virtual box settings allow to restrict the motion range of the robot arm. These restrictions
are monitored both, in linear and in joint motion.

73
 This functionality assists to avoid mechanical damages. It is not a functionality
rated for personal safety!

Figure 10.4: Robot arm violating the virtual box.

In manual jogging mode an error message appears on the left side of the iRC window.
When running a program that violates the virtual box the program is stopped with an error
message.

Advanced Robot Configuration

The robolink DP robots come with a standard set of parameters. If your application requires
changing parameters such as, joint length, etc. please get in contact.
Although many of these parameters can be changed in the robot configuration files, a GUI to
help with these changes is not available at present.

74
 Interfaces Configuration

12.1. Cameras
The iRC software has built-in support for receiving target positions from cameras. Currently
the IFM O2D is supported.

Figure 12.1: Camera configuration dialog.

The work piece position reported by the camera can be accessed with the “Camera” command
in the robot program, see section 8.7.

12.2. PLC Interface

The PLC interface (PLC = Programmable Logic Controller) allows the integration of the Robot
into a production system controlled by a PLC. In this way, the Robot can work without manual
interaction. Also, it is possible to connect third party control panel with push buttons to
simplify and restrict operation of the robot in a production environment.
Specifically, this interface assigns certain digital IO channels to special functions, such as:

75
 inputs: "reset/enable motors", "start/stop program”, "reference";
 outputs: "noFault", "enabled" and "program running".
Further details are available on the Wiki (section "PLC interface", http://wiki.cpr-robots.com/).

12.3. CRI Ethernet Interface

The Commonplace Robotics Interface (CRI) allows the Robot to be controlled via Ethernet.
The Robot can be moved, programs can be uploaded and executed. It allows the development
of a custom robot control software. The control software (TinyCtrl) on the Embedded
Computer and igus® Robot Control on the Windows PC communicate via the CRI interface.

This interface makes it possible to combine the igus® Robot Control functions with
application-specific algorithms, such as a teleoperation system or a database. The CRI
documentation and a C# sample project for a client can be downloaded on request.

76
 Troubleshooting

13.1. Support Contacts

In case of problems we would be happy to help!
 igus support landing page: https://www.igus.de/info/robotics-low-cost-robotics
 Phone: +49 (0) 2203-96498-255
 E-mail: ww-robot-control@igus.net
Please describe the problem briefly and send the file "logMessages.log"
from the folder C:\iRC-igusRobotControl\.

13.2. Online Tool - Fault Identification and Recovery

Via the igus support landing page you have access to web pages that allow to:
 Identify a problem based on user observations
 Propose solutions to the problem

77
13.3. Configuration of the Stepper Modules
The operating parameters of the Stepper Modules, particularly the motor currents, can be
adapted to the application. The Stepper Modules are delivered with a standard
parameterization for the specific Robot. Normally no change of the parameters is necessary.
If the Robot is to be operated at high loads or speeds, the motor currents can be increased.

This configuration can be done via the software tool "CPR ModuleCtrl". It can be downloaded
from the Wiki (http://wiki.cpr-robots.com/).

Figure 13.1. CPR ModuleCtrl Software, Stepper Motor Configuration Tab.

Figure 13.1 shows the configuration of the stepper motors. The behavior during referencing is
defined on the left side. Motor currents and microstepping are defined on the right side.

78
 The Current Scale parameters define the max. current during normal operation (Load),
during the start-up phase (Start), at standstill (Idle) and during referencing (Ref).
o The Stepper Module uses Trinamic CoolStep technology to adjust the motor current
between these values and a lower limit value, which is a fraction of the Current Scale
value.
o At lower Current Scale values, total power consumption and heat generation are lower.
However, a so-called "motor stall" can occur. In this case the current scale values must
be increased.
o At higher values, there is no motor stall, but the system becomes hotter.
 The current scale during the reference movement can be set separately to avoid damage,
e.g. by collision.
 The higher the microstepping, the smoother the movement. In operation without encoder
a microstepping of max. 1:64 should be used.
 It is possible to reverse the direction of rotation of the encoder. This change is applied after
the next cold start of the controller. If the encoder direction does not correspond to the
motor direction, the axis does not move correctly but accelerates until a position lag error
occurs. In this case, the encoder direction must be changed, and the system restarted.
The axis should then function properly.

13.4. Calibration of the Robot

The robolink® Robot Arms are referenced using reference switches. For design reasons,
however, these are not exactly on the zero positions of the axes. The offset between reference
switch and zero position is stored in the EEPROM of the Stepper Modules.

If the Robot was supplied with the Robot Controller, these offsets are already set.

To perform the calibration yourself, you will find the necessary steps on the Wiki (section
"Define the Zero Position Offsets", http://wiki.cpr-robots.com/).

79
13.5. Error Codes
The Robot Controller provides several status information:
 Status LEDs on the Electronic Modules.
 igus® Robot Control status information, received via CAN status bytes.

13.5.1. Status LED of the Electronic Modules

Support Module:
Green LED on: Logic power supply on
Green LED flashing: CAN communication with the Support Module
Orange LED on: Error
Red LED on: Emergency Stop Button pressed

Stepper Module:
Green LED on: Logic power supply on
Green LED flashing: CAN communication with the Stepper Module
Orange LED on: Reference switch is active
Red LED on: Stepper Module is in error state or motor is not
enabled

Digital In/Out Module:

Green LED on: Logic power supply on
Green LED flashing: CAN communication with the DIO module
Orange LED on: The state of an input or output changes.
Red LED on: Error

80
13.5.2. CAN-Bus and iRC Status Information

Bit in
Error Meaning Measures
error byte
Bus dead The CAN-Bus is not available. Check the plug connections of the
Reasons are missing power power supply and the CAN line.
supply or missing plug Restart the control computer.
connections.
Temp Bit 1 The temperature of the Motor Check if the ventilation is installed
Modules is too high. and working. The motor current
may have to be reduced.
E-Stop / Bit 2 Emergency stop or voltage too Check if the Emergency Stop
Supply low. Button is released.
MNE Bit 3 No error. The motors are not Press the "Enable motors" button.
Motor not released yet.
enabled
COM Bit 4 The time period without CAN The position commands via the
Comm command from the controller CAN-Bus must be sent in short
Watch was too long. intervals. Turn off other programs
Dog or update / virus scan functions.
LAG Bit 5 Position lag error. The Robot Decrease the speed of movement.
Position cannot maintain the target
Lag position.
ENC Bit 6 Error in motor encoder or Check the encoder cables
Encoder absolute encoder
Error
OC Bit 7 Overcurrent in the motors Reduce the motor current
Over
Current
DRV Bit8 Error in motor driver or motor Drive specific
algorithm

After an "Error Reset" the normal status of the axes is 0x04 (motor not enabled).
After releasing the motors the status is 0x00, now the axes are ready for operation.

81
82
83