Abb Control Builder 3bse026333

ControlIT
Control Software and Control Builder M

Version 3.2
Product Guide
ControlIT
Control Software and Control Builder M
Version 3.2
Product Guide
NOTICE
The information in this document is subject to change without notice and should not be construed as a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document. In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB be liable for incidental or consequential damages arising from use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. Copyright 19992001 ABB All rights reserved. Release: Document number: May 2002 3BSE 026 333 R101 Rev A
TRADEMARKS
Registrations and trademarks used in this document include: Acrobat Reader Adobe Control IT Engineer IT Ethernet HART INSUM Industrial IT Solutions Microsoft ModBus OPC Operate IT PROFIBUS Windows Windows 2000 Registered trademark of Adobe Systems, Inc. Registered trademark of Adobe Systems, Inc. Trademark of ABB Automation Inc. Trademark of ABB Automation Inc. Trademark of Xerox Corporation. Registered trademark of HART Communication Foundation. Trademark of ABB Schaltanlagentechnik GmbH, Germany. Trademark of ABB Automation Inc. Registered trademark of Microsoft Corporation. Registered trademark of Modicon, Inc. Trademark of OPC Foundation. Trademark of ABB Automation Inc. Registered trademark of PROFIBUS International. Registered trademark of Microsoft Corporation. Registered trademark of Microsoft Corporation.
FOUNDATION Fieldbus Trademark of Fieldbus Foundation, USA.
TABLE OF CONTENTS
About This Book
Intended Use of This Book..............................................................................................11 Target Group.........................................................................................................11 Purpose, Scope and Intended Use ........................................................................11 Use of Information, and Tip Icons...................................................................................12 Document Conventions ...................................................................................................12 Terminology.....................................................................................................................14 Related Product Guides ...................................................................................................18
Section 1 - Key Benefits

Introduction .....................................................................................................................19 Supported Controller Platforms ...........................................................................19 Control Software ..................................................................................................19 Control Builder M ................................................................................................20 Market Segments, Licenses and Control Builder Variants...................................21 New This Version ............................................................................................................22 Control Software ..................................................................................................22 Control Builder M ................................................................................................24 OPC Server for AC 800M/C ................................................................................25 Key BenefitsSCADA and PLC Solutions......................................................................25 Control SoftwareBinary and Basic Licenses .....................................................25 Control Builder M Basic and Standard ................................................................27
3BSE 026 333 R101 Rev A
Table of Contents
Key BenefitsIntegrated Automation.............................................................................. 29 Control SoftwareAdvanced Process Control License........................................ 29 Control Builder M Professional ........................................................................... 30 Professional, Standard and Basic......................................................................... 31 Integration with Other IndustrialIT Products................................................................... 32
Section 2 - Product Description

Overview ......................................................................................................................... 33 Control Software.................................................................................................. 33 Control Builder M................................................................................................ 33 Control Software ............................................................................................................. 36 Download ............................................................................................................ 36 I/O and Fieldbus Communication........................................................................ 37 Control Network .................................................................................................. 40 Other Communication Protocols ......................................................................... 42 Time Synchronization .......................................................................................... 44 Redundancy.......................................................................................................... 45 Alarm and Events Handling................................................................................. 46 Execution of Control Software ............................................................................ 47 Control Builder M ........................................................................................................... 48 Project Explorer ................................................................................................... 48 Programming Environment.................................................................................. 50 Online Help and Manuals .................................................................................... 53 Additional Software ............................................................................................. 54 OPC Server for AC 800M/C ........................................................................................... 56 OPC Server for AC 800M/CData Access (DA) Part ......................................... 57 OPC ServerAlarm and Event (AE) Part ............................................................ 58 AC 800M/C Connect....................................................................................................... 58
3BSE 026 333 R101 Rev A
Table of Contents
Section 3 - Technical Data and Performance

General ............................................................................................................................59 Prerequisites and Requirements ......................................................................................59 Software Requirements ........................................................................................59 Hardware Requirements.......................................................................................60 OPC Server Requirements ...................................................................................61 Hardware Requirements When Running Several Products on Same PC.............62 Technical Data and Performance .....................................................................................63 Memory Consumption and Execution Times.......................................................63 Compilation and Download .................................................................................75 Hardware and I/O .................................................................................................76 MMS Communication..........................................................................................88 Control Network Clock Synchronization.............................................................92 OPC Server for AC 800M/C ................................................................................92
Section 4 - Ordering
Ordering Procedure .........................................................................................................95 Price Lists.............................................................................................................95 Ordering Example ...........................................................................................................98 Original Order ......................................................................................................98 Expansion of an Existing Installation ..................................................................99
Appendix A - Licenses
License Concept ............................................................................................................101 Control Builder M Licenses ..........................................................................................102 Expansion Licenses ............................................................................................102 Control Software Licenses.............................................................................................102 Base Licenses .....................................................................................................103 I/O Points ...........................................................................................................104 Examples of Control Software Licenses ............................................................105 OPC Server for AC 800M/C Licenses...........................................................................105
3BSE 026 333 R101 Rev A
Table of Contents
AC 800M/C Connect Licenses...................................................................................... 105 AC 800M/C Connect License Concept.............................................................. 105 AC 800M/C Connect Tags ................................................................................. 106 Tag Counting Example ...................................................................................... 107 Example of Simple AC 800M/C System Configuration ............................................... 108 Example of Integrated AC 800M/C System Configuration .......................................... 109
Appendix B - Supported Hardware and I/O Systems

Controllers..................................................................................................................... 111 AC 800M .......................................................................................................... 111 AC 800C .......................................................................................................... 113 Advant Controller 250 ....................................................................................... 114 Adapters ........................................................................................................................ 117 I/O Families................................................................................................................... 120 S100 I/O .......................................................................................................... 121 S200 I/O .......................................................................................................... 122 200L I/O .......................................................................................................... 123 S800 I/O .......................................................................................................... 123 S900 I/O .......................................................................................................... 125 ABB Standard Drives......................................................................................... 126 ABB Engineered Drives..................................................................................... 126 I/O for Updating................................................................................................. 127
Appendix C - Library Objects Overview

System Library .............................................................................................................. 130 Data Types in SystemLib ................................................................................... 131 Functions in SystemLib ..................................................................................... 134 Function Block Types in SystemLib.................................................................. 143 Supervision Signals Library .......................................................................................... 150 Function Block Types in SignalLib ................................................................... 150 Basic Library for Process Objects................................................................................. 152 Function Block Types in ProcessObjBasicLib .................................................. 152
3BSE 026 333 R101 Rev A
Table of Contents
Extended Library for Process Objects ...........................................................................154 Function Block Types in ProcessObjExtLib ......................................................155 Control Module Types in ProcessObjExtLib .....................................................156 Support Control Library ................................................................................................157 Basic Control Library ....................................................................................................158 Data Types in ControlBasicLib ..........................................................................158 Function Block Types in ControlBasicLib.........................................................158 Simple Control Functions Library.................................................................................160 Standard Control Library...............................................................................................163 Control Module Types in ControlStandardLib...................................................164 Extended Control Library..............................................................................................171 Control Modules in ControlExtendedLib...........................................................172 Advanced Control Library.............................................................................................175 Control Module Types in ControlAdvancedLib.................................................176 Fuzzy Control Library ...................................................................................................177 Control Module Types in FuzzyLib ...................................................................178 Alarm and Event Library ...............................................................................................182 Function Block Types in AlarmEventLib ..........................................................182 Control Module Types in AlarmEventLib..........................................................184 Batch Library.................................................................................................................185 Equipment Procedure Element Control Module Types......................................185 Communication Library ................................................................................................186 Data Types in CommunicationLib .....................................................................186 MODBUS...........................................................................................................186 FOUNDATION Fieldbus ...................................................................................187 COMLI MMS SattBus ...........................................................................................................189 ...........................................................................................................189 ...........................................................................................................191
Siemens 3964R...................................................................................................192 Other Function Blocks .......................................................................................192
3BSE 026 333 R101 Rev A
Table of Contents
Serial Communication Library...................................................................................... 193 Data Types ......................................................................................................... 193 Function Block Types ........................................................................................ 193 INSUM Library ............................................................................................................. 194 Introduction........................................................................................................ 194 Provided Services............................................................................................... 194 Data Types ......................................................................................................... 195 Function Block Types ........................................................................................ 196 MB300 Library.............................................................................................................. 197 Introduction........................................................................................................ 197 Function Block Types ........................................................................................ 198
INDEX
10
3BSE 026 333 R101 Rev A
About This Book

Intended Use of This Book
This Product guide does not contain last-minute product information and updates which might affect functionality and/or performance. For information on late changes and restrictions, please refer to the Release Notes.
Target Group
The prime target group of this product guide is ABB sales representatives. Other target groups are marketing and additional ABB personnel wishing to acquaint themselves with the Control Software and the Control Builder M tool.
Purpose, Scope and Intended Use

This Control Software and Control Builder M product guide describes the following items from a sales perspective: AC 800M/C Control Software functions The Control Builder M programming tool Stand-alone tools associated with Control Builder M (GSD Import Tool, IP Configuration tool, Serial Firmware Upgrade tool) OPC Server for AC 800M/C
The guide does not describe AC 800M/C Connect. This product is described in a separate product guide. See Related Product Guides on page 18. The guide is intended for use as an introduction to the new Control Software and Control Builder M versions, as well as a reference for discussion of technical solutions with customers.
3BSE 026 333 R101 Rev A
11
Use of Information, and Tip Icons
About This Book
The product guide provides: Information on key benefits An overview of functions offered by Control Software and Control Builder M Technical and performance data Instructions on how to order
Three appendices describe the licensing system, the Control Builder libraries, and Supported hardware and I/O, respectively.
Use of Information, and Tip Icons

This publication includes Information items, where appropriate to point out important information. It also includes Tip to point out useful hints to the reader. The corresponding symbols should be interpreted as follows: Information icon alerts the reader to pertinent facts and conditions.
Tip icon indicates advice on, for example, how to configure the product or how to use a certain function.
Document Conventions
The following conventions are used for the presentation of material: The words in names of screen elements (for example, the title in the title bar of a window, the label for a field of a dialog box) are initially capitalized Capital letters are used for the name of a keyboard key if it is labeled on the keyboard. For example, press the ESC key Lowercase letters are used for the name of a keyboard key that is not labeled on the keyboard. For example, the space bar, comma key, and so on Press CTRL+C indicates that you must hold down the CTRL key while pressing the C key (to copy a selected object in this case)
12
3BSE 026 333 R101 Rev A
About This Book
Document Conventions
Press ESC E C indicates that you press and release each key in sequence (to copy a selected object in this case) The names of push and toggle buttons are boldfaced. For example, click OK The names of menus and menu items are boldfaced. For example, the File menu The following convention is used for menu operations: MenuName > MenuItem > CascadedMenuItem. For example: select File > New > Type The Start menu name always refers to the Start menu on the Windows Task Bar
System prompts/messages are shown in the Courier font, and user responses/input are in the boldfaced Courier font. For example, if you enter a value out of range, the following message is displayed:
Entered value is not valid. The value must be 0 to 30.
You may be told to enter the string TIC132 in a field. The string is shown as follows in the procedure: TIC132 Variables are shown using lowercase letters. MaxLimit
3BSE 026 333 R101 Rev A
13
Terminology
About This Book
Terminology
The following is a list of terms associated with Control Software and Control Builder M. The reader should familiarize himself with these terms before going further in this product guide. The list contains only those terms and abbreviations that are unique to ABB or have a usage or definition different from standard industry usage.
Term AC 800M/C Connect Description A software package used to integrate Control Software for AC 800M/C with the Aspect Integrator Platform (AIP). AC 800M/C Connect can be installed from the ControlIT for AC 800M/C Products CD-ROM Variables that can be accessed remotely, for example from another controller Aspect Integrator Platform, the common software platform used to integrate Industrial IT software Applications contain the program code to be compiled and downloaded for execution in the controller. Applications are displayed in the Project Explorer Control Network Clock Protocol, an ABB protocol for time synchronization in Control Network Cold retain variable values are maintained after a warm or cold restart. The Cold Retain attribute overrides the retain attributes in a structured data type The programming tool described in this product guide, referred to as Control Builder throughout this document Control modules are program units that support objectoriented data flow programming with code sorting, freelayout graphical programming and static parameter connections. Instances of control modules are created from control module types ABB control software offering, including controller firmware, libraries and executable control applications
Access variables AIP Applications
CNCP Cold retain
Control Builder M Control module
Control Software
14
3BSE 026 333 R101 Rev A
About This Book
Terminology
Term Data type
Description A variables data type defines its characteristics, set of values and set of permitted operations. Data types are simple or structured, either predefined or user defined Device Type Manager, software module used to manage devices via HART using Fieldbus Builder P, via the Tool Routing Service (TRS) Function Block Diagram, one of the five languages defined in the IEC-61131 standard FOUNDATION Fieldbus, a fieldbus system of US origin A variable that can be used by all programs Gerte Stamm Datei, a hardware description file for a PROFIBUS-DP or PROFIBUS-DP/V1 slave type Highway Addressable Remote Transducer, a protocol for communication with and configuration of remote devices with HART support A method used for calculating licensing costs, see Appendix A, Licenses An IEC standard for control languages; includes Structured Text (ST), Ladder Diagram (LD), Instruction List (IL), Function Block Diagram (FBD), and Sequential Function Chart (SFC) Instruction List, one of the five languages defined in the IEC-61131 standard An instance is an individual object that behaves in accordance with the rules of the corresponding type INtegrated System for User-optimized Motor control, an ABB system for motor control Ladder Diagram, one of the five languages defined in the IEC-61131 standard
DTM
FBD FF Global variable GSD file HART
I/O point count IEC 61131-3
IL Instance INSUM LD
3BSE 026 333 R101 Rev A
15
Terminology
About This Book
Term LON MMI MMS MMS Server for AC 800M/C OPC PROFIBUS Program Project Project Explorer
Description Local Operating Network, a protocol used for INSUM fieldbus communication Man-Machine Interface Manufacturing Message Specification. a standard for messages used for industrial communication The server provides services to the MMS Client. Examples of services provided are transfer of variable content and start of programs OLE for Process Control, a standard for exchange of process control information A fieldbus system of German origin A program contains written execution code. Programs are connected to tasks with the same name A source code representation of the configuration data entered by an engineer to build a control solution The part of the Control Builder user interface used to create, modify and navigate a project. All objects such as data types, functions and function block types can be selected and displayed in an editor. All software and hardware is configured in the Project Explorer Redundant Network Routing Protocol, an ABB protocol for redundancy handling and routing in Control Network Standard No. 232 for PC communication, established by EIA (Electronics Industries Association, USA) A communication interface standard from EIA (Electronics Industries Association, USA), operating on voltages between 0V and +5V. RS-485 is more noiseresistant than RS-232C, handles data transmission over longer distances, and can drive more receivers Sequence Functional Chart, one of the five languages defined in the IEC-61131 standard
RNRP RS-232C RS-485
SFC
16
3BSE 026 333 R101 Rev A
About This Book
Terminology
Term SNTP SOE ST Task
Description Simple Network Time Protocol, a protocol used for time synchronization in Control Network Sequence-Of-Events, a logging method involving timestamping at digital inputs Structured Text, one of the five languages defined in the IEC-61131 standard A task is a work schedule for a program.Three default tasks are available; Fast, Normal and Slow. At run time, tasks are executed according to interval time, priority and offset
Tool Routing Service for See TRS AC 800M/C TRS Tool Routing Service, a part of AC 800M/C Connect. The TRS lets users use Fieldbus Builder P to configure HART devices,via AC 800M The type is a general description of a unit that defines the behavior of an instance of the type
Type
3BSE 026 333 R101 Rev A
17
Related Product Guides
About This Book
Related Product Guides

The following product guides contain information on related products and concepts.
Category Hardware, Product Guides Title AC 800M Controller Hardware 2.1, Product Guide AC 800C Controller Hardware, Version 2.0, Product Guide S800 I/O, Product Guide Software, Product Guides System Guide, System Baseline 2, May 2002 Process Portal A, Product Guide AC 800M/C Connect, Product Guide Description Description of the AC 800M controller Description of the AC 800C controller Description of the S800 I/O family Description of the total IndustrialIT product offering Description of the Process Portal A product Description of the AC 800M/C Connect product (integration with Process Portal A and other IndustrialIT suites) Description of the SCADA Portal product Description of the Fieldbus Builder P product Description of the Engineering Studio product family
SCADA Portal, version 1.1, Product Guide Fieldbus Builder PROFIBUS/HART Engineering Studio, Product Guide
18
3BSE 026 333 R101 Rev A
Section 1 Key Benefits

Introduction
Supported Controller Platforms
AC 800M/C Control Software, created with the Control Builder M programming tool, can be downloaded to and executed on the following hardware platforms. AC 800M AC 800C Advant Controller 250 For information on supported combinations of hardware, protocol and software, see Section 2, Product Description, and Appendix B, Supported Hardware and I/O Systems.
Control Software
AC 800M/C Control Software consists of firmware and control software that can be run on the supported control platforms. Control Software is not controller platform specific. A control system can be designed without considering controller platform specific issues such as the execution model, as long as supported ABB controllers are used. Control Software is also scalable. If an application becomes too big or too complex for the selected controller type, a more powerful controller can be used without changing the application.
3BSE 026 333 R101 Rev A
19
Control Builder M
Licenses
There are three levels of Control Software license: Binary Control (access to system library only) Basic Control (access to binary control, batch handling library and basic libraries) Advanced Process Control (full access to all Control Builder libraries) License costs also depend on the number of I/O points in the customers control system. Licensing issues are described in detail in Appendix A, Licenses.
Control Builder M
Control Builder M (Control Builder in this document) is a Windows 2000-based programming tool for control logic. The tool is used to program control applications for AC 800M/C controllers. See Supported Controller Platforms on page 19.
Control Builder Variants
There are three variants of Control Builder M: Control Builder Professional (same as Standard, plus access to all libraries functions and control modules; higher number of applications, more applications per controller and integration with Industrial IT products) Control Builder Standard (same as Basic, plus create and change libraries, code distribution and sharing of source code) Control Builder Basic (basic functionality only) Control Builder variants are upward compatible. This means that applications created with Basic can be used in Basic, Standard and Professional, and that applications created in Standard can be used in Standard and Professional.
20
3BSE 026 333 R101 Rev A
Market Segments, Licenses and Control Builder Variants
Libraries made with a higher level Control Builder M license can be used in a Control Builder variant of a lower level, as long as they do not violate any restriction set by the lower license level. For example, it is possible to build libraries using Control Builder Standard, for use in Control Builder Basic. It is important that the customer selects the right Control Builder Variant. For a complete comparison between the three variants, please refer to Professional, Standard and Basic on page 31.
Market Segments, Licenses and Control Builder Variants

AC 800M/C Control Software is aimed primarily at two market segments: SCADA and PLC Solutions Integrated Automation
The product line is different for these two market segments. It is important that the products and licenses best suited to the current segment are offered on each occasion.
SCADA and PLC Solutions
SCADA and PLC solutions are those where the operator interface communicates with controllers using signals, without any object integration, and where controllers do not handle alarms and events. The following products and licenses are suitable for SCADA and PLC solutions. SCADA Portal Process Panel AC 800M and AC 800C controllers Control Software: Binary and Basic licences OPC Server for AC 800M/C Control Builder: Basic and Standard variants
3BSE 026 333 R101 Rev A
21
New This Version
Integrated Automation
Integrated Automation solutions involve integrating faceplates with controllers handling objects from the operator interface. Integrated Automation also takes in handling of alarms and events in controllers. The following products and licenses are suitable for Integrated Automation. Process Portal A AC 800M/C Connect AC 800M and AC 800C controllers Control Software: Advanced Process Control licenses Control Builder: Professional variant Other integrated Aspect System products (FieldBus Builder P, Engineering Studio, etc.)
ABB Controllers
ABB AC 800M and AC 800C controllers handle control system within both the above market segments. For detailed information on ABB controller performance, see Section 3, Technical Data and Performance and the hardware product guides listed in Related Product Guides on page 18.
New This Version

The subsection below gives an overview of new functions in Control IT for AC 800M/C, version 3.1. New functions and features are divided into Control Software, Control Builder M, and OPC Server for AC 800M/C.
Control Software
Increased language support: Case statements in Structured Text (ST) Execution of control modules inside function blocks
22
3BSE 026 333 R101 Rev A
Control Software
New and expanded libraries (see Appendix C, Library Objects Overview): A number of low-level function blocks have been added to System Library New library, named Signal Library, has been added, containing function blocks used to monitor signals (internal and between applications) Increased support for building control loops using Control Library (function blocks, control modules and data types added)
Time synchronization and logging: 1 millisecond time synchronization accuracy between AC 800M nodes in Control Network 50 millisecond time synchronization accuracy for AC 800C and AC 250 controllers, using an AC 800M master in Control Network Sequence-Of-Events (SOE) logging using time stamps for digital I/O with high accuracy System alarm and system event functions
Improved redundancy functions: Redundant Control Network on MMS and TCP/IP, using Redundant Network Routing Protocol (RNRP) Line redundancy (PROFIBUS-DP/V1) for AC 800M (CI854 interface module) AC 800M CPU redundancy (using PM861)
Added CPU support: PM861 (AC 800M)
Added communication support: MasterBus300 (new master CI855) PPP for Advant Controller 250 (PM253 and PM254)
3BSE 026 333 R101 Rev A
23
Control Builder M
Added I/O support: PROFIBUS-DP/V1 (new master CI854) S100 I/O (new master CI856) INSUM support (new master CI857) S800 I/O HART modules (AI895 and AO895) S800 I/O Sequence-Of-Events (SOE) modules (DI830, DI831 and DI885) S900 I/O OSP on S200 I/O modules connected to 200-APB12 ABB Standard and Application Drives: ACS 300, ACS 400, ACS 600, ACS 1000, DCS 300, DCS 400, DCS 600
Configuration of HART devices, via AC 800M and PROFIBUS-DP/V1 Integration with other IndustrialIT products: Mirroring from Plant Explorer/Process Portal A to Control Builder M
Control Builder M
FBD/LD editor enhancements: Improved connection of functions/function blocks Improved insertion dialog for functions/function blocks Enable (EN) parameter in function blocks Improved declaration feature when inserting/connecting function blocks
Printing from editors: Printing of complete editor content (not only what fits on the screen, but the complete editor window)
Documentation can be created in online mode, allowing users to document parameter values and settings New user help function allows users to add custom online help for communication protocols, I/O protocols, libraries and applications (added online help can then be accessed from within Control Builder)
24
3BSE 026 333 R101 Rev A
OPC Server for AC 800M/C
GSD Import Tool updated to support conversion of PROFIBUS-DP/V1 GSD files Improved integration with other IndustrialIT products through Aspect Integration Platform (AIP) (for details, see AC 800M/C Connect product guide)

Attribute hidden added to variables, allows control over OPC server display of variables Saving of cold retain data in OPC server Multiple read and write operations
Key BenefitsSCADA and PLC Solutions

The following Control Software licenses and products are suitable for SCADA and PLC solutions. Control Software licenses: Binary and Basic
Control Builder variants: Basic and Standard
Control SoftwareBinary and Basic Licenses

