Foundation Field bus

Applications in Intools
 Foundation Field bus in SPI Forward

 This presentation suggests a sequence of

activities for Foundation Field bus system
design using SmartPlant Instrumentation.
 Note that you can carry out some of the
procedures in a different order, depending
on your preferences and project
requirements.
 Foundation Field bus in SPI Forward

 FFB - The open, nonproprietary Foundation architecture provides a communications

protocol for control and instrumentation systems in which each device has its' own
"intelligence" and communicates via an all-digital, serial, two-way communications
system.
 H1- Foundation H1 technology is intended primarily for process control, field-level
interface and device integration. The technology interconnects devices such as
transmitters and actuators on a field network. H1 is designed to operate on existing
twisted pair instrument cabling with power and signal on the same wire.
 Function Block Model - A unique characteristic of the Foundation architecture
ensuring device interoperability is its use of a fully specified, standard User Layer
based on "Blocks" and Device Descriptions (DDs). The User Layer defines a Function
Block Application Process (FBAP) using Resource Blocks, Function Blocks,
Transducer Blocks, System Management, Network Management and DD technology.
 EDDL - Electronic Device Description Language (EDDL) is a programming language
used to create Device Descriptions (DDs) to describe the attributes of field devices in
an Operating System (OS) and Human Machine Interface (HMI)-neutral environment.
 SIF - The Field bus Foundation's Safety Instrumented Systems (SIS) program is
delivering the benefits of open, interoperable Field bus technology to the industrial
safety market.
 Foundation H1 Protocol

 Foundation H1 Technology devices comprise a function block application, act

as a publisher and subscriber of process variables, transmit alarms and trends,
and provide server functionality for host access and management functions.
Devices can act as a scheduler for regulating communication on a Field bus
segment. They are also used for bus interfaces in process control systems or in
linking devices.
 Field bus advantages:
 Reduce the number of wires and marshaling panels

 Reduce the number of I/O

 Reduce the size of the equipment rooms

 Allow remote configuration of devices

 Increased quantity and accuracy of measurements

 Increased flexibility of instrument systems

 Increased reliability due to self diagnostics

 Foundation Function Block Model
 Blocks enable Field bus device functionality
 Flexible Function Blocks enhance control in the field
 Resource Blocks define parameters that pertain to the entire application
process (e.g., manufacturing ID, device type, etc.).
 Function Blocks encapsulate control functions (e.g., PID controller, analog
input, etc.)
 Transducer Blocks offer an interface to sensors such as temperature,
pressure and flow, and actuators for valves.
 Electronic Device Description Language

 Electronic Device Description Language (EDDL)

 EDDL is a universal, method of accessing diagnostic, real-time and asset

management information contained in more than 20 million compliant field
instruments from a host of manufacturers, and to provide optimum data and
device interoperability.

 EDDL is a text-based description of the variables contained in field devices,

such as flow, pressure, drive speed, ambient temperature, high and low
limits, calibration settings, and so on. The description defines each variable,
and describes the way to access it.

 With EDDL technology, a user can calibrate instruments, diagnose problems,

provide data for user interface displays, identify process alarms and obtain
information needed for high-level software, such as MES, UI/SCADA, plant
historians, asset management and DCS systems.
 Field bus Segment Network

 FFD - a digital, two-way multi-drop communication network linking intelligent

instrument measurement and control devices, and automation monitoring, display or
programming systems

Field bus Network X

Terminator Terminator
+ Signal
Control or
Isolation
Circuit
Monitoring
- Device
Field bus X X
Power Supply Field Devices
 Foundation Field bus Wiring Model

 Foundation Field bus Segment

 H1 Card or Segment Coupler I/O to the Field bus Host

 Field bus Power Supply, Power Conditioner or Diagnostics

 Field bus or Instrument Homerun Segment or Trunk Cable

 Bricks or Mega-blocks to gather the spur wiring to the

Devices
 Field bus Devices with Interface and Function Blocks

 Internal or external Terminators at both ends of a Segment

 SPI Field bus Sequence of Activities

 Define the Segment-Wide Parameters for the project

 Define Foundation Field bus instrument type profiles
 Add a new browser view for Field bus Manager
 Create user-defined function blocks (if required)
 Associate function blocks with instrument types
 Create Foundation Field bus instruments in Index
 Generate Field bus Device Specifications
 Associate unique Function Blocks with Field bus Tags
 Create Field bus Segments in the Field bus Manager
 Associate Field bus Instruments with Segments
 Design your wiring and termination equipment
 Add your Field bus home-run cables and spurs
 Make required cable connections and associations
 Effect the Field bus I/O H1 assignments
 Generate Field bus validation reports (if required)
 Generate segment diagrams and wiring reports
 SPI Segment-Wide Parameters

 Define the Segment-Wide Parameters for the project

 From the Wiring Module / Segment Manager / Action / Segment-Wide Parameter
