Professional Documents
Culture Documents
Geh-6761 G PDF
Geh-6761 G PDF
Related Documents
Doc # Title
GEI-100757 WorkstationST* Device Manager Gateway Instruction Guide
GEI-100758 Mark VIe Control FOUNDATION Fieldbus Block Library Instruction Guide
Mark VIe and Mark VIeS Control Systems Manual, Volume II, the chapter, PFFA FOUNDATION
GEH-6721_Vol_II
Fieldbus Function Block Parameters Fieldbus Linking Device
ControlST* Software Suite How-to Guides, the section, How to Qualify a FOUNDATION Fieldbus
GEH-6808
Function Block Parameters Fieldbus Field Device
ToolboxST* User Guide for Mark* Controls Platforms, the chapter Mark VIe Control FOUNDATION
GEH-6700
Fieldbus Function Block Parameters Fieldbus Integration
Note For compatibility testing guidelines and further details, refer to the ControlST Software Suite How-to Guides
(GEH-6808), the section How to Qualify a FOUNDATION Fieldbus Field Device.
1.1 Features
FOUNDATIONfieldbus features include:
Switches
IONet - HSE
100 MB Ethernet
RS232
Serial Redundant
Linking Devices
Redundant
Power Conditioners
Field Devices
1.2.1 H1
H1 is a fieldbus network operating at 31.25 kbit/s. The H1 network interconnects devices such as pressure or temperature
transmitters and actuators on a field network. It is designed to operate on existing twisted pair instrument cabling with power
and signal on the same wire. H1 supports intrinsic safety (IS) applications.
Note PFFA is not rated for Intrinsic Safety (IS) but IS is part of the H1 standard. Refer to drawing 238A7779 for guidelines,
rules, and technology for using IS with H1.
H1 devices contain a function block application, act as a publisher and subscriber of process variables, transmit alarms and
trends, and provide server functionality for host access and management functions. Devices can act as a scheduler and time
master for regulating communication on a fieldbus segment. They are also used for bus interfaces in process control systems
or in linking devices. Capable of controlling bus communications and many connections to multiple devices, they support
both client and server applications.
H1 technology enables field instruments and other devices to perform control functions reducing the load on plant computers
and workstations. Since the H1 network is digital, I/O conversion subsystems are eliminated.
1.2.2 HSE
Like H1, HSE is an international standard (IEC™ 61158). HSE is used as a control backbone. Running at 100 Mbit/s, the
technology is designed for device, subsystem and enterprise integration. It supports the entire range of fieldbus capabilities,
including standard function blocks and device descriptions (DDs), as well as application-specific flexible function blocks
(FFBs) for advanced process and discrete/hybrid/batch applications.
HSE supports complex logic functions for data-intensive process devices, such as analyzers and gateways to other networks.
HSE enhances access to H1 fieldbus technology by way of linking devices, while providing expanded capabilities for
high-speed automation devices and hybrid or batch applications.
HSE provides the same benefits as H1, but at the subsystem integration level instead of the field device level. It supports
interoperability between disparate controllers and gateways in the same way that H1 supports interoperability between
transmitters and actuators from different suppliers. FFBs in HSE devices can be set up using programming languages such as
those found in the international standard IEC 61131-3.
HSE also supports standard Ethernet wiring, including the use of fiber-optic cable to provide cost-effective electrical isolation
between plant areas or immunity from distortion through noisy environments.
• Gateway between an Ethernet (HSE) port and four fieldbus (H1) ports
• Supports up to 16 field devices per segment
• Supports up to four separate H1 links. In each of these links, the Linking Device operates as the Link Master and the
System Management (SM) Time Publisher.
• Identification of the devices connected to the H1 links
• Configuration of the connected H1 devices by System Management and Network Management through HSE
• Access to the function blocks of the connected H1 devices through HSE
• Republishing of process data from one H1 link to another
• Republishing of process data from H1 to HSE and vice versa
Note Refer to the Mark VIe and Mark VIeS Control Systems Manual, Volume II (GEH-6721 Vol II), the chapter PFFA
FOUNDATION Fieldbus Linking Device.
1.2.4 Blocks
To ensure device interoperability FOUNDATION fieldbus technology uses a fully specified, standard user layer based on blocks
and device descriptions (DDs). The user layer defines a function block application process (FBAP) using resource blocks,
function blocks, transducer blocks, system management, network management, and DD technology.
Resource blocks define parameters that pertain to the entire application process (for example, manufacturing ID, device type,
and so forth). Function blocks encapsulate control functions (for example, PID controller, analog input, and so forth) and
transducer blocks offer an interface to sensors such as temperature, pressure, and flow, and actuators for valves.
Blocks are incorporated into fieldbus devices to achieve the desired device functionality, as well as to define a wide range of
features and behaviors that must work in a standard way for devices to interoperate. For example, a simple temperature
transmitter can contain an analog input (AI) function block. A control valve might contain a proportional/integral/derivative
(PID) function block as well as the expected analog output (AO) block. Thus, a complete control loop can be built using only
a simple transmitter and a control valve.
• FOUNDATION fieldbus blocks appear in the controller in special FOUNDATION fieldbus tasks. FOUNDATION fieldbus tasks in
the controller perform at the macrocycle rate for the slowest macrocycle that contains a block in the task.
• Segment macrocycle is determined by the number of devices on a FOUNDATION fieldbus segment, the number of blocks
used in devices on a segment, the interconnections between blocks (in the same or different devices) on a FOUNDATION
fieldbus segment, and minimum macrocycle requirements by device manufacturers.
Note Refer to the ToolboxST User Guide for Mark Controls Platforms (GEH-6700), the chapter Mark VIe Control
FOUNDATION Fieldbus Interface, the section Attached Segments for information regarding macrocycle and macrocycle
timeline.
• Macrocycle and controller task execution rate are not synchronized. It may take as much as one task execution time plus
one macrocycle time to complete the control strategy in a task. Information about the macrocycle timeline can be
obtained from the Macrocycle Timeline Viewer as displayed in the following figure.
• Macrocycle is constrained to be a binary multiple of frame rate. The macrocycle contains time reserved for scheduled
(synchronous) and unscheduled (asyncronous) tasks. The segment Unscheduled Overhead Percent property (time
allowed for asynchronous communications) can be configured for 30%, 40%, or 50% of the total macrocycle time. If
more than the configured time is consumed, the next longest macrocycle is selected by the system.
Note Refer to the ToolboxST User Guide for Mark Controls Platforms (GEH-6700), the chapter Mark VIe Control
FOUNDATION Fieldbus Interface, the section Configure an Attached Segment Macrocycle for additional information.
Note Refer to the ToolboxST User Guide for Mark Controls Platforms (GEH-6700), the chapter Mark VIe Control
FOUNDATION Fieldbus Interface for information on configuring fieldbus devices.
The addition of fieldbus devices to a H1 segment involves the use of a placeholder. A fieldbus device placeholder is a
representation of a fieldbus device. They are created inside a Mark VIe controller. Before a placeholder can be tied to a
physical fieldbus device, it must go through the commissioning process. After commissioning, the fieldbus device becomes
live and active in the system and is included in the download process of the controller.
If you delete an H1 device that has associated blockware, perform a build of the
controller before you insert a new H1 device on the segment. This build will result in
errors if there are any function blocks on the Software tab that were assigned to the
H1 device that was deleted. These function blocks either need to be deleted or
unassigned and re-assigned to another H1 device block on that segment before a
successful build will occur. If these blocks are not unassigned and re-assigned, then
Attention there is a possibility that an inserted H1 device will generate the PDTags necessary for
the blockware to assume that the original H1 device is present and it will not rebuild
the macrocycle. This could potentially lead to build and download errors.
As part of the commissioning process in the ToolboxST application, a physical H1 device must be matched to a placeholder.
In order for the ToolboxST application to know whether the correct H1 device is present, certain parameters that detail what
the device is and its version are read from the DD files. When configuring a fieldbus device, the device type and revision
number must be the same as those in the ToolboxST application or the commissioning of the device produces an error. The
DD file version in the ToolboxST application can be higher (but not lower) than the one in the device.
The ToolboxST application's block palette for a special fieldbus task displays the generic FOUNDATION fieldbus function
blocks in a fieldbus category in addition to the traditional Mark VIe control function block categories. FOUNDATION fieldbus
function blocks can only be used in the special FOUNDATION fieldbus task. Mark VIe control function blocks are also allowed
to operate in this special task in addition to the normal Mark VIe control tasks.
• As FOUNDATION fieldbus segment loading is increased, live data update time may also increase.
• A minimum FOUNDATION fieldbus macrocycle of 320 mS is recommended; shorter macrocycles may result in
inconsistent inputs during redundancy fail-overs.
• The Mark VIe system can accommodate one alert transition per second without queuing. To improve the likelihood that
alert data is not dropped during periods of burst activity, use native Mark VIe analog alarms instead of FOUNDATION
fieldbus alerts.
• The Mark VIe controller is capable of supporting up to 200 PAIC-equivalent I/O packs per IONet. Each PFFA represents
a load of five PAIC equivalent I/O packs to the system.
Configuration Example:
An engineer wants to configure a system with 1100 Motor Operated Valves (MOVs) on FOUNDATION fieldbus and therefore
needs to understand the minimum amount of Mark VIe hardware required to support it. Each MOV currently requires four
VCRs.
Dividing the total number of devices (1100) by the number supportable per segment (16) yields a minimum of 69 H1
segments necessary. Since each PFFA can support four segments, the minimum number of PFFAs required is 69/4, or 18.
Further, since a single IONet can support up to 20 PFFAs only one IONet is required for this application. The MOVs will
generate 4400 VCRs, which spread evenly across 18 PFFAs comes to 244 per linking device. This number of VCRs is well
within the limit of 400 for a single PFFA, as well as the limit of 2048 for a single controller. The minimum hardware
necessary to achieve this configuration is therefore a single Mark VIe controller, using a single IONet, with 18 fully populated
PFFAs. Other specifications may drive the need for additional hardware (for example, application code loading, redundancy,
spares, or partitioning for functionality, and so forth).
Arithmetic FF_AR
Integrator FF_IT
Multiple Analog
FF_MAI
Input
Multiple Analog
FF_MAO
Output
Multiple Discrete
FF_MDI
Input
Multiple Discrete
FF_MDO
Output
P, PD Controller FF_PD
Setpoint Ramp
FF_SPG
Generator
Timer FF_TMR
Unassigned Unassigned
Note Refer to the ToolboxST User Guide for Mark Controls Platforms (GEH-6700), the chapter Mark VIe Control
FOUNDATION Fieldbus Interface, for information on assigning FOUNDATION fieldbus function blocks.
In the block editing space, unassigned generic FOUNDATION fieldbus function blocks display Unassigned, in black lettering,
where the PD tag would be for an assigned function block. A question mark icon ( ) displays in the upper right-hand
corner in place of the operational icon displayed for as assigned function block.
Assigned fieldbus function blocks display the PD tag of the fieldbus device the function block is assigned to in blue lettering.
They also display a specific operational icon in the upper right-hand corner that identifies the block’s function. The
operational icon replaces the question mark icon of the unassigned function block.
Only Mark VIe function blocks are given execution orders because the fieldbus function block execution order in the
macrocycle is determined by connection.
Mixed FOUNDATION Fieldbus Function Block and Mark VIe Function Block Example
• Less complex
• Can support task configurations with multiple segments and multiple linking device
• Synchronous execution among controllers
Note Refer to Appendix A FOUNDATION Fieldbus Function Block Parameters for a list of the block parameters and their
descriptions.
To support homogeneity with the ToolboxST application, fieldbus parameters that are listed on a function block’s View 1
parameter list can be placed on EGD. Parameters on EGD display the following properties in the Hardware tab parameter
grid:
• Indication in the linking device Summary View if the linking device is online
− If the linking device is not in the Live List, the linking device is not online
− If no Live List is emitting from the linking device, the linking device is not online
Note Refer to the Mark VIe and Mark VIeS Control Systems Manual, Volume II (GEH-6721 Vol II), the chapter PFFA
FOUNDATION Fieldbus Linking Device.
Error, warning, and informational symbols display on the linking device in the Hardware tab Summary View. This
information is provided by the alarm and diagnostic subsystems inside the Mark VIe controller.
– If the fieldbus device is not in the Live List, a red X ( ) displays, the fieldbus
device is not online
Note When a fieldbus device is added to a system, it acts as a placeholder until it is commissioned. The commissioning
process makes the fieldbus device live and active in the system.
The ToolboxST application classifies a fieldbus device in one of the following states:
• Uninitialized State
− Fieldbus device does not have a PD_TAG
− Fieldbus device does not have a permanent node address
– Overlay symbol:
• Initialized State
− Fieldbus device has a PD_TAG
− Fieldbus device does not have a permanent node address
− Fieldbus device revisions match placeholder revisions
– Overlay symbol:
• Commissioned State
− Fieldbus device has a PD_TAG
− Fieldbus device has a permanent node address
– Overlay symbol:
• Mismatch State
− Fieldbus device revisions have not been obtained. Check for a communications failure diagnostic to determine if
there is a problem or if it is just taking a while to update.
− Fieldbus device revisions do not match the placeholder revisions. Re-add the placeholder using a DD file matching
the revisions.
− Fieldbus device has a node address collision with a fieldbus device placeholder of a different type
− Fieldbus device has a node address that does not exist in the ToolboxST configuration
− No DD files are available for the fieldbus device in the ToolboxST DD file database
– Overlay symbol:
• Indicate the PD tag of the device to which the FOUNDATION fieldbus function block is assigned.
• Display the description of the assigned FOUNDATION fieldbus function block.
• Display the assigned FOUNDATION fieldbus function block’s View 1 parameters from EGD.
• Write to those parameters where the actual mode of the target block allows write access.
• Perform the Goto logic function to enable opening the special fieldbus task that references the assigned FOUNDATION
fieldbus function block.
The following FOUNDATION fieldbus blocks have a smart object configured:
• FF_AI
• FF_AO
• FF_DI
• FF_DO
• FF_PID
The ToolboxST application only supports the drag-and-drop of assigned fieldbus function blocks, configured to put View 1 on
EGD, onto a CIMPLICITY HMI screen. The ToolboxST application populates the clipboard with the proper data to enable
the CIMPLICITY smart object to function properly.
Note The drag-and-drop of other blocks is not prevented, but they will not function.
Parameters
The following is a description of each block parameter and its intended use.
ACK_OPTION Selection of whether alarms associated with the block is automatically acknowledged.
ALARM_HYS Amount the PV must return within the alarm limits before the alarm condition clears. Alarm Hysteresis is
expressed as a percent of the PV span.
ALARM_SUM The current alert status, unacknowledged states, unreported states, and disabled states of the alarms
associated with the function block.
ALERT_KEY The identification number of the plant unit. This information may be used in the host for sorting alarms, etc.
BAL_TIME The difference value used in the block calculation for bumpless transfer should ramp to zero in the time
specified by BAL_TIME.
BIAS The bias value used in computing the function block output, expressed in engineering units.
BKCAL_HYS The amount that the output must change away from its output limit before the limit status is turned off,
expressed as a percent of the span of the output.
BKCAL_IN The value and status from a lower block's BKCAL_OUT that is used to prevent reset windup and to initialize
the control loop.
BKCAL_OUT The value and status required by an upper block’s BKCAL_IN so that the upper block may prevent reset
windup and provide bumpless transfer to closed loop control.
BKCAL_OUT_D The output value and status provided to an upstream discrete block. This information is used to provide
bumpless transfer to closed loop control.
BKCAL_SEL_1 Control elector output value and status associated with SEL_1 input which is provided to BKCAL_IN of
the block connected to SEL_1 to prevent reset windup.
BKCAL_SEL_2 Control selector output value and status associated with SEL_2 input which is provided to BKCAL_IN
of the block connected to SEL_2 to prevent reset windup.
BLOCK_ALM The 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 sets the Active status in the Status
attribute. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported without
clearing the Active status, if the subcode has changed.
BLOCK_ERR This parameter reflects the error status associated with the hardware or software components associated
with a block. It is a bit string, so that multiple errors may be displayed.
BYPASS The normal control algorithm may be bypassed through this parameter. When bypass is set, the setpoint value (in
percent) is directly transferred to the output. To prevent a bump on transfer to/from bypass, the setpoint is automatically
initialized to the output value or process variable, respectively, and the path broken flag is set for one execution.
CAS_IN This parameter is the remote setpoint value, which must come from another Fieldbus block, or a DCS block
through a defined link.
CAS_IN_D This parameter is the remote setpoint value of a discrete block, which must come from another Fieldbus block,
or a DCS block through a defined link.
CHANNEL The number of the logical hardware channel that is connected to this I/O block. This information defines the
transducer to be used going to or from the physical world.
CLR_FSTATE Writing a Clear to this parameter clears the device fault state if the field condition, if any, has cleared.
CONFIRM_TIME The time the resource waits for confirmation of receipt of a report before trying again. Retry shall not
happen when CONFIRM_TIME = 0.
CONTROL_OPTS Options which the user may select to alter the calculations done in a control block.
CYCLE_SEL Used to select the block execution method for this resource.
CYCLE_TYPE Identifies the block execution methods available for this resource.
DD_RESOURCE String identifying the tag of the resource which contains the Device Description for this resource.
DD_REV Revision of the DD associated with the resource - used by an interface device to locate the DD file for the
resource.
DEV_REV Manufacturer revision number associated with the resource - used by an interface device to locate the DD file
for the resource.
DISC_ALM The status and time stamp associated with the discrete alarm.
DV_HI_ALM The status and time stamp associated with the high deviation alarm.
DV_HI_LIM The setting of the high deviation alarm limit in engineering units.
DV_LO_ALM The status and time stamp associated with the low deviation alarm.
DV_LO_LIM The setting of the low deviation alarm limit in engineering units.
FAULT_STATE Condition set by loss of communication to an output block, fault promoted to an output block or a
physical contact. When Fault State condition is set, Then output function blocks perform their FSTATE actions.
FF_GAIN The gain that the feed forward input is multiplied by before it is added to the calculated control output.
FF_SCALE The feedforward input high and low scale values, engineering units code, and number of digits to the right of
the decimal point.
FIELD_VAL Raw value of the field device in percent of thePV range, with a status reflecting the Transducer condition,
before signal characterization (L_TYPE) or filtering (PV_FTIME).
FIELD_VAL_D Raw value of the field device discrete input, with a status reflecting the Transducer condition.
FREE_SPACE Percent of memory available for further configuration. Zero in a preconfigured resource.
FREE_TIME Percent of the block processing time that is free to process additional blocks.
FSTATE_TIME The time in seconds from detection of fault of the output block remote setpoint to the output action of the
block output if the condition still exists.
FSTATE_VAL_D The preset discrete SP_D value to use when fault occurs. This value is used if the I/O option Fault State
to value is selected.
GAIN Dimensionless value used by the block algorithm in calculating the block output.
GRANT_DENY Options for controlling access of host computer and local control panels to operating, tuning and alarm
parameters of the block.
HI_ALM The status for high alarm and its associated time stamp.
HI_HI_ALM The status for high high alarm and its associated time stamp.
IO_OPTS Options which the user may select to alter input and output block processing.
IN The primary input value of the block, required for blocks that filter the input to get the PV.
IN_1 Auxiliary input value to the block, used for other values than the PV.
ITK_VER Major revision number of the interoperability test case used in certifying this device as interoperable. The
format and range of the version number is defined and controlled by the Fieldbus Foundation. Note: The value of this
parameter is zero (o) if the device has not been registered as interoperable by the FF.
L_TYPE Determines if the values passed by the transducer block to the AI block may be used directly (Direct) or if the
value is in different units and must be converted linearly (Indirect), or with square root (Ind Sqr Root), using the input range
defined by the transducer and the associated output range.
LO_ALM The status of the low alarm and its associated time stamp.
LOW_CUT Limit used in square root processing. A value of zero percent of scale is used in block processing if the
transducer value falls below this limit. This feature may be used to eliminate noise near zero for a flow sensor.
MANUFAC_ID Manufacturer identification number - used by an interface device to locate the DD file for the resource.
MEMORY_SIZE Available configuration memory in the empty resource. To be checked before attempting a download.
MIN_CYCLE_T Time duration of the shortest cycle interval of which the resource is capable.
MODE_BLK The actual, target, permitted, and normal modes of the block.
NV_CYCLE_T Minimum time interval specified by the manufacturer for writing copies of NV parameters to non-volatile
memory. Zero means it is never automatically copied. At the end of NV_CYCLE_TIME, only those parameters which have
changed (as defined by the manufacturer) need to be updated in NVRAM.
OUT The primary analog value calculated as a result of executing the function.
OUT_D The primary discrete value calculated as a result of executing the function.
OUT_SCALE The high and low scale values, engineering units code, and number of digits to the right of the decimal
point to be used in displaying the OUT parameter and parameters which have the same scaling as OUT.
PV Either the primary analog value for use in executing the function, or a process value associated with it. May also be
calculated from the READBACK value of an AO block.
PV_D Either the primary discrete value for use in executing the function, or a process value associated with it. May also be
calculated from the READBACK_D value of a DO block.
PV_SCALE The high and low scale values, engineering units code, and number of digits to the right of the decimal point
to be used in displaying the PV parameter and parameters which have the same scaling as PV.
RA_FTIME Time constant of a single exponential filter for the value to be ratioed, in seconds.
RCAS_IN Target setpoint and status provided by a supervisory Host to a analog control or output block.
RCAS_IN_D Target setpoint and status provided by a supervisory Host to a discrete control or output block.
RCAS_OUT Block setpoint and status after ramping - provided to a supervisory Host for back calculation and to allow
action to be taken under limiting conditions or mode change.
RCAS_OUT_D Block setpoint and status provided to a supervisory Host for back calculation and to allow action to be
taken under limiting conditions or mode change.
READBACK This indicates the readback of the actual continuous valve or other actuator position, in transducer units.
READBACK_D This indicates the readback of the actual discrete valve or other actuator position, in the transducer state.
RESTART Allows a manual restart to be initiated. Several degrees of restart are possible. They are 1: Run, 2: Restart
resource, 3: Restart with defaults, and 4: Restart processor.
ROUT_IN Target output and status provided by a Host to the control block for use as the output (ROut mode).
ROUT_OUT Block output and status - provided to a Host for back calculation in ROut mode and to allow action to be
taken under limited conditions or mode change.
SET_FSTATE Allows the Fault State condition to be manually initiated by selecting Set.
SHED_RCAS Time duration at which to give up on computer writes to function block RCas locations. Shed from RCas
shall never happen when SHED_RCAS = 0.
SHED_ROUT Time duration at which to give up on computer writes to function block ROut locations. Shed from Rout
shall never happen when SHED_ROUT = 0.
SIMULATE Allows the transducer analog input or output to the block to be manually supplied when simulate is enabled.
When simulation is disabled, the simulate value and status track the actual value and status.
SIMULATE_D Allows the transducer discrete input or output to the block to be manually supplied when simulate is
enabled. When simulation is disabled, the simulate value and status track the actual value and status.
SP_HI_LIM The setpoint high limit is the highest setpoint operator entry that can be used for the block.
SP_LO_LIM The setpoint low limit is the lowest setpoint operator entry that can be used for the block.
SP_RATE_DN Ramp rate at which downward setpoint changes are acted on in Auto mode, in PV units per second. If the
ramp rate is set to zero, then the setpoint is used immediately. For control blocks, rate limiting applies only in Auto. For
output blocks, rate limiting applys in Auto, Cas, and RCas modes.
SP_RATE_UP Ramp rate at which upward setpoint changes are acted on in Auto mode, in PV units per second. If the
ramp rate is set to zero, then the setpoint is used immediately. For control blocks, rate limiting applies only in Auto. For
output blocks, rate limiting applies in Auto, Cas, and RCas modes.
ST_REV The revision level of the static data associated with the function block. To support tracking changes in static
parameter attributes, the associated block’s static revision parameter is incremented each time a static parameter attribute
value is changed. Also, the associated block’s static revision parameter may be incremented if a static parameter attribute is
written but the value is not changed.
STRATEGY The strategy field can be used to identify grouping of blocks.. This data is not checked or processed by the
block.
TRK_IN_D This discrete input is used to initiate external tracking of the block output to the value specified by TRK_VAL.
TRK_SCALE The high and low scale values, engineering units code, and number of digits to the right of the decimal
point, associated with TRK_VAL.
TRK_VAL This input is used as the track value when external tracking is enabled by TRK_IN_D.
WRITE_LOCK If set, no writes from anywhere are allowed, except to clear WRITE_LOCK. Block inputs continue to be
updated.
XD_SCALE The high and low scale values, engineering units code, and number of digits to the right of the decimal point
used with the value obtained from the transducer for a specified channel.
XD_STATE Index to the text describing the states of a discrete for the value obtained from the transducer.
2 TAG_DESC 27 EXPAND_DN
3 STRATEGY 28 IGNORE_TIME
4 ALERT_KEY 29 UPDATE_EVT
5 MODE_BLK 30 BLOCK_ALM
6 BLOCK_ERR 31 ALARM_SUM
7 PV 32 ACK_OPTION
8 OUT 33 ALARM_HYS
9 OUT_RANGE 34 HI_HI_PRI
10 GRANT_DENY 35 HI_HI_LIM
11 STATUS_OPTS 36 HI_HI_LIMX
12 PV_FTIME 37 HI_PRI
13 IN 38 HI_ LIM
15 HI_GAIN 40 LO_PRI
18 HI_BIAS 43 LO_LO_PRI
19 LO_BIAS 44 LO_LO_LIM
20 LO_LO_BIAS 45 LO_LO_LIMX
21 PRE_OUT_ALM 46 HI_HI_ALM
23 OUT_ALM_SUM 48 LO_ALM
24 ALM_RATE_UP 49 LO_LO_ALM
25 ALM_RATE_DN
2 TAG_DESC 20 UPDATE_EVT
3 STRATEGY 21 BLOCK_ALM
4 ALERT_KEY 22 ALARM_SUM
5 MODE_BLK 23 ACK_OPTION
6 BLOCK_ERR 24 ALARM_HYS
7 PV 25 HI_HI_PRI
8 OUT 26 HI_HI_LIM
9 SIMULATE 27 HI_PRI
10 XD_SCALE 27 HI_LIM
11 OUT_SCALE 29 LO_PRI
12 GRANT_DENY 30 LO_LIM
13 IO_OPTS 31 LO_LO_PRI
14 STATUS_OPTS 32 LO_LO_LIM
15 CHANNEL 33 HI_HI_ALM
16 L_TYPE 34 HI_ALM
17 LOW_CUT 35 LO_ALM
18 PV_FTIME 36 LO_LO_ALM
2 TAG_DESC 17 CAS_IN
3 STRATEGY 18 SP_RATE_DN
4 ALERT_KEY 19 SP_RATE_UP
5 MODE_BLK 20 SP_HI_LIM
6 BLOCK_ERR 21 SP_LO_LIM
7 PV 22 CHANNEL
8 SP 23 FSTATE_TIME
9 OUT 24 FSTATE_TIME
10 SIMULATE 25 BKCAL_OUT
11 PV_SCALE 26 RCAS_IN
12 XD_SCALE 27 SHED_OPT
13 GRANT_DENY 28 RCAS_OUT
14 IO_OPTS 29 UPDATE_EVT
15 STATUS_OPTS 30 BLOCK_ALM
2 TAG_DESC 20 RANGE_LO
3 STRATEG 21 BIAS_IN_1
4 ALERT_KEY 22 GAIN_IN_1
5 MODE_BLK 23 BIAS_IN_2
6 BLOCK_ERR 24 GAIN_IN_2
7 PV 25 BIAS_IN_3
8 OUT 26 GAIN_IN_3
9 PRE_OUT 27 COMP_HI_LIM
10 PV_SCALE 28 COMP_LO_LIM
11 OUT_RANGE 29 ARITH_TYPE
12 GRANT_DENY 30 BAL_TIME
13 INPUTS_OPTS 31 BIAS
14 IN 32 GAIN
15 IN_LO 33 OUT_HI_LIM
16 IN_1 34 OUT_LO_LIM
17 IN_2 35 UPDATE_EVT
18 IN_3 36 BLOCK_ALM
2 TAG_DESC 18 SP_LO_LIM
3 STRATEGY 19 GAIN
4 ALERT_KEY 20 BAL_TIME
5 MODE_BLK 21 BKCAL_IN
6 BLOCK_ERR 22 OUT_HI_LIM
7 SP 23 OUT_LO_LIM
8 OUT 24 BKCAL_OUT
9 OUT_SCALE 25 RCAS_IN
10 GRANT_DENY 26 SHED_OPT
11 CONTROL_OPTS 27 RCAS_OUT
12 STATUS_OPTS 28 TRK_SCALE
13 IN_1 29 TRK_IN_D
14 CAS_IN 30 TRK_VAL
15 SP_RATE_DN 31 UPDATE_EVT
16 SP_RATE_UP 32 BLOCK_ALM
2 TAG_DESC 11 OUT_D
3 STRATEGY 12 BKCAL_IN_D
4 ALERT_KEY 13 PV_D
5 MODE_BLK 14 IN_D
6 BLOCK_ERR 15 BLOCK_ALM
7 OUT 16 R_DS256
8 BKCAL_IN 17 R_DS257
9 PV
2 TAG_DESC 10 OUT_D
3 STRATEGY 11 PV_D
4 ALERT_KEY 12 IN_D
5 MODE_BLK 13 BLOCK_ALM
6 BLOCK_ERR 14 R_DS256
7 OUT 15 R_DS257
8 PV
2 TAG_DESC 21 BLOCK_ALM
3 STRATEGY 22 ALARM_SUM
4 ALERT_KEY 23 ACK_OPTION
5 MODE_BLK 24 ALARM_HYS
6 BLOCK_ERR 25 HI_HI_PRI
7 PV 26 HI_HI_LIM
8 OUT 27 HI_PRI
9 SIMULATE 28 HI_LIM
10 XD_SCALE 29 LO_PRI
11 OUT_SCALE 30 LO_LIM
12 GRANT_DENY 31 LO_LO_PRI
13 IO_OPTS 32 LO_LO_LIM
14 STATUS_OPTS 33 HI_HI_ALM
15 CHANNEL 34 HI_ALM
16 L_TYPE 35 LO_ALM
17 LOW_CUT 36 LO_LO_ALM
18 PV_FTIME 37 R_DS256
19 FIELD_VAL 38 R_DS257
2 TAG_DESC 18 SP_RATE_DN
3 STRATEGY 19 SP_RATE_UP
4 ALERT_KEY 20 SP_HI_LIM
5 MODE_BLK 21 SP_LO_LIM
6 BLOCK_ERR 22 CHANNEL
7 PV 23 FSTATE_TIME
8 SP 24 FSTATE_VAL
9 OUT 25 BKCAL_OUT
10 SIMULATE 26 RCAS_IN
11 PV_SCALE 27 SHED_OPT
12 XD_SCALE 28 RCAS_OUT
13 GRANT_DENY 29 UPDATE_EVT
14 IO_OPTS 30 BLOCK_ALM
15 STATUS_OPTS 31 R_DS256
16 READBACK 32 R_DS257
2 TAG_DESC 13 SEL_3
3 STRATEGY 14 SEL_TYPE
4 ALERT_KEY 15 BKCAL_IN
5 MODE_BLK 16 OUT_HI_LIM
6 BLOCK_ERR 17 OUT_LO_LIM
7 OUT 18 BKCAL_SEL_1
8 OUT_SCALE 19 BKCAL_SEL_2
9 GRANT_DENY 20 BKCAL_SEL_3
10 STATUS_OPTS 21 UPDATE_EVT
11 SEL_1 22 BLOCK_ALM
2 TAG_DESC 27 RESET_D
3 STRATEGY 28 ACCEPT_D
4 ALERT_KEY 29 DC_STATE
5 MODE_BLK 30 TRAVEL_TIMER
6 BLOCK_ERR 31 CFM_PASS_TIME
7 PV_D 32 CFM_ACT1_TIME
8 SP_D 33 TRIP_TIME
9 OUT_D 34 IGNORE
10 OUT_STATE 35 FAIL
11 GRANT_DENY 36 ALARM_SUM
12 DEVICE_OPTS 37 BKCAL_IN_D
13 STATUS_OPTS 38 TRK_IN_D
14 IN_D 39 CAS_IN_D
15 ACK_OPTION 40 BKCAL_OUT_D
16 FAIL_PRI 41 RCAS_IN_D
17 ACCEPT_PRI 42 RCAS_OUT_D
18 IGNORE_PRI 43 SHED_OPT
19 UPDATE_EVT 44 CRACK_TIMER
20 BLOCK_ALM 45 DELAY_TIMER
21 FAIL_ALM 46 CFM_ACT2_TIME
22 ACCEPT_ALM 47 CRACK_TIME
23 IGNORE_ALM 48 DELAY_TIME
24 SHUTDOWN_D 49 RESTART_TIME
25 INTERLOCK_D
2 TAG_DESC 14 STATUS_OPTS
3 STRATEGY 15 CHANNEL
4 ALERT_KEY 16 PV_FTIME
5 MODE_BLK 17 FIELD_VAL_D
6 BLOCK_ERR 18 UPDATE_EVT
7 PV_D 19 BLOCK_ALM
8 OUT_D 20 ALARM_SUM
9 SIMULATE_D 21 ACK_OPTION
10 XD_STATE 22 DISC_PRI
11 OUT_STATE 23 DISC_LIM
12 GRANT_DENY 24 DISC_ALM
2 TAG_DESC 14 STATUS_OPTS
3 STRATEGY 15 READBACK_D
4 ALERT_KEY 16 CAS_IN_D
5 MODE_BLK 17 CHANNEL
6 BLOCK_ERR 18 FSTATE_TIME
7 PV_D 19 FSTATE_VAL_D
8 SP_D 20 BKCAL_OUT_D
9 OUT_D 21 RCAS_IN_D
10 SIMULATE_D 22 SHED_OPT
11 PV_STATE 23 RCAS_OUT_D
12 XD_STATE 24 UPDATE_EVT
13 GRANT_DENY 25 BLOCK_ALM
2 TAG_DESC 11 IN
3 STRATEGY 12 FOLLOW
4 ALERT_KEY 13 DEAD_TIME
5 MODE_BLK 14 BAL_TIME
6 BLOCK_ERR 15 OUTAGE_LIM
7 OUT 16 UPDATE_EVT
8 OUT_Range 17 BLOCK_ALM
9 GRANT_DENY
2 TAG_DESC 14 IN_4
3 STRATEGY 15 DISABLE_1
4 ALERT_KEY 16 DISABLE_2
5 MODE_BLK 17 DISABLE_3
6 BLOCK_ERR 18 DISABLE_4
7 OUT 19 SELECT_TYPE
8 OUT_RANGE 20 MIN_GOOD
9 GRANT_DENY 21 SELECTED
10 STATUS_OPTS 22 OP_SELECT
11 IN_1 23 UPDATE_EVT
12 IN_2 24 BLOCK_ALM
2 TAG_DESC 22 REV_FLOW2
3 STRATEGY 23 RESET_IN
4 ALERT_KEY 24 STOTAL
5 MODE_BLK 25 RTOTAL
6 BLOCK_ERR 26 SRTOTAL
7 TOTAL_SP 27 SSP
8 OUT 28 INTEG_TYPE
9 OUT_RANGE 29 INTEG_OPTS
10 GRANT_DENY 30 CLOCK_PER
11 STATUS_OPTS 31 PRE_TRIP
12 IN_1 32 N_RESET
13 IN_2 33 PCT_INCL
14 IN 34 GOOD_LIM
15 OUT_TRIP 35 UNCERT_LIM
16 TIME_UNIT1 36 OP_CMD_INT
17 TIME_UNIT2 37 OUTAGE_LIM
18 UNIT_CONV 38 RESET_CONFIRM
19 PULSE_VAL1 39 UPDATE_EVT
20 PULSE_VAL2 40 BLOCK_ALM
2 TAG_DESC 11 IN
3 STRATEGY 12 FOLLOW
4 ALERT_KEY 13 LAG_TIME
5 MODE_BLK 14 LEAD_TIME
6 BLOCK_ERR 15 BAL_TIME
7 OUT 16 OUTAGE_LIM
8 OUT_RANGE 17 UPDATE_EVT
9 GRANT_DENY 18 BLOCK_ALM
2 TAG_DESC 11 OUT_4
3 STRATEGY 12 OUT_5
4 ALERT_KEY 13 OUT_6
5 MODE_BLK 14 OUT_7
6 BLOCK_ERR 15 OUT_8
7 CHANNEL 16 UPDATE_EVT
8 OUT_1 17 BLOCL_ALM
9 OUT_2
2 TAG_DESC 16 MO_OPTS
3 STRATEGY 17 FSTATE_TIME
4 ALERT_KEY 18 FSTATE_VAL1
5 MODE_BLK 19 FSTATE_VAL2
6 BLOCK_ERR 20 FSTATE_VAL3
7 CHANNEL 21 FSTATE_VAL4
8 IN_1 22 FSTATE_VAL5
9 IN_2 23 FSTATE_VAL6
10 IN_3 24 FSTATE_VAL7
11 IN_4 25 FSTATE_VAL8
12 IN_5 26 FSTATE_STATUS
13 IN_6 27 UPDATE_EVT
14 IN_7 28 BLOCK_ALM
2 TAG_DESC 11 OUT_D4
3 STRATEGY 12 OUT_D5
4 ALERT_KEY 13 OUT_D6
5 MODE_BLK 14 OUT_D7
6 BLOCK_ERR 15 OUT_D8
7 CHANNEL 16 UPDATE_EVT
8 OUT_D1 17 BLOCL_ALM
9 OUT_D2
2 TAG_DESC 16 MO_OPTS
3 STRATEGY 17 FSTATE_TIME
4 ALERT_KEY 18 FSTATE_VAL_D1
5 MODE_BLK 19 FSTATE_VAL_D2
6 BLOCK_ERR 20 FSTATE_VAL_D3
7 CHANNEL 21 FSTATE_VAL_D4
8 IN_D1 22 FSTATE_VAL_D5
9 IN_D2 23 FSTATE_VAL_D6
10 IN_D3 24 FSTATE_VAL_D7
11 IN_D4 25 FSTATE_VAL_D8
12 IN_D5 26 FSTATE_STATUS
13 IN_D6 27 UPDATE_EVT
14 IN_D7 28 BLOCK_ALM
2 TAG_DESC 23 TRK_IN_D
3 STRATEGY 24 TRK_VAL
4 ALERT_KEY 25 UPDATE_EVT
5 MODE_BLK 26 BLOCK_AM
6 BLOCK_ERR 27 ALARM_SUM
7 PV 28 ACK_OPTION
8 OUT 29 ALARM_HYS
9 PV_SCALE 30 HI_HI_PRI
10 OUT_SCALE 31 HI_HI_LIM
11 GRANT_DENY 32 HI_PRI
12 CONTROL_OPTS 33 HI_LIM
13 STATUS_OPTS 34 LO_PRI
14 IN 35 LO_LIM
15 PV_FTIME 36 LO_LO_PRI
16 BKCAL_IN 37 LO_LO_LIM
17 OUT_HI_LIM 38 HI_HI_ALM
18 OUT_LO_LIM 39 HI_ALM
19 ROUT_IN 40 LO_ALM
20 SHED_OPT 41 LO_LO_ALM
21 ROUT_OUT
2 TAG_DESC 14 CAS_IN
3 STRATEGY 15 BKCAL_OUT
4 ALERT_KEY 16 IN_ARRAY
5 MODE_BLK 17 OUT_ARRAY
6 BLOCK_ERR 18 LOCKVAL
7 SP 19 BKCAL_IN_1
8 OUT_1 20 BKCAL_IN_2
9 OUT_2 21 BAL_TIME
10 OUT_1_RANGE 22 HYSTVAL
11 OUT_2_RANGE 23 UPDATE_EVT
12 GRANT_DENY 24 BLOCK_ALM
2 TAG_DESC 35 RCAS_OUT
3 STRATEGY 36 ROUT_OUT
4 ALERT_KEY 37 TRK_SCALE
5 MODE_BLK 38 TRK_IN_D
6 BLOCK_ERR 39 TRK_VAL
7 PV 40 FF_VAL
8 SP 41 FF_SCALE
9 OUT 42 FF_GAIN
10 PV_SCALE 43 UPDATE_EVT
11 OUT_SCALE 44 BLOCK_ALM
12 GRANT_DENY 45 ALARM_SUM
13 CONTROL_OPTS 46 ACK_OPTION
14 STATUS_OPTS 47 ALARM_HYS
15 IN 48 HI_HI_PRI
16 PV_FTIME 49 HI_HI_LIM
17 BYPASS 50 HI_PRI
18 CAS_IN 51 HI_LIM
19 SP_RATE_DN 52 LO_PRI
20 SP_RATE_UP 53 LO_LIM
21 SP_HI_LIM 54 LO_LO_PRI
22 SP_LO_LIM 55 LO_LO_LIM
23 GAIN 56 DV_HI_PRI
24 BIAS 57 DV_HI_LIM
25 BAL_TIME 58 DV_LO_PRI
26 RATE 59 DV_LO_LIM
27 BKCAL_IN 60 HI_HI_ALM
28 OUT_HI_LIM 61 HI_ALM
29 OUT_LO_LIM 62 LO_ALM
30 BKCAL_HYS 63 LO_LO_ALM
31 BKCAL_OUT 64 DV_HI_ALM
32 RCAS_IN 65 DV_LO_ALM
33 ROUT_IN
2 TAG_DESC 35 RCAS_OUT
3 STRATEGY 36 ROUT_OUT
4 ALERT_KEY 37 TRK_SCALE
5 MODE_BLK 38 TRK_IN_D
6 BLOCK_ERR 39 TRK_VAL
7 PV 40 FF_VAL
8 SP 41 FF_SCALE
9 OUT 42 FF_GAIN
10 PV_SCALE 43 UPDATE_EVT
11 OUT_SCALE 44 BLOCK_ALM
12 GRANT_DENY 45 ALARM_SUM
13 CONTROL_OPTS 46 ACK_OPTION
14 STATUS_OPTS 47 ALARM_HYS
15 IN 48 HI_HI_PRI
16 PV_FTIME 49 HI_HI_LIM
17 BYPASS 50 HI_PRI
18 CAS_IN 51 HI_LIM
19 SP_RATE_DN 52 LO_PRI
20 SP_RATE_UP 53 LO_LIM
21 SP_HI_LIM 54 LO_LO_PRI
22 SP_LO_LIM 55 LO_LO_LIM
23 GAIN 56 DV_HI_PRI
24 RESET 57 DV_HI_LIM
25 BAL_TIME 58 DV_LO_PRI
26 RATE 59 DV_LO_LIM
27 BKCAL_IN 60 HI_HI_ALM
28 OUT_HI_LIM 61 HI_ALM
29 OUT_LO_LIM 62 LO_ALM
30 BKCAL_HYS 63 LO_LO_ALM
31 BKCAL_OUT 64 DV_HI_ALM
32 RCAS_IN 65 DV_LO_ALM
33 ROUT_IN
2 TAG_DESC 31 SHED_OPT
3 STRATEGY 32 RCAS_OUT
4 ALERT_KEY 33 TRK_SCALE
5 MODE_BLK 34 TRK_IN_D
6 BLOCK_ERR 35 TRK_VAL
7 PV 36 UPDATE_EVT
8 SP 37 BLOCK_ALM
9 OUT 38 ALARM_SUM
10 PV_SCALE 39 ACK_OPTION
11 OUT_SCALE 40 ALARM_HYS
12 GRANT_DENY 41 HI_HI_PRI
13 CONTROL_OPTS 42 HI_HI_LIM
14 STATUS_OPTS 43 HI_PRI
15 IN 44 HI_LIM
16 PV_FTIME 45 LO_PRI
17 IN_1 46 LO_LIM
18 RA_FTIME 47 LO_LO_PRI
19 CAS_IN 48 LO_LO_LIM
20 SP_RATE_DN 49 DV_HI_PRI
21 SP_RATE_UP 50 DV_HI_LIM
22 SP_HI_LIM 51 DV_LO_PRI
23 SP_LO_LIM 52 DV_LO_LIM
24 GAIN 53 HI_HI_ALM
25 BKCAL_IN 54 HI_ALM
26 OUT_HI_LIM 55 LO_ALM
27 OUT_LO_LIM 56 LO_LO_ALM
28 BKCAL_OUT 57 DV_HI_ALM
29 BAL_TIME 58 DV_LO_ALM
2 TAG_DESC 11 GRANT_DENY
3 STRATEGY 12 IN_1
4 ALERT_KEY 13 IN_2
5 MODE_BLK 14 SWAP_2
6 BLOCK_ERR 15 CURVE_X
7 OUT_1 16 CURVE_Y
8 OUT_2 17 UPDATE_EVT
9 X_RANGE 18 BLOCK_ALM
2 TAG_DESC 22 TIME_POSN_T
3 STRATEGY 23 OP_CMD_SPG
4 ALERT_KEY 24 SPG_STATE
5 MODE_BLK 25 PRE_OUT
6 BLOCK_ERR 26 RESET_IN
7 OUT 27 BAL_TIME
8 OUT_RANGE 28 OUTAGE_LIM
9 GRANT_DENY 29 UPDATE_EVT
10 STATUS_OPTS 30 BLOCK_ALM
11 START_VAL 31 ALARM_SUM
12 DURATION 32 ACK_OPTION
13 TIME_UNITS 33 ALARM_HYS
14 BKCAL_IN 34 DV_HI_PRI
15 START 35 DV_HI_LIM
16 START_TYPE 36 DV_LO_PRI
17 PAUSE 37 DV_LO_LIM
18 PAUSE_CAUSE 38 DV_HI_ALM
19 AUTO_CYCLE 39 DV_LO_ALM
20 STEP_POSN
2 TAG_DESC 17 IN_D3
3 STRATEGY 18 IN_D4
4 ALERT_KEY 19 COMB_TYPE
5 MODE_BLK 20 TIMER_TYPE
6 BLOCK_ERR 21 PRE_OUT_D
7 PV_D 22 N_START
8 OUT_D 23 OUT_EXP
9 TIMER_SP 24 OUT_REM
10 PV_STATE 25 RESET_IN
11 OUT_STATE 26 QUIES_OPT
12 GRANT_DENY 27 TIME_UNITS
13 INVERT_OPTS 28 UPDATE_EVT
14 STATUS_OPTS 29 BLOCK_ALM
15 IN_D1
Bus is an H1 fieldbus cable between a host and field devices connected to multiple segments, sometimes through the use of
repeaters.
Communications Stack is a layered software supporting communication between devices. It is the device communications
software which provides encoding and decoding of User Layer messages, deterministic control of message transmission, and
message transfer.
Control Loop is a group of function blocks (FBs) that perform at a specified rate within a fieldbus device or distributed
across the fieldbus network.
Data Link Layer (DLL) controls transmission of messages onto the fieldbus, and manages access to the fieldbus through the
Link Active Scheduler (LAS).
Deterministic is the ability to measure the maximum worst-case delay in delivery of a message between any two nodes in a
network. Any network protocol that depends on random delays to resolve mastership is nondeterministic.
Device Alerts are produced by fieldbus devices to provide status information to the ToolboxST application and Alarm
Viewer.
Device Description (DD) provides an extended description of each object in the virtual field device (VFD), and includes
information needed for a control system or host to understand the meaning of data in the VFD.
Discrete Input (DI) means the signal is from the field device to the host system.
Discrete Output (DO) means the signal is generated by the host system and transmitted to a field device.
Fieldbus is a digital, two-way, multi-drop communication link among intelligent measurement and control devices. It serves
as a local area network (LAN) for advanced process control, remote input/output and high-speed factory automation
applications.
Fieldbus Access Sublayer (FAS) maps the fieldbus message specification (FMS) onto the data link layer (DLL).
Flexible Function Block (FFB) is similar to a standard FB, except that an application specific algorithm created by a
programming tool determines the function of the block, the order and definition of the block parameters, and the time required
to perform the block. FFBs are typically used for control of discrete processes and for hybrid (batch) processes. A PLC can be
modeled as a flexible function block device.
Gateway is a computer that translates another fieldbus-related protocol to FOUNDATION Fieldbus Function Block Parameters
fieldbus protocol, for example, HART® or Modbus® to FOUNDATION Fieldbus Function Block Parameters fieldbus protocol.
H1 is a term used to describe a fieldbus network operating at 31.25 kbit/s. They have control functions in the form of
configurable blocks (scaling, filtering, PID, and so forth) that are integrated with the rest of the control logic in the Mark VIe
controller.
H1 Field Device is a fieldbus device connected directly to an H1 fieldbus. Typical H1 field devices are valves and
transmitters.
H1 Repeater is an active, bus-powered or non-bus-powered device used to extend the range over which signals can be
correctly transmitted and received for a given medium. A maximum of four repeaters and/or active couplers can be used
between any two devices on a H1 fieldbus network. Repeaters connect segments together to form larger networks.
FOUNDATION HSE is the FOUNDATION Fieldbus Function Block Parameters fieldbus backbone network running Ethernet and
IP.
HSE Field Device is a fieldbus device connected directly to a HSE fieldbus. Typical HSE field devices are HSE linking
devices, HSE field devices running function blocks (FBs), and host computers.
HSE Linking Device (PFFA) is a device used to interconnect H1 fieldbus networks and segments to HSE to create a larger
system. A system can have no more than 20 linking devices. Each linking device can have up to 4 links, with no more than 16
fieldbus devices per link.
• View which assigned fieldbus function blocks perform at what time during the macrocycle.
• View time allotted during the unscheduled portion of the macrocycle for the reading of views of assigned fieldbus
function blocks configured for placement on EGD.
• Refresh the macrocycle timeline view by invoking a method which recalculates the macrocycle timeline calculation
algorithm.
• Switch to view a different segment’s macrocycle timeline.
• Print the displayed macrocycle view.
Methods are optional (but highly desirable) additions to DDs. Methods are used to define and automate procedures (such as
calibration) for operation of field devices.
Network Management (NM) permits FOUNDATION network manager (NMgr) entities to conduct management operations
over the network by using network management agents (NMAs). Each NMA is responsible for managing the communications
within a device. The NMgr and NMA communicate through use of the fieldbus messaging specification (FMS) and VCR.
Object Dictionary (OD) contains all FB, resource block (RB) and transducer block (TB) parameters used in a device.
Through these parameters, the blocks can be accessed over the fieldbus network.
Physical Layer receives messages from the communications stack and converts the messages into physical signals on the
fieldbus transmission medium, and vice-versa.
Resource Block (RB) schedules define when FBs perform and when data and status is published on the bus.
Segment is a section of an H1 fieldbus that is terminated in its characteristic impedance. Segments can be linked by
repeaters to form a longer H1 fieldbus. Each segment can include up to 32 H1 devices.