ABB FDNA 01 User Manual

Options for ABB drives, converters and inverters  
User’s manual  
FDNA-01 DeviceNet adapter module  
User’s manual  
FDNA-01 DeviceNet adapter module  
Table of contents  
1. Safety  
4. Mechanical installation  
5. Electrical installation  
6. Start-up  
3AFE68573360 Rev E  
EN  
EFFECTIVE: 2012-04-04  
© 2012 ABB Oy  
All Rights Reserved.  
Table of contents  
5
Table of contents  
1. Safety  
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11  
Use of warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12  
Safety in installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13  
2. About the manual  
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15  
Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15  
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15  
Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16  
Purpose of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16  
Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16  
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17  
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18  
Terms and abbreviations used in this manual . . . . . . . . . . . . . . 19  
General terms and abbreviations . . . . . . . . . . . . . . . . . . . . 19  
DeviceNet terms and abbreviations . . . . . . . . . . . . . . . . . . . 20  
3. Overview of the DeviceNet network and the FDNA-01  
module  
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23  
DeviceNet network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23  
Example topology of the DeviceNet link . . . . . . . . . . . . . . . 24  
FDNA-01 DeviceNet adapter module . . . . . . . . . . . . . . . . . . . . 25  
Layout of the adapter module . . . . . . . . . . . . . . . . . . . . . . . 26  
4. Mechanical installation  
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27  
Delivery check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27  
Mounting the adapter module . . . . . . . . . . . . . . . . . . . . . . . . . . 28  
5. Electrical installation  
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29  
 
