con_020

Redundant Modbus Interface User Guide for Ovation Windows Platform CON_020

Version 1 July 2006

Copyright Notice

Since the equipment explained in this 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 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 and WEStation are registered trademarks of Emerson Process Management. All other trademarks or registered trademarks 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: [email protected] Website: http://www.EmersonProcess.com

Contents

1 Redundant Modbus Interface 1 1.1 What is the Redundant Modbus Interface?......................................................................... 1

1.1.1 Redundant Modbus Interface Features............................................................. 1

2 Software Information 3 2.1 Software Architecture.......................................................................................................... 3

2.1.1 How is Data Transferred? ................................................................................. 3 2.2 Diagnostics.......................................................................................................................... 5

3 Hardware Information 7 3.1 Hardware Architecture ........................................................................................................ 7

3.1.1 Non-Redundant Configuration with a Directly Connected RTU........................ 8 3.1.2 Non-Redundant Configuration using a Modbus Gateway................................. 9 3.1.3 Standard Redundancy with Directly Connected RTU(s)................................. 10 3.1.4 Standard Redundancy using Modbus Gateways............................................ 11 3.1.5 Enhanced Redundancy with Directly Connected RTU(s) Configuration 1...... 12 3.1.6 Enhanced Redundancy with Directly Connected RTU(s) Configuration 2...... 13

3.2 Configuring Hardware ....................................................................................................... 14 3.2.1 Configuring Third Party Devices Overview ..................................................... 14 3.2.2 To Insert New Device Numbers ...................................................................... 14 3.2.3 To Set Redundant Modbus Device Number Parameters................................ 15 3.2.4 To Insert an RTU Device................................................................................. 16 3.2.5 To Configure the Required Attributes of the RTU Device ............................... 17 3.2.6 To Insert a Redundant Modbus Slave............................................................. 21 3.2.7 To Configure Modbus Interface Points............................................................ 25 3.2.8 I/O Access Path Examples for Redundant Modbus........................................ 29

3.3 Download, Reboot and Load............................................................................................. 29 3.3.1 To Download Controller Drop Configuration ................................................... 30 3.3.2 To Reboot a Controller Drop ........................................................................... 31 3.3.3 To Load a Controller Drop............................................................................... 32

3.4 Redundant Modbus Specification ..................................................................................... 32 3.4.1 Configuration ................................................................................................... 32

4 What are the Redundant Modbus Fault Codes? 35 4.1 Redundant Modbus Error Codes Overview ...................................................................... 35

4.1.1 Redundant I/O Error (66-B-2).......................................................................... 36 4.1.2 Datalink Errors (66-B-5) .................................................................................. 37 4.1.3 Datalink Warning (66-B-6)............................................................................... 42

CON_020 i

Table of Contents

Glossary of Terms 47

Index 69

ii CON_020

S E C T I O N 1

REDUNDANT MODBUS INTERFACE

IN THIS SECTION

What is the Redundant Modbus Interface?.........................................................................1

1.1 WHAT IS THE REDUNDANT MODBUS INTERFACE?

The Redundant Modbus interface is a communication interface designed to provide communication between Ovation Controllers and Redundant Modbus devices.

Ovation already contains a Modbus Master interface, but there are advantages to using the Redundant Modbus Interface instead of the Modbus Master Interface. The Modbus Master interface, and the Redundant Modbus interface both support input and output points. These points can be analog, digital or packed points. The Redundant Modbus interface also supports both versions of the Modbus protocol, OpenTcp Modbus and TCP/IP Modbus. Although the Modbus interfaces are similar, the Redundant Modbus interface offers three modes of redundancy, a high level of custom configurability and extensive diagnostics via node records.

1.1.1 REDUNDANT MODBUS INTERFACE FEATURES

The Redundant Modbus interface provides maximum flexibility when defining the interface. The following features help make the Redundant Modbus Interface an excellent option for your Modbus communication needs.

Three Levels of Redundancy

The Redundant Modbus interface can be configured for non-redundant, standard redundancy, or enhanced redundancy. Each configuration, provides optimal fail over to the backup Controller on communication error. This allows you flexibility when defining the interface for all types of redundancy requirements. Further explanation of each of these modes is included in How is Data Transferred? (see page 3).

User Selected Modbus Commands

The Ovation Developer Studio allows you to select the appropriate Modbus command to use when communicating with the end device. This allows greater flexibility for older or less robust systems that do not support all the possible Modbus commands.

CON_020 1

1.1 What is the Redundant Modbus Interface?

User Selected Messaging Format

You have two options when it comes to messaging format; optimal messaging and strict messaging. If optimal messaging is selected, the driver will make the most efficient messages, even if that means gathering data that is not required as part of a request. Strict messaging format will make onle messages of contiguous registers. This is another feature that helps Ovation support communication to older and less robust Modbus devices. Refer to How is Data Transferred? (see page 3) for more information.

Periodic Outputs and Outputs by Exception

The Redundant Modbus interface supports outputs by exception as well as periodic outputs. This allows you to configure the device in such a way as to not overload the end device with continuous outputs.

Support for More Connections

The Redundant Modbus interface allows you to define up to five devices as Modbus-R. Each Modbus-R device allows up to eight RTU definitions. This means that a single OCR161 Controller without any real I/O can support up to 40 individual connections while the OCR400 Controller can support up to 32 Modbus devices.

How do I Choose?

You should review the above features and determine if the Redundant Modbus is the best option for your needs. The Redundant Modbus is the recommended solution for Modbus operations in an Ovation system. The remainder of this document describes the configuration and operation of this interface.

2 CON_020

S E C T I O N 2

SOFTWARE INFORMATION

IN THIS SECTION

Software Architecture..........................................................................................................3Diagnostics..........................................................................................................................5

2.1 SOFTWARE ARCHITECTURE

The Ovation Controller provides I/O access to Redundant and Non-redundant Modbus devices through the Ovation Redundant Modbus device interface. The interface supports input and output points. An Ovation node record monitors the status of each Redundant Modbus device pair.

The Ovation Redundant Modbus interface communicates with a redundant or non-redundant Modbus RTU using either OpenModbus TCP or Modbus TCP/IP communications protocol. The Ovation Redundant Modbus Interface utilizes the existing Ovation data link device driver and API to transfer data from the Ovation Redundant Modbus Interface into process points in the Controller.

2.1.1 HOW IS DATA TRANSFERRED?

Data is transferred between Ovation and the Modbus RTU(s) using TCP/IP or OpenTCP Modbus protocol. This is a standard published protocol. You have the ability to select various items during configuration including messaging format and redundancy.

Redundant Modbus Device (RTU) Specification

You have the ability to add/insert up to eight Redundant Modbus device pairs. The attributes of these objects are viewed and modified via the Ovation Developer Studio. Refer to Configuring Hardware (see page 14) for more information.

Messaging Format

There are two types of messaging format available, optimal or strict.

WHAT IS THE OPTIMAL MESSAGING FORMAT?

If Optimal messaging format is selected, the Controller creates the most efficient Modbus messages. This means the Controller generates messages asking for up to 125 registers per request. This allows the Controller to retrieve as much data as possible per message, even if this means reading data that is not required.

CON_020 3

2.1 Software Architecture

WHAT IS THE STRICT MESSAGING FORMAT?

If strict messaging format is selected, messages are created so that the Controller will only request the data that has been configured in the point records. If strict messaging format is selected, messages are created for each set of continuous registers.

