Ovation Profibus

Profibus User Guide for Ovation 3.
5
OW350_36
Version 1
February 2013
Copyright Notice
Since the equipment explained in this document has a variety of uses, the user and those
responsible for applying this equipment must satisfy themselves as to the acceptability of each
application and use of the equipment. Under no circumstances will Emerson Process
Management be responsible or liable for any damage, including indirect or consequential losses
resulting from the use, misuse, or application of this equipment.
The text, illustrations, charts, and examples included in this manual are intended solely to explain
TM
the use and application of the Ovation Unit. Due to the many variables associated with specific
uses or applications, Emerson Process Management cannot assume responsibility or liability for
actual use based upon the data provided in this manual.
No patent liability is assumed by Emerson Process Management with respect to the use of
circuits, information, equipment, or software described in this manual.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, including electronic, mechanical, photocopying, recording or otherwise
without the prior express written permission of Emerson Process Management.
The document is the property of and contains Proprietary Information owned by Emerson Process
Management and/or its subcontractors and suppliers. It is transmitted in confidence and trust, and
the user agrees to treat this document in strict accordance with the terms and conditions of the
agreement under which it was provided.
This manual is printed in the USA and is subject to change without notice.
Ovation is the mark of Emerson Process Management. Other marks are the property of their
respective holders.
Copyright © Emerson Process Management Power & Water Solutions, Inc. All rights reserved.
Emerson Process Management
Power & Water Solutions
200 Beta Drive
Pittsburgh, PA 15238
USA
E-Mail: Technical.Communications@Emerson.com
Web site: https://www.ovationusers.com
Contents
1 Introduction to Ovation Profibus 1

1.1 What is Profibus DP? .......................................................................................................... 1
1.2 What is device interoperability? .......................................................................................... 2
1.3 What are the Profibus and Ovation components? .............................................................. 3
1.4 What are Profibus devices? ................................................................................................ 4
1.5 What are device database (GSD) files? .............................................................................. 5
1.6 What is Profibus redundancy? ............................................................................................ 6
1.7 What is Profibus Port redundancy? .................................................................................... 8
2 Profibus hardware 9
2.1 What is a Profibus DP module? .......................................................................................... 9
2.1.1 Terminal block pin assignments - Profibus (DP) .................................................... 9
2.1.2 Logic card diagnostic LEDs - Profibus (DP) ......................................................... 10
2.1.3 Field card diagnostic LEDs - Profibus (DP) ......................................................... 11
2.1.4 Specifications - Profibus (DP) .............................................................................. 11
2.2 What are Profibus hardware and software requirements? ............................................... 12
3 Configuring Profibus 13
3.1 Configuring Profibus devices for standard (simplex) configurations ................................. 13
3.1.1 To create a control task ........................................................................................ 14
3.1.2 To enable multiple control tasks .......................................................................... 16
3.1.3 To add a new I/O device number to the Controller using the
Developer Studio .................................................................................................. 16
3.1.4 To insert a Profibus I/O module in the Developer Studio ..................................... 18
3.1.5 To add a module record point name .................................................................... 21
3.1.6 To configure Profibus Port Redundancy .............................................................. 23
3.1.7 To create a node record ....................................................................................... 25
3.1.8 To assign a node record to each of your ports .................................................... 27
3.1.9 To add a redundant module (optional) ................................................................. 28
3.1.10 To set a module's mode as simplex (optional-- the default is simplex) ............... 28
3.1.11 To access the Profibus module engineering window ........................................... 29
3.1.12 To access the Profibus module configuration window ......................................... 30
3.1.13 To add new slave devices to your device catalog ............................................... 31
3.1.14 To add Profibus slaves ......................................................................................... 31
3.1.15 To configure Profibus slaves ................................................................................ 32
3.1.16 To edit a slave's station ID (optional) ................................................................... 33
3.1.17 To use the Process Data window (optional) ........................................................ 34
3.1.18 To configure bus parameter settings (optional) ................................................... 35
3.1.19 To view the Address Table (optional) .................................................................. 36
3.1.20 To configure points for each Profibus signal ........................................................ 37
3.1.21 To download the Controller .................................................................................. 39
3.1.22 To clear the Controller .......................................................................................... 40
3.1.23 To load the Controller ........................................................................................... 41
OW350_36 i
Table of Contents
3.2 Configuring Profibus devices for redundant modules configurations................................ 42

3.2.1 To create a control task ........................................................................................ 43
3.2.2 To enable multiple control tasks .......................................................................... 44
3.2.3 To add a new I/O device number to the Controller using the
3.2.4 To insert a Profibus I/O module for module redundancy in the
3.2.5 To add a module record point name .................................................................... 48
3.2.6 To configure Profibus Port Redundancy .............................................................. 50
3.2.7 To create a node record ....................................................................................... 52
3.2.8 To assign a node record to each of your ports .................................................... 54
3.2.9 To add a redundant module (optional) ................................................................. 55
3.2.10 To set a module's mode as redundant ................................................................. 55
3.2.11 To access the Profibus module engineering window ........................................... 56
3.2.12 To access the Profibus module configuration window ......................................... 57
3.2.13 To design a redundant module segment (optional) ............................................. 58
3.2.14 To add new slave devices to your device catalog ............................................... 58
3.2.15 To add Profibus slaves ......................................................................................... 59
3.2.16 To configure Profibus slaves ................................................................................ 60
3.2.17 To edit a slave's station ID (optional) ................................................................... 61
3.2.18 To use the Process Data window (optional) ........................................................ 62
3.2.19 To configure bus parameter settings (optional) ................................................... 63
3.2.20 To view the Address Table (optional) .................................................................. 65
3.2.21 To configure points for each Profibus signal ........................................................ 66
3.2.22 To download the Controller .................................................................................. 68
3.2.23 To clear the Controller .......................................................................................... 68
3.2.24 To load the Controller ........................................................................................... 70
4 Profibus on-line diagnostics 71

4.1 What are Profibus online diagnostics? .............................................................................. 71
4.1.1 To access Profibus online diagnostics ................................................................. 71
4.1.2 To use Profibus on-line diagnostics to configure a driver .................................... 74
4.2 Network scan option .......................................................................................................... 76
4.2.1 Preparing to perform network scan ...................................................................... 76
4.2.2 Requirements for a successful network scan ...................................................... 76
4.2.3 Network scan ....................................................................................................... 77
4.2.4 Topology scan ...................................................................................................... 77
4.2.5 Module scan ......................................................................................................... 78
5 Module firmware 79
5.1 What is module firmware? ................................................................................................. 79
5.1.1 To download module firmware ............................................................................. 79
ii OW350_36
Table of Contents
6 Troubleshooting Profibus 85
6.1 How do I troubleshoot Profibus? ....................................................................................... 85
6.1.1 To troubleshoot using the module and node records .......................................... 86
6.1.2 Module record information ................................................................................... 86
6.1.3 Simplex module information ................................................................................. 88
6.1.4 Redundant module information ............................................................................ 89
6.1.5 Node record information....................................................................................... 90
6.2 What is the best way to troubleshoot redundant module pairs? ....................................... 93
6.3 Troubleshooting the bus using the LEDs .......................................................................... 94
6.4 Resolving a slave alarm .................................................................................................... 94
6.5 Investigating a Profibus fault code .................................................................................... 95
7 Bus Diagnostic Diagrams 97

7.1 What are Ovation Bus Diagnostics? ................................................................................. 97
7.2 What is the Ovation Bus Diagnostics Generation tool? .................................................... 97
7.2.1 To access the Ovation Bus Diagnostics Generation program ............................. 98
7.2.2 To create diagrams using the Ovation Bus Diagnostics Generation program ..... 99
7.2.3 What are the Ovation Bus Diagnostics Generator window fields? .................... 101
7.2.4 To Generate the Graphic files ............................................................................ 103
7.2.5 To import the graphics into the Developer Studio .............................................. 105
7.2.6 To access the Bus Diagnostics Graphics from Ovation ..................................... 106
7.3 What is the Device Status Display? ................................................................................ 106
7.3.1 Drop Interface window ....................................................................................... 107
7.3.2 Foundation Fieldbus Main window ..................................................................... 109
7.3.3 To access the Foundation Fieldbus window ...................................................... 110
7.3.4 Profibus Main window ........................................................................................ 111
7.3.5 DeviceNet Main window ..................................................................................... 114
7.3.6 To access the DeviceNet window ...................................................................... 116
A Appendix: Ovation Native Profibus Port Redundancy 117

A.1 Port Redundancy General Guidelines ............................................................................ 117
A.1.1 Basic Operation .................................................................................................. 117
A.1.2 Restrictions......................................................................................................... 119
A.1.3 Implementation Guidelines................................................................................. 119
Index 121
OW350_36 iii
S E C T I O N 1
1 Introduction to Ovation Profibus
IN THIS SECTION
What is Profibus DP? .......................................................................................................... 1

What is device interoperability? .......................................................................................... 2
What are the Profibus and Ovation components? .............................................................. 3
What are Profibus devices? ................................................................................................ 4
What are device database (GSD) files? .............................................................................. 5
What is Profibus redundancy? ............................................................................................ 6
What is Profibus Port redundancy?..................................................................................... 8
1.1 What is Profibus DP?
Profibus (Process Field Bus) DP (decentralized periphery) is an all-digital, two-way

communication system that links devices (also known as slaves) and automation systems. A
decentralized periphery uses a network bus (in this instance, Profibus) between the Controller
(Ovation) and its connected I/O channels. Therefore, the I/O is decentralized as compared to a
programmable logic controller (PLC) that has its I/O arranged centrally. At the base level in the
hierarchy of plant networks, Profibus serves as a Local Area Network (LAN) for instruments.
Profibus DP offers reduced installation and material cost by replacing the traditional one-to-one
wiring scheme with a networking or multi-drop configuration. Conventional analog and discrete
field instruments use point-to-point wiring (one wire pair per device). If your plant has 1000 field
devices, you would need 1000 wire pairs. In addition, conventional instruments are limited to
carrying only one piece of information over a wire pair (usually a process variable or control
output).
Profibus DP technology does not have these limitations. Each Ovation Profibus DP network
supports up to 125 devices (for redundant Ovation module operation only 124 devices are
allowed per network).
Notes:
 For all process applications including Ovation, considerations such as power, process
modularity, and data update rate must be considered.
 For example, a single Profibus network with the maximum number of slave devices on a
single pair of wires might provide a quantity of I/O that exceeds the automation system's
capability. Therefore, process segmentation is a recommended practice.
Profibus DP is one of a family of protocols that was developed in Germany by a group of many
companies and universities. The technology is controlled by the Profibus User Organization,
consisting of approximately 1,000 member companies in 23 regional user organizations united
under the umbrella organization, Profibus International. The objective of Profibus International is
to develop a single, open, interoperable, international fieldbus. This objective gives users the
option of choosing from a wide range of “fieldbus-compatible” equipment from a large selection of
vendors.
OW350_36 1
1.2 What is device interoperability?
The Ovation implementation of Profibus DP uses hardware and software components to integrate
Profibus devices with Ovation technology through a Profibus I/O module that resides in a
Controller cabinet. Each Profibus I/O module provides two ports (where each port acts as an
independent Profibus DP network). Ovation can support redundant Profibus masters on two
different Profibus segments and eliminates the need for an Ethernet switch and a gateway
module.
Notes:
 Each port of the Ovation Profibus DP module is considered a Profibus DP network. Profibus
masters and slaves can occupy addresses 0 to 125 (for redundant applications, addresses
0 and 1 are reserved for the masters leaving 2-125 available for devices).
 Due to Profibus physical layer restrictions, the Profibus network may need to be broken
down into segments connected by repeaters or couplers. Typically, 32 devices can be
supported on a single segment. Refer to www.profibus.com for detailed Profibus installation
information and to determine the proper network segmentation and layout.
The Emerson Profibus interface I/O is capable of being scanned by the control schemes at
different configurable scan rates. The scan rate is based on which of the five control tasks that the
Profibus interface I/O is assigned to in the Ovation Controller. (Refer to: To enable multiple control
tasks (see page 15) for details.)
For more information on Profibus, visit the Profibus User Organization web site at
http://www.profibus.com.
Note: Refer to the individual Profibus device vendor manuals and Profibus standards
documents for specific details of device and network capabilities.
1.2 What is device interoperability?
Interoperability between field devices means that field devices from different manufacturers can
work together, sending and receiving information related to their specific function in the process.
The Profibus User Organization establishes guidelines for interoperability between field devices
on a Profibus segment. These guidelines address such aspects as physical characteristics,
communication, and software functionality.
Manufacturers can apply for a Profibus-approved certificate from the Profibus Trade Organization.
Interoperability for a device is guaranteed after the device has successfully passed all of the tests.
Devices can be certified as either slaves or masters and can use various protocols with the
Profibus standard.
A number of Profibus variants exist including DP-V0, DP-V1, and DP-V2. All devices support, at a
minimum, DP-V0, which provides the guaranteed cyclic transmission of device data. DP-V1 is
also supported for a configuration master where a second connection to Profibus can be used for
configuration software support.
Profibus PA is supported by means of its connection capability to DP-V0. However, the capability
is handled by Ovation through PlantWeb capabilities of Foundation Fieldbus. The Profibus family
of protocols is extensive as is the knowledge needed to understand them. The level of knowledge
for Profibus PA is outside the scope of this manual.
2 OW350_36
1.3 What are the Profibus and Ovation components?
1.3 What are the Profibus and Ovation components?
Unlike conventional analog installations that have a dedicated pair of wires connecting each field
device to a host system, Profibus DP installations use a single twisted-pair cable (also called a
bus or a trunk) to connect to multiple devices. The cable, connected devices, and supporting
components are called a segment. The segment can be designed as either a branch or tree
layout topology. The following figure depicts a typical implementation of Profibus with an Ovation
system.
Figure 1: Implementation of Profibus with Ovation
OW350_36 3
1.4 What are Profibus devices?
In computer networking, master/slave is a communication model where one device or process

(known as the master) controls one or more other devices or processes (known as slaves). The
master makes a service request and the slave fulfills the request. The master/slave model
provides a convenient way to interconnect programs that are distributed efficiently across different
locations.
After the master/slave relationship is established, the direction of local control commands is
always from the master to the slave(s). In the Ovation-Profibus implementation, the Profibus I/O
module is the master and the Profibus devices are the slaves. There are various slave devices
on each segment that collect input information and send output information to the master. The
slave devices are linked to the Ovation Controllers through a Profibus I/O module.
The Profibus I/O module resides in the Controller cabinet. An I/O data agent within the Controller
works with the server to exchange information and diagnostics between the Profibus I/O module
and the Operator Station. The I/O data agent scans I/O at a fixed 1 second rate. The Operator
Station, Controller, and I/O module each run a version of the server in order to facilitate
configuration and diagnostics of Profibus slave devices.
1.4 What are Profibus devices?
Profibus devices are field instruments that can range from simple I/O devices such as push
buttons and lights to sophisticated devices like motor starters. These slave devices collect input
information and send output information to the master. Profibus devices use a digital, rather than
analog, connection to the Ovation system. Profibus devices notify the control system of standard
operating parameters, are self-diagnosing, and are capable of reporting device problems to the
control system.
Each Profibus device must have a unique physical device tag and a corresponding network
address. The network address is the current address that Profibus is using for the device.
Each Profibus device has its own configuration file known as the GSD file. This file is provided by
the device vendor, contains the system characteristics of the device, and is stored in the Ovation
database.
There are three types of Profibus DP devices:

 Master Class 1 (DPM1) [Address 1] — DP-V0