6 Table of contents  
Connecting the module to the DeviceNet network . . . . . . . . . . . 30  
6. Start-up  
Drive configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34  
DeviceNet connection configuration . . . . . . . . . . . . . . . . . . 34  
FDNA-01 configuration parameters – group A (group 1) 35  
FDNA-01 configuration parameters – group B (group 2) 47  
FDNA-01 configuration parameters – group C (group 3) 48  
Control locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49  
Parameter setting examples – ACS355 . . . . . . . . . . . . . . . . 50  
ABB Drives profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50  
ODVA AC/DC drive profile . . . . . . . . . . . . . . . . . . . . . . . 52  
Starting up ACSM1 drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54  
Parameter setting examples – ACSM1 . . . . . . . . . . . . . . . . 55  
ABB Drives profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55  
ODVA AC/DC drive profile . . . . . . . . . . . . . . . . . . . . . . . 57  
Starting up ACS850 and ACQ810 drives . . . . . . . . . . . . . . . . . . 59  
Parameter setting examples – ACS850 and ACQ810 . . . . . 60  
ABB Drives profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60  
ODVA AC/DC drive profile . . . . . . . . . . . . . . . . . . . . . . . 63  
Starting up ACS880 drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65  
Parameter setting examples – ACS880 . . . . . . . . . . . . . . . . 65  
ABB Drives profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65  
ODVA AC/DC drive profile . . . . . . . . . . . . . . . . . . . . . . . 67  
Configuring the master station . . . . . . . . . . . . . . . . . . . . . . . . . . 70  
EDS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70  
Configuring an Allen-Bradley® PLC . . . . . . . . . . . . . . . . . . 71  
7. Communication profiles  
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77  
Communication profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77  
ODVA AC/DC drive profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79  
ODVA output attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79  
Run Forward & Run Reverse  
(Control supervisor object). . . . . . . . . . . . . . . . . . . . . . . 80  
Net Ctrl (Control supervisor object) . . . . . . . . . . . . . . . . 80  
Net Ref (AC/DC drive object). . . . . . . . . . . . . . . . . . . . . 80  
ODVA input attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83  
Faulted (Control supervisor object) . . . . . . . . . . . . . . . . 83  
Running Reverse (Control supervisor object) . . . . . . . . 83  
Ready (Control supervisor object) . . . . . . . . . . . . . . . . . 83  
Ctrl From Net (Control supervisor object) . . . . . . . . . . . 83  
Ref From Net (AC/DC drive object) . . . . . . . . . . . . . . . . 83  
At Reference (AC/DC drive object) . . . . . . . . . . . . . . . . 84  
State (Control supervisor object) . . . . . . . . . . . . . . . . . . 84  
Speed Actual (AC/DC drive object) . . . . . . . . . . . . . . . . 86  
Torque Actual (AC/DC drive object). . . . . . . . . . . . . . . . 87  
ABB Drives communication profile . . . . . . . . . . . . . . . . . . . . . . . 88  
Control word and Status word . . . . . . . . . . . . . . . . . . . . . . . 88  
Control word contents . . . . . . . . . . . . . . . . . . . . . . . . . . 88  
Status word contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 91  
State machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93  
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94  
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94  
Actual values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95  
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95  
8. Communication protocol  
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97  
DeviceNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97  
Object modeling and functional properties . . . . . . . . . . . . . . . . . 97  
8 Table of contents  
Assembly objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98  
Basic speed control plus drive parameters assembly . . . . . 99  
Extended speed control assembly . . . . . . . . . . . . . . . . . . . 101  
Basic speed and torque control  
plus drive parameters assembly . . . . . . . . . . . . . . . . . . . . 105  
Extended speed and torque control assembly . . . . . . . . . . 108  
Extended speed and torque control  
plus drive parameters assembly . . . . . . . . . . . . . . . . . . . . 109  
ABB Drives profile with set speed  
plus drive parameters assembly . . . . . . . . . . . . . . . . . . . . 112  
ABB Drives profile with set speed and  
set torque assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115  
ABB Drives profile with set speed and set torque  
plus drive parameters assembly . . . . . . . . . . . . . . . . . . . . 116  
Transparent 16 with one assembly . . . . . . . . . . . . . . . . . . 118  
Transparent 16 with one assembly plus drive parameters 119  
Transparent 16 with two assembly . . . . . . . . . . . . . . . . . . 121  
Transparent 16 with two assembly plus drive parameters . 122  
Transparent 32 with one assembly . . . . . . . . . . . . . . . . . . 125  
Transparent 32 with one assembly plus drive parameters 126  
Transparent 32 with two assembly . . . . . . . . . . . . . . . . . . 128  
Transparent 32 with two assembly plus drive parameters . 130  
Class objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133  
Identity object, class 01h . . . . . . . . . . . . . . . . . . . . . . . . . . 134  
Class attributes (Instance #0). . . . . . . . . . . . . . . . . . . . 134  
Instance attributes (Instance #1) . . . . . . . . . . . . . . . . . 135  
Attribute explanations. . . . . . . . . . . . . . . . . . . . . . . . . . 135  
DeviceNet object, class 03h . . . . . . . . . . . . . . . . . . . . . . . . 137  
Class attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137  
Instance attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138  
Connection object, class 05h . . . . . . . . . . . . . . . . . . . . . . . 138  
Class attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139  
Table of contents  
9
Instance attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139  
Class attributes (Instance #0) . . . . . . . . . . . . . . . . . . . 141  
Instance attributes (Instance #1) . . . . . . . . . . . . . . . . . 141  
Motor data object, class 28h . . . . . . . . . . . . . . . . . . . . . . . 142  
Class attributes (Instance #0) . . . . . . . . . . . . . . . . . . . 142  
Instance attributes (Instance #1) . . . . . . . . . . . . . . . . . 143  
Control supervisor object, class 29h . . . . . . . . . . . . . . . . . 143  
Class attributes (Instance #0) . . . . . . . . . . . . . . . . . . . 144  
Instance attributes (Instance #1) . . . . . . . . . . . . . . . . . 144  
AC/DC-drive object, class 2Ah . . . . . . . . . . . . . . . . . . . . . 146  
Class attributes (Instance #0) . . . . . . . . . . . . . . . . . . . 146  
Instance attributes (Instance #1) . . . . . . . . . . . . . . . . . 146  
Drive parameter object, Class 90h . . . . . . . . . . . . . . . . . . 147  
Fieldbus configuration object 91h . . . . . . . . . . . . . . . . . . . 148  
Class attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148  
Instance #1: FDNA-01 configuration parameters  
group A (group 1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148  
Instance #2: FDNA-01 configuration parameters  
group B (group 2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151  
Instance #3: FDNA-01 configuration parameters  
group C (group 3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152  
9. Diagnostics  
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155  
LED indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156  
10. Technical data  
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159  
FDNA-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160  
DeviceNet link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161  
11. Appendix A – Varying the number of drive parame-  
ters  
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163  
Modification of the EDS file . . . . . . . . . . . . . . . . . . . . . . . . . . . 163  
10 Table of contents  
Further information  
Product and service inquiries . . . . . . . . . . . . . . . . . . . . . . . . . . 167  
Product training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167  
Providing feedback on ABB Drives manuals . . . . . . . . . . . . . . 167  
Document library on the Internet . . . . . . . . . . . . . . . . . . . . . . . 167  
Safety 11  
1
Safety  
What this chapter contains  
The chapter presents the warning symbols used in this manual and  
the safety instructions which you must follow when installing an  
optional module into a drive, converter or inverter. If ignored,  
physical injury or death may follow, or damage may occur to the  
equipment. Read this chapter before you start the installation.  
     
12 Safety  
Use of warnings  
Warnings caution you about conditions which can result in serious  
injury or death and/or damage to the equipment and advise on how  
to avoid the danger. The following warning symbols are used in  
this manual:  
Electricity warning warns of hazards from electricity  
which can cause physical injury and/or damage to the  
equipment.  
General warning warns about conditions, other than  
those caused by electricity, which can result in physical  
injury and/or damage to the equipment.  
 
Safety 13  
Safety in installation  
These warnings are intended for all who install an optional module  
into a drive, converter or inverter.  
WARNING! Ignoring the following instructions can cause  
physical injury or death, or damage to the equipment.  
Only qualified electricians are allowed to install and maintain  
the drive, converter or inverter!  
Disconnect the drive, converter or inverter into which the  
module will be installed from all possible power sources. After  
disconnecting, always wait for 5 minutes to let the intermediate  
circuit capacitors discharge before you proceed.  
Do not work on the control cables when power is applied to the  
external control circuits of the drive, converter or inverter.  
Externally supplied control circuits may carry dangerous  
voltage.  
 
14 Safety  
About the manual 15  
2
About the manual  
What this chapter contains  
This chapter introduces this manual.  
Applicability  
This manual applies to the FDNA-01 DeviceNet adapter module  
(+K451), SW version 0.223 or later.  
Compatibility  
The FDNA-01 DeviceNet adapter module is compatible with the  
following drives:  
ACS355  
ACSM1  
ACS850  
ACQ810  
ACS880.  
The FDNA-01 DeviceNet adapter module is compatible with all  
master stations that support the DeviceNet™ protocol.  
       
16 About the manual  
Target audience  
The reader is expected to have a basic knowledge of fieldbus  
interface, electrical fundamentals, electrical wiring practices and  
how to operate the drive.  
Purpose of the manual  
The manual provides information on installing, commissioning and  
using an FDNA-01 DeviceNet adapter module.  
Related manuals  
The related manuals are listed below.  
Code (English)  
Drive user’s manuals  
ACS355 drives (0.37…22 kW,  
0.5…30 hp) user’s manual  
Drive hardware manuals and  
guides  
ACSM1-204 regen supply modules 3AUA0000053713  
(5.3 to 61 kW) hardware manual  
ACSM1-04 drive modules (0.75 to 3AFE68797543  
45 kW) hardware manual  
ACSM1-04 drive modules (55 to 110 3AFE68912130  
kW) hardware manual  
ACSM1-04Lx liquid-cooled drive  
modules (55 to 160 kW) hardware  
manual  
ACS850-04 (0.37…45 kW)  
hardware manual  
ACS850-04 (55…160 kW, 75…200 3AUA0000045487  
hp) hardware manual  
ACS850-04 (200…500 kW,  
250…600 hp) hardware manual  
ACQ810-04 drive modules  
(0.37…45 kW, 0.5…60 hp) hardware  
manual  
ACQ810-04 drive modules (55 to  
160 kW, 75 to 200 hp) hardware  
manual  
       
About the manual 17  
Code (English)  
ACQ810-04 drive modules  
(200…400 kW, 250…600 hp)  
hardware manual  
ACS880-01 (0.55 to 250 kW, 0.75 to 3AUA0000078093  
350 hp) hardware manual  
Drive firmware manuals and  
guides  
ACSM1 motion control program  
firmware manual  
ACSM1 speed and torque control  
program firmware manual  
ACSM1 regen supply control  
program firmware manual  
ACS850 standard control program 3AUA0000045497  
firmware manual  
ACQ810 standard pump control  
program firmware manual  
ACS880 primary control program  
firmware manual  
Option manuals and guides  
FDNA-01 DeviceNet adapter module 3AFE68573360  
user’s manual  
You can find manuals and other product documents in PDF format  
on the Internet. See section Document library on the Internet on  
the inside of the back cover. For manuals not available in the  
Document library, contact your local ABB representative.  
Before you start  
It is assumed that the drive is installed and ready to operate before  
you start the installation of the adapter module.  
In addition to conventional installation tools, have the drive  
manuals available during the installation as they contain important  
information not included in this manual. The drive manuals are  
referred to at various points of this manual.  
 
18 About the manual  
Contents  
The manual consists of the following chapters:  
Safety presents the safety instructions which you must follow  
when installing a fieldbus adapter module.  
About the manual introduces this manual.  
Overview of the DeviceNet network and the FDNA-01 module  
contains a short description of the DeviceNet network and the  
adapter module.  
Mechanical installation contains a delivery checklist and  
instructions on mounting the adapter module.  
Electrical installation contains cabling and bus termination  
instructions and instructions on connecting the module to the  
DeviceNet network.  
Start-up presents the steps to take during the start-up of the  
drive with the adapter module and gives examples of  
configuring the master system.  
Communication profiles describes the communication profiles  
used in the communication between the DeviceNet network,  
the adapter module and the drive.  
Communication protocol describes the DeviceNet  
communication protocol for the adapter module and the  
configuration of the scanner.  
Diagnostics explains how to trace faults with the status LEDs  
on the adapter module.  
Technical data contains the technical data of the adapter  
module and the DeviceNet link.  
Appendix A – Varying the number of drive parameters  
describes how to reduce the number of drive parameter  
members in FDNA-01 assemblies by modifying the EDS file.  
 
About the manual 19  
Terms and abbreviations used in this manual  
General terms and abbreviations  
Term  
Explanation  
Command word  
See Control word.  
Communication module Communication module is a name for a device  
(eg, a fieldbus adapter) through which the drive  
is connected to an external communication  
network (eg, a fieldbus). The communication  
with the module is activated with a drive  
parameter.  
Control word  
16-bit or 32-bit word from master to slave with  
bit-coded control signals (sometimes called the  
Command word).  
DCU profile  
DTC  
Drive Control Unit profile, native profile used in  
the ACS350 and ACS355 drives  
Direct Torque Control is a motor control method  
for AC drives. DTC allows accurate control of  
both motor speed and torque without pulse  
encoder feedback from the motor shaft.  
FBA profile  
Fieldbus Adapter profile, native profile used in  
the ACQ810, ACS850 and ACSM1 drives  
FDNA-01 DeviceNet  
adapter module  
One of the optional fieldbus adapter modules  
available for ABB drives. FDNA-01 is a device  
through which an ABB drive is connected to a  
DeviceNet serial communication bus.  
LSW  
Least significant word  
Most significant word  
MSW  
Parameter  
An operating instruction for the drive.  
Parameters can be read and programmed with  
the drive control panel, drive PC tools or  
through the adapter module.  
Profile  
RFG  
Adaptation of the protocol for certain application  
field, for example, drives.  
In this manual, drive-internal profiles (eg, DCU  
or FBA) are called native profiles.  
Ramp Function Generator  
   
20 About the manual  
Term  
Explanation  
Status word  
16-bit or 32-bit word from slave to master with  
bit-coded status messages  
DeviceNet terms and abbreviations  
Term  
Explanation  
Change of State/Cyclic  
Message  
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 Message may be returned in  
response to this message.  
CIP™  
Common Industrial Protocol (CIP) is an  
industrial protocol for industrial automation  
applications. It is managed by ODVA.  
EDS File  
Electronic Data Sheet (EDS) file identifies the  
properties of the device to the DeviceNet  
Scanner. Each type of drive and application  
program requires its own EDS file.  
Input  
In the ODVA DeviceNet specification the word  
‘input’ is used to describe data flow from a  
device (such as FDNA-01) to the network.  
I/O assembly selection  
Smart networked devices (like FDNA-01) can  
produce and/or consume more than one I/O  
value. Typically, they produce and/or consume  
one or more I/O value, as well as status and  
diagnostic information. Each piece of data  
communicated by a device is represented by an  
attribute of one of the device’s 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  
Every node on DeviceNet network has to have  
a unique identifier. This node number is called  
MAC ID (Media Access Control Identifier).  
 
About the manual 21  
Term  
Explanation  
ODVA™  
ODVA stands for Open DeviceNet Vendor  
Association. ODVA is an independent  
organization that promotes interoperativity  
between different manufacturers’ DeviceNet  
products. ABB is an Associate Member at  
ODVA.  
Output  
In the ODVA DeviceNet specification the word  
‘output’ is used to describe data flow from the  
network into a device (such as FDNA-01).  
Poll Message  
Most DeviceNet Scanners as well as the FDNA-  
01 module support two different data services.  
These are Poll and Change of State/Cyclic  
messages.  
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, FDNA-01 always acts as a slave). A  
master must transmit a separate Poll Command  
Message for each 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.  
Scanlist  
DeviceNet Scanner communicates with the  
DeviceNet slaves in a user-defined order. This  
order of communication is the scanlist. The  
scanlist contains a complete list of the slave  
nodes and the order in which the slaves are  
accessed.  
22 About the manual  
Overview of the DeviceNet network and the FDNA-01 module 23  
3
Overview of the DeviceNet  
network and the FDNA-01  
module  
What this chapter contains  
This chapter contains a short description of the DeviceNet network  
and the FDNA-01 DeviceNet adapter module.  
DeviceNet network  
The DeviceNet network has a linear bus topology. Terminating  
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.  
The maximum length of the trunk cable depends on the data rate  
and on the type of the cable used (see chapter Technical data).  
       
24 Overview of the DeviceNet network and the FDNA-01 module  
Example topology of the DeviceNet link  
An example of an allowable topology is shown below.  
Trunk line  
Tap  
Node  
Node  
Tap  
Node  
Node  
Node  
Node  
Terminating  
Resistor  
Tap  
Tap  
Node  
Node  
Drop line  
Node  
Node  
Node  
 
Overview of the DeviceNet network and the FDNA-01 module 25  
FDNA-01 DeviceNet adapter module  
The FDNA-01 DeviceNet Adapter module is an optional device for  
ABB drives. It enables the connection of the drive to a DeviceNet  
network. The drive is considered a slave in the DeviceNet network.  
Through the adapter module you can:  
give control commands to the drive (for example, Start, Stop,  
Run enable)  
feed a motor speed or torque reference to the drive  
give the actual value or reference of the process to the PID  
controller of the drive  
read status information and actual values from the drive  
change drive parameter values  
reset a drive fault.  
The adapter module acts as a class 2 slave only with predefined  
master-slave connection set services. These include the explicit  
messaging, the poll-response service and the change of state/  
cyclic service. The DeviceNet commands and services supported  
by the adapter module are described in chapter Communication  
protocol.  
The adapter module is mounted into an option slot on the motor  
control board of the drive. See the drive manuals for the module  
placement options.  
 
26 Overview of the DeviceNet network and the FDNA-01 module  
Layout of the adapter module  
Diagnostic LEDs  
(see chapter Diagnostics)  
Bus connector X1  
(see chapter Electrical  
installation)  
Mounting screw  
 
Mechanical installation 27  
4
Mechanical installation  
What this chapter contains  
This chapter contains a delivery checklist and instructions on  
mounting the adapter module.  
WARNING! Follow the safety instructions given in this  
manual and the drive documentation.  
Delivery check  
The option package for the adapter module contains:  
DeviceNet adapter module, type FDNA-01  
this manual.  
       
28 Mechanical installation  
Mounting the adapter module  
The adapter module is to be inserted into its specific position in the  
drive. The module is held in place with plastic pins and one screw.  
The screw also provides the electrical connection between the  
module and drive frame for cable shield termination.  
When the module is installed, the signal and power connection to  
the drive is made through a 20-pin connector. (All drives do not use  
all the available signals so the connector on the drive may have  
fewer pins.)  
Mounting procedure:  
1. Insert the module carefully into its position on the drive.  
2. Fasten the screw.  
Note: It is essential to install the screw properly to fulfill the EMC  
requirements and to ensure the proper operation of the module.  
For more information on mounting, see the drive manuals.  
 
Electrical installation 29  
5
Electrical installation  
What this chapter contains  
This chapter contains:  
general cabling instructions  
instructions on connecting the module to the DeviceNet  
network  
instructions on switching on the bus termination.  
WARNING! Before installation, switch off the drive power  
supply. Wait five minutes to ensure that the capacitor bank  
of the drive is discharged. Switch off all dangerous  
voltages connected from external control circuits to the inputs and  
outputs of the drive.  
General cabling instructions  
Arrange the bus cables as far away from the motor cables as  
possible.  
Avoid parallel runs.  
Use bushings at cable entries.  
       
30 Electrical installation  
Connecting the module to the DeviceNet network  
Connect the bus cable to terminal block X1 on the adapter module.  
Terminal block description  
X1  
Description  
1
2
3
4
5
V-  
Network power supply ground (0V DC)  
CAN_L bus line  
CAN_L  
SHLD  
CAN_H  
V+  
Network cable shield  
CAN_H bus line  
Network power supply source (24V DC)  
Connection examples  
5-pin micro-style connector:  
0 V  
+24 V  
Network  
power supply  
Male micro-style  
connector  
2
1
5
4
3
V-  
CAN_L  
SHLD  
CAN_H  
V+  
3
2
FDNA  
X1  
4
1
5
5-pin mini-style connector:  
0 V  
Network  
power supply +24 V  
Male mini-style  
connector  
3
2
1
5
4
3
V-  
CAN_L  
SHLD  
CAN_H  
V+  
FDNA  
X1  
4
2
5
1
     
Electrical installation 31  
Standard open-style screw connector:  
+24 V  
0 V  
Network  
power supply  
V-  
CAN_L  
SHLD  
CAN_H  
V+  
FDNA  
X1  
Switching on the bus termination  
The adapter module does not provide bus termination. The  
DeviceNet network should be terminated at both ends of the trunk  
cable with a 121 ohm, ¼ W, 1% metal film resistor. Connect the  
resistor between the two signal wires (CAN_H, CAN_L) on the  
DeviceNet cable, as shown in the figure below.  
Scanner  
Node 1  
Node n  
CAN_H  
121  
Ω
121  
1%  
Metal Film  
1/4 W  
Ω
CAN_L  
1%  
Metal Film  
1/4 W  
Further information on the DeviceNet protocol is available at  
 
32 Electrical installation  
Start-up 33  
6
Start-up  
What this chapter contains  
This chapter contains:  
information on configuring the drive for operation with the  
adapter module  
drive-specific instructions on starting up the drive with the  
adapter module  
examples of configuring the master station for communication  
with the adapter module.  
WARNING! Follow the safety instructions given in this  
manual and the drive documentation.  
     
34 Start-up  
Drive configuration  
The following information applies to all drive types compatible with  
the adapter module, unless otherwise stated.  
DeviceNet connection configuration  
After the adapter module has been mechanically and electrically  
installed according to the instructions in chapters Mechanical  
installation and Electrical installation, the drive must be prepared  
for communication with the module.  
The detailed procedure of activating the module for DeviceNet  
communication with the drive depends on the drive type. Normally,  
a parameter must be adjusted to activate the communication. See  
the drive-specific start-up procedures starting on page 49.  
Once communication between the drive and the adapter module  
has been established, several configuration parameters are copied  
to the drive. These parameters are shown in the tables below and  
must be checked first and adjusted where necessary.  
Note: Not all drives display descriptive names for the configuration  
parameters. To help you identify the parameters in different drives,  
the names displayed by each drive are given in grey boxes in the  
tables.  
Note: The new settings take effect only when the adapter module  
is powered up the next time or when the fieldbus adapter refresh  
parameter is activated.  
Note: If communication between the adapter module and  
DeviceNet master is established, changes to the configuration  
parameters can be done also through Fieldbus configuration object  
91h.  
   
Start-up 35  
FDNA-01 configuration parameters – group A (group 1)  
Note: The actual parameter group number depends on the drive  
type. Group A (group 1) corresponds to:  
parameter group 51 in ACS355, ACSM1, ACS850 and  
ACQ810  
parameter group 51 in ACS880 if the adapter is installed as  
fieldbus adapter A or group 54 if the adapter is installed as  
fieldbus adapter B.  
No. Name/Value  
Description  
Default  
01  
FBA TYPE  
Read-only. Shows the fieldbus adapter type as 1 = Devi-  
detected by the drive. Value cannot be adjusted ceNet  
by the user.  
If the value is 0 = None, the communication  
between the drive and the module has not been  
established.  
02  
MAC ID  
Defines the MAC ID number for the drive the  
adapter module is connected to. Each device  
on the DeviceNet network must have a unique  
MAC ID number.  
63  
ACS355:  
FB PAR 2  
ACSM1:  
FBA PAR2  
ACS850/ACQ810:  
FBA par2  
ACS880:  
MAC ID  
0…63  
MAC ID  
03  
BAUD RATE  
Read-only. Indicates the detected  
0 = 125  
communication speed in kbit/s.  
kbit/s  
ACS355:  
FB PAR 3  
ACSM1:  
FBA PAR3  
ACS850/ACQ810:  
FBA par3  
ACS880:  
Baud rate  
0 = 125 kbit/s  
1 = 250 kbit/s  
2 = 500 kbit/s  
Communication speed is 125 kbit/s.  
Communication speed is 250 kbit/s.  
Communication speed is 500 kbit/s.  
             
36 Start-up  
No. Name/Value  
Description  
Default  
04  
DRIVE PROFILE  
Defines the communication used between the  
0 =  
module and the drive (not fieldbus and module). Native  
ACS355:  
FB PAR 4  
If a drive supports more than one drive profile,  
this parameter is used to select the preferred  
profile. Presently, to use the ODVA and ABB  
Drives profiles, the drive must support a native  
profile (eg, DCU or FBA). Transparent16 and  
Transparent32 profiles may be used with any  
drive profile.  
prof  
ACSM1:  
FBA PAR4  
ACS850/ACQ810:  
FBA par4  
ACS880:  
Drive profile  
0 = Native prof  
Native profile of the drive selected  
05  
ODVA STOP  
FUNC  
Used with the ODVA AC/DC drive profile.  
Determines how the motor is stopped when a  
stop command is received via DeviceNet.  
0 = Ramp  
stop  
ACS355:  
FB PAR 5  
ACSM1:  
FBA PAR5  
ACS850/ACQ810:  
FBA par5  
ACS880:  
ODVA stop func  
0 = Ramp stop  
Motor decelerates along the active deceleration  
ramp.  
1 = Coast stop  
Motor comes to a stop by coasting.  
       
Start-up 37  
No. Name/Value  
Description  
Default  
06  
OUTPUT  
INSTANCE  
Configures the output assembly instances used 20  
by the adapter module. Tables below list the  
supported assemblies and allowed  
combinations. For the descriptions of the  
assembly instances, see section Assembly  
objects on page 98.  
ACS355:  
FB PAR 6  
ACSM1:  
FBA PAR6  
ACS850/ACQ810:  
FBA par6  
ACS880:  
Output instance  
Name  
Output  
Input  
Default  
Profile  
instance instance input  
size  
(bytes)  
Basic speed control  
20  
21  
70  
71  
4
ODVA AC/DC drive  
ODVA AC/DC drive  
Extended speed  
control  
4
Basic speed and  
torque control  
22  
72  
6
ODVA AC/DC drive  
ODVA AC/DC drive  
ODVA AC/DC drive  
ODVA AC/DC drive  
Extended speed and 23  
torque control  
73  
6
Basic speed control  
plus drive parameters  
120  
170  
171  
24  
24  
Extended speed  
control plus drive  
parameters  
121  
122  
Basic speed and  
torque control plus  
drive parameters  
172  
173  
26  
26  
ODVA AC/DC drive  
ODVA AC/DC drive  
Extended speed and 123  
torque control plus  
drive parameters  
ABB Drives profile  
with set speed  
801  
802  
851  
852  
4
6
ABB Drives  
ABB Drives  
ABB Drives profile  
with set speed and  
set torque  
(continued)  
       
38 Start-up  
No. Name/Value  
Name  
Description  
Output  
Default  
Input  
Default  
Profile  
instance instance input  
size  
(bytes)  
(continued)  
ABB Drives profile  
with set speed plus  
drive parameters  
901  
902  
951  
952  
24  
ABB Drives  
ABB Drives  
ABB Drives profile  
with set speed and  
set torque plus drive  
parameters  
26  
24  
ABB Drives profile  
with set speed plus  
drive parameters  
901  
951  
ABB Drives  
Transparent16 with  
one  
811  
812  
911  
861  
862  
961  
4
Transparent16  
Transparent16  
Transparent16  
Transparent16 with  
two  
6
Transparent16 with  
one plus drive  
parameters  
24  
Transparent16 with  
two plus drive  
parameters  
912  
962  
26  
Transparent16  
Transparent32 with  
one  
821  
822  
921  
871  
872  
971  
8
Transparent32  
Transparent32  
Transparent32  
Transparent32 with  
two  
12  
28  
Transparent32 with  
one plus drive  
parameters  
Transparent32 with  
two plus drive  
parameters  
922  
972  
32  
Transparent32  
 
Start-up 39  
No. Name/Value  
Description  
Default  
Note: With ACSM1, ACQ810, ACS850 and ACS880, when using the ODVA  
AC/DC drive or ABB Drives profile, make sure that drive parameter 50.04 FBA  
REF MODESEL is set to SPEED. With ACSM1, ACS850 and ACS880, make  
sure that 50.05 FBA REF2 MODESEL is set to TORQUE.  
Input  
ODVA  
ABB DRIVES  
TRANSPARENT16 TRANSPARENT32  
(70-73; 170-173) (851-852; 951-952 (861-862; 961-962) (871-872; 971-972)  
ODVA  
(20-23; 120-123)  
x
ABB DRIVES  
(801-802; 901-902)  
x
x
x
TRANSPARENT16  
(811-812; 911-912)  
TRANSPARENT32  
(821-822; 921-922)  
For alternative values, see column Output  
instance in the table describing parameter 06  
OUTPUT INSTANCE.  
07  
OUTPUT NUM  
PARS  
Some assembly instances support transferring 10  
drive parameter values between the I/O  
scanner and drive. Parameters 07 OUTPUT  
NUM PARS and 09 INPUT NUM PARS specify  
how many drive parameter values should be  
included in the respective assembly instance.  
Changing the numbers of the drive parameters  
to values other than the defaults also changes  
the lengths of the associated assembly  
instances. This requires manual changes to  
either the EDS file or I/O scanner configuration.  
Before changing these parameters, consult  
Appendix A – Varying the number of drive  
parameters.  
ACS355:  
FB PAR 7  
ACSM1:  
FBA PAR7  
ACS850/ACQ810:  
FBA par7  
ACS880:  
Output num pars  
Note: This parameter is only used when the  
output assembly instance is 120, 121, 122, 123,  
901, 902, 911, 912, 921, 922. It must always be  
set to the default, 10, except as described in  
Appendix A – Varying the number of drive  
parameters  
110  
Number or drive parameter values to be  
included in the assembly instance  
       
40 Start-up  
No. Name/Value  
Description  
Default  
08  
INPUT INSTANCE Configures the input assembly instances used  
70  
by the adapter module. See parameter 06  
OUTPUT INSTANCE.  
ACS355:  
FB PAR 9  
ACSM1:  
FBA PAR9  
ACS850/ACQ810:  
FBA par9  
ACS880:  
Input instance  
For alternative values, see parameter 06  
OUTPUT INSTANCE.  
09  
INPUT NUM  
PARS  
See parameter 07 OUTPUT NUM PARS.  
Note: This parameter is only used when the  
input assembly instance is 170, 171, 172, 173,  
951, 952, 961, 962, 971, 972. It must always be  
set to the default, 10, except as described in  
Appendix A – Varying the number of drive  
parameters.  
10  
ACS355:  
FB PAR 9  
ACSM1:  
FBA PAR9  
ACS850/ACQ810:  
FBA par9  
ACS880:  
Input num pars  
110  
Number or drive parameter values to be  
included in the assembly instance  
           
Start-up 41  
No. Name/Value  
Description  
Default  
10  
ODVA SPEED  
SCALE  
Defines the speed scale in the ODVA AC/DC  
drive profile. Units of reference and actual  
speeds for the ODVA AC/DC drive profile are  
given by the formula below. No effect on the  
ABB Drives profiles.  
Note: While a wide range of resolutions may be  
configured, the actual performance is limited to  
the performance capabilities of the drive.  
128  
ACS355:  
FB PAR 10  
ACSM1:  
FBA PAR10  
ACS850/ACQ810:  
FBA par10  
(-1 X ODVA speed scale value)  
Speed unit = RPM X 2  
ACS880:  
ODVA speed scale  
Table below shows how the values of drive  
parameter ODVA SPEED SCALE correspond  
to the ODVA Speed Scale units.  
1)  
ODVA speed scale value Speed scale value of Unit  
2)  
drive parameter  
-5  
123  
124  
125  
126  
127  
128  
129  
130  
131  
132  
133  
32 RPM  
-4  
16 RPM  
-3  
8 RPM  
-2  
4 RPM  
-1  
2 RPM  
0 (default)  
1 RPM  
1
2
3
4
0.5 RPM  
0.25 RPM  
0.125 RPM  
0.0625 RPM  
0.03125 RPM  
5
1)  
Use the ODVA speed scale value when reading/writing parameter ODVA  
SPEED SCALE via AC/DC-drive object, class 2Ah. When written via the  
AC/DC drive object, the new value takes effect immediately.  
2)  
Use the speed scale value of the drive parameter when reading/writing  
parameter ODVA SPEED SCALE via the drive control panel, Drive parameter  
object, Class 90h and Fieldbus configuration object 91h. When written via  
these methods, the new value takes effect after the drive is repowered or a  
“Fieldbus Adapter Parameter refresh” is given.  
123133  
Speed scale value of the drive parameter  
     
42 Start-up  
No. Name/Value  
Description  
Default  
11  
ODVA TORQUE  
SCALE  
Defines the torque scale in the ODVA AC/DC  
drive profile. Units of reference and actual  
torques for the ODVA AC/DC drive profile are  
given by the formula below. No effect on the  
ABB Drives profiles.  
Note: While a wide range of resolutions may be  
configured, the actual performance is limited to  
the performance capabilities of the drive.  
(N·m = Newton x Meter)  
128  
ACS355:  
FB PAR 11  
ACSM1:  
FBA PAR11  
ACS850/ACQ810:  
FBA par11  
ACS880:  
ODVA torque  
scale  
(-1 X ODVA torque scale)  
Torque unit = N·m x 2  
Table below shows how the values of drive  
parameter ODVA TORQUE SCALE correspond  
to the ODVA Torque Scale units.  
1)  
ODVA torque scale value Torque scale value of Unit  
2)  
drive parameter  
-5  
123  
124  
125  
126  
127  
128  
129  
130  
131  
132  
133  
32 N·m  
-4  
16 N·m  
-3  
8 N·m  
-2  
4 N·m  
-1  
2 N·m  
0 (default)  
1 N·m  
1
2
3
4
0.5 N·m  
0.25 N·m  
0.125 N·m  
0.0625 N·m  
0.03125 N·m  
5
1)  
Use the ODVA torque scale value when reading/writing parameter ODVA  
TORQUE SCALE via AC/DC-drive object, class 2Ah. When written via the  
AC/DC drive object, the new value takes effect immediately.  
2)  
Use the torque scale value of the drive parameter when reading/writing  
parameter ODVA TORQUE SCALE via the drive control panel, Drive  
parameter object, Class 90h and Fieldbus configuration object 91h. When  
written via these methods, the new value takes effect after the drive is  
repowered or a “Fieldbus Adapter Parameter refresh” is given.  
123133  
Torque scale value of the drive parameter  
Not used by the adapter module.  
12  
25  
Reserved  
N/A  
         
Start-up 43  
No. Name/Value  
Description  
Default  
26  
UNRECOVER-  
ABLE ERROR  
Read-only. Shows information about the cause  
of an unrecoverable error in the adapter  
module. Bit field parameter, that is, several  
status bits can be set at a time. Value 0  
indicates that there are no errors.  
0
ACS355:  
FB PAR 26  
ACSM1:  
FBA PAR26  
ACS850/ACQ810:  
FBA par26  
ACS880:  
Unrecover. error  
Bit Name  
Value Description  
1
2
3
4
5
6
7
DUP_MAC_ERROR  
0x0001 Duplicate MAC ID error  
RX_QUEUE_OVERRUN  
TX_QUEUE_OVERRUN  
IO_SEND_ERROR  
CAN_BUS_OFF  
CAN_OVERRUN  
DNS_RESET  
0x0002 Message receive queue is full.  
0x0004 Message transmit queue is full.  
0x0008 Transmitting I/O data has failed.  
0x0010 Bus-off is detected.  
0x0020 CAN message was lost.  
0x0040 DeviceNet driver of the module is  
reset.  
8
9
DNS_BUS_SENSE_ERROR 0x0080 No voltage detected in the  
network.  
DNS_SWITCH_ERROR  
0x0100 DeviceNet driver reset failed due  
to an invalid MAC ID or baud rate.  
13 SYS_FILE_ERR  
0x1000 Initialization with the drive failed.  
065535  
Active unrecoverable errors  
27  
FBA PAR  
REFRESH  
Validates any changed adapter module  
configuration parameter settings. After  
refreshing, the value reverts automatically to  
0 = Done.  
Note: This parameter cannot be changed while  
the drive is running.  
0 = Done  
ACS355/ACSM1:  
FBA PAR  
REFRESH  
ACS850/ACQ810/  
ACS880:  
FBA par refresh  
0 = Done  
Refreshing done  
Refreshing  
1 =  
Refresh/Configure  
       
44 Start-up  
No. Name/Value  
Description  
Default  
28  
PAR TABLE VER  
Read-only. Displays the parameter table  
revision of the fieldbus adapter module  
mapping file stored in the memory of the drive.  
In format xyz, where  
x = major revision number  
y = minor revision number  
z = correction number  
N/A  
ACS355:  
FILE CPI FW REV  
ACSM1:  
PAR TABLE VER  
ACS850/ACQ810/  
ACS880:  
Par table ver  
OR  
in format axyz, where  
a = major revision number  
xy = minor revision numbers  
z = correction number or letter.  
0x0000…0xFFFF  
Parameter table revision  
29  
DRIVE TYPE  
CODE  
Read-only. Displays the drive type code of the N/A  
fieldbus adapter module mapping file stored in  
the memory of the drive.  
ACS355:  
FILE CONFIG ID  
ACSM1:  
DRIVE TYPE  
CODE  
ACS850/ACQ810/  
ACS880:  
Drive type code  
0…65535  
Drive type code of the fieldbus adapter module  
mapping file  
30  
MAPPING FILE  
VER  
Read-only. Displays the fieldbus adapter  
module mapping file revision stored in the  
memory of the drive in decimal format.  
Example: 0x107 = revision 1.07.  
N/A  
ACS355:  
FILE CONFIG  
REV  
ACSM1:  
MAPPING FILE  
VER  
ACS850/ACQ810/  
ACS880:  
Mapping file ver  
0…65535  
Mapping file revision  
           
Start-up 45  
No. Name/Value  
Description  
Default  
31  
D2FBA COMM  
STA  
Read-only. Displays the status of the fieldbus  
adapter module communication.  
0 = Idle  
Note: The value names may vary by drive.  
ACS355:  
FBA STATUS  
ACSM1:  
D2FBA COMM  
STA  
ACS850/ACQ810/  
ACS880:  
D2FBA comm sta  
0 = Idle  
Adapter is not configured.  
Adapter is initializing.  
1 = Exec.init  
2 = Time out  
Time-out has occurred in the communication  
between the adapter and the drive.  
3 = Conf.err  
Adapter configuration error: Major or minor  
revision code of the common program revision  
in the fieldbus adapter module is not the  
revision required by the module or mapping file  
upload has failed more than three times.  
4 = Off-line  
5 = On-line  
6 = Reset  
Adapter is off-line.  
Adapter is on-line.  
Adapter is performing a hardware reset.  
32  
FBA COMM SW  
VER  
Read-only. Displays the common program  
revision of the adapter module in format axyz,  
where:  
N/A  
ACS355:  
FBA CPI FW REV  
a = major revision number  
xy = minor revision numbers  
z = correction number or letter.  
Example: 190A = revision 1.90A  
ACSM1:  
FBA COMM SW  
VER  
ACS850/ACQ810/  
ACS880:  
FBA comm SW  
ver  
0x0000…0xFFFF  
Common program version of the adapter  
module  
       
46 Start-up  
No. Name/Value  
Description  
Default  
33  
FBA APPL SW  
VER  
Read-only. Displays the application program  
revision of the adapter module in format axyz,  
where:  
N/A  
ACS355:  
FBA CPI APPL  
REV  
a = major revision number  
xy = minor revision numbers  
z = correction number or letter.  
Example: 190A = revision 1.90A  
ACSM1:  
FBA COMM APPL  
VER  
ACS850/ACQ810/  
ACS880:  
FBA appl SW ver  
0x0000…0xFFFF  
Application program revision of the adapter  
module  
   
Start-up 47  
FDNA-01 configuration parameters – group B (group 2)  
Note: The actual parameter group number depends on the drive  
type. Group B (group 2) corresponds to:  
parameter group 55 in ACS355  
parameter group 53 in ACSM1, ACS850 and ACQ810  
parameter group 53 in ACS880 if the adapter is installed as  
fieldbus adapter A or group 56 if the adapter is installed as  
fieldbus adapter B.  
1)  
No.  
01  
Name/Value  
Description  
Default  
DATA OUT 1  
(master to drive)  
In the output assembly instances that include  
drive parameters, this parameter specifies  
which parameter’s value is placed in location  
DATA OUT 1 value received by the drive from  
the DeviceNet network. Content is defined by a  
decimal number in the range of 0 to 9999 as  
follows:  
0
ACS355:  
FBA DATA OUT 1  
ACSM1:  
FBA DATA OUT1  
ACS850/ACQ810/  
ACS880:  
FBA data out1  
0
Not used  
1…99 Virtual address area of drive control.  
Not used with the FDNA-01 module.  
101… Parameter area of the drive  
9999  
Note: The FDNA-01 configuration parameters  
are 16-bit parameters. If the mapped parameter  
is a 32-bit parameter, it automatically reserves  
two consecutive parameters. For example,  
mapping a 32-bit parameter to parameter no. 1  
also reserves parameter no. 2.  
0
Not used  
101…9999  
Parameter index with format xxyy, where xx is  
the parameter group number (1…99) and yy is  
the parameter number index within that group  
(01…99).  
02DATA OUT 2…  
See parameter DATA OUT 1.  
0
10  
DATA OUT 10  
1)  
The number of parameters in this group may vary by drive type and drive firmware.  
       
48 Start-up  
FDNA-01 configuration parameters – group C (group 3)  
Note: The actual parameter group number depends on the drive  
type. Group C (group 3) corresponds to:  
parameter group 54 in ACS355  
parameter group 52 in ACSM1, ACS850 and ACQ810  
parameter group 52 in ACS880 if the adapter is installed as  
fieldbus adapter A or group 55 if the adapter is installed as  
fieldbus adapter B.  
1)  
No.  
01  
Name/Value  
Description  
Default  
DATA IN 1  
(drive to master)  
In input assembly instances that include drive  
parameters, this parameter specifies which  
parameter’s value is placed in location DATA IN  
1 value sent by the drive to the DeviceNet  
network. Content is defined by a decimal  
number in the range of 0 to 9999 as follows:  
0
ACS355:  
FBA DATA IN 1  
ACSM1:  
FBA DATA IN1  
0
Not used  
ACS850/ACQ810/  
ACS880:  
FBA data in1  
1…99 Virtual address area of drive control.  
Not used with the FDNA-01 module.  
101… Parameter area of the drive  
9999  
Note: The FDNA-01 configuration parameters  
are 16-bit parameters. If the mapped parameter  
is a 32-bit parameter, it automatically reserves  
two consecutive parameters. For example,  
mapping a 32-bit parameter to parameter no. 1  
also reserves parameter no. 2.  
0
Not used  
101…9999  
Parameter index with format xxyy, where xx is  
the parameter group number (1…99) and yy is  
the parameter number index within that group  
(01…99).  
02DATA IN 2…  
See parameter DATA IN 1.  
0
10  
DATA IN 10  
1)  
The number of parameters in this group may vary by drive type and drive firmware.  
       
Start-up 49  
Control locations  
ABB drives can receive control information from multiple sources  
including digital inputs, analog inputs, the drive control panel and a  
communication module (for example, the adapter module). ABB  
drives allow the user to separately determine the source for each  
type of control information (Start, Stop, Direction, Reference, Fault  
Reset, and so on).  
To give the fieldbus master station the most complete control over  
the drive, the communication module must be selected as the  
source for this information. The parameter setting examples below  
contain the drive control parameters needed in the examples. For  
a complete parameter list, see the drive documentation.  
Starting up ACS355 drives  
1. Power up the drive.  
2. Enable the communication between the adapter module and  
the drive by setting parameter 9802 COMM PROT SEL to EXT  
FBA.  
3. Set the FDNA-01 configuration parameters in parameter group  
51.  
At the minimum, set the required number in parameter 5102  
MAC ID and the required baud rate in 5103 BAUD RATE. In  
addition, select the communication profile in 5104 DRIVE  
PROFILE. With the ODVA AC/DC drive profile select the way  
in which the motor is stopped in 5105 ODVA STOP FUNC.  
4. Define the process data transferred to and from the drive in  
FDNA-01 parameter groups 54 and 55.  
Note: If communication between the FDNA-01 and DeviceNet  
master is established, changes to the configuration parameters  
can be done also through Fieldbus configuration object 91h.  
5. Validate the settings made in parameter group 51 by setting  
parameter 5127 FBA PAR REFRESH to REFRESH.  
   
50 Start-up  
6. Set the relevant drive control parameters to control the drive  
according to the application. Examples of appropriate values  
are shown in the tables below.  
Parameter setting examples – ACS355  
ABB Drives profile  
This example shows how to configure the ACS355 drive to use the  
ABB Drives profile with set speed and set torque plus drive  
parameters assembly.  
The used I/O assembly instances are 902 and 952.  
The table below gives the recommended drive parameter settings.  
Drive parameter  
Setting for  
Description  
ACS355 drives  
9802 COMM PROT SEL  
4 = EXT FBA  
Enables communication between  
drive and adapter module.  
1)  
5101 FBA TYPE  
DEVICENET  
Displays the type of the adapter  
module.  
5102 FB PAR 2  
(MAC ID)  
2
Defines the MAC ID number of the  
adapter module.  
5103 FB PAR 3  
(BAUD RATE)  
0 (= 125 kbit/s)  
Sets the baud rate for the  
DeviceNet interface.  
5104 FB PAR 4  
(DRIVE PROFILE)  
0 (= DCU Profile) Selects the profile used in the  
communication between drive and  
adapter module.  
5105 FB PAR 5  
(ODVA STOP FUNC)  
0 (= Ramp)  
Motor decelerates along the active  
deceleration ramp.  
5106 FB PAR 6  
(OUTPUT INSTANCE)  
902  
Selects the ABB Drives profile with  
speed and torque plus drive  
parameters output instance.  
5107 FB PAR 7  
(OUTPUT NUM PARS)  
10  
Must always be set to 10, except as  
provided in Appendix A – Varying  
the number of drive parameters.  
5108 FB PAR 8  
(INPUT INSTANCE)  
952  
Selects the ABB Drives profile with  
speed and torque plus drive  
parameters input instance.  
   
