Endress+Hauser Profibus Planing Guide

Guidelines for planning and commissioning
PROFIBUS DP/PA
Field Communication
BA 034S/04/en/06.04 Nr. 56004242
PROFIBUS planning and commissioning
Table of Contents
Revision History . . . . . . . . . . . . . . . . . 3 Registered Trademarks . . . . . . . . . . . . 3 1
1.1 1.2 1.3
5
5.1 5.2 5.3 5.4
PROFIBUS PA Planning . . . . . . . . . . . . . 50
Selection of the segment coupler . . . . . . . . . . . . . . Cable type and length . . . . . . . . . . . . . . . . . . . . . . Current consumption . . . . . . . . . . . . . . . . . . . . . . . Voltage at last device . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Worst case calculation . . . . . . . . . . . . . . . . 5.4.2 Accurate calculation . . . . . . . . . . . . . . . . . Calculation examples for bus design . . . . . . . . . . . . 5.5.1 Example 1: Non-hazardous application . . . 5.5.2 Example 2: EEx ia application . . . . . . . . . . 5.5.3 Example 3: EEx ib application . . . . . . . . . . 5.5.4 Example: fieldbus barrier application . . . . . Data quantity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Addressing and cycle times . . . . . . . . . . . . . . . . . . 5.7.1 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . 5.7.2 Cycle times . . . . . . . . . . . . . . . . . . . . . . . . 5.7.3 Example 1: Siemens segment coupler . . . . . 5.7.4 Example 2: Pepperl+Fuchs SK1 coupler . . . 5.7.5 Example 3: Pepperl+Fuchs SK2 coupler . . . 5.7.6 Example 4: Siemens PA link . . . . . . . . . . . . 50 51 52 54 54 55 56 56 58 60 63 64 68 68 68 69 70 71 73
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Conventions and icons . . . . . . . . . . . . . . . . . . . . . . 6 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.5
2
2.1
Introduction to PROFIBUS . . . . . . . . . . . . 8
PROFINET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.1.1 Component-based Automation . . . . . . . . . 10 2.1.2 I/O integration . . . . . . . . . . . . . . . . . . . . . 12 PROFIBUS DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.2.1 Transmission standards . . . . . . . . . . . . . . . 15 2.2.2 PROFIBUS DP communication protocol . . . 16 2.2.3 Application profiles . . . . . . . . . . . . . . . . . . 19 2.2.4 PROFIsafe . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.2.5 PROFIdrive . . . . . . . . . . . . . . . . . . . . . . . . 20 2.2.6 Integration technologies . . . . . . . . . . . . . . 21 2.2.7 Quality assurance . . . . . . . . . . . . . . . . . . . 21 PROFIBUS PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2.3.1 Operating principle . . . . . . . . . . . . . . . . . . 24 2.3.2 Applications in hazardous areas . . . . . . . . . 25 Field Device Tool (FDT) . . . . . . . . . . . . . . . . . . . . 26 5.6 5.7
2.2
6
6.1 6.2 6.3 6.4 6.5 6.6
Installation PROFIBUS PA . . . . . . . . . . . 74
Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Grounding and shielding . . . . . . . . . . . . . . . . . . . . Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overvoltage protection . . . . . . . . . . . . . . . . . . . . . . Installation of the devices . . . . . . . . . . . . . . . . . . . . Setting addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.1 Using DIP switches . . . . . . . . . . . . . . . . . . 6.6.2 Software addressing with FieldCare . . . . . . 6.6.3 Software addressing with Commuwin II . . . 74 75 79 79 80 82 82 83 84
2.3
2.4
3
3.1 3.2 3.3 3.4 3.5
PROFIBUS DP basics . . . . . . . . . . . . . . . . 29
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bus access method . . . . . . . . . . . . . . . . . . . . . . . . Network configuration . . . . . . . . . . . . . . . . . . . . . Applications in hazardous areas . . . . . . . . . . . . . . . 29 31 34 35 36
7
7.1
System Integration . . . . . . . . . . . . . . . . . . 85
Network configuration . . . . . . . . . . . . . . . . . . . . . . 85 7.1.1 Tested systems . . . . . . . . . . . . . . . . . . . . . . 86 Device database files (GSDs) . . . . . . . . . . . . . . . . . 87 7.2.1 GSD file example . . . . . . . . . . . . . . . . . . . . 89 7.2.2 Full configuration with manufacturer-specific GSDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 7.2.3 Partial configuration with manufacturer-specific GSDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 7.2.4 Profile GSD . . . . . . . . . . . . . . . . . . . . . . . . 93 Cyclic data exchange . . . . . . . . . . . . . . . . . . . . . . . 94 7.3.1 Status codes: Device status BAD . . . . . . . . 95 7.3.2 Status code: Device status UNCERTAIN . . . 96 7.3.3 Status codes: Device status GOOD . . . . . . . 97 Bus parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 7.4.1 Aligning FieldCare . . . . . . . . . . . . . . . . . . 100 7.4.2 Aligning Commuwin II . . . . . . . . . . . . . . 100 7.4.3 Commissioning the Pepperl+Fuchs SK2 . . 101 7.4.4 Watch Dog Time TWD . . . . . . . . . . . . . . . . . . 103
4
4.1 4.2
PROFIBUS PA Basics . . . . . . . . . . . . . . . . 38
Synopsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Segment coupler and links . . . . . . . . . . . . . . . . . . . 4.2.1 Segment coupler . . . . . . . . . . . . . . . . . . . . 4.2.2 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bus access method . . . . . . . . . . . . . . . . . . . . . . . . 4.4.1 Segment coupler . . . . . . . . . . . . . . . . . . . . 4.4.2 Gateway-type segment coupler . . . . . . . . . 4.4.3 Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Configuration . . . . . . . . . . . . . . . . . . . . . FISCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fieldbus multi-drop barriers . . . . . . . . . . . . . . . . . . 38 39 40 40 41 44 44 45 46 47 48 49
7.2
4.3 4.4
7.3
4.5 4.6 4.7
7.4
Endress+Hauser
8
8.1 8.2
Device Parametrization . . . . . . . . . . . . 104

PROFIBUS PA block model . . . . . . . . . . . . . . . . . PROFIBUS PA profile . . . . . . . . . . . . . . . . . . . . . 8.2.1 Block structure . . . . . . . . . . . . . . . . . . . . 8.2.2 Device management . . . . . . . . . . . . . . . . 8.2.3 Transmitter and actuator blocks . . . . . . . 8.2.4 Analysis devices . . . . . . . . . . . . . . . . . . . 8.2.5 Function overview . . . . . . . . . . . . . . . . . FieldCare Asset Management . . . . . . . . . . . . . . . 8.3.1 Using FieldCare . . . . . . . . . . . . . . . . . . . 8.3.2 Generation of a live list . . . . . . . . . . . . . . 8.3.3 Device parametrization . . . . . . . . . . . . . . 8.3.4 On-line parametrization . . . . . . . . . . . . . 8.3.5 Plant View . . . . . . . . . . . . . . . . . . . . . . . Commuwin II Operating Program . . . . . . . . . . . . 8.4.1 Operation . . . . . . . . . . . . . . . . . . . . . . . . 8.4.2 Device menu . . . . . . . . . . . . . . . . . . . . . 105 106 108 109 110 113 114 116 117 118 118 119 119 120 120 121
8.3
8.4
9
9.1 9.2 9.3 9.4
Trouble-Shooting . . . . . . . . . . . . . . . . . 122
Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . PLC planning . . . . . . . . . . . . . . . . . . . . . . . . . . . Data transmission . . . . . . . . . . . . . . . . . . . . . . . . Commuwin II . . . . . . . . . . . . . . . . . . . . . . . . . . 122 123 123 124
10
10.1 10.2
Technical Data . . . . . . . . . . . . . . . . . . . . 125

PROFIBUS DP . . . . . . . . . . . . . . . . . . . . . . . . . . 125 PROFIBUS PA . . . . . . . . . . . . . . . . . . . . . . . . . . 126
11
11.1 11.2 11.3 11.4 11.5
PROFIBUS Components . . . . . . . . . . . 127

Endress+Hauser field devices PROFIBUS PA . . . . Endress+Hauser field devices PROFIBUS DP . . . . Network components . . . . . . . . . . . . . . . . . . . . . Asset management and operating software . . . . . Supplementary documentation . . . . . . . . . . . . . . 127 153 160 162 163
12
12.1 12.2 12.3 12.4
Terms and Definitions . . . . . . . . . . . . . 164

Bus architecture . . . . . . . . . . . . . . . . . . . . . . . . . Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . Miscellaneous terms . . . . . . . . . . . . . . . . . . . . . . 164 165 166 167
13
13.1 13.2 13.3
Appendix: Calculation Sheets . . . . . . 168

Explosion hazardous areas EEx ia . . . . . . . . . . . . 168 Explosion hazardous areas EEx ib . . . . . . . . . . . . 170 Non-hazardous areas . . . . . . . . . . . . . . . . . . . . . 172
Endress+Hauser
Revision History
Issue BA198F/00/en/11.99 BA034S/04/en/07.04 Changes Original Version Revision of manual to include latest information on PROFIBUS standard Additional descriptions of new components Revision of device techniical data
Registered Trademarks
PROFIBUS is a registered trademark of PROFIBUS User-Organisation e.V., Karlsruhe, Germany Microsoft, Windows, Windows NT, Windows 2000,Windows XP are registered trademarks of Microsoft Corporation, Redmond, Washington, USA
Endress+Hauser
Endress+Hauser
1 Safety
1
1.1
Approved usage
Safety
General
These guidelines have been written with the view of giving the potential PROFIBUS user an introduction to the planning and commissioning of a PROFIBUS PA network. They are based on the experience of Endress+Hauser employees who have been actively involved in PROFIBUS projects and who, in the meantime, have successfully commissioned a large number of plants. The approved usage of the individual devices that are used in a network can be taken from the corresponding device operating instructions.
Installation, commissioning, operation
The field devices, segment coupler, cables and other components must be designed to operate safely in accordance with current technical safety and EU standards. If installed incorrectly or used for applications for which they are not intended, it is possible that dangers may arise. For this reason, the system must be installed, connected, operated and maintained according to the instructions in this and other relevant manuals: personnel must be authorised and suitably qualified.
Explosion hazardous area
If the system is to be installed in an explosion hazardous area: Ensure that all personnel are suitably qualified Observe the specifications in the certificate Observe any national and local regulations. For PROFIBUS PA, it is recommended components should be designed in accordance with the FISCO model. This greatly simplifies the acceptance testing of the PROFIBUS PA segment. Where another scheme is used, e.g. Exe/Exi multibarriers, proof of intrinsic safety must be furnished.
Endress+Hauser
1 Safety
1.2
Conventions and icons
In order to highlight safety relevant or alternative operating procedures in the manual, the following conventions have been used, each indicated by a corresponding icon in the margin. Safety conventions . Icon
Meaning A note highlights actions or procedures which, if not performed correctly, may indirectly affect operation or may lead to an instrument response which is not planned
Caution! Caution highlights actions or procedures which, if not performed correctly, may lead to personal injury or incorrect functioning of the instrument Warning! A warning highlights actions or procedures which, if not performed correctly, will lead to personal injury, a safety hazard or destruction of the instrument
Explosion protection
. Icon
Meaning Device certified for use in explosion hazardous area If the device has this symbol embossed on its name plate it can be installed in an explosion hazardous area in accordance with the specifications in the certificate or in a safe area Explosion hazardous area Symbol used in drawings to indicate explosion hazardous areas. Devices located in and wiring entering areas with the designation explosion hazardous areas must conform with the stated type of protection Safe area (non-explosion hazardous area) Symbol used in drawings to indicate, if necessary, non-explosion hazardous areas. Devices located in safe areas stiill require a certificate if their outputs run into explosion hazardous areas.
Electrical symbols
. Icon
Meaning Direct voltage A terminal to which or from which a direct current or voltage may be applied or supplied
Alternating voltage A terminal to which or from which an alternating (sine-wave) current or voltage may be applied or supplied Grounded terminal A grounded terminal, which as far as the operator is concerned, is already grounded by means of an earth grounding system Protective grounding (earth) terminal A terminal which must be connected to earth ground prior to making any other connection to the equipment Equipotential connection (earth bonding) A connection made to the plant grounding system which may be of type e.g. neutral star or equipotential line according to national or company practice
Endress+Hauser
1 Safety
1.3
Documentation
The guidelines are structured as follows:

Chapter Chapter 1 Title Introduction Content Advantages of a bus as well as general information about the PROFIBUS standard An overview of PROFIBUS standards for factory and process automation Information about PROFIBUS DP Information about PROFIBUS PA, couplers, links and use in explosion hazardous areas (FISCO-Model) What must be observed when planning PROFIBUS DP/PA systems, with examples Notes on the installation of devices in a PROFIBUS DP/PA system Notes on mapping PROFIBUS PA devices in a PLC General information on setting the parameters in Endress+Hauser devices PROFIBUS applications Causes and remedies for general faults that may occur during the commissioning of a system Principle technical data of PROFIBUS PA and PROFIBUS DP Profiles of the Endress+Hauser PROFIBUS DP and PROFIBUS PA devices Explanation of the terminology used to describe bussystems Calculation sheets for your applications
Chapter 2
Introduction PROFIBUS
Chapter 3 Chapter 4
PROFIBUS DP Basics PROFIBUS PA Basics
Chapter 5
PROFIBUS PA Planning
Chapter 6
PROFIBUS PA Installation
Chapter 7 Chapter 8
System Integration Device Configuration
Chapter 9
Trouble-Shooting
Chapter 10 Chapter 11
Technical Data PROFIBUS Components
Chapter 12 Chapter 13
Terms and Definitions Appendix
Endress+Hauser
2 Introduction to PROFIBUS
Introduction to PROFIBUS
PROFIBUS is a standardized, open communications system for all areas of application in factory and process automation. The technology was introduced in the early 1990s and has been developed continuously ever since. The PROFIBUS DP and PROFIBUS PA technologies are specified in the international standards EN 50170 and IEC 61158 and are suitable for replacement of discrete and analog signals in control systems. PROFIBUS DP The original specification was aimed primarily at the requirements of Factory Automation, but this was quickly extended to include the requirements of process automation, in particular the need for intrinisically safe bus powering of devices. This is mirrored in the PROFIBUS PA specifications. As its popularity increased, the PROFIBUS DP specifications were extended to include a number of common but optional application profiles for e.g. safety, time stamping etc.. Similarly several application profiles were developed to meet the needs of specific device types, e.g. measuring devices, drives, remote I/O etc.. By the turn of the century, the PROFIBUS DP/PROFIBUS PA standard had covered many of the requirements of both Factory and Process Automation from field to control level - as shown by Fig. 2-1. It was rewarded by a large degree of support from both equipment manufactures and users, and today has an installed base of over 10,000,000 I/0 points.
ES Internet OPERATIONS: PROFINET
OS
Ethernet TCP/IP
PLC
IPC
RS-485/FO
MBP (IEC 61158-2)
12:00
14:00
16:00
18:00
20:00
22:00
HART, ASi FACTORY: PROFIBUS DP PROCESS: PROFIBUS DP
Fig. 2-1: Overview of PROFIBUS technologies
PROFINET
At this point in time, however, Ethernet had already begun to work its way down from the office environment on to the factory floor, and was being seen as the future standard for control system backbones. Office Ethernet is in itself not suitable for control systems, since media access is stochchastic (CSMA/CD), not deterministic, so there was a need to develop a further standard for the operations level. The result is the PROFINET specification, which not only addresses the problems of deterministic control for real time and isochronic real time applications, but also those of network engineering, operation and I/O integration of control and fieldbus networks. PROFINET is only just at the beginning of its development, but promises many exciting solutions for the future. PROFIBUS is supported by PROFIBUS International, which is a world-wide association of PROFIBUS user organisations. It is responsible for the development of the standard, its maintenance, the conformance testing of PROFIBUS devices as well as the issuing of device certificates. It has a number of independent accredited PROFIBUS Competence Centers thoughout the world (one is located Endress+Hauser Process Solutions AG) which maintain test facilities that are accessible for users and offer training courses for prospective PROFIBUS engineers.
PROFIBUS User Organisations
Endress+Hauser
2.1
PROFINET
As can be seen from Fig. 2-1, PROFINET is the Ethernet-based automation standard of PROFIBUS International. It intended for use in a wide range of industrial applications, for example in: Production systems Assembly systems Systems in the automotive industries Systems in the food and beverage industries Packaging systems
PROFINET allows the implementation of distributed automation structures, integration of simple decentralized field devices as well as the operation of motion control applications. As can be seen in Fig. 2-2, each of these applications places different demands on the system with regard to response times and real time operation.
Internet
Controller and HMI
Field Devices
Motion Control
100ms TCP/IP Real Time
10ms
<1ms Isochronic Real Time Real Time
Fig. 2-2: PROFINET allows the parallel operation of several "Control Islands" via Ethernet TCP/IP
PROFINET recognises this fact and provides a modular solution which treats each application as a separate "Control Island". Such islands might be for example, a SCADA system for monitoring and operating the plant, a control network for flow, ratio and level control of a reactor, a complete filling machine or an industrial robot. PROFINET specifies those functions that allow implementation of an integrated automation solution from network installation to web-based diagnosis. The modular structure of PROFINET permits extremely easy expansion. PROFINET operates over a high speed (100 Mbit/s) switched Ethernet TCP/IP backbone. This ensures: Full duplex communication Isochronous communication Priorization of Real-Time Frames (Quality of Service) A specially developed PROFINET chip enables switch integration into a device and controller. The specification itself has two facets: PROFINET CbA (Component-based Automation) PROFINET I/O (Integration of PROFIBUS devices in PROFINET) These are discussed in more detail in the following sections
Endress+Hauser
2.1.1
Component-based Automation
Component-based Automation is best explained by taking the practical example that PROFIBUS International uses in its own presentations, that of bottling in brewing or soft drinks production. The bottling is done by a number of machines that wash, fill, close and pack the bottles. Prior to this the product must be manufactured, a classical process control application. Fig. 2-3 illustrates the task in question.
Horizontal integration along the production line
Production
Machine 1
Machine 2
Machine 3
Wash
Fill
Close
Pack
Data exchange between intelligent devices within the machine

Fig. 2-3: Schematic diagram of automation tasks in a brewery or soft drinks plant
Network architecture
The network architecture depends on the nature of the processes involved and the demands they make on control. Typically, however, the closing and packing of bottles are purely factory automation tasks requiring isochronous real time communication, washing and filling are hybrid tasks and the production of the beer or soft drink is a process automation task. Fig. 2-4 illustrates the type of architecture to be expected, the production process being a PROFIBUS DP/PA task and the washing and filling a typical PROFIBUS DP task today.
Machine 2 Engineering ES Close
Machine 3
Pack
Ethernet
PROXY PROFIBUS DP/PA Production Mash Filter Ferment
PROXY PROFIBUS DP Machine 1 Wash Fill
Fig. 2-4: Possible plant architecture for brewery or soft drinks plant
Technological module
PROFINET considers machines and systems to be divided into technological modules, each of which comprises of mechanical, electrical and software components. The functionality of the technological modules is encapsulated in the form of PROFINET components. These have standard interfaces for use in a PROFINET engineering tool. They can be used as building blocks, combined as required and are easily reused. The PROFINET components for all technological modules in a machine or component assembly are supplied by the manufacturer. on e.g. a CD-ROM.
10
Endress+Hauser
CbA engineering
The technological modules are basically Global Function Blocks for the machine or component assemblies in the plant and can be used within a PROFINET Engineering Tool to build up a logical view of the plant. The standard interfaces allow the logical sequences to be programmed in a graphical environment. Thus for instance, a connection between the "Finished" output of one machine to the "Start" input of another, will cause the appropriate message to be sent over Ethernet and the downstream machine will start up when the upstream machine has finished its task.
Manufacturer's programming and configuration tools Component Editor Interface PROFInet Configuration Editor
Manfacturer A
Manfacturer B
Component Editor Interface
Manfacturer C
Component Editor Interface
Fig. 2-5: Machine and component assembly manufacturers deliver standardised function blocks for their equipment
The Engineering Tool is also used to build up a view of the the PROFINET and PROFIBUS network, the technical modules forming the link between the two views. When the tool goes on-line, i.e. the various components are connected physically to the network, the logical project is downloaded to the connected machines and devices. The system can then be started up with preconfigured links.
Machine 2
Machine 3
Close Download
Pack
PROXY
PROXY
Production Mash Filter Ferment
Machine 1 Wash Fill
Fig. 2-6: The links are downloaded to the machines and the system is ready for start-up
Endress+Hauser
11
2.1.2
PROFINET I/O devices
I/O integration
PROFINET allows direct interfacing of decentralized field devices on Ethernet. This supports flat communication hierarchies in automation. All the devices used are connected in a consistent network structure and therefore provide open communication throughout the entire production system. PROFINET defines three types of I/O device: I/O controller, the device containing the control program and managing data exchange to assigned field devices I/O device, the field device connected to the I/O controller I/O supervisor, the HMI and diagnostic station Fig. 2-7 shows the types of data that are exchanged between the three components.
I/O Supervisor e.g. SCADA or Configuration Diagnosis Up/Download
I/O Controller e.g. PLC
Ethernet
Configuration Production Data Alarms
Diagnostic Status control Parametrization
I/O Device Field Device
Fig. 2-7: Data exchange between PROFINET I/O devices
PROFINET communication
In order to achieve the very short response times required in motion control a special ASIC chip is available. The communication stack is shown in Fig. 2-8.
IT applications
HTPP SMNP DHCP...
PROFIBUS applications Standard data UDP Real-time data
IP RT Ethernet
Real-time
TCP
IRT
Real Time
Real Time Switch ASIC
Fig. 2-8: PROFIBUS communication stack
12
Endress+Hauser
It can be seen that PROFINET uses Ethernet at three performance levels for communcation between I/O devices: Engineering and time-uncritical data are transferred via TCP/IP and DCOM. For time-critical process data, e.g. alarms, a real-time channel is available(RT). It is implemented as software based on available controllers. For motion control isochronous real-time communication (IRT) is available which allows jitter accuracy of 1 s at a clock rate of 1 ms. The integration of existing field bus applications is accomplished with the proxy concept. The proxy is the representative of the field bus devices on the PROFINET, see Fig. 2.4. The network management covers all the functions for the administration of PROFINET devices in Ethernet networks: Device and network configuration, e.g. issue of IP parameters based on standards like DHCP; Network diagnosis based on standards like SNMP Integration of Web functions, e.g. access to components by means of standard technologies from the Internet field such as HTTP, XML, HTML and addressing with scripting. Field device integration The signals from the (PROFIBUS DP/PA) field devices (decentralized peripherals) are processed directly in the assigned controller. The controller communicates with other PROFINET I/O devices via a proxy. Devices are integrated in the controller by means of standard GSD files. Integration of the decentralized field devices is an in the PROFINET system is optional add-on to distributed automation. Here a special GSD file, GSDML written in XML is used for integration. A combination of the standard and top-level integration can be implemented in a PROFINET network at any time. Installation The specific requirements for Ethernet networks in an industrial environment are: System-specific cable routing Specific degree of networking for each machine/system Linear network structures Rough industry-compatible cables and connectors with special requirements fulfilled in terms of EMC and temperature.
PROFINET installations are based on these principles and provide the device manufacturer with clear specifications for device interfaces and the wiring for them. The PROFINET Installation Guide provides the system manufacturer/operator with simple rules for the installation of Ethernet networks. More information on PROFINET can be found at www.profibus.com.
Endress+Hauser
13
2.2
PROFIBUS DP
Weighing & Dosing
Application Profiles II PA Devices Indent Systems RIO for PA PROFIdrive
Integration Technologies
- Description (GSD, EDD) - Tools (DTM, Cofigurators)
Encoder
Application Profiles I Communication Technologies
Common Application Profiles (optional):

- Master Conformance Classes - Interfaces (Comm-FB, FDT, etc.) - Constraints
PROFISAFE, Time Stamp, Redundancy, etc.

