—

ABB INDUSTRIAL DRIVES

FEIP-21 EtherNet/IP fieldbus adapter module

User's manual
User's manual
FEIP-21 EtherNet/IP fieldbus adapter module

Table of contents

1. Safety instructions

4. Mechanical installation

5. Electrical installation

6. EtherNet/IP – Start-up

© 2018 ABB Oy. All Rights Reserved. 3AXD50000158621 Rev A

EN
EFFECTIVE: 2018-12-18
 Table of contents 5

Table of contents

1 Safety instructions
Contents of this chapter .......................................................................... 9
Use of warnings and notes ...................................................................... 9
Safety in installation and maintenance ........................................................ 9

2 Introduction to the manual

Contents of this chapter .......................................................................... 11
Applicability ........................................................................................ 11
Compatibility ....................................................................................... 11
Drives ........................................................................................... 11
Protocol ......................................................................................... 11
Target audience ................................................................................... 12
Purpose of the manual ........................................................................... 12
Cybersecurity disclaimer ......................................................................... 12
Terms and abbreviations ......................................................................... 12
Related manuals .................................................................................. 13

3 Overview of the Ethernet network and the FEIP-21 module

Contents of this chapter .......................................................................... 15
Ethernet network .................................................................................. 15
Example topology of the Ethernet link ...................................................... 15
FEIP-21 module overview ....................................................................... 17
FEIP-21 layout ................................................................................. 18

4 Mechanical installation
Contents of this chapter .......................................................................... 19
Necessary tools and instructions ............................................................... 19
Unpacking and examining the delivery ........................................................ 19
Installing the module ............................................................................. 20

5 Electrical installation
Contents of this chapter .......................................................................... 23
Necessary tools and instructions ............................................................... 23
General cabling instructions ..................................................................... 23
Connecting the FEIP-21 to the Ethernet network ............................................ 23

6 EtherNet/IP – Start-up
Contents of this chapter .......................................................................... 25
Warnings ........................................................................................... 25
Drive configuration ................................................................................ 25
EtherNet/IP connection configuration ...................................................... 25
FEIP-21 configuration parameters – group A (group 1) .............................. 26
FEIP-21 configuration parameters – group B (group 2) .............................. 33
FEIP-21 configuration parameters – group C (group 3) .............................. 34
6 Table of contents

Control locations ............................................................................... 34

Starting up fieldbus communication for the drive ............................................. 34
Parameter setting examples – ACS380, ACS480, ACS580 and ACS880 ............ 35
Speed control using the ODVA AC/DC drive profile, Extended speed control
assembly .................................................................................... 35
Configuring the client ............................................................................. 37
Before you start ................................................................................ 37
Select profile ................................................................................ 37
Select output and input assembly instances ........................................... 37
Select connection method ................................................................ 38
EDS files ........................................................................................ 39
Configuring an Allen-Bradley® PLC ........................................................ 39
Example 1: RSLogix 5000 ................................................................ 39
Example 2: Studio 5000 .................................................................. 43
Configuring DLR topology for FEIP-21 ..................................................... 48
Setup using Logix Designer .............................................................. 48
Setup using RSLinx® Classic ............................................................ 50

7 EtherNet/IP – Communication profiles

Contents of this chapter .......................................................................... 53
Communication profiles .......................................................................... 53
ODVA AC/DC drive profile ....................................................................... 54
ODVA output attributes ....................................................................... 55
Run Forward & Run Reverse (Control supervisor object) ........................... 55
Fault Reset (Control supervisor object) ................................................. 55
Net Ctrl (Control supervisor object) ..................................................... 55
Net Ref (AC/DC drive object) ............................................................ 55
Speed Reference (AC/DC drive object) ................................................ 55
Torque Reference (AC/DC drive object) ................................................ 56
ODVA input attributes ......................................................................... 57
Faulted (Control supervisor object) ..................................................... 57
Warning (Control supervisor object) .................................................... 57
Running Forward (Control supervisor object) ......................................... 57
Running Reverse (Control supervisor object) ......................................... 57
Ready (Control supervisor object) ....................................................... 57
Ctrl From Net (Control supervisor object) .............................................. 57
Ref From Net (AC/DC drive object) ..................................................... 57
At Reference (AC/DC drive object) ...................................................... 57
State (Control supervisor object) ........................................................ 57
Speed Actual (AC/DC drive object) ..................................................... 58
Torque Actual (AC/DC drive object) ..................................................... 59
ABB Drives communication profile ............................................................. 60
Control word and Status word ............................................................... 60
Control word contents ..................................................................... 60
Status word contents ...................................................................... 61
State machine .............................................................................. 62
References ..................................................................................... 63
Scaling ....................................................................................... 63
Actual values ................................................................................... 64
Scaling ....................................................................................... 64
 Table of contents 7

8 EtherNet/IP – Communication protocol

