- Rosemount
- MLT 1, MLT 2 and CAT 200 FOUNDATION Fieldbus Communication Software-3rd Ed.
- Owner's manual
Rosemount MLT 1, MLT 2 and CAT 200 FOUNDATION Fieldbus Communication Software-3rd Ed. Owner's Manual
Add to my manuals
98 Pages
advertisement
Instruction Manual
ETC01184
10/2003
Instruction Manual
Foundation TM Fieldbus
Communication Option for
MLT 1, MLT 2 and CAT 200
3 rd Edition 10/2003 www.EmersonProcess.com
Foundation Fieldbus for MLT 1, MLT 2 & CAT 200 Instruction Manual
ETC01184
10/2003
ESSENTIAL INSTRUCTIONS
READ THIS PAGE BEFORE PROCEEDING!
Emerson Process Management (Rosemount Analytical) designs, manufactures and tests its products to meet many national and international standards. Because these instruments are sophisticated technical products, you MUST properly install, use, and maintain
them to ensure they continue to operate within their normal specifications. The following instructions MUST be adhered to and integrated into your safety program when installing, using and maintaining Emerson Process Management (Rosemount Analytical) products.
Failure to follow the proper instructions may cause any one of the following situations to occur: Loss of life; personal injury; property damage; damage to this instrument; and warranty invalidation.
• Read all instructions prior to installing, operating, and servicing the product.
• If you do not understand any of the instructions, contact your Emerson Process
Management (Rosemount Analytical) representative for clarification.
• Follow all warnings, cautions, and instructions marked on and supplied with the product.
• Inform and educate your personnel in the proper installation, operation, and
maintenance of the product.
• Install your equipment as specified in the Installation Instructions of the appropriate
Instruction Manual and per applicable local and national codes. Connect all products to the proper electrical and pressure sources.
• To ensure proper performance, use qualified personnel to install, operate, update, program, and maintain the product.
• When replacement parts are required, ensure that qualified people use replacement parts specified by Emerson Process Management (Rosemount Analytical). Unauthorized parts and procedures can affect the product’s performance, place the safe operation of your process at risk, and VOID YOUR WARRANTY. Look-alike substitutions may result in fire, electrical hazards, or improper operation.
• Ensure that all equipment doors are closed and protective covers are in place, except when maintenance is being performed by qualified persons, to prevent electrical
shock and personal injury.
The information contained in this document is subject to change without notice. Misprints reserved.
1 st Edition 06/2003 2 nd Edition 10/2003
3rd Edition 10/2003
© 2003 by Emerson Process Management
Emerson Process Management
GmbH & Co. OHG
Industriestrasse 1
D-63594 Hasselroth
Germany
T +49 (0) 6055 884-0
F +49 (0) 6055 884-209
Internet: www.EmersonProcess.com
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
TM Fieldbus
PREFACE
The purpose of this manual is to provide information concerning the technology, components and functions of F
OUNDATION
TM Fieldbus in combination with a MLT or CAT 200 analyzer.
Some sections may describe equipment not used in your configuration.
The user should become thoroughly familiar with the operation of this module before operating it. Read this instruction manual completely.
Definitions
The following definitions apply to WARNINGS, CAUTIONS and NOTES found throughout this publication.
Highlights an operation or maintenance procedure, practice, condition, statement, etc. If not strictly observed, could result in injury, death, or long-term health hazards of personnel.
Highlights an operation or maintenance procedure, practice, condition, statement, etc. If not strictly observed, could result in damage to or destruction of equipment, or loss of effectiveness.
NOTE
Highlights an essential operating procedure, condition or statement.
P-1
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
IMPORTANT
SAFETY INSTRUCTIONS
INTENDED USE STATEMENT
The equipment covered by or referred to within this manual is inteded for use as an industrial process measurement device only. It is not intended for use in medical, diagnostic, or life support applications, and no independent agency certifications or approvals are to be implied as covering such applications.
SAFETY SUMMARY
If this equipment is used in a manner not specified in the related instructions, protective systems may be impaired.
AUTHORIZED PERSONNEL
To avoid loss of life, personal injury and damage to this equipment and on-site property, do not operate or service this instrument before reading and understanding all related instruction manuals and receiving appropriate training. Save these instructions.
EXPLOSION HAZARD
In principle F
OUNDATION
TM Fieldbus signals as described in this manual are
NOT INTRINSICALLY SAFE according to national and international standards for explosion protection for equipment to be used in hazardous areas, except stated on the equipment’s nameplate label!
Do not connect NON INTRINSICALLY SAFE circuits to INTRINSICALLY SAFE ciruits!
Connecting NON INTRINSICALLY SAFE circuits to INTRINSICALLY SAFE ciruits voids the safety of the whole equipment and could result in injury, death, or longterm health hazards of personnel and/or damage to or destruction of equipment!
P-2
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
TM Fieldbus
TABLE OF CONTENTS
PREFACE P-1
SECTION 1
F
Fieldbus Technology 1-1
SECTION 2
Transducer Block 2-1
T-1
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
Table of Contents
Input Failure/ Process Variable has BAD Status .............................................. 2-18
SECTION 3
Resource Block 3-1
SECTION 4
Analog Input (AI) Function Block 4-1
Pressure Transmitter used to Measure Level in Open Tank ........................... 4-10
Differential Pressure Transmitter used to Measure Flow ................................ 4-11
T-2
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
Table of Contents
F
OUNDATION
TM Fieldbus
SECTION 5
Analog Output (AO) Function Block 5-1
SECTION 6
Input Selector (ISEL) Function Block 6-1
SECTION 7
Arithmetic (ARTHM) Function Block 7-1
SECTION 8
Proportional / Integral / Derivative (PID) Function Block 8-1
T-3
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
Table of Contents
8-15-1 Application Example 1
Cascade Control with Master and Slave Loops ............................................... 8-13
APPENDIX
Operation with EMERSON™ Process Management DeltaV™ A-1
T-4
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
TM Fieldbus
SECTION 1
F
OUNDATION
TM
Fieldbus Technology
1-1 Overview
F
OUNDATION
TM Fieldbus is an all digital, serial, two-way communication system that interconnects field equipment such as sensors, actuators, and controllers. Fieldbus is a Local
Area Network (LAN) for instruments used in both process and manufacturing automation with built-in capacity to distribute the control application across the network. It is the ability to distribute control among intelligent field devices on the plant floor and digitally communicate that information at high speed that makes F
OUNDATION
TM Fieldbus an enabling technology.
Emerson offers a full range of products from field devices to the DeltaV scalable control system to allow an easy transition to Fieldbus technology.
The Fieldbus retains the features of the
4-20 mA analog system, including standardized physical interface to the wire, bus powered devices on a single wire, and intrinsic safety options, and enables additional capabilities such as:
• Increased capabilities due to full digital communications.
• Reduced wiring and wire terminations due to multiple devices on one set of wires.
• Increased selection of suppliers due to interoperability.
• Reduced loading on control room equipment with the distribution of some control and input/output functions to field devices.
• Speed options for process control and manufacturing applications.
NOTE: The following descriptions and definitions are not intended as a training guide for Foundation Fieldbus technology but are presented as an overview for those not familiar with Fieldbus and to define device specific attributes for the Fieldbus system engineer.
Anyone attempting to implement Fieldbus communications and control with this analyzer must be well versed in Fieldbus technology and protocol and must be competent in programming using available tools such as
DeltaV. See „References“ below for additional sources for Fieldbus technology and methodology.
1-2 Introduction
A Fieldbus system is a distributed system composed of field devices and control and monitoring equipment integrated into the physical environment of a plant or factory.
Fieldbus devices work together to provide I/O and control for automated processes and operations. The Fieldbus Foundation provides a framework for describing these systems as a collection of physical devices interconnected by a Fieldbus network. One of the ways that the physical devices are used is to perform their portion of the total system operation by implementing one or more function blocks.
1-1
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
1-2-1 Function Blocks
1-2-1 Function Blocks
Function blocks within the Fieldbus device perform the various functions required for process control. Because each system is different, the mix and configuration of functions are different.
Therefore, the Fieldbus F
OUNDATION
has designed a range of function blocks, each addressing a different need.
Function blocks perform process control functions, such as analog input (AI) and analog output (AO) functions as well as proportionalintegral-derivative (PID) functions. The standard function blocks provide a common structure for defining function block inputs, outputs, control parameters, events, alarms, and modes, and combining them into a process that can be implemented within a single device or over the Fieldbus network. This simplifies the identification of characteristics that are common to function blocks.
The Fieldbus F
OUNDATION
has established the function blocks by defining a small set of parameters used in all function blocks called universal parameters. The F
OUNDATION
has also defined a standard set of function block
Input Events Execution Control classes, such as input, output, control, and calculation blocks. Each of these classes also has a small set of parameters established for it. They have also published definitions for transducer blocks commonly used with standard function blocks. Examples include temperature, pressure, level, and flow transducer blocks.
The F
OUNDATION
specifications and definitions allow vendors to add their own parameters by importing and sub-classing specified classes.
This approach permits extending function block definitions as new requirements are discovered and as technology advances.
Fig. 1-1 illustrates the internal structure of a function block. When execution begins, input parameter values from other blocks are snapped-in by the block. The input snap process ensures that these values do not change during the block execution. New values received for these parameters do not affect the snapped values and will not be used by the function block during the current execution.
Output Events
Input Parameter
Input
Status
Fig. 1-1
Function Block Internal Structure
Processing Output
Status
Output
1-2
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
1-2-2 Device Descriptions
F
OUNDATION
TM Fieldbus
Once the inputs are snapped, the algorithm operates on them, generating outputs as it progresses. Algorithm executions are controlled through the setting of contained parameters. Contained parameters are internal to function blocks and do not appear as normal input and output parameters.
However, they may be accessed and modified remotely, as specified by the function block.
Input events may affect the operation of the algorithm. An execution control function regulates the receipt of input events and the generation of output events during execution of the algorithm. Upon completion of the algorithm, the data internal to the block is saved for use in the next execution, and the output data is snapped, releasing it for use by other function blocks.
A block is a tagged logical processing unit. The tag is the name of the block. System management services locate a block by its tag.
Thus the service personnel need only know the tag of the block to access or change the appropriate block parameters.
Function blocks are also capable of performing short-term data collection and storage for reviewing their behavior.
1-2-2 Device Descriptions
Device Descriptions are specified tool definitions that are associated with the function blocks. Device descriptions provide for the definition and description of the function blocks and their parameters.
To promote consistency of definition and understanding, descriptive information, such as data type and length, is maintained in the device description. Device Descriptions are written using an open language called the Device
Description Language (DDL). Parameter transfers between function blocks can be easily verified because all parameters are described using the same language. Once written, the device description can be stored on an external medium, such as a CD-ROM or diskette.
Users can then read the device description from the external medium. The use of an open language in the device description permits interoperability of function blocks within devices from various vendors. Additionally, human interface devices, such as operator consoles and computers, do not have to be programmed specifically for each type of device on the bus. Instead their displays and interactions with devices are driven from the device descriptions.
Device descriptions may also include a set of processing routines called methods. Methods provide a procedure for accessing and manipulating parameters within a device.
1-3
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
1-3 Instrument Specific Function Blocks
1-3 Instrument Specific Function Blocks
In addition to function blocks, Fieldbus devices contain two other block types to support the function blocks. These are the resource block and the transducer block. The resource block contains the hardware specific characteristics associated with a device. Transducer blocks couple the function blocks to local input/output functions.
1-3-1 Resource Blocks
Resource blocks contain the hardware specific characteristics associated with a device; they have no input or output parameters. The algorithm within a resource block monitors and controls the general operation of the physical device hardware. The execution of this algorithm is dependent on the characteristics of the physical device, as defined by the manufacturer. As a result of this activity, the algorithm may cause the generation of events.
There is only one resource block defined for a device. For example, when the mode of a resource block is „out of service,“ it impacts all of the other blocks.
1-3-2 Transducer Blocks
Transducer blocks connect function blocks to local input/output functions. They read sensor hardware and write to effector (actuator) hardware. This permits the transducer block to execute as frequently as necessary to obtain good data from sensors and ensure proper writes to the actuator without burdening the function blocks that use the data. The transducer block also isolates the function block from the vendor specific characteristics of the physical
I/O.
1-3-3 Alerts
When an alert occurs, execution control sends an event notification and waits a specified period of time for an acknowledgment to be received. This occurs even if the condition that caused the alert no longer exists. If the acknowledgment is not received within the prespecified time-out period, the event notification is retransmitted. This assures that alert messages are not lost.
Two types of alerts are defined for the block, events and alarms. Events are used to report a status change when a block leaves a particular state, such as when a parameter crosses a threshold. Alarms not only report a status change when a block leaves a particular state, but also report when it returns back to that state.
1-4
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
1-4 Network Communication
F
OUNDATION
TM Fieldbus
1-4 Network Communication
Fig. 1-2 illustrates a simple Fieldbus network consisting of a single segment (link).
LAS
(Link Active Scheduler)
Fieldbus Link
Link Master
Fig. 1-2
Single Link Fieldbus Network
1-4-1 Link Active Scheduler (LAS)
All links have one and only one Link Active
Scheduler (LAS). The LAS operates as the bus arbiter for the link. The LAS does the following:
• recognizes and adds new devices to the link.
• removes non-responsive devices from the link.
• distributes Data Link (DL) and Link
Scheduling (LS) time on the link. Data Link
Time is a network-wide time periodically distributed by the LAS to synchronize all device clocks on the bus. Link Scheduling time is a link-specific time represented as an offset from Data Link Time. It is used to indicate when the LAS on each link begins and repeats its schedule. It is used by system management to synchronize function block execution with the data transfers scheduled by the LAS.
• polls devices for process loop data at scheduled transmission times.
• distributes a priority-driven token to devices between scheduled transmissions.
Any device on the link may become the LAS, as long as it is capable. The devices that are
Basic Devices and/or LinkMaster Devices capable of becoming the LAS are called link master devices. All other devices are referred to as basic devices. When a segment first starts up, or upon failure of the existing LAS, the link master devices on the segment bid to become the LAS. The link master that wins the bid begins operating as the LAS immediately upon completion of the bidding process. Link masters that do not become the LAS act as basic devices. However, the link masters can act as LAS backups by monitoring the link for failure of the LAS and then bidding to become the LAS when a LAS failure is detected.
Only one device can communicate at a time.
Permission to communicate on the bus is controlled by a centralized token passed between devices by the LAS. Only the device with the token can communicate. The LAS maintains a list of all devices that need access to the bus. This list is called the „Live List.“
Two types of tokens are used by the LAS. A time-critical token, compel data (CD), is sent by the LAS according to a schedule. A nontime critical token, pass token (PT), is sent by the LAS to each device in ascending numerical order according to address.
1-5
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
1-4-2 Device Addressing
1-4-2 Device Addressing
Fieldbus uses addresses between 0 and 255.
Addresses 0 through 15 are reserved for group addressing and for use by the data link layer.
For all Emerson Fieldbus devices addresses
20 through 35 are available to the device. If there are two or more devices with the same address, the first device to start will use its
1-4-3 Scheduled Transfers
Information is transferred between devices over the Fieldbus using three different types of reporting.
• Publisher/Subscriber: This type of reporting is used to transfer critical process loop data, such as the process variable. The data producers (publishers) post the data in a buffer that is transmitted to the subscriber (S), when the publisher
• Report Distribution: This type of reporting is used to broadcast and multicast event and trend reports. The destination address may be predefined so that all reports are sent to the same address, or it may be provided separately with each report. Transfers of this type are
• Client/Server: This type of reporting is used for request/response exchanges between pairs of devices. Like Report Distribution reporting, the transfers are queued, unscheduled, and prioritized.
Queued means the messages are sent and received in the order submitted for programmed address. Each of the other devices will be given one of four temporary addresses between 248 and 251. If a temporary address is not available, the device will be unavailable until a temporary address becomes available.
receives the Compel data. The buffer contains only one copy of the data. New data completely overwrites previous data.
Updates to published data are transferred simultaneously to all subscribers in a single broadcast. Transfers of this type can be scheduled on a precisely periodic basis.
queued. They are delivered to the receivers in the order transmitted, although there may be gaps due to corrupted transfers. These transfers are unscheduled and occur in between scheduled transfers at a given priority.
transmission, according to their priority, without overwriting previous messages.
However, unlike Report Distribution, these transfers are flow controlled and employ a retransmission procedure to recover from corrupted transfers.
1-6
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
1-4-3 Scheduled Transfers
F
OUNDATION
TM Fieldbus
Fig. 1-3 diagrams the method of scheduled data transfer. Scheduled data transfers are typically used for the regular cyclic transfer of process loop data between devices on the
Fieldbus. Scheduled transfers use publisher/ subscriber type of reporting for data transfer.
The Link Active Scheduler maintains a list of transmit times for all publishers in all devices
LAS
Schedule
X
Y
Z
DT(A)
CD(X,A) that need to be cyclically transmitted. When it is time for a device to publish data, the LAS issues a Compel Data (CD) message to the device. Upon receipt of the CD, the device broadcasts or „publishes“ the data to all devices on the Fieldbus. Any device that is configured to receive the data is called a
„subscriber.“
A B
P S
C A
P S
Device X Device Y
LAS = Link Active Scheduler
P = Publisher
S = Subscriber
CD = Compel Data
DT = Data Transfer Packet
D A
P S
Device Z
Fig. 1-3
Scheduled Data Transfer
1-7
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
1-4-4 Inscheduled Transfers
1-4-4 Unscheduled Transfers
Figure 1-4 diagrams an unscheduled transfer.
Unscheduled transfers are used for things like user-initiated changes, including set point changes, mode changes, tuning changes, and upload/download. Unscheduled transfers use either report distribution or client/server type of reporting for transferring data.
All of the devices on the Fieldbus are given a chance to send unscheduled messages between transmissions of scheduled data. The
LAS grants permission to a device to use the
Fieldbus by issuing a pass token (PT) message to the device. When the device receives the PT, it is allowed to send messages until it has finished or until the „maximum token hold time“ has expired, whichever is the shorter time. The message may be sent to a single destination or to multiple destinations.
LAS
Schedule
X
Y
Z
PT(Z)
DT(M)
A
M
B
P S
C
P
A
S
Device X Device Y
LAS = Link Active Scheduler
P = Publisher
S = Subscriber
PT = Pass Token
M = Message
D
M
A
P S
Device Z
Fig. 1-4
Unscheduled Data Transfer
1-8
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
1-4-5 Function Block Scheduling
OUNDATION
TM Fieldbus
1-4-5 Function Block Scheduling
Figure 1-5 shows an example of a link schedule. A single iteration of the link-wide schedule is called the macrocycle. When the system is configured and the function blocks are linked, a master link-wide schedule is created for the LAS. Each device maintains its portion of the link-wide schedule, known as the Function Block Schedule. The Function
Block Schedule indicates when the function blocks for the device are to be executed. The scheduled execution time for each function block is represented as an offset from the beginning of the macrocycle start time.
Device 1 AI
Macrocycle Start Time
Offset from macrocycle Start time = 0 for AI Execution
AI
Offset from macrocycle Start time = 20 for AI Communication
Sequence Repeats
Scheduled
Communication
Unscheduled
Communication
Device 2
PID AO
Offset from macrocycle Start time = 30 for PID Execution
Offset from macrocycle Start time = 50 for AO Execution
PID AO
Macrocycle
Fig. 1-5
Example of Link Schedule
(Showing scheduled and unscheduled communication)
To support synchronization of schedules, periodically Link Scheduling (LS) time is distributed. The beginning of the macrocycle represents a common starting time for all
Function Block schedules on a link and for the
LAS link-wide schedule. This permits function block executions and their corresponding data transfers to be synchronized in time.
1-9
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
1-5 References
1-5 References
The following Fieldbus F
OUNDATION
documents should be used to gain an understanding of
Fieldbus, and are referenced wherever appropriate in the document:
Document Number Document Title
FF-890 Fieldbus Foundation™ Fieldbus Specification —
Function Block Application Process – Part 1
FF-891
FF-902
Fieldbus Foundation™ Fieldbus Specification —
Function Block Application Process – Part 2
Fieldbus Foundation™ Fieldbus Specification —
FF-903
Transducer Block Application Process – Part 1
Fieldbus Foundation™ Fieldbus Specification —
Transducer Block Application Process – Part 2
Tab. 1-1
Fieldbus Foundation Documents
1-5-1 Fieldbus Foundation
The Fieldbus Foundation is the leading organization dedicated to a single international, interoperable Fieldbus standard.
Established in September 1994 by a merger of World FIP North America and the Interoperable Systems Project (ISP), the foundation is a not-for-profit corporation that consists of nearly 120 of the world’s leading suppliers and end users of process control and manufacturing automation products. Working together, these companies have provided unparalleled support for a worldwide Fieldbus protocol, and have made major contributions to the IEC/ISA
Fieldbus standards development.
Important differences exist between the
Fieldbus Foundation and other Fieldbus initiatives. The foundation’s technology -
FOUNDATION Fieldbus - is unique insomuch as it is designed to support mission-critical applications where the proper transfer and handling of data is essential. Unlike proprietary network protocols, FOUNDATION Fieldbus is neither owned by any individual company, or controlled by a single nation or regulatory body.
Rather, it is an „open,“ interoperable Fieldbus that is based on the International Standards
Organization’s Open System Interconnect (OSI/
ISO) seven-layer communications model. The
FOUNDATION specification is compatible with the officially sanctioned SP50 standards project of The International Society for Measurement and Control (ISA) and the International
Electrotechnical Committee (IEC).
Contact information:
9005 Mountain Ridge Drive
Bowie Buldg - Suite 190
Austin, TX 78759-5316, USA
Tel: +1.512.794.8890
Fax: +1.512.794.8893
Email: [email protected]
Internet: www.fieldbus.org
1-10
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
1-6 Implemented Function Blocks
OUNDATION
TM Fieldbus
1-6 Implemented Function Blocks
For the MLT we have implemented the following function blocks :
Intended Use or
Transducer Block Channel Assignments
Resource Block (RB)
TransducerBlock (TB)
Analog-Input Block 1 (AI1) PRIMARY_VARIABLE_1 (see Table 7? 1)
Analog-Input Block 2 (AI2) PRIMARY_VARIABLE_2 (see Table 7? 1)
Analog-Input Block 3 (AI3) SENSOR_FLOW_1 (see Table 7? 1)
Analog-Input Block 4 (AI4) SENSOR_FLOW_2 (see Table 7? 1)
Analog-Input Block 5 (AI5) SENSOR_PRESSURE_1(read) (see Table 7? 1)
Analog-Output Block1 (AO1) SENSOR_PRESSURE_1(w rite) (seeTable 7? 2)
Analog-Output Block2 (AO2) SENSOR_PRESSURE_2(w rite) (seeTable 7? 2)
Arithmetic Block (ARTHM) 4 th order polynomial for any AI-block
PID Block (PID) proportional/integral/derivative control of any AI-block
Input Selector Block (ISEL) selector of any AI-block
Tab. 1-2
Implemented Function Blocks
1-11
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
1-12
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
TM Fieldbus
SECTION 2
Transducer Block
The Transducer Block part was designed to provide the information necessary to interface the MLT to the Fieldbus. The data structures should be used for transferring Fieldbus information between the MLT’s Object
Dictionary and other hosts and devices on
Fieldbus.
Three tables are used to describe the MLT parameters. The List of Parameters table defines the relative index value used to reference the parameter in the MLT Transducer
Block Object Dictionary and the mnemonic used to reference the parameter, as well as the
View(s )in which the parameter is contained.
The Parameter Descriptions table gives a brief description of the behavior of each of the parameters. The Parameter Attributes table describes the key attributes of each of the parameters.
The transmitter specific detailed status and its relationship to standard Fieldbus block alarms and errors are shown in a table in the Detailed
Status section of the document. The I/O channel assignments and their status values are shown in the Channel Assignments section.
Finally the default values for parameters are defined. These are the parameters which will be loaded into the Fieldbus Interface Board’s database before any communication to the transducer itself is performed.
Dynamic parameter default values are specified to aid in configuring static simulations of the transducer block. For example, when creating a placeholder for this device in a host application’s database.
2-1
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
2-1 List of Transducer Block Parameters
2-1 List of Transducer Block Parameters
This section defines parameter access for a basic sensor.
Relative
Index
Parameter Mnemonic VIEW_1 VIEW_2
2 2
Parameter access is described in FF-890.
VIEW_3 VIEW_3 VIEW_4 VIEW_4 VIEW_4 VIEW_4
1 st
2
2 nd
2
1
2 st 2 nd 3 rd 4 th
1 ST_REV
2 TAG_DESC
3 STRATEGY
4 ALERT_KEY
5 MODE_BLK
6 BLOCK_ERR
7 UPDATE_EVT
8 BLOCK_ALM
9 TRANSDUCER_DIRECTORY
10 TRANSDUCER_TYPE
11 XD_ERROR
12 COLLECTION_DIRECTORY
13 PRIMARY_VALUE_TYPE_1
14 PRIMARY_VALUE_1
15 PRIMARY_VALUE_RANGE_1
16 CAL_POINT_HI_1
17 CAL_POINT_LO_1
18 CAL_MIN_SPAN_1
19 CAL_UNIT_1
20 CAL_GAS_TIME_1
21 CAL_ZERO_TOLERANCE_1
22 CAL_SPAN_TOLERANCE_1
23 CAL_SLOPE_1
24 CAL_CONSTANT_1
25 CAL_ZERO_INTERVAL_1
26 CAL_ZERO_DATE_1
27 CAL_SPAN_INTERVAL_1
28 CAL_SPAN_DATE_1
2
1
4
2
5
2
2
4
4
2
1
4
2
5
4
4
7
7
2
1
2
11
2
4
4
2
4
2
2
2
7
31 SPAN_CAL_DATE_1
32 ZERO_CAL_DATE_1
33 SENSOR_TYPE_1
34 SENSOR_RANGE_1
35 SENSOR_ID_1
36 SENSOR_FILTER_VALUE_1
37 SENSOR_RAW_CONCENTRATION_1
38 SENSOR_AVG_CYCLES_1
39 SENSOR_AVG_METHOD_1
40 SENSOR_NOISE_REFVAL_1
4
30
2
1
4
7
7
2
11
4
Tab. 2-1
Transducer Block Parameters
2-2
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
2-1 List of Transducer Block Parameters
TM Fieldbus
Relative
Index
Parameter Mnemonic
66
67
68
69
70
60
61
62
63
64
65
77
78
79
80
71
72
73
74
75
76
54
55
56
57
58
59
48
49
50
51
52
53
41
42
43
44
45
46
47
SENSOR_NOISE_LEVEL_1
SENSOR_NOISE_TUNE_1
SENSOR_ZTEMPERATURE_1
SENSOR_STEMPERATURE_1
SENSOR_TEMP_OFFSET_1
SENSOR_CROSS_INTF_OFFSET_1
SENSOR_TEMP_FACTOR_1
SENSOR_PRESSURE_1
SENSOR_PRESSURE_FACTOR_1
SENSOR_FLOW_1
SENSOR_OPTS_1
PRIMARY_VALUE_TYPE_2
PRIMARY_VALUE_2
PRIMARY_VALUE_RANGE_2
CAL_POINT_HI_2
CAL_POINT_LO_2
CAL_MIN_SPAN_2
CAL_UNIT_2
CAL_GAS_TIME_2
CAL_ZERO_TOLERANCE_2
CAL_SPAN_TOLERANCE_2
CAL_SLOPE_2
CAL_CONSTANT_2
CAL_ZERO_INTERVAL_2
CAL_ZERO_DATE_2
CAL_SPAN_INTERVAL_2
CAL_SPAN_DATE_2
CAL_ ZERO_SPAN_INTERVAL_2
CAL_ ZERO_SPAN_DATE_2
SPAN_CAL_DATE_2
ZERO_CAL_DATE_2
SENSOR_TYPE_2
SENSOR_RANGE_2
SENSOR_ID_2
SENSOR_FILTER_VALUE_2
SENSOR_RAW_CONCENTRATION_2
SENSOR_AVG_CYCLES_2
SENSOR_AVG_METHOD_2
SENSOR_NOISE_REFVAL_2
SENSOR_NOISE_LEVEL_2
VIEW_1 VIEW_2
5
5
VIEW_3 VIEW_3 VIEW_4 VIEW_4 VIEW_4 VIEW_4
1 st 2 nd 1 st 2 nd 3 rd 4 th
4
4
4
4
4
4
4
5
4
5
4
2
5 5
11
4
4
4
2
2
4
4
4
4
2
7
2
7
2
7
7
7
2
11
30
4
4
4
4
2
1
Tab. 2-1 (cont’d)
Transducer Block Parameters
2-3
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
2-1 List of Transducer Block Parameters
Relative
Index
Param eter Mnem onic
81 SENSOR_NOISE_TUNE_2
92
93
94
95
89
90
91
96
97
98
82
83
84
85
86
87
88
SENSOR_ZTEMPERATURE_2
SENSOR_STEMPERATURE_2
SENSOR_TEMP_OFFSET_2
SENSOR_CROSS_INTF_OFFSET_2
SENSOR_TEMP_FACTOR_2
SENSOR_PRESSURE_2
SENSOR_PRESSURE_FACTOR_2
SENSOR_FLOW_2
SENSOR_OPTS_2
ANALYZER_OPTS
MEASUREMENT_OPTS
GAS_CTRL_STATE
CAL_STATE
CAL_STEP
CAL_OPTS
FUNCTION_CALL
DETAILED_FAILURE
99 DETAILED_MAINTENANCE
100 DETAILED_STATUS
101 SIM_DETAILED_FAILURE
102 SIM_DETAILED_MAINTENANCE
103 SIM_DETAILED_STATUS
104 DEVICE_TIME
105 MODULE_SN
106 MANUFACTURING_DATE
107 ANALYZER_HW_VERSION
108 ANALYZER_SW_VERSION
109 ACCESS_MODE
110 STATS_ATTEMPTS
111 STATS_TIMEOUTS
Totals
VIEW_1 VIEW_2
5
5
2
2
45 24
4
4
1
4
4
4
4
7
VIEW_3 VIEW_3 VIEW_4 VIEW_4 VIEW_4 VIEW_4
1 st 2 nd 1 st 2 nd 3 rd 4
4 th
4
4
4
4
4
5
4
5
4
1
2
2
2
1
1
20
30
30
30
1
4
4
86 116 72 110 83 83
Tab. 2-1 (cont’d)
Transducer Block Parameters
2-4
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
2-2 Transducer Block Parameter Descriptions
TM Fieldbus
2-2 Transducer Block Parameter Descriptions
This table gives a description of all parameters in the above table, or gives the location in the
Parameter Mnemonic Description
ACCESS_MODE
ALERT_KEY
ANALYZER_HW_VERSION
ANALYZER_OPTS
ANALYZER_SW_VERSION
BLOCK_ALM
BLOCK_ERR
CAL_CONSTANT_n
CAL_GAS_TIME
CAL_MIN_SPAN_n
CAL_OPTS
CAL_POINT_HI_n
CAL_POINT_LO_n
CAL_SLOPE_n
CAL_SPAN_DATE_n
CAL_SPAN_INTERVAL_n
CAL_SPAN_TOLERANCE_n
CAL_STATE
CAL_STEP
CAL_UNIT_n
CAL_ZERO_DATE_n
CAL_ZERO_INTERVAL_n
CAL_ZERO_SPAN_DATE_n
CAL_ZERO_SPAN_INTERVAL_n
CAL_ZERO_TOLERANCE_n
COLLECTION_DIRECTORY
DETAILED_FAILURE
DETAILED_MAINTENANCE
DETAILED_STATUS
DEVICE_TIME
FUNCTION_CALL
GAS_CTRL_STATE
MANUFACTURING_DATE
MEASUREMENT_OPTS
MODE_BLK
MODULE_SN
PRIMARY_VALUE_n
PRIMARY_VALUE_RANGE_n
PRIMARY_VALUE_TYPE_n
SENSOR_AVG_CYCLES_n
SENSOR_AVG_METHOD_n
SENSOR_CROSS_INTF_OFFSET_n
SENSOR_FILTER_VALUE_n
Fieldbus specifications that the description can be found.
This parameter controls access to the transducer block parameters. See Table 6-8.
See FF-891 section 5.3.
The type of the analyzer hardw are including boot image version string
The installed analyzer options
The version number of the analyzer softw are
See FF-891 section 5.3.
See FF-891 section 5.3.
The zero correction offset (calculated by zero calibration).
Purge delay time (in secs) for calibration gas supply
See FF-903 section 3.3.
The calibration options. See Table 6-5.
See FF-903 section 3.3
See FF-903 section 3.3
This parameter represents the span correction factor (calculated by span calibration).
The date/time the next automatic span calibration w ill be started.
The time interval (in hours) for automatic span calibrations (0 = OFF).
The allowed deviation tolerance (% of CAL_POINT_HI_n) for a span calibration.
This parameter represents the present state a calibration cycle is in.
This parameter is used to control zero and/or span calibrations. See Table 6-3 for the definition of states.
See FF-903 section 3.3.
The date/time the next automatic zero calibration w ill be started.
The time interval (in hours) for automatic zero calibrations (0 = OFF).
The date/time the next automatic zero & span calibrations w ill be started.
The time interval (in hours) for automatic zero & span calibrations (0 = OFF).
The allowed deviation tolerance (% of CAL_POINT_HI_n) for a zero calibration.
See FF-891 section 5.3.
This is a bit-enumerated value used to communicate the failures of the device. SeeTable 6-9.
This is a bit-enumerated value used to communicate the maintenance requests of the device. SeeTable 6-10.
This is a bit-enumerated value used to communicate the status of the device. See Table 6-11 - Detailed
This is the analyzer's internal real time clock. It is used to automatically start time/date controlled procedures.
To synchronize it w ith the FF-central date/time w e should w rite to in certain time intervals.
This parameter is used to call certain device procedures. SeeTable 6-12 for the definition of the states.
The state of controlling the gas valves as w ell as gas pumps.
The analyzer's manufacturing date string
The different kind of options for the measurement.
See FF-891 section 5.3.
The analyzer's serial number
See FF-903 section 3.3.
See FF-903 section 3.3.
See FF-903 section 3.3 and 4.1.
The number of preaveraging cycles for digital signal filtering.
The preaveraging method for digital signal filtering (arithmetic or sliding).
The zero correction of cross interference compensation.
The t90 response time (in secs) for gas change.
Tab. 2-2
Transducer Block Parameter Descriptions
2-5
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
2-1 List of Transducer Block Parameters
Parameter Mnemonic
SENSOR_FLOW_n
SENSOR_ID_n
SENSOR_NOISE_LEVEL_n
SENSOR_NOISE_REFVAL_n
SENSOR_NOISE_TUNE_n
SENSOR_OPTS_n
SENSOR_PRESSURE_n
SENSOR_PRESSURE_FACTOR_n
SENSOR_RANGE_n
SENSOR_RAW_CONCENTRATION_n
SENSOR_STEMPERATURE_n
SENSOR_TEMP_FACTOR_n
SENSOR_TEMP_OFFSET_n
SENSOR_TYPE_n
SENSOR_ZTEMPERATURE_n
SIM_DETAILED_FAILURE
SIM_DETAILED_MAINTENANCE
SIM_DETAILED_STATUS
SPAN_CAL_DATE_n
ST_REV
STATS_ATTEMPTS
STATS_FAILURES
STATS_TIMEOUTS
STRATEGY
TAG_DESC
TRANSDUCER_DIRECTORY
TRANSDUCER_TYPE
UPDATE_EVT
XD_ERROR
ZERO_CAL_DATE_n
Description
The current gas flow (in l/min) of a measurement sensor. If the optional flow sensor is installed this is a dynamic variable. If the sensor is not installed w e do not use for further evaluations.
String w hich contents the measurement sensor's identifier as w ell as the measured gas type.
This is the percentage level of the reference value the dynamic noise filtering becomes active.
This parameter is a reference value (in ppm) for the dynamic noise filter.
Tuning factor how extremely the dynamic noise filter reduces dynamic noises.
The installed sensor specific options.
The current pressure (in hPa) of a measurement sensor:
If internal pressure sensor is installed this is a readonly dynamic variable.
If no pressure sensor is installed w e can input the current pressure value.
If w e use remote pressure w e have to input via AO block. There w e have to select appropriate assignment by the CHANNEL-parameter.
This parameter represents the span correction of pressure compensation.
See FF-903 section 3.3.
This parameter represents the raw value of A/D-Conversion of measurement channel.
This parameter is the temperature (in °C) used for compensation of span corrections.
This parameter represents the span correction of temperature compensation
This parameter represents the zero correction of temperature compensation.
See FF-903 section 3.3 and 4.3.
This parameter is the temperature (in °C) used for compensation of zero corrections.
This is a bit-enumerated value used to simulate the failures of the device. SeeTable 6-9.
This is a bit-enumerated value used to simulate the maintenance requests of the device. SeeTable 6-10.
This is a bit-enumerated value used to simulate the stati of the device. SeeTable 6-11.
The date the last span calibration w as performed.
See FF-891 section 5.3.
Total number of messages sent to the transducer a/d board.
Total number of failed a/d board message attempts.
Total number of timed out a/d board message attempts.
See FF-891 section 5.3.
See FF-891 section 5.3.
See FF-903 section 3.3.
See FF-903 sections 3.3.
See FF-891 section 5.3.
SeeTable 6-9, Table 6-10, Table 6-11and FF-903 section 3.3.
The date the last zero calibration w as performed.
Tab. 2-2 (cont’d)
Transducer Block Parameter Descriptions
2-6
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
2-3 Transducer Block Parameter Attribute Definitions
TM Fieldbus
2-3 Transducer Block Parameter Attribute Definitions
The parameters not described in FF-891 or FF-
903 are described in the following table. This table also includes some parameters defined in FF-891 or FF-903, but are redefined for this application. This table has the same definitions as the one in FF-891, except that the columns for Use/Model and Direction have been omitted because all parameters are contained.
Refer to FF-891, section 5 – Block Parameters, for an explanation of this table.
Parameter Mnemonic
ACCESS_MODE
ANALYZER_HW_VERSION
ANALYZER_OPTS
ANALYZER_SW_VERSION
CAL_CONSTANT_n
CAL_GAS_TIME
CAL_OPTS
CAL_POINT_HI_n
CAL_POINT_LO_n
CAL_SLOPE_n
CAL_SPAN_DATE_n
CAL_SPAN_INTERVAL_n
CAL_SPAN_TOLERANCE_n
CAL_STATE
CAL_STEP
CAL_UNIT_n
CAL_ZERO_DATE_n
CAL_ZERO_INTERVAL_n
CAL_ZERO_SPAN_DATE_n
CAL_ZERO_SPAN_INTERVAL_n
CAL_ZERO_TOLERANCE_n
COLLECTION_DIRECTORY
DETAILED_FAILURE
DETAILED_MAINTENANCE
DETAILED_STATUS
DEVICE_TIME
FUNCTION_CALL
GAS_CTRL_STATE
MANUFACTURING_DATE
MEASUREMENT_OPTS
MODULE_SN
PRIMARY_VALUE_n
S
S
S
A
S
S
S
S
S
S
S
S
R
S
S
S
Obj
Type
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
Data Type /
Structure
Unsigned8
Octet String
Unsigned8
Octet String
Floating Point
Unsigned16
Unsigned8
Floating Point
Floating Point
Floating Point
Date-(11)
Unsigned16
Floating Point
Unsigned16
Unsigned8
Unsigned16
Date-(11)
Unsigned16
Date-(11)
Unsigned16
Floating Point
Array of Unsigned32
Unsigned32
Unsigned32
Unsigned32
Date-(11)
Unsigned8
Unsigned16
Octet String
Unsigned16
Octet String
DS-65
D
D
D
N
D
D
S
S
D
S
S
S
D
D
D
S
Var
4
4
4
7
7
2
4
7
2
2
20
5
1
2
30
Store Size
S
D
S
S
S
S
S
S
S
S
D
D
S
S
D
D
30
4
2
1
4
1
30
1
2
4
2
1
2
4
4
7
Valid Range
See Table 6-8
See Table 6-7
2 - 1000
See Table 6-5
0-999
0 - 100
See Table 6-2
See Table 6-3 ppm, %
(see FF-903 sect. 4.10 Units Codes)
0-999
0-999
0 - 100
FF-903 section 3.3
See Table 6-9
See Table 6-10
See Table 6-11
See Table 6-12
See Table 6-1
See Table 6-4
Initial
Value
0
0
0
0
0
10
2
0
100
0
10
0
0
%
0
0
0
0
0
0
0
0
0
0
0
0
0
Tab. 2-3
Transducer Block Parameter Attribute Definitions
Hours
Hours
%
None
Bit String
Bit String
Bit String
Enumerated
Bit String none
Bit String none
PVR
Units
Enumerated none
Bit String none none
Sec
Bit String
CAL_UNIT
CAL_UNIT
Mode
O/S
O/S
O/S
O/S
Hours
%
Bit String
Enumerated
Enumerated
O/S
O/S
O/S
O/S
Other
Read Only
Read Only
Read Only
Read Only
Note 5-2
Note 5-2
Note 5-2
Note 5-2
Read Only
Note 5-4
Note 5-4
Note 5-2
Read Only
Note 5-2
Note 5-2
Range
Check
Yes
Yes
Yes
Yes
Yes
Yes
Yes
O/S
O/S
O/S
O/S
O/S
Note 5-4
Note 5-4
Note 5-4
Note 5-4
Note 5-2
Read Only
Read Only
Read Only
Read Only
O/S
O/S
Note 5-2
Note 5-2
Read Only
Note 5-2
Read Only
Read Only
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
2-7
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
2-3 Transducer Block Parameter Attribute Definitions
Parameter Mnemonic
PRIMARY_VALUE_RANGE_n
PRIMARY_VALUE_TYPE_n
SENSOR_AVG_CYCLES_n
SENSOR_AVG_METHOD_n
SENSOR_CROSS_INTF_OFFSET_n
SENSOR_FILTER_VALUE_n
SENSOR_FLOW_n
SENSOR_ID_n
SENSOR_NOISE_LEVEL_n
SENSOR_NOISE_REFVAL_n
SENSOR_NOISE_TUNE_n
SENSOR_OPTS_n
SENSOR_PRESSURE_n
SENSOR_PRESSURE_FACTOR_n
SENSOR_RANGE_n
SENSOR_RAW_CONCENTRATION_n
SENSOR_STEMPERATURE_n
SENSOR_TEMP_FACTOR_n
SENSOR_TEMP_OFFSET_n
SENSOR_TYPE_n
SENSOR_ZTEMPERATURE_n
SIM_DETAILED_FAILURE
SIM_DETAILED_MAINTENANCE
SIM_DETAILED_STATUS
SPAN_CAL_DATE_n
STATS_ATTEMPTS
STATS_FAILURES
STATS_TIMEOUTS
ZERO_CAL_DATE_n
Obj
Type
R
S
S
S
S
S
S
S
S
S
S
S
R
S
R
S
S
S
S
S
A
S
S
S
S
S
S
S
S
Tab. 2-3
Transducer Block Parameter Attribute Definitions
Data Type /
Structure
DS-68
Unsigned16
Unsigned16
Unsigned8
Floating Point
Floating Point
DS-65
Octet String
Floating Point
Floating Point
Floating Point
Unsigned32
DS-65
Floating Point
DS-68
Floating Point
Floating Point
Floating Point
Floating Point
Unsigned16
Floating Point
Unsigned32
Array of Unsigned8
Unsigned32
Date-(11)
Unsigned32
Unsigned32
Unsigned32
Date-(11)
S
S
S
S
D
S
D
S
D
D
S
D
D
D
D
S
D
D
S
D
D
D
D
D
S
4
4
4
4
4
4
5
30
5
4
11
4
4
4
4
2
4
4
7
4
4
4
4
4
7
Store Size
S
S
11
2
S
S
2
1
Valid Range
0-100%
See section 4.1 in FF-
903
0: arithmetic
1: sliding
Initial
Value
65535
(other)
1
0
Units
PVR
Enumerated none
Enumerated
0.01-1000
0 – 100
0 – 1000000
1 – 1000
See Table 6-6
0.0-2000.0
0-100 %
0
See FF-903 sect. 4.3 Sensor Types
See Table 6-9
See Table 6-10
See Table 6-11
0-16777215
0-16777215
0-16777215
0
1
0
65535
(Non-Std)
0
0
0
0
0
0
0
0
0
2
0
NULL
0
0
0
0
1013
1 none
Sec l/min none
% ppm none
Bit String hPa none
PVR
ADC Counts
° C none none
Enumerated
° C
Bit String
Bit String
Bit String none none
Mode
O/S
O/S
O/S
O/S
O/S
Other
Note 5-2
Read Only
Read Only
Read Only
Range
Check
Read Only
Note 5-2
Read Only
Read Only
Read Only
Read Only
Read Only
Read Only
Yes
Note 5-1 Note 5-3
Read Only
Read Only
Read Only
Read Only
Read Only
Read Only
Read Only
Read Only
Note 5-5
Note 5-5
Note 5-5
Read Only
Read Only
Read Only
Read Only
Read Only
Note 5-1: Writable only if PRES_REMOTE bit of SENSOR_OPTS_n is set, otherwise is only
Readable.
Note 5-2: This parameter is Read Only if the “local parameter access active ” bit or the "parameter
access via serial service interface active" bit is on in the DETAILED_STATUS word.
Note 5-3: Range check is only done if in SENSOR_OPTS_n the bit PRES_CORR is set.
Note 5-4: This parameter is similar to Note 5-2 and additionally Read Only if VALVES_INST of
SENSOR_OPTS_n is cleared.
Note 5-5: Writable only if Simulation-bit of DETAILED_STATUS is set otherwise Read Only.
2-8
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
2-4 Transducer Block Enumerations
TM Fieldbus
2-4 Transducer Block Enumerations
2-4-1 Gas Control State
Bit Number
15
14
13
12
11
10
9
8
FFValue of
GAS_CTRL_
Description
0x8000 Sample Gas Valve for Snsr1 opened
0x4000 Zero Gas Valve for Snsr1 opened
0x2000 Span Gas Valve for Snsr1 opened
0x0100 Sample Gas pump for Snsr1 running
0x0800 Sample Gas Valve for Snsr2 opened
0x0400 Zero Gas Valve for Snsr2 opened
0x0200 Span Gas Valve for Snsr2 opened
0x0100 Sample Gas pump for Snsr2 running
Tab. 2-4
Gas Control State
During a running calibration procedure of a sensor (see Table 2-5) the gas control states are controlled by this procedure.
So it is refused to change this states by operator during this running procedures.
2-4-2 Calibration States
Bit Number
15
14
13
12
11
10
9
8
FF-Value of
CAL_STATE
Description
0x8000 running zero calibration on Snsr1
0x4000 running span calibration on Snsr1
0x2000 purging changed gas on Snsr1
0x1000 running cross interference calibration of Snsr2 onto Snsr1
0x0800 running zero calibration on Snsr2
0x0400 running span calibration on Snsr2
0x0200 purging changed gas on Snsr2
0x0100 running cross interference calibration of Snsr1 onto Snsr2
Tab. 2-5
Calibration States
2-9
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
2-4 Transducer Block Enumerations
2-4-3 Calibration Step Control
Value CAL_STEP – Description
0 No Action
7
8
5
6
3
4
1
2
Zero Calibration Snsr1
Zero Calibration Snsr2
Zero Calibration Snsr1+2
Span Calibration Snsr1
Span Calibration Snsr2
Span Calibration Snsr1+2
Zero & Span Calibration Snsr1
Zero & Span Calibration Snsr2
9 Zero & Span Calibration Snsr1+2
10 Cross Interference Calibration of Snsr2 onto Snsr1
11 Cross Interference Calibration of Snsr1 onto Snsr2
12 Cancel running Calibration of Snsr1
13 Cancel running Calibration of Snsr2
14 Cancel running Calibration of Snsr1+2
15 Load factory Calibration of Snsr1
16 Load factory Calibration of Snsr2
17 Load factory Calibration of Snsr1+2
Tab. 2-6
Calibration Control Enumerations
To start a calibration procedure of a sensor is only allowed if there is no procedure already running on the same sensor (seeTable 2-5).
If we do not want to wait for finishing the already running procedure we have first to cancel it before starting the new procedure.
2-10
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
2-4 Transducer Block Enumerations
TM Fieldbus
2-4-4 Measurement Options
Bit Num be r
15
14
13
12
11
10
9
8
7
6
5
V alue of
MEAS UREMENT_O PTS
0x8000
0x4000
0x2000
0x1000
0x0800
0x0400
0x0200
0x0100
0x0080
0x0040
0x0020
Pne um onic De s cription
XCMP_1 Cross-Compensation Enabled f or Snsr1
SPLINE_1 Multiple Splines Linearization Enabled f or Snsr1
POLY NOM_1 4 th Order Polynomial Linearization Enabled f or Snsr1 reserved reserved reserved reserved
XCMP_2 reserved
Cross-Compensation Enabled f or Snsr2
SPLINE_2 Multiple Splines Linearization Enabled f or Snsr2
POLY NOM_2 4 th Order Polynomial Linearization Enabled f or Snsr2
Tab. 2-7
Measurement Options
2-4-5 Calibration Options
Bit Number
15
14
13
12
11
Value of
CAL_O PTS
0x8000
0x4000
0x2000
0x1000
0x0800
Description
Calibration Deviation Tolerance Check Enabled for Snsr1 reserved reserved reserved
Calibration Deviation Tolerance Check Enabled for Snsr2
Tab. 2-8
Calibration Options
2-11
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
2-4 Transducer Block Enumerations
2-4-6 Sensor Options
18
17
16
15
22
21
20
19
14
13
12
31
30
25
24
23
29
28
27
26
Bit Num ber
Tab. 2-9
Sensor Options
Value of
SENSOR_O PTS_n
0x80000000
0x40000000
0x20000000
0x10000000
0x08000000
0x04000000
0x02000000
0x01000000
0x00800000
0x00400000
0x00200000
0x00100000
0x00080000
0x00040000
0x00020000
0x00010000
0x00008000
0x00004000
0x00002000
Pneumonic Description not usable
MUX1_ZTEMP Multiplexer1 input is used for temperature zero correction
MUX2_ZTEMP Multiplexer2 input is used for temperature zero correction
OTHER_ZTEMP other sensor is used for temperature zero correction reserved
MUX1_STEMP Multiplexer1 input is used for temperature span correction
MUX2_STEMP Multiplexer2 input is used for temperature span correction
OTHER_STEMP other sensor is used for temperature span correction of sensor
PRES_SENSOR pressure sensor installed
PRES_MANMEAS manual pressure input is used for pressure measurement
PRES_SNSMEAS built-in pressure sensor is used for pressure measurement
PRES_CORR pressure measurement is used for span correction
PRES_REMOTE remote pressure measurement is used for pressure measurement reserved reserved reserved
FLOW_SENSOR flow sensor installed
PUMP_INST pump installed
VALVES_INST valves installed
0x00001000 HEATER_INST heater installed
2-4-7 Analyzer Options
Bit Number
7
6
5
Value of
ANALYZER_O PTS
0x80
0x40
0x20
Description
Serial Gas Flow through Analyzer Cells (otherw ise parallel)
Sensor2 not built-in
FF host is master of date/time
Tab. 2-10
Analyzer Options
2-12
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
2-4 Transducer Block Enumerations
TM Fieldbus
2-4-8 Access Mode Control
Value
0
1
ACCESS_MODE – Description
Normal
Fieldbus access only
Tab. 2-11
Parameter Access Mode Enumerations (ACCESS_MODE)
2-4-9 Detailed Status
2-4-9-1 Detailed Maintenance
Bit
Num ber
19
18
17
16
23
22
21
20
27
26
25
24
31
30
29
28
11
10
9
8
15
14
13
12
Value of
DETAILED_MAINTENANCE
0x80000000
0x40000000
0x20000000
0x10000000
0x08000000
0x04000000
0x02000000
0x01000000
0x00800000
0x00400000
0x00200000
0x00100000
0x00080000
0x00040000
0x00020000
0x00010000
0x00008000
0x00004000
0x00002000
0x00001000
0x00000800
0x00000400
0x00000200
0x00000100
Description
Value of XD_ERROR
(see FF-903) not usable
Deviation too high for zero calibration of Snsr1 CALIBRATION_FAILURE
Deviation too high for span calibration of Snsr1 CALIBRATION_FAILURE
Measurement too noisy during zero calibration of Snsr1 CALIBRATION_FAILURE
Measurement too noisy during span calibration of Snsr1 CALIBRATION_FAILURE digital input notifies maintenance request for Snsr1 IO_FAILURE reserved reserved
NONE
NONE reserved
Deviation too high for zero calibration of Snsr2
NONE
CALIBRATION_FAILURE
Deviation too high for span calibration of Snsr2 CALIBRATION_FAILURE
Measurement too noisy during zero calibration of Snsr2 CALIBRATION_FAILURE
Measurement too noisy during span calibration of Snsr2 CALIBRATION_FAILURE digital input notifies maintenance request for Snsr2 IO_FAILURE reserved reserved
NONE
NONE
Maintenance interval for the device expired factory configuration loaded measurement sensors running in w rong mode and d
GENERAL_FAILURE
DATA_INTEGRITY_FAILURE
IO_FAILURE
NONE reserved reserved reserved reserved
NONE
NONE
NONE
NONE
Tab. 2-12
Detailed Maintenance
2-13
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
2-4 Transducer Block Enumerations
2-4-9-2 Detailed Failure
Bit
Num ber
31
17
16
15
14
13
22
21
20
19
18
27
26
25
24
23
30
29
28
5
4
7
6
12
11
10
9
8
3
2
Tab. 2-13
Detailed Failure
Value of
DETAILED_FAILURE
0x80000000
0x40000000
0x20000000
0x10000000
0x08000000
0x04000000
0x02000000
0x01000000
0x00800000
0x00400000
0x00200000
0x00100000
0x00080000
0x00040000
0x00020000
0x00010000
0x00008000
0x00004000
0x00002000
0x00001000
0x00000800
0x00000400
0x00000200
0x00000100
0x00000080
0x00000040
0x00000020
0x00000010
0x00000008
0x00000004
Description
Value of XD_ERROR
(see FF-903) not usable
Chopper motor turning fails for Snsr1
A/D converter out of range for Snsr1
Source light failed for Snsr1
ELECTRICAL_FAILURE
ALGORITHM_ERROR
ELECTRICAL_FAILURE
Detector component failed for Snsr1
Heater control failed for Snsr1
ELECTRICAL_FAILURE
ELECTRICAL_FAILURE
Sensor of temperature correction failed for Snsr1 IO_FAILURE
Pressure measurement for pressure correction failed for Snsr1 IO_FAILURE digital input notifies failure for Snsr1 IO_FAILURE interfering measurement onto Snsr1 failed over temperature shut dow n for Snsr1 reserved reserved reserved reserved reserved reserved
Chopper motor turning fails for Snsr2
A/D converter out of range for Snsr2
IO_FAILURE
GENERAL_FAILURE
NONE
NONE
NONE
NONE
NONE
NONE
ELECTRICAL_FAILURE
ALGORITHM_ERROR
Source light failed for Snsr2
Detector component failed for Snsr2
Heater control failed for Snsr2
Sensor of temperature correction failed for Snsr2
ELECTRICAL_FAILURE
ELECTRICAL_FAILURE
ELECTRICAL_FAILURE
IO_FAILURE
Pressure measurement for pressure correction failed for Snsr2 IO_FAILURE digital input notifies failure for Snsr2 interfering measurement onto Snsr2 failed over temperature shut dow n for Snsr2 reserved
Communication to sensor electronics failed.
No communication to transducer device
IO_FAILURE
IO_FAILURE
GENERAL_FAILURE
NONE
ELECTRICAL_FAILURE
ELECTRICAL_FAILURE
2-14
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
2-4 Transducer Block Enumerations
TM Fieldbus
2-4-9-3 Detailed Status
Bit
Number
6
5
8
7
4
12
11
10
9
3
2
1
15
14
13
19
18
17
16
23
22
21
20
27
26
25
24
31
30
29
28
FF-Value of
DETAILED_STATUS
0x80000000
0x40000000
0x20000000
0x10000000
0x08000000
0x04000000
0x02000000
0x01000000
0x00800000
0x00400000
0x00200000
0x00100000
0x00080000
0x00040000
0x00020000
0x00010000
0x00008000
0x00004000
0x00002000
0x00001000
0x00000800
0x00000400
0x00000200
0x00000100
0x00000080
0x00000040
0x00000020
0x00000010
0x00000008
0x00000004
0x00000002
Description
Value of XD_ERROR
(see FF-903) not usable
Raw signal for Snsr1 is a simulated one
No valid sample gas measurement running for Snsr1
Any calibration in progress for Snsr1
CONFIGURATION_ERROR
NONE
NONE
Snsr1 is still in w arming up phase
Snsr1 is in a defined state of measurement interruption
NONE
NONE
Snsr1 is in standby-mode NONE
Any of secondary measurements for Snsr1 in simulation mode CONFIGURATION_ERROR digital input notifies an 'out of service' mode for Snsr1 linearization procedure of Snsr1 produces an underflow linearization procedure of Snsr1 produces an overflow installed sample gas pump of Snsr1 not running
NONE
ALGORITHM_ERROR
ALGORITHM_ERROR
NONE reserved reserved reserved reserved
Snsr2 not built in
Raw signal for Snsr2 is a simulated one
No valid sample gas measurement running for Snsr2
NONE
NONE
NONE
NONE
NONE
CONFIGURATION_ERROR
NONE
Any calibration in progress for Snsr2
Snsr2 is still in w arming up phase
Snsr2 is in a defined state of measurement interruption
Snsr2 is in standby-mode
NONE
NONE
NONE
NONE
Any of secondary measurements for Snsr2 in simulation mode CONFIGURATION_ERROR digital input notifies an 'out of service' mode for Snsr2 NONE linearization procedure of Snsr2 produces an underflow linearization procedure of Snsr2 produces an overflow installed sample gas pump of Snsr2 not running
ALGORITHM_ERROR
ALGORITHM_ERROR
NONE local parameter access active parameter access via local serial service interface active
Status simulation active
NONE
NONE
NONE
Tab. 2-14
DetailedStatus
2-15
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
2-4 Transducer Block Enumerations
2-4-10 Function Call Control
Value
0
5
6
7
8
9
3
4
1
2
FUNCTION_CALL – Description
No Action
Acknow ledge and clear Failures Snsr1
Acknow ledge and clear Maintenance Requests Snsr1
Acknow ledge and clear Function Controls Snsr1
Acknow ledge and clear Failures Snsr2
Acknow ledge and clear Maintenance Requests Snsr2
Acknow ledge and clear Function Controls Snsr2
Set FF Host as master of date/time
Set sensor device's clock as master of date/time
Load transducer's factory configuration
Tab. 2-15
Function Call Enumerations (FUNCTION_CALL)
2-16
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
2-5 Transducer Block Channel Assignments
TM Fieldbus
2-5 Transducer Block Channel Assignments
2-5-1 I/O Channel Assignments for AI-Blocks
Transducer Block
Channel Value
1
4
5
2
3
6
Process Variable
PRIMARY_VALUE_1
PRIMARY_VALUE_2
SENSOR_FLOW_1
SENSOR_FLOW_2
SENSOR_PRESSURE_1(read)
SENSOR_PRESSURE_2(read)
XD_SCALE
UNITS
%, ppm
%, ppm l/min l/min hPa hPa
Tab. 2-16
I/O Channel Assignments for AI-Blocks
2-5-2 I/O Channel Assignment for A0-Blocks
Transducer Block
Channel Value
7
8
Process Variable
SENSOR_PRESSURE_1(w rite)
SENSOR_PRESSURE_2(w rite)
XD_SCALE
UNITS hPa hPa
Tab. 2-17
I/O Channel Assignments for AI-Blocks
The assignment of SENSOR_PRESSURE_n is only possible if the device has not enabled the PRES_SNSMEAS-bit of SENSOR_OPTS_n (seeTable 2-9)
2-17
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
2-6 Simulation of TBlk States
2-6 Simulation of TBlk States
The TBlk parameters which are evaluated for the PWAs (=PlantWeb Alerts)
(DETAILED_FAILURE, DETAILED_STATUS and DETAILED_MAINTENANCE) can be simulated.
For the simulation use the parameters SIM_DETAILED_FAILURE,
SIM_DETAILED_MAINTENANCE and
SIM_DETAILED_STATUS.
For activating the simulation mode of these use the bit „Status simulation active“ in
SIM_DETAILED_STATUS .
Having this bit activated the values of
D E T A I L E D _ F A I L U R E ,
D E T A I L E D _ M A I N T E N A N C E ,
DETAILED_STATUS equal the values of
S I M _ D E T A I L E D _ F A I L U R E ,
SIM_DETAILED_MAINTENANCE and
SIM_DETAILED_STATUS.
That means the user has the opportunity to simulate the TBlk-states by writing to the
SIM_DETAILED_XXXX-parameter bits. By this means he has the opportunity to check the correct mapping onto the PWA’s
XXXX_ACTIVE-parameters of the RBlk.
2-7 Supported Transducer Block Errors
2-7-1 Out of Service
Set whenever the transducer block actual mode is OOS
2-7-2 Block Configuration Error
Set whenever there is a communication error between the round board and the a/d board.
2-7-3 Input Failure/ Process Variable has BAD Status
Set whenever PRIMARY_VARIABLE_1 or
PRIMARY_VARIABLE_2 has BAD status.
2-7-4 Device needs Maintenance Now
Set whenever DETAILED_FAILURE is unequal ‘0’.
2-7-5 Simulate Active
Set whenever „Status simulation active“-bit of
DETAILED_STATUS is set.
2-7-6 Other Error
Set whenever XD_ERROR is non-zero.
2-18
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
TM Fieldbus
SECTION 3
Resource Block
3-1 Mapping of the PlantWeb Alerts
Advisory Alert
PlantWeb Alerts
Simulate Active
Inactive Measurement
Mode
Local operator or technician sw itched device into inactive state.
The affected PV quality status w ill go to BAD
Inactive Gas Pump
Maintenance Interval
Expired
Diagnostic Condition
Active
What this Alert is
Detecting?
The alerts are simulated and might not come from live detection
There is installed a sample gas pump but it is not sw itched on.
Maintenance period defined by user is due
What is the effect on the instrument?
R block
RB.BLOCK_ERR
3 Simulate Active
Tblock
DETAILED_STATUS
30 Status simulation active
PWA_SIMULATE
The affected PV quality status w ill go to BAD
No impact
Local operator or technician sw itched device into simulation/diagnostic state.
No impact
Relevant Param eters
RB.SIMULATE_STATE
DETAILED_STATUS
5 Sensor 1 is in a defined state of measurement pause
21 Sensor 2 is in a defined state of measurement pause
6 Sensor 1 is in standby-mode
22 Sensor 2 is in standby-mode
DETAILED_STATUS
11 Installed sample gas pump of sensor 1 not running
27 Installed sample gas pump of sensor 2 not running
DETAILED_STATUS
2 No valid sample gas measurement..Snsr1
18 No valid sample gas measurement..Snsr2
SENSOR_OPTS_1:PUMP_INST
SENSOR_OPTS_1:FLOW_SENSOR
SENSOR_FLOW_1:value
SENSOR_FLOW_1:status
SENSOR_OPTS_2:PUMP_INST
SENSOR_OPTS_2:FLOW_SENSOR
SENSOR_FLOW_2:value
SENSOR_FLOW_2:status
DETAILED_MAINTENANCE
16 maintenance interval expired
DETAILED_STATUS
1 raw signal simulated for sens1
7 2nd measurement simulated for sens1
17 raw signal simulated for sens2
23 2nd measurement simulated for sens2
8 digital input notifies 'out of service' mode for sensor 1
24 digital input notifies 'out of service' mode for sensor 2
Tab. 3-1
MLT PWA Mapping - Advice
Health Bit
90
90
90
90
90
2
3
4
5
8
Maintenance Alert
Calibration Error
What this Alert is
Detecting?
During the calibration, the deviation or noise exceeded acceptable ranges.
What is the effect on the instrum ent?
Analyzer continues to operate, but affected
PV quality status w ill go to UNCERTAIN.
Rblock
RB.BLOCK_ERR
0 Other
Tblock
DETAILED_MAINTENANCE
1 deviation of zero cal Sens1
2 deviation of span cal Sens1
3 noise during zero cal Sens1
4 noise during span cal Sens1
9 deviation of zero cal Sens2
10 deviation of span cal Sens2
11 noise during zero cal Sens2
12 noise during span cal Sens2
DETAILED_MAINTENANCE
5 digital input notify for Snsr1
13 digital input notify for Snsr2
External Maintenance
Request
Configuration Error
A digital input signals a maintenance request from an
Analyzer continues to operate, but affected
PV quality status w ill go to UNCERTAIN.
external facility.
Analyzer configuration does
Analyzer continues to operate, but affected not match definition or configuration has go to UNCERTAIN.
been lost
PV quality status w ill
Linearizer out of range The raw signal readings are out of linearizer's defined range.
Analyzer continues to operate, but affected
PV quality status w ill go to UNCERTAIN.
DETAILED_MAINTENANCE
17 failed battery caused factory config
18 w rong mode of sensors
DETAILED_STATUS
9 linearization proc. of sensor 1 produces an underflow
10 linearization proc. of sensor 1 produces an overflow
25 linearization proc. of sensor 2 produces an underflow
26 linearization proc. of sensor 2 produces an overflow
Relevant Parameters
CAL_OPTS:0
CAL_OPTS:4
PRIMARY_VALUE_1: value
SENSOR_RAW_CONCENTRATION_1
PRIMARY_VALUE_2: value
SENSOR_RAW_CONCENTRATION_2
Tab. 3-2
MLT PWA Mapping - Maintenance
Health Bit
70
70
70
1
2
4
40 16
3-1
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
3-1 Mapping of the PlantWeb Alerts
Failure Alert
What this Alert is
Detecting?
What is the effect on the instrument?
External Failure Signal A digital input signals a failure from an external facility.
The affected PV quality status w ill go to BAD
Rblock Tblock
DETAILED_FAILURE
9 digital input notifies failure for Snsr1
25 digital input notifies failure for Snsr2
Relevant Parameters
Temperature Sensor
Malfunction
Pressure
Compensation
Malfunction
Interfering Gas
Compensation Failure
Temperature out of
Range
Sensor Engine
Hardw are Failure
Output Board NV
Memory Failure
Sensor Board
Electronics Failure
Output Board
Electronics Failure
This detects an out of range temperature sensor.
The sensor w hich is used for pressure compensation calculations is out of order.
It notifies a failure in interfering gas measurements.
This detects an out of range temperature inside the device.
The affected PV quality status w ill go to BAD
The affected PV quality status w ill go to BAD
The affected PV quality status w ill go to BAD
The affected PV quality status w ill go to BAD
DETAILED_FAILURE
6 Sensor of temp. corr. failed for sensor 1
22 Sensor of temp. corr. failed for sensor 2
DETAILED_FAILURE
7 Pressure measurement for pressure correction failed for Snsr1
23 Pressure measurement for pressure correction failed for Snsr2
DETAILED_FAILURE
8 interfering meas. onto Snsr1 failed
24 interfering meas. onto Snsr2 failed
DETAILED_FAILURE
5 Heater control failed for Snsr1
21 Heater control failed for Snsr2
10 over temperature shut dow n for Snsr1
26 over temperature shut dow n for Snsr2
SENSOR_ZTEMPERATURE_1
SENSOR_STEMPERATURE_1
SENSOR_ZTEMPERATURE_2
SENSOR_STEMPERATURE_2
SENSOR_PRESSURE_1:value
SENSOR_PRESSURE_1:status
SENSOR_PRESSURE_2:value
SENSOR_PRESSURE_2:status
SENSOR_OPTS_1: PRES_REMOTE
SENSOR_OPTS_2: PRES_REMOTE
PRIMARY_VALUE_2:value
PRIMARY_VALUE_2:status
PRIMARY_VALUE_1:value
PRIMARY_VALUE_1:status
SENSOR_ZTEMPERATURE_1
SENSOR_STEMPERATURE_1
SENSOR_ZTEMPERATURE_2
SENSOR_STEMPERATURE_2
SENSOR_OPTS_1: HEATER_INST
SENSOR_OPTS_2: HEATER_INST
Various faults w ill cause the analysis to be bad includig failure in chopper motor, light source or the detector component output w ill not be valid or analyzer w ill not operate
DETAILED_FAILURE
1 Chopper motor failure Snsr1
17 Chopper motor failure Snsr2
2 A/D converter out of range for Snsr1
18 A/D converter out of range for Snsr2
3 Source light failed for Snsr1
19 Source light failed for Snsr2
4 Detector component failed for Snsr1
20 Detector component failed for Snsr2
28 Sensor Communication failed
The non-volatile parameter storage on the CPU board has become unreliable
RB.BLOCK_ERR
0 Other
11 Lost NV Data
This occurs w hen the electronics of the sensor can not reliably send data to the Fieldbus Output
Electronics Board.
Data w ill be unusable,
bad quality alarm w ill be sent to the operator
RB.DETAILED_STATUS
4 NV Integrity error
RB.BLOCK_ERR
0 Other
13 Device Needs and the analyzer w ill be Maintenance Now taken out of service.
15 Out of service
RB.DETAILED_STATUS
1 Sensor transducer error
DETAILED_FAILURE
29 No communication to transducer device
This occurs w hen the electronics can not reliably collect data from the sensors
Data w ill be unusable, a bad quality alarm w ill be sent to the operator
RB.BLOCK_ERR
0 Other
9 Memory Failure and the analyzer w ill be taken out of service.
13 Device Needs
Maintenance Now
15 Out of service
RB.DETAILED_STATUS
2 Manufacturing block integrity error
5 Register test failure
6 ROM integrity error
Health Bit
10 9
10
10
10
10
10
10
10
10
11
12
13
14
16
22
23
24
Tab. 3-3
MLT PWA Mapping - Failed
3-2
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
3-2 PWA_Simulate
F
OUNDATION
TM Fieldbus
3-2 PWA_SIMULATE
Having PWA_SIMULATE == ON allows simulating the RBlk-parameters
FAILED_ACTIVE, MAINT_ACTIVE and
ADVISE_ACTIVE.
„Allow simulating“ means that these parameters get write permission and the host’s written value is the only one which is used for parameter’s read back value. The data which come via
1451-protocol from the MLT itself is not used in this case (also no wired-OR).
There are some bits of DETAILED_STATUS of the RBlk (not TBlk!) which are mapped to
FAILED_ACTIVE („Electronics Failure“ and
„NV memory failure“).
We also allow simulating them in this state.
Hereby is used a wired-OR logic of these
DETAILED_STATUS bits and of the appropriate FAILED_ACTIVE bits.
3-3
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
3-4
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
TM Fieldbus
SECTION 4
Analog Input (AI) Function Block
OUT = The block output value and status
OUT_D = Discrete output that signals a selected alarm condition
Fig. 4-1
Analog input function block
The Analog Input (AI) function block processes field device measurements and makes them available to other function blocks. The output value from the AI block is in engineering units and contains a status indicating the quality of the measurement. The measuring device may have several measurements or derived values available in different channels. Use the channel number to define the variable that the AI block processes.
The AI block supports alarming, signal scaling, signal filtering, signal status calculation, mode control, and simulation.
Parameter
ACK_OPTION
ALARM_HYS
Index
Number
23
24
Units
None
Percent
ALARM_SEL
ALARM_SUM
ALERT_KEY
BLOCK_ALM
38
22
4
21
None
None
None
None
In Automatic mode, the block’s output parameter (OUT) reflects the process variable
(PV) value and status. In Manual mode, OUT may be set manually. The Manual mode is reflected on the output status. A discrete output
(OUT_D) is provided to indicate whether a selected alarm condition is active. Alarm detection is based on the OUT value and user specified alarm limits. Figure 3-2 on page 3–3 illustrates the internal components of the AI function block while table 3-1 lists the AI block parameters and their units of measure, descriptions and index numbers.
Description
Used to set auto acknow ledgment of alarms.
The amount the alarm value must return w ithin the alarm limit before the associated active alarm condition clears.
Used to select the process alarm conditions that w ill cause the OUT_D parameter to be set.
The summary alarm is used for all process alarms in the block. The cause of the alert is entered in the subcode field. The first alert to become active w ill set the Active status in the Status parameter. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported w ithout clearing the Active status, if the subcode has changed.
The identification number of the plant unit. This information may be used in the host for sorting alarms, etc.
The block alarm is used for all configuration, hardw are, connection failure or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active w ill set the Active status in the Status parameter. As soon as the
Unreported status is cleared by the alert reporting task, another block alert may be reported w ithout clearing the Active status, if the subcode has changed.
Tab. 4-1
Definitions of Analog Input Function Block System Parameters
4-1
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
4 Analog Input (AI) Function Block
Parameter
BLOCK_ERR
CHANNEL
FIELD_VAL
GRANT_DENY
HI_ALM
HI_HI_ALM
HI_HI_LIM
HI_HI_PRI
HI_LIM
HI_PRI
IO_OPTS
L_TYPE
Index
Number
6
15
26
25
28
27
13
16
34
33
19
12
Units Description
None
None
Percent
None
None
None
EU of
PV_SCALE
None
EU of
PV_SCALE
None
None
None
This parameter reflects the error status associated w ith the hardw are or softw are components associated w ith a block. It is a bit string, so that multiple errors may be show n.
The CHANNEL value is used to select the measurement value. Refer to the appropriate device manual for information about the specific channels available in each device. The
CHANNEL parameter must be configured before configuring the XD_SCALE parameter.
The value and status from the transducer block or from the simulated input w hen simulation is enabled.
Options for controlling access of host computers and local control panels to operating, tuning, and alarm parameters of the block. Not used by device.
The HI alarm data, w hich includes a value of the alarm, a timestamp of occurrence and the state of the alarm.
The HI HI alarm data, w hich includes a value of the alarm, a timestamp of occurrence and the state of the alarm.
The setting for the alarm limit used to detect the HI HI alarm condition.
The priority of the HI HI alarm.
The setting for the alarm limit used to detect the HI alarm condition.
The priority of the HI alarm.
Allow s the selection of input/output options used to alter the PV. Low cutoff enabled is the only selectable option.
Linearization type. Determines w hether the field value is used directly (Direct), is converted linearly (Indirect), or is converted w ith the square root (Indirect Square Root).
LO_ALM
LO_LIM
LO_LO_ALM
LO_LO_LIM
LO_LO_PRI
LO_PRI
LOW_CUT
MODE_BLK
OUT
OUT_D
OUT_SCALE
PV
PV_FTIME
SIMULATE
STRATEGY
ST_REV
35
30
36
32
31
29
17
5
8
37
11
7
18
9
3
1
None The LO alarm data, w hich includes a value of the alarm, a timestamp of occurrence and the state of the alarm.
The setting for the alarm limit used to detect the LO alarm condition.
EU of
PV_SCALE
None The LO LO alarm data, w hich includes a value of the alarm, a timestamp of occurrence and the state of the alarm.
The setting for the alarm limit used to detect the LO LO alarm condition.
EU of
PV_SCALE
None
None
%
None
None
None
None
The priority of the LO LO alarm.
The priority of the LO alarm.
If percentage value of transducer input fails below this, PV = 0.
The actual, target, permitted, and normal modes of the block.
Target: The mode to “go to”
Actual: The mode the “block is currently in”
Permitted: Allow ed modes that target may take on
Normal: Most common mode for target
The block output value and status.
EU of
OUT_SCALE
None
None
Discrete output to indicate a selected alarm condition.
The high and low scale values, engineering units code, and number of digits to the right of the decimal point associated w ith OUT.
The process variable used in block execution.
EU of
XD_SCALE
Seconds The time constant of the first-order PV filter. It is the time required for a 63% change in the IN value.
A group of data that contains the current transducer value and status, the simulated transducer value and status, and the enable/disable bit.
The strategy field can be used to identify grouping of blocks. This data is not checked or processed by the block.
The revision level of the static data associated w ith the function block. The revision value w ill be incremented each time a static parameter value in the block is changed.
Tab. 4-1 (cont’d)
Definitions of Analog Input Function Block System Parameters
4-2
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
4-1 Simulation
F
OUNDATION
TM Fieldbus
Param eter
TAG_DESC
UPDATE_EVT
VAR_INDEX
VAR_SCAN
XD_SCALE
Index
Num ber
2
20
39
40
10
Units
None
None
% of OUT
Range
Seconds
None
Description
The user description of the intended application of the block.
This alert is generated by any change to the static data.
The average absolute error betw een the PV and its previous mean value over that evaluation time defined by VAR_SCAN.
The time over w hich the VAR_INDEX is evaluated.
The high and low scale values, engineering units code, and number of digits to the right of the decimal point associated w ith the channel input value. The XD_SCALE units code must match the units code of the measurement channel in the transducer block. If the units do not match, the block w ill not transition to MAN or AUTO.
Tab. 4-1 (cont’d)
Definitions of Analog Input Function Block System Parameters
4-1 Simulation
To support testing, either change the mode of the block to manual and adjust the output value, or enable simulation through the configuration tool and manually enter a value for the measurement value and its status. In both cases, the ENABLE jumper on the field device must first be set.
With simulation enabled, the actual measurement value has no impact on the OUT value or the status.
Analog
Measurement
ALARM_TYPE
Access
Analog
Meas.
CHANNEL
HI_HI_LIM
HI_LIM
LO_LO_LIM
LO_LIM
ALARM_HYS
LOW_CUT
Alarm
Detection
Convert
Sq Root
Cutoff Filter PV
SIMULATE L_TYPE
FIELD_VAL
OUT_SCALE
XD_SCALE
IO_OPTS
Fig. 4-2
Analog Input Function Block Schematic
PV_FTIME
MODE
STATUS_OPTS
Status
Calc.
All Fieldbus instruments have a simulation jumper. As a safety measure, the jumper has to be reset every time there is a power interruption. This measure is to prevent devices that went through simulation in the staging process from being installed with simulation enabled.
OUT_D
OUT
OUT = The block output value and status
OUT_D= Discrete output that signals a
selected alarm condition
4-3
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
4-2 Filtering
63% of Change
OUT (mode in man)
OUT (mode in auto)
PV
FIELD_VAL
PV_FTIME
Fig. 4-3
Analog Input Function Block Timing Diagram
Time (seconds)
4-2 Filtering
The filtering feature changes the response time of the device to smooth variations in output readings caused by rapid changes in input.
The filter time constant (in seconds) can be adjusted using the PV_FTIME parameter. Set the filter time constant to zero to disable the filter feature.
4-3 Signal Conversion
Set the signal conversion type with the
Linearization Type (L_TYPE) parameter.
View the converted signal (in percent of
XD_SCALE) through the FIELD_VAL parameter.
FIELD_VAL =
100 x
(
(
EU
Channel
* @ 100
Value
% − EU
EU *
* @
@0%
0 %
)
)
*XD_SCALE values
4-4
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
4-3 Signal Conversion
F
OUNDATION
TM Fieldbus
Choose from direct, indirect, or indirect square root signal conversion with the L_TYPE parameter.
• Direct
Direct signal conversion allows the signal to pass through the accessed channel input value (or the simulated value when simulation is enabled).
PV = Channel Value
• Indirect
Indirect signal conversion converts the signal linearly to the accessed channel input value (or the simulated value when
PV = simulation is enabled) from its specified range (XD_SCALE) to the range and units of the PV and OUT parameters
(OUT_SCALE).
FIELD _ VAL
100 x
(
EU * * @ 100 % − EU * * @ 0 %
)
+ EI * * @ 0 %
*OUT_SCALE values
• Indirect Square Root
Indirect Square Root signal conversion takes the square root of the value computed with the indirect signal conversion and scales it to the range and units of the PV and OUT parameters.
PV =
FIELD _ VAL
100
x
(
EU * * @ 100 % − EU * * @ 0 %
)
+ eu * * @ 0 %
*OUT_SCALE values
When the converted input value is below the limit specified by the LOW_CUT parameter, and the Low Cutoff I/O option (IO_OPTS) is enabled (True), a value of zero is used for the converted value (PV). This option is useful to eliminate false readings when the differential pressure measurement is close to zero, and it may also be useful with zero-based measurement devices such as flow meters.
Low Cutoff is the only I/O option supported by the AI block. It is possible to set the I/O option in
Manual or Out of Service mode only.
4-5
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
4-4 Block Errors
4-4 Block Errors
Table 32 lists conditions reported in the
BLOCK_ERR parameter. Conditions in italics are inactive for the AI block and are here listed for reference only.
10
11
12
13
14
15
6
7
8
9
4
5
2
3
Condition
Number
0
1
Condition Name and Description
Other
Block Configuration Error: the selected channel carries a measurement that is incompatible w ith the engineering units selected in XD_SCALE, the L_TYPE parameter is not configured, or CHANNEL = zero.
Link Configuration Error
Sim ulate Active: Simulation is enabled and the block is using a simulated value in its execution.
Local Override
Device Fault State Set
Device Needs Maintenance Soon
Input Failure/Process Variable has Bad Status: The hardw are is bad, or a bad status is being simulated.
Output Failure: The output is bad based primarily upon a bad input.
Memory Failure
Lost Static Data
Lost NV Data
Readback Check Failed
Device Needs Maintenance Now
Power Up
Out of Service: The actual mode is out of service.
Tab. 4-2
Block Error Conditions
4-5 Modes
The AI Function Block supports three modes of operation as defined by the MODE_BLK parameter:
• Manual (Man) The block output (OUT) may be set manually
• Automatic (Auto) OUT reflects the analog input measurement or the simulated value when simulation is enabled.
• Out of Service (O/S) The block is not processed. FIELD_VAL and PV are not updated and the OUT status is set to Bad:
Out of Service. The BLOCK_ERR parameter shows Out of Service. In this mode, changes can be made to all configurable parameters. The target mode of a block may be restricted to one or more of the supported modes.
4-6
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
4-6 Alarm Detection
F
OUNDATION
TM Fieldbus
4-6 Alarm Detection
A block alarm will be generated whenever the
BLOCK_ERR has an error bit set. The types of block error for the AI block are defined above.
Process Alarm detection is based on the OUT value. The alarm limits of the following standard alarms can be configured:
• High (HI_LIM)
• High high (HI_HI_LIM)
• Low (LO_LIM)
• Low low (LO_LO_LIM)
In order to avoid alarm chattering when the variable is oscillating around the alarm limit, an alarm hysteresis in percent of the PV span can be set using the ALARM_HYS parameter. The priority of each alarm is set in the following parameters:
• HI_PRI
• HI_HI_PRI
• LO_PRI
• LO_LO_PRI
Alarms are grouped into five levels of priority:
Priority
0
1
2
03. Jul
Aug 15
Priority Description Number
The priority of an alarm condition changes to 0 after the condition that caused the alarm is corrected.
An alarm condition w ith a priority of 1 is recognized by the system, but is not reported to the operator.
An alarm condition w ith a priority of 2 is reported to the operator, but does not require operator attention (such as diagnostics and system alerts).
Alarm conditions of priority 3 to 7 are advisory alarms of increasing priority.
Alarm conditions of priority 8 to 15 are critical alarms of increasing priority.
Tab. 4-3
Alarm Priorities
4-7
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
4-7 Status Handling
4-7 Status Handling
Normally, the status of the PV reflects the status of the measurement value, the operating condition of the I/O card, and any active alarm condition. In Auto mode, OUT reflects the value and status quality of the PV. In Man mode, the
OUT status constant limit is set to indicate that the value is a constant and the OUT status is
Good.
The Uncertain - EU range violation status is always set, and the PV status is set high- or low-limited if the sensor limits for conversion are exceeded.
In the STATUS_OPTS parameter, select from the following options to control the status handling:
• BAD if Limited – sets the OUT status quality to Bad when the value is higher or lower than the sensor limits.
• Uncertain if Limited – sets the OUT status quality to Uncertain when the value is higher or lower than the sensor limits.
• Uncertain if in Manual mode – The status of the Output is set to Uncertain when the mode is set to Manual.
The instrument must be in Manual or Out of Service mode to set the status option.
The AI block only supports the
BAD if Limited option. Unsupported options are not grayed out; they appear on the screen in the same manner as supported options.
4-8 Advanced Features
The AI function block provided with Emerson
Fieldbus devices provides added capability through the addition of the following parameters:
• ALARM_TYPE – Allows one or more of the process alarm conditions detected by the AI function block to be used in setting its OUT_D parameter.
• OUT_D – Discrete output of the AI function block based on the detection of process alarm condition(s). This parameter may be linked to other function blocks that require a discrete input based on the detected alarm condition.
• VAR_SCAN – Time period in seconds over which the variability index
(VAR_INDEX) is computed.
• VAR_INDEX – Process variability index measured as the integral of average absolute error between PV and its mean value over the previous evaluation period.
This index is calculated as a percent of
OUT span and is updated at the end of the time period defined by VAR_SCAN.
4-8
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
4-9 Applicatin Information
F
OUNDATION
TM Fieldbus
4-9 Application Information
The configuration of the AI function block and its associated output channels depends on the specific application. A typical configuration for the AI block involves the following parameters:
• CHANNEL If the device supports more than one measurement, verify that the selected channel contains the appropriate measurement or derived value.
• L_TYPE
Select Direct when the measurement is already in the engineering units that are desired for the block output.
Select Indirect when it is desired to convert the measured variable into another, for example, pressure into level or flow into energy.
Select Indirect Square Root when the block I/O parameter value represents a flow measurement made using differential pressure, and when square root extraction is not performed by the transducer.
4-9-1 Application Example 1
Temperature Transmitter
Situation
A temperature transmitter with a range of
–200 to 450 °C.
Parameter Configured
Values
L_TYPE Direct
XD_SCALE Not Used
OUT_SCALE Not Used
• SCALING XD_SCALE provides the range and units of the measurement and
OUT_SCALE provides the range and engineering units of the output.
Solution
The table below lists the appropriate configuration settings, and the figure illustrates the correct function block configuration.
Temperature
Measurement
AI Function Block
OUT_D
OUT To Another
Function Block
4-9
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
4-9 Application Information
4-9-2 Application Example 2
Pressure Transmitter used to Measure Level in Open Tank
Situation #1
The level of an open tank is to be measured using a pressure tap at the bottom of the tank.
The level measurement will be used to control the level of liquid in the tank.
The maximum level at the tank is 16 ft. The liquid in the tank has a density that makes the level correspond to a pressure of 7.0 psi at the pressure tap (see diagram below).
16 ft
Full Tank
7.0 psi measured at the transmitter
Fig. 4-5
Situation #1 Diagram
Solution to Situation #1
The table below lists the appropriate configuration settings, and the figure illustrates the correct function block configuration.
Param eter Configured
Values
L_TYPE Indirect
XD_SCALE 0 to 7 psi
OUT_SCALE 0 to 16 ft
Analog
Measurement
AI
Function
Block
BKCAL_IN
PID
Function
Block
CAS_IN
OUT_D
OUT
OUT CAS_IN
BKCAL_OUT
AO
Function
Block
Fig. 4-6
Function Block Diagram for a Pressure Transmitter used in Level Measurement
4-10
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
4-9 Application Information
F
OUNDATION
TM Fieldbus
Situation #2
The transmitter in situation #2 is installed below the tank in a position where the liquid column is in the impulse line, when the tank is empty, is equivalent to 2.0 psi.
Param eter
L_TYPE
XD_SCALE
OUT_SCALE
Configured
Values
Indirect
2 to 9 psi
0 to 16 ft
16 ft
Empty Tank
0 ft
Fig. 4-7
Stuation #2 Diagram
2.0 psi measured at the transmitter
4-9-3 Application Example 3
Differential Pressure Transmitter used to Measure Flow
Situation
The liquid flow in a line is to be measured using the differential pressure across an orifice plate in the line, and the flow measurement will be used in a flow control loop. Based on the orifice specification sheet, the differential pressure transmitter was calibrated for 0 to 20 in H2 0 for a flow of 0 to 800 gal/min, and the transducer was not configured to take the square root of the differential pressure.
Solution
The table below lists the appropriate configuration settings, and the figure illustrates the correct function block configuration.
Param eter
L_TYPE
XD_SCALE
OUT_SCALE
Configured
Values
Indirect Square Root
0 to 20 in
0 to 800 gal/min
Analog
Measurement
AI
Function
Block
BKCAL_IN BKCAL_OUT
OUT_D
OUT IN
PID
Function
Block
AO
Function
Block
Fig. 4-8
Function Block Diagram for Differential Pressure Transmitter in Flow Measurement
4-11
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
4-10 Troubleshooting
4-10 Troubleshooting
Sym ptom Possible Causes Corrective Action
Mode w ill not leave OOS
1. Target mode not set. 1. Set target mode to something other than OOS.
2. Configuration error
3. Resource block
4. Schedule
Process and/or 1. Features
2. Notification
3. Status Options
Value of output 1. Linearization Type
2. Scaling
2. BLOCK_ERR will show the configuration error bit set. The following are parameters that must be set before the block is allowed out of OOS: a.
CHANNEL must be set to a valid value and cannot be left at initial value of 0.
b.
XD_SCALE.UNITS_INDX must match the units in the transducer block channel value.
c.
L_TYPE must be set to Direct, Indirect, or Indirect Square Root and cannot be left at initial value of 0.
3. The actual mode of the Resource block is OOS. See Resource Block Diagnostics for corrective action.
4. Block is not scheduled and therefore cannot execute to go to Target Mode. Schedule the block to execute.
1. FEATURES_SEL does not have Alerts enabled. Enable the Alerts bit.
2. LIM_NOTIFY is not high enough. Set equal to MAX_NOTIFY.
3. STATUS_OPTS has Propagate Fault Forw ard bit set. This should be cleared to cause an alarm to occur.
1. L_TYPE must be set to Direct, Indirect, or Indirect Square Root and cannot be left at initial value of 0.
2. Scaling parameters are set incorrectly: a.
XD_SCALE.EU0 and EU100 should match that of the transducer block channel value.
b.
OUT_SCALE.EU0 and EU100 are not set properly.
1. Limit values are outside the OUT_SCALE.EU0 and OUT_SCALE.EU100 values. Change OUT_SCALE or set values w ithin range.
Cannot set
HI_LIMIT,
HI_HI_LIMIT,
LO_LIMIT, or
. LO_LO_LIMIT
Values
1. Scaling
Tab. 4-4
Troubleshooting AI Block
4-12
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
TM Fieldbus
SECTION 5
Analog Output (AO) Function Block
CAS_IN
AO
BKCAL_OUT
OUT
CAS_IN = The remote point value from another function block.
BKCAL_OUT = The value and status required by the BKCAL_IN input of another block
OUT
to prevent reset windup and to provide bumpless transfer to closed loop control.
= The block output and status.
Fig. 5-1
Analog output function block
The Analog Output (AO) function block assigns an output value to a field device through a specified I/O channel.
The block supports mode control, signal status calculation, and simulation. Figure 5-2 illustrates the internal components of the AO function block, and Table 5-1 lists the definitions of the system parameters.
Param eters
CHANNEL
Units
None
Description
BKCAL_OUT EU of PV_SCALE The value and status required by the BKCAL_IN input of another block to prevent reset w indup and to provide bumpless transfer to closed loop control.
BLOCK_ERR None The summary of active error conditions associated w ith the block. The block errors for the Analog Output block are Simulate Active, Input
CAS_IN
Failure/Process Variable has Bad Status, Output Failure, Read
back Failed, and Out of Service.
EU of PV_SCALE The remote setpoint value from another function block.
IO_OPTS None Allow s you to select how the I/O signals are processed. The supported
I/O options for the AO function block are SP_PV Track in Man,
Increase to Close, and Use PV for BKCAL_OUT.
Defines the output that drives the field device.
MODE
OUT
None Enumerated attribute used to request and show the source of the setpoint and/or output used by the block.
EU of XD_SCALE The primary value and status calculated by the block in Auto mode. OUT may be set manually in Man mode.
PV EU of PV_SCALE The process variable used in block execution. This value is converted from READBACK to show the actuator position in the same units as the setpoint value.
PV_SCALE None The high and low scale values, the engineering units code, and the number of digits to the right of the decimal point associated with the PV.
READBACK EU of XD_SCALE The measured or implied actuator position associated w ith the OUT value.
SIMULATE EU of XD_SCALE Enables simulation and allow s you to enter an input value and status.
SP EU of PV_SCALE The target block output value (setpoint).
SP_HI_LIM EU of PV_SCALE The highest setpoint value allow ed.
SP_LO_LIM EU of PV_SCALE The low est setpoint value allow ed.
SP_RATE_DN EU of PV_SCALE per second
SP_RATE_UP EU of PV_SCALE per second
Ramp rate for dow nw ard setpoint changes. When the ramp rate is set to zero, the setpoint is used immediately.
Ramp rate for upw ard setpoint changes. When the ramp rate is set to zero, the setpoint is used immediately.
SP_WRK EU of PV_SCALE The w orking setpoint of the block. It is the result of setpoint rate-ofchange limiting. The value is converted to percent to obtain the block’s
OUT value.
Tab. 5-1
Analog Output Function Block System Parameters
5-1
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
5-1 Setting the Output
5-1 Setting the Output
To set the output for the AO block, you must first set the mode to define the manner in which the block determines its setpoint. In Manual mode the value of the output attribute (OUT) must be set manually by the user, and is independent of the setpoint. In Automatic mode,
OUT is set automatically based on the value specified by the setpoint (SP) in engineering units and the I/O options attribute (IO_OPTS).
In addition, you can limit the SP value and the rate at which a change in the SP is passed to
OUT.
In Cascade mode, the cascade input connection (CAS_IN) is used to update the SP.
The back calculation output (BKCAL_OUT) is wired to the back calculation input (BKCAL_IN) of the upstream block that provides CAS_IN.
Operator
Setpoint
RCAS_IN
This provides bumpless transfer on mode changes and windup protection in the upstream block. The OUT attribute or an analog readback value, such as valve position, is shown by the process value (PV) attribute in engineering units.
To support testing, you can enable simulation, which allows you to manually set the channel feedback. There is no alarm detection in the
AO function block.
To select the manner of processing the SP and the channel output value configure the setpoint limiting options, the tracking options, and the conversion and status calculations.
RCAS_OUT
SP_RATE_DN
SP_RATE_UP
READ_BACK
PV
BKCAL_OUT
CAS_IN
SP
HI/LO
Limit
SP
Rate
Limit
Convert and Status
Calculation
OUT
SP_LO_LIM
SP_HI_LIM
MODE
SP_WRK
PV_SCALE
IO_OPTS
SIMULATE
Shed
Mode
Access
Analog
Input
Access
Analog
Output
CHANNEL
Fig. 5-2
Analog Output Function Block Schematic
5-2
Position
Feedback
Analog
Output
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
5-2 Setpoint Selection and Limiting
TM Fieldbus
OUT (Mode in CAS)
OUT (Mode in AUTO)
OUT (Mode in MAN)
SP
SP_RATE_UP
SP_RATE_DN
1 second
Fig. 5-3
Analog Output Function Block Timing Diagram
5-2 Setpoint Selection and Limiting
To select the source of the SP value use the
MODE attribute. In Automatic (Auto) mode, the local, manually-entered SP is used. In Cascade
(Cas) mode, the SP comes from another block through the CAS_IN input connector. In
RemoteCascade (RCas) mode, the SP comes from a host computer that writes to RCAS_IN.
The range and units of the SP are defined by the PV_SCALE attribute.
In Manual (Man) mode the SP automatically tracks the PV value when you select the SP-
PV Track in Man I/O option. The SP value is set equal to the PV value when the block is in
1 second
Time manual mode, and is enabled (True) as a default. You can disable this option in Man or
O/S mode only.
The SP value is limited to the range defined by the setpoint high limit attribute (SP_HI_LIM) and the setpoint low limit attribute (SP_LO_LIM).
In Auto mode, the rate at which a change in the
SP is passed to OUT is limited by the values of the setpoint upward rate limit attribute
(SP_RATE_UP) and the setpoint downward rate limit attribute (SP_RATE_DN). A limit of zero prevents rate limiting, even in Auto mode.
5-3 Conversion and Status Calculation
The working setpoint (SP_WRK) is the setpoint value after limiting. You can choose to reverse the conversion range, which will reverse the range of PV_SCALE to calculate the OUT attribute, by selecting the Increase to Close I/
O option. This will invert the OUT value with respect to the setpoint based on the
PV_SCALE and XD_SCALE.
In Auto mode, the converted SP value is stored in the OUT attribute. In Man mode, the OUT attribute is set manually, and is used to set the analog output defined by the CHANNEL parameter.
You can access the actuator position
5-3
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
5-4 Simulation associated with the output channel through the
READBACK parameter (in OUT units) and in the PV attribute (in engineering units). If the actuator does not support position feedback, the PV and READBACK values are based on the OUT attribute.
The working setpoint (SP_WRK) is the value normally used for the BKCAL_OUT attribute.
However, for those cases where the
READBACK signal directly (linearly) reflects
5-4 Simulation
When simulation is enabled, the last value of
OUT is maintained and reflected in the field value of the SIMULATE attribute. In this case, the PV and READBACK values and statuses are based on the SIMULATE value and the status that you enter.
5-5 Action on Fault Detection
To define the state to which you wish the valve to enter when the CAS_IN input detects a bad status and the block is in CAS mode, configure the following parameters:
• FSTATE_TIME: The length of time that the
AO block will wait to position the OUT value to the FSTATE_VAL value upon the detection of a fault condition. When the block has a target mode of CAS, a fault condition will be detected if the CAS_IN has a BAD status or an Initiate Fault State substatus is received from the upstream block.
the OUT channel, you can choose to allow the
PV to be used for BKCAL_OUT by selecting the Use PV for BKCAL_OUT I/O option.
NOTE: SP_PV Track in Man, Increase to
Close, and Use PV for BKCAL_OUT are the only I/O options that the AO block supports. You can set I/O options in Manual or Out of Ser-
vice mode only.
• FSTATE_VAL: The value to which the OUT value transitions after FSTATE_TIME elapses and the fault condition has not cleared. You can configure the channel to hold the value at the start of the failure action condition or to go to the failure action value (FAIL_ACTION_VAL).
5-4
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
5-6 Block Errors
F
OUNDATION
TM Fieldbus
•
•
5-6 Block Errors
The following conditions are reported in the
BLOCK_ERR attribute:
Input failure/process variable has Bad
status – The hardware is bad, the Device
Signal Tag (DST) does not exist, or a BAD status is being simulated.
Out of service – The block is in Out of
Service (O/S) mode.
• Output failure – The output hardware is bad.
• Readback failed – The readback failed.
• Simulate active – Simulation is enabled and the block is using a simulated value in its execution.
5-7 Modes
The Analog Output function block supports the following modes:
• Manual (Man) – You can manually set the output to the I/O channel through the OUT attribute.
This mode is used primarily for maintenance and troubleshooting.
• Automatic (Auto) – The block output (OUT) reflects the target operating point specified by the setpoint (SP) attribute.
• Cascade (Cas) – The SP attribute is set by another function block through a connection to
CAS_IN. The SP value is used to set the OUT attribute automatically.
• RemoteCascade (RCas) – The SP is set by a host computer by writing to the RCAS_IN parameter. The SP value is used to set the OUT attribute automatically.
• Out of Service (O/S) – The block is not processed. The output channel is maintained at the last value and the status of OUT is set to Bad: Out of Service. The BLOCK_ERR attribute shows
Out of Service.
• Initialization Manual (Iman) – The path to the output hardware is broken and the output will remain at the last position.
• Local Override (LO) – The output of the block is not responding to OUT because the resource block has been placed into LO mode or fault state action is active.
The target mode of the block may be restricted to one or more of the following modes: Man, Auto,
Cas, RCas, or O/S.
5-8 Status Handling
Output or readback fault detection are reflected in the status of PV, OUT, and BKCAL_OUT. A limited SP condition is reflected in the
BKCAL_OUT status. When simulation is enabled through the SIMULATE attribute, you can set the value and status for PV and
READBACK.
When the block is in Cas mode and the
CAS_IN input goes bad, the block sheds mode to the next permitted mode.
5-5
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
5-6
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
TM Fieldbus
SECTION 6
Input Selector (ISEL) Function Block
IN (1-4) = Input used in the selection algorithm.
DISABLE (1-4) = Discrete input used to enable or disable the associated input channel.
OP_SELECT = Input used to override algorithm.
TRK_VAL = The value after scaling applied to OUT in Local Override mode.
SELECTED = The selected channel number.
OUT
Fig. 6-1
Input Selector (ISEL) Function Block
= The block output and status.
The Input Selector (ISEL) function block can be used to select the first good, Hot Backup, maximum, minimum, or average of as many as four input values and place it at the output.
The block supports signal status propagation.
There is no process alarm detection in the Input Selector function block.
Figure 5-2 illustrates the internal components of the ISEL function block. Table 5-1 lists the
ISEL block parameters and their descriptions, units of measure, and index numbers.
Param eter Index
Num ber
4
Units Description
ALERT_KEY
BLOCK_ALM
BLOCK_ERR
DISABLE_1
DISABLE_2
24
6
15
16
None
None
None
None
None
The identification number of the plant unit. This information may be used in the host for sorting alarms, etc.
The block alarm is used for all configuration, hardw are, connection failure, or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active w ill set the Active status in the Status parameter. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported w ithout clearing the
Active status, if the subcode has changed.
This parameter reflects the error status associated w ith the hardw are or softw are components associated w ith a block. It is a bit string, so that multiple errors may be show n.
A Connection from another block that disables the associated input from the selection.
A Connection from another block that disables the associated input from the selection.
Tab. 6-1
Input Selector Function Block System Parameters
6-1
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
6 Input Selector (ISEL) Function Block
Parameter
DISABLE_3
DISABLE_4
GRANT_DENY
IN_1
IN_2
IN_3
IN_4
MIN_GOOD
MODE_BLK
OP_SELECT
OUT
OUT_UNITS
SELECTED
SELECT_TYPE
STATUS_OPTS
STRATEGY
ST_REV
TAG_DESC
UPDATE_EVT
21
19
10
3
22
7
8
1
11
12
13
14
20
5
Index
Number
17
18
9
2
23
Units Description
None
None
None
A Connection from another block that disables the associated input from the selection.
A Connection from another block that disables the associated input from the selection.
Options for controlling access of host computers and local control panels to operating, tuning, and alarm parameters of the block. Not used by device.
Determined by source
Determined by source
Determined by source
Determined by source
None
None
None
EU of IN
None
None
None
None
None
None
None
None
The connection input from another block. One of the inputs to be selected from.
The connection input from another block. One of the inputs to be selected from.
The connection input from another block. One of the inputs to be selected from.
The connection input from another block. One of the inputs to be selected from.
The minimum number of good inputs
The actual, target, permitted, and normal modes of the block.
Target: The mode to “go to”
Actual: The mode the “block is currently in”
Permitted: Allow ed modes that target may take on
Normal: Most common mode for target
Overrides the algorithm to select 1 of the 4 inputs regardless of the selection type.
The block output value and status.
The engineering units of the output. Typically, all inputs have the same units and the value is also the same.
The selected input number (1–4).
Specifies selection method (see Block Execution)
Allow s selection of options for status handling and processing. The supported status option for the PID block is Target to Manual if Bad IN.
The strategy field can be used to identify grouping of blocks. This data is not checked or processed by the block.
The revision level of the static data associated w ith the function block. The revision value w ill be incremented each time a static parameter value in the block is changed.
The user description of the intended application of the block.
This alert is generated by any change to the static data.
Tab. 6-1 (cont’d)
Input Selector Function Block System Parameters
6-2
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
6 Input Selector (ISEL) Function Block
TM Fieldbus
IN_1
IN_2
IN_3
IN_4
Selection
Algorithm
DISABLE_1
DISABLE_2
DISABLE_3
DISABLE_4
OP_SELECT
Fig. 6-2
Input Selector Function Block Schematic
AUTO
MAN
SEL_TYPE
MIN_GOOD
OUT
SELECTED
6-1 Block Errors
Table 5-2 lists conditions reported in the
BLOCK_ERR parameter.
Conditions in italics are inactive for the ISEL block and are listed for reference only.
Condition
Num ber
Condition Nam e and Description
0 Other: The output has a quality of uncertain.
1
2
3
Block Configuration Error
Link Configuration Error
Simulate Active
Local Override: The actual mode is LO.
Device Fault State Set
6
7
4
5
8
9
10
11
12
13
Device Needs Maintenance Soon
Input Failure/Process Variable has Bad Status:
One of the inputs is Bad or not connected.
Output Failure: The output has the quality of Bad.
Mem ory Failure: A memory failure has occurred in
FLASH, RAM, or EEROM memory.
Lost Static Data
Lost NV Data
Readback Check Failed
Device Needs Maintenance Now
14
15
Tab. 6-2
Block Error Conditions
Pow er Up: The device w as just pow ered-up.
Out of Service: The actual mode is out of service.
6-3
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
6-2 Modes
6-2 Modes
The ISEL function block supports three modes of operation as defined by the MODE_BLK parameter:
• Manual (Man) The block output (OUT) may be set manually.
• Automatic (Auto) OUT reflects the selected value.
• Out of Service (O/S) The block is not processed. The BLOCK_ERR parameter shows Out of Service. In this mode, changes caNn be made to all configurable parameters. The target mode of a block may be restricted to one or more of the supported modes.
6-3 Alarm Detection
A block alarm will be generated whenever the
BLOCK_ERR has an error bit set. The types of block error for the ISEL block are defined above.
Alarms are grouped into five levels of priority:
Priority
0
1
2
03. Jul
Aug 15
Tab. 5-3
Alarm Priorities
Priority Description Number
The priority of an alarm condition changes to 0 after the condition that caused the alarm is corrected.
An alarm condition w ith a priority of 1 is recognized by the system, but is not reported to the operator.
An alarm condition w ith a priority of 2 is reported to the operator, but does not require operator attention
(such as diagnostics and system alerts).
Alarm conditions of priority 3 to 7 are advisory alarms of increasing priority.
Alarm conditions of priority 8 to 15 are critical alarms of increasing priority.
6-4 Block Execution
The ISEL function block reads the values and statuses of as many as four inputs. To specify which of the six available methods (algorithms) is used to select the output, configure the selector type parameter (SEL_TYPE) as follows:
• max selects the maximum value of the inputs.
• min selects the minimum value of the inputs.
• avg calculates the average value of the inputs.
• mid calculates the middle of three inputs or the average of the middle two inputs if four inputs are defined.
• 1st Good selects the first available good input.
• Hot Backup latches on the selected input and continues to use it until it is bad.
If DISABLE_N is active, the associated input is not used in the selection algorithm.
If OP_SELECT is set to a value between 1 and
4, the selection type logic is overridden and the output value and status is set to the value
6-4
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
6-5 Status Handling
F
OUNDATION
TM Fieldbus and status of the input selected by
OP_SELECT.
SELECTED will have the number of the selected input unless the SEL_TYPE is average, in which case it will have the number of inputs used to calculate its value.
6-5 Status Handling
In Auto mode, OUT reflects the value and status quality of the selected input. If the number of inputs with Good status is less than
MIN_GOOD, the output status will be Bad.
In Man mode, the OUT status high and low limits are set to indicate that the value is a constant and the OUT status is always Good.
In the STATUS_OPTS parameter, the following options can be selected from to control the status handling:
6-6 Application Information
The ISEL function block can be used to select the maximum temperature input from four inputs and send it to a PID function block to control a
• Use Uncertain as Good: sets the OUT status quality to Good when the selected input status is Uncertain.
• Uncertain if in Manual mode: The status of the Output is set to Uncertain when the mode is set to manual.
The instrument must be in Manual or Out of Service mode to set the status option.
process water chiller (see fig. 5-3) or it can use the block to calculate the average temperature of the four inputs (see fig. 5-4).
IN1 = 126 °F
IN2 = 104 °F
IN3 = 112 °F
IN4 = 130 °F
Input Selector
(ISEL) Function
Block
OUT = 130 °F
To Another
Function Block
SEL_TYPE = max
Fig. 6-3
Input Selector Function Block Application Example (SEL_TYPE = max).
6-5
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
6-6 Application Information
IN1 = 126 °F
IN2 = 104 °F
IN3 = 112 °F
IN4 = 130 °F
Input Selector
(ISEL) Function
Block
OUT = 118 °F
To Another
Function Block
SEL_TYPE = avg
Fig. 6-4
Input Selector Function Block Application Example (SEL_TYPE = avg.).
IN1 = 126 °F
IN2 = 104 °F
IN3 = 112 °F
IN4 = 130 °F
Input Selector
(ISEL) Function
Block
SEL_TYPE = Hot Backup
Fig. 6-5
Input Selector Function Block Application Example (SEL_TYPE = Hot Backup).
IN1 IN2 Out Selected
Time Value Status Value Status Value Status Value Status
T
T
1
T
2
0
Good
Bad
Good
20
20
20
Good
Good
Good
21
21
21
Good
Good
Good
20
21
21
Good
Good
Good
1
2
2
Tab. 6-4
Input Selector Function Blocks
6-6
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
6-7 Troubleshooting
F
OUNDATION
TM Fieldbus
6-7 Troubleshooting
Symptom
Mode w ill not leave OOS
Possible Causes Corrective Action
1. Target mode not set.
1. Set target mode to something other than OOS.
Status of output is bad.
Block alarms w ill not w ork
2. Configuration error 2. BLOCK_ERR will show the configuration error bit set. SELECT_TYPE must be set to a valid value and cannot be left at 0.
3. Resource block 3. The actual mode of the Resource block is OOS. See Resource Block Diagnostics for corrective action.
4. Schedule 4. Block is not scheduled and therefore cannot execute to go to Target Mode.
Schedule the block to execute.
1. Inputs
2. OP selected
3. Min good
1. All inputs have Bad status.
2. OP_SELECT is not set to 0 (or it is linked to an input that is not 0), and it points to an input that is Bad.
3. The number of Good inputs is less than MIN_GOOD.
1. Features
2. Notification
1. Status Options
1. FEATURES_SEL does not have Alerts enabled. Enable Alerts bit..
2. LIM_NOTIFY is not high enough. Set equal to MAX_NOTIFY.
1. STATUS_OPTS has Propagate Fault Forw ard bit set. This should be cleared to cause an alarm to occur.
Tab. 6-5
Troubleshooting ISEL Block
6-7
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
6-8
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
TM Fieldbus
SECTION 7
Arithmetic (ARTHM) Function Block
IN
IN_LO
IN_1
IN_2
IN_3
ARTHM
OUT
The Arithmetic function block provides the ability to configure a range extension function for a primary input and applies the nine (9) different arithmetic types as compensation to or augmentation of the range extended input. All operations are selected by parameter and input connection.
The nine (9) arithmetic functions are Flow
Compensation Linear, Flow Compensation
Square Root, Flow Compensation
Approximate, BTU Flow, Traditional Multiply and Divide, Average, Summer, Fourth Order
Polynomial, and Simple HTG Compensate
Level.
This Arithmetic function block supports mode control (Auto, Manual, Out of Service). There is no standard alarm detection in this block.
7-1
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
7 Arithmetic (ARTHM) Function Block
Index
Number
4
29
30
6
27
28
32
22
24
26
12
31
21
23
25
36
14
16
17
18
15
13
5
8
33
Parameter
ALERT_KEY
ARITH_TYPE
BAL_TIME
BIAS
BIAS_IN_1
BIAS_IN_2
BIAS_IN_3
BLOCK_ALM
BLOCK_ERR
COMP_HI_LIM
COMP_LO_LIM
GAIN
GAIN_IN_1
GAIN_IN_2
GAIN_IN_3
GRANT_DENY
IN
IN_1
IN_2
IN_3
IN_LO
INPUT_OPTS
MODE_BLK
OUT
OUT_HI_LIM
Tab. 7-1
Arithmetic Block Parameters
Units Description
None
None
Seconds
None
None
None
None
None
None
The identification number of the plant unit. This information may be used in the host fro sorting alarms, etc.
The set of 9 arithmetic functions applied as compensation to or augmentation of the range extended input.
Specifies the time for a block value to match an input, output, or calculated value or the time for dissipation of the internal balancing bias.
The bias value
The bias value for IN_1.
The bias value for IN_2.
The bias value for IN_3.
This block alarm is used for all configuration, hardware, connection failure, or system problems in the block. The cause of the alert is entered in the subcode field.The first alert to become active will set the active status in the status parameter. As soon as the Unreported status is cleared by the alert reporting task, and other block alert may be reported without clearing the Active status, if the subcode has changed.
The summary of active error conditions associated with the block. The possible block errors are Block configuration error, Simulate active, Local override, Input failure/process variable has Bad status, Output failure,
Readback failed, Out of service, and Other. Each function block reports none
EU of PV
EU of PV
None
None
None
None or a subset of these error conditions.
Determines the high limit of the compensation input.
Determines the low limit of the compensation input.
The proportional gain (multiplier) value.
The proportional gain (multiplier) value for IN_1
The proportional gain (multiplier) value for IN_2
The proportional gain (multiplier) value for IN_3
None Options for controlling access of host computers and local control panels to operating, tuning, and alarm parameters of the block. Not used by the device.
Determined by source or The analog input value and status. The number of inputs is an extensible
EU of PV_SCALE parameter in some function blocks.
Determined by supplying The first analog input value and status.
block or source.
Determined by supplying The second analog input value and status.
block or source.
Determined by supplying The third analog input value and status.
block or source.
None
None
The value used for the input whenever IN is below range.
Sets the options for using IN, IN_LO, IN_1, IN_2 and IN_3 when any are either
Bad or Uncertain.
None The mode record of the block. MODE contains the actual, target, permitted, and normal modes. In some function blocks, this parameter is used to request and show the source of the setpoint, the source of the output, and/or the block operating state.
EU of OUT_SCALE or The analog output value and status. The number of outputs is an extensible
Percent or EU of IN parameter in some blocks.
EU of OUT_SCALE or The maximum output value allowed.
Supplied by IN
7-2
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
F
OUNDATION
7 Arithmetic (ARTHM) Function Block
TM Fieldbus
Index
Number
34
11
9
7
10
19
20
3
1
2
35
Parameter Units Description
OUT_LO_LIM EU of OUT_RANGE or The minimum output value allowed.
OUT_RANGE
PRE_OUT
PV
PV_SCALE
Supplied by IN
None
EU of OUT
Range of the output
The pre-trip limit from SP or zero.
EU of OUT or EU of The process variable used in block execution and alarm limit detection.
PV_SCALE
None
RANGE_HI
RANGE_LO
STRATEGY
ST_REV
None
None
None
None
The high and low scale values, engineering units code, and number of digits to the right of the decimal point associated with OUT.
The high limit for IN.
The low limit for IN. If IN is less than RANGE_LO, then IN_LO is used.
The strategy field can be used to identify grouping of blocks. This data is not checked or processed by the block.
The revision level of the static data associated with the function block. The revision value will be incremented each time a static parameter value in the block is changed.
TAG_DESC
UPDATE_EVT
None
None
The user description of the intended application of the block.
This alert is generated by any changes to the static data.
Tab. 7-1 (cont’d)
Arithmetic Block Parameters
Fig. 7-2
Arithmetic Function Block Schematic
7-3
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
7-1 Block Errors
7-1 Block Errors
Table 6-2 lists conditions reported in the
BLOCK_ERR parameter.
Conditions in italics are inactive for the ARTHM block and are listed here only for your reference.
8
9
10
11
12
13
14
15
Condition
Number
0
1
4
5
2
3
6
7
Condition Name and Description
Other: The output has a quality of uncertain.
Block Configuration Error: Select type is not configured
Link Configuration Error
Simulate Active
Local Override
Device Fault State Set
Device Needs Maintenance Soon
Input Failure/Process Variable has Bad Status: One of the inputs is Bad or not connected.
Output Failure
Memory Failure
Lost Static Data
Lost NV Data
Readback Check Failed
Device Needs Maintenance Now
Power Up: The device was just powered-up.
Out of Service: The actual mode is out of service.
Tab. 7-2
BLOCK_ERR parameters
7-2 Modes
The ARTHM block supports the following modes:
• Manual (Man) – The block output (OUT) may be set manually.
• Automatic (Auto) – OUT reflects the analog input measurement or the simulated value when simulation is enabled.
• Out of Service (O/S) – The block is not processed. FIELD_VAL and PV are not updated and the OUT status is set to Bad:
Out of Service. The BLOCK_ERR parameter shows Out of Service. In this mode, you can make changes to all configurable parameters.
The target mode of a block bay be restricted to one or more of the supported modes.
7-4
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
7-3 Alarm Detection
F
OUNDATION
TM Fieldbus
7-3 Alarm Detection
A block alarm will be generated whenever the
BLOCK_ERR has anerror bit set. The types of block error for the ARTHM block aredefined above.
Alarms are grouped into five levels of priority:
Priority
Number
0
Priority Description
1
The priority of an alarm condition changes to 0 after the condition that caused the alarm is corrected.
An alarm condition with a priority of 1 is recognized by the system, but is
2 not reported to the operator.
An alarm condition with a priority of 2 is reported to the operator, but does
3-7 not require operator attention (such as diagnostics and system alerts).
Alarm conditions of priority 3 to 7 are advisory alarms of increasing priority.
8-15 Alarm conditions of priority 8 to 15 are critical alarms of increasing priority.
Tab. 7-3
Alarm Level Priorities
7-4 Block Execution
The Arithmetic function block provides range extension and compensation through nine (9) arithmetic types.
There are two inputs (IN and IN_LO) used in calculating PV. PV is then combined with up to three inputs (IN_1, IN_2, and IN_3) through the user selected compensation function
(ARITH_TYPE) to calculate the value of func. A gain is applied to func and then a bias is added to get the value PRE_OUT. In AUTO,
PRE_OUT is used for OUT.
Range Extension and Calculation of PV
When both IN and IN_LO are usable, the following formula is applied to calculate range extension for PV:
Compensation Input Calculations
For each of the inputs IN_1, IN_3, IN_4 there is a gain and bias. The compensation terms
(t) are calculated as follows:
PV = G * IN + (1 - G) * IN_LO
(G has a range from 0 to 1, for IN from
RANGE_LO to RANGE_HI.)
• When IN_(k) is usable:
t(k) = GAIN_IN(k) * (BIAS_IN(k) + IN_(k))
• When IN_(k) is not usable, then t(k) gets the value of the last t(k) computed with a usable input.
7-5
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
7-5 Status Handling
7-5 Status Handling
IN_x Use Bad
IN_x Use Uncertain
IN_LO Use Uncertain
IN Use Uncertain
For complete descriptions of supported input options, refer to the Option Bitstring Parameters topic.
7-6 Application Information
The Arithmetic function block can be used to calculate tank level changes based on greatly changing temperature conditions in devices that depend on the physical properties of the fluid.
For example, a differential pressure cell’s analog input can be scaled initially to provide a 4-
20 mA signal for 0-100% of level indication. As the temperature of the system rises, the density of the fluid decreases. For a system that requires accurate level indication at widely ranging temperature, changing density proves inconvenient.
The Arithmetic function block allows for the automatic compensation of this change by incorporating gain and bias adjustments to the temperature signal. It then applies both the compensated temperature signal and the level signal to a characteristic system equation. The result is a level that is a true indication of fluid in the vessel.
Different fluids over the same temperature range have different effects on level due to their thermal expansion coefficients. Vessel geometry also plays a major role. As the height of the vessel increases, the effect of thermal expansion becomes more apparent. The following figure shows the relative temperature effects on a level signal.
Fig. 7-3
Relative Temperature Effects on Level
7-6
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
7-6 Application Information
F
OUNDATION
TM Fieldbus
The calculation is done by applying the level signal to the IN connector, the liquid temperature to the IN_1 connector, and the ambient air temperature to the IN_2 connector.
Select the Arithmetic type (ARITH_TYPE) of
Flow Compensation - Linear.
This allows a ratio to be set up that increases the level indication at block output for an increase in the tank temperature relative to ambient temperature.
Fig. 7-4
Arithmetic Function Block Diagram Example
This application can be applied to very large storage tanks whose contents are subject to thermal expansion and contraction during seasonal changes in temperature.
7-7
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
7-7 Advanced Topics
7-7 Advanced Topics
Arithmetic Types
The parameter ARITH_TYPE determines how
PV and the compensation terms (t) are combined. User may select from nine (9) commonly used math functions, depicted below.
COMP_HI and COMP_LO are compensation limits.
If there is a divide by zero and the numerator is positive, f is set to COMP_HI; if the numerator is negative, then f is set to COMP_LO.
The square root of a negative value will equal the negative of the square root of the absolute value. Imaginary roots are not supported.
If there is a divide by zero and numerator is positive, f will be limited to COMP_HI; if the numerator is negative, f will be limited to
COMP_LO. Compensation inputs which are not usable are not included in the calculation.
PV is always included.
7-8
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
7-8 Troubleshooting
F
OUNDATION
TM Fieldbus
7-8 TROUBLESHOOTING
Refer to Table 6-4 to troubleshoot any problems that you encounter.
Symptom Possible Causes Corrective Action
Model will not leave OOS Target model not set Set target mode to something other than OOS
Configuration error BLOCK_ERR will show the configuration error set. ARITH_TYPE must be set to a
Resource Block
Schedule valid value and cannot be left at 0.
The actual mode of the Resource block is OOS. See Resource block diagnostics for corrective action.
Block is not scheduled and therefore cannot execute to go to the target mode.
Status of outputs is BAD Inputs
Block alarms will not work Features
Notification
Status Options
Typically, BLOCK_ERR will show “Power-Up” for all blocks that are not scheduled.
Schedule the block to execute.
Input has BAD status.
FEATURES_SEL does not have Alerts enabled. Enable the Alert bit.
LIM_NOTIFY is not high enough. Set equal to MAX_NOTIFY.
STATUS_OPTS has the Propagate Fault Forward bit set. This must be cleared to cause the alarm to occur.
Tab. 7-4
Troubleshooting
7-9
F
OUNDATION
TM Fieldbus
F
OUNDATION
TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
7-10
Foundation TM
ETC01184
10/2003
Fieldbus Communication Instruction Manual
Foundation TM Fieldbus
SECTION 8
Proportional / Integral / Derivative (PID) Function Block
BKCAL_IN = The analog input value and status from another block’s
BKCAL_OUT output that is used forbackward output tracking for bumpless transfer and to pass limit status.
CAS_IN = The remote setpoint value from another function block.
FF_VAL = The feedforward control input value and status.
IN = The connection for the process variable from another function block.
TRK_IN_D = Initiates the external tracking function.
TRK_VAL = The value after scaling applied to OUT in Local
Override mode.
BKCAL_OUT= The value and status required by the BKCAL_IN input of another function block to prevent reset windup and to provide bumpless transfer to closed
OUT = loop control.
The block output and status.
The PID function block combines all of the necessary logic to perform proportional / integral / derivative (PID) control. The block supports mode control, signal scaling and limiting, feedforward control, override tracking, alarm limit detection, and signal status propagation.
The block supports two forms of the PID equation: Standard and Series. Choose the appropriate equation using the FORM parameter. The Standard ISA PID equation is the default selection.
Standard Out = GAIN x e x
1 +
τ r s
1
+ 1
+
α x
τ d s
τ d s + 1
+ F
Series Out = GAIN x e x
1 +
1
τ r s
+
α x
τ d s + 1
τ d s + 1
+ F t d a:
:
F: e:
Where
GAIN: Proportional gain value.
t r
: s:
Integral action time constant (RESET parameter) in seconds.
Laplace operator
Derivative action time constant (RATE parameter).
Fixed smoothing factor of 0.1 applied to RATE.
Feedforward control contribution from the feedforward input (FF_VAL parameter).
Error between setpoint and process variable.
8-1
Foundation TM Fieldbus
Foundation TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
8 PID Function Block
To further customize the block for use in an application, it is possible to configure filtering, feedforward inputs, tracking inputs, setpoint and output limiting, PID equation structures, and block output action.
Table 8-1 lists the PID block parameters and their descriptions, units of measure, and index numbers, and fig. 8-1 illustrates the internal components of the PID function block.
Parameter
ACK_OPTION
ALARM_HYS
ALARM_SUM
ALERT_KEY
ALG_TYPE
BAL_TIME
BIAS
BKCAL_HYS
BKCAL_IN
BKCAL_OUT
BLOCK_ALM
BLOCK_ERR
BYPASS
CAS_IN
CONTROL_OPTS
DV_HI_ALM
DV_HI_LIM
DV_HI_PRI
DV_LO_ALM
DV_LO_LIM
DV_LO_PRI
ERROR
FF_ENABLE
FF_GAIN
Index
Number
46
47
45
4
74
25
66
30
27
31
44
6
17
18
13
64
57
56
65
59
58
67
70
42
Units
Description
None
Percent
None
Used to set auto acknow ledgment of alarms.
The amount the alarm value must return to w ithin the alarm limit before the associated active alarm condition clears.
The summary alarm is used for all process alarms in the block. The cause of the alert is entered in the subcode field. The first alert to become active w ill set the Active status in the Status parameter. As soon as the
Unreported status is cleared by the alert reporting task, another block alert may be reported w ithout clearing the
Active status, if the subcode has changed.
The identification number of the plant unit. This information may be used in the host for sorting alarms, etc. None
None
Seconds
Selects filtering algorithm as Backw ard or Bilinear.
The specified time for the internal w orking value of bias to return to the operator set bias. Also used to specify the time constant at w hich the integral term w ill move to obtain balance w hen the output is limited and the mode is AUTO, CAS, or RCAS.
EU of OUT_SCALE The bias value used to calculate output for a PD type controller.
Percent The amount the output value must change aw ay from the its output limit before limit status is turned off.
EU of OUT_SCALE The analog input value and status from another block’s BKCAL_OUT output that is used for backw ard output tracking for bumpless transfer and to pass limit status.
EU of PV_SCALE The value and status required by the BKCAL_IN input of another block to prevent reset w indup and to provide bumpless transfer of closed loop control.
None
None
The block alarm is used for all configuration, hardw are, connection failure, or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active w ill set the active status in the status parameter. As soon as the Unreported status is cleared by the alert reporting task, and other block alert may be reported w ithout clearing the Active status, if the subcode has changed.
This parameter reflects the error status associated w ith the hardw are or softw are components associated w ith a block. It is a bit string so that multiple errors may be show n.
None Used to override the calculation of the block. When enabled, the SP is sent directly to the output.
EU of PV_SCALE The remote setpoint value from another block.
None
None
Allow s definition of control strategy options. The supported control options for the PID block are Track enable,
Track in Manual, SP-PV Track in Man, SP-PV Track in LO or IMAN, Use PV for BKCAL OUT, and Direct Acting
The DV HI alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the alarm.
EU of PV_SCALE The setting for the alarm limit used to detect the deviation high alarm condition.
None The priority of the deviation high alarm.
None The DV LO alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the alarm.
EU of PV_SCALE The setting for the alarm limit use to detect the deviation low alarm condition.
None The priority of the deviation low alarm.
EU of PV_SCALE The error (SP-PV) used to determine the control action.
None
None
Enables the use of feedforw ard calculations
The feedforw ard gain value. FF_VAL is multiplied by FF_GAIN before it is added to the calculated control output.
FF_SCALE
FF_VAL
GAIN
GRANT_DENY
HI_ALM
HI_HI_ALM
41
40
23
12
61
60
None The high and low scale values, engineering units code, and number of digits to the right of the decimal point associated w ith the feedforw ard value (FF_VAL).
EU of FF_SCALE The feedforw ard control input value and status.
None The proportional gain value. This value cannot = 0.
None
None
None
Options for controlling access of host computers and local control panels to operating, tuning, and alarm parameters of the block. Not used by the device.
The HI alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the alarm.
The HI HI alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the alarm.
HI_HI-LIM
HI_HI_PRI
HI_LIM
HI_PRI
IN
LO_ALM
49
48
51
50
15
62
EU of PV_SCALE The setting for the alarm limit used to detect the HI HI alarm condition.
None The priority of the HI HI Alarm.
EU of PV_SCALE The setting for the alarm limit used to detect the HI alarm condition.
None The priority of the HI alarm.
EU of PV_SCALE The connection for the PV input from another block.
None The LO alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the alarm.
Tab. 8-1
PID Function Block System Parameters
8-2
Foundation TM
ETC01184
10/2003
Fieldbus Communication Instruction Manual
Foundation TM Fieldbus
8 PID Function Block
LO_LIM
LO_LO_ALM
LO_LO_LIM
LO_LO_PRI
LO_PRI
MATH_FORM
MODE_BLK
OUT
Parameter
OUT_HI_LIM
OUT-LO_LIM
OUT_SCALE
PV
PV_FTIME
PV_SCALE
RATE
RCAS_IN
RCAS_OUT
RESET
ROUT_IN
ROUT_OUT
SHED_OPT
SP
SP_FTIME
SP_HI_LIM
SP_LO_LIM
SP_RATE_DN
SP-RATE_UP
SP_WORK
STATUS_OPTS
STRATEGY
ST_REV
STRUCTURE. CONFIG
TAG_DESC
TRK_IN_D
TRK_SCALE
TRK_VAL
UBETA
UGAMMA
UPDATE_EVT
34
8
69
21
22
19
Index
Number
53
63
55
54
52
73
5
9
28
29
11
7
16
10
26
32
35
24
Units
Description
EU of PV_SCALE The setting for the alarm limit used to detect the LO alarm condition.
None The LO LO alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the alarm.
EU of PV_SCALE The setting for the alarm limit used to detect the LO LO alarm condition.
None The priority of the LO LO alarm.
None
None
The priority of the LO alarm.
Selects equation form (series or standard).
The actual, target, permitted, and normal modes of the block.
None
Target: The mode to “go to”
Actual: The mode the “block is currently in” Permitted: Allow ed modes that target may take on Normal: Most common mode for target.
EU of OUT SCALE The block input value and status.
EU of OUT_SCALE The maximum output value allow ed.
EU of OUT_SCALE The minimum output value allow ed
None The high and low scale values, engineering units code, and number of digits to the right of the decimal point associated w ith OUT.
EU of PV_SCALE The process variable used in block execution.
Seconds The time constant of the first-order PV filter. It is the time required for a 63 percent change in the IN value.
None The high and low scale values, engineering units code, and number of digits to the right of the decimal point associated w ith PV.
Seconds The derivative action time constant.
EU of PV_SCALE Target setpoint and status that is provided by a supervisory host. Used w hen mode is RCAS.
EU of PV_SCALE Block setpoint and status after ramping, filtering, and limiting that is provided to a supervisory host for back calculation to allow action to be taken under limiting conditions or mode change. Used w hen mode is RCAS.
Seconds per repeat The integral action time constant.
33
36
20
68
14
3
1
75
2
38
37
39
72
71
43
EU of OUT_SCALE Target output and status that is provided by a supervisory host. Used w hen mode is ROUT.
EU of OUT_SCALE Block output that is provided to a supervisory host for a back calculation to allow action to be taken under limiting conditions or mode change.
Used w hen mode is RCAS.
None Defines action to be taken on remote control device timeout.
EU of PV_SCALE The target block setpoint value. It is the result of setpoint limiting and setpoint rate of change limiting.
Seconds The time constant of the first-order SP filter. It is the time required for a 63 percent change in the IN value.
EU of PV_SCALE The highest SP value allow ed.
EU of PV_SCALE The low est SP value allow ed.
EU of PV_SCALE per second
EU of PV_SCALE per second
Ramp rate for dow nw ard SP changes. When the ramp rate is set to zero, the SP is used immediately.
Ramp rate for upw ard SP changes. When the ramp rate is set to zero, the SP is used immediately.
EU of PV_SCALE The w orking setpoint of the block after limiting and filtering is applied.
None
None
None
Allow s selection of options for status handling and processing. The supported status option for the PID block is
Target to Manual if Bad IN.
The strategy field can be used to identify grouping of blocks. This data is not checked or processed by the block.
The revision level of the static data associated w ith the function block. The revision value w ill be incremented each time a static parameter value in the block is changed.
Defines PID equation structure to apply controller action. None
None
None
None
The user description of the intended application of the block.
Discrete input that initiates external tracking.
The high and low scale values, engineering units code, and number of digits to the right of the decimal point associated w ith the external tracking value (TRK_VAL).
The value (after scaling from TRK_SCALE to OUT_SCALE) applied to OUT in LO mode.
EU of
TRK SCALE
Percent
Percent
None
Used to set disturbance rejection vs. tracking response action for a 2.0 degree of freedom PID.
Used to set disturbance rejection vs. tracking response action for a 2.0 degree of freedom PID.
This alert is generated by any changes to the static data.
Tab. 8-1 (cont’d)
PID Function Block System Parameters
8-3
Foundation TM Fieldbus
Foundation TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
8-1 Setpoint Selection And Limiting
FF_GAIN
FF_SCALE
FF_VAL
BKCAL_IN
MODE
TRK_IN_D
RCAS_OUT
CAS_IN
RCAS_IN
Setpoint
Limiting
And
Filtering
Operator
Setpoint
SP_HI_LIM
SP_LO_LIM
SP_RATE_DN
SP_RATE_UP
SP_FTIME
IN
Scaling and
Filtering
Feedforward
Calculation
TRK_VAL
PV_SCALE
PV_FTIME
Convert
PID
Equation
GAIN
RATE
RESET
Alarm
Detection
HI_HI_LIM
HI_LIM
DV_HI_LIM
DV_LO_LIM
LO_LIM
LO_LO_LIM
TRK_SCALE
OUT_SCALE
Fig. 8-1
PID Function Block Schematic
BKCAL_OUT
ROUT_OUT
ROUT_IN
Output
Limiting
OUT_HI_LIM
OUT_LO_LIM
OUT_SCALE
Operator
Output
OUT
8-1 Setpoint Selection and Limiting
The setpoint of the PID block is determined by the mode. The SP_HI_LIM and SP_LO_LIM parameters can be configured to limit the setpoint. In Cascade or RemoteCascade mode, the setpoint is adjusted by another function block or by a host computer, and the output is computed based on the setpoint.
In Automatic mode, the setpoint is entered manually by the operator, and the output is computed based on the setpoint. In Auto mode, it is also possible adjust the setpoint limit and the setpoint rate of change using the
SP_RATE_UP and SP_RATE_DN parameters.
In Manual mode the output is entered manually by the operator, and is independent of the setpoint. In RemoteOutput mode, the output is entered by a host computer, and is independent of the setpoint.
Figure 8-2 illustrates the method for setpoint selection.
8-4
Foundation TM
ETC01184
10/2003
Fieldbus Communication Instruction Manual
Foundation TM Fieldbus
8-2 Filtering
Operator
Setpoint
Auto
Man
Cas
SP_HI_LIM
SP_LO_LIM
SP_RATE_UP
SP_RATE_DN
Setpoint
Limiting
Rate
Limiting
Auto
Man
Cas
Fig. 8-2
PID Function Block Setpoint Selection
8-2 Filtering
The filtering feature changes the response time of the device to smooth variations in output readings caused by rapid changes in input.
The filtering feature can be configured with the
FILTER_TYPE parameter, and the filter time constant (in seconds) can be adjusted using the PV_FTIME or SP_FTIME parameters. Set the filter time constant to zero to disable the filter feature.
8-3 Feedforward Calculation
The feedforward value (FF_VAL) is scaled
(FF_SCALE) to a common range for compatibility with the output scale
(OUT_SCALE). A gain value (FF_GAIN) is applied to achieve the total feedforward contribution.
8-4 Tracking
Output tracking is enabled through the control options. Control options can be set in Manual or Out of Service mode only.
The Track Enable control option must be set to True for the track function to operate. When the Track in Manual control option is set to True, tracking can be activated and maintained only when the block is in Manual mode. When
Track in Manual is False, the operator can override the tracking function when the block is in Manual mode. Activating the track function causes the block’s actual mode to revert to
Local Override.
The TRK_VAL parameter specifies the value to be converted and tracked into the output when the track function is operating. The
TRK_SCALE parameter specifies the range of TRK_VAL.
When the TRK_IN_D parameter is True and the Track Enable control option is True, the
TRK_VAL input is converted to the appropriate value and output in units of OUT_SCALE.
8-5
Foundation TM Fieldbus
Foundation TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
8-5 Output Selection And Limiting
8-5 Output Selection and Limiting
Output selection is determined by the mode and the setpoint. In Automatic, Cascade, or
RemoteCascade mode, the output is computed by the PID control equation.
In Manual and RemoteOutput mode, the output may be entered manually (see also Set-
point Selection and Limiting). The output can be limited by configuring the OUT_HI_LIM and
OUT_LO_LIM parameters.
8-6 Bumpless Transfer and Setpoint Tracking
The method for can be configured tracking the setpoint by configuring the following control options (CONTROL_OPTS):
SP-PV Track in Man — Permits the SP to track the PV when the target mode of the block is Man.
SP-PV Track in LO or IMan — Permits the
SP to track the PV when the actual mode of the block is Local Override (LO) or
Initialization Manual (IMan).
When one of these options is set, the SP value is set to the PV value while in the specified mode.
The value that a master controller uses can be selected for tracking by configuring the Use PV
for BKCAL_OUT control option. The
BKCAL_OUT value tracks the PV value.
BKCAL_IN on a master controller connected to BKCAL_OUT on the PID block in an open cascade strategy forces its OUT to match
BKCAL_IN, thus tracking the PV from the slave
PID block into its cascade input connection
(CAS_IN). If the Use PV for BKCAL_OUT option is not selected, the working setpoint
(SP_WRK) is used for BKCAL_OUT.
Control options can be set in Manual or Out
of Service mode only. When the mode is set to Auto, the SP will remain at the last value (it will no longer follow the PV.
8-7 PID Equation Structures
Configure the STRUCTURE parameter to select the PID equation structure. Select one of the following choices:
• PI Action on Error, D Action on PV
• PID Action on Error
• Action on Error, PD Action on PV
Set RESET to zero to configure the PID block to perform integral only control regardless of the STRUCTURE parameter selection. When
RESET equals zero, the equation reduces to an integrator equation with a gain value applied to the error:
GAIN x e ( s ) s
Where
GAIN: Proportional gain value.
e: s:
Error.
Laplace operator.
8-6
Foundation TM
ETC01184
10/2003
Fieldbus Communication Instruction Manual
Foundation TM Fieldbus
8-8 Reverse and Direct Action
8-8 Reverse and Direct Action
To configure the block output action, enable the
Direct Acting control option. This option defines the relationship between a change in
PV and the corresponding change in output.
With Direct Acting enabled (True), an increase in PV results in an increase in the output.
Control options can be set in Manual or Out
of Service mode only.
Track Enable, Track in Manual,
SP-PV Track in Man, SP-PV
Track in LO or IMan, Use PV for
BKCAL_OUT, and Direct Acting are the only control options supported by the PID function block. Unsupported options are not grayed out; they appear on the screen in the same manner as supported options.
8-9 Reset Limiting
The PID function block provides a modified version of feedback reset limiting that prevents windup when output or input limits are encountered, and provides the proper behavior in selector applications.
8-10 Block Errors
Table 8-2 lists conditions reported in the
BLOCK_ERR parameter. Conditions in italics are inactive for the PID block and are given here for reference only.
7
8
9
10
4
5
6
Condition
Number
0 Other :
1
2
Condition Name and Description
Block Configuration Error: The BY_PASS parameter is not configured and is set to 0, the SP_HI_LIM is less than the SP_LO_LIM, or the OUT_HI_LIM is less than the OUT_LO_LIM.
Link Configuration Error
3 Simulate Active
11
12
13
14
15
Local Override: The actual mode is LO.
Device Fault State Set
Device Needs Maintenance Soon
Input Failure/Process Variable has Bad Status: The parameter linked to IN is indicating a Bad status.
Output Failure
Memory Failure
Lost Static Data
Lost NV Data
Readback Check Failed
Device Needs Maintenance Now
Power Up
Out of Service: The actual mode is out of service.
Tab. 8-2
Block Error Conditions
8-7
Foundation TM Fieldbus
Foundation TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
8-11 Modes
8-11 Modes
The PID function block supports the following modes:
Manual (Man)—The block output (OUT) may be set manually.
Automatic (Auto)—The SP may be set manually and the block algorithm calculates OUT.
Cascade (Cas)—The SP is calculated in another block and is provided to the PID block through the CAS_IN connection.
RemoteCascade (RCas)—The SP is provided by a host computer that writes to the RCAS_IN parameter.
RemoteOutput (Rout)—The OUT is provided by a host computer that writes to the
ROUT_IN parameter
Local Override (LO)—The track function is active. OUT is set by TRK_VAL. The
BLOCK_ERR parameter shows Local override.
Initialization Manual (IMan)—The output path is not complete (for example, the cascadeto-slave path might not be open). In IMan mode, OUT tracks BKCAL_IN.
Out of Service (O/S)—The block is not processed. The OUT status is set to Bad:
Out of Service. The BLOCK_ERR parameter shows Out of service.
The Man, Auto, Cas, and O/S modes can be configured as permitted modes for operator entry.
8-12 Alarm Detection
A block alarm will be generated whenever the
BLOCK_ERR has an error bit set. The types of block error for the AI block are defined above.
Process alarm detection is based on the PV value. The alarm limits of the following standard alarms can be configured:
• High (HI_LIM)
• High high (HI_HI_LIM)
• Low (LO_LIM)
• Low low (LO_LO_LIM)
Additional process alarm detection is based on the difference between SP and PV values and can be configured via the following parameters:
• Deviation high (DV_HI_LIM)
• Deviation low (DV_LO_LIM)
In order to avoid alarm chattering when the variable is oscillating around the alarm limit, an alarm hysteresis in percent of the PV span can be set using the ALARM_HYS parameter. The priority of each alarm is set in the following parameters:
• HI_PRI
• HI_HI_PRI
• LO_PRI
• LO_LO_PRI
• DV_HI_PRI
• DV_LO_PRI
Alarms are grouped into five levels of priority
8-8
Foundation TM
ETC01184
10/2003
Fieldbus Communication Instruction Manual
Foundation TM Fieldbus
8-13 Status Handling
Priority
0
1
2
3-7
8-15
Tab. 8-3
Alarm Priorities
Priority Description Number
The priority of an alarm condition changes to 0 after the condition that caused the alarm is corrected.
An alarm condition w ith a priority of 1 is recognized by the system, but is not reported to the operator.
An alarm condition w ith a priority of 2 is reported to the operator, but does not require operator attention (such as diagnostics and system alerts).
Alarm conditions of priority 3 to 7 are advisory alarms of increasing priority.
Alarm conditions of priority 8 to 15 are critical alarms of increasing priority.
8-13 Status Handling
If the input status on the PID block is Bad, the mode of the block reverts to Manual. In addition, the Target to Manual if Bad IN status option can be selected to direct the target mode to revert to manual. The status option can be set in Manual or Out of Service mode only.
Target to Manual if Bad IN is the only status option supported by the PID function block.
Unsupported options are not grayed out; they appear on the screen in the same manner as supported options.
8-14 Closed Loop Control
To implement basic closed loop control, compute the error difference between the process variable (PV) and setpoint (SP) values and calculate a control output signal using a
PID (Proportional Integral Derivative) function block.
The proportional control function responds immediately and directly to a change in the PV or SP. The proportional term GAIN applies a change in the loop output based on the current magnitude of the error multiplied by a gain value.
The integral control function reduces the process error by moving the output in the appropriate direction. The integral term
RESET applies a correction based on the magnitude and duration of the error. Set the
RESET parameter to zero for integral-only control. To reduce reset action, configure the
RESET parameter to be a large value.
The derivative term RATE applies a correction based on the anticipated change in error. Derivative control is typically used in temperature control where large measurement lags exist.
The MODE parameter is a switch that indicates the target and actual mode of operation. Mode selection has a large impact on the operation of the PID block:
Manual mode allows the operator to set the value of the loop output signal directly.
Automatic mode allows the operator to select a setpoint for automatic correction of error using the GAIN, RESET, and RATE tuning values.
Cascade and Remote Cascade modes use a setpoint from another block in a cascaded configuration.
8-9
Foundation TM Fieldbus
Foundation TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
8-15 Closed Loop Control
Remote Out mode is similar to Manual mode except that the block output is supplied by an external program rather than by the operator.
Initialization Manual is a non-target mode used with cascade configurations while transitioning from manual operation to automatic operation.
Local Override is a non-target mode that instructs the block to revert to Local
Override when the tracking or fail-safe control options are activated.
Out of Service mode disables the block for maintenance.
Abrupt changes in the quality of the input signal can result in unexpected loop behavior. To prevent the output from changing abruptly and upsetting the process, select the SP-PV Track
in Man I/O option. This option automatically sets the loop to Manual if a Bad input status is detected. While in manual mode, the operator can manage control manually until a Good input status is reestablished.
8-15 Application Information
The PID function block is a powerful, flexible control algorithm that is designed to work in a variety of control strategies. The PID block is configured differently for different applications.
The following examples describe the use of the
PID block for closed-loop control (basic PID loop), feedforward control, cascade control with master and slave, and complex cascade control with override.
8-10
Foundation TM
ETC01184
10/2003
Fieldbus Communication Instruction Manual
Foundation TM Fieldbus
8-15 Application Information
8-15-1 Application Example 1
Basic PID Block for Steam Heater Control
TCV
101
Steam Supply
TT
100
Steam Heater
TC
101
TT
101
Fig. 8-2
PID Function Block Steam Heater Control Example
Situation
A PID block is used with an AI block and an AO block to control the flow steam used to heat a process fluid in a heat exchanger. The diagram below illustrates the process instrumentation.
Condensate
Solution
The PID loop uses TT101 as an input and provides a signal to the analog output TCV101.
The BKCAL_OUT of the AO block and the
BKCAL_IN of the PID block communicate the status and quality of information being passed between the blocks. The status indication shows that communications is functioning and the I/O is working properly. The diagram below illustrates the correct function block configuration.
Outlet
Temperature
Input BKCAL_IN BKCAL_OUT
AI
Function
Block
OUT IN
PID
Function
Block
TC101 TT101
Fig. 8-3
PID Function Block Diagram for Steam Heater Control Example
CAS_IN
OUT
AO
Function
Block
TCV101
OUT
8-11
Foundation TM Fieldbus
Foundation TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
8-15 Application Information
8-15-2 Application Example 2
Feedforward Control
Situation
In the previous example, control problems can arise because of a time delay caused by thermal inertia between the two flow streams
(TT100 and TT101). Variations in the inlet temperature (TT100) take an excessive amount of time to be sensed in the outlet
(TT101). This delay causes the product to be out of the desired temperature range.
TCV
101
Solution
Feedforward control is added to improve the response time of the basic PID control. The temperature of the inlet process fluid (TT100) is input to an AI function block and is connected to the FF_VAL connector on the PID block.
Feedforward control is then enabled
(FF_ENABLE), the feedforward value is scaled
(FF_SCALE), and a gain (FF_GAIN) is determined. The diagrams below illustrate the process instrumentation, and the correct function block configuration.
FF
TC
101
Steam Supply
TT
100
TT
101
Steam Heater
Condensate
Fig. 8-4
PID Function Block Feedforward Control Example
Outlet
Temperature
Input
BKCAL_IN BKCAL_OUT
AI
Function
Block
Inlet
Temperature
Input
TT101
AI
Function
Block
OUT IN
FF_VAL
PID
Function
Block
TC101
OUT
CAS_IN
OUT
AO
Function
Block
TCV101
OUT
Fig. 8-5
PID Function Block Diagram for Feedforward Control Example
8-12
Foundation TM
ETC01184
10/2003
Fieldbus Communication Instruction Manual
Foundation TM Fieldbus
8-15 Application Information
8-15-3 Application Example 3
Cascade Control with Master and Slave Loops
Situation
A slave loop is added to a basic PID control configuration to measure and control steam flow to the steam heater. Variations in the steam pressure cause the temperature in the heat exchanger to change. The temperature variation will later be sensed by TT101. The temperature controller will modify the valve position to compensate for the steam pressure change. The process is slow and causes variations in the product temperature. The diagram below illustrates the process instrumentation
Solution
If the flow is controlled, steam pressure variations will be compensated before they significantly affect the heat exchanger temperature. The output from the master temperature loop is used as the setpoint for the slave steam flow loop. The BKCAL_IN and
BKCAL_OUT connections on the PID blocks are used to prevent controller windup on the master loop when the slave loop is in Manual or Automatic mode, or it has reached an output constraint. The diagram below illustrates the correct function block configuration.
FC
101
TC
101
FT
101
TCV
101
Steam
Supply
TT
100
TT
101
Steam Heater
Condensate
Fig. 8-6
PID Function Block Cascade Control Example
Outlet
Temperature
Input
BKCAL_IN BKCAL_OUT
AI
Function
Block
Steam
Flow
Input
TT101
OUT IN
PID
Function
Block
TC101
OUT
AI
Function
Block
OUT
CAS_IN
IN
Fig. 8-7
PID Function Block Diagram for Cascade Control Example
PID
Function
Block
OUT
IN
AO
Function
Block
TCV101
8-13
Foundation TM Fieldbus
Foundation TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
8-15 Application Information
8-15-4 Application Example 4
Cascade Control with Override
The PID function block can be used with other function blocks for complex control strategies.
The diagram below illustrates the function block diagram for cascade control with override.
When configured for cascade control with override, if one of the PID function blocks connected to the selector inputs is deselected, that PID block filters the integral value to the selected value (the value at its BKCAL_IN). The selected PID block behaves normally and the deselected controller never winds up. At steady state, the deselected PID block offsets its OUT value from the selected value by the proportional term. When the selected block becomes output-limited, it prevents the integral term from winding further into the limited region.
When the cascade between the slave PID block and the Control Selector block is open, the open cascade status is passed to the Control
Selector block and through to the PID blocks supplying input to it. The Control Selector block and the upstream (master) PID blocks have an actual mode of IMan.
If the instrument connected to the AI block fails, the AI block can be placed in Manual mode and set the output to some nominal value for use in the Integrator function block. In this case,
IN at the slave PID block is constant and prevents the integral term from increasing or decreasing.
BKCAL_IN
Slave Controller
Master Controller
PID
Function
Block
OUT
CAS_IN
IN
PID
Function
Block
TC101
SEL_1
SEL_2
BCAL_SEL_1
Configured for High Selection
Control
Selector
Function
Block
OUT
BCAL_SEL_2
Master Controller
PID
Function
Block OUT
OUT
CAS_IN
IN_1
BKCAL_OUT
AO
Function
Block
PID
Function
Block
AI
Function
Block
Fig. 8-8
PID Function Block Diagram for Cascade Control with Override
8-14
Foundation TM
ETC01184
10/2003
Fieldbus Communication Instruction Manual
Foundation TM Fieldbus
8-16 Troubleshooting
8-16 Troubleshooting
Symptom
Mode w ill not leave OOS
Possible Causes
1. Target mode not set.
2. Configuration error
Mode w ill not leave IMAN
Mode w ill not change to
AUTO
Mode w ill not
3. Resource block
4. Schedule
1. Back Calculation
1. Target mode not set.
2. Input
1.Target mode not set.
change to CAS 2. Cascade input
Mode sheds from RCAS to
AUTO
1. Remote Cascade Value
2. Shed Timer
Mode sheds from ROUT to
MAN
1. Remote output value
2. Shed timer
Process and/or 1. Features block alarms w ill not w ork.
2. Notification
3. Status Options
Tab. 8-4
Troubleshooting for PID
Corrective Action
1. Set target mode to something other than OOS.
2. BLOCK_ERR w ill show the configuration error bit set. The follow ing are parameters that must be set before the block is allow ed out of OOS: a. BYPASS must be off or on and cannot be left at initial value of 0.
b. OUT_HI_LIM must be less than or equal to OUT_LO_LIM.
c. SP_HI_LIM must be less than or equal to SP_LO_LIM.
3. The actual mode of the Resource block is OOS. See Resource Block Diagnostics for corrective action.
4. Block is not scheduled and therefore cannot execute to go to Target Mode. Schedule the block to execute.
1. BKCAL_IN a. The link is not configured (the status w ould show “Not Connected”). Configure the BKCAL_IN link to the dow nstream block.
b. The dow nstream block is sending back a Quality of “Bad” or a Status of “Not Invited”. See the appropriate dow nstream block diagnostics for corrective action.
1. Set target mode to something other than OOS.
2. IN a. The link is not configured (the status w ould show “Not Connected”). Configure the IN link to the block.
b. The upstream block is sending back a Quality of “Bad” or a Status of “Not Invited”. See the appropriate upstream block diagnostics for corrective action.
1. Set target mode to something other than OOS.
2. CAS_IN a. The link is not configured (the status w ould show “Not Connected”). Configure the CAS_IN link to the block.
b. The upstream block is sending back a Quality of “Bad” or a Status of “Not Invited”. See the appropriate up stream block diagnostics for corrective action.
1. Host system is not w riting RCAS_IN w ith a quality and status of “good cascade” w ithin shed time (see 2 below ).
2. The mode shed timer, SHED_RCAS in the resource block is set too low . Increase the value.
1. Host system is not w riting ROUT_IN w ith a quality and status of “good cascade” w ithin shed time (see 2 below ).
2. The mode shed timer, SHED_RCAS, in the resource block is set too low . Increase the value.
1. FEATURES_SEL does not have Alerts enabled. Enable the Alerts bit.
2. LIM_NOTIFY is not high enough. Set equal to MAX_NOTIFY.
3. STATUS_OPTS has Propagate Fault Forw ard bit set. This should be cleared to cause an alarm to occur.
8-15
Foundation TM Fieldbus
Foundation TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
8-16
Foundation TM
ETC01184
10/2003
Fieldbus Communication Instruction Manual
Foundation TM Fieldbus
APPENDIX
Operation with EMERSON™ Process Management DeltaV™
A-1 About DeltaV Software with AMS inside
AMSinside DeltaV software allows users to manage their instrumentation, and to perform on-line configurations of their instruments.
The ability to communicate with instruments and configure instruments on-line facilitates instrument commissioning and loop validation.
With AMSinside, users can also access status and diagnostic data from smart devices and monitor their performance.
AMS leverages the I/O capabilities of the control system to gather asset management data without interfering with the control system’s operations.
A-2 Install the Analyzer onto DeltaV TM
The following procedures assume that the DeltaV and the analyzer are installed and powered.
The following steps have to be performed to install a new device onto a DeltaV TM system:
• From the start menu select DeltaV >
Engineering > DeltaV Explorer
• Select/Expand „Library“ (right below
DeltaV_System)
• Select „Fieldbus Devices“, using right mouse button. Click on „Fieldbus
Devices“. This will bring up a list of options
• From the list, select „Add Device Definition...“ This should give you a „Browse for folder“ selection box.
Browse to the directory that contains the 7 files needed to „register“ a new device with
DeltaV. These file will consist of 3 *.dll files,
*.sym, *.ffo, *.fhx and *.reg file.
The files probably will be on a floppy disk or a CD-ROM that accompanies your device. On CD-ROMs delivered together with Emerson Process Management analyzers the files are located in the directory \Fieldbus. Dependent on the existent system use the files of the appropriate subdirectory.
• After answering „yes“ to the first prompt,
DeltaV will start the installation.
Fig. A-1 shows the „Exploring DeltaV“ screen for reference.
A-1
Foundation TM Fieldbus
Foundation TM Fieldbus Communication Instruction Manual
ETC01184
10/2003
A-2
Fig. A-1
DeltaV Explorer
Instruction Manual
ETC01184
10/2003
Foundation TM Fieldbus MLT 1-2 & CAT 200
Foundation TM Fieldbus MLT 1-2 & CAT 200
WORLD HEADQUARTERS
ROSEMOUNT ANALYTICAL EUROPE
Emerson Process Management
GmbH & Co. OHG
Industriestrasse 1
63594 Hasselroth
Germany
T 49 6055 884 0
F 49 6055 884209
Emerson Process Management
Rosemount Analytical Inc.
6565 P Davis Industrial Parkway
Solon, OH 44139 USA
T 440.914.1261
Toll Free in US and Canada 800.433.6076
F 440.914.1271
e-mail: [email protected]
www.raihome.com
GAS CHROMATOGRAPHY CENTER
AND LATIN AMERICA
Emerson Process Management
Rosemount Analytical Inc.
11100 Brittmoore Park Drive
Houston, TX 77041
T 713 467 6000
F 713 827 3329
EUROPE, MIDDLE EAST AND AFRICA
Emerson Process Management
Shared Services Limited
Heath Place
Bognor Regis
West Sussex PO22 9SH
England
T 44 1243 863121
F 44 1243 845354
ASIA-PACIFIC
Emerson Process Management
Asia Pacific Private Limited
1 Pandan Crescent
Singapore 128461
Republic of Singapore
T 65 6 777 8211
F 65 6 777 0947 e-mail: [email protected]
Instruction Manual
ETC01184
10/2003
© Emerson Process Management GmbH & Co. OHG 2007
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 1 Instruction Manual FoundationTM Fieldbus Communication Option for MLT 1, MLT 2 and CAT 200
- 2 ESSENTIAL INSTRUCTIONS
- 3 PREFACE
- 3 Definitions
- 4 Safety Instructions
- 5 Table of Contents
- 9 SECTION 1 Foundation™ Fieldbus Technology
- 9 1-1 Overview
- 9 1-2 Introduction
- 10 1-2-1 Function Blocks
- 11 1-2-2 Device Descriptions
- 12 1-3 Instrument Specific Function Blocks
- 12 1-3-1 Resource Blocks
- 12 1-3-2 Transducer Blocks
- 12 1-3-3 Alerts
- 13 1-4 Network Communication
- 13 1-4-1 Link Active Scheduler (LAS)
- 14 1-4-2 Device Addressing
- 14 1-4-3 Scheduled Transfers
- 16 1-4-4 Unscheduled Transfers
- 17 1-4-5 Function Block Scheduling
- 18 1-5 References
- 18 1-5-1 Fieldbus Foundation
- 19 1-6 Implemented Function Blocks
- 21 SECTION 2 Transducer Block
- 22 2-1 List of Transducer Block Parameters
- 25 2-2 Transducer Block Parameter Descriptions
- 27 2-3 Transducer Block Parameter Attribute Definitions
- 29 2-4 Transducer Block Enumerations
- 29 2-4-1 Gas Control State
- 29 2-4-2 Calibration States
- 30 2-4-3 Calibration Step Control
- 31 2-4-4 Measurement Options
- 31 2-4-5 Calibration Options
- 32 2-4-6 Sensor Options
- 32 2-4-7 Analyzer Options
- 33 2-4-8 Access Mode Control
- 33 2-4-9 Detailed Status
- 33 2-4-9-1 Detailed Maintenance
- 34 2-4-9-2 Detailed Failure
- 35 2-4-9-3 Detailed Status
- 36 2-4-10 Function Call Control
- 37 2-5 Transducer Block Channel Assignments
- 37 2-5-1 I/O Channel Assignments for AI-Blocks
- 37 2-5-2 I/O Channel Assignment for A0-Blocks
- 38 2-6 Simulation of TBlk States
- 38 2-7 Supported Transducer Block Errors
- 38 2-7-1 Out of Service
- 38 2-7-2 Block Configuration Error
- 38 2-7-3 Input Failure/ Process Variable has BAD Status
- 38 2-7-4 Device needs Maintenance Now
- 38 2-7-5 Simulate Active
- 38 2-7-6 Other Error
- 39 SECTION 3 Resource Block
- 39 3-1 Mapping of the PlantWeb Alerts
- 41 3-2 PWA_SIMULATE
- 43 SECTION 4 Analog Input (AI) Function Block
- 45 4-1 Simulation
- 46 4-2 Filtering
- 46 4-3 Signal Conversion
- 48 4-4 Block Errors
- 48 4-5 Modes
- 49 4-6 Alarm Detection
- 50 4-7 Status Handling
- 50 4-8 Advanced Features
- 51 4-9 Application Information
- 51 4-9-1 Application Example 1 Temperature Transmitter
- 52 4-9-2 Application Example 2 Pressure Transmitter used to Measure Level in Open Tank
- 53 4-9-3 Application Example 3 Differential Pressure Transmitter used to Measure Flow
- 54 4-10 Troubleshooting
- 55 SECTION 5 Analog Output (AO) Function Block
- 56 5-1 Setting the Output
- 57 5-2 Setpoint Selection and Limiting
- 57 5-3 Conversion and Status Calculation
- 58 5-4 Simulation
- 58 5-5 Action on Fault Detection
- 59 5-6 Block Errors
- 59 5-7 Modes
- 59 5-8 Status Handling
- 61 SECTION 6 Input Selector (ISEL) Function Block
- 63 6-1 Block Errors
- 64 6-2 Modes
- 64 6-3 Alarm Detection
- 64 6-4 Block Execution
- 65 6-5 Status Handling
- 65 6-6 Application Information
- 67 6-7 Troubleshooting
- 69 SECTION 7 Arithmetic (ARTHM) Function Block
- 72 7-1 Block Errors
- 72 7-2 Modes
- 73 7-3 Alarm Detection
- 73 7-4 Block Execution
- 74 7-5 Status Handling
- 74 7-6 Application Information
- 79 SECTION 8 Proportional / Integral / Derivative (PID) Function Block
- 82 8-1 Setpoint Selection and Limiting
- 83 8-2 Filtering
- 83 8-3 Feedforward Calculation
- 83 8-4 Tracking
- 84 8-5 Output Selection and Limiting
- 84 8-6 Bumpless Transfer and Setpoint Tracking
- 84 8-7 PID Equation Structures
- 85 8-8 Reverse and Direct Action
- 85 8-9 Reset Limiting
- 85 8-10 Block Errors
- 86 8-11 Modes
- 86 8-12 Alarm Detection
- 87 8-13 Status Handling
- 87 8-14 Closed Loop Control
- 88 8-15 Application Information
- 89 8-15-1 Application Example 1 Basic PID Block for Steam Heater Control
- 90 8-15-2 Application Example 2 Feedforward Control
- 91 8-15-3 Application Example 3 Cascade Control with Master and Slave Loops
- 92 8-15-4 Application Example 4 Cascade Control with Override
- 93 8-16 Troubleshooting
- 95 APPENDIX Operation with EMERSON™ Process Management DeltaV™
- 95 A-1 About DeltaV Software with AMS inside
- 95 A-2 Install the Analyzer onto DeltaVTM