Safety Instrumented System (SIS) User Guide for Ovation 3.3.1 OW331_47 Version 1 July 2010
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 ® 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: https://www.ovationusers.com
Contents 1
Introduction to Ovation Safety Instrumented System (SIS)
1.1 1.2 1.3
What is a Safety Instrumented System?............................................................................. 1 Functions of Ovation SIS .................................................................................................... 2 Safety Instrumented System terminology ........................................................................... 2
2
Planning your Safety Instrumented System
2.1
SIS issues to consider......................................................................................................... 5 2.1.1 Safety Instrumented Functions (SIFs)............................................................... 6 2.1.2 Safety Integrity Levels (SILs) ............................................................................ 6 Limitations for SIS ............................................................................................................... 7 SIS environmental specifications ........................................................................................ 7 SIS network design examples............................................................................................. 8 2.4.1 Physical network design example ..................................................................... 8 2.4.2 Logical network design example ....................................................................... 9 Planning your hardware installation .................................................................................... 9 2.5.1 Installation tools............................................................................................... 10
2.2 2.3 2.4
2.5
1
5
3
Hardware for Ovation SIS
3.1 3.2
Hardware components of Ovation SIS.............................................................................. 11 SIS carriers........................................................................................................................ 14 3.2.1 SIS Carrier part numbers ................................................................................ 14 3.2.2 Vertical carriers ............................................................................................... 15 3.2.3 To install the 1-wide carrier (dual-left/right extender cables) .......................... 17 3.2.4 To install the 2-wide power/SIS Data Server carriers ..................................... 18 3.2.5 To install the 4-wide Vertical (Power/SIS Data Server) carrier ....................... 20 3.2.6 To install the 8-wide I/O interface carrier (can hold up to four simplex Logic Solvers) 20 3.2.7 To install the 8-wide Vertical (left/right side) carrier (can hold up to four simplex Logic Solvers).................................................................................................................... 21 SLS terminal blocks .......................................................................................................... 23 3.3.1 SIS terminal block part numbers ..................................................................... 23 3.3.2 To install terminal blocks ................................................................................. 23 SIS Data Server ................................................................................................................ 24 3.4.1 SIS Data Server part number .......................................................................... 24 3.4.2 To install a simplex SIS Data Server............................................................... 24 3.4.3 To power up a simplex SIS Data Server ......................................................... 25 3.4.4 To power up a duplex SIS Data Server........................................................... 26 3.4.5 To remove a redundant SIS Data Server........................................................ 26 3.4.6 SIS Data Server LEDs..................................................................................... 27 SIS Logic Solvers.............................................................................................................. 28 3.5.1 SIS Logic Solver part number ......................................................................... 29 3.5.2 Logic Solver specifications .............................................................................. 29
3.3
3.4
3.5
OW331_47
11
i
Table of Contents
3.6
3.7
3.8 3.9
3.10
3.11 3.12
67
4
Software for Ovation SIS
4.1
Software components of Ovation SIS ............................................................................... 67
5
SIS Algorithms
5.1 5.2
Algorithm types ................................................................................................................. 70 Using algorithm reference pages ...................................................................................... 70 5.2.1 Algorithm functional symbols........................................................................... 71 Ovation SIS Logic Solver algorithm table ......................................................................... 72 LSAI................................................................................................................................... 75 LSALM............................................................................................................................... 78 LSAND .............................................................................................................................. 80 LSAVTR ............................................................................................................................ 82 LSBDE............................................................................................................................. 100
5.3 5.4 5.5 5.6 5.7 5.8
ii
3.5.3 To install Logic Solvers ................................................................................... 30 3.5.4 Logic Solver redundancy................................................................................. 31 3.5.5 SIS Logic Solver LEDs .................................................................................... 32 SIS I/O channels ............................................................................................................... 33 3.6.1 Analog Input and HART Analog Input channel specifications and wiring ....... 33 3.6.2 HART two-state output channel specifications and wiring .............................. 34 3.6.3 Digital Input channel specifications and wiring................................................ 35 3.6.4 Digital Output channel specifications and wiring............................................. 37 SIS Net Repeater .............................................................................................................. 38 3.7.1 SIS Net Repeater part number........................................................................ 38 3.7.2 To install SIS Net Repeaters for horizontal mounting ..................................... 39 3.7.3 SIS Net Distance Extender.............................................................................. 39 3.7.4 SIS Net Repeater LEDs .................................................................................. 40 Fiber-optic cable\ring......................................................................................................... 41 Carrier extender cables..................................................................................................... 41 3.9.1 Carrier extender cable part numbers .............................................................. 41 3.9.2 To install carrier extender cables .................................................................... 42 3.9.3 To terminate the local bus ............................................................................... 43 Power Supply .................................................................................................................... 44 3.10.1 Power supply part number .............................................................................. 45 3.10.2 Power supply specifications ............................................................................ 45 3.10.3 To install power supplies ................................................................................. 45 3.10.4 To provide power to the Logic Solvers............................................................ 46 3.10.5 To provide power to the SISNet Repeaters .................................................... 46 3.10.6 To provide power to SISNet Distance extenders ............................................ 47 3.10.7 SIS Power Supply LEDs.................................................................................. 48 SIS LAN switches and routers .......................................................................................... 49 Ovation SIS accessories ................................................................................................... 49 3.12.1 SIS Relay module............................................................................................ 50 3.12.2 Voltage Monitor module .................................................................................. 54 3.12.3 SIS Current Limiter module ............................................................................. 56 3.12.4 Auxiliary Relay DTA-Inverting module ............................................................ 59 3.12.5 Auxiliary Relay ETA-Direct module ................................................................. 63 3.12.6 Auxiliary Relay Diode module ......................................................................... 64
69
OW331_47
Table of Contents 5.9 5.10 5.11 5.12 5.13 5.14 5.15 5.16 5.17 5.18 5.19 5.20 5.21 5.22 5.23 5.24 5.25 5.26 5.27 5.28 5.29 5.30 5.31 5.32 5.33 5.34 5.35 5.36 5.37 5.38 5.39 5.40 5.41 5.42 5.43
LSBFI .............................................................................................................................. 102 LSBFO............................................................................................................................. 105 LSCALC .......................................................................................................................... 107 LSCEM ............................................................................................................................ 113 LSCMP ............................................................................................................................ 145 LSDI ................................................................................................................................ 147 LSDO............................................................................................................................... 150 LSDVC ............................................................................................................................ 157 LSDVTR .......................................................................................................................... 169 LSLIM .............................................................................................................................. 185 LSMID ............................................................................................................................. 188 LSNAND.......................................................................................................................... 191 LSNDE ............................................................................................................................ 193 LSNOR ............................................................................................................................ 195 LSNOT ............................................................................................................................ 197 LSOFFD .......................................................................................................................... 198 LSOND ............................................................................................................................ 200 LSOR............................................................................................................................... 202 LSPDE............................................................................................................................. 204 LSRET............................................................................................................................. 206 LSRS ............................................................................................................................... 208 LSSEQ ............................................................................................................................ 210 LSSR ............................................................................................................................... 215 LSSTD............................................................................................................................. 217 LSTP ............................................................................................................................... 226 LSXNOR.......................................................................................................................... 228 LSXOR ............................................................................................................................ 229 SIS connector algorithm table ......................................................................................... 230 SECPARAM .................................................................................................................... 231 SECPARAMREF............................................................................................................. 232 GSECPARAMREF .......................................................................................................... 233 NONSECPARAM ............................................................................................................ 234 Connecting SIS sheets.................................................................................................... 235 Secured algorithm parameters........................................................................................ 236 Nonsecured algorithm parameters.................................................................................. 236
6
Adding and configuring SIS components in the Developer Studio 237
6.1 6.2 6.3 6.4 6.5 6.6
Overview of adding and configuring SIS components .................................................... 237 To add an SIS Network to the Ovation system ............................................................... 238 To add an SIS Data Server to the Ovation System ........................................................ 241 Initial installation SIS upgrade......................................................................................... 244 To add an SIS network switch to the Ovation System.................................................... 244 To create SIS network switch configuration files ............................................................ 246 6.6.1 To initialize SIS network switches ................................................................. 248
OW331_47
iii
Table of Contents 6.7 6.8
6.14 6.15 6.16
To add an SIS I/O device number................................................................................... 250 To add an SIS I/O device to the Ovation System ........................................................... 250 6.8.1 To associate a Node point with an SIS I/O device ........................................ 253 To assign an SIS I/O Data Server to an SIS I/O Device................................................. 255 6.9.1 Viewing SIS points in the Developer Studio hierarchy.................................. 258 6.9.2 Removing Ovation SIS points from SIS control sheets................................. 259 To configure SIS LAN network switches......................................................................... 260 To add and configure SIS Logic Solvers in the Ovation System .................................... 263 6.11.1 Configuring the Logic Solver Config tab........................................................ 266 6.11.2 Configuring the Logic Solver General tab ..................................................... 267 6.11.3 Configuring the Logic Solver Proof Testing tab............................................. 268 To add an SIS control sheet to the SIS Ovation system................................................. 270 To configure an SIS I/O channel..................................................................................... 271 6.13.1 Configuring an Analog Input Channel ........................................................... 273 6.13.2 Configuring a HART Analog Input Channel .................................................. 275 6.13.3 Configuring a HART Two-state Output Channel ........................................... 277 6.13.4 Configuring a Digital Input Channel .............................................................. 279 6.13.5 Configuring a Digital Output Channel............................................................ 280 To configure SIS control modules................................................................................... 280 To configure SIS digital points for alarming with timestamps ......................................... 282 To view SIS points .......................................................................................................... 284
7
Using Ovation SIS
7.1
Loading Logic Solvers..................................................................................................... 285 7.1.1 To load an SIS Logic Solver.......................................................................... 285 Using Point Information (PI) to identify SIS points .......................................................... 287 7.2.1 To use Point Information to identify SIS points ............................................. 288 Viewing SIS Tuning windows for SIS algorithms ............................................................ 290 7.3.1 To access the SIS Tuning window for SIS algorithms .................................. 290 7.3.2 SIS Tuning window for the LSCALC algorithm ............................................. 291 7.3.3 SIS Tuning window for the LSCEM algorithm ............................................... 292 7.3.4 SIS Tuning window for the LSSEQ algorithm ............................................... 294 7.3.5 SIS Tuning window for the LSSTD algorithm................................................ 296 Forcing an algorithm input value ..................................................................................... 298 7.4.1 To force an algorithm input value .................................................................. 298 Restarting a Logic Solver ................................................................................................ 307 7.5.1 To restart (reboot) a Logic Solver.................................................................. 307 Requiring a reset before outputs can become energized ............................................... 309 Configuring the Logic Solver's response to detected faults ............................................ 309 7.7.1 Detecting faults on input channels ................................................................ 310 7.7.2 Detecting faults on output channels .............................................................. 314 Choosing the Logic Solver scan rate .............................................................................. 315 Loading to a running process.......................................................................................... 315 Restarting a Logic Solver after a power failure ............................................................... 316 Proof testing the Logic Solver ......................................................................................... 316 7.11.1 Automatic proof testing.................................................................................. 317 7.11.2 Manual proof testing...................................................................................... 317
6.9
6.10 6.11
6.12 6.13
7.2 7.3
7.4 7.5 7.6 7.7
7.8 7.9 7.10 7.11
iv
285
OW331_47
Table of Contents 7.12 7.13
7.14 7.15 7.16
Index
OW331_47
Customizing your Ovation Control Builder frame............................................................ 318 Upgrading SIS firmware .................................................................................................. 319 7.13.1 To initially load or upgrade an SIS Data Server ............................................ 319 7.13.2 To upgrade an SIS Logic Solver ................................................................... 320 Using Fault Codes for SIS (66, 3, 8) ............................................................................... 321 SIS Diagnostics............................................................................................................... 322 SIS Logic Solver events .................................................................................................. 324
327
v
S
E C T I O N
1
Introduction to Ovation Safety Instrumented System (SIS)
IN THIS SECTION What is a Safety Instrumented System?............................................................................. 1 Functions of Ovation SIS .................................................................................................... 2 Safety Instrumented System terminology ........................................................................... 2
1.1
What is a Safety Instrumented System? A Safety Instrumented System (SIS) is a set of components that includes sensors, Logic Solvers, and final control elements whose purpose is to respond to dangerous plant conditions, which may be hazardous. The Safety Instrumented System must generate the correct outputs to prevent the hazard or reduce the consequences of the hazard. A Safety Instrumented System (SIS) is a form of process control typically used in industrial processes, such as those of Power Generation and Waste Water. The SIS performs specified functions in order to maintain a safe state of a control process when any unacceptable process conditions are detected. A safe state is a state of the process operation where the hazardous event cannot occur. The safe state should be achieved within one-half of the process safety time. International standard IEC 61508 is a standard of rules applied to all types of industry. This standard covers the complete safety life cycle, and has its origins in the process control industry sector. International standard IEC 61511 was published in 2003 to provide guidance to end-users on the application of Safety Instrumented Systems in the process industries. Refer to the Ovation Safety Instrumented System (SIS) User Guide for information about using SIS with Ovation.
OW331_47
1
1.2 Functions of Ovation SIS
1.2
Functions of Ovation SIS The Safety Instrumented System performs the following functions:
Implements a risk reduction strategy which is intended to reduce the likelihood of a hazardous event causing a catastrophe in a plant.
Validates messages that are sent from Ovation workstations to the safety system. This reduces the risk of sending invalid and perhaps unsafe messages to the SIS. This function is known as SIS Write.
Manages the safety instrumented functions (SIFs) to provide a risk reduction strategy which is intended to reduce the likelihood of a hazardous event. Each SIF defines:
Measurement sensors to use.
Actions to take.
When to apply the actions.
How fast to measure and react.
1.3
Safety Instrumented System terminology Safety Instrumented System terms
2
TERM
DESCRIPTION
Algorithms
Algorithms are self-contained software modules that reside in the Logic Solvers.
Backplane
Backplane is the electronic bus that is part of an SIS carrier. Backplane carries signals between the SIS Logic Solvers and the SIS Data Server.
CIS
Ovation Controller Interface to SIS Data Server (CIS) provides communication between the Ovation Controller and the SIS Data Server.
Control module
When a Logic Server is added to the Studio, four control modules are automatically created and appear under the Logic Solver in the Studio tree. The control sheets are stored in the control modules. All the control sheets stored in a control module are scanned at the same frequency.
CRC
Cyclic redundancy check (CRC) is a mathematical function designed to detect changes to computer data, and is commonly used in digital communications and data storage. A CRC-enabled device calculates CRC code for each block of data. When a new block is received, the device repeats the calculation; if the new CRC code does not match the old CRC code, this indicates that there is a difference between the two blocks of data. This means there is either a data error or a change in the configuration of the data.
DHCP
Dynamic Host Configuration Protocol (DHCP) is a network application protocol used by devices to obtain configuration information for operation in an Internet Protocol network. This allows networks to add devices with little or no manual intervention.
HAZOP
Hazard and Operational Studies. Requirements for SIS projects.
IP Address
Unique number consisting of four parts separated by dots. An example of an IP address is 129.228.36.38. Every computer that is on the Internet has a unique IP address.
Local bus
Communications between Logic Solvers and one SIS Data Server. Achieved via backplanes and extender cables.
Local SISNet (Local peer bus)
Communications of safety data among Logic Solvers connected to one SIS Data Server. Achieved via carrier backplanes and coaxial extender cables.
OW331_47
1.3 Safety Instrumented System terminology
TERM
DESCRIPTION
LOPA
Layers of Protection Analysis. Requirements for SIS projects.
Netmask
The netmask (also known as an address mask) is a number that identifies the range of IP addresses that are on a local network. The netmask serves as a filter that enables a computer to determine whether it can transfer data directly to another machine on the local network or if the computer must use a router to transfer data.
NAMUR
NAMUR is an international association of automation technology in process control industries. NAMUR alarming can be performed on I/O channels. The NAMUR limits are 106.25% top limit and -2.5% bottom limit.
NTP task
Network Time Protocol. Synchronizes time between the Ovation Controller and its attached Logic Solvers.
Remote SISNet (Remote peer bus)
Communications among Logic Solvers connected to different SIS Data Servers. Achieved via SISNet Repeaters and a fiber optic loop
Shadow algorithm
Term used to describe SIS algorithms when they are loaded into the Ovation Controller. The algorithms are not actually used by the Controller for control, but serve as a visual representation to the user of the algorithms in the Logic Solver.
SIF
Safety Instrumented Function (see page 6).
SIL
Safety Integrity Level (see page 6).
SIS Force
Force operation (see page 298) occurs when a value for an algorithm input parameter (pin) is manually changed, typically for testing purposes.
SIS hardware
Refer to Hardware components (see page 11).
SIS LAN
Communication between a SIS Data Server and an Ovation Controller.
SIS point
An Ovation point that has been used on an SIS control sheet. After the sheet is saved and loaded to an SIS Logic Solver, the point can then be used in SIS control schemes.SIS points can be analog or digital points.
SISNet Ring
Sub-network of SIS components that is contained within one fiber-optic ring (value between 0 and 15).
SISNet
Communications among Logic Solvers, with both local and remote architectures.
SIS Write
SIS Write provides for the validation of messages between Ovation Operator Stations and the SIS Logic Solvers. This function greatly reduces the risk of sending an invalid message to the safety system from the Ovation system.
SNMP
Simple Network Management Protocol (SNMP) is used in network management systems to monitor network-attached devices.
OW331_47
3
S
E C T I O N
2
Planning your Safety Instrumented System
IN THIS SECTION SIS issues to consider......................................................................................................... 5 Limitations for SIS ............................................................................................................... 6 SIS environmental specifications ........................................................................................ 7 SIS network design examples............................................................................................. 8 Planning your hardware installation .................................................................................... 9
2.1
SIS issues to consider A Safety Instrumented System (SIS) is a form of process control usually implemented in industrial processes, such as those in a factory. The SIS performs specified functions to achieve or maintain a safe state of the process when unacceptable or dangerous process conditions are detected. Consider the following issues when planning a SIS project:
The safe state is a state of the process operation where the hazardous event cannot occur. You should be able to achieve a safe state within one-half of the process safety time.
Even though safety instrumented systems are composed of elements that are similar to elements in a process control system (such as sensors, logic solvers, actuators, and support systems), you should keep the safety system separate and independent from your regular control systems.
The specified functions, or safety instrumented functions (SIF (see page 6)) should be implemented as part of an overall risk reduction strategy since they are intended to reduce the likelihood of a catastrophic release and create a safe state.
The correct operation of an SIS requires a series of equipment to function properly, such as the following:
Sensors capable of detecting abnormal operating conditions, such as high flow, low level, or incorrect valve positioning.
Logic Solvers that receive the sensor input signal(s), make appropriate decisions based on the nature of the signal(s), and change its outputs according to user-defined logic.
Final elements that take action on the process (for example, closing a valve) to bring it to a safe state due to changes in Logic Solver output.
Support systems, such as power and communications, are generally required for SIS operation. The support systems should be designed to provide the required integrity and reliability.
Functional and safety integrity requirements for an SIS are determined from hazard and operability studies (HAZOP), layers of protection analysis (LOPA), risk graphs, and so on. All techniques are mentioned in IEC 61511 and IEC 61508.
You need to verify that during SIS design, construction, and operation, these functional and safety requirements are met.
OW331_47
5
2.1 SIS issues to consider
You can verify functional requirements by design reviews, such as failure modes, effects, and diagnostic analysis (FMEDA). You can also use various types of testing, such as factory acceptance testing, site acceptance testing, and regular functional testing.
You can verify safety integrity requirements by reliability analysis. For SIS that operates on demand, it is often the probability of failure on demand (PFD) that is calculated. In the design phase, the PFD may be calculated using generic reliability data. Later on, the initial PFD estimates may be updated with field experience from the specific plant in question.
Since it is not possible to address all factors that affect SIS reliability through reliability calculations, you should also have adequate measures in place (for example, processes, procedures, and individual training and certification) to avoid, reveal, and correct SIS related failures
2.1.1 Safety Instrumented Functions (SIFs) Safety instrumented systems are applied to a process to substantially reduce the risk from costly or dangerous failures in industrial processes. The magnitude of risk reduction needed is determined from an analysis of the severity of hazardous process events and their probability of occurrence. Safety instrumented systems are typically comprised of multiple Safety Instrumented Functions (SIFs). Each SIF can be considered a control loop, defining:
Measurements (sensors) to use.
Actions to take (control elements to drive).
When to apply the actions (logic linking the measurements to the actions).
How fast to measure and react.
Every SIF has a Safety Integrity Level (SIL (see page 6)) assigned to it.
2.1.2 Safety Integrity Levels (SILs) Every SIF has a Safety Integrity Level (SIL) assigned to it. SIL is a measure of the risk reduction provided by a SIF based on four discrete levels, each representing an order of magnitude of risk reduction. The factors considered in determining a SIL include:
6
Device integrity
Diagnostics
Failures
Testing
Operation
Maintenance
OW331_47
2.2 Limitations for SIS
2.2
Limitations for SIS The following table provides the limits that are imposed on an Ovation SIS system.
2.3
COMPONENT
M AXIM UM
SISNet Repeater rings in a system
1
SISNet Repeater pairs in an Ovation SIS system
32
Logic Solvers per SIS Data Server
32 (simplex), 16 (redundant)
Logic Solvers in a SIS system
1024
SIS control modules in a Logic Solver
4
Algorithms in a SIS control module
127
Secure parameters per Logic Solver
16
Non-secure parameters per Logic Solver
24
Logic Solvers that can publish data globally on one SIS Data Server
8
Secure parameters published globally per SIS system
256
LIMIT
SIS environmental specifications The following table provides the environmental specifications for normal operation of Ovation SIS devices. SPECIFICATION
DESCRIPTION
Storage temperature
-40°C to 85°C (-40°F to 185°F)
Operating temperature
-40°C to 70°C (-40°F to 158°F)
Relative humidity
5 to 95%, non-condensing
Airborne contaminants
Severity level G3
Protection rating
IP 20, NEMA 12
Shock
10 g half-sine wave for 11 ms
Vibration
1 mm peak-to-peak from 5 to 16 Hz; 0.5 g from 16 to 150 Hz
Input power
20 rating
Electromagnetic compatibility
Per EN61326-1, Criteria A and Namur NE21
OW331_47
7
2.4 SIS network design examples
2.4
SIS network design examples There are many different ways to design an SIS network. Each system has unique requirements that must be considered when planning the SIS network. The following SIS network design examples illustrate the different design types:
Physical network design (see page 8) provides a hardware view of the SIS network.
Logical network design (see page 9) provides a conceptual view of the SIS network.
2.4.1 Physical network design example
8
OW331_47
2.5 Planning your hardware installation
2.4.2 Logical network design example
2.5
Planning your hardware installation The following list provides an overview of the basic SIS hardware installation. Refer to the specific sections for installation details. 1. Install appropriate carriers (see page 14) on the DIN rails in a hardware cabinet. 2. Install terminal blocks (see page 23) onto a carrier. 3. Install the SIS Data Servers (see page 24) onto a carrier. 4. Install Logic Solvers (see page 30) onto the terminal block. 5. Connect the field wiring. 6. Install the SIS Net Repeaters (see page 39). 7. Install extender cables (see page 42). 8. Terminate the local bus (see page 43). 9. Provide power to (see page 44):
SIS Data Servers
SIS Logic Solvers.
SIS Net Repeaters.
SIS Net Extenders. 10. If desired, install auxiliary equipment (see page 49).
OW331_47
9
2.5 Planning your hardware installation
2.5.1 Installation tools The following tools are needed to install standard Ovation SIS:
10
Standard electrical tools (voltmeter, wire cutter, wire stripper, pliers, screwdrivers).
Standard installation tools (screwdrivers, drill with standard bits).
Ethernet cable tools (crimper, cable tester).
OW331_47
S
E C T I O N
3
Hardware for Ovation SIS
IN THIS SECTION Hardware components of Ovation SIS.............................................................................. 11 SIS carriers........................................................................................................................ 14 SLS terminal blocks .......................................................................................................... 23 SIS Data Server ................................................................................................................24 SIS Logic Solvers.............................................................................................................. 28 SIS I/O channels ............................................................................................................... 33 SIS Net Repeater .............................................................................................................. 38 Fiber-optic cable\ring......................................................................................................... 41 Carrier extender cables..................................................................................................... 41 Power Supply .................................................................................................................... 44 SIS LAN switches and routers .......................................................................................... 49 Ovation SIS accessories ................................................................................................... 49
3.1
Hardware components of Ovation SIS The SIS system contains various hardware components that are described in the following table. Note: For information on installing switches and routers in your SIS system, refer to the manufacturer's installation instructions. SIS hardware components HARDWARE COMPONENT
DESCRIPTION
SIS carriers (see page 14)
Vertical or horizontal brackets that mount on the DIN rails in a cabinet and hold the SIS Logic Solvers and terminal blocks.
Simplex terminal block (see page 23)
Interfaces between I/O devices and one Logic Solver.
Duplex terminal block (see page 42)
Interfaces between I/O devices and two Logic Solvers.
SIS Data Server (see page 24)
Provides the interface between the Ovation Controller and Logic Solvers and SISNet Repeaters. The SIS Data Server can manage up to 32 Logic Solvers.
SIS Logic Solvers (see page 28)
Hardware modules that contain logic solving capability and provide an interface to 16 I/O channels.
SIS Net Repeaters (see page 38)
Provides communication between Logic Solvers that are connected to different SIS Data Servers.
Fiber optic cable/ring (see page 41)
Used to permit one SISNet Repeater connected to a SIS Data Server to communicate with another SISNet Repeater connected to a different SIS Data Server.
OW331_47
11
3.1 Hardware components of Ovation SIS
12
HARDWARE COMPONENT
DESCRIPTION
Carrier Extender cables (see page 41)
Connects power and signals between 8-wide carriers.
SIS Net Distance Extender (see page 39)
Permits SISNet Repeaters to communicate over greater distances.
Power Supply (see page 44)
Provides power to the SIS Data Server.
OW331_47
3.1 Hardware components of Ovation SIS The following graphic illustrates the SIS hardware components in a typical system.
OW331_47
13
3.2 SIS carriers
3.2
SIS carriers SIS carriers are brackets that are used to secure the SIS modules in a cabinet. The SIS carriers mount on standard 35 mm (1.38 in.) T- or G-type DIN rails in the hardware cabinets. There are two types of SIS carriers:
Horizontal carriers
1-wide carrier (dual-left/right cable extender).
2-wide carriers (SIS Data Server, SIS Net Repeater).
8-wide carriers (I/O) (can hold up to four simplex Logic Solvers).
Vertical carriers
1-wide carrier (right cable extender Vertical).
1-wide carrier (left cable extender Vertical).
4-wide Vertical (Power/SIS Data Server).
4-wide Vertical (SIS Net Repeater).
8-wide Vertical (I/O, left/right side) (can hold up to four simplex Logic Solvers).
Note: The LocalBus, including all cabling, cannot be longer than 6.5 m (21.3 ft).
3.2.1 SIS Carrier part numbers SIS carriers are brackets that are used to secure the SIS modules in a cabinet. The following table lists the available SIS carrier parts. SIS carriers CARRIER
P ART
DESCRIPTION
NUMBER
14
KJ4001X1-NA1-PW
1-Wide Horizontal Dual Right Cable Extender
KJ4001X1-NB1-PW
1-Wide Horizontal Dual Left Cable Extender
KJ2221X1-EA1-PW
2-Wide Horizontal - holds SISNet Repeaters
KJ4001X1-BA3-PW
2-Wide Horizontal - SIS Data Server w/ Redundancy and SIS + Bus Term
KJ4001X1-BE1-PW
8-Wide Horizontal - I/O with Shield Bar (Can hold up to four simplex Logic Solvers)
KJ4003X1-BC1-PW
4-Wide Vertical Power/SDS, Top
KJ4003X1-BD1-PW
4-Wide Vertical SISNet Repeater
KJ4003X1-BA1-PW
8-Wide Vertical - I/O SIS Compatible, Left Side (Can hold up to four simplex Logic Solvers)
KJ4003X1-BB1-PW
8-Wide Vertical - I/O SIS Compatible, Right Side (Can hold up to four simplex Logic Solvers)
KJ4003X1-BE1-PW
Extender, Right 1-Wide Vertical
KJ4003X1-BF1-PW
Extender, Left 1 -Wide Vertical
OW331_47
3.2 SIS carriers
3.2.2 Vertical carriers Vertical carriers mount on standard 35 mm (1.38 in.) T- or G-type DIN rails. Note: The vertical carriers are mounted properly when the lettering is in the upright position. There are six types of carriers for mounting vertically in a cabinet:
Two types of 1-wide extenders.
Two types of 4-wide carriers for power/SDS and SISNet repeaters.
Two types of 8-wide I/O interface carriers (8-wide carrier can hold up to four simplex Logic Solvers).
There are two separate cable lengths for connecting the 8-wide I/O interface carriers (8-wide carrier can hold up to four simplex Logic Solvers):
1 meter bottom cable extender.
2 meter top cable extender.
The LocalBus, including all cabling, cannot be longer than 6.5 m (21.3 ft). The following figure illustrates a cabinet containing vertical configurations.
OW331_47
15
3.2 SIS carriers
Figure 1: Cabinet with vertical SIS configuration
16
OW331_47
3.2 SIS carriers The following figure illustrates suggested spacing for vertical DIN rail installation.
Figure 2: Vertical DIN rail installation
3.2.3 To install the 1-wide carrier (dual-left/right extender cables) The 1-wide carrier is used to extend the local peer bus through the use of extender cables (see page 42) or to terminate the Local peer bus. Refer to To install carrier extender cables (see page 42) for directions on using 1-wide carriers as extenders. Use the following procedure to use the 1-wide carrier as a terminator: 1. Install a one-wide carrier onto the right/left side of the last carrier on the DIN rail. 2. Place a 120 ohms BNC terminator (KJ4010X1-BN1) onto each BNC connector on the carrier and push and turn to lock the terminator into place.
OW331_47
17
3.2 SIS carriers 3. Terminate both connectors.
Figure 3: 1-wide SIS carrier
3.2.4 To install the 2-wide power/SIS Data Server carriers Use the 2-wide power/SDS carrier to install one power supply and one SIS Data Server. 1. Install the 2-wide power/controller carrier on the DIN rails in the cabinet. 2. You can install an SIS Data Server and power supply on the 2-wide power/SIS Data Server carrier. Note: Be sure that you are using the 2-wide power/SDS carrier numbered KJ4001X1- BA3-PW or higher for any SIS installation. 3. Install the 2-wide SISNet Repeater carriers on the DIN rails if remote communication is required. (SISNet Repeater carriers can be installed anywhere between the 2-wide power/SDS carrier and the terminated one-wide carrier.) 4. Connect the carriers to any adjacent carriers by sliding together the 48 pin connectors on the sides of the carriers.
18
OW331_47
3.2 SIS carriers 5. If you are installing carriers on separate DIN rails, you will need to connect two (left and right) one-wide carriers and then connect cables to extend the LocalBus and local peer bus.
Figure 4: 2-wide SIS power/Data Server carrier
OW331_47
19
3.2 SIS carriers
3.2.5 To install the 4-wide Vertical (Power/SIS Data Server) carrier Use the 4-wide power/SIS Data Server carrier to install two power supplies and two redundant SIS Data Servers. The 4-wide power/SIS Data Server carriers supply power and communications connections for vertically mounted SIS Data Servers.
Top 4-wide power/controller carriers connect to the left 8-wide I/O interface carrier. The 96 pin connector is at the bottom of this carrier. (The left 8-wide I/O interface carrier holds cards 1-8 from top to bottom.)
Figure 5: 4-wide SIS Vertical (Power/SIS Data Server) carrier
3.2.6 To install the 8-wide I/O interface carrier (can hold up to four simplex Logic Solvers) Use the 8-wide carrier to install eight I/O cards with terminal blocks. The power and cable specifications are:
20
Local Bus that powers I/O cards uses 8.0 A. (For large systems, use the LocalBus extenders to add more power.)
Bussed field power bus that is shared by multiple I/O card pairs uses 6.5 A for each connection.
Local Bus cable =1 .2 m (3.9 ft) long.
OW331_47
3.2 SIS carriers 1. Install the 8-wide I/O interface carrier on the DIN rails in the cabinet next to the 2-wide carrier. 2. You can install Logic Solver terminal blocks on the 8-wide carrier.
Figure 6: 8-wide SIS I/O interface carrier
3.2.7 To install the 8-wide Vertical (left/right side) carrier (can hold up to four simplex Logic Solvers) Use the 8-wide Vertical carrier to install up to four Logic Solvers with terminal blocks. There are two types of 8-wide interface carriers:
Left 8-wide interface carrier (card positions 1-8 from top to bottom).
Right 8-wide interface carrier (card positions 8-1 from top to bottom).
The extender cable specifications are:
Bottom cable extender = 1.0 m (3.3 ft) nominal length.
Top cable extender = 2.0 m (6.6 ft) nominal length.
Local Bus cable = 1.2 m (3.9 ft) long.
1. Mount the DIN rail at the appropriate location. 2. Connect each 8-wide carrier to any adjacent carriers by sliding the 96-pin connectors at the top or bottom of the carriers together. Hold the carrier in position to ensure that it does not fall. 3. Turn the screws counter-clockwise to disengage the latch. With the carrier on the rail, tighten the screws clockwise to latch.
OW331_47
21
3.2 SIS carriers
Note The middle two screws are for G-rail mounting and the outer screws are for T-rail mounting. 4. If you are mounting 8-wide carriers on separate rails, use the bottom cable extender for a left-to-right bridge and the top cable extender for a right-to-left bridge. 5. Install ground wiring. For a good connection, use a signal ground cable and a block spade terminal, sized for AC/DC system power.
Figure 7: 8-wide SIS Vertical (left/right side) carrier
22
OW331_47
3.3 SLS terminal blocks
3.3
SLS terminal blocks Terminal blocks connect the wires from the devices in the plant to the SIS Logic Solvers. The terminal blocks are mounted on the SIS carriers in the Ovation cabinets.
3.3.1 SIS terminal block part numbers Terminal blocks connect the wires from the devices in the plant to the SIS Logic Solvers. The following table lists the available SIS terminal blocks. SIS terminal blocks TERMINAL
BLOCK P ART NUM BER
DESCRIPTION
KJ2201X1-HA1-PW
Connects to SIS Logic Solver (Simplex).
KJ2201X1-JA1-PW
Connects to Redundant SIS Logic Solver (Duplex).
3.3.2 To install terminal blocks Terminal blocks are mounted on the SIS 8-wide I/O carriers (can hold up to four simplex Logic Solvers) and are used to contain the SIS Logic Solvers (SLS). SIS terminal blocks are yellow. 1. Install an 8-wide I/O carrier onto a DIN rail. 2. Locate an odd slot number on the I/O interface carrier. Simplex terminal blocks occupy two slots and redundant terminal blocks occupy four slots. 3. Insert the tabs on the back of the terminal block through the slots on the carrier and push the terminal block up to lock it into place. The following figure shows a redundant terminal block installed on an I/O interface carrier. 4. Connect the field wiring.
OW331_47
23
3.4 SIS Data Server The following figure illustrates the installation of an SIS terminal block on a horizontal 8-wide carrier:
Figure 8: SIS terminal block installation example
3.4
SIS Data Server An SIS Data Server provides the interface between the Ovation Controller and Logic Solvers and SISNet Repeaters.
3.4.1 SIS Data Server part number The SIS Data Server provides the interface between the Ovation Controller and Logic Solvers and SISNet Repeaters. The following table lists the available SIS Data Server. SIS Data Server DATA SERVER
DESCRIPTION
P ART NUM BER
KJ2003X1-PW1
Ovation SIS Data Server
3.4.2 To install a simplex SIS Data Server A SIS Data Server provides the interface between the Ovation Controller and Logic Solvers and SISNet Repeaters. 1. Install a 2-wide power/SIS Data Server carrier onto a DIN rail. 2. Align the connectors on the back of the SIS Data Server with the connectors on the right slot of the 2-wide power/SIS Data Server carrier and push to attach. 3. Tighten the mounting screw.
24
OW331_47
3.4 SIS Data Server The following figure illustrates the installation of an SIS Data Server.
.
3.4.3 To power up a simplex SIS Data Server Prerequisites:
Install (see page 24) the SIS Data Server into a 2-wide carrier.
Make sure the system power supply is connected to the SIS Data Server and the power is off.
Make sure the Ovation network is set up in such a way that the SIS Data Server is able to communicate (once it is powered up) with a DHCP server.
Procedure 1. Power up the SIS Data Server's power supply. 2. Refer to the flashing LEDs (see page 27) on the SIS Data Server:
The SIS Data Server attempts to contact the DHCP server and obtain its runtime configuration. Until the DHCP transaction is complete, the SIS Data Server continues to flash its LEDs.
The SIS Data Server initializes in the ACTIVE mode. The ACTIVE LED switches to the constant ON state. The Pri CN and Sec CN LEDs flash to indicate network activity. Note: If the DHCP server does not contain a valid configuration for the SIS Data Server, the SIS Data Server remains in the ‘obtaining runtime configuration’ state until a valid configuration can be provided by the DHCP server.
OW331_47
25
3.4 SIS Data Server
3.4.4 To power up a duplex SIS Data Server Prerequisites:
Install (see page 24) the SIS Data Server into a 2-wide carrier.
Make sure the system power supply is connected to the SIS Data Server and the power is off.
Make sure the Ovation network is set up in such a way that the SIS Data Server is able to communicate (once it is powered up) with a DHCP server.
Make sure theSIS Data Server's redundant partner is running and active, and that there is a physical redundant connection between the SIS Data Server and its partner.
Procedure 1. Power up the SIS Data Server's power supply. 2. Refer to the flashing LEDs (see page 27) on the SIS Data Server:
The SIS Data Server attempts to contact the DHCP server and obtain its runtime configuration. Until the DHCP transaction is complete, the SIS Data Server continues to flash its LEDs.
The SIS Data Server communicates with its partner over the redundancy link. It detects that the partner is currently in the ACTIVE state. The SDS initializes in the STANDBY state. The STANDBY LED switches to the constant ON state. The Pri CN and Sec CN LEDs flash to indicate network activity.
Note that if the redundancy configuration obtained from the DHCP server by the two SIS Data Servers does not match, the two SIS Data Servers cannot communicate over the redundancy link. The SIS Data Server reboots while the redundant partner continues to operate in the ACTIVE mode. This cycle will repeat itself until the redundancy configuration is the same for both SIS Data Servers. Note: If the DHCP server does not contain a valid configuration for the SIS Data Server, the SIS Data Server remains in the ‘obtaining runtime configuration’ state until a valid configuration can be provided by the DHCP server.
3.4.5 To remove a redundant SIS Data Server Prerequisites 1. Make sure both SIS Data Servers in a redundant pair are running and both have active connections to the Ovation network. Procedure 1. Remove the active redundant SIS Data Server from its slot on the carrier. 2. Refer to the flashing LEDs (see page 27) on the SIS Data Server:
The partner SIS Data Server in the redundant pair detects the failure of its partner and switches to ACTIVE mode.
The STANDBY LED switches to the constant OFF state. The ACTIVE LED switches to the constant ON state. The Pri CN and Sec CN LEDs flash as per network activity. The Pri CN and Sec CN LEDs flash to indicate network activity. Note: If you remove the standby SIS Data Server from its slot on the carrier, the active partner remains unaffected and continues to run in the ACTIVE state.
26
OW331_47
3.4 SIS Data Server
3.4.6 SIS Data Server LEDs The following table describes the LED indicators on an SIS Data Server (SDS). LED
LED STATUS
D AT A SERVER STATUS
Power (Green)
On
Power is supplied to the unit.
Off
System power is not supplied to unit (possible line power problem) (Internal Fault).
Error (Red)
On (solid/continuous)
Internal fault.
Off
No Fault.
On for one second followed by all LEDs on for five seconds
Unit went through RESET due to an unrecoverable software error.
Flashing
SIS Data Server is cleared.
On
SIS Data Server is Active.
Off
SIS Data Server is on Standby.
Active (Green)
SIS Data Server is cleared. (Internal Fault) Standby (Green)
On
SIS Data Server is on Standby.
Off
SIS Data Server is Active.
Flashing
SIS Data Server is not configured.
Primary CN (Orange)
Flashing
Communication is active for Primary Physical Interface.
Off
Communication is not active for Primary Physical Interface.
Secondary CN (Orange)
Flashing
Communication is active for Secondary Physical Interface.
Off
Communication is not active for Secondary Physical Interface.
When you install and load an Ovation SIS Data Server, the LEDs flash a pattern that reveals the state of the SIS Data Server. Initialization state When you install (see page 24) an SIS Data Server in an Ovation carrier, the LEDs perform the following sequence, with one second between each phase, until the SIS Data Server is fully activated: LED
PHASE 1
PHASE 2
PHASE 3
PHASE 4
PHASE 5
Power
ON
ON
ON
ON
ON
Error
OFF
OFF
OFF
OFF
OFF
Active
OFF
ON
ON
ON
ON
Standby
OFF
OFF
ON
ON
ON
Pri CN
OFF
OFF
OFF
ON
ON
Sec CN
OFF
OFF
OFF
OFF
ON
OW331_47
27
3.5 SIS Logic Solvers Minimal Firmware load After the SIS Data Server has been initialized, the LEDs perform the following sequence to indicate that the basic SIS firmware is loaded on the SIS Data Server: LED
STATE
Power
Constant ON
Error
Constant OFF
Active
If this is the active SIS Data Server, constant ON. If this is not the active SIS Data Server, constant OFF.
Standby
If this is the standby SIS Data Server, constant ON. If this is not the standby SIS Data Server, constant OFF.
Pri CN
Dependent on network activity.
Sec CN
Dependent on network activity.
Upgraded Firmware load After the SIS Data Server has been upgraded, the LEDs perform the following sequence only once to indicate that upgraded SIS firmware is now loaded on the SIS Data Server:
3.5
LED
STATE
Power
Constant ON
Error
Constant OFF
Active
Blinks every two seconds.
Standby
Blinks every 0.5 seconds.
Pri CN
Dependent on network activity.
Sec CN
Dependent on network activity.
SIS Logic Solvers Logic Solvers are hardware modules that contain logic solving capability. There are simplex and redundant Logic Solvers. Local Logic Solvers use the same SIS Data Server but remote Logic Solvers use different SIS Data Servers. Each Logic Solver can provide an interface to a maximum of 16 I/O channels. The following table lists the available types of SIS I/O. SIS Logic Solver I/O
28
I/O TYPE
DESCRIPTION
FUNCTIONALITY
Analog input
Reports the analog value present at the channel.
Used with LSAI algorithms as input I/O references. Used with LSAO algorithms as readback references to read a 4
OW331_47
3.5 SIS Logic Solvers
I/O TYPE
DESCRIPTION
FUNCTIONALITY to 20 mA signal.
HART analog input
Reports the analog value present at the channel and up to four digital values from a HART field device.
Used with LSAI algorithms as input I/O references. Used with LSAI algorithms as readback references to read a 4 to 20 mA signal.
HART two-state output
Drives a digital valve controller output device. On value is 20 mA. Off value is configurable: either 0 mA or 4 mA (to allow for HART communications).
Used with LSDVC algorithm to drive DVC6000ESD digital valve controllers.
Digital Input
Reports the digital value present at the channel.
Used with LSDI algorithms as input I/O references when reading a digital (On/Off) signal. Used with LSDO algorithms as a readback I/O reference for a digital signal.
Digital Output
Drives the output to a digital value and holds the output at that value. Outputs immediately reflect the output value that was received. Upon receiving a configuration that indicates a change from one type of output to another, the outputs switch to the off state
Used with LSDO algorithms as output I/O references when driving a digital signal.
3.5.1 SIS Logic Solver part number Logic Solvers are hardware modules that contain logic solving capability. The following table lists the available SIS Logic Solver. SIS Logic Solver LOGIC SOLVER
DESCRIPTION
P ART NUM BER
KJ2201X1-PW1
Ovation SIS Logic Solver
3.5.2 Logic Solver specifications The following table provides the SIS Logic Solver specifications. SPECIFICATION
DESCRIPTION
Storage temperature
-40 to 85 C (-40 to 185 deg. F)
Operating temperature
-40 to 70 C (-40 to 158 deg. F)
OW331_47
29
3.5 SIS Logic Solvers
SPECIFICATION
DESCRIPTION
Relative humidity
5 to 95%, non-condensing
Airborne contaminants
ISA-S71.04-1985 Airborne Contaminants Class G3 Conformal coating
Protection rating
IP 20, NEMA 12
Shock
10 g ½-sine wave for 11 ms
Vibration
1 mm peak-to-peak from 5 to 16 Hz; 0.5 g from 16 to 150 Hz
Input power
24 VDC +- 20%, 1.0A plus field power (5.0 A total) Note: it is recommended that the Logic Solver and SIS Data Server use separate power supplies
Field power
4 A maximum (actual value depends upon channel type and field device type)
Isolation
Each channel is optically isolated from the system and factory-tested to 1500 VDC. No channel-to channel isolation.
LocalBus current
None
Mounting
In SIS terminal blocks in odd-numbered slots (1,3,5,7) on the 8-wide carrier. Simplex logic solvers take two slots and redundant Logic Solvers take four slots
Dimensions
Height 105.5 mm (4.1 in.) Width 83.8 mm (3.3 in.) Depth 110.0 mm (4.3 in.)
3.5.3 To install Logic Solvers Logic Solvers are hardware modules that contain logic solving capability. These modules communicate with each other through the SIS carriers. 1. Install an 8-wide I/O carrier (can hold up to four simplex Logic Solvers) onto a DIN rail (can hold up to four simplex Logic Solvers). 2. Install a Logic Solver terminal block on the I/O interface carrier. 3. Install a Logic Solver on the terminal block. 4. Use odd numbered slots (1,3,5,7) on an 8-wide carrier. 5. Use two slots for Simplex Logic Solvers and four slots for redundant Logic Solvers (see page 31). 6. Align the connectors on the back of the Logic Solver with the connectors on the front of the terminal block and push to attach.
30
OW331_47
3.5 SIS Logic Solvers The following figure illustrates the installation of an SIS Logic Solver.
Figure 9: SIS Logic Solver Installation example
3.5.4 Logic Solver redundancy A redundant Logic Solver configuration consists of a pair of Logic solvers mounted in adjacent carrier slots with a redundant terminal block. Each Logic Solver is powered separately. The redundant Ovation SIS Logic Solver modules are connected to the field at the redundant terminal block. No control sheet configuration is required to take advantage of Logic Solver redundancy, as the system automatically recognizes the redundant pair of cards. An integrity error alarm in a redundant Logic Solver pair will notify the operator if a Logic Solver fails. When an Ovation SIS system uses redundant Logic Solvers, this means that any two redundant Logic Solvers run in parallel at all times. Both Logic Solvers read the inputs from the I/O terminals, both execute the logic and both drive the outputs at the I/O terminals. There is no concept of primary and backup or master and slave. The only difference between the two is that the active Logic Solver communicates with both the Ovation Developer Studio and the Ovation Operator Station, and the dedicated safety network (SISnet). The standby Logic Solver is communicating only on the SISnet. If a failure is detected in one of the Logic Solvers, it automatically goes to a failed state. In this condition all its output channels are de-energized. This has no impact on the other Logic Solver or the physical outputs because the other module continues to read inputs, execute logic, and drive outputs. The transition from the active to the standby Logic Solver is therefore completely bumpless.
OW331_47
31
3.5 SIS Logic Solvers
3.5.5 SIS Logic Solver LEDs The following table describes the LED indicator patterns on an SIS Logic Solver (SLS) module. POWER LED (GREEN)
ERROR LED (RED)
ACTIVE LED (YELLOW)
ST ANDBY LED (YELLOW)
SLS STATUS
On
On
On
On
Power-up tests in progress
Flashing in sync with Standby Alternating with Error and Active
Flashing in sync with Active Alternating with Power and Standby
Flashing in sync with Error Alternating with Power and Standby
Flashing in sync with Power Alternating with Error and Active
On
On
On
Off
Solid
Flashing in sync with Active
Flashing in sync with Error
On
On
On
Solid
Flashing in sync with Active
Flashing in sync with Error
On
On
Off
Solid
Flashing in sync with Standby
On
Off
Solid On
Off
On
Off
Off
Solid On
Off
Off
On
Off
On
Redundant pair (Standby)
Flashing in sync with Error
Not initialized
Off
Non-Redundant Setup Initialized, not configured
Off
Off
Off
Redundant pair (Active) Initialized, not configured
On
Redundant pair (Standby)
Flashing
Initialized, not configured or configuration in progress
Off
Non-Redundant Setup Configured
Off
Non-Redundant Setup Configured
Off
Solid
Solid
32
On
Solid
Solid On
On
Redundant pair (Active) Not initialized
Solid
Solid On
Off
Flashing
Solid On
Not initialized
Flashing
Solid On
On
Non-Redundant Setup
Redundant pair (Active) Configured
On
Redundant pair (Standby)
Solid
Configured
On
On
On
On
Card is not fully operational
Solid
Solid
Flashing
Flashing
(Contact technical support)
On
On
Off
Off
Solid
Solid
Error detected during power-up tests (Contact technical support)
OW331_47
3.6 SIS I/O channels
3.6
SIS I/O channels A Logic Solver provides 16 channels of flexible I/O. This means that each channel can be used as one of the following:
Analog Input (see page 33).
HART Analog Input (see page 33).
HART Two-State Output (see page 34).
Digital Input (see page 35).
Digital Output (see page 36).
Note: To configure an SIS I/O channel (see page 271) provides information on configuring the SIS I/O channels.
3.6.1 Analog Input and HART Analog Input channel specifications and wiring Analog Input channel specifications SPECIFICATION
DESCRIPTION
Number of channels
16
Isolation
Each channel is optically isolated from the system and factory tested to 1500 VDC. No channel-to-channel isolation.
Nominal signal range (span)
4 to 20 mA
Full signal range
1 to 24 mA
Field circuit power per channel
24 mA
2-wire transmitter power
15.0 V minimum terminal to terminal @ 20 mA; current limited to 24 mA max.
Safety/diagnostic accuracy
2.0% of span
Resolution
16 bits 2-pole filter, corner frequency 5.68 Hz
Filtering
-3 db at 5.68 Hz -20.0 db at 40 Hz (half the sample rate)
OW331_47
33
3.6 SIS I/O channels
Figure 10: Wiring diagram and terminations for Analog Input and HART Analog Input channels
3.6.2 HART two-state output channel specifications and wiring HART two-state output channel specifications SPECIFICATION
34
DESCRIPTION
Number of channels
16
Isolation
Each channel is optically isolated from the system and factory tested to 1500 VDC. No channel-to-channel isolation.
Nominal signal range (span)
On state - 20 mA
Full signal range
0 to 24mA
Safety/diagnostic accuracy
5% of span
Resolution
12 bits
Compliance voltage
20 mA into 600 Ω load
Open-loop detection
11 mA (redundant)
Line fault detection
>40 kΩ for guaranteed open loop detection
Open circuit (optional)
18VDC
Input for de-energized relay
< 6VDC
OW331_47
3.12 Ovation SIS accessories
ITEM
SPECIFICATIONS
Input current at 24 VDC
< 70 mA ±- 20%
Relay current rating for AC operation
2.5A @ 250 VAC
Relay current rating for DC operation Note: When used in switched applications where transients and current are limited.
2.5A @ 30 VDC
Maximum AC Source
280 VAC
Maximum DC Source
30 VDC
Output series impedance (energized state)
< 0.5 Ω
Output series impedance (de-energized state)
> 1 MΩ
Maximum DC source 1 to source 2 potential
100 V
Input to Output isolation rating
300 VAC
Input to output delay (de-energize)
10 msec
Input to output delay (energize)
12 msec
Mounting configuration
Horizontal DIN rail
Lifetime limitation on number of relay cycles
>30,000 cycles or 20 years
The dimensions for the SIS Relay module are the same as for the Voltage Monitor module (see page 54).
OW331_47
53
3.12 Ovation SIS accessories
3.12.2 Voltage Monitor module The Voltage Monitor provides two independent sets of voltage monitoring circuitry in one device. Each circuit is suitable for use in both high and low de-energize to trip applications to extend the voltage input monitoring capability of the Ovation SIS Logic Solver or any other safety PLC digital input compatible with its specified output states. It also supplies a secondary output for non-safety critical monitoring for each input. Refer to the Ovation SIS Accessories Safety Manual for information on proof testing the Voltage Monitor. The state of both outputs for an associated input is controlled by the voltage level of the input with the outputs going to the de-energized state when the input goes below a specified value. The Voltage Monitor is designed to be used with the Ovation SIS Logic Solver to drive the Logic Solver's Digital Input channel or an Ovation Digital Input channel (auxiliary) based on the output of the SIS Relay module. Refer to the following figures.
Figure 23: Voltage Monitor Top View and Dimensions
54
OW331_47
3.12 Ovation SIS accessories
Figure 24: Voltage Monitor Bottom View and Connections The Voltage Monitor has the following connections:
Two four-pin connection blocks, one for each voltage monitoring channel for connection to DC or AC power source being monitored.
Two four-pin connection blocks, one for each voltage monitoring channel for connecting the output to a Logic Solver or other safety PLC monitored DI channel and an Ovation Digital Input channel (auxiliary).
The table below shows the specifications for the Voltage Monitor. Voltage Monitor Specifications ITEM
SPECIFICATIONS
Input for energized output
>18 VDC or > 80 VAC
Input for de-energized output
All Programs -> Accessories -> Communications ->Hyper Terminal. If Hyper Terminal is not installed on your computer, proceed to Step 2 If Hyper Terminal is already installed on your computer, skip to Step 4. 2. Navigate to: Control Panel -> Add/Remove Programs -> Add/Remove Windows Components -> Accessories and Utilities -> Communications -> Check "HyperTerminal." This should install Hyper Terminal on your computer. 3. Make sure the blue cable is connected to the console port on the router and COM1 serial port on the server. 4. After HyperTerminal is installed, navigate to: Start -> All Programs -> Accessories -> Communications -> HyperTerminal, and then open HyperTerminal. 5. Select icon, name connection RouterCfg, and select Connect using COM1 from the drop-down menu. 6. Once connected, go to File -> Properties -> Settings. 7. Connect using COM1, Configure Make the following settings: 9600 baud 8 1 no flow control 8. Select OK. Emulation = VT100 Set ASCII Setup to Line Delay and Character Delay of 10 milliseconds.
248
OW331_47
6.6 To create SIS network switch configuration files
9. Enter the following data (shown in bold )in the terminal: switch> ena switch# term width 132 switch# conf t switch(config)# (open the -.txt file, "ctrl a" selects all, "ctrl c" copies) right click and paste to host switch# copy running-config startup-config 10. Close the Hyper Terminal window. This initializes the Primary switch. 11. After the Primary switch is configured, open Hyper Terminal again to initialize the Partner switch: Start _> All Programs -> Accessories -> Communications -> HyperTerminal, and then open HyperTerminal. 12. Select icon, name connection RouterCfg, and select Connect using COM1 from the drop-down menu. 13. Once connected, go to File -> Properties -> Settings. 14. Connect using COM1, Configure Make the following settings: 9600 baud 8 1 no flow control 15. Select OK. Emulation = VT100 Set ASCII Setup to Line Delay and Character Delay of 10 milliseconds. 16. Enter the following data (shown in bold )in the terminal: switch> ena switch# term width 132 switch# conf t switch(config)# (open -.txt file, "ctrl a" selects all, "ctrl c" copies) right click and paste to host switch# copy running-config startup-config 17. Close the Hyper Terminal window. Both SIS network switches are now initialized.
OW331_47
249
6.7 To add an SIS I/O device number
6.7
To add an SIS I/O device number Prerequisites
Make sure you have added and configured an SIS network (see page 238).
Make sure you have added and configured an SIS Data Server (see page 241).
Make sure you have added and initialized an SIS network switch (see page 244).
Procedure After you have added and configured an SIS network, SIS Data Server, and network switch, you need to add an SIS I/O device (see page 250). However, before you do this, you need to first add a device number for the device. 1. Access the Ovation Developer Studio. 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 9. 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.
6.8
To add an SIS I/O device to the Ovation System Prerequisites
Make sure you have added and configured an SIS network (see page 238).
Make sure you have added and configured an SIS Data Server (see page 241).
Make sure you have added and configured an SIS network switch (see page 244).
Make sure you have added an SIS I/O device number (see page 250).
Procedure After you have added and configured an SIS Data Server for your Ovation system, you need to assign this Data Server to a specific Ovation Controller drop. In order to do this, you must add a new I/O device to the Controller and then assign the Data Server to this I/O device. 1. Access the Ovation Developer Studio.
250
OW331_47
6.8 To add an SIS I/O device to the Ovation System 2. Use the system tree to navigate to the I/O Devices folder: System Networks Units Drops I/O Devices 3. Right-click I/O Devices and select Insert New. The Insert New I/O Device window appears.
Figure 55: Insert New SIS I/O Devices Wizard 4. Select an I/O Device Number number sequentially, starting at 5 to a maximum of 11. Select Ovation SIS for the I/O Device Type.
OW331_47
251
6.8 To add an SIS I/O device to the Ovation System 5. Select the Finish button. The configuration window for the new SIS I/O device appears. (Notice that the field for the Node Record Point Name is blank.)
Figure 56: SIS New I/O Devices Config tab 6. Enter the following attributes for the new I/O device. ATTRIBUTE
DESCRIPTION
I/O Device Number
Number of the SIS I/O device. This is displayed by the system.
I/O Device Type
Should be Ovation SIS. This is displayed by the system.
Node Record Point Name
Comes from the Node point (RN record type). Refer to To associate a Node point with an SIS I/O device (see page 253) for instructions on creating the Node point.
SIS identifier
This is displayed by the system.
Network Interface
252
Message Port
UDP port used for communication between the SIS Data Server and the Ovation Controller. This is a socket number. The recommended value is 2080, DO NOT change this number.
Alarm Handler Port
Transfers alarm messages between the SIS Data Server and the Ovation Controller. This is a socket number. The recommended value is 3051, DO NOT change this number.
Network Interface Connection
This can be a single or dual network connection.
OW331_47
6.8 To add an SIS I/O device to the Ovation System
ATTRIBUTE
DESCRIPTION
Network Interface
Number of the SIS network (N1 - N4).
Backup Network Interface
Number of the backup SIS network (N1 - N4).
Primary Network Interface IP Address
IP Address of primary network interface (typically provided by the System Administrator).
Subnet Mask
Identifies the range of IP addresses that are on a local network.
Partner Network Interface IP Address
IP Address of partner network interface (typically provided by the System Administrator).
Subnet Mask
Identifies the range of IP addresses that are on a local network.
7. Select the Apply button and the new SIS I/O Device appears in the Ovation Studio hierarchy tree. 8. You can right-click on the new I/O Device and select from the following menu items: MENU ITEM
DESCRIPTION
Open
Opens the selected item for editing.
Delete
Removes the selected item.
Search
Searches the database for items that match specified criteria.
Where Used
Searches the database to find and identify where an item is used by another item in the system.
Find
Performs a quick name search for items in the database.
Consistency Check
Displays a window that checks the consistency of Ovation components.
6.8.1 To associate a Node point with an SIS I/O device Prerequisites
Make sure you have added and configured an SIS network (see page 238).
Make sure you have added and configured an SIS Data Server. (see page 241)
Make sure you have added and configured an SIS network switch (see page 244).
Make sure you have added an SIS I/O device number (see page 250).
Make sure you have you have added an SIS I/O device (see page 250).
Procedure After you have added an SIS I/O device, you need to create a Node point and assign it to the new I/O device. 1. Access the Ovation Developer Studio.
OW331_47
253
6.8 To add an SIS I/O device to the Ovation System
2. Use the system tree to navigate to the Node Points folder: System Networks Units Drops (appropriate Controller drop) Points Node Points 3. Right-click on Node Points and select Insert New. The Insert New Node Points Wizard appears.
4. Enter a point name and select the desired frequency for the point. 5. Select Finish. The configuration window for the Node point appears. 6. Select the Hardware tab.
254
OW331_47
6.9 To assign an SIS I/O Data Server to an SIS I/O Device 7. Select the SIS I/O device you want to associate with the Node point. Select the I/O task index.
8. After the Node point is created, select the Refresh button and the name of the Node point appears in the Node Record Point Name field in the New I/O devices window (see page 250).
6.9
To assign an SIS I/O Data Server to an SIS I/O Device Prerequisites
Make sure you have added and configured an SIS network (see page 238).
Make sure you have added and configured an SIS Data Server (see page 241).
Make sure you have added and configured an SIS network switch (see page 244).
Make sure you have added an SIS I/O device number (see page 250).
Make sure you have added and configured an SIS I/O device (see page 250).
Procedure After you have added and configured an SIS Data Server and an SIS I/O device to your Ovation system, you need to assign this Data Server to a specific Ovation Controller drop. 1. Access the Ovation Developer Studio. 2. Use the system tree to navigate to the Data Server folder: System Networks Drops (appropriate Controller drop) I/O Devices SIS I/O Device Data Servers
OW331_47
255
6.9 To assign an SIS I/O Data Server to an SIS I/O Device 3. Right-click Data Servers and select Insert New. The Insert New SIS Data Server window appears.
Figure 57: Insert New SIS Data Servers Wizard 4. Enter the following attributes for the new I/O Data Server Device.
256
ATTRIBUTE
DESCRIPTION
Data Server Name
This is a pull-down list of the SIS Data Servers that you defined under the SIS Network folder.
SIS Data Server ID
Number assigned to the Data Server.
OW331_47
6.9 To assign an SIS I/O Data Server to an SIS I/O Device 5. Select Finish. The configuration window for the new SIS I/O Data Server appears.
Figure 58: New SIS Data Servers Config tab 6. Enter the following attributes for the new I/O Data Server. ATTRIBUTE
DESCRIPTION
Data Server Name
This is a pull-down list of the SIS Data Servers that you defined under the SIS Network folder.
SIS Data Server ID
Number assigned to the Data Server.
Ovation Point Name
Ovation point that determines the quality of the Data Server.
7. Select Apply and the new SIS I/O Device appears in the Ovation Studio hierarchy tree. 8. You can right-click on the new I/O Data Server and select from the following menu items:
OW331_47
MENU ITEM
DESCRIPTION
Open
Opens the selected item for editing.
Delete
Removes the selected item.
Search
Searches the database for items that match specified criteria.
Where Used
Searches the database to find and identify where an item is used by another item in the system.
Find
Performs a quick name search for items in the database.
Consistency check
Displays a table that provides data about SIS points.
Create Switch Configuration Function
Accesses the Ovation SIS Switch Engineering Tool window (see page 246).
257
6.9 To assign an SIS I/O Data Server to an SIS I/O Device
6.9.1 Viewing SIS points in the Developer Studio hierarchy Ovation points are created through the use of DBID or manually by adding a point using the Ovation Developer Studio. (Refer to Planning Your Ovation System for information about DBID or to the Ovation Developer Studio User Guide for information about adding a point.) Ovation points become SIS points when the points are used by the Control Builder on an SIS control sheet. When the SIS control sheet is saved, the points will appear in the Developer Studio hierarchy in the SIS Points folder under the SIS Data Servers folder When the control sheet is loaded to the Logic Solver, the points now appear in the SIS Points folder under the Logic Solvers folder. The SIS points also appear in the WorkPad area below the Studio hierarchy tree, as seen in the following figure.
258
OW331_47
6.9 To assign an SIS I/O Data Server to an SIS I/O Device
6.9.2 Removing Ovation SIS points from SIS control sheets If you want to remove a SIS point from its SIS control status, you can do this through the Ovation Control Builder: 1. Access the Ovation Control Builder (refer to Ovation Control Builder User Guide for details). 2. Open the control sheet that contains the SIS points that you want to remove from SIS control.
OW331_47
259
6.10 To configure SIS LAN network switches 3. Remove the desired SIS points and save the sheet. 4. Load the sheet to the applicable Logic Solver. The points will move from the SIS Points folder under the Logic Solver to the SIS Points folder under the SIS Data Server folder. This indicates that the points are no longer used as SIS points in a SIS control scheme.
6.10 To configure SIS LAN network switches The SIS Switch Engineering Tool enables you to configure switches (such as Cisco IE 3000) that are used in an SIS network. Prerequisites
Make sure you have added and configured an SIS network (see page 238).
Make sure you have added and configured an SIS Data Server (see page 241).
Make sure you have added an SIS network switch (see page 244).
Make sure you have created SIS network switch configuration files (see page 246).
Make sure you have added an SIS I/O device number (see page 250).
Make sure you have added an SIS I/O device (see page 250).
Make sure you have associated a Node point (see page 253) with the SIS I/O device.
Make sure you have assigned a SIS Data Server (see page 255) to the SIS I/O device.
Procedure 1. Access the Ovation Developer Studio. 2. Use the system tree to navigate to the SIS Networks folder: System Networks SIS Networks 3. Right-click on the desired SIS Network and select Create Switch Configuration Function. The Ovation SIS Switch Engineering Tool window appears. This window is used to configure DHCP and Switch configuration files.
260
OW331_47
6.10 To configure SIS LAN network switches 4. Select the Configuration Files tab.
Figure 59: Ovation SIS Switch Engineering Tool window (Configuration Files tab) 5. Select the Create Files button. This configures the two text files used to create (see page 246) the Primary switch and the Partner switch and now also creates a DHCP text file: - .txt for example SISNet1-SW301.txt - .txt For example SISNet1-SW302.txt - DHCP.txt For example SISNet1- DHCP.txt
OW331_47
261
6.10 To configure SIS LAN network switches
Note: Use the following steps to send the applicable switch configuration file and the DHCP file to each switch (Primary and Partner switch). 6. Select the Telnet Connection tab.
Figure 60: Ovation SIS Switch Engineering Tool window (Telnet Connection tab)
FIELD OR BUTTON
DESCRIPTION
Switch Name/IP
Name or IP address of the switch you want to configure.
Telnet Port
Name of the Telnet port.
Options
262
Connect
Tool will request telnet password and then connect to the switch.
Disconnect
Too will disconnect the switch.
Show Running Config
Sends the switch command "Show Running Config" to the switch. The display area shows the current running configuration. Requires a password to run (default is ChangeMe).
Show Version
Sends the switch command "Show Running Config" to the switch. The display area shows the current running configuration.
OW331_47
6.11 To add and configure SIS Logic Solvers in the Ovation System
FIELD OR BUTTON
DESCRIPTION
Load File
Copies a configuration file into the switch. This file can be any of the files created in the Configuration Files tab. You will be prompted to select the desired file and enter the password. Then, you will be asked if you want to copy the configuration to the startup configuration for the switch.
Apply
Starts the selected option process.
7. Enter the applicable switch name or IP address for the Primary switch. 8. Select the Connect button and select Apply. You will be prompted to enter a password (the default password is ChangeMe). 9. Select the Load File button and select Apply. You will be prompted to select the desired file and to enter a password (the default password is ChangeMe). Select the - DHCP.txt file. Next, you will be asked if you want to copy the configuration to the startup configuration for the switch. 10. Select the Load File button and select Apply. You will be prompted to select the desired file and to enter a password (the default password is ChangeMe) Select the - .txt file. Next, you will be asked if you want to copy the configuration to the startup configuration for the switch. 11. Select the Disconnect button and select Apply. 12. Repeat Steps 7 through 11 to configure the Partner switch.
6.11 To add and configure SIS Logic Solvers in the Ovation System Prerequisites
Make sure you have added and configured an SIS network (see page 238).
Make sure you have added and configured an SIS Data Server (see page 241).
Make sure you have added and configured an SIS network switch (see page 244).
Make sure you have added an SIS I/O device number (see page 250).
Make sure you have added and configured an SIS I/O device (see page 250).
OW331_47
263
6.11 To add and configure SIS Logic Solvers in the Ovation System
Procedure You can add up to 32 Logic Solvers to an SIS Data Server. 1. Access the Ovation Developer Studio. 2. Use the system tree to navigate to the Logic Solvers folder: System Networks Units Drops (appropriate Controller drop) I/O Devices SIS I/O Device Data Servers Logic Solvers 3. Right-click Logic Solvers and select Insert New. The Insert New Logic Solver window appears.
Figure 61: Insert New SIS Logic Solvers Wizard
264
OW331_47
6.11 To add and configure SIS Logic Solvers in the Ovation System
4. Enter the following attributes for the new Logic Solver. ATTRIBUTE
DESCRIPTION
SIS Logic Solver Name
Enter a unique Logic Solver name that is not used anywhere else in your system.
Redundant SIS Logic Solver
Select this checkbox to enable the Logic Solver to work in redundant mode (if a partner is present). You cannot change the redundancy mode after you have added the Logic Solver.
SIS Logic Solver Slot Number
This is the slot used by the Logic Solver. Slot numbers range from 1 to 32 and must be unique within the SIS Data Server. You cannot change the slot number after you have added the Logic Solver.
5. Select the Finish button. The configuration window for the new SIS Logic Solver appears. Enter the appropriate values for the attributes in each tab and then select OK.
Config tab (see page 266).
General tab (see page 267).
Proof Testing tab (see page 268). 6. The new Logic Solver appears in the Ovation Studio hierarchy tree. Note: When a Logic Solver is added to the Studio, four control modules (see page 280) are automatically created and appear under the Logic Solver in the Studio tree. Sixteen I/O channels are also included under each Logic Solver and they appear in the Studio WorkPad area. 7. You can right-click on the new Logic Solver and select from the following menu items:
OW331_47
MENU ITEM
DESCRIPTION
Open
Opens the selected item for editing.
Delete
Removes the selected item.
Search
Searches the database for items that match specified criteria.
Where Used
Searches the database to find and identify where an item is used by another item in the system.
Find
Quick name search for items in the database.
Lock
Closes the Logic Solver so that you cannot load data to it.
Unlock
Opens the Logic Solver so that you can load data to it.
Consistency Check
Displays a window that checks the consistency of Ovation components.
Load (see page 285)
Performs load operation if the Logic Solver is not loaded, sends script configuration to Logic Solver, and loads shadow algorithms into Ovation Controller.
Clear
Clears the Logic Solver. Prepares the Logic Solver for upgrade by removing configuration.
Reboot
Displays a Restart Wizard which is used to restarts the Logic Solver.
Create Switch Configuration
Accesses the Ovation SIS Switch Engineering Tool window (see page 246). This tool creates the switch configuration files for the network switches.
265
6.11 To add and configure SIS Logic Solvers in the Ovation System
6.11.1 Configuring the Logic Solver Config tab After you have added an SIS Logic Solver, use the following Config tab to configure the Logic Solver.
Figure 62: New SIS Logic Solvers window (Config tab) Attributes in New SIS Logic Solvers window (Config tab) ATTRIBUTE
DESCRIPTION
SIS Logic Solver Name
Enter a unique Logic Solver name that is not used anywhere else in your system.
Redundant SIS Logic Solver
Select this checkbox to enable Logic Solver to work in redundant mode (if a partner is present). You cannot change the redundancy mode after you have added the Logic Solver.
SIS Logic Solver Slot Number
This is the slot used by the Logic Solver. Slot numbers range from 1 to 32 and must be unique within the SIS Data Server. You cannot change the slot number after you have added the Logic Solver.
266
Revision
CRC code which reflects the configuration of the entire Logic Solver as calculated by the Ovation Developer Studio and is compared with the code that is calculated by the Logic Solver at load time.
SIS Data Server
SIS Data Server to which this Logic Solver is directly connected through backplane connections. Name is entered by the system.
GSLOT Identifier
Logic Solver global identifier. This is set by the system and is used as an identifier for global Logic Solvers in the SISNet.
All I/O channels CRC
CRC code which reflects the configuration of all I/O channels as calculated by the Ovation Developer Studio and is compared with the code that is calculated by the Logic Solver at load time. This code is the latest database CRC value.
OW331_47
6.11 To add and configure SIS Logic Solvers in the Ovation System
ATTRIBUTE
DESCRIPTION
Diagnostic/Status Ovation Point Name
Enter the name of an Ovation point that will hold status information.
6.11.2 Configuring the Logic Solver General tab After you have added an SIS Logic Solver, use the following General tab to configure the Logic Solver.
Figure 63: New SIS Logic Solvers window (General tab)
OW331_47
267
6.11 To add and configure SIS Logic Solvers in the Ovation System Attributes in New SIS Logic Solver window (General tab) ATTRIBUTE
DESCRIPTION
Scan Rate
This is the Logic Solver loop time. The available scan rates are 50ms, 100ms, 150ms, and 200 ms per period. The default rate (see page 315) is 50 ms. Since the SIS Data Server sends control module information to the Controller every second, scan rate is not related to update time.
Shadow block Control Task
Refers to a specific Controller area where all the control sheets that contain shadow algorithms are scanned at the same frequency. Points are grouped by control tasks so they can be updated (scanned) at different rates. The rate is set in the applicable Ovation configuration tool during configuration for a Controller drop.
Secure parameters Publish secure params globally
Select this checkbox to enable this Logic Solver to publish secure parameters globally over the SIS Network.
Enable high-density secure parameters
This checkbox is currently enabled, but is disabled for editing. This option activates 16 secure parameters for each Logic Solver.
Nonsecure parameters Nonsecure parameters 1 - 24
Identifies nonsecure parameters associated with this Logic Solver.
6.11.3 Configuring the Logic Solver Proof Testing tab After you have added an SIS Logic Solver, use the Proof Testing tab (as shown in the following figure) to configure the Logic Solver. Ovation SIS performs an automatic diagnostic whenever a Logic Solver reboots. You can use the parameters in the Proof Testing tab to set the desired configuration for diagnostics:
You can configure the Proof test timer period so that when the timer period expires, there will be an automatic transfer to the backup Logic Solver. This forces a reboot and diagnostics are performed (only available for redundant Logic Solvers). OR An alarm can be generated to indicate that you should reboot the Logic Solver in order to perform the diagnostics.
268
OW331_47
6.11 To add and configure SIS Logic Solvers in the Ovation System
You can configure the Proof test timer to generate an alert before the Proof Test timer will expire. The alert is sent to the Ovation Error Log.
If a Logic Solver fails the power diagnostic during boot up, it will try again. If it fails a second time, the Logic Solver will enter a "reduced mode." This mode will be indicated through the Logic Solver RN record.
Figure 64: SIS Logic Solvers configuration dialog (Proof Testing tab) Attributes in New SIS Logic Solvers window (Proof Testing tab) ATTRIBUTE
DESCRIPTION
Proof test interval (for this Logic Solver. See SIS Safety Manuals for additional information.) Proof test interval (years)
This, plus the days count, is the total proof test interval.
Proof test interval (days)
This, plus the years count, is the total proof test interval.
Proof test reminder alert Proof test remind alert due (days)
This is the number of days until the user is reminded to execute a proof test.
Enable automatic proof test to run at reminder time
Select this checkbox to allow a proof test to run automatically without operator attention (only available for redundant Logic Solvers).
OW331_47
269
6.12 To add an SIS control sheet to the SIS Ovation system
6.12 To add an SIS control sheet to the SIS Ovation system Prerequisites
Make sure you have added and configured an SIS network (see page 238).
Make sure you have added and configured an SIS Data Server (see page 241).
Make sure you have added and configured a Network switch (see page 244).
Make sure you have added an I/O device number (see page 250).
Make sure you have added and configured an SIS I/O device (see page 250).
Make sure you have assigned a Data Server (see page 255) to the SIS I/O device.
Make sure you have added and configured an SIS Logic Solver (see page 263).
Procedure 1. Access the Ovation Developer Studio. 2. Use the system tree to navigate to the Control Sheets folder: System Networks Drops (appropriate Controller drop) I/O Devices SIS I/O Device Data Servers Logic Solvers Control Modules Control Sheets 3. Right-click on Control Sheets and select Insert New. The Insert New Control Sheet window appears.
Figure 65: Insert New Control Sheet window
270
OW331_47
6.13 To configure an SIS I/O channel
4. Enter the following attributes for the new control sheet. ATTRIBUTE
DESCRIPTION
Algorithm Count
Keeps track of the number of algorithms on a sheet.
Sheet Name
Defines how the sheet is described in the system. This name (up to 30 characters) appears in the Control Sheets section of the Studio hierarchy.
Sheet Number
Short reference number (maximum of three characters). This number is used to identify the sheet to the user, but is not the unique internal .svg file number that is assigned by the Control Builder.
Sheet Component
Defines the sheet component code. Component codes are text strings that are assigned to each sheet or supplemental document that represent the sheet's or document's location in the hierarchy.
5. Select OK. The Ovation Control Builder opens. 6. Draw the desired control scheme and save the sheet. (Refer to the Ovation Control Builder User Guide for more information.)
6.13 To configure an SIS I/O channel Prerequisites
Make sure you have added and configured an SIS network (see page 238).
Make sure you have added and configured an SIS Data Server (see page 241).
Make sure you have added and configured an SIS I/O device (see page 250).
Make sure you have assigned a SIS Data Server (see page 255) to the SIS I/O device.
Make sure you have added and configured an SIS Logic Solver (see page 263).
Procedure 1. Access the Ovation Developer Studio. 2. Use the system tree to navigate to the I/O Channels folder: System Networks Drops (appropriate Controller drop) I/O Devices SIS I/O Device SIS Data Servers Logic Solvers I/O Channels
OW331_47
271
6.13 To configure an SIS I/O channel
Note: Sixteen I/O channels are also included under each Logic Solver and they appear in the Studio WorkPad area. 3. Right-click on I/O Channels and select Open. The I/O Channel window appears.
Figure 66: I/O Channel window (Config tab) 4. Enter the following attributes for the I/O Channel in the Config tab. Each channel type has the same attributes in the Config tab . ATTRIBUTE
DESCRIPTION
Channel Number
Name of the channel (1 through 16)
Enabled
When box is checked, the channel is enabled and can be used.
Channel Type
Type of channel that will be used: Undefined Channel Type. Analog Input Channel (see page 273). HART Analog Input Channel (see page 275). HART Two-state Output Channel (see page 277). Digital Input Channel (see page 279). Digital Output Channel (see page 280).
Ovation Point
Name of the Ovation point that is assigned to the channel.
I/O channel CRC (see page 2)
CRC code which reflects the configuration of this I/O channel as calculated by the Ovation Developer Studio and is compared with the code that is calculated by the Logic Solver at load time.
5. After you have defined the attributes in the Config tab, use the applicable Attributes tab to enter values for the selected Channel Type. 6. After you have entered the applicable attribute values in the Attributes tabs, select OK.
272
OW331_47
6.13 To configure an SIS I/O channel
6.13.1 Configuring an Analog Input Channel 1. After you have configured the Config tab (see page 271) for an Analog Input channel, use the following Attributes tab to configure an Analog Input Channel.
Figure 67: I/O Channel window for SIS Analog Input channel (Attributes tab) Attributes for Analog Input Channel ATTRIBUTE
DESCRIPTION
NAMUR alarming
When this box is checked, NAMUR alarming is performed on the channel. If enabled and if the transmitter supports it, any analog value that is outside the NAMUR limits (106.25% top limit and -2.5% bottom limit) for four seconds has its status marked as BAD:Sensor Failure. (NAMUR is an international association of automation technology in process control industries.)
Analog over range pct
The percent value at which the analog value is considered overrange. If the signal is above this limit, its status indicates the value is limited high.
Analog under range pct
The percent value at which the analog value is considered underrange. If the signal is below this limit, its status indicates the value is limited low.
Conversion type
Raw data is converted to point values. Indirect is the only type of conversion currently in use.
Bottom of Scale
The low scale value, engineering units code, and number of digits to the right of the decimal point associated with OUT.
Top of Scale
The high scale value, engineering units code, and number of digits to the right of the decimal point associated with OUT.
OW331_47
273
6.13 To configure an SIS I/O channel
ATTRIBUTE
DESCRIPTION
Bad if limited
When this box is checked, point status is BAD if the point value is outside of the configured over/under range.
2. Enter the applicable Attributes and select OK.
274
OW331_47
6.13 To configure an SIS I/O channel
6.13.2 Configuring a HART Analog Input Channel 1. After you have configured the Config tab (see page 271) for a HART Analog Input channel, use the following Attributes tab to configure a HART Analog Input Channel.
Figure 68: I/O Channel window for SIS HART Analog Input channel (Attributes tab)
OW331_47
275
6.13 To configure an SIS I/O channel Attributes for HART Analog Input Channel ATTRIBUTE
DESCRIPTION
Loop current mismatch detection
When checked, you can enable the detection of a loop current mismatch between the analog and digital current values from the HART device.
Analog over range pct
The percent value at which the analog value is considered overrange. If the signal is above this limit, the status of the Function Block's Analog parameter associated with this channel is high limited.
Conversion Type
Raw data is converted to point values. Indirect is the only type of conversion currently in use.
Bottom of Scale
The low scale value, engineering units code, and number of digits to the right of the decimal point associated with OUT.
Top of Scale
The high scale value, engineering units code, and number of digits to the right of the decimal point associated with OUT.
Bad if Limited
When this box is checked, point status is BAD if the point value is outside of the configured over/under range.
Analog under range pct
The percent value at which the analog value is considered underrange. If the signal is below this limit, its status indicates the value is limited low.
Enable NAMUR alarming
When this checkbox is checked, NAMUR alarming is performed on the channel. If enabled and if the transmitter supports it, any analog value that is outside the NAMUR limits (106.25% top limit and -2.5% bottom limit) for four seconds has its status marked as BAD:Sensor Failure. (NAMUR is an international association of automation technology in process control industries.)
HART Errors Ignore PV Out out Limits
This field is reserved for future releases.
Ignore Analog-Digital Mismatch
This field is reserved for future releases.
Ignore PV Output Saturated
This field is reserved for future releases.
Ignore PV Output Fixed
This field is reserved for future releases.
Ignore Loss of Digital Comms
This field is reserved for future releases.
Ignore Field Device Malfunction
This field is reserved for future releases.
2. Enter the applicable Attributes and select OK.
276
OW331_47
6.13 To configure an SIS I/O channel
6.13.3 Configuring a HART Two-state Output Channel 1. After you have configured the Config tab (see page 271) for a HART Two-state Output channel, use the following Attributes tab to configure a HART Two-state Output Channel.
Figure 69: I/O Channel window for HART Two-state output channel (Attributes tab)
OW331_47
277
6.13 To configure an SIS I/O channel Attributes for HART Two-state output Channel ATTRIBUTE
DESCRIPTION
Loop current mismatch detection
When checked, you can enable the detection of a loop current mismatch between the analog and digital current values from the HART device.
The slot 0 device code from the AO card
The slot 0 device variable code sent digitally from the Analog Output card. Defines the HART variable whose data is reported by HART_VAL0.
The slot 1 device code from the AO card
The slot 1 device variable code sent digitally from the Analog Output card. Defines the HART variable whose data is reported by HART_VAL1.
The slot 2 device code from the AO card
The slot 1 device variable code sent digitally from the Analog Output card. Defines the HART variable whose data is reported by HART_VAL2.
The slot 3 device code from the AO card
The slot 1 device variable code sent digitally from the Analog Output card. Defines the HART variable whose data is reported by HART_VAL3.
Enabled HART slot 0
When checked, HART slot 0 is enabled and can be used.
Enabled HART slot 1
When checked, HART slot 1 is enabled and can be used.
Enabled HART slot 2
When checked, HART slot 2 is enabled and can be used.
Enabled HART slot 3
When checked, HART slot 3 is enabled and can be used.
4th Variable Point Name
Variable returned by HART transmitter, in Engineering Units. Read digitally.
Primary Variable Point Name
Variable returned by HART transmitter, in Engineering Units. Read digitally.
Second Variable Point Name
Variable returned by HART transmitter, in Engineering Units. Read digitally.
Tertiary Variable Point Name
Variable returned by HART transmitter, in Engineering Units. Read digitally.
HART Errors
Ignore PV Out out Limits
This field is reserved for future releases.
Ignore Analog-Digital Mismatch
This field is reserved for future releases.
Ignore PV Output Saturated
This field is reserved for future releases.
Ignore PV Output Fixed
This field is reserved for future releases.
Ignore Loss of Digital Comms
This field is reserved for future releases.
Ignore Field Device Malfunction
This field is reserved for future releases.
2. Enter the applicable Attributes and select OK.
278
OW331_47
6.13 To configure an SIS I/O channel
6.13.4 Configuring a Digital Input Channel 1. After you have configured the Config tab (see page 271) for a Digital Input channel, use the following Attributes tab to configure a Digital Input Channel.
Figure 70: I/O Channel window for SIS Digital Input channel (Attributes tab) Attributes for Digital Input Channel ATTRIBUTE
DESCRIPTION
Detect open and short circuit
When this box is checked, this enables the card to detect open and short circuits in field wiring, provided that external resistors have been added to the wiring.
Inverted
When this box is checked, the value reported by the LSDI algorithm will be the opposite value of that on the physical input channel.
2. Enter the applicable Attributes and select OK. Once the Input channel is defined, a corresponding Ovation raw input point needs to be created.
OW331_47
279
6.14 To configure SIS control modules
6.13.5 Configuring a Digital Output Channel 1. After you have configured the Config tab (see page 271) for a Digital Output channel, use the following Attributes tab to configure a Digital Output Channel.
Figure 71: I/O Channel window for SIS Digital Output channel (Attributes tab) Attributes for Digital Output Channel ATTRIBUTE
DESCRIPTION
Detect open and short circuit
When this checkbox is checked, this enables the card to detect open and short circuits, provided that external resistors have been added to the wiring.
2. Enter the applicable Attributes and select OK.
6.14 To configure SIS control modules Prerequisites
Make sure you have added and configured an SIS network (see page 238).
Make sure you have added and configured an SIS Data Server (see page 241).
Make sure you have added and configured a Network switch (see page 244).
Make sure you have added an I/O device number (see page 250).
Make sure you have added and configured an SIS I/O device (see page 250).
Make sure you have assigned a SIS Data Server (see page 255) to the SIS I/O device.
Make sure you have added and configured an SIS Logic Solver (see page 263).
Procedure 1. Access the Ovation Developer Studio.
280
OW331_47
6.14 To configure SIS control modules 2. Select the desired Logic Solver. The four control modules for that Logic Solver appear in the Studio tree under the Logic Solver. 3. Right-click on the desired control module and select Open. The following window appears.
Figure 72: Control Module window (Config tab) ATTRIBUTE
DESCRIPTION
Control Module CRC
CRC code which reflects the configuration of this control module as calculated by the Ovation Developer Studio and is compared with the code that is calculated by the Logic Solver at load time.
User Documentation Module Name
Name of the control module which is contained in the Logic Solver.
Module Number
Number of the control module which is contained in the Logic Solver.
Module Revision
Revision of the control module which is contained in the Logic Solver.
Diagnostic/Status Ovation Point Name
OW331_47
Enter the name of an Ovation point that will hold status information.
281
6.15 To configure SIS digital points for alarming with timestamps
Note: When you attempt to load an SIS Logic Solver (see page 285), a Confirm window appears that lists all the SIS devices for that Logic Solver that may be affected by the load. The previous CRC value for each device is listed and the Current CRC value is also listed. The Current value is the CRC value that the device will change to if you continue with the load process.
6.15 To configure SIS digital points for alarming with timestamps 1. Create an Ovation point through the use of DBID or manually add a point using the Ovation Developer Studio. (Refer to Planning Your Ovation System for information about DBID or to the Ovation Developer Studio User Guide for information about adding a point.) 2. If you want to configure digital points for alarms that display a timestamp, perform the following: a) Use the Developer Studio system tree to navigate to the Alarm item: System (or appropriate level such as Network, Unit, or Drop) Configuration Alarm b) Right-click on the Alarm item and choose Open. The Alarm window appears. c) Scroll to select the Alarm Display tab by using the horizontal scroll bar.
282
OW331_47
6.15 To configure SIS digital points for alarming with timestamps d) Select Yes for the Show Millisecond Resolution field, and 100 Milliseconds for the Millisecond Format field. All points under this setting in the tree will now contain these settings for timestamps.
Note: Check to confirm that the OPP Rate for the point is set to U (User Defined). You can use Point tab in the Point Information tool to verify the setting. 3. Download the changes to the drop and reboot the drop for the changes to take effect. 4. In order to make the new point an SIS point, open the Control Builder and use the point on an SIS control sheet. Save the control sheet. (Refer to the Ovation Control Builder User Guide for more information.) 5. Access the Ovation Developer Studio hierarchy tree. The point now appears in the SIS Points folder under the SIS Data Servers folder. 6. Load the control sheet to the Logic Solver. 7. The point now appears in the SIS Points folder under the Logic Solvers folder.
OW331_47
283
6.16 To view SIS points
6.16 To view SIS points SIS points will appear in the WorkPad section of the Studio interface after the applicable Logic Solver has been successfully loaded. When the Logic Solver is loaded, the points will move from the parent Data Server to the Logic Solver. Procedure 1. Use the system tree to navigate to the SIS Points folder: System Networks Drops (appropriate Controller drop) I/O Devices SIS I/O Device SIS Data Servers Logic Solvers SIS Points 2. Click on the Applicable points icon (Analog, Digital, or Algorithm) and any points that have been loaded into the parent Logic Solver display in the WorkPad section.
284
OW331_47
S
E C T I O N
7
Using Ovation SIS
IN THIS SECTION Loading Logic Solvers..................................................................................................... 285 Using Point Information (PI) to identify SIS points .......................................................... 287 Viewing SIS Tuning windows for SIS algorithms ............................................................ 290 Forcing an algorithm input value ..................................................................................... 298 Restarting a Logic Solver ................................................................................................ 307 Requiring a reset before outputs can become energized ............................................... 309 Configuring the Logic Solver's response to detected faults ............................................ 309 Choosing the Logic Solver scan rate .............................................................................. 315 Loading to a running process.......................................................................................... 315 Restarting a Logic Solver after a power failure ............................................................... 316 Proof testing the Logic Solver ......................................................................................... 316 Customizing your Ovation Control Builder frame............................................................ 318 Upgrading SIS firmware ..................................................................................................319 Using Fault Codes for SIS (66, 3, 8) ............................................................................... 321 SIS Diagnostics ............................................................................................................... 322 SIS Logic Solver events .................................................................................................. 324
7.1
Loading Logic Solvers Logic Solvers contain the SIS logic solving capability and provide an interface to 16 I/O channels. When you want to update the logic solving for your safety applications, you may need to load new or edited logic into the Logic Solver.
7.1.1 To load an SIS Logic Solver Prerequisites
Make sure you have SIS load privileges.
Procedure All loads to Logic Solvers are total loads. Incremental loads are not allowed and you cannot load multiple Logic Solvers at the same time. 1. Access the Ovation Developer Studio.
OW331_47
285
7.1 Loading Logic Solvers
2. Use the system tree to navigate to the Logic Solvers folder: System Networks Units Drops (appropriate Controller drop) I/O Devices SIS I/O Device Data Servers Logic Solvers 3. Select the Logic Solver you want to load. 4. If the Logic Solver is locked, right-click and select Unlock. A confirmation dialog window appears. 5. On the confirmation dialog, click Confirm to unlock the Logic Solver. Note: Locking or unlocking a Logic Solver generates an event in the event log. 6. Navigate to the Logic Solver in the SIS Network. 7. Right-click and select Load. 8. A Confirm window appears listing the Previous CRC codes and Current CRC codes of the Logic Solver, the four control modules, and the I/O channels. The Previous CRC values are the codes of the object before you perform a load to the Logic Solver. The Current CRC values are the codes that the object will have after you perform a load to the Logic Solver. If you select Yes to continue the load function, new CRC values for any objects that will change will appear in the Current CRC column and there will be an asterisk (*) in front of the device.
286
OW331_47
7.2 Using Point Information (PI) to identify SIS points Notice in the following Confirm window that there are asterisks in front of the I/O Channels that have changed after the Logic Solver was loaded.
7.2
Using Point Information (PI) to identify SIS points You can use the Point Information window to locate SIS points in a system and to determine if a point is a SIS point. The Point Information window provides the following information about a selected point (refer to the Ovation Operator Station User Guide for additional information about the Point Information function):
The point name (PN record field) displays at the top of the window. All points in the Ovation system are fully specified by three parameters:
Point name ¾ 24-character maximum for Windows systems.
Six-character maximum sub-network (unit) name.
OW331_47
287
7.2 Using Point Information (PI) to identify SIS points
Eight-character maximum network name. The fully qualified name is of the format “name. unit@network.” The (.) and @ are reserved characters for point names.
The description, point value, quality, and engineering units for analog points display below the point name.
The point attributes display by selecting the applicable tabs.
The point record field that corresponds to the parameter name is listed beside the parameter. A point record stores the information which defines the attributes of a point. Point records are used within each drop, and to communicate over the Ovation network to other drops.
The Ovation system has 11 record or point types. (Refer to the Ovation Record Types Reference Manual for additional information about point records.)
The point information displayed in the lower portion of the window displays using a folder format. The tabs are labeled and the information related to the tab label displays below when the tab is selected. When a valid point name is entered, information for the point displays for the first tab, the Point tab.
The SIS Indication (KC) field identifies if a point is a SIS point.
The action buttons Cancel and Apply are active only when a tab with modifiable data is selected.
Last Active Instance (LAI) - displays in the right bottom corner of the window. This identifies the Point Information window that is currently active.
Point status information displays in the left bottom corner of the window.
Note: Value and status fields update once every second. The remaining point attributes update once every three seconds. Point Information requests a one-shot every three seconds to make sure it has the latest static data.
7.2.1 To use Point Information to identify SIS points Prerequisites
Make sure the Ovation point exists and is in the database.
Procedure 1. Open the Ovation Applications folder at the Operator Station and double-click on the Point Information icon. OR If the Point Information application is already running, double click on the PI icon located on the system tray. OR Select Start -> Ovation -> Ovation Applications -> Point Information. The Point Information window appears. 2. If you know the name of the desired point, type in the name and press Enter. The Point Information window appears for that point. 3. If you do not know the name of the desired point, click the Search button in the Point Information window or select from the File pull-down menu. The Find Points window appears.
288
OW331_47
7.2 Using Point Information (PI) to identify SIS points 4. Select the appropriate network, unit, and drop. A scrolling list of all the points for that drop appears. To discontinue or change the search, click the Abort Search button. 5. Double click on the desired point name in the list or select the point and click the Apply button. The Point Information window appears for that point. 6. Select the Config tab.
Figure 73: Point Information window 7. Check the SIS Indication field at the bottom of the window. If the point is a SIS point, the value will be 1 or greater. If the point is not a SIS point, the value will be zero (0).
OW331_47
289
7.3 Viewing SIS Tuning windows for SIS algorithms
7.3
Viewing SIS Tuning windows for SIS algorithms SIS algorithms can be viewed and tuned through an SIS Tuning window in the Signal Diagram application. All of the SIS algorithms have SIS Tuning windows. If the SIS algorithm has tunable parameters, they are tuned through the SIS Tuning window -- not through the Property Summary window. If the SIS algorithm does not have tunable parameters, the tunable column in the SIS Tuning window appears blank. For certain SIS algorithms, the SIS Tuning window has an extra tab. The information in this tab is read-only, and contains the information that was entered in the advanced editing window in the Control Builder. The algorithms that have the extra tab are:
LSCALC (see page 291).
LSCEM (see page 292).
LSSEQ (see page 294).
LSSTD (see page 296).
Note: For more information on the SIS algorithms, refer to Ovation Algorithms Reference Manual.
7.3.1 To access the SIS Tuning window for SIS algorithms To access the SIS Tuning window for SIS algorithms, follow the steps below: 1. Access the Signal Diagram window. 2. Select a sheet from the Open Document window. 3. The sheet appears on the display canvas. Right-click on the desired SIS algorithm on the sheet. Select Advanced Tuning from the menu that appears. The SIS Tuning window applicable to that algorithm displays. See Ovation Algorithms Reference Manual for information on SIS algorithms.
290
OW331_47
7.3 Viewing SIS Tuning windows for SIS algorithms
7.3.2 SIS Tuning window for the LSCALC algorithm
Figure 74: LSCALC SIS Tuning window -- Properties Summary tab
Figure 75: LSCALC SIS Tuning window -- Program tab
OW331_47
291
7.3 Viewing SIS Tuning windows for SIS algorithms
7.3.3 SIS Tuning window for the LSCEM algorithm
Figure 76: LSCEM SIS Tuning window -- Properties Summary tab
292
OW331_47
7.3 Viewing SIS Tuning windows for SIS algorithms
Figure 77: LSCEM SIS Tuning window -- Cause and Effect Table tab
OW331_47
293
7.3 Viewing SIS Tuning windows for SIS algorithms
7.3.4 SIS Tuning window for the LSSEQ algorithm
Figure 78: LSSEQ SIS Tuning window -- Properties Summary tab
294
OW331_47
7.3 Viewing SIS Tuning windows for SIS algorithms
Figure 79: LSSEQ SIS Tuning window -- Sequence Table tab
OW331_47
295
7.3 Viewing SIS Tuning windows for SIS algorithms
7.3.5 SIS Tuning window for the LSSTD algorithm
Figure 80: LSSTD SIS Tuning window -- Properties Summary tab
296
OW331_47
7.3 Viewing SIS Tuning windows for SIS algorithms
Figure 81: LSSTD SIS Tuning window -- State Transition Table tab
OW331_47
297
7.4 Forcing an algorithm input value
7.4
Forcing an algorithm input value A SIS Force operation occurs when you manually change a value for an algorithm input parameter. This means the value is "forced." For example, you might want to see the behavior of an algorithm when it has a certain input value. However, the algorithm might not currently have the input value you need. You can use a Signal Diagram (see page 298) to temporarily force the input value of the algorithm in order to observe the behavior. You cannot force the output of an algorithm to a particular value; you can only force the input to a particular value. However, before you can force an input value for an SIS algorithm, you must turn on the Debug Mode. The Debug Mode is where you can perform functional testing of safety logic by forcing input values for algorithms (see page 298). After you have forced an input value, a blocking icon will appear at the end of the forced input pin of the algorithm in the Signal Diagram. This icon will also appear next to the current value in the Algorithm Summary window. This icon illustrates that the value for the input signal is currently forced and cannot be updated by the system. Note: Remember to remove the forced input value when you want the algorithm to execute normally.
7.4.1 To force an algorithm input value Prerequisites
Make sure the applicable control sheet has been successfully loaded into the Controller and the Logic Solver.
Procedure 1. Access the Signal Diagram window:
From the Operator Station Ovation Applications icons or from a Point Menu (see Ovation Operator Station User Guide for details). OR
From the Control Builder (see Ovation Control Builder User Guide for details). 2. Navigate to a sheet in the Open Document window. See Ovation Control Builder User Guide for more information. 3. Double-click on the sheet and the sheet appears on the display canvas of the Signal Diagram window. 4. Right-click on the desired algorithm on the sheet and select Advanced Tuning from the menu.
298
OW331_47
7.4 Forcing an algorithm input value The SIS Tuning window appears with the selected algorithm name at the top of the window. The following steps provide an example of how to use the SIS force function.
5. Select the Force button. The Force Value window for the selected algorithm appears.
The following table describes the fields and buttons in the Force Value window. FIELD
OW331_47
DESCRIPTION
Turn Debug ON
Use to enter the Debug Mode.
Turn Debug OFF
Use to leave the Debug Mode.
299
7.4 Forcing an algorithm input value
FIELD
DESCRIPTION
Force Inputs Pin Name
Pull-down list of all the algorithm pins whose values can be forced. Name of the pin whose input value you want to force to another value.
Forced Value
Displays the value to which the pin if forced, if applicable.
Forcing
Name of pin whose value is being forced.
Forced Value
Entry field into which you enter the value to which you want to force the pin.
Set Force button
Sets a new forced value for the pin.
Clear Force button
Clears or removes the forced value from the pin.
Set Value button
Use this button to change the value of an already forced value for a pin.
Apply button
Applies the changes you made.
6. If Debug is OFF, press the Turn Debug ON button and continue to Step 7. If Debug is ON, skip to Step 9. Note: When you turn on the Debug Mode, you set the Debug Mode for the entire Control Module and all of the SIS control sheets in that module. 7. A Confirm window appears asking you to confirm that you want to enter the Debug Mode. Select Confirm. (The SIS Write function checks to verify that the process is valid.)
8. The Enter Debug window appears informing you that you have successfully entered the Debug Mode. Select the OK button.
9. The Force Value window now displays showing that you are in Debug Mode. Select from the Pin Name list the desired pin whose value you want to force.
300
OW331_47
7.4 Forcing an algorithm input value 10. Enter the desired value in the Forced Value entry field and select Apply.
11. A Confirm window appears asking you to confirm that you want to force the value of the selected pin. Select Confirm. (The SIS Write function checks to verify that the process is valid.)
OW331_47
301
7.4 Forcing an algorithm input value 12. The Set Force window appears informing you that you have successfully forced the value of the pin. Select the OK button.
13. The Force Value window now displays showing the forced value in the Forced Value list.
Note: A blocking icon will appear on the end of the forced input pin of the algorithm in the Signal Diagram. This icon will also appear next to the current value in the Algorithm Summary window. This icon illustrates that the value for the input signal is currently forced and cannot be updated by the system. 14. After you have forced the pin value, you can do one of the following:
Set a new forced value for the pin. (See Set a new forced value.)
Clear the force (See Clear the force and leave Debug Mode.) See Ovation Safety Instrumented System (SIS) User Guide for information on setting and clearing forced values. Set a new forced value 1. If you decide to set a new forced value for a pin whose value is already forced, do the following in the Force Value window: a) Select the Pin Name b) Enter a new value in the Forced Value field. c) Select the Set Value button.
302
OW331_47
7.4 Forcing an algorithm input value d) Select the Apply button.
2. A Confirm window appears asking you to confirm that you want to force the value of the selected pin. Select Confirm. (The SIS Write function checks to verify that the process is valid.)
OW331_47
303
7.4 Forcing an algorithm input value 3. The Force new value window appears informing you that the value of the pin has been forced. Select the OK button.
4. The Force Value window now displays showing the new forced value in the Forced Value list. You can clear the force now or set a new forced value again.
Clear the force and leave Debug Mode 1. If you decide to clear the forced value for a pin, do the following in the Force Value window: a) Select the Pin Name. b) Select the Clear Force button.
304
OW331_47
7.4 Forcing an algorithm input value c) Select the Apply button.
2. A Confirm window appears asking you to confirm that you want to clear the forced value of the selected pin. Select Confirm. (The SIS Write function checks to verify that the process is valid.)
OW331_47
305
7.4 Forcing an algorithm input value 3. The Clear Force window appears informing you that the forced value of the pin has been cleared. Select the OK button.
4. Emerson recommends that you leave Debug Mode when you are done with your forcing tasks. Select the Turn Debug OFF button in the Force Value window.
5. A Confirm window appears asking you to confirm that you want to leave Debug Mode. Select Confirm. (The SIS Write function checks to verify that the process is valid.)
306
OW331_47
7.5 Restarting a Logic Solver 6. The Leave Debug window appears informing you that you have left Debug Mode. Select the OK button.
7.5
Restarting a Logic Solver The Ovation SIS system supports redundant Logic Solvers. A redundant Logic Solver consists of a pair of Logic Solvers mounted in adjacent carrier slots with a redundant terminal block. Each Logic Solver is powered separately. The Logic Solvers contain the same configuration and run the same logic. If you have a redundant Logic Solver configuration, you might need to do one of the following actions to a redundant Logic Solver:
Restart the active Logic Solver.
Restart the standby Logic Solver.
Switch the active Logic Solver to the standby mode, and the standby Logic Solver to the active mode.
Note: If you must restart a simplex Logic Solver online, such as for proof testing, you need to temporarily bypass or block final elements and provide manual supervision.
7.5.1 To restart (reboot) a Logic Solver 1. Access the Ovation Developer Studio. 2. Use the system tree to navigate to the Logic Solvers folder: System Networks Units Drops (appropriate Controller drop) I/O Devices SIS I/O Device Data Servers Logic Solvers
OW331_47
307
7.5 Restarting a Logic Solver 3. Right-click on the Logic Solver you want to restart and select Reboot. A Restart Wizard window appears.
4. Select the desired action:
Force Restart Active = Restarts the active Logic Solver.
Force Restart Standby = Restarts the standby Logic Solver.
Switchover = Switches the active Logic Solver to standby, and the standby becomes the active Logic Solver. 5. Select the Finish button. A confirmation dialog window appears. 6. On the confirmation dialog, click Confirm to restart the selected Logic Solver or to switch the active Logic Solver to standby, and the standby Logic Solver to active.
308
OW331_47
7.6 Requiring a reset before outputs can become energized
7.6
Requiring a reset before outputs can become energized The configuration of SIS module logic determines which conditions allow de-energized output channels of the Logic Solver to become energized. It is generally desirable to require an operator reset of the Logic Solver before the equipment under control is allowed to go from a shutdown or tripped state to the normal operating state. However, in some cases, the output channels should be allowed to change from de-energized to energized based on input channel values without operator intervention, for example, as soon as an interlock condition clears. Ovation SIS algorithms provide an easy way to configure SIS module logic to either require or not require an operator reset before applicable output channels can become energized. There are certain situations where a powered Logic Solver keeps output channels de-energized independent of SIS module logic. When the Logic Solver is going through power-up testing following a reset or restart, has detected a persistent fatal error, or is in an unconfigured state, output channels remain de-energized. Otherwise, SIS module logic determines the output channel state. The recommended technique for requiring an operator reset is to use the Cause Effect Matrix (LSCEM (see page 113)) algorithm. It has an RRSn (required reset) parameter or each extensible EFFn (output effect) output of the algorithm. Each EFFn output is connected to one or more output algorithms, which are bound to output channels. When RRSn is True (the default value), the EFFn output cannot transition from 0 to 1 unless STAn (current state) is “Ready to Reset” and RSTn (reset) has been changed to True, typically by an SIS Write from an Ovation Operator station. When RRSn is False, EFFn can transition from 0 to 1 when associated CSn (input cause) have become inactive and other permissives are satisfied, without a reset. The “require reset” option is also available in the two output algorithms, but it should be used only if there is no LSCEM algorithm in upstream SIS module logic.
7.7
Configuring the Logic Solver's response to detected faults It is important to consider the status of the input and output channels of the Logic Solver, as BAD status may indicate a problem that must be addressed. The following topics are described below:
Detecting faults on input channels (see page 310)
Detecting faults on output channels (see page 314)
OW331_47
309
7.7 Configuring the Logic Solver's response to detected faults
7.7.1 Detecting faults on input channels Faults detected by the Logic Solver on input channels can originate in field devices, field wiring, or in the Logic Solver input circuitry. The Logic Solver responds to faults detected on input channels by integrating BAD status with the channel value and annunciating the fault. The Logic Solver does not automatically de-energize output channels when faults are detected on input channels. SIS module logic must be configured to take action based on the requirements of the application. For example, you may want to prevent a trip from occurring in the presence of a fault on an input channel, or cause a trip immediately when a fault is detected, or initially prevent a trip yet cause a trip some time later if the fault persists. SIS algorithms contain parameters to facilitate the configuration of these options. You have some control over how BAD status on input channels can get into SIS modules. Certain input channel parameters and algorithm parameters impact the detection of faults on input channels and whether BAD status becomes available to SIS module logic. Handling BAD status on analog input channels An analog input channel (see page 273) always has BAD status when the measured current is outside the sensor failure limits, 0.78 mA (-20.12%) and 22.66 mA (116.6%). The limits can be exceeded due to faults in the transmitter, field wiring, or the Logic Solver. You can also cause the channel to have BAD status when the current reaches a value inside the sensor failure limits. Changing the "Enable NAMUR alarming" channel parameter to True enables NAMUR limit detection, which results in BAD status being applied when the current is greater than 21.0 mA (106.25%) or less than 3.6 mA (-2.5%) for four consecutive seconds. When the channel value exceeds the channel’s configured "Analog over range pct" or "Analog under range pct," high-limited or low-limited status is applied to the channel. The SOP8 parameter in the Analog Input (LSAI) algorithm has a “BAD if Limited” option. When the LSAI algorithm’s referenced input channel has high or low limited status, the algorithm applies BAD status to its PV and OUT parameters if the option is enabled. The HART Analog Input channel’s (see page 275) HART related error parameters allow you to select which HART diagnostic conditions detected in the HART transmitter or by the Logic Solver cause BAD status to be integrated with the analog value on the channel (the "BAD if Limited" channel parameter). The default value of these parameters is to ignore all HART diagnostic errors, meaning the presence of an error condition does not cause BAD status on the channel. If you deselect “Ignore Field Device Malfunction,” for example, the channel has BAD status if the transmitter reports a device malfunction, allowing this HART diagnostic to be integrated with your SIS module logic.
310
OW331_47
7.7 Configuring the Logic Solver's response to detected faults Handling BAD status on digital input channels Faults detected on digital input channels (see page 279) by the Logic Solver result in BAD status on the channel. The Logic Solver detects open and short circuits in field wiring if line fault detection has been enabled on the channel using the "Detect open and short circuit" parameter. When line fault detection is enabled, you must use a NAMUR sensor or install end of line resistors in series and parallel. An open or short detected through line fault detection results in BAD status on the channel. Line fault detection is required when the field switch is normally open, that is, when the channel is On to indicate a demand. Line fault detection is recommended when the field switch is normally closed, that is, when the channel is Off to indicate a demand. If an open circuit occurs in the field wiring, it is a safe failure whether or not line fault detection has been enabled. But a short in the field can be a dangerous failure and be undetected, unless line fault is enabled, in which case the channel has BAD status.
OW331_47
311
7.7 Configuring the Logic Solver's response to detected faults Using BAD Status in SIS Modules Two algorithms are available in SIS modules to manipulate output channels: the Digital Output (LSDO (see page 150)) algorithm and the Digital Valve Controller (LSDVC (see page 157)) algorithm. Each has a CASND input parameter whose value is the commanded state for the output channel, which is connected from upstream logic in the SIS module. When the status of CASND changes to BAD, the algorithm starts a timer whose value is stored in the FTMR (fault detection timer) parameter. If and when the timer reaches the configured FTIM (fault detection delay) value, the algorithm enters the fault state if theFOP2 (Enable detection based on CASND status) option is enabled. The algorithm drives the output channel Off when it is in the fault state. SIS algorithms have a predetermined way of propagating the status of input parameters to output parameters. Faults detected on input channels cause BAD status to reach output algorithms in SIS modules depending on the configuration of other algorithms in the SIS module. The configured value of FTIM in output algorithms determines how long status can be BAD before the output algorithm initiates a trip. The default value is 300 seconds, which gives enough time for operators to bypass a BAD input and take corrective action before a trip is initiated. Use an appropriate value for FTIM in each output algorithm. Some SIFs (see page 6) can tolerate a high number corresponding to your allowed repair time, while other SIFs may require a low number of just a few seconds. The following figure illustrates the use of common SIS algorithms to create shutdown logic in an SIS module. The status on the output parameter of the input algorithms, LSAI and LSDI, is the status of the referenced input channel. The Analog Voter (LSAVTR (see page 82)) and Digital Voter (LSDVTR (see page 169)) algorithms propagate BAD status on input parameters selectively. For example, if a single input of a 1oo2 (1 out of 2) or 2oo3 (2 out of 3) voter algorithm has BAD status, OUT continues to have GOOD status because there are enough good inputs for a real process demand to cause a trip. However, if a single input of a 1oo1 or 2oo2 voter algorithm has BAD status, its OUT has BAD status. If a CSn (input Cause n) input of a Cause and Effect Matrix (LSCEM (see page 113)) algorithm has BAD status, all EFFn (output Effect n) outputs associated with that input have BAD status. LSAVTR, LSDVTR, and LSCEM algorithms have a configurable SOPT parameter, which impacts how the algorithms determine the value of their output parameter(s) based on the status of their inputs. These algorithms determine the status of their output parameter(s) by fixed status propagation logic unique to the algorithm and independent of the SOPT parameter. This assures that if BAD status is capable of preventing a process demand from causing a trip, BAD status propagates to the output algorithm(s). Refer to the LSAVTR, LSDVTR, and LSCEM algorithm documentation for more detail on the impact of the SOPT parameter in these algorithms.
312
OW331_47
7.7 Configuring the Logic Solver's response to detected faults
OW331_47
313
7.7 Configuring the Logic Solver's response to detected faults
7.7.2 Detecting faults on output channels Faults detected by the Logic Solver on output channels (see page 280) can originate in field devices, field wiring, or the Logic Solver output circuitry. As with input channels, the Logic Solver responds to faults on output channels by integrating BAD status with the channel value and annunciating the fault. A fault on an output channel does not prevent the output from being de-energized if there is a demand to trip on that channel. Suppose a Digital Output channel is stuck On due to a fault in the output circuitry. When SIS module logic detects a process demand to trip and the LSDO algorithm drives the channel Off, power remains On as a result of the fault. However, the Logic Solver reads back the output as still being On and initiates a reset, which opens the master power switch and de-energizes all output channels on the Logic Solver. When the "Detect open and short circuit" parameter on Digital Output channels is True (the default value), the Logic Solver detects and annunciates stuck On conditions by means of periodic pulse testing. In this way a failed unit can be replaced before a demand occurs, thereby avoiding a trip on all output channels. The "Detect open and short circuit" parameter should remain configured as True unless the final element cannot tolerate the 1 millisecond Off pulse during each 50 millisecond period. If the Logic Solver detects an open or short in field wiring or the output circuitry, it integrates a special status with the channel value called BAD SensorFailure LowLimited. Output algorithms detect this status on the referenced output channel and optionally drive the output channel Off. If the “Enable detection based on output channel status” option is set in the algorithm’s FOP3 parameter, the algorithm enters the fault state and drives the channel Off immediately upon detection. The FTIM value is not used in this case. An open or short in field wiring implies the final element is in the de-energized state. Therefore the default value for the FOP3 parameter drives the channel Off when an open or short is detected. In order to keep the channel Off after it is driven Off, an operator reset must be required somewhere. The reset can be on the final element itself, in the output algorithm, or in the upstream LSCEM algorithm. The following figure shows an example of using an LSCEM algorithm for latching an output Off.
314
OW331_47
7.8 Choosing the Logic Solver scan rate The CS3 input of the LSCEM (see page 113) algorithm has a value of 1 when neither output algorithm is in the fault state. FSTAT is normally an internal parameter, but in this example, it is exposed as an output parameter on the LSDO and LSDVC algorithms and connected to an LSNOR algorithm. If either output algorithm detects an open or short on its referenced channel, a trip occurs on EFF1 of the LSCEM algorithm and both output algorithms drive their outputs Off (because CASND becomes 0). The algorithm that detected the open or short had already driven its output Off. The outputs remain Off until an operator reset is done on EFF1 by changing RST1 of the LSCEM algorithm to True. The fault state condition clears when a Digital Output channel is driven Off because the diagnostic no longer detects the condition. The same is true for a HART Two-state Output channel when OFCUR is “0 milliamps.” This technique applies to the case where a coordinated trip of multiple final elements is required when any of the final elements involved in an interlock becomes de-energized due to an open or short. If you want to drive Off only the output with the open or short, use a separate LSCEM Effect output for each output algorithm and connect FSTAT into a separate Cause input. In some applications it may not be desirable to drive an output Off when an open or short is detected. For example, you may want the final element to become energized without operator intervention whenever an intermittent short clears. In this case, disable the FOP3 parameter in the output algorithm.
7.8
Choosing the Logic Solver scan rate The default scan rate (see page 267) for SIS module execution in the Logic Solver is 50 milliseconds. You can change the scan rate to 100, 150, or 200 milliseconds from the SLS properties dialog in Ovation Explorer. Increasing the Logic Solver scan rate value impacts the execution rate of SIS modules. But diagnostic cycle times in the Logic Solver remain constant, with the exception of the main processor comparison diagnostic, which is a function of SIS module scan rate. The recommended scan rate to use whenever possible is 50 milliseconds. This scan rate minimizes the input to output response time. The only reason to change the scan rate beyond the default 50 milliseconds is if the Logic Solver is not able to execute the SIS module or modules at the configured scan rate.
7.9
Loading to a running process If you anticipate a need to make online changes to SIS module logic, that is, to load Logic Solvers that are protecting a running process, you should ensure the load does not disrupt the process. Locking a Logic Solver prevents it from being loaded. Locking also prevents a user-initiated Logic Solver switchover. To be able to lock or unlock a Logic Solver you must have the SIS Can Load privilege. A Logic Solver must be unlocked before you can load to it (see page 285). If you attempt to load a locked Logic Solver, you are given the opportunity to unlock the Logic Solver and continue.
OW331_47
315
7.10 Restarting a Logic Solver after a power failure
7.10 Restarting a Logic Solver after a power failure A restart occurs after power is restored to a Logic Solver that had a running configuration prior to losing power for less than 10 days. During a restart the Logic Solver reapplies the last loaded configuration and restores parameters that had been saved to non-volatile memory. At the time power is lost, outputs of the Logic Solver are de-energized, which should result in the same output state as after the original load. After a restart the goal is to retain the same process state that occurred as a result of the power failure, yet to restore the parameter values that were saved to non-volatile memory, which are more current than the last loaded values.
7.11 Proof testing the Logic Solver Logic Solvers must be proof tested periodically to ensure there are no dangerous faults present that are not being detected by continuous runtime diagnostics. A manual proof test for a Logic Solver is initiated from the Developer Studio and causes the Logic Solver to go through reset and power-up testing. Proof testing of Logic Solvers can also be done automatically. Immediately following successful power-up testing, there are no known dangerous faults present. Choose the proof test interval for a Logic Solver based on the associated SIF requiring the shortest proof test period to achieve the required probability of dangerous failure for its Logic Solver subsystem. The Logic Solver proof test timer automatically counts the number of days since the last reset occurred. The Logic Solver configuration dialog in Developer Studio has a Proof Testing tab for entering the required proof testing interval and a reminder time value. See Logic Solver configuration for information about the fields in this tab (see page 268).
Figure 82: SIS Logic Solvers configuration dialog (Proof Testing tab)
316
OW331_47
7.11 Proof testing the Logic Solver The Logic Solver provides an alert when the number of days since the last reset exceeds the configured time. A reminder alert occurs a configured number of days before the “exceeds” alert to assist maintenance personnel in the planning of manual tests. The proof test timer for a redundant Logic Solver indicates the number of days since the last reset of the Active unit, which always occurs earlier than the last reset of the Standby.
7.11.1 Automatic proof testing Automatic proof testing is available for redundant Logic Solvers only. The Proof Testing tab of the Logic Solver configuration dialog has an “Enable automatic proof test to run at reminder time” check box (this check box is grayed-out for simplex Logic Solvers). When checked, the Logic Solver performs the proof test when the number of days since the last reset reaches the configured time. The test begins five minutes after the Logic Solver sets the reminder alert. In this case the reminder alert informs the operator that a test will occur soon so that the "Partner Not Available" alerts can be ignored after the test begins. At the time of automatic proof test:
The Active Logic Solver starts the test by initiating a switchover to the Standby Logic Solver. If the Standby Logic Solver is not available, the Active Logic Solver tries again in five minutes.
After switchover, the Standby Logic Solver becomes Active and the new Standby Logic Solver goes through reset and begins power-up testing. There is no adverse impact to the running process.
The new Active Logic Solver still has a proof test due, so it waits for its partner to become available then initiates a switchover. When the partner has become the Active Logic Solver, the new Standby Logic Solver goes through reset and power-up testing.
7.11.2 Manual proof testing The following procedure should be used for manual proof testing of the Logic Solver. Simplex Logic Solver 1. Initiating a manual reset on a simplex Logic Solver results in all outputs being de-energized. If you must proof test a simplex Logic Solver online, you need to temporarily bypass or block final elements and provide manual supervision. 2. The Logic Solver must be Unlocked to initiate a manual reset. Select the Logic Solver under SIS Network in the Developer Studio. Right-click on the Logic Solver and select Unlock. Click Confirm on the SIS Write confirmation dialog. 3. Right-click on the Logic Solver and select Reboot. The Restart Wizard appears. Select Force Restart Active from the options in the Restart Wizard window (see page 307). Clicking Confirm on the confirmation dialog results in all outputs being de-energized. 4. The Logic Solver goes through power-up testing and returns to the configured state. The proof test timer resets to 0. Redundant Logic Solver The procedure for a redundant Logic Solver allows the proof test to be done online without adversely affecting the running process. 1. The Logic Solver must be Unlocked to initiate a manual reset. Select the Logic Solver under SIS Network in the Developer Studio. Right-click on the Logic Solver and select Unlock. Click Confirm on the SIS Write confirmation dialog.
OW331_47
317
7.12 Customizing your Ovation Control Builder frame 2. Right-click on the Logic Solver and select Reboot. The Restart Wizard appears. Select Force Restart Standby from the options in the Restart Wizard window (see page 307). Clicking Confirm on the confirmation dialog results in all outputs being de-energized. 3. Wait several minutes for the Standby Logic Solver to complete power-up tests and become configured by the Active Logic Solver. The Partner Not Available maintenance alert goes inactive when the Standby Logic Solver is fully configured. 4. Right-click on the Logic Solver and select “Switchover.” Click Confirm on the confirmation dialog. 5. The previously reset Standby Logic Solver becomes the new Active Logic Solver and the new Standby Logic Solver goes through power-up tests and is configured by the new Active Logic Solver. The proof test timer is 0.
7.12 Customizing your Ovation Control Builder frame Every control function, control library, and control macro begins with a template or blueprint that displays on the drawing canvas. This template, called the frame, contains a standard format that can be used to enforce a consistent look for all the items in a project. The format also contains information that identifies the item (sheet, library, macro) to the system and to the user. By placing this information in the frame, you do not have to enter it every time you create a new item. The Control Builder provides an approved frame or template file, called the frame.svg file, which is shipped with the standard release of the Ovation system. All of the elements of the frame are defined in the frame.svg file. You many want to customize a frame in order to more easily identify SIS control sheets. The SIS Data Server, Logic Solver, and Control Module are available as Document Values under the Draw menu. Use the following procedure to create a SIS custom frame (Frame.svg) in the unit's ControlFunctions directory. 1. Copy the default frame (C:\Ovation\CtrlBldr\Frame.svg) into the ControlFunctions Directory. 2. Add a [Document Value] for cb-sis-server in the custom frame (Frame.svg). You may wish to add items for the Logic Solver and/or the Control Module at this time. 3. Recompile all the control sheets. 4. Load the Logic Solvers and control sheets. This document value will remain hidden on NON-SIS Control Functions. Refer to the Ovation Control Builder User Guide for more information about creating frames and sheets, and adding document values.
318
OW331_47
7.13 Upgrading SIS firmware
7.13 Upgrading SIS firmware Future releases of Ovation software will potentially include updated firmware for the SIS components. It may not be necessary to upgrade the firmware in SIS hardware components when the remainder of the Ovation system is upgraded to a new release. But if a new SIS firmware revision has desired features or corrects a specific issue, you can upgrade to the new revision by installing files from an Ovation workstation to flash memory in the SIS component. The following topics provide upgrade procedures:
To initially load or upgrade an SIS Data Server (see page 319).
To upgrade an SIS Logic Solver (see page 320).
7.13.1 To initially load or upgrade an SIS Data Server When you first receive an SIS Data Server, you must perform an initial load of the firmware. Subsequent loads of the SIS Data Server are considered to be upgrades. Emerson provides firmware for the SIS components in your Ovation system. Firmware for the upgrade to your SIS Data Server consists of four Hex files and one UDF file. Use the following procedure to initially load or upgrade your SIS Data Server. 1. Retrieve the new SIS Data Server firmware from the path: Ovation\SIS\firmware\OvSisSDSFirmware.zip 2. Unzip the files and store the four Hex files and one UDF file in an area where they can be easily accessed; (for example, C:\temp\sis) 3. Open a Command Prompt window and go to Ovation\OvationBase. 4. Enter the following: OvSisCtlUpgConsole -n where: = name or IP address of SIS Data Server to be loaded or upgraded = absolute path to Hex and UDF files (for example, OvSisCtlUpgConsole 192.168.1.1 C:\temp\sis\InstallCtlR_MD.udf)
-n
5. Press the Enter key. 6. The upgrade system files will load. The following text is an example of what displays in the Command Prompt window when the upgrade is finished: Percent complete 100 Upgrade system load complete. Target will now restart in upgrade mode. Attempting to re-establish upgrade session. Upgrade session re-established. Upgrading CTLPPCSTART version (MD Controller Start Vector (Debug Component does not need to be loaded) Component CTLPPCSTART upgrade COMPLETE. Upgrading CTLPPCRECOVER version
OW331_47
(MD Controller Recovery (Debug))
319
7.13 Upgrading SIS firmware Component does not need to be loaded Component CTLPPCRECOVER upgrade COMPLETE. Upgrading CTLPPCAPP version 10.3.0 (MD Controller Application (Debug)) 7. The component load will begin. When finished, the following will display Component load complete. Component CTLPPCAPP upgrade COMPLETE. ---------------------------------------------------------------Upgrade Completion Summary: 8. The SIS Data Server is now upgraded.
7.13.2 To upgrade an SIS Logic Solver Emerson provides firmware for the SIS components in your Ovation system. Use the following procedure to upgrade your SIS Logic Solver (SLS): Note: The typical upgrade time for a single Logic Solver is about eight minutes. If during the upgrade process there is a network failure, or the workstation which is hosting the upgrade application fails, you can restart the upgrade. To do so, repeat the procedure starting at Step 4. 1. Retrieve the new Logic Solver firmware package. It consists of four files:
1340.idf
IO_Compatibility.csv
SLSApp.hex
SLSBoot.hex 2. Store the four files in an area where they can be easily accessed; (for example, C:\temp\sis) 3. Clear the target SLS in the Developer Studio (see page 263). 4. Clear the Ovation Controller to which the target Logic Solver is assigned. 5. Run the upgrade application: Ovation.Sis.Sls.Upgrade.Console.exe [SDS ip address/hostname] [logic solver number] [logic solver redundant] [full path to idf file] where: [SDS ip address/hostname] = IP address or hostname of the SIS Data Server which is supervising the Logic Solver that you are upgrading. [logic solver number] = Number (1-32) of the physical Logic Solver that you are upgrading (this is not the carrier slot number). [logic solver redundant] = Flag indicating whether the target Logic Solver is in a redundant configuration. Accepted values of this attribute are true or false. [full path to idf file] = Fully qualified file name of the .idf file which is part of the firmware package, (for example, d:\sls-firmware\v.10.3\1340.idf 6. Confirm that you want to proceed with the upgrade by entering y when prompted.
320
OW331_47
7.14 Using Fault Codes for SIS (66, 3, 8) 7. Wait for the application to terminate. The application will periodically output messages regarding the progress of the upgrade process. In the final step, it will report the status of the entire upgrade. Warnings! Do not shutdown your computer or interrupt the upgrade process until it is completed. Failure to comply may result in corrupting the Logic Solver's flash memory and rendering the Logic Solver unusable. You MUST complete a full function test of the Logic Solver after a firmware upgrade.
7.14 Using Fault Codes for SIS (66, 3, 8) The Ovation system generates fault codes and messages that you can use to diagnose workstation and system problems. This section details the fault codes and messages that are generated by the Safety Instrumented System. To research other fault codes generated by your system, access the Ovation fault information tool at: https://www.ovationusers.com/FIT/index.asp You can find fault information on the System Status diagram and the Drop Details diagram. You can find further information in your 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 Solaris GMD or in the Windows Error Log Viewer).
The SIS shadow algorithms have the following values:
Fault Code = 66 which indicates a Controller fault.
Fault ID = 0x0003 which indicates an algorithm fault.
Fault Parameter 1 =0x0008 which indicates a problem with an SIS shadow algorithm as it appears in the Ovation Controller. F AULT P AR AM ETER 2
DESCRIPTION
0x0001
Logic Solver function number (Y1 field) is invalid. Parameter 3 = Control module ID Parameter 4 = Control sheet number Parameter 5 = Algorithm execution order number for the control sheet
OW331_47
321
7.15 SIS Diagnostics
F AULT P AR AM ETER 2
DESCRIPTION
0x0002
Value in an algorithm field (TT field) is invalid. Parameter 3 = Control module ID Parameter 4 = Control sheet number Parameter 5 = Algorithm execution order number for the control sheet
0x0003
Auxiliary record for the algorithm cannot be found. Parameter 3 = Control module ID Parameter 4 = Control sheet number Parameter 5 = Algorithm execution order number for the control sheet
0x0004
XDB lock cannot be found and the algorithm did not update parameter and output values in that loop. Parameter 3 = Control module ID Parameter 4 = Control sheet number Parameter 5 = Algorithm execution order number for the control sheet
0x0005
There is a module revision mismatch between algorithm point configuration and Logic Solver module configuration. Parameter 3 = Control module ID Parameter 4 = Control sheet number Parameter 5 = Algorithm execution order number for the control sheet
7.15 SIS Diagnostics You can perform diagnostics on your SIS system by referring to the bit values of the Node (RN) record of a point. 1. Access the Ovation Operator Station. 2. Access Point Information from your Ovation Applications folder at the Operator Station to view the node record (refer to the Ovation Operator Station User Guide for more information about the Point Information function). 3. Navigate to the Value/Status tab in the node record (the value used for the node record is the A2 field). 4. Review the collected bit information about the module or node. SIS I/O driver status (Node Record, A2 field definitions)
322
BIT
DESCRIPTION
SET
RESET
DETAILS
0
Configured
OK
NCONF
I/O Driver is configured. This bit is set by the I/O driver during the first pass.
1
Communication error
ERROR
Ok
There is a communication error. The I/O driver cannot send messages to the SIS Data Servers.
OW331_47
7.15 SIS Diagnostics
BIT
DESCRIPTION
SET
RESET
DETAILS
2
Configuration error
ERROR
Ok
There is an error in a configuration file or the configuration is inconsistent.
3
Alarm handler error
ERROR
Ok
The alarm handler has indicated that one or more alarm files are corrupted.
4 through 15
SIS Data Server status (Node Record, A2 field definitions) BIT
DESCRIPTION
SET
RESET
DETAILS
0
Configured
OK
NCONF
SIS Data Server is configured.
1
Primary in control
PRIM
BCKP
The primary SIS Data Server is in control.
2
Local bus communication error
ERROR
OK
There is an error in the SIS Data Server communication over the backplane.
3
SIS LAN communication timeout
ERROR
OK
There is a timeout in the communication between a SIS Data Server and an Ovation Controller.
4 through 15
SIS Logic Solver status (Node Record, A2 field definitions) BIT
DESCRIPTION
SET
RESET
DETAILS
0
Configured
OK
NCONF
The Logic Solver is configured.
1
Commissioned
OK
DECOMD
The Logic Solver has been recognized by Ovation.
2
Calibration
ACTIVE
NACT
The logic Solver has been calibrated.
3
Configuring state
ACTIVE
NACT
The Logic Solver is configured.
4
Communication error
ERROR
OK
There is an error in the communication with the Logic Solver.
5
IO channel error
ERROR
OK
There is an error in the Logic Solver's I/O channels.
6
Primary in control
PRIM
BCKP
The primary Logic Solver is in control.
7
Locked
LOCKED
UNLCKD
The Logic Solver is locked and cannot be loaded.
OW331_47
323
7.16 SIS Logic Solver events
BIT
DESCRIPTION
SET
RESET
DETAILS
8
Scan rate overloaded
OVRLD
NOVRLD
The configured scan rate for the Logic Solver is exceeded by the estimated execution time.
9 through 15
SIS Logic Solver module status (Node Record, A2 field definitions) BIT
DESCRIPTION
SET
RESET
DETAILS
0
Module not registered
NREG
OK
The module is not registered
1
Debug mode
DEBUG
NORM
The Debug Mode is where you can perform functional testing of safety logic by forcing input values for algorithms.
2 through 15
7.16 SIS Logic Solver events There are two types of events generated by the SIS Logic Solver. The following tables describe these events.
Module Events.
Diagnostic Events.
Module events EVENT
324
INDEX
STRING
TM_ME_DVC_CNFRM_SUCCESS
1
Successful confirmation following a command to trip
TM_ME_DVC_CNFRM_FAILURE
2
Failed to confirm following a command to trip
TM_ME_DVC_CNFRM_OFF_WHILE_ON
3
Confirmed Off while commanded On
TM_ME_DVC_PST_STARTED
4
Partial stroke test started
TM_ME_DVC_PST_DENIED
5
Partial stroke test denied
TM_ME_DVC_PST_FAILED
6
Partial stroke test failed
TM_ME_DVC_PST_SUCCESS
7
Successful partial stroke test
TM_ME_DVC_PST_PAST_DUE
8
Partial stroke test past due
TM_ME_DO_CNFRM_SUCCESS
11
Successful confirmation following a command to trip
TM_ME_DO_CNFRM_FAILURE
12
Failed to confirm following a command to trip
TM_ME_DO_CNFRM_OFF_WHILE_ON
13
Confirmed Off while commanded On
OW331_47
7.16 SIS Logic Solver events
EVENT
INDEX
STRING
TM_ME_AV_BYPASS_REMOVED
21
Bypass removed on
TM_ME_AV_BYPASS_PERMIT
22
Maintenance bypass permitted
TM_ME_AV_BYPASS_PERMIT_REMOVED
23
Maintenance bypass permit removed
TM_ME_AV_BYPASS_SET
24
Maintenance bypass on
TM_ME_AV_BYPASS_REMOVED_TIMEOU T
25
Maintenance bypass removed by block due to timeout
TM_ME_AV_VOTE_NOT_TRIP
26
voting not to trip
TM_ME_AV_VOTE_TRIP
27
voting to trip
TM_ME_AV_BYPASS_VOTE_TRIP
28
A bypassed input is voting to trip
TM_ME_AV_BYPASS_VOTE_NOT_TRIP
29
No bypassed input is voting to trip
TM_ME_AV_BYPASS_VOTE_PRETRIP
30
A bypassed input is voting to pretrip
TM_ME_AV_BYPASS_VOTE_NOT_PRETRI P
31
No bypassed input is voting to pretrip
TM_ME_DV_BYPASS_REMOVED
41
Bypass removed on
TM_ME_DV_BYPASS_PERMIT
42
Maintenance bypass permitted
TM_ME_DV_BYPASS_PERMIT_REMOVED
43
Maintenance bypass permit removed
TM_ME_DV_BYPASS_SET
44
Maintenance bypass on
TM_ME_DV_BYPASS_REMOVED_TIMEOU T
45
Maintenance bypass removed by block due to timeout
TM_ME_DV_VOTE_NOT_TRIP
46
voting not to trip
TM_ME_DV_VOTE_TRIP
47
voting to trip
TM_ME_DV_BYPASS_VOTE_TRIP
48
A bypassed input is voting to trip
TM_ME_DV_BYPASS_VOTE_NOT_TRIP
49
No bypassed input is voting to trip
TM_ME_CEM_EFFECT_TRIPPED
61
Trip, first out Cause
TM_ME_CEM_EFFECT_NORMAL
62
FIRST_OUT cleared
TM_ME_MISC_EVENTS_LOST
71
SLS Control subsystem lost SIF Module Events
Diagnostic events EVENT
INDEX
STRING
TM_DE_SWITCHOVER
1
REDIO: Switchover Occurred; card switch x
TM_DE_POWER_FAIL
2
Power Failure Occurred for x seconds
TM_DE_PAST_ERROR
3
An error condition was present after the previous powerup
TM_DE_LOST_EVENTS
4
Logic Solver Card Lost Event(s)
TM_DE_POWER_UP_EVENT
5
Logic solver proof test and power up successful
OW331_47
325
Index A
G
Adding and configuring SIS components in the Developer Studio • 237 Algorithm functional symbols • 71 Algorithm types • 70 Analog Input and HART Analog Input channel specifications and wiring • 33 Automatic proof testing • 317 Auxiliary Relay Diode module • 64 Auxiliary Relay DTA-Inverting module • 59 Auxiliary Relay ETA-Direct module • 63
GSECPARAMREF • 233
C Carrier extender cable part numbers • 41 Carrier extender cables • 41 Choosing the Logic Solver scan rate • 315 Configuring a Digital Input Channel • 279 Configuring a Digital Output Channel • 280 Configuring a HART Analog Input Channel • 275 Configuring a HART Two-state Output Channel • 277 Configuring an Analog Input Channel • 273 Configuring the Logic Solver Config tab • 266 Configuring the Logic Solver General tab • 267 Configuring the Logic Solver Proof Testing tab • 268 Configuring the Logic Solver's response to detected faults • 309 Connecting SIS sheets • 235 Copyright Notice • 2 Customizing your Ovation Control Builder frame • 318
D Detecting faults on input channels • 310 Detecting faults on output channels • 314 Digital Input channel specifications and wiring • 35 Digital Output channel specifications and wiring • 37
F Fiber-optic cable\ring • 41 Forcing an algorithm input value • 298 Functions of Ovation SIS • 2
OW331_47
H Handling BAD status on analog input channels • 310 Handling BAD status on digital input channels • 311 Hardware components of Ovation SIS • 11 Hardware for Ovation SIS • 11 HART two-state output channel specifications and wiring • 34
I Initial installation SIS upgrade • 244 Installation tools • 10 Introduction to Ovation Safety Instrumented System (SIS) • 1
L Limitations for SIS • 7 Loading Logic Solvers • 285 Loading to a running process • 315 Logic Solver redundancy • 31 Logic Solver specifications • 29 Logical network design example • 9 LSAI • 75 LSALM • 78 LSAND • 80 LSAVTR • 82 LSBDE • 100 LSBFI • 102 LSBFO • 105 LSCALC • 107 LSCEM • 113 LSCMP • 145 LSDI • 147 LSDO • 150 LSDVC • 157 LSDVTR • 169 LSLIM • 185 LSMID • 188 LSNAND • 191 LSNDE • 193 LSNOR • 195 LSNOT • 197 LSOFFD • 198 LSOND • 200 LSOR • 202
327
Index LSPDE • 204 LSRET • 206 LSRS • 208 LSSEQ • 210 LSSR • 215 LSSTD • 217 LSTP • 226 LSXNOR • 228 LSXOR • 229
M Manual proof testing • 317
N NONSECPARAM • 234 Nonsecured algorithm parameters • 236
O Ovation SIS accessories • 49 Ovation SIS Logic Solver algorithm table • 72 Overview of adding and configuring SIS components • 237
P Physical network design example • 8 Planning your hardware installation • 9 Planning your Safety Instrumented System • 5 Power Supply • 44 Power supply part number • 45 Power supply specifications • 45 Proof testing the Logic Solver • 316
R Removing Ovation SIS points from SIS control sheets • 259 Requiring a reset before outputs can become energized • 309 Restarting a Logic Solver • 307 Restarting a Logic Solver after a power failure • 316
S Safety Instrumented Functions (SIFs) • 6 Safety Instrumented System terminology • 2 Safety Integrity Levels (SILs) • 6 SECPARAM • 231 SECPARAMREF • 232 Secured algorithm parameters • 236 SIS Algorithms • 69 SIS Carrier part numbers • 14 SIS carriers • 14 SIS connector algorithm table • 230 SIS Current Limiter module • 56 SIS Data Server • 24
328
SIS Data Server LEDs • 27 SIS Data Server part number • 24 SIS Diagnostics • 322 SIS environmental specifications • 7 SIS I/O channels • 33 SIS issues to consider • 5 SIS LAN switches and routers • 49 SIS Logic Solver events • 324 SIS Logic Solver LEDs • 32 SIS Logic Solver part number • 29 SIS Logic Solvers • 28 SIS Net Distance Extender • 39 SIS Net Repeater • 38 SIS Net Repeater LEDs • 40 SIS Net Repeater part number • 38 SIS network design examples • 8 SIS Power Supply LEDs • 48 SIS Relay module • 50 SIS terminal block part numbers • 23 SIS Tuning window for the LSCALC algorithm • 291 SIS Tuning window for the LSCEM algorithm • 292 SIS Tuning window for the LSSEQ algorithm • 294 SIS Tuning window for the LSSTD algorithm • 296 SLS terminal blocks • 23 Software components of Ovation SIS • 67 Software for Ovation SIS • 67
T To access the SIS Tuning window for SIS algorithms • 290 To add an SIS control sheet to the SIS Ovation system • 270 To add an SIS Data Server to the Ovation System • 241 To add an SIS I/O device number • 250 To add an SIS I/O device to the Ovation System • 250 To add an SIS network switch to the Ovation System • 244 To add an SIS Network to the Ovation system • 238 To add and configure SIS Logic Solvers in the Ovation System • 263 To assign an SIS I/O Data Server to an SIS I/O Device • 255 To associate a Node point with an SIS I/O device • 253 To configure an SIS I/O channel • 271 To configure SIS control modules • 280 To configure SIS digital points for alarming with timestamps • 282 To configure SIS LAN network switches • 260
OW331_47
Index To create SIS network switch configuration files • 246 To force an algorithm input value • 298 To initialize SIS network switches • 248 To initially load or upgrade an SIS Data Server • 319 To install a simplex SIS Data Server • 24 To install carrier extender cables • 42 To install Logic Solvers • 30 To install power supplies • 45 To install SIS Net Repeaters for horizontal mounting • 39 To install terminal blocks • 23 To install the 1-wide carrier (dual-left/right extender cables) • 17 To install the 2-wide power/SIS Data Server carriers • 18 To install the 4-wide Vertical (Power/SIS Data Server) carrier • 20 To install the 8-wide I/O interface carrier (can hold up to four simplex Logic Solvers) • 20 To install the 8-wide Vertical (left/right side) carrier (can hold up to four simplex Logic Solvers) • 21 To load an SIS Logic Solver • 285 To power up a duplex SIS Data Server • 26 To power up a simplex SIS Data Server • 25 To provide power to SISNet Distance extenders • 47 To provide power to the Logic Solvers • 46 To provide power to the SISNet Repeaters • 46 To remove a redundant SIS Data Server • 26 To restart (reboot) a Logic Solver • 307 To terminate the local bus • 43 To upgrade an SIS Logic Solver • 320 To use Point Information to identify SIS points • 288 To view SIS points • 284
Voltage Monitor module • 54
W What is a Safety Instrumented System? • 1
U Upgrading SIS firmware • 319 Using algorithm reference pages • 70 Using BAD Status in SIS Modules • 312 Using Fault Codes for SIS (66, 3, 8) • 321 Using Ovation SIS • 285 Using Point Information (PI) to identify SIS points • 287
V Vertical carriers • 15 Viewing SIS points in the Developer Studio hierarchy • 258 Viewing SIS Tuning windows for SIS algorithms • 290
OW331_47
329
