foundation fieldbus overview

Taking Advantage of

Foundation FieldbusDevice Functionality

Larry WolfeDirector, Technology Deployment

REM Services, Inc.Charlotte, NC

November 17, 2009 Slide 22

Abstract

Taking Advantage of Foundation Fieldbus DeviceFunctionality

Foundation Fieldbus systems have been deployed in many facilitiessince their introduction in the late 1990’s. System and devicefunctionalities have improved in many ways since. This presentationwill provide an overview of Foundation Fieldbus functionality, contrastthe use of 4-20mA devices versus fieldbus devices in monitoring andcontrol strategies, and highlight what users across the organizationneed to know about the technology to gain the most benefit.

A control system and field devices utilizing current Foundation Fieldbusfunctionality will used throughout the presentation.


Larry Wolfe - Biography

Larry Wolfe is Director, Technology Deployment for REM Services,Inc. in Charlotte, North Carolina. Larry earned a BS in AerospaceEngineering in 1968 and an MS in Mechanical Engineering in 1974from the University of Oklahoma. Between his times at University heserved four years in the Air Force. He came to North Carolina aftergraduate school to Fiber Industries, Inc. in Salisbury, NC. After 10 +years with that company, he took a job with the Robert E. MasonCompany in Charlotte in 1985 and has worked for the Robert E. Masonfamily of companies since.

Larry has worked with the integration of Process Control systems andfield devices for most of his career. He has worked with FieldbusFoundation host and device products from Emerson since theirintroduction. He has worked with customers to implement the benefitsthe systems provide and has helped to familiarize users with systemand device capabilities.


Quick History of FF

• DCS Systems introduction in 1970’s• ISA – SP50 Committee efforts• Interoperability Systems Project• WorldFIP North America• Merging of ISP and WorldFIP NA to form


What is Foundation Fieldbus?

• H1 is an all-digital, serial, two-way, deterministic,cyclic and acyclic communication systeminterconnecting “field” equipment such assensors, actuators and I/O

• The Physical Layer is OSI layer 1• The Data Link Layer (DLL) is OSI layer 2• The Fieldbus Message Specification (FMS) is

OSI layer 7• The Communication Stack is comprised of

layers 2 and 7 in the OSI model


Physical Layer

• Foundation Fieldbus uses a two or threewire shielded cable (several classes fordifferent applications)

• Terminated at both ends• Maximum segment length 1900m• Segment Design Tools available• Connectivity and diagnostics products and

tools available from multiple vendors


OSI vs Fieldbus Model

* The user application is not defined by the OSI Model

OSI Model*

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer

Data Link Layer

Physical Layer

Application Layer

Fieldbus AccessSublayer

Physical Layer

Communication“Stack”

UserApplication

UserApplication

Fieldbus Model

6

7

5

4

3

2

1


Device Descriptions

• The “drivers” for Foundation FieldbusDevices

• Typically two DD files and one capabilitiesfile

• Used by the host/control system tounderstand functions available in device

• DD’s are available on Foundation Fieldbuswebsite and vendor websites


Foundation Fieldbus Blocks

• The Fieldbus Foundation has defined astandard User Application Layer based on“Blocks.”

• There are three standard block types inthe FF User Application Layer

• Resource Block• Transducer Block• Function Block


Resource Block

• The Resource Block describescharacteristics of the fieldbus device suchas the device name, manufacturer, andserial number

• There is only one Resource Block in adevice


Transducer Block

• The Transducer Blocks are used toconfigure devices

• Transducer Blocks decouple FunctionBlocks from the local input/outputfunctions required to read sensors andcommand output hardware

• They can contain information such ascalibration date and sensor type


Function Blocks

• Function Blocks (FB) provide the controlsystem behavior

• The input and output parameters ofFunction Blocks can be linked over thefieldbus

• The execution of each Function Blockused is precisely scheduled


Partial Function Block List

RARatio

PIDProportional/Integral/Derivative

PDProportional/Derivative

MLManual Loader

DODiscrete Output

DIDiscrete Input

CSControl Selector

BGBias/Gain

AOAnalog Output

AIAnalog Input

SymbolFunction Block Name

AALAnalog Alarm

TMRTimer

ARArithmetic

ISInput Selector

SPGSetpoint Ramp Generator

ITIntegrator (Totalizer)

DTDeadtime

LLLead Lag

SCSignal Characterizer

OSOutput Splitter

DCDevice Control



Still More Function Blocks

MDOMultiple Discrete Output

MDIMultiple Discrete Input

MAOMultiple Analog Output

MAIMultiple Analog Input



Commissioning Devices

• Assign the device a name• Assign the device a permanent address

– (DeltaV calls this the Commissioned address)

• Download the information to the deviceand the host


Downloading Devices

• Loads information into host accessibleparameters of the device – typically innon-volatile memory

• Assigns permanent Fieldbus addressesand names to devices and device blocks

• May require download of “shadow” blocksif host uses this functionality


Segment Communications

• VCR• DD / DDL• Basic Device• Link Master• Compel Communications• Publish PV OUT• Subscribe• Token• Probe Node Message


DeltaV Macrocycle


Segment Design Software

• Pepperl+Fuchs Segment Design– http://www.segmentchecker.com/

• MTL Fieldbus segment calculator v1.5.4– http://www.mtl-inst.com/products/C397


Handheld Tools

• Segment Diagnostic Tools– MTL Fieldbus Monitor, FBT-6– MTL FBT-3 Fieldbus monitor– MTL FBT-4 Fieldbus Power & Signal Probe– MTL Fieldbus Wiring Validator, FBT-5

• http://www.mtl-inst.com/product/test_equipment/

• Device Configuration/Diagnostic Tools– Emerson 375 / 475 Field Communicators

HART and Foundation Fieldbus• http://www2.emersonprocess.com/en-us/brands/fieldcommunicator/Pages/fieldcommunicators.aspx


Foundation Fieldbus DeviceConfiguration / Diagnostic Software

• Emerson AMS Intelligent Device Manager– http://www2.emersonprocess.com/en-

US/brands/amssuite/amsdevicemanager/Pages/AMSDeviceManager.aspx

• National Instruments– http://sine.ni.com/nips/cds/view/p/lang/en/nid/10240


References

• Fieldbus Foundation– http://www.fieldbus.org/

• Emerson Process Managementhttp://www2.emersonprocess.com/en-US/plantweb/whatisplantweb/connecting/Pages/FOUNDATION_Fieldbus.aspx


References

• Pepperl+Fuchs– http://www.am.pepperl-fuchs.com/products/productfamily.jsp?division=PA&productfamily_id=1244

• MTL– http://www.mtl-inst.com/products/C77/


Resources for learninghttp://www2.emersonprocess.com/en-US/plantweb/whatisplantweb/connecting/Pages/FOUNDATION_Fieldbus.aspx


Resources for learning cont.

• http://www2.emersonprocess.com/en-US/plantweb/whatisplantweb/connecting/Pages/FOUNDATION_Fieldbus.aspx



• http://plantweb.emersonprocess.com/university/default.asp



• http://plantweb.emersonprocess.com/university/engSch_Fieldbus_XML.asp


Questions?

Questions? / Comments!


Foundation Fieldbus Demo

• Foundation Fieldbus Demonstration– Host DeltaV V10.3 Scalable Process System– AMS Intelligent Device Manager– Devices

• Rosemount– 3051S DPT 848T TT 644 TT– 3144 TT 752 Indicator

• Fisher Controls International– DVC6000F

• FieldQ– QC34 FF Controller


Thank You Very Much!!

Thank you very muchfor your hospitality!!!

foundation fieldbus overview

Documents