DeviceNet 3HAC020676-001 - Revf - en PDF

Application manual
DeviceNet
Robot controller
RobotWare 5.0
Application manual
DeviceNet
RobotWare 5.0
Document ID: 3HAC020676-001

Revision: F
© Copyright 2004-2007 ABB. All rights reserved.
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 2004-2007 ABB All rights reserved.

ABB AB
Robotics Products
SE-721 68 Västerås
Sweden
Table of Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Product documentation, M2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1 Overview 11
1.1 DeviceNet, general . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 DeviceNet, IRC5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.3 Definition of I/O units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2 Hardware description 17
2.1 DeviceNet Master/Slave, DSQC 658 and DSQC 659 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2.1 Shield grounding and power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2.2 Connection of the DeviceNet bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.3 Selecting cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2.4 Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3 DeviceNet Master/Slave configuration 27

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2 Configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.2.1 DeviceNet master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.2.2 Internal DeviceNet slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.3 Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.1 Configuration of third part units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.2 Working with IRC5 internal DeviceNet slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.3 DeviceNet communication between two IRC5 controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4 System parameters 41
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.2 Type Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.2.1 DeviceNet Master Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.2.2 DeviceNet Communication Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.3 Type Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.3.1 DeviceNet Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.4 Type Unit Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.4.1 Vendor ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.4.2 Product Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.4.3 Device Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.4.4 Major Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.4.5 Minor Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.4.6 Production Inhibit Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.4.7 Explicit Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.4.8 Connection 1 Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.4.9 Connection 1 Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.4.10 Connection 1 Output Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.4.11 Connection 1 Input Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.4.12 Quick Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.4.13 Internal Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.4.14 Trigger Poll I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.5 Type Fieldbus Command Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.5.1 Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.5.2 Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3HAC020676-001 Revision: F 3
Table of Contents
5 Trouble shooting 63
5.1 Bus off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6 Boards and units 65

6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.1.1 DeviceNet Bus and I/O board status LED description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.1.2 DeviceNet Bus status LEDs at power-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.1.3 External I/O units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.1.4 Coil neutralization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.1.5 Setting DeviceNet bus ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.2 Unit descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.2.2 DSQC 651, AD combi I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.2.3 DSQC 652, Digital I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.2.4 DSQC 653, Digital I/O with relay outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.2.5 DSQC 355A, Analog I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
6.2.6 DSQC 350A, DeviceNet/Allen Bradley remote I/O gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6.2.7 DSQC 351A, DeviceNet/INTERBUS gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
6.2.8 DSQC 352A, DeviceNet/PROFIBUS-DP gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6.2.9 DSQC 378A, DeviceNet/CCLink gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6.2.10 DSQC 377A, Queue tracking unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Index 131
4 3HAC020676-001 Revision: F
Overview
Overview
About this manual

This manual describes the DeviceNet option and contains instructions for the DeviceNet
Master/Slave configuration. It also describes the configuration of boards and units.
Usage
This manual should be used during installation and configuration of the DeviceNet bus and
upgrading of the DeviceNet option.
Who should read this manual?

This manual is intended for:
• Personnel that are responsible for installations and configurations of fieldbus
hardware/software
• Personnel that make the configurations of the I/O system
• System integrators
Prerequisites
The reader should have the required knowledge of:
• Mechanical installation work
• Electrical installation work
Organization of chapters
The manual is organized in the following chapters:
Chapter Contents
1 This chapter gives an overview of the DeviceNet fieldbus and includes the
following:
• A general description of DeviceNet and the communication protocol
connections
• Description of how the DeviceNet master/slave unit and I/O units are
connected in a robot system
• Definition of I/O units in the IRC5 controller and the configuration of
the controller
2 This chapter describes the DeviceNet Master/Slave boards.
The chapter also describes:
• Communication units
• How to connect the DeviceNet master to an I/O unit
• Termination
• Cable types and data rates
• Repeater functions
3 This chapter gives an overview of the DeviceNet master and internal slave
configuration. The chapter also contains descriptions of workflows.
4 This chapter describes the DeviceNet specific system parameters.
5 This chapter contains information and instructions for trouble shooting the
DeviceNet connection.
Continues on next page

Overview
Continued
Chapter Contents
6 This chapter gives detailed descriptions of I/O units and gateways available
from ABB Robotics and that support DeviceNet communication.
The chapter also describes:
• DeviceNet bus status LEDs at power-up
• How to set the DeviceNet bus ID
References
Document references
References Document ID
Application manual - Conveyor tracking 3HAC16587-1
Application manual - Motion coordination and supervision 3HAC18154-1
Application manual - Robot communication and I/O control 3HAC020435-001
Operating manual - IRC5 with FlexPendant 3HAC16590-1
Operating manual - RobotStudio Online 3HAC18236-1
Product manual - IRC5 3HAC021313-001
Product specification - IRC5 with FlexPendant 3HAC021785-001
Technical reference manual - System parameters 3HAC17076-1
Other references
References Description
www.odva.org The web site of ODVA (Open DeviceNet
Vendor Association).
ODVA DeviceNet Specification, revision 2.0 Specification from ODVA (Open DeviceNet
Vendor Associations).

Overview
Continued
Revisions
Revision Description
- First edition
A The following corrections are made in chapter 5 Boards and units:
• A completing in section General.
• A correction in the description of the numerical format for the DSQC
355A unit, in section Unit descriptions.
B The following updates are made in chapter 2 Overview:
• Section DeviceNet, general; the different types of I/O connections are
described more in detail.
• Section DeviceNet, IRC5; the figure illustrating the hardware overview is
updated.
The following updates are made in chapter 4 DeviceNet Master/Slave config-
uration:
• Section Working with IRC5 internal DeviceNet slave; the illustration is
updated.
• Section DeviceNet communication between two IRC5 controllers; the
illustration is updated.
The following updates are made in chapter 5 Boards and units:
• Section Unit descriptions; the article numbers for the respective units are
completed in the overview table of the I/O units. Each I/O unit description
includes information about which types of I/O connections they support.
• Section DSQC 332A, Digital I/O with relay outputs; illustrations of how to
connect the digital outputs and digital inputs.
C New DeviceNet Master/Slave boards, DSQC 658 and DSQC 659, which
replace the earlier version, DSQC 603. Section DSQC 658 and DSQC 659,
DeviceNet Master/Slave.
The following new I/O units are included in section Unit descriptions:
• DSQC 651, AD combi I/O
• DSQC 652, Digital I/O
• DSQC 653, Digital I/O with relay outputs
D Information about DeviceNet internal slave, I/O connection, in chapter 4.2.2
updated.
E Information updated in chapter 2.2 DeviceNet, IRC5. Chapter 6 Trouble

shooting added.
F Updates and corrections are made. New system parameters, Trigger Poll I/O
and Internal Slave, are added.
Descriptions of the following circuit boards are removed: DSQC 327A, DSQC
328A, and DSQC 332A.
Product documentation, M2004
General
The robot documentation is divided into a number of categories. This listing is based on the
type of information contained within the documents, regardless of whether the products are
standard or optional. This means that any given delivery of robot products will not contain all
documents listed, only the ones pertaining to the equipment delivered.
However, all documents listed may be ordered from ABB. The documents listed are valid for
M2004 robot systems.
Product manuals
All hardware, robots and controllers, will be delivered with a Product manual that contains:
• Safety information
• Installation and commissioning (descriptions of mechanical installation, electrical
connections)
• Maintenance (descriptions of all required preventive maintenance procedures
including intervals)
• Repair (descriptions of all recommended repair procedures including spare parts)
• Additional procedures, if any (calibration, decommissioning)
• Reference information (article numbers for documentation referred to in Product
manual, procedures, lists of tools, safety standards)
• Part list
• Foldouts or exploded views
• Circuit diagrams
Technical reference manuals

The following manuals describe the robot software in general and contain relevant reference
information:

• RAPID Overview: An overview of the RAPID programming language.
• RAPID Instructions, Functions and Data types: Description and syntax for all
RAPID instructions, functions and data types.
• System parameters: Description of system parameters and configuration workflows.
Application manuals
Specific applications (for example software or hardware options) are described in
Application manuals. An application manual can describe one or several applications.
An application manual generally contains information about:
• The purpose of the application (what it does and when it is useful)
• What is included (for example cables, I/O boards, RAPID instructions, system
parameters, CD with PC software)
• How to use the application
• Examples of how to use the application

Continued
Operating manuals
This group of manuals is aimed at those having first hand operational contact with the robot,
that is production cell operators, programmers and trouble shooters. The group of manuals
includes:
• Emergency safety information
• Getting started - IRC5 and RobotStudio Online
• IRC5 with FlexPendant
• RobotStudio Online
• Trouble shooting - IRC5 for the controller and robot
Safety
Safety
Safety of personnel
When working inside the robot controller it is necessary to be aware of voltage-related risks.
A danger of high voltage is associated with the following parts:
• Units inside the controller, for example I/O units can be supplied with power from an
external source.
• The mains supply/mains switch.
• The power unit.
• The power supply unit for the computer system (230 VAC).
• The rectifier unit (400-480 VAC and 700 VDC). Capacitors!
• The drive unit (700 VDC).
• The service outlets (115/230 VAC).
• The power supply unit for tools, or special power supply units for the machining
process.
• The external voltage connected to the controller remains live even when the robot is
disconnected from the mains.
• Additional connections.
Therefore, it is important that all safety regulations are followed when doing mechanical and
electrical installation work.
Safety regulations
Before beginning mechanical and/or electrical installations, make sure you are familiar with
the safety regulations described in Product manual - IRC5.
1 Overview
1.1. DeviceNet, general
1 Overview
What is DeviceNet?
DeviceNet is a communications link to connect industrial devices. It is a simple networking
solution that reduces both cost and time to wire and install industrial automation devices, and
the direct connectivity provides improved communication between devices. DeviceNet is an
open network standard.
Here are some examples of applications:
• Peer-to-peer data exchange where a DeviceNet product can produce and consume
messages
• Master/slave operation defined as a proper subset of Peer-to-Peer
• A DeviceNet product can function as a client or server, or both
DeviceNet specification
The DeviceNet specification defines a network communication system for moving data
between elements of an industrial control system.
Communication protocol connections

The user must establish a connection with a device in order to exchange information with that
device.
DeviceNet defines the following two different types of messaging:
Type of message Description

Explicit messages Explicit messages provide multi-purpose and point-to-point
communication paths between two devices. Explicit messages
provide the typical request/response oriented network commu-
nications used to perform node configuration and problem

diagnosis.
I/O messages I/O messages are for time-critical and control-oriented data,
and they provide a dedicated and special-purpose communica-
tion path between a producing application and one or more
consuming applications.

1 Overview
Continued
I/O messages - connection types

The following table describes the different types of I/O connections.
Type of I/O connection Description

Polled connection This technique is used for any amount of I/O data. Each slave
receives a query from the master and may or may not respond
before the next device has received a query. A slave can only
respond to a request from the master.
Strobe connection A single multicasting request. Quick exchange of a small
amount of I/O data between a master and its slaves. The
master sends one message that contains one bit of output data
to each slave that has a strobe connection. This will result in a
synchronized reading of data.
Change-Of-State (COS) Units are configured to produce data upon a change of I/O data.
connection This technique can improve system throughput significantly.
Data messages must be acknowledged by the receiver before
new messages can be sent. Heart beat messages are used to
tell the receiver that the unit is still alive even if no data has
changed state for a long time.
Cyclic connection Units are configured to produce data on a pre-configured time
interval. Data production messages must be acknowledged
before a new message can be sent.
Change-Of-State with Units are configured to produce data upon a change of
acknowledge suppression application data. This technique can improve system
throughput significantly. No acknowledge is required - that is,
the receiver of data must be able to consume the data at the
same rate as it is produced by the sending unit.
Cyclic with acknowledge Units are configured to produce data on a pre-configured time
suppression interval. No acknowledge is required - that is, the receiver of
data must be able to consume the data at the same rate as it is
produced by the sending unit.
1 Overview
1.2. DeviceNet, IRC5
General
Several I/O units and gateways for DeviceNet communication are available from ABB
Robotics. See Unit descriptions on page 73.
When ordering DeviceNet there are the following three options:
• DeviceNet single, which consists of 1 Master/Slave channel
• DeviceNet dual, which consists of 2 Master/Slave channels
• DeviceNet quadruple, which consists of 4 Master/Slave channels
Hardware overview
The hardware of the DeviceNet fieldbus consists of a Master/Slave unit, DSQC 658 (single
channel) or DSQC 659 (dual channel), and distributed I/O units (called Slave units). The
Master/Slave unit is connected to the PCI backplane on the main computer in the robot
controller.
The slave part of the Master/Slave unit is normally controlled by an external master on the
same physical DeviceNet network. It is possible to act as a master and a slave simultaneously.
Slave units
The slave units are attached to the fieldbus network, and can be any DeviceNet compliant
device. They are controlled via the master part of the Master/Slave unit.
Illustration, example
The following illustration shows an example of the hardware.
xx0300000531
A DSQC 658, DeviceNet fieldbus. Placed in the computer module.