Profiles:
 Define General and Cable Length Properties as defined by Field bus System
manufacturer

Manufacture will provide Parameters

These Parameters will be used later
when the user Generates Field bus
validation reports
 Segment-Wide Parameters - Alternative

 An Alternative method to defining the Segment-Wide Parameters:

 Create a Conservative Design Guidance for Segment Loading and
lengths that is approved by the client for design of the Foundation Field
bus Segments:

Recommended Segment Parameters Conservative Design Guidance

16 Maximum Devices per segment 8 Maximum Devices per segment
12 Function Blocks per segment 10 Function Blocks per segment
1900m Maximum Segment Length 1000m Maximum Segment Length
120m Maximum Spur Length 60m Maximum Spur Length

The Design Guidance will be used as the basis for the Field bus Segment
design so Field bus validation reports can be run on only the worst case or
most extreme Segments to verify compliance with the system rules
Make the Field bus Segment Design Guidance part of the project Smart Plant
Instrumentation Implementation Specification
 Field bus Instrument Types

 Define Foundation Field bus instrument type profiles

Note: The I/O Type must be “Field busFF”

Note: Create Field bus Wiring Reference

Items with proper wire colors and sequence
prior to defining Field bus Instrument Types

Note: Do not check the Control

System or Automatic CS Tag
Checkbox

Note: Each Field bus Device

must have a Function Block
 Associate Function Blocks

 Associate Function Blocks with Instrument Types

 Any additional Function Blocks that are common across an Instrument Type
may be associated (e.g. Control Valves that have a controller function in the
field may have a DC (Device Controller) assigned in addition to the AO)
 If no field control is being configured - skip this step
 Field bus Browser Views

 In the Browser Manager - add a new Field bus Tag Number List browser view for
the Field bus Segment Manager
 Add Field bus Instruments to Index

 Create Foundation Field bus instruments in SPI Index

 Do not assign Tag Class until they are needed

 Do check the Instrument Type profiles before adding

 Do make sure the I/O Type is “Field busFF”

 Field bus Tags may be created just like Conventional Tags

 User Defined Function Blocks

 Create user-defined function blocks (If Required)

 From the Index Module / Tables / Function Blocks… Menu
 Users may add any additional Function Blocks required for the project
 To allow editing of the Multiple and Execution Time, users must enable the
check box
 Associate Function Blocks

 To Associate or Dissociate Function Blocks on a Tag:

 Expand the Instruments folder in the Domain Explorer
 Select the Properties of the Tag you wish to modify
 Click the Field bus tab and Associate or Dissociate Field bus Function Blocks as
required
 On most projects – Simple AI and AO Function Blocks are all that are required:
 Additional Function Blocks may be configured from the DCS
 Field bus Device Specifications
 A Field bus Spec Page may be
added to any standard spec
form to create a new Field bus
Specification
 Use a Field bus page only
if instruments are being
purchased pre-configured
or pre-programmed

 Note: A Standard Instrument

Spec may be used for Field
bus instruments by simply
defining the Signal Type as
“Field bus”
 Field bus Segments

 The next steps will create Field bus segments, associate the appropriate instruments
with their respective segments, and create the necessary virtual tags
 Create Field bus Segments in the Domain Explorer / Field bus Segments Folder –
Right Click / New / Field bus Segments… - Enter a unique Segment number, select
Segment Profile and Check if Intrinsically Safe.
 Associate Tags to Segments

 In the Wiring Module / Field bus Segment Manager select the Field bus Tag you wish to
associate
 Drag the Tag to the required Segment in the Field bus Segments folder of the Domain
Explorer
 To Dissociate a Tag from a Segment - Right-click an instrument in the Field bus
Segments folder of the Domain Explorer, click Actions > Dissociate Item (Do NOT
Delete Tag)
 Enable Virtual Field Devices (V-2007)

 In the Field bus Segments folder of the Domain Explorer – Expand a Field bus Tag to
see the Function Blocks
 Right-click the required function block under the highlighted tag number and click
Actions > Enable
 To assign a Tag Number to a VFD you must Renumber in the Tag Number Properties
dialog Box
 Create Virtual Field Devices (V-7)

 In the Segment Manager

 Create segments per naming convention

 Drag and drop Field bus tags from browser list to segment

 Open segment to reveal Tags

 Open tag to reveal function blocks

 Right click on function block & create new virtual tag

 Field bus Wiring Equipment

 Field bus Device Panels:

 Make sure that the Field bus device profiles are correct.
 Check Field bus I/O type
 Check associated function blocks
 Uncheck Control System tag creation.
 Enter the tags creating the device panels & cables
 Use Conventional cable pairs or Field bus Cables