Start-up 51  
Drive parameter  
Setting for  
Description  
ACS355 drives  
5109 FB PAR 9  
(INPUT NUM PARS)  
10  
Must always be set to 10, except as  
provided in Appendix A – Varying  
the number of drive parameters.  
5110 FB PAR 10  
(ODVA SPEED SCALE)  
128  
128  
Sets the scaling as 1 rpm for the  
ODVA speed reference.  
5111 FB PAR 11  
(ODVA TORQUE SCALE)  
Sets the scaling as 1 Nm for the  
ODVA torque reference.  
5401 FBA DATA IN 1  
5402 FBA DATA IN 2  
104  
107  
0
Current  
DC bus voltage  
5403 FB DATA IN 3  
…5410 DATA IN 10  
5501 FBA DATA OUT 1  
5502 FBA DATA OUT 2  
2205  
2206  
0
Acceleration time 2  
Deceleration time 2  
5503 FB DATA OUT 3  
…5510 DATA OUT 10  
51.27 FBA PAR REFRESH 1 = REFRESH  
Validates the FDNA-01  
configuration parameter settings.  
1001 EXT1 COMMANDS  
10 = COMM  
Selects the fieldbus interface as the  
source of the start and stop  
commands for external control  
location 1.  
1003 DIRECTION  
3 = REQUEST  
Allows control of rotation direction.  
1103 REF1 SELECT  
8 = COMM  
Selects the fieldbus reference 1 as  
the source for speed reference.  
1604 FAULT RESET SEL  
8 = COMM  
Selects the fieldbus interface as the  
source for the fault reset signal.  
9904 MOTOR CTRL MODE 2 = VECTOR:  
Selects the vector control mode as  
the motor control mode.  
TORQ  
1002 EXT2 COMMANDS  
10 = COMM  
Selects the fieldbus interface as the  
source of the start and stop  
commands for external control  
location 2.  
1102 EXT1/EXT2 SEL  
1106 REF2 SELECT  
8 = COMM  
Enables external control location  
1/2 selection through the fieldbus.  
8 = COMM  
Selects the fieldbus reference 2 as  
the source for torque reference.  
52 Start-up  
Drive parameter  
Setting for  
Description  
ACS355 drives  
1601 RUN ENABLE  
7 = COMM  
Selects the fieldbus interface as the  
source for the inverted Run enable  
signal (Run disable).  
1)  
Read-only or automatically detected/set  
The start sequence for the parameter example above is given  
below.  
Control word:  
47Eh (1150 decimal) –> READY TO SWITCH ON  
47Fh (1151 decimal) –> OPERATING (Speed mode)  
or  
C7Fh (3199 decimal) –> OPERATING (Torque mode).  
ODVA AC/DC drive profile  
The following example shows how to configure the ACS355 drive  
to use the Extended speed and torque control assembly of the  
ODVA AC/DC drive profile.  
The used I/O assembly instances are 23 and 73.  
The table below gives the recommended drive parameter settings.  
Drive parameter  
Setting for  
Description  
ACS355 drives  
9802 COMM PROT SEL  
4 = EXT FBA  
Enables communication between  
drive and adapter module.  
1)  
5101 FBA TYPE  
DEVICENET  
Displays the type of the adapter  
module.  
5102 FB PAR 2  
(MAC ID)  
5
Defines the MAC ID number of the  
adapter module.  
5103 FB PAR 3  
(BAUD RATE)  
0 (= 125 kbit/s)  
0 (= DCU Profile)  
Sets the baud rate for the  
DeviceNet interface.  
5104 FB PAR 4  
(DRIVE PROFILE)  
Selects the profile used in the  
communication between drive and  
adapter module.  
5105 FB PAR 5  
(ODVA STOP FUNC)  
0 (= Ramp)  
Motor decelerates along the active  
deceleration ramp.  
 
Start-up 53  
Drive parameter  
Setting for  
Description  
ACS355 drives  
5106 FB PAR 6  
(OUTPUT INSTANCE)  
23  
Selects the ODVA extended speed  
and torque control output instance.  
5108 FB PAR 8  
(INPUT INSTANCE)  
73  
Selects the ODVA extended speed  
and torque control input instance.  
5110 FB PAR 10  
(ODVA SPEED SCALE)  
128  
128  
Sets the scaling as 1 rpm for the  
ODVA speed reference.  
5111 FB PAR 11  
(ODVA TORQUE SCALE)  
Sets the scaling as 1 Nm for the  
ODVA torque reference.  
51.27 FBA PAR REFRESH 1 = REFRESH  
Validates the FDNA-01  
configuration parameter settings.  
1001 EXT1 COMMANDS  
10 = COMM  
Selects the fieldbus interface as  
the source of the start and stop  
commands for external control  
location 1.  
1003 DIRECTION  
3 = REQUEST  
Allows control of rotation direction.  
1103 REF1 SELECT  
8 = COMM  
Selects the fieldbus reference 1 as  
the source for speed reference.  
1604 FAULT RESET SEL  
8 = COMM  
Selects the fieldbus interface as  
the source for the fault reset  
signal.  
9904 MOTOR CTRL MODE 2 = VECTOR:  
Selects the vector control mode as  
the motor control mode.  
TORQ  
1002 EXT2 COMMANDS  
10 = COMM  
Selects the fieldbus interface as  
the source of the start and stop  
commands for external control  
location 2.  
1102 EXT1/EXT2 SEL  
1 = DI1  
Selects digital input DI1 as the  
source for the external control  
location EXT1/EXT2 selection.  
1106 REF2 SELECT  
1601 RUN ENABLE  
8 = COMM  
Selects the fieldbus reference 2 as  
the source for torque reference.  
7 = COMM  
Selects the fieldbus interface as  
the source for the inverted Run  
enable signal (Run disable).  
1)  
Read-only or automatically detected/set  
54 Start-up  
Note: In this example, digital input DI1 has been configured to  
control whether to use the speed or torque control mode.  
The start sequence for the parameter example above is given  
below.  
Control word:  
0h (0 decimal) –> READY  
1h (1 decimal) –> ENABLED (Running forward)  
2h (2 decimal) –> ENABLED (Running reverse)  
Starting up ACSM1 drives  
1. Power up the drive.  
2. Enable the communication between the adapter module and  
the drive by setting parameter 50.01 FBA ENABLE to Enable.  
3. Ensure that 50.04 FBA REF1 MODESEL is set to Speed and  
50.05 FBA REF2 MODESEL is set to Torque.  
4. Set the FDNA-01 configuration parameters in parameter group  
51.  
5. Define the process data transferred to and from the drive in  
FDNA-01 parameter groups 52 and 53.  
Note: If communication between the FDNA-01 and DeviceNet  
master is established, changes to the configuration parameters  
can be done also through Fieldbus configuration object 91h.  
6. Validate the settings made in parameter groups 51, 52 and 53  
by setting parameter 51.27 FBA PAR REFRESH to REFRESH.  
7. Set the relevant drive control parameters to control the drive  
according to the application. Examples of appropriate values  
are shown in the tables below.  
 
Start-up 55  
Parameter setting examples – ACSM1  
ABB Drives profile  
The following example shows how to configure the ACSM1 drive to  
use the ABB Drives profile.  
The used I/O assembly instances are 902 and 952.  
The table below gives the recommended drive parameter settings.  
Drive parameter  
Setting for  
Description  
ACSM1 drives  
50.01 FBA ENABLE  
1 = Enable  
Enables communication between  
drive and adapter module.  
50.04 FBA REF1  
MODESEL  
Speed  
Torque  
Selects speed as the adapter  
module REF1 type.  
50.05 FBA REF2  
MODESEL  
Selects torque as the adapter  
module REF2 type.  
1)  
51.01 FBA TYPE  
DEVICENET  
Displays the type of the adapter  
module.  
51.02 FBA PAR2  
(MAC ID)  
6
Defines the MAC ID number of the  
adapter module.  
51.03 FBA PAR3  
(BAUD RATE)  
0 (= 125 kbit/s)  
Sets the baud rate for the DeviceNet  
interface.  
51.06 FBA PAR6  
(OUTPUT INSTANCE)  
902  
Selects the ABB Drives profile with  
speed and torque plus drive  
parameters output instance.  
51.07 FBA PAR7  
(OUTPUT NUM PARS)  
10  
Must always be set to 10, except as  
provided in Appendix A – Varying  
the number of drive parameters.  
51.08 FBA PAR8  
(INPUT INSTANCE)  
952  
10  
Selects the ABB Drives profile with  
speed and torque plus drive  
parameters input instance.  
51.09 FBA PAR9  
(INPUT NUM PARS)  
Must always be set to 10, except as  
provided in Appendix A – Varying  
the number of drive parameters.  
52.01 FBA DATA IN1  
52.02 FBA DATA IN2  
52.03 FBA DATA IN3  
52.04 FBA DATA IN4  
117  
104  
0
Motor temp  
Motor current - MSW  
Motor current - LSW  
DC voltage - MSW  
107  
   
56 Start-up  
Drive parameter  
Setting for  
Description  
ACSM1 drives  
52.05 FBA DATA IN5  
52.06 FBA DATA IN6  
52.07 FBA DATA IN7  
0
DC voltage - LSW  
108  
0
Encoder 1 speed - MSW  
Encoder 1 speed - LSW  
52.08 FBA DATA IN8…  
52.10 FBA DATA IN10  
0
53.01 FBA DATA OUT1  
53.02 FBA DATA OUT2  
53.03 FBA DATA OUT3  
53.04 FBA DATA OUT4  
53.05 FBA DATA OUT5  
53.06 FBA DATA OUT6  
53.07 FBA DATA OUT7  
2503  
0
Acceleration time - MSW  
Acceleration time - LSW  
Deceleration time - MSW  
Deceleration time - LSW  
Constant speed  
2504  
0
2408  
2410  
2411  
0
Speed ref jog1  
Speed ref jog2  
53.08 FBA DATA OUT8…  
53.10 FBA DATA OUT10  
51.27 FBA PAR REFRESH 1 = REFRESH  
Validates the FDNA-01 configuration  
parameter settings.  
10.01 EXT1 START FUNC  
10.04 EXT2 START FUNC  
3 = FBA  
Selects the fieldbus interface as the  
source of the start and stop  
commands for external control  
location 1.  
3 = FBA  
Selects the fieldbus interface as the  
source of the start and stop  
commands for external control  
location 2.  
24.01 SPEED REF1 SEL  
32.01 TORQ REF1 SEL  
3 = FBA REF1  
Selects the fieldbus reference 1 as  
the source for speed reference 1.  
4 = FBA REF2  
Selects the fieldbus reference 2 as  
the source for torque reference 1.  
34.02 EXT1 MODE 1/2SEL P.2.12.15 =  
Selects FBA Control word bit 15 as  
the source for the external control  
location EXT1/EXT2 selection.  
P.FBA MAIN  
CW.15  
34.03 EXT1 CTRL MODE1 1 = Speed  
Selects speed as the control mode  
for external control location 1.  
34.05 EXT2 CTRL MODE1 2 =Torque  
Selects torque as the control mode  
for external control location 2.  
Start-up 57  
Drive parameter  
Setting for  
Description  
ACSM1 drives  
99.05 MOTOR CTRL  
MODE  
0 = DTC  
Selects DTC as the motor control  
mode.  
1)  
Read-only or automatically detected/set  
The start sequence for the parameter example above is given  
below.  
Control word:  
47Eh (1150 decimal) –> READY TO SWITCH ON  
47Fh (1151 decimal) –> OPERATING (Speed mode)  
or  
C7Fh (3199 decimal) –> OPERATING (Torque mode).  
ODVA AC/DC drive profile  
The following example shows how to configure the ACSM1 drive to  
use the ODVA AC/DC drive profile.  
The used I/O assembly instances are 23 and 73.  
The table below gives the recommended drive parameter settings.  
Drive parameter  
Setting for  
Description  
ACSM1 drives  
50.01 FBA ENABLE  
1 = Enable  
Enables communication between  
drive and adapter module.  
50.04 FBA REF1  
MODESEL  
Speed  
Torque  
Selects speed as the adapter  
module REF1 type.  
50.05 FBA REF2  
MODESEL  
Selects torque as the adapter  
module REF2 type.  
1
51.01 FBA TYPE  
DEVICENET  
Displays the type of the adapter  
module.  
51.02 FBA PAR2  
(MAC ID)  
5
Defines the MAC ID number of the  
adapter module.  
51.03 FBA PAR3  
(BAUD RATE)  
0 (= 125 kbit/s)  
Sets the baud rate for the DeviceNet  
interface.  
51.06 FBA PAR6  
(OUTPUT INSTANCE)  
23  
Selects the ODVA extended speed  
and torque control output instance.  
 
58 Start-up  
Drive parameter  
Setting for  
Description  
ACSM1 drives  
51.08 FBA PAR8  
(INPUT INSTANCE)  
73  
Selects the ODVA extended speed  
and torque control input instance.  
51.27 FBA PAR REFRESH 1 = REFRESH  
Validates the FDNA-01 configuration  
parameter settings.  
10.01 EXT1 START FUNC  
10.04 EXT2 START FUNC  
3 = FBA  
Selects the fieldbus interface as the  
source of the start and stop  
commands for external control  
location 1.  
3 = FBA  
Selects the fieldbus interface as the  
source of the start and stop  
commands for external control  
location 2  
24.01 SPEED REF1 SEL  
32.01 TORQ REF1 SEL  
34.01 EXT1/EXT2 SEL  
3 = FBA REF1  
Selects the fieldbus reference 1 as  
the source for speed reference 1.  
4 = FBA REF2  
Selects the fieldbus reference 2 as  
the source for torque reference 1.  
P.2.1.0 = PI.DI  
STATUS.0  
Selects digital input DI1 as the  
source for the external control  
location EXT1/EXT2 selection.  
34.03 EXT1 CTRL MODE1 1 = Speed  
Selects speed as the control mode  
for external control location 1.  
34.05 EXT2 CTRL MODE1 2 =Torque  
Selects torque as the control mode  
for external control location 2.  
99.05 MOTOR CTRL  
MODE  
0 = DTC  
Selects DTC as the motor control  
mode.  
1)  
Read-only or automatically detected/set  
Note: In this example, digital input DI1 has been configured to  
control whether to use the speed or torque control mode.  
The start sequence for the parameter example above is given  
below.  
Control word:  
0h (0 decimal) –> READY  
1h (1 decimal) –> ENABLED (Running forward)  
2h (2 decimal) –> ENABLED (Running reverse)  
Start-up 59  
Starting up ACS850 and ACQ810 drives  
1. Power up the drive.  
2. Enable the communication between the adapter module and  
the drive by setting parameter 50.01 Fba enable to Enable.  
3. Ensure that 50.04 Fb ref1 modesel is set to Speed (both  
ACS850 and ACQ810) and 50.05 Fb ref2 modesel is set to  
Torque (only ACS850).  
4. Set the FDNA-01 configuration parameters in drive parameter  
group 51.  
5. Define the process data transferred to and from the drive in  
FDNA-01 parameter groups 52 and 53.  
Note: If communication between the FDNA-01 and DeviceNet  
master is established, changes to the configuration parameters  
can be done also through Fieldbus configuration object 91h.  
6. Validate the settings made in parameter groups 51, 52 and 53  
by setting parameter 51.27 FBA par refresh to Refresh.  
7. Set the relevant drive control parameters to control the drive  
according to the application. Examples of appropriate values  
are shown in the tables below.  
 
60 Start-up  
Parameter setting examples – ACS850 and ACQ810  
ABB Drives profile  
The following example shows how to configure the ACS850 or  
ACQ810 drive to use the ABB Drives profile.  
The used I/O assembly instances are 902 and 952.  
The table below gives the recommended drive parameter settings.  
Drive parameter  
Setting for  
ACS850/ACQ810  
drives  
Description  
50.01 Fba enable  
1 = Enable  
Enables communication between  
drive and adapter module.  
50.04 Fb ref1 modesel  
50.05 Fb ref2 modesel  
Speed  
Torque  
Selects speed as the adapter  
module ref1 type.  
Selects torque as the adapter  
module ref2 type (only with  
ACS850).  
1)  
51.01 Fba type  
DEVICENET  
Displays the type of the adapter  
module.  
51.02 FBA par2  
(MAC ID)  
5
Defines the MAC ID number of the  
adapter module.  
51.03 FBA par3  
(BAUD RATE)  
0 (= 125 kbit/s)  
Sets the baud rate for the  
DeviceNet interface.  
51.06 FBA par6  
(OUTPUT INSTANCE)  
902  
Selects the ABB Drives profile with  
speed and torque plus drive  
parameters output instance.  
51.07 FBA par7  
(OUTPUT NUM PARS)  
10  
Must always be set to 10, except as  
provided in Appendix A – Varying  
the number of drive parameters.  
51.08 FBA par8  
(INPUT INSTANCE)  
952  
10  
Selects the ABB Drives profile with  
speed and torque plus drive  
parameters input instance.  
51.09 FBA par9  
(INPUT NUM PARS)  
Must always be set to 10, except as  
provided in Appendix A – Varying  
the number of drive parameters.  
52.01 FBA data in1  
52.02 FBA data in2  
123  
0
Motor power  
Motor power - LSW  
   
Start-up 61  
Drive parameter  
Setting for  
ACS850/ACQ810  
drives  
Description  
52.03 FBA data in3  
52.04 FBA data in4  
52.05 FBA data in5  
52.06 FBA data in6  
52.07 FBA data in7  
105  
107  
0
Motor current percent  
DC voltage  
DC voltage - LSW  
Encoder1 speed  
108  
0
Encoder 1 speed - LSW  
52.08 FBA data in8…  
52.10 FBA data in10  
0
53.01 FBA data out1  
53.02 FBA data out2  
53.03 FBA data out3  
53.04 FBA data out4  
53.05 FBA data out5  
53.06 FBA data out6  
53.07 FBA data out7  
2204  
0
Acc time 2  
Acceleration time 2 - LSW  
Dec time 2  
2205  
0
Deceleration time 2 - LSW  
Const speed1  
2606  
2607  
2608  
0
Const speed2  
Const speed3  
53.08 FBA data out8…  
53.10 FBA data out10  
51.27 FBA par refresh  
10.01 Ext1 start func  
1 = Refresh  
Validates the FDNA-01  
configuration parameter settings.  
FB  
Selects the fieldbus interface as the  
source of the start and stop  
commands for external control  
location 1.  
10.04 Ext2 Start func  
12.01 Ext1/Ext sel  
12.03 Ext1 ctrl mode  
3 = FB  
Selects the fieldbus as the source  
for start and stop commands for  
external control location EXT2 (only  
with ACS850).  
P.2.22.15 = P.FBA Selects FBA Control word bit 15 as  
main cw.15  
the source for external control  
location EXT1/EXT2 selection (only  
with ACS850).  
1 = Speed  
Selects speed as the operating  
mode for external control location  
EXT1.  
62 Start-up  
Drive parameter  
Setting for  
ACS850/ACQ810  
drives  
Description  
12.05 Ext2 ctrl mode  
2 = Torque  
Selects torque as the operating  
mode for external control location  
EXT2 (only with ACS850).  
16.15 Menu set sel  
(ACS850)  
2 = Load long  
(ACS850)  
Load long parameter list. All  
parameters will be displayed.  
16.21 Menu selection  
(ACQ810)  
2 = Full (ACQ810)  
21.01 Speed ref1 sel  
FB  
Selects the fieldbus reference 1 as  
the source for speed reference 1.  
24.01 Torq ref1 sel  
FBA ref2  
Selects fieldbus reference 2 as the  
source of the torque reference 1  
(only with ACS850).  
1)  
Read-only or automatically detected/set  
The start sequence for the parameter example above is given  
below.  
Control word:  
47Eh (1150 decimal) –> READY TO SWITCH ON  
47Fh (1151 decimal) –> OPERATING (Speed mode)  
or  
C7Fh (3199 decimal) –> OPERATING (Torque mode in  
ACS850).  
Start-up 63  
ODVA AC/DC drive profile  
The following example shows how to configure the ACS850 or  
ACQ810 drive to use the ODVA AC/DC drive profile.  
The used I/O assembly instances are 23 and 73.  
The table below gives the recommended drive parameter settings.  
Drive parameter  
Setting for  
ACS850/ACQ810  
drives  
Description  
50.01 Fba enable  
1 = Enable  
Enables communication between  
drive and adapter module.  
50.04 Fb ref1 modesel  
50.05 Fb ref2 modesel  
Speed  
Torque  
Selects speed as the adapter  
module ref1 type.  
Selects torque as the adapter  
module ref2 type (only with  
ACS850).  
1)  
51.01 FBA type  
DEVICENET  
Displays the type of the adapter  
module.  
51.02 FBA par2  
(MAC ID)  
5
Defines the MAC ID number of the  
adapter module.  
51.03 FBA par3  
(BAUD RATE)  
0 (= 125 kbit/s)  
Sets the baud rate for the  
DeviceNet interface.  
51.06 FBA par6  
(OUTPUT INSTANCE)  
23  
73  
Selects the ODVA AC/DC drive  
profile output instance.  
51.08 FBA par8  
(INPUT INSTANCE)  
Selects the ODVA AC/DC profile  
input instance.  
51.27 FBA par refresh  
10.01 Ext1 start func  
1 = Refresh  
Validates the FDNA-01  
configuration parameter settings.  
3 = FB  
Selects the fieldbus interface as the  
source of the start and stop  
commands for external control  
location 1.  
10.04 Ext2 Start func  
3 = FB  
Selects the fieldbus as the source  
for start and stop commands for  
external control location EXT2 (only  
with ACS850).  
 