IEC 61158/61784
PROFIBUS DP
DP-V0...V2
RS485: RS485-IS: NRZ Intrinsic Safety Fiber: Optics: Glass Multi Mode Glass Single Mode PCF / Plastic Fiber MBP *): MBP-LP: MBP-IS: Manchester Bus Powered Low Power Intrinsic Safety
Transmission Technologies
Fig. 2-9: Overview of PROFIBUS standards
Fig. 2-9 gives an overview of PROFIBUS DP system standards: DP stands for Decentralised Periphery. The standards comprise the following groups: Transmission Technology PROFIBUS signal transmission is based on the RS-485, fibre optics or IEC 61158-2 standards. In the latest literature the latter is also referred to as MBP or MBP-IS (Manchester Bit Protocol). Communication Technology The PROFIBUS DP communication protocol is at the core of the standard. It is available in three variants, DP-V0, DP-V1 and DP-V2. Common Application Protocols A set of optional protocols for network management. Device Application Protocols A set of protocols for particular device types or applications, e.g. measuring devices or motion control. Integration Technology These standards determines how field devices can be integrated into PROFIBUS systems. System Profiles Contain specifications regarding conformance classes, interfaces and constraints. The standards of interest to process automation are described in the following sections. Table 2.1 gives an overview of where these are used.
Target Application Factory Automation Motion Control Process Automation PROFIBUS PA PA device PROFIBUS DP protocol RS-485 MBP-IS Safety
Typical designation Application profile Communication
PROFIBUS DP None or specific PROFIBUS DP protocol RS-485
PROFIdrive PROFIdrive PROFIBUS DP protocol RS-485
PROFIsafe PROFIsafe PROFIBUS DP protocol RS-485 MBP-IS
Transmission
Table 2-1: Target applications and typical use of PROFIBUS standards
14
Endress+Hauser
System Profiles 1...x
SEMI
2.2.1
Transmission standards
PROFIBUS provides for three different transmission technologies, RS-485, Fibre Optics and MBP (Manchester Coding/Bus Powered). Both RS-485 and IEC 61158-2 make provision for intrinsically safe transmission in hazardous areas. RS-485 RS-485 is used for tasks that require high transmission rates. The transmission technology is simple and cost-effective: no expert knowledge is required for installation of the cable. STP copper cable (shielded, twisted pairs) with one conductor pair is used. RS-485 allows a bus structure to be built that allows addition or removal of stations or the step-by-step commissioning of the system without influencing other stations. Subsequent expansions (within defined limits) have no effect on stations already in operation. The transmission rate can be set between 9.6 Kbit/s and 12 Mbit/s, however, all PROFIBUS DP within a system must operate at the same rate. Up to 32 stations (master or slaves) can be connected to a single segment. If more than 32 stations are required, repeaters may be used. The maximum permissible line length depends on the transmission rate. Four RS-485 cable types (Types A - D) for designed for different applications are available on the market. PI recommends the use of cable type A. More details on designing networks are to be found in Chapter 3. RS-485 IS RS-485 IS is a recent innovation in response to an increasing market demand for the use of RS-485 in explosion-hazardous areas. A corresponding PROFIBUS guideline is now available that specifies the configuration of intrinsically safe RS-485 solutions with simple device interchangeability. It details the current and voltage levels that must be adhered to by all stations in order to ensure safe functioning during interconnection. When active sources are connected, the sum of the currents of all stations must not exceed the maximum permissible current allowed by the circuitry. In contrast to the FISCO model (see below), all stations represent active sources. Up to 32 stations can be connected to the intrinsically safe bus circuit. IEC-61158-2 physical layer describes several connection technologies. PROFIBUS uses only one: MBP ("Manchester Coding" and "Bus Powered"). To avoid confusion, PROFIBUS International has decided to use MBP in all its literature in future. MBP is synchronous transmission at a defined transmission rate of 31.25 Kbit/s using Manchester coding. It is used in process automation as it also satisfies the key demands for intrinsic safety and two-wire bus power. MBP transmission technology is usually limited to specific segments within a plant, which are then linked to a RS485 segment via a segment coupler or link, see Chapter 4. Tree or line structures (and any combination of the two) are network topologies supported by PROFIBUS with MBP transmission with up to 32 stations per segment and max. 126 per network. FISCO Model The FISCO model (Fieldbus Intrinsically Safe Concept) considerably simplifies the planning, installation and expansion of PROFIBUS networks in explosion-hazardous areas. It stipulates that a network is intrinsically safe and requires no individual intrinsic safety calculations provided the four relevant bus components (field devices, cables, segment couplers and bus terminators) fall within predefined voltage, current, output, inductance and capacity limits. The corresponding proof is provided by certification of the components through authorized accreditation agencies, such as PTB and BVS (Germany) or UL and FM(USA). When FISCO-approved devices are used, not only is it possible to operate more devices on a single line, but the devices can also be replaced or the line can be expanded during operation without the need for time-consuming calculations or system certification. MBP with FISCO model is sometimes referred to as MBP-IS. Fiber optic transmission is used for fieldbus applications that preclude the use of copper wires, e.g. for environments with very high electromagnetic interference or when particularly large distances need to be covered. PROFIBUS guideline (2.021) for fiber optic transmission specifies the technology available for this purpose, including multimode and single mode glass fiber, plastic fiber, and HCS fiber. When determining these specifications, great care was naturally taken to allow problem-free integration of existing PROFIBUS devices in a fiber optic network without the need to change the protocol behavior of PROFIBUS. This ensures backward compatibility with existing PROFIBUS installations.
MBP
Fiber optics
Endress+Hauser
15
2.2.2
PROFIBUS DP communication protocol
PROFIBUS DP is designed for fast data exchange at control and field level. The exchange of data with distributed devices is primarily cyclic and the associated communication functions are specified by the basic PROFIBUS DP protocol (version DP-V0). The special demands of particular applications have meant that the basic functionality has been gradually expanded, so that now three versions are available: DP-V0, DP-V1 and DP-V2. All versions are specified in IEC 61158. System configuration and device types DP supports implementation of both mono-master and multi-master systems. This affords a high degree of flexibility during system configuration. A maximum of 126 devices (masters or slaves) can be connected to a bus. In mono-master systems, only one master is active on the bus during operation of the bus system. The device types are as follows: DP master class 1 (DPM1) is a central controller that cyclically exchanges information with the distributed stations (slaves) at a specified message cycle. Typical DPM1 devices are programmable logic controllers (PLCs) or PCs. A DPM1 has active bus access with which it can read measurement data (inputs) of the field devices and write the setpoint values (outputs) of the actuators at fixed times. This continuously repeating cycle is the basis of the automation function. DP master class 2 (DPM2) are engineering, configuration or operating devices. They are implemented during commissioning and for maintenance and diagnostics in order to configure connected devices, evaluate measured values and parameters and request the device status. A DPM2 does not have to be permanently connected to the bus system. The DPM2 also has active bus access . Slaves are peripherals (I/O devices, drives, HMIs, valves, transducers, analyzers) that read in process information and/or use output information to intervene in the process. There are also devices that solely process input information or output information. As far as communication is concerned, slaves are passive devices, they only respond to direct queries. This behavior is simple and cost-effective to implement (in the case of DP-V0 it is already completely included in the hardware). Figure 2-10 shows the system configuration of a mono-master system. The PLC is the central control component. The slaves are decentrally coupled to the PLC over the transmission medium. This system configuration enables the shortest bus cycle times. In multi-master systems several masters are connected to one bus. They represent either independent subsystems, comprising one DPM1 and its assigned slaves, or additional configuration and diagnostic devices.
Controller Cyclic communication in master-slave relationship PROFIBUS DP
Fig. 2-10: Basic principle of Version DP-V0 in mono-master system
Version DP-V0
Version DP-V0 provides the basic functionality for a mono-master architecture with high-speed, deterministic master-slave communication, see Fig. 2-10, including: cyclic data exchange station, module and channel-specific diagnostics four different interrupt types for diagnostics and process interrupts pulling and plugging of stations.
The master can be a personal computer or programmable logic controller.
16
Endress+Hauser
Version DP-V1
Fig. 2-11 shows the standard architecture for PROFIBUS DP, Version DP-V1. This contains enhancements for process automation, in particular acyclic data communication for parameter assignment, operation, visualization and interrupt control of intelligent field devices from a so-called Class 2 master. In addition, it offer three additional interrupt types: status interrupt, update interrupt and a manufacturer-specific interrupt.
Class 1 master Controller
Medium access by token passing
Class 2 master e.g. Parametrization
Cyclic communication in master-slave relationship PROFIBUS DP
Coupler
Acyclic communication in master-slave relationship PROFIBUS PA
Fig. 2-11: Standard architecture for Version DP-V1
4...20 mA Intensor Mat. 1.4571 / Al3 O2 / FPM U 10,5 ... 45 V DC IP 65
Order Code XXXXXXXXXXXXXXXXXX Ser.-No. XX X XXXX
P min Span 100 mbar P max 20 bar
P -1 ... 2 bar
Patented
Cyclic and acyclic communication
Cyclic data communication between the DPM1 and its assigned slaves is automatically handled by the DPM1 in a defined, recurring sequence. The user defines the assignment of the slave(s) to the DPM1 when configuring the bus system. The user also defines which slaves are to be included/ excluded in the cyclic user data communication. Data communication between the DPM1 and the slaves is divided into parameterization, configuration and data transfer. Before the master includes a DP slave in the data transfer phase, a check is run during the parameterization and configuration phase to ensure the correct configuration. In addition to the station-related user data communication, which is automatically handled by the DPM1, the master can also send control commands to all slaves or a group of slaves simultaneously. These control commands are transmitted as multicast commands and enable sync and freeze modes for event-controlled synchronization of the slaves. For safety reasons, it is necessary to ensure that DP has effective protective functions against incorrect parameterization or failure of transmission equipment. For this purpose the DP master and the slaves are fitted with monitoring mechanisms in the form of time monitors. The monitoring interval is defined during configuration. Acyclic data communication is the key feature of version DP-V1. This forms the requirement for parameterization and calibration of the field devices over the bus during runtime and for the introduction of confirmed alarm messages. Transmission of acyclic data is executed parallel to cyclic data communication, but with lower priority. Addressing with slot and index is used both for cyclic and acyclic communication services. When addressing data, PROFIBUS assumes that the physical structure of the slaves is modular or can be structured internally in logical functional units, so-called modules. The slot number addresses the module and the index addresses the data blocks assigned to a module. Compact devices are regarded as a unit of virtual modules. These can also be addressed with slot number and index.
Endress+Hauser
17
Version DP-V2
Version DP-V2 contains further enhancements to DP-V1 and is geared towards the demands of drive technology. Due to additional functionalities, such as isochronous slave mode and lateral slave communication (DXB) etc., DP-V2 can also be implemented as a drive bus for controlling fast movement sequences in drive axes.
PROFIBUS DP Master Class 1
Output data
Input data via broadcast
Publisher e.g. light array Slave
Subscriber e.g. drive Slave
Subscriber e.g. drive Slave
Slave-to-slave communcation
Fig. 2-12: Slave-to-slave communication with Version DP-V2
The enhancements are as follows: Slave-to-Slave Communication enables direct, time-saving, communication between slaves without the detour over a master. Figure 2-12 shows the mechanism. On the command of the master, one slave acts as "publisher" and broadcasts its information to other slaves embedded in the sequence, the so-called "subscribers". This enables slaves to sense data from other slaves and use them as their own input. This not only opens up a new range of applications, it also reduces response times on the bus by up to 90 %. Isochronous mode enables clock synchronous control in masters and slaves, irrespective of the bus load. The function enables highly precise positioning processes with clock deviations of less than a microsecond. All participating device cycles are synchronized to the bus master cycle through a "global control" broadcast message. A special sign of life (consecutive number) allows monitoring of the synchronization. Clock control synchronizes all stations to a system time with a deviation of less than one millisecond. This allows the precise tracking of events. This is particularly useful for the acquisition of timing functions in networks with numerous masters. It facilitates the diagnostics of faults as well as the chronological planning of events. Upload and download allows the loading of any data area in a field device, irrespective of size, with a single command. This enables, for example, programs to be updated or devices replaced without the need for manual loading processes.
18
Endress+Hauser
2.2.3
Application profiles
PROFIBUS offers a range of application profiles that simplify its use in specific industries or applications. Profiles are manufacturer and user specifications that determine properties, performance features and behavior for a particular set of devices or system. They take into account application, field device type characteristics, control features and the means of integration (engineering). Conformance with the profile facilitates device interoperability and interchangeability. A profile may encompass only a few specifications for a specific device class or extend to a set of comprehensive application specifications for a specific industry. PROFIBUS makes a distinction between common application profiles with implementation options for different applications, application profiles and system and master profiles. The common profiles include, for example, PROFIsafe, Redundancy and Time Stamp. PROFIdrive, SEMI or PA Devices are examples of application profiles. The system and master profiles describe the system performance that is available to field devices. A short description of PROFIsafe and PROFIdrive follows this section. More information on the other profiles can be found on the PROFIBUS web site www.profibus.org.
2.2.4
PROFIsafe
PROFIsafe is an optional, common application profile that allows safety-relevant devices to be connected to the same single transmission line as standard devices. These then communicate with an additional safety programmable logic controller or a combined standard/safety-controller. For applications such as presses, saws, robots, chemical processes, burners etc., special precautions are necessary to avoid risk to operators, environment or investment. Traditionally, safety systems are hard-wired, i.e. based on relays or a similar trusted and tangible technology. In recent years, however, safety automation has seen an influx of microcontrollers, software and communication networks, which have now been proven in use in millions of applications. The basis for their use is laid down in international safety standard IEC 61508. This details the measures required for the detection and management of errors and failures, together with the description of systematic software development processes. PROFIsafe merges standard automation and safety automation in one technology, thus providing higher efficiency to the user. It is available in products such as programmable and numerical controllers, remote I/Os, laser scanners, light curtains, motor starters, frequency converters, drives, gas and fire sensors etc.. Its safety measures are added to the device as a safety layer on top of the existing PROFIBUS layers in the communication stack. This layer is responsible for the transmission of safety relevant process data (safety application) as well as the unchanged existing standard application for non-safety critical functions, like e.g. diagnosis. PROFIsafe uses single-channel transfer and its error detection mechanisms are totally independent of the underlying PROFIBUS DP (black channel principle). The safety data are packed in the PROFIBUS telegram frame as a supplement to the standard data. This is then passed completely unmodified from a (safety) sender to a (safety) receiver no matter what kind of transmission system is used. Different industry requirements are taken into account. Factory automation deals with short signals processed at very high speed, while process automation involves longer process values that may take more time. PROFIsafe therefore offers two different process data lengths limited to a maximum of 12 bytes and 122 bytes respectively.
Endress+Hauser
19
2.2.5
PROFIdrive
PROFIdrive is an application profile that addresses the specific requirements of motion control. It utilises the new functions realised in PROFIBUS Version DP-V2: clock cycle synchronisation and slave-to-slave communication. PROFIdrive allows intelligent drives to be used in decentralised automation structures. Digital servo-drives can also be synchronised and position control loops can be closed via PROFIBUS. Drive application classes The integration of drives into automation solutions depends strongly on the task of the drive. To simplify use, PROFIdrive defines the following generic application classes: Standard drive In the simplest case, the drive is controlled via a main setpoint (e.g. rational speed) by PROFIBUS. The complete closed-loop speed control is carried out in the drive controller. The application case is employed primarily in the area of conventional drive technology, e.g. in conveying systems. Standard drive with technological function This class is a very flexible variant for realising automation applications. This involves breaking down the entire automation process into several small subprocesses. The automation functions are no longer located exclusively in the central automation drive but can be distributed in the drive controllers. In this respect, PROFIBUS serves as the technology interface. Distribution of automation functions assumes that communication is possible in all directions. Thus slave-toslave communication is required, e.g. between setpoint cascades, winders and applications for rotational speed synchronisation for continuous web processes. Positioning drive In addition to the drive controller, the drive also contains a position controller. Positioning tasks are forwarded to the drive controller and started by PROFIBUS. Position drives have a very wide scope of application, for example, the twisting on and off of lids in a bottling plant, or the positioning of knives in a foil-cutting maschine. Device model PROFIdrive defines a device model as it can be found - at least partly - in any drive system. The device comprises multiple functional modules which work together and thereby reflect the intelligence of the drive system. Objects are assigned to these functional modules, which then constitute the interface to the automation process. The objects are described and their functions defined in the profile. Parameters are assigned to the objects, which are collectively referred to as the "profile parameters". These include such functions as fault buffers, drive control, device identification, process data configuration and the overall parameter list. All other parameters, which can number more than 1000 in the case of complex devices, are manufacturer-specific. This provides the producers with the utmost flexibility in realising control functions such as ramp-function generators. The profile does not determine the parameters of the latter, although it does determine its interface to the control program through the control word. This means that the control system remains identical, even if a user changes the drive manufacturer. Since control and parameter creation tools are manufacturer-specific, they can determine and visualise all the parameter information either directly from the drive or from a device description file. Central motion control Robotics and tool maschine applications call for a coordinated motional sequence of muliple drives. The motion is controlled mostly with the aid of a central numerical control system (CNC). The position control loop is closed via the bus. The clock cycle synchronisation from PROFIBUS Version DP-V2 is employed in order to synchronise the clock pulses of the position controller in the control system and the controllers in the devices. The stiffness and the dynamics of the control loop can be increased significantly by simple means with the aid of the new "dynamic servo control" position control concept that is also decripted in the profile. Thanks to this concept, even highly demanding applications with linear motors can be realised.
20
Endress+Hauser
2.2.6
Integration technologies
Modern field devices in both Factory and Process Automation provide a wide range of information and execute functions that were previously in the domain of PLCs and control systems. For this reason, tools for commissioning, maintenance, engineering, and parameterization of these devices require an exact and complete description of device data and functions. This includes type of application function, configuration parameters, range of values, units of measurement, default values, limit values, identification, etc. The same applies to the controller/control system, the device-specific parameters and data formats of which must also be made known (integrated) to ensure error-free data exchange with the field devices. PROFIBUS has developed a number of methods and tools ("integration technologies", GSD, EDD and DTM) which enable standardization of device management. The performance range of these tools is optimized to specific tasks (simplest handling, device-tuning at runtime,etc.), which has given rise to the term scaleable device integration. GSD and EDD are both types of "Electronic device data sheets", developed with different languages, whilst a DTM (Device Type Manager) is a software component containing specific field device functions for parameterization, configuration, diagnostics and maintenance, generated by mapping and to be used together with the universal software interface FDT (Field Device Tool), which is able to implement software components. More information on GSD files are to be found in Chapters 3 and 4. Information on EDD can be found on the PROFIBUS site www-profibus.com. A short overview of FDT technology is to be found in Section 2.4.
2.2.7
Quality assurance
In order for PROFIBUS devices of different types and manufacturers to correctly fulfil their tasks in the automation process, it is essential to ensure error-free exchange of information over the bus. This requires an implementation of communications protocol and application profiles in compliance with the standard. To ensure that this requirement is fulfilled, the PNO has established a quality assurance procedure, whereby on the basis of test reports, certificates are issued to devices that successfully complete the test . The certification procedure is based on European standard EN 45 000. The PROFIBUS User Organization has approved independent test laboratories in accordance with the specifications of this standard. Only these test laboratories are authorized to carry out device tests that form the basis for certification. The test procedure, which is the same for all test laboratories, is made up of several parts: GSD/EDD Check: ensures that the device description files comply to the specification. Hardware Test: tests the electrical characteristics of the devices PROFIBUS interface for compliance to the specifications. This includes terminating resistors, suitability of the implemented drivers and other modules and the quality of line level. Function Test: examines the bus access and transmission protocol and the functionality of the test device. Conformity Test: forms the main part of the test. The object is to test conformity of the protocol implementation with the standard. Interoperability Test: checks the test device for interoperability with PROFIBUS devices of other manufacturers in a multi-vendor plant. This checks that the functionality of the plant is maintained when the test device is added. Operation is also tested with different masters. Once a device has successfully passed all the tests, the manufacturer can apply for a certificate from the PROFIBUS User Organization. Each certified device contains a certification number as a reference. The certificate is valid for 3 years but can be extended after the devices undergoes a further test.
Endress+Hauser
21
2.3
PROFIBUS PA
PROFIBUS PA (Process Automation) is an extension of PROFIBUS DP tailored to the requirements of process automation. It has two main characteristics: Participants can draw (intrinsically safe) power from the bus Data transfer is handled according to the international standard IEC 61158-2. PROFIBUS PA was designed to provide an economic and versatile replacement for convention process control systems, as shown in Fig. 2-13.
Conventional process-near component PNC I/O assemblies
PROFIBUS PA process-near component PNC bus couplerEx [i]
marshalling rack Control room
Ex [i]
power
marshalling rack
Fig. 2-13: Signal transmission: conventional and via PROFIBUS PA
One obvious advantage of PROFIBUS is the substution of point-to-point wiring, marshalling racks, barriers and power supplies by a single bus cable. The technology also leaves a much smaller footprint in the control cabinet. The other benefits are less tangible, but more important economically. Digital communication allows comfortable commissioning of field devices from the control room. Individual devices can not only be configured from a personal computer but the settings can also be archived centrally. If there are several identical measuring points in an application, the stored parameters can be downloaded to the devices. An individual configuration of each device is no longer necessary. Other benefits lie in operation and maintenance. PROFIBUS PA devices (and their DP equivalents) offer more information. Every parameter in the device can be accessed, provided an appropriate tool is available. By using Endress+Hausers FieldCare asset management tool, for instance, the device status can be monitored and reports on device health can be generated as desired. The device serial number can also be read, and linked via Internet to a common equipment record at Endress+Hauser that contains the device history. The same parameter also gives access to spare parts and e-business ordering procedures.
22
Endress+Hauser
Field
junction box
connectors
PROFIBUS PA in process engineering
Most manufacturing facilities have a mixture of tasks which are associated with both process and factory automation: Process automation: measurement, actuation, control... Factory automation: filling, storage, conveyance, drives... For this reason, Endress+Hauser devices installed in a factory will be integrated into PROFIBUS DP, PROFIBUS PA or mixed systems.
e.g. FieldCare
PLC / PLS
process control system RS 485 up to 12 Mbit/s
PROFIBUS DP PROFIBUS PA
Non-hazardous area
MBP 31,25 kBit/s
segment coupler
Explosion-hazardous area
MBP 31,25 kBit/s
Fig. 2-14: Prozess automation with PROFIBUS DP and PROFIBUS PA
Fig. 2-14 shows a typical architecture: The process is controlled by a process control system or a programmable logic controller (PLC). The control system or PLC serves as a Class 1 master. It uses the cyclic services to acquire measurements and output control commands. The operating program, e.g. FieldCare, serves as a Class 2 master. It uses the acyclic services and serves to configure the bus participants during installation and normal operation. The PROFIBUS DP system is used to handle the communication at the control level. Drives, remote I/Os etc. may all be found upon the bus. It is also possible to connect externally powered field devices to this level, e.g. the flowmeters Promass and Promag. PROFIBUS DP ensures that data are quickly exchanged, whereby in mixed PROFIBUS DP/PA systems the baudrate supported by the segment coupler is often the limiting factor. PROFIBUS PA is used at field level. The segment coupler serves both as interface to the PROFIBUS-DP system and as power supply for the PROFIBUS PA field devices. Depending upon the type of segment coupler, the PROFIBUS PA segment can be installed in safe or hazardous areas. The practical implementation of such an architecture is the subject of this manual.
Endress+Hauser
23
2.3.1
Operating principle
The PROFIBUS PA bus system is powered by a segment coupler. The field devices function as current sinks and draw a direct current of about 10 mA from the bus cable (some participants require more). This current supplies the energy necessary for operation. If a field device transmits data, it does so by modulating the current by 9 mA. The functional principle is displayed in Fig 3.8. When it is transmitting data, the fieldbus acts as an ohmic resistance. Since the device does not output power, the intrinsic safety of a bus segment is largely determined by the current and voltage limitations placed on the bus power supply (segment coupler). In order that a field device does not block the bus should it fail, its maximum current consumption is limited by the so-called fault disconnection electronics (FDE). This current must be considered when the segment is planned. See corresponding examples in Chapter 5.6.
field device current
mac. current fault current
basic current
Fig. 2-15: Function of a PROFIBUS PA device
Fault disconnection electronics
An important requirement for participants on a PROFIBUS PA segment, is that a defective device may not detrimentally effect the functioning of the system. The fault disconnection electronics ensure that high current consumption is not possible. An electronic circuit detects the rise in the basis current above the specified manufacturer's value and either limits the current consumption or isolates the participant from the bus. The increase in basic current above the normal value in the event of a fault is designated the fault current.
24
Endress+Hauser
2.3.2
Applications in hazardous areas
The explosion protection concept for the PROFIBUS PA fieldbus is based on the type of protection "intrinsic safety i". In contrast to other types of explosion protection, intrinsic safety is not confined to the individual unit, but extends over the entire electrical circuit. All circuits connected to the PROFIBUS PA fieldbus must be realised with type of protection "intrinsic safety", i.e. all devices and terminators that are installed in hazardous areas as well as all associated electrical apparatus (e.g. PA links or segment couplers) must be approved for the corresponding atmospheres. FISCO model In order to reduce the proof of intrinsic safety of the fieldbus system, comprising different devices from different vendors, to a justifiable level, the German PTB and various equipment manufacturers developed the FISCO model (Fieldbus Intrinsically Safe COncept). Further information on FISCO is to be found in Chapter 3.8. The basic idea is that only one device supplies power to a particular fieldbus segment. The model determines the boundary conditions. The field devices are divided into those that draw their power from the bus itself and those that must be powered locally. In addition to the type of protection "intrinsic safety", the latter devices, which require more energy, must also exhibit a further type of protection. The auxiliary energy required by the segment coupler and the locally powered devices is galvanically isolated from the intrinsically safe circuits. As is the case for all intrinsic circuits, special precautions must be observed when installing the bus. The aim is to maintain the separation between the intrinsically safe and all other circuits. Grounding The intrinsically safe fieldbus circuit is operated earth-free, which does not preclude that individual sensor circuits can be connected to ground. If a overvoltage protector is installed before the device, it must be bonded to the plant grounding system in accordance with the instructions in the certificate or device manual. Particular attention must be paid to the grounding of the conducting cable screening because if it is to be earthed at several positions, a high integrity plant grounding system must be present. The category of the intrinsically safe field bus is determined by the circuit with the worst rating, i.e. if the fieldbus circuit of one device has the type of protection EEx ib, then the whole fieldbus falls in the category ib. Devices that must be connected to a circuit with type of protection EEx ia (requirements as per certificate) may not be operated on field bus circuits with type of protection ib. Only circuits that are connected directly to the fieldbus must be considered here. Devices that are approved for different explosion groups (IIC, IIB or IIA) can be operated on the same segment. The permissible explosive atmosphere allowed at a particular device is determined by the type of protection of that device as well as the explosion group for which the segment coupler is approved. All devices and terminators that are installed in hazardous areas as well as all associated electrical apparatus (e.g. PA links or segment couplers) must be approved for the corresponding atmospheres, e.g. PTB, BVS, FMRC, CSA etc.).
Category
Explosion group
Endress+Hauser
25
2.4
Field Device Tool (FDT)
Field Device Tool (FDT) provides a standard interface, open to all communication protocols and software environments that allows any device to be accessed from any host through any protocol. The essential parts of FDT technology are the frame application and the so-called Device Type Managers (DTMs), which are available for field devices and communication equipment, see Fig. 2-16 The two components could be likened to the Print Manager in a Windows Office program and the Print Drivers that must be installed to make printers work and which contain a graphical user interface for their configuration.
FDT frame program
DTM: Device Type Manager
Network configuration Navigation User Management DTM Management Data Management Communication Interfaces HART, PROFIBUS, FF
Plant Network (Devices, Drives, PLCs, etc.)
Fig. 2-16: Schematic diagram of FDT frame
FDT Frame
The FDT frame communicates with the hosting or stand-alone application and the device drivers via a set of standardised interfaces. All data are exchanged through these interfaces, including those generated within the application for engineering, DTM management and device configuration. It is no longer necessary to use proprietary interfaces to operate devices or build up communication paths. Frame applications can be device configuration tools, control system-engineering tools, operator consoles or asset management tools. The frame application is also open to all communication technologies, e.g. for HART, PROFIBUS and FOUNDATION Fieldbus, see Fig 2-16. Proprietary service bus protocols can also be integrated simply into the frame application because of the standardised interface. The device DTM is a software driver developed by the device manufacturer for each of his devices or group of devices. The DTM encapsulates all the device-specific data, functions and management rules such as the device functions, its communication capabilities, internal data structure and dependencies as well as the user interface elements. It provides functions for accessing device parameters, configuring and operating the devices, calibrating, and diagnosing problems. DTMs can range from a simple user interface for setting device parameters to a highly sophisticated application. They may perform complex calculations for diagnosis and maintenance purposes or display results in the form of curves, trends and other graphical elements. For communication equipment, such as gateways, multiplexers and other hardware interfaces a CommDTM is required. Like any communication driver, this converts data from one protocol to another, but with the difference that the integration into the system is via a standardised FDT rather than a proprietary interface. This means that users wishing to integrate existing communication equipment into a FDT frame application require only the corresponding CommDTMs. Similarly, vendors need only modify their existing drivers to include a FDT interface and their equipment can be integrated into any FDT frame application.
Device DTM
Communication DTM
26
Endress+Hauser
FDT also includes the concept of 'Nested Communication', so that with the aid of CommDTMs, the communication hierarchies found in the plant can be replicated simply in the hosting configuration tool. In this way, the FDT architecture eliminates the integration problems that normally occur when different devices must communicate with each other. It also provides transparent access to data at all system levels.
FDT-Application
e.g. FieldCare Engineering tool DTM
DTM
DTM
PLC
Communication& Device-DTMs
Segment coupler
DTM
PROFIBUS DP
Remote I/O DTM
PROFIBUS PA
4...20 mA HART
DTM DTM
PROFIBUS PA-Slaves
Fig. 2-17: FDT/DTM Technology - Fieldbus- and device management
The FDT standard uses XML and of is modular construction, each standardised interface reflecting a certain functionality such as configuration or display of measured values. This scalable approach allows DTMs to be developed that exactly match device capabilities and keep up improvements within its life-cycle. There is no reduction of functionality here. FDT is also extendable: new interfaces can be added to cater for functional system enhancements. Not only does this ensure that the standard will keep pace with technical advance, it also ensures that future developments will not affect existing solutions. DTM Production A Device Type Manager file can written from scratch or be produced from a EDD or HART DD file by running the latter through a special DTM compiler. The Comm DTM is a separate entity that is used to map the communication infrastructure existing in the field. The DTM compilation process is largely automatic and as long as an EDD or HCF DD file exists for the device, a corresponding DTM can be produced. This makes the integration of legacy HART or PROFIBUS devices into an FDT frame application a practical proposition. The FDT tool can then run in parallel to the existing system device configuration tool. For new FDT based installations, the frame application may be stand-alone or integrated into the control system. This has enormous benefits for the user, since he has freedom of choice in the components he uses. Any device or communication component with a device DTM or Comm DTM will operate in any FDT-based configuration tool. Seen for the operators point of view: a single FDT frame can be used to operate a range of devices from a number of different vendor.
Endress+Hauser
27
FDT Joint Interest Group
The non profit making FDT Joint Interest Group is an open collaboration of international automation companies for the proliferation of FDT/DTM technology. The group is open to all companies and organizations that wish to participate. The mission of the FDT Joint Interest Group is to promote the acceptance and usage of FDT technology in the factory automation industry, process automation industry and hybrid application industry. Endress+Hauser is a founding member of the FDT Joint Interest Group and servers on the Marketing and Steering Committees. The PROFIBUS User Organisation (PNO) has granted to the FDT Joint Interest Group ownership rights to use the technology. PNO is the association of users of Profibus technology. FDT technology is available to all companies that wish to utilize it. The Groups headquarters are in Germany/America. For more information on FDT technology and the FDT Joint Interest Group, see web site http://www.fdt-jig.org
28
Endress+Hauser
3 PROFIBUS DP basics
PROFIBUS DP basics
As far as PROFIBUS systems in process engineering are concerned, the versions PROFIBUS DP (variant DP-V1) and PROFIBUS PA are of interest. This chapter describes the basics of PROFIBUS DP. The chapter is structured as follows: Synopsis Topology Bus access method Network configuration Applications in hazardous areas
3.1
Synopsis
Class 1 Master Class 2 Master e.g. FieldCare
PLC
PROFIBUS DP
PROFIBUS DP Slaves
Fig. 3-1: PROFIBUS DP-System, Version DP-V1
Application
PROFIBUS DP is used primarily for factory automation. In PROFIBUS PA systems for process automation, a PROFIBUS DP system is used at the control level for quick transmission of the data. Here, PROFIBUS DP-V1 is normally used. In addition to the cyclic exchange of data with a PLC, DP-V1 allows the field devices to be configured via acyclic services. The principle technical data for PROFIBUS DP are listed in Table 3-1 below.
Standard Support Physical layer Max. length IEC 61158 PROFIBUS User Organisation e.V. (PNO) RS-485 and/or fibre optics max. 1200 m without repeater (RS 485), max. 9 repeaters or several kilometers (fibre optics) max. 126, including max. 32 as master 9.6 kBit/s up to 12 MBit/s in defined levels Token passing with master-slave DP-V0; DP-V1; DP-V2 Table 3-1: Technical data PROFIBUS DP
Participants Transmission rate Bus access method Protocol
Endress+Hauser
29
Participants
Depending upon the application at hand, the participants in a PROFIBUS DP system might be frequency converters, remote I/Os, actuators, sensors, links, gateways etc. as well as the PLC or process control system. The following Endress+Hauser devices can be connected directly to a PROFIBUS DP system:
Type/Name ASP 2000 Function and Application Stationary precision water sampler for water and wastewater applications Plant Asset Mangement - universal, FDT-based, operating tool for field devices with PROFIBUS PA/DP and other protocols pH/ORP, conductivity, oxygen, turbidity, chlorine measurement for water and waste water 16/7 channel (analog/digital) videographic display recorder for where exact recording is required Magnetic-inductive flow measurement for inductive liquids Coriolis mass flow measurement for liquids, steam and gases Ultrasonic level and flow measurement for solids and liquids Ultrasonic flow measurement for liquids Energy manager for water and steam with up to 10 inputs for 1-3 applications Measurement of conductivity and concentration in highly conductive liquids PROFIBUS DP gateway for Commutec Table 3-2: Available Endress+Hauser PROFIBUS DP products
FieldCare
Liquisys M
Memo-Graph RSG 10
Promag 53 Promass 83 Prosonic DP (FMU 86x) Prosonic Flow 93 RMS 621
Smartec S
ZA 375
30
Endress+Hauser
3.2
Topology
PROFIBUS DP is based on a linear topology. For lower data transmission rates, a tree structure is also possible. Cable (Type A) EN 50 170 specifies two types of bus cable. For transmission rates up to 12 Mbit/s, cable type A is recommended. The specification is given in Table 3-3:
Terminator Cable capacitance Core cross-section Cable type Loop resistance Signal attenuation Screening 135 to165 at a measuring frequency of 3 MHz to 20 MHz < 30pF per Meter > 0.34 mm, corresponds to AWG 22 twisted pairs, 1x 2, 2x 2 or 1x 4 core 110 per km max. 9 dB over the entire length of the segment woven copper sheath or woven sheath and foil sheath Table 3-3: Specifications of Cable Type A
Structure
The following points should be noted when the bus structure is being planned: The max. permissible cable length depends upon the transmission rate. For PROFIBUS RS-485 cable of type A (see table 2.3) the dependency is as follows:
Transmission rate (kBit/s) Cable length (m) 9.6; 19.2; 45.45; 93.75 1200 187.5 1000 500 400 1500 200 3000; 6000; 12000 100
A maximum of 32 participants per segment is allowed A terminating resistance must be installed at both ends of every segment (ohmic load 220 ) The cable length and/or the number of participants can be increased by using repeaters If repeaters are used: The first and last segment may contain up to 31 particpants, the segments between repeaters may contain up to 30 participants. The maximum distance between two participants is: (NO_REP +1) * Segment length where = NO_REP = max number of repeaters that may be used in series (dependent on type).
Example: According to a manufacturers specifications, up to 9 repeaters can be connected in series on a standard line. The maximum distance between two bus participants for a transmission speed of 1.5 MBit/s is thus: (9+1)*200 m = 2000 m
Endress+Hauser
31
Spurs
A spur is the cable connecting the field device to the T-box on the bus.
"
Examples
Caution! As a rule of thumb: For transmission rates up to 1.5 MBit/s, the total length (sum) of the spurs may not exceed 6.6 m Spurs should not be used for transmission rates greater than 1.5 MBit/s. Figs 3-2 and 3-3 show examples for a linear and tree bus structure. Fig 3-2. shows that three repeaters are necessary if the PROFIBUS DP system is to be developed to the full. The maximum cable length corresponds to 4x the value quoted in the table above. Since three repeaters are used, the maximum number of participants is reduced to 120. Fig 3-3 shows how several repeaters can be used to create a tree structure. The number of participants allowable per segment is reduced by one per repeater.
Fig. 3-2: PROFIBUS DP-system with linear structure (T = terminator, R = repeater, 1...n = max. number of field devices on a segment)
Fig. 3-3: PROFIBUS DP-system with tree structure (T = terminator, R = repeater, 1...n = max. number of field devices on a segment)
32
Endress+Hauser
Optical network
If the PROFIBUS DP system has to be routed over large distances or in plant with heavy electromagnetic interference, then an optical or mixed optical/copper network can be used. Provided that all participants support them, very high transmission rates are possible. Fig. 3-4 shows a possible structure for an optical network, whereby the technical details can be taken from the PROFIBUS standard.
Master (PLC)
RS 485 copper
optical interface modulel
optical interface module
fibre optics
Fig. 3-4: Example for a mixed optical/RS-485-network (T = terminator, 1...n = field devices (slaves)
Endress+Hauser
33
3.3
Bus access method
PROFIBUS DP uses a hybrid access method of centralised master/slave and decentralised token passing, see Fig. 3-5. The masters build a logical token ring. When a master possesses the token, it has the right to transmit. It can now talk with its slaves in a master-slave relationship for a defined period of time. At the end of this time, the token must be passed on to the next active device in the token ring. Master class PROFIBUS DP version DP-V1 differentiates between two classes of master: A Class 1 master communicates cyclically with its slaves. The master communicates only with those slaves that are assigned to it. A slave may be assigned to only one Class 1 master. A typical class 1 master is a programmable logic controller (PLC) or a process control system. A Class 2 master communicates acyclically with its slaves, i.e. on demand. Its slaves may also be assigned to a Class 1 master. A typical example is a PC with corresponding operating software, e.g. FieldCare - Plant Asset Management Tool. It is used for commissioning as well as for device configuration, diagnosis and alarm handling during normal operation. If a PROFIBUS-DP network has more than one master e.g. because both cyclic and acyclic services are required, then it is a multi-master system. If, for example, a PLC only is used for control tasks, then the system is a mono-master system.
Master 1, Class 1 has the right to transmit. Data are exchanged cyclically.
Class 1
logical token ring between master participants
Master 2, Class 2 receives the right to transmit. It can talk to all slaves. Data exchage, e.g. with slave 3 is acyclic.
Class 2
Fig. 3-5: Data exchange in a PROFIBUS DP-multi-master system (M = master, S = slave)
34
Endress+Hauser
3.4
Data transmission
Network configuration
Data are exchanged over PROFIBUS DP by means of standard telegrams which are transmitted via the RS-485 interface. The permissible telegram length of reference data is specified in the PROFIBUS DP protocol at 244 bytes. it should be noted, however, that some controllers only support an maximum telegram length of 122 bytes. The PROFIBUS DP devices manufactured by Endress+Hauser may transmit both input and output values, see also Table 5.17. In general: Measured value and status inputs are transmitted in 5 bytes. Display values and status outputs are transmitted in 5 bytes Control output values generally require 1 byte per action, the actual number available being dependent upon device. An instrument with several measured values can transmit correspondingly more bytes. In the case of the flowmeter Promass 63, for example, a cyclic telegram up to 37 bytes (25 bytes input and 12 byte output data) is transmitted at maximum configuration, see Section 3.4.2. The values to be transmitted are determined during the commissioning of the network. The total number of inputs and outputs enabled then determine the telegram length. The same telegram is used for transmission to and from the PLC.
GSD (device database file)
In order to integrate the field devices into the bus system, the PROFIBUS DP system requires a description of the device parameters such as output data, input data, data format, data length and the transmission rates supported. These data are contained in the GSD device database file, which is required by the PROFIBUS DP master during the commissioning of the communication system. In addition, device bit maps are required, which appear as icons in the network tree. Further information on device database files is to be found in Chapter 7.2. A prerequisite for communication on the bus is the correct addressing of the participants. Every participant in the PROFIBUS DP system is assigned a unique address between 0 and 125 (cyclic data transmission). Normally the low addresses are assigned to the masters. The addresses may be assigned by DIP switch, on-site operating elements or by an operating program, e.g. FieldCare. The exact way in which this is done should be taken from the appropriate device manual. For Endress+Hauser devices, the factory default address is always 126. This must be changed during commissioning and no device in the system should use it for cyclic communication.
Bus address
Transmission rate
All participants in a PROFIBUS DP system must support the governing transmission rate. This means that the speed of data exchange is determined by the slowest participant. In the case of Endress+Hauser devices that are designed for PROFIBUS DP, all transmission rates from 9.6 kbits/ s to 12 Mbit/s are supported. For other manufacturers, please consult the relevant operating manual. In addition to the transmission rate, all active participants on the bus must operate with the same bus parameters. If FieldCare is in use, the bus parameters can be set by using the corresponding Communication DTM for PROFIBUS. Individual device rates are set within their DTMs. More information on bus parameters are to be found in the Chapter 4.
Bus parameters
Endress+Hauser
35
3.5
Applications in hazardous areas
All devices and terminators that are installed in hazardous areas as well as all associated electrical apparatus (e.g. PA links or segment couplers) must be approved for the corresponding atmospheres. RS-485 IS RS-485 IS is a recent innovation in response to an increasing market demand for the use of RS-485 in explosion-hazardous areas. A corresponding PROFIBUS guideline is now available that specifies the configuration of intrinsically safe RS-485 solutions with simple device interchangeability. In contrast to the FISCO model (see Chapters 2.2.1 and 6.1), for which there is only one active supply device per segment, all stations represent active sources. The devices are supplied with external energy and can supply this to the bus. RS-485 IS segments are coupled to RS-485 safe segments by means of so-called "Fieldbus Isolating Repeaters". Up to 32 stations can be connected to the intrinsically safe bus circuit, provided the conditions in Table 3-7 arre upheld. More details can be found in the specification. Endress+Hauser devices do not support RS-485 IS at the present moment, but offers equivalent solutions with standard devices. The following table shows all safety-relevant values for the entire bus system.
Parameter Bus system Maximum input voltage Maximum input current Maximum inductance to resistance ratio Number of devices Communication device Maximum output voltage Maximum output current Uo [V] I [mA] Ui [V] Li [H] Ci [nF] Ui [V] Ii [A] L /R [H/] Description Value Remarks
4.2
4.8 15 For the whole operation Temperaturee range of the bus system
NTN
32 4.2
149 Total current from wires A, B and supply for bus termination
Maximum input voltage Maximum internal inductance Maximum internal capacitance External active bus termination Maximum output voltage Maximum output current Maximum input voltage Maximum internal inductance Maximum internal capacitance
4.2
0 N/A Insignificant for safety
Uo [V] I [mA] Ui [V] Li [H] Ci [nF]
4.2
16
4.2
0 N/A Insignificant for safety
Table 3-4: PROFIBUS RS_485 IS: list of safety-relevant parameters
36
Endress+Hauser
If a PROFIBUS DP segment runs through an explosiion hazardous area, it must be executed with a degree of protection "increased safety" "e". For copper cabling, the number of devices per segment is limited to four. Proof of instrinsic safety is required for every segment, since every intrinsically safe component has different electrical characteristics. The cable and spurs must be included in the calculation. Exchange of a component from one manufacturer by a component from another manufacture is always requires renewed proof of intrinsic safety. Mixed network PROFIBUS DP/PA Since PROFIBUS PA systems are designed for use in hazardous areas, it is much easier install a segment there. For this reason, a PROFIBUS PA segment is used to extend the PROFIBUS DP segment into a hazardous area. PROFIBUS PA networks are connected to PROFIBUS DP networks by a segment coupler or link, see Chapter 3.2.
PLC Class 1 master
e.g. FieldCare Class 2 master
segment coupler / link
PROFIBUS DP
PROFIBUS PA
PROFIBUS DP-Slaves
PROFIBUS PA-Slaves
Fig. 3-6: The PROFIBUS DP system can be extended into a hazardous area by using a segment coupler/link.
Endress+Hauser
37
4 PROFIBUS PA Basics
PROFIBUS PA Basics
This chapter presents the basic principles behind PROFIBUS PA. It is structured as follows: Synopsis Segment couplers and links Topology Bus access method Network configuration Applications in hazardous areas Operating mode FISCO Fieldbus barriers
4.1
Application
Synopsis
PROFIBUS-PA has been designed to satisfy the requirements of process engineering. There are three major differences to a PROFIBUS DP system: PROFIBUS PA supports the use of devices in explosion hazardous areas without the need for specific proof of intrinsic safety. The devices can be powered over the bus cable (two-wire devices). The data are transferred via the IEC 61158-2 physical layer (MBP), which allows great freedom in the selection of the bus topology. The most important technical data are listed in Table 4-1.
Participants
Depending upon the application, the participants on a PROFIBUS PA segment might be actuators, sensors and a segment coupler or link, see Chapter 4.2. Endress+Hauser offers PROFIBUS PA instrumentation for the most important process variables, i.e. analysis, flow, level, pressure and temperature. A complete list is to be found in Chapter 10.
PLC Class 1 master
DP/PA link or segment coupler
PROFIBUS DP
PROFIBUS PA
PROFIBUS PA-Slaves
Fig. 4-1: PROFIBUS PA-system
38
Endress+Hauser
Standard Support Physical layer Max. length from segment coupler
IEC 61158 PROFIBUS User Organisation (PNO) IEC 61158-2, Mancester Coding Bus Powered (MBP) 1900 m: Standard- und eigensichere Anwendungen der Kategorie ib 1000 m: Eigensicheren Anwendungen der Kategorie ia max. 10 in hazardous areas (EEx ia) max. 24 in hazardous areas (EEx ib) max. 32 in safe areas 31.25 kBit/s Master-slave DP-V1 Table 4-1: Technical data PROFIBUS PA
Participants
Transmission rate Bus access method Protocol
4.2
Segment coupler and links
PROFIBUS PA is always used in conjunction with a supervisory PROFIBUS DP control system. Since the physical layer and transmission rates of PROFIBUS DP and PROFIBUS PA are different, see Tables 3-1 and 4-1, the PROFIBUS PA segment is connected to the PROFIBUS DP system via a segment coupler or link. Segment couplers are signal converters that modulate the RS485 signals to the MBP signal level and vice versa. They are transparent from the bus protocol standpoint. In contrast, links have their own intrinsic intelligence. They map all the field devices connected to the MBP segment as a single slave in the RS485 segment.
PLC Class 1 master
PROFIBUS DP
segment coupler / link segment coupler PROFIBUS PA segment coupler
junction box
Fig. 4-2: Integration of a PROFIBUS PA segment into a PROFIBUS DP system using a segment coupler or link
Endress+Hauser
39
4.2.1
Segment coupler
A segment coupler comprises a signal coupler and bus power unit. Depending upon model, they may support a fixed or a range of transmission rates on thePROFIBUS DP side. The transmission rate for PROFIBUS PA is fixed at 31.25 kbit/s. Three types of segment couplers have been specified according to the type of protection required.
Segment coupler Type of protection Supply voltage Max. power Max. supply current No. of devices Type A EEx [ia/ib] IIC 13.5 V 1.8 W 110 mA ca. 10 Type B EEx [ib] IIB 13.5 V 3.9 W 280 mA ca. 20 Type C None-Ex 24 V 9.1 W 400 mA max. 32
Table 4-2: Segment couplers defined in standard
At the moment two manufacturers have segment couplers available:

Manufacturer / Model Description Type of protection Non-Ex Non-Ex EEx [ia] IIC EEx [ia] IIC EEx [ia] IIC Non-Ex Supply current 380 mA 400 mA 100 mA 100 mA 100 mA 400 mA Voltage DP-baudrate
Pepperl+Fuchs SK1 Pepperl+Fuchs SK1 Pepperl+Fuchs SK1 Pepperl+Fuchs SK1 Pepperl+Fuchs SK1 Pepperl+Fuchs SK2
KFD2-BR-1.PA.2 KFD2-BR-1.PA.93 KFD2-BR-EX1.PA KFD2-BR-EX1.2PA.93 KFD2-BR-EX1.3PA.93 KLD2-PL(2)-1.PA
22.0 V DC 24.0-26,0 V DC 12.6-13.4 V DC 12.6-13.4 V DC 12.6-13.4 V DC 24,0-26,0 V DC
93.75 kBit/s 93.75 kBit/s 93.75 kBit/s 93.75 kBit/s 93.75 kBit/s 45.45 kBit/s 12 MBit/s* 45.45 kBit/s 12 MBit/s* 45.45 kBit/s** 45.45 kBit/s** 45.45 kBit/s** 45.45 kBit/s** 45.45 kBit/s**
Pepperl+Fuchs SK2
KLD2-PL(2)-EX1.PA
EEx [ia] IIC
100 mA
12.8 - 13.4 V DC
Siemens DP/PA-coupler Siemens DP/PA-coupler Siemens DP/PA-coupler Siemens DP/PA-coupler Siemens DP/PA-coupler
6ES7157-0AC80-0XA0 6ES7157-0AD00-0XA0 6ES7157-0AD80-0XA0 6ES7157-0AD81-0XA0 6ES7157-0AD82-0XA0
Nicht-Ex EEx [ia] IIC EEx [ib] IIC EEx [ia] IIC EEx [ia] IIC
400 mA 90 mA 110 mA 110 mA 110 mA
19.0 V DC 12.5 V DC 12.5 V DC 13.5 V DC 13.5 V DC
Table 4-3: Segment couplers on the market * in coinnection with gateway KLD2-GT-DP.xPA or KLD2-GT-DPR.xPA ** in connection with 6ES7157-0AA8x-0XA0 as DP/PA link, rates from 9.6 kBit/s up to 12 MBit/s are supported.
4.2.2
Link
A link comprises an intelligent interface and one or more segment couplers, whereby the couplers may exhibit different types of protection. Normally, a range of transmission rates are supported on the PROFIBUS DP side. The transmission rate for PROFIBUS PA is fixed at 31.25 kbit/s. Links differ from pure segment couplers by the fact that they are PROFIBUS DP slaves on one side and PROFIBUS PA masters on the other. There is no direct communication between the PROFIBUS DP master and the PROFIBUS PA slaves, i.e. the link is not transparent. Futher information is to be found in the sections on addressing and cycle times.
40
Endress+Hauser
4.3
Topology
The field devices on the PROFIBUS PA segment communicate with a master on the PROFIBUS DP system. The bus is designed according to the rules for PROFIBUS DP up to the segment coupler or link, see Chapter 3.2. Within the PROFIBUS PA segment, practically all topologies are permissible, see Fig. 4-3, below.
Termination at JB possible if spurs do not exceed 30 m
Fig. 4-3: Bus topologies (A:Tree, B:Bus, C:Bus + Tree, D:Bus + Tree + extension), PNK: process near component, SiK: Signal coupler, SG: Power supply, T: Terminator, JB: Junction box, R: Repeater, 1...n: Field devices, Sk: Segment coupler
Endress+Hauser
41
Cable type
The fieldbus comprises two-core cable. According to IEC 61158-2 (MBP), four different cable types (A, B, C, D) can be used, only two of which (cable types A and B) are shielded. Cable types A or B are recommended for new installations. Their cable shielding guarantee adequate protection from electromagnetic interference and thus the most reliable data transfer. On multi-pair cables (Type B), it is permissible to operate multiple fieldbuses (with the same degree of protection) on one cable. No other circuits are permissible in the same cable. Practical experience has shown that cable types C and D should not be avoided where possible since the lack of shielding means that electromagnetic interference characteristics generally do not meet the requirements described in the standard. Table 4-4 lists the technical data of the four cable types as taken from the informative annex to the standard (i.e. this has not actually been specified.) The electrical data determine important characteristics of the design of the fieldbus, such as distances bridged, number of participants, electromagnetic compatibility, etc.
Cable type A Cable construction twisted pair, shielded Cable type B one or more twisted pairs, common shielded 0.32 mm2 AWG 22 112 /km 100 30 % Cable type C one or more twisted pairs, unshielded Cable type D one or more untwisted pairs, unshielded
Core cross-section
0.8 mm2 AWG 18 44 /km 100 20 %
0.13 mm2 AWG 26 254 /km
1.23 mm2 AWG 16 40 /km
Loop resistance (DC)
Characteristic impedance at 31.25 kHz
Attenuation constant at 39 kHz Capacitive unsymmetry Envelope delay distortion (7.9...39 kHz) Degree of coverage of shielding Max. recommended bus length (including spurs)
3 dB/km 2 nF/km 1.7 s/km 90 % 1900 m
5 dB/km 2 nF/km 1200 m
8 dB/km 400 m
8 dB/km 200 m
Table 4-4: Cable types according IEC 61158-2, Annex C
Intrinisic safety
Cable for intrinsically safe applications as per the FISCO model must also satisfy the following additional requirements:
EEx ia/ib IIC Loop resistance (DC) Specific inductance Specific capacitance Max. spur length Max. bus length 15...150 /km 0.4...1 mH/km 80...200 nF/km 30 m 1000 m EEx ib IIB 15...150 /km 0.4...1 mH/km 80...200 nF/km 30 m 1900 m
Table 4-5: Safety limits for the bus cable according FISCO
42
Endress+Hauser
Cable manufacturers
Table 4-6 list examples for Type A PROFIBUS-PA cable available from various manufacturers.
Manufacturer Turck Turck Siemens Siemens Lapp Lapp Order No. Cable 483-*M Cable 483B-*M 6XV1830-5FH10 6XV1830-5EH10 2170235 2170234 Application Standard EEx ia/ib IIC Standard EEx ia/ib IIC Standard EEx ia/ib IIC Table 4-6: PROFIBUS PA cable Specific resistance 44 /km 44 /km 44 /km 44 /km 44 /km 44 /km
Maximum overall cable length
The maximum network length depends on the type of ignition protection and the cable specifications. The overall cable length is made up of the length of the main cable and the length of all spurs that are longer than 1 m.
Cable type A 1900 m Cable type B 1200 m Cable type C 400 m Cable type D 200 m
Table 4-7: Maximum permissible overall cable length depending upon the cable type used
Note! In FISCO systems with type of protection EEx ia, the maximum line length 1000 m If repeaters are used, the maximum permissible cable length is [length in table x (N+1)], where N is the number of repeaters. A maximum of four repeaters are permitted between station and master. The line between distribution box and field device is described as a spur. In the case of non ex-rated applications the max. length of a spur depends on the number of spurslonger than 1 m:
Number of spurs Max. length per spur 1...12 120 m 13...14 90 m 15...18 60 m 19...24 30 m 25...32 1m
Maximum spur length
Table 4-8: Maximum length of a spur depending on the number of spurs
!
Number of field devices
Note! In FISCO systems with type of protection EEx ia, the max. length per spur is 30 m. As far as the specification is concerned, a maximum of: 32 stations per segment in safe areas 10 stations in an explosive hazardous arrea (EEx ia IIC) are possible. The actual number of stations is dependent on several factors, however, and must be determined during project planning. The start and end of each fieldbus segment must be terminated with a bus terminator. The terminator may be a separate component or be integrated into a bus component.
Bus termination
Note! If the segment is in an explosion hazardous area, the terminators must be certified to the FISCO standard. In the case of a branched bus segment, the device furthest from the segment coupler represents the end of the bus. If the fieldbus is extended with a repeater then the extension must also be terminated at both ends.
Endress+Hauser
43
4.4
Bus access method
PROFIBUS PA uses the central master/slave method to regulate bus access. The process near component, e.g. a PLC, is a Class 1 master that is installed in the PROFIBUS DP system. The field devices are configured from a PROFIBUS PA Class 2 master, e.g. FieldCare. The field devices on the PROFIBUS PA segment are the slaves.
4.4.1
Segment coupler
Segment couplers are transparent as far as the PROFIBUS DP master is concerned, so that they are not mapped in the PLC. They simply convert the signals and power the PROFIBUS PA segment. The do not need to be configured nor are they assigned an address. The field devices in the PROFIBUS PA segment are each assigned a PROFIBUS DP address and behave as PROFIBUS DP slaves. A slave may be assigned to only one Class 1 master. A master communicates directly with its slaves: A Class 1 master, e.g. the PLC, uses the cyclic polling services to fetch the data provided by the field devices. A Class 2 master, e.g. FieldCare, transmits and receives field device data by using the acyclic services.
PLC Class 1 master
PROFIBUS DP cyclic data exchange Segment coupler acyclic data exchange
PROFIBUS PA
PROFIBUS PA-slaves
Fig. 0.1
Data exchange via segment coupler
Segment coupler SK1 from Pepperl+Fuchs
If the SK1 segment coupler is used, the transfer rate for the PROFIBUS DP is fixed at 93.75 kBd. In this case, if type A cable is used for the PROFIBUS DP the PROFIBUS DP segment can be up to a length of 1200 m. The length of the PROFIBUS PA segment depends on: whether the PROFIBUS PA segment in question is intrinsically safe or not. how many PROFIBUS PA stations are connected to the segment. how high is the current consumption of the individual PA slaves. how the PA slaves are distributed on the PROFIBUS PA segment.
The SK1 segment coupler works transparently. This means that PROFIBUS DP masters have direct access to every PROFIBUS PA slave. Addresses that have been assigned on a PROFIBUS PA segment are also occupied on the PROFIBUS DP.
44
Endress+Hauser
4.4.2
Gateway-type segment coupler
This type of segment coupler allows several segments to be connected to one central coupler unit, whilst retaining the transparency of the unit. For the user, however, it operates in exactly the same manner as the normal segment coupler, see Fig. 4-5.
e.g. FieldCare Class 2 master PLC Class 1 master
PROFIBUS DP
SK 2
acyclic data exchange
cyclic data exchange
Gateway Segment coupler 1 ... max. 5
PROFIBUS PA
PROFIBUS PA-slaves
PROFIBUS PA-slaves
Fig. 4-4: Bus access using a Pepperl+Fuchs SK2 segment coupler
Segment coupler SK2 from Pepperl+Fuchs
The SK2 segment coupler is a modular unit comprising power pack, gateway with up to four channels and up to 20 power links. The power links supply (intrinsically safe) power to their segments, whilst the gateway couples the PROFIBUS PA devices to the PROFIBUS-DP network. A maximum of five power links per channel is allowed. The SKs has the following properties: No restriction on PROFIBUS PA data volume (244 Byte I/O per slave possible) Support of PROFIBUS DP transfer rates (45,45 kBd... 12 MBd) No addressing of the segment coupler, either PROFIBUS DP or PROFIBUS PA Direct access for the PROFIBUS DP master to the PROFIBUS PA slave (transparency).
The major difference to a standard segment coupler is the variable transmission rate on the DP side. This allows better cycle times to be attained in mixed DP/PA systems.
Note! When a SK2 coupler is used in a PROFIBUS network, the GSD files of the PROFIBUS PA slaves to be connected to it must be converted using a special program supplied by Pepperl+Fuchs. Despite the conversion, the PNO certificates for these devices still retain their validity. No PROFIBUS PA slave may be assigned the address 1.
Endress+Hauser
45
4.4.3
Links
In contrast to a segment coupler, a link is recognised by the PROFIBUS DP master and is a participant in the PROFIBUS DP system. It is assigned a PROFIBUS DP address and thus becomes opaque to the master. The field devices on the PROFIBUS PA side can no longer be directly polled using the cyclic services. Instead, the link collects the device data in a buffer, which can be read cyclically by a Class 1 master. Hence a link must be mapped in the PLC. On the PROFIBUS PA side, the link acts as the PA master. It polls the field device data cyclically and stores them in a buffer. Every field device is assigned a PROFIBUS PA address that is unique for the link, bit which may be used in a segment connected to another link. When the link is accessed by a Class 2 master with the acyclic services it is quasi-transparent. The desired field device can be accessed by specifying the link address (DP address) and the device address (PA address).
PLC Class 1 master
PROFIBUS DP
Cyclic data exchange with Class 1 master using the master-slave method Link
Acyclic data exchange with Class 2 master using the master-slave method
PROFIBUS PA-slaves
PROFIBUS PA-slaves
Fig. 4-5: Data exchange via a link
Siemens DP-/PA link
The Siemens DP/PA link acts as described above. It supports PROFIBUS DP transmission rates from 9.6 kBit/s up to 12MBit/s. As indicated, the DP/PA link is not transparent and must be planned in the PLC or control system by means of a GSD file. Among other things, all the cyclic I/O data of the connected slaves must be entered into this file. In order to facilitate the generation of a project specific GSD file for the link, Siemens supplies a special software application. The link is limited in the amount of PROFIBUS PA data it can transmit. The total amount of cyclic I/O data permitted, i.e. the accumulated total from all PROFIBUS PA devices connected to the link, is 244 bytes for input and 244 bytes for output data.
46
Endress+Hauser
4.5
Data transmission
Network Configuration
Data exchange on the PROFIBUS PA segment is handled by the IEC 61158-2 interface. The cyclic and acyclic polling services are used to transmit data. Since the PROFIBUS PA standard offers the possibility of interconnecting devices from different vendors, a profile set has been defined that contains standardised device parameters and functions: Mandatory parameters: Every device must provide these parameters. These are parameters, with which the basic parameters of the device can be read or configured. Application parameters: These are optional parameters. These parameters allow a calibration and, e.g., additional functions such as a linearisation to be performed. In view of the fact that these functions are dependent upon the measured variable, there are several profile sets, e.g. for level, pressure, flow etc.. The parameters can be accessed acyclically and require a Class 2 master, e.g. FieldCare, if they are to be read or modified. Cyclic data exchanged is handled by standard telegrams. The permissible telegram length depends upon the master used: according PROFIBUS PA-standard, 244 bytes for inputs and 244 bytes for outputs. For PROFIBUS PA devices, analogue measured values and status are transmitted in 5 bytes. If a device offers more values, more bytes may be transmitted, see Chapter 3.4. In the case of the level limit swich Liquiphant M/S, the limit signals are transmitted in 2 bytes per channel. Byte 1 contains the signal condition, byte 2 the status.
GSD (device database file)
In order to integrate the field devices into the bus system, the PROFIBUS DP system requires a description of the device parameters such as output data, input data, data format, data length and the transmission rates supported. These data are contained in the GSD device database file, which is required by the PROFIBUS DP master during the commissioning of the communication system. In addition, device bit maps are required, which appear as icons in the network tree. Further information on device database files is to be found in Chapter 7.2. A pre-requisite for communication on the bus is the correct addressing of the participants. Every device on the PROFIBUS PA segment is assigned a unique address between 0 and 125. The addressing is dependent upon the type of DP-/PA-interface used (segment coupler or link) and is set by DIP switches, via on-site operating elements or by software. The addressing procedure is described in detail in Chapter 5.5. The transmission rate on a PROFIBUS PA segment is fixed at 31.25 kbit/s. The transmission rate on PROFIBUS DP is dependent upon the application and the type of DP-/PA-interface used (segment coupler or link). In addition to the transmission rate, all active participants on the bus must operate with the same bus parameters. For the operating and display program Commuwin II, the bus parameters can be set by using the DPV1-DDE server (submenu Parameter Settings). For FieldCare the bus parameters can be set by using the corresponding Communication-DTM.
Bus address
Transmission rate
Bus parameters
Endress+Hauser
47
4.6
FISCO
To render the proof of Intrinsic Safety as simple as possible, the so-called FISCO model was developed. FISCO stands for Fieldbus Intrinsically Safe COncept. The German PTB (Federal Technical Institute) developed the FISCO model and has published details in Report PTB-W-53 "Examination of intrinsic safety for fieldbus systems. This model is based on the following prerequisites: 1. To transmit power and data, the bus system uses the physical configuration defined by IEC 61158-2. This is the case for PROFIBUS PA. 2. Only one active source is permitted on a bus segment (in this case the segment coupler). All other components work as passive current sinks. 3. The basic current consumption of a bus station is at least 10 mA. 4. It must be ensured for each bus station that Ui > Uo of the segment coupler/power link Ii > Io of the segment coupler/power link Pi > Po of the segment coupler/power link 5. Each bus station must fulfill the following requirement: Ci < 5 nFLi Li < 10 H 6. The permissible line length for EEx ia IIC applications is 1000 m. 7. The permissible spur length for Ex applications is 30 m per spur. The definition of the spur must be observed in this connection (= lines longer than 1 m). 8. The bus cable used must conform to the following cable parameters: Specific resistance: 15 /km < R' < 150 /km Specific inductance: 0.4 mH/Km < L' < 1 mH/km Specific capacitance: 80 nF/km < C' < 200 nF/km (including the shield) Taking the shield into consideration, the specific capacitance is calculated as follows: C' = C'conductor/conductor + 0.5 * C'conductor/shield, if the bus line is potential free or C' = C'shield/shield + C'conductor/shield, if the shield is connected with a terminal of the segment coupler/power link. 9. The bus segment must be terminated on both ends with a fieldbus terminator. According to the FISCO model the terminal bus resistance must conform to the following limits: 90 < R < 100 0 F < C < 2.2 F On condition that the points 1 up to 9 are all satisfied, the proof of intrinsic safety has been provided by means of the FISCO model. Points 1, 3 and 5 are automatically satisfied if a product is certified in accordance with the FISCO model. More information on the planning of PROFIBUS PA systems is to be found in Chapter 5.
48
Endress+Hauser
4.7
Fieldbus multi-drop barriers
When a PROFIBUS PA segment is operated according to FISCO, the segment coupler ensures intrinsic safety by limiting the current available to the bus. This results in the number of devices per segment being limited to a maximum of 10. If the application demands a large number of intrinsically safe devices, a correspondingly large number of Exi segment couplers are required. Multi-drop barriers provide an alternative and more economic solution to such applications.
0 - 10 bar
0 - 10 bar
Exe power supply and conditioner
T
Coupler
MULTIDROP BARRIER Ex e/Ex i
Fig. 4-6: Use of multi-barriers in explosion-hazardous areas - barriers mounted in Zone 1.
The multi-drop barriers are connected to a non-intrinsically safe PROFIBUS segment. In order that the barriers can be mounted and operated in Zone 1, however, the segment is executed to "enhanced safety, Exe" standards. Similarly, the terminals of the barriers are executed to Exe. Multi-drop barriers have several intrinsically safe outputs (usually four) that conform to the FISCO model. The PA slaves connected must be intrinsically safe and certified as FISCO devices. Any externally powered devices must have Exe or Exd power supplies and appropriate connection compartment certification. The barriers offer additional protection of the PROFIBUS PA trunk cable, since they have short-circuit protection. In view of the fact that the trunk cable does not have to be intrinsically safe, the full power of a standard non-Ex coupler can be used on the segment, typically 400 mA, see Chapter 5.2. This means that up to 32 devices can be operated per segment, should this be required.
Endress+Hauser
49
5 PROFIBUS PA Planning
PROFIBUS PA Planning
Various aspects must be taken into consideration when a PROFIBUS-PA segment is planned. Since the importance of each aspect varies from system to system, it is recommended that the following sections are worked through one after the other. If at some point it becomes obvious that a concept cannot be realised, then start the whole procedure again from the beginning with a modified concept. The chapter is structured as follows: Selection of the segment coupler Cable type and length Current consumption Voltage at last device Example calculations for bus design Data quantity Addressing and cycle times
5.1
Selection of the segment coupler
The first step in planning a PROFIBUS-PA system is the selection of the segment coupler according where the segment is to be operated, see also Chapter 2.3.2. Table 5-1 summerises these:.
Zone/Explosion group Zone 0 Segment coupler Remarks
[EEx ia] IIx
Devices that are in installed in Zone 0 must be operated in a segment with type of protection "EEx ia". All circuits connected to this segment must be certified for type of protection "EEx ia". Devices that are in installed in Zone 1 must be operated in a segment with type of protection "EEx ia" or "EEx ib". All circuits connected to this segment must be certified for type of protection "EEx ia" or "EEx ib". If measurements are made in a medium of explosion group IIC, the devices concerned as well as the segment coupler must be certified for explosion group IIC. For media of explosion group IIB, both the devices and the segment coupler can be certified for both group IIC or IIB. Devices that are operated on a non-Ex segment may not be installed in an explosion hazardous area.
Zone 1
[EEx ia] IIx [EEx ib] IIx
Explosion group IIC
IIC [EEx ia] IIC
Explosion group IIB
[EEx ia] IIC [EEx ib] IIB Non-Ex
Non-Ex
Table 5-1: Selection of the segment coupler according to the type of protection and the explosion group of the measured media.
Table 4-3 in Section 4.2.1 lists the couplers currently on the market.
50
Endress+Hauser
5.2
Cable type and length
The bus length is dependent upon the type of protection of the segment and the specification of the cable. In order that the basic requirements for transmission on the IEC 61158-2 (MBP) physical layer are fulfilled and that the inductance and capacitance of the cable can be neglected, the bus length and loop resistance are limited. Table 5-2 lists data from PROFIBUS specifications.
Power supply Application Supply voltage* Max. power* Max. current consumption* Max. loop resistance Type A EEx [ia/ib] IIC 13.5 V 1.8 110 mA 40W Type B EEx [ib] IIB 13.5 V 4.2 280 mA 16W Type C Non-Ex 24 V 9.1 400 mA 39 W
Max. bus segment length Max. spur length
1000 m (EEx ia) 30 m
1900 m 30 m
1900 m see Table 5-3
*see also the technical data supplied by the manufacturer Table 5-2: Standardised power supplies with max. loop resistance and bus length for various applications
Bus length
The bus length is the sum of the length of the trunk cable plus all spurs. A spur is any cable connecting to the trunk line that is over 1 metre in length. If a repeater is used, then the max. permissible length is doubled. The spurs are subject to the following limitations: Spurs longer than 30 m are not permissible in explosion hazardous areas. For non-hazardous applications, the maximum length of a spur is dependent upon the number of field devices, see Table 5-3. Spurs which are shorter than 1 m are treated as connection boxes and are not included in the calculation of the total bus length, provided that they do not together exceed 8 m for a 400 m bus or 2 % of the total length for a longer bus.
No. of field devices Spur length 25-32 1m 19-24 30 m 15-18 60 m 13-14 90 m 1-12 120 m
Spurs
Table 5-3: Max. spur length for non-hazardous applications
Max. cable length (worst case)
The maximum cable length for a particular cable resistance is calculated as follows, whereby the limits in Table 4.4. must be observed: Max. cable length (km) = max. loop resistance of the segment coupler (Table 5-2) specific resistivity of the cable /km If not given, the loop resistance is (/km) = 2 x (1000 /A) whereby = specific resistivity mm2/m und A = core cross-section mm2. Table 4-6 in Chapter 4.3 lists examples for the PROFIBUS-PA cable available from various manufacturers.
Endress+Hauser
51
5.3
Current consumption
The primary factors in determining the number of devices on a segment are the current supplied by the segment coupler and the current consumption of the field devices. For this reason, the current consumption must be calculated for every segment. As a rule of thumb for general planning: Max. 32 devices per segment are permissible in non-hazardous areas (A repeater allows more devices on the segment). Max. 10 devices are permissible in hazardous areas of category ia. For the calculation, the current supplied by the segment coupler IS, the basic current of every device IB and the fault current of every device IFDE must be known. From the electrical point of view, a segment is permissible when: IS ISEG whereby ISEG = IB + max. IFDE
Table 5-4 lists the basic current, the fault current and other specifications of Endress+Hauser devices. The following examples illustrate how the calculation should be made. Empty forms can be found in Appendix A. Device current consumption
Type IB (mA) 11 11 11 11 29 IFDE (mA) 0 0 0 0 5 Supply current from bus from bus from bus from bus from bus Ui (V) 17.5 17.5 17.5 17.5 15 Ii (mA) 500 280 280 280 215 Pi (W) 5.5 4.9 4.9 4.9 1.93 Operating instructions BA222P/00/en BA168P/00/en BA167P/00/en BA164P/00/en --Safety instructions XA096P, XA097P XA004P XA003P XA007F XA093F, ATEX 2150 KEMA 02, ATEX 1109 ATEX 5172X
Cerabar S Cerabar S Deltabar S Deltapilot S FXA164
Levelflex M
11
from bus
17.5
500
5.5
BA243F/00/en
Liquiphant M Liquisys M
11
from bus
30
500
5.5
BA141F/00/en
11
local
non EX 17.5
non EX 280
non EX 4.9
BA209C/07/en
---
Micropilot II
12
from bus
BA176F/00/en, BA202F/00/en BA225F/00/en, BA226F/00/en BA261F/00/en BA143C/07/en
XA013F, XA018F, XA021F XA102F, XA106F
Micropilot M
13
from bus
17.5
500
5.5
Multicap Mycom CPM152 Mycom CPM153 Mypro CXX431 Promag 33 Promag 35
14 11
0 0
from bus local
17.5 17.5
500 280
5.5 4.9
--XA143C, 130849
11
local
17.5
280
4.9
BA298C/07/en
---
11
from bus
17.5
280
4.9
BA198C/07/en
XA173C, 130849
12 12
0 0
local local
30 non EX 30 30
500 non EX 500 500
5.5 non EX 5.5 5.5
BA029D/06/en BA029D/06/en
XA009D ---
Promag 50 Promag 53
11 11
0 0
local local
ATEX E003U ATEX E003U
52
Endress+Hauser
Type
IB (mA) 12 11
IFDE (mA) 0 0
Supply current local local
Ui (V) 30 non EX 30 30
Ii (mA) 500 non EX 500 500
Pi (W) 5.5 non EX 5.5 5.5
Operating instructions BA033D/06/en BA072D/06/en
Safety instructions XA003D ---
Promass 63 Promass 80
Promass 83 Prosonic Flow 93 Prosonic M Prosonic T Prosonic T FMU232 Prowirl 72 Prowirl 77 RID261 Smartec S
11 11
0 0
local local
ATEX E074X ATEX E064X
12 13 17
0 0 0
from bus from bus from bus
17.5 17.5 17.5
500 280 280
5.5 4.9 4.9
BA238F/00/en BA166F/00/en BA166F/00/en
XA175F-A XA008F XA008F, XA035F
15 12 11 11
0 0 0 0
from bus from bus from bus local
17.5 17.5 15 non EX 17.5 17.5
500 280 --non EX 280 500
5.5 4.9 --non EX 4.9 5.5
BA085D/06/en BA037D/06/en BA098R06/en BA213C/07/en
XA071DA3 EX038D XA002R, E062 ---
TMD834 TMT184
13 11
0 0
from bus from bus
BA090R06/en BA115R06/en
EX-98.D.089 XA008R
Table 5-4: PROFIBUS PA data of Endress+Hauser devices
Endress+Hauser
53
5.4
Voltage at last device
The resistance of the cable causes a voltage drop on the segment that is greatest at the device farthest from the segment coupler. It must be checked whether an operating voltage of 9 V (for FEB 24 P in Zone 0 9.6 V) is present at this device. There are two ways of doing this: Worst case calculation: if the resulting voltage is over 9V, then the segment will work in all cases Accurate calculation: this calculation takes into account the actual physical distribution of the devices and should be used if the worst case calculation gives a voltage less than 9V
5.4.1
Worst case calculation
The worst case assumes that all devices are located at the end of the bus. The equivalent curcuit diagram is shown in Fig. 5.1
ISEG RL I1 Segment coupler UL US >9V In I2
Fig. 5-1: Voltage calculation and line length (Example 1)
Voltage
The length of the bus is known, the voltage at the last device is to be calculated. Ohm's law is used: UB = US (ISEG x RSEG) whereby: UB = Voltage at last device US = Output voltage of the segment coupler (manufacturer's data) ISEG = Current consumed on the segment (IB + max. IFDE, see Section 4.3) RSEG = Cable resistance = bus length x specific resistance
Bus length
The bus length is to be calculated from given conditions on the bus. A PROFIBUS PA slave requires at least 9 V to function properly (for FEB 24 P in Zone 0 9.6 V). The following applies to the maximum voltage drop over the bus: ULmax = US - 9 V where ULmax = the maximum permissible voltage drop over the bus US = Output voltage of the segment coupler (manufacturer's data)
The corresponding line length in metres L = 1000 x ULmax / [ISEG x ] where metres
ISEG = Current consumed on the segment in amps (IB + max. IFDE, see Section 4.3) = specific resistivity of the bus cable in /km
54
Endress+Hauser
5.4.2
Accurate calculation
This calculation takes into account the actual distribution of the devices on the bus. The equivalent circuit is shown in Fig. 5-2,where: RLx = line resistance of line segment x in and In = current consumption of PA station n in amps
L2 L2 L1 RL1 RL2
Segment coupler US
i1
I2 >9V
In
Fig. 5-2: Voltage calculation and line length (Example 2)
Each station causes a voltage drop on the length segment through which its power supply current flows. For the first station, this would be: URL1 = = where I1 x RL1 I1 x L1 x ;
= the specific resistance bus cable in /km L1 = length of line segment 1 in km, measured from the terminals of the coupler
For the second station, the following applies: URL2 = = I2 x (RL1 + RL2) I2 x L2 x
In general, the voltage drop over the entire bus segment URL is: n URL = x [Ix x Lx] x=1 The segment is in order when: URL = US - 9 V where Us is the supply voltage
If the condition described above is not fulfilled, the bus has be shortened or a cable with reduced specific resistivity has to be used or the number of devices on the segment must be reduced.
Endress+Hauser
55
5.5
5.5.1
Calculation examples for bus design

Example 1: Non-hazardous application
Calculation example for a PROFIBUS PA segment in a non-hazardous area with the architecture shown in Fig. 4.3. Used components: Segment coupler non-hazardous area: Siemens, Is = 400 mA, Us = 19 V. Cable: Lapp, specific resistance of cable = 44 /km
Segment coupler, non-hazardous Us = 19 V IS = 400 mA 20 m 15 m 20 m 20 m 15 m 20 m 20 m 7m 5m 7m 7m 5m
Trunk cable 40 m
UB = 17.81 V
Fig. 5-3: Example 1: Bus installed in non-hazardous area
Cable length (worst case)
Spur
Max. loop resistance, non-hazardous area (see Table 5-2) Specific resistance of cable Max. length (m)= 1000 x (loop resistance/specific resistance) 1000 x (39 /44 ) =
39 44 /km 886 m
Length of trunk cable Total length of spurs Total length of cable (= trunk cable + spurs) LSEG
60 m 141 m 201 m
Total length of cable LSEG 201 m < Max. length 886 m
OK!
Table 5-5: Cable length (worst case) non-hazardous area
56
Endress+Hauser
Current consumption
No. 1 2 3 4 5 6 7 8 9 10 11 12
Device Promass 83 Positioner Levelflex M TMT 184 Promass 83 Positioner Promass 83 Positioner Levelflex M TMT 184 Promass 83 Positioner
Manufacturer Endress+Hauser Endress+Hauser Endress+Hauser Endress+Hauser Endress+Hauser Endress+Hauser Endress+Hauser Endress+Hauser
Tag FIC122 FV121 LIC124 TIC123 FIC126 FV125 FIC222 FV221 LIC224 TIC223 FV226 VIC225
Basic current 11 mA 10 mA 11 mA 11 mA 11 mA 10 mA 11 mA 10 mA 11 mA 11 mA 11 mA 11 mA 6mA
Fault current 0 mA 0 mA 0 mA 0 mA 0 mA 6 mA 0 mA 0mA 0 mA 0 mA 0 mA 4 mA
Max. fault current (max. IFDE)
Current consurption ISEG = IB + max. IFDE Output current of segment coupler Is Is IB + max. IFDE ?
135 mA 400 mA Yes OK!
Table 5-6: Current consumption (non-hazardous area)
Output voltage of segment coupler US (manufacturers data) Specific resistance of cable RK Total length of cable LSEG Resistance of cable RSEG = LSEG x RK Current consumption of segment ISEG Voltage drop UA = ISEG x RSEG Voltage at last device UB = US - UA 44 /km
19.00 V
201 m 8.844
135 mA
1.19 V
17.8 V
9V
Table 5-7: Voltage at last device (non-hazardous area)
OK!
Conclusion
Result of the calculations: Cable length: OK Current consumption: OK Voltage at last device: OK From the point of view of the architecture, the segment in Example 1 can be operated with a standard segment coupler with an output current of 400 mA.
Endress+Hauser
57
5.5.2
Example 2: EEx ia application
In Examples 2 and 3, the PROFIBUS PA segment is to operate in an explosion hazardous area. In accordance with the FISCO model, the devices are operated on two separate segments with type of protection EEx ia for Zone 0 and EEx ib for Zone 1. Calculations are made for both segments. Specimen calculation for a bus operating in a hazardous area Zone 0 with the architecture shown in Fig. 5-4. Segment coupler [EEx ia] IIC: P+F, Is = 100 mA, Us = 13 V. Cable: Siemens, specific resistance of cable = 44 /km, max. bus length = 1000 m.
Segment coupler [EEx ia] IIC IS = 100 mA US = 13 V
EEx ib Trunk cable 50 m 5m 5m EEx ia
15 m
Fig. 5-4: Example 2: Calculation of the segment EEx ia, Bus installed with routing to Zone 0 (EEx ia) and Zone 1 (EEx ib)
Spur
Max. loop resistance, EEx (see Table 4.3) Specific resistance of the cable Max. length (m)= 1000 x (loop resistance/specific resistance) 1000 x (40 /44 ) =
40 44 /km 909 m
Length of trunk cable Total length of spurs Total length of cable (= trunk cable + surs) LSEG
50 m 40 m 90 m
Total length of cable LSEG 90 m < Max. length 909 m
OK!
Table 5-8: Cable length (worst case) EEx ia area
58
15 m
Endress+Hauser
Current consumption
Nr. 3 4 9 10
Device Deltapilot S TMT 184 Deltapilot S TMT 184
Manufacturer Endress+Hauser Endress+Hauser Endress+Hauser Endress+Hauser
Tag LIC124 TIC123 LIC224 TIC223
Basic current 11 mA 11 mA 11 mA 11 mA 0 mA
Fault current 0 mA 0 mA 0 mA 0 mA
Ma. fault current (max. IFDE)
Current consumption ISEG = IB + max. IFDE Output current of segment coupler Is Is IB + max. IFDE ?
44 mA 100 mA Yes OK!
Table 5-9: Current consumption (EEx ia area)
Output voltage of segment coupler US (manufacturers data) Specific resistance of cable RK Total length of cable LSEG Resistance of cable RSEG = LSEG x RK Current consumption of segment ISEG Voltage drop UA = ISEG x RSEG Voltage at last device UB = US - UA 44 /km 90 m 3.96 44 mA
13.00 V
0.17 V
12.83 V
9 V?
*the operating voltage for the FEB 24 P in Zone 0 is 9.6 V Table 5-10: Voltage at last device (EEx ia area)
OK!
Conclusion
Result of the calculations: Cable length: OK Current consumption: OK Voltage at last device: OK From the point of view of the architecture, the segment in Example 2 can be operated with an EEx ia segment coupler with an output current of 100 mA.
Endress+Hauser
59
5.5.3
Example 3: EEx ib application
Specimen calculation for a bus operating in a hazardous area Zone 1 with the architecture shown in Fig. 5-5. Segment coupler [EEx ia/ib] IIC: P+F, Is = 100 mA, Us = 13 V. Cable: Siemens, specific resistance of cable = 44 /km
Segment coupler [Ex ia/ib] IIC IS = 100 mA US = 13 V
UB = 12.31 V
Trunk cable 60 m
EEx ib EEx ia
7m
7m
7m 20 m 20 m Spur
7m
Fig. 5-5: Example 3: Calculation of the segment EEx ib, Bus installed with routing to Zone 0 (EEx ib) and Zone 1 (EEx ia)
Max. loop resistance, EEx (siehe Tabelle 4.3) Specific resistance of cable Max. length (m)= 1000 x (loop resistance/specific resistance) 1000 x (40 /44 ) =
16 44 /km 363 m
Length of trunk cable Total length of spurs Total length of cable (= trunk cable + spurs) LSEG
60 m 108 m 168 m
Total length of cable LSEG 168 m < Max. lenght 363 m
OK!
Table 5-11: Cable length (worst case) EEx ib area
60
20 m
20 m
Endress+Hauser
Current consumption
No. 1 2 5 6 7 8 11 12
Device Promass 83 Positioner Promass 83 Positioner Promass 83 Positioner Promass 83 Positioner
Manufacturer Endress+Hauser Endress+Hauser Endress+Hauser Endress+Hauser
Tag FIC122 FV121 FIC126 FV125 FIC222 FV221 FIC226 FV225
Basic current 11 mA 13 mA 11 mA 13 mA 11 mA 13 mA 11 mA 13 mA 6 mA
Fault current 0 mA 0 mA 0 mA 6 mA 0 mA 0 mA 0 mA 6 mA
Max. fault current (max. IFDE)
Current consumption ISEG = IB + max. IFDE Output current of segment coupler Is (EEx ia IIC) Is IB + max. IFDE ?
102 mA 100 mA no impossible!
Output current of segment coupler Is (EEx ia IIB) Is IB + max. IFDE ?
<=280 mA Yes OK!
Table 5-12: Current consumption (EEx ib area)
Output voltage of segment coupler US (manufacturers data) Specific resistance of cable RK Total length of cable LSEG Resistance of cable RSEG = LSEG x RK Current consumption of segment ISEG Voltage drop UA = ISEG x RSEG Voltage at last device UB = US - UA 44 /km 168 m 7.39 102 mA
13.00 V
0.75 V
12.25 V
9 V?*
*the operating voltage for the FEB 24 P in Zone 0 is 9.6 V Table 5-13: Voltage at last device (EEx ia area)
OK!
Conclusion
Result of the calculations: Cable length: OK Current consumption EEx ia not permissible, EEx ib: OK Voltage at last device: OK
Endress+Hauser
61
Alternatives
The result for a segment with type of protection EEx ib and a segment coupler EEx ia IIC is negative. A segment coupler with type of protection EEx ib IIB would be permissible but at the moment there is none on the market. Two possible alternatives are shown in Fig. 5-5: Version A: two segments with type of protections EEx ib are routed to one tank each. In this case, the current consumption is reduced to 56 mA. A segment coupler with type of protection EEx ia IIC is adequate for this requirement. Version B: only circuits with type of protection EEx ia are connected to the bus. The plant can then be equipped with two segments with type of protection EEx ia. The current consumption per segment is 80 mA. VersionC: Einsatz von Feldbusbarrieren und einem Segmentkoppler in Nicht-Ex-Ausfhrung.
Segment coupler 3x [EEx ia] IIC EEx ib EEx ib EEx ia
Segment coupler 2x [EEx ia] IIC
EEx ib EEx ia
Fig. 5-6: Example 4: Alternative architectures: Version A two segments withdgree of protection EEx ib IIC Version B two segments withdgree of protection EEx ia IIC T: Terminator
62
Endress+Hauser
5.5.4
Example: fieldbus barrier application
0 - 10 bar
0 - 10 bar
Exe power supply and conditioner
T
Coupler
Fig. 5-7: Use of multi-barriers in explosion-hazardous areas - barriers mounted in Zone 1.
Pepperl+Fuchs barrier
The Fieldbarrier from Pepperl+Fuchs is used to connect up to 4 intrinsically safe PROFIBUS PA devices to a non-intrinsically safe PROFIBUS PA segment. When the Fieldbus barrier is mounted in an hazardous area, Zone 1, the PROFIBUS PA trunk has to be realised to Exe "increased safety" standards. The Fieldbus barrier outputs are intrinsically safe and correspond to the requirements the FISCO Model. The trunk is galvanically separated from the outputs. No terminators are required on the barrier output lines. The complete bus must satisfy the functional considerations cable length, voltage at last device and current consumption as shown in Examples 1 to 3. The technical safety considerations are based on the entity concept. In contrast to the standard Ex i concept, however, the technical safety calculation is made for each individual multidrop barrier. The devices are considered safe if the junction box output characteristics (Uo, Io, Po, Co, Lo) do not exceed the input parameters of the field devices (Ui, Ii, Pi, Ci, Li) and the inductance and capacitance are within the permissible limits. FISCO devices always conform to these requirements. The output characteristics are as follows: Input voltage16 V ... 32 V Output voltage 0 V Output current 40 mA Spur length 120 m in safe areas, 30 m in hazardous areas
The total spur length varies according to the manner in which the the barriers are connected to the trunk line: For daisy chains or connections to the trunk less than one metre, each output line on the barrier counts as a spur from the trunk For connections to the trunk greater than one metre, the connection and all output lines count as one spur and their total length is limited according to Table 5-3, whereby the total length in Ex areas must be less than or equal to 30 m. Dimensioning tool To simplify dimensioning of a fieldbus segment, Pepperl+Fuchs has developed a software tool that makes the necessary calculations. This can be downloaded from the Pepperl+Fuchs home page www.pepperl-fuchs.com free of charge.
Endress+Hauser
63
5.6
Data quantity
If the participants communicate directly with the PROFIBUS DP master through a segment coupler, then the amount of data exchanged sets no limits to the design of the PROFIBUS PA segment. If a link is used as interface to the PROFIBUS DP system, however, the amount of data that can be stored in the I/O buffer is limited. According to the PROFIBUS specification, the maximum telegram length is 244 byte of input data and 244 byte for output data. The system itself may, however, support less: always check the manufacturers specifications!
Specifications in byte
Link, non-hazardous area Amount of data 44...284 bytes to PLC
0...45
0...45
0...12
0...45
0...12
0...45
0...12
Fig. 5-8: Example1: Bus installed in non-hazardous area
Example: data quantity
Take Example 1 in Fig 5-8: can a link be used? The data for Endress+Hauser devices is to be found in Table 5-15,overleaf.
Device No. 1, 5, 7, 11 3, 9 4, 10 I 5-45 5-10 5 0 0-12 0-5 0-5 Imin 20 10 10 Imax 180 20 10 Omin 0 0 0 Omax 48 10 10 Amount of data I : 40-258 Bytes O : 20-88 Bytes
Positioner No. 2, 6, 8, 12 0-12 5 0 48 20 20
Table 5-14: Example: Data quantity of a PROFIBUS PA segment
Depending upon the device configuration, from min. 40 bytes to max. 258 bytes (Inputs) and min. 20 bytes to max. 88 bytes (Outputs) are periodically exchanged with the PLC. In the case of a link, the data are transmitted to the PLC in a telegram. The telegram length is limited: a) by the buffer size of the link, e.g. 244 bytes, b) by the max. telegram length of the PLC, e.g. 122 bytes c) by the PROFIBUS-PA specification 244 bytes. It can seen that the use of a link is determined by the configuration of the field devices, see Chapter 3.4 and the system components used. Should the maximum configuration or 258 bytes be required, a link could not be used.
64
bytes per device
Endress+Hauser
0...12
Endress+Hauser devices
Type
Cycle data
Data amount PLC
Response time
Blocks
Inputs
Outputs
depending on configuration 10...11.3 ms
PB*
TB**
FB***
Cerabar M
Pressure 2. cycle value(1) Display value(1) Pressure 2. cycle value(1) Display value(1) Differential pressure 2. cycle value(1) 3. cycle value(1) Display value(1) Pressure/Level 2. cycle value(1) Display value(1) Level limit Level 2. cycle value(1) Display value(1) Level limit pH Value Temperature O2 Temperature Turbidity Temperature Conductivity Temperature Chlorid Temperature pH Value Redox
5 Byte 5 Byte --5 Byte 5 Byte --5 Byte 5 Byte 5 Byte --5 Byte 5 Byte --2...8 Byte 5 Byte 5 Byte --2 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte --5 Byte 5 Byte --5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte
----5 Byte ----5 Byte ------5 Byte ----5 Byte ------5 Byte --------------------------------5 Byte ----5 Byte -------------
1 AI
Cerabar S
10...11.3 ms
1 AI
Deltabar S
10 ms...12.6 ms
1 AI
Deltapilot S
10...11.3 ms
1 AI
FXA 164 Levelflex M
10...13.9 ms 10...11.3 ms
1 1
4 1
4 DI 1 AI
Liquiphant M Liquisys M
10 ms 11.3 ms
1 1
1 ---
1 DI 1 AI
11.3 ms
---
1 AI
11.3 ms
---
1 AI
11.3 ms
---
1 AI
11.3 ms
---
1 AI
Micropilot II Micropilot M
Level Level 2. cycle value(1) Display value(1) Level Temperature Display value(1) pH Value Temperature Conductivity (ind.) Temperature Conductivity (kond.) Temperature
10 ms 10...11.3 ms
1 1
1 1
1 AI 1 AI
Multicap
10...11.3 ms
1 AI
Mycom II
11.3 ms
---
1 AI
11.3 ms
---
1 AI
11.3 ms
---
1 AI
Mycom S
Endress+Hauser
65
pH
pH Value 1 Temperature 1(1) pH Value 2 Temperature 2(1) Control CLM(1)
5 Byte 5 Byte 5 Byte 5 Byte --5 Byte 5 Byte 5 Byte 5 Byte --5 Byte 5 Byte 5 Byte 5 Byte ----5 Byte 5 Byte(1) 5 Byte 5 Byte(1) 5 Byte 5 Byte --5 Byte 5 Byte ----5 Byte 5 Byte 5 Byte 5 Byte 5 Byte ----5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte --5 Byte 5 Byte 5 Byte 5 Byte 5 Byte -----
--------2 Byte --------2 Byte --------2 Byte 2 Byte --------1 Byte
10...15.2 ms
4 AI
Lf (ind.)
Conductivity 1 (ind.) Temperature 1(1) Conductivity 2 (ind.)(1) Temperature 2(1) Control CLM(1)
10...15.2 ms
4 AI
Lf (kond.)
Conductivity 1 (kond.)(1) Temperature 1(1) Conductivity 2 (kond.)(1) Temperature 2(1) Control CPM(1) Control CPC(1)
10...15.2 ms
4 AI
Mypro
Conductivity Temperature(1) pH Value Temperature(1)
10...11.3 ms
1 AI
10...11.3 ms
1 AI
Promag 33/ 35
Mass flow Totalizer(1) Control(1) Mass flow Totalizer(1) Control(1) Display value(1) Mass flow Totalizer 1 (1) Totalizer 2(1) Totalizer 3(1) Volumetric flow(1) Control(1) Display value(1) Mass flow Totalizer 1 (1) Temperature(1) Density(1) Totalizer 2(1) Volumetric flow(1) Standard mass flow(1) Target medium flow(1) Carrier medium flow(1) Calculated density(1) Control(1) Mass flow Volumetric flow(1) Density(1) Temperature(1) Totalizer(1) Display value(1) Control(1)
10...11.3 ms
1 AI 1 TOT
Promag 50
--2 Byte(1) 1 Byte 5 Byte --2 Byte(1) 2 Byte(1) 2 Byte(1) --1 Byte 5 Byte --------------------1 Byte --------2 Byte(1) 5 Byte 1 Byte
10...11.3 ms
1 AI 1 TOT
Promag 53
10...15.2 ms
2 AI 3 TOT
Promass 63
10...21.7 ms
8 AI 2 TOT
Promass 80
10...15.2 ms
4 AI 1 TOT
66
Endress+Hauser
Promass 83
Mass flow Volumetric flow(1) Standard mass flow(1) Density(1) Standard density(1) Temperature(1) Totalizer 1(1) Totalizer 2(1) Totalizer 3(1) Display value(1) Control(1) "Volumetric flow or calculated mass flow or standard mass flow" Totalizer(1) Control(1) Flow Totalizer(1) Control(1) Volumetric flow Speed of sound(1) Flow rate1) Totalizer 1(1) Display value(1) Control(1) Flow (optional 11 measured variables)(1) Totalizer 1(1) Totalizer 2(1) Totalizer 3(1) Display value(1) Control(1) Level 2. cycle value(1) Display value(1) Level Display Conductivity Temperature(1) MRS(1) Temperature Temperature Display value
5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte 5 Byte ----5 Byte
------------2 Byte(1) 2 Byte(1) 2 Byte(1) 5 Byte(1) 1 Byte(1) ---
10...20.4 ms
6 AI 3 TOT
Prowirl 72
10...11.3 ms
1 AI 1 TOT
5 Byte --5 Byte 5 Byte --5 Byte 5 Byte 5 Byte 5 Byte ----5..40 Byte 5 Byte 5 Byte 5 Byte ----5 Byte 5 Byte --5 Byte --5 Byte 5 Byte --5 Byte 5 Byte ---
2 Byte(1) 1 Byte ----1 Byte ------2 Byte(1) 5 Byte 1 Byte --2 Byte(1) 2 Byte(1) 2 Byte(1) 5 Byte 1 Byte ----5 Byte --------2 Byte ----5 Byte 10...11.3 ms 1 1 1 AI 10...11.3 ms 1 1 1 AI 1 TOT
Prowirl 77
Prosonic Flow 90
10...13.9 ms
3 AI 1 TOT
Prosonic Flow 93
10...23 ms
8 AI 3 TOT
Prosonic M
Prosonic T RID 261 Smartec S
10 ms --10...11.3 ms
1 --1
1 --2
1 AI --2 AI
TMD 834 TMT 184
10 ms 10 ms
1 1
1 1
1 AI 1 AI
(1)
Optional * PB = Physical Block ** TB = Transducer Block *** FB = Function Block with AI = Analog Input, DI = Discrete Input and TOT = Totalizer
Table 5-15: PROFIBUS PA data of Endress+Hauser devices
Endress+Hauser
67
5.7
5.7.1
Addressing and cycle times