Control Software Binary and Basic licenses offer the following key benefits for SCADA and PLC Solutions: Controller scalability: Applications can be moved from one supported controller to another. This simplifies expanding existing applications and control systems by adding applications and/or controllers
3BSE 026 333 R101 Rev A
25
Control SoftwareBinary and Basic Licenses
Software portability: Applications can be created before selecting controller hardware
One time data entry: Once entered, data is automatically accessible for all functions and units. Adding an OPC server will allow OPC clients to share data from up to 12 controllers. Variable communication allows communication between parts of the application located on different controllers
Code distribution: Applications can be distributed on several controllers. Variable communication allows communication between applications located in different controllers
Execution control: Control of priorities and execution times through task management. Power fail handling
Supervision, fault-finding and log functions: Synchronization of controller time (1 ms accuracy) throughout the control network (using AC 800M master) Logging of alarms and events Logging of system alarms and events System diagnostics tool
Redundancy support: Redundant Control Network on MMS and TCP/IP, using Redundant Network Routing Protocol (RNRP) Line redundancy for PROFIBUS-DP/V1 AC 800M CPU redundancy (PM861 only)
26
3BSE 026 333 R101 Rev A
Control Builder M Basic and Standard
Communication support (hardware dependent): MMS, SattBus, COMLI, Siemens 3964R, MODBUS, MasterBus 300, PPP on RS-485 and RS-232C Control Network Controller communication by means of MMS and named access variables
I/O support: Integrated fieldbus support: PROFIBUS DP, PROFIBUS DP/V1, FOUNDATION Fieldbus (FF) Import and conversion of PROFIBUS-DP and PROFIBUS-DP/V1 GSD files using GSD Import Tool S800 I/O and S900 I/O common controller I/O systems S100 I/O and S200 I/O systems
ABB Drives support: ABB Standard Drives ABB Application Drives

For a complete list of functions included in a particular Control Builder version, see Professional, Standard and Basic on page 31. Control Builder M Basic and Standard variants offer the following key benefits for SCADA and PLC Solutions: One time data entry: All data entered via the Control Builder interface is automatically accessible to all functions and units
Multi-user development (Control Builder Standard only): Source code can be distributed on several programming stations. User access can be controlled through user privileges and different parts of the source can be reserved or have access/updating dates restricted to certain users
3BSE 026 333 R101 Rev A
27
Graphic editor support for all five IEC 61131-3 languages: Structured Text (ST), Instruction List (IL), Function Block Diagram (FBD), Ladder Diagram (LD), and Sequential Function Chart (SFC)
Built-in hardware and I/O configuration editor for configuring supported controllers, I/O systems and I/O units. Support for code re-use and object-oriented programming: System Library containing function, data and function block types that can be instantiated and will inherit properties from their parents Users can create custom types (not in Basic)
Programming environment: Offline simulation and debug of applications Download to controllers via serial communication or Ethernet Online change of control applications Cold retain of data (kept at cold start) Backup/restore of projects Functions for creating and handling custom libraries (Control Builder Standard only)
Access to user information from within the product: Extensive context-sensitive help (accessible through F1 key) Manuals in pdf format can be opened from Help menu Documentation function allows printing complete documentation for a library or for a number of objects
Addition of external user help: Users can add online help for new communication or I/O protocols, as well as custom libraries and applications. This online help is then accessible from within the Control Builder interface
28
3BSE 026 333 R101 Rev A
Key BenefitsIntegrated Automation
Key BenefitsIntegrated Automation

The following Control Software licenses and products are suitable for solutions within Integrated Automation. Control Software licenses: Advanced Process Control
Control Builder variants: Professional AC 800M/C Connect (integration with other IndustrialIT products via Aspect Integration Platform) For more information regarding integration with other IndustrialIT products, please refer to the Industrial IT and AC 800M/C Connect product guides. See Related Product Guides on page 18.
Control SoftwareAdvanced Process Control License

Upgrading Control Software to an Advanced Process Control license adds the following key benefits for Integrated Automation: Support for code re-use and object-oriented programming: Object-oriented programming by means of control modules. Re-use of programs and single control modules.
Alarm and events handling: I/O time stamps and Sequence-Of-Events (SOE) logging Alarm and Events library with standard types
I/O support: INSUM support (hardware dependent) Integration with other IndustrialIT products, for example Process Portal A: For more information on integration, refer to the AC 800M/C Connect product guide. See Related Product Guides on page 18
3BSE 026 333 R101 Rev A
29
Control Builder M Professional
Control Builder M Professional

For a complete list of functions available in a particular Control Builder version, see Professional, Standard and Basic on page 31. Upgrading to Control Builder M Professional adds the following key benefits of interest to Integrated Automation solutions: Support for large networks: Maximum number of configured controllers is 32 (8 in Standard and 1 in Basic) Maximum number of applications is 256 (8 in Standard and 1 in Basic) Maximum number of applications per controller is 8 (1 in Standard and 1 in Basic)
Programming environment: User privileges at login increases control over source code in large development projects Control Module Diagram (CMD) editor for working with control modules (not in Basic) Code sorting in order to avoid sorting loops
Integration with other IndustrialIT products, for example Process Portal A: For more information on integration functions, refer to the AC 800M/C Connect product guide. See Related Product Guides on page 18.
30
3BSE 026 333 R101 Rev A
Professional, Standard and Basic
Professional, Standard and Basic

Table 1. Differences between Control Builder Professional, Standard and Basic
Function Create/Change libraries Create/Change/Use control modules Maximum No of controllers Maximum No of applications Maximum No of appl./controller Maximum No of progr./application Maximum number of tasks/controller Distr. code to several controllers Share code between progr. stations Source code control (multi-user) Integr. with other Industrial
IT
Professional Yes Yes 32

(1)
Standard Yes No 8 8 1 64 16 Yes Yes Yes No No
Basic No No 1 1 1 3 3 No No No No No
256 8 64 16 Yes Yes Yes Yes Yes
prod.
Logging in and user privileges
(1) The maximum number of controllers also depends on the Control Network and other factors. This means that the actual maximum number of controllers can be much lower than 32.
3BSE 026 333 R101 Rev A
31
Integration with Other IndustrialIT Products
Integration with Other IndustrialIT Products

Control Builder M software can be integrated with other IndustrialIT products via Aspect Integration Platform (AIP). Integration with AIP requires Control Builder Professional and installation of AC 800M/C Connect. The most important products for integration purposes are: Process Portal A 2.1 Engineering Studio (Bulk Data Manager and other tools) Fieldbus Builder P for HART device configuration (via AC 800M and the Tool Routing Service, which is installed with AC 800M/C Connect) This requires installation of the AC 800M/C Connect product, as well as a license for this product. AC 800M/C Connect is included on the ControlIT for AC 800M/C Products CD-ROM. For more information regarding integration with other IndustrialIT products, please refer to the IndustrialIT and AC 800M/C Connect product guides. See Related Product Guides on page 18.
32
3BSE 026 333 R101 Rev A
Section 2 Product Description

Overview
Control Software
Control Software comprises two types of software: Firmware that is downloaded to controllers and interface modules Control applications that are downloaded to, and executed in, controllers
In most cases, firmware is delivered with hardware components. However, some hardware is delivered without firmware, which means that firmware has to be downloaded. Download of firmware to controllers can be done from Control Builder M. Control applications have to be created using Control Builder, and then downloaded to controllers. Control applications can be distributed and executed on several controllers and communicate with each other using named variable communication. Control Software licenses are described in Appendix A, Licenses and in Control Software on page 19.
Control Builder M
Control Builder M is a programming tool used to create control applications and download software to controllers. Control Builder is also used to configure I/O and controller communication.
3BSE 026 333 R101 Rev A
33
Control Builder M
Programming Station
Control Builder is Windows 2000-based and can be run on most Windows 2000 platforms. However, to secure acceptable performance, a number of hardware and software requirements must be met. See Prerequisites and Requirements on page 59.
Control Builder M (OPC Server for AC 800M/C) MMS Server for AC 800M/C Standard PC (AC 800M/C Connect)
Figure 1. Control Builder and supporting software OPC Server for AC 800M/C is included in AC 800M/C Connect licenses and, if run in an integrated configuration, does not have to be ordered separately. . However, if OPC Server for AC 800M/C is used without an AC 800M/C Connect license, then a separate OPC Server for AC 800M/C license is required. See Appendix A, Licenses.
Download from Programming Station
Control Software (firmware and control applications) can be downloaded to controllers using Ethernet or via a direct serial link. The controller IP address must be known by Control Builder, communication must be set up and physical connections established.
Control Builder M Ethernet or direct serial link Controller Standard PC Control Network
Figure 2. Downloading firmware and/or applications
34
3BSE 026 333 R101 Rev A
Control Builder M
Controller Communication
There is also a need for controllers to communicate with one another and with other devices. This of course requires a control network. However, design and configuration of control networks is outside the scope of this product guide.
Programming Station Control Network
Controllers
Figure 3. Controller communication in control network Controllers, programming stations and operator stations communicate with each other through the Control Network. The Network can be used for synchronizing controller time and to send alarms and events to operator stations. Control Network also supports redundancy. If AC 800M/C Connect is installed, then AC800 M can also be used for configuring remote devices using Fieldbus Builder P and the HART protocol. Controller communication using variable communication is described under MMS Communication on page 40.
3BSE 026 333 R101 Rev A
35
Control Software
Control Software
Control Software consists of firmware and applications running in controllers. Control Software supports a number of functions: Download of firmware/applications to controllers Fieldbus communication I/O communication Control Network communication Other communication protocols Redundancy functions Time synchronization Alarm and events handling Execution of control software (applications)
Download
Firmware and applications are downloaded to the controller from the programming station using Control Builder M, see Figure 2. If Ethernet is used, the controller's IP address must be set before download. This is carried out with the the IP Configuration tool.
Firmware
Firmware can be downloaded to both CPUs and CEX modules via Ethernet or direct serial communication. Once firmware is installed in the controller, the firmware takes care of downloaded applications and ensures they run correctly. If download fails, the Serial Upgrade tool can be used to solve the problem.
Applications
Applications can be downloaded to the controller either via Ethernet, or direct serial communication. An application can be distributed between several controllers. Parts of the application are then downloaded to different controllers.
36
3BSE 026 333 R101 Rev A
I/O and Fieldbus Communication

Control Software supports a number of fieldbuses and I/O systems. Controllers can be connected to fieldbuses and other I/O systems using adapters and I/O units belonging to a number of ABB I/O families. In some cases third party products can be used.
Fieldbus Communication
Control Software supports two fieldbus systems (plus an extra version of one of these): FOUNDATION Fieldbus (FF), the most common fieldbus system in the US, can be connected to AC 800M controllers via the CI852 interface module PROFIBUS-DP, the most common fieldbus system in Europe, can be connected to all supported controllers (AC 800M, AC 800C and AC 250), AC 800M controllers via the CI851 interface module PROFIBUS-DP/V1, an enhanced version of PROFIBUS-DP, can be connected to AC 800M controllers via the CI854 interface module, offering built-in line redundancy
Control applications access built-in fieldbus functions through protocol-specific function blocks and I/O modules. Function blocks for fieldbus communication are found in the Communication library. Function blocks are described in detail in the Control Builder online help. See also Appendix C, Library Objects Overview.
SattBus
SattBus is a network standard for controller communication. SattBus can be used as a low-cost fieldbus for collection of small amounts of data under harsh conditions. SattBus can also be used on Ethernet (Advant Controller 250 only on copper wire).
ControlNet
ControlNet is a high-speed network standard for industrial applications. It is intended for fast communication between control applications and distributed I/O units.
3BSE 026 333 R101 Rev A
37
ControlNet can only be used with Advant Controller 250. For information on supported I/O modules, see Appendix B, Supported Hardware and I/O Systems.
INSUM
INSUM (INtegrated System for User-optimized Motor control) is an ABB system for motor and switch gear control and protection. AC 800M controllers can be integrated with INSUM by means of a TCP/IP gateway and a CI857 interface module. Note that INSUM and Control Network must use separate physical networks.
Control Network AC 800M controllers TCP/IP Ethernet CI857 CI857
INSUM TCP/IP gateway LonWorks Router Subnet 1 MCU 1/01 MCU 1/32 Router Subnet 2 Router
MMI
Router
Figure 4. INSUM integration with AC 800M controllers
38
3BSE 026 333 R101 Rev A
The TCP/IP gateway connects controllers to the Local Operating Network (LON) fieldbus. Motor Control Units (MCUs) are grouped into subnets accessed through a number of routers. INSUM applications handle motor and switch gear control. They can also be set to send alarm and event information to AC 800M through the TCP/IP gateway. The INSUM operator station gives direct access to INSUM functions. AC 800M controllers also have access to INSUM functions through the function blocks in the INSUM library. See Appendix C, Library Objects Overview.
MasterBus 300 (MB 300)
The MasterBus 300 (MB 300) network protocol can be used with both AC 400 and AC 800M controllers. AC 800M controllers may be connected to both Control Network and MB 300, simultaneously. The MB 300 network supports both network redundancy and time synchronization (with the accuracy offered by MB 300). Note that MasterBus 300 and Control Network must use separate physical networks.
Other I/O Systems and Families
Control Software supports the following common ABB I/O systems and families. S800 I/O, a distributed modular I/O system for communication via PROFIBUS-DP, PROFIBUS-DP/V1, or directly S900 I/O, a remote I/O system for use in hazardous areas that can be connected to controllers via PROFIBUS-DP or PROFIBUS-DP/V1 S200 I/O and S200L I/O, two compatible, modular I/O systems where S200L I/O is the light version; S200 I/O modules can be connected directly to AC 800C and AC 250, and via PROFIBUS-DP to all supported controllers S100 I/O, a rack-based I/O system, can be connected to AC 800M using the CI856 interface module
For a complete list of supported I/O modules, see Appendix B, Supported Hardware and I/O Systems.
3BSE 026 333 R101 Rev A
39
Control Network
Control Network
The recommended alternative for communication with controllers and other devices, is Control Network, a private IP domain designed for industrial applications. Control Network is based on MMS via either Ethernet or PPP on RS-232C. Routing and redundancy functions are handled by the Redundant Network Routing Protocol (RNRP), an ABB protocol for handling redundancy and for routing between nodes in a control network. In previous Control Software versions, there was a requirement for separating the control network from the client/server area of the network. This is no longer a must. However, the control network must remain protected by servers and/or firewalls and the risk of overloading the network with other traffic must be taken into account
MMS Communication
Control Network is based on Manufacturing Message Specification (MMS) protocol via Ethernet or via PPP on RS-232C. MMS is an ISO-9506 standard for sending information between industrial applications. MMS provides a number of functions, the most important for control applications are: Downloading executable code, for example from a programming station to a controller Creating, deleting, starting and stopping applications over the network Reading and writing variables over the network Obtaining information on the status of remote applications Reading and writing files over the network Alarm handling Obtaining information on the capability of remote applications Obtaining information on the revision and version of remote applications
40
3BSE 026 333 R101 Rev A
Control Network
MMS can be used on several standard network protocols, but TCP/IP should be used for MMS communication. MMS messages are handled by the MMS Server for AC 800M/C, which is installed with Control Builder M and runs as a Windows 2000 service. The MMS server works as a multiplexer between the OPC server, controllers and Control Builder M.
OPC server and Control Builder M
MMS server Ethernet
Controllers
Figure 5. The MMS server as a multiplexer between controllers, OPC server and Control Builder M
RNRP
Redundant Network Routing Protocol (RNRP) is an ABB protocol for handling redundancy functions and routing between nodes in a control network. The protocol is designed for rapid detection of network failure and instant switching to alternative paths.
3BSE 026 333 R101 Rev A
41
Other Communication Protocols

Control Software supports a number of additional communication protocols. These protocols can be used for communication between controllers, as well as with other devices
ModBus RTU
ModBus is a wide-spread communication protocol that can be used on a variety of media, such as wire, fiber optics, radio and telephony. ModBus is an asynchronous serial master/slave protocol that is executed in half-duplex. Control Software only supports ModBus RTU master functionality.
COMLI
COMLI is an ABB protocol for data transmission between controllers. It is designed for asynchronous master/slave communication in half-duplex. COMLI can be used for serial communication (RS-232C or RS-485) or for SattBus, or SattBus on TCP/IP.
Siemens 3964R
Siemens 3964R is a standard serial, point-to-point master/slave protocol. It can be used on any RS-232C or RS-485 channel. It is suitable for communicating with controllers and devices with Siemens 3964R support. Communication requires installation of the RK512 interpreter in the slave system. Control Software for AC 800M/C supports only the Siemens 3964R master protocol (no support for slave protocol).
42
3BSE 026 333 R101 Rev A
Modem Communication
There are two types of modem that can be used with Control Software: Short-distance modems using PPP, COMLI, Siemens 3964R, ModBus RTU or PROFIBUS-DP Dial-up modems using public telecommunications, COMLI is the only protocol for which dial-up modem communication is supported Note that it is still possible to set up serial modem communication using a phone line between, for example, Control Builder M and a controller, or between an external system and a controller (using AutoConnect). There are two main reasons for using modem communication: A need for increasing the maximum length of RS-232C, RS-485 and Ethernet twisted-pair connections A need for using fiber-optic communication, to eliminate either electromagnetic interference or the risk of intrusion
3BSE 026 333 R101 Rev A
43
Time Synchronization
Time Synchronization
Process Portal A
CNCP w. medium accuraccy
On-time switch
High-precision SNTP CNCP w. medium accuraccy
Control Network
CNCP*) AC 400 AC 800M
CNCP AC 800M
AC 800C
MB 300 TS
MasterBus 300
*) The direction depends on which controller is the master.
Figure 6. Time synchronization in Control Network, with an AC 800M as master Time synchronization uses Coordinated Universal Time (UTC), with an AC 800M controller as Clock Master. Time is retrieved from a time server or from some other high precision source. A high-precision version of the Simple Network Time Protocol (SNTP) is available for communication, for example with a time server that receives its time reference from a GPS time receiver. Only one controller can function as Clock Master, but several controllers can have Clock Master capability. Such a controller will attempt to take over as Clock Master if it does not receive time from the current Clock Master within a certain interval. Time is forwarded to all non-master AC 800M controllers using the Control Network Clock Protocol (CNCP), and to other controllers using SNTP or a light version of CNCP.
44
3BSE 026 333 R101 Rev A
Redundancy
The accuracy of time synchronization differs, depending on protocol and device. CNCP synchronization is accurate to 1 ms, while CNCP light is accurate to 50 ms. Time synchronization can be configured using the Control Builder M tool. Controllers running an older version of Control Software that does not support time synchronization via CNCP/SNTP must be synchronized using some other method, for example via an OPC server using MMS.
Redundancy
Control Software supports the following redundancy functions: CPU redundancy for AC 800M (PM861) Network redundancy (RNRP) Line redundancy (CI854)
CPU Redundancy
AC 800M controllers with PM861 processor can be configured for CPU redundancy. Two PM861 CPU modules are then run in parallel, one as primary and one as secondary. If the primary CPU fails, the secondary CPU automatically takes over. It is also possible to run an AC 800M controller with PM861 in single CPU mode.
CEX bus PM861 Dual AC 800M RCU link Redundant network PM861
Figure 7. Example of redundant CPU configuration
3BSE 026 333 R101 Rev A
45
Alarm and Events Handling
Network Redundancy
Network redundancy is based on the Redundant Network Routing Protocol (RNRP). This protocol is designed for rapid detection of network failure and instant switching to alternative paths.
Figure 8. Redundant Control Network Network redundancy requires two independent IP networks, one primary and one secondary. Whenever the maximum number of lost messages is exceeded, then traffic is switched to the secondary network. All devices with network redundancy must be connected to both networks. The node number must be identical in both networks Network redundancy can be implemented in part of the network. Nodes with one connection only must be connected to the primary network.
Line Redundancy
Line redundancy support is built into PROFIBUS-DP/V1 communication, through dual ports on the CI854 interface module. Line redundancy may be achieved for other communication by adding extra equipment
Alarm and Events Handling

Alarm and event handling supports the following. Disabling and enabling of alarms Acknowledgement and cancellation of alarms Filtering of alarms and events Printing of alarm and event lists on local printer System events and alarms
46
3BSE 026 333 R101 Rev A
Execution of Control Software
The Alarm and Event library contains function blocks for handling alarms and events, for example detection, notification or definition of alarm conditions. The Signal library contains function blocks for monitoring of signals, both internally and between applications System events and alarms are created in a particular controller, but can be read and acted upon by operators in other systems. The event or alarm has its origin attached to it. Alarms and events are collected and forwarded by the Alarm and Event (AE) part of the OPC server. Controllers then gain access to alarms and events from other controllers by reading data from the OPC server. Alarm and event information can also be read by other OPC clients, such as Process Portal A. See OPC ServerAlarm and Event (AE) Part on page 58. OPC Server for AC 800M/C is included in AC 800M/C Connect licenses and, if run in an integrated configuration, does not have to be ordered separately. However, if OPC Server for AC 800M/C is used without an AC 800M/C Connect license, then a separate OPC Server for AC 800M/C license is required. See Appendix A, Licenses.
Execution of Control Software

Execution of applications is supported by a number of functions: Task management gives programmers control over the execution order of different parts of the code, as well as priorities between different programs and modules. It is also possible to set an offset for a task Code distribution makes possible the simultaneous execution of different parts of an application on several controllers Access variables allow for named communication between applications running on different controllers
3BSE 026 333 R101 Rev A
47
Control Builder M
Control Builder M
Control Builder consists of the following main parts: Project Explorer Programming environment Online help and manuals
Project Explorer
The Project Explorer is the main work area of Control Builder M.
Figure 9. Control Builder M Project Explorer The content of Project Explorer menus varies slightly with the Control Builder M variant (Professional, Standard, or Basic). This overview describes the Control Builder Professional Project Explorer. The Project Explorer resembles the Windows Explorer and the tree structure contains three main branches: Libraries Applications Controllers
48
3BSE 026 333 R101 Rev A
Project Explorer
Libraries
The Libraries branch contains all libraries, (see Figure 9). The user can insert or remove standard libraries, as well as create and add custom libraries.
Applications
The Applications branch lists all applications that are handled in that particular Control Builder M installation. Each application contains data types, function block types, control module types, control modules, and programs (called Program Organization Units, POUs, in the IEC-61131-3 standard). An application can be copied to a specific controller, if required.
Controllers
The Controllers branch displays the hardware tree. The tree shows all connected controllers and the hardware units that have been associated with them. For a hardware unit to be added, the hardware definition file for that unit must be supported by Control Builder.
Figure 10. The Controllers branch in the Control Builder Project Explorer tree
3BSE 026 333 R101 Rev A
49
Programming Environment
For each controller in the hardware tree, the following items can be added and changed: Access variables that can be used for variable communication with other controllers are listed under a separate entry. Double-clicking this icon starts the access variable editor A controller hardware definition is added when the controller is created in the tree. When creating the controller, the user must select the controller type, for example AC 800M. Double-clicking on this icon starts the hardware editor, where hardware can be configured Tasks that can be associated with different applications in order to control priorities and execution order. See Execution of Control Software on page 47 Applications that should be downloaded to and executed in the controller
Editors
Using control modules, Control Builder M handles all five IEC-61131-3 languages, as well as program-oriented programming. There are six different language editors: Ladder Diagram Editor (LD Editor) Instruction List Editor (IL Editor) Structured Text Editor (ST Editor) Function Block Diagram Editor (FBD Editor) Sequence Functional Chart Editor (SFC Editor) Control Module Diagram Editor (CMD Editor) (Control Builder Professional only)
50
3BSE 026 333 R101 Rev A
Figure 11. Example of a language editor (Function Block Diagram Editor) All editors support graphic programming and contain a number of functions for creating, changing, moving, grouping and connecting graphic elements and variables. In addition to language editors, there is a Connection Editor that is used to connect input and output parameters to function blocks and functions.
Supporting Functions
The programming environment also offers a number of supporting functions: Firmware and applications can be downloaded either via Ethernet or a direct serial link Both projects and parts of the code can be access-restricted. Source code distribution is supported Code can be re-used through instantiation of types
3BSE 026 333 R101 Rev A
51
Users can create custom libraries containing function blocks or control modules. Access to these libraries can be limited to certain users or user groups. (Not possible in Control Builder Basic.) Code (types, libraries) can be set to protected, to protect intellectual capital Applications can be simulated and debugged offline, without connecting to any I/O units or external units Cold retain attributes can be set so that variables and parameter values are stored on the hard disk, and restored at cold restart Applications can be changed online Projects can be documented in a Word file, using the documentation function. This function can also be used to document libraries, or even individual function blocks or control modules (both online and offline) The complete contents of any editor can be printed at any time A Backup/Restore function A system diagnostics tool is available for fault-finding and/or optimizing an application The user has access to extensive alarm and event logs
Additional Control Builder Professional Functions
Control Builder Professional offers a number of additional functions: Object-oriented programming using control modules User login function The Control Module Diagram (CMD) editor allows for object-oriented programming using control modules Code sorting function that analyzes the execution of different parts of the control modules and finds the optimum order of execution. If a sorting loop is discovered, the user is alerted and prompted to resolve the loop. The code sorting function also points out the place in the code where the sorting loop occurred
52
3BSE 026 333 R101 Rev A
Online Help and Manuals
A larger number of connected controllers (32), a larger total number of applications (256), and more applications per controller (8) If integration with the Aspect Integration Platform (AIP) through AC 800M/C Connect is installed, it is necessary to use Control Builder Professional.
Online Help and Manuals