64 Start-up  
Drive parameter  
Setting for  
ACS850/ACQ810  
drives  
Description  
12.01 Ext1/Ext2 sel  
12.05 Ext2 ctrl mode  
DI1  
Selects digital input DI1 as the  
source for external control location  
EXT1/EXT2 selection (only with  
ACS850).  
2 = Torque  
Selects torque as the operating  
mode for external control location  
EXT2 (only with ACS850).  
16.15 Menu set sel  
(ACS850)  
2 = Load long  
(ACS850)  
Load long parameter list. All  
parameters will be displayed.  
16.21 Menu selection  
(ACQ810)  
1 = Full (ACQ810)  
21.01 Speed ref1 sel  
FBA ref1  
FBA ref2  
Selects the fieldbus reference 1 as  
the source for speed reference 1.  
24.01 Torq ref1 sel  
Selects fieldbus reference 2 as the  
source of the torque reference 1  
(only with ACS850).  
1)  
Read-only or automatically detected/set  
Note: For ACS850 in this example, digital input DI1 has been  
configured to control whether to use the speed or torque control  
mode.  
The start sequence for the parameter example above is given  
below.  
Control word:  
0h (0 decimal) –> READY  
1h (1 decimal) –> ENABLED (Running forward)  
2h (2 decimal) –> ENABLED (Running reverse)  
Start-up 65  
Starting up ACS880 drives  
This example sets up the fieldbus adapter installed as fieldbus  
adapter A. To set up the fieldbus adapter B, perform the same  
tasks with the corresponding parameters in parameter groups 50,  
54, 55, and 56.  
1. Power up the drive.  
2. Enable the communication between the adapter module and  
the drive by setting parameter 50.01 FBA A enable to Enable.  
3. Ensure that parameter 50.04 FBA A ref1 type is set to Speed  
and parameter 50.05 FBA A ref2 type is set to Torque.  
4. Set the FDNA-01 configuration parameters in drive parameter  
group 51.  
5. Define the process data transferred to and from the drive in  
FDNA-01 parameter groups 52 and 53.  
Note: If communication between the FDNA-01 and DeviceNet  
master is established, changes to the configuration parameters  
can be done also through Fieldbus configuration object 91h.  
6. Validate the settings made in parameter groups 51, 52 and 53  
by setting parameter 51.27 FBA par refresh to Refresh.  
7. Set the relevant drive control parameters to control the drive  
according to the application.  
Examples of appropriate values are shown in the tables below.  
Parameter setting examples – ACS880  
ABB Drives profile  
The following example shows how to configure the ACS880 drive  
to use the ABB Drives profile.  
The used I/O assembly instances are 902 and 952.  
     
66 Start-up  
The table below gives the recommended drive parameter settings.  
Drive parameter  
Setting for  
Description  
ACS880 drives  
50.01 FBA A enable  
1 = Enable  
Enables communication between  
drive and adapter module.  
50.04 FBA A ref1 type  
50.05 FBA A ref2 type  
4 = Speed  
Selects speed as the fieldbus A  
reference 1 type.  
3 = Torque  
Selects torque as the fieldbus A  
reference 2 type.  
1)  
51.01 FBA type  
51.02 MAC ID  
DeviceNet  
Displays the type of the adapter  
module.  
6
Defines the MAC ID number of the  
adapter module.  
51.03 Baud rate  
51.06 Output instance  
0 = 125kbit/s  
Sets the baud rate for the DeviceNet  
interface.  
902  
Selects the ABB Drives profile with  
speed and torque plus drive  
parameters output instance.  
51.07 Output num pars  
10  
Must always be set to 10. For  
exceptions, see Appendix A –  
Varying the number of drive  
parameters.  
52.01 FBA data in1  
52.02 FBA data in2  
52.03 FBA data in3  
52.04 FBA data in4  
1.7  
Motor current - MSW  
Motor current - LSW  
DC voltage - MSW  
DC voltage - LSW  
0 = None  
1.11  
0 = None  
0 = None  
52.05 FBA data in5…  
52.10 FBA data in10  
53.01 FBA data out1  
53.02 FBA data out2  
53.03 FBA data out3  
53.04 FBA data out4  
23.12  
Acceleration time - MSW  
Acceleration time - LSW  
Deceleration time - MSW  
Deceleration time - LSW  
0 = None  
23.13  
0 = None  
0 = None  
53.05 FBA data out5…  
53.10 FBA data out10  
51.27 FBA par refresh  
1 = Configure  
Validates the FDNA-01 configuration  
parameter settings.  
Start-up 67  
Drive parameter  
Setting for  
Description  
ACS880 drives  
19.11 Ext1/Ext2 selection 2 = MCW bit11: Ext Selects FBA Control word bit 11 as  
ctrl  
the source for the external control  
location EXT1/EXT2 selection.  
19.12 Ext1 control mode 1 2 = MCW bit11: Ext Selects speed control as the control  
ctrl loc  
mode 1 for external control location  
EXT1.  
19.14 Ext2 control mode 1 3 = Torque  
Selects torque control as the control  
mode 1 for external control location  
EXT2.  
20.01 Ext1 commands  
20.06 Ext2 commands  
12 = Fieldbus A  
Selects fieldbus interface A as the  
source of the start and stop  
commands for external control  
location EXT1.  
12 = Fieldbus A  
Selects fieldbus interface A as the  
source of the start and stop  
commands for external control  
location EXT2.  
22.11 Speed ref1  
selection  
4 = FB A ref1  
Selects fieldbus A reference 1 as the  
source for speed reference 1.  
26.11 Torque ref1  
selection  
5 = FB A ref2  
Selects fieldbus reference 2 as the  
source for torque reference 1.  
1)  
Read-only or automatically detected/set  
Example  
2)  
The start sequence for the parameter example above is given  
below.  
Control word:  
47Eh (1150 decimal) –> READY TO SWITCH ON  
47Fh (1151 decimal) –> OPERATING (Speed mode)  
or  
C7Fh (3199 decimal) –> OPERATING (Torque mode)  
ODVA AC/DC drive profile  
The following example shows how to configure the ACS880 drive  
to use the ODVA AC/DC drive profile.  
The used I/O assembly instances are 23 and 73.  
 
68 Start-up  
The table below gives the recommended drive parameter settings.  
Drive parameter  
Setting for  
Description  
ACS880 drives  
50.01 FBA A enable  
1 = Enable  
Enables communication between  
drive and adapter module.  
50.04 FBA A ref1 type  
50.05 FBA A ref2 type  
4 = Speed  
Selects Speed as the fieldbus A  
reference 1 type.  
3 = Torque  
Selects Torque as the fieldbus A  
reference 2 type.  
1)  
51.01 FBA type  
51.02 MAC ID  
DeviceNet  
Displays the type of the adapter  
module.  
6
Defines the MAC ID number of the  
adapter module.  
51.03 Baud rate  
51.06 Output instance  
0 = 125kbit/s  
Sets the baud rate for the DeviceNet  
interface.  
23  
Selects the ABB Drives profile with  
speed and torque plus drive  
parameters output instance.  
51.07 Output num pars  
51.27 FBA par refresh  
10  
Must always be set to 10. For  
exceptions, see Appendix A –  
Varying the number of drive  
parameters.  
1 = Configure  
Validates the FDNA-01 configuration  
parameter settings.  
19.11 Ext1/Ext2 selection 3 = DI1  
19.12 Ext1 control mode 1 2 = Speed  
19.14 Ext2 control mode 1 3 = Torque  
Selects digital input DI1 as the  
source for the external control  
location EXT1/EXT2selection.  
Selects speed control as the control  
mode 1 for external control location  
EXT1.  
Selects torque control as the control  
mode 1 for external control location  
EXT2.  
20.01 Ext1 commands  
12 = Fieldbus A  
Selects fieldbus interface A as the  
source of the start and stop  
commands for external control  
location EXT1.  
Start-up 69  
Drive parameter  
Setting for  
Description  
ACS880 drives  
20.06 Ext2 commands  
12 = Fieldbus A  
Selects fieldbus interface A as the  
source of the start and stop  
commands for external control  
location EXT2.  
22.11 Speed ref1  
selection  
4 = FB A ref1  
Selects fieldbus A reference 1 as the  
source for speed reference 1.  
26.11 Torque ref1  
selection  
5 = FB A ref2  
Selects fieldbus reference 2 as the  
source for torque reference 1.  
1)  
Read-only or automatically detected/set  
Example  
2)  
Note: In this example, digital input DI1 has been configured to  
control whether to use the speed or torque control mode.  
The start sequence for the parameter example above is given  
below.  
Control word:  
0h (0 decimal) –> READY  
1h (1 decimal) –> ENABLED (Running forward)  
2h (2 decimal) –> ENABLED (Running reverse)  
70 Start-up  
Configuring the master station  
After the adapter module has been initialized by the drive, the  
master station must be prepared for communication with the  
module. An example of an Allen-Bradley® PLC is given below. If  
you are using another master system, refer to its documentation  
for more information.  
The example can be applied to all drive types compatible with the  
module.  
EDS files  
The Electronic Data Sheet (EDS) files specify the properties of the  
device for the DeviceNet scanner. The DeviceNet scanner  
identifies the device by means of the product code, device type,  
and major revision attributes. For more information, see Identity  
object, class 01h on page 134.  
To enable the use of different ABB drive types on the same  
DeviceNet network, a unique product code has been given to each  
drive type and application combination.  
EDS files are available from the Document library  
(www.abb.com/drives).  
Note: Only one EDS file with the same DeviceNet product code  
can be installed in the PLC at a time.  
   
Start-up 71  
Configuring an Allen-Bradley® PLC  
This example shows how to set up an Allen-Bradley CompactLogix  
PLC with a 1769-SDN DeviceNet Scanner to use a drive equipped  
with a FDNA-01 fieldbus adapter, using RSNetWorx and RSLogix  
5000 to configure and control the network. Slight vendor-specific  
differences may exist when using other programs or master  
devices.  
In this example, ACS880 is used as the drive.  
1. Select and import the EDS file for the drive, for example,  
ACS880_FDNA01_v2.23_eu.EDS. For more help on choosing  
the correct file, refer to ABB EDS Selection Guide delivered  
with the EDS files.  
Note: Only one EDS file with the same Product ID can be  
installed in the PLC at a time.  
2. Add a drive to the network in RSNetWorx for DeviceNet.  
 
72 Start-up  
3. Configure the device MAC address.  
Start-up 73  
4. Configure the DeviceNet Scanner. Add the drive to Scanlist  
and edit I/O parameters. Select Polled or Change of  
State/Cyclic. Then enter the input and output sizes of the I/O  
assemblies that are used (for example, for Basic Speed  
Control Assemblies 20 and 70, each size is set to 4 bytes.).  
74 Start-up  
5. For convenience, you can also edit the Input and Output  
memory mappings. By default, the two 16-bit input words are  
mapped into a single 32-bit double word. It is more convenient  
to map them into separate double words. Output words can be  
mapped similarly.  
6. Download the scanner settings to the device in the online  
mode.  
Start-up 75  
7. Add your DeviceNet scanner to an RSLogix 5000 project. You  
should get new Controller Tags Local:<slot>:I and  
Local:<slot>:O. You can use them to access the data as  
mapped above:  
Local:<slot>:O.Data[0] is the Control word  
Local:<slot>:O.Data[1] is the Reference  
Local:<slot>:I.Data[0] is the Status word  
Local:<slot>:I.Data[1] is the Actual value  
Note: You may need to change the value of  
Local:<slot>:O.CommandRegister.Run or  
Local:<slot>:I.CommandRegister.Run to 1.  
76 Start-up  
Communication profiles 77  
7
Communication profiles  
What this chapter contains  
This chapter describes the communication profiles used in the  
communication between the DeviceNet network, the adapter  
module and the drive.  
Communication profiles  
Communication profiles are ways of conveying control commands  
(Control word, Status word, references and actual values) between  
the master station and the drive.  
With the FDNA-01 module, the DeviceNet network may employ  
either the ODVA AC/DC drive profile or the ABB Drives profile.  
Both are converted to the native profile (eg, DCU or FBA) by the  
adapter module. In addition, two Transparent modes – for 16-bit  
and 32-bit words respectively – are available. With the Transparent  
modes, no data conversion takes place.  
       
78 Communication profiles  
The figure below illustrates the operation of the profiles:  
DeviceNet  
network  
FDNA-01  
Drive  
FDNA-01 profile  
selection:  
Native profile  
(eg, DCU,  
FBA)  
ODVA AC/DC  
ODVA AC/DC  
Data conversion  
Native profile  
(eg, DCU,  
FBA)  
ABB Drives  
ABB Drives profile  
Data conversion  
1)  
1)  
Transparent16  
Transparent32  
Drive-specific profile  
(with 16-bit words)  
Drive-specific profile  
(with 32-bit words)  
1)  
Can be used if the native profile is supported by the drive.  
The following sections describe the Control word, the Status word,  
references and actual values for the ODVA AC/DC drive and ABB  
Drives communication profiles. Refer to the drive manuals for  
details on the native profiles.  
Communication profiles 79  
ODVA AC/DC drive profile  
A DeviceNet node is modelled as a collection of abstract objects.  
Each object represents the interface to and behavior of a  
component within the product. The ODVA AC/DC drive profile  
defines a collection of objects suitable for the control of the AC and  
DC drives. The objects supported by the FDNA-01 DeviceNet  
adapter are listed in Class objects on page 107.  
The objects are defined by:  
Service  
Class  
Instance  
Attribute  
Behavior.  
For example, to set the drive speed reference, the  
Set_Attribute_Single service can be requested for the SpeedRef  
attribute of the AC/DC drive object class. The resulting behavior is  
that the reference speed of the drive is set to the requested value.  
This is an example of explicit messaging, where each attribute of a  
class is set individually. While this is allowed, it is inefficient.  
Instead, implicit messaging using input and output assembly  
instances is recommended. Implicit messaging allows the  
DeviceNet Master to set or get predefined groups of attributes in a  
single message exchange. The assembly instances supported by  
the adapter module are listed and defined in Assembly objects on  
page 74.  
ODVA output attributes  
This section briefly describes the instances found in the output  
assemblies of the ODVA AC/DC drive profile. Note that all output  
assembly instances do not support all attributes listed here.  
   
80 Communication profiles  
Run Forward & Run Reverse  
(Control supervisor object)  
These attributes are used to assert run and stop commands to the  
Control supervisor object state machine according to the following  
Run/Stop event matrix. See State (Control supervisor object) on  
page 60.  
RunFwd  
RunRev  
Trigger event  
Stop  
Run type  
N/A  
0
0
0
0
0
0
1
0
1
1
1
1
Run  
RunFwd  
RunRev  
N/A  
0
0
1
1
1
1
1
Run  
No Action  
No Action  
Run  
N/A  
RunRev  
RunFwd  
0
Run  
Fault Reset (Control supervisor object)  
This attribute resets a drive fault on a transition from zero to one if  
the condition that caused the fault has been cleared.  
Net Ctrl (Control supervisor object)  
This attribute requests that the drive Run/Stop command is  
supplied locally (Net Ctrl = 0) or by the network (Net Ctrl = 1).  
Net Ref (AC/DC drive object)  
This attribute requests that the drive Speed and Torque  
References are supplied locally (Net Ref = 0) or by the network  
(Net Ref = 1).  
Speed Reference (AC/DC drive object)  
This attribute is the speed reference for the drive. The units are  
scaled by the Speed Scale attribute of the AC/DC drive object. See  
Table 4. for details.  
           
Communication profiles 81  
Scalar mode  
When the drive is operating in the scalar mode, the adapter  
module provides the drive with a frequency reference. The ODVA  
AC/DC drive profile uses rpm units for the Speed Reference. The  
drive frequency reference is calculated as follows:  
Osr × Us× Mf  
Dfr =  
Mss  
where  
Dfr = Drive frequency reference in Hz  
Osr = ODVA Speed Reference  
Us = ODVA speed unit (see 10 ODVA SPEED SCALE on page 41)  
Mf = Motor nominal frequency in Hz  
Mss = Motor synchronous speed in rpm (not motor nominal speed)  
For example, for a 4-pole 60 Hz motor (Mss = 1800 rpm) with a  
unit of 1 rpm and an ODVA Speed Reference of 900, the drive  
frequency reference is:  
Osr × Us× Mf 900×1rpm×60Hz  
Dfr =  
=
= 30Hz  
Mss  
1800rpm  
Vector mode  
When the drive is operating in the vector mode, the adapter  
module provides the drive with a speed reference. The ODVA  
AC/DC drive profile uses rpm units for the speed reference. The  
drive speed reference is calculated as follows:  
Dsr = Osr × Us  
where  
Dsr = Drive Speed Reference in rpm  
Osr = ODVA Speed Reference  
Us = ODVA speed unit (see 10 ODVA SPEED SCALE on page 41)  
82 Communication profiles  
For example, for an ODVA Speed Reference of 900 rpm with a unit  
of 0.5 rpm, the drive speed reference is:  
Dsr = Osr × Us = 900× 0.5rpm = 450rpm  
Torque Reference (AC/DC drive object)  
This attribute is the torque reference for the drive. The units are  
scaled by the Torque Scale attribute of the AC/DC drive object.  
See Table 5. for details.  
The adapter module provides the drive with a Torque Reference in  
percent of the motor nominal torque. The ODVA AC/DC drive  
profile uses Newton-meter (N·m) units for the Torque Reference.  
The drive torque reference is calculated as follows:  
100×Otr × Ut  
Dtr =  
Mt  
where  
Dtr = Drive torque reference in percent of motor nominal torque  
Otr = ODVA Torque Reference  
Ut = ODVA torque unit (see 11 ODVA TORQUE SCALE on page 42)  
Mt = Motor nominal torque in Nm.  
For example, for a 1000 Nm motor nominal torque with a unit of 1  
Nm and an ODVA Torque Reference of 500, the drive torque  
reference is:  
100×Otr × Ut 100×500×1Nm  
Dtr =  
=
= 50  
Mt  
1000 Nm  
 
Communication profiles 83  
ODVA input attributes  
This section briefly describes the instances found in the input  
assemblies of the ODVA AC/DC drive profile. Note that all input  
assembly instances do not support all attributes listed here.  
Faulted (Control supervisor object)  
This attribute indicates that the drive has experienced a fault. The  
fault code may be read from the FaultCode attribute of the Control  
supervisor object.  
Warning (Control supervisor object)  
This attribute indicates that the drive is experiencing a warning  
condition. The warning code may be read from the WarnCode  
attribute of the Control supervisor object.  
Running Forward (Control supervisor object)  
This attribute indicates that the drive is running in the forward  
direction.  
Running Reverse (Control supervisor object)  
This attribute indicates that the drive is running in the reverse  
direction.  
Ready (Control supervisor object)  
This attribute indicates that the Control supervisor object state  
machine is in the Ready, Running or Stopping state. See State  
(Control supervisor object) on page 60.  
Ctrl From Net (Control supervisor object)  
This attribute indicates if the Run/Stop command is being supplied  
locally (Ctrl From Net = 0) or by the network (Ctrl From Net = 1).  
Ref From Net (AC/DC drive object)  
This attribute indicates if the Speed and Torque References are  
being supplied locally (Ref From Net = 0) or by the network (Ref  
From Net = 1).  
               
84 Communication profiles  
At Reference (AC/DC drive object)  
This attribute indicates that the drive is operating at the specified  
Speed or Torque Reference.  
State (Control supervisor object)  
This attribute indicates the current state of the Control supervisor  
object.  
State  
Description  
Vendor Specific  
Startup  
State  
Description  
Enabled  
0
1
2
3
4
5
6
7
Stopping  
Fault Stop  
Faulted  
Not Ready  
Ready  
     
Communication profiles 85  
The ODVA state transition diagram is shown below:  
ALM = Alarm  
DEC = Deceleration  
FWD = Forward  
REV = Reverse  
RDY = Ready  
Non Existent  
Startup  
Power off  
Power on  
Power on  
Faulted  
ALM=1  
FaultRst  
ALM=1  
Not Ready  
DEC=0  
Fault stop  
Power-on  
AND RDY  
Power-on AND not RDY  
DEC=0  
Ready  
Stopping  
ALM=1  
FWD OR REV  
FWD OR REV  
DEC=1  
ALM=1  
Enabled  
86 Communication profiles  
Speed Actual (AC/DC drive object)  
This attribute indicates the actual speed at which the drive is  
operating. The units are scaled by the SpeedScale attribute of the  
AC/DC drive object. See Table 4. for details.  
Scalar mode  
When the drive is operating in the scalar mode, the drive provides  
the adapter module with a frequency actual. The ODVA AC/DC  
drive profile uses rpm units for the speed actual. The ODVA Speed  
Actual is calculated as follows:  
Dfa × Mss  
Osa =  
Mf × Us  
where  
Osa = ODVA Speed Actual  
Dfa = Drive frequency actual in Hz  
Us = ODVA speed unit (see 10 ODVA SPEED SCALE on page 41)  
Mf = Motor nominal frequency in Hz  
Mss = Motor synchronous speed in rpm (not motor nominal speed)  
For example, for a 4 pole 60 Hz motor (Mss = 1800 rpm) with a unit  
of 1 rpm and a Drive frequency actual of 30 Hz, the ODVA Speed  
Actual is:  
Dfa×Mss 30Hz×1800rpm  
Osa =  
=
= 900  
Mf × Us  
60Hz×1rpm  
 
