ABB Drives Use of DeviceNet

Protocol in
Advant Controller 80
 Use of DeviceNet
Protocol in Advant Controller (AC80)

AC80

Code: 3BFE 64336886 R0125

EFFECTIVE: 10.05.2000
SUPERSEDES: None

PDM: Vault Item 00071167

 2000 ABB Industry Oy. All rights reserved.

 Table of Contents

Table of Contents .................................................................................................................................................i

Chapter 1 – Introduction to This Manual ...................................................................................................... 1-1

Overview ................................................................................................................................................. 1-1
Intended Audience .................................................................................................................................. 1-1
What This Manual Contains .................................................................................................................... 1-1
Glossary of Terms Used in this Document .............................................................................................. 1-2
DeviceNet Protocol Levels ...................................................................................................................... 1-5

Chapter 2 - Overview....................................................................................................................................... 2-1

Overview ................................................................................................................................................. 2-1
DeviceNet Bus Topology............................................................................................................... 2-1
The NDNA-80 DeviceNet Adapter Module.................................................................................... 2-2
Compatibility.................................................................................................................................. 2-3
Delivery Check .............................................................................................................................. 2-3
Warranty and Liability Information................................................................................................. 2-3

Chapter 3 – Hardware and Installation.......................................................................................................... 3-1

Overview ................................................................................................................................................. 3-1
Mounting ....................................................................................................................................... 3-1
General Cabling Instructions......................................................................................................... 3-2
Earthing the NDNA-80 Module...................................................................................................... 3-2
DIP Switch Settings....................................................................................................................... 3-2
NDNA-80 Connections ............................................................................................................................ 3-3
AC80 Connection .......................................................................................................................... 3-3
DeviceNet Connection .................................................................................................................. 3-4
DeviceNet Bus Termination ......................................................................................................... 3-4
Connection Examples ................................................................................................................... 3-5

Chapter 4 - Message Level ............................................................................................................................. 4-1

Data Exchange between Master/Producer and Slave/Consumer in the DeviceNet System.................. 4-1

Chapter 5 - Data Level..................................................................................................................................... 5-1

AC80 Support for DeviceNet Protocol..................................................................................................... 5-1

Chapter 6 - Application Programming........................................................................................................... 6-1

General.................................................................................................................................................... 6-1
Creation of Data Base Element DCB01 .................................................................................................. 6-1
Creation of the DCBAID Function Block.................................................................................................. 6-3
Use of Type Circuits ................................................................................................................................ 6-4
Receiving REFERENCE Data from DeviceNet Master and Sending FEEDBACK Data to
DeviceNet Master.......................................................................................................................... 6-4

Chapter 7 – Fault Tracing ............................................................................................................................... 7-1

General.................................................................................................................................................... 7-1
NDNA-80 Status Codes .......................................................................................................................... 7-2
Status LEDs ............................................................................................................................................ 7-3
Installation Problems ............................................................................................................................... 7-3
PLC Programming................................................................................................................................... 7-4

Use of DeviceNet Protocol in AC80

Table of Contents

Scanner Fault Indications ........................................................................................................................ 7-4

Special DeviceNet Diagnostics in the AC80 Application Program .......................................................... 7-4
Special Diagnostics for DeviceNet at NCB Board ................................................................................... 7-7

Chapter 8 – DeviceNet Master Configuration ............................................................................................... 8-1

Overview ................................................................................................................................................. 8-1
Introduction to DeviceNet ........................................................................................................................ 8-1
Object Modelling and Functional Profiles ................................................................................................ 8-1
Assembly Object...................................................................................................................................... 8-1
1747-SDN Configuration ......................................................................................................................... 8-1
Software Setup.............................................................................................................................. 8-2
Creating the EDS File ................................................................................................................... 8-2
On-line Network Configuration ................................................................................................................ 8-3
Connect Devices ..................................................................................................................................... 8-3
Define Project.......................................................................................................................................... 8-4
Define Network........................................................................................................................................ 8-5
Add Devices to Network .......................................................................................................................... 8-5
Configure Scanner .................................................................................................................................. 8-6
Downloading the Configuration ............................................................................................................... 8-8

Chapter 9 – Electronic Data Sheets for DeviceNet ...................................................................................... 9-1

General Information and Compatibility .................................................................................................... 9-1

Chapter 10 – Appendices ............................................................................................................................. 10-1

APPENDIX A ........................................................................................................................................ 10-1
Data Base Element DCB01......................................................................................................... 10-1
Management of FBA CommunicationsPC Element DCBAID...................................................... 10-1
Overview ..................................................................................................................................... 10-2
Type Circuit DN24WEXC ............................................................................................................ 10-2
Disintegrated Type Circuit DN24WEXC ................................................................................................ 10-3
PC Element DCBRX ................................................................................................................... 10-3
APPENDIX B - General ........................................................................................................................ 10-4
Using Standard NDNA-01 with AC80.......................................................................................... 10-4
Configuration............................................................................................................................... 10-4
Startup......................................................................................................................................... 10-5
APPENDIX C – Error Codes for DCB Protocols / DeviceNet................................................................ 10-6
Communication Error Codes....................................................................................................... 10-6

ii Use of DeviceNet Protocl in AC80

 Chapter 1 – Introduction to This Manual

Overview This manual describes the use of the DeviceNet protocol for the
Advant Controller 80 (AC80).

This chapter contains a description of the Use of DeviceNet Protocol

in Advant Controller 80 manual for the NDNA-80 DeviceNet Adapter
Module.

Intended Audience The Manual is intended for the people who are responsible for
engineering, installing, commissioning and using a DeviceNet
Adapter Module with an AC80 controller. The reader is expected to
have a basic knowledge of electrical fundamentals, electrical wiring
practices, the drives and the DeviceNet protocol.

What This Manual The engineering, installation and start-up of the NDNA-80 DeviceNet
Adapter Module are introduced in this Manual.
Contains
It is assumed that the AC80 is installed and ready to operate before
starting the installation of the adapter module. For more information
on the installation and start-up procedures of the AC80, please refer
to its user documentation.

Chapter 1 – Introduction to This Manual contains a short

description of the Manual.

Chapter 2 – Overview contains a short description of the DeviceNet

protocol and the NDNA-80 DeviceNet Adapter Module, a delivery
checklist, and information on the manufacturer’s warranty.

Chapter 3 – Hardware and Installation contains mounting, wiring,

bus termination and earthing instructions for the module.

Chapter 4 – Message Level contains short description of messaging

used with this NDNA-80 module.

Chapter 5 – Data Level contains short description of the support

given by the AC80 for DeviceNet option.

Chapter 6 – Application Programming gives information for the

application designer.

Chapter 7 – Fault Tracing describes how to fault diagnose the

DeviceNet connection during installation, commissioning, and normal
operation.

Chapter 8 – DeviceNet Master Configuration describes how to

configure the Scanner 1747 for Allen-Bradley SLC 500.

Use of DeviceNet Protocol in AC80 1-1

Chapter 1 – Introduction to This Manual

Chapter 9 – Electrical Data Sheets for DeviceNet describes how to

Configure the Electrical Data Sheets for Allen-Bradley PLC.

Chapter 10 – Appendices includes the following appendices:

Appendix A contains diagrams of Database element DCB01, PC

element DCBAID, type circuit DN24WEXC and PC element DCBRX.

Appendix B contains instructions for using a standard NDNA-02 with

AC80.

Appendix C contains the error code list for DeviceNet protocol in

AC80.

Glossary of Terms BIT-STROBE MESSAGE is an I/O message that is transmitted by

the Master in the Device Net communication. It is not used with
Used in this NDNA-80.
Document
CHANGE OF STATE / CYCLIC MESSAGE is transmitted by either
the Master or the Slave. A Change of State / Cyclic message is
directed towards a single specific node (point-to-point). An
Acknowledge may be returned in response to this message.

COMMUNICATION MODULE is a name for a device (e.g. Fieldbus

Adapter) through which the AC80 controller is connected to an
external serial communication network (e.g. a Fieldbus).

DATA BLOCK on a DeviceNet bus contains 1 to 121 words (16 bit)

in in both directions. The data block carries either reference or
feedback data (1 word for diagnostics). The maximum data block
length may be restricted by the PLC type.

DATASET on a DDCS bus contains 3 words (16 bit). Data sets carry
reference, feedback or status data.

FEEDBACK TABLE is a data table in the FBA (Fieldbus Adapter)

unit containing 16 bit words (integers or packed Boolean values). The
maximum number of feedback values is 120. The locations can be
used e.g. to store feedback values from the drives. The application
program of the AC80 sends desired feedback values (or other data)
to the feedback table.

INITIALIZING PARAMETERS is a data block included in the