Online Help
Control Builder M has an extensive online help system with context-sensitive (F1) help for objects displayed in the Project Explorer. Online help is displayed for the selected object when F1 is tapped. Online help can also be displayed by clicking Help in dialog boxes or selecting it under the Help menu.
F1
Figure 12. Context-sensitive (F1) help If a library or hardware definition is added, online help can be added using the User Help function. Added files are displayed under User Help on the Help menu.
Manuals
ControlIT user manuals in pdf format are available from within Control Builder M. The documentation overview can be selected from the Help menu and a manual opened by clicking the title in the overview.
3BSE 026 333 R101 Rev A
53
Additional Software
Additional Software
Control Builder is aided by a number of additional tools and products: Control Builder Setup Wizard GSD Import tool IP Configuration tool Serial Firmware Upgrade tool MMS Server for AC 800M/C
Control Builder Setup Wizard
The Setup Wizard is used to configure Control Builder M and OPC Server for AC 800M/C, as well as RNRP.
GSD Import Tool
The GSD Import tool is used to convert PROFIBUS GSD files to a format that can be read by Control Builder M. GSD Import supports conversion of both PROFIBUS-DP and PROFIBUS-DP/V1.
IP Configuration Tool
The IP Configuration tool is used to set controller IP addresses via a direct serial channel. The initial IP address must be set before downloading firmware and applications to the controller.
Serial Firmware Upgrade Tool
The Serial Firmware Upgrade tool is used to upgrade controller CPU firmware via a direct serial channel. This tool is used as a last resort, if for some reason the normal firmware upgrade procedure fails.
54
3BSE 026 333 R101 Rev A
Additional Software
MMS Server for AC 800M/C Control Builder M and OPC Server for AC 800M/C MMS Server for AC 800M/C Control Network
Figure 13. MMS Server for AC 800M/C The MMS server handles MMS communication. It serves as a multiplexer between Control Builder M, OPC servers, and controllers.
3BSE 026 333 R101 Rev A
55

OPC Server for AC 800M/C gives OPC clients access to controller data they subscribe to. The OPC server can also be used to transfer alarm and event information. It consists of two parts: Data Access (DA) part Alarm and Event (AE) part
The OPC server exposes data to the clients (DA part) and supports the transfer of alarm and event information from attached controllers to subscribing OPC clients (AE part). OPC Server for AC 800M/C is included in AC 800M/C Connect licenses and, if run in an integrated configuration, does not have to be ordered separately. However, if OPC Server for AC 800M/C is used without an AC 800M/C Connect license, then a separate OPC Server for AC 800M/C license is required. See Appendix A, Licenses. This product guide focuses on the stand-alone use of the OPC server. When integrating Control Builder M with Process Portal A, the OPC server is included in this license. For information on OPC Server for AC 800M/C as part of AC 800M/C Connect, refer to the corresponding product guide. See Related Product Guides on page 18. For information regarding OPC server performance, possible configurations or OPC server restrictions, see Section 3, Technical Data and Performance.
56
3BSE 026 333 R101 Rev A
OPC Server for AC 800M/CData Access (DA) Part
OPC Server for AC 800M/CData Access (DA) Part

The Data Access (DA) part of the OPC server gives all OPC clients access to data stored in controllers programmed with Control Builder M. The OPC server exposes the following data to OPC clients. Variables and parameters used in applications, programs, modules, function blocks, data structures, etc. (variables can be hidden by setting a hidden attribute) Hardware configurations Access variables
It can also be used to store cold retain data. The OPC server detects the following events and updates data on each. A new version of an application and/or a controller configuration is downloaded. A new application (an application that did not previously exist) is downloaded An application is deleted from a controller One application or several new ones and a controller configuration are downloaded to a previously empty controller When integrating Control Builder M with Process Portal A, the OPC server can be used for time syncronization, based on a time stamp that is created by Process Portal A. The DA part of OPC Server for AC 800M/C supports the OPC Data Access 1.0a and OPC Data Access 2.05 standards.
3BSE 026 333 R101 Rev A
57
OPC ServerAlarm and Event (AE) Part
OPC ServerAlarm and Event (AE) Part

The Alarm and Event (AE) part of the OPC server subscribes to alarms and events generated by controllers and other devices in the control network. All these alarms and events are then stored and made accessible to OPC clients. The AE part of the OPC server also collects acknowledgements and cancellations of alarms from OPC clients and forwards them to the controller or device in question. Clients may also disable or enable alarm conditions in controllers or devices through the OPC server. The AE part of OPC Server for AC 800M/C supports the OPC Alarm and Events 1.02 standard.
AC 800M/C Connect
The AC 800M/C Connect product is an option that can be installed from the ControlIT for AC 800M/C Products CD-ROM. AC 800M/C Connect must be installed in order to run Control Builder M in integration with Process Portal A. AC 800M/C Connect also gives the user access to the AC 800M/C Tool Routing function, which allows use of the Fieldbus Builder P tool to change the setup of various HART devices via AC 800M. For information about AC 800M/C Connect product, please refer to the corresponding product guide (see Related Product Guides on page 18).
58
3BSE 026 333 R101 Rev A
Section 3 Technical Data and Performance

General
This section presents performance and technical data for Control Software and Control Builder M key functions, configuration and items. For this data to be valid, the following prerequisites and requirements must be fulfilled. Late changes might affect performance and/or functionality. For information on late changes and restrictions in the use of the product, please refer to the Release Notes.
Prerequisites and Requirements

Software Requirements
The following software recommendations must be met in order for Control Builder M to function properly. Using other software than recommended might affect performance. Table 2. Control Builder M software requirements
Software Operating system Browser Printing project documentation Reading online manuals Requirement Windows 2000 with Service Pack 2 Internet Explorer 5.5 plus SP2 or higher Microsoft Word Acrobat Reader 5.0
3BSE 026 333 R101 Rev A
59
Hardware Requirements
Hardware Requirements
The following hardware requirements must be met in order for Control Builder M to function correctly. Using hardware other than that recommended can affect performance. Table 3. Control Builder M hardware requirements
Hardware CPU Internal memory Hard disk Screen Drives Communication ports Mouse Minimum requirement Pentium 166 MHz 64 MB RAM 50 MB free (200 MB for full installation) 800x600, 32768 colors CD-ROM, local or network Ethernet or RS-232C for controller communication Standard, 3-button mouse if Control Module Editor is used Recommended for medium and large configurations Pentium II 350 MHz, or better 128 MB RAM 50 MB free (200 MB for full installation) 1280x1024, 32768 colors CD-ROM, local network Ethernet or RS-232C for controller communication Standard with scroll wheel, 3button mouse if Control Module Editor is used
60
3BSE 026 333 R101 Rev A
OPC Server Requirements
OPC Server Requirements

For a complete list of which feature is included in which Control Builder version, please refer to Professional, Standard and Basic on page 31. Table 4. OPC server software requirements
Software Operating system Browser Requirement Windows 2000 with Service Pack 2 Internet Explorer 5.5 plus SP2 or higher
Table 5. OPC server hardware requirements

Hardware CPU Internal memory Hard disk Screen Drives Communication ports Requirement Pentium 166 MHz 64 MB RAM 25 MB free (200 MB for full installation) Color or monochrome CD-ROM, local or network Ethernet for controller communication
3BSE 026 333 R101 Rev A
61
Hardware Requirements When Running Several Products on Same PC
Section 3 Technical Data
Hardware Requirements When Running Several Products on Same PC

Table 6. Hardware requirements when running Control Builder M and OPC Server for AC 800M/C on the same PC
Hardware CPU Internal memory Hard disk Screen Drives Communication ports Mouse Recommended Pentium II, 350 MHz or better 128 MB RAM 50 MB free (200 MB for full installation) 1280x1024, 32768 colors CD-ROM, local network Ethernet or RS-232C for controller communication Standard with scroll wheel, 3-button mouse if Control Module Editor is used
This recommendation is taken without consideration on the OPC client installed in the same PC. Normally the OPC client, for example Process Portal A, has higher requirement, where the recommendation should be adjusted.
62
3BSE 026 333 R101 Rev A
Technical Data and Performance
Technical Data and Performance

Memory Consumption and Execution Times
Available RAM Memory
Available RAM memory is measured after loading firmware and an "empty" project, that is to say a project that has had nothing added to it after being created.
Maximum application size = 50% of Available memory
Available memory
Empty project
Firmware
Figure 14. Available memory The memory occupied by an empty project is subtracted since this space is required regardless of the size and complexity of the application, and will be the same for all controllers. As a general rule, an application should never exceed half the size of the available memory. The reason for this is the manner in which applications are updated online: 1. 2. 3. 4. The increment (the difference between the old and the updated application) is downloaded to controller memory. A new version of the application is built in controller memory, based on the old application and the increment. The controller switches from the old to the new application. The old application is deleted.
This technique handles all updates in a very controlled and efficient way. What is required is for free memory to equal the size of the largest application. If an application comes close to the limit, it should be split in two so the two parts can be updated separately.
.
3BSE 026 333 R101 Rev A
63
Table 7. Available RAM memory

Controller AC 800M AC 800M AC 800C AC 250 AC 250 AC 250 CPU PM861 PM856/860 PM210 PM253 PM254 PM255 Total RAM 16 MB 8 MB 2 MB 2 MB 8 MB 8 MB Firmware + Empty Project 6 507 kB 4 500 kB 625 kB TBD TBD TBD Available Memory 9 493 kB 3 500 kB 1 315 kB TBD TBD TBD
Memory Consumption and Execution Times for Function Blocks and Control Modules
Memory is reserved for each defined function block type. When another instance is created, the amount of memory reserved for the instance is very small in relation to the type. This means that the memory consumed by the type itself is of great importance. The following tables show memory consumption and execution time per controller and CPU, for a number of common function blocks and control modules, as well as for a number of common control loops.
64
3BSE 026 333 R101 Rev A
Table 8. AC 800M memory consumption and execution time for function blocks and control modules
Object Function Blocks UniCore UniHSI BiCore BiHSI DriveCore Uni Bi MotorUni MotorBi ValveUni PidSimpleReal PidLoop PidLoop3P PidCascadeLoop PidCascadeLoop3P SignalBool SignalInBool SignalOutBool SignalReal SignalInReal SignalOutReal 15 716 5 560 18 260 5 924 8 004 34 696 36 656 38 764 51 452 33 944 8 544 51 928 56 368 60 344 66 788 17 008 17 576 17 716 37 132 38 576 35 512 2 680 648 4 644 792 2 038 6 072 5 212 9 396 2 068 4 344 1 468 6 336 7 344 14 684 12 544 1 616 2 452 2 420 10 844 9 508 9 520 TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD 0.076 0.0072 0.105 0.01 0.126 0.185 0.2595 0.234 0.321 0.139 0.0885 0.453 0.481 0.8235 0.807 0.03375 0.02925 0.0289 0.143 0.115 0.105 TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD First Instance Next Instance (bytes) (bytes) PM856 (ms)
PM860 (ms) PM861 (ms)
3BSE 026 333 R101 Rev A
65
Table 8. AC 800M memory consumption and execution time for function blocks and control modules
Object Control Modules UniM BiM MotorUniM MotorBiM ValveUniM AnalogInCC AnalogOutCC Level6CC ThreePosCC PidSimpleCC PidCC PidAdvancedCC 30 364 35 524 35 912 40 132 29 740 14 364 15 612 47 652 19 204 10 812 75 512 171 652 4 880 5 856 8 716 7 488 4 344 3 324 3 444 16 304 4 050 2 340 13 460 25 156 TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD 0.067 0.079 0.077 0.098 0.107 0.0977 0.104 0.173 0.221 0.134 0.453 1.163 TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD First Instance Next Instance (bytes) (bytes) PM856 (ms)
PM860 (ms) PM861 (ms)
Table 9. AC 800C memory consumption and execution time for function blocks and control modules
Object Function Blocks Bi BiCore BiHSI TBD TBD TBD TBD TBD TBD TBD TBD TBD First Instance Next Instance (bytes) (bytes) PM210 (ms)
66
3BSE 026 333 R101 Rev A
Object DriveCore MotorBi MotorUni PidCascadeLoop PidCascadeLoop3P PidLoop PidLoop3P Uni UniCore UniHSI ValveUni First Instance Next Instance (bytes) (bytes) TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD PM210 (ms) TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD
3BSE 026 333 R101 Rev A
67
Object Control Modules BiM MotorBiM MotorUniM UniM ValveUniM AnalogInCC PidAdvancedCC AnalogOutCC Level6CC ThreePosCC PidCC PidSimpleCC TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD First Instance Next Instance (bytes) (bytes) PM210 (ms)
68
3BSE 026 333 R101 Rev A
Table 10. Advant Controller 250 memory consumption and execution time for function blocks and control modules
Object Function Blocks Bi BiCore BiHSI DriveCore MotorBi MotorUn PidCascadeLoop PidCascadeLoop3P PidLoop PidLoop3P Uni UniCore UniHSI ValveUni TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD First Instance Next Instance (bytes) (bytes) PM253 (ms)
PM254 (ms) PM255 (ms)
3BSE 026 333 R101 Rev A
69
Table 10. Advant Controller 250 memory consumption and execution time for function blocks and control modules
Object Control Modules BiM MotorBM MotorUniM UniM ValveUniM AnalogInCC PidAdvancedCC AnalogOutCC Level6CC ThreePosCC PidCC PidSimpleCC TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD First Instance Next Instance (bytes) (bytes) PM253 (ms)
PM254 (ms) PM255 (ms)
70
3BSE 026 333 R101 Rev A
Execution Times for Function Block Calls
Table 11. CPU execution time per CPU for a number of standard function block calls
Function Block Type ACOFActivate (disabled) ACOFActivate (enabled) ACOFActivate (timer on) CTUD Empty FB call LevelHigh (Active) LevelHigh (not Active) PulseGenerator (1 sec. High / 1 sec. Low) PulseGenerator (disabled) PulseGenerator (High out) PulseGenerator (Low out) RTC (read) RTC (set) AC 800M PM856/860(*) (s) 33.6 39.1 90.9 12.5 4.5 12.8 12.9 51.5 AC 800M PM861 (s) TBD TBD TBD TBD TBD TBD TBD TBD AC 800C PM210 (s) TBD TBD TBD TBD TBD TBD TBD TBD AC 250 PM253 (s) TBD TBD TBD TBD TBD TBD TBD TBD AC 250 PM254 (s) TBD TBD TBD TBD TBD TBD TBD TBD AC 250 PM255 (s) TBD TBD TBD TBD TBD TBD TBD TBD
10.6 51.5 51.5 17.0 52.8
TBD TBD TBD TBD TBD
TBD TBD TBD TBD TBD
TBD TBD TBD TBD TBD
TBD TBD TBD TBD TBD
TBD TBD TBD TBD TBD
3BSE 026 333 R101 Rev A
71
Table 11. CPU execution time per CPU for a number of standard function block calls
Function Block Type SR TOn (after stopping timer) TOn (before starting timer) TOn (timer active) TP (after stopping timer) TP (before starting timer) TP (timer active) AC 800M PM856/860(*) (s) 8.16 10.1 37.9 11.3 11.5 32.8 11.3 AC 800M PM861 (s) TBD TBD TBD TBD TBD TBD TBD AC 800C PM210 (s) TBD TBD TBD TBD TBD TBD TBD AC 250 PM253 (s) TBD TBD TBD TBD TBD TBD TBD AC 250 PM254 (s) TBD TBD TBD TBD TBD TBD TBD AC 250 PM255 (s) TBD TBD TBD TBD TBD TBD TBD
(*) The execution time should be doubled for PM856.
72
3BSE 026 333 R101 Rev A
Execution Times for Operations and Function Calls
Table 12. CPU execution time for a number of standard operations and function calls
Operation/ Function a:= b - c (dint) a:= b - c (int) a:= b - c (real) a:= b * c (dint) a:= b * c (int) a:= b * c (real) a:= b / c (dint) a:= b / c (int) a:= b / c (real) a:= b + c (dint) a:= b + c (int) a:= b + c (real) a:= b <> c (dint) a:= b <> c (real) a:= b and c (Boolean) a:= b and c (word) a:= b or c (Boolean) a:= b or c (word) AC 800M AC 800M AC 800M AC 800C PM856 PM860 PM861 PM210 (s) (s) (s) (s) 2.14 2.46 7.84 2.24 2.48 6.28 3.92 3.78 17.5 2.16 2.46 8.52 3.08 7.92 2.18 2.44 2.12 2.46 1.07 1.23 3.92 1.12 1.24 3.14 1.96 1.89 8.75 1.08 1.23 4.26 1.54 3.96 1.09 1.22 1.06 1.23 TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD AC 250 PM253 (s) TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD AC 250 PM254 (s) TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD AC 250 PM255 (s) TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD
3BSE 026 333 R101 Rev A
73
Operation/ Function a:= b xor c (Boolean) a:= b xor c (word) a:= shl(b, c) (word) a:= shr(b, c) (word) dint := real (real_to_dint) real := dint Real_to_time Sqrt (real) Str1 := Str2 (string) Str1 := Str2 + Str3 (string) Time_to_real Time_to_string (0d0h0m) Time_to_string (34d10h23m 45s678ms) Time1 >= Time2 TimeElapsed AC 800M AC 800M AC 800M AC 800C PM856 PM860 PM861 PM210 (s) (s) (s) (s) 2.18 2.44 3.70 3.68 79 8.20 111.6 23.0 23.6 234 40.8 342 330 1.09 1.22 1.85 1.84 39.5 4.10 55.8 11.5 11.8 117 20.4 171 165 TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD AC 250 PM253 (s) TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD AC 250 PM254 (s) TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD AC 250 PM255 (s) TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD
36.4 13.8
18.2 6.90
TBD TBD
TBD TBD
TBD TBD
TBD TBD
TBD TBD
74
3BSE 026 333 R101 Rev A
Compilation and Download
Operation/ Function TimerHold (after stopping timer) TimerHold (before starting timer) TimerHold (timer on hold) TimerHold (timer started) AC 800M AC 800M AC 800M AC 800C PM856 PM860 PM861 PM210 (s) (s) (s) (s) 5.96 2.98 TBD TBD AC 250 PM253 (s) TBD AC 250 PM254 (s) TBD AC 250 PM255 (s) TBD
6.04
3.02
TBD
TBD
TBD
TBD
TBD
6.50 9.26
3.25 4.63
TBD TBD
TBD TBD
TBD TBD
TBD TBD
TBD TBD
Compilation and Download

It takes 1 until 1.5 minutes to compile and download a 3.5 MB complex application, from a Pentium III 1 GHz 512 MB PC, to a controller. CPU load is calculated as a percentage using the following formula. CPU load (%) = 100*(Total execution time / Total interval time) Note that applications can never use more than 70% of CPU capacity. If an application demands more than 70%, the controller will reschedule its tasks until the demand is back at 70%. Running a controller at close to 70% CPU load will result in poor performance and longer response times for peer-to-peer and OPC communication. Under all conditions peak cyclic load should be held at 65% and "static" cyclic load at 60%. If high communication throughput is important, cyclic load should be kept at 30-40%. CPU load is also influenced by other factors, such as Modulebus scan interval and the number of modules on Modulebus (AC 800M), or the scanning of ABB Drives.
3BSE 026 333 R101 Rev A
75
Hardware and I/O
Hardware and I/O

Modulebus Scanning of Digital/Analog Modules (AC 800M)
The Modulebus scanning (AC 800M) has great influence on CPU load, since I/O copying on Modulebus is handled by the controller CPU. The scan time increases as modules are added, and at a certain point Modulebus scanning will start to seriously influence CPU load. The Modulebus scan interval can be set in Control Builder. The interval must be set to fit the module requiring the shortest scan interval. A solution to this problem is to connect I/O variables requiring shorter scan times via the PROFIBUS adapters (CI851+CI854). In AC 800M, Modulebus scanning has the highest priority. The cyclic load presented for IEC-61131-3 applications includes extra load caused by Modulebus interrupts.
76
3BSE 026 333 R101 Rev A
Hardware and I/O
The following table shows CPU load and scan times for three different configurations. The desired scan time is 100 ms. Table 13. Scanning of digital/analog modules on AC 800M Modulebus, three different configurations
Item/Measured Data Digital modules No. of modules Modulebus scan interval for modules CPU load (%) Analog modules No. of modules Modulebus scan interval(1) CPU load (%) Total CPU load (%) in this case Shortest possible scan interval for all above modules (ms) CPU load at shortest scan interval (%) 24 100 (4*400) ms 2.9 7.9 33 23 2 20 (4*80) ms 1.2 4.0 4 20 5 10 (4*40) ms 6.0 11.6 5 23 72 100 ms 5.0 8 20 ms 2.8 8 10 ms 5.6 Configuration 1 Configuration 2 Configuration 3
(1) Analog modules are scanned every fourth cycle; temperature modules every eighth cycle.
The numbers in the above table can be calculated as follows.
Scan time in ms
where NDigital = No. of digital modules NAnalog = No. of analog modules T Digital = Processing time for a digital module = 70 s, TAnalog = Processing time for an analog module = 120 s,
3BSE 026 333 R101 Rev A
77
Hardware and I/O
and
Minimum Scan Interval

