Device PN ABB Drive

—
OPTIONS FOR ABB DRIVES, CONVERTERS AND INVERTERS
FPNO-21 PROFINET fieldbus adapter module

User's manual
User's manual
FPNO-21 PROFINET fieldbus adapter module
Table of contents
1. Safety instructions
4. Mechanical installation
5. Electrical installation
© 2018 ABB Oy. All Rights Reserved. 3AXD50000158614 Rev A

EN
EFFECTIVE: 2018-07-11
Table of contents 5
Table of contents
1 Safety instructions
Contents of this chapter ........................................................................... 9
Use of warnings and notes ....................................................................... 9
Safety in installation and maintenance ......................................................... 9
2 Introduction to the manual

Applicability ......................................................................................... 11
Compatibility ........................................................................................ 11
Drives ............................................................................................ 11
Protocol .......................................................................................... 11
Target audience .................................................................................... 12
Purpose of the manual ............................................................................ 12
Cybersecurity disclaimer .......................................................................... 12
Terms and abbreviations .......................................................................... 12
Related manuals ................................................................................... 14
3 Overview of the Ethernet network and the FPNO-21 module

Ethernet network ................................................................................... 17
Example topology of the Ethernet link ....................................................... 17
FPNO-21 module overview ....................................................................... 18
FPNO-21 layout ................................................................................ 19
4 Mechanical installation
Necessary tools and instructions ................................................................ 21
Unpacking and examining the delivery ......................................................... 21
Installing the module .............................................................................. 22
5 Electrical installation
Necessary tools and instructions ................................................................ 25
General cabling instructions ...................................................................... 25
Connecting the FPNO-21 to the Ethernet network ............................................ 25
6 PROFINET IO – Start-up
Warnings ............................................................................................ 27
Drive configuration ................................................................................. 27
PROFINET IO connection configuration .................................................... 27
FPNO-21 configuration parameters – group A (group 1) ............................. 28
FPNO-21 configuration parameters – group B (group 2) ............................. 34
FPNO-21 configuration parameters – group C (group 3) ............................. 35
6 Table of contents
Control locations ................................................................................ 36

Starting up fieldbus communication for drives ................................................. 36
Parameter setting examples – ACS380, ACS480, ACH580, ACQ580, and ACS580 ... 37
Frequency control using PROFIdrive communication profile with PPO Type 4 ....... 37
Parameter setting examples – ACS880 ........................................................ 38
Speed control using PROFIdrive communication profile with PPO Type 4 ............ 38
Configuring the master station ................................................................... 39
Downloading the GSD file ..................................................................... 40
Configuring an ABB AC500 PLC ............................................................. 40
Configuring a Siemens SIMATIC S7 PLC .................................................. 43
Resetting PROFINET IO device to factory default via S7 ................................ 48
Configuring a Siemens PLC with TIA14 .................................................... 52
Media Redundancy Protocol (MRP) ............................................................ 60
Configuring Media Redundancy Protocol (MRP) with Siemens PLC ................... 61
Configuring Media Redundancy Protocol (MRP) with TIA14 ............................ 67
Shared Device ...................................................................................... 70
Configuring Shared Device for ABB PLC with Automation builder ...................... 70
Configuring drive control PLC ............................................................. 70
Configuring safety PLC .................................................................... 71
Configuring Shared Device for Siemens PLC with TIA portal ........................... 73
Configuring drive control PLC ............................................................. 73
Configuring safety PLC .................................................................... 73
7 PROFINET IO – Communication profiles

Communication profiles ........................................................................... 75
PROFIdrive communication profile .............................................................. 76
Control word and Status word ................................................................ 76
Control word contents ...................................................................... 77
Status word contents ....................................................................... 78
State machine for all operating modes .................................................. 80
State machine for the positioning mode ................................................. 80
References ...................................................................................... 81
References in speed control mode ....................................................... 82
Actual values .................................................................................... 82
Actual values in speed control mode .................................................... 82
ABB Drives communication profile .............................................................. 82
Control word and Status word ................................................................ 82
Control word contents ...................................................................... 82
Status word contents ....................................................................... 84
State machine ............................................................................... 85
References ...................................................................................... 86
Scaling ........................................................................................ 86
Actual values .................................................................................... 86
Scaling ........................................................................................ 86
8 PROFINET IO – Communication protocol

PROFINET IO ...................................................................................... 89
PROFINET network settings ..................................................................... 90
PROFINET IO in FPNO-21 ....................................................................... 90
Table of contents 7
The services provided by the FPNO-21 module .............................................. 90

Cyclic message types ............................................................................. 91
PPO types ....................................................................................... 91
Standard telegram (ST) types (DP-V1) ..................................................... 92
Behavior of output data ........................................................................ 92
Parameter handling using acyclic parameter access mechanism (DP-V1) .............. 92
Header and frame structures ................................................................. 92
ErrorCode1 .................................................................................. 93
DP-V1 read/write request sequence ......................................................... 94
Read and write blocks ...................................................................... 95
Data block .................................................................................... 96
Function blocks for sending DP-V1 messages (Siemens S7) ........................... 99
Parameter data transfer examples ........................................................... 99
Example 1a: Reading a drive parameter (array element) ............................. 100
Example 1b: Reading 3 drive parameters (multi-parameter) ......................... 101
Example 2a: Writing a drive parameter (one array element) ......................... 102
Example 2b: Writing 2 drive parameters (multi-parameter) ........................... 103
Example 3: Reading a PROFIdrive parameter ......................................... 105
Example 4: Configuring the process data written to the drive ........................ 106
Example 5: Determining the source of the process data read from the drive ...... 108
Diagnostic and alarm mechanism ............................................................... 109
Alarm mechanism .............................................................................. 109
Fault code mapping ........................................................................ 110
Fault buffer mechanism ....................................................................... 111
9 PROFINET IO – Diagnostics
Fault and warning messages ..................................................................... 113
LEDs ................................................................................................. 113
10 NONE – Start-up
Warnings ............................................................................................ 117
Drive configuration ................................................................................. 117
Connection configuration using NONE protocol ........................................... 117
FPNO-21 configuration parameters – group A (group 1) ............................. 118
Starting up fieldbus communication ............................................................. 121
11 NONE - Diagnostics
Fault and warning messages ..................................................................... 123
LEDs ................................................................................................. 123
12 Technical data
Dimension drawing ................................................................................ 125
General data ........................................................................................ 126
Ethernet link ........................................................................................ 126
TCP and UDP service ports ...................................................................... 126
8 Table of contents
13 Appendix A – PROFIdrive parameters and I&M records of PROFINET IO

PROFIdrive parameters ........................................................................... 129
I&M records ......................................................................................... 134
Call-REQ-PDU telegram for read/write access to I&M records .......................... 134
Response structure for I&M0 (Read-only) .................................................. 134
Response structure for I&M1 (Read/Write) ................................................. 135
14 Appendix B – ABB IP configuration tool

Installation ........................................................................................... 137
Finding adapter modules in the network ........................................................ 137
Rewriting the IP configuration of adapter modules ........................................... 138
15 Appendix C - FPNO-21 configuration web pages

Browser requirements ............................................................................. 141
Compatibility ........................................................................................ 141
Logging in ........................................................................................... 141
Menu overview ..................................................................................... 143
Status page ..................................................................................... 143
Configuration page ............................................................................. 143
Changing the PROFINET IO station name via web page ............................ 144
Service configuration page .................................................................... 146
Configuring SNTP .......................................................................... 147
Support page .................................................................................... 148
Password page ................................................................................. 148
Reset FPNO-21 web page password to default ............................................... 149
Enable web page access after it was disabled ................................................ 149
16 Appendix D - FPNO-21 configuration back-up

Compatibility ........................................................................................ 151
Settings for backup ................................................................................ 151
Configuration backup for all protocols in FPNO-21 ....................................... 151
Using the restored backup .................................................................... 152
Further information
Safety instructions 9
1
Safety instructions
Contents of this chapter

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

Warnings tell you about conditions which can cause injury or death, or damage to the
equipment. They also tell you how to avoid danger. Notes draw attention to a particular
condition or fact, or give information on a subject.
The manual uses these warning symbols:
WARNING!
Electricity warning tells about hazards from electricity which can cause injury or
death, or damage to the equipment.
WARNING!
General warning tells about conditions, other than those caused by electricity,
which can cause injury or death or damage to the equipment.
Safety in installation and maintenance

These instructions are for all who install or connect an option module to a unit and need to
open its front cover or door to do the work.
10 Safety instructions
WARNING!
Obey these instructions. If you ignore them, injury or death, or damage to the
equipment can occur.
• If you are not a qualified electrician, do not do installation or maintenance work.

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

This chapter introduces this manual.
Applicability
This manual applies to the FPNO-21 fieldbus adapter module, revision A.
Compatibility
￭ Drives
The FPNO-21 fieldbus adapter module is compatible with:
• ACS880 primary control program version 2.51.0.0 and later
• ACS580 standard control program version 2.02.0.1 and later
• ACH580 HVAC control program 2.01.0.4 and later
• ACQ580 pump control program 2.03.0.3 and later
• ACS380 machinery control program version 2.02.0.1 and later
• ACS480 standard control program 2.02.0.3 and later
Note:
Not all compatible drives are listed here. For details of compatibility, check the drive's
firmware manual.
￭ Protocol
The FPNO-21 module is compatible with Ethernet standards IEEE 802.3 and IEE 802.3u
and it supports the PROFINET IO protocol.
All PROFINET IO masters that support:
• GSDML file version 2.33

• PROFINET IO protocol according to IEC standards 61158 and 61784
• PROFINET IO conformance class B
are compatible with the PROFINET IO module.
In addition, it is possible to have other protocols running on the FPNO-21 module which
can be enabled/disabled via web pages:
• ABB IP configuration tool
• Simple Network Time Protocol (SNTP)
• Drive composer tool via Ethernet tool network.
Target audience
This manual is intended for people who plan the installation, install, start up, use and service
the module. Before you do work on the module, read this manual and the applicable drive
manual that contains the hardware and safety information for the product in question.
You are expected to know the fundamentals of electricity, wiring, electrical components and
electrical schematic symbols.
This manual is written for readers worldwide. Both SI and imperial units are shown.
Purpose of the manual

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

Term Description
ACT Actual value
Istwert
Acyclic communication Communication in which messages are sent only once on request
Array Parameter consisting of data fields of equal data type
Command word See Control word.
Control word 16-bit or 32-bit word from a controller to the controlled device with bit-coded control
signals (sometimes called the Command word).
Cyclic communication Communication in which messages are sent cyclically at pre-defined intervals
DAP Device access point
Term Description
Data object Special object that contains parameter and process data
DCP Discovery Control Protocol. A protocol that allows the master controller to find every
PROFINET IO device on a subnet.
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.
DP Decentralized 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 ex-
change
Drive Frequency converter for controlling AC motors
EMC Electromagnetic compatibility
Fault Event that leads to tripping of the device
FBA Fieldbus adapter
Fieldbus adapter mod- Device through which the drive is connected to an external communication network,
ule that is, a fieldbus
GSD file General Station Description file, an 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.
GSDML General Station Description Markup Language
I/O controller Control system with bus initiative. In PROFINET IO terminology, I/O controllers are
also called master stations.
Index Access reference for objects in PROFINET IO
ISW See ACT.
LSB Least significant bit
MAC address Media Access Control address
MAP Module access point
Master Control system with bus initiative. In PROFINET IO terminology, master stations are
also called active stations.
MSB Most significant bit
PAP Parameter access point
Parameter In the drive control program, user-adjustable operation instruction to the drive, or signal
measured or calculated by the drive.
In some (for example fieldbus) contexts, a value that can be accessed as an object,
eg, variable, constant, or signal.
Parameter/Process data Special object that contains parameter and process data
object
PD Process data
Prozessdaten
PKE Parameter identification
Parameter-Kennung
PKW Parameter identification value
Parameter-Kennung-Wert
PLC Programmable logic controller
PNU Parameter number
Parameternummer
PPO Parameter/Process data object
Parameter-/Prozessdaten-Objekt
Process data Data that contains Control word and reference value or Status word and actual value.
May also contain other (user-definable) control information.
Profile Adaptation of a communication protocol for a certain application field (for example
drives)
PWE Parameter value
Parameter-Wert
Term Description
PZD See PD.
PZDO Process data object
Prozessdatenobjekt
SAP Service access point
Slave Passive bus participant. In PROFINET IO terminology, slave stations (or slaves) are
also called passive stations. Also referred to as node.
SNTP Simple Network Time Protocol. A protocol to synchronize drive time with the network
time server.
SOW Reference
Sollwert
Status word Binary word with bit-coded status messages
STW Control word
Steuerwort
Warning Signal caused by an existing alarm which does not lead to tripping of the device
ZSW Status word
Zustandswort
Related manuals
Manual Code
Drive hardware manuals and guides
ACS380-04 manuals 9AAK10103A6193
ACS480 manuals 9AKK106930A8739
ACS580-01 manuals 9AKK105713A8085
ACH580-01 manuals 9AKK10103A0587
ACQ580-01 manuals 9AKK106713A2709
ACS880-07 (45 to 710 kW) manuals 9AKK105408A8149
Option manuals and guides
FPNO-21 PROFINET fieldbus adapter module user’s manual 3AXD50000158614
The links above contain lists of documents. You can find manuals and other product
documents in PDF format on the Internet. See ABB Document Library. For manuals not
available in the Document library, contact your local ABB representative.
FPNO-21 PROFINET fieldbus adapter module Fieldbus connectivity web page

User's manual
16
Overview of the Ethernet network and the FPNO-21 module 17
3
Overview of the Ethernet network and
the FPNO-21 module

This chapter contains a short description of the Ethernet network and the topology supported
by the FPNO-21 adapter module.
Ethernet network
Ethernet standards support a variety of physical media (coaxial cable, twisted pair, fiber
optics) and topologies (bus and star).
The FPNO-21 module supports twisted pair as the physical media. FPNO-21 supports star
topology, daisy chain topology and ring topology (Media Redundancy Protocol
(MRP) (page 60)).
The maximum length for an Ethernet segment on twisted pair media is 100 meters. All
twisted pair media between the Ethernet node and the switch or router must be shorter than
100 meters, including media within patch panels.
￭ Example topology of the Ethernet link

