ABB FENA 01 11 Ethernet Manual

ABB fieldbus options
User’s manual
FENA-01/-11 Ethernet adapter module
List of related manuals
See section Related manuals on page 23.
User’s manual
FENA-01/-11 Ethernet adapter
module
Table of contents
1. Safety
4. Mechanical installation
5. Electrical installation
Modbus/TCP protocol
EtherNet/IP protocol
PROFINET IO protocol
3AUA0000093568 Rev A
EN © 2011 ABB Oy
EFFECTIVE: 2011-09-07 All Rights Reserved.
Table of contents 5
Table of contents
List of related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1. Safety
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Use of warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Safety in installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2. About the manual
Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Purpose of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Terms and abbreviations used in this manual . . . . . . . . . . . . . . 27
General terms and abbreviations . . . . . . . . . . . . . . . . . . . . 27
Modbus/TCP terms and abbreviations . . . . . . . . . . . . . . . . 28
EtherNet/IP terms and abbreviations . . . . . . . . . . . . . . . . . . 28
PROFINET IO terms and abbreviations . . . . . . . . . . . . . . . 29
3. Overview of the Ethernet network and the FENA-01/
-11 module
Ethernet network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Example topology of the Ethernet link . . . . . . . . . . . . . . . . . 34
FENA-01/-11 Ethernet adapter module . . . . . . . . . . . . . . . . . . . 34
Layout of the adapter module . . . . . . . . . . . . . . . . . . . . . . . 35
6 Table of contents
4. Mechanical installation
Delivery check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Mounting the adapter module . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5. Electrical installation
General cabling instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Connecting the module to the Ethernet network . . . . . . . . . . . . 40
Modbus/TCP protocol
6. Modbus/TCP – Start-up
Drive configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Modbus/TCP connection configuration . . . . . . . . . . . . . . . . 44
FENA-01/-11 configuration parameters – group A
(group 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
FENA-01/-11 configuration parameters – group B
(group 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
FENA-01/-11 configuration parameters – group C
(group 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Control locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Starting up ACS355 drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Parameter setting examples – ACS355 . . . . . . . . . . . . . . . . 58
Speed and torque control using the ABB Drives -
Enhanced communication profile . . . . . . . . . . . . . . . . . . 58
Starting up ACSM1 drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Parameter setting examples – ACSM1 . . . . . . . . . . . . . . . . 62
Enhanced communication profile . . . . . . . . . . . . . . . . . . 62
Starting up ACS850 and ACQ810 drives . . . . . . . . . . . . . . . . . . 66
Parameter setting examples – ACS850 and ACQ810 . . . . . 67
Speed control using the ABB Drives - Enhanced
communication profile. . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table of contents 7
Starting up ACS880 drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Parameter setting examples – ACS880 . . . . . . . . . . . . . . . 71
communication profile . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Modbus register maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
7. Modbus/TCP – Communication profiles
Communication profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
ABB Drives communication profile . . . . . . . . . . . . . . . . . . . . . . . 77
Control word and Status word . . . . . . . . . . . . . . . . . . . . . . . 77
Control word contents . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Status word contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
State machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Actual values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8. Modbus/TCP – Communication protocol
Modbus/TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Register addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Function codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Encapsulated Interface Transport / Read Device Identification . 87
Exception codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Communication profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
ABB Drives profile - Classic . . . . . . . . . . . . . . . . . . . . . . . . . 89
ABB Drives profile - Enhanced . . . . . . . . . . . . . . . . . . . . . . 90
Transparent 16-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Transparent 32-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
9. Modbus/TCP – Diagnostics
LED indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Internal error code registers . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8 Table of contents
10. EtherNet/IP – Start-up
What this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Drive configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
EtherNet/IP connection configuration . . . . . . . . . . . . . . . . 106
(group 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
(group 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
(group 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Control locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Starting up ACS355 drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Speed control using the ODVA AC/DC drive profile,
Extended speed control assembly . . . . . . . . . . . . . . . . 124
Starting up ACSM1 drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Parameter setting examples – ACSM1 . . . . . . . . . . . . . . . 128
Starting up ACS850 and ACQ810 drives . . . . . . . . . . . . . . . . . 131
Parameter setting examples – ACS850 and ACQ810 . . . . 132
Configuring the client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Select protocol/profile . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Select output and input assembly instances . . . . . . . . 139
Select connection method . . . . . . . . . . . . . . . . . . . . . . 141
EDS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Configuring an Allen-Bradley® PLC . . . . . . . . . . . . . . . . . 143
Table of contents 9
11. EtherNet/IP – Communication profiles

Communication profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
ODVA AC/DC drive profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
ODVA output attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Run Forward & Run Reverse (Control supervisor
object) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Fault Reset (Control supervisor object) . . . . . . . . . . . . 152
Net Ctrl (Control supervisor object) . . . . . . . . . . . . . . . 152
Net Ref (AC/DC drive object) . . . . . . . . . . . . . . . . . . . . 152
Speed Reference (AC/DC drive object) . . . . . . . . . . . . 153
Torque Reference (AC/DC drive object) . . . . . . . . . . . 155
ODVA input attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Faulted (Control supervisor object) . . . . . . . . . . . . . . . 156
Warning (Control supervisor object). . . . . . . . . . . . . . . 156
Running Forward (Control supervisor object) . . . . . . . 156
Running Reverse (Control supervisor object) . . . . . . . 156
Ready (Control supervisor object) . . . . . . . . . . . . . . . . 156
Ctrl From Net (Control supervisor object) . . . . . . . . . . 156
Ref From Net (AC/DC drive object) . . . . . . . . . . . . . . . 156
At Reference (AC/DC drive object) . . . . . . . . . . . . . . . 157
State (Control supervisor object) . . . . . . . . . . . . . . . . . 157
Speed Actual (AC/DC drive object) . . . . . . . . . . . . . . . 159
Torque Actual (AC/DC drive object). . . . . . . . . . . . . . . 161
ABB Drives communication profile . . . . . . . . . . . . . . . . . . . . . . 162
Control word and Status word . . . . . . . . . . . . . . . . . . . . . . 162
Control word contents . . . . . . . . . . . . . . . . . . . . . . . . . 162
Status word contents . . . . . . . . . . . . . . . . . . . . . . . . . . 165
State machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Actual values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
10 Table of contents
12. EtherNet/IP – Communication protocol

EtherNet/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Object modeling and functional profiles . . . . . . . . . . . . . . . . . . 172
Assembly objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Basic speed control assembly . . . . . . . . . . . . . . . . . . . . . . 172
Basic speed control plus drive parameters assembly . . . . 173
Extended speed control assembly . . . . . . . . . . . . . . . . . . . 175
Extended speed control plus drive parameters assembly . 176
Basic speed and torque control assembly . . . . . . . . . . . . . 179
Basic speed and torque control plus drive
parameters assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Extended speed and torque control assembly . . . . . . . . . . 182
Extended speed and torque control plus drive
ABB Drives profile with set speed assembly . . . . . . . . . . . 186
ABB Drives profile with set speed plus drive
ABB Drives profile with set speed and set
torque assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
torque plus drive parameters assembly . . . . . . . . . . . . . . . 190
Transparent 16 with one assembly . . . . . . . . . . . . . . . . . . 193
Transparent 16 with one assembly plus drive parameters 194
Transparent 16 with two assembly . . . . . . . . . . . . . . . . . . 196
Transparent 16 with two assembly plus drive parameters . 197
Transparent 32 with one assembly . . . . . . . . . . . . . . . . . . 199
Transparent 32 with one assembly plus drive parameters 200
Transparent 32 with two assembly . . . . . . . . . . . . . . . . . . 203
Transparent 32 with two assembly plus drive parameters . 204
Class objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Identity object, class 01h . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Class attributes (Instance #0). . . . . . . . . . . . . . . . . . . . 208
Instance attributes (Instance #1) . . . . . . . . . . . . . . . . . 208
Attribute explanations . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Motor data object, class 28h . . . . . . . . . . . . . . . . . . . . . . . 211
Table of contents 11
Class attributes (Instance #0) . . . . . . . . . . . . . . . . . . . 211

Control supervisor object, class 29h . . . . . . . . . . . . . . . . . 212
AC/DC-drive object, class 2Ah . . . . . . . . . . . . . . . . . . . . . 214
Drive parameter object, class 90h . . . . . . . . . . . . . . . . . . . 215
Fieldbus configuration object, class 91h . . . . . . . . . . . . . . 216
Class attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Instance #1: FENA-01/-11 configuration parameters
group A (group 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
group B (group 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
group C (group 3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
TCP/IP interface object, class F5h . . . . . . . . . . . . . . . . . . 222
Attribute explanations. . . . . . . . . . . . . . . . . . . . . . . . . . 223
Ethernet link object, class F6h . . . . . . . . . . . . . . . . . . . . . . 225
Connection object, class 05h . . . . . . . . . . . . . . . . . . . . . . . 226
Class attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Instance attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Acknowledge handler object, class 2Bh . . . . . . . . . . . . . . 229
13. EtherNet/IP – Diagnostics
LED indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
14. PROFINET IO – Start-up
Drive configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
PROFINET IO connection configuration . . . . . . . . . . . . . . 238
(group 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
(group 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
(group 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Virtual address area allocation with ACSM1 . . . . . . . . 251
Control locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Speed control using the PROFIdrive communication
profile with PPO Type 4 . . . . . . . . . . . . . . . . . . . . . . . . 254
Speed and torque control using the ABB Drives
communication profile with PPO Type 4. . . . . . . . . . . . 256
Starting up ACSM1 drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Parameter setting examples – ACSM1 . . . . . . . . . . . . . . . 260
Position control using the PROFIdrive communication
communication profile with PPO Type 4. . . . . . . . . . . . 266
Starting up ACS850 and ACQ810 drives . . . . . . . . . . . . . . . . . 269
Parameter setting examples – ACS850 and ACQ810 . . . . 270
Speed control using PROFIdrive communication
Configuring the master station . . . . . . . . . . . . . . . . . . . . . . . . . 276

Downloading the GSD file . . . . . . . . . . . . . . . . . . . . . . . . . 276
Configuring an ABB AC500 PLC . . . . . . . . . . . . . . . . . . . . 276
Configuring a Siemens SIMATIC S7 PLC . . . . . . . . . . . . . 282
15. PROFINET IO – Communication profiles
Communication profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
PROFIdrive communication profile . . . . . . . . . . . . . . . . . . . . . 293
State machine for all operating modes. . . . . . . . . . . . . 298
State machine for the positioning mode. . . . . . . . . . . . 299
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
References in speed control mode . . . . . . . . . . . . . . . 300
References in positioning mode (ACSM1 only) . . . . . . 300
Actual values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Actual values in speed control mode . . . . . . . . . . . . . . 301
Actual values in positioning mode (ACSM1 only) . . . . 301
ABB Drives communication profile . . . . . . . . . . . . . . . . . . . . . . 302
State machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Actual values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
16. PROFINET IO – Communication protocol

PROFINET IO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
PROFINET IO in FENA-01/-11 . . . . . . . . . . . . . . . . . . . . . . . . . 311
Cyclic message types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
PPO types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Standard telegram (ST) types (DP-V1) . . . . . . . . . . . . . . . 313
Parameter handling using acyclic parameter access
mechanism (DP-V1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Header and frame structures . . . . . . . . . . . . . . . . . . . . . . . 314
DP-V1 read/write request sequence . . . . . . . . . . . . . . . . . 316
Read and write blocks . . . . . . . . . . . . . . . . . . . . . . . . . 317
Data block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Function blocks for sending DP-V1 messages
(Siemens S7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Parameter data transfer examples . . . . . . . . . . . . . . . . . . . 325
Example 1a: Reading a drive parameter (array
element) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Example 1b: Reading 3 drive parameters
(multi-parameter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Example 2a: Writing a drive parameter (one array
element) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Example 2b: Writing 2 drive parameters
(multi-parameter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Example 3: Reading a PROFIdrive parameter . . . . . . . 333
Example 4: Configuring the process data written to the
drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Example 5: Determining the source of the process data
read from the drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
17. PROFINET IO – Diagnostics
LED indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
18. Technical data

FENA-01/-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Ethernet link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
19. Appendix A – PROFIdrive parameters of PROFINET
IO
PROFIdrive parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
20. Appendix B – I&M records of PROFINET IO
I&M records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Call-REQ-PDU telegram for read/write access to
I&M records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Response structure for I&M0 (Read-only) . . . . . . . . . . . . . 355
Response structure for I&M1 (Read/Write) . . . . . . . . . . . . 356
Response structure for I&M2 (Read/Write) . . . . . . . . . . . . 356
Further information
Product and service inquiries . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Product training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Providing feedback on ABB Drives manuals . . . . . . . . . . . . . . 357
Document library on the Internet . . . . . . . . . . . . . . . . . . . . . . . 357
Safety 17
Safety
What this chapter contains

The chapter presents the warning symbols used in this manual and
the safety instructions which you must follow when installing an
optional module into a drive, converter or inverter. If ignored,
physical injury or death may follow, or damage may occur to the
equipment. Read this chapter before you start the installation.
18 Safety
Use of warnings
Warnings caution you about conditions which can result in serious
injury or death and/or damage to the equipment and advise on how
to avoid the danger. The following warning symbols are used in
this manual:
Electricity warning warns of hazards from electricity

which can cause physical injury and/or damage to the
equipment.
General warning warns about conditions, other than

those caused by electricity, which can result in physical
injury and/or damage to the equipment.
Safety 19
Safety in installation
These warnings are intended for all who install an optional module
into a drive, converter or inverter.
WARNING! Ignoring the following instructions can cause

physical injury or death, or damage to the equipment.
• Only qualified electricians are allowed to install and maintain

the drive, converter or inverter!
• Disconnect the drive, converter or inverter into which the
module will be installed from all possible power sources. After
disconnecting, always wait for 5 minutes to let the intermediate
circuit capacitors discharge before you proceed.
• Always ensure by measuring with a multimeter (impedance at
least 1 Mohm) that:
• there is no voltage between the input power terminals of
the drive, converter or inverter and the ground
• there is no voltage between the output power terminals of
the drive, converter or inverter and the ground.
• Do not work on the control cables when power is applied to the
external control circuits of the drive, converter or inverter.
Externally supplied control circuits may carry dangerous
voltage.
20 Safety
About the manual 21
About the manual

This chapter introduces this manual.
Applicability
This manual applies to the FENA-01/-11 Ethernet adapter module
(+K473/+K474), SW version 0.251 and later.
Compatibility
The table below shows the compatibility of the FENA-01/-11
Ethernet adapter module with the different ABB drives:
ACS355 ACSM1 ACS850 ACQ810 ACS880
FENA-01 x
FENA-11 x x x x x
22 About the manual
The FENA-01/-11 module is compatible with Ethernet standards

IEEE 802.3 and IEEE 802.3u, and supports the protocols and
clients/masters listed in the table below.
Protocol Compatible client/master
Modbus/TCP1) All Modbus/TCP clients that support:
• Modbus Application Protocol Specification v1.1b
• Modbus Messaging on TCP/IP Implementation
Guide v1.0b
EtherNet/IP™ 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
PROFINET IO All PROFINET IO masters that support:
• GSDML file version 2.20
• PROFINET IO protocol according IEC standards
61158 and 61784
1)
Besides Modbus/TCP, FENA-01/-11 also supports Modbus over UDP.
The Modbus/TCP, EtherNet/IP and PROFINET IO protocols are

supported from FENA-01/-11 SW version 0.251 onwards.
The FENA-01/-11 module supports the Drive composer PC tool.
With Drive composer, multiple ACS880 drives with Ethernet-based
fieldbus can be commissioned and maintained simultaneously. For
more information on Drive composer, see Drive composer user’s
manual (3AUA0000094606 [English]).
Target audience
The reader is expected to have a basic knowledge of the fieldbus
interface, the Modbus/TCP, EtherNet/IP and PROFINET IO
networks, electrical fundamentals, electrical wiring practices and
how to operate the drive.
About the manual 23
Purpose of the manual

The manual provides information on installing, commissioning and
using the FENA-01/-11 Ethernet adapter module.
Related manuals
The related manuals are listed below.
Code (English)
Drive user’s manuals
ACS355 drives (0.37…22 kW, 3AUA0000066143
0.5…30 hp) user’s manual
Drive hardware manuals and

guides
ACSM1-204 regen supply modules 3AUA0000053713
(5.3 to 61 kW) hardware manual
ACSM1-04 drive modules (0.75 to 3AFE68797543
45 kW) hardware manual
ACSM1-04 drive modules (55 to 110 3AFE68912130
kW) hardware manual
ACSM1-04Lx liquid-cooled drive 3AUA0000022083
modules (55 to 160 kW) hardware
manual
ACS850-04 (0.37…45 kW) 3AUA0000045496
hardware manual
ACS850-04 (55…160 kW, 75…200 3AUA0000045487
hp) hardware manual
ACS850-04 (200…500 kW, 3AUA0000026234
250…600 hp) hardware manual
ACQ810-04 drive modules 3AUA0000055160
(0.37…45 kW, 0.5…60 hp) hardware
manual
ACQ810-04 drive modules (55 to 3AUA0000055161
160 kW, 75 to 200 hp) hardware
manual
ACQ810-04 drive modules 3AUA0000055155
(200…400 kW, 250…600 hp)
hardware manual
ACS880-01 (0.55 to 250 kW, 0.75 to 3AUA0000078093
350 hp) hardware manual
24 About the manual
Code (English)
Drive firmware manuals and
guides
ACSM1 motion control program 3AFE68848270
firmware manual
ACSM1 speed and torque control 3AFE68848261
program firmware manual
ACSM1 regen supply control 3AUA0000052174
ACS850 standard control program 3AUA0000045497
firmware manual
ACQ810 standard pump control 3AUA0000055144
ACS880 primary control program 3AUA0000085967
firmware manual
Option manuals and guides

FENA-01/-11 Ethernet adapter 3AUA0000093568
module user’s manual
You can find manuals and other product documents in PDF format
on the Internet. See section Document library on the Internet on
the inside of the back cover. For manuals not available in the
Document library, contact your local ABB representative.
About the manual 25
Before you start

It is assumed that the drive is installed and ready to operate before
you start the installation of the adapter module.
In addition to conventional installation tools, have the drive
manuals available during the installation as they contain important
information not included in this manual. The drive manuals are
referred to at various points of this manual.
Contents
The manual consists of the following chapters:
• Safety presents the safety instructions which you must follow
when installing a fieldbus adapter module.
• About the manual introduces this manual.
• Overview of the Ethernet network and the FENA-01/-11
module contains a short description of the Ethernet network
and the adapter module.
• Mechanical installation contains a delivery checklist and
instructions on mounting the adapter module.
• Electrical installation contains instructions on cabling and
connecting the module to the Ethernet network.
Modbus/TCP protocol
• Modbus/TCP – Start-up presents the steps to take during the
start-up of the drive with the adapter module and gives
information on configuring the Modbus/TCP client.
• Modbus/TCP – Communication profiles describes the
communication profiles used in the communication between
the client, the adapter module and the drive.
• Modbus/TCP – Communication protocol describes the
Modbus/TCP communication protocol for the adapter module.
• Modbus/TCP – Diagnostics explains how to trace faults with
the status LEDs on the adapter module.
26 About the manual
• EtherNet/IP – Start-up presents the steps to take during the
examples of configuring the EtherNet/IP client.
• EtherNet/IP – Communication profiles describes the
the client, the adapter module and the drive.
• EtherNet/IP – Communication protocol describes the
EtherNet/IP communication protocol for the adapter module.
• EtherNet/IP – Diagnostics explains how to trace faults with the
status LEDs on the adapter module.
• PROFINET IO – Start-up presents the steps to take during the
examples of configuring the PROFINET master.
• PROFINET IO – Communication profiles describes the
the master, the adapter module and the drive.
• PROFINET IO – Communication protocol describes the
PROFINET IO communication protocol for the adapter module.
• PROFINET IO – Diagnostics explains how to trace faults with
the status LEDs on the adapter module.
• Technical data contains the technical data of the adapter

module and the Ethernet link.
• Appendix A – PROFIdrive parameters of PROFINET IO
contains the PROFIdrive profile parameters of the PROFINET
IO protocol.
• Appendix B – I&M records of PROFINET IO contains the
telegram and response structures for the Identification &
Maintenance records of the PROFINET IO protocol.
About the manual 27
Terms and abbreviations used in this manual
General terms and abbreviations

Term Explanation
Communication module Communication module is a name for a device
(eg, a fieldbus adapter) through which the drive
is connected to an external communication
network (eg, a fieldbus). The communication
with the module is activated with a drive
parameter.
Command word See Control word.
Control word 16-bit word from master to slave with bit-coded
control signals (sometimes called the
Command word).
FENA-01/-11 Ethernet One of the optional fieldbus adapter modules
adapter module available for ABB drives. FENA-01/-11 is a
device through which an ABB drive is
connected to an Ethernet network.
MAC ID Every node on an Ethernet network has to have
a unique identifier. This node number is called
MAC ID (Media Access Control ID).
Parameter Operating instruction for the drive. Parameters
can be read and programmed using the drive
control panel, drive PC tools or through the
adapter module.
Profile Adaptation of the protocol for certain application
field, for example, drives.
In this manual, drive-internal profiles (eg, DCU
or FBA) are called native profiles.
Status word 16-bit word from slave to master with bit-coded
status messages.
28 About the manual
Abbreviation Explanation
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.
EMC Electromagnetic compatibility
FBA Fieldbus adapter
LSB Least significant bit
MSB Most significant bit
PLC Programmable logic controller
Modbus/TCP terms and abbreviations

Term Explanation
Exception code If an error related to the requested Modbus
function occurs, the data field contains an
exception code that the server application can
use to determine the next action to be taken.
Function code The second byte sent by the client. The function
indicates to the server what kind of action to
perform.
Holding register Holds data that will be later executed by an
application program.
EtherNet/IP terms and abbreviations

Term Explanation
EDS file The Electronic Data Sheet (EDS) file identifies
the properties of the device to the EtherNet/IP
client. Each type of drive and application
program requires its own EDS file.
Input 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.
About the manual 29
Term Explanation
I/O Assembly selection Smart networked devices (like FENA-01/-11)
can produce and/or consume more than one I/O
value. Typically, they will produce and/or
consume one or more I/O value, as well as
status and diagnostic information. Each piece of
data communicated by a device is represented
by an attribute of one of the device’s internal
objects.
Communicating multiple pieces of data
(attributes) across a single I/O connection
requires that the attributes be grouped or
assembled together into a single block.
ODVA™ ODVA stands for Open DeviceNet Vendor
Association. ODVA is an independent
organization that promotes interoperativity
between different manufacturers’ EtherNet/IP
products. ABB is an Associate Member at
ODVA.
Output 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).
PROFINET IO terms and abbreviations

Term Explanation
Acyclic communication Communication in which messages are sent
only once on request
Array Parameter consisting of data fields of equal
data type
Cyclic communication Communication in which parameter/process
data objects are sent cyclically at pre-defined
intervals
DCP Discovery Control Protocol. A protocol that
allows the master controller to find every
PROFINET IO device on a subnet.
Fault Event that leads to tripping of the device
30 About the manual
Term Explanation
GSD file ASCII-format device description file in a
specified form. Each different slave type on the
PROFINET IO network needs to have its own
GSD file. GSD files in PROFINET IO are written
in GSDML.
Index Access reference for objects in PROFINET IO
I/O controller Control system with bus initiative. In PROFINET
IO terminology, I/O controllers are also called
master stations.
Master Control system with bus initiative. In PROFINET
IO terminology, master stations are also called
active stations.
Name Symbolic name of a parameter
Parameter Value that can be accessed as an object, eg,
variable, constant, signal
Parameter number Parameter address
Parameter/Process Special object that contains parameter and
process
Data object Special object that contains parameter and
process data
Process data Data that contains Control word and reference
value or Status word and actual value. May also
contain other (user-definable) control
information.
Slave Passive bus participant. In PROFINET IO
terminology, slave stations (or slaves) are also
called passive stations. Also referred to as
node.
Warning Signal caused by an existing alarm which does
not lead to tripping of the device
About the manual 31
The text in italics is the original German term.

ACT Actual value
Istwert
DAP Device access point
DP Decentralised Periphery
Dezentrale Peripherie
DP-V0 PROFINET IO extension to the EN 50170
standard, providing the basic functionality of DP,
including cyclic data exchange
DP-V1 PROFINET IO extension to the EN 50170
standard, including, eg, acyclic data exchange
GSDML General Station Description Markup Language
ISW See ACT.
MAP Module access point
PAP Parameter access point
PD Process data
Prozessdaten
PKE Parameter identification
Parameter-Kennung
PKW Parameter identification value
Parameter-Kennung-Wert
PNU Parameter number
Parameternummer
PPO Parameter/Process data object
Parameter-/Prozessdaten-Objekt
PWE Parameter value
Parameter-Wert
PZD See PD.
PZDO Process data object
Prozessdatenobjekt
SAP Service access point
32 About the manual
SOW Reference
Sollwert
STW Control word
Steuerwort
ZSW Status word
Zustandswort
Overview of the Ethernet network and the FENA-01/-11 module 33
Overview of the Ethernet

network and the FENA-01/-11
module

This chapter contains a short description of the Ethernet network
and the FENA-01/-11 Ethernet adapter module.
Ethernet network
Ethernet standards support a variety of physical media (coaxial
cable, twisted pair, fiber optics) and topologies (bus and star). The
FENA-01/-11 Ethernet adapter module supports twisted pair as the
physical media in a star topology.
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 less than 100 meters,
including media within patch panels. For more information, see
chapter Technical data.
34 Overview of the Ethernet network and the FENA-01/-11 module
Example topology of the Ethernet link

An example of an allowable topology is shown below.
Other slave ABB drive Other slave

device device
Switch or router
FENA-01/-11 Ethernet adapter module

The FENA-01/-11 Ethernet adapter module is an optional device
for ABB drives which enables the connection of the drive to an
Ethernet 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.
The protocols used to access these functionalities over Ethernet
are described in chapters:
• Modbus/TCP – Communication protocol
• EtherNet/IP – Communication protocol
• PROFINET IO – Communication protocol.
Overview of the Ethernet network and the FENA-01/-11 module 35
The FENA-01/-11 module supports 10 Mbit/s and 100 Mbit/s data

transfer rates and automatically detects the data transfer rate used
in the network.
Note: PROFINET IO uses only 100 Mbit/s in the Full duplex mode.
The adapter module is mounted into an option slot on the motor
control board of the drive. See the drive manuals for module
placement options.
Layout of the adapter module
Diagnostic LEDs
(See chapters:
• Modbus/TCP – Diagnostics
• EtherNet/IP – Diagnostics
• PROFINET IO – Diagnostics)
Ethernet connector X1
(See chapter Electrical
installation)
Mounting screw
36 Overview of the Ethernet network and the FENA-01/-11 module
Mechanical installation 37
Mechanical installation

This chapter contains a delivery checklist and instructions on
mounting the adapter module.
WARNING! Follow the safety instructions given in this

manual and the drive documentation.
Delivery check
The option package for the adapter module contains:
• Ethernet adapter module, type FENA-01/-11
• this manual.
38 Mechanical installation
Mounting the adapter module

The adapter module is to be inserted into its specific position in the
drive. The module is held in place with plastic pins and one screw.
The screw also provides the electrical connection between the
module and drive frame for cable shield termination.
When the module is installed, the signal and power connection to
the drive is made through a 20-pin connector. (All drives do not use
all the available signals so the connector on the drive may have
fewer pins.)
Mounting procedure:
1. Insert the module carefully into its position on the drive.
2. Fasten the screw.
Note: It is essential to install the screw properly to fulfill the EMC
requirements and to ensure the proper operation of the module.
For more information on mounting, see the drive manuals.
Electrical installation 39
Electrical installation

This chapter contains:
• general cabling instructions
• instructions on connecting the module to the Ethernet network.
WARNING! Before installation, switch off the drive power

supply. Wait five minutes to ensure that the capacitor bank
of the drive is discharged. Switch off all dangerous
voltages connected from external control circuits to the inputs and
outputs of the drive.
General cabling instructions

• Arrange the bus cables as far away from the motor cables as
possible.
• Avoid parallel runs.
• Use bushings at cable entries.
40 Electrical installation
Connecting the module to the Ethernet network

Connect the network cable to the RJ45 connector (X1) on the
adapter module. The cable can be CAT5 or higher, and type UTP,
FTP or STP.When CAT5 FTP or STP is used, the cable shield is
connected through an RC network to the drive frame.
In FENA-01, it is possible to change this connection by using
jumper J1 located next to the X1 connector. The jumper connects
the cable shield internally either:
• directly to the drive frame (position 1-2) or
• by default, through an RC network to drive frame (position
2-3).
The figure below shows the location of jumper pin 1 on the module.
J1
X1
Pin 1
41
Modbus/TCP protocol
Modbus/TCP – Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Modbus/TCP – Communication profiles . . . . . . . . . . . . . . . . . . . 75
Modbus/TCP – Communication protocol . . . . . . . . . . . . . . . . . . 85
Modbus/TCP – Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
42
Modbus/TCP – Start-up 43
Modbus/TCP – Start-up

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

44 Modbus/TCP – Start-up
Drive configuration
The following information applies to all drive types compatible with
the adapter module, unless otherwise stated.
Modbus/TCP connection configuration

After the adapter module has been mechanically and electrically
installed according to the instructions in chapters Mechanical
installation and Electrical installation, the drive must be prepared
for communication with the module.
The detailed procedure of activating the module for Modbus/TCP
communication with the drive depends on the drive type. Normally,
a parameter must be adjusted to activate the communication. See
the drive-specific start-up sections starting on page 57.
Once communication between the drive and the adapter module
has been established, several configuration parameters are copied
to the drive. These parameters are shown in the tables below and
must be checked first and adjusted where necessary.
Note that not all drives display descriptive names for the
configuration parameters. To help you identify the parameters in
different drives, the names displayed by each drive are given in
grey boxes in the tables.
Note: The new settings take effect only when the module is
powered up the next time or when the fieldbus adapter refresh
parameter is activated.
FENA-01/-11 configuration parameters – group A (group 1)

Note: The actual parameter group number depends on the drive
type. Group A (group 1) corresponds to:
• parameter group 51 in ACS355, ACSM1, ACS850 and
ACQ810
• parameter group 51 in ACS880 if the adapter is installed as
fieldbus adapter A or group 54 if the adapter is installed as
fieldbus adapter B.
No. Name/Value Description Default
01 FBA TYPE Read-only. Shows the fieldbus adapter type as 128 =
detected by the drive. The value cannot be ETHER-
adjusted by the user. NET
If the value is 0 = None, the communication
between the drive and the module has not
been established.
02 PROTOCOL/ Selects the application protocol and 0=
PROFILE communication profile for the network MB/TCP
connection. ABB C
ACS355: The selections available for Modbus
FB PAR 2 communication are listed below.
ACSM1:
FBA PAR2
ACS850/ACQ810:
FBA par2
ACS880:
Protocol/Profile
0 = MB/TCP ABB C Modbus/TCP: ABB Drives profile - Classic
1 = MB/TCP ABB E Modbus/TCP: ABB Drives profile - Enhanced
2 = MB/TCP T16 Modbus/TCP: Transparent 16-bit profile
3 = MB/TCP T32 Modbus/TCP: Transparent 32-bit profile
4 = MB/UDP ABB C Modbus over UDP: ABB Drives profile - Classic
5 = MB/UDP ABB E Modbus over UDP: ABB Drives profile -
Enhanced
6 = MB/UDP T16 Modbus over UDP: Transparent 16-bit profile
7 = MB/UDP T32 Modbus over UDP: Transparent 32-bit profile

03 COMM RATE Sets the bit rate for the Ethernet interface. 0 = Auto
ACS355:
FB PAR 3
ACSM1:
FBA PAR3
ACS850/ACQ810:
FBA par3
ACS880:
Commrate
0 = Auto Autonegotiate
1 = 100 Mbps FD 100 Mbps, full duplex
2 = 100 Mbps HD 100 Mbps, half duplex
04 IP Sets the method for configuring the IP address, 1 = Dyn
CONFIGURATION subnet mask and gateway address for the IP DHCP
module.
ACS355:
FB PAR 4
ACSM1:
FBA PAR4
ACS850/ACQ810:
FBA par4
ACS880:
IP configuration
0 = Static IP Configuration will be obtained from parameters
05…13.
1 = Dyn IP DHCP Configuration will be obtained via DHCP.
05 IP ADDRESS 1 An IP address is assigned to each IP node on a 0
network. An IP address is a 32-bit number that
ACS355:
is typically represented in “dotted decimal”
FB PAR 5
notation consisting of four decimal integers, on
ACSM1: the range 0…255, separated by periods. Each
FBA PAR5 integer represents the value of one octet (8-
ACS850/ACQ810: bits) in the IP address. Parameters 05...08
FBA par5 define the four octets of the IP address.
ACS880:
IP address 1
0…255 IP address
… … … …

08 IP ADDRESS 4 See parameter 05 IP ADDRESS 1. 0
ACS355:
FB PAR 8
ACSM1:
FBA PAR8
ACS850/ACQ810:
FBA par8
ACS880:
IP address 4
0…255 IP address
09 SUBNET CIDR Subnet masks are used for splitting networks 0
into smaller networks called subnets. A subnet
ACS355:
mask is a 32-bit binary number that is used to
FB PAR 9
split the IP address into a network address and
ACSM1: host address.
FBA PAR9 Subnet masks are typically represented in
ACS850/ACQ810: either dotted decimal notation or the more
FBA par9 compact CIDR notation, as shown in the table
ACS880: below.
Subnet CIDR
Dotted decimal CIDR Dotted decimal CIDR

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


10 GW ADDRESS 1 IP gateways connect individual physical IP 0
subnets into a unified IP network. When an IP
ACS355: node needs to communicate with an IP node
FB PAR 10 on another subnet, the IP node sends the data
ACSM1: to the IP gateway for forwarding. Parameters
FBA PAR10 10…13 define the four octets of the gateway
ACS850/ACQ810: address.
FBA par10
ACS880:
GW address 1
0…255 GW address
… … … …
13 GW ADDRESS 4 See parameter 10 GW ADDRESS 1. 0
ACS355:
FB PAR 13
ACSM1:
FBA PAR13
ACS850/ACQ810:
FBA par13
ACS880:
GW address 4
0…255 GW address
14 Reserved These parameters are not used by the adapter N/A
… module when the module is configured for
18 Modbus/TCP.

19 T16 SCALE Defines the reference multiplier/actual value 99
divisor for the adapter module. The parameter
ACS355: is effective only when the Transparent 16
FB PAR 19 profile is selected AND the drive is using the
ACSM1: native communication profile (eg, DCU or FBA)
FBA PAR19 and a 16-bit transparent Reference 1/Actual
ACS850/ACQ810: value 1.
FBA par19 With an ACS355 drive, the speed reference
from the PLC is multiplied by the value of this
ACS880:
parameter plus one. For example, if the
T16 scale
parameter has a value of 99 and a reference of
1000 given by the master, the reference will be
multiplied by 99 +1 = 100 and forwarded to the
drive as 100000. According to the DCU profile,
this value is interpreted as a reference of
100 rpm in the drive.
With ACSM1, ACS850, ACQ810 and ACS880,
setting this parameter to 65535 provides the
approximation of 1 = 1 rpm.
0…65535 Reference multiplier/actual value divisor
20 MODBUS/TCP The Modbus protocol does not specify a 20
TIMEOUT timeout mechanism for the application layer. A
timeout mechanism may be desired when
ACS355: controlling a drive, so a method is provided for
FB PAR 20 this purpose.
ACSM1: • If the parameter value is zero, this feature is
FBA PAR20 disabled.
ACS850/ACQ810: • If the parameter value is non-zero, the
FBA par20 timeout is:
ACS880: (Modbus/TCP Timeout Value) * 100 milliseconds
Timeout time
For example, a Modbus/TCP timeout value of
22 would result in a timeout of:
22 * 100 milliseconds = 2.2 seconds
In the event of a Modbus/TCP timeout, the

adapter module will signal the drive that
communication with the client has been lost.
The drive configuration will determine how it
will respond.
Example: if the Modbus/TCP timeout is
configured for 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.
0…65535 Modbus/TCP timeout value

21 TIMEOUT MODE Selects which Modbus/TCP register accesses 2=
reset the timeout counter. Control
ACS355: RW
FB PAR 21
ACSM1:
FBA PAR21
ACS850/ACQ810:
FBA par21
ACS880:
Timeout mode
0 = None The Modbus/TCP timeout feature is disabled.
1 = Any message The timeout counter is reset when any Modbus
register of the drive is accessed.
2 = Control RW The timeout counter is reset when the drive
receives either a new Control word or new
reference value (REF1 or REF2) from the
Modbus/TCP client.
22 WORD ORDER Selects in which order the 16-bit registers of 1 = HILO
32-bit parameters are transferred.
ACS355:
For each register (16-bit), the first byte contains
FB PAR 22
the high order byte and the second byte
ACSM1: contains the low order byte.
FBA PAR22
ACS850/ACQ810:
FBA par22
ACS880:
Word order
0 = LOHI The first register contains the low order word
and the second register contains the high order
word.
1 = HILO The first register contains the high order word
and the second register contains the low order
word.
26 Modbus/TCP.

27 FBA PAR Validates any changed adapter module 0 = Done
REFRESH configuration parameter settings. After
refreshing, the value reverts automatically to
ACS355/ACSM1: 0 = Done.
FBA PAR Note: This parameter cannot be changed while
REFRESH the drive is running.
ACS850/ACQ810/
ACS880:
FBA par refresh
0 = Done Refreshing done
1 = Refresh / Refreshing
Configure
28 PAR TABLE VER Read-only. Displays the parameter table N/A
revision of the fieldbus adapter module
ACS355: mapping file stored in the memory of the drive.
FILE CPI FW REV In format xyz, where
ACSM1: x = major revision number
PAR TABLE VER y = minor revision number
z = correction number
ACS850/ACQ810/
OR
ACS880:
in format axyz, where
Par table ver a = major revision number
xy = minor revision numbers
z = correction number or letter.
Parameter table revision
29 DRIVE TYPE Read-only. Displays the drive type code of the N/A
CODE fieldbus adapter module mapping file stored in
the memory of the drive.
ACS355:
FILE CONFIG ID
ACSM1:
DRIVE TYPE
CODE
ACS850/ACQ810/
ACS880:
Drive type code
Drive type code of the fieldbus adapter module
mapping file

30 MAPPING FILE Read-only. Displays the fieldbus adapter N/A
VER module mapping file revision stored in the
memory of the drive in decimal format.
ACS355:
FILE CONFIG REV
ACSM1:
MAPPING FILE
VER
ACS850/ACQ810/
ACS880:
Mapping file ver
Mapping file revision
31 D2FBA COMM STA Read-only. Displays the status of the fieldbus 0 = Idle
adapter module communication. OR
ACS355: Note: The value names may vary by drive. 4 = Off-
FBA STATUS line
ACSM1:
D2FBA COMM STA
ACS850/ACQ810/
ACS880:
D2FBA comm sta
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 COMM SW Read-only. Displays the common program N/A
VER revision of the adapter module in format axyz,
where:
ACS355: a = major revision number
FBA CPI FW REV xy = minor revision numbers
ACSM1: z = correction number or letter.
FBA COMM SW
VER
ACS850/ACQ810:
FBA comm sw ver
ACS880:
FBA comm SW ver
Common program version of the adapter
module
33 FBA APPL SW Read-only. Displays the application program N/A
where:
FBA APPL FW xy = minor revision numbers
REV z = correction number or letter.
ACSM1:
FBA APPL SW
VER
ACS850/ACQ810:
FBA appl sw ver
ACS880:
FBA appl SW ver
Application program revision of the adapter
module
FENA-01/-11 configuration parameters – group B (group 2)

type. Group B (group 2) corresponds to:
• parameter group 55 in ACS355
• parameter group 53 in ACSM1, ACS850 and ACQ810
fieldbus adapter B.
No.1) Name/Value Description Default
01 DATA OUT 1 Selects the drive parameter address into which 0 = None
(client to drive) the value of the DATA OUT 1 register is written
(from the client to the server). The Modbus
ACS355: register address maps are explained in chapter
FBA DATA OUT 1 Modbus/TCP – Communication protocol.
ACSM1: The content is defined by a decimal number in
FBA DATA OUT1 the range of 0 to 9999 as follows:
ACS850/ACQ810/
0 Not used
ACS880:
FBA data out1 1…99 Virtual address area of drive control.
Not used when the Modbus/TCP
protocol is used.
101… Parameter area of the drive
9999
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).
Other Path to parameter area selection (ACS880
(ACS880 only) only)
02… DATA OUT 2 … See parameter 01 DATA OUT 1. 0 = None
12 DATA OUT 12
1) The number of parameters in this group may vary by drive type and drive firmware.
FENA-01/-11 configuration parameters – group C (group 3)

type. Group C (group 3) corresponds to:
fieldbus adapter B.
01 DATA IN 1 Selects the drive parameter address from 0 = None
(drive to client) which the data is read to the DATA IN 1
register (from the server to the client). The
ACS355: Modbus register address maps are explained
FBA DATA IN 1 in chapter Modbus/TCP – Communication
ACSM1: protocol.
FBA DATA IN1 The content is defined by a decimal number in
ACS850/ACQ810/ the range of 0 to 9999 as follows:
ACS880:
0 Not used
FBA data in1
1…99 Virtual address area of drive
control. Not used when the
Modbus/TCP protocol is used.
9999
0 = None Not used

(ACS880 only) only)
02… DATA IN 2 … See parameter 01 DATA IN 1. 0 = None
12 DATA IN 12
Control locations
ABB drives can receive control information from multiple sources
including digital inputs, analog inputs, the drive control panel and a
communication module (for example, the adapter module). ABB
drives allow the user to separately determine the source for each
type of control information (Start, Stop, Direction, Reference, Fault
reset, etc.).
In order to give the fieldbus client the most complete control over
the drive, the communication module must be selected as the
source of this information. The drive-specific parameter setting
examples below contain the drive control parameters needed in
the examples. For a complete parameter list, see the drive
documentation.
Starting up ACS355 drives

1. Power up the drive.
2. Enable the communication between the adapter module and
the drive by setting parameter 9802 COMM PROT SEL to EXT
FBA.
3. Set the FENA-01/-11 configuration parameters in group 51.
• Select the communication protocol and profile with
parameter 5102 and configure the network settings with
parameters 5103…5113.
• With parameters 5120 and 5121, select how the adapter
module detects fieldbus communication breaks.
4. With parameter 3018 COMM FAULT FUNC, select how the
drive reacts to a fieldbus communication break.
5. With parameter 3019 COMM FAULT TIME, define the time
between communication break detection and the selected
action.
6. Define the process data transferred to and from the drive in
parameter groups 54 and 55.
Note: The adapter module assigns the Control word, Status
word, references 1…2 and actual values 1…2 automatically to
Modbus registers. Process data groups are not available for
the ABB Drives - Classic communication profile.
7. Validate the settings made in parameter groups 51, 54 and 55
by setting parameter 5127 FBA PAR REFRESH to REFRESH.
8. Set the relevant drive control parameters to control the drive
according to the application. Examples of appropriate values
are shown in the tables below.
Parameter setting examples – ACS355

Enhanced communication profile
This example shows how to configure a speed and torque control
application that uses the ABB Drives - Enhanced profile. In
addition, some application-specific data is added to the
communication.
The start/stop commands and reference are according to the ABB
Drives profile. For more information, see section ABB Drives
communication profile on page 77.
When Reference 1 (REF1) is used, a reference value of ±20000
(decimal) corresponds to the reference set with parameter 1105
REF1 MAX in the forward and reverse directions.
(decimal) corresponds to the reference set with parameter 1108
The minimum and maximum 16-bit integer values that can be
given through the fieldbus are -32768 and 32767 respectively.
Output data Modbus Input data Modbus
register register
Control word 400001 Status word 400051
Speed reference 400002 Speed actual value 400052
Torque reference 400003 Torque actual value 400053
Acceleration time1) 400004 Power1) 400054
Deceleration time1) 400005 DC bus voltage1) 400055
1) Example
The table below gives the recommended drive parameter settings.

Drive parameter Setting for ACS355 Description
drives
9802 COMM PROT SEL 4 = EXT FBA Enables communication
between the drive and the
fieldbus adapter module.
5101 FBA TYPE ETHERNET1) Displays the type of the fieldbus

adapter module.

drives
5102 FB PAR 2 1 (= MB/TCP ABB E) Selects the Modbus/TCP
(PROTOCOL/PROFILE) protocol and the ABB Drives -
Enhanced profile.
5103 FB PAR 3 0 (= Auto)2) Ethernet communication rate is
(COMMRATE) negotiated automatically by the
device.
5104 FB PAR 4 0 (= Static IP) Configuration will be obtained
(IP CONFIGURATION) from parameters 05…13.
5105 FB PAR 5 1922) First part of the IP address
(IP ADDRESS 1)
5106 FB PAR 6 1682) Second part of the IP address
(IP ADDRESS 2)
5107 FB PAR 7 02) Third part of the IP address
(IP ADDRESS 3)
5108 FB PAR 8 162) Last part of the IP address
(IP ADDRESS 4)
5109 FBA PAR 9 242) Sets the network mask as
(SUBNET CIDR) 255.255.255.0, allowing access
only to the last subnet.
5120 FB PAR 20 102) Sets the communication timeout
(MODBUS/TCP as 1 second.
TIMEOUT)
5121 FB PAR 21 2 (= Control RW)2) The timeout feature monitors the
(TIMEOUT MODE) updating of the Control word and
Reference 1.
3018 COMM FAULT 1 = FAULT2) Enables fieldbus communication