Communication profiles 87  
Vector Mode  
When the drive is operating in the vector mode, the drive provides  
the adapter module with a speed actual. The ODVA AC/DC drive  
profile uses rpm units for the speed actual. The ODVA Speed  
Actual is calculated as follows:  
Dsa  
Osa =  
Us  
where  
Dsa = Drive speed actual in rpm  
Osa = ODVA Speed Actual  
Us = ODVA speed unit (see 10 ODVA SPEED SCALE on page 41)  
For example, for a drive speed actual of 900 rpm with a unit of 0.5  
rpm, the ODVA Speed Actual is:  
Dsa 450rpm  
Osa =  
=
= 900  
Us  
0.5rpm  
Torque Actual (AC/DC drive object)  
This attribute indicates the actual torque at which the drive is  
operating. The units are scaled by the Torque Scale attribute of the  
AC/DC drive object. See Table 5. for details.  
The drive provides the adapter module with a torque actual in  
percent of the motor nominal torque. The ODVA AC/DC drive  
profile uses Newton-meter (N·m) units for the Torque Actual. The  
ODVA Torque Actual is calculated as follows:  
Dta×Mt  
100× Ut  
Ota =  
where  
Dta = Drive torque actual in percent of motor nominal torque  
Ota = ODVA Torque Actual  
Ut = ODVA torque unit (see 11 ODVA TORQUE SCALE on page 42)  
Mt = Motor nominal torque in Nm  
 
88 Communication profiles  
For example, for a 1000 Nm motor nominal torque with a unit of 1  
Nm and a drive torque actual of 50%, the ODVA Torque Actual is:  
Dta×Mt 50×1000 Nm  
Ota =  
=
= 500  
100× Ut  
100×1Nm  
ABB Drives communication profile  
Control word and Status word  
The Control word is the principal means for controlling the drive  
from a fieldbus system. It is sent by the fieldbus master station to  
the drive through the adapter module. The drive switches between  
its states according to the bit-coded instructions in the Control  
word, and returns status information to the master in the Status  
word.  
The contents of the Control word and the Status word are detailed  
below. The drive states are presented on page 93.  
Control word contents  
The table below shows the contents of the Control word for the  
ABB Drives communication profile. The upper case boldface text  
refers to the states shown in the state machine on page 93.  
Bit Name  
Value  
STATE/Description  
0
OFF1_  
CONTROL  
1
0
Proceed to READY TO OPERATE.  
Stop along currently active deceleration  
ramp. Proceed to OFF1 ACTIVE; proceed  
to READY TO SWITCH ON unless other  
interlocks (OFF2, OFF3) are active.  
1
OFF2_  
CONTROL  
1
0
Continue operation (OFF2 inactive).  
Emergency OFF, coast to stop.  
Proceed to OFF2 ACTIVE; proceed to  
SWITCH-ON INHIBITED.  
     
Communication profiles 89  
Bit Name  
Value  
STATE/Description  
2
OFF3_  
CONTROL  
1
0
Continue operation (OFF3 inactive).  
Emergency stop, stop within time defined  
with the drive parameter. Proceed to OFF3  
ACTIVE; proceed to SWITCH-ON  
INHIBITED.  
Warning: Ensure motor and driven  
machine can be stopped using this stop  
mode.  
3
INHIBIT_  
OPERATION  
1
Proceed to OPERATION ENABLED.  
Note: Run enable signal must be active;  
see drive documentation. If the drive is set  
to receive the Run enable signal from the  
fieldbus, this bit activates the signal.  
0
1
0
Inhibit operation. Proceed to OPERATION  
INHIBITED.  
4
5
6
RAMP_OUT_  
ZERO  
Normal operation. Proceed to RFG:  
OUTPUT ENABLED.  
Force the Ramp Function Generator output  
to zero. Drive ramps to stop (current and  
DC voltage limits in force).  
RAMP_HOLD  
1
Enable ramp function.  
Proceed to RFG: ACCELERATOR  
ENABLED.  
0
1
Halt ramping (Ramp Function Generator  
output held).  
RAMP_IN_  
ZERO  
Normal operation. Proceed to  
OPERATION.  
Note: This bit is effective only if the  
fieldbus interface is set as the source for  
this signal by drive parameters.  
0
Force the Ramp Function Generator input  
to zero.  
90 Communication profiles  
Bit Name  
RESET  
Value  
STATE/Description  
7
0=>1 Fault reset if an active fault exists. Proceed  
to SWITCH-ON INHIBITED.  
Note: This bit is effective only if the  
fieldbus interface is set as the source for  
this signal by drive parameters.  
0
Continue normal operation.  
8…9 Reserved.  
10 REMOTE_  
CMD  
1
0
Fieldbus control enabled.  
Control word and reference not getting  
through to the drive, except for CW bits  
OFF1, OFF2 and OFF3.  
11 EXT_CTRL_  
LOC  
1
0
Select External Control Location EXT2.  
Effective if the control location  
parameterized to be selected from the  
fieldbus.  
Select External Control Location EXT1.  
Effective if the control location  
parameterized to be selected from the  
fieldbus.  
12… Reserved.  
15  
Communication profiles 91  
Status word contents  
The table below shows the contents of the Status word for the ABB  
Drives communication profile. The upper case boldface text refers  
to the states shown in the state machine on page 93.  
Bit Name  
RDY_ON  
Value  
STATE/Description  
READY TO SWITCH ON.  
0
1
2
3
4
5
6
7
8
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
NOT READY TO SWITCH ON.  
READY TO OPERATE.  
OFF1 ACTIVE.  
RDY_RUN  
RDY_REF  
TRIPPED  
OPERATION ENABLED.  
OPERATION INHIBITED.  
FAULT.  
No fault.  
OFF_2_STA  
OFF_3_STA  
OFF2 inactive.  
OFF2 ACTIVE.  
OFF3 inactive.  
OFF3 ACTIVE.  
SWC_ON_  
INHIB  
SWITCH-ON INHIBITED.  
ALARM  
Warning/Alarm.  
No warning/alarm.  
AT_  
OPERATION. Actual value equals  
reference = is within tolerance limits, ie, in  
speed control, speed error is 10% max. of  
nominal motor speed.  
SETPOINT  
0
1
0
Actual value differs from reference = is  
outside tolerance limits.  
9
REMOTE  
Drive control location: REMOTE (EXT1 or  
EXT2).  
Drive control location: LOCAL.  
 
92 Communication profiles  
Bit Name  
Value  
STATE/Description  
10 ABOVE_  
LIMIT  
1
Actual frequency or speed equals or  
exceeds the supervision limit (set by the  
drive parameter). Valid in both directions of  
rotation.  
0
1
Actual frequency or speed within  
supervision limit.  
11 EXT_CTRL_  
LOC  
External Control Location EXT2 selected.  
Note concerning ACS880: This bit is  
effective only if the fieldbus interface is set  
as the target for this signal by drive  
parameters. User bit 0 selection (06.30).  
0
1
External Control Location EXT1 selected.  
12 EXT_RUN_  
ENABLE  
External Run Enable signal received.  
Note concerning ACS880: This bit is  
effective only if the fieldbus interface is set  
as the target for this signal by drive  
parameters. User bit 1 selection (06.31).  
0
No External Run Enable signal received  
13… Reserved.  
14  
15 FBA_ERROR  
1
0
Communication error detected by the  
fieldbus adapter module.  
Fieldbus adapter communication OK.  
Communication profiles 93  
State machine  
The state machine for the ABB Drives communication profile is  
shown below.  
SWITCH-ON  
INHIBITED  
ABB Drives  
Communication  
Profile  
MAINS OFF  
(SW Bit6=1)  
(SW Bit0=0)  
Power ON  
(CW Bit0=0)  
NOT READY TO  
SWITCH ON  
CW = Control word  
SW = Status word  
A
B
C
D
n
I
= Speed  
= Input Current  
(CW=xxxx x  
1
xx xxxx x110  
)
RFG = Ramp Function  
Generator  
f
(CW Bit3=0)  
READY TO  
= Frequency  
OPERATION  
INHIBITED  
SWITCH ON  
(SW Bit0=1)  
(SW Bit2=0)  
from any state  
Fault  
operation  
inhibited  
(CW=xxxx x  
1
xx xxxx x111  
)
READY TO  
OPERATE  
FAULT  
(SW Bit3=1)  
from any state  
OFF1 (CW Bit0=0)  
(SW Bit1=1)  
(CW Bit7=1)  
(CW=xxxx x1xx xxxx 1111  
OFF1  
ACTIVE  
and SW Bit12=1)  
(SW Bit1=0)  
from any state  
from any state  
Emergency Stop  
Emergency OFF  
n(f)=0 / I=0  
OFF2 (CW Bit1=0)  
OFF3 (CW Bit2=0)  
(CW Bit3=1  
and  
OFF3  
ACTIVE  
OFF2  
ACTIVE  
SW Bit12=1)  
B
C
D
C
(SW Bit5=0)  
(SW Bit4=0)  
n(f)=0 / I=0  
(CW Bit4=0)  
OPERATION  
ENABLED  
D
(SW Bit2=1)  
A
B
(CW Bit5=0)  
(CW Bit6=0)  
(CW=xxxx x  
1
xx xxx1 1111  
)
RFG: OUTPUT  
ENABLED  
D
(CW=xxxx x  
1
xx xx11 1111)  
RFG: ACCELERATOR  
ENABLED  
state  
condition  
C
D
(CW=xxxx x  
1
xx x111 1111  
)
rising edge  
of the bit  
OPERATION  
(SW Bit8=1)  
 
94 Communication profiles  
References  
References are 16-bit signed two's complement integers. A  
negative reference indicates a reverse direction of rotation.  
ABB drives can receive control information from multiple sources  
including analogue and digital inputs, the drive control panel and a  
communication module (for example, FDNA-01). To have the drive  
controlled through the fieldbus, the module must be defined as the  
source for control information, for example, reference.  
Scaling  
References are scaled as shown below.  
Note: The values of REF1 MAX and REF2 MAX are set with drive  
parameters. See the drive documentation for further information.  
In ACSM1, ACS850, ACQ810 and ACS880, the speed reference  
(REFx) in decimal (0…20000) corresponds to 0 … 100% of the  
speed scaling value (as defined with a drive parameter, eg,  
ACS880 parameter 46.10 Speed scaling).  
In ACS355, drive parameter REFx MIN may limit the actual  
minimum reference.  
Fieldbus  
Drive  
REF2: 10000  
REF1: 20000  
REFx MAX / Speed scale  
REFx MIN  
-(REFx MIN)  
0
REF2: -10000  
REF1: -20000  
-(REFx MAX) / Speed scale  
   
Communication profiles 95  
Actual values  
Actual values are 16-bit signed two's complement integers  
containing information on the operation of the drive. A negative  
reference indicates a reverse direction of rotation. The functions to  
be monitored are selected with a drive parameter.  
Scaling  
Actual values are scaled as shown below.  
Note: The values of REF1 MAX and REF2 MAX are set with drive  
parameters. See the drive documentation for further information.  
Fieldbus  
Drive  
ACT2: 10000  
REFx MAX  
ACT1: 20000  
0
0
ACT2: -10000  
ACT1: -20000  
-(REFx MAX)  
   
96 Communication profiles  
Communication protocol 97  
8
Communication protocol  
What this chapter contains  
This chapter describes the DeviceNet communication protocol for  
the adapter module and the configuration of the scanner. For  
detailed information on DeviceNet communication, refer to ODVA  
DeviceNet Specifications Release 2.0.  
DeviceNet  
DeviceNet is a protocol based on the CAN technology. CAN  
specifies the physical layer interface. DeviceNet specifies the  
wiring and the data transfer through CAN.  
The FDNA-01 module is a device acting as a Group 2 only Server  
realizing the Predefined Master Slave Connection Set functionality.  
The Off-line Connection Set functionality and Unconnected  
Message Manager (UCMM) are not supported.  
Object modeling and functional properties  
One of the main features of DeviceNet is object modeling. A group  
of objects can be described with a Functional Profile. The FDNA-  
01 adapter module realizes the ODVA AC/DC drive Functional  
Profile with additional features.  
         
98 Communication protocol  
Assembly objects  
I/O assembly instances may also be referred to as Block Transfer  
of data. Intelligent devices realizing a Functional Profile, such as  
FDNA-01, 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 FDNA-01 adapter module uses  
static assemblies (in other words, fixed groupings of different  
object data only). The following tables describe the assembly  
instances supported by the adapter module.  
Basic speed control assembly  
The Basic speed control assembly is defined by the ODVA AC/DC  
drive profile. The format of the output assembly is:  
Instance 20  
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2  
Bit 1 Bit 0  
Run Fwd  
0
Fault  
Reset  
1
2
3
Speed Reference (Low Byte)  
Speed Reference (High Byte)  
The format of the input assembly is:  
Instance 70  
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2  
Bit 1 Bit 0  
Faulted  
0
Running1  
(Fwd)  
1
2
3
Speed Actual (Low Byte)  
Speed Actual (High Byte)  
     
Communication protocol 99  
Basic speed control plus drive parameters  
assembly  
The Basic speed control plus drive parameters assembly, defined  
by ABB, adds configurable drive parameters to the Basic speed  
control assembly of the ODVA AC/DC drive profile.  
The format of the output assembly is:  
Instance 120  
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2  
Bit 1 Bit 0  
0
Fault  
Reset  
Run  
Fwd  
1
2
Speed Reference (Low Byte)  
Speed Reference (High Byte)  
DATA OUT 1 Value (Low Byte)  
DATA OUT 1 Value (High Byte)  
DATA OUT 2 Value (Low Byte)  
DATA OUT 2 Value (High Byte)  
DATA OUT 3 Value (Low Byte)  
DATA OUT 3 Value (High Byte)  
DATA OUT 4 Value (Low Byte)  
DATA OUT 4 Value (High Byte)  
DATA OUT 5 Value (Low Byte)  
DATA OUT 5 Value (High Byte)  
DATA OUT 6 Value (Low Byte)  
DATA OUT 6 Value (High Byte)  
DATA OUT 7 Value (Low Byte)  
DATA OUT 7 Value (High Byte)  
DATA OUT 8 Value (Low Byte)  
DATA OUT 8 Value (High Byte)  
DATA OUT 9 Value (Low Byte)  
3
4
5
6
7
8
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
 
100 Communication protocol  
Instance 120  
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2  
Bit 1 Bit 0  
21  
22  
23  
DATA OUT 9 Value (High Byte)  
DATA OUT 10 Value (Low Byte)  
DATA OUT 10 Value (High Byte)  
The format of the input assembly is:  
Instance 170  
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2  
Bit 1 Bit 0  
Faulted  
0
Running1  
(Fwd)  
1
2
Speed Actual (Low Byte)  
3
Speed Actual (High Byte)  
4
DATA IN 1 Value (Low Byte)  
DATA IN 1 Value (High Byte)  
DATA IN 2 Value (Low Byte)  
DATA IN 2 Value (High Byte)  
DATA IN 3 Value (Low Byte)  
DATA IN 3 Value (High Byte)  
DATA IN 4 Value (Low Byte)  
DATA IN 4 Value (High Byte)  
DATA IN 5 Value (Low Byte)  
DATA IN 5 Value (High Byte)  
DATA IN 6 Value (Low Byte)  
DATA IN 6 Value (High Byte)  
DATA IN 7 Value (Low Byte)  
DATA IN 7 Value (High Byte)  
DATA IN 8 Value (Low Byte)  
DATA IN 8 Value (High Byte)  
5
6
7
8
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
Communication protocol 101  
Instance 170  
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2  
Bit 1 Bit 0  
20  
21  
22  
23  
DATA IN 9 Value (Low Byte)  
DATA IN 9 Value (High Byte)  
DATA IN 10 Value (Low Byte)  
DATA IN 10 Value (High Byte)  
Extended speed control assembly  
The Extended speed control assembly is defined by the ODVA  
AC/DC drive profile. The format of the output assembly is:  
Instance 21  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
NetRef NetCtrl  
Fault  
Reset  
Run  
Rev  
Run  
Fwd  
1
2
3
Speed Reference (Low Byte)  
Speed Reference (High Byte)  
The format of the input assembly is:  
Instance 71  
Byte Bit 7  
Bit 6 Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1 Bit 0  
0
At  
Refer- From From  
ence Net Net  
Ref  
Ctrl  
Ready Run-  
ning2  
Run-  
ning1  
(Fwd)  
Warn- Faulted  
ing  
(Rev)  
1
2
3
Drive State (See section State (Control supervisor object).)  
Speed Actual (Low Byte)  
Speed Actual (High Byte)  
 
102 Communication protocol  
Extended speed control plus drive parameters  
assembly  
The Extended speed control plus drive parameters assembly,  
defined by ABB, adds configurable drive parameters to the  
Extended speed control assembly of the ODVA AC/DC drive  
profile.  
The format of the output assembly is:  
Instance 121  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
NetRef NetCtrl  
Fault  
Reset  
Run  
Rev  
Run  
Fwd  
1
2
Speed Reference (Low Byte)  
Speed Reference (High Byte)  
DATA OUT 1 Value (Low Byte)  
DATA OUT 1 Value (High Byte)  
DATA OUT 2 Value (Low Byte)  
DATA OUT 2 Value (High Byte)  
DATA OUT 3 Value (Low Byte)  
DATA OUT 3 Value (High Byte)  
DATA OUT 4 Value (Low Byte)  
DATA OUT 4 Value (High Byte)  
DATA OUT 5 Value (Low Byte)  
DATA OUT 5 Value (High Byte)  
DATA OUT 6 Value (Low Byte)  
DATA OUT 6 Value (High Byte)  
DATA OUT 7 Value (Low Byte)  
DATA OUT 7 Value (High Byte)  
DATA OUT 8 Value (Low Byte)  
DATA OUT 8 Value (High Byte)  
DATA OUT 9 Value (Low Byte)  
3
4
5
6
7
8
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
 
Communication protocol 103  
Instance 121  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
21  
22  
23  
DATA OUT 9 Value (High Byte)  
DATA OUT 10 Value (Low Byte)  
DATA OUT 10 Value (High Byte)  
The format of the input assembly is:  
Instance 171  
Byte Bit 7  
Bit 6 Bit 5 Bit 4  
Ref Ctrl Ready Run-  
Refer- From From  
ence Net Net  
Bit 3  
Bit 2  
Bit 1  
Warn-  
Bit 0  
0
At  
Run-  
Faulted  
ning2 ning1 ing  
(Rev) (Fwd)  
1
2
Drive State (See section State (Control supervisor object).)  
Speed Actual (Low Byte)  
3
Speed Actual (High Byte)  
4
DATA IN 1 Value (Low Byte)  
DATA IN 1 Value (High Byte)  
DATA IN 2 Value (Low Byte)  
DATA IN 2 Value (High Byte)  
DATA IN 3 Value (Low Byte)  
DATA IN 3 Value (High Byte)  
DATA IN 4 Value (Low Byte)  
DATA IN 4 Value (High Byte)  
DATA IN 5 Value (Low Byte)  
DATA IN 5 Value (High Byte)  
DATA IN 6 Value (Low Byte)  
DATA IN 6 Value (High Byte)  
DATA IN 7 Value (Low Byte)  
DATA IN 7 Value (High Byte)  
DATA IN 8 Value (Low Byte)  
5
6
7
8
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
104 Communication protocol  
Instance 171  
Byte Bit 7  
Bit 6 Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
19  
20  
21  
22  
23  
DATA IN 8 Value (High Byte)  
DATA IN 9 Value (Low Byte)  
DATA IN 9 Value (High Byte)  
DATA IN 10 Value (Low Byte)  
DATA IN 10 Value (High Byte)  
Basic speed and torque control assembly  
The Basic speed and torque control assembly is defined by the  
ODVA AC/DC drive profile. The format of the output assembly is:  
Instance 22  
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
Fault  
Reset  
Run  
Fwd  
1
2
3
4
5
Speed Reference (Low Byte)  
Speed Reference (High Byte)  
Torque Reference (Low Byte)  
Torque Reference (High Byte)  
 
Communication protocol 105  
The format of the input assembly is:  
Instance 72  
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
Run-  
Faulted  
ning1  
(Fwd)  
1
2
3
4
5
Speed Actual (Low Byte)  
Speed Actual (High Byte)  
Torque Actual (Low Byte)  
Torque Actual (High Byte)  
Basic speed and torque control  
plus drive parameters assembly  
The Basic speed and torque control plus drive parameters  
assembly, defined by ABB, adds configurable drive parameters to  
the Basic speed and torque control assembly of the ODVA AC/DC  
drive profile.  
The format of the output assembly is:  
Instance 122  
Byte Bit 7  
0
Bit 6 Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
Fault  
Reset  
Run  
Fwd  
1
2
3
4
5
6
7
8
9
Speed Reference (Low Byte)  
Speed Reference (High Byte)  
Torque Reference (Low Byte)  
Torque Reference (High Byte)  
DATA OUT 1 Value (Low Byte)  
DATA OUT 1 Value (High Byte)  
DATA OUT 2 Value (Low Byte)  
DATA OUT 2 Value (High Byte)  
 