The figures below show example topologies for an Ethernet network with FPNO-21.
18 Overview of the Ethernet network and the FPNO-21 module
Star topology
Other slave ABB drive Other slave

device device
Switch or router
Daisy chain topology
FPNO-21 module overview

The FPNO-21 adapter Network
module is amaster
plug-in device
devicefor ABB drives which enables the
connection of the drive to a PROFINET IO network.
Through the adapter module you can:
• give control commands to the drive (for example, Start, Stop, Run enable)
• feed a motor speed or torque reference to the drive
• give a process actual value or a process reference to the PID controller of the drive
• read status information and actual values from the drive
• reset a drive fault
• read/write parameters of the drive
1 2 3 4 5
First angle projection. Original drawing made with 3D CAD. Set the correct scale factor when adding
dimension
Overview of the Ethernet network and the FPNO-21 module 19
• connect Drive composer pro tool
23,6
[1]
• synchronize real time clock.
The adapter module supports 10 Mbit/s and 100 Mbit/s data transfer rates and automatically
detects the data transfer rate used in the network.
Note:
PROFINET IO uses only 100 Mbit/s in the Full duplex mode.
The adapter module is installed into an option slot on the drive control unit. See the drive
manuals for module placement options.
SUPPLY CO
￭ FPNO-21 layout LOCK
63 5 16 20
[2.48] [.20] [.63] [.8
6
[2.56]
65
3 4 5
3 23
No. Description
[.12] [.89]
1 Lock
2 Mounting screw
3 X1 connector to Ethernet
4 X2 connector for chaining another module

Based on 5 Diagnostic LEDs Prepared T.Huoso 19-Oct-17 Title DIMENSION DRA
Customer Check. M.Karna 19-Oct-17 FPNO-21 ADAPT
6 MAC address Appr. V.Jung 19-Oct-17 PROFINET IO
Cust. Doc. No. Project name
DMS Number 3AXD10000657934 Weight kg 0.07
20
Mechanical installation 21
4
Mechanical installation

This chapter contains a delivery checklist and instructions on installing the module.
Necessary tools and instructions

You will need a Torx TX10 screwdriver to secure the FPNO-21 module to the drive. See
also the drive hardware manual.
Unpacking and examining the delivery

1. Open the option package.
2. Make sure that the package contains:
• fieldbus module, type FPNO-21
• quick guide
3. Make sure that there are no signs of damage.
verters 22 Mechanical installation
on and start-up
Installing the moduleguide
dapter module
WARNING!
Obey the safety instructions. If you ignore the safety instructions, injury or death
can occur.
The module is installed to a free option slot on the drive control unit. Plastic pins, a lock and
one screw hold the module in place. The screw also makes an electrical connection between
the module and drive frame for cable shield termination.
Note:
instructions. If install
Do not you ignore them,module
the FPNO-21 injuryon
orthe
death, orF-series
FEA-03 damage to the adapter.
extension
he user’s manual.
When the module is installed, it makes the signal and power connection to the drive through
a 20-pin connector.
To install or remove the module from the control unit:
1. Pull out the lock.
n option
e drive
1
3
N·m using
ssive force,
. Over-
ew or 4
he EMC 2. Install the module carefully to an option module slot of the drive. See the drive hardware
manual.
n operation
No. Description
1 Lock
2 Mounting and grounding screw
3 RJ-45 connector [X1] to Ethernet
4 RJ-45 connector [X2] for chaining another module
5 Diagnostic LEDs
ou ignore them, injury or death, or damage to the
Mechanical installation 23
3. Push in the lock.
1
3
4. Tighten the screw to torque 0.8 N·m using a Torx TX10 screwdriver.
WARNING!
Do not use excessive force, or leave the screw too loose. Overtightening can
damage the screw or module. A loose screw decreases the EMC performance,
and can even cause an operation failure.
See the drive manual for further instructions on how to install the module to the drive.
o. Description
Lock
Mounting and grounding screw
RJ-45 connector [X1] to Ethernet
RJ-45 connector [X2] for chaining another module
Diagnostic LEDs
24
Electrical installation 25
5
Electrical installation

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

See the drive hardware manual.
General cabling instructions

• Arrange the bus cables as far away from the motor cables as possible.
• Avoid parallel runs.
• Use bushings at cable entries.
Connecting the FPNO-21 to the Ethernet network

The network cable can be CAT5 or higher, braided and foiled shield, with minimum AWG
22 / 0×32mm2. Use a PROFINET-certified cable. The cable shield is connected to the drive
frame through an RC network. It is recommended to use a dedicated PROFINET-cable for
PROFINET installation.
Note:
Further information on PROFINET-wiring is available from the PROFIBUS organization
publications at https://www.profibus.com/download/profinet-installation-guidelines/
• Design guideline, Order no. 8.062

• Installation guideline for cabling and assembly, Order no. 8.072
• Commissioning guide, Order no. 8.082
26 Electrical installation
WARNING!
Obey the safety instructions. If you ignore the safety instructions, injury or death
can occur. If you are not a qualified electrician, do not do electrical work.
1. Connect the network cable to the RJ-45 connector (X1) on the adapter module.
2. If you want to create a daisy chain with FPNO-21 adapter modules, connect the X2
connector of the first adapter module to X1 on the next adapter module, and so on.
Note:
If a device in the daisy chain is powered off or fails, the rest of the chain is disconnected
from the network. In applications where this is not acceptable, consider using ring topology
instead.
PROFINET IO – Start-up 27
6
PROFINET IO – Start-up

This chapter contains:
• information on configuring the drive for operation with the adapter module
• drive-specific instructions on starting up the drive with the adapter module
• examples of configuring the master station for communication with the adapter module.
Warnings
WARNING!
Obey the safety instructions given in this manual and the drive documentation.
Drive configuration
The information in this section applies to all drive types compatible with the FPNO-21 module,
unless otherwise stated.
￭ PROFINET IO connection configuration

After the adapter module has been mechanically and electrically installed, you must prepare
the drive for communication with the module.
The detailed procedure of activating the module for PROFINET IO communication with the
drive depends on the drive type. Normally, you must set the PROFINET parameters to
establish the communication. See the drive-specific start-up instructions starting on page
21.
Once communication between the drive and the adapter module has been established,
several configuration parameters are shown to user. These parameters are listed in the
tables below and must be checked first and adjusted where necessary. You can adjust the
parameters via a drive control panel, a web user interface, or a PC tool.
• The new parameter settings take effect only when you power up the module the next
time or when you activate the fieldbus adapter refresh parameter.
FPNO-21 configuration parameters – group A (group 1)
Note:
The actual parameter group number depends on the drive type. Group A (group 1)
corresponds to:
• parameter group 51 in ACS380, ACS480, ACH580, ACQ580 and ACS580.
• parameter group 51 in ACS880 if the adapter is installed as fieldbus adapter A or group
54 if the adapter is installed as fieldbus adapter B.
No. Name/Value Description Default
01 FBA type Read-only. Shows the fieldbus adapter type as detec- 132 = PROFINET IO
ted by the drive. The value cannot be adjusted by the
user.
If the value is 0 = None, the communication between
the drive and the module has not been established.
02 Protocol.Profile Selects the application protocol and communication 11 = PNIO ABB Pro
profile for the network connection.
The selections available for PROFINET IO communic-
ation are listed below.
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
03 Commrate Sets the bit rate for the Ethernet interface. 0 = Auto
0 = Auto Auto-negotiate
1 = 100 Mbps FD 100 Mbps, full duplex
2 = 100 Mbps HD 100 Mbps, half duplex

04 IP configuration Sets the method for configuring the IP address, subnet 0 = Static IP
mask and gateway address for the module.
In a PROFINET IO network, the master controller has
a Duplicate Address Detection mechanism.
Note:
It is recommended to use IP setting for PROFINET as
Static IP and address 0.0.0.0. Use PLC hardware
configuration to set the IP address for each device in
the network.
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 configured
for 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.
2 = Temp IP IP address is set as Temporary through DCP by the

controller.
Parameters 05...13 shows the set IP. After reboot this
setting goes back to static IP and address 0.0.0.0 is
taken to use. This setting is not allowed to be set by
the user.
05 IP address 1 An IP address is assigned to each IP node on a net- 0

... work. An IP address is a 32-bit number that is typically
represented in “dotted decimal” notation consisting of
08
four decimal integers, on the range 0…255, separated
by periods. Each integer represents the value of one
octet (8-bits) in the IP address. Parameters 05…08
define the four octets of the IP address.
0...255 IP address
... ... ...
IP address 4 See parameter 05 IP address 1. 0
0...255 IP address
09 Subnet CIDR Subnet masks are used for splitting networks into 0
smaller networks called subnets. A subnet mask is a
32-bit binary number that splits the IP address into a
network address and host address.
Subnet masks are typically represented in either dotted
decimal notation or the more compact CIDR notation,
as shown in the table below.
CIDR Dotted decimal CIDR Dotted decimal

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

... into a unified IP network. When an IP node needs to
communicate with an IP node on another subnet, the
13
IP node sends the data to the IP gateway for forward-
ing. Parameters 10…13 define the four octets of the
gateway address.
0...255 GW address
... ... ...
GW address 4 See parameter 10 GW address 1. 0
0...255 GW address
14 Commrate 2 Sets the bit rate for the Ethernet port 2. 0 = Auto
0 = Auto Autonegotiate

15 Reserved These parameters are not used by the adapter module N/A
... when the module is configured for PROFINET IO.
18
19 T16 scale Defines the scaling for reference 1 and actual 1 with 99
Transparent 16 profile. (Protocol.Profile = PNIO T16)
Scaling also depends on the selected Reference type
on 50.04 FBA A Ref 1 type and 50.34 FBA B Ref 1
type and 50.07 and 50.37 for the actual 1.
Ref type = Transparent
FBA_A/B_Ref1 = Ref1_from_PLC * (T16_Scale + 1)
Ref type = General
FBA_A/B_Ref1 = Ref1_from_PLC * (T16_Scale + 1)
/ 100
0…65535 Reference multiplier/actual value divisor
20 Telegram type Read-only. Indicates the telegram type selected for 0 = Unknown
PROFINET IO communication. The adapter module
automatically detects the telegram type defined in the
PLC.
For more information on the supported PPO message
types, see section PPO types (page 91).
0 = Unknown Cyclical communication between the master and the

module has not been established yet.
3 = PPO3 PPO3 selected
8 = ST1 ST1 selected
9 = ST2 ST2 selected
21 Diagnostic alarm Disables the PROFIdrive alarm mechanism which 0 = Enabled

generates alarms in case of drive faults.
But the standard PROFINET alarms are still sent.
For more information on the diagnostics and alarm
mechanism for PROFIdrive, see section Diagnostic
and alarm mechanism (page 109).
0 = Enabled PROFIdrive alarms are enabled.
1 = Disabled PROFIdrive alarms are disabled.
22 Map selection Defines the preferred data type of mapped parameters 1 = 16bit
when mapping is done through PROFIdrive paramet-
ers.
0 = 32bit 32 bits
1 = 16bit 16 bits
23 ... Reserved This parameter is not used by the adapter module N/A
24 when the module is configured for PROFINET IO.
25 PN Name Index Allows defining the PROFINET station name in the 0

format: “abbdrive-xx”, where xx is the value of the
parameter name index, i.e. 25 (parameter 25 PN
NAME INDEX).
Example: A value 12 results in the name “abbdrive-12”
Value 0 means rotary switch is disabled, other values
mean rotary switch is active.
Note:
During every boot the FPNO-21 module checks the
value of PN Name Index,
• If the value is not Zero then the active PN Name In-
dex overrides the PROFINET station name.
• If the new name is set by DCP Set command as
permanent, the new name is used and stored to
flash. The PN Name Index parameter value is not
changed, so after next boot, the name is taken ac-
cording to the PN Name Index.
• If the new name is set by DCP Set command as
temporary, the new name is used and the empty
name is stored to flash. The PN Name Index para-
meter value is not changed, so after next boot name
is taken according to the PN Name Index.
• The PROFINET DCP factory reset also resets the
PN Name Index value to default (0).
0...65535
26 Reserved Reserved for web page functionality. For more inform- N/A
ation, see Appendix C - FPNO-21 configuration web
pages (page 141).
27 FBA A/B par refresh Validates any changed adapter module configuration 0 = Done
parameter settings. After refreshing, the value reverts
automatically to 0 = Done.
Note:
This parameter cannot be changed while the drive is
running.
0 = Done Refreshing done
1 = Refresh Refreshing
28 FBA A/B par table ver Read-only. Displays the parameter table revision of N/A
the fieldbus adapter module mapping file stored in the
memory of the drive. In format xyz, where
x = major revision number
y = minor revision number
z = correction number
OR
in format axyz, where
a = major revision number
xy = minor revision numbers
z = correction number or letter.
Parameter table revision

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

ping file
30 FBA A/B mapping file Read-only. Displays the fieldbus adapter module N/A
ver mapping file revision stored in the memory of the drive
in decimal format.
Mapping file revision
31 D2FBA A/B comm Read-only. Displays the status of the fieldbus adapter 0 = Idle
status module communication. or
Note: The value names may vary by drive. 4 = Offline
Note: Only active drive-controlled channel will change
comm status online. PROFIsafe alone will not change
the comm status.
0 = Idle Adapter is not configured
1 = Exec.init Adapter is initializing.
2 = Time out A timeout has occurred in the communication between

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

between the adapter and the drive. Contact your local
ABB representative.
4 = Off-line Adapter is off-line
5 = On-line Adapter is on-line
6 = Reset Adapter is performing a hardware reset.
32 FBA A/B comm SW Read-only. Displays patch and build numbers of the N/A
ver adapter module's firmware version in xxyy format,
where:
xx = patch number
yy = build number.
Example: If the firmware version (<ma-
jor>.<minor>.<patch>.<build>) is 3.10.200.13, the value
C80D is displayed. If the version is 3.10.0.0, the value
0 is displayed.
See also parameter 33.
33 FBA A/B appl SW ver Read-only. Displays major and minor revision numbers N/A
of the adapter module's firmware version in xxyy
format, where:
xx = major revision number
yy = minor revision number
jor>.<minor>.<patch>.<build>) is 3.10.200.13 or
3.10.0.0, the value 310 is displayed.
FPNO-21 configuration parameters – group B (group 2)

