2VAA000813-230 A en Splus Engineering 2.3 Automation Architect User Manual

—
INDUSTRIAL AUTOMATION
ABB Ability™ Symphony® Plus

S+ Engineering 2.3 Automation architect
User manual
—
INDUSTRIAL AUTOMATION
ABB Ability™ Symphony® Plus

S+ Engineering 2.3 Automation architect
User manual
Notice
This document contains information about one or more ABB products and may include a description of or
a reference to one or more standards that may be generally relevant to the ABB products. The presence of
any such description of a standard or reference to a standard is not a representation that all of the ABB
products referenced in this document support all of the features of the described or referenced standard.
In order to determine the specific features supported by a particular ABB product, the reader should con-
sult the product specifications for the particular ABB product.
ABB may have one or more patents or pending patent applications protecting the intellectual property in
the ABB products described in this document.
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.
Products described or referenced in this document are designed to be connected and to communicate in-
formation and data through network interfaces, which should be connected to a secure network. It is the
sole responsibility of the system/product owner to provide and continuously ensure a secure connection
between the product and the system network and/or any other networks that may be connected.
The system/product owners must establish and maintain appropriate measures, including, but not limit-
ed to, the installation of firewalls, application of authentication measures, encryption of data, installation
of antivirus programs, and so on, to protect these products, the network, its system, and interfaces
against security breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or
information.
ABB performs functionality testing on the products and updates that we release. However, system/prod-
uct owners are ultimately responsible for ensuring that any product updates or other major system up-
dates (to include but not limited to code changes, configuration file changes, third-party software
updates or patches, hardware change out, and so on) are compatible with the security measures imple-
mented. The system/product owners must verify that the system and associated products function as ex-
pected in the environment in which they are deployed.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any na-
ture 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, cop-
ied, or disclosed only in accordance with the terms of such license.
This product meets the requirements specified in EMC Directive 2014/30/EU and in Low Voltage Directive
2014/35/EU.
The crossed-out wheeled bin symbol on the product and accompanying documents means
that used electrical and electronic equipment (WEEE) should not be mixed with general house-
hold waste. If you wish to discard electrical and electronic equipment (EEE), please contact
your dealer or supplier for further information.
Disposing of this product correctly will help save valuable resources and prevent any potential negative
effects on human health and the environment, which could otherwise arise from inappropriate waste
handling.
Trademarks and copyright

Symphony and Symphony Plus are registered or pending trademarks of ABB S.p.A.
Ability is a trademark of ABB.
All rights to copyrights, registered trademarks, and trademarks reside with their respective owners.
Copyright © 2011-2020 ABB. All rights reserved.
Release: May 2020

Document number: 2VAA000813-230
Revision: A
TABLE OF CONTENTS
TABLE OF CONTENTS
1. Introduction.................................................................................................... 1-1
1.1 Overview ..............................................................................................................1-1
1.2 Features ...............................................................................................................1-1
1.3 Intended User ......................................................................................................1-1
1.4 Instruction Content .............................................................................................1-1
1.5 How to Use this Instruction ................................................................................1-2
1.6 Document Conventions ......................................................................................1-2
1.7 Glossary of Terms and Abbreviations...............................................................1-3
1.8 Reference Documents ........................................................................................1-3
2. Controller Configuration Overview .............................................................. 2-1

2.1 Introduction .........................................................................................................2-1
2.2 General Configuration Procedure......................................................................2-1
2.3 Exchange .............................................................................................................2-2
2.4 Tag Assignment...................................................................................................2-2
2.5 CLD Editing Modes .............................................................................................2-3
2.6 Automation Architect Window Menus...............................................................2-3
2.7 Document Operations.........................................................................................2-3
2.7.1 Open ................................................................................................................2-4
2.7.2 Save.................................................................................................................2-4
2.7.3 Print..................................................................................................................2-4
2.7.4 Revise ..............................................................................................................2-4
2.7.5 Close................................................................................................................2-4
2.7.6 Document Modes.............................................................................................2-4
2.8 Multiple Document Windows .............................................................................2-4
2.9 Document Workspace.........................................................................................2-4
2.9.1 Toolbar .............................................................................................................2-5
2.9.2 Environment Properties ...................................................................................2-5
2.9.3 Saving and Restoring Environment Properties ..............................................2-14
2.9.4 Magnify, Pan, and Refresh the View..............................................................2-15
2.9.5 Mouse Scrolling Horizontal and Vertical ........................................................2-16
2.9.6 Mouse Zooming In/Out ..................................................................................2-17
2.9.7 Mouse Panning ..............................................................................................2-19
2.9.8 Fit to view Selected Objects...........................................................................2-21
2.9.9 Cursor ............................................................................................................2-22
2.9.10 Grid ................................................................................................................2-22
2.9.11 Open Previous/Next Document .....................................................................2-23
2.10 Measuring Distance ..........................................................................................2-23
2VAA000813-230 A 1
TABLE OF CONTENTS
3. Configuration Components .......................................................................... 3-1

3.1 Introduction .........................................................................................................3-1
3.2 Entities .................................................................................................................3-1
3.3 Drawing Entities ..................................................................................................3-2
3.4 Arc ........................................................................................................................3-2
3.5 Border...................................................................................................................3-2
3.6 Circle ....................................................................................................................3-3
3.7 Constant Block ....................................................................................................3-3
3.8 Function Code .....................................................................................................3-4
3.9 Cross-References................................................................................................3-5
3.9.1 I/O Connector...................................................................................................3-6
3.9.2 Reference Connector.......................................................................................3-7
3.9.3 Example using Reference Connections to Connect Function Codes on Different
Sheets in a CLD...............................................................................................3-8
3.9.4 Example using Reference Connections to connect Different Controllers, Same
HCU Node........................................................................................................3-8
3.9.5 Example using Reference Connections to connect Different HCU Nodes or
Different Control Networks...............................................................................3-8
3.9.6 Cross Reference Description Fields ................................................................3-8
3.10 Line .....................................................................................................................3-10
3.11 Macro.................................................................................................................. 3-11
3.12 Rectangle ........................................................................................................... 3-11
3.13 Shape..................................................................................................................3-12
3.14 Signal..................................................................................................................3-12
3.15 Text .....................................................................................................................3-13
3.16 Defining Tag and Trend Points.........................................................................3-13
3.17 Multiple Sheets ..................................................................................................3-14
3.18 Control Logic Templates...................................................................................3-14
3.18.1 Linking Functions ...........................................................................................3-14
4. Editing Configurations .................................................................................. 4-1

4.1 Introduction .........................................................................................................4-1
4.2 Entity Selection ...................................................................................................4-1
4.3 Entity Editing .......................................................................................................4-2
4.3.1 Attributes..........................................................................................................4-2
4.3.2 Tag ...................................................................................................................4-3
4.3.3 Block Number ..................................................................................................4-4
4.3.4 Cross-Reference Name ...................................................................................4-4
4.3.5 Line and Signal Width ......................................................................................4-5
4.3.6 Cut, Copy, and Paste .......................................................................................4-5
4.3.7 Delete...............................................................................................................4-5
2 2VAA000813-230 A
TABLE OF CONTENTS
4.3.8 Explode ............................................................................................................4-5

4.3.9 Specifications...................................................................................................4-6
4.3.10 Text ..................................................................................................................4-7
4.3.11 Movement ........................................................................................................4-7
4.3.12 Rotate ..............................................................................................................4-8
4.3.13 Scale ................................................................................................................4-8
4.3.14 Resize ..............................................................................................................4-8
4.4 Creating Shapes, Macros, Borders, and Control Logic Templates ................4-8
4.5 Editing Shapes, Macros, Borders, and Control Logic Templates...................4-9
4.5.1 Shapes.............................................................................................................4-9
4.5.2 Borders ............................................................................................................4-9
4.5.3 Macros ...........................................................................................................4-10
4.5.4 Control Logic Templates ................................................................................4-10
4.6 Repeating the Last Command..........................................................................4-10
4.7 Undoing and Redoing Operations ................................................................... 4-11
5. Example Configuration ................................................................................. 5-1

5.1 Introduction .........................................................................................................5-1
5.2 Example Control Logic Document Data ............................................................5-1
5.3 Configuration Procedure ....................................................................................5-1
5.3.1 Creating and Opening a Control Logic Document ...........................................5-2
5.3.2 Inserting a Border ............................................................................................5-2
5.3.3 Inserting Function Codes .................................................................................5-2
5.3.4 Inserting Cross-References .............................................................................5-2
5.3.5 Inserting Constant Blocks ................................................................................5-2
5.3.6 Connecting Components with Signals .............................................................5-2
5.3.7 Connecting Components with Branches..........................................................5-3
5.3.8 Adding Text ......................................................................................................5-3
5.3.9 Setting Specifications.......................................................................................5-4
5.3.10 Setting Properties ............................................................................................5-4
5.3.11 Assigning Tags.................................................................................................5-5
6. Monitor/Tune Configurations........................................................................ 6-1

6.1 Introduction .........................................................................................................6-1
6.2 Online Mode.........................................................................................................6-1
6.2.1 Configuration....................................................................................................6-1
6.2.2 Usage...............................................................................................................6-2
6.2.3 Monitor/Tune Tag Status Indicators .................................................................6-2
6.2.4 Communication Status Indicator ......................................................................6-3
6.2.5 Instant Trend ....................................................................................................6-4
6.3 Communication Settings for Monitoring...........................................................6-4
2VAA000813-230 A 3
TABLE OF CONTENTS
A. Standard Entities ........................................................................................... A-1
B. CLD Lockable Properties .............................................................................. B-1
4 2VAA000813-230 A
TABLE OF CONTENTS
2VAA000813-230 A 5
TABLE OF CONTENTS
6 2VAA000813-230 A
LIST OF TABLES
LIST OF TABLES
Table 1-1: Glossary of Terms and Abbreviations ................................................................ 1-3

Table 1-2: Reference Documents ....................................................................................... 1-3
Table 3-1: Available Template Linking Functions .............................................................. 3-16
Table 4-1: Function Code Specification Column Headings ................................................. 4-6
Table 4-2: Border Text Fields .............................................................................................. 4-9
Table 6-1: Status Indicator .................................................................................................. 6-3
Table A-1: Standard Entities ................................................................................................ A-1
Table B-1: Linking-Related Logic Entity Properties ............................................................. B-1
2VAA000813-230 A 5
LIST OF TABLES
6 2VAA000813-230 A
LIST OF FIGURES
LIST OF FIGURES
Figure 2-1: S+ Engineering Automation Architect Window.................................... 2-1

Figure 2-2: Automation Architect Toolbar .............................................................. 2-5
Figure 2-3: Tools Options General Tab ................................................................. 2-5
Figure 2-4: Tool Options View Tab ........................................................................ 2-6
Figure 2-5: Override Specification Display Location per Function Code ............... 2-7
Figure 2-6: Tools Options View Show Property Example...................................... 2-7
Figure 2-7: Tools Options Edit Tab........................................................................ 2-8
Figure 2-8: Override Width Selection for Line Entity.............................................. 2-8
Figure 2-9: Tools Options Grid Tab ....................................................................... 2-9
Figure 2-10: Tools Options Layer Tab ................................................................. 2-10
Figure 2-11: Tools Options Function Codes Tab................................................. 2-11
Figure 2-12: Tools Options Signal Tab ................................................................ 2-11
Figure 2-13: Override Global Setting for Width Selection Signal Entity............... 2-12
Figure 2-14: Tools Options Instant Trend Tab..................................................... 2-12
Figure 2-15: Instant Trend Example .................................................................... 2-13
Figure 2-16: Tools Options Monitoring Tab ......................................................... 2-13
Figure 2-17: Group Monitoring Example.............................................................. 2-14
Figure 2-18: Tools Options General Functions.................................................... 2-14
Figure 2-19: Import/Export/Restore Preferences................................................. 2-15
Figure 2-20: Mouse Properties ............................................................................ 2-17
Figure 2-21: Mouse Zooming In/Out.................................................................... 2-17
Figure 2-22: Zooming In ...................................................................................... 2-18
Figure 2-23: Zooming Out.................................................................................... 2-19
Figure 2-24: Pan Mode Instantiated .................................................................... 2-20
Figure 2-25: Pan Mode Activation ....................................................................... 2-21
Figure 2-26: Fit window option............................................................................. 2-21
Figure 2-27: Fit to View Selected Object ............................................................. 2-22
Figure 2-28: Previous and Next Document Selection.......................................... 2-23
Figure 3-1: Cross-Reference Descriptions ............................................................ 3-9
Figure 3-2: Description Fields.............................................................................. 3-10
Figure 3-3: Combined Top and Bottom Description Values ................................ 3-10
Figure 3-4: Line Style and Width Style Drop Down ............................................. 3-11
Figure 3-5: Adding a Signal ................................................................................. 3-21
Figure 3-6: Deleting a Signal ............................................................................... 3-22
Figure 3-7: Moving Source Connectors ............................................................... 3-23
Figure 3-8: Moving Target Connectors ................................................................ 3-24
Figure 3-9: Disconnected Signals........................................................................ 3-25
Figure 5-1: Example Control Logic ........................................................................ 5-1
Figure 6-1: Enabling the Group Monitoring function .............................................. 6-1
Figure 6-2: “G” Mark .............................................................................................. 6-1
Figure 6-3: Communication Status Indicator ......................................................... 6-3
2VAA000813-230 A vii
LIST OF FIGURES
Figure 6-4: Instant Trend Display ......................................................................... 6-4

Figure A-1: Standard Entities (1 of 4) ....................................................................A-4
viii 2VAA000813-230 A
Preface
This instruction provides details to use S+ Engineering Control Engineering Automation Architect application. The
Automation Architect window provides a means of developing and editing control logic documents using graphical
representations of function code algorithms and their interconnections. The function codes and other graphic elements are
actually inserted or drawn on sheets which make up a control logic document. Typically, a control logic document is made
up of a number of sheets in which each sheet contains a portion of the configuration. Sheets can also contain graphic
elements which are used for documentation purposes. However, documentation elements are not actually part of the
configuration.
The Automation Architect window can also be used to monitor and tune a process control system using the monitor/tune
mode of operation. In this mode, live function code values from the controller are displayed in the configuration sheet.
Tunable parameters can be adjusted and the process values can be monitored while making adjustments
2VAA000813-230 A
2VAA000813-230 A
Support Services
ABB will provide assistance in the operation and repair of its products. Requests for sales or application services should be
made to your nearest sales or service office. ABB can also provide installation, repair and maintenance contract services.
When ordering parts, use nomenclature or part numbers and part descriptions from equipment manuals. Parts without a
description must be ordered from the nearest sales or service office. Recommended spare parts lists, including prices are
available through the nearest sales or service office.
ABB has modern training facilities available for training your personnel. On-site training is also available. Contact your
nearest ABB sales office for specific information and scheduling. Additional copies of this instruction, or other instructions,
can be obtained from the nearest ABB sales office at a reasonable charge.
2VAA000813-230 A
2VAA000813-230 A
About This Book
About This Book
General
This user manual describes the Control Engineering Automation Architect functionality.
Document Conventions
Microsoft Windows conventions are normally used for the standard presentation of material when entering text, key
sequences, prompts, messages, menu items, screen elements, etc.
S+ Engineering Themes
The theme for S+ Engineering is a user configurable setting. The theme depicted in this Online help is independent of the
described functionality.
Use of Information, Tip, and Warning Icons

