Fieldbus 简介

课程目的

Purpose the course……

1. Basic knowledge of Foundation Fieldbus

2. Operation in YOKOGAWA Builder
3. How to do FF loop check during SAT
4. Others (Trouble shooting)

2
1. Introduction
1. 1 What’s Fieldbus
Fieldbus is a digital, two-way, multidrop communication link among
intelligent measurement and control devices. This communication
method replaces the conventional standard communication, i.e., 4 to
20mA analog communication. The following eight types of definitions
are made in the IEC Fieldbus Communication Standard:
• Current IEC TS 61158
• FOUNDATION fieldbus
• FOUNDATION fieldbus High Speed Ethernet
• PROFIBUS
• Control Net
• P-Net
• Swift Net
• World FIP
• Interbus
• Profi Net
CENTUM CS 1000/CS 3000 support the FOUNDATION fieldbus and
PROFIBUS-DP communication standards.

3
1. Introduction
1.2 Features of Fieldbus
Fieldbus has the following features:
• Because multiple devices can be connected, and multivariables can
be transmitted on a single cable, thus reducing the number of cables,
wiring costs are reduced.
• A digital transmission protocol ensures accurate information
processing and hence strict quality control.
• Multiplex communications allow other information as well as PV and
MV to be transmitted from field devices.
• Communication between field devices allows truly distributed control.
• Interoperability enables devices from different manufacturers to be
combined.
• A broad choice of devices from any manufacturer permits flexible
system construction.
• Some adjustments and inspections of field devices can be performed
from the control room.

4
1. Introduction

A comparison between the conventional 4 to 20 mA analog 　

transmission, hybrid communication, and Field bus communication
protocols is shown below.

5
1.Introduction

1.3 Fieldbus Standard Specifications

Fieldbus Standard
Specifications

*1: Yokogawa has

developed dual-
redundant
configuration of
ALF111 Fieldbus
Communication
Module for FF-H1.

6
1.Introduction
Type of Fieldbus Cables and Transmissible Length

Yokogawa recommends the use of Type A.

Usage of Types B and D is restricted.
Yokogawa does not recommend the use of Type C

7
1.Introduction

1.4 Network Topology

The Fieldbus installation shall use the 'tree', 'spur', or 'combinatio
n' topology. The daisy chain topology (i.e., routing the trunk dire
ctly through each device) shall not be used. The topology selecte
d is usually driven by the physical device location in order to redu
ce installation costs, hence, in addition to P&ID’s, the instrument l
ocation plans should be available during segment design.

8
1.Introduction
1.4.1 Tree or Chicken Foot Topology
A tree topology is used when several related instrument
s are physically located close to each other. A Fieldbus
junction box is located close to the instruments with sp
urs extending from it to each instrument. An example o
f a tree topology is shown in the figure below.

To ALF111 Junction
JB Box
Card

Trunk Spur

Tree
Topology

Figure 1.4.1 – Tree or Chicken Foot Topology

9
1.Introduction

1.4.2 Spur or Bus Topology

A spur topology is used when several related instrumen
ts are located in the same direction from the Host contr
ol system but not necessarily close to each other. In th
is case, a trunk line is extended from the host control s
ystem to the farthest instrument and spurs are extende
d from it as it runs past each instrument.

To ALF111 JB JB JB JB
Card

Trunk

Spur
Bus or Spur
Topology

Figure 1.4.2 – Spur or Bus Topology

10
1.Introduction

1.4.3 Combination Spur-Tree Topology

A spur-tree topology is used when some combination of
the above instrument locations exists. Note that spurs
are permitted to extend only from trunk lines and not fr
om other spur lines.
To ALF111
Card JB JB

Trunk Spur

Spur

Combination
Topology

Figure 1.4.3 – Combination Spur-Tree Topology

11
1.Introduction
1.4.4 Daisy-Chain Topology
Daisy-Chain Topology is chained from device to device.
• Important to ensure that a device may be
disconnected without other devices also being
disconnected
• Daisy chain is NOT recommended.

Figure 1.4.4 – Daisy-Chain Topology

12
2. Engineering
This section describes the procedures followed in configuring the Fieldbus dev
ices in the Centum CS3000 system