Note: The actual parameter group number depends on the drive type. Group B (group 2)
corresponds to:
• parameter group 53 in ACS380, ACS480, ACH580, ACQ580 and ACS580
No.1) Name/Value Description Default
01 FBA data out 1 (mas- Selects the resolution of control word (16 bit or 32 bit) 1 or 112)
ter to drive) received by the drive.
1 = CW 16bit Control word (16 bits)
02 FBA data out 2 Selects data word 1 received by the drive over the 0 or 2
PROFINET network. The content is defined by a
decimal number in the range of 0 to 9999 as follows:
0 Not used
1...99 Virtual address area of drive control
101... Parameter area of the drive
9999
0 = None Not used
2 = Ref1 16bit Reference REF1 (16 bits)
12 = Ref1 32bit Reference REF1(32 bits)
21 = CW2 16bit Control word 2 (16 bits)
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.
03 ... FBA data out 3 … See parameter 02 FBA data out 1. 0

10 FBA data out12
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 Transparent32 profile is used.
FPNO-21 configuration parameters – group C (group 3)
Note:
The actual parameter group number depends on the drive type. Group C (group 3)
corresponds to:
• parameter group 52 in ACS380, ACS480, ACH580, ACQ580 and ACS580
No.1) Name/Value Description Default
01 FBA data in 1 (drive Selects the resolution of status word (16 bit or 32 bit) 4 or 142)
to master) sent by the drive.
4 = SW 16bit Status word (16 bits)
02 FBA data in 2 (drive Selects data word 1 sent by the drive over the 0 or 5
to master) PROFINET network. The content is defined by a
decimal number in the range of 0 to 9999 as follows:
0 Not used
1...99 Virtual address area of drive control
101... Parameter area of the drive
9999
0 = None Not used
5 = Act1 16bit Actual value ACT1 (16 bits)
24 = SW2 16bit Status word 2 (16 bits)
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.
03 ... DATA IN 3… DATA See parameter 01 FBA data in 1. 0

10 IN 12
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 Transparent32 profile is used.
￭ Control locations
ABB drives can receive control information from multiple sources including digital inputs,
analog inputs, the drive control panel and a fieldbus adapter module. ABB drives allow the
user to separately determine the source for each type of control information (Start, Stop,
Direction, Reference, Fault reset, etc.).
To give the fieldbus master the most complete control over the drive, you must select the
adapter module as the source of this information. The drive-specific parameter setting
examples below contain the drive control parameters relevant in the examples. For a
complete parameter list, see the drive documentation.
Starting up fieldbus communication for drives

1. Power up the drive.
2. Enable the communication between the adapter module and the drive by selecting the
correct slot number in parameter 50.01 FBA A enable.
The selection must correspond to the slot where the adapter module is installed. For
example, if the adapter module is installed in slot 2, you must select "slot 2".
3. With parameter 50.02 FBA A comm loss func, select how the drive reacts to a fieldbus
communication break.
Note that this function monitors both communication between the fieldbus master and
the adapter module and communication between the adapter module and the drive.
4. With parameter 50.03 FBA A comm loss t out, define the time between communication
break detection and the selected action.
5. Select application-specific values for the rest of the parameters in group 50, starting
from 50.04.
Examples of appropriate values are shown in the tables below.
6. Set the module configuration parameters in group 51.
At the minimum, select the communication protocol and profile with parameter 51.02
Protocol/Profile and configure the network settings with parameters 51.03…51.13.
7. Define the process data transferred to and from the drive in parameter groups 52 and
53.
Note:
The adapter module 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.
8. Save the valid parameter values to permanent memory with parameter 96.07 Parameter
save manually.
9. Validate the settings made in parameter groups 51, 52 and 53 with parameter 51.27
FBA A par refresh.
10. Set the relevant drive control parameters to control the drive according to the application.
Examples of appropriate values are shown in the tables below.
Parameter setting examples – ACS380, ACS480, ACH580,

ACQ580, and ACS580
￭ Frequency control using PROFIdrive communication profile with PPO
Type 4
This example shows how to configure a basic frequency control application that uses the
PROFIdrive profile. In addition, some application-specific data is added to the communication.
The start/stop commands and reference are according to the PROFIdrive profile, speed
control mode. For more information, see the PROFIdrive state machine on page 80.
The reference value ±16384 (4000h) corresponds to parameter 46.02 Frequency scaling
in the forward and reverse directions.
Direction PZD1 PZD1 PZD3 PZD4 PZD5 PZD6
Out Control word Frequency ref- Constant frequency 11) Constant frequency 21)
erence
In Status word Frequency ac- Power1) DC bus voltage1)

tual value
1) Example
The table below gives an example of the drive parameter settings.
Drive parameter Setting for drives Description
50.01 FBA A enable 1 = Enable Enables communication between the drive and the
fieldbus adapter module.
50.04 FBA A ref1 type 0 = SPEED or frequency Selects the fieldbus A reference 1 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 paramet-
er 50.04.
51.01 FBA A type 132 = PROFINET IO1) Displays the type of the fieldbus adapter module.
51.02 Protocol/Profile 10 = PNIO Pdrive Selects the PROFINET IO protocol and the
PROFIdrive profile.
51.03 Commrate 0 = Auto Ethernet communication rate is negotiated automat-

ically by the device.
51.04 IP configuration 0 = Static IP Configuration will be obtained from parameters

51.05…13 or from the PLC via the DCP protocol.
52.01 FBA DATA IN1 4 = SW 16bit Status word
52.02 FBA DATA IN2 5 = Act1 16bit Actual value 1
52.03 FBA data in3 01.14 Output power
52.05 FBA data in5 01.11 DC voltage
53.01 FBA DATA out1 1 = CW 16bit Control word
53.02 FBA DATA out2 2 = Ref1 16bit Reference 1 (frequency)
53.03 FBA data out3 28.26 Constant frequency 1

53.05 FBA data out5 28.27 Constant frequency 2
51.27 FBA A par refresh 1 = Refresh Validates the configuration parameter settings.
19.12 Ext1 control mode 2 = Speed Selects speed control as the control mode 1 for ex-
ternal control location 1.
20.01 Ext1 commands 12 = Fieldbus A Selects the fieldbus A interface as the source of the
start and stop commands for external control location
1.
22.11 Speed ref1 source 4 = FB A REF1 Selects the fieldbus A reference 1 as the source for
speed reference 1.
1) Read-only or automatically detected/set
The start sequence for the parameter example above is given below.
Control word:
• Reset the fieldbus communication fault (if active).
• Enter 47Eh (1150 decimal) → READY TO SWITCH ON.
Enter 47Fh (1151 decimal) → OPERATING.
Parameter setting examples – ACS880

￭ Speed control using PROFIdrive communication profile with PPO Type
4
This example shows how to configure a basic speed control application that uses the
PROFIdrive profile. In addition, some application-specific data is added to the communication.
The start/stop commands and reference are according to the PROFIdrive profile, speed
control mode. For more information, see the PROFIdrive state machine on page 80.
The reference value ±16384 (4000h) corresponds to parameter 46.01 Speed scaling in
the forward and reverse directions.
Direction PZD1 PZD2 PZD3 PZD4 PZD5 PZD6
Out Control word Speed refer- Constant speed 11) Constant speed 21)
ence
In Status word Speed actual Power1) DC bus voltage1)

value
1) Example
The table below gives an example of the drive parameter settings.
50.01 FBA A enable 1 = Option slot 22) Enables communication between the drive and the
fieldbus adapter module.
50.04 FBA A ref1 type 4 = SPEED Selects the fieldbus A reference 1 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 paramet-
er 50.04.
51.01 FBA A type 132 = PROFINET IO1) Displays the type of the fieldbus adapter module.
51.02 Protocol/Profile 10 = PNIO Pdrive Selects the PROFINET IO protocol and the
PROFIdrive profile.
51.03 Commrate 0 = Auto2) Ethernet communication rate is negotiated automat-

ically by the device.
51.04 IP configuration 0 = Static IP Configuration will be obtained from parameters

51.05…13 or from the PLC via the DCP protocol.
52.01 FBA DATA IN1 4 = SW 16bit Status word
52.02 FBA DATA IN2 5 = Act1 16bit Actual value 1
52.03 FBA data in3 01.14 Output power
52.05 FBA data in5 01.11 DC voltage
53.01 FBA DATA out1 1 = CW 16bit Control word
53.02 FBA DATA out2 2 = Ref1 16bit Reference 1 (speed)
53.03 FBA data out3 22.26 Constant speed 1
53.05 FBA data out5 22.27 Constant speed 2
51.27 FBA A par refresh 1 = Refresh Validates the configuration parameter settings.
19.12 Ext1 control mode 2 = Speed Selects speed control as the control mode 1 for ex-
ternal control location 1.
20.01 Ext1 commands 12 = Fieldbus A Selects the fieldbus A interface as the source of the
start and stop commands for external control location
1.
22.11 Speed ref1 source 4 = FB A REF1 Selects the fieldbus A reference 1 as the source for
speed reference 1.
1) Read-only or automatically detected/set

2) Example
The start sequence for the parameter example above is given below.
Control word:
• Reset the fieldbus communication fault (if active).
• Enter 47Eh (1150 decimal) → READY TO SWITCH ON.
Enter 47Fh (1151 decimal) → OPERATING.
Configuring the master station

After the adapter module has been initialized by the drive, you must prepare the master
station 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 apply 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 FPNO-21 GSD file from the Document library
(http://new.abb.com/drives/connectivity/fieldbus-connectivity/profinet). The file name format
is GSDML-Vx.x-ABB-FPNO-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 Control Builder Plus PS501, software version 2.1.0 and later.
Before you start, make sure that you have downloaded the FPNO-21 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 adapter module to the PROFINET IO network.
7. Add the I/O module, for example, PPO Type 4 to the adapter 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 adapter module 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. Open the PLC program.

11. Compile the project and download it to the PLC.
This is necessary for you to be able to configure the CM579-PNIO master device and
allow it to scan the network.
12. Return to the CM579-PNIO master properties. On the Assign station name tab, do
the following tasks:
• 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.
13. 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.
14. Open the PLC program and create a program that controls the drive.
15. 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.
Document library.
1. Start the SIMATIC manager and open/create a SIMATIC program.
2. Open the hardware configuration of the project.
3. Install the FPNO-21 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 FPNO-21 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 FPNO-21 to open the Properties window.
6. On the General tab, type a name for the adapter module in the Device name box.
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 FPNO-21.
• 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
is to be assigned. This will assign the name to the FPNO-21 adapter module. Then
click Assign name.
10. Download the hardware configuration to the PLC.

The PLC is now ready for communication with the adapter module.
￭ Resetting PROFINET IO device to factory default via S7

You can reset the PROFINET IO device to factory default.
1. In HW configuration go to PLC → Ethernet → Edit Ethernet Node.
2. In the Edit Ethernet Node window, click Browse....

The list of available devices appear.

3. Select the device that needs to be reset to default. Click OK.
4. Click Reset to clear configuration.
5. A pop-up window appears when reset started. Click OK.

The configuration is now reset to default (PROFINET IO station name, Ethernet services
configuration).
￭ Configuring a Siemens PLC with TIA14

This example shows how to configure communication between a Siemens SIMATIC S7
PLC and the adapter module using SIMATIC Manager Step 7.
Document library.
1. Start TIA14 and create new project.
2. Change to project view.
3. Install the FPNO-21 GSD file:
• Options > Manage general station description files
• Browse to source path where GSDML file is located.
• Select the check box and click Install.
4. Add new device and select CPU from list.
5. Add FPNO-21 to device configuration.

6. Open FPNO-21 device view and add desired telegram to slot 1.
7. Assign FPNO-21 to PROFINET controller.

8. Select Properties tab > General tab > Ethernet addresses submenu, and set the PLC
IP address.
9. In FPNO-21 properties, Ethernet addresses submenu, set FPNO-21 IP address and

PROFINET device name. Device name will be used as identification. After successful
identification, PLC will assign IP address to FPNO-21.
10. Add new function block ABB_Drive.
11. Add variables to ABB_Drive FB.

12. Add ABB_Drive to OB1. Assign new instance Data Block for ABB_Drive FB.
13. Add FPNO-21 PPO HW address to Drive PPO HW ADDR FB input.
14. Add blocks DPRD_DAT and DPWR_DAT to ABB_Drive FB. Map inputs and outputs.
15. Save and download project to PLC.

16. In device configuration, right-click FPNO-21 icon and select Assign device name.
17. Values can now be monitored when online.
18. If values want to be forced, add FPNO-21 addresses to tag table, and add the tag table
variables to the force table.
Media Redundancy Protocol (MRP)

The Media Redundancy Protocol (MRP) network uses ring topology that includes multiple
nodes as shown in the connection diagram below. One of the nodes has the Media
Redundancy Manager (MRM) role and the nodes with FPNO-21 module(s) have the role
of Media Redundancy Clients (MRC). Each node, MRM or MRC, has a pair of ports for
connecting in the ring.
For FPNO-21 module, the link speed of both ports is 100 Mbit/s, full duplex.
Note:
The number of nodes in the ring should not exceed 50 nodes.
1 2
...
4
No. Description
1 ABB drive
2 ABB drive
3 FPNO-21 module
4 PLC MRM (Media Redundancy Manager)
5 Port 1
6 Port 2
￭ Configuring Media Redundancy Protocol (MRP) with Siemens PLC

You can configure MRP for Siemens PLC with SIMATIC S7 after setting the basic
configuration. For instructions on basic configuration, see section Configuring a Siemens
SIMATIC S7 PLC (page 43).
1. Double-click PN-IO in the station window.
PN-IO properties window is displayed.

2. In the Properties PN-IO window, select Media Redundancy tab.
3. From the Role drop-down list, select Manager (Auto) role for the PLC and then click
OK.
4. In the master station window, click FPNO and then double-click Interface.
Properties-Interface window is displayed.

5. In the Properties-Interface window, select Media Redundancy tab.
6. From the Role drop-down list, select Client role for the FPNO module.
7. In the Properties-Interface window, select IO Cycle and set watchdog time.
A recommended value for the watchdog time is 200 ms. Make sure that the connection
is maintained during the ring break.
8. In the master station window, right-click on PROFINET IO System and select PROFINET
IO Domain Management.
The configured devices (PN-IO and FPNO) are shown in the Domain management
window.
￭ Configuring Media Redundancy Protocol (MRP) with TIA14

You can configure MRP for Siemens PLC with TIA14 after setting the basic configuration.
For instructions of basic configuration, see section Configuring a Siemens PLC with
TIA14 (page 52).
To configure an MRP with TIA portal, proceed as follows:

1. In TIA portal Device overview, expand PLC and select the desired PROFINET interface.
PROFINET interface view is displayed.
2. In PROFINET interface view, click General tab and select Media Redundancy and then
select Manager (auto) role for the PLC.
3. In the Device overview, expand FPNO-21 and select Interface.
PROFINET interface view is displayed.
4. In PROFINET interface view, click General tab and select Media Redundancy and then
select Client role for the PLC.
5. In the General tab, select IO cycle and set watchdog time.
The recommended value for the watchdog time is 200 ms. Make sure that the connection
is maintained during the ring break.
For MRP domain management, go to Media Redundancy view and click Domain settings
button.
Shared Device
Using Shared Device enable option, you can access one drive from two controllers through
one FPNO-21 module.
For example, one PLC to control the drive, other Safety PLC for safety communication. The
PROFINET drive control and PROFIsafe can be used by separate PLCs.
￭ Configuring Shared Device for ABB PLC with Automation builder

Configuring drive control PLC
1. Select PPO telegram to use on slot 1. Leave slot 2 empty.
2. Define PROFINET station name and IP address based on the network.
Configuring safety PLC

1. Select safety telegram to use on slot 2. Leave slot 1 empty.
2. Use same PROFINET station name as in drive control PLC configuration.

3. Under Option tab, tick the Shared Device check box.
￭ Configuring Shared Device for Siemens PLC with TIA portal

Configuring drive control PLC
1. Select PPO telegram to use on slot 1. Leave slot 2 empty.
2. Define PROFINET station name and IP address.
Configuring safety PLC

1. Select safety telegram to use on slot 2. Leave slot 1 empty.
2. Use same PROFINET station name as in drive control PLC configuration.
3. Choose the master from the Shared Device tab by changing the master in the Access
column.
PPO frame is located in port 1 and safety telegrams are located in port 2.
74
PROFINET IO – Communication profiles 75
7
PROFINET IO – Communication profiles

This chapter describes the communication profiles used in the communication between the
PROFINET IO master, the adapter module and the drive.
Communication profiles
Communication profiles are ways of conveying control commands (Control word, Status
word, references and actual values) between the master station and the drive.
With the FPNO-21 module, the PROFINET network may employ either the PROFIdrive
profile or the ABB Drives profile. Both are converted to the native profile (e.g., DCU or FBA)
by the adapter module. In addition, two Transparent modes – for 16-bit and 32-bit words
respectively – are available. With the Transparent modes, no data conversion takes place.
The figure below illustrates the profile selection:
Profile_selection.pdf
The figure below
76 PROFINET illustrates
IO – Communication the profile selection:
profiles
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)
Note:
Native profile (eg, DCU or FBA)
The diagram is applicable only when PPO messaging is used. If Standard Telegrams (ST)
are used, the communication profile is selected automatically.
Note: The diagram is applicable only when PPO messaging is used. If
The following sections describe the Control word, the Status word, references and actual
Standard Telegrams
values for the (ST)
PROFIdrive andare
ABBused,
Drivesthe communication
communication profile
profiles. Refer is
to selected
the drive
automatically.
manuals for details on the native profiles.
The following sections describe the Control word, the Status word,
PROFIdrive
references andcommunication profile
actual values for the PROFIdrive and ABB Drives
communication profiles. Refer to the drive manuals for details on
￭ Control word and Status word
the native profiles.
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).
The contents of the Control word and the Status word are detailed below. See the drive
documentation for information on the drive-specific bits. The drive states are presented on
page 80. The drive states for the positioning mode are presented on page 80.
Control word contents