Note: You should be aware that strict messaging could increase the number of messages needed to gather all of the necessary data. This may slow down the interface, depending on your configuration.

Redundancy

There are three available Redundancy configurations:

Non-redundant Standard Redundancy Enhanced Redundancy

NON-REDUNDANT MODBUS DATA TRANSFER

A non-redundant configuration includes communication to a single Modbus RTU or Modbus gateway. Both the primary and backup Ovation Controllers communicate with the same devices.

Data is sent and received at all times from the Controller that is in control to the end device. When the Controller is in backup mode, it reads input values, but does not send output values to the device. The communication ensures a smooth transfer to the backup Controller if a failure were to occur.

A failover feature is available for this configuration. You can choose whether or not to fail the Controller on communication error. When this option is set to true, if communication is lost to any RTU, the Controller will fail over to the backup. If communication is lost while the Controller is in backup mode, the Controller will go to the failed mode.

STANDARD REDUNDANCY MODBUS DATA TRANSFER

Standard redundancy means that each Controller (primary and backup) talks to a different Modbus RTU or gateway.

Data is sent and received from the Controller that is in control at all times to the end device. When the Controller is in backup mode, it reads input values, but does not send output values to the device. The communication ensures a smooth transfer to the backup Controller if a failure were to occur.

A failover feature is available for this configuration. You can choose whether or not to fail the Controller on communication error. When this option is set to true, if communication is lost to any RTU, the Controller fails over to the backup. If communication is lost while the Controller is in backup mode, the Controller will go to failed mode.

4 CON_020

2.2 Diagnostics

ENHANCED REDUNDANCY MODBUS DATA TRANSFER

Enhanced redundancy means each Ovation Controller talks to both a primary and a backup Modbus device at all times. This redundancy is done using separate Modbus devices or separate Ethernet ports on a single Modbus device.

Note: The driver supports direct communication to a Modbus RTU. Modbus gateways are not supported for enhanced redundancy configuration.

Controllers in primary mode will read inputs and write outputs to both the designated primary and backup Modbus devices. If communication is lost with the primary Modbus device, the Ovation Controller uses data from the backup Modbus device. The internal switch over between the designated primary and backup Modbus devices will be handled similar to the way the Ovation Controller handles failovers. Once a switch between the designated primary and backup device has occurred, communication will continue in this way until the new primary device fails. You will configure the designated primary and backup Modbus devices using the Ovation Developer Studio.

During normal communication, the Ovation Controller sends outputs to both Modbus RTUs, and receives data from both Modbus RTU's, but uses the primary RTU data for points.

A failover feature is available for this configuration. You can choose whether or not to fail the Controller on communication error. When this option is set to true, if communication is lost to both devices of any enhanced redundancy pair, the Controller will fail over to the backup. If communication is lost to both Modbus devices of any enhanced redundancy pair while the Controller is in backup mode, the Controller will go to failed mode.

2.2 DIAGNOSTICS

Each node record (RN) can be defined to monitor the status of each pair of the Redundant Modbus devices. When configuring an RTU, add the desired status point name in the diagnostics/status Ovation point name field. Status information is stored in the A2 field of the node record.

Bits 0 - 7 are reserved to monitor the status of the primary Modbus RTU and bits 8 - 15 are reserved to monitor the status of the secondary Modbus RTU when configured with enhanced redundancy. The node record is configured to alarm on a true condition for bits 0, 1, 8 and 9.

For the primary slave, bits 2 - 5 represent the last Modbus exception code returned. For the partner slave, bits 10 - 13 represent the last Modbus exception code returned.

BI T ER R O R CO N DI T I O N SE T DE S C RI P T I O N

RE SE T DE S C RI P T I O N

AL AR M CO N DI T I O N

0 1 - Loss of communication with Modbus device.

ALARM NORMAL 1

1 1 - System error returned from Primary Modbus device.

ALARM NORMAL 1

2 - 5 Modbus exception code returned from device.

N/A N/A N/A

CON_020 5

2.2 Diagnostics

BI T ER R O R CO N DI T I O N SE T RE SE T AL AR M CO N DI T I O N DE S C RI P T I O N DE S C RI P T I O N

8 1 - Loss of communication with Secondary Modbus device.

ALARM NORMAL 1

9 1 - System error returned from Secondary Modbus device.

ALARM NORMAL 1

10 -13 Modbus exception code returned from device.

N/A N/A N/A

6 CON_020

S E C T I O N 3

HARDWARE INFORMATION

IN THIS SECTION

Hardware Architecture ........................................................................................................7Configuring Hardware .......................................................................................................14Download, Reboot and Load.............................................................................................29Redundant Modbus Specification .....................................................................................32

3.1 HARDWARE ARCHITECTURE

The Ovation Controller can interface to the Redundant Modbus RTU(s) through either a dedicated Ethernet interface on the Controller, or by utilizing the Ovation network.

When using a dedicated interface, a switch or hub may be required for both the primary and the backup Controllers. A maximum of eight Redundant Modbus device pairs can communicate to any single PCI device in the Ovation Controller. Up to four virtual PCI devices can be defined as Redundant Modbus.

The following drawings represent possible configurations.

CON_020 7

3.1 Hardware Architecture

3.1.1 NON-REDUNDANT CONFIGURATION WITH A DIRECTLY CONNECTED RTU

The following figure is a representation of a non-redundant Modbus RTU configuration. In this configuration, both the primary and backup Ovation Controllers communicate to a single RTU. This RTU is directly connected, therefore it is not a gateway. In this configuration, the IP address and slave number of the RTU is identical for both the primary and backup Controllers. See sections To Configure the Required Attributes of the RTU Device (see page 16) and To Insert a Redundant Modbus Slave (see page 21) for more information.

Figure 1: Non-Redundant Configuration Using a Connected RTU

8 CON_020


3.1.2 NON-REDUNDANT CONFIGURATION USING A MODBUS GATEWAY

The following figure is a representation of a non-redundant Modbus RTU gateway configuration. In this configuration, both the primary and backup Ovation Controllers communicate to the same RTU gateway. The IP address of the RTU is the same for both the primary and backup Controllers. This configuration has multiple slave objects representing each node using the appropriate slave entity defined under the RTU in the Ovation Developer Studio. See sections To Configure the Required Attributes of the RTU Device (see page 16) and To Insert a Redundant Modbus Slave (see page 21) for more information.

Figure 2: Non-Redundant Configuration using a Modbus Gateway

CON_020 9


3.1.3 STANDARD REDUNDANCY WITH DIRECTLY CONNECTED RTU(S)

The following figure is a representation of a standard redundancy Modbus RTU configuration. In this configuration, both the primary and backup Ovation Controllers communicate to separate RTUs. These RTUs are directly connected to each Controller. This means that they do not act as a gateway to other Modbus devices. In this configuration, the IP address is different for the primary and backup Controllers. The slave/node numbers may or may not be different depending on the configuration of the RTU. See sections To Configure the Required Attributes of the RTU Device (see page 16) and To Insert a Redundant Modbus Slave (see page 21) for more information.

Figure 3: Standard Configuration Using a Connected RTU

10 CON_020


3.1.4 STANDARD REDUNDANCY USING MODBUS GATEWAYS

The following figure is a representation of a standard redundancy Modbus RTU gateway configuration. In this configuration, both the primary and backup Controllers communicate to separate RTUs. These RTUs act as gateways to other modbus devices. In this configuration, the IP address is different for the primary and backup Controllers. For each RTU, there will be multiple slave entities. These slave entities are used to map points to the appropriate slave. See sections To Configure the Required Attributes of the RTU Device (see page 16) and To Insert a Redundant Modbus Slave (see page 21) for more information.