Master Class 1 devices perform cyclical user data and provide application data. Class 1
Masters can configure device parameters via the GSD file.
 Master Class 2 (DPM2) — DP-V1
Master Class 2 devices communicate with the Class 1 devices and all of the slaves. Class 2
Masters read all diagnostic information from the slaves devices.
 Slave [Address 2-125] — DP-V0 and/or DP-V1
Slaves are peripheral devices (for example VSDs, I/O, motor starters, and so forth) that can
import and export data.
4 OW350_36
1.5 What are device database (GSD) files?
Profibus supports both mono-master and multi-master systems. In a mono-master system, there
is only one master device active on the bus. Class 1 Master devices are normally PLCs that
cyclically exchange data with the connected slave devices and act as a main controller for
handling exchange of I/O information. This setup has the shortest bus cycle times. Because
Profibus uses a cyclical polling setup between masters and slaves, the behavior is deterministic,
meaning that the behavior of a Profibus system can be predicted over time.
In a multi-master system, there are several master devices on a single bus. Each of the masters
can read the input and output messages of each slave. Only one master (DP-V0) has write
access to the outputs. A Class 1 master automatically detects the presence of a new segment
connected to a Class 2 master. When the Class 1 master completes its polling cycle, it passes a
"token" to the Class 2 master to grant temporary access to the bus. Each master can only poll the
connected slave devices when it possesses the token.
A slave can only have a single master, so a multi-master system can be two DPM1 masters each
talking to a separate set of Profibus slaves. In effect, you can have two completely separate
Profibus segments sharing common wiring communications. DPM1 and DPM2 masters can be on
the same segment but only the DPM1 master has write access to the slaves. The DPM2 master
can read all diagnostic information from the slave devices only.
1.5 What are device database (GSD) files?
Each Profibus device has its own GSD configuration file. The GSD file contains the system
characteristics of each device and is supplied by the device vendor. There are three parts to the
GSD file:
 General specifications — Information on vendor, device name, hardware and software
release states, supported baud rates, monitoring time intervals, signal assignment on the bus,
and other device-specific information.
 DP master related specifications — Only used for master devices.
 DP slave related specifications — Number and type of I/O channels, diagnostic test
specifications, and information on available modules for the slave device.
The information in the GSD file is used directly by the Ovation Engineering tools. The Ovation
system uses the information in the GSD file to establish communication with the slave device.
After configuration, the GSD information is loaded into the Profibus I/O module's EC-1 chip and
stored in the Ovation database.
In some cases, specific language GSD files are available from the device vendors. Examples are:
GSE for English, GSF for French, and GSI for Italian.
Note: “GSD” is the general name for these types of files as well as for the German version of
the file.
OW350_36 5
1.6 What is Profibus redundancy?
1.6 What is Profibus redundanc y?
Profibus redundancy is available for Ovation 3.1.1 and later releases.
Emerson has developed technology to give you the option of using redundant Ovation Profibus
modules, to protect your Profibus system in the event that a module or segment (EC-1 chip) fails.
Failovers between the redundant modules can occur for any of the following reasons:
 No communication to all devices on either segment of a module.
 No communication/faulty communication between the module and the Controller.
 Additional module faults (such as internal hardware or software faults associated with a
module).
Redundant Profibus modules are connected to the Ovation Controllers, and each other, via the
Ovation bus. There can only be one master at a time on the Profibus network (some Profibus
implementations allow more than one master - this is not supported in the Ovation Profibus
network). The module acting as the Profibus master is referred to as being in control. The module
operating as a slave on the Profibus network is considered to be in backup. The module in control
actively exchanges I/O between the Ovation Controller and the Profibus devices. The backup
module does not exchange any I/O and passively waits to take control. Before a backup module
goes into control, it is updated with all Profibus outputs assigned to devices on its Profibus
segments.
The Ovation Controller evaluates the health of each Profibus module and segment. Initially, the
Ovation Controller attempts to make the primary module take control. In the case of a failure on
the control module, if there is a healthy backup, the Ovation Controller will initiate a failover to
make the backup module take control. This ensures that no process data is lost in the case of a
failure on the module in control. The Ovation Controller will only perform a failover if there is a
healthy backup available to take control (control will not be switched to a less healthy module).
The individual modules in a redundant Profibus module pair are designated primary and
secondary. The primary module is located on an odd numbered Ovation branch. The secondary
module is located on the next highest branch number (for example, if a primary module is located
on odd-numbered branch n, the secondary module is located on branch n + 1).
6 OW350_36
1.6 What is Profibus redundancy?
Figure 2: Redundancy diagram
OW350_36 7
1.7 What is Profibus Port redundancy?
The module and node records for the redundant Profibus modules and segments contain
information useful in troubleshooting the redundant Profibus modules. The module record
contains information about the operating mode of each segment (control, backup, or off),
communication status of each segment, and general module health status. The node records
contain the segment number, module status, and communication status.
Note: The Ovation Profibus system provides module redundancy only. Due to the nature of the
Profibus cabling requirements, data loss due to disconnected or broken cables is not supported.
The Ovation Profibus system provides module redundancy only (for example, this redundancy
guards against data loss due to a module failure). Due to the nature of the Profibus cabling
requirements, cable redundancy is not explicitly supported (which means that data loss could
possibly occur). Some devices support redundant cabling. Refer to the individual device's manual
for details.
A failover can only occur if there is a healthy module in backup. Once a module loses control
because of a failover, a module enters a failed state. The Port node records contain information
on that failed state. The module needs to be rebooted to remove it from a failed state. This will
clear the error in the Port node record. You should physically check the LEDs on the module,
cabling, and devices to help ensure that the error has truly been cleared. After rebooting, the
module should boot up in backup.
1.7 What is Profibus Port redundanc y?

Profibus System Redundancy (SR) pairs two Profibus ports together for redundant operation.
This form of SR provides an additional layer of redundancy by protecting against single physical
media, Profibus slave device channel, Ovation Profibus port, or Ovation Profibus module failures.
SR redundancy is evaluated per slave device and not per overall channel. In this redundancy,
there is no concept of a failover; both channels of every device are active and the Ovation Native
Profibus driver in the Ovation Controller reads inputs from every device, evaluates device status,
and determines which channel’s data to write to the system. For more information refer to:
Appendix: Ovation Native Profibus Port Redundancy (see page 117).
Note: Profibus Port redundancy is available for Ovation 3.3.1 and later releases.
8 OW350_36
S E C T I O N 2
2 Profibus hardware
IN THIS SECTION
What is a Profibus DP module? .......................................................................................... 9

What are Profibus hardware and software requirements? ............................................... 12
2.1 What is a Profibus DP modul e?
Profibus DP is an all-digital, two-way communication system that links devices and automation
systems.
A decentralized periphery uses a network bus, (in this instance Profibus), between the Controller
(Ovation) and its connected I/O channels. Therefore, the I/O is decentralized as compared to a
programmable logic controller (PLC) that has its I/O arranged centrally.
At the base level in the hierarchy of plant networks, Profibus serves as a Local Area Network
(LAN) for instruments.
2.1.1 Terminal block pin assignments - Profibus (DP)
The Profibus DP module base unit has a 53-position compression-style terminal block arranged in
three (3) rows. The "A" row, highest relative to the base, has 18 positions. The middle, or "B" row
has 17 positions. The "C" row, nearest to the base, has 18 positions.
Note: For the Standard I/O Marshalling Base Unit, field terminations are located on the half
shells and connected to the base. See Marshaling Base Unit for more information.
 Maximum working voltage is 150 V peak DC or RMS AC.

 Current rating is 5 amps.
 Maximum wire size is 12 AWG single wire or two 14 AWG wires/terminal.
OW350_36 9
2.1 What is a Profibus DP module?
The base unit termination block assignments are show in the following table.
ROW C SIGNAL NAME ROW B PIN SIGNAL NAME ROW A SIGNAL

PIN NO. NO. PIN NO. NAME
1-3 RSV 1-3 RSV 1-3 RSV

4 CROSS CONNECT TX 4 CROSS CONNECT 4 RSV
RX
5 RSV 5 CROSS CONNECT 5 RSV
GND
6 - 16 RSV 6 - 16 RSV 6 - 16 RSV
17 EARTH GROUND 17 PS+ 17 PS+
18 EARTH GROUND 18 PS-
Note: PS+ and PS- are not used. The cross connect redundancy signals are the same that are
accessed with the RS232 redundancy connector on the PMOD. No connections are permitted to
terminals marked RSV.
Note: Connection to the Profibus is made through a 9 pin female "D subminiature" connector
on the PMOD. There is one connector for each channel.
2.1.2 Logic card diagnostic LEDs - Profibus (DP)
LED DESCRIPTION
P (green) Power OK LED. Lit when the logic board's +5V and +3.3V digital supply voltage
level is OK.
C (green) Communication OK LED. Lit when the Ovation Controller is communicating with the
module.
E No LED.
I (red) Internal Fault LED. Lit when the forced error bit (bit 1) of the configuration register
is set, or when the Ovation Controller is not communicating with the module.
1-5 No LED.
6 ACT (green) Ethernet activity.
7 FDX (yellow) Full duplex Ethernet communication.
8-12 S4 - S0 (red) General purpose red LEDs. Lit under firmware control of the ARM9 processor.
13 - 16 No LED.
10 OW350_36
2.1 What is a Profibus DP module?
2.1.3 Field card diagnostic LEDs - Profibus (DP)
Field card LED indications Channels 1 and 2
LED LED STATE ME ANING
RDY (yellow) ON Device is ready.

5 Hz Flashing Firmware Download in progress.
1Hz Flashing Device in Bootloader mode and is awaiting firmware download.
Non-Cyclic Flashing Hardware or runtime error.
OFF Device has no power or hardware defect.
RUN (green) ON Communication is established with at least one field device.
5 Hz Flashing If ERR LED is OFF then Device communication is stopped, If
ERR LED is ON then NO slave has been found
Non-Cyclic Flashing At power up it indicates configuration missing, at runtime it
indicates watchdog timeout.
OFF No Communication.
ERR (red) ON Device has communication problem or has detected a short
circuit.
OFF No Error.
STATUS ON Device is holding the Profibus token.
COMBINED
(yellow) Non-Cyclic Flashing The device is sharing the Profibus token with another master on
the Profibus network.
OFF Device is not configured or has not received a token.
2.1.4 Specifications - Profibus (DP)
DESCRIPTION VALUE
Voltage Main Primary Voltage 21.0V Min. 24.0V Nominal 25.0V Max.
Main Secondary Voltage 21.0V Min. 24.0V Nominal 25.0V Max.
Ovation I/O Bus Current (+24V Main) 160 mA typ.*, 214 mA Max.
Ovation I/O Bus Power (+24V Main) 3.84 W typ.*, 5.136 W Max.
Input Under-voltage Lockout 17-18.5 volts
Input Over-voltage Crowbar 29-35 volts
Number of segments per module 2
Interface characteristics RS485, 12 Mbaud Max
Ethernet 10/100 MBaud, Auto-negotiation supported
MDIX not supported, Standard RJ45 connection on the EMOD
Access only with cap removed
Redundancy Port RS232, 57.6 Kbaud Max, RJ45 jack on the PMOD.
ARM9 Diagnostic Port RS232, 57.6 Kbaud Max, 5 pin header on the logic card.
Access only with cap removed.
OW350_36 11
2.2 What are Profibus hardware and software requirements?
DESCRIPTION VALUE
Dielectric Isolation +/- 1,000 V DC or peak AC for one minute, channel to channel or
channel to logic.
International Electromagnetic Specification
Compatibility EN55011
EN61000-4-2
EN61000-4-3
EN61000-4-4
EN61000-4-5
EN61000-4-6
Operating temperature range 0 to 60°C (32°F to 140°F).
Storage temperature range Per Ovation standard.
Humidity (non-condensing) range 0% to 95%
Vibration 0.15mm displacement from 10 to 57 Hz and 2G's from 57 to 500
Hz.
Shock 15G's for 11 milliseconds and 1/2 sine wave.
2.2 What are Profibus hardw are and softw are requirements?
Proper operation of a Profibus interface with an Ovation system requires:

 Ovation 3.1 or greater. Ovation 3.1.1 or greater is required if you want to utilize redundancy.
 One Ovation Operator Station drop, running the Windows operating system.
 One or more Profibus I/O modules as necessary.
 Profibus cabling (2-wire) as necessary to connect the Profibus I/O module to the Profibus
device(s). Additional modules might be necessary if you plan to create a redundant
connection.
 GSD configuration files for each Profibus slave device connected to the network.
Note: When installing Profibus segments, it is crucial to use genuine Profibus cabling. Both
Profibus cables and Type E thermocouple cables are similar purple colors. Ensure that your
Profibus cabling is actually labeled 'Profibus' on the purple cable casing.
12 OW350_36
S E C T I O N 3
3 Configuring Profibus
IN THIS SECTION
Configuring Profibus devices for standard (simplex) configurations ................................. 13

Configuring Profibus devices for redundant modules configurations ................................ 42
3.1 Configuring Profibus devices for standard (simplex)

configurations
The following steps provide an overview of configuring a Profibus device for standard (simplex)
configurations in an Ovation system. Refer to the specific topics for detailed instructions.
To configure and use your Profibus devices, complete the following tasks:
1. Create a control task. (see page 14)

2. Enable multiple control tasks. (see page 15)
3. Use the Developer Studio to add a new Ovation I/O device number to the Controller. (see
page 16)
4. Insert a Profibus I/O module in the Developer Studio. (see page 18)
5. Add a module record point name (see page 21).
6. Configure Profibus Port Redundancy. (see page 23)
7. Create a node record. (see page 24)
8. Assign a node record to each of your ports. (see page 27)
9. Add a redundant module (optional). (see page 28)
10. Set a module's mode as simplex (optional-- the default is simplex). (see page 28)
11. Access the Profibus module engineering window. (see page 28)
12. Access the Profibus module configuration window. (see page 30)
13. Add new slave devices to your device catalog. (see page 30)
14. Add Profibus slaves. (see page 31)
15. Configure Profibus slaves. (see page 32)
16. Edit a slave's station ID (optional). (see page 33)
17. Use the Process Data window (optional). (see page 33)
18. Configure bus parameter settings (optional). (see page 35)
19. View the Address Table (optional). (see page 36)
20. Configure points for each Profibus signal. (see page 37)
21. Download the Controller. (see page 38)
OW350_36 13
3.1 Configuring Profibus devices for standard (simplex) configurations
22. Clear the Controller. (see page 39)