B Terminating resistor (121 Ohm).

1 Overview
Continued
C DSQC 608/609, DeviceNet power supply 24 V

D DSQC 608/609, Customer power supply 24 V
E DSQC 652, Distributed digital I/O. The maximum length of the drop cable
is 6 m.
F IRC5 controller
Additional Master/Slave
The IRC5 system supports up to four Master/Slave units. They will work independently from
each other, for example have different baud rates, and have the same possibilities and
constrains as described in this document. To achieve this it is possible to use up to two
DeviceNet boards of the same type (DSQC 658 or DSQC 659).
There are the following possible hardware configurations:
• One or two DSQC 658
• One or two DSQC 659
NOTE!
It is not possible to use the DSQC 603 together with the DSQC 658 or the DSQC 659, in the
same robot controller.
Bus configuration
Configuration of the bus is done using RobotStudio Online. Refer to Operating manual -
RobotStudio Online .
Specification overview
Item Specification
Fieldbus type DeviceNet
Specification revision DeviceNet specification release 2.0
Data rate 125, 250, 500 Kbps © Copyright 2004-2007 ABB. All rights reserved.
Support for Predefined Master/Slave Group 2 Client (Master)

connection set Group 2 Only Client (Master)
Group 2 Server (Slave)
1 Overview
1.3. Definition of I/O units
General
It is possible to connect any type of DeviceNet compliant I/O unit on the DeviceNet master
bus. All I/O units should comply with the DeviceNet standard and be conformance tested by
ODVA.
I/O units may be mounted inside the controller. In the standard form no I/O unit is mounted
to the controller. However, digital inputs and outputs are available on the customer plate in
the controller module. For details about I/O units, see Boards and units on page 65.
Configuration of the controller
xx0500002046
A Control Module of the Dual Controller

B Drive Module of the Dual Controller

C Single Cabinet Controller
Further information
The table gives references to additional information:
Information See
Detailed descriptions of all I/O units and Section Introduction on page 73.
gateways available from ABB Robotics and
that support DeviceNet communication.
How to install the I/O units and gateways Product manual - IRC5, section Replacement
mechanically and electrically. of I/O units and gateways, IRC5.
Allowed configurations of I/O units and how Technical reference manual - System
to setup the configurations parameters.
1 Overview
2 Hardware description
2.1. DeviceNet Master/Slave, DSQC 658 and DSQC 659
Description
The DSQC 658 and DSQC 659 are PCI cards mounted in the computer module. The Master/
Slave boards can be operated both as a master and a slave (at the same time) for a DeviceNet
system.
Installation of DSQC 658 and DSQC 659

For installation descriptions of the DeviceNet Master/Slave board refer to Product manual -
IRC5, section Replacement of PCI cards in the Computer unit slots.
The figure illustrates where the DeviceNet Master/Slave boards are located in the computer
unit.
xx0700000432
Description Art. no. Note Pos.

DeviceNet master/slave 3HAC025779-001 DSQC 658 A, B, C, D

(single)
DeviceNet master/slave 3HAC025780-001 DSQC 659 A, B, C, D
(dual)
Prerequisites
RobotWare 5.07 or later version, and the DeviceNet option are required to run the DeviceNet
Master/Slave board.

Continued
Illustration, DSQC 659

The figure below illustrates the mounting bracket for the DSQC 659, the front view.
NOTE!
The mounting bracket for the DSQC 658 is identical with the DSQC 659, except of the
channel B that is not included.
xx0600002860
A Channel A Health LED

B Channel A DeviceNet connector
C Channel A Communication LED
D Channel B Health LED
E Channel B DeviceNet connector
F Channel B Communication LED

Continued
DeviceNet connector
xx0200000292
The table below shows the connections to the DeviceNet connector:
Signal name I/O pin Wire color Function

V+ 1 black DeviceNet network negative power (0 V)
CANH 2 blue DeviceNet communication bus terminal (high)
Shield 3 bare Network cable shield
CANL 4 white DeviceNet communication bus terminal (low)
V- 5 red DeviceNet network positive power (24 V DC)
LEDs
Designation Color status Description

COMM Off Offline - that is, board is not communicating on the
network.
COMM Flashing green Online - that is, board is communicating on the network
but no configured devices are found.
COMM Solid green Online and configured - that is, board is communicating
on the network and at least one configured device is
found.
COMM Solid red Bus off - that is, board unable to communicate on
network.
HLT Off No power supply to PCI bus.
HLT Solid green Board is running. Start-up self test OK.
HLT Solid red Board is not running, an error occurred during board
firmware load or a fatal runtime error occurred.
NOTE!
This LED should be lit red at start-up until the proper
software is loaded.
2.2.1. Shield grounding and power
2.2 Connections
2.2.1. Shield grounding and power
General
The DeviceNet shield and V- should be interconnected and grounded at only one place in the
DeviceNet network. For more advanced connections with several power supplies refer to the
DeviceNet Specification, see References on page 6.
Grounding
The illustration below shows an example of cable grounding.
xx0300000525
2.2.2. Connection of the DeviceNet bus
Illustration
The illustration below shows an example of how to connect the DeviceNet bus.
xx0300000615
A Computer unit
B DeviceNet PCI board
C DeviceNet connector, channel A
D DeviceNet connector, channel B (DSQC 659)
E 121 ohm, 1 %, 0.25 W metal film resistor
F I/O unit
Physical connection between DeviceNet bus and DeviceNet node

The following figure shows how the next DeviceNet node is connected to the DeviceNet bus.
xx0400000849
A Incoming DeviceNet bus cable

B Outgoing DeviceNet bus cable

Continued
Termination resistors in DeviceNet bus

Each end of the DeviceNet bus must be terminated with a 121 ohm resistor. The two
terminating resistors should be as far apart as possible.
The termination resistor is placed in the cable connector. There is no internal termination on
the DeviceNet PCI board. The termination resistor is connected between CANL and CANH
- that is, between pin 2 and pin 4 according to the illustration below.
xx0400000674
2.2.3. Selecting cables
DeviceNet bus
The end-to-end network distance varies with data rate and cable thickness. For information
about cable length depending on cable type and data rate, see tables below.
For specification of the designations on the different cable types, see ODVA DeviceNet
Specification.
Data rate 500 kbit/s
Cable type Max. length

Thick trunk length 100 m
(328 ft)
Thin trunk length 100 m
(328 ft)
Flat trunk cable 75 m
(246 ft)
Maximum drop length 6m
(20 ft)
Cumulative drop length 39 m
(128 ft)

(820 ft)
(328 ft)
(656 ft)
(20 ft)
(256 ft)

(1,640 ft)
(328 ft)
(1,250 ft)
(20 ft)
(512 ft)
Continued
Illustration of trunk line and drop lines

The figure below illustrates a trunk line with drop lines. Thick or thin cable can be used for
either trunk lines or drop lines, for information about cable thickness and data rate see the
tables in section DeviceNet bus on page 23.
xx0300000579
A Terminator
B Trunk line
C Drop line
D Tap
E Zero drop
F Node
G Short drop
H T-connector
2.2.4. Repeaters
2.2.4. Repeaters
Usage
Repeaters are used for the following purposes:
• To avoid disturbances such as ESD/EFT, which may otherwise propagate to other
parts of the network.
• To isolate noisy segments.
• When using several power supplies a repeater could be used to isolate the supplies
from each other to avoid voltage potential differences and ground currents.
Extending the length of a trunk line

The following figure illustrates an application example where a repeater is used for extending
the length of a trunk line.
en0400000724
Control Controller
TR Terminating resistor
PS Power supply
Extending the length of a drop line

The following figure illustrates an application example where a repeater is used for extending
the length of a drop line.
en0400000725
Control Controller
TR Terminating resistor
PS Power supply
2.2.4. Repeaters
3 DeviceNet Master/Slave configuration
3.1. Introduction

3.1. Introduction
Controller software
The IRC5 controller must be installed with software that supports the use of the DeviceNet
network - that is, the option for DeviceNet must be installed.
For description of how to add the DeviceNet option refer to Operating manual - RobotStudio
Online, section Adding RobotWare option.
PC software
RobotStudio Online is a PC software that is used to set up connections to robots and to work
with robots.
The configuration for the DeviceNet communication is done either manually by RobotStudio
Online, or by loading a configuration file from RobotStudio Online. For information on how
to work with RobotStudio Online refer to Operating manual - RobotStudio Online, see
References on page 6.
3.2.1. DeviceNet master
3.2 Configuration overview
Configuration
The maximum number of I/O units that can be defined in the IRC5 system is described in
Technical reference manual - System parameters, see References on page 6. DeviceNet has
an addressing range from 0-63.
Counted as I/O units are:
• All DeviceNet slave units connected to the IRC5 DeviceNet master.
• The internal DeviceNet slave.
• Simulated I/O units and other I/O units connected to other IRC5 fieldbuses.
ABB I/O units and/or units from other vendors can be used. No additional software option,
except for the DeviceNet option, is required to run I/O units from other vendors.
DeviceNet generic unit type

Use the DeviceNet generic unit type if the EDS file is unavailable. To define a unit with the
predefined unit type DN_GENERIC, you only need to know the network address of the
device to be able to communicate with it.
When the unit is connected, messages containing the information necessary to create a unit
type will appear on the Event Log window of the FlexPendant. The following information
appears:
• Unit identification system parameters (Vendor ID, Device Type and Product Code)
• The first connection system parameters of the unit (Connection 1 Type, Connection 1
Input Size and Connection 1 Output Size)
Other system parameters in the Unit Type can be left to their default values. See
Configuration of third part units on page 33.
NOTE!

DN_GENERIC should only be used when installing and commissioning new devices. Using
DN_GENERIC will increase the startup time. When restarting the system the identification
of the I/O unit will be lost and there will not be any information if the unit is replaced with
another unit, which has other functionality or size.

Continued
Explicit Messaging services

It is possible to configure I/O units through explicit messaging services. This could either be
done at startup by defining Fieldbus Commands to the configured unit, or at runtime from
RAPID through the Fieldbus Command Interface (FCI), which is a RobotWare option. For
information refer to RAPID reference manual, and Application manual - Robot
communication and I/O control, section Fieldbus Command Interface. See References on
page 6.
For explicit messaging at startup:
1. Use RobotStudio Online to define a Fieldbus Command type that is general to the unit
type and could be used by many DeviceNet units of this unit type.
2. Use RobotStudio Online to define a Fieldbus Command that is specific to a certain
unit and that specifies unit specific data to be sent to the unit. The Fieldbus Command
is linked to a certain unit. The data defined in the value parameter should fit the
instance or attribute size on the DeviceNet unit.
DeviceNet specific system parameters in the Fieldbus Command type are:
• Path
• Service
For more information, refer to the DeviceNet Specification. See References on page 6.
CIP routing
To be able to use CIP routing the system parameter Explicit Messaging must be set in the unit
configuration for those units that will use CIP routing. For details about the unit
configuration, refer to Application manual - EtherNet/IP Fieldbus adapter.
3.2.2. Internal DeviceNet slave
Configuration
The internal DeviceNet slave shares address and physical connector with the master, and is
configured as an ordinary I/O unit.
The following table gives descriptions of defining the types Bus, Unit Type and Unit.
Defining... Description
Bus A DeviceNet bus must be defined before any communication on the
bus is possible - that is, define rules for the DeviceNet master to
communicate on the network.
The following two system parameters are DeviceNet specific:
• DeviceNet Master Address defines the address which the
DeviceNet master should use.
• DeviceNet Communication Speed defines the communica-
tion speed (baud rate).
For detailed information, refer to Type Bus on page 42.
Unit Type When creating a unit type some system parameters are fieldbus
specific. For detailed information about the parameters see System
parameters on page 41.
Unit specific values can be found in the EDS file (Electronic Data
Sheet) for the unit, see Electronic Data Sheet file on page 31. The
EDS file should be obtained from the vendor of the I/O module. If an
EDS file is unavailable, the generic unit type could be used to obtain
necessary information about the unit. Refer to DeviceNet generic
unit type on page 28.
Unit Technical reference manual - System parameters
Predefined bus
When the system is installed with the DeviceNet option, a predefined bus DeviceNet1 is
created.
Predefined Unit Types

The following Unit Types are predefined for the internal slave:
• DN_INTERNAL_SLAVE is used on the slave side to allow an IRC5 DeviceNet master © Copyright 2004-2007 ABB. All rights reserved.
to create a connection to an IRC5 DeviceNet slave.
• DN_SLAVE is used on the master side to connect to another IRC5 DeviceNet slave.
The predefined Unit Types are supporting a polled connection with the size of 8 input bytes
and 8 output bytes as defined in the Unit Types configuration for the fieldbuses.
If another input or output size on the internal DeviceNet slave is required, the predefined Unit
Types must be changed or new Unit Types must be created.