FUNC fault monitoring.
3019 COMM FAULT TIME 3.0 s2) Defines the fieldbus
communication break
supervision time.
5401 FBA DATA IN 1 1062) Power

5402 FBA DATA IN 2 1072) DC bus voltage
5501 FBA DATA OUT 1 22022) Acceleration time
5502 FBA DATA OUT 2 22032) Deceleration time
5127 FBA PAR REFRESH 1 = REFRESH Validates the FENA-01/-11

configuration parameter
settings.

drives
9904 MOTOR CTRL 2 = VECTOR: TORQ Selects the vector control mode
MODE as the motor control mode.
1001 EXT1 COMMANDS 10 = COMM Selects the fieldbus interface as
the source of the start and stop
commands for external control
location 1.
location 2.
1102 EXT1/EXT2 SEL 8 = COMM Enables external control location
1/2 selection through the
fieldbus.
1103 REF1 SELECT 8 = COMM Selects the fieldbus reference 1
as the source for speed
reference 1.
reference 1.
1601 RUN ENABLE 7 = COMM Selects the fieldbus interface as
the source for the inverted Run
enable signal (Run disable).
1604 FAULT RESET SEL 8 = COMM Selects the fieldbus interface as
the source for the fault reset
signal.
1) Read-only or automatically detected/set
2) Example
The start sequence for the parameter example above is given

below.
Control word:
• 47Eh (1150 decimal) –> READY TO SWITCH ON
• 47Fh (1151 decimal) –> OPERATING (Speed mode)
• C7Fh (3199 decimal) –> OPERATING (Torque mode)
Starting up ACSM1 drives

the drive by setting parameter 50.01 FBA ENABLE to Enable.
3. With parameter 50.02 COMM LOSS FUNC, select how the
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 COMM LOSS T OUT, define the time
action.
5. Select application-specific values for parameters
50.04…50.11. Examples of appropriate values are shown in
the tables below.
6. Set the FENA-11 configuration parameters in group 51.
parameter 51.02 and configure the network settings with
parameters 51.03…51.13.
• With parameters 51.20 and 51.21, select how the adapter

Modbus registers. Process data groups are not available in the
ABB Drives - Classic communication profile.
by setting parameter 51.27 FBA PAR REFRESH to REFRESH.
Parameter setting examples – ACSM1

Enhanced communication profile
application that uses the ABB Drives - Enhanced profile. In
addition, some application-specific data is added to the
communication.
(4E20h) corresponds to the reference set with parameter 25.02
SPEED SCALING in the forward and reverse directions.
(2710h) corresponds to the reference set with parameter 32.04
TORQUE REF 1 MAX in the forward and reverse directions.

register register
Torque reference 400003 Torque actual value 400053
400005 400055
400007 400057
1)
Example

Drive parameter Setting for ACSM1 Description
drives
50.01 FBA ENABLE Enable Enables communication
50.02 COMM LOSS FUNC Fault2) Enables fieldbus communication
fault monitoring.
50.03 COMM LOSS T OUT 3.0 s2) Defines the fieldbus
communication break
supervision time.
50.04 FBA REF1 Speed Selects the fieldbus reference 1
MODESEL scaling.
50.05 FBA REF2 Torque Selects the fieldbus reference 2
MODESEL scaling.
51.01 FBA TYPE ETHERNET1) Displays the type of the fieldbus

adapter module.
51.02 FBA PAR2 1 (= MB/TCP ABB E) Selects the Modbus/TCP
(PROTOCOL/PROFILE) protocol and the ABB Drives -
Enhanced profile.
51.03 FBA PAR3 0 (= Auto)2) Ethernet communication rate is
device.
51.04 FBA PAR4 0 (= Static IP)2) Configuration will be obtained

drives
51.05 FBA PAR5 1922) First part of the IP address
(IP ADDRESS 1)
51.06 FBA PAR6 1682) Second part of the IP address
(IP ADDRESS 2)
51.07 FBA PAR7 02) Third part of the IP address
(IP ADDRESS 3)
51.08 FBA PAR8 162) Last part of the IP address
(IP ADDRESS 4)
51.09 FBA PAR9 242) Sets the network mask as
51.20 FBA PAR20 102) Sets the communication timeout
(MODBUS/TCP TIMEOUT) as 1 second.
51.21 FBA PAR21 2 (= Control RW)2) The timeout feature monitors the
TIMEOUT MODE) updating of the Control word and
Reference 1.
52.01 FBA DATA IN1 1222) Power