Contents of this chapter .......................................................................... 65
EtherNet/IP ........................................................................................ 65
Object modeling and functional profiles ....................................................... 65
Assembly objects ................................................................................. 65
Basic speed control assembly ............................................................... 66
Basic speed control plus drive parameters assembly .................................... 66
Extended speed control assembly .......................................................... 68
Extended speed control plus drive parameters assembly ............................... 69
Basic speed and torque control assembly ................................................. 70
Basic speed and torque control plus drive parameters assembly ...................... 71
Extended speed and torque control assembly ............................................ 73
Extended speed and torque control plus drive parameters assembly ................. 74
ABB Drives profile with set speed assembly .............................................. 76
ABB Drives profile with set speed plus drive parameters assembly ................... 76
ABB Drives profile with set speed and set torque assembly ............................ 78
ABB Drives profile with set speed and set torque plus drive parameters assembly .. 79
Transparent 16 with one assembly ......................................................... 81
Transparent 16 with one assembly plus drive parameters .............................. 81
Transparent 16 with two assembly ......................................................... 83
Transparent 16 with two assembly plus drive parameters .............................. 84
Transparent 32 with one assembly ......................................................... 86
Transparent 32 with one assembly plus drive parameters .............................. 86
Transparent 32 with two assembly ......................................................... 88
Transparent 32 with two assembly plus drive parameters .............................. 89
Class objects ...................................................................................... 92
Identity object, class 01h ..................................................................... 92
Class attributes (Instance #0) ............................................................ 92
Instance attributes (Instance #1) ........................................................ 92
Reset service (Service code 05h) ....................................................... 93
Attribute explanations ..................................................................... 93
Motor data object, class 28h ................................................................. 94
Class attributes (Instance #0) ............................................................ 95
Instance attributes (Instance #1) ........................................................ 95
Control supervisor object, class 29h ........................................................ 95
Class attributes (Instance #0) ............................................................ 96
Instance attributes (Instance #1) ........................................................ 96
AC/DC-drive object, class 2Ah .............................................................. 97
Class attributes (Instance #0) ............................................................ 97
Instance attributes (Instance #1) ........................................................ 97
Drive parameter object, class 90h .......................................................... 98
Fieldbus configuration object, class 91h ................................................... 99
Class attributes ............................................................................. 99
Instance #1: FEIP-21 configuration parameters group A (group 1) ................ 99
Instance #2: FEIP-21 configuration parameters group B (group 2) ................ 101
Instance #3: FEIP-21 configuration parameters group C (group 3) ................ 102
TCP/IP interface object, class F5h .......................................................... 103
Class attributes (Instance #0) ............................................................ 103
Instance attributes (Instance #1) ........................................................ 103
Attribute explanations ..................................................................... 104
Ethernet link object, class F6h .............................................................. 105
8 Table of contents

Connection object, class 05h ................................................................ 106

Class attributes ............................................................................. 106
Instance attributes ......................................................................... 107
Acknowledge handler object, class 2Bh ................................................... 108
Class attributes (Instance #0) ............................................................ 108
Instance attributes (Instance #1) ........................................................ 108

9 EtherNet/IP – Diagnostics
Contents of this chapter .......................................................................... 109
Fault and warning messages ................................................................... 109
LEDs ................................................................................................ 109

10 NONE – Start-up
Contents of this chapter .......................................................................... 111
Warnings ........................................................................................... 111
Drive configuration ................................................................................ 111
Connection configuration using NONE protocol .......................................... 111
FEIP-21 configuration parameters – group A (group 1) .............................. 112
Starting up fieldbus communication ............................................................ 116

11 NONE – Diagnostics
Contents of this chapter .......................................................................... 117
Fault and warning messages ................................................................... 117
LEDs ................................................................................................ 117

12 Technical data
Contents of this chapter .......................................................................... 119
Dimension drawing ............................................................................... 119
General data ....................................................................................... 120
Ethernet link ....................................................................................... 120
TCP and UDP service ports ..................................................................... 120

13 Appendix A - ABB IP configuration tool

Contents of this chapter .......................................................................... 123
Installation ......................................................................................... 123
Finding adapter modules in the network ...................................................... 123
Rewriting the IP configuration of adapter modules .......................................... 124

14 Appendix B - Module configuration backup

Contents of this chapter .......................................................................... 127
Compatibility ....................................................................................... 127
Settings for backup ............................................................................... 127
Configuration backup for all protocols in FEIP-21 ........................................ 127

Further information
 Safety instructions 9

1
Safety instructions

Contents of this chapter

The chapter contains the warning symbols used in this manual and the safety instructions
which you must obey when you install or connect an option module. If you ignore the safety
instructions, injury, death or damage can occur. Read this chapter before you start the
installation.

Use of warnings and notes

Warnings tell you about conditions which can cause injury or death, or damage to the
equipment. They also tell you how to avoid danger. Notes draw attention to a particular
condition or fact, or give information on a subject.
The manual uses these warning symbols:

WARNING!
Electricity warning tells about hazards from electricity which can cause injury or
death, or damage to the equipment.

WARNING!
General warning tells about conditions, other than those caused by electricity,
which can cause injury or death or damage to the equipment.

Safety in installation and maintenance

These instructions are for all who install or connect an option module to a unit and need to
open its front cover or door to do the work.
10 Safety instructions

WARNING!
Obey these instructions. If you ignore them, injury or death, or damage to the
equipment can occur.

• If you are not a qualified electrician, do not do installation or maintenance work.

• Disconnect the unit from all possible power sources. After you have disconnected the
unit, always wait for 5 minutes to let the intermediate circuit capacitors discharge before
you continue.
• Disconnect all dangerous voltages connected to other connectors or parts in reach. For
example, it is possible that 230 V AC is connected from outside to a relay output of the
unit.
• Always use a multimeter to make sure that there are no parts under voltage in reach.
The impedance of the multimeter must be at least 1 Mohm.
 Introduction to the manual 11

2
Introduction to the manual

Contents of this chapter

This chapter introduces this manual.

Applicability
This manual applies to the FEIP-21 fieldbus adapter module, revision A.

Compatibility
￭ Drives
The FEIP-21 fieldbus adapter module is compatible with:
• ACS880 primary control program version 2.51.0.0 and later
• ACS580 standard control program version 2.02.0.1 and later
• ACH580 HVAC control program 2.01.0.4 and later
• ACQ580 pump control program 2.03.0.3 and later
• ACS380 machinery control program version 2.02.0.1 and later
• ACS480 standard control program 2.02.0.3 and later

Note:
Not all compatible drives are listed here. For details of compatibility, check the drive's
firmware manual. You can check the current firmware version of the drive with parameter
07.05 Firmware version.

￭ Protocol
The FEIP-21 module is compatible with Ethernet standards IEEE 802.3 and IEE 802.3u
and it supports the EtherNet/IP protocol.
12 Introduction to the manual

All EtherNet/IP clients that support:

• The CIP Networks Library, Volume 1, Common Industrial Protocol (CIP), Edition 3.0
May, 2006
• The CIP Networks Library, Volume 2, EtherNet/IP Adaptation of CIP, Edition 1.2 May,
2006
• Recommended Functionality for EtherNet/IP Devices Version 1.2, Feb., 2006
are compatible with the EtherNet/IP module.

Target audience
This manual is intended for people who plan the installation, install, start up, use and service
the module. Before you do work on the module, read this manual and the applicable drive
manual that contains the hardware and safety information for the product in question.
You are expected to know the fundamentals of electricity, wiring, electrical components and
electrical schematic symbols.
This manual is written for readers worldwide. Both SI and imperial units are shown.

Purpose of the manual

The manual provides information on installing, commissioning and using the FEIP-21 adapter
module.

Cybersecurity disclaimer
This product is designed to be connected to and to communicate information and data via
a network interface. It is Customer's sole responsibility to provide and continuously ensure
a secure connection between the product and Customer network or any other network (as
the case may be). Customer shall establish and maintain any appropriate measures (such
as but not limited to the installation of firewalls, application of authentication measures,
encryption of data, installation of anti-virus programs, etc) to protect the product, the network,
its system and the interface against any kind of security breaches, unauthorized access,
interference, intrusion, leakage and/or theft of data or information. ABB and its affiliates are
not liable for damages and/or losses related to such security breaches, any unauthorized
access, interference, intrusion, leakage and/or theft of data or information.

Terms and abbreviations

Term Description
Control word 16-bit or 32-bit word from a controller to the controlled device with bit-coded control
signals (sometimes called the Command word).
DHCP Dynamic Host Control Protocol. A protocol for automating the configuration of IP
devices. DHCP can be used to automatically assign IP addresses and related network
information.
DLR Device Level Ring. DLR network is a single-fault tolerant ring network topology intended
for interconnection of automation devices.
Drive Frequency converter for controlling AC motors
EDS file Electronic Datasheet File identifies the properties of the device to the EtherNet/IP client.
Each type of drive and application program requires its own EDS file.
EMC Electromagnetic compatibility
FBA Fieldbus adapter
FEIP-21 Optional Ethernet adapter module
 Introduction to the manual 13

Term Description
MAC address Media Access Control address
ODVATM Open DeviceNet Vendor Association. ODVA is an independent organization the pro-
motes interoperability between different manufacturers' EtherNet/IP products. ABB is
an Associate Member at ODVA.
PLC Programmable logic controller
Profile Adaptation of a communication protocol for a certain application field (for example
drives)
Status word 16-bit or 32-bit word from a controlled device to the controller with bit-coded status
signals

Related manuals
Manual Code
Drive hardware manuals and guides
ACS380-04 manuals 9AAK10103A6193
ACS480 manuals 9AKK106930A8739
ACS580-01 manuals 9AKK105713A8085
ACH580-01 manuals 9AKK10103A0587
ACQ580-01 manuals 9AKK106713A2709
ACS580-04 manuals 9AKK106930A9060
ACH580-04 manuals 9AKK106930A9059
ACQ580-04 manuals 9AKK106930A9053
ACS580-07 manuals 9AKK106930A5239
ACH580-07 manuals 9AKK106930A5241
ACQ580-07 manuals 9AKK106930A3150
ACS880-01 manuals 9AKK105408A7004
ACS880-04 manuals 9AKK105713A4819
ACS880-07 (45 to 710 kW) manuals 9AKK105408A8149
ACS880-07 (560 to 2800 kW) manuals 9AKK105713A6663
ACS880-11 manuals 9AKK106930A9565
ACS880-14 manuals 9AKK107045A8023
ACS880-17 (45 to 400 kW) manuals 9AKK106930A3466
ACS880-17 (160 to 3200 kW) manuals 9AKK106354A1499
ACS880-31 manuals 9AKK106930A9564
ACS880-34 manuals 9AKK107045A8025
ACS880-37 (45 to 400 kW) manuals 9AKK106930A3467
ACS880-37 (160 to 3200 kW) manuals 9AKK106354A1500
Option manuals and guides
FEIP-21 EtherNet/IP fieldbus adapter module user’s manual 3AXD50000158621
FEIP-21 EtherNet/IP fieldbus adapter module quick installation and start-up 3AXD50000158584
guide

The links above contain lists of documents. You can find manuals and other product
documents in PDF format on the Internet. See ABB Document Library. For manuals not
available in the Document library, contact your local ABB representative.
14 Introduction to the manual

FEIP-21 EtherNet/IP fieldbus adapter module User's Fieldbus connectivity web page
manual
 Overview of the Ethernet network and the FEIP-21 module 15

3
Overview of the Ethernet network and
the FEIP-21 module

Contents of this chapter

This chapter contains a short description of the Ethernet network and the topology supported
by the FEIP-21 adapter module.

Ethernet network
Ethernet standards support a variety of physical media (coaxial cable, twisted pair, fiber
optics) and topologies (bus and star).
The FEIP-21 module supports twisted pair as the physical media. FEIP-21 supports star
topology, daisy chain topology and ring topology (Device Level Ring, DLR).
The maximum length for an Ethernet segment on twisted pair media is 100 meters. All
twisted pair media between the Ethernet node and the switch or router must be shorter than
100 meters, including media within patch panels.

￭ Example topology of the Ethernet link

The figures below show example topologies for an Ethernet network with FEIP-21.
16 Overview of the Ethernet network and the FEIP-21 module

Star topology

2
1 1

1 Other device

2 ABB drive

3 Switch or router

Daisy chain topology using integrated Ethernet switch

1 1 1
2

1 ABB drive

2 Other device

3 Network master device

 Overview of the Ethernet network and the FEIP-21 module 17

Ring topology
For DLR configuration, see Configuring DLR topology for FEIP-21 (page 48).

1 1 1
2

1 ABB drive

2 Other device

3 Network master device

FEIP-21 module overview

The FEIP-21 adapter module is a plug-in device for ABB drives which enables the connection
of the drive to an EtherNet/IP 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 a process actual value or a process reference to the PID controller of the drive
• read status information and actual values from the drive
• reset a drive fault
• read/write parameters of the drive
• connect Drive composer pro tool
The adapter module supports 10 Mbit/s and 100 Mbit/s data transfer rates and automatically
detects the data transfer rate used in the network.
The adapter module is installed into an option slot on the drive control unit. See the drive
manuals for module placement options.
18 Overview of the Ethernet network and the FEIP-21 module

￭ FEIP-21 layout

5
3 4
2

No. Description

1 Lock

2 Mounting screw (Grounding screw)

3 X1 connector to Ethernet

4 X2 connector for chaining another module

5 Diagnostic LEDs

6 MAC address
 Mechanical installation 19

4
Mechanical installation

Contents of this chapter

This chapter contains a delivery checklist and instructions on installing the module.
10
Necessary tools and instructions
You will need a Torx TX10 screwdriver to secure the FEIP-21 module to the drive. See also
the drive hardware manual.

Unpacking and examining the delivery

1. Open the option package.
2. Make sure that the package contains:
• fieldbus module, type FEIP-21
• quick guide
3. Make sure that there are no signs of damage.
 20 Mechanical installation

verters Installing the module

on and start-up guide WARNING!

Obey the safety instructions. If you ignore the safety instructions, injury or death

dapter module can occur.

The module is installed to a free option slot on the drive control unit. Plastic pins, a lock and
one screw hold the module in place. The screw also makes an electrical connection between
the module and drive frame for cable shield termination.
Note:
Do not install the FEIP-21 module on the FEA-03 F-series extension adapter.

Note:
instructions. If install
Do not you ignore them,
the FEIP-21 injury
when or death,
the drive or damage
is powered up. to the
he user’s manual.
When the module is installed, it makes the signal and power connection to the drive through
a 20-pin connector.
To install or remove the module from the control unit:
1. Pull out the lock.

n option
e drive
1
3

N·m using

ssive force,
. Over-
ew or 4
he EMC 2. Install the module carefully to an option module slot of the drive. See the drive hardware
manual.
n operation

No. Description
1 Lock
2 Mounting and grounding screw
3 RJ-45 connector [X1] to Ethernet
ou ignore them, injury or death, or damage to the

Mechanical installation 21

3. Push in the lock.

1
3

4. Tighten the screw to torque 0.8 N·m using a Torx TX10 screwdriver.

WARNING!
Do not use excessive force, or leave the screw too loose. Overtightening can
damage the screw or module. A loose screw decreases the EMC performance,
and can even cause an operation failure.
10
See the drive manual for further instructions on how to install the module to the drive.

o. Description
Lock
Mounting and grounding screw
RJ-45 connector [X1] to Ethernet
RJ-45 connector [X2] for chaining another module
Diagnostic LEDs
22
 Electrical installation 23

5
Electrical installation

Contents of this chapter

This chapter contains general cabling instructions and instructions on connecting the FEIP-21
module to the Ethernet network and the drive.

Necessary tools and instructions

See the drive hardware manual.
11

General cabling instructions

• Arrange the bus cables as far away from the motor cables as possible.
• Avoid parallel runs.
• Use bushings at cable entries.

Connecting the FEIP-21 to the Ethernet network

Choose correct cable for your application, CAT5e and CAT6 cables are recommended for
industrial applications. It is recommended to use shielded twisted pair cables, eg. "SF/FTP",
for use in industrial environments and with frequency converters.

WARNING!
Obey the safety instructions. If you ignore the safety instructions, injury or death
can occur. If you are not a qualified electrician, do not do electrical work.
24
 EtherNet/IP – Start-up 25

6
EtherNet/IP – Start-up

Contents of this chapter

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 client for communication with the adapter module

Warnings
WARNING!
Obey the safety instructions given in this manual and the drive documentation. 12

Drive configuration
The information in this section applies to all drive types compatible with the adapter module,
unless otherwise stated.

￭ EtherNet/IP connection configuration

After the adapter module has been mechanically and electrically installed according to the
instructions in chapters Mechanical installation and Electrical installation, you must prepare
the drive for communication with the module.
Normally, you must adjust a parameter to activate the communication. For detailed procedure
of activating the module for EtherNet/IP communication with the drive, see Starting up
fieldbus communication for the drive (page 34).
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
26 EtherNet/IP – Start-up

the tables below and must be checked first and adjusted where necessary. You can adjust
the parameters via a drive control panel or a PC tool.
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 gray
boxes in the tables.

Note:
The new parameter settings take effect only when you power up the module the next time
or when you activate the fieldbus adapter refresh parameter.

FEIP-21 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 ACS380, ACS480, ACH580, ACQ580 and ACS580
• parameter group 51/54 (or 151/154 in some variants) in ACS880 if the adapter is installed
as fieldbus adapter A/B.

No. Name/ Value Description Default

01 FBA type Read-only. Shows the fieldbus adapter type as detected by the drive. 2222 = Ether-
The value cannot be adjusted by the user. Net/IP
If the value is 0 = None, the communication between the drive and
the module has not been established.

02 Protocol/Profile Selects the application protocol and communication profile for the 101 = EIP ABB
network connection. Pro
The selections available for EtherNet/IP communication are listed
below.

100 = EIP EtherNet/IP protocol: ODVA AC/DC drive profile

AC/DC

101 = EIP ABB EtherNet/IP protocol: ABB Drives profile

Pro

102 = EIP T16 EtherNet/IP protocol: Transparent 16-bit profile

103 = EIP T32 EtherNet/IP protocol: Transparent 32-bit profile

03 Commrate Sets the bit rate for the Ethernet interface. In FEIP-21 this parameter 0 = Auto
is used for configuring port 1. For configuring port 2, see parameter
14 Commrate port 2 (page 28).

0 = Auto Autonegotiate

1 = 100 Mbps 100 Mbps, full duplex

FD

2 = 100 Mbps 100 Mbps, half duplex

HD

3 = 10 Mbps 10 Mbps, full duplex

FD

4 = 10 Mbps 10 Mbps, half duplex

HD
 EtherNet/IP – Start-up 27

No. Name/ Value Description Default

04 IP configura- Sets the method for configuring the IP address, subnet mask and 1 = Dyn IP DH-
tion gateway address for the adapter module. CP

0 = Static IP Configuration will be obtained from parameters 05…13.

1 = Dyn IP DH- Configuration will be obtained via DHCP.

CP

05 IP address 1 An IP address is assigned to each IP node on a network. An IP ad- 0

dress is a 32-bit number that is typically represented in “dotted
decimal” notation consisting of four decimal integers, on the range
0…255, separated by periods. Each integer represents the value of
one octet (8-bits) in the IP address. Parameters 05…08 define the
four octets of the IP address.

0 … 255 IP address

... ... ... ...

08 IP address 4 See parameter 05 IP address 1 (page 27). 0

0 … 255 IP address

09 Subnet CIDR Subnet masks are used for splitting networks into smaller networks 0
called subnets. A subnet mask is a 32-bit binary number that splits
the IP address into a network address and host address.
Subnet masks are typically represented in either dotted decimal
notation or the more compact CIDR notation, as shown in the table
below.

CIDR Dotted decimal CIDR Dotted decimal

31 255.255.255.254 15 255.254.0.0
30 255.255.255.252 14 255.252.0.0
29 255.255.255.248 13 255.248.0.0
28 255.255.255.240 12 255.240.0.0
27 255.255.255.224 11 255.224.0.0
26 255.255.255.192 10 255.192.0.0 12
25 255.255.255.128 9 255.128.0.0
24 255.255.255.0 8 255.0.0.0
23 255.255.254.0 7 254.0.0.0
22 255.255.252.0 6 252.0.0.0
21 255.255.248.0 5 248.0.0.0
20 255.255.240.0 4 240.0.0.0
19 255.255.224.0 3 224.0.0.0
18 255.255.192.0 2 192.0.0.0
17 255.255.128.0 1 128.0.0.0
16 255.255.0.0

1 ... 31 Subnet mask in CIDR notation

28 EtherNet/IP – Start-up

No. Name/ Value Description Default

10 GW address 1 IP gateways connect individual physical IP subnets into a unified IP 0

network. When an IP node needs to communicate with an IP node
on another subnet, the IP node sends the data to the IP gateway
for forwarding. Parameters 10…13 define the four octets of the
gateway address.

0 ... 255 GW address

... ... ... ...

13 GW address 4 See parameter 10 GW address 1 (page 28). 0

0 ... 255 GW address

14 Commrate port Sets the bit rate for the Ethernet port 2. This parameter is used only 0 = Auto
2 with FEIP-21.

0 = Auto Autonegotiate

1 = 100 Mbps 100 Mbps, full duplex

FD

2 = 100 Mbps 100 Mbps, half duplex

HD

3 = 10 Mbps 10 Mbps, full duplex

FD

4 = 10 Mbps 10 Mbps, half duplex

HD

15 Service config- Disable services that are not required.

uration Each service is represented by a single bit. Bit 0, Lock configuration,
can be used to prevent accidental changing of this parameter.
By default, all services are enabled and configuration is unlocked.

Bit Name Information

0 Lock configuration Changing of this parameter are no longer possible when this bit
is set. Only reset fieldbus configuration to default will unlock the
parameter.

1 Disable IP config tool When this bit is set, access from ABB IP Configuration tool is
prevented.

2 Disable ETH tool net- When this bit is set, access from Ethernet tool network (eg, ABB
work Drive Composer tool) is prevented.

3 Disable ping response When this bit is set, response to ICMP (ping) message is preven-
ted.

0000b…1111b Service configuration

16 ... Reserved These parameters are not used by the adapter module when the N/A
18 module is configured for EtherNet/IP.
 EtherNet/IP – Start-up 29

No. Name/ Value Description Default

19 T16 scale Defines the scaling for reference 1 and actual 1 with Transparent 99
16 profile. (Protocol.Profile = EIP T16)
Scaling also depends on the selected Reference type on 50.04 FBA
A Ref 1 type and 50.34 FBA B Ref 1 type and 50.07 and 50.37 for
the actual 1.
Ref type = Transparent
FBA_A/B_Ref1 = Ref1_from_PLC * (T16_Scale + 1)
Ref type = General
FBA_A/B_Ref1 = Ref1_from_PLC * (T16_Scale + 1) / 100

0 ... 65535 Reference multiplier/actual value divisor

20 Control timeout Defines the control timeout value. 0

The EtherNet/IP protocol specifies connection timeout for I/O mes-
saging (Class 1) and Connected explicit messaging (Class 3), but
not Unconnected explicit messaging.
This parameter provides a timeout for Unconnected explicit mes-
saging and for instances of Connected explicit messaging (Class
3), where the client breaks the connection in between requests.

Connection type Control timeout Timeout source

I/O messaging 0 … 65535 (Requested Packet Interval) X (Connection Timeout Multipli-
(Class 1) er)

Note:
Timeout behavior may be modified by Watchdog Timeout
Action attribute of Connection object.

Connected explicit 0 (Requested Packet Interval) X (Connection Timeout Multipli-

messaging (Class er)
3)
Note:
Timeout behavior may be modified by Watchdog Timeout
Action attribute of Connection object.

1 ... 65534 100ms X (Control Timeout Value) since last Control Event
65535 Never Timeout
12
Unconnected expli- 0 Always Timeout
cit messaging Control Timeout must be greater than zero to control drive
with Unconnected Explicit Messaging.
1 ... 65534 100ms X (Control Timeout Value) since last Control Event
65535 Never Timeout

Control timeout events:

• Write of an output assembly object instance
• Write of control bits (Run1, Run2, NetCtrl, NetRef and FaultReset)
• Write Speed Reference
• Write Torque Reference
• Reset Control Supervisor object
• Write Force Fault via Control Supervisor object
If a timeout occurs, the adapter module signals the drive that com-
munication with the client has been lost. The drive configuration then
determines how to respond.
Example: If the timeout is 250 ms and the drive is configured to fault
on a communication failure with a delay of 500 ms, then the drive
will fault 750 ms after communications is lost.
30 EtherNet/IP – Start-up

No. Name/ Value Description Default

0 ... 65535 Control timeout value

21 Idle action I/O connections may include a Run/Idle notification. This parameter 0 = Off-line
determines the action the drive takes in response to an Idle notifica-
tion.

0 = Off-line In the event of an Idle notification, the adapter module signals the
drive that communication with the client has been lost. The drive
configuration then determines how to respond.
Example: If the timeout is 250 ms and the drive is configured to fault
on a communication failure with a delay of 500 ms, then the drive
will fault 750 ms after communications is lost.
1 = On-line In the event of an Idle notification, the drive will continue to operate
using the last command and references received.

22 Stop function Determines how the motor is to be stopped when a stop command 0 = Ramp
is received via EtherNet/IP.
This parameter only applies to the ODVA AC/DC drive profile.

0 = Ramp The motor decelerates along the active deceleration ramp.

1 = Coast The motor comes to a stop by coasting.

23 Speed scale This parameter only applies to the ODVA AC/DC drive profile. The 128
units of reference and actual speeds for the ODVA AC/DC drive
profile are given by the formula below.
Speed unit = RPM × 2(-1 × ODVA speed scale value)

Note:
While a wide range of resolutions may be configured, the actual
performance is limited to the performance capabilities of the drive.
The table below shows the how the drive ODVA speed scale para-
meter values correspond to the ODVA speed scale units.

ODVA speed scale value 1) Speed scale value of drive Unit

parameter 2)
-5 123 32 RPM
-4 124 16 RPM
-3 125 8 RPM
-2 126 4 RPM
-1 127 2 RPM
0 (default) 128 1 RPM
1 129 0.5 RPM
2 130 0.25 RPM
3 131 0.125 RPM
4 132 0.0625 RPM
5 133 0.03125 RPM

1) Use the ODVA speed scale value when reading/writing parameter 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 Speed scale via
the drive control panel, Drive parameter object, class 90h and Fieldbus configuration object, class
91h. When written via these methods, the new value takes effect after the drive is repowered or a
“Fieldbus Adapter Parameter refresh” is given.
 EtherNet/IP – Start-up 31

No. Name/ Value Description Default

0 ... 255 Speed scale value of drive parameter

24 Torque scale This parameter only applies to the ODVA AC/DC drive profile. The 128
units of reference and actual torques for the ODVA AC/DC drive
profile are given by the formula below.
Torque unit = N·m × 2(-1 × ODVA torque scale)
where:
(N·m = Newton × Meter)

Note:
While a wide range of resolutions may be configured, the actual
performance is limited to the performance capabilities of the drive.
The table below shows how the drive ODVA torque scale parameter
values correspond to the ODVA torque scale units.

ODVA torque scale value 1) Torque scale value of drive Unit

parameter 2)
-5 123 32 RPM
-4 124 16 RPM
-3 125 8 RPM
-2 126 4 RPM
-1 127 2 RPM
0 (default) 128 1 RPM
1 129 0.5 RPM
2 130 0.25 RPM
3 131 0.125 RPM
4 132 0.0625 RPM
5 133 0.03125 RPM

1) Use the ODVA torque scale value when reading/writing parameter 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 Torque scale
via the drive control panel, Drive parameter object, class 90h and Fieldbus configuration object, 12
class 91h. When written via these methods, the new value takes effect after the drive is repowered
or a “Fieldbus Adapter Parameter refresh” is given.

0 ... 255 Torque scale value of drive parameter

25 ... Reserved
26

27 FBA A/B par Validates any changed adapter module configuration parameter 0 = Done
refresh settings. After refreshing, the value reverts automatically to 0 = Done.

Note:
This parameter cannot be changed while the drive is running.

0 = Done Refreshing done

1 = Refresh Refreshing
32 EtherNet/IP – Start-up

No. Name/ Value Description Default

28 FBA A/B par Read-only. Displays the parameter table revision of the fieldbus N/A
table ver 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
OR
in format axyz, where
a = major revision number
xy = minor revision numbers
z = correction number or letter.

Parameter table revision

29 FBA A/B drive Read-only. Displays the drive type code of the fieldbus adapter N/A
type code module mapping file stored in the memory of the drive.

Drive type code of the fieldbus adapter module mapping file

30 FBA A/B map- Read-only. Displays the fieldbus adapter module mapping file revi- N/A
ping file ver sion stored in the memory of the drive in decimal format.

Mapping file revision

31 D2FBA A/B Read-only. Displays the status of the fieldbus adapter module 0 = Idle
comm status communication. or
Note: 4 = Offline
The value names may vary by drive.

0 = Idle Adapter is not configured.

1 = Exec.init Adapter is initializing.

2 = Time out A timeout has occurred in the communication between the adapter
and the drive.

3 = Conf.err Adapter configuration error: The 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 Adapter is off-line.

5 = On-line Adapter is on-line.

6 = Reset Adapter is performing a hardware reset.

32 FBA A/B comm Read-only. Displays firmware patch and build number of the adapter N/A
SW ver module in the xxyy format, where:
xx = patch number
yy = build number
Example: If the firmware version (<major>.<minor>.<patch>.<build>)
is 3.10.200.13, the value C80D is displayed. If the version is 3.10.0.0,
the value 0 is displayed.
See also parameter 33 FBA A/B appl SW ver (page 33).
 EtherNet/IP – Start-up 33

No. Name/ Value Description Default

33 FBA A/B appl Read-only. Displays firmware version of the adapter module in xxyy N/A
SW ver format, where:
xx = major revision number
yy = minor revision number
Example: If the firmware version (<major>.<minor>.<patch>.<build>)
is 3.10.200.13 or 3.10.0.0, the value 310 is displayed.
See also parameter 32 FBA A/B comm SW ver (page 32).

FEIP-21 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 53 in ACS380, ACS480, ACH580, ACQ580 and ACS580
• parameter group is typically 53/56 (153/156 in some variants) in ACS880 if the adapter
is installed as fieldbus adapter A/B.

No. 1) Name/ Value Description Default

01 FBA A/B data In output assembly instances that include drive parameters, this 0 = None
out 1 (client to parameter specifies which parameter’s value will be placed in loca-
drive) tion Data out 1 value received by the drive from the EtherNet/IP cli-
ent.
The content is defined by a decimal number in the range of 0 to
9999 as follows:

0 Not used

1 ... 99 Virtual address area of drive control. Not used

when the EtherNet/IP protocol is used.

101 ... 9999 Parameter area of the drive

0 = None Not used 12

101 … 9999 Parameter index with format xxyy, where
• xx is the parameter group number (1…99)
• yy is the parameter number index within that group (01…99).
Note:
In ACS480, ACS580 and ACS880, choose Other to display a list of
mappable drive parameters.

02 ... Data out 2 ... See parameter 01 FBA A/B data out 1 (client to drive) (page 33). 0 = None
10 Data out 10

1) The number of parameters in this group may vary by drive type and drive firmware.
34 EtherNet/IP – Start-up

FEIP-21 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 52 in ACS380, ACS480, ACH580, ACQ580 and ACS580
• parameter group is typically 52/55 (152/155 in some variants) in ACS880 and
ACS880-M04 if the adapter is installed as fieldbus adapter A/B.

No. 1) Name/ Value Description Default

01 FBA A/B data In input assembly instances that include drive parameters, this 0 = None
in1 (drive to cli- parameter specifies which parameter’s value will be placed in loca-
ent) tion Data in 1 value sent by the drive to the EtherNet/IP client.
The content is defined by a decimal number in the range of 0 to
9999 as follows:

0 Not used

1 ... 99 Virtual address area of drive control. Not used

when the EtherNet/IP protocol is used.

101 ... 9999 Parameter area of the drive

0 = None Not used

101 … 9999 Parameter index with format xxyy, where

• xx is the parameter group number (1…99)
• yy is the parameter number index within that group (01…99).
Note:
In ACS480, ACS580 and ACS880, choose Other to display a list of
mappable drive parameters.

02 … Data in 2 … See parameter 01 FBA A/B data in1 (drive to client) (page 34). 0 = None
10 Data in 10

1) The number of parameters in this group may vary by drive type and drive firmware.

￭ Control locations
ABB drives can receive control information from multiple sources including digital inputs,
analog inputs, the drive control panel and a fieldbus adapter module. ABB drives allow the
user to separately determine the source for each type of control information (Start, Stop,
Direction, Reference, Fault reset, etc.).
To give the fieldbus client the most complete control over the drive, you must select the
adapter module as the source of this information. The drive-specific parameter setting
examples below contain the drive control parameters relevant in the examples. For a
complete parameter list, see the drive documentation.

Starting up fieldbus communication for the drive

1. Power up the drive.
2. Enable the communication between the adapter module and the drive by selecting the
correct slot number in parameter 50.01 FBA A enable.
 EtherNet/IP – Start-up 35

The selection must correspond to the slot where the adapter module is installed. For
example, if the adapter module is installed in slot 2, you must select slot 2.
3. With parameter 50.02 FBA A comm loss func, select how the drive reacts to a fieldbus
communication break.
Note that this function monitors both communication between the fieldbus master and
the adapter module and communication between the adapter module and the drive.
4. With parameter 50.03 FBA A comm loss t out, define the time between communication
break detection and the selected action.
5. Select application-specific values for the rest of the parameters in group 50, starting
from 50.04.
Examples of appropriate values are shown in the tables below.
6. Set the module configuration parameters in group 51.
At the minimum, select the communication protocol and profile with parameter 51.02
and configure the network settings with parameters 51.03…51.13.
7. Define the process data transferred to and from the drive in parameter groups 52 and
53.
Note:
The adapter module assigns the Control word, Status word, references 1…2 and actual
values 1…2 automatically to cyclical communication according to the selected assembly
instances.

8. Save the valid parameter values to permanent memory with parameter 96.07 Parameter
save manually.
9. Validate the settings made in parameter groups 51, 52 and 53 with parameter 51.27
FBA A par refresh.
10. 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 – ACS380, ACS480, ACS580 and ACS880

Speed control using the ODVA AC/DC drive profile, Extended speed control assembly
This example shows how to configure a speed control application that uses the ODVA
12
AC/DC drive profile, Extended speed control assembly. In addition, some application-specific
data is added to the communication.
The start/stop commands and reference scaling are according to the ODVA AC/DC drive
profile. For more information, see section ODVA AC/DC drive profile (page 54).
When Reference 1 (REF1) is used for speed control and the value of parameter 51.23 is
128, an ODVA speed reference value of ±30000 (decimal) corresponds to an equal amount
of rpm in the drive. The speed reference value sent from the PLC is limited by parameter
30.12 Maximum speed in the forward direction and 30.11 Minimum speed in the reverse
direction.
The minimum and maximum 16-bit integer values that can be given through the fieldbus
are -32768 and 32767 respectively.

Bytes Instance 121 Instance 171

0...1 Control word Status word

2...3 Speed reference Speed actual value

4...7 Constant speed 1 [32] 1) Output power [32]1

36 EtherNet/IP – Start-up

Bytes Instance 121 Instance 171

8...11 Constant speed [32]1 DC voltage [32]1

1) Example