Continued
Limitations
The internal DeviceNet slave has the following limitations:
• The default DN_INTERNAL_SLAVE and DN_SLAVE have 8 digital input bytes and 8
digital output bytes but can be increased to the maximum value, which is 64 digital
input bytes and 64 digital output bytes.
• For the internal DeviceNet slave both the input and output map starts at bit 0 and ends
at bit 63.
Related information
Technical reference manual - System parameters
Electronic Data Sheet file

An EDS file (Electronic Data Sheet) for the DeviceNet Master/Slave units, matching the
configuration of the internal DeviceNet slave, is located on the RobotWare release CD in the
directory:
utility\fieldbus\DeviceNet\eds
If another input or output size than the predefined is used, it is recommended the values in the
EDS file are edited to match the new system parameter values.
Example, EDS file

An example from the EDS file when changing the predefined input and output sizes from 8
bytes to 16 bytes:
[IO_Info]
Default = 0x0000;
Input1 = 16;
Output1 = 16;
I/O connection
One I/O connection is supported, but there is no explicit connection to the application. Size
and connection type supported are defined in slave type Unit Type.
NOTE!
If the DeviceNet internal slave loses connection with the master, for example, bus off or
connection is interrupted, the input signals of the slave are cleared (reset to zero).
When connecting two IRC5 systems, the internal slave should be seen and configured as any
other ordinary I/O unit on the other IRC5 system, which is acting as a master.

Continued
Connecting two IRC5 systems

When connecting two IRC5 systems the internal slave should be seen and configured as any
other ordinary I/O unit from the other IRC5 system, which is acting as a master. Refer to
Working with IRC5 internal DeviceNet slave on page 35.
Illustration
The following picture illustrates how to use the predefined Unit Types.
en0700000564
3.3.1. Configuration of third part units
3.3 Workflows
Description of DeviceNet generic unit type

DN_GENERIC is a predefined unit type that is used to set up a communication with any I/O
unit in an easy way.
Usage
When new DeviceNet units should be configured and the information available is not
sufficient to create a new unit type, then the generic unit type DN_GENERIC could be used
to retrieve necessary information. This could be the case when third part units should be
configured and the EDS file is missing.
Prerequisites
The network address of the I/O unit must be known and the baud rate must match the master.
Limitations
In the Event Log window of the FlexPendant you get information about the following system
parameters:
• Vendor ID
• Product Code
• Device Type
• Connection 1 Type
• Connection 1 Input Size
• Connection 1 Output Size
NOTE!
When using DN_GENERIC you accept any type of unit as long as the address matches - that
is, make sure to use the correct address.
How to use the DeviceNet generic unit type

Following steps describe how to use the DeviceNet generic unit type:
Step Action Info/Note

1. Determine the address on the physical I/O
unit.
2. Add unit at the determined address and For information see Operating manual -
with unit type DN_GENERIC. RobotStudio Online.
3. Restart the system.
4. View event log that shows unit identifica- For information see Operating manual -
tion parameters and connection support RobotStudio Online and/or Operating
information. manual - IRC5 with FlexPendant.
Two event messages appear in the
Event Log window, in RobotStudio
Online.

Continued
Step Action Info/Note

5. Create new unit type by using information For information see Operating manual -
from the event log, and change unit type RobotStudio Online.
from DN_GENERIC to the type just
created.
6. Define the signals. For information see Operating manual -
RobotStudio Online and/or Technical
reference manual - System parameters.
7. Restart the system.
3.3.2. Working with IRC5 internal DeviceNet slave
Usage
When the IRC5 controller is connected, for example, to an external PLC, the IRC5 controller
should act as an ordinary slave unit on the DeviceNet network. The PLC connects to the IRC5
DeviceNet slave unit to exchange data.
To configure the IRC5 controller as a slave unit on the DeviceNet network, use the Unit Type
DN_INTERNAL_SLAVE. See Illustration on page 35.
Prerequisites
The network address of the DeviceNet master on the IRC5 controller must be known. The
unit configured with the predefined Unit Type DN_INTERNAL_SLAVE will share this
address. A master will connect to the internal DeviceNet slave using this address.
Illustration
The figure illustrates how to use the internal DeviceNet slave.
D
xx0400000787
A PLC
B DeviceNet master, for example, with the address 4 and a configured I/O
unit with the address 2.
C Power supply unit, 24 VDC
D IRC5 controller
E Internal DeviceNet slave, for example, with the address 2 (the same
address as the DeviceNet Master Address on the IRC5 controller).

Continued
How to use the internal DeviceNet slave
Action
1. Add a unit with the Unit Type DN_INTERNAL_SLAVE.
xx0700000557
For information about how to change the master (internal slave address), refer to
DeviceNet master on page 28, DeviceNet communication between two IRC5 controllers
on page 37, and DeviceNet Master Address on page 42.
2. Define the signals on the created unit.
xx0700000558
For information, refer to Operating manual - RobotStudio Online.

3. Restart the system. Now the IRC5 controller is ready to be contacted from another
DeviceNet master.
3.3.3. DeviceNet communication between two IRC5 controllers
Usage
When two IRC5 controllers are connected to each other via DeviceNet, one of them must be
configured as a slave and the other one must be configured as a master. See Illustration on
page 37.
Limitations
The master address cannot be the same on the two controllers since they shall be
interconnected.
Illustration
The figure illustrates DeviceNet communication between two IRC5 controllers.
xx0400000788
A IRC5 DeviceNet master

B IRC5 DeviceNet slave
C DeviceNet master
D Internal DeviceNet slave
E Power supply unit, 24V DC

Continued
How to configure the DeviceNet master-/slave controllers

The following procedures describe the configuration of a hardware setup like the one
illustrated in the picture in section Illustration on page 37. There are references to the
hardware via the capital letters associated with the respective hardware in the picture.
Action Info/Note
1. Change the DeviceNet master address See How to use the internal DeviceNet
on the DeviceNet slave (B). slave on page 36 and Change master
address on the IRC5 DeviceNet slave on
page 38.
The DeviceNet master address needs to
bechanged to avoid duplicated addresses
onthe interconnected network with theDe-
viceNet master (A).
2. Configure the DeviceNet slave (B) See How to use the internal DeviceNet
according to the configuration procedure slave on page 36 and Add unit with the Unit
for the internal DeviceNet slave. Type DN_INTERNAL_SLAVE on page 39.
3. Configure the DeviceNet master (A) to See Add unit to the DeviceNet master on
connect to the internal DeviceNet slave page 40.
(B).
4. Configure signals on the created unit.
5. Physically interconnect the two IRC5 con- The shield should only be connected to
trollers. earth at one point, and the power should
only be connected to the bus cable in one
place.
6. Restart the master controller. The master should try to connect to the
slave controller.
7. Now it is possible to set output signals on The output signals shall appear as inputs
one controller. on the other controller.
Change master address on the IRC5 DeviceNet slave
Action
1. In RobotStudio Online, go to the Robot View explorer and expand the Configuration
node for the controller. © Copyright 2004-2007 ABB. All rights reserved.
2. Double-click I/O. The Configuration Editor appears.
3. In the Configuration Editor, click Bus. Then right-click in the workspace and click Edit
Bus.

Continued
Action
4. In the Edit Bus(s) dialog box, type the DeviceNet Master Address for DeviceNet1.
Choose an address that is different from the DeviceNet master address (B).
xx0700000559
Add unit with the Unit Type DN_INTERNAL_SLAVE
Action
node for the controller.
3. In the Configuration Editor, click Unit. To add the internal DeviceNet slave unit, right-
click in the workspace and click Add Unit.
4. In the Edit Unit(s) dialog box, type the values for the parameters.
xx0700000560

Continued
NOTE!
The DeviceNet address used by this unit on the DeviceNet network is the same as the chosen
DeviceNet master address on the IRC5 DeviceNet slave (B).
Add unit to the DeviceNet master
Action
node for the controller.
3. Add a unit of the Unit Type DN_SLAVE that corresponds to the Unit Type
DN_INTERNAL_SLAVE on the DeviceNet slave IRC5 conroller (B).
4. In the Edit Unit(s) dialog box, type the values for the parameters. Set the address tothe
same value that was chosen as the DeviceNet Master Address of the DeviceNet slave
(B).
xx0700000561
4 System parameters
4.1. Introduction
4 System parameters
4.1. Introduction
Structure of this chapter

There are both DeviceNet specific parameters and more general parameters. This chapter
describes all DeviceNet specific system parameters. The parameters are divided into the type
they belong to.
For information about other system parameters refer to Technical reference manual - System
parameters.
4 System parameters
4.2.1. DeviceNet Master Address
4.2 Type Bus
4.2.1. DeviceNet Master Address
Parent
DeviceNet Master Address belongs to the type Bus, in the topic I/O.
Cfg name
DN_MasterAddress
Description
DeviceNet Master Address is mandatory for a DeviceNet fieldbus and decides what address
the master should use to communicate with other devices on the DeviceNet network.
Usage
The master address is the address that the master uses to communicate.
DeviceNet Master Address is a DeviceNet specific parameter that is only available for
DeviceNet unit types.
Prerequisites
DeviceNet single, DeviceNet dual, or DeviceNet quadruple option must be installed.
Limitations
The DeviceNet Master Address should not use the same address as another device on the
network.
Default value
The default value is 2.
Allowed values

Allowed values are the integers 0-63.
4 System parameters
4.2.2. DeviceNet Communication Speed
4.2.2. DeviceNet Communication Speed
Parent
DeviceNet Communication Speed belongs to the type Bus, in the topic I/O.
Cfg name
DN_BaudRate
Description
DeviceNet Communication Speed is mandatory for a DeviceNet fieldbus and decides what
communication speed (baud rate) the DeviceNet master should use to communicate with
other devices on the DeviceNet network.
Usage
The baud rate is the signalling speed of the communication, and determines the maximum
speed of the data transfer in serial channels. The higher the baud rate is, the faster the
communication can be.
DeviceNet Communication Speed is a DeviceNet specific parameter that is only available for
Prerequisites
Limitations
When using DeviceNet Communication Speed, all devices on the same physical network must
use the same baud rate.
Default value
Allowed values
Allowed values are 125, 250, and 500, specifying the baud rate in Kbps (kilobits per second).
4 System parameters
4.3.1. DeviceNet Address
4.3 Type Unit
4.3.1. DeviceNet Address
Parent
DeviceNet Address belongs to the type Unit, in the topic I/O.
Cfg name
DN_Address
Description
DeviceNet Address specifies the address that the I/O unit is assumed to be using on the
network, and which the master should try to setup a connection against.
Usage
DeviceNet Address is a DeviceNet specific parameter that is only available for DeviceNet
units.
Prerequisites
Limitations
There can be no sharing of addresses on the DeviceNet network when other than the internal
DeviceNet slave and the master are on the same board. All addresses on a DeviceNet network
must be unique, the only exception is that the master and the internal DeviceNet slave share
the same address.
Default value

Allowed values
4 System parameters
4.4.1. Vendor ID
4.4 Type Unit Type
4.4.1. Vendor ID
Parent
Vendor ID belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_VendorId
Description
Vendor ID is used as an identification of the I/O unit to secure communication to the correct
type of device.
Usage
The value of Vendor ID can either be found in the Electronic Data Sheet (EDS) for the unit
(called VendCode in EDS file), or by using the generic unit type (DN_GENERIC).
Vendor ID is a DeviceNet specific parameter that is only available for DeviceNet unit types.
Prerequisites
Default value
Allowed values
Additional information
The I/O unit vendor number is assigned by Open DeviceNet Vendor Associations (ODVA) to
the vendor of the specific I/O unit.
4 System parameters
4.4.2. Product Code
4.4.2. Product Code
Parent
Product Code belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_ProductCode
Description
Product Code is used as an identification of the I/O unit to secure communication to the
correct device.
Usage
The value of Product Code can either be found in Electronic Data Sheet (EDS) for the unit
(called ProdCode in EDS file), or by using the generic unit type (DN_GENERIC).
Product Code is a DeviceNet specific parameter that is only available for DeviceNet unit
types.
Prerequisites
Default value
Default value is 0.
Allowed values
The I/O unit product code is defined by the vendor of the unit and shall be unique for the
actual product type.
4 System parameters
4.4.3. Device Type
4.4.3. Device Type
Parent
Device Type belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_DeviceType
Description
The parameter Device Type specifies the device type of this I/O unit as defined by the Open
DeviceNet Vendor Association.
Usage
This parameter is used as an identification of the I/O unit to secure communication to the
correct device.
The value of this parameter can either be found in the Electronic Data Sheet (EDS) for the
unit (called ProdType in EDS file), or by using the generic unit type (DN_GENERIC).
Device Type is a DeviceNet specific parameter that is only available for DeviceNet unit types.
Prerequisites
Default value
Allowed values
4 System parameters
4.4.4. Major Revision
4.4.4. Major Revision
Parent
Major Revision belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_MajorRev
Description
Major Revision is only used as information and is the major part of the software revision on
the I/O unit.
Usage
The value of Major Revision can be found in the Electronic Data Sheet (EDS) for the unit
(called MajRev in EDS file).
Major Revision is a DeviceNet specific parameter that is only available for DeviceNet unit
types.
Prerequisites
Default value
Allowed values
4 System parameters
4.4.5. Minor Revision
4.4.5. Minor Revision
Parent
Minor Revision belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_MinorRev
Description
Minor Revision is only used as information and is the minor part of the software revision of
the I/O unit.
Usage
The value of this parameter can be found in the Electronic Data Sheet (EDS) for the unit
(called MinRev in EDS file).
Minor Revision is a DeviceNet specific parameter that is only available for DeviceNet unit
types.
Prerequisites
Default value
Allowed values
4 System parameters
4.4.6. Production Inhibit Time
4.4.6. Production Inhibit Time
Parent
Production Inhibit Time belongs to the type Unit Type, in the topicI/O.
Cfg name
DN_ProdInhibitTime
Description
Production Inhibit Time specifies the minimum time, expressed in milliseconds, between
network messages sent by the unit.
Usage
Production Inhibit Time is used to control the minimum time between transmissions from the
I/O unit in order to prevent overloading of the DeviceNet network.
Production Inhibit Time is a DeviceNet specific parameter that is only available for
This parameter is only applicable when connection type is set to Change-Of-State (COS)
connection or Change-Of-State with acknowledge suppression.
Prerequisites
Limitations
Maximum and minimum values might be constrained by the unit.
This parameter is not applicable when connection type is set to polled or strobe connection.
Default value
Allowed values © Copyright 2004-2007 ABB. All rights reserved.

