ABB IRC5 M2004 Robot Controller Operating manual

ABB Robotics

Operating manual

Trouble shooting, IRC5

Operating manual - Trouble shooting, IRC5

Robot Controller

IRC5

M2004

Document ID: 3HAC020738-001

Revision: K

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.

In no event shall ABB be liable for incidental or consequential damages arising from use of this manual and products described herein.

This manual and parts thereof must not be reproduced or copied without ABB's written permission, and contents thereof must not be imparted to a third party nor be used for any unauthorized purpose. Contravention will be prosecuted.

Additional copies of this manual may be obtained from ABB at its then current charge.

© Copyright 2005-2010 ABB All rights reserved.

ABB AB

Robotics Products

SE-721 68 Västerås

Sweden

Table of Contents

Overview of this manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Safety 7

1.1 Safety signals in the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2 Safety symbols on the manipulator labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3 Safety during trouble shooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.4 Applicable safety standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1.5 Safe Trouble Shooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.5.1 DANGER - Robot without axes' holding brakes are potentially lethal! . . . . . . . . . . . . . . . . . . . . 16

1.5.2 DANGER - Live voltage inside Drive Module!. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1.5.3 WARNING - The unit is sensitive to ESD! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1.5.4 CAUTION - Hot parts may cause burns! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2 Trouble shooting Overview 23

2.1 Documentation and references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.3 Standard toolkit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.4 Tips and Tricks while trouble shooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.4.1 Trouble shooting strategies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.4.2 Work systematically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.4.3 Keeping track of history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.5 Filing an error report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3 Troubleshooting by fault symptoms 33

3.1 Start-up failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.2 Controller not responding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.3 Low Controller performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.4 All LEDs are OFF at Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.5 No voltage in service outlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.6 Problem starting the FlexPendant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.7 Problem connecting FlexPendant to the controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.8 Erratic event messages on FlexPendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.9 Problem jogging the robot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.10 Reflashing firmware failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.11 Inconsistent path accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.12 Oil and grease stains on motors and gearboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.13 Mechanical noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.14 Manipulator crashes on power down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.15 Problem releasing Robot brakes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.16 Intermittent errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4 Trouble shooting by Unit 55

4.1 Trouble shooting the FlexPendant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.2 Trouble shooting communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4.3 Trouble shooting fieldbuses and I/O units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4.4 Trouble shooting power supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.4.1 Trouble shooting DSQC 604 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59



3HAC020738-001 Revision: K 3

Table of Contents

5 Descriptions and background information 69

5.1 Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5.1.1 LEDs in the Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5.1.2 LEDs in the Drive Module for Drive System 04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

5.1.3 LEDs in the Drive Module for Drive System 09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6 Trouble shooting by Event log 83

Index 465

4 3HAC020738-001 Revision: K

Overview of this manual

Overview of this manual

About this manual

This manual contains information, procedures and descriptions, for trouble shooting IRC5 based robot systems.

Usage

Who should read this manual?

This manual is intended for the following personnel:

•

Machine and robot operators qualified to perform very basic trouble shooting and reporting to service personnel.

• Programmers qualified to write and change RAPID programs.

•

Specialized trouble shooting personnel, usually very experienced service personnel, qualified for methodically isolating, analyzing and correcting malfunctions within the robot system.

Prerequisites

This manual should be used whenever robot operation is interrupted by malfunction, regardless of whether an error event log message is created or not.

The reader should:

•

Have extensive experience in trouble shooting industrial electro-mechanical machinery.

• Have in depth knowledge of the robot system function.

•

Be familiar with the actual robot installation at hand, its surrounding equipment and peripherals.

References

Reference:

Product manual - IRC5

Emergency safety information

General safety information

Operating manual - IRC5 with FlexPendant

Operating manual - RobotStudio

Operating manual - Getting started, IRC5 and RobotStudio

Technical reference manual - System parameters

Application manual - MultiMove

Document ID:

3HAC021313-001

3HAC027098-001

3HAC031045-001

3HAC16590-1

3HAC032104-001

3HAC027097-001

3HAC17076-1

3HAC021272-001

3HAC020738-001 Revision: K

Continues on next page

5

Overview of this manual

Continued

Revisions

F

G

H

C

D

E

Revision

-

A

B

J

K

Description

First edition.

Information has been added.

The document has been partly restructured.

Information on how to submit error report has been changed.

Information on RAPID change logs have been added.

Event log messages have been added.

Updated Event log messages.



Minor corrections. Updated Event log messages.

Minor corrections. Updated Event log messages.

New information in section Serial Measurement Unit regarding the battery pack.

More detailed information about trouble shooting power supplies DSQC 604,

661 and 662.

Removed safety I/O signals: DRV1PANCH1, DRV1PANCH2, DRV1SPEED.

New drive system introduced. Drive System 04 and Drive System 09 are both described.

Released with RobotWare 5.13

The chapter Safety updated with:

• Updated safety signal graphics for the levels Danger and Warning,

see

Safety signals in the manual on page 7

.

• New safety labels on the manipulators, see

Safety symbols on the manipulator labels on page 9

.

•

Updated the graphic in the section

DANGER - Live voltage inside

Drive Module! on page 17

.

The contents in the following sections were updated:

•

Corrections regarding drive system information in chapter

Descriptions and background information on page 65

• Restructured the chapters as per the new document startergy.

• Updated the graphic in the Recommended actions of the section

No voltage in service outlet on page 38

.

•

Updated the Possible causes in the section

Problem starting the

FlexPendant on page 40

.

• Updated the graphics in the section

LEDs in the Control Module on page 65

.

•

Updated the graphic in Possible causes of the section

Problem releasing Robot brakes on page 50

.



1 Safety

1.1. Safety signals in the manual

1 Safety

1.1. Safety signals in the manual

Introduction to safety signals

This section specifies all dangers that can arise when doing the work described in this manual.

Each danger consists of:

• A caption specifying the danger level (DANGER, WARNING, or CAUTION) and the type of danger.

•

A brief description of what will happen if the operator/service personnel do not eliminate the danger.

• An instruction on how to eliminate the danger to simplify doing the work.

Danger levels

The table below defines the captions specifying the danger levels used throughout this manual.

Symbol

danger warning

Designation

DANGER

WARNING

ELECTRICAL

SHOCK

Significance

Warns that an accident will occur if the instructions are not followed, resulting in a serious or fatal injury and/or severe damage to the product. It applies to warnings that apply to danger with, for example, contact with high voltage electrical units, explosion or fire risk, risk of poisonous gases, risk of crushing, impact, fall from height, etc.

Warns that an accident may occur if the instructions are not followed that can lead to serious injury, possibly fatal, and/or great damage to the product. It applies to warnings that apply to danger with, for example, contact with high voltage electrical units, explosion or fire risk, risk of poisonous gases, risk of crushing, impact, fall from height, etc.

Warns for electrical hazards which could result in severe personal injury or death.

Electrical shock

CAUTION caution

Warns that an accident may occur if the instructions are not followed that can result in injury and/or damage to the product. It also applies to warnings of risks that include burns, eye injury, skin injury, hearing damage, crushing or slipping, tripping, impact, fall from height, etc. Furthermore, it applies to warnings that include function requirements when fitting and removing equipment where there is a risk of damaging the product or causing a breakdown.



7

1 Safety

1.1. Safety signals in the manual

Continued

Symbol Designation Significance

ELECTROSTATIC

DISCHARGE (ESD)

Warns for electrostatic hazards which could result in severe damage to the product.

Electrostatic discharge

(ESD)

NOTE Describes important facts and conditions.

Note

TIP Describes where to find additional information or how to do an operation in an easier way.

Tip


1 Safety

1.2. Safety symbols on the manipulator labels

1.2. Safety symbols on the manipulator labels

Introduction to labels

This section describes safety symbols used on labels (stickers) on the manipulator.

Symbol are used in combinations on the labels, describing each specific warning. The descriptions in this section are generic, the labels can contain additional information such as values.

Types of labels

Both the manipulator and the controller are marked with several safety and information labels, containing important information about the product. The information is useful for all personnel handling the manipulator system, for example during installation, service, or operation.

The safety labels are language independent, they only use graphics. See

Symbols on safety labels on page 9

.

The information labels can contain information in text (English, German, and French).

Symbols on safety labels

Symbol Description

Warning!

Warns that an accident may occur if the instructions are not followed that can lead to serious injury, possibly fatal, and/or great damage to the product. It applies to warnings that apply to danger with, for example, contact with high voltage electrical units, explosion or fire risk, risk of poisonous gases, risk of crushing, impact, fall from height, etc.

xx0900000812 xx0900000811

Caution!

Warns that an accident may occur if the instructions are not followed that can result in injury and/or damage to the product.

It also applies to warnings of risks that include burns, eye injury, skin injury, hearing damage, crushing or slipping, tripping, impact, fall from height, etc. Furthermore, it applies to warnings that include function requirements when fitting and removing equipment where there is a risk of damaging the product or causing a breakdown.

Prohibition

Used in combinations with other symbols. xx0900000839



9

1 Safety


Continued


Product manual

Read the product manual for details.

xx0900000813

Before dismantling see product manual

xx0900000816

Do not dismantle

Dismantling this part can cause injury.

xx0900000815 xx0900000814 xx0900000808 xx0900000810

Extended rotation

This axis has extended rotation (working area) compared to standard.

Brake release

Pressing this button will release the brakes. This means that the manipulator arm can fall down.

Tip risk when loosening bolts

The manipulator can tip over if the bolts are not securely fastened.

Crush

Risk for crush injuries.

xx0900000817

10



Symbol

1 Safety


Continued

Description

Heat

Risk of heat that can cause burns.

xx0900000818 xx0900000819

Moving robot

The robot can move unexpectedly.

Brake release buttons

xx0900000820

Lifting bolt

xx0900000821

Lifting of robot

xx0900000822 xx0900000823

Oil

Can be used in combination with prohibition if oil is not allowed.



11

1 Safety


Continued


Mechanical stop

xx0900000824 xx0900000825

Stored energy

Warns that this part contains stored energy.

Used in combination with Do not dismantle symbol.

Pressure

Warns that this part is pressurized. Usually contains additional text with the pressure level.

xx0900000826

Shut off with handle

Use the power switch on the controller.

xx0900000827


1 Safety

1.3. Safety during trouble shooting

1.3. Safety during trouble shooting

General

All normal service work; installation, maintenance and repair work, is usually performed with all electrical, pneumatic and hydraulic power switched off. All manipulator movements are usually prevented by mechanical stops etc.

Trouble shooting work differs from this. While trouble shooting, all or any power may be switched on, the manipulator movement may be controlled manually from the FlexPendant, by a locally running robot program or by a PLC to which the system may be connected.

Dangers during trouble shooting

This implies that special considerations unconditionally must be taken when trouble shooting:

• All electrical parts must be considered as live.

•

The manipulator must at all times be expected to perform any movement.

• Since safety circuits may be disconnected or strapped to enable normally prohibited functions, the system must be expected to perform accordingly.


1 Safety

1.4. Applicable safety standards

1.4. Applicable safety standards

Standards, EN ISO

The manipulator system is designed in accordance with the requirements of:

Standard

EN ISO 12100 -1

EN ISO 12100 -2

EN ISO 13849-1

EN ISO 13850

EN ISO 10218-1

1

EN ISO 9787

EN ISO 9283

Description

Safety of machinery - Basic concepts, general principles for design - Part 1: Basic terminology, methodology

Safety of machinery - Basic concepts, general principles for design - Part 2: Technical principles

Safety of machinery, safety related parts of control systems -

Part 1: General principles for design

Safety of machinery - Emergency stop - Principles for design

Robots for industrial environments - Safety requirements -Part 1

Robot

Manipulating industrial robots, Coordinate systems and motion nomenclatures

Manipulating industrial robots, Performance criteria and related test methods

Classification of air cleanliness

Ergonomics of the thermal environment - Part 1

EMC, Generic emission

EN ISO 14644-1

2

EN ISO 13732-1

EN 61000-6-4

(option 129-1)

EN 61000-6-2

EN IEC 60974-1

3

EN IEC 60974-10

3

EN 60204-1

IEC 60529

EMC, Generic immunity

Arc welding equipment - Part 1: Welding power sources

Arc welding equipment - Part 10: EMC requirements

Safety of machinery - Electrical equipment of machines - Part 1

General requirements

Degrees of protection provided by enclosures (IP code)

1. There is a deviation from paragraph 6.2 in that only worst case stop distances and stop times are documented.

2. Only robots with Protection Clean Room.

3. Only valid for arc welding robots. Replaces EN 61000-6-4 for arc welding robots.

European standards

Standard

EN 614-1

EN 574

EN 953

Description

Safety of machinery - Ergonomic design principles - Part 1:

Terminology and general principles

Safety of machinery - Two-hand control devices - Functional aspects - Principles for design

Safety of machinery - General requirements for the design and construction of fixed and movable guards

14



1 Safety

1.4. Applicable safety standards

Continued

Other standards

Standard

ANSI/RIA R15.06

ANSI/UL 1740

(option 429-1)

CAN/CSA Z 434-03

(option 429-1)

Description

Safety Requirements for Industrial Robots and Robot Systems

Safety Standard for Robots and Robotic Equipment

Industrial Robots and Robot Systems - General Safety Requirements


1 Safety

1.5.1. DANGER - Robot without axes' holding brakes are potentially lethal!

1.5 Safe Trouble Shooting

1.5.1. DANGER - Robot without axes' holding brakes are potentially lethal!

Description

Since the robot arm system is quite heavy, especially on larger robot models, it is dangerous if the holding brakes are disconnected, faulty, worn or in any way rendered non-operational.

For instance, a collapsing IRB 7600 arm system may kill or seriously injure a person standing beneath it.

Elimination

Action Info/illustration

1. If you suspect that the holding brakes are non-operational, secure the robot arm system by some other means before working on it.

2. If you intentionally render the holding brakes non-operational by connecting an external voltage supply, the utmost care must be taken!

Weight specifications etc. may be found in the Product manual of each robot model.

How to correctly connect an external voltage supply is detailed in the Product

manual of each robot model.

DANGER!

NEVER stand inside the robot working area when disabling the holding brakes unless the arm system is supported by some other means!

DANGER!

Under no circumstance stand beneath any of the robot’s axes!


1 Safety

1.5.2. DANGER - Live voltage inside Drive Module!

1.5.2. DANGER - Live voltage inside Drive Module!

Description

The Drive Module has live voltage potentially accessible directly behind the rear covers and inside the front cover, even when the main switches have been switched off.

A en1000000049

B en1000000050

A Live voltage at transformer terminals even if the main power switches have been

switched off.

B Live voltage at Motors ON terminals even if the main power switches have been

switched off.



17

1 Safety

1.5.2. DANGER - Live voltage inside Drive Module!

Continued

Elimination

Read this information before opening the rear cover of either module.

Step Action

1. Make sure the incoming mains power supply has been switched off.

2. Use a voltmeter to verify that there is not voltage between any of the terminals.

3. Proceed with the service work.


1 Safety

1.5.3. WARNING - The unit is sensitive to ESD!

1.5.3. WARNING - The unit is sensitive to ESD!

Description

ESD (electrostatic discharge) is the transfer of electrical static charge between two bodies at different potentials, either through direct contact or through an induced electrical field. When handling parts or their containers, personnel not grounded may potentially transfer high static charges. This discharge may destroy sensitive electronics.

Elimination

Action Note

1. Use a wrist strap Wrist straps must be tested frequently to ensure that they are not damaged and are operating correctly.

2. Use an ESD protective floor mat.

The mat must be grounded through a currentlimiting resistor.

3. Use a dissipative table mat.

The mat should provide a controlled discharge of static voltages and must be grounded.

Location of wrist strap button

The location of the wrist strap button is shown in the following illustration.

IRC5

The wrist strap button is located in the top right corner.

xx0500002171

A Wrist strap button



19

1 Safety

1.5.3. WARNING - The unit is sensitive to ESD!

Continued

Panel Mounted Controller xx0600003249

A

B

C

Panel Mounted Control Module

Panel Mounted Drive Module

Wrist strap button NOTE! When not used, the wrist strap must always be attached to the wrist strap button.


1 Safety

1.5.4. CAUTION - Hot parts may cause burns!

1.5.4. CAUTION - Hot parts may cause burns!

Description

During normal operation, many manipulator parts become hot, especially the drive motors and gears. Sometimes areas around these parts also become hot. Touching these may cause burns of various severity.

Because of a higher environment temperature, more surfaces on the manipulator get hot and may result in burns.

NOTE!

The drive parts in the cabinet can be hot.

Elimination

The instructions below detail how to avoid the dangers specified above:

Action

1. Always use your hand, at some distance, to feel if heat is radiating from the potentially hot component before actually touching it.

2. Wait until the potentially hot component has cooled if it is to be removed or handled in any other way.

3. The Bleeder can be hot upto 80 degrees.

Info


1 Safety

1.5.4. CAUTION - Hot parts may cause burns!


2 Trouble shooting Overview

2.1. Documentation and references


2.1. Documentation and references

General

A great deal of effort was put into writing the event log messages as well as the technical documentation. Though imperfect, they may give vital clues. They are also constantly being upgraded.

The product documentation is available in several languages.

Read the documentation!

Do not wait until nothing else works to read the manual!

References to document numbers are specified in the chapter Reference information in

Product manual - IRC5.

Read the circuit diagram!

The complete electrical circuitry of the controller is documented in Product manual - IRC5.

It contains a lot of information useful, or even essential, to a trained trouble shooter.

Read the logs!

The error event logs which may be viewed on either the FlexPendant or RobotStudio, contain lots of information about any malfunction detected by the system.

en0300000547

Check the electronical unit's LEDs!

If a fault is thought to be caused by an electronic unit (circuit board in the controller or other), the LEDs on the unit front may give leads.

These are described in section

Indications on page 65

.



2.2. Overview

2.2. Overview

How to use this manual when trouble shooting

The illustration and description detail how to put the information in this manual to best use during trouble shooting the robot system.

en0400001200

Trouble shooting manual

Fault symptoms and malfunctions:

•

Each fault or error is first detected as a symptom, for which an error event log message may or may not be created. It could be an error event log message on the FlexPendant, an observation that the gearbox on axis 6 is getting hot or that the controller can not be started. The faults displaying an event log message are listed in the end of this manual.

Instructions, how to correct faults:

•

The instructions are divided into two main categories: descriptions of how to correctly handle the different parts of the system and instructions of how to remedy faults causing the symptoms specified above. The latter category is divided into two sub-



2.2. Overview categories, depending on whether to trouble shoot a specific symptom or a suspected unit causing the problem. The first category contains information on how to use the event log to facilitate trouble shooting, etc.

Recommended working procedures:

•

Here, you will find a procedure for how to correctly perform certain specific tasks.

These may be used to make sure the seemingly irrational behavior of the system is not due to incorrect handling.

Basic reference info:

•

This section contains information about what tools to use, references to documents that may be useful when trouble shooting, etc.

Description, systems:

•

The different systems and sub-systems are described to give a better understanding of its function when it works “as it’s supposed to”. This enables the trouble shooter to better see and understand the differences between a system that’s functional and one that’s not.

Description, components and details:

•

Specific details of the system are described with regards to their function, etc.

Description, functions:

•

Contains descriptions on how specific functions within the system work, e.g the RUN chain, and what signals and other systems affect that particular function. This provides for a better understanding of the relations and mechanisms of the robot system.

Indications

•

All indication LEDs and other indications (as found on the Control and Drive Modules as well as separate circuit boards, etc) are described in this section along with information about their indication modes and significances respectively.

Recommended actions are often specified or references containing such instructions.

Event log messages:

•

This section is basically a printout of all available event log messages. These may be displayed either on the FlexPendant or using RobotStudio. Having access to all messages at the same time may be useful during trouble shooting.

Additional information

In addition to the information given in this document, other documents may provide vital information, e.g. the Circuit Diagram.

Such useful documents are listed in

Overview of this manual on page 5

.



25


2.3. Standard toolkit

Continued

2.3. Standard toolkit

General

Listed are tools required to perform the actual trouble shooting work. All tools required to perform any corrective measure, such as replacing parts, are listed in their Product Manual section respectively.

Contents, standard toolkit, IRC5

Tool

Screw driver, Torx

Screw driver, Torx

Ball tipped screw driver, Torx

Screw driver, flat blade



Screw driver

Box spanner

Remark

Tx10

Tx25

Tx25

4 mm

8 mm

12 mm

Phillips-1

8 mm

Contents, standard toolkit, trouble shooting

Qty Art. no. Tool

1

1

-

1

-

-

-

Normal shop tools

Multimeter

Oscilloscope

Recorder

Rem.

-

-

-

Contents as specified above.



2.4.1. Trouble shooting strategies

2.4 Tips and Tricks while trouble shooting

2.4.1. Trouble shooting strategies

Isolate the fault!

Any fault may give rise to a number of symptoms, for which error event log messages may or may not be created. In order to effectively eliminate the fault, it is vital to distinguish the original symptom from the consequential ones.

A help in isolating the fault may be creating a historical fault log as specified in section

Make a historical fault log! on page 29

.

Split the fault chain in two!

When trouble shooting any system, a good practice is to split the fault chain in two. This means:

• identify the complete chain.

• decide and measure the expected value at the middle of the chain.

• use this to determine in which half the fault is caused.

• split this half into two new halves, etc.

• finally, a single component may be isolated. The faulty one.

Example

A specific IRB 7600 installation has a 12 VDC power supply to a tool at the manipulator wrist. This tool does not work, and when checked, there is no 12 VDC supply to it.

• Check at the manipulator base to see if there is 12 VDC supply. Measurement show there are no 12 VDC supply. (Reference: Circuit Diagram in the

Product manual,

IRC5

)

•

Check any connector between the manipulator and the power supply in the controller.

Measurement show there are no 12 VDC supply. (Reference: Circuit Diagram in the

Product manual, IRC5

)

• Check the power supply unit LED. (Reference:


)

Check communication parameters and cables!

The most common causes of errors in serial communication are:

•

Faulty cables (e.g. send and receive signals are mixed up)

• Transfer rates (baud rates)

•

Data widths that are incorrectly set.

Check the software versions!

Make sure the RobotWare and other software run by the system are the correct version.

Certain versions are not compatible with certain hardware combinations.

Also, make a note of all software versions run, since this will be useful information to the

ABB support people.

How to file a complete error report to your local ABB service personnel is detailed in section

Filing an error report on page 30

.



2.4.2. Work systematically

2.4.2. Work systematically

Do not replace units randomly!

Before replacing any part at all, it is important to establish a probable cause for the fault, thus determining which unit to replace.

Randomly replacing units may sometimes solve the acute problem, but also leaves the trouble shooter with a number of units that may/may not be perfectly functional.

Replace one thing at a time!

When replacing a presumably faulty unit that has been isolated, it is important that only one unit be replaced at a time.

Always replace components as detailed in the Repairs section of the Product manual of the robot or controller at hand.

Test the system after replacing to see if the problem has been solved.

If replacing several units at once:

• it is impossible to determine which of the units was causing the fault.

• it greatly complicates ordering a new spare part.

• it may introduce new faults to the system.

Take a look around!

Often, the cause may be evident once you see it. In the area of the unit acting erroneously, be sure to check:

• Are the attachment screws secured?

•

Are all connectors secured?

• Are all cabling free from damage?

•

Are the units clean (especially for electronic units)?

• Is the correct unit fitted?

Check for tools left behind!

Some repair and maintenance work require using special tools to be fitted to the robot equipment. If these are left behind (e.g. balancing cylinder locking device or signal cable to a computer unit used for measuring purposes), they may cause erratic robot behavior.

Make sure all such tools are removed when maintenance work is complete!



2.4.3. Keeping track of history

2.4.3. Keeping track of history

Make a historical fault log!

In some cases, a particular installation may give rise to faults not encountered in others.

Therefore, charting each installation may give tremendous assistance to the trouble shooter.

To facilitate trouble shooting, a log of the circumstances surrounding the fault gives the following advantages:

• it enables the trouble shooter to see patterns in causes and consequences not apparent at each individual fault occurrance.

• it may point out a specific event always taking place just before the fault, for example a certain part of the work cycle being run.

Check up the history!

Make sure you always consult the historical log if it is used. Also remember to consult the operator, or similar, who was working when the problem first occurred.

At what stage did the fault occur?

What to look for during trouble shooting depends greatly of when the fault occurred: was the robot just freshly installed? Was it recently repaired?

The table gives specific hints to what to look for in specific situations:

If the system has just: then:

been installed been repaired had a software upgrade been moved from one site to another (an already working robot)

Check:

• the configuration files

• connections

• options and their configuration

Check:

• all connections to the replaced part

• power supplies

• that the correct part has been fitted

Check:

• software versions

• compatibilities between hardware and software

• options and their configuration

Check:

• connections

• software versions



2.5. Filing an error report

2.5. Filing an error report

Introduction

If you require the assistance of ABB support personnel in trouble shooting your system, you may file a formal error report as detailed below.

In order for the ABB support personnel to better solve your problem, you may attach a special diagnostics file that the system generates on demand.

The diagnostics file includes:

• Event log A list of all system events.

•

Backup A backup of the system taken for diagnostics purposes.

• System information Internal system information useful to ABB support personnel.

NOTE that it is not required to create or attach any additional files to the error report if not explicitely requested by the support personnel!

Creating the diagnostics file

The diagnostics file is created manually as detailed below.

Action

1. Tap ABB, then Control Panel and then Diagnostics.

A display is shown:

30 en0500002175

2. Specify the name you want for the diagnostics file, the save folder of it and tap OK. The default save folder is C:/Temp, but any folder may be selected, for instance an externally connected USB memory.

This may take a couple of minutes, while “Creating file. Please wait!” is displayed.

3. To shorten file transfer time, you may compress the data into a zip-file.

4. Write a regular e-mail addressed to your local ABB support personnel, and make sure to include the following information:

• Robot serial number

• RobotWare version

• External options

• A written fault description. The more detailed, the easier for the ABB support personnel to assist you.

• if available, enclose the license key.

• attach the diagnostics file!

5. Mail it!


3 Troubleshooting by fault symptoms

3.1. Start-up failures


3.1. Start-up failures

Introduction

This section describes possible faults during start-up and the recommended action for each failure.

Consequences

Problem starting the sytem.

Symptoms and causes

The following are the possible symptoms of a start-up failure:

•

LEDs not lit on any unit.

• Earth fault protection trips.

•

Unable to load the system software.

• FlexPendant not responding.

•

FlexPendant starts, but does not respond to any input.

• Disk containing the system software does not start correctly.

Recommended actions

The following are the recommended actions to be taken during a start-up failure:

NOTE!

This may be due to a loss of power supply in many stages.


1. Make sure the main power supply to the system is present and is within the specified limits.

Your plant or cell documentation can provide this information.

2. Make sure that the main transformer in the Drive module is correctly connected to the mains voltage levels at hand.

How to strap the mains transformer is detailed in the product manual for the controller.

3. Make sure that the main switches are switched on.

4. Make sure that the power supply to the Control module and Drive module are within the specified limits.

If required, trouble shoot the power supply units as explained in section

Trouble shooting power supply on page 56

.

5. If no LEDs lit, proceed to section

All LEDs are

OFF at Controller on page 36

.

6. If the system is not responding, proceed to section

Controller not responding on page 33

.

7. If the FlexPendant is not responding, proceed to section

Problem starting the FlexPendant on page 40

.



31


3.1. Start-up failures

Continued

Action

8. If the FlexPendant starts, but does not communicate with the controller, proceed to section

Problem connecting FlexPendant to the controller on page 41

.

Info/illustration



3.2. Controller not responding

3.2. Controller not responding

Description

This section describes the possible faults and the recommended actions for each failure:

• Robot controller not responding

•

LED indicators not lit

Consequences

System cannot be operated using the FlexPendant.

Possible causes

Symptoms Recommended action

1 Controller not connected to the mains power supply.

2 Main transformer is malfunctioning or not connected correctly.

3 Main fuse (Q1) might have tripped.

Ensure that the mains power supply is working and the voltage level matches that of the controller requirement.

Ensure that the main transformer is connected correctly to the mains voltage level.

Ensure that the mains fuse (Q1) inside the Drive

Module is not tripped

4 Connection missing between the

Control and Drive modules.

If the Drive Module does not start although the

Control Module is working and the Drive Module main switch has been switched on, ensure that all the connections between the Drive module and the

Control module are connected correctly.



3.3. Low Controller performance

3.3. Low Controller performance

Description

The controller performance is low, and seems to work irrationally.

The controller is not completely“ dead”. If it is, proceed as detailed in section

Controller not responding on page 33

.

Consequences

These symptoms can be observed:

• Program execution is sluggish, seemingly irrational and sometimes stalls.

Possible causes

The computer system is experiencing too high load, which may be due to one, or a combination, of the following:

•

Programs containing too high a degree of logical instructions only, causing too fast program loops and in turn, overloads the processor.

• The I/O update interval is set to a low value, causing frequent updates and a high I/O load.

•

Internal system cross connections and logical functions are used too frequently.

• An external PLC, or other supervisory computer, is addressing the system too frequently, overloading the system.



1. Check whether the program contains logical instructions (or other instructions that take “no time” to execute), since such programs may cause the execution to loop if no conditions are fulfilled.

To avoid such loops, you can test by adding one or more WAIT instructions. Use only short

WAIT times, to avoid slowing the program down unnecessarily.

Suitable places to add WAIT instructions can be:

• In the main routine, preferably close to the end.

• In a WHILE/FOR/GOTO loop, preferably at the end, close to the

ENDWHILE/ENDFOR etc. part of the instruction.

2. Make sure the I/O update interval value for each I/O board is not too low. These values are changed using RobotStudio.

I/O units that are not read regularly may be switched to “change of state” operation as detailed in the RobotStudio manual.

ABB recommends these poll rates:

• DSQC 327A: 1000

• DSQC 328A: 1000

• DSQC 332A: 1000

• DSQC 377A: 20-40

• All others: >100

3. Check whether there is a large amount of cross connections or I/O communication between

PLC and robot system.

Heavy communication with PLCs or other external computers can cause heavy load in the robot system main computer.



3.3. Low Controller performance

Action

4. Try to program the PLC in such a way that it uses event driven instructions, instead of looped instructions.


The robot system have a number of fixed system inputs and outputs that may be used for this purpose.

Heavy communication with PLCs or other external computers can cause heavy load in the robot system main computer.



3.4. All LEDs are OFF at Controller

3.4. All LEDs are OFF at Controller

Description

No LEDs at all are lit on the Control Module or the Drive Module respectively.

Consequences

The system cannot be operated or started at all.

Possible causes

The symptom can be caused by (the causes are listed in order of probability):

•

The system is not supplied with power.

• The main transformer is not connected for the correct mains voltage.

•

Circuit breaker F6 (if used) is malfunctioning or open for any other reason.

• Contactor K41 is malfunctioning or open for any other reason.

en1000000051

36




3.4. All LEDs are OFF at Controller

Continued


Action Info

1. Make sure the main switch has been switched on.

2. Make sure the system is supplied with power.

3. Check the main transformer connection.

Use a voltmeter to measure incoming mains voltage.

The voltages are marked on the terminals.

Make sure they match the shop supply voltage.

4. Make sure circuit breaker F6 (if used) is closed in position 3.

The circuit breaker F6 is shown in the circuit diagram in the product manual for the controller.

5. Make sure contactor K41 opens and closes when ordered.

6.

Measure between pins X1.1 and X1.5.

-

Disconnect connector X1 from the Drive

Module power supply and measure the incoming voltage.

7. If the power supply incoming voltage is correct (230 VAC) but the LEDs still do not work, replace the Drive Module power supply.

Replace the power supply as detailed in the product manual for the controller.



3.5. No voltage in service outlet

3.5. No voltage in service outlet

Description

Some Control Modules are equipped with service voltage outlet sockets, and this information applies to these modules only.

No voltage is available in the Control Module service outlet for powering external service equipment.

Consequences

Equipment connected to the Control Module service outlet does not work.

Probable causes


• Tripped circuit breaker (F5)

•

Tripped earth fault protection (F4)

• Mains power supply loss

•

Transformers incorrectly connected xx0500001403

38




3.5. No voltage in service outlet

Continued


Action Info

1. Make sure the circuit breaker in the

Control Module has not been tripped.

Make sure any equipment connected to the service outlet does not consume too much power, causing the circuit breaker to trip.

2. Make sure the earth fault protection has not been tripped.

Make sure any equipment connected to the service outlet does not conduct current to ground, causing the earth fault protection to trip.

3. Make sure the power supply to the robot system is within specifications.

Refer to the plant documentation for voltage values.

4. Make sure the transformer (A) supplying the outlet is correctly connected, i.e. input and output voltages in accordance with specifications.

xx0500002028

Refer to the plant documentation for voltage values.



3.6. Problem starting the FlexPendant

3.6. Problem starting the FlexPendant

Description

The FlexPendant is completely or intermittently "dead".

No entries are possible, and no functions are available.

If the FlexPendant starts but does not display a screen image, proceed as detailed in section


.

Consequences

The system cannot be operated using the FlexPendant.

Possible causes


•

The system has not been switched on.

• The FlexPendant is not connected to the controller.

•

The cable from the controller is damaged.

• The cable connector is damaged.

•

FlexPendant power supply from controller is faulty.


The following actions are recommended (listed in order of probability):

Action Info

1. Make sure the system is switched on and that the FlexPendant is connected to the controller.

How to connect the FlexPendant to the controller is detailed in Operating manual

- Getting started, IRC5 and RobotStudio.

2. Inspect the FlexPendant cable for any visible damage.

If faulty, replace the FlexPendant.

3. If possible, test by connecting a different

FlexPendant to eliminate the FlexPendant and cable as error sources.

4. If possible, test the FlexPendant with a different controller to eliminate the controller as error source.

40




3.7. Problem connecting FlexPendant to the controller

Continued

3.7. Problem connecting FlexPendant to the controller

Description

The FlexPendant starts but does not display a screen image.

No entries are possible, and no functions are available.

The FlexPendant is not completely dead. If it is dead, proceed as detailed in section


.

Consequences

The system cannot be operated using the FlexPendant.

Possible causes


•

The Ethernet network has problems.

• The main computer has problems.



Action Info

1. Check all cables from power supply unit to main computer, making sure these are correctly connected.

2. Make sure the FlexPendant has been correctly connected to the controller.

3. Check all indication LEDs on all units in the controller.

All indication LEDs and their significance are specified in section


.

4. Check all status signals on the main computer.



3.8. Erratic event messages on FlexPendant

3.8. Erratic event messages on FlexPendant

Description

The event messages displayed on the FlexPendant are erratic and do not seem to correspond to any actual malfunctions on the robot. Several types of messages can be displayed, seemingly erroneously.

This type of fault may occur after major manipulator disassembly or overhaul, if not performed correctly.

Consequences

Major operational disturbances due to the constantly appearing messages.

Possible causes


• Internal manipulator cabling not correctly performed. Causes may be: faulty connection of connectors, cable loops too tight causing the cabling to get strained during manipulator movements, cable insulation chafed or damaged by rubbing shortcircuiting signals to earth.



Action Info

1. Inspect all internal manipulator cabling, especially all cabling disconnected, connected re-routed or bundled during recent repair work.

Refit any cabling as detailed in the product manual for the robot.

2. Inspect all cable connectors to make sure these are correctly connected and tightened.

3. Inspect all cable insulation for damage.

Replace any faulty cabling as detailed in the product manual for the robot.



3.9. Problem jogging the robot

3.9. Problem jogging the robot

Description

The system can be started but the joystick on the FlexPendant does not work.

Consequences

The robot can not be jogged manually.

Possible causes


•

The joystick is malfunctioning.

• The joystick may be deflected.



Action

1. Make sure the controller is in manual mode.

Info

How to change operating mode is described in Operating manual - IRC5

with FlexPendant.

2. Make sure the FlexPendant is connected correctly to the Control Module.

3. Reset the FlexPendant.

Press Reset button located on the back of the FlexPendant.

NOTE!

The Reset button resets the

FlexPendant not the system on the

Controller.



3.10. Reflashing firmware failure

3.10. Reflashing firmware failure

Description

When reflashing firmware, the automatic process can fail.

Consequences

The automatic reflashing process is interrupted and the system stops.

Possible causes

This fault usually occurs due to a lack of compatibility between hardware and software.

Consequences


Action Info

1. Check the event log for a message specifying which unit failed.

The logs may also be accessed from

RobotStudio.

2. Was the relevant unit recently replaced?

If YES; make sure the versions of the old and new unit is identical.

If NO; check the software versions.

3. Was the RobotWare recently replaced?

If YES; make sure the versions of the old and new unit is identical.

If NO; proceed below!

4. Check with your local ABB representative for a firmware version compatible with your hardware/software combination.



3.11. Inconsistent path accuracy

3.11. Inconsistent path accuracy

Description

The path of the robot TCP is not consistent. It varies from time to time, and is sometimes accompanied by noise emerging from bearings, gearboxes, or other locations.

Consequences

Production is not possible.

Possible causes


•

Robot not calibrated correctly.

• Robot TCP not correctly defined.

•

Parallel bar damaged (applies to robots fitted with parallel bars only).

• Mechanical joint between motor and gearbox damaged. This often causes noise to be emitted from the faulty motor.

•

Bearings damaged or worn (especially if the path inconsistency is coupled with clicking or grinding noises from one or more bearings).

• The wrong robot type may be connected to the controller.

•

The brakes may not be releasing correctly.


In order to remedy the symptom, the following actions are recommended (the actions are listed in order of probability):

Action Info/Illustration

1. Make sure the robot tool and work object are correctly defined.

How to define these are detailed in

Operating manual - IRC5 with FlexPendant.

2. Check the revolution counters’ positions. Update if required.

3. If required, recalibrate the robot axes.

How to calibrate the robot is detailed in

Operating manual - IRC5 with FlexPendant.

4. Locate the faulty bearing by tracking the noise.

Replace faulty bearing as specified in the product manual for the robot.

5. Locate the faulty motor by tracking the noise.

Study the path of the robot TCP to establish which axis, and thus which motor, may be faulty.

Replace the faulty motor/gearbox as specified in the product manual for the robot.

6. Check the trueness of the parallel bar

(applies to robots fitted with parallel bars only).

Replace the faulty parallel bar as specified in the product manual for the robot.

7. Make sure the correct robot type is connected as specified in the configuration files.

8. Make sure the robot brakes work properly.

Proceed as detailed in section

Problem releasing Robot brakes on page 50

.



3.12. Oil and grease stains on motors and gearboxes

3.12. Oil and grease stains on motors and gearboxes

Description

The area surrounding the motor or gearbox shows signs of oil leaks. This can be at the base, closest to the mating surface, or at the furthest end of the motor at the resolver.

Consequences

Besides the dirty appearance, in some cases there are no serious consequences if the leaked amount of oil is very small. However, in some cases the leaking oil lubricates the motor brake, causing the manipulator to collapse at power down.

Possible causes


•

Leaking seal between gearbox and motor.

• Gearbox overfilled with oil.

•

Gearbox oil too hot.



Info

1.

Action

CAUTION!

Before approaching the potentially hot robot component, observe the safety information in

section

CAUTION - Hot parts may cause burns! on page 21

.

2. Inspect all seals and gaskets between motor and gearbox. The different manipulator models use different types of seals.

3. Check the gearbox oil level.

Replace seals and gaskets as specified in the product manual for the robot.

Correct oil level is specified in the product manual for the robot.

4. Too hot gearbox oil may be caused by:

• Oil quality or level used is incorrect.

• The robot work cycle runs a specific axis too hard. Investigate whether it is possible to program small "cooling periods" into the application.

• Overpressure created inside gearbox.

Check the recommended oil level and type as specified in the product manual for the robot.

Manipulators performing certain, extremely heavy duty work cycles may be fitted with vented oil plugs.

These are not fitted to normal duty manipulators, but may be purchased from your local ABB representative.



3.13. Mechanical noise

3.13. Mechanical noise

Description

During operation, no mechanical noise should be emitted from motors, gearboxes, bearings, or similar. A faulty bearing often emits scraping, grinding, or clicking noises shortly before failing.

Consequences

Failing bearings cause the path accuracy to become inconsistent, and in severe cases, the joint can seize completely.

Possible causes


•

Worn bearings.

• Contaminations have entered the bearing races.

•

Loss of lubrication in bearings.

If the noise is emitted from a gearbox, the following can also apply:

•

Overheating.



Info

1.

Action

CAUTION!

Before approaching the potentially hot robot component, observe the safety information

in section

CAUTION - Hot parts may cause burns! on page 21

.

2. Determine which bearing is emitting the noise.

3. Make sure the bearing has sufficient lubrication.

As specified in the product manual for the robot.

4. If possible, disassemble the joint and measure the clearance.

As specified in the product manual for the robot.

5. Bearings inside motors are not to be replaced individually, but the complete motor is replaced.

Replace faulty motors as specified in the product manual for the robot.

6. Make sure the bearings are fitted correctly.

Also see the product manual for the robot for general instruction on how to handle bearings.



3.13. Mechanical noise

Action Info

7. Too hot gearbox oil may be caused by:

• Oil quality or level used is incorrect.

• The robot work cycle runs a specific axis too hard. Investigate whether it is possible to program small "cooling periods" into the application.

• Overpressure created inside gearbox.

Check the recommended oil level and type as specified in the product manual for the robot.

Manipulators performing certain, extremely heavy duty work cycles may be fitted with vented oil plugs. These are not fitted to normal duty manipulators, but may be purchased from your local

ABB representative.



3.14. Manipulator crashes on power down

3.14. Manipulator crashes on power down

Description

The manipulator is able to work correctly while Motors ON is active, but when Motors OFF is active, it collapses under its own weight.

The holding brake, integral to each motor, is not able to hold the weight of the manipulator arm.

Consequences

The fault can cause severe injuries or death to personnel working in the area or severe damage to the manipulator and/or surrounding equipment.

Possible causes


• Faulty brake.

•

Faulty power supply to the brake.



Action Info

1. Determine which motor(s) causes the robot to collapse.

2. Check the brake power supply to the collapsing motor during the Motors OFF state.

Also see the circuit diagrams in the product manuals for the robot and the controller .

3. Remove the resolver of the motor to see if there are any signs of oil leaks.

If found faulty, the motor must be replaced as a complete unit as detailed in the product manual for the robot.

4. Remove the motor from the gearbox to inspect it from the drive side.

If found faulty, the motor must be replaced as a complete unit as detailed in the product manual for the robot.



49


3.15. Problem releasing Robot brakes

Continued

3.15. Problem releasing Robot brakes

Description

When starting robot operation or jogging the robot, the internal robot brakes must release in order to allow movements.

Consequences

If the brakes do not release, no robot movement is possible, and a number of error log messages can occur.

Possible causes


•

Brake contactor (K44) does not work correctly.

• The system does not go to status Motors ON correctly.

•

Faulty brake on the robot axis.

• Supply voltage 24V BRAKE missing.

50 en1000000051



3.15. Problem releasing Robot brakes


This section details how to proceed when the robot brakes do not release.

Action Info

1. Make sure the brake contactor is activated. A ‘tick’ should be audible, or you may measure the resistance across the auxiliary contacts on top of the contactor.

2. Make sure the RUN contactors (K42 and K43) are activated. NOTE that both contactors must be activated, not just one!

A ‘tick’ should be audible, or you may measure the resistance across the auxiliary contacts on top of the contactor.

3. Use the push buttons on the robot to test the brakes.

If just one of the brakes malfunctions, the brake at hand is probably faulty and must be replaced.

If none of the brakes work, there is probably no

24V BRAKE power available.

The location of the push buttons differ, depending on robot model.

Please refer to the product manual for the robot!

4. Check the Drive Module power supply to make sure 24V BRAKE voltage is OK.

5. A number of other faults within the system can cause the brakes to remain activated. In such cases, event log messages will provide additional information.

The event log messages can also be accessed using RobotStudio.



3.16. Intermittent errors

3.16. Intermittent errors

Description

During operation, errors and malfunctions may occur, in a seemingly random way.

Consequences

Operation is interrupted, and occasionally, event log messages are displayed, that sometimes do not seem to be related to any actual system malfunction. This sort of problem sometimes affects the Emergency stop or Enable chains respectively, and may at times be very hard to pinpoint.

Probable causes

Such errors may occur anywhere in the robot system and may be due to:

•

external interference

• internal interference

•

loose connections or dry joints, e.g. incorrectly connected cable screen connections.

• thermal phenomena , e.g. major temperature changes within the workshop area.




1. Check all the cabling, especially the cables in the

Emergency stop and Enable chains. Make sure all connectors are connected securely.

2. Check if any indication LEDs signal any malfunction that may give some clue to the problem.

3. Check the messages in the event log. Sometimes specific error combinations are intermittent.

The significance of all indication LEDs are specified in

section


.

The event log messages may be viewed either on the

FlexPendant or using Robot-

Studio.

4. Check the robot’s behaviour, etc, each time that type of error occurs.

If possible, keep track of the malfunctions in a log or similar.

5. Check whether any condition in the robot working environment also changes periodically, e.g, interference from any electric equipment only operating periodically.

6. Investigate whether the environmental conditions

(such as ambient temperature, humidity, etc) has any bearing on the malfunction.

If possible, keep track of the malfunctions in a log or similar.

52



4 Trouble shooting by Unit

4.1. Trouble shooting the FlexPendant

Continued


4.1. Trouble shooting the FlexPendant

General

The FlexPendant communicates, through the Panel Board, with the Control Module main computer. The FlexPendant is physically connected to the Panel Board through a cable in which the +24 V supply and two Enabling Device chains run and emergency stop.

Procedure

The procedure below details what to do if the FlexPendant does not work correctly.

Action

1. If the FlexPendant is completely “dead”, proceed as detailed in section


.

2. If the FlexPendant starts, but does not operate correctly, proceed as detailed in section


.

3. If the FlexPendant starts, seems to operate, but displays erratic event messages, proceed as detailed in section

Erratic event messages on

FlexPendant on page 42

.

4. Check the cable for connections and integrity.

5. Check the 24 V power supply.

6. Read the error event log message and follow any instructions of references.




4.2. Trouble shooting communications

4.2. Trouble shooting communications

Overview

This section details how to trouble shoot data communication in the Control and Drive

Modules.

Trouble shooting procedure

When trouble shooting communication faults, follow the outline detailed below:

Action

1. Faulty cables (e.g. send and receive signals are mixed up).

2. Transfer rates (baud rates).

3. Data widths that are incorrectly set.

Info/illustrations



4.3. Trouble shooting fieldbuses and I/O units

4.3. Trouble shooting fieldbuses and I/O units

Where to find information

Information about how to trouble shoot the fieldbuses and I/O units can be found in the manual for the respective fieldbus or I/O unit.



4.4.1. Trouble shooting DSQC 604

4.4 Trouble shooting power supply

4.4.1. Trouble shooting DSQC 604

Required test equipment

Equipment needed for trouble shooting:

• Ohmmeter

•

Resistive load (e.g. Main Computer DSQC 639 on +24V_PC)

• Voltmeter

Preparations

Action

1. Check the FlexPendant for errors and warnings.

Note

Trouble shooting procedure, DSQC 604

The trouble shooting table is supposed to be used as a detailed instruction together with the

trouble shooting flowchart, see

Trouble shooting flowchart, DSQC 604 on page 58

.

Test Note Action

1. Check the indicator

LED on DSQC 604.

2. Check connections between DC outputs and connected units.

The indicator LED is labelled DCOK.

If the LED is GREEN, the power supply should be working properly.

If the LED is PULSING GREEN, the

DC outputs are probably not connected to any units or there may be a short circuit on an output.

Proceed with step 2.

If the LED is OFF, either the power supply is faulty or it does not have sufficient input voltage. Proceed with step 4.

Make sure that the power supply is connected to its proper units.

A minimum load of 0.5-1A is required on at least one

DC output for the 604 to work properly.

If the connections are OK, proceed with step 3.

If the connections are faulty or the power supply is not connected to any units at all, repair connections/ connect units. Verify that the fault has been fixed and restart this guide if necessary.

3. Check for short circuits on DC outputs.

Check both the DC outputs on DSQC 604 and the inputs on surrounding units.

Measure the resistance between voltage pins and ground. The resistance should NOT be zero.

The DC outputs are shown in the Circuit

Diagram in Product

manual - IRC5.

If no short circuit is found, proceed with step 4.

If a short circuit is found on DSQC

604, proceed with step 10.

If a short circuit is found on any surrounding unit, get that unit working. Verify that the fault has been fixed and restart this guide if necessary.





4. Disconnect one DC output at a time and measure its voltage.

5. Measure the input voltage to the 604.

Measure the voltage using a voltmeter. Voltage should be: 172 < U <

276V.

The AC input is shown in the Circuit Diagram in


If the input voltage is correct, proceed with step 10.

If no or the wrong input voltage is detected, proceed with step 6.

6. Check switches Q1-

2.

7. Check main fuse F2 and optional fuse F6 if used.

8. Make sure that the input voltage to the cabinet is the correct one for that particular cabinet.

Make sure that they are closed.

Their physical location is shown in the Circuit


manual - IRC5.

If the switches are closed, proceed with step 7.

If the switches are open, close them.

Verify that the fault has been fixed and restart this guide if necessary.

Make sure that they are open.

Their physical location is shown in the Circuit


manual - IRC5.

If the fuses are open, proceed with step 8.

If the fuses are closed, open them.

Verify that the fault has been fixed and restart this guide if necessary.


If the input voltage is incorrect, adjust it. Verify that the fault has been fixed and restart this guide if necessary.

9. Check the cabling.

Make sure that at least one unit is connected at all times. A minimum load of 0.5- 1A is required on at least one output for the

604 to work properly.

Measure the voltage using a voltmeter. The voltage should be: +24V

< U < +27V.

The DC outputs are shown in the Circuit


manual - IRC5.

If the correct voltage is detected on all outputs and the DCOK LED is green, the power supply is working properly.

If the correct voltage is detected on all outputs and the DCOK LED is off, the power supply is regarded as faulty but does not have to be replaced instantly.

If no or the wrong voltage is detected, proceed with step 5.

Make sure that the cabling is correctly connected and not faulty.

If the cabling is OK, the problem is likely to be the transformer T1 or the input filter. Try to get this part of the supply working. Verify that the fault has been fixed and restart this guide if necessary.

If the cabling is found unconnected or faulty, connect/replace it. Verify that the fault has been fixed and restart this guide if necessary.




Trouble shooting flowchart, DSQC 604

1 . D C O K L E D

D S Q C 6 0 4

P U L S I N G

G R E E N

O F F

F i x c o n n e c t i o n s

C o n n e c t i o n s n o t o k 2 . C h e c k o u t p u t c o n n e c t i o n s

G R E E N

4 . M e a s u r e D C o u t p u t s

C o r r e c t

D C l e v e l

F i x s h o r t c i r c u i t

S h o r t c i r c u i t o n u n i t ( s ) 3 . C h e c k f o r s h o r t c i r c u i t s o n o u t p u t s

S h o r t c i r c u i t o n o u t p u t ( s )

7 . C h e c k f u s e s

F 2 ( F 6 )

S w i t c h e s c l o s e d

6 . C h e c k s w i t c h e s Q 1 - 2

W r o n g

A C l e v e l

5 . M e a s u r e A C i n p u t

C o r r e c t

A C l e v e l

58

O p e n f u s e s

8 . M e a s u r e A C t o c a b i n e t

C l o s e s w i t c h e s

Q 1 - 2

9 . C h e c k c a b l i n g

A d j u s t A C i n p u t

F i x c a b l i n g P r o b a b l e c a u s e o f d y s f u n c t i o n : t r a n s f o r m e r T 1 o r f i l t e r en0800000354

1 0 . R e p l a c e D S Q C 6 0 4

T h e p o w e r s u p p l y u n i t w o r k s p r o p e r l y







• Ohmmeter

•


• Voltmeter

Preparations

Action


2. Make sure that the control system power supply is in run-time mode.

Do this by waiting 30 seconds after power-on.


The trouble shooting table is supposed to be used as a detailed instruction together with the trouble shooting flowchart, see


.

Test


LED on DSQC 661.

2. Check connection between DC output and connected unit.

3. Check for short circuit on DC output.

Note Action

The indicator LED is labelled

DCOK.

If the LED is GREEN, the 661 should be working properly.

If the LED is PULSING GREEN, the DC output is probably not connected to any unit (load) or there may be a short circuit on the output. Proceed with step 2.

If the LED is OFF, either the 661 is faulty or it does not have sufficient input voltage. Proceed with step

4.

Make sure that the power supply is connected to

DSQC 662.

A minimum load of 0.5-1A is required on the DC output for the 661 to work properly.

If the connection is OK, proceed with step 3.

If the connection is faulty or the power supply is not connected to

DSQC 662, repair connection/ connect it. Verify that the fault has been fixed and restart this guide if necessary.

Check both the DC output on

DSQC 661 and the input on

DSQC 662.

Measure the resistance between voltage pins and ground. The resistance should NOT be zero.

The DC output is shown in the Circuit Diagram in


If no short circuit is found, proceed with step 4.


661, proceed with step 10.


662, get that unit working. Verify that the fault has been fixed and restart this guide if necessary.



59



Continued


4. Measure the DC voltage while the output is connected to DSQC 662 or some other load.

5. Measure the input voltage to the 661.

6. Check switches Q1-

2.

DSQC 661 requires a minimum load of 0.5- 1A in order for it to deliver +24V.

Measure the voltage using a voltmeter. The voltage should be: +24V < U < +27V.

The DC output is shown in the Circuit Diagram in


If the correct voltage is detected and the DCOK LED is green, the power supply is working properly.

If the correct voltage is detected and the DCOK LED is off, the power supply is regarded as faulty but does not have to be replaced instantly.


Measure the voltage using a voltmeter. Voltage should be: 172 < U < 276V.

The AC input is shown in the

Circuit Diagram in Product

manual - IRC5.


If no or the wrong input voltage is detected, proceed with step 6.

Make sure that they are closed.

Their physical location is shown in the Circuit Diagram in Product manual - IRC5.

If the switches are closed, proceed with step 7.

If the switches are open, close them. Verify that the fault has been fixed and restart this guide if necessary.

7. Check main fuse F2 and optional fuse F6 if used.

Make sure that they are open.

Their physical location is shown in the Circuit Diagram in Product manual - IRC5.

If the fuses are open, proceed with step 8.

If the fuses are closed, open them. Verify that the fault has been fixed and restart this guide if necessary.

8. Make sure that the input voltage to the cabinet is the correct one for that particular cabinet.


If the input voltage is incorrect, adjust it. Verify that the fault has been fixed and restart this guide if necessary.

9. Check the cabling.

10. The 661 may be faulty, replace it and verify that the fault has been fixed.

Make sure that the cabling is correctly connected and not faulty.

If the cabling is OK, the problem is likely to be the transformer T1 or the input filter. Try to get this part of the supply working. Verify that the fault has been fixed and restart this guide if necessary.

If the cabling is found unconnected or faulty, connect/ replace it. Verify that the fault has been fixed and restart this guide if necessary.

How to replace the unit is detailed in Product manual -

IRC5.

60




1 . D C O K L E D

D S Q C 6 6 1

P U L S I N G

G R E E N

O F F

F i x c o n n e c t i o n

C o n n e c t i o n s n o t o k 2 . C h e c k o u t p u t c o n n e c t i o n



Continued

G R E E N

4 . M e a s u r e D C o u t p u t

C o r r e c t

D C l e v e l

F i x s h o r t c i r c u i t

S h o r t c i r c u i t o n u n i t ( s )

3 . C h e c k f o r s h o r t c i r c u i t o n o u t p u t

S h o r t c i r c u i t o n o u t p u t ( s )

7 . C h e c k f u s e s

F 2 ( F 6 )

S w i t c h e s c l o s e d 6 . C h e c k s w i t c h e s Q 1 - 2

W r o n g

A C l e v e l 5 . M e a s u r e A C i n p u t

C o r r e c t

A C l e v e l

O p e n f u s e s

8 . M e a s u r e A C t o c a b i n e t

C l o s e s w i t c h e s

Q 1 - 2

9 . C h e c k c a b l i n g

A d j u s t A C i n p u t

1 0 . R e p l a c e D S Q C 6 6 1


F i x c a b l i n g P r o b a b l e c a u s e o f d y s f u n c t i o n : t r a n s f o r m e r T 1 o r f i l t e r en0800000355







• Ohmmeter

•


• Voltmeter

Preparations

Action


2. Make sure that the power distribution board is in run-time mode.

Do this by waiting 1 minute after power-on.

Note

When the AC power has been cut off, the indicator LED (Status

LED) on DSQC 662 will turn red and stay red until UltraCAP is empty. This may take a long time and is completely normal. It does not mean that there is something wrong with the 662.


The trouble shooting table is supposed to be used as a detailed instruction together with the

trouble shooting flowchart, see


.

Test


LED on DSQC 662.

Note Action

The indicator LED is labelled

Status LED.

If the LED is GREEN, the 662 should be working properly.

If the LED is PULSING GREEN, a

USB communication error has occurred. Proceed with step 2.

If the LED is RED, the input/output voltage is low, and/or the logic signal ACOK_N is high. Proceed with step 4.

If the LED is PULSING RED, one or more DC outputs are under specified voltage level. Make sure cables are properly connected to its respective units. Proceed with step 4.

If the LED is PULSING

REDGREEN, a firmware upgrade error has occurred. This is not supposed to happen during runtime mode, proceed with step

6.

If the LED is OFF, either the 662 is faulty or it does not have sufficient input voltage. Proceed with step

4.

62





Continued


2. Check USB connection on both ends.

3. Try to fix the communication between the power supply and the computer by reconnecting the cable.

Make sure that the USB cable is properly connected on both ends.

If the connection seems OK, proceed with step 6.

If there is a problem with the connection, proceed with step 3.

If the communication comes back up, verify that the fault has been fixed and restart this guide if necessary.

If unable to fix the communication, proceed with step 6.

4. Disconnect one DC output at a time and measure its voltage.

Make sure that at least one unit is connected at all times.

A minimum load of 0.5- 1A is required on at least one output for the 662 to work properly.

If the correct voltage is detected on all outputs and the Status LED is green, the power supply is working properly.

Measure the voltage using a voltmeter. The voltage should be: +24V < U < +27V.

The DC outputs are shown in the Circuit Diagram in


If the correct voltage is detected on all outputs and the Status LED is NOT green, the power supply is regarded as faulty but does not have to be replaced instantly.


5. Measure the input voltage to the 662 and the ACOK_N signal.

6. The 662 may be faulty, replace it and verify that the fault has been fixed.

Measure the voltage using a voltmeter. Input voltage should be: 24 < U < 27V and

ACOK_N should be 0V.


If no or the wrong input voltage is detected, troubleshoot DSQC

661.

Make sure that connectors

X1 and X2 are connected properly on both ends.

The DC input X1 and

ACOK_N connector X2 are shown in the Circuit Diagram in Product manual - IRC5.

How to replace the unit is detailed in Product manual -

IRC5.



63



Continued


D S Q C 6 6 2

1 . D C O K L E D

P U L S I N G

G R E E N

P U L S I N G

R E D - G R E E N

O F F P U L S I N G

R E D

R E D G R E E N

2 . C h e c k U S B c o n n e c t i o n

4 . M e a s u r e D C o u t p u t s

C o r r e c t

D C l e v e l

3 . F i x c o n n e c t i o n

5 . M e a s u r e

2 4 V _ D C i n p u t a n d A C O K

2 4 V n o t o k

64 en0800000356

6 . R e p l a c e D S Q C 6 6 2

T r o u b l e s h o o t

D S Q C 6 6 1



5 Descriptions and background information

5.1.1. LEDs in the Control Module


5.1 Indications

5.1.1. LEDs in the Control Module

General

The Control Module features a number of indication LEDs, which provide important information for trouble shooting purposes. If no LEDs light up at all when switching the system on, trouble shoot as detailed in section

All LEDs are OFF at Controller on page 36

All LEDs on the respective units, and their significance, are described in the following sections.

All units with LEDs are shown in the illustration below:

LEDs

Single cabinet controller

C

B

A

E

D en1000000039

A

B

C

D

E

Ethernet board (any of the four board slots)

Computer unit (DSQC 639)

Customer I/O power supply (up to three units)

Control module power supply

LED board



65



Continued

Control module for Dual cabinet controller en1000000035

D

E

B

C

F

Ethernet board (any of the four board slots)

Computer unit (DSQC 639)

Customer I/O power supply (up to three units)

Control module power supply

LED board

66





Continued

Ethernet board

The illustration below shows the LEDs on the Ethernet board: en0400000919

A

B

C

AXC2 connector LED

AXC3 connector LED

AXC4 connector LED

Description Significance

AXC2 connector

LED

AXC3 connector

LED

AXC4 connector

LED

Shows the status of Ethernet communication between Axis Computer 2 and the Ethernet board.

GREEN OFF:10 Mbps data rate has been selected.

GREEN ON:100 Mbps data rate has been selected.

YELLOW flashing: The two units are communicating on the Ethernet channel.

YELLOW steady: A LAN link is established.

YELLOW OFF: A LAN link is not established.

Shows the status of Ethernet communication between Axis Computer 3 and the Ethernet board

See the description above!

Shows the status of Ethernet communication between Axis Computer 4 and the Ethernet board

See the description above!




Control module Power supply

The illustration below shows the LEDs on the Control module power supply:

DSQC

A xx0400001073

DSQC 661 en1000000041

DSQC 662

A en1000000042

A DCOK indicator


DCOK indicator GREEN: When all DC outputs are above the specified minimum levels.

OFF: When one or more DC output/s below the specified minimum level.




Control module Power distribution board


DCOK indicator GREEN: When DC output is above the specified minimum level.

OFF: When the DC output below the specified minimum level.

Customer Power Supply

The illustration below shows the LEDs on the Customer Power Supply Module:

A en1000000037

A DCOK indicator


DCOK indicator GREEN: When all DC outputs are above the specified minimum levels.


Computer unit

The illustration below shows the LEDs on the Computer unit: en1000000040

Description

Status LED

Significance

Shows the status of the communication on the computer unit



69



Continued

Panel board

The illustration below shows the LEDs on the Panel board:

A

LED board

dummy

A Panel board LEDs

The panel board LEDs are described from top to bottom below:


Status LED GREEN flashing: serial communication error.

GREEN steady: no errors found and system is running.

RED flashing: system is in power up/selftest mode.

RED steady: other error than serial communication error.

Indication LED, ES1 YELLOW when Emergency stop chain 1 closed

Indication LED, ES2 YELLOW when Emergency stop chain 2 closed

Indication LED, GS1 YELLOW when General stop switch chain 1 closed

Indication LED, GS2 YELLOW when General stop switch chain 2 closed

Indication LED, AS1 YELLOW when Auto stop switch chain 1 closed

Indication LED, AS2 YELLOW when Auto stop switch chain 2 closed

Indication LED, SS1 YELLOW when Superior stop switch chain 1 closed

Indication LED, SS2 YELLOW when Superior stop switch chain 2 closed

Indication LED, EN1 YELLOW when ENABLE1=1 and RS-communication is OK

The function of the LEDs on the LED board are identical to those on the Panel board as described above.

Should the LED board not be working, but the Panel board is, the problem is the communication between these boards or the LED board itself. Check the cabling between them.

70




5.1.2. LEDs in the Drive Module for Drive System 04

Continued

5.1.2. LEDs in the Drive Module for Drive System 04

General

The Drive Module features a number of indication LEDs, which provide important information for trouble shooting purposes. If no LEDs light up at all when switching the system on, trouble shoot as detailed in section


.



LEDs

xx0400001084

D

E

F

A

B

C

Rectifier

Axis Computer

Contactor interface board

Single servo drive

Drive Module Power Supply

Main drive unit



71



Continued

Axis computer

The illustration below shows the LEDs on the Axis computer:

72 xx0300000023

A

B

Status LED

Ethernet LEDs


Status LED

Ethernet LED

Normal sequence during startup:

1. RED steady: Default at power-up.

2. GREEN flashing: Establish connection to main computer, retrieve

IP address and download the application file.

3. GREEN steady. Start-up sequence ready. Application is running.

The following indicates errors:

• RED steady (forever): The axis computer has failed to initialize basic hardware.

• RED (long) -> GREEN flashing (short) -> RED (long) -> GREEN flashing (short) -> ... : Missing connection to main computer.

Possible cable problem.

• RED (short) -> GREEN flashing (long) -> RED (short) -> GREEN flashing (long) -> ... : Connection established with main computer.

Possible RobotWare problem in main computer.

• GREEN flashing (forever): Possible cable or RobotWare problem in main computer.

Shows the status of Ethernet communication between an additional axis computer (2, 3 or 4) and the Ethernet board.

• GREEN OFF:10 Mbps data rate has been selected. This is an error state.

• GREEN ON:100 Mbps data rate has been selected.

• YELLOW flashing: The two units are communicating on the

Ethernet channel.

• YELLOW steady: A LAN link is established.

• YELLOW OFF: A LAN link is not established.





Continued

Main drive unit, single drive unit and rectifier unit

The illustration below shows the indication LEDs on the main drive unit, single drive unit and rectifier unit.

NOTE that there are two types of main drive units: a six unit drive and a three unit drive which are both used to power a six axes robot. Shown in the illustration is a six unit drive. The three unit drive is half the size of the six unit drive, but the indication LED is positioned in the same place.

xx0400001089

C

D

A

B

E

F

Single drive unit

Rectifier unit

Main drive unit

Indication LED, single servo drive

Indication LED, rectifier unit

Indication LED, main drive unit


Indication LEDs

D, E and F

GREEN flashing: Internal function is OK and there is a malfunction in the interface to the unit. The unit does not need to be replaced.

GREEN steady: Program loaded successfully, unit function OK and all interfaces to the units is fully functional.

RED steady: Permanent internal fault detected. The LED is to have this mode in case of failure at internal self test at start-up, or in case of detected internal failure state in running system. The unit probably needs to be replaced.



73



Continued

Drive Module Power Supply

The illustration below shows the LEDs on the Drive Module power supply:

A xx0400001090

A DCOK indicator

Description

DCOK indicator

Significance

GREEN: When all DC outputs are above the specified minimum levels.


Contactor interface board

The illustration below shows the LEDs on the Contractor interface board:

A xx0400001091

A

Description

Status LED

Status LED

GREEN flashing: serial communication error.


RED flashing: system is in power up/selftest mode.





5.1.3. LEDs in the Drive Module for Drive System 09

General

The Drive Module features a number of indication LEDs, which provide important information for trouble shooting purposes. If no LEDs light up at all when switching the system on, trouble shoot as detailed in section


.



Units

xx0800000484

A

B

C

D

E

Main Drive Unit

Additional Drive Units

Axis computer

Drive Module power supply

Contactor interface board



75



Continued

Axis computer

The illustration below shows the LEDs on the Axis computer:

76 xx0800000485

A

B

Status LED

Ethernet LED


Status LED Normal sequence during startup:

1. RED steady: Default at power-up.

2. RED flashing: Establish connection to main computer and load program to axis computer.

3. GREEN flashing: Start-up of axis computer program and connect peripheral units.

4. GREEN steady. Start-up sequence ready. Application is running.

The following indicates errors:

• DARK: No power to axis computer or internal error (hardware/ firmware).

• RED steady (forever): The axis computer has failed to initialize basic hardware.

• RED flashing (forever): Missing connection to main computer, main computer start-up problem or RobotWare installation problem.

• GREEN flashing (forever): Missing connections to peripheral units or RobotWare start-up problem.





Continued


Ethernet LED Shows the status of Ethernet communication between an additional axis computer (2, 3 or 4) and the Ethernet board.

• GREEN OFF:10 Mbps data rate has been selected.



Ethernet channel.



Main Drive Unit and Additional Drive Unit

The illustration below shows the indication LEDs on the Main Drive Unit and Additional

Drive Units.

xx0800000486

A

B

C

D

Main Drive Unit

Main Drive Unit Ethernet LEDs

Additional Drive Unit

Additional Drive Unit Ethernet LEDs



77



Continued


Ethernet LEDs

(B and D)

Shows the status of Ethernet communication between an additional axis computer (2, 3 or 4) and the Ethernet board.

• GREEN OFF:10 Mbps data rate has been selected.



Ethernet channel.



Drive Module Power Supply

The illustration below shows the LEDs on the Drive Module power supply:

A xx0400001090

A DCOK indicator

Description

DCOK indicator

Significance

GREEN: When all DC outputs are above the specified minimum levels.


Contactor interface board

The illustration below shows the LEDs on the Contractor interface board:

78

A xx0400001091

A

Description

Status LED

Status LED

GREEN flashing: serial communication error.


RED flashing: system is in power-up/self-test mode.



6 Trouble shooting by Event log


10002, Program pointer has been reset

Description

The program pointer of task arg has been reset.

Consequences

When started, program execution will start on the first instruction of the task's entry routine. NOTE that the manipulator may move to unexpected position when restarted!

Probable causes

The operator has probably requested this action manually.

Probable causes

Any safety device connected to the system's stop inputs have been opened. These are shown in the Circuit Diagram.


1. Check which safety device caused the stop.

2. Close the device.

3. To resume operation, switch the system back to state Motors ON.

10009, Work memory full

Description

The task arg has no memory left for new RAPID instructions or data.


Save the program and then restart the system.

10010, Motors OFF state

Description

The system is in the Motors OFF state. It enters this state either after switching from Manual mode to Automatic, or after the Motors ON circuit has been opened during program execution.

Consequences

No operation will be possible until after closing the Motors ON circuit.

The manipulator's axes are meanwhile held in position by mechanical holding brakes.

10013, Emergency stop state

Description

The system is in the Emergency stop state, since the Motors ON circuit has been opened by an Emergency Stop device.

Consequences

All program execution and thus robot actions are immediately halted.

The robot axes are meanwhile held in position by mechanical holding brakes.

Probable causes

Any emergency stop device connected to the emergency stop input have been opened. These may be internal (on the controller or on the teach pendant) or external (devices connected by the system builder).

The internal devices are shown in the Circuit Diagram.


1) Check which emergency stop device caused the stop.

2) Close/reset the device.

3) To resume operation, switch the system back to state Motors ON by pressing this button on the Control Module.

10011, Motors ON state

Description

The system is in the Motors ON state.

Consequences

The Motors ON circuit has been closed., enabling power supply to the manipulator's motors. Normal operation may be resumed.

10012, Safety guard stop state

Description

The system is in the Guard stop state. It enters this state either after switching from Automatic mode to Manual, or after the Motors ON circuit has been opened by an Emergency Stop, General Stop,

Automatic Stop or Superior Stop.

Consequences

No operation will be possible until after closing the Motors ON circuit.

The manipulator's axes are meanwhile held in position by mechanical holding brakes.


10014, System failure state

Description

Execution of all NORMAL tasks has been stopped due to malfunction.

Consequences

No start of program execution or manual manipulator jogging will be possible until after the system has been restarted.

Probable causes

A large number of malfunctions may cause this condition. Please use the teach pendant or RobotStudio to check other event log messages for events occurring at this time!


1. Determine what caused the stop by studying the event log.

2. Remedy the fault.

3. Restart the system as detailed in the Operator's Manual.

10015, Manual mode selected

Description

The system is in the Manual mode.


79


Continued

Consequences

Programmed operation is possible, but only with a max. speed of 250 mm/s. The manipulator may also be jogged manually after pressing the enabling device on the teach pendant.


1. Determine what caused the stop by studying the event log.

2. Remedy the fault.

3. If neccesary, move Program Pointer to main before pressing start button.

10016, Automatic mode requested

Description

The system has been ordered to go to the Automatic mode.

Consequences

The system will go to the Automatic mode after confirmed from teach pendant.

10021, Execution error reset

Description

The program execution in task arg has left a spontaneous error state.

10017, Automatic mode confirmed

Description

The system is in the Automatic mode.

Consequences

The enabling device is disconnected. The robot can move without human intervention.

10024, Collision triggered

Description

Some mechanical part of the manipulator has collided with a piece of fixed equipment in the cell.

Consequences

Manipulator movement is interrupted and program execution is stopped.

10018, Manual mode full speed requested

Description

The system has been ordered to go to the Manual mode without any speed restraints.

Consequences

The system will go to the Manual mode full speed.

10025, Collision confirmed

Description

The collision detection has been confirmed.


10019, Manual mode full speed confirmed

Description

The system is in the Manual mode without any speed restraints.

Consequences

Programmed operation is possible while pressing the hold-to-run button on the teach pendant. The manipulator may also be jogged manually after pressing the enabling device on the teach pendant.

10026, Collision retraction

Description

The manipulator has attempted to back away from the obstacle, into which it collided, and succeeded.

Consequences

The system is ready to go back to normal operation.

10020, Execution error state

Description

The program execution in task arg has been stopped due to a spontaneous error.

Consequences

No program execution will be possible until the error has been removed.

Probable causes

A large number of malfunctions may cause this condition. Please use the teach pendant or RobotStudio to check other event log messages for events occurring at this time!

10027, Collision retraction fail

Description

The manipulator has attempted to back away from the obstacle, into which it collided, and failed.

Consequences

The system is NOT ready to go back to normal operation.

Probable causes

This may be caused by the robot being stuck to the object into which it collided.


1) Go to Manual Mode.

2) Manually run the robot away from the object.

3) Resume operation by restarting the program.

80




Continued

10030, All axes commutated

Description

After checking, the system has found all manipulator axes to be commutated.

Consequences

Normal operation is possible.

10031, All axes calibrated

Description

After checking, the system has found all manipulator axes to be calibrated.

Consequences


10035, Axis not calibrated

Description

After checking, the system has found that one or more manipulator axes are not calibrated.

Consequences

To enable operation, all manipulator axes must be calibrated.

Probable causes

The manipulator drive motor and related units may have been altered, e.g. after replacing a faulty unit.


Calibrate the manipulator axes as detailed in the manipulator Product

Manual.

10032, All revolution counters updated

Description

After checking, the system has found all revolution counters for all manipulator axes to be updated.

Consequences


10033, All axes synchronized

Description

After checking, the system has found all manipulator axes to be synchronized.

Consequences


10036, Revolution counter not updated

Description

After checking, the system has found that the revolution counters of one or more manipulator axes are not updated.

Consequences

To enable operation, the revolution counters of all manipulator axes must be updated.

Probable causes



Update the revolution counters of all manipulator axes as detailed in the manipulator Product Manual.

10034, Axis not commutated

Description

After checking, the system has found that one or more manipulator axes are not commutated.

Consequences

To enable operation, all manipulator axes must be commutated.

Probable causes



Commutate the manipulator axes as detailed in the manipulator

Product Manual.

10037, Axis not synchronized

Description

After checking, the system has found that one or more manipulator axes are not synchronized.

Consequences

To enable operation, all manipulator axes must be synchronized.

Probable causes



Synchronize the manipulator axes as detailed in the manipulator

Product Manual.

10038, SMB memory is OK

Description

During startup, the system has found that all data on the Serial

Measurement Board (SMB) is OK.



81


Continued

Consequences

Operation is possible.

10039, SMB memory is not OK

Description

During startup, the system has found that data in the Serial

Measurement Board (SMB) memory is not OK.

Consequences

All data must be OK before automatic operation is possible. Manually jogging the robot is possible.

Probable causes

There are differences between the data stored on the SMB and the data stored in the controller. This may be due to replacement of SMB, controller or both.


1) Update the Serial Measurement Board data as detailed in Operator's

Manual, IRC5.

10044, Program Pointer updated

Description

The task arg could have changed the Program Pointer position.


10045, System restarted

Description

An already installed system was restarted.


10046, System restarted in cold mode

Description

First start after installation.


10040, Program loaded

Description

A program or program module has been loaded into task arg. After loading, arg bytes memory remain. The size of the loaded program is

arg.

10048, Background task did stop

Description

The task arg stopped without reason.


10041, Program deleted

Description

A program or program module was deleted from task arg.

Consequences

If the deleted program contained the task entry routine, the program will no longer be executable.

Probable causes

The program may have been removed manually.


1) Define an entry routine in one of the task's remaining programs, or:

2) Load a program containing an entry routine.

10051, Event routine error

Description

The task arg could not start the specified system event routine arg. The routine is either unknown to the system or the program is unlinkable.


Insert the routine in a system module or correct the program.

10052, Regain start

Description

A regain movement has started.


10042, Axis recalibrated

Description

Fine calibration or rev counter update was made for an axis in an already synchronized mechanical unit.

10053, Regain ready

Description

The regain movement is ready.


10043, Restart failed

Description

The task arg can't restart.

10054, Regain rejected

Description

Regain on path not possible, as one client has already ordered it.




A new regain movement is ordered during an already started regain movement. Reduce the number of start orders from e.g system I/O

10055, Path process restarted

Description

The path process has been restarted.


10060, Test of enable chain

Description

The enable chain is always tested at startup. If the test failed an error message concerning enable will follow.


If enable chain test at startup failed the related error message will be

"Enable chain timeout"

10061, A target has been modified

Description

A target in module arg in task arg has been modified or tuned.

Start line arg, column arg, end line arg.

10062, A module has been edited.

Description

Module arg in task arg has been edited between lines: arg, arg.

10063, Module has been edited

Description

Module arg in task arg has been edited.

10067, Program Pointer Reset

Description

Unable to reset the program pointer for task arg.

Consequences

The program will not start.

Probable causes

- No program is loaded.

- The main routine is missing.

- There are errors in the program.


1. Load program if no program is loaded.

2. Check that the program has a main routine. If there is no main routine, add one.

3. Check for errors in the program and correct them.

4. See previous error messages in the Event log.

10068, Start Program

Description

Unable to start program for task arg.

Consequences

The program will not execute.

10074, NFS server up

Description

The control system communicates correctly with the NFS server arg.

10064, A module has been erased.

Description

Module arg in task arg has been erased.

10065, New user has started to modify RAPID.

Description

User arg has started with RAPID program modifications in task arg.

10066, Not possible to load system module

Description

System module arg in task arg cannot be loaded since the file is not found.

10075, NFS server down

Description

The control system is not able to communicate correctly with the NFS server arg.

Consequences

If the server arg is defined as TRUSTED, robot program execution will be stopped. If the server is defined as NON-TRUSTED, execution will proceed. These definitions are specified in the Application manual -

Robot communication and I/O control.

Probable causes

If this message is displayed at first start-up, the server configuration may be incorrect. If displayed during operation, the previously working communication has been lost due to a broken connection.

Also see the I/O event log!


1. Check the NFS server configuration.

2. Check all communication hardware, cables and such.

3. Check NFS client configuration on the controller.



10076, FTP server up

Description

The control system communicates correctly with the FTP server arg.

10077, FTP server down

Description

The control system is not able to communicate correctly with the FTP server arg.

Consequences

If the server arg is defined as TRUSTED, robot program execution will be stopped. If the server is defined as NON-TRUSTED, execution will proceed. These definitions are specified in the Application manual -

Robot communication and I/O control.

Probable causes

If this message is displayed at first start-up, the server configuration may be incorrect. If displayed during operation, the previously working communication has been lost due to a broken connection.

Also see the I/O event log!


1. Check the FTP server configuration.

2. Check all communication hardware, cables and such.

3. Check the FTP client configuration on the controller.

10083, RAPID Task supervision

Description

Task arg is not running. The system will be set in motors off state. arg


See previous messages for the cause.


Description

Task arg is not running. All NORMAL tasks will also be stopped.


See previous messages for the cause.


Description

Task arg can't be stopped. The trustLevel is set to a safety level.


If the task should be possible to stop change the trustLevel or task type in the system parameters menu.

10080, An updated RAPID file is found

Description

The SEMISTATIC task arg has an older version of a module installed than the source arg


Restart the system with a P-START to install the newer version.

10086, Robot is purged OK

Description

Purging pressure regained after a purge fault.


10087, Purge state: arg.

Description

State changed.

Recommended actions 10081, Background task arg

Description

failed to load a newer version of a module. The source of the module is arg.


See previous messages for the cause or restart the system with a P-

START to load the newer version.


Description

Task arg is not running. The system will be set in SysFail state. It's now impossible to change to motors on arg.


See previous messages for the cause. Restart the system to reset the error state.

10090, P-Start done

Description

A P-Start is done.

Consequences

After restart the system's state will be resumed except for manually loaded programs and modules. Static and semistatic tasks are restarted from the beginning, not from the state they had when the system was stopped.

Modules will be installed and loaded in accordance with the set configuration. System parameters will not be affected.

Probable causes

1. The P-start was ordered by the user.

2. The system forced the P-start due to inconsistent data, malfunction or unrecoverable task state.



10091, Restart not possible

Description

A restart after collision detection is not possible before acknowledge the error dialogue.


10092, (Re)start not possible

Description

(Re)start is not possible due to lost contact with IO module arg configured with trustlevel 3.



The Program Pointer must be moved before restart.

10099, Program start rejected

Description

The system has performed a soft stop, and the program may not be restarted.

Consequences

The system goes to the Motors OFF state and can not be started. The full meaning of this status is described in the Trouble shooting manual,

IRC5.

Probable causes

The soft stop may be caused by opening the safety circuit.


1) Check the safety circuits for an open switch.

2) Go to Motors ON and restart the program.

10093, (Re)start not possible

Description

(Re)start of task arg is not possible before a warm start is done.


The background task is configured with Trustlevel set to SysHalt

10095, At least one task is unchecked in the task selection panel

Description

One or more of the NORMAL tasks are unchecked in the task selection panel when performing a (re)start.


10106, Service Message

Description

It's time for service for robot arg because it is arg days since the last service.



Description

It remains arg days for robot arg until it's time for service.


10096, arg not active!

Description

The workobject arg contains a coordinated mechanical unit which is not activated.


Activate the mechanical unit and perform the operation again.


Description

It's time for service for robot arg cause it's arg hours of production since last service.



Description

The task arg is set in blocked state and the program is for that reason not possible to restart from the current program position.


The Program Pointer must be moved before restart.


Description

It remains arg hours of production for robot arg to next service.



Description

The task arg has been in system failure state and the program is for that reason not possible to restart from the current program position.


Description

The gearbox at arg of robot arg needs service.



Recommended actions Recommended actions


Description

The gearbox at arg of robot arg has reached arg of its service interval.


10125, Program stopped

Description

The task arg has stopped. The reason is that an external or internal stop has occurred.



Description

The system date and time has changed.

This could cause problems with the SIS calender notification.


The SIS parameters Calender Limit and Calender Warning might need to be changed


Description

The task arg has stopped. The reason is that an error has occurred.



Description

The task arg has stopped. The reason is that an external or internal stop after current instruction has occurred.


10127, Backward execution not possible

Description

The task arg has stopped. The reason is that it is not possible to execute backward past beginning of instruction list.



Description

The task arg has stopped. The reason is that the task has reached an exit instruction.


10128, Backward execution not possible

Description

The task arg has stopped. The reason is that it is not possible to execute backward past the instruction.



Description

The task arg has stopped. The reason is that the task is ready.



Description

The task arg has stopped. The reason is that the event routine for

RESET or POWER_ON is ready.



Description

The task arg has stopped. The reason is that the task is ready with this step.



Description

The task arg has stopped. The reason is that the task is ready with this move step.



Description

The task arg has stopped. The reason is that the task has reached a break instruction.


Description

The task arg has stopped. The reason is that the routine called from system IO interrupt is ready.





Description

The task arg has stopped. The reason could not be determined.


10157, Program restarted

Description

Execution of task arg has been restarted from where it was previously stopped. The restart order was initiated by an action causing the

UNDO handler to execute.


Description

The task arg has stopped. The reason is that the task is ready with the execution of the UNDO handlers.

10170, Background task arg

Description

refuse to start. Task is empty.


10150, Program started

Description

Execution of task arg has been started from the first instruction of the task's entry routine. The originator could not be determined.



Description

refuse to start. Wrong state.



Description

Execution of task arg has been started from the first instruction of the task's entry routine. The originator is an external client.



Description

Execution of task arg has been started from the first instruction of the task's entry routine. The start order was initiated by an action causing the UNDO handler to execute.


Description

refuse to start. Can't set PP to the main routine.

Probable causes

The module that contains the main routine was not loaded since the module file is missing in the target directory.

The module that contains the main routine was not loaded since the configuration file has no entry for automatic loading of the module.

The main routine is missing.

The main entry is corrupted.


Load the module by hand or perform an I-start when the cause of the problem is removed.


Description

Execution of task arg has been restarted from where it was previously stopped. The originator could not be determined.



Description

refuse to start. Can't set the execution mode.



Description

Execution of task arg has been restarted from where it was previously stopped. The originator is an external client.


Description

refuse to start. The start order failed.





Description

refuse to start due to a syntax error.


There is not sufficient program memory or the program memory is fragmented. Modules could be missing or data may not have been installed.


1. Unload/reload modules and warm start.

2. Split large data structures.

3. P-start the system.


Description

refuse to start. Can't load module.

Probable causes

The module file is missing in the target directory.


1. Copy the module file to the target directory.

2. Perform an I-start.

10190, Protected area not done

Description

A power fail did occur in the middle of a protected area for the task arg.

The system is trying to selfheal.


10177, Task refuses to start

Description

Task arg:

There is not sufficient program memory or the program memory is fragmented. Modules could be missing or data may not have been installed.


1. Unload/reload modules and warmstart.

2. Split large data structures.

3. P-start the system.

4. Increase stack size for task.


Description


A pending error is removed from the queue.



Description


A pending exit is removed from the queue.


10178, A static/semistatic task can't be stepped

Description

Task arg can't be started.

A static/semistatic task can only run in continuous mode.

Consequences

No tasks will be started.

Probable causes

Trying to step (forward or backward) a static/semistatic task.


Start arg in continuous mode.


Description


This may result in an extra program cycle.



Description


The task will be restarted from the main routine.


10185, Task could not be prepared for start

Description

Task arg:


Description


All tasks are reset and all user programs are lost.


Try to save the user program and do a warm start of the system




Description




10216, Execution cancelled

Description

The restart will clear the execution in task arg of an INTERNAL system event routine.



Description

The restart will clear the execution in task arg of a POWER ON system event routine.



Description

The restart will clear the execution in task arg of a USER routine.



Description

The restart will clear the execution in task arg of a STOP system event routine.



Description

The restart will clear the execution in task arg.



Description

The restart will clear the execution in task arg of an EMERGENCY

STOP system event routine.



Description

The restart will clear the execution in task argof a STEP system event routine.



Description

The restart will clear the execution in task arg of a START system event routine.


10230, Backup step ready

Description

The backup step Prepare is ready.



Description

The restart will clear the execution in task arg of a RESTART system event routine.



Description

The backup step Configuration is ready.



Description

The restart will clear the execution in task arg of a RESET system event routine.


Description

The backup of Task is ready.




10250, Restore step ready

Description

The restore step Prepare is ready.


10270, Cyclic Brake Check Done

Description

The Cyclic Brake Check has been done for all brakes supervised by

Safety Controllers.


Description

The restore step Configuration is ready.


10300, A P-Start is ordered

Description

The P-Start has been ordered from the system.



Description

The restore of Task is ready.


10301, A P-Start is ordered

Description

The P-Start has been ordered manually or automatically during a configuration.



Description

The restore of User Task is ready.


10304, An update has been ordered

Description

An update of program configuration is done.


10260, System diagnostics info generated

Description

System diagnostics information was successfully generated to file arg

10350, Update of task failed

Description

The system could not update task arg to the new configuration.


10351, A task is removed

Description

The task arg was removed because of configuration changes.


10261, System diagnostics info unavailable

Description

User requested to save diagnostics system information to file arg.

System was unable to fulfill this request.

Consequences

Diagnostics system information is normally used when reporting a problem with the system to ABB support.

Probable causes

The system is in such state that it is not possible to generate the requested information.

Please check that the device has enough space left.


If you are experiencing a problem with the system contact ABB support.

10352, A task is added

Description

The task arg was installed because of configuration changes.


10353, A task is reinstalled

Description

The task arg was reinstalled because of configuration changes.




10354, Restore aborted due to lost system data.

Description

The system is using a backup of the system data, since the system data was not properly saved at last shutdown. Due to this, a previously ordered Restore from directory arg was attempted again, but was aborted.

Consequences

No RAPID programs or modules will be loaded.

Probable causes

The system data was not properly saved at last shutdown.


After recovering from the system data loss by a (B)ackup-Restart or system re-installation, please verify that the backup directory arg is

OK, and perform the Restore again.


Check your program pointer and move it if necessary.

Reduce the speed.

10421, Planned path not aborted

Description

A target that may be part of the planned robot path has been modified.

The new target position will be used the next time the instruction with the target is executed.

Consequences

The current planned path is using the old target position.


If the current planned path is unsafe, move the program pointer to abort it.

10355, Restore error

Description

Error during the restore of Task. Trying to load to unknown task, arg.

Consequences

Loading has been aborted for arg.

Probable causes

The current system doesn't have the same options as the one used to create the backup.

11020, Backup error

Description

Error during the backup step Prepare. Unknown error.


arg


Description

Error during the backup step Prepare. General error.


arg

10400, User arg logged on

Description

User arg logged on using arg.

10401, User arg logged off

Description

User arg using arg logged off.


Description

Error during the backup step Prepare. The directory contains items that are to be created.


arg

10420, New unsafe robot path

Description

The robot path has been cleared after a target has been modified in task

arg. The robot will for that reason move towards the position pointed out by the move instruction at the program pointer. Move instructions between the modified target and the program pointer will be skipped.

Consequences

The programmed speed is used for this movement.

The new untested path may contain obstacles that might cause a collision.


Description

Error during the backup step Prepare. The directory lacks at least one neccessary item.


arg


Description

Error during the backup step Prepare. The directory does not exist.




arg


Description

Error during the backup step Prepare. Directory cannot be created.


arg


Description

Error during the backup step Prepare. The directory lacks at least one neccessary item.


arg


Description

Error during the backup step Prepare. Error whilst writing the backup.


arg


Description

Error during the backup step Prepare. The system version doesn't match the backup.


arg


Description

Error during the backup step Prepare. Error reading configuration parameters.


arg


Description

Error during the backup step Prepare. Error restoring configuration parameters.


arg


Description

Error during the backup step Prepare. Error writing configuration parameters.


arg


Description

Error during the backup step Prepare. Error restoring configuration parameters.


arg


Description

Error during the backup step Prepare. The structure is too deep.


arg


Description

Error during the backup step Prepare. Mismatch between current system and the backup.


arg


Description

Error during the backup step Prepare. No more objects.


arg


Description

Error during the backup step Prepare. Write error.

Consequences

The backup will be incomplete.

Probable causes

You may not have write access to the backup drive.

The drive might be full.

If it is a network drive you might have lost connection.




arg


Description

Error during the backup step Prepare. At least one modname is too long.


arg


Description

Error during the backup step Prepare. Unknown task.


arg


Description

Error during the backup step Prepare. Storage media full.


arg


Description

Error during the backup step Prepare. Item not possible to delete.


arg


Description

Error during the backup step Configuration. Unknown error.



Description

Error during the backup step Configuration. General error.



Description

Error during the backup step Configuration. The directory contains items that are to be created.



Description

Error during the backup step Configuration. The directory lacks at least one neccessary item.



Description

Error during the backup step Configuration. The directory does not exist.



Description

Error during the backup step Configuration. Directory cannot be created.



Description

Error during the backup step Configuration. Error whilst writing the backup.



Description

Error during the backup step Configuration. Error reading configuration parameters.



Description

Error during the backup step Configuration. Error writing configuration parameters.



Description

Error during the backup step Configuration. The structure is too deep.





Description

Error during the backup step Configuration. No more objects.



Description

Error during the backup step Configuration. The directory lacks at least one neccessary item.



Description

Error during the backup step Configuration. The system version doesn't match the backup.



Description

Error during the backup step Configuration. Error restoring configuration parameters.



Description

Error during the backup step Configuration. Error restoring configuration parameters.



Description

Error during the backup step Configuration. Mismatch between current system and the backup.



Description

Error during the backup step Configuration. Write error.



Description

Error during the backup step Configuration. At least one modname is too long.



Description

Error during the backup step Configuration. Unknown task.



Description

Error during the backup step Configuration. Storage media full.



Description

Error during the backup step Configuration. Item not possible to delete.



Description

Error during the backup of Task. Unknown error.



Description

Error during the backup of Task. General error.



Description

Error during the backup of Task. The directory contains items that are to be created.





Description

Error during the backup of Task. The directory lacks at least one neccessary item.



Description

Error during the backup of Task. The directory does not exist.



Description

Error during the backup of Task. Directory cannot be created.



Description

Error during the backup of Task. Error whilst writing the backup.



Description

Error during the backup of Task. Error reading configuration parameters.



Description

Error during the backup of Task. Error writing configuration parameters.



Description

Error during the backup of Task. The structure is too deep.



Description

Error during the backup of Task. No more objects.



Description

Error during the backup of Task. The directory lacks at least one neccessary item.



Description

Error during the backup of Task. The system version doesn't match the backup.



Description

Error during the backup of Task. Error restoring configuration parameters.



Description

Error during the backup of Task. Error restoring configuration parameters.



Description

Error during the backup of Task. Mismatch between current system and the backup.



Description

Error during the backup of Task. Write error.


Check: No space left on device. Corrupt device.




Description

Error during the backup of Task. At least one modname is too long.



Description

Error during the restore step Prepare. The directory lacks at least one neccessary item.


arg


Description

Error during the backup of Task. Unknown task.



Description

Error during the restore step Prepare. The directory does not exist.


arg


Description

Error during the backup of Task. Storage media full.



Description

Error during the backup of Task. Item not possible to delete.



Description

Error during the restore step Prepare. Directory cannot be created.


arg


Description

Error during the restore step Prepare. Unknown error.


arg


Description

Error during the restore step Prepare. Error whilst writing the backup.


arg


Description

Error during the restore step Prepare. General error.


arg


Description

Error during the restore step Prepare. Error reading configuration parameters.


arg


Description

Error during the restore step Prepare. The directory contains items that are to be created.


arg


Description

Error during the restore step Prepare. Error writing configuration parameters.


arg


Description

Error during the restore step Prepare. The structure is too deep.




arg


Description

Error during the restore step Prepare. No more objects.


arg


Description

Error during the restore step Prepare. The directory lacks at least one neccessary item.


arg


Description

Error during the restore step Prepare. The system version doesn't match the backup.


arg


Description

Error during the restore step Prepare. Error restoring configuration parameters.


arg


Description

Error during the restore step Prepare. Error restoring configuration parameters.


arg


Description

Error during the restore step Prepare. Mismatch between current system and the backup.


arg


Description

Error during the restore step Prepare. Write error.


arg


Description

Error during the restore step Prepare. At least one modname is too long.


arg


Description

Error during the restore step Prepare. Unknown task.


arg


Description

Error during the restore step Prepare. Storage media full.


arg


Description

Error during the restore step Prepare. Item not possible to delete.


arg


Description

Error during the restore step Configuration. Unknown error.



Description

Error during the restore step Configuration. General error.





Description

Error during the restore step Configuration. The directory contains items that are to be created.



Description

Error during the restore step Configuration. The structure is too deep.



Description

Error during the restore step Configuration. The directory lacks at least one neccessary item.



Description

Error during the restore step Configuration. No more objects.



Description

Error during the restore step Configuration. The directory does not exist.



Description

Error during the restore step Configuration. The directory lacks at least one neccessary item.



Description

Error during the restore step Configuration. Directory cannot be created.



Description

Error during the restore step Configuration. The system version doesn't match the backup.



Description

Error during the restore step Configuration. Error whilst writing the backup.



Description

Error during the restore step Configuration. Error restoring configuration parameters.



Description

Error during the restore step Configuration. Error reading configuration parameters.



Description

Error during the restore step Configuration. Error restoring configuration parameters.



Description

Error during the restore step Configuration. Error writing configuration parameters.


Description

Error during the restore step Configuration. Mismatch between current system and the backup.





Description

Error during the restore step Configuration. Write error.



Description

Error during the restore of Task. The directory contains items that are to be created.



Description

Error during the restore step Configuration. At least one modname is too long.



Description

Error during the restore of Task. The directory lacks at least one neccessary item.



Description

Error during the restore step Configuration. Unknown task.



Description

Error during the restore of Task. The directory does not exist



Description

Error during the restore step Configuration. Storage media full



Description

Error during the restore step Configuration. Item not possible to delete.



Description

Error during the restore of Task. Error whilst writing the backup



Description

Error during the restore of Task. Unknown error.



Description

Error during the restore of Task. General error.


Description

Error during the restore of Task. Directory cannot be created



Description

Error during the restore of Task. Error reading configuration parameters



Description

Error during the restore of Task. Error writing configuration parameters





Description

Error during the restore of Task. The structure is too deep




Description

Error during the restore of Task. Write error.



Description

Error during the restore of Task. No more objects



Description

Error during the restore of Task. At least one modname is too long.



Description

Error during the restore of Task. The directory lacks at least one neccessary item.



Description

Error during the restore of Task. Unknown task.



Description

Error during the restore of Task. The system version doesn't match the backup.



Description

Error during the restore of Task. Storage media full.



Description

Error during the restore of Task. Error restoring configuration parameters.



Description

Error during the restore of Task. Item not possible to delete.



Description

Error during the restore of Task. Error restoring configuration parameters.



Description

Error during the restore of User Task. Unknown error.



Description

Error during the restore of User Task. General error.



Description

Error during the restore of Task. Mismatch between current system and the backup.


Description

Error during the restore of User Task. The directory contains items that are to be created.





Description

Error during the restore of User Task. The directory lacks at least one neccessary item.



Description

Error during the restore of User Task. No more objects



Description

Error during the restore of User Task. The directory does not exist



Description

Error during the restore of User Task. The directory lacks at least one neccessary item.



Description

Error during the restore of User Task. Directory cannot be created



Description

Error during the restore of User Task. The system version doesn't match the backup.



Description

Error during the restore of User Task. Error whilst writing the backup



Description

Error during the restore of User Task. Error restoring configuration parameters.



Description

Error during the restore of User Task. Error reading configuration parameters



Description

Error during the restore of User Task. Error restoring configuration parameters.



Description

Error during the restore of User Task. Error writing configuration parameters



Description

Error during the restore of User Task. Mismatch between current system and the backup.



Description

Error during the restore of User Task. The structure is too deep


Description

Error during the restore of User Task. Write error.





Description

Error during the restore of User Task. At least one modname is too long.



Description

Error during the restore of User Task. Unknown task.



Description

Error during the restore of User Task. Storage media full.



Description

Error during the restore of User Task. Item not possible to delete.


12510, Network subnet mask illegal

Description

The subnet mask arg for network interface arg is illegal.

Consequences

The network interface will not be configured, and may not be used.

Probable causes

The network subnet mask may be mistyped.


1) Make sure the network subnet mask is correct.

12511, Network interface IP address illegal

Description

The network IP address arg for interface arg is illegal/missing.

Consequences

The interface will not be configured, and may not be used.

Probable causes

The network IP address may be mistyped or it already exists on the network.


1) Make sure the interface IP address is correct and not a duplicate.

12512, Network gateway IP address illegal

Description

The default gateway IP address arg is illegal/missing or the LAN IP address arg is illegal.

Consequences

The network will not be reached, and may not be used.

Probable causes

The gateway IP and/or LAN IP addresses may be mistyped.


1) Make sure the gateway IP and LAN IP addresses are correct.

12513, No parameters from the DHCP server

Description

The network interface arg has not received any parameters from the

DHCP server.

Consequences


Probable causes

The LAN connection is not working -The DHCP server is not activated.


1) Make sure the LAN cable is working and correctly connected.

2) Make sure the DHCP server is activated.

3) Set the LAN IP address manually.

12514, Network interface initialization error

Description

The network interface arg could not be initialized.

Consequences


Probable causes

The network parameters may be wrong.

-Although unlikely, the hardware may be faulty, requiring replacement.


1) Make sure the network parameters for the interface at hand are correct.

2) Isolate the cause, by replacing the suspected hardware.



20010, Emergency stop state

Description

The emergency stop circuit has previously been broken, and while broken, an attempt was made to operate the robot.

Consequences

The system remains in state "Waiting for Motors ON after emergency stop".

Probable causes

An attempt has been made to maneuvre a control, before switching the system back to status Motors ON.


1) To resume operation, switch the system back to state Motors ON by pressing the Motors ON button on the Control Module.

20011, Emergency stop state.

Description

Emergency stop reset is required.


First release the Em stop button and then press the panel button.


20031, Axis not calibrated.

Description

One or several absolute/relative measurement axes are not calibrated.


Check what axis that are not calibrated and calibrate them.

20032, Rev. counter not updated

Description

Revolution counter is not updated.

One or several absolute measurement axes are not synchronized.


Move the axes to the sync position and update the revolution counters.

20012, Sys failure state active

Description

Fatal non-recoverable system error.

Warm start is required.


Turn the mains switch off and on again if the soft restart command is ignored or not possible to reach.

20033, Axis not synchronized.

Description

One or several relative measurement axes are not synchronized.


Order Motors On and synchronize all mechanical units in the list.

20025, Stop order timeout

Description

The stop order was carried out as a forced guard stop when no acknowledgement was received within the expected time


20030, Axis not commutated

Description

One or several internal drive unit axes are not commutated.

20034, SMB memory is not OK

Description

This action or state is not allowed since data in the Serial Measurement

Board (SMB) memory is not OK.

Consequences


Probable causes

There are differences between the data stored on the SMB and the data stored in the controller. This may be due to replacement of SMB, controller or both, or manually cleared SMB.



Manual, IRC5.



20051, Not allowed command

Description

The command is only allowed when the client is in control of the resource (program/motion).

Consequences

The system remains in the same status, and the requested action will not be performed.


1) Check if the client is in control, by checking "Write Access" in

RobotStudio.

2) Check if the client who ought to be in control really is.


Description

The command is NOT allowed when the program is executing.

Consequences



1) Make sure the program is not executing.


Description

The command is not allowed in Auto mode.

Consequences



1) Make sure the system is NOT in Auto Mode.


Description

The command is not allowed when changing to Auto mode.

Consequences



1) Make sure the system is NOT changing to Auto Mode.


Description

The command is not allowed in Manual mode.

Consequences



1) Make sure the system is NOT in Manual Mode.


Description

The command is not allowed in Manual full speed mode.

Consequences



1) Make sure the system is NOT in Manual full speed Mode.


Description

The command is not allowed when changing to Manual full speed mode.

Consequences



1) Make sure the system is NOT changing to Manual full speed Mode.


Description

The command is only allowed in Manual mode (reduced or full speed).

Consequences



1) Make sure the system is NOT in Auto mode or changing to Manual

Mode (reduced or full speed).


Description

The command is not allowed in Motors ON state.

Consequences



1) Make sure the system is in Motors OFF state.




Description

The command is not allowed while changing to Motors ON state.

Consequences



1) Investigate by whom and why the action was requested, and, if required, correct the reason.


Description

The command is not allowed in Motors OFF state.

Consequences



1) Make sure the system is in Motors ON state.


Description

The command is not allowed while changing to Motors OFF state.

Consequences





Description

The command is not allowed in Guard Stop state.

Consequences



1) Make sure the system is NOT in Guard Stop state.


Description

The command is not allowed in Emergency Stop state.

Consequences

Emergency stop reset is required.


1) Make sure the system is NOT in Emergency Stop state.


Description

The command is not allowed in System Failure state.

Consequences

A non-recoverable system error has resulted, and a warm start is required.


1) Make sure the system is NOT in Emergency Stop state.

2) Perform a restart as detailed in the Operator's Manual, IRC5.

3) If restarting is not possible, switch the main power OFF and then back ON.


Description

The command is not allowed when axis has not been commutated.

Consequences



1) Commutate the axis as detailed in the Additional Axes Manual.



Description

The command is not allowed when axis is not calibrated.

Consequences



1) Calibrate the axis as detailed in the Calibration Pendulum

Instruction or the Instructions for Levelmeter calibration, depending on which equipment to be used.


Description

The command is not allowed when axis revolution counter is not updated.

Consequences





1) Update the revolution counter as detailed in Operator's Manual,

IRC5.


Description

The command is not allowed when axis is not synchronized.

Consequences



1) Synchronize the axis as detailed in the Calibration Pendulum

Instruction or the Instructions for Levelmeter calibration, depending on which equipment to be used.

Consequences

The system can not enter automatic mode.

Probable causes

Program pointer could not be set to Main.


1) Switch back to manual mode.

2a) Move PP to main.

2b) or if the program always shall start at the new routine, change

System Parameter "Main entry" (Domain Controller, Type Task) to the new routine name.

2c) or set System Parameter Controller/Auto Condition Reset/

AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto.

3) Switch back to automatic mode and confirm.


Description

This command is not allowed since data in the Serial Measurement

Board (SMB) memory is not OK.

Consequences




Manual, IRC5.

20088, Automatic Mode Rejected

Description

The speed could not be set to 100% when automatic mode was requested.

Consequences


Probable causes

The speed could not be set to 100%.


1) Switch back to manual mode

2a) Set the speed in the QuickSet menu

2b) or set System Parameter Controller/Auto Condition Reset/




Description

The call chain was altered to begin at a routine other than main and could not be reset to main when automatic mode was requested.


Description

Not allowed in state

System IO Start Blocked.



Description

One or more of the NORMAL tasks were disabled and could not be enabled when automatic mode was requested.

Consequences


Probable causes

It is not possible to reset Task Selection Panel in synchronized block.



2a) Set PP to main.

2b) or step out of synchronized block.

2c) or set System Parameter Controller/Auto Condition Reset/



20094, Load name could not be found

Description

Load name arg could not be found.

Consequences

It is not possible to jog without a correct defined load.

Probable causes

The module with the load definition is probably deleted.




Load module with load definition.

Choose other load.

20095, Tool name could not be found

Description

Tool name arg could not be found.

Consequences

It is not possible to jog without a correct defined tool.

Probable causes

The module with the tool definition is probably deleted.


Load module with tool definition.

Choose other tool.

20096, WorkObject name could not be found

Description

WorkObject name arg could not be found.

Consequences

It is not possible to jog without a correct defined workobject.

Probable causes

The module with the workobject definition is probably deleted.


Load module with workobject definition.

Choose other workobject.

20097, Not allowed to jog with LOCAL PERS

Load

Description

The object arg is of type LOCAL PERS and is not possible to jog.


Change Load.


Tool

Description



Change Tool.


Work Object

Description



Change Work Object.

20101, TP (program) in control.

Description

The teachpendant programming window has focus and is in control of the program server.


Change to the production window and perform the command again.

20103, Controller busy updating Task Selection

Panel.

Description

The Task Selection Panel is having an update.

It is not possible to do the requested command.


Perform the command again or make a warm start and perform the command again.

20105, Backup already in progress

Description

A backup is already in progress.

Consequences

The command "Backup" from System Input Signal will be rejected.


Use System Output Signal "Backup in progress" to control if a backup can be strarted or not.

20106, Backup path

Description

There are errors in the backup path or the backup name in the configuration for the System Input Backup. The directory for the backup can not be created.

Backup path: arg

Backup name: arg

Consequences

The command "Backup" from System Input Signal will be rejected.




Verify that configured path and name for the System Input Backup are correct.

20111, TP (program) in control

Description

The teachpendant programming window has focus and is in control of the program server.


Change to the production window and perform the command again.

20120, System IO in control

Description

See Title


20128, Work object data has changed

Description

The active work object arg was removed and replaced with arg. The work object data was located in task: arg connected to mechanical unit

arg.

Consequences

The work object definition for jogging may not be correct.

Probable causes

The work object data was removed. The module containing the original tool definition may have been deleted.


If you require the old definition, locate the program or module of the original work object data and load it.

20126, Load data has changed

Description

The active load arg was removed and replaced with arg. The load data was located in task: arg connected to mechanical unit arg.

Consequences

The load definition for jogging may not be correct.

Probable causes

The load data was removed. The module containing the original tool definition may have been deleted.


If you require the old definition, locate the program or module of the original load data and load it.

20130, Active Task Menu is restored

Description

During warm start, the "Active Task Menu" is restored in Auto mode.

Consequences

If one or several tasks were unchecked, they are now checked again after the warm start in Auto mode.

Probable causes

A warm start has been performed


Go to manual mode.

2. Uncheck the not wanted tasks

3. Go back to Auto mode.

20127, Tool data has changed

Description

The active tool arg was removed and replaced with arg. The tool data was located in task: arg connected to mechanical unit arg.

Consequences

The tool definition for jogging may not be correct.

Probable causes

The tool data was removed. The module containing the original tool definition may have been deleted.


If you require the old definition, locate the program or module of the original tool data and load it.


Description

One or more logical I/O signals were blocked and could not be unblocked when automatic mode was requested.

Consequences


Probable causes

Some blocked I/O signal could not be unblocked.



2a) Check Event Log for errors related to I/O.

2b) or set System Parameter Controller/Auto Condition Reset/





20132, Blocked I/O signals

Description

One or more logical I/O signals were blocked during startup in automatic mode.

Consequences

Blocked signals will be unblocked.

Probable causes

System was switched to automatic mode during warm start.

System parameter AllDebugSettings is set to Yes.


None, system has automatically reset debug settings.

To keep debug settings in auto:


2) Set system parameter Controller/Auto Condition Reset/

AllDebugSettings/Reset to NO.


4) For more info, see the Technical Reference Manual - System

Parameters.

20133, Debug Settings in Auto

Description

One or more logical I/O signals were blocked during startup in automatic mode.

Consequences

Blocked I/O signals will stay blocked.

System will not be in full production mode in auto.


For full production mode:



AllDebugSettings/Reset to YES.



Parameters.

20134, Call Chain

Description

The call chain has been altered to begin at a routine other than main.

Consequences

Program pointer will be reset to main routine.

Probable causes




For debug mode in auto:



2) Set system parameter AllDebugSetting, reset to NO.



Parameters.


Description

The call chain has been altered to begin at a routine other than main.

Consequences

Program pointer will not be set to main.









Parameters.

20136, Reduced Speed

Description

The system was running at reduced speed during startup in automatic mode.

Consequences

Speed will be set to 100%.

Probable causes










Parameters.


Description

The system was running at reduced speed during startup in automatic mode.

Consequences

Speed will stay unchanged.




109







Parameters.

20138, Disabled Tasks

Description

One or more of the NORMAL tasks were disabled during the startup when in automatic mode.

Consequences

All disabled normal tasks will be enabled.

Probable causes

System was switched to automatic mode during warm start










Parameters.


20141, Motors Off rejected

Description

Motors Off, via System IO, was rejected.


20142, Start rejected

Description

Start/restart of program, via System IO, was rejected.

The reason could be that the robot is outside of regain distance.


20143, Start at main rejected

Description

Start of program at main, via System IO, was rejected.


20144, Stop rejected

Description

Stop of program, via System IO, was rejected.



Description

One or more of the NORMAL tasks were disabled during startup in automatic mode.

Consequences

Disabled tasks will stay disabled.









Parameters.

20140, Motors On rejected

Description

Motors On, via System IO, was rejected.

20145, Stop cycle rejected

Description

Stop of program after cycle, via System IO, was rejected.


20146, Manual interrupt rejected

Description

Manual interrupt of program, via System IO, was rejected.


20147, Load and start rejected

Description

Load and start of program, via System IO, was rejected.


The name of the program file to be loaded (including mass memory unit) must be defined.



20148, Confirm rejected

Description

Emergency Stop reset confirm, via System IO, was rejected.


20149, Error reset rejected

Description

Program execution error reset, via System IO, was rejected.


Manual Interrupt is not defined.


Configure the interrupt routine name.

20157, Undefined Argument

Description

Program name for System IO

LoadStart is not defined


Configure the program name.

20150, Load failure

Description

Load of program, via System IO, failed.

Consequences

Program will not be possible to start.

Probable causes

- The arguments for the System Input Load are wrong.

- The module was loaded, but the system failed to set the program pointer.

- The program was executing.


Check the following:

- correct arguments for System Input Load.

- defined and correct name of the program file to be loaded (including mass memory unit).

- defined and correct name of the task that the program should be loaded in.

- program stopped before activating System Input Load.

20153, Motors On and Start rejected

Description

Motors On and Start/Restart of program, via System IO, was rejected.

The reason could be that the robot is outside of regain distance.


20158, No System Input signal

Description

A System Input has been configured to an I/O-signal that doesn't exist.

System Input: arg

Signal Name: arg

Consequences

The system goes to status SYS FAIL.


Add signal arg to eio.cfg or remove System Input arg from eio.cfg.

For every System Input a signal must be configured.

20159, No System Output signal

Description

A System Output has been configured to an I/O-signal that doesn't exist.

System Output: arg

Signal Name: arg

Consequences



Add signal arg to eio.cfg or remove System Output arg from eio.cfg.

For every System Output a signal must be configured.

20154, Stop instruction rejected

Description

Stop of program after instruction, via System IO, was rejected.


20156, Undefined Argument

Description

Interrupt routine name for System IO

20161, Path not found

Description

The system module arg in task

arg has a corresponding specification in the configuration for "Task modules" that point out a non existing file path


View "Task modules" in the "System

Parameter" menu and change the path



in the item for this system module

20162, Write error

Description

A write error occur when the system try to save the system module arg at arg in task arg. Or the file system was full


View "Task modules" in the "System

Parameter" menu and change the path in the item for this system module

20164, Reconfig failed

Description

There are still some unsaved system modules.


Read error descriptions in earlier messages.

Try another system start

20165, Program Pointer lost.

Description

Restart is no longer possible from current position.


The program has to be started from the beginning.

20166, Refuse to save module

Description

The module arg is older than the source at arg in task arg.


20167, Unsaved module

Description

The module arg is changed but not saved in task arg.

112


20170, The system was stopped

Description

An error was detected, which stopped the system.

Consequences

The system goes to status SYS STOP and the robot is stopped along the path. The full meaning of this status is described in the Trouble

Shooting Manual, IRC5.

Probable causes

A number of errors may cause this status transition.


1) Check other event log messages occurring at the same time to determine the actual cause.

2) Fix the cause of the fault.

20171, The system was halted

Description

An error was detected, which halted the system.

Consequences

The system goes to status SYS HALT, the program and robot motion is stopped and the motors are switched OFF. The full meaning of this status is described in the Trouble Shooting Manual, IRC5.

Probable causes





3) Restart the program.

20172, The system has failed

Description

An error was detected, which caused the system to fail.

Consequences

The system goes to status SYS FAIL. The program and robot motion is stopped and the motors are switched OFF. The full meaning of this status is described in the Trouble Shooting Manual, IRC5.

Probable causes





3) Perform a system restart as detailed in the Operator's Manual, IRC5.



20176, Analog System Output Outside Limits

Description

The value arg for the System Output arg, signal arg, is outside its limits (logical min: arg m/s, logical max: arg m/s).

Consequences

The new value is not set; the previous value of the analogue signal is preserved.

Probable causes

The logical upper and/or lower limit for the signal may be defined wrongly.


Adjust the values of the logical upper and/or lower limit for the signal and restart the controller.

Consequences

The disk memory is very close to being completely full. When this happens the system will not be able to function.

Probable causes

Too much data on the disk


1) Save the files on some other disk connected to the network.

2) Erase data from disk.

3) After removing files from the drive, restart the program.

20181, System Reset rejected.

Description

System Reset via System IO not allowed.


20177, Short circuit in Motor phase circuit

Description

The motor or motor cable for joint arg in drive module arg, drive unit number arg, is a short circuit.

Consequences

No operation will be possible until after correcting the fault. The system goes to status SYS HALT.

Probable causes

This may be caused by a faulty motor or motor cable. It may also be caused by contamination in the contactors for the cables or a failure of the motor windings.


1) Make sure the motor cable is correctly connected to the drive unit.

2) Check the cable and motor by measuring their resistance respectively. Disconnect before measuring.

3) Replace any faulty component.

20178, Wrong task name configured

Description

Wrong task name arg configured for System Input arg.

Consequences

The digital input signal will not be connected to the specified event.


Change the configuration and restart the system.

20179, Disk memory critically low

Description

The amount of free storage capacity on the disk has reached a critical level. It is now less than 10 Mb. Execution of RAPID programs is stopped.

20184, Incorrect argument for System Inputs

Description

An undefined Start Mode has been declared for System IO.


20185, Incorrect Name

Description

An undefined Name has been declared in current runchn_bool configuration.


20187, Diagnostics record file created

Description

Due to any of a number of faults, a system diagnostics file was created at arg. This file contains internal debug info and is intended for trouble shooting and debugging purposes.

Consequences

The system will react to the error causing the stop as specified in its own event log text.

Probable causes

A number of errors may cause this. Faults causing the system to go to status SYS FAIL will generally also create a diagnostics record file.


If required, the file may be appended to an error report sent to your local ABB representative.



20188, System data is not valid

Description

The contents of the file, arg, containing system persistent data is invalid. Internal error code: arg. The system has been started using last good system data saved earlier at arg.

Consequences

Any changes made in the system configuration or RAPID programs since arg will NOT be available after restart. Any such changes will have to be re-implemented.



2) If acceptable, perform a B-restart to accept starting with the loaded last good system data.

3) Reinstall the system.

4) Check the available disk storage capacity. If required, erase data to increase free storage capacity.

data (SIS) was restored from backup.

The system independent robot data was not saved during system shutdown. The data was restored from latest backup.


Make sure there is free memory left on the device.

The backup battery may be drained. Check the hardware log.

20194, System data backup could not be created

Description

The system was restored successfully but a backup of the current system data could not be created.


Make sure there is free memory left on the device arg.

20189, Robot data not valid

Description

Could not load the system independent robot data from file arg.

The file exists but the content is not valid. Internal code: arg


Check other logged messages for needed actions.

Make sure there is free memory left on the device.

20192, Disk memory low

Description

The amount of free storage capacity on the disk is less than 25 MB.

When reaching 10 MB, execution of RAPID programs will be stopped.

Consequences

The disk memory is close to being completely full. When this happens the system will not be able to function.

Probable causes

Too much data on the disk


1) Save the files on some other disk connected to the network.

2) Erase data from disk.

20195, System data from last shutdown is lost

Description

Normally, all system data is saved on shutdown. During the last shutdown saving data has failed. The system has been started using last good system data saved earlier at arg.

Consequences

Any changes made in system configuration or RAPID programs since

arg will NOT be available after restart. Any such changes will have to be re-implemented.

Probable causes

The backup energy bank may have been drained at the time of the shut down. The storage disk may be full.



2) If acceptable, perform a B-restart to accept starting with the loaded system data.


4) Check the available disk storage capacity. If required, erase data to increase free storage capacity.

20193, Robot data update warning

Description

Axis sync values and service information

20196, Module saved

Description

During reconfiguration of the system a changed and not saved module was found.

The module was saved to

arg.




20197, System data from last shutdown can not be found

Description

Normally, all system data is saved on shutdown. The file containing system persistent data cannot be found. The system has been started using last good system data saved earlier at arg.

Consequences

Any changes made in system configuration or RAPID programs since

arg will NOT be available after restart. Any such changes will have to be re-implemented.

Probable causes

The file containing the saved system data may have been manually moved or deleted.


1) Check the location and availability of the saved system data file.

2) If acceptable, perform a B-restart to accept starting with the loaded last good system data.


20199, System SoftStop Rejected

Description

The System Input SoftStop is not allowed


Consequences

The system goes to the Motors OFF status.

Probable causes

The robot has been run outside the working range defined by the limit switches fitted to the robot.


1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area.

2) Resume operation.

20202, Emergency Stop open

Description

The emergency stop circuit has previously been broken, and while broken, an attempt was made to operate the robot.

Consequences

The system remains in the Emergency Stop status.

Probable causes

An attempt has been made to manoeuvre a control, e.g. the enabling device.


1) To resume operation, first reset the emergency stop button triggering the stop.

2) Then switch the system back to state Motors ON by pressing the

Motors ON button on the Control Module.

20200, Limit Switch opened by SC

Description

The limit switch on the robot has been opened by the Safety Controller

(SC)

Consequences

The system goes to the Guard stop state.

Probable causes

The Safety Controller has opened the limit switch because of a safety violation.


1) Check for reason found in other event logs.

2)Check the cable between the contactor board and the Safety

Controller

3)Do a Confirm Stop by pressing the Motors on push button or by activating the appropriated system input.

20203, Enabling Device open

Description

Only one of the two Enabling Device chains was opened.

Consequences

The system goes to status SYS HALT.

Probable causes

The teach pendant Enabling Device may be faulty or incorrectly connected. The teach pendant and its Enabling Device is described in the Trouble Shooting Manual, IRC5.


1) Check the teach pendant cable and its connection.

2) If required, replace the faulty teach pendant or its cable.

20201, Limit Switch open

Description

The limit switch on the robot has opened.

20204, Operation Key imbalance

Description

The system has detected an imbalance in the two parallel MANUAL /

AUTO Operation Key circuits.

Probable causes

The contact pair in any of the cables connected to the Operation Key circuit is not working correctly.




1) Isolate the cable connection causing the conflict

2) Connect the cable in a correct way


1) Check other error messages for primary fault reason.

2) Locate the switch, reset it and restart the system.

3) Check cables and connections.

20205, Auto Stop open

Description

The Automatic Mode Safeguarded Stop circuit has been broken.

Consequences

The system goes to the Auto Stop status.

Probable causes

One or more of the switch connected in series with the Automatic

Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is only possible while in the

Auto operational mode. The Automatic Mode Safeguarded Stop circuit is described in the Trouble Shooting Manual.




20206, General Stop open

Description

The General Mode Safeguarded Stop circuit has been broken.

Consequences

The system goes to the General Stop status.

Probable causes

One or more of the switch connected in series with the General Mode

Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is possible in any operational mode. The

General Mode Safeguarded Stop circuit is described in the Trouble

Shooting Manual.




20208, Chain switches open

Description

A safety chain, other than Auto Stop and General Stop, has been broken.

Consequences

The system goes to the Guard Stop status.

Probable causes

One or more of the switch connected in series with the RUN Chain Top circuit have been opened, which may be causes by a large number of faults. The RUN Chain Top is described in the Trouble Shooting

Manual and Circuit Diagram.

20209, External Contactor open

Description

An external contactor has been opened.

Consequences

The system goes from the Motors OFF status to SYS HALT when attempting to start.

Probable causes

The RUN chain of external equipment has been broken, which may be caused by the external contactor auxiliary contacts or, if used, any

PLC, controlling it. The external contactor supplies power to a piece of external equipment, equivalently to how the RUN contactor supplies a robot. This fault may occur when attempting to go to the Motors ON mode only. The RUN chain is described in the Trouble Shooting

Manual and Circuit Diagram.




3) Check the external contactor auxiliary contacts.

4) If used, check any PLC equipment controlling the external contactor.

20211, Two channel fault, ENABLE chain

Description

A switch in only one of the two ENABLE chains was briefly affected, opening the chain and then reclosing it, without the other chain being affected.

Consequences


Probable causes

There may be a loose signal connection on either the axis computer or the Safety System. The ENABLE chain is described in the Trouble

Shooting Manual and Circuit Diagram.



2) Make sure all signal connectors on the axis computer board and the

Safety System are securely connected.

3) If there is no loose connection, replace the faulty board.

20212, Two channel fault, RUN CHAIN

Description

Only one of the two RUN chains was closed.



Consequences


Probable causes

Any of the switches connected to the RUN chain may be faulty or not correctly connected, causing only one channel to close. The RUN chain is described in the Trouble Shooting Manual, IRC5.



2) Check other event log messages occurring at the same time to determine which switch caused the fault.

3) Make sure all switches are working correctly.

4) To assist in returning the chains to a defined status, first pressing, then resetting the Emergency Stop

5) If there is no loose connection, replace the faulty switch.

20215, Superior Stop open

Description

The Superior Mode Safeguarded Stop circuit has been opened.

Consequences

The system goes to the Superior Stop status.

Probable causes

One or more of the switch connected in series with the Superior Mode

Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is possible in any operational mode. The

Superior Mode Safeguarded Stop circuit is described in the Trouble

Shooting Manual.



20213, Two channel fault

Description

A brief status change in any of the RUN or ENABLE chains has been detected.

Consequences


Probable causes

This may be caused by a number of faults. The ENABLE and RUN chains are described in the Trouble Shooting Manual, IRC5.



2) Check other event log messages occurring at the same time to determine the cause of the fault.

3) To assist in returning the chains to a defined status, first pressing, then resetting the Emergency Stop may work.

20216, Enabling device active in Auto mode

Description

The system has detected that the Enabling device has been pressed for more than 3 seconds in Automatic operating mode.

Consequences

The system goes to status Guard Stop.


1. Release the Enabling device

2. Switch to Manual mode

20214, Limit Switch open, DRV1

Description


Consequences


Probable causes






Description


Consequences


Probable causes






Description


Consequences




Probable causes






Description


Consequences


Probable causes






Please check the Run chain cables.

20222, Limit switch conflict

Description

Only one of the two Limit switch chains was opened.

Consequences


Probable causes

Any of the switches connected to the Limit switch chain may be faulty or not correctly connected, causing only one channel to close. The

Limit switch chain is described in the Trouble Shooting Manual, IRC5.






20220, Superior stop conflict

Description

Only one of the two Superior Mode Safeguarded Stop chains was opened.

Consequences


Probable causes

Any of the switches connected to the Superior Stop chain may be faulty or not correctly connected, causing only one channel to close.

The Superior Stop chain is described in the Trouble Shooting Manual,

IRC5.






20221, Run chain conflict

Description

Status conflict for Run chain.

20223, Emergency Stop conflict

Description

Only one of the two Emergency Stop chains was opened.

Consequences


Probable causes

Any of the switches connected to the Emergency Stop chain may be faulty or not correctly connected, causing only one channel to close.

The Emergency Stop chain is described in the Trouble Shooting

Manual, IRC5.






20224, Enabling Device conflict

Description

Only one of the two Enabling Device chains was opened.

Consequences


Probable causes

The teach pendant Enabling Device may be faulty or incorrectly connected. The teach pendant and its Enabling Device is described in the Trouble Shooting Manual, IRC5.




1) Check the teach pendant cable and its connection.

2) If required, replace the faulty teach pendant or its cable.

20225, Auto Stop conflict

Description

Only one of the two Automatic Mode Safeguarded Stop chains was opened.

Consequences


Probable causes

Any of the switches connected to the Auto Stop chain may be faulty or not correctly connected, causing only one channel to close. The Auto

Stop chain is described in the Trouble Shooting Manual, IRC5.






Probable causes

A failure of the motor contactor auxiliary contacts or the supply to these.



2) Check the function of the auxiliary contacts.

20231, Delayed Emergency Stop due to circuit imbalance

Description

The system has detected an imbalance in the two parallel Emergency

Stop circuits.

Consequences

The system goes to status Emergency Stop after approximately 1 sec.

Probable causes

The contact pair in any of the Emergency Stop buttons is not working correctly.


1. Isolate the Emergency Stop button causing the conflict.

2. Check the contact pair.

3. Make sure all connections are tight.

4. Replace the button if required.

20226, General Stop conflict

Description

Only one of the two General Mode Safeguarded Stop chains was opened.

Consequences


Probable causes

Any of the switches connected to the General Stop chain may be faulty or not correctly connected, causing only one channel to close. The

General Stop chain is described in the Trouble Shooting Manual,

IRC5.






20232, Delayed Auto Stop due to circuit imbalance

Description

The system has detected an imbalance in the two parallel Auto Stop circuits.

Consequences

The system goes to status Guard Stop after approximately 1 sec.

Probable causes

The contact pair in any of the safety devices connected to the Auto

Stop circuit is not working correctly.


1. Isolate the safety device causing the conflict.

2. Make sure the device used is a two-channel device.



5. Replace the device if required.

20227, Motor Contactor conflict, DRV1

Description

Only one of the two Motor Contactors for drive system 1 has acknowledged the activation order.

Consequences


20233, Delayed General Stop due to circuit imbalance

Description

The system has detected an imbalance in the two parallel General Stop circuits.



Consequences


Probable causes

The contact pair in any of the safety devices connected to the General








20234, Immediate Emergency Stop

Description

The Emergency Stop circuits have been broken.

Consequences

The system goes directly to status Emergency Stop.

Probable causes

One or more of the red emergency stop buttons have been activated.


1) Isolate the Emergency Stop button that was opened.

2) Reset the button.

20235, Immediate Auto Stop

Description

The Auto Stop circuits have been broken.

Consequences

The system goes directly to status Guard Stop.

Probable causes

One or more of the safety device switches in the Auto Stop circuit have been opened


1) Isolate the safety device that was opened

2) Reset the device switch.




20237, Immediate Superior Stop

Description

The Superior Stop circuits have been broken.

Consequences


Probable causes

One or more of the safety device switches in the Superior Stop circuit have been opened




20238, Delayed Superior Stop due to circuit imbalance

Description

The system has detected an imbalance in the two parallel Superior Stop circuits.

Consequences


Probable causes

The contact pair in any of the safety devices connected to the Superior








20236, Immediate General Stop

Description

The General Stop circuits have been broken.

Consequences


Probable causes

One or more of the safety device switches in the General Stop circuit have been opened

20240, Conflict between ENABLE signals

Description

A switch in only one of the two ENABLE chains was affected, without the other chain being affected.

Consequences


Probable causes

There may be a loose signal connection on the Safety System. The

ENABLE chain is described in the Trouble Shooting Manual and

Circuit Diagram.





2) Make sure all signal connectors on the Safety System are securely connected.

3) If there is no loose connection, replace the faulty board.

20241, Operating mode conflict

Description

There is a conflict between the operating mode selected on the operating mode selector on the controller cabinet front and the actual operating mode as detected by the axis computer.

Consequences


Probable causes

There may be a hardware fault in the operating mode selector or its cabling to the Safety System.


Check the operating mode selector and its cabling to the Safety

System.

20247, Run Control status conflict, DRV4

Description

Status conflict between Run Control and Motor Contactors for drive system 4.

Consequences


Probable causes

A failure of the Motor Contactors or the supply to these.



2) Do a Warm start.


Description


Consequences


Probable causes




2) Do a Warm start.


Description


Consequences


Probable causes






Description


Consequences


Probable causes




2) Do a Warm start.


Description


Consequences


Probable causes






Description


Consequences




Probable causes






1) Wait until the overheated Motor has cooled down before ordering

Motors On again.

2) If optional air filter is used, check if it is clogged and has to be exchanged

20252, Motor temperature high, DRV1

Description

Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again.



Motors On again.


20255, External device temperature high, DRV2

Description

Over temperature in External Device. Make sure to let the External

Device cool down before ordering Motors On again.


Wait until the overheated Motor has cooled down before ordering

Motors On again.


Description



Description





Motors On again.


Description





Motors On again.


Description




Motors On again.



Description




Motors On again.



Description





Motors On again.


Description


Consequences


Probable causes




2) Do a Warm start.



20262, SC arg Not found

Description

The system has an option for arg Safety Controller (SC) on drive module arg, but no Safety Controller was found.


- Check Safety Controller cabling.

- Check Safety Controller health.

Warm start controller, after performing recommended actions.


1. Check previous error logs for possible causes.

2. Restart the system.

20268, SC arg Wrong Type

Description

Found arg Safety Controller (SC) on drive module arg, expected

arg.


- Check drive module software options.

- Install a system with correct Safety Controller option.

- Install a Safety Controller of the correct type.

20263, SC arg Communication Failure

Description

Communication error with Safety Controller (SC) arg





20270, Access error

Description

Panel Module access error.


Examine your I/O configuration files.

20264, SC arg Option Not Present

Description

Found arg Safety Controller (SC) on drive module arg.This system does not have the option for a Safety Controller on that drive module.


- Check drive module software options.

- Install a system with Safety Controller option.

20265, SC Soft Stop Error

Description

Safety Controller (SC) Soft Stop has not opened the Motor Contactors within the calculated time


Check Lim-switch connection if SafeMove is present

20280, Symbol conflict

Description

The signal arg defined in the IO configuration conflict with another program symbol with the same name.

Due on that fact the signal will not be mapped to a program variable.


Rename the signal in the IO configuration.

20266, SC arg PIN Code Request

Description

Safety Controller (SC) arg has a new Safety Configuration and needs a new PIN code to be activated.


1. Log in as a user with Safety Configuration grants.

2. Enter new PIN-Code for the Safety Controller in the Control Panel.

20281, IO configuration error

Description

argarg with signal name arg has wrong signal type. Found arg expected arg.


Change your configuration and restart the system.

20267, SC arg Initialization Failed

Description

Safety Controller (SC) arg failed to initialize properly, or failed to respond during start up.

20282, Resource and index exist

Description

Resource arg

Index arg.




20283, Text database is full.

Description

Resource arg

Index arg


20288, Unknown System Output Type

Description

The configured System Output type is unknown by the system.

Unknown System Output: arg


Verify that the System Output name is correctly spelled.

20284, Wrong Signal Type For System Input

Description

The System Input arg is configured with an I/O-signal of wrong type.

The I/O-signal arg is of type arg and this System Input requires an I/O-signal of type arg.


Change the configuration for the specified System Input.

20289, Unknown System Input Type

Description

The configured System Input type is unknown by the system.

Unknown System Input: arg


Verify that the System Input name is correctly spelled.

20285, Wrong Signal Type For System Output

Description

The System Output arg is configured with an I/O-signal of wrong type.

The I/O-signal arg is of type arg and this System Output requires an I/O-signal of type arg.


Change the configuration for the specified System Output.

20290, Unknown Mechanical Unit Name For

System Output

Description

A System Output is configured with a mechanical unit name which is unknown by the system.


Mechanical unit name: arg


The specified mechanical unit must be configured in order to be used by System Outputs

Verify that the mechanical unit name is correctly spelled.

20286, Not Unique I/O-Signal For System

Output

Description

Each System Output must have a unique I/O-signal configured.

It is not possible to configure same I/O-signal to several System

Outputs.


Signal Name: arg


20291, Unknown System Input Restriction Type

Description

The configured System Input Restriction Type is unknown by the system.

Unknown System Input Restriction: arg


Verify that the System Input Restriction name is correctly spelled.

20287, Not Unique I/O-signal For System Input

Description

Each System Input must have a unique I/O-signal configured.

It is not possible to configure same I/O-signal to several System Inputs.

System Input: arg

Signal Name: arg

20292, Unknown System Input Restriction

Description

The configured System Input Restriction is unknown by the system.

System Input Restriction Type: arg

Unknown System Input Restriction: arg


Verify that the System Input Restriction name is correctly spelled.



20293, System Input is Restricted

Description

The system input arg is restricted by the system input arg set by I/O signal arg.

Consequences

The action called for by system input arg will not take place, and the operation will NOT be affected.

Probable causes

System input arg may be set by external equipment, such as PLCs, etc, for a number of reasons.


1) Investigate why the system input was set, and, if required, correct the reason.

20307, Motor cooling fan malfunction, axis 1

Description

The axis 1 motor cooling fan on the robot connected to Drive Module

arg does not work correctly.

Consequences

The full meaning of this status is described in the Trouble Shooting

Manual, IRC5.

Probable causes

-The fan power cabling may be damaged or not connected correctly to motor or contactor unit.

-The fan or the Drive Module Power Supply may be faulty.


1) Make sure the fan cable is correctly connected

2) Make sure the fan is free to rotate and that the air flow is not obstructed.

3) Make sure the Drive Module Power Supply output and input voltages are within specified limits as detailed in the Trouble shooting manual. Replace any faulty unit.

20294, Action arg can not be fulfilled.

Description

The requested action cannot be fulfilled since the IO unit is not responding.

Consequences

It is not possible to decide if there are any restrictions set to the action.

Probable causes

The requested action will not be fulfilled until the I/O unit is enabled again.


Never disable a unit with System Inputs/Outputs.

20295, Signal cannot be used as System

Output.

Description

The System Output arg is configured with an I/O-signal with wrong category. The I/O-signal arg has category Safety and can not be used as System Output.


Choose another signal or set to another category.


Description



Consequences


Manual, IRC5.

Probable causes







20296, Wrong task name configured

Description

Wrong task name arg configured for System Output arg.

Consequences

The digital output signal will not be connected to the specified event.




Description



Consequences


Manual, IRC5.



Probable causes







20310, SC arg Communication Failed

Description

An error occurred while trying to communicate with Safety

Controller (SC) arg





20313, Enable1 supervision fault

Description

The ENABLE1 circuit has been broken. This circuit monitors the function of the Safety System and the main computer.

Consequences


Probable causes

A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE1 circuit.


1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative.

2) Determine which unit is faulty by checking its indication LEDs. The

LEDs are described in the Trouble Shooting Manual. Replace the faulty unit.

20311, Enable 1 open

Description

The ENABLE 1 circuit monitoring the Safety System has been opened.

Consequences


Probable causes

There may be an internal fault in the Safety System or the internal supervision has detected a fault.


1) Check all connections to the Safety System.

2) If faulty, replace the faulty board.

20314, Enable2 supervision fault

Description

The ENABLE2 circuit to drive module 1 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer.

Consequences


Probable causes






20312, Enable 2 open

Description

The ENABLE 2 circuit monitoring the Axis Computer has been opened.

Consequences


Probable causes

There may be a connection problem between Main Computer and Axis

Computer.


1) Check all connections to the axis computer.

2) Check cables conntected to the Safety System.

20315, Enable2 Supervision fault

Description


Consequences


Probable causes





1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in safety board, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative.



20350, Not a valid task name

Description

The task name arg cannot be used as a name of a task. It is either already used as an installed symbol, a reserved word in the system or too long (max. 16 characters).

Consequences

The task will not be installed in the system.


Change the configuration of the task name and restart the controller.


Description


Consequences


Probable causes






20351, Max number of tasks exceeded

Description

The maximum number of tasks, arg, of the configuration type arg is exceeded.

Consequences

All configured tasks will not be installed.




Description


Consequences


Probable causes



1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, Axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative.



20352, Not a valid motion planner name

Description

The motion planner name for mechanical unit group arg in arg is not correct.

The reason can be one of the following:

1. empty name

2. not present in the motion configuration

3. already in use by another mechanical unit group

Consequences

The system will not be able to use.


Change the configuration and restart the controller.

20353, Mechanical unit not found

Description

The mechanical unit arg in arg can not be found in the list of configured mechanical units.

Consequences

It is not possible to execute any RAPID instructions that use the configured mechanical units.

Probable causes

The unit is probably not present in the motion configuration.





20354, The argument is undefined

Description

The configured argument arg for task arg is not a valid type.

Consequences

The behaviour of the task will be undefined.



20355, Mechanical unit group name not correct

Description

The configured name of arg in task arg is not correct.

The reason could be:

1. The argument is not used in the configuration

2. The configured name is not a member of the mechanical unit group

3. The configured name is already used by another task.

Consequences

The task will not be installed or it will not be possible to execute

RAPID motion instructions.



Consequences

It is not possible to execute any RAPID move instructions.



20359, Cfg type arg is configured

Description

The type was found but not expected in a system with current options.


Check if the right configuration file is loaded or remove all instances of the type.

Restart the controller.

20360, Unknown event in cfg type arg

Description

The event arg is not a system event.



20356, Maximum number of motion tasks exceeded

Description

Only arg tasks are allowed to control mechanical units i.e. execute

RAPID move instructions.



20361, Only shared modules in the shared task

Description

The module arg is not configured shared and cannot be loaded into the shared task.



20362, Not defined task name

Description

The task arg in cfg type arg is not configured in the system.



20357, No configured motion task

Description

No task is configured to control mechanical units i.e. execute RAPID move instructions.

Consequences

It is not possible to execute any RAPID move instructions.


Change the configuration to include a task controlling mechanical units.


20363, Module not a system module

Description

The module arg loaded from the file arg is not a system module.


Change the file suffix or add a module attribute to the module.

Load the module again or restart the system.

20358, No members of arg configured

Description

The configuration type is required in a multi robot system.

20364, Max number of mechanical unit groups exceeded

Description

The maximum number of mechanical unit groups, arg, of the configuration type arg is exceeded.



Consequences

Exceeded instances are ignored.



20365, Update of configuration is done

Description

All tasks are reset to its main routine due to configuration changes.


20366, Type error in task configuration

Description

The task arg is configured with wrong type. Task configured to control mechanical units i.e. execute RAPID move instructions must be of type arg.

Consequences

The task will not be installed.



20367, No configured mechanical units

Description

The instance arg of configuration type arg has no mechanical unit argument.

Consequences

It will not be possible to perform any actions against the motion system, i.e. execute RAPID move instructions.



3. Remove the mechanical unit group.

4. Check for misspelled names.

20369, Confusing configuration of system parameters.

Description

There is a mixture of old and new structure of type System Misc.

Consequences

It is possible that not the correct parameters are configured.

Probable causes

Configuration of old and new structure has been loaded into the system.


1. Check that the correct parameters are configured.

2. Update the parameters in System Misc with correct values.

3. Save the controller domain and replace the old config file.

20370, Failed to read configuration data for regain distance

Description

The system failed to read the configuration data for the type <arg>.

The regain distance is the limit when the system will warn before a start with regain movement.

Consequences

Default value for the regain distance will be used.

Probable causes

-The sys.cfg file loaded into the system does not contain any regain distance information.

-No sys.cfg file has been loaded due to file errors.


1) Load a new sys.cfg file and restart the system

20368, Not connected mechanical unit group

Description

There is no RAPID motion task connected with the mechanical unit group arg.

Consequences

It will not be possible to use the mechanical units that belong to this group.

Probable causes

The cause of this error can be a missing RAPID task instance in the controller domain of the configuration or a task that has not been configured as a motion task.


1. Add a motion task instance that is connected to the mechanical unit group.

2. Change an existing non-motion task to a motion task.

20371, A default mechanical unit group is used

Description

The configuration of task arg has no connection to arg. The attribute

arg is required in a multimove system and is missing.

Consequences

The task performs no movement by the mechanical unit, but can read motion data. The RAPID functions may fail, if they read motion data and is connected to the wrong mechanical unit. The mechanical unit group in arg has been connected to the task.

Probable causes

-The attribute was not specified when the configuration was created.

-The configuration file could have been created in a non-multi move system.




1) Make sure the correct mechanical unit group is connected to the task.

20372, Failed to read configuration data.

Description

The system failed to read the configuration data for the type <arg>.

Consequences

Hotedit or modpos will not be possible.

Probable causes

-The sys.cfg file loaded into the system does not contain hotedit and modpos information.

-No sys.cfg file has been loaded due to file errors.


Load a new sys.cfg file and restart the system

20390, Start rejected

Description

Start/restart of program, via System IO, was rejected.

The reason is that write access is held by

arg using arg


20391, Start at main rejected

Description

Start of program at main, via System IO, was rejected.


arg using arg


20380, No motion planner connected to mechanical unit

Description

The mechanical unit arg has no motion planner connected.

Consequences

It is not possible to use this mechanical unit in any operations such as calibration or activation.

Probable causes

The cause of this error is probably an error in the configuration.


Check the motion and/or controller configuration.


Description

Manual interrupt of program, via System IO, was rejected.


arg using arg


20393, Load and start rejected

Description

Load and start of program, via System IO, was rejected.


arg using arg


20381, Error when recreating path after power fail

Description

The path wasn't successfully recreated.

Consequences

The Program Pointer must be moved before restarting the program. It's recommended to move the robot to a safe position though the robot might not follow the original path when restarted.

Probable causes

A number of errors may cause this. Faults causing the system to go to status SYS FAIL will generally also cause path recreate after powerfail to fail.




3) Move the robot to a safe position before restarting. The robot may not follow the original path.

20394, Motors On and Start rejected.

Description

Motors On and Start/restart of program, via System IO, was rejected.


arg using arg


20395, Load rejected

Description

Load of program via System IO, was rejected.


arg using arg




Description

Manual interrupt of program, via System IO, was rejected in task arg.

Manual interrupt is not allowed during synchronized movement.


1) Switch back to auto mode





Parameters.


Description

Manual interrupt of program, via System IO, was rejected in task arg.

The interrupt is connected to arg, which is not a valid RAPID procedure.

Consequences

arg will not be executed.

Probable causes

1. arg does not exist.

2. arg is not a procedure (PROC) that takes zero (0) parameters.


Make sure that arg is an existing procedure (PROC) that takes zero (0) parameters.

20400, Debug Settings In Auto

Description

A static/semistatic task (alias background task) has been stopped.

Consequences

The static/semistatic task will not be started.






AllDebugSettings/Reset to Yes.



Parameters.


Description

A stopped static/semistatic task (alias background task) could not be started when automatic mode was requested.

Consequences


Probable causes

A stopped static/semistatic task could not be started.



2) Make sure that all static/semistatic tasks has a program/module containing the configured production entry.

3) Make sure that no static/semistatic task has any syntax errors.


20401, Too many CFG instances

Description

There are too many instances arg of type arg in topic arg.

Consequences

The wrong instance may be used and cause unexpected behavior.

Probable causes

There are multiple instances of argof type arg in topic arg.


Remove all instances but one.

20399, Static/Semistatic task started

Description

At least on static/semistatic task (alias background task) was not executing after startup in automatic mode.

Consequences

Execution was started in at least one static/semistatic task.

Probable causes




20440, Failed to initialize FW upgrade framework

Description

The firmware upgrade framework for hardware boards could not be initialized

Consequences

No firmware upgrade of hardware boards will be performed

Probable causes

An invalid xml file in the controller installation:

arg


For developers:

- Correct the file. Use the hw_compatibility.xsd schema to verify.



For other users:

- Reinstall the system.

20441, Failed to initialize firmware patch

Description

Failed to initialize the firmware patch handling for hardware boards.

Consequences

No firmware patches for hardware boards will be applied

Probable causes

The firmware patch file was invalid:

arg


Correct the patch file. Use the schema hw_compatibility.xsd to verify.

20453, SC arg Wrong Sync. Position

Description

The positions of the supervised Mechanical units do not match the synchronization positions defined in the Safety Configuration for

Safety Controller (SC) arg on axis arg.


- Check that all supervised Mechanical units are positioned at the configured synchronization position.

- Check that the synchronization switch is working properly.

- Check that motor calibration and revolution counters are updated and correct.

- Check that the synchronization position in the Safety

Configuration is correct.

- Check for configuration error.

- Download Motor calibration values.

- Check if axis 4 or 6 is configured as independent, if YES, check that the EPS configuration is configured likewise.

20443, Multiple firmware upgrade restarts

Description

A new restart to firmware upgrade mode was ordered after two consecutive upgrade restarts.

Consequences

No further restart to firmware upgrade mode was performed.

Probable causes

Firmware upgrade of a hardware board has most likely failed. The board's firmware or hardware may be corrupt.


Check the event log for previous error messages.

20450, SC argCBC Speed exceeded

Description

Cyclic Brake Check (CBC) speed limit is exceeded in Safety

Controller (SC) on Mechanical unit arg, when Brake check is required


Decrease speed and execute Brake check

20454, SC arg Servo-Lag Limit exceeded

Description

Safety Controller (SC) arg detected a too big difference between the ordered and actual position, for Mechanical unit arg on axis arg.


- Check for collision.

- If using external axis, check Servo Lag settings in the Safety

Configuration.

- If using Soft Servo, Check that the Operational Safety Range

(OSR) Tolerance in the Safety Configuration is not set too low

- Verify that revolution counters are updated.

- Check for communication problems to the Main Computer, Axis

Computer or the Serial Measurement Board.

- Check if tool weight is correctly defined.

20451, SC arg Not synchronized

Description

Safety Controller (SC) arg is not synchronized with supervised

Mechanical units.


Move all Mechanical units supervised by Safety Controller arg to the synchronization positions defined in the Safety Configuration.

20455, SC arg Incorrect Position Value

Description

Incorrect position value from Serial Measurement Board detected by Safety Controller (SC) arg on Mechanical unit arg.


- Check resolver and resolver connections.

- Replace Serial Measurement Board.

- Replace resolver.

20452, SC arg Synchronized

Description

Safety Controller (SC) arg is now synchronized to supervised

Mechanical units. Safety supervision can be used.

20456, SC arg Reference Data Timeout

Description

The Robot Controller has stopped sending reference data to Safety

Controller (SC) arg.


1. Check previous error logs for possible causes.



2. Restart System.

20457, SC arg Corrupt Safety Configuration

Description

The Safety Configuration for Safety Controller (SC) arg is corrupt or contains invalid data.


- Warm start Robot Controller.

- Download a Safety Configuration to the Safety Controller.

- Reinstall System.

20462, SC arg Calibration Offset not found

Description

Failed to retrieve Motor Calibration offsets for Safety Controller

(SC) arg.


Download new Calibration offsets to the SC.

20463, SC arg Safety Configuration downloaded

Description

Download of Safety Configuration was successful for Safety


20458, SC arg Internal Failure

Description

Internal Failure in Safety Controller (SC) arg.



- Check Safety Controller health on LED

- Replace Safety Controller if remaining error

20459, SC arg Input/Output Failure

Description

I/O Error on Safety Controller (SC) arg.




Warm start Robot Controller, after performing recommended actions.

20464, SC arg OSR Limit exceeded

Description

Safety Controller (SC) arg detected a too big difference between the ordered and actual position inside Operational Safety Range (OSR)

, for Mechanical unit arg on axis arg.


- Check for collision.

- Check that Operational Safety Range (OSR) Tolerance in the Safety

Configuration is not set too low.

- Synchronize the Safety Controller, if the revolution counters have been updated since last synchronization.

20460, SC arg Safety Configuration not found

Description

Failed to retrieve Safety Configuration for Safety Controller (SC)

arg.



- Download a Safety Configuration to the SC.

- Reinstall System.

20461, SC arg Robot Configuration not found

Description

Failed to retrieve Robot Configuration for Safety Controller (SC)

arg.



- Reinstall System.

20465, SC arg SAS Speed exceeded

Description

Safe Axis Speed (SAS) violation on Mechanical unit arg Axis arg on Safety Controller (SC)


Decrease speed on Axis arg

20466, SC arg Input/Output Failure

Description

I/O Error on Safety Controller (SC) arg I/O arg Type arg

Type 1: Input

Type 2: Output

Probable causes

- Wrong connection to I/O terminals on SC

- Two channel I/O mismatch


- Check SC cabling.

- Check SC health.

Warm start Robot Controller, after performing recommended actions.



20467, SC arg STS speed exceeded

Description

Safe reduced Tool Speed (STS) in Safety Controller (SC) on

Mechanical unit arg too high. Cause arg.

Probable causes

1. Tool0 speed

2. Elbow speed

3. Tool speed

4. Additional axis speed


Reduce tool speed.

20468, SC arg STZ violation

Description

Safe Tool Zone (STZ) arg is violated on Mechanical unit arg. Cause

arg

Probable causes

1. Exceeded speed

2. Wrong tool position

3. Wrong tool orientation

4. Wrong elbow position

11. Wrong tool point 1 position









- Reduce speed

- Move Robot tool to safe position

- Adjust tool orientation


Perform synchronization before the time limit expires.

20471, SC arg Synchronization Timeout

Description

Synchronization time limit expired for Safety Controller (SC) arg.

Last synchronization was arg hours ago.


Perform synchronization.

20472, SC arg New Safety Configuration

Description

Safety Controller (SC) arg has received a new Safety

Configuration. A new PIN-code is needed to activate.


1. Log in as a user with Safety Configuration grants.

2. Enter new PIN-Code for the Safety Controller in the Control Panel.

20473, SC arg Dual Computer mismatch

Description

Safety Controller (SC) arg have had conflicting values for a Safety

Output for too long.

Consequences

The Safety Controller has entered a Safe State and issue an error after

10 minutes of internal mismatch, if recommended actions are not performed.

Probable causes

- The Mechanical unit have been parked at a position on, or close to, a supervised or monitored function limit for too long time.

- Internal computation error in Safety Controller.


Move all Mechanical units’ axes and tools well inside or outside monitored and supervised function limits.

20469, SC arg SAR violation

Description

Safe Axis Range (SAR) arg is violated on Mechanical unit arg Axis

arg


Move Mechanical unit to safe position

20470, SC arg Synchronization Pre-warning

Description

Synchronization required for Mechanical units supervised by Safety

Controller (SC) arg in less than arg hour(s).

20474, SC arg I/O Supply Failure

Description

I/O supply voltage level for Safety Controller (SC) arg is out of range.

Probable causes

Either the voltage is out of limits or the voltage is missing.


1. Connect 24V supply with correct voltage level to I/O supply terminals.

2. Warm start Robot Controller.



20475, SC arg Synchronization rejected

Description

Safety Controller (SC) arg is not correctly configured for synchronization.

Probable causes

- Safety Configuration PIN is not set or is incorrect.

- Safety Configuration is empty.

- Safety Configuration is corrupt or missing.

- Safety Controller connected to the wrong SMB bus.

- I/O Power supply missing.


Verify and check possible causes

20476, SC arg Disabled

Description

Safety Controller (SC) arg is disabled.

Consequences

All safety supervision has been disabled in the Safety Controller.

Risk for Safety hazards.


Download a Safety Configuration to the Safety Controller.

20477, SC arg SMB Communication Failure

Description

Safety Controller (SC) arg failed to communicate with Serial

Measurement Board (SMB).


1. Make sure that the cabling from SMB to Safety Controller is connected to the right SMB connector and functional.

2. Restart System.

20478, SC arg Main Supply Failure

Description

The main power supply voltage for Safety Controller (SC) arg is out of range.

Probable causes

Either the voltage is out of limit or the voltage is missing.


1. Check Safety Controller cabling.

2. Check voltage from power supply.

3. Warm start Robot Controller.

20479, SC arg Additional Axis missing

Description

An Additional Axis that is supervised by Safety Controller (SC) arg is no longer present in the System Configuration.


Reinstall the supervised Additional Axis, or Download a Safety

Configuration without supervision of the Additional Axis.

20480, SC arg SST violation

Description

Safe Stand Still (SST) arg in Safety Controller (SC) is violated on

Mechanical unit arg Axis arg.


- Verify Rapid program

- Verify process equipment

- Check that movement is not ongoing when SST is active

- Check previous elog messages

20481, SC arg OVR active

Description

Override Operation (OVR) active on Safety Controller (SC) arg

SafeMove will stop the robot after approximately 20 minutes with

OVR active.

Speed is limited to 250 mm/s or 18 degrees/s.


Deactivate signal connected to OVR input

20482, SC arg OVR time out

Description

Override Operation (OVR) has been active too long time on Safety



1. Warmstart Robot Controller 2. Toggle signal connected to

OVR input

3. Activate Confirm stop by pressing Motors On push button

4. Jog Robot back into working area

5. Deactivate signal connected to OVR input

20483, SC arg CBC soon required

Description

Cyclic Brake Check (CBC) required in less than arg hours.


Perform a Brake Check before the time limit expires.



20484, SC arg CBC Time Limit expired

Description

Cyclic Brake Check (CBC) time limit expired in Safety Controller

(SC). Last Brake Check was executed arg hours ago.


Perform a Brake Check.

20489, SC arg has been disabled

Description

Safety Controller (SC) arg has been disabled and no supervision functions are active.

Probable causes

Either a C-start has been performed or it's the first startup of SC.


Download a Configuration to SC arg.

20485, SC arg Too low brake torque

Description

Too low brake torque in Safety Controller (SC) on Mechanical unit

arg.

Probable causes

- Axis has not been tested.

- Worn out brake(s).


- Check that the failing axis is activated

- If failing axis is activated replace brake(s)as soon as possible.

20490, SC arg OVR Speed exceeded

Description

Override (OVR) Speed limit exceeded on Mechanical unit arg.

Probable causes

If Override (OVR) is active, then OVR speed limitations will be active


- Decrease speed.

- Deactivate OVR.

20486, SC arg CBC incorrect

Description

Safety Controller (SC) has detected that the last Cyclic Brake Check

(CBC) on Mechanical unit arg was incorrect.


- Perform a new Brake Check.

- Check previous elogs.

20491, SC arg Override active during startup

Description

Override digital input was active during startup on SCarg

20487, SC arg Unsynchronized speed exceeded

Description

Exceeded Axis speed when Safety Controller (SC) arg was unsynchronized.


Jog Mechanical unit to synch position with low axis speed. Reduce speed to 250 mm/s or 18 degrees/s.

20492, SC arg SST violation in Brake test

Description

Movement detected during Brake test on Safety Controller (SC)arg

Mechanical unit arg Axis arg

Probable causes

- Interrupted braketest.

- Worn out Brakes.


- Restart CBC.

- Replace Brake.

20488, SC arg Unsynchronized time limit expired

Description

Available time to move the Robot when unsynchronized has expired for Safety Controller (SC) arg.


1. Do a Confirm stop by pressing the Motors ON push button or activate System input

2. Synchronize SC arg.

20493, SC arg SBR triggered

Description

Safe Brake Ramp (SBR) on Safety Controller (SC) was interrupted by a Class 0 stop due to slow deceleration on Mechanical unit arg. This is normal and occurs in cases when a stop1 is to slow. Check for other safety controller elog.


- Change parameter value for SBR in motion configuration

- Trigger a new stop to test the Brake Ramp.

- If this happens frequently, check the Application manual for

Mechanical units configuration.



20494, SC arg Tool change incorrect

Description

Incorrect tool change with Tool arg on Mechanical unit arg


- Check if correct tool.

- Decrease speed if needed.

- Perform a new tool change.

20501, ES panel open

Description

The emergency stop panel has previously been broken, and while broken, an attempt was made to operate the robot.

Consequences


Probable causes



1) To resume operation, first reset the emergency stop panel button.



20502, ES pendant open

Description

The emergency stop pendant has previously been broken, and while broken, an attempt was made to operate the robot.

Consequences


Probable causes



1) To resume operation, first reset the emergency stop pendant button.




1) To resume operation, first reset the emergency stop external button.



20505, Delayed stop open

Description

Delayed stop open.

Consequences



1) To resume operation, first reset the delayed stop button.



20506, Test Stop open

Description

The Test Mode Safeguarded Stop circuit has been broken.

Consequences


Probable causes

One or more of the switch connected in series with the Test Mode

Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is only possible while in the Manual operational mode




20507, Hardware chain open

Description

Relays (KA16 and KA17) on Safety Interface Board (SIB) not activated.

Consequences

Motor on command rejected.


Press motor ON button to close the chain.

20503, ES ext.cat.0 open

Description

The emergency stop external has previously been broken, and while broken, an attempt was made to operate the robot.

Consequences


Probable causes


20521, Test Stop conflict

Description

Status conflict for the Test Stop chain.

Consequences





Please check the two-channel safety guard that caused the status conflict.

Consequences

Paint enable chain opens.


Check cables and connections.

20525, ES panel conflict

Description

Status conflict for the Emergency Stop panel chain.

Consequences

The system goes to status emergency stop.



20531, Delayed Stop conflict

Description

Status conflict for the delayed stop circuit.

Consequences




20526, ES pendant conflict

Description

Status conflict for the Emergency Stop pendant chain.

Consequences




20534, Mode selector conflict

Description

Any of the connections to the mode selector are faulty.

Consequences




20527, ES ext.cat.0 conflict

Description

Status conflict for the Emergency Stop ext.cat.0 chain.

Consequences




20535, AUX Interlock conflict

Description

Only one of the two AUX interlock chains was opened. Normally used on CBS door interlock.

Consequences




20528, HV Interlock input conflict

Description

Only one of the two input signals in the high voltage chains is opened.

Consequences




20536, Motor on chain conflict

Description

Only one of the two motor on chain signals in run chain is opened.

Consequences




20529, Cabin Interlock input conflict

Description

Only one of the two input signals in cabin interlock chains is opened.

20556, Enable 2 AXC 1 open

Description

Status active when enable from Axis Computer 1 open.

Consequences





1. Check other error messages for primary fault reason.

2. If no other error messages, please check line voltage for one phase missing.

20557, Enable 2 AXC 2 open

Description

Status active when enable from Axis Computer 2 open.

Consequences



1. Check other error messages for primary fault reason.

2. If no other error messages, please check line voltage for one phase missing.

20558, Manipulator fault

Description

Status active when power to manipulator arg connected to Manipulator

Interface Board (MIB) arg is lost, or manipulator's enable chain conditions is not OK.

Consequences



1. Check the power to the manipulator.

2. Check that the enable chain on Manipulator Controller Board

(MCOB) is OK.

20561, MCOB software has opened enable chain

Description

Status active when Manipulator Controller Board (MCOB) software has opened the enable chain on MCOB.

Consequences



Check the MCOB software.

20562, Reset ES fault

Description

Status active when Reset Emergency Stop input is activated for more than 3 seconds.

Consequences



1. Check the connection of external reset of Emergency Stop.

2. Check the motor on push button.

20563, Servo disconnect open

Description

Status active when Servo disconnect switch on system arg is off.

Consequences



If Servo disconnect switch is not installed, check the disable link on

Manipulator Interface Board (MIB).

20559, Collision sensor active

Description

Status active when digital collision sensor on Manipulator Controller

Board (MCOB) is active.

Consequences



Check the collision sensors connected to MCOB.

20564, Brake rel. on axes 1 & 7

Description

Status active when manual brake release on axes 1 and 7 enabled.

Consequences



Check switch for manual brake release of axes 1 and 7.

20560, Axis limit on MCOB

Description

Status active when limit sensor on Manipulator Controller Board

(MCOB) is active.

Consequences



Check the limit sensors connected to MCOB.

20565, External enable 1 open

Description

Status active when external enable 1 on Manipulator Controller Board

(MCOB) is open.

Consequences





Check connection on MCCB X25.

2. Check Pendant Interface Board (TIB) and Manipulator Interface

Board (MIB).

20566, External enable 2 open

Description

Status active when external enable 2 on Manipulator Controller Board

(MCOB) is open.

Consequences



Check connection on MCCB X43.

20571, HV Interlock open

Description

Paint system High Voltage (HV) interlock is opened by external interlock connection.

Consequences



Check manual switch for disconnecting of the HV system.

20567, Power low on MCOB

Description

Status active when power below 16V on Manipulator Controller Board

(MCOB).

Consequences



Check power on MCOB.

20572, Cabin Interlock open

Description

Cabin Interlock is opened by external interlock connection.

Consequences



Check cabin ventilation and other cabin safety functions.

20568, Hardware enable open on MCOB

Description

Status active when firmware on Manipulator Controller Board

(MCOB) has opened the enable chain.

Consequences


20569, Watchdog fault on MCOB

Description

Status active when watchdog on Manipulator Controller Board

(MCOB) fails.

Consequences


20570, TPU wiring error

Description

Status active when Process Interface Board (PIB) detects fault on emergency stop pendant and enabling device signals (glitch test).

Consequences



1. Check cables and connections to Teach Pendant Unit (TPU).

20573, Controller ID is Missing

Description

Controller ID is the controller's unique identity. It is by default equal to the serial number of the controller's cabinet. The software configuration of the controller is missing this identity information.

Probable causes

This may happen if the storage media of the controller has been replaced or reformatted.


Read the serial number of the controller from the controller cabinet to find out what the controller ID should be. Use RobotStudio tools to set this value for the controller.

20574, Process Interlock open

Description

Process Interlock is opened by external interlock connection.

Consequences



Check manual switch for disconnecting of the process system.

20575, AUX Interlock open

Description

AUX Interlock is opened by external interlock connection. Normally used for Cartridge Bell System (CBS).



Consequences



Check cables and equipments connected to AUX inputs.

20576, System 2 Interlock open

Description

System 2 Interlock is opened. Normally used for Cartridge Bell

System (CBS) or paint pumps

Consequences



Check cables and equipments connected to system 2.

20577, HV ON open

Description

High Voltage (HV) switch on operating panel is opened.

Consequences



Give acknowledge on motor ON and switch on the HV key to close the

HV interlock chain.

20583, Watchdog towards PIB software fails

Description

Status active when firmware on Process Interface Board (PIB) discover watchdog fault between PIB firmware and PIB software.

Consequences


Probable causes

Too high processor load on PIB software.

20584, Fault on internal SPI

Description

Status active when firmware on Process Interface Board (PIB) discover watchdog fault towards Safety Interface Board (SIB) and

Manipulator Interface Board (MIB).

Consequences


Probable causes

Serial Peripheral Interface (SPI) communication is down on SPI 1.


Check cables between PIB, SIB and MIB.

20581, SPI communication towards SIB is down

Description

Status active when cyclic enable 1 test fails from Safety Interface

Board (SIB).

Consequences



1. Check status on Serial Peripheral Interface (SPI) status.

2. Check cables between Process Interface Board (PIB) abd SIB.

20582, SPI communication towards MIB is down

Description

Status active when cyclic enable 1 test fails from Manipulator Interface

Board (MIB) arg.

Consequences



Check cables and Serial Peripheral Interface (SPI) status.

2. Check cables between SIB and Manipulator Interface Board (MIB).

20585, Enable chain opened from IPS

Description

Status active when enable chain is opened from signal Safety/PibSw/

Enable.

Consequences



Check the actuator connected to signal Safety/PibSw/Enable.

20586, Watchdog fault towards PIB firmware

Description

Status active when software on Process Interface Board (PIB) discover watchdog fault towards PIB firmware caused by fault on FPGA.

Consequences


20587, Watchdog fault towards PIB firmware

Description

Status active when software on Process Interface Board (PIB) discover watchdog fault towards PIB firmware caused by fault on the In-System

Micro Controller.

Consequences




Probable causes

Firmware not running.


Press motor ON button to close the chain.

20588, Watchdog fault between PIB and MC

Description

Status active when software on Process Interface Board (PIB) discover watchdog fault towards Main Computer (MC).

Consequences



Check ethernet cable between PIB and MC.

20600, Unofficial RobotWare release

Description

The current RobotWare is not an officially supported release.

Unofficial RobotWare releases may only be used for time-limited test and validation purposes.

Consequences

ABB will not provide long-term support on unofficial releases.


If this is a production system, install an official RobotWare release as soon as possible.

20589, Watchdog fault between PIB and MCOB

Description

Status active when agent connection on CAN between Process

Interface Board (PIB) and Manipulator Controller Board (MCOB) is down.

Consequences



1. Check CAN cables.

2. Check MCOB status.

20590, Open circuit mask not set

Description

The open circuit mask for brakes on Manipulator Controller Board

(MCOB) is not set. The mask should be set from Process Interface

Board (PIB) during start-up.

Consequences

This message will be given every time the brakes are released, until the open circuit mask on MCOB is set.

Probable causes

IPS configuration on PIB is not loaded or configuration file for brake settings is missing.


1. Check that IPS configuration is loaded during start-up.

2. Check that IPS configuration file for brake settings are installed on

PIB.

20591, TPU hot plug timeout

Description

The TPU hot plug button is pressed for too long time.

Consequences


20601, Too long paths when unpacking

RobotWare files

Description

The RobotWare installation package was not properly unpacked on the controller. Some files in the package have a path that is too long and could not be handled by the controller software.

During the installation process the controller software was upgraded to handle longer paths, so a re-installation of the system should solve the problem.

Consequences

Some RobotWare files are missing on the controller and your system may not be able to operate properly.


Re-install the system by using SystemBuilder. If the error is still present after the re-installation, contact customer support.

20602, Unofficial RobotWare image

Description

The current RobotWare main computer image is not the original, and is hence not officially supported.

Consequences

ABB will not provide long-term support on unofficial RobotWare releases.

Probable causes

The officially released main computer image has been replaced, e.g., for the purpose of collecting diagnostic data for a specific problem.


If this is a production system, install an official RobotWare release as soon as possible.



20610, Motor phase short circuit

Description

The drive unit for joint arg has reported short circuit. The joint is connected to drive module arg with unit position arg and node arg.

Consequences

No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque.

Probable causes

1) Short circuit in cables or connectors between the phases or to ground.

2) Short circuit in motor between the phases or to ground.


1) Check/replace cables and connectors.

2) Check/replace motor.

20620, The system has entered an internal test mode

Description

A feature to perform ABB Robotics internal tests has been enabled in arg.

Consequences

The system may not behave as expected.


Restart the system when the test has been performed. If this was an unexpected message, please contact your contact your local ABB representative for assistance.

31810, DeviceNet master/slave board is missing

Description

The DeviceNet master/slave board does not work.

Consequences

No communication on the Devicenet is possible.

Probable causes

The DeviceNet master/slave board is either malfunctioning or missing.


1. Make sure a DeviceNet master/slave board is installed.

2. Replace the board if faulty.

31811, Second DeviceNet master/slave board is missing

Description

Dual option is configured but only one DeviceNet master/slave board is installed.

Consequences

Only one DeviceNet bus is available.

Probable causes

The Second DeviceNet master/slave board is either malfunctioning or missing.


1. Make sure a Second DeviceNet master/slave board is installed.

2. Replace the Second board if faulty.

31812, Incompatible DeviceNet Boards

Description

The system has detected incompatible types of DeviceNet boards.

Consequences

No communication on the DeviceNet is possible.

Probable causes

Incompatible types of DeviceNet boards have been installed in the system.


Make sure that compatible board types are installed.

31910, Profibus-DP master/slave board is missing

Description

The Profibus-DP master/slave board does not work.

Consequences

No communication on the Profibus is possible.

Probable causes

The Profibus-DP master/slave board is either malfunctioning or missing.


1. Make sure a Profibus-DP master/slave board is installed.


31911, Profibus board update error

Description

The RobotWare software was not able to download new driver software to the Profibus-DP master/slave board. The arg channel (ch

arg) of the Profibus board could not be programmed. Internal error code:arg.

Consequences


Probable causes

The RobotWare software may be corrupt or the board hardware may be malfunctioning.




1. Restart the system to reattempt downloading the software.

2. Reinstall the present system files.

3. Create and run a new system to download the driver software.


31912, Profibus-DP master/slave board failure

Description

The Profibus-DP master/slave board did not start up correctly.

Consequences


Probable causes

The Profibus-DP master/slave board hardware may be malfunctioning.



2. Replace the Profibus-DP master/slave board if faulty.

31913, Profibus-DP master/slave board internal error

Description

The Profibus-DP master/slave board reported internal error arg.

Consequences


Probable causes





31914, Profibus startup error

Description

- Profibus master bus error Error code arg. Check cabling, terminators and modules then restart.


Duplicated profibus addresses.


Check cabling, terminators and modules.

31916, Profibus bus OK

Description

- Profibus regained contact on the master bus.


31917, Profibus-DP master/slave board exception

Description

A fatal error has occurred on the Profibus-DP master/slave board. arg channel in task arg. Parameters arg

Consequences


Probable causes





32500, Robot Communication Card is missing

Description

The system cannot contact the Robot Communication Card.

Consequences

No communication with the Safety System is possible. The system goes to status SYS FAIL.

Probable causes

The Robot Communication Card is either malfunctioning or missing.


1. Make sure a Robot Communication Card is installed.

2. Replace the unit if faulty.

31915, Profibus Bus Error

Description

Profibus master bus error.

Internal error

Error code arg.

Consequences

Certain expected associated errors may be delayed.

Probable causes

Faulty profibus cabling, terminators and/or module(s).

32501, Incorrect RCC firmware

Description

The FPGAR11-Firmware on the RCC (DSQC602) is of an incompatible version. Current version: arg.arg Requested version:

arg.arg


1. Replace the DSQC602 board

2. Restart the system



32502, Can't find file

Description

The system cannot find the file: [arg]


Reinstall the system

32503, Requested info not in file

Description

The system cannot find information about what software to download to HardWare ID="arg", Version="arg", Revision="arg" in file [arg].

Probable causes

The file has either been damaged, or the actual hardware version of the unit is not supported.


1. Reinstall the system

2. Replace the unit to a version which is supported by this SW-release.

32542, Drive unit hardware not supported

Description

In drive module arg, the system cannot use the drive unit with hardware identity arg because the hardware revision arg is not supported.

Consequences

The system is unable to use the drive unit. The system goes to System

Failure state.

Probable causes

The RobotWare version is too old to support the drive unit.


1) Upgrade the system to a RobotWare version supporting the drive unit revision.

2) Replace the drive unit to one with compatible revision.

32530, No Communication With The Safety

System

Description

There is no serial communication between the Safety System and the robot communication card.

Consequences


Probable causes

Probably hardware fault in cable between Safety System and Robot

Communication Card. The Safety System, or it's power supply, may also be faulty.


1) Restart the system to resume operation.

2) Make sure the cable between robot communication card and Safety

System is working and correctly connected.

3) Check the Safety System power supply.

4) Replace the unit if faulty.

32540, Drive unit firmware reflash started

Description

In drive module arg, a required upgrade of the firmware in the drive unit at unit position arg has started. The old firmware revision arg is replaced with revision arg.


Wait for the firmware upgrade process to complete. Do not turn off system power!

32541, Drive unit firmware reflash complete

Description

In drive module arg, the upgrade of the firmware in the drive unit with unit position arg is completed. New revision is arg.

32543, Drive unit firmware reflash failed

Description

In drive module arg, the upgrade of the firmware in the drive unit at unit position arg failed.

Consequences

The required upgrade of the drive unit firmware is not performed.


1) Check other hardware eventlog messages for detailed explanation of the error condition.

2) Try again by restart the system using the main power switch.

32544, Drive unit firmware file not found

Description

The file arg, required to upgrade a drive unit’s firmware, is not found.

Consequences


Probable causes

The RobotWare installation does not contain the firmware file.


Reinstall the system.

32545, Drive unit firmware file type error

Description

The file arg, required to upgrade a drive unit’s firmware, is of wrong type.



Consequences


Probable causes

The RobotWare installation is faulty.



32554, Firmware file not found

Description

The firmware file [arg] is not found.



32546, Drive unit firmware file error

Description

The file arg, required to upgrade a drive unit’s firmware, is not usable because it failed the integrity check.

Consequences


Probable causes

The RobotWare installation is faulty.



32550, Firmware reflash started

Description

A required update of the arg firmware has started. File used: [arg].


Wait for the reflash to complete

32555, Safety System Unit Not Supported

Description

The system cannot use the Safety System unit arg, revision arg.

Consequences

The system is unable to use the affected hardware.


1. Change the affected hardware to a compatible version.

32560, Axis computer firmware reflash started

Description

In drive module arg, a required upgrade of the firmware in the axis computer arg with hardware identity arg has started. The old firmware revision arg is replaced with revision arg.


Wait for the firmware upgrade process to complete. Do not turn off system power!

32551, Firmware reflash completed

Description

The update of arg firmware has completed successfully.

32561, Axis computer firmware reflash complete

Description

In drive module arg, the upgrade of the firmware in the axis computer

arg with hardware identity arg is completed. New revision is arg.

32552, Firmware reflash failed

Description

The update of arg firmware failed.

Internal errorcode:arg


1. Check other error messages for detailed explanation


3. Reinstall the system

4. Replace the arg

32553, Firmware file is corrupt

Description

The firmware file [arg] is corrupt. Internal errorcode:arg



32562, Axis computer communication error

Description

The system failed to communicate with the axis computer in drive module arg when trying to read firmware information.

Consequences

The system is unable to determine if an upgrade is required of the firmware in the affected drive module. The system goes to System

Failure state.

Probable causes

This may be due to a cable break, bad connector or high levels of interference in the cable between the main computer and the axis computer.


1) Make sure the cable between the main computer and the axis computer is not damaged and that both connectors are correctly connected.



2) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling.

32563, Axis computer hardware not supported

Description

In drive module arg, the system cannot use the axis computer with hardware identity arg because the hardware revision arg is not supported.

Consequences

The system is unable to use the axis computer. The system goes to

System Failure state.

Probable causes

The RobotWare version is too old to support the axis computer unit.


1) Replace the axis computer to one with compatible revision.

2) Upgrade the system to a RobotWare version supporting the axis computer revision.

32564, Axis computer firmware reflash failed

Description

In drive module arg, the upgrade of the firmware in the axis computer

arg with hardware identity arg failed.

Consequences

The required upgrade of the axis computer firmware is not performed.


1) Check other hardware eventlog messages for detailed explanation of the error condition.

2) Retry again by restarting the system using the main power switch.

Consequences

The required upgrade of the axis computer’s firmware is not performed.

Probable causes

The firmware file is corrupt.



32568, Axis computer firmware file error

Description

The file arg, required to upgrade an axis computer’s firmware, is not usable because it failed the integrity check.

Consequences


Probable causes

The firmware file is corrupt.



32569, Corrupt axis computer hardware

Description

In drive module arg, the axis computer flash memory has a corrupt content.


1. Retry again by restarting the system using the main power switch.

2. If the problem remains then replace the axis computer.

32565, Axis computer firmware file not found

Description

The file arg, required to upgrade an axis computer’s firmware, is not found.

Consequences


Probable causes

The RobotWare installation does not contain the firmware file.




Description

A required update of the arg firmware has started. Replacing old firmware version: [arg].




Description

The update of arg firmware has completed successfully. New version:

[arg]. Internal code:[arg]

32567, Axis computer firmware file type error

Description

The file arg, required to upgrade an axis computer firmware, is of wrong type.


Description

The upgrade of arg firmware failed.

Current version:arg. Internal errorcode:arg.




1. Check other hardware eventlog messages for detailed explanation of the error condition.

2. Reinstall the system.

32573, Unable to download firmware file

Description

The firmware file arg is not found. Internal error code:arg.



Consequences

The system goes to System Failure state.

Probable causes

The integrity check of the axis computer information stored on the unit has failed.



2) Replace the faulty axis computer.

32574, Corrupt axis computer hardware

Description

The arg flash memory has a corrupt content. Internal error code:arg.


1. Check other hardware eventlog messages for detailed explanation of the error condition.


3. If failure occurs again, replace the axis computer.


Description

A required update of the arg firmware has started. Internal code: [arg].

File: [arg].



32575, Found no axis computer board

Description

System failed to detect any connected axis computer.


1. Check system for axis computer board.

2. Check ethernet cables between the main computer and the axis computer.



Description

The update of arg firmware has completed successfully . Internal code:[arg]


No action required


Description


Internal errorcode:arg


1. Check other error messages for detailed explanation.


32576, Axis firmware: No communication

Description

The system failed to communicate with axis board arg when trying to check the firmware version.

Consequences

The system is unable to check and if necessary upgrade the firmware in the affected axis computer.


1. Check system for axis computer board.

2. Check ethernet cables between the main computer and the axis computer.

3. Restart system.

32583, Firmware file corrupt

Description


The firmware file [arg] is corrupt.

Internal errorcode:arg.



32577, Axis computer hardware data error

Description

In drive module arg, the axis computer has corrupt information stored on the unit.


Description



Internal errorcode:arg.





32585, No Safety System Found By Axis

Computer

Description

Axis computer failed to detect the Safety System.


1. Check communication cables between the axis computer and the

Safety System.

2. Check power supply to the Safety System.



Description

A required update of the arg firmware in drive module arg has started.

File: [arg].


Wait for the reflash to complete, this will take approximately 3.5 minutes.


Description

The update of arg firmware in drive module arg has sucessfully completed.


No action required


Description

The update of arg firmware in drive module arg has failed.


1. Check other error messages for detailed explanation.


32593, Firmware file corrupt

Description


The firmware file [arg] is corrupt.




Description





32601, Interbus master/slave board is missing

Description

The Interbus master/slave board does not work.

Consequences

No communication on the Interbus is possible.

Probable causes

The Interbus master/slave board is either malfunctioning or missing.


1) Make sure a Interbus master/slave board is installed.

2) Replace the board if faulty.

32651, Serial port hardware is not accessible

Description

The system has tried to address the serial port arg, and failed.

Consequences

The optional serial port hardware can not be accessed. The connector and the physical channel using the connector will not be available for use.

Probable causes

The serial port hardware is missing or malfunctioning.


1) Make sure the required serial port hardware has been correctly installed and is not faulty.

2) Replace the serial port hardware.

33503, Revolution counter update failure

Description

Update of the revolution counter for joint arg failed.

Consequences

Joint not synchronized

Probable causes

1. Joint missing or not active

2. Measurement system error


1. Check if joint active

2. Check configuration files

3. Check measurement system



33601, Fieldbus Adapter is missing

Description

The Fieldbus Adapter is missing.

Consequences

No communication with the Fieldbus Adapter is possible.

Probable causes

The Fieldbus Adapter is either malfunctioning or missing.


1. Make sure a Fieldbus Adapter is installed.

2. Replace the module if faulty.

34100, Drive system not supported

Description

The configured drive system in drive module arg is not of type Drive

System '04.

Consequences


Probable causes

1. Wrong drive module key used, i.e., the configuration does not match hardware.

2. Wrong hardware used in the system.


1. Reinstall the system with a drive module key that matches the hardware.

2. Replace the drive module with one that supports Drive System '04.

Consequences


Probable causes

Communication problem between drive units and the axis computer.


1) Check that all cables are properly connected.

2) Check that the drive units have logic power.

3) Check/replace Ethernet cables.

4) Check for other hardware eventlog messages.

5) Check the event log for power supply unit error messages.

6) Check the cabling between the power supply unit and the drive unit.

7) Check the 24V output from the power supply unit.

34201, Connected drive unit not configured

Description

The drive unit in drive module arg with drive unit position arg is connected but not used in the configuration.

Consequences

Operation will be possible, but the extra drive unit will not be used.

Probable causes

The drive unit is not used in the configuration.


1) Remove extra drive unit if not needed.

2) Reinstall the system with a drive module key supporting the extra drive unit.

34101, Drive system not supported

Description

The configured drive system in drive module arg is not of type Drive

System '09.

Consequences


Probable causes

1. Wrong drive module key used, i.e., the configuration does not match hardware.

2. Wrong hardware used in the system.


1. Reinstall the system with a drive module key that matches the hardware.

2. Replace the drive module with one that supports Drive System '09.

34200, Lost communication with all drive units

Description

In drive module arg, the axis computer has lost communication with all drive units.

34202, Lost communication with drive unit

Description

In drive module arg, the axis computer has lost communication with the drive unit at unit position arg.

Consequences


Probable causes

Communication problem between the drive unit and the axis computer.


1) Check that all cables are properly connected.

2) Check that the drive unit has logic power.

3) Check/replace Ethernet cables.







34203, Motor current too high

Description

The motor current is too high for joint arg, connected to drive module arg with the drive unit at unit position arg and node arg.

Consequences

No operation will be possible until the fault is corrected. The system goes to Motors Off state.

Probable causes

1) The motor configuration is incorrect.

2) The axis load may be too high or the motor may have stalled (maybe due to a collision).

3) The motor is too small for the drive unit.

4) Short circuit between motor phases or ground.


1) Check that the motor configuration is correct.

2) Check that the robot has not collided.

3) If possible, reduce the speed of the user program.

4) Check that the axis load is not too high for the motor.

5) Verify that the maximum motor current is not too small compared to the maximum current of the drive unit.

6) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring.

Probable causes

1) Incoming mains voltage loss.

2) Some malfunction in the cabling or in internal 3-phase components.

3) The rectifier unit is faulty.


1) Check the incoming mains voltage.

2) Check all the internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module.

34255, Rectifier temperature error

Description

In drive module arg, the rectifier unit at drive unit position arg has reached a too high temperature level.

Consequences

No operation will be possible until the rectifier has cooled down. The system goes to Motors Off state.

Probable causes

1) The cooling fans may be faulty or the air flow may be obstructed.

2) The ambient temperature may be too high.

3) The system may be running with a too high torque for extended periods of time.


1) Verify that the fans are running and that the air flow is not obstructed.

2) Verify that the ambient temperature does not exceed the cabinet's temperature rating.

3) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration.

4) Reduce the static torque due to gravity or external forces.

34251, Incoming mains phase missing

Description

In drive module arg, the rectifier unit at drive unit position arg has detected a power loss in one phase.

Consequences

The system may stop with DC link too low voltage.

Probable causes

1) Incoming mains voltage loss of one phase.

2) Some malfunction in cabling or internal 3-phase components.

3) The rectifier unit is faulty.


1) Check all incoming mains phases to the cabinet.

2) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module.

34252, Incoming mains missing

Description

In drive module arg, the rectifier unit at drive unit position arg has detected a mains voltage loss.

Consequences


34256, Rectifier temperature warning

Description

In drive module arg, the rectifier unit at drive unit position arg is approaching a too high temperature level.

Consequences

It is possible to continue but the margin to maximum allowed temperature is too low to sustain long term operation.

Probable causes



3) The system may be running with a too high torque for extended periods of time.








34257, Open circuit in bleeder resistor circuit

Description

In drive module arg, the bleeder resistor connected to the rectifier unit at drive unit position arg has too high resistance (open circuit).

Consequences


WARNING HIGH VOLTAGE: THE DC LINK WILL NOT BE

DISCHARGED WHEN THE SYSTEM IS POWERED OFF.

Probable causes

This may be caused by a faulty bleeder resistor cable or a faulty bleeder resistor.


WARNING HIGH VOLTAGE CAN BE PRESENT.

1) Make sure the bleeder resistor cable is properly connected to the rectifier unit.

2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms.

Consequences


Probable causes

This may be caused by a faulty rectifier inrush control relay.


Restart the system and try again. If the problem remains then replace the unit.

34262, Incoming mains frequency warning

Description

In drive module arg, the incoming mains voltage has wrong frequency. The rectifier unit at drive unit position arg has reported the problem.

Consequences

The system may stop with DC link voltage too low.

Probable causes

1) The incoming mains frequency is not within specification.



1) Check and adjust incoming mains frequency.


34258, Short circuit in bleeder resistor circuit

Description

In drive module arg, the bleeder resistor connected to the rectifier unit at drive unit position arg is indicating a short circuit.

Consequences


WARNING HIGH VOLTAGE: THE DC LINK WILL NOT BE

DISCHARGED WHEN THE SYSTEM IS POWERED OFF.

Probable causes

This may be caused by a faulty bleeder resistor cable or a faulty bleeder resistor.



1) Make sure the bleeder resistor cable is correctly connected to the rectifier unit.


3) Check for bleeder short circuit against ground.

34261, Rectifier startup error

Description

In drive module arg, the inrush control relay in the rectifier unit at drive unit positionarg indicates an error.


Description

In drive module arg, the inrush control resistor in the rectifier unit at drive unit position arg has too high resistance (open circuit).

Consequences


Probable causes

This may be caused by a faulty rectifier inrush control resistor.


Restart the system and try again. If the problem remains then replace the unit.

34264, Rectifier inrush limitation active in

Motors On

Description

In drive module arg, the inrush control resistor in the rectifier unit at drive unit position arg is wrongly engaged.

Consequences

The system goes to Motors Off state to protect the hardware.



Probable causes

This error occur when the DC link voltage becomes too low and all mains phases are missing.


1) Check the hardware eventlog for other errors.

2) Check incoming mains voltage.

3) Check that the correct voltage is selected with jumpers on the transformer (optional).


34265, DC link short circuit error

Description

In drive module arg, the DC link in the rectifier unit at drive unit position arg is short circuit.

Consequences


Probable causes

1) DC link cables for an additional drive unit is damaged or wrongly connected.

2) Internal error in rectifier unit or drive unit.


Check DC link cables and connectors.

34266, Rectifier inrush limitation and bleeder active

Description

In drive module arg, with rectifier unit at drive unit position arg, the inrush control resistor is active at the same time as the bleeder resistor is active.

The inrush control resistor is located in the rectifier unit.

The bleeder resistor is connected to the rectifier unit or the drive unit with embedded rectifier.

Consequences

The system goes to Motors Off state to protect the hardware.

Probable causes

This problem is most likely to occur when the incoming mains voltage is too high to the rectifier.


1) Check that the incoming mains voltage is according to specification for the drive unit.


34267, Too many rectifiers connected

Description

In drive module arg the system has detected more rectifers than the system can handle. The limit was reached when drive unit at unit position arg was detected.

Consequences

No operation will be possible until the fault is corrected. The system goes to System Failure state.

Probable causes

1) Too many drive unit that are equippted with rectifiers are connected.

2)


1) Verify that the proper drive units types are connected to the drive unit communication link.

2) Disconnect unused drive unit(s).

34300, Unknown drive unit type

Description

In drive module arg, the drive unit at unit position arg has an unknown hardware identity arg.

Consequences


Probable causes

The drive unit is either unsupported or faulty.


1) Verify that the drive unit is supported by the RobotWare version. Upgrade RobotWare if needed.

2) Replace drive unit.

34303, Motor current warning

Description

For joint arg, the current controller detected a too large torque current deviation for the motor. The joint is connected to drive module

arg in the drive unit at unit position arg and node arg.

Consequences

Operation will be possible but system is close to a stopping error.

Probable causes

1) The motor data in the configuration files may be wrong.

2) The motor cables are not correctly connected or damaged.

3) Short circuit in motor cable between phase to phase or phase to ground.

4) The DC link voltage may be too low.

5) The incoming mains voltage is not within specification.




1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble

Shooting Manual.

2) Verify that the motor cables are not damaged or badly connected.

3) Verify that the motor cables has no short circuits internally or to ground.

4) Verify that no DC link errors are present in the event log.

5) Verify that the incoming mains voltage is within the specification.



2) Clean the cooling fins.





Description

For joint arg, the current controller detected a too large current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg.

Consequences


Probable causes








Shooting Manual.





34307, Drive unit temperature warning

Description

The drive unit for joint arg is approaching a too high temperature level. The joint is connected to drive module arg with the drive unit at unit position arg and node arg.

Consequences


Probable causes


2) The cooling fins are covered by dust reducing the cooling effect.


4) The joint may be running with a too high torque for extended periods of time.







34306, Drive unit temperature error

Description

The drive unit for joint arg has reached a too high temperature level.

The joint is connected to drive module arg with the drive unit at unit position arg and node arg.

Consequences


Probable causes





34308, Drive unit critical temperature error

Description

The drive unit for joint arg has reached a critical high temperature level. The joint is connected to drive module arg with the drive unit at unit position arg and node arg.

Consequences


Probable causes













34309, Drive transistor current too high

Description

The drive unit transistor current is too high for joint arg. The joint is connected to drive module arg with the drive unit at unit position arg and node arg.

Consequences


Probable causes

1) The motor configuration is incorrect.

2) The axis load may be too high or the motor may have stalled (maybe due to a collision).



1) Check that the motor configuration is correct.



4) Check that the axis load is not too high for the drive unit.


34311, Drive inverter saturated warning

Description

The drive unit for joint arg has reached maximum output voltage.


Consequences


Probable causes

1) The motor is not properly connected to the drive unit.

2) The motor data in the configuration is not correct.

3) The DC link voltage is too low.



1) Check motor cables and connectors.

2) Check configuration of motor parameters.


4) Check incoming mains voltage to the rectifier unit.


34312, Missing drive unit

Description

For joint arg, the system cannot find configured drive unit. The joint is configured for drive module arg, in the drive unit at unit position arg.

Consequences


Probable causes

A joint is configured but drive unit is not found.


1) Verify that the drive module contains the drive unit for the configured joint.

2) Verify that the configuration for the drive unit position is correct.

3) Verify that the cables between drive units are correctly inserted in the correct connector position.

4) If the cable is correctly connected, then it may be damaged and should be replaced.




34313, Wrong type of drive unit

Description

In drive module arg, the hardware identity for drive unit at unit position arg is different from the one specified in the configuration.

Installed drive unit hardware identity is arg, and the configured identity is arg.

Consequences


Probable causes

The drive unit type does not match the one specified in the installation key.


1) Verify that the drive unit positions are correct, i.e., the Ethernet cables are correctly connected.

2) Verify that the drive module key match the installed hardware.

3) Replace the drive unit with the one specified in the drive module key.

34314, Missing drive unit node

Description

For joint arg, the drive unit does not support the node number configured. The joint is configured for drive module arg, in the drive unit at unit position arg with node arg.



Consequences


Probable causes

The configured drive unit node is not supported for the configured type of drive unit.


Check the drive unit node number in the configuration.



Shooting Manual.





34316, Motor current error

Description

For joint arg, the current controller detected a too large torque current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg.

Consequences

The system goes to Motors Off state.

Probable causes








Shooting Manual.





34317, Motor current error

Description

For joint arg, the current controller detected a too large current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg.

Consequences

The system goes to Motors Off state.

Probable causes






34318, Drive inverter saturated error

Description

The drive unit for joint arg has reached maximum output voltage. The joint is connected to drive module arg with the drive unit at unit position arg and node arg.

Consequences

The system goes to Motors Off state

Probable causes

1) The motor is not properly connected to the drive unit.

2) The motor data in the configuration is not correct.

3) The DC link voltage is too low.



1) Check motor cables and connectors.

2) Check configuration of motor parameters.


4) Check incoming mains voltage to the rectifier unit.


34319, Drive unit critical error

Description

The drive unit for joint arg gives an unspecified error, but is likely due to over temperature or short circuit. The joint is connected to drive module arg with the drive unit at unit position arg and node arg.

Consequences


Probable causes





5) Short circuit in cables or connectors between the phases or to ground.

6) Short circuit in motor between the phases or to ground.









6) Check/replace cables and connectors.

7) Check/replace motor.

34320, Too many drive nodes connected

Description

In drive module arg the system has detected more drive nodes than the system can handle. The limit was reached when drive unit at unit position arg was detected.

Consequences


Probable causes

1) Too many drive units is connected to the drive unit communication link.

2) Too many drive unit that are equippted with many drive nodes are connected.


1) Verify that the proper drive units types are connected to the drive unit communication link.


34400, DC link voltage too high

Description

In drive module arg, the drive unit at unit position arg has a DC link voltage that is too high.

Consequences


WARNING HIGH VOLTAGE: THE DC LINK MAY BE

DISCHARGED VERY SLOWLY (APPROXIMATELY 1 HOUR)

WHEN THE SYSTEM IS POWERED OFF.

Probable causes

1) The bleeder resistor is not connected or faulty.

2) The user program may contain too much deceleration of the manipulator's axes. This fault is more likely if the system contains additional axes.





3) Rewrite the user program to reduce the amount of hard decelerations.

34401, DC link voltage too low warning

Description

In drive module arg, the drive unit at unit position arg has a DC link voltage that is close to minimum limit.

Consequences

Operation will be possible but the system is close to a stopping error.

Probable causes

The incoming mains voltage to the rectifier unit is out of specification.


1) Check for other hardware eventlog messages regarding mains voltage problem.




34402, DC link voltage too low

Description

In drive module arg, the DC link voltage is too low for the drive unit at unit position arg.

Consequences


Probable causes

The incoming mains voltage to the rectifier unit is out of specification.


1) Check for other hardware eventlog messages regarding mains voltage problem.




34404, DC link voltage is critically high

Description

In drive module arg, the drive unit at unit position arg has a DC link voltage that is critically high.

Consequences







Probable causes












34407, Drive unit internal error

Description

In drive module arg, the drive unit at unit position arg has indicated an internal error.

Consequences

The system goes to System Failure state with zero torque.

Probable causes

An internal error has occurred in the drive unit firmware.


Restart the system by using the main power switch.

34405, DC link voltage too high warning

Description

In drive module arg, the drive unit at unit position arg has a DC link voltage that is close to maximum limit.

Consequences

Operation will be possible but the system is close to a stopping error.




Probable causes








34406, Drive unit power supply error

Description

In drive module arg, the drive unit with unit position arg has detected problem with the logic power.

Consequences


Probable causes

The 24V logic supply to the drive is temporary or constantly lost.

34408, Drive unit hardware data error

Description

In drive module arg, the drive unit at unit position arg has corrupt information stored on the unit.

Consequences


Probable causes

The integrity check of the drive unit information stored on the drive unit has failed.



2) Replace the faulty drive unit.

34409, Drive unit startup error

Description

The system has failed to complete the initialization phase of a drive unit. The drive unit is located in drive module arg at unit position arg.

Consequences


Probable causes

The system has failed to complete the initialization phase of the drive unit.


1) Retry by restarting the system using the main power switch.




34410, Too many drive units connected

Description

In drive module arg the system has detected more drive units than the system can handle. The maximum number of drive units supported is

arg, but arg was detected.

Consequences


Probable causes

1) Too many drive unit that are connected.




1) Check all loads connected to the AC_ON and SPEED circuits

2) Check the Safety System cabling and connectors, and replace any faulty unit if required.

37044, Overload on Panel Board digital output signals

Description

The Panel Board User Digital outputs draw too much current.

Consequences

The Panel Board shuts down the signals, causing the system to go to status SYS HALT.

Probable causes

A load connected to the circuit may be too high, or the Panel Board may be malfunctioning. See the Circuit Diagram!


1) Check all loads connected to the User Digital outputs

2) Check the Panel Board cabling and connectors, and replace any faulty unit if required.

37001, Motors ON contactor activation error

Description

Motors ON contactor arg in drive module arg failed to close when ordered.

Consequences

The mechanical unit can not be run manually or automatically.

Probable causes

1) The runchain for the contactor is open.

2) There are problems in the contactor itself, either mechanical or electrical.

3) The teach pendant enabling device may have been toggled too quickly, or the system may not be configured correctly. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log.


1) To resume normal operation, first acknowledge the error, then release the enabling device and press it again after approx. one second.

2) Check cables and connections on the Safety System.

3) Check any other error log messages coinciding in time with this one for clues.

4) Check the system motion configuration regarding Motors ON relay.

How to check the configuration file is detailed in the Trouble Shooting

Manual.

37045, Faulty External Computer fan

Description

The External Computer fan in the Control Module spins too slowly.

Consequences

No system consequence. The Control Module temperature will rise.

Probable causes

Faulty fan, cabling or power supply. See the Circuit Diagram!


1) Check the cabling to the External Computer fan.

2) Check the fan, and replace any faulty unit if required.

37043, Safety signals overloaded

Description

The AC_ON or SPEED signals draw too much current.

Consequences

The Safety System shuts down the signals, causing the system to go to either status SYS FAIL (for AC_ON) or status SYS HALT (for

SPEED).

Probable causes

A load connected to the circuit may be too high, or the Safety System may be malfunctioning. See the Circuit Diagram!

37046, Safety signals overloaded

Description

The 24 V PANEL supply draws too much current.

Consequences

The Safety System shuts down the signal, causing the system to go to status SYS HALT.

Probable causes

A load connected to the circuit may be too high, or the Safety System unit may be malfunctioning. See the Circuit Diagram!


1) Check all loads connected to the 24V PANEL circuit.

2) Check cabling on the Safety System.



37049, Activation contactor activation error

Description

The activation relay for mechanical unit arg failed to close.

Consequences

The mechanical unit can not be run manually or automatically.

Probable causes

The activation relay configured within the system may be faulty, or the system may not be configured correctly.


1) Check the contactor and make sure its connections are connected correctly.

2) Check the system motion configuration regarding the activation relay. How to check the configuration file is detailed in the Trouble

Shooting Manual.

Probable causes



1) Check the cabling to the Computer Unit fan.

2) Check the fan.

3) Check the fan power supply.

4) Replace the faulty component if required.

37056, Cooling fan error

Description

Cooling unit fan has stopped or is rotating very slowly (Less than arg rpm).


1. Check the fan cables.

2. Replace the fan.

37050, Overtemperature in main computer

Description

The temperature in the main computer unit or the main computer processor is too high.

Consequences

The system might get damaged.

Probable causes

The unit may be overloaded, its fans may be malfunctioning or the air flow may be restricted.


1) Make sure the fans are operating.

2) Check that air flow to the unit fans is not restricted.

37062, Computer Module power supply warning

Description

The arg V voltage of the Computer Module power supply is arg V, which is out of the allowed range.

Consequences

-

Probable causes

The power supply unit, cabling, input voltage to the power supply or the output load may cause the faulty voltage level. See the Trouble

Shooting Manual and Circuit Diagram!


1) Check all cabling to the power supply unit.

2) Measure the output and input voltage levels.

3) Replace the faulty unit if required.

37053, Low CMOS battery voltage level

Description

The CMOS battery on the computer board is empty.

Consequences

On restart, the system will use an erroneous setup or no restart will be possible.

Probable causes

Faulty battery.


1. Replace the CMOS battery

37054, Faulty Computer Unit fan

Description

The fans in the Computer Unit spin too slowly.

Consequences

No system consequence. The Computer Unit temperature will rise.

37069, Faulty backup Power Supply

Description

The backup energy bank in the Control Module supplying the backup voltage is faulty.

Consequences

After switching the power off, a B type restart must be performed. No system data changes will be saved at power off.

Probable causes

This may be caused by a faulty backup energy bank, cabling or charger.


Do not turn the main power off until battery has been charged, or the system may perform a cold start!

1) Check the backup energy bank cabling and connectors.

2) Check the backup energy bank.

3) Check the power supply.





Check the purge unit and the air supply.

37070, Overtemp in Control Module Power

Supply

Description

The temperature in the control module power supply is too high.

Consequences

The system is shut down immediately.

Probable causes

This may be caused by poor cooling, too high a load on the power supply or by a faulty power supply.


1) Check the cooling fan.

2) Check the output power.

3) Replace any faulty unit if required.

37078, Purge timers differ

Description

Unacceptable divergence between Process Interface Board (PIB) and

Manipulator Interface Board (MIB) arg purge timers.

Consequences

The purge timer will be restarted.


1. Check Serial Peripheral Interface (SPI) cables.

2. Replace MIB if faulty.

3. Replace PIB if faulty.

37074, Purge pressure too low

Description

Purge system number arg assosiated with Manipulator Interface Board

(MIB) arg.


Check the purge air supply and search for leaks in:

1. The purge unit.

2. The flexible hose conduit.

3. The manipulator itself.

37080, Purge configuration not valid.

Description

The Purge Time Key on Manipulator Interface Board (MIB) arg X19 is not valid.

Consequences

Default time (300s) is used.

Probable causes

Faulty or missing Purge Time Key.


1. Check that the Purge Time Key is correctly mounted.

2. Replace Purge Time Key.

37075, Purge pressure too high

Description


(MIB) arg.


Check the purge unit and the air supply.

37081, Purge timers differ

Description

Unacceptable divergence between CPLD and FPGA firmware on

Manipulator Interface Board (MIB) arg purge timers.

Consequences

The purge timer will be restarted.


Replace MIB if faulty.

37076, Unexpected low purge flow

Description


(MIB) arg.


Check the purge unit and the air supply. Search for leaks in the purge system.

37077, Unexpected high purge flow

Description


(MIB) arg.

37082, Divergence between PIB and MIB outputs

Description

Process Interface Board (PIB) and Manipulator Interface Board (MIB)

arg are not agreed concerned to output status for purge relay and power relay.

Consequences

Purge sequence is restarted.



37090, Temp. too high, sensor arg

Description

System overheat detected. Sensors 1-7: motor 1-7, sensor 8: Serial measurement board. Run chain has been opened.


37098, Brake open circuit fault

Description

The supervision of brakes on Manipulator Controller Board (MCOB/

MCB) has detected an open circuit on axis arg and turned ON all brakes.


1. Check for open circuit on brakes.

37094, Activate connection error

Description

Could not activate arg. Connection relay input arg indicates no connection.


1. Check that if mechanical unit is connected.

2. Check the connection relay input signal setup.

37099, Temp. too high, sensor arg

Description

System overheat detected on motors, Serial measurement unit (SMU) or process equipment. Run chain has been opened.


Sensors 1-8: Robot motors 1-8

Sensor 9: SMU

Sensors 10-14: Process 1-5

Please refer to current robot config. for more details.

37095, Brake power fault

Description

The supervision of brake power on Manipulator Controller Board

(MCOB) has detected fault on the power signal and turned ON all brakes.


1. Check brake power on MCOB.

2. Check brake power relay in cabinet.

3. Check for disturbances on the brake power signal on MCOB/MCB.

4. Check for short circuit on brakes.

37100, I/O node flash disk error

Description

Flash name: arg

Flash disk function: arg

Error description: arg


Report error.

37096, Brake power fault

Description

The supervision of brake power on Manipulator Controller Board

(MCOB/MCB) has detected fault on the power signal and turned ON all brakes.


1. Check brake power on MCOB/MCB.

2. Check brake power relay in cabinet.

3. Check for disturbances on the brake power signal on MCOB/MCB.

37097, Brake short circuit fault

Description

The supervision of brakes on Manipulator Controller Board (MCOB/

MCB) has detected a short circuit on axis arg and turned ON all brakes.


1. Check for short circuit on brakes.

37101, Brake Failure

Description

The brakes for mechanical unit arg fail to engage.

Consequences

The mechanical unit may collapse when the motors are turned off.

Probable causes

The configuration of brake relay may be incorrect, or the brake relay may be faulty If an external brake relay is being used, the relay must be correctly defined in the motion configuration file.


1) Check that the external brake relay (if used) is correctly defined in the configuration file.

2) Check that the corresponding I/O signal is correctly defined in the

I/O configuration file. How to check the configuration files is detailed in the Trouble Shooting Manual.



37102, Power supply warning, faulty 24V COOL level

Description

The 24V COOL output of the Control Module Power Supply is out of range.

Consequences

No system consequence.

Probable causes

The Control Module Power Supply unit cabling or the output load may cause the faulty voltage level. The power supplies are shown in the

Trouble Shooting Manual and the Circuit Diagram!


1) Check all cabling to the Control Module Power Supply unit.

2) Check the output voltage level, and replace any faulty unit if required.

37103, Power supply warning, faulty 24V SYS level

Description

The 24V SYS output of the Control Module Power Supply is out of range.

Consequences

No system consequence.

Probable causes

The Control Module Power Supply unit, cabling or the output load may cause the faulty voltage level. The power supplies are shown in the Trouble Shooting Manual and the Circuit Diagram!


1) Check all cabling to the Control Module Power Supply unit.

2) Check the output voltage level, and replace any faulty unit if required.

37104, There is no backup voltage available!

Description

The backup energy bank maintaining the backup voltage is not functional.

Consequences

After switching the power off, a B type restart must be performed. No system data changes will be saved at power off.

Probable causes



Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved.

1) Check the cables and connectors of the backup energy bank.




37105, Regained communication with Power

Supply

Description

The main computer has regained communication with the Control

Module Power Supply.

37106, Low backup energy bank voltage level

Description

The voltage in the computer unit backup energy bank is too low to be functional.

Consequences

No system consequence. No system data changes will be saved at power off.

Probable causes




1) Check the cables and connectors of the backup energy bank.




37107, Faulty backup energy bank

Description

The backup energy bank in the Control Module maintaining the backup voltage is not functional.

Consequences

If switching the power off, a B type restart must be performed. No backup will be made at power off.

Probable causes




1) Check the backup energy bank cable and connector.





37108, Lost communication: Power Supply and

Computer

Description

The main computer has lost communication with the Control Module

Power Supply.

Consequences

The main computer cannot retrieve status info or switch the power supply off. No system data changes will be saved at power off.

Probable causes

The USB cable from the main computer to the Control Module Power

Supply may be faulty or disconnected, or the power supply may be faulty.



1) Check the cabling and connectors to the Control Module Power

Supply.

2) Check the power supply unit, and replace any faulty unit if required.

37200, Power fault: Emergency Stop supply

Description

Power fault on 24V Emergency Stop supply. Feedback from Safety

Interface Board (SIB).

Consequences



1. Check cables and connections.

2. Check power supply.

37201, Power fault: 24V Failsafe supply

Description

Power fault on 24V Failsafe supply. Feedback from Safety Interface

Board (SIB).

Consequences





37202, Power fault: 24V I/O supply

Description

Power fault on 24V I/O supply. Feedback from Safety Interface Board

(SIB).

Consequences





37203, Power fault: 24V SYS supply

Description

Power fault reported when 24V SYS < 18V. Feedback from

Manipulator Interface Board (MIB) arg.

Consequences





37204, Power fault: 24V I/O supply

Description

Power fault reported when 24V I/O < 18V. Feedback from Manipulator

Interface Board (MIB) arg.

Consequences





37205, Power fault: 12V Purge supply

Description

Power fault reported when 12V Purge < 10.8V. Feedback from


Consequences





37206, Power fault: 12V TPU supply

Description

Power fault on 12V Teach Pendant Unit (TPU) supply. Feedback from

Pendant Interface Board (TIB).

Consequences







37207, Battery charge low.

Description

Less than 2 months until the battery backup to Serial Measurement

Board (SMB) is discharged. Counting from first time this message was displayed. The battery is mounted on Manipulator Interface Board

(MIB).


Replace battery mounted on MIB.

37211, Fault on contactor KM2

Description

A fault is observed on motor contactor KM2.

Consequences




2. Check contactor.

37208, Overtemperature in transformer

Description

The temperature in the transformer is too high.

Consequences


Probable causes






Description


Consequences




2. Check contactor.

37209, Overtemperature in cabinet

Description

The temperature in the cabinet is too high.

Consequences


Probable causes






Description


Consequences




2. Check contactor.


Description


Consequences




2. Check contactor.

37214, Run chain 1 feedback conflict

Description

Safety Interface Board (SIB) and Manipulator Interface Board (MIB)

arg reports divergence on Run chain 1 feedback signals.

Consequences




2. Replace SIB if faulty.


37215, Run chain 2 feedback conflict

Description


arg reports divergence on Run chain 2 feedback signals.



Consequences






Consequences






37216, Brake chain 1 feedback conflict

Description


arg reports divergence on Brake chain 1 feedback signals.

Consequences






37220, HV Interlock chain 1 feedback conflict

Description


arg reports divergence on High Voltage (HV) Interlock chain 1 feedback signals.

Consequences






37217, Brake chain 2 feedback conflict

Description


arg reports divergence on Brake chain 2 feedback signals.

Consequences






37221, HV Interlock chain 2 feedback conflict

Description


arg reports divergence on High Voltage (HV) Interlock chain 2 feedback signals.

Consequences






37218, Cabin Interlock chain 1 feedback conflict

Description


arg reports divergence on Cabin Interlock chain 1 feedback signals.

Consequences






37219, Cabin Interlock chain 2 feedback conflict

Description


arg reports divergence on Cabin Interlock chain 2 feedback signals.

37222, System 2 Interlock chain feedback conflict

Description


arg reports divergence on System 2 Interlock chain feedback signals.

Consequences








37223, Main relay chain feedback conflict

Description


arg reports divergence on Main relay chain feedback signals.

Consequences






37227, HV Interlock chain 2 conflict

Description

Divergence on High Voltage (HV) Interlock chain 2 between input and output signals on Safety Interface Board (SIB).

Consequences





37224, Cabin Interlock chain 1 conflict

Description

Divergence on Cabin Interlock chain 1 between input and output signals on Safety Interface Board (SIB).

Consequences





37228, Cabin Interlock chain conflict from SIB

Description

Only one of the two Cabin Interlock chains is opened. Reported from

Safety Interface Board (SIB).

Consequences



Replace SIB if faulty.

37225, Cabin Interlock chain 2 conflict

Description

Divergence on Cabin Interlock chain 2 between input and output signals on Safety Interface Board (SIB).

Consequences





37229, HV Interlock chain conflict from SIB

Description

Only one of the two High Voltage (HV) Interlock chains is opened.

Reported from Safety Interface Board (SIB).

Consequences




37226, HV Interlock chain 1 conflict

Description

Divergence on High Voltage (HV) Interlock chain 1 between input and output signals on Safety Interface Board (SIB).

Consequences





37230, Brake Performance Warning

Description

The Cyclic Brake Check indicates that the brake for the mechanical unit arg axis no arg has not full braking torque.

Consequences

This is only a warning and no immediate action need to be taken.

37231, Brake Performance Error

Description

The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg has too low braking torque.

This brake will not be approved by the Safety Controller for Drive

Module no arg.

Consequences

WARNING: The brake performance is too low for this axis.



Until the brake has approved braking torque, it is only possible to move the robot with the specified "Reduced max speed (mm/s)" according to the setup in the Configurator for Cylic Brake Check.


1) Run the Cycle Brake Check once more.

2) Exchange the motor with its brake.

37232, Cyclic Brake Check Configuration Error

Description

The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg has no defined brake torque requirement level.

Consequences

The Cyclic Brake Check will continue but no valid brake check will be done for this axis.

Probable causes

The motion configuration data are not correct specified for this axis.


The motion configuration data are not correct specified for this axis:

1) Specify a value for parameter max_static_arm_torque if axis shell be tested.

2) Deactivate Cyclic Brake Check in motion configuration if axis not to be tested.



37241, HV Interlock chain conflict from MIB

Description

Only one of the two High Voltage (HV) chains is opened. Reported from Manipulator Interface Board (MIB) arg.

Consequences




37242, Run chain conflict from SIB

Description

Only one of the two run chain feedback signals from Safety Interface

Board (SIB) was opened.

Consequences




37233, Cyclic Brake Check Configuration Error

Description

The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg should be tested according to the configuration.

But the actual mechanical unit can not be included in the Safety

Controller, because activation/deactivation at runtime is allowed.

Consequences

The Cyclic Brake Check will continue with other mechanical units.

Probable causes

The motion configuration data are not correct specified for this axis.


The motion configuration data are not correct specified for this axis:

1) Cyclic Brake Check has been specified but should not be done for this axis

2) The mechanical unit must be active at startup and deactivation must not be allowed

37243, Brake chain conflict from SIB

Description

Only one of the two brake chain signals from Safety Interface Board

(SIB) was opened.

Consequences




37244, Run chain conflict from MIB arg

Description

Only one of the two run chain feedback signals from Manipulator

Interface Board (MIB) was opened.

Consequences




37240, Cabin Interlock chain conflict from MIB

Description

Only one of the two cabin interlock chains is opened. Reported from


Consequences


37245, Brake chain conflict from MIB arg

Description

Only one of the two brake chain feedback signals from Manipulator

Interface Board (MIB) was opened.



Consequences




37246, Emergency Stop relay conflict

Description

Only one of the two Emergency Stop chains was opened internal on

Safety Interface Board (SIB).

Consequences



1. Press emergency stop and reset emergency stop once again.


37501, Filesystem unknown: USB Device

Description

The filesystem type on the USB device with logical unit arg is not supported.

Consequences

The USB device with the logical unit arg cannot be accessed. The filesystem is of type arg. The file(s) on the USB device with logical number arg will not be accessible.

Probable causes

The filesystem is formatted with an unsupported file system type.


Format the USB device with the FAT32 filesystem.

37247, Circulation Fan arg malfunction

Description

Circulation fan for the drive systems at the cabinet rear side has stopped or is rotating very slowly.

Consequences

The drive systems temperature will rise.

Probable causes




2. Check the power supply.

3. Check the fan.

37502, Mass storage device removed

Description

The mass storage device was removed.

Consequences

The system goes to sys fail. The filesystem on the mass storage device could be corrupt. The file(s) on the mass storage device could be corrupt. The file(s) on the mass storage device will not be accessible.

Probable causes

The mass storage device was removed or there was a malfunction of the mass storage device.


Check that the mass storage device firmly is in place. If the problem persists, try with another device.

37248, Circulation Fan arg malfunction

Description

Circulation fan in the cabinet front door has stopped or is rotating very slowly.

Consequences

The temperature in the cabinet will rise.

Probable causes




2. Check the power supply.

3. Check the fan.

38100, Configuration failure

Description

Drive Module has detected configuration failure at measurement link.

Drive module: arg

Measurement link: arg

Board node: arg


- Check configuration for measurement link.

- Check configuration for measurement board.

- Check configuration for measurement nodes.

38101, SMB Communication Failure

Description

A transmission failure has been detected between the axis computer and the serial measurement board on measurement link arg in Drive

Module arg.

Consequences

The system goes to status SYS FAIL and loses its calibration information.



Probable causes

This may be caused by bad connections or cables (screening), especially if non-ABB cables are used for additional axes. Possible causes are also faulty serial measurement board or axis computer.


1) Reset the robot's revolution counters as detailed in the robot Product

Manual.

2) Make sure the cable between serial measurement board and axis computer is connected correctly, and that it meets the specification set by ABB.

3) Make sure the cable screen is correctly connected at both ends.


5) Make sure the serial measurement board and axis computer are fully functional. Replace any faulty unit.



Manual.

2) Make sure the cable between serial measurement board and axis computer is connected correctly, and that it meets the specification set by ABB.

3) Make sure the cable screen is correctly connected at both ends.


5) Make sure the serial measurement board and axis computer are fully functional. Replace any faulty unit.

38102, Internal failure

Description

The measurement system has detected a hardware or software fault on measurement link arg in Drive Module arg.

Consequences

The system goes to status SYS HALT and loses its calibration information.

Probable causes

This may be caused by some temporary disturbance in the robot cell or by a faulty axis computer.


1) Restart the system.


Manual.


4) Make sure the axis computer is fully functional. Replace any faulty unit.

38103, Lost communication with the SMB

Description

The communication has been lost between the axis computer and the serial measurement board on measurement link arg in Drive Module

arg.

Consequences

The system goes to status SYS HALT and loses its calibration information.

Probable causes

This may be caused by bad connections or cables (screening), especially if non-ABB cables are used for additional axes. Possible causes are also faulty serial measurement board or axis computer.

38104, Overspeed During Teach Mode

Description

One or more axes of the robot connected to drive module arg has exceeded the maximum speed for teach mode operation.

Consequences


Probable causes

The robot may have been moved manually while in state Motors OFF.

The error may also be caused by a misadjustment in the relation, commutation, between motor shaft and resolver on an additional axis, primarily during installation.


1) Press the Enabling Device to attempt resuming operation.

2) Check other event log messages occuring at the same time to determine the actual cause.

3) Perform a re-commutation of the motor at hand. How to do this is specified in the Additional Axes Manual.

38105, Data not found.

Description

Configuration data for measurement board not found.

System will use default data.

Drive module: arg


Board node: arg


Check configuration.

38200, Battery backup lost

Description

The battery backup to serial measurement board (SMB) arg in the robot connected to drive module arg on measurement link arg has been lost.

Consequences

When the SMB battery power supply is interrupted, the robot will lose the revolution counter data. This warning will also repeatedly be logged.



Probable causes

This may be due to an SMB battery that is discharged or not connected.

For some robot models, the SMB battery power is supplied through a jumper in the robot signal cable (refer to the IRC5 Circuit Diagram), and disconnecting the cable interrupts the battery power supply. Some earlier robot versions used rechargeable batteries, and these must be charged for at least 18 hrs before working correctly.


1) Make sure a charged SMB battery is connected to the board.

2) NOTE! Disconnecting the robot signal cable may disconnect the

SMB battery power supply, triggering the battery warning to be logged.

3) Reset the battery power warning by updating the revolution counters as detailed in the Calibration or Product Manual.

4) Replace the battery if discharged.

38205, SMB Linearity Error

Description

Linearity error for X-Y signal difference at Serial Measurement Board.

System may still operate with warning.

System will not function with error.

Drive module: arg


Measurement board: arg



38201, Serial Board not found

Description

Serial Measurement Board not found on measurement link.

Drive module: arg




- Check system configuration parameters.

- Check connections and cables to Serial Measurement Board.


38203, SMB offset X error

Description

Offset error for X signal at Serial Measurement Board.

Drive module: arg





38206, SMB Linearity X Error

Description

Linearity error for X signal on Serial Measurement Board.

Drive module: arg





38207, SMB Linearity Y Error

Description

Linearity error for Y signal at Serial Measurement Board.

Drive module: arg





38204, SMB offset Y error

Description

Offset error for Y signal at Serial Measurement Board.

Drive module: arg




- Replace Serial Measurement Board

38208, Resolver error

Description

Too high voltage from X or Y resolver signals.

Sum of squared X and Y exceeds max.

Joint: arg

Drive module: arg



Board node: arg




- Replace resolver.



38209, Resolver error

Description

Too low voltage from X or Y resolver signals.

Sum of squared X and Y too low.

Joint: arg

Drive module: arg



Board node: arg




- Replace resolver.

38210, Transmission fault.

Description

Serial Measurement Board SMS communication failed.

Status: arg

Drive module: arg



Board node: arg


- Restart system.

- Check cable and connectors for SMB communication.

- Replace the Serial Measurement Board.

38211, Functionality error.

Description

The Serial Measurement Board does not support 7 axes.

Drive module: arg




- Check configurations of the 7th axis.

- Replace Serial Measurement Board to a board with 7 axes functionality.

38212, Data not found.

Description

Configuration data for Serial Measurement Board not found. System will use default data.

Drive module: arg




- Check configuration.

38213, Battery charge low.

Description

Less than 2 months until battery on Serial Measurement Board is discharged. Counting from first time this message was displayed.

Drive module: arg




- Replace battery on serial measurement.

38214, Battery failure.

Description

Transportation shut down of battery failed. The battery will still be in normal mode.

Drive module: arg




- Retry shut down.

- Replace serial measurement board.

38215, Battery supervision failure.

Description

Failure occurred during reset of battery supervision circuit in Serial

Measurement Board.

Drive module: arg




- Repete update of revolution counter for joint connected to the SMB.

- Replace serial measurement board.

38230, PMC card not connected correctly

Description

The PMC card that is configured in the motion configuration is not connected or is not working correctly.

Consequences

The application that needs this PMC card can not be ran.

Probable causes

The PMC card is not connected or the card is broken.


Please check the PMC card that is attached to the axis computer in the drive module arg.



38231, PMC card can not be started

Description

The PMC card that is configured in the motion configuration is not set up correctly and can not be started.

Consequences

The application that uses this PMC card can not be ran.

Probable causes

The error is problably a error in the motion configuration.


Please check the limits for channels for this card in the motion configuration.

38234, Max Force or Torque reached

Description

The measurend force or torque in the force sensor attached to the axis computer in drive module arg has higher value than it is configured for.

Consequences

The system will not stop due to this.

Probable causes

The appliced force or torque on the sensor is higher that configured.

Too high ordered reference can be the cause. The configuration might also be faulty.


Check the force and torque references in the program and if the environment have applied too high force or torque to the sensor.

38232, PMC max channels reached

Description

The PMC card that is configured in the motion configuration is not set up correctly and can not be started.

Consequences

The application that uses this PMC card can not be ran.

Probable causes

The error is problably a error in the motion configuration.


Please check the limits for channels for this card in the motion configuration.

38235, Saturation warning of force sensor input

Description

The analog input values of the measurment board connected to the force sensor have saturated and the time in saturation has reached the warning level.

The measurment board is connected to the axis computer in drive module arg


Check the load that was applied to the force/torque sensor.

Check that the cable, sensor and measurment board is not damaged.

Increase the system parameter: time in satuartion before warning

38233, Force sensor safety channel error

Description

The safety channel in the cable between the force sensor and measurment board is under configured safety channel voltage level.

The force sensor is connected to the axis computer in drive module

arg.

Consequences

The system will go to SYS HALT and the application that uses this sensor can not be ran until cable is connected or replaced. Safety channel supervision can be disconnected in the motion configuraion.

Probable causes

1. The cable is not attached correctly.

2. The cable has damage to the connectors or the cable itself.

3. The sensor cable does not have satefy channel.


Assure that the cable is connected properlly and inspect the connectors at both ends of the cable and the cable itself. Replace if damaged.

38236, Saturation error of of force sensor input

Description

The analog input values of the measurment board connected to the force sensor have saturated and the time in saturation has reached the error level. The measurment board is connected to the axis computer in drive module arg

Consequences

system will stop


Check the load that was applied to the force/torque sensor. Check that the cable, sensor and measurment board is not damaged. Increase the system parameter: time in satuartion before error

38237, Configuration error for Force

Measurement Board

Description

The configuration input values for the Force Measurement Board connected to the force sensor is erroneous. The board is connected to drive module arg, link arg.

Consequences





Check the configuration.

39401, Torque Current Reference Error

Description

The torque-current reference is increasing too quickly for joint arg, connected to drive module arg.

Consequences

-

Probable causes

The resolver feedback may be poor or the speed loop gain may be badly adjusted.


1) Check the resolver cable and the resolver grounding for this joint. If this joint is an additional axis, then check that the motor data in the configuration file is correct. How to check the configuration file is detailed in the Trouble Shooting Manual.

2) Reduce the gain of the speed loop.


1) Check that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble

Shooting Manual.

2) Check that no DC bus errors are present in the event log.

3) Check that the incoming mains voltage is within the specification.

4) Check that the motor cables are not damaged or badly connected.

39404, Torque Loop Overcurrent

Description

The field-current controller detected too high current for joint arg, connected to drive module arg.

Consequences

-

Probable causes

The motor data in the configuration files may be wrong.


1) Check that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble

Shooting Manual.


3) Check that the incoming mains voltage is within the specification.

4) Check that the motor cables are not damaged or badly connected.

39402, Motor Angle Reference Warning

Description

The motor angle reference is increasing too quickly for joint arg, connected to drive module arg.

Consequences

-

Probable causes

The resolver feedback may be poor or the speed loop gain may be badly adjusted.


1) Check the resolver cable and the resolver grounding for this joint. If this joint is an additional axis, then check that the motor data in the configuration file is correct. How to check the configuration file is detailed in the Trouble Shooting Manual.

2) Reduce the gain of the speed loop.

39403, Torque Loop Undercurrent

Description

The torque-current controller detected too low current for joint arg, connected to drive module arg.

Consequences

-

Probable causes

The motor data in the configuration files may be wrong or the DC bus voltage may be too low.

39405, Maximum PWM Reached in Torque

Controller

Description

The torque-current control loop has been saturated for joint arg, connected to drive module arg.

Consequences

-

Probable causes

The mains voltage may be too low or the motor windings or motor cables may be broken.



2) Check that the incoming mains voltage is within specified limits.

3) Check the motor cables and motor windings for open circuits.

39406, Field Loop overcurrent

Description

The field-current control loop has produced too high current for joint

arg, connected to drive module arg.

Consequences

-



Probable causes

The motor data in the configuration files may be wrong.



2) Check that the incoming mains is within specified limits.

3) Check the motor cables and motor windings.

2) Make sure the configuration key match the installed hardware/ software combination. How to check the configuration file is detailed in the Trouble Shooting Manual.

3) If the rectifier unit was recently replaced, make sure a unit of the correct type code is used.

39407, Drive Unit has the wrong type code

Description

The type code in drive unit for joint arg in drive module arg is different from the one specified in the configuration file. Installed drive unit type is arg, and the configured type is arg.

Consequences


Probable causes

The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the drive unit was recently replaced, a drive unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination.


1) Make sure the values in the configuration file match the installed hardware.


3) If the drive unit was recently replaced, make sure a unit of the correct type code is used.

39409, Capacitor Unit has the wrong type code

Description

The type code for capacitor unit arg in drive module arg is different from the one specified in the configuration file. Installed capacitor unit type is arg, and the configured type is arg.

Consequences


Probable causes

The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the capacitor unit was recently replaced, a capacitor unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination.




3) If the capacitor unit was recently replaced, make sure a unit of the correct type code is used.

39408, Rectifier Unit has the wrong type code

Description

The type code for rectifier unit arg in drive module arg is different from the one specified in the configuration file. Installed rectifier unit type is arg, and the configured type is arg.

Consequences


Probable causes

The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the rectifier unit was recently replaced, a rectifier unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination.



39410, Drive Unit communication warning

Description

Many communication errors are being detected between the axis computer and drive unit number arg in drive module arg. (error rate per time unit)

Consequences

If the number of communication errors increases further, there is a risk that the controller will be forced to stop

Probable causes

External noise may interfere with the communication signals.


1) Check the communication link cable between the axis computer and the main drive unit is correctly connected.

2) Check that the module is properly grounded.

3) Check for external electromagnetic noise sources close to the drive module.



39411, Too Many communication errors

Description

Four or more consecutive communication packets have been lost between the axis computer and drive unit arg in drive module arg.

Consequences


Probable causes

There may be a break in the communication link cable between the axis computer and the main drive unit, the drive module may be incorrectly grounded or excessive noise may interfere with the communication signals.




3) Check for external electromagnetic noise sources close to the drive module.


1) Restart the controller.

2) If the problem persists, contact your local ABB representative..

39414, Unknown Capacitor Type Code

Description

The type code for the capacitor unit arg in drive module arg is not recognised by the system.

Consequences


Probable causes

The wrong type of capacitor unit may have been fitted or the capacitor version used is not supported by the software.


1) Check the type of capacitor unit fitted. Replace if it is the wrong type.

2) If the problem persists, contact your local ABB representative.

39412, Too Many Missed Reference Updates

Description

Too many missed communication packets have been detected for joint

arg, in drive module arg.

Consequences


Probable causes





3) Check for external electromagnetic noise sources close to the drive module..

39415, Communication with the Drive Unit Lost

Description

Communication with drive unit number arg in drive module arg has been lost.

Consequences


Probable causes





3) Check for external electromagnetic noise sources close to the drive module..

39413, Drive Software Not Synchronised

Description

The axis computer software in drive module arg has become unsynchronised with the drive software for joint arg. This is an unstable software state.

Consequences


Probable causes

There may be glitches in the system timing.

39416, Drive Unit Not Responding

Description

The main drive unit in drive module arg is not responding.

Consequences




Probable causes

There may be a break in the communication link cable between the axis computer and the main drive unit, or there may be a lock-up in the software.



2) Restart the controller.

3) If the problem persists, contact your local ABB representative.

39417, Cannot find Drive Software Version File

Description

The system cannot locate a valid drive version file on the disk.

The file may have been erased my mistake. Without this file it is not possible to check if the drive units software needs updating.


Contact your local ABB representative.


1) Make sure the cable connections on the rectifier unit unit are correct.

2) Make sure the rectifier unit is one supported by this controller.

3) If the rectifier unit was recently replaced, make sure a unit of the correct type code is used.

39420, Drive Unit built in test failure

Description

Drive unit number arg in drive module arg has detected an internal hardware failure.

Consequences


Probable causes

The test software is not working correctly, or the actual hardware is faulty.


1) Perform a shutdown and then restart the system.

2) If the problem persists, isolate the faulty drive unit and replace it.

39418, Unknown Drive Unit type code

Description

The type code for the drive unit arg in drive module arg is not recognised by the system. Installed drive unit type is arg, and the configured type is arg.

Consequences


Probable causes

The connection to the drive unit may be bad or the hardware may be faulty.


1) Make sure the cable connections on the drive unit are correct.

2) Make sure the drive unit is one supported by this controller.

3) If the drive unit was recently replaced, make sure a unit of the correct type code is used.

39421, Drive Unit configuration test failure

Description

Drive unit number arg in drive module arg has detected an internal error.

Consequences


Probable causes

The connection to the drive unit may be bad or incorrect hardware may have been fitted.




39419, Unknown Rectifier type code

Description

The type code for the rectifier unit arg in drive module arg is not recognised by the system. Installed rectifier unit type is arg, and the configured type is arg.

Consequences


Probable causes

The connection to the drive unit may be bad or the hardware may be faulty.

39422, Drive Unit watchdog timeout

Description

The time limit for watchdog timer for drive unit number arg in drive module arg has expired.

Consequences


Probable causes

The connection to the drive unit may be bad or incorrect hardware may have been fitted. It may also be caused by an internal error in the drive unit.






39423, Drive Unit Internal Warning

Description

Internal measurement warning for drive unit number arg in drive module arg.

supervision code = arg

Consequences


Probable causes

There may be problems with the control cable, the DC link connection

(bus bar or cable) or internal hardware.


1) Check the control cables and DC link connection (bus bar or cable) are correctly inserted for this unit.


Probable causes

This may be caused by a faulty or lacking DC link connection between the rectifier and drive units.


1) Make sure the DC link connection (bus bar or cable) is correctly connected between the rectifier and drive unit.

2) Check the indication LEDs on the rectifier and drive units. The significance of the LEDs is described in the Trouble Shooting Manual.

39426, Rectifier internal failure

Description

The rectifier on communication link arg attached to drive module

arghas detected an internal failure.

Consequences


Probable causes

This may be caused by a faulty or lacking signal connection between the rectifier and drive units.


1) Make sure the signal cable is correctly connected between the rectifier and drive unit.

2) Check the indication LEDs on the rectifier and drive units. The significance of the LEDs is described in the Trouble Shooting Manual.

39424, Drive Unit internal error

Description

Internal measurement warning for drive unit number arg in drive module arg.

Supervision Code = arg

Consequences


Probable causes

The connection to the drive unit may be bad or incorrect hardware may have been fitted. It may also be caused by faulty control cable, DC link connection (bus bar or cable) or internal hardware.


1) Make sure the control cables and DC link connection (bus bar or cable) are correctly connected for this unit.


3) If the problem persists, isolate the faulty unit and replace it.

39427, Rectifier communication missing

Description

The communication with the rectifier on drive comm link arg, drive module arg has been lost.

Consequences


Probable causes

This may be caused by a faulty or lacking signal connection between the rectifier and drive units.




3) If the problem persists, isolate the faulty unit and replace it.

39425, Drive Unit measurement failure

Description

A current measurement circuit in drive unit number arg, drive module

arg, attached to joint arg has failed.

Consequences



Description

The rectifier on drive comm link arg, drive module arg has detected a startup error.



Consequences


Probable causes

This may be caused by an internal error in the rectifier unit.




3) If the problem persists, isolate the faulty rectifier unit and replace it.

39431, Update of Drive Unit Software in

Progress

Description

The drive unit software in drive module arg is being updated.

Please wait for the upgrade to be completed. This will take approximately 3.5 minutes.

NOTE: Please do not turn off the power or restart the controller until the download is complete.


Please wait...

2) If the problem persists, replace the drive unit.

39435, Cannot find additional axis drive unit

Description

The system cannot detect an additional axis drive for joint arg in drive module arg.

Consequences

System goes to SYS_FAIL.

Probable causes

This can be due to:

1) Having an additional axis configured but not having a drive unit in the drive module.

2) Having an external drive unit but not connecting the cable to the

Xarg connector position on the main drive unit.

3) Damaged cable between the additional axis drive and the main drive unit.


1) Check the drive module contains enough additional axis drives.

2) Check that the configuration key does not define more external drive units then are connected in the drive module

3) Check the cable between the additional axis drive unit and to the main drive unit is correctly inserted in the right connector position.

4) If the cable exists and is correctly inserted, then it may be damaged and should be replaced.

39432, Incompatible boot version in drive unit

Description

The boot version in drive module arg is version arg, which is not allowed. The latest allowed boot version is arg.

Consequences


Probable causes

The boot version is not compatible with the hardware version.


1) Replace the drive unit with one using a boot version equal to or greater than the latest allowed one.

39434, Drive Unit Start Failure

Description

The drive unit in drive module arg failed to start. drive boot status =

arg. drive dsp1 status = arg

Consequences

The robot can not be operated.

Probable causes

A number of errors may cause this.


1) Switch the main power off to the module and then switch it back on.

Note that a normal restart will NOT suffice!

39440, Open circuit in bleeder resistor circuit

Description

The bleeder resistor connected to the rectifier on drive link arg, drive module arg, is an open circuit.

Consequences


Probable causes

This may be caused by a faulty bleeder resistor cable or bleeder resistor.



2) Make sure the cable and resistor is working correctly by measuring their resistance respectively. Disconnect before measuring.


39441, Short circuit in bleeder resistor circuit

Description

The bleeder resistor connected to the rectifier on drive link arg, drive module arg, is a short circuit.



Consequences


Probable causes

This may be caused by a faulty bleeder resistor cable or bleeder resistor.



2) Make sure the cable and resistor is working correctly by measuring their resistance respectively. Disconnect before measuring.


Consequences


Probable causes

The user program may contain too much hard braking or too high a payload of the manipulators. This is more likely if the system contains additional axes.


1) Rewrite the user program to reduce the amount of hard braking.

39442, Bleeder Resistance Too Low

Description

The bleeder resistance is too low for the rectifier on drive comm link

arg, drive module arg.

Consequences


Probable causes

The bleeders may have the wrong resistance value or one of the bleeders may have failed, causing a short circuit.


1) Check the bleeder resistors to see that they are the correct resistance value for this drive module configuration.

2) Check that none of the resistors have failed. How to check the configuration file is detailed in the Trouble Shooting Manual.

39450, Faulty Fan Unit Power Supply

Description

The power supply for the fan unit in drive module arg is not within its allowed voltage limits.

Consequences

-

Probable causes

The main fan power supply unit may be faulty or the supply to this power supply unit may not be within its allowed voltage limits.


1) Check the fan cable is correctly inserted.

2) Check that all fans are working. 3) Check the input voltage to the main fan power supply unit. Replace any faulty unit.

39443, Bleeder Resistor Overload Warning

Description

The power consumed by the bleeder resistors is approaching overload for the rectifier on drive communication link arg, drive module arg.

Consequences


Probable causes

The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes.



39444, Bleeder resistor overload error

Description

The bleeder resistors have been overloaded for the rectifier on drive communication link arg, drive module arg.

39451, Fan Unit Malfunction

Description

The fan unit in drive module arg has malfunctioned.

Consequences

-

Probable causes

The fan unit may be faulty, a loss of power supply or the fan power cable may not be connected correctly.


1) Make sure the fan cable is correctly connected.

2) Make sure all fans are working and that air flow is not obstructed.

3) Measure the output voltage from the drive unit supplying the fan.

Replace any faulty unit.

39452, Axis Computer Cooling Fan Malfunction

Description

The cooling fan for the axis computer in drive module arg has malfunctioned.


1)Check that the fan cable is correctly inserted.

2) Replace the faulty fan unit.



39453, Transformer Cooling Fan Malfunction

Description

The cooling fan for the transformer supplying drive module arg has malfunctioned.


Check if fan cable is correctly inserted.

2) Replace the faulty fan unit.

39460, DC Link Voltage Too Low

Description

The DC link voltage is too low for the rectifier on drive communication link arg, drive module arg.

Consequences


Probable causes

The DC link bus bar may be incorrectly connected or the three-phase mains power may be interrupted while the robot is in the Motors ON state. The mains contactor may also have been opened whilst the robot is in Motors ON state (breaking the safety chain). The incoming main power supply may also be too low.


1) Make sure the DC link bus bar is correctly connected.

2) Make sure the mains supply has not been interrupted.

3) Make sure the safety chain has not been broken.

4) Make sure the Drive Module Power Supply output voltage is within acceptable limits as specified in the Product Manual.

39461, DC Link Voltage Too High

Description

The DC link voltage is too high for the rectifier on drive communication link arg, drive module arg.

Consequences


Probable causes

The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes. The brake resistors may also be faulty.



2) Check that none of the resistors have failed.

3) If possible, rewrite the user program to reduce the amount of hard braking.

39462, DC Link Voltage at Critical

Description

The DC link voltage is critically high for the rectifier on drive communication link arg, drive module arg.

Consequences


Probable causes

The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes. The brake resistors may also be faulty.



2) Check that none of the resistors have failed.


39463, Motor Phase Short Circuit Warning

Description

A brief short circuit was detected in the motor/motor cable for the motor attached to joint arg in drive module arg.

Consequences

-

Probable causes

This may be due to dust or metal fragments contaminating the contacts or motor windings.


No action is required if the problem does not persist.

39464, Short circuit in Motor phase circuit

Description

The motor or motor cable for joint arg in drive module arg, drive unit number arg, is a short circuit.

Consequences


Probable causes

This may be caused by a faulty motor or motor cable. It may also be caused by contamination in the contactors for the cables or a failure of the motor windings.


1) Make sure the motor cable is correctly connected to the drive unit.

2) Check the cable and motor by measuring their resistance respectively. Disconnect before measuring.





Description

The motor current is higher than the allowed for joint arg in drive module arg, drive unit number arg.

Consequences

-

Probable causes

The motor load may be too high or the motor may have stalled (maybe due to a collision).


1) Check that the robot has not collided with anything.


3) If the axis is an additional axis, check that the motor load is not too high for the drive unit.

39466, Motor Current Overload

Description

The motor current is too high for joint arg in drive module arg, drive unit number arg.

Consequences


Probable causes

The motor load may be too high or the motor may have stalled (maybe due to a collision).




3) If the axis is an additional axis, check that the motor load is not too high for the drive unit.

2) Check that the ambient temperature does not exceed the cabinet rating.

3) If the system contains additional axes then check that motors are not too large for the drive units.

4) If possible, rewrite the user program to reduce the amount of hard acceleration.

39468, Drive Unit Temperature Alarm

Description

The temperature has risen above the alarm level in drive unit number

arg, drive module arg, which is the second abnormal level of three.

Consequences


Probable causes

The ambient temperature may be too high, the cooling fans may have failed or the user program may consume more current than the drive system can supply.


1) Check that the fans are running and that the air flow is not obstructed.




39467, Drive Unit Temperature Warning

Description

The temperature has risen above the warning level in drive unit number arg, drive module arg, which is the lowest abnormal level of three.

Consequences

-

Probable causes




39469, Drive Unit Temperature Critical

Description

The temperature has risen above the critical level in drive unit number

arg, drive module arg, which is the top abnormal level of three.

Consequences


Probable causes









39470, Power Semiconductor Warning

Description

The power semiconductor is approaching overload for joint arg, in drive unit number arg, drive module arg .

Consequences

-

Probable causes

The motor load may be too high, the motor may have stalled (maybe due to a collision), the motor load may be too high or there may not be enough cooling.







Consequences


Probable causes

This may be caused by an actual mains power loss, some malfunction in the Motors ON contactors or its cabling or in another part of the three phase chain inside the cabinet. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log.


1) Make sure the mains switch is closed and that there is mains voltage present. No volts means the problem is in mains cable connector or the factory power supply.

2) If the voltage is OK, disconnect the input mains cable and measure the resistance of all three phases across all the components in the 3 phase supply chain. Start from the contactor closest to the rectifier and work backwards towards the mains switch. The contactors can be closed manually to perform the test. Refer to the electrical drawings for the cabinet.

3) Check the indication LEDs on the rectifier unit. The significance of these is described in the Trouble Shooting Manual.

4) If the voltage is OK, check any other error log messages coinciding in time with this one for clues.

39471, Power Semiconductor Overload Error

Description

The power semiconductor has been overloaded for joint arg, in drive unit number arg, drive module arg .

Consequences


Probable causes

The motor load may be too high, the motor may have stalled (maybe due to a collision), the motor load may be too high or there may not be enough cooling.







39472, Incoming Mains Phase Missing

Description

The rectifier connected to communication link arg in drive module arg detects a power loss in one phase.

39473, All Incoming Mains Phases Missing

Description

The rectifier connected to communication link arg in drive module arg detects a power loss in one or more phases.

Consequences


Probable causes

This may be caused by an actual mains power loss, some malfunction in the Motors ON contactors or its cabling or in another part of the three phase chain inside the cabinet. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log.


1) Make sure the mains switch is closed and that there is mains voltage present. No volts means the problem is in mains cable connector or the factory power supply.

2) If the voltage is OK, disconnect the input mains cable and measure the resistance of all three phases across all the components in the 3 phase supply chain. Start from the contactor closest to the rectifier and work backwards towards the mains switch. The contactors can be closed manually to perform the test. Refer to the electrical drawings for the cabinet.

3) Check the indication LEDs on the rectifier unit. The significance of these is described in the Trouble Shooting Manual.

4) If the voltage is OK, check any other error log messages coinciding in time with this one for clues.



39474, Rectifier Current Warning

Description

The rectifier connected to drive communication link arg in drive module arg is approaching overload.

Consequences


Probable causes

The total motor current may be greater than that which the rectifier can supply.



39475, Rectifier Current Error

Description

The rectifier connected to drive communication link arg in drive module arg has reached overload.

Consequences


Probable causes

The total motor current may be greater than that which the rectifier can supply.




39477, Rectifier Temperature Error

Description

The temperature in the rectifier unit connected to drive communication link arg in drive module arg has reached a too high a level.

Consequences


Probable causes

The cooling fans may be faulty or the air flow may be obstructed. The ambient temperature may be too high or the system may be running with a too high load for extended periods.






39476, Rectifier Temperature Warning

Description

The temperature in the rectifier unit connected to drive communication link arg in drive module arg is approaching a too high a level.

Consequences


Probable causes

The cooling fans may be faulty or the air flow may be obstructed. The ambient temperature may be too high or the system may be running with a too high load for extended periods.





39478, Internal Motor PTC Temperature Error

Description

The temperature in one or more robot motors connected to drive module arg is has reached a too high a level.

Consequences


Probable causes

The motor may have stalled (possibly due to a collision), the motor may be overloaded or the ambient temperature may be higher than the rated level for the robot.



2) Check that the ambient temperature does not exceed the robot rating.

3) Allow the robot to cool down, and then run the system again.

Replace any motors damaged by the excessive heat.


39479, External Motor PTC Temperature Error

Description

One or more additional axis motors connected to drive module arg is has reached a too high a level.



Consequences


Probable causes

The motor may have stalled (possibly due to a collision), the motor may be overloaded or the ambient temperature may be higher than the rated level for the robot.


1) Check that the additional axis has not collided.

2) Check that the ambient temperature does not exceed the rating.

3) Allow the motor to cool down, and then run the system again.

Replace any motors damaged by the excessive heat.


Consequences

System goes to SYS_HALT.

Probable causes

1) Cables and connections on the Safety System are unplugged or damaged.

2) The contactor for this run chain in the drive module may be stuck due to mechanical problem in contactor itself.

3) The help contactor on the contactor can suffer from bad galvanic behavior or faulty cable to the Safety System.


1) Check if a motor contactor is stucked.

2) Replace faulty motor contactor.

39482, Mains Voltage Too High

Description

The mains voltage detected in drive module arg is too high.

Consequences


Probable causes

The mains transformer may be incorrectly wired or the external supply voltage may be too high.


1) Measure the incoming mains voltage at the main contactor in the drive module. Make sure it is within the range specified for this module.

2) Check the wiring of the mains transformer as detailed in the robot

Product Manual.

39485, Run chain close in motor off state

Description

Run chain arg is open when system is in motor on state. The problem occurred in drive system arg.

Consequences

System goes to SYS_HALT.

Probable causes

1) The contactor for this run chain placed in the drive module has been pulled down manually.

2) The contactor has been welded in close position.


1) If the contactor is not released and stays in pulled position, shut down the system and replace the contactor.

2) If the contactor has been pulled down manually, take this message as a warning only.

39483, DC Link Short Circuit

Description

A short circuit has been detected on the DC link of drive module arg.

Consequences


Probable causes

The DC bus bar may be badly connected or its contact surfaces may be contaminated causing a short circuit.


1) Check that all DC link bus bars have been correctly connected.

2) Check that all contacts are free from contamination.

39486, DC Link Not Connected

Description

The DC Link connection to the drive serving joint arg in drive module

arg, drive unit number arg is missing or is not properly connected.

Consequences

The system goes to SYS_HALT.

Probable causes

1) The DC Bussbar is either missing or is not properly connected.

2) If the bussbar is correctly connected. The drive unit reporting the error may have a fault.


1) Check the DC Bussbar is properly connected to all the drive units

39484, Run chain open in motor on state

Description

Run chain arg is open when system is in motor on state. The problem occurred in drive system arg.

39500, Logic Voltage to Drive Unit Warning

Description

The 24V supply from the Drive Module Power Supply to the main drive unit in drive module arg is out of range.



Consequences

-

Probable causes

The 24V supply from the Drive Module Power Supply may be out of range.


1) Make sure the power cable from the Drive Module Power Supply to the main drive unit is connected correctly.

2) Check if the power supply unit LED is red. The full meaning of all

LED indications are described in the Trouble Shooting Manual, IRC5.

Consequences


Probable causes

The fan unit may be faulty, the cooling air flow may be obstructed or the ambient temperature may be too high.


1) NOTE! Do not try to restart the controller for approx. ten minutes to let it cool down.

2) Make sure the fans are running and that the air flow is not obstructed.

3) Make sure the ambient temperature does not exceed the drive module rating.

4) Make sure the power supply connectors are correctly connected to the axis computer.

39501, Logic Voltage to Drive Unit Error

Description

The 24V supply to the main drive unit in drive module arg is out of range.

Consequences


Probable causes

The 24V supply from the power supply unit may be out of range.


1) Make sure the power cable from the power supply unit to the main drive unit is connected correctly.

2) Check if the power supply unit LED is red. The full meaning of all

LED indications are described in the Trouble Shooting Manual, IRC5.

39502, Logic Voltage to Rectifier Error

Description

The 24V to the rectifier in drive module arg is out of range.

Consequences

-

Probable causes

The cable between the drive unit and the rectifier may be badly connected, or the power supply voltage to the drive unit may be out of range.


1) Check that the power cable between the power supply unit and the rectifier unit has been connected correctly.

2) Check the 24 V voltage in the power cable to the drive unit..

39503, Power Supply Overtemperature

Description

The temperature in the Drive Module Power Supply of drive module

arg has reached a critical level.

39504, Power Supply to Brakes Overload

Description

The brake power circuit in drive module arg draws too much current.

Consequences


Probable causes

The brake power cable may be faulty (short circuit), or additional axis motors with brakes consuming too much power may be used. The fault may also occur if the cable from the power supply unit is not correctly connected to the drive module.


1) Make sure the power supply cable is correctly connected to the drive module.

2) Check the brake supply cable for short circuits.

3) Make sure the total current consumed by additional axes' motors does not exceed the specification for the drive module.

4) Make sure the power supply connectors are correctly connected to the axis computer.

5) Make sure the 24 V BRAKE voltage is within specified limits. See the Circuit Diagram in the Product Manual, IRC5.

39505, Mains Voltage to Power Supply Lost

Description

The mains power supply to the power supply unit in Drive Module arg is missing.

Consequences

No operation will be possible until after correcting the fault. The system goes to status SYS FAIL.



Probable causes

The main power switch on the Drive Module may be turned off. The incoming mains cable may be faulty (break), or the circuit breaker for the power supply may have tripped. The fault may also occur if the connector from the power supply unit is not correctly connected to the axis computer.


1) Check that the main power switch in turned on for the Drive Module and restart the system.

2) Check that the connector from the power supply unit is correctly connected to the axis computer.

3) Measure the voltage at the mains contactor to ensure that the mains is present.

4) Check that the power supply fuses/circuit breakers in the drive module have not tripped.

Probable causes

This may be due to a cable break, badly connected connectors or loss of power supply.


1) Make sure the main power switch on Drive Module arg has been switched ON.

2) Make sure the cable between Control Module and Drive Module is not damaged and that both connectors are correctly connected.

3) Make sure the cable is connected to the correct AXC connector on the Main Computer Unit Robot Communication Card or EtherNet

Board (if the MultiMove option has been installed).


5) Make sure the Power Supply Unit in Drive Module arg is working correctly.

39520, Communication lost with Drive Module

Description

The main computer has lost contact with drive module arg.

Consequences

The system goes to status SYS HALT No operation will be possible until the fault has been corrected.

Probable causes

This may be due to a cable break, badly connected connector or high levels of interference in the cable.


1) Make sure the cable between Control Module and Drive Module is not damaged and that both connectors are correctly connected.


39521, Drive Module Communication Warning

Description

There are a large number of communication errors being detected on the ethernet link to drive module arg.

This can be due to external noise sources interfering with the cable.


Check that there are no electromagnetic interference sources running near the cable or the drive or computer modules.

39523, Unused Axis computer connected

Description

Axis computer in the drive module arg is connected to the main computer but not in use.

Probable causes

This can be due to configuration problem.


1. Disconnect the unused axis computer or setup the system to use the axis computer.


39524, Drive Module Command timeout

Description

Drive Module arg does not respond to command arg. The system has stopped the program for safety reasons.


1. Check that drive module is powered on.

2. Check the cable between the main computer and axis computer.


39522, Axis computer not found

Description

The axis computer in drive module arg is not connected to the main computer.

Consequences

The system goes to status SYS FAIL. No operation will be possible until the fault has been corrected.

39525, Drive Module startup error

Description

The system has failed to complete the initialization phase of drive module arg .

Consequences


Probable causes

The system has failed to complete the initialization phase of the drive module.


1) Retry by restarting the system using the main power switch.




39530, Axis Computer Lost Communication

With Safety System

Description

Communication has been lost between axis computer and the Safety

System in drive module arg.

Consequences

System goes to status SYS FAIL.

Probable causes

This may be due to a faulty communication cable or connection between the axis computer and the Safety System. It may also be due to severe interference or if the Safety System has lost its power.


1) Check cable between the axis computer and the Safety System is intact and correctly connected.

2) Check power supply connected to the Safety System.


40003, Argument error

Description

An argument for the required parameter arg was expected, but the optional argument arg was found.


1) Make sure all arguments are specified in the same order as the parameters for the routine called.


Description

The argument for REF parameter arg is not a data reference.


1) Make sure the argument is a data or a parameter reference.

39531, Run chain glitch test not running

Description

The glitch test of the run chain has not been performed. The problem was discovered by the Safety System connected to the axis computer in drive module arg.

Consequences

System goes to status SYS HALT.

Probable causes

This may be due internal errors.


Contact your local ABB support office.


Description

The argument for INOUT parameter arg is not a variable or persistent reference, or it is read-only.


1) Make sure the argument is a variable or a persistent variable parameter or a persistent parameter reference and that it is NOT readonly.

2) Also make sure the argument is NOT written within brackets ().


Description

Parameter arg is missing an optional argument value.


The only parameters that may be specified by a name only are "switch" parameters. All others must be assigned a value.

1) Make sure parameter has a value.


Description

The optional argument arg has been used more than once in the same routine call.


1) Make sure the optional parameter is not used more than once in the same routine call.


Description

The optional argument arg is not found in its correct position in the argument list.


1) Make sure all arguments are specified in the same order as the parameters for the routine called.


Description

The argument arg has been specified for more than one parameter.


The parameter list, from which the parameter is selected, contains parameters mutually exclusive.

1) Make sure the argument is used for one parameter only.


Description

A reference to the optional parameter arg is missing.




Each optional parameter must have a reference argument, specified with a leading backslash character (\).

1) Change the required argument into an optional argument.


A routine call must supply values for all required parameters of the routine being called. The argument list must have as many arguments, as the parameter list has parameters.

1) Add more arguments to fit the parameter list.


Description

A reference to the required parameter arg in a conditional argument is missing.


Each conditional value for an optional parameter must refer to an optional parameter in the calling routine.

1) Change the conditional value.


Description

The call to routine arg has too many arguments.


No arguments, more than those defined by the called routine parameter list, must be supplied. The argument list must have as many arguments, as the parameter list has parameters.

1) Remove excessive arguments from the argument list.


Description

A reference to the required parameter arg in an optional argument is missing.


Each required parameter must have a reference argument, specified with a leading backslash character (\).

1) Change the optional argument into a required argument.

40015, Data declaration error

Description

The number of array dimensions is arg, but may be 1, 2 or 3 only.


1) Change the dimension expression.


Description

The required argument arg is not found in its correct position in the argument list.


Make sure all arguments are specified in the same order as the parameters for the routine called.


Description

Too many dimensions in array definition.


An array may have at most 3 dimensions.

Rewrite the program so that no more than 3 dimensions are needed.


Description

The "switch" argument arg has a value.

Probable causes

An argument corresponding to a "switch" parameter may not be assigned a value.


1) Remove the value.


Description

The call to routine arg has too few arguments.

40017, Type error

Description

Indexed data arg, arg is not of array type.


Only data that have been declared to be arrays may be indexed.

1) Remove the index or indices.

2) Declare the data to be an array.


Description

Data arg, arg is not of record type.


Components are only available for data of record type.

1) Check the type and name of the referenced data.



40019, Limit error

Description

Task arg: Error when creating the persistent variable arg.

The error occurred when the persistent variable was to be inserted into the database.

Program Ref. arg

Consequences

The created persistent variable can not be used in a RAPID program.

Probable causes

The program memory is full or fragmentated.


Check if large data structures could be split into smaller blocks.

Use of installed modules can save program memory.


Description

Illegal combination of operand types arg and arg for the '*' operator.


Allowed operand type combinations are: "num"*"num", "num"*"pos",

"pos"*"num", "pos"*"pos" and "orient"*"orient".

1) Check the operand types.

40023, Instruction error

Description

Cannot transfer control into another instruction list.


It is not possible to jump into a program flow instruction.

1) Make sure that the label is located in the same instruction list as the

GOTO instruction, at the same or an outer level.


Description

Illegal type arg for left operand of binary '+' or '-' operator.


Allowed operand types for the binary "+" operator are "num", "pos" and "string", and for the binary "-" operator "num" and "pos".



Description

Expression arg is not a constant expression.


Any expression contained within a data declaration must be a constant expression.

1) Make sure no expression contains variables or persistent references, or function calls.


Description

Missing expression in RETURN instruction.

Probable causes

A RETURN instruction within a function must specify a value to be returned.


1) Add a value expression.


Description

Illegal type arg for operand of unary '+' or '-' operator.


Allowed operand types for the unary "+" and "-" operators are "num" and "pos".



Description

Illegal type arg for right operand of binary '+' or '-' operator.


Allowed operand types for the binary "+" operator are "num", "pos" and "string", and for the binary "-" operator "num" and "pos".



Description

Illegal type arg for left operand of '/', 'DIV' or 'MOD' operator.


Allowed operand type for the "/", "DIV" or "MOD" operators is

"num".



Description

Illegal type arg for right operand of '/', 'DIV' or 'MOD' operator.


Allowed operand type for the "/", "DIV" or "MOD" operators is

"num".





Description

Illegal type arg for left operand of '<', '<=', '>' or '>=' operator.


Allowed operand type for the "<", "<=", ">" or ">=" operators is

"num".



Description

Illegal type arg for right operand of '<', '<=', '>' or '>=' operator.


Allowed operand type for the "<", "<=", ">" or ">=" operators is

"num".



Description

Illegal type arg for left operand of '*' operator.


Allowed operand types for the "*" operator are "num", "pos" or

"orient".



Description

Illegal type arg for right operand of '*' operator.


Allowed operand types for the "*" operator are "num", "pos" or

"orient".



Description

Illegal type arg for operand of 'NOT' operator.


Allowed operand type for the "NOT" operator is "bool".



Description

Illegal type arg for left operand of 'OR', 'XOR' or 'AND' operator.


Allowed operand type for the "OR", "XOR" or "AND" operators is

"bool".



Description

Illegal type arg for right operand of 'OR', 'XOR' or 'AND' operator.


Allowed operand type for the "OR", "XOR" or "AND" operators is

"bool".



Description

Incorrect number of indices in index list for array arg with arg dimension(s).


1) Make sure that the number of indices in the index list corresponds to the number of dimensions of the indexed data array.


Description

LOCAL illegal in routine constant declaration.


Only program data declarations may have the LOCAL attribute.

Remove the LOCAL attribute or move the declaration outside of the routine.


Description

LOCAL illegal in routine variable declaration


Only program data declarations may have the LOCAL attribute.

Remove the LOCAL attribute or move the declaration outside of the routine.

40039, Name error

Description

Constant name arg ambiguous.


Routine data must have names that are unique within the routine.

Program data must have names that are unique within the module.

Rename the data or change the conflicting name.




Description

Global constant name arg ambiguous.


Global data must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the data or change the conflicting name.


Description

Global persistent name arg ambiguous.




Modules must have names that are unique among all the global types, global data, global routines and modules in the entire program.

Rename the module or change the conflicting name.


Description

Parameter name arg ambiguous.


Parameters must have names that are unique within the routine.

Rename the parameter or change the conflicting name.


Description

Persistent name arg ambiguous





Description

Global routine name arg ambiguous.


Global routines must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the routine or change the conflicting name.


Description

Routine name arg ambiguous.


Routines must have names that are unique within the module. Rename the routine or change the conflicting name.


Description

Global variable name arg ambiguous.




Description

Variable name arg ambiguous.


Routine data must have names that are unique within the routine.




Description

Label name arg ambiguous.


Labels must have names that are unique within the routine. Rename the label or change the conflicting name.


Description

Operand types arg and arg for binary '+' or '-' operator not equal


The two operands of the '+' and '-' operators must have equal type.

Check the operand types.


Description

Module name arg ambiguous.


Description

Operand types arg and arg for '=' or '<>' operator not equal




The two operands of the '=' and '<>' operators must have equal type.

Check the operand types.


Description

RETURN with expression only allowed in function


In a procedure or trap the return instruction must not specify a return value expression. Remove the expression.


Description

Assignment target type arg is not value or semi-value type.


The type, of the data to be assigned a value, must be a value or semivalue type. Data of non-value types may only be set by special type specific predefined instructions or functions.


Description

TEST expression type arg not value or semi-value type


The TEST instruction may only be applied to an expression of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed.


Description

Different dimension of array type (arg) and aggregate (arg)


Make sure that the number of expressions in the aggregate is the same as the dimension of the data array.


Description

Place holder for value expression not allowed in definition of named constant


Complete the data declaration or change the data name to a place holder.


Description

Place holder for array dimension not allowed in definition of named constant or variable




Description

Type arg for left operand of '=' or '<>' operator not value or semi-value type


The '=' and '<>' operators may only be applied to expressions of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed.

40061, Routine declaration error

Description

Place holder for parameter array dimensions not allowed in definition of named routine


Complete the parameter declaration or change the routine name to a place holder.


Description

Type arg for right operand of '=' or '<>' operator not value or semivalue type


The '=' and '<>' operators may only be applied to expressions of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed.


Description

Place holder for parameter name not allowed in definition of named routine


Complete the routine declaration or change the routine name to a place holder.


Description

Place holder for initial value expression not allowed in definition of named persistent






At least one other object sharing the same name as the referred data is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness.

40064, Routine declaration error

Description

Place holder for parameter not allowed in definition of named routine


Complete the parameter declaration, remove the place holder or change the routine name to a place holder.

40065, Reference error

Description

Place holder for type not allowed in definition of named data, record component or routine


Complete the data or routine declaration or change the data or routine name to a place holder.


Description

function reference arg is ambiguous


At least one other object sharing the same name as the referred function is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness.


Description

Label reference arg is ambiguous


At least one other object sharing the same name as the referred label is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness.


Description

Place holder for initial value expression not allowed in definition of named variable




Description

Procedure reference arg is ambiguous


At least one other object sharing the same name as the referred procedure is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness.


Description

Too few components in record aggregate of type arg


Make sure that the number of expressions in the aggregate is the same as the number of components in the record type.


Description

Too many components in record aggregate of type arg


Make sure that the number of expressions in the aggregate is the same as the number of components in the record type.


Description

Trap reference arg is ambiguous.


At least one other object sharing the same name as the referred trap is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness.


Description

Data reference arg is ambiguous


Description

arg

not entire data reference


The specified name identifies an object other than data. Check if the desired


data is hidden by some other object with the same name.


Description

arg

not function reference


The specified name identifies an object other than a function. Check if the desired function is hidden by some other object with the same name.


Description

arg

not label reference


The specified name identifies an object other than a label. Check if the desired label is hidden by some other object with the same name.


Description

arg

not optional parameter reference in conditional argument value


The specified name identifies an object other than an optional parameter. Change the name to refer to an optional parameter.


Description

arg

not optional parameter reference


The specified name identifies an object other than an optional parameter. Change the name to refer to an optional parameter.




Description

Task arg: arg is not a procedure reference


The specified name identifies an object

other than a procedure. Check if the

desired procedure is hidden by some

other object with the same name.


Description

arg

not required parameter reference


The specified name identifies an object other than a required parameter. Change the name to refer to a required parameter.


Description

arg

not trap reference


The specified name identifies an object other than a trap. Check if the desired trap is hidden by some other object with the same name.


Description

arg

not type name


The specified name identifies an object other than a type. Check if the desired type is hidden by some other object with the same name.


Description

arg

not value type


Only variables that lack initial value,

195


and 'VAR' mode parameters may be of semi-value or non-value type.


Description

Reference to unknown label arg


The routine contains no label (or other

object) with the specified name.


Description

Reference to unknown optional parameter

arg


The called routine contains no optional parameter (or other object) with the specified name.


Description

Reference to unknown record component

arg


The record type contains no record component with the specified name.


Description

Reference to unknown required parameter

arg


The called routine contains no required parameter (or other object) with the specified name.


Description

Unknown type name

arg

196


No data type (or other object) with the specified name is visible from this program position.


Description

Assignment target is read only


The data to be assigned a value may not be a constant, read only variable or read only persistent.


Description

Persistent declaration not allowed in routine


Persistents may only be declared at module level. Move the persistent declaration from the routine.


Description

RAISE without expression only allowed in error handler


Add an error number expression to the

RAISE instruction.


Description

RETRY only allowed in error handler


The RETRY instruction may only be used in error handlers. Remove it.


Description

TRYNEXT only allowed in error handler


The TRYNEXT instruction may only be used


in error handlers. Remove it.

40098, Parameter error

Description

'switch' parameter must have transfer mode IN


Remove the parameter transfer mode specifier. If IN transfer mode is not sufficient, change the data type of the parameter.


Description

'switch' parameter cannot be dimensioned


Remove the array dimension specification, or change the data type of the parameter.


Description

'switch' only allowed for optional parameter


Change the parameter into an optional parameter, or change the data type of the parameter. If the object is not a parameter, change the data type.


Description

Type mismatch of expected type arg and found type arg


The expression is not of the expected data type.


Description

Type mismatch of aggregate, expected type

arg




The aggregate does not match the expected data type.


Description

Persistent

arg, arg type mismatch


There is already a persistent data with the same name but with another data type. Rename the persistent, or change its data type.


Description

Cannot determine array dimensions (circular constant references ?)


Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the declarations.


Description

Cannot determine type of constant value (circular constant references ?)




Description

Cannot evaluate constant value expression (circular constant references ?)


Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the

197


declarations.


Description

Cannot determine type of variable value (circular constant references?)




Description

Unknown aggregate type


An aggregate may not be used in this position since there is no expected data type. Declare data with the desired data type and aggregate value. Use the name of the data instead of the aggregate.

40109, Type definition error

Description

Cannot determine type of record component

arg

(circular type definitions?)


Check that the type of the component is correctly defined. If so, it could be a circular definition, the type of a component could not refer to the its own record type.


Description

Record name

arg is ambiguous


At least one other object sharing the same name as the referred record name is visible from this program position. Make sure that all object names fulfill the

198 naming rules regarding uniqueness.


Description

Global record name arg ambiguous


Global type must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the record or change the conflicting name.


Description

Alias name

arg is ambiguous


At least one other object sharing the same name as the referred alias name is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness.


Description

Global alias name arg ambiguous


Global type must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the alias or change the conflicting name.


Description

Type reference of alias name arg is an alias type


Check that the type of the component is correctly defined. If so, it could be a circular definition. The type of a component could not refer to its own record type.



Description

Cannot determine type of alias arg

(circular type definitions?)


Check that the type of the alias is correctly defined. If so, it could be a circular definition, the type of an alias could not refer to a record that use this alias as a component.


Description

Record component name

arg is ambiguous


At least one other object sharing the same name as the referred component is visible from this program position. Make sure that all object names fulfill the aming rules regarding uniqueness.


Description

Place holder for record component not allowed in definition of named record


Complete the definition or change the data name to a place holder.


Description

Cannot use the semi-value type

arg for record components



Description

Illegal reference to installed task object

arg from shared object


Install the referred object shared, or



install the referring ReaL object/ archive or RAPID module in each task

(not shared).


Description

Cannot use semi-value type for arrays



Description

arg not procedure reference


The specified name identifies an object other than a procedure.

Check if the desired procedure is hidden by some other object with the same name.


Description

Argument for 'PERS' parameter arg is not a persistent reference or is read only


Make sure the argument is just a persistent or persistent parameter reference and that it is writable.

Do not use () around the argument.


Description

Argument for 'VAR' parameter arg is not variable reference or is read only


Make sure the argument is just a variable or variable parameter reference and that it is writable.



Description

The Interrupt number is not static variable reference, or it is shared, or it is read only


Make sure the interrupt number is just a variable or variable parameter reference. The variable must be static and not shared. The variable may

not be read only.

199


40126, Value error

Description

Integer value arg is too large


The value of the expression must be an integer value. The current value is outside the integer range.

40135, Syntax error.

Description

Expected arg



Description

arg is not an integer value


The value of the expression must be an exact integer value. The current value has a fraction part.

40136, Syntax error

Description

Unexpected arg



Description

Expected arg but found arg



Description

Reference to unknown entire data arg


No data (or other object) with the specified name is visible from this

program position.


Description

Syntax error, stack backed up



Description

Reference to unknown function arg


No function (or other object) with the specified name is visible from this program position.


Description

Syntax error, parsing terminated



Description

Reference to unknown procedure arg


No procedure (or other object) with the specified name is visible from this program position.

40140, Numerical value for symbol arg is out of range.

Description

Numerical value for symbol arg is out of range.


Make the value smaller


Description

Reference to unknown trap arg


No trap (or other object) with the specified name is visible from this program position.

40141, String too long

Description

The string arg is too long.


Make the string shorter.

40142, TxId is out of range

Description

The Text identifier arg is out of range.




40143, Aggregate is out of range

Description

The aggregate arg is out of range.


Make the aggregate smaller

40144, Integer out of range

Description

The integer arg is out of range.


Make the integer smaller.

40145, Parser stack is full

Description

The parser stack is full.


Reduce program complexity

40146, Not enough heap space.

Description

There is not enough heap space to fulfill the action.


Rewrite your program

40147, Identifier is reserved word in current language

Description

The identifier arg is a reserved word in current language.


Change the name of the identifier

40148, Identifier too long

Description

The name of the identifier arg is too long.


Rename the identifier with a shorter name.

40149, Placeholder too long

Description

The placeholder arg is too long.



Rename the placeholder with a shorter name.

40150, Unexpected unknown token

Description

Unexpected unknown token.


Remove the unknown token.

40151, Initial value of PERS not updated.

Description

The initial value of PERS: arg will not be updated.

A PERS with the same name in another task has already an initial value of the PERS.


Check the value in the Program Data window to see that the PERS have the correct value. if necessary, unload modules with that PERS from all tasks and reload with new initial value.

The PERS is of type: arg.


Description

TASK illegal in routine variable declaration


Only program data declarations may have the TASK attribute. Remove the TASK attribute or move the declaration outside of the routine.


Description

Task arg: Argument for

'PERS' parameter arg is not persistent reference or is read only


Make sure the argument is just a persistent or persistent parameter reference and that it is writable. Do not use () around the argument.


Description

Task arg: Argument for 'VAR' parameter arg is not variable reference or is read only


Make sure the argument is just a variable or variable parameter reference and that it is writable.

201




Description

Task arg: Interrupt number is not a static variable reference, is shared, or is read only.


Make sure the interrupt number is just a variable or variable parameter reference. The variable must be static and not shared. The variable may not be read only.


Description

Task arg: Integer value

arg too large


The value of the expression must be an integer value. The current value is outside the integer range.


Description

Task arg: arg not integer value


The value of the expression must be an exact integer value. The current value has a fraction part.

40160, Errors in RAPID program.

Description

Task arg: There are errors in the RAPID program.


Check for RAPID errors using Check program in the Program editor and correct the program.

40161, Option is missing.

Description

The instruction arg requires the option arg.

Consequences

The program will not execute properly.

202

Probable causes

The system image doesn't include the required option.


Update the system image with the required option.

40162, Errors in RAPID program.

Description

Task arg: There are errors in the RAPID program.


Take the following actions to be able to debug the program:

1 Change the type of the task to NORMAL.

2 Restart the controller.

3 Check for RAPID errors and correct the program.


Description

Task arg: Reference to unknown entire data arg


No data (or other object) with the specified name is visible from this program position.


Description

Task arg: Reference to unknown function arg


No function (or other object) with the specified name is visible from this program position.


Description

Task arg: Reference to unknown procedure arg


No procedure (or other object) with the specified name is visible from this program position.

To avoid run time errors like this, add code in error handler to handle this.

ERRNO will be set to "ERR_REFUNKPRC".


Description

Task arg: Reference to unknown trap arg




No trap (or other object) with the specified name is visible from this program position.


At least one other object sharing the same name as the referred procedure is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness.


Description

Task arg:

Reference to unknown data (or other object) found during execution of module arg.


Check the program for unresolved references.


Description

Task arg: Variable and trap

routine already connected


It is not legal to connect a specific

variable with a trap routine

more than once.


Description

Task arg:

Reference to unknown module arg.


No module (or other object) with the specified name is visible from this program position. Check the program for incorrect module reference or if the module is missing.


Description

Task arg: arg

is second present conditional argument for excluding parameters


Arguments may not be present for more than one parameter from a list of parameters that exclude each other.


Description

Task arg:

Reference to object arg that is not a module.


The specified name identifies an object other than a module.

Check the program for incorrect module reference.

40193, Execution error

Description

Task arg: Late binding procedure call error arg


There is an error in the procedure call instruction. See previous message for the actual cause.


Description

Task arg:

Reference to module arg is ambiguous.


At least one other object sharing the same name as the referred module is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness.


Description

Task arg: Division by zero


Cannot divide by 0. Rewrite the program so that the divide operation is not executed when the divisor is 0.


Description

Task arg:

Reference to procedure arg is ambiguous.


Description

Task arg:

The configured maximum number of RETRYs (arg retries)



is exceeded.


The error correction performed before the RETRY instruction is executed, is probably not enough to cure the error.

Check the error handler.


Description

Task arg: Attempt to execute place holder


Remove the place holder or the instruction containing it, or make the instruction complete. Then continue execution.


Description

Task arg: Function does not return any value


The end of the function has been reached without a RETURN instruction being executed. Add a RETURN instruction specifying a function return value.


Description

Task arg: Illegal orientation value

arg


Attempt to use illegal orientation

(quaternion) value


Description

Task arg: Illegal error number arg in arg.


Use error numbers in the range 1-90 or book error numbers with the instruction BookErrNo.


Description

Task arg: No more interrupt number available


There is a limited number of interrupt numbers available. Rewrite the program to use fewer interrupt numbers. This message may also occur as a consequence of a system error.


Description

Task arg: Dimensions arg and arg of conformant array dimension number arg are incompatible


The array is not of the expected size.

Array assignment may only be performed on arrays of identical size.


Description

Task arg: Optional parameter arg not present


The value of a non-present optional parameter may not be referred. Use the predefined function 'Present' to check the presence of the parameter before using its value.


Description

Task arg: Array index arg for dimension number arg out of bounds

(1-arg)


The array index value is non-positive or violates the declared size of the array.


Description

Task arg: Rapid String arg too long




String value exceeds the maximum allowed length. Rewrite the program to use strings of less length.

40206, Interrupt queue full

Description

Execution of all normal tasks has stopped. Too many interrupts has occurred in arg while executing a trap routine.

Consequences

The system goes to blocked state and can not be restarted before moving the program pointer to an arbitrary position.

Probable causes

Too many interrupts has occurred while executing a trap routine. This can be caused by heavy CPU load.


1) Minimize execution time in the trap routine.

2) Disable/enable interrupts while executing a trap routine using the

Isleep or Iwatch commands.


Description

Task arg: Illegal error number arg in arg


Error numbers used in an ERROR handler must be positive.

Probable causes

-The program has been stopped

-A service routine or an event routine may be executing.

-The program is executing in step mode.


-


Description

Task arg: Execution aborted


Execution was aborted due to a fatal error.


Description

Task arg: Execution stack overflow


The program is too complex to execute.

Probably the program contains recursive routines.

40208, Error event queue full

Description

Task arg: The program was already executing an error event when a new event occurred.


Attend the cause of the error event and restart the program.

40209, Error context already consumed

Description

An error event in task arg has occurred. The context of the RAPID instruction that has generated this event is however already consumed.

No error handling is therefore possible to execute.


Attend the cause of the error event and restart the program.


Description

The execution of task arg has been stopped by a runtime error.

Consequences

The program execution is immediately halted.

Probable causes

The program error is considered UNRECOVERABLE so no error recovery attempt by an error handler routine (if used) was allowed. The actual cause of the error may vary, and is likely to be specified in an event log message logged simultaneously as this one.


1) Check other event log messages logged simultaneously to determine the actual cause.

40210, Interrupt removed from queue

Description

All interrupts have been deleted from the interrupt queue in task arg.

Consequences

No trap routines, connected with the interrupt, may be executed.


Description

Task arg: Illegal return code arg from ReaL routine

This is always caused by an internal error in the ReaL routine.





Description

Task arg: Execution could not be restarted

Execution of the program could not be continued after power failure.


Restart the program.


Description

Task arg : Unhandled error


An error occurred in called instruction but was not handled by any

ERROR clause in the program.

Check the previous error or warning in the common log for the cause.


Description

Task arg: Procedure name

arg

is not a RAPID identifier excluding reserved words


The procedure name, must be a legal

RAPID identifier not equal to any of the reserved words of the RAPID language. Change the name expression.


Description

Task arg: Unhandled non-fatal runtime error


A non-fatal runtime error has occurred but was not handled by any ERROR clause.


Description

Task arg: Array dimension number arg out of range (1-arg)


The value of the 'DimNo' parameter of the 'Dim' function must be an integer value in the specified range.


Description

Task arg : Runtime stack overflow

The program is too complex to execute.

Probably the program contains recursive routines.



Description

Task arg: Data is not an array


The 'DatObj' parameter of the 'Dim' function must be an array.


Description

The execution of task arg has been stopped by a runtime error arg.

Consequences


Probable causes

The program error is considered RECOVERABLE but the error was not recovered. The actual cause of the error may vary, and is likely to be specified in an event log message logged simultaneously as this one.


1) Check other event log messages logged simultaneously to determine the actual cause.


Description

Task arg: Unknown interrupt number


Check that the specified interrupt variable has been initialized by

CONNECT, and that the interrupt has been defined using the ISignalDI or other interrupt definition instruction.




Description

Task arg:

Object arg is of non-value type


Use expression or data object of value or semivalue type.


Description

Parameters in arg and arg is not matching (late binding)


Make sure that all procedures that are

called from the same late binding node have matching parameters. I.e. they should be matching concerning base type, mode and required/optional parameters.

40246, Cannot Deactivate Safe Interrupt

Description

Task: arg

It is not possible to deactivate a Safe Interrupt with the instruction

ISleep.

Program ref. arg


Recovery: arg


Description

Task arg: Ambiguous symbol name arg


Installed objects must have names that are unique. Rename the object or change the conflicting name.


Description

Task arg: Error arg when creating sdb entry for arg


An error occurred when the persistent was to be inserted into the shared database. Probably the database is full.



Description

Task arg: Alias

arg of alias

arg not allowed


It is not possible to define an alias type equal to another alias type.

Instead, define two alias types equal to the same atomic or record type.

40254, Symbol definition error

Description

Task arg: 'ANYTYPE#' parameter arg cannot be dimensioned


Remove the dimension specification.

'ANYTYPE#' includes array types.


Description

Task arg: 'ANYTYPE#' only allowed for parameter (not for

arg)


Use another type.


Description

Task arg: 'alt' must not be set for first optional parameter

arg in alternatives list


Make sure that only the second and following in each list of excluding optional parameters are marked as alternatives.


Description

Task arg: REF mode parameter arg cannot be dimensioned

207



Remove the array dimension specification, or change the mode of the parameter.


Description

Task arg: 'switch' parameter arg can not be dimensioned


Remove the array dimension specification, or change the data type of the parameter.


Description

Task arg: 'switch' parameter arg must have transfer mode IN (specified value

arg)


Remove the parameter transfer mode specifier. If IN transfer mode is not sufficient, change the data type of the parameter.


Description

Task arg: 'switch' only allowed for optional parameter

(not for arg)


Change the parameter into an optional parameter, or change the data type of the parameter. If the object is not a parameter, change the data type.


Description

Task arg: Value type class for arg must be one of

REAL_SYMVALTYP_VAL, _SEMIVAL, _NONVAL or

_NONE (specified value arg)


Change the value type class.

208


Description

Task arg: Too many array dimensions for arg

(specified value arg)


An array may have at most 3 dimensions.


Description

Task arg: Symbol name

arg

is not a RAPID identifier excluding reserved words


The names of installed objects, including parameters and components, must be legal RAPID identifiers not equal to any of the reserved words of the RAPID language. Change the name.


Description

Task arg: Missing C function for arg


A C-function that executes the ReaL function being defined, must be specified.


Description

Task arg: Missing value initialization function for

arg


A value initialization function must be specified.


Description

Task arg: arg is not a data type name (object

arg)

The specified name identifies an object


other than a type.



Description

Task arg: arg is not a value data type (object

arg)

Only record components, alias types, variables and 'VAR' mode parameters may be of semi-value or non-value type.



Description

Task arg: Missing value conversion function for arg


A value conversion function must be specified for a semi-value type.


Description

Task arg: Not enough memory for value of data

arg


More memory required.


Description

Task arg: Private type

arg can only be semi-value or non-value type (specified value

arg)


Change the value type class.


Description

Task arg: Private type

arg size must be multiple of 4 (specified value arg)




All RAPID types must have a size that is

a multiple of four. Change the specified type size.


Description

Task arg: Persistent type mismatch for arg


There is already a persistent data with the same name but with another data type. Rename the persistent, or change its data type.


Description

Task arg: Unknown data type name arg for

arg


There is no data type (or other object) with the specified name.


Description

Task arg: Unknown parameter transfer mode arg for

arg


The specified parameter transfer mode is not one of IN, 'VAR', 'PERS', 'INOUT' or

REF. Use corresponding REAL_SYMPARMOD_x.


Description

Task arg: Unknown symbol definition type arg

The symbol definition type tag does not specify one of the allowed symbol types (REAL_SYMDEF_x).

209



40277, Undo Aborted

Description

Task arg

The program execution was stopped while processing the UNDO statements.

UNDO was not fully executed.

The routine arg was executing when UNDO was stopped.


If the processing of UNDO takes too long, try to remove timeconsuming instructions such as TPWrite from the UNDO-clause.

If the undo processing never seems to finish, make sure any loops in the undo-statements are correct.


Description

Task arg

The processing of UNDO was aborted due to an EXIT-statement in the routine arg.




Description

Task arg

The processing of UNDO was aborted due to a run-time error in routine arg.



Investigate the cause of the error.


Description

Task arg

The program execution of UNDO statements was aborted due to edit operation.

40301, File access error

Description

Task arg is trying to access file arg, but failing.

Consequences

No data in the file may be accessed.

Probable causes

File may be write protected.


1) Check if the file is write protected, and in such case change the setting.


Description

Task arg is trying to access file arg, but does not find file or directory.

Consequences

If the missing file is a module, no automatic loading to a task is possible.

Probable causes

-File may not have been correctly copied to the target directory.

-File or directory may have incorrect name.


1) Make sure the file and directory names are correct.


Description

Task arg

The instructions BREAK, RAISE, RETURN and STOP are not allowed to use in an undo-clause or any routine that is called from an undo-clause.

The instruction arg was found in UNDO context when executing the routine arg.


Avoid executing the instruction when in undo-context.


Description


Consequences


Probable causes

No storage space available on device.


1) Make sure there is enough storage space available.


Description




Consequences


Probable causes

-File may be write protected.

-File or directory may have incorrect name.

-No storage space available on device.


1) Check if the file is write protected, and in such case change the setting.

2) Make sure the file and directory names are correct.

3) Make sure there is enough storage space available.

40322, Load error

Description

Task arg: RAPID syntax

error(s) in file

arg


The source file to be loaded contains

RAPID syntax errors. Correct the source

file.


Description

Task arg: Syntax error(s) in header in file

arg


The source file to be loaded contains syntax error in the file header. Correct the source file. The syntax errors are logged in a separate file.


Description

Task arg: Keywords not defined in specified language (file

arg)


Cannot load RAPID source code in the national language specified in the file header.


Description

Task arg:


A big enough free program memory block is not available. The ordered operation could not be completed.

Probable causes

The program memory is full or fragmentated.


Check if large data structures could be split into smaller blocks.

Use of installed modules can save program memory.


Description

Task arg : Parser stack full (file

arg)


The program is too complex to load.


Description

Task arg: Not current RAPID version (file

arg)


Cannot load RAPID source code of the version specified in the file header.


Description

Task: arg

Program memory is full.

arg


The module arg could not be loaded because the program memory is full.

Recovery: arg

40329, Module installation failure

Description

Task: arg It is not possible to install a module from file arg.

Consequences

The module will not be installed.

Probable causes

The RAPID module may have RAPID errors.


1) Check the event messages in the Elog domain RAPID

2) Correct the RAPID errors and make a P-start.

211


40330, Rapid errors in installed module

Description

Task: arg. Module (line/column): arg

There is an error with symbol: arg.

Consequences

The module will not be installed.


Description

Operand types arg and arg for the '/', 'DIV' or 'MOD' operator not equal


The two operands of the '/', 'DIV' or 'MOD' operators must have equal type. Check the operand types.


Check the mechanical unit component of the workobject.

40354, A copy of a dynamic loaded module has been saved.

Description

Task: arg

A dynamic loaded module arg has been changed.

The module is lost when PP is set to main.

A copy of the changed module is saved on arg

Probable causes

- A dynamic loaded module has been changed.

- PP is set to main.

- The dynamic loaded module is removed.

- A copy of the changed module is saved.


If the changes shall be saved, replace the original file with the copy.


Description

Operand types arg and arg for the '<', '<=', '>' or '>=' operator not equal


The two operands of the '<', '<=', '>' or '>=' operators must have equal type. Check the operand types.

40351, Memory allocation error

Description

Task arg: Failed to allocate hash table, use linear list


40355, A Stop/QStop event routine has been stopped.

Description

Task: arg

A arg event routine has been stopped by an external stop command.

Any running Stop/QStop event routines will be stopped after arg ms when controller receives second stop command.


Keep all event routines short and free from RAPID instructions of type

WaitTime, WaitDI, etc.

40352, Memory allocation error

Description

Task arg: Failed to update persistent expression, keep old one


40357, Missing Error Handler

Description

There is no error handler that deals with the process error for task arg.

Consequences

The program will not be able to execute past the next move instruction.

Probable causes

The error handler is missing.


Add an error handler. The error handler should include the StartMove

(StartMoveRetry) instruction.

40353, Mechanical Unit arg Missing!

Description

The mechanical unit component of the workobject arg is faulty.

Probable causes

- No mechanical unit is defined.

- The mechanical unit defined can not be found.

- The robot can not move the workobject by itself.

40358, RMQ message discarded

Description

A RMQ message was discarded in task arg. arg received a RMQ message that couldn't be handled.



Consequences

The RMQ message was discarded without any notification to the sender.

Probable causes

There can be several different reasons.

1. No interrupt is connected to the type of the received message.

2. No interrupt could be created because the interrupt queue was full.

3. The received message was corrupt.


Make sure that the task has connected an interrupt to all types of messages that is possible to receive. Read about IRMQMessage in the

RAPID reference maunal.

40508, Orientation Value Error

Description

Task: arg

Wrong orientation value in arg.

Program Ref. arg


All used orientations must be normalized, i.e. the sum of the quaternion elements squares must equal 1.

40502, Digital Input Break

Description

Task: arg

A digital input interrupted the execution.

Program Ref. arg


Recovery: arg

40511, Parameter Error

Description

Task: arg

The parameter arg in arg is specified with a negative value.

Program Ref. arg


The parameter must be set to a positive value.

40512, Missing External Axis Value

Description

Some active external axis have incorrect or no order value.


Reprogram the position.


Description

Task: arg

arg arg arg


Recovery: arg

40513, Mechanical Unit Error

Description

Task: arg

Not possible to activate or deactivate mechanical unit. Previous message may contain more information.

Program Ref. arg

40506, System Access Error

Description

Task: arg

arg arg arg


Recovery: arg

40514, Execution Error

Description

Task: arg

The robot is too far from path to perform StartMove of the interrupted movement.

Program Ref. arg


Position the robot to the interrupted position in the program.

Recovery: arg

40507, Limit Error

Description

Task: arg

Can not step further back on path arg.

Program Ref. arg


Recovery: arg

40515, Type Error

Description

Task: arg

Illegal data type of argument for parameter arg.




Change the parameter to a legal type. Make sure the value type is value or semivalue.

40525, Conveyor Access Error

Description

Task: arg

No single number defined.

Program Ref. arg


Description

Task: arg

Expected type differs from read type in arg.

Program Ref. arg


Check the type in the argument.


Description

Task: arg

The mechanical unit arg is not a single.

Program Ref. arg

40519, End Of File

Description

Task: arg

End of file was found before all bytes were read in arg.

Program Ref. arg


Recovery: arg


Description

Task: arg

Stop watch overflow.

Program Ref. arg


Recovery: arg

40523, Mechanical Unit Conflict

Description

Not possible to deactivate mechanical unit arg due to the configuration.



40527, File Access Error

Description

Task: arg

Unable to open arg.

Program Ref. arg

Probable causes

- The I/O device reference is already in use.


- If the I/O device reference is already in use, close it or use another.

Recovery: arg


Description

Task: arg

File or serial channel is not open.

ProgramRef. arg

Probable causes

- The I/O device reference is not open, or has already been closed


- Check that device is open

Recovery: arg


Description

Task: arg

The conveyor is not activated.

Program Ref. arg


Recovery: arg


Description

Task: arg

Could not access the file arg.

Program Ref. arg

Probable causes

- The path or filename is wrong.

- The I/O device reference is already in use.

- The maximum number of simultaneously opened files is exceeded.

- The disk is full.




- Check the path or filename.

- If the I/O device reference is already in use, close it or use another.

- Check the disk space.

Recovery: arg


Description

Task: arg

The number of characters, parameter arg in WriteBin, you want to write to the serial channel is greater than the size of the array containing the characters to be written.

Program Ref. arg


Make the array bigger or decrease the parameter.


Description

Task: arg

The array arg in WriteBin is smaller than 0 or greater than 255.

Program Ref. arg


Change the size of the array to be 0 - 255.

40534, Timeout

Description

Task: arg

A timeout interrupted the execution.

Program Ref. arg


Recovery: arg


Description

Task: arg

The data you was trying to read in the file was not a numeric type.

Program Ref. arg


Recovery: arg


Description

Task: arg

Too many pending read requests.

Program Ref. arg


Description

Task: arg

The serial channel is not open, or you are trying to use the instruction on a file.

Program Ref. arg


- Open the serial channel.

- Check that the instruction is used on a serial channel.

Recovery: arg

40538, Max Time Expired

Description

Task: arg

The programmed waiting time has expired.

Program Ref. arg


Recovery: arg


Description

Task: arg

Not allowed option in this task.

Program Ref. arg


Description

Task: arg

arg is not a directory.

ProgramRef. arg


Check that the path is the correct path to the directory you want to open.

Recovery: arg


Description

Task: arg

Directory arg is not accessible.

Program Ref. arg


Check the directory you are trying to open.

Recovery: arg




Description

Task: arg

Could not access the file system arg.

Program Ref. arg


- Check the path and filename.

Recovery: arg

Could not remove the file arg.

Program Ref. arg


- Check the path.

- Check if you have write permission for the file.

- Check write and execute permission for the directory under which the file you want to remove is located.

Recovery: arg


Description

Task: arg

You can not open arg.

Program Ref. arg

Probable causes

There are too many directories already open.


Close one of the already open directories.

Recovery: arg


Description

Task: arg

Could not rename the file arg.

Program Ref. arg


- Check the path.

- Check write permission for the file you want to rename.

- Check write and execute permission for the directory under which the file you want to remove is located.

Recovery: arg


Description

Task: arg

Could not create the directory arg.

Program Ref. arg


- Check the path.

- Check write and execute permission for the directory under which the new directory should be created.

Recovery: arg


Description

Task: arg

Could not copy the file arg.

Program Ref. arg


- Check the path.

- Check write permision for the directory that you want to copy the file to.

- Check the available space.

Recovery: arg


Description

Task: arg

Could not remove the directory arg.

Program Ref. arg


- Check the path.

- Check write and execute permission for the directory under which the directory you want to remove is located.

Recovery: arg


Description

Task: arg

Unknown mechanical unit arg.

The data of type mecunit is unknown for the system.

Program Ref. arg

Probable causes

Data of type mecunit has been declared in the program.


Remove the declaration of mecunit data in the program and use one of the predefined data of type mecunit (automatic defined by the system).


Description

Task: arg


40555, I/O Error

Description

Task: arg

Unable to read I/O signal.

Program Ref. arg

40556, I/O Error

Description

Task: arg

Unable to write I/O signal.

Program Ref. arg

40557, I/O Error

Description

Task: arg

Configuration error for I/O signal.

Program Ref. arg


Check the IO signal configuration or alias definition.

40558, I/O Error

Description

Task: arg

Unable to read the I/O signal arg in unit arg.

Program Ref. arg

40559, I/O Error

Description

Task: arg

Unable to write to the I/O signal arg in unit arg.

Program Ref. arg


Description

Task: arg

Can't save program module arg.

Program Ref. arg


Description

Task: arg

arg is not a module name.

Program Ref. arg

Consequences

You can not unload, save or erase this module.




Check the name of the module.


Description

Task: arg

Unknown axis number for the mechanical unit arg.

Program Ref. arg


Check the value for argument AxisNo.

Recovery: arg


Description

Task: arg

Mechanical unit arg is not active.

Program Ref. arg


Activate the mechanical unit.

Recovery: arg

40564, Argument Error

Description

Task: arg

Orientation definition error.

GripLoads attach frame in tool or work object (user + object) is unnormalized.

Program Ref. arg


Check the orientation. All used orientations must be normalized i.e. the sum of the quaternion elements squares must equal 1.


Description

Task: arg

Both arguments must be > 0.

Program Ref. arg


Check the value of the arguments.


Description

Task: arg

Both arguments must be > 0 and <= 100.

Program Ref. arg

217



Check the value of the arguments.


Description

Task: arg

Quaternion error.

Program Ref. arg


Check the aom component of loaddata.


Description

Task: arg

Axis may not have a value less than 0.

Program Ref. arg


Change to a positive value.


Description

Task: arg

The argument AccMax must be set if the argument AccLim is set to

TRUE.

Program Ref. arg


Set a value to argument AccMax.


Description

Task: arg

The argument DecelMax must be set if argument DecelLim is set to

TRUE.

Program Ref. arg


Set a value to argument DecelMax.


Description

Task: arg

The value of parameter AccMax is too low.

Program Ref. arg


Increase the value of parameter AccMax.

Recovery: arg


Description

Task: arg

The value of parameter DecelMax is too low.

Program Ref. arg


Increase the value of parameter DecelMax.

Recovery: arg


Description

Task: arg

The value of argument On is too low.

Program Ref. arg


Increase the value of argument On.

Recovery: arg

40574, Search Warning

Description

Task: arg

Number of hits during search was arg.

Before performing next search, make sure that TCP is moved back to the start position of the search path.

Program Ref. arg

Consequences

If no repositioning is done, before restart of circular search, movement that can cause damage might occur.


Recovery: arg

40576, ParId Error

Description

Task: arg

The array size of argument AxValid is not equal to number of axes.

Program Ref. arg


Check the size of the array.


Description

Task: arg

This parameter identification can not be done in this robot type.

Program Ref. arg




Description

Task: arg

The optional argument PayLoad is missing. For PayLoad identification the argument must be given.

Program Ref. arg


Give a value to the argument PayLoad.


Description

Task: arg

The optional argument PayLoad may only be used for PayLoad identification.

Program Ref. arg


Remove the argument PayLoad.


Description

Task: arg

Faulty state for LoadIdInit.

Program Ref. arg


Check the whole ParId sequence.


Description

Task: arg

Faulty state for ParIdMoveSeq.

Program Ref. arg




Description

Task: arg

Faulty state for LoadIdInit.

Program Ref. arg





Description

Task: arg

Backward execution not allowed.

Program Ref. arg


Description

Task: arg

ParIdMoveSeq / Parameter NextMove:

Faulty array size.

Program Ref. arg




Description

Task: arg

Missed argument WObj in LoadId for PayLoad with roomfix TCP.

Program Ref. arg


Add argument WObj.


Description

Task: arg

Not allowed argument WObj. The argument is only to be used for

PayLoad with roomfix TCP.

Program Ref. arg


Remove argument WObj.

40587, ParId error

Description

Task: arg

ParIdMoveSeq / Parameter MoveData:

Faulty array size.

Program Ref. arg




Description

Task: arg

ParIdMove / Parameter StartIndex:

219


Faulty StartIndex.

Program Ref. arg


Check the StartIndex.


Description

Task: arg

ParIdMove / Parameter StartIndex:

Point at negative movetype.

Program Ref. arg

40594, User Error During Load Identification

Description

Task: arg

Error resulting in raise of PP to the beginning of the parameter identification procedure.

Program Ref. arg


Start the identification procedure from the beginning again.

Recovery: arg

40590, ParId error

Description

arg arg


arg


Description

Task: arg

Unknown type of load identification.

Program Ref. arg


Check the argument LoadIdType.


Description

Task: arg

Unknown type of parameter identification.

Program Ref. arg


Check the argument ParIdType.

40596, Program Stop During Load Identification

Description

Task: arg

Any type of program stop during load identification is not allowed.

Program Ref. arg


Restart the program execution again for load identification from beginning.

40592, Program Stop During Load Identification

Description

Task: arg

No type of program stop is allowed during load identification.

Program Ref. arg


Start the identification procedure from the beginning again.

Recovery: arg

40597, Speed Override

Description

Task: arg

Speed override is not 100 percent.

Program Ref. arg


- Change the speed override to 100.

- Restart the program execution again for load identification from beginning.

40593, Power Fail During Load Identification

Description

Task: arg

A Power Fail during load identification results in faulty load result.

Program Ref. arg


Restart the program execution again with the same run mode (without

PP move) for load identification from the beginning.

Recovery: arg

40598, Program Stop during Load Identification

Description

No type of Program Stop is allowed during the Load Identification movements.

Consequences

Not possible to complete the Load Identification sequence.

Note that some axes for the actual mechanical unit are now in independent mode.



Probable causes

Interrupt of the Load Identification sequence with Program Stop or release of the Enable Device.


1) Restart the program. The Load Identification service routine will then start from beginning.

2) Also possible to cancel the Service Routine to completly skip the

Load Identification.


Description

Argument arg may not have a negative value.


Set argument arg to a positive value.


Description

Task: arg

Not allowed to change run mode from forward to backward or vice versa when running a circular movement.

Program Ref. arg


If possible, select the original run mode and press start to continue the stopped circular movement. If this is not possible, move robot and program pointer for a new start.


Description

Task: arg

Not allowed to step backwards with this move instruction.

Program Ref. arg

Consequences

Step backwards to a position defined with another tool or work object could result in faulty path.


Check tool and work object.


Description

Task: arg

No argument programmed for the name of the output signal.

Program Ref. arg


Possible to set one position fix IO such as digital, group of digital or analog output signals during the robot movement.


Description

Task: arg

Optional argument arg can only be combined with output signal argument arg.

Program Ref. arg


Check and change the arguments.


Description

Task: arg

Orientation definition error in arg.

Program Ref. arg


All used orientations must be normalized i.e. the sum of the quaternion elements squares must equal 1.


Description

Task: arg

Argument arg is not 0 or 1.

Program Ref. arg


Digital signals can only be set or checked to 0 or 1.


Description

Task: arg

Argument \WObj specifies a mechanical unit with too long name.

Program Ref. arg


Use max. 16 characters to specify the name of a mechanical coordinated unit.


Description

Task: arg

Argument arg is not an integer value.

Program Ref. arg


Digital group of in/out signals, process identity or process selector can only have an integer value.




Description

Task: arg

Argument arg is outside allowed limits.

Program Ref. arg


Used group of digital in/out signals can only be set or checked within

0 to arg according to configuration in system parameters.

Recovery: arg


Change the value for Time to a value greater than or equal to 0.01 s.


Description

Task: arg

Argument arg is not between 0 and 2.

Program Ref. arg


Specify the flank to generate the interrupt.

0 = Negative flank (high -> low).

1 = Positive flank (low -> high).

2 = Both negative and positive flank.


Description

Task arg:

One of the arguments SetValue, SetDvalue, ScaleValue, CheckValue or CheckDvalue is outside allowed limits.

Program Ref. arg

Probable causes

The analog signal can only be set/checked within arg to arg according to the I/O system parameter configuration.


Check the RAPID program or the I/O configuration.

Recovery: arg


Description

Task: arg

The robot is outside its limits.

Program Ref. arg

Probable causes

- Axis outside working area.

- Limits exceeded for at least one coupled joint.


Recovery: arg


Description

Task: arg

Argument arg have too large negative value.

Program Ref. arg


Set argument arg to arg or more.


Description

Task: arg

The value of argument Time is too low for cyclic interrupts.

Program Ref. arg


Change the value for Time, to a value greater than or equal to 0.1 s.


Description

Task: arg

The value of argument Time is too low for single interrupts.

Program Ref. arg

40631, Instruction Error

Description

Task: arg

Too many move instructions in sequence with concurrent RAPID program execution.

Program Ref. arg


Edit the program to max. 5 MoveX \Conc in sequence on the basic execution level of the program.


Description

Task: arg

No move instructions with concurrent RAPID program execution are allowed within the StorePath-RestoPath part of the program.

Program Ref. arg


Edit the program so it does not contain any MoveX \Conc instructions within the StorePath-RestoPath part of the program.



40634, Reference Error

Description

Task: arg

The signal arg is unknown in the system.

Program Ref. arg

Probable causes

If the signal is defined in the RAPID program, it must be connected to the configured signal with instruction AliasIO.


All signals (except AliasIO signals) must be defined in the system parameters and can not be defined in the RAPID program.

Program Ref. arg


The sensor is busy with an other function.

Recovery: arg

40640, Sensor Error

Description

Task: arg

Unknown command.

Program Ref. arg


The function requested from the sensor is unknown.

Recovery: arg


Description

Task: arg

No measurement from sensor.

Program Ref. arg


Requested data is not available.

Recovery: arg


Description

Task: arg

Illegal variable or block number.

Program Ref. arg


Requested variable or block is not defined in the sensor.

Recovery: arg


Description

Task: arg

Not ready yet.

Program Ref. arg


Requested function is not ready yet.

Recovery: arg


Description

Task: arg

External alarm.

Program Ref. arg


Alarm from external equipment.

Recovery: arg


Description

Task: arg

General error.

Program Ref. arg


General error has occurred which is not specifically connected to the requested action. Read the block "Error log" if the function is available.

Recovery: arg


Description

Task: arg

Camera alarm.

Program Ref. arg


Some error has been detected in the camera. Run Camcheck to test if the camera is OK.

Recovery: arg


Description

Task: arg

Sensor busy, try later.




Description

Task: arg

Temperature alarm.

Program Ref. arg


The camera is overheated it needs more cooling air or water.

Recovery: arg

Probable causes

Executing of instruction StorePath while searching is active.


Not possible to use StorePath in TRAP, event or service routine while searching is active on motion base path level.

If using interupts in the program for execution of TRAPs, such interrupt must be deactivated during any search.

E.g. ISleep - SearchL - IWatch


Description

Task: arg

Value out of range.

Program Ref. arg


The value of the data sent to the sensor is out of range.

Recovery: arg

40649, Path Limitation

Description

Task: arg

arg is already done or executing. Instruction arg must first be executed, before a new arg can be done.

Program Ref. arg


Check the RAPID program.


Description

Task: arg

Camera check failed.

Program Ref. arg


The CAMCHECK function failed. The camera is broken. Send it for repair.

Recovery: arg

40650, Wrong Combination Of Parameters

Description

Task: arg

Optional parameters and switches are not used in a correct combination.

Program Ref. arg


- No optional parameters and no switch keep the old coordinate system.

- The switch Old has the same function.

- RefPos or RefNum has to be defined with Short, Fwd or Bwd.


Description

Task: arg

Communication time out.

Program Ref. arg


Increase the time out time and check the connections to the sensor.

Recovery: arg

40651, Use Numeric Input

Description

Task: arg

Use numeric input for the position instead of a robtarget.

Program Ref. arg


The position can not be defined with a robtarget for robot axes.

Use the optional parameter for numeric input of the position.

40648, Search Error

Description

Task: arg

Not allowed to do StorePath while searching is active on motion base path level.

Program Ref. arg

Consequences

Program is stopped.

40652, Axis Is Moving

Description

Task: arg

A Robot axis, an external axis or an independent axis is moving.

Program Ref. arg


All Robot axes, external axes and independent axes have to stand still.



Use MoveL with Fine argument for the Robot and external axes.

Use IndRMove for the independent axes.

Recovery: arg

40654, Axis Not Active

Description

Task: arg

The axis destination position to move to is undefined (9E9) or the axis to move is not active at present.

Program Ref. arg

Probable causes

1)The position to move to has been programmed or ModPos with not active mechanical unit

2) The mechanical unit is not active at present


The mechanical unit has to be activated before programming, ModPos or execution of this instruction.

Recovery: arg

Before performing next search, make sure that TCP is moved back to the start position of the search path.

Program Ref. arg

Consequences

If no repositioning is done, before restart of circular search, movement that can cause damage might occur.


Recovery: arg

40662, Invalid Worldzone Type

Description

Task: arg

The switch \ arg must be associated with a arg worldzone.

Program Ref. arg


If use of switch \Temp, the datatype must be wztemporary in

WorldZone.

If use of switch \Stat, the datatype must be wzstationary in WorldZone.

40655, Axis Is Not Independent

Description

Task: arg

The axis is not in independent mode.

Program Ref. arg

Consequences

It is only possible to get the status from an axis in independent mode.


Set the axis to independent.

Recovery: arg

40663, World Zone Not In Use

Description

Task: arg

The argument arg of the instruction arg refers to a not used worldzone.

Program Ref. arg


The worldzone must have been defined and activated by a WZLimSup or WZDOSet instruction.


Description

Task: arg

Parameter arg can only be used, if parameter arg is greater than zero.

Program Ref. arg


Parameter arg has effect only in the first TriggX instruction, in a sequence of several TriggX instructions, that controls the speed proportional AO signal.

40664, World Zone Already In Use

Description

Task: arg

The ' arg ' worldzone has already been defined and activated.

A world zone can only be defined once.

Program Ref. arg


Use a worldzone with another name.


Description

Task: arg

The signal arg for the SearchX instruction is already high at the start of searching or the I/O-unit for the signal isn't up and running for the occasion.

40665, Too Many World Zones

Description

Task: arg

It is not possible to add the world zone arg . The world zone table is full.

Program Ref. arg


Check the RAPID program to see if any word zone might be removed.



40666, Illegal World Zones

Description

Task: arg

Worldzone ' arg ' is defined locally in current routine.

Program Ref. arg


Define the world zone as global or local in module.

40667, Illegal World Zones

Description

Task: arg

WorldZone arg is not entire data reference.

Program Ref. arg


Check the value of argument WorldZone.

40668, Shapedata Not In Use

Description

Task: arg

The ' arg ' argument of the instruction arg must refer to a defined shapedata.

Program Ref. arg


A shapedata is used to store a volume definition. It must have been defined by WZBoxDef, WZSphDef or WZCylDef before it can be used by

WZLimSup or WZDOSet.

40669, World Zone Too Small

Description

Task: arg

At least one side or radius is less than the minimal allowed in instruction arg .

Program Ref. arg


Check previous volume definition instruction.

40670, Invalid World Zone

Description

Task: arg

The index of the world zone argument arg in arg is not a valid index defined by WZLimSup or WZDOSet.

Program Ref. arg



226

40671, Illegal Use Of World Zone

Description

Task: arg

The argument ' arg ' for arg must be a temporary world zone.

Program Ref. arg


Check the argument..

40672, World Zone Already In Use

Description

Task: arg

It is not possible to add the world zone arg . Another world zone with the same name is already defined in the system.

Program Ref. arg


Check the name of the world zone.

40673, I/O Access Error

Description

Task: arg

The signal given in parameter arg is write protected for RAPID access.

Program Ref. arg


Select other user signal or change the access mode for the signal.

40674, I/O Access Error

Description

Task: arg

The signal given in parameter arg is not write protected for user access from teach pendant or RAPID.

Program Ref. arg


Change the access mode to system type for the signal in the I/O configuration.


Description

Not allowed changing the run mode from forward to backward or vice versa when running an invisible trap routine.


If possible, select the original run mode and press start to continue.


Description

Task: arg



The DeltaJointVal for robot axis arg is <= 0.

Program Ref. arg


Check the value for DeltaJointVal. The DeltaJointVal for all axes to supervise must be > 0 mm or degrees.


Description

Task: arg

The DeltaJointVal for external axis arg is <= 0.

Program Ref. arg


Check the value for DeltaJointVal. The DeltaJointVal for all axes to supervise must be > 0 mm or degrees.


Description

Task: arg

LowJointVal is higher than or equal to HighJointVal for robot axis arg.

Program Ref. arg


Check the values for HighJointVal and LowJointVal. The HighJointVal must be higher than the LowJointVal for all axes with defined high or/ and low limits.


Description

Task: arg

LowJointVal is higher than or equal to HighJointVal for external axis

arg.

Program Ref. arg


Check the values for HighJointVal and LowJointVal. The HighJointVal must be higher than the LowJointVal for all axes with defined high or/ and low limits.


Description

Task: arg

Error in used WZLimJointDef. It is not allowed to specify limitation of not active axis arg.

Program Ref. arg


Set the argument LowJointVal and HighJointVal to 9E9 for the actual axis.

40698, Read error

Description

Task arg is trying to read file arg, but is failing.

Consequences

It was not possible to read/load arg.

Probable causes

If trying to access file on FTP mounted disc, make sure that the size of

arg isn't larger then the maximum file size configured in the FTP protocol settings.

40699, Program Memory Full

Description

The task arg, has only arg bytes in its program memory.

Consequences

It was not possible to load module arg.


1. Remove some other module and try again.

2. Check if large data structures could be split into smaller blocks

3. Use of installed modules can save program memory.

40700, Syntax Error

Description

Task: arg

Syntax error.

arg


Description

Task: arg

Error in used WZHomeJointDef. It is not allowed to specify supervision of not active axis arg

Program Ref. arg


Set the argument MiddleJointVal to 9E9 for the actual axis.

40701, Program Memory Full

Description

The task arg , has only arg free bytes in its user space.

Consequences

The ordered operation could not be completed.


1. Remove some modules and try again.

2. Check if large data structures could be split into smaller blocks



3. Use of installed modules can save program memory.


More syntax errors will follow this.

40702, File Not Found

Description

Task: arg

The file arg was not found.

Program Ref. arg


- Check the file path and the file name.

- Check if the file exists.

Recovery: arg

40706, Load Error

Description

Task: arg

The program module is already loaded.

Program Ref. arg

Probable causes

The module name in the head of the file arg already exists in the program memory.


Recovery: arg

40703, Unload Error

Description

Task: arg

The program module could not be unloaded.

The reason is that the module is changed but not saved.

Program Ref. arg


The instruction UnLoad:

Use the optional switch ErrIfChanged, without recover from this situation, in an Error handler.

Recovery: arg

40707, I/O Unit Name Invalid

Description

Task: arg

The unit name arg does not exist.

Program Ref. arg


- Check if the unit name is misspelled.

- Check if the unit is defined.

Recovery: arg

40704, UnLoad Error

Description

Task: arg

arg

The program module couldn't be unloaded.

Program Ref. arg

Probable causes

- Module not loaded with Load instr.

- Not same file path as used for Load


- Check if the program module has been loaded with the instruction

Load.

- Check if the file path and name are the same in the UnLoad and Load instruction.

Recovery: arg

40705, Syntax Error

Description

Task: arg

Syntax error

arg

40708, I/O Unit Is Not Enabled

Description

Task: arg

I/O unit arg was not enabled.

Program Ref. arg

Probable causes

The maximum period of waiting time was too short.


Increase the waiting time or make a retry.

Recovery: arg

40709, I/O Unit Is Not Disabled

Description

Task: arg

I/O unit arg was not disabled.

Program Ref. arg

Probable causes

The maximum period of waiting time was too short.


Increase the waiting time or make a retry.

Recovery: arg




Description

Task: arg

The argument arg is an expression value, is not present or is of the type switch.

Program Ref. arg


Change the parameter arg to a valid one.

Recovery: arg

40711, Alias Type Error

Description

Task: arg

The data types for the arguments FromSignal and ToSignal must be the same and must be of signalxx type.

Program Ref. arg


Change the type to a valid one (signalai/ao, signaldi/do, signalgi/go).

Recovery: arg


This is probably an off-line generated "dummy" position (undefined orientation), which needs to be modified with modpos.

40720, Alias IO Installation

Description

The system could not refresh all IO signals as RAPID symbols.

Consequences

No IO signals can be used in a RAPID program.

Probable causes

- Incorrect IO configuration

- Incorrect task configuration



40712, Event Routine Error

Description

Task: arg

Too many event routines, the routine arg will not be executed.


Encapsulate the routine in one of the others that are specified for the same event.

40721, IO Installation

Description

Task arg:

The system could not refresh all IO signals as RAPID symbols.

Consequences

No IO signals can be used in a RAPID program.

Probable causes

- Incorrect IO configuration




40713, Alias Define Error

Description

Task: arg

The signal in argument FromSignal: arg, must be defined in the IO configuration and the signal in argument ToSignal: arg, must be declared in the RAPID program and not defined in the IO configuration.

Program Ref. arg


Check the IO configuration and the RAPID program.

Recovery: arg

40722, Mechanical Units

Description

The system could not refresh all mechanical units as RAPID symbols.

Consequences

No mechanical units can be used in a RAPID program.

Probable causes

- Incorrect motion configuration





Description

Task: arg

Orientation definition error in arg .

Program Ref. arg

40724, Save or Erase Error

Description

Task: arg

The program module arg could not be saved or could not be erased.

Program Ref. arg




- Check the spelling of the module name

- Check if the module is loaded.

Recovery: arg


Description

Task: arg

The reference to the load session is not valid.

Program Ref. arg


Check if the specified reference is the same as in StartLoad

Recovery: arg

40732, Value Error

Description

Task: arg

The value of the argument arg for signal arg is below its minimum logical value.

Program Ref. arg


Change the argument or change the min logical value parameter for the signal.

Recovery: arg

40727, Save Error

Description

Task: arg

Missing file source arg.

Program Ref. arg


Use FilePath argument to specify the file destination.

Recovery: arg


Description

Task: arg

The value of the argument arg for signal arg is below the value for argument arg.

Program Ref. arg


Change the values of the arguments.

40728, Frame Error

Description

Task: arg

Unable to calculate new frame.

Program Ref. arg

Probable causes

The positions have not the required relations or are not specified with enough accuracy.


Check if the positions are too close or not specified with enough accuracy.

Recovery: arg

40734, Symbol Definition Error

Description

Task: arg

The string in text table arg at index arg is too long.

Program Ref. arg


Change the file for the text table and perform a cold start.


Description

The axis is not defined.


The axis has to be defined, before this instruction is executed.


Description

Task: arg

The value of the argument arg for signal arg is above its maximum logical value.

Program Ref. arg


Change the argument or change the maximum logical value parameter for the signal.

Recovery: arg

40736, Mechanical Unit Error

Description

Task: arg

It is not possible to define a payload on the robot with this instruction.

Program Ref. arg


Use the instruction GripLoad instead of MechUnitLoad.



40737, Symbol Definition Error

Description

Task: arg

The requested text or text package does not exist. Text table arg, Index

arg.

Program Ref. arg


Check the arguments.

Recovery: arg

40738, I/O Error

Description

Unable to access the I/O signal arg on unit arg .

Impossible to restart.

Probable causes

The connection with the I/O module is broken.


Re-establish the connection with the I/O unit. To make it possible to restart the program move PP to a safe restart position.

Instruction arg may only be used in an event routine.

Program Ref. arg


Remove the instruction.


Description

Task: arg

The timing parameter DipLag is larger than the system parameter

Event preset time.

Program Ref. arg


Increase the system parameter Event preset time or check the equipment dip lag (delay) compensation.

Recovery: arg


Description

Task: arg

Not a valid subtype in argument arg.

Program Ref. arg


Check the argument.


Description

Task: arg

None of the option arguments DO1, GO1, GO2, GO3 or GO4 are specified.

Program Ref. arg


Specify at least one of the arguments.


Description

Task: arg

Invalid value in arg in argument arg.

Program Ref. arg


Check the argument.


Description

The PERS variable specified in the instruction TriggStopProc can not be updated, because it does not exist any more.

Probable causes

The program module with the PERS variable is probably removed from the program memory.


Check if the module with the PERS variable is removed, if so put it back.

40741, Context Error

Description

Task: arg


Description

Task: arg

arg is less than arg in argument arg.

Program Ref. arg


Check the argument.


Description

Task: arg

arg TRUE in parameter arg in combination with conveyor coordination.



Program Ref. arg


Cannot use fine points when leaving conveyors after coordinated stoppoint.

Use a zone instead.

40747, Access Error

Description

Task: arg

Can not read or write to the system parameter arg. The parameter is internal and protected from reading and writing.

Program Ref. arg


Recovery: arg


Description

Task: arg

The data to write from parameter CfgData to the system parameter, is outside valid limits.

Program Ref. arg


Recovery: arg

Because of power fail in executed Load or StartLoad ... WaitLoad instruction, the RAPID program memory is inconsistent.

*** TO REPAIR DO P-START ***

Program Ref. arg


Important to do P-start, because the RAPID program memory is destroyed:

- Faulty init value of PERS variables

- Reduction of the available program memory size


Description

Task: arg

There are no arguments given.

Program Ref. arg


If you want a limitation set the optional argument On with a value, otherwise set to Off.


Description

Task: arg

Instruction arg may only be used in a trap routine.

Program Ref. arg




Description

Task: arg

It is not possible to execute StartMove when the robot is moving.

Program Ref. arg


Recovery: arg


Description

Task: arg

Instruction arg may only be used in a trap routine ordered through instruction arg.

Program Ref. arg


Check that INTNO has the interrupt number used by arg.


Description

Task: arg

Some load session with StartLoad - WaitLoad has not been finished.

Program Ref. arg


Finish the load session with WaitLoad, cancel it with CancelLoad or set PP to main.

Recovery: arg


Description

Task: arg

The load session you are trying to cancel is not in use.

Program Ref. arg


Recovery: arg

40753, Memory Fault

Description

Task: arg



40758, I/O Error

Description

Unable to access the I/O signal arg unit arg .

Probable causes



Re-establish the connection with the I/O unit.


Description

Task: arg

The argument Data in arg has improper data type.

Program Ref. arg


Check the data type.Non-value and semi-value types may not be used.


Description

Task: arg

The argument arg has a negative value.

Program Ref. arg


Set the value positive or to zero.


Description

Task: arg

The value of argument arg forces the robot out of workspace.

Program Ref. arg


Decrease the value.


Description

Task: arg

The instruction arg can not be executed while the system is in a stop state.

Program Ref. arg


Use one of the switch Total or Free.


Description

Task: arg

In the instruction arg the argument arg is not an open directory.

Program Ref. arg


Open the directory before trying to read it.

Recovery: arg


Description

Task: arg

In the instruction arg the argument arg can't be used without the argument arg.

Program Ref. arg




Description

Task: arg

Object of the type arg could not be searched for.

Program Ref. arg



40768, Symbol Access Error

Description

Task: arg

No system symbol arg is accessible in the system.

Program Ref. arg


Recovery: arg

40764, Switch Argument Error

Description

Task: arg

The instruction arg must be used with one switch argument.

Program Ref. arg

40769, Symbol Read Access Error

Description

Task: arg

The symbol arg is not a readable object.

Program Ref. arg


Recovery: arg



40770, Symbol Type Error

Description

Task: arg

The symbol arg is of type arg and not the expected type arg .

Program Ref. arg



Program Ref. arg

40776, Conveyor Error

Description

Task: arg

Another arg instruction is waiting for the object.

Program Ref. arg

40771, Symbol Access Error

Description

Task: arg

The symbol arg is not accessible in this scope.

Program Ref. arg


Recovery: arg


Description

Task: arg

The arg instruction is already connected.

Program Ref. arg


Recovery: arg

40772, I\O Error

Description

Task: arg

The arg instruction has lost contact with the conveyor.

Program Ref. arg


Description

Task: arg

Booking of the new error number arg failed. The init value must be -1 or the old number.

Program Ref. arg


Check the init value of the new errnum variable.

40773, Instruction Interrupted

Description

Task: arg

The instruction arg was interrupted, reason unknown.

Program Ref. arg

40774, Object Dropped

Description

Task: arg

The object that the instruction arg was waiting for has been dropped.

Program Ref. arg

Probable causes

Start window passed or Checkpoint not satisfied.


If Checkpoint not used, Checkpoint Distance and Checkpoint Window

Width must be set to zero.

Rerun the instruction

Recovery: arg

40780, Data Object Error

Description

Task: arg

There is no valid data object for the argument arg of the instruction

arg.

Program Ref. arg


Check if there is a right data object.


Description

Task: arg

Another arg instruction is waiting for a distance to the object.

40779, Error Number Local

Description

Task: arg

The RAPID user error number arg must not be declared as local in routine.

Program Ref. arg


Check the errnum declaration.



40781, File Error

Description

Task: arg

The parameter arg does not correspond to any loaded text file.

Program Ref. arg


Check if the text file is (correct) installed.

40782, Mode Error

Description

Task: arg

File or serial channel is not opened for writing.

Program Ref. arg


Check how the file or serial channel was opened..


Description

Task: arg

File or serial channel is not opened in a character-based mode.

Program Ref. arg


Check how the file or serial channel was opened.


Description

Task: arg

File or serial channel is not opened in a binary mode.

Program Ref. arg




Description

Task: arg

File or serial channel is not opened for reading.

Program Ref. arg



40786, Read Error

Description

Task: arg


One or more bytes is not read properly. The value of the read data might be inconsistent.

Program Ref. arg

Consequences

Because the checksum for the received message is not the same as calculated at sending, the message data can not be used.

Probable causes

The reason can be:

- Communication problem

- Different WriteAnyBin - ReadAnyBin software version between the sending WriteAnyBin and the receiving ReadAnyBin


Error Recovery for communication problem: arg

40787, User Frame Error

Description

Task: arg

Not possible to get the coordinated user frame.

Program Ref. arg

40788, Axis Error

Description

Task: arg

The single axis is not init correctly.

Program Ref. arg

40789, Limitation Error

Description

Task: arg

The string length of the argument for the file path is too long.

Program Ref. arg

Probable causes

The maximum allowed string length for the full system file path is arg characters.


Shorten the length of the path.


Description

Task: arg

The RAPID string is too long.

Program Ref. arg

Probable causes

String value exceeds the maximum allowed length.

235



Rewrite the program to use strings of less length.

Recovery: arg

40791, I/O Error

Description

Task: arg

No space left on device (file name arg).

Program Ref. arg


Recovery: arg

40792, I/O Error

Description

Task: arg

File open/access error for path arg.

Program Ref. arg


- Check permission, is the file write protected?

- Check if the file or directory exists.

- Check if there is any space left on device.

Recovery: arg

40793, Error Installing Text Table

Description

Task: arg

No or faulty text resource name or index number in the text file.

Program Ref. arg

Consequences

The contents of some of the text tables may have been destroyed.


Correct the error, cold start the system and try again.


Description

Task: arg

The specified index within the text resource already exists in the system.

Program Ref. arg

Probable causes

- Error in the index numbering.

- The file has been installed twice.


If error in the index, correct it, cold start the system and try again.

236


Description

Task: arg

System memory for text tables is full.

Program Ref. arg


Reduce the amount of user defined text string installed from RAPID.

Cold start the system and try again.

40796, Overload Error

Description

Task: arg

The system is overloaded so the actual order can not be ready in time.

Program Ref. arg


Reduce the main computer load, for example by:

- Add WaitTime in RAPID loops

- Increase filter time for I/O signals

- Avoid cyclic interrupts

40797, I/O Error

Description

Unable to access the I/O signal arg on unit arg.

Probable causes





Description

arg


Description

Task: arg

TestSignRead is using a channel without a defined signal.

Program Ref. arg


Use TestSignDefine to define a signal to the channel.

40800, Tool Error

Description

Task: arg

The component robhold in the tool has not got the correct value.



Program Ref. arg


Change the value of robhold.

If the robot is holding the tool the value should be TRUE. If the robot is not holding the tool, i.e. a stationary tool, the value should be

FALSE.

40805, Motion Error

Description

Task: arg

Error from MocGenInstr.

Ref to former message for reason.

Program Ref. arg

40801, Calculation error

Description

Task: arg

Can not calculate the tool frame.

Program Ref. arg

Probable causes

It is not possible to calculate the tool frame with the selected approach points.


Select new approach points as accurate as possible.

40806, IOF Error

Description

Task: arg

Error from IofGenInstr.

Ref to former message for reason.

Program Ref. arg


Description

Task: arg

Not possible to do subscribe.

Program Ref. arg

Probable causes

There is no memory left to make another subscription on this variable.


To continue, PP must be moved to main!

40803, Error msg too long

Description

The length of the following error message was too long and has been cut.

This means you will not be able to read the whole message.

40807, File Error

Description

Task: arg

The file arg already exists.

Program Ref. arg


To be able to rename or copy:

Change the file name or remove the existing file.

Recovery: arg

40811, No Contact With Unit

Description

Task: arg

There is no contact with unit.

Program Ref: arg

Probable causes

- The unit may have been disabled ( IODisable "UNIT1", 1; )

- No power to the unit.


Description

Task: arg

The argument "type" in stoppointdata may not be followtime in the instructions MoveJ, MoveAbsJ and MoveExtJ.

Program Ref. arg


Change "type" to inpos or stoptime.


Description

Task: arg

Not allowed to run this program in non_motion_execution_mode.

Program Ref. arg


Change mode.


Description

Task: arg

The task is not allowed to execute the instruction arg.



Program Ref. arg

Probable causes

The task is not configured to control mechanical units.


Change the configuration or remove the instruction.


Description

Task: arg

StartMove could not get the regain distance.

Program Ref. arg

Probable causes

Application error.


Please restart the path.

Recovery: arg

40815, Non Existing Axis Number

Description

Task: arg

Unknown axis number for the mechanical unit arg

Program Ref. arg


Check the value for the argument Axis.

40816, RolGenInstr Error

Description

Task: arg

Error from instruction RolGenInstr.

Ref. to former user or internal error message for reason.

Program Ref. arg

Recovery: arg

41000, Item source exists

Description

Item source arg already exists. Two item sources may not have the same name.

41001, Not a valid name

Description

Choose arg or arg

41002, Buffer size exceeded

Description

Fatal internal error for item source arg. Try warm start or cold start.

Please report this error.

41003, Item source not defined

Description

The item source object has not been defined.

41004, Itmsrc internal error

Description

Internal error for item source arg.

Error type: arg.

41005, Flush item source first

Description

Item source arg must be flushed before it is used.

41006, Ack item target first

Description

Item target must be acknowledged before executing the GetItmTgt(s) instruction again.

Error occurred for item source arg.

41007, Item target buffer full

Description

Item target buffer full for item source arg .

41008, Conveyor I/O init error

Description

Error in the initialization of the I/O signal for item source arg, for conveyor

arg. I/O signal name arg.

41009, Conveyor does not exist

Description

Error for item source arg. The conveyor arg does not exist.

41010, No conveyor name given

Description

Error for item source arg. No conveyor name specified.



41011, Conveyor limits error

Description

Error for item source arg, conveyor arg. The limits are incorrectly specified.

41012, Conveyor data are defined late

Description

Error for item source arg, conveyor arg. The ItmSrcCnvDat instruction must be called before the ItmSrcFlush instruction.

41100, Too Many Corrections

Description

Task: arg

Max 5 correction descriptors are allowed to be connected.

Program Ref. arg


Check number of connected descriptors.

Recovery: arg

41050, Record not activated

Description

Record not ready for activation

Consequences

Record not activated

Probable causes

Try to activate record too early


Instruction Start Record must be called before activate record

41101, Correction Not Connected

Description

Task: arg

Can not write to correction descriptor.

Program Ref. arg


Check that the current correction descriptor is connected.

Recovery: arg

41051, Record not stored

Description

No valid record to store

Consequences

Nothing stored

Probable causes

Try to store a record not existing or not activated .


Instruction Activate must be called before

Store record

41102, No Corrections Connected.

Description

Task: arg

Correction unable to be read.

Program Ref. arg

Probable causes

No correction descriptor connected.


Check if any correction generator is connected.

Recovery: arg

41052, Can't use this record file

Description

File not found or data not valid

Consequences

Record not used

Probable causes

File not found or data not valid .


Check file directory and name and record data.

41200, Servo Tool Open Error.

Description

Task: arg

Not possible to open servo gun in motors off state.

Program Ref. arg


Retry after setting motors on.

Recovery: arg

41201, Servo Tool Close Error.

Description

Task: arg

Not possible to close servo gun in motors off state.

Program Ref. arg





Recovery: arg

41202, Servo Tool Calibration Error.

Description

Task: arg

Not possible to calibrate servo gun in motors off state.

Program Ref. arg



Recovery: arg

41203, Servo Tool Error.

Description

Task: arg

Servo tool arg does not exist.

Program Ref. arg


Check mechanical unit name.

Recovery:arg

41204, Servo Tool error.

Description

Task: arg

Emergency stop when executing instruction in background task.

Program Ref. arg


Retry after emergency stop reset.

Recovery:arg


Description

Task: arg

Not possible to close servo gun. The gun is not open.

Program Ref. arg


Retry after opening the gun.

Recovery: arg

41206, Servo Tool Parameter Error.

Description

Task: arg

The parameter PrePos must be a positive value.

Program Ref. arg

240


Change the parameter value.

Recovery: arg

41207, Servo Tool Init Error.

Description

Task: arg

The position for servo tool arg is not initialized.

Program Ref. arg


Change the parameter value or perform a tip change calib.

Recovery: arg

41208, Servo Tool Synchronization Error.

Description

Task: arg

The tips for servo tool arg are not synchronized.

Program Ref. arg


Synchronize via ManServiceCalib or perform a tool change calibration.

Recovery: arg

41209, Servo Tool Activation Error.

Description

Task: arg

Servo tool arg is not activated.

Program Ref. arg


Use ActUnit to activate.

Recovery: arg


Description

Task: arg

Not possible to execute instruction in motors off state for servo tool

arg.

Program Ref. arg



Recovery: arg


Description

Task: arg

Not possible to perform a recalibration of the gun arg.



Program Ref. arg


Retry after checking values.

Recovery: arg


Description

The argument Joint must be between 1 and arg.


Check and change the value.


Description

The argument Type doesn't correspond to a service value.


Description

The argument Type does not correspond to a service value.


Description

The argument Robot must be between 1 and arg.




Description

The argument Level doesn't correspond to a service level.


Description

Task: arg

Faulty AxisNo.

Program Ref. arg



Press Start to continue.

41401, I/O Error

Description

Unable to access the I/O signal.

Signal and unit unknown.


Probable causes





Description

Task: arg

Illegal value of argument for parameter Axis or Strength.

Program Ref. arg




Description

Task: arg

Illegal value of argument for parameter Speed Priority Type.

Program Ref. arg


Description

Task: arg

Argument On or Off missing.

Program Ref. arg


Check the RAPID program. One of the switch On or Off must be given.


Description

Task: arg

Argument TuneValue not allowed together with argument Off.

Program Ref. arg


Check and change the RAPID program.


Description

Task: arg

This TuneType is only valid for option Advanced Shape Tuning.

Program Ref.arg


Change TuneType or install option.

241



Description

Task: arg

Symbol arg is read-only.

Program Ref. arg


Recovery: arg


Description

Task: arg

The symbol arg was not found.

Program Ref. arg


Recovery: arg


Description

Task: arg

Ambiguous symbol arg.

Program Ref. arg




Description

Task: arg

Search error for symbol arg.

Program Ref. arg


Recovery: arg


Description

Task: arg

Unknown module name arg.

Program Ref. arg

Probable causes

The module does not exist.



242


Description

Task: arg

Ambiguous module arg.

Program Ref. arg




Description

Task: arg

Ambiguous routine name arg.

Program Ref. arg




Description

Task: arg

Unknown routine name arg.

Program Ref. arg

Probable causes

The routine does not exist.




Description

Task: arg

The module name arg does not exist.

Program Ref. arg



Recovery: arg


Description

Task: arg

The symbol arg is not a module.

Program Ref. arg



Recovery: arg




Description

Task: arg

Can not convert date.

Program Ref. arg


Warm start and retry.


Description

Task: arg

arg must be num, bool or string.

Program Ref. arg




Description

Task: arg

The argument type of arg is not compatible with cfg type. Expected

arg.

Program Ref. arg


Recovery: arg


Description

Task: arg

Unknown cfg domain in argument arg.

Program Ref. arg



Recovery: arg


Description

Task: arg

Unknown cfg type in argument arg.

Program Ref. arg



Recovery: arg


Description

Task: arg

Unknown cfg instance in argument arg.

Program Ref. arg



Recovery: arg


Description

Task: arg

Unknown cfg attribute in argument arg.

Program Ref. arg



Recovery: arg


Description

Task: arg

The path 'arg' in argument arg is incorrect.

Program Ref. arg


Check and change the path.

Recovery: arg

41426, I/O Error

Description

Unable to access the I/O signal. Signal and unit unknown.

Consequences

Impossible to restart.

Probable causes



Re-establish the connection with the I/O unit. To make it possible to restart the program move PP to a safe restart position.


Description

Task arg:

The delaytime has to be positive.

Program Ref. arg




Change the value of delaytime.


Description

Task: arg

The single axis is not init correctly. The sensor is not activated.

Program Ref. arg


Description

Task: arg

The single axis is not init correctly.

The sensor process is not init correctly.

Program Ref. arg

Unknown mechanical unit.

Program Ref. arg


Check if the mechanical unit exists in the system.

Recovery: arg


Description

Task: arg

Argument Axis is out of range.

Program Ref. arg


Check and change the value of the argument axis.

Recovery: arg


Description

Task: arg

Orientation definition error in arg .

Program Ref. arg


Check orientation.

All used orientations must be normalized i.e. the sum of the quaternion elements squares must equal 1.


Description

Task: arg

Unknown LOGSRV instance.

Program Ref. arg




Description

Task: arg

Argument Channel is out of range.

Program Ref. arg


Check and change the value of argument Channel.


Description

Task: arg

Can not reset all test signals.

Program Ref. arg




Description

Task: arg

Can not set test signals.

Program Ref. arg




Description

Task: arg

41438, Undefined Load

Description

Task: arg

WARNING!

Argument arg has undefined load (mass=0).

Program Ref. arg

Consequences

IMPORTANT TO DEFINE CORRECT LOAD to avoid mechanical damages of the robot.


Define the actual load for the tool or the grip load before program movement or jogging. A good motion performance requires a correctly defined load.



41439, Undefined Load

Description

Task: arg

WARNING!

Argument arg has undefined load center of gravity.

Program Ref. arg

Consequences

IMPORTANT TO DEFINE CORRECT LOAD to avoid mechanical damage of the robot.


Define the actual center of gravity for the tool load or the grip load before program movement or jogging (cog.x, cog.y and cog.z can not be 0 mm at the same time). Load identification can be done with the service routine

LoadIdentify.

The reference in argument arg is not an entire persistent variable.

Program Ref. arg


It is not possible to use record component or array element in arg. arg .

It is only possible to use entire persistent variables for Tool, WObj or

Load in any motion instruction.


Description

Task: arg

Argument Tool has negative load of the tool.

Program Ref. arg


Define the correct load of the tool before use of the tool for jogging or program movement. Load identification of the tool can be done with the service routine LoadIdentify.

41440, Argument Is Missing

Description

Task: arg

One of the switch parameter arg or arg has to be defined.

Program Ref. arg

Consequences

The called RAPID routine could not be executed.


An argument of the data type switch must be specified.


Description

Task: arg

Argument Tool has at least one inertia data component with negative value.

Program Ref. arg


Define all inertia data components (ix, iy or iz) to actual positive values.

41441, UnLoad Error

Description

Task: arg

Module loaded with path arg is active and therefore can not be erased.

Program Ref. arg

Probable causes

Instruction UnLoad or WaitLoad is executed in the same module as the module that should be removed.

Instruction UnLoad or WaitLoad is in a trap that is executed earlier then expected.

If there is a CONNECT to a trap routine in the module, an IDelete on the trap has to be done before the module can be unloaded.


Check that the module does not contain routines or data that are still active, for example CONNECT.

Recovery: arg


Description

Task: arg


Description

Task: arg

No \WObj specified for movement with stationary TCP.

Program Ref. arg


Add argument \WObj for actual work object.

If not movement with stationary TCP, change the component

"robhold" in argument Tool to TRUE (robot holds the tool).


Description

Task: arg

Undefined if robot holds the tool or the work object.

Program Ref. arg


Check if mismatch between argument Tool and argument \WObj for data component robhold.




Description

Task: arg

Argument arg has at least one data component with negative value.

Program Ref. arg


Set all data components in argument arg to positive values.


Description

Task: arg

Argument arg may not have a negative value.

Program Ref. arg


Set argument arg to a positive value.


Use the instruction CONNECT to allocate and connect an interrupt number to a trap routine.


Description

Task: arg

Argument arg contains an interrupt number, which is already in use for other purposes.

Program Ref. arg


Before reuse of an interrupt variable in the program, it must have been cancelled with the instruction IDelete.


Description

Task: arg

Illegal value in argument arg.

Program Ref. arg




Description

Task: arg

Illegal data type of argument arg.

Program Ref. arg




Description

Task: arg

Argument \WObj specifies a mechanical unit name, which is not activated or is unknown in the system.

Program Ref. arg


The mechanical unit name defined in \WObj must correspond to the name earlier defined in the system parameters and must be activated.


Description

Task: arg

Argument arg contains an illegal interrupt number.

Program Ref. arg

Probable causes

Input interrupt number is illegal because it has not been allocated by the instruction CONNECT.


Description

Task: arg

Trigg parameter number arg, reference to undefined trigg data.

Program Ref. arg


Define trigg data by executing instruction TriggIO, TriggInt,

TriggEquip, TriggSpeed or TriggCheckIO before execution of instruction TriggL, TriggC, TriggJ, CapL or CapC.


Description

Task: arg

Operative system get time failed.

Program Ref. arg




Description

Task: arg

Argument arg not within range.

Program Ref. arg



The argument must be in range arg


Description

Task: arg

Missing optional argument.

Program Ref. arg


Add one of the optional arguments arg or arg.


Description

Task: arg

Argument arg or arg not within range.

Program Ref. arg


Check and change the value of the argument.


Description

Task: arg


Program Ref. arg




Description

Task: arg

Argument arg or arg or arg not within range.

Program Ref. arg


Check and change the argument.


Description

Task: arg

Illegal value of argument arg.

Program Ref. arg


The index must be an integer and in range 1 to 1024.




Description

Task: arg

Illegal value of argument for parameter arg.

Program Ref. arg


The value must be an integer and in the correct range.

41463, Argument Switch Is Missing.

Description

Task: arg

There is an argument missing.

Program Ref. arg


One of the switch parameters \Hex1, \Long4, \Float4 or \ASCII has to be defined.

41464, Index To High.

Description

Task: arg


Program Ref. arg



41465, The String Is Empty.

Description

Task: arg


Program Ref. arg


Check the argument, and use a non-empty string.

41466, The Variables Are Equal.

Description

Task: arg

The argument FromRawData and ToRawData are equal.

Program Ref. arg




Description

Task: arg

247



Program Ref. arg


Check and change the value. It must be an integer and in range 0 to

255.


Description

Task: arg


Program Ref. arg


Check and change the value. NoOfBytes must be an integer and in range 1 to 1024, and not higher than RawData length.


Description

Task: arg


Program Ref. arg


Check the value. NoOfBytes must not be higher than RawData length.


Recovery: arg


Description

It was not possible to send data using SCWrite to external computer.

Failed to send variable arg


Description

Task: arg


Program Ref. arg


Check the value: arg

arg must be a positive integer.

41475, Wrong size of tasklist

Description

Task: arg

The tasklist has wrong number of elements. It must not have less than

1 or more than arg.

Program Ref. arg


Check and change the number of arguments in the tasklist.


Description

Task: arg

Argument arg or arg not within range.

Program Ref. arg




Description

Task: arg

You are not allowed to disable unit arg.

Program Ref. arg


Recovery: arg


Description

Task: arg

There is no client e.g. a teach pendant taking care of instruction.

Program Ref. arg

41476, Non-consistent task list

Description

Task: arg

arg in the tasklist is not one of the tasks that are configured in the system (max arg tasks can be configured).

Program Ref. arg


Add the task to the system (in sys.cfg) or remove it from the tasklist.

41477, TimeOut

Description

Task: arg

The time set in argument arg in instruction WaitSyncTask has expired.

Program Ref. arg


Recovery: arg




Description

Task: arg

The value of the ID is negative or is not an integer.

Program Ref. arg


Check the value of the optional argument ID. The value must be a nonnegative integer.


Description

Task: arg

The robot axis arg is not moveable and therefore must not be supervised.

Program Ref. arg


Change the value of axis arg to 9E9.

41484, TimeOut

Description

Task: arg

The time set in argument arg in instruction SyncMoveOn has expired.

Program Ref. arg


Recovery: arg

41490, TimeOut

Description

Task: arg

The time set in argument arg in instruction SyncMoveOff has expired.

Program Ref. arg


Recovery: arg


Description

Task: arg

The instruction arg is only available if there is a TCP-robot defined in the program task.

Program Ref. arg


- Check the configuration.

- The instruction must be removed, if the task is not supposed to have a TCP-robot.


Description

Task: arg

The instruction arg is not available if there is a TCP-robot defined in the program task.

Program Ref. arg


- Check the configuration.

- The instruction must be removed, if the task is supposed to have a

TCP-robot.


Description

Task: arg

The instruction arg only works if the TCP-robot is active.

Program Ref. arg


Activate the TCP-robot in the task.


Description

Task: arg

There is no TCP-robot defined in the program task. One or several robot axis value input is not equal to 9E9.

Program Ref. arg


Change the robot axis value to 9E9.


Description

Task: arg

The instruction arg only works if the mechanical unit is active.

Program Ref. arg


Activate the mechanical unit in the task.


Description

Task: arg

There is no TCP-robot available in the task.

Program Ref. arg


To be able to run the instruction a TCP-robot must be available in the task.




Description

Task: arg

The task does not control mechanical unit: arg.

Program Ref. arg



41495, Move PP Error

Description

Task: arg

Not ready with the switch from independent to synchronized mode.

Program Ref. arg

Consequences

Restart of current instruction is blocked.

The system can either be in synchronized motion mode or still in independent motion mode.

Probable causes

Stop of program when having an active instruction. Then a PP movement within program has been done.


Move PP to start the program again. PP must be moved in all program tasks. To have a well defined state of the system you should move PP to main.

Instruction arg was active in this task. Moving PP within the program can be dangerous in some cases.

Program Ref. arg

Consequences

Moving PP in the RAPID program can result in unsynchronized

RAPID tasks or/and collision between robots.

Probable causes

PP movement within RAPID program when having active arg instruction.


Move PP to suitable position in this program task.

41498, No Defined UserFrame In Mechanical

Unit arg!

Description

The workobject arg contains a coordinated mechanical unit which has no defined userframe.


Check the mechanical unit component of the workobject.

41499, Synchronized Mode

Description

Task: arg

System is in synchronized mode. Instruction must have an ID.

Program Ref. arg


Add switch \ID with an identification number to the instruction.

41496, Move PP Error

Description

Task: arg

Not ready with the switch from synchronized to independent mode.

Program Ref. arg

Consequences

Restart of current instruction is blocked.

The system can either be in synchronized motion mode or still in independent motion mode.

Probable causes

Stop of program when having an active instruction. Then a PP movement within program has been done.


Move PP to start the program again. PP must be moved in all program tasks. To have a well defined state of the system you should move PP to main.

41497, Move PP Notification

Description

Task: arg

41500, Independent Mode

Description

Task: arg

System is in independent mode. Instruction must not have an ID.

Program Ref. arg


Remove switch \ID from the instruction.

41501, Illegal Id

Description

Task: arg

ErrorId has wrong value. It must be an integer in interval arg - arg.

Program Ref. arg


Change the value.



41502, Illegal Domain

Description

Task: arg

Domain arg can not be used.

Program Ref. arg


Choose another Elog Domain.

Task reads another Mechanical Unit than the one stated in the instruction.

Program Ref. arg


Change Mechanical Unit in the instruction.

41503, Illegal Error Type

Description

Task: arg

Error type TYPE_ALL can not be used.

Program Ref. arg


Use another Error Type.

41508, LoadId Error

Description

Task: arg

Load Identification is not available for this robot type.

Program Ref. arg


Check next Event Log message, for the next user action to do.

41504, No Mechanical Unit Stated

Description

Task: arg

No TCP in the system and no Mechanical Unit added to the instruction.

Program Ref. arg


Add a Mechanical Unit, that exists in the task, to the instruction .


Description

Task: arg

Not valid load identification position.

Program Ref. arg


Change the position for the robot.


41505, Mechanical Unit Not In Task

Description

Task: arg

The Mechanical Unit stated does not exist in the task.

Program Ref. arg


Add another Mechanical Unit to the instruction.


Description

Task: arg

Not allowed to identify (or use) tool0.

Program Ref. arg


Set the tool that should be identified, active in the jogging window.


41506, Task Does Not Read a TCP Robot

Description

Task: arg

The read task does not read a tcp robot.

Program Ref. arg


Change the configuration or add a Mechanical Unit, that exists in the task, to the instruction.


Description

Task: arg

Not allowed to identify load0.

Program Ref. arg


Use another load for identification.


41507, Task Reads Other Mechanical Unit

Description

Task: arg

41512, Internal Error

Description

Task: arg

Measurement axes > 2 at the same time.



Program Ref. arg




Description

Task: arg

Selection of PayLoad out of limits.

Program Ref. arg


Select a PayLoad in the system.



Description

Task: arg wobj0 can not be active for roomfix TCP.

Program Ref. arg


Select another Work Object.



Description

Task: arg

Selection of method out of limits.

Program Ref. arg


Select one of the identification methods given.



Description

Task: arg

The configuration angle is not adequate.

Program Ref. arg

Consequences

It is not possible to run the identification.

Probable causes

The selected value of the configuration angle is less than 30, or has another value that is not possible to use for identification.


Select a configuration angle between +/- 30 and +/- 90 degrees.



Description

Task: arg

PP has been moved to the beginning of the Load Identification routine and is now ready for a new restart.

Program Ref. arg

Probable causes

Service routine was stopped during measurement, interruped with cancel by the user or interrupted because some type of other error.

Check former Event Log message for reason.


1) Start service routine again

2) Use Debug - Cancel Call Routine to quit execution of service routine.

NOTE: Cancel Call Routine result in loose of Program Pointer.

Use Debug - PP to Main to get a new Program Pointer.


Description

Task: arg

Selection of MechUnit out of limits.

Program Ref. arg


Select one of the Mechanical Units displayed.



Description

Task: arg

Mass must be > 0 kg.

Program Ref. arg


Specify the mass to something greater than 0.


41520, Error Recovery Constant Not Booked

Description

Task: arg

Error recovery constant arg is not booked.

Program Ref. arg


Use instruction BookErrNo to book the constant or use an error recovery constant booked by the system (can not be used with

ErrRaise).



41521, Task Status Error

Description

Task: arg

None of the tasks in the tasklist is a NORMAL, activated task.

Program Ref. arg


Check in the Task Selection Panel that at least one of the tasks in the tasklist are selected = activated.

Check in the .cfg-file that at least one of the tasks selected is

NORMAL.

41522, Wrong Error Recovery Constant Used

Description

Task: arg

Error recovery constant arg has been booked by the system. The constant can not be used with instruction ErrRaise.

Program Ref. arg


Book a new error recovery constant with instruction BookErrNo.


Description

Task: arg

Argument arg is not an integer or is negative.

Program Ref. arg


Change the value of the argument to a non-negative integer.


Description

Task: arg

The program is executing in an UNDO handler. It is not allowed to execute the instruction arg in an UNDO handler.

Program Ref. arg




Description

Task: arg

The program is executing in an EVENT routine. It is not allowed to execute the instruction arg in an EVENT routine.

Program Ref. arg




Description

Task: arg

Instruction arg may only be used in an ERROR handler.

Program Ref. arg


Remove the instruction or move it to an ERROR handler.

41527, Argument Switch Is Missing.

Description

Task: arg

There is an argument missing.

Program Ref. arg


One of the switch parameters \Continue or \BreakOff in arg has to be defined.


Description

Task: arg

Instruction arg may only be used in a no stepin routine.


Remove the instruction or move it to a no stepin routine.


Description

Task: arg

The switch \Inpos is only allowed when the task is in control of a mechanical unit.

Program Ref. arg


Remove the switch \Inpos from the instruction


Description

Task: arg

It is not possible to execute the instruction arg, while the coordinated workobject has a reference to the mechanical unit arg, located in another task.

Program Ref. arg


Change to a workobject with reference to a mechanical unit located in the same task as the TCP robot.

Function CalcJointT can be used even when the coordinated workobject is located in another task if:

- Switch \UseCurWObjPos is used



- The coordinated workobject is standing still PP must be moved to main in all tasks before you can continue.

41531, Task Not In TaskList

Description

Task: arg

arg is not one of the tasks in the TaskList, or there is a mismatch between the tasklists in the different tasks.

Program Ref. arg


- Add current task to the TaskList.

- Check that the tasklists in the different tasks are similar.

When using PERS variables, it might be necessary to unload the modules containing the tasklists, and then reload them again.

41532, Mismatch of task list

Description

Task: arg

Failed to synchronize because of:

1) The task list, arg, does not match with the task lists with the same

SyncID in the other tasks, or a task name is used multiple times in the task list.

2) Not the same active tasks in task selection panel in the first executed instruction as in the following instructions.

Program Ref. arg

Consequences


Probable causes

The reason for this error is one of the following:

1) Tasklists do not have the same content for the same SyncID or a taskname is used multiple times.

2) One or several tasks has been enabled/disabled in the task selection panel after first instruction was executed.


1) Check and modify tasklists and SyncIDs, or the same error will occur again.

2) Start again. The instructions will be executed with the current status of the task selection panel.

41534, Inconsistent Synch Data

Description

Task: arg

Inconsistent synchdata in TaskList arg.

Program Ref. arg


Change content of the TaskList.

PP must be moved to main in all tasks before you can continue.

41535, Unexpected SyncMoveOn

Description

Task: arg

Unexpected SyncMoveOn (SyncID arg). The system is already in synchronized mode.

Program Ref. arg

Probable causes

The program task is already in synchronized mode becuase

SyncMoveOn has already been executed.

Use of tasklists that are non global can cause this error.


PP must be moved to main in all task before you can continue the program execution.

Remove the SyncMoveOn instruction. Every SyncMoveOn must be followed by a SyncMoveOff instruction.

Check your tasklists.

41536, Unexpected SyncMoveOn

Description

Task: arg

Unexpected SyncMoveOn (SyncID arg). The system is waiting for a

SyncMoveOff.

Program Ref. arg


Remove the SyncMoveOn instruction. Every SyncMoveOn must be followed by a SyncMoveOff instruction.

41533, Mismatch Of SyncID

Description

Task: arg

SyncID arg does not match with SyncID in the other task/tasks.

Program Ref. arg

Probable causes



Change SyncID and check the tasklists.

41537, Unexpected SyncMoveOff

Description

Task: arg

Unexpected SyncMoveOff (SyncID arg). The system is waiting for a

SyncMoveOn.

Program Ref. arg


Remove the SyncMoveOff instruction. Every SyncMoveOn must be followed by a SyncMoveOff instruction.



41538, Wrong TaskList

Description

Task: arg

The task, arg, in the TaskList is a read task and can not be synchronized.

Program Ref. arg


Change the TaskList or the configuration.

41540, Wrong Mechanical Unit

Description

Task: arg

The task reads the control task, arg, which does not control the mechanical unit arg.

Program Ref. arg


Change \MechUnit or the configuration.


Description

Task: arg

A loaddata has been defined, but is no longer available in the system.

Program Ref. arg

Probable causes

The instruction GripLoad might have been run in a module that is no longer available in the system.


Be sure to run GripLoad Load0, to reset loaddata.

41539, Speed Too High

Description

Task: arg

Speed is over 100 mm/s. This is too fast when Stiff Stop (switch \Stop) is used.

Program Ref. arg


Change the speed.

41544, Obsolete Instruction

Description

Task: arg

The procedure arg is obsolete and will not have the expected behavior.

PFIOResto will do nothing at all.

PFDOVal and PFGOVal will act as the functions DOutput and

GOutput respectively.

Program Ref. arg


Description

Task: arg

The argument arg may not be of type LOCAL PERS.

Program Ref. arg


Remove the directive LOCAL from the data declaration.

41541, Not Allowed From a Read Task

Description

Task: arg

The instruction is not allowed to execute in a read task.

Program Ref. arg




Description

Task: arg

The object arg does not exist in the system or is of type LOCAL PERS.

Program Ref. arg


- Declare the object

- Remove the directive LOCAL from the data declaration

41542, Program Stop

Description

Task: arg

Not possible to regain to path because of program stop in the system.

Program Ref. arg


Recovery: arg


Description

Task:arg

The \Corr switch can not be used without the option Path Offset.

Program Ref. arg


Remove the argument or install the option.



41548, Module Error

Description

Task: arg

The module you are trying to erase, arg, is active and thus can not be removed.

Program Ref. arg


Check that the module you want to erase is not active.


- Switch to trap-level.

- Execute StorePath to switch path level.

41553, Destroyed Data

Description

System data arg in one of the tasks has been changed. It is NOT allowed to change this data.


The system has restored the data when it was started, but the program has to be checked. Remove where arg has been assigned a value.

41549, Unexpected SyncMoveOn or

SyncMoveOff

Description

Task: arg

Wrong path level. It is not possible to use SyncMoveOn or

SyncMoveOff on StorePath level.

Used arg: arg

Program Ref. arg



41554, Synchronized Mode

Description

Task: arg

It is not possible to use the optional parameter \Conc when the system is in synchronized mode.

Program Ref. arg


Remove the optional parameter \Conc from any move instruction used in synchronized mode.

41550, PathRecorder Start/Stop Error

Description

Task: arg

Unable to execute arg

Program Ref. arg


Ensure that a backward motion has not been initiated with

PathRecMoveBwd without being terminated with PathRecMoveFwd.


Description

Task: arg

There is no contact with the unit arg.

Program Ref. arg

Probable causes

The unit may have been disabled (IODisable "UNIT1", 1;)

No power to the unit.


Recovery: arg

41551, PathRecorder Move Error

Description

Task: arg

Unable to execute arg. The given identifier can not be reached.

Program Ref. arg


Ensure that the PathRecorder has been started.

Ensure that the program pointer not is being moved manually.

Ensure that the limit of arg recorded move instructions is not exceeded.

41552, PathRecorder Path Level Error

Description

Task: arg

Can not execute arg on current path level.

Program Ref. arg


Description

Task: arg

There is no contact with unit.

Program Ref. arg

Probable causes

The unit may have been disabled (IODisable "UNIT1", 1;)

No power to the unit.


Recovery: arg



41557, Mec. Unit not stopped

Description

Task: arg

Not allowed to change run mode, if not all motion program tasks are stopped.

Program Ref. arg


Do program stop and try again.

41558, Argument Switch Missing

Description

Task: arg

An argument is missing to instruction arg.

Program Ref. arg


Add switch SyncOrgMoveInst or SyncLastMoveInst to the instruction.

41559, Not PERS variable

Description

Task: arg

The task list, arg, is either LOCAL or TASK persistent. It is not allowed. It has to be global.

Program ref. arg


Change the task list to PERS.

Consequences

When the instruction is executing there will be no button available to press.


Put a text in at least one of the function keys TPFK1 .. TPFK5

41562, Risk for faulty circular movement

Description

Task: arg

Risk for faulty circular movement because of:

1) An asynchronous process error has occurred and was not handled in any error handler

2) Program Pointer at circular instruction in combination with done

MODPOS of any previous move instruction

Program Ref. arg

Consequences

The Program may not be started from the current position, because there is a risk that the robot might perform an unexpected movement.

Probable causes

One of following:

1) The RAPID program is missing an error handler or the error handler does not handle this specific error

2) MODPOS operation done when not running in step or move step mode


One of following:

1) Edit the program

2) Move the program pointer to be able to start the program.

41560, No Start of Movement

Description

Task: arg

It was not possible to start the movement.

Program Ref. arg

Probable causes

1. There has been an emergency stop.

2. There was another error in the system.


1. Reset the emergency stop, if there has been one.

2. Check former error messages for reason.

Recovery: arg


Description

Task: arg

The Mechanical Unit arg specified in the WObj for this MOVE instruction is the same Mechanical Unit arg as the robot for this program task.

Program Ref. arg

Consequences

It is not possible that the robot moves the work object itself.


Edit the used wobjdata.

41561, No Text in Function Key

Description

Task: arg

The instruction TPReadFK has no text in either of the function keys.

Program Ref. arg

41564, Not allowed to run from a Motion Task

Description

Task: arg

The instructions StopMove, StartMove and StopMoveReset with the option parameter \AllMotionTasks are not allowed to run from a motion program task.



Program Ref. : arg

Probable causes

It is only allowed to do stop and restart of all movements in the system from a supervision program task running as a read (or background) program task.



41569, Socket error

Description

Task: arg

The socket is already connected and can not be used to listen for incoming connections.

Program Ref. arg


Use another socket to listen for incoming connections.

41565, Not allowed value

Description

Task: arg


Program ref. arg


Check and change the value. It must be an integer between arg and arg.


Description

Task: arg

The socket can not accept incoming connection requests since it is not set to listen state.

Program Ref. arg

Probable causes

SocketAccept is used before SocketListen.


Set socket to listen for incoming connections before trying to accept.

41566, Signal exceeds max number of allowed bits

Description

Task: arg

The signal arg is too big.

Program ref. arg


Group signals consisting of 23 bits or less can be represented by the num datatype, and group signals of 32 bits or less can be represented by the dnum datatype, if they are used in a RAPID program


Description

Task: arg

The address and port is already in use and can not be used by this socket.

Program Ref. arg


Recovery: arg

41567, Digital Output Break

Description

Task: arg

A digital output interrupted the execution.

Program Ref. arg


Recovery: arg


Description

Task: arg

Unexpected error creating socket.

Check log for further messages of possible cause.

Program Ref. arg


Move program pointer to main and restart program.

41568, Specified name is not a bus

Description

Task: arg

The bus name arg doesn't exist.

Program Ref.arg

Probable causes

The unit name is misspelled or not defined.


Recovery: arg


Description

Task: arg

No more sockets can be created. The maximum number of concurrent sockets is eight.

Program Ref. arg




Close one or more sockets, to allow a new socket to be created.


Description

Task: arg

The socket must be created before it can be used in any socket instruction.

Program Ref. arg

Probable causes

The reason for this error is one of the following:

1) Socket not created at all.

2) PP movements has been done.

3) Start of program after power fail.

4) The socket has been closed after SocketCreate.


Insert an SocketCreate instruction at a suitable place in the program before the socket is used.

Recovery: arg


Description

Task: arg

Unexpected error when connecting socket.

Check event log for other messages for possible cause.

Program Ref. arg


Move program pointer to Main and restart program.


Description

Task: arg

The connection was refused by the remote host.

Program Ref. arg


Description

Task: arg

The specified address is invalid. The only valid addresses are the LAN address of the controller or the service port address, 192.168.125.1.

Program Ref. arg


Specify the LAN address or the service port address.


Description

Task: arg

The specified port is invalid.

Program Ref. arg


It is recommended that a port number in the range 1025-4999 is used.


Description

Task: arg

The socket is already connected and can not be connected again.

Program Ref. arg

Probable causes

SocketConnect has already been executed for the specified socket.


Close the socket and recreate before connecting.


Description

Task: arg

The instruction was not finished within the timeout period.

Program Ref. arg


Use a higher timeout value or use an error handler to retry the instruction.

Recovery: arg


Description

Task: arg

The timeout specified in the instruction is too low. The timeout is specified in seconds and must not be zero.

Program Ref. arg


Use a timeout value greater than zero.


Description

Task: arg

Empty data was specified to be sent or as storage in receive.

Program Ref. arg


Use a string, rawbyte or byte array with size greater than zero.




Description

Task: arg

The specified data is too big.

Program Ref. arg


A socket can handle at most 1024 bytes in one instruction.


Description

Task: arg

The byte array is invalid. A byte array can only contain integers between 0 and 255.

Program Ref. arg


Change the byte array to contain valid data or use rawbytes to send complex data.


Description

Task: arg

The specified string or data to be sent is empty.

Program Ref. arg


Check that the data is correct.


Description

Task: arg

Unexpected error when trying to get socket state.

Program Ref. arg


Move programpointer to Main and restart program.


Description

Task: arg

The number of bytes to send has to be a value bigger than zero.

Program Ref. arg


Change the value for the optional parameter NoOfBytes to a value bigger than zero.


Description

Task: arg

The specified number of bytes to be sent is longer than the length of the actual data.

Program Ref. arg


Change the value for the optional parameter NoOfBytes to be less than or equal to the actual data.

If all data should be sent remove the optional parameter.


Description

Task: arg

No data was received.

Program Ref. arg

Probable causes

The connection may have been closed by the remote host.




Description

Task: arg

The data received is too long to be stored in a string. The maximum length of data that can be stored in a string is 80 characters.

Program Ref. arg


Use an byte array or rawbytes to receive data longer than 80 bytes.


Description

Task: arg

An unexpected error occurred when sending data.

Check the event log for other messages for the possible cause.

Program Ref. arg


Move the programpointer to Main and restart the program.


Description

Task: arg

The socket is not connected.

Program Ref. arg

Probable causes

For client, use SocketConnect before receiving/sending data.

For server, use SocketAccept before receiving/sending data.




Use SocketConnect or SocketAccept to connect socket before trying to receive/send.


Use SocketBind to specify which address to listen for incoming connections.


Description

Task: arg

The connection has been closed by the remote host.

Program Ref. arg


Use error handler to re-establish connection before retrying to send/ receive.

Recovery: arg


Description

Task: arg

The specified client socket is already in use. The client socket must not be created before calling SocketAccept.

Program Ref. arg

Probable causes

SocketAccept has already been executed for the specified socket.


Close the client socket before using it in the call to SocketAccept, or remove multiple SocketAccept with same client socket.


Description

Task: arg

Unexpected error binding socket.

Program Ref. arg




Description

Task: arg

The socket has already been bound to an address and can not be bound again.

Program Ref. arg


Close socket and recreate before trying to bind socket to a new address.


Description

Task: arg

Unexpected error accepting connection.

Program Ref. arg




Description

Task: arg

Unexpected error receiving data.

Program Ref. arg




Description

Task: arg

Unexpected error trying to listen for connections.

Program Ref. arg




Description

Task: arg

The socket has not been bound to an address.

Program Ref. arg


Description

Task: arg

The socket has already been created.

A socket can only be created once and must be closed before it can be created again.

Program Ref. arg


Use another socket or close socket before creating.


Description

Task: arg



The socket is already listening for incoming connections.

A socket can only be used once to listen for incoming connections.

Program Ref. arg

Probable causes

Multiple use of SocketListen with same socket.


Use another socket or close socket before using it again.

41611, UIMsgBox - No user or program action defined

Description

Task: arg

The instruction UIMsgBox or function UIMessageBox has no user or program action defined.

None of the option arguments \Buttons, \BtnArray,\MaxTime,

\DIBreak or

\DOBreak are used.

Program Ref. arg

Consequences

The RAPID program will be executed for ever.


Use one or several of the arguments \Buttons, \BtnArray, \MaxTime,

\DIBreak or \DObreak.

Recovery: arg

Consequences

Not possible to continue the program execution.


Change the argument \InitValue so it's inside the value range.

Recovery: arg

41614, InitValue is not an integer

Description

Task: arg

In function arg, the argument \InitValue is not an integer value as specified in argument \AsInteger.

Program Ref. arg

Consequences

The program execution can not continue.


Change the argument \InitValue to an integer.

Recovery: arg


Description

Task: arg

The datapos arg is undefined.

Program Ref. arg


All datapos is retrieved with the function GetNextSym.

41612, MinValue greater than MaxValue

Description

Task: arg

In function arg, the argument \MinValue is greater than \MaxValue.

Program Ref. arg

Consequences

Not possible to continue the program execution.


Change the RAPID program so argument \MaxValue is greater than

\MinValue.

Recovery: arg

41613, InitValue not within specified value range

Description

Task: arg

In function arg, the argument \InitValue is not specified within the range \MaxValue ... \MinValue.

Program Ref. arg


Description

Task: arg

The taskid arg is unknown in the system.

Program Ref. arg


Program tasks must be defined in the system parameter and not in the

RAPID program. (Taskid can be used as a parameter when declaring a routine).

41617, Too intense frequency of Write

Instructions

Description

A high usage frequency of user interface write instructions, such as

TPWrite, has forced the program execution to slow down.


Decrease the usage frequency of user interface write instructions. Add wait instructions, such as WaitTime, when many write instructions are used in conjunction.



41618, Argument error buttondata

Description

Task: arg

The argument Buttons of type buttondata has not allowed value.

Only allowed to use the predefined data of type buttondata.

Program Ref. arg

Probable causes

Buttondata must be:

- an integer

- have a value within the predefined range


Edit the program.

Consequences


Probable causes

Error in the RAPID programs.


Check that no mix of StorePath and StorePath \KeepSync is used.

Change the program.

PP must be moved in all tasks before you can continue.

41619, Argument error icondata

Description

Task: arg

The argument Icon of type icondata has not allowed value.

Only allowed to use the predefined data of type icondata.

Program Ref. arg

Probable causes

Icondata must be:

- an integer

- have a value within the predefined range.


Edit the program.

41620, Socket Error

Description

Task: arg

The Socket Messaging subsystem is overloaded.

Program Ref. arg

Probable causes

This can happen if sockets are created and closed frequently and very rapidly.


Try to rewrite the program in such a way that sockets are reused instead of closed and then recreated.

41622, Unexpected instruction

Description

Task: arg

The instruction arg can only be used in between instruction

arg and instruction arg (on store path level).

Program Ref. arg

Consequences


Probable causes

Error in the RAPID program.




41623, Faulty use of arg

Description

Task: arg

Instruction arg is used multiple times, or the instruction is used when already in synchronized motion mode.

arg suspends synchronized coordinated movements.

arg resumes synchronized coordinated movements.

Program Ref. arg

Consequences


Probable causes





41621, StorePath Error

Description

Task: arg

Instruction arg is used with arg switch in one or several tasks together with arg without arg switch.

Program Ref. arg

41625, Unexpected arg

Description

Task: arg

Instruction arg is used directly after instruction arg, or the system is not in synchronized motion mode.

A change to independent motion mode can not be done.



Program Ref. arg

Consequences


Probable causes





41626, Unexpected arg \arg

Description

Task: arg

Instruction arg \arg is used in independent motion mode.

Program Ref. arg

Consequences


Probable causes





41627, Faulty use of arg

Description

Task: arg

arg is used on store path level and system was not in synchronized motion mode before arg.

Program Ref. arg

Consequences


Probable causes





41630, Unsafe Synchronization

Description

Task: arg

To reach safe synchronization functionality, variable arg should be used only one time, not in several arg or arg instructions.

Program Ref. arg

Consequences

Program tasks/movements may not always be synchronized.

Probable causes

Use of arg several times in the same program.




Description

Task: arg

The program is executing in an EVENT routine. It is not allowed to execute the instruction arg in an EVENT routine with shelf arg.

Program Ref. arg


Remove the instruction

41632, Argument does not exist

Description

Task: arg

The functionality when using arguments TP_SCREENVIEWER and

TP_PROGRAM in instruction TPShow has been removed.

Program Ref. arg

Consequences

When the instruction with these arguments is executing nothing will happen.



41633, Can only be used in an UNDO handler

Description

Task: arg

The instruction arg can only be used in an UNDO handler.

Program Ref. arg

Consequences

Program execution will be stopped.


Use another instruction and/or move this instruction to the UNDO handler.

41634, Unknown Task Name

Description

Task: arg

The task name arg is unknown in the system.

Program Ref. arg

Consequences

It is not possible to execute this instruction with a task name that is not found in the system.



Probable causes

1. The program task is not defined in the system parameters.

2. The task name is wrong spelled.


Recovery: arg


Description

Task: arg

Unexpected SyncMoveOff (SyncID arg). The system is already in unsynchronized mode.

Program Ref. arg

Probable causes



Remove the SyncMoveOff instruction. Every SyncMoveOn must be followed by one SyncMoveOff instruction.



Description

Task: arg

Unexpected SyncMoveOff (SyncId arg) from Task not included in synchronized group.

Program Ref.arg

Probable causes



Remove the SyncMoveOff instruction. Every SyncMoveOn must be followed by one SyncMoveOff instruction.


41637, Task not active in task selection panel anymore

Description

Task: arg

The task arg is not active in the task selection panel anymore.

The task arg was active in task selection panel at start from main.

Because of that not possible to pass this arg instruction.

Program Ref. arg

Consequences

The program execution is immediately stopped..

Probable causes

The task arg has been deactivated in the task selection panel.


1) Activate task arg in the task selection panel.


2) To permanent skip task arg for the rest of this cycle run the service routine SkipTaskExec.

After that restart the instruction arg.

41638, Not allowed task activation

Description

Task: arg

The task arg is active in the task selection panel. This task was not active in the task selection panel when start from main was done. It is not allowed to add tasks in the task selection panel after start from main.

Program Ref. arg

Consequences

The program execution is immediately stopped.

Probable causes

1) The task arg was not active when start from main was done.

2) Deactivation of task arg with service routine arg, but not deactivating the task in the task selection panel.

3) Activation of task arg that earlier was deactivated in task selection panel and deactivated with service routine arg.


Move PP to main to reset tasks used at start from main. Then use the task selection panel to select which tasks that you want to execute.

41640, Move PP Warning

Description

Task: arg

Move of program pointer when path is stored may cause problems if moved to a place after the path restore.

Consequences

Path may unintentionally stay in a stored state.

Probable causes

Stop of program when having a stored path. Then a PP movement within the program has been done.


Ensure that restore of path is not skipped by moving PP to a RestoPath instruction if necessary.

41641, Move PP Warning

Description

Task: arg

Move of program pointer when stop motion is active may cause problems if moved to a place after stop motion deactivation.

Consequences

Restart of motion may be blocked.

Program execution may be waiting at motion instructions.

265


Probable causes

Stop of program when stop motion is active. Then a PP movement within the program has been done.


Ensure that stop motion deactivation is not skipped.


Description

Task: arg


Program Ref. arg


arg must be > 0 when arg = 0.

41646, Program Blocked from RAPID

Description

Task: arg

Program and movement are stopped and blocked with System Stop

RAPID Block from RAPID.

Program Ref. arg

Consequences

Due to a programmed System Stop RAPID Block in RAPID both program execution and movements are stopped. The problem causing the stop has preferable been presented in another log.

If the robot is performing a circular movement, the robot has to be moved to the beginning of the circular movement before restarting the program.


Find out why the program has been blocked (maybe in other logs), correct the problem and move program pointer in all motion tasks before restarting the program.


Description

Task: arg


Program Ref. arg


arg must be an integer when arg < 0


Description

Task: arg


Program Ref. arg


arg must greater or equal to 0.

41647, Program Halted from RAPID

Description

Task: arg

Program and movement are halted with System Halt from RAPID.

Program Ref. arg

Consequences

Due to a programmed System Halt in RAPID both program execution and movements are stopped. The problem causing the stop has preferable been presented in another log.


Find out why the program has been halted (maybe in other logs), correct the problem and turn motors on before restarting the program.

41645, Program Stopped from RAPID

Description

Task: arg

Program and movement are stopped with System Stop from RAPID.

Program Ref. arg

Consequences

Due to a programmed System Stop in RAPID both program execution and movements are stopped. The problem causing the stop has preferable been presented in another log.


Find out why the program has been stopped (maybe in other logs), correct the problem and restart the program.


Description

Task: arg

Not allowed to change run mode from forward to backward, from continues to stepwise or vice versa.

Program Ref. arg


Select the original run mode and continue program execution.

41649, Incorrect Error Message

Description

Task: arg

At least one of the arguments in the instruction arg exceeds the limitations described in the manual.

Program Ref. arg



Probable causes

The arguments to instruction arg contain limitations both on each string and the total amount of characters used in the instruction. This is described in the manual.


Consult the manual and correct the arguments.

41650, Task already stopped by another task

Description

The non motion task arg has executed a StopMove instruction. No stop action has, however, been taken because the motion task arg was already stopped by task arg.

Program Ref. arg

Consequences

The motion task must be started, with the instruction StartMove, from the task that stopped it or the switch \AllMotionTasks has to be used in

StartMove from this task.

41651, Ignored StartMove actions for task

Description

The non motion task arg has executed a StartMove instruction. The motion task arg has, however, not been started.

Program Ref. arg

Consequences

No movements can be performed if the motion task has been stopped by another non motion task.

Probable causes

1. The motion task has not been stopped.

2. The motion task was stopped by another non motion task arg.

This time the cause was arg.


Use the switch \AllMotionTasks in StartMove if this instruction should start a movement that is stopped by another non motion task.

41652, Forced StartMove action

Description

The non motion task arg has executed a StartMove instruction. The instruction discovered that the motion task arg has been stopped by this task. That motion task will be started to prevent inexplicable stopped movements.

Program Ref.arg

Probable causes

1. The motion task has been stopped with the switch \AllMotionTasks active in the StopMove instruction but not in the StartMove instruction.

2. The StopMove instruction has been executed in synchronized mode and the StartMove in independent mode.

41653, Argument error CalcJointT

Description

Task: arg

It is not possible to execute the function CalcJointT with argument

\UseCurWObjPos, if the coordinated workobject moved by some mechanical unit is located in the same task as the TCP robot or if the workobject is not moved by any mechanical unit at all.

Program Ref. arg


Remove the argument \UseCurWObjPos, so can the function

CalcJointT be executed and the calculation can be done with data solely from the RAPID program.

41654, Execution error CalcJointT

Description

Task: arg

It was not possible to execute the function CalcJointT with argument

\UseCurWObjPos, because the mechanical unit arg was moving at the time of execution of CalcJointT.

Program Ref. arg


Function CalcJointT with argument \UseCurWObjPos can only be exected without error, if the coordinated workobject moved by another task is standing still.

Recovery: arg

41655, Argument not a motion task

Description

Task: arg

The function CRobT or CJointT has been used with an argument that refer to an other task, arg. That task is not a motion task (controlling mechanical units) and can therefore not be used.

Program Ref. arg

Probable causes

CRobT or CJoinT with argument \TaskRef or \TaskName can only be used without errors if the task that the arguments refer to is a motion task.


Change the argument \TaskRef or \TaskName or remove it and restart the program execution.

Recovery: arg


Description

Task: arg


Program ref. arg




Check and change the value. It must be between arg and arg.


Description

Task: arg

Could not access the file/device arg.

Program Ref. arg

Probable causes

- The path or filename is wrong.

- The maximum number of simultaneously opened files is exceeded.

- The disk is full.

- Function does not support check of selected device.


- Check the path or filename.

- Check the disk space.

Recovery: arg

41658, Program task is in StopMove state

Description

Task: arg

No movement will be performed in this motion task, because the task is currently set in StopMove state ordered by some non-motion task.

Consequences

Not possible to start any movements.

Probable causes

Some non-motion task connected to this motion task has set the task in

StopMove state.


To perform movements in this motion task, the StopMove state must be reset by the responsible non-motion task with one of the following actions:

1) Execute StartMove

2) Start the non-motion task from main a) Do power off-on if semi static non-motion task b) Do installation start if static non-motion task c) Set PP to main if normal non-motion task

Probable causes

Too many open views.


Close one view and try again.

Recovery: arg

41661, Assembly could not be found

Description

Task: arg

1) The assembly could not be found, or does not exist.

2) The FlexPendant Interface option is missing.

Status arg.

Program Ref.arg

Consequences

The view will not be launched.

Probable causes

1) The assembly arg could not be found.

2) The system image does not include the required option FlexPendant

Interface.


1) Check inparameters. Make sure that the modules been loaded correctly to the robot controller.

2) Check that FlexPendant Interface option is used.

Recovery: arg

41662, Assembly could not be loaded

Description

Task: arg

The assembly was found but could not be loaded.

Status arg.

Program Ref.arg

Consequences



Make sure that the loaded modules are executable files for the

FlexPendant.

Recovery: arg

41660, No space left for the new view

Description

Task: arg

Maximum number of views has been exceeded.

There is no space left on the FlexPendant for the new view.

Program Ref. arg

Consequences


41663, Instance could not be created

Description

Task: arg

The assembly exist but no new instance could be created.

Status arg.

Program Ref.arg



Consequences



Make sure that the loaded modules are executable files for the

FlexPendant.

Recovery: arg

41664, The typename is invalid for this assembly

Description

Task: arg

The inparameter arg is invalid. The typename does not match the assembly.

Status arg.

Program Ref arg.

Consequences



Check the inparameters.

Recovery: arg

41665, arg does not match assembly to load

Description

Task: arg

The type or name of the assembly does not match with the used arg.

Status arg.

Program Ref arg.

Consequences


Probable causes

Use of arg without setting it to 0 first.


Set arg to 0 before using it.

Recovery: arg

41666, Fatal UIShow error

Description

Task: arg

Unknow error code arg received.

Program Ref. arg

Consequences



Report this to ABB Robotics.

41670, Entire Array Not Allowed As Argument

Description

Task: arg

The argument arg is of data type any type and can for that reason only be checked during runtime.

An entire array can not be used as argument even if the array is of right data type.

Program ref. arg

Consequences



Replace the array with a valid argument.

41671, Too high poll rate

Description

Task: arg

The specified poll rate is too high for the robot system.

Program Ref. arg

Consequences

The system can be overloaded.


Change instruction WaitUntil, argument \PollRate to a value greater than or equal to 0.01 s.

41672, Invalid Combination

Description

Task: arg

Invalid combination of paramters in Trigg

Program Ref: arg


Either run Trigg without /Time option or use TriggRampAO with option \Time on ramplength.

41673, Index Out Of Bounds

Description

Task: arg

Index for cfg instance was out of bounds

Program Ref: arg



Recovery: arg



41674, Value Out Of Bounds

Description

Task: arg

Parameter arg is not between the range of 0 to 100.

Program Ref: arg



Recovery: arg

41675, Not Integer

Description

Task: arg

Parameter arg is not an integer.

Program Ref: arg


Check the RAPID program, or use ERROR handler

Recovery: arg

41676, Device access error

Description

Task:arg

Unable to open File or Serial channel, 'arg' does not exist.

Program Ref: arg


Check file or serial channel name.

Recovery: arg


Description

Task: arg

Unable to write to file: arg, the disc is full.

Program Ref: arg


Make sure there are enough free space on the disc.

Recovery: arg


Description

Task: arg

Unable to write to file : arg, The file is write protected.

Program Ref:arg


Remove the write protection of the file or select a different filename.

Recovery: arg


Description

Task: arg

The maximum number of simultaneously opend files is exceeded.

Program Ref: arg


Close one or more I/O devices and try again

Recovery: arg

41680, String too long

Description

Task: arg

The string arg exceeds the maximum number of characters allowed for a module.

Program Ref: arg


Change the string for module name.

Recovery: arg

41682, Too many subscriptions from I/O

Description

Task: arg

The number of simultaneous subscriptions on signal events has been exceeded.

Program Ref: arg


Remove some subscriptions on signals or change the time for the event.

(i.e any ISignalXX or TriggIO)


Description

Task: arg

The argument arg must be given when searching for a not named parameter.

Program Ref: arg


Add the parameter arg to the instruction.


Description

Task: arg

The argument arg is outside the range of value type unsigned long.

Program Ref: arg



Probable causes

The value is to large.


Use a smaller value for arg

41685, Not valid value

Description

Task: arg

A wrong combination of switch and value is used.

The signal can have values between:

Min: arg

Max: arg

Switch and value used: arg

Program Ref. arg

Consequences


Probable causes

Wrong value used, or wrong switch used.


Change the value used, or change the switch argument.

41687, File Open Error

Description

Task: arg

Unable to open arg

Program Ref: arg

An unknown error occured while opening the file.

Probable causes

- If the file was located on an USB disk, check that the disk is not removed, or has to many files in root folder.

- Check that the given file is not a directory


Do a check of Probable Causes.

Recovery: arg

41688, Invalid Argument

Description

Task: arg

Inparameter arg is declared as a PERS.

Program Ref: arg

Consequences


Probable causes

Using a PERS in argument arg to instruction arg.



Replace the PERS with a valid argument.


Description

Task: arg

The argument arg is of the type arg and is not valid to use.

Program Ref. arg

Consequences



Check the data type. Non-value, semi-value types or motsetdata data type can not be used.

41691, RMQ Error - Client name not valid

Description

Task: arg

The name arg can not be found. It is not a valid RMQ client name.

Program Ref. arg

Probable causes

A non valid name is used.


Change name to search for.

Recovery: arg

41692, RMQ Error - Not valid Slot

Description

Task: arg

The arg used is not valid.

Program Ref. arg

Consequences

Communication with client with current arg is no longer possible.

Probable causes

1) The arg has not been initialized.

2) The destination slot is not valid anymore. This can happen if a remote client has disconnected from the controller.

3) Instruction RMQSendWait was restarted after a power fail. When the instruction is restarted, the arg is set to 0.


Recovery: arg

41693, RMQ Error - Max size for message exceeded

Description

Task: arg

271


The size of the data in arg exceeds maximum size.

Program Ref. arg

Consequences

The message will not be sent.

Probable causes

Trying to send larger messages then arg. Due to limitations in RMQ, such big messages can not be sent.


Send smaller messages.

Recovery: arg

41694, RMQ Error - Not equal datatypes

Description

Task: arg

The datatype in the rmqmessage is of the type arg and the datatype in argument Data is of the type arg.

Program Ref. arg.

Consequences

No data can be fetched.

Probable causes

1) The data type in the rmqmessage is of type arg and the data type used in argument Data is of type arg.

2) If the data types has equal names, the structure of the data can be different.


1) Use datatype arg in argument Data.

2) Check that the data types are equal defined in both sender and receiver code.

Recovery: arg

41696, RMQ Error - Not valid use of instruction

Description

Task: arg

The instruction arg is only supported on TRAP level.

Program Ref. arg

Consequences


Probable causes

Instruction arg is used either on user execution level or normal execution level.


Remove instruction, or move it to a TRAP routine.

41697, RMQ Error - No RMQ configured

Description

Task: arg

No RMQ is configured for task arg.

Program Ref. arg

Consequences


Probable causes

No configuration has been added for the RAPID Message Queue.


Add configuration for the RAPID Message Queue.

41695, RMQ Error - Not equal dimensions on data

Description

Task: arg

The data types are equal, but the dimensions differs between the data in the message and the parameter used in argument arg

Program Ref. arg

Consequences

The data could not be copied.


Use a parameter in argument arg with equal dimensions as the data in the message.

Recovery: arg

41698, RMQ Error - Faulty use of instruction

Description

Task: arg

Instruction arg can only be used on normal level, not in a TRAP routine or service routine.

Program Ref. arg

Consequences


Probable causes

Instruction arg used on wrong level.


Use instruction on normal level.

41699, RMQ Error - Max size for message exceeded

Description

Task: arg

The size of the data in arg exceeds maximum size.

Program Ref. arg



Consequences

The message will not be sent.

Probable causes

Trying to send larger messages then allowed. The receiving client is not configured to receive the size of the message sent.


Change the size of the RMQ for the receiver, or send smaller messages.

Recovery:arg

Consequences

The program execution is immediately stopped

Probable causes

Use of a variable arg that not contain any valid data. The variable has only been initialized, no valid data has been copied to the variable.



41700, RMQ Error - Interrupt setup failed

Description

Task: arg

Two different interrupt identities can not be used for the same data type in instruction arg. Each data type need a unic interrupt identity and unic TRAP routine.

Program Ref. arg

Consequences


Probable causes

Same data type is used in two arg instructions with two different interrupt identities.


An unic interrupt identity is needed for each data type when order and enable interrupts for a specific data type.

41703, RMQ Error - Data could not be copied

Description

Task: arg

The data type arg exceeds the maximum size supported for the RMQ configured for task arg.

Program Ref. arg

Consequences

No message has been received.

Probable causes

The RMQ of the receiving task is not configured for the size of the data sent. The sending client have sent data that is bigger then the size the

RMQ for task arg can receive.


Increase the size of the RMQ for task arg.

Or, send less data.

Recovery: arg

41701, RMQ Error - No message to collect

Description

Task: arg

Instruction arg failed. There was no message to collect.

Program Ref. arg

Consequences

No message was collected.

Probable causes

1) This can happen if ta power fail occur between the trap was ordered and the instruction arg was executed.

2) If multiple use of arg in a TRAP routine.

3) If using arg in a TRAP routine that execute without any new message in the RMQ.


Recovery: arg

41704, RMQ Error - Full Queue

Description

Task: arg

The client named arg can not receive more messages.

Program Ref. arg

Consequences

The sent message will be thrown.

Probable causes

The client does not receive in the same pace as the sender is sending messages. If using instruction arg, you might need a wait time between each arg instruction.


The client should receive messages to make room for new messages.

Or the sender should limit the number of messages sent.

Recovery: arg

41702, RMQ Error - arg not valid

Description

Task: arg

Use of non-valid data in argument arg.

Program Ref.arg

41705, RMQ Error - Max Time Expired

Description

Task: arg


Program Ref. arg



Consequences

There is no guarantee that the message has arrived to the client.

Probable causes

1) The client that should receive the message is not interested of receiving data of the specified data type. The message has been discarded.

2) The client has received the message, and in the answer sent a data type not matching with the specified data type used in arg of instruction arg.

3) The client has received the message. The answer is delayed so the time out time for instruction arg expired.


1) Check the client program.

2) Increase the waiting time for instruction arg.

Recovery: arg

41706, RMQ Error - Max Time Expired

Description

Task: arg


Program Ref. arg

Consequences

No message has been received.

Probable causes

The time out time for instruction arg expired.


Increase the waiting time for instruction arg.

Recovery: arg

The received RMQ message was invalid.

Program Ref: arg

Consequences

The received RMQ message was discarded.

Probable causes

A received RMQ message had a corrupt header or data part.


Recovery: arg

41711, Value is not percent

Description

Task: arg

The value of argument arg is not a valid percent.

Program Ref: arg


Check that the value is in the range of 0 to 100.


Description

Task: arg

Tooldata arg has been defined, but is no longer available in the system.

Program Ref: arg

Probable causes

Tooldata might have been defined in a module that is no longer available in the system.

41707, RMQ Error - Instruction invalid in current mode

Description

Task: arg

arg is only allowed when RMQ is configured in arg mode.

Program Ref: arg

Consequences


Probable causes

The RMQ is configured in arg mode


Change the configuration of the RAPID Message Queue in arg to arg mode, or use an instruction that is allowed in the current mode.

41708, RMQ Error - Invalid message

Description

Task: arg


Description

Task: arg

Wobjdata arg has been defined, but is no longer available in the system.

Program Ref: arg

Consequences

Wobjdata might have been defined in a module that is no longer available in the system.

41714, Too many error events

Description

Execution of task arg has stopped. There are too many unhandled error events in queue. The system can only handle one error event at a time.

Consequences

The system goes to blocked state and can not be restarted before moving the program pointer to an arbitrary position.



Probable causes

A power fail restart (warm start) occurred while handling a process error.


Never warm start the system while handling a process error. If warm start is needed, first move PP to Main in all tasks to reset the process error.

41715, Invalid Direction

Description

Task: arg

The argument arg must be either CSS_X, CSS_Y or CSS_Z.

Program Ref: arg


Check the value of arg

41716, Invalid Offset Direction

Description

Task: arg

The argument arg must be either

CSS_POSX, CSS_NEGX, CSS_POSY, CSS_NEGY, CSS_POSZ,

CSS_NEGZ

Program Ref: arg


Check the value of arg

41717, Too Low Value

Description

Task: arg

The value of argument arg is too low.

Program Ref: arg


Increase the value of arg

41718, Invalid Dimensions

Description

Task: arg

Dimension arg on searched symbol is incompatible with dimension

arg in argument.

Program Ref: arg.

A dimension of '{0}' means given symbol is of non array type.


Recovery: arg

41719, Illegal Parameter

Description

Task: arg

The symbol in argument arg is an array from a parameter. Arrays from paramters are illegal to use in SetDataVal/GetDataVal.

Program Ref: arg

41720, Path Not In Stop Point

Description

Task: arg

The path did not finish for the following task(s): arg make sure the task is running.

Program Ref: arg

Probable causes

The task is not running or the movement has been stopped.


Recovery: arg

41721, Invalid Argument

Description

Task: arg

The type arg in argument arg is invalid.

Program Ref: arg


Change the type to a valid one (arg).

41722, Too High Value

Description

Task: arg

The value of argument arg is too high. The value must be between arg and arg.

Program Ref: arg

41723, Bus is in error state

Description

Task: arg

The I/O unit arg can not be activated. The bus arg is in error state.

Program Ref. arg

Consequences

Unit arg could not be activated.

Probable causes

Bus is in error state.


Recovery:arg



41724, Current Work Object is Invalid

Description

Task: arg

Cartesian Soft Servo Activation is not allowed with a moving work object. Only a programmed user frame is allowed.

Program Ref: arg


Description

Task: arg

The signal arg is too big. If using signals over 23 bits, use the datatype triggiosdnum that accept signals up to 32 bits.

Program ref. arg


Group signals can have 23 bits or less if using datatype triggios in arg instruction.

41725, Invalid Configuration Settings

Description

Task: arg

The configuration parameters for Cartesian Soft Servo are invalid.

The current combination can lead to unstable behaviour.

Program Ref arg


Change the configuration for Cartesian Soft Servo

41726, Ignored StopMoveReset actions for task

Description

Task: arg

The StopMoveReset instruction had no impact on the system

Program Ref: arg

Consequences

The StopMove was not reset.

Probable causes

1. The motion task has not been stopped.

2. The motion task was stopped by another non motion task: arg.

This time the cause was arg.


Use the switch \AllMotionTasks in StopMoveReset if this instruction should reset a StopMove from another non motion task.

41727, The size can not be represented in a num

Description

Task: arg

When using instruction arg to read the size of the file system, it was detected that the value is to big to be set in a num.

Program Ref:arg

Consequences

The size can not be read.

Probable causes

The value can not be represented in a num.


Use a switch to specify another unit to show the size in.

Recovery: arg

41731, Signal name undefined

Description

Task: arg

The signal arg is unknown in the system.

Program Ref. arg

Consequences


Probable causes

The signal must be defined in the system parameters.


Define the signal in the system parameters.

41732, Too many trigs used

Description

Task: arg

Too many trigs has been set up for instruction arg. The limit is arg.

Program Ref. arg

Consequences



Remove some trig actions in arg instruction.

41737, Instruction order Error

Description

Task: arg

The instruction arg needs to be executed before instruction arg.

Program Ref. arg.

Probable causes

Instruction arg was executed before instruction arg.


Execute instructions in right order.

Recovery: arg



41738, Wrist Interpolation option needed

Description

Task: arg

Instruction arg is used with a switch that requires option Wrist

Interpolation.

Program Ref.arg

Consequences


Probable causes

Missing a Robotware option.


Do not use any of the following switches: arg.

41739, StorePath required

Description

Task: arg

Instruction arg is executing in an error handler or a trap routine. Use

arg before using a movement instruction on other level then base.

Program Ref. arg

Consequences


Probable causes

A movement instruction executed without having the path stored.


Execute arg before using movement instruction arg.

Read Programming type examples in the RAPID manual to see how to use movement instructions in TRAP routines and error handlers.

41740, Load Identification failed

Description

Task: arg

WARNING!

Not possible to identify the mass for the arg because of too small weight for automatic load identification.

Program Ref. arg


Do a manually estimation of the actual load and manually edit the

RAPID program.

41741, Calculation overflow

Description

Task: arg

The calculation result is not within the range 0 - 4294967295.

Program Ref. arg

Consequences

The calculation will return error.

Probable causes

The values in the operation is probably to big.


Recovery: arg

41742, Negative subtraction

Description

Task: arg

The subtraction result is negative.

Program Ref.arg

Consequences

The calculation will return error.

Probable causes

The first value in the subtraction is smaller than the second value.


Make sure the first value is larger than the second upon subtraction.

Recovery: arg

41743, Division with zero

Description

Task: arg

Division with zero

Program Ref. arg

Consequences

Calculation will return error.

Probable causes

Division with zero.


Recovery: arg


Description

Task: arg

The program is executing in an ERROR handler. It is not allowed to execute the instruction arg in an ERROR handler.

Program Ref. arg




Description

Task: arg



The program is executing in an BACKWARD handler. It is not allowed to execute the instruction arg in an BACKWARD handler.

Program Ref. arg



Probable causes

The value is to large.


Use a smaller value for arg.

Recovery: arg


Description

Task: arg

The program is executing at USER level, i.e. in an event routine or a service routine. It is not allowed to execute the instruction arg at USER level.

Program Ref. arg



41747, Process signal off

Description

Task: arg

The process signal arg is set to off (0).

Program Ref. arg

Consequences

A recoverable error ERR_PROCSIGNAL_OFF is thrown.

Probable causes

The optional argument \ProcSignal has been used for the instruction

ProcerrRecovery. The signal makes it possible for the user to turn on/ off the instruction ProcerrRecovery.


Add an error handler for ERR_PROCSIGNAL_OFF error or remove the optional argument \ProcSignal from the instruction call.


Description

Task: arg


Program ref. arg

Probable causes

1) The system has interpreted the expression as a num data type, and the value is above the maximum integer value for num (value

8388608).

2) The system has interpreted the expression as a dnum data type, and the value is above the maximum integer value for a dnum (value

4503599627370496).



The parameter name arg can give you information about how the system interpreted the indata.

41751, Array size error

Description

Task: arg

The array arg is not big enough to fit arg number of elements.

Program Ref. arg

Consequences



Change the size of the array to fit all elements.


Description

Task: arg


Program Ref. arg



Recovery: arg

41752, Num Limit Error

Description

Task: arg

The value for parameter arg is out of limit.

Program Ref. arg


Recovery: arg


Description

Task: arg

The value for parameter arg is out of limit.

Program Ref: arg

41753, Invalid path level

Description

Task: arg

Program Ref. arg

arg requires the robot to run at the first path level.



Consequences


Probable causes

Executing arg on wrong path level.



41754, Path Recorder cleared

Description

Task: arg

WARNING!

Path Recorder is cleared. The stored path is cleared before doing friction identification.

Program Ref. arg

41756, Missing FricIdInit

Description

Task: arg

arg must be executed before arg.

Program Ref. arg

Consequences


41758, Array too small

Description

Task: arg

The array used is too small.

The size of the array arg must be equal to arg, the number of robot axes.

Program Ref. arg

Consequences



Increase the size of the array arg.

41755, Path time too long

Description

Task: arg

Execution time is too long for friction tuning. arg > arg, which is the maximum time in seconds.

Program Ref. arg

Consequences



Increase speed or shorten the length of the path.


Description

Task: arg

The signal arg is too big.

Program ref. arg


Group signals consisting of 23 bits or less can be used in IF statements and assigned to the num datatype.

Group signals consisting of 24 - 32 bits can not be used in IF statements. Instead use the functions arg or arg.

41760, arg when in synchronized mode

Description

Task: arg

arg cannot be used together with synchronized movement.

Program ref.: arg

Consequences



Remove any SyncMoveOn between arg and arg

41757, Mechanical unit not found

Description

Task: arg

Mechanical unit arg not found.

Program Ref. arg

Consequences



Specify another mechanical unit.

41761, Value out of range

Description

Task: arg

The integer value arg can not be copied to a arg datatype. The value is out of limit for the data type arg.

Program ref.: arg

Consequences



Use a variable of the type arg instead of a variable of type arg.



41762, The argument string value is invalid

Description

Task: arg

The argument string arg is invalid and can not be converted.

Program ref.: arg

Consequences


Probable causes

1) The only valid letter characters is a-f and A-F and only for

HexToDec.

2) The ., - and + characters is not valid for HexToDec.

3) The - character is not valid for DecToHex.

4) The value is not an valid integer.


Edit the argument value string so it gets valid and can be converted.

41763, The argument string value is too high

Description

Task: arg

The argument string arg value exceeds the highest supported value in the system.

Program ref.: arg

Consequences

The argument value string is converted but it is set to the highest supported value (9223372036854775807).

Probable causes

The argument string value exceeds the highest supported value.


Edit the argument value string so it do not exceed the highest supported value.

41765, The argument value is too high

Description

Task: arg

Too high value in argument arg.

Program Ref. arg

Probable causes

The argument value exceeds the highest supported value. (arg)


Decrease the value for argument arg.

Recovery: arg

41766, Illegal combination of inarguments

Description

Task: arg

It is not allowed to combine argument arg with argument arg.

The value to be stored in the variable can be higher then the maximal value for a num integer.

Program Ref. arg

Consequences



Use argument arg instead.

50021, Joint position error

Description

Actual position of joint arg is too far away from the ordered position.


Check tuning parameters, external forces or hardware.

41764, Wrong combination in arg

Description

Task: arg

When using instruction arg, you can not add a dnum variable/ persistent to a num variable/persistent.

Program ref.: arg

Probable causes

The value to be added is of the type dnum, and the variable/persistent that should be changed is a num.


Read about arg in RAPID reference manual

50022, Too low DC-link voltage

Description

The drive units cannot detect the dc link voltage, or the voltage is too low.

This can occur if the DC link bus bar is not correctly inserted or if the mains contactors do not close properly.


Check the DC bus bar is correctly inserted between the drive unit and the rectifier.

Check that the motors on contactors are closed and that there is voltage on the side connected to the rectifier.

50024, Corner path failure

Description

Task: arg



Corner path executed as stop point due to some of the following reasons:

- Time delay.

- Closely programmed points.

- System requires high CPU-load.

Program Ref. arg


- Reduce the number of instructions between consecutive move instructions.

- Reduce speed, use wider spaced points, use /CONC option.

- Increase ipol_prefetch_time.


Use the joystick to move the involved joint into the working range again.

50030, Robot outside its limits

Description

Jogging was made in wrong direction when parallelogram was out of working range for robot arg.


Use the joystick to move the joint in opposite direction.

50025, Restart interrupted

Description

Current position is too far from path.


Make a new restart with regain.

50031, Command not allowed

Description

System parameters cannot be changed in MOTORS ON state.


Change to MOTORS OFF.

50026, Close to singularity

Description

Task: arg

Robot too close to singularity.

Program Ref. arg

(Internal code: arg)


Modify path away from the singularity or change to joint interpolation.


Description

An attempt was made to calibrate while in MOTORS ON state.



50027, Joint Out of Range

Description

Position for arg joint arg is out of working range.


Use the joystick to move the joint into its working range.


Description

An attempt was made to commutate the motors in MOTORS ON state.



50028, Jog in wrong direction

Description

Position for arg joint arg is out of working range.




Description

An attempt was made to synchronize in MOTORS ON state.



50029, Robot outside its limits

Description

The robot arg has reached the configuration limit for the parallelogram transmission.

50036, Correct regain impossible

Description

A stop occurred with too many close points with corner zones. At restart the robot will move to a point farther forward in the program.


Reduce the number of close points, increase the distance between them or reduce the speed.



50037, MOTORS ON order ignored

Description

MOTORS ON order ignored since the previous stop was not yet acknowledged.


Order MOTORS ON again.

50041, Robot in a singularity

Description

The robot is too close to a singularity.


During program execution, use SingArea instruction or joint interpolation.

During jogging, use axis by axis.

50053, Too large revolution counter difference

Description

Too large revolution counter difference for joint arg. The system has detected too large a difference between the actual revolution counter value on the serial measurement board and the value anticipated by the system.

Consequences

The robot is not calibrated and may be jogged manually, but no automatic operation is possible.

Probable causes

The position of the robot arm may have been changed manually while the power supply was switched off. The serial measurement board, resolver or cables may also be faulty.


1) Update the revolution counter.

2) Check resolver and cables.

3) Check the serial measurement board to determine whether it is faulty. Replace the unit if faulty.

50042, Could not create path

Description

The path could not be created.


Increase the distance between close points and/or decrease speed and/ or change acceleration value.

50050, Position outside reach

Description

Position for arg joint arg is outside working area.

Joint 1-6 : Number of the axis which causes the error.

Joint 23: Combination of axis 2 and 3 causes the error.

Probable causes

The reason may be that ConfL_Off is used and a movement is too large, more than 90 degrees for an axis.


- Check work object or working range.

- Move the joint in joint coordinates.

- Check motion configuration parameters.

- Insert intermediate points on large movements.

50055, Joint load too high

Description

Actual torque on joint arg too high. Might be caused by incorrect load data, too high acceleration, high external process forces, low temperature or hardware error.


-Check load data.

-Reduce acceleration or speed.

-Check hardware.

50056, Joint collision

Description

Actual torque on joint arg is higher than ordered while at low or zero speed. Might be caused by jam error (the arm has got stuck) or hardware error.


Check that arm is not stuck.

Check hardware.

Check for other hardware eventlogs.

50052, Joint speed error

Description

The speed of joint arg is wrong relative the ordered speed due to error in system or collision.


- Check the tune parameters, external forces on the joint and hardware.

- Reduce programmed speed.

50057, Joint not synchronized

Description

The position of joint arg after power down/failure is too far away from the position before the power down/failure.


Make a new update of the revolution counter.



50058, Tool coord. system error

Description

The z-direction of the tool coordinate system is almost parallel with the path direction.


Change the tool coordinate system to achieve at least 3 degrees deviation between z-direction and path direction.

50067, Unit not active

Description

Attempt to coordinate motion or calculate position of deactivated single unit arg.


Activate unit via Motion Unit key, then Jogging window, or program.

Check work object and program.

50060, Incorrect tool

Description

The definition of stationary tool is not valid.


Check the tool and object data.

50076, Orientation not correct

Description

Orientation is incorrectly defined.


Make an accurate normalization of the quaternion elements.

50063, Circle uncertain

Description

Task: arg

The points are misplaced, reasonarg:

1 End point too close to start point.

2 Circle point too close to start point.

3 Circle point too close to end point.

4 Uncertain reorientation.

5 Circle too large > 240 degrees.

Program Ref. arg


Check the points of the circle and the end point of the move instruction before. The points of the circle can be verified by stepping trough the circle in manual mode.

50078, Too many close positions

Description

Too many consecutive closely spaced positions.


Increase the distance between consecutive close positions.

50079, Cannot use wrist weaving

Description

Wrist weaving not possible.


Use smaller weaving amplitude or a larger TCP.

50065, Kinematics error

Description

The destination of the movement is outside the reach of the robot or too close to a singularity. Robot arg.


Change the destination position.

50080, Position not compatible

Description

The desired position cannot be reached with the given robot configuration. Robot arg.


Modify the robot position in the program.

50066, Robot not active

Description

Attempt to coordinate motion or calculate position of deactivated robot

arg.


Activate robot via the Motion Unit key, then Jogging window, or program. Check work object and program.

50082, Deceleration limit

Description

The path calculation for mechanical units running in motion planner

arg exceeds internal limit. The motion planner task did not execute within its time limit.

Probable causes

The cpu load is to high. Could for example be generated by to frequent

EIO communication.


1. Set system parameter High Interpolation Priority for the affected

Motion Planner.



2. Try to reduce the cpu load by one or more of the following actions:

- Reduce speed

- Change AccSet

- Avoid singularity (SingArea\Wrist).

- Increase Path Resolution for the affected Motion Planner using system parameter or by using the Rapid instruction PathResol for critical movements.

- high weaving frequency

- not allowed shift of weave method or

- that SingArea/Wrist is used with wrist weave.

Program Ref. arg


Increase weave length or period time.

Don't shift between arm and wrist weave.

Use SingArea/Off with wrist weave.

50083, Speed lowered by system.

Description

The speed has been lowered by the system due to dynamic limitations.


Decrease speed and/or do not use close positions at high speed and/or increase acceleration (if below 100%).

50091, Restart not possible.

Description

Restart no longer possible. Change of unit state made restart of program impossible.


Move the program pointer and start a new movement.

50085, Too many user frames.

Description

For mechanical unit arg more than one user frame has been defined.


Take away one user frame or define one more mechanical unit.

50092, Axis computer response

Description

Incorrect response from axis computer.


Check motion configuration parameters.

Check axis computer hardware.

50086, Singularity problem

Description

Too close to wrist singularity with respect to numerical resolution for joint 4 of arg.


Change destination position a few increments.

50094, TuneServo not possible

Description

Tuning is not implemented for the specified joint.


Verify that a parameter and/or joint that can be used with TuneServo is chosen.

50087, Singularity problem

Description

Too close to wrist singularity with respect to numerical resolution for joint 6 of arg.


Change destination position a few increments.

50095, Cannot access joint.

Description

Cannot access external joint.


Check configuration and activation of external Joints.


Description

It is not possible to restart the path due to a previous error.


Move the program pointer to clear the path and start a new movement.

50089, Weaving changed

Description

Task: arg

The ordered weaving is not achieved due to:

50096, TuneServo not allowed

Description

Tuning is not allowed for the specified joint.


Verify that a parameter and/or joint that can be used with TuneServo is chosen.



50100, Manipulator configuration

Description

There are more configurations or numerical errors in motion domain.


Correct previous ones and try again.

50132, Commutation failed

Description

Commutation failed for joint arg.


- Make a new commutation.

- Restart the system.


Description

'arg' is not free for the param.

'arg' in type 'arg' named 'arg'.


Use another one. For internal names, see moc_chk.log.

50133, Test signal error.

Description

No test signals are available for robot arg.


Verify that correct test signals are defined.


Description

'arg' used in the parameter 'arg' in type 'arg' named 'arg' is not defined.


Use another one that is defined or define the used one. For internal names, see moc_chk.log.

50134, Corr. vector warning

Description

Sensor correction vector calculations failed due to previous error.



Description

The orientation defined by quaternions including 'arg' in the type 'arg' named

'arg' is not normalized.(SQRSUM =1)


Check the quaternions and/or recalculate them. For internal names, see moc_chk.log.


Description

The parameter 'arg' in type 'arg' named 'arg' is not 'arg'.


Check the value. For internal names, see moc_chk.log.


Description

Terminating the topic check for manipulator due to earlier errors.


Correct the reported errors and run topic check again.

50135, SoftAct not possible.

Description

Soft servo is not possible to activate.


Verify that a joint that can be used with SoftAct is chosen.

50137, No finepoint

Description

Continous mode without any finepoint in the program.


Change at least one corner zone in the program to a fine point.

50138, Arm check point limit

Description

The robot arg has reached the limit for arm check point.


Use the joystick to move the involved joint into the working range again.

50139, Arm check point limit

Description

Jogging was made in wrong direction when arm check point was out of working range for robot arg.





50140, Payload too large

Description

Heavy payload caused static torque limit to be exceeded on joint arg.


Check and reduce payload for arm and/or wrist. Reduce joint working range to decrease static torque due to gravity.


If estimated error is unacceptable:

- Verify that correct TCP is used.

- Try more than 3 reference points.

- Be careful when positioning robot to reference points.

50141, Jog or Speed error

Description

One of the following problems occured:

-Jogging error

-High speed error

-Robot too close to singularity


-Jog with incremental movement

-Reduce the programmed speed

50145, Kinematic limitation

Description

Kinematic limitation for robot arg, no solution found.

- Long segment.

- Position close to singularity.

- Joint 1, 2 or 3 out of range.

- Position outside reach.


- Insert an intermediary point to reduce the length of the segment.

- Use MoveAbsJ.

- Check working range.


Description

Configuration of the manipulator failed.

arg arg


Check the parameter values under System parameters:Manipulator. If mismatch between int/ext parameters i.e. wrong MOC.cfg loaded - cold start the system with correct parameters.

50146, Restart limitation

Description

Corner path executed as a stop point. Power fail restart not possible near the stop point.


Use finepoint in the Move-instr before RestoPath, ActUnit, Wait or

Stop-instr to make power fail restart possible.

50143, Robot axes configuration

Description

Actual configuration is not the same as ordered and/or movement of any robot axis is larger than 90 degrees. Robot arg, axis arg.


Use SingArea_Wrist, ConfL_Off, modify position or insert intermediary point.

Proceding in Auto mode will not be possible without correcting the configuration. To be able to move to the position anyway change to

Manual mode and repeat start.

50144, Displ frame uncertain

Description

Calibration of displacement frame uncertain for robot arg, due to one or several of:

- Wrong TCP.

- Reference points inaccurate.

- Reference points badly spaced.

50147, Power fail restart failed

Description

Re-creation of the path failed.


Move the program pointer and start a new movement.


Description

Task: arg

The given instruction, or command, was not allowed since the robot program was executing in a hold state.

(Internal code: argarg)

Program Ref. arg


Modify program or stop program execution before issuing command.


Description

SingArea\Wrist mode interpolation is not supported for the arg robot.




Replace SINGAREA\WRIST instruction with SINGAREA\OFF.

- Check the used work object.

50155, Power fail restart failed

Description

Not possible to restart the Move-instruction before RestoPath,

ActUnit, Wait or Stop-instruction.


Remove MOTION WARNING 50146 Restart limitation, by changing the Move-instruction to finepoint. Move the program pointer and start a new movement.

50161, Singularity area

Description

Robot arg is close to a singularity. Work area with kinematic limitations.


During jogging, use axis by axis. During program execution, use

MoveAbsJ.

50156, Not an independent joint

Description

Joint arg is not configured as an independent joint.


Modify the program or configure the joint as an independent joint.

50162, Internal position error

Description

Error caused by internal numerical limitation.


- Reset independent joint.

- Reduce work area if extended.

- Remove or separate close points.


Description

Sensor correction vector X calculations failed due to previous error.


50158, Sensor process missing

Description

Sensor process missing during initialization. Named sensor process

arg could not be found or initialized.


Check process name in motion and process configuration files.

50163, Position adjustment

Description

External position adjustment too large. TCP speed, orientation speed, or external position speed exceed allowed robot performance.


- Reduce programmed TCP- and orientation speeds.

- Modify the path.

- WaitWObj closer to sync.

- Run in AUTO.

50159, No external process

Description

Attempt to coordinate motion or calculate position of single arg without an external process.


Check process name in motion and process configuration files.

50164, Deactivation not possible

Description

Deactivation of mechanical unit may not be done while in independent mode.


Make sure that independent mode is not used and try to deactivate again.

50167, Warning: new sync

Description

Warning: a new object sync signal has arrived while conveyor is active and program is running.

50160, Cannot reach position

Description

Programmed position of independent joint arg is outside working range and thus cannot be reached.


- Change the position.

- Check the joint working area limits.




50168, New sync on arg

Description

New object sync arrived while conveyor was tracking the previous object. Cannot track two objects simultaneously.


Reduce speed of conveyor. Increase programmed speed.

50175, Conveyor moving

Description

Conveyor arg moving while attempt to coordinate robot TCP to conveyor work object while in prohibited mode.


It is not possible to coordinate to conveyor while in Manual Reduced

Speed, or stepping in Auto, and the conveyor is moving.

50171, Speed too low

Description

Numerical problem when interpolation of long segments with low speed and heavy additional axes or when interpolation close to singularity.


Split segments with long interpolation time (path_resolution * 4 minutes) or change to joint interpolation or move position away from singularity.

50172, MoveJ not allowed

Description

MoveJ not allowed with work object coordinated with external position mechanical unit.


Change interpolation mode or work object.

50176, Conveyor not active

Description

Conveyor arg was not active when attempt to coordinate robot TCP to conveyor work object.


Make sure conveyor mechanical unit is active. Check for fine point for last coordinated motion before DeactUnit.

50177, Unable to restart

Description

Conveyor arg moving while attempting to restart or before pressing

Stop or stepping through program.


Make sure conveyor is standing still. Move the program pointer and start a new movement.

50173, Fine point necessary

Description

Use fine point when changing tool or work object coordination when work object is coordinated with external position mechanical unit.


Create a fine point and then change the tool.

50178, Non optimal movement

Description

Required torque too high. Manual adjustment of acceleration or speed is needed.


Reduce acceleration (AccSet 50 100) in this movement, restore it afterwards (AccSet 100 100). Optimize performance by search for max acceleration 50-99. Alternatively, reduce speed.

50174, WObj not connected

Description

The WObj is not connected to the conveyor arg. Robot TCP cannot be coordinated to work object. Object can be dropped because of time synchronization fault on conveyor node.


Check for missing WaitWObj.

Check for DropWObj occuring before end of coordination.

Check for time synchronization fault, see status on conveyor node.

50181, Out of coupled range

Description

Joint arg and arg are out of coupled working range.


Use the joystick to move joints into their coupled working range.

50182, Jog in wrong direction

Description

Joint arg and arg are out of coupled working range.


Use the joystick to move joints into their coupled working range.



50183, Robot outside work area.

Description

The robot has reached the World Zone arg, arg


Check the reason of the World Zone. Use the joystick to move the robot out of the World Zone if needed.


Description




Check I/O signal definitions and System Parameters definition of

Manipulator, Types: Relay.

50190, Permanent interpolator lock error

Description

Scanned number of active joints not equal to expected number of joints.


Check configuration of the unit that is using general kinematics.


Description



50191, Too many TCP speed's

Description

The number of TCP speed's in one segment is too large. Maximum number of TCP speed's is arg.


Check if one segment has too many TCP speed's set or if a sequence of segments have increasing DipLag.

50186, Missing function

Description

Not possible to run robot arg with coordinated base frame. Function not installed in this system.


Install the option Multiple Axis Positioner.

50192, Jogging error

Description

Jogging is started too soon after program stop.


Try to jog the robot again.


Description

Not possible to coordinate user frame with robot arg Function not installed in this system.


Install the option Multiple Axis Positioner.

50193, Joint not synchronized

Description

The speed of joint arg before power down/failure was too high.


Make a new update of the revolution counter.

50188, Non optimal movement

Description

Required torque too high. Manual adjustment of weave frequency or amplitude is needed.


Reduce weave frequency or weave amplitude in this movement.

Alternatively, reduce speed.

50194, Internal position error

Description

Error caused by internal numerical limitation. Joint number arg.

Calculated reference position = arg.


- Adjust the system parameters in Uncal ctrl master 0.

- If TuneServo is used, adjust parameter Tune_df.

50189, Relay signal not found

Description

The signal arg for relay arg is not found in the I/O configuration. The mechanical unit using this relay is ignored.

50195, Cannot move independent

Description

Joint arg cannot be moved in independent mode.


Make sure that independent mode is not used when trying to move joint.



50196, Calibration failed

Description

Points 0 and 1 too close.


Make a new calibration with larger distance between points 0 and 1.


Description

Points 0, 1, 2 on a line or point 2 too close to points 0 or 1.


Make a new calibration with points moved so that 0, 1 and 2 are not on a line or with larger distance between point 2 and points 0 and 1.


Description

Internal error during calibration due to unknown origin switch.


- Report the occurance to ABB.

- Make a new calibration.


Select another node.

50204, Motion supervision

Description

Motion supervision triggered for axis arg on mechanical unit arg.

Consequences

The movement of mechanical unit arg is halted immediately. It then returns to a position on the path on which it was running. There, it will remain in status Motors ON, awaiting a start request.

Probable causes

Triggering of the motion supervision may be caused by a collision, incorrect load definition or forces in external process.


1) If possible, acknowledge the fault, and resume operation by pressing the Start button on the teach pendant.

2) Make sure any loads are defined and identified correctly.

3) If the mechanical unit is exposed to forces from the external processes, use RAPID command or system parameters to raise the supervision level.

50200, Torque error

Description

Torque calculation error due to high speed for mechanical unit arg.

Internal info code arg


- Check load data.

- Reduce speed.

50205, Data logger error:

Description

arg


Solution:

arg

50201, Orientation outside reach

Description

The error of the programmed orientation exceeds the acceptance limit.


- Adjust robtarget orientation.

- Adjust/check orientations of currently used frames: tool frame, base frame, user frame, object frame.

- It is possible (but not recommendable) to switch off the orientation supervision using the corresponding system parameter. Please see system parameters documentation for details (Topic Motion/Type

Robot).

50206, Probe warning

Description

Probe buffer is full.


50207, Add intermediate point

Description

Intermediate point not coordinated to external pos mechanical unit is necessary when changing conveyor.


Create an intermediate point then change the conveyor.

50203, Measurement node used

Description

The measurement node for joint arg is already used.


Description

Friction compensation can not be activated for joint arg.


Install the option Advanced Shape Tuning.



50209, Kinematic limitation

Description

No acceptable solution found. Residual: arg deg in orientation, arg mm in x,

arg mm in y, arg mm in z.


Insert an intermediary point. Check singularity. Increase position and orient. tolerance. Use MoveAbsJ. Check working range.

50210, Load identification fail

Description

Cannot perform load identification because configuration angle is too small.


- Increase configuration angle.

50220, No input signal

Description

No input signal to contactor relay for mechanical unit arg


Ensure that an input signal is connected and configured.

50221, Object outside limit

Description

Object on conveyor arg is outside max dist or min dist limits. Object

Dropped.


Check limits or reduce conveyor speed.

50212, Missing option

Description

General kinematics can not be used without the option 'GKIN'.


Install the option 'GKIN'.

50222, Mismatch type - MechUnit

Description

Mismatch between selected manipulator type and selected mechanical unit.


Make sure that selected manipulator corresponds to selected mechanical unit and try again.

50214, Work area config failed

Description

Possibly the defined work area is larger than max allowed area for robot arg.


Adjust the work area parameters in Robot system parameters and try again.

50224, Cannot define load

Description

It is not allowed to define a load on axis arg for mechanical unit arg or the interpolation is not stopped in a finepoint.


Change axis number, mechanical unit or change the move before to finepoint.

50215, Load identification fail

Description

Axis arg will move outside working range.


Move the axis to a position further from the working range limit.

50225, Old boot safe area lost

Description

Error in boot safe memory area.

- Area updated with new data.

- System unsynchronized.


Update all revolution counters.

50218, Path not finished

Description

Task: arg

Previous motion path was not finished before new motion was sent.

Program Ref. arg


Use StorePath when in Trap routines. Move the program pointer and start a new movement.

50226, Motor reference error

Description

Calculation time for motor references exceeds internal limits.


- Reduce load on main computer.

- Restart controller.



50227, Test signal error

Description

Invalid channel number arg.


Allowed channel numbers are 1 - 12 for test signals and 1 - 6 for data log signals.

Consequences


Probable causes

The robot communication card may be faulty.


1) Restart the system to resume operation.

2) Replace the robot communication card if faulty.

3) Check any other error log messages coinciding in time with this one for clues.


Description

Unknown test signal number arg.


Make sure that a valid test signal number is defined.


Description

Unknown mechanical unit arg.


Check spelling or configuration.

50236, Reference underrun

Description

Reference underrun in Main computer interrupt routine for Axis computer connected to connector board arg.




- Replace Axis computer board.


Description

Invalid axis number arg for mechanical unit arg.


Check mechanical unit and axis number.

50237, Reference task error

Description

Reference task queue full (Slot id = arg)




- Replace Axis computer board(s).


Description

Mechanical unit arg not active.


Activate mechanical unit before defining test signals.

50239, Optimal Em. Stop change

Description

Optimal Emergency Stop changed to Electrical brake mode because of acceleration limitation.


Limit acceleration in the program.

50234, Overflow during logging

Description

An overflow occured when logging test signals or data log signals.


- Define fewer signals.


- Reduce network load.

50240, Optimal Em. Stop change

Description

Optimal Emergency Stop changed to Electrical brake mode because of torque limitation.


Check load data.

50235, No interrupts received

Description

No interrupts received from the robot communication card within timeout.


Description

Absolute Accuracy not purchased.




Change Robot system parameter use_robot_calib to uncalib.

50242, Unsync due to CFG data

Description

- Mismatch between controller and cfg data for joint arg (calibration offset or calibration position), or

- Valid flags for calibration offset or commutation offset not true in cfg.


Update measurement system:

- Update revolution counter.

- Recalibrate joint.

- Change cfg data.

50243, No acceleration limit

Description

Acceleration limitation is not implemented for robot arg.

50248, Internal Servo Tool error

Description

Internal error for tool arg in state arg

arg arg arg


Contact ABB.

50249, Programmed force reduced

Description

Programmed tip force too high for tool arg. Requested motor torque

(Nm)= arg. Force was reduced to max motor torque.


1) Reduce programmed tip force.

2) Check force vs torque calibration in system parameters.

3) Check max motor torque in system parameters.

50244, AbsAcc calibration failed

Description

Could not perform an AbsAcc calibration.



- Check that the harddrive isn't full.

- Install more memory.

50250, Calibration force reduced

Description

Requested calibration force too high for tool arg. Requested motor torque (Nm)= arg. Force was reduced to max motor torque


1) Check calib forces in sys par.

2) Check force vs torque calibration in system parameters.

3) Check max motor torque in system parameters.


Description

Cannot set non motion execution mode when in MOTORS ON state.



50251, Tool opening failed

Description

An ordered tool axis movement of arg was detected during tool opening.


Make sure the tool opening is ready before executing next tool axis movement. Decrease the system parameter 'post sync time'.

50246, Linked motor error

Description

Large position offset between follower axis and master axis.


Start linked motor service program. Jogg the follower axis to same position as the master axis.

50247, Clear of Path failed

Description

The movement has to be stopped when the path is to be cleared.


Use StopMove before the ClearPath instruction. Move the program pointer and start a new movement.

50252, Tool opening failed

Description

An ordered tool axis movement of arg was detected during tool opening in calibration.


Make sure no movements of the tool axis are ordered during calibration.



50253, Cannot deactivate unit

Description

Deactivation of mechanical unit may not be done while in process mode.


Make sure to leave process mode before deactivating mechanical unit.

50259, Sensor max dist error

Description

Distance between sensor position and programmed position too large.

arg


- Check programmed sensor positions in robtarget.

- Check sensor speed.

- Start sync earlier or reduce waitsensor dist.

50254, Linked motor error.

Description

Too large speed for follower axis when follower axis is in jog mode.


Start linked motor service program. Reset jog mode.


Description

Linked motors can't be used without installing appropriate option.


Install the option 'Electronically linked motors'.

50260, Sensor Check dist error

Description

Distance sensor pos to programmed pos arg too large arg.



- Check sensor speed

- Increase max deviation.

50256, Sync pos warning

Description

Sensor movement outside limits. The sensor start pos should be arg than arg and found arg.


Check programmed sensor position in robtarget. Start sync earlier or change robtarget.

50261, WZone outside work area

Description

The definition of minimum limit for the World Zone arg is outside work area for: argargarg...


Change the definition of the World Zone so the limit will be inside work area or insert 9E9 to remove an axis from test by the WZone.

50257, Sync speed warning

Description

Programmed speed outside limits. The speed should be arg than arg and found arg.


- Check programmed robot speed

- Check sensor teach pos

- Check sensor nominal speed.

50258, Sensor direction error

Description

Programmed sensor pos speed arg and found sensor speed arg in opposite direction.



- Start sync earlier or reduce waitsensor dist .

50262, WZone outside work area

Description

The definition of maximum limit for the World Zone arg is outside work area for: argargarg...


Change the definition of the World Zone so the limit will be inside work area or insert 9E9 to remove an axis from test by the WZone.

50263, Duty factor warning

Description

The duty factor for the gearbox of joint arg of robot arg is too high.

Continued running without adjustment may cause damage to motor and gearbox. Contact your local ABB service support center.


Reduce the speed or increase the wait time.

50264, Saved parameters used

Description

Valid calibration data was found after system update and will be used unless a calib.cfg file is added with RobInstall or in syspar directory.




If calibration data from file should be used, add a calib.cfg file with

RobInstall or in syspar directory and make a new installation of system.

50265, Thickness out of reach

Description

Servo Tool: arg Programmed thickness arg mm is out of reach


- Adjust programmed thickness

- Check working range (min. stroke)

50266, Close request failed

Description

Not allowed to close Servo Tool:arg in reverse direction

Pre close position: arg mm

Programmed thickness: arg mm


- Adjust pre close position

- Adjust programmed thickness

50267, Open request failed

Description

Not allowed to open Servo Tool:arg in reverse direction


Check that programmed robtarget positions of the Servo Tool are larger than programmed thickness.


Description

Not allowed to calibrate Servo Tool:arg from negative position


Adjust Servo Tool position before calibration

50269, Tune value out of limit

Description

Tune value for Servo Tool: arg is out of limit. Parameter: arg


Adjust tune value

50271, Poor event accuracy

Description

Task: arg

The system is presently configured with time event supervision, and now an event could not be accurately activated.


Program Ref. arg


Decrease the programmed speed or increase the distance between the programmed positions. Turn off this check by changing the system parameters.


Description

Failed to read arg data for arg , from the configuration file.


Check the configuration file - cold start the system with correct parameters.

Check both configuration data for the current instance and any instances below in the structure.


Description

Incorrect configuration parameter arg for arg. The configuration parameter could for instance be an unknown type or a numerical value that is out of range.




Description

Failed to read or create arg with the name: arg. If the current instance exists it is read, else it is created. In other words, the instance could not be read or created.




Description

Failed to read next arg name, previous name is arg. The previous instance is ok, but the next instance cannot be read.

Check also the configuration error log for more details.




Description

Standard servo queue length (arg) out of range (min=1, max=arg).

295



Check std_servo_queue_length in the configuration file - cold start the system with correct parameters.


Description

Number of joints (arg) in dynamic group override. Allowed number is

arg.




Description

Failed to configure servo gun (arg).


Check the servo gun data in the configuration file. Cold start the system with correct parameters.


Description

Servo tool change requires option Servo Tool Change.

Without this option, installation of this mechanical unit is not allowed.



50282, Record not ready

Description

Record not ready to activate


Make sure that record is finished before activating.

Check sensor_start_signal

50283, Unknown record file name

Description

Record file name: arg is unknown.


Check file name or existence with file manager.

Record a new file

50284, Cannot activate Mechanical Unit

Description

The Mechanical Unit arg cannot be activated because it is not connected to a Rapid task.


Check that the connection between Mechanical Unit and Rapid task is done correctly in the SYS.cfg.

50285, DitherAct not possible

Description

Dithering is not possible to activate.


Verify that a joint that can be used with DitherAct is chosen.

50280, System configuration

Description

Mechanical Unit arg is defined in more than one Rapid program.



50281, Process failed

Description

Task: arg

A process in the task arg has failed. This is caused by a failure of a process in this task or a synchronized task if MultiMove is used.

arg


Check other messages occuring at the same time for the reason.

Recovery: arg

50286, Mix of coordinated frames

Description

Task: arg

More than one unit move frames, reasonarg:

1 It is not allowed to have a chain of coordinated frames.

2 It is not allowed to exchange the unit that control the frame in a cornerzone.

Program Ref. arg


1 Rearrange the units so that all units, which perform coordinated movements, are following the same unit.

2 Insert a finepoint or a not coordinated movement between the two coordinated movements.



50287, Unit out of position

Description

The robot arg is semi coordinated to Unit arg and the Unit must stand in a finepoint when the Robot is moving in the user_frame.


Use WaitSyncTask to separate the semi coordinated move from other moves, SyncMoveOn, SyncMoveResume and SyncMoveOff. After a

SyncMoveOff the Unit must also be moved (MoveL or MoveExtJ) to a finepoint to make regain possible after a stop during the semi coordinated move. Keep the program active for the Unit in the task selection panel to get a regain of the Unit at restart, the reason is that the Unit can move a little when doing motors off and on.

50292, Activation not allowed

Description

Activation of mechanical unit arg is not allowed when task is in synchronized motion mode.

Probable causes

Instruction ActUnit is used in a synchronized part of the program.


- Make sure no ActUnit instruction is used in a synchronized part of the program.

- Move the program pointer to main.

50288, Sync ID mismatch

Description

The specified id number for the move instruction has to be equal for all cooperating program tasks.

Current id number mismatch arg, arg.


Verify that the specified id numbers are equal and that all PP are synchronized before program start.

50293, Configuration error

Description

The configuration file is erroneous concerning SMB memory storage.

Probable causes

Wrong parameter set up in configuration file. Wrong type of SMBboard.


- Make sure that parameter memory_index is defined.

- Use SMB-board with memory functionality.

50289, Point type mismatch at sync

Description

The move instructions with syncId = arg, have a mix between finepoints and zonepoints.


Make sure that the move instruction in all cooperating program tasks specifies the same kind of point type, either finepoints or zonepoints.

50294, Transmission error of data

Description

Transmission of data between cabinet and SMB-memory has failed.

Probable causes

Cable, or transmission electronics failed. Electrical interference high.


- Restart try once more.

- Check cables.

- Check SMB-board.

- Check drive module.

50290, Service unavailable

Description

Unable to obtain correct license.


Please check the license settings.

50291, Deactivation not allowed

Description

Deactivation of mechanical unit arg is not allowed when task is in synchronized motion mode.

Probable causes

Instruction DeactUnit is used in a synchronized part of the program.


- Make sure no DeactUnit instruction is used in a synchronized part of the program.

- Move the program pointer to main.

50295, Manipulator data missing

Description

Data in SMB- and cabinet memory missing for mechanical unit arg.

Probable causes

Configuration file missing. New SMB-board together with new cabinet.


- Load new configuration files.

50296, SMB memory data difference

Description

Data in SMB memory is not same as in cabinet for mechanical unit arg.



Probable causes

Not the same data or serial number in SMB memory and cabinet.

Manipulator (SMB module) or cabinet exchanged or configuration parameters changed.


Check status via teach pendant and check if right configuration data

(serial number) loaded in cabinet. Check that serial number belongs to the manipulator connected to the cabinet. If not, replace configuration files or manually transfer data from SMB memory to cabinet if cabinet has been exchanged.

If Serial Measurement Board replaced with board from another manipulator (serial numbers not the same), clear first SMB memory via teach pendant and then transfer data from cabinet to SMB.


50301, All SMB data missing

Description

All data is missing in SMB-memory at board arg, link arg, drive module arg.

Probable causes

An error in SMB-memory or communication has occurred. The data has been cleared.


If proper data exists in cabinet - transfer the data to SMB-memory. If still problem - check communication cable to SMB-board. Replace

SMB-board.

50297, Memory updated in SMB

Description

Data for mechanical unit arg is moved from cabinet to SMB-memory.

Probable causes


50298, Memory updated in cabinet

Description

Data for mechanical unit arg is moved from SMB-memory to cabinet.

Probable causes


50302, Sensor data missing

Description

No serial number is defined for mechanical unit arg in SMB-memory.

Probable causes

The SMB-memory has been cleared or new SMB-board has been installed.


If proper data exists in cabinet - transfer the data to SMB-memory.

50299, Speed control warning

Description

Speed for Unit arg is reduced due to limiting Unit arg.

Task: arg Intruction line: arg

Probable causes

Programmed speed too high on this Unit or movement too long on limiting Unit


Change path or programmed speed .

Set speed control off

50303, Cabinet data missing

Description

No serial number is defined for mechanical unit arg in cabinet.

Probable causes

The cabinet memory has been cleared or new cabinet has been installed..


If proper data exists in SMB-memory - transfer the data to cabinet memory.

50300, SMB memory not used

Description

SMB-memory is not used for this mechanical unit.

Probable causes

Additional axes can't and should not use the SMB-memory.

50304, Transfer of data not allowed

Description

The SMB-memory for mechanical unit arg has another serial number, than used in the cabinet.

Probable causes

A SMB-board from another robot has been installed in the used robot.


Clear first the data in SMB-memory via calibration/SMB-memory/ advanced/. Then repeat the transfer command once again.



50305, Old SMB board used

Description

Old SMB board used without data memory.

Probable causes


Replace board with a new with data memory or set parameter "Use old

SMB" in configuration MOTION/ROBOT.

50311, Cannot activate Mechanical Unit in task

Description

The Mechanical Unit arg cannot be activated in specified task.


Check the connection between Mechanical Unit and Rapid task in the

SYS.cfg.

50306, Load identification error

Description

Cannot perfom load identification because configuration angle makes inertia matrix singular.


- Move axis 6 on the robot about 30 degrees in any direction.

50312, Mechanical Unit already active in other task

Description

Cannot activate Mechanical Unit arg, since it is already active in another Rapid task.

50307, Extended working range

Description

The option Extended working range has been installed.

Make sure that the mechanical stop has been removed.

50313, Independet move reset failed

Description

Independent reset movement failed for arg, a synchronized movement

(MoveL/MoveJ) of the servo tool occured during the the independent reset movement.


Make sure the synchronized speed of the servo tool is zero during execution of independent reset movements.

50308, In Position timeout

Description

Condition for finepoint not fulfilled within arg seconds.


Check tuning of additional axes, In Position Conditions (In Position

Range, Zero Speed) and check if disturbance of resolver cables.

50314, Independent move outside reach

Description

Programmed independent move position for argis outside reach.

Programmed position = arg mm.


Adjust independent move position.

Check working range of the servo tool.

50309, AbsAcc error

Description

Data moved from SMB-memory to cabinet. AbsAcc data not valid in

SMB-memory. AbsAcc cleared in cabinet for mechanical unit arg.


Load new AbsAcc data if data available.

50310, Independent joint not active

Description

Mechanical unit arg with independent joint is not active.


Activate the mechanical unit before executing the independent joint instruction.

50315, Corner path failure

Description

Task: arg

Interpolation and process stopped before the corner path due to some of the following reasons:

- Time delay.

- Closely programmed points.

- System requires high CPU-load.

arg


- Reduce the number of instructions between consecutive move instructions.

- Reduce speed, use wider spaced points, use /CONC option.

- Increase ipol_prefetch_time.

Recovery: arg



50316, Absolute accuracy not activated

Description

Absolute accuracy function not activated.

Consequences

Robot positioning will not be absolute accurate.


Make sure absacc.cfg is loaded into controller memory and switch

AbsAcc on. Verfiy status in jogging window.

Probable causes

The mechanical unit is connected to Drive Module arg which is disconnected.


1) Reconnect the Drive Module. 2) Retry to activate the Mechanical

Unit.

50317, Disconnecting the Drive Module not allowed

Description

An attempt was made to disconnect drive module arg, which is not allowed.

Consequences

The system goes to state Motors OFF, and then disconnects the Drive

Module.

Probable causes

Disconnecting drive modules is only allowed in the Motors OFF state.


Make sure that the system is in Motors OFF state before disconnecting the Drive Module.

50320, Drive Module has been disconnected

Description

Drive Module arg has been disconnected.

Consequences

No mechanical units connected to the drive module may be operated.

50321, Drive Module has been reconnected

Description

Drive Module arg has been reconnected after being disconnected.

Consequences

All mechanical units connected to drive module arg may be operated.

50318, Reconnecting the Drive Module not allowed

Description

Drive Module should not be reconnected since the system is not in the state Motors OFF.

Consequences

An attempt was made to reconnect drive module arg, which is not allowed.

Probable causes

Reconnecting drive modules is only allowed in the Motors OFF status.


Make sure that the system is in Motors OFF state before reconnecting the Drive Module.

50322, Mechanical Unit not connected to motion task

Description

Cannot activate Mechanical Unit arg, since it is not connected to any motion task.


Check the connection between Mechanical Unit and Rapid task in the

SYS.cfg.

50323, Failed to read force sensor

Description

Failed to return calibrated force sensor reading.

Probable causes

Force control system not calibrated.


Use the instruction FCCalib before using this instruction.

50319, Cannot activate Mechanical Unit

Description

An attempt was made to activate mechanical unit arg, which failed.

Consequences

The mechanical unit remains deactivated.

50324, Force control calibration failed

Description

Failed to calibrate the force control system.

Probable causes

The system is not in position control.


Make sure the robot is in position control mode before using the

FCCalib instruction.



50325, Failed to activate force control

Description

Activation of force control failed.

Probable causes

The system is either not calibrated or we are already in force control.

Another reason for this could be incorrect arguments.


Only use the FCAct or FCPress1LStart instruction when the force control system is calibrated and we are in position control. Check all arguments to the activation instruction.

50330, Parameter error in FCRefSprTorque

Description

Error in parameter MaxTorque in instruction FCRefSprTorque.


Change the parameter MaxTorque in instruction FCRefSprTorque to a value larger than zero.

50331, Parameter error in FCRefForce

Description

Error in parameter Amp in instruction FCRefForce.


Change the parameter Amp in instruction FCRefForce to a value larger than zero.

50326, Failed to deactivate force control

Description

Failed to return to position control.

Probable causes

Can not set position control if the robot is moving due to external forces or ordered references.


Stop any active references and remove any external forces and try again.

50332, Parameter error in FCRefTorque

Description

Error in parameter Amp in instruction FCRefTorque.


Change the parameter Amp in instruction FCRefTorque to a value larger than zero.

50327, Failed to start references

Description

Failed to start the user specified references

Probable causes

Only allowed to start references when in force control.


Must activate force control before trying to start references.

50333, Error FCRefLine, FCRefRot or

FCRefCircle

Description

The parameter Distance in instruction FCRefLine or instruction

FCRefRot and the paraneters Radius and Speed in instruction

FCRefCircle have to be larger than zero.


Change the parameters above according to the manual.

50328, Parameter error in FCRefSprForce or

FCRefSprTorque

Description

Error in parameter Stiffness in instruction FCRefSprForce or

FCRefSprTorque.


Change the parameter Stiffness in instruction FCRefSprForce or

FCRefSprTorque to a value larger than zero.

50334, Parameter error in FCRefLine

Description

Not allowed parameter value used in function FCRefLine.

Probable causes

Error in parameter values of function FCRefLine.


Modify the parameter values in function FCRefLine.

50329, Parameter error in FCRefSprForce

Description

Error in parameter MaxForce in instruction FCRefSprForce.


Change the parameter MaxForce in instruction FCRefSprForce to a value larger than zero.

50335, Parameter error in FCRefSpiral

Description

Not allowed parameter value used in function FCRefSpiral.

Probable causes

Error in parameter values of function FCRefSpiral.




Modify the parameter values in function FCRefSpiral.

50336, Parameter error in FCGetProcessData

Description

Failed to retrieve process information.

Probable causes

Using the optional parameter DataAtTrigTime in instruction

FCGetProcessData. If no trig has occured this error is reported.


Remove the optional parameter.

50342, Error in force control sphere definition

Description

An error in the parameter Sphere in either FCCondPos or FCSupvPos.


Change the parameter Sphere in either FCCondPos or FCSupvPos.

50343, Error in force control cone definition

Description

An error in the parameters for either FCCondOrient or FCSupvOrient.


Change the parameters in either FCCondOrient or FCSupvOrient.

50337, Force sensor not setup

Description

Error in the force sensor parameters.


Check the force sensor configuration parameters.

50338, Parameter error in FCCondAdvanced

Description

Error in parameter LogicCond in instruction FCCondAdvanced.


Modify the parameter LogicCond in instruction FCCondAdvanced.

50339, Parameter error in FCCondTime

Description

Error in parameter Time in instruction FCCondTime.


Change the parameter Time in instruction FCCondTime to a value larger than zero.

50344, Joints outside limits in force control

Description

One or more joints are outside their working range in force control.


Modify the program to avoid the physical joint limits.

50345, Force control supervision error

Description

The user specified supervision has trigged. The type is arg.

Types:

1: TCP position

2: Tool Orientation

3: TCP speed

4: Reorientation speed

5: Force

6: Torque

7: Teach TCP Speed

8: Teach Reorientation Speed

Consequences

The robot will stop.


Modify the supervision or the program.

50340, Error in force control box definition

Description

An error in the parameter Box in either FCCondPos or FCSupvPos.


Change the parameter Box in either FCCondPos or FCSupvPos.

50341, Error in force control cylinder definition

Description

An error in the parameter Cylinder in either FCCondPos or

FCSupvPos.


Change the parameter Cylinder in either FCCondPos or FCSupvPos.

50346, Motor temperature error

Description

Motor temperature for joint arg is too high.

Consequences

It is not possible to continue until the motor has cooled down.



50347, Progam pointer moved in Force Control mode

Description

Program pointer has been moved in Force Control mode.

Consequences

Robot is stopped and the mode is changed from Force Control mode to normal mode.

If Force Contol mode is desired the program pointer must be moved to the FCAct instruction.

50352, Number of move instruction mismatch

Description

Using the path recorder within syncronised motion requires:

That Tool offset must be present for all or none cooperating program tasks.

That all cooperating program tasks move backwards/forwards the same number of move instructions.


Verify that the all tasks or none of the tasks use the optional argument

Tool Offset.

Verify that the pathrec identifier moving towards are at the same position in all tasks within the syncronised block.


Description

Definition of a test signal failed for arg, axis arg on channel arg.

Probable causes

The Mechanical Unit is not active.

The test signal number does not correspond to an actual test signal.

The channel number is too high.

50349, Synchronization ID Warning

Description

Two consecutive synchronized move instructions in arg have the same syncronization ID value arg.

Consequences

If the ID value is repeated for more than one move instruction it can be very difficult to keep track of which move instructions are synchronized. This can, for example, cause problems when modifying positions.


Change the synchronized move instruction arg in arg so that it has a unique synchronization ID value.

50353, Failed to read data from encoder card

Description

The system has failed to read data from one encoder card.

Consequences

The tracking accuracy during acceleration and deceleration might be reduced.

Probable causes

Wrong unit name has probably been specified in the process parameter for

arg


1) Check that the correct unit name is specified in the process parameter

eio unit name for arg

50350, Software Equalizing Not Allowed

Description

It is not possible to run Software Equalizing since Independent Move is active.


Make sure independent move is not active when executing a Software

Equalizing servo spot.

50354, Ordered force reference is too large

Description

The ordered force reference is larger than the configured maximum value.

Consequences

The ordered force reference has been reduced to the configured value.


To allow a larger reference force the system parameters need to be updated. Note that there is an absolute limit of force reference size that depends on the robot type.

50351, Independent Move not allowed

Description

It is not possible to execute an Independent Move when Software

Equalizing is active.


Make sure Software Equalizing is off when executing an Independent

Gun Move.

50355, Ordered torque reference is too large

Description

The ordered torque reference is larger than the configured maximum value.

Consequences

The ordered torque has been reduced to the configured maximum value.




To allow a larger reference torque the system parameters need to be updated.

50356, Ordered MaxForce is too large

Description

The parameter MaxForce in instruction FCRefSprForce is larger than the configured maximum value.

Consequences

The parameter MaxForce has been reduced to the configured maximum value.


To allow a larger value the system parameters need to be updated.

50362, Brake release time out

Description

Joint arg was not in position after max time for brake release.


Try once more. Check cables. Check hardware. Check tuning if error on additional axis.

50363, SyncMoveOn failed

Description

Starting synchronized movements failed due to an internal error.

Consequences

It is not possible to restart the programs from the current position.


Move the program pointers and try again.

50357, Ordered MaxTorque is too large

Description

The parameter MaxTorque in instruction FCRefSprTorque is larger than the configured maximum value.

Consequences

The parameter MaxTorque has been reduced to the configured maximum value.


To allow a larger value the system parameters need to be updated.

50364, Axis in current vector mode

Description

Warning: Joint arg is configed in arg data as a current vector axis.

Drive system will be disconnected for this axis during normal operation.


Run service program to activate the current vector.

Set configuration data for the DRIVE SYSTEM parameter current_vector_on to FALSE, for normal operation..

50358, Close to singularity when in force control

Description

Close to singularity when in force control mode for robot arg.


Modify path away from the singularity or change to joint interpolation.

50359, Path Recorder on StorePath level not allowed

Description

The Path Recorder can only be used on base path level. The Path

Recorder has been stopped.


Stop Path Recorder before StorePath, restart it after RestoPath.

50361, Brake release error

Description

Too large position error of joint arg after brake release.


Try once more. Check cables. Check hardware. Check tuning if error on additional axis.

50365, Cyclic Brake Check Warning

Description

Cyclic Brake Check has failed

Consequences

Cyclic Brake Check has detected that robot arg may have reduced brake perfomance on axis arg.


Repeat the test to verify the result.


Description

An error has occurred in the reference calculation. Internal status arg.

Consequences

The controller goes to Motors Off


Check the error logs for previous errors that could be causing this problem.

Try to restart the program possibly after moving the program pointer.




50367, Sensor Sync machine stop

Description

Sensor Sync device arg has set machine stop signal arg.


Do not restart robot before machine is open. Sensor sync is disabled.

50368, Too Short distance between equidistant events

Description

The events are too close together. End of internal resources (events).

Task: arg

Program Ref. arg


Increase the distance between equidistant events or use intermediate positions to decrease segment length.


Lower the programmed speed or modify the configuration parameters.

50372, Contact force too high

Description

The contact force is too high during the recover phase.

Probable causes

The programmed path in the recover function causes too high contact forces.


Check and modify the recover function or allow higher contact force.

50369, Calibration using stored offset failed

Description

Failed to calibrate the sensor using stored offset.

Consequences

The force control system is not calibrated. It is not possible to activate force control.

Probable causes

Calibration using stored offset is only possible if a normal calibration has been performed earlier.

50373, Too high Event Preset Time

Description

The configured Event Preset Time is too high. The maximum value is

arg.

Consequences

The Event Preset Time is reduced to the maximum value.

Probable causes

This error can occur for robots with a low Dynamic Resolution and a high Event Preset Time. The reason is a computer memory limitation.


Reduce the Event Preset Time in the configuration parameters to a value no higher than arg.

50370, Transfer of data to SMB memory failed

Description

Transfer of data from cabinet to SMB memory not allowed or interrupted for mechanical unit arg due to disconnect of SMB.

Probable causes

SMB was disconnected before or during calibration or manual move of data to SMB memory.


Retry to calibrate or manually move data from cabinet to SMB memory when SMB is reconnected.

50375, Dynamic load too high

Description

Required torque for robot arg axis arg too high.


If weaving one of these actions may help:

- Reduce weave frequency or weave amplitude for this movement.

- Reduce process speed.

- Increase zone size if small zones are used.

- Increase distance between programmed points if they are close.

If Conveyor Tracking: Reduce conveyor speed.

50371, The programmed speed is too high

Description

The speed change functionality is only allowed for low programmed speed.

Probable causes

The programmed speed is too high.

50376, Geometric interpolation failed.

Description

Task. arg

Failed to interpolate the desired geometry.

Program Ref. arg

(Internal code: arg)


Increase the zone size, move the programmed point, change tool orientation or change interpolation method.



50377, Only allowed in position control

Description

The instruction is only allowed when the robot is in position control mode.

Probable causes

The error depends on calling an instruction that is only allowed to be used in position control while in force control mode.


Call the instruction only when the robot is in position control mode.


Increase the programmed speed.

Check also the other synchronized tasks in a multimove application.

50382, Weave pattern error

Description

Calculation of weave pattern has failed due to an internal error.


Try to restart.

50378, Error in FCSetMaxForceChangeTune

Description

Incorrect value of the parameter ForceChange in instruction

FCSetMaxForceChangeTune.

Consequences

The program will stop.

Probable causes

The parameter must be set larger than zero and less than the configured value.


Change the parameter value.

50383, Cartesian Soft Servo configuration error

Description

Some configuration parameter for Cartesian Soft Servo is not valid.

Consequences

The system will not start.

Probable causes

Some configuration parameter has been set to a value that is not allowed.


Verify that any modifed parameter are within allowed limits.

50379, Active mechanical units have changed

Description

When calling RestoPath all mechanical units have to be in the same active state as when StorePath was called.


Make sure that all mechanical units that were active when calling

StorePath still are and that no other mechanical unit is active when calling RestoPath.

50384, Cartesian Soft Servo quaternions invalid

Description

The quaternions of the tool, workobject or the argument RefOrient in the CSSAct instruction are invalid.

Consequences

Cartesian Soft Servo will not activate.


Check the quaternions of the tool, workobject or the argument

RefOrient in the CSSAct instruction.

50380, Checksum error

Description

Data in SMB memory for mechanical unit arg has erroneous checksum.

Probable causes

New SMB-board. System shut down before data save finished.


- Load new configuration files.

50385, Cartesian Soft Servo activation failed

Description

The instruction CSSAct failed.

Probable causes

Cartesian Soft Servo already active.


Cartesian Soft Servo needs to be deativated before it can be activated.

50381, Speed too low.

Description

Task. arg

The speed is too low (numerical resolution).

Program Ref. arg

50386, Cartesian Soft Servo offset activation failed

Description

The instruction CSSForceOffsetAct failed.



Consequences

Force offset was not activated.

Probable causes

CSSForceOffsetAct instruction is only allowed when Cartesian Soft

Servo is active.


Activate Cartesian Soft Servo with the instruction CSSAct before using the instruction CSSForceOffsetAct .

50387, Cartesian Soft Servo close to unstable

Description

Cartesian Soft Servo is close to unstable.

Consequences

The robot is halted as a security measure.

Probable causes

The system damping is too low.


Increase the value of Damping in the CSSAct instruction or if that does not help increase the value of the configuration parameter Damping

Stability Limit.

50388, Cartesian Soft Servo position supervision error

Description

The user defined position supervision in Cartesian Soft Servo mode trigged.

Consequences

The robot halts.

Probable causes

The position error is larger than the allowed range specified in the configuration.


Increase the allowed position error in the configuration or modify the program.

50390, Cartesian Soft Servo speed supervision

Description

The user defined speed supervision in Cartesian Soft Servo mode trigged.

Consequences

The robot halts.

Probable causes

The speed error is larger than the allowed range specified in the configuration.


Increase the allowed speed error in the configuration or modify the program.

50391, Cartesian Soft Servo movement not allowed

Description

Jogging or a programmed movement has been detected.

Consequences

The ordered movement is ignored.


Movement during Cartesian Soft Servo is only allowed if the switch

AllowMove has been used in the CSSAct instruction.

50392, SafeMove communication error

Description

Communication with SafeMove controller on drive module arg has failed.

Consequences

Brake tests can not be done.


Check if SafeMove hardware is connected.

50389, Cartesian Soft Servo singularity

Description

The robot is too close to singularity which effects the Cartesian Soft

Servo behaviour.

Consequences

The robot behaviour will be different from specified.


Modify the program to avoid the singularity.

50393, Force offset applied in non-soft direction

Description

The force-offset direction in CSSForceOffsetAct is not the same as the soft direction specified by CSSAct.

Consequences

The robot will not become easier to push in the soft direction. There can also be position deviations from the programmed path in the nonsoft directions.


Make sure the direction given in CSSForceOffsetAct is compatible with the direction given in CSSAct.



50394, Unit out of position

Description

The Robot arg is semi coordinated to Unit arg and the Unit must stand in a fine point when the Robot is moving in the user frame.

Consequences

The restart will be interrupted.


Use WaitSyncTask to separate the semi coordinated move from other moves, SyncMoveOn, SyncMoveResume and SyncMoveOff. After a

SyncMoveOff the Unit must also be moved (MoveL or MoveExtJ) to a finepoint to make regain possible after a stop during the semi coordinated move. If the programmed position of the Unit is moved by modpos the Robot program must be reset by moving the PP to be able to restart the program. Step also the unit to the new position to make stepping of the robot possible.


Reduce programmed speed, increase corner zones, or decrease the distance between the programmed path and the surface.

50398, AbsAcc circle begins with a frame change

Description

Task: arg

When having the AbsAcc option, MoveC instructions that are coordinated to another robot must use the same tool and work object as the previous move instruction.

Consequences



Change the move instruction before arg so that they both use the same frames. Alternatively, add a (redundant) MoveL to the start point of the circle arc, using the same frames as the MoveC instruction.

50395, Too long programmed move

Description

Task: arg

This move is too long for the programmed speed. The numerical resolution in the path planning is not enough.

Program Ref. arg

Consequences

The speed will be increased i.e. higher than the programmed speed.


Insert intermediate points or increase the speed.

50399, AbsAcc circle is first movement instruction

Description

Task: arg

When having the AbsAcc option, MoveC cannot be the first movement instruction.

Consequences



Add a movement instruction before arg, using the same tool and frames.

50396, Default FC force supervision error

Description

The default force supervision has trigged because the programmed or measured external forces are larger than the safety limit for the robot type.

Consequences



Modify the program to decrease the total external force acting on the robot.

50400, Manipulator configuration error

Description

The parameter disconnect_link_at_deactivate for

MEASUREMENT_CHANNEL was inconsistent for measurement_link arg. All channels on the same link have to have the same setting for this parameter.



50397, Path frame rotation speed error

Description

The rotation speed of the path frame is too high when using FC

Machining with ForceFrameRef set to FC_REFFRAME_PATH.

Consequences


50401, Startup synchronization failed

Description

The system relay 'arg' is defined but no response was received during the startup(waited for arg minutes).


Make sure that the in_signal of the relay is configured and connected and startup all synchronized systems simultaneously.



50402, Correction is not ended in a finepoint

Description

Task: arg

The last move instruction with correction specified has to be a finepoint.

Program Ref. arg


Change the zone parameter to fine.

50403, AW board not connected

Description

During startup, no communication was established with unit <arg> on bus <arg>.

Consequences

It is not possible to access the unit or signals on the unit, since it is currently not communicating with the controller.

Probable causes

The unit is either not connected to the system, or it is connected, but has been assigned the wrong address.


1. Make sure all unit addresses match the configuration.

2. Make sure all addresses are unique, and not used by more than one unit.

3. Change the address and/or connect the missing unit.

4. If you changed the address, the power supply to the unit must be cycled (switched OFF and then back ON), to make sure the address has been changed.

Consequences

The task execution will stop.


Remove movement coordination while doing the Wrist Interpolation.

50406, Wrist Interpolation point not on circle plane

Description

Task: arg

Program Ref. arg

The target arg is not on the circle plane. The deviation is arg mm.

p1 = starting point p2 = circle point p3 = end point

Consequences

For a cutting process, the cut hole will not be circular.


If a circular arc is intended, then change the corresponding target so that it is on the circle plane.

50407, Wrist axis locked

Description

Task: arg

Program Ref. arg

Cannot do Wrist Interpolation using arg because axis arg is locked.

Consequences



Change to another wrist axis combination that does not involve the locked axis. Note that the robot must have at least two movable wrist axes to do Wrist Interpolation.

50404, Additional axis movement during Wrist

Interpolation

Description

Task: arg

Program Ref. arg

An additional axis is programmed to move during Wrist Interpolation.

Consequences



Make sure that no additional axis is programmed to move while doing

Wrist Interpolation.

50405, Coordinated movement during Wrist

Interpolation

Description

Task: arg

Program Ref. arg

Attempt to do Wrist Interpolation against a moving frame.

50408, Wrist joint limit

Description

Task: arg

Program Ref. arg

Cannot do Wrist Interpolation because robot axis arg will violate a joint limit.

Consequences



Choose another robot configuration or another wrist axis combination.



50409, Wrist Interpolation not possible

Description

Task: arg

Program Ref. arg

The programmed Wrist Interpolation is not kinematically possible using arg.

Consequences



Choose another robot configuration or another wrist axis combination.

Possible wrist axis combinations are: Wrist45, Wrist46, and Wrist56.

50410, Collinear targets in wrong order

Description

Task: arg

Program Ref. arg

The programmed targets are collinear, but the end point is between the start point and the circle point.

Consequences



If a straight line is intended, then let the circle point and the end point swap places with each other.

50411, Maximum allowed programmed TCP load exceeded

Description

The currently defined TCP load for robot arg exceeds the maximum allowed load for the robot model.

Consequences


Probable causes

The combination of the current tool load and payload exceeds the maximum load allowed for the robot model.


Make sure that the total TCP load is inside the load diagram for the robot.

50412, Error in speed change tuning instruction

Description

The speed change tuning instruction resulted in an error.

Consequences


Probable causes

The speed change tuning instruction was not allowed, or the parameters given were invalid.


Check the values for the parameter and tuning type, and make sure the correct force control option is installed and configured correctly.

50413, Bleeder resistor overload error

Description

In drive module arg, the bleeder resistor connected to the rectifier unit at drive unit position arg was overloaded.

Consequences

No operation will be possible until the bleeder resistor has cooled down. The system goes to Motors Off state.

Probable causes


2) Bleeder resistor has wrong resistance.






50414, Bleeder resistor overload warning

Description

In drive module arg, the bleeder resistor connected to the rectifier unit at drive unit position arg is close to overload.

Consequences


Probable causes


2) Bleeder resistor has wrong resistance.








50415, Motor temperature error

Description

Motor temperature for joint arg is too high.

Consequences

It is not possible to continue until the motor has cooled down. The system goes to Motors Off state.

Probable causes

The user program may contain too much hard acceleration and deceleration of the joint. Gravity torque or external forces for the joint can also be too high.


Rewrite the user program to reduce the motor utilization.

50416, Motor temperature warning

Description

The motor temperature for joint arg is close to maximum value.

Consequences


Probable causes

The user program may contain too much hard acceleration and hard deceleration of the joint. The gravity torque or external forces for the joint can also be too high.


Rewrite the user program to reduce the motor utilization.

50417, Drive unit overload error

Description

The drive unit for joint arg has reached a too high temperature level.


Consequences

No operation will be possible until the drive has cooled down. The system goes to Motors Off state.

Probable causes


2) Short circuit in the manipulator using long motor cables.




3) Check for short circuit in the motor cable or in the motor.

4) Check for other hardware eventlogs.

50418, Drive unit overload warning

Description

The drive unit for joint arg, connected to drive module arg with the drive unit at unit position arg and node arg is approaching a too high temperature level.

Consequences

It is possible to continue but margin to max temperature is too low for long term operation.

Probable causes


2) Short circuit in the manipulator using long motor cables.




3) Check for short circuit in the motor cable or in the motor.

4) Check for other hardware eventlogs.

50419, Common base_frame error

Description

Task: arg

The base_frame is moved by another task than the robot and could not be solved, reasonarg:

1 SingArea\Wrist not supported with MoveC.

2 The base_frame must be moved by first synchronized motion_group.

3 Only one common base_frame can be handled.

4 Absacc not supported with MoveC.

5 The common base_frame can only be solved in synchronized move.

Program Ref. arg


1 Use SingArea\Off. The CirPathMode can also be used.

2,3 Check SYS.cfg and MOC.cfg.

4 Use MoveL or remove absacc.

5 Use MoveAbsJ.

50420, IndCnv Mechanical Unit Error

Description

The mechanical unit arg is not correctly configured for IndCnv functionality.

Consequences

Program execution is stopped.

Probable causes

The mechanical unit arg consists of more than one single.

The single connected to arg is not of type FREE_ROT.

The single connected to arg is not defined as an Indexing Move single.




Make sure mechanical unit arg consists of only one single.

Make sure configuration parameter Motion/Single Type/Mechanics is of type FREE_ROT.

Make sure configuration parameter Motion/Single Type/Indexing

Move is TRUE.

50421, IndCnv Tracking Single Error

Description

The single arg is not configured as an Indexing Move single

Consequences



Make sure configuration parameter Process/Can Interface/Single To

Track refers to a single with Motion/Single Type/Indexing Move set to

TRUE.

50422, IndCnv and Independent joint error

Description

Independent joint instructions are not allowed when single arg is in indexing mode.

Consequences



Execute the RAPID instruction IndCnvReset before using the axis as an independent joint.

50425, Friction FFW parameter is not On

Description

Tuning friction parameters requires Friction FFW On to be set to True.

Consequences

Friction tuning for joint arg will have no effect.


Set parameter Friction FFW On to True for joint arg in the type arg that belongs to the topic Motion.

50426, Out of interpolation objects

Description

The maximum number of available interpolation objects has been reached. This can occur if the dynamic performance is set to a very low value e.g. by use of the AccSet command.

Consequences

The program execution is stopped and the system goes to motors off.


Increase the number of objects by adding 'extended_dec_dist 1' in cfg instance MOTION_PLANNER.

6,

Description

50423, IndCnv Time before indexing move too low

Description

The time between trig signal and start of indexing movement is configured too low.

Consequences

The program execution is stopped.


Increase system parameter "Motion/Single Type/Time before indexing move" to at least arg (ms).

Remove or decrease robot acceleration limitations if possible.

Please consult the Conveyor Tracking application manual for further actions.

50424, IndCnv Robot type not supported

Description

The IndCnv functionality does not support the installed robot type.

Consequences

The program execution is stopped.

71001, Duplicated address

Description

The I/O configuration is invalid.

The same addresses have been given for I/O unit <arg> and I/O unit

<arg>.

I/O units connected to the same I/O bus must have unique addresses.

This I/O unit has been rejected.


1. Check that addresses are correct.

2. Check that the I/O units are connected to the correct I/O bus.

71002, Unit type undefined

Description

The I/O configuration for I/O unit <arg> is invalid.

Consequences

This unit type has been rejected, and no functions depending on this unit type will work.

Probable causes

The unit type <arg> is unknown. All I/O units must refer to an existing, defined unit type.




1. Make sure the unit type is defined.

2. Make sure the unit type is correctly spelt.

71003, I/O unit undefined

Description

The I/O configuration for I/O signal <arg> is invalid.

Consequences

This I/O signal has been rejected, and no functions depending on it will work.

Probable causes

The I/O unit <arg> is unknown. All I/O signals must refer to an existing/defined I/O unit.


1. Make sure the I/O unit is defined.

2. Make sure the I/O unit name is correctly spelt.

71005, Invalid filter time

Description


The passive filter time should either be 0 ms or in the range [arg, arg] ms.

This I/O signal has been rejected.


Correct the passive filter time for the I/O signal.

71008, Physical values out of range

Description


The physical minimum value must be less than the physical maximum value.



Correct the physical values for the I/O signal so that the minimum value becomes less than the maximum value.

71017, Cross connection without actor I/O signal

Description


The parameter <Actor arg> of one of the cross connections have been omitted.

Rules:

1. All cross connections must specify at least one actor signal, i.e. parameter <Actor I/O signal 1> must always be specified.

2. For each operator specified an actor I/O signal must follow, e.g. if parameter <Operator 2> is specified then parameter <Actor 3> must also be specified.

This cross connection has been rejected.


Correct the cross connection so the required actor I/O signals are specified.

71006, Invalid filter time

Description


The active filter time should either be 0 ms or in the range [arg, arg] ms.



Correct the active filter time for the I/O signal.

71007, Logical values out of range

Description


The logical minimum value must be less than the logical maximum value.



Correct the logical values for the I/O signal so that the minimum value becomes less than the maximum value.

71019, I/O signal undefined

Description

The I/O configuration of a cross connection is invalid.

Consequences

The cross connection has been rejected, and no functions depending on it will work.

Probable causes

The parameter <Actor arg> of one of the cross connections contains a reference to an undefined I/O signal <arg>.


1. Make sure the I/O signal is defined.

2. Make sure the I/O signal name is correctly spelt.

71020, Cross connection without resultant I/O signal

Description


The parameter <Resultant I/O signal> of one of the cross connections have been omitted.

All cross connections must specify a resultant I/O signal.





Correct the cross connection so that there are one resultant I/O signal per cross connection.

71021, Duplicated cross connection resultants

Description


Multiple cross connections have the same resultant I/O signal <arg>.

Having more than one cross connection that result in the setting of the same signal may cause unpredictable behaviours, as you cannot control their order of evaluation.

The complete cross connection configuration has been rejected.


Make sure that the I/O signal is not specified as the resultant of several cross connections.

71037, Closed chain in cross connection

Description


The I/O signal <arg> is part of a cross connection chain that is closed

(i.e. forms a circular dependence that cannot be evaluated).



Correct the configuration for the cross connections where the I/O signal above is part.

71038, Cross connection max depth exceeded

Description


The I/O signal <arg> is part of a cross connection chain that is too deep.

The maximum depth of a cross connection chain is <arg>.



Make the cross connection less deep.

71049, Analog I/O signal inverted

Description


Analog I/O signals must not be inverted.

Only digital and group I/O signals can be inverted.



Remove the invert for the I/O signal (or change the signal type).

71050, Cross connection with non-digital actor

I/O signal

Description


The parameter <Actor arg> of one of the cross connections refer to a

I/O signal <arg>, that is not digital.

Only digital I/O signals can be cross connected.



Remove the non-digital I/O signal from the cross connection.

71052, Max number of cross connections exceeded

Description


The maximum number of cross connections, arg ,in the I/O system has been exceeded.

Not all the cross connections have been accepted.


Modify the configuration of the I/O system (by reducing the number of cross connections) so that the maximum limit is not exceeded.

71045, Invalid filter specification

Description


No filter times can be specified for this type of I/O signal.



Set filter time to 0 or remove the statement.

71054, Invalid signal type

Description


The specified signal type <arg> is invalid/unknown.

Valid signal types are:

- DI (Digital input)

- DO (Digital output)

- AI (Analog input)

- AO (Analog output)

- GI (Group input)

- GO (Group output)



Correct the signal type of the I/O signal.



71058, Lost communication with I/O unit

Description

The previously working communication with I/O unit <arg> on I/O bus <arg> has been lost.

Consequences

It is not possible to access the I/O unit itself or I/O signals on the I/O unit since it is currently not communicating with the controller. The system will go to state SYS FAIL, if the I/O unit has been assigned

Unit Trustlevel Required (0) in the configuration.

Probable causes

The I/O unit may have been disconnected from the system.


1. Make sure the I/O unit has been correctly installed.

2. Make sure the cabling to the I/O unit is correctly connected.

71078, Communication error from rtp1

Description

The response from the device has an invalid frame sequence.


Check for noise on the serial line.

71080, Max number of unit types exceeded

Description


The maximum number, arg, of unit types in the I/O system has been exceeded.


Modify the configuration of the I/O system (by reducing the number of unit types) so that the maximum limit is not exceeded.

71061, Communication failure on I/O bus

Description

A communication failure on I/O bus <arg> has been detected.


1. Check other messages for fieldbus specific error.

2. If no I/O units are configured to I/O bus, configure I/O units or remove bus configuration.


Description

Not possible to deliver the received message.


Check the communication flow.

71081, Max number of physical I/O signals exceeded

Description


The maximum number, arg, of physical I/O signals (bit-mappings) in the I/O system has been exceeded.


Modify the configuration of the I/O system (by reducing the number of physical I/O signals) so that the maximum limit is not exceeded.

71072, Cannot read stored signal value

Description

Cannot read the stored signal value for I/O signal <arg> as it is not stored.


Change the configuration of the I/O signal by setting the store attribute.


Description

No response from the serial line.


Check the device or connection.

71082, Max number of user I/O signals exceeded

Description


The maximum number, arg, of user I/O signals in the I/O system has been exceeded.


Modify the configuration of the I/O system (by reducing the number of

I/O signals) so that the maximum limit is not exceeded.

71083, Max number of symbols exceeded

Description


The maximum number, arg, of symbols in the I/O system has been exceeded.

The number of symbols is the sum of all namned configuration instances:

- I/O Buses

- Unit types

- I/O Units

- I/O Signals



- Command types

- Commands

- I/O Access levels

- CIP Routes


Modify the configuration of the I/O system (by reducing the number of symbols) so that the maximum limit is not exceeded.

71099, Trusted NFS server lost

Description

The contact with the trusted NFS server <arg> is lost.


1. The NFS server.

2. The network connection.

3. The controller configuration.

71084, Max number of subscribed I/O signals exceeded

Description


The maximum number, arg, of subscribed I/O signals in the I/O system has been exceeded.


Modify the configuration of the I/O system (by reducing the number of subscriptions) so that the maximum limit is not exceeded.

71100, Max number of I/O buses exceeded

Description


The maximum number, arg, of I/O buses in the I/O system has been exceeded.



I/O buses) so that the maximum limit is not exceeded.

71085, Max number of I/O units exceeded

Description


The maximum number, arg, of I/O units in the I/O system has been exceeded.



I/O units) so that the maximum limit is not exceeded.

71097, Input I/O signal stored

Description


Input I/O signals must not be stored.

Only output I/O signals can be stored.



Remove the store for the I/O signal (or change the signal type).

71101, I/O bus undefined

Description


The I/O bus <arg> cannot be found in the system. An I/O unit must refer to a defined I/O bus.

Installed I/O buses are:argargarg

Consequences

This I/O unit has been rejected, and no functions depending on it will work.


1. Make sure the I/O bus is defined.

2. Make sure the I/O bus name is correctly spelt.

71098, NFS server lost

Description

The contact with the NFS server <arg> is lost.


1. The NFS server.

2. The network connection.

3. The controller configuration.

71108, Interbus I/O unit failure

Description

I/O unit <arg> at address <arg> reported peripheral fault. Interbus specific error code: arg.

Consequences

The I/O unit cannot be contacted by the control system. Parts of the

Interbus network will not be accessible, depending on the network topology and the nature of the fault.

Probable causes

A number of errors may cause this. Further information may be found in the standard Interbus documentation.


1. Make sure the I/O unit at the above address is functioning correctly.

2. Check the Interbus specific error code as specified in the Interbus

Manuals: Firmware Service and Error Messages.



71109, Interbus bus failure

Description

The control system has lost communication with the Interbus network.

There is no error message from any Interbus board.

Consequences

Parts of the Interbus network will not be accessible, depending on the network topology and the nature of the fault.

Probable causes



1. Make sure the Customer Power Supply unit, supplying the

Interbus network with power, is working correctly. Replace any faulty

I/O unit.

2. Make sure any fuses are correctly connected.

3. Make sure all communication cables and connectors are working correctly and of the recommended type.

4. Check network topology and cable length.



Description

The control system has lost communication with the I/O unit at address

<arg.arg>. Interbus specific error code: arg.

Consequences


Probable causes



1. Make sure the I/O unit at the above address is functioning correctly.




Check the ID code of the I/O unit's unit type in the system parameters.

How to check the configuration file is detailed in the Trouble Shooting

Manual.

2. Replace the I/O unit with another using the correct ID code in the

Interbus configuration as specified in the supplier's documentation.

3. Specify a generic unit type in the system parameters: ibsGeneric and ibsSlave.

71114, Invalid IP address

Description

The IP address <arg> is not valid.


Check the communication configuration.

71115, Invalid subnet mask

Description

The subnet mask <arg> is not valid.


Check the communication configuration.

71116, Deactivated I/O unit with Unit Trustlevel

<Required (0)>

Description

The I/O configuration of I/O unit <arg> is invalid.

I/O units with Unit Trustlevel Required (0) are not allowed to be

Deactivated.

Consequences

This I/O unit has been rejected, and no functions depending on it will work.


Correct the configuration of the I/O unit by either Activating it or changing the Unit Trustlevel.

71111, ID code mismatch

Description

The ID code <arg> read from Interbus I/O unit <arg> doesn't match the expected value arg from the unit type configuration.

Consequences

The I/O unit has not been configured, and cannot be used by the system.

Probable causes

Wrong ID code value may have been introduced to the system parameters. The Interbus network may have been configured with a I/

O unit with the wrong ID code.

71122, Incorrect IP address

Description

The address <arg> in protocol <arg> is not a correct IP address.


Correct the address.

71123, No transmission protocol

Description

The transmission protocol <arg> given for application protocol <arg> could not be found.


Change the transmission protocol.



71125, Mount Permission denied

Description

Permission was denied to mount the directory <arg> on the server

<arg>.


Change the User or Group ID.

71139, Access error from I/O system

Description

Cannot read or write I/O signal <arg> due to communication down.


Check 'No contact with I/O unit' report for more detailed information.

71126, Directory not exported

Description

Mounting directory <arg> as <arg> failed since it is not exported on the server computer <arg>.

Protocol: <arg>.


Export the directory on the server computer.

71141, Default value for I/O signal out of range

Description


The default value is out of range.



Change the default value for the I/O signal.

71128, Ethernet not installed

Description

The Ethernet Services option has to be installed when using remote mounted disk.


Reboot and install the Ethernet Services option.

71145, Interbus bus has been deactivated

Description

The Interbus bus has switched to a none running mode.


Restart the system.

2. Check that correct Interbus boot project is selected.

71129, Too many remote disks

Description

The maximum number of remote mounted disks have been exceeded.

The maximum number is arg.


Reduce the number of remote mounted disks.

71147, No response from the Interbus network

Description

Access to the Interbus network is denied.


1. Check the Interbus board.

2. Check the internal Interbus configuration.

3. Reduce the cycle time on the slave I/O unit.

71130, Too many remote servers

Description

The maximum number of servers for remote mounted disks have been exceeded.

The maximum number is arg.


1. Reduce the number of servers.

71148, No access to the Interbus network

Description

Access to the Interbus service interface is denied during arg, error code is 0xarg.


1. Check the internal Interbus configuration.

2. The Interbus may be faulty. Replace any faulty I/O unit if required.

71131, Could not mount directory

Description

Mounting directory <arg> on the computer <arg> failed.

Protocol: <arg>.


Check the server setup.

71156, IPC queue full

Description

The interprocess communication (IPC) queue <arg> was full, when sending to trap routine.


Restart the system.



71158, Address out of range

Description


The address of I/O unit <arg> is invalid (out of range).



1. Change the address.

2. Check the address syntax.

71163, I/O signal on internal I/O unit

Description


The user-defined I/O signal <arg> must not be connected to the internal I/O unit <arg>

User defined I/O signals are not allowed to be connected to internal I/

O units.



Connect the I/O signal to another I/O unit.

71164, Internal I/O signal in cross connection

Description

The I/O configuration contains an invalid cross connection.

The <Actorargarg> is a user-defined I/O signal whereas the resultant

I/O signal <arg> is an internal I/O signal.

It is not allowed to define cross connections where user-defined I/O signals affect internal I/O signals.


Correct the cross connection so that there are no internal I/O signals in the resultant expression.

71165, FTP server went down

Description

The connection to a non-trusted FTP server has been lost.

IP address: <arg>.


Check cable and FTP server settings.

71167, Wrong transmission protocol

Description

No matching transmission protocol was found in the configuration.


Change the transmission protocol.

71169, Ethernet not installed

Description

The option Ethernet Services with FTP is not installed on this system.


Reboot and install the Ethernet Services with FTP option.

71182, I/O signal undefined

Description


The parameter <Resultant I/O signal> of one of the cross connections contains a reference to an undefined I/O signal <arg>.



Correct the cross connection so that the resultant I/O signal refers to an existing I/O signal.

71183, Cross connection with invalid operator

Description


The parameter <Operator arg> of one of the cross connections contains an invalid/unknown operator <arg>.

Valid values for the logical operator are:

- AND

- OR



Correct the operator.

71166, FTP server went down

Description

The connection to a trusted FTP server has been lost.

IP address: <arg>.


Check cable and FTP server settings.

71185, Duplicated name

Description


The identifier <arg> has already been used as the name of another configuration instance.

The following configuration instances must have unique names:

- I/O Buses

- Unit types

- I/O Units

- I/O Signals

- Command types

- Commands



- I/O Access levels

- CIP Routes

This configuration instance has been rejected.


1. Rename one of the configuration instances in system parameters.


71193, Invalid physical I/O mapping

Description

I/O mapping error on I/O unit <arg>.


Check configuration for physical signal mapping.

71196, Invalid encoding type

Description


The encoding type <arg> is not valid for signal type <arg>.

Valid encoding types are:

- UNSIGNED

- TWO_COMP



Correct the encoding type for the I/O signal.

71220, No Profibus option has been installed

Description

A Profibus-DP master/slave board has been fitted, but no Profibus option has been installed.

Consequences

No communication on the Profibus is possible. There may be consequential errors from configuring Profibus when no such option has been installed.

Probable causes

An attempt may have been made to add the Profibus functionality, without installing the option correctly.


1. If the Profibus option is required: configure a new system with this option, and install the system.

2. If the Profibus option is not required: configure a new system without this option, and install the system.

71221, Profibus firmware file not found

Description

The Profibus <arg> firmware file not found or not readable.

The board firmware may be out of date.



71201, Unknown I/O bus

Description


The I/O bus <arg> cannot be found in the system.

Installed I/O buses are:argargargarg

Consequences

This I/O bus has been rejected, and no functions depending on it will work.


1. Make sure the system has been configured with the desired I/O bus.

2. Make sure the I/O bus option at hand is installed.

3. Check the configuration for I/O bus.

71205, Could not mount directory

Description

Mounting directory <arg> on the computer <arg> failed.

Protocol: <arg>.


1. Check the FTP server setup.

2. Check the FTP client configuration.

3. Check communication hardware, cabling.

71222, Profibus configuration file not found

Description

The binary Profibus configuration file was not found.

- File: <arg>

- Path: <arg>.


1. Make sure the file exists.

2. Change the path in the I/O configuration.

71223, Profibus file parse error

Description

The binary Profibus configuration file is corrupt. (Internal error: arg)

- File: <arg>

- Path: <arg>.


Recreate and download the binary configuration file using the external

Profibus configuration tool.

71224, Profibus channel has been reflashed

Description

The arg channel firmware of the Profibus board has been updated from

<arg> to <arg>.



71225, Profibus configuration error

Description

The local slave channel has more DI/DO than the configuration in its master.


Make the number of DI/DO of the external Profibus master more or equal than the local slave.

71230, I/O unit configuration error

Description

I/O unit <arg> is configured in system parameters but is missing or incorrect in Profibus binary file.


1. Check/change system parameters.

2. Check/change Profibus binary file.

71226, Profibus configuration ok

Description

The number of DI/DO of the external Profibus master is now more or equal than for the I/O unit of DP_SLAVE type.


71227, Initialization of Profibus slave failed

Description

The slave channel on the Profibus-DP master/slave board did not start up correctly.

Consequences

No communication on the Profibus slave channel is possible.

Probable causes

The board hardware may be malfunctioning.



2. Replace the Profibus slave board if faulty.

71231, Wrong Profibus I/O unit is connected

Description

Profibus I/O unit <arg> at address <arg> has the wrong identity number. Reported identity number is arg. Expected identity number is

arg.

Consequences

The system will not be able to Activate the I/O unit and no communication on the Profibus will be possible.

Probable causes

-The I/O unit at address <arg> may be the wrong type of I/O unit.

-The configuration may be incorrect, i.e. an incorrect binary configuration file and in some cases incorrect system parameters.


1. Make sure the system parameters are correct.

2. Make sure the Profibus binary file is correct.

3. Replace the I/O unit.

71228, Profibus binary configuration fault

Description

The configuration data in the binary file is not accepted by the slave at address <arg>.


Make the configuration data in the binary file match the configuration for the slave and reboot the system

71229, Profibus binary parameter fault

Description

The parameter data in the binary file is not accepted by the slave at address <arg>.


Make the parameter data in the binary file match the parameters for the slave and reboot the system.

71232, Too many internal Profibus slaves

Description

There are too many internal Profibus slaves defined in the system.

Consequences

Profibus I/O unit <arg> will not be configured. No communication with this unit will be possible.

Probable causes

Profibus I/O unit <arg> is defined as an internal slave while another internal slave has already been configured.

The maximum number of internal slaves is 1.



2. Make sure the Profibus binary file is correct.

71241, Too many I/O units on I/O bus

Description


The number of I/O units on I/O bus <arg> must not exceed arg.





Reduce the number of defined I/O units and reboot the system.

71244, Incorrect Interbus unit type

Description

I/O unit <arg> at address <arg> has a unit type not supported by the system.

Consequences


Probable causes

One or more of the units connected to the network is of a hardware version not supported by the system.


1. Replace the unsupported I/O unit with one of the correct version.


3. Reconfigure the Interbus network.

71245, I/O unit not defined in Interbus configuration

Description

I/O unit <arg.arg> is not assigned to any address in the Interbus configuration.

Consequences


Probable causes

Data for defining the I/O unit is missing in the Interbus configuration.


Change the Interbus configuration using the CMD tool under the

Process Data menu. Add an address for the I/O unit. The CMD tool is available from your local ABB representative.

71246, No access to Interbus data

Description

Access to the Interbus board data interface is denied. arg not performed, error code arg.


1. The Interbus board may be faulty. Replace any faulty boards if required.

2. Check the Interbus internal configuration.

Consequences


Probable causes

The Interbus unit address in the Interbus configuration differs from that in the system parameters, or the I/O unit may not have been configured at all in the Interbus configuration.


1. Make sure system parameters are correct.


71249, Interbus I/O unit configuration mismatch

Description

The Interbus I/O unit with address <arg.arg> is configured in the

Interbus configuration, but not in the system parameters.

Consequences


Probable causes

The Interbus unit address in the Interbus configuration differs from that in the system parameters, or the I/O unit may not have been configured at all in the system parameters.


1. Make sure system parameters are correct.


71250, Cannot configure Interbus board

Description

An error has occurred when downloading Interbus configuration file to the Interbus board. Interbus specific error code: arg.

Consequences

The I/O bus has not been configured, and cannot be used by the system.

Probable causes

The path specifying the Interbus configuration files points out the wrong files or that configuration file is incorrect.


1. Use RobotStudio to check the path to the configuration files.

2. Make sure the configuration files are correct.



71248, Interbus I/O unit configuration mismatch

Description

The Interbus I/O unit with address <arg> is configured in the system parameters, but not in the Interbus configuration.

71258, Interbus configuration file not found

Description

The Interbus configuration file <arg>, configured in the system parameters, was not found.



Consequences


Probable causes

The Interbus configuration file does not exist or the path specified in the system parameters was incorrect.


1. Make sure the Interbus configuration files are correctly located.

2. Use RobotStudio to check the path to the configuration files.

71273, I/O unit configuration mismatch

Description

I/O unit <arg> is configured in the system parameters, but it cannot be found in the I/O bus specific configuration.

Probable causes

1. The address of the I/O unit in the system parameters are not the same as in the I/O bus specific configuration.

2. The I/O unit has not been configured at all in the I/O bus specific configuration.


1. Check I/O unit configuration in system parameters

2. Check I/O bus specific configuration

71259, Cannot read the Interbus configuration file

Description

An error occurred when attempting to read the Interbus board configuration file <arg>.

Consequences



1. Reload the Interbus configuration file to the robot controller.



Description

The control system was unable to determine the bus operating mode of the Interbus board.


Restart the system.


Description

The control system has lost communication with the Interbus network.

Interbus specific error code: arg.

Consequences


Probable causes



1. Make sure all communication cables and connectors are working correctly and of the recommended type



71261, Transport layer failure

Description

The physical channel for transport layer arg is invalid.


Verify that the physical channel is valid, see manual.

71276, Communication established with I/O unit

Description

Communication established with I/O unit <arg>.

71278, Mount permission denied

Description

Permission was denied to mount the directory <arg> on the server

<arg>.


Check the username and password.

71288, Mount path is too large

Description

Mount path is too large. Mount path consists of FTP server mount point and server path.

- Max length: <arg>

- Protocol used: <arg>


Change FTP server mount point or server path.

71289, Memory partition is too big

Description

The memory partition for communication purposes cannot be allocated. The requested partition arg kB. System partition will be used.




Decrease commPartSize.

71290, Could not add FTP device

Description

Adding the FTP device <arg> to the operating system failed.

Application protocol <arg>.


Change the local path of the configuration of the FTP device.

71291, Invalid local path

Description

Local path of the FTP device <arg> is invalid.


Local path must end with :

71293, Invalid input size

Description

On DeviceNet I/O unit <arg> the connection 1 input size does not match the I/O unit.


1. Change size in configuration.

2. Check module.

3. Use DN_GENERIC unit type

71294, Invalid output size

Description

On DeviceNet I/O unit <arg> the connection 1 output size does not match the I/O unit.



2. Check module.

3. Use DN_GENERIC unit type

71295, Invalid input size

Description

On DeviceNet I/O unit <arg> the connection 2 input size does not match the I/O unit.



2. Check module.

71296, Invalid output size

Description

On DeviceNet I/O unit <arg> the connection 2 output size does not match the I/O unit.



2. Check module.

71297, Invalid connection type

Description

The DeviceNet I/O unit <arg> does not support arg connection.


1. Change connection 1 type and/or connection 2 type in configuration.

2. Use DN_GENERIC unit type.

71298, Duplicated address

Description

The address <arg> for the DeviceNet master on I/O bus <arg> is occupied by another I/O unit on the network.


1. Change master address in configuration.

2. Disconnect I/O unit occupying the address from the network.


71299, No power on DeviceNet bus

Description

The 24 V power supply from the DeviceNet power supply is missing.

Consequences

No communication on the DeviceNet bus <arg> is possible.

Probable causes

The power supply unit, cabling, input voltage to the power supply or the output load may cause the power loss. See the Trouble Shooting

Manual and Circuit Diagram!


1. Check all cabling to the power supply unit.

2. Measure the output and input voltage levels.

3. Replace the faulty I/O unit if required.

71300, DeviceNet bus communication warning

Description

A minor number of communication errors occurred on DeviceNet bus

<arg>.

Consequences

Normal operation will be maintained, even on the DeviceNet.



Probable causes

The fault may be caused by interference, power supply units and cables, or communication cables.


1. Make sure any terminating resistors are correctly connected.



4. Make sure the DeviceNet Power Supply unit is working correctly.

Replace any faulty unit.

71303, Invalid DeviceNet vendor id

Description

The vendor id read from DeviceNet I/O unit <arg> doesn't match value in unit type configuration.

- Configuration: <arg>

- Actual: <arg>


1. Change vendor id in configuration.

2. Check that the type of I/O unit is correct.

71301, Bus off, DeviceNet bus communication failure

Description

A major number of communication errors occurred on DeviceNet bus

<arg>.

Consequences

All communication on the DeviceNet Bus has stopped.

Probable causes

The fault may be caused by interference, power supply units and cables, or communication cables.


1. Make sure the DeviceNet Power Supply unit is working correctly.

Replace any faulty I/O unit.

2. Make sure any terminating resistors are correctly connected.




71304, Invalid DeviceNet device type

Description

The device type read from DeviceNet I/O unit <arg> doesn't match value in unit type configuration.


- Actual: <arg>


1. Change device type in configuration.


71305, Invalid DeviceNet product code

Description

The product code read from DeviceNet I/O unit <arg> doesn't match value in unit type configuration.


- Actual: <arg>


1. Change product code in configuration.


71302, No DeviceNet option has been installed

Description

A DeviceNet master/slave board has been fitted, but no DeviceNet option has been installed.

Consequences

No communication on the DeviceNet is possible. There may be consequential errors from configuring DeviceNet when no such option has been installed.

Probable causes

An attempt may have been made to add the DeviceNet functionality, without installing the option correctly.


1. If the DeviceNet option is required: configure a new system with this option, and install the system.

2. If the DeviceNet option is not required: configure a new system without this option, and install the system.

71306, DeviceNet unknown error

Description

An unknown error is reported from I/O unit <arg> error code arg.



2. Report problem to ABB.

71307, DeviceNet generic connection 1

Description

On DeviceNet I/O unit <arg> connection 1 configuration are generic.

Real values:

- Connection 1 type: <arg>

- Connection 1 input size: <arg>

- Connection 1 output size: <arg>




1. Create a new unit type with correct values.

2. Update your current unit type configuration.

71308, DeviceNet generic connection 2

Description

On DeviceNet I/O unit <arg> connection 2 configuration are generic.

Real values:

- Connection 2 type: <arg>

- Connection 2 input size: <arg>

- Connection 2 output size: <arg>




71309, DeviceNet generic unit identification

Description

On DeviceNet I/O unit <arg> identity configuration are generic.

Real values:

- Vendor Id: <arg>

- Product code: <arg>

- Device type: <arg>




71310, DeviceNet I/O unit connection error

Description

DeviceNet I/O unit <arg> is occupied by another master.


1. Check configuration.

2. Cycle power on I/O unit.

71312, DeviceNet I/O unit explicit connection not enabled

Description

DeviceNet I/O unit <arg> does not have the explicit message connection enabled.


Change configuration.

71313, Fieldbus command type order number not unique.

Description


Fieldbus command <arg> and <arg> are connected to the same unit type <arg> and have the same order number <arg>.

The order number of commands connected to the same I/O unit must be unique.

This command has been rejected.


Correct the configuration.

71314, Invalid fieldbus command type

Description


One of the fieldbus commands has a reference to an invalid/unknown command type < arg>.

All fieldbus commands must refer to an existing command type.

This fieldbus command has been rejected.


Correct the fieldbus command type for the command.

71311, Unable to established communication on DeviceNet bus

Description

Unable to established communication on DeviceNet bus <arg> because no I/O units are physically connected.


1. Check cables and connectors.

2. Connect I/O units to I/O bus.


4. Remove I/O units on the I/O bus <arg> from the configuration.

71315, Max number of fieldbus commands exceeded

Description


The maximum number, arg, of fieldbus commands in the I/O system has been exceeded.


Modify the configuration of the I/O system (by reducing the number of fieldbus commands) so that the maximum limit is not exceeded.

71316, Max number of fieldbus command types exceeded

Description


The maximum number arg, of fieldbus command types in the I/O system has been exceeded.




Modify the configuration of the I/O system (by reducing the number of fieldbus command types) so that the maximum limit is not exceeded.

71317, DeviceNet I/O unit reset

Description

DeviceNet I/O unit <arg> have been restarted through fieldbus command arg, to make sure fieldbus command values are activated.

This will cause the I/O unit to loose contact while the I/O unit is restarted and then automatically be reconnected.


1. Do nothing.

2. If restart not necessary remove fieldbus command configuration on unit type.

71318, Failed to send fieldbus command

Description

Fieldbus command <arg> to I/O unit &l