Documente Academic
Documente Profesional
Documente Cultură
Manual 06/2010
Safety Guidelines: Warning notices must be observed to ensure personal safety as well as that of
others, and to protect the product and the connected equipment. These warning notices are
accompanied by a clarification of the level of caution to be observed.
Qualified Personnel: This device/system may only be set up and operated in conjunction with this
manual. Qualified personnel are only authorized to install and operate this equipment in accordance with
established safety practices and standards.
Unit Repair and Excluded Liability:
The user is responsible for all changes and repairs made to the device by the user or the users
agent.
All new components are to be provided by Siemens Milltronics Process Instruments Inc.
Restrict repair to faulty components only.
Do not reuse faulty components.
Warning: Cardboard shipping package provides limited humidity and moisture protection. This product
can only function properly and safely if it is correctly transported, stored, installed, set up, operated, and
maintained.
This product is intended for use in industrial areas. Operation of this equipment in a residential area
may cause interference to several frequency based communications.
Table of Contents
Foundation Fieldbus (FF) Communications for Siemens Level Instruments ........... 1
mmmmm
Overview ....................................................................................................................................................1
Safety Notes .............................................................................................................................................1
The Manual ...............................................................................................................................................1
Technical Support ....................................................................................................................................2
Abbreviations and Identifications .............................................................................................2
Foundation Fieldbus (FF) Profile Structure .................................................................... 5
Block Model for recording and processing measured values .....................................................5
Description of individual blocks ...........................................................................................................6
Resource Block (RESOURCE) .....................................................................................................6
Level Transducer Block (LTB) .....................................................................................................6
Analog Input Function Blocks 1 and 2 (AIFB 1 & AIFB 2) ....................................................9
LCD Transducer Block (LCD) ....................................................................................................11
Diagnostic Transducer Block (DIAG) ......................................................................................11
Communications via Foundation Fieldbus (FF) ........................................................... 13
System Integration ................................................................................................................................13
Data transmission .......................................................................................................................13
Simulation .....................................................................................................................................13
Link Master Capability ...............................................................................................................16
Diagnostics ...................................................................................................................................16
Extended Diagnostics ................................................................................................................17
Blocks and Parameter Descriptions .................................................................................................23
Resource Block (RESOURCE) ...................................................................................................23
Level Transducer Block (LTB) ...................................................................................................36
Analog Input Function Block (AIFB 1 and AIFB 2) ..............................................................44
LCD Transducer Block (LCD) ....................................................................................................56
Diagnostic Transducer Block (DIAG) ......................................................................................61
i
mmmmm
Table of Contents
ii
Foundation Fieldbus (FF)
Communications for Siemens Level
Instruments
Overview
For operation of Siemens Level Instruments via Foundation Fieldbus it is necessary to use
PC software such as AMS Device Manager. Please consult the appropriate operating
instructions for details of how to operate this software.
Siemens Foundation Fieldbus Level instruments are implemented as FF (H1) devices of
Introduction
Class 31PS and 32L. They use a block model for recording and processing measured
mmmmm
values. These instruments support publish and subscribe functionality as well as Backup
LAS functionality. The full range of FF Level device functions is available only over an FF
network.
Foundation Fieldbus (FF) is an open industrial protocol. Full details about FF can be
obtained from Fieldbus FOUNDATION at www.fieldbus.org.
Safety Notes
Special attention must be paid to warnings and notes highlighted from the rest of the text
by grey boxes.
Note: means important information about the product or that part of the operating
manual.
The Manual
This manual provides information on the use of Foundation Fieldbus protocol with
Siemens FF Level instruments. The manual is designed to help you get the most out of
your level device when used in conjunction with the Foundation Fieldbus protocol, and it
provides information on the following:
Block model
Function and Transducer blocks inputs and outputs
Block descriptions
System integration
Diagnostics and General fault codes
Fieldbus Communication
Block parameter description/format
If you have any questions, comments, or suggestions about the manual contents, please
email us at techpubs.smpi@siemens.com.
For the complete library of Siemens Milltronics manuals, go to
www.siemens.com/processautomation.
www.siemens.com/automation/support-request
mmmmm
Enter the device name or order number, then click on Search, and select the
appropriate product type. Click on Next.
You will be prompted to enter a keyword describing your issue. Then either
browse the relevant documentation, or click on Next to email a detailed
description of your issue to Siemens Technical Support staff.
Introduction
mmmmm
FF Profile Structure
The Resource Block, Level Transducer Block, LCD Transducer Block and Diagnostic
Transducer Block do not need to be scheduled by external software. They are always
running.
mmmmm
The AIFB 1, and AIFB 2 Function Blocks have to be scheduled using software such as
National Instruments NI-FBUS Configurator, or Emerson DeltaV.
The block execution times for the different products are shown below:
AIFB
SITRANS LR250 FF 40 ms
1)
See Link Master Capability on page 16
Resource
Block
The Resource Block for a standard FF device contains data specific to the hardware
associated with the resource. This includes the device type and revision, manufacturer
ID, serial number and resource state. These are contained parameters: accessible to the
communication network but may not be linked to an input or output parameter. The
parameter value may be used in the block algorithm or written by the block algorithm. The
data is not processed in the way that a function block processes data. As the Resource
Block is central to the field instrument, it contains the Quick Start Wizard used for easy
configuration of the instrument.
The Level Transducer Block takes raw data from the level sensor and converts it to
measurement data used by the Analog Input Function Blocks (AIFBs). The LTB contains
information such as calibration, signal processing setup, etc.
Level AIFB 1
Offset (Analog
Sensor High Low Linearization Input)
Offset Calibration Calibration Type
SV1
Point Point
High Level Low Level
FF Profile Structure
Point Point Secondary Value 1 AIFB 2
Calibration [Level] (Analog
Type (Level Units) Input)
SV2
mmmmm
Secondary Value 2
[Distance]
(Sensor Units)
The Level TB implements all of the basic parameters (see parameter diagram on page 8),
including level to volume calculation, if that option has been selected.
1. The sensor technology sub-block selects the proper echo. (For an explanation of
sensor technology, see Echo Processing - Process Intelligence in the Siemens level
instrument instruction manual.)
The sensor value (in sensor units) is checked to see if it is within its measuring limits.
If the limit is exceeded, this results in a Bad status and the error message Failure in
measurement.
The analog signal from the sensor is transformed into a digital signal.
A Sensor Offset parameter (default 0) provides compensation if necessary for
changes in the sensor.
Sensor
Reference Point
(flange face)
High Level High Calibration
Point Point
(default: 100%) sensor value1)
distance/SV2
Level/PV
Electronics temperature
The Transducer Block also monitors the internal temperature of the device electronics. A
change in temperature can provide advance warning of a possible device failure, and
allow for preventative maintenance.
If the temperature limit is exceeded, the output value is unchanged but the output status
changes. (The permitted limits correspond to those of the permitted ambient
temperature.)
Peak indicators (see parameters Minimum Sensor Value and Maximum Sensor Value in
the Siemens level instrument instruction manual) allow you to check the maximum and
minimum temperatures that have occurred.
1)
Level Offset (default 0) can compensate for specific vessel configurations.
The Analog Input Function Block (AIFB 1 or AIFB 2) is connected to one of the channels of
the Level Transducer Block (LTB). It is the source of measurements for a function block
application. The AIFB is a standard block as per the Fieldbus Foundation Function block
specification (FF-891).
The figure below shows how measured values are processed within the Analog Input
Function Block (AIFB 1 or AIFB 2) to produce the device outputs, which are
communicated via FF (H1), and displayed on the LCD.
Analog Input Function Block
FIELD_VAL Output
OUT
FF Profile Structure
Mode Alarms
HI/LO
mmmmm
1) If the CHANNEL value has a BAD status, the Convert, Cutoff, and Filter steps will not
be performed. The CHANNEL value will be sent directly to the OUT value.
Simulation
The input can be a simulated value instead of one of the output channels of the Level
Transducer Block. This allows the AI block to be tested independently of the
characteristics of the environment. To enable this feature, the SIMULATE ENABLE
parameter must be enabled using the hand programmer. Please see the device manual
for more details on how to turn on the SIMULATE ENABLE.
Output
When the block is in manual mode, the user can enter a value into the output section and
mmmmm
this will be passed onto bus as the output. When in auto mode, and the status of the
CHANNEL value is not BAD, the output is always the PV (see Analog Input Function Block
diagram on page 9).
Alarms:
There are four levels of alarms and three variables connected to each level.
1)
For this mode of operation, XD_SCALE and OUT_SCALE must match.
Note: The Transducer Block units and Function Block units are configured separately
and are independent of each other.
The LCD Transducer Block is a custom block that is used to configure the measurement
display.
The following figure illustrates the basic functionality of the LCD Transducer Block.
FF Profile Structure
Select Language Adjust LCD
Contrast
mmmmm
Select LUI Mode Enable LUI
Mode Handling
Data transmission
The Foundation Fieldbus protocol was designed for distributed control which allows the
control functions to reside in the field devices. A system can be set up in the traditional
fashion where a central system retrieves all the inputs, processes them and sends the
outputs back to the actuators. During the engineering of a control system the designer
may also choose to let the processing of the information be done in field devices. This
mainly depends on the features and configuration utilities supported by the system.
An engineering tool, such as NI-FBUS Configurator or DeltaV, is used to generate a
schedule. This schedule is used to instruct devices when they should publish their
outputs or results and to which data a device has to subscribe and listen. This schedule is
loaded into the available link masters.
One of the masters is the Link Active Scheduler (LAS) which is used for the arbitration of
the bus. Another link master can function as a Backup LAS and take over the arbitration if
the primary LAS fails. For details on how to setup a specific Fieldbus System please refer
to the manuals of the respective vendor.
Simulation
The Siemens level instrument supports the standard simulation of the fieldbus protocol
for the function blocks. In addition to this the Level Transducer Block features a
simulation mechanism that can be set to fixed values or ramps.
Simulation can be enabled on the Siemens FF level instrument using the hand FF Communications
programmer. Setting the SIMULATE ENABLE parameter to ON replaces a physical
jumper switch that is required for simulation on some FF devices.
mmmmm
Addressing
Every fieldbus device must have a unique node address and physical device tag for the
Foundation Fieldbus network to operate properly. The node address must be unique
within the link (segment), the physical device tag must be unique within the whole
network.
S I T R A N S L R 2 5 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Node Address
The instrument must have an address unique to the FF (H1) segment where it is
connected. A host configuration tool such as DeltaV or NI-FBUS Configurator
automatically assigns a unique permanent address to the instrument the first time it is
connected to the host. Out of the box, a temporary address is assigned to the instrument.
This temporary address is in the range 248 to 251. It uses this address until the host
assigns it a permanent address.
Configuration
For the configuration of the Siemens instrument you need:
The Electronic Device Description (EDD) describes in machine-readable format all the
information available at the fieldbus interface. It contains details on how to display
information to the user and how to arrange the parameters in hierarchical menus.
The EDD also contains a number of methods to ease configuration and operation of the
device. Help texts are included in the EDD to describe the meaning and handling of
various parameters.
Hosts and configuration tools can use the information contained in the EDD to generate a
user-friendly configuration interface.
The EDD consists of two files (with associated filename extensions):
FF Communications
The capability file (.cff) contains all information necessary for offline configuration.
Note: Please refer to the manual of your configuration tool or control system for the
installation of these files.
1.
EDD also known as Device Description (DD)
Configuration information is set up as acyclic data. Each of the two Analog Input Function
Blocks (not active out of the box) can be set up (using a configurator such as NI-FBUS
Configurator or DeltaV) to return Level, Distance, or Volume (if volume supported). Within
the function blocks, the values are scaled according to the user requirements.
AIFB 1 and AIFB 2 return 5 bytes of data each:
Status Floating Point
AIFB 2 byte 1
byte10 byte 2 byte 3 byte 4 byte 5
The 1st byte is the status byte and the list of possible values is given in the Status Codes
chart below. The next 4 bytes are the floating point representation (IEEE) of the variable.
The variables are the outputs of the function block.
Status Byte
Status Byte is defined in FF Specification FF-891-1.7. Status provides information about:
the usability of the measured value in the user program
the device status (self-diagnosis/system diagnosis)
additional process information (process alarms)
FF Communications
mmmmm
Status Codes
Priority Quality Sub Status Status Value
Lowest Good (NC) Non-specific 0x80
Good (NC) Active Block Alarm 0x84-0x87
Good (NC) Active Advisory Alarm 0x88-0x8b
Good (NC) Active Critical Alarm 0x8c-0x8f
Good (NC) Unack Block Alarm 0x90-0x93
Good (NC) Unack Advisory Alarm 0x94-0x97
Good (NC) Unack Critical Alarm 0x98-0x9b
Uncertain Non-specific 0x40-0x43
Uncertain Last usable value 0x44-0x47
Uncertain Substitute/Manual Entry 0x4b
Uncertain Initial value 0x4c-0x4f
Uncertain Sensor conversion not accurate 0x50-0x53
Uncertain Engineering unit range violation 0x54-0x57
Uncertain Sub normal 0x58-0x5b
Bad Non-specific 0x00
Bad Configuration error 0x03-0x07
Bad Device failure 0x0c-0x0f
Bad Sensor failure 0x10-0x13
Highest Bad Out of Service 0x1c
Note: The highest priority code determines the displayed status if more than one fault is
present. (See Device Status Icons in Siemens level instrument instruction manual.)
malfunctions the instrument can step in to maintain the operation of the FF segment. In
order to do so the instrument must receive the schedule for the loop during setup.
For detailed instructions on how the system management functions are configured,
mmmmm
Diagnostics
All diagnostic information shown below is viewable via AMS Device Manager. (Refer to
the AMS Device Manager chapter of the Siemens level instrument instruction manual for
details: for basic Diagnostics refer to the Alarms & Errors section within the LTB and
Resource blocks, and for Extended Diagnostics refer to the Extended Diagnostics section
within the LTB and Resource blocks.)
Diagnostics
(BLOCK_ERR)
Hex values Byte Bit Description
0x0100 0 Input Failure
0x0200 1 Maintenance Required
0x0400 2 Device Fault State
0x0800 3 Local Override
0
0x1000 4 Simulation Active
0x2000 5 Link Configuration
0x4000 6 Block Configuration
0x8000 7 Other
0x0001 0 Out of Service
0x0002 1 Power Up
0x0004 2 Maintenance Demanded
0x0008 3 Readback Check
1
0x0010 4 Lost Non-Volatile Data
0x0020 5 Lost Static Data
0x0040 6 Memory Failure
0x0080 7 Output Failure
Extended Diagnostics
In addition to the Diagnostics available above, further Extended Diagnostics are
available. These are displayed in the following charts. The fault code is given, along with
its meaning, and corrective action to remove the fault.
The digital codes shown below, with the corresponding fault code, icon, and error
message are displayed on the device when the variable being displayed has a status
condition active.
LEVELTB_BLOCK_ERR_DESC_1.
Note: Certain fault codes (identified by an asterisk [*] in the table below) will persist
until a manual reset has been performed. (See Fault Reset parameter in the Siemens
level instrument instruction manual.)
Siemens representative.
the resource. This includes the device type, device revision, manufacturer ID, serial
number and resource state. These are contained parameters: accessible to the
communication network but may not be linked to an input or output parameter. The
parameter value may be used in the block algorithm or written by the block algorithm. The
data is not processed in the way that a function block processes data.
This block offers a service timer based on the operating hours of the electronics. This can
be used to cause the alarms for "Device needs maintenance soon" and "Device needs
maintenance now".
Note: The resource block must be in automatic mode for any function
blocks of the instrument to execute.
Label/Name/
Description/Format
Handling
Selection of whether alarms associated with the resource block will be
automatically acknowledged.
Bit Clear (0): Auto acknowledge disabled
ACK_OPTION
Bit Set (1): Auto acknowledge enabled
Acknowledge Option
Bit 0: Write has been disabled
Read & Write
Bit 7: Block Alarm
Data format: Bit string with 16 bits (2 bytes)
Default value: 0
The time when evaluation of the block was started and a change in
alarm/event state was detected that is unreported.
3. TIME_STAMP
The time stamp value will be maintained constant until alert
Time Stamp
confirmation has been received even if another change of state
Read only
occurs.
Data format: Time-Value (8 bytes)
5. Value The value of the associated parameter at the time the alert was
Value detected.
Read only Data format: Unsigned 8
Writing a Clear to this parameter will clear the device fault state.
0: Uninitialized
1: Off Normal operating condition
CLR_FSTATE 2: Clear Block fault state conditions will be cleared
Clear Fault State Data format: Unsigned 8
Default value: 1
Note: This parameter defaults to Off and Read Only since there are no
output blocks in this device.
DD_RESOURCE String identifying the tag of the resource which contains the Device
DD Resource Description of this device.
Read Only Data format: Visible string (32 bytes)
CERTIFICATION
Device Certifications (Agency Approvals)
Device Certification
Data format: Visible string (32 bytes)
Read Only
The date when the device was installed in the system. Example:
DEVICE_INSTALL_DATE
12.01.2003
Device Installation Date
Data format: FF DATE_AND_TIME structure, MM/DD/YY HH:MM:SS
Read & Write
(See FF specification for details of format.)
POWERED_DAYS
Total powered operating days of this device electronics.
Device Operating Days
Data format: Unsigned 32
Read Only
PRODUCT_CODE
The manufacturers order number (MLFB) for this device.
Device Product Code
Data format: Visible string (48 bytes)
Read Only
DEVICE_SER_NUM
The manufacturers unique serial number for this device.
Device Serial Number
Data format: Visible string (32 bytes)
Read Only
HARDWARE_REVISION
The revision state of the hardware (electronics) of this field device.
Hardware Revision
Data format: Visible string (16 bytes)
Read Only
FF Communications
ITK_VER Major revision number of the interoperability test case used to register
ITK Version this device. mmmmm
MIN_CYCLE_T
The manufacturer specified minimum time to execute a cycle.
Minimum Cycle Time
Data format: Unsigned 32
Read Only
FF Communications
mmmmm
This is the mode requested by the operator. The Target Mode is limited
1. TARGET to the values allowed by the Permitted Mode Parameter.
Target Bit 3: Auto (Automatic Mode)
Read & Write Bit 7: OOS (Out of Service)
Data format: Bit string with 8 bits (1 byte)
This is the current mode of the block, which may differ from the target
based on operating conditions. Its value is calculated as part of the
2. ACTUAL
block execution.
Actual
Bit 3: Auto
Read Only
Bit 7: OOS
Data format: Bit string with 8 bits (1 byte)
Defines the modes which are allowed for an instance of the block. The
permitted mode is configured based on application requirements.
3. PERMITTED
Bit 3: Auto
Permitted
Bit 7: OOS
Read & Write
Data format: Bit string with 8 bits (1 byte)
Default value: 0x11 (Auto | OOS)
This is the mode which the block should be set to during normal
4.NORMAL operating conditions.
Normal Bit 3: Auto
Read & Write Data format: Bit string with 8 bits (1 byte)
Default value: 0x10 (Auto | OOS)
Sets the time limit for loss of communication from a remote device.
SHED_RCAS
Shed from RCAS will not occur when SHED_RCAS is set to 0.
Shed Remote Cascade
Data format: Unsigned 32
Read & Write
Default value: 640000 (20 s)
Sets the time limit for loss of communication from a remote device.
SHED_ROUT
Shed from ROUT will not occur when SHED_ROUT is set to 0.
Shed Remote Output
Data format: Unsigned 32
Read & Write
Default value: 640000 (20 s)
SOFTWARE_REVISION
FF Communications
The revision level of the static data associated with the function block.
ST_REV
The revision level will be incremented each time a static parameter in
Static Revision
the block is changed.
Read Only
Data format: Unsigned 16
TAG_DESC
The user entered description for the resource function block.
Tag Description
Data format:Octet string (32 bytes)
Read & Write
The time when evaluation of the block was started and a change in
3. TIME_STAMP event state was detected that is unreported. The time stamp value will
Time Stamp be maintained constant until alert confirmation has been received
Read only even if another change of state occurs.
Data format: Time-Value (8 bytes)
The static revision of the block whose static parameter was changed
4. STATIC_REVISION and is being reported. It is possible for the present value of the static
Static Revision revision to be greater than this because static parameters can be
Read only changed at any time.
Data format: Unsigned 16
FF Communications
The Object Dictionary (OD) index of the static parameter (minus the
5. RELATIVE_INDEX function block starting index) whose change caused the alert to occur.
Relative Index If the update event was caused by a write to multiple parameters, then
mmmmm
The time when evaluation of the block was started and a change in
alarm/event state was detected that is unreported.
3. TIME_STAMP
The time stamp value will be maintained constant until alert
Time Stamp
confirmation has been received even if another change of state
Read only
occurs.
Data format: Time-Value (8 bytes)
4. SUB_CODE
An enumeration specifying the cause of the alert to be reported.
Subcode
Data format: Unsigned 16
Read only
5. Value The value of the associated parameter at the time the alert was
FF Communications
parameter will indicate the position of the hardware jumper. When the
feature Hard Write Lock Supported is not set in FEATURES_SEL, this
WRITE_LOCK parameter can be written to Lock or Unlock writing configuration
Write Lock parameters. The hardware jumper must be in the Unlocked position
Read & Write for this feature .
1: Unlocked
2: Locked
Data format: Unsigned 8
DEVICE_ID
The product name.
Device ID
Data format: Visible string (16 bytes)
Read only
DEVICE _MESSAGE
Text that can be used in any way. Limited to 32 ASCII characters. No
Device Message
specific recommended use.
Read & Write
LOADER_REV
The revision state of the firmware boot loader of the field device.
Loader Revision
Data format: Visible string 16
Read only
POWERON_RESETS
Total number of device resets of this device electronics.
Poweron Resets
Data format: Unsigned 32
Read only
RESOURCE_BLOCK_
ERR_DESC_1 Bit-field representing each fault that can be thrown by Resource block.
Resource Block Error Data format: Unsigned 32
Description Default Value: 0
Read only
Parameter Description
The LTB contains all standard parameters as specified in [FF-891-1.7] and some
manufacturer-specific parameters. These include additional static information about the
device and several counters for operating time.
For detailed information see the following table:
Label/Name/
Description/Format
Handling
The identification number of the plant unit. This information may be
ALERT_KEY used in the host for sorting alarms, etc.
Alert Key Data format:Unsigned 8
Read & Write Value range:1 255
Default value:0
FF Communications
mmmmm
The time when evaluation of the block was started and a change in
alarm/event state was detected that is unreported.
3. TIME_STAMP
The time stamp value will be maintained constant until alert
Time Stamp
confirmation has been received even if another change of state
Read only
occurs.
Data format: Time-Value (8 bytes)
Read only
5. Value The value of the associated parameter at the time the alert was
Value detected.
Read only Data format:Unsigned 8
CAL_POINT_HI
The maximum adjustment point of the sensor in CAL_UNIT units used
Calibration Point High
during the last calibration. Data format:Float value (4 bytes)
Read & Write
CAL_POINT_LO
The minimum adjustment point of the sensor in CAL_UNIT units used
Calibration Point Low
during the last calibration. Data format:Float value (4 bytes)
Read & Write
This is the current mode of the block, which may differ from the target
based on operating conditions. Its value is calculated as part of the
2. ACTUAL
block execution.
Actual
Bit 3:Auto
Read Only
Bit 7:OOS
Data format:Bit string with 8 bits (1 byte)
Defines the modes which are allowed for an instance of the block.
The permitted mode is configured based on application requirements.
3. PERMITTED
Bit 3:Auto
Permitted
Bit 7:OOS
Read & Write
Data format: Bit string with 8 bits (1 byte)
Default value:0x11 (Auto | OOS)
This is the mode which the block should be set to during normal
operating conditions.
4.NORMAL
Bit 3:Auto
Normal
Data format:Bit string with 8 bits (1 byte)
Read & Write
Default value:0x10 (Auto)
The primary variable and the channel 1 output from the transducer
PRIMARY_VALUE(Record)
block.
Primary Value
Data format:Record with 2 parameters (5 bytes)
1. STATUS The status of the primary variable. Includes QUALITY, LIMITS, &
Status SUBSTATUS attributes for the value.
FF Communications
Read & Write Data format:Unsigned 8
Value PRIMARY_VALUE_RANGE.UNITS_INDEX
Read Only Data format:Float value (4 bytes)
1. EU_100 The engineering unit value which represents the upper end of the
EU at 100% range associated with the primary variable.
Read Only Data format:Float value (4 bytes)
2. EU_0 The engineering unit value which represents the lower end of the
EU at 0% range associated with the primary variable.
Read Only Data format:Float value (4 bytes)
3. UNITS_INDEX
The Device Description units code index for the primary variable.
Units Index
Data format:Unsigned 16
Read Only
4. DECIMAL The number of digits to the right of the decimal point to be used by an
Decimal interface device for displaying the primary variable.
Read Only Data format:Unsigned 8
FF Communications
mmmmm
This value is used in the simulation of the primary variable when the
1. FIXED_VALUE
fixed value simulation is selected.
Fixed Value
Data format:Float value (4 bytes)
Read & Write
Default value:0
This value is used as the starting point in the simulation of the primary
2. MINIMUM_VALUE
variable when ramp simulation is selected.
Minimum Value
Data format:Float value (4 bytes)
Read & Write
Default value:0
This value is used as the ending point in the simulation of the primary
3. MAXIMUM_VALUE
variable when ramp simulation is selected.
Maximum Value
Data format:Float value (4 bytes)
Read & Write
Default value:0
1. STATUS The status of the secondary variable. Includes QUALITY, LIMITS, &
Status SUBSTATUS attributes for the value.
Read & Write Data format:Unsigned 8
The high & low range limit values, the engineering units, and the
SENSOR_RANGE (Record) number of digits to the right of the decimal point to be used to display
Sensor Range the sensor input.
Data format: Record with 4 parameters (11 bytes)
1. EU_100 The engineering unit value which represents the upper end of the
EU at 100% range associated with the sensor input.
Read Only Data format: Float value (4 bytes)
2. EU_0 The engineering unit value which represents the lower end of the
EU at 0% range associated with the sensor input.
Read Only Data format:Float value (4 bytes)
3. UNITS_INDEX
The Device Description units code index for the sensor input.
Units Index
Data format:Unsigned 16
Read Only
The revision level of the static data associated with the function block.
ST_REV
The revision level will be incremented each time a static parameter in
Static Revision
the block is changed.
Read Only
Data format:Unsigned 16
FF Communications
TAG_DESC
The user entered description for the level transducer block.
Tag Description
Data format:Octet string (32 bytes)
Read & Write
A directory that lists the number and starting index for transducers in
TRANSDUCER_ DIRECTORY
the transducer block.
Transducer Directory
Data format: Unsigned 16
Read Only
Default value:0x0000
The time when evaluation of the block was started and a change in
3. TIME_STAMP event state was detected that is unreported. The time stamp value
Time Stamp will be maintained constant until alert confirmation has been received
Read only even if another change of state occurs.
Data format: Time-Value (8 bytes)
The static revision of the block whose static parameter was changed
4. STATIC_REVISION and is being reported. It is possible for the present value of the static
Static Revision revision to be greater than this because static parameters can be FF Communications
Read only changed at any time.
Data format:Unsigned 16 mmmmm
The Object Dictionary (OD) index of the static parameter (minus the
5. RELATIVE_INDEX function block starting index) whose change caused the alert to
Relative Index occur. If the update event was caused by a write to multiple
Read Only parameters, then the attribute will be set to 0.
Data format:Unsigned 16
Note: If more than one Analog Input has the same source the input units
FF Communications
(XD_SCALE) of all analog input blocks must have the same value.
Otherwise a configuration error will occur.
mmmmm
1.
Volume only if supported by instrument.
Label/Name/Handling Description/Format
Selection of whether alarms associated with the block will be
automatically acknowledged.
Bit Clear (0): Auto Acknowledge is Disabled
Bit Set (1): Auto Acknowledge is Enabled
Bit 0: Unacknowledged Alarm 1
Bit 1: Unacknowledged Alarm 2
Bit 2: Unacknowledged Alarm 3
Bit 3: Unacknowledged Alarm 4
Bit 4: Unacknowledged Alarm 5
ACK_OPTION Bit 5: Unacknowledged Alarm 6
Acknowledge Option Bit 6: Unacknowledged Alarm 7
Read & Write Bit 7: Unacknowledged Alarm 8
Bit 8: Unacknowledged Alarm 9
Bit 9: Unacknowledged Alarm 10
Bit 10: Unacknowledged Alarm 11
Bit 11: Unacknowledged Alarm 12
Bit 12: Unacknowledged Alarm 13
Bit 13: Unacknowledged Alarm 14
Bit 14: Unacknowledged Alarm 15
Bit 15: Unacknowledged Alarm 16
Data format: Bit string with 16 bits (2 bytes)
FF Communications
mmmmm
The time when evaluation of the block was started and a change
in alarm/event state was detected that is unreported.
3. TIME_STAMP
The time stamp value will be maintained constant until alert
Time Stamp
confirmation has been received even if another change of state
Read only
occurs.
Data format: Time-Value (8 bytes)
5. Value The value of the associated parameter at the time the alert was FF Communications
Value detected.
Read only Data format: Unsigned 8 mmmmm
1. STATUS The status of the Field Value variable. Includes QUALITY, LIMITS,
Status & SUBSTATUS attributes for the value.
Read & Write Data format: Unsigned 8
2. VALUE
The Field Value in % of XD_SCALE range
Value
Data format: Float value (4 bytes)
Read Only
The time when evaluation of the block was started and a change
in alarm/event state was detected that is unreported.
3. TIME_STAMP
The time stamp value will be maintained constant until alert
Time Stamp
confirmation has been received even if another change of state
Read only
occurs.
Data format: Time-Value (8 bytes)
4. SUB_CODE
An enumeration specifying the cause of the alert to be reported.
Subcode
Data format: Unsigned 16
Read only
5. Value The value of the associated parameter at the time the alert was
Value detected.
Read only Data format: Unsigned 8
The limit setting used to detect the High High Alarm condition. FF Communications
HI_HI_LIM
The setting is in OUT_SCALE engineering units.
High High Limit
Data format: Float value (4 bytes)
mmmmm
The limit setting used to detect the High Alarm condition. The
HI_LIM
setting is in OUT_SCALE engineering units.
High Limit
Data format: Float value (4 bytes)
Read & Write
Default value: 1.# INF
LO_ALARM(Record) The status and time stamp associated with the Low Alarm.
Low Alarm Data format: Record with 5 parameters (13 bytes)
The limit setting used to detect the Low Alarm condition. The
LO_LIM
setting is in OUT_SCALE engineering units.
Low Limit
Data format: Float value (4 bytes)
Read & Write
Default value: 1.# INF
LO_LO_ALARM(Record) The status and time stamp associated with the Low Low Alarm.
Low Low Alarm Data format: Record with 5 parameters (13 bytes)
The limit setting used to detect the Low Low Alarm condition.
LO_LO_LIM
The setting is in OUT_SCALE engineering units.
Low Low Limit
Data format: Float value (4 bytes)
Read & Write
Default value: 1.# INF
When the scaled output signal falls below this value, the PV will
go to 0.0 as determined by the PV filter time constant. This
LOW_CUT function is active when the IO_OPTS Bit 10 is set and is only
Low Cutoff useful for 0 based signals such as flow.
Read & Write Data format:Float value (4 bytes) must be a positive
number
Default value: 0.0
FF Communications
mmmmm
This is the current mode of the block, which may differ from the
target based on operating conditions. Its value is calculated as
2. ACTUAL part of the block execution.
Actual Bit 3: Auto
Read Only Bit 4: Man
Bit 7: OOS
Data format: Bit string with 8 bits (1 byte)
This is the mode which the block should be set to during normal
4.NORMAL operating conditions.
Normal Bit 3: Auto
Read & Write Data format: Bit string with 8 bits (1 byte)
Default value: 0x10 (Auto)
1. STATUS The status of the OUT variable. Includes QUALITY, LIMITS, &
Status SUBSTATUS attributes for the value.
Read & Write Data format: Unsigned 8
mmmmm
2. VALUE
The OUT Value in engineering units of OUT_SCALE range
Value
Data format:Float value (4 bytes)
Read Only
1. EU_100 The engineering unit value which represents the upper end of
EU at 100% the range associated with the block output.
Read & Write Data format:Float value (4 bytes)
2. EU_0 The engineering unit value which represents the lower end of the
EU at 0% range associated with the block output.
Read & Write Data format: Float value (4 bytes)
The Device Description units code index for the block output.
3. UNITS_INDEX
Note: Refer to Foundation Fieldbus Specification Ff-131 FS 1.0
Units Index
section 3 for a complete listing of unit index codes.
Read & Write
Data format: Unsigned 16
4. DECIMAL The number of digits to the right of the decimal point to be used
Decimal by an interface device for displaying the block output.
Read & Write Data format: Unsigned 8
1. STATUS The status of the Process Variable. Includes QUALITY, LIMITS, &
Status SUBSTATUS attributes for the value.
Read & Write Data format: Unsigned 8
2. VALUE
The Process Variable in engineering units of OUT_SCALE range
Value
Data format: Float value (4 bytes)
Read Only
2. SIMULATE_VALUE The value of the simulation variable in the units of the transducer
Simulation Value block output.
Read & Write Data format: Float value (4 bytes)
3. TRANSDUCER_STATUS
The actual status of the transducer block output.
Transducer Status
Data format: Unsigned 8
Read Only
4. TRANSDUCER_VALUE
The actual value of the transducer output.
Transducer Value
Data format: Float value (4 bytes)
Read Only
The revision level of the static data associated with the function
ST_REV
block. The revision level will be incremented each time a static
Static Revision
parameter in the block is changed.
Read Only
Data format: Unsigned 16
Enables the selection of options for the analog input block. The
following options are available:
Bit 3: Propagate Fault Forward
STATUS_OPTS
Bit 6: Uncertain if Limited
Status Options
Bit 7: BAD if Limited
FF Communications
TAG_DESC
The user entered description for theAIFB.
Tag Description
Data format: Octet string (32 bytes)
Read & Write
The time when evaluation of the block was started and a change
3. TIME_STAMP in event state was detected that is unreported. The time stamp
Time Stamp value will be maintained constant until alert confirmation has
Read only been received even if another change of state occurs.
Data format: Time-Value (8 bytes)
1. EU_100 The engineering unit value which represents the upper end of
EU at 100% the range associated with the channel input.
Read & Write Data format: Float value (4 bytes)
2. EU_0 The engineering unit value which represents the lower end of the
EU at 0% range associated with the channel input.
Read & Write Data format: Float value (4 bytes)
The Device Description units code index for the channel input.
3. UNITS_INDEX
This UNITS_INDEX must match the UNITS_INDEX of the
Units Index
transducer or the block will not transition to Man or Auto
Read & Write
Data format: Unsigned 16
4. DECIMAL The number of digits to the right of the decimal point to be used
Decimal by an interface device for displaying the channel input.
Read & Write Data format: Unsigned 8
Parameter Description
FF Communications
The LCD transducer block contains all standard parameters as specified in [FF-891-1.7]
and some manufacturer specific parameters.
mmmmm
Label/Name/
Description/Format
Handling
The identification number of the plant unit. This information may be
ALERT_KEY used in the host for sorting alarms, etc.
Alert Key Data format: Unsigned 8
Read & Write Value range: 1 255
Default value: 0
The time when evaluation of the block was started and a change in
alarm/event state was detected that is unreported.
3. TIME_STAMP
The time stamp value will be maintained constant until alert
Time Stamp
confirmation has been received even if another change of state
Read only
occurs.
Data format: Time-Value (8 bytes)
5. Value The value of the associated parameter at the time the alert was
mmmmm
Value detected.
Read only Data format: Unsigned 8
This parameter reflects the error status associated with the hardware
BLOCK_ERR or software components associated with a block. It is a bit string, so
Block Error that multiple errors may be shown. The following bits are supported:
Read Only Bit 15: Out of Service Actual mode is Out of Service
Data format: Bit string with 16 bits (2 bytes)
This is the mode requested by the operator. The Target Mode is limited
1. TARGET to the values allowed by the Permitted Mode Parameter.
Target Bit 3: Auto (Automatic Mode)
Read & Write Bit 7: OOS (Out of Service)
Data format: Bit string with 8 bits (1 byte)
This is the current mode of the block, which may differ from the target
based on operating conditions. Its value is calculated as part of the
2. ACTUAL
block execution.
Actual
Bit 3: Auto
Read Only
Bit 7: OOS
Data format: Bit string with 8 bits (1 byte)
Defines the modes which are allowed for an instance of the block. The
permitted mode is configured based on application requirements.
3. PERMITTED
Bit 3: Auto
Permitted
Bit 7: OOS
Read & Write
Data format: Bit string with 8 bits (1 byte)
Default value: 0x11 (Auto | OOS)
This is the mode which the block should be set to during normal
4.NORMAL operating conditions.
Normal Bit 3: Auto
Read & Write Data format: Bit string with 8 bits (1 byte)
Default value: 0x10 (Auto)
The revision level of the static data associated with the function block.
ST_REV
The revision level will be incremented each time a static parameter in
Static Revision
the block is changed.
Read Only
Data format: Unsigned 16
STRATEGY
The Strategy parameter can be used to identify groupings of blocks.
FF Communications
The data is not checked or processed by the block.
Strategy
Data format: Unsigned 16
Read & Write
Default value: 0
mmmmm
TAG_DESC
The user entered description for the LCD transducer function block.
Tag Description
Data format: Octet string (32 bytes)
Read & Write
TRANSDUCER_ A directory that lists the number and starting index for transducers in
DIRECTORY the transducer block.
Transducer Directory Data format: Unsigned 16
Read Only Default value: 0x0000
UPDATE_EVT
This alert is generated by any change to the static data.
(Record)
Data format: Record with 5 parameters (14 bytes)
Update Event
The time when evaluation of the block was started and a change in
3. TIME_STAMP event state was detected that is unreported. The time stamp value will
Time Stamp be maintained constant until alert confirmation has been received
Read only even if another change of state occurs.
Data format:Time-Value (8 bytes)
The static revision of the block whose static parameter was changed
FF Communications
4. STATIC_REVISION and is being reported. It is possible for the present value of the static
Static Revision revision to be greater than this because static parameters can be
Read only changed at any time.
mmmmm
The Object Dictionary (OD) index of the static parameter (minus the
5. RELATIVE_INDEX function block starting index) whose change caused the alert to occur.
Relative Index If the update event was caused by a write to multiple parameters, then
Read Only the attribute will be set to 0.
Data format:Unsigned 16
FF Communications
mmmmm
Notes
IQ300IX.fm Page 5 Tuesday, October 2, 2001 1:43 PM
www.siemens.com/processautomation
www.siemens.com/continuous-weighing
Siemens Milltronics Process Instruments Inc. Subject to change without prior notice
Industry Automation (IA) 7ML19985MP01 Rev. 1.0
1954 Technology Drive
P.O. Box 4225
Peterborough, ON
Canada K9J 7B1
Siemens Milltronics Process Instruments Inc. 2010
*7ml19985MP01*
Printed in Canada
email: techpubs.smpi@siemens.com
www.siemens.com/processautomation