NDNA-80 system program, containing 16-bit integers. The
parameters define the operation of the protocol e.g. the baud rate,
bus address (Mac ID) and data length. Each parameter has a default
value which can be adjusted by the AC80 application designer if
necessary.

INPUT in the DeviceNet specification is used to describe data flow

from a device into the network or to the Master.

1-2 Use of DeviceNet Protocol in AC80

 Chapter 1 – Introduction to This Manual

IO ASSEMBLY SELECTION. Smart networked devices (like the

NDNA-80) can produce and consume more than one I/O value.
Typically they will, as well as, status and diagnostics information.
Each piece of data communicated by a device is represented by an
attribute of one of the devices internal objects.

Communicating multiple pieces of data (attributes) across a single I/O

connection requires that the attributes be grouped or assembled
together into a single block.

MAC ID is Media Access Control ID. Every node on DeviceNet

network has to have a unique identifier. This node number is called
MAC ID.

ODVA stands for Open DeviceNet Vendor Association. ODVA is an

independent organisation that promotes interoperability between
different manufacturers DeviceNet products. ABB is an Associate
Member of the ODVA.

OUTPUT in the ODVA DeviceNet specification is used to describe

data flow from the network (or from the Master) to a device.

POLL MESSAGE is one of the the three services supported by the

most of the DeviceNet scanners.

SCANLIST is the list indicating the user-defined order according to

which the DeviceNet Scanner communicates with the DeviceNet
Slaves.

SUBADDRESSING means that, under one Mac ID address, up to 16

subaddresses can be used to address data to separate VCI buffers in
one AC80. Subaddresses 0 to 15 are assigned to VCI buffer numbers
1 to 32 in such a way that VCI buffers 1 (input) and 2 (output) are
assigned to the subaddress 0, VCI buffers 3 and 4 and assigned to
the subaddress 1 an so on. Each VCI buffer pair is identified by its
Ident value having values between 1 to 115. All bits in each VCI
buffer pair are freely usable for the application. The application
designer does not need to take care of subaddressing; just creating
the correct type circuit and defining its Ident value is enough.

REFERENCE TABLE is a data table in the NDNA-80 containing 16

bit words (integers or 16 packed Boolean values). The maximum
number of reference values is 120. These locations can be used e.g.
to store reference data sets sent by the master (equipment). The
application program of the AC80 receives reference data from the
Reference Table to the AC80.

VCI BUFFER is a communication buffer located at the Dual Port

Memory (in)-between the AC80 CPU and NCB boards.

Use of DeviceNet Protocol in AC80 1-3

Chapter 1 – Introduction to This Manual

The following services are available in the DeviceNet software

package of NDNA-80. All these services are not utilized.

Item Service Function

1 Bit Strobe The Bit Strobe Command is an I/O
Message message that is transmitted by the Master.
(Not used with the NDNA-80)
2 Change of State The Change of state / Cyclic Message is
/Cyclic transmitted by either the Master or the
Message Slave. A Change of State / Cyclic Message
is directed towards a single specific node
(point-to-point). An Acknowledge Message
may be returned in response to this
message.
3 Poll Message The Poll Command is an I/O Message that
is transmitted by the Master. A Poll
Command is directed towards a single,
specific Slave (point-to-point, NDNA-80
acts as a Slave). A Master must transmit a
separate Poll Command Message for each
one of its Slaves that is to be polled. The
Poll Response is an I/O Message that a
Slave transmits back to the Master when
the Poll Command is received.
The AC80 and the NDNA-80 communicate over a pair of optical
fibres. The communication occurs cyclically on the initiative of the
NDNA-80. The cycle time is typically 20 ..40 ms per subaddress /
type circuit and cannot be changed.

The shortest communication interval between the DeviceNet master

and the NDNA-80 is about 30 to 300 ms per message pair depending
on the baud rate. Performance of the master station and a great
number of slaves may prolong the communication interval.

The maximum number of message buffers at the AC80 is 33.

DeviceNet uses a maximum of 16 buffers for reference and feedback
data. If many buffers are used, the communication interval must be
increased.

A communication sequence consists of a query message and a

response message. Broadcasting is not used. The communication
sequence between the NDNA-80 and the master station is described
in Chapter 4 - Message level.

1-4 Use of DeviceNet Protocol in AC80

 Chapter 1 – Introduction to This Manual

DeviceNet Protocol The DeviceNet protocol for AC80 has six levels according to
Figure 1 - 1.
Levels
Application Layer
Logical Link Control (LLC)
Media Access Control (MAC)
Physical Layer Signalling (PLS)
Medium Attachment Unit (MAU)
Transmission Media
Figure 1 - 1 DeviceNet / CAN protocol levels

Use of DeviceNet Protocol in AC80 1-5

Chapter 1 – Introduction to This Manual

1-6 Use of DeviceNet Protocol in AC80

 Chapter 2 - Overview

Overview This chapter contains a short description of a DeviceNet bus

topology, the NDNA-80 Adapter Module, a delivery checklist, and
warranty information.

Further information can be obtained from [Link].

DeviceNet Bus The DeviceNet network has a linear bus topology. Terminating
Topology resistors are required on each end of the trunk line. Drop lines as
long as 6 metres (20 feet) each are permitted, allowing one or more
nodes to be attached. DeviceNet allows branching structures only on
drop lines. An example of an allowable topology is shown in Figure 2-
1.

Figure 2 – 1 DeviceNet bus topology.

The maximum length of trunk cable depends on the data rate and on
the type of the cable used.

The DeviceNet network should be terminated at both ends of the

trunk cable with a 121 Ω, ¼ W, 1% Metal Film resistor. Connect this
resistor between the two signal wires (CAN_H, CAN_L) on the
DeviceNet Cable.

Use of DeviceNet Protocol in AC80 2-1

Chapter 2 - Overview

The NDNA-80 The NDNA-80 DeviceNet Adapter Module is an optional device for
the AC80 controller which enables the connection of the AC 80 to a
DeviceNet
DeviceNet system. The AC80 is considered as a slave in the
Adapter Module DeviceNet network. Through the NDNA-80 DeviceNet Adapter
Module it is possible to:

• Receive 6 to 120 16-bit words of Drive group-specific or other

data from the DeviceNet master.
• Send 6 to 120 16-bit words of Drive group-specific or other data
to the DeviceNet master.

The NDNA-80 acts as a Class 2 slave only with predefined master-

slave connection set services. These include the the Poll-Response
service and possibly the Change of State/Cyclic service. The
DeviceNet commands and services supported by the NDNA-80
DeviceNet Adapter Module are discussed in Chapter 2.
The adapter module can be mounted onto a standard mounting rail.

Figure 2 - 2 The construction of the DeviceNet link and the NDNA-80

Adapter Module.

2-2 Use of DeviceNet Protocol in AC80

 Chapter 2 - Overview

Compatibility The NDNA-80 is compatible with AC80 software version 801SW010

or later, and all scanners that work according to ODVA DeviceNet
specifications. (The NDNA-80 has been tested with the Allen-Bradley
1747-SDN and 1756-DNB scanner modules.)

The AC80 can be connected via DriveBus to the following drive

types:

• ACS 400
• ACS 600 with NAMC-03
• ACS 600 with NAMC-11
• ACS 600 with NAMC-21
• DCS 600
• TSU

Delivery Check The option package for the NDNA-80 DeviceNet Adapter Module
contains:

• DeviceNet Adapter Module, Type NDNA-80

• Two pairs (four pieces) of fibre optic cables for connecting the
adapter to the drive
• Mounting rail
• This manual, the Use of DeviceNet Protocol in Advant Controller
80.

Warranty and The warranty for your ABB drive and options covers manufacturing
defects. The manufacturer carries no responsibility for damage due
Liability to transport or unpacking.
Information
In no event and under no circumstances shall the manufacturer be
liable for damages and failures due to misuse, abuse, improper
installation, or abnormal conditions of temperature, dust, or
corrosives, or failures due to operation above rated capacities. Nor
shall the manufacturer ever be liable for consequential and incidental
damages.

The period of manufacturer's warranty is 12 months, and not more

than 18 months, from the date of delivery. Extended warranty may be
available with certified start-up. Contact your local distributor for
details.

Your local ABB Drives company or distributor may have a different

warranty period, which is specified in their sales terms, conditions,
and warranty terms.

Use of DeviceNet Protocol in AC80 2-3

Chapter 2 - Overview

If you have any questions concerning your ABB drive equipment,

contact your local distributor or ABB Drives office.

The technical data and specifications are valid at the time of printing.
ABB reserves the right to subsequent alterations.

2-4 Use of DeviceNet Protocol in AC80

 Chapter 3 – Hardware and Installation

Overview This chapter contains:

• NDNA-80 module mounting instructions

• general cabling instructions
• module earthing instructions
• instructions for connecting the module to the AC80 and to the
DeviceNet bus.