Addressing
Every device in the bus system is assigned a unique address. Valid addresses lie in the range 0...126, whereby 126 is the address of the delivery status. If the address is not set correctly, the device cannot communicate. Networks with coupler or gateway The PLC is able to assign up to 126 (0...125) addresses to individual participants at the bus. A device address may appear only once within a particular PROFIBUS DP system. If a segment coupler is used, then the addresses assigned to the PROFIBUS PA devices count as PROFIBUS DP addresses. For a typical bus configuration with PLC and PC, the addresses are assigned as follows: the PLC is assigned an address (Class 1 master), typically address 1 the PC or operating tool is assigned an address (Class 2 master), typically address 0 or 2 the other addresses are assigned to the field devices. Networks with links Links act as PROFIBUS DP slaves and receive their own address. The PROFIBUS PA field devices connected to link, however, form a separate PROFIBUS PA system. These are addressed separately. The PROFIBUS DP addresses are assigned as follows: the PLC is assigned an address (Class 1 master), typically address 1 the PC or operating tool is assigned an address (Class 2 master), typically address 0 or 2 every link is assigned an address (e.g. addresses 3, 4, 5, 6, ...) the rest of the addresses are assigned to the other field devices that are connected to transporent segment couples or directly to the PROFIBUS DP system.
On the PROFIBUS PA side, the field devices connected to the link are assigned a unique address for the PROFIBUS PA segment of which they are part. They are not counted as part of the PROFIBUSDP system every device is assigned an address between 3 and 125, the addresses 0, 1 and 2 cannot be assigned when the link is operating together with a standard master. Examples for addressing are to be found in Sections 5.7.3 to 5.7.5
5.7.2
Cycle times
The cycle times must also be considered when the PROFIBUS PA segment is planned. Data exchange between a PLC (a Class 1 master) and the field devices occurs automatically in a fixed, repetitive order. The cycle times determine how much time is required until the data of all the devices in the network are updated. The more complex a device, the greater the amount of data to be exchanged and the longer the response time for the exchange between PLC and device. Table 5-15 summarises the amount of data and the response times for Endress+Hauser devices. The total cycle time for the updating of network data is calculated as follows: Total cycle time = Sum of the cycle times of the field devices + internal PLC cycle time + PROFIBUS-DP transmission time
When links or the transparent SK2 segment coupler are used, the total cycle time of a system can be reduced.
68
Endress+Hauser
5.7.3
Example 1: Siemens segment coupler

