EXPERION PKS RELEASE 516
PROFINET User Guide
EPDOC-X567-en-516A
August 2020 Disclaimer
This document contains Honeywell proprietary information. Information contained herein is to be used solely for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or disclosed to a third party without the express permission of Honeywell International Sàrl. While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The information and specifications in this document are subject to change without notice.
Copyright 2020 - Honeywell International Sàrl
- 2 - Contents 3 Chapter 1 - About This Document 5 1.1 Scope & Purpose 5 1.2 Revision History 5 1.3 Related documents 5 1.4 Terms and definitions 6 Chapter 2 - Introduction to PROFINET 8 2.1 Overview about PROFINET 8 2.2 Advantages of PROFINET 8
2.2.1 Comparison between PROFINET and PROFIBUS 9 2.3 PROFINET components 9 2.4 PROFINET protocols 10
2.4.1 PROFINET RT classes 11 2.5 PROFINET device model 11 2.6 PROFINET alarms 11 2.7 Integration with field-bus devices 16 Chapter 3 - Planning and designing a PROFINET network 18 3.1 PROFINET network topologies 18 3.2 PROFINET network components 20
3.2.1 Cables 21
3.2.2 Connectors 22 3.2.3 Switches 24 3.2.4 PROFINET stripping tool 24 3.3 PROFINET security 25 Chapter 4 - Experion PROFINET Solution Overview 26 4.1 Profinet User Defined Submodule block 27 4.2 PROFINET IO Data in Control Application 27 Chapter 5 - PROFINET License 28 Chapter 6 - Installation 29 Chapter 7 - Configuration 30 7.1 Enable PROFINET in UOC Platform Block 30 7.2 Configure PROFINET 30
- 3 - 7.3 Configure PROFINET Custom Sub Module 38
7.3.1 Creating PROFINET Custom Input SubModule type 38 Chapter 8 - PROFINET Supportability 44 Chapter 9 - PROFINET IO Behavior during UOC switchover 48 Chapter 10 - Simulate Control Strategy 49 10.1 For UDS Blocks 49 10.2 For IO Blocks 49 Chapter 11 - Troubleshooting Scenarios 50 11.1 Checking Control Builder error code reference 50
11.1.1 Using Firmware Manager to capture diagnostic data 50 11.1.2 Viewing release information log 50 11.1.3 Checking server point build log 50 11.1.4 Checking error log 50 11.2 Parameter Reference Dictionary Configuration failure 51 11.3 Inaccurate Device name 51 11.4 Incorrect Network Structure 51 11.5 Alarms 51
- 4 - CHAPTER 1 ABOUT THIS DOCUMENT
The Experion PKS PROFINET User Guide provides information about the PROFINET protocol implementation in UOC and its extent and capacity, assembly and maintenance, field network definition, and so on.
l Revision History
l Related documents
l Terms and definitions
1.1 Scope & Purpose
This document provides information about PROFINET configuration and integration in UOC controller. The UOC architecture depicts the integration of PROFINET in UOC for Experion system.
1.2 RevisionHistory
Revision Date Description
A August 2020 Initial release of the PROFINET User Guide.
1.3 Related documents
The following list identifies publications that may contain information relevant to the information in this document. You can find these documents on https://www.honeywellprocess.com/en- US/support/pages/all-documentation.aspx.
- 5 - Chapter 1 - About This Document
Document Description
UOC_User_ This guide provides an overview of the UOC, the pairing of Guide_EPDOC- vUOC and its integration with the Experion DCS systems. It X512-en- describes about the networking, installing, configuring and 511.pdf loading the configuration of UOC using the Control Builder. It also provides an insight of CEE in UOC and vUOC along with the troubleshooting information.
Network_and_ This document contains networking and security-related Security_ information applicable to Experion. It provides information PlanningGuide_ about the recommendations to assist you in planning, EPDOC-XX75- setting up, and maintaining a secure environment for your en-511.pdf system.
1.4 Terms and definitions
Term Definition PROFINET PROFINET IO as the Ethernet-based automation standard of IO PROFIBUS International defines a cross-vendor communication, automation, and engineering model. PROFINET IO is based on Switched Ethernet full-duplex operation and a bandwidth of 100 Mbps.
IO An IO Controller is a programmable controller, in which controller automation routine is executed. A PROFINET configuration contains at least one IO controller. The IO controller function corresponds to those of a Profibus class-1 master.
IO device An IO device is a distributed field device which exchanges data with one or more IO controllers using PROFINET IO mechanisms. A PROFINET IO configuration contains at least one IO-device. The IO device functions correspond to those of a Profibus slave. IO Engineering device which manages commissioning and/or supervisor diagnosing of an IO system IO supervisor functions corresponds to those of a class 2 master.
Slot Address of a structural unit within an IO device. Within a modular device, slot typically addresses a physical module. Within compact devices, a slot typically addresses a logical function or virtual module
Subslot Address of structural unit within a slot. A subslot may address a physical interface for submodules within a module. Generally, a subslot is a second level to structure data within a device
Module Hardware or logical component of a physical device
- 6 - Chapter 1 - About This Document
Term Definition
Submodule Hardware of logical component of a module
IOPS Input Output Provider Status
IOCS Input Output Consumer Status
MRP Media Redundancy Protocol (MRP) is data network protocol standardized as IEC62439-2 by IEC. It the protocol used by PROFINET devices to support Ethernet network redundancy. All devices supporting MRP needs to have inbuilt managed Ethernet switch with minimum two Ethernet interfaces.
AR Application Relationship is a cooperative association between PROFINET IO controller and PROFINET IO device. This association is initiated and activated by PROFINET IO controller by explicit connection establishment procedure as per PROFINET specification.
Backup AR Backup AR is hot standby AR. This is supported by devices supporting S2 type of redundancy.
DCP Discovery and basic Configuration protocol used for basic configuration like IP address, station names to PROFINET IO devices on network.
GSD Generic Station Description that describes the device features
GSDML GSD in markup language. XML based representation of PROFINET IO devices GSD.
IRT Isochronous Real Time protocol used in Profinet for low jitter communications (typically in motion control applications)
LLDP Link Layer Discovery Protocol (IEEE 802.1AB), used in PROFINET for network topology configuration and discovery.
NRT Non-Real-Time Protocol used in PROFINET for non-real time needs like configuration and diagnostics.
RT Real Time protocol used in PROFINET for process data exchange and alarm reporting.
SNMP Simple Network Management Protocol (IETF RFC 1157) used in PROFINET for network management.
- 7 - CHAPTER 2 INTRODUCTION TO PROFINET
l Overview about PROFINET
l Advantages of PROFINET
l PROFINET components
l PROFINET protocols
l PROFINET device model
l PROFINET alarms
l Integration with field-buse devices
2.1 Overview about PROFINET
PROFINET is an Ethernet open standard (IEC 61158) defined by PI (PROFIBUS and PROFINET International) and complies with the industrial Ethernet requirements. PROFINET IO is Ethernet based automation standard. PROFINET uses TCP/IP for diagnostics, non-real time critical data and for communicating with other non PROFINET IO based devices. PROFINET uses real-time protocol for IO data access. This real-time protocol co-exists with TCP/IP stack without restrictions. PROFINET has two variants:
l PROFINET IO: used to integrate simple distributed I/O and time-critical applications to communicate over Ethernet.
l PROFINET Component Based Automation (CBA): used to integrate a distributed automation system to communicate over Ethernet.
2.2 Advantages of PROFINET
The following are the advantages of PROFINET:
l Applies the Ethernet standard to automation, therefore it is easy to implement.
l Allows a smooth and easy integration of other legacy fieldbus devices.
l Enables simple distributed I/O and time-critical applications to be integrated into Ethernet communication.
l Enables high-speed (millisecond) and secure data exchange at all levels, and enables implementation of innovative machine and plant concepts.
l Offers maximum freedom to users in structuring machine and plant architectures using Fiber optic and wired/wireless networks.
l Enables optimal use of available user resources, and a significant increase in plant availability.
- 8 - Chapter 2 - Introduction to PROFINET
2.2.1 Comparison between PROFINET and PROFIBUS
The following table provides a comparison of PROFINET and PROFIBUS.
Features PROFIBUS DP PROFINET Node Types Master Class-1 IO Controller
Master Class-2 IO Supervisor
Slave IO Device
Wired PROFIBUS over copper or Industrial Ethernet over copper Transmission fiber optic cable (RS- 485) or fiber optic cable Technology
Wireless Infrared Transmission Industrial Wireless Local Area Transmission Network (WLAN) IEEE 802.11, 15.1 Technology
Data Exchange Request /Response Provider /Consumer Method
Data Channels One exactly defined channel Multiple data channels between between Master and Slave Controller/Supervisor Devices
Address Space 126 As per IP class
Device Description ASCII Format XML Based Schema Definition
Data Priority Same priority Different Priorities can be set
Address Assignment PROFIBUS address over a DIP Assignment of IP addresses to IO Switch or Engineering Tool Controller with Engineering tool
Assignment of IP addresses to IO devices with IO Controller
Assignment of device name to IO device with Engineering tool
Assignment of IP addresses through web page integrated with switches
Maximum Data 12 Mbps 100 Mbps Full Duplex Transfer Rate Topology Standard: Line Standard: Star and Tree Optional: Tree and Ring Optional: Line and Ring
Maximum Data Size 244 bytes 1440 bytes
2.3 PROFINET components
PROFINET IO is used for data exchange between I/O controllers (PLC) and I/O devices (field devices). It provides a greater bandwidth, and allows more stations on the network.
- 9 - Chapter 2 - Introduction to PROFINET
The PROFINET IO specifications define a protocol and an application interface for exchanging I/O data, alarms and diagnostics, and for transmitting data records and log information. To exchange I/O data and alarms, PROFINET IO is based directly on the Ethernet protocol. A PROFINET IO system consists of the following:
l IO controller: controls the automation task.
l IO device: field device that is monitored and controlled by an IO controller. An IO device may consist of several modules and sub-modules.
l IO supervisor: software typically installed on a PC for setting parameters and diagnosing individual IO devices.
Figure 2.1 UOC Network Connectivity (Uplink FTE Network)
An Application Relation (AR) is established between an IO controller and an IO device. These ARs are used for defining Communication Relations (CR) with different characteristics for the transfer of parameters, cyclic exchange of data, and handling of alarms. The characteristics of an IO device are described by the device manufacturer in a General Station Description (GSD) file, which is the device communication database file for PROFINET IO devices. The language used for this purpose is the GSD Markup Language (GSDML). The GSDML isa XML-based language to describe the characteristics of PROFINET IO devices. For example, communication and module parameters.
2.4 PROFINET protocols
The following are the PROFINET protocol variants.
l PROFINET Real Time (RT)
l PROFINET Non-Real Time (NRT)
l PROFINET Isochronous-Real Time (IRT)
The following are the PROFINET protocols used.
- 10 - Chapter 2 - Introduction to PROFINET
l Real Time Acyclic (RTA) for configuration and alarms
l Real Time Cyclic (RTC ) for data communication
l Discovery and Configuration Protocol (DCP ) for device name assignment
l Link Layer Discovery Protocol (LLDP) for topology identification
l Simple Network Management Protocol (SNMP) for network diagnostics
l Media Redundancy Protocol (MRP ) for media redundancy
l Precision Transparent Clock Protocol (PTCP) for time synchronization
2.4.1 PROFINETRTclasses
The following are the PROFINET RT classes used.
l RT Class-1: Standard communication, used for cyclic/acyclic data, no special switches are required.
l RT Class-2: Real-time communication, used for cyclic data, special switches are required.
l RT Class-3 (IRT): Isochronous real-time communication, used for cyclic data in motion control applications. Requires special switches and explicit communication planning.
2.5 PROFINET device model
PROFINET IO describes a device model, which consists of slots (where modules can be inserted) and sub-slots (groups of IO channels). IO data are always assigned to sub-slots (real IO channels). Each sub-slot can contain IO data or alarms. IO data are transferred with status information at the sub-slot level. Only one controller is allowed to write to a sub-slot.
Figure 2.2 PROFINET device model
2.6 PROFINET alarms
The process events are signalled within a PROFINET IO configuration with Alarms. An IO device transmits alarms with priority as real-time messages. These alarms must be acknowledged by an IO controller. The alarms are of two types:
- 11 - Chapter 2 - Introduction to PROFINET
l Process Alarms: These are alarms associated with points - for example, alarms are reported when the measurement value may be above or below the acceptable range. They are known as process alarms as they are associated with the process being monitored and are displayed on the Alarm Summary display.
l System Alarms: These are alarms generated when any important event occurs, such as a communication failure. They are known as system alarms as they are associated with components that form the system and are displayed on the System Status display.
In addition to alarms, events are generated to communicate any significant process changes. These changes are useful to know. However, they do not need any corrective action.
Station Alarm Description filed
Following table lists the Channel Error alarm descriptions in station:
Channel Error alarm descriptions to show in Note station Channel Error Type: Short circuit 1. These are various Channel Error alarms that can be shown in station. Channel Error Type: 2. Appears and disappears of the channel properties field Undervoltage in the Alarm notification data from the Profinet device can be used for Alarm/RTN Channel Error Type: Overvoltage
Channel Error Type: Overload
Channel Error Type: Overtemperature
Channel Error Type: Line break
Channel Error Type: Upper limit value exceeded
Channel Error Type: Lower limit value exceeded
Channel Error Type: Error
Channel Error Type: Simulation active
Channel Error Type: Parameter missing
Channel Error Type: Parameterization fault
Channel Error Type: Power
- 12 - Chapter 2 - Introduction to PROFINET
Channel Error alarm descriptions to show in Note station supply fault
- 13 - Chapter 2 - Introduction to PROFINET
Channel Error alarm descriptions to show in Note station Channel Error Type: Fuse blown / open
Channel Error Type: Communication fault
Channel Error Type: Ground fault
Channel Error Type: Reference point lost
Channel Error Type: Process event lost / sampling
Channel Error Type: Error
Channel Error Type: Threshold warning
Channel Error Type: Output disabled
Channel Error Type: FunctionalSafety event
Channel Error Type: External fault
Channel Error Type: Temporary fault
Channel Error Type: Functional Safety
Channel Error Type: Manufacturer specific
Channel Error Type: Data transmission impossible
Channel Error Type: Remote mismatch
Channel Error Type: Media redundancy mismatch
Channel Error Type: Sync mismatch
- 14 - Chapter 2 - Introduction to PROFINET
Channel Error alarm descriptions to show in Note station Channel Error Type: IsochronousMode mismatch
Channel Error Type: Multicast CR mismatch
Channel Error Type: Reserved
Channel Error Type: Fiber optic mismatch
Channel Error Type: Network component function mismatch
Channel Error Type: Time mismatch
Channel Error Type: Dynamic frame packing function
Channel Error Type: Mismatch
Channel Error Type: Media redundancy with planned
Channel Error Type: Duplication mismatch
Channel Error Type: Reserved
Channel Error Type: Multiple interface mismatch
Channel Error Type: Nested diagnosis indication
Following table lists the Profinet Module and Sub-Module alarms descriptions:
Profinet Module, Sub-Module alarms Note descriptions Module: Pull/Plug Pull/Plug form Alarm/RTN Module: Logical Pull/Plug pair
SubModule: Pull/Plug
- 15 - Chapter 2 - Introduction to PROFINET
Following table lists the Profinet Module and Sub-Module Events descriptions:
Profinet Module, Sub-Module Note Event descriptions Plug Wrong SubModule These will be logged as a event as they don’t Return of Submodule have Corresponding RTN state
SubModule: Status
SubModule: Update
SubModule: Controlled by supervisor
Following table lists the PROFINET Notification Description in station:
Profinet Notification Descriptiosn to show in Note station Notfication: Media Redundancy These are posted as Events in station as these Notification: Multicast don't have proper directions defined communication Mismatch
Notfication: Port data change
Notfication: Sync data change
Notfication: Isochronous mode problem
Notfication: Network component problem
Notfication: Time data change
Notfication: Dynamic Frame Packing problem
Notfication: MRPD problem
Notfication: Multiple interface mismatch
Notification: Upload and retrieval
In Addition to these alarms and events following events can be logged when a Channel error alarms are reported with additional data to indicate operator to fetch these data manually.
l Extended Channel Diagnosis exists
l Qualified Channel Error type exists
2.7 Integration with field-bus devices
PROFINET offers a simple and seamless transition strategy for interfacing existing PROFIBUS systems to PROFINET. For this purpose, PROFINET supports a proxy concept that enables integration of any installed field device with PROFINET without modifications.
- 16 - Chapter 2 - Introduction to PROFINET
A proxy largely consists of two main components, an Ethernet-based unit and a fieldbus unit, for example, a PROFIBUS DP Master. This guarantees that all I/O and diagnostics data can be exchanged with the configured slaves. The result is then placed by the DP master in a common memory. With PROFINET CBA, for example, the PROFINET unit of the proxy accesses this memory and transmits the data present there to the respective consumers with the configured links. If the consumer is present in the PROFIBUS unit, the PROFIBUS DP master transmits the arriving link data to the respective DP slave in the next PROFIBUS cycle.
- 17 - CHAPTER 3 PLANNING AND DESIGNING A PROFINET NETWORK
l PROFINET network topologies
l PROFINET network components
l PROFINET security
3.1 PROFINET network topologies
Network topologies must be oriented according to the requirements of the equipment to be networked. The supported topologies are: • Line (Linear) • Star • Ring • Media Redundancy Protocol (MRP)
Figure 3.1 PROFINET topologies
NOTE The ETAP shown below is a device that help in connecting PROFINET IO devices to DLR ring. It is preferred to use Ethernet switch like Stratix S5700 to connect PROFINET IO devices to DLR Ring. ETAP devices acts as a hub and can cause extra uni-cast message forwarding on PROFINET IO network. By default, the LLC messages are displayed during the PROFINET configuration.
PROFINET supports the following network topologies for R511:
- 18 - Chapter 3 - Planning and designing a PROFINET network
l Combination of Line and Star topology:
Figure 3.2 Combination of Line and Star topology
- 19 - Chapter 3 - Planning and designing a PROFINET network
l Combination of Line and Star topology:
Figure 3.3 Combination of Line and Star topology
3.2 PROFINET network components
A PROFINET network largely consists of active and passive network components. These are hardware components of a network.
- 20 - Chapter 3 - Planning and designing a PROFINET network
l Passive components are the components associated with the connection system. They pass on signals without actively influencing them. Passive components include cables, connectors, sockets, and cabinets.
l Active components are components that actively influence the signal. Active components include hubs, repeaters, bridges, switches, and routers.
3.2.1 Cables
The PROFINET transmission technology fundamentally corresponds to the Fast Ethernet standard with a full duplex data transfer of 100 Mbps in a switched network. Transmission technologies with lower data transfer rates (10 Mbps) do not satisfy the demands for transmission performance in automation systems. The following cable is suitable for transmission of electrical signals in PROFINET.
l 100Base-TX: electrical transmission system at 100 Mbps (Fast Ethernet) with two pairs of conductors.
100Base-TX Twisted copper cables (100Base-TX) are used for electrical signal transmission at a rate of 100 Mb/s (Fast Ethernet) in full duplex mode. The transmission procedure for 100Base-TX is defined in the IEEE 802.3i/IEEE 802.3u standards of the Institute of Electrical and Electronics Engineers. The transmission medium is a symmetrical and shielded twisted-pair or star-quad copper cable with a characteristic impedance of 100 Ω. The conductors are color-coded: conductor pair 1 is yellow/orange, and is used for sending. The white/blue conductor pair is used as the receive line. Twisted-pair connections are always point-to-point connections between a transmitter block and a receiver block.
Figure 3.4 100Base-TX cable
- 21 - Chapter 3 - Planning and designing a PROFINET network
Property Value
Standard IEC 61158
Cable sort 2-pair, symmetrical and shielded copper cable
Cable type 100Base-Tx, CAT 5
Characteristic impedance 100
Transmission rate 100 Mbps
Maximum segment length 100 m
Maximum number of section 3
Connections RJ45 plug connector, M12 plug
Maximum number of 6 pairs of plugs/sockets per connection connections
3.2.2 Connectors
The PROFINET cable can be directly connected to all connectors. The connectors used for PROFINET are shielded and designed for use in harsh industrial environments. PROFINET supports only two connector types:
l RJ45
l M12
RJ45 The RJ45 connector type is a rugged metal enclosure immune to interference. It is available in two degrees of protection, as an IP20 solution for use in control cabinets and an IP65/67 solution for system designs without control cabinets. It protects data communication from interference.
- 22 - Chapter 3 - Planning and designing a PROFINET network
Figure 3.5 RJ45 connector
M12 The 4-pin M12 connector with D coding is used with IP65/67. The M12 connector for data transfer is standardized in IEC 61076-2-101. The advantages of M12 connector is the round design, which enables simple sealing to comply with the IP67 degree of protection.
Figure 3.6 M12 connector
- 23 - Chapter 3 - Planning and designing a PROFINET network
Contact assignment Contact assignment Signal Conductor Function in the RJ45 in the M12 color connector connector
TD + Transmission Yellow 1 1 data +
TD - Transmission Orange 2 3 data -
RD + Receiver data White 3 2 +
RD- Receiver data Blue 6 4 -
3.2.3 Switches
A network switch is a device that physically connects devices together in a network. Multiple cables can be connected to a switch to enable networked devices to communicate with each other and ensure easy installation. Transmission cables are assembled with the same connectors and in the same assignment at both ends. The maximum segment length possible between two stations (field devices or switches) is 100 m for data transmission with copper cables. The maximum segment length for fiber-optic cables can be reached up to 14 km. Switches provide structure to networks. They must be suitable for 100 Mbps and full- duplex operation. This prevents collisions on the line, as data can be sent and received simultaneously in a switch with a port. Because the field devices can be found in 10 Mbps systems, network components must support the following features:
l Auto crossover function: adaptation of send and receive lines to enable use of standard 1:1 cables.
l Auto negotiation: automatic adjustment to transmission speed
3.2.4 PROFINET stripping tool
The Industrial Ethernet Fast Connect Stripping Tool (IE FCS) is the stripping tool for the IE FC cables. It can be used for removing the exactly required lengths of outer sheath and shield on the FC cables in one operation as a result of the exactly preset cutting depths and distance of the knives. Sources of error resulting from inexact stripping of the cable when assembling the outlets are thus eliminated. The stripping tool can be used for rapidly connecting the IE Outlet RJ45 and IE FC RJ45 plug complying with PROFINET standards and without causing problems to the industrial Ethernet FC cables. When setting up a PROFINET system, cut the AWG 22 twisted pair cable to the required length, strip it with the stripping tool (for Industrial Ethernet), and fit the Industrial Ethernet Fast Connect RJ45-plugs using the cut-and-clamp technique.
- 24 - Chapter 3 - Planning and designing a PROFINET network
3.3 PROFINET security
PROFINET security concept takes account of the higher network security requirements in Ethernet-based automation systems. This concept covers access control, data encryption, authentication, and logging of safety-relevant events. Ethernet-based communication is taking a central role in the automation world. For example, industrial Ethernet is increasingly being used at the field level, for example, PROFINET. The visibility of activities at plant level (ongoing work, status of systems and devices, and production schedules) is increased, thereby enabling the design of better end-to- end information systems and facilitating decision making. The information exchange between production systems and other enterprise systems is more direct, which allows the company to react more quickly. Uniform interfaces reduce the total costs for diagnostics and support, in particular, because remote support of production processes is possible. Security concepts developed for office environments cannot simply be transferred to automation networks. Security measures implemented for automation systems and networks must not conflict with PROFINET-related requirements. The goal of security measures in the automation area is a reliable automation network that meets requirements. Another point to be aware of is that automation systems are designed for maximum performance and not for maximum security. For example, many systems do not employ proper authentication measures to protect access. The objective is to fulfill the central security objectives of the automation world. A secure system ensures the confidentiality, integrity, and availability of systems and data, even in the case of malicious attacks. To achieve the maximum reasonable level of security for automation systems and networks, a suitable security management process is essential. As part of a consistent security management process, consideration must be given to the following:
l Risk analysis, including identification of counter measures for reducing risk to a reasonable level.
l Coordinated organizational/technical measures (systems engineering).
l Periodic/event-triggeredrepetition.
The basic concept for achieving appropriate security for PROFINET-based automation solutions relies on controlling the necessary accesses to the individual PROFINET domains. This is accomplished by segmentation of the network and establishment of defined zones and by control of communication links between the segments and zones (cell security concept). Together with the use of different technologies and methods, this results in the implementation of a defense-in- depth approach. Because different solutions and technologies may be used depending on the specific requirements and these may be applied in any combination and in connection with segments, the result is an integrated security concept.
- 25 - CHAPTER 4 EXPERION PROFINET SOLUTION OVERVIEW
PROFINET IO device is described by Device Access Point (DAP) which describes how many slots a device has. Slots can be real or virtual. Each slot can take one module. GSDML (Generic Station Description Markup Language) file contains list of modules that a PROFINET device supports. Each Module can contain multiple submodules. Each submodule can have multiple DataItems categorized under Input and Outputs. Terms inputs and outputs are always from the perspective of controller. Controller receives inputs from and provides outputs to IO devices. PROFINET follows provider consumer model for cyclic data access where data provider sends status, called IOPS (Input Output Provider Status) along with data. DataItems are entities that are mapped to controller tags. They are equivalent to channels. Modules or slots do not have IO data or record data. Only submodule can contain cyclic IO data and acyclic record data. Along with cyclical data each submodule provides IOPS (Input Output Provider Status) and /or IOCS (Input Output Consumer Status). Most of the data types supported for each DataItem in PROFINET are of fixed width. All fixed width data item can be represented as built in PROFINET IO blocks. However, for PROFINET devices that do not belong to IO family, DataItem of fixed width might still contain multiple parameters. Such composition of multiple parameters in one DataItem is not defined in GSDML file. In Experion, a generic block template is used to represent PROFINET IO device. Since modules are only a container, we do not represent them in block hierarchy. Each submodule is represented by an IOM type of block.
NOTE IOM block instances for PROFINET device are automatically assigned by the PROFINET configuration tool. Manual assignment (drag and drop) from library to project view is not required.
There are 5 types of IOM blocks that represent submodules in block hierarchy as follows:
l PNETAI Representing PROFINET submodule that has only inputs with fixed data width as described in GSDML file. This IOM will have AI channels under it and number of channels is per device description in GSDML file.
l PNETAO Representing PROFINET submodule that has only outputs with fixed data width as described in GSDML file. This IOM will have AO channels under it and number of channels as per GSDML file.
l PNETDI Representing PROFINET submodule that has only digital inputs (GSDML description with "UseAsBits" as TRUE and device family is IO). This IOM will have DI channels with number of channels as per GSDML file.
l PNETDO Representing PROFINET submodule that has only digital outputs (as described above for DI IOM). This IOM will have DO channels with number as defined in GSDML file.
l PNETMIXSUBMOD Representing PROFINET submodule that has mix of AI, AO, DI, DO channels. Number of channels will depend on GSDML file.
- 26 - Chapter 4 - Experion PROFINET Solution Overview
PNETARRSUBMOD Representing all other submodule that cannot be represented by above 5 submodule types. All inputs for such submodule are mapped to INDATA parameter with array size as per GSDML, and all outputs are mapped to OUTDATA arrayed parameter with size as per GSDML. Making data available in IOM parameter will help using IOPOINT with POINT_PARAM type to use LEAP concepts for this type of submodule. PROFINET IO devices belonging to modular IO family will typically be modeled in Experion as one of PNETAI, PNETAO, PNETDI, PNETDO and PNETMIXSUBMOD. Other PROFINET devices like PLCs, Drives, encoders are not IO modules and submodules description in GSDML file for these devices makes IO data available in the form of array of bytes. All these submodules by default will be mapped to PN_GEN_SUBMOD type of IOM as described earlier.
4.1 Profinet User Defined Submodule block
During engineering of control application, project engineer may need to split the arrays of bytes (input or output) from PROFINET IO devices into meaningful parameters. Content of such array of bytes is not defined in GSDML file. Project engineer is responsible for reading the device user manual to understand the composition of parameters within array of bytes. User Defined Submodule(UDS) block creation is provided for a user to enter the composition in Control Builder. UDS block is conceptually like Gen Device (Generic Device) block in Ethernet/IP, GenDevice block in Ethernet/IP is used where Project Engineer can describe the parameters contained in InputAssembly and OutputAssembly. Similarly, in PROFINET, UDS block can be used by Project engineer to map user defined parameters to input and output from PROFINET submodule. UDS block will have an arrayed parameter called INDATABYTES and OUTDATABYTES to represent raw data in PROFINET submodule, this is in addition to user defined parameters. Instances of various IOM blocks are determined by block extension based on the configuration output generated by Profinet configuration support tool.
4.2 PROFINET IO Data in Control Application
NOTE IOM block instances for PROFINET device are automatically assigned by the PROFINET configuration tool. To load PROFINET IO Data, make sure that the physical devices are communicating with the UOC, otherwise errors will result.
See Control Builder UOC User Guide EPDOC-X512 and Control Building User’s Guide_EPDOC-XX19 for more information.
- 27 - CHAPTER 5 PROFINET LICENSE
This chapter describes the procedure to obtain the license for PROFINET. UOC as PROFINET Controller is a separately licensed feature. Honeywell marketing model number for this license is TC-PROF01. Every UOC controller requires one instance of this license on which PROFINET function is enabled. Two licenses must be procured for the redundant UOC controller.
- 28 - CHAPTER 6 INSTALLATION
This chapter provides information on the procedure to configure PROFINET using Control Builder to integrate with Experion DCS systems. For more information on installing the Experion software, refer to Software Installation User's Guide.
- 29 - CHAPTER 7 CONFIGURATION
l Enable PROFINET in UOC Platform Block
l Configure PROFINET
l Configure PROFINET Custom Sub Module
7.1 Enable PROFINET in UOC Platform Block
The PROFINET in UOC Platform Block presents parameters which describe key characteristics of PROFINET and allows a subset of those parameters to be configured. The PROFINET Block is configured within Experion Control Builder along with all other elements of PROFINET configuration. For a general introduction to the use of Experion Control builder in configuring and monitoring platform blocks, CEE blocks, Control Modules, Sequence Control Modules and other types of loadable objects, see the UOC User Guide.
NOTE PROFINET and EIP can co-exists on Downlink.
7.2 Configure PROFINET
Perform the following steps to configure PROFINET: 1. To enable PROFINET on UOC block, select Enable PROFINET in the Main Tab.
- 30 - Chapter 7 - Configuration
NOTE The connection type for Downlink Network Configuration are: a. For UOC: Ring-DLR b. For vUOC: Non-Redundant
- 31 - Chapter 7 - Configuration
2. Go to PROFINET Configuration Tab, and click PROFINET Device Configuration.
3. To Import the GSDML Files: i. In the Configured Devices page, go to the left top icon to Import GSDML.
NOTE Download the GSDML file from secure sites hosted by device vendors.
- 32 - Chapter 7 - Configuration
ii. Click on the screen to browse the GSDML files from your computer.
iii. Open the GSDML file from your computer.
iv. After completion, the files have been imported successfully confirmation dialog box appears.
NOTE The Station Discovery and Configuration View tool is used for identifying and configuring PROFINET devices which are defined within the PROFINET specification. The DCP tool is capable of:
l Identifying PROFINET devices
l Configuring device name
l Configuring IP address
- 33 - Chapter 7 - Configuration
4. To configure Device Name and to configure IP address. i. In the Configured Devices, click on the Station Discovery and Configuration View icon to identify PROFINET devices, to configure Device Name and to configure IP address.
ii. In the Station Discovery and Configuration, click on the Scan Station icon to scan the devices. It lists all the available PROFINET devices under Downlink.
iii. The user must provide the valid PROFINET device Station Name by changing the name from the list, and click the Set button, and then Save.
- 34 - Chapter 7 - Configuration
iv. A prompt dialog box appears, click Yes to change the Station Name .
v. Once the changes have been saved, a confirmation dialog box appears.
NOTE Similarly, IP address of the device can be change using DCP tool.
NOTE To identify the selected device on Downlink, click Signal button. It shows the selected device with a flash for 3 sec.
Similarly, to Reset Factory Settings of the device click the Reset button. This action deletes all the earlier configuration from the device.
5. Once imported you will be directed to the Configured Device page. Select the device file type from the drop down, it will list the PROFINET devices under that category.
As you select different categories, it will list the Devices under it.
- 35 - Chapter 7 - Configuration
6. Click + to add the device to the PROFINET controller page.
7. Click on the IP to configure the device, fill the Station name, Station IPAddress and Station Scan Time and then click Configure Module.
- 36 - Chapter 7 - Configuration
8. In the Module Configuration page, select the input and output as required, and set the slot number for each, and then click Save.
9. To configure the device parameters select the module, if the parameters already exists it appears on the right-side of the window. Here the user can configure the parameter.
Once saved , click CLOSE, and it will direct you to the PROFINET Configuration tab, click OK.
- 37 - Chapter 7 - Configuration
10. Once done, the selected device will appear on the CONTROL BUILDER Project Assignment.
Here under the UOC IO module you can find the devices with their respective channels.
7.3 Configure PROFINET Custom Sub Module
In ControlBuilder, once you import GSDML(GSDML describes PROFINET IO field devices, it also contains the station name configured in PLC) into control builder, S7 device appears with defined submodules with BYTE octet data. It may be difficult and time consuming for engineers to configure octet string data into control module application. To overcome above issue user can replace default submodules by using User Defined Submodules (UDS) blocks, user can access these parameters by creating IOPOINT. Engineers can define user defined submodules in control builder and can define custom parameters using the PDE (Parameter Definition Editor) tool. Once a UDS block is defined, it can be re-used later.
l Create Custom PROFINET Input submodule type
7.3.1 Creating PROFINET Custom Input SubModule type
Perform the following steps to create PROFINET Custom Input SubModule:
- 38 - Chapter 7 - Configuration
1. Select File -> New ->Type -> Profinet Custom SubModule.
2. Enter library name, type name and then click OK.
- 39 - Chapter 7 - Configuration
3. A PROFINET submodule type with no input parameters is created.
4. Define the input parameters based on the layout of the input data item corresponding to PLC Transfer area.
- 40 - Chapter 7 - Configuration
5. Enter total size in Bytes for the Input corresponding to PLC Transfer area (octet data) item that is used for communication, then click the down arrow.
6. For the input data, define the byte offset, bit offset and size in bits for each of the input parameter defined in the Input Parameters tab. Click OK to close the dialog.
- 41 - Chapter 7 - Configuration
7. Define the scaling values for the each of the input parameter defined in the Input Parameters tab.
8. Click the Save icon on the toolbar to save the changes to the database. Click (X) button to close the Parameter Definition view of the Custom PROFINET SubModule.
9. The newly created SubModule type gets listed under the Library, specified in the Type and Library Definition dialog during creation.
- 42 - Chapter 7 - Configuration
NOTE You can use the same procedure to configure PROFINET Output SubModule. Only exception being that define OPERATORS as the Access Lock in step 4.
- 43 - CHAPTER 8 PROFINET SUPPORTABILITY
The following table provides information about PROFINET functionality specification in UOC.
Interfaces
Number of Profinet 1 (Downlink interface of UOC) Interfaces
Number of Ports 1 (Only port 3 of UOC downlink when Downlink is configured with RING-DLR mode) 2 (If Downlink mode is set to DLR )
Integrated Switch Yes
RJ45 (Ethernet) Yes
Functionality
Profinet IO Yes Controller
Profinet IO No Device
Media No Redundancy (No support of MRP in UOC in R511, external switches can be (MRP) used to connect Profinet IO devices in ring topology with nonredundant connection to UOC) (Downlink can be configured in DLR mode in R511 with all Profinet devices connected to DLR rign using ETAP. This topology should only be used if downlink network comprises of mostly EIP devices with very few Profinet IO devices)
- 44 - Chapter 8 - PROFINET Supportability
Profinet IO Controller
Isochronous No Mode
MRP No
MRPD No
Number of IO 128 devices that can be connected
Fastest Scan 1 ms Time Supported (Minimum cycle time)
Maximum size 64KB Includes IOxS status bytes (This is maximum amount of total Cyclic of data that UOC can exchange with Devices using cyclic Input & Output data exchange protocol) Data
Maximum 1440 bytes including IOxS status bytes number of cyclic input data per device
Maximum 1440 bytes including IOxS status bytes number of cyclic output data per device
Acyclic No Communication
DCP Function Supported (Setting of Name, IP Address, Signal device and Reset device to factory)
Alarms Yes Alarms reported to Experion Station
Diagnostics No
HART support No
Controller Yes. Support redundant UOC controller on Profinet Redundancy network.
- 45 - Chapter 8 - PROFINET Supportability
Profinet IO Controller
System Redundancy (S2 Redundancy) is not supported.
Shared Device No support iDevice No (Intelligent Device support)
CiR No (Configuration New Profinet IO devices can be added on process. Existing in Run) support Profinet devices can be removed on process. But any configuration changes in existing device needs that device to made inactive.
Fast Startup No Support
Support of No Device Profiles
Certification No from PI
Engineering Tool
Experion Yes Control Profinet engineering including DCP settings can be done using Builder as Control Builder tool. engineering tool (Proxy devices like Profibus to Profinet or ASI bus to Profinet adapters/gateways need to be configured using vendor provided tool. GSDML from such vendor provided tool can then be imported in Control Builder)
- 46 - Chapter 8 - PROFINET Supportability
Experion Features
Peer to Peer Yes control Peer to Peer control between C300 and other CDA capable controllers can be done for exchanging Profinet data
LEAP Yes. Supports Experion LEAP features for Profinet engineering support
HART Auto No Device Commission
Profinet IO Yes Data Model Each Profinet device and its contained submodules with their Over CDA IO data is available as UOC blocks over CDA. Standard Experion HMI can be used to design displays with Profinet IO data.
NOTE l The usable cycle time depends on the number of IO devices, input and output data size of used IO devices and the station scan time configured. Number of devices, cycle time and IO data length are related and dependent with each other. E.g. Though maximum number of devices supported are 128, all devices cannot be scanned at 1ms rate.
l RT over UDP is not supported
l Multicast communication is not supported
l DHCP is not supported (either for UOC downlink interface or for connected Profinet IO devices)
- 47 - CHAPTER 9 PROFINET IO BEHAVIOR DURING UOC SWITCHOVER
This chapter provides information on IO channel role during UOC Switch over. In R511, UOC PROFINET controller does not support S2 System Redundancy as defined by PROFINET specification. Please refer PROFINET specifications to understand S2 System Redundancy. Only primary UOC controller maintains PROFINET connection with PROFINET IO devices. On UOC controller switchover, new primary UOC controller will re-establish PROFINET connection (AR) to PROFINET IO devices. Establish new primary connection after old connection is dropped by the IO devices. Connection drop by IO devices depends on the Watchdog time configuration. It is typically three times of configured scan time. Fastest scan time is 1ms and slowest scan time is 2048 ms, so typically range of watchdog time will be between 3ms to 6144ms. Default scan time is 32ms and watchdog time is 96 ms. State of outputs (hold, fail-safe, etc.) from UOC to PROFINET IO devices between the time of loss of Primary controller connection to new connection establishment by new primary controller depends on the PROFINET IO device. Connection establishment from new primary will take 3-6 seconds depending on the size of network and configuration size of PROFINET IO device. Verify how PROFINET IO device manages outputs during connection drop.
- 48 - CHAPTER 10 SIMULATE CONTROL STRATEGY
10.1 For UDS Blocks
Both Aggregate and Scalar Blocks can be used in simulation environment. The behavior is as described below:
l For Parameters configured ad “ Read-Only” Parameters, the behavior based on SIMMODE Configuration is as follows:
SIMMODE = NONE Value cannot be written to.
SIMMODE = DIRECTSUB Value can be directly written to the Parameter.
SIMMODE = SIMVALSUB Value can be directly written to the Parameter.
l For Parameters configured as Writeable Parameters, Value can be written to the Parameter as-is without the need for any additional configuration.
10.2 For IO Blocks
The behavior of PROFINET IO Channels in simulation environment is as described below:
l For SIMMODE = SIMVALSUB one would be able to write the SIMVALUE (AICHANNEL.SIMVALUE or DICHANNEL.SIMVALUE) which then gets propagated to the input parameter.
l For SIMMODE = DIRECTSUB one would be able to write to the input parameter (AICHANNEL.PV or DICHANNEL.PVFL) directly. One is still allowed to write SIMVALUE, or, if you don’t write SIMVALUE, it tracks the written input parameter value.
l For SIMMODE = INITDISABLE you should see INITREQ go Off (AOCHANNEL.INITREQ should be off or DOCHANNEL.INITREQ should be off.
l For FETCHMODE = 1, you should be able to write to the input parameter (AICHANNEL.PV or DICHANNEL.PVFL).
l For FETCHMODE = 1, initialization from output channels should be disabled (AOCHANNEL.INITREQ should be off or DOCHANNEL.INITREQ should be off).
- 49 - CHAPTER 11 TROUBLESHOOTING SCENARIOS
This section provides guidance and background information about the failures which may occur in the PROFINET. The following topics are presented here.
11.1 Checking Control Builder error code reference
An indication of a problem may be in the form of an error dialog that includes an error message and possibly an error code in Control Builder. The syntax for a typical Control Builder error message is as follows: “Connection to device is not open EPKS_E_CL_NOCONN(6L.101.3326). In this syntax, the error code is the last four digits in the message (3326 in this example). See the Control Builder Error Codes Reference_EPDOC-XX17 for applicable error code information.
11.1.1 Using Firmware Manager to capture diagnostic data
The Firmware Manager will show if the module is communicating at all, and if it is, what state it is in, when communication appears lost; this must be the first check. For a redundant controller, the Firmware Manager’s diagnostic capture procedure must be repeated for both the primary and secondary controller. For more information, see Firmware Manager_EPDOC-X404.
11.1.2 Viewing release information log
The ReleaseInfo.txt log provides a list of Experion software releases that have been installed on the computer. To view the log, navigate to this file location on the server: C:\Program Files\Honeywell\Experion\Engineering Tools\system\bin\ReleaseInfo.txt.
11.1.3 Checking server point build log
The SvrPtBld_servername.txt log provides list of process CB points built in the server database. To check the log, navigate to this file location on the server: C:\Program Files\Honeywell\Experion PKS\Engineering Tools\temp\SvrPtBld_servername.txt.
11.1.4 Checking error log
The Errlog_n.txt log provides a running list of Control Builder detected errors in chronological order. The “n” represents any number that is assigned to the most recent log. To check the log, navigate to this file location on the server: C:\ProgramData\Honeywell\Experion PKS\ErrLog_n.txt.
- 50 - Chapter 11 - Troubleshooting Scenarios
11.2 Parameter Reference Dictionary Configuration failure
If you have an ESM Server installed, use the Diagnostic Studio Analysis Tools. These tools examine Experion network configuration parameters and Experion security settings, and will correct detected problems, where possible. See the Control Builder Parameter Reference_EPDOC-XX18.
11.3 Inaccurate Device name
The Discovery and Configuration Protocol (DCP) tool is used for identifying and configuring PROFINET devices which are defined within the PROFINET specification. The DCP tool is capable of
l Identifying PROFINET devices
l Configuring device name
l Configuring IP address
Ensure the accuracy of data and device name in the DCP view.
11.4 Incorrect Network Structure
Ensure the network infrastructure is correct.
11.5 Alarms
In certain circumstances, Alarm Summary and Event Summary displays may not display any alarms or events. The issue can occur in different forms depending on how the user is connecting to the server.
See the section PROFINET alarms for applicable Alarm information.
NOTE All channel related alarms will be present if module related alarm is present.
- 51 - Notices
Trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks of Honeywell International, Inc. ControlEdge™ is a trademark of Honeywell International, Inc. OneWireless™ is a trademark of Honeywell International, Inc. Matrikon® and MatrikonOPC™ are trademarks of Matrikon International. Matrikon International is a business unit of Honeywell International, Inc. Movilizer® is a registered trademark of Movilizer GmbH. Movilizer GmbH is a business unit of Honeywell International, Inc. Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Trademarks that appear in this document are used only to the benefit of the trademark owner, with no intention of trademark infringement. Third-party licenses
This product may contain or be derived from materials, including software, of third parties. The third party materials may be subject to licenses, notices, restrictions and obligations imposed by the licensor. The licenses, notices, restrictions and obligations, if any, may be found in the materials accompanying the product, in the documents or files accompanying such third party materials, in a file named third_party_licenses on the media containing the product, or at http://www.honeywell.com/ps/thirdpartylicenses. Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions support website at: http://www.honeywellprocess.com/support If you have comments about Honeywell Process Solutions documentation, send your feedback to: [email protected] Use this email address to provide feedback, or to report errors and omissions in the documentation. For immediate help with a technical problem, contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell Technical Assistance Center (TAC). How to report a security vulnerability
For the purpose of submission, a security vulnerability is defined as a software defect or weakness that can be exploited to reduce the operational or security capabilities of the software. Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and services. To report a potential security vulnerability against any Honeywell product, please follow the instructions at: https://www.honeywell.com/product-security Support
- 52 - For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To find your local CCC visit the website, https://www.honeywellprocess.com/en-US/contact- us/customer-support-contacts/Pages/default.aspx. Training classes
Honeywell holds technical training classes that are taught by process control systems experts. For more information about these classes, contact your Honeywell representative, or see http://www.automationcollege.com.
- 53 -