EasyManua.ls Logo

Honeywell Series A User Manual

Honeywell Series A
560 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
Page #1 background imageLoading...
Page #1 background image
Honeywell Process Solutions
Experion PKS
Series A Fieldbus Interface
Module
User's Guide
EP-DCX166
R400
July 2010
Release R400
Honeywell

Table of Contents

Question and Answer IconNeed help?

Do you have a question about the Honeywell Series A and is the answer not in the manual?

Honeywell Series A Specifications

General IconGeneral
BrandHoneywell
ModelSeries A
CategoryRecording Equipment
LanguageEnglish

Summary

Symbol Definitions

CAUTION

Indicates a situation which, if not avoided, may result in equipment damage or injury.

WARNING

Indicates a potentially hazardous situation which, if not avoided, could result in serious injury or death.

3. Fieldbus Integration With Experion System

3.1 Overview

Summarizes key areas of enhancement for Fieldbus integration into the Experion system.

Non-Redundant Fieldbus integrated architecture for CIOM-A FIM

Illustrates the typical non-redundant Fieldbus architecture using CIOM-A FIM.

Redundant Fieldbus integrated architecture for CIOM-A FIM

Illustrates a redundant Fieldbus architecture using CIOM-A FIMs and Redundancy Modules.

Fieldbus Interface Module (FIM) - the key to integration

Explains the FIM's role as a bridge for Fieldbus integration and communication.

Redundancy Module - the key to redundant operation

Describes the Redundancy Module's function in coordinating synchronization for redundant systems.

Control Builder serves as common configuration tool

Explains how Control Builder facilitates integral creation and configuration of Fieldbus and Experion blocks.

Parameter Definition Editor serves as key interoperability tool

Details how the Parameter Definition Editor (PDE) edits function block parameters and its role in interoperability.

Parameter Definition Editor supports Fieldbus Methods

Explains how the PDE retrieves method code from DD files and includes a dedicated Methods tab.

3.2 Control Integration

Explains data integration handled by FIM, link objects, network management, and system management.

Type creation makes integration possible

Explains how Control Builder's Type function enables integrating fieldbus function blocks with Experion blocks.

Fieldbus device Analog Input integration

Describes wiring an Analog Input (AI) function block output to a control module input in Control Builder.

Fieldbus Analog Input data manipulation

Explains how Control Builder handles analog input from fieldbus blocks, mapping data structures and status.

Fieldbus device Analog Output or PID integration

Describes wiring a control module output to an Analog Output (AO) or PID function block in a fieldbus device.

Fieldbus Analog Output or PID data manipulation

Explains how Control Builder handles analog output and back calculation, mapping parameters and status.

Fieldbus device Discrete Input integration

Describes wiring a Discrete Input (DI) function block output to a Device Control (DEVCTL) function block.

Fieldbus Discrete Input data manipulation

Explains how Control Builder handles discrete input from fieldbus blocks, mapping data structures and Boolean values.

Fieldbus device Discrete Output data integration

Describes wiring a Device Control (DEVCTL) function block output to a Discrete Output block in a fieldbus device.

Fieldbus Discrete Output data manipulation

Explains how Control Builder handles discrete output and back calculation, mapping parameters and status.

3.3 Control Mode Interaction

Explains block modes (Actual, Target, Permitted, Normal) and their effects on operation.

Fieldbus block modes versus control modes

Explains the MODE_BLK parameter and its relationship to Actual, Target, Permitted, and Normal modes.

3.4 Link and Block Schedules

Explains Link Active Scheduler (LAS) and Link Master roles and Link/Block schedules.

Link Active Scheduler (LAS) and Link Master

Explains the LAS's role as a bus arbiter and the Link Master's function.

Link Schedule

Describes the Link Schedule as the overall schedule for link data transfer and function block execution.

Function block execution schedule

Details the schedule derived from link data transfer, including preprocessing, execution, and postprocessing phases.

3.5 Tags, Addresses, and Live List

Covers tag and address assignments, including physical device tags and data link addresses.

Tag and address assignments

Explains the assignment of names (PD_TAG) and data link addresses to fieldbus devices.

3.6 Notification Scheme