52.03 FBA DATA IN3 1072) DC bus voltage
53.01 FBA DATA OUT1 25032) Acceleration time
53.03 FBA DATA OUT3 25042) Deceleration time
51.27 FBA PAR REFRESH REFRESH Validates the FENA-11

configuration parameter settings.
10.01 EXT1 START FUNC FBA Selects the fieldbus interface as

location 1.
location 2.
24.01 SPEED REF1 SEL FBA REF1 Selects the fieldbus reference 1
reference 1.
32.02 TORQ REF ADD FBA REF2 Selects the fieldbus reference 2
SEL as the source for torque
reference 1.

drives
34.01 EXT1/EXT2 SEL P.FBA MAIN CW.15 Enables external control location
1/2 selection through the fieldbus
only (bit 15 in the fieldbus
Control word).
34.03 EXT1 CTRL MODE1 Speed Selects speed control as the
control mode 1 for external
control location 1.
34.05 EXT2 CTRL MODE1 Torque Selects torque control as the
control location 2.
2) Example

below.
Control word:
Starting up ACS850 and ACQ810 drives

the drive by setting parameter 50.01 FBA enable to Enable.
3. With parameter 50.02 Comm loss func, select how the drive
reacts to a fieldbus communication break.
4. With parameter 50.03 Comm loss t out, define the time
action.
the tables below.

by setting parameter 51.27 FBA par refresh to Refresh.
Parameter setting examples – ACS850 and ACQ810

communication profile
This example shows how to configure a speed control application
that uses the ABB Drives - Enhanced profile. In addition, some
application-specific data is added to the communication.
Speed scaling in the forward and reverse directions.

register register
Reference 2 (Not 400003 Actual value 2 (Not 400053
used) used)
400005 400055
400007 400057
1) Example

Drive parameter Setting for Description
ACS850/ACQ810
drives
50.01 Fba enable Enable Enables communication between
the drive and the fieldbus adapter
module.
50.02 Comm loss func Fault2) Enables fieldbus communication
fault monitoring.
50.03 Comm loss t out 3.0 s2) Defines the fieldbus
communication break supervision
time.
50.04 Fb ref1 modesel Speed Selects the fieldbus reference 1
scaling.
51.01 FBA type Ethernet1) Displays the type of the fieldbus

adapter module.
51.02 FBA par2 1 (= MB/TCP ABB E) Selects the Modbus/TCP protocol
(PROTOCOL/ and the ABB Drives - Enhanced
PROFILE) profile.
51.03 FBA par3 0 (= Auto)2) Ethernet communication rate is
device.
51.04 FBA par4 0 (= Static IP)2) Configuration will be obtained

ACS850/ACQ810
drives
51.05 FBA par5 1922) First part of the IP address
(IP ADDRESS 1)
51.06 FBA par6 1682) Second part of the IP address
(IP ADDRESS 2)
51.07 FBA par7 02) Third part of the IP address
(IP ADDRESS 3)
51.08 FBA par8 162) Last part of the IP address
(IP ADDRESS 4)
51.09 FBA par9 242) Sets the network mask as
51.20 FBA par20 102) Sets the communication timeout
(MODBUS/TCP TIME- as 1 second.
OUT)
51.21 FBA par21 2 (= Control RW)2) The timeout feature monitors the
(TIMEOUT MODE) updating of the Control word and
Reference 1.
52.01 FBA data in1 1222) Power

52.03 FBA data in3 1072) DC bus voltage
53.01 FBA data out1 22022) Acceleration time
53.03 FBA data out3 22032) Deceleration time
51.27 FBA par refresh Refresh Validates the FENA-11

10.01 Ext1 start func FB Selects the fieldbus interface as

location 1.
21.01 Speed ref1 sel FBA ref1 Selects the fieldbus reference 1
(ACS850) as the source for speed reference
21.01 Speed ref sel FBA ref1 1.
(ACQ810)
2) Example

below.
Control word:

the drive by setting parameter 50.01 FBA A Enable to Enable.
3. With parameter 50.02 FBA A comm loss func, select how the
4. With parameter 50.03 FBA A comm loss t out, define the time
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.
parameter 51.02 Protocol/Profile and configure the
network settings with parameters 51.03…51.13.

8. Save the valid parameter values to permanent memory by
setting parameter 96.07 Param save to Save.
by setting parameter 51.27 FBA par refresh to Configure.

communication profile
that uses the ABB Drives - Enhanced profile. In addition, some
Speed scaling in the forward and reverse directions.

register register
Reference 2 (Not 400003 Actual value 2 (Not 400053
used) used)
400005 400055
400007 400057
1) Example

drives
50.01 FBA A Enable 1 = Enable Enables communication between
module.
50.02 FBA A comm loss 1 = Fault2) Enables fieldbus A
func communication fault monitoring.
50.03 FBA A comm loss t 3.0 s2) Defines the fieldbus A
out communication break supervision
time.
50.04 FBA A ref1 type 4 = Speed Selects the fieldbus A reference 1
type and scaling.
51.01 FBA type 128 = ETHERNET1) Displays the type of the fieldbus
adapter module.
51.02 Protocol/Profile 1 = MB/TCP ABB E Selects the Modbus/TCP protocol
and the ABB Drives - Enhanced
profile.
51.03 Commrate 0 = Auto2) Ethernet communication rate is
negotiated automatically by the
device.
51.04 IP configuration 0 = Static IP2) Configuration will be obtained
from parameters 05…13.
51.05 IP address 1 1922) First part of the IP address

drives
51.06 IP address 2 1682) Second part of the IP address
51.07 IP address 3 02) Third part of the IP address
51.08 IP address 4 162) Last part of the IP address
51.09 Subnet CIDR 242) Sets the network mask as
255.255.255.0, allowing access
51.20 Timeout time 102) Sets the communication timeout
as 1 second.
51.21 Timeout mode 2 = Control RW2) The timeout feature monitors the
updating of the Control word and
Reference 1.
52.01 FBA data in1 P.1.142) Output power

52.03 FBA data in3 P.1.112) DC voltage
53.01 FBA data out1 P.23.122) Acc time 1
53.03 FBA data out3 P.23.132) Dec time 1
51.27 FBA par refresh 1 = Configure Validates the FENA-11

20.01 Ext1 commands 8 = Fieldbus A Selects the fieldbus A interface

as the source of the start and
stop commands for external
control location 1.
22.11 Speed ref1 FB A ref1 Selects the fieldbus A reference 1
selection as the source for speed reference
1.
2) Example

below.
Control word:
Client configuration
After the adapter module has been initialized by the drive, the
client must be prepared for communication with the module.
Due to the large number of different Modbus clients, specific
instructions cannot be provided here. Refer to the documentation
of your client for more information.
Modbus register maps

The Modbus register map presented by the adapter module to the
Modbus client is selected with parameter 02 PROTOCOL/
PROFILE.
For Modbus register map definitions, see chapter Modbus/TCP –
Communication protocol.
For definitions of the Control word, Status word, references and
actual values for a given communication profile, see chapter
Modbus/TCP – Communication profiles.
Modbus/TCP – Communication profiles 75
Modbus/TCP –
Communication profiles

This chapter describes the communication profiles used in the
communication between the Modbus/TCP client, the adapter
module and the drive.
Communication profiles are ways of conveying control commands
(Control word, Status word, references and actual values) between
the Modbus client and the drive.
With the FENA-01/-11 module, the Modbus/TCP network may
employ either the ABB Drives profile or one of two Transparent
modes for 16-bit and 32-bit words respectively. For the ABB Drives
profile, data is converted by the adapter module into the native
profile (eg, DCU or FBA). For the Transparent modes, no data
conversion takes place.
76 Modbus/TCP – Communication profiles
The figure below illustrates the profile selection:
Modbus/TCP FENA-01/-11 Drive

network
Profile selection:
Native
profile (eg,
ABB Drives DCU, FBA)
ABB Drives profile
Data conversion
Transparent16
Drive-specific profile1) Optional reference/

(with 16-bit words) 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 ABB Drives communication
profile. Refer to the drive manuals for details on the native 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 on page 81.
Control word contents

The table below shows the contents of the Control word for the
ABB Drives communication profile. The upper case boldface text
refers to the states shown in the state machine on page 81.
Bit Name Value STATE/Description
0 OFF1_ 1 Proceed to READY TO OPERATE.
CONTROL
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_ 1 Continue operation (OFF2 inactive).
CONTROL
0 Emergency OFF, coast to stop.
Proceed to OFF2 ACTIVE, proceed to
SWITCH-ON INHIBITED.
CONTROL
0 Emergency stop, stop within time defined
by drive parameter. Proceed to OFF3
ACTIVE; proceed to SWITCH-ON
INHIBITED.
Warning: Ensure motor and driven
machine can be stopped using this stop
mode.

3 INHIBIT_ 1 Proceed to OPERATION ENABLED.
OPERATION 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_ 1 Normal operation. Proceed to RAMP
ZERO FUNCTION GENERATOR: OUTPUT
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).
6 RAMP_IN_ 1 Normal operation. Proceed to
ZERO OPERATING.
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.
0 Continue normal operation.
8…9 Reserved.

10 REMOTE_ 1 Fieldbus control enabled.
CMD
0 Control word and reference not getting
through to the drive, except for CW bits
OFF1, OFF2 and OFF3.
11 EXT_CTRL_ 1 Select External Control Location EXT2.
LOC Effective if control location parameterized
to be selected from fieldbus.
0 Select External Control Location EXT1.
Effective if control location parameterized
12… Reserved or freely programmable control bits
15 (Not supported with ACS355)
Status word contents

The table below shows the contents of the Status word for the ABB
Drives communication profile. The upper case boldface text refers
to the states shown in the state machine on page 81.
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
0 OFF3 ACTIVE
6 SWC_ON_ 1 SWITCH-ON INHIBITED
INHIB 0 –

7 ALARM 1 Warning/Alarm
0 No warning/alarm
8 AT_ 1 OPERATING. Actual value equals reference
SETPOINT (= 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_ 1 Actual frequency or speed equals or exceeds
LIMIT supervision limit (set by drive parameter).
Valid in both directions of rotation.
0 Actual frequency or speed within supervision
limit
11 EXT_CTRL_ 1 External Control Location EXT2 selected
LOC 0 External Control Location EXT1 selected
12 EXT_RUN_ 1 External Run Enable signal received
ENABLE 0 No External Run Enable signal received
13… Reserved or freely programmable status bits
14 (Not supported with ACS355)
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.
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
OPERATION
C D
ENABLED (SW Bit2=1)
A
(CW Bit5=0) (CW=xxxx x1xx xxx1 1111)
RFG: OUTPUT
D
ENABLED
B
(CW Bit6=0) (CW=xxxx x1xx xx11 1111)
RFG: ACCELERATOR
state
ENABLED
C
(CW=xxxx x1xx x111 1111) condition
OPERATION
rising edge
(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.
including analog and digital inputs, the drive control panel and a
communication module (for example, FENA-01/-11). In order to
have the drive controlled through the fieldbus, the module must be
defined as the source for control information, for example,
reference.
Scaling
References are scaled as shown below.
Note: The values of REF1 MAX and REF2 MAX are set with drive
parameters. See the drive manuals for further information.
In ACSM1, ACS850, ACQ810 and ACS880, the speed reference
(REFx) in decimal (0…20000) corresponds to 0…100% of the
speed scaling value (as defined with a drive parameter, eg,
ACS880 parameter 46.10 Speed scaling.)
In ACS355, drive parameter REFx MIN may limit the actual
minimum reference.
Fieldbus Drive
REF2: 10000 REFx MAX / Speed scale

REF1: 20000
0 0
REF2: -10000 -(REFx MAX) / Speed scale

REF1: -20000
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.
Fieldbus Drive
ACT2: 10000 REFx MAX

ACT1: 20000
0 0
ACT2: -10000 -(REFx MAX)

ACT1: -20000
Modbus/TCP – Communication protocol 85
Modbus/TCP –
Communication protocol

This chapter describes the Modbus/TCP communication protocol
for the adapter module.
Modbus/TCP
Modbus/TCP is a variant of the Modbus family of simple, vendor
neutral communication protocols intended for supervision and
control of automation equipment. Specifically, it covers the use of
Modbus messaging over TCP connection on an IP network.
The FENA-01/-11 module acts as a Modbus/TCP server with
support for the ABB Drives and Transparent profiles. FENA-01/-11
also supports Modbus over UDP.
The supported Modbus commands are listed in section Function
codes on page 86. Two simultaneous Modbus/TCP connections
are supported, that is, two clients can be connected to the adapter
module at a time.
Further information on the Modbus/TCP protocol is available at
www.modbus.org.
86 Modbus/TCP – Communication protocol
Register addressing
The address field of Modbus Requests for accessing Holding
registers is 16 bits. This allows the Modbus protocol to support
addressing of 65536 Holding registers.
Historically, Modbus client devices used 5-digit decimal addresses
from 40001 to 49999 to represent Holding register addresses.
5-digit decimal addressing limited to 9999 the number of holding
registers that could be addressed.
Modern Modbus client devices typically provide a means to access
the full range of 65536 Modbus Holding registers. One of these
methods is to use 6-digit decimal addresses from 400001 to
465536. This manual uses 6-digit decimal addressing to represent
Modbus Holding register addresses.
Modbus client devices that are limited to 5-digit decimal
addressing may still access registers 400001 to 409999 by using
5-digit decimal addresses 40001 to 49999. Registers 410000-
465536 are inaccessible to these clients.
Function codes
The adapter module supports the Modbus function codes shown
below.
Function Name Description
code
03h Read Holding Registers Reads the contents of a
contiguous block of holding
registers in a server device.
06h Write Single Register Writes a single holding register in
a server device.
10h Write Multiple Registers Writes the contents of a
registers in a server device.
17h Read/Write Multiple Writes the contents of a
Registers contiguous block of holding
registers in a server device, then
reads the contents of a
registers (same or different than
those written) in a server device.
Function Name Description

code
2Bh/0Eh Encapsulated Interface Allows reading identification and
Transport / Read Device other information of the server.
Identification Parameter "Read Device ID code"
allows to define three access
types:
• 01: Request to get the basic
device identification (stream
access)
• 02: Request to get the regular
device identification (stream
access)
• 04: Request to get one specific
identification object (individual
access).
Encapsulated Interface Transport / Read Device

Identification
The adapter module supports the Modbus EIT/RDI objects shown
below.
Object ID Name
00h Vendor Name
01h Product Code
02h Major/Minor Revision
03h Vendor URL
04h Product Name
Exception codes
The adapter module supports the Modbus exception codes shown
below.
Exception Name Description
Code
01h ILLEGAL FUNCTION The function code received in the
query is not an allowable action for
the server.
02h ILLEGAL DATA The data address received in the
ADDRESSS query is to an allowable address
for the server.
03h ILLEGAL DATA VALUE A value contained in the query data
field is not an allowable value for
the server.
04h SLAVE DEVICE An unrecoverable error occurred
FAILURE while the server was attempting to
perform the requested action.
06h SLAVE DEVICE BUSY The server is engaged in
processing a long-duration
command. The client should
retransmit the message later when
the server is free.
Modbus is an application layer messaging protocol. It describes
how data is transferred between the client and a server, but not the
meaning of that data. Communication profiles are used to define
the meaning of the data.
ABB Drives profile - Classic

The ABB Drives profile - Classic communication profile provides
register mapped access to the control, status, reference and actual
values of the ABB Drives profile in the classic format for backward
compatibility.
Register Address1) Register Data (16-bit)
400001 ABB Drives Profile Control
400002 ABB Drives Profile Reference 1
400004 ABB Drives Profile Status
400005 ABB Drive Profile Actual 1
400101…409999 Drive Parameter Access (16-bit)
Register Address = 400000 + 100 x Group +

Index
Example for Drive Parameter 3.18

400000 + 100 x 3 + 18 = 400318
1)
6-digit register addressing (400001) is used instead of 5-digit register
addressing (40001) to describe register map. See section Register
addressing on page 86 for additional information.
ABB Drives profile - Enhanced

The ABB Drives profile - Enhanced communication profile provides
register mapped access to the control, status, reference and actual
values of the ABB Drives profile. The mapping of the registers has
been enhanced to allow writing of control and reading of status in a
single Read/Write Multiple Register request.
Register Address 1), 2) Register Data (16-bit)
400001 ABB Drives Profile Control
400004 DATA OUT 1
400005 DATA OUT 2
400006 DATA OUT 3
400007 DATA OUT 4
400008 DATA OUT 5
400009 DATA OUT 6
400010 DATA OUT 7
400011 DATA OUT 8
400012 DATA OUT 9
400013 DATA OUT 10
400014 DATA OUT 11
400015 DATA OUT 12
400051 ABB Drives Profile Status
400054 DATA IN 1
400055 DATA IN 2
400056 DATA IN 3
400057 DATA IN 4
400058 DATA IN 5
400059 DATA IN 6

400060 DATA IN 7
400061 DATA IN 8
400062 DATA IN 9
400063 DATA IN 10
400064 DATA IN 11
400065 DATA IN 12

Index

400000 + 100 x 3 + 18 = 400318
Register addressing of the 32-bit parameters

(not supported with ACS355):
420000 + 200 x Group + 2 x Index

420000 + 200 x 1 + 2 x 27 = 420254
1)
2) Register
addresses of the 32-bit parameters cannot be accessed by
using 5-digit register numbers.
Transparent 16-bit
The Transparent 16-bit communication profile provides unaltered
16-bit access to the configured drive profile.
400001 Native Drive Profile Control
400002 Native Drive Profile Reference 1
400003 Native Drive Profile Reference 2
400004 DATA OUT 1
400005 DATA OUT 2
400006 DATA OUT 3
400007 DATA OUT 4
400008 DATA OUT 5
400009 DATA OUT 6
400010 DATA OUT 7
400011 DATA OUT 8
400012 DATA OUT 9
400013 DATA OUT 10
400014 DATA OUT 11
400015 DATA OUT 12
400051 Native Drive Profile Status
400052 Native Drive Profile Actual 1
400053 Native Drive Profile Actual 2
400054 DATA IN 1
400055 DATA IN 2
400056 DATA IN 3
400057 DATA IN 4
400058 DATA IN 5
400059 DATA IN 6

400060 DATA IN 7
400061 DATA IN 8
400062 DATA IN 9
400063 DATA IN 10
400064 DATA IN 11
400065 DATA IN 12

Index

400000 + 100 x 3 + 18 = 400318

420000 + 200 x Group + 2 x Index

420000 + 200 x 1 + 2 x 27 = 420254
1)
2)
Register addresses of the 32-bit parameters cannot be accessed by
Transparent 32-bit
The Transparent 32-bit communication profile provides unaltered
32-bit access to the configured drive profile.
400001 Native Drive Profile Control - Least Significant
16-bits
400002 Native Drive Profile Control - Most Significant
16-bits
400003 Native Drive Profile Reference 1 - Least
Significant 16-bits
400004 Native Drive Profile Reference 1 - Most
Significant 16-bits
400005 Native Drive Profile Reference 2 - Least
Significant 16-bits
400006 Native Drive Profile Reference 2 - Most
Significant 16-bits
400007 DATA OUT 1
400008 DATA OUT 2
400009 DATA OUT 3
400010 DATA OUT 4
400011 DATA OUT 5
400012 DATA OUT 6
400013 DATA OUT 7
400014 DATA OUT 8
400015 DATA OUT 9
400016 DATA OUT 10
400017 DATA OUT 11
400018 DATA OUT 12
400051 Native Drive Profile Status - Least Significant 16-
bits
400052 Native Drive Profile Status - Most Significant 16-
bits
400053 Native Drive Profile Actual 1 - Least Significant
16-bits

400054 Native Drive Profile Actual 1 - Most Significant
16-bits
400055 Native Drive Profile Actual 2 - Least Significant
16-bits
400056 Native Drive Profile Actual 2 - Most Significant
16-bits
400057 DATA IN 1
400058 DATA IN 2
400059 DATA IN 3
400060 DATA IN 4
400061 DATA IN 5
400062 DATA IN 6
400063 DATA IN 7
400064 DATA IN 8
400065 DATA IN 9
400066 DATA IN 10
400067 DATA IN 11
400068 DATA IN 12


Index

400000 + 100 x 3 + 18 = 400318

420000 + 200 x Group + 2 x Index

420000 + 200 x 1 + 2 x 27 = 420254
1) 6-digit register addressing (400001) is used instead of 5-digit register
2)
Register addresses of the 32-bit parameters cannot be accessed by
Modbus/TCP – Diagnostics 97
Modbus/TCP – Diagnostics

This chapter explains how to trace faults with the status LEDs on
the adapter module when the module is used for Modbus/TCP
communication.
98 Modbus/TCP – Diagnostics
LED indications
The adapter module is equipped with three bicolor diagnostic
LEDs. The LEDs are described below.
Name Color Function

Blinking green Establishing communication to host
Green Connection to host OK
Blinking red Communication to host lost temporarily
HOST
Flashing orange, Internal file system error. The error may
alternating with be cleared by cycling drive power. If the
the MODULE error persists, contact your local ABB
flashing orange representative.
Name Color Function

Off There is no power applied to the device.
Flashing orange Device is attempting to obtain IP
configuration from the DHCP server.
Orange Device is executing Duplicate Address
Detection.
Flashing green Device is waiting for a Modbus request.
Green Device has received a Modbus request
within the Modbus/TCP Timeout period.
MODULE 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.
the HOST error persists, contact your local ABB
NETWORK Off Ethernet link is down.
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.
Internal error code registers

A Modbus query can fail in many ways in the drive. The Modbus
standard does not specify detailed error descriptions. The standard
error codes are too generic. That is why the FENA-01/-11 module
has an internal error register area.
The internal error register area is used if Modbus error code 0x04
occurs. The registers contain information about the last query. You
can figure out the reason of the failure by reading the registers.
The internal error register is cleared when a query has finished
successfully.
Address Registers (16-bit word)
(4)00090 Reset internal error registers (0 = Do nothing, 1 = Reset)
(4)00091 Function code of the failed query
(4)00092 Internal error code; see the error number.
(4)00093 Failed register
(4)00094 Last register that was written successfully
(4)00095 Last register that was read successfully
Error code Description Situation

0x00 No error Used when a Modbus query was
successful
0x02 Low or high limit Change access with a value
exceeded outside the value limits
0x03 Faulty subindex Access to an unavailable
subindex of an array parameter
0x05 Incorrect data type Change access with a value that
does not match the data type of
the parameter
0x65 General error in drive Undefined error when handling a
communication Modbus query
0x66 Timeout Timeout in drive communication
when handling a Modbus query
0x70 Read-only An attempt to write a non-zero
value to a read-only drive
parameter
Error code Description Situation

0x71 Parameter group An attempt to write to multiple
ended parameter groups
0x72 MSB is not zero An attempt to write a 16-bit
parameter with a 32-register
address and the MSB bytes are
not zero
0x73 LSB query start An attempt to access only the
LSB register of the 32-bit
parameter
0x74 MSB query end An attempt to access only the
MSB register of the 32-bit
parameter
103
EtherNet/IP – Start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

EtherNet/IP – Communication profiles . . . . . . . . . . . . . . . . . . . 149
EtherNet/IP – Communication protocol. . . . . . . . . . . . . . . . . . . 171
EtherNet/IP – Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
104
EtherNet/IP – Start-up 105
EtherNet/IP – Start-up

adapter module
adapter module
• examples of configuring the client for communication with the
adapter module.

106 EtherNet/IP – Start-up
Drive configuration
EtherNet/IP connection configuration

The detailed procedure of activating the module for EtherNet/IP

ACQ810
fieldbus adapter B.
01 FBA TYPE Read-only. Shows the fieldbus adapter type as 128 =
detected by the drive. The value cannot be ETHER-
between the drive and the module has not been
established.
02 PROTOCOL/ Selects the application protocol and 01)
PROFILE communication profile for the network
connection.
ACS355: The selections available for EtherNet/IP
ACSM1:
FBA PAR2 1)
0 = Modbus/TCP: ABB Drives profile -
ACS850/ACQ810: Classic
FBA par2
ACS880:
Protocol/Profile
100 = EIP AC/DC EtherNet/IP protocol: ODVA AC/DC drive
profile
101 = EIP ABB Pro EtherNet/IP protocol: ABB Drives profile
102 = EIP T16 EtherNet/IP protocol: Transparent 16-bit profile
103 = EIP T32 EtherNet/IP protocol: Transparent 32-bit profile

ACS355:
FB PAR 3
ACSM1:
FBA PAR3
ACS850/ACQ810:
FBA par3
ACS880:
Commrate
04 IP Sets the method for configuring the IP address, 1 = Dyn
CONFIGURATION subnet mask and gateway address for the IP DHCP
module.
ACS355:
FB PAR 4
ACSM1:
FBA PAR4
ACS850/ACQ810:
FBA par4
ACS880:
IP configuration
0 = Static IP Configuration will be obtained from parameters
05…13.
05 IP ADDRESS 1 An IP address is assigned to each IP node on a 0
network. An IP address is a 32-bit number that
ACS355:
is typically represented in “dotted decimal”
FB PAR 5
notation consisting of four decimal integers, on
ACS850/ACQ810: bits) in the IP address. Parameters 05…08
ACS880:
IP address 1
0…255 IP address
… … … …