The table below shows the contents of the Control word for the PROFIdrive communication
profile (PROFIdrive parameter 967). The upper case boldface text refers to the states shown
in the state machine on page 80.
Bit Name Value STATE/Description
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).
0 Emergency OFF, coast to stop. Proceed to OFF2 ACTIVE;

proceed further to SWITCH-ON INHIBIT.
2 OFF3 1 Continue operation (OFF3 inactive).
0 Emergency stop, stop according to fastest possible decelera-

tion mode. Proceed to OFF3 ACTIVE; proceed further to
SWITCH-ON INHIBIT.
Warning: Ensure motor and driven machine can be stopped
using this stop mode.
3 OPERATION_ENABLE 1 Proceed to ENABLE OPERATION.
0 Inhibit operation. Proceed to OPERATION INHIBIT.
4 ENABLE_ RAMP_ GENER- 1 Normal operation. Proceed to Normal operation. Do not re-
ATOR RAMP FUNCTION GENER- ject traversing task.
or ATOR: ENABLE OUTPUT.
TRAVERSING _TASK 0 Stop according to selected Reject traversing task.
stop type.
5 1 Normal operation. Proceed to Normal operation. No interme-

RAMP FUNCTION GENERAT- diate stop.
OR: ENABLE ACCELERA-
TION.
0 Halt ramping (Ramp Function Intermediate stop

Generator output held).
6 1 Normal operation. Proceed to Activate traversing task (0 →

OPERATING. 1). This is a toggle bit; each
Note: This bit is effective only rising edge of signal enables
if the fieldbus interface is set a traversing task or a new set
as the source for this signal point.
by drive parameters.
0 Force Ramp Function Gener-

ator 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_ CMD 1 Fieldbus control enabled
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 as defined Start homing procedure.

by PROFIdrive parameter 933
0 Stop homing procedure.
12 Vendor-specific bit as defined by PROFIdrive parameter 934.

As default mapped to Drive Main CW bit 12.



Status word contents

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 machine on page 80.
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 ENABLE OPERATION
0 OPERATION INHIBIT
3 TRIPPED 1 FAULT
0 No fault
4 OFF_2_STA 1 OFF2 inactive
0 OFF2 ACTIVE
0 OFF3 ACTIVE
6 SWC_ON_ INHIB 1 SWITCH-ON INHIBIT ACTIVE
0 SWITCH-ON INHIBIT NOT ACTIVE
7 ALARM 1 Warning/Alarm
0 No Warning/Alarm
8 AT_SETPOINT 1 OPERATING. Actual value equals reference value (= is

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

ance limits).
9 REMOTE 1 Automation system is requested to assume control.
0 Control by automation system is not possible. Control is

possible only at the device or by another interface.
10 1 Actual frequency or speed Target position reached.

value equals or is greater than
supervision limit.
0 Actual frequency or speed Not at target position

value is within supervision
limit.
11 1 Mapped to PROFIdrive SW Homing procedure was ex-

bit 11. ecuted and is valid.
Vendor-specific bit as defined
0 by PROFIdrive parameter No valid home position avail-
939. able.
As default mapped to
PROFIdrive SW bit 11.
12 1 Mapped to PROFIdrive SW Traversing task acknowledge-

bit 11. ment (0 → 1)
0 Vendor-specific bit as defined
by PROFIdrive parameter
940.
13 1 Mapped to PROFIdrive SW Drive stopped.

bit 11.
0 Vendor-specific bit as defined Drive moving. Traversing task
by PROFIdrive parameter is executed (n <> 0).
941.

As default mapped to PROFIdrive SW bit 14.
PROFINET IO mode
Speed control – Communication profiles
Positioning mode 53
15 Vendor-specific bit as defined by PROFIdrive parameter 943
State machine for all operating modes
State machine for all operating modes
The general PROFIdrive state machine for all operating modes is
The general
shown PROFIdrive state machine for all operating modes is shown below.
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
OPERATION SWITCH ON (SW Bit0=1)
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.
PROFIdrive_state_machine_all.pdf
State machine for the positioning mode
The PROFIdrive state machine for the PROFINET
positioning mode is shown
IO – Communication profiles 81
below.
F
BASIC STATE:
Operating1) (SW Bit10,13=1)
E
(CW Bit4,5=1
and (CW Bit11=1)
CW Bit6
edge 01)
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
01) positioning mode
Braking with
ramp (SW Bit10,13=0)
CW= Control word
SW = Status word
Intermediate
stop
E State
(CW Bit5=0) condition
1)
(CW Bit4=0) In the “Operating”
state of the general
state machine:
Braking with SW bits 0, 1 and 2 = 1
ramp (SW Bit10,13=0) SW bit 6 = 0.
PROFIdrive_state_machine_posit.pdf
￭ References
ABB drives can receive control information from multiple sources including analog and digital
inputs, the drive control panel and a fieldbus adapter module (for example, FPNO-21). To
have the drive controlled through PROFINET, you must select the module 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).
￭ 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 the maximum reference (as defined with a drive parameter, for
example, speed scaling in ACSM1, ACS850, ACQ810, ACS480, ACS580 and ACS880,
and external reference in ACS355).
The scaling of 32-bit actual speed values (NIST_B) in hexadecimal (0…4000 0000h)
corresponds to 0…100% of the maximum reference (as defined with a drive parameter, for
example, speed scaling in ACSM1, ACS850, ACQ810, ACS480, ACS580 and ACS880,
and external reference in ACS355).
ABB Drives communication profile

￭ Control word and Status word
The Control word is the principal means for controlling the drive from a fieldbus system. It
is sent by the fieldbus master station to the drive through the adapter module. The drive
switches between its states according to the bit-coded instructions in the Control word and
returns status information to the master in the Status word.
The contents of the Control word and the Status word are detailed below. The drive states
are presented on page 85.
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 on page 85.
0 OFF1_ CONTROL 1 Proceed to READY TO OPERATE.
0 Stop along currently active deceleration ramp. Proceed to OFF1

ACTIVE; proceed to READY TO SWITCH ON unless other inter-
locks (OFF2, OFF3) are active.
1 OFF2_ CONTROL 1 Continue operation (OFF2 inactive).
0 Emergency OFF, coast to stop. Proceed to OFF2 ACTIVE, pro-

ceed to SWITCH-ON INHIBITED.
2 OFF3_ CONTROL 1 Continue operation (OFF3 inactive).
0 Emergency stop, stop within time defined by drive parameter.

Proceed to OFF3 ACTIVE; proceed to SWITCH-ON INHIBITED.
Warning: Ensure that motor and driven machine can be stopped
using this stop mode.
3 INHIBIT_ OPERATION 1 Proceed to OPERATION ENABLED.
Note:
Run enable signal must be active; see drive documentation. If the
drive is set to receive the Run enable signal from the fieldbus, this
bit activates the signal.
0 Inhibit operation. Proceed to OPERATION INHIBITED.
4 RAMP_OUT_ ZERO 1 Normal operation. Proceed to RAMP 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_ ZERO 1 Normal operation. Proceed to OPERATION.
Note:
This bit is effective only if the fieldbus interface is set as the source
for this signal by drive parameters.
0 Force Ramp Function Generator input to zero.
7 RESET 0→1 Fault reset if an active fault exists. Proceed to SWITCH-ON INHIB-
ITED.
Note:
This bit is effective only if the fieldbus interface is set as the source
for this signal by drive parameters.
0 Continue normal operation.
8 … 9 Reserved
10 REMOTE_ CMD 1 Fieldbus control enabled
0 Control word and reference not getting through to the drive, except
for CW bits OFF1, OFF2 and OFF3.
11 EXT_CTRL_ LOC 1 Select External Control Location EXT2. Effective if control location
parameterized to be selected from fieldbus.
0 Select External Control Location EXT1. Effective if control location

parameterized to be selected from fieldbus.
12 ... Drive-specific (For information, see the drive documentation.)

15
Status word contents

The table below shows the contents of the Status word for the ABB Drives communication
profile. The upper case boldface text refers to the states shown on page 85.
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
0 OFF2 ACTIVE
0 OFF3 ACTIVE
6 SWC_ON_ INHIB 1 SWITCH-ON INHIBITED
0 –
7 ALARM 1 Warning/Alarm
0 No warning/alarm
8 AT_SETPOINT 1 OPERATION. Actual value equals reference (= is within tolerance

limits, i.e., in speed control, speed error is 10% max. of nominal
motor speed).
0 Actual value differs from reference (= is outside tolerance limits).
9 REMOTE 1 Drive control location: REMOTE (EXT1 or EXT2)
0 Drive control location: LOCAL
10 ABOVE_ LIMIT 1 Actual frequency or speed equals or exceeds supervision limit

(set by drive parameter). Valid in both directions of rotation.
0 Actual frequency or speed within supervision limit
11 EXT_CTRL_ LOC 1 External Control Location EXT2 selected. Note concerning

ACS880: This bit is effective only if the fieldbus interface is set
as the target for this signal by drive parameters. User bit 0 selec-
tion (06.33)
0 External Control Location EXT1 selected
12 EXT_RUN_ ENABLE 1 External Run Enable signal received.

Note concerning ACS880: This bit is effective only if the fieldbus
interface is set as the target for this signal by drive parameters.
User bit 1 selection (06.34)
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 0 Fieldbus adapter communication OK
State
The machine
state machine for the ABB Drives communication profile is
shown below.
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
SWITCH ON CW = Control word
A B CD (SW Bit0=0)
SW = Status word
n = Speed
(CW=xxxx x1xx xxxx x110) I = Input current
(CW Bit3=0) RFG = Ramp function
READY TO generator
OPERATION SWITCH ON (SW Bit0=1) f = Frequency
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 ACTIVE (SW Bit4=0)
(SW Bit5=0)
(CW Bit4=0) n(f)=0 / I=0
C D OPERATION
ENABLED (SW Bit2=1)
A
(CW Bit5=0) (CW=xxxx x1xx xxx1 1111)
D RFG: OUTPUT
ENABLED
B
(CW Bit6=0) (CW=xxxx x1xx xx11 1111)
RFG: ACCELERATOR state