Covers fieldbus alarms, Experion alarm priorities, and advanced alarming features.

Fieldbus versus Experion Alarm Priorities

Explains how fieldbus alarms are integrated with the Experion notification system and their priority mapping.

Advanced Alarming

Introduces the feature of configuring alarm conditions on diagnostic parameters for FF devices.

Fieldbus Alarm Conditions

Discusses process and device-related alarms and how they are reported into the Experion system.

3.7 CIOM-A FIM Redundancy Functionality

Details CIOM-A FIM redundancy, switchover behaviors, and failure conditions.

About CIOM-A FIM redundancy

Explains implementing redundant Series A FIM operation via a Redundant Chassis Pair (RCP).

Switchover and Secondary readiness

Describes the switchover process and the readiness states of the secondary chassis.

Switchover behavior considerations

Lists display and control data behaviors during a CIOM-A FIM switchover action.

Failure conditions and switchover

Identifies failure conditions that result in a switchover and those that do not.

Fieldbus network switchover considerations

Lists key considerations for initiating an H1 network switchover for redundant FIM operation.

Switchover versus fieldbus network activities

Summarizes how fieldbus network activities behave during a switchover.

3.8 Block Instantiation Support

Explains block instantiation, Control Builder support, and implementation considerations.

4. Installation

4.1 Planning Considerations

Provides general planning details and installation considerations for Experion systems.

Installation declaration

States that equipment installation must comply with electrical codes and be mounted within an enclosure.

Fieldbus wiring selection and calculation

Discusses preferred cable types and the importance of calculating topology, wiring, and power impact.

4.2 Installing CIOM-A Fieldbus Interface Module TC-FFIF01

Provides front view details and explains intrinsically safe applications for RTP models.

Inserting module in chassis

Step-by-step procedure for inserting the CIOM-A FIM into an unpowered chassis.

Connecting RTP cable to module

Procedure for connecting the RTP cable to the CIOM-A FIM in an unpowered chassis.

Loading FIM firmware

Instructions on loading FIM firmware to make it operational, referring to Appendix G.

4.3 Installing Fieldbus RTP TC-FFRU01/TC-FFRP02 or RRTP TC-FFSU01/TC-FFSP02

Shows front view of RTP models and their usage in hazardous locations or for powering devices.

Mounting on a DIN rail

Procedure for mounting the RTP on a user-supplied DIN rail, recommending enclosure use.

Wiring

Provides wiring schematics and warnings for RTP models TC-FFSU01 and TC-FFSP02.

5. Configuration

5.2 Non-Experion Interface Precautions

Warns about using non-Experion interfaces, potential access rights issues, and data integrity risks.

5.4 Configuring Fieldbus Components In a Control Strategy

Guides on configuring process Control Strategy using predefined function blocks integrated with Experion.

About control strategy configuration

Explains using Control Builder to configure strategies with fieldbus-related Function Blocks.

Configuration considerations only for redundant CIOM-A FIM applications

Lists considerations specific to configuring fieldbus devices with redundant CIOM-A FIM applications.

Adding CIOM-A FIM block to Project

Procedure to add a CIOM-A FIM block to the Project tab in Control Builder, including Link blocks.

Checking link configuration

Procedure to check the link configuration of links associated with a CIOM-A FIM block in Control Builder.

Creating a Fieldbus device type from vendor DD

Guides on creating a fieldbus device block type using Control Builder and vendor-supplied DD files.

Editing device block parameters

Procedure to edit selected block parameters using the Parameter Definition Editor (PDE).

Adding a fieldbus device to Project

Describes adding a fieldbus device from the Library tab to the Project tab using drag-and-drop or file menu.

Assigning a device to a Link in Project

Procedure to assign a device to a Link associated with the applicable FIM in the Project tab.

Checking device configuration

Procedure to check the configuration of a selected fieldbus device in the Project tab after assignment to a Link.

Making fieldbus block template and assigning function block to device

Outlines steps for creating a user template, adding blocks to a CM, and assigning blocks to a fieldbus device.

5.5 Loading Components Online

Explains the load operation process for transferring Control Strategy to field components, including fieldbus.

About load operations