2.1 Fieldbus Glossary of Terms

• ALF111: A communication module for FIO nodes of the CS 1000/3000 sup

porting connection to up to four H1 Fieldbus segments .

• Basic Device: A Basic Device is any device not having the capability to co
ntrol communications on an H1 Fieldbus segment.

• Device Description (DD): A Device Description (DD) provides an extend

ed description of each object in the Virtual Field Device (VFD), and includes in
formation needed for a control system or host to understand the meaning of
data in the VFD.

• H1 Repeater: An H1 Repeater is an active, bus-powered or non-bus-powe

red device used to extend the range over which signals can be correctly trans
mitted and received for a given medium. A maximum of four Repeaters and/
or active Couplers can be used between any two devices on an H1 Fieldbus n
etwork.

13
2. Engineering
Link Active Scheduler (LAS): A Link Active Scheduler (LAS) is a determi
nistic, centralized bus scheduler that maintains a list of transmission times f
or all data buffers in all devices that need to be cyclically transmitted. Only
one Link Master (LM) device on an H1 Fieldbus Link can be functioning as t
hat link's LAS.

Link Master (LM): A Link Master (LM) is any device containing Link Activ
e Scheduler (LAS) functionality that can control communications on an H1 F
ieldbus Link. There must be at least one LM on an H1 Link; one of those L
M devices will be elected to serve as LAS.

Physical Device Tag: An identifier used to identify a particular device fro

m all devices on a network. Unique physical device tags must be set for indi
vidual devices on a network without omission. The physical device tag must
be set for a device prior to connecting it to a Fieldbus; unless the physical d
evice tag is set, the node address cannot be set.

Schedules: Schedules define when Function Blocks (FBs) execute and wh

en data and status is published on the bus.

14
2. Engineering
Segment: A Segment is a section of an H1 Fieldbus that is terminated in
its characteristic impedance. Segments can be linked by Repeaters to for
m a longer H1 Fieldbus. Each Segment can include up to 32 H1 devices.

Spur: A Spur is an H1 branch line connecting to the Trunk that is a final c

ircuit. A Spur can vary in length from 1 m (3.28 ft.) to 120 m (394 ft.).

Terminator: A Terminator is an impedance-matching module used at or

near each end of a transmission line. Only two Terminators can be used o
n a single H1 segment.

Trunk: A Trunk is the main communication highway between devices on

an H1 Fieldbus network. The Trunk acts as a source of main supply to Sp
urs on the network.

15
2. Engineering
Difference between Offline initial Download, Offline Master
data Download, online Download, Upload

16
2. Engineering
2.2 System Builder

The following configuration tools are provided in the CS3000 system in the Fieldb
us system configuration.

• System View – This builder defines the basic structure of Field Control Stations
(FCS) and Input/Output Modules (IOM). I/O nodes and ALF111 cards are defined
in this builder.

• Fieldbus Builder – This builder defines detailed information related to a segmen

t, such as registration of Fieldbus devices, setting of various parameters, and defi
nition of Fieldbus blocks.

• Control Drawing Builder – This builder defines the function blocks and FF facepl
ate blocks of the FCS.

17
2. Engineering
2.3 Configuration Work Flow

Start

Operation in
Creation of ALF111
System View

Registration of Operation in
Device Fieldbus Builder

Creation of FF
Faceplate Blocks
Operation in
Control Drawing
Connections and Builder
Detailed Definition

Download

End

Figure 2.3.1 – Configuration Work Flow

18
2. Engineering
2.4 Typical CS3000 Fieldbus System Configuration
A typical configuration of the Fieldbus system implementation in Y
okogawa Centum CS3000 is shown below.
HIS EWS PRM

VNET/IP
NETWORK

FCS
FCU

ESBbus

ALF111 ALF111 ALF111 ALF111 SB401

(Control) (Standby) (Control) (Standby) (Duplexed)

Local Node
Fieldbus
Terminator
H1 Fieldbus

FF Power
Supply

FF Marshalling Cabinet

Fieldbus
Terminator
H1 Fieldbus

FF Power
Supply

FF Marshalling Cabinet

19
2. Engineering