23. Load the Controller (see page 40).
Note: When you add or delete a Profibus module, you must download and load the Controller.
After the initial configuration, you will only need to load when you add or delete a module, or
change point records (for example: assigning points, renaming points, or deleting points) that
are not module records.
3.1.1 To create a control task

1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the drop that you want to create a new control task for:
Systems
Network
Units
Drops
Configuration
Controller
Control
Control Tasks
3. Right-click on Control Tasks and select Insert New. The Insert New Control Tasks Wizard
displays:
Figure 3: Insert New Control Tasks Wizard
4. Enter the number of your control task, or accept the automatically generated, sequentially
next number.
14 OW350_36
5. Click Finish. The New Control Tasks window displays:
Figure 4: New Control Tasks window
6. Enter your sheet set size and period (in milliseconds), as well as your I/O scan type (serial or
parallel).
7. Click OK.
OW350_36 15
3.1.2 To enable multiple control tasks
Note: Multiple Profibus control tasks are supported in Ovation 3.1.2 and later. Each segment
can run on a different control task, but all I/O points assigned to a port must be on the same
control task that the port resides on.

2. Use the system tree to navigate to a port:
System
Network
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
3. Right-click on the port and select Open.
4. Select a control task from the I/O task index drop-down.
5. Click OK.
6. Ensure that the node record and all associated points assigned to this port have the same
control task. To check this, open the node record and navigate to the Hardware tab. Check
the number in I/O task index. That number should match the I/O Task Index number on the
Hardware tab of the I/O point. If the I /O task does not match, you will receive an error when
you load the Controller.
Note: For redundant Profibus modules, it is recommended that you use a 1000ms (1s) control
task time.
3.1.3 To add a new I/O device number to the Controller using the Developer
Studio
2. Use the system tree to navigate to the Device Number item:
System
Network
Units
Drops
Configuration
Controller
Devices
Device Number
3. Right-click on the Device Number.
16 OW350_36
4. Select Insert New. The Insert New Device Numbers Wizard appears.
Figure 5: Insert New Device Numbers wizard
5. From the Value drop-down menu, select an unused number (for example, you might start
with 5, and continue numbering successive devices sequentially).
6. Click Finish. The New Device Numbers window appears:
7. From the I/O Driver Type drop-down menu, select PROFIBUS MODULE.
8. Click OK.
9. Use the Developer Studio system tree to navigate to I/O Devices:
Systems > Networks > Units > Drops > I/O Devices
10. Right-click on the I/O Devices to select Insert New. The Insert New I/O Devices wizard
appears.
OW350_36 17
11. From the I/O Device Number drop-down menu, select an unused number greater than 1 (for
example, you might start with 2 and continue numbering sequentially).
12. Click Finish.
13. Select PROFIBUS from the I/O Device Type drop-down menu.
14. Click Finish. The New I/O Device window appears.
15. Click OK.
Note: You only have to perform this task once for each Controller that utilizes Profibus.
3.1.4 To insert a Profibus I/O module in the Developer Studio

2. Use the system tree to navigate to an empty slot under your Ovation I/O Interface:
System
Network
Units
Drops
I/O Devices
IOIC
I/O Interfaces
Branch
Slot
3. Select the Ovation module in the slot that you want to modify.
4. Right-click on the Ovation module and select Insert New. The Insert New Ovation Module
wizard appears.
Figure 6: Insert New Ovation Module wizard
5. Select Profibus BusModule.

6. Click Finish. The New Ovation Module window appears.
18 OW350_36
7. Emerson recommends that you leave the Module Record Point Name in the Value column
empty.
8. Navigate to the Module tab.
Figure 7: Module tab
9. Select radio button: Simplex/Port Redundancy (the standard configuration).

10. Click OK to finish.
OW350_36 19
11. The following figure shows the two ports (P01 and P02) that have been automatically created
in the appropriate slot in the Developer Studio.
Figure 8: P01 and P02
Notes:
 If Ovation Profibus Port Redundancy is going to be used for ports on this module, the user
must select Simplex/Port Redundancy.
 You must perform this task for each Profibus I/O module that you add.
20 OW350_36
3.1.5 To add a module record point name

2. Use the system tree to navigate to the appropriate Module Points:
System
Network
Units
Drops
Points
Module Points
3. Right-click on the Module Points and select Insert New. The Insert New Module Points
wizard appears.
Figure 9: Insert New Module Points wizard
4. Type a point name.

5. Pick a frequency.
OW350_36 21
6. Click Finish. The New Module Points window appears.
Figure 10: New Module Points window
7. Navigate to the Hardware tab.
Figure 11: New Module Points Hardware tab
8. Choose the I/O module from the location where you added it.
9. Click OK. If you navigate to your card and Refresh, you will see the fully-qualified module
record point name (for example, TEST.UNIT@PB).
Note: You must perform this task for each Profibus I/O module that you add.
22 OW350_36
3.1.6 To configure Profibus Port Redundancy

2. Use the system tree to navigate to the appropriate ports:
System
Networks
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
3. Determine which two ports will be paired together. These can be any two ports within same
drop. These ports cannot be on modules configured for Module Redundancy.
5. Designate a Channel A and a Channel B port.
6. For all Channel B ports:
a) Remove any existing Profibus configuration and un-assign any associated I/O and node
records.
b) If devices are configured, open the SYCON.net engineering tool for the port and delete
all devices.
c) Delete the slave devices under the port in the Ovation Developer Studio.
Note: If you attempt to designate a port as Channel B and there are existing devices, the
Ovation Developer Studio displays an error alert similar to the following figure.
Figure 12: Error message
OW350_36 23
7. Open the port configuration and set the Channel field as either Channel A or Channel B.
8. Click Apply.
9. Go to the partner port, set its field, and click Apply.
10. Designate a mode and click Apply.
11. A list of available partner ports appears in the Redundant Channel drop-down box. Select a
channel and click OK/Apply.
12. Repeat the steps listed above in this topic for every channel.
Note: The default mode for every port is stand-alone. Therefore, no action needs to be taken for
simplex ports. Also, any already configured simplex ports will not need to be adjusted.
13. For each Channel A port, open up the SYCON.net engineering tool and configure the port
as usual.
Notes:
 Only the Channel A and stand-alone ports can be configured.

 The Ovation Developer Studio will not allow a Channel B port to be configured. If an attempt
is made to configure a Channel B port, the Ovation Developer Studio will display an error
alert similar to the following figure.
Figure 13: Error Message
24 OW350_36
3.1.7 To create a node record

Systems
Networks
Units
Drops
Points
Node Points
3. Right-click on the Node Points and select Insert New. The Insert New Node Points wizard
displays:
Figure 14: Insert New Nodes Points Wizard
4. Enter the point name for your new node record.
OW350_36 25
5. Click Finish. The New Node Points window displays:
Figure 15: New Node Points window
Note: You can select your security settings, display properties, choose hardware settings, and
select historian settings by scrolling through the tabs of this window.
6. Navigate to the Hardware tab:
Figure 16: New Node Points window, Hardware tab
7. Leave the I/O Module field blank.

8. Select an I/O task index number. The I/O task index number must match the I/O task index
number that you configure when you assign a node record to each of your ports (see page
27).
9. Click OK.
26 OW350_36
3.1.8 To assign a node record to each of your ports
Note: You must open each port that you want to use and assign it a node record.

System
Network
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
3. Select the port that you want to update (for example, P01 or P02).
4. Right-click the port and select Open. A port configuration window appears:
Figure 17: Port configuration window
OW350_36 27
5. Type an Ovation Point Name. Do not fully qualify the point name (for example, type TEST,
not TEST.UNIT@PB). If this name currently does not exist in your system, it is added when
you click OK.
Notes:
 Module Redundancy must be Simplex.

 Channel must be set to Channel A or Channel B.
6. Enter an I/O task index number in the I/O task index field.
7. Click OK.
Notes:
 All points assigned to a port must be assigned to the same control task or you will receive
an error when you attempt to load.
3.1.9 To add a redundant module (optional)
If you are using redundant modules, add them now by repeating the three following configuration
steps for each of your redundant modules:
1. To insert a Profibus I/O module in the Developer Studio (see page 18)
2. To add a module record point name (see page 21)
3. To assign a node record to each of your ports (see page 27)
You must perform additional configuration steps from a primary module, not a secondary module.
The settings that you make on a primary module are inherited by its redundant partner module.
3.1.10 To set a module's mode as simplex (optional-- the default is simplex)
Note: Profibus modules are set as simplex modules by default. You only need to change this
setting if you are using redundant modules.
1. Select a module from the slot in the Developer Studio tree.

2. Double-click the module to open it. The module configuration window displays.
3. Click the Module tab.
4. Select the radio button: Simplex (the default).
5. Click OK.
28 OW350_36
3.1.11 To access the Profibus module engineering window

2. Use the system tree to navigate to a Profibus port:
System
Networks
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
3. Right-click on a port (for example, P01 or P02) and select Engineer. The Profibus module
engineering window displays:
Figure 18: Profibus module configuration window
Your device catalog displays in the right-hand pane, organized by manufacturer. The main
pane is where you design your segment and its devices.
Note: Ports are engineered and locked individually to give you more freedom to update and use
ports separately. This means that you must engineer each Profibus port individually.
OW350_36 29
3.1.12 To access the Profibus module configuration window

System
Networks
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
3. Right-click on a port (for example, P01 or P02) and select Open. The Profibus module
configuration window displays.
30 OW350_36
3.1.13 To add new slave devices to your device catalog

1. Locate the GSD file that comes with your device.
2. Add the GSD file to this directory:
C:\Ovation\SYCON.net\EMPBGenSlaveDTM\GSD
3. Restart the Ovation Developer Studio. Your new device displays in the right-hand device
catalog in the Profibus module configuration window.
Note: You must add this GSD file to each workstation that you want to engineer this device on.
3.1.14 To add Profibus slaves

1. Access the Profibus module configuration window (see page 28).
2. Click on the slave device that you want to add from the right-hand device catalog.
3. Drag and drop the slave onto the magenta line in the main pane:
Figure 20: Master and slave diagram
You have now added a slave device to your Ovation I/O module (which is a master).
Device names are a combination of your symbolic (local) name, the manufacturer name, and
a station ID.
For example, if your device name is: TEMP01 [CIF60-DPS] <4>, your local name is set to
TEMP01, the manufacturer name is [CIF60-DPS], and the station ID is <4>.
The local name of a device by default duplicates the manufacturer's name. So in this
example, the device name would have been CIF60-DPS [CIF60-DPS] <4> before you edited
your local name. The station ID number is set by default to the next available number, but you
can also edit this.
OW350_36 31
3.1.15 To configure Profibus slaves

2. Right-click on one of the slaves that you have added to your segment in the main pane.
3. Select Symbolic Name. The Change Symbolic Name window displays:
Figure 21: Change Symbolic Name window
4. If desired, type a new symbolic (local) name and click OK. By default, the symbolic name is
identical to the manufacturer's name, but you might need to edit the symbolic name to ensure
that each device in your system has a unique, easy-to-identify name.
5. Right-click on the slave again and select Configuration. A configuration screen tailored to
this device displays:
Figure 22: Slave configuration window
32 OW350_36
You can use this window to perform all the configuration tasks for a slave device. For
example, you can select available modules (input types) that you want this slave to use and
click Insert for each type. These modules define the work that each slave is capable of doing.
Each slave can hold up to 24 modules. Remember that other considerations (such as byte
size of each module that you add, up to 368 bytes) can also constrain you.
6. Click OK. The slave is now configured.
3.1.16 To edit a slave's station ID (optional)

2. Right-click on your master device in the main pane to select Configuration. A configuration
window specific to your master device displays.
3. On the left-hand pane, under Configuration, click Station Table:
Figure 23: Station Table window
4. Edit a slave device's Station field to give the slave a new station ID number.
5. Click Apply.
OW350_36 33
3.1.17 To use the Process Data window (optional)

window specific to your master device displays:
Figure 24: Master configuration window
3. Click Process Data in the left-hand tree. A Process Data configuration window specific to
your master device displays:
Figure 25: Process Data window
34 OW350_36
You can use this window to view and edit details for your master's slave devices, and perform
tasks like changing the name of a signal.
4. Select a 16-byte input to view the list of 8-byte inputs beneath it.
5. Rename the inputs as needed (for example, you could change INPUT_1 to TEMPERATURE)
for a specific Profibus signal.
6. Click OK.
3.1.18 To configure bus parameter settings (optional)

3. Click on the Bus Parameters in the left-hand tree. The Bus Parameters window displays:
Figure 26: Bus Parameters window
4. Edit the parameters as needed. You can click the Adjust button at any time to refresh
numerical values after you have updated settings. One example of when you might want to
use the Adjust button is after you have configured all devices on a segment.
OW350_36 35
Notes:
 If you are using redundant modules, it is recommended that you select the Override slave
specific Watchdog Control Time check box, and set the Watchdog Control Time at least
2,000 ms.
 In addition, you should adjust the Data Control Time to six times the watchdog control time
(making this adjustment will eliminate error pop-up dialogs).
 This modification is due to the fact that redundant modules add complexity to your system,
and the watchdogs that monitor the slave devices should be set to allow the slaves extra
time to communicate before the watchdogs cause a device to indicate a bad status (which
will cause any assigned points to go into bad quality).
5. Click OK.
CAUTION! There is no option to return the settings to their default values after you
make changes. It is recommended that you document the original settings before
making changes.
3.1.19 To view the Address Table (optional)

3. Click on the Address Table in the left-hand tree. The Address Table window displays:
Figure 27: Address Table window
You can use this window to view a memory map of your entire port. You cannot make any
edits or configuration changes in this window.
4. Click OK.
36 OW350_36
3.1.20 To configure points for each Profibus signal

2. Click the Point Assignment tab in the main pane.
3. Click on one of the slots under a slave device:
Figure 28: Slave device slots
The signals for that slot are displayed on the bottom right side.
OW350_36 37
4. Follow the instructions in the following table to add an analog, digital, or packed point to a
signal:
TYPE OF ACTION TO ADD POINT
POINT
Analog Click Analog Points in the Developer Studio tree to display a list of available analog
points in the bottom pane.
Drag and drop an analog point from the bottom pane into the Point field for the
signal that you want to assign it to.
By default, the data is interpreted as unsigned short. To change this, open the point
and navigate to the Hardware tab.
Digital Select the 8-bit input check box for the signal that you want to add a digital point to.
When the check box is selected, the signal becomes expandable so that you can
view each individual bit for that signal.
Click Digital Points in the Developer Studio tree to display a list of available digital
Drag and drop a digital point from the bottom pane into one of the numbered bit
fields that you expanded for that signal.
Packed Click Packed Points in the Developer Studio tree to display a list of available
packed points in the bottom pane.
Drag and drop a packed point from the bottom pane into the yellow Point field for
the signal that you want to assign it to.
By default, it is assumed that you do not need to swap bytes or other information when
interfacing with Profibus slave data. If you need to change bytes or other information, open
the point and navigate to its Hardware tab.
Notes:
 Some devices do not comply with the requirement that the highest-order byte be transmitted