Explains the load operation process for transferring Control Strategy to field components, including fieldbus components.

Fieldbus device matching rules

Outlines matching rules used by CIOM-A FIM when loading devices, based on Device ID and state.

Loading a CIOM-A FIM and its Links

Typical steps to load a CIOM-A FIM and its associated RTP and links via Project tab in Control Builder.

Matching uncommissioned device to project device or vice versa

Procedure to match uncommissioned fieldbus devices with their counterpart devices in the Project tab.

Loading Link contents or fieldbus device

Procedure to load Link contents or fieldbus devices, assuming CIOM-A FIM and devices are installed and powered.

5.6 Configuring Advanced Alarming

Explains how advanced alarming monitors diagnostic parameters and generates system alarms based on user-defined conditions.

Overview

Explains how advanced alarming monitors diagnostic parameters and generates system alarms based on user-defined conditions.

Configuring/creating a condition

Steps to configure a condition, including typing a name and selecting parameters.

Enabling or disabling a condition

Describes disabling active alarm conditions to clear alarms and enabling conditions to generate alarms.

5.7 Block Offnet Diagnostic Alarm

Configures high-priority alarm when a device containing a block is disconnected from the network using OFFNETALM_ENABLED.

Block Offnet Diagnostic Alarm

Configures a high-priority alarm when a device containing a block is disconnected from the network using OFFNETALM_ENABLED.

Behavior of the Block Offnet and Device Offnet System alarms in various communication loss scenarios

Table detailing alarm behavior during communication loss between C300/FIM and FF device/FIM.

Behavior of the Block Offnet and Device Offnet System alarms in various operational scenarios

Explains alarm behavior during operational scenarios like inactivating/activating links or CMs.

5.8 Configuring non-cache parameters

Steps to configure non-cache parameters, warning about performance degradation and special circumstances.

Configuring non-cache parameters

Steps to configure non-cache parameters, warning about performance degradation and special circumstances.

6. Operation

6.1 Monitoring Fieldbus Functions Through Station Displays

Describes using pre-configured Detail displays in Experion Server Station for monitoring FIM, Link, device, and function blocks.

6.3 Monitoring Fieldbus Functions Through Monitoring Tab

Details how to monitor fieldbus functions using the Monitoring tab in Control Builder.

Inactivating/Activating a Link

Procedure to inactivate/activate a fieldbus Link via the Monitoring tab in Control Builder.

Monitoring/Interacting with given component/block

Describes interacting with components and function blocks in fieldbus devices using the Monitoring tab.

Checking/changing fieldbus device functional class

Procedure to check and change the functional class of a fieldbus device, noting wizard guidance for R210+ software.

Checking live list and interacting with uncommissioned devices

Procedure to check the link for uncommissioned devices added to the Live List and interact with them.

Viewing and optimizing Link schedule configuration

Summarizes how to call up and optimize Link schedule configuration for viewing in Control Builder.

Considerations

Key considerations for optimizing Link schedule, focusing on ORDERINCM parameter for sequencing.

To configure link schedule optimization

Steps to configure FFLink for automatic schedule optimization using Link Schedule Optimization parameters.

CheckingCIOM-A FIM redundancy status and initiating manual switchover

Monitors redundant CIOM-A FIM status and initiates manual switchover via the Redundancy Module configuration form.

7. Fieldbus Device Commissioning

Getting Started

Provides initial setup and commissioning guidance for a fieldbus device, highlighting parameter considerations.

Initial checks and operations

Lists initial checks and operations required before commissioning a device, including wire connections and FIM block loading.

7.2 Connecting Devices

Outlines the process for connecting fieldbus devices to the network and checking if they appear on the link.

7.3 Checking Device

Details steps to check firmware, DD revision, and device presence on the link.

7.4 Checking Control Strategy

Guides on checking if the control strategy is configured, measurements within specifications, and adding devices.

8. Maintenance, Checkout, and Calibration

8.1 Adding, Removing and Replacing Components

Covers procedures for adding, removing, and replacing components, including RIUP and general replacement precautions.

General procedure

Emphasizes extreme caution when replacing components and potential need for configuration changes.

Guidelines for adding fieldbus device to "live"/operating Link