Mounting Choose the location for the module. Note the following:

• The general cabling instructions (see Figure 3 - 1) must be

followed.
• The ambient conditions should be taken into account. (The
degree of protection of the module is IP 20.)
• Observe the free space requirements for the module (see the
figure below).
• Module earth is connected to its mounting rail by means of an
earthing tab (see the figure below). The mounting rail must be
earthed to a noiseless earth. If the rail is not mounted on a
properly earthed base, a separate earthing conductor must be
used. The conductor must be as short as possible and its cross-
sectional area must be 6 mm2 at least. Note: No solid copper
conductor may be used (stranded wire allowed only).
Mounting instructions:

1. Switch off all dangerous voltages in the enclosure that the module
is to be mounted in. Note that residual voltages may remain in
some components (e.g. drive modules) even though the power is
switched off.
2. Fasten the rail and ensure the proper earthing as described
above.
3. Push the module onto the rail. The module can be released by
pulling the locking spring with a screwdriver (see Figure 3 - 1).

Use of DeviceNet Protocol in AC80 3-1

Chapter 3 - Hardware and Installation

Figure 3 – 1

General Cabling Arrange the bus cables as far away from any power cables as
Instructions possible. Avoid parallel runs. Use bushings at cable entries. Suitable
cable types are e.g. YR - 29790 (Thick DeviceNet Cable) and YR-
29832 (Thin DeviceNet cable).

Handle fibre optic cables with care. When unplugging optic cables,
always grab the connector, not the cable itself. Do not touch the ends
of the fibres with bare hands as the fibre is extremely sensitive to dirt.

The maximum long term tensile load for the fibre optic cables is 1 N.
The minimum short term bend radius is 25 mm.

Earthing the The NDNA-80 module earth is connected to the rail onto which the
module is mounted. If the rail is fastened to an earthed metallic
NDNA-80 Module assembly plate, the module is automatically earthed, and no external
earthing wire is needed. If the rail is fastened to a base that is not
earthed, the rail must be connected to the nearest earthing terminal.
However, the earthing wire should not be connected to the same
terminal as the power cable screens.

DIP Switch The DIP switches SW1 and SW2 on the NDNA printed circuit board
can optionally be used to select the node number and the baud rate
Settings for the module.

If SW1:8 is however set to OFF (default), the node number and the
baud rate are selected through the module configuration parameters
(see Chapter 6).

The figures 3 – 2 show how the DIP switches on the circuit board can
be accessed.

3-2 Use of DeviceNet Protocol in AC80

 Chapter 3 – Hardware and Installation

Figure 3 - 2

NDNA-80
Connections
AC80
The NDNA-80 module is connected to the AC80 using a fibre optic
Connection cable link. Consult the AC80 documentation as to the corresponding
terminals.

Figure 3 – 3 Fibre optic link connecting the NDNA-80 to the AC80.

Use of DeviceNet Protocol in AC80 3-3

Chapter 3 - Hardware and Installation

DeviceNet The bus cable and the external power supply are connected to
terminal blocks X1 and X2 on the NDNA-80.
Connection
The terminal blocks are described below.

X1 Description
1 0V DC GND Power supply ground (0 V). If the power to the
module is supplied through the DeviceNet
network, this terminal should be left
unconnected.
2 UC +24 VDC +24 V ±10% (80 mA) d.c. supply to the module.
The power can be taken from a dedicated
external power supply, or through the DeviceNet
network.
The on-board power supply is disabled if the
voltage drops below 11 V.
3 EXT DC GND These terminals should be connected together if
the power to the module is supplied through the
DeviceNet network. This makes the NDNA-80 a
non-isolated node.
4 CAN
GND

X2 Description
5 SHLD Network cable shield.
6 CAN_L CAN_L bus line.
7 GND DeviceNet bus ground (digital ground).
8 CAN_H CAN_H bus line.

DeviceNet Bus The DeviceNet bus line must be terminated with 121 ohm resistors
Termination connected between the CAN_L and CAN_H wires at each end as
shown below.

Figure 3 – 4 DeviceNet bus termination.

3-4 Use of DeviceNet Protocol in AC80

 Chapter 3 – Hardware and Installation

Connection
Examples

Figure 3 – 5

Use of DeviceNet Protocol in AC80 3-5

Chapter 3 - Hardware and Installation

3-6 Use of DeviceNet Protocol in AC80

 Chapter 4 - Message Level

Data Exchange The DeviceNet protocol defines two different types of messaging.
They are called I/O messaging and Explicit messaging.
between
With the NDNA-80, only I/O messaging is used. I/O messaging
Master/Producer
provides a dedicated, special purpose communication path between
and a producing application and one or more consuming applications.
Slave/Consumer in
the DeviceNet
DeviceNet Master: DeviceNet Slave:
System
Output Data message

CAN Header Application Output CAN Trailer

Data

Input Data message

CAN Header Application Input CAN Trailer

Data

Because more than 8 bytes of I/O data are always needed with the
NDNA-80, so called DeviceNet Fragmentation Protocol is used. In
this protocol, the application I/O data area consists of numerous
fragments described on the following page.

Use of DeviceNet Protocol in AC80 4-1

Chapter 4 – Message Level

The fragments are structured as follows including 8 bytes:

Bits:
7 6 5 4 3 2 1 0
Fragment Fragment Count
Type (Byte 0)
st
The 1 byte of application specific data
( Byte 1)
The 2nd byte of application specific data
( Byte 2)
The 3rd byte of application specific data
( Byte 3)
th
The 4 byte of application specific data
( Byte 4)
th
The 5 byte of application specific data
( Byte 5
The 6Th byte of application specific data
( Byte 6 )
th
The 7 byte of application specific data
( Byte 7)

Contents of fragments:
Fragment Type 0 = First fragment of the message
1 = Middle fragment (any) of the message
2 = Last fragment of the message
3 = Fragment Acknowledge
Fragment Count Marks each separate fragment such that
the receiver can determine whether or not a
fragment has been missed.

4-2 Use of DeviceNet Protocol in AC80

 Chapter 5 - Data Level

AC80 Support for In DeviceNet slave mode, the AC80 is able to:

DeviceNet Protocol 1. Receive 6 to 120 16-bit words of Drive group-specific or other

data from the DeviceNet master.
2. Send 6 to 120 16-bit words of Drive group-specific or other
data to the DeviceNet master.
The following function blocks from the library of the AC80 are needed
for DeviceNet communication functions.

Block Name: Purpose:

DCBAID Supports the DCB communication
DCBRX Sends/Receives data message to/from the
DeviceNet master station

One DCB01 DB element is needed:

DB-Element Name: Purpose:
DCB01 Specifies DeviceNet parameters and
allocates communication buffer area.

Following type circuits support the DeviceNet protocol:

Name of Purpose:
Type Circuit:
DN24WEXC, Receiving 24 / 12 / 6 words (16 bit) from
DN12WEXC or the DeviceNet master and
DN6WEXC Sending 24 / 12 / 6 words (16 bit) to the
DeviceNet master

Use of DeviceNet Protocol in AC80 5-1

Chapter 5 – Data Level

5-2 Use of DeviceNet Protocol in AC80

 Chapter 6 - Application Programming

General In order to use the DeviceNet protocol the AC80 must be properly
programmed. The application program is created by using the FCB
tool. The DeviceNet protocol functions require:
• one Data Base element DCB01 (See Chapter 10, Figure 10 - 1)
• one DCBAID function block (See Chapter 10, Figure 10 - 2)
• one or more DN24WEXC / DN12WEXC / DN6WEXC type circuits
(See Chapter 10, Figure 10 - 3) / DCBRX function blocks (See
Chapter 10, Figure 10 - 4)
• typically one type circuit for each drive group or data group

Message structures and addressing must match the corresponding

message structures in the master station.

Creation of Data The DCB01 defines the DeviceNet protocol and the NDNA-80
adapter (See Chapter 3 – Hardware and Installation). The NDNA-80
Base Element
has only one bus address for DeviceNet bus.
DCB01
Select DCB link: Base Part

Pin: Instructions:
NAME Enter DCBXX (XX can be any digits)
FBATYPE Enter NDNA_80
PROTOCOL Enter 10
Select DCB link: Channels

Pin: Instructions:
RECS1 Enter 33
RECSIZE1 Enter 24
RECS2 Enter 0
RECSIZE2 Enter 0
The NDNA-80 adapter includes default values for the DCB
Parameters of a DeviceNet application.

Use of DeviceNet Protocol in AC80 6-1

Chapter 6 - Application Programming

The following parameters can be adjusted / monitored for the

DeviceNet protocol.
Param. Default Max. Min. Significance
Group/ Value Value Value
Index
151.1 101 101 101 101 = NDNA-80
151.2 10 10 10 Protocol code
(10 = DeviceNet)
151.3 63 63 2 Own station number
(= Mac ID.)
109.4 2 6 1 Module state (output display)
0 = Self test
1 = No connection
2 = Connected
3 = Time-out
4 = Duplic. Mac ID error
5 = Bus off
6 = Communication error
7 = Wrong assembly
151.5 8 8 2 Number of datasets
Needed in DDCS bus.
VCI data length: Datasets:
6 2
12 4
24 8
151.6 9 9 9 Number of free dataset
numbers at the beginning of
table.
151.9 500 2000 50 Time-out value for error
situation (ms * 2).
151.10 2 2 0 Baud rate in DeviceNet bus.
0 = 125 kilobaud
1 = 250 kilobaud
2 = 500 kilobaud
151.11 4 16 1 Number of type circuits /
DCBRX function blocks.
151.12 24 24 6 Data length of a VCI buffer
(words)
151.13 1 1 0 Fast VCI (Ident = 1) in use
1 = yes
0 = no
151.14 500 2000 50 Diagnostics interval (ms)
151.15 121 121 7 Data block length in DeviceNet
(1 word for diagnostics).

6-2 Use of DeviceNet Protocol in AC80

 Chapter 6 – Application Programming

If you want to adjust any DCB parameter values:

Select → DCB link:→ Parameters 1 to 9
The parameter valuesthat need to be adjusted are given as follows:
E.g. Bus address (MAC ID) should be adjusted to 5 and number of
subaddresses / type circuits should be adjusted to 8.
Note: Parameter group 151 is a hidden default value, only Parameter
Index INDX needs to be specified. The indexes 1 and 2 are not
allowed.)