first in messages from your devices. If your device does not transmit bytes 'highest first,' you
must swap the byte order to remedy the situation.
 For each type of point, open the point to configure it, and navigate to the Byte Order
selection on the Hardware tab.
 The choices are Swap Bytes, Swap Words, and Swap Bytes and Words. Set the Byte
Order option to match the byte order of the corresponding slave device. Consult the device
manual for the particular Profibus Slave device to determine the appropriate byte order.
5. If you no longer want a point on a signal, right-click on that point to select Unassign Point.
The point is removed from that signal.
6. Click OK or Apply. Your changes are sent to the Ovation database. You can view your
configuration changes immediately in the Developer Studio tree.
38 OW350_36
3.1.21 To download the Controller

2. Use the system tree to navigate to the Controller drop that you added configurations to:
Studio System
System
Network
Unit
Drops
3. Right-click on a drop and select Download:
Figure 29: Drop download
4. Select the drop that you want to download.

5. Click Finish.
Note: You can also download at the System, Network, and Unit level when you want to
download multiple drops.
OW350_36 39
3.1.22 To clear the Controller

Studio System
System
Network
Unit
Drops
3. Right-click on the drop and select Clear. A confirmation window displays.
4. Select Yes.
5. Select the drop that you want to clear.
6. Click Finish.
40 OW350_36
3.1.23 To load the Controller

System
Network
Unit
Drops
3. Right-click on the drop and select Load:
Figure 30: Drop load
4. Select the drop that you want to load.

5. Click Finish.
OW350_36 41
3.2 Configuring Profibus devices for redundant modules configurations
3.2 Configuring Profibus devices for redundant modules

configurations
The following steps provide an overview of configuring a Profibus device for redundant modules
configurations in an Ovation system. Refer to the specific topics for detailed instructions.
To configure and use your Profibus devices, complete the following tasks:
1. Create a control task (see page 14).

2. Enable multiple control tasks. (see page 15)
3. Use the Developer Studio to add a new Ovation I/O device number to the Controller (see
page 16).
4. Insert a Profibus I/O module in the Developer Studio (see page 18).
5. Add a module record point name (see page 21).
6. Configure Profibus Port Redundancy. (see page 23)
7. Create a node record (see page 24).
8. Assign a node record to each of your ports (see page 27).
9. Add a redundant module (optional) (see page 28).
10. Set a module's mode as simplex or redundant (optional-- the default is simplex) (see page
28).
11. Access the Profibus module engineering window. (see page 28)
13. Design a redundant module segment (optional) (see page 58).
14. Add new slave devices to your device catalog (see page 30).
15. Add Profibus slaves (see page 31).
16. Configure Profibus slaves (see page 32).
17. Edit a slave's station ID (optional) (see page 33).
18. Use the Process Data window (optional) (see page 33).
19. Configure bus parameter settings (optional) (see page 35).
20. View the Address Table (optional) (see page 36).
21. Configure points for each Profibus signal (see page 37).
22. Download the Controller (see page 38).
23. Clear the Controller (see page 39).
24. Load the Controller (see page 40).
Note: When you add or delete a Profibus module, you must download and load the Controller.
After the initial configuration, you will only need to load when you add or delete a module, or
change point records (for example: assigning points, renaming points, or deleting points) that
are not module records.
42 OW350_36
3.2.1 To create a control task

Systems
Network
Units
Drops
Configuration
Controller
Control
Control Tasks
3. Right-click on Control Tasks and select Insert New. The Insert New Control Tasks Wizard
displays:
Figure 31: Insert New Control Tasks Wizard
4. Enter the number of your control task, or accept the automatically generated, sequentially
next number.
OW350_36 43
5. Click Finish. The New Control Tasks window displays:
Figure 32: New Control Tasks window
6. Enter your sheet set size and period (in milliseconds), as well as your I/O scan type (serial or
parallel).
7. Click OK.
3.2.2 To enable multiple control tasks
Note: Multiple Profibus control tasks are supported in Ovation 3.1.2 and later. Each segment
can run on a different control task, but all I/O points assigned to a port must be on the same
control task that the port resides on.

System
Network
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
4. Select a control task from the I/O task index drop-down.
44 OW350_36
5. Click OK.
6. Ensure that the node record and all associated points assigned to this port have the same
control task. To check this, open the node record and navigate to the Hardware tab. Check
the number in I/O task index. That number should match the I/O Task Index number on the
Hardware tab of the I/O point. If the I /O task does not match, you will receive an error when
you load the Controller.
Note: For redundant Profibus modules, it is recommended that you use a 1000ms (1s) control
task time.
3.2.3 To add a new I/O device number to the Controller using the Developer
Studio
2. Use the system tree to navigate to the Device Number item:
System
Network
Units
Drops
Configuration
Controller
Devices
Device Number
3. Right-click on the Device Number.

4. Select Insert New. The Insert New Device Numbers Wizard appears.
Figure 33: Insert New Device Numbers wizard
5. From the Value drop-down menu, select an unused number (for example, you might start
with 5, and continue numbering successive devices sequentially).
OW350_36 45
6. Click Finish. The New Device Numbers window appears:
7. From the I/O Driver Type drop-down menu, select PROFIBUS MODULE.
8. Click OK.
9. Use the Developer Studio system tree to navigate to I/O Devices:
Systems > Networks > Units > Drops > I/O Devices
10. Right-click on the I/O Devices to select Insert New. The Insert New I/O Devices wizard
appears.
11. From the I/O Device Number drop-down menu, select an unused number greater than 1 (for
example, you might start with 2 and continue numbering sequentially).
12. Click Finish.
13. Select PROFIBUS from the I/O Device Type drop-down menu.
14. Click Finish. The New I/O Device window appears.
15. Click OK.
Note: You only have to perform this task once for each Controller that utilizes Profibus.
3.2.4 To insert a Profibus I/O module for module redundancy in the Developer
Studio
2. Use the system tree to navigate to an empty slot under your Ovation IOIC branch:
System
Network
Units
Drops
I/O Devices
IOIC
I/O Interfaces
Branch
Slot
3. Select the Ovation module in the slot that you want to modify.
46 OW350_36
4. Right-click on the Ovation module and select Insert New. The Insert New Ovation Module
wizard appears.
Figure 34: Insert New Ovation Module wizard
5. Select Profibus BusModule.

6. Click Finish. The New Ovation Module window appears.
7. Emerson recommends that you leave the Module Record Point Name in the Value column
empty.
8. Navigate to the Module tab.
Figure 35: Module tab
9. Select radio button: Module-Level Redundancy.

10. Select a redundant partner from the Redundant Partner drop-down list, which must already
be added.
OW350_36 47
11. Click OK.

12. Click OK. Two ports (P01 and P02) are automatically created in the slot.
3.2.5 To add a module record point name

2. Use the system tree to navigate to the appropriate Module Points:
System
Network
Units
Drops
Points
Module Points
3. Right-click on the Module Points and select Insert New. The Insert New Module Points
wizard appears.
Figure 36: Insert New Module Points wizard
4. Type a point name.

5. Pick a frequency.
48 OW350_36
6. Click Finish. The New Module Points window appears.
Figure 37: New Module Points window
7. Navigate to the Hardware tab.
Figure 38: New Module Points Hardware tab
8. Choose the I/O module from the location where you added it.
9. Click OK. If you navigate to your card and Refresh, you will see the fully-qualified module
record point name (for example, TEST.UNIT@PB).
OW350_36 49
3.2.6 To configure Profibus Port Redundancy

2. Use the system tree to navigate to the appropriate ports:
System
Networks
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
3. Determine which two ports will be paired together. These can be any two ports within same
drop. These ports cannot be on modules configured for Module Redundancy.
5. Designate a Channel A and a Channel B port.
6. For all Channel B ports:
a) Remove any existing Profibus configuration and un-assign any associated I/O and node
records.
b) If devices are configured, open the SYCON.net engineering tool for the port and delete
all devices.
c) Delete the slave devices under the port in the Ovation Developer Studio.
Note: If you attempt to designate a port as Channel B and there are existing devices, the
Ovation Developer Studio displays an error alert similar to the following figure.
Figure 39: Error message
50 OW350_36
7. Open the port configuration and set the Channel field as either Channel A or Channel B.
8. Click Apply.
9. Go to the partner port, set its field, and click Apply.
10. Designate a mode and click Apply.
11. A list of available partner ports appears in the Redundant Channel drop-down box. Select a
channel and click OK/Apply.
12. Repeat the steps listed above in this topic for every channel.
Note: The default mode for every port is stand-alone. Therefore, no action needs to be taken for
simplex ports. Also, any already configured simplex ports will not need to be adjusted.
13. For each Channel A port, open up the SYCON.net engineering tool and configure the port
as usual.
Notes:
 Only the Channel A and stand-alone ports can be configured.

 The Ovation Developer Studio will not allow a Channel B port to be configured. If an attempt
is made to configure a Channel B port, the Ovation Developer Studio will display an error
alert similar to the following figure.
Figure 40: Error Message
OW350_36 51
3.2.7 To create a node record

Systems
Networks
Units
Drops
Points
Node Points
3. Right-click on the Node Points and select Insert New. The Insert New Node Points wizard
displays:
Figure 41: Insert New Nodes Points Wizard
4. Enter the point name for your new node record.
52 OW350_36
5. Click Finish. The New Node Points window displays:
Figure 42: New Node Points window
Note: You can select your security settings, display properties, choose hardware settings, and
select historian settings by scrolling through the tabs of this window.
6. Navigate to the Hardware tab:
Figure 43: New Node Points window, Hardware tab
7. Leave the I/O Module field blank.

8. Select an I/O task index number. The I/O task index number must match the I/O task index
number that you configure when you assign a node record to each of your ports (see page
27).
9. Click OK.
OW350_36 53
3.2.8 To assign a node record to each of your ports
Note: You must open each port that you want to use and assign it a node record.

System
Networks
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
3. Select the port that you want to update (for example, P01 or P02).
4. Right-click on the port and select Open. A port configuration window appears:
Figure 44: Port configuration window
54 OW350_36
5. Type an Ovation Point Name. Do not fully qualify the point name (for example, type TEST,
not TEST.UNIT@PB). If this name currently does not exist in your system, it is added when
you click OK.
Notes:
 Module Redundancy must be Port Redundancy. Port Redundancy is not supported on

modules configured for Module Redundancy.
 Channel must be set to Channel A or Channel B.
 The Redundant Channel combo-box contains a list of available complementary ports
(Channel A for a port configured as Channel B).
6. Enter an I/O task index number in the I/O task index field.
7. Click OK.
Notes:
 All points assigned to a port must be assigned to the same control task or you will receive
an error when you attempt to load.
3.2.9 To add a redundant module (optional)
If you are using redundant modules, add them now by repeating the three following configuration
steps for each of your redundant modules:
1. To insert a Profibus I/O module in the Developer Studio (see page 18)
2. To add a module record point name (see page 21)
3. To assign a node record to each of your ports (see page 27)
You must perform additional configuration steps from a primary module, not a secondary module.
The settings that you make on a primary module are inherited by its redundant partner module.
3.2.10 To set a module's mode as redundant
Note: Profibus modules are set as simplex modules by default. You only need to change this
setting if you are using redundant modules.
1. Select a module from the slot in the Developer Studio tree.

2. Double-click the module to open it. The module configuration window displays.
3. Click the Module tab.
4. Select the radio button: Redundant.
If you pick Redundant, you will be able to select a redundant partner from the drop down list,
if there is already a redundant module configured. Configuring a module as redundant is a
setting that must be made at the primary module (and is reflected in its secondary partner
module).
5. Click OK.
OW350_36 55
3.2.11 To access the Profibus module engineering window

System
Networks
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
3. Right-click on a port (for example, P01 or P02) and select Engineer. The Profibus module
engineering window displays:
Your device catalog displays in the right-hand pane, organized by manufacturer. The main
pane is where you design your segment and its devices.
Note: Ports are engineered and locked individually to give you more freedom to update and use
ports separately. This means that you must engineer each Profibus port individually.
56 OW350_36
3.2.12 To access the Profibus module configuration window

System
Networks
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
3. Right-click on a port (for example, P01 or P02) and select Open. The Profibus module
configuration window displays.
OW350_36 57
3.2.13 To design a redundant module segment (optional)
The method to create a redundant module segment is essentially the same as the method to
create a module segment. Note that when you create a redundant segment, you can only access
the primary module, not the secondary. All settings that you choose in the primary module are
inherited by its secondary module. If you attempt to engineer a secondary module, an error
window reminds you:
Figure 47: Secondary module edit warning
To design your redundant segment, refer to "To design a module segment (see page 28)".
3.2.14 To add new slave devices to your device catalog

1. Locate the GSD file that comes with your device.
2. Add the GSD file to this directory:
C:\Ovation\SYCON.net\EMPBGenSlaveDTM\GSD
3. Restart the Ovation Developer Studio. Your new device displays in the right-hand device
catalog in the Profibus module configuration window.
Note: You must add this GSD file to each workstation that you want to engineer this device on.
58 OW350_36
3.2.15 To add Profibus slaves

2. Click on the slave device that you want to add from the right-hand device catalog.
3. Drag and drop the slave onto the magenta line in the main pane:
Figure 48: Master and slave diagram
You have now added a slave device to your Ovation I/O module (which is a master).
Device names are a combination of your symbolic (local) name, the manufacturer name, and
a station ID.
For example, if your device name is: TEMP01 [CIF60-DPS] <4>, your local name is set to
TEMP01, the manufacturer name is [CIF60-DPS], and the station ID is <4>.
The local name of a device by default duplicates the manufacturer's name. So in this
example, the device name would have been CIF60-DPS [CIF60-DPS] <4> before you edited
your local name. The station ID number is set by default to the next available number, but you
can also edit this.
OW350_36 59
3.2.16 To configure Profibus slaves

2. Right-click on one of the slaves that you have added to your segment in the main pane.
3. Select Symbolic Name. The Change Symbolic Name window displays:
Figure 49: Change Symbolic Name window
4. If desired, type a new symbolic (local) name and click OK. By default, the symbolic name is
identical to the manufacturer's name, but you might need to edit the symbolic name to ensure
that each device in your system has a unique, easy-to-identify name.
5. Right-click on the slave again and select Configuration. A configuration screen tailored to
this device displays:
Figure 50: Slave configuration window
60 OW350_36
You can use this window to perform all the configuration tasks for a slave device. For
example, you can select available modules (input types) that you want this slave to use and
click Insert for each type. These modules define the work that each slave is capable of doing.
Each slave can hold up to 24 modules. Remember that other considerations (such as byte
size of each module that you add, up to 368 bytes) can also constrain you.
6. Click OK. The slave is now configured.
3.2.17 To edit a slave's station ID (optional)

3. On the left-hand pane, under Configuration, click Station Table:
Figure 51: Station Table window
4. Edit a slave device's Station field to give the slave a new station ID number.
5. Click Apply.
OW350_36 61
3.2.18 To use the Process Data window (optional)