where TSlave = Slave frame time-out time = 256 s. The CPU load formula is only valid if TSlave >= Minimum Scan Interval.
Modulebus Scanning of ABB Drives (AC 800M)General
Scanning of ABB Drives on Modulebus also influences CPU load (for AC 800M). The CPU load should be calculated separately and added to the CPU load generated by I/O modules on the Modulebus.
Modulebus Scanning of ABB Engineered Drives (AC 800M)
Scanning of an Engineered Drive is distributed over 3*12 scan cycles. Three channels (DDS Pairs) are scanned in each scan cycle. The first two are always channels 1 and 2 (i.e. DDS Pair 10/11 and 12/13); the third will be different for each scan cycle. Table 14. Scan cycles for ABB Application Drives
Scan Cycle 1 2 3 4 5 6 7 8 DDS Pair 1 10/11 10/11 10/11 10/11 10/11 10/11 10/11 10/11 DDS Pair 2 12/13 12/13 12/13 12/13 12/13 12/13 12/13 12/13 DDS Pair 3 14/15 16/17 18/19 20/21 14/15 16/17 18/19 22/23
78
3BSE 026 333 R101 Rev A
Hardware and I/O
Table 14. Scan cycles for ABB Application Drives

Scan Cycle 9 10 11 12 DDS Pair 1 10/11 10/11 10/11 10/11 DDS Pair 2 12/13 12/13 12/13 12/13 DDS Pair 3 14/15 16/17 18/19 24/25
To scan the three DDS pairs each cycle takes approximately 1.5 ms. Therefore in a system that only contains Application drives, the scan time will be approximately 1.5 ms * number of drives. It is not possible to have a scan interval less then 2 ms for the Modulebus scanner. Thus, for one drive the scan time will be 2 ms. Example For four drives, the scan time will be 1.5 ms * 4 = 6 ms for the DDS pairs 10/11 and 12/13, and the scan interval for the remaining of the DDS pairs will be 1.5 ms * 4 * 12 = 72 ms.
Modulebus Scanning of ABB Standard Drives (AC 800M)
For ABB Standard Drives, all data sets (DDS 1/2 and DDS 3/4) are scanned in each scan cycle. It takes approximately 1 ms to scan a single Standard Drive. Example For four ABB Standard Drives the scan time will be 1 ms * 4 = 4 ms.
3BSE 026 333 R101 Rev A
79
Hardware and I/O
S800 I/O Memory Consumption
Table 15. Memory consumption for S800 I/O digital input modules
Module DI801 DI802 DI803 DI810 DI811 DI814 DI820 DI821 DI830 DI831 DI885 DI890 DP820 First Module bytes 2780 1756 1756 2796 2668 2668 1820 1756 3676 3676 2264 2012 7336 Next Module (bytes) 3509.6 2616 2670.4 3506.4 3664 3568 2580.8 2616 4504 4504 3228 2748 7836
80
3BSE 026 333 R101 Rev A
Hardware and I/O
Table 16. Memory consumption for S800 I/O digital output modules
Module DO801 DO802 DO810 DO814 DO815 DO820 DO821 DO890 First Module (bytes) 3052 1900 3176 3196 2020 2040 2024 1396 Next Module (bytes) 4052 2788 3884 3873.6 2804 2768 2784 2234.4
Table 17. Memory consumption for S800 I/O analog input modules
Module AI801 AI810 AI820 AI830 AI835 AI890 AI895 First Module (bytes) 4696 4688 2672 4572 4656 4708 4704 Next Module (bytes) 5442.4 5592 3461.6 5460.8 5531.2 5700 5456
3BSE 026 333 R101 Rev A
81
Hardware and I/O
Table 18. Memory consumption for S800 I/O analog output modules
Module AO801 AO810 AO820 AO890 AO895 First Module (bytes) 4724 4580 2652 4728 4728 Next Module (bytes) 5463.2 5666 3517.6 5744 5463.2
82
3BSE 026 333 R101 Rev A
Hardware and I/O
Table 19. Memory consumption for S900 I/O digital combined modules
Module DP910 (F12P) DP910S (F12F) DX910 (DIO8) DX910 (DIO8S) DX910 (DIO8 8I) DX910 (DIO8 8I S) First Module (bytes) 5435 4544 5792 6672 4740 5652 Next Module (bytes) 2716.8 1828 3004 3851.2 2064 2893.6
Module DO910 (DO4) First Module (bytes) 4152 Next Module (kbytes)) 1485.6
Module AI910 (AI4) AI920 (AI4I) AI921 (AI4IU) AI930 (AI4HA) AI930 (AI4HA1H) First Module (bytes) 5500 5500 5500 5500 5988 Next Module (bytes) 2904.8 2856 2856 2856 3185.6
3BSE 026 333 R101 Rev A
83
Hardware and I/O
Module AI930 (AI4HA4H) AI930 (AI4HA8H) AI931 (AI4HP) AI931 (AI4HP1H) AI931 (AI4HP4H) AI931 (AI4HP8H) AI950 (TI4R) AI950 (TI4T) First Module (bytes) 7196 8580 5460 5960 7080 8548 5384 5352 Next Module (bytes) 4361.6 5980 2832 3272 4396 5788 2796 2880.8
Module AO910 (AO) AO920 (AO4I) AO930 (AO4H) AO930 (AO4H1H) AO930 (AO4H4H) AO930 (AO4H8H) First Module (bytes) 5424 5424 5344 5844 6944 8320 Next Module (bytes) 2827.2 2828.4 2756 3094.4 4226.4 5840
84
3BSE 026 333 R101 Rev A
Hardware and I/O
This section lists memory consumption for S200L I/O and S200 I/O modules. Table 23. Memory consumption for S200L I/O modules
Module DI210 DO210 DX210 AI210 AO210 AX210 First Module (bytes) 3 256 2 974 3 206 4 718 3 072 4 020 Next Module (bytes) 2 831 2 580 2 748 4 629 2 846 3 610
Table 24. Memory consumption for S200 I/O digital input modules
Module 200-IB16 200-IB32 First Module (bytes) 3 108 4 740 Next Module (bytes) 2 904 4 448
Table 25. Memory consumption for S200 I/O digital combined modules
Module 200-IB10xOB6 200-IB16xOB16P First Module (bytes) 4 646 4 726 Next Module (bytes) 2 856 4 606
3BSE 026 333 R101 Rev A
85
Hardware and I/O
Module 200-OB8EP 200-OB16 200-OB16P 200-OB32P First Module (bytes) 3 034 4 334 2 944 4 560 Next Module (bytes) 2 746 2 598 2 546 4 460
Module) 200-IE8 First Module (bytes) 4 332 Next Module (bytes) 4 774
Table 28. Memory consumption for S200 I/O analog combined modules
Module 200-IE4xOE2 First Module (bytes) 3 402 Next Module (bytes) 3 115
Module 200-OE4 First Module (bytes) 2 828 Next Module (bytes) 2 632
86
3BSE 026 333 R101 Rev A
Hardware and I/O
Table 30. Memory consumption for S200 I/O special modules

Module 200-IT8 200-IR8 200-IR8R 200-IF4I 200-OF4I 200-IA8 200-OA8 200-IM8 200-OM8 200-OW8 200-IP2 200-IP4 First Module (bytes) 4 768 4 504 3 802 2 428 2 456 2 080 3 510 1 272 3 486 3 502 4 062 4 360 Next Module (bytes) 4 488 4 581 4 060 2 224 2 271 1 840 1 736 1 806 1 752 1 738 2 098 2 486
3BSE 026 333 R101 Rev A
87
MMS Communication
The performance data for S100 I/O modules is not available, because that the implementation is not ready yet.
MMS Communication
Serial communication performance is affected by transmission speed, message length and application load. MMS communication takes place serially and asynchronously, according to the master/slave (or client/server) principle. The master channel of a system initiates the message transmission sequence, while a system acting as a slave simply responds to the calls from the master via a slave channel. The following table shows the performance of a master system in terms of messages per second for MMSWrite and MMSRead commands respectively.
.
88
3BSE 026 333 R101 Rev A
MMS Communication
Table 31. Performance of MMS master system

Application load in master (%) 0 0 0 0 0 0 50 50 50 50 50 50 Messages/sec. Messages/sec. Messages/sec. Messages/sec. AC 800M, AC 800M, AC 800C AC 800C AC 250 AC 250 Write Read Read Write 190 65 45 71 42 185 95 32 21 34 21 86 188 84 71 75 81 184 94 51 46 51 52 93 20.0 4.3 2.7 5.1 3.0 17.3 8.4 1.8 1.2 2.2 1.3 7.0 20.2 10.7 7.9 11.6 9.8 19.4 8.6 4.6 3.4 4.9 4.2 8.4
Data type
1 dint or 1 bool 159 dint 319 bool 136 real 190 string [1] 6 string [140] 1 dint or 1 bool 159 dint 319 bool 136 real 190 string [1] 6 string [140]
The two tables on the following pages show the influence of application load in slave systems (new measurements must be taken to deliver up-to-date values).
3BSE 026 333 R101 Rev A
89
MMS Communication
Table 32. Performance of a slave system, AC 800M and Advant Controller 250.
Application load in slave (%) 1 dint or 1 bool Write command from master 0 10 40 50 69 0 10 40 50 69 208 206 136 112 67 202 208 135 110 66 Messages/sec. 319 bool 90 64 72 50 41 38 25 21 12 159 dint 118 110 102 64 62 60 39 32 19 136 real 130 111 87 62 74 73 48 39 23
90
Read command from master
3BSE 026 333 R101 Rev A
MMS Communication
Table 33. Performance of a slave system, AC 800C

Application load in slave (%) 1 dint or 1 bool Write command from master 0 10 40 50 70 0 10 40 50 70 20.4 16.5 11.7 8.6 4.3 17.2 16.8 10.9 8.0 3.7 Messages/sec. 319 bool 2.4 2.3 1.5 1.5 0.7 159 dint 3.8 3.7 2.4 1.9 1.0 136 real 4.5 4.4 2.7 2.1 1.2
3BSE 026 333 R101 Rev A
Read command from master
Note that the performance values presented here were obtained under optimized conditions. Several function blocks have been triggered in parallel at a short interval time (10 ms) to get the maximum communication rate. Please consider these facts when you use the figures for your communication design. Note also that extensive use of named access variables deteriorates performance. The application internal communication load can be monitored from Control Builder M. The Ethernet standard allows bandwidth transmission at 10 Mb/s, 100 Mb/s (fast Ethernet), and 1000 Mb/s (gigabit Ethernet), but ControlIT for AC 800M/C currently supports only 10 Mb/s.
91
Control Network Clock Synchronization
Control Network Clock Synchronization

Clock Synchronization
SNTP : 1 ms CNCP (between AC 800M): 1 ms CNCP (AC 800M to AC 800C/250): 200 ms

MB300:
Transmission speed: 200 packet/sec Time synchronization: 3 ms

The OPC Server for AC 800M/C collects data from controllers via MMS, and makes it available to OPC clients. Performance depends on the amount of MMS traffic between the OPC server and controllers. This, in turn, depends on the number of items and the rate at which the items are updated in the OPC Server. The following information is based on an OPC Server for AC 800M/C running on a PC with a Pentium III, 1 GHz processor and 512 Mbyte RAM. OPC Server for AC 800M/C can handle more than 25000 different variables in total. This means that, at this update rate, one OPC client can subscribe to 30000 items or 4 OPC clients can subscribe to 7500 items each. Performance also depends on the controller's ability to provide the OPC server with data. This ability is controller-dependent and shown in the table below. Values are based on an update rate of 1.0 s.
92
3BSE 026 333 R101 Rev A
Table 34. Number of variables read per second at 1.0 s update rate
Controller/CPU AC 800M / PM861 AC 800M / PM860 AC 800C / PM210 AC 250 / PM253 AC 250 / PM254 AC 250 / PM255 18000 25 31500 1600 40 27 Total Items CPU Load (%) Transmission Speed (telegram/s) TBD 94 6 TBD TBD 54
This data is tested on a Pentium III, 800 MHz processor and 512 Mbyte RAM.
3BSE 026 333 R101 Rev A
93
94
3BSE 026 333 R101 Rev A
Section 4 Ordering
Ordering Procedure
The product guide is aimed to assist ABB sales representatives in ordering Control Software and Control Builder M licenses and products. This section describes the price lists required when ordering and provides an example of an order. However, it is outside the scope of this product guide to give a complete description of all ordering procedures and tools. It is assumed that each ABB sales representative is familiar with price lists, CAST and other tools to order.
Price Lists
Counting I/O Points
The licensing system for Control Software licenses is based on counting I/O points. The I/O point count is calculated based on the number of variables used on local and remote I/O channels, and on variables used in communication with third party systems. Each Boolean variable counts as one I/O point, while each non-Boolean variable counts as two points. See Appendix A, Licenses.
Control Software Base Licenses, version 3.1
Document no: 3BSE 025 497 Use this price list to order the following Control Software licenses. Binary Control License for AC 800M/C, with or without I/O point support Basic Control License for AC 800M/C, with or without I/O point support
3BSE 026 333 R101 Rev A
95
Price Lists
Section 4 Ordering
Advanced Process Control License for AC 800M/C, with or without I/O point support Optional Advanced Control License for Fuzzy Control Library (this option might be removed)
Control Software Expansion Licenses, version 3.1
Document no: 3BSE 025 498 Use this price list to order the following Control Software licenses. Binary Control I/O Expansion License for AC 800M/C, from x to y I/O Points (for a number of x and y values) Basic Control I/O Expansion License for AC 800M/C, from x to y I/O Points (for a number of x and y values) Advanced Process Control I/O Expansion License for AC 800M/C, from x to y I/O Points (for a number of x and y values) Note that it might be necessary to obtain several I/O point expansion licenses should the I/O point count increase notably. Should the need for I/O point support increase from x to z, then two licenses are required: one for expansion from x to y I/O points, and one for expansion from y to z I/O points. Optional Advanced Control License for Fuzzy Control Library (this option might be removed) Expansion to a higher license level from Binary Control to Basic Control, with or without I/O Point support Basic Control to Advanced Control, with or without I/O Point support Binary Control to Advanced Control, with or without I/O Point support
96
3BSE 026 333 R101 Rev A
Section 4 Ordering
Price Lists
Control Builder M Base Licenses, version 3.1
Document no: 3BSE 028 325 Use this price list to order the following Control Builder M licenses Control Builder M Basic Control Builder M Standard Control Builder M Professional
Control Builder M Expansion Licenses, version 3.1
Document no: 3BSE 028 326 Expansion to a higher Control Builder M license level from Basic to Standard Basic to Professional Standard to Professional
OPC Server for AC 800M/C Licenses, version 3.1
Document no: 3BSE 025 500 Use this price list to order the following OPC Server for AC 800M/C licenses. License for OPC Server, version 3.1, Support for Data Access and Alarm/Event
AC 800M/C, Product Box (sw ver. 3.1) and Manuals
Document no: 3BSE 025 501 This price list is used for ordering the following ControlIT products. ControlIT for AC 800M/C, Product Box, version 3.1 ControlIT for AC 800M/C, CD only, version 3.1 ControlIT for AC 800M/C, version 3.1, individual manuals
3BSE 026 333 R101 Rev A
97
Ordering Example
Section 4 Ordering
Ordering Example
For information on how to calculate I/O points, refer to Appendix A, Licenses. The first part of this example shows how to use price lists to order a "normal" Control Software and Control Builder M constellation. The second part shows how to use the price lists to expand the original order.
Original Order
The following is to be ordered: A Control Builder M Standard License A Control Software Basic Control License, with support for up to 50 I/O points To create a working margin, it is recommended that a 20 percent margin be used when calculating the number of I/O points. The above 50 I/O points are assumed to include such a margin. Step-by-step Example: 1. 2. 3. 4. 5. Find the correct price list for the Control Builder Standard license: The Control Builder M license price list has the number 3BSE 028 325 Find the correct heading and item number: 1.4 Control Builder Standard, A205 Find the correct price list for Control Software Base licenses: The Control Software Base license price list has the number 3BSE 025 497 Find the correct heading and item number: 3.1 Basic License, C008 Find the correct heading for I/O support and the I/O Point level immediately above 50 I/O points: 3.2 I/O Point Support, C015 corresponds to a maximum of 64 I/O points
Order A205 from list number 3BSE 028 325. Order C008 and C015 from price list number 3BSE 025 497.
98
3BSE 026 333 R101 Rev A
Section 4 Ordering
Expansion of an Existing Installation

The license ordered in the first part of the example is to be expanded. The following should be included on the expansion order: An expansion license from Basic Control to Advanced Process Control The license should support 180 I/O points, instead of the 64 I/O points supported by the current license
Step-by-step example: 1. Find the correct price list for expansion of Control Software licenses: The Control Software Expansion Licenses price list has the number 3BSE 025 498. Find the correct heading for expanding the license: 7.1 Base License (no I/O Support), F008 is used for expansion from Basic Control to Advanced Process Control, and F015 is required for support of up to 64 I/O points. Find the correct heading for expanding the number of I/O points for an Advanced Process Control license: 4.1 Incremental licenses for expansion of I/O support are used to expand the number of I/O points for an Advanced Process Control license. Find the items corresponding to expansion from 64 to 180 I/O points: 4.1 Incremental licenses for expansion of I/O support, C020 expands I/O point support from 64 to 128 I/O points, and C025 expands I/O point support from 128 to 200 I/O points Note that expanding I/O point support from 64 to 200 points requires two I/O point expansion licenses, C020 and C025. Order F008, F015, C020 and C025 from price list number 3BSE 025 498.
2.
3.
4.
3BSE 026 333 R101 Rev A
99
Section 4 Ordering
100
3BSE 026 333 R101 Rev A
Appendix A Licenses
License Concept
The license concept for AC 800M/C controllers is as follows. A license is required for the Control Builder M engineering and programming tool. There are three Control Builder variants, each with its own license (Basic, Standard, and Professional) A runtime license is required for each controller, for running and executing applications. It is called a Control Software license, and is based on two independent factors: the libraries used the number of used I/O points (see definition below)
A license is required for integration between Control Software and other IndustrialIT products, either through OPC Server for AC 800M/C (in which case integration can include third party products) or through AC 800M/C Connect. If OPC Server for AC 800M/C is used without AC 800M/C Connect, then a specific OPC Server for AC 800M/C license is required. If AC 800M/C Connect is installed, the license cost is based on the tag count, see AC 800M/C Connect Tags on page 106. The OPC Server for AC 800M/C license is then included in the AC 800M/C Connect license.
3BSE 026 333 R101 Rev A
101
Control Builder M Licenses
Appendix A Licenses
Control Builder M Licenses

A license is required for each Control Builder M variant: Control Builder M Basic Control Builder M Standard Control Builder M Professional
Control Builder M Professional is required when using AC 800M/C Connect.
Expansion Licenses
Special licenses are required for moving from one Control Builder M variant to another: Control Builder M Basic to Control Builder M Standard Control Builder M Basic to Control Builder M Professional Control Builder M Standard to Control Builder M Professional
Control Software Licenses

Control Software licenses consist of a Base License (see below), with support for a number of I/O points.
In controller Large numbers of I/O points
A few libraries
Several and more advanced libraries
Small numbers of I/O points
Figure 15. Control Software licenses are based on the libraries used in applications and on the I/O point count To find out which Control Software license to use, look up the relevant Base license (see Base Licenses on page 103) count the I/O point (see I/O Points on page 104), and find the right combination in the price list.
102
3BSE 026 333 R101 Rev A
Appendix A Licenses
Base Licenses
Base Licenses
There are three Control Software Base licenses. Binary Control Basic Control Advanced Process Control
The fuzzy control library, FuzzyLib, can be ordered as an option. The following table shows the libraries included in each Base license type. Libraries containing supporting functions only (such as ControlSupportLib and IconLib) are not included. Table 35. Libraries included in different Base license types
License Level Binary Control Basic Control Libraries
SystemLib SystemLib CommunicationLib(1) ProcessObjBasicLib ControlBasicLib ControlSimpleLib SerialLib SignalObjLib BatchLib ControlStandardLib(2)
(1)
Advanced Process Control
SystemLib CommunicationLib AlarmEventLib

(1)
ControlExtendedLib(2) ControlAdvancedLib(2) SerialLib SignalObjLib BatchLib(1) INSUMLib
ProcessObjBasicLib ProcessObjExtLib(1) ControlBasicLib ControlSimpleLib FuzzyLib(2)
FuzzyLib Option
(1) This library contains control modules, the use of which requires Control Builder M Professional. (2) This library consists of control modules which require Control Builder M Professional.
3BSE 026 333 R101 Rev A
103
I/O Points
Appendix A Licenses
Expansion Licenses
Base licenses can be expanded through the following three expansion licenses: Binary Control to Basic Control Basic Control to Advanced Process Control Binary Control to Advanced Process Control
I/O Points
The I/O point count is based on all variables connected to local and remote I/O channels. Variables are either connected via the I/O buses, such as Modulebus, FOUNDATION Fieldbus (FF) and Profibus-DP. Each variable of Boolean data type counts as one I/O point Each variable of non-Boolean data type counts as two I/O points
Counting I/O Points
To calculate the total number of I/O points: Identify all objects to be controlled by each controller Count all Boolean connected variables Count all non-Boolean connected variables For each Boolean variable, add one (1) I/O point to the I/O count For each non-Boolean variable, add two I/O points to the I/O count Add 20% to the I/O point count, to create a margin for growth
I/O Point Expansion Licenses
If the I/O point count exceeds the supported level, an expansion license can be used to move to a higher I/O point level. If the I/O point count increases notably, several expansion licenses might be required. See ControlIT for AC 800M/C price lists.
104
3BSE 026 333 R101 Rev A
Appendix A Licenses
Examples of Control Software Licenses
Examples of Control Software Licenses

Examples of combinations of Base licenses and I/O point support: Binary Control license, with support for up to 64 I/O points Basic Control license, with support for up 1200 I/O points Advanced Process Control, with support for more than 1600 I/O points
OPC Server for AC 800M/C Licenses

The OPC Server for AC 800M/C license includes support for OPC Data Access 2.05, as well as OPC Alarms and Events 1.02. This license is not required if an AC 800M/C Connect license is purchased, since an OPC server license is included in the Connect license.
AC 800M/C Connect Licenses

AC 800M/C Connect License Concept
An AC 800M/C Connect license consists of a base license, with support for a number of tags (see below). The base license for the first AC 800M/C Connect workplace should support the number of tags used in the integrated configuration. Tag support can be selected in stages up to a maximum number. The OPC Server for AC 800M/C license is included free of charge. Additional Connect licenses must be purchased for each additional workplace. These licenses, with reference to the base license, are also based on the number of tags used in that particular workplace. Expansion licenses can be used to expand the number of tags supported by an AC 800M/C Connect license.
The number of tags is calculated in the integrated system, and is a measure of the size and complexity of the system. For a description of how to calculate tags, see AC 800M/C Connect Tags on page 106.
3BSE 026 333 R101 Rev A
105
AC 800M/C Connect Tags
Appendix A Licenses
AC 800M/C Connect Tags

An AC 800M/C Connect tag is equivalent to an instance of a function block or control module type that is set to be an aspect object. Only instances of types set to be aspect objects are mirrored to or from Process Portal A. All such mirrored instances are counted, the result being the number of tags for the AC 800M/C Connect license. All instances of aspect objects are treated equally, regardless of whether their types reside in a standard library or in a custom-made library or application. Programs are always mirrored, but are not counted as tags. However, any instance of an aspect object within them is counted as a tag. Hardware instances are always mirrored, but are not counted as tags.
Using deep structures in an application may produce more tags than the use of flat structures. However, deep structures are normally the result of objectoriented programming, which typically requires fewer engineering and testing hours than traditional programming methods. Do not jeopardize the benefits of object-oriented programming just to lower the number of tags.
106
3BSE 026 333 R101 Rev A
Appendix A Licenses
Tag Counting Example
Tag Counting Example