CPU 100 ms DP master address A 1 Operating tool e.g. FieldCare address A 2
Power supply
PROFIBUS DP Standard segment coupler
45.45 kbit/s Ex segment coupler Ex segemnt coupler
A8
A 14 A 15 PROFIBUS PA
A3 PROFIBUS PA PROFIBUS PA A4
A9
A 10
A 16
A5
A 11
A 17 A 18
A6
A 12
A7
A 13
A 19
Non-hazardous area
Fig. 5-9: Network example for Siemens segment coupler
Siemens segment couplers 6ES7-157-0 AD81-0XA0 and 6ES7-157-0 AC80-0XA0, see Table 4-3, can be used by any PROFIBUS DP master (PLC or process control system) that supports a baudrate of 45.45 kbit/s. In the example, two couplers for hazardous areas and one for non-hazardous areas are used. A maximum of 126 (0 - 125) addresses can be given to the participants, since The segment coupler is transparent. 124 addresses are available for assignment to the field devices. The addresses 3 - 19 are used. The transmission rate is 45.45 kBit/s.
The cycle time for the following example is: (cycle time of the devices) + PLC cycle time (ca. 100 ms) = 17 x 10 ms + 100 ms = 270 ms
Note! For PROFIBUS DP alone, the DP transmission time must also be considered. The (bus) cycle time is the time period required under worse case conditions for the changes in input data to be transmitted to the master and the changes in output data to the slaves
Endress+Hauser
69
5.7.4
Example 2: Pepperl+Fuchs SK1 coupler

Power supply
PROFIBUS DP Standard segment coupler
93.75 kbit/s Ex segemnt coupler Ex segemnt coupler
A8
A 14 A 15 PROFIBUS PA
A3 PROFIBUS PA PROFIBUS PA A4
A9
A 10
A 16
A5
A 11
A 17 A 18
A6
A 12
A7
A 13
A 19
Non-hazardous area
Fig. 5-10: Network example for Pepperl+Fuchs segment coupler SK1
The Peppert+Fuchs segment couplers KFD2-BR-EX1.PA and KFD2-BR-1PA.93, see table 4-3, can be used by any PROFIBUS DP master (PLC or process control system). The Segment coupler SK1 supports both cyclic and acyclic data exchange. It can thus be used in all common PLC or process control systems. In the example, two couplers for hazardous areas and one for non-hazardous areas are used. A maximum of 126 (0 - 125) addresses can be given to the participants, since the segment coupler is transparent. 124 addresses are available for assignment to the field devices. The addresses 3 - 19 are used. The transmission rate is 93.75 kbit/s. The cycle time for the following example is: (cycle time of the devices) + PLC cycle time (ca. 100 ms) = 17 x 10 ms + 100 ms = 270 ms
Note! For PROFIBUS DP alone, the DP transmission time must also be considered. The (bus) cycle time is the time period required under worse case conditions for the changes in input data to be transmitted to the master and the changes in output data to the slaves
70
Endress+Hauser
5.7.5
Power supply
Example 3: Pepperl+Fuchs SK2 coupler

PROFIBUS DP Standard power link Gateway Gateway
...12 Mbit/s Ex power link Gateway Ex power link
PA 7 PA 8 PROFIBUS PA
PA 20
PA 23 PA 24
PROFIBUS PA
PA 3 PA 4
PA 12
PA 9 PA 10
PA 13 PA 18 PA 14
PA 21 PA 25 PA 26 PA 22
PA 5 PA 11 PA 6
PA 19 PA 15
Segment 1 Non-hazardous area
Segment 2 Explosion hazardous area
Segment 3
Fig. 5-11: Network example for Pepperl+Fuchs segment coupler SK2
The segment coupler SK2 (KLD2-PL(2)-1.PA with gateway KLD-GT-DP.1PA or KLD2-PL(2)Ex1.PA with gateway KLD-GT-DP.1PA) supports both cyclic or and acyclic data exchange of the PROFIBUS DP V1 protocol. In the example, three segment couplers SK2 are used: two couplers for hazardous areas and one for non-hazardous areas. All data that is to be updated cyclically is automatically updated in the common data area by the PROFIBUS PA master. The update time depends on the data volume transferred via the PROFIBUS PA channel. Cycle time From the point of view of PROFIBUS DP, the segment coupler represents a multi-slave device. If the PROFIBUS DP Master sends a request to a slave address existing at the segment coupler, the gateway answers directly on the request with the data, that are stored in the common data range. Through this behavior, the PROFIBUS DP master does not need to wait for the PROFIBUS PA slave to respond. The result of this is that the cycle time of the entire system is calculated as follows: tCycle = tCycle_PA-channel + tCycle_DP The time tCycle_PA-channel can be estimated as follows: tCycle_PA-channel = 10 ms + n*10,5 ms + 0,256 ms*(LE + LA) where n = the number of PROFIBUS PA slaves LE = total number of input bytes of all PROFIBUS PA slaves on the channel. LA = total number of output bytes of all PROFIBUS PA slaves on the channel.
Endress+Hauser
71
DP cycle time
The time tCycle_DP can be estimated as follows: tCycle_DP = TBit * n * 500 + 11*TBit*(LE +LA) where n = the number of PROFIBUS DP/PA slaves LE = total number of input bytes of all PROFIBUS slaves LA = total number of output bytes of all PROFIBUS slaves TBit = bit time = 1/transfer rate
For the time tCycle_DP a safety add-on of 10% should be included in the calculation in accordance with the PROFIBUS User Organization. The equation above applies given the following pre-conditions: The PROFIBUS DP network is operated as a monomaster system, i. e. there is only one master on the PROFIBUS DP. If you want to use a multimaster system, the token hold time and the corresponding pause times of the additional masters must be added to the total. Only acyclic data exchange takes place. If the master is also supposed to transfer acyclic telegrams, the time required for acyclic communication must be added in total. Example The cycle time for the example in Fig. 5.11 is: 1 (Cycle time of the PA network) = PA segment 1 + PA segment 2 + PA segment 3 where 1 = cycle PA segment 1 + cycle PA segment 2 + cycle PA segment 3 1 = (10 ms + n*10.5 ms + 0.256 ms*(50)) + (10 ms + n*10.5 ms + 0.256 ms*(40)) + (10 ms + n*10.5 ms + 0.256 ms*(90)) 1 = 117.3 ms + 104.24 ms + 106.54 ms 1 = 328.08 ms 2 (Cycle time of the DP PLC) where
2 = ------ Mbit \s 24 500 + 11 ------ Mbit \s 180 + 100m\s 12 12