Figure 4: Standard Redundancy using Modbus Gateways

CON_020 11


3.1.5 ENHANCED REDUNDANCY WITH DIRECTLY CONNECTED RTU(S) CONFIGURATION 1

The following figure is a representation of an enhanced redundancy Modbus RTU configuration. In this configuration, both the primary and backup Ovation Controllers each communicate to two separate RTUs. These RTUs do not act as gateways to other Modbus devices. For each RTU, there will be one slave entity. See sections To Configure the Required Attributes of the RTU Device (see page 16) and To Insert a Redundant Modbus Slave (see page 21) for more information.

The Ovation Controller communicates with each of its defined RTUs all of the time. Inputs and outputs are received and sent to each RTU, however, inputs are only written to process points from the designated primary RTU. If communication is lost to the designated primary RTU, the Ovation Controller writes the point data received from the designated Backup RTU. For more details on Enhanced Redundancy, see How is Data Transferred? (see page 3)

Figure 5: Enhanced Redundancy with Directly Connected RTU(s) Configuration 1

12 CON_020


3.1.6 ENHANCED REDUNDANCY WITH DIRECTLY CONNECTED RTU(S) CONFIGURATION 2

The following figure is a representation of an enhanced redundancy Modbus RTU configuration. In this configuration, both the primary and backup Ovation Controllers each communicate to the same two RTUs. These RTUs do not act as gateways to other Modbus devices. For each RTU there is one slave entity. See sections To Configure the Required Attributes of the RTU Device (see page 16) and To Insert a Redundant Modbus Slave (see page 21) for more information.

The Ovation Controller communicates with each of its defined RTUs all of the time. Inputs and outputs are received and sent to each RTU, however, inputs are only written to process points from the designated primary RTU as defined in the configuration. If communication is lost to the designated primary RTU, the Ovation Controller writes point data received from the designated Backup RTU. For more details on Enhanced Redundancy, see How is Data Transferred? (see page 3).

Figure 6: Enhanced Redundancy with Directly Connected RTU(s) Config 2

CON_020 13

3.2 Configuring Hardware

3.2 CONFIGURING HARDWARE

3.2.1 CONFIGURING THIRD PARTY DEVICES OVERVIEW

The following is an overview of configuring a third party device:

Insert a new device number (see page 14) Set the device number parameters (see page 15) Insert the device (see page 16) Configure the device (see page 16) Configure the device interface points (see page 25) Download, reboot, and load (see page 29)

3.2.2 TO INSERT NEW DEVICE NUMBERS

1. Access the Ovation Developer Studio.

Note: The OCR400 only requires the building of one driver for all local Ovation and local Q-Line devices. The system automatically adds two local Ovation drivers and one Q-Line driver items. If remote Ovation, remote Q-Line, or extra local Q-Line devices are required, you must add a fourth driver item.

2. Use the system tree to navigate to the Device Numbers item: Systems Networks Units Drops Configuration Controller Devices Device Numbers

3. Right-click on the Device Numbers item.

4. Select Insert New from the pop-up menu. The Insert New Device Numbers Wizard appears.

Note: If you need to change a driver on a previously configured device, or anytime a new device is added, perform a clear/load function on the Controller. The Device Number represents the physical devices that can communicate with the Controller.

5. Select a number sequentially, starting at 1 to a maximum of 5. An example would be if two devices were to be configured, their device numbers would be 1 and 2, not 1 and 3 or 4 or 5.

6. Select Finish. The New Device Numbers dialog box appears showing the Controller Driver Parameters tab. See To Set Redundant Modbus Device Number Parameters (see page 15).

14 CON_020


3.2.3 TO SET REDUNDANT MODBUS DEVICE NUMBER PARAMETERS

1. Make the appropriate choices in the New Device Numbers dialog box, see the following figure and table.

Figure 7: Controller Driver Parameters (Redundant Modbus)

Controller Driver Parameters Fields (Redundant Modbus)

FI E L D DE S C RI P T I O N

I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third-party devices)

Default = Ovation

Scan Point Entries Displays the amount of points available.

Fail Controller on Error Allows you to determine if this interface can fail the Controller when an error occurs.

If False is selected, the Controller does NOT fail over to Backup when the response time limit (set in the Timeout parameter) is exceeded.

If True is selected, the Controller fails over to Backup when the response time limit (set in the Timeout parameter) is exceeded.

(False, True)

Default = True

2. Select the Ok or Apply button.

CON_020 15


3.2.4 TO INSERT AN RTU DEVICE


2. Use the system tree to navigate to the I/O Devices item: Systems Networks Units Drops I/O Devices

3. Right-click on the I/O Devices item.

4. Select Insert New from the resulting pop-up menu. The Insert New I/O Devices Wizard appears.

5. Select the I/O Device Number: OCR400 - first available (5-9) OCR161 - same as the Device number (1-4).

6. Select Modbus-R from the I/O Device Type pull-down menu.

7. Select the Finish button. The New I/O Devices dialog box appears.

Figure 8: New I/O Devices

8. Select the Apply button. Notice that the new Modbus I/O Device item now appears in the System Tree. The title of the I/O Device item contains the device number and type.

16 CON_020


3.2.5 TO CONFIGURE THE REQUIRED ATTRIBUTES OF THE RTU DEVICE


2. Use the system tree to navigate to the I/O Devices item: Systems Networks Units Drops I/O Devices

3. Right-click on the I/O Devices item.

CON_020 17


4. Choose Open. The Config tab appears for the selected device. The following figures and table explain the setting options available in this tab.

Figure 9: RTU-1 Configuration Non-Redundant

18 CON_020


Figure 10: RTU - 1 Configuration Standard Redundancy

CON_020 19


Figure 11: RTU-1 Configuration Enhanced Redundancy

RTU-1 Configuration


Identification

RTU Number This attribute can have a value of 1 through 8 and must be unique within the context of the parent Ovation I/O driver. There is no requirement that RTU numbers be sequential within the Ovation I/O driver. This value is generated by the Ovation database interface. This attribute is used to aid in associating Ovation points with the applicable Redundant Modbus device.