ENABLED
C
(CW=xxxx x1xx x111 1111) condition
rising edge
OPERATION
(SW Bit8=1) of the bit
D
ABB_Drives_comm_profile.pdf
ences are 16-bit words containing a sign bit and a 15-bit
er. A negative reference (indicating reversed direction of
on) is formed by calculating the two’s complement from the
sponding86positive
PROFINETreference.
IO – Communication profiles
drives can receive control information from multiple sources

￭ References
ing analog and digital inputs, the drive control panel and a
us adapter module
References are(for
16-bitexample, FENA).
words containing a signTo have
bit and theinteger.
a 15-bit drive A negative reference
olled through thereversed
(indicating fieldbus, youofmust
direction select
rotation) thebymodule
is formed asthethe
calculating two’s complement
e for control information, for example, reference.
from the corresponding positive reference.
ABB drives can receive control information from multiple sources including analog and digital
ng inputs, the drive control panel and a fieldbus adapter module (for example, FPNO-21). To
have the drive controlled through the fieldbus, you must select the module as the source
ences are scaled
for control as shown
information, below. reference.
for example,
Scaling
The values of REF1 MAX and REF2 MAX are set with drive
meters. See the drive
References manuals
are scaled forbelow.
as shown further information.
Note:
SM1, ACS850, ACQ810, ACS480, ACS580 and ACS880,
The values of REF1 in
peed reference (REFx) MAX and REF2
decimal MAX are set with
(0…20000) drive parameters.
corresponds to See the drive
manuals for further information.
0% of the speed scaling value (as defined with a drive
meter). In ACSM1, ACS850, ACQ810, ACS480, ACS580 and ACS880, the speed reference (REFx)
in decimal (0…20000) corresponds to 0…100% of the speed scaling value (as defined with
S355, drive parameter REFx MIN may limit the actual
a drive parameter).
um reference.
In ACS355, drive parameter REFx MIN may limit the actual minimum reference.
Fieldbus Drive
REF2: 10000 REFx MAX / Speed scale
REF1: 20000
REFx MIN
0 -(REFx MIN)
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
caling_references.pdf
functions to be monitored are selected with a drive parameter.
Scaling
Actual values are scaled as shown below.
Note:
The values of REF1 MAX and REF2 MAX are set with drive parameters. See the drive
manuals for further information.
Scaling
Actual values are scaled as shown below.
Note: The values of REF1 MAX and REF2 MAX are set with
PROFINET IO – drive
Communication profiles 87
parameters. See the drive manuals for further information.
Fieldbus Drive
ACT2: 10000 REFx MAX

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

ACT1: -20000
Scaling_actual_values.pdf
88
PROFINET IO – Communication protocol 89
8
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.
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 FPNO-21).
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 (page 40)
.
PROFINET network settings

In PROFINET, network devices are identified with station names. The controller uses DCP
(Discovery and Configuration protocol) to find devices with configured names from the
network. Device with the given name responds with an Identity response which also contains
the current IP address of the device.
If the current IP address differs from the address in the hardware configuration of the
controller, the controller sets the device with a new IP address according to the configuration.
This IP is set as temporary, which means that after reboot of the device, the IP address will
be 0.0.0.0 as specified in the PROFINET standard.
The recommended IP setting for PROFINET is Static IP and address is 0.0.0.0. With this
setting, there is need to configure the IP in only one place (hardware configuration) and this
avoids any IP conflicts among the devices.
PROFINET IO in FPNO-21
When PROFINET IO is selected as the communication protocol, the FPNO-21 module can
employ the ABB Drives, Transparent 16 and Transparent 32 communication profiles or the
PROFIdrive profile. You can select the profile via FPNO-21 configuration parameter 02
Protocol/Profile. You can select the appropriate device access point (DAP) and functional
module with the tool as well.
• Slot 0 has sub-slots, and the DAP module attached to it represents the device itself.
The following sub-slots are available:
• sub-slot 0x0001 is DAP
• sub-slot 0x8000 is interface sub-module
• sub-slot 0x8001 is port 1
• sub-slot 0x8002 is port 2.
• Slot 1 and its sub-slots support other functional modules and sub-modules described
in the GSD file. The following sub-slots are available:
1. For PPO types
• sub-slot 0x0001 is the telegram
2. For Standard telegrams
• sub-slot 0x0001 is the Module Access point
• sub-slot 0x0002 is the telegram
• Slot 2 is used for PROFIsafe

• sub-slot 0x0001 is PROFIsafe telegram
The services provided by the FPNO-21 module

• Cyclic messaging
• Acyclic parameter access mechanism
• Identification & Maintenance functions (I&M)

• Media Redundancy Protocol (MRP)
• Shared Device
• Network Diagnostic (SNMP)
• Topology information (LLDP) with LLDP-MIB
• PROFIdrive parameters (limited in the ABB Drives and Transparent profiles)
• Diagnostic and alarm mechanism (only with the PROFIdrive profile)
• 70Fault
PROFINET IO – Communication
buffer mechanism protocol
(limited in the ABB Drives and Transparent profiles).
Cyclicmessage
Cyclic message types
types
PPO 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 –OUT areafrom

Data sent – Data sent
master from(control
to slave master to
data) slave (control data)
IN area – Data sent from slave to master (actual data)
IN area – Data sent from slave to master (actual data)
Parameter identification:
Parameter ID
identification:
– Parameter identification
ID – Parameter
INDidentification
– Index for arrays
IND – Index for arrays– Parameter value (Max. 4 bytes)
VALUE
PKW – value
VALUE – Parameter Parameter
(Max. 4 ID/value
bytes)
Process data:
PKW – Parameter ID/value
CW – Control word
Process data:
SW – Status word
REF
CW – Control word– Reference
SW – Status word Actual value
ACT –
PZD – Process data (application-specific)
REF – Reference
DW – Data word
ACT – Actual value
1) Not
PZD – Process datasupported
(application-specific)
by ACS355 drives
DW – Data word
1) Not supported by ACS355 drives
PPO_types.pdf
￭ 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 value B Status word 2
Note:
For the contents of the Control word, the Status word, references and actual values, see
chapter PROFINET IO – Communication profiles
￭ Behavior of output data

In the case of IOPS (PLC provider status)=Bad:
Output data retains last values
In the case of connection loss:
Output data retains last values
After power-up:
All output data is 0
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 FPNO-21 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 ad- Src addr. Ether IP UDP RPC NDR Read or Data
dr. type 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 section ErrorCode1 (page 93). Error-
Code2 is 0.
0x81 (PNIO) ErrorCode1 and ErrorCode2 decoded as shown in section Error-

Code1 (page 93).
ErrorCode1 Error class and error code. See section ErrorCode1 (page 93).
ErrorCode2 Not described here
ErrorCode1 ErrorCode1.pdf
ErrorCode1
The table
The table below
below lists
lists the the ErrorCode1
ErrorCode1 with PNIORWwith PNIORW decoding.
decoding.
MSB x x x x x x x x LSB
Error class Meaning Error code

Error class Meaning Error code
0…9 (Reserved)
0…9 (Reserved)
10 (0x0A)
10 (0x0A)
Application
Application
0 = Read error
0 = Read error
1 =error
1 = Write Write error
2 = Module
2 = Module failure failure
3…7 = Reserved
3…7 = Reserved
8 = Version conflict
8 = Version
9 = Feature conflict
not supported
10…15 = User-specific
9 = Feature not supported
11 (0x0B) Access 0 = Invalid index
1 = Write length error
2 = Invalid slot
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
74 PROFINET IO –User-specific
13…15
Communication protocol DP-V1 read_write_seq.pdf
￭DP-V1
DP-V1 read/write
read/write requestrequest
sequencesequence
AAread/write service
read/write on a drive
service onparameter is illustrated below.
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
The messaging employs
messaging DP-V1 data
employs units. The
DP-V1 dataPROFIdrive parameter
units. The request is included
PROFIdrive
within
parameter request is included within the DP-V1 request the
the DP-V1 request as data. Likewise, the DP-V1 response contains as PROFIdrive
data.
parameter response as data.
Likewise, the DP-V1 response contains the PROFIdrive parameter
Aresponse
write requestas data.
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
A then
will writesend
request
a read is first sent
request. containing
If the adapter the
module parameter
is still request.
busy performing If the
the internal
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
parameter request, it will return a negative response with the DP-V1 error code B5h (State
conflict). In this case, the master will repeat the read request 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
section ErrorCode1 (page 93)).
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 service Request (0x00) UI8

Response (0x80)
Operation Read or Write operation Write (0x08) UI8

Read (0x09)
Block length Length of the block 0…0xFFFF UI16
ARUUID Identifier UI32

• time low UI16
• time mid UI16
• time high and version
Octet[2]
• clock
• node Octet[6]
API Application process identifier Device access point UI32

(0x0000)
PROFIdrive (0x3A00)
Slot Slot of the module access point 0x01 UI16

(MAP/PAP)
Subslot Subslot of the module access point 0x01 UI16

(MAP/PAP)
Padding 2 bytes
Index Index of the record data object 0x2F UI16

0xB02E
0xB02F
Data length Length of the data block 0…0xFFFFFFFF UI32
Additional value 1 Field for transferring additional data UI16

(response only)
Additional value 2 Field for transferring additional data UI16

(response only)
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 Reference Unique identification set by the mas- 1…255 Byte

ter. Changed for each new request.
Request ID Request type for the issued block Request Parameter (01h) Byte
Change Parameter (02h)
Drive Object ID To be set to 0 or 1. 0…255 Byte
No. of Parameters Number of the parameters that are 1…37 Byte

present in the request
Attribute Type of the object being accessed. Value (10h) Description Byte
Note: “Description” and “Text” are not (20h) Text (30h)
supported.
No. of Elements Number of the array elements ac- 0, 1…234 Byte

cessed or length of the string ac-
cessed. Set to 0 if non-array paramet-
ers are used.
Parameter Index Address of the parameter that is being 1…65535 Word

accessed. “0” is allowed by FPNO-21.
Subindex Addresses 0…65535 Word

• the first array element of the para-
meter 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 97. See the table on page 97. Byte
Number of Values1) Number of the values following 0…234 Byte
Values1) The values of the request. In case of – See the Format

an odd number of bytes, a zero byte field.
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 Reference Mirrored from the request. 1…255

(mirrored)
Response ID Response from the slave. In case any requested Request Param OK
services fail, a “not acknowledged” (NAK) re- (01h)
sponse will be indicated. Request Param NAK
(81h)
Change Param OK
(02h)
Change Param NAK
(82h)
Field(s) Description Range
Drive Object ID To be set to 1. 0…255
No. of Parameters Number of the parameters that are present in the 1…37
response
Format1) See the table on page 97. See the table on page 97.
Number of Values1) Number of the values following 0…234
Values1) The values of the request. In case of an odd –

number of bytes, a zero byte is appended to en-
sure the word structure of the telegram.
1)Only if Response ID is 01h (Request Parameter OK). The Format, Numberof 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 parameter number Access to an unavailable parameter
01h Parameter value cannot be changed Change access to a parameter value that cannot be
changed
02h Low or high limit exceeded Change access with a value outside the limits
03h Invalid subindex Access to an unavailable subindex
04h No array Access with a subindex to a non-indexed parameter

Error # Meaning Used at
05h Incorrect data type Change access with a value that does not match the
data type of the parameter
06h Setting not permitted (can only be reset) Change access with a value unequal to 0 when this is
not permitted
07h Description element cannot be changed Change access to a description element that cannot
be changed
09h No description data available Access to an unavailable description (parameter value

is available)
0Bh No operation priority Change access rights without rights to change para-
meters
0Fh No text array available Access to a text array that is not available (Parameter
value is available.)
11h Request cannot be executed because of Access is temporarily not possible for reasons that are
operating mode not specified in 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 max-
imum transmittable length.
16h Parameter address impermissible Illegal value or value that is not supported for the attrib-
ute, 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 inconsistent Write request: Number of values of the parameter data
does not match the number of elements at the paramet-
er address.
65h … Manufacturer-specific error area –

FF
65h Vendor-specific error Vendor-specific error
66h Request not supported Request not supported
67h Communication error Request cannot be completed because of a communic-

ation 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,
e.g., double mapping of bits).
8Ch Set torque mode error Cannot change mode to TORQUE (frequency is used).
96h Internal buffer Buffer overflow
A0h Internal communication Communication error between the
module and the drive
ErrorFunction
# Meaning blocks for sending
Used at DP-V1 messages
90h (Siemens S7)

Illegal Request ID The request ID of the response is illegal.
In96h Internal buffer

