Hide thumbs Also See for 800xA:
Table of Contents

Advertisement

800xA for MOD 300
Operation
System Version 6.0
Power and productivity
for a better world
TM

Advertisement

Table of Contents
loading

Summary of Contents for ABB 800xA

  • Page 1 800xA for MOD 300 Operation System Version 6.0 Power and productivity for a better world...
  • Page 3 800xA for MOD 300 Operation System Version 6.0...
  • Page 4 This document contains information about one or more ABB products and may include a description of or a reference to one or more standards that may be generally relevant to the ABB products. The presence of any such description of a standard or reference to a standard is not a representation that all of the ABB products referenced in this document support all of the features of the described or ref- erenced standard.
  • Page 5: Table Of Contents

    Table of Contents About This User Manual User Manual Conventions ....................15 Warning, Caution, Information, and Tip Icons..............16 Terminology........................17 Released User Manuals and Release Notes..............18 Section 1 - Introduction Document Overview ......................19 Product Overview ......................21 Section 2 - Getting Started General ..........................23 Operating Overview......................25 Accessing Displays......................25 Printing Displays ......................30...
  • Page 6 Table of Contents Tool Tips ......................45 Loop FCM Display ......................45 Operating Procedures for CCF Displays................. 46 Viewing Trend Data ..................... 47 Taking Control of a Loop..................49 Changing Control Parameters ................49 Tuning/Engineering Procedures for CCF Displays............51 Tuning Via the Loop Detail Display ..............
  • Page 7 Table of Contents Unit Overview Display ....................78 Unit Detail Display......................80 Unit Detail Display Format ..................80 Loading the Sequence from the Unit Detail Display ...........81 Loading a Recipe from the Unit Detail Display...........82 Changing Sequence State, Mode, and Status ............82 Sequence Detail Display....................84 Sequence Detail Display Format................85 Choosing a Sequence for Sequence Detail............85 Changing Sequence State, Mode, and Status ............85...
  • Page 8 Table of Contents Register Faceplate ......................109 Counter Display ......................110 Counter Faceplate......................111 Timer Display........................ 112 Timer Faceplate ......................114 I/O Point Display......................115 I/O Point Faceplate......................115 File Display ........................117 Sequencer Display......................118 TLL Device Logged Changes ..................119 TLL Messages .......................
  • Page 9 Table of Contents PROFIBUS Displays .....................167 PROFIBUS LAN Display ..................168 PROFIBUS Device Display ................171 Module/Channel Display ...................176 Startup ......................178 TRIO Displays.......................179 Accessing the Remote I/O Displays for a SC Controller ........179 Accessing the Remote I/O Displays for an AC Controller ........179 TRIO LAN Display....................180 TRIO Block Display ..................185 Direct I/O Displays......................189...
  • Page 10 Table of Contents Loop Definition Templet ....................213 Device Loop Templet ....................221 PID Controller FCM ..................... 231 Adaptive Gain........................ 245 Adaptive Reset ......................249 Auto/Manual Controller FCM..................250 Input FCMs ........................251 Common Fields....................251 Analog Input FCM..................... 251 Digital Input FCM .....................
  • Page 11 Table of Contents Normalize FCM ....................260 Inverse Normalize FCM ..................261 Scale Input FCM ....................261 Flow Calculation FCM..................262 Temperature Compensation FCM ..............263 Ratio/Bias FCM ....................263 Time Related Calculator FCMs ..................264 Time Derivative FCM..................264 Time Integration FCM..................265 First Order Filter FCM ..................265 Totalizer FCM ....................265 Lead/Lag Filter FCM ..................266 Dead Time FCM....................266...
  • Page 12 Table of Contents Data Entry FCM....................278 String FCM ......................278 User Math Block FCM ..................278 MOD30_MOD300_MAP .................. 279 Extended Processing FCM .................... 280 Common Fields....................280 Continuous Moving Average FCM..............281 Standard Deviation FCM ................... 282 Non-Rate Periodic Total FCM ................282 Periodic Average FCM..................
  • Page 13 Table of Contents SP_ALGO5_FCM....................318 BRKPTS ........................319 Revision History Updates in Revision Index A..................321 Index 3BUR002418-600 A...
  • Page 14 Table of Contents 3BUR002418-600 A...
  • Page 15: About This User Manual

    Any security measures described in this user manual, for example, for user access, password security, network security, firewalls, virus protection, etc., represent possible steps that a user of an 800xA System may want to consider based on a risk assessment for a particular application and installation. This risk...
  • Page 16: Warning, Caution, Information, And Tip Icons

    Warning, Caution, Information, and Tip Icons About This User Manual Warning, Caution, Information, and Tip Icons This user manual includes Warning, Caution, and Information where appropriate to point out safety related or other important information. It also includes Tip to point out useful hints to the reader.
  • Page 17: Terminology

    About This User Manual Terminology Terminology A complete and comprehensive list of terms is included in System 800xA System Guide Functional Description (3BSE038018*). The listing includes terms and definitions that apply to the 800xA System where the usage is different from commonly accepted industry standard definitions and definitions given in standard dictionaries such as Webster’s Dictionary of Computer Terms.
  • Page 18: Released User Manuals And Release Notes

    Released User Manuals and Release Notes About This User Manual Released User Manuals and Release Notes A complete list of all User Manuals and Release Notes applicable to System 800xA is provided in System 800xA Released User Manuals and Release Notes (3BUA000263*).
  • Page 19: Section 1 Introduction

    Section 1 Introduction Document Overview This user manual describes how to use 800xA for MOD 300 software for MOD 300 system operation. The 800xA System provides a common operation and configuration view for MOD 300 and other field devices and software options. This user manual has the following objectives: •...
  • Page 20 Document Overview Section 1 Introduction Operation Refer to the following operation chapters for instructions and reference information related to runtime operation. Specifically, these chapters provide a detailed description of each display related to runtime operation: • Section 3, CCF Displays. •...
  • Page 21: Product Overview

    Product Overview Product Overview 800xA for MOD 300 is an integration product to the 800xA System for the MOD 300 control network (DCN). The Connectivity Server, with an external RTA Unit connects to the DCN and gathers data for display as different MOD Aspect Objects on Client Workstations.
  • Page 22 Product Overview Section 1 Introduction – MOD 300 Environment Area Status. – MOD 300 Environment Group Graphic. – MOD 300 Environment Group Status. – MOD 300 Environment Group Trend. • – MOD 300 TCL Unit Overview. – MOD 300 TCL Unit Detail. –...
  • Page 23: Section 2 Getting Started

    Your status changes to the User Rights as defined in the User Manager and you are now logged into the computer. From the ABB Start Menu, select ABB Industrial IT 800xA > System > and then select Workplace. The desktop will be shown and the Workplace Login is launched. Start the Plant Explorer or Operator Workplace to access the MOD 300 displays.
  • Page 24 The permitted actions in the open windows are controlled by the permissions of the logged over user. The log over only affects the 800xA System permission. Windows security is still the same as the user logged in.
  • Page 25: Operating Overview

    When operator interaction is required, the operator interface is supported by the displays described in the following chapters. These displays are based upon aspects of the object type templets described in 800xA for MOD 300 Configuration (3BUR002417*). Refer to the System 800xA Operation (3BSE036904*) user manual for basic topics regarding runtime operation.
  • Page 26 Accessing Displays Section 2 Getting Started Accessing Displays Using Graphic Displays Graphic displays may be associated with an object with context navigation to trends, faceplates, and overview type displays. Overview graphics can provide a panoramic view of the process and can provide one-step access to critical displays. They can be made the software equivalent of the Page Selector Alarm Panel with the capability to monitor alarms for different areas and groups from one display or have target blocks that can initiate a TCL program sequence state or status transition.
  • Page 27 Section 2 Getting Started Accessing Displays MOD 300 Objects and Associated Aspects Table 1 shows the relationships between MOD 300 objects and aspects. Table 1. MOD 300 Objects and Associated Aspects MOD 300 Objects Associated Aspects MOD_DB MOD 300 System Status, Alarm and Event Lists (CCF Alarm, Diagnostic Message, TCL Message) MOD_AREA...
  • Page 28 Accessing Displays Section 2 Getting Started Table 1. MOD 300 Objects and Associated Aspects (Continued) MOD 300 Objects Associated Aspects MOD_CCF_DEV_LOOP MOD300 Alarm Summary, MOD300 Loop Detail, MOD300 Loop FCM, Faceplate, Alarm List, Command_DVAlue MOD_UNIT MOD300 TCL, MOD300 Recipe Detail, MOD300 Sequence Debug, MOD300 Sequence Detail, MOD300 SFC, MOD300 Unit Detail MOD_SEQUENCE...
  • Page 29 Section 2 Getting Started Accessing Displays Table 1. MOD 300 Objects and Associated Aspects (Continued) MOD 300 Objects Associated Aspects MOD_BUM MOD300 Message, MOD 300 System Status MOD_CONSOLE, MOD300 Multibus, MOD_ADVANT_D2D, MOD300 Message, MOD_DCN_DCN, MOD300 System Performance, MOD_GENERICD MOD 300 System Status MOD_ENV_AREA MOD300 Area Status, MOD300 Area Graphic, MOD300 Area Alarm...
  • Page 30: Printing Displays

    Printing Displays Section 2 Getting Started Printing Displays To print the active window of a display, use the Print Screen key to capture the screen, paste the image into an application such as Microsoft Word and then send it to the printer. For best resolution, maximize detail displays to full screen before printing.
  • Page 31: Section 3 Ccf Displays

    Section 3 CCF Displays Operational Displays for Configurable Control Functions The format and functionality of each runtime display that supports the Configurable Control Functions (CCF) is described here along with procedures for basic operations that are executed from the displays. In addition, tuning and engineering procedures are described.
  • Page 32: Loop Detail Displays

    Generally, users with Operator authority have read-only access to the Loop Detail Display. Control/tuning functions are restricted to System Engineers. The authority assignment for functions associated with this display can be changed as described in the Objects and Access Rights section of System 800xA Configuration (3BDS011222*). Control and PID Loops...
  • Page 33 Section 3 CCF Displays Control and PID Loops – Enabled/disabled condition, limit value where applicable, and priority for each alarm parameter (input, setpoint, deviation and output). Figure 2. Loop Detail Display for a PID Loop If you click on any field in the process values box, a Faceplate, Figure 3, is displayed.
  • Page 34 Control and PID Loops Section 3 CCF Displays Figure 3. MOD CCF PID Loop Reduced Faceplate Figure 4. MOD CCF PID Loop Standard Faceplate 3BUR002418-600 A...
  • Page 35 Section 3 CCF Displays Control and PID Loops Fields that do not apply to the type of loop being displayed are left blank and the labels for these fields are dimmed. For Auto/Manual Controller loops, Figure 5, the following fields are blank: setpoint; setpoint and deviation alarms; deviation deadband;...
  • Page 36: Device Loops

    Device Loops Section 3 CCF Displays Device Loops Figure 6 is an example of the information that is included on a Loop Detail Display for device loops. Device loops detect the device state. There is no trend or alarm limit/priority information on Loop Detail Displays for device loops. Select the command, mode, and state process values box to access the device loop faceplate.
  • Page 37 Section 3 CCF Displays Device Loops The device loop standard faceplate, Figure 7, is used to modify command, mode, and state. Only device descriptor state values of 0 to 15 are allowed. If the Enable Access Restriction configuration is set to Yes, then device commands are not allowed while in auto (shaded buttons).
  • Page 38: Continuous Loops

    Continuous Loops Section 3 CCF Displays The device loop reduced faceplate, Figure 8, is also used to modify command, mode, and state. Figure 8. MOD CCF Device Loop Reduced Faceplate Device loops that are Special Device types do not show all possible commands. The faceplate for a Special Device type only shows four of 16 possible outputs.
  • Page 39: Loop Faceplates

    A tag descriptor can be up to 24 characters and normally explains the purpose of the tag. The descriptor defined during configuration and then imported into the 800xA system, after it is imported it is no longer updated.
  • Page 40: Process Bar Graphs And Values

    Process Bar Graphs and Values Section 3 CCF Displays Alarm Acknowledge Status Area Auto/ Computer Loc/Rem Loc/Rem Loc/Rem Abnormal Manual / Local Track Bias Ratio State Mode or Ramp Output Track Setpoint Figure 10. Faceplate Name Area Features Process Bar Graphs and Values The area shown in Figure 11 contains graphical and numerical representations of the...
  • Page 41 Section 3 CCF Displays Process Bar Graphs and Values Figure 11. Faceplate Process Bar Graph and Values Features (CCF) 3BUR002418-600 A...
  • Page 42: Operator Controls

    Operator Controls Section 3 CCF Displays Operator Controls The Operator area, Figure 12, provides controls that manipulate the tag being displayed. Some of the actions available in the operator area include: change auto or manual mode, change computer mode, and change set point mode (a shaded button does not allow change).
  • Page 43 Section 3 CCF Displays Operator Controls Table 3. Buttons and Indicators Icon Name Description Auto Switch to Auto from Manual. In auto, the setpoint and ratio can be adjusted. If shaded, switching to Auto is not allowed. Manual Switch to Manual from Auto. In manual, the output can be adjusted.
  • Page 44 Operator Controls Section 3 CCF Displays Table 3. Buttons and Indicators (Continued) Icon Name Description Local Bias Switch to Local Bias operation. Bias value can be changed locally while in this mode. Remote Bias Switch to Remote Bias operation. Local Ratio Switch to Local Ratio operation.
  • Page 45: Tool Tips

    Section 3 CCF Displays Tool Tips Table 3. Buttons and Indicators (Continued) Icon Name Description Ramp Setpoint is being ramped by a TCL source. Abnormal State An abnormal condition for a CCF loop is checked when the ABNORMAL STATE Field on page 219 is set to yes.
  • Page 46: Operating Procedures For Ccf Displays

    Operating Procedures for CCF Displays Section 3 CCF Displays accessible using the LOOP TMPL and FCM TMPL buttons or by double clicking on the FCM. Figure 13. Loop FCM Display Operating Procedures for CCF Displays This section provides information on the following topics: •...
  • Page 47: Viewing Trend Data

    The source of the values that appear on Loop Detail Display trends are gathered from real-time CCF trend data. Other trend view objects, as described in System 800xA Operations (3BSE036904*), can show real-time and historical trend data for several tags at once.
  • Page 48 Viewing Trend Data Section 3 CCF Displays select the Top of Range field and enter a new number. To change the bottom number on the Y-axis, select the Bottom of Range field and enter a new number. Click on the Auto Expand field to dynamically change the range limits to a new limit value as new values cross the limits.
  • Page 49: Taking Control Of A Loop

    Section 3 CCF Displays Taking Control of a Loop Taking Control of a Loop You can take control of a loop from the loop’s faceplate or from the Loop FCM display by changing a control parameter. Control parameter changes for a loop tag that are made from these displays allow you to monitor the results of both manual and auto control operations.
  • Page 50 Changing Control Parameters Section 3 CCF Displays Figure 14. Changing Setpoint on MOD CCF PID Loop Faceplate Select the entry field, and then enter the new value via the keyboard. As an alternative, you can use the control slider to change the setpoint or output value up or down.
  • Page 51: Tuning/Engineering Procedures For Ccf Displays

    Section 3 CCF Displays Tuning/Engineering Procedures for CCF Displays Select the FCM on a Loop FCM display. Again, you may have to adjust some preliminary parameters as a prerequisite for changing the parameter that you actually want to change. Select the entry field, and then enter the new value via the keyboard. Press Enter to accept the new value.
  • Page 52 Tuning Via the Loop Detail Display Section 3 CCF Displays Changes made to any of the parameters on the Loop Detail Display are not made to the database until you press Enter. Value is reset if focus is lost. Entered value goes red after it is written to the controller. Once the new value come back from the controller it changes back to black.
  • Page 53: Engineer Tuning Displays For A Continuous Loop

    Section 3 CCF Displays Engineer Tuning Displays for a Continuous Loop Changing a Device Parameter Device parameters include: Simulation Mode, Override Mode, Lock State, and Field State. Field State is a read only field and cannot be changed. The other device parameters can be switched between ON and OFF in the Device Values area.
  • Page 54 Engineer Tuning Displays for a Continuous Loop Section 3 CCF Displays The value of the output is displayed on the line that extends from the right side of the FCM block. You can change the values of the status parameters by selecting the block and entering a new value in the fields provided along the bottom of the Loop FCM Display.
  • Page 55 Section 3 CCF Displays Engineer Tuning Displays for a Continuous Loop To support Loop FCM Display functions, the following buttons are provided: LOOP TMPL This button accesses the runtime version of the Loop Definition Templet. Figure 15 shows a typical MOD Loop Definition Templet.
  • Page 56 Engineer Tuning Displays for a Continuous Loop Section 3 CCF Displays Figure 15. Loop Templet Display Runtime Versions of Loop Definition and FCM Templets The runtime versions of the templets are used to make the actual tuning changes. The templets are accessed via the Loop FCM Display as described above. Their format is similar to the configurator templets in AdvaBuild with the following exceptions: •...
  • Page 57: Engineer Tuning Displays For A Device Loop

    Section 3 CCF Displays Engineer Tuning Displays for a Device Loop Tuning changes are made to database attributes by first changing the information on the templet and then saving the templet information to the database by selecting the SAVE button. If the save process is not successful, a message describing the problem is displayed.
  • Page 58: Alarms

    Alarms Section 3 CCF Displays Select the Loop FCM Display. Select the device block. Select LOOP TMPL. There is no FCM Templet for device loops. Use the fields at the bottom of the Loop FCM Display to make State, Mode and Command changes. Alarms Alarms based on the process measurement are defined as part of the loop.
  • Page 59: Alarm Detection

    Section 3 CCF Displays Alarm Detection Alarm Detection PID loops detect alarms on the measured variable, setpoint, deviations, and output. Control loops (Auto/Manual for example) detect alarms on the measured variable and output. Continuous loops (indicator and calculator for example) detect alarms on the measured variable.
  • Page 60: Alarm Priority

    Alarm conditions may also be indicated audibly by a .WAV file. Various combinations of audible and visual alarm indication can be obtained by configuration. Refer to the System 800xA Operations (3BSE036904*) for a description of the event bar and event display included with the base product.
  • Page 61: Alarm Acknowledgement

    Section 3 CCF Displays Alarm Acknowledgement mean that two separate alarms are configured on a single variable with either two high or two low trip points. The high, low, and rate of change alarms are extensions of output limiting. For example, the OUTPUT HIGH LIMIT specifies the maximum output value.
  • Page 62: Mod Group Displays

    MOD Group Displays Section 3 CCF Displays MOD Group Displays A group is a collection of related loops. Generally, a group has up to 12 control loops or up to 36 indicator loops or a combination of both. Control loops assigned to indicator targets provide limited information and cannot be used for control.
  • Page 63 Section 3 CCF Displays Group Status Display Figure 18. Group Status Display PID and A/M Status Blocks The PID status block shows tag, descriptor, setpoint (SP) value and mode, measured variable value, engineering units, output value and mode, computer mode, a current output value bar graph, a current measured value bar graph with setpoint and limits, engineering low limit, engineering high limit, FF/FB, and a trend graph.
  • Page 64 Group Status Display Section 3 CCF Displays The trend graph represents one division of trended data (60 sampled points) from the engineering low limit to the engineering high limit. The most current trend sample is on the right side of the graph. Trend data is only displayed if the trend rate is enabled (not 0) for the tag.
  • Page 65 Section 3 CCF Displays Group Status Display MOD Group Object. Only device descriptor command and state values of 0 to 15 are shown. Use the loop fcm if your configuration uses greater values. Indicator Status Blocks Indicator loop status blocks show tag and descriptor as well as measured variable, engineering units and alarm indications for PID, continuous or A/M loops or command state for device loops.
  • Page 66: Group Trend Display

    Group Trend Display Section 3 CCF Displays Group Trend Display The Group Trend Display, Figure 21, provides trend records for up to 12 loops. Group trends are displayed on three full-width graphs. Each graph shows trends for up to four loops, and is accompanied by the corresponding status blocks. The most current trend sample is on the right side of the grid.
  • Page 67 Section 3 CCF Displays Group Trend Display Group Trend Status Blocks To make changes to a loop on the Group Trend Display, select the desired field in the loop’s status block, Figure 22. Control functions within the block depend on how the loop is configured and user authority.
  • Page 68: Group Graphic Display

    Group Graphic Display Section 3 CCF Displays Group Graphic Display The Group Graphic Display, Figure 24, presents a custom graphic for a group and status blocks for each tag in the group. The status blocks occupy the right one-third of the screen, and the graphic occupies the left two-thirds of the screen. Status blocks operate as described in Group Trend Status Blocks on page 67.
  • Page 69: Group Alarm Display

    Section 3 CCF Displays Group Alarm Display Group Alarm Display The Group Alarm Display is a selected event group page with an additional filter applied based upon the tags assigned to the MOD environment group. The primary event group page is a filtered set of event attributes such as state (acknowledged and active) and type (operator action and process related).
  • Page 70 Area Status Display Section 3 CCF Displays Figure 25. Area Status Display One to three indicators are displayed on one status line, Figure 26, depending on the configuration. Each indicator line segment is context sensitive to its own tag. Measured Measured Device Variable...
  • Page 71: Area Alarm Display

    Section 3 CCF Displays Area Alarm Display For a PID control loop, information is displayed on one status line, Figure 27. The measured value bar graph also indicates the setpoint value with an orange triangle on the bottom of the graph, and it indicates the input high and low limits with red triangles on the top of the graph.
  • Page 72: Area Graphic Display

    Area Graphic Display Section 3 CCF Displays The filters defined in the event group narrow the scope of events seen by the page. The page can provide further filtering of the events but cannot expand beyond the filter of the event group. When the Area Alarm display is first called up, the primary filter is applied and then the filtered list of tags assigned to the area is applied.
  • Page 73 Section 3 CCF Displays Area Graphic Display There is an Area Graphic aspect for each area. The graphic configured for that aspect gets displayed in the Area Graphic display. 3BUR002418-600 A...
  • Page 74 Area Graphic Display Section 3 CCF Displays 3BUR002418-600 A...
  • Page 75: Section 4 Tcl Displays

    Section 4 TCL Displays Operational Displays for TCL This section describes the standard operational displays for sequential control using the Taylor Control Language (TCL). Sequential control operational displays support monitoring and control functions for TCL. Functions you can perform using the sequential operational displays include: •...
  • Page 76: Displays For Sequence And Recipe Development

    Displays for Sequence and Recipe Development Section 4 TCL Displays Displays for Sequence and Recipe Development TCL sequences and recipes are developed using the TCL Editor and TCL Recipe Editor respectively. These editors are available with AdvaBuild. TCL Version Mismatch Warning If the source code of a TCL sequence is re-compiled or modified after that sequence has been loaded, a warning message, Figure...
  • Page 77: Tcl / Unit Message Display

    Section 4 TCL Displays TCL / Unit Message Display TCL / Unit Message Display The TCL / Unit Message Display, Figure 31, lists certain need-to-know process condition messages sent from executing TCL programs. Messages which require a response cause the originating sequence to pause until an appropriate response is entered.
  • Page 78: Unit Overview Display

    Unit Overview Display Section 4 TCL Displays Figure 31. TCL Message Display Unit Overview Display The Unit Overview Display, Figure 32, lists all the units configured for the system, as well as the batches and recipes associated with each unit when viewed from the default MOD300 TCL Unit Overview aspect at the database control structure level.
  • Page 79 Section 4 TCL Displays Unit Overview Display Click on the Unit ID field to access the Unit Detail display for the selected unit. Figure 32. Unit Overview Display 3BUR002418-600 A...
  • Page 80: Unit Detail Display

    Unit Detail Display Section 4 TCL Displays Unit Detail Display The Unit Detail Display, Figure 33, lists the sequences that reside on and can be run on a unit. This display is used to: • Load a sequence onto the unit. •...
  • Page 81: Loading The Sequence From The Unit Detail Display

    Section 4 TCL Displays Loading the Sequence from the Unit Detail Display The information shown in the main portion of the display for each sequence in the unit includes: Sequence ID Sequence program name. Sequence Type Schedule, Procedure, or Operation. Sequence State Active, Inactive, Paused, Loading.
  • Page 82: Loading A Recipe From The Unit Detail Display

    Loading a Recipe from the Unit Detail Display Section 4 TCL Displays Loading a Recipe from the Unit Detail Display Note the ID of the recipe you want to download (refer to your Advabuild documentation). Access the Unit Detail Display of the unit where the recipe is to be downloaded.
  • Page 83 Section 4 TCL Displays Changing Sequence State, Mode, and Status Functions for sequence mode are: AUTO Programs execute steps in order without requiring operator intervention. SEMI_AUTO Programs execute steps automatically, but pause at configured breakpoints. The operator can then resume or abort.
  • Page 84: Sequence Detail Display

    Sequence Detail Display Section 4 TCL Displays Sequence Detail Display The Sequence Detail Display, Figure 34, supports runtime monitoring and manipulation of an individual sequence. Most of the runtime changes made to a sequence are done from this display. The changes you can make include: •...
  • Page 85: Sequence Detail Display Format

    Section 4 TCL Displays Sequence Detail Display Format Sequence Detail Display Format The unit ID, recipe ID, batch ID, and sequence are shown at the top of the Sequence Detail Display. Step data fields show the current step, next step, step time (the time spent executing the current step), and pause step (or the step on which the program pauses in semiauto mode).
  • Page 86: Sfc (Sequential Function Chart) Display

    SFC (Sequential Function Chart) Display Section 4 TCL Displays causes the step indicated to be executed after the current step. The next step can skip or repeat other steps as necessary. Pause Step determines at which step the sequence stops and waits for an operator response. SFC (Sequential Function Chart) Display The SFC (Sequential Function Chart) Display, Figure...
  • Page 87: Sfc Display Format

    Section 4 TCL Displays SFC Display Format When changing a value on the SFC Display, there is an indication of the change that was made, but then the value turns black with the previous value shown instead of the newly written value. However, the write does occur and the first scan shows the old value and then the next scan shows the written value.
  • Page 88: Sfc Display Operation

    SFC Display Operation Section 4 TCL Displays Figure 37. SFC Display with Expanded Step Transitions are shown beneath the activities and conditions window for a step. There are two types of transition windows. If a transition contains a GOTO which addresses the next step in the TCL sequence, it is displayed with the step number and step text beneath the tic mark on the main program flow line.
  • Page 89 Section 4 TCL Displays SFC Display Operation point the program has progressed to). There are three highlight states: Base, Last- Executed, and Executed. Table 5 lists the highlight states and their colors. Table 5. SFC Highlight States Presentation ACTIVITY CONDITION TRANSITION White on gray or blue Base Base...
  • Page 90 SFC Display Operation Section 4 TCL Displays Selecting a transition provides direct control access to the database reference(s) associated with the transition. You can change the value of the referenced database point to satisfy the transition expression. To gain control access, right click on a transition button, then select either the Loop FCM Display or the control dialog for the loop associated with the transition.
  • Page 91: Sequence Debug Display

    Section 4 TCL Displays Sequence Debug Display Sequence Debug Display The Sequence Debug Display, Figure 38, supports runtime troubleshooting and debugging of sequences. The troubleshooting and debug functions on this display are trace and breakpoint. Control functions supported by the sequence debug display are: sequence state, mode, and status changes.
  • Page 92: Choosing A Sequence For Debug Display

    Choosing a Sequence for Debug Display Section 4 TCL Displays the display. Below this are toggle buttons that show the status of the Breakpoint Trace debug functions. You can move the contents of the display to a requested point in the program through the Find Goto buttons.
  • Page 93 Section 4 TCL Displays Sequence Debug Program Functions point in the program. The current statement is highlighted while the program is executing. Select Follow current St# to follow the current statement. Find To go to a specific text string in the program, select the Find button.
  • Page 94 Sequence Debug Program Functions Section 4 TCL Displays To modify a variable, select the variable in the Trace Variables list and Enter the new value in the text entry field. To delete a variable, select the variable in the Trace Variables list and then click on the Delete button.
  • Page 95 Section 4 TCL Displays Sequence Debug Program Functions Figure 39. Trace Steps and Variable Window Breakpoint Breakpoints support testing of program logic via manual program execution. When breakpoints are enabled, the sequence is executed until the sequence reaches a line at which a breakpoint has been set.
  • Page 96 Sequence Debug Program Functions Section 4 TCL Displays To enable breakpoints, select the Breakpoint Enabled box. A breakpoint can be set at five different lines, causing the sequence to execute until it reaches a line at which a breakpoint has been set. To set a breakpoint at a certain line, either select the Breakpoint Window box (this displays the Breakpoint Window, Figure...
  • Page 97: Recipe Detail

    Section 4 TCL Displays Recipe Detail Recipe Detail The Recipe Detail Display, Figure 41, shows the recipe items and accompanying data values for the recipe residing on the unit. Runtime changes to recipe parameters are made via this display. Figure 41. Recipe Detail Display Recipe Detail Display Format The unit ID, unit description, recipe ID, and batch ID are shown at the top of the display.
  • Page 98: Changing Recipe Values

    Changing Recipe Values Section 4 TCL Displays Changing Recipe Values Only recipe values can be changed from the Recipe Detail Display. To edit a recipe value, select the parameter you want to change, type a new value and press Enter. Any changes to recipe values from the Recipe Detail Display are not permanent.
  • Page 99 Section 4 TCL Displays Using TCL Array Plot Figure 42. TCL Array Plot Context Menu Use the context menu to perform the following activities: • Trace 1 and Trace 2 > Configure This menu is active when using the In Plot Array option during configuration. The fields can be set as follows: 3BUR002418-600 A...
  • Page 100 Using TCL Array Plot Section 4 TCL Displays Number of Points This field is used to specify the number of points to be plotted. Number of Points + X-Start Position = X-Axis Width Specifying more points than available will cause a diagnostic error message and will not display any points.
  • Page 101: Batch Connectivity To M0D 300

    Batch Connectivity to M0D 300 When using the MOD-300 Control Systems as part of the System 800xA Batch Management, the primary operation displays are accessed from the Batch Overview, Batch History Overview, and Equipment Overview icons. The standard TCL displays are available for use as secondary displays for the normal control of the Batch Process.
  • Page 102 Batch Connectivity to M0D 300 Section 4 TCL Displays 3BUR002418-600 A...
  • Page 103: Section 5 Tll Displays

    Section 5 TLL Displays Operational Displays for Taylor Ladder Logic This section describes the runtime support displays for Taylor Ladder Logic (TLL). These displays are used to monitor TLL segments and data structures. Each data structure has its own type of display (Counter, Register, Timer, IOPoint, File and Sequencer).
  • Page 104 Segment Display Section 5 TLL Displays Figure 43. Segment Display The power rails are displayed in red because they are always powered. The rungs and branches are displayed in red if they have power, or in white if they do not. The elements are labeled with the name that was entered for them when the segment was built.
  • Page 105: Segment Display Fields And Buttons

    Section 5 TLL Displays Segment Display Fields and Buttons Figure 44. TLL Segment Display File to File Symbol Segment Display Fields and Buttons Device The Device field indicates the TLL name in a specific node or controller. This name is defined on the Ladder Logic Device object during database configuration.
  • Page 106: Faceplates For Program Elements

    Faceplates for Program Elements Section 5 TLL Displays Search: Use this field to specify an element you wish to find within the Segment display starting with the currently open segment or the first segment if none are open. To find an element, select the search field and enter the name of the element you want to find.
  • Page 107 Section 5 TLL Displays Faceplates for Program Elements To change AC, you must first put the I/O point into a forced state by clicking on the Forced YES button. Then you can change the status between ON and OFF or OPEN and CLOSED.
  • Page 108: Register Display

    Register Display Section 5 TLL Displays Register Display The Register Display, Figure 46, contains a list of the registers, places in memory that are used to store values, in the device. This display is accessed by selecting a Ladder Logic object and then selecting MOD300 TLL Register from the context menu.
  • Page 109: Register Faceplate

    Section 5 TLL Displays Register Faceplate Search is case sensitive and will find any partial string in the Register column. A match is colored green. The search arrows will find the previous or next match. Register Faceplate Each register can have a faceplate. Select the register (left click) to get the faceplate or use the context menu to get the faceplate of an imported register as shown in Figure 47.
  • Page 110: Counter Display

    Counter Display Section 5 TLL Displays Counter Display The Counter Display, Figure 48, contains a list of the counters in the device. This display is accessed by selecting a Ladder Logic object (MOD_LL_DEV) and then selecting MOD300 TLL Counter from the context menu. TLL counters can count by increments of one.
  • Page 111: Counter Faceplate

    Section 5 TLL Displays Counter Faceplate The following fields can be edited on this display: Value You can change the value of a counter by selecting the Value field for the counter, entering the new value, then pressing ENTER. This change is logged. Preset You can change the preset of a counter (the value counted up to or down from) by selecting the Preset field for the...
  • Page 112: Timer Display

    Timer Display Section 5 TLL Displays Timer Display The Timer Display, Figure 50, contains a list of the timers in the device. This display is accessed by selecting a Ladder Logic object and then selecting MOD300 TLL Timer from the context menu. TLL timers can time with a configurable time base that can be either 1.0, 0.1, or 0.01 seconds (displayed on faceplate).
  • Page 113 Section 5 TLL Displays Timer Display The following fields can be edited on this display: Preset The Preset and Value fields are displayed to the hundredth place. For example, 001:20:15.25 is one hour, twenty Value minutes, fifteen and twenty-five hundredths seconds. Your entry should be within the resolution of the time base.
  • Page 114: Timer Faceplate

    Timer Faceplate Section 5 TLL Displays • A period indicates seconds. Examples: 6 seconds .5 seconds Timer Faceplate Each timer can have a faceplate, Figure 51. Select the timer (left click) to get the faceplate or use the context menu to get the faceplate of an imported timer. The timer can be enabled (YES) or disabled (NO) from the faceplate.
  • Page 115: I/O Point Display

    Section 5 TLL Displays I/O Point Display I/O Point Display The I/O Point Display, Figure 52, contains a list of the I/O points of the node or controller. This display is accessed by selecting a Ladder Logic object and then selecting MOD300 TLL I/O Point from the context menu.
  • Page 116 I/O Point Faceplate Section 5 TLL Displays S800 I/O points, the faceplate shows the Channel number. The following fields can be edited on this display: Status The Status field gives the current value of the AC parameter of the point. It can be either Open or Closed for a contact, or On or Off for a coil.
  • Page 117: File Display

    Section 5 TLL Displays File Display File Display Each file in the device has a File Display which lists up to 128 values for use by the sequencer, Figure 54. This display is accessed by selecting a Ladder Logic Device object and then selecting MOD300 TLL File from the context menu and then selecting a specific file from the File List.
  • Page 118: Sequencer Display

    Sequencer Display Section 5 TLL Displays LL_FILE template allows a base 10 integer, from 0 to 4,294,967,295 (32 bits); however, it will be displayed as a signed 32 bit number (-1). Sequencer Display The Sequencer Display, Figure 55, has multiple pages, with one page for each step in the sequencer.
  • Page 119: Tll Device Logged Changes

    Section 5 TLL Displays TLL Device Logged Changes Use the Step field to display the screen for a particular step of the sequencer. Use the up/down arrow of the Step field to display the screen for the previous/next step of the sequencer. Enter a step value to go to a particular step. You can switch to a display for another sequencer in the device by selecting one from the Sequencer field.
  • Page 120 TLL Messages Section 5 TLL Displays 3BUR002418-600 A...
  • Page 121: Section 6 Status Displays

    You are alerted to the presence of a diagnostic message by the Diagnostic Message List of the base product as described in System 800xA Operations (3BSE036904*). Entries identifying an operator action on the diagnostic displays are relayed to the appropriate logging device.
  • Page 122: System Status Display

    System Status Display Section 6 Status Displays System Status Display The System Status Display, Figure 56, shows the current status of all subsystems (nodes) recognized on the DCN. Each subsystem status icon lists the subsystem name, device address, device type, media state, device state, and controller status (Controller types only).
  • Page 123 Section 6 Status Displays System Status Display Subsystem Types The available subsystem types (shown above icon on icon views and in the heading line of the corresponding Subsystem or I/O Status Display) include: ADVANT STATION Advant Station COMPACT STATION Advant Controller 410 (AC410) Subsystem PROCESS STATION Advant Controller 460 (AC460) Subsystem CONSOLE...
  • Page 124: Subsystem Status Displays

    Subsystem Status Displays Section 6 Status Displays the status of Control Modules 1 through 12. ADVANT STATION icons contain two status boxes that indicate the status of the Real Time Accelerator Board. AC410 and AC460 icons contain two status boxes that indicate the status of the DCN interface submodules, and AC460 icons have up to three additional status boxes that indicate the status of controllers.
  • Page 125: Ac460 Subsystem Status Display

    Section 6 Status Displays AC460 Subsystem Status Display AC460 Subsystem Status Display The AC460 Subsystem Status Display, Figure 57, provides: node address and name; controller address, name and status (active and backup); status of power supplies; TC520 Monitor Status; fan and auxiliary input status; status for PM510 Processor Module Cards and whether a card is currently a primary or backup;...
  • Page 126 AC460 Subsystem Status Display Section 6 Status Displays PROFIBUS Interface The status of the PROFIBUS Interface will show if it is active, failed or missing. In addition, you can select the PROFIBUS LAN display by selecting its display target. TRIO Interface The status of the TRIO LAN submodule will show if it is active, failed or missing.
  • Page 127 Section 6 Status Displays AC460 Subsystem Status Display S100 Interface S100 is redundant at the device level. A device’s redundant mate may reside on the same, or on a different S100 LAN. When redundant, both LANs are active, therefore, no S100 LAN interface is considered to be a “backup” for another. The status of the S100 LAN submodule will show if it is active, failed or missing.
  • Page 128 AC460 Subsystem Status Display Section 6 Status Displays The descriptions for the three command push-buttons follows: • RESET for UPGRADE The RESET for UPGRADE push-button is used to reset a backup controller and reboot into the “UPGRDE” state. The following restrictions apply for this command: –...
  • Page 129 Section 6 Status Displays AC460 Subsystem Status Display • HARD RESET The HARD RESET push-button can be used to reset any controller on the AC 460 subsystem display. Resetting a controller through this push-button has the same effect as depressing the “Enter” button on the controller’s front panel. This button must not be used during the on-line upgrade procedure.
  • Page 130: Ac410 Subsystem Status Display

    AC410 Subsystem Status Display Section 6 Status Displays AC410 Subsystem Status Display The AC410 Subsystem Status Display, Figure 59, provides: node address and name; DCN status; PM150 Controller address, name and status; and TRIO and S100 submodule status and logical LAN numbers. See the AC460 for a description of the TRIO Interface, S100 I/O Interface, S800 I/O Interface, MVI interface and DCN interface.
  • Page 131: Controller Node Subsystem Status Display

    Section 6 Status Displays Controller Node Subsystem Status Display Controller Node Subsystem Status Display The Controller Subsystem Status Display, Figure 60, provides information on the specified node's general condition. The first line of the display below the Subsystem Status title provides the device number, type and current state of the Controller Subsystem.
  • Page 132 Controller Node Subsystem Status Display Section 6 Status Displays immediately after the request to confirm is the request executed. You can select Cancel at any time to abort a request that has not yet been confirmed. A Control Card redundancy request is initiated by selecting the status block for the desired Control Module.
  • Page 133 Section 6 Status Displays Controller Node Subsystem Status Display Controller Subsystem Status Display Description The main areas on the Controller Subsystem Display are: CONTROLLERS Status and redundancy information for up to 12 Control Modules are shown in individual status blocks whose arrangement corresponds to the slots in the Controller Card File(s) of the subsystem.
  • Page 134 Controller Node Subsystem Status Display Section 6 Status Displays – ?????????? - No status received (Red). – UNKNOWN (Red). – FAILED (Red). – EMULATING - Back-up controller only (Yellow). – NOT AVAIL (Yellow). – LOST (Yellow). – TERMINATED - Controller only (Yellow). –...
  • Page 135 Section 6 Status Displays Controller Node Subsystem Status Display – BACK-UP MEMORY Status information for up to three Backup Memory Modules per Controller Subsystem are shown in individual status blocks to the right of the status blocks for the controllers they back up. Each field in a status block is a target. When selected, it is highlighted and that Backup Memory Module becomes the object of subsequent redundancy and display requests.
  • Page 136 Controller Node Subsystem Status Display Section 6 Status Displays only meaningful displays for use with D/F Modules are the Diagnostic Message Displays. The D/F status, shown in the D/F fields, is either DOWN (Red) or ACTIVE (Green). DIAGNOSTICS The status of power up diagnostics for each module accessible on the DCN is reported in this field.
  • Page 137: Turbo/Console Node Subsystem Status Display

    Section 6 Status Displays Turbo/Console Node Subsystem Status Display With the exception of diagnostic detection of an output channel failure, all of the above failures to a Control Module automatically initiate the fail over process. A failed output channel is configured to perform one of the following four actions based upon a detected diagnostic failure: –...
  • Page 138 Turbo/Console Node Subsystem Status Display Section 6 Status Displays Figure 61. Turbo Node Subsystem Status Display (Data Processor) The current status data, reported by the System Integrity Module (SIM) for the specified subsystem, is shown in this field. Buttons are also available for controlling the Annunciator, the Contact output, and erasing the SIM.
  • Page 139 Section 6 Status Displays Turbo/Console Node Subsystem Status Display Refer to your Subsystem Status and Diagnostics user manual for descriptions of the codes and their meanings. DIAGNOSTICS The status of power up diagnostics for each module in the subsystem is reported in this field.
  • Page 140: Diagnostic Message Display

    Diagnostic Message Display Section 6 Status Displays Diagnostic Message Display If the system is configured with multiple connectivity pairs user will receive duplicate diagnostic messages. The original diagnostic message and duplicate messages if any can be acknowledged. The Diagnostic Messages Display, Figure 63, shows all messages reported and filed as a diagnostic failure by a device/subdevice of the MOD control system (both...
  • Page 141 Section 6 Status Displays Diagnostic Message Display Device Identification The first line of the Diagnostic Message Display provides the device/subdevice number, type, and state of the device. Archive Messages The total number of records stored in the disk archive file is shown as a percentage of the total size of the archive in the MESSAGE mode, or as an exact number of messages in the ARCHIVE mode.
  • Page 142 Diagnostic Message Display Section 6 Status Displays E (Error) Red - An error occurred which prevents an individual package from running. W (Warning) Yellow - An abnormal event occurred which does not prevent anything from running. S (Success) Green - A procedure completed successfully. Diagnostic Messages Display Targets Additional fields/targets available on this display and their use are: OPERATOR By default, OPERATOR messages are displayed (those which cause...
  • Page 143 Section 6 Status Displays Diagnostic Message Display EMPHASIS SOURCE The emphasis source determines whether the set of messages for the current device/subdevice (SUBDEVICE), subsystem (SUBSYSTEM), or archive file (ARCHIVE) are displayed or highlighted. To change the emphasis source, use the pull-down menu to select either the SUBDEVICE, SUBSYSTEM, and ARCHIVE source.
  • Page 144 Diagnostic Message Display Section 6 Status Displays Printing Diagnostic Messages The print view icon along the tool bar prints a screen dump of the diagnostic message display. To print selected messages, use the Print Diagnostic Messages context menu selection on the Diagnostic Message Display. Use the standard print setup function to select a printer.
  • Page 145: System Performance Display

    Section 6 Status Displays System Performance Display System Performance Display The System Performance Display, Figure 65, is called up from the Subsystem Status Display. It provides information on the performance of a specified device/subdevice (node) in terms of CPU loading, Configurable Control Functions (CCF) software loading, and memory pool usage.
  • Page 146 System Performance Display Section 6 Status Displays The bar graphs are color coded. Red indicates a high level of resource utilization (90 to 100%), yellow a moderately high level of utilization (75 to 90%), and green a moderate level of utilization (0 to 75%). White is used to indicate neutral facts. Excessive CCF load (red region) may be caused by problem areas such as: •...
  • Page 147: Section 7 I/O Displays

    Section 7 I/O Displays I/O Displays Overview I/O displays contain information that allow you to identify detectable fault conditions, monitor general status and performance, change process outputs directly for testing, and control the status of redundancy. The I/O displays include: •...
  • Page 148: S800 I/O Displays

    S800 I/O Displays Section 7 I/O Displays S800 I/O Displays These S800 runtime displays relate to the Series 800 process interface as described in the S800 I/O User’s Guides where you can find additional information about S800 I/O. S800 LAN Display The S800 LAN display, Figure 66, shows the CI520/CI522 submodule status and...
  • Page 149 Section 7 I/O Displays S800 LAN Display This field represents the number of the Local Area Network (LAN) for all the stations shown. For the AC 460 this is LAN # 1 - 4 and for the AC 410 this is LAN # 1 or 2. Go back to the controller display to select a different LAN.
  • Page 150 S800 LAN Display Section 7 I/O Displays AF100 INTERFACE - X Menu Each AF100 Interface status area contains an AF 100 INTERFACE - X menu button. When the AF100 INTERFACE - x button is selected, a menu is displayed with the items shown in Figure 67 and as explained below.
  • Page 151 Section 7 I/O Displays S800 LAN Display Station Item Description Station This is the number of the S800 I/O Number Station as specified during database configuration (1 - 80). It is also a screen target to the Station display. Station Type The station type is shown under the station number.
  • Page 152: S800 Station Display

    S800 Station Display Section 7 I/O Displays S800 Station Display The S800 Station display is started by selecting a configured I/O station from the S800 LAN Display. The S800 Station display, Figure 69, shows information about the FCI Module, each S800 I/O Module and the I/O Clusters that are configured for the I/O Station.
  • Page 153 Section 7 I/O Displays S800 Station Display The top of the S800 Station display identifies the I/O Station, its Advant Controller and has other information as described below. Devsub The controller DCN address where the S800 I/O is located. State This field shows the status of the controller as ACTIVE, DOWN or AVAIL.
  • Page 154 S800 Station Display Section 7 I/O Displays FCI - X Status Area FCI Status areas represent a CI810A FCI or the redundant CI820 FCIs. For the CI810A, the status box contains the current state of FCI - 1. For the redundant CI820 FCIs, the left status box contains the current state of FCI - 1 (or the left FCI), the right status box contains the current state of FCI - 2 (or the right FCI).
  • Page 155 Section 7 I/O Displays S800 Station Display S800 Device and FCI Detail In the main part of the display, Figure 69, a detail window shows specific information about the FCI, I/O Clusters and each I/O module device. The right scroll bar is used to view other devices of the station. For the FCI and each I/O module, information is displayed as described below (see Figure 69 for device...
  • Page 156: S800 Device Display

    S800 Device Display Section 7 I/O Displays S800 Device Display The S800 Device display is started by selecting a configured I/O device from the S800 Station Display. The S800 Device display, Figure 70, shows information for the device and each channel configured for the S800 I/O module (device diagnostics are not displayed).
  • Page 157 Section 7 I/O Displays S800 Device Display At the top of the display there is a section related to the addressing of the I/O module. Module Address Info Description Devsub This field is the controller DCN address where the S800 I/O is located.
  • Page 158 S800 Device Display Section 7 I/O Displays The next section gives information about the I/O module selected. Templet The device name created during database configuration is given in this field. Label This field shows the label given this I/O module. Revision Gives the revision level of the module if available.
  • Page 159: S800 Warmstart

    Section 7 I/O Displays S800 Warmstart Value The actual value of the input from the process or the output value sent to the process. For an output field, you can change the value of an output channel by selecting it and entering a value. The loop needs to be warm- started from the FCM display.
  • Page 160 S800 Warmstart Section 7 I/O Displays Actions On Loop Download When a loop with an output FCM configured for warmstart is downloaded, the output mode of the FCM is placed in the MANUAL mode and the output value from the module is written to its result attribute. When a device loop configured for warmstart is downloaded, its DEV_CMND attribute is set to NO COMMAND.
  • Page 161: S100 I/O Displays

    Section 7 I/O Displays S100 I/O Displays For continuous loops with Analog and Digital Output FCMs or device loops configured for warmstart that have been warm started, the tag is shown with a white background. When CCF loops with output FCMs configured for warmstart are placed in the MANUAL mode by either a warmstart or user action, their tags are shown with a white background.
  • Page 162 S100 LAN Display Section 7 I/O Displays Figure 71. S100 LAN Display The heading fields on the S100 LAN display are described below. Devsub The controller DCN address where the S100 I/O is located. State The runtime status of the controller. ACTIVE indicates the submodule is in use.
  • Page 163: S100 Device Status Display

    Section 7 I/O Displays S100 Device Status Display The column headings for each device row on the S100 I/O overview display are described below. Device This field is the logical block number of the S100 device as specified during database configuration. Templet The logical device name created during database configuration is given in this field.
  • Page 164 S100 Device Status Display Section 7 I/O Displays Figure 72. S100 I/O Device Status Display The following is a description of the fields on the S100 I/O Device display. See the S100 overview heading descriptions for Devsub, State, Name and Lan. See the S100 overview column heading descriptions for Device, Templet, Dev Type, Comm Addr, and Dev State.
  • Page 165: Smoothstart Start-Up Sequence

    Section 7 I/O Displays Smoothstart Start-up Sequence Value The actual value of the input from the process or the output value sent to the process. For an output field, you can change the value of an output channel by selecting it and entering a value. Diagnostics Not used.
  • Page 166 S100 Warmstart Section 7 I/O Displays holding its initial command. A period of time is allowed for each S100 board to log into the system. As each board is recognized, its outputs are read. If configured for warmstart, the corresponding CCF loop output FCM for each output channel on the board is placed in the MANUAL mode and its result is synchronized with the field output value in the board memory.
  • Page 167: Profibus Displays

    Section 7 I/O Displays PROFIBUS Displays reference the same channel, only the last loop downloaded participates in warmstart and is listed on the S100 I/O Display. Operation Action With warmstart configured for output FCMs and device loops, the authorized user should: •...
  • Page 168: Profibus Lan Display

    PROFIBUS LAN Display Section 7 I/O Displays PROFIBUS LAN Display The PROFIBUS LAN display, Figure 73, shows the CI541 submodule status (CTL) and information about each device (DEV) configured under a particular LAN. From this display you can: • Select a device display target (DEV) to call up the PROFIBUS Device display. •...
  • Page 169 Section 7 I/O Displays PROFIBUS LAN Display Name The controller subsystem part of the logical name created during database configuration. This field represents the number of the Local Area Network (LAN) for all the stations shown. For the AC 460 this is LAN # 1 - 4. Go back to the controller display to select a different LAN.
  • Page 170 PROFIBUS LAN Display Section 7 I/O Displays PROFIBUS LAN Device Detail In the main section of the display, a detail window shows specific information about each PROFIBUS Device. The right scroll bar is used to view other devices on the LAN.
  • Page 171: Profibus Device Display

    Section 7 I/O Displays PROFIBUS Device Display If the device is the CI541 type CTL, selecting that icon will bring up the CI541 Diagnostics Display, Figure 74. Currently, there are no LAN diagnostics. Only the revision will be displayed. Figure 74. CI541 Diagnostics Display PROFIBUS Device Display The PROFIBUS Device display is started by selecting a configured device from the PROFIBUS LAN Display.
  • Page 172 PROFIBUS Device Display Section 7 I/O Displays Figure 75. PROFIBUS Device Display PROFIBUS Device Header Area The top of the PROFIBUS Device display identifies the device, the associated AC460 controller and has other information as described below. Devsub The controller DCN address where the device is located. State This field shows the status of the controller as ACTIVE or DOWN.
  • Page 173 Section 7 I/O Displays PROFIBUS Device Display Name The controller subsystem part of the logical name created during database configuration. This field represents the number of the Local Area Network (LAN) for all the stations shown. For the AC 460 this is LAN # 1 - 4. Go back to the controller display to select a different LAN.
  • Page 174 PROFIBUS Device Display Section 7 I/O Displays Figure 76. PROFIBUS Device Get Diagnostics and Get Device Info displays Device Detail In the main part of the display, Figure 75, a detail window shows specific information about the devices and each associated I/O module. The right scroll bar is used to view other modules.
  • Page 175 Section 7 I/O Displays PROFIBUS Device Display Station Item Description Module This is the position of the I/O module. It Number or is also a screen target to the Module Position Display. I/O modules not configured are not shown and a blank space is left. Component The component type is shown under the Type...
  • Page 176: Module/Channel Display

    Module/Channel Display Section 7 I/O Displays Module/Channel Display The PROFIBUS Module/Channel display is started by selecting a configured module from the Device Display. The Module/Channel display, Figure 77, shows information for a single module, including channel type and value, CCF or TLL tag association, channel value, data quality and diagnostics.
  • Page 177 Section 7 I/O Displays Module/Channel Display PROFIBUS Module/Channel Header Area At the top of the display there is a section related to the addressing of the I/O module as described below. Module Address Info Description Devsub The controller DCN address where the device is located. State This field shows the status of the controller as ACTIVE or DOWN.
  • Page 178: Startup

    Startup Section 7 I/O Displays PROFIBUS Module/Channel Status Area The channel status window section shows specific information about each channel of the module. A scroll bar is used to view other channels of the device. For each channel, several columns of information are displayed as described below. Channel The input (IN) or output (OUT) and channel number of the device.
  • Page 179: Trio Displays

    The TRIO runtime displays using MOD 300 are described here. For a complete description of the aspects of TRIO which operators and engineers must understand to perform their runtime functions, refer to the 800xA for TRIO/Genius, (3BUR002460*). The types of Remote I/O Displays are: •...
  • Page 180: Trio Lan Display

    TRIO LAN Display Section 7 I/O Displays TRIO LAN Display The TRIO LAN Display, Figure 78 for AC Controller and Figure 79 for SC Controller, show the status of the TRIO Field Bus and its attached blocks. From this display you can: •...
  • Page 181 Section 7 I/O Displays TRIO LAN Display Figure 79. TRIO LAN Display (SC) TRIO LAN Header Area The heading fields on the TRIO LAN display are described below. Devsub The controller DCN address where the TRIO is located. State This field shows the status of the controller as ACTIVE or DOWN. Name The controller subsystem part of the logical name created during database configuration.
  • Page 182 TRIO LAN Display Section 7 I/O Displays TRIO LAN Status Area The TRIO LAN status area represents the Field Bus Interface as described below. Redundancy Possible values are: AVAILABLE - Redundancy is configured and enabled. When it is available, the system switches buses when communications with an active block is lost.
  • Page 183 Section 7 I/O Displays TRIO LAN Display Mod/Sub This field represents the slot number of the of the controller carrier Module, and the Submodule location of the CI560 TRIO MIB submodule (AC). This field is N/A on the SC controller. State This field shows the status of the CI560 submodule (AC).
  • Page 184 TRIO LAN Display Section 7 I/O Displays Use Restart Bus if the CI560 TRIO MIB submodule does not come up as expected after a controller reboot or to restart a failed Field Bus Controller. Use Switch Bus to force a switchover of all blocks using the selected ACTIVE bus with redundancy AVAILABLE to the other bus.
  • Page 185: Trio Block Display

    Section 7 I/O Displays TRIO Block Display Block Type The type is displayed here. The actual type may be the same as the corresponding block templet or it may be different. Block State There are four possible block states: ACTIVE (shown green) INACTIVE (shown yellow) FAILED (shown red).
  • Page 186 TRIO Block Display Section 7 I/O Displays Figure 80. TRIO Block Display (Analog) Figure 81. TRIO Block Display (Counter) 3BUR002418-600 A...
  • Page 187 Section 7 I/O Displays TRIO Block Display TRIO Block Header Area The heading fields on the TRIO Block display are described below. Devsub The controller DCN address where the TRIO is located. State This field shows the status of the controller as ACTIVE or DOWN. This field represents the number of the Local Area Network (LAN) for all the stations shown.
  • Page 188 TRIO Block Display Section 7 I/O Displays TRIO Block I/O Area The TRIO Block I/O area represents the I/O data as described below. Channel Channel number. The type of channel is indicated as: IN (Input) OUT (Output) TRI (Tri state Input) BSM (Bus Switch Block controller output) The colors used to display the data quality are: •...
  • Page 189: Direct I/O Displays

    Section 7 I/O Displays Direct I/O Displays Value Current value of the channel expressed as one of the following: 0 or 1 for digital counts or engineering value for analog degrees for thermocouples degrees or ohms for RTDs A or B for BSM (Bus Switch Module) status Normally, writing an output causes the value to show red until the value is actually updated.
  • Page 190 Direct I/O Displays Section 7 I/O Displays Access the Direct I/O Display, Figure 82, from the Controller Subsystem Status display by selecting an active controller, then selecting the Display Request button and selecting Controller I/O, Alternately, you can select a direct I/O device in the Diagnostics window of the Controller Subsystem Status display.
  • Page 191: Direct I/O Block Header Area

    Section 7 I/O Displays Direct I/O Block Header Area TLL uses only the Digital I/O. Direct I/O for a controller can supply up to 40 regular digital channels and eight interrupting contact input channels. The number of points provided by direct I/O for a turbo node depends on the number of digital I/O boards in the node.
  • Page 192 If the channel type is output, the Value field is editable (TRIOCONTROL is used for special access rights as described in 800xA for MOD 300 Configuration (3BUR002417*) Normally, writing an output causes the value to show red until the value is actually updated. However, writing a forced I/O point in manual may stay red because no value is ever written back.
  • Page 193: Section 8 Operation Examples

    Typical Operator Activities All operator activities related to ongoing operations are performed using the operation displays provided with 800xA for MOD 300. Tuning parameters can be accessed from these displays. The ability to make tuning adjustment for alarm and control parameters depends on the access rights of the user.
  • Page 194: Selecting And Viewing A Control Loop

    Selecting and Viewing a Control Loop Section 8 Operation Examples Selecting and Viewing a Control Loop Object Browser Select an object from the Object Browser using the Control Structure. Click the object to access the primary display aspect. For a CCF loop, this is the Faceplate. Right click to get the context menu.
  • Page 195 Section 8 Operation Examples Selecting and Viewing a Control Loop Loop Faceplate (Auto/Local Mode) Tag description could indicate that this faceplate applies to PID control loop. The data displayed applies only to the loop which is identified by the tag name. [Pv] indicates the current measured value.
  • Page 196: Single Loop Operation In Automatic Mode

    Single Loop Operation in Automatic Mode Section 8 Operation Examples Single Loop Operation in Automatic Mode Typical operations for a single control loop in the automatic mode can be with local setpoint, remote setpoint, and remote setpoint with ratio and bias. Single Loop Automatic Operation with Local Setpoint When a control loop is configured for single loop operation with local setpoint, the faceplate displays and control button operations resemble the example below.
  • Page 197: Single Loop Automatic Operation With Remote Setpoint

    Section 8 Operation Examples Single Loop Automatic Operation with Remote Setpoint Single Loop Automatic Operation with Remote Setpoint When a control loop is configured for single loop operation with remote setpoint, the faceplate displays and control operations resembles the example shown in Figure Control loop is in automatic mode.
  • Page 198: Single Loop Automatic Operation With Ratio And Bias

    Single Loop Automatic Operation with Ratio and Bias Section 8 Operation Examples Single Loop Automatic Operation with Ratio and Bias A setpoint bumpless transfer is possible when the balance mode is enabled and the system can manipulate the ratio and/or bias to prevent process bumps. These configurations calculate a ratio or bias value that balances the remote setpoint with the local setpoint upon a switch from local to remote setpoint.
  • Page 199: Single Loop Automatic Operation With Feedforward

    Section 8 Operation Examples Single Loop Automatic Operation with Feedforward Single Loop Automatic Operation with Feedforward Feedforward control is a strategy used to compensate for disturbances in a system before they affect the controlled process variable. A feedforward control system measures a disturbance variable, predicts its effect on the process, and applies corrective action to cancel the effect of the disturbance.
  • Page 200 Single Loop Automatic Operation with Feedforward Section 8 Operation Examples The faceplate display and control button operations for feedforward control resembles the example shown in Figure with indicates that the controller is in automatic feedforward input indicates local setpoint. indicates that the loop is in the Feedback mode.
  • Page 201: Single Loop Auto/Manual Transfer

    Section 8 Operation Examples Single Loop Auto/Manual Transfer Single Loop Auto/Manual Transfer Operations required in transferring a single control loop between the automatic and manual control modes, and the influence of automatic or manual reset on these operations is described in this manual. Transfer from Manual to Automatic The faceplate displays and control button operations for the transfer from manual to automatic resembles the example shown in...
  • Page 202 Transfer from Manual to Automatic Section 8 Operation Examples Switching from Manual to Auto can be made bumpless by using the following techniques: Transfers In A Loop With Ratio Or Bias Balancing The Balance Mode field on the FCM templet is used to specify either ratio or bias automatic adjustment by the system so the Auto Output Value of the controller is equal to the Manual Output Value.
  • Page 203: Transfer From Automatic To Manual

    Section 8 Operation Examples Transfer from Automatic to Manual If the loop does not have procedureless manual reset, a setpoint or a process offset after transfer to automatic can be eliminated by adjusting the manual reset value. Transfer from Automatic to Manual The faceplate displays and control button operations for the transfer from automatic to manual resembles the example shown in Figure...
  • Page 204: Single Loop Operation In Manual Mode

    Single Loop Operation in Manual Mode Section 8 Operation Examples Single Loop Operation in Manual Mode This section describes operations when a control loop is in manual. The faceplate displays and control button operations resemble the examples shown in Figure indicates that the controller is in manual.
  • Page 205: Cascade Operation

    Section 8 Operation Examples Cascade Operation Cascade Operation A cascade control system is a multiple-loop system where the primary variable (in the master controller) is controlled by adjusting the setpoint of a related secondary variable (in the slave controller). The secondary variable then effects the primary variable through the process.
  • Page 206: Cascade Operation In Auto

    Cascade Operation in Auto Section 8 Operation Examples Master Controller Slave setpoint Slave Controller tracks slave process variable. Master output tracks slave setpoint. Slave output can be adjusted manually. Master setpoint tracks master process variable. Figure 90. Manual Cascade operation Meanwhile, the output of the master controller tracks a signal from the slave controller which represents the setpoint of the slave automatically adjusted for ratio or bias.
  • Page 207 Section 8 Operation Examples Cascade Operation in Auto Master Controller Remote slave Slave Controller setpoint tracks master output. Local setpoint on Master. Figure 91. Auto Cascade Operation • The slave setpoint tracks (automatically remains equal to) the slave process variable while in manual. This feature eliminates the need for the slave to respond immediately to any deviation when the mode is changed from manual to auto (cascade).
  • Page 208: Viewing Alarms On Mod Loop Displays

    Viewing Alarms on MOD Loop Displays Section 8 Operation Examples configured for automatic mode only. This ensures that all mode transfers and manual intervention can be accomplished exclusively at the slave. Viewing Alarms on MOD Loop Displays Alarms can be configured for each control loop to respond to an alarm condition on the process variable, the control output, and the deviation between the setpoint and process value (as a normalized measured value into the PID FCM).
  • Page 209 Section 8 Operation Examples Viewing Alarms on MOD Loop Displays CCF Control Loop Faceplate with Alarms [Pv] indicates that this display applies to the measured variable while the colored background shows an active alarm. The Pv field color blinks if the alarm is unacknowledged.
  • Page 210 Viewing Alarms on MOD Loop Displays Section 8 Operation Examples Setpoint/Process Deviation Alarm Display This display is set to alarm on the deviation between the PID setpoint and the normalized measured value input to the PID. [D] indicates that the alarm is activated by increasing deviation.
  • Page 211: Viewing Abnormal State On Mod Loop Displays

    Section 8 Operation Examples Viewing Abnormal State on MOD Loop Displays Viewing Abnormal State on MOD Loop Displays The Abnormal State field specifies whether the system should check the loop for an abnormal condition. Indicates and abnormal condition. An abnormal condition for a continuous loop is caused by any one of the following conditions: •...
  • Page 212 Viewing Abnormal State on MOD Loop Displays Section 8 Operation Examples 3BUR002418-600 A...
  • Page 213: Appendix A Runtime Templates

    Appendix A Runtime Templates Introduction The runtime versions of the Loop Definition and FCM templets are used to make tuning changes that cannot be made from the faceplate and device loop displays. Their information is always current since it comes directly from the active data base. Some fields are for reference only and are dimmed, other fields are black and are tunable.
  • Page 214 Loop Definition Templet Appendix A Runtime Templates PROCESSING RATE Field Specifies the interval at which the loop is processed (scanned). This field, the PROCESSING PHASE, and BASERATE fields interact to determine the actual loop processing rate. Scan Rate (Loop Detail display) equals the Processing Rate divided by the Base Rate.
  • Page 215 Appendix A Runtime Templates Loop Definition Templet LO ENG. UNIT LIMIT Field Specifies the lower boundary for the trend graphs. Valid entries are: a decimal number. HI ENG. UNIT LIMIT Field Specifies the upper boundary for the trend graphs. Valid entries are: a decimal number.
  • Page 216 Loop Definition Templet Appendix A Runtime Templates CUTOUT STATE Field This field defines the state the cutout source must be in to cause cutout. Cutout allows posting of the alarms to control the loop from an FCM of this or another loop.
  • Page 217 Appendix A Runtime Templates Loop Definition Templet LO ALARM PRIORITY Field This field specifies the priority level for the low alarm. Valid entries are: STD (standard priority), MED (medium priority), HIGH (high priority). BAD MEASURE ALARMS? Field This field specifies whether the bad data quality alarm for the measured variable is enabled.
  • Page 218 Loop Definition Templet Appendix A Runtime Templates ENGU ALARM DEADBAND Field This field defines a deadband for the high, low, high high, and low low alarms on the measured variable. It also becomes the deadband for any setpoint low or setpoint high alarm for the loop.
  • Page 219 Appendix A Runtime Templates Loop Definition Templet LOLO LIMIT Field This field defines the low low alarm limit for the measured variable. The alarm becomes active when the measured variable becomes equal to or less than the low low limit and clears when the measured variable increase to the value of the low low limit plus the alarm deadband.
  • Page 220 Loop Definition Templet Appendix A Runtime Templates • Loop is off • An FCM is off • Output of an FCM which is not a PID or AM Controller FCM is in MANUAL • Output mode of a PID Controller FCM or an AM Controller FCM is not in its design state as defined on its templet •...
  • Page 221: Device Loop Templet

    Appendix A Runtime Templates Device Loop Templet Device Loop Templet This section describes the active runtime fields on the Device Loop Templet. Select the Loop FCM Display and then the device block to get the runtime version of the Device Loop Templet. Use the fields at the bottom of the Loop FCM Display to make State, Mode and Command changes.
  • Page 222 Device Loop Templet Appendix A Runtime Templates PROCESSING PHASE Field This field allows for even distribution of loop processing about the processing interval. How this field, the PROCESSING PHASE field, and BASE RATE field of the CCF Templet interact to determine the loop processing rate. Valid entry is: any integer from 0 to (PR/BR-1 rounded up to the next higher integer) where PR is the processing rate of the loop and BR is the base rate of the module...
  • Page 223 Appendix A Runtime Templates Device Loop Templet Valid entry is: a decimal number identifying which bits are inverted. See the description of the INVERTED INPUTS field for an example of inverting bits. TRANSITION OVERRIDE Field A transition timeout occurs when the system issues a command to a device and the device does not go to the proper state within the time specified by the TIMER field.
  • Page 224 Device Loop Templet Appendix A Runtime Templates ALARM PRIORITY Field This field specifies the priority level for any alarms occurring for the device. Valid entries are: HIGH high (priority 1) medium (priority 2) standard (priority 3) POSTING ENABLE Field This field indicates whether posting is enabled for the loop. Posting affects the way alarm information is presented at the Operator Stations or Multibus-based consoles and on the Alarm/Event Log.
  • Page 225 Appendix A Runtime Templates Device Loop Templet NORMAL do not override the feedback timer SIMULATION MODE Field This field facilitates testing and simulating device situations with TCL or a host computer. When the Simulation Mode is ON, the device loop does not perform inputs and outputs.
  • Page 226 Device Loop Templet Appendix A Runtime Templates This is often used when the device loop interacts with a programmable controller over a PC interface. The entry NO COMMAND is used to insure the device loop does not affect the programmable controller when the device loop goes on-line.
  • Page 227 Appendix A Runtime Templates Device Loop Templet field. If you want the specified abnormal override actions to occur, you must enter a non-zero entry. Abnormal state change alarms will occur (if the device is so configured), regardless of the entry in this field. Valid entry is an amount of time in whole seconds.
  • Page 228 Device Loop Templet Appendix A Runtime Templates SPECIAL COMMAND Field This field specifies the command automatically sent to the device as part of transition override. See the description of the TRANSITION OVERRIDE field for an explanation of this feature. Valid entry is: a command from the descriptor set defined for the device on its Device Descriptor Templet SAFE COMMAND Field...
  • Page 229 Appendix A Runtime Templates Device Loop Templet Valid entries are: enable disable REVERT COMMAND Field This field specifies the command to which DEV_CMND is automatically set as part of revert. Valid entry is: a command from the descriptor set defined for the device on its Device Descriptor Templet CUTOUT ENABLE Field This field specifies whether cutout is enabled for the loop.
  • Page 230 Device Loop Templet Appendix A Runtime Templates LOG STATE CHANGES Field This field provides the means to enable or disable logging of state changes for this device (that is, an audit trail of device state change messages in a historical archive). Valid entries are: log state changes for this device.
  • Page 231: Pid Controller Fcm

    Appendix A Runtime Templates PID Controller FCM PID Controller FCM This section describes the active runtime fields on the controller FCM templets. The PID controller FCM is treated in a different manner from other FCMs because the PID Controller FCM Templet can have children. These children are the Adaptive Gain and Adaptive Reset Templets.
  • Page 232 PID Controller FCM Appendix A Runtime Templates BASE RESET Field This field specifies the base value for the reset. If no adaptive functions are turned on, the base reset is the active reset of the FCM. When an adaptive function is turned on, all changes in active reset due to the algorithm for that function are based on the base reset.
  • Page 233 Appendix A Runtime Templates PID Controller FCM PROCESS HIGH VALUE Field This field gives the value of the process input corresponding to 100.0% of the range. Valid entry is a decimal value. PROCESS LOW VALUE Field This field gives the value of the process input corresponding to 0.0% of the range. Valid entry is a decimal value.
  • Page 234 PID Controller FCM Appendix A Runtime Templates LOC/TRK/REM, LOC/TRK/RMP, LOC/TRK, LOC/REM/RMP, LOC/REM, TRK/REM/RMP, LOC/RMP, ALL MANUAL RESET MODE Field This field specifies whether the manual reset control action is used and whether it is used for bumpless transfers. If it is specified as BALANCE, the value of the manual reset is automatically adjusted by the system to provide bumpless transfers when switching to the Auto output mode.
  • Page 235 Appendix A Runtime Templates PID Controller FCM INTERACTIVE FORM Field This field specifies the method to multiply the proportional gain of the FCM by the integral. Valid entries are: YES (use interactive form), NO (use non-interactive form). INTERACTIVE FORM: Output = (G + G * (integral term)) * derivative term NONINTERACTIVE FORM: Output = (G + integral term) * derivative term ERROR SQUARED OPTION Field This field specifies whether the integral calculation uses the error signal or square of...
  • Page 236 PID Controller FCM Appendix A Runtime Templates BAD INPUTS ACCEPTED Field This field specifies whether an input with BAD data quality is treated as if the data quality is GOOD. Valid entries are: do not accept bad inputs accept bad inputs ACTION ON BAD INPUT Field This field specifies the action to take if the controller input signal goes to BAD data quality.
  • Page 237 Appendix A Runtime Templates PID Controller FCM SETPT VALUE ON FAIL Field This field specifies the setpoint value in effect upon a remote link failure. Valid entry is a value in engineering units. CHANGE SETPT ON FAIL Field This field specifies whether a new setpoint value is supplied upon a remote link failure.
  • Page 238 PID Controller FCM Appendix A Runtime Templates CHANGE OUTPUT ON FAIL Field This field specifies if a new output value is supplied upon a remote link failure. Valid entries are: do not change the output value change the output value LINK TIME-OUT Field This field specifies the initial time interval for the watchdog timer.
  • Page 239 Appendix A Runtime Templates PID Controller FCM LOCAL BIAS Field This field specifies the local bias value for the FCM. The configured entry is the initial local bias. During runtime, you can enter the local bias value at the console. Valid entry is a decimal value.
  • Page 240 PID Controller FCM Appendix A Runtime Templates LOCAL RATIO Field This field specifies the local remote setpoint ratio value for the controller. The configured entry is the initial local ratio. During runtime, you can change the local ratio value at the console. Valid entry is a value in engineering units. LIMITED RATIO MODES Field This field specifies the ratio modes to which the ratio limits are applied.
  • Page 241 Appendix A Runtime Templates PID Controller FCM The following equation is used to determine the critical value for a pulse duration output: CV = (100 x DO_RATE) where: DO_RATE is the resolution in milliseconds for the pulse digital outputs (as specified on the Controller or Multibus I/O Templet) is the 100% (HI_COUNT) value for the pulse digital outputs (as defined on the Pulse Duration Output Templet)
  • Page 242 PID Controller FCM Appendix A Runtime Templates OUTPUT LOW LIMIT Field This field specifies the low limit for the output signal. It is used to limit the output when the FCM is in the modes specified in the LIMITED OUTPUT MODES field. It is also the alarm limit if the entry in the OUTPUT LOW ALARMS? field is YES.
  • Page 243 Appendix A Runtime Templates PID Controller FCM amount). It is used when the entry in the DEVIATION HI ALARMS? field is YES. Valid entry is a decimal value in engineering units. DEVIATION LOW LIMIT Field This field specifies the low alarm limit for the deviation value (normalized measured value input to the PID FCM is less than the PID setpoint by this amount).
  • Page 244 PID Controller FCM Appendix A Runtime Templates BAD OUTPUT ALARMS Field This field specifies whether the bad data quality alarm for the output signal is enabled. If this field is YES, an alarm occurs when the data quality of the output goes to BAD.
  • Page 245: Adaptive Gain

    Appendix A Runtime Templates Adaptive Gain Alarm PRIORITY Fields These following fields specify the priority levels for their respective alarms. • OUTPUT HIGH PRIORITY • OUTPUT LOW PRIORITY • OUTPUT RATE PRIORITY • BAD OUTPUT PRIORITY • SETPOINT HIGH PRIORITY •...
  • Page 246 Adaptive Gain Appendix A Runtime Templates CONTACT STATE Field This field specifies on which state of the contacts the gain or reset is adapted by the contact adaptive function. Valid entries are: TRUE apply the contact adaptive function when the signal is true (closed contacts - non-zero) FALSE apply the contact adaptive function when the signal is false (open...
  • Page 247 Appendix A Runtime Templates Adaptive Gain REMOTE LOWER BRKPT Field This field specifies the lower breakpoint, BP1, for the remote variable adaptive function. The gain or reset changes when the remote variable becomes less than the lower breakpoint. Valid entry is decimal value with same type of units as the remote variable (engineering units or percent).
  • Page 248 Adaptive Gain Appendix A Runtime Templates OUTPUT LOWER FACTOR Field This field specifies the multiplier of the base gain or reset associated with the lower breakpoint, BP1, of the output adaptive function. Valid entry is a decimal value. PROCESS HIGH LIMIT Field This field specifies the maximum allowed value for the process adaptive contribution to the overall gain or reset.
  • Page 249: Adaptive Reset

    Appendix A Runtime Templates Adaptive Reset ERROR HIGH LIMIT Field This field specifies the maximum allowed value for the error adaptive contribution to the overall gain or reset. Valid entry is the high limit value. ERROR LOW LIMIT Field This field specifies the minimum allowed value for the error adaptive contribution to the overall gain or reset.
  • Page 250: Auto/Manual Controller Fcm

    Auto/Manual Controller FCM Appendix A Runtime Templates Auto/Manual Controller FCM The following tunable fields are the same as in the PID Controller templet: PROCESSING RATE Field ACTION ON BAD INPUT Field TRACK ACTIVATE STATE Field BAD INPUTS ACCEPTED Field INITIAL MODE Field INITIAL OUTPUT Field OUTPUT RETURN MODE Field LINK TIME-OUT Field...
  • Page 251: Input Fcms

    Appendix A Runtime Templates Input FCMs Input FCMs This section describes the active runtime fields on the input FCM templets. Common Fields INITIAL OUTPUT MODE Field This field determines the output mode for the FCM at startup. Valid entries are: AUTO FCM determines output values operator determines output values...
  • Page 252: Digital Input Fcm

    Digital Input FCM Appendix A Runtime Templates ENGU - UPPER BOUND Field This field specifies the engineering units range upper limit. Valid entry is a decimal number. See the CCF User’s Guide if the loop receives input from a smart device. Digital Input FCM INVERTED INPUTS Field This field is used to modify the input bit patterns received by the Digital Input FCM.
  • Page 253: Output Fcms

    Appendix A Runtime Templates Output FCMs Output FCMs This section describes the active runtime fields on the output FCM templets. Common Fields INITIAL OUTPUT MODE Field or INITIAL MODE Field These fields indicate the output mode for the loop at start-up and the TRIO warmstart action.
  • Page 254: Analog Output Fcm

    Analog Output FCM Appendix A Runtime Templates Controller and Multibus I/O Subsystems, this choice shuts down CCF processing when an error condition occurs. LOOP OFF turn the loop off Analog Output FCM SIGNAL INVERSION Field This field indicates whether the output signal is inverted before it is sent to the I/O Module.
  • Page 255: Digital Output Fcm

    Appendix A Runtime Templates Digital Output FCM ENGU - LOWER BOUND Field This field specifies the lower limit of the engineering units range. Valid entry is a decimal number ENGU - UPPER BOUND Field This field specifies the upper limit of the engineering units range. Valid entry is a decimal number.
  • Page 256: Common Calculator Fcm Fields

    Common Calculator FCM Fields Appendix A Runtime Templates Common Calculator FCM Fields The following fields are common to most all calculator FCMs. INITIAL MODE Field This parameter specifies if the output mode of the FCM is set at MAN (manual) or AUTO.
  • Page 257: Sum Of 4 Inputs Fcm

    Appendix A Runtime Templates Sum of 4 Inputs FCM • Exponentiation • Multiplication • Absolute Value Sum of 4 Inputs FCM The Sum of 4 Inputs FCM finds the sum of up to 4 input signals, each with an optional scaling constant. Constant 1 through Constant 4 Fields These fields specify the values of the constants.
  • Page 258: Subtraction Fcm

    Subtraction FCM Appendix A Runtime Templates Subtraction FCM The Subtraction FCM subtracts one input from another. You can use the constant factors for scaling. Constant 1 and Constant 2 Fields These fields specify the values of the constants. Valid entry is any number. Division FCM The Division FCM calculates the quotient of two input signals.
  • Page 259: Absolute Value Fcm

    Appendix A Runtime Templates Absolute Value FCM Constant 1 Field This field specifies the values of the constant. Valid entry is any number Absolute Value FCM The Absolute Value FCM calculates the absolute value of the input signal. Scale Compensation Calculator FCMs This section describes the active runtime fields on the following scale compensation calculator FCM templets.
  • Page 260: Linearization Fcm

    Linearization FCM Appendix A Runtime Templates LO ENG UNITS Field (Low Engineering Units) This field specifies the low limit of the engineering units range. Valid entry is any number. Linearization FCM This FCM uses the table look-up method to linearize an input. The linearization tables support thermocouples and RTDs (Resistance Temperature Devices) used by the system.
  • Page 261: Inverse Normalize Fcm

    Appendix A Runtime Templates Inverse Normalize FCM SCALING Field This field specifies the scaling factor. Valid entry is any number. Inverse Normalize FCM The Inverse Normalize FCM converts a value from a normalized, dimensionless, zero-based scale (percentage) to a value on an engineering units scale. LOW RANGE Field This field specifies the low range value for the input signal.
  • Page 262: Flow Calculation Fcm

    Flow Calculation FCM Appendix A Runtime Templates NEW HIGH RANGE Field This field specifies high range value of the result. Valid entry is any number. Flow Calculation FCM This FCM calculates mass and volume flow rates for liquids and gases. Its primary input is either a differential pressure measurement or a velocity measurement.
  • Page 263: Temperature Compensation Fcm

    Appendix A Runtime Templates Temperature Compensation FCM COEF THERM EXP Field This field specifies the value for the coefficient of thermal expansion. Valid entry is any number. FLOW COEFFICIENT Field This field specifies the value for the flow coefficient. Valid entry is any number. Temperature Compensation FCM The Temperature Compensation FCM calculates temperature compensated volumetric and mass flow rates for incompressible fluids.
  • Page 264: Time Related Calculator Fcms

    Time Related Calculator FCMs Appendix A Runtime Templates LOCAL BIAS Field This field specifies the local bias value. It is used when the bias mode is LOCAL. Valid entry is any number. LOCAL RATIO Field This field specifies the local ratio value. It is used when the ratio mode is LOCAL. Valid entry is any number.
  • Page 265: Time Integration Fcm

    Appendix A Runtime Templates Time Integration FCM Time Integration FCM The Time Integration FCM performs time integration on its input. The calculation is a trapezoidal approximation of the integral. SCALE FACTOR Field This field specifies the value of the scaling constant. Valid entry is any number. First Order Filter FCM The First Order Filter FCM provides a first order lag function.
  • Page 266: Lead/Lag Filter Fcm

    Lead/Lag Filter FCM Appendix A Runtime Templates UP OR DOWN Field This field specifies if the totalizer adds or subtracts each new input from the current total. Valid entries are: totalizer adds input DOWN totalizer subtracts input THRESHOLD VALUE Field This field specifies the threshold value.
  • Page 267: Dead Time Compensation Fcm

    Appendix A Runtime Templates Dead Time Compensation FCM Dead Time Compensation FCM When the process contains a dead time which threatens control loop stability, the Dead Time Compensation FCM provides a compensated process signal to the loop controller. MAX DEAD TIME Field This field specifies the value of the deadtime time interval.
  • Page 268: Delay Timer Fcm

    Delay Timer FCM Appendix A Runtime Templates counting. You can compare the count to two configured reference values, or you can initialize the count to a configured value. TIME UNITS (SECONDS) Field This field provides a means to scale the result into the desired time units. The result is usually calculated in seconds.
  • Page 269: Logic Calculator Fcms

    Appendix A Runtime Templates Logic Calculator FCMs Logic Calculator FCMs This section describes the active runtime fields on the following logic calculator FCM templets. See Common Calculator FCM Fields on page 256 for common fields. • Logical AND • Logical OR •...
  • Page 270: Logical Or

    Logical OR Appendix A Runtime Templates SHIFT DIRECTION 1 through 4 Fields These fields specify whether input bits are shifted left or right, when LOGICAL/BITWISE is BITWISE. Valid entries are: RIGHT shift input to right LEFT shift input to left Logical OR The Logical OR FCM performs the OR function on up to 4 inputs.
  • Page 271: Logical Not

    Appendix A Runtime Templates Logical NOT Logical NOT The Logical NOT FCM performs the NOT function on its input. LOGICAL/BITWISE Field Logical If inp = 0, Result = 1. If inp is not 0, Result = 0. Individual bits of input are NOTed. The inputs for bitwise type of FCM are decimal numbers translated into bit patterns by the FCM.
  • Page 272: Real Compare Fcm

    Real Compare FCM Appendix A Runtime Templates where prev is the value of the result from the previous sample period any non-zero input is treated as a 1 As long as inp2 (Reset) is 0, the result goes to 1 as soon as inp1 (Set) goes to 1. The result remains at 1 regardless of the subsequent state of inp1.
  • Page 273: Miscellaneous Calculator Fcms

    Appendix A Runtime Templates Miscellaneous Calculator FCMs Miscellaneous Calculator FCMs This section describes the active runtime fields on the following miscellaneous calculator FCM templets. See Common Calculator FCM Fields on page 256 for common runtime fields. • Selector • Put Generic Value •...
  • Page 274: Put Generic Value Fcm

    Put Generic Value FCM Appendix A Runtime Templates SELECT OP 1 through 3 Fields These fields specify the type of comparisons used for the selections that the FCM can make. SELECT OP 1 should always be defined. The other two SELECT OPs are defined as needed.
  • Page 275 Appendix A Runtime Templates Get Generic Value FCM ATTRIBUTE NAME Field This field specifies the mnemonic of the source parameter. An entry must be made to this field. Valid entry is a parameter mnemonic. DATAQUAL ATTRIBUTE Field This field specifies the parameter from which to obtain the data quality of the parameter named in the ATTRIBUTE NAME field.
  • Page 276: Select Next

    Select Next Appendix A Runtime Templates SETPT HI setpoint high alarm SETPT LO setpoint low alarm DEV DQ BDdeviation bad data quality alarm DEV HI deviation high alarm DEV LO deviation low alarm Select Next This FCM compares two inputs and determines which FCM in the loop is processed next.
  • Page 277: Input Limiter Fcm

    Appendix A Runtime Templates Input Limiter FCM Input Limiter FCM The Input Limiter FCM defines analog input high and low limits. When the input exceeds the high or low limit, the input value is clamped at the specified limit and a flag is set.
  • Page 278: Data Entry Fcm

    Data Entry FCM Appendix A Runtime Templates • A TCL program to execute the algorithm must be edited, compiled, and loaded. • A CCF loop with a UCAL FCM must be configured. When processed, the UCAL FCM starts the TCL program and makes variables available to it. The program can also pass variables back to the UCAL FCM.
  • Page 279: Mod30_Mod300_Map

    Appendix A Runtime Templates MOD30_MOD300_MAP INITIAL RESULT Field This field specifies an initial result for the FCM. It is available for the first scan of the FCM. You can view and change the value during runtime via the Loop/FCM Display. Valid entry is a real number. HIGH LIMIT Field This field specifies a high limit for the result of the FCM if the entry in the ENABLE HIGH LIMIT field is YES.
  • Page 280: Extended Processing Fcm

    Extended Processing FCM Appendix A Runtime Templates Extended Processing FCM The Extended Processing FCMs perform mathematical functions on data gathered over an extended period of time. These FCMs provide information for historical, long-range evaluation of a process, rather than for direct operational control. This section describes the active runtime fields on the following extended processing FCM templets.
  • Page 281: Continuous Moving Average Fcm

    Appendix A Runtime Templates Continuous Moving Average FCM GOOD is the only acceptable data quality for the input SAMPLE RATE Field This field specifies the interval at which the FCM samples the input value. Valid entry is in the form: hh:mm:ss the sample interval in hours, minutes, seconds The SAMPLE RATE, PERIOD UNIT, and PERIOD SIZE fields must be configured...
  • Page 282: Standard Deviation Fcm

    Standard Deviation FCM Appendix A Runtime Templates discarded. The result is always available, even if too few samples have been taken to make up the full complement specified at configuration. MAX BAD SAMPLES Field This field specifies the maximum number of bad samples allowable and present to still perform the calculation.
  • Page 283: Periodic Rate Total Fcm

    Appendix A Runtime Templates Periodic Rate Total FCM Periodic Rate Total FCM The Periodic Rate Total FCM measures an integrated total for an input over a specified time period. The time period is synchronized with the real time clock (minutes, hours, and so on). S800 I/O Runtime Templets The S800 I/O runtime templets include: •...
  • Page 284 AI810, AI890 Appendix A Runtime Templates The default value is YES. AUTO DOWNLOAD To automatically download the configuration to the I/O module enter a YES. In the future, if the configuration is to be loaded locally enter a NO. Default value is YES. CLUSTER Enter the I/O device cluster of the station where this module is located.
  • Page 285 Appendix A Runtime Templates AI810, AI890 LABEL Enter a characteristic name to identify the AI810 or AI890 Module of the station. The name may contain up to 20 characters. For the AI890 module, enter a description that includes the module type for future reference to help alleviate confusion with an AI890 being used in the AI810 templet.
  • Page 286: Ai820

    AI820 Appendix A Runtime Templates The default range is 0..20mA. REPORT FAULTS 01 through 08 If channel faults are to be reported, enter a YES; if not enter a NO. The default value is YES. RESERVED OPTIONS Used to select I/O module type: Enter: 0 (zero) for the AI810 Module 274333696 for the AI890 Module...
  • Page 287 Appendix A Runtime Templates AI820 AUTO DOWNLOAD To automatically download the configuration to the I/O module enter a YES. In the future, if the configuration is to be loaded locally enter a NO. Default value is YES. CLUSTER Enter the I/O device cluster of the station where this module is located. The cluster connected directly to the FCI is number zero (0).
  • Page 288 AI820 Appendix A Runtime Templates The default is NO. POSITION Enter a number from 1 to 12 representing the position of the I/O module relative to the FCI. The I/O module directly next to the FCI is number 1. Default value is 1. If positions are to be used for spare MTUs, the spares must be in place so the rest of the I/O modules are numbered correctly.
  • Page 289: Ai830

    Appendix A Runtime Templates AI830 VALUE CYCLE TIME Enter the channel value update period (msec) over the fieldbus. Refer to the S800 I/O User’s Guide for details of AF 100 loading in relation to cycle time. The valid values are: 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048 and 4096.
  • Page 290 AI830 Appendix A Runtime Templates FILTER 01 through 08 Enter the lowpass filter time constant (in 10msec units) for each channel. Filter times shorter than the update time are not usable. Update time can be calculated as: = 160ms + (n * 80ms) n = number of active channels 1...8 Update Therefore the T...
  • Page 291 Appendix A Runtime Templates AI830 -200..250 C, -328..482 F -200..850 C, -328..1562 F -60..180 C, -76..356 F -80..260 C, -112..500 F -100..260 C, -148..500 F 0..400 OHMS. The default range is -328..1562 F. When the user saves the templet, the sensor type is used to determine if the user entered a correct range option.
  • Page 292: Ai835

    AI835 Appendix A Runtime Templates VALUE CYCLE TIME Enter the channel value update period (msec) over the fieldbus. Refer to the S800 I/O User’s Guide for details of AF 100 loading in relation to cycle time. The valid values are: 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048 and 4096.
  • Page 293 Appendix A Runtime Templates AI835 The default value is NONE. FILTER 01 through 08 Enter the lowpass filter time constant (in 10msec units) for each channel. Filter times shorter than the update time are not usable. Update time can be calculated as: = 160ms + (n * 80ms) n = number of active channels 1...8 Update...
  • Page 294 AI835 Appendix A Runtime Templates The default entry is 0 (zero) LABEL Enter a characteristic name to identify the AI835 Module of the station. The name may contain up to 20 characters. POSITION Enter a number from 1 to 12 representing the position of the I/O module relative to the FCI.
  • Page 295: Ao810, Ao890

    Appendix A Runtime Templates AO810, AO890 PT100, that will be connected to channel 8. The type LINEAR is used if the input is a -25mV to 75mV signal. The valid values are: B, C, E, J, K, N, R, S, T, PT100 and LINEAR The default entry is J.
  • Page 296 AO810, AO890 Appendix A Runtime Templates Default value is YES. CLUSTER Enter the I/O device cluster of the station where this module is located. The cluster connected directly to the FCI is number zero (0). The number in this field is 0 -7. Default value is 0.
  • Page 297 Appendix A Runtime Templates AO810, AO890 The default value is 1024. OSP VALUE 01 through 08 Enter the channel value in counts to output after an OSP TIMEOUT. If the OSP HOLD has been selected as the OSP value then this field entry is ignored. The valid values are: 0 to 28480.
  • Page 298: Ao820

    AO820 Appendix A Runtime Templates VALUE CYCLE TIME Enter the channel value update period (msec) over the fieldbus. Refer to the S800 I/O User’s Guide for details of AF 100 loading in relation to cycle time. The valid values are: 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048 and 4096.
  • Page 299 Appendix A Runtime Templates AO820 The default value is 128. LABEL Enter a characteristic name to identify the AO820 Module of the station. The name may contain up to 20 characters. OSP HOLD 01 through 04 If an OSP TIMEOUT has occurred, will the AO810 hold the last value during OSP? Enter a YES if it will, or enter a NO if an OSP VALUE will be used.
  • Page 300 AO820 Appendix A Runtime Templates POSITION Enter a number from 1 to 12 representing the position of the I/O module relative to the FCI. The I/O module directly next to the FCI is number 1. Default value is 1. If positions are to be used for spare MTUs, the spares must be in place so the rest of the I/O modules are numbered correctly.
  • Page 301: Di810

    Appendix A Runtime Templates DI810 DI810 The DI810 templet is also used for the DI890 except as noted in the field entry descriptions. The DI890 also supports only 8 channels. ACTIVE 01 through 16 If the channel is to be active enter a YES. If the channel will not be used enter a NO.
  • Page 302 DI810 Appendix A Runtime Templates LABEL Enter a characteristic name to identify the DI810 or DI890 Module of the station. The name may contain up to 20 characters. For the DI890 module, enter a description that includes the module type for future reference to help alleviate confusion with an DI890 being used in the DI810 templet.
  • Page 303 Appendix A Runtime Templates DI810 The default value is 0 (zero). Examples from above: All with No Supervision hex number = 205A0000 converted to decimal = 542769152 All with Supervision hex number = 205A00FF converted to decimal = 542769407 Channels 4 through 1 with Supervision hex number = 205A000F converted to decimal = 542769167 Channels 8 through 5 with Supervision...
  • Page 304: Di814

    DI814 Appendix A Runtime Templates The default value is 128. DI814 The DI814 templet on an AC 400 Series controller. ACTIVE 01 through 16 If the channel is to be active enter a YES. If the channel will not be used enter a NO. The default value is YES.
  • Page 305: Di820

    Appendix A Runtime Templates DI820 MONITOR POWER To monitor process power source enter a YES; if not needed enter a NO. Default Value is NO. POSITION Enter a number from 1 to 12 representing the position of the I/O module relative to the FCI.
  • Page 306 DI820 Appendix A Runtime Templates The default value is YES. AUTO DOWNLOAD To automatically download the configuration to the I/O module enter a YES. In the future, if the configuration is to be loaded locally enter a NO. Default value is YES. CLUSTER Enter the I/O device cluster of the station where this module is located.
  • Page 307: Di821

    Appendix A Runtime Templates DI821 Default value is 1. REPORT FAULTS 01 through 08 If channel faults are to be reported, enter a YES; if not enter a NO. The default value is YES. RESERVED OPTIONS This field reserved for future use. A zero (0) should be entered as a default value. VALUE CYCLE TIME Enter the channel value update period (msec) over the fieldbus.
  • Page 308 DI821 Appendix A Runtime Templates CLUSTER Enter the I/O device cluster of the station where this module is located. The cluster connected directly to the FCI is number zero (0). The number in this field is 0 -7. Default value is 0. FILTER Enter the input filter time in msec.
  • Page 309: Do810

    Appendix A Runtime Templates DO810 RESERVED OPTIONS This field reserved for future use. A zero (0) should be entered as a default value. VALUE CYCLE TIME Enter the channel value update period (msec) over the fieldbus. Refer to S800 I/O User’s Guide for details of AF 100 loading in relation to cycle time.
  • Page 310 DO810 Appendix A Runtime Templates DQ CYCLE TIME Enter the channel data quality update period (msec) over the fieldbus. Refer to the S800 I/O User’s Guide for details of AF 100 loading in relation to cycle time. The valid values are: 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, and 4096 The default value is 128.
  • Page 311 Appendix A Runtime Templates DO810 OSP VALUE 01 through 16 Enter the channel value (0 or 1) to output after an OSP TIMEOUT. If the OSP HOLD has been selected as the OSP value then this field entry is ignored. The valid values are: 0 or 1.
  • Page 312 DO810 Appendix A Runtime Templates The default value is 0 (zero) Examples from above: All with No Supervision hex number = 205A0000 converted to decimal = 542769152 All with Supervision hex number = 205A000F converted to decimal = 542769167 Channels 4 and 1 with Supervision hex number = 205A0009 converted to decimal = 542769161 Channels 3 and 2 with Supervision...
  • Page 313: Do814

    Appendix A Runtime Templates DO814 The default value is 128. DO814 ACTIVE 01 through 16 If the channel is to be active enter a YES. If the channel will not be used enter a NO. The default value is YES. AUTO DOWNLOAD To automatically download the configuration to the I/O module enter a YES.
  • Page 314 DO814 Appendix A Runtime Templates MONITOR POWER To monitor process power source enter a YES; if not needed enter a NO. Default Value is NO. OSP HOLD 01 through 16 If an OSP TIMEOUT has occurred, will the DO814 hold the last value during OSP? Enter a YES if it will, or enter a NO if an OSP VALUE will be used.
  • Page 315: Do820

    Appendix A Runtime Templates DO820 REPORT FAULTS 01 through 16 If channel faults are to be reported, enter a YES; if not enter a NO. The default value is YES. RESERVED OPTIONS This field reserved for future use. A zero (0) should be entered as a default value. VALUE CYCLE TIME Enter the channel value update period (msec) over the fieldbus.
  • Page 316 DO820 Appendix A Runtime Templates Default value is 0. DQ CYCLE TIME Enter the channel data quality update period (msec) over the fieldbus. Refer to the S800 I/O User’s Guide for details of AF 100 loading in relation to cycle time. The valid values are: 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, and 4096 The default value is 128.
  • Page 317 Appendix A Runtime Templates DO820 OSP VALUE 01 through 08 Enter the channel value (0 or 1) to output after an OSP TIMEOUT. If the OSP HOLD has been selected as the OSP value then this field entry is ignored. The valid values are: 0 or 1.
  • Page 318: Special Applications Runtime Templets

    Special Applications Runtime Templets Appendix A Runtime Templates Special Applications Runtime Templets The runtime templets for these FCMs are implemented only in systems having special applications software installed. SP_ALGO1_FCM The runtime templet for this FCM is implemented only in systems having special application software installed.
  • Page 319: Brkpts

    Appendix A Runtime Templates BRKPTS BRKPTS The Breakpoint Sets (BRKPTS) object is a child of CCF object. One BRKPTS object is required for each breakpoint set being defined for the system. See Runtime Version of Breakpoint Sets Templet on page 57. NAME OF SET The NAME OF SET field specifies the name of the linearization table used when referencing the breakpoint set.
  • Page 320 BRKPTS Appendix A Runtime Templates 3BUR002418-600 A...
  • Page 321: Revision History

    August 2014 Updated for 800xA 6.0.3 September 2016 Updates in Revision Index A The following table shows the updates made in this User Manual for 800xA 6.0.3. Updated Section/Sub-section Description of Update Section 4 TCL Displays TCL / Unit Message Display subsection updated with Acknowledge and Message.
  • Page 322 Updates in Revision Index A 3BUR002418-600 A...
  • Page 323 Index Analog Input 286 Analog Output 298 Abnormal State 39, 45, 211 Analog output 295 Abnormal State Change 59 AO810 templet 295 About 23 AO820 298 AC410 Subsystem Status Display 130 AO890 295 to 296 AC460 Subsystem Status Display 125 Archive Messages 141 Acknowledge 61, 209 to 210 Area Alarm Display, CCF 71...
  • Page 324 Index Parameter 53 Device Descriptor State 37 Cascade Control System 205 Device Loop Templet 221 CCF 17 DI810 301 CCF Load 145 DI814 templet 304 CCF Runtime Displays 31 DI890 301 Change User 24 Diagnostic (Status) Displays 121 CI520/CI522 Submodule Status 148 Diagnostic Message List 121 CI541 Submodule Status 168 Differential Analog Input 286...
  • Page 325 Index S100 LAN 161 Alarm Indications 40 S800 Device 156 Continuous Loop 39 S800 LAN 148 Device Loop 37 to 38 S800 Station 152 Operator Controls 42 TRIO Block 185 PID Loop 34 TRIO LAN 180 Process Bargraphs and Values 40 Displays, Overview (Graphic) 26 Reduced Size 33 Displays, TCL 75...
  • Page 326 Index Group Trend Display, CCF 66 Comp Mode Restrict 219 Cutout State 216 Dmnd Processing Mode 220 Enable Hi Alarms? 216 Hard Reset 125 Enable Hihi Alarms? 218 Help 20 Enable Lo Alarms? 216 Hybrid Line Array 98 Enable Lolo Alarms? 218 Hybrid Plot 98 Enable Posting 215 Enable Rate Alarms? 217...
  • Page 327 Index Loop Mode 32, 36, 52 Tracking 44 Loop Parameter 52 Value 33, 45 Loop Setup 32, 36 Output Tracking 202 Loop State 215 Override Mode 36, 53 LOOP TMPL (Loop Definition Templet) 46, 55 Overview Type Displays 26 Loop Tuning 32 Loop, Control 49 Loop, Tuning 51 Page Selector Alarm Panel 26...
  • Page 328 Index Loading 82 Steps 85 Reduced Faceplates 33 Sequence Debug Display Redundancy Commands, TRIO 182 Breakpoint 95 Redundancy Request 131 Trace 93 Redundancy Status, AF 100 149 Sequence Debug Display, TCL 91 Redundancy Status, TRIO LAN 182 Sequence Detail Display, TCL 84 Redundant Device, S100 161 Sequence List 85, 92, 118 Refresh Rate, Trend 47...
  • Page 329 Index TCL Editor 76 Loop Definition Templet 53, 56 TCL Message Display 77 Loop Detail Display 51 TCL Recipe Editor 76 Loop FCM Display 51, 53 TCL Reply 77 Parameters 32 TCL Sequences 76 Turbo Node Subsystem Status Display 137 TCL Version Mismatch 76 Turbo/Console Node Subsystem Status Templet...
  • Page 330 Index 3BUR002418-600 A...
  • Page 332 Contact us www.abb.com/800xA Copyright© 2016 ABB. www.abb.com/controlsystems All rights reserved. Power and productivity for a better world...

Table of Contents