Pin: Instructions:
IND1 Enter 3 (= Parameter index)
VAL1 Enter 5 (= Desired new value)
IND2 Enter 11 (= Parameter index)
VAL2 Enter 8 (= Desired new value)
Note: Parameter Index 33 in the DCB01 element is reserved for a
time-out value setting of AC80 application elements. The value is
given in milliseconds (e.g. time-out at DCBRX).

Creation of the One DCBAID PC element is needed to make it possible to use the
NDNA-80.
DCBAID Function
One instance of DCBAID must be in the application program which
Block
includes DN24WEXC / DN12WEXC / DN6WEXC type circuits /
DCBRX function blocks (or other FBA communication elements).

In a cyclic task the DCBAID block is recommended to precede other

DeviceNet blocks or type circuits (in execution order).

DCBAID has the following input terminals:

Pin: Instructions:
CHAN Enter D = 1
PARID Parameter index the actual value of which is to be
shown. Enter e.g. D = 3 (DeviceNet address). If 0 then
no value is shown.
VCIADDR Number of the VCI buffer to be examined by
Means of DCBAID. Enter e.g. D = 1
VCIOFFS Location in the VCI buffer to be shown. Enter e.g. D = 5
The output pins of the DCBAID element are very useful in finding out
the status and possible errors in DCB communication. The output
pins are discussed in Chapter 7 and in the AC80 PC Elements
Reference Manual.

Use of DeviceNet Protocol in AC80 6-3

Chapter 6 - Application Programming

Use of Type Type circuits DN24WEXC / DN12WEXC / DN6WEXC (see Chapter

6) are included in the FCB library to support the DeviceNet protocol.
Circuits Type Circuits consist of one DCBRX block (see Chapter 10, Figure
10 - 4).

Receiving One DN24WEXC / DN12WEXC / DN6WEXC type circuit is inserted

REFERENCE into the application program for each subaddress (e.g. drive group /
data group).
Data from
DeviceNet The input terminals of DN24WEXC should be set as follows:
Master and
DN24WEXC Type Circuit:
Sending
Input Pin: Instructions:
FEEDBACK Data
IDENT Enter IDENT value as follows:
to DeviceNet (Only these values are legal for the TC)
Master Related drive Related sub-
Value of Ident Group or data address in
group / Values NDNA-80
1 1 / 1 to 24 0
25 2 / 25 to 48 1
49 3 / 49 to 72 2
73 4 / 73 to 96 3
97 5 / 97 to 120 4
EN Enter 1
CLEAR Enter 0
IN1 Process data value 1 of group n to DN master
IN2 Process data value 2 of group n to DN master
IN3 Process data value 3 of group n to DN master
IN4 Process data value 4 of group n to DN master
IN5 Process data value 5 of group n to DN master
IN6 Process data value 6 of group n to DN master
IN7 Process data value 7 of group n to DN master
IN8 Process data value 8 of group n to DN master
… Process data value 9 …
IN24 Process data value 24 of group n to DN master

6-4 Use of DeviceNet Protocol in AC80

 Chapter 6 – Application Programming

The output terminals of DN24WEXC should be set as follows:

Output Pins: Data Contents:
RDY RDY indicates whether DN24WEXC / DCBRX has
recently found new data in the input VCI buffer or
previous
Data was just picked from the output VCI buffer.
ERR ERR indicates whether this DCBRX is operative
and has communicated with FBA recently.
STATUS STATUS is a boolean word consisting of 16
individual bits. E.g. the combinations 19 and 211
exist in normal operation. More details are
given in the AC80 PC Elements Reference
Manual.
OUT1 Process data 1 for group n from DN master
OUT2 Process data 2 for group n from DN master
OUT3 Process data 3 for group n from DN master
OUT4 Process data 4 for group n from DN master
OUT5 Process data 5 for group n from DN master
OUT6 Process data 6 for group n from DN master
OUT7 Process data 7 for group n from DN master
OUT8 Process data 8 for group n from DN master
… Process data 9 …
OUT24 Process data 24 for group n from DN master
ERRC Error code pin of DCBRX block

The input terminals of DN12WEXC should be set as follows:

DN12WEXC Type Circuit:
Input Pin: Instructions:
IDENT Enter IDENT value as follows:
(Only these values are legal for the TC)
Related drive Related sub-
Value of Ident Group or data address in
group / Values NDNA-80
1 1 / 1 to 12 0
13 2 / 13 to 24 1
25 3 / 25 to 36 2
37 4 / 37 to 48 3
49 5 / 49 to 60 4
61 6 / 61 to 72 5
73 7 / 73 to 84 6
85 8 / 85 to 96 7
97 9 / 97 to 108 8
109 10 / 109 to 120 9

Use of DeviceNet Protocol in AC80 6-5

Chapter 6 - Application Programming

The input terminals of DN12WEXC (table) continued

DN12WEXC Type Circuit:
Input Pin: Instructions:
EN Enter 1
CLEAR Enter 0
IN1 Process data value 1 of group n to DN master
IN2 Process data value 2 of group n to DN master
IN3 Process data value 3 of group n to DN master
IN4 Process data value 4 of group n to DN master
IN5 Process data value 5 of group n to DN master
IN6 Process data value 6 of group n to DN master
IN7 Process data value 7 of group n to DN master
IN8 Process data value 8 of group n to DN master
… Process data value 9 …
IN12 Process data value 12 of group n to DN master

The output terminals of DN12WEXC should be set as follows:

Output Pins: Data Contents:
RDY RDY indicates whether DN12WEXC / DCBRX has
recently found new data in the input VCI buffer or
previous data was just picked from the output VCI
buffer.
ERR ERR indicates whether this DCBRX is operative
and has communicated with FBA recently.
STATUS STATUS is a boolean word consisting of 16
individual bits. E.g. the combinations 19 and 211
exist in normal operation. More details are
given in the Function Blocks manual.
OUT1 Process data 1 for group n from DN master
OUT2 Process data 2 for group n from DN master
OUT3 Process data 3 for group n from DN master
OUT4 Process data 4 for group n from DN master
OUT5 Process data 5 for group n from DN master
OUT6 Process data 6 for group n from DN master
OUT7 Process data 7 for group n from DN master
OUT8 Process data 8 for group n from DN master
… Process data 9 …
OUT12 Process data 12 for group n from DN master
ERRC Error code pin of DCBRX block

6-6 Use of DeviceNet Protocol in AC80

 Chapter 6 – Application Programming

The input terminals of DN6WEXC should be set as follows:

DN6WEXC Type Circuit:
Input Pin: Instructions:
IDENT Enter IDENT value as follows:
(Only these values are legal for the TC)
Related drive Related sub-
Value of Ident Group or data address in
group / Values NDNA-80
1 1 / 1 to 6 0
7 2 / 7 to 12 1
13 3 / 13 to 18 2
19 4 / 19 to 24 3
25 5 / 25 to 30 4
31 6 / 31 to 36 5
37 7 / 37 to 42 6
43 8 / 43 to 48 7
49 9 / 49 to 54 8
55 10 / 55 to 60 9
61 11 / 61 to 66 10
67 12 / 67 to 72 11
73 13 / 73 to 78 12
79 14 / 79 to 84 13
85 15 / 85 to 90 14
91 16 / 91 to 96 15
EN Enter 1
CLEAR Enter 0
IN1 Process data value 1 of group n to DN master
IN2 Process data value 2 of group n to DN master
IN3 Process data value 3 of group n to DN master
IN4 Process data value 4 of group n to DN master
IN5 Process data value 5 of group n to DN master
IN6 Process data value 6 of group n to DN master