IEC 61131-3 Buffer overflow
compatible systems, function blocks are available
for accessing data non-cyclically. In Siemens
A0h Internal communication Communication S7,
error SFB
between 52 and the
the module
drive
"RDREC" can be used for reading and SFB53 "WRREC" for
writing data records as follows:
￭ Function blocks for sending DP-V1 messages (Siemens S7)
• On INDEX: Connect the value 0xB02F, 0xB02E or 0x2F.
In IEC 61131-3 compatible systems, function blocks are available for accessing data
•non-cyclically.
On Write record:S7,
In Siemens Set the
SFB length of
52 "RDREC" canthe DP-V1
be used writeand
for reading request
SFB53 to
"WRREC"
MLEN.for writing data records as follows:
• On INDEX: Connect the value 0xB02F, 0xB02E or 0x2F.
•• On
OnWrite
Read record:
record: Set theSet the
length maximum
of the DP-V1 writelength ofMLEN.
request to the DP-V1 read
response.
• On Read record: Set the maximum length of the DP-V1 read response.
• Connect the DP-V1 message to RECORD.
• Connect the DP-V1 message to RECORD.
RDREC
BOOL --- REQ VALID --- BOOL S7_read_write.pdf
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
Note: The function block names for Siemens 12xx and 15xx series
Note:
The function
PLCs block names and
are RD_REC for Siemens 12xx andand
WR_REC, 15xx this
seriesnaming
PLCs are RD_REC and is
convention
WR_REC, and this naming convention is also applicable for other blocks.
also applicable for other blocks.
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.
Only the data block part of the request is presented in the examples. See section Read and
write blocks (page 95).
Note: Only the data block part of the request is presented in the
examples. See section Read and write blocks on page 75.
Example 1a: Reading a drive parameter (array
element)
Drive
Example 1a:parameters are parameter
Reading a drive addressed so that
(array the drive
element) parameter group
corresponds to the Parameter index (PNU), and the drive
Drive parameters are addressed so that the drive parameter group corresponds to the
parameter number within the group corresponds to the Subindex
Parameter index (PNU), and the drive parameter number within the group corresponds to
(IND). In the following example, a value is read from drive
the Subindex (IND). In the following example, a value is read from drive parameter 12.04
parameter 12.04 (0C.04h).
(0C.04h).
• DP-V1
• DP-V1 Write(Read
Write request request (Readvalue):
parameter 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
84header
PROFINET
DP-V1IO – Communication
Command V3 ParameterDP-V1_Read_request_1.pdf
protocol
PROFIdrive Channel
•
• Positive Read response to DP-V1 Read request:
Positive Read response to DP-V1 Read request:
DP-V1_Write_request_1.pdf
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:

• Negative response to PROFIdrive Read request:
Slot number
Subslot number
Index
Data length
Response ID
Drive object ID (mirrored)
Format (44h = Error)
DP 01 01 B0 2F 08 05 01 01 01 42 01 05 64 DP
• PROFINET
Negative response to PROFIdrive IO –request:
Read Communication protocol 101
Slot number
Subslot number
Index
Data length
Response ID
Format (44h = Error)
Number of values
Reserved
PROFINET IO – Communication protocol
PROFIdrive error 85
code
DP 01 01 B0 2F 08 85 01 01 01 44 01 00 00 DP
Example
header
1b: Reading 3 drive parameters trailer
DP-V1 Response PROFIdrive V3 Parameter Channel
(multi-parameter)
In this example, three parameters (12.04, 20.08 and 30.19) are
PROFIdrive_Read_request.pdf
Example 1b: Reading 3 drive parameters (multi-parameter)
read using one telegram.
In this example, three parameters (12.04, 20.08 and 30.19) are read using one telegram.
• DP-V1 Write request (Read parameter value):
• DP-V1 Write request (Read parameter value)
Slot number
Subslot number
Index
Data length
Request reference
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)
86 PROFINET
102 PROFINET IO – Communication
IO – Communication protocol protocol
•
• Positive Read response to DP-V1 Read request:
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
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).
Drive parameters are addressed so that the drive parameter group
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
88 PROFINET IO – Communication
DP-V1 Command protocol
PROFIdrive V3 Parameter Channel
Slot number
Slot number
Write_param_1202_1.pdf 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.
Write_param_1202_2.pdf
(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
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)

Write_param_1202_2008_1.pdf
For more information

Slot number
on the above function blocks, see document
Communication Function Blocks for PROFIBUS DP and
PROFINET IO v2.0 available
Subslot number at www.profibus.com.
Index
Parameter data transfer examples
Data length
The following examples show how parameter data is transferred
using the DP-V1 mechanisms READ andResponse
WRITE.ID
Note: Only the data block part of the request is presented in the
examples. See section Read and write blocks on pageNumber75.
of parameters
Example
01 1a:
01 Reading
B0 2F a 04
drive08parameter
02 01 (array
02
DP
element) DP
header PROFIdrive V3 trailer
DP-V1 Response
Parameter Channel
Drive parameters are addressed so that the drive parameter group
parameter
Example number
3: Reading within the
a PROFIdrive group corresponds to the Subindex
parameter
(IND). In the following example, a value is read from drive
In this example, PROFIdrive parameter 919 (397h) is used to read the device system number
of theparameter
slave, which12.04 (0C.04h).
is the product code of the drive.
•
• DP-V1 Write request (Reading a(Read
DP-V1 Write request parameter
PROFIdrive value):
parameter):
Write_param_1202_2008_2.pdf
Slot number
Subslot number
Index
Data length
Request reference
Drive object ID
Number of elements
Parameter index
Subindex
DP 01 01 B0 2F 0A 05 01 01 01 10 01 00 0C 00 04
DP trailer
• DP-V1 Read response:

• DP-V1
106 PROFINET IO – Read response:
Communication protocol DP-V1_Read_response_3.pdf
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

The slave returns the product code of the drive (20Bh in this example).
(0C.05h).
Example 4: Configuring the process data written to the drive
Diagnostic
PROFIdrive and
parameter 915 alarm
(393h) can be mechanism
used to define which data is written cyclically to
a drive parameter as application-specific process data.
The FENA adapter module has mechanisms for sending alarms
In theand
example below,
saving the value of data
diagnostics drive parameter
to a fault12.06 (0C.06h)
buffer. is selected
An alarm to be taken
is triggered
from if
PZD3. The parameter will continue to be updated with the contents
the host or drive has faults in communication or operation. The of PZD3 in each
Request frame until a different selection is made.
alarm and fault buffer mechanisms are enabled by default and can
be disabled
Subindex with
(IND) defines a configuration
which parameter
process data word (21data
the required Alarm disable
is taken on
from. Value
page 13).
selects the drive parameter to which that word is mapped.
• DP-V1 Write request
In this example, three parameters (12.04, 20.08 and 30.19) are
read using one telegram.
• DP-V1 Write request (Read parameter
PROFINET IO –value):
Communication protocol 107
Slot number
Subslot number
Index
Data length
Request reference
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
•••
10 01 00 14 00 08
continued)
10 01 00 1E 00 13
DP
continued)
108 PROFINET
• IO – Communication
Positive protocol
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
header DP-V1 Response
Channel
42 01 01 F4
cont’d)
42 01 00 30
DP
cont’d)
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
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 trailer95
PROFINET IO – Communication protocol
header DP-V1 Response PROFIdrive V3 Parameter Channel
• DP-V1 Read response: DP-V1_Read_response_3.pdf

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

Value(0C.05h).
indicates the source of PZD3 as drive parameter 12.05 (0C.05h).
Diagnostic and and

Diagnostic alarm mechanism
alarm mechanism
The FPNO-21 module has mechanisms for sending alarms and saving diagnostics data to
a faultThe FENA
buffer. adapter
An alarm module
is triggered if thehas
host mechanisms forin sending
or drive has faults alarms
communication or
and saving diagnostics data to a fault buffer. An alarm is triggered
operation. The alarm and fault buffer mechanisms are enabled by default and can be disabled
with aifconfiguration
the host orparameter,
drive has faults
see FPNO-21in communication or operation.
configuration parameters – group AThe
(group
alarm
1) (page 28).and fault buffer mechanisms are enabled by default and can
be disabled with a configuration parameter (21 Alarm disable on
￭ Alarm
pagemechanism
13).
When a fault situation occurs, the adapter module sends an alarm notification, which the
master station has to acknowledge. Alarm notifications can be acknowledged, viewed and
handled, for example, with Siemens S7 blocks OB82, OB83, OB86 and OB122.
• Block OB82 is used to make sure that the drive does not go to the stop mode during a
diagnostic alarm.
• Block OB83 is called if a module is inserted or removed from the system or if the module
is modified.
• Block OB86 indicates if there is a failure or event in the distributed periphery.
• Block OB122 is called if the CPU calls a device that is not accessible.
Fault code mapping

An alarm notification contains a fault code, which is called ChannelErrorType. For PROFIdrive
API, the drive internal DRIVECOM fault numbers are mapped to PROFIdrive
ChannelErrorTypes according to the table below. The fault numbers that are not listed are
mapped to ChannelErrorType Other.
ChannelErrorType Description DRIVECOM fault numbers
0x9000 Microcontroller hardware or software 4211, 5000, 5401, 5402, 5403,

5484, 5691, 5693, 6100, 6180,
6300, 6306, 6306, 6320, 6481,
6487, 630D, 630F, 64A1, 64A2,
64A3, 64E1, 6581, 65A1, 6682,
6683, 6684, 6881, FF55
0x9001 Mains supply 3291
0x9002 Low voltage supply 3130, 3220
0x9003 DC link overvoltage 3210
0x9004 Power electronics 2211, 2281, 2310, 2312, 2340,

2381, 3180, 3181, 3182, 3183,
3184, 3185, 3186, 3187, 3381,
3385, 5400, 5482, 5682, 5692, FF56
0x9005 Overtemperature electronic device 4110, 4210, 4212, 4290, 4310,

4313, 4981, 7182, 42F1, 4380
0x9006 Earth/ground fault 2330
0x9007 Motor overload 7121
0x9008 Fieldbus system
0x9009 Safety channel 8182, 8183, 5090, 5091, FA81,

FA82, FF7A, FFA0, FFA1, FFA2
0x900A Feedback 7301, 7310, 7380, 7381, 7389,

7391, 8480, 8584, 738A, 738B,
738C, 73A0, 73A1
0x900B Internal communication 5480, 5681, 5690, 7000, 7080,

7081, 7510, 7520, 7540, 7584
0x900C Infeed
0x900D Brake resistor 7111, 7112, 7113, 7181, 7183,

7184, 7185, 7186, 7187, 7191,
71A2, 71A3, 71A5
0x900E Line filter
0x900F External 9000, 9001, 9081, FF81, FF82,

FF8E, FF90
ChannelErrorType Description DRIVECOM fault numbers
0x9010 Technology 6382
0x9011 Engineering
0x9012 Other 5080, 5093, 5210, 5300, 6200,

7583, 8110, 8500, 8582, 8583,
FF61, FF69, FF6A, FF83, FF84,
FF95
￭ Fault buffer mechanism

The PROFIdrive profile has a mechanism that can store eight fault situations to PROFIdrive
parameters. Fault and diagnostic data, like fault number and fault code, can be accessed
simultaneously with only one subindex. The mechanism consists of four PROFIdrive
parameters:
• PNU944: Fault message counter.
• Incremented each time the fault buffer changes.
• PNU945: PROFIdrive fault codes presented in section on page .
• PNU946: Fault code list that converts fault numbers to fault codes.
• Read using the fault number as a subindex to get the corresponding fault code.
• PNU947: Fault numbers according to the DRIVECOM profile.
The table below illustrates the structure of a fault buffer. The fault buffer consists of two
parameters: fault number (PNU 947) and fault code (PNU 945). The rows of the fault buffer
are represented by the parameter subindices. Fault messages are entered into the buffer
in the sequence they are detected. Each line in the fault buffer represents a fault message,
which is a part of a fault situation. A fault situation lasts from a detection of a fault to its
acknowledgement.
Fault situation PNU947 PNU945
Fault number Fault code Subindex
0x4210 0x9005 0
0 0 1
0 0 2
0 0 3
0 0 4
0 0 5
Actual fault situation n 0 0 6
0 0 7
Fault situation PNU947 PNU945
Fault number Fault code Subindex
0x7510 0x900B 8
0 0 9
0 0 10
0 0 11
0 0 12
0 0 13
Fault situation n-1 0 0 14
0 0 15
… … … …
0 0 56
0 0 57
0 0 58
0 0 59
0 0 60
0 0 61
Fault situation n-7 0 0 62
0 0 63
PROFINET IO – Diagnostics 113
9
PROFINET IO – Diagnostics

This chapter explains how to trace faults with the status LEDs on the adapter module when
the module is used for PROFINET IO communication.
Fault and warning messages

For the fault and warning messages concerning the adapter module, see the drive firmware
manual.
LEDs
The adapter module is equipped with three bicolor diagnostic LEDs. The LEDs are described
below.
114 PROFINET IO – Diagnostics
Name Color Function
Flashing green Establishing communication to drive
Green Connection to drive OK
Flashing red Communication to drive lost temporarily
the module
Flashing orange, al- Internal file system error. The error may be cleared by cycling
HOST ternating with the drive power. If the error persists, contact your local ABB repres-
MODULE flashing entative.
orange
Off There is no power applied to the device.
Flashing orange Device is blinking. Used for identification. The blinking is started
by the PROFINET master and also the network LED is flashing
green.
Flashing green Device is waiting for PROFINET connection.

This may be caused by missing PROFINET station name config-
uration or PLC is not running.
Green Device is operating in normal condition.
Flashing red Recoverable fault
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.
MODULE Flashing red-green Device is in Self Test.
ternating with the drive power. If the error persists, contact your local ABB repres-
HOST flashing or- entative.
ange
PROFINET IO – Diagnostics 115
Name Color Function
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.
of the module
NETWORK/NET
Flashing green Device is receiving/transmitting on the Ethernet.
116
NONE – Start-up 117
10
NONE – 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.
Warnings
WARNING!
Obey the safety instructions given in this manual and the drive documentation.
Drive configuration
The information in this section applies to all drive types compatible with the adapter module,
unless otherwise stated.
￭ Connection configuration using NONE protocol

After the adapter module is mechanically and electrically installed according to the instructions
in chapters Mechanical installation and Electrical installation, you must prepare the drive
for communication with the module.
The detailed procedure of activating the module using the NONE protocol with the drive
depends on the drive type. Normally, you must adjust a parameter to activate the
communication. See the drive-specific start-up sections Starting up fieldbus
communication (page 121).
Once communication between the drive and the adapter module is established, several
configuration parameters are copied to the drive. These parameters are shown in the tables
below and must be checked first and adjusted where necessary. You can adjust the
parameters via a drive control panel, a web user interface, or a PC tool.
Note:
• Not all drives will display the descriptive names for the configuration parameters.
• The new parameter settings take effect only when you power up the module the next
time or when you activate the fieldbus adapter refresh parameter.
• Use the NONE protocol selection when no fieldbus protocol is required. For example,
when only the Ethernet tool network is used or for synchronizing time.
FPNO-21 configuration parameters – group A (group 1)
Note:
The actual parameter group number depends on the drive type. Group A (group 1)
corresponds to:
• parameter group 51 in ACS380, ACS480, ACH580, ACQ580 and ACS580.
01 FBA TYPE Read-only. Shows the fieldbus adapter type as detec- 132 = PROFINET IO
ted by the drive. The value cannot be adjusted by the
user.
If the value is 0 = None, the communication between
the drive and the module has not been established.
02 Protocol/Profile Selects the application protocol and communication 11 = PNIO ABB Pro
profile for the network connection.
Select NONE to disable PROFINET protocol. Other
services (ABB IP Configuration tool, Ethernet tool net-
work, SNTP, etc.) are still available, see Service con-
figuration page (page 146).
200 = NONE NONE protocol
03 Commrate Sets the bit rate for the Ethernet interface. 0 = Auto
1 = 100 Mbps FD
2 = 100 Mbps HD
3 = 10 Mbps FD
4 = 10 Mbps HD
04 IP configuration Sets the method for configuring the IP address, subnet 1 = Dyn IP DHCP
mask and gateway address for the module.
0 = Static IP Configuration is obtained from parameters 05-13.
1 = Dyn IP DHCP Configuration is obtained via DHCP.

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