4 System parameters
4.4.7. Explicit Messaging
4.4.7. Explicit Messaging
Parent
Explicit Messaging belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_ExplicitMsgEnabled
Description
Explicit Messaging enables DeviceNet explicit connection to the I/O unit.
Usage
Explicit Messaging is used for a Fieldbus Command Interface (FCI) and CIP routing, and
must then be set to Enabled.
Explicit Messaging is a DeviceNet specific parameter that is only available for DeviceNet
unit types.
Prerequisites
Limitations
The maximum size of Explicit Messaging is 100 bytes, including service, path, and other
header information.
Default value
The default value is Disabled.
Allowed values
Enabled and Disabled.
Related information
Service on page 61.
Path on page 59.
4 System parameters
4.4.8. Connection 1 Type
4.4.8. Connection 1 Type
Parent
Connection 1 Type belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_C1Type
Description
Connection 1 Type specifies the type of the first connection that should be established to the
unit.
Usage
Connection 1 Type is used to define the communication scheme used towards the I/O unit.
The different connection types are described in the ODVA DeviceNet specification (Open
DeviceNet Vendor Associations).
The type of connection supported by the I/O unit can either be found in the [IO_Info] section
of the Electronic Data Sheet (EDS) for the unit, or by using the generic unit type
(DN_GENERIC).
Connection 1 Type is a DeviceNet specific parameter that is only available for DeviceNet unit
types.
Prerequisites
Limitations
All connection types may not be supported by unit.
Default value
The default value is Polled connection.
Allowed values
Allowed values are:
• Polled connection
• Strobe connection
• Change-Of-State (COS) connection
• Cyclic connection
• Change-Of-State with acknowledge suppression
• Cyclic with acknowledge suppression
4 System parameters
4.4.9. Connection 1 Interval
4.4.9. Connection 1 Interval
Parent
Connection 1 Interval belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_C1Interval
Description
Connection 1 Interval defines the cyclicity of the communication over the first connection.
Usage
Connection 1 Interval is used to optimize network bandwidth and I/O update rates.
Connection 1 Interval is a DeviceNet specific parameter that is only available for DeviceNet
unit types.
Prerequisites
Limitations
Maximum and minimum values might be constrained by the unit.
Default value
Allowed values
Allowed values are the integers 0-65535, specifying the time in milliseconds.
4 System parameters
4.4.10. Connection 1 Output Size
4.4.10. Connection 1 Output Size
Parent
Connection 1 Output Size belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_C1OutputSize
Description
Connection 1 Output Size defines the data size that is transmitted to the unit over the first
connection.
Usage
The value of Connection 1 Output Size can either be found in the [IO_Info] section of the
Electronic Data Sheet (EDS) for the unit, or by using the generic unit type (DN_GENERIC).
Connection 1 Output Size is a DeviceNet specific parameter that is only available for
Prerequisites
Limitations
A limitation is the maximum unit size for the Unit Type.
Default value
Default value is 0.
Allowed values
Allowed values are the integers 0-64, specifying the data size in bytes.
For units that can give the unit size itself by an explicit message, the value -1 is also allowed.
4 System parameters
4.4.11. Connection 1 Input Size
4.4.11. Connection 1 Input Size
Parent
Connection 1 Input Size belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_C1InputSize
Description
Connection 1 Input Size defines the data size received from the unit over the first connection.
Usage
The value of Connection 1 Input Size can either be found in the [IO_Info] section of the
Electronic Data Sheet (EDS) for the unit, or by using the generic unit type (DN_GENERIC).
Connection 1 Input Size is a DeviceNet specific parameter that is only available for
Prerequisites
Limitations
A limitation is the maximum unit size for the Unit Type.
Default value
Allowed values
Allowed values are the integers 0-64, specifying the data size in bytes.
For units that can give the unit size itself by an explicit message, the value -1 is also allowed.
4 System parameters
4.4.12. Quick Connect
4.4.12. Quick Connect
Parent
Quick Connect belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_QuickConnectEnabled
Description
The Quick Connect parameter enables the quick connect option on the master side of a
connection to a unit.
Usage
Quick Connect is used to shorten the time when an I/O unit is enabled from a disabled state.
Quick Connect is a DeviceNet specific parameter that is only available for DeviceNet unit
types.
Prerequisites
Default value
Default value is Disabled.
Allowed values
Enabled or Disabled.
To be able to use this option completely, the I/O unit must support Quick Connect according
to the ODVA DeviceNet Specification.
4 System parameters
4.4.13. Internal Slave
4.4.13. Internal Slave
Parent
Internal Slave belongs to the type Unit Type, in the topic I/O.
Cfg name
InternalSlave
Description
The Internal Slave specifies if the Unit Type is an internal DeviceNet slave or not.
Usage
If the Unit Type should be used as an internal DeviceNet slave, set the parameter to Yes. If the
parameter is set to Yes only the necessary parameters for the internal DeviceNet slave are
shown. When a unit of this Unit Type is added the DeviceNet address does not need to be
specified, the unit automatically receives the master address.
Prerequisites
Default value
The default value is No.
Allowed values
Allowed values are Yes or No.
4 System parameters
4.4.14. Trigger Poll I/O
4.4.14. Trigger Poll I/O
Parent
Trigger Poll I/O belongs to the type Unit Type, in the topic I/O.
Cfg name
DN_TriggerPollDisabled
Description
With the Trigger Poll I/O parameter it is possible to decide if the digital output data from the
IRC5 DeviceNet master should be updated directly or with the poll cycle.
Usage
If the Trigger Poll I/O is enabled (default) the output data is updated directly, even if the unit
uses a polled connection. To prevent this the Trigger Poll I/O can be disabled and the output
data will be updated with the poll cycle (connection interval).
NOTE!
Trigger Poll I/O disabled is normally used together with a polled connection but can also be
used with a change-of-state connection. The output data will then be updated with the poll
cycle (connection interval) and the input data with change of state.
Prerequisites
Default value
The default value is Enabled.
Allowed values
Allowed values are Enabled or Disabled.
4 System parameters
4.5.1. Path
4.5 Type Fieldbus Command Type
4.5.1. Path
Parent
Path belongs to the type Fieldbus Command Type, in the topic I/O.
Cfg name
DN_Path
Description
Path defines the path to DeviceNet object instance or attribute. Information about how to
define this can usually be found in the [param] section of the EDS file.
Usage
Path is used to describe the path to the instance or attribute, the data type identifier and the
data size that are to be affected by the explicit message.
Prerequisites
The system parameter Explicit Messaging (of the type Unit Type) must be enabled. The path
can usually be found in the EDS file for the I/O unit.
Limitations
Supported data type identifiers and their size:
Type/Identifier (hex)/size (hex)
WORD/D2/2
UINT/C7/2
INT/C3/2
BOOL/C1/1
SINT/C2/1
USINT/C6/1
UDINT/C8/4
REAL/CA/4
SHORT_STRING/DA/20
BYTE/D1/1
Default value
The default value is an Empty string.
Allowed values
A string with maximum 30 characters.

4 System parameters
4.5.1. Path
Continued
Related information
Explicit Messaging on page 51.
ODVA DeviceNet Specification 2.0.
Example
6,20 01 24 08 30 01,C6,1
Description of example:
• 6 is the length of the path - that is, the number of hexadecimal figurs until the next
comma.
• Path (20 01 24 08 30 01) is a software description of DeviceNet class, instance and
attribute. A further description can be found in the ODVA DeviceNet Specification
2.0.
• C6 is the hexadecimal value for the data type identifier.
• 1 is the data size - that is, the number of bytes as a hexadecimal value.
4 System parameters
4.5.2. Service
4.5.2. Service
Parent
Service belongs to the type Fieldbus Command Type, in the topic I/O.
Cfg name
DN_Service
Description
Service defines the explicit service that should be performed on DeviceNet object instance or
attribute pointed out in Path.
Usage
Service is used to define the type of action to be used.
Prerequisites
The system parameter Explicit Messaging (of the type Unit Type) must be enabled. The
services supported by the unit can usually be found in the EDS file for the I/O unit.
Default value
Allowed values
Following values are allowed:
• Reset (0x05 or 5 in the configuration file)
• Create (0x08 or 8 in the configuration file)
• Apply_Attributes (0x0D or 13 in the configuration file)
• Set_Attribute_Single (0x0E or 14 in the configuration file)
Related information
Path on page 59.

Explicit Messaging on page 51.
4 System parameters
4.5.2. Service
5 Trouble shooting
5.1. Bus off
5 Trouble shooting
5.1. Bus off
Description
The master/slave channel goes bus off when an excessive number of communication errors
are detected and the CAN chip automatically goes off-line.
An event message will inform the users that bus off has occurred. The master/slave channel
will automatically try to recover from bus off and if succeeded an event message will inform
the user that the master/slave channel has recovered from bus off.
To turn off the automatically bus off recovery you can use the system parameter
Automatically Bus Restart. Refer to Technical reference manual - System parameters.
Consequences
Bus off indicates a serious communication fault such as incorrect baud rate or physical layer
error (short, open etc.).
Possible causes
The symptom is caused by:
• Different baud rates on the master and some I/O units (the I/O units do not support
auto baud rate).
• No or faulty power on the bus.
• Short circut between CAN high and CAN low.
• Cable length on trunk cables and drop cables.
• Faulty terminations.
Recommended actions
In order to remedy the symptom, the following actions are recommended:
Cause Action/Info
Different baud rates on the master and Cycle the power of the units or manually change
some I/O units. (The I/O units do not the baud rate of the units.
support auto baud rate.)
No or faulty power on the bus. Refer to Shield grounding and power on page 20
Cable length on trunk cables and drop Refer to Selecting cables on page 23 or
cables. Repeaters on page 25.
Faulty terminations. Refer to Connection of the DeviceNet bus on
page 21.
NOTE!
If the master/slave channel goes bus off also the I/O unit(s) on the bus can go bus off. The
only way to recover this unit(s) is to cycle the power on the I/O unit (the behaviour may be
different depending on the fabric of the I/O unit).
5 Trouble shooting
5.1. Bus off
6 Boards and units
6.1.1. DeviceNet Bus and I/O board status LED description
6 Boards and units
6.1 General
General
Each of the units connected to the DeviceNet Bus includes LED indicators which indicate the
condition of the unit and the function of the network communication.
LEDs
The LEDs found on the units connected may be divided into two categories.
Common LEDs
The following LEDs can be found on all units:
• MS - Module status
• NS - Network status
Specific LEDs
Certain units also include the following LEDs:
• DeviceNet Tx - DeviceNet network transmit
• DeviceNet Rx - DeviceNet network receive
MS - Module status
This bicolor (green/red) LED indicates the status of the device. It indicates whether or not the
device has power and is operating properly. The LED is controlled by software. The table
below shows the different states of the MS LED.
LED color Description Remedy/cause

OFF No power applied to the device. Check power supply.

GREEN steady Device is operating in a normal If no light, check other LED
condition. modes.
GREEN flashing Device needs commissioning due to Check system parameters.
missing, incomplete or incorrect Check messages.
configuration. The device may be in
the stand-by state.
RED flashing Recoverable minor fault. Check messages.
RED steady The device has an unrecoverable Device may need replacing.
fault.
RED/GREEN flashing The device is running self test. If flashing for more than a few
seconds, check hardware.