ACS355:
FB PAR 8
ACSM1:
FBA PAR8
ACS850/ACQ810:
FBA par8
ACS880:
IP address 4
0…255 IP address
ACS355:
mask is a 32-bit binary number that is used to
FB PAR 9
split the IP address into a network address and
ACSM1: host address.
ACS880: below.
Subnet CIDR

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


ACS355: node needs to communicate with an IP node on
FB PAR 10 another subnet, the IP node sends the data to
ACSM1: the IP gateway for forwarding. Parameters
FBA par10
ACS880:
GW address 1
0…255 GW address
… … … …
ACS355:
FB PAR 13
ACSM1:
FBA PAR13
ACS850/ACQ810:
FBA par13
ACS880:
GW address 4
0…255 GW address
18 EtherNet/IP.

ACSM1: native communication profile (eg, DCU or FBA)
FBA PAR19 and a 16-bit transparent Reference 1/Actual
ACS850/ACQ810: value 1.
ACS880:
T16 scale
parameter has a value of 99 and a reference of
1000 given by the master, the reference will be
multiplied by 99 +1 = 100 and forwarded to the
drive as 100000. According to the DCU profile,
this value is interpreted as a reference of
100 rpm in the drive.

20 CONTROL The EtherNet/IP protocol specifies connection 0
TIMEOUT timeout for I/O messaging (Class 1) and
Connected explicit messaging (Class 3), but
ACS355: not Unconnected explicit messaging.
FB PAR 20 This parameter provides a timeout for
ACSM1: Unconnected explicit messaging and for
FBA PAR20 instances of Connected explicit messaging
ACS850/ACQ810: (Class 3), where the client breaks the
FBA par20 connection in between requests.
ACS880:
Control timeout
Connection type Control Timeout source

timeout
I/O messaging 0…65535 (Requested Packet Interval) X
(Class 1) (Connection Timeout Multiplier)
Note: Timeout behavior may be modified by
Watchdog Timeout Action attribute of
Connection object.
Connected 0 (Requested Packet Interval) X
explicit (Connection Timeout Multiplier)
messaging Note: Timeout behavior may be modified by
(Class 3) Watchdog Timeout Action attribute of
Connection object.
1…65534 100ms X (Control Timeout Value) since last
Control Event
65535 Never Timeout
Unconnected 0 Always Timeout
explicit Note: Control Timeout must be greater than
messaging 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
In the event of a timeout, the adapter module
will signal the drive that communication with the
client has been lost. The drive configuration will
determine how it will respond.
Example: If the timeout is configured for
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.
0…65535 Control timeout value
21 IDLE ACTION I/O connections may include a Run/Idle 0=
notification. This parameter determines the Off-line
ACS355: action the drive takes in response to an Idle
FB PAR 21 notification.
ACSM1:
FBA PAR21
ACS850/ACQ810:
FBA par21
ACS880:
Idle action
0 = Off-line In the event of an Idle notification, the adapter
module will signal the drive that communication
with the client has been lost. The drive
configuration will determine how it will respond.
Example: If the timeout is configured for
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 ODVA STOP This parameter only applies when the ODVA 0=
FUNCTION AC/DC drive profile is used. It determines how Ramp
the motor will be stopped when a stop
ACS355: command is received via EtherNet/IP.
FB PAR 22
ACSM1:
FBA PAR22
ACS850/ACQ810:
FBA par22
ACS880:
Stop function
0 = Ramp The motor decelerates along the active
deceleration ramp.
1 = Coast The motor comes to a stop by coasting.

23 ODVA SPEED This parameter only applies to the ODVA 128
SCALE AC/DC drive profile. The units of reference and
actual speeds for the ODVA AC/DC drive
ACS355: profile are given by the formula below. This
FB PAR 23 parameter does not have an effect on the ABB
ACSM1: Drives profiles.
FBA PAR23 Note: While a wide range of resolutions may be
ACS850/ACQ810: configured, the actual performance is limited to
FBA par23 the performance capabilities of the drive.
ACS880:
Speed unit = RPM × 2(-1 × ODVA speed scale value)
Speed scale
The table below shows the how the drive
ODVA speed scale parameter values
correspond to the ODVA speed scale units.
ODVA speed scale value1) Speed scale value of Unit

drive parameter2)
-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 ODVA
SPEED SCALE via AC/DC-drive object, class 2Ah. When written via the
AC/DC drive object, the new value takes effect immediately.
2) Use the speed scale value of the drive parameter when reading/writing
parameter ODVA SPEED SCALE via the drive control panel, Drive parameter
object, class 90h and Fieldbus configuration object, 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 Speed scale value of drive parameter


24 ODVA TORQUE This parameter only applies when using the 128
SCALE ODVA AC/DC drive profile. The units of
reference and actual torques for the ODVA
ACS355: AC/DC drive profile are given by the formula
FB PAR 24 below. This parameter does not have an effect
ACSM1: on the ABB Drives profiles.
FBA PAR4 Note: While a wide range of resolutions may be
ACS850/ACQ810: configured, the actual performance is limited to
FBA par24 the performance capabilities of the drive.
(N·m = Newton × Meter)
ACS880:
Torque scale
Torque unit = N·m × 2(-1 × ODVA torque scale)
The table below shows the how the drive
ODVA torque scale parameter values
correspond to the ODVA torque scale units.
ODVA torque scale value1) Torque scale value of Unit

drive parameter2)
-5 123 32 N·m
-4 124 16 N·m
-3 125 8 N·m
-2 126 4 N·m
-1 127 2 N·m
0 (default) 128 1 N·m
1 129 0.5 N·m
2 130 0.25 N·m
3 131 0.125 N·m
4 132 0.0625 N·m
5 133 0.03125 N·m
1)
Use the ODVA torque scale value when reading/writing parameter ODVA
TORQUE SCALE via AC/DC-drive object, class 2Ah. When written via the
AC/DC drive object, the new value takes effect immediately.
2)
Use the torque scale value of the drive parameter when reading/writing
parameter ODVA TORQUE SCALE via the drive control panel, Drive
parameter object, class 90h and Fieldbus configuration object, 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

26 EtherNet/IP.

ACS355/ACSM1: 0 = Done.
FBA PAR Note: This parameter cannot be changed while
REFRESH the drive is running.
ACS850/ACQ810/
ACS880:
FBA par refresh
Configure
ACS850/ACQ810/
OR
ACS880:
in format axyz, where
ACS355:
FILE CONFIG ID
ACSM1:
DRIVE TYPE
CODE
ACS850/ACQ810/
ACS880:
Drive type code
mapping file

ACS355:
FILE CONFIG REV
ACSM1:
MAPPING FILE
VER
ACS850/ACQ810/
ACS880:
Mapping file ver
31 D2FBA COMM Read-only. Displays the status of the fieldbus 0 = Idle
STA adapter module communication. OR
Note: The value names may vary by drive. 4 = Off-
ACS355:
line
FBA STATUS
ACSM1:
D2FBA COMM
STA
ACS850/ACQ810/
ACS880:
D2FBA comm sta
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.

where:
FBA COMM SW
VER
ACS850/ACQ810:
FBA comm sw ver
ACS880:
FBA comm SW ver
module
where:
FBA APPL FW xy = minor revision numbers
REV z = correction number or letter.
ACSM1:
FBA APPL SW
VER
ACS850/ACQ810:
FBA appl sw ver
ACS880:
FBA appl SW ver
module

fieldbus adapter B.
01 DATA OUT 1 In output assembly instances that include drive 0 = None
(client to drive) parameters, this parameter specifies which
parameter’s value will be placed in location
ACS355: DATA OUT 1 value received by the drive from
FBA DATA OUT 1 the EtherNet/IP client.
FBA DATA OUT1 the range of 0 to 9999 as follows:
ACS850/ACQ810/
0 Not used
ACS880:
FBA data out1 1…99 Virtual address area of drive control.
Not used when the EtherNet/IP
protocol is used.
9999
0 = None Not used

(ACS880 only) only)
02… DATA OUT 2 … See parameter 01 DATA OUT 1. 0 = None
10 DATA OUT 10

fieldbus adapter B.
01 DATA IN 1 In input assembly instances that include drive 0 = None
(drive to client) parameters, this parameter specifies which
parameter’s value will be placed in location
ACS355: DATA IN 1 value sent by the drive to the
FBA DATA IN 1 EtherNet/IP client.
FBA DATA IN1 the range of 0 to 9999 as follows:
ACS850/ACQ810/
0 Not used
ACS880:
FBA data in1 1…99 Virtual address area of drive control.
Not used when the EtherNet/IP
protocol is used.
9999
0 = None Not used

(ACS880 only) only)
02… DATA IN 2 … See parameter 01 DATA IN 1. 0 = None
10 DATA IN 10
Control locations
reset, etc.).
In order to give the fieldbus client the most complete control over
documentation.

FBA.
3. Set the FENA-01/-11 configuration parameters in group 51. At
the minimum, select the communication protocol and profile
with parameter 5102 and configure the network settings with
action.
cyclical communication according to the selected assembly
instances.

Extended speed control assembly
that uses the ODVA 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 on page 151.
When Reference 1 (REF1) is used for speed control and the
parameter 5123 value is 128, an ODVA speed reference value of
±30000 (decimal) corresponds to an equal amount of rpm in the
drive. The reference value sent from the PLC is limited by
parameter 1105 REF1 MAX in the forward and reverse directions.
Bytes Instance 121 Instance 171
0…1 Control word Status word
2…3 Speed reference Speed actual value
4…5 Acceleration time1) Power1)
6…7 Deceleration time1) DC bus voltage1)
1)
Example

drives
9802 COMM PROT SEL 4 = EXT FBA Enables communication between
module.

adapter module.
5102 FB PAR 2 100 (= EIP AC/DC) Selects the EtherNet/IP protocol
(PROTOCOL/PROFILE) and the ODVA AC/DC drive profile.

drives
device.
5104 FB PAR 4 0 (= Static IP)2) Configuration will be obtained from
(IP CONFIGURATION) parameters 05...13.
(IP ADDRESS 1)
(IP ADDRESS 2)
(IP ADDRESS 3)
(IP ADDRESS 4)
5123 FB PAR 23 1282) Sets the scaling for the ODVA
(ODVA SPEED SCALE) speed reference.
3018 COMM FAULT 1 = FAULT2) Enables fieldbus communication

3019 COMM FAULT 3.0 s2) Defines the fieldbus
TIME communication break supervision
time.

5127 FBA PAR 1 = REFRESH Validates the FENA-01/-11

REFRESH configuration parameter settings.
9904 MOTOR CTRL 1 = VECTOR: SPEED Selects the speed control mode as
MODE the motor control mode.
1001 EXT1 10 = COMM Selects the fieldbus interface as
COMMANDS the source of the start and stop
location 1.
1103 REF1 SELECT 8 = COMM Selects the fieldbus reference 1 as
the source for speed reference 1.

drives
1604 FAULT RESET 8 = COMM Selects the fieldbus interface as
SEL the source for the fault reset
signal.
2)
Example

below.
Control word:
• 0h (0 decimal) –> READY
• 1h (1 decimal) –> ENABLED (Running forward)
• 2h (2 decimal) –> ENABLED (Running reverse)

action.
the tables below.
6. Set the FENA-11 configuration parameters in group 51. At the
minimum, select the communication protocol and profile with
instances.

the communication.
When Reference 1 (REF1) is used for speed control and the value
of parameter 51.23 is 128, an ODVA speed reference value of
drive. The speed reference value sent by the PLC is limited by
parameter 20.01 MAXIMUM SPEED in the forward direction and
20.02 MINIMUM SPEED in the reverse direction.
1)
Example

drives
50.01 FBA ENABLE Enable Enables communication between
module.
50.02 COMM LOSS Fault2) Enables fieldbus communication
50.03 COMM LOSS T 3.0 s2) Defines the fieldbus
OUT communication break supervision
time.
MODESEL scaling.

adapter module.
51.02 FBA PAR2 100 (= EIP AC/DC) Selects the EtherNet/IP protocol
(PROTOCOL/PROFILE) and the ODVA AC/DC drive
profile.
51.03 FBA PAR3 0 (= Auto2) Ethernet communication rate is
device.
51.04 FBA PAR4 0 (= Static IP)2) Configuration will be obtained
51.05 FBA PAR5 1922) First part of the IP address
(IP ADDRESS 1)
51.06 FBA PAR6 1682) Second part of the IP address
(IP ADDRESS 2)
51.07 FBA PAR7 02) Third part of the IP address
(IP ADDRESS 3)
51.08 FBA PAR8 162) Last part of the IP address
(IP ADDRESS 4)
51.09 FBA PAR9 242) Sets the network mask as
51.23 FBA PAR23 1282) Sets the scaling for the ODVA


drives
51.27 FBA PAR REFRESH Validates the FENA-11

10.01 EXT1 START FBA Selects the fieldbus interface as

FUNC the source of the start and stop
location 1.
as the source for speed reference
1.
34.01 EXT1/EXT2 SEL C.FALSE Selects that the external control
location is always EXT1.
34.03 EXT1 CTRL Speed Selects speed control as the
MODE1 control mode 1 for external control
location 1.
1) Read-only
or automatically detected/set
2) Example

below.
Control word:

action.
the tables below.
instances.

the communication.
drive. The speed reference value sent from the PLC is limited by
parameter 20.01 Maximum speed in the forward direction and
20.02 Minimum speed in the reverse direction.
1)
Example

ACS850/ACQ810
drives
module.
fault monitoring.

ACS850/ACQ810
drives
50.03 Comm loss t out 3.0 s2) Defines the fieldbus
time.
scaling.

adapter module.
51.02 FBA par2 100 (= EIP AC/DC) Selects the EtherNet/IP protocol
(PROTOCOL/PROFILE) and the ODVA AC/DC drive
profile.
51.03 FBA par3 0 (= Auto)2) Ethernet communication rate is
device.
51.04 FBA par4 0 (= Static IP)2) Configuration will be obtained
51.05 FBA par5 1922) First part of the IP address
(IP ADDRESS 1)
51.06 FBA par6 1682) Second part of the IP address
(IP ADDRESS 2)
51.07 FBA par7 02) Third part of the IP address
(IP ADDRESS 3)
51.08 FBA par8 162) Last part of the IP address
(IP ADDRESS 4)
51.09 FBA par9 242) Sets the network mask as
51.23 FBA par23 1282) Sets the scaling for the ODVA



ACS850/ACQ810
drives
10.01 Ext1 start func FB Selects the fieldbus interface as
location 1.
21.01 Speed ref1 sel FBA ref1 Selects the fieldbus reference 1
(ACS850) as the source for speed reference
21.01 Speed ref sel FBA ref1 1.
(ACQ810)
2)
Example

below.
Control word:

action.
instances.


the communication.
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.
1) Example

drives
module.
50.02 FBA A comm loss 1 = Fault2) Enables fieldbus A
func communication fault monitoring.
50.03 FBA A comm loss t 3.0 s2) Defines the fieldbus A
out communication break supervision
time.
type and scaling.
adapter module.
51.02 Protocol/Profile 100 = EIP AC/DC Selects the EtherNet/IP protocol
and the ODVA AC/DC drive
profile.
device.
51.04 IP configuration 0 = Static IP2) Configuration will be obtained
from configuration parameters
05…13.
51.05 IP address 1 1922) First part of the IP address
51.06 IP address 2 1682) Second part of the IP address
51.07 IP address 3 02) Third part of the IP address
51.08 IP address 4 162) Last part of the IP address
51.09 Subnet CIDR 242) Sets the network mask as
255.255.255.0, allowing access
51.23 ODVA speed scale 1282) Sets the scaling for the ODVA
speed reference.
52.01 FBA data in1 P.1.142) Output power

52.03 FBA data in3 P.1.112) DC voltage
53.01 FBA data out1 P.23.122) Acc time 1
53.03 FBA data out3 P.23.132) Dec time 1

drives
20.01 Ext1 commands 8 = Fieldbus A Selects the fieldbus A interface as

location 1.
1.
2)
Example

below.
Control word:
Configuring the client

client must be prepared 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 can be applied to all drive types compatible with the
module.
Before you start

Decide on the following points before starting the client
configuration.
Select protocol/profile
During the configuration of the drive and the client, it is necessary
to select a communication protocol, in this case EtherNet/IP, and a
communication profile. The communication profile determines
what I/O assemblies and objects are available. See chapter
EtherNet/IP – Communication profiles 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. The table below provides a listing of the
output and input assemblies.
Name Output Input Size Profile
instance instance (bytes)
Basic Speed Control 20 70 4 ODVA AC/DC
drive
Enhanced Speed Control 21 71 4 ODVA AC/DC
drive
Basic Speed and Torque 22 72 6 ODVA AC/DC
Control drive
Enhanced Speed and 23 73 6 ODVA AC/DC
Torque Control drive
Name Output Input Size Profile

instance instance (bytes)
Basic Speed Control plus 120 170 24 ODVA AC/DC
Drive Parameters drive
Enhanced Speed Control 121 171 24 ODVA AC/DC
plus Drive Parameters drive
Basic Speed and Torque 122 172 26 ODVA AC/DC
Control plus Drive drive
Parameters
Enhanced Speed and 123 173 26 ODVA AC/DC
Torque Control drive
plus Drive Parameters
ABB Drives Profile w/ Set 1 51 4 ABB Drives
Speed profile
ABB Drives Profile w/ 2 52 6 ABB Drives
Set Speed and Set Torque profile
Set Speed plus Drive profile
Parameters
Set Speed and Set Torque profile
plus Drive Parameters
Transparent16 w/One 11 61 4 Transparent16
profile
Transparent16 w/Two 12 62 6 Transparent16
profile
Transparent16 w/One plus 111 161 24 Transparent16
Drive Parameters profile
Transparent16 w/Two plus 112 162 26 Transparent16
Transparent32 w/One 21 71 8 Transparent32
profile
Transparent32 w/Two 22 72 12 Transparent32
profile
Transparent32 w/One plus 121 171 28 Transparent32
Transparent32 w/Two plus 122 172 32 Transparent32
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 FENA-01/-11 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

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.
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. For more information, see The table below lists the
service names of the objects: on page 207.
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
(www.abb.com/drives).
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

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

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 Output assembly PLC word settings
instances instances
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
161 111 12
162 112 13
For more information on the input/output assembly instances,

see chapter EtherNet/IP – Communication protocol.
5. Enter the following information. The example below uses the

ODVA AC/DC assembly instances 121 and 171. The PLC will
transmit and receive 12 words.
Type the name to be given Type the Input and Output Select the sizes of the
to the adapter module. Assembly Instance Input and Output words for
numbers. the adapter module.
FENA-01/-11 uses 16-bit Type the IP address of the Set Configuration as 1

words. Change Comm adapter module. and Size as 0.
Format to Data - INT (16
bits).
6. Click OK.
The adapter module is now added to the PLC I/O.
7. Click the FENA-01/-11 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.
9. Download the new configuration to PLC.

The PLC is now ready for communication with the adapter
module.
EtherNet/IP – Communication profiles 149
EtherNet/IP – Communication
profiles

communication between the EtherNet/IP client, the adapter
the master station and the drive.
With the FENA-01/-11 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.
150 EtherNet/IP – Communication profiles
EtherNet/IP FENA-01/-11 Drive

network
Profile selection:
Native
profile (eg,
ODVA AC/DC DCU, FBA)
ODVA AC/DC profile
Data conversion
Native
profile (eg,
ABB Drives
DCU, FBA)
ABB Drives profile Data conversion
Transparent16
Drive-specific profile1) Optional reference/

(with 16-bit words) actual value scaling
Drive-specific profile1) Transparent32

(with 32-bit words)
1) Can be used if the native profile is supported by the drive.
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 on page 207.
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 instances supported by
the adapter module are listed and defined in section Assembly
objects on page 172.
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.
Run Forward & Run Reverse (Control supervisor object)

These attributes are used to assert run and stop commands to the
Control supervisor object state machine according to the following
Run/Stop event matrix. See State (Control supervisor object) on
page 157.
RunFwd RunRev 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 ODVA SPEED SCALE 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
where
Dfr = Drive Frequency Reference in Hz
Osr = ODVA Speed Reference
Us = ODVA Speed Unit (see 23 ODVA SPEED SCALE on page 115)
Mf = Motor Nominal Frequency in Hz
Mss = Motor Synchronous Speed in rpm (not Motor Nominal Speed).
For a 4 pole 60 Hz motor (Mss = 1800 rpm) with a unit 1 rpm and
an ODVA Speed Reference of 900:
Osr × Us × Mf 900 ×1 rpm× 60 Hz

Dfr = = = 30 Hz
Mss 1800 rpm
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 23 ODVA SPEED SCALE on page 115).
For an ODVA Speed Reference of 900 rpm with a unit of 0.5 rpm:
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 ODVA TORQUE SCALE 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 ODVA TORQUE SCALE on page 116)
Mt = Motor Nominal Torque in N·m.
For a 1000 N·m Motor Nominal Torque with a unit of 1 N·m and an
ODVA Torque Reference of 500:
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.
Faulted (Control supervisor object)

This attribute indicates that the drive has experienced a fault. The
fault code may be read from the FaultCode attribute of the Control
supervisor object.
Warning (Control supervisor object)

This attribute indicates that the drive is experiencing a warning
condition. The warning code may be read from the WarnCode
attribute of the Control supervisor object.
Running Forward (Control supervisor object)

This attribute indicates that the drive is running in the forward
direction.
Running Reverse (Control supervisor object)

This attribute indicates that the drive is running in the reverse
direction.
Ready (Control supervisor object)

This attribute indicates that the Control supervisor object state
machine is in the Ready, Running or Stopping state. See State
(Control supervisor object) on page 157.
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:
ALM = Alarm
DEC = Deceleration
Non Existent FWD = Forward
Power off REV = Reverse
RDY = Ready
Power on
Startup ALM=1 Faulted
Power on
FaultRst
Not Ready
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
DEC=1
Enabled
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 ODVA SPEED SCALE 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 23 ODVA SPEED SCALE on page 115)
Mf = Motor Nominal Frequency in Hz
Mss = Motor Synchronous Speed in rpm (not Motor Nominal Speed).
For a 4 pole 60 Hz motor (Mss = 1800 rpm) with a unit of 1 rpm and
a Drive Frequency Actual of 30 Hz:
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 23 ODVA SPEED SCALE on page 115).
For a Drive Speed Actual of 900 rpm with a unit of 0.5 rpm:
Dsa 450 rpm

Osa = = = 900
Us 0.5 rpm
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 ODVA TORQUE SCALE 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 24 ODVA TORQUE SCALE on page 116)
Mt = Motor Nominal Torque in N·m.
For a 1000 N·m Motor Nominal Torque with a unit of 1 N·m and a
drive torque actual of 50%:
Dta× Mt 50 ×1000 Nm
Ota = = = 500
100 × Ut 100 ×1 Nm

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.

refers to the states shown in the state machine on page 167.
CONTROL
CONTROL
CONTROL
INHIBITED.
mode.

see drive documentation. If the drive is set
to receive the Run enable signal from the
fieldbus, this bit activates the signal.
INHIBITED.
ENABLED.
ENABLED.
output held).
ZERO OPERATING.
zero.
7 RESET 0 –> 1 Fault reset if an active fault exists. Proceed
to SWITCH-ON INHIBITED.
8…9 Reserved

10 REMOTE_ 1 Fieldbus control enabled.
CMD
12… Reserved
15

to the states shown in the state machine on page 167.
0 OFF1 ACTIVE
3 TRIPPED 1 FAULT
0 No fault
0 OFF2 ACTIVE
0 OFF3 ACTIVE
INHIB
0 –
0 No warning/alarm
8 AT_ 1 OPERATING. Actual value equals
SETPOINT reference (= is within tolerance limits, ie, in
speed control, speed error is 10% max. of
nominal motor speed).
outside tolerance limits).
9 REMOTE 1 Drive control location: REMOTE (EXT1 or
EXT2)

10 ABOVE_ 1 Actual frequency or speed equals or
LIMIT exceeds supervision limit (set by drive
parameter). Valid in both directions of
rotation.
0 Actual frequency or speed within
supervision limit
LOC
0 External Control Location EXT1 selected
ENABLE
0 No External Run Enable signal received
13… Reserved
14
15 FBA_ERROR 1 Communication error detected by fieldbus
adapter module
State machine
shown below.
SWITCH-ON
MAINS OFF INHIBITED (SW Bit6=1)
ABB Drives
communication
profile
NOT READY TO
A B C D
SWITCH ON (SW Bit0=0) CW = Control word
SW = Status word
n = Speed
generator
READY TO f = Frequency
from any state
inhibited Fault
READY TO FAULT

ACTIVE (SW Bit1=0)
and
B C D ACTIVE (SW Bit5=0) ACTIVE (SW Bit4=0)
(CW Bit4=0) n(f)=0 / I=0
OPERATION
C D
ENABLED (SW Bit2=1)
A
RFG: OUTPUT
D
ENABLED
B
RFG: ACCELERATOR
state
ENABLED
C
OPERATION
rising edge
D
References
reference.
Scaling
minimum reference.
Fieldbus Drive

REF1: 20000
REFx MIN
0 -(REFx MIN)

REF1: -20000
Actual values
Scaling
Fieldbus Drive

ACT1: 20000
0 0

