Delta V DCS System

Operator, Maintenance & Configuration

Nawar Talib
ENERGY TRAINING CENTER
www.energytrainingcenter.org
Nawar.Talib@energytrainingcenter.org
nawartalib@yahoo.co.uk
Delta V Overview
 Objectives
Upon completion of this module, you will be able to identify
• DeltaV System architecture
• Delta V Software components
• Common Troubleshooting applications in Delta V
Note: For additional information, refer to DeltaV Books Online
Hardware Installation / Installing Your DeltaV Digital Automated
System.
Delta V System Architecture
10/100BaseT Cable
Workstation Maximum Length 100m (330ft)

Controller
Primary Switch

Secondary Switch
10/100BaseTx Cable
Maximum Length 100m (330ft)
 Delta V System Architecture
The basic Delta V Control Network consists of

• DeltaV Workstation - A personal computer running Windows 7 or Server 2008

operating system, connected to the Control Network. Used for engineering control
strategies, operating the process, and diagnostics of the Delta V system on-line.

• DeltaV Controller - The DeltaV system device that runs the algorithms to control the
process equipment and communicates the process data to the operator.

• Node - A device- either a controller or workstation - on the Control Network.

• Control Network - A communications network connecting various nodes in the

DeltaV system. The Control Network is a 10/l00 BaseTx local area network that
can be redundant. It may also have Fiber-Optic segments.
Note: The DeltaV Control Network is an isolated Ethernet Local area network (LAN).
Ethernet is an IEEE 802.2 & 802.3 specification which describes how computers
communicate over a medium in a Local area environment.
DeltaV System Architecture
 Multiple Nodes
Workstation

Primary Switch Secondary Switch

System Power Supply,

Controller, and
I/O Subsystem

Legend:
Primary Control Network
Secondary Control Network
DeltaV System Architecture
DeltaV System Architecture
 Multiple Nodes
 A DeltaV Control Network with eight nodes is illustrated above.
 Maximums:
 120 – Nodes
 100 – Controllers / Simplex or Redundant Pairs
 65 – Workstations
 30,000 Device Signal T ags (DSTs) per system

Note: A Device Signal Tag (DST) is a DeltaV tag given to a specific

signal that is received from, or sent to, a field device.
 Other nodes can be added, which are not counted against the 120-

node limit: 300 additional nodes, consisting of Wireless I/O Cards,

CHARM I/O Cards, or Remote I/O nodes
- Up to 120 Wireless Gateway nodes
 System Capacity
 System Sizing
◦ 120 max Nodes (redundant nodes count as 1 node)
◦ 65 max workstations of any kind
◦ 1 ProfessionalPLUS Station
◦ 10 max Professional Stations
◦ 59 max Operator Stations
◦ 20 max Application Stations
◦ 72 max Remote Workstations
◦ 8 max Remote Data Servers (ProfessionalPLUS and 7 Application stations)
◦ 15 max (recommended) Remote clients per Professional PLUS or Operator Station
◦ 100 max simplex/redundant Controllers
◦ 30,000 DSTs
◦ 25,000 max (recommended) SCADA tags
◦ 1500 max DST’s per MX Controller, 750 max. DSTs per MD Controller
◦ 15,000 Advanced Unit Management DSTs
 Workstation Licenses
You determine the functionality of each workstation with software licenses. Each
workstation license type, listed below, enables the use of specific functions and
applications on the workstation node to which it is assigned.
• Professional PLUS contains the system-wide licensing. This is the only workstation
containing the active Delta V database, and assigns TCP/IP addressing to other
Delta V Nodes. May be used to configure, operate, and diagnose the system .
• Professional may be used to configure, operate, and diagnose the system .
• Operator is typically used to monitor and manipulate the process using the
Operator Interface.
• Application is typically used for integrating Delta V system with other networks and
third-party applications. Not used for configuration or operations.
• Maintenance Station is tailored to maintenance personnel. Diagnostics, Control
Studio (view only), commission, decommission, calibrate, and configure field devices,
and download fieldbus devices.
• Base allows you to customize functionality.
Workstation Licensing
 Workstations are licensed, based on the functionality required, as
follows:
◦ ProfessionalPLUS Station – Configuration, Operation and
Configuration Database node
◦ Professional Station – Configuration and Operation
◦ Operator Station – Operation
◦ Maintenance Station – Diagnostics
◦ Base Station – Select necessary functionality
◦ Application Station – Run-time database plus user-selected
applications. User applications include DeltaV Batch software or
other third-party OPC applications for interfacing to the plant
business systems.
 Delta V Licenses
One System ID Key, typically located on the Professional PLUS workstation, is required
per DeltaV System.
Licenses are encoded ensuring they will only work with a matching System ID Key. The
System ID Key must remain on the Delta V workstation. If removed, the operator will be
able to control the process but the download function is disabled.
Device Signal Tag (DST) Licensing
 DST licensing is based on the number of inputs and outputs as
follows:
◦ Analog Output
◦ Analog Input
◦ Discrete Output
◦ Discrete Input
 Each instrument, wired into a set of screw terminals, requires one
DST. Start with the P&ID and count the number and type of
instruments when identifying the required DST licensing. The
exception are FOUNDATION fieldbus devices. Such intelligent
devices can have multiple inputs and outputs per instrument
resulting in multiple DSTs for a device.
Delta V Zones
 Delta V Zones
Delta V Zones allow multiple Delta V systems to communicate operating data and
alarms between one another via InterZone Servers (IZS).
Each zone is a standalone Delta V system comprised of the Professional PLUS
node, an Inter-Zone Server node, and other nodes as desired.
Zone considerations:
• The ability to upgrade systems independently while maintaining
communications
• Large systems greater than 30,000 DSTs and/or 120 Nodes
• A maximum of 15 Zones
• Optional redundant IZS
• Each Zone requires a license
Delta V Hardware
DeltaV I/O Interface
2-Wide Power/ 8-Wide I/O
Controller Carrier Interface Carrier

Mounting Screw
DIN Rail I/O Card I/O Terminal Block
DeltaV I/O Interface
The I/O Subsystem includes I/O Interfaces mounted on one or more 8-wide I/O Interface Carriers
and an optional power source that provides power to field devices.
The I/O Interface consists of the following components as illustrated above:
I/O Terminal Block snaps onto the I/O Interface Carrier to provide screw terminations for field
wiring.
I/O Card snaps over the I/O Terminal Block on the I/O Interface Carrier to convert field signals
to a digital format for control and communications.
Refer to DeltaV Books Online for additional information about the DeltaV System’s architecture.
DeltaV I/O Card Types
Analog Inputs
• AI, 8 Channel, 4-20 mA, HART
• AI, 16 Channel, 4-20 mA, HART
• AI, 4 Channel, Isolated Input (Tcouple, RTD, MVolt, Ohms, Voltage)
• Intrinsically Safe, I.S. AI, 8 Channel, 4-20 mA, HART
• Millivolt, 8 Channel
• RTD, 8 Channel
• Thermocouple, 8 Channel
DeltaV I/O Card Types
Discrete Inputs
DI, 8 Channel, 24 VDC, Isolated
DI, 8 Channel, 24 VDC, Dry Contact
DI, 8 Channel, 120 VAC, Isolated
DI, 8 Channel, 120 VAC, Dry Contact
High Density DI, 32 Channel, 24 VDC, Dry Contact
Intrinsically Safe (I.S.) DI, 16 Channel, 12 VDC I.S. Power
Multifunction, 4 Channel, DI or Pulse Input (High Frequency)
DeltaV I/O Card Types
Analog Outputs
AO, 8 Channel, 4-20 mA, HART
I.S. AO, 8 Channel, 4-20 mA, HART
DeltaV I/O Card Types
Discrete Outputs
DO, 8 Channel, 120/230 VAC, Isolated
DO, 8 Channel, 120/230 VAC, High Side
DO, 8 Channel, 24 VDC, Isolated
DO, 8 Channel, 24 VDC, High Side
High Density DO, 32 Channel, 24 VDC, High Side
I.S. DO, 4 Channel, 12 VDC I.S. Power
DeltaV Communication Interface
FOUNDATION fieldbus Interface
• 2 Ports, maximum of 16 Devices/Port, 1900 meters
DeviceNet
• 1 Port, maximum of 61 Devices, 500 meters @ 125K baud
Profibus DP
• 1 Port, maximum of 64 Devices, 2000 meters @ 1.5M baud
Actuator Sensor Interface (AS-i)
• 2 Ports, maximum of 31 Devices/Port, 300 meters
Serial Interface
• 2 Port Modbus Protocol, RS232/RS485 or 2 Port Programmable
Remote I/O
Remote I/O consists of a Remote Interface Unit and I/O cards. The Remote Interface Unit
communicates on the control network and allows the I/O to be mounted Ethernet distances from
controllers that are supported by the control network.
The Remote Interface Unit is considered a node on the control network but does not count
against the 120 node capacity. Remote I/O cards can be assigned to different controllers on a
card-by-card basis. Controller

Remote Interface Unit

DeltaV Remote I/O Card Types Zone 2
Analog Inputs
• AI, 8 Channel, 4-20 mA, HART
• AI, 16 Channel, 4-20 mA, HART
• Millivolt, 8 Channel
• RTD, 8 Channel
• Thermocouple, 8 Channel
Analog Output
• AO, 8 Channel, 4-20 mA, HART
DeltaV Remote I/O Card Types Zone 2
Discrete Inputs

DI, 8 Channel, 24 VDC, Isolated

DI, 8 Channel, 24 VDC, Dry Contact

DI, 8 Channel, 120 VAC, Isolated

DI, 8 Channel, 120 VAC, Dry Contact

High Density DI, 32 Channel, 24 VDC, Dry Contact

Discrete Outputs

DO, 32 Channel, High Density

DO, 8 Channel, 120/230 VAC, High Side

DO, 8 Channel, 120/230 VAC, Isolated

DO, 8 Channel, 24 VDC High Side

DO, 8 Channel, 24 VDC, Isolated

DeltaV Remote I/O Card Types Zone 1
Analog Input/Output
• 8 AI Channels, 4-20 mA, HART
• 4 AO Channels, 4-20 mA, HART
Discrete Input/Output
• 16 DI Channels, Dry Contact
• 8 DO Channels, High Side
Refer to DeltaV Books Online . . .
Configuration  I/O configuration  DeltaV Remote I/O
For card specifications, refer to the HART Analog Input Channel specifications, HART Analog
Output Channel specifications, Discrete Input Channel specifications and Discrete Output
Channel specifications topics in the Installing Your DeltaV Zone 1 hardware manual.
DeltaV SIS - SLS 1508 Logic Solver
 16 channels of I/O per Logic Solver consists of a mix of:
◦ HART Analog Input
◦ Analog Input
◦ HART two-state Output
◦ Discrete Input 12 VDC dry contact
◦ Discrete Output 24 VDC High Side
◦ Line fault detection on I/O
◦ Separate I/O processor
◦ Redundant Main Processors
◦ 50 ms Module Execution
◦ SOE timestamp at module execution
◦ Eight additional Boolean values published Peer-to-Peer on every
scan
Controller
2-Wide Power/ 8-Wide I/O
Controller Carrier Interface Carrier
I/O Card

DIN Rail
Mounting Screw I/O Terminal Block
Controller
M-series Controller
M-series Controller

Controller I/O Hardware Support

•64 Local I/O Cards

Controller Software Support

• 1500 DSTs per Controller maximum (MX)
• 750 DSTs per Controller maximum (MD)
 S-series
The SD and SX controllers offer the same performance and DST capacities as the MD and MX controllers
respectively. The S-series provides the same I/O card types and number of I/O cards as the traditional M
-series. S-series controllers are required for Wireless I/O cards and Electronic Marshalling
S-series Controller

Controller I/O Hardware Support

• 64 Loca1 I/0 Cards

Controller Software Support

• 1500 DSTs per Controller maximum (SX)
• 750 DSTs per Controller maximum (SD+)

I/O Anywhere Support

• Up to 16 CIOCs CHARM I/O Cards and WIOCs
Wireless I/O cards
Switches
Unmanaged switches provide a means to connect multiple nodes in smaller DeltaV systems
containing less than 15 network devices. This type of switch serves as a connection point and
rejuvenates the electrical signal as messages are forwarded on the control network.
DeltaV Smart Switches are the preferred switch to be used within the DeltaV network as they
provide network management and automatic lockdown capability. The switches are plug-and-
play and pre-configured for a DeltaV Network.
To ensure that you have proper switch configuration and the correct switch software for your
DeltaV system, you should purchase switches through normal Emerson channels.
Switches
Available unmanaged switches for small systems consisting of less than 15 nodes:
Allied Telesyn AT-FS708, 8-port 10/100Base-TX
Allied Telesyn AT-FS 709FC, 8-port 10/100Base-TX, 1 Fiber port
Emerson Media Converter, 4x10/100Base-TX to 1x100Base-FX, Class 1 Div2
DeltaV Smart Switches
DeltaV Smart Switches offer a variety of environmental, mounting and sizing options.

RM100 MD20/30

FP20
DeltaV Switches
Available DeltaV Smart Switches:
• FP20 is a Fixed Port with 8 ports
− Wired and fiber combinations
− Extended operating temperature range (-40° to 70°C) for remote mounting
• MD20/30 is a Modular DIN rail with up to 24 ports
− Eleven different modules wired and fiber ports
− Extended operating temperature range (-40° to 70°C) for remote mounting
− MD30, 2 Gigabit uplinks, up to 26 ports
• RM100 is Rack Mountable up to 24 ports
− 2 Gigabit uplinks, fiber or wired
Gigabit connections are supported only between switches. Connections between controllers and
workstations are 10/100MB.
DeltaV System Power Supply
G Bulk Power Supply
N Power
Distribution
N
Ground DC Return

- +

Pwr
Fault

DC Return
1
2
3
4
5
6
7
8

Bulk Power Supply

System Power Supply

2 3 4 5 6 7 8

2-Wide I/O Carrier

Power/Controller Carrier
DeltaV Power Supplies
The DeltaV System Power Supply consists of the following options:
• System Power Supply (AC/DC) – Input 110 VAC or 220 VAC
• System Power Supply (Dual DC/DC) – Input 24 VDC or 12 VDC
The DeltaV Bulk Power Supply consists of the following options:
• Bulk AC to 24 VDC Power Supply
• Bulk AC to 12 VDC Power Supply
An Intrinsically Safe Power Supply is available for the Intrinsically Safe I/O:
• Intrinsically safe (DC/DC) - Input 24 VDC
 Wireless Network and I/O Network