Use of DeviceNet Protocol in AC80 6-7

Chapter 6 - Application Programming

Output terminals of DN6WEXC should be set as follows:

Output Pins: Data Contents:
RDY RDY indicates whether DN6WEXC / DCBRX has
recently found new data in the input VCI buffer or
previous data was just picked from the output VCI
buffer.
ERR ERR indicates whether this DCBRX is operative
and has communicated with FBA recently.
STATUS STATUS is a boolean word consisting of 16
individual bits. E.g. the combinations 19 and 211
exist in normal operation. More details are
given in the Function Blocks manual.
OUT1 Process data 1 for group n from DN master
OUT2 Process data 2 for group n from DN master
OUT3 Process data 3 for group n from DN master
OUT4 Process data 4 for group n from DN master
OUT5 Process data 5 for group n from DN master
OUT6 Process data 6 for group n from DN master
ERRC Error code pin of DCBRX block

6-8 Use of DeviceNet Protocol in AC80

 Chapter 7 – Fault Tracing

General When the DeviceNet communication does not work or any error
occurs, this chapter helps to find the cause.

The diagnostics information can be seen by means of special tools or

the Led indicators located on the NDNA-80 (DeviceNet Adapter
Module).

An error may be (e.g.):

• a configuration error
• a programming error
• hardware fault
• broken line
• electromagnetic interference.

The origin of an error code can be:

• certain function blocks
• the AC80 system program
• the NDNA-80 unit.
The NDNA-80 error codes are transferred to the DCBAID element in
the application program of the AC80.

Error codes for (the) DeviceNet communication are listed in Chapter

10 Appendix C - Error codes for DCB protocols.

The error code can be read from:

• the error terminals of the diagnostic DCBAID block, or
• the ERRC terminal of an ordinary DCBRX function block, or
• the ERRC terminal of a DNnEXC type circuit.
Only the latest error code can be read from the error terminals. By
connecting the error terminal to terminal I of an ERROR block the
occurrence of an error code can be registered and time stamped.
The ERROR block stores the occurred errors in an event buffer in
order of appearance. The event buffer can be read from the panel
CDP 80 or the DriveWindow tool.

Error codes at the ERRC pin of DCBRX can be cleared with a rising
edge on the CLEAR pin.

Use of DeviceNet Protocol in AC80 7-1

Chapter 7 – Fault Tracing

NDNA-80 Status This Status parameter 109.04 can be seen with the DriveDebug tool
at the Configuration DeviceNet parameters and it indicates the
Codes status of the DeviceNet module.

0 = SELF TEST
The module is initialising and performing self-test.

1 = NO CONNECT
The module has completed its power-up sequence, and is waiting for
a DeviceNet Scanner or the Manager software to establish a
connection.

2 = CONNECTED
The DeviceNet module is connected and communicating with a
DeviceNet Scanner or Manager software.

3 = TIME-OUT
The DeviceNet Scanner has stopped communicating with the
NDNA-80 module. The Scanner might have been powered down.

Note: Timeout is only observed with I/O connections (Poll, Bit-strobe,

COS/Cyclic) and not with explicit messaging connection.

4 = DUP. MAC ERR

The module has observed another device with the same MAC ID in
the network. Change the MAC ID value and switch the module power
off and on.

5 = BUS OFF
The module has detected an error on the DeviceNet wire physical
communication, and is disconnected. To clear this state, switch the
module power off and on.

6 = COM. ERROR
Some other communication error (receive buffer overflow for
example) has been detected by the module. Try switching the module
power off and on. Also check the connections and increase Scanner
interscan cycles.

7 = WRONG ASMBLY
The AC80 does not support the chosen I/O assembly. See the I/O
assembly selection parameter settings.

7-2 Use of DeviceNet Protocol in AC80

 Chapter 7 – Fault Tracing

Status LEDs There are three status LEDs on the NDNA-80 module, labelled
DDCS, NS (Network Status) and MS (Module Status). The LEDs are
bicolour (green/red) with white diffused lens.

The LED indications are as follows:

LED Mode Description
DDCS Off Not powered
Flashing DDCS initialisation in progress
Green
Green DDCS communication established
Flashing Red DDCS communication errors
Red • DDCS communication failed, or
• Module fault
NS Off Not on-line/Not powered:
• Not powered (see MS LED), or
• Dup_MAC_ID test not completed yet
Flashing On-line, but without connections in the
Green established state:
• Dup_MAC_ID test completed but no
established connections to other nodes, or
• Not allocated to a master
Green Link OK. On-line with connections in the
established state. Allocated to a master
Flashing Red One or more connections are in timed-out
state
Red Critical link failure. The module has detected
an error that has rendered it incapable of
communicating on the network (Duplicate
MAC ID, or Bus-off)
MS Off Not powered
Flashing Stand-by. Module needs commissioning due
Green to incomplete or incorrect configuration. E.g.
wrong assembly selected
Green Operating in a normal condition
Red Unrecoverable fault
Flashing Self test in progress
Red–Green

Installation Verify all the connections on the module:

Problems • DeviceNet and power cables connected to terminal blocks X1 and
X2 as described in Chapter 3.
• DeviceNet power cable (if used) has sufficient 24 V d.c. regulated
power connected to it.

Use of DeviceNet Protocol in AC80 7-3

Chapter 7 – Fault Tracing

• Fibre optic cables are connected between the correct channel of

the AC80 and the NDNA-80 module.
• Check that the fibre optic cable connector colours match the
AC80 and the NDNA-80 module connector colours.

PLC Programming The PLC program is beyond ABB Drives support. Contact the
manufacturer for assistance.

However one 16 bit word in feedback data block is used for

st
communication supervision. This word is the 1 word in the feedback
data block including one bit for error diagnostics for each used
subaddress. The bit number 0 is for subaddress 0, bit number 1 is for
subaddress 1 and so on. If any of these bits is 1 then the
respective subaddress is inhibited in AC80.

Scanner Fault Refer to scanner documentation. The latest revision is available at

Allen-Bradley internet homepage [Link]
Indications
Special DeviceNet Chapter 10, Appendix A, Figure 10 - 2 shows the DCBAID function
block which can be used to display the communication status of the
Diagnostics in the DeviceNet link. The output pins of the DCBAID block indicate the
AC80 Application status in the following way:
Program Pin Name of Meaning
Number Pin
10 ERR Indicates whether DCBAID is usable
0 = yes, 1 = no
11 FAIL Indicates some error codes in application
programming. See listing in Chapter 10.
12 FBATYPE Text: ABB NDNA-80
13 PROTOCS Available protocols: A (= DeviceNet)
14 HWVERS FBA hardware version: e.g. HW-VERS. 1.0
15 SWVERS FBA software version: e.g. SW-VERS. 1.0
16 DATE FBA software generating date: e.g. 00-02-20
17 DCBSTAT DCB communication status inside AC80
CPU
0= No DCB Data Base element created.
1= Data Base Element DCB01 exists
2= DCB definition written to the Dual Port
Memory of NCB board.
3= VCI buffers ready at the Dual Port M.
4= AC80 running or ready to run DCB
Protocol (=DeviceNet).
5= AC80 application blocked.
6= DCB communication is reconfigured.
99 = Fatal error in DCB communication.

7-4 Use of DeviceNet Protocol in AC80

 Chapter 7 – Fault Tracing

The output pins of the DCBAID block (continued)

Pin Name of Meaning
Number Pin
18 DCBERR Fatal error in DCB communication when
DCBERR not zero. See error code listing in
Chapter 10.
19 DCBSPEC Special information for DCB communication
inside AC80 CPU.
• If DCBERR is not zero then DCBSPEC
may give more information.
• If DCBERR is zero then DCBSPEC is
used as a counter indicating that
DCBAID in the AC80 application
program is working.
20 NCBSTAT DCB communication status inside NCB
board.
0= AC80 system not operative.
1= DCB communication undefined.
2= NCB board ready to receive DCB
definitions.
3= DCB definition written to the AMC
table.
4= FBA type matches with DCB
definition.
5= Final DCB parameter list expected
from the FBA.
6= DCB parameter list written to the
Dual Port Memory (between AC80,
NCB and CPU).
7= Not in use.
8= VCI buffer headers ready for FBA.
9= NCB board running or ready to run
DCB protocol (= DeviceNet).
10 = DCB protocol blocked.
11 = DCB protocol reconfigured.
12 = Fatal failure detected with FBA.
99 = Fatal error with DCB communication.
21 NCBERR Error in DCB communication realized by
NCB board.
0 = No error.
> 0 See error code list in Chapter 10.