ACT1: -20000
EtherNet/IP – Communication protocol 171
EtherNet/IP – Communication
protocol

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 FENA-01/-11 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.
172 EtherNet/IP – Communication protocol
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
FENA-01/-11 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
FENA-01/-11, 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.
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 Run
Reset Forward
1
2 Speed Reference (Low Byte)
3 Speed Reference (High Byte)
The format of the input assembly is:

0 Running Faulted
Forward
1
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:
0 Fault Run
Reset Forward
1
4 DATA OUT 1 Value (Low Byte)
5 DATA OUT 1 Value (High Byte)


0 Running Faulted
Forward
1
4 DATA IN 1 Value (Low Byte)
5 DATA IN 1 Value (High Byte)


The Extended speed control assembly is defined by the ODVA
AC/DC drive profile. The format of the output assembly is:
0 Net Net Fault Run Run
Ref Ctrl Reset Reverse Forward
1

0 At Ref Ctrl Ready Run- Run- Warn- Faulted
Refer- From From ning ning ing
ence Net Net Re- For-
verse ward
1 Drive State (See section State (Control supervisor object) on page
157.)
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.
Ref Ctl Reset Reverse Forward
1


verse ward
157.)

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:
0 Fault Run
Reset Forward
1
4 Torque Reference (Low Byte)
5 Torque Reference (High Byte)

0 Running Faulted
Forward
1
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.
0 Fault Run
Reset Forward
1


0 Running Faulted
Forward
1

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:
Ref Ctl Reset Reverse Forward
1

verse ward
157.)
Extended speed and torque control plus drive

parameters assembly
The Extended speed and torque control plus drive parameters
the Extended speed and torque control assembly of the ODVA
AC/DC drive profile.
0 NetRef NetCtl Fault Run Run
Reset Reverse Forward
1


verse ward
157.)

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)
0 Reset Ramp Ramp Ramp Inhibit Off 3 Off 2 Off 1
in Hold Out Oper- Control Control Con-
Zero Zero ation trol
1 Ext Remote
Ctrl Cmd
Loc
2 Set Speed (Low Byte)
3 Set Speed (High Byte)

0 Alarm Swc Off 3 Off 2 Tripped Rdy Rdy Rdy
On Sta Sta Ref Run On
Inhib
1 Field- Ext Ext Ctrl Above Remo At Set-
bus Run Loc Limit te point
Error Enable
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
the ABB Drives profile with set speed of the ABB Drives profile.
in Hold Out Oper- Control Con- Con-
Zero Zero ation trol trol
1 Ext Remote
Ctrl Cmd
Loc


Inhib
1 Field- Ext Ext Ctrl Above Remote At
bus Run Loc Limit Set-
Error Enable point


torque assembly
The ABB Drives profile with set speed and set torque assembly is
defined by ABB. The format of the output assembly is:
in Hold Out Oper- Control Control Con-
Zero Zero ation trol
1 Ext Remote
Ctrl Cmd
Loc
4 Set Torque (Low Byte)
5 Set Torque (High Byte)

Inhib
Error Enable point
4 Actual Torque (Low Byte)
5 Actual Torque (High Byte)

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.
in Hold Out Oper- Con- Con- Con-
Zero Zero ation trol trol trol
1 Ext Re-
Ctrl mote
Loc Cmd
4 Set Torque (Low Byte)
5 Set Torque (High Byte)


Inhib
Error Enable point
4 Actual Torque (Low Byte)
5 Actual Torque (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.
Instance 11 (Transparent 16 profile)
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)

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,
Transparent 16 with one assembly.



Transparent 16 with two assembly

The Transparent 16 with two assembly, defined by ABB, provides
4 Drive Profile16-bit Reference 2 Word (Low Byte)

4 Drive Profile16-bit Actual 2 Word (Low Byte)
Transparent 16 with two assembly plus drive

parameters
The Transparent 16 with two assembly plus drive parameters,
Transparent 16 with two assembly.



Transparent 32 with one assembly

The Transparent 32 with one assembly, defined by ABB, provides
1 Drive Profile 32-bit Control Word
5 Drive Profile 32-bit Reference 1 Word

1 Drive Profile 32-bit Status Word
5 Drive Profile 32-bit Actual 1 Word
Transparent 32 with one assembly plus drive

parameters
The Transparent 32 with one assembly plus drive parameters,
Transparent 32 with one assembly.



Transparent 32 with two assembly

The Transparent 32 with two assembly, defined by ABB, provides


Transparent 32 with two assembly plus drive

parameters
The Transparent 32 with two assembly plus drive parameters,
Transparent 32 with two assembly.



Class objects
Legend Data type
UINT8 Unsigned Integer 8 bit
SINT16 Signed Integer 16 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:
• User’s manual for the drive
• Electronic Data Sheet Files (EDS) for the drive.
Note that the units of the attributes may differ from those of the
parameters documented elsewhere and those differences must be
considered when interfacing to the drive via the module.
The table below lists the service names of the 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 Services Description Data
name type
1 Revision Get Revision of the identity object Array of
UINT8
Instance attributes (Instance #1)

# Attribute Services Description Data type
name
1 Vendor ID Get Identification of the device UINT16
vendor
2 Device Get Identification of the general UINT16
Type product type
3 Product Get Assigned vendor code to UINT16
Code describe the device
4 Revision Get Revision of the item the Array[UINT8
identity object represents UINT8]
5 Status Get Summary status of the UINT16
device
6 ODVA Get Serial number of the UINT32
Serial EtherNet/IP module
Number
7 Product Get Product identification. Max 32 Short String
Name characters.
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
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
DRIVE TYPE CODE.
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 Predefined Master/Slave
Connection Set has been allocated to a
master. Outside the Master/Slave paradigm
the meaning of this bit is to be defined.
1 Reserved, set to 0
Bit(s) Type/Name Definition

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 TRUE indicates the device detected a
Recoverable recoverable problem. The problem does not
Fault cause the device fault state.
9 Minor TRUE indicates the device detected a
Unrecoverable unrecoverable problem. The problem does
Fault not cause the device fault state.
10 Major TRUE indicates the device detected a
Recoverable problem which caused the device to transfer
Fault into the “Major Recoverable Fault” state.
11 Major TRUE indicates the device detected a
Unrecoverable problem which caused the device to transfer
Fault 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

This object serves as a database for motor parameters. Different
motor types require different data to describe the motor. For
example, AC induction motors do not need field current data like a
DC motor to describe the motor.
Motor class Motor types in class
AC motors 3 - PM synchronous
6 - Wound rotor induction
7 - Squirrel cage induction motor
DC motors 1 - PM DC motor
2 - FC DC motor

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

# Attribute Services Description Motor Data
name type type
3 Motor Get See the table above. AC UINT16
Type
6 Rated Get, Set Rated Stator Current AC/DC UINT16
Current from motor name plate
Units: [100mA]
7 Rated Get, Set Rated Base Voltage AC/DC UINT16
Voltage from motor name plate
Units: [V]
8 Rated Get, Set Rated Power at Rated AC/DC UINT32
Power Frequency
Units: [W]
# Attribute Services Description Motor Data

name type type
9 Rated Get, Set Rated Electrical AC UINT16
Frequency Frequency
Units: [Hz]
12 Pole Get Number of poles in the AC UINT16
Count motor
15 Base Get, Set Nominal speed at rated AC/DC UINT16
Speed frequency from
nameplate
Units [RPM]
Control supervisor object, class 29h

The object models all the management functions for devices within
the ‘Hierarchy of Motor Control Devices’. The behavior of motor
control devices is described by the AC/DC-drive object, class 2Ah
on page 214 and the Run/Stop event matrix under Run Forward &
Run Reverse (Control supervisor object) on page 152. See section
State (Control supervisor object) on page 157.
Note: If assembly instances are used, they override this object, for
example, upon drive power-up.

name type
1 Revision Get Revision of the CIP Object Class Array of
Definition upon which the UINT8

name type
3 Run 1 Get, Set 0 = Stop, 1 = Run BOOL
(See the Run/Stop event matrix
on page 152.)

name type
4 Run 2 Get, Set 0 = Stop, 1 = Run BOOL
(See the Run/Stop event matrix
on page 152.)
5 Net Control Get, Set 0 = Local Control, 1 = Network BOOL
Control
6 State Get State of Object UINT8
(See section State (Control
supervisor object) on page 157.)
7 Running 1 Get 0 = Stopped, 1 = Running BOOL
8 Running 2 Get 0 = Stopped, 1 = Running BOOL
9 Ready Get 1 = Ready, Enabled or Stopping; BOOL
0 = Other state
10 Faulted Get 0 = Not faulted, 1 = Fault BOOL
occurred
11 Warning Get 0 = No Warnings present, 1 = BOOL
Warning
12 FaultRst Get, Set 0 → 1 Fault Reset BOOL
13 Fault Code Get The fault that caused the last UINT16
transition to the Faulted state.
DRIVECOMM codes are
reported. See Drive Manual for
further information on
DRIVECOMM codes.
14 Warning Get Code word indicating warning UINT16
Code present. If multiple warnings are
present, the lowest code value is
displayed. DRIVECOMM codes
are reported. See Drive Manual
for further information on
DRIVECOMM codes.
15 CtlFromNet Get 0 = NetControl disabled BOOL
1 = NetControl enabled
16 DNFaultMode Get, Set 2 = Vendor specified UINT8
17 ForceFault Get, Set 0 → 1 forces the drive to fault BOOL
AC/DC-drive object, class 2Ah

This object models the functions specific to an AC or DC Drive.

name type
1 Revision Get Revision of the CIP Object Class Array of
Definition upon which the UINT8

name type
3 At Get Frequency arrival BOOL
Reference
4 NetRef Get, Set Requests torque or speed BOOL
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 Get, Set 0 = Vendor specific UINT8
mode
7 Speed Get Units = See parameter 23 ODVA SINT16
Actual SPEED SCALE.
8 SpeedRef Get, Set Units = See parameter 23 ODVA SINT16
SPEED SCALE.
11 Torque Get Units = See parameter 24 ODVA SINT16
Actual TORQUE SCALE.
12 TorqueRef Get, Set Units = See parameter 24 ODVA SINT16
TORQUE SCALE.
18 AccelTime Get, Set Units = milliseconds UINT16
19 DecelTime Get, Set Units = milliseconds UINT16

name type
22 Speed Get, Set Speed scaling factor. See UINT8
Scale parameter 23 ODVA SPEED
SCALE.
24 Torque Get, Set Torque scaling factor. See UINT8
Scale parameter 24 ODVA TORQUE
SCALE.
29 Ref From Get Reflecting attribute 4 BOOL
Net
Drive parameter object, class 90h

With FENA-01/-11, drive parameters can also be accessed via
Explicit Messaging. Explicit Messaging makes use of objects
consisting of three parts: class, instance and attribute.
Note: When using the drive parameter object to update the
fieldbus configuration groups, changes to the fieldbus configuration
will only take effect when the module is powered up the next time
or when a ‘Fieldbus Adapter parameter refresh’ is given.
Class is always 144 (90h). Instance and attribute correspond to the
drive parameter group and index in the following way:
• Instance = Parameter group (0…99)
• Attribute = Parameter index (01…99)
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 the user to configure the
fieldbus configuration groups without needing to know the drive-
specific groups associated with the configuration groups.
Note: When using the fieldbus configuration object to update the
fieldbus configuration groups, changes to the fieldbus configuration
will only take effect when a reset service 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
name type
1 Revision Get Revision of the Configuration Array of
Object UINT8

group A (group 1)
The actual parameter group number depends on the drive type.
Group A (group 1) corresponds to:
ACQ810
fieldbus adapter B.
# Attribute name Services Description Data
type
1 Configuration Group A Get, Set See 01 FBA TYPE on UINT16
(Group 1) - Parameter page 107.
1
2 Configuration Group A Get, Set See 02 PROTOCOL/ UINT16
(Group 1) - Parameter PROFILE on page 107.
2
3 Configuration Group A Get, Set See 03 COMM RATE UINT16
(Group 1) - Parameter on page 108.
3

type
4 Configuration Group A Get, Set See 04 IP CONFIGU- UINT16
(Group 1) - Parameter RATION on page 108.
4
5 Configuration Group A Get, Set See 05 IP ADDRESS UINT16
(Group 1) - Parameter 1...08 IP ADDRESS 4.
5
6
7
8
9 Configuration Group A Get, Set See 09 SUBNET CIDR UINT16
9
10 Configuration Group A Get, Set See 10 GW ADDRESS UINT16
(Group 1) - Parameter 1...13 GW ADDRESS
10 4.
11 4.
12 4.
13 4.
14 Configuration Group A Get, Set See 14… 18 Reserved UINT16
14
15

type
16
17
18
19 Configuration Group A Get, Set See 19 T16 SCALE on UINT16
(Group 1) - Parameter page 111.
19
20 Configuration Group A Get, Set See 20 CONTROL UINT16
(Group 1) - Parameter TIMEOUT on page 112.
20
21 Configuration Group A Get, Set See 21 IDLE ACTION UINT16
21
22 Configuration Group A Get, Set See 22 ODVA STOP UINT16
(Group 1) - Parameter FUNCTION on page
22 114.
23 Configuration Group A Get, Set See 23 ODVA SPEED UINT16
(Group 1) - Parameter SCALE on page 115.
23
24 Configuration Group A Get, Set See 24 ODVA UINT16
(Group 1) - Parameter TORQUE SCALE on
24 page 116.
25 Configuration Group A Get, Set See 25 … 26 Reserved UINT16
25
26 Configuration Group A Get, Set See 25 … 26 Reserved UINT16
26
27 Configuration Group A Get, Set See 27 FBA PAR UINT16
(Group 1) - Parameter REFRESH on page
27 117.

type
28 Configuration Group A Get See 28 PAR TABLE UINT16
(Group 1) - Parameter VER on page 117.
28
29 Configuration Group A Get See 29 DRIVE TYPE UINT16
(Group 1) - Parameter CODE on page 117.
29
30 Configuration Group A Get See 30 MAPPING FILE UINT16
30
31 Configuration Group A Get See 31 D2FBA COMM UINT16
(Group 1) - Parameter STA on page 118.
31
32 Configuration Group A Get See 32 FBA COMM UINT16
(Group 1) - Parameter SW VER on page 119.
32
33 Configuration Group A Get See 33 FBA APPL SW UINT16
33

group B (group 2)
Group B (group 2) corresponds to:
fieldbus adapter B.
type
1 Configuration Group B Get, Set See 01 DATA OUT 1 UINT16
(Group 2) - Parameter 1 on page 120.
10

group C (group 3)
Group C (group 3) corresponds to:
fieldbus adapter B.
type
1 Configuration Group C Get, Set See 01 DATA IN 1 UINT16
10
TCP/IP interface object, class F5h

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

name type
1 Revision Get Revision of the TCP/IP Interface Array of
Object Class Definition upon UINT8
which the implementation is
based

type
1 Interface Status Get See Interface Status DWORD
attribute (#1) bits on page
223.
2 Configuration Get See Configuration DWORD
Capability Capability attribute (#2)
bits on page 224.
3 Configuration Get See Configuration Control DWORD
Control attribute (#3) bits on page
225.
4 Physical Link Get Path to physical link object STRUCT
Object of:
Path Size Path size UINT
Path Logical segments Padded
identifying the physical link EPATH
object

type
5 Interface Get STRUCT
Configuration of:
IP Address IP Address UDINT
Network Mask Network Mask UDINT
Gateway Gateway Address UDINT
Address
Unused UDINT
Unused UDINT
Default Domain Default Domain Name for STRING
Name unqualified host names.
6 Host Name Get Host name STRING
Attribute explanations
Interface Status attribute (#1) bits
Bit Name Description
0…3 Interface Indicates the status of the Interface Configuration
configuration attribute.
status
Value Description
0 The Interface Configuration attribute has
not been configured.
1 The Interface Configuration attribute
contains valid configuration obtained
from BOOTP, DHCP or non-volatile
storage.
2 The IP address member of the Interface
Configuration attribute contains valid
configuration, obtained from hardware
settings (eg, pushwheel, 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.
5…31 Reserved, set to 0
Configuration Capability attribute (#2) bits

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 1 (True) = The device is capable of sending its
update host name in the DHCP request as documented
in Internet draft <draft-ietf-dhc-dhcp-dnc-12.txt>
4 Configuration 1 (True) = The Interface Configuration attribute is
settable settable. Some devices, eg, a PC or workstation,
may not allow interface configuration to be set via
the TCP/IP interface object.
5 Hardware 1 (True) = The IP address member of the Inter-
configurable face Configuration attribute can be obtained from
hardware settings (eg, pushwheel, thumbwheel).
0 (False) = The Status instance attribute (1) Inter-
face configuration status field value shall never be
2 (The Interface configuration attribute contains
valid configuration obtained from hardware set-
tings.)
Configuration Control attribute (#3) bits

0…3 Start-up Determines how the device obtains its initial
configuration configuration and start-up.
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 configura-
tion values via BOOTP.
2 The device obtains its interface configura-
tion values via DHCP upon start-up.
3…15 Reserved
4 DNS enable 1 (True) = The device resolves host names by
querying a DNS server.
Ethernet link object, class F6h

This object maintains link-specific counters and status information
for the Ethernet communication interface.

name type
1 Revision Get Revision of the Ethernet Link Array of
Object Class Definition upon UINT8
which the implementation is
based

name type
1 Interface Get, Set 10 or 100 Mbps UDINT
Speed
2 Interface Get, Set Interface status flags: DWORD
Flags
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 Get Ethernet MAC address of the ARRAY
Address module 6XUSINT
Connection object, class 05h

Note: Do not modify this object. This object is only used while
establishing the connection between the adapter module and the
PLC.
The connection class allocates and manages the internal
resources associated with both I/O and explicit messaging
connections. The specific instance generated by the connection
class is referred to as connection instance or connection object.
The table below shows the connection object states:
State Description State Description
00 Non-Existent 03 Established
01 Configuring 04 Timed Out
02 Waiting for Connection 05 Deferred Delete
ID
Class attributes
name type
1 Revision Get Revision of the connection Array of
object UINT8
Instance attributes
Instance number Description
1 Explicit messaging connection
2 Polled I/O connection
4 Change-of-State/Cyclic I/O connection

name type
1 State Get State of the object (See the UINT8
state table on page 226.)
2 Instance Get Indicates either I/O (1) or UINT8
Type messaging connection (0).
3 Transport Get Defines the behavior of the UINT8
Class Trig- connection.
ger
4 Produced Get Placed in CAN Identifier Field UINT16
Cnxn Id when the connection
transmits
5 Consumed Get CAN Identifier Field value that UINT16
Cnxn Id denotes message to be
received
6 Comm Char- Get Defines the Message UINT8
acteristics Group(s) across which
productions and
consumptions are associated
in this connection.
7 Produced Get Maximum number of bytes UINT16
Connection transmitted across this
Size connection

name type
8 Consumed Get Maximum number of bytes UINT16
Connection received across this
size connection
9 Expected Get, Set Defines the timing associated UINT16
Packet Rate with this connection in
milliseconds. A value of 0
deactivates the associated
timers.
12 Watchdog Get, Set Defines how to handle UINT8
Timeout Inactivity/Watchdog timeouts.
Action
13 Produced Get Number of bytes in the UINT16
Connection produced_connection_path
Path Length length attribute
14 Produced Get Application object producing Array of
Connection data on this connection UINT8
Path
15 Consumed Get Number of bytes in the UINT16
Connection consumed_connection_path
Path Length length attribute
16 Consumed Get Specifies the application Array of
Connection object(s) that are to receive UINT8
Path the data consumed by this
connection object.
17 Production Get Defines minimum time UINT16
Inhibit Time between new data production
in milliseconds.
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.

name type
1 Revision Get Revision of the CIP Object Array of
Class Definition upon which the UINT8

name type
1 Acknowl- Get, Set Time in milliseconds to wait for UINT16
edge Timer acknowledge before resending
2 Retry Limit Get, Set Number of Acknowledge UINT8
Timeouts to wait before
informing the producing
application of a Retry-
Limit_Reached event
3 COS Get Connection Instance Id which UINT16
Producing contains the path of the
Connection producing I/O application object
Instance which will be notified of
Acknowledge Handler events
EtherNet/IP – Diagnostics 231
EtherNet/IP – Diagnostics

the adapter module when the module is used for EtherNet/IP
communication.
232 EtherNet/IP – Diagnostics
LED indications
Name Color Function

HOST
Flashing orange representative.
EtherNet/IP – Diagnostics 233
Name Color Function

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 Recoverable fault
Red Device has an unrecoverable fault. This
MODULE
may be cleared by a Fieldbus Adapter
parameter refresh or by cycling drive
power. This may have been caused by
the device detecting another device on
the network with the same MAC ID or IP
address.
Flashing red- Device is in Self Test.
green
Flashing orange representative.
234 EtherNet/IP – Diagnostics
Name Color Function

NETWORK Off Device is not on-line.
• 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).
235
PROFINET IO – Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

PROFINET IO – Communication profiles . . . . . . . . . . . . . . . . . 291
PROFINET IO – Communication protocol . . . . . . . . . . . . . . . . 309
PROFINET IO – Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . 339
236
PROFINET IO – Start-up 237
PROFINET IO – Start-up

adapter module
adapter module
• examples of configuring the master station for communication
with the adapter module.

238 PROFINET IO – Start-up
Drive configuration
PROFINET IO connection configuration

The detailed procedure of activating the module for PROFINET IO

ACQ810
fieldbus adapter B.
01 FBA TYPE Read-only. Shows the fieldbus adapter type 128 =
as detected by the drive. The value cannot be ETHER-
between the drive and the module has not
been established.
02 PROTOCOL/ Selects the application protocol and 01)
PROFILE communication profile for the network
connection.
ACS355: The selections available for PROFINET IO
ACSM1:
FBA PAR2 1)
0 = Modbus/TCP: ABB Drives profile -
ACS850/ACQ810: Classic
FBA par2
ACS880:
Protocol/Profile
10 = PNIO Pdrive PROFINET IO protocol: PROFIdrive profile
11 = PNIO ABB Pro PROFINET IO protocol: ABB Drives profile
12 = PNIO T16 PROFINET IO protocol: Transparent 16-bit
profile
13 = PNIO T32 PROFINET IO protocol: Transparent 32-bit
profile
14 = PNIO PdriveM PROFINET IO protocol: PROFIdrive
positioning mode

ACS355:
FB PAR 3
ACSM1:
FBA PAR3
ACS850/ACQ810:
FBA par3
ACS880:
Commrate
04 IP Sets the method for configuring the IP 1 = Dyn
CONFIGURATION address, subnet mask and gateway address IP DHCP
for the module.
ACS355:
In a PROFINET IO network, the master
FB PAR 4 controller has a Duplicate Address Detection
ACSM1: mechanism.
FBA PAR4
ACS850/ACQ810:
FBA par4
ACS880:
IP configuration
0 = Static IP Configuration will be obtained from
parameters 05…13 or from the PLC via DCP.
The DCP protocol allows the master controller
to find every PROFINET IO device on a
subnet. When the adapter module is initialized
with the PROFINET IO protocol, the IP
address is transferred to the PROFINET IO
communication stack.
If there is a need to change the IP address
configured via DCP, it should be done with a
DCP tool, such as Siemens Step7. If some of
the other methods are used to change the IP
address, the module must be restarted to
enable any changes.

05 IP ADDRESS 1 An IP address is assigned to each IP node on 0
a network. An IP address is a 32-bit number
ACS355: that is typically represented in “dotted decimal”
FB PAR 5 notation consisting of four decimal integers, on
ACS850/ACQ810: bits) in the IP address. Parameters 05…08
ACS880:
IP address 1
0…255 IP address
… … … …
ACS355:
FB PAR 8
ACSM1:
FBA PAR8
ACS850/ACQ810:
FBA par8
ACS880:
IP address 4
0…255 IP address

ACS355: mask is a 32-bit binary number that is used to
FB PAR 9 split the IP address into a network address
ACSM1: and host address.
below.
ACS880:
Subnet CIDR

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

ACS355:
node needs to communicate with an IP node
FB PAR 10
on another subnet, the IP node sends the data
ACSM1: to the IP gateway for forwarding. Parameters
FBA par10
ACS880:
GW address 1
0…255 GW address

… … … …
ACS355:
FB PAR 13
ACSM1:
FBA PAR13
ACS850/ACQ810:
FBA par13
ACS880:
GW address 4
0…255 GW address
18 PROFINET IO.
ACSM1: native communication profile (eg, DCU or
FBA PAR19 FBA) and a 16-bit transparent Reference
ACS850/ACQ810: 1/Actual value 1.
ACS880:
T16 scale
parameter has a value of 99 and a reference
of 1000 given by the master, the reference will
be multiplied by 99 +1 = 100 and forwarded to
the drive as 100000. According to the DCU
profile, this value is interpreted as a reference
of 100 rpm in the drive.

20 TELEGRAM TYPE Read-only. Indicates the telegram type 0=
selected for PROFINET IO communication. Unknown
ACS355: The adapter module automatically detects the
FB PAR 20 telegram type defined in the PLC.
ACSM1: For more information on the supported PPO
FBA PAR20 message types, see section PPO types on
ACS850/ACQ810: page 312.
FBA par20
ACS880:
Telegram type
0 = Unknown Cyclical communication between the master
and the module has not been established yet.
1 = PPO1 PPO1 selected
7 = PPO7 PPO7 selected. Not supported with ACS355.
8 = ST1 ST1 selected
9 = ST2 ST2 selected. Not supported with ACS355.
26 PROFINET IO.
ACS355/ACSM1:
0 = Done.
FBA PAR
Note: This parameter cannot be changed
REFRESH
while the drive is running.
ACS850/ACQ810/
ACS880:
FBA par refresh
Configure

ACS850/ACQ810/ OR
ACS880: in format axyz, where
ACS355:
FILE CONFIG ID
ACSM1:
DRIVE TYPE
CODE
ACS850/ACQ810/
ACS880:
Drive type code
mapping file
ACS355:
FILE CONFIG REV
ACSM1:
MAPPING FILE
VER
ACS850/ACQ810/
ACS880:
Mapping file ver

31 D2FBA COMM STA Read-only. Displays the status of the fieldbus 0 = Idle
adapter module communication. OR
ACS355: Note: The value names may vary by drive. 4 = Off-
FBA STATUS line
ACSM1:
D2FBA COMM STA
ACS850/ACQ810/
ACS880:
D2FBA comm sta
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.
where:
FBA COMM SW
VER
ACS850/ACQ810:
FBA comm sw ver
ACS880:
FBA comm SW ver
module

where:
FBA APPL FW REV xy = minor revision numbers
FBA APPL SW
VER
ACS850/ACQ810:
FBA appl sw ver
ACS880:
FBA appl SW ver
module

fieldbus adapter B.
01 DATA OUT 1 Selects data word 1 received by the drive over 1 or 112)
(master to drive) the PROFINET network. The content is defined
by a decimal number in the range of 0 to 9999
ACS355: as follows:
FBA DATA OUT 1
ACSM1: 0 Not used
FBA DATA OUT1
1…99 Virtual address area of drive control
ACS850/ACQ810/
ACS880: 101… Parameter area of the drive
FBA data out1 9999
See also Virtual address area allocation with

ACSM1 on page 251.
0 = None Not used
1 = CW 16bit Control word (16 bits)3)
2 = Ref1 16bit Reference REF1 (16 bits)3)
3 = Ref2 16bit Reference REF2 (16 bits)3)
11 = CW 32bit Control word (32 bits)
12 = Ref1 32bit Reference REF1(32 bits)
13 = Ref2 32bit Reference REF2 (32 bits)
21 = CW2 16bit Control word 2 (16 bits)
(ACS880 only) only)