The DeltaV Wireless I/O Network contains Wireless I/O Cards (WIOCs) and Wireless
Gateways. The DeltaV I/O Network contains Charm I/O Cards (CIOCs) and Charms.
These nodes on th e Control Network are not counted against the 120 node limit for
Delta V controllers and workstations.
• Wireless I/O Cards - The WIOC provides redundant communications between S-
series controllers and Smart Wireless Field Links, which communicate to wireless
HART field devices using a self-organizing network. The WIOC supports up to 99
wireless HART transmitters.
• Charm I/O Cards and CHARMs- CIOCs and CHARMs together are called CHARM
I/O. CIOCs are simplex or redundant cards that process signals from up to 96
configurable channels called CHARMs and make the CHARMs' signals available to as
man y as four S-series controllers over the Delta V Control Network.
• Smart Wireless Gateway - The Smart Wireless Gateway integrates signals from
HART Wireless devices into the Delta V system. The Delta V system supports up to
120 Wireless Gateway nodes.
 Delta V Smart SIS
The Delta V Smart SIS provides an integrated approach to the entire safety instrumented function
(SIF) - from sensor to logic solver to final control element - as a complete entity. The use of digital
intelligence and predictive diagnostics increases system availability while reducing life cycle costs
and enabling easy regulatory compliance. The purpose is to take a process to a safe state when
predetermined hazardous conditions arise.
Delta V Smart SIS

SIS Capacities
• 32 Smart Logic Solvers per Controller Node
• 100 SISNet Controller Nodes per DeltaV System
• 3200 Smart Logic Solvers in a DeltaV System
• Controller nodes can be M-series and/or S-series
Delta V Troubleshooting
Troubleshooting Break Points
 Troubleshooting an Abnormal Symptom
Troubleshooting an abnormal symptom, whether hardware or software related,
is accomplished by first determining the location of the problem; accomplished
by establishing breakpoints for testing. The model, illustrated above, is a good
breakdown for DeltaV.
Keep this breakdown in mind as you look at the DeltaV tools in this course
and develop your own troubleshooting style or method.
 Workstation/Common Troubleshooting Tools
Delta V Diagnostics
Use DeltaV Diagnostics as a starting point to diagnose nodes (controllers and
workstations), communications, I/0 cards, channels and assigned modules in your
DeltaVSystem. This application detects and identifies hardware and software faults.
 Workstation/Common Troubleshooting Tools
Delta V Alarm List Display
The Alarm List display contains active acknowledged, active unacknowledged, and
inactive unacknowledged alarms. Al arms include control module alarms, hardware alarms
(Controllers and Workstations), HART device alarms, and Fieldbus device alarms.
Access the Alarm List from the button on the tool bar window in the Delta V Operate
(Run).
 Workstation/Common Troubleshooting Tools
DeltaV Process History View - [Event Journal]
The Event Journal is displayed using the Process History View application. Open the
Process History View application by clicking the Process History View button on the
Operate Run Tool bar The Event Journal provides a spreadsheet-like view of the events
occurring in the process control system.
 Workstation/Common Troubleshooting Tools
Delta V Control Studio
Control Studio is an application used to design and modify the individual modules and
templates that make up your control strategy. While in the on-line view, you can step
through an algorithm and see the specific input and output values of a function block.
This allows you to solve problems, identify areas to increase performance, and gain an
understanding of a function .
 Workstation/Common Troubleshooting Tools
Delta V Explorer
The Delta V Explorer presents a view of the overall structure and layout of your system.
The tree view shows your control strategies and the hierarchy of the nodes on your
Control Network. These nodes can be physically connected to the system, or they can be
placeholders configured prior to the installation of the actual hardware.
 Workstation/Common Troubleshooting Tools
AMS Intelligent Device Manager
From Delta V Explorer, you can launch AMS Intelligent Device Manager in context from
FOUNDATION fieldbus, HART, and PROFIBUS-DP devices.
Delta V Software
User Station Software Components
 The DeltaV User Station Software consists of
◦ Operate
◦ Configuration Suite
◦ Diagnostics
DeltaV Operate
 The DeltaV Operate (Run) is used by the operator to view and
control the process. It consists of three items:
◦ Button Toolbar
◦ Working Area
◦ Alarm Banner
 DeltaV Operate (Configure) is used to create and edit DeltaV
graphics.
 Access DeltaV Operate by selecting . . .
 Start  DeltaV  Operator  DeltaV Operate Run
DeltaV Operate
Button
Toolbar

Working
Area

Alarm
Banner
DeltaV Operate (Configure)
DeltaV Control Module
 The DeltaV Control Module contains algorithms that define
the control system’s behavior. The DeltaV Control Module
consists of the following:
◦ Hierarchy
◦ Displays
◦ Alarms
◦ Conditionals
◦ Algorithms
◦ Module
◦ I/O
◦ Parameters
DeltaV Configuration Suite
 The DeltaV User Station Configuration Suite includes the
following:
◦ DeltaV Explorer
◦ Control Studio
DeltaV Explorer
 Access the DeltaV Explorer by selecting . . .
 Start  DeltaV  Engineering  DeltaV Explorer
DeltaV Explorer
 The DeltaV Explorer is used to view and edit the system’s configuration.
Use the Explorer’s pull-down menus to perform various DeltaV-related
functions or use the buttons at the top of the DeltaV Explorer window to
access other DeltaV programs. Also, use the plus (+) and minus (-)
symbols to expand and collapse the selected item.

Access buttons

Pull-down menus
DeltaV Control Studio
 Access the DeltaV Control Studio by selecting . . .
 Start  DeltaV  Engineering  Control Studio
DeltaV Control Studio
 A typical DeltaV Control Studio display is shown below.
DeltaV Diagnostics
 Access DeltaV Diagnostics by selecting . . .
 Start  DeltaV  Operator  Diagnostics
DeltaV Diagnostics
 A typical DeltaV Diagnostics display is shown below.
 Commissioning the Controller
 Step 1. Power-up the DeltaV Monitor and Workstation. The initial Windows
XP Professional log-on window appears in approximately one minute.
 Step2. Enter the following information, in lower case, as prompted:
 Username: administrator
 Password: deltav
 Step 3. Click the OK button or press the ENTER key to continue. Wait for the
DeltaV Logon window to appear and the hour glass icon has changed to a
selector.
 Note: Do not select Windows Desktop until completing the DeltaV log-on.
 Step 4. Log-in to DeltaV using the same User name and Password specified
above.
 Step 5. Select Windows Desktop from the FlexLock menu bar.
Decommissioned Controllers
 View a list of decommissioned controllers by launching DeltaV
Explorer by selecting . . .
 Start  DeltaV  Engineering  DeltaV Explorer
 Decommissioned controllers are listed in the DeltaV Explorer’s
Contents window accessed by selecting . .
 Physical Network  Decommissioned Nodes
Decommissioned Controllers
 CTLR-02F896, shown above, is a decommissioned controller.
 Decommissioned State – Controller(s) are non-active members of a
Control Network. For example:
◦ A new Controller added to the Control Network.
◦ A replacement for an existing controller (any new controller starts
in a decommissioned state).
◦ A controller deliberately decommissioned for an extended
scheduled shutdown.
 Decommissioned State Visual Indicators –
 Power LED (Green) ON
 Error LED (Red) FLASH at one second interval
 Active/Standby LED (Green) OFF
 Yellow LEDs FLASH at random
Identify Controller
 Identify the controller from DeltaV Explorer by selecting . . .
 (right mouse button) Decommissioned Controller 
 (left mouse button) Properties  Flash lights
Identify Controller
 Identify State – A specific controller is located on the DeltaV
network. Identify is a property of the controller that can be used to
located a specific controller when multiple controllers are part of a
DeltaV Network. Identify can be performed on Decommissioned and
Commissioned Controllers.
 Identify State Visual Indicators –
 Power LED (Green) ON
 All other LEDs FLASH at one second interval
 Note: Automatically terminate the identify state by closing the
Identify pop-up dialog box or selecting Stop Flashing on the
controller’s Properties window.
Commissioning a Controller & Auto-Sensing
I/O Cards
 Commission –The act of making a controller an active
member of a DeltaV Control Network. A TCP/IP address is
automatically assigned by the ProfessionalPLUS workstation at
commissioning. Commissioning can be performed from the
DeltaV Explorer or Configuration Assistant application. The
last step of commissioning will prompt you to Auto-Sense I/O
cards.
Commissioning a Controller & Auto-Sensing
I/O Cards
Commission a controller and auto-sense the I/O cards from the DeltaV
Explorer
 by selecting the Decommissioned Controller CTLR-02F896 and dragging

and dropping it onto the Control Network or existing placeholder. A

Properties window appears requesting various information.

Drag ‘n Drop
Commissioning a Controller
 Commissioning a Controller
 Define Controller Properties as follows:
◦ Name – A user-defined name with a maximum of 16 characters
containing at least one alpha character. It may also contain $, -, or _.
◦ Description – An optional user description of no more than 255
characters appearing in the DeltaV Explorer. It is for information only
and not used by the controller.
◦ Associate Alarms & Events with Area – Define the plant area that will
be associated with the controller node and subordinate field device
alarms.
◦ Enable System Hardware Alarms – Checking the box  enables
controller hardware errors to appear as alarms.
◦ Enable network redundancy for this node – Checking the box 
enables the secondary control network for the node.
Commissioning a Controller
◦ Show integrity error when not in time sync – Checking the
box  enables an integrity error on this controller when the
time is not synchronized with the master time server.
◦ Node is redundant – A Simplex Controller will be grayed out.
A checked box  indicates the controller is redundant.
Auto-Sensing I/O Cards
 When the above fields have been completed, click the OK button to
continue. The last step in commissioning the controller permits you to Auto-
sense the I/O cards for the controller.

Auto-Sense I/O cards – Clicking the YES button causes the controller to scan
its I/O sub-system and identify the card types and carrier slots where the I/O
cards are installed. By clicking the NO button, the controller WILL NOT SCAN
the I/O sub-system for installed I/O cards but will continue to commission
itself. Auto-sense can be performed at any time from the DeltaV Explorer.
Cold Restart
 Define a cold restart from the DeltaV Explorer by selecting . . .
 CTLR  Properties  Controller tab
Cold Restart
 In the event of a power failure, the controller can download itself
using the configuration data in its non-volatile memory. If the data
in non-volatile memory is not present or does not match the
ProfessionalPLUS database, the controller downloads the download
script from the ProfessionalPLUS workstation.
 You can set this feature on an individual controller basis using the
DeltaV Explorer as shown above. The options are Always Disabled,
Always Enabled (maximum time), or Enabled Within A Time Limit.
 The amount of time is set in any combination of Days (0 to 30),
Hours (0 to 23) or Minutes (0 to 59). Commissioning and
downloading procedures will be executed if power returns to the
controller in less than or equal to the cold restart time. A time
setting of 0 sets the cold restart option to Always Disabled.
Cold Restart
 It is further recommended that a UPS be installed between
the AC distribution (source) and the System Power Supply for
the controller(s) to ensure controller operations during short
interruptions of plant power.
 Refer to Books Online for additional information about Cold
Restart.
 Search for Preserving Configuration During Power Loss.
DeltaV Explorer Indicators
 Access Help by right clicking the controller and selecting What’s This? from the
pop-up menu.
Commissioning the Controller
 Commission the decommissioned controller CTLR-XXXXXX
from DeltaV Explorer by performing the following tasks:
 Step 1. Identify the Controller using the Identify State.
 Step 2. Commission the Controller, name it, enable network
redundancy and
 Auto-sense I/O.
 Step 3. Set Cold Restart to 5 minutes.
Delta V Operate with Alarms
 Alarm Banner & Alarm Priorities
Highest ranked alarms appear from left to right. The default color codes are:

• CRITICAL (red)
• WARNING (yellow)
• ADVISORY (purple)
 Delta V Alarm Ranking

Delta V Alarms are ranked in the following manner:

• Unacknowledged alarms are more important than acknowledged alarms .
• Alarms with equal acknowledgment status - Active alarms are more important
than inactive alarms.
• Alarms with equal acknowledgement status and active status - alarms with higher
Priority (numeric) values are more important.
• Alarms with equal acknowledgement status, active status and priority value-
NEWER alarms (i.e., alarms with more recent time stamps) are more important
th an OLDER alarms.
 Delta V Alarm List
The Alarm List picture, displayed by clicking the Alarm List button provides a
list of alarms. This list displays alarms that are not visible on the alarm banner.
 Delta V Alarm List
The Alarm List displays all Active alarms visible to the workstation, both acknowledged
and unacknowledged. Inactive unacknowledged alarms are identified by the empty box
in the Ack column.
Alarm Access
An alarm of interest can be examined by selecting it from the list, right-clickin g and
selecting Open Faceplate Display.
 DeltaV Operate- Faceplates
A faceplate contains information about a control module
and the device. A typical faceplate contains the following
Parameters:
• Setpoint (SP)- shown in white
• Output- shown in cyan (blue)
• PV - shown in yellow
• Mode
•Alarm levels

A set of buttons on the bottom of the faceplate provides

access to additional information.
 Faceplate Buttons
Buttons along the bottom of the faceplate provide access to other screens and applications that
help you determine the problem.
 DeltaV Operate- Opening a Faceplate
There are several ways to open a faceplate:
•Click an alarm indicator in the Alarm Banner. This works only when there is a
check box in the Enable/Disable Faceplate icon in the lower-right area of the Alarm
Banner.

•Click the Search Utility icon and type the first few letters of the control mod ule
name in the Search di alog box. Click the appropri ate modul e name, then click the
faceplate icon.
 DeltaV Operate- Opening a Faceplate
• Click the Faceplate button on the Delta V Operate toolbar and type the name of the
control module name in the Open Module Faceplate dialog box. The name must be
typed exactly as it appears in the database, although it is not case-sensitive.

l
Click an object on the operator display if it is configured to open the faceplate.
 Delta V Operate - Additional Information
In addition to a module's faceplate, there is often a detail sheet that contains more
detailed information.
 Process Alarms
Process Alarms are displayed on the alarm Banner.
 Event Records
The Event Journal is displayed using the Process History View application. The Event
Journal provides a spreadsheet-like view of the events occurring in the process control
system. Each row in the journal is called a record.
Click the Process History View button in the Operate (Run) toolbar to start the Process
History View application. The most recent 8 hours of records appear in the window.
Historic Events
 Event Journal Fields
