Instantiable Block Implementation Considerations - Honeywell Series A User Manual

Fieldbus interface module
Hide thumbs Also See for Series A:
Table of Contents

Advertisement

The Type function in Control Builder supports the functions associated with instantiable
blocks in fieldbus devices with single capability levels. It lets you build block types for
devices that support block instantiation that include both the fixed function blocks and
the instantiable function blocks. This means you can view the instantiable blocks as part
of the device's block hierarchy in the Library tab of Control Builder. The icon for an
instantiable function block has a slash across it and a letter "I_" tag prefix as illustrated
below, so you can easily distinguish it from a fixed function block.
ATTENTION
A manufacturer may choose to define Transducer blocks as instantiable
instead of fixed. In this case, be sure you instantiate a Transducer block for
each physical sensor that is to be used in the device. A Transducer block
usually corresponds to a physical sensor in the vendor's device.

Instantiable block implementation considerations

The following table summarizes considerations that are unique to implementing control
strategies that include fieldbus devices with optional instantiated blocks. Please use these
considerations to supplement the appropriate procedures in the remainder of this
document that are tailored to fieldbus devices with only fixed function blocks including
resource and transducer blocks.
If you want
to . . .
R400
Experion PKS Series A Fieldbus Interface Module User's Guide
July 2010
3. Fieldbus Integration With Experion System
Then,
Honeywell
3.8. Block Instantiation Support
Notes and References
87

Advertisement

Table of Contents
loading

This manual is also suitable for:

Experion pks series a

Table of Contents