02 DATA OUT 2 See parameter 01 DATA OUT 1. 0 or 24)
03… DATA OUT 3… See parameter 01 DATA OUT 1. 0
10 DATA OUT 10
1)
The number of parameters in this group may vary by drive type and drive firmware.
2)
11 (CW 32bit) is the default setting if the Transparent 32 profile is used.
3)
With an ACS355 drive, Control word and REF1 are always fixed to virtual addresses
1 and 2 respectively. If REF2 is used, its virtual address is always 3.
4) 2 (Ref1 16bit) is a fixed setting with an ACS355 drive.

fieldbus adapter B.
01 DATA IN 1 Selects data word 1 sent by the drive over the 4 or 142)
(drive to master) PROFINET network. The content is defined by
a decimal number in the range of 0 to 9999 as
ACS355: follows:
FBA DATA IN 1
ACSM1: 0 Not used
FBA DATA IN1
1…99 Virtual address area of drive control
ACS850/ACQ810/
ACS880: 101… Parameter area of the drive
FBA data in1 9999
See also Virtual address area allocation with

ACSM1 on page 251.
0 = None Not used
4 = SW 16bit Status word (16 bits)
5 = Act1 16bit Actual value ACT1 (16 bits)
14 = SW 32bit Status word (32 bits)
24 = SW2 16bit Status word 2 (16 bits)
(ACS880 only) only)

02 DATA IN 2 See parameter 01 DATA IN 1. 0 or 53)
03… DATA IN 3… See parameter 01 DATA IN 1. 0
10 DATA IN 10
1)
The number of parameters in this group may vary by drive type and drive firmware.
2)
14 (SW 32bit) is the default setting if the Transparent 32 profile is used.
3)
5 (Act1 16bit) is a fixed setting with an ACS355 drive.
Virtual address area allocation with ACSM1

When the PROFIdrive profile or PROFIdrive positioning mode is
used with an ACSM1 drive, the virtual addresses shown below are
recommended. (FBA REFx mode is selected with drive parameter
50.04/50.05.)
The information in the table is applicable only if PPO messaging is
used (see parameter 20 TELEGRAM TYPE). If standard telegrams
(STx) are used, virtual addresses for standard telegrams (ST1 and
ST2) are updated automatically.
Abbreviation Description Data Recommended virtual
length address with ACSM1
FBA REFx modes
Speed Position
mode mode
STW1 Control word 1 16-bit 1 1
NSOLL_A Speed set point A 16-bit 2 or 3
NSOLL_B Speed set point B 32-bit 12 or 13
STW2 Control word 2 16-bit 21 21
XSOLL_A Position set point A 32-bit 12 or 13
VELOCITY_A Velocity 32-bit 13
ZSW2 Status word 2 16-bit 24 24
NIST_A Speed actual value A 16-bit 5 or 6
NIST_B Speed actual value B 32-bit 15 or 16
ZSW1 Status word 1 16-bit 4 4
XIST_A Position actual value A 32-bit 15 or 16
Control locations
reset, etc.).
In order to give the fieldbus master the most complete control over
documentation.

FBA.
3. Set the FENA-01/-11 configuration parameters in group 51. At
the minimum, select the communication protocol and profile
with parameter 5102 and configure the network settings with
action.
Note: The adapter module sets the Status word and actual
value automatically in parameters 5401 and 5402, and Control
word and reference in parameters 5501 and 5502.

profile with PPO Type 4
This example shows how to configure a basic speed control
application that uses the PROFIdrive profile. In addition, some
The start/stop commands and reference are according to the
PROFIdrive profile. For more information, see the PROFIdrive
state machine on page 298.
The reference value ±16384 (4000h) corresponds to parameter
1105 REF1 MAX in the forward and reverse directions.
Direction PZD1 PZD2 PZD3 PZD4 PZD5 PZD6
Out Control Speed Accelera- Decelera- N/A N/A
word reference tion time1) tion time
In Status Speed Power1) DC bus N/A N/A
word actual value voltage
1)
Example

drives
9802 COMM PROT 4 = EXT FBA Enables communication between
SEL the drive and the fieldbus adapter
module.

adapter module.
5102 FB PAR 2 10 (= PNIO Pdrive) Selects the PROFINET IO protocol
(PROTOCOL/ and PROFIdrive profile.
PROFILE)
device.
5104 FB PAR 4 0 (= Static IP)2) Configuration will be obtained from
(IP CONFIGURATION) parameters 05…13 or from the PLC
via the DCP protocol.
(IP ADDRESS 1)

drives
(IP ADDRESS 2)
(IP ADDRESS 3)
(IP ADDRESS 4)
5109 FB PAR 9 242) Sets the network mask as
3018 COMM FAULT 3 = LAST SPEED2) Enables fieldbus communication

3019 COMM FAULT 3.0 s2) Defines the fieldbus communication
TIME break supervision time.
5401 FBA DATA IN 1 4 (= SW 16bit)1) Status word

5402 FBA DATA IN 2 5 (= Act1 16bit)1) Actual value 1 (speed)
5501 FBA DATA OUT 1 1 (= CW 16bit)1) Control word
5502 FBA DATA OUT 2 2 (= Ref1 16bit)1) Reference 1 (speed)
5127 FBA PAR 1 = REFRESH Validates the FENA-01/-11

1001 EXT1 10 = COMM Selects the fieldbus interface as the

COMMANDS source of the start and stop
location 1.
1103 REF1 SELECT 8 = COMM Selects the fieldbus reference 1 as
the source for speed reference 1.
1601 RUN ENABLE 7 = COMM Selects the fieldbus interface as the
source for the inverted Run enable
signal (Run disable).

drives
1604 FAULT RESET 8 = COMM Selects the fieldbus interface as the
SEL source for the fault reset signal.
1)
Read-only or automatically detected/set
2)
Example

below.
Control word:

communication profile with PPO Type 4
application that uses the ABB Drives profile. From the PLC
programming point, the ABB Drives profile is similar to the
PROFIdrive profile shown in the first example.
(decimal) corresponds to the reference set by parameter 1105
(decimal) corresponds to the reference set by parameter 1108
Out Control Speed Torque N/A N/A N/A
word reference reference
In Status word Speed actual Torque N/A N/A N/A
value actual

drives
9802 COMM PROT SEL 4 = EXT FBA Enables communication between
module.

adapter module.
5102 FBAPAR 2 11 (= PNIO ABB Pro) Selects the PROFINET IO
(PROTOCOL/PROFILE) protocol and ABB Drives profile.
device.
5104 FB PAR 4 0 (= Static IP) Configuration will be obtained
(IP CONFIGURATION) from parameters 05…13 or from
the PLC via the DCP protocol.
3018 COMM FAULT 3 = LAST SPEED2) Enables fieldbus communication

3019 COMM FAULT TIME 3.0 s2) Defines the fieldbus
time.
5401 FBA DATA IN 1 4 (= SW 16bit)1) Status word

5402 FBA DATA IN 2 5 (= Act1 16bit)1) Actual value 1 (speed)
5403 FBA DATA IN 3 6 (= Act2 16bit)2) Actual value 2 (torque)
5501 FBA DATA OUT 1 1 (= CW 16bit)1) Control word
5502 FBA DATA OUT 2 2 (= Ref1 16bit)1) Reference 1 (speed)
5503 FBA DATA OUT 3 2 (= Ref2 16bit)2) Reference 2 (torque)
5127 FBA PAR REFRESH 1 = REFRESH Validates the FENA-01/-11

9904 MOTOR CTRL 2 = VECTOR: TORQ Selects the vector control mode
MODE as the motor control mode.
location 1.

drives
location 2.
1102 EXT1/EXT2 SEL 8 = COMM Enables external control location
1/2 selection through the fieldbus.
1.
1.
1604 FAULT RESET SEL 8 = COMM Selects the fieldbus interface as
the source for the fault reset
signal.
1) Read-only
or automatically detected/set
2) Example

below.
Control word:

action.
the tables below.
Note: The adapter module automatically sets the
communication profile-specific virtual address for the Status
word in parameter 52.01 and for the Control word in parameter
53.01.

PROFIdrive profile, speed control mode. For more information, see
the PROFIdrive state machine on page 298.
25.02 SPEED SCALING in the forward and reverse directions.
Out Control Speed Acceleration time1) Deceleration time1)
word reference
In Status Speed actual Power1) DC bus voltage1)
word value
1) Example

drives
50.02 COMM LOSS FUNC Last speed Enables fieldbus
communication fault
monitoring.
50.03 COMM LOSS T OUT 3.0 s Defines the fieldbus
communication break
supervision time.
MODESEL scaling.

adapter module.
51.02 FBA PAR2 10 (= PNIO Pdrive) Selects the PROFINET IO
(PROTOCOL/PROFILE) protocol and PROFIdrive
profile.

drives
device.
51.04 FBA PAR4 0 (= Static IP) Configuration will be obtained
(IP CONFIGURATION) from parameters 05…13 or
from the PLC via the DCP
protocol.
52.01 FBA DATA IN1 4 (= SW 16bit)1) Status word

52.02 FBA DATA IN2 5 (= Act1 16bit) Actual value 1 (speed)
53.01 FBA DATA OUT1 1 (= CW 16bit)1) Control word
53.02 FBA DATA OUT2 2 (= Ref1 16bit) Reference 1 (speed)

settings.

location 1.
reference 1.
control location 1.
2) Example

below.
Control word:
Position control using the PROFIdrive communication

This example shows how to configure a basic positioning
application. The start/stop commands and reference are according
to the PROFIdrive profile, positioning mode. For more information,
see the PROFIdrive state machine on page 299.
Note: By default, fieldbus is not the only control source. See actual
signal 02.12 FBA MAIN CW in ACSM1 Motion Control Program
Firmware Manual for details.
The position set point and velocity reference are defined as 32-bit
integer values; both are scaled as defined in the drive parameter
settings.
Out Control word Position set point Velocity reference N/A
(STW1)
In Status word Position actual Velocity actual value N/A
(ZSW1) value

drives
50.01 FBA ENABLE Enable Enables communication between
module.
50.02 COMM LOSS Fault Enables fieldbus communication
50.03 COMM LOSS T 3.0 s Defines the fieldbus communication
OUT break supervision time.
50.04 FBA REF1 Position Selects the fieldbus reference 1
MODESEL scaling.

drives
50.05 FBA REF2 Velocity Selects the fieldbus reference 2
MODESEL scaling.

adapter module.
51.02 FBA PAR2 14 (= PNIO PdriveM) Selects the PROFINET IO protocol
(PROTOCOL/PROFILE) and PROFIdrive positioning mode.
51.03 FBA PAR3 0 (= Auto2) Ethernet communication rate is
device.
51.04 FBA PAR4 0 (= Static IP) Configuration will be obtained from
(IP CONFIGURATION) parameters 05...13 or from the PLC
52.01 FBA DATA IN1 4 (= SW 16bit)1) Status word

52.02 FBA DATA IN2 15 (= Act1 32bit) Actual value 1
53.02 FBA DATA OUT2 12 (= Ref1 32bit) Reference 1
51.27 FBA PAR REFRESH Validates the FENA-11 configuration

REFRESH parameter settings.
10.01 EXT1 START FBA Selects the fieldbus interface as the

FUNC source of the start and stop
location 1.
22.01 SPEED FB SEL Enc1 speed2) Selects the actual speed measured
by encoder 1 as the speed
feedback.
34.02 EXT1 MODE P.FBA MAIN CW.26 Selects the source for external 1
1/2SEL control mode 1/2 selection.
Selection is done by
START_HOMING bit (bit 26 in the
fieldbus Control word).
Mode 1: Position, Mode 2: Homing
34.03 EXT1 CTRL Position Selects position control as the
location 1.

drives
34.04 EXT1 CTRL Homing Selects homing control as the
location 1.
62.01 HOMING CAN Methodxx Selects the homing mode. Select the
METHOD appropriate CAN Method.
62.03 HOMING START C.False Selects the fieldbus as the homing
start source.
65.01 POS Fieldbus Position reference and speed are
REFSOURCE read from the fieldbus.
65.03 POS START 1 C.False Selects the fieldbus as the position
start1source.
65.04 POS REF 1 SEL FBA REF 1 Selects the FBA reference 1 as the
position reference source.
65.11 POS START 2 C.False Selects the fieldbus as the position
start2 source.
65.22 PROF VEL REF FBA REF2 Selects the FBA reference 2 as the
SEL velocity reference source.
66.05 POS ENABLE C.False Selects the fieldbus as the source
for enabling the position reference
generator.
70.03 POS REF ENA C.False Selects the fieldbus as the source
for the position reference enable
command.
1)
Read
only or automatically detected/set
2)
Example
The position set point is scaled as follows:

Drive parameter Setting
60.05 POS UNIT (Position unit) m1)
60.08 POS2INT SCALE 1001)
1) Example
The position set point and actual values are scaled with the above
example values as follows:
1000 / 100 = 10.00 m
60.05 POS UNIT

Physical value
60.06 POS2INT SCALE

Set point value
Example for velocity set point scale:

Drive Name Value Description
parameter
60.10 POS SPEED UNIT u/s1) Unit/s (in this case m/s)
60.11 POS SPEED2INT 1001) Scales position speed values to
integer values.
Selections:
1/10/100/1000/10000/100000
1 ) Example
The velocity set point and actual values are scaled with the above
example values as follows:
1000 / 100 = 10.00 m
60.10 POS SPEED UNIT

Physical value
60.11 POS SPEED2INT
Set point value
Pay attention to the following parameters:

Group Description
90 Encoder selection
91/92/93 Settings of the encoder
The start sequence for the above parameter example is given

below:
Control word:
• 406h (1030 decimal) –> READY TO SWITCH ON
• 40Fh (1039 decimal) –> OPERATING
• 43Fh (1087 decimal) –> OPERATING (Do reject traversing
task with no intermediate stop)
• 47Fh (1151 decimal) –> OPERATING (Activate traversing
task)
• C0Fh (3087 decimal) –> OPERATING (Start Homing
procedure)

communication profile with PPO Type 4
application that uses the ABB Drives profile. From the PLC
programming point, the ABB Drives profile is similar to the
PROFIdrive profile shown in the first example.
(4E20h) corresponds to the reference set by parameter 25.02
SPEED SCALING in the forward and reverse directions.
(2710h) corresponds to the reference set by parameter 32.04
TORQUE REF 1 MAX in the forward and reverse directions.
Out Control Speed Torque N/A N/A N/A
word reference reference
In Status Speed actual Torque actual N/A N/A N/A
word value

drives
50.02 COMM LOSS FUNC Fault Enables fieldbus communication
fault monitoring.
50.03 COMM LOSS T OUT 3.0 s Defines the fieldbus
communication break
supervision time.
MODESEL scaling.
50.05 FBA REF2 Torque Selects the fieldbus reference 2
MODESEL scaling.

adapter module.
51.02 FBA PAR2 11 (= PNIO ABB Pro) Selects the PROFINET IO
(PROTOCOL/PROFILE) protocol and the ABB Drives
profile.
device.
51.04 FBA PAR4 0 (= Static IP) Configuration will be obtained
(IP CONFIGURATION) from parameters 05…13 or from
52.01 FBA DATA IN1 4 (= SW 16bit)1) Status word (PZD 1)


settings.

drives
location 1.
location 2.
24.01 SPEED REF1 SEL FBA REF 1 Selects the fieldbus reference 1
reference 1.
32.02 TORQ REF ADD SEL FBA REF 2 Selects the fieldbus reference 2
as the source for torque
reference 1.
34.01 EXT1/EXT2 SEL P.FBA MAIN CW.15 Enables external control location
1/2 selection through the
fieldbus only (bit 15 in the
fieldbus Control word).
control location 1.
34.05 EXT2 CTRL MODE1 Torque Selects torque control as the
control location 2.
1)
2) Example

below.
Control word:

action.
the tables below.
53.01.

19.01 Speed scaling in the forward and reverse directions.
Out Control Speed Acceleration Deceleration time1)
word reference time1)
In Status Speed Actual Power1) DC bus voltage1)
word value
1) Example

ACS850/ACQ810
drives
module.
fault monitoring.
50.03 Comm loss t out 3.0 s2) Defines the fieldbus communication
break supervision time.
scaling.

adapter module.
51.02 FBA par2 10 (= PNIO Pdrive) Selects the PROFINET IO protocol
(PROTOCOL/PROFILE) and the PROFIdrive profile.

ACS850/ACQ810
drives
51.03 FBA par3 0 (= Auto2) Ethernet communication rate is
device.
51.04 FBA par4 0 (= Static IP) Configuration will be obtained from
(IP CONFIGURATION) parameters 05…13 or from the PLC
52.01 FBA data in1 4 (= SW 16bit)1) Status word

52.02 FBA data in2 5 (= Act1 16bit) Actual value 1 (speed)
53.01 FBA data out1 1 (= CW 16bit)1) Control word
53.02 FBA data out2 2 (= Ref1 16bit) Reference 1 (speed)

10.01 Ext1 start func FB Selects the fieldbus interface as the

source of the start and stop
location 1.
21.01 Speed ref1 sel FBA ref1 Selects the fieldbus reference 1 as
(ACS850) the source for speed reference 1.
21.01 Speed ref sel FBA ref1
(ACQ810)
1)
2) Example

below.
Control word:

action.
parameter 51.02 Protocol/Profile and configure the network
settings with parameters 51.03…51.13.
53.01.


Speed control using PROFIdrive communication
46.10 Speed scaling in the forward and reverse directions.
Out Control Speed Acceleration time1) Deceleration time1)
word reference
In Status Speed actual Power1) DC bus voltage1)
word value
1) Example

drives
module.
type and scaling.
50.07 FBA A act1 type 0 = Auto Selects the actual value type and
scaling according to the currently
active Ref1 mode defined in
parameter 50.04.
adapter module.
51.02 Protocol/Profile 10 = PNIO Pdrive Selects the PROFINET IO
protocol and the PROFIdrive
profile.
device.
51.04 IP configuration 0 = Static IP Configuration will be obtained
from parameters 05…13 or from
52.01 FBA data in1 4 = SW 16bit1) Status word

52.02 FBA data in2 5 = Act1 16bit Actual value 1
52.03 FBA data in3 P.1.14 Output power
52.05 FBA data in5 P.1.11 DC voltage
53.01 FBA data out1 1 = CW 16bit1) Control word
53.02 FBA data out2 2 = Ref1 16bit Reference 1 (speed)
53.03 FBA data out3 P.23.12 Acc time 1
53.05 FBA data out5 P.23.13 Dec time 1

19.12 Ext1 ctrl mode1 2 = Speed Selects speed control as the

control mode 1 for external control
location 1.

drives
20.01 Ext1 commands 8 = Fieldbus A Selects the fieldbus A interface as
location 1.
1.
1)
2)
Example
Configuring the master station

master station must be prepared for communication with the
module. Examples of an ABB AC500 PLC and Siemens SIMATIC
S7 PLC are given below. If you are using another master system,
refer to its documentation for more information.
The examples can be applied to all drive types compatible with the
module.
Downloading the GSD file

Configuration of the master station requires a type definition (GSD)
file. In PROFINET IO, the GSD file is written in XML-based
language called GSDML.
Download the FENA GSD file from the Document library
(www.abb.com/drives). The file name format is GSDML-Vx.x-
ABB-FENA-yyyymmdd.xml.
The GSD file describes the vendor-specific and PROFIdrive-
specific features of the adapter module. Vendor-specific features
can be used, for example, in the ABB Drives communication
profile. The PROFIdrive profile supports a set of services
described in the PROFIdrive specification.
Configuring an ABB AC500 PLC

This example shows how to configure communication between an
ABB AC500 PLC and the adapter module using the Control Builder
Plus PS501, software version 2.1.0 and later.
Before you start, make sure that you have downloaded the FENA
GSD file from the Document library.
1. Start the ABB Control Builder software.
2. On the Tools menu, select Device Repository.
3. In the window that opens, click Install... and browse for the
GSD file.
4. Open or create the PLC project that is used to control the

drive.
5. Add the CM579-PNIO PROFINET master device to the PLC
project, if necessary.
6. Add the FENA module to the PROFINET IO network.
7. Add the I/O module, for example, PPO Type 4 to the FENA
module to define cyclical communication between the module
and the PLC.
8. Define the CM579-PNIO master properties, such as the IP

address and address settings for slaves.
9. Define the FENA properties:

On the PNIO identification tab, select the IP address and
Subnet mask, and type the Station name. Note: Use only small
letters for the Station name.
10. Return to the CM579-PNIO master properties. On the Assign

station name tab:
• Click Connect to PLC (Login) and select the
communication link used between Control Builder and the
PLC. Then, click Scan slaves to find all PROFINET slaves
connected to the network.
• In the Configure station name box, select the station

name defined for the module in step 9, and then click
Assign station name.
• In the IP address and Network mask boxes, select/type
the IP address and subnet mask defined in step 9, and
then click Assign IP configuration.
11. Define the I/O module properties:

• On the PNIO parameters tab, configure the Stop mode
and Control-zero mode functionalities, and define fail safe
values for the PLC output process data (PZDs).
• On the PNIO Module I/O Mapping tab, type names for the
variables that refer to the drive's signals in the PLC
program.
12. Open the PLC program and create a program that controls the
drive.
13. Compile the project and download it to the PLC.
Note: Make sure that the variable names defined for the
drive's signals are used in the PLC program. Otherwise the
communication will not work.
Configuring a Siemens SIMATIC S7 PLC

This example shows how to configure communication between a
Siemens SIMATIC S7 PLC and the adapter module using SIMATIC
Manager Step 7.
Before you start, make sure that you have downloaded the FENA
GSD file from the Document library.
1. Start the SIMATIC manager and open/create a SIMATIC
program.
2. Open the hardware configuration of the project.
3. Install the FENA GSD file:

• On the Options menu, select Install GSD Files.
• Browse for the GSD file downloaded from the Document
library and click Install.
4. Click and drag the FENA object from the device catalog to the
Ethernet (1): PROFINET-IO-System.
5. Click and drag the PP0 Type 7 object to Slot 1.

Then, double-click FENA to open the Properties window.
6. On the General tab, type the Device name for the adapter
module.
This is the IP address that

will be assigned to the
adapter module.
You can modify the IP

address by clicking the
Ethernet button.
The IP address will be

assigned by the IO
controller.
7. In the hardware configuration, double-click PPO Type 7 in

Slot 1 to open the Properties window.
8. On the Parameters tab, configure the stop mode and control-
zero mode functionality, and define fail safe values for the PLC
output process data (PZDs).
9. Assign the device name (defined in step 6) to the adapter

module:
• In the hardware configuration, click FENA.
• On the PLC menu, select Ethernet, and then select
Assign Device Name.
• Click the available device with the correct MAC address to

which the device name will be assigned. This will assign
the name to the FENA module. Then click Assign name.
10. Download the hardware configuration to the PLC.