All Event Journal records contain the following common fields or columns.
• Date/Time - Date and time the event occurred to the fraction of a second
• Event Type- A short descriptor of the event
• Category- A category word used to group event records
• Area- Name of the plant area where the event occurred
• Node - Name of the node where the event was detected
• Unit- Name of the control module's Unit (if applicable)
• Module- Name of the module associated with the event
• Module Description- Description of the control module's function
• Parameter- Further identifies the event using its parameter
• State -The state of an alarm. Values in the State column record the conditions when the
event was detected and may vary depending on the type of event record generated .
• Level- Level column fields indicate the priority, or severity, of the event
depending on the type of event record generated.
• Descl - Records user names for user-initiated events or other descriptive
information depending on the type of event record generated.
• Desc2- Records a user-defined descriptor associated with alarm events
or other descriptive information depending on the type of event record generated.
 Viewing Events
You can sort any column of data in either an ascending or descending format.
For example, to sort the records by time, right-click on the Datefrime column to open a
popup menu that allows you to select a sorting option. Ascending/descendin g refers to
the time stamp of the event.
 Viewing Events
Another option, as shown below, is to select a record or event time, right-click, then
select filter before or after that time. The list is then sorted according to the filter.
 Filtering Event Records

The number of events logged over time can easily run into the thousands and be
overwhelming. Filters allow you to abbreviate the list of Event records in order to meet
a specific criteria.
Assume MTR-102_M is of special interest. As shown below, ri ght-click on MTR-
102_M to display only events for that module.
 Filtering Types of Events
The Modify Filter Settings button allows you to filter the event journal using multiple
parameters. The Filter Se ttings dialog has tabs to select the parameters. In the example
below, the Event Type tab is selected.
 Trend Charts
Trend charts can be a valuable tool in troubleshooting problems. Two buttons on the
bottom of faceplates allow you to open real-time and historical trend charts:

Opens a real-time trend chart containing the parameters defined for that
module. The default timeline is one minute.

Opens the Process History View application with a historical chart of the
parameters defined for that module. Use the timeline controls to view the time
period of interest.
 Tuning Objectives
Tuning is a controller design (gain, reset, and rate) based on the data obtained from the
process during normal operation or during simple tuning process test.
• Achieve minimum or no overshoot with setpoint changes
• Achieve stable controller operation at significant process parameter changes
You must have the Can Tune privilege to change the tuning parameters.
Launching On-Demand Tuning
 Delta V On-Demand Tuning Window
To use the On-Demand Tuning application in the DeltaV InSight window, select the PID
function block, then c1ick the On-Demand Tuning tab.
Delta V On-Demand Tuning Window
The On-Demand Tuning window provides a trend of the selected block at the top. A
working area for tuning is provided at the bottom of the window.
On-Demand Tuning Parameter Setup
• Integrating process - Select this option if the PV represents an accumulation the process.

• Step size- Determines the percent control OUT change from its initial value during test.

Note: Start with small step changes as recommended in the Tuning General Guidelines.

•Test- Starts the Tune application's calculation for Process Dynamics.

Delta V Diagnostics
 Delta V Diagnostics
Delta V Diagnostics captures and logs diagnostic events as they happen, making it possible
to immediately access overview or detailed system information.
Open Diagnostics from Delta V Operate by clicking the Diagnostics button
Delta V Diagnostics
From the DeltaV Explorer, right-click on a node and select Diagnose fro m the contex t
menu, or click the Launch Diagnostics button in the button bar.
Delta V Diagnostics
When Diagnostics is launched, the tree contains the names and icons of the nodes on the
Control Network. Select an icon to view its details .
Delta V Diagnostics
The Delta V Diagnostic display update rate is 15 seconds by default. By selecting
Options, a three-second rate can be selected and used while the display is open.
The Display Update Rate reverts to 15 seconds when you close Diagnostics .
Delta V Diagnostics
The Control Network level of the tree shows a summary of integrity and communications
statistics for all nodes.
Delta V Diagnostics
When you select a node in the tree, righ-level diagnostics information for that node and
its sub-systems are displayed.
Sub-systems of interest for controllers typically include Communications, I/0, and Redundancy.
Tools
The Tools menu provides access to a number of applications and operations, including a
redundancy switchover, as shown below
Controller Communication Status
To display details on the status of communication as seen by a node, select. . .
(right-click) Communications - Display Comm Connection List The Communications
Connection List dialog box appears. This shows all the nodes that the selected node can "see"
on the Control Network
Identifying Decommissioned Nodes
Decommissioned nodes can be identified by flashing their LEDs
Controller Status Summary
The subsystems under a Controller are typically Communications, I/O, Remote I/O, Wireless Gateways, Assigned
Modules, and Restart. If applicable, a Redundancy sub-system represents the Standby controller.
Integrity Fault
An Integrity fault is indicated by the Integrity icon ? beginning at the root level. As you drill down, the icon
appears on each menu item with a fault. The Integrity icon also appears in Delta V Explorer, but only at the node
level.
Integrity Fault
Click the plus sign next to the I/0 icon to drill down and view additional information.
Diagnostic Example - Simplex I/O Card
I/0 Card information is available by selecting the I/0 Card in the directory tree in the left
pane.
Simplex I/O Card BAD
The Contents pane indicates that CH01 Status is Bad, and has a Device Failure. The
Integrity History indicates when Channel 1 failed.
Assigned Modules
The Assigned Modules selection below a Controller contains software information,while the l/0 Network and
SIS Network directory tree selections provide hardware information.
Module-Level Parameters
Select a specific Control Module to view its individual information
Module-Level Parameters with Errors
An Integrity Error indication at the Control Module level is a configurable choice.
Enabling Simulate in a Control Module may not cause an Alarm or Integrity Enor.
However, this state is visible in Diagnostics
DI Line Fault Detection
"detects" an open or short circuit. To detect an open circuit, the dry
contact must be connected to a 8.8 k. Ohem resistor in parallel. The dry
contact must be connected to a 2.4 k. Ohem in series to detect a short circuit.
The resistor circuit should be installed at or near the field device.
Line fault detection is built into NAMUR sensors. Do not use external resistors
with NAMUR sensors; however, you must enable Line Fault Detection in your
configuration when using NAMUR sensors. Resistors for DO Line Fault
Detection are not required.
I/O Card Failure Action- Loss of Controller

AIl Delta V system I/0 cards support failure action. What each type of card does is
dependent on the card type.
After the controller downloads the I/0 card configuration, a two-second Rail Time Out
is enabled.
If communications is lost between the I/0 card and the controller for more than two
seconds, the I/0 card will enter the failure action mode as long as 12 VDC system
power is available.
For Analog or Discrete output channels (each channel is independently configured),
the Fail_Action_Mode Parameter default value is Hold Last Value.
The Fail_Action_Mode Parameter can be changed to Go To Configured Failure Action
Value; the channel will then use th e value of the Fail_ Action_ Val parameter. The
default values are False for DO and 0% for AO.
M-series I/O Terminal Blocks
M-series I/O Terminal Blocks

I/0 tennin al blocks provide connections for field device wiring. To simplify installation,
I/0 terminal blocks have field wiring protection keys that correspond to keys on the I/0
card s. The keys ensure that the I/O card and the I/O terminal block match; an I/0
card plugs into an I/O terminal block only if the keys match.

Redundant terminal blocks have make-before-break magnetic latching relays whi ch

permits the field device signal to switch between a redundant pair of I/O cards. Each
redundant terminal block is labeled for the I/O card types. The example above shows
Analog Input Field Type, indicating that only Analog Input card s are plugged onto this
terminal block.
M-series Horizontal I/O Carrier Extension
Delta V Controllers
Delta V Controllers
The controller executes a series of control modules, which is a software element that is
usually connected to and controls a single piece of field equipment. Control modules
link algorithms, conditions, alarms, displays, and other characteristics together. The
control modules are downloaded to the controllers from th e Professional Plus
workstation.
The Controller also performs conm1uni cation tasks, receiving instructions from and
sending information back to workstations on the Control Network.
S-Series and M-Series controllers perform the same functions, but differ in their
physical appearance, connections and power distribution. The S-series supports l/0
such as CIOCs (CHARM l/0 cards) and WIOCs (Wireless VO cards) that is not
supported by M-series
Delta V v 11.3 Controller Compatibility

DeltaV v 11 .3 supports MD, MD+, MX, SD+, and SX controllers.

• The SD+ and MD+ controllers have 48MB of user memory and support up
to 750 DSTs
• The SX and MX controllers have 96MB of user memory, support up to 1500
DSTs,and are twice as fast as the SD+/MD+
Note: The MD controller is still supported for installed base replacements.
For new M- series installations the current controllers are MD+ and MX.
Redundant Controllers
Redundant controllers provide backup for process control and allow online
upgrade of the controller. Controllers must be of the same type and version
for redundancy
Commissioned Controllers
Controllers are normally in the commissioned state; it must be commissioned
and downloaded in order to manage the process.
Locate commissioned controllers on the Control Network by selecting . .
M-series Controller LEDs
S-series Controller LEDs
Identify Controller
Identify the commissioned controller by selecting....
Identify Controller

Identify is a controller function that can be used to locate a specific controller

when multiple controllers are part of a DeltaV Control Network. Identify can
be performed on both decommissioned and commissioned controllers.
Visual indicators in the Identify state are:
Power LED (Green): ON
A11 other LEDs: FLASH at one-second interval
Note: Closing th e Properties dialog box automatically terminates the identify
state.
Decommissioned Controllers
Decommissioning a controller takes it out of service and unbinds th e controller MAC
address from the DeltaV database. When you decommission a controller, all th e
information in the controller is erased.
Locate Decommissioned controllers on the Control Network by selecting .
Decommissioned Controllers

Controllers are in one of two states: Decommissioned or Comrnissioned.

In the decommissioned state, controllers are non-active members of a Control
Network
and the process is not active. Controllers are in this state when:
• A new controller is added to the Control Network
• You remove and replace an existing simplex controller; the new controller will be
in a decommissioned state
• You decommission a controller (take it out of service) for an extended shutdown
or move it to a different location on the Control Network
Visual indicators on a decommissioned controller are:
Power LED (Green): ON
Error LED: FLASH at one-second interval
Active/Standby LED (Green): OFF
Yellow LEDs: FLASH at random rate
Delta V Visual Indicators
Delta V provides visual inductors used throughout the different applications to display
such things as Node status and integrity, download status, module status and SIS
status.
Select and right-click the object with the visual indicator, then select What's this? from
the menu. Click the More about visual indicators button to open a detailed help window
fo r the visual inductors used in the Delta V system.
Delta V Visual Indicators
Node Status Indicators and Download Status Inductors are the most commonly
seen visual indicators within the DeltaV system.
Delta V Downloads

A download transfers information from the configuration database in the

ProfessionalPlus workstation to nodes on the Control Network. There are two
main types of downloads: Total and Partial.
Delta V Downloads
Download - Transfers controller configuration, setup data, and cold restart memory
from the configuration database of the ProfessionalPLUS to the controller and/or
workstation run-time database. Downloads are performed using Delta V Explorer or
Control Studio.
Two types of downloads:
•Total/Full Download - Downloads the entire configuration for the selected node
(controller or workstation). A total/full controller download following commissioning will
download all Control Modules assigned to the selected node.
Control parameters are set to configured default (Initial) values.
Important: It is not desirable to perform a Total/Full Download on a running process.

•Partial Download- Downloads only specific parts of the configuration ; e.g. ,a single
Control Module. This only affects the Control Module that is being downloaded. Partial
downloads will not change module critical control parameterse.g. SP, Mode, or Out. *

*Refer to Books Online (Downloading Data) for additional information

Cold Restart
Cold Restart allows each Controller node to retain a copy of the last download script
in cold restart memory. Cold restart memory is retained through a power loss. When
power is restored, the controller automatically restarts using the download script in
cold restart memory
Cold Restart

In the event of a power failure, the controller can collission and download itself
using the download script and configuration data in its cold restart memory. If
the cold restart memory is not available, the controller retrieves the download
script from the ProfessionalPLUS workstation.
You enable cold restart memory for each controller using its Properties
windows in DeltaV Explorer. You can select Always Enabled, Always Disabled,
or Enabled Within a Time Limit in any combination of Days, Hours, or Minutes,
up to a maximum of 30 days, 23 hours, and 59 minutes.
Commissioning and downloading procedures are performed if Cold Restart is
Always Enabled, or if power returns to the controller in less than or equal to the
Cold Restart Time.
Emerson recommends that a UPS be used to ensure controller operations
during short interruptions of plant power.
Delta V HART I/O
Delta V HART I/O

Highway Addressable Remote Transducer (HART)

• 2-way (1200 bit/sec) Digital signal superimposed on 4-20 rnA twisted pair wiring
• Communications Protocol Standard for the Digital signal between the HART field
device and the Delta V HART card (AI or AO)
• The Delta V HART card (and/or Handheld Communicator) is the master requesting
information digitally using standard HART commands
• The HART Standard supports 0 to 255 device variables
• The first four variables are Dynamic .
HART Field Device Variable DeltaV
0 Primary variable in engineering units (HART_PY)
1 Secondary variable in engineering un its (HART_SV)
2 Tertiary variable in engineering units (HART_TY)
3 Fourth variable in engineering units (HART_FY)
HART Messages
HART uses Bell 202 standard frequency shift keying (fsk) to communicate
asynchronously at 1200 baud , superimposed at a low level (± 0.5 mA) on
the 4 to 20 mA analog measurement signal as shown below.
HART Messages
HART is a master-slave protocol; a field device only replies when it is spoken to.
There can be two masters; e.g., a control system and/or a hand-held HART
communicator.
Masters issue messages called commands and slaves respond with messages.
For a card with a signal channel enabled HART, approximately two to three messages
per second are sent or received .
The " 1 ' s" and "O's" of the HART signal are interpreted by the master as a series of
hexadecimal numbers as shown below.
HART Device Descriptions (DDs)
HART DDs are used to map the information in the commands and
responses to user interfaces such as AMS Suite: Intelligent Device Manager
HART Device Descriptions (DDs)
The HART Organization provides a standard software library called Device Description
Services which can read the DD binary. Any host with Device Description Services can
intemperate with a HART field device if it has the device's DD.
Device Descriptions .. .
• Define Standard Block Parameters and Supplier Unique Parameters
• Are loaded into a host that supports DD Services (Delta V or a 375/475)
• Are unique for every different device
Delta V Tested Devices
In the DeltaV Explorer Library, the HART Devices folder contains ...
• The list of manufacturers of tested HART devices
• Each listed manufacturer contains specific HART devices
• Each HART device for a manufacturer contains the device description
• A device description, identified by the revision level for the specific device
type
Analog Input / Analog Output Channels
Delta V Analog Input and Analog Output cards for the M-series, S-series, and for
CHARMS support both HART and non-Hart devices, configurable on a channel-by-
channel basis . No additional licensing is required for a HART channel versus a
non-HART. The channel type is configured from the Channel Properties dialog box.
Analog Input / Analog Output Cards
Once a channel has been enabled as HART, note that the D ST (Device Signal Tag)
for the channel now has a different icon than a conventional DST. Also , additional
parameters become available. The associated card or CHARM will require a
download when the channel has been configured and enabled.
Analog Input / Analog
Output Cards
The is an indication of a
placeholder,in this case a channel
that has been enabled HART, but
not yet configured.
A HART -enabled channel can be
configured in one of two ways :
Right-click the DST (not the
channel) and select Properties.
Use the drop downs to identify
the HART device manufacturer,
HART device type, and HART
device revision.
The Safety Lifecycle
High Pressure Hazard
A hazard is a potential source of harm _ As illustrated below, high pressure could result
in a malfunction of the control strategy or equipment. lt could also result in damage to
the environment, equipment, and personnel fatalities.
Risk
History has shown that similar equipment in similar process plants have resulted in one
fatality per 10 years of operation. Unmitigated risk is 0.1 fatalities 1 year
Safety Integrity Level
A SlL is determined by a target risk reduction shown in the right column of the
table below. Various qualitative or quantitative methods can be used to
calculate the target risk reduction which is a combination of likelihood and
consequence of an event
Layers of Protection
Risk reduction can be achieved by adding a layer of protection in the form
of an SIS.
Safety Instrumented Function
A Safety Instrumented Function (SIF) is a combination of sensors, logic solvers, and
final elements with a specified safety integrity level that detects an out-of-limit
(abnormal) condition and brings the process to a functionally safe state.
Average Probability of Failure on Demand
The design team can find the necessary failure data on devices from the
customer database, supplier documentation, third party FMEDA, or third party
certification.
PFDSIFI = PFD FV- 101 + PFD PT- 101 + PFD logic solver
Architectural Constraints
Safe Failure Fraction (SFF) is the relationship between the safe failure fraction and
diagnostic coverage. Failure Mode and Effects Diagnostic Analysis (FMEDA) data is
utilized to determine SFF.