1 1
2 = 1.165 ms + 100 ms 2 = 101.165 ms tcycle = 1 + 2 = approx 430 ms
72
Endress+Hauser
5.7.6
Power supply
Example 4: Siemens PA link

PROFIBUS DP Standard segment coupler A3 Link Link A4
...12 Mbit/s Ex segment coupler A5 Link Ex segment coupler
PA 3
PA 6 PA 7
PROFIBUS PA
PA 3 PA 4
PA 3
PA 9 PA 10
PA 4 PA 9 PA 5
PA 4 PA 8 PA 9 PA 5
PA 5 PA 11 PA 6
PA 10 PA 6
Segment 1 Non-hazardous area
Segment 2 Explosion hazardous area
Segment 3
Fig. 5-12: Network example for Siemens DP/PA-link
The Siemens PA-link (6ES7-157-0 AD81-0XA0 with link 6ES7-157-0AA82-0XA0 or 6ES7-157-0 AC80-0XA0 with link 6ES7-157-0AA82-0XA0) can be used by any PROFIBUS DP master (PLC or process control system). Three links are used in the example, each with two segment couplers A maximum of 126 addresses can be assigned to the participants on the PROFIBUS DP system. A maximum of 122 PA addresses (address range 3 - 125) can be assigned in the PROFIBUS PA segments connected to each link. The PROFIBUS DP addresses 3 -5 are used to address the links. In the PROFIBUS PA segments, the addresses 3-11, 3-10 and 3-9 are used for the PA devices, whereby addresses 0 - 2 is reserved for the link in each case and not useable for PA devices. The transmission rate may be up to 12 Mbit/s. The cycle time for the example is: 1 (Cycle time of the PA devices) PA segment1: 9 x 10 ms = 90 ms PA segment 2: 8 x 10 ms = 80 ms PA segment 3: 7 x 10 ms = 70 ms 2 (Cycle time of the DP devices up to 12 Mbit/s) + PLC cycle time (ca. 100 ms) 3 x 1 ms + 100 ms = 103 ms
Note! For PROFIBUS DP alone, the DP transmission time must also be considered.
Endress+Hauser
73
6 Installation PROFIBUS PA
Installation PROFIBUS PA
The chapter contains information on physical installation of the network. It contains the following sections: Cabling Grounding and shielding Termination Overvoltage protection Installation of the devices Setting the address
6.1
Cabling
When installing a PROFIBUS network, particular attention must be paid to the cabling. This covers both choice of cabling, see below, and the way in which the cables are laid in the plant. Thus by careful routing, e.g. avoidance of potential sources of intense electromagnetic interference, use of metal trays or separation of power and bus cables in the cable tray, a significant contribution can sometimes be made to the fault-free running of the bus. PROFIBUS DP On the PROFIBUS DP side it is usual to make connections via a screw terminals or 9-pin DIN connectors. Cable specifications are listed in Tables 3-3 and 3-7 in Chapter 3 and suitable cables are to be found on the market for PROFIBUS DP or RS-485 applications. Junction boxes, terminators and other connection equipment are also available. The connection to the segment coupler or link is usually by means of screw terminals. For the connection of devices and spurs to the trunk cable, the customer has following choices: T-box with screw terminals or M12 connectors Junction boxes with screw terminals or M12 connectors Field barriers with M12 connectors Chapter 4, Tables 4-4 and 4-5 contain cable specifications and Table 4-6 a list of manufacturers (partial). PROFIBUS PA cables are available on the market for both safe and FISCO applications, and cord sets with M12 connectors are readily available in different lengths. In all cases, however, care must be taken regarding the continuity of the screening and the correct termination of the segment. For this reason, it is important to consider the grounding scheme to be adopted, before equipment is purchased.
PROFIBUS PA
Note! Where the network is operating in explosion hazardous areas, it is important to remember that all equipment, including cables, connecting units, terminators etc., has the appropriate certification. For PROFIBUS PA, the use of FISCO equipment simplifies proof of intrinsically safety. The M12 connector cannot be used for four-wire EEx d devices and only under certain conditions for EEx e devices. Endress+Hauser offer a number of products and accessories for PROFIBUS PA. For more information, please ask for the documentation "Instrumnetation aids and accessories for PROFIBUS.
74
Endress+Hauser
6.2
Grounding and shielding
This section describes three possible grounding and shielding schemes for a PROFIBUS PA network. Full isolation Installation with multiple grounding Capacitive isolation The difference between the schemes lies in the grounding of the bus cable shield. In one case it is connected to a separate ground and in the other integrated into the general plant grounding system. Plant grounding schemes also differ according to national and or local practice. For example, British practice is neutral star earth bonding, German practice is the use of a potential equalisation line and Americans often run cables in grounded steel conduits and enclose control equipment in steel cabinets.
Central grounding
Potential matching line
Fig. 6-1: Device grounding schemes: In neutral star earth bonding it is assumed that the device is electrically connected to the tank via the process connection. The Tanks are grounded at a central grounding point.
In German practice, each device is connected directly to a thick potential equalisation line which runs throughout the plant and is connected to a single grounding point. The purpose of grounding the shielding is to protect the digital signals on the fieldbus from highfrequency electromagnetic interference caused, e.g., by cellular telephones or harmonics from frequency converters and other plant equipment. It can be seen, therefore, that local installation practice may also have some influence on the suitability of a particular scheme. The conditions for transmission may also be poorer in extensive networks or in networks with many branches. Finally, Ex considerations may rule out some schemes in some countries. Applicability The grounding schemes shown overleaf assume that the T-boxes/junction boxes are serving plant sections that are some distance from each other and the control room, making it likely that each is connected to a different earth potential. They address the problem of preventing current loops developing within the cable shield, should a multiple grounding scheme be chosen, see Fig. 6-2. For simplicity, the wiring is shown with screw terminals. If a M12 connector is used, the device connection compartment should be opened to check whether the shield wire is already connected to the internal device grounding terminal. If this is the case, it must be detached and isolated, if a isolated scheme is required. For T-boxes and junction boxes, the manufacturers instructions must be followed.
Endress+Hauser
75
Full isolation
Full isolation is the scheme described in IEC 61158-2, and is the favoured method in Britain and the USA. In this case, the cable shield ground is fully isolated from the device grounds. The shield is grounded at the power supply or safety barrier only. The disadvantage of this method is that the bus signal is not optimally protected from high frequency interference. Just how much this disturbs communication, depends upon the length of the bus, its topology and the sources of interference. As pointed out at the start of this chapter, if the bus runs in grounded metal conduits, as e.g. in American installations, then this scheme may work quite well.
Fig. 6-2: Full isolation with optional grounding of devices: 1 Power supply/segment coupler, 2 T-Box or junction box, 3 Bus terminator, 4 Grounding point for bus cable shield, 5 Optional grounding of devices, e.g. by neutral star bonding or conduit
Fig. 6-3: Full isolation with optional potential equalisation of devices: 1 Power supply/segment coupler, 2 T-Box or junction box, 3 Bus terminator 4 Grounding point for bus cable shield, 5 Local device grounds, 6 Optional potential equalisation line
76
Endress+Hauser
Multiple grounding
Multiple grounding provides enhanced protection against electromagnetic interference in noisy environments. It is the favoured method in Germany. All devices and cable shields are grounded locally. Each local ground is connected to a thick potential equalisation line, which itself is grounded in a safe area. According to IEC 79-13, Paragraph 12.2.2.3, this method can be used provided that the installation is effected and maintained in such a manner that there is a high level of assurance that potential equalisation exists between each end of the circuit. Under these circumstances it fulfils intrinsic safety requirements.
Fig. 6-4: Multible grounding with neutral star earth bonding: 1 Power supply/segment coupler, 2 T-Box or junction box, 3 Bus terminator, 4 Potential equalisation through star bonding
Fig. 6-5: Multible grounding with potential equalisation line: 1 Power supply/segment coupler, 2 T-Box or junction box, 3 Bus terminator, 4 Local ground, 5 Potential equalisation line
Endress+Hauser
77
Capacitive isolation
In the case of capacitive grounding, the shield is connected to the grounding system (here shown as potential equalisation line) via a capacitor at all points except the power supply or safety barrier, which is grounded in the normal way. Small capacitors (e.g. 1 nF, 1500 V, dielectric strength, ceramic) are used and the total capacitance connected to the shielding may not exceed 10 nF. The capacitors are normally built into the T-box and junction box connectors, and offered as such by the component manufacturers. This method is not permitted in Ex applications.
Fig. 6-6: Capacitive grounding in a safe area: 1 Power supply/segment coupler, 2 T-Box or junction box with capacitive shield grounding, 3 Bus terminator with capacitive shield grounding, 4 Local grounds, 5 Potential equalisation line (optional)
If the bus runs into a hazardous area the T-boxes and junction boxes must be wired in the normal way and the power supply or barrier grounded via a capacitor.
Fig. 6-7: Capacitive grounding in a explosion hazardous area: 1 Power supply/segment coupler with capacitive shield grounding, 2 T-Box or junction box, 3 Bus terminator, 4 Local grounds, 5 Potential equalisation line (optional)
78
Endress+Hauser
6.3
Termination
The start and end of every PROFIBUS PA segment must be fitted with a bus terminator. For nonhazardous areas, some T-boxes have an integrated terminating element that can be switched in when required. If this is not the case, a separate terminator must be used. The segment coupler at the beginning of the segment has a built in terminator. The terminator in the T-box at the end of the segment must be switched in, or a separate terminator must be used. T-boxes with switchable terminators may not be used in explosion hazardous areas. The terminator requires the corresponding FISCO approval and is a separate unit. For a segment with a tree architecture, the bus ends at the device that is the furthest from the segment coupler. For a junction box, the termination can be made at the box, provided that none of the connected spurs exceeds 30 m in length. If the bus is extended by the use of a repeater, then the extension must also be terminated at both ends. The beginning and end of the PROFIBUS DP segment must also be terminated, see Chapter 3. The terminating resistors are already built into most of the connectors on the market and must only be switched in.
6.4
Overvoltage protection
Depending upon the application, the PROFIBUS PA segment can also be protected against overvoltages. An overvoltage protector is installed immediately after the segment coupler. An overvoltage protector is installed immediately before every device (between the device and the T-box). In the case of hazardous applications, each overvoltage protector must have the corresponding approval. The manufacturer's instructions are to be observed when installing. The overvoltage protectors HAW 560, HAW 560Z, HAW 562, HAW 562Z, HAW 569 and HAW 569Z are available from Endress+Hauser.
Segment coupler
Field device
Overvoltage protection
Fig. 6-8: PROFIBUS PA overvoltage protection system
Endress+Hauser
79
6.5
Installation of the devices
PROFIBUS devices must be installed in accordance with their operating manuals. Table 6-1 lists all manuals available at the time of writing. Current manuals can be downloaded from the companys Internet site: www.endress.com. It should be noted that for some devices, a separate manual is available covering PROFIBUS installation. All Endress+Hauser devices have integrated polarity protection and can be commissioned independent of the actual polarity. If a device without polarity protection is incorrectly wired, then it will not be recognised by the PLC or operating program. Such an incorrect connection, however, has no damaging effect on the device or the segment.
Note! All Endress+Hauser devices designed for use in explosion hazardous areas conform to the FISCO model /Ex ia. In the case of four wire devices, the supply connection compartments are designed with type of protection Ex d and/or Ex e. This usually precludes the use of the standard M12 connector. In addition to the general installation guidelines, any special guidelines for installation in explosion-hazardous areas as well as the guidelines in Chapter 5-1 regarding the interconnection of devices in explosion hazardous areas must be observed. . Device
Cerabar M Cerabar S Deltabar S Deltapilot S
Operating manuals
Device type
ID Code
Operating instructions BA222P/00/en BA168P/00/en BA167P/00/en BA164P/00/en
PMC41, PMC45, PMP41, PMP45, PMP46, PMP48 PMC631, PMC731, PMP635, PMP731 PMD230, FMD230, PMD235, FMD630, FMD633 DB50, DB50A, DB50, DB50S, DB51, DB51A, DB52, DB52A, DB53, DB53A, FEB24, FEB24P FXA164 FMP40 FDL60, FDL6,1 FEL67, FTL670 LF, pH, Tu, O2, Cl FMR130, FMR131, FMR230V, FMR231E, FMR230, FMR231, FMR240, FMR530, FMR531, FMR532, FMR533, FMR130, FMR131, FMR230V, FMR231E, FMR230, FMR231, FMR24,0 FMR530, FMR531, FMR532, FMR533, FEC14 pH Value: CPM152 LF inductive: CLM152 LF conductive: CPM152
151C 1501 1504 1503
PROFIBUS I/O-Box Levelflex M Liquiphant M Liquisys M
1514 152D 152B 1515 1516 1517 1518 1519 150A
--BA243F/00/en BA141F/00/en BA209C/00/en
Micropilot II
BA176F/00/en, BA202F/00/en BA225F/00/en, BA226F/00/en BA261F/00/en BA143C/07/en BA168C/07/en BA144C/07/en
Micropilot M
1522
Multicap Mycom II
153A 1508 1509 150B 1513 1535 1537 1539 150C 150D 1505 1505
Mycom S
LF conductive: CLM153 LF inductive: CPM153 pH Value: CPM153 LF: CLM431 pH Value: CPM431 33W, 33P, 33H 35W, 35P, 35H
BA234C/07/en, BA298C/07/en
Mypro
BA198C/07/en
Promag 33 Promag 35
80
Endress+Hauser
Device
Device type
ID Code
Operating instructions BA055D/06/en BA053D/06/en BA033D/06/en BA072D/06/en BA063D/06/en BA085D/06/en BA094D/06/en BA037D/06/en BA074D/06/en BA076D/06/en BA238F/00/en BA166F/00/en
Promag 50 Promag 53 Promass 63 Promass 80 Promass 83 Prowirl 72 Prowirl 73 Prowirl 77 Prosonic Flow 90 Prosonic Flow 93 Prosonic M Prosonic T
50W, 50P, 50H 53W, 53P, 53H 63A, 63E, 63F, 63H, 63I, 63M 80A, 80E, 80F, 80H, 80I, 80M 83A, 83E, 83F, 83H, 83I, 83M 72F, 72W 73F, 73W 77 90W, 90U, 90C DDU10, DDU15, DDU18, DDU19 FMU40, FMU41, FMU43 FMU130, FMU131, FMU230, FMU231, FMU232, FTU230, FTU231 RID261 CLD132 TMD834 TMT184
1525 1527 1506 1528 152A 153B 153C 1510 152F 1530 152C 1502
Display Smartec S TMD834 iTemp PA
BA098R/09/a3 153E 1507 1523 BA213C/07/en BA090R/09/en BA115R/09/en
Table 6-1: Endress+Hauser operating manuals for installation of the PROFIBUS PA devices
Endress+Hauser
81
6.6
Setting addresses
The device address can be set either locally via switch (e.g. DIP, DIL, ...), via local operating elements or by the appropriate software (e.g. FieldCare or Commuwin II). All PROFIBUS devices must have a unique address. Valid addresses lie within the range 0125. For the rules and examples of address assignment, see Section 5.7. If an address is not configured correctly, the device will not be recognised by the master. The address 126 is used for initial commissioning and for service purposes. This is normally the default address of Endress+Hasuer PROFIBUS PA set at the factory.
6.6.1
Eight-gang DIP switch
Using DIP switches
All Endress+Hauser devices except the analysis device Mypro or TMT 834 are fitted with an DIP switch for setting the device address. Fig. 6-9 shows a typical example: A = DIP switches 1 - 7: defining the device address B = DIP switch 8: address mode (type of addressing) (ON = software addressing / OFF = hardware addressing)
Fig. 6-9: Example 1: DIP switches for setting the device address
Ten-gang DIP switch
The flowmeter Prowirl 72/73 has a ten-gang switch, see Fig. 6-10: A = DIP switches 1 - 7 = defining the device address B = DIP switches 8 - 9 = not defined C = DIP switch 10 = address mode (type of addressing) (ON = hardware addressing / OFF = software addressing)
Fig. 6-10: Example 2: DIP switches for setting the device address at Prowirl 72/73
Hardware addressing
1. Set switch 8 to OFF. (For Prowirl 72/73 set switch 10 to ON) 2. Set an address with DIP switches 1 - 7: the associated values are shown in the table below.
Switch No. Value in position "off" Value in position "on"
1 0 1
2 0 2
3 0 4
4 0 8
5 0 16
6 0 32
7 0 64
Table 6-2: Setting the device address
Software addressing
1. Set switch 8 to ON. (For Prowirl 72/73 set switch 10 to OFF)
82
Endress+Hauser
6.6.2
Software addressing with FieldCare
If software addressing is used, the devices must be switched on one-by-one or connected point-topoint to the workstation. 1. Where appropriate, check that software addressing has been enabled at the DIP-switch. 2. In the Network View click on the PROFIdtm and open the Set Device Station Address dialog Menu Device Operation Device Functions Additional Functions Set Device Station Address 3. In the dialog, enter the following Old Address: Enter the current device address. NewAddress: Enter the new device address. Click on Set.
4. If changing address was successful, click on Close.
Endress+Hauser
83
6.6.3
Software addressing with Commuwin II
If software addressing is used, the devices must be switched on one-by-one or connected point-topoint to the workstation.To set an address with Commuwin II proceed as follows: 1. Where appropriate, check that software addressing has been enabled at the DIP-switch. 2. Start the DVP1 server with a double click on the DPV1 icon in the Commuwin II program group. 3. Select the item Set Address in the menu Configure. 4. If a type IM 157 Siemens DP/PA link is being used, enter its DP-address under PA Link Addr. 5. Enter the current address under Old Addr. (= 126 when commissioning).Check the address entered by clicking on Check Old Address. If a device with the entered address is found, a message to this effect appears under Device ID. Otherwise the error message "unknown" appears.
6. Enter the new address in New Addr. Check that there is no address conflict by clicking on Check New Address. When the button Set Address becomes active, click on it to assign the new address to the device.
7. When the procedure is completed correctly, the following message appears: "Address successfully changed!"
84
Endress+Hauser
7 System Integration
System Integration
This chapter is concerned with system integration and is structured as follows: Network configuration Device database files Cyclic data exchange Bus parameters
7.1
Network configuration
In general, the a PROFIBUS network configuration proceeds as follows: 1. The network participants are stipulated in the configuration program (see Table 7-1). The GSD files are then loaded into the specified directory of the program and the network is configured off-line with the planning software. 2. The PLC application program is now written. This is done using the manufacturer's system programming software. The application program controls the input and output of data and determines where the data are to be stored. If necessary, an additional conversion module must be used for PLCs that do not support the IEEE 754 floating point format. Depending upon the way the data is stored in the PLC (LSB or MSB), a byte swapping module may be required. 3. After the network has been designed and configured, the result is loaded into the PLC as a binary file. 4. When the PLC configuration is complete, the system can be started up. The master opens a connection to each individual device. Now by using a Class 2 master, e.g. FieldCare, the individual devices can be parametrized from a central workstation.
System
Master
PROFIBUS configuration software COM PROFIBUS HW Config HW Config SST PROFIBUS Configuration Tool
System programming software Step 5 Step 7 PCS 7 RS Logix-5 RS Logix-5000 RS Logix-500
IEEE conv.block FB 201 ___ ___ ___
bytes swap
Siemens
S5 series S7 series
no
Allen Bradley
PLC-5 ControlLogix SLC-500 ProcessLogix TSX Premium Modicon Quantum
yes ___
Schneider Schneider Quantum Klckner-Moller ABB Freelance Bosch Emerson
Sycon Hilscher Sycon
PL7 Pro Concept
___ ___
yes yes
PS 416 AC 800 F ZS 401 Delta V
CFG-DP Control Builder F Win DP Delta V Explorer
S 40 Control Builder F Win SPS Delta V Explorer
___ ___ ___ -----
yes no yes no
not necessary, since integrated in software Table 7-1: Examples of network design software
Endress+Hauser
85
7.1.1
Tested systems
Table 7-2 lists PROFIBUS DP systems that have been successfully tested by Endress+Hauser. New systems are tested as they come on the market. For the systems listed coupling documentation is available on request for customers wishing to integrate Endress+Hauser devices into their systems. Information on systems not in the list *is available on request.
PLC/PCS ABB Freelance 2000 Allen-Bradley PLC-5 Allen-Bradley PLC-5 Allen-Bradley SLC-500 Allen-Bradley ControlLogix Bosch CL400 Emerson DeltaV HIMA H41 (Modbus) Mitsubishi Melsec AnS Moeller PS416 Omron CS-1 Schneider TSX Premium Quantum S7-300 DP interface FieldController SST-PFB-PLC SST-PFB-PLC + ZA375 Slave SST-PFB-SLC SST-PFB-CLX BM-DP12 VE4014 PKV20-DPM (Hilscher) A1S-J71PB92D PS416-NET-440 C200HW-PRM21 TSXPBY100 140 CRP 81100 315-2 DP Segment coupler Pepperl+Fuchs Pepperl+Fuchs, Siemens link Pepperl+Fuchs Pepperl+Fuchs, Siemens link Pepperl+Fuchs, Siemens link Pepperl+Fuchs, Siemens link Pepperl+Fuchs Pepperl+Fuchs Pepperl+Fuchs Pepperl+Fuchs Pepperl+Fuchs Pepperl+Fuchs Pepperl+Fuchs, Siemens link Pepperl+Fuchs, Siemens coupler, Siemens link Siemens link Siemens link Pepperl+Fuchs Pepperl+Fuchs, Siemens coupler, Siemens link Pepperl+Fuchs, Siemens coupler, Pepperl+Fuchs, Siemens coupler, Pepperl+Fuchs, Siemens coupler, Siemens link Pepperl+Fuchs
Siemens S7-300 Siemens S7-300 Siemens S7-300 Siemens S7-400
315-2 DP + ZA375 Slave 315-2 DP + AS-I Link CP342-5 414-2 DP
Siemens S5-115U Siemens S5-135U Siemens S5-155U
IM308C IM308C IM308C
Softing OPC Server
Profiboard / Proficard
Table 7-2: Summary of tested PROFIBUS DP-systems
86
Endress+Hauser
7.2
Device database files (GSDs)
The PROFIBUS system requires a description of the device parameters, e.g. output data, input data, data format and supported transmission rate, so that it can integrate the field devices into the bus system. This data is contained in a PROFIBUS device description file (GSD file) which is placed at the disposal of the PROFIBUS-DP master when the communication system is being commissioned. Device bitmaps, which appear as symbols in the network tree, can also be integrated. If devices are used that support the "PA devices" profile, there are three different versions of the GSD file: Manufacturer-specific GSD): This guarantees the maximum functionality of the field device. Device-specific process parameters and functions are available. Two versions of the manufacturer-specific GSD are available, standard and extended. Use the version supported by you control system. Profile GSD: This contains a fixed number of Analog Input blocks (AI) dependent upon the profile of the measuring principle. If a system is configured with profile GSDs, it will be possible to exchange a device supplied by one manuafacturer for one produced by another manufacturer. Profile GSD (multi-variable) with the ID number 9760Hex: This GSD contains all possible function blocks specified in the device profile such as AI, DO, DI, etc.. It is not supported by Endress+Hauser devices. A decision on which type of GSD is to be used must be made during the planning of the network. The configuration can be changed during operation (using a Class 2 master, or sometimes the local display), but it should be remembered, that if the segment is running at or near maximum capacity, this could lead to a breakdown in communication because the telegram length exceeds 244 bytes. Obtaining GSD files The GSD files for all Endress+Hauser devices can be acquired in the following manner: Internet (Endress+Hauser) http://www.endress.com (Download Area) Internet (PNO) http://www.profibus.com (Products - Product Guide) On CD-ROM from Endress+Hauser: Order-Code-No. 56003894 Contents of the download file from the internet and the CD-ROM: All Endress+Hauser GSD files Endress+Hauser bitmap files Useful information relating to the devices All the files which are needed for configuration are contained in one zipped file. During unpacking, the following structure will be created: Version #xx stands for the corresponding device version. Device-specific bitmaps can be found in the directories BMP and DIB. The utilisation of these will depend on the configuration software that is being used. The GSD files are saved in the subdirectories Extended and Standard which can be found in the GSD folder. Information relating to the implementation of the field transmitter and any dependencies in the device software can be found in the Info folder. Please read this carefully before configuration takes place.
Endress+Hauser
87
Standard and extended formats
Some systems require that the modules of the GSD files are transmitted with an extended identification (e.g. 0x42, 0x84, 0x08, 0x05). The associated GSD files can be found in the Extended folder. All GSD files that have a standard identification (e.g. 0x94) can be found in the Standard folder. When integrating field transmitters, the GSD files with the extended identification should be used first. If, however, the integration is not successful, the standard GSD should be used. This differentiation is the result of a specific implementation in the master systems.
Identification
The GSD designations are derived from the PNO device ID or Profile ID numbers as follows: Standard GSD: EH3_15xx EH = Endress+Hauser 3 = Profile 3.0, _= standard identification 15xx = Device ID-No. EH = Endress+Hauser 3 = Profile 3.0, x= extended identification 15xx = Device ID-No. PA = PROFIBUS PA (DP) 03 = Profile 3.0, PA; 13 = Profile 3.0, DP 9741 = Profile ID number
Extended GSD:
EH3x15xx
Profile GSD
PA039741
DP files are required for PROFIBUS DP devices and for PROFIBUS PA devices that are operating with a Pepperl+Fuchs SK2 coupler, see Section 7.4.1. Working with GSD files The GSD files must be integrated into the automation control system. Depending on the software that is being used, the GSD files can be copied to the program-specific directory or can be read into the database using the import function within the configuration software, see operating manuals of your system. Example: In the case of the configuration software Siemens STEP 7 (Siemens PLC S7-300 / 400) The GSD files are copied to the subdirectory ...\ siemens \ step7 \ s7data \ gsd. The bitmap files are used to display the measuring points in image form. The bitmap files are saved to the directory ...\ siemens \ step7 \ s7data \ nsbmp. Taking the example of the Promag 53, the following sections show how the GSD files are integrated and used
88
Endress+Hauser
7.2.1
Example Promag 53
GSD file example
Fig. 7-1 shows the block structure of the Promag 53 flowmeter. It can be seen that the device supports both a manufacturer specific and a Profile 3.0 configuration. The parameters required for this are carried by the associated GSD files
Local Operation Transducer Block AI1: Volume flow PROFILE Parameters AI2: Mass flow Totalizer 1 Totalizer 2 Physical Block Manufacturer specific parameters Totalizer 3
OUT VALUE Value/Status OUT VALUE Value/Status TOT1 OUT VALUE Value/Status TOT2 OUT VALUE Value/Status TOT3 OUT VALUE Value/Status DISPLAY VALUE Value/Status
CONTROL
Fig. 7-1: Block structure of Promag 53
For the Promag 53, which depending upon type supports PROFIBUS PA or PROFIBUS DP, the following GSD files and bit maps are available:
Device type Promag 53 PA PROFIBUS PA (IEC 61158-2 (MBP)) File type Manufacture specific GSD ID-No. 1527 (Hex) File name EH3_1527.gsd EH3x1527.gsd PA139741.gsd EH_1527_d.bmp/.dib EH_1527_n.bmp/.dib EH_1527_s.bmp/.dib EH3_1526.gsd EH3x1526.gsd PA039741.gsd EH_1526_d.bmp/.dib EH_1526_n.bmp/.dib EH_1526_s.bmp/.dib
Profile 3.0 GSD Bitmaps
9741 (Hex) N/A
Promag 53 DP PROFIBUS DP (RS 485)
Manufacture specific GSD
1526 (Hex)
Profile 3.0 GSD Bitmaps
9741 (Hex) N/A
Table 7-3: Promag 63 GSD files
Endress+Hauser
PROFIBUS DP/PA
Sensor
Signal Processing
89
7.2.2
Example Promag 53
Full configuration with manufacturer-specific GSDs
After the device has been connected, a double click on the device node configures the communication telegram.
Fig. 7-2: Full configuration in Siemens PDM
Note! For level and pressure devices, the telegram frame is empty and the content must be selected from the blocks offered in the device tree This form of configuration activates all blocks supported by the device. The parameters SET_TOT and MODE_TOT must be now configured.
Iput Byte 04 Output Byte Data blocks Status Access type read Block Designation AI Extended block ID 0x42, 0x84, 0x08, 0x05 0xC1, 0x81, 0x84, ox85 Standard block ID 0x94
Volume flow + status Totalizer 1 + status + control value Totalizer 1 + status + control value Totalizer 2 + status + control value Mass flow + status
active
59
0+1
active
read + write read + write read + write read + write write
SET_TOT_ MODE_TOT_ TOTAL SET_TOT_ MODE_TOT_ TOTAL SET_TOT_ MODE_TOT_ TOTAL AI
0xC1, 0x81, 0x84, ox85
10 14
2+3
active
0xC1, 0x81, 0x84, ox85
0xC1, 0x81, 0x84, ox85
15 19
4+5
active
0xC1, 0x81, 0x84, ox85
0xC1, 0x81, 0x84, ox85
20 24
active
0x42, 0x84, 0x08, 0x05
0x94
6 10
Display value + status Control variable3
active
DISPLAY_ VALUE CONTROL_ BLOCK
0x82, 0x84, 0x08, 0x05 0x20
0xA4
11
active
write
0x20
Table 7-4: Full configuration of Promag 53 telegram
90
Endress+Hauser
VALUE and STATUS
The values and status are transmitted in the following formats: Volume flow: Totalizer 1...3: Mass flow: Display value: Status: Control value: 32-bit floating point number (IEEE-754) 32-bit floating point number (IEEE-754) 32-bit floating point number (IEEE-754) 32-bit floating point number (IEEE-754) 1 byte bit code 1 byte bit code m3/h m3 or kg kg/h
Totalizers 1-3 can be configured individually. The following settings are possible (factory setting: volume flow in m3): Off, Mass flow, Volume flow Output data The display value allows the transfer of a measured value that has been calculated in the controller to the Promag display. This value can be assigned to the main line, the secondary line and the info line of the display. The display value comprises 4 bytes measured value and 1 byte status. The status is displayed as being OK, UNCERTAIN or BAD. The control variables SET_TOT_n and MODE_TOT_n for totalizers 1-3 allow them to be controlled from the automation control system. The following control variables are possible: SET_TOT 0= 1= 2= Totalize Reset Activate predefined value Balancing positive flow detection negative flow detection Stop totalizing.
Control variables
MODE_TOT 0= 1= 2= 3=
The control variable is executed through the cyclic data exchange each time the output byte changes. It is not necessary to reset to 0 to execute a control variable. The predefined totalizer value is set via the local display or the Class 2 master! Example of SET_TOT and MODE_TOT: If the control variable SET_TOT is set to 1 (1 = Reset the totalizer), the value of the totalizer will be set to 0. The value of the totalizer will now be added up starting from 0. If the totalizer is to retain the value 0, it will be necessary to set the control variable MODE_TOT to 3 (3 = STOP totalizing). The totalizer will now stop adding up. The control variable SET_TOT can be set to 1 at a later point in time (1 = Reset the totalizer).
Endress+Hauser
91
7.2.3
Example Promag 53
Partial configuration with manufacturer-specific GSDs
If not all measured variables are not required, the placeholder EMPTY_MODULE (0x00) is used to to deactivate individual measured variables:
Fig. 7-3: Using place holders in Siemens PDM
Note! The placeholder is sometimes called "FREE_SPACE" The result is that selected blocks are deactivated and the telegram length is reduced. The totaliser has been configured "without control variable" in this example, so that it acts as an additional measured value without control. There is no possiblity to stop or reset it.
Iput Byte 04 Output Byte Data blocks Status Access type read Block Designation AI Extended block ID 0x42, 0x84, 0x08, 0x05 0x81, 0x84, ox85 0xC1, 0x81, 0x84, ox85 0xC1, 0x81, 0x84, ox85 0x42, 0x84, 0x08, 0x05 0x82, 0x84, 0x08, 0x05 0x20 Standard block ID 0x94
Volume flow + status Totalizer 1 + status
active
59
active
read
TOTAL
0x81, 0x84, ox85 0xC1, 0x81, 0x84, ox85 0xC1, 0x81, 0x84, ox85 0x94
Placeholder
disabled
EMPTY_ MODULE EMPTY_ MODULE EMPTY_ MODULE write DISPLAY_ VALUE CONTROL_ BLOCK
Placeholder
disabled
Placeholder
disabled
0 46
Display value + status Control variable3
active
0xA4
active
write
0x20
Fig. 7-4: Example for parrtial configuration of the Promag 53
92
Endress+Hauser
7.2.4
Example Promag 53
Profile GSD
After the device has been connected, a double click on the device node configures the communication telegram.
Fig. 7-5: Configuration using Profile GSD
Note! For level and pressure devices, the telegram frame is empty and the content must be selected from the blocks offered in the device tree This form of configuration activates all blocks supported by device profile. The GSD file contains two AI blocks and a Totalizer block. The first AI block is always assigned to the volume flow. This guarantees that the first measured variable agrees with the field equipment of other manufacturers. The second AI block can be freely selected as Promag 53 is capable of producing a calculated mass flow. There is no difference between the PROFIBUS DP and PROFIBUS PA Profile GDSs except regarding the transmission rates supported.
Iput Byte 04 Output Byte Data blocks Status Access type read Block Designation AI Extended block ID 0x42, 0x84, 0x08, 0x05 0xC1, 0x81, 0x84, ox85 Standard block ID 0x94
Volume flow + status Totalizer 1 + status + control value Mass flow + status
active
59
0+1
active
read + write read + write
SET_TOT_ MODE_TOT_ TOTAL AI
0xC1, 0x81, 0x84, ox85
20 24
active
0x42, 0x84, 0x08, 0x05
0x94
Table 7-5: Example for profile configuration with Promag 53
Endress+Hauser
93
7.3
Transfer of analogue values
Cyclic data exchange
As mentioned previously, analog process values are transmitted to the PLC cyclically in 5 byte blocks. The measured value is a four byte floating point number to IEEE 754, see Table 7-6. The fifth byte contains the associated status information.
Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Status
Measured value as IEEE 754 floating point number Table 7-6: Structure of cyclic analog value
If a device delivers more than one measured value (e.g. Promag), the measured value telegram is increased accordingly, see Chapter 7.3. The number of measured values that a device transmits is set while the system planning. Table 5-15 in Chapter 5.6 as well as the device operating manuals summarise the measured values that can be transmitted by Endress+Hauser devices. IEEE 754 floating point number The measured value is transmitted as a IEEE 754 floating point number, whereby Measured value = (1)Sign x 2(E 127) x (1 + F)
D15 Sign D14 D13 D12 D11 D10 D9 D8 D7 D6 D5 D4 D3 D2 D1 D0
Exponent (E) 27 26 25 24 23 22 21 20
Fraction (F) 2-1 2-2 2-3 2-4 2-5 2-6 2-7
Fraction (F) 2-8 2-9 2-10 2-11 2-12 2-13 2-14 2-15 2-16 2-17 2-18 2-19 2-20 2-21 2-22 2-23
Table 7-7: IEEE 754 floating point number
Example
40 F0 00 00 hex = 0100 0000 1111 0000 0000 0000 0000 0000 binary Value = (1)0 * 2(129-127) * (1 + 2-1 + 2-2 + 2-3) = 1 x 22 x (1 + 0.5 + 0.25 + 0.125) = 1 x 4 x 1.875 = 7.5
Not all PLCs support the IEEE 754 format. For this reason a conversion module must often be used or written. Transfer of discrete values If the field device outputs a level limit signal, e.g. Liquiphant M, the information is transmitted in two bytes as follows. An exact description of the transmission format is to be found in the operating instructions.
Byte 1 Digital value (USGN8) Byte 2 Status
Table 7-8: Structure of digital cyclic value
Status code
The status code correspond to the PROFIBUS profiles 3.0 PROFIBUS PA profile for Process Control Devices - General Requirements V 3.0, and are listed in the following sections
94
Endress+Hauser
7.3.1
Status codes: Device status BAD