The table below gives the recommended drive parameter settings.

Drive parameter Setting for drives Description

50.01 FBA A enable 1 = Option slot 1 1) Enables communication between the

drive and the fieldbus adapter module.

50.02 FBA A comm loss func 1 = Fault1 Enables fieldbus A communication fault
monitoring.

50.03 FBA A comm loss t out 3.0 s1 Defines the fieldbus A communication
break supervision time.

50.04 FBA A ref1 type 4 = Speed Selects the fieldbus A reference 1 type
and scaling.

51.01 FBA A type 2222 = EtherNet/IP 2) Displays the type of the fieldbus adapter
module.

51.02 Protocol/Profile 100 = EIP AC/DC Selects the EtherNet/IP protocol and the
ODVA AC/DC drive profile.

51.03 Commrate 0 = Auto1 Ethernet communication rate is negoti-

ated automatically by the device.

51.04 IP configuration 0 = Static IP1 Configuration will be obtained from

parameters 05...13.

51.05 IP address 1 1921 First part of the IP address

51.06 IP address 2 1681 Second part of the IP address

51.07 IP address 3 01 Third part of the IP address

51.08 IP address 4 161 Last part of the IP address

51.09 Subnet CIDR 241 Sets the network mask as

255.255.255.0, allowing access only to
the last subnet.

51.23 ODVA speed scale 1281 Sets the scaling for the ODVA speed
reference.

52.01 FBA data in1 01.141 Output power

52.03 FBA data in3 01.111 DC voltage

53.01 FBA data out1 22.261 Constant speed 1

53.03 FBA data out3 22.271 Constant speed 2

51.27 FBA A par refresh 1 = Refresh Validates the FEIP-21 configuration

parameter settings.

20.01 Ext1 commands 12 = Fieldbus A Selects the fieldbus A interface as the

source of the start and stop commands
for external control location 1.
 EtherNet/IP – Start-up 37

Drive parameter Setting for drives Description

22.11 Speed ref1 source 4 = FB A ref1 Selects the fieldbus A reference 1 as the
source for speed reference 1.

1) Example
2) Read-only or automatically detected/set

The start sequence for the parameter example above is given below.
Control word:
• Reset the fieldbus communication fault (if active).
• Enter 0h (0 decimal) → READY.
• Enter 1h (1 decimal) → ENABLED (Running forward).
• Enter 2h (2 decimal) → ENABLED (Running reverse).

Configuring the client

After the adapter module has been initialized by the drive, you must prepare the client for
communication with the module. An example of an Allen-Bradley® PLC is given below. If
you are using another client system, refer to its documentation for more information.
The example applies to all drive types compatible with the module.

￭ Before you start

Decide on these points before you start the client configuration.

Select profile
The communication profile determines which I/O assemblies and objects are available. See
chapter EtherNet/IP – Communication profiles (page 53) for more information.

Select output and input assembly instances

EtherNet/IP devices implement multiple objects each with many attributes. While it is possible
to write or read each attribute separately to control the drive, this is inefficient. Assembly
object instances provide a means to group writes or reads of attributes. The selection of
assembly objects is limited by the choice of the communication profile. This table gives a12
listing of the output and input assemblies.

Name Output in- Input instance Size Size (16- Profile

stance (bytes) bit
words)

Basic Speed Control 20 70 4 2 ODVA AC/DC drive

Enhanced Speed Control 21 71 4 2 ODVA AC/DC drive

Basic Speed and Torque Control 22 72 6 3 ODVA AC/DC drive

Enhanced Speed and Torque 23 73 6 3 ODVA AC/DC drive

Control

Basic Speed Control plus Drive 120 170 24 12 ODVA AC/DC drive
Parameters

Enhanced Speed Control plus 121 171 24 12 ODVA AC/DC drive

Drive Parameters
38 EtherNet/IP – Start-up

Name Output in- Input instance Size Size (16- Profile

stance (bytes) bit
words)

Basic Speed and Torque Control 122 172 26 13 ODVA AC/DC drive
plus Drive Parameters

Enhanced Speed and Torque 123 173 26 13 ODVA AC/DC drive

Control plus Drive Parameters

ABB Drives Profile w/ Set Speed 1 51 4 2 ABB Drives profile

ABB Drives Profile w/ Set Speed 2 52 6 3 ABB Drives profile

and Set Torque

ABB Drives Profile w/ Set Speed 101 151 24 12 ABB Drives profile
plus Drive Parameters

ABB Drives Profile w/ Set Speed 102 152 26 13 ABB Drives profile
and Set Torque plus Drive
Parameters

Transparent16 w/One 11 61 4 2 Transparent16 pro-

file

Transparent16 w/Two 12 62 6 3 Transparent16 pro-

file

Transparent16 w/One plus Drive 111 161 24 12 Transparent16 pro-

Parameters file

Transparent16 w/Two plus Drive 112 162 26 13 Transparent16 pro-

Parameters file

Transparent32 w/One 21 71 8 4 Transparent32 pro-

file

Transparent32 w/Two 22 72 12 6 Transparent32 pro-

file

Transparent32 w/One plus Drive 121 171 28 14 Transparent32 pro-

Parameters file

Transparent32 w/Two plus Drive 122 172 32 16 Transparent32 pro-

Parameters file

Select connection method

EtherNet/IP provides a variety of connection methods to communicate between devices.
Not all methods are supported by all devices. Refer to the client documentation to determine
which method(s) are supported by the client.
Note:
The choice of the connection method has a significant impact on the timeout behavior. Refer
to configuration parameters 20 Control timeout and 21 Idle action for more information.

The FEIP-21 adapter module supports the following connection methods:

I/O connections
The adapter module supports Class 1 I/O connections. I/O connections are often also
referred to as “Implicit Messaging”. I/O connections are typically established by configuring
an I/O scanner to write and read assembly object instances.
Connected explicit messaging
 EtherNet/IP – Start-up 39

The adapter module supports Class 3 connected explicit messaging. Class 3 connected
explicit messages are typically established by using a “message instruction” to write or read
an attribute.
Note:
When using Class 3 explicit messaging, some EtherNet/IP clients may close the connection
after the MSG instruction is done. This will cause the module to behave as if it were controlled
via unconnected explicit messaging.

Unconnected explicit messaging

The adapter module supports unconnected explicit messaging. Unconnected explicit
messages are typically established by using a “message instruction” to write or read an
attribute.
Note:
EtherNet/IP does not provide a timeout means for unconnected explicit messaging. To use
unconnected explicit messaging for control, refer to configuration parameter 20 Control
timeout (page 29).