Use of DeviceNet Protocol in AC80 7-5

Chapter 7 – Fault Tracing

The output pins of the DCBAID block (continued)

Pin Name of Meaning
Number Pin
22 NCBSPEC Special information for DCB communication
inside NCB board.
• If NCBERR is not zero then NCBSPEC
may give more information about error.
• IF NCBERR is zero then NCBSPEC is
used as a counter indicating that the
DCB specific software of NCB board is a
working.
23 FBASTAT DCB communication status inside FBA
module
0= DDCS link not ok
1= DDCS communication with data sets
running between FBA and NCB.
2= DDCS communication with service
messages opened between FBA and
NCB.
3= Identification data of FBA sent to NCB.
4= DCB definition received from NCB.
5= DCB parameters approved.
6= Final DCB parameters sent to NCB.
7= Not in use.
8= VCI buff. Headers received from
AC80.
9= VCI buffer headers checked.
10= Not in use
11= Profibus-DP communication start.
12= FBA running or ready to run DCB
protocol (= DeviceNet).
13= FBA blocked DCB communication.
14= DCB communication reconfigured.
99= Fatal error in DCB communication.
24 FBAERR An some error in DCB communication
detected by FBA.
0 = No error.
> 0 See error code list in Chapter 10.

7-6 Use of DeviceNet Protocol in AC80

 Chapter 7 – Fault Tracing

The output pins of the DCBAID block (continued)

Pin Name of Meaning
Number Pin
25 FBASPEC Special information for DCB communication
inside FBA.
• If FBAERR is not zero then FBASPEC
may give more information about error.
• If FBAERR is zero then FBASPEC is
used as a counter indicating that
DeviceNet master is sending data. If
DCBSPEC does not change then the DN
master does not send data to FBA.
30 PARVAL Shows the actual value of a DCB parameter
the index of which is specified by the PARID
input pin.
31 VCIMAX Shows how many VCI buffers are available
to DeviceNet protocol.
32 VCIUSED Shows how many VCI buffers are needed by
the AC80 application program.
40 VCIVAL Shows the requested value from a VCI
buffer header specified by the VCIADDR pin
(1…32, 0 = not in use). Offset from the
header start is given via pin VCIOFFS.
99 ERRC Shows error code indicating what is wrong in
using DCBAID. See list in Chapter 10.

Special A special diagnostics tool, DriveDebug, is included in the AC80

software package. If the FCB tool is not available or DriveDebug is
Diagnostics for preferred, then it can be used for supervision or diagnostics (see
DeviceNet at NCB DriveDebug User’s Manual).
Board
By means of this tool any RAM memory location on the NCB board
can be read from or written to. DriveDebug must be used very
carefully because writing to any memory location may be
dangerous.

A few DriveDebug windows are pre-defined in the software package

801sw010 (or later) in order to help finding DeviceNet problems.
Three different windows are described below.

Use of DeviceNet Protocol in AC80 7-7

Chapter 7 – Fault Tracing

DeviceNet parameters window:

These parameters are described in Chapter 6. Default values are

defined in the Fieldbus Adapter NDNA-80 but application specific
adjustments are defined in the Database element DCB01 by the
AC80 application designer. Illegal parameter values are given in
brackets and shown in red colour.

FBA data and semaphores window:

This window includes mainly similar values compared to the output

pins of the DCBAID function blocks but some values are missing,
some added. Illegal values are given in brackets and shown in red
colour on the screen of the DriveDebug tool.

• Parameter 115.02 DISABLE NCB indicates whether the NCB

programs are running or not.

7-8 Use of DeviceNet Protocol in AC80

 Chapter 7 – Fault Tracing

• Variable AC_status indicates whether the AC80 application is

running or not.
• Variable fb_configured indicates whether the NCB board is
aware of the DCB protocol configuration in the AC80 application.
• Variable DCB_Cond_flag is only for test purpose.
• DCB_Stat_DPM, DCB_Error_code_DPM,
DCB_Spec_info_DPM, NCB_Stat_DPM,
NCB_Error_code_DPM, NCB_Spec_info_DPM,
FBA_Stat_DPM, FBA_Error_code_DPM and
FBA_Spec_info_DPM are described in Chapter 6.
• When communication is working normally then
DCB_Spec_info_DPM, NCB_Spec_info_DPM and
FBA_Spec_info_DPM are used as counters having changing
values.

Basic window of DeviceNet diagnostic:

Conficuration:
• The 1st column consists of counters counting open commands
sent by the Fieldbus adapter.
•
nd
The 2 column consists of counters counting errors in open
commands.
•
rd
The 3 column consists of latest error codes detected in open
trials.
• The following 3 columns include the respective counters and
codes for close commands sent by Fieldbus Adapter.

Use of DeviceNet Protocol in AC80 7-9

Chapter 7 – Fault Tracing

• The 7th column includes counters for datasets addressed to

separate VCI buffers.
•
th
The 8 column includes counters for dataset errors.
• The 9th column includes variables for error codes.

7 - 10 Use of DeviceNet Protocol in AC80

 Chapter 8 – DeviceNet Master Configuration

Overview This chapter describes the DeviceNet communication protocol for the
NDNA-80 and the configuration of the scanner. For detailed
information on DeviceNet communication, refer to ODVA DeviceNet
Specifications Release 2.0.

Introduction to DeviceNet is a protocol based on CAN technology. CAN specifies the

physical layer interface. DeviceNet specifies the wiring, and the data
DeviceNet transfer through CAN.

The NDNA-80 is a device acting as a Group 2 Only Server realising

the Predefined Master Slave Connection Set functionality. The Offline
Connection Set functionality and UCMM are not supported.

Object Modelling One of the main features of DeviceNet is Object modelling. A group
of Objects can be described with a Functional Profile.
and Functional
Profiles
Assembly Object I/O Assembly Instances may also be referred to as Block Transfer of
data. Intelligent devices, such as the NDNA-80, realising a Functional
Profile have several objects. Since it is not possible to transmit more
than one Object data through a single Connection, it is practical and
more efficient to group Attributes from different Objects into a single
I/O connection (for example a Polled Connection) using the Assembly
Object. The Assembly Object acts as a tool for grouping these
attributes.

The Assembly Selections described above are in fact Instances of

the Assembly Object Class. The NDNA-80 uses Static Assemblies (in
other words, fixed groupings of different object data only). These are
predefined and cannot be changed.

The NDNA-80 communicates with the AC80 mainly using fast cyclic
data set communication.

1747-SDN The 1747-SDN Scanner for the SLC 500 is used in the examples in
this manual, but the concepts demonstrated in the examples apply to
Configuration the 1771-SDN Scanner for the PLC 5 as well.

The 1747-SDN is configured in the example below using the 1787-

MGR DeviceNet Manager tool (version 3.004), which defines the
scan list for the DeviceNet Scanner. The information in this manual is
intended to be a short summary. Further details on how to configure
the Scanner are found from the Scanner documentation and the
DeviceNet Manager documentation.

Use of DeviceNet Protocol in AC80 8-1

Chapter 8 – DeviceNet Master Configuration

Software Setup The Scanner scan table and data transfer is defined with the
DeviceNet manager software. This short description will go through
step by step how to configure a Scanner to communicate with the
AC80 with the Poll service. Note! In the following pictures the FBA
type is NDNA-02 version 2.1 but with AC80 it is NDNA-80 version 1.0
or later.

Creating the EDS The AC80 controller must be ‘introduced’ to DeviceNet Manager in
order to define the functionalities supported by the NDNA-80. This is
File done by adding the NDNA-80 specific EDS (Electronic Data Sheet)
file to DeviceNet Manager’s device list. EDS files for AC80 controller
are available from your local ABB representative, but can also be
created with DeviceNet Manager. The EDS file needs to be copied to
(or created with) DeviceNet Manager only once.

The EDS file can be created manually in off-line mode or

automatically in on-line mode. To do this, start DeviceNet Manager
and establish the on-line network connection through the network
adapter from the Utilities menu. Use the baudrate defined for the
connected NDNA-80 and for the planned network.

After the network connection is successfully established, select

Utilies – Create EDS Stub. This will bring up the dialogue box shown
below.

Figure 8 - 1

To upload the data press the ‘Load from Device’ button. Choose the
MAC ID of the connected NDNA-80.

After the data is succesfully uploaded, the fields are updated with the
information received from NDNA-80 as shown below.

8-2 Use of DeviceNet Protocol in AC80

 Chapter 8 – DeviceNet Master Configuration