Name Must be unique within the context of the Ovation Controller. The valid character set consists of upper-case alphanumeric characters (A-Z and 0-9, the hyphen "-", and the underscore "_". The maximum length of this attribute is 16.

20 CON_020



Configuration

Redundancy Specifies the configuration of the device as it relates to redundancy. Refer to How is Data Transferred? (see page 3) for more information.

Non-Redundant Standard Redundancy Enhanced Redundancy

Messaging Format Specifies how the messages are formed. Refer to How is Data Transferred? (see page 3) for more information. Optimal Strict

Scan Rate (msec) Specifies the I/O scan period used for points assigned to I/O channels in this redundant device pair. Value of this attribute must be a multiple of 100 and is a minimum value of 100.

Message Timeout (msec)

Species the length of time the I/O driver interface software waits for a response from the Modbus RTU before declaring an error condition. The Ovation Controller faults or fails (based on configuration settings), and the points related to this Modbus RTU go into bad quality. Value of this attribute must be a multiple of 100 and is a minimum value of 100.

Diagnostics/Status

Ovation Point Name This field defines a node record for the purpose of providing status and diagnostic information about the Modbus RTU.

Partner/Primary Ctrl Primary/Secondary RTU

IP Address Identifies the IP address of the primary/partner half of the redundant device pair.

Communication Protocol Specifies the communication protocol employed when communicating with the device. TCP/IP Open TCP/IP

Port Number Specifies the port number to connect to (on the end device) for Modbus communications. The default is 502, but may be based on the manufacturer.

5. Make the appropriate configuration changes. Click Apply or Ok to save the changes.

3.2.6 TO INSERT A REDUNDANT MODBUS SLAVE


2. Use the system tree to navigate to the I/O Devices item: Systems Networks Units Drops I/O Devices I/O Device Modbus-R RTU Modbus Slaves

3. Right-click on the Modbus Slaves item.

CON_020 21


4. Select Insert New from the resulting pop-up menu. The Insert New Modbus Slaves Wizard appears. Choose Ok.

5. The New Modbus Slaves dialog box appears. See the following table for information about this window.

Figure 12: New Redundant Modbus Slave

22 CON_020


Figure 13: New Redundant Modbus Slave - Standard Configuration

CON_020 23


Figure 14: New Redundant Modbus Slave - Enhanced Configuration

Modbus Slaves


Slave Number Value of 1 - 255 and must be unique within the context of the parent RTU. This attribute contributes to the name of the object in the database. For example, the object slave 1 is referenced in the Developer Studio as Slave Number 1.

Primary Controller Primary Node This attribute is a value of 1-255 and represents the Modbus node. If the parent of the RTU is configured as Non-Redundant, this is the node number used by both the primary and partner Ovation Controllers. If the parent RTU is configured for Standard Redundancy, this is the node number used by the primary half of the Ovation Controller when accessing data. If the parent RTU is configured for Enhanced Redundancy, this is the node number used by the primary half of the Ovation Controller when accessing data from the Primary half of the redundant RTU.

24 CON_020



Partner Controller Primary Node This attribute (applicable if the parent RTU is configured for Standard or Enhanced Redundancy), is used to identify the node number used by the partner half of the Ovation Controller when accessing data. If the parent RTU is configured for Enhanced Redundancy, this is the number used by the partner half of the Ovation Controller when accessing data from the primary half of the redundant RTU.

Primary Controller Secondary Node This attribute (applicable only if the parent RTU is configured for Enhanced Redundancy), is used to identify the node number used by the primary half of the Ovation Controller when accessing data from the secondary half of the redundant RTU.

Partner Controller Secondary Node This attribute (applicable only if the parent RTU is configured for Enhanced Redundancy), is used to identify the node number used by the partner half of the Ovation Controller when accessing data from the secondary half of the redundant RTU.

6. Select the Apply button. Notice that the new Redundant Modbus Device item appears in the system tree. The title of the I/O Device item contains the device number and type.

3.2.7 TO CONFIGURE MODBUS INTERFACE POINTS


2. Use the following path to access the Points item: Systems Networks Units Drops Points

3. Under the Points item, select either an Analog, Digital, or Packed point to configure.

4. Right-click on the applicable Points item.

5. Select Insert New. The Insert New Points Wizard appears (where = Analog, Digital, or Packed).

6. Fill in the Point Name and Frequency (S-Slow (1 sec.), F-Fast (0.1 sec.), or A-Aperiodic (as needed).

7. Press the Finish button. The New Points dialog appears.

8. Select the Hardware tab on the New Points dialog.

9. Select third-party from the I/O Type drop down menu.

CON_020 25


10. Select Modbus-R from the I/O module pull-down menu. The New Points window appears with additional parameters, as shown below.

Figure 15: New Analog Points - Redundant Modbus

11. Complete the information in the window as it pertains to the Redundant Modbus device. The following table explains the setting options available in this window.

Hardware Tab Fields Entries - Redundant Modbus


IO type This is set to third-party to indicate a third-party point.

IO module The third-party driver is assigned a device number in the Insert New Device Numbers Wizard. This field is used to match the point with the device number.

Note: There can be no gaps in the assigned device numbers. For example, if only one PCI slot number is needed. Then device 1 is reserved for that card, and any third-party driver would be assigned as device 2 (not 3, 4, or 5).

IO channel This is disabled for Modbus R third-party points.

26 CON_020



IO task index

(Control Task)

Points are grouped by the Control task index so that they can be updated (scanned) at different rates. The Control task rate is set in the Controller Configuration Parameters dialog box.

Control Task 1 = 100 msec

Control Task 2 = 1000 msec (1 second)

Control Tasks 3, 4, and 5 are user configurable and the scan rate should be appropriate for the application and system needs.

It is recommended that third-party points be given their own task area. The scan rate should be no faster than one second because of the communication overhead.

No more than 2000 points can be assigned to a task area.

IO module units Not Applicable for this application.

IO access path This field is filled automatically from the information entered in the Hardware tab fields that are specific to Modbus R. This information may also be imported from DBID files (See Ovation Database User Guide).

RTU Device Name Name of the Redundant Modbus Device.

Slave Reference The Modbus slave number (1 to 255). This slave number corresponds to the slave number attribute

Modbus Command Read Holding Registers (RHR)

Read Input Registers (RIR)

Preset Single Register (PSR)

Read Exception Status (RES)

Preset Multiple Registers (PMR)

Preset Single Register by Exception (PSR_E)

Preset Multiple Registers by Exception (PMR_E)

Read Coil Status (RCS)

Read Input Status (RIS)

Force Single Coil (FSC)

Force Multiple Coils (FMC)

Force Single Coil by Exception (FSC_E)

Force Multiple Coils by Exception (FMC_E)

Modbus Address You enter this address. The following is an example of addresses:

40001 10001 30001 1

Note: Six digit addressing is supported by this driver.

CON_020 27



Data Type Used to interpret the data type of the RTU register (optional and not order dependent)

Unsigned Short - default - treats two consecutive bytes as a sixteen bit unsigned integer.

Signed Short - treats two consecutive bytes as a sixteen bit signed integer.

Signed Long - treats four consecutive bytes as a thirty-two bit signed integer.

Unsigned Long - treats four consecutive bytes as a thirty-two bit unsigned integer.

Float - treats four consecutive bytes as a four byte IEEE format floating point number.

Note: Signed Longs and Unsigned Longs are implemented according to the Modicon standard format.

Byte Order Key words that allow register byte order to be changed.

Swap Bytes - swap the bytes of a value before assigning it to a point.

Swap Words - swaps the words of a value before assigning it to a point.

Swap Bytes and Words- swaps both the bytes and words before assigning it to a point.

12. After completing the information in the window, select the Ok or Apply button. Continue using this procedure for each point you want to configure.

28 CON_020

3.3 Download, Reboot and Load

3.2.8 I/O ACCESS PATH EXAMPLES FOR REDUNDANT MODBUS

The following is an example of the format that is used in the Hardware tab IO access path field for a Modbus third-party point.

RMOD RTU-2 SLAVE:1 CMD:RHR MB:40555 USHORT

where:

RMOD Defines the driver.

RTU-2 Defines the RTU to associate with this point.

SLAVE:1 Defines the slave to associate with this point.

CMD:RHR Specifies the Modbus command to be used.

MB:40555 Defines the Modbus register to access.

USHORT Defines the appropriate data type.

Additional examples:

RMOD RTU-2 SLAVE:2 CMD:PMR MB: 40101 FLOATSW RMOD RTU-5 SLAVE:5 CMD:RCS MB: 40102 ULONGSW

3.3 DOWNLOAD, REBOOT AND LOAD

Use the following procedures To Download Controller Drop Configuration (see page 29), To Reboot Controller Drop (see page 31) and To Load Controller Drop (see page 32) commands on the Ovation Controller drop. These functions are done through the Developer Studio.

Note: In the OCR400, when using the direct connection (Port N4 to N4) Control Synchronization, make sure that both Controllers have Control Synchronization enabled and that the cable is attached before performing a download, reboot and load.

If a pair of redundant Controllers has been running with Control Synchronization enabled and Control Synchronization is then disabled, the dedicated cable should be disconnected from the Controllers before rebooting the Controllers with the new configuration.

Conversely, if a pair of redundant Controllers has been running with Control Synchronization disabled and Control Synchronization is then enabled, the dedicated cable should be connected between the Controllers after they have been running with the new configuration.

CON_020 29


3.3.1 TO DOWNLOAD CONTROLLER DROP CONFIGURATION

Note: The Download command must be performed any time configuration and software changes have been made to a Controller drop.


2. Use the system tree to navigate to the Drops folder: Systems Networks Units Drops

3. Right-click on the appropriate Controller drop item.

4. Select Download from the pop-up menu.

Note: The Download function can also be executed on a System, Network, and Unit item when multiple drops are to be downloaded (See Ovation Developer Studio User Guide.)

5. For redundant Controller drop configurations, the Download Wizard appears.

6. Select a drop from the window. The Download Preview dialog box appears and lists any files that may have been altered during drop configuration and software changes.

7. Select which files should be included in the Download process.

Figure 16: Download Preview Dialog Box

8. Place a check next to the Download option and click Ok.

30 CON_020


Download Preview Dialog Box

SE L E CT I O N DES CRIP T I ON

Query Results The top left check box selects or deselects all of the files in the preview list.

DownLoad When this action is checked, a download of all selected previewed files is executed after pressing the OK button.

Reboot When this action is checked, a reboot is executed on the drop currently selected after pressing the OK button.

Note: To automatically reboot after completing the Download command, check both Download and Reboot before clicking Ok.

Abort Cancels the Download Preview and returns you to the Ovation Developer Studio interface without executing any commands.

Ok Executes the settings and closes the window.

Skip To Next Drop When downloading to System, Network, or Unit items, this button advances to the next drop for file preview.

9. See To Reboot a Controller Drop (see page 31).

3.3.2 TO REBOOT A CONTROLLER DROP

Note: In most cases, the Reboot command should be executed immediately following the completion of the Download command. This may not always be completely necessary, but it is a safe and recommended practice.


2. Use the system tree to navigate to the Drops item: Systems Networks Units Drops

3. Right-click on the appropriate Controller Drop item.

4. Select Reboot from the pop-up menu.

5. For redundant Controller drop configurations, the Reboot Wizard appears.

6. Select the same Controller drop that was chosen for the download. A confirmation dialog box appears.

Figure 17: Reboot Confirmation Dialog Box

7. Click Yes to close the window and execute the reboot process.

CON_020 31

3.4 Redundant Modbus Specification

3.3.3 TO LOAD A CONTROLLER DROP

The Load function is necessary anytime changes have been made relating to points or control. Since a new drop point was inserted in Configuring Controller Software, the Load command should be executed immediately following the completion of the Reboot command.

Note: The Load function is also required when Controller device drivers (Configuring Ovation Drivers), that have been configured with I/O points, are either deleted or changed. This would also require the deletion of the existing points and execution of the Clear command as well. (See Ovation Developer Studio User Guide.)


2. Use the system tree to navigate to the Drops item: Systems Networks Units Drops

3. Right-click on the appropriate Controller Drop item.

4. Select Load from the pop-up menu.

5. For redundant Controller drop configurations, the Select a drop to load dialog box appears.

6. Select the same Controller drop that was rebooted. The load process executes.

7. Repeat the Download, Reboot and Load procedures for the partner drop in redundant Controller drop configurations.

3.4 REDUNDANT MODBUS SPECIFICATION

You have the ability to add/insert up to eight Redundant Modbus device (RTP) pairs. The attributes of these objects can be viewed (and modified) using the Ovation Developer Studio Open operation in the command pull-down window.

3.4.1 CONFIGURATION

Defined Point Attributes

IO_TYPE - T for third-party IO_LOCATION - used to indicate the applicable IO driver. IO_CHANNEL - (applicable for digital points) dictates which bit of the data register is

accessed. IO_ACCESS - indicates the applicable Redundant Modbus Device (RTU), Modbus Slave,

Modbus command, Modbus register, and access method used to assign the Ovation point. The syntax: RMOD SLAVE: CMD:

MB:

Where:

DeviceName - name of the Redundant Modbus Device.

SlaveNum - Modbus slave number (1 to 255).

Cmd - the Modbus command used to access the defined register.

32 CON_020

3.4 Redundant Modbus Specification

ModbusAddress - the applicable Modbus address that you entered. Valid values for this field are dictated by the Modbus command that is used.

DataType - applies to analog points. This dictates how the data is accessed.

SwapMode - this optional field specifies if bytes or words will be swapped when accessing the target Modbus data.

CON_020 33

S E C T I O N 4

WHAT ARE THE REDUNDANT MODBUS FAULT CODES?

IN THIS SECTION

Redundant Modbus Error Codes Overview ......................................................................35

4.1 REDUNDANT MODBUS ERROR CODES OVERVIEW

The Ovation system provides error codes and messages that can be used to diagnose system problems.

Fault information is found on the System Status diagram and the Drop Details diagram. Drop Fault Code information is found in the following record fields of the Drop Status (DU) record or in designated station's General Message Display (GMD) or the Error Log Viewer.

Fault Code = FC (displayed in decimal in the Drop Details diagram) Fault ID = FK (displayed in hexadecimal in the Drop Details diagram) Fault Parameter 1 = FS (displayed in hexadecimal in the Drop Details diagram) Fault Parameter 2 = FO (displayed in hexadecimal in the Drop Details diagram) Fault Parameter 3, 4, and 5 (displayed in hexadecimal in the Error Log Viewer) The following sections describe the error codes associated with the Redundant Modbus interface.

CON_020 35

4.1 Redundant Modbus Error Codes Overview

4.1.1 REDUNDANT I/O ERROR (66-B-2)

All fault codes in this section have similar characteristics:

66 - This fault originated in your Controller. A fault originating in your Controller means that there is a problem in one of your input/output modules or the network that connects them. Your Controller is one or more cabinets that contain input- and output- monitoring modules connected to your field device by wires. Fault codes are displayed by the green LED lights on the IOIC cards in your Controller cabinets, or displayed on the system drop status screen on your Ovation system. You can get further information on your General Message Display (if you are using a Solaris platform) or your error log (if you are using a Windows platform).

B - This is an I/O subsystem error. The I/O subsystem incorporates all of the input and output devices that share data with your Controller. These devices can be Emerson products, or third-party products. They can be hardware or software.

2 - This indicates a Redundant I/O error for physical devices such as, a PCRR module. This error also indicates a problem with connections, if the device is a datalink.

Fault Code 66-B-2

FAU L T CO D E (C O DE - ID - FP1 - FP2)

SUM M AR Y US E R RE SP ON S E

66-B-2-0x08-0x13661

This error occurs when the Controller is configured to fail on error and has received a disconnect from the Modbus end device.

Check to make sure the Modbus device is powered on and available for communication.

Check the integrity of the communication path between the Ovation Controller and the Modbus device (switches, cables, etc).

66-B-2-0x08-0x13658 This error occurs when the Controller is configured to fail on communication error and the Controller did not receive a reply from the Modbus end device within the user defined timeout.



66-B-2-0x08-0x13451 This error occurs when the Controller is configured to fail on communication error and the Controller was trying to send a message to the device but could not send the packet. This is typically due to the connection being closed.



36 CON_020


4.1.2 DATALINK ERRORS (66-B-5)

All of the fault codes in this section have similar characteristics:



5 - This fault is due to a datalink error. Datalink errors are generated by any module that utilizes the DLAP (Toshiba, MHI, Fieldbus, GE Genius, Redundant Modbus). Datalink errors cause the Controller to go into failed mode.

Fault Code 66-B-5



66-B-5-0x13000 Operating system error. This is a fatal error that causes the Controller to be placed in failed mode. The driver could not get enough memory.

This fault code returns a status number in the fault parameter 3 position. This status number indicates the error returned when allocating memory.

This fault code returns the size of the memory block requested in fault parameter 4.

Check to make sure you have 64 MB of memory in your Controller.

If you are using 64 MB of memory and this error still occurs, call Emerson service.

66-B-5-0x13001 Operating system error. This is a fatal error that causes the Controller to be placed in failed mode. The driver could not partition memory.





CON_020 37


FAU L T CO D E SUM M AR Y US E R RE SP ON S E (C O DE - ID - FP1 - FP2)






66-B-5-0x13003 Operating system error. This is a fatal error that causes the Controller to be placed in failed mode. Error accessing WDPF_HOME directory.

This error indicates a problem with the flash memory. Try reformatting the flash.

If this does not work, report all parameters to Emerson service.

66-B-5-0x13004 Operating system error. This error occurs if the Controller can not read the shc configuration file. This file is used to determine if the Controller is the primary or partner Controller.

This error indicates a problem with the flash memory. Try reformatting the flash.

If this does not work, report all parameters to Emerson service.

66-B-5-0x13005 Could not read the Redundant Modbus configuration file correctly.

This fault indicates that the Controller could not read the Modbus configuration file correctly.

Make sure the Controller has been query downloaded and rebooted since configuration of the Redundant Modbus driver.

If the download has occurred and this error still happens, this indicates a problem with the flash memory. Try reformatting the flash.

If reformatting the flash does not work, report all parameters to Emerson service.

66-B-5-13100 Operating system error. This is a fatal error that causes the Controller to be placed in failed mode. The driver could not partition memory.

This fault code returns a status number in fault parameter 3 indicating the error returned when allocating memory.

This fault code returns the pointer that was trying to be allocated in fault parameter 4.

Fault parameter 5 returns the size of the memory block requested.



38 CON_020



66-B-5-0x13101 One of the state machines used inside the code is in an unknown state.

Fault parameter 3 returns the state.

This is a critical error, try a clear and load of the Controller.

If this does not correct the problem, report all parameters to Emerson service.

66-B-5-0x13102 DL API error. Failed setting point value.

This fault returns the value of the critical error returned by the DLAPI in fault parameter 3.

This fault returns the device index of the driver in question in the fault parameter 4 position.

This fault code returns the error type returned in the fault parameter 5 position.

Make sure there is no database mismatch.

Report all parameters to Emerson service.

66-B-5-0x13200 Operating system error. This is a fatal error that will cause the Controller to be placed in failed mode. The driver could not partition memory.












CON_020 39






If this does not correct the problem, report all parameters to Emerson service.













66-B-5-0x13501 The Modbus task is unable to determine the mode of the drop: control, backup, or failed. This is a critical error.

Reboot the Controller and see if this is corrected.

If the error still occurs, call Emerson service.

40 CON_020










Fault parameter 3 returns the RTU that is having problems.

Fault parameter 4 returns the slave that is having problems.



If this does not correct problem, report all parameters to Emerson service.

CON_020 41


4.1.3 DATALINK WARNING (66-B-6)

All fault codes in this section have similar characteristics:



6 - This is a Data Link warning. Data Link Warnings are generated by any module that utilizes the DLAPI (Toshiba, MHI, Fieldbus, GE Genius, Redundant Modbus). Data Link Warnings cause the Controller to go into alarm.

Fault Code 66-B-6



66-B-6-0x13050 This warning is generated when the Modbus task cannot close its configuration file.

Check to make sure the flash is accurate.

If the flash is accurate and this error still occurs, call Emerson service.

66-B-6-0x13150 This warning is generated when the Modbus task is unable to tell the DLAPI it is running.

Fault parameter 3 represents the device in question.

Check to make sure your device is configured correctly. Try rebooting the Controller. If this does not correct the problem, call Emerson service.

66-B-6-0x13151 This warning is generated when the Modbus task is unable to tickle the DLAPI.


Check to make sure your device is configured correctly. Try rebooting the Controller. If this does not correct the problem call Emerson service.

66-B-6-0x13152 This warning is generated when the Modbus task is unable to determine if an online edit has occurred.


Check to make sure your device is configured correctly. Try restarting the Controller. If this does not correct the problem, call Emerson service.

66-B-6-0x13153 This warning is generated when the Modbus task is unable to access online edit information.

Fault parameter 3 represents the device in questions.

Check to make sure your device is configured correctly. Try restarting the Controller. If this does not correct the problem, call Emerson service.

42 CON_020



66-B-6-0x13450 This warning is generated when an invalid Modbus command type is requested.

Fault parameter 3 represents the requested Modbus function code.

Clear and load the Controller.

If this problem still occurs, call Emerson service.

66-B-6-0x13451 This warning occurs when the Controller trying to send a message to the device but could not send the packet. This is typically due to the connection being closed.

Check to make sure the Modbus device is on and available for communication.

Check the integrity of the communication path between the Ovation Controller and the Modbus device(switches, cables, etc)

66-B-6-0x13550 This warning is generated when the Modbus task cannot read the TT field of a Modbus point.

Fault parameter 3 represents the RTU in question.

Fault parameter 4 represents the tag handle in question.

Fault parameter 5 is the SID of the point in question.

Check the configuration of the point in question.


If this error still occurs, call Emerson service.

66-B-6-0x13551 This warning is generated when the Modbus task cannot read the HD field of a Modbus point.


Fault parameter 4 represents the tag handle in question.





66-B-6-0x13552 This warning is generated when the Modbus driver is asked to delete a point from the interface but cannot find the point in its tables.


Fault parameter 4 represents the tag handle of the point in question.





CON_020 43



66-B-6-0x13650 This warning occurs if the Modbus task cannot make a TCP connection to the end device.

Fault parameter 3 represents the system level error code returned.

Fault parameter 4 represents the socket file descriptor of the connection in question.

Check to make sure you have a valid connection path to the end device.

Check to make sure the end device is powered up and running.


66-B-6-0x13651 This warning occurs if the Modbus task is unable to set the no delay socket option.


Fault parameter 4 represents the socket file descriptor in question.

There is no user action. Please call Emerson service and report all fault parameters.

66-B-6-0x13652 This warning occurs if the Modbus task is unable to set the keep alive socket option on the socket.




66-B-6-0x13653 This warning occurs if the Modbus task is unable to set the linger socket option on the socket.




66-B-6-0x13654 This warning occurs if the Modbus task is unable to get the socket file descriptor.


66-B-6-0x13655 This warning occurs if the Modbus task is unable to set the socket to non-blocking.


66-B-6-0x13656 This warning occurs if the Modbus task is unable to destroy the port once it is finished communicating.




44 CON_020



66-B-6-0x13657 This warning occurs if the Modbus task is unable to perform the select operation on the socket.


Fault parameter 4 represents the Slave in question.


Check to make sure the Modbus end device is up and running.

Check the integrity of the network between Ovation and the end device.

If this warning still occurs please call Emerson service and report all fault parameters.

66-B-6-0x13658 This warning occurs if the Controller did not receive a reply from the Modbus end device within the user-defined timeout.



66-B-6-0x13659 This warning occurs if the Modbus task is unable to set the retransmission time.


Fault parameter 4 represents the Slave in question.



66-B-6-0x13660 This warning occurs if the Modbus task is unable to make a connection on the socket.

Fault parameter 3 is the system level error returned.

Fault parameter 4 is the socket file descriptor in question.



66-B-6-0x13661 This warning occurs when the Controller has received a disconnect from the Modbus end device.


Fault parameter 4 represents the slave in question.


Check the integrity of the communication path between the Ovation Controller and the Modbus device (switches, cables, etc)

CON_020 45



66-B-6-0x13662 This warning occurs when the Modbus task receives an invalid or malformed reply.


Fault parameter 4 represents the slave in question.

Fault parameter 5 is the Modbus function code from the message.

Check the integrity of the communication path between the Ovation Controller and the Modbus device (switches, cables, etc). Check to make sure you have 64 MB of memory in your Controller.

Check the health of the Modbus end device.

If this error still occurs, please call Emerson service.

46 CON_020

GLOSSARY OF TERMS

A A PORT

Port on a dual-attached Ovation station where the primary ring enters and the secondary ring exits.

ADMIN TOOL

The Administrative Tool is an Emerson utility that configures and downloads software to the drops through the use of GUIs. (Do not confuse this tool with the Sun utility also named Admin Tool.)

ALARM

A message or other signal intended to draw attention to a non-normal plant condition; for displays at user interfaces, an alarm reflects a point status.

ALGORITHM

1) A set of rules, procedures, and mathematical formulas that define a desired control strategy. 2) Software provided with a Controller to automatically apply a specified algorithm during the system scan. 3) Ovation record type (LC) used to store tuning or data configuration for an algorithm in the system.