window specific to your master device displays:
Figure 52: Master configuration window
3. Click Process Data in the left-hand tree. A Process Data configuration window specific to
your master device displays:
Figure 53: Process Data window
62 OW350_36
You can use this window to view and edit details for your master's slave devices, and perform
tasks like changing the name of a signal.
4. Select a 16-byte input to view the list of 8-byte inputs beneath it.
5. Rename the inputs as needed (for example, you could change INPUT_1 to TEMPERATURE)
for a specific Profibus signal.
6. Click OK.
3.2.19 To configure bus parameter settings (optional)

3. Click on the Bus Parameters in the left-hand tree. The Bus Parameters window displays:
Figure 54: Bus Parameters window
4. Edit the parameters as needed. You can click the Adjust button at any time to refresh
numerical values after you have updated settings. One example of when you might want to
use the Adjust button is after you have configured all devices on a segment.
OW350_36 63
Notes:
 If you are using redundant modules, it is recommended that you select the Override slave
specific Watchdog Control Time check box, and set the Watchdog Control Time at least
2,000 ms.
 In addition, you should adjust the Data Control Time to six times the watchdog control time
(making this adjustment will eliminate error pop-up dialogs).
 This modification is due to the fact that redundant modules add complexity to your system,
and the watchdogs that monitor the slave devices should be set to allow the slaves extra
time to communicate before the watchdogs cause a device to indicate a bad status (which
will cause any assigned points to go into bad quality).
5. Click OK.
CAUTION! There is no option to return the settings to their default values after you
make changes. It is recommended that you document the original settings before
making changes.
64 OW350_36
3.2.20 To view the Address Table (optional)

3. Click on the Address Table in the left-hand tree. The Address Table window displays:
Figure 55: Address Table window
You can use this window to view a memory map of your entire port. You cannot make any
edits or configuration changes in this window.
4. Click OK.
OW350_36 65
3.2.21 To configure points for each Profibus signal

2. Click the Point Assignment tab in the main pane.
3. Click on one of the slots under a slave device:
Figure 56: Slave device slots
The signals for that slot are displayed on the bottom right side.
66 OW350_36
4. Follow the instructions in the following table to add an analog, digital, or packed point to a
signal:
TYPE OF ACTION TO ADD POINT
POINT
Analog Click Analog Points in the Developer Studio tree to display a list of available analog
Drag and drop an analog point from the bottom pane into the Point field for the
By default, the data is interpreted as unsigned short. To change this, open the point
and navigate to the Hardware tab.
Digital Select the 8-bit input check box for the signal that you want to add a digital point to.
When the check box is selected, the signal becomes expandable so that you can
view each individual bit for that signal.
Click Digital Points in the Developer Studio tree to display a list of available digital
Drag and drop a digital point from the bottom pane into one of the numbered bit
fields that you expanded for that signal.
Packed Click Packed Points in the Developer Studio tree to display a list of available packed
Drag and drop a packed point from the bottom pane into the yellow Point field for the
By default, it is assumed that you do not need to swap bytes or other information when
interfacing with Profibus slave data. If you need to change bytes or other information, open
the point and navigate to its Hardware tab.
Notes:
 Some devices do not comply with the requirement that the highest-order byte be transmitted
first in messages from your devices. If your device does not transmit bytes 'highest first,' you
must swap the byte order to remedy the situation.
 For each type of point, open the point to configure it, and navigate to the Byte Order
selection on the Hardware tab.
 The choices are Swap Bytes, Swap Words, and Swap Bytes and Words. Set the Byte
Order option to match the byte order of the corresponding slave device. Consult the device
manual for the particular Profibus Slave device to determine the appropriate byte order.
5. If you no longer want a point on a signal, right-click on that point to select Unassign Point.
The point is removed from that signal.
6. Click OK or Apply. Your changes are sent to the Ovation database. You can view your
configuration changes immediately in the Developer Studio tree.
OW350_36 67
3.2.22 To download the Controller

System
Network
Unit
Drops
3. Right-click on a drop and select Download:
Figure 57: Drop download
4. Select the drop that you want to download.

5. Click Finish.
Note: You can also download at the System, Network, and Unit level when you want to
download multiple drops.
3.2.23 To clear the Controller

68 OW350_36
Studio System
System
Network
Unit
Drops
3. Right-click on the drop and select Clear. A confirmation window displays.
4. Select Yes.
5. Select the drop that you want to clear.
6. Click Finish.
OW350_36 69
3.2.24 To load the Controller

System
Network
Unit
Drops
3. Right-click on the drop and select Load:
Figure 58: Drop load
4. Select the drop that you want to load.

5. Click Finish.
70 OW350_36
S E C T I O N 4
4 Profibus on-line diagnostics
IN THIS SECTION
What are Profibus online diagnostics? .............................................................................. 71

Network scan option .......................................................................................................... 76
4.1 What are Profibus online diagnostics?
The Profibus Online Diagnostics tool provides live diagnostics information from a selected
Profibus network. When connected to the Profibus network, you are able to see the status of
slaves on the network along with diagnostic and running state information for the slaves and the
master. While not a complete set of diagnostics, the information can be used when
troubleshooting slave failures and detecting certain communication problems.
4.1.1 To access Profibus online diagnostics

System
Networks
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
OW350_36 71
3. Right-click on a port to select Open. The Profibus module configuration window displays:
4. Right-click the Ovation Profibus master (displayed in the example as the module stemming
from the green line) to select one of the main menu functions:
Figure 60: Profibus configuration window main menu
72 OW350_36
Profibus menu descriptions
MAIN MENU OPTION USE
Connect Use this option to connect your master to the segment beneath it. This is
mandatory before your Profibus network can function.
Disconnect Not used.
Download Not used.
Upload Not used.
Configuration Use this menu option to select the appropriate driver, IP address range of the
Controllers that your Profibus network is using, and to scan for all available
ports in order to select a port.
Measured Value Not used.
Simulation Not used.
Diagnostic Not used.
Additional Functions This menu option has one enabled use: Print Configuration, which lets you
print your configuration and diagnostic information for your records.
Delete Not used.
Symbolic Name Use this menu option to change the symbolic name of the master module. The
symbolic name is the name that the network uses internally to refer to the
master device.
Device Properties Not used.
OW350_36 73
4.1.2 To use Profibus on-line diagnostics to configure a driver

System
Networks
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
3. Right-click on a port to select Engineer.
4. Right-click on the Profibus port that you want to monitor and select Configuration. The
Profibus module configuration window displays.
5. Navigate to Driver in the left-hand pane and select the OCR400 check box:
Figure 61: Driver OCR400 selection
6. Select OCR400 under Driver in the left-hand pane.
74 OW350_36
7. Enter the range of Controller IP addresses that you want to scan. You can only enter one IP
address in the Start and End columns. The IP address range that you enter here tells the tool
which Controller IPs to search for bus module ports:
Figure 62: IP address ranges
8. Change the Scan Time to 10000ms (10s).

9. Click Save.
10. Select Device Assignment in the left-hand pane.
11. Click Scan. A list of each available Profibus port/segment on each Controller in your IP
scanning range displays.
12. Select the check box next to the port that you want to monitor.
13. Click OK.
14. Right-click on the Profibus master to select Connect. After connection, the text above the
Profibus master displays in a green box.
15. After connecting, right-click on the Profibus master to select Diagnostic.
16. Navigate through the different diagnostic functions. The Bus Diagnosis window shows the
operating state of the master and network. The Station Diagnosis window shows the status of
the individual slaves on the segment. If the slave appears green or yellow, the device is
healthy and communicating. If the slave is red, there is an error. At the bottom of the Station
Diagnosis window, an error code may be displayed. Refer to the specific device manual for
further help.
OW350_36 75
4.2 Network scan option
4.2 Netw ork scan option
Network scan is an auto sensing option that is part of the Profibus engineering user interface in
the Ovation Developer Studio. Network Scan provides a list of slave devices detected on the
Profibus port.
Network scan can be initiated while engineering the Profibus port after the master is assigned to
the physical port.
Options for Network Scan include the following:

 Add - adds the detected device to the Ovation database.
 Replace - replaces the existing device to the Ovation database.
 Ignore - ignores the detected device and retains the existing device configuration in the
Ovation database.
After the device scan has completed, a module scan is performed to detect the module
configuration for each device selected to be added or replaced. If a conflict arises during the
module scan, you may be required to manually resolve the conflict before modules can be added
or replaced.
4.2.1 Preparing to perform network scan
Before performing a network scan on a Profibus port, the following factors should be considered:
During the network scan, if you choose to replace an existing device with the detected device on
the Profibus port, then any I/O or node/diagnostic (RN record) point assignments to the modules
of the device will be lost.
All point assignments to the selected device will be lost (although, the points will not be deleted
from the database). All points will need to be manually reassigned.
Therefore, careful consideration must be given before deciding to replace an existing device
configuration with the detected device. After replacing a device, you have to manually re-assign
all the points back to the appropriate modules and devices.
4.2.2 Requirements for a successful network scan
The following requirements are necessary for a network scan to function properly:
 The Ovation Profibus module must be assigned to a physical port. For example, a correct
access path must be assigned in the Device Assignment page of the master device's
Configuration dialog. Refer to: To access Profibus online diagnostics (see page 71).
 GSD files for the slave devices must exist in the device catalog for the network scan to
recognize the device configuration correctly. Refer to: To add new slave devices to your
device catalog (see page 30).
 GSD files must be a generic (standard) device definition file. Network scan will not be able to
use non-generic (custom) GSD files.
76 OW350_36
4.2.3 Network scan
Profibus network scan is accessed through the Ovation Developer Studio using the Profibus
Engineering user interface. The Profibus master context menu has an option to perform the
network scan.
Network scan is performed only after assigning the Ovation Profibus Module to the physical port
and configuring the appropriate access path in the Configuration dialog's Device Assignment
page.
To start a network scan:
1. Right-click on the Profibus Module (Master device) in the Profibus UI.

2. Select the Network Scan option.
4.2.4 Topology scan
The Topology scan produces a list of slaves detected on the Profibus network.
When the Topology scan completes, a dialog with the list of devices is displayed. In this dialog,
you are given an option to skip, add, or replace the current configured devices with the detected
devices.
The following information is provided in the Topology scan result dialog:
ITEM DESCRIPTION
Station Address Device address on the Profibus network.

Device Type ID Unique 2 byte identifier of the device.
DTM to Use Specifies which DTM to use.
DTM Device Specifies the detected GSD file from the catalog. If more than one GSD file is
detected for the same device type, you can pick the appropriate DTM from the list.
Action List of choices:
If the detected device already exists in the engineering UI, then you can select either
Skip or Replace.
 Skip - Retains the existing device in the engineering UI.
 Replace - Overwrites the existing device in the engineering UI with the detected
device.
If the detected device does not exist in the engineering UI, then you can select either
Skip or Add.
 Skip - To ignore the detected device.
 Add - To auto create the detected device in the engineering UI.
Notes:
 If the Add or Replace option is selected for a device, then a module scan is performed to get
the device configuration.
 If the Replace option is selected for a device, then the scan configuration is replaced with
the current detected configuration in the engineering UI. In this case, all the previously
mapped points to the modules and the device itself will be lost.
OW350_36 77
4.2.5 Module scan
If Add or Replace is selected for a device in the topology scan dialog, that device will be
automatically scanned to detect its module configuration.
Since, for a particular slave device, a single module identifier can be associated with different
physical hardware, a situation could exist where the automatic module scan might not be able to
correctly resolve the module configuration from the detected device.
In this case, a module configuration dialog is displayed and the conflict can be resolved manually.
Once the conflict is resolved and the configuration is confirmed, the device is added to the
network in the engineering UI.
78 OW350_36
S E C T I O N 5
5 Module firmware
IN THIS SECTION
What is module firmware? ................................................................................................. 79
5.1 What is module firmw are?
Firmware contains the elements necessary for proper Ovation DeviceNet or Profibus module
operation, including:
 Scripts.
 Ovation bus communication drivers.
 Ovation driver.
 Ovation I/O interface drivers.
The firmware runs on the Ovation modules and is downloaded to the module using Controller
Diagnostics. The firmware must be query/downloaded to the drop (where the Ovation module is
installed). When updating the module firmware, Controller diagnostics looks at the files on the
drop and module and presents the list and timestamps to you. You can then select the files that
you want to download.
Note: All module firmware files must be downloaded to the Controller before you load the
module.
For more information about using Controller Diagnostics, refer to the appropriate Ovation
Controller User Guide.
5.1.1 To download module firmware

2. Use the system tree to navigate to a drop.
System
Networks
Units
Drops
3. Right-click on the drop to select Download. All of the latest module firmware files should be
loaded. When performing a query/download to a Controller make sure all the files located in
the \Ovation\VxWorks\Modules directory are downloaded to the Controller. Failure to do this
could result in outdated software residing on the Controller.
4. Navigate your Windows menu to Ovation->Ovation Utilities->Diagnostics.
OW350_36 79
5.1 What is module firmware?
5. Highlight and double-click a Controller from the Controller List:
Figure 63: Controller Diagnostics window
6. Open the I/O Information tab (in the right pane):
Figure 64: I/O Information tab
7. Select a module.
80 OW350_36
8. Click Download Available Firmware. The Module Firmware Download window displays:
Figure 65: Module Firmware Download window
Note: Any out-of-date version is automatically flagged by the Controller Diagnostics Tool. If the
file has a different date than the date on the Controller, the Controller Diagnostics Tool flags this
by automatically setting the check box.
9. Select the files that you want to download by selecting the check boxes. To select all of the
files, check the box next to "Query Results".
OW350_36 81
10. Click Download. It is recommended that you always download all of the available files. This
ensures that the module and software versions are compatible. The following window displays
to continue the download:
11. Click Yes if you want to continue.
Note: All module firmware files must be downloaded to the Controller before you load the
module.
82 OW350_36
12. Reboot the module.
Note: Rebooting can be accomplished by either removing the module and re-installing the
module, or by clicking the "Reboot Module" button. After selecting "Reboot Module" a
confirmation pop-up window appears after approximately 10 seconds to indicate that the module
is in the process of rebooting. Refer to the following figure:
Figure 66: Module confirm window
OW350_36 83
S E C T I O N 6
6 Troubleshooting Profibus
IN THIS SECTION
How do I troubleshoot Profibus? ....................................................................................... 85

What is the best way to troubleshoot redundant module pairs? ....................................... 93
Troubleshooting the bus using the LEDs .......................................................................... 94
Resolving a slave alarm .................................................................................................... 94
Investigating a Profibus fault code .................................................................................... 95
6.1 How do I troubleshoot Profibus?
There are three different ways that you can diagnose Profibus health: through the module itself,
through the slave devices, and by visually inspecting the module LED lights in your Controller.
Diagnostic information for each is accessed differently:
 Module information displays in the module (RM) and node (RN) records status value.
 Slave device information displays in the Controller Diagnostics utility.
Refer to the Ovation Controller User Guide for more information about the Controller
Diagnostics utility.
 LED information is found on the front of the module device in your Controller cabinet.
