configuration abb 2010 vietnam - fieldbus · opc server ethernet tcp/ip iec 61158-2 engineer...

1Vietnam FF Seminar

18 Mar 2010

Fieldbus Configuration

Developed by: Jack van der Horst (ABB Singapore)

• Presented by: • Stephen Djong (ABB Singapore)

2Vietnam FF Seminar

18 Mar 2010

Contents

• Big pictureoverview

• Block modelControl in the Field, control in the Host

• ConfigurationElectronic Device Description, Capability Files

• Diagnosis

This session covers:

3Vietnam FF Seminar

18 Mar 2010

Overview

• Following IEEE 820.3 standard (Fast Ethernet)

• Up to 100 MBit Fast Ethernet

• Utilization of Ethernet hardware / software / wiring standards

• Star topology

• Half/full Duplex operation

• Cyclic Redundancy Check (CRC)

• Device powering via the bus possible

• Intrinsic safety option: FISCO / Entity model

• Digital data transmission with 31.25 kBit/s

• Deterministic asynchronous communication

HSE (High Speed Ethernet) H1 (MBP)

Big PictureBlock conceptConfigurationDiagnosis

4Vietnam FF Seminar

18 Mar 2010

FOUNDATION Fieldbus network


Ethernet / IEEE 802 / FOFOUNDATION Fieldbus HSE

OPCServer

Ethernet TCP/IP

IEC 61158-2

EngineerEngineer

FOUNDATION Fieldbus H1

LinkingDevice

OperateOperate

EngineerEngineer

ControlControl

FieldFieldPS

5Vietnam FF Seminar

18 Mar 2010

FOUNDATION Fieldbus communication



OPCServer

Ethernet TCP/IP

EngineerEngineer

LinkingDevice

OperateOperate

EngineerEngineer

ControlControl

FieldField FOUNDATION Fieldbus H1 – Link A

FOUNDATION Fieldbus H1 – Link B

PS

Application implemented and executed in the controller (control in the host) or in the field (control in the field).Communication scheduled by LAS. Scheduled execution of Function Blocks not just polling.

6Vietnam FF Seminar

18 Mar 2010

Objectives / Big Picture

HSE

H1

T RF F

Block Model


7Vietnam FF Seminar

18 Mar 2010

Blocks

R T

F

Blocks are software componentswithin the device

Object Dictionarystores parameterinformation forBlocks

Profiles describe Function Block types

Standard Transducer and Function Blocks specified

Blocks described within Capabilities File (*.cff)

Block parameters can be accessed by using Fieldbus Builder FF

Function Block application can be implemented by using Fieldbus Builder FF


8Vietnam FF Seminar

18 Mar 2010

Block concept

physical characteristics of the FF device

Hosts can read all Information of the Resource Block

Every Device must have one Resource Block.

Manufacturer IDDevice TypeDD RevisionDevice RevisionState

Acyclic access – client / server

Resource Blocks

TransducerBlocks

links the physical Sensor / Actuator world to the information world

Can be executed in higher frequency than Function Blocks

Input & Outputs addressed by channels

Temperature with calibrationFlow with calibrationBasic positioner valveAdvanced positionervalve

Acyclic access – client / server

FunctionBlocks

Encapsulates basic automation functions

Can communicate with other Function Blocks

Execution is explicitly scheduledby System Management (deterministic)

independent from host system (control in the field)

Cyclic & Acyclic access / execution –publisher/subscriber


9Vietnam FF Seminar

18 Mar 2010

Block concept


Resource Block

PressureT- Block AI F-BlockPressure

Sensor

FOU

ND

ATIO

N F

ield

bus

H1

V V V V V‘ V‘ V‘ V‘ SV V V V S

Parameter Read / Writeacyclic

TemperatureT-Block AI F-BlockTemp.

SensorV V V V V V V V V‘ V‘ V‘ V‘ SS

Data Exchange of process valuecyclic

Device: Device can have one Resource Block only.Sensor: Each sensor has one Transducer BlockFunction: Device may have N Function Blocks implemented

10Vietnam FF Seminar

18 Mar 2010

Function Block Profiles

World of Function Blocks

Standard Function Blocksminimal set of parameters definded in Function Block

specificationsProfile Revision = 0x0001

Enhanced Function Blocksminimal set of parameters

+additional parameters

Profile revision > 0x0001

Custom Function Blockscontains manufacturer

specific parameters onlyProfile revision > 0x8000

100%Interchangeable

Limited Interchangeability

Interchangeabilitynot possible

Profile Revision ofBlock Profile

within capabilities file (*.cff)

AI = 0x0101AO = 0x0102PID = 0x0108



18 Mar 2010

Block combinations

AI DI

AO DO

ML

AOInput

OutputManualControl

AI

PID

AO

AI

DIFeedforward

Control