6 Boards and units
Continued
NS - Network status
This bicolor (green/red) LED indicates the status of the communication link. The LED is
controlled by software. The table below shows the different states of the NS LED.

OFF Device has no power or is not online. Check status of MS LED.
The device has not completed the Check power to affected
Dup_MAC_ID test yet. module.
GREEN steady The device is online and has If no light, check other LED
connection in the established state. modes.
For a group 2 device only: the device
is allocated to a master.
For a UCMM capable device: the
device has one or more established
connections.
GREEN flashing Device is online, but has no Check that other nodes in the
connections in the established state. network are operative.
The device has passed the Check parameter to see
Dup_MAC_ID test, is online, but has whether module has correct ID.
no established connections to other
nodes.
For a group 2 device only: the device
is not allocated to a master.
For a UCMM capable device: the
device has no established connec-
tions.
RED flashing One or more I/O connections are in Check system messages.
the time-out state.
RED steady Failed communication device. The Check system messages and
device has detected an error parameters.
rendering it incapable of communi- Refer to Bus off on page 63.
cating on the network.
(Duplicate MAC_ID, or Bus-off).
DeviceNet Tx - DeviceNet network transmit © Copyright 2004-2007 ABB. All rights reserved.
The following table shows the different states of the DeviceNet Tx LED.
GREEN steady Physically connected to the If no light when transmission is
DeviceNet Tx line. expected, check error
messages.
Check system boards in rack.
GREEN flashing Flashes when the CPU is receiving
data on the DeviceNet bus.

6 Boards and units
Continued
DeviceNet Rx - DeviceNet network receive

The following table shows the different states of the DeviceNet Rx LED.
GREEN steady Physically connected to the If no light, check network and
DeviceNet Rx line. connections.
GREEN flashing Flashes when the CPU is trans-
mitting data on the DeviceNet
bus.
6 Boards and units
6.1.2. DeviceNet Bus status LEDs at power-up
6.1.2. DeviceNet Bus status LEDs at power-up
Process
The system performs a test of the MS and NS LEDs during startup. The purpose of this test
is to check that all LEDs are working properly. The test runs as follows:
Order LED action

1 NS LED is switched Off.
2 MS LED is switched On green for approx. 0.25 seconds.
3 MS LED is switched On red for approx. 0.25 seconds.
4 MS LED is switched On green.
5 NS LED is switched On green for approx. 0.25 seconds.
6 NS LED is switched On red for approx. 0.25 seconds.
7 NS LED is switched On green.
Additional LEDs
If a device has other LEDs, each LED is tested in sequence.
6 Boards and units
6.1.3. External I/O units
6.1.3. External I/O units
General
Up to 20 units may be connected to the same controller.
Requirements
Description Data/value More information

The maximum cable length between 100 m Selecting cables on page
controller and external I/O unit. 23.
Controller placement on cable chain. At one end or anywhere
between the ends.
Power supply to I/O units. 24 VDC
Function of I/O units. Section 5.2 Unit descrip-
tions.
Termination of DeviceNet bus. 121 ohm resistor Termination resistors in
DeviceNet bus on page
22.
6 Boards and units
6.1.4. Coil neutralization
6.1.4. Coil neutralization
External units
External relay coils, solenoids, and other units that will be connected to the controller must
be neutralized. The figure below illustrates how this can be done.
NOTE!
The turn-off time for DC relays increases after neutralization, especially if a diode is
connected across the coil. Varistors give shorter turn-off times. Neutralizing the coils
lengthens the life of the switches that control them.
Clamping with a diode

The diode should be dimensioned for the same current as the relay coil, and a voltage of twice
the supply voltage.
xx0100000163
Clamping with a varistor

The varistor should be dimensioned for the same current as the relay coil, and a voltage of
twice the supply voltage.
xx0100000164
Clamping with an RC circuit

R 100 ohm, 1W C 0.1 - 1 mF.
>500 V max. voltage, 125 V nominal voltage.
xx0100000165
6 Boards and units
6.1.5. Setting DeviceNet bus ID
Description
Each I/O unit is given a unique address (ID).
How to set the ID

The connector contains address pins and can be keyed as shown in the figure below. When
all terminals are unconnected the highest address is obtained - that is, 63. When all terminals
are connected to 0 V, the address would be 0.
To obtain address 10: Cut address pins 2 and 8 (see figure below!)
To obtain address 25: Cut address pins 1, 8 and 16
xx0100000245
A Connector X5
B Address pins
C Address key
Connector X5
Connector X5 is a DeviceNet connector. The following table shows the connections to
connector X5:
Signal name X5 pin

1 Supply voltage GND - Black
2 CAN signal low - Blue
3 Shield
4 CAN signal high - White
5 Supply voltage 24 VDC - Red
6 Logic GND
7 Board ID bit 0 (LSB)
8 Board ID bit 1
9 Board ID bit 2

6 Boards and units
Continued
Signal name X5 pin

10 Board ID bit 3
11 Board ID bit 4
12 Board ID bit 5 (MSB)
6 Boards and units
6.2.1. Introduction
6.2 Unit descriptions
6.2.1. Introduction
Overview
This section includes descriptions of the different I/O units that support DeviceNet
communication. The following units are described:
Board
Name of unit Type of unit Article number
designation
DSQC 651 AD combi I/O Distributed I/O unit 3HAC025784-001
DSQC 652 Digital I/O Distributed I/O unit 3HAC025917-001
DSQC 653 Digital I/O with relay outputs Distributed I/O unit 3HAC025918-001
DSQC 355A Analog I/O Distributed I/O unit 3HNE00554-1
DSQC 350A DeviceNet/AllenBradley Gateway unit 3HNE00025-1
remote I/O
DSQC 351A DeviceNet/INTERBUS Gateway unit 3HNE00006-1
DSQC 352A DeviceNet/PROFIBUS-DP Gateway unit 3HNE00009-1
DSQC 378A DeviceNet/CCLink Gateway unit 3HNE00421-1
DSQC 377A Queue tracking Encoder interface unit 3HNE01586-1
6 Boards and units
6.2.2. DSQC 651, AD combi I/O
Description
The DSQC 651 is a circuit board normally mounted inside the robot controller. As an option,
it may also be mounted in an external I/O module.
The combi I/O unit handles digital and analog communication between the robot system and
any external systems.
Illustration
The figure below shows the DSQC 651 unit:
xx0600002853

6 Boards and units
Continued
Parts
The table below refers to the illustration in section Illustration on page 74.
Item Description
A Status LEDs
X1 Digital outputs
See Connector X1 on page 76 for connection table!
X3 Digital inputs
X5 DeviceNet connector
See Connector X5 on page 77!
X6 Analog outputs
Facts, DSQC 651

This section specifies a number of facts applicable to the DSQC 651. Unless stated otherwise,
the data applies to the standard version.
Technical data
No. of digital inputs 8
No. of digital outputs 8
No. of analog outputs 2 (galvanically isolated from the controller electron-
ics)
0-10 V, 12 bit unsigned encoding
Supply voltage 24 VDC
Power supply, digital and analog I/O Integrated power supply in controller.
Separate 24 VDC power, supplied by customer in
non-ABB external I/O unit.
SW connections Support for the following connections:
• Polled
• Change-Of-State
• Change-Of-State with acknowledge

suppression
• Cyclic
For descriptions of the different types of I/O connec-
tions, see I/O messages - connection types on page
12.

6 Boards and units
Continued
Baud rate Autodetect; the unit will detect the baud rate automat-
ically.
NOTE!
When the master baud rate is changed disconnect
the power to the unit(s) before the system is restarted,
reconnect the power when the master is up and
running.
This is required for the unit(s) to be able to establish
a new connection with the master.
Unit setup
The unit must be given an address, and setup parameters must be entered into the system.
Connector X1
If supervision of the supply voltage is required, a bridge connection can be made to an
optional digital input. This also requires the particular unit to have a separate power supply,
in order to be able to monitor the regular power supply voltage.
The supervision instruction must be written in the RAPID program.
xx0200000264
The table below shows the connections to connector X1:
Unit function Signal name X1 pin

Optically isolated output Out ch 1 1

Optically isolated output 0 V for outputs 9

6 Boards and units
Continued
Connector X3
xx0200000264

Optically isolated input In ch 1 1
Optically isolated input 0 V for inputs 9
Optically isolated input Not used 10
The input current is 5.5 mA (at 24 V) on the digital inputs. A capacitor connected to ground,
to prevent disturbances, causes a short rush of current when setting the input.
When connecting outputs, sensitive to pre-oscillation current, a series resistor (100 Ohms)
may be used.
Connector X5
xx0100000244
Connector X5 is a DeviceNet connector specified in section Setting DeviceNet bus ID on

page 71.
Connector X6
xx0200000265
Signal name X6 pin Explanation

- 1 No connection
- 2 No connection
- 3 No connection
0 VA 4 0 V for Out channels 1-2
AN_OCH1 5 Out channels 1
AN_OCH2 6 Out channels 2

6 Boards and units
Continued
LEDs
The significance of the LEDs are specified in section DeviceNet Bus and I/O board status
LED description on page 65.
Input map
The figure below shows the digital input mapping.
xx0300000613
Output map
The figure below shows the analog and digital output mapping.
NOTE!
Pay attention to the order of the bits for the analog signals.

xx0300000532
LSB The least significant bit of the binary number representing the analog
signal.
MSB The most significant bit of the binary number representing the analog
signal.

6 Boards and units
Continued
Numerical format
The numerical representation of the values are described in the table below:
Signal Analog physical value Hexadecimal number Bit value

AO 1-AO 2 +10 V 0xFFFF MaxBitVal = 65535
AO 1-AO 2 +5 V 0x7FFF
AO 1-AO 2 0V 0x0 MinBitVal = 0
The table shows the physical type of the signals, resolution etc.
Signal Type Range Resolution Encoding type

AO 1 Voltage 0 V .. +10 V 12 bit Unsigned
AO 2 Voltage 0 V .. +10 V 12 bit Unsigned
6 Boards and units
6.2.3. DSQC 652, Digital I/O
Description
The unit handles digital input and output signals between the robot system and any external
systems.
Illustration
The figure below shows the DSQC 652 board:
xx0600002855 © Copyright 2004-2007 ABB. All rights reserved.
Parts
Item Description
A Status LEDs
X1 Digital outputs
See section Connector X1 on page 82 for connection table!
X2 Digital outputs
See Connector X2 on page 82for connection table!
X3 Digital inputs
X4 Digital inputs

6 Boards and units
Continued
Item Description
Facts, DSQC 652

Technical data
No. of inputs 16
No. of outputs 16
Supply source 24 V I/O or separate external supply
• Polled
• Change-Of-State
• Cyclic
For descriptions of the different types of I/O connections, see
I/O messages - connection types on page 12.
Baudrate Autodetect; the unit will detect the baud rate automatically.
NOTE!
When the master baud rate is changed disconnect the power
to the unit(s) before the system is restarted, reconnect the
power when the master is up and running.
This is required for the unit(s) to be able to establish a new
connection with the master.
Unit setup

6 Boards and units
Continued
Connector X1
optional digital input. The supervision instruction must be written in the RAPID program.
xx0200000264

Connector X2
optional digital input. The supervision instruction must be written in the RAPID program.
xx0200000264



6 Boards and units
Continued
Connector X3
xx0200000264

may be used.
Connector X4
xx0200000264


When connecting outputs, sensitive to pre-oscillation current, a series resistor (100 ohms)
may be used.
6 Boards and units
Continued
Connector X5
xx0100000244

page 71.
LEDs
Input map
xx0300000613
Output map
The figure below shows the digital output mapping.
en0400000716
6 Boards and units
6.2.4. DSQC 653, Digital I/O with relay outputs
Description
The unit handles input and output signals between the robot system and any external systems
through relay outputs and digital inputs.
Illustration
The figure below shows the DSQC 653 board:
xx0600002857
Parts
Item Description
A Status LEDs
X1 Relay outputs
See section Connector X1 on page 87 for connection table!
X3 Digital inputs
See section Connector X3 on page 88for connection table!
See section Connector X5 on page 89!

6 Boards and units
Continued
Facts, DSQC 653

Technical data
No. of digital inputs 8
No. of relay outputs 8
Digital inputs Rated voltage: 24 VDC
Input voltage range: “1” 15 to 35 VDC, “0” -35 to 5 VDC
Digital outputs Rated voltage: 24 VDC
Max output current: 2A/channel
Supply source 24 V I/O or separate external supply
• Polled
• Change-Of-State
• Cyclic
For descriptions of the different types of I/O connections, see I/O
messages - connection types on page 12.
Baud rate Autodetect; the unit will detect the baud rate automatically.
NOTE!
When the master baud rate is changed disconnect the power to the
unit(s) before the system is restarted, reconnect the power when
the master is up and running.
This is required for the unit(s) to be able to establish a new
connection with the master.

Unit setup

6 Boards and units
Continued
Connecting digital outputs and digital inputs

