Page 4
The information in this manual is subject to change without notice and should not be construed as a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this manual. Except as may be expressly stated anywhere in this manual, nothing herein shall be construed as any kind of guarantee or warranty by ABB for losses, damages to persons or property, fitness for a specific purpose or the like.
Page 6
Example of creating asynchronously raised error ............ Example with movements in error handler ............. Running a subset of a MultiMove system How to continue with one or more drive units inactive..........Running a subset in the “Unsync Arc” examples .............
Usage This manual can be used either as a brief description to find out if MultiMove is the right choice for solving a problem, or as a description of how to use it. This manual provides information about system parameters and RAPID components related to MultiMove, and many examples of how to use them.
Page 8
• Added information about the Ethernet switch, see Ethernet connections on page Released with RobotWare 6.02. Section Create a MultiMove system on page 27 updated to use Installation Manager. Released with RobotWare 6.04. • Minor corrections. Released with RobotWare 6.05.
Product documentation Categories for user documentation from ABB Robotics The user documentation from ABB Robotics is divided into a number of categories. This listing is based on the type of information in the documents, regardless of whether the products are standard or optional.
Several robots can cooperate to lift heavy objects. Included functionality MultiMove allows up to 7 tasks to be motion tasks (task that has move instructions). Since no more than 4 drive modules can be used, a controller can handle up to 4 robots.
One Ethernet cable and one safety signal cable for each additional drive module must be connected to the control module. A MultiMove control module is equipped with an extra Ethernet switch to communicate with the additional drive modules. This manual only describes what is specific for a MultiMove installation. For more information about installation and commissioning of the controller, see Product manual - IRC5.
Page 21
It is important that the right drive module is connected to the right Ethernet connection. If the order of the Ethernet connections do not match the selections made in Installation Manager (see Create a MultiMove system on page 27), the robot configuration will not correlate to the correct robot.
Page 22
(already connected at delivery) Note The Ethernet switch is mandatory for MultiMove, also when running MultiMove with only one axis computer in the system. For example, when running MultiMove on one robot together with a positioner or additional axes. Continues on next page...
2.1.3 Connections on the drive module Already connected at delivery When a MultiMove system is delivered from ABB, the Ethernet cable and the safety signal cable are already connected to the drive module. You only need to know how these cables are connected if you are going to change the hardware configuration or replace parts.
Creating a new system is described in Operating manual - RobotStudio. Select the MultiMove option under System Options. What is specific for a MultiMove system is that in the tab Drive Modules, one robot should be selected for each drive module.
About the system parameters This chapter contains a brief description of each parameter that is specific for MultiMove. Parameters that are used the same way as for a single robot system are not mentioned here. For more information about system parameters, see Technical reference manual - System parameters.
Indicates if it should be possible to deactivate the mechanical unit. In a single robot system it is not possible to deactivate a robot. In a MultiMove system, one robot can be deactivated while an- other is still active. Motion Planner A motion planner calculates the movements of a mechanical unit group.
Relative calibration is used to calibrate the base coordinate system of one robot, using a robot that is already calibrated. This calibration method can only be used for a MultiMove system where two robots are placed close enough to have some part of their working areas in common.
5.1 FlexPendant for MultiMove system About FlexPendant for MultiMove system Working with the FlexPendant in a MultiMove system is not very different from a single robot system. This chapter will explain a few things that are specific for a MultiMove system. For general information about the FlexPendant, see Operating manual - IRC5 with FlexPendant.
An additional axis that is not active. Either the mechanical unit is deactivated, or the task inactive. xx0400001170 Example en0400001158 This is an example of a MultiMove system with 4 robots and 2 additional axes, where... • robot 1 belongs to a task that is inactive. •...
Page 49
5 User interface specific for MultiMove 5.2 Status bar indications Continued • additional axis 1 is selected mechanical unit and robot 3 and 4 are coordinated with additional axis 1. Any jogging at this point will move these three mechanical units.
5 User interface specific for MultiMove 5.3 Opening the Program Editor 5.3 Opening the Program Editor Select task When opening the Program Editor for a system with more than one task, a list of all the tasks will be displayed. By tapping the task you want, the program code for that task is displayed.
5 User interface specific for MultiMove 5.4 Production Window 5.4 Production Window The graphical display In a system with more than one motion task there will be one tab for each motion task. By tapping a tab, you can see the program code for that task and where the program pointer and motion pointer are in that task.
5 User interface specific for MultiMove 5.5 Mechanical unit menu 5.5 Mechanical unit menu The graphical display In the QuickSet menu, tap the Mechanical unit menu button. All mechanical units will be shown. en0400000789 The selected mechanical unit is highlighted with a frame around it.
This will only work in manual mode, no STATIC or SEMISTATIC task can be started, stepped, or stopped in auto mode. Task Panel Settings To start the Task Panel Settings, tap the ABB menu, and then Control Panel, FlexPendant and Task Panel Settings. Selecting tasks Use this procedure to select which of the tasks are to be started with the START button.
Page 54
5 User interface specific for MultiMove 5.6 Select which tasks to start with START button Continued Resetting debug settings in manual mode Use this procedure to resume normal execution manual mode. Action Select Only Normal tasks in the Task Panel Settings.
6.1 RAPID components 6 Programming 6.1 RAPID components Data types This is a brief description of each data type in MultiMove. For more information, see the respective data type in Technical reference manual - RAPID Instructions, Functions and Data types. Data type...
Page 56
MoveExtJ is used to move additional axes, in a task without any robot. Functions This is a brief description of each function in MultiMove. For more information, see the respective function in Technical reference manual - RAPID Instructions, Functions and Data types.
8 Running a subset of a MultiMove system 8.1 How to continue with one or more drive units inactive. 8 Running a subset of a MultiMove system 8.1 How to continue with one or more drive units inactive. Overview It is possible to disconnect a drive module and continue working, for example: •...
Page 96
8 Running a subset of a MultiMove system 8.1 How to continue with one or more drive units inactive. Continued Action Info/illustration Remove the connector from X22 in the drive module. When the connector is removed the following message appears on the Flex Pendant: Event Message 50320, Drive Module Disconnected.
Page 97
8 Running a subset of a MultiMove system 8.1 How to continue with one or more drive units inactive. Continued Action Info/illustration Switch on the power to the controller. Select a new robot system that is configured without the disconnected mechanical unit.
8 Running a subset of a MultiMove system 8.2 Running a subset in the “Unsync Arc” examples 8.2 Running a subset in the “Unsync Arc” examples Example with Drive Module Disconnect In this example the configuration is according to “UnsyncArc”, and an error occurs on the process equipment on robot 1.
Page 99
8 Running a subset of a MultiMove system 8.2 Running a subset in the “Unsync Arc” examples Continued Action Info/illustration Remove the safety signal connection of drive module 1 Ethernet connections on from X7 on the panel board in the control module. Move...