AI

PID

AOCascadeControl

AI

PID

AI

PID

AORatio

Control

AI

RA



18 Mar 2010

Function Block applications

The single basic automation functions of Function Blockswithin one device or different devices can be linked together. Result -> Function Block Application

Function Block application, built up using Fieldbus Builder FF



18 Mar 2010

„Control in the Host“

HSELinking Device

FF HSE

FF H1 Links

ControllerHSE interface

Ethernet

• Use of Function Blocks out of Controller Function Block Libraries (PID, …)

• Calculation and logic within controller

• Application resident in controller

• Transmission of values from field to controller and controller to the field



18 Mar 2010

„Control in the Field“

HSELinking Device

FF HSE

FF H1 Links

ControllerHSE interface

Ethernet

• Use of Function Blocks out of the device(s)

• Calculation within device(s)

• Application resident in device(s)

• Transmission of values from device to device (Block to Block)



18 Mar 2010

Communication Configuration

• Capability Files

– Structure like Windows initialization files (.ini)

– Can be used for offline configuration

– Based on Common File Format Specification (CFF)

– Can Provide example values

– Number of Function Blocks, Function Block Timing, Virtual Field Devices, …



18 Mar 2010

.CFF File Example

[File Header]Description = "Common Format File for ABB TZIDC-x20 Basic Diagnostics"FileType = CapabilitiesFileFileDate = 2003,10,01CffVersion = 1,5

BitmapDevice = "TZIDCico.bmp"BitmapFault = "TZIDCerr.bmp"BitmapDetail = "TZIDC.bmp"

// Device Header

[Device Header]DeviceName = "TZIDC-x20"CommGroup = 3CommClass = Class31+Class32CommSubClass = Class3LinkMaster+Class3Publisher+Class3SubscriberDeviceClass = LINKMASTER

// Device VFD

[Device VFD 1] // Management VFDVendorName = "ABB"ModelName = "MIB"Revision = "2.01"VersionOD = 0x01ProfileNumber = 0x4d47

Key Value

Key Name



18 Mar 2010

Communication configuration


OperateOperate EngineerEngineer


LinkingDevice

OPCServer

Ethernet TCP/IP

IEC 61158-2FOUNDATION Fieldbus H1

2. Import CF Files

3. Set FF addresses

1. Install devices

4. Match ID devices


18 Mar 2010

Diagnosis


BlockMode

Value & Status (4+1 Byte)

via Publisher / Subscriber

Alarm or Event (Alerts) + Timestampnotification

via Report Distribution

Block Modes Status of variables / process values

Alarms & Events notification

Alert list

Alarms & Events list


18 Mar 2010

Diagnosis - Status


Status of Variables / Process Values is represented by1 octet (1 Byte)

Status validates the data

Quality Substatus Limits

21 2023 2225 2427 26

(0) Bad: e.g. sensor failure, out of service

(64)Uncertain: e.g. engineering unit violation

(128)Good: e.g. needed for writing a valid setpoint

(192)Limits: e.g. low limited, high limited

Examples:(15) Out of Service(7) Sensor failure(8) Output failure


18 Mar 2010

Block Mode


Out of Service

Manual

Initialize Manual

Automatic

Cascade

Remote Cascade

Remote Out

Local Override

Parameter

Block must be in Out of Service to changeParameter settings

Modes

Target Mode -> set by operatorActual mode -> during execution of BlockPermitted -> Modes limited by BlockNormal -> Desired operating mode of Block

Service

Block needs Target and Actual Mode= Automatic to be / get in service

Actual Mode

Depends on the health of the values and the parameters and the resource. Mode propagates and influences Mode of successionalBlocks


18 Mar 2010

Details

http://www.fieldbus.org


18 Mar 2010

Summary

– HSE refers to FF protocol on Ethernet– Application can be implemented in the Host or Field– Data Communication is scheduled by LAS– Blocks are software components within the device– A device contains 3 main blocks, i.e. Resource Blocks,

Transducer Blocks and Function Blocks– Multiple Function Blocks can be linked together using FF

Builder– Capability Files (CFF) are required to make offline & online

configuration– FF Communication Configuration Steps:

Install devices, Import CF Files, Set FF Addresses and MatchID Devices

– FF Diagnosis Consists of Block Modes, Alarm & Events and Variables Status


18 Mar 2010

Summary

OperateOperate

ControllerController

Ethernet TCP/IP

T

RFO

R RTTTTTT

HSEEngineer

FieldBarrier

H1-devicesBus-powered

Power Hub

H1 (MBP)

OPCServer

Linking deviceLD800HSE

PS


18 Mar 2010

QUESTIONS?QUESTIONS?QUESTIONS?

configuration abb 2010 vietnam - fieldbus · opc server ethernet tcp/ip iec 61158-2 engineer...

Documents