In the example, all instances of the ConveyorProcessLib:Conveyor control module type Figure 16 are set to be aspect objects. One conveyor will then be equivalent to eight tags, and all eight conveyors will then generate 64 tags.
Eight tags
Figure 16. Eight conveyors with eight tags each generate 64 tags
3BSE 026 333 R101 Rev A
107
Example of Simple AC 800M/C System Configuration
Appendix A Licenses
Example of Simple AC 800M/C System Configuration

The following licenses are required to build, download and run applications for a simple AC 800M/C controller system configuration (Figure 17). 1. 2. 3. A Control Builder M license A Control Software license based on the I/O point count An OPC Server for AC 800M/C license for connection to 3rd party OPC clients
3rd party OPC clients
OPC Server for AC 800M/C (3)
Control Builder M (1)
Controller
Control Software license (2)
fieldbuses remote I/O points
local I/O points
Figure 17. Simple AC 800M/C system configuration
108
3BSE 026 333 R101 Rev A
Appendix A Licenses
Example of Integrated AC 800M/C System Configuration

This example configuration shows AC 800M/C Connect being used to integrate Control Builder M with the Process Portal A environment via Aspect Integration Platform, AIP (Figure 18). The following licenses are required for the example configuration. Two Control Builder M Professional licenses (1) Three Control Software licenses, one for each controller A, B, and C, based on libraries used and the I/O point count of each controller (2) An AC 800M/C Connect license (this license includes an OPC Server for AC 800M/C) for the Process Portal A server (3) Two AC 800M/C Connect licenses, one for each additional Process Portal A client that is part of the integrated AC 800M/C configuration (4) Process Portal A licenses (5) are also required. These are described in the Process Portal A product guide (see Related Product Guides on page 18)
* Control Builder M Professional is required if using mirroring to a Process Portal A client. Process Portal A (5) Client 1 AC 800M/C Connect (4) Control Builder M Professional* (1) Process Portal A (5) Client 2 AC 800M/C Connect (4)
Process Portal A (5) Server AC 800M/C Connect (3) OPC Server for AC 800M/C included Control Builder M Professional (1)
Controller A fieldbuses remote I/O points
Controller B local I/O points
Controller C
Control Software licenses (2)
local I/O points
3rd party system
local I/O points
Figure 18. Example of an integrated AC 800M/C system configuration
3BSE 026 333 R101 Rev A
109
Appendix A Licenses
110
3BSE 026 333 R101 Rev A
Appendix B Supported Hardware and I/O Systems

Controllers
AC 800M
The following AC 800M modules are supported.
Unit PM856 PM860 PM861 CI851 CI852 CI853 CI854 CI855 CI856 CI857 Description CPU CPU CPU Communication Interface PROFIBUS-DP/V0 Communication Interface Foundation Fieldbus H1 Communication Interface RS-232C Communication Interface PROFIBUS-DP/V1 Communication Interface MasterBus 300 Communication Interface S100 I/O Communication Interface INSUM
PM856 PM856 is a high-performance, 32-bit, Single Board Computer, which directly connects to the S800 I/O system via Modulebus.
3BSE 026 333 R101 Rev A
111
AC 800M
PM860 PM860 is a high-performance, 32-bit, Single Board Computer, which directly connects to the S800 I/O system via Modulebus. PM860 is twice as fast as PM856 in executing an application program. PM861 (Redundant and Singular) PM861 is a high-performance, 32-bit, Single Board Computer, which directly connects to the S800 I/O system via Modulebus. PM861 has one optional Redundancy Control Link for redundant configuration.
Communication Interface Modules
CI851 The CI851 unit is the communication interface for PROFIBUS-DP/V0 for the AC 800M. It is a master unit and you can connect up to 125 slaves to it. However, you cannot connect more than 32 units in one segment. CI852 CI852 is the communication interface for the Fieldbus Foundation H1 bus for the AC 800M. The unit acts as a Link Active Scheduler (LAS) on the H1 bus. CI853 CI853 is the RS-232C serial communication interface unit for the AC 800M. Two possible settings of the serial ports on the CI853 unit are not valid and must not be used. These are: 1) 7 data bits, no parity, 1 stop bit 2) 8 data bits, parity, 2 stop bits
CI854 The CI854 unit is the communication interface for PROFIBUS DP for the AC 800M with redundant PROFIBUS lines and DP/V1 communication. It is a master unit and you can connect up to 125 slaves to the master. However, you cannot connect more than 32 units in one segement.
112
3BSE 026 333 R101 Rev A
AC 800C
CI855 The CI855 unit is the communication interface for MasterBus 300 for the AC 800M. CI855 houses two Ethernet ports to support MasterBus 300 Network redundancy. CI856 The CI856 is a communication interface for the S100 I/O system for the AC 800M. Up to five S100 I/O racks can be connected to one CI856 where each I/O rack can hold up to 20 I/O boards. CI857 The CI857 unit is the communication interface for INSUM for the AC 800M.
AC 800C
The following AC 800C modules are supported.
Unit PM210 CI271 CI272 CI274 Description CPU Communication Interface RS-232C Communication Interface Ethernet Communication Interface PROFIBUS-DP/V0
PM210 The PM210 is a high-performance, 32-bit, Single Board Computer with digital inputs and outputs directly on-board. The controller is connected to the S200L I/O system. It is also possible to connect different communication and fieldbus boards using two inbuilt expansion slots.
3BSE 026 333 R101 Rev A
113
Advant Controller 250
CI271 The CI271 unit is the RS-232C serial communication interface unit for AC 800C. CI272 The CI272 unit is the Ethernet communication interface unit for AC 800C. CI274 The CI274 unit is the PROFIBUS-DP communication interface unit for the AC 800C. It is a master unit and you can connect up to 125 slaves to it. However, you cannot connect more than 32 units in one segment.

The following Advant Controller 250 modules are supported.
Unit PM253 PM254 PM255 200-PSMG 200-PSSG 200-CICN 200-CIPB/DP 200-CISB 200-CIE 200-CI232 200-CI485 200-DU Description CPU CPU CPU Master power supply Slave power supply Communication Interface ControlNet Communication Interface PROFIBUS-DP/V0 Communication Interface SattBus Communication Interface Ethernet Communication Interface RS-232C Communication Interface RS-485 Blank unit for protection of the bus
114
3BSE 026 333 R101 Rev A
PM253 PM253 is a high-performance, 32-bit, Single Board Computer available in different configurations. It is a CPU with 2 Mbyte memory. The unit has two serial (COM) ports and one SattBus interface. PM254 PM254 a high-performance, 32-bit, Single Board Computer available in different configurations. It is a CPU with 8 Mbyte memory. The unit has two serial (COM) ports and one SattBus interface. PM255 PM255 is a high-performance, 32-bit, Single Board Computer available in different configurations. It has a floating point processor (FPU). It is a CPU with 8 Mbyte memory. The unit has one serial (COM) port.
Power Supplies
200-PSMG 200-PSMG is the master power supply unit for the Advant Controller 250 system. Only one 200-PSMG can be used in a system. For higher capacity, one or more 200-PSSGs can be added. 200-PSSG 200-PSSG is a complementary power supply to 200-PSMG when an additional power supply is needed in a system.
200-CICN 200-CICN is a communication interface unit for remote I/O for ControlNet I/O. 200-CIPB/DP The 200-CIPB/DP is the PROFIBUS-DP/V0 communication interface unit for the Advant Controller 250. It is a master unit and you can connect up to 125 slaves to the master. However, you cannot connect more than 32 units in one segment.
3BSE 026 333 R101 Rev A
115
200-CISB 200-CISB is a SattBus communication interface unit with two SattBus supervisor channels, which may be configured individually. 200-CIE 200-CIE is the Ethernet communication interface unit. 200-CI232 200-CI232 is a communication interface unit with two RS-232C asynchronous serial channels, which may be configured individually. 200-CI485 200-CI485 is a communication interface unit with two RS-485 asynchronous serial channels (with galvanic isolation), which may be configured individually. 200-DU 200-DU is a blank unit used to protect an empty slot in the backplane from external mechanical and electrical damage. Earlier versions of 200-DU were called 200-DMOD.
116
3BSE 026 333 R101 Rev A
Adapters
Adapters
Adapter TB820 Can be connected to HART
(1)
SOE Yes(1) Yes(1) Yes(1) Yes Yes Yes Yes Yes Yes No No No No No No No No No No No No No No No No No No
PM856 Yes PM860 Yes(1) PM861 (single CPU only) Yes(1) PM856 PM860 PM861 CI856 CI856 CI856 CI274 CI851 CI854 200-CIPB/DP CI854 CI851 CI854 200-CIPB/DP CI274 200-CICN 200-CICN PM253 PM254 PM255 CI274 CI851 200-CIPB/DP PM210 Yes Yes Yes No No No No No No No Yes No Yes No No No No No No No No No No No
TB840
DSBC 173A DSBC 174 DSBC1 76 CI830
CI840 CI920
200-RACN 200-ACN 200-ANN
200-APB12
200-AIO
(1) HART and SOE are also available for modules placed on the electrical modulebus (12 slots) for PM856, PM860, and PM861 (single CPU only).
3BSE 026 333 R101 Rev A
117
Adapters
TB820 Modulebus Modem TB840 Modulebus Modem, primarily for redundant modulebus. DSBC 173A The DSBC 173A unit is the bus extender slave inserted in the last position of a S100 I/O rack. DSBC 174 The DSBC 174 unit is the bus extender slave inserted in the last position of a S100 I/O rack. DSBC 176 The DSBC 176 unit is the bus extender slave inserted in the last position of a S100 I/O rack. CI830 The unit CI830 is a remote PROFIBUS-DP I/O adapter for units. CI830 is connected to a controller via a PROFIBUS-DP master unit on the controller system bus. The CI830 can handle up to 24 S800 I/O-units. 12 I/O-units can be directly connected to the ModuleBus on the CI830, while the remaining I/O-units have to be connected via I/O-clusters. Up to 7 I/O-clusters can be connected to one CI830, and the numbering of I/O-units connected to a cluster will start with 101 for cluster 1, 201 for cluster 2 and so on. CI840 The CI840 is a remote PROFIBUS-DP/V1 adapter for S800 I/O units. The CI840 can handle up to 24 S800 I/O-units. 12 I/O-units can be directly connected to the ModuleBus on the CI840, while the remaining I/O-units have to be connected via I/O-clusters. Up to 7 I/O-clusters can be connected to one CI840, and the numbering of I/O-units connected to a cluster will start with 101 for cluster 1, 201 for cluster 2 and so on.
118
3BSE 026 333 R101 Rev A
Adapters
CI920 The CI920 is a communication interface which connects the S900 Station to the external fieldbus. The data received via the fieldbus are distributed accordingly to the respective I/O modules. The parameters are submitted to a plausibility check. The incoming data are buffered and are available even in case of a fieldbus failure. When an I/O module needs to be replaced, the new module can be parameterized immediately. 200-RACN An Advant Controller 250 configured with a ControlNet communication interface (200-CICN) may connect to a remote rack-based I/O system. The 200-RACN unit is a remote ControlNet I/O adapter for rack based I/O units. 200-RACN is connected to the controller via a 200-CICN unit on the controller system bus. In the Project Explorer, below the 200-CICN unit, one or several adapter 200-RACN units are used as nodes on the ControlNet fieldbus. A 200RACN unit can have up to sixteen I/O boards. Limitations On each ControlNet fieldbus, maximun eight (8) I/O-racks are supported, if 200-CICN Firmware version = 1.3 Expansion I/O-racks are not supported, i.e. it is necessary to install a 200RACN board in every I/O-rack Expansion racks, with board adresses starting with 20, 60, etc., are not supported
200-ACN The 200-ACN unit is a remote ControlNet I/O adapter for I/O units. 200-ACN is connected to the controller via a 200-CICN unit on the controller system bus. In the Project Explorer, below the 200-CICN unit, one or several adapter 200ACN units are used as nodes on the ControlNet fieldbus. A 200-ACN unit can have up to eight I/O units. 200-ANN The 200-ANN unit is a central I/O adapter for I/O units. One or several 200ANN units can be connected to the Advant Controller 250 system bus. Up to eight I/O units can be connected to each 200-ANN unit. 200-APB12 The 200-APB12 unit is a remote PROFIBUS-DP I/O adapter for I/O units. 200-APB12 is connected to the controller via a PROFIBUS DP master unit on the controller system bus. A 200-APB12 unit can have up to eight I/O units.
3BSE 026 333 R101 Rev A
119
I/O Families
PM210, 200-AIO In the Project Explorer, for an AC 800C, the two Ext I/O adapters can have up to eight I/O units. On the AC800C CPU unit the Ext I/O adapters are built-in. Locate the I/O units to the right of the first Ext I/O in position 11. For the second Ext I/O, in position 12, you must have a 200-AIO cable connector with a housing to which the I/O units are located on another rail.
I/O Families
I/O Family S100 I/O S200 I/O Connects To CI856 PM210 200-AIO 200-ANN 200-ACN 200-APB12 PM210 200-AIO 200-ANN 200-ACN 200-APB12 PM856, PM860, PM861 TB820, TB840 CI830, CI840 CI920 200-RACN PM856, PM860, PM861 TB820, TB840 CI830 PM856, PM860, PM861 TB820, TB840
S200L I/O
S800 I/O
S900 I/O Rack I/O ABB Standard Drives
ABB Engineered Drives
120
3BSE 026 333 R101 Rev A
S100 I/O
S100 I/O
The following selection of S100 I/O modules are supported.
Name DSAI 130 DSAI 130A DSAI 130D DSAI 133 DSAI 133A DSAI 146 DSAI 155 DSAI 155A DSDI 110 DSDI 110A DSDI110AV1 DSDI 120 DSDI 120A DSDI 120AV1 DSDO 110 DSDO 115 DSDO 115A DSAO 110 DSAO 120 DSAO 120A DSAO 130 DSAO 130A DSAX 110 DSAX 110A DSDP 010 Description Analog input board, 16 channels Analog input board, 16 channels with 4 sets of filter times Analog input board, 32 channels Analog input board, 31 channels for Pt100 elements Analog input board, 16 channels for thermocouples Digital input board, 14 channels, 24V
Digital input board, 32 channels, 48 V
Digital output board, 32 channels Digital output board, 32 channels Digital output board, 32 channels, OSP control Analog output board, 4 channels Analog output board, 8 channels Analog output board, 8 channels, OSP control Analog output board, 16 channels Analog output board, 16 channels, OSP control Analog input/output board, 8+8 channels Absolute binary decoder with hardware strobe, 2 channels
3BSE 026 333 R101 Rev A
121
S200 I/O
Name DSDP 140B DSDP 161 DSDP 170
Description Positioning controller board Loop transducer interface, 4 channels Pulse counter board, 4 channels
S200 I/O
Name 200-DUTB 200-IA8 200-IB10xOB6 200-IB16 200-IB16xOB16P 200-IB32 200-IE4xOE2 200-IE8 200-IF4I 200-IM8 200-IP2 200-IP4 200-IR8 200-IR8R 200-IT8 200-OA8 200-OB16 200-OB16P Description Dummy I/O unit Digital input unit, 8 inputs Digital combined unit, 10 inputs and 6 outputs Digital input unit, 16 inputs Digitally combined unit, 16 inputs and 16 outputs Digital input unit, 32 inputs Analog combined unit, 4 inputs and 2 outputs Analog input unit, 8 inputs Analog input unit, 4 inputs Digital input unit, 8 inputs Pulse counter board, 2 x 4 inputs Pulse counter board, 4 x 2 inputs Analog input unit, 8 inputs Analog input unit, 8 inputs Analog input unit, 8 inputs Digital output unit, 8 outputs Digital output unit, 16 outputs Digital output unit, 16 outputs
122
3BSE 026 333 R101 Rev A
200L I/O
Name 200-OB32P 200-OB8EP 200-OE4 200-OF4I 200-OM8 200-OW8
Description Digital output unit, 2 x 16 outputs Digital output unit, 8 outputs Analog output unit, 4 outputs Analog output unit, 4 outputs Digital output unit, 8 outputs Digital output unit, 8 outputs
200L I/O
Name AI210 AO210 AX210 DI210 DO210 DX210 Description Analog input unit, 8 inputs Analog output unit, 4 outputs Analog combined unit, 4 inputs and 2 outputs Digital input unit, 16 inputs Digital output unit, 16 outputs Digital combined unit, 10 inputs and 6 outputs
See also, S200C I/O on page 127.
S800 I/O
Name AI801 AI810 AI820 Description Analog input unit, 8 inputs Analog input unit, 8 inputs Differential analog input unit, 4 inputs
3BSE 026 333 R101 Rev A
123
S800 I/O
Name AI830 AI835 AI890 AI895 AO801 AO810 AO820 AO890 AO895 DI801 DI802 DI803 DI810 DI811 DI814 DI820 DI821 DI830 DI831 DI885 DI890 DO801 DO802 DO810
Description Analog input unit, 8 inputs Analog input unit, 8 inputs Analog input unit, 8 inputs Analog input unit, 8 inputs(1) Analog output unit, 8 outputs Analog output unit, 8 outputs Analog output unit, 4 outputs Analog output unit, 8 outputs Analog output unit, 8 outputs(1) Digital input unit, 16 inputs Digital input unit, 8 inputs Digital input unit, 8 inputs Digital input unit, 16 inputs Digital input unit, 16 inputs Digital input unit, 16 inputs Digital input unit, 8 inputs Digital input unit, 8 inputs Digital input unit, 16 inputs(1, 2) Digital input unit, 16 inputs(1, 2) Digital input unit, 8 inputs(1, 2) Digital input unit, 8 inputs Digital output unit, 16 outputs Digital output unit, 8 outputs Digital output unit, 16 outputs
124
3BSE 026 333 R101 Rev A
S900 I/O
Name DO814 DO815 DO820 DO821 DO890 DP820

(1) Not in CI830 (2) Not in CI840
Description Digital output unit, 16 outputs Digital output unit, 8 outputs Digital output unit, 8 outputs Digital output unit, 8 outputs Digital output unit, 8 outputs Digital pulse counter(2)
S900 I/O
Name AI910N/S AI920N/S AI921N/S AI930N/S AI931N/S AI950N/S AO910N/S AO920N/S AO930N/S DO910N/S DP910N/S DX910N/S Description Analog input unit, 4 inputs Analog input unit, 4 inputs Analog input unit, 4 inputs Analog input unit, 4 inputs Analog input unit, 4 inputs Analog input unit, 4 inputs Analog output unit, 4 outputs Analog output unit, 4 outputs Analog output unit, 4 outputs Digital output unit, 4 outputs Frequency input and pulse counter Bidirectional unit, 8 channels
3BSE 026 333 R101 Rev A
125
ABB Standard Drives
ABB Standard Drives

Name ACS400 ACS600 ACS600 ACS600 ACS800 ACS800 ACS800 DCS400 DCS500 Application Standard drive Crane application Pump and fan application Standard application Crane application Pump and fan application Standard application Standard drive Standard drive
ABB Engineered Drives

Name ACS600 ACS600 ACS600AD ACS600C ACS600SD ACS800 ACS800 ACS1000 DCS600 Application IGBT supply (ISU) application System application Asynchronous drive Cyclo converter drive Synchronous drive IGBT supply (ISU) application System application Standard drive System application
126
3BSE 026 333 R101 Rev A
I/O for Updating
I/O for Updating

S200C I/O Name Description
200C-IB10xOB6P Digital combined unit, 10 inputs and 6 outputs 200C-IB16 200C-IE4xOE2 200C-IE8 200C-OB16P 200C-OE4 Rack I/O Digital input unit, 16 inputs Analog combined unit, 4 inputs and 2 outputs Analog input unit, 8 inputs Digital output unit, 16 outputs Analog output unit, 4 outputs
The boards are only supported for Advant Controller 250 on ControlNet.
Name RAID16 RAID32 RAOD16 RAOD32 RAIA8 RAOA2 RAOA4 RAOAH4 RAIPA4 Description Used for IAPG, IDLD (16-bit digital input) Used for IDP, IDPG, IDN, IDI, PTC, IPA4 (32-bit digital input) Used for ORG, ORGH, OATG, ODP2, ODPG2, ORM (16-bit digital output) Used for ODP.5, ODP.8, ODPG.8, ODPL.5, ODPLD, ODN.2, ODLD.5, ODSG (32-bit digital output) Used for IBA, IRA, ICA, IVA, IVAPOT (8 channel analog input) Used for OCVA (2 channel analog output) Used for OCAHG, ACAH (4 channel analog output) Used for OCAH with hand-station ( 4 channel output / manual) Used for IPA4 (32-bit digital input (counter))
3BSE 026 333 R101 Rev A
127
I/O for Updating
128
3BSE 026 333 R101 Rev A
Appendix C Library Objects Overview

This appendix gives an overview of all library objects, such as data types, functions, function block types and control module types that can be used in applications created using the Control Builder engineering tool. Refer to manuals and Control Builder online help describing the libraries in detail for further information.. Some tables have a display column headed ED and/or OD indicating that the function includes a faceplate with associated display elements. ED denotes Engineer Display (Control Builder M) and OD denotes Operator Display (HSI). All Library function types are protected, apart from a few. This means that the types cannot be copied to your own library and then modified. You can check whether the library function is protected by selecting the function in the Project Explorer and then trying to copy it. A dimmed function means it is protected.
3BSE 026 333 R101 Rev A
129
System Library
System Library
This System Library (SystemLib) is the basic library for the Control Builder M. It contains IEC 61131-3 data types, functions and function block types, together with data types, functions and function block types with extended functionality, designed by ABB. About 130 functions are contained in this library.
130
3BSE 026 333 R101 Rev A
Data Types in SystemLib

IEC 61131-3 Standard Data Types
Table 36. IEC 61131-3 Standard data types.

Data type Bool Date_and_time Dint Dword Int Real String Time Uint Word Boolean Date and time of day (Year, Month, Day, Hour, Minute, Second, Millisecond) Signed double integer (32 bits). Range 2,147,483,648 to 2,147,483, 647 Double word (32-bit) bit string. Signed integer (16-bit). Range 32,768 to 32,767 Floating point values in the range +/ 10+/38 String data type for character strings. Maximum string length 140 characters Duration (Day, Hour, Minute, Second, Millisecond) Unsigned integer (16-bit) with the range 065535 Word (16-bit) bit string Description
I/O-Related Data Types
Table 37. I/O Related data types.

Data type BoolIO Description Represents a discrete I/O point (input or output). This structure contains: Value (Bool) Value in the application IOValue (Bool) Value from I/O before forcing Forced (Bool) True if the input or output is forced
3BSE 026 333 R101 Rev A
131
Table 37. I/O Related data types. (Continued)