Field bus Brick Wiring (Physical)

 Field bus Mega-block or Brick:

 Note the +,S,- on the left and -, S,
+ on the Right side of the brick
 If you create the Brick with
physical representation the
resulting wiring will be difficult
with standard Connect Types
Field bus Brick Wiring (Diagrammatic)

 Diagrammatic Solution
 Configure Field bus Bricks
diagrammatically for ease of wiring
 Create in Junction Box folder in
Reference Explorer
 Note the Left to Right Wiring
Connections and segment diagram
 Create a Power Supply / Conditioner

 Field bus Power Supply, Power Conditioner

or Diagnostics
 Created as a Terminal Strip with Apparatus
Channels
 Each Segment will pass through a Power
Supply Channel before connecting to the Field
bus H1 card
 Additional Apparatus may be connected at the
Power Supply
 Power Conditioners
 Segment Diagnostics
 Critical application Isolators
 Calibration Interface connections
 Create a Field bus I/O Card

 In the Reference Explorer select the DCS Panel and right click New / Wiring
Equipment – select I/O Card under Category and name the card
 Open the Wiring Equipment Properties select Apply naming convention or Enter a
Name
 In the Control Systems Tab – Select Field busFF as the I/O Type

 Add Terminal Strips or Channels and

Terminals as required
 The Field bus I/O card is now ready to drag
and drop into a DCS rack as needed
 Create the Field bus DCS Racks and Slots

 Create DCS cabinet with Racks, Slots, I/O

Cards & I/O Terminations for Field bus
segments
 Include one power conditioner per 8
segments.
 Place defaults in the Reference explorer
for the power conditioner and the
terminations
 Note that the defaults are I/O
terminations not I/O cards.
 Do not forget to add the Terminator in the
Strip that you are connecting to a
segment
 Field bus Connection Types

 Field bus Cable Connection Types

 Users must manually manipulate the conductors at each connection to facilitate
the different connection methods and polarity
 Note wire colors and polarity at each terminal

Conventional Field bus

Connection Types Connection Types

+- +-S +S- +-S +S-

 Create Field bus Home-run Cables

 From the Domain Explorer Right-click the Cables folder and click New > Home-run
Cable
 In the Cable Configuration dialog box:
 Select Field bus cable from the Cable Configuration List
 or
 Define a new Cable Configuration
 In the Cable Properties dialog box select Field bus home-run from the Cable class list
 Spur cables may or may not be the same as conventional Tags (Check required color
codes)
 Field bus Field Wiring

 Wiring Field bus instruments:

 Create junction box with Field bus Brick or Mega-block

 Name Brick per Field bus naming convention

 Use default from the reference explorer or duplicate

 Open Connection and Drag and Drop instruments to brick.

 Note the connection order (+, s, -)

 Create a Field bus homerun cable

 Name cable per Field bus naming convention

 Use default from the reference explorer or duplicate

 Field bus Wiring

 Wiring Field bus instruments (continued):

 Connect Field bus Homerun Cable (1 pair of 2 pair) at brick
 Note the connection order (+, s, -)
 Connect Field bus Homerun Cable to power conditioner
 Note the connection order (+, s, -)
 Right click on Cable and associate cable to segment
 Field bus Wiring

 Wiring Field bus instruments (continued):

 Create a Field bus DCS Jumper (single pair) cable

 Per Field bus Segment naming convention

 Use default from the reference explorer or duplicate

 Connect Field bus DCS Jumper Cable (1 pair) at Power Conditioner

 Note the connection order (-, s, +)

 Connect Field bus DCS Jumper Cable to DCS

 Note the connection order (+, -)

 Field bus Wiring

 Wiring Field bus instruments (continued):

 After connecting the Field bus DCS Jumper (single pair) to power conditioner
and DCS termination.
 Associate Field bus DCS Jumper cable to segment.

 Note: Field bus segments can be loaded and unloaded into I/O assignments just
like conventional CS tags so you can load the I/O prior to wiring them if needed
 Field bus Multi-input Devices

 Field bus 848T, 848L and 9331-T1 instruments:

 Emerson Rosemount 848T – 8 input Field bus Temperature transmitter

 Up to 128 Temperature measurement signals per Segment – 8 inputs per

848T
 Emerson Rosemount 848L – Logic Discrete Input or Output with Boolean
