Professional Documents
Culture Documents
Table of contents
1. Safety instructions
4. Mechanical installation
5. Electrical installation
Table of contents
1 Safety instructions
Contents of this chapter ........................................................................... 9
Use of warnings and notes ....................................................................... 9
Safety in installation and maintenance ......................................................... 9
4 Mechanical installation
Contents of this chapter ........................................................................... 21
Necessary tools and instructions ................................................................ 21
Unpacking and examining the delivery ......................................................... 21
Installing the module .............................................................................. 22
5 Electrical installation
Contents of this chapter ........................................................................... 25
Necessary tools and instructions ................................................................ 25
General cabling instructions ...................................................................... 25
Connecting the FPNO-21 to the Ethernet network ............................................ 25
6 PROFINET IO – Start-up
Contents of this chapter ........................................................................... 27
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
9 PROFINET IO – Diagnostics
Contents of this chapter ........................................................................... 113
Fault and warning messages ..................................................................... 113
LEDs ................................................................................................. 113
10 NONE – Start-up
Contents of this chapter ........................................................................... 117
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
Contents of this chapter ........................................................................... 123
Fault and warning messages ..................................................................... 123
LEDs ................................................................................................. 123
12 Technical data
Contents of this chapter ........................................................................... 125
Dimension drawing ................................................................................ 125
General data ........................................................................................ 126
Ethernet link ........................................................................................ 126
TCP and UDP service ports ...................................................................... 126
8 Table of contents
Further information
Safety instructions 9
1
Safety instructions
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.
WARNING!
Obey these instructions. If you ignore them, injury or death, or damage to the
equipment can occur.
2
Introduction to the 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:
12 Introduction to the manual
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.
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.
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
14 Introduction to the manual
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
ACS580-04 manuals 9AKK106930A9060
ACH580-04 manuals 9AKK106930A9059
ACQ580-04 manuals 9AKK106930A9053
ACS580-07 manuals 9AKK106930A5239
ACH580-07 manuals 9AKK106930A5241
ACQ580-07 manuals 9AKK106930A3150
ACS880-01 manuals 9AKK105408A7004
ACS880-04 manuals 9AKK105713A4819
ACS880-07 (45 to 710 kW) manuals 9AKK105408A8149
ACS880-17 (132 to 355 kW) manuals 9AKK106930A3466
ACS880-37 (132 to 355 kW) manuals 9AKK106930A3467
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.
Introduction to the manual 15
3
Overview of the Ethernet network and
the FPNO-21 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.
Star topology
Switch or router
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
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
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
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
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.
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.
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.
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.
03 Commrate Sets the bit rate for the Ethernet interface. 0 = Auto
0 = Auto Auto-negotiate
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...255 IP address
0...255 IP address
30 PROFINET IO – Start-up
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.
0...255 GW address
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
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).
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.
32 PROFINET IO – Start-up
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.
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.
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.
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.
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.
32 FBA A/B comm SW Read-only. Displays patch and build numbers of the N/A
ver adapter module's firmware version in xxyy format,
where:
xx = patch number
yy = build number.
Example: If the firmware version (<ma-
jor>.<minor>.<patch>.<build>) is 3.10.200.13, the value
C80D is displayed. If the version is 3.10.0.0, the value
0 is displayed.
See also parameter 33.
33 FBA A/B appl SW ver Read-only. Displays major and minor revision numbers N/A
of the adapter module's firmware version in xxyy
format, where:
xx = major revision number
yy = minor revision number
Example: If the firmware version (<ma-
jor>.<minor>.<patch>.<build>) is 3.10.200.13 or
3.10.0.0, the value 310 is displayed.
See also parameter 32.
34 PROFINET IO – Start-up
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.
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
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.
PROFINET IO – Start-up 35
Note:
The actual parameter group number depends on the drive type. Group C (group 3)
corresponds to:
• parameter group 52 in ACS380, ACS480, ACH580, ACQ580 and ACS580
• parameter group 52 in ACS880 if the adapter is installed as fieldbus adapter A or group
55 if the adapter is installed as fieldbus adapter B.
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.
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
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.
36 PROFINET IO – Start-up
■ 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.
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.
PROFINET IO – Start-up 37
Out Control word Frequency ref- Constant frequency 11) Constant frequency 21)
erence
1) Example
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.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.
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.
Out Control word Speed refer- Constant speed 11) Constant speed 21)
ence
1) Example
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.
PROFINET IO – Start-up 39
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.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.
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.
The examples apply to all drive types compatible with the module.
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.
PROFINET IO – Start-up 41
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.
• 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).
PROFINET IO – Start-up 43
• 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.
4. Click and drag the FPNO-21 object from the device catalog to the Ethernet (1):
PROFINET-IO-System.
PROFINET IO – Start-up 45
6. On the General tab, type a name for the adapter module in the Device name box.
46 PROFINET IO – Start-up
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).
PROFINET IO – Start-up 47
• 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.
48 PROFINET IO – Start-up
The configuration is now reset to default (PROFINET IO station name, Ethernet services
configuration).
8. Select Properties tab > General tab > Ethernet addresses submenu, and set the PLC
IP address.
12. Add ABB_Drive to OB1. Assign new instance Data Block for ABB_Drive FB.
PROFINET IO – Start-up 57
14. Add blocks DPRD_DAT and DPWR_DAT to ABB_Drive FB. Map inputs and outputs.
16. In device configuration, right-click FPNO-21 icon and select Assign device name.
PROFINET IO – Start-up 59
18. If values want to be forced, add FPNO-21 addresses to tag table, and add the tag table
variables to the force table.
60 PROFINET IO – Start-up
1 2
...
4
No. Description
1 ABB drive
2 ABB drive
3 FPNO-21 module
5 Port 1
6 Port 2
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.
64 PROFINET IO – Start-up
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.
66 PROFINET IO – Start-up
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.
PROFINET IO – Start-up 67
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.
PROFINET IO – Start-up 69
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.
70 PROFINET IO – Start-up
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.
7
PROFINET IO – Communication profiles
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:
46 PROFINET IO – Communication profiles
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.
PROFINET IO – Communication profiles 77
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.
Note:
This bit is effective only if the fieldbus interface is set as the
source for this signal by drive parameters.
0 OFF1 ACTIVE
0 OPERATION INHIBIT
3 TRIPPED 1 FAULT
0 No fault
PROFINET IO – Communication profiles 79
0 OFF2 ACTIVE
0 OFF3 ACTIVE
7 ALARM 1 Warning/Alarm
0 No Warning/Alarm
As default mapped to
PROFIdrive SW bit 11.
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)
(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)
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
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.
82 PROFINET IO – Communication profiles
■ 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.
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.
Note:
This bit is effective only if the fieldbus interface is set as the source
for this signal by drive parameters.
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.
8 … 9 Reserved
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 OFF1 ACTIVE
0 OPERATION INHIBITED
3 TRIPPED 1 FAULT
0 No fault
0 OFF2 ACTIVE
0 OFF3 ACTIVE
0 –
7 ALARM 1 Warning/Alarm
0 No warning/alarm
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)
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)
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
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)
■ 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
0 0
Scaling_actual_values.pdf
88
PROFINET IO – Communication protocol 89
8
PROFINET IO – Communication
protocol
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.
90 PROFINET IO – Communication protocol
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 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
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
PPO_types.pdf
92 PROFINET IO – Communication protocol
PZD1 PZD2
ST2
Note:
For the contents of the Control word, the Status word, references and actual values, see
chapter PROFINET IO – Communication profiles
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.
ErrorDecode 0x80 (PNIORW) ErrorCode1 decoded as shown in section ErrorCode1 (page 93). Error-
Code2 is 0.
ErrorCode1 Error class and error code. See section ErrorCode1 (page 93).
PROFINET IO – Communication protocol 73
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
■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.
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
PROFINET IO – Communication protocol 95
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)).
Padding 2 bytes
Data block Used only with write request and read response.
96 PROFINET IO – Communication protocol
Data block
The data block contains a PROFIdrive-specific request or response header.
The table below shows the contents of the PROFIdrive request.
Request ID Request type for the issued block Request Parameter (01h) Byte
Change Parameter (02h)
Attribute Type of the object being accessed. Value (10h) Description Byte
Note: “Description” and “Text” are not (20h) Text (30h)
supported.
1)Only if Request ID is 02h (Change Parameter). The Format, Number of Values and Values fields are repeated for other
parameters.
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)
PROFINET IO – Communication protocol 97
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.
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)
0x40 Zero
0x41 Byte
0x42 Word
0x44 Error
0x45…0xFF (Reserved)
The table below shows the PROFIdrive parameter request error codes.
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
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
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
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.
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
PROFINET IO – Communication protocol 99
ErrorFunction
# Meaning blocks for sending
Used at DP-V1 messages
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.
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
Number of parameters
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
• PROFINET
Negative response to PROFIdrive IO –request:
Read Communication protocol 101
Slot number
Subslot number
Index
Data length
Response reference (mirrored)
Response ID
Drive object ID (mirrored)
Number of parameters
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
Request ID (01h= Request Parameter
Drive object ID
Number of parameters
Attribute (10h = Value)
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 reference (mirrored)
Response ID
Drive object ID
Number of parameters
Format (42h = Word)
Number of values
Parameter value
01 01 B0 2F 10 06 01 01 03 42 01 01 90
DP
PROFIdrive V3 Parameter •••
header DP-V1 Response
Channel
42 01 01 F4
••• (Par. Channel •••
cont’d)
42 01 00 30
DP
••• (Par. Channel trailer
cont’d)
The values 190h (400), 1F4h (500) and 1Eh (30) are returned.
The values 190h (400), 1F4h (500) and 1Eh (30) are returned.
Slot number
Subslot number
Index
Data length
Request reference
Request ID
Drive object ID
Number of parameters
Attribute (10h = Value)
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
Drive object ID (mirrored)
Number of parameters
01 01 B0 2F 04 07 02 01 01
DP DP
header PROFIdrive V3 trailer
DP-V1 Response
Parameter Channel
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)
104 PROFINET IO – Communication protocol
respectively using one telegram.
Slot number
Subslot number
Index
Data length
Request reference
Request ID (02h= Change Parameter)
Drive object ID
Number of parameters
Attribute (10h = Value)
Number of elements
Parameter number
Subindex
01 01 B0 2F 14 08 02 01 02 10 01 00 0C 00 02
DP
PROFIdrive V3 Parameter •••
header DP-V1 Command
Channel
••• 10 01 00 14 00 08
•••
(Par. Channel cont’d)
42 01 01 2C
••• •••
(Par. Channel
cont’d)
42 01 01 F4
DP
••• (Par. Channel trailer
cont’d)
Value
Number of values
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
corresponds to the Parameter index (PNU), and the drive
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
Request ID (01h= Request Parameter
Drive object ID
Number of parameters
Attribute (10h = Value)
Number of elements
Parameter index
Subindex
DP 01 01 B0 2F 0A 05 01 01 01 10 01 00 0C 00 04
DP trailer
header DP-V1 Command PROFIdrive V3 Parameter Channel
• DP-V1
106 PROFINET IO – Read response:
Communication protocol DP-V1_Read_response_3.pdf
Slot number
Subslot number
Index
Data length
Request reference (mirrored)
Response ID
Drive object ID (mirrored)
Number of parameters
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
header DP-V1 Response PROFIdrive V3 Parameter Channel trailer
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 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)
DP-V1_Write_request_2.pdf
86 PROFINET IO – Communication protocol
108 PROFINET
• IO – Communication
Positive protocol
Read response to DP-V1 Read request:
Slot number
Subslot number
Index
Data length
Response reference (mirrored)
Response ID
Drive object ID
Number of parameters
Format (42h = Word)
Number of values
Parameter value
01 01 B0 2F 10 06 01 01 03 42 01 01 90
DP
PROFIdrive V3 Parameter •••
header DP-V1 Response
Channel
42 01 01 F4
••• (Par. Channel •••
cont’d)
42 01 00 30
DP
••• (Par. Channel trailer
cont’d)
The values 190h (400), 1F4h (500) and 1Eh (30) are returned.
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.
PROFINET IO – Communication protocol 109
• DP-V1 Write request:
Slot number
Subslot number
Index
Data length
Request reference
Request ID (01h = Read)
Drive object ID
Number of parameters
Attribute (10h = Value)
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
Slot number
DP-V1_Write_request_3.pdf
Subslot number
Index
Data length
Request reference (mirrored)
Response ID
Drive object ID (mirrored)
Number of parameters
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
header DP-V1 Response PROFIdrive V3 Parameter Channel trailer
• 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.
0x900C Infeed
0x9011 Engineering
0x4210 0x9005 0
0 0 1
0 0 2
0 0 3
0 0 4
0 0 5
0 0 7
112 PROFINET IO – Communication protocol
0x7510 0x900B 8
0 0 9
0 0 10
0 0 11
0 0 12
0 0 13
0 0 15
… … … …
0 0 56
0 0 57
0 0 58
0 0 59
0 0 60
0 0 61
0 0 63
PROFINET IO – Diagnostics 113
9
PROFINET IO – Diagnostics
LEDs
The adapter module is equipped with three bicolor diagnostic LEDs. The LEDs are described
below.
114 PROFINET IO – Diagnostics
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
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 orange, al- Internal file system error. The error may be cleared by cycling
ternating with the drive power. If the error persists, contact your local ABB repres-
HOST flashing or- entative.
ange
PROFINET IO – Diagnostics 115
of the module
NETWORK/NET
Flashing green Device is receiving/transmitting on the Ethernet.
116
NONE – Start-up 117
10
NONE – Start-up
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.
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.
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.
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).
03 Commrate Sets the bit rate for the Ethernet interface. 0 = Auto
0 = Auto Autonegotiate
1 = 100 Mbps FD
2 = 100 Mbps HD
3 = 10 Mbps FD
4 = 10 Mbps HD
04 IP configuration Sets the method for configuring the IP address, subnet 1 = Dyn IP DHCP
mask and gateway address for the module.
0...255 IP address
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.
0...255 GW address
0.255 GW address
14 Commrate port 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 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.
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.
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.
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.
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
32 FBA A/B comm SW Read-only. Displays patch and build numbers of the N/A
ver adapter module's firmware version in xxyy format,
where:
xx = patch number
yy = build number.
Example: If the firmware version (<ma-
jor>.<minor>.<patch>.<build>) is 3.10.200.13, the value
C80D is displayed. If the version is 3.10.0.0, the value
0 is displayed.
See also parameter 33.
33 FBA A/B appl SW ver Read-only. Displays major and minor revision numbers N/A
of the adapter module's firmware version in xxyy
format, where:
xx = major revision number
yy = minor revision number
Example: If the firmware version (<ma-
jor>.<minor>.<patch>.<build>) is 3.10.200.13 or
3.10.0.0, the value 310 is displayed.
See also parameter 32.
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
LEDs
The adapter module is equipped with three bicolor diagnostic LEDs. The LEDs are described
below.
124 NONE - Diagnostics
the module
HOST Flashing orange, al- Internal file system error. The error may be cleared by cycling
ternating with the drive power. If the error persists, contact your local ABB repres-
MODULE flashing entative.
orange
Flashing orange, al- Internal file system error. The error may be cleared by cycling
ternating with the drive power. If the error persists, contact your local ABB repres-
HOST flashing or- entative.
ange
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.
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)
General data
Installation Into an option slot on the drive control unit
Ambient conditions The applicable ambient conditions specified for the drive in its manuals
are in effect.
Ethernet link
Compatible devices Ethernet Standard IEEE 802.3 and IEEE 802.3u devices
Protocol PROFINET IO
Note:
Used only when PROFINET IO protocol is selected.
Technical data 127
Note:
Used only when PROFINET IO protocol is selected.
Note:
Used only when PROFINET IO protocol is selected.
Note:
Used only when IP configuration method is selected as "Dyn IP
HFCP".
Note:
Used only when PROFINET IO protocol is selected.
13
Appendix A – PROFIdrive parameters
and I&M records of PROFINET IO
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
130 Appendix A – PROFIdrive parameters and I&M records of PROFINET IO
Value Mode
0 Parameters cannot be written, only read (927
can be written).
1 Parameters can be written and read (default).
Value Mode
0 PZD part is disabled, i.e., Receipt of new PZD
data is ignored.
1 PZD part is enabled (default).
Appendix A – PROFIdrive parameters and I&M records of PROFINET IO 131
Note:
This parameter is not available if Standard telegram ST1 or
ST2 is selected.
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.
934 R/W Unsigned16 Selection switch for Control word, bit 12. (See parameter 933
for coding.)
935 R/W Unsigned16 Selection switch for Control word, bit 13. (See parameter 933
for coding.)
936 R/W Unsigned16 Selection switch for Control word, bit 14. (See parameter 933
for coding.)
937 R/W Unsigned16 Selection switch for Control word, bit 15. (See parameter 933
for coding.)
939 R/W Unsigned16 Selection switch for Status word, bit 11.
940 R/W Unsigned16 Selection switch for Status word, bit 12. (See parameter 939
for coding.)
941 R/W Unsigned16 Selection switch for Status word, bit 13. (See parameter 939
for coding.)
132 Appendix A – PROFIdrive parameters and I&M records of PROFINET IO
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.
Value Description
0 No action
1 Restore factory settings
Value Description
0 No action
1 Save the drive parameters to non-volatile
memory
Value Description
0 No action
1 Re-boot PROFIBUS module
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.
Value Description
-1440, 1440 Time in minutes to offset the UTC time re-
ceived from SNTP
134 Appendix A – PROFIdrive parameters and I&M records of PROFINET IO
Value Description
0 PNIO alarms enabled
1 PNIO alarms disabled
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.
I&M0 0xAFF0
I&M1 0xAFF1
I&M2 0xAFF2
I&M3 0xAFF3
I&M4 0xAFF4
Header 10 Octets –
Appendix A – PROFIdrive parameters and I&M records of PROFINET IO 135
Header 10 Octets –
Header 10 Octets –
Note:
I&M1, I&M2 and I&M3 are blank (0x20) by default.
Header 10 Octets –
Header 10 Octets –
Note:
I&M4 is filled with zeros (0x0) by default.
Appendix B – ABB IP configuration tool 137
14
Appendix B – ABB IP configuration tool
Installation
The ABB IP configuration tool is part of the Control Builder Plus software. No separate
installation is needed.
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
15
Appendix C - FPNO-21 configuration
web pages
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/
142 Appendix C - FPNO-21 configuration web pages
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).
144 Appendix C - FPNO-21 configuration web pages
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.
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.
The web page validates the Station name format and displays any correction to the new
name, as shown in this example screen.
146 Appendix C - FPNO-21 configuration web pages
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.
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:
SNTP update interval Interval to request time from server. Default: 30 seconds
Minimum: 30
seconds
148 Appendix C - FPNO-21 configuration web pages
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.
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.
Appendix C - FPNO-21 configuration web pages 149
16
Appendix D - FPNO-21 configuration
back-up
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.
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).
When set, backup will automatically include this configuration.
Station name Sets the station name using DCP. See PROFINET network settings (page 90).
When set, backup will automatically include this configuration.
I&M 1-3 Writable strings for identification and maintenance. See I&M re-
cords (page 134).
When set, backup will automatically include this configuration.
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 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.
Drive and fieldbus adapter can have any config- Configuration from backup is used in drive and
uration. in FPNO-21
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 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.
154 Appendix D - FPNO-21 configuration back-up
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.
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.
a102 (working)
PDF-Web
Created: 2018-07-13, 13:51:08
www.abb.com/drives
www.abb.com/solarinverters
www.abb.com/windconverters
3AXD50000158614A