RealIO Represents an analog I/O point (input or output). This structure contains: Value (real) Value used by the application IOValue (real) Value of the I/O channel.Forced (Bool) True if the channel is forced Status (dint) Status of the channel Parameters (SignalPar) I/O settings and scaling DintIO Represents an integer I/O point (input or output). This structure contains: Value (dint) Value in the application IOValue (dint) Value from I/O before forcing Forced (bool) True if the input or output is forced DwordIO Represents a bitstring I/O point (input or output). This structure contains: Value (dword) Value in the application IOValue (dword) Value from I/O before forcing Forced (bool) True if the input or output is forced SignalPar The SignalPar data type is used for Max, Min, Inverted, Fraction and Unit values of analog signals. The structure contains: Max (real): Max value Min (real): Min value Inverted (bool): Indicates if input is inverted Fraction (dint): Signal fraction Unit (string): Engineering Unit of the signal
132
3BSE 026 333 R101 Rev A
Control-Related Data Types
The data type ControlConnection is abbreviated CC in some contexts. Table 38. Control-related data types.
Data type ControlConnection Level6Connection Description Represents the data flow between control modules for continuous control applications. Used for intermediate communication of level detection within the control libraries.
Other Data Types
There are a number of data types which are used by specific functions, e.g.: HWStatus RandomGenerator Timer, CalendarStruct SetDTPar, TimeZoneInfo ArrayObject, QueueObject Boolean8, 16, 32 Comm_Channel Range ControlConnection ControlConnectionBackward ControlConnectionForward
3BSE 026 333 R101 Rev A
133
Functions in SystemLib
IEC 61131-3 Standard Functions
Table 39. IEC 61131-3 standard functions.

Function type Description Type conversion functions *_TO_** Type conversion from * to ** The following type conversions are implicit (i.e. a call to a type conversion function is not needed): BOOL -> WORD, BOOL -> DWORD, WORD -> DWORD INT -> DINT, INT -> REAL UINT -> DINT, UINT -> REAL DINT -> REAL Explicit conversion functions: <BOOL, INT, DINT, UINT, TIME, STRING>_TO_REAL <BOOL, INT, DINT, UINT, WORD, DWORD, REAL, TIME, DATE_AND_TIME>_TO_STRING <DINT, REAL, STRING>_TO_TIME <STRING>_TO_DATE_AND_TIME <INT, DINT, UINT, WORD, DWORD, REAL, STRING>_TO_BOOL <BOOL, UINT, DINT, WORD, DWORD, REAL, STRING>_TO_INT <BOOL, INT, UINT, WORD, DWORD, REAL, TIME, STRING>_TO_DINT <BOOL, INT, DINT, WORD, DWORD, REAL, STRING>_TO_UINT <BOOL, INT, DINT, UINT, DWORD, STRING>_TO_WORD <BOOL, INT, DINT, UINT, WORD, STRING>_TO_DWORD
134
3BSE 026 333 R101 Rev A
Table 39. IEC 61131-3 standard functions. (Continued)

Function type Description General functions ABS SQRT Absolute value Square root Logarithmic functions LN LOG EXP Natural logarithm Logarithm to base 10 Natural exponential Trigonometric functions SIN COS TAN ASIN ACOS ATAN Sine of input in radians Cosine in radians Tangent in radians Principal arc sine Principal arc cosine Principal arc tangent Extensible arithmetic functions ADD MUL Addition (OUT:= IN1 + IN2 + + Inn) Multiplication (OUT:= IN1 * IN2 * * INn) Non-extensible arithmetic functions SUB DIV MOD EXPT MOVE Subtraction (OUT := IN1 IN12) Division (OUT := IN1 / IN2) Modulus (OUT := IN1 modulo IN2) Exponentiation (OUT := IN1 raised to IN2) Move (OUT := IN)
3BSE 026 333 R101 Rev A
135

Function type Description Standard bit shift functions SHL SHR ROR ROL Shift bits left (OUT := IN left-shifted by N bits, zero-filled on right) Shift bits right (OUT := IN right-shifted by N bits, zero-filled on left) Rotate bits right (OUT := IN right-rotated by N bits, circular) Rotate bits left (OUT := IN left-rotated by N bits, circular) Standard bitwise Boolean functions AND OR XOR NOT Boolean AND (OUT := IN1 & IN2 & & INn) Boolean OR (OUT := IN1 OR IN2 OR OR INn) Boolean Exclusive OR (OUT := IN1 XOR IN2 XOR XOR INn) Boolean negation (OUT := NOT IN1) Standard selection function SEL MIN MAX LIMIT MUX Binary selection (non extensible) Select the smallest of the input variables (extensible) Select the largest of the input variables (extensible) Delimiter between a minimum, min, variable value and a maximum, max, variable value. (non extensible) Multiplexer which selects the variable pointed out by the input variable (extensible) Standard comparison functions GT (>) GE (>=) EQ (=) Decreasing sequence Monotonic decreasing sequence Equality
136
3BSE 026 333 R101 Rev A

Function type LE (<=) LT (<) NE (<>) Description Monotonic increasing sequence Increasing sequence Inequality (non-extensible) Standard character string functions LEN LEFT RIGHT MID CONCAT INSERT DELETE REPLACE FIND String length function Left-most L characters of IN Right-most L characters of IN L characters of IN beginning at the Pth character position Extensible concatenation Insert IN2 into IN1 after the Pth character position Delete L characters of IN, beginning at the Pth character position Replace L characters of IN1 by IN2, starting at the Pth character position Find the character position of the beginning of the first occurrence of IN2 in IN1. If no occurrence of IN2 is found, then OUT := 0. Functions of time data types ADD SUB Add time variables Subtract time variables
3BSE 026 333 R101 Rev A
137
Non-IEC 61131-3 Conversion Functions
Table 40. Non IEC 61131-3 conversion functions.

Function type Description Type conversion functions ASCIIStructToString The ASCIIStructToString function takes a struct of dints, which contains the codes for an ASCII string, and reconstructs the string from the values in the components of the struct. The component values of the integer, DintStruct are read and translated to the value of the destination string, String. BCDToDint converts a BCD value BCD into a dint type integer. Bool16ToDint converts a Boolean struct BoolStruct with 16 items into a dint. Bool32ToDint converts a Boolean struct BoolStruct with 32 items into a dint. This function converts a CalendarStruct to a date_and_time value. This function converts a date_and_time value to a CalendarStruct. DintToBCD converts an integer value into a BCD value. The DIntToBool16 and DIntToBool32 functions convert a dint into a Boolean struct BoolStruct with 16 or 32 items, respectively. This function converts a dint value to a Graycoded value. This function converts a Graycoded value to a dint value. The MaxStringLength function returns the maximum length of a string, i.e. the allocated size of the string variable, as an integer value. This function converts a string to an ASCIIStruct.
BCDToDint Bool16ToDint Bool32ToDint CalendarStructTo Date_and_Time Date_and_TimeTo CalendarStruct DintToBCD DIntToBool16 and DIntToBool32 DintToGraycode GraycodeToDint MaxStringLength
StringToASCIIStruct
138
3BSE 026 333 R101 Rev A
Other Functions
Table 41. Other functions.

Function type CheckSum ExecuteControl Modules Description The CheckSum function calculates checksums used for ASCII protocols written in the programming language. This function is used in function blocks that contain control modules. When the function is called from the function block, all control modules in that function block are executed. Returns the quality of the system time. It may be GOOD, UNCERTAIN or BAD. This procedure reads (copies) values from a struct component. Returns the system time when current task was started. Returns the system time for the specified local time. The Match function returns the position of a string within another string. Unlike the Find function a wildcard pattern can be used. The Modp function returns the remainder after a number is divided by a divisor. The Modp function corresponds to the ST "mod" operator. The Modp function works differently for negative values (compatible with SattLine version 2.2 or earlier). NationalLowerCase NationalUpperCase PutStructComponent RandomNorm The NationalLowerCase function sets uppercase letters to lowercase letters. The NationalUpperCase function sets lowercase letters to uppercase letters. This procedure writes (copies) values into a struct component. The RandomNorm function returns a normally distributed random number.
GetDTQuality GetStructComponent GetSystemDT LocalDTToSystemDT Match
Modp
3BSE 026 333 R101 Rev A
139
Table 41. Other functions. (Continued)

RandomRect RandomSeed The RandomRect function returns a random number uniformly distributed between 0.0 and 1.0. The RandomSeed function initializes the RandomGenerator to a random value.
ReadStatusZeroDivInt The ReadStatusZeroDivInt function checks for zero division exceptions for integer values. ReadStatusZeroDiv Real Round SetFalse SetSeed SetTrue SystemDTToLocalDT Timer TimerElapsed TimerElapsedMS TimerHold TimerReset TimerStart Trunc WriteVar The ReadStatusZeroDivReal function checks for zero division exceptions for real values. The Round function rounds a real value up to the nearest integer. The Boolean operator will be set to false. The SetSeed function initializes a random generator using a specific start value. The Boolean operator will be set to true. Returns the local time for the specified system time. The Timer function controls a timer. The TimerElapsed function returns the elapsed time of a timer as a time value. The TimerElapsedMS function returns the elapsed time of a timer in milliseconds as a dint value. The TimerHold function stops a timer. The TimerReset function stops and resets a timer. The TimerStart function starts a timer. The Trunc function truncates a real value to an integer. Enables a system to write to a variable in a controller, or transfer variables between controllers, without owning the variable.
140
3BSE 026 333 R101 Rev A
Array and Queue Functions
Table 42. Array and queue functions.

Function type Arrays CreateArray PutArray GetArray DeleteArray Creates an array Array of elements of the same type as ArrayElement. Puts the contents of ArrayElement into the data type at position Index in the array Array. Gets the contents of the data type at position Index in the array Array into ArrayElement. Deletes the array Array and deletes the whole tree structure of arrays. Queues CreateQueue PutFirstQueue GetFirstQueue PutLastQueue GetLastQueue ReadQueue ClearQueue CurrentQueueSize DeleteQueue Creates a queue Queue of elements of the same type as QueueElement. Puts the contents of QueueElement into the first element of the queue Queue. Puts the contents of the first element from the queue Queue into QueueElement. Puts the contents of QueueElement into the last record element of the queue Queue. Puts the contents of the last element from the queue Queue into QueueElement. Reads the contents of the specified element number from the queue Queue and puts it into QueueElement. This procedure clears the queue Queue. This integer function returns the current number of elements in the queue Queue. This procedure deletes the queue Queue. Description
3BSE 026 333 R101 Rev A
141
Task Control Functions
Table 43. Task control functions.

Function type FirstScanAfter ApplicationStart FirstScanAfter PowerUp GetPriority SetPriority GetIntervalTime Description The FirstScanAfterApplicationStart function checks if the current scan/execution is the first one performed by the current task. The FirstScanAfterPowerUp function checks if the controller has been warm started. Use the GetPriority function to obtain the priority of the current task Use the SetPriority function to set the priority of the current task. Use the GetIntervalTime function to get the requested interval time of the current task.
GetActualIntervalTime Use the GetActualIntervalTime function to get the actual interval time of the current task. SetIntervalTime Use the SetIntervalTime function to set the requested interval time of the current task.
142
3BSE 026 333 R101 Rev A
Function Block Types in SystemLib

IEC 61131-3 Function Block Types
Table 44. IEC 61131-3 function block types.

Function type Description Standard bistable function blocks SR RS Bistable function block (set dominant) Bistable function block (reset dominant) Standard edge detection function blocks R_TRIG F_TRIG Rising edge detector Falling edge detector Standard counter function blocks CTU CTD CTUD Up-counter Down-counter Up-down counter Standard timer function blocks TP TON TOF RTC SEMA Pulse timer On-delay timer Off-delay timer The RTC (Real-Time-Clock) function block performs display and date and time setting. Sema, the semaphore function block, is designed to allow competing tasks to share a particular resource.
3BSE 026 333 R101 Rev A
143
Process Object Function Block Types
Use the ACOF (Automatic Check Of Feedback) functions primarily for supervision of process objects. ACOF function blocks can monitor up to three output signals and up to three feedback signals. Use ACOF when a feedback signal is expected within a certain time after an output to the process object has been activated or deactivated. If the feedback signal is not detected, an alarm signal is given. Table 45. Process object function block types.
Function type ACOFAct ACOFAct Deact ACOFAct 3P ACOFAct Deact 3P Description Object control with two limit switches and automatic return. This object has one stable position. Object control with two limit switches. This object has two stable positions. Object control with three limit switches and automatic return. This object has one stable position. Object control with three limit switches. This object has three stable positions.
Other Function Block Types
Table 46. Other function block types.

Function block type GetDT Description GetDT retrieves the system time from the controller at which the current task was started. The function block converts the system time to local time so that both are available as parameters. GetTimeZoneInfo retrieves the currently used time-zone settings. Display
GetTimeZoneInfo
144
3BSE 026 333 R101 Rev A
Table 46. Other function block types. (Continued)

IntegerToRealIO IntegerToRealIO converts a raw integer value to a scaled RealIO value with a measuring range, units and decimals. It can be treated as a physical RealIO value in the application. A high-level detector is a trip for supervising an analog signal. A high-level trip indicates when the input signal exceeds the selected high detect level. The detector has hysteresis on the input signal, which prevents the level detector output signal from repeatedly changing state when the supervised input signal varies near the detect level. A lo- level detector is a trip for supervising an analog signal. A low level trip indicates when the input signal drops below the preset low-detect level. The detector has a hysteresis on the input signal, which prevents the level detector output signal from repeatedly changing state when the supervised input signal varies near the detect level. PowerFailureInfos provides information on power failure status, such as number and duration. In addition, the total number of power failures since the last reset and the duration of these can also be presented. PrintLines prints text lines on a printer. PulseGenerator is a pulse generator to create a continuous pulse signal. The RealIOToInteger function block converts a scaled RealIO value to a raw integer value.
LevelHigh
LevelLow
PowerFailureInfos
PrintLines PulseGenerator RealIOToInteger
3BSE 026 333 R101 Rev A
145

SetDT SetDT sets the system time on the controller. It ED is possible to set the time directly as system time or indirectly as local time and the function block will perform the conversion to system time. The time can be set as relative or as absolute time. This functionality is available through parameters and an interaction window. The interaction window also shows the current system time and local time. ED SetTimeZoneInfo sets the time-zone information. StandardDT and DaylightDT can be specified with the absolute or the day-in-month format. This functionality is available through parameters and an interaction window. This function overwrites the time-zone information downloaded by the ACB. SystemDiagnostics SystemDiagnostics can be used to measure and display the following: Stop time and memory usage during a controller download. Current memory in use Maximum memory used since the last cold start Fragmentation of the memory. TimePulses The pulse generator creates a pulse on the outputs every new hour on the Hour output and every new day on the Day output, synchronized to the real-time clock TimerOffHold is an Off-delay timer function block with a hold input function. TimerOnHold is an On-delay timer, with a hold input function. TimerPulseHold is a pulse timer with a hold function. ED
SetTimeZoneInfo
TimerOffHold TimerOnHold TimerPulseHold(1)
146
3BSE 026 333 R101 Rev A

TimerPulseHoldDel TimerPulseHoldDel is a the pulse timer with a hold input function and a delayed start to generate Q output pulses. Trigger provides a combined time and event trigger functionality. Threshold is used to determine when more than, or equal to, a given number of Boolean values are true. TimerD measures the elapsed time in negative direction and gives indication when a specified level is past. TimerU measures the elapsed time in positive direction and gives indication when a specified level is past. SinGen is used to generate a sinus signal. The frequency and amplitude are controlled by inputs. SqGen is used to generate a square wave with an optional number of amplitudes. Each amplitude is determined by an input and for each amplitude a time during which it is to be maintained is specified. BcToDint converts data from an optional number of binary coded bool inputs and a sign input into a dint. DintToBc converts data from dint to an optional number of bool outputs, using binary coded conversion, and a sign output. FirstOfNToDint converts data from 1-of-N format with an optional number of bool inputs and a sign input into a dint.
Trigger Threshold
TimerD
TimerU
SinGen
SqGen
BcToDint
DintToBc
FirstOfNToDint
3BSE 026 333 R101 Rev A
147

DintToFirstOfN DintToFirstOfN converts data from dint to an optional number of bool outputs using 1-of-N conversion, and a sign output. BcdToDint converts data from an optional number of bool inputs (in groups of four coded as BCD) and a sign input into a dint. DintToBcd converts from dint to an optional number of bool (in groups of four coded as BCD) and a sign output. GrayToDint converts data from gray code with an optional number of bool inputs and a sign input into a dint. LevelHigh is used to compare a real value with an optional number of high limits with the possibility to specify hysteresis. LevelLow is used to compare a real value with an optional number of low limits with the possibility to specify hysteresis. Max is used to select the largest value of an optional number of inputs. The Max function block exists for real and dint: MaxReal and MaxDint. Min is used to select the lowest value of an optional number of inputs. The function block exists for real and dint: MinReal and MinDint. Median is used to calculate the median value of an optional number of input values. The function block supports real and dint: MedianReal and MedianDint. RSD is used as a memory for bool variables. Besides the RS function, it can also override this function with a write function.
BcdToDint
DintToNBcd
GrayToDint
LevelHigh(1)
LevelLow(1)
Max
Min
Median
RSD
148
3BSE 026 333 R101 Rev A

DeMux Register DeMux can handle the data types real, dint and bool: DeMuxReal, DeMuxDint and DeMuxBool. Register is used as a memory function block with an optional number of positions. The function block exists for data types real, dint and bool: RegisterReal, RegisterDint and RegisterBool. Shift is used as a shift register of optional length. The function block exist for data types real, dint and bool: ShiftReal, ShiftDint and ShiftBool. ShiftL is used as a shift register of optional length. All positions can be written and read. The function block exist for data type real, dint and bool: ShiftLReal, ShiftLDint and ShiftLBool. Fifo is a queue register of First-In-First-Out type. FifoRW is a queue register of First-In-First-Out type. In addition, data can be changed and deleted at any queue place. The FifoRW can handle the data types real, dint and bool: FifoRWReal, FifoRWDint and FifoRWBool. Used to calculate the mean value of a number of real numbers.
Shift
ShiftL
Fifo FifoRW
MajorityReal
(1) Extended functionality in new versions
3BSE 026 333 R101 Rev A
149
Supervision Signals Library
Supervision Signals Library

This library (SignalLib) contains a number of function blocks for analog and digital inputs and outputs. They extend the functionality of I/O signals and application variables with alarm and event handling. The function blocks also provide filtering and error handling. In the faceplates it is possible to force the objects, view trim curves, configure and enable/disable alarms and events and view/modify parameters.
Function Block Types in SignalLib

Table 47. SignalLib function block types.
Function block type SignalInReal Description Display
OD, ED SignalInReal extends the functionality of an Analog Input signal of data type RealIO with alarm/event handling for three high levels, three low levels and error handling. OD, ED SignalOutReal extends the functionality of an Analog Output signal of data type RealIO with alarm/event handling for three high levels, three low levels and error handling. SignalReal is used to achieve alarm/event handling of an application variable of data type real with up to three high and three low levels. SignalInBool extends the functionality of a Digital Input signal of data type BoolIO with alarm/event handling when the input value is different than Normal value. In corresponding faceplates it is possible to force the object, view trim curves, configure and enable/disable alarms and events. OD, ED
SignalOutReal
SignalReal
SignalInBool
OD, ED
150
3BSE 026 333 R101 Rev A
Function Block Types in SignalLib
Table 47. SignalLib function block types. (Continued)

Function block type SignalOutBool Description SignalOutBool extends the functionality of a Digital Output signal of data type BoolIO with alarm/event handling when the input value is different than Normal value. In corresponding faceplates it is possible to force the object, view trim curves, configure and enable/disable alarms and events. SignalBool SignalBool extends the functionality of an application variable of data type Bool with alarm/event handling when the input value is different than Normal value. In corresponding faceplates it is possible to force the object, view trim curves, configure and enable/disable alarms and events. OD, ED Display OD, ED
3BSE 026 333 R101 Rev A
151
Basic Library for Process Objects
Basic Library for Process Objects

This library (ProcessObjBasicLib) contains basic core function block types for valve and motor control functions. They are to be used when designing your own function block types. The core function block types should be encapsulated in your own function block type. These core function block types are protected and cannot be changed.
Function Block Types in ProcessObjBasicLib

Table 48. ProcessObjBasicLib function block types.
Function block type UniCore Description Uni-directional object: Basic function block with one or two outputs and 0, 1 or 2 feedback signals. This function block can be used to represent e.g. a valve. Parameters are available for the connection of an external panel for manual operation of the object, and interlock and force signals for connection of different safety interlocking. It is also possible to connect an external fault signal. BiCore Bi-directional object: Basic function block with two or three outputs and 0, 2 or 3 feedback signals. This function block can be used to represent e.g. a two-speed motor or a forward-backward motor. Parameters are available for the connection of an external panel for manual operation of the object, and interlock and force signals for connection of different safety interlocking. It is also possible to connect an external fault signal. Display
152
3BSE 026 333 R101 Rev A
Function Block Types in ProcessObjBasicLib
Table 48. ProcessObjBasicLib function block types. (Continued)

Function block type UniHSI Description Uni-directional object: Basic function block for support of the HSI in OperateIT A graphical environment as faceplates and display elements. This function block is used in control modules or function blocks using the process object library function block UniCore when an operator display element is to be used. BiHSI Bi-directional object. Basic function block for support of the HSI in OperateIT A graphical environment as faceplates and display elements. This function block is used in control modules or function blocks using the process object library function block BiCore when an operator display element is to be used. DriveCore The function block can be used as a base for control of ABB Drive, ACS600 and ACS400 and their corresponding DC drives. The function block can easily be used together with other function blocks s to create more complex objects that handle functionality such as modes and HSI. This function block provides the user with the possibility to start and stop a drive with a chosen setpoint according to the local state matching in drive. Display
3BSE 026 333 R101 Rev A
153
Extended Library for Process Objects
Extended Library for Process Objects

This library contains 5 different types with 2 variants each. All types are based on the protected core functions available in the Basic Library for Process Objects (on page 152). Unprotected code is then added to the core. The 10 types in this library are not protected, which means that you can copy the type to your library, and then modify the unprotected code in the type and use instances of it, see Figure 19.
Function block or Control module Protected code Unprotected code Added function Unprotected function block or control module
Core function
Figure 19. The function blocks and the control modules in this library are unprotected, i.e., they can be used and modified in your own library. There are five different library types for unidirectional (Uni in the type name) and five for bidirectional (Bi in the type name) objects, such as valves and motors. They all have alarm handling and support graphics.
154
3BSE 026 333 R101 Rev A
Function Block Types in ProcessObjExtLib
Function Block Types in ProcessObjExtLib

Table 49. ProcessObjExtLib function block types.
Function block type Uni Description Uni-directional object with alarm and graphics: This function block is based on UniCore and is extended with alarm handling and a faceplate. Bi Bi-directional object with alarm and graphics: This function block is based on BiCore, and is extended with alarm handling and a faceplate. ValveUni Valve uni-directional with alarm and graphics: This function block is based on the UniCore, and is extended with alarm handling and a faceplate. Some parameters from UniCore are not used, and this block serves as a more basic example for a normal valve. MotorUni Motor uni-directional with alarm and graphics: This function block is based on UniCore, and is extended with alarm handling and a faceplate. This function block has additional interlocks, safety commands, and output delay timers. MotorBi Motor bi-directional with alarm and graphics: This function block is based on BiCore, and is extended with alarm handling and a faceplate. This function block has additional interlocks, safety commands, and output delay timers. ED, OD ED, OD ED, OD ED, OD Display ED, OD
3BSE 026 333 R101 Rev A
155
Control Module Types in ProcessObjExtLib
Control Module Types in ProcessObjExtLib