Function Blocks
 Up to 128 Inputs per Segment – 8 per 848L

 Up to 64 Outputs per Segment – 4 per 848L

 MTL-Relcom 9331-T1 8-channel Field bus temperature multiplexer

 Field bus 848T Wiring

 Wiring Field bus Multi-Input instruments:

 Make sure that the profiles are correct.

 Check Field bus I/O type

 Check associated function blocks

 Check NO to Control System tag creation.

 Create RTD's and Thermocouples using their regular profiles

 Create Discrete Devices using conventional profiles

 Field bus 848T Wiring

 Create an 848T Temperature Transmitter:

 Use the “Temp Transmitter, multi-channel (FF)“ Instrument Type

 This will build a device with 8 inputs and one Field bus output

 It will also have 8 function blocks assigned, one for each TE)

 Create a Junction Box and drag the TT device panel into the box
 See Junction Box naming convention
 Field bus 848T Wiring

 In the Segment Manager

 Create segments per naming convention

 Drag and drop Field bus tags from browser list to segment

 Open segment to reveal Tags

 Open tag to reveal function blocks

 Right click on function block & create new virtual tag

 Field bus 848T Wiring

 From the Segment Explorer Manager select the 848T Temperature Transmitter
 Disassociate the 848T tag from the segment
 It will be re-assigned after the segment is loaded into the I/O

 Create a One or Two Brick Field bus Junction Box

 Per Field bus Junction Box naming convention

 Defaults exists in the reference explorer

 Field bus 848T Wiring

 From the Connection Screen:

 Connect each Temperature Element to the 848T Temperature Transmitter

 Go to the each Temperature Element cable properties

 Change the Cable Class to “Field bus Homerun”

 Right click on Cable and associate cable to the segment

 This association will allow the TE's to show up on the segment drawing
 Field bus 848T Wiring

 Create DCS cabinet with Racks,

Slots, I/O Cards & I/O Terminations
for Field bus segments
 Include one power conditioner
per 8 segments.
 Defaults exist in the reference
explorer for the power
conditioner and the terminations
 Note that the defaults are I/O
terminations not I/O cards.
 Field bus 848T Wiring

 Wire the 848T Temperature Transmitter to the Field bus brick and associate cable
to the segment
 Connect Field bus Homerun Cable (1 pair of 2 pair) at brick
 Note the connection order (+, s, -)

 Connect Field bus Homerun Cable to power conditioner

 Note the connection order (+, s, -)

 Right click on Cable and associate cable to segment

 Field bus 848T Wiring

 Create a Field bus DCS Jumper (single pair) cable

 Per Field bus Segment naming convention

 Use default from the reference explorer or duplicate

 Connect Field bus DCS Jumper Cable (1 pair) at Power Conditioner

 Note the connection order (-, s, +)

 Connect Field bus DCS Jumper Cable to DCS

 Note the connection order (+, -)
 Field bus 848T Wiring

 Return to the segment manager and drag the 848T tag to the correct segment
 (you may see an error message "unable to retrieve cross wiring")

 After connecting the Field bus DCS Jumper (single pair) to power conditioner
and DCS termination.
 Associate Field bus DCS Jumper cable to segment.

 Note: Field bus segments can be loaded and unloaded into I/O assignments just
like conventional CS tags so you can load the I/O prior to wiring them if needed
 Field bus Validation Reports
 Run Validation Report Only if
necessary
 Report basis is Segment-Wide
Parameter Profile Properties
 Single or Multiple Tag Validation
Reporting capabilities
 Enhanced Report generator
required
 Cable Type Properties must have
values for capacitance, capacitance
UOM, cable resistance, cable
resistance UOM, length UOM, and
maximum Field bus length
 The Tag Number dialog box must
have valid information under Field
bus Tag Number Properties
 SmartPlant Instrumentation
validation supports basic Field bus
networks consisting of a single
segment with no parallel branches
and no repeaters.
 Field bus Validation Reports

 Validation Report verifies the following:

 Field bus tags associated with a
segment but not wired
 Field bus tags that have wiring, but are
not connected to a segment
 There is a connection discontinuity
between the field and a DCS or an I/O
terminal strip
 The number of instruments in a
segment exceeds the maximum
specified
 The number of devices on a given spur
exceeds the segment-wide parameters
 A spur length is exceeds the maximum
 Total cable length exceeds the
maximum
 Less than two terminators in a segment.
 Actual voltage at instrument is below
the minimum operating voltage.
 Total segment current consumption
exceeds the maximum specified value.
 Total capacitance exceeds segment
maximum specified capacitance.
 Field bus Wiring Reports

 Field bus Wiring reports are the same as Conventional Wiring

 Field bus Segment Diagrams
 Create Enhanced Field bus Segment Diagrams
 Field bus Loop Diagrams

 Enhanced Field bus Loop Diagram

Field bus in Smart Plant Instrumentation