... work. An IP address is a 32-bit number that is typically
represented in “dotted decimal” notation consisting of
08
four decimal integers, on the range 0…255, separated
by periods. Each integer represents the value of one
octet (8-bits) in the IP address. Parameters define the
four octets of the IP address.
0...255 IP address
... ... ...
IP address 4 See parameter 05 (page 119) IP address 1 (page 119). 0
0...255 IP address
09 Subnet CIDR Subnet masks are used for splitting networks into 0
smaller networks called subnets. A subnet mask is a
32-bit binary number that splits the IP address into a
network address and host address.
Subnet masks are typically represented in either dotted
decimal notation or the more compact CIDR notation,
as shown in the table below.
CIDR Dotted decimal CIDR Dotted decimal

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

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

... into a unified IP network. When an IP node needs to
communicate with an IP node on another subnet, the
13
IP node sends the data to the IP gateway for forward-
ing. Parameters define the four octets of the gateway
address.
0...255 GW address
... ... ...
GW address 4 See parameter 10 (page 120) GW address 1 (page 120). 0
0.255 GW address
14 Commrate port 2 Sets the bit rate for the Ethernet port 2. 0 = Auto
15 Reserved These parameters are not used by the adapter module N/A
... when using the NONE protocol.
25
26 Reserved Reserved for web page functionality. For more inform- N/A
ation, see Appendix C - FPNO-21 configuration web
pages (page 141).
27 FBA A/B par refresh Validates any changed adapter module configuration 0 = Done
parameter settings. After refreshing, the value reverts
automatically to 0 = Done.
Note:
This parameter cannot be changed while the drive is
running.
0 = Done Refreshing done
1 = Refresh Refreshing
28 FBA A/B par table ver Read-only. Displays the parameter table revision of N/A
the fieldbus adapter module mapping file stored in the
memory of the drive. In format xyz, where
x = major revision number
y = minor revision number
z = correction number
OR
in format axyz, where
a = major revision number
xy = minor revision numbers
z = correction number or letter.
Parameter table revision

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

ping file
30 FBA A/B mapping file Read-only. Displays the fieldbus adapter module N/A
ver mapping file revision stored in the memory of the drive
in decimal format.
Mapping file revision
31 D2FBA A/B comm Read-only. Displays the status of the fieldbus adapter 0 = Idle
status module communication. or
4 = Offline
Note: or
The value names may vary by drive. 2 = Time out
0 = Idle Adapter is not configured.
1 = Exec.init Adapter is initializing.
2= Time out A timeout has occurred in the communication between

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

between the adapter and the drive. Contact your local
ABB representative.
4 = Off-line Adapter is off-line.
5 = On-line Adapter is on-line.
6 = Reset Adapter is performing a hardware reset.
32 FBA A/B comm SW Read-only. Displays patch and build numbers of the N/A
ver adapter module's firmware version in xxyy format,
where:
xx = patch number
yy = build number.
jor>.<minor>.<patch>.<build>) is 3.10.200.13, the value
C80D is displayed. If the version is 3.10.0.0, the value
0 is displayed.
33 FBA A/B appl SW ver Read-only. Displays major and minor revision numbers N/A
of the adapter module's firmware version in xxyy
format, where:
xx = major revision number
yy = minor revision number
jor>.<minor>.<patch>.<build>) is 3.10.200.13 or
3.10.0.0, the value 310 is displayed.
Starting up fieldbus communication

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

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

For the fault and warning messages concerning the adapter module, see the drive firmware
manual.
LEDs
The adapter module is equipped with three bicolor diagnostic LEDs. The LEDs are described
below.
124 NONE - Diagnostics
Name Color Function
Flashing green Establishing communication to drive
Green Connection to drive OK
Flashing red Communication to drive lost temporarily
the module
HOST Flashing orange, al- Internal file system error. The error may be cleared by cycling
MODULE flashing entative.
orange
Off There is no PC tool connected to the device.
Flashing orange Device is attempting to obtain IP configuration from the DHCP

server.
Orange Device is executing Duplicate Address Detection.
Green PC tool is connected to the device.
Flashing red Ethernet link is down.
Red Ethernet interface is disabled. Duplicate Address Detection may

MODULE have detected a duplicate address. Check the IP configuration
and either initiate a Fieldbus Adapter parameter refresh or cycle
power to the drive.
HOST flashing or- entative.
ange
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.

NETWORK/NET Flashing indicates activity on interface.
Technical data 125
12
1 2 3 4 5 6
First angle projection. Original drawing made with 3D CAD. Set the correct scale factor when adding
dimensions after DWG/DXF conversion.
Technical data
therein. Reproduction,
A
forbidden.

23,6
[1]
use or disclosure to third parties without express authority is strictly
This chapter contains the technical specifications of the FPNO-21 module.

We reserve all rights in this document and in the information contained
B Dimension drawing
© ABB Oy. PROPRIETARY AND SECRET INFORMATION. CONFIDENTIAL
SUPPLY CONDITION
LOCK OPEN
63 5 16 20 15
[.30]
[2.48] [.20] [.63] [.80] [.
7,5
C
[2.56]
[1.97]
D
65
50
A.0+
-.0
E
3 23
[.12] [.89]
3AXD50000190256
FPNO-21 (ASSEM)
F Based on Prepared T.Huoso 19-Oct-17 Title DIMENSION DRAWING Doc. d

Customer Check. M.Karna 19-Oct-17 FPNO-21 ADAPTER DIMEN
Appr. V.Jung 19-Oct-17 PROFINET IO Resp.de
Cust. Doc. No. Project name Doc. N
DMS Number 3AXD10000657934 Weight kg 0.07
126 Technical data
General data
Installation Into an option slot on the drive control unit
Degree of protection IP20
Ambient conditions The applicable ambient conditions specified for the drive in its manuals
are in effect.
Package Cardboard. Plastic wrapping: Antistatic air bubble sheet (PE).
Indicators Three bicolor LEDs (HOST, MODULE, NETWORK/NET)
Connectors A 20-pin connector to the drive

RJ-45 connector to Ethernet (X1)
RJ-45 connector for chaining another adapter module (X2)
Power supply +3.3 V ±5% max. 400 mA (supplied by the drive)
General Complies with EMC standard EN 61800-3:2004

Printed circuit board conformal coated
Ethernet link
Compatible devices Ethernet Standard IEEE 802.3 and IEEE 802.3u devices
Medium 10BASE-TX or 100Base-TX with Auto-negotiation and Auto-MDIX (Auto-

crossover)
• Wiring: CAT5/6 UTP, CAT5/6 FTP, CAT5/6 STP
• Connector: RJ-45
• Termination: Internal
• Maximum segment length: 100 m / 328 ft
Topology Bus, star or ring.
Max. 50 nodes allowed for FPNO-21 module in a ring topology.
In a chain maximum recommended amount of nodes is 50. More can be
used but PROFINET cycle time should be adjusted because of the delays
in the network. Each FPNO-21 has an integrated switch which adds 19
μs forwarding delay for the minimum Ethernet frame. Length of
PROFINET cyclic frame FPNO-21 uses is minimum Ethernet frame so
50 nodes will add 1 ms delay for the PROFINET frame.
Transfer rate 10 Mbps or 100 Mbps
Serial communication type Half or full duplex
Protocol PROFINET IO
TCP and UDP service ports

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

34962 (TCP/UDP) PROFINET PROFINET RT Unicast.
Note:
Used only when PROFINET IO protocol is selected.
Technical data 127
Port Service Purpose

34963 (TCP/UDP) PROFINET PROFINET RT Multicast.
Note:
34964 (TCP/UDP) PROFINET PROFINET Context Manager.
Note:
80 (TCP) HTTP Web server, provides the UI over HTTP protocol.

Used for Ethernet tool communication. To disable, go to Service
configuration page (page 146) via web interface.
68 (UDP) DHCP DHCP client
Note:
Used only when IP configuration method is selected as "Dyn IP
HFCP".
24576 (UDP) ABB Netconfig • Auto discovery protocol

• Used by ControlBuilder plus (IP Configuration tool) and Drive
composer pro and DriveWindow 2.40 PC tools
• Discovers ABB-specific Ethernet devices in a local network
segment, by listening to and responding to UDP broadcasts.
To disable, go to Service configuration page (page 146) via web
interface.
123 (UDP) SNTP Simple Network Time Protocol.
By default, this service is switched off. To enable the service, go
to Service configuration page (page 146) via web interface.
161 (UDP) SNMP Simple Network Management Protocol (SNMP).
Note:
To disable, go to Service configuration page (page 146) via web

interface.
128
Appendix A – PROFIdrive parameters and I&M records of PROFINET IO 129
13
Appendix A – PROFIdrive parameters
and I&M records of PROFINET IO

• PROFIdrive parameters of the PROFINET IO communication protocol
• telegram and response structures for the I&M (Identification & Maintenance) records of
the PROFINET IO communication protocol.
PROFIdrive parameters
Par. no. R/W1) Data type Description
915 R/W Array [12] Unsigned16 Assignment PZD1 to PZD12 in PPO-write
916 R/W Array [12] Unsigned16 Assignment PZD1 to PZD12 in PPO-read
919 R Octet String4 Device system number
922 R Unsigned16 Telegram selection

923 R Array [n] Unsigned16 List of all parameters for signals. Mandatory if process data
normalization is used and/or parameters 915 and 916 are
implemented.
Signal no. and name Type

1 – Control word 1 (STW1) Unsigned16
2 – Status word 1 (ZSW1) Unsigned16
3 – Control word 2 (STW2) Unsigned16
4 – Status word 2 (ZSW2) Unsigned16
5 – Speed set point A (NSOLL_A) Signed16
6 – Speed actual value A (NIST_A) Signed16
7 – Speed set point B (NSOLL_B) Signed32
8 – Speed actual value B (NIST_B) Signed32
27 – Position set point A (XSOLL_A) Signed32
28 – Position actual value A (XIST_A) Signed32
32 – Traversing block selection Unsigned16
(SATZANW) (not supported)
33 – Actual traversing block (AKTSATZ) Unsigned16
(not supported)
34 – Target position (TARPOS_A) (not Signed32
supported)
35 – Velocity (VELOCITY_A) Unsigned32
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, i.e., Receipt of new PZD
data is ignored.
1 PZD part is enabled (default).

929 R Unsigned16 Selected PPO type
Value PPO type

1 PPO1
2 PPO2
3 PPO3
4 PPO4
5 PPO5
6 PPO6
7 PPO7
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 with bit

0 None
1 to 5 Vendor-specific 1 to 52)
934 R/W Unsigned16 Selection switch for Control word, bit 12. (See parameter 933
for coding.)
for coding.)
for coding.)
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 12. (See parameter 939
for coding.)
for coding.)

for coding)
for coding.)
944 R Unsigned16 Fault message counter
945 R Array[64] Unsigned16 Fault code (Channel Error Type)
Sub- Contents
index
0 Last fault
8 Second last ackn. fault
16 Third last ackn. fault
24 Fourth last ackn. fault
32 Fifth last ackn. fault
40 Sixth last ackn. fault
48 Seventh last ackn. fault
56 Eighth last ackn. fault
946 R Array [n] Unsigned16 Fault code list. Contains the mapping between DRIVECOM
fault codes and Channel Error Types.
If you use a DRIVECOM fault code as an index when reading
PNU946, the corresponding Channel Error Type is returned.
947 R Array [64] Unsigned16 Fault number (coded according to the DRIVECOM profile).
Subindex Contents
See parameter 945.
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)
964 R Array [7] Unsigned16
Sub- Contents
index
0 Manufacturer
1 Device type
2 Version
3 Firmware date (year)
4 Firmware date (day/month)
5 Number of Axes
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

972 R/W Unsigned16 Software reset
Value Description
0 No action
1 Re-boot PROFIBUS module

975 R Array[n] Unsigned16 DO identification. For subindexes 0…4, see parameter 964.
Sub- Meaning
index
5 Value 2 = Axis
980 R Array[n] Unsigned16 Number list of defined parameters. If the subindex is 0, the
981 end of the list has been reached. If the subindex is the num-
ber of the next list parameter, the list is continued there.
1000 R/W Unsigned16 Map 16-bit selection3). Used to request the data type for
mapped parameters if mapping is done with parameter 915
or 916.
Value Description
1 User 16-bit mapping, if available.
1001 R/W Integer16 SNTP time offset to UTC time.
Value Description
-1440, 1440 Time in minutes to offset the UTC time re-
ceived from SNTP

50000 R/W Unsigned16 Disable alarms.
Value Description
0 PNIO alarms enabled
1 PNIO alarms disabled
61000 R VisibleString24 Name of station

61001 R Unsigned32 IP of station
61002 R OctetString[6] MAC address of station
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 control program.
3) Support depends on the drive type.
I&M records
I&M (Identification & Maintenance) records can be read, for example, with the DTM tool.
The FPNO-21 module supports the mandatory I&M0 record as well as the optional I&M1,
I&M2, I&M3 and I&M4 records.
￭ Call-REQ-PDU telegram for read/write access to I&M records
Function Record Data Index
I&M0 0xAFF0
I&M1 0xAFF1
I&M2 0xAFF2
I&M3 0xAFF3
I&M4 0xAFF4
￭ Response structure for I&M0 (Read-only)
Contents Size Coding
Header 10 Octets –
I&M block MANUFACTURER_ID 2 Octets 0x1A = ABB Automation
ORDER_ID 20 Octets 6438177508335 = EAN code for