Guidelines to avoid loss of control and view when adding a Link Master capable device to a live link.

Using optional safe handling of new devices

Explains automatic actions initiated by the safe handling option when adding a new device to a loaded Fieldbus link.

Replacing a failed device with a like device having the same model name and device revision

Procedure to replace a failed device with an identical model and revision, noting wizard guidance in Station.

Replacing a failed device with a different device using a different block type

Procedure to replace a failed device with a different device type, assuming system is offline or safe mode.

8.2 Unlike Device Replacement Report

Explains how to generate an Unlike Device Replacement (UDR) Report to view information about replaced devices and affected control modules.

Unlike Device Replacement Report

Explains how to generate an Unlike Device Replacement (UDR) Report to view information about the device to be replaced and the control modules that are affected.

8.3 Replacing Device Template with a Different One

Procedure to replace one or more instances of a fieldbus device type with a different device type using the Unlike Template Replacement wizard.

8.4 Correcting Some Common UTR errors

Identifies common UTR errors during operation and suggests corrective actions.

8.5 Upgrading Firmware in Uncommissioned Device

Procedure to upgrade firmware in an uncommissioned device using Control Builder and vendor-supplied files.

8.6 Changing or Clearing Tag and/or Address of Uncommissioned Device

General procedure to change or clear the tag name and/or address of an uncommissioned device for re-initialization.

Changing or Clearing Tag and/or Address of Uncommissioned Device

General procedure to change or clear the tag name and/or address of an uncommissioned device for re-initialization.

8.7 Using Fieldbus Device Simulate Function

Shows general steps for using the simulate function with an Analog Input block for testing purposes.

Using Fieldbus Device Simulate Function

Shows general steps for using the simulate function with an Analog Input block for testing purposes.

8.8 Preparing Fieldbus Device for a Move or Software Migration

Procedure to prepare a device before migrating the system to a new software release or moving it to another Link.

8.10 FIM Self-Test Diagnostic Codes

Lists self-test diagnostic codes the FIM steps through upon power up for troubleshooting.

FIM Self-Test Diagnostic Codes

Lists self-test diagnostic codes the FIM steps through upon power up for troubleshooting.

9. Experion PKS Host Registration

10. Appendix A

Analog Input block

Functional schematic and description of the Analog Input (AI) block, including its inputs, outputs, and parameters.

Analog Output block

Functional schematic and description of the Analog Output (AO) block, converting set point to hardware-usable numbers.

Discrete Input block

Describes the Discrete Input (DI) block that takes discrete input data from a transducer channel and provides it as output.

Discrete Output block

Explains the Discrete Output (DO) block that converts SP_D to useful output for linked hardware via CHANNEL selection.

Proportional/Integral/Derivative block

Explains the PID block for classic three-mode control, acting on error to correct deviation and supporting cascade applications.

Ratio block

Describes the Ratio block that uses input IN_1 and SP to calculate target output, with IN as actual ratio displayed as PV.

11. Appendix B

11.1 Standard Function Block Parameters

Lists and defines standard function block parameters, starting with ACK_OPTION.

OFFNETALM_ENABLED

Represents enabling/disabling the Block Offnet Diagnostic Alarm; disabled by default.

SP

Defines the set point of any analog block.

SP_D

Defines the set point of any discrete block.

13. Appendix D

14. Appendix E

15. Appendix F

16. Appendix G

16.1 Loading CIOM-A FIM firmware

Instructions to load CIOM-A FIM firmware if not pre-configured or for replacement FIMs.

Loading Boot code

Procedure to load Boot code assumes NTools is launched and CIOM-A FIM firmware needs updating.

Loading Personality image

Procedure to load Personality image, assuming previous step or CIOM-A FIM startup in ALIV mode.

17. Appendix H

18. Appendix I

Parameters for Link Configuration in Project Mode

Summarizes user-configurable parameters for the LINK Block in Project Mode for identifying and tuning Link communications.

Device Diagnostics

Details parameters for enabling/disabling alarm conditions and configuring non-cache parameters.

Maintenance tab

Parameter for enabling/disabling the Block Offnet Diagnostic Alarm.

Related product manuals