106 Communication protocol  
Instance 122  
Byte Bit 7  
Bit 6 Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
DATA OUT 3 Value (Low Byte)  
DATA OUT 3 Value (High Byte)  
DATA OUT 4 Value (Low Byte)  
DATA OUT 4 Value (High Byte)  
DATA OUT 5 Value (Low Byte)  
DATA OUT 5 Value (High Byte)  
DATA OUT 6 Value (Low Byte)  
DATA OUT 6 Value (High Byte)  
DATA OUT 7 Value (Low Byte)  
DATA OUT 7 Value (High Byte)  
DATA OUT 8 Value (Low Byte)  
DATA OUT 8 Value (High Byte)  
DATA OUT 9 Value (Low Byte)  
DATA OUT 9 Value (High Byte)  
DATA OUT 10 Value (Low Byte)  
DATA OUT 10 Value (High Byte)  
The format of the input assembly is:  
Instance 172  
Byte Bit 7  
0
Bit 6 Bit 5 Bit 4  
Bit 3 Bit 2  
Bit 1  
Bit 0  
Run-  
Faulted  
ning1  
(Fwd)  
1
2
3
4
5
Speed Actual (Low Byte)  
Speed Actual (High Byte)  
Torque Actual (Low Byte)  
Torque Actual (High Byte)  
Communication protocol 107  
Instance 172  
Byte Bit 7  
Bit 6 Bit 5 Bit 4  
Bit 3 Bit 2  
Bit 1  
Bit 0  
6
DATA IN 1 Value (Low Byte)  
DATA IN 1 Value (High Byte)  
DATA IN 2 Value (Low Byte)  
DATA IN 2 Value (High Byte)  
DATA IN 3 Value (Low Byte)  
DATA IN 3 Value (High Byte)  
DATA IN 4 Value (Low Byte)  
DATA IN 4 Value (High Byte)  
DATA IN 5 Value (Low Byte)  
DATA IN 5 Value (High Byte)  
DATA IN 6 Value (Low Byte)  
DATA IN 6 Value (High Byte)  
DATA IN 7 Value (Low Byte)  
DATA IN 7 Value (High Byte)  
DATA IN 8 Value (Low Byte)  
DATA IN 8 Value (High Byte)  
DATA IN 9 Value (Low Byte)  
DATA IN 9 Value (High Byte)  
DATA IN 10 Value (Low Byte)  
DATA IN 10 Value (High Byte)  
7
8
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
24  
25  
108 Communication protocol  
Extended speed and torque control assembly  
The Extended speed and torque control assembly is defined by the  
ODVA AC/DC drive profile. The format of the output assembly is:  
Instance 23  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
NetRef NetCtrl  
Fault  
Reset  
Run  
Rev  
Run  
Fwd  
1
2
3
4
5
Speed Reference (Low Byte)  
Speed Reference (High Byte)  
Torque Reference (Low Byte)  
Torque Reference (High Byte)  
The format of the input assembly is:  
Instance 73  
Byte Bit 7  
Bit 6 Bit 5 Bit 4  
Ref Ctrl Ready Run-  
Refer- From From  
ence Net Net  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
At  
Run-  
Warn-  
ing  
Faulted  
ning2 ning1  
(Rev) (Fwd)  
1
2
3
4
5
Drive State (See section State (Control supervisor object).)  
Speed Actual (Low Byte)  
Speed Actual (High Byte)  
Torque Actual (Low Byte)  
Torque Actual (High Byte)  
 
Communication protocol 109  
Extended speed and torque control  
plus drive parameters assembly  
The Extended speed and torque control plus drive parameters  
assembly, defined by ABB, adds configurable drive parameters to  
the Extended speed and torque control assembly of the ODVA  
AC/DC drive profile.  
The format of the output assembly is:  
Instance 123  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
NetRef NetCtrl  
Fault  
Reset  
Run  
Rev  
Run  
Fwd  
1
2
3
4
5
6
7
8
9
Speed Reference (Low Byte)  
Speed Reference (High Byte)  
Torque Reference (Low Byte)  
Torque Reference (High Byte)  
DATA OUT 1 Value (Low Byte)  
DATA OUT 1 Value (High Byte)  
DATA OUT 2 Value (Low Byte)  
DATA OUT 2 Value (High Byte)  
10 DATA OUT 3 Value (Low Byte)  
11 DATA OUT 3 Value (High Byte)  
12 DATA OUT 4 Value (Low Byte)  
13 DATA OUT 4 Value (High Byte)  
14 DATA OUT 5 Value (Low Byte)  
15 DATA OUT 5 Value (High Byte)  
16 DATA OUT 6 Value (Low Byte)  
17 DATA OUT 6 Value (High Byte)  
18 DATA OUT 7 Value (Low Byte)  
19 DATA OUT 7 Value (High Byte)  
20 DATA OUT 8 Value (Low Byte)  
 
110 Communication protocol  
Instance 123  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
21 DATA OUT 8 Value (High Byte)  
22 DATA OUT 9 Value (Low Byte)  
23 DATA OUT 9 Value (High Byte)  
24 DATA OUT 10 Value (Low Byte)  
25 DATA OUT 10 Value (High Byte)  
The format of the input assembly is:  
Instance 173  
Byte Bit 7  
Bit 6 Bit 5 Bit 4  
Ref Ctrl Ready Run-  
Refer- From From  
ence Net Net  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
At  
Run-  
Warn-  
Faulted  
ning2 ning1 ing  
(Rev) (Fwd)  
1
2
3
4
5
6
7
8
9
Drive State (See section State (Control supervisor object).)  
Speed Actual (Low Byte)  
Speed Actual (High Byte)  
Torque Actual (Low Byte)  
Torque Actual (High Byte)  
DATA IN 1 Value (Low Byte)  
DATA IN 1 Value (High Byte)  
DATA IN 2 Value (Low Byte)  
DATA IN 2 Value (High Byte)  
10 DATA IN 3 Value (Low Byte)  
11 DATA IN 3 Value (High Byte)  
12 DATA IN 4 Value (Low Byte)  
13 DATA IN 4 Value (High Byte)  
14 DATA IN 5 Value (Low Byte)  
15 DATA IN 5 Value (High Byte)  
16 DATA IN 6 Value (Low Byte)  
Communication protocol 111  
Instance 173  
Byte Bit 7  
Bit 6 Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
17 DATA IN 6 Value (High Byte)  
18 DATA IN 7 Value (Low Byte)  
19 DATA IN 7 Value (High Byte)  
20 DATA IN 8 Value (Low Byte)  
21 DATA IN 8 Value (High Byte)  
22 DATA IN 9 Value (Low Byte)  
23 DATA IN 9 Value (High Byte)  
24 DATA IN 10 Value (Low Byte)  
25 DATA IN 10 Value (High Byte)  
ABB Drives profile with set speed assembly  
The ABB Drives profile with set speed assembly is defined by  
ABB. The format of the output assembly is:  
Instance 801  
Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
Reset Ramp Ramp Ramp Inhibit Off 3  
Off 2  
Off 1  
in  
Zero  
Hold  
Out  
Zero  
Oper- Control Control Control  
ation  
Ext  
Ctrl  
Loc  
Remote  
Cmd  
2
3
Set Speed (Low Byte)  
Set Speed (High Byte)  
 
112 Communication protocol  
The format of the input assembly is:  
Instance 851  
Byte Bit 7 Bit 6 Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
1
Alarm Swc  
On  
Off 3 Off 2  
Tripped Rdy  
Ref  
Rdy  
Run  
Rdy  
On  
Sta  
Sta  
Inhib  
Field-  
bus  
Ext  
Run  
Ext Ctrl Above Re-  
Loc Limit  
At Set-  
mote point  
Error  
Enable  
2
3
Actual Speed (Low Byte)  
Actual Speed (High Byte)  
ABB Drives profile with set speed  
plus drive parameters assembly  
The ABB Drives profile with set speed plus drive parameters  
assembly, defined by ABB, adds configurable drive parameters to  
the ABB Drives profile with set speed of the ABB Drives Profile.  
The format of the output assembly is:  
Instance 901  
Byte Bit 7 Bit 6 Bit 5 Bit 4  
Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
Reset Ramp Ramp Ramp Inhibit Off 3  
Off 2  
Off 1  
Con-  
trol  
in  
Hold  
Out  
Oper Control Con-  
Zero  
Zero  
ation  
trol  
Ext  
Ctrl  
Loc  
Remote  
Cmd  
2
3
4
5
6
7
8
Set Speed (Low Byte)  
Set Speed (High Byte)  
DATA OUT 1 Value (Low Byte)  
DATA OUT 1 Value (High Byte)  
DATA OUT 2 Value (Low Byte)  
DATA OUT 2 Value (High Byte)  
DATA OUT 3 Value (Low Byte)  
 
Communication protocol 113  
Instance 901  
Byte Bit 7 Bit 6 Bit 5 Bit 4  
Bit 3 Bit 2  
Bit 1  
Bit 0  
9
DATA OUT 3 Value (High Byte)  
DATA OUT 4 Value (Low Byte)  
DATA OUT 4 Value (High Byte)  
DATA OUT 5 Value (Low Byte)  
DATA OUT 5 Value (High Byte)  
DATA OUT 6 Value (Low Byte)  
DATA OUT 6 Value (High Byte)  
DATA OUT 7 Value (Low Byte)  
DATA OUT 7 Value (High Byte)  
DATA OUT 8 Value (Low Byte)  
DATA OUT 8 Value (High Byte)  
DATA OUT 9 Value (Low Byte)  
DATA OUT 9 Value (High Byte)  
DATA OUT 10 Value (Low Byte)  
DATA OUT 10 Value (High Byte)  
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
The format of the input assembly is:  
Instance 951  
Byte Bit 7 Bit 6 Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
1
Alarm Swc  
On  
Off 3 Off 2  
Tripped Rdy  
Ref  
Rdy  
Run  
Rdy  
On  
Sta  
Sta  
Inhib  
Field-  
bus  
Ext  
Run  
Ext Ctrl Above Remote At  
Loc  
Limit  
Set-  
Error  
Enable  
point  
2
3
4
5
Actual Speed (Low Byte)  
Actual Speed (High Byte)  
DATA IN 1 Value (Low Byte)  
DATA IN 1 Value (High Byte)  
114 Communication protocol  
Instance 951  
Byte Bit 7 Bit 6 Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
6
DATA IN 2 Value (Low Byte)  
DATA IN 2 Value (High Byte)  
DATA IN 3 Value (Low Byte)  
DATA IN 3 Value (High Byte)  
DATA IN 4 Value (Low Byte)  
DATA IN 4 Value (High Byte)  
DATA IN 5 Value (Low Byte)  
DATA IN 5 Value (High Byte)  
DATA IN 6 Value (Low Byte)  
DATA IN 6 Value (High Byte)  
DATA IN 7 Value (Low Byte)  
DATA IN 7 Value (High Byte)  
DATA IN 8 Value (Low Byte)  
DATA IN 8 Value (High Byte)  
DATA IN 9 Value (Low Byte)  
DATA IN 9 Value (High Byte)  
DATA IN 10 Value (Low Byte)  
DATA IN 10 Value (High Byte)  
7
8
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
Communication protocol 115  
ABB Drives profile with set speed and  
set torque assembly  
The ABB Drives profile with set speed and set torque assembly is  
defined by ABB. The format of the output assembly is:  
Instance 802  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
Reset Ramp Ramp Ramp Inhibit Off 3  
Off 2  
Off 1  
in  
Hold  
Out  
Oper- Control Control Con-  
Zero  
Zero  
ation  
trol  
Ext  
Ctrl  
Loc  
Remote  
Cmd  
2
3
4
5
Set Speed (Low Byte)  
Set Speed (High Byte)  
Set Torque (Low Byte)  
Set Torque (High Byte)  
The format of the input assembly is:  
Instance 852  
Byte Bit 7  
Bit 6 Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
1
Alarm Swc Off 3 Off 2  
Tripped Rdy  
Ref  
Rdy  
Run  
Rdy  
On  
On  
Sta  
Sta  
Inhib  
Field-  
bus  
Ext  
Run  
Ext Ctrl Above Remote At  
Loc  
Limit  
Set-  
Error  
Enable  
point  
2
3
4
5
Actual Speed (Low Byte)  
Actual Speed (High Byte)  
Actual Torque (Low Byte)  
Actual Torque (High Byte)  
 
116 Communication protocol  
ABB Drives profile with set speed and set torque  
plus drive parameters assembly  
The ABB Drives profile with set speed and set torque plus drive  
parameters assembly, defined by ABB, adds configurable drive  
parameters to the ABB Drives profile with set speed and set torque  
of the ABB Drives Profile.  
The format of the output assembly is:  
Instance 902  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4 Bit 3  
Bit 2  
Bit 1 Bit 0  
0
1
Reset Ramp Ramp Ramp Inhibit Off 3  
Off 2 Off 1  
in  
Zero  
Hold  
Out  
Zero tion  
Opera- Control Con- Con-  
trol trol  
ExtCtrl Remote  
Loc Cmd  
2
3
4
5
6
7
8
9
Set Speed (Low Byte)  
Set Speed (High Byte)  
Set Torque (Low Byte)  
Set Torque (High Byte)  
DATA OUT 1 Value (Low Byte)  
DATA OUT 1 Value (High Byte)  
DATA OUT 2 Value (Low Byte)  
DATA OUT 2 Value (High Byte)  
10 DATA OUT 3 Value (Low Byte)  
11 DATA OUT 3 Value (High Byte)  
12 DATA OUT 4 Value (Low Byte)  
13 DATA OUT 4 Value (High Byte)  
14 DATA OUT 5 Value (Low Byte)  
15 DATA OUT 5 Value (High Byte)  
16 DATA OUT 6 Value (Low Byte)  
17 DATA OUT 6 Value (High Byte)  
18 DATA OUT 7 Value (Low Byte)  
 
Communication protocol 117  
Instance 902  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4 Bit 3  
Bit 2  
Bit 1 Bit 0  
19 DATA OUT 7 Value (High Byte)  
20 DATA OUT 8 Value (Low Byte)  
21 DATA OUT 8 Value (High Byte)  
22 DATA OUT 9 Value (Low Byte)  
23 DATA OUT 9 Value (High Byte)  
24 DATA OUT 10 Value (Low Byte)  
25 DATA OUT 10 Value (High Byte)  
The format of the input assembly is:  
Instance 952  
Byte Bit 7  
Bit 6 Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
1
Alarm Swc  
Off 3 Off 2  
Tripped Rdy  
Ref  
Rdy  
Run  
Rdy  
On  
On  
Inhib  
Sta  
Sta  
Field-  
bus  
Ext  
Run  
Ext Ctrl Above Remote At  
Loc  
Limit  
Set-  
Error  
Enable  
point  
2
3
4
5
6
7
8
9
Actual Speed (Low Byte)  
Actual Speed (High Byte)  
Actual Torque (Low Byte)  
Actual Torque (High Byte)  
DATA IN 1 Value (Low Byte)  
DATA IN 1 Value (High Byte)  
DATA IN 2 Value (Low Byte)  
DATA IN 2 Value (High Byte)  
10 DATA IN 3 Value (Low Byte)  
11 DATA IN 3 Value (High Byte)  
12 DATA IN 4 Value (Low Byte)  
13 DATA IN 4 Value (High Byte)  
118 Communication protocol  
Instance 952  
Byte Bit 7  
Bit 6 Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
14 DATA IN 5 Value (Low Byte)  
15 DATA IN 5 Value (High Byte)  
16 DATA IN 6 Value (Low Byte)  
17 DATA IN 6 Value (High Byte)  
18 DATA IN 7 Value (Low Byte)  
19 DATA IN 7 Value (High Byte)  
20 DATA IN 8 Value (Low Byte)  
21 DATA IN 8 Value (High Byte)  
22 DATA IN 9 Value (Low Byte)  
23 DATA IN 9 Value (High Byte)  
24 DATA IN 10 Value (Low Byte)  
25 DATA IN 10 Value (High Byte)  
Transparent 16 with one assembly  
The Transparent 16 with one assembly, defined by ABB, provides  
unaltered 16-bit access to the configured drive profile.  
The format of the output assembly is:  
Instance 811  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
2
3
Drive Profile 16-bit Control word (Low Byte)  
Drive Profile 16-bit Control word (High Byte)  
Drive Profile 16-bit Reference 1 word (Low Byte)  
Drive Profile 16-bit Reference 1 word (High Byte)  
 
Communication protocol 119  
The format of the input assembly is:  
Instance 861  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
2
3
Drive Profile 16-bit Status word (Low Byte)  
Drive Profile 16-bit Status word (High Byte)  
Drive Profile 16-bit Actual 1 word (Low Byte)  
Drive Profile 16-bit Actual 1 word (High Byte)  
Transparent 16 with one assembly plus drive  
parameters  
The Transparent 16 with one assembly plus drive parameters,  
defined by ABB, adds configurable drive parameters to the  
Transparent 16 with one assembly.  
The format of the output assembly is:  
Instance 911  
Byte Bit 7 Bit 6 Bit 5 Bit 4  
Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
Drive Profile 16-bit Control word (Low Byte)  
Drive Profile 16-bit Control word (High Byte)  
Drive Profile 16-bit Reference 1 word (Low Byte)  
Drive Profile 16-bit Reference 1 word (High Byte)  
DATA OUT 1 Value (Low Byte)  
2
3
4
5
DATA OUT 1 Value (High Byte)  
6
DATA OUT 2 Value (Low Byte)  
7
DATA OUT 2 Value (High Byte)  
8
DATA OUT 3 Value (Low Byte)  
9
DATA OUT 3 Value (High Byte)  
10  
11  
12  
13  
DATA OUT 4 Value (Low Byte)  
DATA OUT 4 Value (High Byte)  
DATA OUT 5 Value (Low Byte)  
DATA OUT 5 Value (High Byte)  
 
120 Communication protocol  
Instance 911  
Byte Bit 7 Bit 6 Bit 5 Bit 4  
Bit 3 Bit 2  
Bit 1  
Bit 0  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
DATA OUT 6 Value (Low Byte)  
DATA OUT 6 Value (High Byte)  
DATA OUT 7 Value (Low Byte)  
DATA OUT 7 Value (High Byte)  
DATA OUT 8 Value (Low Byte)  
DATA OUT 8 Value (High Byte)  
DATA OUT 9 Value (Low Byte)  
DATA OUT 9 Value (High Byte)  
DATA OUT 10 Value (Low Byte)  
DATA OUT 10 Value (High Byte)  
The format of the input assembly is:  
Instance 961  
Byte Bit 7 Bit 6 Bit 5 Bit 4  
Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
Drive Profile 16-bit Status word (Low Byte)  
Drive Profile 16-bit Status word (High Byte)  
Drive Profile 16-bit Actual 1 word (Low Byte)  
Drive Profile 16-bit Actual 1 word (High Byte)  
DATA IN 1 Value (Low Byte)  
2
3
4
5
DATA IN 1 Value (High Byte)  
6
DATA IN 2 Value (Low Byte)  
7
DATA IN 2 Value (High Byte)  
8
DATA IN 3 Value (Low Byte)  
9
DATA IN 3 Value (High Byte)  
10  
11  
12  
13  
DATA IN 4 Value (Low Byte)  
DATA IN 4 Value (High Byte)  
DATA IN 5 Value (Low Byte)  
DATA IN 5 Value (High Byte)  
Communication protocol 121  
Instance 961  
Byte Bit 7 Bit 6 Bit 5 Bit 4  
Bit 3 Bit 2  
Bit 1  
Bit 0  
14  
15  
16  
17  
18  
19  
20  
21  
22  
23  
DATA IN 6 Value (Low Byte)  
DATA IN 6 Value (High Byte)  
DATA IN 7 Value (Low Byte)  
DATA IN 7 Value (High Byte)  
DATA IN 8 Value (Low Byte)  
DATA IN 8 Value (High Byte)  
DATA IN 9 Value (Low Byte)  
DATA IN 9 Value (High Byte)  
DATA IN 10 Value (Low Byte)  
DATA IN 10 Value (High Byte)  
Transparent 16 with two assembly  
The Transparent 16 with two assembly, defined by ABB, provides  
unaltered 16-bit access to the configured drive profile.  
The format of the output assembly is:  
Instance 812  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
Drive Profile 16-bit Control word (Low Byte)  
Drive Profile 16-bit Control word (High Byte)  
Drive Profile 16-bit Reference 1 word (Low Byte)  
Drive Profile 16-bit Reference 1 word (High Byte)  
Drive Profile16-bit Reference 2 word (Low Byte)  
Drive Profile 16-bit Reference 2 word (High Byte)  
 
122 Communication protocol  
The format of the input assembly is:  
Instance 862  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
Drive Profile 16-bit Status word (Low Byte)  
Drive Profile 16-bit Status word (High Byte)  
Drive Profile 16-bit Actual 1 word (Low Byte)  
Drive Profile 16-bit Actual 1 word (High Byte)  
Drive Profile16-bit Actual 2 word (Low Byte)  
Drive Profile 16-bit Actual 2 word (High Byte)  
Transparent 16 with two assembly plus drive  
parameters  
The Transparent 16 with two assembly plus drive parameters,  
defined by ABB, adds configurable drive parameters to the  
Transparent 16 with two assembly.  
The format of the output assembly is:  
Instance 912  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
6
7
8
9
Drive Profile 16-bit Control word (Low Byte)  
Drive Profile 16-bit Control word (High Byte)  
Drive Profile 16-bit Reference 1 word (Low Byte)  
Drive Profile 16-bit Reference 1 word (High Byte)  
Drive Profile 16-bit Reference 2 word (Low Byte)  
Drive Profile 16-bit Reference 2 word (High Byte)  
DATA OUT 1 Value (Low Byte)  
DATA OUT 1 Value (High Byte)  
DATA OUT 2 Value (Low Byte)  
DATA OUT 2 Value (High Byte)  
10 DATA OUT 3 Value (Low Byte)  
11 DATA OUT 3 Value (High Byte)  
 
Communication protocol 123  
Instance 912  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
12 DATA OUT 4 Value (Low Byte)  
13 DATA OUT 4 Value (High Byte)  
14 DATA OUT 5 Value (Low Byte)  
15 DATA OUT 5 Value (High Byte)  
16 DATA OUT 6 Value (Low Byte)  
17 DATA OUT 6 Value (High Byte)  
18 DATA OUT 7 Value (Low Byte)  
19 DATA OUT 7 Value (High Byte)  
20 DATA OUT 8 Value (Low Byte)  
21 DATA OUT 8 Value (High Byte)  
22 DATA OUT 9 Value (Low Byte)  
23 DATA OUT 9 Value (High Byte)  
24 DATA OUT 10 Value (Low Byte)  
25 DATA OUT 10 Value (High Byte)  
The format of the input assembly is:  
Instance 962  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
6
7
8
9
Drive Profile 16-bit Status word (Low Byte)  
Drive Profile 16-bit Status word (High Byte)  
Drive Profile 16-bit Actual 1 word (Low Byte)  
Drive Profile 16-bit Actual 1 word (High Byte)  
Drive Profile 16-bit Actual 2 word (Low Byte)  
Drive Profile 16-bit Actual 2 word (High Byte)  
DATA IN 1 Value (Low Byte)  
DATA IN 1 Value (High Byte)  
DATA IN 2 Value (Low Byte)  
DATA IN 2 Value (High Byte)  
124 Communication protocol  
Instance 962  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
10 DATA IN 3 Value (Low Byte)  
11 DATA IN 3 Value (High Byte)  
12 DATA IN 4 Value (Low Byte)  
13 DATA IN 4 Value (High Byte)  
14 DATA IN 5 Value (Low Byte)  
15 DATA IN 5 Value (High Byte)  
16 DATA IN 6 Value (Low Byte)  
17 DATA IN 6 Value (High Byte)  
18 DATA IN 7 Value (Low Byte)  
19 DATA IN 7 Value (High Byte)  
20 DATA IN 8 Value (Low Byte)  
21 DATA IN 8 Value (High Byte)  
22 DATA IN 9 Value (Low Byte)  
23 DATA IN 9 Value (High Byte)  
24 DATA IN 10 Value (Low Byte)  
25 DATA IN 10 Value (High Byte)  
Communication protocol 125  
Transparent 32 with one assembly  
The Transparent 32 with one assembly, defined by ABB, provides  
unaltered 32-bit access to the configured drive profile.  
The format of the output assembly is:  
Instance 821  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
6
7
Drive Profile 32-bit Control word (Low Byte)  
Drive Profile 32-bit Control word  
Drive Profile 32-bit Control word  
Drive Profile 32-bit Control word (High Byte)  
Drive Profile 32-bit Reference 1 word (Low Byte)  
Drive Profile 32-bit Reference 1 word  
Drive Profile 32-bit Reference 1 word  
Drive Profile 32-bit Reference 1 word (High Byte)  
The format of the input assembly is:  
Instance 871  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
6
7
Drive Profile 32-bit Status word (Low Byte)  
Drive Profile 32-bit Status word  
Drive Profile 32-bit Status word  
Drive Profile 32-bit Status word (High Byte)  
Drive Profile 32-bit Actual 1 word (Low Byte)  
Drive Profile 32-bit Actual 1 word  
Drive Profile 32-bit Actual 1 word  
Drive Profile 32-bit Actual 1 word (High Byte)  
 