Significance = Non-specific Device status BAD Limits OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT
Status code 0x00 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1A 0x1B 0x1C 0x1D 0x1E 0x1F
= Configuartion error
BAD
= Function block not available
BAD
= Device failure
BAD
= Sensor failure
BAD
= No communication (last usable value)
BAD
= No communication (no usable value)
BAD
= Out of order
BAD
Table 7-9: Status code - device status: BAD
Endress+Hauser
95
7.3.2
Status codes: Device status UNCERTAIN

Significance = Non-specific (Simulation) Device status UNCERTAIN Limits OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT
Status Code 0x40 0x41 0x42 0x43 0x44 0x45 0x46 0x47 0x48 0x49 0x4A 0x4B 0x4C 0x4D 0x4E 0x4F 0x50 0x51 0x52 0x53 0x54 0x55 0x56 0x57 0x58 0x59 0x5A 0x5B 0x5C 0x5D 0x5E 0x5F 0x60 0x61 0x62 0x63 0x64 0x65 0x66 0x67
= Last usable value
UNCERTAIN
= Substitute set
UNCERTAIN
= Initial value (values which are not saved after the device or parameters have been reset)
UNCERTAIN
= Sensor conversion not accurate (measured value of sensor not accurate)
UNCERTAIN
= Engineering unit rage violation
UNCERTAIN
= Subnormal
UNCERTAIN
= Configuration error
UNCERTAIN
= Simulated value
UNCERTAIN
= Sensor calibration not accurate
UNCERTAIN
Table 7-10: Status code - device status: UNCERTAIN
96
Endress+Hauser
7.3.3
Status codes: Device status GOOD

Significance = Measuring value OK Device status GOOD Limits OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT
Status code 0x80 0x81 0x82 0x83 0x84 0x85 0x86 0x87 0x88 0x89 0x8A 0x8B 0x8C 0x8D 0x8E 0x8F 0x90 0x91 0x92 0x93 0x94 0x95 0x96 0x97 0x98 0x99 0x9A 0x9B 0xA0 0xA1 0xA2 0xA3 0xA4 0xA5 0xA6 0xA7 0xC0 0xC1 0xC2 0xC3 0xC4 0xC5 0xC6 0xC7 0xC8 0xC9 0xCA 0xCB 0xCC 0xCD 0xCE 0xCF
= Update event (change of parameters)
GOOD
= Active advisory alarm (warning: advance warning limit exceeded) (priority < 8) = Active critical alarm (critical alarm: alarm limit exeeded) (priority >8)
GOOD
GOOD
= Update event (unconfirmed change of parameters)
GOOD
= Unacknowledged advisory alarm
GOOD
= Unacknowledged critical alarm
GOOD
= Initiate fail-safe status
GOOD
= Wartung erforderlich
GOOD
= Measured value OK
GOOD
= Initialisierung besttigt
GOOD
= Initialisierung angefordert
GOOD
= not invited
GOOD
Endress+Hauser
97
Status code 0xD0 0xD1 0xD2 0xD3 0xD4 0xD5 0xD6 0xD7 0xD8 0xD9 0xDA 0xDB 0xDC 0xDD 0xDE 0xDF 0xE0 0xE1 0xE2 0xE3 = reserved
Significance
Device status GOOD
Limits OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT OK LO_LIM HI_LIM CONSTANT
= do not select
GOOD
= local override
GOOD
= reserved
GOOD
= Initiate fail-safe status
GOOD
Table 7-11: Status code - device status: GOOD
98
Endress+Hauser
7.4
Transmission rates
Bus parameters
Endress+Hauser's PROFIBUS DP devices support baudrates up to 12 Mbit/s (depends on version). The baudrate is automatically adjusted to that used by the master and must not be set at the device. Similarly, PROFIBUS PA devices do not have to be adjusted, since the transmission rate is fixed. On the other hand, if FieldCare or Commuwin II is used as a Class 2 master, both the transmssion rate and other bus parameters must be aligned with those of the segment coupler. The same PROFIBUS DP baudrate must be also be set in the network configuration software: Pepperl+Fuchs segment coupler SK1: 93.75 kBit/s Pepperl+Fuchs segment coupler SK2: 45.45 kBit/s - 12 MBit/s Siemens DP/PA coupler: 45.45 kBit/s Siemens DP/PA link: 9.6 kBit/s - 12 MBit/s
The typical values for the other bus parameters are listed in Table 7-12. Please note that for the Pepperl+Fuchs SK2 coupler, additional parameters must be set, as described later in theis chapter.
Segment coupler Slot time Max. station delay time Min. station delay time Setup time GAP update factor Max. retry limit Target rotation time2) (TTR) Siemens 640 400 11 95 1 3 P+F "old" 10000 1000 255 255 1 3 P+F "new"1) 4095 1000 22 150 1 3
TTR calculated by master + 20 000 bit times
1) Segment coupler has the label with 12-3-98 or newer 2) Value must be set in all masters. Table 7-12: Bus parameters for FieldCare and Commuwin II
Endress+Hauser
99
7.4.1
Aligning FieldCare
The FieldCare transmission rate is set in the PROFIBUS CommDTM: 1. Add the CommDTM for PROFIBUS to the network. 2. Right click on the CommDTM to opens the context menu. Select Configuration.
3. After changing the baudtrate, update the bus parameters and click on Defaults. 4. If necessary optimise the parameters as the manufacturer's specifications.
7.4.2
Aligning Commuwin II
The Commuwin II transmission rate is set in the DPV1 DDE server. 1. Start the server DPV1 from the File Manager or Explorer by a double click on the DPV1 icon in the Commuwin II program group. 2. Open the item Parameter Settings in the Configure menu. The baudrate can now be adjusted.
3. After the baudrate has been entered, update the bus parameters by clicking on Default. 4. If necessary optimise the parameters as the manufacturer's specifications.
100
Endress+Hauser
7.4.3
PROFIBUS PA-slaves
Commissioning the Pepperl+Fuchs SK2
Since the SK2 segment coupler works transparently, PROFIBUS PA stations are treated by the PROFIBUS DP master as if they were PROFIBUS DP slaves. This also applies to commissioning and configuration. In order that a PROFIBUS PA slave be placed in operation and be configured by a configuration tool, the GSD file of the slave must be integrated into the configuration tool. In view of the fact that the SK2 coupler supports several transmission rates on the PROFIBUS DP side, the normal PROFIBUS PA GSD file cannot be used. Instead, the PROFIBUS DP GSD file is required. If the device does not support PROFIBUS DP, the PROFIBUS PA GSD file must be converted with the conversion program supplied by Pepperl+Fuchs with the SK2. This applies both to the manufacturer-specific and profile GSDs.
Note! The naming conventions for GSD files are described in Chapter 3.4.1. If you uncertain what GSD you have, integrate it into your configuration tool and check the transmission rates supported: If the transmission rate 31.25 kBd is supported, it is a PA GSD. If the transmission rates of 9.6 kBd to 1.5 MBd or 12 MBd are supported, it is a DP GSD.
GSD Converter
If no PROFIBUS DP GSD exists, the PA GSD must be converted. The software can be downloaded free-of-charge from www.pepperl-fuchs.com. The task of this conversion software is exclusively to enter the missing transfer rate and set specific bus parameters to values that allow for problemfree operation of the PROFIBUS DP.
Note! The PROFIBUS user organization has agreed that certified GSD files that have been modified by the Pepperl+Fuchs GSD converter software do not lose their certificate. The conversion of the GSD file imposes the following restrictions if the function was previously supported by the original GSD file: FREEZE and SYNC functionality is deactivated. These functions are used in PROFIBUS DP for synchronizing sensors/actuators. Since the system is working with transfer rates of up to 12 MBd on the PROFIBUS DP side (host side) and with a transfer rate of 31.25 kBd on the PROFIBUS PA side (field side) it is not possibleto ensure that this synchronization will work with no problems. A maximum of 4 master Class 2 connections (C2 connections) are supported for each slave. Some PROFIBUS functions are currently not supported. If the field device is supposed to support one or more of the following functions, a warning will inform the user that this is no longer the case after the conversion. This affects the following functions: Alarms based on PROFIBUS DP V1 The following functions of the PROFIBUS DP V2 - Data Exchange Broadcast (Publisher/Subscriber) - Time synchronization - Isochronous mode, i. e. cycle-synchronous transfer
Endress+Hauser
101
Using GSD Converter
After the program is started (pfgsdcv.exe) the following dialogue appears:
Fig. 7-6: Dialogue box: Pepperl+Fuchs GSD Converter
To convert a GSD file, proceed as follows: 1. Switch to the directory in which the GSD files to be converted are located. 2. Select the GSD files to be converted: You can select one or more files (using Ctrl or Shift) for conversion. Files with + before the file name are the result of a former conversion and generate an error message if you attempt to convert them again. Files with a - are not the result ofa conversion and can be converted. You can open a file to view it and edit it by double clicking on it. 3. Determine the version number of the GSD file to be converted: the name of a PROFIBUS GSD file always consists of three parts: The manufacturer-specific part (1- 4 characters) The device ID number (4 characters) The file extension For converted PROFIBUS PA GSD files, the Profibus User Organization (PNO) has specified that the charaters "YP0" and a version number as the the manufacturer-specific part of the name. You can select the version number using a drop-down box (revision) and thus generate different versions of GSD files for a field device (with the same ID number). 4. Switch to the directory in which the converted GSD files will be stored. 5. Convert the GSD files by clicking on the Process GSD --> button. You can start the conversion process with this button. Another window appears in which you are informed of the results of the conversion process.
102
Endress+Hauser
7.4.4
Watch Dog Time TWD
PROFIBUS devices can activate a watchdog mechanism that checks whether the PROFIBUS master is still actives every data exchange cycle. The time is measured in the PROFIBUS slave. If the watchdog is activated and the time TWD (Watch Dog Time) since the last cyclic call expires, the device quits cyclic data exchange mode, goes into the original state (Wait_prm) and sets the outputs to the secure state. The value of TWD and the activation of the watch dog are transferred in the configuration telegram sent on start up from the PROFIBUS Master to the PROFIBUS slave (transition to the data exchange). In general, dimensioning of the time TWD is user-specific (not device-specific and not in the GSD). The lower limit of the value is given by the cycle time. As a rule, the configuration tool is used to enter the time TWD. There are configuration tools for which the watchdog time is set at 1x of PROFIBUS master and others for which the watchdog time is set individually for each PROFIBUS PA station. The value is the same in both cases. For many tools, the time TWD is automatically calculated based on the cycle time of the master with a corresponding transmission rate. At higher transmission rates on the PROFIBUS DP side (for example 12 MBd) cycle times on the PROFIBUS PA side may be longer by a factor of 300. If parameters were set directly for a PROFIBUS PA device using a high transmission rate, TWD is usually less than the PA cycle and the device never exchanges data. Segment coupler SK2 To ensure reliable operation of the PROFIBUS the following bus parameters should be used: Transfer rate 45.45 kBd... 12 MBd Watchdog time TWD = 5 s PROFIBUS DP standard bus parameter
Note! If there are a large number of PROFIBUS PA stations per channel of the SK2 segment coupler, the watchdog time TWD should be verified. The limit for the above value is about 32 stations, but depends on the volume of data to be transferred. The above watchdog time is based on experience. If it is too long (slaves are not switching into the secure state quickly enough) or too short (slaves are switching into the secure state without the master ever having failed) this must be taken into the calculation. Depending on the configuration tool, you can: set parameters for only one watchdog time TWD for the entire PROFIBUS system. In this case, the greatest delay time must be used as the basis for determining TWD. set parameters for a watchdog time TWD for each individual slave. The time TWD set must be greater than the longest delay time TV_max that will occur: TV_max = TCycle_DP + TCycle_PA_cannel where TCycle_PA_channel = TCycle_DP = Cycle time of the PROFIBUS PA channel Cycle time of the PROFIBUS DP side
Determining TWD
Pepperl+Fuchs recommends three times the PROFIBUS PA cycle time be used for the SK2. Calculating TWD The PA cycle time TCycle_PA_channel depends on 1) the number n of stations on a channel and 2) the effective data length L (total bytes input and output data of all devices/no. of devices): Cycle time can be calculated in an approximate manner as TCycle_PA_cannel = n * (0.256 ms * L + 12 ms) + 40 ms For more information on calculating cycle time, please refer to the P+F instruction manuals.
Endress+Hauser
103
8 Device Parametrization
Device Parametrization
This chapter describes the operating concept of the PROFIBUS PA devices and is subdivided as follows: PROFIBUS PA block model Functional survey FieldCare asset management software Commuwin II operating and display program
There are two reasons for parametrizing a PROFIBUS PA or DP device: the adjustment of the operating parameters of the device to calibrate it for the application at hand. In this case the corresponding operating instructions should be used. the adjustment of the profile parameters of the device in order to e.g. scale or simulate the cyclic measured value output to the PLC. Profile parameters are accessible only through the acyclic services of the PROFIBUS DP system. Local operation The operating parameters of most Endress+Hauser devices can be set up using the local operating elements of the device, if they are so equipped. This facility is provided in order that they can be set up before installation, e.g. on a test bench. It is not advisable to change parameters locally during the operation of a system, since this may have unforseen consequences, e.g. on control loops. For this reason, local operating should be disabled when the system is commissioned. More details on this function and the calibration of Endress+Hauser devices are to be found in the corresponding manuals. Device parameters can also be adjusted by the acyclic services of the PROFIBUS DP system, with an appropriate configuration program. This might be embedded within the system or run on an independent workstation. Endress+Hauser offers two alternatives: the FieldCar asset management ent software and the Commuwin II operating and display program. The latter is to be found in many existing plants, but will be gradually replaced over the next year. This chapter contains a short overviewof the parametrization of devices via both these programs. Full descriptions must be taken from the appropriatte device manuals.
Remote operation
104
Endress+Hauser
8.1
PROFIBUS PA block model
The PROFIBUS PA block model describes several parameters that can be used to realise a device. Mandatory parameters must always be present. Optional parameters are only present when required, e.g. for a particular transmitter type. Manufacturer-specific parameters are used to realise device functions that are not in the profile. A manufacturer's operating tool or a device description is required for their operation. Based on this general structure, special block characteristics are specified in the PROFIBUS PA profile. Fig. 8-1 and 8-2 shows the general way in which the blocks are used within the system. In the case of PROFIBUS PA devices that conform to PROFIBUS PA Profile 3.0 , these parameters are managed in block objects.
PLC Device management
Physical block
Sensor signal
Transducer block
Function block
Output value of transmitter/ input value of PLC
Measured value
Fig. 8-1: PROFIBUS PA block model of a sensor
Fig. 8-1 shows the block model of a simple sensor. It comprises four blocks: device management, physical block, transducer block and function block that are described in detail in the following sections. The sensor signal is converted to a measured value by the transducer block and transmitted to the function block. Here the measured value can be scaled or limits can be set before it is made available as the output value to the cyclic services of the PLC.
PLC Device management
Physical block
Input value of actuator (set point)/ output value of PLC
Function block
Transducer block
Signal to valve
Output value
Fig. 8-2: PROFIBUS PA block model of an actuator
For an actuator, the processing is in the reverse order, see Fig. 8-2. The PLC outputs a setpoint value that serves as the input value to the actuator. After any scaling, the setpoint value is transmitted to the transducer block as the output value of the function block. It processes the value and outputs a signal that drives the valve to the desired position.
Endress+Hauser
105
8.2
PROFIBUS PA profile
The PROFIBUS PA profile defines standard block parameters for transmiiters, actuators and analysers. Fig. 8-3 gives an overview of the devices that have been considered in the specification of the flow, pressure, temperature, level blocks etc.
Measuring equipment
Measuring equipment with analogue or digital output
Measuring equipment Limit detection
D (Density)
F (Flow)
L (Level)
Q (Quality)
R (Radiation)
T (Temperature)
W (Weight Mass)
E (Electrical variables)
P (Pressure)
S (Speed, Rotation, Frequency)
Differential pressure
Hydrostatic
Resistance thermocouple
Floating body
Displacement Pressure
Pyrometer
Electromagnetic
Float Differential pressure
Expansion
Ultrasonic
Ultrasonic
Bimetallic strip
Vortex counter
Microwave
Hot/cold conductor
Displacement counter
Laser/optical
Turbine wheel counter
Radiometric
Coriolis
Capacitance
Thermal
Fig. 8-3: Overview of device types covered by the profile blocks
106
Endress+Hauser
The profile itself defines two block structures, one for transmitters and actuators (Fig. 8-4) and a second for analysers (Fig. 8-5), whereby the latter differs only by a number of additional functions.
Sensor(s)
Actuator(s)
Physical Block
Temperaturee, Pressure, Flow, Level
Electropneumatic, Electric Actuation
Discrete Input
Discrete Output
Administration Transducer Blocks Function Blocks