Some general symptoms and suggested solutions for Profibus troubleshooting include:
SYMPTOM POSSIBLE CAUSE SOLUTION
The module never takes Software has been incorrectly Use the Controller Diagnostics utility to
control and data does not loaded or not loaded at all on the verify that the proper software is loaded
update. module. There is no Profibus on the modules. Update if necessary.
configuration file (.DBM) loaded.
Check the module configuration. Check
the segment and device configuration (in
the A2 field of the node records). Perform
a drop load if necessary.
Module and node record Software has been incorrectly Use the Controller Diagnostics utility to
points periodically go to loaded or not loaded at all on the verify that the proper software is loaded
bad quality or into sensor module. on the modules. Update if necessary.
alarm.
For a redundant module, it is If this is a simplex module, verify that the
possible that both modules think module is in control (for each configured
they are in control. segment).
If this is a redundant module, check to
see that both modules are not in control.
OW350_36 85
SYMPTOM POSSIBLE CAUSE SOLUTION
During a redundant The Profibus watchdog timer Adjust the watchdog times in the Profibus
module failover, one of expired and the devices think that Engineering window. Depending on the
these situations occurs: they have lost connection to the Profibus and Ovation traffic (number of
 Bus fault lights illuminate bus. modules, segments, devices, and I/O), a
on Profibus devices. failover takes anywhere from 100ms to
400ms. It is recommended that the
 Points go into bad Profibus network watchdog time be set to
quality. at least 1,000 ms.
The module failed An internal fault caused a module Reboot the module (remove and
(general). to fail. reinstall). If the problem persists with this
module, it is possible the hardware is
bad.
All devices on a simplex Profibus lost communication with Check that the cabling on the failed
segment go into alarm the segment. segment is intact and connections are
properly secured.
A redundant module failed Profibus lost communication with Check that the cabling on the failed
over due to a an entire segment (indicated by segment is intact and connections are
communication fault on a bits 8 and 9 in the node record). properly secured. Reboot the module
segment. (remove and reinstall).
6.1.1 To troubleshoot using the module and node records

1. Access Point Information from your Ovation Applications folder at the Operator Station to view
the module or node record. Refer to the Operator Station User Guide for more information
about the Point Information function.
2. Navigate to the Value/Status tab in the module or node record (the value used for the module
and node record is the A2 field).
3. Review the collected bit information about the module or node.
6.1.2 Module record information
The Profibus-related module record values are:
MODULE R E C O R D ( A2 FIELD) DESCRIPTION

BIT
0 Module configured on the bus.
1 (Not applicable)
2 Redundant Indication
0 = Simplex module
1 = Redundant (Module acknowledges redundancy)
3 (Not applicable)
4 (Not applicable)
5 Internal Module Fault (Failover Request)
86 OW350_36
MODULE R E C O R D ( A2 FIELD) DESCRIPTION

BIT
6 Bus Communication Status (Segment 1)
7 Bus Communication Status (Segment 2)
8,9 Segment 1 Operating Mode (00 = Off, 01 = Primary, 10 = Backup)
10,11 Segment 2 Operating Mode (00 = Off, 01 = Primary, 10 = Backup)
12 (Not applicable)
13 (Not applicable)
14 System Up
15 (Not applicable)
Each nibble (4-bits) can be analyzed to determine the operating state of the module. The
following is an example of a status value for a redundant module:
Figure 67: Status value diagram
Typically, for a non-redundant (simplex) module, the status value should equal something like
0x45C1 (assuming both segments are in use). For a redundant module typical status values
would be 0x45C5 (redundant, online, both segments communicating) for the in control module
and 0x4AC5 for the backup. The second nibble (which includes bits 6 and 7) indicates the
communication status of each segment. If only one segment is configured, only the bit
corresponding to that segment (bit 6 if segment 1 and bit 7 for segment 2) is considered by the
Controller in evaluating the overall module health.
OW350_36 87
6.1.3 Simplex module information
Simplex modules refer to non-redundant Profibus modules. The only valid operating states are
online and off (no backup).
In the following tables, if a value is indicated by “X” it means the exact value is not important for
the purpose of describing that case. Common record values for a simplex module are:
PRIMARY DESCRIPTION
VALUE
0x45C1 The module is healthy and running and has control of the Profibus network. Both
segments are healthy and should be communicating.
0x4001 The module is configured but both segments are in the off mode. It is possible that the
module has either failed (for example, lost communication to a segment) or is in the
process of booting up.
0xXAXX The module is operating in backup mode. This should never occur for a simplex
module. If this does occur for a simplex module, check the configuration of the module
and reboot the module.
0xXXX5 The module is configured as redundant.
0xXXX4 In this case, the module is configured as redundant but is not attached to the bus. Verify
the module configuration and reboot the module.
88 OW350_36
6.1.4 Redundant module information
In the following tables, if a value is indicated by “X” it means the exact value is not important for
the purpose of describing that case. Redundant modules operate as part of a pair. Their operating
state can be Off, Control, or Backup.
Common record values for a redundant module pair are:
PRIMARY SECONDARY DESCRIPTION

VALUE VALUE
0x45C5 0x4AC5 Both modules are running and healthy. The primary module is in control.
The secondary module is in backup.
0xX5XX 0xX5XX Both modules are in control. This causes faults on the Profibus network.
Devices on the Profibus network will begin to go from configured
(healthy) to unconfigured (unhealthy). This also causes the segment and
device node records to go into and out of bad quality (along with the
points associated with those segments/devices).
Reboot the Profibus modules.
0xXAXX 0xXAXX Both modules are in backup. No I/O can be exchanged. Reboot both
modules.
0xXXX1 0xXXXX There is a configuration error. The module is expected to be redundant
but the redundant bit (bit 2 of the module record) is not set. Check the
module configuration. Clear and reload the Controller. If the problem
persists, reboot the module (remove and reinstall).
0xXXXX 0xXXX1 There is a configuration error. The module is expected to be redundant
but the redundant bit (bit 2 of the module record) is not set. Check the
module configuration. Clear and reload the Controller. If the problem
persists, reboot the module (remove and reinstall).
0xX6XX 0xXXXX There is a mismatch in the segment operating state. If both segments are
in use, the operating mode of both segments should be the same (both
0xX9XX backup or both control).
Reboot the module (remove and reinstall). If the problem persists, reboot
both modules.
0xXXXX 0xX6XX There is a mismatch in the segment operating state. If both segments are
in use, the operating mode of both segments should be the same (both
0xX9XX backup or both control).
Reboot the module (remove and reinstall). If the problem persists, reboot
both modules.
0xX100 0xXXXX Only one segment is in control or backup and the other is in the off state.
If the segment is not in use, it should be in the off state. If a segment is
0xX200 off but is in use and the other segment is in control or backup, then there
0xX400 is an error. Reboot the modules and the Controller.
0xX800
0xXXXX 0xX100 Only one segment is in control or backup and the other is in the off state.
If the segment is not in use, it should be in the off state. If a segment is
0xX200 off but is in use and the other segment is in control or backup, then there
0xX400 is an error. Reboot the modules and the Controller.
0xX800
OW350_36 89
6.1.5 Node record information
You can use the segment node records and the device node records to troubleshoot. Module bits
for each record type and their descriptions are listed in the following table:
Note: The items in bold only apply to Ports configured for Profibus Port redundancy and are not
used for Module redundancy or regular simplex Profibus configuration.
Segment/Port Node Record Bit Definitions
BIT ALARM DESCRIPTION SET RESET NOTES

STATE
0 REDUND CHA 1 0 Profibus Only. Port is part

of redundant pair (Channel
A).
1 REDUND CHB 1 0 Profibus Only. Port is part
of redundant pair (Channel
B).
2 0 PORT STATUS NORMAL ALARM
3 RDP STATUS ON OFF

4 0 MODULE STATUS NORMAL ALARM
5 OP MODE 00-OFF 1 0
01-CTRL 10-BK
6 OP MODE 00-OFF 1 0
01-CTRL 10-BK
7 1 FAIL 00-NO 01-P1 1 0 Profibus only.
10-P2 11-GEN
8 1 FAIL 00-NO 01-P1 1 0 Profibus only.
10-P2 11-GEN
9
10 CONTROL TASK 1 0 0-based same as in RM
IDX (BIT 0) record.
IDX (BIT 1) record.
IDX (BIT 2) record.
13
14 1 BKP LOST COMM 1 0 Profibus Only
TO MASTER
15 FAILOVER IN YES NO Profibus only (NOT alarmed
PROGRESS as in previous version).
90 OW350_36
When a segment record goes into bad quality (point is not functioning properly), all of the devices
and I/O points assigned to the segment also go into bad quality. The segment record goes into
bad quality when Bit 4 is clear.
Note: The items in bold only apply to Ports configured for Profibus Port redundancy and are not
used for Module redundancy or regular simplex Profibus configuration.
Device Node Record Bit Definitions

STATE
0 0 DEVICE YES NO For redundant ports, applies

CONFIGURED to Channel A or Channel B
as indicated by bits 14 and
15.
1 0 DEVICE STATE NORMAL ALARM For redundant ports, applies

to Channel A or Channel B
15.
2 ADDITIONAL DIAG YES NO For redundant ports, applies

STATUS to Channel A or Channel B
15.
3 0 PORT STATUS NORMAL ALARM For redundant ports, applies
to Channel A or Channel B
15.
4
5
6 PORT 1 YES NO
7 PORT 2 YES NO
8
9 DEVICE YES NO Profibus only. For
CONFIGURED redundant ports, applies to
Channel A or Channel B as
indicated by bits 14 and
15.
10 DEVICE STATE NORMAL ALARM Profibus only. For
redundant ports, applies to
15.
11 ADDITIONAL YES NO Profibus only. For
DIAG STATUS redundant ports, applies to
15.
OW350_36 91

STATE
0 0 DEVICE YES NO For redundant ports, applies

CONFIGURED to Channel A or Channel B
15.
12 PORT STATUS NORMAL ALARM Profibus only. For

redundant ports, applies to
15.
13 PORT REDUND YES NO Profibus only. Indicates if
the device is part of a
redundant pair. Profibus
port redundancy only.
14 CH A Used YES NO Profibus only. Indicates
the data from Channel A
being written to the
Ovation network. This
follows the same logic as
presented in the Ovation
Native Profibus Port
Redundancy. For more
information refer to:
Ovation Native Profibus Port
Redundancy. (see page 117)
15 CH B Used YES NO Profibus only. Indicates
the data from Channel A
being written to the
Ovation network. This
follows the same logic as
presented in the Ovation
Native Profibus Port
Redundancy. For more
information refer to:
Ovation Native Profibus Port
Redundancy. (see page 117)
When a device record goes into bad quality, all of the points assigned to the device also go into
bad quality. A module is considered to be in bad quality in the following cases:
 Bit 0 clear (the device is not configured on the Profibus network).
 Bit 1 clear (the device state is bad on the Profibus network).
 Bit 3 clear (the associated segment is in a bad state).
Bit 2 is an indication that additional diagnostics are available. It is not an indication of health or
status of a device. Typically, this bit is set. However, if it is not set, it does not indicate an issue
with the device.
92 OW350_36
6.2 What is the best way to troubleshoot redundant module pairs?
6.2 What is the best way to troubleshoot redundant module pairs?
The following tables describe common operating scenarios and failures for a redundant Profibus
module pair. The operating state for the primary and secondary modules are included along with
the corresponding RM record status values (A2 field).
It is important to remember that once a module fails over, it stays failed until it is rebooted. Before
rebooting a failed module, you should investigate the cause of the problem and correct the
problem. A failover can only occur to a healthy backup module. Paying attention to the status
values in the port node (RN) records and the module (RM) records should help narrow down the
cause of a failover.
Scenario 1: Loss and restoration of communication to segment 1 (assuming both

segments are in use)
In this scenario, communication is lost to a port. This situation could be caused by either a failure
of the module hardware associated with the port or, more likely, a cable failure (for example, if a
cable is removed). Once communication is lost to a segment, the module remains in a
communication failure state until the module is rebooted.
ACTION PRIMARY SECONDARY DESCRIPTION

MODULE MODULE
STATE STATE
No fault Control Backup Everything is working properly - one module is

(0x45C5) (0x4AC5) operating in control and the other is in backup.
Loss of Comm Fail Control When communication is lost to port 1, and there
communication (0x4005) (0x45C5) is a healthy backup module, the controller fails
on port 1 (for over. The secondary module is now in control
example, a cable and the primary is in a communication fail state.
pulled from The port node The port node record for the primary module port
primary module record will be 1 is in alarm and indicated a failure on port one
port 1) in alarm. (bits 7 and 8 = 01).
Loss of Comm Fail Control No failover occurs because there is not a healthy
communication (0x4005) (0x4585) backup. The Comm 1 ok bit is clear in the
on port 1 of the Secondary RM record status. All of the points on
secondary (for the port will be in bad quality and stop updating.
example, cable
pulled )
Communication Comm Fail Control The Comm ok bit returns. With communication
restored on port 1 (0x4005) (0x45C5) restored, the points associated with the port will
of the secondary no longer be in bad quality. The primary module
still remains failed.
Reboot primary Backup Control The primary module will bootup in backup
module (0x4AC5) (0x45C5) whether or not the cable has been reinstalled. It
is critical when rebooting a module to
troubleshoot and fix the issue that caused the
problem.
OW350_36 93
6.3 Troubleshooting the bus using the LEDs
Scenario 2: Sudden loss of the in-control module (assuming both segments are in use)
In this scenario, the primary module is removed and a failover occurs to the secondary. The
secondary module is now in control but cannot failover until the primary is reinstalled and enters
the backup operating state.
ACTION PRIMARY SECONDARY DESCRIPTION

MODULE MODULE
STATE STATE
No fault Control Backup Everything is working properly - one module is

(0x45C5) (0x4AC5) operating in control and the other is in backup.
Sudden loss of No module Control Module failover occurs (100ms to 400ms) and
the in-control (0x0) (0x45C5) the secondary module takes control.
module (for
example, removal
of the primary
module)
Loss of No module Control There is a communication failure on the
communication (0x0) (0x4585) secondary module.
on Port 1 of the
secondary Because there is no healthy backup, the module
module cannot failover.
Because communication was lost, all points
assigned to Port 1 will go into alarm.
Primary module Backup Control Primary module reboots, sees its partner is in
reboots (0x4AC5) (0x45C5) control, and goes into backup.
6.3 Troubleshooting the bus using the LEDs
You can examine the physical LED lights on the front of the bus module. The module displays
seven LEDs (on the right side, from top to bottom, position 6-12):
 ACT: lights when the card is on.
 FDX: lights when the Ethernet is on.
 S4: lights when the backup bus module is detecting activity on the bus.
 S3: lights when the backup bus module is detecting activity on the bus.
 S2: lights when the module is active and running.
 S1: lights when the Controller is actively exchanging information with the bus module.
 S0: lights when the Controller is actively exchanging information with the bus module.