126 Communication protocol  
Transparent 32 with one assembly plus drive  
parameters  
The Transparent 32 with one assembly plus drive parameters,  
defined by ABB, adds configurable drive parameters to the  
Transparent 32 with one assembly.  
The format of the output assembly is:  
Instance 921  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
6
7
8
9
Drive Profile 32-bit Control word (Low Byte)  
Drive Profile 32-bit Control word  
Drive Profile 32-bit Control word  
Drive Profile 32-bit Control word (High Byte)  
Drive Profile 32-bit Reference 1 word (Low Byte)  
Drive Profile 32-bit Reference 1 word  
Drive Profile 32-bit Reference 1 word  
Drive Profile 32-bit Reference 1 word (High Byte)  
DATA OUT 1 Value (Low Byte)  
DATA OUT 1 Value (High Byte)  
10 DATA OUT 2 Value (Low Byte)  
11 DATA OUT 2 Value (High Byte)  
12 DATA OUT 3 Value (Low Byte)  
13 DATA OUT 3 Value (High Byte)  
14 DATA OUT 4 Value (Low Byte)  
15 DATA OUT 4 Value (High Byte)  
16 DATA OUT 5 Value (Low Byte)  
17 DATA OUT 5 Value (High Byte)  
18 DATA OUT 6 Value (Low Byte)  
19 DATA OUT 6 Value (High Byte)  
20 DATA OUT 7 Value (Low Byte)  
21 DATA OUT 7 Value (High Byte)  
 
Communication protocol 127  
Instance 921  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
22  
23  
24  
25  
26  
27  
DATA OUT 8 Value (Low Byte)  
DATA OUT 8 Value (High Byte)  
DATA OUT 9 Value (Low Byte)  
DATA OUT 9 Value (High Byte)  
DATA OUT 10 Value (Low Byte)  
DATA OUT 10 Value (High Byte)  
The format of the input assembly is:  
Instance 971  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
6
7
8
9
Drive Profile 32-bit Status word (Low Byte)  
Drive Profile 32-bit Status word  
Drive Profile 32-bit Status word  
Drive Profile 32-bit Status word (High Byte)  
Drive Profile 32-bit Actual 1 word (Low Byte)  
Drive Profile 32-bit Actual 1 word (High Byte)  
Drive Profile 32-bit Actual 1 word  
Drive Profile 32-bit Actual 1 word (High Byte)  
DATA IN 1 Value (Low Byte)  
DATA IN 1 Value (High Byte)  
10 DATA IN 2 Value (Low Byte)  
11 DATA IN 2 Value (High Byte)  
12 DATA IN 3 Value (Low Byte)  
13 DATA IN 3 Value (High Byte)  
14 DATA IN 4 Value (Low Byte)  
15 DATA IN 4 Value (High Byte)  
16 DATA IN 5 Value (Low Byte)  
17 DATA IN 5 Value (High Byte)  
128 Communication protocol  
Instance 971  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
18 DATA IN 6 Value (Low Byte)  
19 DATA IN 6 Value (High Byte)  
20 DATA IN 7 Value (Low Byte)  
21 DATA IN 7 Value (High Byte)  
22 DATA IN 8 Value (Low Byte)  
23 DATA IN 8 Value (High Byte)  
24 DATA IN 9 Value (Low Byte)  
25 DATA IN 9 Value (High Byte)  
26 DATA IN 10 Value (Low Byte)  
27 DATA IN 10 Value (High Byte)  
Transparent 32 with two assembly  
The Transparent 32 with two assembly, defined by ABB, provides  
unaltered 32-bit access to the configured drive profile.  
The format of the output assembly is:  
Instance 822  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
6
7
Drive Profile 32-bit Control word (Low Byte)  
Drive Profile 32-bit Control word  
Drive Profile 32-bit Control word  
Drive Profile 32-bit Control word (High Byte)  
Drive Profile 32-bit Reference 1 word (Low Byte)  
Drive Profile 32-bit Reference 1 word  
Drive Profile 32-bit Reference 1 word  
Drive Profile 32-bit Reference 1 word (High Byte)  
 
Communication protocol 129  
Instance 822  
8
9
Drive Profile 32-bit Reference 2 word (Low Byte)  
Drive Profile 32-bit Reference 2 word  
10 Drive Profile 32-bit Reference 2 word  
11 Drive Profile 32-bit Reference 2 word (High Byte)  
The format of the input assembly is:  
Instance 872  
Byte Bit 7 Bit 6  
Bit 5  
Bit 4 Bit 3 Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
6
7
8
9
Drive Profile 32-bit Status word (Low Byte)  
Drive Profile 32-bit Status word  
Drive Profile 32-bit Status word  
Drive Profile 32-bit Status word (High Byte)  
Drive Profile 32-bit Actual 1 word (Low Byte)  
Drive Profile 32-bit Actual 1 word  
Drive Profile 32-bit Actual 1 word  
Drive Profile 32-bit Actual 1 word (High Byte)  
Drive Profile 32-bit Actual 2 word (Low Byte)  
Drive Profile 32-bit Actual 2 word  
10 Drive Profile 32-bit Actual 2 word  
11 Drive Profile 32-bit Actual 2 word (High Byte)  
130 Communication protocol  
Transparent 32 with two assembly plus drive  
parameters  
The Transparent 32 with two assembly plus drive parameters,  
defined by ABB, adds configurable drive parameters to the  
Transparent 32 with two assembly.  
The format of the output assembly is:  
Instance 922  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
6
7
8
9
Drive Profile 32-bit Control word (Low Byte)  
Drive Profile 32-bit Control word  
Drive Profile 32-bit Control word  
Drive Profile 32-bit Control word (High Byte)  
Drive Profile 32-bit Reference 1 word (Low Byte)  
Drive Profile 32-bit Reference 1 word  
Drive Profile 32-bit Reference 1 word  
Drive Profile 32-bit Reference 1 word (High Byte)  
Drive Profile 32-bit Reference 2 word (Low Byte)  
Drive Profile 32-bit Reference 2 word  
10 Drive Profile 32-bit Reference 2 word  
11 Drive Profile 32-bit Reference 2 word (High Byte)  
12 DATA OUT 1 Value (Low Byte)  
13 DATA OUT 1 Value (High Byte)  
14 DATA OUT 2 Value (Low Byte)  
15 DATA OUT 2 Value (High Byte)  
16 DATA OUT 3 Value (Low Byte)  
17 DATA OUT 3 Value (High Byte)  
18 DATA OUT 4 Value (Low Byte)  
19 DATA OUT 4 Value (High Byte)  
20 DATA OUT 5 Value (Low Byte)  
21 DATA OUT 5 Value (High Byte)  
 
Communication protocol 131  
Instance 922  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
22 DATA OUT 6 Value (Low Byte)  
23 DATA OUT 6 Value (High Byte)  
24 DATA OUT 7 Value (Low Byte)  
25 DATA OUT 7 Value (High Byte)  
26 DATA OUT 8 Value (Low Byte)  
27 DATA OUT 8 Value (High Byte)  
28 DATA OUT 9 Value (Low Byte)  
29 DATA OUT 9 Value (High Byte)  
30 DATA OUT 10 Value (Low Byte)  
31 DATA OUT 10 Value (High Byte)  
The format of the input assembly is:  
Instance 972  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
0
1
2
3
4
5
6
7
8
9
Drive Profile 32-bit Status word (Low Byte)  
Drive Profile 32-bit Status word  
Drive Profile 32-bit Status word  
Drive Profile 32-bit Status word (High Byte)  
Drive Profile 32-bit Actual 1 word (Low Byte)  
Drive Profile 32-bit Actual 1 word  
Drive Profile 32-bit Actual 1 word  
Drive Profile 32-bit Actual 1 word (High Byte)  
Drive Profile 32-bit Actual 2 word (Low Byte)  
Drive Profile 32-bit Actual 2 word  
10 Drive Profile 32-bit Actual 2 word  
11 Drive Profile 32-bit Actual 2 word (High Byte)  
12 DATA IN 1 Value (Low Byte)  
13 DATA IN 1 Value (High Byte)  
132 Communication protocol  
Instance 972  
Byte Bit 7  
Bit 6  
Bit 5 Bit 4  
Bit 3  
Bit 2  
Bit 1  
Bit 0  
14 DATA IN 2 Value (Low Byte)  
15 DATA IN 2 Value (High Byte)  
16 DATA IN 3 Value (Low Byte)  
17 DATA IN 3 Value (High Byte)  
18 DATA IN 4 Value (Low Byte)  
19 DATA IN 4 Value (High Byte)  
20 DATA IN 5 Value (Low Byte)  
21 DATA IN 5 Value (High Byte)  
22 DATA IN 6 Value (Low Byte)  
23 DATA IN 6 Value (High Byte)  
24 DATA IN 7 Value (Low Byte)  
25 DATA IN 7 Value (High Byte)  
26 DATA IN 8 Value (Low Byte)  
27 DATA IN 8 Value (High Byte)  
28 DATA IN 9 Value (Low Byte)  
29 DATA IN 9 Value (High Byte)  
30 DATA IN 10 Value (Low Byte)  
31 DATA IN 10 Value (High Byte)  
Communication protocol 133  
Class objects  
The following table lists the data types used in the class object  
descriptions of this manual. The table also includes the  
corresponding data type names of the Common Industrial Protocol  
(CIP) Specification.  
Data type  
UINT8  
CIP data type name Data type description  
USINT  
UINT  
Unsigned 8-bit integer value  
Unsigned 16-bit integer value  
Unsigned 32-bit integer value  
Signed 8-bit integer value  
Signed 16-bit integer value  
Bit string – 8 bits  
UINT16  
UINT32  
SINT8  
UDINT  
SINT  
SINT16  
BYTE  
INT  
BYTE  
WORD  
BOOL  
WORD  
BOOL  
Bit string – 16 bits  
Logical Boolean with values TRUE  
(1) and FALSE (0)  
Short String SHORT_STRING  
Character string (1 byte per  
character, 1-byte length indicator)  
Note: The adapter module is designed to provide DeviceNet  
communications for a variety of drives with different capabilities.  
Default, minimum and maximum values for attributes necessarily  
vary based upon the capabilities of the drive to which the module is  
attached and are not documented herein. Default, minimum and  
maximum values for attributes may be found in the:  
User’s manual for the drive  
Electronic Data Sheet Files (EDS) for the drive.  
Note that the units of the attributes may differ from those of the  
parameters documented elsewhere and those differences must be  
considered when interfacing to the drive via the module.  
 
