PROFINET System Description Technology and Application

HMI Controller

Security Switching Wireless Safety

Sensors Remote Robots I/O Proxy Proxy & Drives

Other Fieldbusses Safety

Remote I/O

Figure 1: PROFINET satisfies all requirements of technology

Introduction

The ever-shorter innovation cycles for new the board. As technology that is standard in the products makes the continuous evolution of automotive industry, widely disseminated in ma- automation technology necessary. The use of chine building, and well-proven in the food and technology has been a significant devel- beverage, packaging, and logistics industries, opment in the past few years. It has made it pos- PROFINET has found its way into all application sible to migrate from central automation systems areas. New application areas are constantly to distributed ones. , as the global emerging, such as marine and rail applications or market leader, has set the benchmark here for even day-to-day operations in a beverage shop. more than 20 years. And highly topical: the new PROFIenergy tech- nology profile will improve the energy balance in In today's automation technology, and production processes. information technology (IT) are increasingly call- ing the shots with established standards like PROFINET is standardized in IEC 61158 and IEC TCP/IP and XML. Integrating information 61784. The ongoing further development of PRO- technology into automation opens up significantly FINET offers users a long-term view for the im- better communication options between automa- plementation of their automation tasks. tion systems, extensive configuration and diag- nostic possibilities, and network-wide service For plant and machine manufacturers, the use of functionality. These functions have been integral PROFINET minimizes the costs for installation, components of PROFINET from the outset. engineering, and commissioning. For plant own- ers, PROFINET offers ease of plant expansion PROFINET is the innovative open standard for and high system availability due to autonomously . PROFINET satisfies all re- running plant units and low maintenance require- quirements for automation technology. Whether ments. the application involves factory automation, process automation, or drives (with or without The mandatory certification for PROFINET de- functional safety), PROFINET is the first choice vices also ensures a high quality standard. across

PROFINET System Description I Table of Contents

1. PROFINET AT A GLANCE…………1 6. OPTIONAL FUNCTIONS………….. 11