FPNO-21 kit
SERIAL_NUMBER 16 Octets Serial number of FPNO-21 module
HARDWARE_REVISION 2 Octets Hardware version of FPNO-21 module
SOFTWARE_REVISION 4 Octets Format: V255.255.255 E.g., 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_ TYPE 2 Octets 0 = no specific type
IM_VERSION 2 Octets 0x0101 = version 1.1
IM_SUPPORTED 2 Octets 30 = I&M0, I&M1, I&M2, I&M3 and

I&M4 supported
￭ Response structure for I&M1 (Read/Write)
I&M block TAG_FUNCTION 32 Octets Device function or task
TAG_LOCATION 22 Octets Device location
I&M block INSTALLATION_DATE 16 Octets Installation date. E.g., 2011-01-01

16:23
RESERVED 38 Octets Reserved
Note:
I&M1, I&M2 and I&M3 are blank (0x20) by default.
I&M block DESCRIPTOR 54 Octets Description of the device set by the

user

I&M4 is read-only and shows the PROFIsafe configuration CRC.
I&M block SIGNATURE 54 Octets Security code for identifying sessions

and changes
Note:
I&M4 is filled with zeros (0x0) by default.
Appendix B – ABB IP configuration tool 137
14
Appendix B – ABB IP configuration tool

This chapter shows how to use the ABB IP configuration tool to:
• find configured and unconfigured FPNO-21 adapter modules in the network
• rewrite the IP configuration of the adapter modules.
Installation
The ABB IP configuration tool is part of the Control Builder Plus software. No separate
installation is needed.
Finding adapter modules in the network

1. Open the ABB IP configuration tool.
2. Click the Scan button.
The FPNO-21 adapter modules present in the network appear on the results list.
138 Appendix B – ABB IP configuration tool
Rewriting the IP configuration of adapter modules

1. Scan the network for adapter modules.
For instructions, see section Finding adapter modules in the network (page 137).
2. On the results list, click to select the adapter module whose IP configuration you want
to modify.
3. Below New configuration, define the IP configuration settings according to your network
configuration.
4. If you want the adapter module to use a static IP address instead of DHCP, clear the
DHCP check box.
Appendix B – ABB IP configuration tool 139
5. To apply the new settings, click the Send Configuration button.

The new current IP address and configured IP address appear on the results list.
140
Appendix C - FPNO-21 configuration web pages 141
15
Appendix C - FPNO-21 configuration
web pages

This chapter presents the FPNO-21 configuration web pages.
Note:
The web pages are meant only for configuring the device during commissioning. For security
reasons, it is recommended to disable the web pages after commissioning.
Browser requirements
Any web browser can be used.
Compatibility
The web pages work with all drives compatible with the FPNO-21 adapter module. For a
compatibility table, see section Drives (page 11).
Logging in
1. Open a web browser and type the IP address of the adapter module in the address
field. The IP address is visible in group A, parameter 5...8.
Example: http://192.168.0.100/
2. Log in with a user name and a password.

Default user name: admin
Password: The last six digits of the MAC address of the adapter module, in upper case,
without hyphens.
The MAC ID is visible on the cover of the adapter module and in the ABB IP configuration
tool (see Appendix B – ABB IP configuration tool (page 137)).
Example: If the MAC address of the adapter module is 00-1C-01-00-2F-73, the password
is 002F73.
The user interface is loaded.
3. After successful login, you will be prompted to change the password for security reasons.
It is recommended to change the default password.
Menu overview
To navigate on the web pages, use the menu items available:
• Status
• Configuration
• Service configuration
• Support
• Password
￭ Status page
The Status page shows various version information, as well as the serial number and MAC
address (MAC ID) of the adapter module.
￭ Configuration page
On the Configuration page, you can modify parameter settings in the configuration parameter
groups A (1), B (2) and C (3).
After you have changed any setting in any of the groups, you must click Save and reboot
at the bottom of Group A to validate the settings.
Changing the PROFINET IO station name via web page

The PROFINET IO configuration web page is shown below with default values. The
PROFINET IO Station Name field is blank by default.
To set a new name, type the name in the PROFINET IO Station Name field. Click Save
without rebooting, and then click Save and reboot to reboot FPNO-21. See screen in
Configuration page. The new name is effective only after FPNO-21 reboot.
Note:
The value in PROFINET IO Name Index field must be 0 to use the set station name.
Otherwise the name generated by the PROFINET IO Name index overrides it.
Example: PROFINET IO Station Name is set as fpno-21.

After you click Save without rebooting, and then click Save and reboot, the refreshed web
page is as shown below.
The web page validates the Station name format and displays any correction to the new
name, as shown in this example screen.
If PROFINET IO Name Index was set from web page or from parameters, the PROFINET
IO Station Name field shows its generated name after reboot, as shown in this example
screen.
￭ Service configuration page

On the Service configuration page, you can enable or disable certain Ethernet services. All
services except Simple Network Time Protocol (SNTP) are enabled by default. You can
disable the following services on this page:
• access to FPNO-21 configuration web page
• allow to change IP settings remotely via ABB IP configuration tool
• remote access drive with Drive composer tool via Ethernet tool network
• Ping response
• configure SNTP.
• Simple Network Management Protocol (SNMP).
The SNMP can be used to collect and organize information of the managed devices on IP
networks.
The new settings take effect after reboot of the module. You can click Save and reboot, to
validate the new settings immediately or click Save without rebooting if you want to do other
settings also and then reboot.
Note: These settings are available only through web pages. When you select to disable the
web page, a warning appears to confirm before you can save the selection. If you want to
access the disabled web page again, the web page can be accessed only by PROFINET
reset to factory settings command. See Resetting PROFINET IO device to factory default
via S7 (page 48).
Or, you can use the web page password. See Enable web page access after it was
disabled (page 149).
It is recommended to disable all services that are not used after commissioning.
Configuring SNTP
Simple Network Time Protocol (SNTP) can be used to synchronize drive time with a network
time server. When SNTP is enabled, FPNO-21 will request the time from configured server
at a given interval. To receive this time synchronization, you must configure the drive with
parameter 96.20 time sync primary source. The table below shows the settings for SNTP:
Settings Description Value
SNTP update interval Interval to request time from server. Default: 30 seconds
Minimum: 30
seconds
Settings Description Value
SNTP time offset to UTC Time offset to the time received from SNTP. This value -1440...1440 minutes
can also be set over PROFIdrive parameter 1001.
Note:
SNTP time offset change does not need a reboot.
SNTP server address 1 Primary server address for requesting time. -

Format: IP address followed by optional port number,
eg:
192.168.0.1:123
Note:
If port number is missing, the default NTP port number
"123" is used.
SNTP server address 2 Secondary server address used if the request to server -
1 fails.
￭ Support page
On the Support page, you can access documentation related to the adapter module and
the GSDML file. The latest files corresponding to the drive firmware are available through
the hyperlinks listed under WWW documentation and downloads. You can find more
information about each parameter under Click here for more information about fieldbus
parameters.
￭ Password page
On the Password page, you can change password. FPNO-21 supports only one user access
level.
Reset FPNO-21 web page password to default

You can reset the FPNO-21 web page password to factory default.
Note:
The password can be reset only with local access to the drive.
1. Disconnect all cable connections to FPNO-21.

The NET led should switch off.
2. Write 0 (zero) to the parameter 26 under Group A (e.g. 51.26).
3. Refresh the settings by selecting Refresh in parameter 27 (e.g. 51.27).
4. Write 17989 to parameter 26 under Group A.
5. Refresh the settings by selecting Refresh in parameter 27.
FPNO-21 password is now reset to the default password. For information of default password,
see section Logging in (page 141).
Enable web page access after it was disabled

You can enable the access to web pages with drive parameters.
1. Disconnect all cable connections to FPNO-21.
The NET led should switch off.
2. Write 0 (zero) to the parameter 26 under Group A (e.g. 51.26).
3. Refresh the settings by selecting Refresh in parameter 27 (e.g. 51.27).
Access to web pages is now enabled.
150
Appendix D - FPNO-21 configuration back-up 151
16
Appendix D - FPNO-21 configuration
back-up

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

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

Backup includes the following configuration for PROFINET IO in FPNO-21:
Configuration Description
Ethernet service configuration Enables different Ethernet services. See Service configuration page (page 146).
When set, backup will automatically include this configuration.
Web page password Login password for accessing FPNO-21 configuration web pages. See
Password page.
Backup will automatically include the set password.
Note:
Backup will include the default password.
SNTP configuration Enables SNTP, request interval, UTC offset, and server addresses. See
Service configuration page (page 146).
Station name Sets the station name using DCP. See PROFINET network settings (page 90).
I&M 1-3 Writable strings for identification and maintenance. See I&M re-
cords (page 134).
PROFIdrive parameters 934-943 PROFIdrive CW and SW user bit mapping. See PROFIdrive paramet-
ers (page 129).
Note:
Backup will include this configuration only when it is stored with PROFIdrive
parameter 971.
System location Writable SNMP MIB-2 string.

System name
System contact
The settings are saved to the drive after 10 seconds. If a Refresh command is given to
FPNO-21 using parameter 51.27, the pending backup is transferred to drive immediately
and FPNO-21 is rebooted after the transfer is completed.
Note:
The new setting is not saved to drive if the drive was powered off or the adapter was
disconnected from the drive within 10 seconds of changing a setting.
￭ Using the restored backup

The use cases in the below table show how FPNO-21 settings are used after you restored
a backup or after you powered up or enabled the module. The matching status box colours
indicate matching configurations.
Appendix D - FPNO-21 configuration back-up 153
No. Configuration status
Before restore After restore
1 Restoring a backup to drive with Drive composer or panel.
Drive and fieldbus adapter can have any config- Configuration from backup is used in drive and
uration. in FPNO-21
2 Replacing a new fieldbus adapter of the same type.
Drive has a backup of FPNO-21 configuration Drive backup is used in FPNO-21.

and a new FPNO-21 with no configuration is in-
stalled.
3 Replacing a fieldbus adapter with another adapter of the same type. But the new adapter was used
with some other drive previously.
Drive has a backup of FPNO-21 configuration Drive backup is used in FPNO-21.

and a new FPNO-21 with existing configuration
is attached.
4 A new drive and fieldbus adapter are used.
Drive has no backup or a backup of some other FPNO-21 generates a new backup with its default
type of fieldbus adapter other than FPNO-21 ex- settings and copies it to drive.
ists.
FPNO-21 with no configuration is attached.
No. Configuration status
Before restore After restore
5 Replacing drive with a new drive and reusing the old Fieldbus adapter.
Drive has no backup or a backup of some other FPNO-21 copies its backup to drive.
type of fieldbus adapter other than FPNO-21 ex-
ists.
FPNO-21 with an existing configuration is at-
tached.
6 Clearing fieldbus configuration from drive and module to defaults.
You can clear the fieldbus configuration from Clears the fieldbus parameters and backup files
drive and module to defaults with parameter for FBA A and FBA B on the drive side. If a
96.06 Parameter restore using the selection Re- FPNO-21 module is connected, its configurations
set all fieldbus settings. are reset to defaults.
—
Further information
Product and service inquiries
Address any inquiries about the product to your local ABB representative, quoting the type
designation and serial number of the unit in question. A listing of ABB sales, support and service
contacts can be found by navigating to www.abb.com/searchchannels.
Product training
For information on ABB product training, navigate to new.abb.com/service/training.
Providing feedback on ABB manuals

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

You can find manuals and other product documents in PDF format on the Internet at
www.abb.com/drives/documents.
a102 (working)
PDF-Web
Created: 2018-07-13, 13:51:08
www.abb.com/drives
www.abb.com/solarinverters
www.abb.com/windconverters
3AXD50000158614A
3AXD50000158614 Rev A (EN) EFFECTIVE 2018-07-11
© Copyright 2018 ABB. All rights reserved.

Specifications subject to change without notice.

Device PN ABB Drive

Uploaded by

Document Information

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

Device PN ABB Drive

Uploaded by

Copyright:

Available Formats

—

OPTIONS FOR ABB DRIVES, CONVERTERS AND INVERTERS

FPNO-21 PROFINET fieldbus adapter module

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

2 Introduction to the manual

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

Control locations ................................................................................ 36

7 PROFINET IO – Communication profiles

8 PROFINET IO – Communication protocol

The services provided by the FPNO-21 module .............................................. 90

13 Appendix A – PROFIdrive parameters and I&M records of PROFINET IO

14 Appendix B – ABB IP configuration tool

15 Appendix C - FPNO-21 configuration web pages

16 Appendix D - FPNO-21 configuration back-up

Contents of this chapter

Use of warnings and notes

Safety in installation and maintenance

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

Contents of this chapter

• GSDML file version 2.33

Purpose of the manual

Terms and abbreviations

FPNO-21 PROFINET fieldbus adapter module Fieldbus connectivity web page

Contents of this chapter

￭ Example topology of the Ethernet link

Other slave ABB drive Other slave

Daisy chain topology

FPNO-21 module overview

Overview of the Ethernet network and the FPNO-21 module 19

• connect Drive composer pro tool

4 X2 connector for chaining another module

Contents of this chapter

Necessary tools and instructions

Unpacking and examining the delivery

3. Push in the lock.

Contents of this chapter

Necessary tools and instructions

General cabling instructions

Connecting the FPNO-21 to the Ethernet network

• Design guideline, Order no. 8.062

Contents of this chapter

￭ PROFINET IO connection configuration

FPNO-21 configuration parameters – group A (group 1)

No. Name/Value Description Default

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

1 = 100 Mbps FD 100 Mbps, full duplex

2 = 100 Mbps HD 100 Mbps, half duplex

3 = 10 Mbps FD 10 Mbps, full duplex

4 = 10 Mbps HD 10 Mbps, half duplex

No. Name/Value Description Default

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

2 = Temp IP IP address is set as Temporary through DCP by the

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

... ... ...

IP address 4 See parameter 05 IP address 1. 0

No. Name/Value Description Default

CIDR Dotted decimal CIDR Dotted decimal

1...31 Subnet mask in CIDR notation

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

... ... ...