Figure 8 - 2

Note: The fields for connection information are not updated

automatically. They can be filled manually after uploading from
NDNA-80. This is not mandatory because this information acts only
as default information which can be altered later during scanlist
editing.

If you wish to create the EDS file manually, the on-line mode is not
needed and the fields in ‘Create EDS Stub’ dialogue can be updated
manually with the information given in the figure above.

On-line Network The network and scanlists can be configured in off-line mode and
then downloaded to the devices in on-line mode. The following
Configuration
example describes the basic procedure for on-line configuration.
Please refer to the DeviceNet Manager manual for further details on
off-line and on-line configuration.

Connect Devices Before entering on-line configuration, at least the Scanner must be
present in the network with MAC ID and baudrate correctly selected.
To verify this, establish the on-line connection and perform the
‘Network Who’ function from the Who menu. After scanning the
network, the devices detected are displayed in the result display like
shown in the following figure.

Use of DeviceNet Protocol in AC80 8-3

Chapter 8 – DeviceNet Master Configuration

Figure 8 - 3

The Manager software works with projects. One project contains

Define Project
information on one or many separate DeviceNet networks. To define
a new project, select File – New Project, and fill in the dialogue box
like depicted below.

Figure 8 - 4

8-4 Use of DeviceNet Protocol in AC80

 Chapter 8 – DeviceNet Master Configuration

Define Network After defining the project, the DeviceNet network must be added. This
is done with the dialogue box shown in the figure below.

Figure 8 - 5

Add Devices to Now the NDNA-80 modules and the Scanner must be added to the
network. This is done by dragging and dropping from the Device List.
Network
While doing this, select the MAC IDs so that they correspond to those
used. The finished network is shown below.

Figure 8 - 6

Use of DeviceNet Protocol in AC80 8-5

Chapter 8 – DeviceNet Master Configuration

Configure Scanner The Scanner module must be configured to scan the selected nodes
on the network, and to ‘map’ the drive data to the Block Transfer
Tables. To do this, double-click the Scanner icon on the display. A
scanner configuration dialogue is shown in the figure below.

Figure 8 - 7

To set the scan list, select the Edit Scan List button. This will bring up
the dialogue box where the actual mapping is done, as shown below.

Figure 8 - 8 The Scan List Editor.

To add devices to the scan list, press the Add Devices From Proj.
button. In the resulting display you need to drag and drop the two
NDNA-80 icons on the Scanner icon. Press OK. The scanlist is
updated as shown in the following figure.

8-6 Use of DeviceNet Protocol in AC80

 Chapter 8 – DeviceNet Master Configuration

Figure 8 - 9 Devices added to the Scanlist.

After a drive has been added to the scanlist, the I/O parameters can
be defined. By default, the I/O connection formats used are the ones
selected in the EDS file. They can however be altered at this stage.
To do this press the Edit I/O Parameters button. The following
dialogue box is displayed.

Figure 8 - 10 Editing I/O parameters. Polled Connection chosen.

In NDNA-80, all the possible selections can not be chosen. In this

example, the Polled Connection with a Rx/Tx size of 4 bytes is
chosen which corresponds to the data size defined by the BASIC
SPEED assembly.

Use of DeviceNet Protocol in AC80 8-7

Chapter 8 – DeviceNet Master Configuration

After the I/O connection editing is done, the data mapping between
the DeviceNet network and the Block Transfer (to the PLC) must be
defined. The easiest way to do this is to select the Auto Map
command. The mapping can be reviewed with the Datatable Map
command.

Downloading the The selected configuration must be downloaded to the Scanner. For
this, the PLC must be in program mode. You cannot download the
Configuration configuration to the Scanner while the PLC is executing the ladder
logic. To download, press the Save To SDN button. You need to
select the scope of the download (in this example from 1 to 2).

After the download the PLC needs to be set to the Run mode in order
to start operation. Resetting the NDNA-80 modules may also be
required in some cases.

8-8 Use of DeviceNet Protocol in AC80

 Chapter 9 – Electronic Data Sheets for DeviceNet

General The Electronic Data Sheet for NDNA-80 need to be loaded for the
Master equipment. These sheets are available from the local ABB
Information and representative.
Compatibility
EDS files can be configured either with A special tool or they can be
configured as an ASCII character file which can be loaded to the
Master equipment.

In principle the same Electronic Data Sheets can be used both for the
NDNA-80 and the NDNA-02 apart from some alterations for the
NDNA-80.

E.g. for Allen-Bradley SLC 500 family the EDS file of NDNA-80 could
look like as follows:
$ DeviceNet Manager Generated Electronic Data Sheet
[File]
DescText = "AC80 with DeviceNet";
CreateDate = 04-04-99;
CreateTime = [Link];
ModDate = 04-04-99;
ModTime = [Link];
Revision = 1.00;

[Device]
VendCode = 46;
$ Vendor Code
ProdType = 0;
$ Product Type
ProdCode = 12;
$ Product Code
MajRev = 1;
$ Major Rev
MinRev = 00;
$ Minor Rev
VendName = "ABB Industrial Systems";
ProdTypeStr = "Generic device";
ProdName = "NDNA-80 Version V1.0";
Catalog = "";

[IO_Info]
Default = 0X0001;
PollInfo = 0X0001, 1, 1;

Input1 = 242;
Output1 = 242;

[ParamClass]
MaxInst=0;
Descriptor=0;
CfgAssembly=0;

[Params]

Use of DeviceNet Protocol in AC80 9-1

Chapter 9 – Eloctronic Data Sheets for DeviceNet

[EnumPar]

[Groups]
E.g. For the 1756-DNB scanner of the Control Logix PLC the EDS file
can be created by the software tool RS Networx for DeviceNet and
down-loaded to the scanner.

Open PC tool for Control Logix network.

RS NetWorx for DeviceNet

Revision File [Link].0

Product 2.11.51

Rockwell Software Inc.

6600 Beta Drive

Mayfield Village, OH, USA

Technical Support 440 – 646 – 7800

440 – 646 - 7801

Communication definitions:
• Interscan delay 20ms (polled)
• Foreground to backgraound poll ratio 1
• Slot 5
• Expected packet rate 75ms
• Polled mode
• RX size 242 bytes
• TX size 242 bytes
• Poll rate every scan
Download to DeviceNet scanner

9-2 Use of DeviceNet Protocol in AC80

 Chapter 10 – Appendices

APPENDIX A
Data Base
DCB Link: Base Part Channels
Element DCB01 [Link] 1..

NAME RECS1 IND1

FBATYPE RECSIZE1 VAL1
PROTOCOL RECS2 IND2
RECSIZE2 VAL2
IND3
VAL3
IND4
VAL4
IND5
VAL5
IND6
VAL6
IND7
VAL7
IND8
VAL8
IND9
VAL9

Figure 10 - 1 DB element DCB01

DCBAID
Management of -1 CHAN ERR 10
-2 PARID FAIL 11
FBA -3 VCIADDR FBATYPE 12
Communications -4 VCIOFFS PROTOCS 13
PC Element HWVERS 14
SWVERS 15
DCBAID DATE 16
DCBSTAT 17
DCBERR 18
DCBSPEC 19
NCBSTAT 20
NCBERR 21
NCBSPEC 22
FBASTAT 23
FBAERR 24
FBASPEC 25
PARVAL 30
VCIMAX 31
VCIUSED 32
VCIVAL 40
ERRC 99

Figure 10 - 2 DCBAID

Use of DeviceNet Protocol in AC80 10 - 1

Chapter 10 - Appendices

Overview DCBAID PC element makes it possible to use FBA

(=FieldBusAdapter) modules connected to the AC80’s NCB board. It
is intended for general management of the link between NCB and
FBA, and also for debugging of communication start up.
One instance of DCBAID must exist in every application program that
contains DCBRX elements (or other FBA communication elements).
DCBAID should not be inserted more than once in any application
program.

Type Circuit TC DN24WEXC

F=0-F2 IDENT RDY 4
DN24WEXC -1 EN ERR 5
-3 >CLEAR STATUS 6

-10 IN1 OUT1 50

-11 IN2 OUT2 51
-12 IN3 OUT3 52
-13 IN4 OUT4 53
-14 IN5 OUT5 54
-15 IN6 OUT6 55
-16 IN7 OUT7 56
-17 IN8 OUT8 57
-18 IN9 OUT9 58
-19 IN10 OUT10 59
-20 IN11 OUT11 60
-21 IN12 OUT12 61
-22 IN13 OUT13 62
-23 IN14 OUT14 63
-24 IN15 OUT15 64
-25 IN16 OUT16 65
-26 IN17 OUT17 66
-27 IN18 OUT18 67
-28 IN19 OUT19 68
-29 IN20 OUT20 69
-30 IN21 OUT21 70
-31 IN22 OUT22 71
-32 IN23 OUT23 72
-33 IN24 OUT24 73
ERRC 99