The following illustration shows how to connect the relay outputs for the connector X1. When
a bit is set to 1, the relay output will be activated.
en0500001565
The following illustration shows how to connect the digital inputs for the connector X3.
en0500001566
Connector X1
xx0100000235
Signal name X1 pin Function

Out ch 1a 1 Contact, relay 1
Out ch 1b 2 Contact, relay 1

6 Boards and units
Continued

Connector X3
xx0100000235
Signal name X3 pin

In ch 1 1
In ch 2 2
In ch 3 3
In ch 4 4
In ch 5 5
In ch 6 6
In ch 7 7
In ch 8 8
0 v for inputs 9
Not used 10

Not used 11
Not used 12
Not used 13
Not used 14
Not used 15
Not used 16
may be used.

6 Boards and units
Continued
Connector X5
xx0100000244

page 71.
LEDs
Input map
xx0300000613
Output map
en0400000716
6 Boards and units
6.2.5. DSQC 355A, Analog I/O
Description
The DSQC 355A is a circuit board normally mounted inside the control module. As an option,
The unit handles interface between the robot system and any external systems through analog
input and output signals.
Illustration
The figure below shows the DSQC 355A board:
xx0100000238
Parts
The following table refers to the illustration in section Illustration on page 90.
Item Description © Copyright 2004-2007 ABB. All rights reserved.
X3 Back-up feed supply

See section Connector X3 on page 91 for connection tables!
X7 Analog outputs
X8 Analog inputs

6 Boards and units
Continued
Facts, DSQC 355A

This section specifies a number of facts applicable to the DSQC 355A. Unless stated
otherwise, the data applies to the standard version.
Technical data
• Polled
• Change-Of-State
Unit ID and setup

The unit must be given an ID address, and setup parameters must be entered into the system.
Connector X3
xx0100000221
The following table shows the connections to connector X3:

0 VDC 1 Supply voltage GND
NC 2 Not connected
GND 3 Ground connection
NC 4 Not connected
+ 24 VDC 5 Supply voltage + 24 VDC
Connector X5
xx0100000244
Connector X5 is a DeviceNet connector further described in section Setting DeviceNet bus ID

on page 71.

6 Boards and units
Continued
Connector X7
xx0100000236

ANOUT_1 1 Analog output 1, -10 V/+10 V
ANOUT_4 4 Analog output 4, 4-20 mA
Not used 5
Not used 6
Not used 7
Not used 8
Not used 9
Not used 10
Not used 11
Not used 12
Not used 13
Not used 14
Not used 15
Not used 16

Not used 17
Not used 18
GND 19 Analog output 1, 0 V
GND 23
GND 24
NOTE!
The load on analog outputs on current mode must always be between 500-1000 ohm.

6 Boards and units
Continued
Connector X8
xx0100000237

ANIN_1 1 Analog input 1, -10 V/+10 V
Not used 5
Not used 6
Not used 7
Not used 8
Not used 9
Not used 10
Not used 11
Not used 12
Not used 13
Not used 14
Not used 15
Not used 16
+24 V out 17 +24 VDC supply
GND 25 Analog input 1, 0 V
GND 29
GND 30

6 Boards and units
Continued

GND 31
GND 32
Board specific LEDs

The designations refer to LEDs shown in the figure in section Illustration on page 90.
Designation Color Description

RS232 Rx Green Indicates the state of the RS232 Rx line.
LED is active when receiving data. If there is no
light, check communication line and connections.
RS232 Tx Green Indicates the state of the RS232 Tx line. LED is
active when transceiving data.
If there is no light when transmission is expected,
check error messages. Check also system
boards in rack.
+5VDC / +12VDC / -12VDC Green Indicates that supply voltage is present and at
correct level.
If there is no light, check that voltage is present on
power unit and that power is present in power
connector. If not, check cables and connectors.
If power is applied to the unit but it does not work,
replace the unit.
General LEDs

6 Boards and units
Continued
Input map
The figure below shows the analog input mapping.
NOTE!
en0400000806
signal.
signal.

6 Boards and units
Continued
Output map
The figure below shows the analog output mapping.
NOTE!
en0400000805
signal.
signal.
Numerical format
The numerical representation of the values are described in the table below:
Signal Analog physical value Hexadecimal number Bit value © Copyright 2004-2007 ABB. All rights reserved.
AO 1 - AO 3 +10 V 0x7FFF MaxBitVal = 32767

0V 0x0
-10 V 0x800 MinBitVal = -32768
AO 4 20 mA 0xFFFF MaxBitVal = 65535
4 mA 0x0 MinBitVal = 0
AI 1 - AI 4 +10 V 0x7FFF MaxBitVal = 32767
0V 0x0
-10 V 0x8000 MinBitVal = -32768

6 Boards and units
Continued
The table shows the physical type of the signals, resolution etc.
Signal Type Range Resolution Encoding type

AO 1 Voltage -10 V .. +10 V 12 bit Twos complement
AO 4 Current 4 mA .. 20 mA 12 bit Unsigned
AI 1 Voltage -10 V .. +10 V 16 bit Twos complement
6 Boards and units
6.2.6. DSQC 350A, DeviceNet/Allen Bradley remote I/O gateway
Description
The DSQC 350A is a circuit board normally mounted in the control module. As an option, it
may also be mounted in an external I/O module.
The unit handles input and output signals between the DeviceNet system and the Allen
Bradley system.
Warranty
This product incorporates a communications link which is licensed under patents and
proprietary technology of the Allen-Bradley Company, Inc. The Allen-Bradley Company,
Inc. does not warrant or support this product. All warranty and support services for this
product are the responsibility of and provided by ABB.
Termination
When the robot is last in a RIO loop, the loop must be terminated with a termination resistor
according to Allen-Bradley's specification.
Illustration
xx0100000226 © Copyright 2004-2007 ABB. All rights reserved.
Parts
Item Description
X3 Backup feed supply
X5 DeviceNet and ID connector
X8 RIO in
See section Connector X8 on page 99 for connection
tables!
X9 RIO out
See section Connector X9 on page 100 for connection
tables!

6 Boards and units
Continued
Facts, DSQC 350A

Technical data
No. of digital inputs Unit is programmable for 32, 64, 96 or 128 digital inputs.
No. of digital outputs Unit is programmable for 32, 64, 96 or 128 digital outputs.
• Polled
• Change-Of-State
Baud rate 500 Kbps
Connector X3
xx0100000221

NC 2 Not connected
NC 4 Not connected
Connector X5
xx0100000244

page 71.
Connector X8
xx0400000718

LINE1 (blue) 1 Remote I/O in
LINE2 (clear) 2 Remote I/O in
Shield 3 Remote I/O in
Cabinet ground 4 Remote I/O in
6 Boards and units
Continued
Connector X9
xx0400000718

Blue 1 Remote I/O out
Clear 2 Remote I/O out
Shield 3 Remote I/O out
Cabinet ground 4 Remote I/O out
Board specific LEDs

The figure and table below show the location and significance of the the LEDs on the board.

POWER-24 VDC Green Indicates that a supply voltage is present, and has
a level above 12 VDC.
power unit and in power connector. If not, check
cables and connectors.
replace the unit.
NAC STATUS Green Steady green indicates RIO link in operation.
If there is no light, check network, cables and con-
nections. Also check that PLC is operational.
Flashing green indicates that communication is
established, but the INIT_COMPLETE bit is not set
in NA chip, or configuration, rack size etc. does not
match configuration set in PLC.
If LED keeps flashing continuously, check setup.

General LEDs
Unit size
The table explains the unit size for the input and output units.
Unit size Rack size Number of bits Number of bytes

32+2 DI/32 DO 0 32 4
64+2 DI/64 DO 1 64 8
96+2 DI/96 DO 2 96 12
128+2 DI/128 DO 3 128 16

6 Boards and units
Continued
Input map
en0400000720
m The rack size (in 32 bit intervals) that the unit has been configured to, using
the Fieldbus Command Type RackSize.
RIO Status The status of the remote I/O communication can be monitored using the
signal RIO Status. When RIO Status is set it indicates that the unit is in data
communication with the PLC/master controlling it (the NAC STATUS LED
is steady green).
RIO Comm The status of the remote I/O communication can be monitored using the
signal RIO Comm. When RIO Comm is set it indicates that the RIO com-
munication is "partially up" (the NAC STATUS LED is flashing) - that is, the
PLC is in programming mode.
N.U. Not used. The signal position is reserved for future use and shall not be
used.
The RIO status signals are located at the first bits of the last byte of the input area. For
example, if the RackSize is set to 1 (2 * 32 bit) there are 8 bytes of input data (bit 0-63), and
the signals RIO Command RIO Status are located at bit 64 and bit 65 respectively.
Output map
en0400000719
m The rack size (in 32 bit intervals) that the unit has been configured to, using
the Fieldbus Command Type RackSize.

6 Boards and units
Continued
Fieldbus Command Types

The following table gives necessary data on the Fieldbus Command Types for DeviceNet
communication.
Fieldbus Path
Command (DeviceNet Allowed values Usage
Type parameter)
LinkAddr 6, 20 64 24 0-63 Determines the address of
01 30 01, C6, the DSQC 350A on the RIO
1 connection.
Note! The rack address is
entered in decimal form (0-
63) while AllenBradley use
octal representation (base 8,
range 0-77).
DataRate 6, 20 64 24 0-2 according to: Determines the communica-
01 30 02, C6, 0 = 57.6 kbaud tion speed on the RIO bus.
1 1 = 115.2 kbaud
2 = 230.4 kbaud
StartQ 6, 20 64 24 0-3 according to: Determines the RIO Starting
01 30 03, C6, 0 = First (PLC value 0) Quarter of the unit.
1 1 = Second (PLC value 2)
2 = Third (PLC value 4)
3 = Fourth (PLC value 6)
RackSize 6, 20 64 24 0-3 according to: Determines the size of the
01 30 04, C6, 0 = 1/4 rack (32 DO, 32+2 DI) input and output data areas
1 1 = 1/2 rack (64 DO, 64+2 DI) of the RIO gateway.
2 = 3/4 rack (96 DO, 96+2 DI)
3 = Full rack (128 DO, 128+2 DI)
LastRack 6, 20 64 24 0 and 1 according to: Determines if the unit is the
01 30 05, C6, 0 = No (this is NOT the last rack) last rack on the RIO bus.
1 1 = Yes (this is the last rack)

The data areas of the gateway are "byte-consistent", which means that signals within the same
byte (groups of 8 bits) are handled as one piece and are guaranteed to belong to the same bus-
cycle. Normally this does not cause any problems, but if a signal group has been defined
across the byte boundaries as e.g. a 16 bit group signal this needs to be considered. It is
important to make sure that undesired behaviors are avoided in the case when the group signal
is updated at exactly the same time as the gateway is being polled/scanned by one of the
masters.
The values for the Fieldbus Command Types are stored in flash memory of the gateway
module. Any change of these values requires a reset (or power cycle) of the gateway module
before it actually assumes these new values. By using the standard configuration files for the
gateways, the robot controller will automatically issue a reset command to activate the
modified configuration.

6 Boards and units
6.2.7. DSQC 351A, DeviceNet/INTERBUS gateway
Description
may also be mounted in an external I/O unit.
The unit handles input and output signals between the DeviceNet system and the INTERBUS
system.
Communication concept
The INTERBUS system is able to communicate with a number of external devices,
depending on the number of process words occupied by each unit. The robot controller may
be equipped with several DSQC 351A boards. The INTERBUS inputs and outputs are
accessible in the robot controller as general inputs and outputs.
Following figure is an outline diagram of the communication concept:
xx0100000224
A Master PLC (customer equipment)

B Robot 1 controller, word 1-4
C Robot 2 controller, word 5-8
D Robot 3 controller, word 9-12
E 128 inputs/128 outputs
F 64 inputs/64 outputs
Note! A link is connected between pin 5 and 9 in the plug on the interconnection cable
connected to the OUT connector (connector X21) of each unit. The link informs the
INTERBUS unit that more units are connected further out in the chain. (The last unit does not
have a cable connected and therefore no link.)

6 Boards and units
Continued
Illustration of DSQC 351A

The illustration below shows the DSQC 351A board:
xx0100000225
Parts
The table below refers to Illustration of DSQC 351A on page 104.
Item Description
X20 INTERBUS, input
X21 INTERBUS, output © Copyright 2004-2007 ABB. All rights reserved.
Facts, DSQC 351A

Also see the INTERBUS specification, International Standard DIN 19258.
Technical data
• Polled
• Change-Of-State
Baud rate 500 Kbps

6 Boards and units
Continued
Supply
The INTERBUS gateway must be fed externally to avoid shutting down the INTERBUS net
if a robot cell is switched off. The 24V power supply must be fed from an external power
source and be connected to connector X3.
INTERBUS master setup