￭ EDS files
Electronic Data Sheet (EDS) files specify the properties of the device for the EtherNet/IP
client. The client identifies the device by means of the product code, device type and major
revision attributes.
To enable the use of different ABB drive types on the same EtherNet/IP network, a unique
product code has been given to each drive type and application combination.
EDS files are available from the Document library (http://new.abb.com/drives/ethernet-ip).
Note:
Only one EDS file with the same EtherNet/IP product code can be installed in the PLC at a
time.

￭ Configuring an Allen-Bradley® PLC

Example 1: RSLogix 5000
12
This example shows how to prepare an Allen-Bradley® Control-Logix5555™ PLC for
communication with the adapter module by using the RSLogix 5000® software as the
configuration tool.
1. Start the RSLogix software and open/create an RSLogix project.
Note:
It is assumed that the PLC configuration has already been established in the RSLogix
project.
40 EtherNet/IP – Start-up

2. In the RSLogix I/O, right-click the EtherNet/IP communication module and select New
Module.

3. In the Select Module window, select ETHERNET-MODULE.

 EtherNet/IP – Start-up 41

4. Select the input and output assembly instances and the PLC I/O memory size to be
used.
The table below shows the available combinations. The example below uses the ODVA
AC/DC assembly instances 121 and 171.

Input assembly instances Output assembly instances PLC word settings

70 20 2

71 21 2

72 22 3

73 23 3 12
170 120 12

171 121 12

172 122 13

173 123 13

51 1 2

52 2 3

151 101 12

152 102 13

61 11 2

62 12 3

161 111 12
42 EtherNet/IP – Start-up

Input assembly instances Output assembly instances PLC word settings

162 112 13

For more information on the input/output assembly instances, see section Select output
and input assembly instances (page 37).
5. Enter the following information.
The example below uses ODVA AC/DC assembly instances 121 and 171. The PLC will
transmit and receive 12 words.

1
4 5

2
6

• Type a name for the adapter module. (1)

• FEIP uses 16-bit words. Change Comm Format to Data - INT (16 bits). (2)
• Type the IP address of the adapter module. (3)
• Type the Input and Output Assembly Instance numbers. (4)
• Select the sizes of the Input and Output words for the adapter module. (5)
• Set Configuration as 1 and Size as 0. (6)
6. Click OK.
The adapter module is now added to the PLC I/O.
7. Click the FEIP-21 module to open the Module Properties window.
8. On the Connection tab, select the Requested Packet Interval (RPI) for the adapter
module I/O communication.
 EtherNet/IP – Start-up 43

9. Download the new configuration to the PLC.

The PLC is now ready for communication with the adapter module.

Example 2: Studio 5000

This example shows how to prepare an Allen-Bradley® CompactLogix™ PLC for
communication with the adapter module using the Studio 5000® software as the configuration
tool.
1. Start the RSLogix software and open/create an RSLogix project.
Note:
It is assumed that the PLC configuration was already established in the Studio 5000®
project.

2. If EDS file for the correct device is not installed, use the EDS hardware installation tool.
12
To register a new EDS file:
• Select Tools → EDS Hardware Installation Tool.

• Select the option Register an EDS file(s). Click Next.

44 EtherNet/IP – Start-up

• Browse to FEIP-21 EDS file and select the file. Click Next to register the EDS file.

• Click Next and Finish to finalize registration. After the EDS file is successfully
registered the device can be used in the PLC project.
 EtherNet/IP – Start-up 45

3. Add new devices to EtherNet/IP bus by right-clicking Ethernet under I/O Configuration
and selecting New Module.

4. In the Select Module Type window, select ACS880 module (AC Drive Device). You can
easily find the ABB devices using filters. Click Create to add a new module.

12

5. Enter the following information to configure the IP address and module name.
46 EtherNet/IP – Start-up

• Type a name for the adapter module. (1)

• Type the IP address of the adapter module. (2)
6. Click Change, to select the input and output assembly instances and the PLC I/O memory
size to be used. The table below shows the available combinations.

Input assembly instances Output assembly instances PLC word setting

70 20 2

71 21 2

72 22 3

73 23 3

170 120 12

171 121 12

172 122 13

173 123 13

51 1 2

52 2 3

151 101 12

152 102 13

61 11 2

62 12 3
 EtherNet/IP – Start-up 47

Input assembly instances Output assembly instances PLC word setting

161 111 12

162 112 13

For more information on the input/output assembly instances, see section Select output
and input assembly instances (page 37).
FEIP-21 uses 16-bit words. Change the size to INT (16 bits). The example below uses
ODVA AC/DC assembly instances 121 and 171. The PLC transmits and receives 12
words.

12
7. Click OK and confirm selection to change the module data types.

8. On the Connection tab, select the Requested Packet Interval (RPI) for the adapter
module I/O communication.
48 EtherNet/IP – Start-up

9. Click OK. The adapter module is now added to the PLC I/O. You can add more modules
by choosing Create or exit the window by choosing Close.
10. Download the new configuration to the PLC. The PLC is now ready for communication
with the adapter module.

￭ Configuring DLR topology for FEIP-21

This example shows how to prepare an Allen-Bradley® CompactLogix™ PLC for DLR
topology with FEIP-21 adapter modules. After installing the devices on the DLR network,
at least one supervisor node must be configured. Configuration can be done by using the
Studio 5000® Logix Designer or RSLinx® Classic Lite software.
Note:
The examples below uses ACSxxx drive. You can also use this configuration with other
drives that supports FEIP-21.

Setup using Logix Designer

1. Open the Studio 5000® software. Test setup uses an Allen Bradley PLC connected in
a ring topology with two FEIP-21 fieldbus Ethernet modules. The topology used in the
example is shown below. More devices can be added, but the recommended maximum
number of nodes on a single DLR network is 50.

PC Studio 5000 ACSxxx ACSxxx

FEIP-21 FEIP-21
USB port
...
X1 X2 X1 X2
PLC
CompactLogix L24ER
USB port ...
Port 1

Port 2

Note:
It is assumed that the PLC configuration was already established in the Studio 5000®
project and the EDS file(s) are installed and at least two FEIP-21 modules are added
to the project.
 EtherNet/IP – Start-up 49

For more information on adding modules to a project and installing EDS files, see chapter
Configuring an Allen-Bradley® PLC (page 39).

2. Download the project to the PLC.

3. Go online with the PLC and leave it in Program mode.
4. Double-click the module in the I/O Configuration. In the Controller Properties window,
open Network tab and select Enable Supervisor Mode. Click OK.

12
50 EtherNet/IP – Start-up

Setup using RSLinx® Classic

You can configure and enable DLR supervisor via RSLinx®Classic.
1. Open the RSLinx®Classic software.
2. Browse to the DLR network.

3. Open the Module Configuration by right-clicking on the ring supervisor in the list.

4. On the Network tab, select Enable Ring Supervisor, to enable DLR messages in the
ring.
 EtherNet/IP – Start-up 51

5. Click Advanced... to configure DLR parameters, such as Beacon Interval and Beacon
Timeout.
Note:
It is recommended to use the default values.

6. Go back to Logix Designer and make sure that none of the FEIP-21 modules are faulted,
that is no warning symbols are displayed.

12
52
 EtherNet/IP – Communication profiles 53

7
EtherNet/IP – Communication profiles

Contents of this chapter

This chapter describes the communication profiles used in the communication between the
EtherNet/IP client, 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 FEIP-21 adapter module, the EtherNet/IP 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.
The figure below illustrates the profile selection:
54 EtherNet/IP – Communication profiles

EtherNet/IP FEIP Drive

network
Profile selection:

Native
ODVA AC/DC ODVA AC/DC profile (eg,
profile Data DCU, FBA)
conversion
Native
ABB Drives profile (eg,
ABB Drives profile Data DCU, FBA)
conversion

Drive-specific Transparent16
profile1
Optional
(with 16-bit words) reference/actual
value scaling
Drive-specific
profile1 Transparent32
(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.

ODVA AC/DC drive profile

This section briefly describes the ODVA AC/DC drive profile. Additional information is
available at www.odva.org.
An EtherNet/IP node is modeled 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 AC and DC drives. The objects
supported by the adapter module are listed in section Class objects (page 92).
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 EtherNet/IP client to
set or get predefined groups of attributes in a single message exchange. The assembly
 EtherNet/IP – Communication profiles 55

instances supported by the adapter module are listed and defined in section Assembly
objects (page 65).

￭ 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.
In the ODVA EtherNet/IP specification the word output is used to describe data flow from
the network into a device (such as the adapter module).

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 sectionState (Control
supervisor object) (page 57).

RunFwd (Run1) RunRev (Run2) Trigger event Run type

0 0 Stop N/A

0→1 0 Run RunFwd

0 0→1 Run RunRev

0→1 0→1 No action N/A

1 1 No action N/A

0→1 1 Run RunRev

1 1→0 Run RunFwd

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 be 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 be 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 parameter 23 Speed scale (page 30) for details.
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
56 EtherNet/IP – Communication profiles

where
Dfr = Drive Frequency Reference in Hz
Osr = ODVA Speed Reference
Us = ODVA Speed Unit (see parameter 23 Speed scale (page 30))
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 parameter 23 Speed scale (page 30)).
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 parameter 24 Torque scale (page 31) 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 24 Torque scale on page 128)
Mt = Motor Nominal Torque in N·m.
For example, for a 1000 N·m Motor Nominal Torque with a unit of 1 N·m and an ODVA
Torque Reference of 500, the drive torque reference is:
 EtherNet/IP – Communication profiles 57

100 × Otr × Ut 100 × 500 × 1 Nm

Dtr = = = 50
Mt 1000 Nm

￭ ODVA input attributes

This section briefly describes the instances found in the ODVA AC/DC drive profile’s input
assemblies. Note that all input assembly instances do not support all attributes listed here.
In the ODVA EtherNet/IP specification the word input is used to describe data flow from a
device (such as the adapter module) to the network.

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) (page 57).

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).

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 State Description

0 Vendor-specific 4 Enabled

1 Startup 5 Stopping

2 Not ready 6 Fault stop

3 Ready 7 Faulted

The ODVA state transition diagram is shown below:

58 EtherNet/IP – Communication profiles

ALM = Alarm
DEC = Deceleration
Non Existent FWD = Forward
Power off REV = Reverse
RDY = Ready
Power on
Startup ALM=1 Faulted

Power on
Not Ready FaultRst
DEC=0
ALM=1
Power-on Fault stop
AND RDY Power-on AND not RDY
Ready
DEC=0

FWD OR REV FWD OR REV Stopping ALM=1

Enabled DEC=1

ALM=1

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 parameter 23 Speed
scale (page 30) 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 parameter 23 Speed scale (page 30))
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:
 EtherNet/IP – Communication profiles 59

Dfa × Mss 30Hz × 1800rpm

Osa = = = 900
Mf × Us 60Hz × 1rpm

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 parameter 23 Speed scale (page 30)).
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 parameter 24 Torque
scale (page 31) 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
Ota =
100 × Ut

where
Dta = Drive Torque Actual in Percent of Motor Nominal Torque
Ota = ODVA Torque Actual
Ut = ODVA Torque Unit (see parameter 24 Torque scale (page 31))
Mt = Motor Nominal Torque in N·m.
For example, for a 1000 N·m Motor Nominal Torque with a unit of 1 N·m and a drive torque
actual of 50%, the ODVA Torque Actual is:

Dta × Mt 50 × 1000Nm
Ota = = = 500
100 × Ut 100 × 1Nm
60 EtherNet/IP – Communication profiles

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 client 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 client in the Status word.
The contents of the Control word and the Status word are detailed below. The drive states
are presented in section State machine (page 62).

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 section State
machine (page 62).

Bit Name Value STATE/Description

0 OFF1_CONTROL 1 Proceed to READY TO OPERATE.

0 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 Continue operation (OFF2 inactive).

0 Emergency OFF, coast to stop. Proceed to OFF2 ACTIVE, proceed to

SWITCH-ON INHIBITED.

2 OFF3_CONTROL 1 Continue operation (OFF3 inactive).

0 Emergency stop, stop within time defined by drive parameter. Proceed

to OFF3 ACTIVE; proceed to SWITCH-ON INHIBITED.

WARNING!
Ensure that motor and driven machine can be stopped using
this stop mode.

3 INHIBIT_OPERA- 1 Proceed to OPERATION ENABLED.

TION
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 Inhibit operation. Proceed to OPERATION INHIBITED.

4 RAMP_OUT_ZERO 1 Normal operation. Proceed to RAMP FUNCTION GENERATOR: OUT-

PUT ENABLED.

0 Force Ramp Function Generator output to zero. Drive ramps to stop

(current and DC voltage limits in force).

5 RAMP_HOLD 1 Enable ramp function. Proceed to RAMP FUNCTION GENERATOR:

ACCELERATOR ENABLED.

0 Halt ramping (Ramp Function Generator output held).

 EtherNet/IP – Communication profiles 61

Bit Name Value STATE/Description

6 RAMP_IN_ZERO 1 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 Ramp Function Generator input to zero.

7 RESET 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 ... Drive-specific (For information, see the drive documentation.)

9

10 REMOTE_CMD 1 Fieldbus control enabled.

0 Control word and reference not getting through to the drive, except for
CW bits OFF1, OFF2 and OFF3.

11 EXT_CTRL_LOC 1 Select External Control Location EXT2. Effective if control location

parameterized to be selected from fieldbus.

0 Select External Control Location EXT1. Effective if control location

parameterized to be selected from fieldbus.

12 ... Reserved
15

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 section State
machine (page 62).

Bit Name Value STATE/Description

0 RDY_ON 1 READY TO SWITCH ON

0 NOT READY TO SWITCH ON

1 RDY_RUN 1 READY TO OPERATE

0 OFF1 ACTIVE

2 RDY_REF 1 OPERATION ENABLED

0 OPERATION INHIBITED

3 TRIPPED 1 FAULT

0 No fault

4 OFF_2_STA 1 OFF2 inactive

0 OFF2 ACTIVE
62 EtherNet/IP – Communication profiles

Bit Name Value STATE/Description

5 OFF_3_STA 1 OFF3 inactive

0 OFF3 ACTIVE

6 SWC_ON_INHIB 1 SWITCH-ON INHIBITED

0 –

7 ALARM 1 Warning/Alarm

0 No warning/alarm

8 AT_SETPOINT 1 OPERATION. Actual value equals reference (= is within tolerance limits,

ie, in speed control, speed error is 10% max. of nominal motor speed).

0 Actual value differs from reference (= is outside tolerance limits).

9 REMOTE 1 Drive control location: REMOTE (EXT1 or EXT2)

0 Drive control location: LOCAL

10 ABOVE_LIMIT 1 Actual frequency or speed equals or exceeds supervision limit (set by

drive parameter). Valid in both directions of rotation.

0 Actual frequency or speed within supervision limit

11 EXT_CTRL_LOC 1 External Control Location EXT2 selected.

Note:
For 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.33).

0 External Control Location EXT1 selected

12 EXT_RUN_ENABLE 1 External Run Enable signal received.

Note:
For 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.34)

0 No External Run Enable signal received

13 ... Reserved
14

15 FBA_ERROR 1 Communication error detected by fieldbus adapter module

0 Fieldbus adapter communication OK

State machine
The state machine for the ABB Drives communication profile is shown below.
 EtherNet/IP – Communication profiles 63

SWITCH-ON
MAINS OFF INHIBITED (SW Bit6=1)
ABB Drives
communication
Power ON (CW Bit0=0)
profile
NOT READY TO
A B C D SWITCH ON (SW Bit0=0) CW = Control word
SW = Status word
n = Speed
(CW=xxxx x1xx xxxx x110 ) I = Input current
(CW Bit3=0) RFG = Ramp function
generator
READY TO f = Frequency
OPERATION SWITCH ON (SW Bit0=1)
INHIBITED (SW Bit2=0)
from any state
operation (CW=xxxx x1xx xxxx x111 )
inhibited Fault

READY TO FAULT
from any state OPERATE (SW Bit1=1) (SW Bit3=1)

OFF1 (CW Bit0=0) (CW Bit7=1)

(CW=xxxx x1xx xxxx 1111
OFF1 and SW Bit12=1)
ACTIVE (SW Bit1=0)
from any state from any state
n(f)=0 / I=0 Emergency stop Emergency OFF
(CW Bit3=1 OFF3 (CW Bit2=0) OFF2 (CW Bit1=0)
and
SW Bit12=1) OFF3 OFF2
B C D ACTIVE (SW Bit5=0) ACTIVE (SW Bit4=0)

(CW Bit4=0) n(f)=0 / I=0

C D OPERATION
ENABLED (SW Bit2=1)
A
(CW Bit5=0) (CW=xxxx x1xx xxx1 1111 )

D RFG: OUTPUT
ENABLED
B
(CW Bit6=0) (CW=xxxx x1xx xx11 1111 )

RFG: ACCELERATOR state

ENABLED
C
(CW=xxxx x1xx x111 1111 ) condition

rising edge
OPERATION
(SW Bit8=1) of the bit
D

￭ References
References are 16-bit words containing a sign bit and a 15-bit integer. A negative reference
(indicating reversed direction of rotation) is formed by calculating the two’s complement
from the corresponding positive reference.
ABB drives can receive control information from multiple sources including analog and digital
inputs, the drive control panel and a fieldbus adapter module (for example, FEIP-21). To
have the drive controlled through the fieldbus, you must select the module 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
manuals for further information.
64 EtherNet/IP – Communication profiles

In ACS380, ACS480, ACH580, ACQ580, ACS580 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).

Fieldbus Drive

REF2: 10000 REFx MAX /

REF1: 20000 Speed scale