Figure 10 - 3 DN24WEXC

10 - 2 Use of DeviceNet Protocol in AC80

 Chapter 10 - Appendices

Disintegrated Type
Circuit DN24WEXC
DCBRX
PC Element F=1-F1 CHAN RDY 4
F=0-F2 SPECIAL ERR 5
DCBRX F=0-F3 >STATION STATUS 6
F=0-F4 IDENT LASTPIN 7
F=0-F5 CONFIG VCI_IN 8
-1 EN VCI_OUT 9
-2 >INIT
-3 >CLEAR

-10 IN1 OUT1 50

-11 IN2 OUT2 51
-12 IN3 OUT3 52
-13 IN4 OUT4 53
-14 IN5 OUT5 54
-15 IN6 OUT6 55
-16 IN7 OUT7 56
-17 IN8 OUT8 57
-18 IN9 OUT9 58
-19 IN10 OUT10 59
-20 IN11 OUT11 60
-21 IN12 OUT12 61
-22 IN13 OUT13 62
-23 IN14 OUT14 63
-24 IN15 OUT15 64
-25 IN16 OUT16 65
-26 IN17 OUT17 66
-27 IN18 OUT18 67
-28 IN19 OUT19 68
-29 IN20 OUT20 69
-30 IN21 OUT21 70
-31 IN22 OUT22 71
-32 IN23 OUT23 72
-33 IN24 OUT24 73
ERRC 99

Figure 10 - 4 DCBRX

Use of DeviceNet Protocol in AC80 10 - 3

Chapter 10 - Appendices

APPENDIX B -
General
Using Standard It is possible to use the standard DeviceNet adapter NDNA-01 with
the AC80 when the needed amount of data is restricted (max. 6
NDNA-01 with
words in both directions) and no parameter communication is
AC80 required.

The following rules must be followed:

• For hardware installation see manual: Installation and start-up /
DeviceNet Adapter Module NDNA-01.
• The DataBase element DCB01 is forbidden.
• The type circuits DNxxWEXC / function blocks DCBRX are
forbidden.
• The function block DCBAID is unnecessary.

Configuration • Install the ToolBox option into the AC80 application (otherwise it
is impossible to insert the necessary type circuit into the
application)
• Insert the type circuit DN_6WDS into the AC80 [Link]
type circuit contains both input and output functions. You can use
only one instance of this type circuit in an AC80 application.
• Because no DataBase element DCB01 in AC80 application for
DeviceNet communication exists, the parameter definitions must
be done with DriveDebug.
• Restart the NDNA-01 module.
• Start DriveDebug tool and open the "DeviceNet DN_6WDS
parameters" window (Menu = MonWin/OpenMonitorWindow...)
Especially you must know and specify the station address (=MAC ID)
for NDNA-01. It should be written into parameter 109.02 MAC ID.

First the parameter values can be e.g. as follows:

109.01 *NDN’
109.02 0…63 ; MAC ID.
109.03 0 ; Baud rate
109.04 1
109.05 0
109.06 3
109.07 3
109.08 3
109.09 default
109.10 1

10 - 4 Use of DeviceNet Protocol in AC80

 Chapter 10 - Appendices

Startup • Connect the NDNA-01 to the AC80 (plastic fibres to the channel 2
of the NCB board, nearest to the base of the AC80)
• Disconnect the DeviceNet cable from NDNA-01
• Check (with DriveDebug) the NCB parameter 105.10 = FFFFFF
and the parameters mentioned above.
• Reset NDNA-01 (Switch power supply off and on). Now you
should see communication running for a while between the FBA
and the AC80 .
• Reconnect the DeviceNet cable and restart the DeviceNet master
station.
• Restart the NDNA-01 module again.
If the communication is running well, you will see it from the output
pins of the DN_6WDS type circuit.

Use of DeviceNet Protocol in AC80 10 - 5

Chapter 10 - Appendices

APPENDIX C –
Error Codes for
DCB Protocols /
DeviceNet
Communication Displayed by FAIL Pin of DCBAID
Error Codes 1000 No Data base element DCB01 exists.
1100 Duplicate instance of DCBAID.
1101 Illegal VCI buffer number.

Displayed by ERRCpin of DCBRX

1000 No Data base element DCB01 in the AC80 application.
1001 VCI buffers can not be created because DCB01 failed.
1200 RECSIZE1 definition too short in the DCB01 element
1201 No data length configured for a VCI buffer.
1202 Illegal definition in the CONFIG pin of a DCBRX.
1203 Illegal definition in the CONFIG pin of a DCBRX.
1204 Illegal definition in the CONFIG pin of a DCBRX
1205 No more VCI buffers available.
1206 Illegal channel number.
1207 Duplicate definition for an IDENT value.
2000 NCB non-functional / missing.
2001 Too long start-up time for this DCBRX.
3000 Too long time gap for receiving data from the FBA.
3001 Too long time gap for data request by given FBA.
3002 Time-out for ACK waiting from FBA.
3003 Too long initial waiting for the first input data from FBA.
5002 This DCBRX tried to use a VCI buffer in wrong direction.
5003 This DCBRX tried open a VCI buffer which was open.
5004 This DCBRX tried to close a VCI buffer which was
closed
5005 This DCBRX tried to use a buffer which did not exist.

Displayed by DCBERR Pin of DCBAID

1000 No DCB01 exists.
1002 RECS1 and/or RECSIZE1 too high in DCB01.

Displayed by NCBERR Pin of DCBAID

8192 FBATYPE definition in DCB01 does not match with FBA.
8193 Operation with protected group in AMC table.
8194 Operation with protected index in AMC table.
8195 Operation with illegal group number in AMC table.
8196 Operation with undefined group in AMC table.
8197 Operation with illegal index in AMC table.
8198 Operation with undefined index in AMC table.
8199 Operation with illegal format in AMC table.
8208 Operation with illegal selection in AMC table.
8209 Operation with reserved group in AMC table.
16001 Temporary illegal value in the state machine NCBSTAT.

10 - 6 Use of DeviceNet Protocol in AC80

 Chapter 10 - Appendices

Displayed by FBAERR Pin of DCBAID

16000 Time-out in communication between NCB and FBA
21400 Common error code for DeviceNet (undefined reason).
21401 Illegal IDENT value in a DCBRX block / type circuit.
21402 Illegal partner type in a DCBRX configuration.
21403 Illegal data type in a DCBRX configuration.
21404 Illegal data length in a DCBRX configuration.
21405 Illegal structure in a DCBRX configuration.
21406 Illegal overwrite definition in a DCBRX configuration.
21407 Illegal CHAN pin value in a DCBRX configuration.
21408 Duplicate IDENT definition in a DCBRX configuration
(reference).
21409 Duplicate IDENT definition in a DCBRX configuration
(feedback).
21410 Receiving of DCB parameter definition by FBA failed.
21411 Illegal DCB protocol code at the DCB01 element.
21412 DCB definition block to FBA was corrupted.
21413 DCB parameter index too high
21414 DCB parameter index illegal.
21415 DCB parameter value too high.
21416 DCB parameter value too low.
21417 Illegal value detected in FBASTAT state machine.
21418 Opening of a VCI buffer failed: Illegal library flag value.
21419 Opening of a VCI buffer failed: Erroneous/missing
header.
21420 Opening of a VCI buffer failed: Time-out.
21421 Opening of a VCI buffer failed: VCI not ready
(temporary).
21422 Opening of a VCI buffer failed: VCI disabled.
21423 Opening of a VCI buffer failed: AC80 blocked.
21424 Opening of a VCI buffer failed: VCI reconfigured.
21430 Opening of a VCI buffer failed: Unknown command.
21431 Opening of a VCI buffer failed: Unknown error.
21432 Not in use.
21433 Opening of a VCI buffer failed: VCI not closed.
21434 Opening of a VCI buffer failed: Illegal VCI number.
21435 Opening of a VCI buffer failed: Not buffer pair.
21436 Opening of a VCI buffer failed: Direction forbidden.
21437 Opening of a VCI buffer failed: VCI buffer not defined.
21439 Opening of a VCI buffer failed: Open sequence error.
21440 Not in use.
21441 Not in use.
21442 Data transfer failed between FBA and NCB.
21443 Closing of a VCI buffer failed.
21461 Multi-subaddress mode not defined.

Use of DeviceNet Protocol in AC80 10 - 7

 EFFECTIVE: 10.05.2000
3BFE 64336886 R0125

ABB Industry Oy
Drives
[Link] 184
FIN-00381 Helsinki
FINLAND
Telephone + 358 10 22 2000
Telefax + 358 10 22 22681