Hardware Fault Tolerance

A hardware fault tolerance of N means that N+ 1 faults could cause a loss of the safety function.
Purpose of the Standards
A study by the Health and Safety Executive (UK) showed accidents involving
control systems resulted from the following causes.

IEC 61508 directed at SIS product manufacturers fol lows a safety life cycle
IEC 61511 Directed at Implementers
Delta V Safety Instrumented
System (SIS) Overview
Basic Process Control System - BPCS
A Basic Process Control System (BPCS) compares process inputs to operator-entered
set points and continuously regulates final control elements to maintain those set
points. The DeltaV automation system is a BPCS and is shown below in a flow control
application.
BPCS - SIS Integration
Data is often passed between a BPCS and the SIS for coordination and interlocking.
The BPCS and SIS are typically from different vendors which can make the integration
effort extensive.
Delta V SIS Hardware
DeltaV combines the BPCS and the SIS. The DeltaV Logic Solver SLS 1508 is plugged
into the same backplane as the BPCS; thus the phrase integrated but separate. For
integration purposes the DeltaV controller can read SLS data and the SLS can read
Delta V controller control data. The Delta V controller and SLS use separate power and
communications. Logic Solvers can be used with M-Series and S-Series controllers
Delta V SIS Hardware
There may be as many as 32 Logic Solvers per M-Series or S-Series controller. Each
Logic Solver can execute up to four SIS modules, each module typically performs a
SIF
I/O
Each Logic Solver has 16 I/0 channels. The channels can be any mixture of
• Analog Inputs
• HART Analog Inputs
• HART Two-state Outputs
• Discrete Inputs
• Discrete Outputs
Logic Solvers can read input channels from any Logic Solver under the same controller.
They can only write to their own output channels
Secure Parameters
DeltaV Logic Solvers communicate with each other using peer to peer communications
through secure parameters and secure parameter references. All Logic Solvers under
the same controller can read any secure parameters on the Local Peer to Peer. Each
Logic Solver has 8 secure parameters or 16 High-density secure param eters that can
be broadcast on the Local Peer to Peer.
SISNet Repeaters
SISNet Repeaters provide communication between Logic Solvers that are attached to
different controllers for Remote Peer to Peer communications. Only Boolean data can
be transferred between SIS modules on different controllers and a total of eight or
sixteen Booleans can be broadcast by a Logic Solver. The SISNet is a fiber-optic ring.
SIS Network
The SIS Network is a separate category in the DeltaV Explorer view and contains
the Logic Solvers and their associated configuration
SIS Network and Domains
The SIS Network is a separate category in the DeltaV Explorer. Logic Solvers are
configured in SISNet Domains under the DeltaV SIS Network. By default the SIS
Network contains Domains that cannot be deleted (but it can be renamed). An
additional 14 domains can be created in the DeltaV SIS Network allowing for individual
SISNets not connected to each other through SISNet repeaters.
SIS Network and Domains
All Logic Solvers that belong to a controller node must be in the same SISNet Domain.
After one Logic Solver card is associated with a SISNet Domain, none of the other
Logic Solver cards on that controller node can be associated with another SISNet
Domain. Multiple controller nodes and their Logics Solvers can be part of a domain
SIS Function Blocks
The SIS Function Blocks are designed specifically for SIS applications.
User Manager
The DeltaV User Manager application allows you to define users and their
respective keys and privileges. The Administrator account DOES NOT have SIS
privileges by default.
SIS Alerts
Traditional safety system srelied on PLCs and non-intelligent field devices. Without
additional testing, you did not know the state of the equipment. The DeltaV SIS, along
with the Rosemount SIS instruments and Fisher SIS digital valve controllers,
incorporate HART technology to alert you if the system has an integrity problem.
SIS Alerts
The Rosemount 3144P and 3051S diagnostics detect failures. You are alerted of
possible failures through SIS Alerts The SIS Alert indicates an alarm on a safety device
TT-l in the illustration below. The operator can view the problem by clicking the device
alarm.
Partial Stroke Testing
While a BPCS is dynamic with outputs continually moving, a SIS is static. On-line testing
can reveal undetected failures of a final element, such as a stuck valve, by partial stroke
testing. Partial Stroke testing can be initiated manually or scheduled with the DVC block.
Delta V SIS Hardware
M-Series Delta V SIS Hardware Components
The SIS 1508 Logic Solvers could be four simplex or two redundant pairs.
M-Series Delta V SIS Hardware Components
• System Power Supply - DeltaV Dual Power Supply 12/24VDC.
• Communication Processor - DeltaV controller provides Primary and Secondary
Ethernet connections to the DeltaV Control Network. Ethernet communications is for
configuration and monitoring only, not for SIS-related functions. DeltaV SIS
requires the DeltaV controller to have a part number of 12P2093X082 or greater,and
hardware revision greater than 5.1.
• Logic Solvers - Contains logic solving capability. Logic Solvers run the SIS
modules that the user configures.
• Terminal Blocks- Field device connections to Logic Solver I/0 channels .
• Dual Right Extender - Terminates the 2-channel peer-to-peer communications for
the Logic Solvers in the example above. The Power/Controller 2- Wide carrier has
the peer-to-peer communication termination built in.
Note: DeltaV SIS requires that you use Part Number 12P 33778XOJ2, Assembly
Number KJ400 JX J-BA 3 or greater for the 2- Wide Power/Controller carrier. This
carrier has a white rectangle at the top of the PWB.
Logic Solver
Internal Architecture
• I/0 CPU reads input data,
adds CRC and sends to MP 2.
• MP 2 error-checks data,
sends data to MP 1 which a
lso error checks data.
• MP 2 publishes data to
SISnet and reads the data
back.
• MP 1 reads the data from
SIS net.
• MP 2 and MP 1 use the data
from SISnet as will any other
logic solvers connected to SIS
net.
Logic Solver Internal
Architecture
MP 2 and MP 1 run the logic
software synchronously, with
certain tasks assigned to only
one processor of the pair.

MP 2 and MP 1 run their

application logic, using
extensive comparison and error
checking to ens ure that the
correct output values are set.
If an error is detected then it
wiII be flagged and all of the
I/O circuits in the logic solver
will be switched off as this is
the only safe course of action
Logic Solver Internal
Architecture
•If the I/O CPU detects an
error,such as a short or open
circuit
in the field wiring, an error will be
flagged. However, the I/0
diagnostics will not trigger a
module shutdown until the
output is required to be
de-energized by the module or
I/O configuration parameters .
DeltaV SLS 1508 Redundant Logic Solver
• Dedicated Redundancy Link between Logic Solver pairs
• Separate power per Logic Solver
• Both Logic Solvers use same input data for checking
• Solvers are synchronized with each other
• Redundant peer-to-peer Link
• I/0 published locally on peer-to-peer
every scan
• Redundant partner is not required
for SIL 3 applications
Delta V SLS 1508 Redundant Logic Solver

In some cases additional availability is required and, in such cases, a

redundant logic solver may be installed. Both logic solvers receive input data
and send output data through a single set of terminals that is wired to the field
devices. In a redundant architecture the two logic solvers work in parallel - it is
not a master/slave arrangement. Both logic solvers read the same input data
and write the same outputs all of the time. The exact methodology is
proprietary and under patent. Active Logic Solver One of the logic solvers is
designated as the active logic solver; this is the one of the pair that makes
data available to the Railbus . Both logic solvers write this data to the field
devices.
Discrete Input 12 VDC Dry Contact
The Discrete Input channels have line fault detection to detect open or short circuits
in fie ld wiring. To use this capability you must:
• Enable line fault detection on a channel-by-channel basis when you configure the
channels.
• Connect the dry contact to a 12KQ external resistor in parallel (for open circuit
detection) and a 2.4K n resistor in series (for short circuit detection).
Emersons End of Line Resistance Module (KJ2231Xl -ECJ) provides this function.
The module connects to the Discrete Input channel and to a field contact.
Discrete Output 24VDC High Side
An RC compensator may be required when driving inductive loads greater than, or
equal to, 0.8 Henry in simplex or 0.3 Henry in redundant. Size the RC compensator at
3.3KOhem and 0.47 Micro F simplex and 2.7KOhem and 0 . 22~-Micro F redundant.
Pulse testing is recommended; however, it can be disabled for field devices such as
solid state relays that cannot support pulse testing. With redundant SLSs, pulse
testing requires partner synchronization and stops if the redundant partner becomes
unavailable.
Note: Emerson's SLS RC Compensator Module (KJ2231Xl-EDJ) provides this
function.The module connects to the Discrete Output Channel and the field load.
Labeled connections for Simplex
and Redundant Logic Solvers.
SISNet Repeaters
SiSNet repeaters provide fiber-optic communications between Logic Solvers attached
to different controllers.
SiSNet Repeaters
• SISNet Repeater Carrier - Provides pass-through connections for rail bus signals
and the+ 12 VDC power required for traditional l/0 cards. It provides peer-to-peer s
ignal connection fro m the SIS Net Repeater to the rest of the system and a
commun ication signal connection betvJeen the two SISNet Repeaters.
• SISNet Repeaters - Provides fiber-optic communications between Logic Solvers
attached to different controll ers. The repeaters are attached to the SISNet
Repeater Carrier. The SISNet repeaters can be placed anywhere in the I/0 sub-
system as long as it is between the peer to peer terminations. Shown below are
two typical locations for the SISNet Repeaters
SISNet Repeaters
SISNet Repeaters' Fiber-Optic Rings
SISNet Repeaters, connected to one DeltaV controller, communicate with SISNet
Repeaters connected to a different controller over a fiber-optic ring.
A local SISNet Repeater collects locally-generated global messages into a s ingle
message and sends it to the SISNet Repeater in the ring. Immediately upon receipt of a
message, the receiving SISNet Repeater forwards the message to the next SISNet
Repeater in the ring .
A global message is forwarded around the ring once. The A SISNet Repeaters form one
fiber-optic ring and B form s another ring.
The tiber-optic ring is a multimode fiber cable; maximum distance between SISNet
Repeaters is 2km.
Each SISNet Repeater requires a separate 24 VDC supply.
SISNet Repeaters' Fiber-Optic Rings
M-Series Integrated Yet Separate
You can mix SIS l/0 and DeltaV M-Series 1/0 in the same controller node. Cost-
effective DeltaV l/0 can be added for non-SIL req uirements. The controller cannot
write to the SLS per IEC 61508.
Note: Conttroler or bussed powerfailure have no affect on Logic Solvers.
Commissioning the Logic Solver
Select the Logic Solver you wish to commission, right-click and select Commission
from the pop-up menu, then click the dialog box's Yes button. Click the Commissioning
dialog box 's Confirm button to continue. Once a Logic Solver has been
commissioned, it cannot be renamed or unassigned until it is decommissioned. In
addition, the card slot and redundancy cannot be changed if the Logic Solver card is
commissioned. Downloading the Logic Solver from Delta V explorer only
Delta V Diagnostics for Logic Solver
The DeltaV Diagnostics application provides information on the status and integrity of
Control Network nodes, l/0 Network, Wireless I/0 Network, SIS Network, and Domains.
Logic Solver Power Loss
An SLS 1508 download is necessary if loss of power is for more than 10 days or it has
been removed from the carrier. Loss of power for less than 10 days causes reload of
the application program from within the SLS 1508, with its initial values, when power is
restored to it. Removing and replacing a partner of a redundant pair does not require a
download. The active partner will configure the standby partner after the power-up self
test is complete.
 Delta V
Safety Instrumented Functions
Reactor Emergency Shutdown
REACTOR-2 requires emergency actions based on one of three causes; High
temperature, High pressure, or Emergency Stop button. If any~ occurs, a specific
set of actions or effects must take place.
Reactor Emergency Shutdown
REACTOR-2 requires emergency actions based on one of three causes; High
temperature,High pressure, or Emergency Stop button. If any cause occurs, a specific
set of actions or effects must take place.
Reactor Emergency Shutdown
REACTOR-2 SIS logic is shown below. The LSCEM function block is used to define
interlock and permissive logic that associates as many as 16 inputs (CAUSE) and 16
outputs (EFFECT). Use the block's MATRlX parameter to identify one or more causes
that result in each effect to trip. When a CAUSE becomes active, all effects
associated with that CAUSE trip.
An LSCEM block cause and effect matrix for REACTOR-2 is shown below.
Cause and Effect LSCEM function block
The chart below indicates the inputs, limits, and what position the final control
element will be depending on which input becomes active.
Note: TT-l is being used by two SIF modules: HIGH-TEMP and REACTOR-2. When a
high temperature is detected, both SIFs will be affected. The following workshop is
associated with SJF REACTOR-2.
Fault Detection on SLS1508 Channels
Faults detected by the SLS 1508 on input channels can originate in field devices, field
wiring, or in the SLS1 508 input circuitry. The SLS 1508 responds to faults detected
on the input channels by integrating Bad status with the channel value and
aru1unciating the fault.
Fault Detection on Discrete Input Channels
Faults detected in discrete input circuitry by the SLS 1508 result in Bad status on
the channel. The SLS 1508 detects open and short circuits in field wiring if line
fault detection has been enabled on the channel using the LINEFAULT_DETECT
parameter. When line fault detection is enabled, you must use a NAMUR sensor
or install Emerson's End of Line Resistance Module. The EOL is install ed at or
near the field device
Fault Detection on Discrete Input Channels
DeltaV SIS Safety Manual Engineering Practices:
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 detection is enabled,
in which case the channel has Bad status.
Fault detection on Discrete Input Channels
LINEF A UL T _DETECT enables the SLS to detect open and short circuit if a user has
added Emerson 's End of Line Resistance Module or external resistors to the wiring.
The
channel parameter is configured as enabled or disabled from the Delta V Explorer
application.
 Rosemount 3144P SIS