The PLC is now ready for communication with the adapter
module.
PROFINET IO – Communication profiles 291
PROFINET IO –

communication between the PROFINET IO master, the adapter
the master station and the drive.
With the FENA-01/-11 module, the PROFINET network may
employ either the PROFIdrive 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.
292 PROFINET IO – Communication profiles
FENA-01/-11 Drive
Profile selection:
PROFIdrive
1)
Data conversion
ABB Drives
1)
Data conversion
Select Select
PROFINET
Transparent16
CW
REF1 Optional
REF2 16/32 reference/actual
SW -bit value scaling
ACT1
ACT2 Group A Group A
Par. 02 Par. 02
PROFIdrive
positioning
PROFINET 1)
Data conversion
PZDx
•
• 16/32 Transparent32
• -bit
•
PZD10
1) Native profile (eg, DCU or FBA)
Note: The diagram is applicable only when PPO messaging is used. If

Standard Telegrams (ST) are used, the communication profile is selected
automatically.
references and actual values for the PROFIdrive and ABB Drives
communication profiles. Refer to the drive manuals for details on
the native profiles.
PROFIdrive communication profile

The Control word (PROFIdrive parameter 967) is the principal
means for controlling the drive from a fieldbus system. It is sent by
the fieldbus master station to the drive through the adapter
module. The drive switches between its states according to the bit-
coded instructions in the Control word and returns status
information to the master in the Status word (PROFIdrive
parameter 968).
below; see the drive documentation for information on the drive-
specific bits. The drive states are presented on page 298. The
drive states for the positioning mode are presented on page 299.

PROFIdrive communication profile (PROFIdrive parameter 967).
The upper case boldface text refers to the states shown in the
STATE/Description
Bit Name Value
Speed control mode Positioning mode
0 ON 1 Proceed to READY TO OPERATE.
OFF1 0 Emergency OFF, stop by the selected
deceleration ramp. Proceed to OFF1
ACTIVE; proceed further to READY TO
SWITCH ON unless other interlocks
(OFF2, OFF3) are active.
1 OFF2 1 Continue operation (OFF2 inactive).
Proceed to OFF2 ACTIVE; proceed further
to SWITCH-ON INHIBIT.
STATE/Description
Bit Name Value
2 OFF3 1 Continue operation (OFF3 inactive).
0 Emergency stop, stop according to fastest
possible deceleration mode. Proceed to
OFF3 ACTIVE; proceed further to
SWITCH-ON INHIBIT.
mode.
3 OPERATION_ 1 Proceed to ENABLE OPERATION.
ENABLE
INHIBIT.
4 ENABLE_ 1 Normal operation. Normal operation.
RAMP_ Proceed to RAMP Do not reject
GENERATOR FUNCTION traversing task.
or GENERATOR:
TRAVERSING ENABLE OUTPUT.
_TASK 0 Stop according to Reject traversing
selected stop type. task.
5 1 Normal operation. Normal operation.
Proceed to RAMP No intermediate
FUNCTION stop.
GENERATOR:
ENABLE
ACCELERATOR.
0 Halt ramping (Ramp Intermediate stop
Function Generator
output held).
STATE/Description
Bit Name Value
6 1 Normal operation. Activate traversing
Proceed to task (0 –> 1). This is
OPERATING. a toggle bit; each
Note: This bit is rising edge of signal
effective only if the enables a traversing
fieldbus interface is task or a new set
set as the source for point.
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 INHIBIT.
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 JOGGING_1 Jogging 1 (Not supported by all drive types)
9 JOGGING_2 Jogging 2 (Not supported by all drive types)
10 REMOTE_ 1 Fieldbus control enabled
CMD
0 Control word <> 0 or reference <> 0: Retain
last Control word and reference.
Control word = 0 and reference = 0:
Fieldbus control enabled.
11 1 Vendor-specific bit Start homing
as defined by procedure.
PROFIdrive
0 Stop homing
parameter 933
procedure.
12 Vendor-specific bit as defined by
PROFIdrive parameter 934
STATE/Description
Bit Name Value

The table below shows the contents of the Status word for the
PROFIdrive communication profile (PROFIdrive parameter 968).
The upper case boldface text refers to the states shown in the
STATE/Description
Bit Name Value
0 OFF1 ACTIVE
2 RDY_REF 1 ENABLE OPERATION
0 DISABLE OPERATION
3 TRIPPED 1 FAULT
0 No fault
0 OFF2 ACTIVE
0 OFF3 ACTIVE
6 SWC_ON_INH 1 SWITCH-ON INHIBIT ACTIVE
IB
0 SWITCH-ON INHIBIT NOT ACTIVE
0 No Warning/Alarm
STATE/Description
Bit Name Value
8 AT_SETPOINT 1 OPERATING. Actual value equals
reference value (= is within tolerance
limits).
0 Actual value differs from reference value
(= is outside tolerance limits).
9 REMOTE 1 Drive control location: REMOTE
10 1 Actual frequency or Target position
speed value equals reached.
or is greater than
supervision limit.
0 Actual frequency or Not at target
speed value is position
within supervision
limit.
11 1 Vendor-specific bit Homing procedure
as defined by was executed and is
PROFIdrive valid.
parameter 939
0 No valid home
position available.
12 1 Vendor-specific bit Traversing task
as defined by acknowledgement
0
PROFIdrive (0 –> 1)
parameter 940
13 1 Vendor-specific bit Drive stopped.
as defined by
0 Drive moving.
PROFIdrive
Traversing task is
parameter 941
executed (n <> 0).
State machine for all operating modes

The general PROFIdrive state machine for all operating modes is
shown below.
SWITCH-ON PROFIdrive
MAINS OFF INHIBIT (SW Bit6=1)
State machine
Power ON OFF1 (CW Bit0=0)
CW = Control word
NOT READY SW = Status word
TO SWITCH ON (SW Bit0=0)
A B C D n = Speed
I = Input current
(CW=xxxx x1xx xxxx x110) RFG = Ramp function
(CW Bit3=0) generator
f = Frequency
READY TO
INHIBIT (SW Bit2=0) from any state
operation ON (CW=xxxx x1xx xxxx x111) Fault
inhibited
FAULT
READY TO Main contactor ON (SW Bit3=1)
from any state OPERATE (SW Bit1=1)
(CW Bit7=1)
OFF1 (CW Bit0=0)
OFF1 from any state from any state

ACTIVE (SW Bit1=0)
Emergency stop Emergency stop
Enable operation OFF3 (CW Bit2=0) OFF2 (CW Bit1=0)
n(f)=0 / I=0 (CW Bit3=1)
OFF3 OFF2
ACTIVE (SW Bit5=0) ACTIVE (SW Bit4=0)
B C D
F n(f)=0 / I=0 Main contactor OFF
(CW Bit4=0)
SPEED MODE ONLY
ENABLE
OPERATION (SW Bit2=1)
C D (CW Bit4,5,6=0)
A
E
(CW Bit5=0) (CW Bit4=1)
Jogging 1 or 2 ON
D RFG: ENABLE (CW Bit8=1 or Bit9=1)
OUTPUT
(CW Bit6=0) B JOGGING 1 or 2
(CW Bit5=1) ACTIVE
Jogging 1 or 2 OFF
RFG: ENABLE (CW Bit8=0 or Bit9=0)
state ACCELERATION
C Jogging pause
condition (CW Bit6=1)
rising edge OPERATING ‘n=0 or f =0’ and ‘I=0’

of the bit (SW Bit8=1) and pause expired
D F
State machine for the positioning mode

The PROFIdrive state machine for the positioning mode is shown
below.
F
BASIC STATE:
Operating1) (SW Bit10,13=1)
E
(CW Bit4,5=1
and (CW Bit11=1)
CW Bit6
edge 0⇒1)
HOMING
RUNNING (SW Bit10,11,13=0)
HOMING
READY (SW Bit10,11,13=1)
(CW Bit11=0)
F F
Traversing task
active (SW Bit10,13=0) PROFIdrive
State machine
F
(CW Bit6 edge (CW Bit5=0) for PROFIdrive
0⇒1) positioning mode
Braking with
ramp (SW Bit10,13=0)
CW= Control word
SW = Status word
Intermediate
stop
E State
(CW Bit5=0) condition
1)In the “Operating”

(CW Bit4=0)
state of the general
state machine:
Braking with SW bits 0, 1 and 2 = 1
ramp (SW Bit10,13=0) SW bit 6 = 0.
F
References
have the drive controlled through PROFINET, the communication
module must be defined as the source for control information, for
example, reference.
References in speed control mode

In the speed control mode, references are 16-bit or 32-bit words
containing a sign bit and a 15-bit or 31-bit integer. A negative
reference (indicating reversed direction of rotation) is formed by
calculating the two’s complement from the corresponding positive
reference.
A 16-bit speed reference (REF or NSOLL_A) in hexadecimal
(0…4000h) corresponds to 0…100% of Maximum Reference (as
defined with a drive parameter).
A 32-bit speed reference (NSOLL_B) in hexadecimal (0…4000
0000h) corresponds to 0…100% of Maximum Reference (as
defined with a drive parameter).
References in positioning mode (ACSM1 only)

In the positioning mode, references are 16-bit or 32-bit words. A
32-bit reference contains a sign bit and a 31-bit integer. A negative
reference (indicating reversed direction of rotation) is formed by
calculating the two’s complement from the corresponding positive
reference.
For a 32-bit position reference (XSOLL_A), the unit and scaling are
defined with drive parameters (for example, POS UNIT, POS2INT
SCALE and FEED CONST).
For a 32-bit velocity reference (VELOCITY_A), the unit and scaling
are defined with drive parameters (for example, POS SPEED UNIT
and POS SPEED2INT).
Actual values
Actual values are 16-bit or 32-bit words containing information on
the operation of the drive. The functions to be monitored are
selected with a drive parameter.
Actual values in speed control mode

The scaling of 16-bit actual speed values (ACT or NIST_A) in
hexadecimal (0…4000h) corresponds to 0…100% of Maximum
Reference (as defined with a drive parameter).
The scaling of 32-bit actual speed values (NIST_B) in hexadecimal
(0…4000 0000h) corresponds to 0…100% of Maximum Reference
(as defined with a drive parameter).
Actual values in positioning mode (ACSM1 only)

For a 32-bit actual position value (XIST_A), the unit and scaling
are defined with drive parameters (for example, POS UNIT,
POS2INT SCALE and FEED CONST).

from a fieldbus system. It is sent by the fieldbus master station to
the drive through the adapter module. The drive switches between
its states according to the bit-coded instructions in the Control
word and returns status information to the master in the Status
word.

refers to the states shown on page 306.
CONTROL
CONTROL
CONTROL
INHIBITED.
Warning: Ensure that motor and driven
mode.

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.
ENABLED.
ENABLED.
output held).
ZERO OPERATING.
zero.
7 RESET 0 –> 1 Fault reset if an active fault exists.
Proceed to SWITCH-ON INHIBITED.
8…9 Reserved

10 REMOTE_ 1 Fieldbus control enabled
CMD
12… Drive-specific (For information, see the drive documentation.)
15

to the states shown on page 306.
0 OFF1 ACTIVE
3 TRIPPED 1 FAULT
0 No fault
0 OFF2 ACTIVE
0 OFF3 ACTIVE
INHIB
0 –

0 No warning/alarm
8 AT_SETPOINT 1 OPERATING. Actual value equals
reference (= is within tolerance limits, ie,
in speed control, speed error is 10%
max. of nominal motor speed).
outside tolerance limits).
9 REMOTE 1 Drive control location: REMOTE (EXT1
or EXT2)
10 ABOVE_ 1 Actual frequency or speed equals or
LIMIT exceeds supervision limit (set by drive
parameter). Valid in both directions of
rotation.
0 Actual frequency or speed within
supervision limit
LOC
0 External Control Location EXT1 selected
ENABLE
0 No External Run Enable signal received
13… Drive-specific (For information, see the drive documentation.)
14
15 FBA_ERROR 1 Communication error detected by
fieldbus adapter module
State machine
shown below.
SWITCH-ON
MAINS OFF INHIBITED (SW Bit6=1) ABB Drives
communication
profile
NOT READY TO
SWITCH ON CW = Control word
A B CD (SW Bit0=0)
SW = Status word
n = Speed
READY TO generator
OPERATION SWITCH ON (SW Bit0=1) f = Frequency
from any state
inhibited Fault
READY TO FAULT

ACTIVE (SW Bit1=0)
and
B C D ACTIVE ACTIVE (SW Bit4=0)
(SW Bit5=0)
(CW Bit4=0) n(f)=0 / I=0
C D OPERATION
ENABLED (SW Bit2=1)
A
D RFG: OUTPUT
ENABLED
B
RFG: ACCELERATOR state

ENABLED
C
rising edge
OPERATION
D
References
reference.
Scaling
minimum reference.
Fieldbus Drive
REF1: 20000
REFx MIN
0 -(REFx MIN)

REF1: -20000
Actual values
Scaling
Fieldbus Drive

ACT1: 20000
0 0

ACT1: -20000
PROFINET IO – Communication protocol 309
PROFINET IO –
Communication protocol

This chapter describes the PROFINET IO communication protocol
for the adapter module. For detailed information on PROFINET IO
communication, refer to PROFINET specification Application Layer
protocol for decentralized periphery and distributed automation
v2.0.
PROFINET IO
PROFINET IO is a fieldbus protocol that enables communication
between programmable controllers and distributed field devices in
an Ethernet network. The protocol classifies devices into I/O
controllers, I/O supervisors and I/O devices, which have a specific
collection of services.
310 PROFINET IO – Communication protocol
PROFINET IO uses three different communication channels to

exchange data:
• The standard UDP/IP and TCP/IP channel is used for
parameterization and configuration of devices and for acyclic
operations.
• The real time (RT) channel is used for cyclic data transfer and
alarms.
• The isochronous real time (IRT) channel is used, for example,
in motion control applications (not implemented in FENA-01/-
11).
PROFINET IO devices are structured in slots and sub-slots, which
can contain modules and sub-modules correspondingly. A device
can have almost any number of slots and sub-slots, and they can
be virtual or real. Device-specific data is represented in slot 0;
module-specific and sub-module-specific data in subsequent slots
and sub-slots.
One of the benefits of PROFINET IO is the diagnostics and alarm
mechanism. Every module and sub-module provide alarm data to
the I/O controller using the cyclic channel. Diagnostic data can be
read non-cyclically from the device by using record data.
The properties and services of a PROFINET IO device are
described in a GSD file written in GSDML (General Station
Description Markup Language). The GSD file describes the
device-specific modules and the method of assigning modules and
sub-modules to predefined slots and sub-slots. For more
information, see section Downloading the GSD file on page 276.
PROFINET IO in FENA-01/-11
When PROFINET IO is selected as the communication protocol,
the FENA-01/-11 module can employ the ABB Drives, Transparent
16 and Transparent 32 communication profiles or the PROFIdrive
profile. You can select the profile with a GSD file in a PROFINET
IO hardware configuration tool. You can select the appropriate
device access point (DAP) and functional module with the tool as
well.
The FENA-01/-11 module uses slots 0 and 1. Slot 0 does not have
any sub-slots, and the DAP module attached to it represents the
device itself. Other functional modules and sub-modules described
in the GSD file can be assigned to slot 1 and its sub-slots.
In the ABB Drives and Transparent profiles:
• Slot 0 = Device access point (DAP)
• Slot 1, sub-slot 1 = Vendor object (PPO types)
• Slot 1, sub-slot 1 = Acyclic parameter access (MAP/PAP)
In the PROFIdrive profile:
• Slot 0 = Device access point
• Slot 1 = Drive object
• Slot 1, sub-slot 1 = Acyclic parameter access (MAP/PAP)
• Slot 1, sub-slot 2 = Standard telegram 1
• Slot 1, sub-slots 3…18 = Freely configurable inputs and
outputs
The adapter module provides the following services:
• Cyclic messaging
• Acyclic parameter access mechanism
• Identification & Maintenance functions (I&M)
• PROFIdrive parameters (limited in the ABB Drives and
Transparent profiles)
• Diagnostic and alarm mechanism (only with the PROFIdrive
profile)
• Fault buffer mechanism (limited in the ABB Drives and
Transparent profiles).
Cyclic message types
PPO types
Process data
Parameter
Parameter
Fixed area Freely mappable area
identification
channel
OUT area IND VALUE CW REF PZD3 PZD4 PZD5 PZD6 PZD7 PZD8 PZD9 PZD10 PZD11 PZD12
IN area ID IND VALUE SW ACT PZD3 PZD4 PZD5 PZD6 PZD7 PZD8 PZD9 PZD10 PZD11 PZD12
PKW PZD
Type 3 DP-V1
Type 4 DP-V1
Type 6 DP-V1
Type 71) DP-V1
OUT area – Data sent from master to slave (control data)

IN area – Data sent from slave to master (actual data)
Parameter identification:
ID – Parameter identification
IND – Index for arrays
VALUE – Parameter value (Max. 4 bytes)
PKW – Parameter ID/value
Process data:
CW – Control word
SW – Status word
REF – Reference
ACT – Actual value
PZD – Process data (application-specific)
DW – Data word
1)
Not supported by ACS355 drives
Standard telegram (ST) types (DP-V1)

ST1 PZD1 PZD2
OUT area STW1 NSOLL_A
Control word 1 Speed set point A
IN area ZSW1 NIST_A
Status word 1 Speed actual value A
ST2 PZD1 PZD2…3 PZD4

OUT area STW1 NSOLL_B STW2
Control word 1 Speed set point B Control word 2
IN area ZSW1 NIST_B ZSW2
Status word 1 Speed actual Status word 2
value B
Note: For the contents of the Control word, the Status word,
references and actual values, see chapter PROFINET IO –
Communication profiles.
Parameter handling using acyclic parameter

access mechanism (DP-V1)
PROFINET IO offers record read and write services for the acyclic
parameter access mechanism. When the drive parameters or
FENA-01/-11 parameters are accessed, the corresponding slot,
sub-slot and index are set, and a PROFIdrive DP-V1 message is
placed on the data block of the record read or write frame.
Header and frame structures

PROFINET IO uses the DCE RPC (Distributed Computing
Environment Remote Procedure Call) protocol for acyclic read and
write services. I/O controllers and supervisors take care of
formulating most of the request frames. However, it is possible that
handling the PROFIdrive request and response headers must be
performed in the application logic. The acyclic frame structure,
headers and error codes are described further below.
Frames Dest Src Ether IP RPC NDR Read Data
addr. addr. type UDP or
Write
Bytes 6 6 2 28 80 20 64 ...
Dest addr. and Src addr. are the destination and the source of the
communication relationship. The addresses are in hexadecimal
format, for example, 00-30-11-02-57-AD.
Ether type is 0x800 for non-real-time communication.
IP and UDP fields contain the IP address of the source and the
destination as well as the communication ports and length of the
message.
RPC contains, for example, the read or write service ID, interface
description and selected objects.
NDR request block describes the length of the following data block.
The response block also contains bytes ErrorCode, ErrorDecode,
ErrorCode1 and ErrorCode2 for presenting the status of the
request. The response error codes are listed in the table below.
Byte Value and meaning
ErrorCode 0xDF (Error Write)
0xDE (Error Read)
ErrorDecode 0x80 (PNIORW) ErrorCode1 decoded as shown in the
table on page 315. ErrorCode2 is 0.
0x81 (PNIO) ErrorCode1 and ErrorCode2 decoded as
shown in the table on page 315.
ErrorCode1 Error class and error code. See the table on page 315.
ErrorCode2 Not described here
The table below lists the ErrorCode1 with PNIORW decoding.
MSB x x x x x x x x LSB
Error class Meaning Error code

0…9 (Reserved)
10 (0x0A) Application 0 = Read error
1 = Write error
2 = Module failure
3…7 = Reserved
8 = Version conflict
9 = Feature not supported
10…15 = User-specific
11 (0x0B) Access 0 = Invalid index
1 = Write length error
2 = Invalid slot
3 = Type conflict
4 = Invalid area
5 = State conflict
6 = Access denied
7 = Invalid range
8 = Invalid parameter
9 = Invalid type
12 (0x0C) Resource 0 = Read constraint conflict
1 = Write constraint conflict
2 = Resource busy
3 = Resource unavailable
4…7 = Reserved
13…15 User-specific
DP-V1 read/write request sequence

A read/write service on a drive parameter is illustrated below.
Master DP-V1 Slave
PROFIdrive Write request DB47 Parameter request
Parameter
request
Write response
without data
Read request DB47

without data
Parameter
Read response (–) processing
without data
Read request DB47

without data
PROFIdrive Read response

Parameter with data Parameter response
response
The messaging employs DP-V1 data units. The PROFIdrive

parameter request is included within the DP-V1 request as data.
Likewise, the DP-V1 response contains the PROFIdrive parameter
response as data.
A write request is first sent containing the parameter request. If the
write request is valid, the adapter module acknowledges it with a
DP-V1 write response with no data. The master will then send a
read request. If the adapter module is still busy performing the
internal parameter request, it will return a negative response with
the DP-V1 error code B5h (State conflict). In this case, the read
request will be repeated by the master until the adapter module
has the PROFIdrive response data ready.
If the write request is invalid, a negative response is returned with
a DP-V1 error code (see the table on page 315).
Read and write blocks

A read block is used in read requests and responses, while a write
block is used in write requests and responses. A request consists
of unique identifiers for the connection, addressing information and
the length of the record data. A response also contains two
additional fields for transferring information.
The table below shows the structure of the read and write blocks in
detail.
Field(s) Description Range Type
Service Request or Response Request (0x00) UI8
service Response (0x80)
Operation Read or Write operation Write (0x08) UI8
Read (0x09)
Block length Length of the block 0…0xFFFF UI16
ARUUID Identifier
• time low UI32
• time mid UI16
• time high and version UI16
• clock Octet[2]
• node Octet[6]
API Application process Device access UI32
identifier point (0x0000)
PROFIdrive
(0x3A00)
Slot Slot of the module 0x01 UI16
access point
(MAP/PAP)
Subslot Subslot of the module 0x01 UI16
access point
(MAP/PAP)
Padding 2 bytes
Index Index of the record data 0x2F UI16
object 0xB02E
0xB02F
Data length Length of the data block 0…0xFFFFFFFF UI32
Field(s) Description Range Type

Additional value 1 Field for transferring UI16
(response only) additional data
Additional value 2 Field for transferring UI16
(response only) additional data
Padding 24 bytes for request, 20 bytes for response.
Data block Used only with write request and read response.
Data block
The data block contains a PROFIdrive-specific request or
response header.
The table below shows the contents of the PROFIdrive request.
Field(s) Description Range Byte/
Word
Request Unique identification set 1…255 Byte
Reference by the master. Changed
for each new request.
Request ID Request type for the Request Byte
issued block Parameter (01h)
Change
Parameter (02h)
Drive Object To be set to 0 or 1. 0…255 Byte
ID
No. of Number of the 1…37 Byte
Parameters parameters that are
present in the request
Attribute Type of the object being Value (10h) Byte
accessed Description (20h)
Note: “Description” and Text (30h)
“Text” are not supported.
No. of Number of the array 0, 1…234 Byte
Elements elements accessed or
length of the string
accessed. Set to 0 if non-
array parameters are
used.
Field(s) Description Range Byte/

Word
Parameter Address of the parameter 1…65535 Word
Index that is being accessed.
“0” is allowed by
FENA-01/-11.
Subindex Addresses 0…65535 Word
• the first array element
of the parameter or
• the beginning of a
string access or
• the text array or
• the description
element that is being
accessed
Format1) See the table on page See the table on Byte
321. page 321.
Number of Number of the values 0…234 Byte
Values1) following
Values1) The values of the – See the
request. In case of an odd Format
number of bytes, a zero field.
byte is appended to
ensure the word structure
of the telegram.
1) Only
if Request ID is 02h (Change Parameter). The Format, Number of
Values and Values fields are repeated for other parameters.
The table below shows the contents of the PROFIdrive response.

Field(s) Description Range
Request Mirrored from the request. 1…255
Reference
(mirrored)
Response ID Response from the slave. In Request Param OK
case any requested services fail, (01h)
a “not acknowledged” (NAK) Request Param NAK
response will be indicated. (81h)
Change Param OK
(02h)
Change Param NAK
(82h)
Drive Object To be set to 1. 0…255
ID
No. of Number of the parameters that 1…37
Parameters are present in the response
Format1) See the table on page 321. See the table on page
321.
Number of Number of the values following 0…234
Values1)
Values1) The values of the request. In –
case of an odd number of bytes,
a zero byte is appended to
ensure the word structure of the
telegram.
1) Only
if Response ID is 01h (Request Parameter OK). The Format,
Number of Values and Values fields are repeated for other parameters.
The table below shows the data types for the Format field in the
PROFIdrive response.
Code Type
0x00 (Reserved)
0x01…0x36 Standard data types
1 Boolean (not supported)
2 Integer8 (not supported)
3 Integer16
4 Integer32
5 Unsigned8 (not supported)
6 Unsigned16
7 Unsigned32
8 Floating point (not supported)
9 Visible string (not supported)
•••
0x37…0x3F (Reserved)
0x40 Zero
0x41 Byte
0x42 Word
0x43 Double word
0x44 Error
0x45…0xFF (Reserved)
The table below shows the PROFIdrive parameter request error