1.1 MARKETS AND APPLICATIONS…………. 1 6.1 MULTIPLE ACCESS TO FIELD DEVICES…. 11 1.2 HIGHLIGHTS……………………...... 1 6.2 EXTENDED DEVICE IDENTIFICATION…… 11 1.3 PERSPECTIVES ON PROFINET………. 1 6.3 INDIVIDUAL-PARAMETER-SERVER…….. 12 1.4 CONFORMANCE CLASSES………………2 6.4 CONFIGURATION IN RUN………………. 12 1.5 STANDARDIZATION…………………….. 2 6.5 TIME STAMPING ……………………….. 13 6.6 FAST RESTART………………………... 13 2. MODELING AND ENGINEERING…2 6.7 HIGH AVAILABILITY…………………….. 13 2.1 SYSTEM MODEL OF A PROFINET IO 6.8 CALLING AN ENGINEERING TOOL……….14 SYSTEM………………………………... 2 7. INTEGRATION OF FIELDBUS 2.2 DEVICE MODEL OF AN IO-DEVICE…….. 3 SYSTEMS…………………………… 14 2.3 DEVICE DESCRIPTIONS………………... 3 2.4 COMMUNICATION RELATIONS…………. 3 8. APPLICATION PROFILES………... 15 2.5 ADDRESSING………………………….. 4 8.1 PROFISAFE…………………………... 15 2.6 ENGINEERING OF AN IO SYSTEM……… 4 8.2 PROFIDRIVE………………………….. 15 2.7 WEB INTEGRATION……………………. 5 8.3 PROFIENERGY……………………….. 15 3. BASIC FUNCTIONS OF CONFORMANCE CLASS A………. 5 9. PROFINET FOR PROCESS AUTOMATION……………………… 15 3.1 CYCLIC DATA EXCHANGE……………… 10. NETWORK INSTALLATION……….16 6FEHLER! TEXTMARKE NICHT DEFINIERT. 3.2 ACYCLIC PARAMETER DATA…………… 6 10.1 NETWORK CONFIGURATION…………… 16 3.3 DEVICE/NETWORK DIAGNOSTICS……… 6 10.2 CABLES FOR PROFINET…………….. 17 4. NETWORK DIAGNOSTICS AND 10.3 PLUG CONNECTORS ……………………17 MANAGEMENT OF CONFOR- 10.4 SECURITY………………………………17 MANCE CLASS B………………….. 7 11. PROFINET IO-TECHNOLOGY 4.1 NETWORK MANAGEMENT PROTOCOL…. 7 AND CERTIFICATION…………….. 18 4.2 NEIGHBORHOOD DETECTION………….. 7 4.3 REPRESENTATION OF THE TOPOLOGY… 7 11.1 TECHNOLOGY SUPPORT………………. 18 4.4 DEVICE REPLACEMENT…………………8 11.2 TOOLS FOR PRODUCT DEVELOPMENT… 19 4.5 INTEGRATION OF NETWORK DIAGNOSTICS 11.3 CERTIFICATION TEST………………….. 19 INTO THE IO SYSTEM DIAGNOSTICS…… 8 12. PROFIBUS & PROFINET 5. ISOCHRONOUS REAL-TIME WITH INTERNATIONAL (PI……………… 20 CONFORMANCE CLASS C………. 9 12.1 TASKS PERFORMED BY PI…………….. 20 5.1 SYNCHRONIZED COMMUNICATION…….. 9 5.2 MIXED OPERATION…………………….10 5.3 OPTIMIZED IRT MODE………………...10

Notes on Content

This document describes all essential aspects of Chapters 7 to 9 are dedicated to the integration the PROFINET technology and reflects the level of and other technologies, profiles, and of technology available at the end of 2010. specific process automation topics in PROFINET and describe the additional benefits for PROFI- Chapter 1 introduces PROFINET and provides NET systems. an overview of the market position and modular design. Chapter 10 describes relevant aspects of PRO- FINET networks such as topologies, cables, con- Chapter 2 describes the underlying models and nectors, web integration, and security. the engineering of a PROFINET system. Chapter 11 is directed at product managers and Chapters 3 to 5 cover the basic functions of provides information on product implementation PROFINET communication from the perspective and certification. of conformance classes. Chapter 12 provides information on PROFIBUS Chapter 6 contains a brief description of optional & PROFINET International, the world's largest functions that are used in different applications. interest organization for industrial automation.

PROFINET System Description II Cost-saving and efficient through 1. PROFINET at a glance Application simple putting into operation, target-oriented error search, and faster applications 1.1 Markets and applications

Perfor- Availa- Integrated Devices Openness Flexibility PROFINET is the communication standard for mance bility safety automation of PROFIBUS & PROFINET Interna- tional (PI). The modular range of functions makes PROFINET a flexible solution for all applications PROFINET Net PROFI- TCP/IP Real-time Diagnosis and markets. With PROFINET, applications can Functions structure safe be implemented for production and process automation, safety applications, and the entire range of drive technology up to and including Figure 2: The functionality of PROFINET isochronous motion control applications. Applica- is scalable tion profiles allow optimal use of PROFINET in all areas of automation engineering. flexible line, ring, and star structures and copper and fiber-optic cable solutions. PROFINET saves For plant and machine manufacturers, the use on expensive custom solutions and enables wire- of PROFINET minimizes the costs for installation, less communication with WLAN and . engineering, and commissioning. Scalable real time The plant owner profits from ease of plant ex- pansion, high plant availability, and fast and effi- Communication takes place over the same cable cient automation. in all applications, ranging from simple control tasks to highly demanding motion control applica- The many years of experience with PROFIBUS tions. For high-precision closed-loop control tasks, and the widespread use of Industrial Ethernet deterministic and isochronous transmission of have been rolled into PROFINET. PROFINET time-critical process data with a jitter of less than uses UDP/IP as the higher-level protocol for de- 1 µs is possible. mand-oriented data exchange. In parallel with UDP/IP communication, cyclic data exchange in High availability PROFINET is based on a scalable real-time con- cept. PROFINET integrates automatically reacting re- dundancy solutions and intelligent diagnostic con- In addition, PROFINET plays an important role cepts. Acyclic diagnostic data transmission pro- when it comes to investment protection. PROFI- vides important information regarding the status of NET enables the integration of existing fieldbus the network and devices, including a display of systems like PROFIBUS, AS-Interface, INTER- the network topology. The defined concepts for BUS, Foundation Fieldbus, and DeviceNet, with- media and system redundancy increase the plant out changes to existing devices. That means that availability significantly. the investments of plant operators, machine and plant manufacturers, and device manufacturers Safety integrated are all protected. The proven PROFIsafe safety technology of Establishment of the proven certification process PROFIBUS is also available for PROFINET. The ensures a high standard of quality for PROFINET ability to use the same cable for standard and products and their interoperability in plants. safety-related communication saves on devices, engineering, and setup. 1.2 Highlights 1.3 Perspectives on PROFINET Everything on one cable The PROFINET concept has two perspectives: With its integrated, Ethernet-based communica- PROFINET CBA and PROFINET IO. Figure 3 tion, PROFINET satisfies a wide range of shows how the two perspectives interrelate. requirements, from data-intensive parameter assignment to extremely fast I/O data transmis- PROFINET CBA is suitable for component-based sion. PROFINET thus enables automation in real- machine-to-machine communication via TCP/IP time. In addition, PROFINET provides a direct and for real-time communication required for interface to the IT level. modular plant designs. It enables a simple modu- lar design of plants and production lines based on Flexible network topology distributed intelligence using graphics-based con- figuration of communication between intelligent PROFINET is 100% Ethernet compatible accord- modules. PROFINET IO describes an I/O data ing to IEEE standards and adapts to view of distributed I/O. It includes real-time (RT) circumstances in the existing plant thanks to its communication and isochronous real-time (IRT) communication for cyclic process data.

PROFINET System Description 1 PROFINET CBA A detailed description of the CCs can be found in the document "The PROFINET IO Conformance Classes" under “Downloads/Supplementary Documents”. PROFINET IO 1.5 Standardization PROFINET is specified in IEC 61158 and IEC 61784. The PROFINET concept was defined in close collaboration with end users based on stan- Figure 3: PROFINET perspectives dard Ethernet according to IEEE 802. Additions to standard Ethernet were specified only in cases PROFINET CBA and PROFINET IO can be oper- where requirements could not be met or could not ated separately and in combination such that a be met satisfactorily with standard Ethernet. PROFINET IO unit appears in the plant view as a

PROFINET CBA modul.

This description provides a detailed explanation of 2. Modeling and PROFINET IO specifically. engineering

1.4 Conformance classes This section explains the models of a PROFINET IO system and uses an example planning process The scope of functions supported by PROFINET to describe the addressing options. IO is clearly divided into conformance classes (“CC”). These provide a practical summary of the various minimum properties. 2.1 System model of a PROFI- NET IO system There are three conformance classes that build upon one another and are oriented to typical ap- PROFINET IO follows the Provider/Consumer plications (Figure 4). model for data exchange. Configuring a PROFI- NET IO system has the same look and feel as in PROFIBUS. The following device classes are defined for PROFINET IO (5):

IO-Controller: This is typically the programmable logic controller (PLC) on which the automation program runs. This is comparable to a class 1 master in PROFIBUS. The IO-Controller provides output data to the configured IO-Devices in its role as provider and is the consumer of input data of IO-Devices.

IO-Device: An IO-Device is a distributed I/O field Figure 4: Structure of conformence classes device that is connected to one or more IO- Controllers via PROFINET IO. It is comparable to the function of a slave in PROFIBUS. The IO- CC-A provides basic functions for PROFINET IO Device is the provider of input data and the con- with RT communication. All IT services can be sumer of output data. used without restriction. Typical applications are found, for example, in . Wire- IO-Supervisor: This can be a programming de- less communication is only possible in this class. vice, personal computer (PC), or human machine interface (HMI) device for commissioning or diag- CC-B extends the concept to include network nostic purposes and corresponds to a class 2 diagnostics via IT mechanisms as well as topol- master in PROFIBUS. ogy information. The system redundancy function important for process automation is contained in A plant unit has at least one IO-Controller and one an extended version of CC-B named CC-B(PA). or more IO-Devices. IO-Supervisors are usually integrated only temporarily for commissioning or CC-C describes the basic functions for devices troubleshooting purposes. with hardware-supported bandwidth reservation and synchronization (IRT communication) and is thus the basis for isochronous applications.

The conformance classes also serve as the basis for certification and for the cabling guidelines.

PROFINET System Description 2 To avoid competing accesses in the definition of e.g. PLC Programming device user profiles (e.g., for PROFIdrive, weighing and PROFINET IO-Controller PROFINET IO-Supervisor dosing, etc.), the API (Application Process Identi- fier/Instance) is defined as an additional address- ing level.

PROFINET differentiates between compact field Ethernet devices, in which the degree of expansion is already specified in the as-delivered condition and . Configuration . Diagnostics cannot be changed by the user, and modular . Process data . Status/control field devices, in which the degree of expansion . Alarms . Parameterization can be customized for a specific application when the system is configured.

Field devices PROFINET IO-Device 2.3 Device descriptions The GSD files (General Station Description) of the Figure 5: Communication paths for PROFINET IO field devices to be configured are required for system engineering. This XML-based GSD de- scribes the properties and functions of the PRO- 2.2 Device model of an IO-Device FINET IO field devices. It contains all data rele- vant for engineering as well as for data exchange The device model describes all field devices in with the field device. The field device manufac- terms of their possible technical and functional turer must supply the XML-based GSD in accor- features. It is specified by the DAP (Device dance with the GSDML specification. Access Point) and the defined modules for a par- ticular device family. A DAP is the access point for communication with the Ethernet interface and the 2.4 Communication relations processing program. A variety of I/O modules can To establish communication between the higher- be assigned to it in order to manage the actual level controller and an IO-Device, the communica- process data communication. tion paths must be established. These are set up The following structures are standardized for an by the IO-Controller during system startup based IO-Device: on the configuration data in the engineering sys- tem. This specifies the data exchange explicitly.  The slot designates the place where an I/O module is inserted in a modular I/O field de- Every data exchange is embedded into an AR vice. The configured modules containing one (Application Relation) (Figure 7). Within the AR, or more subslots for data exchange are ad- CRs (Communication Relations) specify the data dressed on the basis of the different slots.  Within a slot, the subslots represent the ac- tual interface to the process (inputs/outputs). The granularity of a subslot (bitwise, byte- wise, or wordwise division of I/O data) is determined by the manufacturer. The data content of a subslot is always accompanied by status information, from which the validity of the data can be derived.  The index specifies the data within a slot/subslot that can be read or written acycli- cally via read/write services. For example, parameters can be written to a module or Figure 6: Addressing of I/O data in PROFINET IO manufacturer-specific module data can be based on slots and subslots read out on the basis of an index. explicitly. As a result, all data for the device Cyclic I/O data are addressed by specifying the modeling, including the general communication slot/subslot combination. These can be freely parameters, are downloaded to the IO-Device. An defined by the manufacturer. For acyclic data IO-Device can have multiple ARs established communication via read/write services, an appli- from different IO-Controllers. cation can specify the data to be addressed using slot, subslot, and index (Figure 6).

PROFINET System Description 3 ing options supported by a field device are defined in the GSD file for the respective field device.

Optionally, the name can also be automatically assigned to the IO-Device by means of a speci- fied topology based on neighborhood detection.

A PROFINET IO-Device is addressed for direct data exchange by its MAC address (see box). Figure 7: Application relations and communication relations MAC address and OUI (organizationally unique identifier)

The communication channels for cyclic data ex- Each PROFINET device is addressed based on a change (IO data CR), acyclic data exchange (re- MAC address. This address is unique worldwide. cord data CR), and alarms (alarm CR) are set up The company code (bits 47 to 24) can be obtained simultaneously. free of charge from the IEEE Standards Depart- ment. This part is called the OUI (organizationally Multiple IO-Controllers can be used in a unique identifier). PROFINET system (Figure 8). If these IO- PI offers MAC addresses to device manufacturers Controllers are to be able to access the same that do not want to apply for their own OUI, in other data in the IO-Devices, this must be specified words, a fixed OUI and the manufacturer-specific when configuring (shared devices, shared inputs). portion (bits 23 to 0). This service allows compo- nents to acquire MAC addresses from the PI Sup- port Center. The assignment can be completed in 4 K-ranges.

The OUI of PI is 00-0E-CF and is structured as shown in the table. The OUI can be used for up to 16,777,214 products.

Bit significance 47 to 24 Bit significance 23 to 0

0 0 0 E C F X X X X X X

Company code  OUI Consecutive number

Figure 8: A field device can be accessed by multiple application relations 2.6 Engineering of an IO system Each IO-Controller manufacturer also provides an An IO-Controller can establish one AR each with engineering tool for configuring a PROFINET sys- multiple IO-Devices. Within an AR, several IOCRs tem. and APIs can be used for data exchange. This can be useful, for example, if more than one user During system engineering, the configuring engi- profile (PROFIdrive, Encoder, etc.) is involved in neer joins together the modules/submodules of an the communication and different subslots are IO-Device defined in the GSD file in order to map required. The specified APIs serve to differentiate them to the real system and to assign them to the data communication within an IOCR. slots/subslots. The configuring engineer config- ures the real system symbolically in the engineer- 2.5 Addressing ing tool. Figure 9 shows the relationship between the GSD definitions, configuration, and real plant In PROFINET IO, each field device has a sym- view. bolic name that uniquely identifies the field device within a PROFINET IO system. This name is used After completion of system engineering, the con- for assigning the IP address and the MAC figuring engineer downloads the system data to address. The DCP protocol (Dynamic Configura- the IO-Controller, which also contains the system- tion Protocol) integrated in every IO-Device is specific application. As a result, an IO-Controller used for this purpose. has all the information needed for addressing the IO-Devices and for data exchange. The IP address is assigned with the DCP protocol based on the device name. Because DHCP (Dy- Before an IO-Controller can perform data namic Host Configuration Protocol) is in wide- exchange with the IO-Devices, these must be spread use internationally, PROFINET has pro- assigned an IP address based on their configured vided for optional address setting via DHCP or via name. This must take place prior to system manufacturer-specific mechanisms. The address- power-up.

PROFINET System Description 4 Engineering Tool

Device Manufacturer provides a GSD file and defines the Plant View I/O modules

Slot 0 Slot 1 Slot 2 Slot 3 ...

Device family 1 Subslot 0 Subslot 0 Subslot 0 …. Definition Module 1 Subslot 1, Definition1Submodule  inputs 0x00, 0x34 Adaption of the GSD VirtualSubmoduleItem Index 1 file to the real device RecordData  0x00,0x34,… Parameter Const Dtata  0x00,0x34,… ... Byte Offset  1 Definition Module 1 Subslot x Bus interface

Figure 9: Assignment of definitions in the GSD file to IO Devices when configuring the system

The IO-Controller performs this automatically 3. Basic functions of Con- using the DCP protocol. formance Class A After a startup/restart, an IO-Controller always initiates system power-up based on the configura- The basic functions of Conformance Class A tion data without any intervention by the user. include cyclic exchange of I/O data with real-time During system power-up, an IO-Controller estab- properties, acyclic data communication for read- lishes an explicitly specified communication rela- ing and writing of demand-oriented data (parame- tion (CR) and application relation (AR) with an IO- ters, diagnostics), including the Identification & Device. This specifies the cyclic I/O data, the Maintenance Function (I&M) for reading out de- alarms, the exchange of acyclic read/write ser- vice information and a flexible alarm model for vices, and the expected modules/submodules. signaling device and network errors with three After successful system power-up, the exchange alarm levels (maintenance required, urgent main- of cyclic process data, alarms, and acyclic data tenance required, and diagnostics) (Table 1). traffic can occur.

2.7 Web integration PROFINET is based on Ethernet and supports Requirement Technical func- TCP/IP. This enables use of web technologies for tion/solution accessing an integrated web server in a field device, among other things. Depending on the Cyclic data exchange PROFINET with RT specific device implementation, diagnostics and communication other information can be easily called up using a Acyclic parameter data/ Read Record/ standard web browser, even across network device identification Write Record boundaries. Thus, an engineering system is no (HW/FW) I&M0 longer necessary for simple diagnostics. PROFI- Device/ network diag- Diagnostics and NET itself does not define any specific contents or nostics (alarms) maintenance formats. Rather, it allows an open and free im- plementation. Table 1: List of basic functions

PROFINET System Description 5 3.1 Cyclic data exchange 3.2 Acyclic parameter data Cyclic I/O data are transmitted via the “IO Data Acyclic data exchange can be used for parameter CR” unacknowledged as real-time data between assignment or configuration of IO-Devices or provider and consumer in an assignable time reading out status information using the “Record base. The cycle time can be specified individually Data CR”. This is accomplished with read/write for connections to the individual devices and are frames using standard IT services via UDP/IP, in thus adapted to the requirements of the applica- which the different data records are distinguished tion. Likewise, different cycle times can be by their index. In addition to the data records selected for the input and output data, within the available for use by device manufacturers, the range of 250 µs to 512 ms. following system data records are also specially defined: The connection is monitored using a time monitor- ing setting that is derived from a multiple of the  Diagnostic information on the network and cycle time. During data transmission in the frame, device diagnostics can be read out by the the data of a subslot are followed by a provider user from any device at any time. status. This status information is evaluated by the  Error log entries (alarms and error mes- respective consumer of the I/O data. As a result, it sages), which can be used to determine de- can evaluate the validity of the data from the tailed timing information about events within cyclic data exchange alone. In addition, the con- an IO-Device. sumer statuses for the opposite direction are  Identification and Maintenance informa- transmitted. tion (I&M)

The data in the message frames are followed by The ability to read out identification information accompanying information that provides informa- from a field device is very helpful for maintenance tion about the data's validity, the redundancy, and purposes. For example, this allows inferences to the diagnostic status (data status, transfer status). be drawn in response to incorrect behavior or The cycle information (cycle counter) of the pro- regarding unsupported functionality in a field vider is also specified so that its update rate can device. This information is specified in the I&M be determined easily. Failure of cyclic data to data structures. arrive is monitored by the respective consumer in the communication relation. If the configured data The I&M functions are subdivided into 5 different fail to arrive within the monitoring time, the con- blocks (IM0 ... IM4) and can be addressed sepa- sumer sends an error message to the application rately using their index. Every IO-Device must (Figure 10). support the IM0 function with information about hardware and firmware versions. The cyclic data exchange can be realized with standard network components, such as switches The I&M specification titled “Identification & Main- tenance Functions” can be downloaded from the PI website.

3.3 Device/network diagnostics A status-based maintenance approach is currently gaining relevance for operation and maintenance. It is based on the capability of devices and com- ponents to determine their status and to commu- nicate this using agreed mechanisms. A system for reliable signaling of alarms and status mes- sages by the IO-Device to the IO-Controller was defined for PROFINET IO for this purpose.

This alarm concept covers both system-defined Figure 10: Real-time communication with cycle events (such as removal and insertion of mod- time monitoring ules) as well as signaling of faults that were detected in the utilized controller technology (e.g., defective load voltage or wire break). This is and standard Ethernet controllers and takes place based on a state model that defines “good” and directly on Layer 2 with Ethertype 0x8892 and “defective” status as well as the “maintenance without any TCP(UDP)/IP information. For opti- required” and “maintenance demanded” pre- mized processing of cyclic data within a network warning levels. A typical example for this is the component, the VLAN tag according to loss of media redundancy, which signals “mainte- IEEE802.1Q is additionally used with a high nance required” but, because of its redundancy, priority. the media is still fully functional.

PROFINET System Description 6 IO-Controller IO-Device 4.2 Neighborhood detection Data Automation systems can be configured flexibly in a line, star, or tree structure. To compare the Alarm specified and actual topologies, i.e., to determine Maintenance which field devices are connected to which switch Alarm port and to identify the respective port neighbor, LLDP according to IEEE 802.1 AB was applied in Diagnostics demanded Alarm PROFINET IO. required PROFINET field devices exchange existing addressing information with connected neighbor incoming outgoing alarm alarm devices via each switch port. The neighbor de- vices are thereby unambiguously identified and Figure 11: Diagnostic model for signaling faults with their physical location is determined (example in different priority Figure 12: The delta device is connected to port 003 of switch 1 via port 001).

Diagnostic alarms must be used if the error or event occurs within an IO-Device or in conjunction with the connected components. They can signal an incoming or outgoing fault status (Figure 11).

In addition, the user can define corresponding process alarms for messages from the process, e.g., limit temperature exceeded. In this case, the IO-Device may still be operable. These process alarms can be assigned different priorities than the diagnostic alarms.

4. Network diagnostics and management of Confor- Figure 13: PROFINET field devices detect their mance Class B neighbors

Conformance Class B expands devices to include functions for additional network diagnostics and for topology detection. PROFINET uses SNMP 4.3 Representation of the (Simple Network Management Protocol) for this. Portions of MIB2 (Management Information Base topology 2) and LLDP-EXT MIB (Lower Link Discovery A plant owner can use a suitable tool to graphi- Protocol-MIB) are integrated into devices. In cally display a plant topology and port-granular parallel to SNMP, all diagnostics and topology diagnostics (Figure 12). The information found information can also be called up from the PDEV during neighborhood detection is collected using (Physical Device Object) using acyclic PROFINET the SNMP protocol. This provides the plant opera- services. tor a quick overview of the plant status. 4.1 Network management protocol In existing networks, SNMP has established itself as the de facto standard for maintenance and monitoring of network components and their func- tions. SNMP can read-access network compo- nents, in order to read out statistical data pertain- ing to the network as well as port-specific data and information for neighborhood detection. In order to monitor PROFINET devices with an es- tablished management system, implementation of SNMP is mandatory for devices of Conformance Classes B and C.

Figure 12: Plan topology

PROFINET System Description 7 Figure 14: PROFINET IO supports convenient device replacement and display of plant topology.

4.4 Device replacement If a field device fails in a known topology, it is possible to check whether the replacement device has been reconnected in the proper position. It is IO-Controller even possible to replace devices without the use of an engineering tool: when replaced, a device at a given position in the topology receives the same name and parameters as its predecessor (Figure 14). 1 2 4.5 Integration of network diag- nostics into the IO system diagnostics IO-Device3 A switch must also be configured as a PROFINET IO-Device and signal the detected network errors of a lower-level Ethernet line directly to the IO- Controller. Acting as an IO-Device, this type of switch can signal faults and specific operating modes to its IO-Controller by transmitting acyclic IO-Device1 IO-Device2 alarms using the “alarm CR”. In this way, the net- work diagnostics can be integrated into the IO Figure 15: Integration of network diagnostics into IO system diagnostics (Figure 15). system diagnostics

PROFINET System Description 8 5. Isochronous real-time with Conformance Class C

Conformance Class C includes all necessary net- work-wide synchronization functions for applica- t1 tions with the most stringent requirements for t2 Cable? Cable Cable Cable deterministic behavior. Networks based on Con- t3 t4 formance Class C enable applications having a jitter of less than 1 microsecond. Cyclic data packets are transferred as synchronized packets Figure 16: Synchronization of clock pulse genera- tors within an IRT domain by the clock on a reserved bandwidth. All other packets, such master as packets for diagnostics or TCP/IP, share the rest of the Ethernet bandwidth.

By default, the minimum update rate is defined at within a clock system (IRT domain) to the same 250 µs in Conformance Class C. For maximum clock (Figure 16). For this purpose, all of the de- control performance, this can be reduced to as vices involved in this type of clock system must be low as 31.25 µs, depending on the hardware connected directly to one another, without cross- used. In order to expand data volumes when ing through any non-synchronized devices. Multi- cycle times are set at less than 250 µs, a mes- ple independent clock systems can be defined in sage frame optimization method (dynamic frame one network. packing, DFP) is incorporated. With this method, nodes that are wired together in a line structure To achieve the desired accuracy for the synchro- are addressed with one message frame. In addi- nization and synchronous operation, the runtime tion, for cycle times less than 250 µs, the TCP/IP on each connecting cable must be measured with communication is fragmented and transmitted in defined Ethernet message frames and figured into smaller packets. the synchronization. Special hardware precau- tions must be taken for implementing this clock synchronization. 5.1 Synchronized communi- cation The bus cycle is divided into different intervals for synchronized communication (Figure 17). First, In order for the bus cycles to run synchronously the synchronous data are transmitted in the red (at the same time) with a maximum deviation of 1 interval. This red interval is protected from delays µs, all devices involved in the synchronous com- caused by other data and allows a high level of munication must have a common clock. A clock determinism. In the subsequent open green inter- master uses synchronization frames to synchro- val, all other data are transmitted according to nize all local clock pulse generators of devices IEEE 802 and the specified priorities.

1 2 3

Controller Device 1 Device 2 Device 3

C  3

C2 C  3 C1 phase C  2 C  3 Real-time Cycle e.g. 1ms e.g. Cycle phase TCP/IP

C1 C 2 C 3

C 2 C 3

phase C 3 Real-time phase TCP/IP

Figure 17: IRT communication divides the bus cycle into a reserved interval (red) and an open interval (green)

PROFINET System Description 9 IRT Domain Switch which supports IRT scheduling The division of the individual intervals can vary. If IO-Controller forwarding of the data before the start of the next (Sync-Master) reserved interval is not assured, these frames are stored temporarily and sent in the next green in-

terval. IO-Device 1 IO-Device 2 IO-Device 3 5.2 Mixed operation

A combination of synchronous and asynchronous Devices without synchronous communication within an automation system is application possible, if certain preconditions are met. A mixed operation is shown in Figure 18. In this example, Figure 18: Mixed operation of synchronized and a synchronizable switch has been integrated in unsynchronized applications the field device for devices 1 to 3. This enables the runtime to be determined and precise syn- chronization of the clock system to be maintained. the field devices in the red interval. This frame is The other two devices are connected via a stan- disassembled or assembled in the corresponding dard Ethernet port and thus communicate asyn- switch, if required. chronously. The switch ensures that this commu- This DFP technology is optional for systems with- nication occurs only during the green interval. stringent requirements. The functionalities of the other intervals are retained, i.e., a mixed opera- 5.3 Optimized IRT mode tion is also possible here. To achieve short cycle times of up to 31,25 µs, however, the green inter- When the time ratios are subject to stringent re- val must also be sharply reduced. To accomplish quirements, the efficiency of the topology-oriented this, the standard Ethernet frames for the applica- synchronized communication can be optimized tion are disassembled transparently into smaller using dynamic frame packing (DFP) (Figure 19). fragments, transmitted in small pieces, and reas- sembled. For a line structure, the synchronous data of sev- eral devices are optionally combined into one Ethernet frame. The individual cyclic real-time data can be extracted for each node. Because the data from the field devices to the controller are

also strictly synchronized, these data can be as- sembled by the switch in a single Ethernet frame.

Ideally, only one frame is then transmitted for all

1 2 3

Controller Device 1 Device 2 Device 3

Header C  3 C  2 Header C  3 C  1 Header CRC C  2 CRC C  3 CRC phase Cycle e.g. 1ms Cycle e.g. Real-time phase TCP/IP

Figure 19: Packing of individual message frames into a group message frame

PROFINET System Description 10 6. Optional functions IO-Controller 1 IO-Controller 2

Additionally, PROFINET provides a large number of optional functions that are not included in de- vices by default by way of Conformance Classes (Table 1). If additional functions are to be used, this must be checked on a case-by-case basis PROFINET using the device properties (data sheet, manuals, GSD file).

Requirement Technical func- tion/solution Multiple access to inputs by Shared input various controllers Distribution of device functions Shared device to various controllers Extended device identification Identification & Maintenance Figure 20: Shared device: Access of multiplecon IM1-4 trollers to different modules in a device Automatic parameter assign- Individual parame- ment of devices using parame- ter server IO-Controller 1 IO-Controller 2 ter sets Configuration changes during Configuration in operation Run (CiR) Time stamping of I/O data Time sync Fast restart after voltage re- Fast start-up covery (FSU) PROFINET Higher availability through ring MRP/MRPD redundancy Call of a device-specific engi- Tool Calling Inter- neering tool face (TCI)

Table 1: List of possible optional fuctions

6.1 Multiple access to field Figure 21: Shared input: Multiple controllers read devices the same inputs a device The innovative starting point for shared devices is the parallel and independent access of two dif- 6.2 Extended device ferent controllers to the same device (Figure 20). In the case of a shared device, the user config- identification ures a fixed assignment of the various I/O mod- Further information for standardized and simpli- ules used in a device to a selected controller. One fied identification and maintenance is defined in possible application of a shared device is in fail- additional I&M data records. I&M1-4 contain plant- safe applications in which a fail-safe CPU controls specific information, such as installation location the safe portion of the device and a standard con- and date, and are created during configuration troller controls the standard I/O within the same and written to the device (Table 3). station. In the safety scenario, the F-CPU uses the fail-safe portion to safely switch off the supply voltage of the outputs. IM1 TAG_FUNCTION Plant designation TAG_LOCATION Location designation In the case of a shared input, there is parallel access to the same input by two different control- IM2 INSTALLA- Installation date lers (Figure 21). Thus, an input signal that must TION_DATE be processed in two different controllers of a plant IM3 DESCRIPTOR Comments does not have to be wired twice or transferred via CPU-CPU communication. IM4 SIGNATURE Signature

Table 3: Extended device identification

PROFINET System Description 11 Figure 23: A parameter server can be used to automatically reload backed-up data during device replacement

6.3 Individual-Parameter-Server field device fails and is replaced, these parame- ters must also be reloaded to the new field device The individual parameter server functionality is without the need for an additional tool. The indi- available for backing up and reloading of other vidual parameter server provides plant operators optional individual parameters of a field device a convenient and uniform solution for this. (Figure 22).

The basic parameter assignment of a field device 6.4 Configuration in Run is carried out using the parameters defined in a Like redundancy, uninterrupted plant operation – GSD file for the field device. A GSD file contains including when reconfiguring devices and net- module parameters for I/O modules, among other works and when inserting, removing, or replacing things. These are stored as static parameters and devices or individual modules – plays an impor- can be loaded from the IO-Controller to an IO- tant role in process automation (Figure 22). All of Device during system power-up. For some field these “Configuration in Run” measures (CiR) are devices it is either impossible or inappropriate to carried out in PROFINET bumpless and without initialize parameters using the GSD approach due adversely affecting network communication. This to the quantities, the user guidance, or the secu- ensures that plant repairs, modifications, or ex- rity requirements involved. Such data for specific pansions can be performed without a plant shut- devices and technologies are referred to as indi- down in continuous production processes, as well. vidual parameters (iPar). Often, they can be specified only during commissioning. If such a

State CiR Phase 1 CiR Phase 2 CiR finish before Establish a AR switch over second AR IOC IOC IOC IOC

AR AR CiR-AR AR CiR-AR AR

PB CiRP P P P CiR (B)

IOD IOD IOD IOD

t B: Backup P: Primary CiR: the CiR-AR is always Backup

Figure 22: Configuration changes without plant interruption thanks to redundant connection

PROFINET System Description 12

The task of a media redundancy manager (MRM) 6.5 Time stamping is to check the functional capability of the config- In large plants, the ability to assign alarms and ured ring structure. This is done by sending out status messages to a sequence of events is often cyclic test frames. As long as it receives all of its required. For this purpose, an optional time test frames again, the ring structure is intact. As a stamping of these messages is possible in PRO- result of this behavior, an MRM prevents frames FINET IO. In order to time stamp data and alarms, from circulating and converts a ring structure into the relevant field devices must have the same time of day. To accomplish this, a master clock and the time synchronization protocol are used to set the clocks to the same time.

6.6 Fast restart Fast Start Up (FSU) defines an optimized system power-up in which data exchange begins much faster starting with the second power-up since many parameters are already stored in the field devices. This optional path can be used in parallel to standard power-up (which is still used after a Power On and during the first power-up or reset). Bild 24: Verhindern von zirkulierenden Frames It must be possible to store communication durch das logische Auftrennen parameters retentively for this. des Busses 6.7 High availability a line structure. Chaining of multiport switches allowed the star topology widely used in Ethernet to be effectively A media redundancy client is a switch that acts combined with a line structure. This combination only as a "passer" of frames and generally does is especially well-suited for control cabinet con- not assume an active role. It must have two nections, i.e., line connection between control switch ports in order to connect to other MRCs or cabinets and star connection to process-level field the MRM in a single ring. device. If the connection between two field de- vices in a line is interrupted, the field devices situ- ated after the interruption are no longer accessi- Media redundancy for planned duplication ble. If increased availability is required, provision (MRPD) must be made for redundant communication paths when planning the system, and field IEC 61158 describes the redundancy concept devices/switches that support the redundancy MRPD (Media Redundancy for Planned Duplica- concept of PROFINET must be used. tion) for topology-optimized IRT communication, which enables smooth switchover from one com- The line can be closed to form a ring to easily munication path to another in the event of a fault. provide a redundant communication path. In the During system power-up, the IO Controller loads event of an error, the connection to all nodes is the data of the communication paths for both ensured via the alternative connection. This communication channels (directions) in a commu- achieves a tolerance for one fault. Organizational nication ring to the individual nodes. Thus, it is measures must be taken to ensure that this fault immaterial which node fails because the loaded is eliminated before a second error occurs. "schedule" for both paths is available in the field devices and is monitored and adhered to without PROFINET has two mechanisms for setting up exception. Loading of the "schedule" alone is ring-shaped media redundancy, depending on the sufficient to exclude frames from circulating in this requirements: variant, because the destination ports are explic- Media redundancy protocol (MRP) itly defined.

The MRP protocol according to IEC 62439 de- scribes PROFINET redundancy with a typical reconfiguring time of < 200 ms for communication paths with TCP/IP and RT frames after a fault. Error-free operation of an automation system in- volves a media redundancy manager (MRM) and several media redundancy clients (MRC) arranged in a ring, as shown in Figure 24.

PROFINET System Description 13 6.8 Calling an engineering tool This means that any combination of fieldbus and PROFINET-based subsystems can be configured. Complex devices, such as drives, laser scanners, Thus a smooth technology transition is possible etc., often have their own engineering software from fieldbus-based systems to PROFINET. The and tools for making settings for these IO- following requirements are taken into considera- Devices. With the tool calling interface (TCI) these tion here: device tools can now be called directly from the plant engineering system for parameter assign-  Plant owners would like the ability to easily ment and diagnostics. In this case, the communi- integrate existing installations into a newly cation of PROFINET is used directly for the set- installed PROFINET system. tings in the field device. In addition to the directly  Plant and machine manufacturers would like integrated device tools, other technologies such the ability to use their proven and familiar as EDDL and FDT can also be used with appro- devices without any modifications for PRO- priate adaption software. TCI consists of the fol- FINET automation projects, as well. lowing main components:  Device manufacturers would like the ability to integrate their existing field devices into  Call interface: The user can call various field PROFINET systems without the need for device user interfaces (Device Tools = DT) costly modifications. from the engineering system (ES). Functions are primarily initiated in the device tools Fieldbus solutions can be easily and seamlessly through user interaction. integrated into a PROFINET system using proxies  Communication interface: The TCI com- and gateways. The proxy acts as a representative munication server allows the field device user of the fieldbus devices on the Ethernet. It inte- interface (DT) to communicate with the field grates the nodes connected to a lower-level field- device. bus system into the higher-level PROFINET sys- tem. As a result, the advantages of fieldbuses, Thanks to the freely available TCI specification, such as high dynamic response, pinpoint diagnos- every manufacturer can create a DT that works tics, and automatic system configuration without autonomously and integrate it into any TCI- settings on devices, can be utilized in the PROFI- capable ES. The use of TCI is well-suited for field NET world, as well. These advantages simplify devices in the lower price bracket as well as com- planning through the use of known sequences. plex devices already equipped with a user inter- Likewise, commissioning and operation are made face, because the implementation effort is easier through the comprehensive diagnostics manageable. properties of the fieldbus system. Devices and software tools are also supported in the accus- 7. Integration of fieldbus tomed manner and integrated into the handling of systems the PROFINET system.

PROFINET specifies a model for integrating existing PROFIBUS and other fieldbus systems such as INTERBUS and DeviceNet (Figure 25).

Figure 25: Integration of fieldbus systems is easy with PROFINET

PROFINET System Description 14 8. Application profiles 8.3 PROFIenergy The high cost of energy and compliance with legal By default, PROFINET transfers the specified obligations are compelling industry to engage in data transparently. It is up to the user to interpret energy conservation. Recent trends toward the the sent or received data in the user program of a use of efficient drives and optimized production PC-based solution or programmable logic control- processes have been accompanied by significant ler. energy savings. However, in today's plants and production units, it is common for numerous Application profiles are specifications for particular energy consuming loads to continue running dur- properties, performance characteristics, and be- ing pauses. PROFIenergy addresses this situa- havior of devices and systems that are developed tion. jointly by manufacturers and users. The term “profile” can apply to a few specifications for a PROFIenergy enables an active and effective particular device class or a comprehensive set of energy management. By purposefully switching specifications for applications in a particular in- off unneeded consumers and/or adapting parame- dustry sector. ters such as clock rates to the production rate, energy demand and, thus, energy costs can be In general, two groups of application profiles are drastically reduced. In doing so, the power con- distinguished: sumption of automation components such as  General application profiles that can be robots and laser cutting machines or other sub- used for different applications (examples of systems used in production industries is con- these include the profiles PROFIsafe and trolled using PROFIenergy commands. PROFI- PROFIenergy) NET nodes in which PROFIenergy functionality is implemented can use the commands to react  Specific application profiles that were each flexibly to idle times. In this way, individual de- developed for a specific type of application, vices or unneeded portions of a machine can be such as PROFIdrive or devices for process shut down during short pauses, while a whole automation. plant can be shut down in an orderly manner dur- These application profiles are specified by PI ing long pauses. In addition, PROFIenergy can based on market demand and are available on help optimize a plant's production on the basis of the PI-website. its energy consumption.

8.1 PROFIsafe 9. PROFINET for Process The PROFIsafe designation refers to a protocol defined in IEC 61784-3-3 for implementation of Automation functional safety (fail-safe) and recognized by IFA and TÜV. PROFIsafe can be used with Compared with production automation, process PROFIBUS and PROFINET alike. automation has a few special characteristics that contribute to defining the use of automation to a The use of PROFIsafe enables elements of a fail- large extent. Plants can have a service life of safe controller to be transferred directly to the many decades. This gives rise to a requirement, process control on the same network. The need on the part of plant operators, for older and newer for additional wiring is eliminated. technologies to coexist in such a way that they are functionally compatible. In addition, require- 8.2 PROFIdrive ments for reliability of process plants, particularly in continuous processes, are often considerably The PROFIdrive designation refers to the specifi- greater. As a result of these two factors, invest- cation of a standardized drive interface for ment decisions regarding new technologies are PROFIBUS and PROFINET. This application- significantly more conservative in process auto- oriented profile, which has been standardized in mation than in production automation. IEC 61800-7, contains standard definitions (syn- tax and semantics) for communication between For optimal use of PROFINET in all sectors of drives and automation systems, thus assuring process automation, PI has created a require- vendor neutrality, interoperability, and investment ments catalog in collaboration with users. In this protection. manner, it is ensured that plant owners can rely on a future-proof system based on PROFIBUS The PROFIdrive application profile provides the today and can change to PROFINET at any time. foundation for almost every drive task in the field The requirements mainly include the functions for of industrial automation engineering. It defines the cyclic and acyclic data exchange, integration of device behavior and the procedure for accessing fieldbuses (PROFIBUS PA, HART, and FF), inte- drive data of electric drives and also optimally gration and parameter assignment of devices integrates the additional PROFIsafe and including Configuration in Run, diagnostics and PROFIenergy profiles. maintenance, redundancy, and time stamping.

PROFINET System Description 15 The cabling guide defines for all Conformance Classes a 2-pair cable according to IEC 61784-5- 3. The use of 4-pair cables is also allowed for transmission systems with Gigabit cabling requirements.

For a CA-A network, complete networking with active and passive components according to ISO/IEC-24702 is allowed, taking into considera- tion the CC-A cabling guide. Likewise, active infrastructure components (e.g., switches) accord- ing to IEEE 801.x can be used if they support the VLAN tag with prioritization.

Easy-to-understand and systematically structured instructions have been prepared to enable prob- lem-free planning, installation, and commissioning Figure 26: Example architecture for use of PROFI of PROFINET IO. These are available to any in- NET in process automation terested party on the PI-website. These manuals should be consulted for further information. The energy-limited bus feed of devices in hazard- ous areas on Ethernet has not been formulated as 10.1 Network configuration a requirement as there is already an ideal, proven solution with PROFINET PA. In addition, proven, The connection of PROFINET IO field devices field-tested Ethernet solutions currently do not occurs exclusively with switches as network com- exist for this. ponents. Switches typically integrated in the field device are used for this (with 2 ports assigned). PROFINET-suitable switches must support “auto- negotiation” (negotiating of transmission parame- 10. Network installation ters) and “autocrossover” (autonomous crossing of send and receive lines). As a result, communi- PROFINET is based on a 100 Mbps, full-duplex cation can be established autonomously, and Ethernet network. Faster communication is also fabrication of the transmission cable is uniform: possible on all transmission sections (e.g., be- only 1:1 wired cables can be used. tween switches, PC systems, or camera sys- tems). PROFINET supports the following topologies for Ethernet communication: PROFINET defines not only the functionality but also the passive infrastructure components  Line topology, which primarily connects ter- (cabling, connectors). Communication may take minals with integrated switches in the field place on copper or fiber-optic cables. In a Con- (Figure 27). formance Class A (CC-A) network, communica-  Star topology, which requires a central switch tion is also allowed over wireless transmission located preferably in the control cabinet. systems (Bluetooth, WLAN) (Table 4).  Ring topology, in which a line is closed to form a ring in order to achieve media redun- dancy.  Tree topology, in which the topologies indi- cated above are combined.

Network cabling and infrastructure components Solution Conformance class Passive network components (connector, cable) RJ45, M12 A, B, C Copper and fiber-optic transmission systems TX, FX, LX, A, B, C Wireless connections WLAN, Bluetooth A IT switch With VLAN tag according A to IEEE 802.x Switch with device function PROFINET with RT B Table 2: Network installation for different conformance classes Switch with device function and bandwidth reservation PROFINET with IRT C

Table 3: Network installation for different conformance classes

PROFINET System Description 16 The selection of suitable PROFINET plug connec- tors accords with the application. If the emphasis is on a universal network that is to be office- compatible, electrical data transmission is via RJ 45, which is prescribed universally for “Inside” environmental conditions. For the “Outside” envi- ronment, a push-pull plug connector has been developed that is also fitted with the RJ 45 con- nector for electrical data transmission. The M12 connector is also specified for PROFINET.

For optical data transmission with polymer optic fibers, the SCRJ plug connector, which is based on the SC plug connector, is specified. The SCRJ Figure 27: Ethernet networks in industrial environ- is used both in the “Inside” environment as well as ments usually have line topology in connection with the push-pull housing in the “Outside” environment. An optical plug connector is available for the M12 family and can be used for PROFINET and the 1 mm polymer optic fiber 10.2 Cables for PROFINET transmission (POF).

The maximum segment length for electrical data At the same time, the plug connectors are also transmission with copper cables between two specified for the power supply, depending on the nodes (field devices or switches) is 100 m. The topology and the supply voltage. Besides the copper cables are designed uniformly in AWG 22. push-pull plug connector, a 7/8" plug connector, a The installation guide defines different cable hybrid plug connector, or an M12 plug connector types, whose range has been optimally adapted can also be used. The difference between these to general requirements for industry. Sufficient connectors lies in their connectable cross sections system reserves allow industry-compatible instal- and thus, their maximum amperages. lation with no limitation on transmission distance.

The PROFINET cables conform to the cable types 10.4 Security used in industry: For networking within a larger production facility  PROFINET Type A: Standard permanently- or over the Internet, PROFINET relies on a routed cable, no movement after installation phased security concept. It recommends a secu-  PROFINET Type B: Standard flexible cable, rity concept optimized for the specific application occasional movement or vibration case, with one or more upstream security zones.  PROFINET Type C: Special applications: for On the one hand, this unburdens the PROFINET example, highly-flexible, constant movement devices, and on the other it allows the security (trailing cable or torsion) concept to be optimized to changing security requirements in a consistent automation engineer- Due to their electrical isolation, the use of fiber- ing solution. optic cables for data transmission is especially suitable if equipotential bonding between individ- ual areas of the plant is difficult to establish. Opti- cal fibers also offer advantages over copper in the case of extreme EMC requirements. For fiber- Copper Fiber Optic optic transmission, the use of 1 mm polymer optic fibers (POF) is supported, whose handling con- IP 20 forms optimally to industrial requirements. Inside

10.3 Plug connectors IP 67 PROFINET has divided the environmental condi- Outside tions into just two classes. This eliminates unnec- essary complexity and allows for the specific re- quirements of automation. The PROFINET envi- Variant 14 Variant 5 D-coded Variant 14 Draft IEC 61076- Pas 61076-3-117 IEC 61076-3-106 IEC 61076-3- Pas 61076-3-117 3-101 ronmental classes for automation applications are AIDA Hybrid 24 Volt 101 AIDA subdivided into one class Inside protected envi- and Data ronments, such as in a control cabinet, and one Figures 27: PROFINET offers a range of industrial class Outside of control cabinets for applications connectors located directly in the field (Figure 28).

PROFINET System Description 17 Figure 28: Segmentation of automation network

The security concept provides for protection of 11.1 Technology support both individual devices as well as whole networks Device manufacturers that want to develop an from unauthorized access. In addition, there are interface for PROFINET IO have the choice of security modules that will allow networks to be developing field devices based on existing segmented and, thus, also separated and pro- Ethernet controllers. Alternatively, member com- tected from the safety standpoint. Only uniquely panies of PI offer many options for efficient identified and authorized messages will be al- implementation of a PROFINET IO interface. lowed to reach devices within such segments from outside (Figure 29). To make development of a PROFINET IO inter- face easier for device manufacturers, the PI Competence Center and member companies offer PROFINET IO basic technology (enabling tech- 11. PROFINET IO-Techno- nology). Consulting services and special devel- logy and Certification oper training programs are also available. Before starting a PROFINET IO development project, device manufacturers should always perform an PROFINET is standardized in IEC 61158. It is on analysis to determine whether internal develop- this basis that devices in industrial plants can be ment of a PROFINET IO device is cost-effective networked together and exchange data without or whether the use of a ready-made communica- errors. Appropriate quality assurance measures tion module will satisfy their requirements. are required to ensure interoperability in automa- tion systems. For this reason, PI has established More detailed information on this topic can be a certification process for PROFINET devices in found in the brochure “PROFINET Technology – which certificates are issued based on test reports The easy way to PROFINET”, which can be of accredited test labs. While PI certification of a downloaded from the PI website. field device was not required for PROFIBUS, the guidelines for PROFINET have changed such that any field device bearing the name PROFINET must be certified. Experience with PROFIBUS over the last 20 years has shown that a very high quality standard is needed to protect automation systems, plant owners, and field device manufac- turers.

PROFINET System Description 18 11.2 Tools for product develop- 11.3 Certification test ment A certification test is a standardized test proce- Device manufacturers are assisted by software dure that is performed by specialists whose tools when developing and checking their prod- knowledge is kept up to date at all times and who ucts. These tools are provided to members of PI are able to interpret the relevant standards un- at no additional charge. A GSD editor assists the equivocally. The test scope is described in binding manufacturer when creating the GSD file for its terms in a test specification for each laboratory. product. This GSD editor can be used to create The tests are implemented as so-called black box the proper files and check them. tests in which the tester is the first real user.

Likewise, PROFINET tester software is available All the defined test cases that are run through in a for testing PROFINET functionalities. The current certification test are field-oriented and reflect in- version supports testing of all Conformance dustrial requirements. This affords all users the Classes as well as IRT functions. The additional maximum possible security for use of the field security tester allows testing for secure function of device in a system. In very many cases, the dy- a field device, including under load conditions. namic behavior of a system can be simulated in the test laboratory. For detailed analysis, the Wireshark freeware tools can be used for problem-free interpretation PI awards the certificate to the manufacturer of individual PROFINET frames since the decod- based on the test report from an accredited test ing of PROFINET is already included in the stan- lab. A product must have this certificate in order dard version. use the PROFINET designation. For the plant manufacturer/owner, the use of certified products means time savings during commissioning and stable behavior during the entire service life. They therefore require certificates from their suppliers for the field devices used, in accordance with the utilized Conformance Class.

PROFINET System Description 19 12. PROFIBUS & PROFINET Technology development International (PI) PI has handed responsibility for technology de- velopment over to PNO Germany. The Advisory Board of PNO Germany oversees the develop- As far as maintenance, ongoing development, ment activities. Technology development takes and market penetration are concerned, open place in the context of more than 50 working technologies need a company-independent insti- groups with input from more than 500 experts tution that can serve as a working platform. This mostly from engineering departments of member was achieved for the PROFIBUS and PROFINET companies. technologies by the founding of the PROFIBUS Nutzerorganisation e.V. (PNO) in 1989 as a non- Technical support profit interest group of manufacturers, users, and institutions. The PNO is a member of PI PI supports more than 40 accredited PICCs (PROFIBUS & PROFINET International), an um- worldwide. These facilities provide users and ma- brella group which was founded in 1995. With its nufacturers with all manner of advice and support. 27 regional PI Associations (RPA) and approxi- As institutions of PI, they are independent service mately 1,400 members, PI is represented on providers and adhere to the mutually agreed every continent and is the world’s largest interest regulations. The PICCs are regularly checked for group for the industrial communications field (Fig- their suitability as part of an individually tailored ure 30). accreditation process. A list of the current ad- dresses can be found on the website.

Certification PI supports 10 accredited PITLs worldwide for the PI (PROFIBUS & PROFINET International) certification of products with a PROFIBUS or Regional PI PI Competence PI Test PI Training PROFINET interface. As institutions of PI, they Associations Centers Laboratories Centers are independent service providers and adhere to Technologies the mutually agreed regulations. The testing ser- vices provided by the PITLs are regularly audited in accordance with a strict accreditation process to ensure that they meet the necessary quality requirements. A list of the current addresses can Fieldbus based Ethernet based Automation Proxy Technology Automation be found on the website. Technology Technology Training The PI Training Centers have been set up with Figure 29: Structure of PROFIBUS & PROFINET In- the specific aim of establishing a global training ternational (PI) standard for engineers and technicians. The accreditation of the Training Centers and the experts that are based there ensures the quality 12.1 Tasks performed by PI of the training and, thus, the quality of the engi- neering and installation services for PROFIBUS The key tasks performed by PI are: and PROFINET. A list of the current addresses  Maintenance and ongoing development of can be found on the website. PROFIBUS and PROFINET. Internet  Promoting the worldwide use of PROFIBUS and PROFINET Current information on PI and the PROFIBUS and  Protection of investment for users and manu- PROFINET technologies is available on the PI facturers by influencing the standardization. website www.profibus.com or www.profinet.com.  Representation of the interests of members This includes, for example, an online product to standards bodies and associations. guide, a glossary, a variety of web-based training  Providing companies with worldwide techni- content, and the download area containing speci- cal support through PI Competence Centers fications, profiles, installation guidelines, and (PICC). other documents.  Quality control through product certification based on conformity tests at PI Test Labs (PITL).  Establishment of a worldwide training stan- dard through PI Training Centers (PITC).

PROFINET System Description 20 Space for your notes:

PROFINET System Description 21 Space for your notes:

PROFINET System Description 22

PROFINET System Description – Technology and Application

Version June 2011

Order number 4.132

Publisher PROFIBUS Nutzerorganisation e.V. PNO Haid-und-Neu-Str. 7 76313 Karlsruhe Germany Tel.: +49 (0)721 / 96 58 590 Fax: +49 (0)721 / 96 58 589 [email protected]

Exclusion of liability

PROFIBUS Nutzerorganisation has examined the contents of this brochure carefully. Nevertheless, errors can not be excluded. Liability of PROFIBUS Nutzerorganisation is excluded, regardless of the reason. The data in this brochure is checked periodically, however. Necessary corrections will be con- tained in subsequent versions. We gratefully accept suggestions for improvement.

Terms used in this brochure may be trade marks and their use by third parties for any purposes may violate the rights of the owner.

This brochure is not a substitute for the respective IEC standards, e.g. IEC 61158 and IEC 61784, and the associated specifications and guidelines of PROFIBUS & PROFINET International. In case of doubt, these documents take precendence.

© Copyright by PROFIBUS Nutzerorganisation e.V. 2011. All rights reserved.

Worldwide support with PI!

Belgium France Netherlands Russia Sweden Germany & Czech Republic Spain Norway Switzerland Austria Denmark UK

Finland Slovakia

Italy China

Ireland India

Poland Japan

Brazil Chile South-East-Asia Southern USA & Canada Australia Korea Middle-East Africa

More information & contact details: www.profibus.com/community

Regional PI Regional PI Associations represent PI around the world and are your perso- Associations nal local contacts. They are responsible for local marketing activities for purposes (RPA) of spreading PROFIBUS, PROFINET, and IO-Link, which include trade fair appearan- ces, seminars, workshops, and press conferences, as well as public relations activities.

PI Compe- The PI Competence Centers collaborate closely with the RPAs and are your irst point of contact tence Center when you have technical questions. The PICCs are available to assist you in the development (PICC) of PROFIBUS or PROFINET devices and the commissioning of systems, and they provide user support and training.

PI Training PI Training Centers support users and developers in gaining experience with the PRO- Center FIBUS and PROFINET technologies and their possible uses. Individuals who successfully (PITC) complete the inal exam of the Certiied Installer or Engineer course receive a certiicate from PI.

PI Test Labs PI Test Labs are authorized by PI to conduct certiication tests for PROFIBUS and PROFI- (PITL) NET. You receive a certiicate from PI for your product once it passes the test. The certii- cation program plays a major role in the sustainable quality assurance of products and thus assures that the systems in use exhibit a high level of trouble-free operation and availability.

PROFIBUS Nutzerorganisation e. V. (PNO) Member of PROFIBUS & PROFINET International Haid-und-Neu-Str. 7 • 76131 Karlsruhe Fon +49 721 96 58 590 • Fax +49 721 96 58 589 www.profibus.com • www.profinet.com