This publication includes Information, Tip, and Warning where appropriate to point out important information or useful
hints to the reader. The corresponding symbols should be interpreted as follows:
Electrical Warning icon: It indicates the presence of a hazard that could result in electrical shock.
Warning icon: It indicates the presence of a hazard that could result in a plant shutdown or personal injury.
Caution icon: It indicates the presence of a hazard that could result in corruption of software or damage to
equipment/property.
Information icon: It alerts the user to pertinent facts and conditions.
Tip icon: It indicates advice on, for example, how to design project or how to use a certain function.
NOTE The Note statement highlights important information pertaining to a particular descriptive text (for example: 'Module
description', 'Installation', 'Configuration', or 'Operational procedure', etc.) in the document.
Although Warning hazards are related to personal injury, and Caution hazards are associated with equipment or property
damage, it must be understood that operation of damaged equipment could, under certain operational conditions, result in
degraded process performance leading to personal injury or death. Therefore, fully comply with all Warning and Caution
notices.
2VAA000813-230 A 1
About This Book
2 2VAA000813-230 A
1. Introduction Overview
1. Introduction
1.1 Overview
Control logic documents form the basis of a process control strategy. A control logic document consists of algorithms called
function codes. Function codes can monitor analog and digital inputs, process data, communicate among themselves, and
send control signals to external devices. A process control system may involve one or more controllers residing in one or
more control units. Function codes are also available to facilitate communication between controllers either in the same or
different control units or control networks. Exception reporting function codes output point data onto the Symphony network
and are able to be monitored by the human system interface (HSI) nodes if the point is defined as a tag.
The Automation Architect window provides a means of developing and editing control logic documents using graphical
representations of function code algorithms and their interconnections. The function codes and other graphic elements are
actually inserted or drawn on sheets which make up a control logic document. Typically, a control logic document is made
up of a number of sheets in which each sheet contains a portion of the configuration. Sheets can also contain graphic
elements which are used for documentation purposes. However, documentation elements are not actually part of the
configuration.
The Automation Architect window can also be used to monitor and tune a process control system using the monitor/tune
mode of operation. In this mode, live function code values from the controller are displayed in the configuration sheet.
Tunable parameters can be adjusted and the process values can be monitored while making adjustments.
1.2 Features
Standard Windows Functionality: The Automation Architect, just like all parts of Control Engineering, uses standard
Windows® practices such as toolbars, pull-down menus, etc.
Single Tag Data Input: Tag data needs to be entered only once because Control Engineering and all its parts use a single
common tag database.
1.3 Intended User

This instruction provides the necessary information to use Automation Architect to create and edit controller configurations
(control logic documents). It is not a tutorial for process control and assumes the reader has knowledge of graphics-based
process control systems. It is intended for personnel with human system interface and controller configuration experience.
This instruction further assumes the reader is familiar with Windows operating systems.
1.4 Instruction Content

This instruction contains seven sections. It includes a Table of Contents, List of Figures, List of Tables, and Index giving
several options to locate specific information quickly. Appendices supplement information presented in the individual
sections. The sections and appendices that make up this instruction include:
Introduction
Describes the contents of this instruction and its intended user. It also highlights some Automation Architect features.
Controller Configuration Overview

Explains the general controller configuration procedure, Automation Architect window, and how to use it.
Configuration Components
Details the component parts of a control logic document and how to insert or draw them.
Editing Configurations
Describes how to select and edit the parts of a configuration. Also given are instructions on forming shapes, macros,
borders, and control logic templates.
Monitor/Tune Configurations
Explains how to use the monitor/tune mode of the Automation Architect to tune an executing configuration and see the
results of changes in real time.
Example Configuration
Details the configuration of a simple control logic document.
Standard Entities
Lists and describes the entities in the exchange folders for use by Automation Architect.
2VAA000813-230 A 1-1
How to Use this Instruction 1. Introduction
CLD Lockable Properties

Details the control logic entity properties that will be CLD locked when the entity is CLD locked and which properties can be
locked individually.
1.5 How to Use this Instruction

To attain optimum use of all available features and functions, it is important to become familiar with the entire contents of
the instruction before configuring a control logic document.
This instruction limits the information presented in each section to only specific items required to complete the desired task.
The organization enables finding specific information quickly, and permits using this instruction as a reference after
becoming fully familiar with the Automation Architect window.
To use the instruction:
1. Read Section 2, Controller Configuration Overview for an overview of the configuration process and the
Automation Architect window.
2. Read for Section 3, Configuration Components a description of control logic document parts and how to insert or
draw them.
3. Read Section 4, Editing Configurations for instructions on how to edit previously drawn or inserted parts of a
control logic document.
4. Read Section 6, Monitor/Tune Configurations for a description of how to monitor or tune a configuration that is
executing in a controller.
Read the notes in text. Notes provide:
• Additional information.
• Information that should be considered before performing a certain operation or function.
1.6 Document Conventions

This document uses standard text conventions to represent keys, display items and user data inputs:
Display item
Any item displayed on a screen appears as italic text. Example:
Running
User data input

Bold - Identifies any part of a command line that is not optional or variable and must be entered exactly as shown.
Italic - Identifies a variable parameter entered in a command line.
[ ] - Indicates an optional parameter; text within the brackets follows the previously described conventions.
Example:
CUP [port] [baud] [file_name.CSP]

SPECIAL KEYS - Identifies a specific key that is not alphabetic, numeric or punctuation. Examples:
Press ENTER.
Press ESC V M. (Press and release each key in sequence.)
Press CTRL-ALT-SHIFT-DEL. (Press all keys in sequence without releasing any one key until you
have pressed them all.)
File names
Name - Indicates a file or directory name.
Example:
file1.exe
c:\new
Revision variable
A ? indicates a value that may change depending on the version of an item. Example:
Part number: 1234567?0

Part number: 1234567??
1-2 2VAA000813-230 A
1. Introduction Glossary of Terms and Abbreviations
1.7 Glossary of Terms and Abbreviations

Table 1-1 is a glossary of terms and abbreviations used in this instruction. It contains those terms and abbreviations that are
unique to ABB or have a definition that is different from standard industry usage.
Table 1-1: Glossary of Terms and Abbreviations
Term Definition
Controller Directs field processes e.g. S+ SD Series controller (HC800, SPC800,

SPC700, SPC600) and S+ Rack controller (BRC410) for Harmony control
systems.
Control Logic In S+ Engineering Control Engineering, a CLD is a grouping of sheets

Document (CLD) containing control logic (usually with a similar purpose). A controller
configuration usually contains many control logic documents to implement
the control strategy for its connected I/O.
Control Logic In S+ Engineering Control Engineering, a CLT is a Preconfigured logic

Template (CLT) configuration document used to simplify the creation of a new control logic
document. A control logic template, when dragged into a controller, creates
a new control logic document that is identical to the template and that can
be linked to the CLT so that changes to the CLT can be automatically
pushed to all linked CLDs, saving time and effort.
Control Network Data communication highway. In Field Engineering, the DP-Net connects
the PROFIBUS slaves. In Control Engineering, the control network consists
of control units and controllers, PN800 network for S+ SD series controllers
and associated I/O modules, and INFI-NET network for S+ Rack controllers
and associated I/O modules.
Exchange The Exchange in Control Engineering is a project-wide repository of system

and user-defined reusable components (symbols, shapes, macros, and
documents). These components are organized into folders.
Function Code For Harmony systems, a function code represents an instance in the
controller of an algorithm that provides specific functions. These functions
are linked together to form the control strategy.
Harmony Control A control network node that contains controllers. The HPC800 is a control
Unit (HCU) unit consisting of a CP800 that connects to the control network, and one
HC800 controller. The SPC600, SPC700, and SPC800 are also control
units. Traditional Harmony systems' control units consist of NIS/NPM
modules and several controllers.
Human System Combined hardware and software entity (sometimes just a software
Interface (HSI) application) used by operators to monitor and control the process control
system.
Project The largest grouping of configuration information (displays, control logic

documents, etc.) for a process.
Sheet The actual pages of a control logic document on which control logic is
inserted.
1.8 Reference Documents

The instruction provides information about Automation Architect and its options. Table 1-2 lists additional documents that
relate to the software.
Table 1-2: Reference Documents
Number Document
2VAA000812* S+ Engineering 2.3 Harmony engineering User manual
2VAA000844* S+ Engineering Function code reference User manual
2VAA000813-230 A 1-3
Reference Documents 1. Introduction
Table 1-2: Reference Documents (Continued)
Number Document
2VAA001978* S+ Engineering 2.3 Automation interface User manual
2VAA005210-230 S+ Engineering 2.3 Third party software licenses Reference manual
1-4 2VAA000813-230 A
Controller Configuration Overview Introduction
2. Controller Configuration Overview

2.1 Introduction
This section provides general information on controller configuration. It also provides information about Automation
Architect window capabilities and operating modes.
The following figure displays the Automation Architect window:
Figure 2-1: S+ Engineering Automation Architect Window
2.2 General Configuration Procedure

The following steps provide a general procedure for creating a S+ Engineering project with a controller configuration:
1. Launch S+ Engineering and navigate to Project Admin to Create a New project PLANT_ONE.
2. Click OK, to OPEN the PLANT_ONE project.
3. Once the PLANT_ONE project is created and opened, navigate to Application Engineering ->Control
Engineering.
4. At the project level, Right-click at the project level
5. Select New > Control Network.
6. In the dialog-box, type: NETWORK_ONE, as PN800 network.
7. Click OK.
8. Right-click the control network (NETWORK_ONE).
9. Select New > HPC
10. In the name field, type: HCU_ONE
11. Click OK.
12. At the HPC controller, Right-click at the controller Select Properties
13. In the name field, type: CONTROL_ONE An HPC800 is added with a controller named CONTROL_ONE.
14. Right-click the controller (CONTROL_ONE).
15. Select New > Logic Document.
16. In the name field, type: CLD_ONE
17. Click OK.
2VAA000813-230 A 2-1
Exchange Controller Configuration Overview
18. Open the control logic document CLD_ONE. This opens the Automation Architect window.
19. Configure the sheets of the control logic document using templates, macros, function codes and signal lines
using the information provided in this instruction.
20. Repeat Step 9 through Step 13 for all control logic documents required by the controller.
21. Right-click the controller (CONTROL_ONE) Select Compile to create a configuration file for this controller.
22. Right-click the controller (CONTROL_ONE) select Runtime -> Load to Controller to download the controller
configuration file to the actual controller.
23. Put the controller into EXECUTE mode and test the controller configuration logic.
NOTE: User must not use the following special characters in CLD names. They will cause errors with the Pack
and Unpack functionality. The messages output from the pack operation identify the control logic documents that
packed successfully as well as control logic documents that failed to pack.The packed file (EPG file) and control
logic documents with valid characters are exported. If a pack operation failed to pack a control logic document,
the unpack operation will fail.
/ (forward slash)
\ (back slash)
“ (double quotes)
* (asterisk)
| (pipe)
: (colon) NOTE: If a colon is used in a CLD name, the pack operation appears to be successful but it is not.
< (less than)
> (greater than)
? (question mark)
& (ampersand) NOTE: If an ampersand is used in a CLD name, the pack operation is successful, however, the
Publish CLD operation for View and Monitor will not function as expected.
NOTE: If a control logic document contains a special character, the special character may cause an issue when
publishing control logic documents for View and Monitor functionality.
2.3 Exchange
The exchange is a project-wide repository for most of the control logic document configuration information. It contains
folders, both system and user-defined, that contain the components used in control logic documents. These components
range from standard symbols, shapes, borders, and macros (in system folders) to customized symbols, shapes, borders,
macros and control logic templates (in user-defined folders) stored by the customer. Components are dragged from the
exchange to the Automation Architect document window.
Refer to Section A, Standard Entities for a description of the entities included in the system folders on the exchange. Refer
to Section 4, Editing Configurations for information on creating shapes, macros, borders, and control logic templates for a
non-system folder.
NOTE: Each object copied to the exchange must be given a unique name before another copy of the object is added.
2.4 Tag Assignment

Single point tag data entry means that tag data need only be entered in one location. For example, since the exception
reporting function codes have an address needed by the tag definition in the tag database, this information can be taken
directly from the function code, instead of entered manually into the tag database. Automatic tag synchronization insures
that when changes are made to tag data in one location, it is updated in other locations using the tag data.
Tags can be assigned to and removed from exception reporting function codes by right-clicking the function code and
selecting Assign Tag or Unassign Tag from the pop-up menu.
When a tag is assigned, an existing tag can be used or a new tag defined. If a new tag is defined, Automation Architect
adds the tag to the tag database along with the tag name, description, addressing information, and control logic document
information.
Once a tag is assigned to an exception reporting function code, Automation Architect gets the tag name and description
from the tag database each time the control logic document is opened. The tag name and description can be fully edited
through Automation Architect.
NOTE: For 800xA for Harmony and S+ Operations 1.x/2.x, an Edit Tag operation is available.
NOTE: For S+ Operations 3.x, an Edit Tag operation is not available, however, the tag can be edited using Signal Man-
ager or the Operations Engineering View.
2-2 2VAA000813-230 A
Controller Configuration Overview CLD Editing Modes
If a tag name is assigned to an exception reporting function code, then each time the control logic document is opened the
tag database is automatically updated with the address and control logic document name from the function code tag
assignment, and the tag type is verified.
A tag can be removed from a function code in three ways. Simply unlinking the tag is one way. Another way is to delete it if
it is not contained in a human system interface tag list. The final way is to delete the tag no matter where it is used. When
removing tag links during editing, the tag is immediately unlinked from the function code regardless of the remove tag link
option settings. When deleting a tag, it is not physically deleted from the database until the document is saved.
The Automation Architect issues a warning when closing a control logic document that has not been saved after tags are
assigned or deleted.
2.5 CLD Editing Modes

Using Automation Architect an engineer can edit a control logic document in two ways or modes: off line and online. Both
modes display the control logic document configuration in a graphical format. Monitoring and tuning cannot be performed in
the off line mode. Configuration can be performed in the online mode. However, changes other than in tunable
specifications are not reflected in the controller until the control logic document is compiled and downloaded.
Offline
Mode in which control logic document configurations are normally created. When a control logic document is opened, the
Automation Architect enters this mode automatically.
Online
Permits the monitoring and tuning of function code blocks. When this mode is entered, the function code block values are
updated with actual values from the controller. Tunable parameters can be tuned in this mode. To use this mode, the
Control Engineering software must be communicating with the Symphony network and the configuration to be monitored
must have been previously downloaded to the controller. Refer to Section 6 for information on monitoring and tuning a
configuration.
2.6 Automation Architect Window Menus

The following paragraphs briefly describe each Automation Architect menu.
File
Contains items to save, revise, close, print, and open previous document or open next document. Refer to Document
Operations.
Edit
Contains items to edit and modify entities, select entities by various methods, undo commands, redo commands, and
repeat commands. Refer to Section 4 contains items to manipulate sheets. Refer to Section 3.
View
Contains items to control the display of the exchange, toolbar, status bar, and sheet (refresh, zoom, etc.). Refer to
Document Workspace contains the monitor/tune mode toggle. Refer to Section 6.
Tools
Contains items to insert and draw entities. Refer to Section 3. Contains items to magnify sheets, measure distance, set
window display attributes, default character size, grid attributes, layer attributes, signal attributes, and pan lock. Refer to
Document Workspace.
Window
Contains an item that creates a new window accessing the same document. Refer to Multiple Document Windows.
Contains items to manage the document windows.
Help
Contains items to access help. Refer to Document Operations.
Other important functions such as those used to edit and modify entities, assign and delete tags, etc. are available in a pop-
up menu displayed when right-clicking an entity. Refer to Section 4.
2.7 Document Operations

This topic describes how to open, save, print, revise, and close control logic documents being edited in the Automation
Architect window. Environmental Properties Tools -> Options General tab provides property selection to define the
maximum number of control logic documents open (Refer to Section 2.9.2).
2VAA000813-230 A 2-3
Open Controller Configuration Overview
2.7.1 Open
Control logic documents, control logic templates, shapes, borders, and macros are opened from the Control Engineering
window.
To open one of these documents, double-click the name or right-click the name and select Open from the pop-up menu.
Refer to the Primary Interface instruction for more information.
When launching Automation Architect to display a CLD from Control Engineering, the Automation Architect window may not
be brought to the front, but the task on the task bar will instead flash. Locate the task on the task bar and OPEN to view the
CLD in the Automation Architect window.
2.7.2 Save
A document can be saved at any time. The saving of documents regularly is recommended in order to prevent loss of data.
To save a document, select File > Save.
2.7.3 Print
Control logic documents can be printed from the Control Engineering and Automation Architect windows. Selective printing
of the whole document or a range of sheets within the document is possible (File > Print > File) as is the ability to print just
the viewable area of the active sheet only (File > Print > View). Refer to the Primary Interface instruction for detailed
information about printing control logic documents.
2.7.4 Revise
Revisions are snapshots of the control logic document. A number of revisions of the same control logic document can be
maintained as an archive or as a backup while testing changes to the configuration.
To create a new revision of a control logic document, select File > Show History and then select the Generate Revision
operation. A snapshot of the present document is saved with the present revision level. The revision level of the opened
control logic document is incremented by one.
2.7.5 Close
When the editing of a control logic document is complete, select File > Close. If the document contains unsaved changes, a
prompt appears to notify that it should be saved before closing.
2.7.6 Document Modes

Control logic document, control logic templates, and macros can have two modes of access. These modes are read/write
and read only.
Read/Write Access
Occurs when opening a document that is not currently opened. This document is fully editable.
Read Only Access

Occurs when trying to open a document that is already opened by another client. During the opening process the following
message is displayed.
File_Name is currently locked by another user. Do you wish to open the document Read Only?
Click Yes in the dialog box and a read only copy of the document is opened. Entities can be selected, their property pages
can be viewed, and they can be copied to the clipboard, but no changes can be made to the document.
2.8 Multiple Document Windows

More than one document window (each containing a single control logic document) can be opened at a time. Also,
Automation Architect provides the capability to open multiple windows containing the same control logic document. These
windows are dynamically linked so changes made in one window are present in all windows. Each window can be
manipulated just like the original window using standard Windows functions. To open a window containing the same control
logic document that is in the active window, select Window > New Window.
2.9 Document Workspace

The document workspace refers to that area of the document window excluding the menu bar and scroll bars. The
workspace has a relative coordinate system extending from 0;0 to 10,000;10,000. A border should be inserted into the
sheet to contain all the configuration entities (refer to Section 3). The document workspace can be zoomed and panned to
2-4 2VAA000813-230 A
Controller Configuration Overview Toolbar
gain a better view of any area of interest; for example, to have finer control when drawing, inserting, or editing entities. Refer
to Magnify, Pan, and Refresh the View for more information.
The coordinate system is used as an aid in drawing, inserting, sizing, and positioning entities by defining a display grid. The
grid is set to some multiple of the coordinate units and is the finest resolution at which entities can be positioned. The
display of the grid can be toggled on and off. Refer to Grid for more information.
2.9.1 Toolbar
The toolbar provides an alternate and more convenient method of selecting a tool for drawing and inserting entities. All the
commands that draw or insert entities on the sheet and perform commonly used functions are represented by an icon on
the toolbar. The toolbar is shown in Figure 2-2.
Figure 2-2: Automation Architect Toolbar
2.9.2 Environment Properties

The environment refers to properties of the Automation Architect workspace that can be customized or set to default values.
These Automation Architect environment properties can be saved as User Preferences. Some of the properties belong to
the sheet and remain in effect for the current editing session or until changed by the user. Other properties affect all the
sheets in a control logic document. Most of the settings that control the environment are reached through the Tools >
Options selection. Once selected, a dialog box of nine tabs is presented. Refer to Figure 2-3.
General
CLD Navigation: Property selection to set the maximum number of control logic documents open in Automation Architect
and prompt before closing when exceeding the maximum number. The user can define the number of control logic
documents that can be opened simultaneously. If the number of control logic documents exceeds the maximum number,
then the first opened control logic document will be closed (if no changes made). If any changes made in the first control
logic document, then the user can either save (or discard) the changes to open new control logic document or cancel
closing the first control logic document on confirmation window.
Prompt before closing when exceeding maximum number of CLDs open is defaulted at enabled. When enabled, the user
will be warned with an additional prompt that the number of control logic documents opened is exceeded and that the first
control logic document will be closed.
CFC: Property selection to enable Configurable Function Code (CFC) White Box functionality. When the double-click CFC
opens Internal Logic property is enabled, the Internal Logic Document (ILD) window is displayed when the user double
clicks the Configurable Function Code. This Internal logic document is read only.
Figure 2-3: Tools Options General Tab
2VAA000813-230 A 2-5
Environment Properties Controller Configuration Overview
View
Show General: Property selection to set what is displayed in a sheet of a control logic document. These properties affect
the current sheet and can be set differently for each sheet in the control logic document. General items include the grid,
attributes, symbol origins, template linking, text, connection references, and tool tips. When hovering over a function code,
the tool tips display function code type, block number, tag name, tag description, and function code specifications.
Show Function Codes: Property selection to show function code specification values, specification descriptors, tag name,
tag descriptor, specification spares, and specification display location. Setting the specification display location is a global
setting for all function codes configured in the control logic documents. There are eight options available for the
specification display location. The default specification display location is BOTTOM-CENTER.
Auto Scrolling: Property selection to enable or disable auto scrolling.
Auto Output Window: Property selection to enable or disable auto output window.
Text Sizes: Property selection to set the text sizes for specifications and tag information.
Monitoring Colors: Property selection for setting the colors for good, error, bad, quality, alarm, disabled, calibration,
tracking, line0, and line1.
Template Linking Colors: Property selection for setting template linking colors for locked, linked, and controlled.
Figure 2-4: Tool Options View Tab
NOTE: In a control logic document, the user can override the specification display location for a function code using the
function code Property Dialog Object tab.
2-6 2VAA000813-230 A
Controller Configuration Overview Environment Properties
Figure 2-5: Override Specification Display Location per Function Code
NOTE: See below a section of a control logic document where View Show properties are set to display specifications at
the bottom left and tool tips is enabled.
Figure 2-6: Tools Options View Show Property Example
Edit
Defaults for All Sheets: Property selection to set the edit color for a selected entity for all sheets in control logic
documents.
Defaults for This Sheet: Property selection to set the layer, line style, line width, and character size defaults for a sheet in
a control logic document. These are global settings global setting for logic configuration in the control logic documents. The
2VAA000813-230 A 2-7
line style affects the “Line” entity only. There are four options for line style. The line width affects both the “Line” entity and
“Signal” entity. There are four options for line width.
Figure 2-7: Tools Options Edit Tab
NOTE: In a control logic document, the user can override the line entity width using the Property Dialog Object tab.
Figure 2-8: Override Width Selection for Line Entity
2-8 2VAA000813-230 A
Grid
Property selection to set the grid spacing, snap to grid, and grid style in a control logic document. Refer to Grid for more
information. The grid spacing and snap properties affect the whole control logic document.
Figure 2-9: Tools Options Grid Tab
Layer
Property selection for the visibility, selectability, and color of each layer. Visibility refers to when entities drawn on a layer are
viewable. Enabling the visibility of a layer means it is always visible. Disabling the visibility means the layer is only visible
when it is the current layer. Selectability refers to the ability to select entities on a layer. Enabling the selectability of a layer
means entities on the layer can be selected. Disabling the selectability of a layer prevents entities from being selected. An
entity can be added and edited but only until another entity is added or the layer is changed.
Property selection for the background color of control logic documents, the exchange, and read-only control logic
documents.
Layer is a property of an entity that helps organize entities on the sheets of the control logic document. Each entity is drawn
or inserted onto the current layer which is one of 16 layers. Layers can be made visible or not visible and selectable or not
selectable or any combination. If a layer is made visible, entities on that layer are visible; otherwise they are not visible. If a
layer is made selectable, entities on that layer can be selected; otherwise they cannot be selected. The selectable settings
allow precise control of which layers permit entities to be selected. An entity must be visible to be selectable. The current
layer is always made visible no matter how selectability is configured for the layer. Each sheet of a control logic document
can have its layer environment set independently of the others.
Entities with a common purpose can be inserted on the same layer. For example, assume that all documentation is inserted
on one layer and configuration entities are inserted on another. When making changes to the configuration, the
documentation layer could be made not visible or not selectable, or both. This would prevent inadvertently selecting a
documentation entity when trying to select a configuration entity.
The current layer is the layer on which new entities are drawn or inserted. To set the current layer, use the layer selection
box located on the toolbar.
2VAA000813-230 A 2-9
Figure 2-10: Tools Options Layer Tab
Function Codes
Removal of Associated (linked) Tags: Property selection to set the behavior for removing tag links from exception
reporting function codes. These options include unlinking the tag, deleting the tag unless it is used in a tag list, or deleting
the tag regardless. If a delete option is selected, the actual deletion from the tag database will occur when the document is
saved.
Pop-up Spec Page while Creating Function Codes: Property selection to enable or disable the display of the property
pages of newly inserted function codes.
Spec Page Options: Property selection for the specification filter used when editing a function code, the displaying of spare
specifications, and the automatic selection of the tuning filter (when tuning specifications).
2-10 2VAA000813-230 A
Figure 2-11: Tools Options Function Codes Tab
Signals
Property selection to set the default line style for analog and digital signals. The signal default line style is a global setting.
There are options for setting the style of the signal lines.
NOTE: The signal line width is set from the Tools Options Edit tab.
Refer to sections Line and Signal for more information.
Figure 2-12: Tools Options Signal Tab
NOTE: In a control logic document, the user can override the signal entity for line width using the Property Dialog Object
tab.
2VAA000813-230 A 2-11
Figure 2-13: Override Global Setting for Width Selection Signal Entity
Instant Trend
Property selection to set the behavior, display and color configurations relate with the Instant Trend function. Refer to
Instant Trend for more information.
Figure 2-14: Tools Options Instant Trend Tab
2-12 2VAA000813-230 A
See below an example of an Instant Trend display for a signal line. The Sample Interval property controls the X axis. The
Display Analog Range property controls the Y axis. The Colors property control the color scheme for the Instant Trend
display.
Figure 2-15: Instant Trend Example
Monitoring
Communication: Property selection to enable/disable Group Monitoring for faster function code updates when using the
Monitor and Tune feature to monitor values in a control logic document.
NOTE: There are limitations when group monitoring is enabled.
Figure 2-16: Tools Options Monitoring Tab
The symbol “G” is displayed at the bottom of a monitored control logic document when group monitoring is enabled.
NOTE: The selected Logical ICI and the status of the monitoring is also displayed.
2VAA000813-230 A 2-13
Saving and Restoring Environment Properties Controller Configuration Overview
Figure 2-17: Group Monitoring Example
General Functions
Buttons along the bottom of the Tools-> Options dialog are OK, Cancel, Apply, Save Settings, Restore Settings, and Help.
The Apply button enables the current settings while the Save Settings button makes the current settings the default
condition. These settings are stored and remembered for the next time the Automation Architect is started up. The Restore
Settings button changes the current settings to the default factory installed condition.
Figure 2-18: Tools Options General Functions
2.9.3 Saving and Restoring Environment Properties

The Automation Architect environment properties can be saved and restored as User Preferences. The file supported is a
“.gmc” type. A user can Import Preferences, Export Preferences, and Restore Preferences, as seen in the figure below. The
user can import or export their User Preferences for use on multiple machines or workplaces.
Follow the step for User Preferences:
2-14 2VAA000813-230 A
Controller Configuration Overview Magnify, Pan, and Refresh the View
1. Select Tools > Options > Import/Export/Restore Preferences.
Figure 2-19: Import/Export/Restore Preferences
2. Select Import Preferences option to import the User Preferences.

a. Browse the “.gmc” file in the Import File dialog box and then click OK.
b. When the file is imported, restart the application (GMC32.exe) for the changes to take effect.
3. Select Export Preferences to export the User Preferences.
a. Choose the export file location and name of *.gmc file type.
b. When the file is exported, take this file and import it into other systems or save.
4. Select the Restore Preferences option to restore the User Preferences to default settings.
a. If User Preferences need to be reverted, a predefined file imports default settings.
b. Select Yes when asked for confirmation.
2.9.4 Magnify, Pan, and Refresh the View

The following operations control the view of the control logic document sheets.
Magnify
Increases or decreases the view of the current sheet. To magnify a document window:
1. Select View > Zoom.
2. Select one of the six available magnifications.
NOTE: It is also possible to change the magnification to the next higher or lower standard magnification using the
+ or - magnifier toolbar buttons.
NOTE: The Zoom function does not change the view "BY xx%", but rather it changes the view "TO xx%".
Fit to Window
Fits the entire document area to the current size of the document window. This can be used after magnifying an area to
return to the original view or after resizing the document window. To fit the document to the document window, select View
> Zoom > Fit in Window.
NOTE: In the Automation Architect, string entities that are blank outside the border of a drawing can give the appearance
that fit to window does not work or the printing margins are incorrect. If this is suspected to be the case, this can be cor-
rected in several ways. One way is to select the suspect area outside the border via rubber band and delete invisible
empty text entities. Alternatively, the user can locate all empty strings by selecting select all entities and tabbing from
entity to entity.
2VAA000813-230 A 2-15
Mouse Scrolling Horizontal and Vertical Controller Configuration Overview
Magnifier Tool
Fits a windowed region to the document window. The magnifier works by defining a rectangular window that is magnified to
fit the document window. To magnify a document using the magnifier tool:
1. Select the magnifier button from the toolbar. The cursor changes to the magnifier cursor.
2. Position the magnifier at one corner of the window and drag the cursor to the diagonally opposite corner and
release the mouse button. The windowed area is magnified to fit the current size of the document window.
A windowed area can be zoomed out by defining the magnify window such that it extends outside the document window
(using auto-panning). The Fit in Window function also affects the magnification of the document.
Scroll Bars
Use the horizontal and vertical scroll bars (standard Windows functionality) to move the visible portion of the document
around the document window.
Auto-Scrolling
To scroll a document using auto-scrolling, point the cursor anywhere in the document window and drag the cursor to any
edge of the window. As the cursor reaches the edge of the window, the window pans toward that edge of the document.
This only works while drawing, moving, or sizing an entity or drawing a selection window. Choose Tools > Options and then
select the view tab to get to the auto-scroll check box.
Refresh
After performing drawing or inserting operations, stray graphics may occasionally litter the document. The refresh function
redraws the document and removes the litter. To refresh the document, select View > Refresh.
2.9.5 Mouse Scrolling Horizontal and Vertical

Horizontal and Vertical mouse scrolling is supported.
Vertical scrolling
For vertical mouse scrolling up and down, scroll the mouse wheel up and down, respectively.
Horizontal scrolling
For horizontal mouse scrolling, user must select shift + mouse scroll. To scroll left hold shift + scroll up, and to scroll right
hold shift + scroll down.
2-16 2VAA000813-230 A
Controller Configuration Overview Mouse Zooming In/Out
Page scrolling
User has the option to scroll a page at a time as shown below. User can do this in the Mouse Properties dialog box.
Figure 2-20: Mouse Properties
2.9.6 Mouse Zooming In/Out

User can now use mouse controls to zoom in and out. Every time a scroll is executed it will zoom in and out (+/-) ~10
percent. The maximum and minimum zoom is 400% and 10% respectively. This updates the zoom percentage combo box.
Figure 2-21: Mouse Zooming In/Out
The object or objects that are currently selected will be the target to zoom in and out. It centers the object and zoom in or out
on it. See the following figures.
2VAA000813-230 A 2-17
Mouse Zooming In/Out Controller Configuration Overview
Zooming In
To zoom in, user must select the control key + mouse scroll up.
Figure 2-22: Zooming In
2-18 2VAA000813-230 A
Controller Configuration Overview Mouse Panning
Zooming Out
To zoom out, user must select the control key + mouse scroll down.
Figure 2-23: Zooming Out
2.9.7 Mouse Panning

A new tool is added to Automation Architect that is Mouse Panning.
2VAA000813-230 A 2-19
Mouse Panning Controller Configuration Overview
Instantiation
To instantiate mouse panning, user must press the Spacebar. This gives an “Open Grab” cursor. User can move the cursor
around as long as the spacebar is down. This selects the original position that user wants the panning to start at.
Figure 2-24: Pan Mode Instantiated
Activation
Once the cursor has been instantiated, user can now start panning by pressing the left mouse button. Once pan mode
activates, it loads a closed hand cursor (see figure below). User can now pan inside or outside of the client window, and the
view will pan with the mouse movements. To stop panning, user has to deselect the left mouse button. If the space key is
still down, then the mouse gets back into instantiation mode.
2-20 2VAA000813-230 A
Controller Configuration Overview Fit to view Selected Objects
Figure 2-25: Pan Mode Activation
2.9.8 Fit to view Selected Objects

This works just like the ‘Fit in window’ option as shown in the following figure.
Figure 2-26: Fit window option
Instead of fitting to the entire window, it fits to the current object or objects selected in the view and make them fit the
screen. To get this option to work, first select an object and then press the control key + Double-click left mouse button. See
below for an example.
2VAA000813-230 A 2-21
Cursor Controller Configuration Overview
Figure 2-27: Fit to View Selected Object
User can do a control + double-click on mouse button anywhere on the screen, as long as user wants fit to page is selected.
If user wants to just ‘Fit to window’ without pressing the button, use the controls without having anything selected.
2.9.9 Cursor
The cursor is used to draw and position entities, to select entities for editing, and to move, size and otherwise edit entities.
The cursor is moved around the document workspace using the mouse in the standard Windows environment manner.
Depending on the tool selected or the action being performed, the cursor takes on different shapes. The default cursor is
the selection arrow. When a drawing tool or editing command is chosen, the cursor takes on the shape of the chosen tool or
a shape that represents the chosen command. Active drawing tools and editing commands can be terminated by right-
clicking the mouse (unless the current cursor position has a right-click menu attached to it) or selecting another tool. The
selection cursor becomes active after a tool or command is terminated.
The coordinates box in the lower right of the window gives the current cursor position in document coordinate units. If the
snap to grid functionality is enabled, cursor movement is restricted to the grid increment when inserting, drawing, or editing
entities.
The keyboard can also be used to move the cursor using the keyboard cursor keys. When using the keyboard, the space
bar performs a primary mouse button click and ENTER performs a double-click.
2.9.10 Grid
The grid can be used as an aid in positioning entities when they are drawn, inserted, or edited. This can be done in two
ways. Visually aligning the entity to the display grid is one way. Enabling the Snap to Grid option to force the entity to lie on
grid points is the other way. Functions from the view and grid tabs of the options dialog box (select Tools > Options) affect
the grid. After configuring the grid settings, click Apply to make them effective.
Grid Control
Sets the number of coordinate units between orthogonally adjacent grid points (spacing). If Grid Lock is enabled, the
drawing, inserting, and editing of entities is restricted to grid points. If Show Grid on the view tab of the options dialog box
(select Tools > Options) is enabled, the displayable grid points are displayed. Three presets are available: Grid 100/100,
Grid 20/20, and Grid 10/10. A fourth setting, Custom Grid, is user configurable.
Show Grid
Toggle that displays the grid. To enable the grid, select Show Grid on the view tab.
2-22 2VAA000813-230 A
Controller Configuration Overview Open Previous/Next Document
Preset Grid Spacing

To use one of the three preset grid spacings, select the desired spacing from Grid Spacing on the grid tab. The toggle grid
settings toolbar button (enabled when the grid is displayed) cycles through the three preset grid settings.
NOTE: As a general practice, it is best to insert function codes with the grid set to Grid 100/100 and to make signal con-
nections with the grid set to Grid 20/20.
Custom Grid Spacing

To set a custom grid spacing:
1. Select Custom on the grid tab.
2. Set the X axis grid spacing value (integers from zero through 100 are valid numbers).
3. Set the Y axis grid spacing value (integers from zero through 100 are valid numbers).
NOTE: The grid may not be displayed if the spacing on the display is determined to be too dense.
Snap to Grid
This is a toggle that confines entity drawing, inserting, and editing to the grid points. To enable this function, select Snap to
Grid on the grid tab.
Snap to grid works somewhat differently depending on the entity: line, polygon, and rectangle vertices must lie on the grid
points; circle and arc center points must lie on grid points; text string start points must lie on grid points; and symbol origins
must lie on grid points.
NOTE: Show Grid and Snap to Grid operate independently of each other.
Grid Style
Two types of grid patterns can be displayed. Patterns of points or solid lines are possible. Use the drop-down menu of the
Grid Style field to select the appropriate pattern.
2.9.11 Open Previous/Next Document

User can navigate to a previous or next document. Once user click on previous/next document #CLD button, it will open the
respective previous/next document #CLD available in the controller. If current document is the first/last document, then
appropriate message will be shown and respective previous or next document navigation will be halted.
Figure 2-28: Previous and Next Document Selection
2.10 Measuring Distance

The distance measure function measures the distance between two coordinate points in the document window.
To measure the distance between two points:
1. Select Tools > Distance Measure. The cursor shape changes to the distance measure tool.
2. Position the cursor at any point in the document window and drag to any other point. The status bar displays the
following information:
(x,y),|distance|
where:
x,y Distance (along each coordinate
axis) from the start point.
distance Distance between the two points.
2VAA000813-230 A 2-23
Measuring Distance Controller Configuration Overview
2-24 2VAA000813-230 A
Configuration Components Introduction
3. Configuration Components
3.1 Introduction
Describes the components that can be inserted or drawn on a sheet of a control logic document. It also explains how to
insert or draw these components.
3.2 Entities
The components that are drawn or inserted into a control logic document are referred to as entities. Certain entities are
used for documentation purposes only. They are not part of the configuration and are not used during compilation. This
includes arcs, circles, lines, rectangles, shapes, and text. Function codes, other configuration entities, and signal lines make
up the actual controller configuration. Complex entities include shapes, borders, and macros. A brief description of each
type of entity is given in the following paragraphs.
Entity Properties
Each type of entity has properties that can be defined and edited. All entity types have layer and entity attributes. Other
properties depend on the entity type. For example, a line has line style, function code has block number and specifications,
and cross-reference connectors have a descriptor. These properties all can be edited using the procedures given in Section
4, Editing Configurations.
Entity Attributes
Assigned to an entity using the attributes property page when the entity properties are accessed. They appear as text under
an entity and can be used in place of the text entity. The advantage of using entity attributes is that they remain connected
to the entity and do not impact the memory usage of a configuration. Refer to Section 4 for more information.
Border
Complex entity that surrounds all other entities forming a sheet within a control logic document. The border has a locator
grid, space for the drawing name and other documentation. Optionally, the border automatically fills in the control network,
HCU, and controller address. Standard borders reside in the border folder on the exchange. Borders can also be created by
the user and stored in a folder on the exchange. Refer to Border for information on inserting borders and a list of available
borders. Refer to Section 4 for information on creating a border.
Configuration
Used to make up the actual configuration that is downloaded to the controller. Refer to Configuration Components,
Constant Block, I/O Connector, Reference Connector, and Signal.
Documentation
Used for documentation purposes only. These entities are not part of the configuration loaded onto the controller. Refer to
Arc, Circle, Line, Rectangle, Shape, and Text for more information.
Macro
User-created collection of configuration and documentation entities referred to by a single name and saved as a single unit
in a folder on the exchange. When a macro is used, all of its configuration and documentation entities are individually added
to the active sheet. Refer to Macro for information on inserting a macro and Section 4 for information on creating a macro.
Standard I/O termination, Harmony control unit arrangement, and power wiring diagrams (in the form of macros) are
included in the Standard Drawings project located in the folder \Program Files (x86)\ABB Symphony
Plus\Engineering\Composer Harmony\SystemData\Source Projects. These macros are accessed by copying the project to
the backup folder and Upgrading the project using the Project Admin application. On project OPEN, the project exchange
contains folders which in turn contain these macros.
Signal
Appears as orthogonal lines in a sheet but is designed to connect function codes. Refer to Signal for detailed information.
Control Logic Templates

Standard drawings that contain commonly used control logic. These templates can be copied to a controller where they
become a control logic document that only needs minor modifications to suit a particular application. Templates are stored
in folders on the exchange. To list the available templates and for information on using them, refer to Control Logic
Templates.
System Shapes
Collection of entities referred to by a single name and saved as a single unit in the shapes folder on the exchange. System
shapes are documentation entities. The individual components of a shape cannot be edited after the shape is inserted into
a sheet. In order to edit components of a shape, the shape must be exploded. Once a shape is exploded, the individual
components are no longer associated. The shapes folder contains predefined system shapes. Refer to Appendix A:
Standard Entitiesfor a description of available system shapes. Refer to Shape for information on inserting a system shape.
2VAA000813-230 A 3-1
Drawing Entities Configuration Components
User Shapes
User-created collection of entities referred to by a single name and saved as a single unit in a folder on the exchange. User
shapes are documentation entities. The individual components of a shape cannot be edited while it is still a shape. Explode
can be used to separate a user shape into its component entities. However, once a user shape is exploded, it loses its
identity as a shape within the sheet. A user shape cannot contain compilable entities (that is, function codes). Refer to
Shape for information on inserting user shapes and Section 4 for information on creating user shapes.
3.3 Drawing Entities

Entities are drawn using their respective tools. The procedure for inserting or drawing an entity depends on the specific
entity. Information on drawing or inserting each type of entity follows. Brief help is given in the status line when inserting or
drawing an entity. Online help is also available for the entity commands.
After an entity is inserted, properties (layer, entity attributes, etc.) can be changed and it can be otherwise edited and
modified (cut, pasted, scaled, etc.). However, before an entity can be modified in any way, it must be selected. Refer to
Section 4 for more information about selecting and editing entities.
3.4 Arc
An arc is a primitive documentation entity defined by a center point, a start point, and an end point. To draw an arc:
1. Select Tools > Arc. The cursor shape changes to the arc cursor.
2. Position the cursor to mark the center point of the arc.
3. Drag the cursor to simultaneously size the arc and to define its start point. A circular shape appears with a radius
line as this is being done. The radius line defines the size of the arc and its start point.
4. Release the mouse button when the arc is sized and the start point is defined.
5. Drag the cursor to define the end point of the arc and release the mouse button when positioned.
NOTE: Use the Tools -> Options Edit tab to define the default line style and line width for an arc used in control logic doc-
uments.
NOTE: Use the line style pull down and width pull down to set a line style and line width when drawing an arc in a control
logic document different from the default line style and line width configured in the Tools -> Options Edit tab.
3.5 Border
Borders are containers for configuration and documentation entities. Each sheet within a control logic document should
have a border. All configuration entities must be placed within the boundaries of the border.
A border is a complex documentation entity that is used to put a page border on a sheet. The border contains a locator grid
and, depending on the type of border, border and controller information. The border locator grid can be used for
documentation and locating references between sheets. When a border is inserted onto a sheet, the appropriate border and
controller information is automatically inserted into the border.
A border should be inserted into a new sheet. It provides a convenient place to insert information such as the sheet name,
control logic document name, control network, HCU, and controller address, and customer information. Borders
automatically insert information such as the control network, HCU, and controller address. Any time the border or controller
information is updated, the border is automatically updated when the control logic document is opened.
Standard borders reside in three exchange folders (traditional borders, enhanced borders 1, and enhanced borders 2).
Borders can also be created and stored in user-created exchange folders. Borders are inserted, from the exchange, using
the standard Windows copy and paste functionality or by dragging and dropping the border onto a sheet. Refer to Section 4
to create a border. The following discussion lists and describes the standard automatic borders available in the enhanced
borders 1 exchange folder:
AVBORD
Vertical with the ABB logo.
AVGBORD
Vertical with the ABB logo, without control network, HCU, and controller addresses shown. Use in generic drawings such as
cabinet or power drawings.
AVBORDG
Vertical without the ABB logo.
AVGBORG
Vertical without the ABB logo, control network, HCU, and controller addresses.
3-2 2VAA000813-230 A
Configuration Components Circle
AHBORD
Horizontal with the ABB logo.
AHGBORD
Horizontal with the ABB logo, without control network, HCU, and controller addresses shown. Use in generic drawings such
as cabinet or power drawings.
AHBORDG
Horizontal without the ABB logo.
AHGBORG
Horizontal without the ABB logo, control network, HCU, and controller addresses.
NOTES:
1. Borders in the traditional borders folder are the same borders used in previous versions of Control Engineering.
2. Borders in the enhanced borders 1 and enhanced borders 2 folders are almost identical to traditional borders
except that the ABB logo is used, sheet and CLD names are in different locations, and revision data (date, com-
ment, designer, and reviewer) is automatically included and updated.
To insert a border:
1. Open the exchange folder containing the border.
2. Position the cursor over the border to be inserted.
3. Drag the border from the exchange to the sheet of the control logic document.
NOTE: The cursor represents the lower left corner of the border.
4. Release the mouse button to insert the border.
3.6 Circle
Circles are primitive documentation entities defined by a center point and a circumference point. To draw a circle:
1. Select Tools > Circle. The cursor shape changes to the circle cursor.
2. Position the cursor to mark the center point of the circle. Drag the cursor to size the circle.
3. Release the mouse button when the circle is sized.
NOTE: Use the Tools -> Options Edit tab to define the default line style and line width for a circle used in control logic
documents.
NOTE: Use the line style pull down and width pull down to set a line style and line width when drawing a circle in a control
3.7 Constant Block

Constant blocks are configuration entities giving a constant output such as 0, 1, or 100.0. The constant blocks are valid only
for certain types of controllers but all of them are in the shapes folder on the exchange. They are inserted by dragging and
dropping them from the exchange folder to the sheet or by using the standard Windows copy and paste functionality.
The following is a list of constant blocks available in the shapes folder of the exchange:
B0
Boolean zero (fixed block 0).
B1
Boolean one (fixed block 1).
R-1
Real negative one (fixed block 4).
R-100
Real negative 100 (fixed block 3).
R0
Real zero (fixed block 5).
R1
Real one (fixed block 6).
2VAA000813-230 A 3-3
Function Code Configuration Components
R100
Real 100 (fixed block 7).
RMAX
Maximum real number allowed: +9E18 (fixed block 9).
RMIN
Minimum real number allowed: -9E18 (fixed block 8).
SETBLK
Modifiable block number (IMLMM02 only).
ZERO
Integer or real zero (fixed block 2).
To insert a constant block:
1. Open the system > constant blocks folder on the exchange.
2. Position the cursor over the constant block to be inserted.
3. Drag the constant block from the exchange to the sheet.
NOTE: The cursor represents the origin of the constant block.
4. Release the mouse button to insert the constant block.
3.8 Function Code

Function codes are algorithms that are the basic components of the control strategy. The function code algorithms
manipulate data and are linked together to form a control strategy during the controller configuration process. Each function
code has a unique graphical representation. This graphical representation is the same as given in the S+ Engineering
Function code reference user manual (2VAA000844) which also gives a complete description of each function code.
Function codes are connected by signals (analog or digital) using the signal tool.
To insert and use a function code:
1. Open the function code folder on the exchange.
2. Position the cursor over the function code to be inserted.
3. Drag the function code from the exchange to the sheet.
NOTE: The cursor position represents the origin of the function code graphic.
4. Release the mouse button to insert the function code.

The function block number is set to undefined.
5. Right-click the function code.
6. Select Properties...from the pop-up menu.
7. Enter the desired function block number in the dialog box.
8. Do any of the following:
– Use Signal to connect the function code input specification to the function code originating the signal. If
necessary, use OREFs and IREFs for signals between sheets as discussed in Reference Connector. Use
the function codes listed in I/O Connector for signal connections between controllers. Branches can be
added to expand the number of allowable connections, refer to Signal for information.
– Fill in the remaining function code specifications, block number, and other attributes by right-clicking the
function code and selecting Properties... from the pop-up menu. It is not possible to enter function code
input specifications by right-clicking the function code and selecting Properties... unless the function code
receives information from another controller. Refer to the list of function codes in I/O Connector.
– If the function code is an exception reporting function code, optionally create a tag link to the tag database
by right-clicking the function code and selecting Assign Tag from the pop-up menu.
3-4 2VAA000813-230 A
Configuration Components Cross-References
In general, all function codes for a sheet can be inserted, then all the connections made, and then all the specifications and
block numbers specified rather than performing each step separately for each function code.
NOTE: It is recommended that duplicate object names not be assigned (via the object tab) to multiple function codes
within a CLD. The Automation Architect currently allows this. However, the automation interface will not present duplicate
names to user-written applications, the Power Tools, or Control Engineering's CLD export utility. Instead it generates a
name using the text function code appended with the object ID for the second through nth instance of a function code
with the same name. This means if a user takes the time to assign names to objects in the Automation Architect (and
some of those objects have the same name), the CLD extract will not present the correct object names to the user for
editing. In addition, even if the user has not edited the object names, the names generated during the extract will be writ-
ten back to the CLDs upon import.
3.9 Cross-References
Cross-referencing is the process of connecting two logic components located in different documents or on different sheets
of a single document using I/O connector or cross-reference entities. The cross-reference name property of these entities is
used to make the connections. Cross-reference connections between control logic documents and control logic templates
or macros are allowed but they are only functional in the instances of control logic templates or macros. The information
generated when making connections is used during controller compilation to validate the configuration and update input
specifications. The ability to open a document containing a reference entity that is connected to the selected reference
entity is also made possible by using this information. Still another function provided by this information is the ability to
display the monitored data value of an output reference at a position just below the corresponding input reference or
I/O connector.
I/O connector and cross-reference entities can be copied individually or in groups. When copied in groups, all
interconnections between the entities are also copied. The names of copied output and input references are automatically
appended with .Copy(n) where n represents the number of times it has been copied.
The general procedure for inserting an I/O connector or cross-reference entity is:
1. Open the exchange folder containing the entity.
2. Position the cursor over the entity to be inserted.
3. Drag the entity from the exchange to the document.
4. Release the mouse button to insert the entity.
5. Use a signal to connect the entity to the associated control logic entities.
6. Right-click the entity.
7. Select Properties from the pop-up menu.
8. If the selected entity is an I/O connector, select the attributes tab and enter the desired function block number.
9. Select the cross-reference tab.
10. Enter the desired cross-reference name or select one from the list provided. Select a column heading to sort the
list in ascending or descending order (the order alternates on each selection).
NOTE: The list contains the names of all the currently defined (both connected and unconnected) cross-refer-
ences available to the connector.
11. Click OK.

User must not use the following special characters in cross-reference names.
# (number sign)
% (percent)
* (asterisk)
? (question mark)
_ (underscore)
Cross-reference text, used to find the other end of the connection, is displayed in the following format:
MM.NNN.SSS
where:
MM Identifier of the controller containing
the I/O connector or cross-reference
entity. This is set on the property
page of the controller.
NNN Order (index) of control logic
documents within the controller.
2VAA000813-230 A 3-5
I/O Connector Configuration Components
SSS Number of the sheet containing the

entity.
The Automation Architect maintains a database for all the cross-references within the controller. This database is used to
generate the cross-reference index report for the controller. This document provides written documentation of all the cross-
reference database information and can be printed or copied to a text file using the print dialog box.
With one end of a cross-reference selected, it is possible to view the other end of the connection (in a control logic
document) using the cross-reference viewer function. To access this feature:
1. Select the entity at one end of a complete cross-reference connection.
2. Right-click the selected entity.
3. Select Connected References from the pop-up menu.
4. Select the desired cross-reference (the other end of the cross-reference connection) from the list provided.
Select a column heading to sort the list in ascending or descending order (the order alternates on each
selection).
5. Click Open CLD.
The appropriate control logic document is opened with the cross-reference selected and scrolled in view.
NOTE: As a side effect of automatically repairing cross-reference information, in some cases the compiler may indicate
that CLDs have missing IREFs or OREFs. Opening those CLDs in Automation Architect should repair the missing infor-
mation. Recompile the CLDs.
3.9.1 I/O Connector

Function codes may need to communicate across controllers in the implementation of a control strategy. The controllers
may be in the same or different HCU cabinets in the same or different control networks. Function codes called I/O
connectors are used to receive input from the source function code and pass it along to the destination function code. The
following function codes accept input from another controller:
FC 25
Analog input, same HCU node (AI/B).
FC 26
Analog input, different HCU node, same control network (AI/L).
FC 41
Digital input, same HCU node (DI/B).
FC 42
Digital input, different HCU node, same control network (DI/L).
FC 46
Digital input list, same HCU node (DIL), logic master module controller.
FC 63
Analog input list, same HCU node (AIL/B).
FC 64
Digital input list, same HCU node (DIL/B).
FC 121
Analog input, different control network (AI/I).
FC 122
Digital input, different control network (DI/I).
3-6 2VAA000813-230 A
Configuration Components Reference Connector
FC 178
Data acquisition analog input, control network (DAANG I/L), source is FC177.
FC 193
User-defined data import (DATAIMPT).
FC 201
Data Point Definition (IDPDEF)
FC 205
Analog Input List/CW800 (Periodic Sample).
FC 206
Digital Input List/CW800 (Periodic Sample).
FC 212
Data acquisition digital input, control network (DADIG I/L), source is FC211.
The I/O connector needs the source address as an input specification in order to receive inputs from function codes in
another controller.
These function codes have cross-reference data as a property. The cross-reference data includes a name which is used as
an aid in locating signal sources and destinations among sheets. The Automation Architect automatically fills in
specification values when the control logic document is compiled. When cross-referencing to an address (I/O connector
name is not known), the cross-reference specifications must be set manually.
3.9.2 Reference Connector

Reference connectors are used for the following purposes:
• OREF, IREFO, and IREF connectors are used to link a block input specification in a function code receiving a signal
from a function block output on another sheet within the same controller.
• OREF and IREFO connectors are used to link function block input specifications or block output to physical I/O
points on termination drawings.
• OREF, IREFO, and IREF connectors along with associated I/O connectors are used to provide cross-reference
information. The cross-reference information shows the controller, control logic document, and sheet of a
corresponding source or destination. The Automation Architect tabulates all the cross-references that are recorded
in the cross-reference index report. This report is used as an aid in locating signal sources and destinations.
• BDIN, BDIND, BDOUT, and BPB connectors are used in manually cross-referencing. These are typically used in
generating Boolean logic drawings.
NOTE: Only IREF, IREFO, and OREF connectors are used during compilation.
BDIN
Boolean control input, for logic drawings (not compilable).
BDIND
Boolean operator indications, for logic drawings (not compilable).
BDOUT
Boolean control output, for logic drawings (not compilable).
BPB
Boolean pushbutton input, for logic drawings (not compilable).
IREF
Input reference (off sheet signal connection).
2VAA000813-230 A 3-7
Example using Reference Connections to Connect Function Codes on Different Sheets in a CLD Configuration Components
IREFO
Left facing output reference. This is typically used on certain types of termination drawings.
OREF
Output reference (off sheet signal connection).
3.9.3 Example using Reference Connections to Connect Function Codes on Different Sheets in a
CLD
Within a sheet, connections between function codes are accomplished using cross-references or graphically drawn using
Signal. This forces the input specification for a function code to match the output block of the corresponding function code
that is sourcing the signal. However, most controller configurations require the use of multiple control logic documents
containing multiple sheets to draw the configuration. When using more than one sheet, references to function code inputs
and outputs across sheets must be made explicitly. Three symbols are used to make these references. They are IREF
(input reference), IREFO (an output that exits the left side of the page), and OREF (output reference). Each of these
symbols has an associated 32-character text name. Names given as part of an input reference are needed to locate the
corresponding output reference with the matching name in order to fill in the function code input specification. Output
references used in control logic templates and macros must be uniquely named within that document. Only output
references used in control logic documents contained in the same controller must be uniquely named within the project.
Connecting Function Codes on Different Sheets

To use input and output reference connectors:
1. If a signal goes off the sheet, insert an OREF on the right side of the sheet from the exchange folder and connect
it to the signal. (Use an IREFO for a signal that goes off the sheet on the left side.)
2. Enter a cross-reference name for the output reference.
3. Insert an input reference on the left side of each sheet that is to receive the output reference connection.
4. Connect each input reference to the appropriate function code input using a signal.
5. Give the input reference the cross-reference name given to the output reference.
3.9.4 Example using Reference Connections to connect Different Controllers, Same HCU Node
To receive a signal from another controller in the same HCU node:
1. Attach an output reference to the output of the source function code. Use an OREF for a signal that exits the
sheet on the right or an IREFO for a signal that exits the sheet on the left.
2. Enter a cross-reference name for the output reference. Refer to Reference Connector for more information.
3. Go to the destination sheet and insert an appropriate I/O connector.
4. Connect a signal from the I/O connector to the destination function code.
5. Give the I/O connector the same cross-reference name given to the corresponding output reference.
3.9.5 Example using Reference Connections to connect Different HCU Nodes or Different Control
Networks
To receive a signal from another controller in a different HCU node or different control network:
1. Attach an exception reporting function code to the source function code.
2. Attach an output reference to the output of the exception reporting function code. Use an OREF for a signal that
exits the sheet on the right or an IREFO for a signal that exits the sheet on the left.
3. Enter a cross-reference name for the output reference. Refer to Reference Connector for more information.
4. Insert an appropriate I/O connector into the sheet that is to receive the output reference.
5. Connect a signal from I/O connector to the destination function code.
6. Give the I/O connector the same cross-reference name given to the corresponding output reference.
3.9.6 Cross Reference Description Fields

Cross-references are enhanced to add two new description fields: “Description (Top)” and “Description (Bottom)”. The
maximum length of each description is 64 bytes.
Descriptions are displayed above entity as shown in Figure 3-1.
3-8 2VAA000813-230 A
Configuration Components Cross Reference Description Fields
Figure 3-1: Cross-Reference Descriptions
Users can configure Description Top and Description Bottom from right-click on the cross-reference entity > Properties >
Cross Reference tab. This information is stored as a part of cross-reference entity to CLD.
2VAA000813-230 A 3-9
Line Configuration Components
Figure 3-2: Description Fields
NOTE: The Description (Top) and Description (Bottom) are also displayed on the Instant Trend Display. The connect top
description and bottom description fields are combined with one string as displayed in Figure 3-3.
Figure 3-3: Combined Top and Bottom Description Values
3.10 Line
This includes single line segments, polylines, and orthogonal line segments used for documentation. Each line segment is
defined by a start and end point. These types of lines cannot be used to connect function codes (refer to Signal for lines that
do connect function codes).
Lines or polylines are primitive documentation entities defined by a minimum of two and a maximum of 100 vertex points for
a total of 99 segments per line entity.
NOTE: Use the Tools -> Options Edit tab to define the default line style and line width for all lines used in control logic
documents.
NOTE: Use the line style pull down and width pull down to set a line style and line width when drawing lines in a control
3-10 2VAA000813-230 A
Configuration Components Macro
Figure 3-4: Line Style and Width Style Drop Down
To draw a single line segment:

1. Define the line style and width.
2. Select Tools > Line. The cursor shape changes to the line tool cursor.
3. Position the cursor to mark the start point and click to anchor the line segment at this point.
4. Position the cursor to mark the end point of the line segment. As the cursor moves, the line rubber bands to fit
between the points. When positioned, double-click to fix the line segment between these points.
To draw a polyline:
1. Define the line style and width.
2. Select Tools > Line. The cursor shape changes to the line tool cursor.
3. Position the cursor to mark the start point and click to anchor the line segment at this point.
4. Position the cursor to mark the end point of the first line segment. As the cursor moves, the line rubber bands to
fit between the points. When positioned, click to fix the first line segment between these points.
5. Do any of the following:
– Continue drawing line segments, by continuing to position the cursor and clicking at each end point.
– Terminate the operation by double-clicking the end point of the last segment.
3.11 Macro
Macros are user-created complex configuration entities stored in a folder on the exchange. The macros system folder
contains some common macros. Custom macros are stored in user folders. Macros can contain documentation and
compilable entities. Exception reporting function codes residing in a macro can have tags assigned (linked) to them. These
tags (and the macro) are part of the exchange and can only be accessed through the function code. Also, these tags are not
viewable in the data browsers.
When a macro is copied, all information (tag linked function codes and cross-reference entities included) is also copied into
the document.
To insert a macro:
1. Open the folder containing the macro being inserted.
2. Drag the macro from the exchange to the sheet.
NOTE: The cursor position represents the origin of the macro graphic.
3. Release the mouse button to insert the macro.

4. If the macro contains function codes with defined function block numbers, a prompt will request a starting
function block number. This block number is used to calculate the function block numbers of all function codes in
the macro.
3.12 Rectangle
Rectangles are defined by two points in diagonally opposite corners.
To draw a rectangle:
1. Select Tools > Rectangle. The cursor shape changes to the rectangle tool cursor.
2VAA000813-230 A 3-11
Shape Configuration Components
2. Position the cursor to mark the first corner point and click.
3. Drag the cursor diagonally to the opposite corner. As the cursor moves, the rectangle rubber bands to fit
between the corners.
4. When the second corner is positioned, release the mouse button to anchor the second corner.
NOTE: Use the Tools -> Options Edit tab to define the default line style and line width for a rectangle used in control logic
documents.
NOTE: Use the line style pull down and width pull down to set a line style and line width when drawing a rectangle in a
control logic document different from the default line style and line width configured in the Tools -> Options Edit tab.
3.13 Shape
Shapes are collections of configuration entities. They cannot contain configuration objects such as function codes. System
shapes reside in a shapes folder on the exchange. User shapes reside in folders created by the user. Refer to Section 2 for
more information on using the exchange.
To insert a shape:
1. Open the folder containing the shape.
2. Position the cursor over the shape to be inserted.
3. Drag the shape from the exchange to the sheet.
NOTE: The cursor represents the origin of the shape graphic.
4. Release the mouse button to insert the shape.
3.14 Signal
Signals connect function codes and other compilable entities. Each entity has one or more connection points to which the
connections are made. Branches can be added to a signal to increase the number of connections to a function code or
other entity. The only limit to the number of branches that can be added is ability to select a location on the signal. Branches
can even be added to branches to provide as complex a signal path as needed. A maximum of two branches can be added
at one location. Each connection point has up to four connections. One connection of each point is automatically
designated the input, leaving three available output connections. Signals and branches can also be moved, refer to
Section 4 for more information.
NOTES:
1. Connected entities must have the same signal type (for example, Real or Boolean) to be compiled.
2. Signals do not automatically align to grid points. It is best to make connections with Grid Lock on and to insure
that the reference points of the entity align to the grid.
3. Signals are only drawn in orthogonal segments.
4. If a connected entity is moved, the connection remains and the signal routes itself to fit the repositioned entity.
5. Signals can only have a solid or dashed line style. The signal line style is configured using the Tools -> Options
Signal tab. The default line style for Analog Signals and Digital Signals is defined.
Connect Entities
To connect compilable entities:
1. Select Tools > Signal. The cursor shape changes to the signal cursor.
2. Position the cursor on an entity connection point and click. The signal will attach itself to the closest available
connection point if within close proximity (20 grid points).
3. Route the signal as desired by clicking to form orthogonal line segments.
4. Position the cursor on the connection point of the second entity and double-click. A signal made up of orthogonal
segments is drawn from one connection point to the other.
NOTE: The signal ends are shown as small unfilled boxes when connecting function codes that use compatible
signal types. The signal ends are shown as small filled boxes when connecting function codes that use incom-
patible signal types.
Partial Connections
To connect a signal line to one entity:
3-12 2VAA000813-230 A
Configuration Components Text
2. Position the cursor on one of the connection points and click. The signal will attach itself to the closest available
connection point if within close proximity (20 grid points).
3. Route the signal as desired by clicking to form orthogonal line segments.
4. Position the cursor at the desired sheet location and double-click to terminate the signal. A small dot marks the
end of the unconnected signal.
NOTES:
1. When rerouting a signal line, the unconnected end of the signal will remain anchored at its current location.
2. When moving the last segment of an unconnected signal, the end point will snap to the nearest grid point if Snap
to Grid is enabled.
The ends of unconnected signals can be merged with other unconnected signals producing complete signal paths. When
merging two unconnected signal ends, the signal attached to an output remains a signal while the other signal becomes a
branch. A branch point marks where they are merged together.
Connect to Signal End

To connect a compilable entity to a signal end, select the entity and move the desired connection point to the end of a grid
aligned signal end.
NOTES:
1. The signal end should be aligned to the grid to ease the connection process.
2. Connection points attached to the end of an unconnected signal end must be used to move the signal end
beyond the nearest grid location.
Branches
There are two methods of adding branches to any signal or branch. It is also possible to delete branches.
To add a branch (method one):
1. Right-click (at the desired branch location) the signal or branch.
2. Select Add Branch from the pop-up menu.
A connection point and short branch appear on the signal or branch where the new branch is added.
To add a branch (method two):
2. Position the cursor on the signal or branch (between end points) to receive the new branch and click.
3. Route the branch as desired by clicking to form orthogonal line segments.
4. Position the cursor at the desired end point and double-click.
To delete a branch:
1. Right-click the branch.
2. Select Delete Branch from the pop-up menu.
3.15 Text
Text is used for documentation purposes only.
To insert text into a sheet:
1. If necessary, define the text size.
2. Select Tools > Text. The cursor shape changes to the text cursor.
3. Position the cursor to mark the starting point of the text string and click. A text dialog box appears.
4. Type a text string, set its size and rotation, and click OK when done to insert the text into the display.
NOTE: The text dialog box supports the Windows clipboard cut, copy, and paste functions. These are activated
by clicking the secondary mouse button when in the text box.
3.16 Defining Tag and Trend Points

If point data is to be used by a human system interface as a tag or trend point, then that point must have an appropriate
exception reporting function code configured in the controller configuration. For a trend point, a trending function code must
also be defined. Refer to the S+ Engineering Function code reference user manual (2VAA000844) for a list of exception
reporting and trending function codes.
2VAA000813-230 A 3-13
Multiple Sheets Configuration Components
3.17 Multiple Sheets

Control logic documents and control logic templates are initially composed of only one sheet. Usually more than one sheet
is needed. The Automation Architect allows for the addition, deletion, renaming, and reordering of sheets.
Add a Sheet
To add a sheet:
1. Select Edit > Sheet > New.
2. Enter the sheet name (up to 32 characters) and desired border (optional) in the sheet properties dialog box. The
name will be validated for uniqueness with the document.
3. Click OK.
Delete a Sheet
To delete a sheet (except the last):
1. Select the tab of the sheet to be deleted.
2. Select Edit > Sheet > Delete.
Rename a Sheet
To rename a sheet:
1. Select the tab of the sheet to be renamed.
2. Select Edit > Sheet > Rename.
3. Enter the new sheet name (up to 32 characters). The name will be validated for uniqueness with the document.
Reorder Sheets
As sheets are added to a control logic document, they are put into an order. This order is initially equal to how they were
added. The original sheet is first in the order and is displayed when the control logic document is opened. The reorder
functionality allows this order to be altered by permitting the order of any sheet to be changed. To reorder the sheets of the
control logic document, select Edit > Sheet > Reorder. Change the sheet being viewed by selecting the appropriate tab
located in the lower left corner of the window.
The tabs along the bottom of the window that represent each sheet are color-coded to show the link status of the sheet:
• The tab text background color is white if the sheet is not associated with a template or it is the color designated in
the environment options if it is associated with a template.
• The tag text color designated in the environment options is used when the sheet is locked, controlled, or linked.
Black text is used when the sheet is not locked, controlled, or linked.
3.18 Control Logic Templates

Control logic templates are drawings that contain reusable control logic from which a copy is easily made. They are created
and stored in user folders on the exchange. To make a copy of a control logic template, drag it from the opened exchange
folder to the controller that will use it. After it is added to the controller, it becomes a control logic document. Refer to
Section 4 for more information about creating control logic templates.
3.18.1 Linking Functions

The control logic template linking feature within Control Engineering enhances the maintenance and management of control
logic in the following ways:
• Fully automatic upgrading of control logic documents to the latest revision of the template used to create it. This
upgrading includes addition, deletion, layout, and specification modifications of all template-based entities and
signals. This feature allows the Automation Architect to retrieve the latest versions of standard reusable logic
entities, etc. without impacting project-specific logic entities on the same document or sheet.
• Fully automatic restoration of control logic documents to the original revision of the template used to create it. This
includes addition, deletion, layout, and specification modifications of all template-based entities and signals. This
feature allows the Automation Architect to replace any corrupted reusable logic with the original logic without
impacting instance-specific logic entities on the same document or sheet.
• Template branching which allows custom versioning of a standard template and any subset of the documents
linked to it.
• Simple control logic document and sheet-level linking and unlinking. Linking enables upgrade and restore
operations (functions that transfer data from a control logic template to a control logic document.
3-14 2VAA000813-230 A
Configuration Components Linking Functions
• Ability to specify certain changes (entity deletion, position, specifications, etc.) to logic entities as controlled by the
template through Automation Architect property pages.
• Ability to lock out or prevent changes (entity deletion, position, specifications, etc.) to logic entities through
Automation Architect property pages.
• Simultaneous linking, unlinking, upgrading, and branching of multiple control logic documents sourced from a
common control logic template or controller.
• Simultaneous template control and CLD locking operations of multiple entities within a control logic document.
• Configurable mechanism for resolving conflicts between control logic template-based and control logic document-
based entities during upgrade and restore operations.
NOTE: Currently only signal connections utilize this mechanism.
• Configurable mechanism for the logging of upgrade and restore operations. Control logic document linking
operations may also be logged.
The background color and design of control logic document icons within the Control Engineering window are coded (in the
following manner) to identify the linking features that applied to it:
White
No template was used to create it and as a result no linking, upgrade, or restore features can be applied to the document or
entities contained within. The document is not CLD locked but sheets, entities, and properties of entities within the
document can be CLD locked.
White with a Key

No template was used to create it and as a result no linking, upgrade, or restore features can be applied to the document or
entities contained within. The document (including all contained sheets) is CLD locked.
Blue
A template was used to create it but it is not linked to the template. Data transfers from the template to this document are
unavailable. The document is not CLD locked but sheets, entities, and properties of entities within the document can be
CLD locked.
Blue with Chain Links

A template was used to create it and it is linked to the template. Data transfers using the upgrade and restore functions are
allowed. Sheets within the document may be individually linked or unlinked. The document is not CLD locked but sheets,
entities, and properties of entities within the document can be CLD locked
Blue with a Key

A template was used to create it and it is CLD locked. All sheets within the document are also CLD locked. Data transfers
from the template (using upgrade or restore functions) are prevented. Link status of document is not applicable.
2VAA000813-230 A 3-15
Linking Functions Configuration Components
3.18.1.1Availability
describes the functions that are available under template linking and the entities to which they apply. Their functions are
explained in more detail later. Section B, CLD Lockable Properties describes the properties of the control logic entities that
can be CLD locked or template controlled.
Table 3-1: Available Template Linking Functions
Window Entity Selection Method Functions1
Control Controller Right-click > Set overriding entity for use when resolving
Engineering Upgrade all CLDs2 CLD/CLT conflicts during upgrade.
Choose to maintain signal connections CLT and
CLD-based logic.
Choose to log upgrade actions, conflicts, and
errors to the output window.
Upgrade all linked CLD entities (in all CLDs in the
controller) to the latest CLT version.
CLD Right-click > Set overriding entity for use when resolving
Template Linking > CLD/CLT conflicts during upgrade.
Restore Choose to maintain signal connections CLT and
CLD-based logic.
Choose to log restoration actions, conflicts, and
Restore CLD entities to the CLT version to which it
was last updated (or created from).
Right-click > Choose to link and/or lock the CLD.

Template Linking View the name and version of the CLT that the CLD
was created from, last upgraded to, or last restored
to.
View the latest version of the CLT (on the
exchange) and notification if the CLD requires
upgrading.
Right-click > Set the overriding entity for use when resolving
Template Linking > CLD/CLT conflicts during upgrade.
Upgrade Choose to maintain signal connections CLT and
CLD-based logic.
Choose to log upgrade actions, conflicts, and
Upgrade CLD entities to the latest CLT version.
Control CLT Right-click > Select the list (CLD icons and names in ascending
Engineering Actions alphabetical order down left side), details (refer to
(continued) following explanation), icons, or small icons (CLD
icons and names in ascending order across top or
down left side) view mode.
View the name, address, order number, link flag,
and current CLT version number of all the CLDs
created from this CLT.
Sort the list by clicking the appropriate column
heading.
Link, unlink, upgrade, or branch the selected CLDs.
Right-click > View the name, version, description, source

Actions > History project, and source name of the current template.
View the complete version history of the template.
3-16 2VAA000813-230 A
Table 3-1: Available Template Linking Functions (Continued)
Window Entity Selection Method Functions1

Automation All Right-click > Set the template-controlled or CLD-locked object
Architect Properties > status.
Object tab > NOTE: Template controlled status can only be set
Object status field when editing the template. Locked status can
only be set when editing the CLD.
Right-click > Set the template-controlled or CLD-locked location

Properties > status.
Object tab > NOTE: Template controlled status can only be set
Location status when editing the template. Locked status can
field only be set when editing the CLD.
Function Right-click > Set the controlled (CLT) or lock status.

code Specifications > NOTE: Template controlled status can only be set
Object tab when editing the template. Locked status can
Sheet Edit > Sheet > Set the link, CLD-locked, and template-controlled
Template Linking > status.
Status... View the latest version of the CLT containing this
sheet (on the exchange) and the version of the CLT
from which this sheets was created of last
upgraded.
NOTE: Template controlled status can only be set
when editing the template. Locked status can
NOTES:
1. All functions do not apply to all entities and all conditions (linked, locked, etc.).
2. Use CLT actions dialog box to selectively upgrade CLDs.
3.18.1.2Control Logic Template and Sheet

The following guidelines describe setting the default link status in control logic templates and their sheets that will be
propagated to new control logic documents (and their sheets) created from this template:
• The option to link newly created control logic documents is disabled by default.
• Link status does not affect the control logic template itself.
• Link status selects the link status of all control logic documents subsequently created from the control logic
template. Previously created control logic templates are not affected.
• Each control logic template sheet has its own link status and controls the link status of that sheet in created control
logic documents that are linked. The document (and any contained sheets) created from a template are linked by
default. The link status of individual sheets can be enabled or disabled as long as the whole document is linked.
Unlinking a document also unlinks all sheets contained within.
• Link status at the sheet level set in the control logic template will only affect sheets in control logic documents
subsequently created from the template. Documents previously created from this template are not affected.
3.18.1.3Control Logic Document
Link Status
The following guidelines describe the effects of setting the link status of a control logic document:
• All sheets contained within an unlinked control logic document are also unlinked.
• Re-linking a control logic document causes the link status of all contained sheets to be restored to their values as
they were before the control logic document was unlinked.
CLD Lock Status

The following guidelines describe the effects of setting the CLD lock status of a control logic document:
2VAA000813-230 A 3-17
• All sheets contained within a CLD locked control logic document are also CLD locked.
• Unlocking a control logic document causes the CLD lock status of all its contents to be restored to their values as
they were before the control logic document was CLD locked.
3.18.1.4Control Logic Document Sheet
Link Status
The following guidelines describe the effects of setting the link status of a sheet:
• The sheets in template-created control logic documents have their own link status.
• Linking a control logic document will not link the contained sheets.
• Unlinking a control logic document will unlink the contained sheets.
• Re-linking a control logic document causes the link status of all contained sheets to be restored to their values as
they were when the control logic document was unlinked.
3.18.1.5CLD Lock Status

The following guidelines describe the effects of setting the CLD lock status of a sheet:
• The CLD lock status of a sheet can be changed if the control logic document containing it is not CLD locked.
• CLD locked control logic document sheets can not be deleted.
• All entities in a CLD locked sheet are also CLD locked.
• Unlocking a sheet causes the CLD lock status of all the contained entities to revert back to the status it had before
the sheet was CLD locked.
Template Control Status

The following guidelines describe the effects of setting the template control status of a sheet:
• To enable the template control status of a control logic document sheet, enable the template control status of the
corresponding sheet in the control logic template used to create it.
• Linked and template controlled sheets within a linked control logic document can not be deleted.
Upgrade/Restore Actions
The following guidelines describe upgrade and restore actions and concerns that are unique to control logic document
sheets:
• Control logic template sheets not in the control logic document will be added with the link status and template
control status being identical to that of the corresponding template sheet.
• Linked and template controlled control logic document sheets will be deleted when the corresponding control logic
template sheet is deleted.
• Locked or unlinked sheets can not be updated or restored.
• A new version of the control logic document should be created before it is updated or restored to avoid accidental
loss of custom logic.
3.18.1.6Entity
CLD Lock Status

The following guidelines describe CLD lock status operation:
• The CLD lock status of an entity can be changed only if the sheet containing it is not CLD locked.
• A CLD locked entity can not be deleted.

The following guidelines describe template control status operation:
3-18 2VAA000813-230 A
• The template control status of an entity and the sheet containing it are independent of each other.
• The template control status of an entity is disabled in unlinked control logic documents or sheets and restored in re-
linked control logic documents or sheets.
• The template control status of all control logic document entities created from the control logic template are
upgraded during control logic document upgrade operations. As a result, previously uncontrolled entities may
become controlled if the entities are template controlled in the control logic template.
• Template controlled entities cannot be deleted from a control logic document.
The following guidelines describe upgrade and restore actions and concerns that are unique to entities:
• Entities added to control logic templates will be added to linked and unlocked control logic documents when they
upgraded. Template controlled status of the entities will be identical to that of the template entities.
• Template controlled entities will be deleted from unlocked control logic documents being upgraded if they have
been deleted from the control logic template.
• The restore operation will not remove control logic entities not present in the control logic template.
• The template control status of properties (location) and specifications of function codes and cross-references are
independent of each other.
3.18.1.7Property
CLD Lock Status

• The CLD lock status of the location property of an entity can be changed only if the entity is not CLD locked.
• Control logic document entities with a CLD locked location property can not be moved.

• Entities whose location property is template controlled can not be moved.
• The template control status of the location property of an entity is independent of the template control status of the
entity.
The location of control logic document entities will be upgraded/restored if the control logic document sheets containing the
entities are linked, not CLD locked, the entities themselves are not CLD locked, and the location property of the entities is
template controlled.
3.18.1.8Function Code Specification
CLD Lock Status

• The CLD lock status of function code specifications can be changed at any time and overrides the template control
status.
• The CLD lock status of control logic document function code specifications can be changed only if the function is
not CLD locked.
• Enabling the CLD lock status of a function code locks all its specifications as well.
• In the function code property page, the Value field data is blue for CLD locked specifications.
2VAA000813-230 A 3-19

• The template control status of control logic template function code specifications is independent of the function
code template control status.
• In the function code property page, the Value field data is read for template controlled specifications.
The value of control logic document entity specifications will be upgraded/restored if the control logic document sheets
containing the specifications are linked, not CLD locked, and the corresponding entity specifications are template controlled
and not CLD locked.
3.18.1.9Template-Controlled Signal Behavior
General
The following general guideline describes how signals are handled when template controlled control logic documents are
upgraded or restored:
• Signals assume the same controlled status as the input connector of the entity it is connected to.
Control Logic Document Signals

The following guidelines describe how control logic document signals are handled:
• The signal input connection cannot be disconnected if any leaf branch of the signal is template controlled.
• Any template controlled leaf branch connection cannot be disconnected or deleted.
• Any signal that has an unconnected input can be deleted.
• Non-template controlled leaf branches can be disconnected or deleted.
• A signal can be deleted if it has no template controlled leaf branches.
• Leaf branches can be added to any signals regardless of template control status.
• Control logic entities with an uncontrolled location can be moved. During upgrade or restore, the signal coordinates
will be updated to coincide with those of the control logic document.
Control Logic Template Signals

The following guidelines describe how control logic template signals are handled:
• Function code input specifications default to template-controlled when a signal is connected.
• Function code input specifications revert to uncontrolled when the signal is disconnected.
3-20 2VAA000813-230 A
Adding a Signal
• Adding a signal with at least one template controlled entity causes the signal to be added to the control logic
document (even if branches must be used) when it is upgraded or restored.
Figure 3-5: Adding a Signal
• Since the input connector of a function code or cross-reference entity can only be connected to one signal source,
the template specified connection will be used during an upgrade or restore operation if the input is template
controlled or control logic template override functionality is used. The control logic document branch will be deleted.
If the input is uncontrolled and the control logic document override functionality is used, the control logic document
will not be changed.
• Since the output connection of a function code or cross-reference entity can only have one signal attached to it, the
signal from the template will be used during an upgrade or restore operation and an existing signal in the control
logic document will be made into a branch.
• There will be no change or upgrade to a control logic document when a signal that already exists in the document
is added to the template.
• If an entity is moved (entity location uncontrolled), signal connector coordinates will be updated to coincide those of
the control logic document.
2VAA000813-230 A 3-21
Deleting a Signal
• Deleting a template controlled signal from a control logic template causes all control logic document template
controlled leaf branch connectors to be disconnected and removed when upgrading or restoring. Connectors
created in the control logic document (non-template controlled connectors) are not removed.
Figure 3-6: Deleting a Signal
• Disconnecting all leaf branch connectors of a signal causes it to be removed.

• The restore functionality does not remove control logic document-defined signal connectors unless a conflict exists.
3-22 2VAA000813-230 A
Moving Source Connectors

• Moving a template controlled source connector in a control logic template causes the template controlled source
connector in the control logic document to be moved when upgrading or restoring.
Figure 3-7: Moving Source Connectors
• Moving non-template controlled source connectors will have no affect during an upgrade or restore operation.
• If moving a template controlled source connector results in a conflict with a non-template controlled source
connector, the non-template controlled connector will be made into a branch.
2VAA000813-230 A 3-23
Moving Target Connectors

• Address specifications of function codes and cross-references will become non-template controlled if the signal is
disconnected from it.
Figure 3-8: Moving Target Connectors
• Address specifications of function codes and cross-references will (by default) become template controlled if a
signal is connected to it.
• Connection or disconnection of target connectors is reflected in the control logic document.
• The control logic template connector will override the control logic document connector if it is template controlled or
control logic template override functionality is used.
• The control logic document connector will override the control logic template connector if the control logic template
connector is uncontrolled and control logic document override functionality is used.
Adding a Leaf Branch

• If the target connector (function code or cross-reference) of the leaf branch is already connected in the control logic
document, the control logic template connection will be created and the control logic document connection will be
deleted if the branch is template controlled or the control logic template override functionality is used during an
upgrade or restore operation.
• If the target connector (function code or cross-reference) of the leaf branch is already connected in the control logic
document, the control logic document connection will remain unchanged if the branch is uncontrolled and the
control logic document override functionality is used during an upgrade or restore operation.
• Signals that do not exist in the control logic document will be created.
• If the target function code does not exist in the control logic document, the branch will not be created.
3-24 2VAA000813-230 A
Deleting a Leaf Branch

• The leaf branch will be deleted from the control logic document.
Disconnected Signals
• Using the Attempt to maintain connections to CLD-defined logic feature during an upgrade or restore operation
causes Control Engineering to attempt to connect orphaned signal connections to connectable entities occupying
the same space.
• Signals with no source connection will be deleted.
• Leaf branches with no target connection will be deleted.
Figure 3-9: Disconnected Signals
Signal Routing
• If the same template-controlled signal (same source and destination connectors with identical X and Y coordinates
but different actual path) is present in both control logic template and document, the actual path in the control logic
template will be used during upgrade or restore operations.
• Control logic documents containing connectable entities not found in the control logic template will display a
message stating that signal paths may need to be manually adjusted in order to clean up the documents
appearance.
3.18.1.10Miscellaneous Issues
• CLDs created from CLTs in previous versions of Control Engineering may be unlinked in on project upgrade. If the
user attempts to link it from the CLD template linking status page, an unspecified error may be displayed. If an
attempt to link is made from the CLT Actions dialog in the exchange, Failed to link Control Logic Document 'XXX'.
may be displayed.
2VAA000813-230 A 3-25
• When using the actions dialog for a CLT, changes to the link status of CLDs associated with the CLT are not
automatically reflected in the icons of the CLDs shown in the list view of Control Engineering. Performing a refresh
(e.g., from the context menu of a controller in the tree view) will cause the icons within the refreshed context to
reflect the correct link status.
• The icons in Control Engineering that indicate the state of the CLD (e.g., linked, locked, etc.) are not automatically
refreshed when these states are changed as the result of a Make Current operation that replaces the working
version with a revision that had a different CLD state.
3-26 2VAA000813-230 A
4. Editing Configurations Introduction
4. Editing Configurations
4.1 Introduction
After entities are inserted or drawn onto a sheet of a control logic document they can be edited. This section describes how
to select and edit entities. Also described is how to use the Assign Tag functionality to assign tags to entities and how to
create shapes, macros, borders, and control logic templates.
4.2 Entity Selection

Entities must be selected before being edited. Entities are selected using the mouse or using the Edit > Select By functions.
When an entity is selected, it is surrounded by a bounding box. The various selection methods apply only to the active sheet
and are described in the following text.
By Pointing and Clicking

To select an entity by pointing and clicking:
1. Choose Tools > Selection Arrow.
2. Position the cursor on the entity to be selected and click.
This method is not guaranteed to select the entity of interest. If one entity is on top of the other, the wrong entity may be
selected. If this happens, reposition the cursor and try again or use another method.
By Shift-Click Mechanism
To select more than one entity at a time:
1. Select the first entity by pointing and clicking.
2. Position the selection arrow on top of the next entity to be selected.
3. Simultaneously press SHIFT and the left mouse button.
4. Repeat Step 2 and Step 3 for the remaining entities to be selected.
By Window
To select one or more entities by window:
2. Position the selection arrow at one corner of the window.
3. Drag the cursor to form a window containing the entity.
4. Release the mouse button. All entities entirely within the window are selected.
Accidentally clicking the selection arrow on an entity can select the entity and prevent a window from being drawn. To
prevent this, hold down CTRL-ALT when drawing the window.
All
To select all entities on the current sheet, choose Edit > Select All.
By Unassigned Block
To select all function codes with unassigned block numbers, choose Edit > Select By > Unassigned Block.
By Block
To select a function code having a block number matching a user provided block number:
1. Choose Edit > Select By > Block.
2. Enter the block number of the function code to be selected in the dialog box.
3. Click OK.
By Layer
To select all entities on user specified layers:
1. Choose Edit > Select By > Layer.
2. A dialog box appears from which layers can be checked for selection. Check each layer on which all entities are
to be selected.
3. Click OK.
By Cross-Reference
To select entities having a cross-reference matching a specified text string:
1. Choose Edit > Select By > Cross-reference.
2. Select a cross-reference from the drop-down list in the select by reference dialog box.
3. Click OK.
2VAA000813-230 A 4-1
Entity Editing 4. Editing Configurations
By Attribute
To select an entity having an entity attribute matching a specified attribute:
1. Choose Edit > Select By > Attribute.
2. Select an attribute type from the dialog box.
3. Click OK.
4. Enter the value of the attribute to be selected in the dialog box.
5. Click OK.
By Tag
To select a function code having a tag name matching a specified tag name:
1. Choose Edit > Select By > Tag Name.
2. Select the tag name corresponding to the exception reporting function code to be selected from the drop-down
list in the select by tag dialog box.
3. Click OK.
By Entity Name
To select entities by user-defined name:
1. Choose Edit > Select By > Entity Name.
2. Select the desired entity name from the drop-down list in the select by name dialog box.
3. Click OK.
By Order
The next and previous selection methods are used in conjunction with other selection techniques. To select entities using
next and previous:
1. Select a group of entities by any of the other methods.
2. Select Edit > Next or use the shortcut key TAB. The first entity in the order (in which the entities are inserted or
drawn) is selected. Further use of Next cycles through all entities in the group according to their order. Once the
last entity is selected, selecting Next again selects all the entities in the original group.
Previous (Edit > Previous or the shortcut keys SHIFT-TAB) works in a similar manner to Next, except the previous entity is
selected according to entity order.
4.3 Entity Editing

Once an entity is drawn or inserted, editing operations can be performed on it. Most entities can be cut, copied, deleted,
moved, and have attributes assigned or modified. Other actions performed on an entity depend on the entity type. Before an
entity can be edited, it must be selected as described in Entity Selection.
4.3.1 Attributes
Entity attributes provide an alternate means of documenting entities drawn or inserted into a sheet. An entity attribute
consists of an attribute type, an attribute value of up to 32 characters, and an occurrence number. Entity attributes appear
below the entity to which they are assigned. Entity attributes are defined and edited by right-clicking the entity, selecting
Properties from the pop-up menu, and selecting the attributes tab.
The attribute types include tag name, tag descriptor, output, unit, directive, and program reference. Some of these attributes
are for ABB internal use. Any attribute can also be searched for using Edit > Select By > Attribute. Other entity attributes
can be defined and used for documentation purposes.
The occurrence number allows an entity to have more than one entity attribute of the same type. For example, a function
code with two block outputs could have a different output entity attribute for each of its block outputs. As well, two different
entities could have identical entity attributes (the same type and value).
There are two advantages in using entity attributes versus text entities:
• Text entered as an entity attribute remains with the entity if it is moved. The position of the entity attributes is fixed,
appearing below the entity to which they are assigned.
• Although entity attributes increase the file size of the control logic document, they are stored separately from and
do not add to the configuration information space.
Adding an Attribute
To define an entity attribute for an entity:
1. Select the entity.
4-2 2VAA000813-230 A
4. Editing Configurations Tag
2. Right-click the entity and select Properties from the pop-up menu.
3. Select the attributes tab of the property page.
4. If no attributes have been defined, click Add. The first attribute can now be defined. To add subsequent
attributes, press  until another record appears.
5. Choose an attribute type from the drop-down list box or use  and  to cycle through the choices. The first
attribute of a given type is given an occurrence number of one. Subsequent attributes of the same type are given
occurrence numbers automatically incremented from the previously defined attribute.
6. Type a text string in the Value Text field.
7. Set the display and print options as desired.
8. Click OK to accept the entity attribute. The entity attribute is visible provided the Show Attributes function (use
Tools > Options) is enabled and the entity display field is set to Yes.
After an entity has one or more entity attributes defined, the entity attributes can be modified.
Modifying an Attribute
To modify the entity attributes of an entity:
1. Right-click the entity and select Properties from the pop-up menu.
2. Select the attributes tab of the property page. A listing of all the entity attributes defined for that entity is
displayed.
3. Make changes as follows:
– To change the attribute type, click the type field and enter a new type from the drop-down list box or use 
and  to cycle through the choices.
– To change the value, click the value field and enter a new text string.
– To change the display or print fields, click the field and select Yes or No from the drop-down list box.
– To remove an attribute, select the attribute and click Delete.
4. Click OK to accept the changes and continue.
4.3.2 Tag
Tags can be assigned to exception reporting function codes to support single point tag data entry. Refer to Section 3,
Configuration Components for information on how the tag assignments are used.
After an exception reporting function code has a tag name assigned, it can be removed. When the assignment is removed,
the control network, HCU, controller, and block address of that tag are set to zero in the tag database. When a tag is
removed, it is immediately unlinked.
User must not use the following special characters in tag names. They are not compatible with technology from previous
product versions and may impact project upgrade to current product version.
(SPACE)
' (apostrophe)
" (double quotes)
@ (at sign)
` (grave accent)
# (number sign)
% (percent)
> (greater than)
< (less than)
! (exclamation mark)
. (period)
[ (brackets)
] (brackets)
* (asterisk)
$ (dollar sign)
; (semicolon)
: (colon)
2VAA000813-230 A 4-3
Block Number 4. Editing Configurations
? (question mark)
^ (caret)
{ (braces)
} (braces)
+ (plus sign)
- (hyphen)
= (equal sign)
~ (tilde)
\ (back slash)
_ (underscore)
Assignment
To assign a tag to an exception reporting function code:
2. Select Assign Tag from the pop-up menu. A dialog box appears with a list of tags defined in the tag database.
3. Do one of the following:
– Select an already defined tag from the pick list and click OK to continue.
– To define a new tag, click New and fill in the tag name and descriptor (optional) fields in the dialog box that
appears.
Removal
To remove a tag assignment:
1. Right-click the exception reporting function code.
2. Select Unassign Tag from the pop-up menu.
3. Click OK to continue.
4.3.3 Block Number

After a function code is inserted, it must be assigned a block number. The block number can also be changed at any time
after it is assigned.
To assign or change a function code block number:
1. Right-click the function code of interest.
2. Select Properties from the pop-up menu. If not already selected, select the specifications tab.
3. Enter a new block number.
4. Click OK. If the function code has been assigned a tag, the tag database is updated with the new block address.
4.3.4 Cross-Reference Name

It is possible to rename a cross-reference after it has been configured. During the renaming process, an option to change all
existing cross-references using the old name to the new name is provided. Utilizing this option changes all the cross-
references thereby keeping all the cross-references connected. Failure to utilize this option renames the selected cross-
reference but disconnects all the cross-references using the old name. Once a cross-reference is renamed, it is
automatically connected to any existing cross-references using the new name.
User must not use the following special characters in cross-reference names.
# (number sign)
% (percent)
* (asterisk)
? (question mark)
_ (underscore)
To edit a cross-reference name:
1. Right-click the cross-reference entity.
3. Select the cross-reference tab.
4-4 2VAA000813-230 A
4. Editing Configurations Line and Signal Width
4. Enter the new cross-reference name in the Descriptor field.

5. Click OK.
6. In the dialog box, specify if all the cross-references using the old name should be changed to the new name.
Refer to Section 3 for more information about cross-references.
4.3.5 Line and Signal Width

After a line, rectangle, circle, arc, or signal is drawn, its line width property can be changed.
To change the line width of a line or signal:
1. Right-click the line or signal.
3. Select the Object tab.
4. Select a new line width from list box.
5. Click OK. Solid and dashed are the only valid line styles for signals. Solid, dashed, dotted, and dot-dash line
styles are valid for lines, rectangles, circles, and arcs.
4.3.6 Cut, Copy, and Paste

The cut, copy, and paste functionality within the Automation Architect work in the standard Windows manner. The Cut,
Copy, and Paste options are available from the edit menu and a pop-up menu displayed by right-clicking entities (previously
selected or not).
Cut
To cut an entity:
2. Select Cut from the pop-up menu.
Copy
To copy an entity:
2. Select Copy from the pop-up menu.
Paste
To paste an entity:
1. Right-click somewhere in the sheet.
2. Select Paste from the pop-up menu. The pasted entity appears at the cursor position.
NOTE: If a function code having a tag assigned is pasted, a copy of the tag will also be created. If an entity
containing cross-references is copied, the cross-reference names are copied and made unique as well.
3. Position the entity as desired and click the mouse button to insert the entity.
4.3.7 Delete
Entities can be deleted from a document. This is different from cutting an entity since a deleted entity is not pasted to the
clipboard.
To delete an entity:
2. Select Delete from the pop-up menu.
NOTE: If a tag linked function code is deleted, the tag is handled according to the current workspace environ-
ment settings (refer to 2.9.2- Environment Properties). If a cross-reference or I/O connector entity is deleted,
the cross-reference name is removed from the cross-reference database.
4.3.8 Explode
User-defined shapes and borders can be separated into its component entities in order to edit one or more of the individual
entities, for example. This is referred to as exploding it. Once the shape is exploded, it loses its identity as a shape. Not all
shapes can be exploded.
2VAA000813-230 A 4-5
Specifications 4. Editing Configurations
To explode a shape:
1. Select the shape to explode.
2. Select Edit > Explode.
4.3.9 Specifications
When a function code is inserted it is given default specification values. These specification values can be modified to suit
the needs of the process control application.
To modify function code specification values:
3. Select the function codes tab in the properties dialog box.
4. This dialog box shows the function block number and all the specifications that can be modified. Table 4-1
describes the columns used to describe the specifications. Select the specification to be modified.
5. Edit the value of the specification as desired. The Minimum, Maximum, and Default buttons set the value to the
indicated number. The Default All button sets all the specifications to their default values.
6. Click Apply.
Table 4-1: Function Code Specification Column Headings
Column Description
Spec Specification number as listed in the Function code reference User manual.
Tune Indicates whether the specification is tunable or not.
Type Data type of the specification: integer, real, character.
Value Specification value.
Translation Meaning of the specification value for binary or decimal coded specifications. An out
of range message appears for integer and real values if they are out of range. If the
translation needs more room, it is extended into the description column and the
description appears in the following line.
Description Description of the specification.
The specifications for all function codes can be filtered by selecting one of the following filters.
All
Displays all usable specifications.
Standard
Displays all important specifications.
Inputs
Displays only input specifications.
Internal
Displays only internal specifications.
Tunable
Displays only tunable specifications.
Online Configuration
Displays only online configuration specifications.
Depending on the function code, more filters are available. These filters include:
4-6 2VAA000813-230 A
4. Editing Configurations Text
Analogs
Digitals
Failure Def
Hardware
Input
Input Addrs
Masks
Min/Max
Module
Output
Output Addrs
Port Def
Signal
Simulation
Thermocouple
Times
Tune Params
Z11 - Z15
Z21 - Z25
Z31 - Z35
Z41 - Z45
Z51 - Z55
NOTE: When editing Function Code 110 specification 1, valid values are 0 through 3, inclusive. Entering a value greater
than 3 and less than 255 where the last digit is 0,1,2, or 3, will cause Control Engineering to incorrectly state that the
value is valid and treats it as if the value were only the last digit. However, when loaded into the controller, the Function
Code 110 will actually function as though a 0 had been entered no matter what the last digit is (i.e. even if the last digit is
1, 2, or 3, it is treated as 0).
NOTE: The advanced editing dialog for Function Code 177 does not show the complete text for the possible values of
Specification 20. These values are listed in the Function Code Manual entry for Function Code 177.
NOTE: It is recommended that the user not configure any of the address-related specifications for I/O connector function
codes when configuring a macro. These specifications will be filled in automatically once the macro logic has been
dropped onto a CLD and the XREF descriptors are defined. Currently, Control Engineering allows these specifications to
be edited in the macro. However, the results are not saved, and default values will be used when the macro is dropped
onto a CLD.
4.3.10 Text
Text strings can be modified as needed. To modify a text string:
1. Right-click the text to be modified.
3. Select the text tab in the dialog box.
4. Make any changes to the text string, character size, or rotation.
5. Click OK to accept the changes and continue.
4.3.11 Movement
Entities and signal segments can be repositioned after initial placement.
Entity
After an entity has been inserted or drawn it can be repositioned as needed.
To move an entity:
2. Position the selection arrow within the selected entity and drag the entity to its new position.
If a signal or an entity having a signal connected to it is moved, the signal automatically adjusts its length and position to
remain connected to the entity.
Signal Segment
The individual segments of the signal can be moved to route them as needed. Branches added to signals can be moved in
the same manner.
2VAA000813-230 A 4-7
Rotate 4. Editing Configurations
To move a signal segment:

1. Select the signal.
2. Position the selection arrow directly on the segment to be moved and drag it to its new position. Connecting
segments automatically adjust themselves to remain connected.
4.3.12 Rotate
Documentation entities and shapes containing only documentation entities can be rotated after they are drawn or inserted.
The rotation occurs about a point selected using the rotate cursor and is restricted to rotation angles in multiples of 90
degrees. A positive rotation angle produces a counterclockwise rotation of an entity while a negative rotation angle
produces a clockwise rotation of an entity.
To rotate an entity:
1. Select one or more entities.
2. Right-click one of the entities.
3. Select Rotate from the pop-up menu. The cursor changes to the rotate cursor.
4. Position the cursor and click to mark the point about which rotation will take place. The rotate dialog box
appears.
5. Select a rotation angle and direction.
The rotate cursor remains as the cursor until another tool is selected or the cursor is placed on the control logic document
background and a right-click is executed.
4.3.13 Scale
Some documentation entities (line, circle, rectangle, and arc) and shapes containing only documentation entities can be
uniformly enlarged or reduced (scaled) after they are drawn or inserted. Scaling is restricted to integer scale factors. A
positive scale factor increases the size of an entity while a negative scale factor reduces the size of an entity. For text, scale
is a multiplier of the text size.
To scale an entity:
1. Select one or more entities.
2. Right-click one of the entities.
3. Select Scale from the pop-up menu. The scale cursor appears.
4. Position the cursor and click to mark the point about which scaling will take place. The scale dialog box appears.
NOTE: Scaled entities may be shifted if the scale point is not exactly centered.
5. Select a scale factor.

The scale cursor remains as the cursor until another tool is selected or the cursor is placed on the control logic document
background and a right-click is executed.
4.3.14 Resize
To resize (non-uniformly scale) an entity:
2. Drag the selection handles until the entity is the correct shape and size.
4.4 Creating Shapes, Macros, Borders, and Control Logic Templates

Shapes, macros, borders, and control logic templates can be created and saved to a user-defined exchange folder.
To create a document shape, macro, custom border, or control logic template:
1. Create a new, or open an existing, exchange folder.
2. Right-click empty space in the exchange window.
3. Select New > Document Shape, New > Macro, New > Custom Border, or New > Control Logic Template from the
pop-up menu.
4. Enter a name on the general tab of the property page.
5. Click OK.
The shape, macro, border, or control logic template appears in the folder directory listing.
4-8 2VAA000813-230 A
4. Editing Configurations Editing Shapes, Macros, Borders, and Control Logic Templates
6. Right-click the new shape, macro, border, or control logic template.

7. Select Open from the pop-up menu.
8. Configure the shape, macro, border, or control logic template from the beginning or copy and paste entities from
other control logic documents.
9. Select File > Save.
10. Select File > Close.
4.5 Editing Shapes, Macros, Borders, and Control Logic Templates

User-defined shapes, borders, macros, and control logic templates can be edited directly from the exchange folder. The
following discussions provide specific information about editing shapes, borders, macros, and control logic templates.
System document shapes and borders can be opened and viewed, but not edited.
The general editing procedure is:
1. Open the exchange folder containing the item to be edited.
2. Right-click the item to be edited.
3. Select Open from the pop-up menu. The Automation Architect window appears with the selected item opened.
4. Edit the item as necessary.
5. Select File > Save.
6. Select File > Close.
4.5.1 Shapes
Only shapes and primitive entities such as lines, arcs, circles, rectangles, and text can be added to a shape. Compilable
entities (function codes, cross-references, and signals), borders, and macros can not be added to shapes.
4.5.2 Borders
Only shapes and primitive entities such as lines, arcs, circles, rectangles, and text can be added to a shape. Compilable
entities (function codes, cross-references, and signals), borders, and macros can not be added to borders. However, the
placement or exclusion of various text fields can be controlled. These text fields represent data that is dynamically filled in
when the border is inserted. Table 4-2 lists and describes the text fields. To exclude a text field, select and then delete it.
Table 4-2: Border Text Fields
Name Description
CLD name Control logic document, control logic template, or macro name (whichever the
border is inserted into) defined in the general properties of the control logic
document.
Control network Control network address defined in the general properties of the control network.
This field is not applicable to borders inserted into macros or control logic
templates.
Controller Controller address defined in the general properties of the controller. This field is
not applicable to borders inserted into macros or control logic templates.
CurAprv Name of the person who approved the current control logic document.
CurDate Date the current control logic document was approved.
CurDesc Description or revision comment associated with the current control logic
document.
CurOwner Name of the person who originated the current control logic document.
CurRev Revision level of the current control logic document.
Customer Customer name defined in the custom properties of the project.
Customer ref1 Customer order reference defined in the custom properties of the project.
Customer ref2 Customer order reference defined in the custom properties of the project.
Drawing Drawing number defined in the custom properties of the project.
Eng Contracting firm defined in the custom properties of the project.
2VAA000813-230 A 4-9
Macros 4. Editing Configurations
Table 4-2: Border Text Fields (Continued)
Name Description
HCU Harmony control unit address defined in the general properties of the Harmony
control unit. This field is not applicable to borders inserted into macros or control
logic templates.
ID Controller ID (two character identifier) defined in the general properties of the

project.
Job number Contract/job number defined in the custom properties of the project.
NM File name in previous configuration tools. Use the CLD Name field instead.
Order Internally defined order or index number of this control logic document within the
controller. This field is not applicable to borders inserted into macros or control
logic templates.
Plant Plant site information defined in the custom properties of the project.
Rev1Aprv Name of the person who approved the next most recent revision of the current
control logic document. Rev1Aprv is the name of the person who approved the
second most recent revision of the current control logic document and so on.
Rev1Date Date the second most recent revision of the current control logic document was
approved. Rev2Date is the date the second most recent revision of the current
control logic document was approved and so on.
Rev1Desc Description or revision comment associated with the next most recent revision of
the current control logic document. Rev2Desc is the description or revision
comment associated with the second most recent revision of the current control
logic document and so on.
Rev1Owner Name of the person who originated the next most recent revision of the current
control logic document. Rev2Owner is the name of the person who originated the
second most recent revision of the current control logic document and so on.
Rev1Rev Revision level of the next most recent revision of the current control logic
document. Rev2Rev is the revision level of the second most recent revision of
the current control logic document and so on.
Sheet name Name of a sheet within a control logic document or control logic template.
Sheet number, Page number of a sheet within a control logic document or control logic template.
sheet #
Title Drawing title information defined in the custom properties of the project.
4.5.3 Macros
Primitive entities (lines, arcs, circles, rectangles, and text), compilable entities (function codes, cross-references, and
signals), borders, shapes, and other macros can be added to macros.
Macros are also supported by a tag linking feature. This feature allows new tags to be created and linked to exception
reporting function codes used in a macro. Assign the new tag name and description by right-clicking the exception reporting
function code and then select Assign Tag from the pop-up menu. Inserting a macro creates a copy of the tags (with
.Copy(n) extension) and maintains their links to the exception reporting function codes also created in the target document.
4.5.4 Control Logic Templates

Control logic templates can contain all the entities that can be placed in a control logic document.
4.6 Repeating the Last Command

The last editing operation can be repeated any number of times. To repeat the last editing operation, select Repeat Last
from the edit menu. This functionality can save time when performing repetitive operations such as inserting a commonly
used function code into a control logic document. After inserting the first instance of the function code, use the Repeat Last
function to insert another. Each new instance is inserted slightly offset from the previous instance.
4-10 2VAA000813-230 A
4. Editing Configurations Undoing and Redoing Operations
4.7 Undoing and Redoing Operations

A history of drawing, inserting, and editing actions performed on the entire control logic document is maintained for the
current editing session. These actions can be successively undone from last to first. Undo can be used to quickly undo an
operation that produced unsatisfactory results. If an action is undone, it can be redone using Redo. Redo reverses the
action of the last undo operation. Undo and Redo functionality extends across all the sheets of a template or document.
NOTE: The deletion of a control logic template or document sheet can not be undone.
Undo
To undo an operation, select Edit > Undo. A message indicating when the undo operation is being performed is displayed.
Redo
To redo the last undo operation, select Edit > Redo. A message indicating when the redo operation is being performed is
displayed.
2VAA000813-230 A 4-11
Undoing and Redoing Operations 4. Editing Configurations
4-12 2VAA000813-230 A
5. Example Configuration Introduction
5. Example Configuration
5.1 Introduction
This section describes one method of configuring a simple control logic document.
5.2 Example Control Logic Document Data

The simple example control logic is depicted in Figure 5-1. Refer to this figure during the configuration process.
Figure 5-1: Example Control Logic
5.3 Configuration Procedure

This procedure is divided into 11 parts. These parts are:
• Creating and opening a control logic document
• Inserting a border
• Inserting function codes
• Inserting cross-references
• Inserting constant blocks.
• Connecting components with signals
• Connecting components with branches
• Adding text
• Setting specifications
• Setting properties
• Assigning Tags
2VAA000813-230 A 5-1
Creating and Opening a Control Logic Document 5. Example Configuration
5.3.1 Creating and Opening a Control Logic Document

To create a control logic document:
1. Open an existing project or start a new project that contains at least one controller.
2. Select the control logic templates folder in the exchange window.
3. Drag the control logic template from the exchange folder onto the controller. A control logic document of the
same name is created.
4. Right-click the control logic document.
5. Select Rename from the pop-up menu.
6. Type:
Practice_CLD
7. Press ENTER.
8. Right-click the Practice_CLD control logic document.
9. Select Open from the pop-up menu.
5.3.2 Inserting a Border

To insert a border:
1. Select the custom borders folder in the exchange window.
2. Drag the AHBORDG custom border from the exchange to the lower left corner of the control logic document.
5.3.3 Inserting Function Codes

To insert the function codes:
1. Select the function codes folder in the exchange window.
2. Drag function code 62 (RCM) from the exchange to the inside of the border. Place it near the left side.
3. Drag function code 86 (ETIMER) from the exchange to a position just to the right of the RCM function code.
4. Drag function code 33 (NOT) from the exchange to a position just to the right of the ETIMER function code.
5. Drag function code 38 (AND4) from the exchange to a position just to the right of the NOT function code.
6. Drag function code 33 (NOT) from the exchange to a position below the RCM function code.
7. Drag function code 62 (RCM) from the exchange to a position below the ETIMER function code.
8. Drag function code 45 (DO/L) from the exchange to a position to the right of the AND4 function code.
9. Drag function code 45 from the exchange to a position below the previous DO/L function code.
5.3.4 Inserting Cross-References

To insert the cross-reference connectors:
1. Select the cross-references folder in the exchange window.
2. Drag the OREF connector from the exchange to a position above the DO/L function codes.
3. Drag the IREF connector from the exchange to a position below and to the left of the AND4 function code.
5.3.5 Inserting Constant Blocks

To insert the constant blocks:
1. Select the constant blocks folder in the exchange window.
2. Drag constant block B1 from the exchange to a position below the AND4 function code.
3. Drag constant block B1 from the exchange to a position below the lower NOT function code.
5.3.6 Connecting Components with Signals

To connect the configuration components using signals:
1. Select Tools > Options.
2. Select the grid tab in the dialog box.
3. Select the 20/1 grid setting.
4. Click OK.
5-2 2VAA000813-230 A
5. Example Configuration Connecting Components with Branches
5. Select Tools > Signal.

6. Click the output of the upper RCM function code.
7. Terminate the signal (double-click) on the S1 input of the ETIMER function code.
8. Click the lower output (A) of the ETIMER function code.
9. Terminate the signal on the S1 input of the upper NOT function code.
10. Click the output of the upper NOT function code.
11. Terminate the signal on the S2 input of the AND4 function code.
12. Click the output of the upper constant block.
14. Click the output of the AND4 function code.
15. Terminate the signal on the S1 input of the upper DO/L function code.
16. Click the output of the lower NOT function code.
17. Terminate the signal on the S3 input of the lower RCM function code.
18. Click the output of the lower constant block.
19. Terminate the signal on the S4 input of the lower RCM function code.
20. Click the output of the lower RCM function code.
5.3.7 Connecting Components with Branches

To connect the configuration components using branches:
1. Right-click the signal connecting the upper RCM and ETIMER function codes.
3. Position the cursor on the S3 input of the upper RCM function code and double-click.
4. Right-click the signal connecting the ETIMER and upper NOT function codes.
6. Position the cursor on the S2 input of the ETIMER function code and double-click.
7. Right-click the signal connecting the AND4 and upper
DO/L function codes.
9. Position the cursor on the input of the OREF connector and double-click.
10. Right-click the signal connecting the AND4 and upper
DO/L function codes.
12. Position the cursor on the S1 input of the lower NOT function code and double-click.
5.3.8 Adding Text

To insert text:
1. Select Tools > Text.
2. Click a position just above the upper RCM function code.
3. Type:
ON LIST GROUP #1
4. Click OK.
5. Click a position just above the lower RCM function code.
6. Type:
OFF LIST GROUP #1
7. Click OK.
8. Click a position just above the ETIMER function code.
9. Type:
HORN TIMER
2VAA000813-230 A 5-3
Setting Specifications 5. Example Configuration
10. Click OK.

11. Click a position just above the upper DO/L function code.
12. Type:
ALARM HORN #1
13. Click OK.
5.3.9 Setting Specifications

To set the specifications of the function codes:
2. Right-click the upper RCM function code.
3. Select Specifications from the pop-up menu.
4. Enter 100 in the Block field.
5. Click OK.
6. Right-click the ETIMER function code.
9. Enter 45 in the Value field of specification S4.
10. Click OK.
11. Right-click the upper NOT function code.
14. Click OK.
15. Right-click the AND4 function code.
18. Click OK.
19. Right-click the lower NOT function code.
22. Click OK.
23. Right-click the lower RCM function code.
26. Click OK.
27. Right-click the upper DO/L function code.
30. Click OK.
31. Right-click the lower DO/L function code.
34. Enter 1 in the Value field of specification S2.
35. Click OK.
5.3.10 Setting Properties

To set the properties of the cross-reference connectors:
1. Right-click the OREF connector.
3. Select the cross-references tab.
5-4 2VAA000813-230 A
5. Example Configuration Assigning Tags
4. Enter GLOBALRESET2 in the Description field.

5. Click OK.
6. Right-click the IREF connector.
8. Select the cross-references tab.
9. Enter GLOBAL1 in the Description field.
10. Click OK.
5.3.11 Assigning Tags

To assign a link (tag) to the exception reporting function code:
1. Right-click the DO/L function code located at function block 175.
2. Select Assign Tag from the pop-up menu. The assign tag dialog box appears.
3. Enter HORN1-ALARM in the Name field.
4. Enter HORN #1 ALARM in the Description field.
5. Click OK.
2VAA000813-230 A 5-5
Assigning Tags 5. Example Configuration
5-6 2VAA000813-230 A
6. Monitor/Tune Configurations Introduction
6. Monitor/Tune Configurations
6.1 Introduction
The Automation Architect has two modes of operation. They are offline and online. This section describes the features and
capabilities of the online mode.
6.2 Online Mode

The online mode permits the monitoring and tuning of function code blocks. When this mode is entered, the function code
block output values are updated with actual values from the controller. Tunable parameters can be tuned in this mode. The
Control Engineering software must be communicating with the Symphony network and the configuration to be monitored
must have been previously downloaded to the controller. Read/write access to the control logic document is required when
tuning values. Read only access permits the monitoring of values only.
Group Monitoring
The Group Monitoring function is one of monitoring type supports high speed monitoring using GMI (General Message
Interface). Maximum 16 block outputs are acquired with a communication command. After checking block presents in the
controller with general monitoring way at startup communication, the Group Monitoring function moves to high speed
monitoring.
The Group Monitoring function has following limitations by communication specification.
Limitations:
• Display of the Quality Status Indicators (“6.2.3 Monitor/Tune Tag Status Indicators”) is not supported.
• Plant loop system is not supported.
• The Soft Controller function and the Harmony Training Simulator are not supported.
NOTE: GMI is one of General Communications Message of communications transactions in which any NETWORK 90,
INFI 90 or Plant Loop module may engage. The GMI message is used by the Plant Bus communications modules to
transfer a Module Bus message from the OIU to the node in which the target module resides. The BIM (Bus Interface
Module) in that node then handles the Module Bus transaction and returns the reply to the OIU using the reply form of
this message.
6.2.1 Configuration
Can be enabled at Environment Properties.
Figure 6-1: Enabling the Group Monitoring function
“G” mark is displayed at bottom-right of status bar when the Group Monitoring function is enabled.
Figure 6-2: “G” Mark
2VAA000813-230 A 6-1
Usage 6. Monitor/Tune Configurations
The client Control Engineering application must be configured to communicate with the server Control Engineering
application which is connected to the actual run-time system through a computer interface module. This configuration needs
to be performed from the Control Engineering window. Refer to Chapter ICI to Computer Interface Setup in the S+
Engineering 2.3 Harmony engineering User manual (2VAA000812) for more information.
Basic behavior, display setting and colors of UI elements of the instant trend can be customized at Environment Properties.
The changed configuration will affect newly opened instant trend, but not already opened. As exception, configuration
related with the windows management will affect newly opened control logic documents.
6.2.2 Usage
To monitor and tune a configuration:
1. Open the control logic document containing the portion of the configuration to be monitored and tuned.
2. Select View > Monitor/Tune.
Current data (except specification values and descriptors) from the controller appears on the sheets above the output line of
each function code. Also displayed during monitor/tune mode is the value brought into a control logic document by input
references. Terminating the monitor/tune mode causes specification information to be displayed again.
3. Examine any function block or input reference connector outputs of interest.
4. If necessary, view and tune function code specifications by right-clicking the function code and selecting
Properties from the pop-up menu.
5. Edit the function code as necessary.
If tunable parameters are modified and the changes are accepted, the changes are stored within the control logic document
and are transmitted to the affected function blocks within the controller.
To open instant trend to monitor any function block output:
1. Select any signal line and show the context menu.
2. Select Open Instant Trend...
The play and pause modes can be switched by toggle button.
User can customize the display range and the sampling interval. Click Apply, it changes the effects and resets the trend
curve.
Vertical slider control changes transparency of the window dynamically.
User can close the instant trend by clicking Close.
Click on context menu to close the sheet, it closes all the instant trends opened on the same sheet with this single action.
6.2.3 Monitor/Tune Tag Status Indicators

Please find an explanation of the status indicators on function block outputs when using Monitor/Tune:
• Bad Quality
– H: High Alarm
– L: Low alarm
– D: High Deviation Alarm
– d: Low Deviation Alarm
– C: Calibration out of range
– S: Output disabled or Status Error Inhibit selected
– T: Output tracking
The title bar shows following items:
• CLD name and sheet name
• Data type (A: analog signal, D: digital signal)
• Current value or CIU error code
• Quality statues
– * : Bad / Suspect
– H : In Alarm / High Alarm
– L : Low Alarm
– D : High Deviation Alarm
6-2 2VAA000813-230 A
6. Monitor/Tune Configurations Communication Status Indicator
– d : Low Deviation Alarm

– C : Calibration Out of Range
– S: Output disabled / Status Error Inhibit Selected
– T: Output Tracking
The instant trend area displays trend curve, function block address, the value range and the time axis with sampling
interval. Good quality signals are drawn in solid line style and bad quality signals are drawn in dashed line style. Analog
signals are drawn in linear type and digital signals are drawn in step type. The initial range for analog signals is configured
in the environment properties and for digital signals it is fixed range (-0.5 ~ 1.5).
6.2.4 Communication Status Indicator

If user try to connect the ICI through Tune/Monitor, it changes to yellow. It will becomes green, once the ICI connection is
successful. If any ICI communication error occurs, this status will be shown as red for which user need to check the
communication settings.
Figure 6-3: Communication Status Indicator
Table 6-1: Status Indicator
Description
Status Color
Offline Gray Offline
Starting Yellow Starting communication.
Online (General Monitoring) Green (Blinking) Online(General Monitoring). Blink on when a

message/command sending out, blink off when
acknowledge is received
Online (Group Monitoring) Blue (Blinking) Online (Group Monitoring). Blink on when a
message/command sending out, blink off when
acknowledge is received
Error Red Communication error.
2VAA000813-230 A 6-3
Instant Trend 6. Monitor/Tune Configurations
6.2.5 Instant Trend

The instant trend is a simple window to easily monitor the function block output status and value with curve. This is available
in the online mode. Multiple instant trends can be opened for different function block outputs simultaneously but not more
than the maximum number configured in environment properties. The instant trends are managed as per control logic
document and closed automatically when user closes the related control logic document.
An example of Instant Trend display can be referred from Figure 6-4.
Figure 6-4: Instant Trend Display
6.3 Communication Settings for Monitoring

After initial installation, Control Engineering limits the communication rate of monitoring function to the default value (10
blocks per second).
Perform the following steps to change the rate of monitoring:
1. Select Tools > Options from Control Engineering program window.
2. Select Communication Settings tab.
3. Change the value for Monitor.
NOTE: It is recommended to use default values for these communications settings. Increasing values to very large num-
ber may have impact to system communication under extreme circumstance. System communication load should be
measured and evaluated to avoid overloading after the change. Contact ABB technical support or local business organi-
zation for assistance if users have issues in communication settings.
6-4 2VAA000813-230 A
A. Standard Entities
The Control Engineering software provides system folders in the exchange that contain standard entities for use by the
Automation Architect. This appendix lists and describes the entities in the exchange folders.
Table A-1 lists and describes each standard entity in the system folders on the exchange. Figure A-1 through Figure A-4
show the entities.
Table A-1: Standard Entities
Name Description
Borders (Borders > Traditional Borders Folder)
AHBORD Horizontal border with ABB logo and control network, HCU, and controller.
AHBORDG Horizontal border without ABB logo, but with control network, HCU, and controller.
AHGBORD Horizontal border with ABB logo, but without control network, HCU, and controller.
AHGBORDG Horizontal border without ABB logo and control network, HCU, and controller.
AVBORD Vertical border with ABB logo, but with control network, HCU, and controller.
AVBORDG Vertical border without ABB logo and control network, HCU, and controller.
AVGBORD Vertical border with ABB logo, but without control network, HCU, and controller.
AVGBORDG Vertical border without ABB logo and control network, HCU, and controller.
Borders (Borders > Enhanced Borders 1 or 2 Folders)1
AHBORDx Horizontal border with ABB logo and control network, HCU, and controller.
AHBORDGx Horizontal border without ABB logo, but with control network, HCU, and controller.
AHGBORDx Horizontal border with ABB logo, but without control network, HCU, and controller.
AHGBORDGx Horizontal border without ABB logo and control network, HCU, and controller.
AVBORDx Vertical border with ABB logo, but with control network, HCU, and controller.
AVBORDGx Vertical border without ABB logo and control network, HCU, and controller.
AVGBORDx Vertical border with ABB logo, but without control network, HCU, and controller.
AVGBORDGx Vertical border without ABB logo and control network, HCU, and controller.
Constant Blocks (Shapes Folder)
B0 Boolean zero (fixed block 0).
B1 Boolean one (fixed block 1).
R-1 Real negative one (fixed block 4).
R-100 Real negative one hundred (fixed block 3).
R0 Real zero (fixed block 5).
R1 Real one (fixed block 6).
R100 Real 100 (fixed block 7).
RMAX Maximum real number allowed - +9e18 (fixed block 9).
RMIN Minimum real number allowed - -9e18 (fixed block 8).
SETBLK Modifiable block number for IMLMM02 and NMLMM02 modules only.
ZERO Integer or real zero (fixed block 2).
Doc Shapes (Shapes Folder)
ADRBLK Shape used to provide NET (Network), UNIT (Control Unit), and CONT (Controller)
addresses as part of a CLD.
2VAA000813-230 A A-1
Table A-1: Standard Entities (Continued)
Name Description
BPB Boolean push button input - for logic drawings.
CID1BLK Shape used to provide ABB Inc. company name as part of a CLD.
CID2BLK Shape used to provide ABB Inc. confidential statement as part of a CLD.
DWGBLK Shape used to provide CLD document information (Document number, Sheet
number) as part of a CLD.
FU Fuse.
GND Ground - used for wiring drawings.
HOUTBLK Shape used to provide a basic horizontal border (outer edge) as part of a CLD.
PRA Forward (right) facing arrow head.
PRAI2 Shape used for standard external connection drawings.
PRAR Reverse (left) facing arrow head.
PRBRF Bracket open to left (forward facing).
PRBRR Bracket open to right (reverse facing).
PRCF Cable designation - forward facing.
PRCLC2 Shape used for standard external connection drawings.
PRCLC3 Shape used for standard external connection drawings.
PRCR Cable designation - reverse facing.
PRD Small dot.
PRD4 Large dot.
PRD6 Larger dot.
PRIF Shape used for standard external connection drawings.
PRIF1 Shape used for standard external connection drawings.
PRIOF Shape used for standard external connection drawings.
PRIOR Shape used for standard external connection drawings.
PRIR1 Shape used for standard external connection drawings.
A-2 2VAA000813-230 A
Name Description
PRISB Isolated system ground bus - for wiring drawings.
PRNTD Shape used for standard external connection drawings.
PRNTE Shape used for standard external connection drawings.
PRNTS Notes used on standard external connection drawings.
PROF1 Shape used for standard external connection drawings.
PROF2 Shape used for standard external connection drawings.
PROR Shape used for standard external connection drawings.
PRSLOC Slave location box for external connection drawings.
PRSSO Shape used for standard external connection drawings.
PRT5 Wire connection for wiring drawings - for wiring drawings.
PRTB Terminal block wire connection - for wiring drawings.
PRTLOC Termination location box for external connection drawings.
PRTW Twist with shape - component of shape TW.
PRWC Wire connection shape - for wiring drawings.
PRWCS Small wire connection shape - for wiring drawings.
PRWL Wire to cable connection (wire on left) - for wiring drawings.
PRWR Cable to wire connection (wire on right) - for wiring drawings.
PRXU Dipshunt used for standard external connection drawings.
PRXUB Dipshunt used for standard external connection drawings.
PRXUB1 Dipshunt used for standard external connection drawings.
RCC Relay contact - energize to close.
RCO Relay contact - energize to open.
REF1BLK Shape used to provide CLD, Sheet, Title, Customer, Plant, Contracting Firm, Job,
and Reference information as part of a CLD.
REF2BLK Shape used to provide Title, Customer, Plant, Contracting Firm, Job, and
Reference information as part of a CLD.
REL Relay coil.
RES Resistor - horizontal orientation.
RESV Resistor - vertical orientation.
REVBLK Shape (grid) used when providing a CLD revision, date, comment, designer, and
reviewer information as part of a CLD.
TB12 Twelve point terminal block.
TW Twist with shape for twisted pair wires - for wiring drawings.
V125 125 VDC source symbol.
V24 24 VDC source symbol.
VOUTBLK Shape used to provide a basic vertical border (outer edge) as part of a CLD.
Cross-References (Shapes Folder)
BDIN Boolean control input - for logic drawings.
BDIND Boolean operator indication - for logic drawings.
2VAA000813-230 A A-3
Name Description
BDOUT Boolean control output - for logic drawings.
IREF Input reference bubble (off page signal connection).
IREFO Left-facing output reference bubble (not frequently used).
OREF Output reference bubble (off page signal connection).

NOTE:
1. The only difference between borders in the enhanced borders 1 and enhanced borders 2 folders is a
slightly different location of the control logic document name and sheet number data.
Figure A-1: Standard Entities (1 of 4)
A-4 2VAA000813-230 A
2VAA000813-230 A A-5
A-6 2VAA000813-230 A
2VAA000813-230 A A-7
A-8 2VAA000813-230 A
B. CLD Lockable Properties

Table B-1 details the control logic entity properties that will be CLD locked when the entity is CLD locked and which
properties that can be locked individually. All properties that can be CLD locked individually can also be individually set as
template controlled.
NOTE: Locking a sheet locks all entities on the sheet. Locking a CLD locks all sheets in the CLD.
Table B-1: Linking-Related Logic Entity Properties
Entity Type Property Lockable with Entity Individually Lockable
Arc Layer Yes No
Line type Yes No
Line width Yes No
Radius Yes No
Location Yes Yes
Filled Yes No
Start point Yes No
End point Yes No
Circle Layer Yes No
Line type Yes No
Line width Yes No
Radius Yes No
Location Yes Yes
Filled Yes No
Constant block Layer Yes No
Line type Yes No
Line width Yes No
Symbol name No No
Location Yes Yes
Orientation Yes No
Scale Yes No
Custom border Layer Yes No
Line type Yes No
Line width Yes No
Symbol name Yes No
Location Yes Yes
Orientation Yes No
Scale Yes No
2VAA000813-230 A B-1
Table B-1: Linking-Related Logic Entity Properties (Continued)

Document shape Layer Yes No
Line type Yes No
Line width Yes No
Symbol name Yes No
Location Yes Yes
Orientation Yes No
Scale Yes No
Function code Layer Yes No
Line type Yes No
Line width Yes No
Symbol name No No
Location Yes Yes
Orientation Yes No
Scale Yes No
FCData object Tag GUID No No

associated with a
function code Tag name No No
Tag description No No
Spec 1 Yes Yes
Spec 2 Yes Yes
... ... ...
Spec n Yes Yes
I/O function code Layer Yes No
Line type Yes No
Line width Yes No
Symbol name No No
Location Yes Yes
Orientation Yes No
Scale Yes No
B-2 2VAA000813-230 A

FCData object Tag GUID No No
associated with an
I/O function code Tag name No No
Tag description No No
Spec 1 Yes Yes
Spec 2 Yes Yes
Spec 3 Yes Yes
... ... ...
Spec n Yes Yes
Descriptor 1 No No
Descriptor 2 No No
Descriptor 3 No No
... ... No
Descriptor n No No
Line Layer Yes No
Line type Yes No
Line width Yes No
Location Yes Yes
Line path Yes No
Polygon Layer Yes No
Line type Yes No
Line width Yes No
Location Yes Yes
Line path Yes No
Filled Yes No
Rectangle Layer Yes No
Line type Yes No
Line width Yes No
Top left Yes No
Bottom right Yes No
Location Yes Yes
Filled Yes No
Text Layer Yes No
Line type Yes No
Line width Yes No
Character size Yes No
Location Yes Yes
Orientation Yes No
String Yes No
2VAA000813-230 A B-3

Input reference Layer Yes No
Line type Yes No
Line width Yes No
Symbol name No No
Location Yes Yes
Orientation Yes No
Scale Yes No
IREF data object Descriptor 1 No No

associated with input
reference
Output reference Layer Yes No
Line type Yes No
Line width Yes No

Symbol name No No
Location Yes Yes
Orientation Yes No
Scale Yes No
ORef data object Descriptor 1 No No

associated with
output reference
Signal Layer No No
Line type No No
Line width No No
B-4 2VAA000813-230 A
INDEX
INDEX Save 2-4

Scale 4-8
Signal 3-1, 3-9
A System shape 3-1, 3-9
Tags 2-2, 4-3
Abbreviations 1-3
Text 3-11, 4-7
Automation architect
User shape 3-2, 3-9, 4-8
Cursor 2-15
Control logic template 3-1, 3-12, 4-8
Environment 2-5
Controller configuration overview 1-1, 2-1
Exchange 2-2, A-1
Controller configuration procedure 2-1
Grid 2-15
Cross-reference name 4-4
Layers 2-7
Cut, copy, paste entities 4-5
Magnify view 2-8
Menus 2-3 D
Multiple windows 2-4 Delete entities 4-5
Online mode 5-1 Document conventions 1-2
Pan view 2-9 Document modes 2-4
Redo commands 4-11 E
Refresh view 2-9 Entities 3-1
Repeat last command 4-10 Entity editing 4-2
Standard entities A-1 Entity selection 4-1
Toolbar 2-5 Example control logic document 6-1
Undo commands 4-11 Exchange 2-2, A-1
Workspace 2-5 Explode entities 4-6
B F
Block number 4-4 Function code 3-4
Border 3-1, 3-2, 4-8 Function code specs 4-6
Branch 3-9 G
C Glossary 1-3
Circle 3-3 H
Constant block 3-3 How to use this instruction 1-2
Control logic documents
Block number 4-4
I
Border 3-1, 3-2, 4-8 I/O connector 3-6
Branch 3-9 Instruction content 1-1
Circle 3-3 Intended user 1-1
Close 2-4 L
Constant block 3-3 Line 3-8, 4-5
Control logic template 3-1, 3-12, 4-8 Linking 3-12
Cross-reference name 4-4 M
Cut, copy, paste 4-5 Macro 3-1, 3-9, 4-8
Delete 4-5 Move entities 4-7
Distance measure 2-16 N
Drawing entities 3-2
Non-system folders 2-2
Entities 3-1
Entity editing 4-2 O
Entity selection 4-1 Online mode 5-1
Example 6-1 R
Exchange 2-2 Rectangle 3-9
Explode 4-6 Redo commands 4-11
Function code 3-4 Reference connector 3-7
Function code specs 4-6 References 1-3
Grid 2-15 Repeat last command 4-10
I/O connector 3-6 Rotate entity 4-8
Layers 2-7 S
Line 3-8, 4-5 Scale entities 4-8
Macro 3-1, 3-9, 4-8 Signal 3-1, 3-9
Monitor/tune 5-1 System folders 2-2
Move 4-7 System shape 3-1, 3-9
Multiple sheets 3-11
Print 2-4
T
Tag point 3-11
Rectangle 3-9
Tags 4-3
Reference connector 3-7
Terms 1-3
Revise 2-4
Text 3-11, 4-7
Rotate 4-8
2VAA000813-230 A 1
INDEX
Trend point 3-11

U
Undo commands 4-11
User shape 3-2, 3-9, 4-8
2 2VAA000813-230 A
—
Visit us
solutions.abb/symphonyplus
Document ID: 2VAA000813-230 Rev. A

solutions.abb/controlsystems
Back Cover

2VAA000813-230 A en Splus Engineering 2.3 Automation Architect User Manual

Uploaded by

Copyright:

Available Formats

You might also like

2VAA000813-230 A en Splus Engineering 2.3 Automation Architect User Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2VAA000813-230 A en Splus Engineering 2.3 Automation Architect User Manual

Uploaded by

Copyright:

Available Formats

—

ABB Ability™ Symphony® Plus

ABB Ability™ Symphony® Plus

Trademarks and copyright

Release: May 2020

2. Controller Configuration Overview .............................................................. 2-1

3. Configuration Components .......................................................................... 3-1

4. Editing Configurations .................................................................................. 4-1

4.3.8 Explode ............................................................................................................4-5

5. Example Configuration ................................................................................. 5-1

6. Monitor/Tune Configurations........................................................................ 6-1

A. Standard Entities ........................................................................................... A-1

B. CLD Lockable Properties .............................................................................. B-1

Table 1-1: Glossary of Terms and Abbreviations ................................................................ 1-3

Figure 2-1: S+ Engineering Automation Architect Window.................................... 2-1

Figure 6-4: Instant Trend Display ......................................................................... 6-4

About This Book

Use of Information, Tip, and Warning Icons

Information icon: It alerts the user to pertinent facts and conditions.

1.3 Intended User

1.4 Instruction Content

Controller Configuration Overview

CLD Lockable Properties

1.5 How to Use this Instruction

1.6 Document Conventions

User data input

CUP [port] [baud] [file_name.CSP]

Part number: 1234567?0

1.7 Glossary of Terms and Abbreviations

Table 1-1: Glossary of Terms and Abbreviations

Controller Directs field processes e.g. S+ SD Series controller (HC800, SPC800,

Control Logic In S+ Engineering Control Engineering, a CLD is a grouping of sheets

Control Logic In S+ Engineering Control Engineering, a CLT is a Preconfigured logic

Exchange The Exchange in Control Engineering is a project-wide repository of system

Project The largest grouping of configuration information (displays, control logic

1.8 Reference Documents

Table 1-2: Reference Documents

2VAA000812* S+ Engineering 2.3 Harmony engineering User manual

2VAA000844* S+ Engineering Function code reference User manual

Table 1-2: Reference Documents (Continued)

2VAA005210-230 S+ Engineering 2.3 Third party software licenses Reference manual

2. Controller Configuration Overview

Figure 2-1: S+ Engineering Automation Architect Window

2.2 General Configuration Procedure

2.4 Tag Assignment

2.5 CLD Editing Modes

2.6 Automation Architect Window Menus

2.7 Document Operations

2.7.6 Document Modes

Read Only Access

2.8 Multiple Document Windows

2.9 Document Workspace

Figure 2-2: Automation Architect Toolbar

2.9.2 Environment Properties

Figure 2-3: Tools Options General Tab

Figure 2-4: Tool Options View Tab

Figure 2-5: Override Specification Display Location per Function Code

Figure 2-6: Tools Options View Show Property Example