Analog Input Totalizer Analog Output Discrete Input Discrete Output
Cyclic Interface MS0 Remote Access
Acyclic Interface MS1 und MS2
Fig. 8-4: Properties of profile blocks for transmittters and actuators
Actuator
Sensor
Physical Block
Analyser
Transfer
Control
Administration
Limit Alarm
Transducer Blocks
Function Blocks
Analog Input Totalizer Analog Output Discrete Input Discrete Output
Cyclic Interface MSO Remote Access
Acyclic Interface MS1 und MS2
Fig. 8-5: Properties of profile blocks for anayzers
Endress+Hauser
107
8.2.1
Block structure
The parameters assigned to the individual blocks use the data structures and data formats that are specified in the PROFIBUS standard. The structures are designed such that the data are stored and transmitted in an ordered and interpretable manner. All parameters in the PROFIBUS-PA profile, whether mandatory or optional, are assigned an address (slot/index). The address structure must be maintained, even if optional parameters are not implemented in a device, This ensures that the relative indices in the profile are also to be found in the devices. Standard parameters With the exception of the device management, the standard parameters are to be found at the beginning of every block. They are used to identify and manage the block. The user can access these parameters using the acyclic services, e.g. by means of the FieldCare asset management software or the Commuwin II operating and display program. Table 8-1 lists and briefly explains the standard parameters.
Rel. Index 1 Parameter Description R/W M/O
BLOCKOBJECT
Contains the type of block, e.g. function block, as well as further classification information in the form of three storey a tree structure. Event counter: Counts every access to a static block parameter. Static parameters are those device parameters that are not influenced by the process. Text for unambiguous identification of the block: In the physical block, TAG_DESC is used as the measuring point tag. A code number that allows blocks to be grouped together.
ST_REV
TAG_DESC
R, W
STRATEGY
R, W
ALERT_KEY
Identifies the part of the plant where the transmitter is located. Helps in the localisation of events. Describes the operating mode of the block. Three parameters are possible: Actual_Mode Permitted_Mode and Normal_Mode. MODE_BLK allows a functional check of the block. If the block is faulty, a default value can be output. Contains the current status of the block alarms. At the moment only the following are signalled: the change of a static parameter (10 s) and the violation of the advisory and critical limits in the analog input block. Provided for batch processes as per IEC 61512 Part 1. Is only to be found in function blocks.
R, W
MODE_BLK
R, W
ALARM_SUM
R, W
BATCH
R, W
R = Read, W = Write, M/O = Mandatory/Optional parameter Table 8-1: Standard block parameters
108
Endress+Hauser
8.2.2
Device management
Device management comprises the directory for the block and device object structure indicating: which blocks are present in the device, where the start addresses are located (slot/index) and how many objects each block holds. By using this information, the application program of the master can find and transmit the mandatory and optional parameters of a profile block, see Fig. 8-3.
Fig. 8-6: Structure and function of the device management (device management block)
Parameters
Rel. Index 0
Parameters
Description
R/W
M/O
DIRECTORY_OBJECT_HEADER
Header comprising (see Fig. 7.3 for parameter names) Directory code (=0) Directory version number Number of directory objects Number of directory entries Index of the first directory entry Number of block types Pointer: Abs. index + offset, 1st physical block Number of physical blocks Abs. index + offset, 1st transducer block Number of transducer blocks Abs. index + offset, 1st function block Number of function blocks Pointer 1 to 1st block Pointer 2 to 2nd block ..... Pointer # to #th block Continuation of COMPOSITE_DIRECTORY_ENTRIES or start of the pointer entries
COMPOSITE_LIST_DIRECTORY _ENTRIES/
COMPOSITE_DIRECTORY_ENTRIES
COMPOSITE_DIRECTORY_ENTRIES_ CONTINUOUS
R = Read, W = Write, M/O = Mandatory/Optional parameter Table 8-2: Device parameters
Endress+Hauser
109
8.2.3
Transmitter and actuator blocks
This section provides an overview of the purpose and properties of the standard transmitter and actuator blocks as shown in Fig. 8-4. Physical block
Block class Administration Physical Block The physical block contains the software and hardware characteristics of a field device that are associated with its resources, e.g. electronics, operating system, device status, etc.. Similar to the transducer block, the physical block isolates the application block from the hardware-specific properties of the device by the provision of a standardised parameter interface. The following functions are offered through read/write services: Nameplate information (read-only) Diagnosis information (read-only) Write protection management Warm and cold start of the device (write) Change of identity number (read/write) Description
Transducer blocks
Block class Transducer Blocks (TB) Temperature TB
Description
This block describes the characteristics of temperature measurement by resistance temperature devices, thermocouples and pyrometers. It contains the following functions: Characterization of sensor type with default examples Connection type setting (2, 3, or 4 leads) Reference temperature compensation Loadable linearisation table Various measured value combinations from two integrated sensors Provision of measured value in at least one of the following units: K, C, F und Rk Monitoring of sensor, sensor lead connection and hardware Minimum and maximum measured value display
Pressure TB
This block describes the characteristics of pressure and differential pressure measurement for pressure, flow and level measurement applications. It contains the following functions: Characterization of sensor and measuring cell type Sensor calibration Loadable linearisation table Low flow cut-off Provision of measured value in the following units: Pressure: kPA, bar, psi and Hg Flow: m3/h, L/s, CFM cubic feet per minute and lb/s Level: %, m und ft Provision of medium temperature Minimum and maximum temperature value display This block describes the characteristics of flow measurement by the Coriolis, magnetic, ultrasonic, vortex, variable area and themal mass principles. It contains the following functions: Characterization of sensor type and mounting Setting of specific parameters for the various measurement principles, e.g. ultrasonic frequency, vortex frequency etc. Sensor calibration Low flow cut-off Readable sensor values Range limit values with signalling of violations Provision of measured value in at least one of the following units: m3/h, L/s, CFM cubic feet per minute as well as kg/s and lb/s Provision of the temperature and density of the medium
Flow TB
110
Endress+Hauser
Block class Transducer Blocks (TB) Level TB
Description
This block describes the characteristics of level measurement by the radar, ultrasonic, hydrostatic and capacitive principles. It contains the following functions: Characterization of sensor type and mounting Sensor calibration Consideration of tank characterisitics Loadable linearisation table Range limit values with signalling of violations Provision of measured value in at least one of the following units: Level: %, m and ft Provision of the temperature of the medium Readbale sensor values Minimum and maximum temperature value display
Actuation TB
The actuation transducer block describes the characteristics of electropneumatic and electrical positioners and provides the following signals: Characterization of positioning principle Identification of the control valve and positioner (manufacturer, ...) Fail safe position Matching of control parameters Loadable linearisatioin table Suppression of small positioning changes Details of positioning time Details of torque Setting of braking performance Details of opening and closing times Storage of installation data and date of last maintenance
Discrete Input TB
The discrete input transducer block provides the following signal processing functions: Sensor cabling check Identification of the sensor (manufacturer, ...) The discrete output transducer block describes the characteristics of electropneumatic positioners and provides the following signal processing functions, dependent upon actuation priniciple: Identification of the control valve and positioner (manufacturer, ...) Fail safe position Details of positioning time Details on the number and limits of the positioning events Details on the time span of the start of movement after the change in set value as well as the time taken to open and close
Discrete Output TB
Function blocks
Block class Application Function Blocks Analog Input
Description
The analog input function block provides the following signal processing functions for the measured values arriving from a sensor transducer block: Scaling Filtering (PT1 element) Change of operating mode: hand/automatic Special arithmetic functions (e.g. square root for flow values from pressure measurements) Simulation of measured values without the use of a transducer block Provision of replacement values on device faults Warnings, alarms and limit values
Endress+Hauser
111
Block class Application Function Blocks Analog Output
Description
The analog output function block provides the following signal processing functions for setpoint values, which are then passed on to the actuator transducer block. It is particularly suitable for use woth controlled actuators: Scaling Change of operating mode: hand/automatic/local override Simulation of the actual value of the positioner Provision of replacement values (fail-safe) on positioner faults or loss of communication
Discrete Input
The discrete input function block provides the following signal processing functions for the discrete value of a sensor transducer block: Change of operating mode: hand/automatic Inversion of discrete value Simulation of discrete value Provision of replacement values on fault recognition
Discrete Output
The discrete output function block provides the following signal processing functions for set point values, which are then passed on to the actuator transducer block.It is particularly suitable for on/off actuators: Inversion of setpoint value Change of operating mode: hand/automatic/local override Simulation of the actual value of the positioner Provision of replacement values (fail-safe) on loss of setpoint value or loss of communication
Totalizer
The tatalizaer function block provides the following signal processing functions for the setpoint values that are directly linked to a transducer block output: Change of operating mode: hand/automaticg Selection of counting mode (forwards, backwards, positive only, negative only, halt) Reset of totalizer Limit value monitoring
112
Endress+Hauser
8.2.4
Analysis devices
This section provides an overview of the purpose and properties of the special blocks for analysers as shown in Fig. 8-4. Physical block
Block class Administration Physical Block see Section 8.2.3 Description
Transducer blocks
Block class Transducer Blocks (TB) Analyser TB
Description
The analyser transducer block contains the measuring pronciple dependent conversion of sensor value into a measured value with engineering units. It contains the follwoing functions: Specification of sensor measuring range Automatic range switching Specification of sampling rate of measuring signal
Transfer TB
The transfer function block executes mathematical calculations. It can be switched in series with the analyser block. It contains the following functions: Correction of measured value Cross-sensitivity compensation Filtering
Control TB
The control transducer block offers complex functions that allow it to work as a device controller. It performs clocked or command-initiated sequential control of the following field device functions: Measurement System check Cleaning Calibration Initialisation
Limit TB
The limit transducer block provides the following limit monitoring functions for measured values. In order that they are integrated into cyclic communication, limit violations can be signalled to a discrete input block as a binary value. Hysteresis Pull-up and drop-down delay Exceeding of limit values Dropping below of limit values
Alarm TB
On the basis of the NAMUR status classes ready for operation, maintenance necessary, functional check or fault, the alarm transducer block provides the status and predefined texts in the device.
Application blocks
Block class Application Blocks Analog Input Analog Output Discrete Input Discrete Output Logbook
Description
see Section 8.2.3 see Section 8.2.3 see Section 8.2.3 see Section 8.2.3 The logbook is a permanent buffer (ring buffer) for the alarm messages of the alarm transducer block
Endress+Hauser
113
8.2.5
Function overview
The block descriptions in Sections 8.2.3 and 8.2.4 are very generalised and highlight selective functions only. The following table lists more functions of interest to field devices together with their use within the blocks and position in the profile specification, For detailed information it is recommended that the original profile specifications are read.
Device function Contained in Function Block Actuator diagnosis Additional measured values Alarm summing X Transducer Block (TB) X X X X Physical Block Data sheet Actuator Data sheet Transmitter General Requirement, Standard parameter ALARM_SUM General Requirement, Standard parameter STRATEGY und ALERT_KEY General Requirement FB Standard function X X General Requirement, Standard parameter Block Objekt Data sheet Transmitter, Actuator and Analyser - all TBs Data sheet Actuator (AO) Data sheet Transmitter (AI) X Data sheet Transmitter, Actuator and Analyser - all TBs Data sheet Analyser, Transducer Transfer Block Data sheet Analyser - Control Transducer Block Data sheet Analyser, Physical Block extensions X X General Requirement, Physical Block Data sheet Analyser: Additions to Physical Block Data sheet Transmitter (AI), Actuator (AO), Discrete Output (DO) General Requirement, Channel und Link Object X X General Requirement, Standard parameter TAG_DESC Data sheet Transmitter, Actuator and Analyser - all TBs General Requirement (Definition), Data sheet Transmitter (Use) and Aktuator (Use) Data sheet Analyser X General Requirement Data structure DS-33 Reference in PROFIBUS PA-Profile
Application related I/O point characterisation
Batch identification to ISA SP88 Block characterisierung
Calibration
Cascading Check process limit value Check sensor limits
X X
Correction and compensation calculations Device function sequential controller Device function test
Device identication Device status
Fail-Safe functions
FB/TB block links
I/O point designation
I/O point definition
Linearisation
(X)
Logbook functions Measurement, setpoint and control signal status
X X
114
Endress+Hauser
Device function
Contained in Function Block Transducer Block (TB) X X X X Physical Block
Reference in PROFIBUS PA-Profile
Min/Max pointer function Operating mode selection
Data sheet Transmitter - some TBs Data sheet Transmitter (AI), Actuator (AO) Discrete Input (DI) und Discrete Output (DO), General Requirement General Requirement, Standard parameter ST_REV Data sheet Transmitter (AI)and Aktuator (AO) Data sheet Transmitter, Actuator and Analyser - all TBs Data sheet Transmitter, Actuator and Analyser - all TBs X General Requirement, Physical Block Data sheet Transmitter (AI) and Analyser (Transfer Transducer Block) Data sheet Discrete Input and Discrete Output Data sheet Transmitter (AI Simulate) and Actuator (AO Simulate)
Register parameter changes
Scaling
Sensor and actuator characterisation Sensor and actuator identification Signal diagnosis Signal filters X X
Signal inversion
Simulate functions
Table of contents of device
General Requirement, Directory, Mapping Document Directory Data sheet Transmitter (AI-LIN_TYPE)
Transformation into mapping variables Warm and cold start of device Write protection mechanisms Zero point suppression
X X X
General Requirement General Requirement, Physical Block Data sheet Transmitter, Actuator LOW_FLOW_CUT_OFF
Table 8-3: Overview of device functions in PROFIBUS PA Profile Version 3.0
Endress+Hauser
115
8.3
FieldCare Asset Management
FieldCare is Endress+Hauser's FDT based Plant Asset Management Tool. It can configure all intelligent field devices in your plant and supports you in managing them. By using status information, it also provides a simple but effective means of checking their health. Supports Ethernet, HART, PROFIBUS, and in future FOUNDATION Fieldbus etc. Operates all Endress+Hauser devices Integrates third-party devices such as actuators, I/O systems and sensors supporting the FDT standard Ensures full functionality for all devices with DTMs Offers generic profile operation for any third-party fieldbus device that does not have a vendor. Installation and commissioning FieldCare ensures that devices can be integrated and configured quickly and easily, with the transparency demanded by good manufacturing practice. User Management allows access rights to beassigned according to user authorisation Network View aids the building of projects Bus Scan automatically finds the devices in the network DTM Device Catalogue facilitates DTM handling and improves system reliability Device DTMs simplify device configuration,including addressing, advanced diagnosisand linearisation Activity Logging and Reporting ensures that all changes to the application or project are registered and traceable Customisation simplifies handling and improves the availability and accessibility of program functions Operations and Maintenance FieldCare manages device life-cycle information and presents it quickly and clearly to the user. Plant View enables quick retrieval of information by showing your assets structured according to ISA S88 into sites, areas, process cells etc. Document Management allows manuals, SOPs, certificates etc.to be linked to a device Placeholders allow display and documentation of transparent or non-communicating equipment Activity Logging registers all user activities with time stampand user ID Report Management generates reports on the state of devices, applications and projects Condition Monitoring will in future give a quick overview of field devices status with immediate location of faulty measuring points
116
Endress+Hauser
8.3.1
Using FieldCare
FieldCare runs on an IBM compatible PC or Notebook under Windows 2000, NT or XP. There are two basic ways in which it can be used in a PROFIBUS system, see Fig. 8-7: The PC is connected directly to the PROFIBUS DP segment via a PROFIBOARD (PC) or PROFICARD (Notebook) and acts as a PROFIBUS. During system integration the computer is registered as a Class 2 master. The PC is resident on the Ethernet TCP/IP backbone and connected to the PROFIBUS network via the Fieldgate FXA720 PROFIBUS/Ethernet gateway. During system integration the Fieldgate is registered as a Class 2 master.
ES
OS
ES
OS
FC
Backbone PLC PC with PROFIBUS interface PLC
Ethernet
FC
Fieldgate FXA720 PROFIBUS DP
PROFIBUS DP
12:00
14:00
16:00
18:00
20:00
22:00
12:00
14:00
16:00
18:00
20:00
22:00
PROFIBUS PA
PROFIBUS PA
HART
Fig. 8-7: FieldCare architectures: left at DP level, right operating from Ethernet
HART
Operation (Network View)
The essence of FieldCare operation is the engineering of the physical network in the so-called network view. This is done by means of CommDTMs for communication objects such as the PROFIBUS card or Fieldgate FXA720, DeviceDTMs for the field devices in the network and Profile DTMs for devices that conform to the PROFIBUS or HART standards, but which do not have a device-specific DTM, see Fig. 8-8. In order that the full network can be reprresented, placeholder DTMs are available non-communicating devices. More details are in the FieldCare on-line help.
HOST PROFIBUS CommDTM DTM Promass Placeholder DTM Coupler DTM Valve DTM Promag DTM Positioner CommDTM Remote I/O DTM Hart device DTM Hart device DTM Hart device HOST Fieldgate CommDTM DTM Promass Placeholder DTM Coupler DTM Valve DTM Promag DTM Positioner CommDTM Remote I/O DTM Hart device DTM Hart device DTM Hart device
Fig. 8-8: Mapping of the networks in Fig. 8-7 in FieldCare Network View
The devices are operated by opening the corresponding DTM from the Network View, see e.g. Section 7.4.1, setting the bus parameters from FieldCare and the example overleaf.
Endress+Hauser
117
8.3.2
Generation of a live list
For a PROFIBUS network, the generation of the tree in Network View is practically automatic: 1. Add the PROFIdtmDPV1 to the Host The same CommDTM is used for PROFIboard, PROFIcard and Fieldgate For Fieldgate, the Host must know the IP address 2. In the Menu bar select Tools Fieldbus Scan Generate Network
3. A live list with TAGs is generated of the devices connected to the PROFIBUS network
8.3.3
Device parametrization
Devices are parametrized by opening the corresponding DTM from the device list. This can be done both off-line and on-line: Off-line parametrization: 1. Click on the device you wish to work on. 2. In the menu bar select Parametrization Device operation Device functions Offline-
3. The device DTM opens: now set the parameters as described in the device manual
Up-/Download:
The Upload function allows data from the device to be transferred and stored in FieldCare. With the Download function, parameters can be transferred from FieldCare and stored in the selected device. This function must now be used to download the configuration generated during offline parametrization to connected device. 1. Click on the device you wish to work on. 2. In the menu bar select Device operation Go Online Device functions Download to
3. When the green dot appears next to the device, select device
118
Endress+Hauser
8.3.4
On-line parametrization
1. Click on the device you wish to work on. 2. In the menu bar select Device operation Go Online Device functions Online-
3. When the green dot appears next to the device, select Parametrization
4. The device DTM opens: now set the parameters as described in the device manual
8.3.5
Plant View
Plant View is a logical mapping of the plant built up according to the ISA S88 standard. It gives an overview of the location of a device within a particular facility.
Fig. 8-9: Plant View is a logical mapping of the plant topology
Plant view forms the basis of FieldCares condition monitoring function. It also provides a convenient way of storing plant documentation, which can be allocated to and retrieved from any position in the plant view tree. This function is not restricted to PROFIBUS or HART devices, since a placeholder can be used at any position to represent a non-communicating device. This also applies to the Network view.
Endress+Hauser
119
8.4
Commuwin II Operating Program
The PROFIBUS DP devices Promass and Promag as well as all PROFIBUS PA devices can be operated by the operating program Commuwin II (from software version 2.0 upwards) A full description of Commuwin II is to be found in operating instructions BA124F/00/en. All the standard functions of Commuwin II are supported excepting envelope curves for ultrasonic and microwave devices. The device settings can be made using the operating matrix or graphic operating interface.
!
Requirements
Note! Due to the introduction of FieldCare, Commuwin II will be phased out by 2006. While support will continue over this period, new devices will not be integrated. Commuwin II runs on an IBM-compatible PC or Laptop. The computer must be equipped with a PROFIBUS interface, i.e. PROFIBOARD for PCs and PROFICARD for laptops. Alternatively, a Fieldgate FXA720 can be be used, see also Fig. 8-7. During the system integration, the computer is registered as a Class 2 master.
8.4.1
Operation
The PA-DPV1 server must be installed. The connection to Commuwin II is opened from the PADPV1 server. 1. Generate a live list with "Tags" 2. Endress+Hauser operation is selected by clicking on the device name, e.g. FEB 24 (Deltapilot S).
3. Select profile operation is selected by clicking on the appropriate tag, e.g. AI: LIC 123 = Analog-Input-Block Deltapilot S.
4. The settings are entered in the device menu.
120
Endress+Hauser
8.4.2
Device menu
The device menu allows matrix or graphical operation to be selected. In the case of matrix operation, the device or profile parameters are displayed in a matrix. A parameter can be changed when the corresponding matrix field is selected. In the case of graphical operation, the operating sequence is shown in a series of pictures with parameters. For profile operation, the pictures Diagnosis, Scaling, Simulation and Block are of interest.
Fig. 8-10: Basic calibration of the Deltapilot S using graphical configuration
The device parameters are set in accordance with the corresponding operating instructions. Tables of profile functions are also to be found here. The parameter blocks are adapted to the transmitters. Third-party devices can also be operated via the profile parameters. In this case, standardised transducer, function or physical blocks appear. Off-line operation Commuwin also allows the devices to be configured off-line. After all parameters have been entered, the file generated can be loaded into the connected device. This function allows the parameters of an already configured device to be loaded and stored in Commuwin II. If several devices (with the same software version) have to be configured in the same way, the parameters can now be downloaded into the devices. Fig. 8-11 shows the graphical operation for the scaling of the Deltapilot S. By selecting the device profile "AI transmitter block" (acknowledge with .) the parameters PV_SCALE and OUT_SCALE can be set. Please note that for DPV1 Version 2.0, the unit is not transmitted with the measured value. The setting of the PV unit also has no effect on the output value OUT. The operating picture "Diagnosis" shows the current status of the device. "Simulation" allows a measured value to be simulated, "Block" displays the current setting of the mode block..
Up-/download
Scaling
Fig. 8-11: Scaling of the PA device output using Commuwin II
Endress+Hauser
121
9 Trouble-Shooting
Trouble-Shooting
This chapter contains a summary of the most frequent faults and questions concerning PROFIBUS that have been dealt with by our service department. It is subdivided as follows: Commissioning PLC network design Data transmission Commuwin II
9.1
Commissioning
Cause/Remedy With the exception of the analysis device Mypro, all Endress+Hauser devices have an address switch that allows hardware or software addressing. Software address changes can be made via the PROFIdtmDPV1 CommDTM is FieldCare, the DPV1-DDE server of Commuwin II or any other PROFIBUS operating tool. See also Chapter 6.6. PROFIBUS PA: There is no termination switch on the device itself. The bus is terminated by using a separate terminator or a T-box with a switchable terminating element PROFIBUS DP: Termination switches are located in the devices. We recommend the use of PROFIBUS connectors with integrated terminators (in cabinet or field) The segment coupler supplies a defined maximum output current to the segment. Every device requires a particular basic current (see Chapter 5.3). If the sum of the basic currents exceeds the output current of the coupler, the bus become unstable. Diagnosis: Measure the current consumption of the devices with an ammeter. Remedy: Reduce the electrical load on the segment concerned, i.e. one or more devices must be disconnected. If a Siemens DP/PA-link Type IM 157 is used, the internal address must be taken into consideration. On the PROFIBUS-PA side, the link has the fixed internal address 2. For this reason, the address 2 may not be assigned to any of the PROFIBUS PA slaves connected to the link. Two devices (slave or master) have the same address. Disconnect the slave with address 2 from the bus and check whether there are others on the bus with the same address (e.g. with FieldCare of Commuwin II). Readdress as approprate. Check the settings of the PROFIBUS master as to whether the address 2 has been allocated twice.
Question/Fault How can I assign an address to a device?
Where is the device termination switch?
When a device is added to the bus, the segment fails
PROFIBUS-PA slave with address 2 cannot be found.
122
Endress+Hauser
9 Trouble-Shooting
9.2
PLC planning
Cause/Remedy The Siemens S5 PLC cannot interpret the IEEE floating point format. A conversion module is required that transforms the IEEE floating point value into Siemens KG format. This can be obtained from Siemens. The module is for Types 135 U and 155 U but not for 115 U and 95 U. The function module SFC 14 must be used. The SFC 14 ensures that e.g. 5 bytes can be consistently loaded into the SPS. If the SFC 14 is not used, only 4 bytes can be consistently loaded into the Siemens S7. Newer versions of the S7 series can access the I/O buffer directly. The SFC 14 is no longer required. The parameters PV_SCALE and OUT_SCALE are not set correctly. OUT_SCALE_Min. = PV-Min. OUT_SCALE_Max. = PV-Max. Instructions on how to adjust the parameters PV_SCALE and OUT_SCALE in the function block can be taken from the device operating instructions. The bus parameters and baudrate were not set when the PLC was configured. The baudrate to be set depends upon the segment coupler used (Chapter 7-5). - Pepperl+Fuchs SK1: 93,75 kBit/s - Siemens: 45.45 kBit/s - PA link (Siemens): freely selectable - Pepperl+Fuchs SK1: 93.75 kBit/s - Pepperl+Fuchs SK2: freely selectable For P+F SK2, the PROFIBUS PA GSD has not been converted The bus parameters require adjustment The polarity of the PROFIBUS-DP line is reversed (A and B)? PROFIBUS-DP bus not terminated? Both the beginning and the end of the bus must be terminated.
Question/Fault The measured value in the Siemens S5 is incorrect
The measured value in Siemens S7 PLCs is always zero
The measured value at the device display is not the same as that in the PLC.
No connection between the PLC and the PROFIBUS PA network.
9.3
Data transmission
Cause/Remedy The measured values are transmitted in 5 byte long data blocks. 4 bytes are used to transmit the measured value. The fifth byte contains standardised status information. Error codes for Endress+Hauser device faults, e.g. E 641, are not transmitted with the status. For limit switches, the information is transmitted in two bytes: Signal condition and status information. See Chapters 3-4 and 7-2. See Chapter 7.3. See Chapter 7.2
Question/Fault How are data transferred to the PLC?
What does status information mean? How is data transmitted from the Promag 53 to the PLC? How can the totalisor of the Promag 53 be reset? How can the PLC switch on the positive zero return of the Promag 53? How can the totalisor of the Promass 83 be reset? How can I suppress a measured value in cyclic communcaition? How can I write a value to the local display?
Via the output word of the cyclic services for the totalisaer in question, see Chapter 7.2 Via the output word of the cyclic services
Via the output word of the cyclic services, see corresponding operating manual By using the placeholder "EMPTY_MODULE" or "FREE_PLACE" during configuration, see Chapter 7.2. By using the Display_Value model from the GSD (if supported), see Chapter 7.2.
Endress+Hauser
123
9 Trouble-Shooting
9.4
Commuwin II
Cause/Remedy Commuwin II is a Class 2 master that allows the transmission of acyclic values. The PROFIBUS-DP baudrate to be set depends upon the segment coupler used.
Question/Fault Commuwin II cannot open the connection to the PROFIBUS PA devices. The connection to the devices cannot be opened.
If the PLC and Commuwin II are used in parallel, the bus parameters must be mutually compatible. The bus parameters must be identical for all connected masters. If Commuwin II is used, the Token Rotation Time (TTR) calculated by the PLC configuration tool must be increased by 20 000 bit times and the corresponding value entered in the Commuwin II DDE server In the case of a Siemens S5 system with ComProfibus, the Delta TTR must be increased by 20 000 bit times. The HSA parameter (Highest Station Address) must permit the Commuwin II address. The HSA specifies the highest address permitted for active participants (masters) on the bus. Slaves can have a higher address. Is the Commuwin II address free or is it being used by another device? Is the correct baudrate set? Have the drivers and cards been correctly installed? Is the green LED on the TAP of the Proficard or Profiboard lit? Is the GAP update to high (the result is longer waiting times)? Device is not connected to segment. Address used twice. The device version is not supported by Commuwin II. A full device description is necessary. The default parameters of the PROFIBUS-PA profile are offered. Full operation is possible for Endress+Hauser devices and Samson positioners only. If the measured value at the device display is to be the same as that transmitted to the PLC, the parameters PV_SCALE and OUT_SCALE must be matched. - OUT_SCALE_MIN = PV_SCALE_MIN - OUT_SCALE_MAX = PV_SCALE_MAX See the device operating instructions.
A device does not appear in the live list. Device cannot be fully operated.
A change of unit at the device has no effect on the value on the bus.
124
Endress+Hauser
10 Technical Data
10
10.1
Identification
Designation Application
Technical Data
PROFIBUS DP
PROFIBUS DP Fieldbus for factory automation and process control
Function and system design
Bus access method Topology No of participants
Multimaster with logical token ring and master-slave See Chapter 2.2 Max. 126 per Bus, but max. 32 per segment Segments can be connected together with repeaters up to 12 Mbit, dependent upon transmission medium and cable length Digital, differential signals according RS 485, NRZ HD=4, Parity-Bit, Start- and End-Delimiter Dependent upon the data transmission rate
Baudrate Data transmission Data storage Response time
Electrical connection
Bus cable Copper: screened, twisted pairs, screening grounded at both ends. Cable specifications, see Chapter 3.2 Fibre optics: see PROFIBUS DP specifications Line topology Copper: up to 1200 m, depending upon baudrate, see Chapter 2.2 Total length of all spurs max. 6.6 m, for baudrates > 1.5 Mbit/s none Connecting elements: 9-pole Sub-D connectors with RS 485 or T-Box At both ends of every segment Max. 9 Repeater
Topology Cable length Spur length
Bus connection Bus termination Repeater
Human interface
Local operation PC operation
If appropriate, via keys or touch keys Via operating program, e.g. FieldCare or Commuwin II and PROFIBUS interface card (if supported by PROFIBUS PA profile) Set with DIP switch, local operating elements or software Software/hardware addressing selectable
Bus address
Standards
PROFIBUS DP
IEC 61158 and IEC 61784 PNO Guidelines for PROFIBUS DP possible: RS 485-IS with EEx ib RS 485
Intrinsic safety Physical layer
Endress+Hauser
125
10 Technical Data
10.2
Identification
Designation Application
PROFIBUS PA
PROFIBUS PA (Process Automation) Intrinsically safe fieldbs for process engineering
Function and system design
Bus access method Topology No. of participants
Multimaster with logical token ring and master-slave See Chapter 3 max. 32 for non-hazardous applications max. 20 for EEX ib IIB max. 10 for EEX ia/ib IIC The actual number is dependent upon the the segment coupler and the current consumption of the participants 31.25 kBits/s Digital, bit synchron, Manchester II coding Prambel, fehlergesicherte Start-End-Delimiter, CRP Dependent upon the number of devices on the bus: t = n x 10 ms + PLC program run time + DP transmission time
Baudrate Data transmission Data storage Update time
Electrical connection
Bus power supply, typical values
EEx ia/ib IIC: 13,5 V, 128 mA EEx ia/ib IIB: 13,5 V, 280 mA Nicht-Ex: 24 V, 400 mA see Chapter 3.2 Preferred: screened, twisted pairs, screening ground at both sides Cable specifications (and other types), see Chapter 3.3 Line- and tree topology, combination possible. For hazardous applications only line topology possible. Dependent upon application and bus coupler, see Chapter 3.3 Max. 30 m each for hazardous applications, otherwise as in Chapter 3.3 Connection elements: T-pieces, junction boxes At both ends Specifications: R = 100 W 2 %, C = 1 mF 20 % Max. 4 per bus segment
Bus cable
Topology
Cable length Spur length Bus connection Bus termination
Repeater
Human interface
Local operation PLC operation PC operation
If appropriate, via keys or touch-keys Via common parameters and profile commands Via operating program, e.g. FieldCare or Commuwin II and PROFIBUS interface card Set with DIP switch, local operating elements or software Software/hardware addressing selectable
Bus address
Standards
PROFIBUS PA
IEC 61158 and IEC 61784 PNO Guidelines for PROFIBUS PA EN 50 020, FISCO-model, IEC 79-14 IEC 61158-2 (MBP)
Intrinsic safety Physical layer
126
Endress+Hauser
11 PROFIBUS Components
11
11.1
Cerabar M
Cerabar M
PROFIBUS Components
Endress+Hauser field devices PROFIBUS PA
Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area:
Pressure 151C Power supply via bus 9...32 VDC 9...24 VDC 9...17.5 VDC according FISCO 11 mA 0 mA < basic current Yes DIP switch, software see Chapter 5.6 3.0 Analog Input, Transducer Block Pressure, Physical Block None Yes see BA 222P/00/en Z00628 No
Max. basic current (IB) Fault current (IFDE) PMC41 PMC45 PMP41 PMP45 PMP46 PMP48 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
Additional signals Application in hazardous area Ex certificate PNO certificate PROFIBUS DP version available
Endress+Hauser
127
Cerabar S
Cerabar S Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Pressure 1501 Power supply via bus 9...32 VDC 9...24 VDC 9...17.5 VDC according FISCO 11 mA 0 mA < basic current Yes DIP switch, software see Chapter 5.6 3.0 Analog Input, Transducer Block Pressure, Physical Block None Yes see BA 168P/00/en Z00656 no
Max. basic current (IB) Fault current (IFDE) PMC631 PMC731 PMP635 PMP731 PMC71 PMP71 PMP72 PMP75 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
128
Endress+Hauser
Deltabar S
Deltabar S Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Differential pressure 1504 Power supply via bus 9...32 VDC 9...24 VDC 9...17.5 VDC according FISCO 11 mA 0 mA < basic current Yes DIP switch, software see Chapter 5.6 3.0 Analog Input, Transducer Block Pressure, Physical Block None Yes see BA 167P/00/en Z00655 No
Max. basic current (IB) Fault current (IFDE) PMD230 FMD230 FMD235 FMD630 FMD633 FMD76 FMD77 FMD78 PMD70 PMD75 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
Endress+Hauser
129
Deltapilot S
Deltapilot S Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Level 1503 Power supply via bus 9...32 VDC 9.6...32 VDC (only for FEB24 P) 9...24 VDC 9...17.5 VDC according FISCO For FEB24 P, 9.6... 11 mA 0 mA < basic current Yes DIP switch, software see Chapter 5.6 3.0 Analog Input, Transducer Block Level, Physical Block None Yes see BA 164F/00/en Z00657 No
Hazardous area:
Max. basic current (IB) Fault current (IFDE) DB50 DB50A DB50 DB50S DB51 DB51A DB52 DB52A DB53 DB53A FEB24 FEB24P Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
130
Endress+Hauser
Levelflex M
Levelflex M Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Level 152D Power supply via bus 9...32 VDC 9...24 VDC 9...17.5 VDC according FISCO 11 mA 0 mA < bsic current Yes DIP switch, software see Chapter 5.6 3.0 Analog Input, Transducer Block Level (herstellerspezifisch), Physical Block None Yes see BA 757F/00/en Z00657 No
Max. basic current (IB) Fault current (IFDE) FMP40 FMP41C Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
Endress+Hauser
131
Liquiphant M
Liquiphant M Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Level, limit switch for liquids 152B Power supply via bus 9...32 VDC 9...24 VDC 9...17.5 VDC according FISCO 11 mA 0 mA < basic current Yes DIP switch, software see Chapter 5.6 3.0 Discrete Input, Transducer Block DI, Physical Block None Yes see BA 141F/00/en Z00690 No
Max. basic current (IB) Fault current (IFDE) FDL60 FDL61 FEL67 FTL670 FTL50 FTL51 FTL50H FTL51H Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
132
Endress+Hauser
Liquisys M
Liquisys M Process variable pH-Wert, Conductivity, Trbung, Sauerstoff, Chlor 1515 Conductivity 1516 pH-value 1517 Turbidity 1518 Oxygen 1519 Chlorine 100/115/230 V AC +10/-15%, 48...62 Hz 24 V AC/DC +20 / -15% Bus communication 9...32 VDC 11 mA 0 mA < Basic current Yes DIP switch, software, local operation see Chapter 5.6 keine Analog Input, Transducer Block (manufacturer specific), Physical Block (manufacturer specific) Relay No None None Yes
PROFIBUS ID code (Hex)
Auxiliary energy (local)
Auxiliary energy Non-hazardous area: Max. basic current (IB) Fault current (IFDE) LF pH Tu O2 Cl CUM223 CUM253 COM223 COM253 CPM223 CPM253 CCM223 CCM253 CLM223 CLM253 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
Endress+Hauser
133
Micropilot M
Micropilot M Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Level 1522 Power supply via bus 9...32 VDC 9...24 VDC, 9...17.5 VDC according FISCO 13 mA 0 mA < Basic current Yes DIP switch, software see Chapter 5.6 3.0 Analog Input, Transducer Block Level (manufacturer specific), Physical Block None Yes see BA 227F/00/en Z00629 No
Max. basic current (IB) Fault current (IFDE) FMR230V FMR231E FMR230 FMR231 FMR240 FMR530 FMR531 FMR532 FMR533 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
134
Endress+Hauser
Multicap
Multicap Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Level 153A Power supply via bus 9...32 VDC 9...24 VDC 9...17.5 VDC according FISCO 14 mA 0 mA < Basic current Yes DIP switch, software see Chapter 5.6 3.0 Analog Input, Transducer Block Level, Physical Block None Yes see BA 261F/00/en Z00629 No
Max. basic current (IB) Fault current (IFDE) FEC14 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
Endress+Hauser
135
Mycom S
Mycom S Process variable PROFIBUS ID code (Hex) Conductivity, pH-value 1535 Conductivity, conductive 1537 Conductivity, inductive 1539 pH-value 100...230 V AC +10/-15%; 24 V AC/DC +20/-15% 9...32 VDC 9...24 VDC, 9...17.5 VDC according FISCO 11 mA 0 mA < Basic current Yes DIP switch, software, local operation see Chapter 5.6 3.0 Analog Input, Analyser Transducer Block, Physical Block Relay Yes see BA 234C/07/en, BA 298C/07/en Z00919, Z00920, Z0921 No
Auxiliary energy
Non-hazardous area: Hazardous area: Max. basic current (IB) Fault current (IFDE) CLM153 CPM153 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
136
Endress+Hauser
Mypro
Mypro Process variable PROFIBUS ID code (Hex) Conductivity, pH-value 150C Conductivity (inductive/conductive) 150D pH-value Power supply via bus 9...32 VDC 9...24 VDC 9...17.5 VDC according FISCO 11 mA 0 mA < Basic current Yes Software, local operation see Chapter 5.6 None Analog Input, Analyser Transducer Block (manufacturer specific), Physical Block (manufacturer specific) None Yes see BA 198C/07/en No No
Auxiliary energy Non-hazardous area: Hazardous area: 9...24 VDC Max. basic current (IB) Fault current (IFDE) CPM431 CLM431 CLD431 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
Endress+Hauser
137
Promag 33/35
Promag 33/35 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 1505 85...260 V AC, 45...65 Hz 20...55 V AC, 45...65 HZ 16...62 V DC Bus communication 9...32 VDC 9...24 VDC (only Promag 33) 12 mA 0 mA < Basic current Yes DIP switch, software, local operation see Chapter 5.6 2.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block 1 x 4...20 mA Flow Yes (only Promag 33) see BA 029D/06/en Z00410 Yes
Auxiliary energy Non-hazardous area: Hazardous area: Max. basic current (IB) 33A 33D 33F 33H 33P 33W 35A 35D 35F 35H 35P 35W Fault current (IFDE) Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
138
Endress+Hauser
Promag 50
Promag 50 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 1525 85...260 V AC, 45...65 Hz 20...55 V AC, 45...65 HZ 16...62 V DC Bus communication 9...32 VDC 9...32 VDC 11 mA 0 mA < Basic current Yes DIP switch, software, local operation see Chapter 5.6 3.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block None Yes see BA 055D/06/en Z00632 No
Auxiliary energy Non-hazardous area: Hazardous area: Max. basic current (IB) 50W 50P 50H Fault current (IFDE) Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
Endress+Hauser
139
Promag 53
Promag 53 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 1527 85...260 V AC, 45...65 Hz 20...55 V AC, 45...65 HZ 16...62 V DC Bus communication 9...32 VDC 9...32 VDC 11 mA 0 mA < Basic current Yes DIP switch, software, local operation see Chapter 5.6 3.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block None Yes see BA 053D/06/en Z00633 Yes
Auxiliary energy Non-hazardous area: Hazardous area: Max. basic current (IB) 53W 53P 53H Fault current (IFDE) Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
140
Endress+Hauser
Promass 63
Promass 63 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 1506 85...260 V AC (50...60 Hz) 20...55 V AC, 16...62 V DC Bus communication 9...32 VDC 9...32 VDC 12 mA 0 mA < Basic current Yes DIP switch, software, local operation see Chapter 5.6 2.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block 1 x 4...20 mA (Mass, Density, Temperature) Yes see BA 063D/06/en Z00407 Yes
Auxiliary energy Non-hazardous area: Hazardous area: Max. basic current (IB) 63A 63E 63F 63H 63I 63M Fault current (IFDE) Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
Endress+Hauser
141
Promass 80
Promass 80 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 1528 85...260 V AC, 45...65 Hz 20...55 V AC, 45...65 HZ 16...62 V DC Bus communication 9...32 VDC 9...32 VDC 11 mA 0 mA < Basic current Yes DIP switch, software, local operation see Chapter 5.6 3.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block None Yes see BA 072D/06/en Z00669 No
142
Endress+Hauser
Promass 83
Promass 83 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 152A 85...260 V AC, 45...65 Hz 20...55 V AC, 45...65 HZ 16...62 V DC Bus communication 9...32 VDC 9...32 VDC 11 mA 0 mA < Basic current Yes DIP switch, software, local operation see Chapter 5.6 3.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block None Yes see BA 063D/06/en Z00670 Yes
Endress+Hauser
143
Prosonic Flow 90
Prosonic Flow 90 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 152F 85...260 V AC, 45...65 Hz 20...55 V AC, 45...65 HZ 16...62 V DC Bus communication 9...32 VDC 9...32 VDC 11 mA 0 mA < Basic current Yes DIP switch, software, local operation see Chapter 5.6 3.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block None Yes see BA 074D/06/en Z00871 No
Auxiliary energy Non-hazardous area: Hazardous area: Max. basic current (IB) 90W 90U 90C Fault current (IFDE) Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
144
Endress+Hauser
Prosonic Flow 93
Prosonic Flow 93 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 1530 85...260 V AC, 45...65 Hz 20...55 V AC, 45...65 HZ 16...62 V DC Bus communication 9...32 VDC 9...32 VDC 11 mA 0 mA < Basic current Yes DIP switch, software, local operation see Chapter 5.6 3.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block None Yes see BA 076D/06/en Z00869 Yes
Auxiliary energy Non-hazardous area: Hazardous area: Max. basic current (IB) DDU10 DDU15 DDU18 DDU19 Fault current (IFDE) Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
Endress+Hauser
145
Prosonic M
Prosonic M Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Level 152C Power supply via bus 9...32 VDC 9...24 VDC 9...17.5 VDC according FISCO 12 mA 0 mA < Basic current Yes DIP switch, software see Chapter 5.6 3.0 Analog Input, Transducer Block Level (manufacturer specific), Physical Block None Yes see BA 283F/00/en Z00724 No
Max. basic current (IB) Fault current (IFDE) FMU40 FMU41 FMU43 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
146
Endress+Hauser
Prosonic T
Prosonic T Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Max. basic current (IB) Fault current (IFDE) FMU130 FMU131 FMU230 FMU231 FMU232 FTU230 FTU231 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data Level 1502 Power supply via bus 9...32 VDC 9...24 VDC 13 mA, at FMU 232 max. 17 mA 0 mA < Basic current Yes DIP switch, software see Chapter 5.6 2.0 Analog Input, Transducer Block Level, Physical Block None Yes see BA 283F/00/en Z00402 No
Endress+Hauser
147
Prowirl 72
Prowirl 72 Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Flow 153B Power supply via bus 9...32 VDC 9...24 VDC, 9...17,5 VDC according FISCO 15 mA 0 mA < Basic current No DIP switch, software see Chapter 5.6 3.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block None Yes see BA 085D/06/en Z00835 No
Max. basic current (IB) Fault current (IFDE) 72F 72W Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
148
Endress+Hauser
Prowirl 73
Prowirl 73 Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Flow 153C Power supply via bus 9...32 VDC 9...24 VDC, 9...17,5 VDC according FISCO 15 mA 0 mA < Basic current No DIP switch, software see Chapter 5.6 3.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block None Yes see BA 094D/06/en requested No
Max. basic current (IB) Fault current (IFDE) 73F 73W Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
Endress+Hauser
149
RID 261
RID 261 Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Max. basic current (IB) Fault current (IFDE) RID261 Start-up current Local operation Variabel (display function) None Power supply via bus 9...32 VDC 9...15 VDC 11 mA 0 mA < Basic current Setting of the address of the monitored slaves and setting of the process variable offset via DIP-switch None None 3.0 None None Yes see BA 098R/09/C4 No No
Addressing Cyclic data to PLC PA profile version Acyclic profile data Additional signals Application in hazardous area Ex certificate PNO certificate PROFIBUS DP version available
150
Endress+Hauser
Smartec S
Smartec S Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Conductivity 153E 100...230 V AC +10/-15% bei 47...64 Hz; 24 V AC/DC +20/-15% Bus communication 9...32 V DC 11 mA 0 mA < Basic current Yes DIP switch, software, local operation see Chapter 5.6 3.0 Analog Input, Transducer Block Analyser, Physical Block None No No Z00955 Yes
Auxiliary energy Non-hazardous area: Max. basic current (IB) Fault current (IFDE) CLD132 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
Endress+Hauser
151
TMT 184
TMT 184 Process variable PROFIBUS ID code (Hex) Auxiliary energy Non-hazardous area: Hazardous area: Temperature 1523 Power supply via bus 9...32 VDC 9...24 VDC, 9...17,5 VDC according FISCO 11 mA 0 mA < Basic current No DIP switch, software see Chapter 5.6 3.0 Analog Input, Transducer Block Temperature, Physical Block None Yes see BA 115R/09/A3 Z00694 No
Max. basic current (IB) Fault current (IFDE) TMT184 Start-up current Local operation Addressing Cyclic data to PLC PA profile version Acyclic profile data
152
Endress+Hauser
11.2
ASP 2000
ASP 2000
Endress+Hauser field devices PROFIBUS DP
Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Supported bus velocities (kBit/s)
Stationary sampler 1533 230 V AC, 50/60 Hz 45.45, 93.75, 187.5, 500, 1500, 3000, 6000, 12000 Yes Yes DIP switch, local operation 60 bytes Inputs + 60 bytes Outputs None None None Yes see BA 080R/09/en No
Integrated bus termination (Terminator) Local operation Adressing ASP2000 Cyclic data to PLC PA profile version Acyclic profile data Additional signals Application in hazardous area Ex certificate PNO certificate
Liqisys M
Liquisys M Process variable pH-value, Conductivity, Turbidity, Oxygen, Chlorine 151D Chlorine, 151E Oxygen, 151F Turbidity, 1520 pH-value, 1521 Conductivity 100/115/230 V AC +10/-15%, 48...62 Hz 24 V AC/DC +20 / -15% 45.45, 93.75, 187.5, 500, 1500, 3000, 6000, 12000 No Yes DIL switch, software, local operation see Chapter 5.6 None Analog Input, Transducer Block (manufacturer specific), Physical Block (manufacturer specific) Relay None No No
PROFIBUS ID code (Hex)
Auxiliary energy (local)
Supported bus velocities (kBit/s)
Integrated bus termination (Terminator) Local operation Adressing CCM223 CCM253 CLM223 CLM253 COM223 COM253 CUM223 CUM253 CPM223 CPM253 Cyclic data to PLC PA profile version Acyclic profile data
Additional signals Application in hazardous area Ex certificate PNO certificate
Endress+Hauser
153
Memo-Graph DP (slave)
Memo-Graph (DP slave) Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Display several I/O 150F 115...230 VAC, 50/60 Hz 24 V AC/DC, 0/50/60 Hz 45.45, 93.75, 187.5, 500, 1500, 3000, 6000, 12000 Yes Yes Local operation see Chapter 5.6 None None Relay, AI, AO, DI, DO No No No
Integrated bus termination (Terminator) Local operation Adressing RSG10 Cyclic data to PLC PA profile version Acyclic profile data Additional signals Application in hazardous area Ex certificate PNO certificate
Promag 33/35
Promag 33/35 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 1511 85...260 V AC, 45...65 Hz 20...55 V AC, 45...65 HZ 16...62 V DC 45.45, 93.75, 187.5, 500, 1500, 3000, 6000, 12000 Yes Yes DIP switch, software, local operation see Chapter 5.6 2.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block 1 x 4...20 mA Flow Yes (only Promag 33) see BA 029D/06/en Z00572
Integrated bus termination (Terminator) Local operation Adressing 33A 33D 33F 33H 33P 33W 35A 35D 35F 35H 35P 35W Cyclic data to PLC PA profile version Acyclic profile data
154
Endress+Hauser
Promag 53
Promag 53 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 1526 85...260 V AC, 45...65 Hz 20...55 V AC, 45...65 HZ 16...62 V DC 45.45, 93.75, 187.5, 500, 1500, 3000, 6000, 12000 Yes Yes DIL switch, software, local operation see Chapter 5.6 3.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block None Yes see BA 053D/06/en Z00631
Integrated bus termination (Terminator) Local operation Adressing 53W 53P 53H Cyclic data to PLC PA profile version Acyclic profile data
Promass 63
Promass 63 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 1506 85...260 V AC (50...60 Hz) 20...55 V AC, 16...62 V DC 45.45, 93.75, 187.5, 500, 1500, 3000, 6000, 12000 Yes Yes DIP switch, software, local operation see Chapter 5.6 2.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block 1 x 4...20 mA (Mass, Density, Temperature) Yes see BA 063D/06/en Z00571
Integrated bus termination (Terminator) Local operation Adressing 63A 63E 63F 63H 63I 63M Cyclic data to PLC PA profile version Acyclic profile data
Endress+Hauser
155
Promass 83
Promass 83 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 152A 85...260 V AC, 45...65 Hz 20...55 V AC, 45...65 HZ 16...62 V DC 45.45, 93.75, 187.5, 500, 1500, 3000, 6000, 12000 Yes Yes DIP switch, software, local operation see Chapter 5.6 3.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block None Yes see BA 063D/06/en Z00671
Integrated bus termination (Terminator) Local operation Adressing 83A 83E 83F 83H 83I 83M Cyclic data to PLC PA profile version Acyclic profile data
Prosonic DP (FMU 86x)
Prosonic DP (FMU 86x) Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 152E 180253 AC (50/60 Hz); 90132 AC (50/60 Hz); 3855 AC (50/60 Hz); 1928 AC (50/60 Hz); 20...30 VDC 9.6, 45.45, 93.75, 187.5, 500, 1500 Yes Yes DIP switch, software see Chapter 5.6 3.0 Analog Input, Transducer Block Level, Physical Block Relay Yes see BA 100F/00/en Z00743
Supported bus velocities (kBit/s) Integrated bus termination (Terminator) Local operation Adressing FMU86x Cyclic data to PLC PA profile version Acyclic profile data
156
Endress+Hauser
Prosonic Flow 93
Prosonic Flow 93 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Flow 1530 85...260 V AC (50...65 Hz), 20...55 V AC (45...65 Hz), 16...62 V DC 9.6, 19.2, 93.75, 187.5, 500, 1500, 3000, 6000, 12000 Yes Yes DIP switch, software, local operation see Chapter 5.6 3.0 Analog Input, Totalizer Block, Transducer Block Flow, Physical Block None Yes see BA 076D/06/en Z00870
Integrated bus termination (Terminator) Local operation Adressing DDU10 DDU15 DDU18 DDU19 Cyclic data to PLC PA profile version Acyclic profile data
RMx 621
RMx 621 Process variable Display several I/O e.g. Pressure, Temperature, Flow, Steam mass 153F 24V DC +/-10% 9.6, 19.2, 93.75, 187.5, 500, 1500, 3000, 6000, 12000 Yes Yes DIP switch on HMS Anybus module max. 240 bytes Inputs None None Relay, AI, AO, DI, DO No see BA 127R/09/en, BA 144R/09/en No
PROFIBUS ID code (Hex) Auxiliary energy (local) Supported bus velocities (kBit/s)
Integrated bus termination (Terminator) Local operation Adressing RMx621 Cyclic data to PLC PA profile version Acyclic profile data Additional signals Application in hazardous area Ex certificate PNO certificate
Endress+Hauser
157
Smartec S
Smartec S Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Conductivity 153D 100 ... 230 V AC +10/-15 % at 47...64 Hz; 24 V AC/DC +20/-15 % 9.6, 19.2, 45.45, 93.75, 187.5, 500, 1500 No Yes DIP switch, software, local operation see Chapter 5.6 3.0 Analog Input, Transducer Block Analyser, Physical Block None None No Z00956
Supported bus velocities (kBit/s) Integrated bus termination (Terminator) Local operation Adressing CLD132 Cyclic data to PLC PA profile version Acyclic profile data
158
Endress+Hauser
Rackbus Gateway
Rackbus Gateway ZA 375 Process variable PROFIBUS ID code (Hex) Auxiliary energy (local) Supported bus velocities (kBit/s) Several 1501 20...30 VDC 9.6, 19.2, 93.75, 187.5, 500, 1500, 3000, 6000, 12000 Yes No DIP switch max. 38 measured values, every 6 bytes None None None None None Z00247
Integrated bus termination (Terminator) Local operation Adressing ZA375 Cyclic data to PLC PA profile version Acyclic profile data Additional signals Application in hazardous area Ex certificate PNO certificate
Endress+Hauser
159
11.3
Network components
Description DP/PA coupler standard DP-PA coupler EEx (ia) E+H Order No. 17039-1000 017039-0000 52014393 52014394 52014395 52014397 52014396 52005649 FXA720-xxxx
Component Segment coupler SK 1 Segment coupler SK 2
Gateway, 1 PA master Gateway, 2 PA master Gateway, 3-PA master Power link module, standard Power link modul, EEx (ia)
Interfaces converter
PROFIBUS RS485 fibre optic cable Ethernet/PROFIBUS DP gateway FieldGate FXA 720
PROFIBUS PA Fieldbus barrier FieldBarrier Pepperl+Fuchs, Input/Output trunk cable EEx (e), spurs EEx (ia), cable gland M20-M12 connector device, Weidmller, cable length 150 mm M20-M12 connector for device, Weidmller, cable length 300 mm M12 connector for cable mounting, Weidmller M12 socket for cable mounting, Weidmller Bus termination Ex terminator Weidmller Ex terminator Turck Junction boxes T-Box Weidmller, spur M12 socket, trunk M16 cable gland, EEx (ia) 2-way junction box Weidmller, spur M12 socket, trunk M16 cable gland, EEx (ia) 4-way junction box Weidmller, spur M12 socket, trunk M16 cable gland, EEx (ia) T-Box Weidmller, spur M12 socket, trunk M16 cable gland, standard 2-way junction box Weidmller, spur M12 socket, trunk M16 cable gland, standard 4-way junction box Weidmller, spur M12 socket, trunk M16 cable gland, standard T-piece Turck, spur M12 socket, trunk M12 connector and socket, EEx (ia) 2-way junction box, spur M12 socket, trunk M12 connector and socket, EEx (ia) 4-way junction box, spur M12 socket, trunk cable M12 connector and socket, EEx (ia) T-Box Weidmller, spur and trunk M16 cable gland, EEx (ia) 2-way junction box Weidmller, spur and trunk M16 cable gland, EEx (ia) 4-way junction box Weidmller, spur and trunk M16 cable gland, EEx (ia) T-Box Weidmller, spur and trunk M16 cable gland, standard 2-way junction box Weidmller, spur and trunk M16 cable gland, standard 4-way junction box Weidmller, spur and trunk M16 cable gland, standard 52014398
Device connector M12
52006628 52006629 017434-0100 017434-0110 017481-0001 52005549 52014352 52014353
52014354
52014358 52014359
52014360
52001029 52001026
52001027
52014355 52014356 52014357 52014331 52014362 52014363
160
Endress+Hauser
Component Cord set, double sided
Description M12 connector socket Turck, length 1 m, blue M12 connector socket Turck, length 2 m, blue M12 connector socket Turck, length 5 m, blue M12 connector socket Turck, length 10 m, blue M12 connector socket Turck, length 1 m, orange M12 connector socket Turck, length 2 m, orange M12 connector socket Turck, length 5 m, orange M12 connector socket Turck, length 10 m, orange M12 connector socket Weidmller, length 1 m, blue M12 connector socket Weidmller, length 2 m, blue M12 connector socket Weidmller, length 5 m, blue M12 connector socket Weidmller, length 10 m, blue M12 connector socket Weidmller, length 1 m, black M12 connector socket Weidmller, length 2 m, black M12 connector socket Weidmller, length 5 m, black M12 connector socket Weidmller, length 10 m, black
E+H Order No. 52001043 52001044 52001045 52001046 52001025 52001040 52001041 52001042 52014372 52014373 52014374 52014375 52014384 52014385 52014386 52014387 52014364 52014364 52014364 52014364 52014376 52014377 52014378 52014379 52014368 52014369 52014370 52014371 52014380 52014381 52014382 52014383
Cord set, single sided
M12 connector Weidmller, length 1 m, blue M12 connector Weidmller, length 2 m, blue M12 connector Weidmller, length 5 m, blue M12 connector Weidmller, length 10 m, blue M12 connector Weidmller, length 1 m, black M12 connector Weidmller, length 2 m, black M12 connector Weidmller, length 5 m, black M12 connector Weidmller, length 10 m, black M12 socket Weidmller, length 1 m, blue M12 socket Weidmller, length 2 m, blue M12 socket Weidmller, length 5 m, blue M12 socket Weidmller, length 10 m, blue M12 socket Weidmller, length 1 m, black M12 socket Weidmller, length 1 m, black M12 socket Weidmller, length 1 m, black M12 socket Weidmller, length 1 m, black
PROFIBUS DP Connector Bus termination M20-M12 connector for device, Weidmller, cable length 300 mm Ex terminator T-Box Weidmller, Output M12 socket, trunk cable M16 cable gland, external power supply 24 VDC T-Box Weidmller, Output M12 socket, trunk M16 cable gland M12 connector Weidmller, length 0.3 m, violet 52018560 52018563
Junction box Cord set, single sided
52018562 52018561
Endress+Hauser
161
11.4
Asset management and operating software