Temperature Transmitter
Rosemount 3144P SIS Temperature Transmitter
The 3144P is certified by TUViT to IEC 6 1508 requirements for single transmitter use in
Safety Instrumented Systems up to SIL 2 and redundant transmitter use in Safety
Instrumented Systems up to SIL 3. All safety certified 3 144P temperature transmitters
require safety certified electronics identified by the yellow plastic casing surrounding
them.
The Failure Modes, Effects, and Diagnostics Analysis (FMEDA) report includes failure
rates, comm on cause Beta factor estimates, and independent in formation on generic
sensor models
Rosemount 3144P SIS Temperature Transmitter
The Rosemount 3 144P temperature transmitter features
• Sensor Drift Alert and Hot Backup® improves measurement re liability.
• Communications using 4-20 mA/H ART.
• Optional Integral LCD Display conveniently displays sensor values and transmitter
diagnostics information.
• Single-sensor and dual-sensor input capability allows the transmitter to accept simultaneous input from
two independent sensors, enabling measurement of differential temperatures, averaging temperature, or
redundant temperature measurement. The transmitter can be configured for a variety of sensor inputs
including :
RTD
Thermocouple
Millivolt or ohm
In addition to the availability of dual sensor configurations, the safety certified 3144?
HART transmitter supports the configuration and simultaneous use of Hot Backup and Sensor Drift Alert
Alarm. If one sensor fail s, th e transmitter will switch its output to the remaining "good" sensor. Should the
difference between the two sensor readings exceed the configured threshold, the AO will go into alarm
indicating the sensor drift condition. T he combination of Sensor Drift Alert Alarm and Hot Backup improves
sensor diagnostic coverage while maintaining a high level of availability.
Auto-sense HART Device
HART Device Alarms w ill be displayed beneath the device after an Auto-Sense is
completed . Selecting HART Device Alarms displays the four alarm s in the right w ind ow
pane. Explorer details show if the alarms are Enabled, the Priority of the alarms, and
Alarm Suppression Timeout.
Rosemount 3144P SIS Temperature Transmitter
The Fail Mode Switch
The Milliamp representation of the output value can be viewed from the AMS Dev ice
Manager or 375 Hand Held Communicator. Using AMS view the Process Variables,
there is an AO column displaying the mA output of the transmitter. The LSAI function
block out parameter displays the corresponding out scale value.
The Failure Mode Switch
The 3 144P features software and hardware failure mode detection. An independent
circuit is designed to provide backup alarm output if the microprocessor hardware or
software fails. The alarm level is user-selectable using the Fail Mode switch . If a failure
occurs, the position of the hardware switch determines the direction in which the output
is driven; either HIGH or LOW. The switch feeds into the digital-to-analog (D/A) converter
which drives the proper alarm output even if the microprocessor fails. The values at
which the transmitter drives its output in failure mode depends on whether it is
configured to standard or NAMUR- compliant (NAMUR recommendation NE 43)
operation.
The Security Switch
The transmitter is equipped with a w rite protect switch that can be positioned to
prevent accidental or deliberate change of configuration data to the transmitter. When
the transmitter security switch, located behind the optional LCD indicator, is placed in
the ON position, any changes to the transmitters configuration from AMS Device
Manager or the 375 H and Held Communicator is denied.
The Simulated Process
Objectives
 Upon completion of this module you will be able to
• Define the process to be controlled
• Define the characteristics of the various plant areas
• Define the characteristics of the Device Signal Tags (DSTs)
• Perform a total download
• View diagnostics
PLANT_AREA_A
 Tank101
LEVEL-101
SFC-T101

LI-101

FIC-102
XV-101
MTR-102
= = XVSTAT-101
To Tank201
PLANT_AREA_A Control Modules
 Listed below are PLANT_AREA_A’s control modules:
• LEVEL-101
• LI-101
• XV-101
• XVSTAT-101
• MTR-102
• FIC-102
• SFC-T101 – Sequential Function Chart for automated STARTUP and
• SHUTDOWN
• Operator Display – picture named Tank101
PLANT_AREA_B
 Tank201

From Tank101 PLM-SHUTDOWN

LEV2-SIM LIC-20X

FIC-20X
MTR-203
=
PLANT_AREA_B Control Modules
 Listed below are PLANT_AREA_B’s control modules:
• LIC-20X
• FIC-20X
• MTR-203
• LEV2-SIM
• PLM-SHUTDOWN – Phase Logic Module for automated plant
shutdown
• Operator Display – picture named Tank201
Plant Areas
 Listed below are the characteristics of a Plant Area.
• Contain control modules
• Define user privilege boundaries
• Define workstation alarms boundaries

Workstation 2
Workstation 1
User 1 User 2

Area A Area B Area C

FIC-101 FIC-201 FIC-301

LIC-101 LIC-201 LIC-301
XV-101 XV-201 XV-301
MTR-101 MTR-201 MTR-301
Equipment Hierarchy






Equipment Hierarchy
DeltaV supports a logical hierarchy which includes the following:
Area – logical division of a process control system. Areas typically
represent plant locations or main processing functions.
Process Cell – may be class-based (available to the Batch
Executive) or non class-based. The process cell can be used to
organize units and modules.
Unit Module – allows you to take advantage of advanced alarming
techniques. Units are also key to the Batch Hierarchy.
Equipment Module – a grouping of equipment that performs a
minor task like a totalizer or header. Allows you to take advantage
of advanced alarming techniques.
Control Module – links I/O, algorithms, conditions displays, and
other parameters to the equipment. Modules typically control a
single entity like a motor or flow loop.
Important: DeltaV Batch requires a full hierarchy of area,
cell, and unit to operate properly.
Equipment Hierarchy
Areas

Building A Building B
Process Cells
Raw Materials Raw Materials
Tank A Tank A
Tank B Tank B
Tank C Tank C

Processing Processing
Line A Line A
Line B Line B

Storage Storage
Tank A Units Tank A
Tank B Tank B
Tank C Tank C
Device Signal Tags (DSTs)

Card 1 2
Controller AI AO
CH2 CH2
FIC-102 FT-2 FY-2

IO_IN FT-2
IO_OUT FY-2

FT-2 FY-2
Device Signal Tags (DSTs)
 DeltaV Device Signal Tags are
• Named items which attach an I/O channel to a control module
• Typically named to match an instrument name
• Define I/O properties such as
 Analog In vs. HART
 DO Latching, Momentary or Continuous Pulse
 Defining Plant Areas
 This requires you to define plant areas.
 Step 1. Rename AREA_A as PLANT_AREA_A. From the DeltaV
Explorer select . . .
 Control Strategies  AREA_A  Rename
 Note: AREA_A appears as a highlighted selection in

the Contents window.

Enter the new name PLANT_AREA_A before
pressing the ENTER key.
 Defining Plant Areas
 Step 2. Add PLANT_AREA_B. From the DeltaV Explorer select . .
.
 Control Strategies  New Area
 Note: AREA1 appears as a highlighted selection in the Contents
window. Enter the new name PLANT_AREA_B before pressing the
ENTER key.
Configuring DSTs
Configuring DSTs
 Configure DSTs from the DeltaV Explorer by selecting . . .
 CTLR  I/O  Card # (CO1)  Channel #(CH01)  Properties
 The selected channel’s Properties box appears providing an
opportunity for you to enter the Description, Channel type and
Device Tag. Remember to check the  Enable box to activate the
channel.

 Note: DSTs can also be configured using the I/O Configuration button
on the DeltaV Explorer.
Downloads
 Download the controller from the DeltaV Explorer by selecting . . .
 CTLR  Download  Controller
 Total / Full Download
 A Download transfers Controller configuration, setup data and cold
restart memory from the configuration database of the ProfessionalPLUS
to the controller(s) and/or workstation(s) run time database. Downloads
are performed from DeltaV Explorer or Control Studio.
 Two Main Types of Downloads
• Total/Full Download – Downloads the entire configuration for the
selected node (controller or workstation). A total/full controller
download will download all control modules assigned to the selected
node. Control parameters will go to configured default values. This
download type is performed from DeltaV Explorer.
 Important: It may not be desirable to perform a Total/Full
Download on a running process.
• Partial Download – Downloads only specific parts of the configuration;
i.e., a single control module or card. This only affects the control
module or card that is being downloaded. All partial downloads are
performed from the DeltaV Explorer or Control Studio.
Download Status Indicators
 A triangle with a question mark indicates that some of the
node’s configuration database parameters may not match the
parameters in the node itself. By selecting Update Download Status
the system will determine if differences exist, resulting in a blue
triangle; if the parameters match, the triangle will disappear.
 A blue triangle indicates that some of the node’s
configuration database parameters do not match the parameters in
the node itself. If you perform a download, some changes will be
made to the node. If this indicator is not present, no download is
required.
 A yellow triangle indicates no configuration.
Download Options
◦ Update Download Status – Updates the download status of the
individual Nodes or Network depending on where it is initiated.
Performed from the DeltaV Explorer.
◦ Download Subsets – Configuration data that is not directly related
to a control module or card.
– Setup Data – Includes named sets, parameter security, cold
restart information, redundancy information, alarm preferences
and event chronicle definitions. Setup data can be downloaded
to Controllers and Workstations. Performed from DeltaV Explorer.
– Changed Setup Data – Sends only changed setup data items.
Download Options
• Controller Cold Restart Memory – Updates the controller’s non-
volatile memory so that the Cold Restart download script is valid.
Should be performed after any of the following tasks:
 Controller Upgrade
 Decommissioning and re-commissioning
 Partial download and/or Uploads
 Note: Does not affect the working configuration in the controller!
Download Options
• Re-send Last Known Good Download – Sends the last successful
total download to a node without going to the database.
If you have performed a total download followed by one or more
partial downloads, this function resends the information contained in
the total download as well as the partials. For controllers, the function
sends the same download script that would be sent to a controller
that restarts after a power failure. This is especially useful for
situations where a workstation fails due to a disk error. It enables you
to bring the new or repaired node up to the previous operational
status without downloading recent edits to the configuration.
Do not use this download function after re-commissioning a
controller. Perform a full download after re-commissioning a
controller.
Downloading the Controller
 Download the controller from the DeltaV
Explorer by selecting . . .
 CTLR  Download  Controller
 You will be required to respond to several
options while stepping through the download
process.
Downloading the Controller
 Verify the configuration download options provides the opportunity
to check selected items for unresolved references and other
configuration problems before downloading. You will be alerted to
problems and given the opportunity to resolve them before
continuing with the download.
 The cautionary note below gives

you the opportunity to abort the

controller’s pending download.
Click the Yes button if you wish
to continue.
Download Dialogue Box
Download Dialogue Box
 The Downloading Selected Objects dialogue box above displays the
download’s progress. The checkmark beside each item indicates that
the function is complete. As a specific event is processing, it is
displayed as bold type. Stippled items are events that do not need to
be performed during the current download.
 Creating Log File – creates the log file for the download which is
stored
• on the hard drive. (C or D:\DeltaV\DVData\DownLoadProgress.log)
• Performing Upload Checks – verifies values on uploadable items.
• Performing Pre-download Checks – determines which items are
installable, loaded, created, licensed and if the user has download
privileges.
• Performing Dependency Checks – initiated when Fieldbus devices or
modules with Fieldbus blocks are included.
 Click the Close button to continue when the download is complete.
 Downloading the Controller
 The blue triangles are removed after the download is complete.
Checking the System
Launch Diagnostics from the DeltaV Explorer by clicking the
Diagnostic button
 on the toolbar or by selecting
 Start  DeltaV  Operator  Diagnostics
 Once Diagnostics has been successfully launched, check out your

system.
Summary
 You should now be able to
◦ Define the process to be controlled
◦ Define the characteristics of the various plant areas
◦ Define the characteristics of the Device Signal Tags (DSTs)
◦ Perform a total download
◦ View diagnostics
DeltaV Control Modules
DeltaV Control Modules
DeltaV Control Modules exhibit the following characteristics:
• Unique name –16 characters maximum with one alpha,
alphanumeric, $, -, or_
• Executes control algorithms
• Smallest entity that may be downloaded to the controller
• Flexible size
• May be independently taken out of service
• Independent scan rate per module
• References a primary, detail and faceplate display
• Independent function block scan rate, execute block every
(1-255) module scan(s)
• Set function block execution order, automatically or
manually
Parameter Path

Module FIC-20X

Function Block PID1

Parameter OUT
Module Templates
Module Templates may be used as a
starting point for creating modules. Access
DeltaV Module Templates by selecting . . .
Start  DeltaV  Engineering  DeltaV
Explorer  Library  Module Templates
DeltaV Control Studio
Control Studio is used to define and modify control modules.
Launch Control Studio from DeltaV Explorer by clicking the
Control Studio button or from the Task bar by selecting .
..
Start  DeltaV  Engineering  Control Studio
Creating Module XV-101
DO
CTLR
XV-101

XV-1
= =
Defining a Discrete Output Module
Using Control Studio, create the new control module XV-101 in
the following manner:

Step 1. Right-click on Plant_Area_A  New  Control

Module. Enter XV-101 as the Object name.
Step 2. Right-click on XV-101  Open Open with Control
Studio.
Step 3. Drag and drop Discrete Output from the IO palette.
Step 4. Double-click Filtered by in the parameter window.
Step 5. Check Quick Configuration and Common
Configuration.
Creating Module XVSTAT-101

DI
CTLR
XVSTAT-101

= = LSO-1
Defining a Discrete Input Module
Use the DeltaV Explorer to create the new module XVSTAT-101
in the following manner:
Step 1. From the DeltaV Explorer select . . .
Library  Module Templates  Monitoring