0
{ REFx MIN
-(REFx MIN)

REF2: -10000 -(REFx MAX) /

REF1: -20000 Speed scale

￭ Actual values
Actual values are 16-bit words containing information on the operation of the drive. 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
manuals for further information.

Fieldbus Drive

ACT2: 10000 REFx MAX /

ACT1: 20000 Speed scale

0 0

ACT2: -10000 -(REFx MAX) /

ACT1: -20000 Speed scale
 EtherNet/IP – Communication protocol 65

8
EtherNet/IP – Communication protocol

Contents of this chapter

This chapter describes the EtherNet/IP communication protocol for the adapter module.

EtherNet/IP
EtherNet/IP is a variant of the Common Industrial Protocol (CIP) family of communication
protocols intended for supervision and control of automation equipment. Specifically, it
covers the use of CIP messaging over an IP network, typically using Ethernet as the media.
The FEIP-21 adapter module acts as a server on an EtherNet/IP network with support for
the ODVA AC/DC drive, ABB Drives and Transparent profiles. Two simultaneous EtherNet/IP
connections are supported, that is, two clients can be connected to the adapter module at
a time.
Further information on the EtherNet/IP protocol is available at www.odva.org.

Object modeling and functional profiles

One of the main features of EtherNet/IP is object modeling. A group of objects can be
described with a Functional Profile. The FEIP-21 adapter module realizes the ODVA AC/DC
drive Functional Profile with additional features.

Assembly objects
I/O assembly instances may also be referred to as Block Transfer of data. Intelligent devices
realizing a Functional Profile, such as FEIP-21, 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 using the
assembly object. The assembly object acts as a tool for grouping these attributes.
66 EtherNet/IP – Communication protocol

The assembly selections described above are, in fact, instances of the assembly object
class. The 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 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Fault Reset Run Fwd

2 Speed Reference (Low Byte)

3 Speed Reference (High Byte)

The format of the input assembly is:

Instance 70 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Running1 Faulted
(Fwd)

2 Speed Actual (Low Byte)

3 Speed Actual (High Byte)

￭ 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 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Fault reset Run Fwd

2 Speed Actual (Low Byte)

3 Speed Actual (High Byte)

4 DATA OUT 1 Value (Low Byte)

5 DATA OUT 1 Value (High Byte)

6 DATA OUT 2 Value (Low Byte)

7 DATA OUT 2 Value (High Byte)

 EtherNet/IP – Communication protocol 67

Instance 120 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

8 DATA OUT 3 Value (Low Byte)

9 DATA OUT 3 Value (High Byte)

10 DATA OUT 4 Value (Low Byte)

11 DATA OUT 4 Value (High Byte)

12 DATA OUT 5 Value (Low Byte)

13 DATA OUT 5 Value (High Byte)

14 DATA OUT 6 Value (Low Byte)

15 DATA OUT 6 Value (High Byte)

16 DATA OUT 7 Value (Low Byte)

17 DATA OUT 7 Value (High Byte)

18 DATA OUT 8 Value (Low Byte)

19 DATA OUT 8 Value (High Byte)

20 DATA OUT 9 Value (Low Byte)

21 DATA OUT 9 Value (High Byte)

22 DATA OUT 10 Value (Low Byte)

23 DATA OUT 10 Value (High Byte)

The format of the input assembly is:

Instance 170 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Running1 Faulted
(Fwd)

2 Speed Actual (Low Byte)

3 Speed Actual (High Byte)

4 DATA IN 1 Value (Low Byte)

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 DATA IN 4 Value (Low Byte)

11 DATA IN 4 Value (High Byte)

68 EtherNet/IP – Communication protocol

Instance 170 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

12 DATA IN 5 Value (Low Byte)

13 DATA IN 5 Value (High Byte)

14 DATA IN 6 Value (Low Byte)

15 DATA IN 6 Value (High Byte)

16 DATA IN 7 Value (Low Byte)

17 DATA IN 7 Value (High Byte)

18 DATA IN 8 Value (Low Byte)

19 DATA IN 8 Value (High Byte)

20 DATA IN 9 Value (Low Byte)

21 DATA IN 9 Value (High Byte)

22 DATA IN 10 Value (Low Byte)

23 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 (ODVA AC/DC profile)

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

2 Speed Reference (Low Byte)

3 Speed Reference (High Byte)

The format of the input assembly is:

Instance 71 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 At Refer- Ref From Ctrl From Ready Running2 Running1 Warning Faulted
ence Net Net (Rev) (Fwd)

1 Drive State.
See section State (Control supervisor object) (page 57).

2 Speed Actual (Low Byte)

3 Speed Actual (High Byte)

 EtherNet/IP – Communication protocol 69

￭ 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 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Net Ref Net Ctrl Fault reset Run Rev Run Fwd

2 Speed Actual (Low Byte)

3 Speed Actual (High Byte)

4 DATA OUT 1 Value (Low Byte)

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 DATA OUT 4 Value (Low Byte)

11 DATA OUT 4 Value (High Byte)

12 DATA OUT 5 Value (Low Byte)

13 DATA OUT 5 Value (High Byte)

14 DATA OUT 6 Value (Low Byte)

15 DATA OUT 6 Value (High Byte)

16 DATA OUT 7 Value (Low Byte)

17 DATA OUT 7 Value (High Byte)

18 DATA OUT 8 Value (Low Byte)

19 DATA OUT 8 Value (High Byte)

20 DATA OUT 9 Value (Low Byte)

21 DATA OUT 9 Value (High Byte)

22 DATA OUT 10 Value (Low Byte)

23 DATA OUT 10 Value (High Byte)

The format of the input assembly is:

70 EtherNet/IP – Communication protocol

Instance 171 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 At Refer- Ref From Ctrl From Ready Running2 Running1 Warning Faulted
ence Net Net (Rev) (Fwd)

1 Drive State
See section State (Control supervisor object) (page 57).

2 Speed Actual (Low Byte)

3 Speed Actual (High Byte)

4 DATA IN 1 Value (Low Byte)

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 DATA IN 4 Value (Low Byte)

11 DATA IN 4 Value (High Byte)

12 DATA IN 5 Value (Low Byte)

13 DATA IN 5 Value (High Byte)

14 DATA IN 6 Value (Low Byte)

15 DATA IN 6 Value (High Byte)

16 DATA IN 7 Value (Low Byte)

17 DATA IN 7 Value (High Byte)

18 DATA IN 8 Value (Low Byte)

19 DATA IN 8 Value (High Byte)

20 DATA IN 9 Value (Low Byte)

21 DATA IN 9 Value (High Byte)

22 DATA IN 10 Value (Low Byte)

23 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 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Fault Reset Run Fwd

1
 EtherNet/IP – Communication protocol 71

Instance 22 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

2 Speed Reference (Low Byte)

3 Speed Reference (High Byte)

4 Torque Reference (Low Byte)

5 Torque Reference (High Byte)

The format of the input assembly is:

Instance 72 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Running1 Faulted
(Fwd)

2 Speed Actual (Low Byte)

3 Speed Actual (High Byte)

4 Torque Actual (Low Byte)

5 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 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Fault reset Run Fwd

2 Speed Reference (Low Byte)

3 Speed Reference (High Byte)

4 Torque Reference (Low Byte)

5 Torque Reference (High Byte)

6 DATA OUT 1 Value (Low Byte)

7 DATA OUT 1 Value (High Byte)

8 DATA OUT 2 Value (Low Byte)

9 DATA OUT 2 Value (High Byte)

10 DATA OUT 3 Value (Low Byte)

72 EtherNet/IP – Communication protocol

Instance 122 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

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)

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 172 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Running1 Faulted
(Fwd)

2 Speed Actual (Low Byte)

3 Speed Actual (High Byte)

4 Torque Actual (Low Byte)

5 Torque Actual (High Byte)

6 DATA IN 1 Value (Low Byte)

7 DATA IN 1 Value (High Byte)

8 DATA IN 2 Value (Low Byte)

9 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)

 EtherNet/IP – Communication protocol 73

Instance 172 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

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)

￭ 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 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Net Ref Net Ctrl Fault Reset Run Rev Run Fwd

2 Speed Reference (Low Byte)

3 Speed Reference (High Byte)

4 Torque Reference (Low Byte)

5 Torque Reference (High Byte)

The format of the input assembly is:

Instance 73 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 At Refer- Ref From Ctrl From Ready Running2 Running1 Warning Faulted
ence Net Net (Rev) (Fwd)

1 Drive State
See section State (Control supervisor object) (page 57).

2 Speed Actual (Low Byte)

74 EtherNet/IP – Communication protocol

Instance 73 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

3 Speed Actual (High Byte)

4 Torque Actual (Low Byte)

5 Torque Actual (High Byte)

￭ 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 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 NetRef NetCtl Fault reset Run Rev Run Fwd

2 Speed Reference (Low Byte)

3 Speed Reference (High Byte)

4 Torque Reference (Low Byte)

5 Torque Reference (High Byte)

6 DATA OUT 1 Value (Low Byte)

7 DATA OUT 1 Value (High Byte)

8 DATA OUT 2 Value (Low Byte)

9 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)

21 DATA OUT 8 Value (High Byte)

22 DATA OUT 9 Value (Low Byte)

 EtherNet/IP – Communication protocol 75

Instance 123 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

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 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 At Refer- Ref From Ctrl From Ready Running2 Running1 Warning Faulted
ence Net Net (Rev) (Fwd)

1 Drive State
See section State (Control supervisor object) (page 57).

2 Speed Actual (Low Byte)

3 Speed Actual (High Byte)

4 Torque Actual (Low Byte)

5 Torque Actual (High Byte)

6 DATA IN 1 Value (Low Byte)

7 DATA IN 1 Value (High Byte)

8 DATA IN 2 Value (Low Byte)

9 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)

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)

76 EtherNet/IP – Communication protocol

Instance 173 (ODVA AC/DC profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

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 1 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Reset Ramp in Ramp Hold Ramp Out Inhibit Oper- Off 3 Con- Off 2 Con- Off 1 Con-
Zero Zero ation trol trol trol

1 Ext Ctrl Loc Remote

Cmd

2 Set Speed (Low Byte)

3 Set Speed (High Byte)

The format of the input assembly is:

Instance 51 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Alarm Swc On In- Off 3 Sta Off 2 Sta Tripped Rdy Ref Rdy Run Rdy On
hib

1 Fieldbus Ext Run Ext Ctrl Loc Above Lim- Remote At Setpoint
Error Enable it

2 Actual Speed (Low Byte)

3 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 101 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Reset Ramp in Ramp Hold Ramp Out Inhibit Oper- Off 3 Con- Off 2 Con- Off 1 Con-
Zero Zero ation trol trol trol

1 Ext Ctrl Loc Remote

Cmd

2 Set Speed (Low Byte)

3 Set Speed (High Byte)

 EtherNet/IP – Communication protocol 77

Instance 101 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

4 DATA OUT 1 Value (Low Byte)

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 DATA OUT 4 Value (Low Byte)

11 DATA OUT 4 Value (High Byte)

12 DATA OUT 5 Value (Low Byte)

13 DATA OUT 5 Value (High Byte)

14 DATA OUT 6 Value (Low Byte)

15 DATA OUT 6 Value (High Byte)

16 DATA OUT 7 Value (Low Byte)

17 DATA OUT 7 Value (High Byte)

18 DATA OUT 8 Value (Low Byte)

19 DATA OUT 8 Value (High Byte)

20 DATA OUT 9 Value (Low Byte)

21 DATA OUT 9 Value (High Byte)

22 DATA OUT 10 Value (Low Byte)

23 DATA OUT 10 Value (High Byte)

The format of the input assembly is:

Instance 151 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Alarm Swc On In- Off 3 Sta Off 2 Sta Tripped Rdy Ref Rdy Run Rdy On
hib

1 Fieldbus Ext Run Ext Ctrl Loc Above Lim- Remote At Setpoint
Error Enable it

2 Actual Speed (Low Byte)

3 Actual Speed (High Byte)

4 DATA IN 1 Value (Low Byte)

5 DATA IN 1 Value (High Byte)

6 DATA IN 2 Value (Low Byte)

7 DATA IN 2 Value (High Byte)

78 EtherNet/IP – Communication protocol

Instance 151 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

8 DATA IN 3 Value (Low Byte)

9 DATA IN 3 Value (High Byte)

10 DATA IN 4 Value (Low Byte)

11 DATA IN 4 Value (High Byte)

12 DATA IN 5 Value (Low Byte)

13 DATA IN 5 Value (High Byte)

14 DATA IN 6 Value (Low Byte)

15 DATA IN 6 Value (High Byte)

16 DATA IN 7 Value (Low Byte)

17 DATA IN 7 Value (High Byte)

18 DATA IN 8 Value (Low Byte)

19 DATA IN 8 Value (High Byte)

20 DATA IN 9 Value (Low Byte)

21 DATA IN 9 Value (High Byte)

22 DATA IN 10 Value (Low Byte)

23 DATA IN 10 Value (High Byte)

￭ 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 2 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Reset Ramp in Ramp Hold Ramp Out Inhibit Oper- Off 3 Con- Off 2 Con- Off 1 Con-
Zero Zero ation trol trol trol

1 Ext Ctrl Loc Remote

Cmd

2 Set Speed (Low Byte)

3 Set Speed (High Byte)

4 Set Torque (Low Byte)

5 Set Torque (High Byte)

The format of the input assembly is:

 EtherNet/IP – Communication protocol 79

Instance 52 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Alarm Swc On In- Off 3 Sta Off 2 Sta Tripped Rdy Ref Rdy Run Rdy On
hib

1 Fieldbus Ext Run Ext Ctrl Loc Above Lim- Remote At Setpoint
Error Enable it

2 Actual Speed (Low Byte)

3 Actual Speed (High Byte)

4 Actual Torque (Low Byte)

5 Actual Torque (High Byte)

￭ 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 102 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Reset Ramp in Ramp Hold Ramp Out Inhibit Oper- Off 3 Con- Off 2 Con- Off 1 Con-
Zero Zero ation trol trol trol

1 Ext Ctrl Loc Remote

Cmd

2 Set Speed (Low Byte)

3 Set Speed (High Byte)

4 Set Torque (Low Byte)

5 Set Torque (High Byte)

6 DATA OUT 1 Value (Low Byte)

7 DATA OUT 1 Value (High Byte)

8 DATA OUT 2 Value (Low Byte)

9 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)

80 EtherNet/IP – Communication protocol

Instance 102 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

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 152 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Alarm Swc On In- Off 3 Sta Off 2 Sta Tripped Rdy Ref Rdy Run Rdy On
hib

1 Fieldbus Ext Run Ext Ctrl Loc Above Lim- Remote At Setpoint
Error Enable it

2 Actual Speed (Low Byte)

3 Actual Speed (High Byte)

4 Actual Torque (Low Byte)

5 Actual Torque (High Byte)

6 DATA IN 1 Value (Low Byte)

7 DATA IN 1 Value (High Byte)

8 DATA IN 2 Value (Low Byte)

9 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)

17 DATA IN 6 Value (High Byte)

18 DATA IN 7 Value (Low Byte)

 EtherNet/IP – Communication protocol 81

Instance 152 (ABB Drives profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

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 11 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 16-bit Control Word (Low Byte)

1 Drive Profile 16-bit Control Word (High Byte)

2 Drive Profile 16-bit Reference 1 Word (Low Byte)

3 Drive Profile 16-bit Reference 1 Word (High Byte)

The format of the input assembly is:

Instance 61 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 16-bit Status Word (Low Byte)

1 Drive Profile 16-bit Status Word (High Byte)

2 Drive Profile 16-bit Actual 1 Word (Low Byte)

3 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 111 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 16-bit Control Word (Low Byte)

82 EtherNet/IP – Communication protocol

Instance 111 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

1 Drive Profile 16-bit Control Word (High Byte)

2 Drive Profile 16-bit Reference 1 Word (Low Byte)

3 Drive Profile 16-bit Reference 1 Word (High Byte)

4 DATA OUT 1 Value (Low Byte)

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 DATA OUT 4 Value (Low Byte)

11 DATA OUT 4 Value (High Byte)

12 DATA OUT 5 Value (Low Byte)

13 DATA OUT 5 Value (High Byte)

14 DATA OUT 6 Value (Low Byte)

15 DATA OUT 6 Value (High Byte)

16 DATA OUT 7 Value (Low Byte)

17 DATA OUT 7 Value (High Byte)

18 DATA OUT 8 Value (Low Byte)

19 DATA OUT 8 Value (High Byte)

20 DATA OUT 9 Value (Low Byte)

21 DATA OUT 9 Value (High Byte)

22 DATA OUT 10 Value (Low Byte)

23 DATA OUT 10 Value (High Byte)

The format of the input assembly is:

Instance 161 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 16-bit Status Word (Low Byte)

1 Drive Profile 16-bit Status Word (High Byte)

2 Drive Profile 16-bit Actual 1 Word (Low Byte)

3 Drive Profile 16-bit Actual 1 Word (High Byte)

4 DATA IN 1 Value (Low Byte)

5 DATA IN 1 Value (High Byte)

 EtherNet/IP – Communication protocol 83

Instance 161 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

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 DATA IN 4 Value (Low Byte)

11 DATA IN 4 Value (High Byte)

12 DATA IN 5 Value (Low Byte)

13 DATA IN 5 Value (High Byte)

14 DATA IN 6 Value (Low Byte)

15 DATA IN 6 Value (High Byte)

16 DATA IN 7 Value (Low Byte)

17 DATA IN 7 Value (High Byte)

18 DATA IN 8 Value (Low Byte)

19 DATA IN 8 Value (High Byte)

20 DATA IN 9 Value (Low Byte)

21 DATA IN 9 Value (High Byte)

22 DATA IN 10 Value (Low Byte)

23 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 12 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 16-bit Control Word (Low Byte)

1 Drive Profile 16-bit Control Word (High Byte)

2 Drive Profile 16-bit Reference 1 Word (Low Byte)

3 Drive Profile 16-bit Reference 1 Word (High Byte)

4 Drive Profile 16-bit Reference 2 Word (Low Byte)

5 Drive Profile 16-bit Reference 2 Word (High Byte)

The format of the input assembly is:

84 EtherNet/IP – Communication protocol

Instance 62 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 16-bit Status Word (Low Byte)

1 Drive Profile 16-bit Status Word (High Byte)

2 Drive Profile 16-bit Actual 1 Word (Low Byte)

3 Drive Profile 16-bit Actual 1 Word (High Byte)

4 Drive Profile16-bit Actual 2 Word (Low Byte)

5 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 112 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 16-bit Control Word (Low Byte)

1 Drive Profile 16-bit Control Word (High Byte)

2 Drive Profile 16-bit Reference 1 Word (Low Byte)

3 Drive Profile 16-bit Reference 1 Word (High Byte)

4 Drive Profile 16-bit Reference 2 Word (Low Byte)

5 Drive Profile 16-bit Reference 2 Word (High Byte)

6 DATA OUT 1 Value (Low Byte)

7 DATA OUT 1 Value (High Byte)

8 DATA OUT 2 Value (Low Byte)

9 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)

 EtherNet/IP – Communication protocol 85