Table 50. ProcessObjExtLib control module types.
Control module type UniM Description Uni-directional object with alarm and graphics: This control module type is based on UniCore, and is extended with alarm handling and a faceplate. BiM Bi-directional object with alarm and graphics: This control module type is based on BiCore, and is extended with alarm handling and a faceplate. ValveUniM Valve uni-directional with alarm and graphics: This control module type is based on UniCore, and is extended with alarm handling and a faceplate. MotorUniM Motor uni-directional with alarm and graphics: This control module is based on UniCore, and is extended with alarm handling and a faceplate. This control module has additional interlocks, safety commands, and output delay timers. MotorBiM Motor bi-directional with alarm and graphics: This control module is based on BiCore, and is extended with alarm handling and a faceplate. This control module has additional interlocks, safety commands, and output delay timers. ED, OD ED, OD ED, OD ED, OD Display ED, OD
156
3BSE 026 333 R101 Rev A
Support Control Library
Support Control Library

This library (ControlSupportLib) contains invisible objects which cannot be used by you. The code of the objects is used by the objects in other Control libraries.
3BSE 026 333 R101 Rev A
157
Basic Control Library
Basic Control Library

This library (ControlBasicLib) contains predefined function block types. These are complete working modules that can be used as is. Hence, you should not use these modules to create new ones. The PID functions have Feedforward, Tracking, 3-position output and Autotuner control functions. Function blocks have been used to construct this library.
Data Types in ControlBasicLib

Table 51. Data types.
Data type ControlConnection See SystemLib. Description
Function Block Types in ControlBasicLib

PID type of Function Blocks
Table 52. PID type of function blocks.

Function block type PidLoop Description Display
This function block type defines a simple control ED, OD loop with a PID controller and a filter. The function block is to be connected directly to I/O via structured variables of the predefined data type RealIO. The PID controller of the control loop has feedforward and tracking functions and an Autotuner. The Autotuner calculates the controller gain, integration time and derivation time based on a simple relay experiment. The PID controller has integrator wind-up prevention and bumpless transfer between modes. It also has built in deviation alarm limits.
158
3BSE 026 333 R101 Rev A
Function Block Types in ControlBasicLib
Table 52. PID type of function blocks. (Continued)

PidLoop3P This function block type defines a simple control ED, OD loop with a three-position controller. It is identical to PidLoop except that the analog output is replaced by two binary outputs to increase or decrease the actuator position, or to keep it constant. This function block type defines a cascade control loop with two PID controllers. The function block is to be connected directly to I/O via structured variables of the predefined data type RealIO. The PID controller is identical to that in PidLoop. The integrator wind-up prevention is extended to also prevent wind-up in the master controller when the output of the slave controller is limited. PidCascadeLoop3P This function block type defines a cascade control loop with a three-position controller as slave controller. It is identical to PidCascadeLoop except that the analog output from the slave controller is replaced by two binary outputs to increase or decrease the actuator position, or to keep it constant. ED, OD ED, OD
PidCascadeLoop
3BSE 026 333 R101 Rev A
159
Simple Control Functions Library

This library (ControlSimpleLib) contains a number of function blocks, that are intended to be used for designing simple control loops. All function blocks in this library can be used in time-critical tasks. Table 53. Simple Control function blocks.
Function block type PidSimpleReal Description This function block is a simple PID-controller with less functionality than the PidLoop function blocks and the PidCC-module. The PidSimpleReal is however less time and memory consuming. This controller supports backtracking, tracking, manual control and output limiting. All transitions from limiting, tracking and manual mode are bumpless. There is also interaction graphics that makes set-up and maintenance of the controller easier. This function block is used either as a Lead or Lag function, i.e. derivative or integrating limiter. The actual function (Lead/Lag) is determined by the relation between the two input time constants, LeadT and LagT. The function block can be forced to track an external signal. Transition from tracking is bumpless. This function block is a single pole low-pass filter. The functionality obtained is mainly the same as with the control module FilterCC. The output can be forced to track an external signal. Transition from tracking is bumpless. This function block can be used in a time-critical task. Display OD, ED
LeadLagReal
FilterReal
160
3BSE 026 333 R101 Rev A
Table 53. Simple Control function blocks. (Continued)

Filter2PReal This function block is a low pass filter with one zero and two complex poles. The output can be forced to track an external signal. Transition from tracking is bumpless. This function block is a look-up table with a number of predefined input-output pairs. Values between these pairs are calculated by linear interpolation. The function block can be used to define a non-linear function y=f(x). The maximum number of data points is 21 and there is an interaction window that makes data input easier. The only restriction on the data points is that the x-values must be increasing. There is also a possibility to calculate the pseudo inverse of the defined function for a given input, InInverse. The functionality of this function block is the same as of the control module PiecewiseLinearCC. ED
PiecewiseLinearReal
PiecewiseLinear2DReal This function block is an extension of the PiecewiseLinearReal function block. It takes two inputs, which means that a non-linear surface, z=f(x,y) can be specified. The restriction to the x-, and the y-values is that they must be increasing. Maximum 21 x-values and 11 y-values can be specified, i.e., 231 data points. There is an interaction window that can be used to edit the data. VelocityLimiterReal This function block is a ramp function that is used to limit the velocity of change for a signal. The output can be forced to track an external signal. Transition from tracking is bumpless.
ED
3BSE 026 333 R101 Rev A
161
Table 53. Simple Control function blocks. (Continued)

AccelerationLimitReal This function block is a ramp function that is used to limit the velocity of change for a signal. The output can be forced to track an external signal. Transition from tracking is bumpless. It limits both the speed and acceleration. This function block is a regular integrator with the same functionality as the control module IntegratorCC. The output is limited and may be forced to track an external signal. All transitions from tracking and limiting are bumpless. This function block is a combined first order low-pass filter and a differentiator. The filter is used to smoothing the derivative action. The functionality is similar to the existing control module DerivativeCC. The output may be forced to track an external signal. Transition from tracking is bumpless. This function block is a three-position converter from a real input to two Boolean outputs (increase/decrease). It can be used with or without feedback from the actual actuator. It is similar to the existing control module ThreePosCC.
IntegratorReal
DerivativeReal
ThreePosReal
162
3BSE 026 333 R101 Rev A
Standard Control Library
Standard Control Library

This library (ControlStandardLib) contains control module types that can be used when designing your own standard control loops. They are to be used for continuous control; e.g. PID loops. They can be used for stand-alone or cascade control in masterslave configurations. The PID functions have Feedforward, Tracking, Backtracking, 3-position output, Hand/Auto and Autotuner control functions. Control modules have been used to create this library, and they have associated engineering and operator graphics. The control functions also have associated engineering and operator graphics. The control modules can be connected to other control modules in ControlExtendedLib, ControlAdvancedLib or ControlFuzzyLib in order to construct simple or advanced control loops. The control modules are connected via graphical connections of the data type Control Connection. Information is sent forwards as well as backwards in the control loop. The automatic sorting of code blocks in control modules is used to obtain signal flow without delay in both directions. This, in turn, is used to obtain good performance concerning bumpless transfer and integrator wind-up in the entire control loop. With the control modules in ControlStandardLib it is possible to create standard control loops suitable for many applications.
3BSE 026 333 R101 Rev A
163
Control Module Types in ControlStandardLib

PID Control Modules
Table 54. PID control modules.

Control module type PidCC Description Display
ED, OD This is a standard PID controller. It has all the functions of the PID controllers of the function blocks described above. But since it is a control module it may be connected to other control modules in order to create more advanced control loops than those that can be obtained with the function blocks described above. OD, ED This control module is a low-functionality Pidcontroller compared to the already existing Pidmodules, PidCC and PidAdvancedCC. The PidSimpleCC is however less time and memory consuming. There are interaction graphics that make set-up and maintenance of the controller easier. The main inputs and the output are of ControlConnection type, which means that backtracking and limiting is handled automatically.
PidSimpleCC
164
3BSE 026 333 R101 Rev A
Process I/O Control Modules
Most of the process I/O modules, used for continuous control operate with the data type Control Connection (CC). Table 55. Process I/O control modules.
Control module type AnalogInCC AnalogOutCC ThreePosCC Analog Input Analog Output Description Display ED, OD ED, OD
This control module is used as the end of a three- ED, OD point control loop with digital outputs. The control module input is an analog signal that is compared with a feedback signal from the valve position or internally generated. This control module is used as the graphical end ED, OD of a control loop with pulse modulated digital output. The control module input is an analog signal that generates the duty cycle of the output signal. The cycle time is defined via the parameter interface.
PulseWidthCC
3BSE 026 333 R101 Rev A
165
Manual Control Modules
Table 56. Manual control modules.

Control module type ManualAutoCC Description With this control module it is possible to enter values into a control loop manually, and supervise the control values graphically in bar graphs and histograms. Display ED, OD
Conversion Control Modules
Table 57. Conversion control modules.

Control module type RealToCC Description This control module is designed to collect each component to form a data type ControlConnection. Display ED
CCToReal
ED This control module functions as an adapter from a signal of data type ControlConnection. It splits the ControlConnection into its components to give a signal of data type real. The control module is an adapter from a signal of data type ControlConnection. It split up ControlConnection into each components, to a signal of data type integer. The real value of the parameter In is converted to the integer parameter Out. At conversion the hysteresis specified by the parameter Hysteresis is used. ED
CCToInteger
166
3BSE 026 333 R101 Rev A
Branch Control Modules
Table 58. Branch control modules.

Control module type BranchCC Branch4CC SplitRangeCC Description This control module divides the control loop connection structure into two equal branches. This control module divides the control loop connection structure into four equal branches. This control module divides the control loop connection structure into two branches in relation to their ranges. Display ED ED ED
MidRangeCC
This control module is a ControlConnection with ED two branches, one fast and one slower branch. The fast branch is acting faster on changes in the signal, and then it is forced to work around the mid point of its operating range as the slower branch takes over the control. This control module can be used in cases where, for example, two valves are acting on the same flow. One of the valves is a smaller, but faster valve, that is used to control small perturbations in the flow. The other valve is a bigger valve that cannot work that fast, but has a larger operating range. This control module divides the control loop connection structure into two branches with a specified ratio between the signal levels. This control module divides the control loop connection structure into two branches one where backtracking is possible and the other where it is not. This control module extracts the value component from the control loop connection structure to produce a real value. ED
CommonRangeCC
TapCC
ED
TapRealCC
ED
3BSE 026 333 R101 Rev A
167
Supervisory Control Modules
Table 59. Supervisory control modules.

Control module type Level6CC Description Display
This control module is used for level detection ED, OD purposes. It has six detection levels (LLL, LL, L, H, HH, HHH). L=Low, H=High
ED, OD SignalSupervisionCC This control module is used to take care of erroneous signal status collected from the transmitters or from the interface system. Three different modes are available let the signal pass through without any interference, freeze the output or linearly switch over to a predetermined value. Both these latter selections cause an alarm condition to be sent if configured.
168
3BSE 026 333 R101 Rev A
Selector Control Modules
Table 60. Selector control modules.

Control module type SelectorCC Description Display
This control module selects one of two inputs of ED, OD data type ControlConnection. Selection is made based on a Boolean signal. This control module selects one out of four inputs of data type ControlConnection. Selection is based on an integer signal. ED, OD
Selector4CC
SelectGoodCC
The first detected valid signal of type ED, OD ControlConnection is selected. If no valid signal is detected, Out is a copy of In1 structure. ED, OD The first detected valid signal of type ControlConnection is selected. If no valid signal is detected, Out is a copy of In1 structure. The control module MaxCC computes the larger ED, OD (maximum) value of two input signals of data type ControlConnection and writes it to the output signal. ED, OD The control module Max4CC computes the larger (maximum) value of four input signals of data type ControlConnection and writes it to the output signal. ED, OD The control module MinCC computes the smaller (minimum) value of two input signals of data type ControlConnection and writes it to the output signal. ED, OD The control module Min4CC computes the smaller (minimum) value of four input signals of data type ControlConnection and writes it to the output signal.
SelectGood4CC
MaxCC
Max4CC
MinCC
Min4CC
3BSE 026 333 R101 Rev A
169
Limiter Control Modules
Table 61. Limiter control modules.

Control module type LimiterCC Description LimiterCC limits the signal so that it does not increase above the upper limit, or decrease below the lower limit. LimiterHighCC limits the signal so that it does not increase above the upper limit. LimiterLowCC limits the signal so that it does not decrease below the lower limit. Display ED
LimiterHighCC LimiterLowCC VelocityLimiterCC
ED ED
ED VelocityLimiterCC limits the velocity of the signal. It can be used, for example, to create a linear movement function between a starting point and a target. This will slow down changes in the output signal to avoid rapid steps.
AccelerationLimitReal AccelerationLimitReal limits the velocity of the signal. It can be used, for example, to create a linear movement function between a starting point and a target. This will slow down changes in the output signal to avoid rapid steps. It limits both the speed and acceleration.
170
3BSE 026 333 R101 Rev A
Extended Control Library
Extended Control Library

This library (ControlExtendedLib) contains control modules for arithmetic and signal processing for continuous control, e.g. PID loops. The control functions are available as control modules, and they also have associated engineering and operator graphics. These control modules can be connected to other control modules in ControlStandardLib, ControlAdvancedLib or ControlFuzzyLib in order to create simple or advanced control loops. The control modules are connected via graphical connections of the data type Control Connection. Information is sent forwards as well as backwards in the control loop. The automatic sorting of code blocks in control modules is used to obtain signal flow without delay in both directions. This, in turn, is used to obtain good performance concerning bumpless transfer and integrator wind-up in the entire control loop. Using the control modules in ControlExtendedLib together with those in ControlStandardLib and ControlAdvancedLib it is possible to construct control loops with higher functionality. Arithmetic operations can be performed on the control signals. The control signals can also be processed in several ways, e.g. filtered or integrated.
3BSE 026 333 R101 Rev A
171
Control Modules in ControlExtendedLib

Arithmetic Control Modules
Table 62. Arithmetic control modules.

Control module type AddCC SubCC MultCC DivCC SqrtCC Description Addition, two inputs Subtraction, two inputs Multiplication, two inputs Division, two inputs Square root, one input Display ED ED ED ED ED
Signal Handling Control Modules
Table 63. Signal handling control modules.

Control module type DerivativeCC IntegratorCC FlowCC Derivation Integration with reset and hold function This control module calculates the mass flow from a differential pressure (orifice plate) compensated by actual temperature and pressure. This control module calculates the mean value of the inputs where extreme values are excluded. This control module has the same functionality as Mean4ExcludeBadCC above. The only difference is the number of inputs. Description Display ED ED ED
Mean4ExcludeBadCC
ED
Mean8ExcludeBadCC
ED
172
3BSE 026 333 R101 Rev A
Table 63. Signal handling control modules. (Continued)

Mean12ExcludeBadCC This control module has the same functionality as Mean4ExcludeBadCC above. The only difference is the number of inputs. FilterCC Filter2PCC LeadLagCC This is a first-order, low-pass filter. This control module is a low pass filter with one zero and two complex poles. This control module is used either as a Lead or Lag function, i.e. derivative or integrating limiter. The actual function (Lead/Lag) is determined by the relation between two input time constants. This is a delay control module for the ControlConnection structure. This control module delays the forward and backward components by one cycle to avoid program loops. Takes the value In1 raised to In2. ED
ED ED ED
DelayCC StateCC
ED ED
XRaisedToYCC
3BSE 026 333 R101 Rev A
173
Signal Conditioning Control Module
Table 64. Signal conditioning control module.

Control module type PiecewiseLinearCC PiecewiseLinear2DCC Description Piece wise linear transformation of the input signal. This control module is a look-up table with a number of predefined input-output data points. It takes two inputs, which means that a non-linear surface, z=f(x,y) can be specified. Maximum 21 x-values and 11 y-values can be specified, i.e. 231 data points. There is an interaction window that can be used to edit the data. Display ED ED
PiecewiseLinear-Extension This control module is to be used as an add-in-module together with the PiecewiseLinearCC module. The latter is only able to handle 21 data points. The control module makes it possible to add another 20 points of data. It is also possible to connect a control module to an existing control module of the same type. Thus, the number of possible points is unlimited.
ED
174
3BSE 026 333 R101 Rev A
Advanced Control Library
Advanced Control Library

This library (ControlAdvancedLib) contains control modules for advanced, continuous control, e.g. PID loops. The control functions are available as control modules, and they also have associated engineering and operator graphics. The control modules can be connected to other control modules in ControlStandardLib, ControlExtendedLib or ControlFuzzyLib in order to create simple or advanced control loops. The control modules are connected via graphical connections of the datatype Control Connection. Information is sent forwards as well as backwards in the control loop. The automatic sorting of code blocks in control modules is used to obtain signal flow without delay in both directions. This, in turn, is used to obtain good performance concerning bumpless transfer and integrator wind-up in the entire control loop. Using the control modules in ControlAdvancedLib together with those in ControlStandardLib and ControlExtendedLib it is possible to construct advanced control loops. The advanced PID controller has all the functionality of the previously described PID controllers. In addition, it may be configured for continuous adaptation of the controller parameters. It may also be configured as a predictive PI, i.e. a PPI, controller and it has a gain scheduler (also called a parameter scheduler).
3BSE 026 333 R101 Rev A
175
Control Module Types in ControlAdvancedLib
Control Module Types in ControlAdvancedLib

PID Control Modules
Table 65. PID control modules.

Control module type PidAdvancedCC Description Display
In addition to the standard functions this control ED, OD module type contains a gain scheduler and an adaptive controller. It has a PPI (predictive PI) controller for processes with long dead times. The loop assessment tools can detect oscillatory or sluggish behavior of the control loop. The Autotuner is more advanced than that in the other PID controllers.
Additional Control Modules
Table 66. Additional control modules.

Control module type Description Display
ED, OD StictionCompensator An optional extension to the AnalogOutCC control module to add pulses to the output of the AO and to avoid the effects of sticky pneumatic valves. Add-on to the AnalogOnCC. The faceplate (OD) for StictionCompensator, is a tab in the extended faceplate of AnalogOutCC.
176
3BSE 026 333 R101 Rev A
Fuzzy Control Library
Fuzzy Control Library

This library (ControlFuzzyLib) contains control modules, which are building blocks for fuzzy controllers. A fuzzy controller is constructed by connecting control modules from ControlFuzzyLib. No programming is necessary. ControlFuzzyLib also has three templates (not protected), which consists of three different fuzzy controllers. The control module types can be copied to your own library and then modified. A fuzzy controller can handle the case of one input and one output as well as many inputs and many outputs. It has most of the functions of a PID controller together with the possibility to define fuzzy logic rules for process control. A fuzzy controller consists of a linear part and a fuzzy logic part. The linear part has many of the functions of a PID controller, e.g.: Computation of the control deviation = Setpoint ProcessValue and its derivative (also the second derivative) Computation of the derivative of the process value A low-pass filter for the derivative of the process value and the control deviation Internal and external set point Handling of absolute and deviation alarms An integrator with anti-reset-wind-up function Manual and automatic output Tracking function for the output A feedforward function
The fuzzy logic part of the controller contains the functions used to define the rules for control of the process, e.g.: Computation of the degrees of membership of a number of signals to a number of fuzzy sets Computation of fuzzy conditions Computation of fuzzy rules
3BSE 026 333 R101 Rev A
177
Control Module Types in FuzzyLib
Computation of output membership functions for a number of controller outputs Defuzzification of the output membership functions.

Table 67. Control module types in FuzzyLib.
Control module type FuzzyController1CC FuzzyController2CC FuzzyController3CC FuzzySpPvIn Description This control module contains a very small configuration of a fuzzy controller. Display ED, OD
This control module has the same structure, but ED, OD contains a much larger configuration. This control module is the same as FuzzyController1CC, but with no setpoint. ED, OD
ED, OD This control module computes the control deviation EOut (setpoint-Process value) and its first and second derivatives. These signals are inputs to the InputMembership control modules. This control module can switch between an external and an internal setpoint. The process value may be filtered in a low-pass filter. Three Pv alarm levels and one deviation alarm may be displayed in the history and bar graphs. The control module also has an optional facility for process value tracking. The outputs from the control module, the control deviation and its two first derivatives may be simulated by the operator. This facility may be used to test the fuzzy logic part of the controller.
178
3BSE 026 333 R101 Rev A
Table 67. Control module types in FuzzyLib. (Continued)

FuzzyPvIn This control module makes the process value and its derivative available to the InputMembership control modules. The process value may be filtered in a low-pass filter. Three absolute alarm levels may be displayed in the history and bar graphs. The outputs from the control module, the process value, and its derivative, may be simulated by the operator. This facility may be used to test the fuzzy logic part of the controller. FuzzyOut This control module takes a defuzzyfied output ED, OD from the fuzzy logic part of the controller and computes the output to the process. The signal may be integrated or not. It may also be put in Manual or Automatic mode or it may track an external value. A feedforward signal may be added, and an anti-reset wind-up function is provided. InputMembership The control module defines an input membership function for the fuzzy logic part of the controller. For every value of the input it computes the degree of membership to the corresponding fuzzy set. The control module is also used, together with the FuzzyCondition control module, to define the fuzzy conditions. ED ED, OD
3BSE 026 333 R101 Rev A
179

OutputMembership ED The control module defines an output membership function for a fuzzy rule. It computes the current membership function, which is equal to the defined membership function, multiplied by the degree of satisfaction of the rule. The current membership functions for a number of rules may then be combined into a membership function for the output of the controller. This is done by computing the envelope, i.e. the maximum of all the current membership functions at every point. This is done in the Defuzzyfication control module. Defuzzyfication The control module computes the envelope of ED all the connected output membership functions. It also computes the center of gravity of the envelope curve. The center of gravity is regarded as the defuzzyfied output from the fuzzy logic part of the controller. ED
FuzzyCondition6, -12 The control modules FuzzyCondition6, and -18 FuzzyCondition12 and FuzzyCondition18 define and evaluate a fuzzy condition. The condition is defined as a fuzzy AND condition between a number of selected input membership functions. The input membership functions may, or may not, be inverted before the condition is formed. Together with other fuzzy conditions, the defined fuzzy condition is used in one or more fuzzy rules. The fuzzy AND condition is defined as the minimum value of the included fuzzy variables.
180
3BSE 026 333 R101 Rev A

ED FuzzyRule5, -10, -15, The control modules FuzzyRule5, -20, -25 and -30 FuzzyRule10, FuzzyRule15, FuzzyRule20, FuzzyRule25, and FuzzyRule30 define and evaluate a fuzzy rule. The condition of the rule is defined as a fuzzy OR expression between a number of fuzzy conditions defined in FuzzyCondition control modules. The conditions from the FuzzyCondition control modules may, or may not, be inverted before the condition of the FuzzyRule control module is formed. The result of the rule is the degree of satisfaction of the rule. The degree of satisfaction is used to compute the output membership function for the rule. The fuzzy OR condition is defined as the maximum value of the included fuzzy variables. FuzzyProgramControl This control module is used to toggle the Edit ED mode of the fuzzy logic part of the controller on and off. The fuzzy controller is fully operational in both modes. FuzzyPres This control module is an icon for the controller. ED It is intended to be built into the controller and displayed in the control module Diagram via a control module selector.
3BSE 026 333 R101 Rev A
181
Alarm and Event Library
Alarm and Event Library

This library (AlarmEventLib) contains functions for alarm and event handling, which include detection and notification. Alarm state handling and alarm acknowledgement are also included. An alarm data model according to OPC Alarms and Events is used.
Function Block Types in AlarmEventLib