The unit must be given an ID address, and setup parameters must be entered into the
INTERBUS master system.
The unit ID to be entered in the INTERBUS master is 3. The length code depends on the
selected data. The width is between 1 and 4 configured by the Fieldbus Command Type,
DataWidth.
Connector X3
xx0100000221

NC 2 Not connected
NC 4 Not connected
Connector X5
xx0100000244

page 71.
Connector X20
xx0100000220

TPDO1 1 Communication line TPDO1
TPDI1 2 Communication line TPDI1
NC 4 Not connected
NC 5 Not connected

6 Boards and units
Continued

TPDO1-N 6 Communication line TPDO1-N
TPDI1-N 7 Communication line TPDI1-N
NC 8 Not connected
NC 9 Not connected
Connector X21
xx0100000220

TPDO2 1 Communication line TPDO2
TPDI2 2 Communication line TPDI2
NC 4 Not connected
+5V 5 + 5 VDC
TPDO2-N 6 Communication line TPDO2-N
TPDI2-N 7 Communication line TPDI2-N
NC 8 Not connected
RBST 9 Synchronization
Note! Pin 5 and pin 9 in X21 must be linked together.
Board specific LEDs

The designations refer to LEDs shown in the figure in section Illustration of DSQC 351A on
page 104.

POWER-24 VDC GREEN Indicates that a supply voltage is present, and has
(upper indicator) a level above 12 VDC.
power module. Check also that power is present in
power connector. If it is not, check cables and
connectors.
If power is applied to unit but unit does not work,
replace unit.
POWER- 5 VDC GREEN Lit when both 5 VDC supplies are within limits, and
(lower indicator) no reset is active.
power module. Check also that power is present in
power connector. If it is not, check cables and
connectors.
If power is applied to unit but unit does not work,
replace unit.

6 Boards and units
Continued

RBDA RED Lit when this INTERBUS station is last in the
INTERBUS network. If it is not, verify the
INTERBUS configuration.
BA GREEN Lit when INTERBUS is active.
If there is no light, check network, nodes and con-
nections.
RC GREEN Lit when INTERBUS communication runs without
errors.
If there is no light, check system messages in
robot and in INTERBUS net.
General LEDs
Input map
en0400000799
m The number of words (16 bit) that the unit has been configured to, using
the Fieldbus Command Type DataWidth.
INTERBUS The status of the INTERBUS communication can be monitored using the
Status signal INTERBUS Status. When INTERBUS Status is set it indicates that
the unit is in data communication with the PLC/master controlling it, i.e. bus
is active (the BA LED is lit).
used.
The INTERBUS Status signal is located in the last bit of the last byte of the input area. For
example, if the DataWidth is set to 4 (words) there are 8 bytes of input data (bit 0-63), and
the INTERBUS Status is located in the last bit of the 9th byte i.e. bit 71.

6 Boards and units
Continued
Output map
en0400000800
m The number of words (16 bit) that the unit has been configured to, using the Fieldbus
Command Type DataWidth.

Following table gives necessary data on the Fieldbus Command Types for DeviceNet
communication.
Fieldbus Path
Type parameter)
DataWidth 6, 20 65 24 01 0-3 according to: Determines the size of the
30 01, C6, 1 0 = 1 word (16 DO, 16+1 DI) input and output data areas of
1 = 2 words (32 DO, 32+1 DI) the INTERBUS gateway.
2 = 3 words (48 DO, 48+1 DI)
3 = 4 words (64 DO, 64+1 DI)
masters.

6 Boards and units
6.2.8. DSQC 352A, DeviceNet/PROFIBUS-DP gateway
Description
may also be mounted in an external I/O unit.
The unit handles input and output signals between the DeviceNet system and the PROFIBUS-
DP system.
The PROFIBUS-DP system is able to communicate with a number of external devices,
depending on the number of process words occupied by each unit. The robot controller may
be equipped with several DSQC 352A boards. The PROFIBUS-DP inputs and outputs are
accessible in the robot controller as general inputs and outputs.
xx0100000222

B Robot 1 controller, word 1-8
C Robot 1 controller, word 9-16
D Robot 2 controller, word 17-24
E 256 inputs/256 outputs
F 128 inputs/128 outputs
Note! The PROFIBUS cable must be terminated in both ends.


6 Boards and units
Continued
Illustration
xx0100000223
Parts
Item Description
X20 PROFIBUS connection

Facts, DSQC 352A

Also see the PROFIBUS-DP specification, International Standard DIN E 19245 part 3.
Technical data
• Polled
• Change-Of-State
Baud rate 500 Kbps

6 Boards and units
Continued
Supply
The PROFIBUS-DP does not need any external power feed, power is supplied via X5.
All the robots cells are connected to the trunk cable via a special D-sub connector which
works as a very short drop cable. Because of this, the PROFIBUS will work correctly even if
a robot cell is turned off.
Unit ID and setup

Connector X3
xx0100000221

NC 2 Not connected
NC 4 Not connected
Connector X5
xx0100000244
Connector X5 is a DeviceNet connector further described in section Setting DeviceNet bus ID

on page 71.
Connector X20
xx0100000220

Shield 1 Cable screen
NC 2 Not connected
RxD/TxD-P 3 Receive/Transmit data P
Control-P 4
+5 VDC 6
NC 7 Not connected
RxD/TxD-N 8 Receive/Transmit data N

6 Boards and units
Continued

NC 9 Not connected
Board specific LEDs

The designations refer to LEDs shown in the figure in section Illustration on page 110.

PROFIBUS Green Lit when the node is communicating with the master.
active If there is no light, check system messages in robot and in
PROFIBUS net.
POWER, 24 VDC Green Indicates that a supply voltage is present, and has a level above
12 VDC.
If there is no light, check that voltage is present in power unit
and in the power connector. If not, check cables and
connectors.
If power is applied to the unit but it does not work, replace the
unit.
General LEDs
Input map
en0400000804
the Fieldbus Command Type MasterInputSize.
PROFIBUS The status of the PROFIBUS communication can be monitored using the
Status signal PROFIBUS Status. When PROFIBUS Status is set it indicate that
the unit is in data communication with the PLC/master controlling it.
used.
The PROFIBUS Status signal is located in the last bit of the last byte of the input area. For
example, if the MasterInputSize is set to 4 (words) there are 8 bytes of input data (bit 0-
63), and the PROFIBUS Status is located in the last bit of the 9th byte i.e. bit 71.

6 Boards and units
Continued
Output map
en0400000912
the Fieldbus Command Type MasterOutputSize.

communication.
Path
Fieldbus Allowed
(DeviceNet Usage
Command Type values
parameter)
MasterInputSize 6, 20 67 24 01 0-8 (words) Determines the size of the input data
30 02, C6,1 area of the gateway module.
The size is expressed in number of
words (16 bit groups), which means that
the maximum size of input data for one
DSQC 352A is 128 bit.
By reducing the size, the allocated
bandwidth decreases and thus the
throughput and performance of the
network increase.
MasterOutputSize 6, 20 67 24 01 0-8 (words) Determines the size of the output data
30 03, C6, 1 area of the gateway module.

The size is expressed in number of
words (16 bit groups), which means that
the maximum size of output data for one
DSQC 352A is 128 bit.
By reducing the size, the allocated
bandwidth decreases and thus the
throughput and performance of the
network increase.
StationAddress 6, 20 67 24 01 2-126 Determines the address of the DSQC
30 04, C6, 1 352A on the PROFIBUS connection.
The value that StationAddress is set
to, is the gateway address found by the
external master (PLC) connected to the
PROFIBUS side of the gateway.

6 Boards and units
Continued
masters.
To configure an external PROFIBUS master (PLC) to communicate with the gateway, a
GSD-file is required. The GSD-file for the DSQC 352A is found on the RobotWare CD-ROM
in following directory:
<CD-drive>:\Utility\fieldbus\PROFIBUS\gsd\abb_0600.gsd

6 Boards and units
6.2.9. DSQC 378A, DeviceNet/CCLink gateway
Description
The DSQC 378A unit offers an interface between the CCLink bus and the DeviceNet bus as
used on the robot system. The unit is regarded as an intelligent device by the CCLink PLC.
The CCLink can communicate with a number of external devices, depending on the number
of stations occupied by each unit. There is a maximum of 64 stations, each capable of up to
32 I/O points and 8 points word data. The units are setup to have between 1 and 4 occupied
stations each. The CCLink unit is connected to the CCLink PLC by a twisted pair cable with
shield.
The CCLink inputs and outputs are accessible in the robot controller as general inputs and
outputs.
xx0400000826

B Robot 1 controller
C Robot 2 controller
D Robot 3 controller
E DSQC 378A controller
F Connector X8 controller
Note! The CCLink cable must be terminated with termination resistors (110 ohm) in both
ends.

6 Boards and units
Continued

xx0400000825
Parts
Item Description
X8 CCLink network connector
Facts, DSQC 378A © Copyright 2004-2007 ABB. All rights reserved.

Technical data
• Polled
• Change-Of-State
Baud rate 500 Kbps
Unit setup

6 Boards and units
Continued
Connector X3
xx0100000221

NC 2 Not connected
NC 4 Not connected
+ 24 VDC 5 Supply voltage +24 VDC
Connector X5
xx0100000244

page 71.
Connector X8
xx0200000265

SLD 1 Shield, connected to power GND/Housing
DA 2 Signal line, A
DG 3 Digital GND, connected to signal GND

DB 4 Signal line, B
NC 5 Not connected
FG 6 Power GND, same as SLD

6 Boards and units
Continued
Board specific LEDs

The designations refer to LEDs shown in the figure in section Illustration of DSQC 378A on
page 116.

POWER-24 VDC Green Indicates that a supply voltage is present, and has a level
above 12 VDC.
If there is no light, check that voltage is present on power
module. Check also that power is present in power
connector. If it is not, check cables and connectors.
If power is applied to unit but unit does not work, replace
unit.
RUN (ON: H output) ON: Receive both refresh and polling signals or just the
refresh signal normally, after joining the network.
See figure below this table.
OFF:
1. Before joining the network.
2. Unable to detect carriers neither for channel 1 or 2.
3. Time out.
4. Resetting hardware.
RDLED (ON: L output) ON: Detecting the carrier for channel 1 or 2. Check cables
and terminator.
OFF:
1. Unable to detect carriers neither for channel 1 or 2.
SDLED (ON: L output) ON: During transmission to During transmission + (0.41
ms * 2(n-1))
n = 1-8
Check setup in both robot controller and PLC.
OFF:
1. Other than listed under ON.

ERRL (ON: L output) ON:
1. CRC error. Check setup in both robot controller and
PLC.
2. Switch setting error during cancellation of reset (0,
65, or greater is set including the number of
occupied stations).
3. Baud rate switch setting error during cancellation of
reset (5 or greater).
OFF:
1. Normal communication.
BLINKING: The switch setting has been changed from the
setting at the reset cancellation (blinks for 0.4 sec.).

6 Boards and units
Continued
The following figure describes the LED sequences.

Note! Read the figure line by line. The Operation column describes the operation status
depending on the status of the four LEDs.
en0400000827
General LEDs

6 Boards and units
Continued
Input map
en0400000823
m The size in bytes (8 bit) that the unit has been configured to, using the
Fieldbus Command Types OccStat and BasicIO. See table in section
Fieldbus Command Types on page 121.
CCLink Status The status of the CCLink communication can be monitored using the signal
CCLink Status. When CCLink Status is set it indicates that the CCLink
communication is OK.
used.
The CCLink Status signal is located at the last bit of the last byte of the input area. For
example, if OccStat is set to 2 and BasicIO is set to 0 there are 6 bytes of input data (bit 0-
47), and the CCLink Status is located in the last bit of the 7th byte i.e. bit 55.
Output map
en0400000824
m The size in bytes (8 bit) that the unit has been configured to, using the
Fieldbus Command Types OccStat and BasicIO. See table in section
Fieldbus Command Types on page 121.

6 Boards and units
Continued

communication.
Fieldbus Path
Type parameter)
StationNo 6, 20 68 24 1-64 Determines the address of the
01 30 01, C6, DSQC 378A on the CCLink
1 connection.
BaudRate 6, 20 68 24 0-4 according to: Determines the communication
01 30 02, C6, 0 = 156 kbps speed on the CCLink bus.
1 1 = 625 kbps
2 = 2.5 Mbps
3 = 5 Mbps
4 = 10 Mbps
OccStat 6, 20 68 24 1-4 according to: Occupied stations. Determines the
01 30 03, C6, 1 = 1 occupied station size of the input and output data
1 2 = 2 occupied stations areas of the CCLink module. The
size, expressed in bits and bytes,
3 = 3 occupied stations
also depends on the value of
4 = 4 occupied stations BasicIO. See table in section Size
of input/output data areas on page
121.
BasicIO 6, 20 68 24 0-1 according to: Determines the type of I/O data to
01 30 04, C6, 0 = Bit I/O only be exchanged with the CCLink
1 1 = Bit I/O and word I/O master. This also affects the size of
the input and output data areas of
the CCLink module. The size,
expressed in bits and bytes, also
depends on the value of OccStat.
See table in section Size of input/
output data areas on page 121.
Size of input/output data areas