Step 2. Drag and drop the DISCRETE Module Template from

the Library to
PLANT_AREA_A.
Step 3. Rename the module XVSTAT-101.
Step 4. Launch the Control Studio by selecting . . .
XVSTAT-101  Open  Open with Control Studio
 DeltaV Operate (Run)

Launch DeltaV Operate (Run) by selecting the button.

DeltaV Operate (Configure)
Open the DeltaV Operate (Configure) by clicking the
button on the DeltaV Explorer.
Or, from DeltaV Operate (Run), right-click and select

Quick Edit and enter DeltaV Operate (Configure).

DeltaV Operate
Operate Modes
• Configure – used during the picture configuration process
• Run – used to run the Operator Interface
System Tree

• Shows the files associated with the project

• Shows objects associated with each file
• Can be resized, moved or not displayed
Work Area

• Contains the current active picture/document

Menu Bar/Tool Bars

• Contains tools and menu selections that allow the user to

manipulate the current document
Creating a New Picture
New Picture from template
New Picture Objects
Object Terminology
• Object – Comprised of data and procedures that are treated
as a unit
 Rectangle
• Properties – Characteristics of an object
 Color
 Size
 Fill
• Methods – Subroutines that effect the behavior of an object
 Scaling
 Moving
• Events – Actions, initiated by the user, program or the
system, which the object recognizes
 Mouse Click
 Timers Expire
 Values Change
Datalink
Add a datalink to a picture by clicking the Datalink Stamper
button in the DeltaV_ToolBox.

The Datalink dialog

box appears.

Open the Expression Builder / Browser by clicking the browse

(ellipsis) button next to the source field on the Datalink dialog.
Expression Builder / Browser
Adding a Datalink
Step 1.With picture Tank101 open, select the Datalink Stamper
button from the DeltaV_ToolBox.

Step 2.When the Datalink dialog opens, click the ellipsis button
to start the Expression Builder.
Step 3.When the Expression Builder opens, select the DeltaV

tab and click the

Browse DeltaV Control Parameters button to start the
browser.
Step 4.Browse to XV-101/DO1/SP_D.F_CV. Check the Refresh

Rate. Click OK to continue.

Step 5.In the Data Entry portion of the dialog, change the Type

from None to In-Place.

Creating Static Objects / Text
The following steps permit you to add text to identify your
datalinks.
Step 1.Select the Text button from DeltaV_ToolBox and
click on the picture where the text is to be placed. Begin
typing the text. When done typing, click on another object or
on an open area of the picture.
Step 2.Modify the color of the text by selecting . . .

View  Color Selections

 from the menu bar and select the desired color.

Step 3.Modify the text, as illustrated below, by selecting the

text on the picture before selecting . . .

 View  Property Window

 from the menu bar and changing the window’s Caption

property.
Dynamos
A Dynamo is a group of objects that represent a
graphic object such as a pump, valve or
transmitter. Some dynamo objects have dynamic
properties built into them. Dynamos are grouped
and stored in dynamo sets as shown below.
Adding a Dynamo
The following adds a dynamo to your picture.
Step 1.Expand Dynamo Sets in the System Tree. Double click

on Valves2 to display the valve selections in Valves2.fds.

Step 2.Expand Valves2 and select the Valve17 and drag it onto

the picture.
DeltaV Alarms
Objectives

Upon completion of this module you will be able to

• Define basic alarm characteristics
• Create an Analog Output control module
• Define cold restart behavior of parameters
• Define partial download behavior of parameters and
critical block values
• Create an Analog Input control module
• Utilize Visibility and Data Entry Experts
• Create a tank graphic using a Dynamo
• Define detailed alarm characteristics
• Define the Event Chronicle
 DeltaV Alarms

A module
created from a
Module Template
may include
preassigned
alarm(s).
Creating Analog Modules & Defining
Analog Alarms
This requires you to perform the following tasks:
 1. Create an Analog Output control module.
 2. Create an Analog Input control module.
 3. Define Analog alarms.
 4. Add a tank Dynamo.
Defining the Analog Output Module

CTRL1
LEVEL-101 AO

LY-1

= =
Restore Parameter Value After Restart
The Default Value for SP below is 500 which will set the SP to 500 on
a Cold Restart of the controller. However, you may not want the
default value applied on Cold Restart of the controller. By checking
the parameter’s Restore parameter value after restart and the module
level Restore parameter values after restart the current operating
value will be stored in NVM and restored on a Cold Restart.
Parameter Download Behavior
Module Properties also allow you to define the partial
download behavior of a module. This applies to two types of
parameters: user-defined (CAS_SP) and critical block
parameters. Critical block parameters are shown below. A
complete table of critical block parameters can be found in
BOL by searching the phrase downloading data.

Partial Download (Mode) critical block (SP) user-defined

behavior value
Configuration database CAS 500

On-line Value AUTO 555

Preserve critical block AUTO 500

values
Preserve user-defined AUTO 555
and critical block values
Use configured values CAS 500
Using Analog Module Templates
AI
CTRL1
LI-101

LT-1

= =
Modifying the Operator Display
Add LI-101 and LEVEL-101 to the Tank101 display in the
following manner:
Step 1.Launch the DeltaV Operate (Configure) application and

open the Tank101 display.

Step 2.Add the Data Link LI-101/AI1/PV.F_CV.

Step 3.Add another datalink to your picture for LEVEL-

101/CAS_SP.F_CV.
Step 4.Leave Data Entry, on the Datalink dialog, set to None

and click OK.

Step 5.Click the Data Entry Expert button in the
DeltaV_ToolBox with the new datalink selected.
Operating the Analog Module
Operate LEVEL-101 and monitor LI-101 in the following
manner:
Step 1.Run the DeltaV Operate application.

Step 2.Verify LEVEL-101 output manipulates LI-101 input.

Note: Alarms occurring on LI-101 can be acknowledged by

clicking the Acknowledge button on LI-101’s

faceplate.
DeltaV Alarm Priorities
DeltaV Alarm Priorities . . .
• Indicate importance of an alarm
• Affect the order alarms appear in the Alarm Banner and
the Alarm List pictures in DeltaV Operate
• Maximum of 12 alarm priority levels, numeric values
ranging from 4 (lowest) to 15 (highest), and a log-only
priority level of 3.
DeltaV Default Alarms
CRITICAL
(15)
WARNING (11)

 ADVISORY (7)
• Time stamped in the controller
• Included in the list of highest priority alarms
• One to six alarms appear on the Alarm Banner
• May cause audible alarm at the Workstation
• Generate alarm records in the Event Chronicle
• Capture a maximum of two parameters
LOG (3)
• Generate event records in the Event Chronicle
• Capture up to two parameters
DeltaV Alarm Ranking
DeltaV Alarms are prioritized in the following manner:
◦ Unacknowledged alarms are more important than
acknowledged alarms.
◦ Alarms with equal acknowledgment status — Active
alarms are more important than inactive alarms.
◦ Alarms with equal acknowledgement status and
active status — alarms with higher priority (numeric)
values have the greatest importance.
◦ Alarms with equal acknowledgement status, active
status and priority value — NEWER alarms (i.e.,
alarms with more recent time stamps) are more
important than OLDER alarms.
DeltaV Alarm List Display
DeltaV Operate provides an Alarm List Display consisting of an
ActiveX object called an Alarm Summary. The Alarm List
Display is accessed by clicking the bell icon.
DeltaV Explorer Alarm Priorities
Access the DeltaV Alarm Priorities definition from the DeltaV
Explorer by selecting . . .
System Configuration  Setup  Alarm Preferences 

Alarm Priorities 
Alarm Priorities (i.e., Advisory)  Properties
 DeltaV Explorer Alarm Types
Access the DeltaV Alarm Types definition from the DeltaV
Explorer by selecting . . .
System Configuration  Setup  Alarm Preferences 

Alarm Types 
Alarm Type (i.e.,High Alarm)  Properties
Alarm Type Properties
The Alarm Types Properties dialog box defines alarm
characteristics by alarm type. For example, all high alarms use
the alarm word HIGH for the operator display.
The Alarm Types Properties dialog box is also used to

• Modify existing alarm properties

• Add new alarm types
A maximum of 255 alarm types may be added and defined.

• Alarm Word appears in DeltaV Operate when the alarm is

active or unacknowledged.
• Category appears in the Event Chronicle for every alarm
state change.
• Message appears in the standard Alarm List picture. The
alarm message is defined as the description field. It is
also logged in the Event Chronicle.
DeltaV Explorer Alarm Types
Access the DeltaV Alarm Types definition from the DeltaV Explorer by
selecting . . .
System Configuration  Setup  Alarm Preferences  Alarm

Types 
Alarm Type (i.e.,High Alarm)  Properties
DeltaV Alarm Fields
Field R/W A_ASCI F_FLOAT
CUALM Current Alarm R OK/HIGH 0/16

LAALM Latched Alarm R OK/HIGH 0/16

CV Same as LAALM R OK/HIGH 0/16

NALM New Unacknowledged R/W NO/YES 0/1

PRI Priority R/W CRITICAL . . . LOG 15 . . . 3

ENAB Enabled R/W NO/YES 0/1

INV Invert Input R/W NO/YES 0/1

OPSUP Alarm Suppression R/W NO/YES 0/1

SUPTMO Suppression Timeout R/W Time(minutes) Time(minutes)

SUPTMR Suppression Timer R/W Time(minutes) Time(minutes)

Display example: Module/Alarm.Format_Field

LI-101/HI_ALM.A_CV
Default Alarm Type Floating Point Values
DeltaV Alarm Types F_Float DeltaV Alarm Types F_Float
Discrete Device 1 Change From Normal 11
Communication Error 2 Change of State 12
Open Circuit Detected 3 High High Alarm 13
General I/O Failure 4 Low Low Alarm 14
Floating Point Error 5 Rate of Change 15
Over Range 6 High Alarm 16
Under Range 7 Low Alarm 17
Statistical Error 8 Deviation Alarm 18
New Alarm 9 Adapt Alarm Active 254
Any Alarm 10 Inspect Limit Active 255
Modifying the Operator Display
Step 1.Launch the DeltaV Operate (Configure)
application and open the
Tank101 display.
Step 2.Add the following Data Links:

 LI-101/HI_ALM.A_CV
 LI-101/LO_ALM.A_CV
Step 3.Save and close the display.
Operating the Analog Module
Operate LEVEL-101 and monitor LI-101 in the following
manner:
Step 1.Run the DeltaV Operate application.

Step 2.Verify LEVEL-101 output manipulates LI-101 input.

Note: Alarms occurring on LI-101 can be acknowledged by

clicking the Acknowledge button on LI-101’s

faceplate.
ALARMS[1-5] Parameter
The ALARMS[1] Field A_(ASCII) F_(FLOAT)
parameter will display LAALM OK 0
the highest priority LOW 17
alarm that is active for HIGH 16
a given module.
CUALM OK 0
For example:
LOW 17
LI-
HIGH 16
101/ALARMS[1].A_LAAL
NALM NO 0
M
YES 1
PRI CRITICAL 15
WARNING 11
ADVISORY 7
ATTR ALARM NAME N/A
TIN Tue Jan 29, 2009 N/A
14:22:05:.22
ALARMS Control Fields
ALARMS.F_MACK – Module Ack
• Setting to a 1 or YES causes all Alarms in the module to
be acknowledged
• Immediately returns to 0
ALARMS.F_ENAB – Module Alarm Enable

• Setting to a 0 or NO causes all Alarms to be disabled

ALARMS.F_PRIAD – Module Priority Adjustment

• Adjusts the effective priority of all alarms in the module (0

. . . 12)
• Setting to a 0 causes alarms to be treated as pre-
configured priority

Refer to Help on Display Parameters when adding data links

for a more complete list of parameters.
 Workstation Alarm Consolidation
Workstations maintain a list of the most important alarms for display in
the Alarm Banner for THISUSER.
Alarms qualify for the Workstation Alarm Banner by being in an eligible
Plant Area which includes:
• Plant Area configured as part of this workstation’s Alarms and Events
Subsystem
• Plant Area where current user is granted any attribute security write
keys
For example:

• Areas in this node’s Alarms and Events subsystem A B C D

• Areas in which user has write privileges CDEF
• Areas in which alarms are consolidated CD
Alarms by Plant Area
Alarms, grouped by plant area, exhibit the following:
• Every Alarm parameter is part of a Module
• Every Module is assigned to a Plant Area
• Each Workstation informs each controller of the list of
Plant Areas in which it is listening for alarms
• Every state change detected in an alarm parameter
generates an event occurrence record which is sent to
Workstations which are listening for alarms in that
specific plant area
• Workstations maintain a list of active alarms, ordered by
importance, from the event occurrence records they
receive
DeltaV Event Chronicle Time stamped in the controller
DeltaV Event Chronicle Properties – General
Operating the Analog Module
Operate LEVEL-101 and monitor LI-101 in the following manner:
Step 1.Run the DeltaV Operate application.

Step 2.Verify that LI-101/ALARMS[1].A_LAALM functions

properly.
Step 3.Verify that the Event Chronicle is logging alarms and

events.
DeltaV Motor Control
Module MTR-102
DI DO
CTLR
MTR-102

XI-2
= =

ZX-2
Motor-2 State Templates
Access the DeltaV’s two-state motors from the DeltaV Explorer by
selecting . . .
Library  Module Templates  Motors-2State
MTR-11_ILOCK

The driving force behind motor control is the Device Control block (DC). The
parameter window, shown above, displays the DC block’s common configuration
parameters. Selecting STATE_MASKS above displays the STATE_MASKS Properties
box shown below.
State Masks
 The STATE_MASKS Properties dialog box
can be modified to meet specific operating
requirements.
 Empty = 0 value on I/O channel
 Check mark = 1 value on I/O
channel
 Stippled check mark light
gray background = don’t care
 Stippled check mark dark gray
background = not available
• Passive = 0 in named set
• Active1 = 1 in named set
Named Sets
Access the Named Set Properties: mtr2-sp dialog box from DeltaV
Explorer by selecting . . .
Setup  Named Sets
Not all default Named Sets can be modified. However, new Named Sets
can be created as needed.
SP_D Parameter
Selecting the SP_D properties for the DC block allows you to browse for the
available named sets. The names in the named set become the setpoint
names for your DC block.
Device Options
Modify the DeltaV Device Options properties for the Device
Control (DC) block so that it satisfies the process’ control
strategy and the operation’s safety requirements.
Interlocking
Interlocking is provided by the use of condition blocks that evaluate
Expression. The Boolean Fan Input (BFI) block provides a first out trap for
operator indication and the OR block provides operator indication of
bypassed conditions.
Creating a Motor Control Module
DI DO
CTLR
MTR-102