ANALOG

1) Conditions or values that continuously vary across some range, represented by more than one bit. 2) A point that is an analog record type. Analog points are typically associated with I/O hardware that converts a field signal (for example, voltage) to a low-level signal used by the processor. Can be Long or Deluxe (Contrast with digital.)

APERIODIC POINTS

Points whose values are scanned only as needed or as requested. See also periodic points.

API

Application Programming Interface, a set of routines or functions a program calls to tell the operating system to perform a task.

APPLICATION PROGRAM

1) Emerson-supplied programs that perform frequently required functions. 2) A series of loops, ladders, and/or algorithms run in a processor to control plant functions. Also known as an Application. 3) User-defined or commercially available software that performs a specific task.

CON_020 47

Glossary of Terms

ASCII

American Standard Code for Information Interchange, a standard for representing computer characters. The set consists of 128 characters numbered from 0 to 127 and includes all the letters, numbers and punctuation marks.

ASYNCHRONOUS

Data communication that is not time critical. Typically provided on demand only and provided at different times (Contrast with synchronous).

AUI CABLE

Attachment Unit Interface Cable that interfaces the PCRR card to the MAU module in Ovation and WDPF migrated remote I/O applications. It contains four sets of individually shielded twisted pairs.

B B PORT

Port on a dual-attached Ovation station where the secondary ring enters and the primary ring exits.