20
2. Engineering
2.5 Integrated Engineering Function
The Centum CS3000 System View provides integrated engineering and co
nfiguration environment for the Fieldbus control loops. A Fieldbus control
loop is configured in the CS3000 Control Drawing Builder using FF facepla
te blocks (or shadow blocks). The FF faceplate block is part of the FCS fu
nction blocks library that represents a Fieldbus function block in a device.

In addition, a Fieldbus Builder is also provided in the CS3000 System View

to perform definitions unique to Fieldbus such as H1 segment configuratio
n and registration of Fieldbus devices.

21
2. Engineering
The figures below shows typical e
xamples of a Fieldbus control loop
s configured in the CS3000 Contr
ol Drawing Builder.

22
3. FF Loop Check Procedure

3.1 FF device Acquisition

• open FF builder from system

• Choose “Display Device Information…” from menu “tools”

23
3. FF Loop Check Procedure

• If devices connect properly, the information of devices will be read

to DCS.

24
3. FF Loop Check Procedure

• Compare device tag

name, address and
device class within the
FF Builder settings.
Choose device from
device panel and Click
right key, choose “tag
assignment” and “set
device class” to
change tag name,
address and device
class from device
panel as below.

25
3. FF Loop Check Procedure
• Double click device in device panel, call the device information
window, make sure all item is match except “Device ID” and “Software
Revision”, if any item not match, it will be highlight with yellow colour.

26
3. FF Loop Check Procedure
• if “Manufac_ID” , “DEV_TYPE” , DEV_REV” or “Block structure” not m
atch, confirm with EPC, if device in field is correct, revise FF device info
rmation in DCS to match actual device. Back to FF builder, and execut
e update DD_ file as below, choose correct “Manufac_ID”, “DEV_TYPE”
etc.

27
3. FF Loop Check Procedure

28
3. FF Loop Check Procedure
• After confirm every thing match between DCS and FF device, back to
FF build and execute initial download

29
3. FF Loop Check Procedure
• Confirm on FF Faceplate Block that the download has been successful.
Check the faceplate display for CNF, O/S, IOP or OOP indication. The
alarm status of O/S, IOP and OOP are less important, because this alarm
may occur depending on the process condition or wrong XD_SCALE. It
is important to remove the CNF alarm. Because when the FF Faceplate
Block detects an abnormality in the communication with the FFB, it
notifies process alarm CNF.

30
3. FF Loop Check Procedure
3.2 FF Loop Check
There are many kind of Loop Check methods that can be considered.
Whatever, the difference between method for Loop Check, the
purpose is confirmation of loop connectivity.
Whatever the kind of the check method will be applied by EPC, the
following items should be confirmed on DCS Standard Function Block.

• DCS Alarm Status (e.g. IOP, OOP, CNF)

• DCS Range
• DCS Unit

31
3. FF Loop Check Procedure

The summary of various Loop Check Methods is showed as below:

3.2.1 Disconnection of the Spur Cable
This method can be applied to all FF loops with any device type.
The spur cable shall be disconnected from Junction Box and alarm
shall be confirmed on DCS Function Block.
Hereinafter the detail procedure is mentioned;
(1). Disconnect the spur cable from Junction Box
(2). Confirm as follows;
• No power voltage at device terminal point.
• The alarm (CNF) is generated for the respective disconnected device.
(3). Reconnect the spur cable to Junction Box.
(4). Confirm as follows;
• The power voltage is life at device terminal point.
• The alarm (CNF) disappeared

32
3. FF Loop Check Procedure

Figure 3.2.1 Methods of Disconnection of the Spur Cable

33
3. FF Loop Check Procedure

3.2.2 Simulation of the FF Device

This method can be applied to analogue input FF device loops.There

are three methods for turning on the simulation mode .
• By setting “SIM_ENABLE_MSG” parameter in RB using software
(parameter configuration tools, e.g. Emerson 375).
• By setting “SIM_ENABLE_MSG” parameter in RB using hardware
DIP-SW on the FF Device.
• By setting nothing on “SIM_ENABLE_MSG” parameter in RB

34
3. FF Loop Check Procedure

Hereinafter the detail procedure is mentioned;