6.4 Resolving a slave alarm
If a slave device detects an abnormal situation, it can raise a high priority alarm.
There are two different information bits that the slave device can communicate for diagnostic
purposes: slave configured and slave active bits. You can implement a monitoring scheme to
compare these values and alert you to potential problems.
94 OW350_36
6.5 Investigating a Profibus fault code
6.5 Investigating a Profibus fault code
Profibus generates fault codes and error messages, which are reported to the Error Log and the
System Status diagram. Error codes and messages can be used to diagnose drop and system
problems.
Some error messages may contain a series of hex numbers. These are typically Fault Codes from
the Controller and have the following format:
<Fault Code>: <Fault ID>: <Fault Parameter1>... <Fault Parameter5>.
Profibus uses the Fault Code - 66, Fault ID - B.

You can diagnose most Fault Codes that appear by accessing the System Viewer application. For
more information on fault codes for the 3.5 release, please refer to the Ovation Operator Station
User Guide.
OW350_36 95
S E C T I O N 7
7 Bus Diagnostic Diagrams
IN THIS SECTION
What are Ovation Bus Diagnostics? ................................................................................. 97

What is the Ovation Bus Diagnostics Generation tool? .................................................... 97
What is the Device Status Display? ................................................................................ 106
7.1 What are Ovation Bus Diagnostics?

The Ovation Bus Diagnostics package is a set of graphics that are automatically generated by the
Ovation Bus Diagnostics Generation tool. These graphics include status information for
components at all levels of the bus, controller status, I/O module status, segment status, and
individual device status for bus technologies. The Bus Diagnostics graphics cover Foundation
Fieldbus, Profibus and DeviceNet bus technologies and are presented in a way that makes sense
for each bus technology. These graphics are a nice way to view all bus related data in a single
place, with an easy to navigate system.
Because bus technologies are different, you may notice that the diagnostic screens for each bus
technology are different. Ovation Bus Diagnostic graphics for Foundation Fieldbus segments
include the ability to view all the way down to the function blocks and allow you to view function
block data as well as change function block modes. Ovation Bus Diagnostic graphics for Profibus
and DeviceNet segments include the ability to view all the way down to the process data. The
lowest level graphic displays all the process data for a given device on the bus.
The Ovation Bus Diagnostic graphics are a set of graphics that can be used during startup and
commissioning to monitor the status of bus devices, segments, ports, and modules all in one
place. This is intended to help speed up commissioning and aid in device troubleshooting.
If devices are added or removed from the system, it is your responsibility to regenerate and re-
download the graphics.
7.2 What is the Ovation Bus Diagnostics Generation tool?
The Ovation Bus Diagnostics Generation tool is used to automatically generate Bus Diagnostics
diagrams. This tool is part of the Ovation Utilities and can be accessed via the start menu. This
tool mines the database for bus related objects (modules, ports, devices) and compiles the
graphics based on user input and the results of the data mined from the Ovation database. The
graphics can then be linked to the system status display for easy access during commissioning
and startup.
OW350_36 97
7.2.1 To access the Ovation Bus Diagnostics Generation program

1. Select Start -> Ovation -> Ovation Utilities -> Bus Graphics.
2. The Ovation Bus Diagnostics Generation program is launched and the Ovation Bus Graphics
Generator window appears.
Figure 68: Ovation Bus Graphics Generator
3. The program reads in the Ovation database, and estimates the number of files that will be
generated. These steps can take a second to a few minutes, depending on the size of your
database. The buttons in this window are defined in the following topic: What are the Ovation
Bus Diagnostics Generator window fields (see page 101).
Note: The program compares the data against what is configured in the database. The Bus
Diagnostics program does not look up references in the Control Builder.
98 OW350_36
7.2.2 To create diagrams using the Ovation Bus Diagnostics Generation program
The Ovation Bus Graphics Generator setup window allows you to customize the diagrams. You
can define where the files are created, the diagram background color, diagram title colors, alarm
colors, and control colors.
1. Click Setup to set configuration.
Figure 69: Ovation Bus Graphics Generator - setup
OW350_36 99
2. Click on the rectangle button next to a color selection to display the Color Selector window.
You can select different foreground and background colors from this window.
Figure 70: Color Selector window
3. Click the rectangle ... button next to the path fields to browse.
100 OW350_36
4. You can choose a different directory to save your graphics.
Figure 71: Browse window
5. Click Save Configuration to save your configuration changes.

6. Click Reload Configuration to abandon the changes you have made to the configuration and
reload the existing configuration. Since reloading will remove all changes, a message box
displays to verify this choice.
7.2.3 What are the Ovation Bus Diagnostics Generator window fields?
Ovation Bus Diagnostics Generator window field descriptions
ITEM SETTINGS
General Displays the program revision number and the XML revision number.
Setup This tab displays the estimated number of files, as well as configurable information.
This form is divided into the Files section and Color and Blink Configuration section.
Files
Estimated Number When the program was first invoked, the program estimated the number of files that
of Files to be would be generated. These estimates cannot be changed. The files are automatically
Generated named and generated and these file names cannot be changed.
Note: This program does not check to see if the files already exist in the Ovation
Developer Studio. It is your responsibility to make sure these files do not already
exist in the studio. Emerson recommends that you import these files with the "prompt
the user" option to not overwrite existing files.
OW350_36 101
ITEM SETTINGS
Paths The default paths are:

 C:\Ovation\BusGraphics\diagrams for main screens and windows, and
 C:\Ovation\BusGraphics\macros for macros.
You can change the folder names by either directly typing into the text-box or
by clicking Folder Browser.
Note: The path must exist before changes are saved.
Color and Blink configuration

Device Status and  Diagram background color - this is the diagram background color of the diagrams
Drop Interface and windows.
 Title background color - this is the background color of the title bar.
 Title foreground color - this is the foreground color of the title bar.
Foundation  Title background color - this is the background color of the title bar.
Fieldbus  Title foreground color - this is the foreground color of the title bar.
Devicenet  Title background color - this is the background color of the title bar.
 Title foreground color - this is the foreground color of the title bar.
Alarm  Normal color - this is the color of normal status.
 Alarm color - this is the color of the alarm state.
 Alarm blink status - this is the alarm blink state.
Control These colors are used on the Fieldbus Window diagram. They are used as the
control button colors.
 Auto background and foreground color.
 Manual background and foreground color.
 Cascade background and foreground color.
Save Click Save Configuration for system to read the configuration from the form after
Configuration checking is complete. Error checking includes:
 Missing or non-existent main path.
 Missing of non-existent macro path.
 Blink state something other than on or off.
 All of the colors must be in the registry.
Reload Click Reload Configuration to abandon the changes you have made to the
Configuration configuration and reload the existing configuration. Since reloading will remove all
changes, a message box displays to verify this choice.
Note: You will not be able to move from this form if there is an error in any of the
entries, or if you have made changes and had not saved them.
Create Click Create to display your choices for the Files section and Color and Blink
Configuration section. These are the parameters that are used to generate the new
files. A Create Files button is at the bottom of the form.
102 OW350_36
7.2.4 To Generate the Graphic files

1. Click Create to create the graphics.
2. A preview of the current configuration settings are shown below.
Figure 72: Create files
3. To generate the graphics files, click Create Files at the bottom of the window. This will take a
few seconds to a few minutes depending on the number of files to be created. Progress and
error messages are displayed in the message box.
4. When the creation is completed, the list-box should contain:
 Starting to create the Bus Graphics Files date time
 Step 1 of 5 completed
OW350_36 103
 Device Status Display Mainscreen is MAIN_BUS_DEVICE_STATUS.SRC
 Finishing creating the Bus Graphics Files
See the following figure.
Figure 73: Ovation Bus Graphics Generator - Finished creating the Bus Graphics Files
104 OW350_36
7.2.5 To import the graphics into the Developer Studio

1. In the Ovation Developer Studio, highlight Graphics under the system tree.
2. Select Import menu item from the Operation drop-down menu, and . The Import Graphics
window displays.
3. For more information on importing graphics, refer to: Ovation Graphics Builder User Guide.
Note: Graphics must be imported, compiled, and downloaded before they can be viewed. Refer
to: Ovation Developer Studio User Guide for information on downloading. This program does
not check to see if the files already exist in the Ovation Developer Studio. It is your responsibility
to make sure these files do not already exist in the studio. Emerson recommends that you
import these files with the "prompt the user" option to not overwrite existing files.
OW350_36 105
7.3 What is the Device Status Display?
7.2.6 To access the Bus Diagnostics Graphics from Ovation
The master Bus Diagnostics diagram is titled Device Status Display and is the first diagram
created. Use the Ovation Graphics application to access this diagram.
1. Open the Ovation Applications folder at the Operator Station click the Graphics icon.
OR
If the Graphics application is already running, double click on the Graphics icon located on
the system tray.
OR
Select Start -> Ovation -> Ovation Applications -> Graphics.
Refer to Ovation Operator Station User Guide for a detailed explanation of the Graphics
application.
2. To display a diagram in the window, select a diagram name from one of the following sources:
 Load Diagram icon on the toolbar.
 Ovation Keyboard (Custom Key).
 Favorites menu
Note: The first bus graphic is called MAIN_BUS_DEVICE_STATUS.
3. You can access additional graphics from poke fields in the diagrams. These graphics appear
in pop-up main-screens and windows. By default, only one pop-up window at a time can
remain open for a diagram. If you want to open more than one pop-up window at a time for a
graphic, you must configure this feature as described in Ovation Operator Station
Configuration Guide.
7.3 What is the Device Status Displa y?

1. The master diagram is titled Device Status Display and is the first diagram created.
2. The Device Status display diagram contains a controller display for each controller that
contains a Fieldbus, Profibus DP, or DeviceNet device.
Figure 74: Device Status Display window
106 OW350_36
Device Status Display window descriptions
ITEM DESCRIPTION
Module Status The Module Status display is the indicator of all the Fieldbus, Profibus DP, and
DeviceNet modules.
 If the status is normal, the normal color displays.
 If the status is not normal, the alarm color and blink will display.
Port Status The Port Status display is the indicator of all of the Fieldbus, Profibus DP, and
DeviceNet ports.
 If the status is normal, the normal color displays.
 If any of the statuses are not normal, the alarm color and blink will display.
Device Status The Fieldbus, Profibus DP, and DeviceNet device status display is the indicator of
all of the ports of the devices.
 If any of the devices are in alarm, this will display alarm color and blink.
Controller Colors  Primary mode: Green

 Backup mode: Yellow
 Off network: Chocolate
 Standby: Cyan
 Alarm/fault: Red
 Failed: Orange
 Operator attention: Magenta
 Offline mode: Ivory3
3. Select View -> Display Pokes to view the poke fields.
4. There is a poke to take you to the Drop Interface window and poke fields for the
Primary/Backup Controllers.
5. Right-click on the poke to display the right-click menu. Click Point Information to access the
Point Information application.
7.3.1 Drop Interface window

1. Click on a port poke field to display the Fieldbus Mainscreen (see page 108), ProfibusDP
Mainscreen (see page 111) and DeviceNet Mainscreen (see page 113)
 Mod Type RPB and RFB, branch 1 and 2 can have redundant modules.
 Branch 3 and 4 can have redundant modules.
 When you see two numbers for the slot, the first number is the current slot number and
the second number is the slot number on the other branch. For example: branch 1, slot
1/8 is redundant with branch 2, slot 8/1.
2. Right-click on the Module or Port to display a right-click menu. Select Point Information to
access the Point Information application.
OW350_36 107
Note: You can press the navigation button to toggle back and forth between the Device Status
Display and Drop Interface displays.
Figure 75: Drop Interface window
Note: If there was another interface defined, you would see a >> poke field below the Mode
legend. Press the arrow poke to jump to another interface.
Drop Interface window descriptions
ITEM DESCRIPTION
Mod  Type: PB, RPB, FB, DN, RFB

 Status: Status of the module. Alarm color or non-alarm color.
Port  Status: Status of the port.
 Mode: Backup, Control, Off, Communications
 Device: An indicator of all of the devices. If any of the devices are in alarm, this
displays its alarm color and blink.
108 OW350_36
7.3.2 Foundation Fieldbus Main window

1. Access the Drop Interface Display diagram; select a FB or RFB port.
2. The Fieldbus Main window appears. Each block on the window represents a device.
Figure 76: Foundation Fieldbus Main window
The following table defines the fields in the sample Foundation Fieldbus Main window shown
above.
Foundation Fieldbus Main
ITEM DESCRIPTION
D25C1P13051-1 Device Name
D25C1P12051-1DIAG Ovation point name and poke field.

Right-click on the dark gray box to access the right-click menu. Select Point
Information to access the Point Information application.
RN Pt English description.
Commissioned  Displayed as a symbol.
 Commissioned or Decommissioned
OW350_36 109
ITEM DESCRIPTION
Alert Status  Displayed as a symbol.

 Failed/Abnormal Alert
 Communications Alert
 Maintenance Alert
 Advisory Alert
Device Status A2 field as Hex value and individual bits.
3. Click Device Status Display to display the Device Status Display diagram.
4. Click Drop Interface Display button to display the Drop Interface Display diagram.
5. Click Device Details to display the Fieldbus window.
7.3.3 To access the Foundation Fieldbus window

1. From the Fieldbus Main window, click on device Details.
2. The Foundation Fieldbus Device Details Window appears. Only the linked points are
displayed in the function blocks.
Figure 77: Foundation Fieldbus window
This window provides the following diagnostic information:

 Identifies the drop number, interface number, branch number, slot number, module name,
port number, device name, device type, device manufacturer, and device revision.
 Identifies all of the function blocks, function block type and function block mode.
110 OW350_36
To change mode
1. Select a function block to change the mode. The selected block is highlighted.
Note: The current mode will be grayed out in the control section (for example, if you are in auto,
auto will not be one of the choices). If another function block is selected for control, you must
clear control before a new function block is selected.
2. Choose the mode:

 Auto
 Man
 Casc
3. The clear control button de-selects the selected box and the control is grayed out.
4. Click Close Window to close the window.
7.3.4 Profibus Main window

1. Access the Drop Interface Display diagram; select a PB or RPB port.
2. The ProfibusDP main window appears. If RPB is selected, Control and Backup Port Modes
are available.
Figure 78: Redundant Profibus Main window
OW350_36 111
The following table defines the fields in the sample Redundant Profibus Main or Profibus Main.
Profibus Main/Redundant Profibus Main window
ITEM DESCRIPTION
Control/Backup Port mode.

Branch Branch number.
Slot Slot number.
Module Module point name and English description.
Port Port number, point name and English description.
Symbolic Name  Displayed on the first line of the block.
 In the example above, CB_AB32-DPS.
Device Name  Displayed on the second line of the block.
 Name of the device.
Station ID  Displayed on the third line of the block.
 In the example above, Station 5
Device Node Point Name  Displayed on the fourth line of the block.
 The device node point name.
Device Node Point English Description  Displayed on the fifth line of the function block.
 Device node point English description.
Device Status  Displayed on the last line of the block.

 Status is green when normal, or the alarm color when in
alarm.
 ADD DIAGS - The device node record (A2 field) where 2 =