134 Communication protocol  
The table below lists the service names of the objects:  
Service  
GET  
Name  
0x0E Get_Attribute_Single  
0x10 Set_Attribute_Single  
0x02 Set_Attribute_All  
0x01 Get_Attribute_All  
SET  
SET ALL  
GET ALL  
Identity object, class 01h  
This object provides identification of and general information about  
the device.  
Class attributes (Instance #0)  
#
Attribute Services Description  
name  
Data  
type  
1
Revision  
Get  
Revision of the Identity Object  
UINT8  
     
Communication protocol 135  
Instance attributes (Instance #1)  
#
1
2
3
4
5
6
Attribute Services Description  
name  
Data type  
Vendor ID Get  
Identification of the device  
UINT16  
UINT16  
UINT16  
vendor  
Device  
Type  
Get  
Get  
Get  
Get  
Get  
Identification of the general  
product type  
Product  
Code  
Assigned vendor code  
describing the device  
Revision  
Revision of the item that the  
identity object represents  
Array[UINT8  
UINT8]  
Status  
Summary status of the  
device  
WORD  
ODVA  
Serial  
Serial number of the  
DeviceNet module  
UINT32  
Number  
7
8
Product  
Name  
Get  
Get  
Product identification; max 32 Short String  
characters  
State  
Present state of the device  
UINT8  
Attribute explanations  
Vendor ID  
Vendor IDs are managed by the Open DeviceNet Vendor  
Association, Inc. (ODVA). The ABB Vendor ID is 46.  
Device Type  
The list of device types is managed by ODVA. It is used to identify  
the device profile that a particular product is using. For example, 2  
= AC drive, 13 = DC drive  
Product Code  
Every ABB drive type or application of the drive has a dedicated  
product code.  
Revision  
Revision attribute, which consists of Major and Minor Revisions,  
identifies the revision of the item the identity object represents.  
   
136 Communication protocol  
Status  
This attribute represents the current status of the entire device. Its  
value changes as the state of the device changes. The Status  
attribute is a WORD with the following bit definitions:  
Bit(s)  
Type/Name  
Definition  
0
Owned  
TRUE indicates that the device (or an object  
within the device) has an owner. Within the  
Master/Slave paradigm the setting of this bit  
means that the Predefined Master/Slave  
Connection Set has been allocated to a  
master. Outside the Master/Slave paradigm  
the meaning of this bit is to be defined.  
1
2
Reserved, set to 0  
Configured  
TRUE indicates the application of the  
device has been configured to do  
something that differs from the “out–of–box”  
default. This does not include configuration  
of the communications.  
3
Reserved, set to 0  
4, 5, 6, 7  
8
Vendor-specific, set to 0  
Minor  
Recoverable  
Fault  
TRUE indicates the device detected a  
recoverable problem. The problem does not  
cause the device fault state.  
9
Minor  
Unrecoverable  
Fault  
TRUE indicates the device detected a  
unrecoverable problem. The problem does  
not cause the device fault state.  
10  
11  
Major  
Recoverable  
Fault  
TRUE indicates the device detected a  
problem which caused the device to transfer  
into the “Major Recoverable Fault” state.  
Major  
Unrecoverable  
Fault  
TRUE indicates the device detected a  
problem which caused the device to transfer  
into the “Major Unrecoverable Fault” state.  
12, 13,  
14, 15  
Reserved, set to 0  
Communication protocol 137  
ODVA Serial Number:  
This attribute is a number used in conjunction with the Vendor ID to  
form a unique identifier for each device on DeviceNet. The value of  
this attribute is 02000000h plus the SERNO value from the device  
label.  
Product Name:  
This text string should represent a short description of the  
product/product family represented by the product code in attribute  
3.  
State:  
Represents current state of the identity object  
Value  
State  
0
1
2
3
4
5
Nonexistent  
Device Self Testing  
Standby  
Operational  
Major Unrecoverable Fault  
Minor Unrecoverable Fault  
DeviceNet object, class 03h  
The DeviceNet object provides the configuration and status of a  
DeviceNet port. Each DeviceNet product must support one (and  
only one) DeviceNet object per physical connection to the  
DeviceNet communication link.  
Class attributes  
#
Attribute  
name  
Class attributes  
(Instance #0)  
Description  
Data  
type  
1
Revision  
Get  
Revision of the  
UINT8  
DeviceNet Object Class  
Definition on which the  
implementation is based  
   
138 Communication protocol  
Instance attributes  
#
Attribute  
name  
Instance attributes Description  
(Instance #1)  
Data  
type  
1
2
5
MAC ID  
Get, Set  
Node address  
UINT8  
Baud Rate Get, Set  
Baud rate of the device UINT8  
Allocation  
information  
Get, Set  
Allocation Choice  
Master’s MAC ID  
Struct:  
BYTE  
UINT8  
The Allocation Information attribute consists of the following:  
Allocation Choice Byte (BYTE)  
The Allocation Choice byte indicates which of the Predefined  
Master/Slave Connections are active (in the Configuring, or  
Established state).  
The Allocation Choice byte is initialized to 00 at device power-  
up or reset.  
Master’s MAC ID (UINT8)  
The range of values is 0…63 and 255 decimal. A value in the  
range of 0…63 indicates that the Predefined Master/Slave  
Connection Set is currently allocated and denotes the MAC ID  
of the device that performed the allocation. The value 255  
means that the Predefined Master/Slave Connection set has  
not been allocated. The Master’s MAC ID attribute is initialized  
to 255 (FF hex) at device power-up/reset.  
Connection object, class 05h  
Note: Do not modify this object. This object is only used while  
establishing the connection between the adapter module and the  
PLC.  
The connection class allocates and manages the internal  
resources associated with both I/O and explicit messaging  
connections. The specific instance generated by the connection  
class is referred to as connection instance or connection object.  
   
Communication protocol 139  
The table below shows the connection object states:  
State Description  
State Description  
00  
01  
02  
Nonexistent  
03  
04  
05  
Established  
Timed Out  
Configuring  
Waiting for Connection ID  
Deferred Delete  
Class attributes  
#
Attribute Services Description  
name  
Data  
type  
1
Revision Get  
Revision of the connection object UINT8  
Instance attributes  
Instance number  
Description  
1
2
4
Explicit messaging connection  
Polled I/O connection  
Change-of-state/Cyclic I/O connection  
#
1
2
3
Attribute  
name  
Services Description  
Data  
type  
State  
Get  
Get  
Get  
State of the object (See the  
state table on page 138.)  
UINT8  
UINT8  
UINT8  
Instance  
Type  
Indicates either I/O (1) or  
messaging connection (0).  
Transport  
Class Trig-  
ger  
Defines the behavior of the  
connection.  
4
5
Produced  
Cnxn Id  
Get  
Get  
Placed in the CAN Identifier  
Field when the connection  
transmits  
UINT16  
Consumed  
Cnxn Id  
CAN Identifier Field value that UINT16  
denotes the message to be  
received  
   
140 Communication protocol  
#
Attribute  
name  
Services Description  
Data  
type  
6
Comm Char- Get  
acteristics  
Defines the message  
group(s) across which  
productions and  
UINT8  
consumptions are associated  
in this connection.  
7
8
9
Produced  
Connection  
Size  
Get  
Maximum number of bytes  
transmitted across this  
connection  
UINT16  
UINT16  
Consumed  
Connection  
size  
Get  
Maximum number of bytes  
received across this  
connection  
Expected  
Packet Rate  
Get, Set  
Defines the timing associated UINT16  
with this connection in  
milliseconds. A value of 0  
deactivates the associated  
timers.  
12 Watchdog  
Timeout  
Get, Set  
Get  
Defines how to handle  
inactivity/watchdog time-outs.  
UINT8  
Action  
13 Produced  
Connection  
Number of bytes in the  
produced_connection_path  
length attribute  
UINT16  
Path Length  
14 Produced  
Connection  
Path  
Get  
Application object producing  
data on this connection  
Array of  
UINT8  
15 Consumed  
Connection  
Get  
Number of bytes in the  
consumed_connection_path  
length attribute  
UINT16  
Path Length  
16 Consumed  
Connection  
Path  
Get  
Specifies the application  
object(s) receiving the data  
consumed by this connection  
object.  
Array of  
UINT8  
17 Production  
Inhibit Time  
Get  
Defines the minimum time  
between new data production  
in milliseconds  
UINT16  
Communication protocol 141  
Acknowledge handler object, class 2Bh  
The acknowledge handler object is used to manage the reception  
of message acknowledgements. This object communicates with a  
message producing application object within the device. The  
acknowledge handler object notifies the producing application of  
acknowledge reception, acknowledge time-outs and production  
retry limit.  
Class attributes (Instance #0)  
#
Attribute Services Description  
name  
Data  
type  
1
Revision  
Get  
Revision of the DeviceNet  
Object Class Definition upon  
which the implementation is  
based  
UINT8  
Instance attributes (Instance #1)  
#
1
2
Attribute  
name  
Services Description  
Data  
type  
Acknowl-  
edge Timer  
Get, Set  
Time in milliseconds to wait for UINT16  
acknowledge before resending  
Retry Limit Get, Set  
Number of Acknowledge  
Timeouts to wait before  
informing the producing  
application of a Retry-  
Limit_Reached event  
UINT8  
3
COS  
Get  
Connection Instance Id which  
contains the path of the  
producing I/O application object  
which is notified of the  
UINT16  
Producing  
Connection  
Instance  
Acknowledge Handler events  
     
142 Communication protocol  
Motor data object, class 28h  
This object serves as a database for motor parameters. Different  
motor types require different data to describe the motor. For  
example, AC induction motors do not need field current data like a  
DC motor to describe the motor.  
Motor class  
Motor types in class  
AC motors  
3 - PM synchronous  
6 - Wound rotor induction  
7 - Squirrel cage induction motor  
DC motors  
1 - PM DC motor  
2 - FC DC motor  
Class attributes (Instance #0)  
#
Attribute Services Description  
name  
Data  
type  
1
Revision  
Get  
Revision of the DeviceNet  
Object Class Definition upon  
which the implementation is  
based  
UINT8  
   
Communication protocol 143  
Instance attributes (Instance #1)  
#
3
6
Attribute Services Description  
name  
Motor  
type  
Data  
type  
Motor  
Type  
Get  
See the table describing AC  
the motor types above.  
UNIT16  
Rated  
Current  
Get, Set Rated stator current  
from motor name plate  
Units: [100mA]  
AC/DC UINT16  
7
8
9
Rated  
Voltage  
Get, Set Rated base voltage from AC/DC UINT16  
motor name plate  
Units: [V]  
Rated  
Power  
Get, Set Rated power at rated  
frequency  
AC/DC UINT32  
Units: [W]  
Rated  
Frequency  
Get, Set Rated electrical  
frequency  
AC  
AC  
UINT16  
UINT16  
Units: [Hz]  
12 Pole  
Count  
Get  
Number of poles in the  
motor  
15 Base  
Speed  
Get, Set Nominal speed at rated AC/DC UINT16  
frequency from  
nameplate units [RPM]  
Control supervisor object, class 29h  
The object models all the management functions for devices within  
the ‘Hierarchy of Motor Control Devices’. The behavior of motor  
control devices is described by the AC/DC-drive object, class 2Ah  
and the Run/Stop event matrix under Run Forward & Run Reverse  
(Control supervisor object). Section State (Control supervisor  
object) defines the states of the object.  
   
144 Communication protocol  
Class attributes (Instance #0)  
#
Attribute Services Description  
name  
Data  
type  
1
Revision  
Get  
Revision of the DeviceNet Object UINT8  
Class Definition upon which the  
implementation is based  
Instance attributes (Instance #1)  
#
Attribute  
name  
Services Description  
Data  
type  
3
Run 1  
Get, Set  
Get, Set  
0 = Stop, 1 = Run  
(See the Run/Stop event  
matrix on page 80.)  
BOOL  
4
Run 2  
0 = Stop, 1 = Run  
BOOL  
(See the Run/Stop event  
matrix on page 80.)  
5
6
Net Control  
State  
Get, Set  
Get  
0 = Local Control, 1 =  
Network Control  
BOOL  
UINT8  
State of Object  
(See section State (Control  
supervisor object).)  
7
8
9
Running 1  
Running 2  
Ready  
Get  
Get  
Get  
0 = Stopped, 1 = Running  
0 = Stopped, 1 = Running  
BOOL  
BOOL  
BOOL  
1 = Ready, Enabled or  
Stopping;  
0 = Other state  
10 Faulted  
11 Warning  
12 FaultRst  
Get  
0 = Not faulted, 1 = Fault  
occurred  
BOOL  
Get  
0 = No Warnings present, 1 = BOOL  
Warning  
Get, Set  
0
1 Fault Reset  
BOOL  
   
Communication protocol 145  
#
Attribute  
name  
Services Description  
Data  
type  
13 Fault Code  
Get  
The fault that caused the last UINT16  
transition to the Faulted state.  
DRIVECOMM codes are  
reported. See the drive  
manual for further information  
on the DRIVECOMM codes.  
14 Warning Code Get  
Code word indicating a  
warning. If multiple warnings  
are present, the lowest code  
value is displayed.  
UINT16  
DRIVECOMM codes are  
reported. See the drive  
manual for further information  
on DRIVECOMM codes.  
15 CtlFromNet  
Get  
0 = NetControl disabled  
1 = NetControl enabled  
BOOL  
16 DNFaultMode Get, Set  
17 ForceFault Get, Set  
2 = Vendor specified  
UINT8  
BOOL  
0
1 forces the drive to  
fault  
146 Communication protocol  
AC/DC-drive object, class 2Ah  
This object models the functions specific to an AC or DC Drive.  
Class attributes (Instance #0)  
#
Attribute Services Description  
name  
Data  
type  
1
Revision  
Get  
Revision of the DeviceNet Object UINT8  
Class Definition upon which the  
implementation is based  
Instance attributes (Instance #1)  
#
3
4
Attribute  
name  
Services Description  
Data  
type  
At  
Get  
Frequency arrival  
BOOL  
Reference  
NetRef  
Get, Set  
Requests torque or speed  
reference to be local or from the  
network.  
BOOL  
0 = Set Reference not DN Control  
1 = Set Reference at DN Control  
Note that the actual status of  
Torque or Speed Reference is  
reflected in attribute 29,  
RefFromNet.  
6
7
8
Drive  
mode  
Get, Set  
Get  
0 = Vendor specific  
UINT8  
Speed  
Actual  
Units = See parameter description SINT16  
10 ODVA SPEED SCALE.  
SpeedRef Get, Set  
Units = See parameter description SINT16  
10 ODVA SPEED SCALE.  
11 Torque  
Actual  
Get  
Units = See parameter description SINT16  
11 ODVA TORQUE SCALE.  
12 TorqueRef Get, Set  
Units = See parameter description SINT16  
11 ODVA TORQUE SCALE.  
18 AccelTime Get, Set  
19 DecelTime Get, Set  
Units = milliseconds [ms]  
Units = milliseconds [ms]  
UINT16  
UINT16  
       
Communication protocol 147  
#
Attribute  
name  
Services Description  
Data  
type  
22 Speed  
Scale  
Get, Set  
Speed scaling factor. See  
parameter description 10 ODVA  
SPEED SCALE.  
UINT8  
UINT8  
BOOL  
24 Torque  
Scale  
Get, Set  
Get  
Torque scaling factor. See  
parameter description 11 ODVA  
TORQUE SCALE.  
29 Ref From  
Net  
Reflecting attribute 4  
Drive parameter object, Class 90h  
With FDNA-01, drive parameters can also be accessed via explicit  
messaging. Explicit messaging makes use of objects consisting of  
three parts: class, instance and attribute.  
Note: When using the Drive parameter object to update the  
fieldbus configuration groups, changes to the fieldbus configuration  
will only take effect when the module is powered up the next time  
or when a ‘Fieldbus Adapter parameter refresh’ is given.  
Class is always 144 (90h). Instance and attribute correspond to the  
drive parameter group and index in the following way:  
Instance  
Attribute  
=
=
Parameter group (0…99)  
Parameter index (01…99)  
For example, parameter 99.01 is accessed as follows:  
Class  
=
=
=
144  
99  
1
=
=
=
90h  
63h  
01h  
Instance  
Attribute  
   
148 Communication protocol  
Fieldbus configuration object 91h  
The Fieldbus configuration object allows the user to configure the  
fieldbus configuration groups without needing to know the drive-  
specific groups associated with the configuration groups.  
Note: When using the Fieldbus configuration object to update the  
fieldbus configuration groups, changes to the fieldbus configuration  
will only take effect when a reset service of the Identity Object is  
requested, the module is powered up the next time or when a  
‘Fieldbus Adapter parameter refresh’ is given.  
Class attributes  
#
Attribute Services Description  
name  
Data  
type  
1
Revision  
Get  
Revision of the configuration  
object  
UINT8  
Instance #1: FDNA-01 configuration parameters  
group A (group 1)  
The actual parameter group number depends on the drive type.  
Group A (group 1) corresponds to:  
parameter group 51 in ACS355, ACSM1, ACS850 and  
ACQ810  
parameter group 51 in ACS880 if the adapter is installed as  
fieldbus adapter A or group 54 if the adapter is installed as  
fieldbus adapter B.  
#
Attribute name  
Services Description  
Data  
type  
1
Configuration Group Get, Set See 01 FBA TYPE.  
A (Group 1) –  
Parameter 1  
UINT16  
UINT16  
UINT16  
2
3
Configuration Group Get, Set See 02 MAC ID.  
A (Group 1) –  
Parameter 2  
Configuration Group Get, Set See 03 BAUD RATE.  
A (Group 1) –  
Parameter 3  
       
Communication protocol 149  
#
Attribute name  
Services Description  
Data  
type  
4
Configuration Group Get, Set See 04 DRIVE  
UINT16  
UINT16  
UINT16  
UINT16  
UINT16  
UINT16  
UINT16  
A (Group 1) –  
Parameter 4  
PROFILE.  
5
6
7
8
9
Configuration Group Get, Set See 05 ODVA STOP  
A (Group 1) –  
Parameter 5  
FUNC.  
Configuration Group Get, Set See 06 OUTPUT  
A (Group 1) –  
Parameter 6  
INSTANCE.  
Configuration Group Get, Set See 07 OUTPUT NUM  
A (Group 1) –  
Parameter 7  
PARS.  
Configuration Group Get, Set See 08 INPUT  
A (Group 1) –  
Parameter 8  
INSTANCE.  
Configuration Group Get, Set See 09 INPUT NUM  
A (Group 1) –  
Parameter 9  
PARS.  
10 Configuration Group Get, Set See 10 ODVA SPEED  
A (Group 1) –  
Parameter 10  
SCALE.  
11 Configuration Group Get, Set See 11 ODVA TORQUE UINT16  
A (Group 1) –  
Parameter 11  
SCALE.  
12 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 12  
13 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 13  
14 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 14  
15 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 15  
150 Communication protocol  
Attribute name Services Description  
#
Data  
type  
16 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 16  
17 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 17  
18 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 18  
19 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 19  
20 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 20  
21 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 21  
22 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 22  
23 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 23  
24 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 24  
25 Configuration Group Get, Set See 12 … 25 Reserved. UINT16  
A (Group 1) –  
Parameter 25  
26 Configuration Group Get, Set See 26  
UINT16  
UINT16  
A (Group 1) –  
Parameter 26  
UNRECOVERABLE  
ERROR.  
27 Configuration Group Get, Set See 27 FBA PAR  
A (Group 1) –  
Parameter 27  
REFRESH.  
Communication protocol 151  
#
Attribute name  
Services Description  
Data  
type  
28 Configuration Group Get  
A (Group 1) –  
See 28 PAR TABLE  
VER.  
UINT16  
UINT16  
UINT16  
UINT16  
Parameter 28  
29 Configuration Group Get  
A (Group 1) –  
See 29 DRIVE TYPE  
CODE.  
Parameter 29  
30 Configuration Group Get  
A (Group 1) –  
See 30 MAPPING FILE  
VER.  
Parameter 30  
31 Configuration Group Get  
A (Group 1) –  
See 31 D2FBA COMM  
STA.  
Parameter 31  
32 Configuration Group Get  
A (Group 1) –  
See 32 FBA COMM SW UINT16  
VER.  
Parameter 32  
33 Configuration Group Get  
A (Group 1) –  
See 33 FBA APPL SW  
VER.  
UINT16  
Parameter 33  
Instance #2: FDNA-01 configuration parameters  
group B (group 2)  
The actual parameter group number depends on the drive type.  
Group B (group 2) corresponds to  
parameter group 55 in ACS355  
parameter group 53 in ACSM1, ACS850 and ACQ810  
parameter group 53 in ACS880 if the adapter is installed as  
fieldbus adapter A or group 56 if the adapter is installed as  
fieldbus adapter B.  
#
1
2
Attribute name  
Services Description  
Data  
type  
Configuration Group B  
(Group 2) – Parameter 1  
Get, Set  
UINT16  
UINT16  
See 01 DATA OUT 1.  
See 01 DATA OUT 1.  
Configuration Group B  
(Group 2) – Parameter 2  
Get, Set  
 
152 Communication protocol  
#
3
4
5
6
7
8
9
Attribute name  
Services Description  
Data  
type  
Configuration Group B  
(Group 2) – Parameter 3  
Get, Set See 01 DATA OUT 1. UINT16  
Get, Set See 01 DATA OUT 1. UINT16  
Get, Set See 01 DATA OUT 1. UINT16  
Get, Set See 01 DATA OUT 1. UINT16  
Get, Set See 01 DATA OUT 1. UINT16  
Get, Set See 01 DATA OUT 1. UINT16  
Get, Set See 01 DATA OUT 1. UINT16  
Get, Set See 01 DATA OUT 1. UINT16  
Configuration Group B  
(Group 2) – Parameter 4  
Configuration Group B  
(Group 2) – Parameter 5  
Configuration Group B  
(Group 2) – Parameter 6  
Configuration Group B  
(Group 2) – Parameter 7  
Configuration Group B  
(Group 2) – Parameter 8  
Configuration Group B  
(Group 2) – Parameter 9  
10 Configuration Group B  
(Group 2) – Parameter  
10  
Instance #3: FDNA-01 configuration parameters  
group C (group 3)  
The actual parameter group number depends on the drive type.  
Group C (group 3) corresponds to:  
parameter group 54 in ACS355  
parameter group 52 in ACSM1, ACS850 and ACQ810  
parameter group 52 in ACS880 if the adapter is installed as  
fieldbus adapter A or group 55 if the adapter is installed as  
fieldbus adapter B.  
#
1
2
Attribute name  
Services Description  
Data  
type  
Configuration Group C  
(Group 3) - Parameter 1  
Get, Set  
UINT16  
See 01 DATA IN 1.  
See 01 DATA IN 1.  
Configuration Group C  
(Group 3) - Parameter 2  
Get, Set  
UINT16  
 
Communication protocol 153  
#
3
4
5
6
7
8
9
Attribute name  
Services Description  
Data  
type  
Configuration Group C  
(Group 3) - Parameter 3  
Get, Set  
Get, Set  
Get, Set  
Get, Set  
Get, Set  
Get, Set  
Get, Set  
Get, Set  
See 01 DATA IN 1. UINT16  
See 01 DATA IN 1. UINT16  
See 01 DATA IN 1. UINT16  
See 01 DATA IN 1. UINT16  
See 01 DATA IN 1. UINT16  
See 01 DATA IN 1. UINT16  
See 01 DATA IN 1. UINT16  
See 01 DATA IN 1. UINT16  
Configuration Group C  
(Group 3) - Parameter 4  
Configuration Group C  
(Group 3) - Parameter 5  
Configuration Group C  
(Group 3) - Parameter 6  
Configuration Group C  
(Group 3) - Parameter 7  
Configuration Group C  
(Group 3) - Parameter 8  
Configuration Group C  
(Group 3) - Parameter 9  
10 Configuration Group C  
(Group 3) - Parameter  
10  
154 Communication protocol  
Diagnostics 155  
9
Diagnostics  
What this chapter contains  
This chapter explains how to trace faults with the status LEDs on  
the adapter module.  
     
156 Diagnostics  
LED indications  
The adapter module is equipped with three diagnostic LEDs. The  
LEDs are described below.  
Name  
Color  
Function  
Blinking green  
Green  
Establishing communication to host  
Communication to host ok  
Communication to host lost temporarily  
Blinking red  
HOST  
Flashingorange, Internal file system error. The error may  
alternating with  
the MODULE  
be cleared by cycling drive power. If the  
error persists, contact your local ABB  
flashing orange representative.  
 
Diagnostics 157  
Name  
Color  
Function  
Off  
There is no power applied to the device.  
Device is operating in a normal condition.  
Green  
Flashing green  
Device needs commissioning due to  
configuration missing, incomplete or  
incorrect. The device may be in the  
standby state.  
Flashing red  
Red  
Recoverable fault  
Device has an unrecoverable fault. This  
may be cleared by:  
Fieldbus Adapter parameter refresh  
cycling DeviceNet network power or  
cycling drive power.  
MODULE  
This may have been caused by:  
duplicate MAC error  
bus-off condition or  
buffer overflow.  
Flashing red-  
green  
Device is in self-test.  
Flashingorange, Internal file system error. The error may  
alternating with  
the HOST  
be cleared by cycling drive power. If the  
error persists, contact your local ABB  
flashing orange representative.  
158 Diagnostics  
Name  
Color  
Function  
Off  
Device is not on-line.  
Device has not completed the  
Dup_MAC_ID test yet.  
Device may not be powered. Look at  
the Module Status LED.  
Flashing green  
Device is on-line but has no connections  
in the established state.  
Device has passed the Dup_MAC_ID  
test, is on-line, but has no established  
connections to other nodes.  
For a Group 2 Only device it means  
that this device is not allocated to a  
master.  
NETWORK  
Green  
Device is on-line and has connections in  
the established state.  
For a Group 2 Only device it means  
that the device is allocated to a master.  
Flashing red  
Red  
One or more I/O connections are in the  
timed-out state.  
Failed communication device. The device  
has detected an error that has rendered it  
incapable of communicating on the  
network (Duplicate MAC ID, or Bus-off).  
Technical data 159  
10  
Technical data  
What this chapter contains  
This chapter contains the technical data of the adapter module and  
the DeviceNet link.  
     
160 Technical data  
FDNA-01  
The figure below shows the enclosure of the adapter module from  
the front and side.  
Mounting  
Into the option slot of the drive  
IP20  
Degree of protection  
Ambient conditions  
Applicable ambient conditions specified for the  
drive in its manuals are in effect.  
Indicators  
Three bicolor LEDs (HOST, MODULE,  
NETWORK)  
Connectors  
20-pin connector to the drive  
Removable 5-pole screw type connector for bus  
2
connection (max. 2.5 mm cross section)  
 
Technical data 161  
Power supply  
Input voltage:  
From the drive: +3.3 V DC (+/- 5%)  
From the network: +24 V DC nominal (+11 V to  
+30 V)  
Input current:  
From the drive: 180 mA typical, 300 mA  
maximum (+3.3 V)  
From the network: 20 mA typical, 50 mA  
maximum (+24 V)  
General  
Estimated min. lifetime 100 000 h  
All materials UL/CSA-approved  
Complies with EMC standard EN 61800-3:2004  
Bus interface functionally isolated from the drive  
Printed circuit board conformal coated  
DeviceNet link  
Compatible devices  
Any ODVA-compliant DeviceNet scanner  
supporting Poll - Response commands to Group  
2 only Slaves  
Medium  
DeviceNet cables: YR-29790 (Thick DeviceNet  
Cable), YR-29832 (Thin DeviceNet Cable)  
Termination: 121 ohm, 1%, Metal Film, 1/4 W  
Maximum bus length: 1200 m  
Topology  
Multi-drop  
Transfer rate  
125, 250 or 500 kBit/s  
Asynchronous, Half duplex  
Serial communication  
type  
Protocol  
DeviceNet  
 
162 Technical data  
Appendix A – Varying the number of drive parameters 163  
11  
Appendix A – Varying the  
number of drive parameters  
What this chapter contains  
This chapter describes how to reduce the number of drive  
parameter members in FDNA-01 assemblies by modifying the  
EDS file.  
Modification of the EDS file  
Assembly object instances can either be dynamic or static. The  
FDNA-01 adapter module only supports static assembly objects.  
For each supported assembly, the member list (and implicitly, the  
length in bytes) has been fixed either by the ODVA AC/DC drive  
profile or ABB Drives profile.  
The FDNA-01 assemblies that include “plus drive parameters”  
have ten members each reserved for the output or input of drive  
parameters. In some cases, it may be desirable for these  
assemblies to have fewer drive parameter members. The adapter  
module provides the flexibility to accomplish this.  
However, this behavior is non-standard and usually requires  
additional configuration of the DeviceNet master as well. In  
particular, the length in bytes of the assembly must be changed to  
match the drive configuration. This can usually be accomplished  
by editing the EDS file for the drive or via manual configuration of  
the DeviceNet master. A description of how to change the EDS file  
       
164 Appendix A – Varying the number of drive parameters  
is provided below. For manual configuration, see the  
documentation for the DeviceNet master.  
Note: Only one EDS file with the same Product ID can be installed  
at a time. Changing the EDS file changes it for all drives with that  
Product ID. In situations where it is necessary to have different  
sizes of the same assembly on devices with the same Product ID,  
manual configuration is required.  
The number of drive parameters may be configured between one  
and ten for output and input by changing the configuration value of  
parameters 07 OUTPUT NUM PARS or 09 INPUT NUM PARS  
respectively. To use zero drive parameters, use the assembly upon  
which the "plus drive parameters" assembly is based.  
To change the EDS file, copy it to a new file name and open the  
copy with a text editor. Search for the [IO_Info] section of the file  
for the appropriate assembly. For example, the entry for the Basic  
speed control input plus drive parameters is below.  
Input7=  
24, 0, 0x0005,  
Length in bytes  
Basic speed control input + drive parameters",  
7, "20 04 24 AA 30 03",  
"Basic speed control input + drive parameters";  
The length in bytes needs to be updated to match the value from  
the table below. If more than one assembly "plus drive parameters"  
is being used, both assembly entries in the file must be changed.  
The assembly entries must be changed in all the "plus drive  
parameters" assemblies needing a custom number of parameters.  
Save the file. Use the new EDS file to configure the DeviceNet  
master.  
Appendix A – Varying the number of drive parameters 165  
Number of drive parameters  
Assembly  
1
6
2
8
3
4
5
6
7
8
9
10  
24  
24  
26  
26  
24  
24  
26  
26  
24  
26  
24  
26  
24  
26  
28  
32  
120  
121  
122  
123  
170  
171  
172  
173  
901  
902  
951  
952  
961  
962  
971  
972  
10  
10  
12  
12  
10  
10  
12  
12  
10  
12  
10  
12  
10  
12  
14  
18  
12  
12  
14  
14  
12  
12  
14  
14  
12  
14  
12  
14  
12  
14  
16  
20  
14  
14  
16  
16  
14  
14  
16  
16  
14  
16  
14  
16  
14  
16  
18  
22  
16  
16  
18  
18  
16  
16  
18  
18  
16  
18  
16  
18  
16  
18  
20  
24  
18  
18  
20  
20  
18  
18  
20  
20  
18  
20  
18  
20  
18  
20  
22  
26  
20  
20  
22  
22  
20  
20  
22  
22  
20  
22  
20  
22  
20  
22  
24  
28  
22  
22  
24  
24  
22  
22  
24  
24  
22  
24  
22  
24  
22  
24  
26  
30  
6
8
8
10  
10  
8
8
6
6
8
8
10  
10  
8
8
6
8
10  
8
6
8
10  
8
6
8
10  
12  
16  
10  
14  
166 Appendix A – Varying the number of drive parameters  
Further information  
Product and service inquiries  
Address any inquiries about the product to your local ABB  
representative, quoting the type designation and serial number of  
the unit in question. A listing of ABB sales, support and service  
contacts can be found by navigating to www.abb.com/drives and  
selecting Sales, Support and Service network.  
Product training  
For information on ABB product training, navigate to  
www.abb.com/drives and select Training courses.  
Providing feedback on ABB Drives manuals  
Your comments on our manuals are welcome. Go to  
www.abb.com/drives and select Document Library Manuals  
feedback form (LV AC drives).  
Document library on the Internet  
You can find manuals and other product documents in PDF format  
on the Internet. Go to www.abb.com/drives and select Document  
Library. You can browse the library or enter selection criteria, for  
example a document code, in the search field.  
           
Contact us  
ABB Oy  
ABB Inc.  
ABB Beijing Drive Systems  
Co. Ltd.  
Drives  
Automation Technologies  
Drives & Motors  
16250 West Glendale Drive  
New Berlin, WI 53151  
USA  
P.O. Box 184  
FI-00381 HELSINKI  
FINLAND  
No. 1, Block D,  
A-10 Jiuxianqiao Beilu  
Chaoyang District  
Telephone +358 10 22 11  
Beijing, P.R. China, 100015  
Telephone +86 10 5821 7788  
Fax  
+358 10 22 22681 Telephone 262 785-3200  
1-800-HELP-365 Fax  
262 780-5135 www.abb.com/drives  
+86 10 5821 7618  
Fax  

NAD VISO TWO User Manual
LG Electronics Tritan UX840H User Manual
Lantronix UBOX 4100 User Manual
La Crosse Technology Wireless 433 MHz Temperature Station WS 9014U User Manual
JVC KW NX7000 User Manual
Hitachi Travelstar 7K750 User Manual
Gemini CD 1800X User Manual
Denon RCD M33 User Manual
Bookendz BE MBP17 User Manual
Black Box Computer Accessories LPJ016A FM User Manual