The size of the input/output data areas expressed in bits and bytes are determined by the
values of the Fieldbus Command Types OccStat and BasicIO according to following table:
No. of bits No. of bytes No. of bits No. of bytes

Value of OccStat when when when when
BasicIO = 0 BasicIO = 0 BasicIO = 1 BasicIO = 1
1 16 2 80 10
2 48 6 176 22
3 80 10 272 34
4 112 14 368 46

6 Boards and units
Continued
byte (group of 8 bits) are handled as one piece and are guaranteed to belong to the same bus-
masters.

6 Boards and units
6.2.10. DSQC 377A, Queue tracking unit
Description
The encoder unit DSQC 377A provides connection for one encoder and one digital input
(synchronization switch), and includes queue tracking functions.
Usage
The encoder unit is normally used for installation on a conveyor to enable the robot programs
to synchronize to the motion (position) of the conveyor (conveyor tracking).
The digital input is used for synchronization switch (also called sync signal), which means
conveyor synchronization point.

xx0400000751
Parts
Item Description
See section Connector X3 on page 125for connection tables!
X20 Conveyor connection

6 Boards and units
Continued
Facts, DSQC 377A

Technical data
No. of encoder inputs 1
No. of digital inputs 1 (24 VDC)
Supply source 24 V I/O or external supply
SW connections Support for the polled connection.
For descriptions of the different types of I/O
connections, see I/O messages - connection
types on page 12.
Baud rate 500 Kbps
Also see Product specification, IRC5 with FlexPendant.
Encoder connections
The wiring diagram in the figure below shows how to connect the encoder and sync signal
switch to the encoder unit. As can be seen from the illustration, the encoder is supplied with
24 VDC and 0 V. The encoder has two channels. The main unit uses quadrature decoding to
compute position and direction information.
xx0100000234
AA 24 V I/O or external supply

AB 0 V I/O or external supply
AC Encoder

6 Boards and units
Continued
AD Sync switch
AE 10-16 not used
AF Encoder interface unit
AG Galvanic isolation
Connector X3
Connector1-5

NC 2 Not connected
NC 4 Not connected
Connector X5
xx0100000244

page 71.
Connector X20
xx0100000235
X20 is the encoder and digital input connector.

Signal name X20 pin

24 VDC supply 1
0V 2
Encoder 1 - 24VDC 3
Encoder 1 - 0V 4
Encoder 1 - Phase A 5
Encoder 1 - Phase B 6
Digital input 1 - 24 VDC 7
Digital input 1 - 0 V 8
Digital input 1 - Signal 9
Not used 10
Not used 11

6 Boards and units
Continued
Signal name X20 pin

Not used 12
Not used 13
Not used 14
Not used 15
Not used 16
Board specific LEDs

The table below shows the significance of the LEDs on the board. For location of the LEDs
see Illustration of DSQC 377A on page 123.

POWER, 24 VDC Green Indicates that a supply voltage is present, and has a
level above 12 VDC.
power unit and in connector X20. If not, check cables
and connectors.
replace the unit.
NS/MS Green/red Network and module status LEDs. See section
DeviceNet Bus and I/O board status LED description
on page 65.
CAN Tx/CAN Rx Green/red See section DeviceNet Bus and I/O board status LED
description on page 65.
ENC 1A/1B Green Indicates phase 1 and 2 from encoder. Flashes at
each Encoder pulse. At frequencies higher than a few
Hz, flashing can no longer be observed (light will
appear weaker).
If there is no light, there is an error due to one or more
of the following reasons:
• Faulty power supply for input circuit (internal or
external).
• Defective input circuit on board.
• Short circuit or broken wire in external wiring or
connectors.
• Internal error in unit.
Constant light indicates constant high level on input
and vice versa.
No light on one LED indicates fault in one encoder
phase.
DIGIN1 Green Lit when digital input is active.
The input is used for external start signal/conveyor
synchronization point.
If there is no light, there is an error due to one or more
of the following reasons:
• Faulty power supply for input circuit (internal or
external).
• Faulty limit switch, photocell etc.
• Short circuit or broken wire in external wiring or
connectors.
• Defective input circuit on board.

6 Boards and units
Continued

ENC 2A/2B Not used.
DIGIN2 Not used.
Input map
The figure below shows the input mapping.
Note! Pay attention to the order of the bits for the analog signals.
en0400000816

6 Boards and units
Continued
Note!
The signals CntFromEnc1, CntFromEnc2, and ScaleEncPulse are dependent on the signal
PosInJobQ (bit 42 in the output map). DSQC377-mode is obtained by setting the output
signal to 1, and DSQC354-mode is obtained by setting the output signal to 0.
Generally PosInJobQ concerns only the queue tracking mode. All signals on the 377 are
available even in DSQC354-mode (c1PosInJobQ=0). The only thing c1PosInJObQ disables,
is that the object position is not sent to the main controller.
Following table specifies the input signals.
Signal name Type Bit Description

Position AI 0-31 Position in meters of the first object in the queue.
Accuracy: 0.1 mm
Speed AI 32-63 Speed of the conveyor in m/s.
Resolution: 10 µm/s
ObjectsInQ GI 64-71 Number of objects in queue (0-255).
Objects that have entered the queue (passed the
sync switch) but have not left the queue (have
become connected or gone outside the start
window).
CntFromEnc1 GI 72-87 Counter value from encoder to controller (Low Word).
The bit group is valid for DSQC377-mode, i.e. when
PosInJobQ is set to 1.
CntFromEnc2 GI 88-103 Counter value from encoder to controller (High
Word).
The bit group is valid for DSQC377-mode, i.e. when
Connected DI 104 Set when an object is being tracked.
NullSpeed DI 105 Set when the conveyor is stopped.
Ready DI 106 Internal handshake signal (toggled).
PassStw DI 107 Set when an object has gone outside the start
window or has fallen off the conveyor.

NewObjStrobe DI 108 New position from the encoder node to enter the job
queue.
The bit is valid for DSQC377-mode, i.e. when
EncSelected DI 109 Indicates which encoder is active.
0 = EncA (must be 0)
EncAFault DI 110 Encoder A is faulty.
N.U. 111 Not used.
Simulating DI 112 Module is in simulated mode, i.e. Speed and
Position are simulated rather than taken from the
actual encoder.

6 Boards and units
Continued

DirOfTravel DI 113 Indicates the direction of the conveyor.
0 = Backward
1 = Forward
ScaleEncPulse DI 114 The encoder pulse scaled down by the factor given
by the command ScalingFactor.
PowerUpStatus DI 115 Indicates how the last shutdown was made.
0 = Abnormal
1 = Normal
N.U. 116-119 Not used.
TimeStamp GI 120-151 Holds the time when following signals were last
sampled:
• Position
• Speed
• Connected
• NullSpeed
Output map
The figure below shows the output signals mapping.
en0400000817
Note!
The signals CntToEnc1, CntToEnc2, and CntToEncStr are dependent on the signal PosInJobQ
(bit 42 in the output map). DSQC377-mode is obtained by setting the signal to 1, and
DSQC354-mode is obtained by setting the signal to 0.
Generally PosInJobQ concerns only the queue tracking mode. All signals on the 377 are
available even in DSQC-354 mode (c1PosInJobQ=0). The only thing c1PosInJObQ disables,
is that the object position is not sent to the main controller.
Following table specifies the output signals.

WaitWObj DO 0 Set when the robot is waiting for an object to enter
the start window.
DropWObj DO 1 Drop and disconnect the currently tracked object.
The object is removed from the queue.

Continued

Rem1PObj DO 2 Remove first pending object from the queue. (If an
object is connected it is not removed.)
RemAllPObj DO 3 Remove all pending objects in the queue. (If an
object is connected it is not removed.)
EncSelect DO 4 Select encoder:
0=EncA (must be 0)
1=EncB, not used
SoftSyncSig DO 5 Soft sync-signal
This signal can be used instead of a physical
signal connected to Digital input 1 of the module.
N.U. 6 Not used.
SimMode DO 7 If set this signal set the module in simulation mode
(simulate Position and Speed instead of using the
encoder values).
CntToEnc1 GO 8-23 Counter value from controller to encoder (Low
Word).
The bit group is valid for DSQC377-mode, i.e.
when PosInJobQ is set to 1.
CntToEnc2 GO 24-39 Counter value from controller to encoder (High
Word).
The bit group is valid for DSQC377-mode, i.e.
when PosInJobQ is set to 1.
CntToEncStr DO 40 Indication to module that the "CntToEncX" signals
contain valid values.
ForceJob DO 41 Run this job even if checkpoint fails (always set/
reset together with the CntToEncStr signal).
PosInJobQ DO 42 Set if the module shall send encoder values to the
controller instead of handling the queue itself.
0=Queue tracking disabled (DSQC354-mode)
1=Queue tracking enabled
N.U. 43-47 Not used.
For detailed information on using the DSQC 377A in an application refer to Application
manual - Motion coordination and supervision, see References on page 6.
Index
B
bus off 63
C
cables
length 23
CIP routing 29
D
DeviceNet generic unit type 33
DSQC 350A 98
DSQC 351A 103
DSQC 352A 109
DSQC 355A 90
DSQC 377A 123
DSQC 378A 115
DSQC 651 74
DSQC 652 80
DSQC 653 85
L
LED
DeviceNet network receive 67
DeviceNet network transmit 66
module status 65
network status 66
test run 68
S
system parameters
Connection 1 Input Size 55
Connection 1 Interval 53
Connection 1 Output Size 54
Connection 1 Type 52
Device Type 47
DeviceNet Address 44
DeviceNet Communication Speed 43
DeviceNet Master Address 42
Explicit Messaging 51
Internal Slave 57
Major Revision 48
Minor Revision 49
Path 59
Product Code 46
Production Inhibit Time 50
Quick Connect 56
Service 61
Trigger Poll I/O 58
Vendor ID 45
T
topic I/O
Bus 30
Unit 30
Unit Type 30
trouble shooting, bus off 63

132
Index
3HAC020676-001 Revision: F
3HAC 020676-001, Revision F, en
ABB AB
Robotics Products
S-721 68 VÄSTERÅS
SWEDEN
Telephone: +46 (0) 21 344000
Telefax: +46 (0) 21 132592

DeviceNet 3HAC020676-001 - Revf - en PDF

Uploaded by

Copyright:

Available Formats

DeviceNet 3HAC020676-001 - Revf - en PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DeviceNet 3HAC020676-001 - Revf - en PDF

Uploaded by

Copyright:

Available Formats

Application manual

Document ID: 3HAC020676-001

© Copyright 2004-2007 ABB. All rights reserved.

© Copyright 2004-2007 ABB All rights reserved.

3 DeviceNet Master/Slave configuration 27

4.4 Type Unit Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6 Boards and units 65

© Copyright 2004-2007 ABB. All rights reserved.

About this manual

Who should read this manual?

Continues on next page

© Copyright 2004-2007 ABB. All rights reserved.

Continues on next page

E Information updated in chapter 2.2 DeviceNet, IRC5. Chapter 6 Trouble

Product documentation, M2004

Technical reference manuals

© Copyright 2004-2007 ABB. All rights reserved.

Continues on next page

© Copyright 2004-2007 ABB. All rights reserved.

1.1. DeviceNet, general

Communication protocol connections

Type of message Description

nications used to perform node configuration and problem

Continues on next page

I/O messages - connection types

Type of I/O connection Description

© Copyright 2004-2007 ABB. All rights reserved.

1.2. DeviceNet, IRC5

A DSQC 658, DeviceNet fieldbus. Placed in the computer module.

Continues on next page

C DSQC 608/609, DeviceNet power supply 24 V

Support for Predefined Master/Slave Group 2 Client (Master)

1.3. Definition of I/O units

Configuration of the controller

A Control Module of the Dual Controller

B Drive Module of the Dual Controller

© Copyright 2004-2007 ABB. All rights reserved.

2.1. DeviceNet Master/Slave, DSQC 658 and DSQC 659

Installation of DSQC 658 and DSQC 659

Description Art. no. Note Pos.

DeviceNet master/slave 3HAC025779-001 DSQC 658 A, B, C, D

Continues on next page

Illustration, DSQC 659

© Copyright 2004-2007 ABB. All rights reserved.

A Channel A Health LED

Continues on next page

The table below shows the connections to the DeviceNet connector:

Signal name I/O pin Wire color Function

Designation Color status Description

2.2.1. Shield grounding and power

© Copyright 2004-2007 ABB. All rights reserved.

2.2.2. Connection of the DeviceNet bus

Physical connection between DeviceNet bus and DeviceNet node

A Incoming DeviceNet bus cable

Continues on next page

Termination resistors in DeviceNet bus

© Copyright 2004-2007 ABB. All rights reserved.

2.2.3. Selecting cables

Data rate 500 kbit/s