BANDWIDTH

This is a description of how much information can be sent through a connection, usually measured in bits-per-second.

BASE ALARM SYSTEM

Standard package used for viewing and acknowledging alarms.

BASE UNIT

Hardware that consists of a printed circuit board, various connectors, and plastic housing and provides a mechanism for the user to land field wiring, and connects the field signals to the I/O module. The unit enables the I/O module to receive power, and also provides a low-impedance earth ground connection. Each Base Unit can house two sets of I/O modules, along with the associated field wiring.

BAUD RATE

Number of bits-per-second a modem can send or receive.

BG

See Packed Group Alarm.

BIT

A single digit number in base-2, either a 1 or a zero. This is the smallest unit of computerized data.

BITMAP FILE

A file type that is used to define which icons are shown when using iconic alarming.

48 CON_020

Glossary of Terms

BOOTSTRAP

A software routine used to start computer operation (sometimes abbreviated boot). The bootstrap routine will typically occur automatically after a reset or power cycle, but may require manual keying.

BRANCH

Set of Base Units configured consecutively on a DIN rail with a local bus being connected to the Ovation I/O Controller.

BRIDGE

Device that connects two or more network components and transmits data with source and destination addresses on different network components.

BROADCAST

Process of sending information across the Ovation network. Broadcasts may be periodic (every second or every 0.1 of a second) or non-periodic (broadcast on demand only).