Instance 112 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

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)

Instance 162 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 16-bit Status Word (Low Byte)

1 Drive Profile 16-bit Status Word (High Byte)

2 Drive Profile 16-bit Actual 1 Word (Low Byte)

3 Drive Profile 16-bit Actual 1 Word (High Byte)

4 Drive Profile 16-bit Actual 2 Word (Low Byte)

5 Drive Profile 16-bit Actual 2 Word (High Byte)

6 DATA IN 1 Value (Low Byte)

7 DATA IN 1 Value (High Byte)

8 DATA IN 2 Value (Low Byte)

9 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)

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)

86 EtherNet/IP – Communication protocol

Instance 162 (Transparent 16 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

24 DATA IN 10 Value (Low Byte)

25 DATA IN 10 Value (High Byte)

￭ 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 21 (Transparent 32 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 32-bit Control Word (Low Byte)

1 Drive Profile 32-bit Control Word

2 Drive Profile 32-bit Control Word

3 Drive Profile 32-bit Control Word (High Byte)

4 Drive Profile 32-bit Reference 1 Word (Low Byte)

5 Drive Profile 32-bit Reference 1 Word

6 Drive Profile 32-bit Reference 1 Word

7 Drive Profile 32-bit Reference 1 Word (High Byte)

The format of the input assembly is:

Instance 71 (Transparent 32 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 32-bit Status Word (Low Byte)

1 Drive Profile 32-bit Status Word

2 Drive Profile 32-bit Status Word

3 Drive Profile 32-bit Status Word (High Byte)

4 Drive Profile 32-bit Actual 1 Word (Low Byte)

5 Drive Profile 32-bit Actual 1 Word

6 Drive Profile 32-bit Actual 1 Word

7 Drive Profile 32-bit Actual 1 Word (High Byte)

￭ 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:
 EtherNet/IP – Communication protocol 87

Instance 121 (Transparent 32 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 32-bit Control Word (Low Byte)

1 Drive Profile 32-bit Control Word

2 Drive Profile 32-bit Control Word

3 Drive Profile 32-bit Control Word (High Byte)

4 Drive Profile 32-bit Reference 1 Word (Low Byte)

5 Drive Profile 32-bit Reference 1 Word

6 Drive Profile 32-bit Reference 1 Word

7 Drive Profile 32-bit Reference 1 Word (High Byte)

8 DATA OUT 1 Value (Low Byte)

9 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)

22 DATA OUT 8 Value (Low Byte)

23 DATA OUT 8 Value (High Byte)

24 DATA OUT 9 Value (Low Byte)

25 DATA OUT 9 Value (High Byte)

26 DATA OUT 10 Value (Low Byte)

27 DATA OUT 10 Value (High Byte)

The format of the input assembly is:

Instance 171 (Transparent 32 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 32-bit Status Word (Low Byte)

88 EtherNet/IP – Communication protocol

Instance 171 (Transparent 32 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

1 Drive Profile 32-bit Status Word

2 Drive Profile 32-bit Status Word

3 Drive Profile 32-bit Status Word (High Byte)

4 Drive Profile 32-bit Actual 1 Word (Low Byte)

5 Drive Profile 32-bit Actual 1 Word (High Byte)

6 Drive Profile 32-bit Actual 1 Word

7 Drive Profile 32-bit Actual 1 Word (High Byte)

8 DATA IN 1 Value (Low Byte)

9 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)

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:
 EtherNet/IP – Communication protocol 89

Instance 22 (Transparent 32 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 32-bit Control Word (Low Byte)

1 Drive Profile 32-bit Control Word

2 Drive Profile 32-bit Control Word

3 Drive Profile 32-bit Control Word (High Byte)

4 Drive Profile 32-bit Reference 1 Word (Low Byte)

5 Drive Profile 32-bit Reference 1 Word

6 Drive Profile 32-bit Reference 1 Word

7 Drive Profile 32-bit Reference 1 Word (High Byte)

8 Drive Profile 32-bit Reference 2 Word (Low Byte)

9 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 72 (Transparent 32 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 32-bit Status Word (Low Byte)

1 Drive Profile 32-bit Status Word

2 Drive Profile 32-bit Status Word

3 Drive Profile 32-bit Status Word (High Byte)

4 Drive Profile 32-bit Actual 1 Word (Low Byte)

5 Drive Profile 32-bit Actual 1 Word

6 Drive Profile 32-bit Actual 1 Word

7 Drive Profile 32-bit Actual 1 Word (High Byte)

8 Drive Profile 32-bit Actual 2 Word (Low Byte)

9 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)

￭ 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:
90 EtherNet/IP – Communication protocol

Instance 122 (Transparent 32 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 32-bit Control Word (Low Byte)

1 Drive Profile 32-bit Control Word

2 Drive Profile 32-bit Control Word

3 Drive Profile 32-bit Control Word (High Byte)

4 Drive Profile 32-bit Reference 1 Word (Low Byte)

5 Drive Profile 32-bit Reference 1 Word

6 Drive Profile 32-bit Reference 1 Word

7 Drive Profile 32-bit Reference 1 Word (High Byte)

8 Drive Profile 32-bit Reference 2 Word (Low Byte)

9 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)

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)

 EtherNet/IP – Communication protocol 91

The format of the input assembly is:

Instance 172 (Transparent 32 profile)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 Drive Profile 32-bit Status Word (Low Byte)

1 Drive Profile 32-bit Status Word

2 Drive Profile 32-bit Status Word

3 Drive Profile 32-bit Status Word (High Byte)

4 Drive Profile 32-bit Actual 1 Word (Low Byte)

5 Drive Profile 32-bit Actual 1 Word

6 Drive Profile 32-bit Actual 1 Word

7 Drive Profile 32-bit Actual 1 Word (High Byte)

8 Drive Profile 32-bit Actual 2 Word (Low Byte)

9 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)

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)

92 EtherNet/IP – Communication protocol

Class objects
The following table lists the data types used in the class object descriptions of this manual.

Legend Data type

UINT8 Unsigned Integer 8 bit

UINT16 Unsigned Integer 16 bit

SINT16 Signed Integer 16 bit

UINT32 Unsigned Integer 32 bit

BOOL Boolean value

Note:
The adapter module is designed to provide EtherNet/IP 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:
• drive manuals
• 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.
The table below shows the service names of the class objects.

Service Name

GET 0x0E Get_Attribute_Single

SET 0x10 Set_Attribute_Single

SET ALL 0x02 Set_Attribute_All

GET ALL 0x01 Get_Attribute_All

￭ Identity object, class 01h

This object provides identification of and general information about the device.

Class attributes (Instance #0)

# Attribute name Services Description Data type

1 Revision Get Revision of the iden- Array of UINT8

tity object

Instance attributes (Instance #1)

# Attribute name Services Description Data type

1 Vendor ID Get Identification of the UINT16

device vendor
 EtherNet/IP – Communication protocol 93

# Attribute name Services Description Data type

2 Device Type Get Identification of the UINT16

general product type

3 Product Code Get Assigned vendor UINT16

code to describe the
device

4 Revision Get Revision of the item Array[UINT8 UINT8]

the identity object
represents

5 Status Get Summary status of UINT16

the device

6 ODVA Serial Num- Get Serial number of the UINT32

ber EtherNet/IP module

7 Product Name Get Product identifica- Short String

tion. Max 32 charac-
ters.

Reset service (Service code 05h)

Value (reset type) Type of reset

0 Reset the adapter

1 Reset the adapter (* and factory default configuration)

2 Reset the adapter (* and set the out-of-box configuration with the exception of
communication link parameters)

* not implemented

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.

Drive Type Profile Device Type Value

AC ODVA AC/DC Drive ODVA AC Drive 02h

ABB Drives Profile ABB AC Drive 64h

Transparent 16 ABB AC Drive 64h

Transparent 32 ABB AC Drive 64h

DC ODVA AC/DC Drive ODVA DC Drive 13h

ABB Drives Profile ABB DC Drive 65h

Transparent 16 ABB DC Drive 65h

Transparent 32 ABB DC Drive 65h

94 EtherNet/IP – Communication protocol

Product Code
Every ABB drive type or application of the drive has a dedicated product code. The product
code is 100 + the value of parameter 29 FBA A/B drive type code (page 32).
Revision
Revision attribute, which consists of Major and Minor Revisions, identifies the revision of
the item the identity object represents.
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 the device (or an object within the device) has an owner.
Within the Master/Slave paradigm the setting of this bit means that the Pre-
defined 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 Reserved, set to 0

2 Configured TRUE indicates that 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 Vendor-specific

8 Minor Recoverable TRUE indicates the device detected a recoverable problem. The problem
Fault does not cause the device fault state.

9 Minor Unrecoverable TRUE indicates the device detected a unrecoverable problem. The problem
Fault does not cause the device fault state.

10 Major Recoverable TRUE indicates the device detected a problem which caused the device to
Fault transfer into the “Major Recoverable Fault” state.

11 Major Unrecoverable TRUE indicates the device detected a problem which caused the device to
Fault transfer into the “Major Unrecoverable Fault” state.

12, 13, Reserved, set to 0

14, 15

ODVA Serial Number

This attribute is a number used in conjunction with the Vendor ID to form a unique identifier
for each device on EtherNet/IP. 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.

￭ Motor data object, class 28h

The Motor data object can only be used if the ODVA AC/DC drive profile is in use.
The 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.
 EtherNet/IP – Communication protocol 95

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 name Services Description Data type

1 Revision Get Revision of the CIP Array of UINT8

Object Class Defini-
tion upon which the
implementation is
based

Instance attributes (Instance #1)

# Attribute name Services Description Motor type Data type

3 Motor type Get See the table AC UINT8

above.

6 Rated Current Get, Set Rated Stator AC/DC UINT16

Current from mo-
tor name plate
Units: [100mA]

7 Rated Voltage Get, Set Rated Base AC/DC UINT16

Voltage from mo-
tor name plate
Units: [V]

8 Rated Power Get, Set Rated Power at AC/DC UINT32

Rated Frequency
Units: [W]

9 Rated frequency Get, Set Rated Electrical AC UINT16

Frequency Units:
[Hz]

12 Pole Count Get Number of poles AC UINT16

in the motor

15 Base Speed Get, Set Nominal speed AC/DC UINT16

at rated fre-
quency from
nameplate Units
[RPM]

￭ Control supervisor object, class 29h

The Control supervisor object can only be used if the ODVA AC/DC drive profile is in use.
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:
• AC/DC-drive object, class 2Ah (page 97) and
96 EtherNet/IP – Communication protocol

• Run/Stop event matrix under Run Forward & Run Reverse (Control supervisor
object) (page 55).
See also section State (Control supervisor object) (page 57).
Note: If assembly instances are used, they override this object, for example, upon drive
power-up.

Class attributes (Instance #0)

# Attribute name Services Description Data type

1 Revision Get Revision of the CIP Array of UINT8

Object Class Defini-
tion upon which the
implementation is
based

Instance attributes (Instance #1)

# Attribute name Services Description Data type

3 Run 1 (RunFwd) Get, Set 0 = Stop, 1 = Run BOOL

See Run Forward &
Run Reverse (Con-
trol supervisor ob-
ject) (page 55).

4 Run 2 (RunRev) Get, Set 0 = Stop, 1 = Run BOOL

See Run Forward &
Run Reverse (Con-
trol supervisor ob-
ject) (page 55).

5 Net Control Get, Set 0 = Local Control, 1 BOOL

= Network Control

6 State Get State of Object. UINT8

See section State
(Control supervisor
object) (page 57).

7 Running 1 (Fwd) Get 0 = Stopped, 1 = BOOL

Running

8 Running 2 (Rev) Get 0 = Stopped, 1 = BOOL

Running

9 Ready Get 1 = Ready, Enabled BOOL

or Stopping; 0 = Oth-
er state

10 Faulted Get 0 = Not faulted, 1 = BOOL

Fault occurred

11 Warning Get 0 = No Warnings BOOL

present, 1 = Warning

12 FaultRst Get, Set 0 → 1 Fault Reset BOOL

 EtherNet/IP – Communication protocol 97

# Attribute name Services Description Data type

13 Fault Code Get The fault that caused UINT16

the last transition to
the Faulted state.
DRIVECOMM codes
are reported. See
the drive manual for
further information
on DRIVECOMM
codes.

14 Warning Code Get Code word indicating UINT16

the warning present.
If multiple warnings
are present, the low-
est code value is
displayed. DRIVE-
COMM codes are
reported. See the
drive manual for fur-
ther information on
DRIVECOMM
codes.

15 CtlFromNet Get 0 = NetControl dis- BOOL

abled
1 = NetControl en-
abled

16 DNFaultMode Get, Set 2 = Vendor specified UINT8

17 ForceFault Get, Set 0 → 1 forces the BOOL

drive to fault

￭ AC/DC-drive object, class 2Ah

The AC/DC-drive object can only be used if the ODVA AC/DC drive profile is in use.
The object models the functions specific to an AC or DC Drive.

Class attributes (Instance #0)

# Attribute name Services Description Data type

1 Revision Get Revision of the CIP Array of UINT8

Object Class Defini-
tion upon which the
implementation is
based

Instance attributes (Instance #1)

# Attribute name Services Description Data type

3 At Reference Get Frequency arrival BOOL

98 EtherNet/IP – Communication protocol

# Attribute name Services Description Data type

4 NetRef Get, Set Requests torque or BOOL

speed reference to
be local or from the
network.
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 Drive mode Get, Set 0 = Vendor-specific UINT8

7 Speed Actual Get Units = See paramet- SINT16

er 23 Speed
scale (page 30).

8 SpeedRef Get, Set Units = See paramet- SINT16

er 23 Speed
scale (page 30).

11 Torque Actual Get Units = See paramet- SINT16

er 24 Torque
scale (page 31).

12 TorqueRef Get, Set Units = See paramet- SINT16

er 24 Torque
scale (page 31).

18 AccelTime Get, Set Units = milliseconds UINT16

19 DecelTime Get, Set Units = milliseconds UINT16

22 Speed Scale Get, Set Speed scaling factor. UINT8

See parameter 23
Speed
scale (page 30).

24 Torque Scale Get, Set Torque scaling UINT8

factor. See paramet-
er 24 Torque
scale (page 31).

29 Ref From Net Get Reflecting attribute 4 BOOL

￭ Drive parameter object, class 90h

With the FEIP-21 adapter module, 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 you use 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.
 EtherNet/IP – Communication protocol 99

Class is always 144 (90h). Instance and attribute correspond to the drive parameter group
and index in the following way:
• Instance = Parameter group (0…99) (ACx880/580: 0...255)
• Attribute = Parameter index (01…99) (ACx880/580: 0...255)
For example, Parameter 99.01 is accessed as follows:
• Class = 144 = 90h
• Instance = 99 = 63h
• Attribute = 1 = 01h

￭ Fieldbus configuration object, class 91h

The fieldbus configuration object allows you to configure the fieldbus configuration groups
without the need to know the drive-specific groups associated with the configuration groups.
Note:
When you use the fieldbus configuration object to update the fieldbus configuration groups,
changes to the fieldbus configuration will only take effect when a reset service is requested
of the Identity Object, the module is powered up the next time or when a ‘Fieldbus Adapter
parameter refresh’ is given.

Class attributes

# Attribute name Services Description Data type

1 Revision Get Revision of the Con- Array of UINT8

figuration Object

Instance #1: FEIP-21 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 ACS380, ACS480, ACH580, ACQ580 and ACS580
• parameter group is typically 51/54 (group 151/154 in some variants) in ACS880 if the
adapter is installed as fieldbus adapter A/B.

# Attribute name Services Description Data type

1 Configuration Group Get, Set See FBA UINT16

A (Group 1) - Para- type (page 26) .
meter 1

2 Configuration Group Get, Set See Protocol/Pro- UINT16

A (Group 1) - Para- file (page 26).
meter 2

3 Configuration Group Get, Set See Comm- UINT16

A (Group 1) - Para- rate (page 26).
meter 3

4 Configuration Group Get, Set See IP configura- UINT16

A (Group 1) - Para- tion (page 27).
meter 4

5 Configuration Group Get, Set See IP address UINT16

A (Group 1) - Para- 1 (page 27).
meter 5
100 EtherNet/IP – Communication protocol

# Attribute name Services Description Data type

6 Configuration Group Get, Set See IP address UINT16

A (Group 1) - Para- 1 (page 27).
meter 6

7 Configuration Group Get, Set See IP address UINT16

A (Group 1) - Para- 1 (page 27).
meter 7

8 Configuration Group Get, Set See IP address UINT16

A (Group 1) - Para- 1 (page 27).
meter 8

9 Configuration Group Get, Set See Subnet UINT16

A (Group 1) - Para- CIDR (page 27).
meter 9

10 Configuration Group Get, Set See GW address UINT16

A (Group 1) - Para- 1 (page 28).
meter 10

11 Configuration Group Get, Set See GW address UINT16

A (Group 1) - Para- 1 (page 28).
meter 11

12 Configuration Group Get, Set See GW address UINT16

A (Group 1) - Para- 1 (page 28).
meter 12

13 Configuration Group Get, Set See GW address UINT16

A (Group 1) - Para- 1 (page 28).
meter 13

14 Configuration Group Get, Set See Commrate port UINT16

A (Group 1) - Para- 2 (page 28).
meter 14

15 Configuration Group Get, Set See Service configur- UINT16

A (Group 1) - Para- ation (page 28).
meter 15

16 Configuration Group Get, Set See Re- UINT16

A (Group 1) - Para- served (page 28).
meter 16

17 Configuration Group Get, Set See Re- UINT16

A (Group 1) - Para- served (page 28).
meter 17

18 Configuration Group Get, Set See Re- UINT16

A (Group 1) - Para- served (page 28).
meter 18

19 Configuration Group Get, Set See T16 UINT16

A (Group 1) - Para- scale (page 29).
meter 19

20 Configuration Group Get, Set See Control UINT16

A (Group 1) - Para- timeout (page 29).
meter 20

21 Configuration Group Get, Set See Idle ac- UINT16

A (Group 1) - Para- tion (page 30).
meter 21
 EtherNet/IP – Communication protocol 101

# Attribute name Services Description Data type

22 Configuration Group Get, Set See Stop func- UINT16

A (Group 1) - Para- tion (page 30).
meter 22

23 Configuration Group Get, Set See Speed UINT16

A (Group 1) - Para- scale (page 30).
meter 23

24 Configuration Group Get, Set See Torque UINT16

A (Group 1) - Para- scale (page 31).
meter 24

25 Configuration Group Get, Set See Re- UINT16

A (Group 1) - Para- served (page 31).
meter 25

26 Configuration Group Get, Set See Re- UINT16

A (Group 1) - Para- served (page 31).
meter 26

27 Configuration Group Get, Set See FBA A/B par re- UINT16
A (Group 1) - Para- fresh (page 31).
meter 27

28 Configuration Group Get See FBA A/B par UINT16

A (Group 1) - Para- table ver (page 32).
meter 28

29 Configuration Group Get See FBA A/B drive UINT16

A (Group 1) - Para- type code (page 32).
meter 29

30 Configuration Group Get See FBA A/B map- UINT16

A (Group 1) - Para- ping file
meter 30 ver (page 32).

31 Configuration Group Get See D2FBA A/B UINT16

A (Group 1) - Para- comm
meter 31 status (page 32).

32 Configuration Group Get See FBA A/B comm UINT16

A (Group 1) - Para- SW ver (page 32).
meter 32

33 Configuration Group Get See FBA A/B appl UINT16

A (Group 1) - Para- SW ver (page 33).
meter 33

Instance #2: FEIP-21 configuration parameters group B (group 2)

The actual parameter group number depends on the drive type. Group B (group 2)
corresponds to:
• parameter group 53 in ACS380, ACS480, ACH580, ACQ580 and ACS580
• parameter group is typically 53/56 (group 153/156 in some variants) in ACS880 if the
adapter is installed as fieldbus adapter A/B.

# Attribute name Services Description Data type

1 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
B (Group 2) - Para- out 1 (client to ACx880 / 580
meter 1 drive) (page 33).
102 EtherNet/IP – Communication protocol

# Attribute name Services Description Data type

2 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
B (Group 2) - Para- out 1 (client to ACx880 / 580
meter 2 drive) (page 33).

3 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
B (Group 2) - Para- out 1 (client to ACx880 / 580
meter 3 drive) (page 33).

4 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
B (Group 2) - Para- out 1 (client to ACx880 / 580
meter 4 drive) (page 33).

5 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
B (Group 2) - Para- out 1 (client to ACx880 / 580
meter 5 drive) (page 33).

6 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
B (Group 2) - Para- out 1 (client to ACx880 / 580
meter 6 drive) (page 33).

7 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
B (Group 2) - Para- out 1 (client to ACx880 / 580
meter 7 drive) (page 33).

8 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
B (Group 2) - Para- out 1 (client to ACx880 / 580
meter 8 drive) (page 33).

9 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
B (Group 2) - Para- out 1 (client to ACx880 / 580
meter 9 drive) (page 33).

10 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
B (Group 2) - Para- out 1 (client to ACx880 / 580
meter 10 drive) (page 33).

Instance #3: FEIP-21 configuration parameters group C (group 3)

The actual parameter group number depends on the drive type. Group C (group 3)
corresponds to:
• parameter group 52 in ACS380, ACS480, ACH580, ACQ580 and ACS580
• parameter group is typically 52/55 (group 152/155 in some variants) in ACS880 if the
adapter is installed as fieldbus adapter A/B.

# Attribute name Services Description Data type

1 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
C (Group 3) - Para- in1 (drive to cli- ACx880 / 580
meter 1 ent) (page 34).

2 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
C (Group 3) - Para- in1 (drive to cli- ACx880 / 580
meter 2 ent) (page 34).

3 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
C (Group 3) - Para- in1 (drive to cli- ACx880 / 580
meter 3 ent) (page 34).
 EtherNet/IP – Communication protocol 103

# Attribute name Services Description Data type

4 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
C (Group 3) - Para- in1 (drive to cli- ACx880 / 580
meter 4 ent) (page 34).

5 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
C (Group 3) - Para- in1 (drive to cli- ACx880 / 580
meter 5 ent) (page 34).

6 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
C (Group 3) - Para- in1 (drive to cli- ACx880 / 580
meter 6 ent) (page 34).

7 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
C (Group 3) - Para- in1 (drive to cli- ACx880 / 580
meter 7 ent) (page 34).

8 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
C (Group 3) - Para- in1 (drive to cli- ACx880 / 580
meter 8 ent) (page 34).

9 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
C (Group 3) - Para- in1 (drive to cli- ACx880 / 580
meter 9 ent) (page 34).

10 Configuration Group Get, Set See FBA A/B data UINT16 / UINT32
C (Group 3) - Para- in1 (drive to cli- ACx880 / 580
meter 10 ent) (page 34).

￭ TCP/IP interface object, class F5h

This object provides the mechanism to configure the TCP/IP network interface of the device.

Class attributes (Instance #0)

# Attribute name Services Description Data type

1 Revision Get Revision of the Array of UINT8

TCP/IP Interface
Object Class Defini-
tion upon which the
implementation is
based

Instance attributes (Instance #1)

# Attribute name Services Description Data type

1 Interface status Get See Interface Status DWORD

attribute (#1)
bits (page 104).

2 Configuration Capab- Get See Configuration DWORD

ility Capability attribute
(#2) bits (page 105).

3 Configuration Con- Get See Configuration DWORD

trol Control attribute (#3)
bits (page 105).
104 EtherNet/IP – Communication protocol

# Attribute name Services Description Data type

4 Physical Link Object Get Path to physical link STRUCT of:

object

Path Size Path size UINT

Path Logical segments Padded EPATH

identifying the physic-
al link object

5 Interface Configura- Get STRUCT of:

tion

IP Address IP Address UDINT

Network Mask Network Mask UDINT

Gateway Address Gateway Address UDINT

Unused UDINT

Unused UDINT

Default Domain Default Domain STRING

Name Name for unqualified
host names.

6 Host Name Get / Set Host name STRING

8 TTL Value Get / Set TTL value for Ether- USINT 1 ... 255
Net/IP multi cast
packets

13 NV Encapsulation Get / Set Encapsulation inactiv- UINT 0 = disabled 1

Inactivity ity timeout ... 3600 timeout in
seconds

Attribute explanations
Interface Status attribute (#1) bits

Bit Name Description

0 ... 3 Interface configura- Indicates the status of the Interface Configuration attribute.
tion status
Value Description

0 The Interface Configuration attribute has not been con-

figured.

1 The Interface Configuration attribute contains valid configur-

ation obtained from BOOTP, DHCP or non-volatile storage.

2 The IP address member of the Interface Configuration attrib-

ute contains valid configuration obtained from hardware
settings (e.g., push-wheel, thumbwheel).

3 ... 15 Reserved

4 Mcast pending Indicates a pending configuration change in the TTL Value and/or Mcast
Config attributes. This bit is set when either the TTL Value or Mcast Config
attribute is set, and cleared the next time the device starts.
 EtherNet/IP – Communication protocol 105

Bit Name Description

5 ... 31 Reserved, set to 0

Configuration Capability attribute (#2) bits

Bit Name Description

0 BOOTP client 1 (True) = The device is capable of obtaining its network configuration via
BOOTP.

1 DNS client 1 (True) = The device is capable of resolving host names by querying a DNS
server.

2 DHCP client 1 (True) = The device is capable of obtaining its network configuration via
DHCP.

3 DCHP-DNS update 1 (True) = The device is capable of sending its host name in the DHCP re-
quest as documented in Internet draft <draft-ietf-dhc-dhcp-dnc-12.txt>

4 Configuration set- 1 (True) = The Interface Configuration attribute is settable. Some devices,
table e.g., a PC or workstation, may not allow interface configuration to be set via
the TCP/IP interface object.

5 Hardware configur- 1 (True) = The IP address member of the Interface Configuration attribute
able can be obtained from hardware settings (e.g., push-wheel, thumb-wheel).

0 (False) = The Status instance attribute (1) Interface configuration status

field value shall never be 2. (The Interface configuration attribute contains
valid configuration obtained from hardware settings.)

6 ... 31 Reserved, set to 0

Configuration Control attribute (#3) bits

Bit Name Description

0 ... 3 Start-up configura- Determines how the device obtains its initial configuration and start-up.
tion
Value Description

0 The device uses the interface configuration values previously

stored (eg, in non-volatile memory or via hardware switches).

1 The device obtains its interface configuration values via

BOOTP.

2 The device obtains its interface configuration values via

DHCP upon startup.

3 ... 15 Reserved

4 DNS enable 1 (True) = The device resolves host names by querying a DNS server.

5 ... 31 Reserved, set to 0.

￭ Ethernet link object, class F6h

This object maintains link-specific counters and status information for the Ethernet
communication interface.
Class attributes (Instance #0)
106 EtherNet/IP – Communication protocol

# Attribute name Services Description Data type

1 Revision Get Revision of the Ether- Array of UINT8

net Link Object
Class Definition
upon which the imple-
mentation is based

Instance attributes (Instance #1)

# Attribute Services Description Data type

name

1 Interface Get, Set 10 or 100 Mbps UDINT

Speed

2 Interface Flags Get, Set Interface status flags: DWORD

Bit Description
0 Link status
1 Half/Full duplex
2 ... 4 Negotiation status
5 Manual setting requires reset
6 Local hardware fault
7 ... 31 Reserved

3 Physical Ad- Get Ethernet MAC address of the module ARRAY 6XUS-
dress INT

￭ Connection object, class 05h

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.
Connection object states

State Description State Description

00 Non-Existent 03 Established

01 Configuring 04 Timed Out

02 Waiting for Connection ID 05 Deferred Delete

Class attributes

# Attribute name Services Description Data type

1 Revision Get Revision of the con- Array of UINT8

nection object
 EtherNet/IP – Communication protocol 107

Instance attributes

Instance number Description

1 Explicit messaging connection

2 Polled I/O connection

4 Change-of-State / Cyclic I/O connection

# Attribute Services Description Data type

name

1 State Get State of the object. UINT8

See the Connection object states (page 106).

2 Instance Type Get Indicates either I/O (1) or messaging connection UINT8
(0).

3 Transport Get Defines the behavior of the connection. UINT8

Class Trigger

4 Produced Get Placed in CAN Identifier Field when the connec- UINT16
Cnxn Id tion transmits.

5 Consumed Get CAN Identifier Field value that denotes the mes- UINT16
Cnxn Id sage to be received

6 Comm Charac- Get Defines the Message Group(s) across which UINT8
teristics productions and consumptions are associated in
this connection.

7 Produced Con- Get Maximum number of bytes transmitted across UINT16

nection Size this connection

8 Consumed Get Maximum number of bytes received across this UINT16

Connection connection
size

9 Expected Get, Set Defines the timing associated with this connection UINT16
Packet Rate in milliseconds. A value of 0 deactivates the as-
sociated timers.

12 Watchdog Get, Set Defines how to handle Inactivity/Watchdog UINT8

Timeout Action timeouts.

13 Produced Con- Get Number of bytes in the produced_connec- UINT16

nection Path tion_path length attribute
Length

14 Produced Con- Get Application object producing data on this connec- Array of UINT8
nection Path tion

15 Consumed Get Number of bytes in the consumed_connec- UINT16

Connection tion_path length attribute
Path Length

16 Consumed Get Specifies the application object(s) that are to re- Array of UINT8
Connection ceive the data consumed by this connection ob-
Path ject.

17 Production In- Get Defines the minimum time between new data UINT16
hibit Time production in milliseconds.
108 EtherNet/IP – Communication protocol

￭ 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 timeouts and production retry limit.

Class attributes (Instance #0)

# Attribute Services Description Data type

name

1 Revision Get Revision of the CIP Object Class Definition upon Array of UINT8
which the implementation is based

Instance attributes (Instance #1)

# Attribute Services Description Data type

name

1 Acknowledge Get, Set Time in milliseconds to wait for acknowledge be- UINT16
Timer fore resending

2 Retry Limit Get, Set Number of Acknowledge Timeouts to wait before UINT8
informing the producing application of a Retry-
Limit_Reached event

3 COS Produ- Get Connection Instance Id which contains the path UINT16
cing Connec- of the producing I/O application object which will
tion Instance be notified of Acknowledge Handler events
 EtherNet/IP – Diagnostics 109

9
EtherNet/IP – Diagnostics

Contents of this chapter

This chapter explains how to trace faults with the status LEDs on the adapter module when
the module is used for EtherNet/IP communication.

Fault and warning messages

For the fault and warning messages concerning the adapter module, see the drive firmware
manual.

LEDs
The adapter module is equipped with three bicolor diagnostic LEDs. The LEDs are described
below.
110 EtherNet/IP – Diagnostics

Name Color Function

HOST Flashing green Establishing communication to host

Green Connection to host OK

Flashing red Communication to host lost temporarily

Flashing orange, al- Internal file system error. The error may be cleared by cycling drive
ternating with the power. If the error persists, contact your local ABB representative.
MODULE flashing
orange

MODULE Off There is no power applied to the device.

Green Device is operating in a normal condition.

Flashing green Device needs commissioning due to configuration missing, incomplete

or incorrect. The device may be in the Standby state. This may be
caused by the adapter waiting for a response from a DHCP server or
Duplicate Address Detection to complete.

Flashing red Ethernet interface is disabled. Duplicate Address Detection may have
detected a duplicate address. Check the IP configuration and either
initiate a Fieldbus Adapter parameter refresh or cycle power to the drive.

Flashing red-green Device is in Self Test.

Flashing orange, al- Internal file system error. The error may be cleared by cycling drive
ternating with the power. If the error persists, contact your local ABB representative.
HOST flashing or-
ange

NETWORK / Off Device is not on-line.

NET • The device has not completed the Duplicate Address Detection yet.
• The 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.
• The device has passed Duplicate Address Detection, is on-line, but
has no established connections to other nodes.
Green Device is on-line and has connections in the established state.

Flashing red One or more I/O connections are in the Timed-out state.

Red Failed communication device. The device has detected an error that
has rendered it incapable of communicating on the network (Duplicate
MAC ID or IP address detected).
 NONE – Start-up 111

10
NONE – Start-up

Contents of this chapter

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
• information on configuring the client for communication with the adapter module.

Warnings
WARNING!
Obey the safety instructions given in this manual and the drive documentation.

Drive configuration
The information in this section applies to all drive types compatible with the adapter module,
unless otherwise stated.

￭ Connection configuration using NONE protocol

After the adapter module is mechanically and electrically installed according to the instructions
in chapters Mechanical installation and Electrical installation, you must prepare the drive
for communication with the module.
The detailed procedure of activating the module using the NONE protocol with the drive
depends on the drive type. Normally, you must adjust a parameter to activate the
communication. See the drive-specific start-up sections Starting up fieldbus
communication (page 116).
112 NONE – Start-up

Once communication between the drive and the adapter module is 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. You can adjust the
parameters via a drive control panel or a PC tool.
Note:
• Not all drives will display the descriptive names for the configuration parameters.
• The new parameter settings take effect only when you power up the module the next
time or when you activate the fieldbus adapter refresh parameter.
• Use the NONE protocol selection when no fieldbus protocol is required. For example,
when only the Ethernet tool network is used or for synchronizing time.

FEIP-21 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 ACS380 and ACS580.
• 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 detec- 2222 = EtherNet/IP
ted by the drive. The value cannot be adjusted by the
user.
If the value is 0 = None, the communication between
the drive and the module has not been established.

02 Protocol/Profile Select NONE to disable the EtherNet/IP protocol. 2222 = EtherNet/IP

Other services (ABB IP Configuration tool, Ethernet
tool network, etc.) are still available, see Service con-
figuration (page 114).

200 = NONE NONE protocol

03 Commrate Sets the bit rate for the Ethernet interface. 0 = Auto

0 = Auto Autonegotiate

1 = 100 Mbps FD

2 = 100 Mbps HD

3 = 10 Mbps FD

4 = 10 Mbps HD

04 IP configuration Sets the method for configuring the IP address, subnet 1 = Dyn IP DHCP
mask and gateway address for the module.

0 = Static IP Configuration is obtained from parameters 05-13.

1 = Dyn IP DHCP Configuration is obtained via DHCP.

 NONE – Start-up 113

No. Name/Value Description Default

05 IP address 1 An IP address is assigned to each IP node on a net- 0

... work. An IP address is a 32-bit number that is typically
represented in “dotted decimal” notation consisting of
08
four decimal integers, on the range 0…255, separated
by periods. Each integer represents the value of one
octet (8-bits) in the IP address. Parameters define the
four octets of the IP address.

0...255 IP address

... ... ...

IP address 4 See parameter 05 (page 113) IP address 1 (page 113). 0

0...255 IP address

09 Subnet CIDR Subnet masks are used for splitting networks into 0
smaller networks called subnets. A subnet mask is a
32-bit binary number that splits the IP address into a
network address and host address.
Subnet masks are typically represented in either dotted
decimal notation or the more compact CIDR notation,
as shown in the table below.

CIDR Dotted decimal CIDR Dotted decimal

31 255.255.255.254 15 255.254.0.0
30 255.255.255.252 14 255.252.0.0
29 255.255.255.248 13 255.248.0.0
28 255.255.255.240 12 255.240.0.0
27 255.255.255.224 11 255.224.0.0
26 255.255.255.192 10 255.192.0.0
25 255.255.255.128 9 255.128.0.0
24 255.255.255.0 8 255.0.0.0
23 255.255.254.0 7 254.0.0.0
22 255.255.252.0 6 252.0.0.0
21 255.255.248.0 5 248.0.0.0
20 255.255.240.0 4 240.0.0.0
19 255.255.224.0 3 224.0.0.0
18 255.255.192.0 2 192.0.0.0
17 255.255.128.0 1 128.0.0.0
16 255.255.0.0

1...31 Subnet mask in CIDR notation

114 NONE – Start-up

No. Name/Value Description Default

10 GW address 1 IP gateways connect individual physical IP subnets 0

... into a unified IP network. When an IP node needs to
communicate with an IP node on another subnet, the
13
IP node sends the data to the IP gateway for forward-
ing. Parameters define the four octets of the gateway
address.

0...255 GW address

... ... ...

GW address 4 See parameter 10 (page 114) GW address 1 (page 114). 0

0.255 GW address

14 Commrate port 2 Sets the bit rate for the Ethernet port 2. 0 = Auto

0 = Auto Autonegotiate

1 = 100 Mbps FD 100 Mbps, full duplex

2 = 100 Mbps HD 100 Mbps, half duplex

3 = 10 Mbps FD 10 Mbps, full duplex

4 = 10 Mbps HD 10 Mbps, half duplex

15 Service configuration Disable services that are not required.

Each service is represented by a single bit. Bit 0, Lock
configuration, can be used to prevent accidental
changing of this parameter.
By default, all services are enabled and configuration
is unlocked.

Bit Name Information

0 Lock configuration Changing of this parameter are no longer possible when this bit
is set. Only reset fieldbus configuration to default will unlock the
parameter.

1 Disable IP config tool When this bit is set, access from ABB IP Configuration tool is
prevented.

2 Disable ETH tool net- When this bit is set, access from Ethernet tool network (eg, ABB
work Drive Composer tool) is prevented.

3 Disable ping response When this bit is set, response to ICMP (ping) message is preven-
ted.

0000b…1111b Service configuration

16 Reserved These parameters are not used by the adapter module N/A
... when using the NONE protocol.
26
 NONE – Start-up 115

No. Name/Value Description Default

27 FBA A/B par refresh Validates any changed adapter module configuration 0 = Done
parameter settings. After refreshing, the value reverts
automatically to 0 = Done.

Note:
This parameter cannot be changed while the drive is
running.

0 = Done Refreshing done

1 = Refresh Refreshing

28 FBA A/B par table ver Read-only. Displays the parameter table revision of N/A
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
OR
in format axyz, where
a = major revision number
xy = minor revision numbers
z = correction number or letter.

Parameter table revision

29 FBA A/B drive type Read-only. Displays the drive type code of the fieldbus N/A
code adapter module mapping file stored in the memory of
the drive.

Drive type code of the fieldbus adapter module map-

ping file

30 FBA A/B mapping file Read-only. Displays the fieldbus adapter module N/A
ver mapping file revision stored in the memory of the drive
in decimal format.

Mapping file revision

31 D2FBA A/B comm Read-only. Displays the status of the fieldbus adapter 0 = Idle
status module communication. or
4 = Offline
Note: or
The value names may vary by drive. 2 = Time out

0 = Idle Adapter is not configured.

1 = Exec.init Adapter is initializing.

2= Time out A timeout has occurred in the communication between

the adapter and the drive.

3= Conf.err There is an internal error in the communication

between the adapter and the drive. Contact your local
ABB representative.

4 = Off-line Adapter is off-line.

5 = On-line Adapter is on-line.

6 = Reset Adapter is performing a hardware reset.

116 NONE – Start-up

No. Name/Value Description Default

32 FBA A/B comm SW Read-only. Displays patch and build numbers of the N/A
ver adapter module's firmware version in xxyy format,
where:
xx = patch number
yy = build number.
Example: If the firmware version (<ma-
jor>.<minor>.<patch>.<build>) is 3.10.200.13, the value
C80D is displayed. If the version is 3.10.0.0, the value
0 is displayed.
See also parameter 33.

33 FBA A/B appl SW ver Read-only. Displays major and minor revision numbers N/A
of the adapter module's firmware version in xxyy
format, where:
xx = major revision number
yy = minor revision number
Example: If the firmware version (<ma-
jor>.<minor>.<patch>.<build>) is 3.10.200.13 or
3.10.0.0, the value 310 is displayed.
See also parameter 32.

Starting up fieldbus communication

1. Power up the drive.
2. Enable communication between the adapter module and the drive by selecting the
correct slot number in parameter 50.01 FBA A enable.
The selection must correspond to the slot where the adapter module is installed. For
example, if the adapter module is installed in slot 1, you must select slot 1.
3. Set the module configuration parameters in group 51.
• select the communication protocol and profile with parameter 51.02, and
• configure the network settings with parameters 51.03…51.13.
4. Save the valid parameter values to permanent memory with parameter 96.07 Parameter
save manually.
5. Validate the settings made in parameter groups 51 with parameter 51.27 FBA A par
refresh.
 NONE – Diagnostics 117

11
NONE – Diagnostics

Contents of this chapter

This chapter explains how to trace faults with the status LEDs on the adapter module using
the NONE protocol.

Fault and warning messages

For the fault and warning messages concerning the adapter module, see the drive firmware
manual.

LEDs
The adapter module is equipped with three bicolor diagnostic LEDs. The LEDs are described
below.
118 NONE – Diagnostics

Name Color Function

HOST Flashing green Establishing communication to drive

Green Connection to drive OK

Flashing red Communication to drive lost temporarily

Flashing orange, al- Internal file system error. The error may be cleared by cycling drive
ternating with the power. If the error persists, contact your local ABB representative.
MODULE flashing
orange

MODULE Off There is no PC tool connected to the device.

Flashing orange Device is attempting to obtain IP configuration from the DHCP server.

Orange Device is executing Duplicate Address Detection.

Green PC tool is connected to the device.

Flashing red Ethernet link is down.

Red Ethernet interface is disabled. Duplicate Address Detection may have

detected a duplicate address. Check the IP configuration and either
initiate a Fieldbus Adapter parameter refresh or cycle power to the drive.

Flashing orange, al- Internal file system error. The error may be cleared by cycling drive
ternating with the power. If the error persists, contact your local ABB representative.
HOST flashing or-
ange

NETWORK / Off Ethernet link is down.

NET
Flashing green Ethernet link is up at 100 Mbps.
Flashing indicates activity on interface.

Flashing orange Ethernet link is up at 10 Mbps.

Flashing indicates activity on interface.
 Technical data 119

12
1 2 3 4 5 6
First angle projection. Original drawing made with 3D CAD. Set the correct scale factor when adding
dimensions after DWG/DXF conversion.

Technical data
therein. Reproduction,

A
forbidden.

[.85]
21,5

Contents of this chapter

T.Huoso
use or disclosure to third parties without express authority is strictly
We reserve all rights in this document and in the information contained

This chapter contains the technical specifications of the FEIP-21 module.

B
Dimension drawing
29-Jan-18
© ABB Oy. PROPRIETARY AND SECRET INFORMATION. CONFIDENTIAL

SUPPLY CONDITION
LOCK OPEN
63 5 16 20 15

[.30]
[2.48] [.20] [.63] [.80] [.

7,5
C
[2.56]

[1.97]

D
65

50
A.3+
A.2+

E
3 21
[.12] [.83]
Initial Approval
3AXD50000192793 (ASSEM)

DIMENSIONAL DRAWING FOR FEIP-21 FIELDBUS KIT 3AXD5000

3AXD50000190171

F Based on Prepared T.Huoso 29-Jan-18 Title DIMENSION DRAWING Doc. d

Customer Check. M.Karna 29-Jan-18 FEIP-21 ADAPTER DIME
Appr. V.Jung 29-Jan-18 ETHERNET/IP Resp.de
Cust. Doc. No. Project name Doc. N
A

DMS Number 3AXD10000657932 Weight kg 0.07

120 Technical data

General data
Installation Into an option slot on the drive control unit

Degree of protection IP20

Ambient conditions The applicable ambient conditions specified for the drive in its manuals
are in effect.

Package Cardboard. Plastic wrapping: Antistatic air bubble sheet (PE).

Indicators Three bicolor LEDs (HOST, MODULE, NETWORK/NET)

Connectors A 20-pin connector to the drive

RJ-45 connector to Ethernet (X1)
RJ-45 connector for chaining another adapter module (X2)

Power supply +3.3 V ±5% max. 400 mA (supplied by the drive)

General Complies with EMC standard EN 61800-3:2004

Printed circuit board conformal coated

Ethernet link
Compatible devices Ethernet Standard IEEE 802.3 and IEEE 802.3u devices

Medium 10BASE-TX or 100Base-TX with Auto-negotiation and Auto-MDIX (Auto-

crossover)
• Wiring: CAT5e/6 FTP, CAT5e/6 STP, CAT5e/6 SF/FTP
• Connector: RJ-45
• Termination: Internal
• Maximum segment length: 100 m / 328 ft
Topology Bus, star or ring.
Max. 50 nodes allowed for FEIP-21 module in a ring topology.
In a chain maximum recommended amount of nodes is 50.

Transfer rate 10 Mbps or 100 Mbps

Serial communication type Half or full duplex

Protocol EtherNet/IP

TCP and UDP service ports

There are multiple in-bound and out-bound network services running on the module. Some
ports are protocol-specific and are not used when other protocols are selected.

Port Service Purpose

80 (TCP) HTTP HTTP protocol, used for Ethernet tool Network (like Drive composer
pro)
68 (UDP) DHCP DHCP client

Note:
Used only when IP configuration method is selected as "Dyn IP
DHCP".
 Technical data 121

Port Service Purpose

24576 (UDP) ABB Netconfig • Auto discovery protocol
• Used by ControlBuilder plus (IP Configuration tool) and Drive
composer pro tools
• Discovers ABB-specific Ethernet devices in a local network
segment, by listening to and responding to UDP broadcasts.
44818 (TCP) Ethernet/IP Ethernet/IP, explicit messaging.

Note:
Used only when Ethernet/IP protocol is selected

2222 (UDP) Ethernet/IP Ethernet/IP, implicit messaging.

Note:
Used only when Ethernet/IP protocol is selected
122
 Appendix A - ABB IP configuration tool 123

13
Appendix A - ABB IP configuration tool

Contents of this chapter

This chapter shows how to use the ABB IP configuration tool to:
• find configured and unconfigured FEIP-21 adapter modules in the network
• rewrite the IP configuration of the adapter modules.

Installation
The ABB IP configuration tool is part of the ABB Automation Builder software. No separate
installation is needed.

Finding adapter modules in the network

1. Open the ABB IP configuration tool.
2. Click the Scan button.
The FEIP-21 adapter modules present in the network appear on the results list.
124 Appendix A - ABB IP configuration tool

Rewriting the IP configuration of adapter modules

1. Scan the network for adapter modules.
For instructions, see section Finding adapter modules in the network (page 123).
2. On the results list, click to select the adapter module whose IP configuration you want
to modify.

3. Below New configuration, define the IP configuration settings according to your network
configuration.
4. If you want the adapter module to use a static IP address instead of DHCP, clear the
DHCP check box.
 Appendix A - ABB IP configuration tool 125

5. To apply the new settings, click the Send Configuration button.

The new current IP address and configured IP address appear on the results list.
126
 Appendix B - Module configuration backup 127

14
Appendix B - Module configuration
backup

Contents of this chapter

This chapter presents the settings for FEIP-21 configuration backup.

Compatibility
FEIP-21 settings are stored in the drive parameters and also in the configuration files.
FEIP-21 adapter module supports backup of all settings to the drive. These settings are
now also included in any backups made of the drive using the Drive composer PC tool or
the control panel.

Settings for backup

Consider the following points:
• Backup is not slot-specific. For example, backup of FEIP-21 in FBA A, slot 1 can be
restored to FEIP-21 FBA A, slot 2.
• Backup depends on the fieldbus channel. For example, backup of FEIP-21 in FBA A is
not restored to FEIP-21 in FBA B.
• FEIP-21 configuration parameters are included in the backup when drive parameters
are saved.

￭ Configuration backup for all protocols in FEIP-21

The settings are saved to the drive after 10 seconds. If a Refresh command is given to
FEIP-21 using parameter 51.27, the pending backup is transferred to drive immediately and
FEIP-21 is rebooted after the transfer is completed.
128 Appendix B - Module configuration backup

Note:
The new setting is not saved to drive if the drive was powered off or the adapter was
disconnected from the drive within 10 seconds of changing a setting.
—
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/searchchannels.

Product training
For information on ABB product training, navigate to new.abb.com/service/training.

Providing feedback on ABB manuals

Your comments on our manuals are welcome. Navigate to
new.abb.com/drives/manuals-feedback-form.

Document library on the Internet

You can find manuals and other product documents in PDF format on the Internet at
www.abb.com/drives/documents.

a1 (frozen)
PDF-Web
Created 2018-12-18, 16:43:18
www.abb.com/drives
www.abb.com/solarinverters
www.abb.com/windconverters

3AXD50000158621A

3AXD50000158621 Rev A (EN) EFFECTIVE 2018-12-18

© Copyright 2018 ABB. All rights reserved.

Specifications subject to change without notice.