XI-2
= =

ZX-2
Modifying an Operator Display

Modify the operator display by adding motor control module MTR-102 to

the Tank101 display in the following manner:
Step 1. Launch the DeltaV Operate (Configure) application and open
the Tank101 display.
Step 2. Add Datalinks with the following characteristics:
MTR-102/DC1/PV_D.A_CV
MTR-102/DC1/SP_D.A_CV (Data Entry Expert/Multi-Item Select)
MTR-102/ALARMS[1].A_LAALM (Visible only when an alarm is active)
Step 3. Add the Dynamo PumpAnimC1 from Dynamo set
PumpsAnim.
DeltaV Regulatory Control
Objectives
Upon completion of this module you will be able to
• Determine DST license requirements
• Define a Regulatory Control module using the
PID_LOOP template
• Define modes and fields
Device Signal Tag (DST) Licensing
DST licensing is based on the number of
inputs and outputs:
• Analog Output
• Analog Input
• Discrete Output
• Discrete Input
DeltaV keeps track of DSTs as you use
them.
LI-101 references one Analog Input
channel.
As a result, it uses one DST.
Note: DSTs can be substituted for less
functional DSTs. For example, an Analog
Output DST License could be used for
an Analog Input DST.
Total System DSTs
View a system summary of DST usage by selecting from the
DeltaV Explorer . . .
 ProfessionalPLUS workstation  Licensing  Licensing

Properties
DeltaV Licenses
DeltaV licenses are provided in the form of a license file(s) provided on a
mini CD and a unique System Identifier (ID) Key.
Licenses are encoded ensuring they will only work with a matching
System ID Key. The System ID Key must remain on a DeltaV workstation
to permit configuration downloads.

Mini License CD USB System ID Key

Loading Licenses
Licenses are loaded into your DeltaV database as shown below. The file
number must match the number on your System ID Key.
Assigning Licenses to Nodes
Licenses can be assigned to the appropriate node using drag and drop.

Drag ‘n drop
Modes
DeltaV Modes include:
• Manual (MAN) – The output is set by the operator.
• Automatic (AUTO) – The setpoint is adjusted by an external source
and the loop calculates the output based on the algorithm.
• Cascade (CAS) – The setpoint is adjusted by another function
block through the CAS_IN parameter and the loop calculates the
output based on the algorithm.
• Initialize Manual (IMAN) – The block output is being set in response
to the status of the BKCAL_IN parameter. For example, when the
secondary loop is not in Cascade, the primary loop goes to IMAN
to prevent windup.
• Out of Service (OOS) – The block does not perform the algorithm.
The status is set to bad.
Mode Fields
DeltaV Mode Fields include:
• Target – Mode is requested by the operator. Only modes from the
permitted list may be requested.
• Actual – This is the block’s current mode. This may differ from the
target based on operating conditions.
• Normal – This is the mode the block should be set to during normal
operating conditions. May be configured and read but is not used
by the block algorithm.
• Permitted – List of valid mode choices.
Regulatory Control Module FIC-102
AI AO
FIC-102 CTLR
0-100 GPM
FT-2 Gain = 0.5
PV Reset = 3
Rate= 0
SP
P I Reverse Act

FY-2 Increase to Open

FY-2
FT-2
= =
Uploading Parameter Changes
On-line values can be changed from Control Studio or DeltaV Operate. The
Upload option allows you to write on-line values back to the configuration
database. ProfessionalPLUS DeltaV Operate
Configuration Database

FIC-102 Default

Gain 0.5
Reset 3
Rate 0

CTLR

FIC-102 On-line

Upload Gain 0.7

Reset 2.5
Rate 0
Downloading with an Upload
Selecting a download will prompt you with an Upload option if external
changes have been made to the on-line data. If an Upload is not
necessary, click the OK button because, by default, no parameters are
selected.
Upload Select None
When you clicked the OK button on the Upload dialog box above no
parameters are uploaded even though the Upload appears to execute.
This is necessary for internal housekeeping.
DeltaV Cascade Control
Objectives

Upon completion of this module you will be able to

• Perform top down configuration
• Implement cascade control using CASCADE_MASTER
template
• Define Module Block
• Implement flow simulation with an Embedded Composite
Block using the Calc and Filter function blocks
• Implement level simulation with the Integrator Function
Block
• Use Control Studio On-line for testing modules
• Implement the Continuous Historian
Cascade Level Control of TANK201

From Tank101 FIC-102

LEV2-SIM IN OUT
“INT” LIC-20X
CAS_IN

OUT
IN FIC-20X

MTR-203
= FLOWSIM
Secondary Flow Control
FIC-20X

PID1 FLOWSIM
OUTPUT
0-100 GPM PV
IN Gain = 0.5
PV Reset = 3
Rate= 0 FILTER OUT
SP IN FIC-20X
Reverse Act IN OUT
P I
TIMECONST = 2
FLOWSIM
OUT
CALC
Increase to Open
INPUT IN1 OUT1
VO
Pass flow signal only if
MTR-203 is running
Module Block
Module blocks allow one control module to be represented on the
diagram of a different control module.
This allows the interactions between multiple control strategies to be
visually created and maintained while ensuring the isolation and integrity
of each independent module. The module block is graphically wired to
other blocks on the strategy.
 Custom Block Types
• Function Block – A basic block provides commonly used functions for your
algorithm.
• Extended Block – A DeltaV function block is defined to run in a Fieldbus device.
• Embedded Composite – A block that is not linked to the original object. An
embedded composite contains one or more other blocks and parameters. If
changes are made to the original object, this composite will be unaffected. Use
this type when you want an independent, standalone copy of an existing
composite.
• Linked Composite – A block that is linked to a composite block or template. A
linked block is a composite of one or more other blocks and parameters. If
changes are made to the original composite block, the changes will affect this
block.
• Module Block – A block that provides input/output connectors to another
module you are editing. For example, when implementing cascade control,
you could have an inner loop and an outer loop that execute at different rates.
The module block you add here could control one loop, and the module you
are editing could control the other. The scan rate is a property of a module.
Embedded Composite
Modification
of Embedded Composite Blocks DOES NOT
MODIFY instances
• You may drill down and modify an Embedded block
from an instance usage.
• You may drill down and modify the parameters of an
Embedded block.
Linked Composite
Library Composite Template

Param1 CALC1
Edit

PID1 Linked Composite PID1 Linked Composite PID1 Linked Composite

Param1 CALC1 Param1 CALC1 Param1 CALC1
Drill down

Module_1 Module_2 Module_3

Modifying Linked Composite Blocks modifies instances

• You are not permitted to drill down and modify a Linked block from
an instance; you must open another Control Studio application.
• You are permitted to drill down and modify a Linked block’s
parameters. The parameter modifications are only applicable to
the module from which they are modified.
Primary Level Control

IN OUT
LEV2-SIM LIC-20X
“INT” CAS_IN

OUT
IN FIC-20X

MTR-203
= FLOWSIM
Continuous Historian
Continuous Historian allows the collection of user-specified parameters
for long-term storage, retrieval and presentation.
• History Collection – allows you to define module and node
parameters to be monitored and stored in the Continuous
Historian.
• Continuous History Subsystems – monitors modules for history
collection data on a plant area basis because each workstation has
a Continuous History Subsystem capable of detecting and storing
historical data.
• Process History View – displays real-time and historical data from
the Continuous History Subsystems as well as from the Event
Chronicle.
Embedded Trend Configuration
An embedded trend object can be placed in a graphic display by using
the Embedded Trend Control button in the DeltaV_Toolbox.
Double-clicking the object in the configure mode allows you to

configure the chart.

Embedded Trend Operation
Right-clicking
the embedded trend object in the run mode
provides many of the same options as Process History View
shown below.
Summary
You should now be able to
• Perform top down configuration
• Implement cascade control using CASCADE_MASTER
template
• Define Module Block
• Implement flow simulation with an Embedded Composite
Block
• Implement level simulation with the Integrator Function
Block
• Use Control Studio On-line for testing modules
• Implement the Continuous Historian
DeltaV Serial Interface
Objectives
Upon completion of this module you will be able to
• Interface DeltaV with serial devices
• Define Serial Interface wiring connections
• Define Serial Interface capabilities
• Configure the Serial Interface

You will also be required to perform the followings

• 1 – Serial Interface Modbus (Master) - Modicon PLC
• 2 – Serial Interface Modbus (Slave) - PROVOX IDI
• 3 – Serial Interface Tie-back (Master and Slave)
DeltaV Serial Interface

Port 1 Port 2
Serial Interface Cable
Serial Interface Cable

Serial Device Serial Device

The Serial Interface provides communication to various serial devices including PLCs
using Modbus (Master or Slave) RTU or ASCII protocol. You can configure the Serial
Card to support RS232, RS422/485 half duplex or RS422/485 full duplex signals.
DeltaV to PROVOX RS232 Wiring

Serial Card Terminal Block PROVOX Intelligent Device Interface

Port 1 (IDI)

(GND) 1 7 (GND)

(TXD) 3 3 (RXD)

(RXD) 5 2 (TXD)

(DTR) 7 6 (DSR)

(DSR) 8 20 (DTR)

Port 2

(GND) 9
(TXD) 11
(RXD) 13
(DTR) 15
(DSR) 16
Serial Interface Capabilities
Serial Card Port Device 1 Device 2 . . . . . . . Device 16
2 Ports 16 Devices Max
Dataset 1 Dataset 1
16 Datasets/Port
100 Regs/Dataset .
500 DSTs OR 100 Registers-Coils
. .
3200 SCADA /Dataset
. .
. .
RS232
Dataset 16 Dataset 16
(Pt - Pt)
RS422/485 (Multi-drop)

Coils
00001 - 0xxxx

Input Status
10001 - 1xxxx

Input Registers
30001 - 3xxxx

Holding Registers
40001 - 4xxxx

PLC 1 PLC 2 PLC 16

Serial Interface Configuration
Workstation
Serial Interface

Dataset
SCADA
Register Type
Register Address
Number of Registers
or

Coils
DSTs 00001 - 0xxxx
Control Module
Input Status

P Hierarchy Displays 10001 - 1xxxx

a Input Registers
r Alarms
a 30001 - 3xxxx
m Conditionals Holding Registers
e
t 40001 - 4xxxx
Algorithms Module
e
r
I/O Serial Device
s
Serial Card Configuration
Serial Port Properties
Adding a Serial Device
Dataset Definition
Module Configuration
Assume a PLC is reading a flow transmitter and the value is stored in Holding register
40001. By bringing this value into DeltaV as a DST, you can use a control module for
higher level control and alarming. This is accomplished by:
Step 1. Configure a new module with a PID function block.
RTD Card Interface
RTD Terminal Block Wiring

2-Wire 3-Wire 4-Wire

Configure RTD
Step 1. Install your RTD card and terminal block in slot 5.
Step 2. Connect the 3-Wire 100 Ohm Platinum RTD to channel 1 as shown below.

Black

Red

White
Configure RTD
Step 3. Configure a new RTD card. Select Card class:
Analog Input Cards, Card type 8 Channel, RTD and Slot
position 5 as shown.
Alternately, you may autosense the card if it is already
plugged into the carrier.
Configure RTD
Step 4. Select the Properties for channel 1. Define the following key items:
a. Enable the channel.
b. Set the Channel Type to Pt 100 RTD Input Channel.
c. Name the channel with the Device Tag (DST) RTD1.
Configure RTD
Step 5. Set the NUM_WIRES parameter to 3 as shown below. The 100 Ohm platinum
RTD is a 3-wire sensor. Therefore, it is necessary to set the NUM_WIRES
parameter to 3.
Module RMTEMP-101
Step 1. Create a new module as shown above from the Library using the
Monitoring/ANALOG module template.
Module RMTEMP-101
Step 4. Set L_Type to Direct because the transducer, or RTD, has units that directly
relate to the OUT value displayed to the operator, -328 to 1562 °F.
Module RMTEMP-101
Step 5. Set the OUT_SCALE Engineering Units to °C or °F depending on your
preference.
It is not necessary to enter 0% or 100% scale because the system will automatically
scale the output based on the sensor selected on the channel properties. See the result on
the next page.
Module RMTEMP-101
Step 6. Assign to your controller.
Step 7. Save the module as RMTEMP-101.
Step 8. Download the module.
Step 9. Download the RTD card.
Step 10. View the module in the On-line
view. As shown above left, while in edit
mode the 0% and 100% scale is not defined.
Once downloaded the On-Line view shows
both OUT_SCALE and XD_SCALE are
automatically set.
Thermocouple/mV Card Interface
Configure Thermocouple
Step 1. Install your Thermocouple card and terminal block
in slot 6.
Step 2. Connect the type T Thermocouple to channel 1 as
shown.

Blue (+)

Red (­)

Note: If you do not have a Thermocouple available you can simply short screw
terminals 1and 2. Proceed with the configuration on the following pages as if you had
a thermocouple and you will be reading the temperature at the terminal block sensed by
the cold junction compensation.
Configure Thermocouple
Step 3. Configure a new Thermocouple card. Select
Card class: Analog Input Cards, Card type 8
Channel, Thermocouple and Slot position 6 as
shown.
Alternately, you may autosense the card if it is
already plugged into the carrier.
Configure Thermocouple
Step 4. Select the Properties for Channel 1. Define the following key items:
a. Enable the channel.
b. Select the appropriate Channel Type. The example above assumes a
Type T Copper/Constantan (Copper-Nickel) Thermocouple.
c. Name the channel with the Device Tag (DST) TC1.
Configure Thermocouple
Step 8. Verify CJT_CHAN is set to Local Compensation, which is the default. This
will provide cold junction compensation for the entire card by using the internal sensor
in the terminal block. The configuration person could change this to any of the 8
channels. Then the card would use the value on that channel as the temperature for
cold junction compensation.
Module RMTEMP-201
Step 1. Create a new module as shown above from the Library using the
Monitoring/ANALOG module template. The following pages take you through the
AI1 block and modify the necessary parameters to properly read the temperature
from the Thermocouple.
Module RMTEMP-201
Step 2. Set IO_IN Device Tag to TC1.
Step 3. Set IO_IN Parameter to FIELD_VAL to read the temperature in degrees.
If IO_IN is set to FIELD_VAL_PCT, the output will only show the value in percent.
Module RMTEMP-201
Step 4. Set L_Type to Direct because the transducer, or Thermocouple, in this case
has units that directly relate to the OUT value that will be displayed; -454 to 752° F.
Module RMTEMP-201
Step 5. Set the OUT_SCALE Engineering Units to °C or °F; your preference.
It isn’t necessary to enter 0% or 100% scale as the system will automatically scale the
output based on the sensor selected on the channel properties, see the result on the next
page.
Module RMTEMP-201
Step 6. Complete the configuration as follows:
a) Assign to your controller.
b) Save the module as RMTEMP-201.
c) Download the module.
d) Download the Thermocouple card.
Step 7. View the module in the On-line view. As
shown above left, while in edit mode the 0% and
100% scale is not defined. Once downloaded the
On-Line view shows both OUT_SCALE and
XD_SCALE are automatically set.
Multifunction Card
Multifunction Card & Terminal Block
Multi-function card supports four channels configured as
Discrete Inputs (DI) or Pulse Inputs (PI). Power
Error

