rEvISION rECOrd ....................................................................................................
1
IM 12A00A01-61E
Introduction 1-1
Manual Name IM No. Instruments mentioned
2-wire pH/ORP Transmitter IM 12B07D02-01E PH202G, PH202S
2-wire Conductivity or Resistivity Transmitter IM 12D08B02-01E SC202G, SC202S
2-wire Inductive Conductivity Transmitter IM 12D06A03-01E ISC202G, ISC202S
2-wire Dissolved Oxygen Transmitter IM 12J05C01-01E DO202G, DO202S
T01.EPS
1. IntroductIon
In the standard user’s manual delivered with the 202 analyzer all necessary information about HART-communication is included. This manual describes only those topics that are required for operation of the fieldbus communications.
For information about instruments related to the EXA202, refer to the following User’s Manuals.
IM 12A00A01-61E
Safety Precautions 2-1
WARNING
CAUTION
IMPORTANT
WARNING
CAUTION
2. SAFETy PrECAUTIONS
• For the protection and safety of the operator and the instrument or the system including the instrument,
please be sure to follow the instructions on safety described in this manual when handling this instrument.
In case the instrument is handled in contradiction to these instructions, Yokogawa does not guarantee
safety.
• For the intrinsically safe equipment and explosionproof equipment, in case the instrument is not restored
to its original condition after any repair or modification undertaken by the customer, intrinsically safe
construction or explosionproof construction is damaged and may cause dangerous condition. Please
contact Yokogawa for any repair or modification required to the instrument.
• The following safety symbol marks are used in this Manual:
Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury.
Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. It
may also be used to alert against unsafe practices.
Indicates that operating the hardware or software in this manner may damage it or lead to system failure.
NOTE
Draws attention to information essential for understanding the operation and features.
• Instrument installed in the process is under pressure. Never loosen or tighten the process connector bolts
as it may cause dangerous spouting of process fluid.
• During draining condensate or venting gas in transmitter pressure-detector section, take appropriate care
to avoid contact with the skin, eyes or body, or inhalation of vapors, if the accumulated process fluid may
be toxic or otherwise harmful.
Since draining condensate or bleeding off gas gives the pressure measurement distur-bance, this should
not be done when the loop is in operation.
• If the accumulated process fluid may be toxic or otherwise harmful, take appropriate care to avoid
contact with the body, or inhalation of vapors even after dismounting the instrument from process line for
maintenance.
This instrument is tested and certified as intrinsically safe type or explosionproof type. Please note that the
construction of the instrument, installation, external wiring, maintenance or repair is strictly restricted, and
non-observance or negligence of these restriction would result dangerous condition.
IM 12A00A01-61E
Foundation Fieldbus 3-1
System/network management VFD
Function block VFD
PD Tag
Sensor
input
Resource block
Block tag
Parameters
Communication
parameters
VCR
Node address
Function block
execution schedule
AI function
block
AI function
block
Output
AI function
block
Block tag
OUT
Parameters
Transducer
block
Block tag
Parameters
Sensor
3. FOUNdATION FIELdBUS
3-1 About Foundation Fieldbus
3-1-1 Outline
Fieldbus is a bi-directional digital communication protocol for field devices, which offers an advancement implementation technologies for process control systems and is widely employed by numerous
field devices.
EXA Series Fieldbus communication type employs the specification standardized by The Fieldbus
Foundation, and provides interoperability between Yokogawa devices and those produced by other
manufacturers. Fieldbus comes with software consisting of three AI function blocks, providing the
means to implement flexible instrumentation system.
For information on other features, engineering, design, construction work, startup and maintenance of
Fieldbus, refer to http://www.yokogawa.com/fbs/fbs-index.htm.
3-1-2 Internal Structure of EXA
The EXA contains two virtual field devices (VFD) that share the following functions.
3-1-2-1 System/network Management vFd
• Sets node addresses and Physical Device tags (PD Tag) necessary for communication
• Controls the execution of function blocks
• Manages operation parameters and communication resources (Virtual Communication Relationship:
VCR)
3-1-2-2 Function Block vFd
(1) resource block
• Manages the status of EXA hardware
• Automatically informs the host of any detected
faults or other problems
(2) Transducer block
• Converts sensor output to process values and
transfers to AI function block by channels
(3) AI1, AI2, AI3 function block
• Conditions raw data from the Transducer block
• Outputs conditioned process values
• Carries out scaling, damping and square root
extraction
3-1-3 Logical Structure of Each Block
Setting of various parameters, node addresses, and
PD Tags shown in Figure 3.1 is required before
starting operation.
Figure 3.1 Logical Structure of Each Block
IM 12A00A01-61E
3-2 Foundation Fieldbus
Sensor cable
gland
Foundation Fieldbus®
cable gland
Grounding terminal
(connect to safety ground,
only if power supply is not grounded)
3-1-4 Wiring System Configuration
The number of devices that can be connected to a single bus and the cable length vary depending on system design. When constructing systems, both the basic and overall design must be carefully considered to
allow device performance to be fully exhibited.
3-2 Getting started
Fieldbus is fully dependent upon digital communication protocol and differs in operation from conventional
4 to 20 mA transmission communication protocol. It is recommended that novice users use field devices in
accordance with the procedures described in this section. The procedures assume that field devices will be
set up on a bench or an instrument shop.
3-2-1 Connection of Devices
3-2-1-1. Fieldbus Preparation
The Foundation Fieldbus® connections and the sensor connections should be made in accordance with figure 3.2 and 3.3. The terminals are of a plug in style for ease of mounting.
The EXA 202 FF is provided with two cable glands. The first is used for the electrode wiring as the other is
used for the power/foundation® Fieldbus wiring shown in figure 3.2.
To open the EXA 202 for wiring:
1. Loosen the four frontplate screws and remove the cover.
2. The terminal strip is now visible.
3. Connect the power supply to the green connector according figure 3.3. Use the gland on the left for this
cable.
4. Connect the sensor input, using the gland on the right (see figure 3.2). Switch on the power.
Commission the instrument as required or use the default settings.
5. Replace the cover and secure frontplate with the four screws.
Figure 3.2 Glands to be used for cabling
Figure 3.3 Green connector for power supply
IM 12A00A01-61E
Foundation Fieldbus 3-3
EXA
Power
supply
Terminator
HOST
Coupler/terminator
IMPORTANT
3-2-1-2. Cables, terminals and glands
The EXA202 is equipped with terminals suitable for the connection of finished cables in the size range:
0.13 to 2.5 mm (26 to 14 AWG). The glands will form a tight seal on cables with an outside diameter in the
range of 6 to 12 mm (0.24 to 0.47 inches).
The following instruments are required for use with Fieldbus devices:
• Power supply
Fieldbus requires a dedicated power supply. It is recommended that current capacity be well over the
total value of the maximum current consumed by all devices (including the host). Conventional DC
current cannot be used as is.
• Terminator
Fieldbus requires two terminators. Refer to the supplier for details of terminators that are attached to the
host.
• Field devices
Connect EXA Fieldbus communication type.
Two or more EXA devices or other devices can be connected.
• Host
Used for accessing field devices. A dedicated host (such as DCS) is used for an instrumentation line
while dedicated communication tools are used for experimental purposes. For operation of the host, refer
to the instruction manual for each host. No details of the host are explained in the rest of this material.
• Cable
Used for connecting devices. Refer to “Fieldbus Technical Information” (TI 38K03A01-01E) for details of
instrumentation cabling.
Fieldbus uses twisted pair wires. To meet the Electro Magnetic Interference standards a shielded twisted
pair is obligated.
Refer to Yokogawa when making arrangements to purchase the recommended equipment.
Connect the devices as shown in Figure 3.4. Connect the terminators at both ends of the trunk, with a mini-
mum length of the spur laid for connection.
The polarity of signal and power must be maintained.
Figure 3.4 Cabling
NOTE
Before using a Fieldbus configuration tool other than the existing host, confirm it does not affect
the loop functionality in which all devices are already installed in operation. Disconnect the relevant
control loop from the bus if necessary.
Connecting a Fieldbus configuration tool to a loop with its existing host may cause communication data scrambles
resulting in a functional disorder or a system failure.
IM 12A00A01-61E
3-4 Foundation Fieldbus
IMPORTANT
Not used
LM device
Not used
Basic device
Default address
Portable-device address
V (FUN)
V (FUN) + V (NUN)
V (NUN)
0xFF
0xFC
0xFB
0xF8
0xF7
0x00
0x0F
0x10
0x13
0x14
Bridge device
Note 1: LM device: with bus control function (Link Master function)
Note 2: BASIC device: without bus control function
EXA
3-2-2 Host Setting
To activate Fieldbus, the following settings are required for the host.
Do not turn off the power immediately after setting. When the parameters are saved to the EEPROM, the
redundant processing is executed for an improvement of reliability. If the power is turned off within 60 seconds after
setting is made, the modified parameters are not saved and the settings may return to the original values.
Table 3.1 Operation Parameters
SymbolParameter Description and Settings
V (ST) Slot-Time Set 4 or greater value.
V (MID) Minimum-Inter-PDU-Delay Set 4 or greater value.
V (MRD) Maximum-Reply-DelaySet so that V (MRD) X V (ST) is 12 or greater
V (FUN) First-Unpolled-NodeDefine the first address that can be used by the host. Set 0x15 or greater.
V (NUN)Number-of-consecutive-Unpolled-NodeThis sets the number of consecutive unpolled nodes. EXA address is
factory-set to 0xEB. Set this address to be within the range of the BASIC
device in Figure 3.5.
Figure 3.5 Available Address Range
3-2-3 Bus Power ON
Turn on the power of the host and the bus. First all segments of the display are lit, then the display begins
to operate. If the indicator is not lit, check the polarity of the power supply.
Using the host device display function, check that the EXA is in operation on the bus.
Unless otherwise specified, the following settings are in effect when shipped from the factory.
If no EXA is detected, check the available address range and the polarity of the power supply. If the node
address and PD tag are not specified when ordering, default value is factory set. If two or more EXA’s are
connected at a time with default value, only one EXA will be detected from the host as EXA’s have the
same initial address.
Separately connect each EXA and set a different address for each.
IM 12A00A01-61E
Foundation Fieldbus 3-5
3-2-4 Integration of dd
If the host supports DD (Device Description), the DD of the EXA needs to be installed. Check if host has the
following directory under its default DD directory.
594543\DEV_TYPE
(594543 is the manufacturer number of Yokogawa Electric Corporation, and DEV_TYPE is the EXA device
number, respectively.)
If this directory is not found, DD of EXA has not been included. Create the above directory and copy the DD
file (0m0n.ffo,0m0n.sym) (m, n is a numeral) (to be supplied separately) into the directory.
Once the DD is installed in the directory, the name and attribute of all parameters of the EXA are displayed.
Off-line configuration is possible by using Capability file (CFF).
3-2-5 reading the Parameters
To read EXA parameters, select the AI1 block of the EXA from the host screen and read the OUT parameter. The current process value is displayed. Check that MODE_BLOCK of the function block and resource
block is set to AUTO.
3-2-6 Continuous record of values
If the host has a function of continuously recording the indications, use this function to list the indications
(values). Depending on the host being used, it may be necessary to set the schedule of Publish (the function that transmits the indication on a periodic basis).
3-2-7 Generation of Alarm
If the host is allowed to receive alarms, generation
of an alarm can be attempted from EXA. In this case, set the reception of alarms on the host side. EXA’s
VCR-7 is factory-set for this purpose. For practical purposes, all alarms are placed in a disabled status; for
this reason, it is recommended that you first use one of these alarms on a trial basis. Set the value of link
object-3 (index 30002) as “0, 299, 0, 6, 0”. Refer to section 3-3-6-1 Link Object for details.
Since the LO_PRI parameter (index 4029) of the AI1 block is set to “0”, try setting this value to “3”. Select
the Write function from the host in operation, specify an index or variable name, and write “3” to it.
The LO_LIM parameter (index 4030) of the AI1 block
determines the limit at which the lower bound alarm for the process value is given. In usual cases, a very
small value is set to this limit. Set a value higher than the current process value, a lower bound alarm is
raised. Check that the alarm can be received at the host. When the alarm is confirmed, transmission of the
alarm is suspended.
The above-mentioned items are a description of the simple procedure to be carried out until EXA is connected to Fieldbus. In order to take full advantage of the performance and functionality of the device, it is
recommended that it be read together with Chapter 5 of relevant User’s Manual, which describes how to
use the EXA.
IM 12A00A01-61E
3-6 Foundation Fieldbus
3-3 Configuration
This chapter contains information on how to adapt the function and performance of the EXA to suit specific
applications. Because two or more devices are connected to Fieldbus, settings including the requirements
of all devices need to be determined. Practically, the following steps must be taken.
(1) Network design
Determines the devices to be connected to Fieldbus and checks the capacity of the power supply.
(2) Network definition
Determines the tag and node addresses for all devices.
(3) definition of combining function blocks
Determines the method for combination between each function block.
(4) Setting tags and addresses
Sets the PD Tag and node addresses one by one for each device.
(5) Communication setting
Sets the link between communication parameters and function blocks.
(6) Block setting
Sets the parameters for function blocks.
The following section describes each step of the procedure in the order given. Using a dedicated configuration tool allows the procedure to be signifi-cantly simplified. This section describes the procedure to be
assigned for a host which has relatively simple functions.
3-3-1 Network design
Select the devices to be connected to the Fieldbus network. The following instruments are necessary for
operation of Fieldbus.
• Power supply
Fieldbus requires a dedicated power supply. It is recommended that current capacity be well over the
total value of the maximum current consumed by all devices (including the host). Conventional DC
current cannot be used as is. A power conditioner is reguired.
• Terminator
Fieldbus requires two terminators. Refer to the supplier for details of terminators that are attached to the
host.
• Field devices
Connect the field devices necessary for instrumentation. EXA has passed the interoperability test
conducted by The Fieldbus Foundation. In order to properly start Fieldbus, it is recommended that the
devices used satisfy the requirements of the above test.
• Host
Used for accessing field devices. A minimum of one device with bus control function is needed.
• Cable
Used for connecting devices. Refer to “Fieldbus Technical Information” for details of instrumentation
cabling. Provide a cable sufficiently long to connect all devices. For field branch cabling, use terminal
boards or a connection box as required.
IM 12A00A01-61E
Foundation Fieldbus �-� �-�
Not used
LM device
Not used
Basic device
Default address
Portable-device address
V (FUN)
V (FUN) + V (NUN)
V (NUN)
0xFF
0xFC
0xFB
0xF8
0xF7
0x00
0x0F
0x10
0x13
0x14
Bridge device
Note 1: LM device: with bus control function (Link Master function)
Note 2: BASIC device: without bus control function
(EXA 0xEB)
First, check the capacity of the power supply. The power supply capacity must be greater than the sum of
the maximum current consumed by all devices to be connected to Fieldbus. The maximum current consumed (power supply voltage 9 to �2 V) for EXA is 26.0 mA. The cable must have the spur in a minimum
length with terminators installed at both ends of the trunk.
3-3-2 Network Definition
Before connection of devices with Fieldbus, define the Fieldbus network. Allocate PD Tag and node
addresses to all devices (excluding such passive devices as terminators).
The PD Tag is the same as the conventional one used for the device. Up to �2 alphanumeric characters
may be used for definition. Use a hyphen as a delimiter as required.
The node address is used to specify devices for communication purposes. Because data is too long for a
PD Tag, the host uses the node address in place of the PD Tag for communication.
A range of 20 to 24� (or hexadecimal 0x14 to 0xF�) can be set.
Addresses of devices with Link Master capabilities are set in a low address range smaller than V(FUN).
Addresses of basic devices are set in a higher range bigger than V(FUN) + V(NUN).
Specify the adress range used by setting the following two parameters in the LM-device:
Table 3.2 Parameters for Setting Address Range
Symbol Parameters Description
V (FUN) First-Unpolled-NodeIndicates the address next to the address range used for the host or other
LM device.
V (NUN) Number-of-consecutive-Unpolled-NodesUnused address range
The devices within the address range written as “Not used” in Figure �.6 cannot be used on a Fieldbus. For
other address ranges, the range is periodically checked to identify when a new device is connected. Care
must be taken not to allow the address range to become wider, which can lead to exhaustive consumption
of Fieldbus communication performance.
Figure 3.6 Available Range of Node Addresses
To ensure stable operation of Fieldbus, determine the operation parameters and set them to the LM devices. While the parameters in Table �.� are to be set, the worst-case values of all the devices to be connected to the same Fieldbus must be used. Refer to the specification of each device for details. Table �.� lists
EXA specification values.
IM 12A00A01-61E
3-8 Foundation Fieldbus
LIC100
FIC100
FC100
FI100
EXA
#2
LI100
EXA
#1
Table 3.3 Operation Parameter Values of the EXA to be Set to LM Devices
Symbol Parameters Description and Settings
V (ST)Slot-TimeIndicates the time necessary for immediate reply of the device. Unit of time is in octets
(256 µs). Set maximum specification for all devices.
For EXA, set a value of 4 or greater.
V (MID) Minimum-Inter-PDU-Delay Minimum value of communication data intervals. Unit of time is in octets (256 µs). Set the
maximum specification for all devices.
For EXA, set a value of 4 or greater.
V (MRD) Maximum-Reply-Delay The worst case time elapsed until a reply is recorded. The unit is Slot-time; set the value
so that V (MRD) 3V (ST) is the maximum value of the specification for all devices.
For EXA, the setting must be a value of 12 or greater.
3-3-3 Definition of Combining Function Blocks
The input/output parameters for function blocks are combined. For the EXA, three AI blocks output parameter (OUT) are subject to combination. They are combined with the input of the control block as necessary.
Practically, setting is written to the EXA link object with reference to “Block setting” in Section 3-3-6 for
details. It is also possible to read values from the host at proper intervals instead of connecting the EXA
block output to other blocks.
The combined blocks need to be executed synchronously with other blocks on the communications schedule. In this case, change the EXA schedule according to the following table. Enclosed values in the table
are factory-settings.
Table 3.4 Execution Schedule of the EXA Function Blocks
Index Parameters Setting (Enclosed is factory-setting)
269(SM)MACROCYCLE_DURATION
276(SM)FB_START_ENTRY.1
277(SM)FB_START_ENTRY.2
278(SM)FB_START_ENTRY.3
279(SM) to
289(SM)
FB_START_ENTRY.4 to 14Not used.
Cycle (MACROCYCLE) period of control or measurement. Unit is 1/32 ms. (32000
= 1 s)
AI1 block startup time. Elapsed time from the start of MACROCYCLE specified in
1/32 ms. (0 = 0 s)
AI2 block startup time. Elapsed time from the start of MACROCYCLE specified in
1/32 ms. (9600 = 0.3 s)
AI3 block startup time. Elapsed time from the start of MACROCYCLE specified in
1/32 ms. (19200 = 0.6 s)
A maximum of 29 ms is taken for execution of an AI block. Executions of AI blocks should be scheduled
sequentially. In no case should two AI function blocks of the EXA be executed at the same time (execution
time is overlapped). 29 ms after AI block execution start the out value is available for further processing.
Figure 3.8 shows an example of schedule based on the loop shown in Figure 3.7.
Figure 3.7 Example of Loop Connecting Function Block of Two EXA with Other Instruments
IM 12A00A01-61E
Foundation Fieldbus 3-9 3-9
LI100
LIC100
FIC100
FC100
FI100
Commu-
nication
Schedule
OUT
IN
OUT
CAS_IN
BKCAL_OUT
BKCAL_IN
BKCAL_IN
BKCAL_OUT
IN
Unscheduled
Communication
Scheduled
Communication
Macrocycle (Control Period)
Figure 3.8 Function Block Schedule and Communication Schedule
When the macrocycle is set to more than 4 seconds, set the following intervals to be more than 1% of the
macrocycle.
- Interval between “end of block execution” and “start of sending CD from LAS”
- Interval between “end of block execution” and “start of the next block execution”“end of block execution” and “start of the next block execution”
3-3-4Settingof Tags andAddresses Setting of Tags and Addresses
This section describes the steps in the procedure to set PD Tags and node addresses in the EXA.
There are three states of Fieldbus devices as shown in Figure 3.9, and if the state is other than SM_
OPERATIONAL state, no function block is executed. EXA must be transferred back to this state after a tag
or address is changed.
UNINITIALIZED
(No tag nor address is set)
Tag clear Tag setting
INITIALIZED
(Only tag is set)
Address clear Address setting
SM_OPERATIONAL
(Tag and address are retained, and
the function block can be executed.)
Figure 3.9 Status Transition by Setting PD Tag and Node Address
EXA has a PD Tag and node address that are set upon shipment from the factory unless otherwise specified. To change only the node address, clear the address once and then set a new node address. To set
the PD Tag, first clear the node address and clear the PD Tag, then set the PD Tag and node address
again.
Devices whose node address was cleared will await the default address (randomly chosen from a range
of 248 to 251, or from hexadecimal F8 to FB). It is necessary to confirm the device ID in order to correctlyorder to correctly
specify the device. The device ID of the EXA is 594543083xxxxxxxxx. (The xxxxxxxxx at the end of the
above device ID is a total of 9 alphanumeric characters. The characters displyed on the screen when each
instrument is powered on, correspond to the xxxxxxxxx and if necessary, should be recorded.)
IM 12A00A01-61E
3-10 Foundation Fieldbus
3-3-5 Communication Setting
To set the communication function, it is necessary to change the database residing in SM-VFD.
3-3-5-1 VCR Setting
Set VCR (Virtual Communication Relationship), which specifies the called party for communication and
resources. EXA has 33 VCRs whose application can be changed, except for the first VCR, which is used for
management.
EXA has VCRs of 3 types:
Publisher(-Subscriber) VCR
Publisher-Subscriber VCR’s are designed to link Function Blocks. When a publishing Function Block runs,
its output data is stored in the buffer of the Publisher VCR. Then the LAS (LM) sends a CD to this VCR to
force it to transfer the data. Subscriber VCRs receive this data and gives this to the subscribing Function
Blocks. Typical example is a linkage from an output of an Analog Input (AI) block to the process value input
of the PID control block.
Publisher-Subscriber model is one-to-many one-way Communication. Subscribers are able to know whether
data is updated since the last publish. This mechanism is important because Data Link Layer transfers data
as scheduled regardless the publishing Function Block updates the data in the buffer.
(Client-)Server Model
Client-Server model is universal and used in many communication technologies. An application called
“Client” requests another application called “Server” to do a specific action. When the Server finishes the
requested action, its result is transferred back to the Client. It is an one-to-one two-way communication.
Typical example is a human-machine interface (Client) to read data of a Function Block (Server). The Client
sends a Read request to the Server and then the Server sends back the data to the Client. This communication is unscheduled and is handled during the unscheduled interval in the macrocycle. A Client may want
to issue many requests at a time. A Client-Server VCR has a queue to store those requests and sends the
requests one by one when the node has the token.
Source(-Sink) Model
A Source-Sink VCR is designed to broadcast messages. It is one-to-many one-way communication without
any schedule. This model is sometimes called “Report Distribution Model.” A Source VCR transfers a message in the queue to an assigned global address when the device has the token. Sink VCRs are set to the
same global address and receive the same message from a Source. Foundation devices use this model for
two specific purposes. One is to report alarms or events detected in the Source and the other is to transmit
trends of Source Function Blocks. Alarms are acknowledged through a Client-Server VCR. It is desirable for
an alarm logger to receive alarms from all devices with just one VCR. A Sink can receive messages from
many Sources if the Sources are configured to send messages to the same global address.
A Source VCR transmits data without established connection. A Sink (QUU) VCR on another device can
receive it if the Sink is configured so. A Publisher VCR transmits data when LAS requests so. An explicit
connection is established from VCR(s) so that a Subscriber knows the format of published data.
Each VCR has the parameters listed in Table 3.5. Parameters must be changed together for each VCR
because modification for each parameter may cause inconsistent operation.
IM 12A00A01-61E
Table 3.5 VCR Static Entry
Subindex
1 FasArTypeAndRole Indicates the type and role of
2 FasDllLocalAddr Sets the local address to
3 FasDllConfigured
4 FasDllSDAP Specifies the quality of
5 FasDllMaxConfirm
6 FasDllMaxConfirm
7 FasDllMaxDlsduSize Specifies maximum DL Service
8 FasDllResidual
9 FasDllTimeliness
Parameter Description
communication (VCR). The
following 3 types are used for
EXA.
0x32: Server (Responds to
requests from host.)
0x44: Source (Transmits alarm
or trend.)
0x66: Publisher (Sends AI
block output to other
blocks.)
specify VCR in EXA. A range of
0x20 to 0xF7 in hexadecimal.
Sets the node address of the
RemoteAddr
DelayOnConnect
DelayOnData
ActivitySupported
Class
called party for communication
and the address (DLSAP or
DLCEP) used to specify VCR
in that address. For DLSAP
or DLCEP, a range of 0x20 to
0xF7 in hexadecimal is used.
Addresses in Subindex 2 and
3 need to be set to the same
contents of the VCR as the
called party (local and remote
are reversed).
communication. Usually, one of
the following types is set.
0x2B: Server
0x01: Source (Alert)
0x03: Source (Trend)
0x91: Publisher
To establish connection for
communication, a maximum
wait time for the called party’s
response is set in ms. Typical
value is 60 seconds (60000).
For request of data, a
maximum wait time for the
called party’s response is
set in ms. Typical value is 60
seconds (60000).
Data unit Size (DLSDU).
Set 256 for Server and Trend
VCR, and 64 for other VCRs.
Specifies whether connection is
monitored. Set TRUE (0xff) for
Server. This parameter is not
used for other communication.
Not used.
Foundation Fieldbus 3-11
Subindex
10 FasDllPublisherTime
11 FasDllPublisher
12 FasDllSubsriberTime
13 FasDllSubscriber
14 FmsVfdId Sets VFD for EXA to be used.
15 FmsMaxOutstanding
16 FmsMaxOutstanding
17 FmsFeatures
Parameter Description
Not used.
WindowSize
Not used.
SynchronizaingDlcep
Not used.
WindowSize
Not used.
SynchronizationDlcep
0x1: System/network
management VFD
0x1234: Function block VFD
Set 0 to Server. It is not
ServiceCalling
ServiceCalled
Supported
used for other applications.
Set 1 to Server. It is not
used for other applications.
Indicates the type of
services in the application
layer. In the EXA, it is
automatically set according
specific applications.
3-11
33 VCRs are factory-set as shown in the table 3.6.
IM 12A00A01-61E
3-12 Foundation Fieldbus
Table 3.6 VCR List VCR List
Index (SM) VCR Number Factory Setting
293 1For system management (Fixed)
294 2Server (LocalAddr = 0xF3)
295 3Server (LocalAddr = 0xF4)
296 4Server (LocalAddr = 0xF7)
297 5Trend Source (LocalAddr = 0x07, Remote Address=0x111)
298 6Publisher for AI1 (LocalAddr = 0x20)
299 7Alert Source (LocalAddr = 0x07, Remote Address=0x110)
3008Server (LocalAddr = 0xF9)
301 to 325 to 3259 to 33Not set
3-3-5-2 Function Block Execution Control
According to the instructions given in Section 3-3-3, set the execution cycle of the function blocks and
schedule of execution.
3-3-6 Block Setting
Set the parameter for function block VFD.
3-3-6-1 Link Object
Link object combines the data voluntarily sent by the function block with VCR. The EXA has 40 link objects.
A single link object specifies one combination. Each link object has the parameters listed in Table 3.7.
Parameters must be changed together for each VCR because the modifications made to each parameter
may cause inconsistent operation.
Table 3.7 Link Object Parameters
Subindex
1 LocalIndex Sets the index of function block parameters to be combined; set “0” for Trend and Alert.
2 VcrNumber Sets the index of VCR to be combined. If set to “0”, this link object is not used.
3 RemoteIndex Not used in EXA. Set to “0”.
4 ServiceOperation
5 StaleCountLimit
Parameters Description
Set one of the following. Only one link object is used for Alert and/or Trend.
0: Undefined
2: Publisher
6: Alert
7: Trend
Set the maximum number of consecutive stale input values which may be received before the input
status is set to BAD. To avoid the unnecessary mode transition caused when the data is not correctly
received by subscriber, set this parameter to “2” or more.
Set link objects as shown in Table 3.8.
Table 3.8 Factory-Settings of Link Objects (example)
IndexLink Object#Factory Settings
30000 1AI1.OUT VCR#6
30001 2Trend VCR#5
30002 3Alert VCR#7
30003 to 300394 to 40Not used
IM 12A00A01-61E
Foundation Fieldbus 3-13
SMIB
(System
Management
Information
Base)
NMIB
(Network
Management
Information
Base)
AI3
OUT
AI1
OUT
AI2
OUT
FBOD
Alert
Trend
VCR
DLSAP
DLCEP
Fieldbus Cable
0xF8 0xF3 0xF4 0xF7
0xF9
0x200x220x21
0x07
#5
Device 3
#10
#1#4
#3
#2
Resource
block
Transducer
block
Host 1
Host 2
Device 1
Device 2
Link
object
#1
#2
#3 #4
#5
#6
#7
#8
#9
3-13
3-3-6-2 Trend Object
It is possible to set the parameter so that the function block automatically transmits Trend. The EXA has
ten Trend objects: eight for trends of analog paramenters and two for discrete parameters. A single Trend
object specifies the trend of one parameter.
Each Trend object has the parameters listed in Table 3.9. The first four parameters are the items to be set.
Before writing to a Trend object, it is necessary to release the WRITE_LOCK parameter.
Table 3.9 Parameters for Trend Objects
Sub-indexParameters Description
1 Block Index Sets the leading index of the function block that takes a trend.
2 Parameter Relative
Index
3 Sample Type Specifies how trends are taken. Choose one of the following 2 types:
4 Sample Interval Specifies sampling intervals in units of 1/32 ms. Set the integer multiple of the function block
5 Last Update The last sampling time.
6 to 21 List of Status 16 samples of status.
21 to 37 List of Samples 16 samples of data.
Sets the index of parameters taking a trend by a value relative to the beginning of the function
block. In the EXA AI block, the following three types of trends are possible.
7: PV
8: OUT
19: FIELD_VAL
1:Sampled upon execution of a function block.
2:The average value is sampled.
execution cycle.
Ten trend objects are factory-set as shown Table 3.10.
Table 3.10 Trend Object are Factory-Set
IndexParametersFactory Settings
32000 to 32007TREND_FLT.1 to TREND_FLT.8Not used.
32008 to 32009TREND_DIS.1 to TREND_DIS.2Not used.
Figure 3.10 Example of Default Configuration
IM 12A00A01-61E
3-14 Foundation Fieldbus
3-3-6-3 ViewObject6-3 View Object
This is the object to form groups of parameters in a block. One advantage of forming groups of parameters
is the reduction of load for data transaction. The EXA has four View Objects for each Resource block,
Transducer block and AI1, AI2, AI3 function block, and each View Object has the parameters listed in Table
3.12 to 3.14.
Table 3.11 Purpose of Each View Object
Description
VIEW_1Set of dynamic parameters required by operator for plant
operation. (PV, SV, OUT, Mode etc.)
VIEW_2Set of static parameters which need to be shown to plant
operator at once. (Range etc.)
VIEW_3Set of all the dynamic parameters
VIEW_4Set of static parameters for configuration or maintenance.
Table 3.12 Indexes of View for Each Block
VIEW_1 VIEW_2 VIEW_3 VIEW_4
Resource Block40100401014010240103
Transducer Block 40200402014020240203
AI1 Function Block40400404014040240403
AI2 Function Block40410404114041240413
AI3 Function Block40420404214042240423
IM 12A00A01-61E
Table 3.13 View Object for Resource BlockTable 3.13 View Object for Resource Block
Function block parameters can be read from the host or can be set. For a list of the parameters of blocks
held by the EXA, refer to “3-6 List of parameters for each block of the EXA”. The following is a list of important parameters with a guide how to set them.
MODE_BLK:
This mode parameter is very important as it gives the state of the block. In O/S (Out_Of_Service) mode the
block is out of operation. In this mode it is allowed to update parameters. Manual mode gives the operator
the possibility to manually update a selected number of parameters (values, scaling e.g.) in order to test the
system. In automatic mode the function block is executed and block parameters are automatically updated.
Under normal operating circumstances, set the Auto mode for normal operation. Auto mode is the factory
default.
Note:
The actual mode is changed by setting the target mode. When the resource block mode is set to
OOS all function blocks in the VFD are set to OOS mode.
CHANNEL:
Transducer blocks convert raw signals into process values. The values are assigned to channels.
For the EXA 202 three or four channels are available.
Scaling information is used for two purposes. Display devices need to know the range for bar graphs and
trending, as well as the units code. Control blocks need to know the range to use internally as percent of
span, so that the tuning constants may remain dimensionless. This is converted back to a number with units
by using the range of OUT_SCALE. The AI block has the parameter XD_SCALE to define the units expected from the transducer.
Transducer scaling (XD_SCALE) is applied to the value from the channel to produce the FIELD_VAL in percent. The XD_SCALE units code must match the channel units code.
The EXA transmitter does this automatically when the Service Codes are changed. See table 3.18 to 3.21
for the Service codes and their results.
If L_TYPE is set to Indirect or Ind Sqr Root, OUT_SCALE determines the conversion from FIELD_VAL to
the output. PV and OUT always have identical scaling. OUT_SCALE provides scaling for PV. The PV is
always the value that the block will place in OUT if the mode is Auto.
Table 3.18 Unit Index by XD_SCALE PH202
ChannelFF parameters Service codeXD_SCALE.UNITS
1-SC01 (set to 0)pH
22029SC11 (set to 0)ºC
22029SC11 (set to 1)ºF
3-SC01 (set to 1)mV
3-SC01 (set to 0), SC02 (set to 1)mV
3-SC01 (set to 0), SC02 (set to 2)rH
Table 3.19 Unit Index by XD_SCALE SC202
ChannelFF parameters Service codeXD_SCALE.UNITS
22023SC11 (set to 0)°C (1001)
22023SC11 (set to 1)°F (1002)
1, 3-SC01 (set to 1)Ω•cm (1295)
1, 3-SC01 (set to 0)S/cm (1594)
4-Default %% (1342)
Table 3.20 Unit Index by XD_SCALE ISC202
ChannelFF parameters Service codeXD_SCALE.UNITS
22023SC11 (set to 0)°C (1001)
22023SC11 (set to 1)°F (1002)
1, 3-Default S/cmS/cm (1594)
4-Default %% (1342)
IM 12A00A01-61E
3-20 Foundation Fieldbus
0%, 0ºC
100%, 212ºF
0%, 32ºF
CHANNEL
PV / OUT
OUT_SCALEXD_SCALE
100%, 100ºC
Table 3.21 Unit Index by XD_SCALE DO202
ChannelFF parameters Service codeXD_SCALE.UNITS
2FF2030SC11 (set to 0)°C (1001)
2FF2030SC11 (set to 1)°F (1002)
1FF2016SC56 (set to 0)ppm (1423)
1FF2016SC56 (set to 1)ppb (1424)
1FF2016SC56 (set to 2)% (1342)
3-Default %% (1342)
4-Default nAnA (1213)
L_TYPE:
Specifies the operation function of the AI block. If set to “Direct”, the input delivered to CHANNEL is directly
reflected on OUT. If set to “Indirect”, scaling by XD_SCALE and OUT_SCALE is carried out and is reflected
on OUT. If set to “Indirect SQRT”, after scaling by XD_SCALE, the square root is extracted and the value
scaled by OUT_SCALE is reflected on OUT.
Example:
Channel range is defined as 0 to 100 °C but °F units is required for HOST display.
Set the following parameters:
XD_SCALE: EU@0% = 0 °C
EU@100% = 100 °C
Unit = °C
Decimal point = 2
OUT_SCALE: EU@0% = 32 °F
EU@100% = 212 °F
Unit = °F
Decimal point = 2
Figure 3.11 Scaling applied to temperature conversion.
PV_FTIME:
Sets the time constant of the damping function within AI block (primary delay) in seconds.
Alarm Priority:
Indicates the priority of the process alarm. If a value of 3 or greater is set, an alarm is transmitted.
The factory default is 0.
Four types of alarm can be set:
HI_PRI, HI_HI_PRI, LO_PRI, and LO_LO_PRI.
Alarm Threshold:
Sets the threshold at which a process alarm is generated. The factory default setting is a value that does
not generate an alarm.
Four types of alarm can be set:
HI_LIM, HI_HI_LIM, LO_LIM, and LO_LO_LIM.
This chapter describes the procedure performed when changing the operation of the function block of the
EXA in process.
3-4-1 Mode Transition
When the function block mode is changed to Out_Of_Service, the function block pauses and a block alarm
is issued.
When the function block mode is changed to Manual, the function block suspends updating of output values. In this case alone, it is possible to write a value to the OUT parameter of the block for output. Note that
no parameter status can be changed.
3-4-2 Generation of Alarm
3-4-2-1 Indication of Alarm
Figure 3.12 Error Identification on Indicator
3-4-2-2 Alarms and Events
Following alarm or event can be reported by EXA as an alert if allowed.
Analog Alerts
(Generated when a process value exceeds threshold)
By AI1 Block Hi-Hi Alarm, Hi Alarm, Low Alarm, Low-Low Alarm
By AI2 Block Hi-Hi Alarm, Hi Alarm, Low Alarm, Low-Low Alarm
By AI3 Block Hi-Hi Alarm, Hi Alarm, Low Alarm, Low-Low Alarm
Discrets Alerts
(Generated when an abnormal condition is detected)
By Resource Block Block Alarm, Write Alarm
By Transducer Block Block Alarm
By AI1 Block Block Alarm
By AI2 Block Block Alarm
By AI3 Block Block Alarm
Update Alerts
(Generated when a important (restorable) parameter is updated)
By Resource Block Update Event
By Transducer Block Update Event
By AI1 Block Update Event
By AI2 Block Update Event
By AI3 Block Update Event
IM 12A00A01-61E
Loading...
+ 63 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.