1). Type of setting by software (e.g. for Yokogawa EJA, YTA and DYF)
Change the “SIM_ENABLE_MSG” parameter in RB to “REMOTE
LOOP TEST SWITCH”
Change the “ENABLE_DISABLE” of “SIMULATE” parameter in FB to
“Active “
Change the “SIMULATE_VALUE” parameter in FB to any value.
Confirm the DCS value is the same with value set in above.
Confirm the display value of FF device (if available).
Change back the “ENABLE_DISABLE” of “SIMULATE” parameter in
FB to “Disable “
Change back the “SIM_ENABLE_MSG” parameter in RB to “ ”.

35
3. FF Loop Check Procedure

2). Type of setting by hardware DIP-SW (e.g. Emerson Fisher-

Rosemount 3144P)
Confirm the simulation mode of hardware DIP-SW on device is
enable, then confirm the “SIMULATE_STATE” parameter in RB is
“jumper on”.
Change the “ENABLE_DISABLE” of “SIMULATE” parameter in FB to
“Active “
Change the “SIMULATE_VALUE” parameter in FB to any value.
Confirm the DCS value is the same with value set in above.
Confirm the display value of FF device (if available).
Change back the “ENABLE_DISABLE” of “SIMULATE” parameter in
FB to “Disable “
Confirm the simulation mode of hardware DIP-SW on device is
Disable, then confirm the “SIMULATE_STATE” parameter in RB is
“jumper off”.

36
3. FF Loop Check Procedure
3). Type of no setting (e.g. Endress Houser Level Flex)
Change the “ENABLE_DISABLE” of “SIMULATE” parameter in FB to
“Active “
Change the “SIMULATE_VALUE” parameter in FB to any value.
Confirm the DCS value is the same with value set in above.
Confirm the display value of FF device (if available).
Change back the “ENABLE_DISABLE” of “SIMULATE” parameter in
FB to “Disable “

37
3. FF Loop Check Procedure

3.2.3 Temperature Multi Input Transmitter

This method can be applied to Temperature Elements (Thermocouple
and RTD )
1). Before check, confirm the PV of DCS (It should be displayed
ambient temperature)
1). For TC, disconnect the signal cable from terminals of TC.
2). For RTD, set jumper to RTD terminals.
3). Confirm the Alarm (IOP) shall be generated for the respective
element.
4). For TC, Reconnect the signal cable to terminals of TC
5). For RTD, remove the Jumper from RTD terminals
6). After test, reconfirm the PV of DCS (It should be displayed
ambient temperature)

38
3. FF Loop Check Procedure

Figure 3.2.2 Methods of Temperature Element

39
3. FF Loop Check Procedure
3.2.4 Valve Positioner
This method can be applied to valve positioner (connected to the
valve with air supply). Give output from DCS and confirm at field the
actual valve position and valve movement direction.
1). Give output to 0% from DCS and confirm valve fully close.
2). Give output to 50% from DCS and confirm valve opening is 50%
and valve movement direction.
3). Give output to 100% from DCS and confirm valve fully open and
valve movement direction.
4). Give output to 0% from DCS and confirm valve fully close.

40
4. Trouble Shooting
4.1 Trouble Shooting
The Loop Check has many factors involved that make the trouble
shooting became complicated.
The most important thing to do trouble shooting, is to separate
whether the issue DCS portion or Local portion (FF Device).

Q1: When device is connected, Can’t find it from Device panel.

A1: Confirm as follows:
• Device address (Node, Slot, Segment).
• Wire have been connected in marshalling cabinet.
• if need supply extra power for this device.

41
4. Trouble Shooting

Q2: Even the spur cable is disconnected, the Alarm (CNF) is not
generate
A2: Confirm as follows:
• Reconnecting the spur cable to FF Device again, and confirm whether
FF Tools is able to access any block parameters or not. If yes the issue
will be the DCS direction side.
• If the other alarm of FF Device is generated when the spur cable is
disconnected, location of FF Device is wrong, or cables connection is
wrong, or Device Tag and Node Address are mismatch. Ask to EPC for
identify the cause.
• Check the Control Drawing Builder settings, “Bad Connection Alarm”
should be “YES”.