Description GSD-CD-ROM E+H Order No. 56003894 or download free of charge at www.endress.com FXS113-xxx 56004080 SFE551-xxxx SFE552-xxxx
Component GSD (device data files)
Operating program
Commuwin II FieldCare Lite FieldCare Standard FieldCare Professional
162
Endress+Hauser
11.5
PROFIBUS Standard
Supplementary documentation
1. IEC 61158-2:Ed 3, Digital data communications for measurement and control - Fieldbus for use in industrial control systems - Part 2: Physical layer specification and service definition. 2. IEC 61158-3:Ed 3, Digital data communications for measurement and control - Fieldbus for use in industrial control systems - Part 3: Data Link Service definition 3. IEC 61158-4:Ed 3, Digital data communications for measurement and control - Fieldbus for use in industrial control systems - Part 4: Data Link Protocol specification. 4. IEC 61158-5:Ed 3, Digital data communications for measurement and control - Fieldbus for use in industrial control systems - Part 5: Application Layer Service definition. 5. IEC 61158-6:Ed 3, Digital data communications for measurement and control - Fieldbus for use in industrial control systems - Part 6: Application Layer protocol specification. 6. IEC 61784-1: 2003 CP3/2, Digital data communications for measurement and control Part 1: Profile sets for continuous and discrete manufacturing relative to fieldbus use in industrial control systems
DIN Standard PROFIBUS User Organisation
1. DIN: 19 245, Teil 1 - 4, Beuth Verlag GmbH, Berlin PROFIBUS User-Organisation e.V. Haid- und Neu-Strasse 7 D76131 Karlsruhe Internet: www.profibus.com 1. PNO: PROFIBUS PA Profile for Process Control Devices. Version3.0, October 1999. 2. PNO: PROFIBUS PA User and Installation Guideline, Version 2.2, February 2003 3. PNO: Installation Guideline for PROFIBUS DP/FMS, Version 1.0, September 1998 4. PNO: Technical Overview. April 2002 5. PNO: PROFIBUS Guideline Interconnection technology, Version 1.1, August 6. PNO: PROFIBUS Produkt-Catalogue, Internet: www.profibus.com
Literature
A number of books exist on the use of PROFIBUS issued e.g. by the ISA. It is recommended that an Internet search be made for suitable material.
Endress+Hauser
163
12 Terms and Definitions
12
Terms and Definitions
This chapter contains a selection of terms and definitions to bemet in fieldbus technology. It is subdivided as follows: Bus architecture Components Data exchange Miscellaneous terms
12.1
Topology
Bus architecture
The structure of the communication system, e.g. linear (bus), tree, ring, star. For PROFIBUS, linear and tree structures are permissible. A device that is connected to and recognised by the communication system. Every participant has a unique address: Active communication participant = master a device that has the right to initiate communcation passive communication participant = slave a device that may communicate only when it receives the right to do so from a master The cable and associated hardware that connects the participants together. Among other things, the physical layer defines how a signal is to be transmitted over the bus, how it is to be interpreted and how many participants are allowed on a segment. The following transmission methods are relevant to PROFIBUS applications: RS-485 Standard for transmission on shielded twisted pairs that is used for PROFIBUS-DP. IEC 61158-2 (MBP Manchester Coded Bus Powered) International fieldbus standard with data transmission and power supply on shielded twisted pairs that is used for PROFIBUS-PA. Fibre optics Alternative to STP for PROFIBUS DP applications when operating in environments with heavy electrical interference or when long buses and high transmission rates are required. Can also be used as a basis for redundant structures. In the case of a tree structure, a network section that is separated from the trunk line by a repeater, segment coupler or link.. Trunk cable The longest bus cable, which is terminated at both ends. Spur Line connecting the field device to trunk cable. For PROFIBUS PA, the number and length of the spurs is limited by the physics and application (standard or explosion-hazardous area (spur cable 30 m, Splice 1 m). Table 12-1: Terms and definitions: Bus architecture
Participant
Physical layer
Segment
164
Endress+Hauser
12.2
Components
A PNC is in direct contact with the fieldbus and manages the communication with the field devices (= bus master). It can be either a PLC or an operating programm running on a personal computer. The interface between a PROFIBUS DP system and a PROFIBUS PA segment. The signal coupler converts the signal from RS-485 to IEC 61158-2 format and adapts the transmission rate.. Supplies the devices on the PROFIBUS PA segment with power (except those which are externally powered). Normally the signal coupler and bus power unit are contained in a signal unit, e.g. as the segment coupler. The can also be designed as a PLC interface card. A device that serves as both signal coupler and bus power unit. In these guidelines, a segment coupler is considered to be "transparent", i.e. its existence is not recognised by the communication system. The master communicates directly with the connected devices. The coupler includes a terminator and in the case of Ex-versions, a barrier. PROFIBUS DP/PROFIBUS PA interface for the connection of one or more PROFIBUS segments. A link is not "transparent", i.e. there is no direct communication between the master and the PROFIBUS PA slaves. Their data are collected by the links and made available as a whole to the PROFIBUS DP master. A link is a slave in a PROFIBUS DP system but a master to the connected PROFIBUS PA segments. A repeater amplifies the communication signal, thus allowing the bus length to be extended. Up to 4 repeaters are allowed per bus segment (PROFIBUS PA). A repeater is a bus participant. Actuators and sensors that are connected to a PROFIBUS PA/PROFIBUS DP segment. Field devices are normally slave. Means of connecting individual field devices to the trunk cable. The field devices can be connected directly to the T-box or via a spur. T-boxes are used for distribution only had have no intelligence. Means of connecting several field devices to the trunk cable. Normally, the field devices are connected to the junction box by a spur. Junction boxes are used for distribution only had have no intelligence. Component that terminates the beginning and end of the bus segment, in order to avoid interfering reflections. For PROFIBUS-PA, one terminator is built inot the segment coupler. Various T-boxes have a built-in terminator that can be switched on when the box is at the end of the segment. For explosionhazardous applications a separate bus terminator must be used. Table 12-2: Terms and definitions: Components
Process-near component (PNC)
Signal coupler
Bus power unit
Segment coupler
Link
Repeater
Field devices
(T-Box)
Junction box
Bus termination (Terminator)
Endress+Hauser
165
12.3
Data exchange
The mechanism that is used to ensure proper communication between the participants on the network. A bus access method for communication systems with several masters (multimaster system). During the network design stage, a central list containing every master with its assigned access time is compiled . The master with the token has the right to transmit for this period of time. Afterwards, the token is passed on to the next master in the list. After the list has be worked through, the procedure is started over again. The time required until all the masters in a token ring have been worked through. Normally, the token rotation time also corresponds the update time for the plant data base. A bus access method in which the right to transmit is assigned to one participant only (the master), whereas all the other participants (slaves) can only transmit when requested to do so. A mixture between two bus access methods, e.g. for PROFIBUS-DP the masters are linked together in a logical token right, but communicate directly with their slaves using the master-slave method. The regular exchange of data between a master and its slaves. For measuring instruments, this concerns the measured value and status signals. The irregular exchange of data between a master and a slave. For measuring instruments, this usually concerns the adjustment of process-relevant device parameters during commissioning or operation. Alternatively a detailed error message may be transmitted when a bad status is detected. The time required in cyclic data exchange to collect the complete set of data available on a bus segment. A unique device code used to identify a bus participant, which enables the master to transmit data to a particular slave on the network. The bus address is normally set via DIP switch or software. Table 12-3: Terms and definitions: Data exchange
Bus access method
Logical token ring
Token rotation time
Master-slave method
Hybrid method
Cyclic data transfer (polling)
Acyclic data transfer
Update time
Bus address
166
Endress+Hauser
12.4
Miscellaneous terms
Basis for the use of PROFIBUS-PA devices in explosion-hazardous areas. Measures aimed at preventing an impermissible current consumption in the event of a fault, so that a defective bus participant cannot detrimentally affect the function of the rest of the system. The increase in the current consumption with respect to the basic current in the event of a fault. Device descriptions and bitmaps required be the master, in order that a device is recognised as a bus participant. The device database files are required during the commissioning of the communication system. Table 12-4: Terms and definitions: Miscellaneous terms
FISCO model Fault disconnection electronics (FDE)
Fault current
Device database file (GSD)
Endress+Hauser
167
13 Appendix: Calculation Sheets
13
Requirements
Appendix: Calculation Sheets
The following data are required to design a PROFIBUS-PA segment: Max. output current of the segment coupler Is Output voltage of the segment coupler Us Specific resistance of the cable RK ( Total length of the spurs ( Length of the trunk cable ( Basic and fault currents of the field devices used (for Endress+Hauser devices see Section 4.3) (mA) (V) /km) m) m)
13.1
Current consumption
No 1 2 3 4 5 6 7 8 9 10 Device
Explosion hazardous areas EEx ia

Manufacturer Tag Basic current IB Fault current IFDE
Highest fault current (max. IFDE)
Current consumption ISEG = IB + max. IFDE Output current of segment coupler IS IS IB + max. IFDE? Yes=OK 40 /km m
Cable length
Max. loop-resistance, standard Specific resistance of cable RK Max. length (m) = 1000 x (40 / Specific resistance of cable)
Length of trunk cable Total length of spurs Total length of cable LSEG
m m m
Total length of cable < Max. length
OK!
168
Endress+Hauser
Output voltage of segment coupler US (Manufacturer's data) Specific resistance of cable RK Total length of cable LSEG Resistance of cable RSEG = LSEG x RK Current consumption of segment ISEG Voltage drop UA = ISEG x RSEG Voltage at last device UB = US UA /km
V V
9* V?
OK!
for FEB 24P 9.6 V
Endress+Hauser
169
13.2
Current consumption
No 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Explosion hazardous areas EEx ib

Device
Current consumption ISEG = IB + max. IFDE Output current of segment coupler IS IS IB + max. IFDE? Yes=OK
Cable length
16 /km m
m m m
OK!
170
Endress+Hauser
V V
9* V?
OK!
for FEB 24P 9.6 V
Endress+Hauser
171
13.3
Current consumption
No 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
Non-hazardous areas
Device
Current consumption ISEG = IB + max. IFDE Output current of segment coupler IS IS IB + max. IFDE? Yes=OK
172
Endress+Hauser
Cable length
39 /km m
m m m
OK!
V V
9* V?
OK!
for FEB 24P 9.6 V
Endress+Hauser
173
174
Endress+Hauser
Index
A
Adressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Application profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 ASP 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Liquiphant M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Liquisys M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
M
Master class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 MBP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Memo-Graph DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Micropilot M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Multicap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 must . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Mycom S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Mypro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
C
Calculation Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Cerabar M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Cerabar S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Communication DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Commuwin II . . . . . . . . . . . . . . . . . . . . . . . . 84, 120, 124 Bus parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Device parametrization . . . . . . . . . . . . . . . . . . . . . . . 120 Component-based Automation . . . . . . . . . . . . . . . . . . . . . 10 Cycle time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Cyclic data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
N
Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
O
Output data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
D
Deltabar S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Deltapilot S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Device current consumption . . . . . . . . . . . . . . . . . . . . . . . 52 Device database files (GSD) . . . . . . . . . . . . . . . . . . . 87, 89 Device DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Device operating manuals . . . . . . . . . . . . . . . . . . . . . . . . . 80 Device parametrization . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Display value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
P
PROFIBUS Analysis blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Block functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Block structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Device management . . . . . . . . . . . . . . . . . . . . . . . . . 109 Netzwerkkomponenten . . . . . . . . . . . . . . . . . . . . . . . 160 Operating tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Standardparameter . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Supplementary documentation . . . . . . . . . . . . . . . . . 163 Technologien . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Transmitter and actuator blocks . . . . . . . . . . . . . . . . . 110 PROFIBUS DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8, 14 Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Bus access method . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Field devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Hazardous areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Network configuration . . . . . . . . . . . . . . . . . . . . . . . . 35 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 PROFIBUS PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Block model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Bus access method . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Bus parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Cable manufacturers . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Cable type and length . . . . . . . . . . . . . . . . . . . . . . . . . 51 Cable types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Current consumption . . . . . . . . . . . . . . . . . . . . . . . . . 52 Datenmenge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Device installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Erdung und Schirmung . . . . . . . . . . . . . . . . . . . . . . . . 75 Field devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Fieldbus barriers . . . . . . . . . . . . . . . . . . . . . . . . . 49, 63 175
E
EDD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Electrical symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Explosion protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
F
FDT Joint Interest Group . . . . . . . . . . . . . . . . . . . . . . . . . . 28 FDT Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 FDT Joint Interest Group . . . . . . . . . . . . . . . . . . . . . . . . . 28 FDT/DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 FieldCare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83, 116 Bus parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Device parametrization . . . . . . . . . . . . . . . . . . . . . . . 117 FISCO Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
G
GSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 GSD configuration . . . . . . . . . . . . . . . . . . . 89, 90, 92, 93
I
I/O integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 IEC-61158-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Integration technologies . . . . . . . . . . . . . . . . . . . . . . . . . . 21
L
Levelflex M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39, 40, 46, 73 Liqisys M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Endress+Hauser
FISCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 FISCO-Modell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Hazardous areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Network configuration . . . . . . . . . . . . . . . . . . . . . . . . 47 Operating principle . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Overvoltage protection . . . . . . . . . . . . . . . . . . . . . . . . 79 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Segment design examples . . . . . . . . . . . . . . . . . . . . . . 56 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 bersicht . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Voltage at last devicet . . . . . . . . . . . . . . . . . . . . . . . . 54 PROFIBUS PA profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 PROFIBUS User Organisations . . . . . . . . . . . . . . . . . . . . . . 8 PROFIdrive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Profile GSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 PROFINET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8, 9 PROFIsafe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Promag 33/35 . . . . . . . . . . . . . . . . . . . . . . . . . . . 138, 154 Promag 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Promag 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140, 155 Promass 63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141, 155 Promass 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Promass 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143, 156 Prosonic DP (FMU 86x) . . . . . . . . . . . . . . . . . . . . . . . . 156 Prosonic Flow 90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Prosonic Flow 93 . . . . . . . . . . . . . . . . . . . . . . . . . 145, 157 Prosonic M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Prosonic T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Prowirl 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Prowirl 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
R
Rackbus Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 RID 261 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 RMx 621 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 RS-485 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 RS-485 IS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
S
Safety conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Segment coupler . . . . . . . . . . . . . . 39, 40, 44, 50, 69, 70 Segment coupler SK2 . . . . . . . . . . . . . . . . . . . . . . . . . 45, 71 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Sicherheitshinweise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Slave-to-Slave Communication . . . . . . . . . . . . . . . . . . . . . 18 Smartec S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151, 158 Status codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95, 96, 97 Statuscode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Strungsbehebung Datenbertragung . . . . . . . . . . . . . . . . . . . . . . . . . . 123 System integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 System intergration Tested systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
T
Technical Data PROFIBUS DP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Terma and definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 164 TMT 184 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Transmission standards . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Trouble-shooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
V
Version DP-V0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Version DP-V1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Version DP-V2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Q
Quality assurance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
176
Endress+Hauser
www.endress.com/worldwide

Endress+Hauser Profibus Planing Guide

Uploaded by

Copyright:

Available Formats

Endress+Hauser Profibus Planing Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Endress+Hauser Profibus Planing Guide

Uploaded by

Copyright:

Available Formats

What are PROFIBUS DP and PA?

What are PROFIBUS DP and PA?

What are the main components and topologies of PROFIBUS DP and PA networks?

What are the main components and topologies of PROFIBUS DP and PA networks?

Guidelines for planning and commissioning

BA 034S/04/en/06.04 Nr. 56004242

PROFIBUS planning and commissioning

4.5 4.6 4.7

PROFIBUS planning and commissioning

Device Parametrization . . . . . . . . . . . . 104

Technical Data . . . . . . . . . . . . . . . . . . . . 125

PROFIBUS Components . . . . . . . . . . . 127

Terms and Definitions . . . . . . . . . . . . . 164

Appendix: Calculation Sheets . . . . . . 168

PROFIBUS planning and commissioning

PROFIBUS planning and commissioning

PROFIBUS planning and commissioning

Installation, commissioning, operation

Explosion hazardous area

PROFIBUS planning and commissioning

Conventions and icons

PROFIBUS planning and commissioning

The guidelines are structured as follows:

PROFIBUS DP Basics PROFIBUS PA Basics

System Integration Device Configuration

Technical Data PROFIBUS Components

Terms and Definitions Appendix

PROFIBUS planning and commissioning

ES Internet OPERATIONS: PROFINET

MBP (IEC 61158-2)

HART, ASi FACTORY: PROFIBUS DP PROCESS: PROFIBUS DP

Fig. 2-1: Overview of PROFIBUS technologies

PROFIBUS User Organisations

PROFIBUS planning and commissioning

Controller and HMI

100ms TCP/IP Real Time

<1ms Isochronic Real Time Real Time

PROFIBUS planning and commissioning

Horizontal integration along the production line

Data exchange between intelligent devices within the machine

Machine 2 Engineering ES Close

PROXY PROFIBUS DP/PA Production Mash Filter Ferment

PROXY PROFIBUS DP Machine 1 Wash Fill

PROFIBUS planning and commissioning

Component Editor Interface

Component Editor Interface

Production Mash Filter Ferment

Machine 1 Wash Fill

PROFIBUS planning and commissioning

I/O Supervisor e.g. SCADA or Configuration Diagnosis Up/Download

I/O Controller e.g. PLC

Configuration Production Data Alarms

Diagnostic Status control Parametrization

I/O Device Field Device

Fig. 2-7: Data exchange between PROFINET I/O devices

PROFIBUS applications Standard data UDP Real-time data

Real Time Switch ASIC

Fig. 2-8: PROFIBUS communication stack

PROFIBUS planning and commissioning

PROFIBUS planning and commissioning