BYTE

A set of bits that represent a single character. Typically, 8 or 10 bits in a byte.

C CDDI

Copper Distributed Data Interface (See FDDI).

CDE

Common Desktop Environment. A windowing system that runs on a Sun-compatible workstation under SunOs or Solaris

CHARACTERISTICS

A set of 8 alphanumeric characters associated with a point, used to represent user-defined aspects of the controlled process. Characteristics are used in alarm processing and point review/search functions.

CLIENT

A computer, or software program that is used to contact and obtain data from a server software program on a networked computer.

COIL

A ladder diagram element that represents either a real-world output field device (for example, a motor starter, solenoid, and so forth) or an internal calculated point. (See discrete output.)

COLLISION

Garbling of data when two or more nodes on the same network segment transmit data simultaneously.

CON_020 49

Glossary of Terms

COLLISION DETECTION

Switches are used to buffer simultaneous data messages and transmit them one at a time.

COMPACT I/O MODULES

Ovation I/O modules that do not contain a Personality module, only an Electronics module.

CONCENTRATOR

FDDI node used to connect multiple Ovation stations to dual rings. Must have an A port, a B port, and at least one M port.

CONDUCTING

The state of a ladder diagram circuit when there is a continuous current path condition caused by closed contacts.

CONFIGURATION

Entering initial data into a processor, including definition of associated hardware. The configuration process typically includes downloading the drop database and other required software, and may involve editing configuration files(s).

CONFIGURATION FILE

Typically, an ASCII file containing statements that specify the configuration of a drop or function. These files may use standard operating system formats or may use an Emerson source language.

CONTACT

A ladder diagram element that represents either a real-world input device (for example, a push-button, switch, etc.) or an internal calculated point. (See discrete input.)

CONTROL BUILDER

AutoCAD based Power tool package used to build control drawings and generate source code from the drawings.

CONTROL SHEET

AutoCAD drawing that contains a graphical representation of a control scheme.

CONTROL TASK

Specific Controller area where all control sheets in that area are scanned at the same frequency.

CONTROLLER

A drop used to control a process. The Controller passes process control information over the network to other drops or devices that need it.

50 CON_020

Glossary of Terms

CPU

Central Processing Unit, a microprocessor chip that powers a computer. May also refer to the case that holds the chip.

CRT

Cathode-Ray Tube, a tube of a monitor that produces images on the screen. Often used as a generic term for a computer monitor.

CURSOR

A character on a display screen indicating the current active location.

D DAC/DAS

Dual Attachment Concentrator/Dual Attachment Station. Provides dual attachment to the FDDI or Fast Ethernet network.

DATA HIGHWAY