Table 68. Function block types in AlarmEventLib.
Function block type AlarmCond Description Defines an alarm condition that follows a condition state diagram. It monitors the changes in an input parameter (boolean type) to detect an abnormal condition. Other inputs include acknowledge, disable and enable. A condition state output parameter presents the state of the alarm. The parameter AckRule (integer) defines the properties for acknowledgement handling. The source name SrcName identifies the name of the object where the alarm occurred. Class and Severity are inputs, which can be used to categorize the event that occurs when the alarm changes state. It is possible to supervise a signal on an I/O device, which reads the time stamp of the I/O changes on the device AttachSystemAlarm Makes it possible to present the current condition state of a specified system alarm. Display ED
182
3BSE 026 333 R101 Rev A
Function Block Types in AlarmEventLib
Table 68. Function block types in AlarmEventLib.

PrintAlarms Prints alarm conditions. On request, this function block prints a list of the alarms currently defined in the control system where the block executes. The printer should be connected directly to a serial port on the control system. The printer should be connected to the port corresponding to the Channel parameter, and should support the 8-bit character set. PrintEvents Prints events continuously. This function block prints both simple events and condition related events to a printer locally connected to the control system. This means that as soon as an AlarmCond changes state (e.g. from inactive to active) this information can be sent to the printer. However, only events generated in the system where the printer is connected, can be printed. The printer should be connected to the port corresponding to the Channel parameter, and should support the 8-bit character set. SimpleEventDetector Generates a simple event on a Boolean type condition. This function block supervises a Boolean type signal. When the signal changes value, a simple event is generated. You can use this function block to detect for example the start and stop of process objects. There is no acknowledgement handling; otherwise the function block resembles the AlarmCond. Severity and Class are inputs that can be used for sorting the events. It is possible to supervise a signal on an I/O device, which reads the time stamp of the I/O changes on the device.
3BSE 026 333 R101 Rev A
183
Control Module Types in AlarmEventLib
Control Module Types in AlarmEventLib

Table 69. Control module types in AlarmEventLib.
Control module type AlarmCondM Description Defines an alarm condition that follows a condition state diagram. This is the control module equivalent of the function block type AlarmCond described above. Display ED
184
3BSE 026 333 R101 Rev A
Batch Library
Batch Library
This library (BatchLib) contains functions for batch control and for control of other discontinuous processes.
Equipment Procedure Element Control Module Types

The control modules described here are used for the interaction between the control application for an Equipment Procedure Element (e.g. a phase or an operation) and the Batch Manager. Table 70. Equipment procedure element control module types.
Control module type Description Display ED, OD
EquipProcedureTemplate A template control module for designing Equipment Procedure Elements, i.e. the control logic for phases, operations, etc. It handles the interaction with the Batch Manager. EquipProcedureCore
Handles the standard ISA/S88-based states ED and modes of an Equipment Procedure Element.
3BSE 026 333 R101 Rev A
185
Communication Library
Communication Library
This library (CommunicationLib) contains a number of IEC 61131 function block types that provide external variable communication with protocols such as MMS, MODBUS, FOUNDATION Fieldbus, SattBus, COMLI, and Siemens 3964R. There are also function blocks for modem connection. Some control modules are also included in this library, supporting the MMS and FF protocols used in connection with control loop handling.
Data Types in CommunicationLib

Table 71. Communication library data types.
Data type Comm_Channel_MMS Comm_Channel_COMLI Comm_Channel_SB Description Reference to an MMS network connection. Reference to a COMLI network connection. Reference to a SattBus network connection.
Comm_Channel_S3964R Reference to a Siemens 3964R network connection. Comm_Channel_FF(1) Comm_Channel_MB Reference to a FOUNDATION Fieldbus network connection. Reference to ModBus network connection.
(1) A number of FOUNDATION Fieldbus data types are also supplied to support the user in a FOUNDATION Fieldbus communication network, for example, DS65.
MODBUS
These control functions are used for communication using MODBUS. Table 72. MODBUS functions.
Function block type MBConnect Description Initiates a communication channel and establishes a connection with a remote system. Display
186
3BSE 026 333 R101 Rev A
FOUNDATION Fieldbus
Table 72. MODBUS functions. (Continued)

MBRead MBWrite MBException Reads one or several variables. Writes to one or several variables. Reads the ModBus exception coils.
FOUNDATION Fieldbus
A number of IEC 61131 function blocks are provided for communication with FOUNDATION Fieldbus devices. These function blocks are used to access data belonging to function blocks in FF device(s) on the (FF) H1 bus (including the custom function blocks on the FF communication interface). All function block types, except those with the extension Cyc, follow the IEC 61131-5 standard. Some control module types are also supplied for accessing FF devices.
3BSE 026 333 R101 Rev A
187
FOUNDATION Fieldbus
Foundation Fieldbus Function Block Types
Table 73. FOUNDATION Fieldbus function block types.

Function block type FFConnect FFRead FFWrite FFReadCyc FFWriteCyc Description Connects to a defined FF device. Reads one parameter from an FF function block. Writes one parameter to an FF function block. Reads one parameter from an FF function block cyclically. Writes one parameter to an FF function block cyclically. Display
Foundation Fieldbus Control Module Types
Table 74. FOUNDATION Fieldbus control module types.

Control module type FFToCC Description Display
This control module is intended to be used when ED, continuously reading an FF- value of a floating OD point structure, i.e. value & status (the scaling is not included in the read operation). The read value is converted to a (OUT) parameter of the data type ControlConnection. This control module is intended to be used when ED, converting a (IN) parameter of the data type OD) ControlConnection to a value of a floating point structure and continuously writing it to an FF device.
CCToFF
188
3BSE 026 333 R101 Rev A
COMLI
COMLI
Use the COMLI function block types to establish communication with a system supporting the COMLI protocol. Function block types with the COMLI prefix support both the address-oriented COMLI and SattBus protocols. When a SattBus channel is used, the COMLI telegrams are packed within SattBus telegrams. The protocol to be used (COMLI or SattBus) is defined by the Channel parameter of the COMLIConnect function block. Communication via a TCP/IP network is also supported. Table 75. COMLI function block types.
Function block type COMLIConnect COMLIRead COMLIReadCyc COMLIReadPhys COMLIWrite COMLIWriteDT Description Connects to a defined communication channel. Reads one or several variables. Reads variable data cyclically. Requests physical values from a legacy (SattCon) system. Writes to one or several variables. Transmits date and time of master to the slave. Display
MMS
Use the MMS function block types and control modules to establish communication with a system supporting the MMS protocol. Table 76. MMS function block types.
Function block type MMSConnect MMSRead MMSReadCyc Description Initiates a communication channel and establishes a connection with a remote system. Reads one or several variables. Reads one or several variables cyclically. Display
3BSE 026 333 R101 Rev A
189
MMS
Table 76. MMS function block types. (Continued)

MMSWrite MMSWriteDT MMSDefAccVar Writes to one or several variables. Transmits date and time. This function block is used to create an access variable, which is connected to a defined variable in the executing system. The defined variable is then accessible for both reading and writing from a remote system and also within its own system
Table 77. MMS control module types.

Control module Type MMSToCC Description Display
This control module is used when continuously ED, reading a signal of a ControlConnection type OD from another system. The communication protocol is MMS. The forward and the backward structure of ControlConnection is handled in MMS variable groups separately. This control module is used when writing a signal of type ControlConnection to another system. The communication protocol is MMS. The forward and the backward structure of ControlConnection is handled in MMS variable groups separately. ED, OD
CCToMMS
190
3BSE 026 333 R101 Rev A
SattBus
Transfer of Variables via MMS
When transferring variables it is important to use data types with the same range on the client as on the server. It is, however, possible to connect variables with different ranges, such as a dint variable on the server and an Int variable on the client. This will only work as long as the variable values are within the range of the Int variable, but if the value of the dint is outside this range it will not work.
SattBus
Use these function block types, supporting SattBus, to communicate through a SattBus channel using the SattBus name-oriented model. To communicate through a SattBus channel using the address-oriented model, use COMLI function block types. Communication via a TCP/IP network is also supported. Table 78. SattBus function block types.
Function block type SBConnect SBRead SBReadCyc SBWrite Description Connects to a defined communication channel. Reads one variable data Reads variable data cyclically. Writes one variable data. Display
3BSE 026 333 R101 Rev A
191
Siemens 3964R
Siemens 3964R
Use the Siemens 3964R function block types to establish communication with a system using the Siemens 3964R protocol. Table 79. Siemens 3964R function block types.
Function block type S3964RConnect S3964RRead S3964RReadCyc S3964RWrite Description Connects to a defined communication channel. Reads one or several variables. Reads variable data cyclically. Writes to one or several variables. Display
Other Function Blocks

Use these function block types to establish communication with a modem. Table 80. Other function blocks.
Function block type ModemConnStat Description ModemConnStat is used to obtain the current status of a modem connected to a selected channel. The current status is given by the Status parameter. ModemDialUp is used to connect a modem via a defined communication channel. ModemHangUpis used to disconnect a modem via a defined communication channel. Display
ModemDialUp ModemHangUp
192
3BSE 026 333 R101 Rev A
Serial Communication Library
Serial Communication Library

This library (SerialLib) contains function blocks for communication with external devices via serial channels with user-defined protocols, for example, printers, terminals, or scanner pens.
Data Types
Table 81. Serial communication library data types.
Data type Description
Comm_Channel_Serial Reference to a serial network connection.
Function Block Types

Table 82. Serial channel function block types.
Function block type SerialConnect SerialSetup SerialWriteWait SerialListenReply SerialWrite SerialListen Description Opens and closes a defined serial communication channel. Changes serial communication settings. Writes a string and waits for a reply. Listens for a string and sends a reply. Writes a string. Listens for a string. Display
3BSE 026 333 R101 Rev A
193
INSUM Library
INSUM Library
Introduction
INSUM (INtegrated System for User-optimized Motor control) utilizes microprocessor-based technology for protection and control of motors and switchgear, and for the transmission of messages and measured values. Each motor has a motor control unit (MCU) located in the motor starter module. The INSUM devices (such as MCUs) are arranged in up to four subnets, each of them supporting up to 32 units at 78 kb/s transfer rate. A network (LonWorks) transfers messages at 1.25 Mb/s between the subnet units via routers. An INSUM MMI (man-machine interface) and one or more AC 800M controllers, equipped with INSUM TCP/IP interface modules CI857 can be connected to the LonWorks network. The Process Portal A and the SCADA Portal can be accessed from the AC 800M.
Provided Services
Up to 128 motors (MCU), circuit breakers (CB) and intelligent tier switches (ITS) can be supervised per INSUM TCP/IP gateway. Multiple controllers can access the same MCU in an INSUM system. Three IEC 61131-3 function blocks are available for initialization and exchanging data with the INSUM system, namely INSUMConnect (establishes connection), INSUMReceive (reads a process data value from an INSUM device), and INSUMWrite (writes a value to an INSUM device). The INSUM system can operate completely independently from other systems belonging to ControlIT or OperateIT. A number of different motor types are supported, such as reversing motors, two-speed drives, actuators, and solenoid valves. Protection is provided against thermal overload, underload, phase loss, earth fault, high motor temperature, locked rotor, etc. Protection functions can be parameterized to specify pre-warnings before a motor is tripped. The reset can be automatic, remote, local or remote and local.
194
3BSE 026 333 R101 Rev A
Data Types
Data Types
Table 83. INSUM library data types.
Data type NVDesState NVCurrentReport NVMotorStateExt Description Forces a MCU (Motor Control Command) up to a desired state. Output Network Variable used to report motor phase current. A variable used for reception of the information about the actual motor state from a MCU (Motor Control Command). Can be used if a bitfield representation of the motor state information is to be used. Obtains information about cumulated run hours. Network Variable of motor power report. Network Variable used to report current values. Forces CommandState of a CB (Circuit Breaker) to a desired state. A variable to be used for reception of the information about the actual status from a CB (Circuit Breaker).
NVMotorStateExtStruct NVCumRunT NVVoltageReport NVAmpsCurrRep NVNodeCommand NVNodeStatusRep
NVNodeStatusRepStruct Can be used if a bitfield representation of the information about the actual status from CB is to be used.
3BSE 026 333 R101 Rev A
195

Table 84. INSUM function block types.
Function block type INSUMConnect Description The INCUMConnect function block establishes a connection to a concerned INSUM Gateway, which is used as a base for other INSUM specific IEC 61131-5 function blocks to access the proper INSUM data. The function block allows to establish a connection between teh calling communication partner and remote communication partner. It also gives a status information about the connected device, which may be used for supervision of the device. INSUMReceive The INSUMReceive function block is used to read one network varibale cyclically from an INSUM device to an 61131 variable, which could be for example input of network varibale used in a control lopp where the controller is part of the loop. INSUMReceive is intended to be the standard method to get data from an INSUM device to the controller. to update the presentation of signals in a set interval viewed in OperateIT, suitably when involved variables are in view. Display
INSUMWrite
The INSUMWrite function block writes from an IEC 61131 variable to a network variable on request, i.e. triggered from an OperateIT, which is used for sending command (start/stop/reset) and handling Pass Control Access.
196
3BSE 026 333 R101 Rev A
MB300 Library
MB300 Library
Introduction
Masterbus 300 (MB 300) can be used with AC 400 and AC 800M. A CI855 communication unit for AC 800M provides connectivity to AC 400 via MB 300. Refer to the relevant users guides and reference manuals regarding the process interface that can be used with AC 400. CI855 is configured by means of Control Builder in the hardware configuration tree, but has no subordinated devices represented in the tree. This means that other controllers on the MB 300 network are not represented in the tree. The CI855 module has two Ethernet channels to provide network redundancy.
Provided Services
DataSet communication with other controllers on MasterBus 300. Function blocks in the AC 800M are used to cyclically send and receive datasets on MasterBus 300. Time synchronization on MB 300 is supported in the AC 800M with the accuracy provided on MB 300. The CI855 device status, watchdog supervision and logged system messages are reported to the AC 800M for display in the Control Builder M and the Process Portal A status system. Support of MB 300 network redundancy.
3BSE 026 333 R101 Rev A
197

Table 85. MB300 function block types.
Function block type MB300Connect Description The MB300Connect is used to establish connection between the calling communication partner and the remote communication partner. MB300Send function block is used to send a DataSet to a node on MB300 The MB300Receive function block is used for reception of a DataSet sent by a note on MB300 Display
MB300Send MB300Receive
198
3BSE 026 333 R101 Rev A
INDEX
A
ABB Drives 27, 78 ABB Engineered Drives 78 ABB Standard Drives 79 AC 250 19 AC 800C 19 AC 800M 19 single CPU mode 45 AC 800M/C Connect 32 Access variable editor 50 Access variables 50 Advanced Process Control 20, 29 Advant Controller 250 19 alarm and event library 182 AlarmEventLib 182 Applications 36 arithmetic control modules, see control modules arithmetic functions (extensible), see functions arithmetic functions (non-extensible), see functions array and queue functions 141 array and queue functions, see functions arrays 141 bitwise Boolean functions (standard), see functions branch control modules 167 Bulk Data Manager 32
C
CAST 95 CD-ROM 32 character string functions (standard), see functions CI851 37 CI852 37 CI854 37, 76 CI856 39 CI857 38 Clock Master 44 CMD editor 30, 52 CNCP light 44 Code distribution 26 COMLI 42, 189 Communication MMS 88 CommunicationLib 186 comparison functions (standard), see functions Compilation 75 Control Builder Basic 20, 31 Professional 20, 31 Standard 20, 31 variants 31 Control Builder M 20, 33 Control Connection 165 control library 163
B
Base licenses 103 libraries 103 Basic Control 20 BatchLib 185 Binary Control 20 bi-stable function blocks (standard), see function blocks bit shift functions (standard), see functions
3BSE 026 333 R101 Rev A
199
Index
control modules additional 176 arithmetic 172 branch 167 conversion 166 limiter 170 manual 166 PID 164, 176 process I/O 165 selector 169 signal conditioning 174 signal handling 172 supervisory 168 types in FuzzyLib 178 Control Network 35, 40 Control Software 19, 33, 36 licenses 102 ControlAdvancedLib 175 ControlBasicLib 158 ControlExtendedLib 171 ControlFuzzyLib 177 Controller platforms 19 ControlNet 37 control-related data types 133 ControlStandardLib 163 conversion control modules 166 Count I/O points 104 counter function blocks (standard), see function blocks CPU load 78 CPU redundancy 45
E
Engineered Drives 78 Engineering Studio 32 Execution times 63 to 64 control modules 64 function block calls 71 function blocks 64 functions 73 operations 73 Expansion 99 Expansion licenses 96, 102, 104 External user help 28
F
F1 help 53 Fieldbus Builder P 32, 35 Fieldbus communication 37 Firmware 36 FOUNDATION Fieldbus 37, 187 function blocks bi-stable (standard) 143 counter (standard) 143 timer (standard) 143 functions arithmetic (extensible) 135 arithmetic (non-extensible) 135 array and queue 141 bit shift (standard) 136 bitwise Boolean (standard) 136 character string (standard) 137 comparison (standard) 136 general 135 logarithmic 135 selection (standard) 136 task control 142 trigonometric 135 type conversion 134, 138 Fuzzy controller 177 FuzzyLib 103
D
Data access 56 Dial-up modems 43 Download 34, 36, 75
200
3BSE 026 333 R101 Rev A
Index
G
GSD Import Tool 25
M
manual control modules 166 Market segments 21 MasterBus 300 39 MB 300 39 Memory consumption 63 control modules 64 function blocks 64 S100 I/O 88 S200 I/O 85 S200L I/O 85 S800 I/O 80 S900 I/O 83 Mirroring 24 MMS 88, 189 master system 89 slave system 90 to 91 MODBUS 186 ModBus RTU master 42 Modem 43 Modulebus 76, 78 scan cycle 78 scan interval 76, 78 scan time 76 Multi-user development 27
H
Hardware requirements 60 HART 24, 32, 35
I
I/O communication 37 I/O points 95 counting 95 I/O support 27, 29 I/O-related data types 131 IEC 61131-3 function block types 143 standard functions 134 IEC 61131-3 languages 28 INSUM 38 Integrated Automation 22, 29 Integration 32 IP Configuration 36
K
Key benefits 19
L
libraries AlarmEventLib 182 ControlStandardLib 163 License concept 101 Licenses 20, 101 limiter control modules 170 Local Operating Network 39 Log functions 26, 29 logarithmic functions, see functions LON 39
N
Network redundancy 45 to 46 New This Version 22
O
Object-oriented programming 28 Online help context-sensitive 53 F1 53 OPC Server performance data 92 requirements 61
3BSE 026 333 R101 Rev A
201
Index
Ordering 95 example 98 procedure 95
Re-use code 51 RNRP 40 to 41 Runtime license 101
P
Performance OPC Server 92 Performance data 61 PID control modules 164, 176 PM861 45 Portability 26 POU 49 Prerequisites 59 Price lists 95 process I/O control modules 165 process object function block types 144 Process object Function Block types 144 Process Portal A 32 ProcessObjBasicLib 152 ProcessObjExtLib 154 Professional 31 PROFIBUS-DP 37 PROFIBUS-DP/V1 37 Programming environment 28 Programming station 34 Project Explorer 48
S
S100 I/O 39 memory consumption 88 S200 I/O 39, 85 memory consumption 85 S200L I/O 39 memory consumption 85 S800 I/O 39 memory consumption 80 S900 I/O 39 memory consumption 83 SattBus 37, 191 SCADA and PLC Solutions 21, 25 Scalability 25 Scan cycle ABB Drives 78 Modulebus 78 Scan interval 76 Modulebus 76 Scanning ABB Drives 76 selection functions (standard), see functions selector control modules 169 SerialLib 193 Short-distance modems 43 Siemens 3964R 42, 192 signal conditioning control module 174 signal handling control modules 172 Standard Drives 79 supervisory control modules 168 System events and alarms 47 SystemLib data types 131 function block types 143 function types 134
Q
queues 141
R
RAM memory 63 Redundancy 26 CPU 45 line 46 network 46 Requirements 59 hardware 60, 62 OPC Server 61
202
3BSE 026 333 R101 Rev A
Index
T
Tags 105 task control functions, see functions Task management 26 Technical data 61 Terminology 14 time functions 137 Time synchronization 23 timer function blocks (standard), see function blocks Tool Routing 32 trigonometric functions, see functions type conversion functions, see functions
U
Update rate 92 User information 28
V
Variants comparison 31
3BSE 026 333 R101 Rev A
203
Index
204
3BSE 026 333 R101 Rev A
3BSE 026 333 R101 Rev A. Printed in Sweden May 2002 Copyright 19992001 by ABB. All Rights Reserved Registered Trademark of ABB. Trademark of ABB.
http://www.abb.com/control Automation Technology Products Vsters, Sweden www.abb.com/processautomation email: processautomation@se.abb.com Automation Technology Products Wickliffe, Ohio, USA www.abb.com/processautomation email: industrialitsolutions@us.abb.com Automation Technology Products Mannheim, Germany www.abb.de/processautomation email: marketing.control-products@de.abb.com

Abb Control Builder 3bse026333

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Abb Control Builder 3bse026333

Caricato da

Copyright:

Formati disponibili

ControlIT

Control Software and Control Builder M

FOUNDATION Fieldbus Trademark of Fieldbus Foundation, USA.

Section 1 - Key Benefits

3BSE 026 333 R101 Rev A

Section 2 - Product Description

3BSE 026 333 R101 Rev A

Section 3 - Technical Data and Performance

3BSE 026 333 R101 Rev A

Appendix B - Supported Hardware and I/O Systems

Appendix C - Library Objects Overview

3BSE 026 333 R101 Rev A

Siemens 3964R...................................................................................................192 Other Function Blocks .......................................................................................192

3BSE 026 333 R101 Rev A

3BSE 026 333 R101 Rev A

About This Book

Purpose, Scope and Intended Use

3BSE 026 333 R101 Rev A

Use of Information, and Tip Icons

About This Book

Use of Information, and Tip Icons

3BSE 026 333 R101 Rev A

About This Book

3BSE 026 333 R101 Rev A

About This Book

Access variables AIP Applications

CNCP Cold retain

Control Builder M Control module

3BSE 026 333 R101 Rev A

About This Book

Term Data type

FBD FF Global variable GSD file HART

I/O point count IEC 61131-3

3BSE 026 333 R101 Rev A

About This Book

RNRP RS-232C RS-485

3BSE 026 333 R101 Rev A

About This Book

Term SNTP SOE ST Task

3BSE 026 333 R101 Rev A

Related Product Guides

About This Book

Related Product Guides

3BSE 026 333 R101 Rev A

Section 1 Key Benefits

3BSE 026 333 R101 Rev A

Section 1 Key Benefits

3BSE 026 333 R101 Rev A

Section 1 Key Benefits

Market Segments, Licenses and Control Builder Variants

Market Segments, Licenses and Control Builder Variants

3BSE 026 333 R101 Rev A

New This Version

Section 1 Key Benefits

New This Version

3BSE 026 333 R101 Rev A

Section 1 Key Benefits

Added CPU support: PM861 (AC 800M)

3BSE 026 333 R101 Rev A

Section 1 Key Benefits

3BSE 026 333 R101 Rev A

Section 1 Key Benefits

OPC Server for AC 800M/C