indicates additional diagnostics are available.
 Status is displayed as a HEX value.
112 OW350_36
This window contains the following diagnostic information:

 Identifies the drop number, interface number, branch number, slot number, module, and port
number.
 Device Status Display displays the Device Status Display diagram.
 Drop Interface Display displays the Drop Interface Display diagram.
 Details displays the Profibus Window.
Figure 79: Profibus Main window

 Displays the drop number, interface number, branch number, slot number, module name, port
number, device name, device type, device vendor, and device revision.
 Click Close window to close the window.
 Displays multiple pages of signal information. There is a next and previous button that
appears on the bottom of the window when all of the information cannot fit on the screen.
 Each valid entry on the window has a poke field. Right-click on the poke field to display the
right-click menu. Click Point Information to access the Point Information application.
OW350_36 113
7.3.5 DeviceNet Main window

1. Access the Drop Interface Display diagram, select a DeviceNet port.
2. The DeviceNet Mainscreen appears.
Figure 800: DeviceNet Main window
114 OW350_36

 Identifies the drop number, interface number, branch number, slot number, module, and port
number.
 Right-click on module point, port point and device point to display the right-click menu. Click
Point Information to access the Point Information application.
 Click Details to display the DeviceNet window.
Profibus Main/Redundant Profibus Main window
ITEM DESCRIPTION
Symbolic Name  Displayed on the first line of the block.

Device Name  Displayed on the second line of the block.
 Name of the device.
Station ID  Displayed on the third line of the block.
 In the example above, Station 5
Device Node Point Name  Displayed on the fourth line of the block.
 The device node point name.
Device Node Point English Description  Displayed on the fifth line of the function block.
 Device node point English description.
Device Status  Displayed on the last line of the block.

 Status is green when normal, or the alarm color when in alarm.
 ADD DIAGS - The device node record (A2 field) where 2 =
indicates additional diagnostics are available.
 Status is displayed as a HEX value.
OW350_36 115
7.3.6 To access the DeviceNet window

1. From the DeviceNet Main screen, click Details.
2. The DeviceNet Window appears. Only the linked points are displayed in the function blocks.
Figure 81: DeviceNet Window

 Displays the drop number, interface number, branch number, slot number, module name, port
number, device name, device type, device vendor, and device revision.
 Click Close window to close the window.
 Displays multiple pages of signal information. There is a next and previous button that
appears on the bottom of the window when all of the information cannot fit on the screen.
 Each valid entry on the window has a poke field. Right-click on the poke field to display the
right-click menu. Click Point Information to access the Point Information application.
116 OW350_36
A P P E N D I X A
A Appendix: Ovation Native Profibus Port Redundancy
A.1 Port Redundanc y General Guidelines
Ovation Port Redundancy implements a form of Profibus System Redundancy (SR) providing
Profibus master, physical layer media, and slave channels redundancy.
Ovation Native Profibus Port Redundancy allows you to pair simplex Ovation Native Profibus
ports for redundant operation. This allows you to configure a single channel, assign a single set of
device node record and I/O points to a redundant pair and still get port redundant Profibus
operation.
A.1.1 Basic Operation
Use the following guidelines to implement Ovation Profibus Port Redundancy:

 Any two Ovation Native Profibus ports on the same controller can be paired for redundant
operation (this includes ports on the same module). This differs from the existing Ovation
Native Profibus module redundancy solution, where redundant modules need to be
configured on adjacent branches.
 Each Ovation Profibus port has a mode designating it as either Stand-alone, Channel A, or
Channel B. Ports for pairing must be designated as either Channel A or Channel B. The
default mode for each port is stand-alone (simplex).
 Only one set of I/O points and device node records is assigned for each redundant pair. The
Ovation Profibus driver internally tracks the status and values of the individual channels and
writes to the set of node records and I/O points for the pair. The redundancy logic is applied
on a slave-by-slave basis as follows:
Port Redundancy Logic
CH. A CH. B WRITE USES INPUTS STATUS VALUE POINT

STATUS STATUS OUTPUT TO FROM TO WRITE TO QUALITY
CHANNEL CHANNEL NODE RECORD
OK OK Both Channel A Channel A GOOD
OK BAD Both Channel A Channel A GOOD

BAD OK Both Channel B Channel B GOOD
BAD BAD Both Channel A Channel A BAD
OW350_36 117
A.1 Port Redundancy General Guidelines
Where:
Port Redundancy Logic
PORT REDUNDANCY DESCRIPTION

LOGIC
Channel A Status Indicates whether or not the node record is in alarm. If the node record is
not in alarm the status will be OK. For more information refer to the device
node record table (see page 90).
The Channel A device status is indicated from the Profibus master.
Channel B Status Indicates whether or not the node record is in alarm. If the node record is
not in alarm the status will be OK. For more information refer to the device
node record table. (see page 90)
The Channel B device status is indicated from the Profibus master.
Write Output to Channel Indicates to which channels the driver writes the outputs. For this type of
redundancy, the slaves are responsible for applying the proper outputs. As
a result, the driver sends outputs to both channels.
Uses Inputs from Indicates which channel’s input the driver uses.
Channel
Status Value to Write to Indicates which channel’s inputs were used. Users can add this information
Node Record to graphics or control.
Point Quality Indicates the quality that is assigned to the inputs and outputs.
 Only stand-alone and Channel A ports can be engineered in Ovation. For redundant ports,
Ovation automatically applies the configuration to Channel B (transparent to the user). This is
similar in concept to how the existing redundant Ovation Profibus module redundancy is
handled (where the user is only able to engineer the primary module ports).
 A module point will need to be assigned to each Native Profibus module and a node record
will be assigned to each port of a redundant pair. Additional bits have been added to the
Ovation Profibus port node records (RN) to indicate port redundancy status.
 Since up to 18 Native Profibus modules are supported per Ovation Controller, up to 36 pairs
of redundant ports will be supported.
 Ovation Port Redundancy can be thought of as two identical Native Profibus networks. As a
result, the same parameters and constraints will apply. The solution will support up to 3584
bytes of input data and 3584 bytes of output data per port pair.
 Ovation Developer Studio will not allow a drop load if there are any (non-stand-alone) un-
coupled ports configured on the drop.
 Ovation Profibus Port Redundancy is evaluated per device not on per channel basis. For a
given network, it is possible to have some devices with a healthy Channel A and others with a
healthy Channel B.
118 OW350_36
A.1 Port Redundancy General Guidelines
A.1.2 Restrictions
 Ovation Port redundancy is not supported with Ovation Module Redundancy. The Ovation
Developer Studio does not allow you to configure port redundancy on Ovation Native Profibus
modules configured for module redundancy.
 This is not a Profibus DP-V2 solution. Ovation does not send any commands to control slave
redundancy or read any slave specific redundancy status information. Profibus Flying
Redundancy is not supported.
 Before designating a port as Channel B, you must manually delete any existing Profibus
configuration for that port. This includes manually deleting devices from the following:
 SYCON.net engineering tool.
 Un-assigning associated I/O points.
 Un-assigning associated device node records.
 Deleting slave devices from the tree underneath the port in the Ovation Developer Studio.
A.1.3 Implementation Guidelines

 It is assumed that slaves with a dual channel interface manage their own redundancy
internally. The slaves, through the use of a RedCom channel or some other mechanism, must
determine the following:
 Which channel’s input data to use?
 Whether or not to use output identical information on both ports?, or
 Whether or not to engage in active data exchange, so Ovation knows the channel is not
primary?
 Both channels of a dual channel slave must be configured to the same slave address. This
port redundancy solution will not accommodate Flying Redundancy (where different slave
addresses are used).
 Any single channel slaves must be attached to an additional repeater/coupler/multiplexing
device, which will take both Channel A, and Channel B as inputs and output a single channel.
 Ovation Profibus Port Redundancy is applicable for Profibus networks configured identically
(same addresses, device configuration, parameter settings, and so forth). If both channels
will not be configured identically (there will be an extra device on one channel, or a device will
have different parameter settings on each of its channels), you must manually configure the
ports and the redundancy. For the port redundancy defined here, the Ovation tools will
automatically apply the configuration of one port to the partner and there will be no means
provided to add an additional device on a port.
OW350_36 119
Index
A P
Appendix Port Redundancy General Guidelines • 117
Ovation Native Profibus Port Preparing to perform network scan • 76
Redundancy • 117 Profibus and Ovation components • 3
Profibus device interoperability • 2
B Profibus devices • 4
Basic Operation • 117 Profibus hardware • 9
Bus Diagnostic Diagrams • 97 Profibus hardware and software
requirements • 12
C Profibus Main window • 111
Profibus on-line diagnostics • 71
Configuring Profibus • 13
Profibus redundancy • 6
Configuring Profibus devices for redundant
modules configurations • 42 R
Configuring Profibus devices for standard
(simplex) configurations • 13 Redundant module information • 89
Copyright Notice • 2 Requirements for a successful network scan
• 76
D Resolving a slave alarm • 94
Restrictions • 119
DeviceNet Main window • 114
Drop Interface window • 107 S
F Simplex module information • 88
Specifications - Profibus (DP) • 11
Field card diagnostic LEDs - Profibus (DP) •
11 T
Foundation Fieldbus Main window • 109
Terminal block pin assignments - Profibus
H (DP) • 9
To access Profibus online diagnostics • 71
How do I troubleshoot Profibus? • 85
To access the Bus Diagnostics Graphics
I from Ovation • 106
To access the DeviceNet window • 116
Implementation Guidelines • 119 To access the Foundation Fieldbus window •
Introduction to Ovation Profibus • 1 110
Investigating a Profibus fault code • 95 To access the Ovation Bus Diagnostics
L Generation program • 98
To access the Profibus module configuration
Logic card diagnostic LEDs - Profibus (DP) • window • 30, 57
10 To access the Profibus module engineering
window • 29, 56
M To add a module record point name • 21, 48
Module firmware • 79 To add a new I/O device number to the
Module record information • 86 Controller using the Developer Studio •
Module scan • 78 16, 45
To add a redundant module (optional) • 28,
N 55
To add new slave devices to your device
Network scan • 77
catalog • 31, 58
Network scan option • 76
To add Profibus slaves • 31, 59
Node record information • 90
OW350_36 121
Index
To assign a node record to each of your What is the Ovation Bus Diagnostics
ports • 27, 54 Generation tool? • 97
To clear the Controller • 40, 69
To configure bus parameter settings
(optional) • 35, 63
To configure points for each Profibus signal •
37, 66
To configure Profibus Port Redundancy • 23,
50
To configure Profibus slaves • 32, 60
To create a control task • 14, 43
To create a node record • 25, 52
To create diagrams using the Ovation Bus
Diagnostics Generation program • 99
To design a redundant module segment
(optional) • 58
To download module firmware • 79
To download the Controller • 39, 68
To edit a slave's station ID (optional) • 33, 61
To enable multiple control tasks • 16, 44
To Generate the Graphic files • 103
To import the graphics into the Developer
Studio • 105
To insert a Profibus I/O module for module
redundancy in the Developer Studio • 46
To insert a Profibus I/O module in the
Developer Studio • 18
To load the Controller • 41, 70
To set a module's mode as redundant • 55
To set a module's mode as simplex
(optional-- the default is simplex) • 28
To troubleshoot using the module and node
records • 86
To use Profibus on-line diagnostics to
configure a driver • 74
To use the Process Data window (optional) •
34, 62
To view the Address Table (optional) • 36,
65
Topology scan • 77
Troubleshooting Profibus • 85
Troubleshooting the bus using the LEDs • 94
W
What are device database (GSD) files? • 5
What are Ovation Bus Diagnostics? • 97
What are Profibus online diagnostics? • 71
What are the Ovation Bus Diagnostics
Generator window fields? • 101
What is a Profibus DP module? • 9
What is module firmware? • 79
What is Profibus DP? • 1
What is Profibus Port redundancy? • 8
What is the best way to troubleshoot
redundant module pairs? • 93
What is the Device Status Display? • 106
122 OW350_36

Ovation Profibus

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

Ovation Profibus

Uploaded by

Copyright:

Available Formats

Profibus User Guide for Ovation 3.

1 Introduction to Ovation Profibus 1

3.2 Configuring Profibus devices for redundant modules configurations................................ 42

4 Profibus on-line diagnostics 71

7 Bus Diagnostic Diagrams 97

A Appendix: Ovation Native Profibus Port Redundancy 117

1 Introduction to Ovation Profibus

What is Profibus DP? .......................................................................................................... 1

1.1 What is Profibus DP?

Profibus (Process Field Bus) DP (decentralized periphery) is an all-digital, two-way

1.2 What is device interoperability?

1.3 What are the Profibus and Ovation components?

Figure 1: Implementation of Profibus with Ovation

In computer networking, master/slave is a communication model where one device or process

1.4 What are Profibus devices?

There are three types of Profibus DP devices:

1.5 What are device database (GSD) files?

1.6 What is Profibus redundanc y?

Profibus redundancy is available for Ovation 3.1.1 and later releases.

Figure 2: Redundancy diagram

1.7 What is Profibus Port redundanc y?

What is a Profibus DP module? .......................................................................................... 9

2.1 What is a Profibus DP modul e?

2.1.1 Terminal block pin assignments - Profibus (DP)

 Maximum working voltage is 150 V peak DC or RMS AC.

ROW C SIGNAL NAME ROW B PIN SIGNAL NAME ROW A SIGNAL

1-3 RSV 1-3 RSV 1-3 RSV

2.1.2 Logic card diagnostic LEDs - Profibus (DP)

2.1.3 Field card diagnostic LEDs - Profibus (DP)

Field card LED indications Channels 1 and 2

LED LED STATE ME ANING

RDY (yellow) ON Device is ready.

2.1.4 Specifications - Profibus (DP)

Proper operation of a Profibus interface with an Ovation system requires:

Configuring Profibus devices for standard (simplex) configurations ................................. 13

3.1 Configuring Profibus devices for standard (simplex)

1. Create a control task. (see page 14)

22. Clear the Controller. (see page 39)

3.1.1 To create a control task

Figure 3: Insert New Control Tasks Wizard

5. Click Finish. The New Control Tasks window displays:

Figure 4: New Control Tasks window

3.1.2 To enable multiple control tasks

1. Access the Ovation Developer Studio.

3. Right-click on the Device Number.

Figure 5: Insert New Device Numbers wizard

3.1.4 To insert a Profibus I/O module in the Developer Studio

Figure 6: Insert New Ovation Module wizard

5. Select Profibus BusModule.

Figure 7: Module tab

9. Select radio button: Simplex/Port Redundancy (the standard configuration).

Figure 8: P01 and P02

3.1.5 To add a module record point name

Figure 9: Insert New Module Points wizard

4. Type a point name.

6. Click Finish. The New Module Points window appears.

Figure 10: New Module Points window

7. Navigate to the Hardware tab.

Figure 11: New Module Points Hardware tab

3.1.6 To configure Profibus Port Redundancy

Figure 12: Error message

 Only the Channel A and stand-alone ports can be configured.

Figure 13: Error Message

3.1.7 To create a node record