42
4. Trouble Shooting
Q3: For Temperature Element, even the signal cable is disconnected
for TC or shorted for RTD, the Alarm (IOP) is not generated.

A3: Confirm as follows;

• Confirm alarm status of “BLOCK_ALM and PV” of FB in FF Device by
FF tools, whether recognizing alarm status or not. If yes the issue will
be the DCS direction side.
• If the other alarm of FF Device is generated when the signal cable is
disconnected, location of FF Device or the element is wrong, or cables
connection is wrong, or Device Tag and Node Address are mismatch.
Ask to EPC for identify the cause.
• Check the Control Drawing Builder settings. “Input Open Alarm”
should be “HL:Both”.

43
4. Trouble Shooting

Q4: IOP alarm status can not be removed

A4: Confirm as follows;
• Ask to EPC to confirm the current situation of FF Device and process.
• Confirm the “CHANNEL” parameter of FB, whether it is set correctly
or wrong.
• Confirm the “SENSOR_TYPE” parameter of FB, whether it is set
correctly or wrong.
• Confirm the TB and RB status is not in O/S

44
4. Trouble Shooting

Q5: O/S status can not be removed

A5: Confirm as follows;
• Confirm the “CHANNEL” parameter of FB, it is set correctly or wrong.
• Confirm the “SENSOR_TYPE” parameter of TB, it is set correctly or
wrong.
• Confirm the TB and RB status is not in O/S
• Confirm the “XD_SCALE” parameter of FB, it is set correctly or wrong.
The XD_SCALE.Unit is restricted by hardware type.

45
4. Trouble Shooting
Q6: Valve is not working properly as the given DCS output
A6: Confirm as follows;
• Whether the air has been already supplied or not.
• Confirm the “ACT_FAIL_ACTION” parameter of TB whether set
correctly or wrong.
• AFC (Air Fail to Close) Valve : Self-closing
• AFO (Air Fail to Open) Valve : Self-opening
Confirm that the “IO_OPTS” settings for “Increase to close” is
“DISABLE”

46
4. Trouble Shooting

Q7: By a method of Loop Check that the process value will be

measured at FF Faceplate Block, the PV is different with the expected
actual value.
A7: Confirm the following setting in the FF Device
• Check the CHANNEL setting
• Check the SENSOR_TYPE setting
• Check Range at OUT_SCALE and XD_SCALE setting
• Check L_TYPE setting

47
4. Trouble Shooting
4.2 Some Example
4.2.1 MICRO MOTION Transmitters (Model 2700)
The Micro Motion Model 2700 transmitter measures mass flow, volume
flow, density and temperature. In addition, the Model 2700 measures
corrected volume flow, concentration and other enhanced density
variables.

48
4. Trouble Shooting
This device has an extra power supply, Commission team need confirm
power on before DCS config it, Otherwise this device can’t be find from
device panel.
After initial download, the FF block status will change from CNF to IOP,
open FF I/O builder, change the channel for AI_01 to “Mass Flow”, default
is “None”.

49
4. Trouble Shooting

4.2.2 Neles-Jamesbury (Model ND9000F)

This device is a field bus powered microcontroller-based intelligent valv
e controller made by Mesto Automation, The ND9000 configuration can
be done either using local push buttons or Fieldbus configurator.

50
4. Trouble Shooting
FF-AO block will stay in OOP IMAN status after initial download; it will b
ack to normal until air supply. This FF device has a PID control block; If
we used FF-PID control block, we need confirm Bypass parameter in PI
D_01 is choose “off” as following. Default is “Uninitialized”.

51
4. Trouble Shooting

4.2.3 Model 752 (Remote display, Rosemount Inc )

The Rosemount 752 Fieldbus Remote Indicator is useful for displaying
the value of a controlled variable next to a final control device or for
displaying information from transmitters mounted in inaccessible
locations. The Indicator can be located anywhere along the segment to
allow information to be displayed wherever it is needed.

52
4. Trouble Shooting
After initial download, FF-IS (DCS block) will back to normal, but in the
remote display will show “Invalid”, check the parameter BLK_TYPE_1 a
nd PARAM_INDEX_1 in Transduce_T01-01, and select the parameter a
s below.

53
4. Trouble Shooting

54
4. Trouble Shooting

55