Multi-function terminal block has 32 terminals available. The

matrix below shows the terminals used with current release
capabilities for the card and the terminal connections for use with
future enhancements.
Multifunction Terminal Block Matrix
The Multifunction Card was designed to support high frequency pulse inputs.

Position 1 Position 2 Position 3 Position 4 Position 5 Position 6 Position 7 Position 8

Top 1 5 9 13 17 (+) 21 (+) 25 (+) 29 (+)

Row AI-Ch 1 AI-Ch2 AI-Ch3 AI-Ch4 DI-Ch1 DI-CH2 DI-Ch3 DI-Ch4
Second 2 6 10 14 18 (-) 22 (-) 26 (-) 30 (-)
Row AI-RTN AI-RTN AI-RTN AI-RTN DI-RTN DI-RTN DI-RTN DI-RTN
Third 3 7 11 15 19 (+) 23 (+) 27 (+) 31 (+)
Row AO-Ch1 AO-Ch2 +24VDC +24VDC DO-Ch1 DO-Ch2 DO-Ch3 DO-Ch4
Bottom 4 8 12 16 20 24 28 32
Row AO-RTN AO-RTN 24V-RTN 24V-RTN DO-RTN D0-RTN DO-RTN DO-RTN

Reserved for future use Currently being used

Pulse Input Specifications
INPUTS
• Input frequency – sine wave 10 Hz - 50 KHz, Square Wave 0.1 Hz - 50 KHz
• Input accuracy – 0.1% reading (over 10 Hz - 50 KHz)
• Resolution – +/- 1 pulse
• Minimum pulse width – 10 microseconds
• Maximum input voltage 26.4 VDC
• Detection level for ON – 4.8 VDC (minimum)
• Detection level for OFF – 1.0 VDC (maximum)
• Isolation – Each channel is optically isolated from the system and each other and
factory tested to 1500 VAC
• Resolution counter – 32 bits
Multifunction Card Channels
 Multifunction Card Channels
Using DeltaV Explorer
The Multifunction Card has four channels used as Discrete Inputs or as Pulse Inputs. The
Multifunction Card is specifically designed for high frequency pulse inputs.
The Channel properties dialog box includes:
Enable – A check in this box enables the channel on the Multifunction card.
Description – Up to 40 characters for a description to appear in DeltaV Explorer
Channel Type – The user chooses between Discrete Input and Pulse Input.
Device Tag – The user may enter a unique name, up to 16 characters, for each channel. The
example above shows Pulse-1.
Multifunction Card Channels
 Multifunction Card Channels
Using DeltaV Explorer
The Pulse Input Channel parameters include:
Counter_In – Usable in control strategies as an external reference Raw Count.
Reset_Count – Usable in control strategies as an external reference. Writing a non-zero number
to this parameter clears the Counter_In parameter.
Channel Type – The user chooses between Discrete Input and Pulse Input.
Device Tag – A unique name, up to 16 characters, for each channel.
The example above shows Pulse-1.
Frequency – Only valid I/O_In parameter to a pulse input function block, also usable in control
strategies as an external reference.
Multifunction Card Channels
 Multifunction Card Channels

Using DeltaV Explorer

The Pulse Input channels provide a count and frequency. The signal frequency is
calculated from the number of pulses received over a configured scan period. You can
define the scan period with the FILTER parameter. In selecting the right filter for the
application, you must determine what emphasis should be placed on precision and what
should be placed on response, particularly for slower frequencies (below 250Hz). The
default filter is 1 second.
Filter Parameter – Selecting FILTER Parameter Properties opens the FILTER Properties
box. A drop-down window titled Named Set provides you with the predefined filter
values that can be used.
As the filters increase, the scan time increases. As the filters decrease, so does the scan
time. Larger filters will give you more precision, but the longer scan rate will decrease
the response to the frequency changes.
Pulse Input Function Block
 Pulse Input Function Block
Using DeltaV Control Studio
Drag and drop a Pulse Input function block from the I/O category of the function block
palette.
Example: A turbine meter used to measure volumetric flow of a gas steam. The pulse
input function block measuring volumetric flow of a natural gas stream.
Pulse Input function block parameters:
IO_IN – Use the browser to select the DST for this input
OUT_SCALE – 0 to X, the range of the meter, used only to back calculate the Field_Val
parameter in percent
Because the meter is pre-set to measure a specific unit, you are permitted to designate
PULSE_VAL – Converts the frequency from the card, from pulses to EU in the
calculation of PV
TIME_UNITS – The lapsed time over which a single pulse’s units are counted
RTD Card Interface
Objectives
Upon completion of this module you will be able to
• Define RTD/Ohm I/O Interface
• Define RTD wiring connections
• Configure the RTD Card
• Configure RTD channel properties
• Configure a temperature module using a RTD sensor
RTD Terminal Block Wiring
The DeltaV RTD/Ohm I/O Interface supports up to 8 RTD or Ohm inputs.
Resistance Temperature Devices (RTDs) change resistance with respect to temperature.
A commonly used RTD is a 100 Ohm platinum sensor with a range from -328°F to
1562°F. The DeltaV RTD card senses the resistance and passes the value as a
percentage to the Controller. An AI block in a control module scales the percentage to a
temperature value in degrees Fahrenheit, Celsius or Kelvin.
In an ideal world a 2-wire RTD would provide a very accurate reading. However, the
lead wire resistance will offset the actual temperature. Thus a 3-wire provides a more
accurate reading because the RTD card can sense the resistance of one lead wire and
negate the lead wire resistance.
However, in a 3-wire application we can only estimate the resistance of the other lead
wire. Thus a 4-wire device is more accurate as it will send a current out (sensor
excitation) and determine the actual resistance of both leads and negate all lead
resistance.
The illustration above shows the wiring connections for 2, 3 and 4-wire RTDs
connected to channel 1.
RTD Terminal Block Wiring

2-Wire 3-Wire 4-Wire

 RTD
This requires you to perform the following tasks:
Task 1. Install the RTD card and terminal block.
Task 2. Wire a 3-Wire RTD.
Task 3. Configure the RTD card.
Task 4. Configure the RTD channel.
Task 5. Configure a control module to show room temperature.
 Configure RTD
Step 1. Install your RTD card and terminal block in slot 5.
Step 2. Connect the 3-Wire 100 Ohm Platinum RTD to channel 1 as shown below.

Black

Red

White
 Configure RTD
Step 3. Configure a new RTD card. Select Card class:
Analog Input Cards, Card type 8 Channel, RTD and Slot
position 5 as shown.
Alternately, you may autosense the card if it is already
plugged into the carrier.
 Configure RTD
Step 4. Select the Properties for channel 1. Define the following key items:
a. Enable the channel.
b. Set the Channel Type to Pt 100 RTD Input Channel.
c. Name the channel with the Device Tag (DST) RTD1.
 Configure RTD
Step 5. Set the NUM_WIRES parameter to 3 as shown below. The 100 Ohm platinum
RTD in our workshop is a 3-wire sensor. Therefore, it is necessary to set the NUM_WIRES
parameter to 3.
 Module RMTEMP-101
Step 1. Create a new module as shown above from the Library using the
Monitoring/ANALOG module template.
 Module RMTEMP-101
Step 2. Set IO_IN Device Tag to RTD1.
Step 3. Set IO_IN Parameter to FIELD_VAL to read the temperature in degrees. If IO_IN is
set to FIELD_VAL_PCT, the output will only show the value in percent which would rarely
be used for a temperature.
 Module RMTEMP-101
Step 4. Set L_Type to Direct because the transducer, or RTD, has units that directly relate to
the OUT value displayed to the operator, -328 to 1562 °F.
 Module RMTEMP-101
Step 5. Set the OUT_SCALE Engineering Units to °C or °F depending on your preference.
It is not necessary to enter 0% or 100% scale because the system will automatically scale the
output based on the sensor selected on the channel properties. See the result on the next page.
 Module RMTEMP-101
Step 6. Assign to your controller.
Step 7. Save the module as RMTEMP-101.
Step 8. Download the module.
Step 9. Download the RTD card.
 Module RMTEMP-101
Step 10. View the module in the On-line view. As shown above left, while in edit mode the 0%
and 100% scale is not defined. Once downloaded the On-Line view shows both OUT_SCALE
and XD_SCALE are automatically set.
Alternative Configuration
The AI block was configured using L_TYPE as Direct. This only requires selecting the units
under OUT_SCALE. If L_TYPE were set to Indirect. The configuration person would have
additional data entry as shown by the .
L_TYPE = Direct L_TYPE = Indirect
XD_SCALE XD_SCALE
100% = * 100% = *
0% = * 0% = *
Units = * Units = °F 
OUT_SCALE OUT_SCALE
100% = * 100% = 1562 
0% = * 0% = -328 
Units = °F Units = °F
*Automatically filled-in based on channel configuration.
Thermocouple/mV Card Interface
Objectives
This module introduces you to the Thermocouple/mV I/O Interface. Upon completion of this
module you will be able to
• Define Thermocouple/mV I/O Interface
• Define Thermocouple wiring connections
• Configure the Thermocouple Card
• Configure Thermocouple channel properties
• Configure a temperature module using a Thermocouple
Thermocouple Terminal Block

Thermocouple sensor
at the process.

Inherent
Thermocouple
(Cold Junction)

Blue (+) (+) Positive

Red (-)
(-) Negative
Thermocouple Terminal Block
The DeltaV Thermocouple/mV card supports up to eight Thermocouples or mV inputs.
Thermocouples consist of two dissimilar metals twisted together which generate a millivolt
signal with respect to temperature.
The Thermocouple terminal block contains sensors for cold junction compensation. An inherent
Thermocouple is created at the screw terminals where the wires are connected. The screw
terminals are also dissimilar metals that create a milli-volt signal (i.e., cold junction).
Cold junction compensation counters the milli-volt signal generated at the terminal block by
sensing temperature at the terminal block with an internal sensor in the terminal block.
Note: When the Thermocouple card is plugged into a Thermocouple terminal block the card
functions as a Thermocouple card. When the Thermocouple card is plugged into a standard I/O
terminal block it functions as a mV card.
 Thermocouple
This requires you to perform the following tasks:
Step 1. Install the Thermocouple card and terminal block.
Step 2. Wire the Thermocouple.
Step 3. Configure the Thermocouple card.
Step 4. Configure the Thermocouple channel.
Step 5. Configure a control module to show room temperature.
 Configure Thermocouple
Step 1. Install your Thermocouple card and terminal block
in slot 6.
Step 2. Connect the type T Thermocouple to channel 1 as
shown.

Blue (+)

Red (­)

Note: If you do not have a Thermocouple available you can simply short screw terminals 1and 2.
Proceed with the configuration on the following pages as if you had a thermocouple and you will
be reading the temperature at the terminal block sensed by the cold junction compensation.
 Configure Thermocouple
Step 3. Configure a new Thermocouple card. Select
Card class: Analog Input Cards, Card type 8
Channel, Thermocouple and Slot position 6 as
shown.
Alternately, you may autosense the card if it is
already plugged into the carrier.
Configure Thermocouple
Step 4. Select the Properties for Channel 1. Define the following key items:
a. Enable the channel.
b. Select the appropriate Channel Type. The example above assumes a
Type T Copper/Constantan (Copper-Nickel) Thermocouple.
c. Name the channel with the Device Tag (DST) TC1.
 Configure Thermocouple
Step 8. Verify CJT_CHAN is set to Local Compensation, which is the default. This will
provide cold junction compensation for the entire card by using the internal sensor in the
terminal block. The configuration person could change this to any of the 8 channels. Then the
card would use the value on that channel as the temperature for cold junction compensation.
Module RMTEMP-201
Step 1. Create a new module as shown above from the Library using the
Monitoring/ANALOG module template. The following pages take you through the AI1 block
and modify the necessary parameters to properly read the temperature from the
Thermocouple.
Module RMTEMP-201
Step 2. Set IO_IN Device Tag to TC1.
Step 3. Set IO_IN Parameter to FIELD_VAL to read the temperature in degrees.
If IO_IN is set to FIELD_VAL_PCT, the output will only show the value in percent.
Module RMTEMP-201
Step 4. Set L_Type to Direct because the transducer, or Thermocouple, in this case has units
that directly relate to the OUT value that will be displayed; -454 to 752° F.
 Module RMTEMP-201
Step 5. Set the OUT_SCALE Engineering Units to °C or °F; your preference.
It isn’t necessary to enter 0% or 100% scale as the system will automatically scale the output
based on the sensor selected on the channel properties, see the result on the next page.
 Module RMTEMP-201
Step 6. Complete the configuration as follows:
a) Assign to your controller.
b) Save the module as RMTEMP-201.
c) Download the module.
d) Download the Thermocouple card.
 Module RMTEMP-201
Step 7. View the module in the On-line view. As shown above left, while in edit mode the
0% and 100% scale is not defined. Once downloaded the On-Line view shows both
OUT_SCALE and XD_SCALE are automatically set.
Alternative Configuration
The AI block was configured using L_TYPE as Direct. This only requires selecting the units
under OUT_SCALE. If L_TYPE were set to Indirect the configuration person would have
additional data entry as shown by the .
L_TYPE = Direct L_TYPE = Indirect
XD_SCALE XD_SCALE
100% = * 100% = *
0% = * 0% = *
Units = * Units = °F 
OUT_SCALE OUT_SCALE
100% = * 100% = 752 
0% = * 0% = -454 
Units = °F Units = °F
*Automatically filled-in based on channel configuration.
Alternative Configuration
The AI block was configured using L_TYPE as Direct. This only requires selecting the units
under OUT_SCALE. If L_TYPE were set to Indirect the configuration person would have
additional data entry as shown by the .
L_TYPE = Direct L_TYPE = Indirect
XD_SCALE XD_SCALE
100% = * 100% = *
0% = * 0% = *
Units = * Units = °F 
OUT_SCALE OUT_SCALE
100% = * 100% = 752 
0% = * 0% = -454 
Units = °F Units = °F
*Automatically filled-in based on channel configuration.