codes.
Error # Meaning Used at
00h Impermissible Access to an unavailable parameter
parameter number
01h Parameter value cannot Change access to a parameter value
be changed that cannot be changed
02h Low or high limit Change access with a value outside
exceeded the limits
03h Invalid subindex Access to an unavailable subindex
04h No array Access with a subindex to a non-
indexed parameter
05h Incorrect data type Change access with a value that
does not match the data type of the
parameter
06h Setting not permitted Change access with a value unequal
(can only be reset) to 0 when this is not permitted
07h Description element Change access to a description
cannot be changed element that cannot be changed
09h No description data Access to an unavailable description
available (parameter value is available)
0Bh No operation priority Change access rights without rights
to change parameters
0Fh No text array available Access to a text array that is not
available (Parameter value is
available.)
11h Request cannot be Access is temporarily not possible
executed because of for reasons that are not specified in
operating mode detail.
14h Value impermissible Change access with a value that is
within limits but is not permissible for
other long-term reasons (parameter
with defined single values)
15h Response too long The length of the current response
exceeds the maximum transmittable
length.

16h Parameter address Illegal value or value that is not
impermissible supported for the attribute, number
of elements, parameter number or
sub-index, or a combination
17h Illegal format Write request: Illegal format or
format of parameter data that is not
supported
18h Number of values Write request: Number of values of
inconsistent the parameter data does not match
the number of elements at the
parameter address.
65h…FF Manufacturer-specific –
error area
65h Vendor-specific error Vendor-specific error
66h Request not supported Request not supported
67h Communication error Request cannot be completed
because of a communication error.
6Eh Non-volatile error Failure during write to non-volatile
memory
6Fh Time-out error Request aborted because of a
timeout.
78h PZD map failure Parameter cannot be mapped to
PZD (size mismatch or non-
existent).
79h PZD memory failure Parameter cannot be mapped to
PZD (out of memory).
7Ah Multiple PZD map Parameter cannot be mapped to
PZD (multiple PZD write).
82h Control word bit map Cannot map Control word bit
(parameter 933…937, eg, double
mapping of bits).
8Ch Set torque mode error Cannot change mode to TORQUE
(frequency is used).
90h Illegal Request ID The request ID of the response is
illegal.

96h Internal buffer Buffer overflow
A0h Internal communication Communication error between the
module and the drive
Function blocks for sending DP-V1 messages

(Siemens S7)
In IEC 61131-3 compatible systems, function blocks are available
for accessing data non-cyclically. In Siemens S7, SFB 52
"RDREC" can be used for reading and SFB53 "WRREC" for
writing data records as follows:
• On INDEX: Connect the value 0xB02F, 0xB02E or 0x2F.
• On Write record: Set the length of the DP-V1 write request to
MLEN.
• On Read record: Set the maximum length of the DP-V1 read
response.
• Connect the DP-V1 message to RECORD.
RDREC
BOOL --- REQ VALID --- BOOL
DWORD ID BUSY --- BOOL
INT INDEX ERROR --- BOOL
INT MLEN STATUS --- DWORD
LEN --- INT
ANY RECORD-- --RECORD
WRREC
BOOL --- REQ DONE --- BOOL
DWORD --- ID BUSY --- BOOL
INT --- INDEX ERROR --- BOOL
INT --- LEN STATUS --- DWORD
ANY --- RECORD-- --RECORD
For more information on the above function blocks, see document

Communication Function Blocks for PROFIBUS DP and
PROFINET IO v2.0 available at www.profibus.com.
Parameter data transfer examples

The following examples show how parameter data is transferred
using the DP-V1 mechanisms READ and WRITE.
Note: Only the data block part of the request is presented in the
examples. See section Read and write blocks on page 317.
Example 1a: Reading a drive parameter (array

element)
Drive parameters are addressed so that the drive parameter group
corresponds to the Parameter index (PNU), and the drive
parameter number within the group corresponds to the Subindex
(IND). In the following example, a value is read from drive
parameter12.04 (0C.04h).
• DP-V1 Write request (Read parameter value):
Slot number
Subslot number
Index
Data length
Request reference
Request ID (01h= Request Parameter
Drive object ID
Number of parameters
Attribute (10h = Value)
Number of elements
Parameter index
Subindex
DP 01 01 B0 2F 0A 05 01 01 01 10 01 00 0C 00 04
DP trailer
header DP-V1 Command PROFIdrive V3 Parameter Channel
• Positive Read response to DP-V1 Read request:
Slot number
Subslot number
Index
Data length
Response reference (mirrored)
Response ID
Drive object ID
Format (42h = Word)
Number of values
Parameter value
DP 01 01 B0 2F 08 05 01 01 01 42 01 05 64 DP
header DP-V1 Response PROFIdrive V3 Parameter Channel trailer
• Negative response to PROFIdrive Read request:
Slot number
Subslot number
Index
Data length
Response ID
Drive object ID (mirrored)
Format (44h = Error)
Number of values
PROFIdrive error
code
DP 01 01 B0 2F 08 05 01 01 01 42 01 05 64 DP
Example 1b: Reading 3 drive parameters

(multi-parameter)
In this example, three parameters (12.04, 20.08 and 30.19) are
read using one telegram.
• DP-V1 Write request (Read parameter value):
Slot number
Subslot number
Index
Data length
Request reference
Request ID (01h= Request Parameter
Drive object ID
Number of elements
Parameter number
Subindex
DP 01 01 B0 2F 16 06 01 01 03 10 01 00 0C 00 04
•••
header DP-V1 Command PROFIdrive V3 Parameter Channel
10 01 00 14 00 08
••• (Par. Channel •••
continued)
10 01 00 1E 00 13
DP
••• (Par. Channel trailer
continued)
• Positive Read response to DP-V1 Read request:
Slot number
Subslot number
Index
Data length
Response ID
Drive object ID
Format (42h = Word)
Number of values
Parameter value
01 01 B0 2F 10 06 01 01 03 42 01 01 90
DP
PROFIdrive V3 Parameter •••
header DP-V1 Response
Channel
42 01 01 F4
••• (Par. Channel •••
cont’d)
42 01 00 30
DP
cont’d)
The values 190h (400), 1F4h (500) and 1Eh (30) are returned.
Example 2a: Writing a drive parameter (one array

element)
Drive parameters are addressed so that the drive parameter group
corresponds to the Parameter index (PNU), and the drive
parameter number within that group corresponds to the Subindex
(IND). In the following example, a value is written to drive
parameter 12.02 (0C.02h).
Slot number
Subslot number
Index
Data length
Request reference
Request ID
Drive object ID
Number of elements
Parameter number
Subindex
Format
(42h = Word)
Number of
values
Value
01 01 B0 2F 0E 07 02 01 01 10 01 00 0C 00 02 42 01 02 58
DP header
DP trailer
DP-V1 Command PROFIdrive V3 Parameter Channel

Slot number
Slot number
Index
Data length
Request reference (mirrored)
Response ID
01 01 B0 2F 04 07 02 01 01
DP DP
header PROFIdrive V3 trailer
DP-V1 Response
Parameter Channel
Example 2b: Writing 2 drive parameters

(multi-parameter)
In this example, the values 300 (12Ch) and 500 (1F4h) are written
to drive parameters 12.02 (0C.02h) and 20.08 (14.08h)
respectively using one telegram.
Slot number
Subslot number
Index
Data length
Request reference
Request ID (02h= Change Parameter)
Drive object ID
Number of elements
Parameter number
Subindex
01 01 B0 2F 14 08 02 01 02 10 01 00 0C 00 02
DP
PROFIdrive V3 Parameter •••
header DP-V1 Command
Channel
••• 10 01 00 14 00 08
•••
(Par. Channel cont’d)
42 01 01 2C
••• •••
(Par. Channel
cont’d)
42 01 01 F4
DP
cont’d)
Value
Number of values
Format (42h = Word)

Slot number
Subslot number
Index
Data length
Response ID
01 01 B0 2F 04 08 02 01 02
DP DP
header PROFIdrive V3 trailer
DP-V1 Response
Parameter Channel
Example 3: Reading a PROFIdrive parameter

In this example, PROFIdrive parameter 919 (397h) is used to read
the device system number of the slave, which is the product code
of the drive.
• DP-V1 Write request (Reading a PROFIdrive parameter):
Slot number
Subslot number
Index
Data length
Request reference
Request ID (01h= Request Parameter)
Drive object ID
Number of elements
Parameter index
Subindex
DP 01 01 B0 2F 0A 09 01 01 01 10 00 03 97 00 00 DP
header DP-V1 Command PROFIdrive V3 Parameter Channel trailer
• DP-V1 Read response:

Slot number
Subslot number
Index
Data length
Response ID
Drive object ID
Format (42h = Word)
Number of values
Value of error
values
DP 01 01 B0 2F 0A 09 01 01 01 07 01 00 00 02 0B DP
The slave returns the product code of the drive (20Bh in this
example).
Example 4: Configuring the process data written to the drive

PROFIdrive parameter 915 (393h) can be used to define which
data is written cyclically to a drive parameter as application-specific
process data.
In the example below, the value of drive parameter 12.06 (0C.06h)
is selected to be taken from PZD3. The parameter will continue to
be updated with the contents of PZD3 in each Request frame until
a different selection is made.
Subindex (IND) defines which process data word the required data
is taken from. Value selects the drive parameter to which that word
is mapped.
• DP-V1 Write request:
Slot number
Subslot number
Index
Data length
Request reference
Request ID (02h = Change
Drive object ID
Number of elements
Parameter number
Subindex
Format (42h =
Word)
Number of
values
Value
01 01 B0 2F 0E 0A 02 01 01 10 01 03 93 00 03 42 01 0C 06
DP header
DP trailer
DP-V1 Command PROFIdrive V3 Parameter Channel


Slot number
Subslot number
Index
Data length
Response ID
Format (42h = Word)
Number of values
Value of error
values
DP 01 01 B0 2F 08 0A 01 01 01 42 01 00 68 DP
Subsequently, the contents of PZD3 in each Request frame are

written to drive parameter 12.06 until a different selection is made.
Example 5: Determining the source of the process data read

from the drive
PROFIdrive parameter 916 (394h) can be used to define which
data is read cyclically from the drive as application-specific process
data. In the example below, the parameter is used to determine
which drive parameter the contents of PZD3 are taken from.
Subindex (IND) defines which process data word the required data
is transmitted in.
• DP-V1 Write request:
Slot number
Subslot number
Index
Data length
Request reference
Request ID (01h = Read)
Drive object ID
Number of elements
Parameter index
Subindex
DP 01 01 B0 2F 0A 0B 01 01 01 10 01 03 94 00 03
DP trailer
header DP-V1 Response PROFIdrive V3 Parameter Channel
Slot number
Subslot number
Index
Data length
Response ID
Format (42h = Word)
Number of values
Value of error
values
DP 01 01 B0 2F 08 0B 01 01 01 42 01 0C 05 DP
Value indicates the source of PZD3 as drive parameter 12.05

(0C.05h).
PROFINET IO – Diagnostics 339
PROFINET IO – Diagnostics

the adapter module when the module is used for PROFINET IO
communication.
340 PROFINET IO – Diagnostics
LED indications
Name Color Function

HOST
PROFINET IO – Diagnostics 341
Name Color Function

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 Recoverable fault
Red Device has an unrecoverable fault. This
may be cleared by a Fieldbus Adapter
MODULE parameter refresh or by cycling drive
power. This may have been caused by
the device detecting another device on
the network with the same MAC ID or IP
address.
Flashing red- Device is in Self Test.
green
Flashing orange Device is blinking. Used for identification.
The blinking is started by the PROFINET
master.
342 PROFINET IO – Diagnostics
Name Color Function

Off Device is not on-line.
• The device has not completed the
Duplicate Address Detection yet.
NETWORK • The device may not be powered; look
at the Module status LED.
Flashing green Device is receiving/transmitting on the
Ethernet.
Technical data 343
Technical data

This chapter contains the technical specifications of the adapter
module and the Ethernet link.
FENA-01/-11
The figure below shows the enclosure of the adapter module from
the front and side.
344 Technical data
Mounting Into the option slot of the drive

Degree of protection IP20
Ambient conditions The applicable ambient conditions specified for
the drive in its manuals are in effect.
Indicators Three bicolor LEDs (HOST, MODULE,
NETWORK)
Connectors 20-pin connector to the drive
RJ-45 connector to Ethernet (X1)
Power supply +3.3 V ±5% max. 400 mA (supplied by the drive)
General Estimated min. lifetime 100 000 h
All materials UL/CSA-approved
Complies with EMC standard EN 61800-3:2004
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: CAT5/6 UTP, CAT5/6 FTP, CAT5/6
STP
• Connector: RJ-45
• Termination: Internal
• Maximum segment length: 100 m / 328 ft
Topology Star
Transfer rate 10 Mbps or 100 Mbps
Serial communication Half or full duplex
type
Protocol Modbus/TCP, EtherNet/IP, PROFINET IO
Appendix A – PROFIdrive parameters of PROFINET IO 345
Appendix A – PROFIdrive
parameters of PROFINET IO

This chapter contains a list of the PROFIdrive parameters for the
PROFINET IO communication protocol.
PROFIdrive parameters
Par. no. R/W1) Data type Description
915 R/W Array [10] Assignment PZD1 to PZD10 in PPO-
Unsigned16 write
916 R/W Array [10] Assignment PZD1 to PZD10 in PPO-
Unsigned16 read
919 R Octet String4 Device system number.
923 R Array [n] List of all parameters for signals.
Unsigned16 Mandatory if process data
normalization is used and/or
parameters 915 and 916 are
implemented.
Signal no. and name Type
1 – Control word 1 Unsigned16
(STW1)
346 Appendix A – PROFIdrive parameters of PROFINET IO

2 – Status word 1 Unsigned16
(ZSW1)
3 – Control word 2 Unsigned16
(STW2)
4 – Status word 2 Unsigned16
(ZSW2)
5 – Speed set point A Signed16
(NSOLL_A)
6 – Speed actual value Signed16
A (NIST_A)
7 – Speed set point B Signed32
(NSOLL_B)
8 – Speed actual value Signed32
B (NIST_B)
27 – Position set point Signed32
A (XSOLL_A)
28 – Position actual Signed32
value A (XIST_A)
32 – Traversing block Unsigned16
selection (SATZANW)
(not supported)
33 – Actual traversing Unsigned16
block (AKTSATZ) (not
supported)
34 – Target position Signed32
(TARPOS_A) (not
supported)
35 – Velocity Unsigned32
(VELOCITY_A)
101…9999 – Drive- –
specific

927 R/W Unsigned16 Operator control rights (parameter
identification, PKW)
Value Mode
0 Parameters cannot be
written, only read (927
can be written).
1 Parameters can be
written and read (default).
928 R/W Unsigned16 Control rights (process data, PZD).
Value Mode
0 PZD part is disabled, ie,
Receipt of new PZD data
is ignored.
1 PZD part is enabled
(default).
929 R Unsigned16 Selected PPO type
Value PPO Configuratio
type n
1 PPO1 F3h, F1h
2 PPO2 F3h, F5h
3 PPO3 F1h
4 PPO4 F5h
5 PPO5 F3h, F9h
6 PPO6 F9h
Note: This parameter is not available if
Standard telegram ST1 or ST2 is
selected.

930 R/W Unsigned16 Selection switch for communication
profile.
Value Mode
1 PROFIdrive
8001h ABB Drives
8002h Transparent 16
8003h Transparent 32
8004h PROFIdrive positioning
mode
933 R/W Unsigned16 Selection switch for Control word, bit
11.
Value Module Control word
bit
0 None
1 to 5 Vendor specific 1 to 52)
12. (See parameter 933 for coding.)
939 R/W Unsigned16 Selection switch for Status word, bit 11.
Value Module Status word bit
0 None
1 to 4 Vendor specific 1 to 42)
940 R/W Unsigned16 Selection switch for Status word, bit

14. (See parameter 939 for coding)
945 R Array[64] Fault code (coded according to
Unsigned16 DRIVECOM profile). Supported with
ACS355 drives only. Note: The drive
may limit the actual number of the
faults recorded.
Subindex Contents
1 Active fault
947 R Array [64] Fault number.
Unsigned16
Subindex Contents
See parameter 945.
952 R/W Unsigned16 Number of faults occurred. Writing a
zero clears the value.
953 R Unsigned16 Last alarm3)
954 R Unsigned16 Second last alarm3)
955 R Unsigned16 Third last alarm3)
956 R Unsigned16 Fourth last alarm3)
957 R Unsigned16 Fifth last alarm3)
958 R Unsigned16 Sixth last alarm (not supported)
959 R Unsigned16 Seventh last alarm (not supported)
960 R Unsigned16 Eighth last alarm (not supported)
961 R Octet String4 Hardware configuration (manufacturer-
specific ID of the drive)

964 R Array [7] Subindex Contents
Unsigned16
0 Manufacturer
1 Device type
2 Version
3 Firmware date (year)
4 Firmware date
(day/month)
5 Number of Axes
6 Identification (0959h)
965 R Octet String2 Profile number of this device.
Eg: 0302h = Profile 3, Version 2
967 R Unsigned16 Control word (CW)
968 R Unsigned16 Status word (SW)
970 R/W Unsigned16 Load parameter record
Value Description
0 No action
1 Restore factory settings
The parameter must do a zero-to-one
transition and the motor must be
stopped.
971 R/W Unsigned16 Save parameter record
Value Description
0 No action
1 Save the drive
parameters to non-
volatile memory
stopped.

972 R/W Unsigned16 Software reset
Value Description
0 No action
1 Re-boot PROFIBUS
module
stopped.
975 R Array[n] DO identification. For subindexes
Unsigned16 0…4, see parameter 964.
Subindex Meaning
5 Value 2 = Axis
6 Bit 0=1 -> Application
Class 1 supported
Bit 2=1 -> Application
Class 3 supported
980 R Array[n] Number list of defined parameters. If
981 Unsigned16 the subindex is 0, the end of the list
has been reached. If the subindex is
the number of the next list parameter,
the list is continued there.
61000 R VisibleString24 Name of station
61001 R Unsigned32 IP of station
61002 R Array [6] MAC of station
Unsigned8
61003 R Unsigned32 Default gateway of station
61004 R Unsigned32 Subnet mask of station
1)
Read and/or Write
2)
The meaning of vendor-specific bits is defined by the drive application
program.
3)
Support depends on the drive type.
Appendix B – I&M records of PROFINET IO 353
Appendix B – I&M records of

PROFINET IO

This chapter contains the telegram and response structures for the
I&M (Identification & Maintenance) records of the PROFINET IO
communication protocol.
I&M records
I&M records can be read, for example, with the DTM tool. The
FENA-01/-11 module supports the mandatory I&M0 record as well
as the optional I&M1 and I&M2 records.
354 Appendix B – I&M records of PROFINET IO
Call-REQ-PDU telegram for read/write access to

I&M records
Contents Size Coding Notes
DP-V1 Function_Num 1 Octet 5Fh fixed
header
Slot_Number 1 Octet 0…255 variable
Index 1 Octet 255 fixed
Length 1 Octet 4 / 68 Call Header only /
Write
Call Extended_Function_ 1 Octet 08h Indicates “Call”,
Header Num fixed
reserved 1 Octet 00h fixed
FI_Index 2 Octets 65000 Subindex of I&M0
… Record
65000 = I&M0
65001 = I&M1
65002 = I&M2
IM_Function 64 Data Write only (I&M1
Octets or I&M2)
Appendix B – I&M records of PROFINET IO 355
Response structure for I&M0 (Read-only)

Contents Size Coding
Header Manufacturer-specific 10 Octets “FENA-01/-11”
I&M MANUFACTURER_ID 2 Octets 0x1A = ABB Automation
block
ORDER_ID 20 Octets For instance,
“68469422” for FENA-
01 kit)
SERIAL_NUMBER 16 Octets Serial number of FENA
module
HARDWARE_REVISION 2 Octets Hardware version of
FENA module
SOFTWARE_REVISION 4 Octets Format: V255.255.255
Eg, V1.0.0 = software
version 100
REVISION_COUNTER 2 Octets (Marks a change of
hardware or its
parameters)
PROFILE_ID 2 Octets 3A00 (…3AFF)
PROFIdrive
PROFILE_SPECIFIC_ 2 Octets 0 = no specific type
TYPE
IM_VERSION 2 Octets 0x0101 = version 1.1
IM_SUPPORTED 2 Octets 3 = I&M0, I&M1 and
I&M2 supported
356 Appendix B – I&M records of PROFINET IO
Response structure for I&M1 (Read/Write)

Header Manufacturer-specific 10 Octets –
I&M0 TAG_FUNCTION 32 Octets Device function or task
block
TAG_LOCATION 22 Octets Device location
Response structure for I&M2 (Read/Write)

Header Manufacturer-specific 10 Octets –
I&M0 INSTALLATION_DATE 16 Octets Installation date.
block Eg, 2011-01-01 16:23
RESERVED 38 Octets Reserved
Note: I&M1 and I&M2 are blank (0x20) by default.

Further information
Product and service inquiries
Address any inquiries about the product to your local ABB
representative, quoting the type designation and serial number of
the unit in question. A listing of ABB sales, support and service
contacts can be found by navigating to www.abb.com/drives and
selecting Sales, Support and Service network.
Product training
For information on ABB product training, navigate to
www.abb.com/drives and select Training courses.
Providing feedback on ABB Drives manuals

Your comments on our manuals are welcome. Go to
www.abb.com/drives and select Document Library – Manuals
feedback form (LV AC drives).
Document library on the Internet

You can find manuals and other product documents in PDF format
on the Internet. Go to www.abb.com/drives and select Document
Library. You can browse the library or enter selection criteria, for
example a document code, in the search field.
Contact us
3AUA0000093568 Rev A (EN) 2011-09-07

ABB Oy ABB Inc. ABB Beijing Drive Systems
Drives Automation Technologies Co. Ltd.
P.O. Box 184 Drives & Motors No. 1, Block D,
FI-00381 HELSINKI 16250 West Glendale Drive A-10 Jiuxianqiao Beilu
FINLAND New Berlin, WI 53151 Chaoyang District
Telephone +358 10 22 11 USA Beijing, P.R. China, 100015
Fax +358 10 22 22681 Telephone 262 785-3200 Telephone +86 10 5821 7788
www.abb.com/drives 1-800-HELP-365 Fax +86 10 5821 7618
Fax 262 780-5135 www.abb.com/drives
www.abb.com/drives

ABB FENA 01 11 Ethernet Manual

Uploaded by

Copyright:

Available Formats

ABB FENA 01 11 Ethernet Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ABB FENA 01 11 Ethernet Manual

Uploaded by

Copyright:

Available Formats

ABB fieldbus options

Starting up ACS880 drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

11. EtherNet/IP – Communication profiles

12. EtherNet/IP – Communication protocol

Class attributes (Instance #0) . . . . . . . . . . . . . . . . . . . 211

Configuring the master station . . . . . . . . . . . . . . . . . . . . . . . . . 276

16. PROFINET IO – Communication protocol

18. Technical data

What this chapter contains

Electricity warning warns of hazards from electricity

General warning warns about conditions, other than

WARNING! Ignoring the following instructions can cause

• Only qualified electricians are allowed to install and maintain

About the manual

What this chapter contains

The FENA-01/-11 module is compatible with Ethernet standards

The Modbus/TCP, EtherNet/IP and PROFINET IO protocols are

Purpose of the manual

Drive hardware manuals and

Option manuals and guides

Before you start

• Technical data contains the technical data of the adapter

Terms and abbreviations used in this manual

 General terms and abbreviations

 Modbus/TCP terms and abbreviations

 EtherNet/IP terms and abbreviations

 PROFINET IO terms and abbreviations

The text in italics is the original German term.

Overview of the Ethernet

What this chapter contains

 Example topology of the Ethernet link

Other slave ABB drive Other slave

FENA-01/-11 Ethernet adapter module

The FENA-01/-11 module supports 10 Mbit/s and 100 Mbit/s data

 Layout of the adapter module

What this chapter contains

WARNING! Follow the safety instructions given in this

Mounting the adapter module

What this chapter contains

WARNING! Before installation, switch off the drive power

General cabling instructions

Connecting the module to the Ethernet network

What this chapter contains

WARNING! Follow the safety instructions given in this

 Modbus/TCP connection configuration

FENA-01/-11 configuration parameters – group A (group 1)

No. Name/Value Description Default

No. Name/Value Description Default

Dotted decimal CIDR Dotted decimal CIDR

1…31 Subnet mask in CIDR notation

No. Name/Value Description Default

No. Name/Value Description Default

In the event of a Modbus/TCP timeout, the

No. Name/Value Description Default

No. Name/Value Description Default

No. Name/Value Description Default

No. Name/Value Description Default

FENA-01/-11 configuration parameters – group B (group 2)

0 = None Not used

General terms and abbreviations

Modbus/TCP terms and abbreviations

EtherNet/IP terms and abbreviations

PROFINET IO terms and abbreviations

Example topology of the Ethernet link

Layout of the adapter module

Modbus/TCP connection configuration

Parameter setting examples – ACS355

Parameter setting examples – ACSM1

Parameter setting examples – ACS850 and ACQ810

Parameter setting examples – ACS880

Modbus register maps

Control word and Status word

ABB Drives profile - Classic