The communication link used to transfer time-critical information between drops or stations; also called a Local Area Network (LAN) or network.

DATA STRUCTURES

Four portions of an Ovation point record type.See also Dynamic Data, Static Data, Flash Data, and MMI Data.

DATABASE

A structured set of data, especially the point database in each Ovation drop (which defines originated and received points) and the Ovation master database (which defines the attributes of all points in the system).

DCS

Distributed Control System (such as Ovation).

DEADBAND

Range of values through which an input signal may vary without initiating an action that causes an observable change in the output signal.

DEFAULT POINTS

Points created by the Control Builder that have a defined naming convention.

DEFAULT VALUE

Used by a program when no specific value has been entered by the user. In the context of an iterative window or program, default may refer to a value specified in the functions configuration file; in the context of configuring a function, default refers to the value used when there is no valid parameter entry.

CON_020 51

Glossary of Terms

DELUXE RECORD TYPE

Optional Ovation record type. Has same functions as Long record type, plus plant mode limits and scan time displays.

DESTINATION

1) The location in memory (such as a holding register) into which data is placed after the completion of certain programmable functions. (Contrast with source.) 2) A method of determining which alarms are displayed at a specific user interface drop, based on the first point characteristic (typically representing the plant area).

DEVICE

1) Peripheral equipment connected to the Ovation system. 2) Algorithm specifically designed to simplify operation of open/close or stop/start devices, using feedback signals to monitor command completion.

DHC

Data Highway Controller. Printed-circuit board(s) in each drop that manage Data Highway communication.

DIAGNOSTICS

Functions that examine hardware or software to isolate malfunctions and errors. In the Ovation system, each drop incorporates automatic self-test diagnostics. If faulty operation is detected, a message or alarm is usually initiated.

DIAGRAM

A graphic depiction of a plant process (or other data), displayed on a CRT at a user interface.

DIALOG BOX

A user interface window that prompts the user to enter information needed by a process.

DIGITAL

1) Signals or conditions that are either on or off, represented by one bit. 2) A point that is a digital record type. Digital points are typically associated with discrete I/O hardware. Can be Long or Deluxe. (Contrast with analog.)

DIN

Connector conforming to the specifications of the German standards organization (Deutsche Industrie Norm).

DIP

Integrated circuit enclosed in a plastic or ceramic housing and connected to pins. (Dual Inline Package)

52 CON_020

Glossary of Terms

DISCRETE I/O

Individual hard-wired circuits connecting real-world field devices with the processor. Each discrete input provides the processor with a single digital signal based on a single state in the field device. Each discrete output sends a single digital signal to the field based on a single bit of data in the processor.

DISTRIBUTED DATABASE

Contains a subset of the information stored on the Master Database and is stored locally on a drop to allow that drop to operate if the Master Database is unavailable. A Distributed Database is present on each drop in the system and is continually updated as point information changes.

DISTRIBUTED I/O

Hardware used to communicate between the processor and I/O modules located outside the processor chassis (also called Remote I/O).

DOMAIN

Logical collection of computers and users on a network that share a common security database.

DOWNLOAD

The process of transferring data to the memory or disk of a drop.

DROP

A collective term for a Controller, Workstation, or Database Server that is a member of an Ovation network and is defined as a drop by an Ovation configuration tool (Developer Studio or Init Tool).

DROP LOADER

Power Tool used to load control and originating point information into drops in an Ovation system. Links the Master Database with all the drops in the system.

DROP POINT (DU)

Record type used to store status information for a drop. Every drop must be configured with at least one point of type DU.

DYNAMIC DATA

Portion of an Ovation point record that is broadcast periodically in Dynamic Data Blocks (DDBs )by the originating drop and stored in volatile memory. DDB size is configured through the Ovation configuration tools (Admin Tool or Developer Studio).

E EDB HISTORIAN

A drop on an Ovation control system that will collect, process, archive, and retrieve information that originates locally or throughout a geographically diverse set of process control sites.

CON_020 53

Glossary of Terms

ELECTRONICS MODULE

Part of Ovation I/O that contains the electronics for processing I/O signals. Fits into the Base Unit and is typically configured by a Personality Module.

EMS

Expanded Memory Specification, a bank-switched memory management scheme that allows applications to access vast quantities of memory.

ENGINEERING STATION

An Ovation drop used for configuration and entry of system programs.

ETHERNET

A standard network protocol. Used to transfer non-time-critical information between drops.

F FAST ETHERNET

Standard for transmitting data at 100 megabits per second. Similar to FDDI, but uses switches instead of concentrators, and dual-channel Ethernet NIC cards instead of dual-attachment FDDI NIC cards (Contrast to FDDI).

FDDI

Fiber Distributed Data Interface, a standard for transmitting data. Typically consists of a dual fiber-optic counter-rotating ring capable of carrying synchronous and asynchronous messages. Ring provides automatic wrap-back reconfiguration if a segment of the highway fails (Contrast to Fast Ethernet).

FIREWALL

Security system intended to protect an organization's computer network from external threats. All communication between the internal computer network and the outside world is routed through a server that determines if a message is safe to pass to the internal network.

FLASH DATA

Portion of an Ovation point record that is stored in the originating drops flash (or disk) memory and copied to receiving drops periodically.

FORCE VALUE

To set the value of a coil or contact to a desired state (on/off; 0, 1), regardless of other values in the ladder diagram.

FOUNDATION FIELDBUS

Digital, two-way, multi-drop communication link among intelligent measurement and control devices.

54 CON_020

Glossary of Terms

FTP

File Transfer Protocol, a set of rules that allows one computer to download a file from another computer via a network connection.

FULLY QUALIFIED POINT NAME

Point name that specifically identifies a point by combining three parameters. Format is pointname.unit@network where point name contains a maximum of 24 characters, unit contains a maximum of 6 characters, network contains a maximum of 8 characters. Do not use when inserting a new point in Developer Studio, only insert point name parameter.

G GATEWAY

Hardware or software that translates between two dissimilar protocols.

GP

See Packed Group.

GRAPHICS BUILDER

Power Tool used to create and edit System Process Diagrams that display on the Operator Station.

GUI

Graphical User Interface, an industry-standard term used to describe a user interface based on a windowing system such as Microsoft Windows.

H HISTORIAN

Dedicated drop in the Ovation system that collects and stores process point data and other information.

HMI/MMI

Human-Machine Interface/Man-Machine Interface. Refers to drops that provide user interface functions between a user and a machine (such as the Operator Station).

HOST

Any computer on a network that is available for services to other computers.

HYPERTEXT

Any text that contains links to other documents-words or phrases in the document that can be chosen by the reader and which cause another document to be retrieved and displayed.

CON_020 55

Glossary of Terms

I I/O

Input/Output, a general term for reading and writing data on a computer. Digitizes information from plant processes and passes it to the Controller for use in control strategies.

I/O BUILDER

Power Tool used to define the I/O modules used in an Ovation system.

I/O CONTROLLER

Interface between the Network and the I/O. The Controller is located in the Ovation I/O cabinet.

I/O MODULE

Typically made up of an Electronics module and a Personality module. Performs the interface between the I/O Controller and the field devices.

I/O NODES

Ovation record types

ICON

A small graphic on a windowing system display that represents an active process or available function. Typically, an icon can be expanded into a window.

ICONIC ALARMING

Provides a mechanism to group alarms based on their priority and their plant area. Each group of alarms is represente

con_020

Documents

redundant configuration

software information

hardware information

actual use

use of circuits

modbus gateway

proprietary information

software architecture